BS PD CEN TS 16986-2016 Electronic Fee Collection Interoperable application profiles for information exchange between Service Provision and Toll Charging《电子收费 服务提供和收费之间的信息交换用互操作应用配.pdf

1、Electronic Fee Collection Interoperable application profiles for information exchange between ServiceProvision and Toll ChargingPD CEN/TS 16986:2016BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06National forewordThis Published Document is the UK implementation of CE

2、N/TS 16986:2016.The UK participation in its preparation was entrusted to TechnicalCommittee EPL/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 provision

3、s ofa contract. Users are responsible for its correct application. The British Standards Institution 2016.Published by BSI Standards Limited 2016ISBN 978 0 580 93168 0ICS 35.240.60Compliance with a British Standard cannot confer immunity fromlegal obligations.This Published Document was published un

4、der the authority of theStandards Policy and Strategy Committee on 31 October 2016.Amendments/corrigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD CEN/TS 16986:2016TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 16986 October 2016 ICS 35.240.60 Eng

5、lish Version Electronic Fee Collection - Interoperable application profiles for information exchange between Service Provision and Toll Charging Perception de tlpage - Profil dapplication interoprabilit pour change dinformations entre la prestation de service et la perception du page Elektronische G

6、ebhrenerhebung - Interoperable Anwendungsprofile fr den Informationsaustausch zwischen den Dienste-Versorgern und MauterhebernThis Technical Specification (CEN/TS) was approved by CEN on 13 July 2016 for provisional application. The period of validity of this CEN/TS is limited initially to three yea

7、rs. After two years 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 availabl

8、e promptly at national 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, Bel

9、gium, 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, Spain, Sweden, Switz

10、erland, Turkey andUnited Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2016 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national

11、 Members. Ref. No. CEN/TS 16986:2016 EPD CEN/TS 16986:2016CEN/TS 16986:2016 (E) 2 Contents Page European foreword . 6 Introduction 7 1 Scope 8 2 Normative references 8 3 Terms and definitions . 9 4 Abbreviations 13 5 Conformance 14 5.1 General . 14 5.2 Base standard 14 5.3 Main contents of an 12855-

12、IAP . 14 5.4 Conformance requirements . 15 5.4.1 General requirements 15 5.4.2 Transaction requirements 15 5.4.3 Data requirements . 16 5.4.4 Transaction requirements 17 5.5 Conformation notification 20 5.6 Interoperability 21 6 Requirements on common transactions 21 6.1 General . 21 6.2 InfoExchang

13、e 21 6.2.1 InfoExchangeContent 21 6.2.2 InfoExchangeAuthenticator . 23 6.3 AckADU 23 6.3.1 General . 23 6.3.2 Syntax and semantics 23 6.4 USERDETAILS - Exchange Enforcement Data - Retrieve and Provide User Details 26 6.4.1 Transaction sequence, triggers and timings 26 6.4.2 Syntax and semantics 28 6

14、.5 LISTOFUSERS - List of Users . 30 6.5.1 Transaction sequence, triggers and timings 30 6.5.2 Syntax and semantics 31 6.6 EXCEPTIONLIST - Managing Exception Lists 32 6.6.1 Transaction sequence, triggers and timings 32 6.6.2 Syntax and semantics 33 6.7 TRUSTOBJECTS - Exchange trust objects . 37 6.7.1

15、 APDU transfer mechanisms 37 6.7.2 Transaction sequence, triggers and timings 37 6.7.3 Syntax and semantics 38 6.8 PAYMENTCLAIM - Payment Claim 40 6.8.1 Transaction sequence, triggers and timings 40 6.8.2 Syntax and semantics 42 7 DSRC profile specific transactions . 44 7.1 DSRC.CONTRACTISSUERLIST C

16、ontractIssuerList 44 7.1.1 Transaction sequence, triggers and timings 44 7.1.2 Syntax and semantics - ContractIssuerListADU 45 PD CEN/TS 16986:2016CEN/TS 16986:2016 (E) 3 7.2 DSRC.EFCCONTEXTDATA - Provide and Request EFC Context Data . 45 7.2.1 Transaction sequence, triggers and timings . 45 7.2.2 S

17、yntax and semantics - EfcContextDataADU . 47 7.3 DSRC.BILLINGDETAILS - Report billing details 48 7.3.1 Transaction sequence, triggers and timings . 48 7.3.2 Syntax and semantics 50 7.4 DSRC.REPORTABNORMALOBE . 62 7.4.1 Transaction sequence, triggers and timings . 62 7.4.2 Syntax and semantics - Repo

