scope:

This part of ISO 17575 defines the format and semantics of thedata exchange between a Front End (OBE plus optional proxy) andcorresponding Back Ends in autonomous toll schemes. It defines thedata elements that are used to generate charge reports containinginformation about the road usage of a vehicle for certain timeintervals, sent from the Front End to the Back End. It also definesthe data that can be used to re-configure the ongoing process ofgathering charge relevant information in the Front End. The scopeis shown in Figure 1. The constitution of the charge report isdependent on configuration data that are assumed to be present inthe Front End. The assembly of charge reports can be configured foreach individual toll scheme according to local needs. Chargereports generated in accordance with this part of ISO 17575 areconsistent with the requirements derived from the architecturalconcept defined in ISO 17573:2010. The definitions in this part ofISO 17575 comprise ? reporting data, i.e. data for transferringroad usage data from Front End to Back End, including a responsefrom the Back End towards the Front End, ? data for supportingsecurity mechanisms, ? contract data, i.e. data for identifyingcontractually essential entities, ? road usage data, i.e. data forreporting the amount of road usage, ? account data for managing apayment account, ? versioning data, and ? compliance checking data,i.e. data imported from ISO 12813:2015, which are required incompliance checking communication. Annex A contains the data typespecifications using ASN.1 notation. The protocol implementationconformity statements (PICS) proforma are provided in Annex B.Annex C provides a graphical presentation of the structure of thedata elements described in Clause 7. Annex D provides informationon how this part of ISO 17575 can be used in EETS environment andhow the requirements that are specified in the EU-Decision 2009/750are addressed by this standard.