1、BSI Standards PublicationBS EN ISO 17575-2:2016Electronic fee collection Application interface definitionfor autonomous systemsPart 2: Communication and connection tothe lower layers (ISO 17575-2:2016)BS EN ISO 17575-2:2016 BRITISH STANDARDNational forewordThis British Standard is the UK implementat
2、ion of EN ISO17575-2:2016. It supersedes DD CEN ISO/TS 17575-2:2010 which iswithdrawn.The UK participation in its preparation was entrusted to TechnicalCommittee EPL/278, Intelligent transport systems.A list of organizations represented on this committee can beobtained on request to its secretary.Th
3、is publication does not purport to include all the necessaryprovisions of a contract. Users are responsible for its correctapplication. The British Standards Institution 2016. Published by BSI StandardsLimited 2016ISBN 978 0 580 84629 8ICS 03.220.20; 35.240.60Compliance with a British Standard canno
4、t confer immunity fromlegal obligations.This British Standard was published under the authority of theStandards Policy and Strategy Committee on 31 March 2016.Amendments issued since publicationDate Text affectedEUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORMEN ISO 17575-2 February 2016 ICS 35.240
5、.60; 03.220.20 Supersedes CEN ISO/TS 17575-2:2010English Version Electronic fee collection - Application interface definition for autonomous systems - Part 2: Communication and connection to the lower layers (ISO 17575-2:2016) Perception du tlpage - Dfinition de linterface dapplication pour les syst
6、mes autonomes - Partie 2: Communications et connexions aux couches basses (ISO 17575-2:2016) Elektronische Gebhrenerhebung - Definition der Anwendungsschnittstelle fr autonome Systeme - Teil 2: Kommunikation und Verbindung mit den unteren Schichten (ISO 17575-2:2016) This European Standard was appro
7、ved by CEN on 11 December 2015. CEN members 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 nationa
8、l standards may be obtained on application 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
9、 and notified to the CEN-CENELEC Management 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, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hu
10、ngary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey andUnited Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG CEN-CEN
11、ELEC 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 Members. Ref. No. EN ISO 17575-2:2016 EBS EN ISO 17575-2:2016EN ISO 17575-2:2016 (E) 3 European foreword This document (EN ISO 17575-2:2016)
12、has been prepared by Technical Committee ISO/TC 204 “Intelligent transport systems” in collaboration with Technical Committee CEN/TC 278 “Intelligent transport systems” the secretariat of which is held by NEN. This European Standard shall be given the status of a national standard, either by publica
13、tion of an identical text or by endorsement, at the latest by August 2016, and conflicting national standards shall be withdrawn at the latest by August 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 shal
14、l not be held responsible for identifying any or all such patent rights. This document supersedes CEN ISO/TS 17575-2:2010. 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 Regulation
15、s, the national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy,
16、Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. Endorsement notice The text of ISO 17575-2:2016 has been approved by CEN as EN ISO 17575-2:2016 without any modification. BS EN ISO 175
17、75-2:2016ISO 17575-2:2016(E)Foreword ivIntroduction v1 Scope . 12 Terms and definitions . 23 Abbreviated terms 34 EFC Front End communication architecture 44.1 General . 44.2 Relationship with the overall EFC architecture 55 EFC communication services (functions) . 55.1 General concept 55.2 Initiali
18、zation phase 75.2.1 General 75.2.2 Incoming (BE to FE Application) session request . 75.2.3 Outgoing (FE Application to BE) session establishment . 85.3 Point-to-point communication service primitives . 85.3.1 General 85.3.2 Unstructured messages (ADUs) 85.3.3 Structured messages (ADUs) 85.4 Session
19、 end . 85.5 Session failure 95.6 Security considerations . 95.7 Media selection options 96 The use of a communication stack . 96.1 General . 96.2 Requirements for an underlying communication technology . 96.3 Mobile terminated calls 10Annex A (normative) Abstract API definition 11Annex B (normative)
20、 Protocol implementation conformance statement (PICS) proforma 17Annex C (informative) API requirements .22Annex D (informative) Examples of definitions for appropriate languages.23Annex E (informative) Use of this part of ISO 17575 for the EETS 26Bibliography .28 ISO 2016 All rights reserved iiiCon
21、tents PageBS EN ISO 17575-2:2016ISO 17575-2:2016(E)ForewordISO (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
22、 member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the Internationa
23、l Electrotechnical 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 t
24、ypes of ISO documents 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 b
25、e held responsible 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 inform
26、ation given for the convenience of users and does not constitute an endorsement.For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the
27、 following URL: Foreword - Supplementary informationThe committee responsible for this document is ISO/TC 204, Intelligent transport systems.This edition of ISO 17575-2 cancels and replaces ISO/TS 17575-2:2010, which has been technically revised. The following changes have been made: conversion from
28、 a Technical Specification to an International Standard; editorial and formal corrections as well as changes to improve readability.ISO 17575 consists of the following parts, under the general title Electronic fee collection Application interface definition for autonomous systems: Part 1: Charging P
29、art 2: Communication and connection to the lower layers Part 3: Context dataIn this edition of the ISO 17575-series the contents of ISO/TS 17575-4:2011 were incorporated into ISO 17575-3:2016. ISO/TS 17575-4:2011 will be withdrawn once ISO 17575-3 has been published.iv ISO 2016 All rights reservedBS
30、 EN ISO 17575-2:2016ISO 17575-2:2016(E)Introduction0.1 Autonomous systemsISO 17575 is a series of standards defining the information exchange between the Front End and the Back End in electronic fee collection (EFC) based on autonomous on-board equipment (OBE). EFC systems automatically collect char
31、ging data for the use of road infrastructure including motorway tolls, zone-based fees in urban areas, tolls for special infrastructure like bridges and tunnels, distance-based charging and parking fees.Autonomous OBE operates without relying on dedicated road-side infrastructure by employing wide-a
32、rea technologies such as Global Navigation Satellite Systems (GNSS) and Cellular Networks (CN). These EFC systems are referred to by a variety of names. Besides the terms autonomous systems and GNSS/CN systems, the terms GPS/GSM systems and wide-area charging systems are also in use.Autonomous syste
33、ms use satellite positioning, often combined with additional sensor technologies such as gyroscopes, odometers and accelerometers, to localize the vehicle and to find its position on a map containing the charged geographic objects, such as charged roads or charged areas. From the charged objects, th
34、e vehicle characteristics, the time of day and other data that are relevant for describing road use, the tariff and ultimately the road usage fee are determined.Two strengths of the autonomous approach to electronic fee collection are its flexibility, allowing the implementation of almost all concei
35、vable charging principles, and its independence from local infrastructure, thereby predisposing this technology towards interoperability across charging systems and countries. Interoperability can only be achieved with clearly defined interfaces, which is the aim and justification of ISO 17575.0.2 B
36、usiness architectureThis part of ISO 17575 complies with the business architecture defined in ISO 17573. According to this architecture, the toll charger is the provider of the road infrastructure and, hence, the recipient of the road usage charges. The toll charger is the actor associated with the
37、toll charging role (see Figure 1).Service UsageServiceProvisionTollChargingInteroperabilityManagementFigure 1 The role-based model underlying ISO 17575Service providers issue OBE to the users of the road infrastructure. Service providers are responsible for operating OBE that will record the amount
38、of road usage in all toll charging systems the vehicle passes through and for delivering the charging data to the individual toll chargers. In general, each service provider delivers charging data to several toll chargers and, in general, each toll charger receives charging data from more than one s
39、ervice provider. Interoperability management, as shown in Figure 1, comprises all specifications and activities that define and maintain a set of rules that govern the overall toll charging environment. ISO 2016 All rights reserved vBS EN ISO 17575-2:2016ISO 17575-2:2016(E)0.3 Technical architecture
40、The technical architecture of Figure 2 is independent of any particular practical realization. It reflects the fact that some processing functionalities can either be allocated to the OBE or to an associated off-board component (proxy). An example of processing functionality that can be realized eit
41、her on- or off-board is map-matching, where the vehicle locations in terms of measured coordinates from GNSS are associated to geographic objects on a map that either reside on- or off-board. Also, the computation of tariffs can be done with OBE tariff tables and processing, or with an off-board com
42、ponent.Processing EquipmentFront End Back EndScope ofISO 17575OBEProxyRoad Usage DataContext DataFigure 2 Assumed technical architecture and interfacesThe combined functionality of OBE and proxy is denoted as Front End. A Front End implementation where processing is predominately on the OBE-side is
43、known as a smart client (or intelligent client, fat client) or edge-heavy. A Front End where processing is mostly done off-board is denoted as thin-client or edge-light architecture. Many implementations between the “thin” and “thick” extremes are possible, as depicted by the gradual transition in t
44、he wedges in Figure 2. Both extremes of architectural choice have their merits and are one means where manufacturers compete with individual allocations of functionality between on-board and central resources.Especially for thin client OBE, manufacturers might devise a wide variety of optimizations
45、of the transfer of localization data between OBE and off-board components, where proprietary algorithms are used for data reduction and data compression. Standardization of this transfer is neither fully possible nor beneficial.0.4 Location of the specification interfaceIn order to abstract from, an
46、d become independent of, these architectural implementation choices, the primary scope of ISO 17575 is the data exchange between Front End and Back End (see the corresponding vertical line in Figure 2). For every toll regime, the Back End will send context data, i.e. a description of the toll regime
47、 in terms of charged objects, charging rules and, if required, the tariff scheme to the Front End, and will receive usage data from the Front End.It has to be noted also that the distribution of tasks and responsibilities between service provider and toll charger will vary individually. Depending on
48、 the local legal situation, toll chargers will require “thinner” or “thicker” data, and might or might not leave certain data processing tasks to service providers. Hence, the data definitions in ISO 17575 may be useful on several interfaces.vi ISO 2016 All rights reservedBS EN ISO 17575-2:2016ISO 1
49、7575-2:2016(E)ISO 17575 also provides for basic media-independent communication services that may be used for communication between Front End and Back End, which might be line-based or an air-link, and can also be used for the air-link between OBE and central communication server.0.5 The parts of ISO 17575Part 1: Charging, defines the attributes for the transfer of usage data from the Front End to the Back End. The contents of charge reports might vary between toll regimes, hence, attributes for all requirements are offered, ranging from attribute
