TSE - TS EN ISO 17575-3
Electronic fee collection - Application interface definition for autonomous systems - Part 3: Context data
| Organization: | TSE |
| Publication Date: | 24 March 2016 |
| Status: | active |
| ICS Code (Road transport): | 03.220.20 |
| ICS Code (IT applications in transport): | 35.240.60 |
scope:
This part of ISO 17575 defines the content, semantics and formatof the data exchange between a Front End (OBE plus optional proxy)and the corresponding Back End in autonomous toll systems. Itdefines the data elements used to specify and describe the tollcontext details. Context data are transmitted from the Back End tothe Front End to configure it for the charging processes of theassociated toll context. In ISO 17575, context data is thedescription of the properties of a single instance of an electronicfee collection (EFC) context. This single instance of an EFCcontext operates according to one of the basic tolling principlessuch as ? road section charging, ? area charging (according totravelled distance or duration of time), and ? cordon charging. EFCcontext data comprise a set of rules for charging, including thedescription of the charged network, the charging principles, theliable vehicles and a definition of the required contents of thecharge report. This set of rules is defined individually for eachEFC context according to local needs. The following data andassociated procedures are defined in this part of ISO 17575: ? dataproviding toll context overview information; ? data providingtariff information (including definitions of required tariffdeterminants such as vehicle parameters, time classe, etc.); ? dataproviding context layout information; ? data providing reportingrules information. This part of ISO 17575 also provides therequired definitions and data specifications to be applied when onesingle toll context is spilt inot more than one toll contextpartitions. This is applicable to cases where one EFC scheme andthe rules applied cannot be described with a single set of contextdata. Annex A provides the data type specification using ASN.1notation. The protocol implementation conformity statements (PICS)proforma are provided in Annex B. Annex C provides a graphicalpresentatio
Document History