1、 Reference numberISO/TS 17575-3:2011(E)ISO 2011TECHNICAL SPECIFICATION ISO/TS17575-3First edition2011-04-Electronic fee collection Application interface definition for autonomous systems Part 3: Context data Perception du tlpage Dfinition de linterface dapplication pour les systmes autonomes Partie
2、3: Donnes du contexte 15ISO/TS 17575-3:2011(E) COPYRIGHT PROTECTED DOCUMENT ISO 2011 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 mechanical, including photocopying and microfilm, without permiss
3、ion 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.iso.org Published in Switzerland ii ISO 2011 All rights reserve
4、dISO/TS 17575-3:2011(E) ISO 2011 All rights reserved iiiContents Page Foreword iv Introduction.v 1 Scope1 2 Normative references1 3 Terms and definitions .2 4 Abbreviated terms.5 5 General concept and overview 5 6 Procedural requirements and encoding rules7 6.1 Communication services7 6.2 Version an
5、d validity handling 7 6.3 Encoding rules.7 7 Application data units.8 7.1 Application data unit structure 8 7.2 Application data unit header 8 7.3 Application data unit body .9 8 EFC Attributes .9 8.1 Rules with respect to support of context data .9 8.2 Attributes and data sets10 8.3 EFC attributes
6、data catalogue10 8.3.1 General .10 8.3.2 Data set “Context Overview” .11 8.3.3 Data group “Tariff Information” .12 8.3.4 Data set “Context Layout”28 8.3.5 Data set “Reporting rules” .38 Annex A (normative) EFC data type specifications 48 Annex B (normative) PICS proforma for the attributes.63 Annex
7、C (informative) How to use context data defining the properties of an EFC regime .82 Annex D (informative) Examples using EFC context data for scheme definitions 87 Bibliography91 ISO/TS 17575-3:2011(E) iv ISO 2011 All rights reservedForeword ISO (the International Organization for Standardization)
8、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 for which a technical committee has been established has the right to be repres
9、ented 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 all matters of electrotechnical standardization. International Standards are
10、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 are circulated to the member bodies for voting. Publication as an International
11、 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 publish other types of normative document: an ISO Publicly Available Specification
12、 (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 Specification (ISO/TS) repres ents an agreement between the members of a te
13、chnical 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 further three years, revised to become an International Standard, or wit
14、hdrawn. 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. ISO/TS 17575-3 was prepared by the European Committee for Standardization (CEN) Technical Committee CEN/TC 278,
15、 Road transport and traffic 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 Electro
16、nic fee collection Application interface 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-3:2011(E) ISO 2011 All rights reserved vIntroduction Autonomous systems This part of ISO/TS 17575 is
17、 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, z
18、one-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
19、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 addi
20、tional 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 d
21、ata 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 independen
22、ce 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 1757
23、5 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 Toll Charging role. See Figure 1. Figure
24、1 The rolebased model underlying this Technical Specification Service UsageService Provision Interoperability Management Toll ChargingISO/TS 17575-3:2011(E) vi ISO 2011 All rights reservedService Providers issue OBE to the users of the road infrastructure. Service Providers are responsible for opera
25、ting 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 in gene
26、ral 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 architecture o
27、f 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-board is map-
28、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 processing, or with an off-board component. Processing EquipmentFront End Bac
29、k 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 intelligent cli
30、ent, 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 extremes of arc
31、hitectural 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 data betw
32、een 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 architectura
33、l 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, charging rul
34、es and, if required, the tariff scheme to the Front End, and will receive usage data from the Front End. ISO/TS 17575-3:2011(E) ISO 2011 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
35、. Depending on 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 basic media-i
36、ndependent 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 attributes for th
37、e 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 priced toll
38、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 of charged g
39、eographical 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 required to ope
40、rate 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 already paid fo
41、r. Figure 3 Scope of ISO/TS 17575 ISO/TS 17575-3:2011(E) viii ISO 2011 All rights reservedIn ISO/TS 17575, context data is the description of the properties of a single instance of an EFC context. This single instance of an EFC context operates according to one of the basic tolling principles such a
42、s road sectioned tolling, area pricing according to travelled distance, area pricing according to the time, cordon pricing. EFC context data comprise a set of rules for charging, including the description of the charged network, the charging principles, the liable vehicles and a definition of the re
43、quired contents of the charge report. This set of rules is defined individually for each EFC context according to local needs. This part of ISO/TS 17575 contains the definitions of the above listed type of data. Only a Front End configured with the context data necessary for the respective EFC conte
44、xt is able to be used for charging processes. The following data definitions are in this part of ISO/TS 17575: data providing toll context overview information; data providing tariff information (this includes definitions of required tariff determinants like vehicle parameters, time classes and othe
45、rs); data providing context layout information; data providing reporting rules information. In case one EFC domain cannot be described with a single set of context data, several of these context data are used. ISO/TS 17575-4 defines the parallel operation of more than one EFC context and how to hand
46、le interdependencies. Applicatory needs covered by ISO/TS 17575 The parts of ISO/TS 17575 are compliant with the architecture defined in ISO 17573. The parts of ISO/TS 17575 support charges for use of road sections (including bridges, tunnels, passes, etc.), passage of cordons (entry/exit), and use
47、of infrastructure within an area (distance, time). The parts of ISO/TS 17575 support fee collection bas ed on units of distance or duration, and based on occurrence of events. The parts of ISO/TS 17575 support modulation of fees by vehicle categor y, road category, time of usage, and contract type (
48、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 with diffe rent legal status (e.g. public tax, private toll). The parts of ISO/TS 17575 support differing requireme
49、nts of different Toll Chargers, especially in terms of geographic domain and context descriptions, contents and frequency of charge reports, ISO/TS 17575-3:2011(E) ISO 2011 All rights reserved ix feedback to the driver (e.g. green or red light), 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 infrastruct
