Transport

 ISO 14819-1 describes the ALERT-C protocol concept and message structure used to achieve densely coded messages to be carried in the RDS-TMC feature. This document specifies the ‘Events List’ to be used in coding those messages.

This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of semantics are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824-1. This document defines:

—    ASN.1 (data) types within the field of EFC;

—    ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC.

This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.

This document defines the architecture of electronic fee collection (EFC) system environments, in which a customer with one contract can use a vehicle in a variety of toll domains with a different toll charger (TC) for each domain.

EFC systems conforming to this document can be used for various purposes including road (network) tolling, area tolling, collecting fees for the usage of bridges, tunnels, ferries, for access or for parking. From a technical point of view the considered toll systems can identify vehicles subject to tolling by means of electronic OBE in a vehicle or by other means that are image-based (e.g. automatic number plate recognition, ANPR).

From a process point of view the architectural description focuses on toll determination, toll charging, 

provision of toll service to the user, and the associated enforcement measures. The actual collection of the toll, i.e. collecting payments, is outside of the scope of this document.

The architecture in this document is defined with no more details than required for an overall overview, a common language, an identification of the need for and interactions among other standards, and the drafting of these standards.

This document as a whole provides:

— the enterprise view on the architecture, which is concerned with the purpose, scope and policies 

governing the activities of the specified system within the organization of which it is a part;

— the terms and definitions specific to this standard, in addition to those provided in ISO/FDIS 17573-2;

— a decomposition of the EFC systems environment into its main enterprise objects;

— the roles and responsibilities of the main actors. This document does not impose that all roles perform all indicated responsibilities. It should also be clear that the responsibilities of a role can be shared between two or more actors. Mandating the performance of certain responsibilities is the task of standards derived from this architecture;

— identification of the provided services by means of action diagrams that underline the needed 

standardized exchanges;

— identification of the interoperability interfaces for EFC systems, in specialized standards.