Skip to main content

eCall (RP 2026)

(A.) Policy and legislation

(A.1) Policy objectives

The pan-European in-vehicle emergency feature, ‘eCall’, is an interoperable service to be available in all new M1 and N1 model types of vehicles in order to reduce the consequences of accidents by better identification of the location of the accident and their faster rescue services. Since 1 April 2018, regulation have been in force and all new M1 and N1 model types of vehicles are equipped with eCall service devices. Since 1st October 2017, EU Members States have deployed eCall at Public Safety Answering Points (PSAPs) hardware and software to handle eCalls. According to Commission Delegated Regulation (EU) 2024/1180 new M1 and N1 vehicle types need to be equipped with an eCall system, which supports now eCall via packet switched (PS) networks (4G/5G) from 1st January 2026 onwards. According to Commission Delegated Regulation (EU) 2024/1084 new PSAPs need to be equipped with a system, which supports also eCall in PS domain (4G/5G) since 2nd May 2024. For already deployed PSAPs the Commission Delegated Regulation (EU) 2024/1084 applies from 1st January 2026 onwards. PSAPs also need to support eCalls using circuit-switched (CS) communication networks (2G/3G) as long as there is at least one CS telecommunication network in operation in the Member State.

(A.2) EC perspective and progress report

In the event of an accident, an in-vehicle device automatically triggers an eCall. A dataset is sent, providing information (the minimum set of data, or MSD) including the time, location and driving direction and other vehicle data via the mobile network to the most appropriate eCall PSAP. An audio connection is made with the European emergency number 112 and connects the PSAP with in-vehicle audio system to provide a bidirectional communication link. The eCall can also be triggered manually which provides the MSD and also builds up an audio connection to the PSAP.

Additional conformance, performance and periodic test standards are developed leveraging the transition from the CS to the PS domain in terms of connectivity and in-vehicle systems.

For other vehicle categories innovative solutions need to be found (e.g. powered 2-wheel vehicles- P2WVs, heavy goods vehicles, busses, etc.) where specific triggering mechanisms and algorithms are needed to meet the PSAP’s requirements (avoidance of high number of false calls). For those applications new standards are necessary and need to be developed.

The European eCall Implementation Platform (EeIP) is making recommendations to ensure the best operation of the service and to take full advantage of all its possibilities. Where eCall is implemented on mandatory basis (currently M1 and N1 vehicles), eCall is part of the vehicle type approval and roadworthiness testing.

Now as the public land mobile network (PLMN) and PSAP support networks are in place and operational, there is an aftermarket opportunity to bring the benefits of eCall to the current stock of vehicles throughout Europe.

However, as it will prove more difficult to control the performance and quality of such aftermarket devices, there is an urgent need to develop standards for the physical parameters, installation and operational performance of such aftermarket devices, to enable adequate certification. This will be essential to avoid PSAPs to be potentially inundated with false messages from such devices, and to increase the reliable and safe operation of such devices.

Subsequently (voluntary) technical specifications (TS) and European standards (EN) have been developed to extend the benefits of eCall to all categories of vehicles, and to migrate from 2G/3G communications to any wireless IP Multimedia Subsystem (IMS) communications media, and in special circumstances, to be even supported over satellite communications. They are referenced in extensions to the current regulations, if appropriate.

