M/338 - Electronic road toll systems

This document specifies the test suite structure (TSS) and test purposes (TPs) for evaluation of on-board equipment (OBE) and roadside equipment (RSE) to EN 15509.
Normative Annex A presents the test purposes for the OBE.
Normative Annex B presents the test purposes for the RSE.
Normative Annex C provides the protocol conformance test report (PCTR) proforma for OBE.
Normative Annex D provides the PCTR proforma for RSE.

This document specifies the test suite structure (TSS) and test purposes (TPs) for evaluation of on-board equipment (OBE) and roadside equipment (RSE) to EN 15509.
Normative Annex A presents the test purposes for the OBE.
Normative Annex B presents the test purposes for the RSE.
Normative Annex C provides the protocol conformance test report (PCTR) proforma for OBE.
Normative Annex D provides the PCTR proforma for RSE.

This document defines an application interface definition by selecting suitable options from the base standard EN ISO 12855:2021. Furthermore, it defines transfer mechanisms and supporting functions to ensure the interoperability between Toll Chargers and Toll Service Providers.
This document covers:
—   exchange of information between the central equipment associated with the two roles service provision and toll charging, e.g.:
o   charging related data (exception lists, toll declarations, billing details, payment claims);
o   administrative data (trust objects, EFC context data, contact details for enforcement, etc.);
o   confirmation data.
—   transfer mechanisms and supporting functions;
—   semantics of data elements;
—   restrictions on parameters and their values
—   implementation conformance statement proforma, in an Annex, as a basis for assessment of conformity to this document;
—   an Interoperability statement proforma, in an Annex, as a basis for assessment of transactional interoperability of two technical implementations;
—   a web service definition, in an Annex, for the use of web services as communication technology.
The implementation of the underlying back office systems and their business processes is not covered.

This document defines an application interface definition by selecting suitable options from the base standard EN ISO 12855:2021. Furthermore, it defines transfer mechanisms and supporting functions to ensure the interoperability between Toll Chargers and Toll Service Providers.
This document covers:
—   exchange of information between the central equipment associated with the two roles service provision and toll charging, e.g.:
o   charging related data (exception lists, toll declarations, billing details, payment claims);
o   administrative data (trust objects, EFC context data, contact details for enforcement, etc.);
o   confirmation data.
—   transfer mechanisms and supporting functions;
—   semantics of data elements;
—   restrictions on parameters and their values
—   implementation conformance statement proforma, in an Annex, as a basis for assessment of conformity to this document;
—   an Interoperability statement proforma, in an Annex, as a basis for assessment of transactional interoperability of two technical implementations;
—   a web service definition, in an Annex, for the use of web services as communication technology.
The implementation of the underlying back office systems and their business processes is not covered.

The scope for this European Standard is limited to:
-   payment method: Central account based on EFC-DSRC;
-   physical systems: OBU, RSE and the DSRC interface between them (all functions and information flows related to these parts);
-   DSRC-link requirements;
-   EFC transactions over the DSRC interface;
-   data elements to be used by OBU and RSE used in EFC-DSRC transactions;
-   security mechanisms for OBU and RSE used in EFC-DSRC transactions.

The scope for this European Standard is limited to:
-   payment method: Central account based on EFC-DSRC;
-   physical systems: OBU, RSE and the DSRC interface between them (all functions and information flows related to these parts);
-   DSRC-link requirements;
-   EFC transactions over the DSRC interface;
-   data elements to be used by OBU and RSE used in EFC-DSRC transactions;
-   security mechanisms for OBU and RSE used in EFC-DSRC transactions.

This document provides an analysis of the use of licence plate number (LPN) information and automatic number plate recognition (ANPR) technologies in electronic fee collection (EFC), through the description of the legal, technical and functional contexts of LPN-based EFC. It also provides an associated gap analysis of the EFC standards to identify actions to support standardized use of the identified technologies, and a roadmap to address the identified gaps.
The gap analysis in this document is based on use cases, relevant regulations, standards and best practices in the field of EFC, based on the European electronic toll service (EETS)[27] model.
Examples of licence plate number (LPN)-based tolling schemes are given in Annex A.

This document provides an analysis of the use of licence plate number (LPN) information and automatic number plate recognition (ANPR) technologies in electronic fee collection (EFC), through the description of the legal, technical and functional contexts of LPN-based EFC. It also provides an associated gap analysis of the EFC standards to identify actions to support standardized use of the identified technologies, and a roadmap to address the identified gaps.
The gap analysis in this document is based on use cases, relevant regulations, standards and best practices in the field of EFC, based on the European electronic toll service (EETS)[27] model.
Examples of licence plate number (LPN)-based tolling schemes are given in Annex A.

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 gives guidelines for the development of multi-operator/multi-service interoperable public surface (including subways) transport fare management systems (IFMSs) on a national and international level.
This document is applicable to bodies in public transport and related services which agree that their systems need to interoperate.
This document defines a conceptual framework which is independent of organizational and physical implementation. Any reference within this document to organizational or physical implementation is purely informative.
This document defines a reference functional architecture for IFMSs and establishes the requirements that are relevant for ensuring interoperability between several actors in the context of the use of electronic tickets.
The IFMS includes all the functions involved in the fare management process, such as:
—     management of media,
—     management of applications,
—     management of products,
—     security management, and
—     certification, registration, and identification.
This document defines the following main elements:
—     identification of the different sets of functions in relation to the overall IFMS and services and media from non-transport systems which interact with fare management systems;
—     a generic model of an IFMS describing the logical and functional architecture and the interfaces within the system, with other IFMSs and with services and media from non-transport systems;
—     use cases describing the interactions and data flows between the different sets of functions;
—     security requirements.
In its annexes, this document provides a framework for mobility platforms that integrate fare management and travel information for inter- and multimodal travel (see Annex A). It also elaborates on specific subjects covered in document and offers some national examples with regard to IFMS implementations (see Annex B, Annex C, Annex D and Annex E).
This document does not define:
—     the technical aspects of the interface between the medium and the medium access device;
—     the data exchanges between the medium and the medium access device;
NOTE     The data exchanges between the medium and the medium access device are proposed by other standardization committees.
—     the financial aspects of fare management systems (e.g. customer payments, method of payment, settlement, apportionment, reconciliation).

