1|Kapsch TrafficCom
ETC Telematics InterfaceUtilizing electronic toll collection systems
for secondary telematics applications
3|Kapsch TrafficCom
ETC-based Traffic Telematics
Trend• Utilizing electronic toll systems
as the “backbone” for secondary traffic telematicssolutions
Benefits• Cost reduction and better data
for traffic management, information and planning
• Improved safety and securitythrough better traffic enforcement and observation
• Better service for the driverthrough end-user services (> increasing acceptance for toll)
• Additional source of incomeby offering commercial services
Traffic Management,Information & PlanningTrafficTraffic Management,Management,
Information & Information & PlanningPlanning
Safety&
Security
SafetySafety& &
SecuritySecurity
MobilityServices
+ Industry
Solutions
MobilityMobilityServicesServices
+ + Industry Industry
SolutionsSolutions
Electronic Electronic Toll SystemToll System
4|Kapsch TrafficCom
�Traffic Monitoring�Traffic Analysis
TrafficTraffic Management, Management, Information Information & & PlanningPlanning
�ANPR �HazMat Tracking
SafetySafety & & SecuritySecurity
�OBU-based Access�OBU-based Payment
EndEnd --useruser MobilityMobilityServicesServices
�Fleet Tracking�Pay-as-you-drive
Insurance
Industry SolutionsIndustry Solutions
Selected Example Applications
Electronic Toll Electronic Toll CollectionCollection SystemSystem
6|Kapsch TrafficCom
Project Overview
• Telematics Application Interface provides data for further processing in telematics applications (e.g. in the National Traffic Information Center).
• Base data is derived from (1) DSRC transactions generated at TS and ES by vehicles equipped OBU as well as (2) the laser scanners of ES.
• Field of application of the current version: traffic management,information and planning.
7|Kapsch TrafficCom
System Overview
EFCCentral System
EFCCentral System
Tel
emat
ics
App
licat
ion
Inte
rfac
e
WANWAN
Tolling Stations- DSRC Transactions
Enforcement Stations- DSRC Transactions - Short-term/Long-term Traffic Data
exte
rnal
App
licat
ions
(e.g
. Tra
ffic
Man
agem
ent S
yste
m)
TelematicsService 1
TelematicsService 2
TelematicsService n
TelematicsService 4
TelematicsService 3
Telematics base data:- Real-time data- Historical data
8|Kapsch TrafficCom
Telematics Application Interface – Main Requirements
Unidirectional interfaceExternal telematics applications can only read data
Read-only principle
Logging Module (LM) for access and volume logging
System shall support commercial data selling
Logging
Utilization of the interface shall be as simple as possible /State-of-the-art technology
Data of road users as well as sensitive operational data must by protected (no access to data by unauthorized applications)
External telematics applications must not influence toll system performance negatively
Description
XML WebServices interfaces (easy and common interface technology)
Easy-to-use
Access Control Module ensures restricted data access:Authentication/Authorization by Username/Password (possible future extension: certificates)
Telematics Platform for capsulation of the central toll system (no direct access to tolling infrastructure possible by external applications)
Measure
User Privacy / Data Protection / Security
System Performance
(Toll System)
Requirement
9|Kapsch TrafficCom
System Architecture
TelematicsPlatform
historicaldata
real-timedata
Toll SystemBack OfficeTraffic
Data ES
Toll Transactions
TelematicsApplication 1
TelematicsApplication 2
TelematicsApplication 3
…
TelematicsApplication 4
Telematics Application Interface
TollDWH
tMC
Logg
ing
Aut
horiz
atio
n
Aut
hent
icat
ion
XML
XML
XML
ACM
LM
TelematicsApplication Server
Administration of access rightsCapsulation of the toll back office
10|Kapsch TrafficCom
Sample XML File: Short Term Data from ES
<?xml version="1.0" encoding="utf-8"?>
<ShortTerm />
<Error code="0" text="" />
<ShortTermConfig start=" 01.04.08 13:45:00" length="15" />
<ResultData>
<StationId id="2460">
<ResultSet lane="0"
q_all_vehicles="92" [Traffic volume - all vehicles]
q_hgv="34" [Traffic volume - trucks and similar vehicles]
avg_v_pc="102" [Average speed passenger - cars and similar vehicles]
avg_v_hgv="72“ [Average speed - trucks and similar vehicles]
nettimegap="5“ [Net time gap - all vehicles]
occupancy="20" [Occupancy of the sensor]
stddev_all="0" [Standard deviation speed - all vehicles]
smoothed_v_all="102" /> [Smoothed velocity - all vehicles]
<ResultSet lane="1" q_all_vehicles="78" q_hgv="28" avg_v_pc="101" avg_v _hgv="71“
nettimegap="6" occupancy="17" stddev_all="0" smooth ed_v_all="101" />
</StationId>
[THE STATION SECTION is REPEATED FOR ALL STATIONS]
</TelematicsPlatform>
12|Kapsch TrafficCom
Interactive Telematics Channel – Hybrid System
Tel
emat
ics
App
licat
ion
Inte
rfac
e
TAI provides data derived from the toll system for telematics purposes
Telematics Message Interface
TMI = Communication channel allowing to exchange telematics messages (independent from the toll system) between telematics applications and GNSS OBUs
13|Kapsch TrafficCom
Telematics Messages Interface - Features
• XML Web Service interface
• Generic messages (have to be defined according to the requirements of a certain
application)
• Bidirectional communication
• One interface to interact with OBUs of different Issuers (group calls are possible)
• Access control mechanism (authentication and authorisation)
• Logging mechanism
14|Kapsch TrafficCom
Telematics Messages Interface – Generic Messages
• TelematicMessage
• Priority
• Message Type
• Text
• Status
• Address List
• TelematicOBUConfig
• Priority
• Address List
• Configuration Tupel
Message Content depends on the type of application and has to bedefined between Telematics Application Provider and OBU Issuer
15|Kapsch TrafficCom
Peter UmmenhoferTechnical Manager Telematics Solutions
Kapsch TrafficCom AGLakeside B03 | A-9020 Klagenfurt | Austria
Tel. +43 (0) 50 811 7800 Mobil +43 (0) 664 628 7800Fax +43 (0) 50 811 99 7800
e-mail [email protected]
16|Kapsch TrafficCom
Telematics Messages Interface Web-Services
TMI Web-Services:
• TMI Service Interface is required at
OBU Proxy
• Callback Interface for incoming
messages is required at TelematicsApplication
Telematics Application n
Client 1Client
ContextServer
Proprietar
y Language
1
Context Layer
AL
Hybrid OBUHybrid OBUHybrid OBUKapsch Area OBU
ciphered
…
Proxy
TMI Service Interface
Arbitration Layer (Dispatcher)
TMI Web Service
TMI ProxyInterface Callback
Callback
CallbackInterface
17|Kapsch TrafficCom
Telematics Messages Interface
TMI Security:
• Web-service protected by VPN
Access Control
• Access Control Module
• Authentication by Username/Password (possible future extension: certificates)
• Authorisation by Central System lookup
• Contracts stored in ACM
• Each Call is verifiedTelematics
Application n
Client 1Client
ContextServer
Proprietar
y Language
1
Context Layer
AL
Hybrid OBUHybrid OBUHybrid OBUKapsch Area OBU
ciphered
…
Proxy
TMI Service Interface
Central System
Arbitration Layer (Dispatcher)
Do Authentication and Authorisation
TMI Web Service
AccessControlModule
TMI ProxyInterface Callback
Callback
CallbackInterface
VPN Tunnel
VPN Tunnel