EN ISO TS 17575-4-2011 en Electronic fee collection - Application interface definition for autonomous systems - Part 4 Roaming《电子收费 自控系统的应用程序接口定义 第4部分 数据漫游》.pdf

《EN ISO TS 17575-4-2011 en Electronic fee collection - Application interface definition for autonomous systems - Part 4 Roaming《电子收费 自控系统的应用程序接口定义 第4部分 数据漫游》.pdf》由会员分享，可在线阅读，更多相关《EN ISO TS 17575-4-2011 en Electronic fee collection - Application interface definition for autonomous systems - Part 4 Roaming《电子收费 自控系统的应用程序接口定义 第4部分 数据漫游》.pdf（40页珍藏版）》请在麦多课文档分享上搜索。

1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationDD CEN ISO/TS 17575-4:2011Electronic fee collection Application interfacedefinition for autonomous systemsPart 4: Roaming (ISO/TS 17575-4:2011)DD CEN ISO/TS 17575-4:2011 DRAFT FO

2、R DEVELOPMENTNational forewordThis Draft for Development is the UK implementation of CEN ISO/TS 17575-4:2011.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 thi

3、s provisional basis, so that 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 st

4、andard. A review of this publication will be initiated not later than 3 years after its publication by the inter-national 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 Stan

5、dards.According to the replies 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 re

6、sponsible BSI Technical Committee at British Standards House, 389 Chiswick High Road, London W4 4AL.The UK participation in its preparation was entrusted to Technical Committee EPL/278, Road transport informatics.A list of organizations represented on this committee can be obtained on request to its

7、 secretary.This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. BSI 2011ISBN 978 0 580 68033 5ICS 03.220.20; 35.240.60Compliance with a British Standard cannot confer immunity from legal obligations.This Draft for

8、 Development was published under the authority of the Standards Policy and Strategy Committee on 31 May 2011.Amendments issued since publicationDate Text affectedTECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN ISO/TS 17575-4 April 2011 ICS 03.220.20; 35.240.60 English Ver

9、sion Electronic fee collection - Application interface definition for autonomous systems - Part 4: Roaming (ISO/TS 17575-4:2011)Perception du tlpage - Dfinition de linterface dapplication pour les systmes autonomes - Partie 4: Itinrance (ISO/TS 17575-4:2011) Elektronische Gebhrenerfassung - Anwendun

10、gsschnittstelle fr autonome Systeme - Teil 4: Roaming (ISO/TS 17575-4:2011) This Technical Specification (CEN/TS) was approved by CEN on 18 October 2010 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

11、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 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

12、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 into an EN is reached. CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic

13、, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NOR

14、MALISATION EUROPISCHES KOMITEE FR NORMUNG Management Centre: Avenue Marnix 17, B-1000 Brussels 2011 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN ISO/TS 17575-4:2011: EDD CEN ISO/TS 17575-4:2011 CEN ISO/TS 17575-4:2011 (E) 3 For

15、eword This document (CEN ISO/TS 17575-4:2011) has been prepared by Technical Committee CEN/TC 278 “Road transport and traffic telematics” the secretariat of which is held by NEN, in collaboration with Technical Committee ISO/TC 204 “Intelligent transport systems“. Attention is drawn to the possibili

16、ty 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. According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bo

17、und to announce this Technical Specification: 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, Slovakia, Slovenia, S

18、pain, Sweden, Switzerland and the United Kingdom.DD CEN ISO/TS 17575-4:2011ISO/TS 17575-4:2011(E) ISO 2011 All rights reserved iiiContents Page Foreword .iv Introductionv 1 Scope.1 2 Normative References1 3 Terms and definitions 1 4 Abbreviated terms4 5 Basic concept .4 5.1 General 4 5.2 Overview5 6

19、 Data elements .6 6.1 General 6 6.2 Elements of the roaming rules attribute 7 6.2.1 The roaming rule identifier 7 6.2.2 The list of relevant EFC contexts7 6.2.3 The list of EFC contexts which are grouped using a single charge report9 6.2.4 House keeping data elements.9 7 Communicating the roaming ru

20、les attribute10 7.1 Requesting an update of the roaming rules attribute.10 7.2 Responding to a roaming rules download request 10 7.3 ASN1 coding rules10 Annex A (normative) EFC data type specifications 11 Annex B (normative) PICS proforma 13 Annex C (informative) How to assemble and use roaming data

21、22 Bibliography.24 DD CEN ISO/TS 17575-4:2011ISO/TS 17575-4:2011(E) iv ISO 2011 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 c

22、arried 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 represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the wor

23、k. ISO collaborates closely with the International Electrotechnical Commission (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 Inter

24、national Standards. Draft International Standards adopted by the technical committees 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

25、 urgent market requirement for such documents, a technical committee may decide 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 th

26、an 50 % of the members of the parent committee casting a vote; an ISO Technical 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

27、 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 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

28、an International Standard or be withdrawn. Attention is drawn to the possibility 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-4 was prepared by the European Committee for

29、Standardization (CEN) Technical Committee CEN/TC 278, 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

30、 the following parts, under the general title Electronic 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 DD CEN ISO/TS 17575-4:2011ISO/TS 17575-4:2011(E) ISO 2011 Al

31、l rights reserved vIntroduction Autonomous systems This part of ISO/TS 17575 is part of a series of four 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

32、collect charging 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 em

33、ploying wide-area technologies such as Global Navigation Satellite Systems (GNSS) and 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 syste

34、ms are in use. Autonomous systems 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 area

35、s. From the charged objects, the 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. Some of the strengths of the autonomous approach to electronic fee collection are its flexibility, allowing

36、 the implementation of almost all conceivable 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

37、aim and justification of ISO/TS 17575. Business architecture This part of ISO/TS 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 To

38、ll Charger is the actor associated with the Toll Charging role. See Figure 1. Figure 1 The rolebased model underlying this Technical Specification Service UsageService Provision Interoperability Management Toll ChargingDD CEN ISO/TS 17575-4:2011ISO/TS 17575-4:2011(E) vi ISO 2011 All rights reservedS

39、ervice Providers issue OBE to the users of 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 gener

40、al, each Service Provider delivers charging 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

41、of rules that govern the overall toll charging 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

42、 component (Proxy). An example of processing 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 b

43、e done with OBE tariff tables and processing, 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

44、End implementation where processing is predominately 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 “thic

45、k” extremes are possible, as depicted by the 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 c

46、lient OBE, manufacturers might devise a wide 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. L

47、ocation of the specification interface In 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 B

48、ack End will send context data, i.e. a description 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-4:2011ISO/TS 17575-4:2011(E) ISO 2011 All rights reserved viiIt

49、has to be noted also that the distribution of tasks and responsibilities between Service Provider and Toll Charger will vary individually. 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-independent communication services that may be used for communication between Front End and Back End,