This document gives guidelines for the development of multi-operator/multi-service interoperable public surface (including subways) transport fare management systems (IFMSs) on a national and international level.
This document is applicable to bodies in public transport and related services which agree that their systems need to interoperate.
This document defines a conceptual framework which is independent of organizational and physical implementation. Any reference within this document to organizational or physical implementation is purely informative.
This document defines a reference functional architecture for IFMSs and establishes the requirements that are relevant for ensuring interoperability between several actors in the context of the use of electronic tickets.
The IFMS includes all the functions involved in the fare management process, such as:
—     management of media,
—     management of applications,
—     management of products,
—     security management, and
—     certification, registration, and identification.
This document defines the following main elements:
—     identification of the different sets of functions in relation to the overall IFMS and services and media from non-transport systems which interact with fare management systems;
—     a generic model of an IFMS describing the logical and functional architecture and the interfaces within the system, with other IFMSs and with services and media from non-transport systems;
—     use cases describing the interactions and data flows between the different sets of functions;
—     security requirements.
In its annexes, this document provides a framework for mobility platforms that integrate fare management and travel information for inter- and multimodal travel (see Annex A). It also elaborates on specific subjects covered in document and offers some national examples with regard to IFMS implementations (see Annex B, Annex C, Annex D and Annex E).
This document does not define:
—     the technical aspects of the interface between the medium and the medium access device;
—     the data exchanges between the medium and the medium access device;
NOTE     The data exchanges between the medium and the medium access device are proposed by other standardization committees.
—     the financial aspects of fare management systems (e.g. customer payments, method of payment, settlement, apportionment, reconciliation).

This document defines an information security framework for all organizational and technical entities of an EFC scheme and for the related interfaces, based on the system architecture defined in ISO 17573-1. The security framework describes a set of security requirements and associated security measures.
Annex D contains a list of potential threats to EFC systems and a possible relation to the defined security requirements. These threats can be used for a threat analysis to identify the relevant security requirements for an EFC system.
The relevant security measures to secure EFC systems can then be derived from the identified security requirements.

This document specifies the test procedures of electronic fee collection (EFC) roadside equipment (RSE) and on-board equipment (OBE) with regard to the conformance to standards and requirements for type approval and acceptance testing which is within the realm of EFC application specifically.
The scope of this document is restricted to systems operating within the radio emission, electromagnetic compatibility (EMC) regulations, traffic, and other regulations of the countries in which they are operated.
This document identifies a set of suitable parameters and provides test procedures to enable the proof of a complete EFC system, as well as components of an EFC system, e.g. OBE, related to the defined requirements of an application. The defined parameter and tests are assigned to the following groups of parameters:
—     functionality;
—     quality;
—     referenced pre-tests.
An overview of the tests and parameters provided by this document is given in 5.1 and 5.2.
This document describes procedures, methods and tools, and a test plan which shows the relation between all tests and the sequence of these tests. It lists all tests that are required to measure the performance of EFC equipment. It describes which EFC equipment is covered by the test procedures; the values of the parameters to be tested are not included. It also describes how the tests are to be performed and which tools and prerequisites are necessary before this series of tests can be undertaken. It is assumed that the security of the system is inherent in the communications and EFC functionality tests, therefore they are not addressed here. All tests in this document provide instructions to evaluate the test results.
This document defines only the tests and test procedures, not the benchmark figures that these are to be measured against. The test procedures defined in this document can be used as input, e.g. by scheme owners, for prototype testing, type approvals, tests of installations and periodic inspections.
Related to a conceptual model of an EFC system, this document relates only to the equipment of the user and the service provider. Any other entities are outside the scope of document.
EFC systems for dedicated short-range communication (DSRC) consist, in principle, of a group of technical components, which in combination fulfil the functions required for the collection of fees by electronic automatic means. These components comprise all, or most, of the following:
—     OBE within a vehicle;
—     OBE containing the communications and computing sub-functions;
—     optional integrated circuit card which may carry electronic money, service rights, and other secured information;
—     communication between OBE and RSE based on DSRC;
—     equipment for the fee collection at the RSE containing the communications and computing sub-functions;
—     equipment for the enforcement at the roadside;
—     central equipment for the administration and operation of the system.
The scope of this document relates solely to OBE and RSE and the DSRC interface between OBE and RSE including its functions to perform the fee collection. All the equipment used for enforcement (e.g. detection, classification, localization, and registration) and central equipment are outside the scope of this document.