(A.3) References

  • Regulation (EU) 2015/758 of the European Parliament and of the Council of 29 April 2015 concerning type-approval requirements for the deployment of the eCall in-vehicle system based on the 112 service and amending Directive 2007/46/EC
  • Commission delegated regulation (EU) of 26 November 2012 305/2013 supplementing Directive 2010/40/EU of the European Parliament and of the Council with regard to the harmonised provision for an interoperable EU-wide eCall
  • Commission Delegated Regulation (EU) 2024/1084 of 6 February 2024 amending Delegated Regulation (EU) No 305/2013 supplementing Directive 2010/40/EU of the European Parliament and of the Council with regard to the harmonised provision for an interoperable EU-wide eCall
  • Commission Implementing Regulation (EU) 2017/78 of 15 July 2016 establishing administrative provisions for the EC type-approval of motor vehicles with respect to their 112-based eCall in-vehicle systems and uniform conditions for the implementation of Regulation (EU) 2015/758 of the European Parliament and of the Council with regard to the privacy and data protection of users of such systems
  • Commission Delegated Regulation (EU) 2017/79 of 12 September 2016 establishing detailed technical requirements and test procedures for the EC type-approval of motor vehicles with respect to their 112-based eCall in-vehicles systems, of 112-based eCall in-vehicle separate technical units and components and supplementing and amending Regulation (EU) 2015/758 of the European Parliament and of the Council with regard to the exemptions and applicable standards
  • Commission Delegated Regulation (EU) 2024/1180 of 14 February 2024 amending Regulation (EU) 2015/758 of the European Parliament and of the Council as regards the standards relating to eCall
  • COM 2011/750/EU: Commission Recommendation of 8 September 2011 on support for an EU-wide eCall service in electronic communication networks for the transmission of in-vehicle emergency calls based on 112 (eCalls)
  • 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
  • COM(2009) 434 final: eCall: Time for Deployment
  • Directive 2002/22/EC of the European Parliament and of the Council of 7 March 2002 on universal service and users' rights relating to electronic communications networks and services (Universal Service Directive).
  • Decision 585/2014 of the European Parliament and of the Council of 15 May 2014 on the deployment of the interoperable EU-wide eCall service Text with EEA relevance
  • Commission Delegated Regulation (EU) 2025/1871 of 23 July 2025 amending Regulation (EU) 2015/758 of the European Parliament and of the Council as regards the standards relating to eCall and amending Delegated Regulation (EU) 2017/79 as regards the technical requirements and test procedures for approval of motor vehicles equipped with 112-based eCall in-vehicle systems

Note: As an eCall is an emergency call, all relevant regulations applicable to emergency communication apply as well. See emergency communications section.

(B.) Requested actions

Action 1: SDOs to develop technical specification and standards for the implementation of eCall in vehicles of categories other than M1 and N1, taking into account requirements included within type-approval regulation.

Action 2: SDOs to lay down physical and operating requirements for aftermarket in-vehicle devices.

Action 3: SDOs to draft guidelines on certification of eCall Systems including aftermarket in-vehicle devices.

Action 4: SDOs to develop conformance and performance tests for recently developed technical specifications / standards for the provision of the eCall service eCall via shared vehicle platforms (C-ITS).

Action 5: SDOs to produce detailed conformity test specifications in support of certification schemes and periodic testing on IVS equipment.

Action 6: SDOs to carry out plugtest interoperability events, taking into account the technological evolution of the system.

Action 7: SDOs to collect feedback about the early versions of the standards and their implementation with technical representatives from vendors and implementers, in particular taking into account the evolution of the networks.

Action 8: SDOs to collect feedback from the relevant stakeholders on the real operation of the eCall service and when needed improve the standards, including through the European eCall Implementation Platform.

Action 9: SDOs to consider any changes to eCall that may be relevant in a 5G paradigm.

(C.) Activities and additional information

(C.1) Related standardisation activities

CEN

CEN/TC 278 WG 15 has developed several initial technical specifications (TS), EN standards, and other deliverables to enable and support eCall for all other categories of vehicle.

CEN/TC 278 WG15 has developed several technical specifications (TS), EN standards, and other deliverables to enable eCall via IMS networks.

CEN/TC 278 WG15 has started to develop several technical specifications (TS), EN standards, and other deliverables to provide optional additional data while retaining the privacy requirements of the eCall Regulation and GDPR in order to provide better useful information to assist PSAPs to manage the response to the incident.

CEN/TC 278 WG 15 has finalized EN standards, and her deliverables to enable and support eCall in PS domain or hybrid CS/PS (e.g. EN 17184, EN 17240 and EN 16072).

CEN/TC 278 WG 15 submitted a LS and asked 3GPP and ETSI to align certain 3GPP/ETSI requirements with the latest requirements in EN 17184:2024 and EN 17240:2024.

