Road Charging Interoperability - PowerPoint PPT Presentation

1 / 45
About This Presentation
Title:

Road Charging Interoperability

Description:

RCI Decision Meeting, 31 May 2006. Today's objectives meeting. Understand ... line RSE and the GPS location service and access to motion sensor and tachograph. ... – PowerPoint PPT presentation

Number of Views:68
Avg rating:3.0/5.0
Slides: 46
Provided by: Stephani322
Category:

less

Transcript and Presenter's Notes

Title: Road Charging Interoperability


1
Road Charging Interoperability
Steering CommitteeDecision Meeting31 May 2006
2
Todays objectives meeting
  • Understand the current status RCI
  • Approve the evaluation, select suppliers
  • Decide on how to continue the project

3
Agenda
  • 11h00/11h30 Start of the meeting
  • Morning session without Commission
  • Current status
  • Presentation on proposals that the RCI project
    received
  • Discussion, open questions
  • Lunch
  • Afternoon session with Commission
  • Presentation of the evaluation results
  • Discussion
  • Conclusions and next steps
  • 16h00 end of meeting

4
Current status
  • Context of the RCI project

5
time
6
(No Transcript)
7
(No Transcript)
8
(No Transcript)
9
RCI scope and objectives
Objective in context EETS
  • converge and establish consensus on an
    appropriate architecture and interface
    identification for interoperability that could
    contribute to the further definition of EETS
  • To specify and implement the RCI prototype that
    operates in any of the existing RCI road charging
    environments.

Basis
10
RCI scope and objectivesThe RCI specifications
  • Define interfaces that can make existing systems
    more open" (allowing different suppliers to
    manufacture equipment that can be certified
    against these specifications and that can operate
    in different contexts)
  • Contribute to the convergence of future tolling
    systems and the evolution of existing tolling
    systems as such allowing for a greater
    re-usability of standard components across
    different systems
  • Should be public and as free of unreasonable
    IPR and should contribute to the technical basis
    for the formulation of standardisation proposals.

11
Current status
  • Consensus meeting February 2006

12
Status further agreements
  • Support for the Supplier Offering Document
  • Prototype should implement all RCI requirements
    not subset
  • No exclusion (yet) of specific architectural
    scenarios
  • Support for EG11 also in Italy (? one DSRC
    tolling application 2 DSRC stacks)
  • Support for Toll Collect by
  • Suppliers MUST propose the implementation of
    functionality that is required for operation and
    testing of the RCI prototype in the Toll Collect
    environment on the basis of Toll Collect
    specifications
  • If suppliers cannot implement the functionality
    themselves that is needed for the operation and
    testing of the RCI prototype in the Toll Collect
    environment, suppliers MUST use all reasonable
    endeavours to integrate support in their
    prototype for a Toll Collect functionality that
    is provided in a suitable wrapper under
    responsibility by TSI
  • And several others

13
Status Intellectual Property protection
  • Preliminary Agreement
  • Allowed partners to sign the contract
  • All partners signed dated on 29 June 2006
  • Not a basis for collaboration and development

14
Status Intellectual Property protection
  • Consortium Agreement
  • Approved by the SC
  • Required basis for project development
  • Al new suppliers approved this agreement already
  • Almost all RCI partners formally signed and sent
    to ERTICO COFIROUTE can provide its signature in
    cooperation with ASFA by 7 June
  • Consortium Agreement with all signatures
    including those of suppliers by General Assembly
    on 13 June

Can this be confirmed and do we all agree?
15
Status Intellectual Property protection
  • RCI starting point for patents in general
  • RCI specifications should be based on solution
    which best meet the technical objectives of RCI,
    not the best patented
  • RCI members are fully entitled to hold and
    benefit from IPRs which they may own
  • Find a balance between the needs of
    standardisation for public use and the rights of
    the owners of IPRs
  • Seek to reduce the risk that investment in the
    definition of standards could be wasted as result
    of an IPR
  • Knowledge of existence of essential IPR is
    required as early as possible

16
Status Intellectual Property protection
  • Proposal for a RCI IPR Policy
  • RCI partners could on voluntary basis respond to
    call for IPR, identifying their essential IPRs
  • IPR by external partners cannot be identified or
    only be identified on an occasional basis by the
    RCI project
  • The analysis of identified IPR and the
    identification of IPR by external companies is
    the responsibility of each individual RCI partner

Do we all agree?
17
Approve evaluation results
  • Overview proposals

18
5 Proposals
  • 3 consortia and 2 times a single company

19
Technolution coordinated proposal
20
Functionality, Technolution
  • OBE operates as event detection and recording
    device
  • GPRS connection to the EETS centre
  • Receive and store receipts also for reading by
    toll charger

21
Software, Technolution
  • The CEN DSRC modem includes the software for the
    applications in Austria, France and Spain
  • The UNI modem includes software for the Italian
    system
  • Combination of DSRC modem OBU for Swiss
    environementTo
  • DSRC IR modem OBU toll gateway for Toll
    Collect environment toll gateway processes data
    that comes from OBU, map matching, define the fee
    to be paid and pass on information to toll
    charger