18、rtAbnormalOBEADU . 64 8 GNSS profile specific transactions 64 8.1 GNSS.TOLLDECLARATIONS - Report toll declarations. 64 8.1.1 Transaction sequence, triggers and timings . 64 8.1.2 Syntax and semantics - TollDeclarationADU 66 8.2 Report billing details . 73 8.2.1 General . 73 8.2.2 GNSS.BILLINGDETAILS

19、.TSP - Transaction sequence, triggers and timings . 73 8.2.3 GNSS.BILLINGDETAILS.TC - Transaction sequence, triggers and timing 75 8.2.4 Syntax and semantics of GNSS.BILLINGDETAILS.TSP and GNSS.BILLINGDETAILS.TC - BillingDetailsADU . 76 8.3 GNSS.PAYMENTANNOUNCEMENT . 80 8.3.1 Transaction sequence, t

20、riggers and timings . 80 8.3.2 Syntax and semantics - PaymentAnnouncementADU . 81 9 APDU Transfer mechanisms . 83 9.1 ASN.1 encoding 83 9.2 Generic transfer mechanisms 83 9.3 Alternative transfer mechanisms for transaction type TRUSTOBJECTS 83 Annex A (normative) ICS Proforma . 84 A.1 Guidance for c

21、ompleting the PICS proforma 84 A.1.1 Purposes and structure 84 A.1.2 Abbreviations and conventions . 84 A.1.3 Instructions for completing the PICS proforma . 86 A.2 Identification of the implementation 86 A.2.1 General . 86 A.2.2 Date of the statement 86 A.2.3 Implementation Under Test (IUT) identif

22、ication 86 A.2.4 System Under Test (SUT) identification . 86 A.2.5 Product supplier . 87 A.2.6 Applicant (if different from product supplier) 87 A.2.7 PICS contact person . 87 A.3 Identification of the protocol . 88 A.4 Global statement of conformance . 88 A.5 Roles 88 A.6 Profiles 88 A.7 InfoExchan

23、ge 89 PD CEN/TS 16986:2016CEN/TS 16986:2016 (E) 4 A.7.1 InfoExchange protocol procedures 89 A.7.2 InfoExchange parameters . 89 A.8 Common AckADU support. 90 A.8.1 AckADU fields 90 A.9 Common Transactions support . 90 A.9.1 General . 90 A.9.2 USERDETAILS support 91 A.9.3 LISTOFUSERS support 92 A.9.4

24、EXCEPTIONLIST support 94 A.9.5 TRUSTOBJECTS support . 96 A.9.6 PAYMENTCLAIM support . 97 A.10 DSRC Specific Transactions Support . 99 A.10.1 Prerequisites . 99 A.10.2 DSRC transactions support . 99 A.10.3 DSRC.CONTRACTISSUERLIST support 99 A.10.4 DSRC.EFCCONTEXTDATA support 100 A.10.5 DSRC.BILLINGDE

25、TAILS support 102 A.10.6 DSRC.REPORTABNORMALOBE support . 108 A.11 GNSS Specific Transactions Support 109 A.11.1 General . 109 A.11.2 Common GNSS.BILLINGDETAILS support 110 A.11.3 GNSS.BILLINGDETAILS.TSP support 113 A.11.4 GNSS.BILLINGDETAILS.TC support 114 A.11.5 GNSS.TOLLDECLARATION support 115 A.

26、11.6 GNSS.PAYMENTANNOUNCEMENT support 118 A.12 Transfer mechanisms . 119 Annex B (normative) Interoperability Statement Proforma . 120 B.1 Guidance for completing the Interoperability Statement proforma . 120 B.2 Interoperablilty Statement for transaction support . 120 B.3 Interoperability Statement

27、 for the USERDETAILS transaction type 121 B.4 Interoperability Statement for the LISTOFUSERS transaction type 121 B.5 Interoperability Statement for the EXCEPTIONLIST transaction type . 122 B.6 Interoperability Statement for the TRUSTOBJECTS transaction type 123 B.7 Interoperability Statement for th

28、e PAYMENTCLAIM transaction type 124 B.8 Interoperability Statement for the DSRC.CONTRACTISSUERLIST transaction type 124 B.9 Interoperability Statement for the DSRC.EFCCONTEXTDATA transaction type 124 B.10 Interoperability Statement for the DSRC.BILLINGDETAILS transaction type 125 PD CEN/TS 16986:201

29、6CEN/TS 16986:2016 (E) 5 B.11 Interoperability Statement for the DSRC.REPORTABNORMALOBE transaction type . 125 B.12 Interoperability Statement for the GNSS.TOLLDECLARATIONS transaction type 125 B.13 Interoperability Statement for the GNSS.BILLINGDETAILS.TSP transaction type . 126 B.14 Interoperabili

