1、BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06Electronic fee collection - Personalization of on-board equipment (OBE) - Part 1: Framework (ISO/TS 21719-1:2018)Part 1: FrameworkPD CEN ISO/TS 217191:2018National forewordThis Published Document is the UK implementatio
2、n of CEN ISO/TS 217191:2018. It is identical to ISO/TS 217191:2018.The UK participation in its preparation was entrusted to Technical Committee EPL/278, Intelligent transport systems.A list of organizations represented on this committee can be obtained on request to its secretary.This publication do
3、es not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2018 Published by BSI Standards Limited 2018ISBN 978 0 580 98137 1ICS 03.220.20; 35.240.60Compliance with a British Standard cannot confer immuni
4、ty from legal obligations. This Published Document was published under the authority of the Standards Policy and Strategy Committee on 31 March 2018.Amendments/corrigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD CEN ISO/TS 217191:2018TECHNICAL SPECIFICATIONSPCIFICATION TECHNIQU
5、ETECHNISCHE SPEZIFIKATIONCEN ISO/TS 21719-1February 2018ICS 03.220.20; 35.240.60EUROPEAN COMMITTEE FOR STANDARDIZATIONCOMIT EUROPEN DE NORMALISATIONEUROPISCHES KOMITEE FR NORMUNGCEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2018 CEN Ref. No. CEN ISO/TS 217191:2018: EAll rights of
6、exploitation in any form and by any means reserved worldwide for CEN national MembersElectronic fee collection Personalization of onboard equipment (OBE) Part 1: Framework (ISO/TS 217191:2018)Perception de tlpage Personnalisation des quipements embarqus Partie 1: Cadre (ISO/TS 217191:2018)Elektronis
7、che Gebhrenerhebung Personalisierung von Onboard Einrichtungen Teil 1: Grundstruktur(ISO/TS 217191:2018)This Technical Specification (CEN/TS) was approved by CEN on 2 February 2018 for provisional application.The period of validity of this CEN/TS is limited initially to three years. After two years
8、the members of CEN will be requested to submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard.CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available promptly at nationa
9、l level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached.CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croati
10、a, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey
11、 and United Kingdom.English VersionCEN ISO/TS 21719-1:2018 (E)European forewordThis document (CEN ISO/TS 217191:2018) has been prepared by Technical Committee ISO/TC 204 “Intelligent transport systems“ in collaboration with Technical Committee CEN/TC 278 “Intelligent transport systems”, the secretar
12、iat of which is held by NEN.Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN shall not be held responsible for identifying any or all such patent rights.According to the CEN/CENELEC Internal Regulations, the national standards
13、organisations of the following countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Lu
14、xembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom.Endorsement noticeThe text of ISO/TS 217191:2018 has been approved by CEN as CEN ISO/TS 217191:2018 without any modification.2PD CEN ISO/TS 217191:20
15、18ISO/TS 21719-1:2018Foreword ivIntroduction v1 Scope . 12 Normative references 23 Terms and definitions . 24 Abbreviated terms 35 Personalization overview 35.1 Process . 35.2 Personalization assets 45.3 System architecture 46 EFC personalization functions 46.1 Overview 46.2 Write function 46.2.1 Ba
16、sic functionality 46.2.2 Security functions . 56.2.3 Access protection 56.2.4 Application data encryption 56.2.5 Write_Request authenticator 66.2.6 Write_Response authenticator 6Annex A (informative) Personalization interfaces . 8Bibliography 9 ISO 2018 All rights reserved iiiContents PagePD CEN ISO
17、/TS 217191:2018ISO/TS 21719-1:2018ForewordISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body inte
18、rested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and nongovernmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical
19、 Commission (IEC) on all matters of electrotechnical standardization.The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of ISO docume
20、nts should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible
21、 for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents).Any trade name used in this document is information given for th
22、e convenience of users and does not constitute an endorsement.For an explanation on the voluntary nature of standards, the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISOs adherence to the World Trade Organization (WTO) principles in t
23、he Technical Barriers to Trade (TBT) see the following URL: www.iso.org/iso/foreword.html.This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.A list of all parts in the ISO 21719 series can be found on the ISO website.iv ISO 2018 All rights reservedPD CEN ISO/
24、TS 217191:2018ISO/TS 21719-1:2018IntroductionOnboard equipment (OBE) is an invehicle device that is able to contain one or more application instances in order to support different intelligent transportation system (ITS) implementations such as electronic fee collection (EFC). Examples of EFC applica
25、tions are road toll collection/road charging, localization augmentation (LAC) or compliance checking (CCC).To assign the EFC application in the OBE to a certain user and/or vehicle, personalization should be performed. This means that unique user and vehicle related data, needs to be transferred to
26、the OBE.The CEN/TR 16152 already assessed many aspects of the personalization process and it also defined the overall personalization assets, i.e. application data, application keys and vehicle data.Different communication media may be used for transferring the personalization assets to the OBE; but
27、 for all media, common procedures may be applied such as an overall message exchange framework and necessary security functionality in order to ensure data protection and integrity.By standardizing the personalization procedure, compatibility of personalization equipment is supported, and the entity
28、 responsible for the personalization, e.g. a toll service provider, will be able to outsource parts of, or a complete, personalization to a third party, another service provider or a personalization agent.This document defines common functionality for personalization that is independent of the commu
29、nication media and personalization equipment (PE) used, while the subsequent parts define in detail how the functions are realized on different defined communication media and interfaces. ISO 2018 All rights reserved vPD CEN ISO/TS 217191:2018This page deliberately left blankElectronic fee collectio
30、n - Personalization of on-board equipment (OBE) - Part 1: Framework (ISO/TS 21719-1:2018) Part 1: Framework1 ScopeThis document describes: an overall description of the EFC personalization process; a description of EFC functionality that can be used for personalization.The personalization process ta
31、kes place within the domain of the entity that is responsible for the application in the OBE.The scope of the EFC functionality is limited to the interface between the personalization equipment (PE) and OBE as shown in Figure 1. It is out of the scope of this document to define whether the personali
32、zation functionality resides completely in the PE or whether this functionality instead resides in a central system and where the PE is more or less “transparent”.Domain of the entity responsible for personalizationCentralSystem PersonalizationEquipment (PE)On-Board Equipment (OBE)Scope of this docu
33、mentDSRCFigure 1 Scope of this document (box delimited by the dotted line)It is outside the scope of this document to define the following: exact application command or message structures for the EFC personalization functionality (these are dependent on the communication media and described in subse
34、quent parts of the ISO/TS 21719 series); conformance procedures and test specification (this may be provided in a by separate set of standards that are referred to in the subsequent parts of the ISO/TS 21719 series); settingup of operating organizations (e.g. Toll Service Provider, personalization a
35、gent, trusted third party, etc.); legal issues.NOTE Some of the above issues are subject to separate standards prepared by CEN/TC 278, ISO/TC 204 or ETSI ERM.TECHNICAL SPECIFICATION ISO/TS 21719-1:2018 ISO 2018 All rights reserved 1PD CEN ISO/TS 217191:2018ISO/TS 21719-1:20182 Normative referencesTh
36、ere are no normative references in this document.3 Terms and definitionsFor the purposes of this document, the following terms and definitions applyISO and IEC maintain terminological databases for use in standardization at the following addresses: IEC Electropedia: available at www.electropedia.org
37、 ISO Online browsing platform: available at www.iso.org/obp3.1attributeaddressable package of data consisting of a single data element (3.3) or structured sequences of data elementsSOURCE: ISO 175751:2016, 3.23.2electronic fee collectionEFCfee collection by electronic meansSOURCE: ISO 12855:2015, 3.
38、63.3elementDSRC directory containing application information in the form of attributes (3.1)3.4OBE personalizationprocess of transferring personalization assets (3.6) to the on-board equipment (OBE) (3.5)3.5on-board equipmentOBErequired equipment onboard a vehicle for performing required electronic
39、fee collection (EFC) (3.2) functions and communication servicesSOURCE: ISO 12855:2015, 3.93.6personalization assetsspecific data stored in the OBE related to the user and the vehicle3.7personalization equipmentequipment for transferring personalization assets (3.6) to the OBE (3.5)3.8toll domainarea
40、 or part of a road network where a certain toll regime is appliedSOURCE: ISO 17573:2010, 3.18, modified “certain” has been added.2 ISO 2018 All rights reservedPD CEN ISO/TS 217191:2018ISO/TS 21719-1:20184 Abbreviated termsCCC Compliance check communication (see ISO 12813)EFC Electronic Fee Collectio
41、n (see ISO 17573)IAP Interoperable Application Profile (see EN 15509)LAC Localization augmentation communication (see ISO 13141)OBE Onboard EquipmentPE Personalization Equipment5 Personalization overview5.1 ProcessTo prepare an OBE for use, it has to be prepared with the EFC applications and data re
42、quired for the toll domain(s) where the OBE shall be used.Before personalization, one or more initial nonpersonalized data structures for the EFC applications should be present in the OBE and it is out of scope of this document how these structures are entered into the OBE. The personalization proce
43、ss deals with how this existing EFC application structures are populated with personalization data (personalization assets), such as payment related data, vehicle data or security keys. It is also assumed that necessary security functionality and initial keys to perform the personalization already a
44、re present in the OBE at time of personalization.According to ISO 14906, application data shall be stored in attributes that are addressed in Elements corresponding to specific EFC applications as shown in Figure 2.System dataPersonalization keys (Initial values)EFC application (Element)Initial or e
45、mptyapplication data structure(attributes)System dataPersonalization keys (personalized values )EFC application (Element)Personalized data in attributessuch as-payment data-vehicle data -application keysOBE before personalizationOBE after personalizationFigure 2 Scope of personalizationThe entity th
46、at is responsible for the EFC application defines the exact data content in the application and also the access rights to this data.When using the interoperable applications profile (IAP) for charging, compliance checking communication (CCC), or local augmentation communication (LAC), data sets and
47、access conditions are already defined in the corresponding standards. ISO 2018 All rights reserved 3PD CEN ISO/TS 217191:2018ISO/TS 21719-1:20185.2 Personalization assetsPersonalization assets are, as in CEN/TR 16152, application keys, application data and vehicle data.The application keys consists
48、of access keys that are used to grant access to application data, and authentication keys which are used to secure the authenticity of the OBE and the data integrity of the application data assets at time of use in the toll domain(s).The application data consist of data that is required to support o
49、ne or several a services. Application data is defined, e.g. in ISO 14906, EN 15509, ISO 12813 or ISO 13141.Vehicle data defines the characteristics of the vehicle in the case that the application in the OBE is bound to a specific vehicle.5.3 System architectureThe overall system architecture required to perform personalization according to the described process is shown in Figure 3.EFC Personalization applicationCommunication media(stack)EFC Personalization dataSecurity functionsand Key storageE
