1、BSI Standards PublicationElectronic fee collection Guidelines for EFC applications based on in-vehicle ITS stationsPD CEN/TR 16690:2014National forewordThis Published Document is the UK implementation of CEN/TR 16690:2014.The UK participation in its preparation was entrusted to TechnicalCommittee EP
2、L/278, Intelligent transport systems.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to include all the necessary provisions ofa contract. Users are responsible for its correct application. The British Standards Insti
3、tution 2014.Published by BSI Standards Limited 2014ISBN 978 0 580 84414 0ICS 35.240.60Compliance with a British Standard cannot confer immunity fromlegal obligations.This Published Document was published under the authority of theStandards Policy and Strategy Committee on 31 July 2014.Amendments/cor
4、rigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD CEN/TR 16690:2014TECHNICAL REPORT RAPPORT TECHNIQUE TECHNISCHER BERICHT CEN/TR 16690 July 2014 ICS 35.240.60 English Version Electronic fee collection - Guidelines for EFC applications based on in-vehicle ITS stations Perception
5、de tlpage - Lignes directrices pour les applications de tlpage installes dans les stations de systmes de transport intelligents (ITS) embarques dans les vhicules Elektronische Gebhrenerhebung - Richtlinien fr Anwendungen der Elektronischen Gebhrenerhebung basierend auf fahrzeuginternen IVS Gerten Th
6、is Technical Report was approved by CEN on 10 May 2014. It has been drawn up by the Technical Committee CEN/TC 278. CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France,
7、Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITE
8、E FR NORMUNG CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2014 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN/TR 16690:2014 EPD CEN/TR 16690:2014CEN/TR 16690:2014 (E) 2 Contents Page Foreword 5 Introduction .6
9、 1 Scope 8 2 Normative references 8 3 Terms and definitions .9 4 Symbols and abbreviations . 12 5 Context of C-ITS 13 5.1 Definition of C-ITS. 13 5.1.1 Introduction . 13 5.1.2 The European Commission basic definition 14 5.1.3 The vehicle active safety viewpoint 14 5.1.4 The CEN/ETSI/ISO definition .
10、 14 5.2 C-ITS role model and business architecture . 15 5.2.1 Role model . 15 5.2.2 Business architecture 17 5.3 Technical architecture 19 5.3.1 ITS Station architecture . 19 5.3.2 ITS communication access technologies 20 5.3.3 Application provisioning and life cycle management. 22 5.3.4 Security 23
11、 5.4 Legal aspects and background . 23 5.4.1 European action plan and directive for ITS . 23 5.4.2 User privacy and data protection 24 5.4.3 Liabilities regarding application performance / suitability for use 24 5.5 Overview of standardization activities . 24 5.5.1 Introduction . 24 5.5.2 Basic set
12、of ITS applications . 25 5.5.3 CEN/TC 278/WG 16 on cooperative systems . 26 5.5.4 ISO/TC 204/WG 18 on cooperative systems 26 5.5.5 ISO/TC 204/WG 16 on wide area communications/protocols and interfaces . 27 5.5.6 ETSI Technical Committee on ITS (ETSI TC ITS) . 27 5.6 Overview of R identify major EFC
13、requirements that will have an impact to the ITS Station; provide a view as to how EFC roles and functionalities (according to ISO 17573) shall be enabled and supported in the cooperative ITS context (in different phases of the entire life cycle of an EFC service); identify a base technical architec
14、ture that enables EFC services in an ITS context; analyse stakeholders in a business architecture and provide an example of a business architecture for EFC services in an ITS environment; and emphasize on particular key areas like conformance and certification, potential synergies in the context of
15、the ITS Station, areas of major concern, governance, critical elements. This approach could be chosen as the EFC environment is seen very mature in terms of architectural, technical and operational requirements and processes. EFC as a service is already in use in various PD CEN/TR 16690:2014CEN/TR 1
16、6690:2014 (E) 7 commercial projects in many countries throughout the world. Operational experiences have already been taken into account in refining the landscape of existing specifications in EFC. This can be seen as an extraordinary condition compared to other (future) ITS services for which such
17、mature environmental and context is not yet available ETSI TC ITS has defined a Basic Set of Applications in ETSI/TR 102 638 which is expected to be deployed relatively swiftly after completion of standardization of C-ITS. EFC is directly addressed in this Basic Set of Applications and considered as
18、 a primary application. Standardization of the EFC application requirements is, however, within the scope of CEN/TC 278/WG 1, which is in charge of defining the requirements for the EFC use cases in accordance with the set of standards developed by this Working Group. PD CEN/TR 16690:2014CEN/TR 1669
19、0:2014 (E) 8 1 Scope 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 speci
20、fied 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 applica
21、tions; 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
22、 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
23、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 requir
24、es 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 functional
25、ities, 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
26、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 wh
27、ich 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. 2 Normative references The following documents, in whole or in part, are normatively ref
28、erenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN 15509, Road transport and traffic telematics - Electronic fee collect
29、ion - Interoperability application profile for DSRC PD CEN/TR 16690:2014CEN/TR 16690:2014 (E) 9 CEN ISO/TS 12813, Electronic fee collection - Compliance check communication for autonomous systems (ISO/TS 12813) EN ISO 12855:2012, Electronic fee collection - Information exchange between service provi
30、sion and toll charging (ISO 12855:2012) CEN ISO/TS 13141, Electronic fee collection - Localisation augmentation communication for autonomous systems (ISO/TS 13141) EN ISO 14906, Electronic fee collection - Application interface definition for dedicated short-range communication (ISO 14906) CEN ISO/T
31、S 17575-1:2010, Electronic fee collection - Application interface definition for autonomous systems - Part 1: Charging (ISO/TS 17575-1:2010) CEN ISO/TS 17575-2, Electronic fee collection - Application interface definition for autonomous systems - Part 2: Communication and connection to the lower lay
32、ers (ISO/TS 17575-2) CEN ISO/TS 17575-3:2011, Electronic fee collection - Application interface definition for autonomous systems - Part 3: Context data (ISO/TS 17575-3:2011) CEN ISO/TS 17575-4:2011, Electronic fee collection - Application interface definition for autonomous systems - Part 4: Roamin
33、g (ISO/TS 17575-4:2011) ISO 17573:2010, Electronic fee collection Systems architecture for vehicle-related tolling 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 back end computing and communication facilities of an actor (e.g. a Toll Charge
34、r or a Toll Service Provider) exchanging data with a Front or Back End 3.2 back office generic name for the centrally located computing and communication facilities (of a role involved in EFC) 3.3 charge report information containing road usage and related information originated at the Front End 3.4
35、 cooperative ITS subset of the overall ITS that communicates and shares information between ITS Stations to give advice or facilitate actions with the objective of improving safety, sustainability, efficiency and comfort beyond the scope of stand-alone systems SOURCE: ISO/DTR 17465 3.5 electronic fe
36、e collection fee collection by electronic means PD CEN/TR 16690:2014CEN/TR 16690:2014 (E) 10 3.6 front end part(s) of the toll system where road usage data for an individual road user are collected, processed and delivered to the Back End Note 1 to entry: The Front End comprises the on-board equipme
37、nt and an optional proxy. SOURCE: CEN ISO/TS 17575-1:2010, 3.13 3.7 interoperability management role that manages the toll charging environment, i.e. defining and maintaining a set of rules that, taken together, defines the policy of a given toll regime or of the overall toll charging environment 3.
38、8 ITS application association of two or more complementary ITS-S applications SOURCE: ETSI EN 302 665 V1.1.1 (2010-09) 3.9 ITS service service provided by an ITS application to the user of ITS SOURCE: ETSI EN 302 665 V1.1.1 (2010-09) 3.10 ITS station entity in a communication network that executes I
39、TS-S applications within a bounded, secured, managed domain comprised of an ITS-S facilities layer, ITS-S networking and shares information; between ITS Stations1)(ITS-S) to: give advice; or facilitate actions; with the objective of improving: safety, sustainability, efficiency and comfort; beyond t
40、he scope of stand-alone systems. This definition seems to attract the most support at the moment, and it is important to see that it also defines the boundary towards existing, non-cooperative ITS. ISO/DTR 17465 (all parts) states the following features of C-ITS: the sharing of information between a
41、ny ITS-SU; the sharing of information between different applications; 1) ITS Station defined in ETSI EN 302 665/ISO 21217, e.g. units installed in vehicles, at the road side, in traffic control/management centres, in service centres, or hand-held units. PD CEN/TR 16690:2014CEN/TR 16690:2014 (E) 15 t
42、he sharing of resources (communication, positioning, security) in an ITS-SU; the authorized use of information for purposes other than the original intent; the support of multiple ITS applications on an ITS-SU. Note that an ITS-SU is not restricted to execute cooperative applications. It might also
43、be used as a platform to implement non-cooperative applications. Therefore an ITS-SU can also communicate with sub-systems in the non-cooperative ITS domain, provided that it can trust these sub-systems to provide credible and accurate data within the appropriate security and privacy constraints. 5.
44、2 C-ITS role model and business architecture 5.2.1 Role model 5.2.1.1 Introduction The roles and responsibilities in the context of C-ITS are defined in prCEN ISO/TS 17427. In addition the EU7FP project CVIS has defined a role model with associated responsibilities. In both of these definitions the
45、role models also define responsibilities and liabilities in regard to privacy and data protection issues. 5.2.1.2 Role model introduced by ISO In prCEN ISO/TS 17427 the definition of roles and responsibilities are based on an organizational or enterprise viewpoint as defined in ISO/IEC 10746 (all pa
46、rts), Information technology Open distributed processing. The roles are separated into external and internal roles, where the internal roles only exists for the purpose of C-ITS, while the external roles are also involved in other activities (non-C-ITS services and applications). The four major role
47、s from prCEN ISO/TS 17427 are shown in Figure 1. Figure 1 Organizational architecture with the four major roles The roles System Operation, Management and Policy Framework are further subdivided into sub-roles. The role System Operation is responsible for the proper execution of the applications tha
48、t provide the end-to-end service(s). The role System Operation is composed of the sub-roles Content Provision, Service Provision and Presentation Provision. Their general responsibilities are reflected in the process chain shown in Figure 2. PD CEN/TR 16690:2014CEN/TR 16690:2014 (E) 16 Figure 2 Sub-
49、roles of System Operation process chain The role System Management is responsible for all management activities in the system. Sub-roles of System Management are: Service Catalogue Manager, Communication Manager, Service Owner, C-ITS Architect, Project Manager, Test Manager, Service Level Manager, Risk Manager, Capacity Manager, Availability Manager, Information Security Manager, Access Manager, Technical Analyst, Change Manager, Configuration Manager, Homologation Manager, System Monitoring, a