This document provides an EETS gap analysis with the aim to identify the need for new or updated standards to provide an enhanced support of the recast of the EU EETS legislation [29], [31], [32].

This document provides an EETS gap analysis with the aim to identify the need for new or updated standards to provide an enhanced support of the recast of the EU EETS legislation [29], [31], [32].

This document defines an information security framework for all organizational and technical entities of an EFC scheme and for the related interfaces, based on the system architecture defined in ISO 17573-1. The security framework describes a set of security requirements and associated security measures.
Annex D contains a list of potential threats to EFC systems and a possible relation to the defined security requirements. These threats can be used for a threat analysis to identify the relevant security requirements for an EFC system.
The relevant security measures to secure EFC systems can then be derived from the identified security requirements.

This document specifies the test procedures of electronic fee collection (EFC) roadside equipment (RSE) and on-board equipment (OBE) with regard to the conformance to standards and requirements for type approval and acceptance testing which is within the realm of EFC application specifically.
The scope of this document is restricted to systems operating within the radio emission, electromagnetic compatibility (EMC) regulations, traffic, and other regulations of the countries in which they are operated.
This document identifies a set of suitable parameters and provides test procedures to enable the proof of a complete EFC system, as well as components of an EFC system, e.g. OBE, related to the defined requirements of an application. The defined parameter and tests are assigned to the following groups of parameters:
—     functionality;
—     quality;
—     referenced pre-tests.
An overview of the tests and parameters provided by this document is given in 5.1 and 5.2.
This document describes procedures, methods and tools, and a test plan which shows the relation between all tests and the sequence of these tests. It lists all tests that are required to measure the performance of EFC equipment. It describes which EFC equipment is covered by the test procedures; the values of the parameters to be tested are not included. It also describes how the tests are to be performed and which tools and prerequisites are necessary before this series of tests can be undertaken. It is assumed that the security of the system is inherent in the communications and EFC functionality tests, therefore they are not addressed here. All tests in this document provide instructions to evaluate the test results.
This document defines only the tests and test procedures, not the benchmark figures that these are to be measured against. The test procedures defined in this document can be used as input, e.g. by scheme owners, for prototype testing, type approvals, tests of installations and periodic inspections.
Related to a conceptual model of an EFC system, this document relates only to the equipment of the user and the service provider. Any other entities are outside the scope of document.
EFC systems for dedicated short-range communication (DSRC) consist, in principle, of a group of technical components, which in combination fulfil the functions required for the collection of fees by electronic automatic means. These components comprise all, or most, of the following:
—     OBE within a vehicle;
—     OBE containing the communications and computing sub-functions;
—     optional integrated circuit card which may carry electronic money, service rights, and other secured information;
—     communication between OBE and RSE based on DSRC;
—     equipment for the fee collection at the RSE containing the communications and computing sub-functions;
—     equipment for the enforcement at the roadside;
—     central equipment for the administration and operation of the system.
The scope of this document relates solely to OBE and RSE and the DSRC interface between OBE and RSE including its functions to perform the fee collection. All the equipment used for enforcement (e.g. detection, classification, localization, and registration) and central equipment are outside the scope of this document.

This document defines the architecture of electronic fee collection (EFC) system environments, in which a customer with one contract may use a vehicle in a variety of toll domains with a different toll charger 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 may identify vehicles subject to tolling by means of electronic equipment on-board in a vehicle or by other means (e.g. automatic number plate recognition, ANPR).
From a process point of view the architectural description focuses on toll determination, toll charging, 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 for common use in an EFC environment;
—          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 may 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 standardised exchanges;
—          identification of the interoperability interfaces for EFC systems, in specialised standards (specified or to be specified).

This document specifies transactions and data for Compliance Checking - Secure Monitoring. The Scope of this document consists of:
—-   the concept and involved processes for Secure Monitoring;
-   the definition of transactions and data;
-   the use of the OBE compliance checking transaction as specified in EN ISO 12813, for the purpose of Compliance Checking - Secure Monitoring;
-   the use of back end transactions as specified in EN ISO 12855, for the purpose of Compliance Checking – Secure Monitoring. This includes definitions for the use of optional elements and reserved attributes;
-   a specification of technical and organizational security measures involved in Secure Monitoring, on top of measures provided for in the EFC Security Framework;
-   the interrelations between different options in the OBE, TSP and TC domain and their high level impacts.
NOTE   Outside the Scope of this document is: The information exchange between OBE and TR, choices related to compliance checking policies e.g. which options are used, whether undetected/unexpected observations are applied, whether fixed, transportable or mobile compliance checking are deployed, locations and intensity of checking of itinerary freezing and checking of toll declaration, details of procedures and criteria for assessing the validity or plausibility of Itinerary Records.

This document defines the requirements for the secure application module (SAM) used in the secure monitoring compliance checking concept. It specifies two different configurations of a SAM:
-   trusted recorder, for use inside an OBE;
-   verification SAM, for use in other EFC system entities.
This document describes
-   terms and definitions used to describe the two Secure Application Module configurations;
-   operation of the two Secure Application Modules in the secure monitoring compliance checking concept;
-   functional requirements for the two Secure Application Modules configurations, including a classification of different security levels;
-   the interface, by means of transactions, messages and data elements, between an OBE or front end and the trusted recorder;
-   requirements on basic security primitives and key management procedures to support Secure Monitoring using a trusted recorder.
This document is consistent with the EFC architecture as defined in EN ISO 17573-1 and the derived suite of standards and Technical Specifications, especially CEN/TS 16702-1 and CEN ISO/TS 19299.
The following is outside the scope of this document:
-   The life cycle of a Secure Application Module and the way in which this is managed;
-   The interface commands needed to get a Secure Application Module in an operational state;
-   The interface definition of the verification SAM;
-   Definition of a hardware platform for the implementation of a Secure Application Module.