22
Hardware, Technolution
23
Vision on deployment, Technolution
24
CS coordinated proposal
25
Functionality, CS
26
Software, CS
27
Hardware, CS
28
Vision on deployment, CS
29
FELA coordinated proposal
30
Functionality, FELA
  • General
  • support of a proprietary initialisation and
    maintenance tool for workshops to set-up the
    vehicle characteristics and contract specific
    data
  • declaration and inspection of vehicle
    characteristics on the OBU
  • transfer of accumulated log event data over CN
  • Remote software update over CN
  • Status indicator
  • Internal analysis of failures, incidents and
    problems
  • Diagnostic and service interface over Bluetooth
  • Real-Time context related information
  • Support of a degraded mode
  • Plus the functionality for the local schemes
  • Not supported are the following functions
  • Pre-pay mode in Telepass and LKW-Maut Austria
  • LSVA PKE security
  • The use of the genuine workshop initialisation
    and maintenance tools from LSVA and LKW-Maut
    Germany (Toll Collect) scheme

31
Software, FELA
32
Hardware, FELA
33
Vision on deployment, FELA
  • RCI prototype close to mass production, following
    steps needed
  • Large scale trials gt 300 vehicles with EETS
  • Verification of business processes
  • Establishment of production channels
  • In-vehicle integration will happen in two phases
  • mainly an after market
  • integration will become in short time also an
    issue to be considered while designing a new
    vehicle
  • Deployment depends on EETS provider and
    operators intention to work together with these
    partners

34
EFKON coordinated proposal
35
Functionality, EFKON
  • Austria (ASFINAG), France (TIS) and Spain (VIA-T)
    by using the RSE based DSRC communication with
    the corresponding infrastructure.
  • Italy (TELEPASS) by using the RSE based DSRC
    communication with the Telepass infrastructure.
  • Germany (TOLL COLLECT) by running the complete
    TollCollect application including all interfaces
    and functions for tolling and enforcement, i.e.
    GSM, GPS, Infrared and motion sensor.
  • Switzerland (LSVA) by running the DSRC
    communication installed at the Swiss border line
    RSE and the GPS location service and access to
    motion sensor and tachograph. Optionally-on call
    of the RCI consortium, the OBU will also have
    implemented a smart card interface which may then
    be configured to accept LSVA smart cards.
  • Generic
  • to communicate with an EETS infrastructure device
    (GSM services, SMS, CS Data or GPRS).
  • The OBU HMI will be based on functional elements
  • An appropriate solution to identify the roaming
    situation, i.e. the entering or leaving road
    sections or areas subject to toll will be
    implemented by EFKON. The tradeoffs of geographic
    information based or RSE triggered autonomous
    identification by the OBU shall be defined in the
    RCI project after acceptance of consortia.

36
Software, EFKON
  • architecture model 3a
  • Several applications are running concurrently
    whereas the active application depends on the
    region of the according provider.
  • The OBU provides a boot loader and an operating
    system capable to run several applications
  • it provides an API to grant access to all
    interfaces necessary to implement toll
    applications for all mentioned contexts.
  • The OBU provides a common database related to
    vehicle data and customer data as required by the
    superset of existing contexts
  • Clarification is to be made for switching between
    different DSRC contexts.

37
Hardware, EFKON
38
Vision on deployment, EFKON
  • EFKON is capable of organisation of manufacturing
    of the EETS OBU, prototyped in RCI, within 12-15
    months
  • When industrialized devices for in-vehicle
    integration, it is expected that there will be
    several suppliers.
  • EFKON own market intelligence dientifies a market
    of about 40 million trucks in the total of
    Europe, including Russia. If the mass produced
    OBU in 3-5 years from now is sold at EUR 100,00
    per unit, this represents a market of 4 billion
    Euros (4E12) in total, which may genrate sales of
    EUR 5-600 million per year. It is EFKONs
    expectation that such a device will be mandated
    sooner or later. The main issues to be resolved
    are
  • Agreement of all toll operators to support an
    independent EETS. This includes governments that
    operate taxing schemes or municipalities
    operating congestion charging schemes
  • Mandating the use of a standardized unit, and
    stopping deployments of non-compliant systems
  • Defining a standardized way for installation of
    the OBU it is currently quite expensive because
    of the motion odometer access. Our technology can
    do without.

39
SIEMENS VDO coordinated proposal
40
Functionality, SIEMENS VDO
41
Software, SIEMENS VDO
42
Hardware, SIEMENS VDO
43
Vision on deployment, SIEMENS VDO
44
What to do before presenting the evaluation
results?
  • SC is not asked to evaluate the proposals
  • SC is asked to approve the evaluation
  • Y ? direct selection
  • N ? define conditions that should be first
    fulfilled by suppliers
  • NN ? majority needed and need to agree on
    extension of tender process

Do we all agree?
45
LUNCH
  • EC will join at 14h to start with the evaluation
    results
Write a Comment
User Comments (0)
About PowerShow.com