NF EN ISO 12855

NF EN ISO 12855

May 2013
Standard Cancelled

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.

View the extract
Main informations

Collections

National standards and national normative documents

Thematics

Management et performance

Publication date

May 2013

Number of pages

91 p.

Reference

NF EN ISO 12855

ICS Codes

03.220.20   Road transport
35.240.60   IT applications in transport

Classification index

P99-413

Print number

1 - 24/04/2013

International kinship

European kinship

EN ISO 12855:2012
Sumary
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.

Standard replaced by (1)
NF EN ISO 12855
March 2016
Standard Cancelled
Electronic fee collection - Information exchange between service provision and toll charging

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

Table of contents
View the extract
  • Avant-propos
    iv
  • Introduction
    v
  • 1 Domaine d'application
    1
  • 2 Références normatives
    2
  • 3 Termes et définitions
    3
  • 4 Symboles et abréviations
    7
  • 5 Concept architectural
    8
  • 5.1 Principaux rôles dans l'environnement de perception du péage
    8
  • 5.2 Échange d'informations entre la perception du péage et la prestation
    9
  • 6 Spécification fonctionnelle par objets (Computational specification)
    17
  • 6.1 Vue d'ensemble
    17
  • 6.2 Unités de données de protocole d'application
    21
  • 6.3 Structure de données RequestADU
    23
  • 6.4 Structure de données AcknowledgeADU
    23
  • 6.5 Structure de données StatusADU
    24
  • 6.6 Structure de données TrustObjectsADU
    25
  • 6.7 Structure de données EFCContextDataADU
    25
  • 6.8 Structure de données ExceptionListADU
    26
  • 6.9 Structure de données ReportAbnormalOBEADU
    27
  • 6.10 Structure de données RetrieveTollDeclarationADU
    27
  • 6.11 Structure de données Toll DeclarationADU
    28
  • 6.12 Structure de données BillingDetailsADU
    28
  • 6.13 Structure de données PaymentClaimADU
    34
  • 6.14 Structure de données RetrieveUserDetailsADU
    34
  • 6.15 Structure de données ProvideUserDetailsADU
    35
  • 6.16 Structure de données RetrieveCCCEventADU
    36
  • 6.17 Structure de données ReportCCCEventADU
    36
  • 6.18 Structure de données Report QA
    37
  • 7 Mécanismes de transfert et fonctions de support
    38
  • 7.1 Mécanismes de transfert
    38
  • 7.2 Fonctions de support
    38
  • Annexe A (normative) Spécifications des types de données
    39
  • Annexe B (normative) Déclaration de conformité d'implémentation de protocole
    56
  • Annexe C (informative) Comment utiliser les attributs de données de réseau routier au format GDF
    69
  • Annexe D (informative) Exemple de processus de contrôle sanction appliquant des échanges de messages normalisés
    72
  • Annexe E (informative) Flux de données dans un domaine de péage
    78
  • Bibliographie
    81
ZOOM ON ... the Requirements department
To comply with a standard, you need to quickly understand its issues in order to determine its impact on your activity.

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!

With Requirements, quickly access the main part of the normative text!
Need to identify, monitor and decipher standards?

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