This document specifies transactions and data for Compliance Checking - Secure Monitoring. The Scope of this document consists of:
—-   the concept and involved processes for Secure Monitoring;
-   the definition of transactions and data;
-   the use of the OBE compliance checking transaction as specified in EN ISO 12813, for the purpose of Compliance Checking - Secure Monitoring;
-   the use of back end transactions as specified in EN ISO 12855, for the purpose of Compliance Checking – Secure Monitoring. This includes definitions for the use of optional elements and reserved attributes;
-   a specification of technical and organizational security measures involved in Secure Monitoring, on top of measures provided for in the EFC Security Framework;
-   the interrelations between different options in the OBE, TSP and TC domain and their high level impacts.
NOTE   Outside the Scope of this document is: The information exchange between OBE and TR, choices related to compliance checking policies e.g. which options are used, whether undetected/unexpected observations are applied, whether fixed, transportable or mobile compliance checking are deployed, locations and intensity of checking of itinerary freezing and checking of toll declaration, details of procedures and criteria for assessing the validity or plausibility of Itinerary Records.

This document defines the requirements for the secure application module (SAM) used in the secure monitoring compliance checking concept. It specifies two different configurations of a SAM:
-   trusted recorder, for use inside an OBE;
-   verification SAM, for use in other EFC system entities.
This document describes
-   terms and definitions used to describe the two Secure Application Module configurations;
-   operation of the two Secure Application Modules in the secure monitoring compliance checking concept;
-   functional requirements for the two Secure Application Modules configurations, including a classification of different security levels;
-   the interface, by means of transactions, messages and data elements, between an OBE or front end and the trusted recorder;
-   requirements on basic security primitives and key management procedures to support Secure Monitoring using a trusted recorder.
This document is consistent with the EFC architecture as defined in EN ISO 17573-1 and the derived suite of standards and Technical Specifications, especially CEN/TS 16702-1 and CEN ISO/TS 19299.
The following is outside the scope of this document:
-   The life cycle of a Secure Application Module and the way in which this is managed;
-   The interface commands needed to get a Secure Application Module in an operational state;
-   The interface definition of the verification SAM;
-   Definition of a hardware platform for the implementation of a Secure Application Module.

This document defines the architecture of electronic fee collection (EFC) system environments, in which a customer with one contract may use a vehicle in a variety of toll domains with a different toll charger 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 may identify vehicles subject to tolling by means of electronic equipment on-board in a vehicle or by other means (e.g. automatic number plate recognition, ANPR).
From a process point of view the architectural description focuses on toll determination, toll charging, 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 for common use in an EFC environment;
—          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 may 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 standardised exchanges;
—          identification of the interoperability interfaces for EFC systems, in specialised standards (specified or to be specified).

This document provides a suite of tests in order to assess the central equipment of toll chargers and toll service providers for compliancy towards the requirements listed in CEN/TS 16986. This document contains the definition of such tests in the form of test cases, reflecting the required individual steps listed in specific Test Purposes defined in CEN/TS 17154-1. The test cases are written in Testing and Test Control Notation version 3 (TTCN v3).

This document specifies the test suite structure (TSS) and test purposes (TP) to test conformity of central equipment of both toll chargers and toll service providers versus CEN/TS 16986.
It further provides templates for the protocol conformance test reports (PCTR) for the implementation under tests (IUT) for both the toll charger and the toll service provider.
This document contains the technical provisions to perform conformance testing of functional and dynamic behaviour of implementations conforming to CEN/TS 16986.
NOTE   The specifications in this Part provide the base for the tree and tabular combined notation (TTCN) of the test cases and steps which are provided in CEN/TS 17154 2.

This document specifies the test suite structure (TSS) and test purposes (TP) to test conformity of central equipment of both toll chargers and toll service providers versus CEN/TS 16986.
It further provides templates for the protocol conformance test reports (PCTR) for the implementation under tests (IUT) for both the toll charger and the toll service provider.
This document contains the technical provisions to perform conformance testing of functional and dynamic behaviour of implementations conforming to CEN/TS 16986.
NOTE   The specifications in this Part provide the base for the tree and tabular combined notation (TTCN) of the test cases and steps which are provided in CEN/TS 17154 2.

ISO 13143-2:2016 specifies the abstract test suite (ATS) to evaluate the conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 12813 in accordance with the test suite structure and test purposes defined in ISO 13143‑1:2016.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) equipment (OBE and RSE) to enable interoperability between equipment supplied by different manufacturers.
In order to ascertain that OBE and RSE fulfil essential radio requirements, they are also likely to be subject to additional factory, site and system acceptance testing (e.g. of physical and environmental endurance, quality assurance and control at manufacturing, and charge point integration), which is outside the scope of this document.

ISO 13140-2:2016 specifies the abstract test suite (ATS) to evaluate the conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 13141:2015 in accordance with the test suite structure and test purposes defined in ISO 13140‑1:2016.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) equipment (OBE and RSE) to support interoperability between different equipment supplied by different manufacturers.

