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.<\/p>\n
The scope of this Technical Report includes:<\/p>\n
description of the context of Cooperative ITS and the ITS Stations;<\/p>\n<\/li>\n
providing details of the context of EFC applications;<\/p>\n<\/li>\n
outlining the basic architectural concepts and role model of both EFC and Cooperative ITS;<\/p>\n<\/li>\n
identification of core requirement areas for operation of an EFC application on an ITS Station;<\/p>\n<\/li>\n
specification of a set of recommendations for functional, operational and security requirements to the ITS Station supporting the EFC application(s);<\/p>\n<\/li>\n
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;<\/p>\n<\/li>\n
provision of considerations in particular areas of EFC like certification and governances;<\/p>\n<\/li>\n
guideless and recommendations for further standardization work in this area;<\/p>\n<\/li>\n
emphasizing on security related elements of EFC that need to be considered in a C-ITS environment.<\/p>\n<\/li>\n<\/ul>\n
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.<\/p>\n
Outside the scope of this Technical Report is:<\/p>\n
detailed technical specifications for EFC services and applications on C-ITS systems;<\/p>\n<\/li>\n
implementation specific elements.<\/p>\n<\/li>\n<\/ul>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 3<\/td>\n | CEN\/TC 278 <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 4 Symbols and abbreviations <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 5 Context of C-ITS 5.1 Definition of C-ITS 5.1.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 5.1.2 The European Commission basic definition 5.1.3 The vehicle active safety viewpoint 5.1.4 The CEN\/ETSI\/ISO definition <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 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 \u2014 Organizational architecture with the four major roles <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | Figure 2 \u2014 Sub-roles of System Operation \u2013 process chain 5.2.1.3 Role model developed in the CVIS project <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | Figure 3 \u2014 CVIS roles [source and courtesy of CVIS] 5.2.2 Business architecture <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | Figure 4 \u2014 Conceptual business model template [source and courtesy of CVIS] <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | Figure 5 \u2014 The service \u201cDangerous goods \/ route guidance\u201d modelled with conceptual business modeller [source and courtesy of CVIS] 5.3 Technical architecture 5.3.1 ITS Station architecture <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | Figure 6 \u2014 Simplified ITS station architecture [source: ISO 21217:2010] 5.3.2 ITS communication access technologies <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 5.3.3 Application provisioning and life cycle management Figure 7 \u2014 Service deployment and provisioning (adapted from CVIS) <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 5.3.4 Security 5.4 Legal aspects and background 5.4.1 European action plan and directive for ITS <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 5.5.2 Basic set of ITS applications <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 5.5.3 CEN\/TC 278\/WG 16 on cooperative systems 5.5.4 ISO\/TC 204\/WG 18 on cooperative systems <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | Figure 8 \u2014 CVIS high-level architecture [source and courtesy of CVIS] 5.6.2 SAFESPOT project on road safety related applications <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 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) <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 6.2 EFC role model and business architecture 6.2.1 Role model Figure 9 \u2014 The EFC role model [source: ISO 17573:2010] <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | 6.2.2 Business architecture <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 6.3 Technical architecture 6.3.1 Overview Figure 10 \u2014 Data flow view of the technical architecture <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 6.3.2 Communication architecture <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | Figure 11 \u2014 Component and interface view of the technical architecture 6.3.3 Autonomous OBE \/ Front End implementation <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | Figure 12 \u2014 Examples of data processing steps in thin and thick client approaches 6.3.4 EFC security <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | 6.4 Additional major aspects 6.4.1 Interoperability 6.4.2 Value added services based on EFC OBE <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | 6.4.3 EFC outside Europe <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | 6.5 Legal aspects and background 6.5.1 Toll domain specific 6.5.2 European Electronic Toll Service (EETS) <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | 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) <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | 6.7 Examples of commercial projects 6.7.1 Small EFC system: Herrentunnel L\u00fcbeck (Germany) 6.7.2 Nationwide EFC system: Germany <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | 6.7.3 Interoperable EFC system: EasyGo 7 Outline of EFC requirements to an ITS Station 7.1 High level EFC requirements <\/td>\n<\/tr>\n | ||||||
| 48<\/td>\n | Figure 13 \u2014 General requirements structure (Example) 7.2 Requirements for the EFC application(s) 7.2.1 Detection of Charge Objects (autonomous toll domains) <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | 7.2.2 Provision of charge reports (autonomous toll domains) <\/td>\n<\/tr>\n | ||||||
| 50<\/td>\n | 7.2.3 Fee calculation (autonomous toll domains) 7.2.4 Generation of charge data (DSRC based toll domains) <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | 7.2.5 Location support (autonomous toll domains) 7.2.6 Support of enforcement application 7.2.7 Operation of an enforcement application <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | 7.2.8 Changing variable tariff parameters 7.2.9 Feedback to the road user <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 54<\/td>\n | 7.3.1.3 Access to sensor data 7.3.1.4 Access to supporting EFC application data <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | 7.3.1.5 Support of toll context data <\/td>\n<\/tr>\n | ||||||
| 56<\/td>\n | 7.3.1.6 Access to processing resources and memory 7.3.1.7 Access to HMI facilities <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | 7.3.2 Security requirements 7.3.2.1 Security and protection of charge data 7.3.2.2 Privacy of data <\/td>\n<\/tr>\n | ||||||
| 58<\/td>\n | 7.3.2.3 Security mechanisms supported by the ITS Station <\/td>\n<\/tr>\n | ||||||
| 59<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 60<\/td>\n | 7.3.3 Operational requirements 7.3.3.1 Life cycle management for the EFC application <\/td>\n<\/tr>\n | ||||||
| 61<\/td>\n | 7.3.3.2 Management of EFC application data <\/td>\n<\/tr>\n | ||||||
| 62<\/td>\n | 7.3.3.3 Configuration of the EFC application 8 EFC services in the C-ITS environment 8.1 EFC services on ITS Stations <\/td>\n<\/tr>\n | ||||||
| 63<\/td>\n | 8.2 Involved C-ITS sub-roles in the life cycle of EFC services 8.2.1 Life cycle of EFC services <\/td>\n<\/tr>\n | ||||||
| 64<\/td>\n | Figure 14 \u2014 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 <\/td>\n<\/tr>\n | ||||||
| 65<\/td>\n | 8.2.2.2 Preparation phase Table 1 \u2014 C-ITS sub-roles involved in the preparation phase 8.2.2.3 Development phase <\/td>\n<\/tr>\n | ||||||
| 66<\/td>\n | Table 2 \u2014 C-ITS sub-roles involved in the service development phase 8.2.2.4 Deployment phase <\/td>\n<\/tr>\n | ||||||
| 67<\/td>\n | Table 3 \u2014 C-ITS sub-roles involved in the service deployment phase 8.2.2.5 Operation phase Table 4 \u2014 C-ITS sub-roles involved in the service deployment phase <\/td>\n<\/tr>\n | ||||||
| 68<\/td>\n | 8.2.2.6 End-of-life Table 5 \u2014 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 <\/td>\n<\/tr>\n | ||||||
| 69<\/td>\n | Figure 15 \u2014 C-ITS and EFC role model relations <\/td>\n<\/tr>\n | ||||||
| 70<\/td>\n | 8.3.2 Technical EFC architecture in C-ITS context Figure 16 \u2014 Application provisioning with ITS Station Service Provider <\/td>\n<\/tr>\n | ||||||
| 71<\/td>\n | Figure 17 \u2014 Example technical EFC architecture in C-ITS context <\/td>\n<\/tr>\n | ||||||
| 72<\/td>\n | 8.3.3 ITS Station Service Provider 8.3.4 Extended EFC role model in C-ITS environment Figure 18 \u2014 Extended EFC role model with three ITS-S service providers <\/td>\n<\/tr>\n | ||||||
| 73<\/td>\n | Figure 19 \u2014 Extended EFC role model with single ITS Station service provider role 8.3.5 Business architecture <\/td>\n<\/tr>\n | ||||||
| 74<\/td>\n | Figure 20 \u2014 Example conceptual business model for EFC in an C-ITS system 9 Considerations on particular implementation aspects 9.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 75<\/td>\n | 9.2 Synergies <\/td>\n<\/tr>\n | ||||||
| 76<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 77<\/td>\n | Figure 21 \u2014 Overview on migration phases from dedicated EFC in vehicle equipment to EFC on ITS-S <\/td>\n<\/tr>\n | ||||||
| 78<\/td>\n | Table 6 \u2014 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. <\/td>\n<\/tr>\n | ||||||
| 79<\/td>\n | 9.3.2 Resource management <\/td>\n<\/tr>\n | ||||||
| 82<\/td>\n | 9.3.3 Performance monitoring <\/td>\n<\/tr>\n | ||||||
| 83<\/td>\n | 9.4 Suitability for use and certification 9.4.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 84<\/td>\n | Figure 22 \u2014 Certification and suitability for use procedure 9.4.2 Conformity to specifications <\/td>\n<\/tr>\n | ||||||
| 85<\/td>\n | 9.4.3 Suitability for use tests 9.4.4 Certification <\/td>\n<\/tr>\n | ||||||
| 86<\/td>\n | Figure 23 \u2014 Requirements as test cases for certification of ITS Station, EFC application and Service Provider 9.4.5 Registration and Certification Authority <\/td>\n<\/tr>\n | ||||||
| 87<\/td>\n | 9.4.6 Quality system approval und surveillance 9.5 Governance and responsibility 9.5.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 88<\/td>\n | 9.5.2 Application configuration of the ITS Station <\/td>\n<\/tr>\n | ||||||
| 89<\/td>\n | Figure 24 \u2014 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 <\/td>\n<\/tr>\n | ||||||
| 90<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 91<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 92<\/td>\n | 10.2 Actions to reduce barriers for the deployment of EFC applications \u2014 Create harmonized certification and test rules 10.2.1 Introduction 10.2.2 Issuing test rules <\/td>\n<\/tr>\n | ||||||
| 93<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 94<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 95<\/td>\n | 10.3.2 Recommendations with regard to the area of (C-)ITS Figure 25 \u2014 Standardising of generic functionality and mapping to APIs <\/td>\n<\/tr>\n | ||||||
| 96<\/td>\n | 10.4 Best practice <\/td>\n<\/tr>\n | ||||||
| 97<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 98<\/td>\n | 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 \u2014 Threat analysis <\/td>\n<\/tr>\n | ||||||
| 99<\/td>\n | Figure A.2 \u2014 Security system lifecycle <\/td>\n<\/tr>\n | ||||||
| 100<\/td>\n | A.3.2 Security system A.3.2.1 General A.3.2.2 Technical security architecture A.3.2.3 Organisational security architecture <\/td>\n<\/tr>\n | ||||||
| 101<\/td>\n | A.4 System and application availability and reliability <\/td>\n<\/tr>\n | ||||||
| 102<\/td>\n | A.5 Security of an ITS Station A.5.1 General A.5.2 Closed ITS Station application platform <\/td>\n<\/tr>\n | ||||||
| 103<\/td>\n | A.5.3 Open ITS Station application platform A.6 Summary <\/td>\n<\/tr>\n | ||||||
| 104<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Electronic fee collection. Guidelines for EFC applications based on in-vehicle ITS stations<\/b><\/p>\n |