NF EN ISO 12855

<div id="MathJax_Message" style="display: none;"></div> <p>ISO 12855:2011 specifies</p> <ul> <li>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;</li> <li>an exchange of information between the central equipment of the two roles of service provision and toll charging, e.g. <ul> <li>charging related data (toll declarations, billing details),</li> <li>administrative data, and</li> <li>confirmation data;</li> </ul> </li> <li>transfer mechanisms and supporting functions;</li> <li>information objects, data syntax and semantics;</li> <li>examples of data interchanges.</li> </ul> <p>ISO 12855:2011 supports any toll service and any technology used for charging.</p> <p>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>

<p>This document specifies:</p> <p>—    the interfaces between electronic fee collection (EFC) back-office systems for vehicle-related transport services, e.g. road user charging, parking and access control;</p> <p>—    an exchange of information between the back end system of the two roles of service provision and toll charging, e.g.:</p> <p>—    charging-related data (toll declarations, billing details),</p> <p>—    administrative data, and</p> <p>—    confirmation data;</p> <p>—    transfer mechanisms and supporting functions;</p> <p>—    information objects, data syntax and semantics.</p> <p>This document is applicable for any vehicle-related toll service and any technology used for charging.</p> <p>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> <p>This document specifies basic protocol mechanisms over which implementations can specify and perform complex transfers (transactions).</p> <p>This document does not specify, amongst others:</p> <p>—    any communication between toll charger (TC) or toll service provider (TSP) with any other involved party;</p> <p>—    any communication between elements of the TC and the TSP that is not part of the back-office communication;</p> <p>—    interfaces for EFC systems for public transport;</p> <p>—    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;</p> <p>—    processes regarding payments and exchanges of fiscal, commercial or legal accounting documents; and</p> <p>—    definitions of service communication channels, protocols and service primitives to transfer the APDUs.</p>