2019/520 - Directive (EU) 2019/520 of the European Parliament and of the Council of 19 March 2019 on the interoperability of electronic road toll systems and facilitating cross-border exchange of information on the failure to pay road fees in the Union (Text with EEA relevance.)

This document defines terms within the field of electronic fee collection (EFC).
This document defines:
—     terms that are used in standards related to electronic fee collection;
—     terms of a more general use that are used more specifically in standards related to electronic fee collection.
This document does not define terms related primarily to other fields that operate in conjunction with EFC, such as terms for intelligent transport systems (ITS), common payment systems, the financial sector, etc.

This document defines terms within the field of electronic fee collection (EFC).
This document defines:
—     terms that are used in standards related to electronic fee collection;
—     terms of a more general use that are used more specifically in standards related to electronic fee collection.
This document does not define terms related primarily to other fields that operate in conjunction with EFC, such as terms for intelligent transport systems (ITS), common payment systems, the financial sector, etc.

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-office system of the two roles of service provision and toll charging, e.g.:
—   charging-related data (toll declarations, billing details, payment claims, payment announcements),
—   administrative data (trust objects, EFC context data, etc.), 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 specified 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 TC or 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 ADUs that can possibly involve several APDU exchanges;
—    processes regarding payments and exchanges of fiscal, commercial or legal accounting documents;
—    definitions of service communication channels, protocols and service primitives to transfer the APDU.

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-office system of the two roles of service provision and toll charging, e.g.:
—   charging-related data (toll declarations, billing details, payment claims, payment announcements),
—   administrative data (trust objects, EFC context data, etc.), 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 specified 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 TC or 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 ADUs that can possibly involve several APDU exchanges;
—    processes regarding payments and exchanges of fiscal, commercial or legal accounting documents;
—    definitions of service communication channels, protocols and service primitives to transfer the APDU.

This document specifies the set-up of a testing system and the test suite structure and test purposes, i.e. tests to be used to assess the level of interference from RLAN devices operating in the 5,8 GHz range on tolling and tachograph devices operating in the same frequency range.
To obtain generalized results that can subsequently be used to design appropriate mitigation techniques, the test environment and the test cases are designed to:
1.   acquire a large number of transactions on devices of different makes and characteristics;
2.   ensure anonymity of results.
The test results ensure calculation of averages as well as standard deviations.
The tests specified in this document are for the sole purpose of investigating RLAN interference over DSRC communications. Other factors that can impact the performance of DSRC and also the level of interference in a test scenario are not subject to test specifications and out of the scope of this document.

This document specifies the set-up of a testing system and the test suite structure and test purposes, i.e. tests to be used to assess the level of interference from RLAN devices operating in the 5,8 GHz range on tolling and tachograph devices operating in the same frequency range.
To obtain generalized results that can subsequently be used to design appropriate mitigation techniques, the test environment and the test cases are designed to:
1.   acquire a large number of transactions on devices of different makes and characteristics;
2.   ensure anonymity of results.
The test results ensure calculation of averages as well as standard deviations.
The tests specified in this document are for the sole purpose of investigating RLAN interference over DSRC communications. Other factors that can impact the performance of DSRC and also the level of interference in a test scenario are not subject to test specifications and out of the scope of this document.

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.

ISO/TS 17574:2017 provides guidelines for preparation and evaluation of security requirements specifications, referred to as Protection Profiles (PP) in ISO/IEC 15408 (all parts) and in ISO/IEC TR 15446.
By Protection Profile (PP), it means a set of security requirements for a category of products or systems that meet specific needs. A typical example would be a PP for On-Board Equipment (OBE) to be used in an EFC system. However, the guidelines in this document are superseded if a Protection Profile already exists for the subsystem in consideration.

ISO/TS 17574:2017 provides guidelines for preparation and evaluation of security requirements specifications, referred to as Protection Profiles (PP) in ISO/IEC 15408 (all parts) and in ISO/IEC TR 15446.
By Protection Profile (PP), it means a set of security requirements for a category of products or systems that meet specific needs. A typical example would be a PP for On-Board Equipment (OBE) to be used in an EFC system. However, the guidelines in this document are superseded if a Protection Profile already exists for the subsystem in consideration.