One or more files are associated with this standard. After your purchase, you will find it (them) directly from your customer area, in the same place as the standard.
NF EN ISO 17575-1
Electronic fee collection - Application interface definition for autonomous systems - Part 1 : charging
ISO 17575-1:2016 defines the format and semantics of the data exchange between a Front End (OBE plus optional proxy) and corresponding Back Ends in autonomous toll schemes. It defines the data elements that are used to generate charge reports containing information about the road usage of a vehicle for certain time intervals, sent from the Front End to the Back End. It also defines the data that can be used to re-configure the ongoing process of gathering charge relevant information in the Front End. The scope is shown in Figure 1. The constitution of the charge report is dependent on configuration data that are assumed to be present in the Front End. The assembly of charge reports can be configured for each individual toll scheme according to local needs. Charge reports generated in accordance with this part of ISO 17575 are consistent with the requirements derived from the architectural concept defined in ISO 17573:2010. The definitions in ISO 17575-1:2016 comprise - reporting data, i.e. data for transferring road usage data from Front End to Back End, including a response from the Back End towards the Front End, - data for supporting security mechanisms, - contract data, i.e. data for identifying contractually essential entities, - road usage data, i.e. data for reporting the amount of road usage, - account data for managing a payment account, - versioning data, and - compliance checking data, i.e. data imported from ISO 12813:2015, which are required in compliance checking communication. Annex A contains the data type specifications using ASN.1 notation. The protocol implementation conformity statements (PICS) proforma are provided in Annex B. Annex C provides a graphical presentation of the structure of the data elements described in Clause 7. Annex D provides information on how this part of ISO 17575 can be used in EETS environment and how the requirements that are specified in the EU-Decision 2009/750 are addressed by this standard.
Collections
Thematics
Publication date
Number of pages
Reference
ICS Codes
Classification index
Print number
International kinship
European kinship
ISO 17575-1:2016 defines the format and semantics of the data exchange between a Front End (OBE plus optional proxy) and corresponding Back Ends in autonomous toll schemes. It defines the data elements that are used to generate charge reports containing information about the road usage of a vehicle for certain time intervals, sent from the Front End to the Back End. It also defines the data that can be used to re-configure the ongoing process of gathering charge relevant information in the Front End. The scope is shown in Figure 1.
The constitution of the charge report is dependent on configuration data that are assumed to be present in the Front End. The assembly of charge reports can be configured for each individual toll scheme according to local needs. Charge reports generated in accordance with this part of ISO 17575 are consistent with the requirements derived from the architectural concept defined in ISO 17573:2010.
The definitions in ISO 17575-1:2016 comprise
- reporting data, i.e. data for transferring road usage data from Front End to Back End, including a response from the Back End towards the Front End,
- data for supporting security mechanisms,
- contract data, i.e. data for identifying contractually essential entities,
- road usage data, i.e. data for reporting the amount of road usage,
- account data for managing a payment account,
- versioning data, and
- compliance checking data, i.e. data imported from ISO 12813:2015, which are required in compliance checking communication.
Annex A contains the data type specifications using ASN.1 notation.
The protocol implementation conformity statements (PICS) proforma are provided in Annex B.
Annex C provides a graphical presentation of the structure of the data elements described in Clause 7.
Annex D provides information on how this part of ISO 17575 can be used in EETS environment and how the requirements that are specified in the EU-Decision 2009/750 are addressed by this standard.
-
1 Domaine d'application
-
2 Références normatives
-
3 Termes et définitions
-
4 Abréviations
-
5 Considérations architecturales
-
6 Spécifications relatives aux procédures
-
7 Eléments de données
- Annexe A Spécifications des types de données
- Annexe B Formulaire de déclarations de conformité d'implémentation de protocole (PICS)
- Annexe C Illustration de la structure hiérarchique des données
- Annexe D Utilisation de la présente partie de l'ISO 17575 pour le SET
- Bibliographie
The Requirements department helps you quickly locate within the normative text:
- mandatory clauses to satisfy,
- non-essential but useful clauses to know, such as permissions and recommendations.
The identification of these types of clauses is based on the document “ISO / IEC Directives, Part 2 - Principles and rules of structure and drafting of ISO documents ”as well as on a constantly enriched list of verbal forms.
With Requirements, quickly access the main part of the normative text!
COBAZ is the simple and effective solution to meet the normative needs related to your activity, in France and abroad.
Available by subscription, CObaz is THE modular solution to compose according to your needs today and tomorrow. Quickly discover CObaz!
Request your free, no-obligation live demo
I discover COBAZ