2010/40/EU - Directive 2010/40/EU of the European Parliament and of the Council of 7 July 2010 on the framework for the deployment of Intelligent Transport Systems in the field of road transport and for interfaces with other modes of transport Text with EEA relevance

This document specifies a publication sub-model within the DATEX II model that supports the publication of electronic traffic regulations and controlled zones.
This publication is intended to support the exchange of informational content from road traffic authorities issuing traffic regulation orders and organizations implementing these orders to other organizations providing ITS services or onward information exchange.

This document specifies a publication sub-model within the DATEX II model that supports the publication of electronic traffic regulations and controlled zones.
This publication is intended to support the exchange of informational content from road traffic authorities issuing traffic regulation orders and organizations implementing these orders to other organizations providing ITS services or onward information exchange.

The main objective of this WI is to define a SIRI Passenger Real-Time Information European profile:
•   To identify a minimum subset of SIRI with codification rules and constraints for a European level plug and play exchange of real-time passenger information data between organisations at a European level
•   To reflect already existing NeTEx profiles defined at national level (Norway, France, Sweden, etc.).
•   To maintain a relevant real-time information dataset, as small and simple as possible, to ensure interoperability is maximised while at the same time enabling exchange of supplementary national real-time data that will not interfere with the core international dataset
•   To complement the EPIP (NeTEx European Passenger Information Profile) with real-time passenger information
•   To establish quality assessment procedures for implementing validation and quality assessment tools - including compliance checking rules - necessary to fulfil the requirement of the Commission
This profile will complement the NeTEx Passenger information profile and NeTEx Accessibility profile (under drafting) in order to get a set of consistent European profiles fulfilling the requirements of the Priority Action "A" of the ITS Directive.

The main objective of this WI is to define a SIRI Passenger Real-Time Information European profile:
•   To identify a minimum subset of SIRI with codification rules and constraints for a European level plug and play exchange of real-time passenger information data between organisations at a European level
•   To reflect already existing NeTEx profiles defined at national level (Norway, France, Sweden, etc.).
•   To maintain a relevant real-time information dataset, as small and simple as possible, to ensure interoperability is maximised while at the same time enabling exchange of supplementary national real-time data that will not interfere with the core international dataset
•   To complement the EPIP (NeTEx European Passenger Information Profile) with real-time passenger information
•   To establish quality assessment procedures for implementing validation and quality assessment tools - including compliance checking rules - necessary to fulfil the requirement of the Commission
This profile will complement the NeTEx Passenger information profile and NeTEx Accessibility profile (under drafting) in order to get a set of consistent European profiles fulfilling the requirements of the Priority Action "A" of the ITS Directive.

This document specifies a unified logical data model based on available existing dynamic information standards. The data has precise relative location references to be linked with ISO/TS 22726-1 which specifies the architecture and the logical data model of static map data for connected and automated driving applications. Dynamic event data comes from external systems and has been defined and specified independently by existing standards. Therefore, the logical data model in this document is formed to synthesize contents referring to other standards.

The proposed Part 13 will specify a DATEX II platform-independent model for expression of intelligent transport system device status and fault data. It will follow the EN 16157-1 methodology and reuse common concepts from EN 16157-2 and EN 16157-7.
It will define a UML model with a corresponding data dictionary and XML Schema.
The model will define a device publication which identifies static data, a device status publication, and a device faults publication.
Devices in scope are any that participate in intelligent transport systems.
This specification may be used in system-to-system exchanges about device status and faults, for example a traffic management system that performs operational control of devices may provide information about the status and faults of those devices to a separate technology status and fault management system.

The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using ‘Public Land Mobile Networks’(PLMN), which supports the European pre-assigned emergency destination address (see normative references) and to provide a means of manually triggering the notification of an incident.
This document specifies the general operating requirements and intrinsic procedures for in-vehicle emergency call (eCall) services in order to transfer an emergency message from a vehicle to a Public Safety Answering Point (PSAP) in the event of a crash or emergency, via an eCall communication session and to establish a voice channel between the in-vehicle equipment and the PSAP.
Private third party in-vehicle emergency supporting services can also provide a similar eCall function by other means. The provision of such services are defined in EN 16102, and are outside the scope of this document.
The communications protocols and methods for the transmission of the MSD are not specified in this document.
This document specifies the operating requirements for an eCall service. An important part of the eCall service is a Minimum Set of Data (MSD). The operating requirements for the MSD are determined in this document, but the form and data content of the MSD is not defined herein. A common European MSD is determined in EN 15722.
This document does not specify whether eCall is provided using embedded equipment or other means (for example in the case of aftermarket equipment).

The Technical Specification will be adapted in the following way:
•   OJP will be realigned with the latest Transmodel version and NeTEx issues, where appropriate (e.g.
        New Modes)
•   The integration of new modes especially the conceptual equivalency to major multi-modal standards
        shall be studied and if necessary, adaptions to OJP occur. The idea is to study OSDM, TOMP, TRIAS
        and GBFS/GOFS. The interactions should be smooth. Interaction between OJP and distribution
        features will be settled.
