This Technical Report (TR) contains an analysis of the technical and operational feasibility of using a generic ITS Station as specified in ETSI EN 302 665, Intelligent Transport Systems (ITS); Communications Architecture, for EFC applications compliant to the requirements specified in ISO 17573, EN ISO 12855, CEN ISO/TS 17575 (all parts), EN ISO 14906, EN 15509, CEN ISO/TS 12813, CEN ISO/TS 13141 and CEN/TS 16439.

The scope of this Technical Report includes:

description of the context of Cooperative ITS and the ITS Stations;
providing details of the context of EFC applications;
outlining the basic architectural concepts and role model of both EFC and Cooperative ITS;
identification of core requirement areas for operation of an EFC application on an ITS Station;
specification of a set of recommendations for functional, operational and security requirements to the ITS Station supporting the EFC application(s);
description of a possible role model in which the roles known in EFC applications make use of the roles in the C-ITS system in order to provide EFC services in an C-ITS context;
provision of considerations in particular areas of EFC like certification and governances;
guideless and recommendations for further standardization work in this area;
emphasizing on security related elements of EFC that need to be considered in a C-ITS environment.

The scope of this Technical Report is limited to in-vehicle ITS Stations. However, an EFC service always requires the involvement of in-vehicle and central functionalities. Furthermore, for enforcement purposes as well as in DSRC based toll domains for toll charging purposes also, it is essential that road-side based functions are provided and operated. In order to facilitate EFC services a set of functionalities, tasks and responsibilities are defined and specified in an EFC role model (ISO 17573). These functionalities, tasks and responsibilities are shared between the roles Toll Charger, Toll Service Provider, Road User and Interoperability Management. All these roles interact with each other. As a consequence this Technical Report provides in various areas explanations that are beyond the in-vehicle environment. This is required in order to present the full environment and context. It keeps the readability of this document at a sound level and provides valuable information to those readers which are not yet familiar with EFC in detail.

Outside the scope of this Technical Report is:

detailed technical specifications for EFC services and applications on C-ITS systems;
implementation specific elements.

PDF Catalog