List of standards (status 2025-08):

  • EN 15722:2020 Intelligent transport systems - ESafety - ECall minimum set of data
  • EN 16062:2023 Intelligent transport systems - ESafety - eCall high level application requirements (HLAP) using GSM/UMTS circuit switched networks
  • EN 16072:2025 Intelligent transport systems - ESafety - Pan-European eCall operating requirements
  • EN 16454:2023 Intelligent transport systems - ESafety - ECall end to end conformance testing
  • CEN/TS 16405:2017 Intelligent transport systems - Ecall - Additional data concept specification for heavy goods vehicles
  • EN 16102:2011 Intelligent transport systems - eCall - Operating requirements for third party support
  • CEN/TS 17148 Intelligent Transport Systems - eSafety - ProForma eCall Agreement between TPSP and ERO
  • CEN/TS 17182:2018 Intelligent transport systems - eSafety - eCall via an ITS-station
  • EN 17184:2024 Intelligent transport systems - eSafety - eCall High level application Protocols (HLAP) using IMS packet switched networks
  • CEN/TS 17234:2018 Intelligent transport systems - eSafety - eCall: Tests to enable PSAPs to demonstrate conformance and performance
  • EN 17240:2024 Intelligent transport systems - eSafety - eCall end to end conformance testing for IMS packet switched based systems
  • CEN/TR 17249-1:2018 Intelligent transport systems - eSafety - extending eCall to other categories of vehicle
  • CEN/TS 17249-2:2018 Intelligent transport systems - eSafety:Part 2: eCall for HGVs and other commercial vehicles
  • CEN/TS 17249-3:2018 Intelligent transport systems - eSafety - Part 3:eCall for Coaches and busses
  • CEN/TS 17249-4:2019 Intelligent transport systems - eSafety - Part 4: eCall for UNECE Category T, R, S agricultural/forestry vehicles
  • EN 17249-5:2025 Intelligent transport systems - eSafety - Part 5: eCall for UNECE Category L1 and L3 powered two wheel vehicles (vehicle based)
  • CEN/TS 17249-6:2019 Intelligent transport systems - eSafety - Part 6: eCall for UNECE Category L2, L4, L5, L6 and L7 Tricycles and Quadricycles (vehicle based)
  • CEN/TS 17312:2019 Intelligent transport systems - eSafety - eCall via satellite telecommunications
  • CEN/TS 17313:2019 Intelligent transport systems - ESafety - Interoperability and user choice in eCall aftermarket and third party eCall services
  • EN 17358:2020 Intelligent transport systems - ESafety - eCall OAD for multiple Optional Additional Datasets
  • CEN/TS 17363:2019 Intelligent transport systems - ECall optional additional data - Linked mobile phone number data concept
  • CEN/TS 17642:2021 Intelligent Transport Systems - eSafety - eCall Interface for PSAPs to access cargo and dangerous goods databases
  • EN 17870:2023 Intelligent transport systems - eSafety - eCall additional data concept for equipment limitations
  • CEN/TS 17875:2022 Intelligent transport systems - eSafety - Incident Support Information System (ISIS) Architecture
  • EN 17905:2023 Intelligent transport systems - eSafety - eCall HLAP in hybrid circuit switched/packet switched network environments

Currently in approval procedures:

  • FprEN 18052 Intelligent transport systems - ESafety - ECall end to end conformance testing for eCall HLAP in hybrid circuit switched/packet switched network environments

ETSI

ETSI TC MSG has largely contributed to eCall specifications, contributing in the definition of the transport protocol to send MSD from the vehicle system to the PSAP via GSM or LTE. The STF 456 has looked at the issue of the migration of the Networks and has adopted and published ETSI TR 103 140.

ETSI TC MSG has published TS 103 683 “Next Generation eCall High Level Application Protocol (HLAP) Interoperability Testing”. This document was drafted by STF 568. A further enhancement of this specification (v2.1.1) was drafted by TTF T017.

ETSI TC MSG has published TS 103 412 v1.3.1 “Pan-European eCall end to end and in-band modem conformance testing”.

ETSI TC MSG has published TS 103 428 “eCall High Level Application Protocol (HLAP) Interoperability Testing”.

ETSI has supported and will support the organization of several eCall Test Fests and Plugtest events:

  • 6th eCall Plugtest (2017; Kranj, Slovenia)
  • 1st NG eCall Plugtests (2020; Kranj, Slovenia)
  • 2nd NG eCall Plugtests (2022; Kranj, Slovenia)
  • 6th NG112 Emergency Communications with NG eCall Plugtests (30.9.-4.10.2024 Malaga, Spain)

Pilots

CIP Pilots HeEROs (Harmonised eCall European Pilot) tested the standards in real conditions.

