1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationElectronic fee collection Interoperable application profiles for autonomous systemsPD CEN/TS 16331:2012National forewordThis Published Document is the UK implementation of CEN/TS
2、 16331:2012.The UK participation in its preparation was entrusted to Technical CommitteeEPL/278, Road transport informatics.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 of ac
3、ontract. Users are responsible for its correct application. The British Standards Institution 2012Published by BSI Standards Limited 2012ISBN 978 0 580 76367 0ICS 03.220.20; 35.240.60Compliance with a British Standard cannot confer immunity fromlegal obligations.This Published Document was published
4、 under the authority of theStandards Policy and Strategy Committee on 30 April 2012.Amendments issued since publicationAmd. No. Date Text affectedPUBLISHED DOCUMENTPD CEN/TS 16331:2012TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 16331 March 2012 ICS 03.220.20; 35.24
5、0.60 English Version Electronic fee collection - Interoperable application profiles for autonomous systems Perception du tlpage - Profil dapplication dinteroprabilit pour les systmes autonomes Elektronische Gebhrenerhebung - Interoperable Anwendungsprofile fr unabhngige Systeme This Technical Specif
6、ication (CEN/TS) was approved by CEN on 8 January 2012 for provisional application. The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their comments, particularly on the question whether the CEN/TS can be convert
7、ed 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 national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS
8、) 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, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Li
9、thuania, 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 KOMITEE FR NORMUNG Management Centre: Avenue Marnix 17, B-1000 Brus
10、sels 2012 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN/TS 16331:2012: EPD CEN/TS 16331:2012CEN/TS 16331:2012(E) 2 Contents Page Foreword 5Introduction .61 Scope 82 Normative references 93 Terms and definitions 104 Abbreviations
11、 115 General profile independent IAP requirements . 125.1 The principle defining EFC cluster supported regime characteristics using profiles 125.2 Toll Charger requirements . 125.2.1 General . 125.2.2 Toll Charge Back End requirements . 135.3 Toll Charger RSE requirements 135.4 Service Provider requ
12、irements 135.4.1 General . 135.4.2 Service Provider Back End Requirements . 145.4.3 Front End specific requirements . 146 The use of conditional requirements 167 Standardised profiles . 167.1 General . 167.2 How to use standardised profiles . 217.2.1 General . 217.2.2 SR (Sectioned Roads tolling) 21
13、7.2.3 SD (Sectioned Roads tolling or Distance based Area pricing) 217.2.4 OSD (Overlapping Sectioned Roads tolling or Distance based Area pricing) . 227.2.5 OSDT (Overlapping Sectioned Roads tolling or Distance or Time based Area pricing) . 227.2.6 OSDTC (Overlapping Sectioned Roads tolling or Dista
14、nce or Time based Area or Cordon pricing) . 227.3 Front End classes selection 22Annex A (normative) Conditional profile requirements . 23A.1 General . 23A.2 Conditional requirements to be observed by the Toll Charger . 23A.2.1 When using contextInterrelations . 23A.2.2 When using roadSectionPricing
15、. 23A.2.3 When using arePricingDistance 23A.2.4 When using roadNetworks 23A.2.5 When using arePricingTime 23A.2.6 When using cordonPricing 23A.2.7 When using agnssGDFLayout or tollContextLayout 24A.2.8 When using tariffTable . 24A.2.9 When using tariffClassDefinition 24A.2.10 When using localVehicle
16、ClassDefinition . 24A.2.11 When using timeClassDefinition . 24A.2.12 When using relativeTimePeriods 24A.2.13 When using classesSetExternally. 25A.2.14 When using userClassdefinition . 25A.2.15 When using actualNumberOfPassengers 25A.2.16 When using SectionLayout 25A.2.17 When using AreaLayout . 25A.
17、2.18 When using roadNetwork 25PD CEN/TS 16331:2012CEN/TS 16331:2012(E) 3 A.2.19 When using chargeReportingEvents 25A.2.20 When using chargeReportConfiguration 25A.3 Conditional requirements to be observed by the Service Provider . 27A.3.1 When using tollDeclarationADU 27A.3.2 When using combinedChar
18、geReportContexts. 28A.3.3 When using precedenceLevel 28A.3.4 When using roadSectionPricing 28A.3.5 When using areaPricingDistance 29A.3.6 When using areaPricingDistance.roadNetworks . 29A.3.7 When using areaPricingTime . 29A.3.8 When using cordonPricing . 29A.3.9 When using tariffTable 29A.3.10 When
19、 using tariffClassDefinition . 29A.3.11 When using localVehiceClasses 29A.3.12 When using timeClasses 29A.3.13 When using timeClasses.ordinalElements.relativeTimeClasses . 30A.3.14 When using timeClasses.nominalElements.classesSetEexternally 30A.3.15 When using userClasses 30A.3.16 When using tollCo
20、ntextLayout. 30A.3.17 When using chargeReportingEvents 30A.3.18 When using chargeReportConfiguration 30A.4 Conditional requirements to be observed by the Front End 30A.4.1 When using in the ChargeReport all other elements than usageStatement . 30A.4.2 When using in the ChargeReport the usageStatemen
21、tList . 31A.4.3 When using aggregatedFee 31A.4.4 When using aggregatedSingleTariffClassSession 31A.4.5 When using listOfChargeObjects 31A.4.6 When using listOfRawUsageData 31Annex B (normative) The use of identifiers . 32B.1 General . 32B.2 Identifiers specified in CEN ISO/TS 13141 36B.3 Identifiers
22、 specified in CEN ISO/TS 17575-1 . 36B.4 Identifiers specified in CEN ISO/TS 17575-3 . 38B.5 Identifiers specified in CEN ISO/TS 17575-4 . 39B.6 Identifiers specified in CEN ISO/TS 12813 39B.7 Identifiers specified in EN ISO 12855 39Annex C (normative) Protocol Implementation Conformance Statement 4
23、1C.1 Guidance for completing the PICS proforma . 41C.1.1 Purposes and structure 41C.1.2 Abbreviations and conventions . 41C.1.3 Instructions for completing the PICS proforma . 43C.2 PICS proforma for the Toll Chargers Back-end 43C.2.1 Identification of the implementation 43C.2.2 Identification of th
24、e protocol 46C.2.3 Global statement of conformance . 46C.2.4 Profiles 46C.2.5 EN ISO 12855 . 46C.3 PICS proforma for the Toll Charger RSE 50C.3.1 Identification of the implementation 50C.3.2 Identification of the protocol 52C.3.3 Global statement of conformance . 52C.3.4 Support for CCC and LAC Appl
25、ications 52C.4 PICS proforma for the Service Provider Back-end 54C.4.1 Identification of the implementation 54C.4.2 Identification of the protocol 56C.4.3 Global statement of conformance . 56C.4.4 Profiles 57C.4.5 EN ISO 12855 . 57PD CEN/TS 16331:2012CEN/TS 16331:2012(E) 4 C.5 PICS proforma for the
26、Service Provider Front End . 61C.5.1 Identification of the implementation . 61C.5.2 Identification of the protocol . 63C.5.3 Global statement of conformance . 63C.5.4 Front End Class 64C.5.5 CEN ISO/TS 17575-1 Charge Report - Usage Statement. 64C.5.6 CEN ISO/TS 17575-3 Charge Report Configuration 64
27、C.5.7 Support for CCC and LAC Applications . 65Annex D (informative) IAP taxonomy and numbering 66D.1 General . 66D.2 Taxonomy of Interoperable Application Profiles (IAP) . 66D.2.1 Specified profiles 66D.2.2 Future new profiles . 67D.3 IAP numbering and referencing 67D.3.1 IAP numbering 67D.3.2 IAP
28、referencing . 67Annex E (informative) How to define new profiles - the profile creation principle 68Bibliography . 69PD CEN/TS 16331:2012CEN/TS 16331:2012(E) 5 Foreword This document (CEN/TS 16331:2012) has been prepared by Technical Committee CEN/TC 278 “Road transport and traffic telematics”, the
29、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 and/or CENELEC shall not be held responsible for identifying any or all such patent rights. This document has been prepared under a mandate g
30、iven 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 announce this Technical Specification: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Re
31、public, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. PD CEN/TS 16331:2012CEN/TS 16331:2012(E)
32、6 Introduction This Technical Specification should be used by stakeholders of a group of electronic fee collection (EFC) regimes as a guide when planning to establish or extending an EFC cluster providing interoperability for tolled vehicles in all participating EFC domains. The scope of this docume
33、nt covers the tolling principles for autonomous EFC systems. The goal of an interoperable EFC cluster is to ensure that all tolled vehicles can be charged the due toll amount in all EFC domains. This can be achieved by requiring that all necessary equipment, whether in the tolled vehicles, the Toll
34、Service Providers central systems, the Toll Chargers central systems and along the roadside in the EFC domains, conform to the same interface standards and to an Interoperable Application Profile, as defined in this Technical Specification. The system architecture defined in ISO 17573 is the basis f
35、or all standards that relate to Electronic Fee Collection systems. It specifies the roles and responsibilities needed within an interoperable EFC cluster. Such a cluster is illustrated in Figure 1, and consists of multiple Toll Service Providers and multiple Toll Chargers. Each Toll Charger has its
36、own EFC Domain and its own EFC regime. Conversely, each Toll Service Provider has a number of clients, who own vehicles and may be liable to pay toll in the EFC domains of the Toll Chargers. Figure 1 Actors and interfaces within an interoperable EFC cluster CEN has produced a set of standards that t
37、ogether specify a basis for EFC systems. This document refers to these standards as the base standards. They are necessary to ensure technical interoperability between different EFC-systems, but in themselves they are not sufficient to achieve this, as they contain a large number of options and choi
38、ces to be made in a concrete implementation. PD CEN/TS 16331:2012CEN/TS 16331:2012(E) 7 Figure 2 shows the base standards and their relationships. Figure 2 Suite of EFC related standards NOTE There may be one or more instances of each box representing an actor This set of base standards includes the
39、 CEN ISO/TS 17575-suite, ISO 17573, EN ISO 12855, CEN ISO/TS 13141 and CEN ISO/TS 12813. These standards have the characteristic of toolbox standards, specifying messages and data elements, which - if used are to be used in the prescribed way. However, these base standards contain many optional feat
40、ures that may or may not be implemented by different Toll Chargers or Service Providers. Therefore, the base standards alone do not guarantee interoperability between the systems of different actors without further restrictions of the use of optional features of these base standards. This is the pur
41、pose of this profile standard to restrict the choices from the above listed set of base standards. This Technical Specification defines a number of Interoperable Application Profiles (IAP) for autonomous Electronic Fee Collection systems, according to the concept of “International Standardised Profi
42、les (ISP)“ as defined in ISO IEC/TR 10000-1. Each profile provides a coherent set of choices from among the options in the base standards. A profile thus may be used to determine a concrete set of requirements for EFC constituents. When multiple EFC systems are based on the same profile, the profile
43、 will serve as a common technical platform for EFC interoperability. Which profile should be chosen will depend on the needs of all participants in this EFC cluster and on the outcome of negotiations between them. The profiles in this Technical Specification were created in order to meet the require
44、ments of early adoptions of the general principles of autonomous interoperable EFC clusters, such as the upcoming European Electronic Toll Service. This Technical Specification specifies also a methodology to define a customised profile if none of the specified profiles are acceptable to all partici
45、pants in an interoperable EFC cluster. PD CEN/TS 16331:2012CEN/TS 16331:2012(E) 8 Each Toll Service Provider taking part in an EFC cluster should be aware that he needs to implement all the features of the chosen profile. Therefore, it will generally be in the best interest of the Service Providers
46、to select the simplest profile that is still acceptable to all Toll Chargers. Toll Chargers within the same EFC cluster, however, still have the choice to use any of these features or not. 1 Scope This Technical Specification defines a set of interoperable application profiles suitable to be used de
47、fining the overall functionality of an interoperable EFC cluster using autonomous vehicle equipment. Doing so, it also defines a way of defining further profiles for future use. The profiles cover a wide range from simple toll road systems up to very complex tolling principles and tariff rules. An E
48、FC cluster shall select and use one of these profiles covering the needs of all participating Toll Chargers. The scope is limited to those base standards providing data elements or messages to be used specifically when defining the data exchange for autonomous tolling principles. This covers ISO 17573 and the base standards CEN ISO/TS 17575 parts 1 to 4, CEN ISO/