•   OJP is extended as far into the distribution area as it is considered a good idea. For the actual
        booking and purchase steps, OSDM, TOMP, TRIAS and/or GOFS are to be used. The line we think to
        draw is: booking. OJP should not transfer personalized information. This results in the following
        proposed adaptions to fit OJP into a full MaaS roaming environment:
o   An availability request (with response)
o   Token/id handling for trips and trip legs (for hand-over) and pushed information during trips. We will
        need to model bookable items on some level.
o   OJPFare needs to be extended/adapted.
o   TripInfoRequest and -Response need to be updated to reflect, information about trips and trip legs
        and not only vehicle and journey.
•   All work prepared under the heading OJP 1.1 will be finalised.
•   EPIAP (Accessibility) minimal profile will be used to verify that the trip planning can make use of it.
•   The provision of an OpenAPI and REST/JSON derived directly from the XSD shall be studied
        (eventually using a converter).

The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using ‘Public Land Mobile Networks’(PLMN), which supports the European pre-assigned emergency destination address (see normative references) and to provide a means of manually triggering the notification of an incident.
This document specifies the general operating requirements and intrinsic procedures for in-vehicle emergency call (eCall) services in order to transfer an emergency message from a vehicle to a Public Safety Answering Point (PSAP) in the event of a crash or emergency, via an eCall communication session and to establish a voice channel between the in-vehicle equipment and the PSAP.
Private third party in-vehicle emergency supporting services can also provide a similar eCall function by other means. The provision of such services are defined in EN 16102, and are outside the scope of this document.
The communications protocols and methods for the transmission of the MSD are not specified in this document.
This document specifies the operating requirements for an eCall service. An important part of the eCall service is a Minimum Set of Data (MSD). The operating requirements for the MSD are determined in this document, but the form and data content of the MSD is not defined herein. A common European MSD is determined in EN 15722.
This document does not specify whether eCall is provided using embedded equipment or other means (for example in the case of aftermarket equipment).

The proposed Part 13 will specify a DATEX II platform-independent model for expression of intelligent transport system device status and fault data. It will follow the EN 16157-1 methodology and reuse common concepts from EN 16157-2 and EN 16157-7.
It will define a UML model with a corresponding data dictionary and XML Schema.
The model will define a device publication which identifies static data, a device status publication, and a device faults publication.
Devices in scope are any that participate in intelligent transport systems.
This specification may be used in system-to-system exchanges about device status and faults, for example a traffic management system that performs operational control of devices may provide information about the status and faults of those devices to a separate technology status and fault management system.

This document specifies a unified logical data model based on available existing dynamic information standards. The data has precise relative location references to be linked with ISO/TS 22726-1 which specifies the architecture and the logical data model of static map data for connected and automated driving applications. Dynamic event data comes from external systems and has been defined and specified independently by existing standards. Therefore, the logical data model in this document is formed to synthesize contents referring to other standards.

The Technical Specification will be adapted in the following way:
•   OJP will be realigned with the latest Transmodel version and NeTEx issues, where appropriate (e.g.
        New Modes)
•   The integration of new modes especially the conceptual equivalency to major multi-modal standards
        shall be studied and if necessary, adaptions to OJP occur. The idea is to study OSDM, TOMP, TRIAS
        and GBFS/GOFS. The interactions should be smooth. Interaction between OJP and distribution
        features will be settled.
•   OJP is extended as far into the distribution area as it is considered a good idea. For the actual
        booking and purchase steps, OSDM, TOMP, TRIAS and/or GOFS are to be used. The line we think to
        draw is: booking. OJP should not transfer personalized information. This results in the following
        proposed adaptions to fit OJP into a full MaaS roaming environment:
o   An availability request (with response)
o   Token/id handling for trips and trip legs (for hand-over) and pushed information during trips. We will
        need to model bookable items on some level.
o   OJPFare needs to be extended/adapted.
o   TripInfoRequest and -Response need to be updated to reflect, information about trips and trip legs
        and not only vehicle and journey.
•   All work prepared under the heading OJP 1.1 will be finalised.
•   EPIAP (Accessibility) minimal profile will be used to verify that the trip planning can make use of it.
•   The provision of an OpenAPI and REST/JSON derived directly from the XSD shall be studied
        (eventually using a converter).

This document specifies an additional SIRI functional service to exchange information about Control Actions, between monitoring systems and servers containing real-time public transport vehicle or journey time data. These include the control centres of transport operators, as well as information systems that deliver passenger travel information services. As for Transmodel, public transport modes include new modes of transport (vehicle sharing, vehicle pooling, etc.).
This document describes the SIRI Control Action service, one of a modular set of services for the exchange of Real-time information. The Control Action service (SIRI-CA) is concerned with the exchange of information about decision made concerning the real-time management of the operation of a transport system as performed by operators while operating the services.

