Information service
35.240 Applications of information technology
New standards
EVS-EN 18162:2026
Building Information Modelling (BIM) - Digital twins applied to the built environment - Concept and definitions
Scope: This document defines the concepts and definitions and is the first part of a set of standards to define the framework for digital twins in the built environment. It includes the terms and definitions, the relation with building information modelling and addresses the lack of standards for the qualitative specification of a digital twin, which can include geometric, attributive, structural and infrastructural quality, as applicable.
This document is based on the experiences obtained in use cases [1] and documents from other technical committees, including ISO/IEC 30173.
This document can be used in the development of other standards and in support of communications among diverse, interested parties or stakeholders. This initiative aims to define an ecosystem of digital twins opening the opportunity to release even greater value, using data for the public good.
This document is based on the experiences obtained in use cases [1] and documents from other technical committees, including ISO/IEC 30173.
This document can be used in the development of other standards and in support of communications among diverse, interested parties or stakeholders. This initiative aims to define an ecosystem of digital twins opening the opportunity to release even greater value, using data for the public good.
Base documents: EN 18162:2026
EVS-EN ISO 12052:2026
Health informatics - Digital imaging and communication in medicine (DICOM) including workflow and data management (ISO 12052:2026)
Scope: Within the field of health informatics, the DICOM (digital imaging and communication in medicine) standard addresses the exchange of digital images, and information related to the production and management of those images, between both medical imaging equipment and systems concerned with the management and communication of that information, such as Picture Archiving anc Communication System (PACS), Hospital Information System (HIS) and Radiology Information System (RIS).
This document is equivalent to part 1 of DICOM. As such, it normatively describes the content of DICOM (Clause 6) and the requirements to make a claim of conformance (Clause 5).
The DICOM standard is applicable to diagnostic medical imaging as practiced in radiology, cardiology, pathology, dentistry, ophthalmology and related disciplines, and image-based therapies such as interventional radiology, radiotherapy and surgery. It is also applicable to a wide range of image and non-image related information exchanged in clinical, research, veterinary, and other medical environments.
This document is equivalent to part 1 of DICOM. As such, it normatively describes the content of DICOM (Clause 6) and the requirements to make a claim of conformance (Clause 5).
The DICOM standard is applicable to diagnostic medical imaging as practiced in radiology, cardiology, pathology, dentistry, ophthalmology and related disciplines, and image-based therapies such as interventional radiology, radiotherapy and surgery. It is also applicable to a wide range of image and non-image related information exchanged in clinical, research, veterinary, and other medical environments.
Base documents: ISO 12052:2026; EN ISO 12052:2026
Replaces: EVS-EN ISO 12052:2017
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
CWA 18353:2026
Terminology definition for domain ontologies in materials science
Scope: This CWA defines a workflow how to define, review, and implement domain-specific terminology of an application in materials science and engineering (MSE) to support domain ontology creation.
The CWA covers:
- roles and responsibilities for terminology work;
- a stepwise process from scoping and term harvesting to publication and implementation;
- a structured term record with mandatory data categories (e.g. definition type, relations, sources);
- quality insurance and review gates; and
- implementation in terminology databases.
This CWA is applicable to industrial and research use cases across MSE sub-domains and languages. It is intended for terminology curators, domain experts, ontology engineers, and data stewards involved in terminology-driven ontology development.
The CWA covers:
- roles and responsibilities for terminology work;
- a stepwise process from scoping and term harvesting to publication and implementation;
- a structured term record with mandatory data categories (e.g. definition type, relations, sources);
- quality insurance and review gates; and
- implementation in terminology databases.
This CWA is applicable to industrial and research use cases across MSE sub-domains and languages. It is intended for terminology curators, domain experts, ontology engineers, and data stewards involved in terminology-driven ontology development.
Base documents: CWA 18353:2026
ISO/IEC TS 20071-41:2026
Information technology — User interface component accessibility — Part 41: Design and use of pictograms, photos, and icons in augmentative and alternative communication (AAC)
Scope: This document provides requirements and recommendations for the design and use of pictograms, photos, and icons in augmentative and alternative communication (AAC) in the information and communication technology (ICT) domain.
This document recognizes that AAC can be delivered on various sized devices including computer displays, tablets, and smart phones. It applies to pictograms, photos, and icons that can be used on a range of devices. It is not specific to particular devices or the particular software used.
This document focuses on the needs of those users who cannot use a natural language in written or spoken form to communicate with a peer group or the community as a whole. In facilitating communication with those other people, it also serves them.
This document recognizes that AAC can be delivered on various sized devices including computer displays, tablets, and smart phones. It applies to pictograms, photos, and icons that can be used on a range of devices. It is not specific to particular devices or the particular software used.
This document focuses on the needs of those users who cannot use a natural language in written or spoken form to communicate with a peer group or the community as a whole. In facilitating communication with those other people, it also serves them.
Base documents:
ISO/IEC 7816-9:2017/Amd 1:2026
Identification cards — Integrated circuit cards — Part 9: Commands for card management — Amendment 1: Data objects for quantum safe cryptography key management operations
Scope: Amendment to ISO/IEC 7816-9:2017
Base documents:
ISO/IEC TS 20071-40:2026
Information technology — User interface component accessibility — Part 40: Augmentative and alternative communication (AAC)
Scope: This document provides an introduction to and basic guidance on augmentative and alternative communication (AAC) in the information and communication technology (ICT) domain. It also provides common definitions and a framework for the development of further, more detailed guidance relating to aspects of these AACs.
This document recognizes that AAC can be delivered on various ICT devices and the importance of consistency for users across devices. It applies to AAC software and not the devices on which the software is used.
This document recognizes that AAC provides many users with a unique form of communication that is not necessarily based on any specific natural language.
This document recognizes that AAC can be delivered on various ICT devices and the importance of consistency for users across devices. It applies to AAC software and not the devices on which the software is used.
This document recognizes that AAC provides many users with a unique form of communication that is not necessarily based on any specific natural language.
Base documents:
ISO/TS 20738:2026
Genomics informatics — Requirements of data analysis for direct-to-consumer testing
Scope: This document specifies the requirements for genetic data analysis relating to direct-to-consumer (DTC) testing, including preprocessing, detection site, evaluation models, the use of databases and the elements of assessment reports.
This document applies to the analysis of genetic data from DTC testing without the involvement of a health care provider.
This document applies to the analysis of genetic data from DTC testing without the involvement of a health care provider.
Base documents:
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:
ISO/IEC TR 30123:2026
Internet of Things (IoT) — Guidance on IoT application to home healthcare
Scope: This document provides guidance on applying IoT technologies to home healthcare systems, taking into account the specific characteristics.
Base documents:
IEC 62264-2:2026
Enterprise-Control System Integration - Part 2: Object models and relationships for interfaces between manufacturing operations and business functions
Scope: IEC 62264-2:2026 specifies interface content exchanged between manufacturing control functions and other enterprise functions as interrelated information models. The information models are represented as an interrelated collection of conceptual object models which can be used for the implementation of applications with logical data and physical data models. The data exchanges in interfaces are scoped as between Level 3 manufacturing operations and Level 4 business systems in the hierarchical model defined in IEC 62264-1. The purpose of this document is to reduce the risk, cost, and errors associated with interface implementation.
Since this document covers many manufacturing operations and enterprise domains and there are many different standards for those domains, the semantics of this data exchange standard are described at a conceptual level intended to enable the other standards to be mapped to these semantics. To this end, this document defines a set of elements contained in the generic interface, together with a mechanism for extending the interface content for implementations.
The scope is limited to the definition of object models and attributes of the exchanged information defined in the IEC 62264-1.
This third edition cancels and replaces the second edition published in 2013. It is published as a double logo standard. This edition constitutes a technical revision. Due to the extent of the changes and updates, this document cannot ensure backward compatibility to implementations based on older editions. This edition includes the following significant technical changes with respect to the previous edition and ANSI/ISA 95.00.02-2018 (ED3):
a) object models are added for the use of interactive communications to notify subscribers about the occurrence of events and to provide context information about the event, making the information exchange more efficient and consistent. The added object models were the operations event model and operations record model.
b) operations location model and spatial definition attribute added to allow the description of operation locations.
c) operations test model added to define how test specifications and test results are related to testable objects, operations test requirements, actual resource, and work definitions.
d) definition of possible measurement uncertainty sub-attributes for all value, quantity and duration attributes defined in this document.
e) updated hierarchy scope model.
f) removed as separate models in this edition were the models for product definition, production schedule, production performance, and production capability. Their content is covered for all manufacturing operations management categories under operations models.
g) object model was added for the operations segment capability as a collection of resources related to other operations models.
h) updated relationship name and role name conventions established in 3.3.4 and implemented across all models and associated tables.
i) updated all objects’ relationship role table with explicit source and target names.
j) updated common header attributes for objects and property objects established in 4.5 and implemented across all models and associated tables.
k) updated explanation of the ‘relationships between resource reference objects in operations management information models and resource models. These additional resource relationships are added to all operations management models.
l) added an annex explanation for implementation options for specifying values in unit of measurement attribute.
m) added an annex explanation for implementation considerations for inheritance and persistence of data exchange object models.
Since this document covers many manufacturing operations and enterprise domains and there are many different standards for those domains, the semantics of this data exchange standard are described at a conceptual level intended to enable the other standards to be mapped to these semantics. To this end, this document defines a set of elements contained in the generic interface, together with a mechanism for extending the interface content for implementations.
The scope is limited to the definition of object models and attributes of the exchanged information defined in the IEC 62264-1.
This third edition cancels and replaces the second edition published in 2013. It is published as a double logo standard. This edition constitutes a technical revision. Due to the extent of the changes and updates, this document cannot ensure backward compatibility to implementations based on older editions. This edition includes the following significant technical changes with respect to the previous edition and ANSI/ISA 95.00.02-2018 (ED3):
a) object models are added for the use of interactive communications to notify subscribers about the occurrence of events and to provide context information about the event, making the information exchange more efficient and consistent. The added object models were the operations event model and operations record model.
b) operations location model and spatial definition attribute added to allow the description of operation locations.
c) operations test model added to define how test specifications and test results are related to testable objects, operations test requirements, actual resource, and work definitions.
d) definition of possible measurement uncertainty sub-attributes for all value, quantity and duration attributes defined in this document.
e) updated hierarchy scope model.
f) removed as separate models in this edition were the models for product definition, production schedule, production performance, and production capability. Their content is covered for all manufacturing operations management categories under operations models.
g) object model was added for the operations segment capability as a collection of resources related to other operations models.
h) updated relationship name and role name conventions established in 3.3.4 and implemented across all models and associated tables.
i) updated all objects’ relationship role table with explicit source and target names.
j) updated common header attributes for objects and property objects established in 4.5 and implemented across all models and associated tables.
k) updated explanation of the ‘relationships between resource reference objects in operations management information models and resource models. These additional resource relationships are added to all operations management models.
l) added an annex explanation for implementation options for specifying values in unit of measurement attribute.
m) added an annex explanation for implementation considerations for inheritance and persistence of data exchange object models.
Base documents:
Replaces: IEC 62264-2:2013
Replaced standards
IEC 62264-2:2013
Enterprise-control system integration - Part 2: Object and attributes for enterprise-control system integration
Scope: IEC 62264-2:2013 specifies generic interface content exchanged between manufacturing control functions and other enterprise functions. The interface considered is between Level 3 manufacturing systems and Level 4 business systems in the hierarchical model defined in IEC 62264-1. The goal is to reduce the risk, cost, and errors associated with implementing the interface. This second edition cancels and replaces the first edition published in 2004 and constitutes a technical revision. It includes the following technical:
- addition of object models for exchange information used in manufacturing operations management activities;
- displacement of the UML object models that were in IEC 62264-1:2003 into this standard so that the object models and the associated attribute tables were available in the same document;
- addition of the Hierarchy scope object definition to replace the Location attribute used in the previous edition;
- addition of a value type section to define the exchange of non-simple value types;
- definition of simple value types were defined using the ISO 15000-5.
- addition of object models for exchange information used in manufacturing operations management activities;
- displacement of the UML object models that were in IEC 62264-1:2003 into this standard so that the object models and the associated attribute tables were available in the same document;
- addition of the Hierarchy scope object definition to replace the Location attribute used in the previous edition;
- addition of a value type section to define the exchange of non-simple value types;
- definition of simple value types were defined using the ISO 15000-5.
Base documents:
Replaced: IEC 62264-2:2026
EVS-EN ISO 12052:2017
Health informatics - Digital imaging and communication in medicine (DICOM) including workflow and data management (ISO 12052:2017)
Scope: ISO 12052:2017, within the field of health informatics, addresses the exchange of digital images and information related to the production and management of those images, between both medical imaging equipment and systems concerned with the management and communication of that information.
ISO 12052:2017 facilitates interoperability of medical imaging equipment by specifying:
- for network communications, a set of protocols to be followed by devices claiming conformance to this document;
- the syntax and semantics of Commands and associated information which can be exchanged using these protocols;
- for media communication, a set of media storage services to be followed by devices claiming conformance to this document, as well as a File Format and a medical directory structure to facilitate access to the images and related information stored on interchange media;
- information that is to be supplied with an implementation for which conformance to this document is claimed.
ISO 12052:2017 does not specify:
- the implementation details of any features of the DICOM standard on a device claiming conformance;
- the overall set of features and functions to be expected from a system implemented by integrating a group of devices each claiming conformance to this document;
- a testing/validation procedure to assess an implementation's conformance to this document.
ISO 12052:2017 pertains to the field of medical informatics. Within that field, it addresses the exchange of digital information between medical imaging equipment and other systems. Because such equipment may interoperate with other medical devices and information systems, the scope of this document needs to overlap with other areas of medical informatics. However, this document does not address the full breadth of this field.
ISO 12052:2017 has been developed with an emphasis on diagnostic medical imaging as practiced in radiology, cardiology, pathology, dentistry, ophthalmology and related disciplines, and image-based therapies such as interventional radiology, radiotherapy and surgery. However, it is also applicable to a wide range of image and non-image related information exchanged in clinical, research, veterinary, and other medical environments.
ISO 12052:2017 facilitates interoperability of systems claiming conformance in a multi-vendor environment, but does not, by itself, guarantee interoperability.
ISO 12052:2017 facilitates interoperability of medical imaging equipment by specifying:
- for network communications, a set of protocols to be followed by devices claiming conformance to this document;
- the syntax and semantics of Commands and associated information which can be exchanged using these protocols;
- for media communication, a set of media storage services to be followed by devices claiming conformance to this document, as well as a File Format and a medical directory structure to facilitate access to the images and related information stored on interchange media;
- information that is to be supplied with an implementation for which conformance to this document is claimed.
ISO 12052:2017 does not specify:
- the implementation details of any features of the DICOM standard on a device claiming conformance;
- the overall set of features and functions to be expected from a system implemented by integrating a group of devices each claiming conformance to this document;
- a testing/validation procedure to assess an implementation's conformance to this document.
ISO 12052:2017 pertains to the field of medical informatics. Within that field, it addresses the exchange of digital information between medical imaging equipment and other systems. Because such equipment may interoperate with other medical devices and information systems, the scope of this document needs to overlap with other areas of medical informatics. However, this document does not address the full breadth of this field.
ISO 12052:2017 has been developed with an emphasis on diagnostic medical imaging as practiced in radiology, cardiology, pathology, dentistry, ophthalmology and related disciplines, and image-based therapies such as interventional radiology, radiotherapy and surgery. However, it is also applicable to a wide range of image and non-image related information exchanged in clinical, research, veterinary, and other medical environments.
ISO 12052:2017 facilitates interoperability of systems claiming conformance in a multi-vendor environment, but does not, by itself, guarantee interoperability.
Base documents: ISO 12052:2017; EN ISO 12052:2017
Replaced: EVS-EN ISO 12052:2026
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
Drafts
prEN 18352
Quality framework for internal data governance for participants in data spaces
Scope: This document defines a framework for assessing the quality of data governance and data management practices for participants in data spaces. It specifies the core principles, processes, and assessment elements that enable organizations to manage, monitor, and improve their data governance and data management practices.
The framework comprises two components:
• Process Reference Model: Defines key processes for data governance and data product management of data space participants, including its fundamental principles, structure, detailed process definitions, links to broader data governance, and required implementation measures.
• Process Assessment Framework: Outlines a model to evaluate process capability by establishing six distinct quality levels expressed in terms of capability levels, describing the corresponding profiles and guiding the systematic assessment.
This standard is aimed at supporting data governance and data management professionals, IT managers, quality assurance officers, and regulatory bodies.
This standard is applicable to organizations of all types and sizes.
The framework comprises two components:
• Process Reference Model: Defines key processes for data governance and data product management of data space participants, including its fundamental principles, structure, detailed process definitions, links to broader data governance, and required implementation measures.
• Process Assessment Framework: Outlines a model to evaluate process capability by establishing six distinct quality levels expressed in terms of capability levels, describing the corresponding profiles and guiding the systematic assessment.
This standard is aimed at supporting data governance and data management professionals, IT managers, quality assurance officers, and regulatory bodies.
This standard is applicable to organizations of all types and sizes.
Base documents: prEN 18352