1、 Reference numberISO/TS 17575-2:2010(E)ISO 2010TECHNICAL SPECIFICATION ISO/TS17575-2First edition2010-06-15Electronic fee collection Application interface definition for autonomous systems Part 2: Communication and connection to the lower layers Perception du tlpage Dfinition de linterface dapplicat
2、ion pour les systmes autonomes Partie 2: Communications et connexions aux couches plus basses ISO/TS 17575-2:2010(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typeface
3、s which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Syste
4、ms Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely e
5、vent that a problem relating to it is found, please inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO 2010 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or m
6、echanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www
7、.iso.org Published in Switzerland ii ISO 2010 All rights reservedISO/TS 17575-2:2010(E) ISO 2010 All rights reserved iiiContents Page Foreword iv Introduction.v 1 Scope1 2 Normative references1 3 Terms and definitions .1 4 Abbreviations.3 5 EFC Front End communication architecture3 5.1 General .3 5.
8、2 Relations to the overall EFC architecture.4 6 Initialize transactions4 6.1 General .4 6.2 Addressing requested parts of a hierarchical data element structure 5 6.3 Identifying payloads for transmission 5 7 EFC communication services (functions).5 7.1 General concept 5 7.2 Initialization phase 6 7.
9、3 Point-to-point communication service primitives7 7.4 Session ending 8 7.5 Session failure .8 7.6 Security considerations8 7.7 Media selection options8 8 The use of a communication stack8 8.1 General .8 8.2 Requirements on a underlying communication technology.9 8.3 Mobile terminated calls.9 Annex
10、A (normative) Abstract API definition.10 Annex B (normative) PICS proforma 15 Annex C (informative) API requirements 20 Annex D (informative) Examples of definitions for appropriate languages21 Annex E (informative) Example of message flow 24 Bibliography25 ISO/TS 17575-2:2010(E) iv ISO 2010 All rig
11、hts 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 subject f
12、or 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 (IEC) on
13、 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 committees a
14、re 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 decide to publ
15、ish 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 Technical Specifi
16、cation (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 for a furth
17、er 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 possibility that s
18、ome 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-2 was prepared by the European Committee for Standardization (CEN) Technical Committee CEN/TC 278, Road transport and traffic telema
19、tics, 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 Application int
20、erface definition for autonomous systems: Part 1: Charging Part 2: Communication and connection to the lower layers Part 3: Context data Part 4: Roaming ISO/TS 17575-2:2010(E) ISO 2010 All rights reserved vIntroduction Autonomous systems This part of ISO/TS 17575 is part of a series of specification
21、s 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, zone-based fees in urban areas, tol
22、ls 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) and Cellular Communications Networks
23、(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 additional sensor technologies such as
24、 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 data that are relevant for describi
25、ng 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 independence from local infrastructure, ther
26、eby 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 17575 complies with the business archi
27、tecture 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 with the Toll Charging role. See Figu
28、re 1. Service UsageServiceProvisionTollChargingInteroperabilityManagementFigure 1 The rolebased model underlying this Technical Specification ISO/TS 17575-2:2010(E) vi ISO 2010 All rights reservedService Providers issue OBE to the users of the road infrastructure. Service Providers are responsible f
29、or 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 charging data to several Toll Chargers, as well as each Toll Charger
30、 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 charging environment. Technical architecture The technical arch
31、itecture 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 either on- or off-boa
32、rd 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 tariffication can be done with OBE tariff tables and processing, or with an off-board component. Processing EquipmentFron
33、t 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 predominately on OBE-side is known as a smart client (or intell
34、igent 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 the wedges in Figure 2. Both extrem
35、es 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 wide variety of optimizations of the transfer of localization
36、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 order to abstract from, and become independent of, these arc
37、hitectural 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 description of the toll regime in terms of charged objects, cha
38、rging rules and, if required, the tariff scheme to the Front End, and will receive usage data from the Front End. ISO/TS 17575-2: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 ind
39、ividually. Depending on 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/TS 17575 may be useful on several interfaces. ISO/TS 17575 also provides for
40、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. The parts of ISO/TS 17575 Part 1: Charging, defines the attr
41、ibutes for the transfer of usage data from the Front End to the Back End. The required attributes will differ from one Toll Charger to another, hence, attributes for all requirements are offered, ranging from attributes for raw localization data, for map-matched geographic objects and for completely
42、 priced toll transactions. Part 2: Communication and connection to lower layers, defines basic communication services for data transfer over the OBE air-link or between Front End and Back End. Part 3: Context Data, defines the data to be used for a description of individual charging systems in terms
43、 of charged geographical objects and charging and reporting rules. For every Toll Chargers system, attributes as defined in part 3 are used to transfer data to the Front End in order to instruct it which data to collect and report. Part 4: Roaming, defines the functional details and data elements re
44、quired to operate more than one EFC regime in parallel. The domains of these EFC regimes may or may not overlap. The charge rules of different overlapping EFC regimes can be linked, i.e. they may include rules that an area pricing scheme will not be charged if an overlapping toll road is used and al
45、ready paid for. Figure 3 Scope of ISO/TS 17575 ISO/TS 17575-2:2010(E) viii ISO 2010 All rights reservedApplicatory needs covered by ISO/TS 17575 The parts of ISO/TS 17575 are compliant with the architecture defined in the future International Standard ISO 17573. The parts of ISO/TS 17575 support cha
46、rges for use of road sections (including bridges, tunnels, passes, etc.), passage of cordons (entry/exit) and use of infrastructure within an area (distance, time). The parts of ISO/TS 17575 support fee collection based on units of distance or duration, and based on occurrence of events. The parts o
47、f ISO/TS 17575 support modulation of fees by vehicle category, road category, time of usage and contract type (e.g. exempt vehicles, special tariff vehicles, etc.). The parts of ISO/TS 17575 support limiting of fees by a defined maximum per period of usage. The parts of ISO/TS 17575 support fees wit
48、h different legal status (e.g. public tax, private toll). The parts of ISO/TS 17575 support differing requirements of different Toll Chargers, especially in terms of geographic domain and context descriptions, contents and frequency of charge reports, feedback to the driver (e.g. green or red light)
49、, and provision of additional detailed data on request, e.g. for settling of disputes. The parts of ISO/TS 17575 support overlapping geographic toll domains. The parts of ISO/TS 17575 support adaptations to changes in tolled infrastructure, tariffs, and participating regimes. The parts of ISO/TS 17575 support the provision of trust guarantees by the Service Provider to the Toll Charger for the data originated from the Front End. TECHNICAL SPECIFICATION ISO/TS 17575-2:2010(E) ISO 2010