This document is a profile of the CEN/TS 16614 series. It focuses on information relevant to feed the necessary accessibility passenger information services and excludes operational and fares information. It is based directly on EPIP (CEN/TS 16614-4).
This European Passenger Information Accessibility Profile (EPIAP) for NeTEx is for exchanging passenger information; it describes how to extend EPIP (the European Passenger Information Profile) with additional information (including a minimal set) to feed the necessary accessibility passenger information services in a European wide and multimodal context. EPIAP especially formulates a mandatory minimal implementation that needs to be filled in by everybody to deliver the necessary information for an assessment of the accessibility of site(s), vehicles and on vehicle-site interaction for impaired persons. The minimal level allows an assessment and contains the information to produce PRM TSI if necessary. It will also cover what the current legislation usually warrants. It then describes how additional information must be provided if an organisation decides to provide it (e.g. the information of the full DELFI+ standard in Germany).
EPIP does not reflect part 5 (New Modes) yet. However, EPIAP takes it into account. EPIP will have to be adapted accordingly.
For EPIAP to be of use, the EC needs to declare the minimal level of EPIAP as mandatory.

This document is a profile of the CEN/TS 16614 series. It focuses on information relevant to feed the necessary accessibility passenger information services and excludes operational and fares information. It is based directly on EPIP (CEN/TS 16614-4).
This European Passenger Information Accessibility Profile (EPIAP) for NeTEx is for exchanging passenger information; it describes how to extend EPIP (the European Passenger Information Profile) with additional information (including a minimal set) to feed the necessary accessibility passenger information services in a European wide and multimodal context. EPIAP especially formulates a mandatory minimal implementation that needs to be filled in by everybody to deliver the necessary information for an assessment of the accessibility of site(s), vehicles and on vehicle-site interaction for impaired persons. The minimal level allows an assessment and contains the information to produce PRM TSI if necessary. It will also cover what the current legislation usually warrants. It then describes how additional information must be provided if an organisation decides to provide it (e.g. the information of the full DELFI+ standard in Germany).
EPIP does not reflect part 5 (New Modes) yet. However, EPIAP takes it into account. EPIP will have to be adapted accordingly.
For EPIAP to be of use, the EC needs to declare the minimal level of EPIAP as mandatory.

This document specifies an additional SIRI functional service to exchange information about Control Actions, between monitoring systems and servers containing real-time public transport vehicle or journey time data. These include the control centres of transport operators, as well as information systems that deliver passenger travel information services. As for Transmodel, public transport modes include new modes of transport (vehicle sharing, vehicle pooling, etc.).
This document describes the SIRI Control Action service, one of a modular set of services for the exchange of Real-time information. The Control Action service (SIRI-CA) is concerned with the exchange of information about decision made concerning the real-time management of the operation of a transport system as performed by operators while operating the services.

In respect of pan-European eCall (operating requirements defined in EN 16072), this document defines the high-level application protocols, procedures and processes required to provide the eCall service using a TS12 emergency call over a circuit-switched mobile communications network.
NOTE 1   The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using a PLMN (such as ETSI prime medium) which supports the European harmonized 112/E112 emergency number (TS12 ETSI TS 122 003) and to provide a means of manually triggering the notification of an emergency incident.
NOTE 2   HLAP requirements for third-party services supporting eCall can be found in EN 16102, and have been developed in conjunction with the development of this work item, and is consistent in respect of the interface to the PSAP. This deliverable makes reference to those provisions but does not duplicate them.

In respect of pan-European eCall (operating requirements defined in EN 16072), this document defines the high-level application protocols, procedures and processes required to provide the eCall service using a TS12 emergency call over a circuit-switched mobile communications network.
NOTE 1   The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using a PLMN (such as ETSI prime medium) which supports the European harmonized 112/E112 emergency number (TS12 ETSI TS 122 003) and to provide a means of manually triggering the notification of an emergency incident.
NOTE 2   HLAP requirements for third-party services supporting eCall can be found in EN 16102, and have been developed in conjunction with the development of this work item, and is consistent in respect of the interface to the PSAP. This deliverable makes reference to those provisions but does not duplicate them.

Existing public and private distribution API specifications will be identified, where practicable, and summarised in a number of ways, including: ownership of specification, scope of API functionality, basis of data model and data categorisation used, management of reference data, commercial access rules to the specification, governance of the specification, existing examples of use for MaaS booking, coherence with existing CEN standards, potential for becoming a new CEN standard.