This European Standard specifies the abstract test suite (ATS) to evaluate the conformity of on-board equipment (OBE) and roadside equipment (RSE) to EN 15509 in accordance with the test suite structure and test purposes defined in EN 15876-1:2016.
The objective of the present document is to provide a basis for conformance tests for DSRC equipment (OBE and RSE) to support interoperability between different equipment supplied by different manufacturers.

ISO 24534-3:2016 provides the requirements for an electronic registration identification (ERI) that is based on an identifier assigned to a vehicle (e.g. for recognition by national authorities) suitable to be used for the following:
-      electronic identification of local and foreign vehicles by national authorities;
-      vehicle manufacturing, in-life-maintenance, and end-of-life identification (vehicle life cycle management);
-      adaptation of vehicle data, e.g. in case of international re-sales;
-      safety-related purposes;
-      crime reduction;
-      commercial services;
-      adhering to privacy and data protection regulations.
ISO 24534-3:2016 defines the vehicle identification data. This data is called the ERI data and includes the following:
-      the vehicle identifier;
-      possible additional vehicle-related information (as typically included in a vehicle registration certificate).
All additional vehicle data elements are defined as optional. It is left to local legislation and/or the discretion of a registration authority to use or not to use a particular data element. If used, the value is assumed to be the one registered by the registration authority in accordance with local legislation. This part of ISO 24534 only provides the syntax for all these data elements.
NOTE          The secure application layer interfaces for the exchange of ERI data with an ERI reader or writer are specified in ISO 24534‑4 and in ISO 24534‑5.

ISO 24534-3:2016 provides the requirements for an electronic registration identification (ERI) that is based on an identifier assigned to a vehicle (e.g. for recognition by national authorities) suitable to be used for the following:
-      electronic identification of local and foreign vehicles by national authorities;
-      vehicle manufacturing, in-life-maintenance, and end-of-life identification (vehicle life cycle management);
-      adaptation of vehicle data, e.g. in case of international re-sales;
-      safety-related purposes;
-      crime reduction;
-      commercial services;
-      adhering to privacy and data protection regulations.
ISO 24534-3:2016 defines the vehicle identification data. This data is called the ERI data and includes the following:
-      the vehicle identifier;
-      possible additional vehicle-related information (as typically included in a vehicle registration certificate).
All additional vehicle data elements are defined as optional. It is left to local legislation and/or the discretion of a registration authority to use or not to use a particular data element. If used, the value is assumed to be the one registered by the registration authority in accordance with local legislation. This part of ISO 24534 only provides the syntax for all these data elements.
NOTE          The secure application layer interfaces for the exchange of ERI data with an ERI reader or writer are specified in ISO 24534‑4 and in ISO 24534‑5.

This Technical Report (TR) contains an analysis of the technical and operational feasibility of using a generic ITS Station as specified in ETSI EN 302 665, Intelligent Transport Systems (ITS); Communications Architecture, for EFC applications compliant to the requirements specified in ISO 17573, EN ISO 12855, CEN ISO/TS 17575 (all parts), EN ISO 14906, EN 15509, CEN ISO/TS 12813, CEN ISO/TS 13141 and CEN/TS 16439.
The scope of this Technical Report includes:
-   description of the context of Cooperative ITS and the ITS Stations;
-   providing details of the context of EFC applications;
-   outlining the basic architectural concepts and role model of both EFC and Cooperative ITS;
-   identification of core requirement areas for operation of an EFC application on an ITS Station;
-   specification of a set of recommendations for functional, operational and security requirements to the ITS Station supporting the EFC application(s);
-   description of a possible role model in which the roles known in EFC applications make use of the roles in the C-ITS system in order to provide EFC services in an C-ITS context;
-   provision of considerations in particular areas of EFC like certification and governances;
-   guideless and recommendations for further standardization work in this area;
-   emphasising on security related elements of EFC that need to be considered in a C-ITS environment.
The scope of this Technical Report is limited to in-vehicle ITS Stations. However, an EFC service always requires the involvement of in-vehicle and central functionalities. Furthermore, for enforcement purposes as well as in DSRC based toll domains for toll charging purposes also, it is essential that road-side based functions are provided and operated. In order to facilitate EFC services a set of functionalities, tasks and responsibilities are defined and specified in an EFC role model (ISO 17573). These functionalities, tasks and responsibilities are shared between the roles Toll Charger, Toll Service Provider, Road User and Interoperability Management. All these roles interact with each other. As a consequence this Technical Report provides in various areas explanations that are beyond the in-vehicle environment. This is required in order to present the full environment and context. It keeps the readability of this document at a sound level and provides valuable information to those readers which are not yet familiar with EFC in detail.
Outside the scope of this Technical Report is:
-   detailed technical specifications for EFC services and applications on C-ITS systems;
-   implementation specific elements.