30、ty Statement for the GNSS.BILLINGDETAILS.TC transaction type 126 B.15 Interoperability Statement for the GNSS.PAYMENTANNOUNCEMENT transaction type . 127 Annex C (normative) Web service definition (WSDL) . 128 Annex D (informative) Use of this Technical Specification for the EETS 129 D.1 General 129

31、D.2 Overall relationship between European standardization and the EETS . 129 D.3 European standardization work supporting the EETS 129 D.4 Correspondence between this Technical Specification and the EETS 130 Annex E (informative) How to read UML class diagrams in this Technical Specification 131 E.1

32、 General 131 E.2 Relation of ASN.1 code and UML class diagrams 131 E.3 Relation of UML class diagrams for the base standard and the profile 133 Bibliography 135 PD CEN/TS 16986:2016CEN/TS 16986:2016 (E) 6 European foreword This document (CEN/TS 16986:2016) has been prepared by Technical Committee CE

33、N/TC 278 “Intelligent transport systems”, the secretariat 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. This document has

34、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 organisations of the following countries are bound to announce this Technical Specification: Austria, Belgium, Bulg

35、aria, 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, Spain, Sweden, Switzerland, Tu

36、rkey and the United Kingdom. PD CEN/TS 16986:2016CEN/TS 16986:2016 (E) 7 Introduction The Standard on information exchange between service provision and toll charging (i.e. EN ISO 12855:2015) is a so-called toolbox standard. That means that it provides a large number of options that can be used to s

37、upport various needs of toll chargers and toll service providers. As such, it provides useful but not sufficient support to ensure technical interoperability. The aim of this Technical Specification is to produce a profile specification that provides technical interoperability to support the EFC inf

38、ormation exchange between toll service providers (TSPs) and toll chargers (TCs): based on DSRC; based on GNSS/CN autonomous systems. This Technical Specification covers the definition of interoperable application profiles (IAP) applicable for the use of EN ISO 12855:2015. These profiles define a spe

39、cific coherent set of transactions, triggers, conditions, data elements, transfer mechanisms and supporting functions for an interoperable exchange of data between the central equipment of TCs and TSPs (in Europe). This IAP defines profiles using the concept of “International Standardised Profiles (

40、ISP)”, as defined in ISO/IEC TR 10000-1. The ISP-concept is specifically suited for defining interoperability specifications where a set of base standards can be used in different ways. This is exactly the case for EN ISO 12855:2015, where the base standard allows for different choices that are not

41、interoperable. The principles of the ISP-concept can be summarized as follows: an ISP will make references only to base standards or other ISPs; the profile will restrict the choice of base standard options to the extent necessary to maximize the probability of interoperability (e.g. chosen classes,

42、 conforming subsets, options and parameter values of base standards); the ISP will not copy content of the base standards (in order to avoid consistency problems with the base standards); the profile will not specify any requirements that would contradict or cause non-conformance to the base standar

43、ds; the profile may contain conformance requirements that are more specific and limited in scope than those of the base standards; conformance to a profile implies by definition conformance to a set of base standards, whereas conformance to that set of base standards does not necessarily imply confo

44、rmance to the profile. This Technical Specification is consistent with and is intended to provide support for the technical specification of the EETS laid down in the European Directive 2004/52/EC and in the subsequent European Commission Decision 2009/750/EC. A suite of test specifications is curre

45、ntly being developed to support assessment of an implementation for compliance with this Technical Specification. PD CEN/TS 16986:2016CEN/TS 16986:2016 (E) 8 1 Scope This Technical Specification defines an application interface definition by selecting suitable options from the base standard EN ISO 1

46、2855:2015. Furthermore, it defines transfer mechanisms and supporting functions to ensure the interoperability between TCs and TSPs. This Technical Specification covers: exchange of information between the central equipment associated with the two roles service provision and toll charging, e.g.: cha

47、rging related data (exception lists, toll declarations, billing details, payment claims); administrative data (trust objects, EFC context data, contact details for enforcement, etc.); confirmation data. transfer mechanisms and supporting functions; semantics of data elements; implementation conforma

48、nce statement proforma (Annex A), as a basis for assessment of conformity to this Technical Specification; an Interoperability statement proforma (Annex B), as a basis for assessment of transactional intereoperability of two technical implementations; a web service definition (Annex C) for the use o

49、f web services as communication technology. The implementation of the underlying back office systems and their business processes is not covered. Therefore, outside of the scope is in particular: details on how to achieve security using the authenticator data elements of the base standards; how to operate compliance checking and the enforcement process; commercial aspects; definition of non-functional features such as performance indicators like accuracy, availability and reporting requirements. This Technical Specif