This document specifies the conceptual and logical data model and physical encoding formats for geographic databases for Intelligent Transport Systems (ITS) applications and services. It includes a specification of potential contents of such databases (data dictionaries for Features, Attributes and Relationships), a specification of how these contents shall be represented, and of how relevant information about the database itself may be specified (metadata).
The focus of this document is on ITS applications and services and it emphasizes road and road-related information. ITS applications and services, however, also require information in addition to road and road-related information.
EXAMPLE 1    ITS applications and services need information about addressing systems in order to specify locations and/or destinations. Consequently, information about the administrative and postal subdivisions of an area is essential.
EXAMPLE 2    Map display is an important component of ITS applications and services. For proper map display, the inclusion of contextual information such as land and water cover is essential.
EXAMPLE 3    Point-of-Interest (POI) or service information is a key feature of traveller information. It adds value to end-user ITS applications and services.
Typical ITS applications and services targeted by this document are in-vehicle or portable navigation systems, traffic management centres, or services linked with road management systems, including public transport systems.
The Conceptual Data Model has a broader focus than ITS applications and services. It is application independent, allowing for future harmonization of this document with other geographic database standards.

Existing public and private distribution API specifications will be identified, where practicable, and summarised in a number of ways, including: ownership of specification, scope of API functionality, basis of data model and data categorisation used, management of reference data, commercial access rules to the specification, governance of the specification, existing examples of use for MaaS booking, coherence with existing CEN standards, potential for becoming a new CEN standard.

This document specifies the conceptual and logical data model in addition to the physical encoding formats for geographic databases for Intelligent Transport Systems (ITS) applications and services. This document includes a specification of potential contents of such databases (data dictionaries for Features, Attributes and Relationships), a specification of how these contents are to be represented, and how relevant information about the database itself can be specified (metadata). This document further defines map data used in automated driving systems, Cooperative-ITS, and Multi-modal transport.
The focus of this document is firstly on emerging ITS applications and services, such as Cooperative-ITS and automated driving systems, and it emphasizes road, lane and relevant information on road and lane. However, ITS applications and services also require other information in addition to road and road-related information, which are provided as external databases to connect with GDF and to complement each other. Highly defined public transport databases, for instance, are indispensable in multi-modal transport applications and services in particular. Thus, this document focuses secondly on an expansion of the specification to connect with externally existing databases. It is particularly designed to connect a Transmodel (EN 12896-1 and EN 12896-2) conformant public transport database.
Typical ITS applications and services targeted by this document are in-vehicle or portable navigation systems, traffic management centres, or services linked with road management systems, including public transport systems.
The conceptual data model specified here has a broader focus than ITS applications and services. It is application independent, allowing for future harmonization of this model with other geographic database standards.

This part of the EN12896-X series (Transmodel-Part 10) takes into account the conceptual data model for the 'new modes' (vehicle pooling, vehicle sharing, taxis, vehicle rental) elaborated within CEN TS 17413 (Models and Definitions for New Modes) and is dedicated to be amended and re- published as a reference data model for the alternative modes of transport (Part 10 of the Public Transport Reference Data Model).
This new publication takes into account the revision of the conceptual model (published as CEN TS 17413) by the project team TC278 PT0303 working on the implementation of the 'new modes' model (NeTEx-Part5).
EN12896-10, supplementing the series of EN12896-X, establishes the semantic reference for the alternative modes data domain and thus facilitates the integration of these modes into the overall mobility environment, in particular into multimodal travel services (e.g. trip planning systems).

This document specifies the conceptual and logical data model in addition to the physical encoding formats for geographic databases for Intelligent Transport Systems (ITS) applications and services. This document includes a specification of potential contents of such databases (data dictionaries for Features, Attributes and Relationships), a specification of how these contents are to be represented, and how relevant information about the database itself can be specified (metadata). This document further defines map data used in automated driving systems, Cooperative-ITS, and Multi-modal transport.
The focus of this document is firstly on emerging ITS applications and services, such as Cooperative-ITS and automated driving systems, and it emphasizes road, lane and relevant information on road and lane. However, ITS applications and services also require other information in addition to road and road-related information, which are provided as external databases to connect with GDF and to complement each other. Highly defined public transport databases, for instance, are indispensable in multi-modal transport applications and services in particular. Thus, this document focuses secondly on an expansion of the specification to connect with externally existing databases. It is particularly designed to connect a Transmodel (EN 12896-1 and EN 12896-2) conformant public transport database.
Typical ITS applications and services targeted by this document are in-vehicle or portable navigation systems, traffic management centres, or services linked with road management systems, including public transport systems.
The conceptual data model specified here has a broader focus than ITS applications and services. It is application independent, allowing for future harmonization of this model with other geographic database standards.

This document specifies the conceptual and logical data model and physical encoding formats for geographic databases for Intelligent Transport Systems (ITS) applications and services. It includes a specification of potential contents of such databases (data dictionaries for Features, Attributes and Relationships), a specification of how these contents shall be represented, and of how relevant information about the database itself may be specified (metadata).
The focus of this document is on ITS applications and services and it emphasizes road and road-related information. ITS applications and services, however, also require information in addition to road and road-related information.
EXAMPLE 1    ITS applications and services need information about addressing systems in order to specify locations and/or destinations. Consequently, information about the administrative and postal subdivisions of an area is essential.
EXAMPLE 2    Map display is an important component of ITS applications and services. For proper map display, the inclusion of contextual information such as land and water cover is essential.
EXAMPLE 3    Point-of-Interest (POI) or service information is a key feature of traveller information. It adds value to end-user ITS applications and services.
Typical ITS applications and services targeted by this document are in-vehicle or portable navigation systems, traffic management centres, or services linked with road management systems, including public transport systems.
The Conceptual Data Model has a broader focus than ITS applications and services. It is application independent, allowing for future harmonization of this document with other geographic database standards.