This Technical Report (TR) contains an analysis of the technical and operational feasibility of using a generic ITS Station as specified in ETSI EN 302 665, Intelligent Transport Systems (ITS); Communications Architecture, for EFC applications compliant to the requirements specified in ISO 17573, EN ISO 12855, CEN ISO/TS 17575 (all parts), EN ISO 14906, EN 15509, CEN ISO/TS 12813, CEN ISO/TS 13141 and CEN/TS 16439.
The scope of this Technical Report includes:
-   description of the context of Cooperative ITS and the ITS Stations;
-   providing details of the context of EFC applications;
-   outlining the basic architectural concepts and role model of both EFC and Cooperative ITS;
-   identification of core requirement areas for operation of an EFC application on an ITS Station;
-   specification of a set of recommendations for functional, operational and security requirements to the ITS Station supporting the EFC application(s);
-   description of a possible role model in which the roles known in EFC applications make use of the roles in the C-ITS system in order to provide EFC services in an C-ITS context;
-   provision of considerations in particular areas of EFC like certification and governances;
-   guideless and recommendations for further standardization work in this area;
-   emphasising on security related elements of EFC that need to be considered in a C-ITS environment.
The scope of this Technical Report is limited to in-vehicle ITS Stations. However, an EFC service always requires the involvement of in-vehicle and central functionalities. Furthermore, for enforcement purposes as well as in DSRC based toll domains for toll charging purposes also, it is essential that road-side based functions are provided and operated. In order to facilitate EFC services a set of functionalities, tasks and responsibilities are defined and specified in an EFC role model (ISO 17573). These functionalities, tasks and responsibilities are shared between the roles Toll Charger, Toll Service Provider, Road User and Interoperability Management. All these roles interact with each other. As a consequence this Technical Report provides in various areas explanations that are beyond the in-vehicle environment. This is required in order to present the full environment and context. It keeps the readability of this document at a sound level and provides valuable information to those readers which are not yet familiar with EFC in detail.
Outside the scope of this Technical Report is:
-   detailed technical specifications for EFC services and applications on C-ITS systems;
-   implementation specific elements.

ISO 24534-1:2010 provides requirements for electronic registration identification (ERI) that are based on an identifier assigned to a vehicle (e.g. for recognition by national authorities), suitable to be used for:
electronic identification of local and foreign vehicles by national authorities;
vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life cycle management);
adaptation of vehicle data (e.g. for international resales);
safety-related purposes;
crime reduction;
commercial services.
It adheres to privacy and data protection regulations.
ISO 24534-1:2010 provides an overview of the ERI system concept, in terms of the onboard vehicle components and the external off-vehicle components required for an operational system. The detailed requirements are defined in Parts 2, 3, 4 and 5 of ISO 24534 and more limited, though relevant, provisions are defined in ISO 24535.

1.1 Definition of VAS
Value Added Services, VAS, is a term that was coined in the telecommunications industry for services that go
beyond core service, such as mobile voice communications. Such additional services are intended to add
value for the consumers in order to encourage them to use the telecommunications service more often and to
add an additional revenue stream for the Service Provider.
In the context of EFC, a VAS in this strict sense is a telematics service offered to the Service User by means
of an EFC OBE. This service might directly be consumed by the driver in the vehicle, or might, particularly in
the case of heavy vehicles, be targeted at the freight operator and be consumed in a back office. Such
services can be fleet management services like track-and-trace, payment services such as paying petrol
automatically at the pump, or regulatory applications such as Electronic Licence Plate or access control. Such
additional services and applications create additional value to the user, either by the value the new service
creates to him, or in the case of regulatory services, by combining several functionalities in a single device,
thus removing the need to install and maintain several pieces of equipment simultaneously.
In a wider sense, the operator of the EFC service can draw additional benefit from the data collected by the
EFC system. Data from EFC OBE gives a good account of the traffic situation on the charged network, and
may be utilised for statistical purposes, for traffic planning or even in real-time for traffic information purposes.
The scope of this TR covers both the original meaning of VAS, namely both additional services to the user of
the core EFC service and additional value created for the operator of the charging system.
1.2 Coverage
The TR analyses all telematics applications that have the potential to be delivered as a VAS to EFC. The
analysis covers the requirements of the VAS applications and the fit to the resources offered by the EFC
system. It also analyses prerequisites in terms of business and technical system architecture in order to
enable VAS to be delivered, including questions of control and governance, security aspects and privacy
issues.
The TR does not analyse commercial viability. Cost to benefit ratio and market potential for VAS are
considered to be out of scope.
The TR analyses the potential and pre-conditions for EFC equipment to serve as platforms for a diverse range
of VAS. The VAS are considered to be add-ons to EFC equipment. The TR does not analyse the reverse
situation, namely the situation where an EFC application is added to a telematics platform that has been
deployed for another core service, such as the suitability of navigation systems to serve as platforms for EFC.

