This document specifies: — the interfaces between electronic fee collection (EFC) back-office systems for vehicle-related transport services, e.g. road user charging, parking and access control; — an exchange of information between the back end system 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. This document is applicable for any vehicle-related toll service and any technology used for charging. 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. This document specifies basic protocol mechanisms over which implementations can specify and perform complex transfers (transactions). This document does not specify, amongst others: — any communication between toll charger (TC) or toll service provider (TSP) with any other involved party; — any communication between elements of the TC and the TSP that is not part of the back-office communication; — interfaces for EFC systems for public transport; — any complex transfers (transactions), i.e. sequences of inter-related application data units (ADUs) that can possibly involve several application protocol data unit (APDU) exchanges; — processes regarding payments and exchanges of fiscal, commercial or legal accounting documents; and — definitions of service communication channels, protocols and service primitives to transfer the APDUs.
This document specifies:
— the interfaces between electronic fee collection (EFC) back-office systems for vehicle-related transport services, e.g. road user charging, parking and access control;
— an exchange of information between the back end system 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.
This document is applicable for any vehicle-related toll service and any technology used for charging.
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.
This document specifies basic protocol mechanisms over which implementations can specify and perform complex transfers (transactions).
This document does not specify, amongst others:
— any communication between toll charger (TC) or toll service provider (TSP) with any other involved party;
— any communication between elements of the TC and the TSP that is not part of the back-office communication;
— interfaces for EFC systems for public transport;
— any complex transfers (transactions), i.e. sequences of inter-related application data units (ADUs) that can possibly involve several application protocol data unit (APDU) exchanges;
— processes regarding payments and exchanges of fiscal, commercial or legal accounting documents; and
— definitions of service communication channels, protocols and service primitives to transfer the APDUs.
<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>
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