The iHeERO pilot under the 2014 CEF call for proposals is expected to produce relevant contributions for eCall standardisation.

ITU

Recommendation ITU-T P.1140 (2022): Speech communication requirements for emergency calls originating from vehicles.
https://www.itu.int/rec/T-REC-P.1140/en

ITU-T SG2 is responsible for Recommendation ITU-T E.212 "The international identification plan for public networks and subscriptions". Under the latest version of E.212, mobile network codes may be assigned to other applicants (e.g. for GSM-R networks) and these assignments are to be made according to procedures and criteria set by the national numbering plan administrator. It also encourages applications to the ITU's shared mobile country and network codes if networks and services are provided in more than one country. Use of global numbering resources for In Car Emergency Communication is under discussion in ITU-T Study Group 2. A statement on “global numbers used for the European eCall service” was published in ITU Operational Bulletin No.1155 of 1.IX.2018; TSB Circular 249 (2020) provides detailed background on in-car emergency services, such as eCall, and alerts national administrations, regulators and network operators that the ranges 883 130, 882 39 and 882 37 are being used for this service.

https://www.itu.int/md/T17-TSB-CIR-0249/en

The issue of ITU ranges for eCall services was also the subject of an ITU news article at https://news.itu.int/why-itu-assigned-numbering-ranges-are-critical-to-road-safety/ and video interview at https://youtu.be/VhA2S2ScJrw

ITU-T SG20 developed Recommendation ITU-T Y.4119 “Requirements and capability framework for IoT-based automotive emergency response system, Recommendation ITU-T Y.4467 “Minimum set of data structure for automotive emergency response system” and Recommendation ITU-T Y.4468 “Minimum set of data transfer protocol for automotive emergency response system”.

More info: https://itu.int/go/tsg20

ISO

ISO/TC 204: ITS. These cover standardisation of information, communication and control systems in the field of urban and rural surface transportation, including intermodal and multimodal aspects, traveller information, traffic management, public transport, commercial transport, emergency services and commercial services in the intelligent transport systems (ITS) field.

The project includes:

ISO/DIS 15638-10: ITS– Framework for cooperative Telematics Applications for Regulated commercial freight Vehicles (TARV) — Part 10: Emergency messaging system/eCall (EMS)

ISO/PWI 21344: ITS– Public transport — Emergency services eCall device for emergency on connected vehicles using ITS station

http://www.iso.org/iso/iso_technical_committee%3Fcommid%3D54706

IETF

The Emergency Context Resolution with Internet Technologies (ECRIT) Working Group has developed a general architecture for enabling IP applications to discover and connect to emergency services.

The Geographic Location/Privacy (GEOPRIV) Working Group has developed protocols that allow IP networks to inform end devices about their geolocation, a critical pre-requisite for emergency calling.

The application-specific working groups in the IETF (for example, the Session Initiation Protocol Core (SIPCORE) Working Group) have developed extensions to support emergency calling as required.

https://wiki.ietf.org/en/group/iab/Multi-Stake-Holder-Platform#h-325-ecall

(C.2) additional information

In respect of commercial vehicles and public transport vehicles, new recently developed Technical Specifications provide the possibility to link relevant related information (such as passenger numbers, commercial cargo type and detail, etc.), but further work may be required to enable and provide and exchange such information in a consistent manner to and between PSAPS, and provide additional information from sensors etc. In respect of public transport, innovative technologies may provide better assessment of the number of passengers involved, and additional specifications/standards may be needed to collect and present this detail to PSAPs in consistent and usable form.

Considerations need to be made for the provision of eCall in CCAM vehicles, especially to segregate eCalls from unmanned vehicles travelling between assignments from those where passengers are being transported in the vehicle.

As part of HeERO, EUCARIS (the European car and driving licence information system) has developed a module with which vehicle information can be exchanged internationally.

On the basis of the vehicle identification number (VIN), this module enables a link between the national vehicle registration authorities of the participating countries. When a foreign vehicle is involved in an accident, this module enables an instant Europe-wide search via EUCARIS to support the respective national 112 emergency centre(s).

[1] such as the eCall Testfest interoperability event which was held in Ostrava, Czech Republic, in November 2015 http://www.etsi.org/news-events/events/1002-4th-ecall-tesfest-2015