1、BSI Standards PublicationBS EN ISO 14906:2011Electronic fee collection Application interface definition for dedicated short-range communication (ISO 14906:2011)BS EN ISO 14906:2011Incorporating corrigendum April 2013BS EN ISO 14906:2011+A1:2015BS EN ISO 14906:2011+A1:2015 BRITISH STANDARDNational fo
2、rewordThis British Standard is the UK implementation of EN ISO 14906:2011+A1:2015. It is identical to ISO 14906:2011, incorporating amendment 1 July 2015 and corrigendum April 2013. It supersedes BS EN ISO 14906:2011, which is withdrawn.The start and finish of text introduced or altered by amendment
3、 is indicated in the text by tags. Tags indicating changes to ISO text carry the number of the ISO amendment. For example, text altered by ISO amendment 1 is indicated by .The start and finish of text introduced or altered by corrigendum is indicated in the text by tags. Text altered by ISO corrigen
4、dum April 2013 is indicated in the text by .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 does not purport to inclu
5、de all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2015. Published by BSI Standards Limited 2015ISBN 978 0 580 84062 3ICS 03.220.20; 35.240.60Compliance with a British Standard cannot confer immunity from legal obligati
6、ons.This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 October 2011.Amendments/corrigenda issued since publicationDate Text affected30 June 2013 Implementation of ISO corrigendum April 201331 August 2015 Implementation of ISO amendment 1:2015
7、 with CEN endorsement A1:2015EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN ISO 14906 October 2011 ICS 03.220.20; 35.240.60 Supersedes EN ISO 14906:2004English Version Electronic fee collection - Application interface definition for dedicated short-range communication (ISO 14906:2011) Percepti
8、on du tlpage - Dfinition de linterface dapplication relative aux communications ddies courte porte (ISO 14906:2011) Elektronische Gebhrenerhebung - Anwendungsschnittstelle zur dezidierten Nahbereich-Kommunikation (ISO 14906:2011) This European Standard was approved by CEN on 20 August 2011. CEN memb
9、ers are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on applicati
10、on to the CEN-CENELEC Management Centre or to any CEN member. This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Managem
11、ent Centre has the same status as the official versions. CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlan
12、ds, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG Management Centre: Avenue Marnix 17, B-1000 Brussels 2011 CEN All rights of exploitation in a
13、ny form and by any means reserved worldwide for CEN national Members. Ref. No. EN ISO 14906:2011: EIncorporating corrigendum April 2013EN ISO 14906:2011+A1July 2015BS EN ISO 14906:2011EN ISO 14906:2011 (E) 3 Foreword This document (EN ISO 14906:2011) has been prepared by Technical Committee ISO/TC 2
14、04 “Intelligent transport systems“ in collaboration with Technical Committee CEN/TC 278 “Road transport and traffic telematics” the secretariat of which is held by NEN. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorseme
15、nt, at the latest by April 2012, and conflicting national standards shall be withdrawn at the latest by April 2012. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN and/or CENELEC shall not be held responsible for identifying a
16、ny or all such patent rights. This document supersedes EN ISO 14906:2004. According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Den
17、mark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. Endorsement notice The text of ISO 14906:2011 has been appro
18、ved by CEN as a EN ISO 14906:2011 without any modification. BS EN ISO 14906:2011+A1:2015EN ISO 14906:2011+A1:2015 (E)EN ISO 14906:2011/A1:2015 (E) 3 European foreword This document (EN ISO 14906:2011/A1:2015) has been prepared by Technical Committee ISO/TC 204 “Intelligent transport systems” in coll
19、aboration with Technical Committee CEN/TC 278 “Intelligent transport systems” the secretariat of which is held by NEN. This Amendment to the European Standard EN ISO 14906:2011 shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the late
20、st by January 2016, and conflicting national standards shall be withdrawn at the latest by January 2016. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN and/or CENELEC shall not be held responsible for identifying any or all s
21、uch patent rights. This document has been prepared under a mandate given to CEN by the European Commission and the European Free Trade Association. According to the CEN-CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European
22、Standard: Austria, Belgium, Bulgaria, Croatia, 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, Slovakia, Slovenia
23、, Spain, Sweden, Switzerland, Turkey and the United Kingdom. Endorsement notice The text of ISO 14906:2011/Amd 1:2015 has been approved by CEN as EN ISO 14906:2011/A1:2015 without any modification. Foreword to amendment A1BS EN ISO 14906:2011ISO 14906:2011(E) ISO 2011 All rights reserved iiiContents
24、 Page Foreword iv Introduction . v 1 Scope 1 2 Normative references 2 3 Terms and definitions . 2 4 Abbreviated terms . 5 5 EFC application interface architecture 7 5.1 Relation to the DSRC communication architecture . 7 5.2 Usage of DSRC application layer by the EFC application interface 9 5.3 Addr
25、essing of EFC attributes . 9 5.4 Addressing of components 11 6 EFC Transaction Model . 12 6.1 General . 12 6.2 Initialisation Phase 12 6.3 Transaction phase . 15 7 EFC Functions . 17 7.1 Overview and general concepts 17 7.2 EFC functions 21 8 EFC Attributes . 34 8.1 General . 34 8.2 Data group CONTR
26、ACT 36 8.3 Data group RECEIPT . 36 8.4 Data group VEHICLE . 36 8.5 Data group EQUIPMENT . 37 8.6 Data group DRIVER . 37 8.7 Data group PAYMENT . 37 Annex A (normative) EFC data type specifications 51 Annex B (informative) CARDME transaction 67 Annex C (informative) Examples of EFC transaction types
27、. 93 Annex D (informative) Functional requirements 103 Annex E (normative) Mapping table from LatinAlphabetNo2 Efc-ContextMark (incl. the ContextVersion), denoting the implementation version, provides a means to ensure co-existence of different implementation versions by means of a look-up table and
28、 associated appropriate transaction processing. This will enable the software of the RSE to determine the version of the OBE and his capabilty to accept the new features of this version of this International Standard. Annex A provides the normative ASN.1 specifications of the used data types (EFC ac
29、tion parameters and attributes). Annex B presents an informative example of a transaction based on the CARDME specification, including bit-level specification. BS EN ISO 14906:2011+A1:2015ISO 14906:2011+A1:2015 (E)BS EN ISO 14906:2011ISO 14906:2011(E) vi ISO 2011 All rights reservedAnnex C presents
30、informative examples of EFC transaction types, using the specified EFC functions and attributes. Annex D presents an informative listing of functional requirements, which can be satisfied by using the tools provided by this International Standard. Annex E presents an informative mapping table from L
31、atinAlphabetNo2 End Application (at RSE); Register Application RSU (at RSE); Deregister Application (at RSE and OBE); Notify Application OBU (at OBE); Register Application OBU (at OBE) are used to realise the EFC-specific initialisation mechanism (see Clause 6); The GET service is used to retrieve E
32、FC attributes (For attribute specifications see Clause 8); The SET service is used to set EFC attributes; The ACTION services are applied to realise additional EFC specific functionality needed to support EFC application processes, such as TRANSFER_CHANNEL, SET_MMI and ECHO (see 7.2). In the followi
33、ng, the EFC-specific usage of the DSRC Layer 7 services is specified in detail. NOTE The EVENT-REPORT-service can be implicitly used by EFC application processes. It is e.g. used indirectly as part of an already defined command to release an application process (see EN 12834/ISO 15628, Ready Applica
34、tion). However as the EVENT-REPORT-service is not explicitly used by EFC application processes, this service is not further referred to in this International Standard. 5.3 Addressing of EFC attributes 5.3.1 Basic mechanism EFC Attributes are used to transfer the EFC application-specific information.
35、 EFC Attributes are composed of one or more data elements of specified ASN.1 types. Each data element is associated with, within the context of this International Standard, an unambiguous name. To each EFC Attribute, an AttributeID is associated. The AttributeId enables to unambiguously identify and
36、 address an EFC Attribute. BS EN ISO 14906:2011+A1:2015ISO 14906:2011+A1:2015 (E) ISO 2011 All rights reservedBS EN ISO 14906:2011ISO 14906:2011(E) 10 ISO 2011 All rights reservedEXAMPLE Figure 3 illustrates the basic addressing mechanism. AttrlD = 0 AttrlD = 4Contract AuthenticatorAttrlD = nAttribu
37、te IDAttributeASN.1-Type.AttrlD = 3AttrlD = 2Contract VehicleContract ValidityContractAuthenticator :=ContractVehicle :=ContractValidity := SEQUENCE contractRestrictions OCTET STRING (SIZE(4) contractExpiryDate DateCompactFigure 3 Basic addressing mechanism 5.3.2 Role of the EID In a given OBE, the
38、DSRC-EID (different from 0) is used to address an EFC context, identified by the EFC-ContextMark (see 6.2.3), in which Attributes can be addressed unambiguously by AttributeIDs inside an Element of the OBE. In the VST, the OBE specifies one or several of these EFC contexts, each corresponding to an
39、EFC ContextMark and the EID to be used for addressing the attributes and using the EFC functions supported by it. EXAMPLE AttrlD = 0 AttrlD = 4Contract AuthenticatorAAttrlD = n.AttrlD = 3AttrlD = 2Contract VehicleAContract ValidityAContract ValidityBContract VehicleBContract AuthenticatorB .Contract
40、 ValidityCContract VehicleCContract AuthenticatorC .EID = 1EID = 2EID = 3Figure 4 Role of the EID EID equals 0 shall be used to address application-independent functions and components, e.g. SET_MMI and TRANSFER_CHANNEL (see 7.2). 5.3.3 Multiple Instances of Attributes There may be n, where n is an
41、integer, instances of an Attribute available in an OBE. The maximum number of instances Nmax of one Attribute may be limited according to the needs of operators and users. The default maximum number of instances is Nmax=1. The value of Nmax is determined at the time of OBE configuration. BS EN ISO 1
42、4906:2011+A1:2015ISO 14906:2011+A1:2015 (E)10 ISO 2011 All rights reservedBS EN ISO 14906:2011ISO 14906:2011(E) 10 ISO 2011 All rights reservedEXAMPLE Figure 3 illustrates the basic addressing mechanism. AttrlD = 0 AttrlD = 4Contract AuthenticatorAttrlD = nAttribute IDAttributeASN.1-Type.AttrlD = 3A
43、ttrlD = 2Contract VehicleContract ValidityContractAuthenticator :=ContractVehicle :=ContractValidity := SEQUENCE contractRestrictions OCTET STRING (SIZE(4) contractExpiryDate DateCompactFigure 3 Basic addressing mechanism 5.3.2 Role of the EID In a given OBE, the DSRC-EID (different from 0) is used
44、to address an EFC context, identified by the EFC-ContextMark (see 6.2.3), in which Attributes can be addressed unambiguously by AttributeIDs inside an Element of the OBE. In the VST, the OBE specifies one or several of these EFC contexts, each corresponding to an EFC ContextMark and the EID to be us
45、ed for addressing the attributes and using the EFC functions supported by it. EXAMPLE AttrlD = 0 AttrlD = 4Contract AuthenticatorAAttrlD = n.AttrlD = 3AttrlD = 2Contract VehicleAContract ValidityAContract ValidityBContract VehicleBContract AuthenticatorB .Contract ValidityCContract VehicleCContract
46、AuthenticatorC .EID = 1EID = 2EID = 3Figure 4 Role of the EID EID equals 0 shall be used to address application-independent functions and components, e.g. SET_MMI and TRANSFER_CHANNEL (see 7.2). 5.3.3 Multiple Instances of Attributes There may be n, where n is an integer, instances of an Attribute a
47、vailable in an OBE. The maximum number of instances Nmax of one Attribute may be limited according to the needs of operators and users. The default maximum number of instances is Nmax=1. The value of Nmax is determined at the time of OBE configuration. BS EN ISO 14906:2011ISO 14906:2011(E) ISO 2011
48、All rights reserved 11EXAMPLE AttrlD = 0 AttrlD = n.AttrlD = 5EID = 1.ReceiptServicePart2ReceiptServicePart1ReceiptServicePart0Figure 5 Multiple instances (0-2) of attribute 5 The handling of multiple instances and the corresponding addressing mechanism are described in detail as part of the behavio
49、ur specification of the corresponding functions supporting multiple instances (see 7.2.6 for GET_INSTANCE and 7.2.7 for SET_INSTANCE). 5.4 Addressing of components Components of an OBE to be addressed via the EFC Application Interface include for example: OBU; SAM 1; SAM 2; ICC; Display; Buzzer; Printer; Serial interface; Parallel interface; GPS; Tachograph; Bluetooth. Addressing of these components is ena