1.1 Definition of VAS
Value Added Services, VAS, is a term that was coined in the telecommunications industry for services that go
beyond core service, such as mobile voice communications. Such additional services are intended to add
value for the consumers in order to encourage them to use the telecommunications service more often and to
add an additional revenue stream for the Service Provider.
In the context of EFC, a VAS in this strict sense is a telematics service offered to the Service User by means
of an EFC OBE. This service might directly be consumed by the driver in the vehicle, or might, particularly in
the case of heavy vehicles, be targeted at the freight operator and be consumed in a back office. Such
services can be fleet management services like track-and-trace, payment services such as paying petrol
automatically at the pump, or regulatory applications such as Electronic Licence Plate or access control. Such
additional services and applications create additional value to the user, either by the value the new service
creates to him, or in the case of regulatory services, by combining several functionalities in a single device,
thus removing the need to install and maintain several pieces of equipment simultaneously.
In a wider sense, the operator of the EFC service can draw additional benefit from the data collected by the
EFC system. Data from EFC OBE gives a good account of the traffic situation on the charged network, and
may be utilised for statistical purposes, for traffic planning or even in real-time for traffic information purposes.
The scope of this TR covers both the original meaning of VAS, namely both additional services to the user of
the core EFC service and additional value created for the operator of the charging system.
1.2 Coverage
The TR analyses all telematics applications that have the potential to be delivered as a VAS to EFC. The
analysis covers the requirements of the VAS applications and the fit to the resources offered by the EFC
system. It also analyses prerequisites in terms of business and technical system architecture in order to
enable VAS to be delivered, including questions of control and governance, security aspects and privacy
issues.
The TR does not analyse commercial viability. Cost to benefit ratio and market potential for VAS are
considered to be out of scope.
The TR analyses the potential and pre-conditions for EFC equipment to serve as platforms for a diverse range
of VAS. The VAS are considered to be add-ons to EFC equipment. The TR does not analyse the reverse
situation, namely the situation where an EFC application is added to a telematics platform that has been
deployed for another core service, such as the suitability of navigation systems to serve as platforms for EFC.

This technical report (TR) analyses requirements for a universal Pre-Pay account system for EFC including the following issues:
-   relations to other existing standards in this domain;
-   the core requirements and functionality that must be provided.
This technical report will show an analysis of the requirements for a universal prepay system and categorise possible different types of pre-pay solutions, in terms of functionality, technical and legal considerations. As far as legal requirements are concerned it will be clarified whether the pre-payment means fall within the scope of European Directive 2000/46/EC on the taking up, pursuit of and prudential supervision of the business of electronic money institutions and whether the medium-issuing organisation has to act as a financial institution and falls within the scope of the Payment Service Directive 2007/64/EC. The latter applying exactly to payment activities undertaken by entities but do not require a full bank license.
The technical report will describe the current state-of-affairs of EFC pre-payment systems, including the demand for standards and inventory of provisions provided by standards. It will identify and prioritize gaps in terms of standards or other enablers needed in order for the market to provide viable pre-payment solutions in a European context.
There are two general approaches to represent the content of the TR:
a)   allocate each requirement under each pre-pay solution;
b)   allocate each pre-pay solution under each requirement.
To achieve a better understanding and readability alternative a) has been decided (this refers to Clause 8 and Clause 9 only).
The TR does not give any decision on how or whether one of the pre-payment solutions described is commercially feasible to be considered as an implementable offer to the Service User. The return for invest for any TSP regarding the system architecture requirements and other obligations (refunding of SU) is questionable.

This technical report (TR) analyses requirements for a universal Pre-Pay account system for EFC including the following issues:
-   relations to other existing standards in this domain;
-   the core requirements and functionality that must be provided.
This technical report will show an analysis of the requirements for a universal prepay system and categorise possible different types of pre-pay solutions, in terms of functionality, technical and legal considerations. As far as legal requirements are concerned it will be clarified whether the pre-payment means fall within the scope of European Directive 2000/46/EC on the taking up, pursuit of and prudential supervision of the business of electronic money institutions and whether the medium-issuing organisation has to act as a financial institution and falls within the scope of the Payment Service Directive 2007/64/EC. The latter applying exactly to payment activities undertaken by entities but do not require a full bank license.
The technical report will describe the current state-of-affairs of EFC pre-payment systems, including the demand for standards and inventory of provisions provided by standards. It will identify and prioritize gaps in terms of standards or other enablers needed in order for the market to provide viable pre-payment solutions in a European context.
There are two general approaches to represent the content of the TR:
a)   allocate each requirement under each pre-pay solution;
b)   allocate each pre-pay solution under each requirement.
To achieve a better understanding and readability alternative a) has been decided (this refers to Clause 8 and Clause 9 only).
The TR does not give any decision on how or whether one of the pre-payment solutions described is commercially feasible to be considered as an implementable offer to the Service User. The return for invest for any TSP regarding the system architecture requirements and other obligations (refunding of SU) is questionable.

ISO 24534-4:2010 provides requirements for electronic registration identification (ERI) that are based on an identifier assigned to a vehicle (e.g. for recognition by national authorities) suitable to be used for:
electronic identification of local and foreign vehicles by national authorities;
vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life cycle management);
adaptation of vehicle data (e.g. for international resales);
safety-related purposes;
crime reduction;
commercial services.
It adheres to privacy and data protection regulations.
ISO 24534-4:2010 specifies the interfaces for a secure exchange of data between an ERT and an ERI reader or ERI writer in or outside the vehicle using asymmetric encryption techniques.
ISO 24534-4:2010 includes:
the application layer interface between an ERT and an onboard ERI reader or writer;
the application layer interface between the onboard ERI equipment and external ERI readers and writers;
security issues related to the communication with the ERT.

ISO 24534-1:2010 provides requirements for electronic registration identification (ERI) that are based on an identifier assigned to a vehicle (e.g. for recognition by national authorities), suitable to be used for:
electronic identification of local and foreign vehicles by national authorities;
vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life cycle management);
adaptation of vehicle data (e.g. for international resales);
safety-related purposes;
crime reduction;
commercial services.
It adheres to privacy and data protection regulations.
ISO 24534-1:2010 provides an overview of the ERI system concept, in terms of the onboard vehicle components and the external off-vehicle components required for an operational system. The detailed requirements are defined in Parts 2, 3, 4 and 5 of ISO 24534 and more limited, though relevant, provisions are defined in ISO 24535.