This part of the EN12896-X series (Transmodel-Part 10) takes into account the conceptual data model for the 'new modes' (vehicle pooling, vehicle sharing, taxis, vehicle rental) elaborated within CEN TS 17413 (Models and Definitions for New Modes) and is dedicated to be amended and re- published as a reference data model for the alternative modes of transport (Part 10 of the Public Transport Reference Data Model).
This new publication takes into account the revision of the conceptual model (published as CEN TS 17413) by the project team TC278 PT0303 working on the implementation of the 'new modes' model (NeTEx-Part5).
EN12896-10, supplementing the series of EN12896-X, establishes the semantic reference for the alternative modes data domain and thus facilitates the integration of these modes into the overall mobility environment, in particular into multimodal travel services (e.g. trip planning systems).

This document provides a Guide to Intelligent transport system standards deliverables from CEN and ISO, and other associated deliverables from other SDOs, together with hotlinks to their source, and to other relevant and related information and Regulations.

This document specifies and defines component facets supporting the exchange and shared use of data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the modelling approach, data content, data structure and relationships.
This document is applicable to:
—   Traffic and travel information which is of relevance to road networks (non-urban and urban) ;
—   Public transport information that is of direct relevance to the use of a road network (e.g. road link via train or ferry service) ;
—   Traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS).
This document establishes specifications for data exchange between any two instances of the following actors:
—   Traffic Information Centres (TICs);
—   Traffic Control Centres (TCCs);
—   Service Providers (SPs);
—   Use of this document may be applicable for other actors.
This document series covers, at least, the following types of informational content:
—   Road traffic event information – planned and unplanned occurrences both on the road network and in the surrounding environment;
—   Operator initiated actions;
—   Road traffic measurement data, status data, and travel time data;
—   Travel information relevant to road users, including weather and environmental information;
—   Road traffic management information and instructions relating to use of the road network.
This Part of CEN/TS 16157 specifies the informational structures, relationships, association ends, attributes and associated data types required for publishing information about facilities within the DATEX II framework. This is specified as a DATEX II "Facilities" namespace, which is part of the DATEX II platform independent model, but this Part excludes those elements that are specified in EN 16157-2 (Location referencing) and EN 16157-7 (Common data elements).

This new work item will revise and extend the sixth part of the DATEX II Technical Specifications which defines three DATEX II parking-related publications and a truck parking profile and that supports the exchange of static as well as dynamic information about parking facilities and areas, including intelligent truck parking as defined by the Directive 2010/40/EU priority action e as well as urban parking as specified in action a.
The formerly used Level B extension will be replaced by a new namespace in the context of version 3.0 of DATEX II.
The publications are intended to support the exchange of informational content from the organisation performing measurements and collecting/eliciting basic data to other organisations providing ITS services or onward information exchange. It is the ambition to harmonise existing information models from different sources such as EasyWay deployment guidelines and truck parking initiatives, and to liaise with the stakeholders involved, especially with the Alliance for Parking Data Standards and CEN/TC 278 working group 3.

This document provides a Guide to Intelligent transport system standards deliverables from CEN and ISO, and other associated deliverables from other SDOs, together with hotlinks to their source, and to other relevant and related information and Regulations.

This new work item will revise and extend the sixth part of the DATEX II Technical Specifications which defines three DATEX II parking-related publications and a truck parking profile and that supports the exchange of static as well as dynamic information about parking facilities and areas, including intelligent truck parking as defined by the Directive 2010/40/EU priority action e as well as urban parking as specified in action a.
The formerly used Level B extension will be replaced by a new namespace in the context of version 3.0 of DATEX II.
The publications are intended to support the exchange of informational content from the organisation performing measurements and collecting/eliciting basic data to other organisations providing ITS services or onward information exchange. It is the ambition to harmonise existing information models from different sources such as EasyWay deployment guidelines and truck parking initiatives, and to liaise with the stakeholders involved, especially with the Alliance for Parking Data Standards and CEN/TC 278 working group 3.

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 a publication sub-model within the DATEX II model that supports the publication of electronic traffic regulations.
This publication is intended to support the exchange of informational content from road traffic authorities issuing traffic regulation orders and organisations implementing these orders to other organisations providing ITS services or onward information exchange.

