eCall is an emergency call service that notifies the emergency services in case of a road accident through technology fitted into the vehicle.
Table of contents
eCall in a nutshell
eCall is an emergency call service that notifies the emergency services in case of a road accident. It can be generated either automatically via the activation of in-vehicle sensors or manually by vehicle passengers. It automatically sends data about the car, for example its location. This way, emergency services can arrive quicker and assist the occupants of the vehicle.
Why ecall?
There are situations in which eCall may be the only way to connect to 112. For example:
- When there are no witnesses of the accident and all occupants are injured
- In accidents involving serious injuries that limit the victim’s ability to communicate
eCall can reduce emergency response times by up to 40% in urban areas and 50% in rural areas, potentially saving thousands of lives each year and reducing the severity of road injuries. By enabling faster and more efficient accident management, eCall also helps to lower congestion costs caused by traffic incidents.
EU Legislation on ecall
The EU first defined requirements for PSAP infrastructure in 2013 with Delegated Regulation (EU) No 305/2013, ensuring all Member States could receive and process 112‑based eCalls by October 2017, ahead of the 2018 obligation for new vehicles to include eCall. As telecommunications networks evolved towards next‑generation 4G/5G technologies, the framework was updated in 2024 through Delegated Regulation (EU) 2024/1084, introducing Next‑Generation eCall (NG eCall) over packet‑switched networks. Since 2 May 2024, all newly deployed PSAP systems must support NG eCall, and by 1 January 2026, all existing PSAPs must be upgraded to process these calls and the associated Minimum Set of Data, while continuing to handle legacy circuit‑switched eCalls during the transition.
Commission Delegated Regulation (EU) 2024/1084 – updates the framework to introduce Next‑Generation (4G/5G) eCall and sets the PSAP compliance deadline of 1 January 2026. https://eur-lex.europa.eu/eli/reg_del/2024/1084/oj/eng
Commission Delegated Regulation (EU) No 305/2013 – establishes technical requirements for PSAP infrastructure to ensure EU-wide interoperability of 112‑based eCall services. https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX%3A32013R0305
Next Generation Ecall
The original eCall system was built for 2G and 3G networks, but as Europe transitions to 4G and 5G, a new standard is being deployed to ensure the continuity and reliability of in‑vehicle emergency communications. NG eCall operates over packet‑switched IP networks (IMS over LTE/5G), offering faster data transfer and improved interoperability.
All PSAPs must support NG eCall by January 2026, while continuing to handle older 2G/3G‑based eCalls during the migration period.
Standards for ecall
eCall relies on a wide range of European and international standards. CEN defines vehicle and PSAP operational requirements (e.g., MSD format, conformance testing), while ETSI, 3GPP, and IETF provide the telecom and IP protocol standards that enable Next‑Generation eCall (NG eCall) over 4G/5G networks.
This list is not exhaustive and highlights the most relevant standards currently referenced in EU legislation and industry practice. Further information and official documents can be found on the CEN, ETSI, 3GPP and IETF websites.
CEN Standards (Vehicle & PSAP Operations)
- EN 16072:2025 – Pan-European eCall operating requirements (service and MSD handling)
- EN 16062:2023 – High-Level Application Requirements for circuit‑switched eCall
- EN 17184:2024 – HLAP for NG eCall over IMS (4G/5G)
- EN 16454:2023 – End‑to‑end conformance testing for eCall systems
- EN 17240:2024 – Conformance testing for IMS-based NG eCall
- EN 15722:2020 – Minimum Set of Data (MSD) structure for eCall
ETSI Standards (Telecom & NG eCall Interoperability)
- ETSI TS 103 683 (v2.1.1 / 2024) – Interoperability tests for NG eCall over IMS
- ETSI TS 122 101 / TS 124 008 – Core network and signaling requirements for LTE eCall
- ETSI TS 123 167 – IMS emergency call handling procedures (adapted for NG eCall)
3GPP Specifications (Mobile Network & IMS Layer)
- 3GPP TS 23.167 – Architecture and functions for IMS emergency calls (basis for NG eCall)
- 3GPP TS 24.229 – SIP signaling for IMS emergency sessions (including eCall)
- 3GPP TS 29.228 / TS 29.229 – Diameter interfaces for IMS emergency services
IETF Standards (IP & Emergency Protocols)
- RFC 5031 – Uniform Resource Name (URN) for emergency services (e.g., urn:service:sos.ecall)
- RFC 6881 / RFC 6442 – LoST (Location-to-Service Translation) and location conveyance in emergency calls
- RFC 7852 – Additional data related to emergency calls (MSD-like information in IP calls)
