1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationDD CEN ISO/TS 17575-1:2010Electronic fee collection Application interface definitionfor autonomous systemsPart 1: Charging (ISO/TS 17575-1:2010)DD CEN ISO/TS 17575-1:2010Incorpor
2、ating corrigendum April 2013DD CEN ISO/TS 17575-1:2010 DRAFT FOR DEVELOPMENTNational forewordThis Draft for Development is the UK implementation of CEN ISO/TS 17575-1:2010, incorporating corrigendum April 2013.The start and finish of text introduced or altered by corrigendum is indicated in the text
3、 by tags. Text altered by ISO corrigendum April 2013 is indicated in the text by .This publication is not to be regarded as a British Standard.It is being issued in the Draft for Development series of publications and is of a provisional nature. It should be applied on this provisional basis, so tha
4、t information and experience of its practical application can be obtained.Comments arising from the use of this Draft for Development are requested so that UK experience can be reported to the international organization responsible for its conversion to an international standard. A review of this pu
5、blication will be initiated not later than 3 years after its publication by the international organization so that a decision can be taken on its status. Notification of the start of the review period will be made in an announcement in the appropriate issue of Update Standards.According to the repli
6、es received by the end of the review period, the responsible BSI Committee will decide whether to support the conversion into an international Standard, to extend the life of the Technical Specification or to withdraw it. Comments should be sent to the Secretary of the responsible BSI Technical Comm
7、ittee at British Standards House, 389 Chiswick High Road, London W4 4AL.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 publicati
8、on does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2013. Published by BSI Standards Limited 2013ISBN 978 0 580 82804 1ICS 03.220.20; 35.240.60Compliance with a British Standard cannot confer
9、immunity from legal obligations.This Draft for Development was published under the authority of the Standards Policy and Strategy Committee on 30 September 2010.Amendments/corrigenda issued since publicationDate Text affected30 June 2013 Implementation of ISO corrigendum April 2013TECHNICAL SPECIFIC
10、ATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN ISO/TS 17575-1 June 2010 ICS 03.220.20; 35.240.60 English Version Electronic fee collection - Application interface definition for autonomous systems - Part 1: Charging (ISO/TS 17575-1:2010)Perception du tlpage - Dfinition de linterface appli
11、cation pour les systmes autonomes - Partie 1: Imputation (ISO/TS 17575-1:2010) Elektronische Gebhrenerfassung - Anwendungsschnittstelle fr autonome Systeme - Teil 1: Gebhrenerhebung (ISO/TS 17575-1:2010) This Technical Specification (CEN/TS) was approved by CEN on 9 February 2010 for provisional app
12、lication. 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 converted into a European Standard. CEN members are required to announce the exis
13、tence 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) until the final decision about the possible conversion of the CEN/TS int
14、o 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, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania
15、, 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 2010 CEN All rights of exploitation in any form and by any means reserved wor
16、ldwide for CEN national Members. Ref. No. CEN ISO/TS 17575-1:2010: EDD CEN ISO/TS 17575-1:2010CEN ISO/TS 17575-1:2010 (E) 3 Foreword This document (CEN ISO/TS 17575-1:2010) has been prepared by Technical Committee CEN/TC 278 “Road transport and traffic telematics”, the secretariat of which is held b
17、y NEN, in collaboration with Technical Committee ISO/TC 204 “Intelligent transport systems“. 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 r
18、ights. 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 Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Icel
19、and, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. DD CEN ISO/TS 17575-1:2010ISO/TS 17575-1:2010(E) ISO 2010 All rights reserved iiiContents Page Foreword iv Introduction.v
20、1 Scope1 2 Normative references2 3 Terms and definitions .2 4 Abbreviations.4 5 Procedural requirements5 5.1 General .5 5.2 Charge report configuration.5 5.3 Charge report response6 6 Data elements 6 6.1 Introduction6 6.2 Reporting7 6.3 General .8 6.4 Contract9 6.5 Usage10 6.6 Account 13 6.7 Version
21、ing 14 6.8 Compliance Checking listOfCCCAttributes and CCCAttributes14 Annex A (normative) EFC data type specifications 15 Annex B (normative) PICS proforma 20 Annex C (informative) Hierarchical data structure illustration.22 Bibliography23 DD CEN ISO/TS 17575-1:2010ISO/TS 17575-1:2010(E) iv ISO 201
22、0 All rights reservedForeword ISO (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 interested in a
23、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 International Electrotechnical Commission
24、 (IEC) on all matters of electrotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical com
25、mittees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. In other circumstances, particularly when there is an urgent market requirement for such documents, a technical committee may decid
26、e to publish other types of document: an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical experts in an ISO working group and is accepted for publication if it is approved by more than 50 % of the members of the parent committee casting a vote; an ISO Technica
27、l Specification (ISO/TS) represents an agreement between the members of a technical committee and is accepted for publication if it is approved by 2/3 of the members of the committee casting a vote. An ISO/PAS or ISO/TS is reviewed after three years in order to decide whether it will be confirmed fo
28、r a further three years, revised to become an International Standard, or withdrawn. If the ISO/PAS or ISO/TS is confirmed, it is reviewed again after a further three years, at which time it must either be transformed into an International Standard or be withdrawn. Attention is drawn to the possibili
29、ty that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO/TS 17575-1 was prepared by the European Committee for Standardization (CEN) Technical Committee CEN/TC 278, Road transport and traff
30、ic telematics, in collaboration with Technical Committee ISO/TC 204, Intelligent transport systems, in accordance with the Agreement on technical cooperation between ISO and CEN (Vienna Agreement). ISO/TS 17575 consists of the following parts, under the general title Electronic fee collection Applic
31、ation interface definition for autonomous systems: Part 1: Charging Part 2: Communication and connection to the lower layers Part 3: Context data Part 4: Roaming DD CEN ISO/TS 17575-1:2010ISO/TS 17575-1:2010(E) ISO 2010 All rights reserved vIntroduction Autonomous systems This part of ISO/TS 17575 i
32、s part of a series of specifications 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 charging data for the use of road infrastructure including motorway tolls,
33、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-area technologies such as Global Navigation Satellite Systems (GNSS) an
34、d Cellular Communications Networks (CN). These EFC systems are referred to by a variety of names. Besides the terms autonomous systems and GNSS/CN systems, also the terms GPS/GSM systems, and wide-area charging systems are in use. Autonomous systems use satellite positioning, often combined with add
35、itional 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, the vehicle characteristics, the time of day and other
36、data that are relevant for describing road use, the tariff and ultimately the road usage fee are determined. Some of the strengths of the autonomous approach to electronic fee collection are its flexibility, allowing the implementation of almost all conceivable charging principles, and its independe
37、nce 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/TS 17575. Business architecture This part of ISO/TS 175
38、75 complies with the business architecture defined in the draft of the future International Standard 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 wi
39、th the Toll Charging role. See Figure 1. Service UsageServiceProvisionTollChargingInteroperabilityManagementFigure 1 The rolebased model underlying this Technical Specification DD CEN ISO/TS 17575-1:2010ISO/TS 17575-1:2010(E) vi ISO 2010 All rights reservedService Providers issue OBE to the users of
40、 the road infrastructure. Service Providers are responsible for operating the OBE that will record the amount 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 chargin
41、g data to several Toll Chargers, as well as each Toll Charger in general receives charging data from more than one Service Provider. Interoperability Management in Figure 1 comprises all specifications and activities that in common define and maintain a set of rules that govern the overall toll char
42、ging environment. Technical architecture 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 processi
43、ng functionality that can be realized either 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 resides on- or off-board. Also tariffication can be done with OBE tariff tables and processi
44、ng, or with an off-board component. Processing EquipmentFront End Back EndScope ofISO 17575OBEProxyRoad Usage DataContext DataFigure 2 Assumed technical architecture and interfaces The combined functionality of OBE and Proxy is denoted as Front End. A Front End implementation where processing is pre
45、dominately on OBE-side is 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 t
46、he gradual transition in the wedges in Figure 2. Both extremes of architectural choices 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 wi
47、de variety of optimizations 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. Location of the specification interface In
48、order to abstract from, and become independent of, these architectural implementation choices, the primary scope of ISO/TS 17575 is the data exchange between Front End and Back End (see the corresponding dotted line in Figure 2). For every toll regime, the Back End will send context data, i.e. a des
49、cription of the toll regime 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. DD CEN ISO/TS 17575-1:2010ISO/TS 17575-1:2010(E) ISO 2010 All rights reserved viiIt has to be noted also that the distribution of tasks and responsibilities between Service Provider and Toll Charger will vary individually. Depending on the local legal situation, Toll Chargers will require “thinner” or “thicker” data, and might or might not leave certain data pr