This document specifies and defines component facets supporting the exchange and shared use of data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the modelling approach, data content, data structure and relationships.
This document is applicable to:
—   Traffic and travel information which is of relevance to road networks (non-urban and urban) ;
—   Public transport information that is of direct relevance to the use of a road network (e.g. road link via train or ferry service) ;
—   Traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS).
This document establishes specifications for data exchange between any two instances of the following actors:
—   Traffic Information Centres (TICs);
—   Traffic Control Centres (TCCs);
—   Service Providers (SPs);
—   Use of this document may be applicable for other actors.
This document series covers, at least, the following types of informational content:
—   Road traffic event information – planned and unplanned occurrences both on the road network and in the surrounding environment;
—   Operator initiated actions;
—   Road traffic measurement data, status data, and travel time data;
—   Travel information relevant to road users, including weather and environmental information;
—   Road traffic management information and instructions relating to use of the road network.
This Part of CEN/TS 16157 specifies the informational structures, relationships, association ends, attributes and associated data types required for publishing information about facilities within the DATEX II framework. This is specified as a DATEX II "Facilities" namespace, which is part of the DATEX II platform independent model, but this Part excludes those elements that are specified in EN 16157-2 (Location referencing) and EN 16157-7 (Common data elements).

The EN 16157 series specifies and defines component facets supporting the exchange and shared use of data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the modelling approach, data content, data structure and relationships.
The EN 16157 series is applicable to:
- traffic and travel information which is of relevance to road networks (non-urban and urban);
- public transport information that is of direct relevance to the use of a road network (e.g. road link via train or ferry service);
- traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS).
This series establishes specifications for data exchange between any two instances of the following actors:
- Traffic Information Centres (TICs);
- Traffic Control Centres (TCCs);
- Service Providers (SPs).
Use of this series can be applicable for use by other actors.
This series covers, at least, the following types of informational content:
- road traffic event information – planned and unplanned occurrences both on the road network and in the surrounding environment;
- operator initiated actions;
- road traffic measurement data, status data, and travel time data;
- travel information relevant to road users, including weather and environmental information;
- road traffic management information and instructions relating to use of the road network.
This part of the CEN/TS 16157 series specifies details of infrastructure for vehicle energy supply. The provided data model is separated into two publications for static and dynamic information. The static information regarding the infrastructure is not subject to frequent changes, whereas the dynamic part offers the ability to provide highly up-to-date information. The static part covers all relevant information on vehicle energy infrastructure, e.g. sites, stations and refill points for electric vehicles as well as petrol, gasoline or gas-based refuelling for vehicles. In terms of dynamic information, the availability of the infrastructure, possible faults and a price indication are covered.

The EN 16157 series specifies and defines component facets supporting the exchange and shared use of data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the modelling approach, data content, data structure and relationships.
The EN 16157 series is applicable to:
- traffic and travel information which is of relevance to road networks (non-urban and urban);
- public transport information that is of direct relevance to the use of a road network (e.g. road link via train or ferry service);
- traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS).
This series establishes specifications for data exchange between any two instances of the following actors:
- Traffic Information Centres (TICs);
- Traffic Control Centres (TCCs);
- Service Providers (SPs).
Use of this series can be applicable for use by other actors.
This series covers, at least, the following types of informational content:
- road traffic event information – planned and unplanned occurrences both on the road network and in the surrounding environment;
- operator initiated actions;
- road traffic measurement data, status data, and travel time data;
- travel information relevant to road users, including weather and environmental information;
- road traffic management information and instructions relating to use of the road network.
This part of the CEN/TS 16157 series specifies details of infrastructure for vehicle energy supply. The provided data model is separated into two publications for static and dynamic information. The static information regarding the infrastructure is not subject to frequent changes, whereas the dynamic part offers the ability to provide highly up-to-date information. The static part covers all relevant information on vehicle energy infrastructure, e.g. sites, stations and refill points for electric vehicles as well as petrol, gasoline or gas-based refuelling for vehicles. In terms of dynamic information, the availability of the infrastructure, possible faults and a price indication are covered.

This European Standard (EN 16157 series) specifies and defines component facets supporting the exchange and shared use of data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the modelling approach, data content, data structure and relationships.
This European Standard is applicable to:
-   Traffic and travel information which is of relevance to road networks (non-urban and urban),
-   Public transport information that is of direct relevance to the use of a road network (e.g. road link via train or ferry service),
-   Traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS).
This European Standard establishes specifications for data exchange between any two instances of the following actors:
-   Traffic Information Centres (TICs),
-   Traffic Control Centres (TCCs),
-   Service Providers (SPs),
Use of this European Standard may be applicable for use by other actors.
This European Standard series covers, at least, the following types of informational content:
-   Road traffic event information – planned and unplanned occurrences both on the road network and in the surrounding environment,
-   Operator initiated actions,
-   Road traffic measurement data, status data, and travel time data,
-   Travel information relevant to road users, including weather and environmental information,
-   Road traffic management information and instructions relating to use of the road network.
This part of the CEN/TS 16157 series specifies the informational structures, relationships, roles, attributes and associated data types required for publishing variable message sign information within the Datex II framework. This is specified in two publications, a DATEX II VMS Table Publication sub-model and a VMS Publication sub-model, which are part of the DATEX II platform independent model, but this part excludes those elements that relate to:
-   location information which are specified in EN 16157-2,
-   common information elements, which are specified in EN 16157-7,
-   situation information which are specified in EN 16157-3.
The VMS Table Publication supports the occasional exchange of tables containing generally static reference information about deployed VMS which enable subsequent efficient references to be made to pre-defined static information relating to those VMS. The VMS Publication supports the exchange of the graphic and textual content of one or several VMS plus any status information on device configuration that aid the comprehension of the informational content. This content is potentially subject to rapid change.
These publications are not intended to support the control or configuration of VMS equipment. Each is part of the DATEX II platform independent model.