PDF Pages	PDF Title
3	CEN/TC 278
7	Foreword
8	Introduction
10	1 Scope 2 Normative references
11	3 Terms and definitions
14	4 Symbols and abbreviations
15	5 Context of C-ITS 5.1 Definition of C-ITS 5.1.1 Introduction
16	5.1.2 The European Commission basic definition 5.1.3 The vehicle active safety viewpoint 5.1.4 The CEN/ETSI/ISO definition
17	5.2 C-ITS role model and business architecture 5.2.1 Role model 5.2.1.1 Introduction 5.2.1.2 Role model introduced by ISO Figure 1 — Organizational architecture with the four major roles
18	Figure 2 — Sub-roles of System Operation – process chain 5.2.1.3 Role model developed in the CVIS project
19	Figure 3 — CVIS roles [source and courtesy of CVIS] 5.2.2 Business architecture
20	Figure 4 — Conceptual business model template [source and courtesy of CVIS]
21	Figure 5 — The service “Dangerous goods / route guidance” modelled with conceptual business modeller [source and courtesy of CVIS] 5.3 Technical architecture 5.3.1 ITS Station architecture
22	Figure 6 — Simplified ITS station architecture [source: ISO 21217:2010] 5.3.2 ITS communication access technologies
24	5.3.3 Application provisioning and life cycle management Figure 7 — Service deployment and provisioning (adapted from CVIS)
25	5.3.4 Security 5.4 Legal aspects and background 5.4.1 European action plan and directive for ITS
26	5.4.2 User privacy and data protection 5.4.3 Liabilities regarding application performance / suitability for use 5.5 Overview of standardization activities 5.5.1 Introduction
27	5.5.2 Basic set of ITS applications
28	5.5.3 CEN/TC 278/WG 16 on cooperative systems 5.5.4 ISO/TC 204/WG 18 on cooperative systems
29	5.5.5 ISO/TC 204/WG 16 on wide area communications/protocols and interfaces 5.5.6 ETSI Technical Committee on ITS (ETSI TC ITS) 5.6 Overview of R&D projects and other relevant initiatives 5.6.1 CVIS project on cooperative vehicle infrastructure systems
30	Figure 8 — CVIS high-level architecture [source and courtesy of CVIS] 5.6.2 SAFESPOT project on road safety related applications
31	5.6.3 eCoMove project on road transport efficiency applications 5.6.4 DRIVE C2X project with focus on field trials 5.6.5 Car-to-car communication consortium (C2C-CC)
32	5.6.6 EasyWay project on applications for the major EU road network 5.6.7 COMeSafety and COMeSafety2 projects on road safety applications 5.6.8 Amsterdam Group 6 Context of EFC 6.1 Definition of EFC
33	6.2 EFC role model and business architecture 6.2.1 Role model Figure 9 — The EFC role model [source: ISO 17573:2010]
34	6.2.2 Business architecture
35	6.3 Technical architecture 6.3.1 Overview Figure 10 — Data flow view of the technical architecture
37	6.3.2 Communication architecture
38	Figure 11 — Component and interface view of the technical architecture 6.3.3 Autonomous OBE / Front End implementation
39	Figure 12 — Examples of data processing steps in thin and thick client approaches 6.3.4 EFC security
40	6.4 Additional major aspects 6.4.1 Interoperability 6.4.2 Value added services based on EFC OBE
42	6.4.3 EFC outside Europe
43	6.5 Legal aspects and background 6.5.1 Toll domain specific 6.5.2 European Electronic Toll Service (EETS)
44	6.5.3 User privacy and data protection 6.6 Overview of standardization activities 6.6.1 CEN/TC 278/WG 1 on Electronic fee collection and access control applications 6.6.2 ISO/TC 204/WG 5 on electronic fee collection and access control applications 6.6.3 ETSI Technical Committee for ITS (ETSI TC ITS)
45	6.7 Examples of commercial projects 6.7.1 Small EFC system: Herrentunnel Lübeck (Germany) 6.7.2 Nationwide EFC system: Germany
46	6.7.3 Interoperable EFC system: EasyGo 7 Outline of EFC requirements to an ITS Station 7.1 High level EFC requirements
48	Figure 13 — General requirements structure (Example) 7.2 Requirements for the EFC application(s) 7.2.1 Detection of Charge Objects (autonomous toll domains)
49	7.2.2 Provision of charge reports (autonomous toll domains)
50	7.2.3 Fee calculation (autonomous toll domains) 7.2.4 Generation of charge data (DSRC based toll domains)
51	7.2.5 Location support (autonomous toll domains) 7.2.6 Support of enforcement application 7.2.7 Operation of an enforcement application
52	7.2.8 Changing variable tariff parameters 7.2.9 Feedback to the road user
53	7.3 Resulting requirements for the ITS Station 7.3.1 Technical requirements 7.3.1.1 Access to and compliance with communication media 7.3.1.2 Support of EFC application data
54	7.3.1.3 Access to sensor data 7.3.1.4 Access to supporting EFC application data
55	7.3.1.5 Support of toll context data
56	7.3.1.6 Access to processing resources and memory 7.3.1.7 Access to HMI facilities
57	7.3.2 Security requirements 7.3.2.1 Security and protection of charge data 7.3.2.2 Privacy of data
58	7.3.2.3 Security mechanisms supported by the ITS Station
59	7.3.2.4 Secure delivery of charge data to the Toll Service Provider 7.3.2.5 Support of secure monitoring and trusted recorder
60	7.3.3 Operational requirements 7.3.3.1 Life cycle management for the EFC application
61	7.3.3.2 Management of EFC application data
62	7.3.3.3 Configuration of the EFC application 8 EFC services in the C-ITS environment 8.1 EFC services on ITS Stations
63	8.2 Involved C-ITS sub-roles in the life cycle of EFC services 8.2.1 Life cycle of EFC services
64	Figure 14 — Life cycle phases of EFC services (and examples of major tasks) 8.2.2 C-ITS sub-roles involved in different phases of the EFC service life cycle 8.2.2.1 General
65	8.2.2.2 Preparation phase Table 1 — C-ITS sub-roles involved in the preparation phase 8.2.2.3 Development phase
66	Table 2 — C-ITS sub-roles involved in the service development phase 8.2.2.4 Deployment phase
67	Table 3 — C-ITS sub-roles involved in the service deployment phase 8.2.2.5 Operation phase Table 4 — C-ITS sub-roles involved in the service deployment phase
68	8.2.2.6 End-of-life Table 5 — C-ITS sub-roles involved in the end-of-life activities 8.3 Combined models of EFC services in C-ITS context 8.3.1 C-ITS and EFC role model relations
69	Figure 15 — C-ITS and EFC role model relations
70	8.3.2 Technical EFC architecture in C-ITS context Figure 16 — Application provisioning with ITS Station Service Provider
71	Figure 17 — Example technical EFC architecture in C-ITS context
72	8.3.3 ITS Station Service Provider 8.3.4 Extended EFC role model in C-ITS environment Figure 18 — Extended EFC role model with three ITS-S service providers
73	Figure 19 — Extended EFC role model with single ITS Station service provider role 8.3.5 Business architecture
74	Figure 20 — Example conceptual business model for EFC in an C-ITS system 9 Considerations on particular implementation aspects 9.1 Introduction
75	9.2 Synergies
76	9.3 Particular and critical areas in relation to EFC in an ITS environment 9.3.1 Phase of migration from dedicated EFC devices to ITS-S based EFC
77	Figure 21 — Overview on migration phases from dedicated EFC in vehicle equipment to EFC on ITS-S
78	Table 6 — Scenarios in the EFC migration phase In Scenarios A and B do not provide any problem Only one EFC application (EFC OBU based or EFC application on ITS-S) is active at a time.
79	9.3.2 Resource management
82	9.3.3 Performance monitoring
83	9.4 Suitability for use and certification 9.4.1 Introduction
84	Figure 22 — Certification and suitability for use procedure 9.4.2 Conformity to specifications
85	9.4.3 Suitability for use tests 9.4.4 Certification
86	Figure 23 — Requirements as test cases for certification of ITS Station, EFC application and Service Provider 9.4.5 Registration and Certification Authority
87	9.4.6 Quality system approval und surveillance 9.5 Governance and responsibility 9.5.1 Introduction
88	9.5.2 Application configuration of the ITS Station
89	Figure 24 — Configurations of an ITS Station 9.5.3 Technical implementation of the ITS Station 9.5.3.1 General 9.5.3.2 Single OBE host / router
90	9.5.3.3 Multi OBE host / router 9.5.3.4 Other OBE host and router configurations 9.5.3.5 Virtualisation of the host environment 9.5.4 Update and installation of applications 9.5.4.1 General
91	9.5.4.2 EFC thick client versus thin-client concepts 10 Guidelines for further work 10.1 Role of EFC to boost the deployment of C-ITS
92	10.2 Actions to reduce barriers for the deployment of EFC applications — Create harmonized certification and test rules 10.2.1 Introduction 10.2.2 Issuing test rules
93	10.2.3 Guidelines on certification and tests 10.3 Recommendations for further standardization activities 10.3.1 Recommendations with regard to the area of EFC 10.3.1.1 Role model
94	10.3.1.2 Application data definitions 10.3.1.3 Compliance checking 10.3.1.4 EFC security 10.3.1.5 EFC test standards
95	10.3.2 Recommendations with regard to the area of (C-)ITS Figure 25 — Standardising of generic functionality and mapping to APIs
96	10.4 Best practice
97	Annex A (informative) Security Considerations A.1 Introduction A.1.1 Security areas and targets A.1.2 System and application availability and reliability A.1.3 Data security
98	A.1.4 User privacy protection A.2 Security scope of this annex A.3 General EFC security considerations A.3.1 Security analysis Figure A.1 — Threat analysis
99	Figure A.2 — Security system lifecycle
100	A.3.2 Security system A.3.2.1 General A.3.2.2 Technical security architecture A.3.2.3 Organisational security architecture
101	A.4 System and application availability and reliability
102	A.5 Security of an ITS Station A.5.1 General A.5.2 Closed ITS Station application platform
103	A.5.3 Open ITS Station application platform A.6 Summary
104	Bibliography

Published By	Publication Date	Number of Pages
BSI	2014	108


PDF Format	Searchable	Printable	Preview Now

Status	Definitive
Pages	108
Publication Date	2014-07-31
ISBN	978 0 580 84414 0
Standard Number	PD CEN/TR 16690:2014
Title	Electronic fee collection. Guidelines for EFC applications based on in-vehicle ITS stations
Identical National Standard Of	CEN/TR 16690:2014
Descriptors	Information exchange, Interoperability, Road vehicles, Data transfer, Interfaces (data processing), Data processing, Traffic control, Traffic, Toll systems, Data transmission, Road transport, Radiocommunication, Application layer (OSI), Electronic equipment and components, Data security
Publisher	BSI
Committee	EPL/278
ICS Codes	35.240.60 - IT applications in transport

BSI PD CEN/TR 16690:2014

PDF Catalog

Related products