Information service
35.240.60 IT applications in transport
New standards
EVS-EN 17184:2024+A1:2026
Intelligent transport systems - eSafety - eCall High level application protocols (HLAP) using IP Multimedia Subsystem (IMS) over packet switched networks
Scope: 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 via
a packet switched wireless communications network using IMS (IP Multimedia Subsystem) and
wireless access (such as LTE, NR and their successors).
This document assumes support of eCall using IMS over packet switched networks by an IVS and a
PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is
initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched
networks is not supported by an IVS or PSAP is out of scope of this document.
At some moment in time packet switched networks will be the only Public Land Mobile Networks
(PLMN) available. However as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12)
ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the
appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks
are available) are out of scope of this document.
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 or IMS packet switched network) 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.
This document makes reference to those provisions but does not duplicate them.
the high level application protocols, procedures and processes required to provide the eCall service via
a packet switched wireless communications network using IMS (IP Multimedia Subsystem) and
wireless access (such as LTE, NR and their successors).
This document assumes support of eCall using IMS over packet switched networks by an IVS and a
PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is
initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched
networks is not supported by an IVS or PSAP is out of scope of this document.
At some moment in time packet switched networks will be the only Public Land Mobile Networks
(PLMN) available. However as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12)
ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the
appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks
are available) are out of scope of this document.
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 or IMS packet switched network) 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.
This document makes reference to those provisions but does not duplicate them.
Base documents: EN 17184:2024+A1:2026
EVS-EN 17240:2024+A1:2026
Intelligent transport systems - ESafety - ECall end to end conformance testing for IMS packet switched based systems
Scope: This document defines the key actors in the eCall chain of service provision using IMS over packet switched networks (such as LTE/4G) as: 1) In-vehicle system (3.20) (IVS)/vehicle, 2) Mobile network Operator (MNO), 3) Public safety answering point (3.27) (PSAP), and to provide conformance tests for actor groups 1) - 3). NOTE 1 Conformance tests are not appropriate nor required for vehicle occupants (3.36), although they are the recipient of the service. NOTE 2 Third party eCall systems (TPS eCall) are not within the scope of this deliverable. This is because the core TPS-eCall (3.32) standard (EN 16102) does not specify the communications link between the vehicle and the TPS service provider (3.29). NOTE 3 These conformance tests are based an the appropriate conformance tests from EN 16454 which was published before Internet Protocol multimedia Systems (IMS) packet switched networks were available. This deliverable therefore replicates the appropriate tests from EN 16454 (and acknowledge their source); adapt and revise Conformance Test Protocols (CTP) from EN 16454 to an IMS paradigm; or provide new additional tests that are required for the IMS paradigm. Some 14 112-eCall (Pan European eCall) tests provided in EN 16454 are specific to GSM/UMTS circuit switched communications and not appropriate for the IMS paradigm and are therefore excluded from this deliverable. This document therefore provides a suite of ALL conformance tests for IVS equipment, MNO's, and PSAPS, required to ensure and demonstrate compliance to CEN/TS 17184. NOTE 4 Because in the event of non-viability or non-existence of an IMS supporting network at any particular time/location, IMS-eCall systems revert to CS networked eCall systems eCall via GSM/UMTS, IVS and PSAPs need to support, and prove compliance to both IMS and CS switched networks. The Scope covers conformance testing (and approval) of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.
Base documents: EN 17240:2024+A1:2026
Replaces: EVS-EN 17240:2024
ISO 21719-1:2026
Electronic fee collection — Personalization of on-board equipment (OBE) — Part 1: Framework
Scope: This document establishes a framework and specifies electronic fee collection (EFC) functions for the personalization process of on-board equipment (OBE) used for EFC.
The personalization process takes place within the domain of the entity that is responsible for the application in the OBE.
This document is applicable to the EFC interface, e.g. using dedicated short-range communication or integrated circuit(s) card, between the personalization equipment (PE) and OBE as shown in Figure 1.
This document does not cover the following:
whether the personalization functionality resides completely in the PE or whether this functionality instead resides in a central system, where the PE is more or less “transparent”;
the exact application command or message structures for the EFC personalization functionality (these are dependent on the communication media and are described in subsequent parts of the ISO 21719 series);
the test procedures for evaluation of an implementation for conformity to the requirements in this document;
setting-up of operating organizations (e.g. toll service provider, personalization agent, trusted third party).
NOTE Some of the issues listed above are subject to separate documents prepared by ISO/TC 204, CEN/TC 278 and the European Telecommunications Standards Institute – Electromagnetic compatibility and Radio Spectrum Matters (ETSI ERM).
The personalization process takes place within the domain of the entity that is responsible for the application in the OBE.
This document is applicable to the EFC interface, e.g. using dedicated short-range communication or integrated circuit(s) card, between the personalization equipment (PE) and OBE as shown in Figure 1.
This document does not cover the following:
whether the personalization functionality resides completely in the PE or whether this functionality instead resides in a central system, where the PE is more or less “transparent”;
the exact application command or message structures for the EFC personalization functionality (these are dependent on the communication media and are described in subsequent parts of the ISO 21719 series);
the test procedures for evaluation of an implementation for conformity to the requirements in this document;
setting-up of operating organizations (e.g. toll service provider, personalization agent, trusted third party).
NOTE Some of the issues listed above are subject to separate documents prepared by ISO/TC 204, CEN/TC 278 and the European Telecommunications Standards Institute – Electromagnetic compatibility and Radio Spectrum Matters (ETSI ERM).
Base documents:
Replaces: ISO/TS 21719-1:2018
ISO/TR 19482:2026
Intelligent transport systems — Smart streetlighting management platform for road traffic safety enhancement — Overview and use cases
Scope: This document establishes the smart streetlighting management platform (SSMP) as a representative case study, based on the Korean implementation. This document provides practical, non-normative reference information to support other countries considering the adoption of similar systems.
This document provides information on:
the system components of SSMP, the roles and functions of each individual component;
the classification, naming, descriptions, and operational procedures of traffic safety service use cases enabled by SSMP.
This document provides information on:
the system components of SSMP, the roles and functions of each individual component;
the classification, naming, descriptions, and operational procedures of traffic safety service use cases enabled by SSMP.
Base documents:
Replaced standards
ISO/TS 21719-1:2018
Electronic fee collection -- Personalization of on-board equipment (OBE) -- Part 1: Framework
Scope: ISO/TS 21719-1:2018 describes:
- an overall description of the EFC personalization process;
- a description of EFC functionality that can be used for personalization.
The personalization process takes place within the domain of the entity that is responsible for the application in the OBE.
- an overall description of the EFC personalization process;
- a description of EFC functionality that can be used for personalization.
The personalization process takes place within the domain of the entity that is responsible for the application in the OBE.
Base documents:
Replaced: ISO 21719-1:2026
EVS-EN 17240:2024
Intelligent transport systems - ESafety - ECall end to end conformance testing for IMS packet switched based systems
Scope: This document defines the key actors in the eCall chain of service provision using IMS over packet switched networks (such as LTE/4G) as:
1) In-vehicle system (3.20) (IVS)/vehicle,
2) Mobile network Operator (MNO),
3) Public safety answering point (3.27) (PSAP),
and to provide conformance tests for actor groups 1) - 3).
NOTE 1 Conformance tests are not appropriate nor required for vehicle occupants (3.36), although they are the recipient of the service.
NOTE 2 Third party eCall systems (TPS eCall) are not within the scope of this deliverable. This is because the core TPS-eCall (3.32) standard (EN 16102) does not specify the communications link between the vehicle and the TPS service provider (3.29).
NOTE 3 These conformance tests are based an the appropriate conformance tests from EN 16454 which was published before Internet Protocol multimedia Systems (IMS) packet switched networks were available. This deliverable therefore replicates the appropriate tests from EN 16454 (and acknowledge their source); adapt and revise Conformance Test Protocols (CTP) from EN 16454 to an IMS paradigm; or provide new additional tests that are required for the IMS paradigm. Some 14 112-eCall (Pan European eCall) tests provided in EN 16454 are specific to GSM/UMTS circuit switched communications and not appropriate for the IMS paradigm and are therefore excluded from this deliverable.
This document therefore provides a suite of ALL conformance tests for IVS equipment, MNO's, and PSAPS, required to ensure and demonstrate compliance to CEN/TS 17184.
NOTE 4 Because in the event of non-viability or non-existence of an IMS supporting network at any particular time/location, IMS-eCall systems revert to CS networked eCall systems eCall via GSM/UMTS, IVS and PSAPs need to support, and prove compliance to both IMS and CS switched networks.
The Scope covers conformance testing (and approval) of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.
1) In-vehicle system (3.20) (IVS)/vehicle,
2) Mobile network Operator (MNO),
3) Public safety answering point (3.27) (PSAP),
and to provide conformance tests for actor groups 1) - 3).
NOTE 1 Conformance tests are not appropriate nor required for vehicle occupants (3.36), although they are the recipient of the service.
NOTE 2 Third party eCall systems (TPS eCall) are not within the scope of this deliverable. This is because the core TPS-eCall (3.32) standard (EN 16102) does not specify the communications link between the vehicle and the TPS service provider (3.29).
NOTE 3 These conformance tests are based an the appropriate conformance tests from EN 16454 which was published before Internet Protocol multimedia Systems (IMS) packet switched networks were available. This deliverable therefore replicates the appropriate tests from EN 16454 (and acknowledge their source); adapt and revise Conformance Test Protocols (CTP) from EN 16454 to an IMS paradigm; or provide new additional tests that are required for the IMS paradigm. Some 14 112-eCall (Pan European eCall) tests provided in EN 16454 are specific to GSM/UMTS circuit switched communications and not appropriate for the IMS paradigm and are therefore excluded from this deliverable.
This document therefore provides a suite of ALL conformance tests for IVS equipment, MNO's, and PSAPS, required to ensure and demonstrate compliance to CEN/TS 17184.
NOTE 4 Because in the event of non-viability or non-existence of an IMS supporting network at any particular time/location, IMS-eCall systems revert to CS networked eCall systems eCall via GSM/UMTS, IVS and PSAPs need to support, and prove compliance to both IMS and CS switched networks.
The Scope covers conformance testing (and approval) of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.
Base documents: EN 17240:2024
Replaced: EVS-EN 17240:2024+A1:2026
EVS-EN 17184:2024
Intelligent transport systems — eSafety — eCall High level application protocols (HLAP) using IP Multimedia Subsystem (IMS) over packet switched networks
Scope: 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 via a packet switched wireless communications network using IMS (IP Multimedia Subsystem) and wireless access (such as LTE, NR and their successors).
This document assumes support of eCall using IMS over packet switched networks by an IVS and a PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched networks is not supported by an IVS or PSAP is out of scope of this document.
At some moment in time packet switched networks will be the only Public Land Mobile Networks (PLMN) available. However as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12) ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks are available) are out of scope of this document.
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 or IMS packet switched network) 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.
This document makes reference to those provisions but does not duplicate them.
the high level application protocols, procedures and processes required to provide the eCall service via a packet switched wireless communications network using IMS (IP Multimedia Subsystem) and wireless access (such as LTE, NR and their successors).
This document assumes support of eCall using IMS over packet switched networks by an IVS and a PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched networks is not supported by an IVS or PSAP is out of scope of this document.
At some moment in time packet switched networks will be the only Public Land Mobile Networks (PLMN) available. However as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12) ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks are available) are out of scope of this document.
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 or IMS packet switched network) 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.
This document makes reference to those provisions but does not duplicate them.
Base documents: EN 17184:2024
Replaced: EVS-EN 17184:2024+A1:2026
EVS-EN 17184:2024/AC2:2025
Intelligent transport systems - eSafety - eCall High level application protocols (HLAP) using IP Multimedia Subsystem (IMS) over packet switched networks
Scope: Corrigendum to EN 17184:2024
Base documents: EN 17184:2024/AC:2025
Replaced: EVS-EN 17184:2024+A1:2026