This document specifies a global transport data management (GTDM) framework composed of
—     global transport basic data model,
—     global transport access control data model,
—     global transport function monitor data model, and
—     sensor and control network data model
to support data exchange between applications.
This document defines standardized data classes in a Global Transport Data Format (GTDF), and the means to manage them.
Application and role-based access control to resources in GTDF are specified in accordance with IEEE 1609.2 certificates.
This document specifies GTDM as an ITS-S capability which is an optional feature (ITS-capabilities are specified in ISO 24102-6).
The GT access control (GTAC) data model specifies access permissions to data and function control by defining role-based mechanisms.
The GT function monitor (GTFM) data model specifies a configuration method to generate a flow logic for monitoring purposes, e.g. observing data parameters with respect of a defined limit.

This document specifies a methodology to define ITS-S communication profiles (ITS-SCPs) based on standardized communication protocols to interconnect trusted devices. These profiles enable secure information exchange between such trusted devices, including secure low-latency information exchange, in different configurations. The present document, in order to exemplify the methodology, also normatively specifies some ITS-SCPs based on the methodology, yet without the intent of covering all possible cases. Further ITS-SCPs can be specified at a later stage.
Configurations of trusted devices for which this document defines ITS-SCP’s include:
a)   ITS station communication units (ITS-SCU) of the same ITS station unit (ITS-SU), i.e. station-internal communications;
b)   an ITS-SU and an external entity such as a sensor and control network (SCN), or a service in the Internet;
c)   ITS-SUs.
The specifications given in this document can be equally applied to secured and unsecured communications, being groupcast and unicast communications, being localized or networked communications.

This European Standard (EN 16157 series) specifies and defines component facets supporting the exchange and shared use of data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the modelling approach, data content, data structure and relationships.
This European Standard is applicable to:
-   Traffic and travel information which is of relevance to road networks (non-urban and urban),
-   Public transport information that is of direct relevance to the use of a road network (e.g. road link via train or ferry service),
-   Traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS).
This European Standard establishes specifications for data exchange between any two instances of the following actors:
-   Traffic Information Centres (TICs),
-   Traffic Control Centres (TCCs),
-   Service Providers (SPs),
Use of this European Standard may be applicable for use by other actors.
This European Standard series covers, at least, the following types of informational content:
-   Road traffic event information – planned and unplanned occurrences both on the road network and in the surrounding environment,
-   Operator initiated actions,
-   Road traffic measurement data, status data, and travel time data,
-   Travel information relevant to road users, including weather and environmental information,
-   Road traffic management information and instructions relating to use of the road network.
This part of the CEN/TS 16157 series specifies the informational structures, relationships, roles, attributes and associated data types required for publishing variable message sign information within the Datex II framework. This is specified in two publications, a DATEX II VMS Table Publication sub-model and a VMS Publication sub-model, which are part of the DATEX II platform independent model, but this part excludes those elements that relate to:
-   location information which are specified in EN 16157-2,
-   common information elements, which are specified in EN 16157-7,
-   situation information which are specified in EN 16157-3.
The VMS Table Publication supports the occasional exchange of tables containing generally static reference information about deployed VMS which enable subsequent efficient references to be made to pre-defined static information relating to those VMS. The VMS Publication supports the exchange of the graphic and textual content of one or several VMS plus any status information on device configuration that aid the comprehension of the informational content. This content is potentially subject to rapid change.
These publications are not intended to support the control or configuration of VMS equipment. Each is part of the DATEX II platform independent model.

This document specifies a global transport data management (GTDM) framework composed of
—     global transport basic data model,
—     global transport access control data model,
—     global transport function monitor data model, and
—     sensor and control network data model
to support data exchange between applications.
This document defines standardized data classes in a Global Transport Data Format (GTDF), and the means to manage them.
Application and role-based access control to resources in GTDF are specified in accordance with IEEE 1609.2 certificates.
This document specifies GTDM as an ITS-S capability which is an optional feature (ITS-capabilities are specified in ISO 24102-6).
The GT access control (GTAC) data model specifies access permissions to data and function control by defining role-based mechanisms.
The GT function monitor (GTFM) data model specifies a configuration method to generate a flow logic for monitoring purposes, e.g. observing data parameters with respect of a defined limit.

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 standard data concepts that comprise the "Minimum Set of Data" (MSD) to be transferred from a vehicle to a 'Public Safety Answering Point' (PSAP) in the event of a crash or emergency via an 'eCall' communication transaction.
Optional additional data concepts may also be transferred as part of the MSD.
The communications media protocols and methods for the transmission of the eCall message are not specified in this document.