ISO 24534-2:2010 provides requirements for electronic registration identification (ERI) that are based on an identifier assigned to a vehicle (e.g. for recognition by national authorities) suitable to be used for:
electronic identification of local and foreign vehicles by national authorities;
vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life cycle management);
adaptation of vehicle data (e.g. for international resales);
safety-related purposes;
crime reduction;
commercial services.
It adheres to privacy and data protection regulations.
ISO 24534-2:2010 defines the operational requirements for the remaining parts of ISO 24534 and the more limited but relevant provisions of ISO 24535.
Whilst the definition of the organizational framework required to implement, operate and maintain an ERI system is outside the scope of ISO 24534-2:2010, a list of potential stakeholders in the public and private sector has been included.

ISO 24534-4:2010 provides requirements for electronic registration identification (ERI) that are based on an identifier assigned to a vehicle (e.g. for recognition by national authorities) suitable to be used for:
electronic identification of local and foreign vehicles by national authorities;
vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life cycle management);
adaptation of vehicle data (e.g. for international resales);
safety-related purposes;
crime reduction;
commercial services.
It adheres to privacy and data protection regulations.
ISO 24534-4:2010 specifies the interfaces for a secure exchange of data between an ERT and an ERI reader or ERI writer in or outside the vehicle using asymmetric encryption techniques.
ISO 24534-4:2010 includes:
the application layer interface between an ERT and an onboard ERI reader or writer;
the application layer interface between the onboard ERI equipment and external ERI readers and writers;
security issues related to the communication with the ERT.

ISO 24534-2:2010 provides requirements for electronic registration identification (ERI) that are based on an identifier assigned to a vehicle (e.g. for recognition by national authorities) suitable to be used for:
electronic identification of local and foreign vehicles by national authorities;
vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life cycle management);
adaptation of vehicle data (e.g. for international resales);
safety-related purposes;
crime reduction;
commercial services.
It adheres to privacy and data protection regulations.
ISO 24534-2:2010 defines the operational requirements for the remaining parts of ISO 24534 and the more limited but relevant provisions of ISO 24535.
Whilst the definition of the organizational framework required to implement, operate and maintain an ERI system is outside the scope of ISO 24534-2:2010, a list of potential stakeholders in the public and private sector has been included.

This technical report analyses DSRC Urban Charge Point Requirements including the following issues:
-   The core requirements and functionality that must be provided within DSRC equipment in an urban context;
-   The potential aesthetic impact;
-   How to handle the different traffic conditions in urban areas;
-   Accommodation of the diversity of road users;
-   The potential need to address highly variable topology;
-   A wide variety of installation challenges;
-   Minimisation of the impact of E-M interference;
-   How to ensure interoperability with systems in non-urban contexts (e.g. motorways, plaza systems, handheld readers, etc);
-   How to minimise and, if possible, have no impact upon OBE design;
-   Relations to other existing standards in this domain;
-   How to meet international requirements for Health and Safety;
-   The wider policy context that city centres must address in addition to tackling congestion.
The physical location and configuration of the installation represent a compromise between the needs of the DSRC transaction, of the local electromagnetic environment and of the existing built environment locally both above and below ground. The urban charging system, of which the DSRC element is a part, will be required to fit within a wider social and transport policy context.
It is recognised that not all the elements above lend themselves to a standard, nor will industry be interested in promoting all above topics. However, with an increasing number of urban Charging Schemes being considered, there is a need to create relevant standards from the above lists and hence make it easier for suppliers to offer equipment and services to meet the requirements.

This technical report analyses DSRC Urban Charge Point Requirements including the following issues:
-   The core requirements and functionality that must be provided within DSRC equipment in an urban context;
-   The potential aesthetic impact;
-   How to handle the different traffic conditions in urban areas;
-   Accommodation of the diversity of road users;
-   The potential need to address highly variable topology;
-   A wide variety of installation challenges;
-   Minimisation of the impact of E-M interference;
-   How to ensure interoperability with systems in non-urban contexts (e.g. motorways, plaza systems, handheld readers, etc);
-   How to minimise and, if possible, have no impact upon OBE design;
-   Relations to other existing standards in this domain;
-   How to meet international requirements for Health and Safety;
-   The wider policy context that city centres must address in addition to tackling congestion.
The physical location and configuration of the installation represent a compromise between the needs of the DSRC transaction, of the local electromagnetic environment and of the existing built environment locally both above and below ground. The urban charging system, of which the DSRC element is a part, will be required to fit within a wider social and transport policy context.
It is recognised that not all the elements above lend themselves to a standard, nor will industry be interested in promoting all above topics. However, with an increasing number of urban Charging Schemes being considered, there is a need to create relevant standards from the above lists and hence make it easier for suppliers to offer equipment and services to meet the requirements.

ISO 17624:2009 provides the specifications of:
common AVI/AEI transaction requirements, which define the common steps of any AVI/AEI transaction;
AVI/AEI application interface to standardized wireless protocols (referred to as the "Air Interface") supporting the AVI transaction requirements, so as to enable interoperability.
ISO 17624:2009 is an interface standard, adhering to the open systems interconnection (OSI) philosophy (ISO/IEC 7498‑1), and it is as such not concerned with the implementation choices to be realized at either side of the air interface between the "Fixed Equipment" and "OBE".