NF EN ISO 12855
Electronic fee collection - Information exchange between service provision and toll charging
ISO 12855:2011 specifies the interfaces between electronic fee collection (EFC) systems for vehicle related transport services, e.g. road user charging, parking and access control; it does not cover interfaces for EFC systems for public transport; an EFC system can include any EFC system, e.g. also systems automatically reading licence plate numbers of vehicles passing a toll point; an exchange of information between the central equipment of the two roles of service provision and toll charging, e.g. charging related data (toll declarations, billing details), administrative data, and confirmation data; transfer mechanisms and supporting functions; information objects, data syntax and semantics; examples of data interchanges. ISO 12855:2011 supports any toll service and any technology used for charging. It is defined as a toolbox standard of transactions and messages which can be used for the assigned purpose. The detailed definitions of mandatory and optional elements in a real implementation are defined elsewhere. It does not define all communication sequences, communication stacks and timings.
ISO 12855:2011 specifies
- the interfaces between electronic fee collection (EFC) systems for vehicle related transport services, e.g. road user charging, parking and access control; it does not cover interfaces for EFC systems for public transport; an EFC system can include any EFC system, e.g. also systems automatically reading licence plate numbers of vehicles passing a toll point;
- an exchange of information between the central equipment of the two roles of service provision and toll charging, e.g.
- charging related data (toll declarations, billing details),
- administrative data, and
- confirmation data;
- transfer mechanisms and supporting functions;
- information objects, data syntax and semantics;
- examples of data interchanges.
ISO 12855:2011 supports any toll service and any technology used for charging.
It is defined as a toolbox standard of transactions and messages which can be used for the assigned purpose. The detailed definitions of mandatory and optional elements in a real implementation are defined elsewhere. It does not define all communication sequences, communication stacks and timings.
<p>ISO 12855:2015 specifies</p> <p>- the interfaces between electronic fee collection (EFC) systems for vehicle related transport services, e.g. road user charging, parking and access control; it does not cover interfaces for EFC systems for public transport; an EFC system can include any EFC system, e.g. including systems that automatically read licence plate numbers of vehicles passing a toll point,</p> <p>- an exchange of information between the central equipment of the two roles of service provision and toll charging, e.g.</p> <ul> <li>- charging related data (toll declarations, billing details),</li> <li>- administrative data, and</li> <li>- confirmation data,</li> </ul> <p>- transfer mechanisms and supporting functions,</p> <p>- information objects, data syntax and semantics,</p> <p>- examples of data interchanges (see Annex C and Annex D), and</p> <p>- an example on how to use this International Standard for the European Electronic Tolling Service (EETS) (see Annex F).</p> <p>ISO 12855:2015 is applicable for any toll service and any technology used for charging. </p> <p>It is defined as a toolbox standard of transactions and Application Protocol Data Units (APDUs), which can be used for the assigned purpose. The detailed definitions of mandatory and optional elements in a real implementation are defined elsewhere. It does not define all communication sequences, communication stacks and timings.</p> <p>The scope of ISO 12855:2015 is illustrated in Figure 2. The data types and associated coding related to the data elements described in Clause 6 are defined in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824‑1.</p>
- Avant-proposiv
- Introductionv
-
1 Domaine d'application1
-
2 Références normatives2
-
3 Termes et définitions3
-
4 Symboles et abréviations7
-
5 Concept architectural8
-
5.1 Principaux rôles dans l'environnement de perception du péage8
-
5.2 Échange d'informations entre la perception du péage et la prestation9
-
6 Spécification fonctionnelle par objets (Computational specification)17
-
6.1 Vue d'ensemble17
-
6.2 Unités de données de protocole d'application21
-
6.3 Structure de données RequestADU23
-
6.4 Structure de données AcknowledgeADU23
-
6.5 Structure de données StatusADU24
-
6.6 Structure de données TrustObjectsADU25
-
6.7 Structure de données EFCContextDataADU25
-
6.8 Structure de données ExceptionListADU26
-
6.9 Structure de données ReportAbnormalOBEADU27
-
6.10 Structure de données RetrieveTollDeclarationADU27
-
6.11 Structure de données Toll DeclarationADU28
-
6.12 Structure de données BillingDetailsADU28
-
6.13 Structure de données PaymentClaimADU34
-
6.14 Structure de données RetrieveUserDetailsADU34
-
6.15 Structure de données ProvideUserDetailsADU35
-
6.16 Structure de données RetrieveCCCEventADU36
-
6.17 Structure de données ReportCCCEventADU36
-
6.18 Structure de données Report QA37
-
7 Mécanismes de transfert et fonctions de support38
-
7.1 Mécanismes de transfert38
-
7.2 Fonctions de support38
- Annexe A (normative) Spécifications des types de données39
- Annexe B (normative) Déclaration de conformité d'implémentation de protocole56
- Annexe C (informative) Comment utiliser les attributs de données de réseau routier au format GDF69
- Annexe D (informative) Exemple de processus de contrôle sanction appliquant des échanges de messages normalisés72
- Annexe E (informative) Flux de données dans un domaine de péage78
- Bibliographie81
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