This document is the fifth part of the DATEX II European Standard which deals with the publication sub-models within the DATEX II model that support the exchange of measured and elaborated information.
These publications are intended to support the exchange of informational content from the organization having the measured data and creating elaborated data to other organisations providing ITS services or onward information exchange. It also includes the exchange of static information about measurement sites.
This is specified in three sub-models, a DATEX II Measurement Site Table Publication sub-model, a DATEX II Measured Data Publication sub-model and a DATEX II Elaborated Data Publication sub-model.

This document specifies a methodology to define ITS-S communication profiles (ITS-SCPs) based on standardized communication protocols to interconnect trusted devices. These profiles enable secure information exchange between such trusted devices, including secure low-latency information exchange, in different configurations. The present document, in order to exemplify the methodology, also normatively specifies some ITS-SCPs based on the methodology, yet without the intent of covering all possible cases. Further ITS-SCPs can be specified at a later stage.
Configurations of trusted devices for which this document defines ITS-SCP’s include:
a)   ITS station communication units (ITS-SCU) of the same ITS station unit (ITS-SU), i.e. station-internal communications;
b)   an ITS-SU and an external entity such as a sensor and control network (SCN), or a service in the Internet;
c)   ITS-SUs.
The specifications given in this document can be equally applied to secured and unsecured communications, being groupcast and unicast communications, being localized or networked communications.

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 specifies the fast service announcement protocol (FSAP) for general purposes in ITS. It references and supports all features of ISO/TS 16460, especially supporting the service response message (SRM) and related features in addition to the service announcement message (SAM), which enables only very basic features.
FSAP supports locally advertised ITS services uniquely identified by an ITS application identifier (ITS-AID).
This document specifies message formats and related basic protocol procedures by reference to ISO/TS 16460, and further related protocol requirements for operation of FSAP in the context of an ITS station specified in ISO 21217.
This document illustrates its relations to service announcement protocols specified by ETSI TC ITS and IEEE.

This document specifies a generic position, velocity and time (PVT) service. It further specifies the PVT service within the ITS station (ITS-S) facilities layer (ISO 21217) and its interface to other functionalities in an ITS-S such as:
—     ITS-S application processes (ITS-S-APs), defined in ISO 21217;
—     the generic facilities service handler (FSH) functionality of the ITS station facilities layer, defined in ISO/TS 17429.
This document specifies:
—     a PVT service which, dependent on a specific implementation, uses a variety of positioning-related sources such as global navigation satellite systems (GNSSs, e.g. GALILEO, GLONASS and GPS), roadside infrastructure, cellular infrastructure, kinematic state sensors, vision sensors;
—     a PVT service which merges data from the above-mentioned positioning-related sources and provides the PVT output parameters (carrying the PVT information) including the associated quality (e.g. accuracy);
—     how the PVT service is integrated as an ITS-S capability of the ITS station facilities layer;
—     the interface function calls and responses (Service Access Point ? service primitives) between the PVT ITS-S capability and other functionalities of the ITS station architecture;
—     optionally, the PVT service as a capability of the ITS-S facilities layer; see ISO 24102-6;
—     an ASN.1 module C-itsPvt, providing ASN.1 type and value definitions (in Annex A);
—     an implementation conformance statement proforma (in Annex B), as a basis for assessment of conformity to this document.
NOTE    It is outside the scope of this document to define the associated conformance evaluation test procedures.

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 a generic position, velocity and time (PVT) service. It further specifies the PVT service within the ITS station (ITS-S) facilities layer (ISO 21217) and its interface to other functionalities in an ITS-S such as:
—     ITS-S application processes (ITS-S-APs), defined in ISO 21217;
—     the generic facilities service handler (FSH) functionality of the ITS station facilities layer, defined in ISO/TS 17429.
This document specifies:
—     a PVT service which, dependent on a specific implementation, uses a variety of positioning-related sources such as global navigation satellite systems (GNSSs, e.g. GALILEO, GLONASS and GPS), roadside infrastructure, cellular infrastructure, kinematic state sensors, vision sensors;
—     a PVT service which merges data from the above-mentioned positioning-related sources and provides the PVT output parameters (carrying the PVT information) including the associated quality (e.g. accuracy);
—     how the PVT service is integrated as an ITS-S capability of the ITS station facilities layer;
—     the interface function calls and responses (Service Access Point ? service primitives) between the PVT ITS-S capability and other functionalities of the ITS station architecture;
—     optionally, the PVT service as a capability of the ITS-S facilities layer; see ISO 24102-6;
—     an ASN.1 module C-itsPvt, providing ASN.1 type and value definitions (in Annex A);
—     an implementation conformance statement proforma (in Annex B), as a basis for assessment of conformity to this document.
NOTE    It is outside the scope of this document to define the associated conformance evaluation test procedures.