EN 16072 EUROPEANSTANDARD NORME EUROPEENNE EUROPAISCHE NORM April 2025 ICS 03.220.20; 35.240.60 Supersedes EN 16072:2022 English Version Intelligent transport systems - ESafety - Pan-European eCall operating requirements Systemes de transport intelligents - eSafety - Exigences Intelligente Verkehrssysteme - eSicherheit - opérationnelles du service eCall paneuropéen Betriebsanforderungen fur den gesamteuropaischen eCall This European Standard was approved by CEN on 7 March 2025. CENmembersareboundtocomplywiththeCEN/CENELECInternalRegulationswhichstipulatetheconditionsforgivingthis European Standard the statusof anational standard without any alteration.Up-to-date lists andbibliographical references concerningsuchnational standardsmaybeobtainedonapplicationtotheCEN-CENELECManagementCentreortoanyCEN member. This European Standard exists in three official versions (English, French, German). A version in any other language made by Centrehasthesamestatus as theofficial versions. CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkiye and United Kingdom. EUROPEANCOMMITTEEFORSTANDARDIZATION COMITEEUROPEENDENORMALISATION EUROPAISCHESKOMITEEFURNORMUNG CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels @2025CEN All rights of exploitation in any form and by any means reserved Ref. No.EN16072:2025 E worldwidefor CENnational Members EN 16072:2025 (E) Contents Page European foreword. Introduction. 1 Scope.. .7 2 Normative references.... 3 Terms and definitions. .8 4 Abbreviated terms... .13 5 Conformance... 13 6 High level functional requirements .. .13 6.1 13 6.1.1 General.... 13 6.1.2 Linguistic aspects. 14 6.1.3 High level In-vehicle system requirements..... 14 6.1.4 eCall architecture... 14 6.1.5 eCall operation sequence.. 6.2 15 6.2.1 General...... .15 6.2.2 Actors in eCall service provision ... .15 6.2.3 6.2.4 Use of location and heading at PSAP .... ..16 > Operational requirements.... 7.1 General.... .16 7.2 Liability... .17 7.3 Routing of an eCall.. 17 7.3.1 General 7.3.2 eCall 'flag'. .17 7.3.3 eCall routing to PSAP .18 7.4 Prioritization of an eCall .18 7.5 Post-crash performance of in-vehicle equipment. .18 7.6 Locationand direction.... 19 7.6.1 Location data .... .19 7.6.2 Data concerning direction and location ... 7.7 7.7.1 Data within the MSD... .20 7.7.2 Optional additional data ... .20 7.7.3 Notification of undecoded MSD data to PSAP operator.... .21 7.8 Modes ofoperationforautomatictriggered eCall... .21 7.9 In-vehicle 'Human Machine Interface' (HMI) aspects.. ..21 7.9.1 General.... 21 7.9.2 HMI aspects in the case of automatic triggering... 21 7.9.3 HMI aspects in the case of a manual triggering.... 21 7.9.4 Alerting of initiated eCall (automatically or manually triggered) 22 7.10 Triggering.... 22 7.10.1 Automatic eCall triggering strategy..... 2 EN 16072:2025 (E) 7.10.2 Manual eCall triggering strategy. 22 7.10.3 Manual termination of eCall by vehicle occupants before trigger confirmation. 22 7.11 Termination of an in progress eCall.. 23 7.12 Requirements to physical layer... 23 7.12.2 Performance requirements - time required to transmit data... 23 7.12.3 End-to-end performance criteria.... .23 7.12.4 Performance criteria - Wireless network..... 7.12.5 Performance criteria - PSAP 24 7.13 Establish voice channel 25 7.13.2 Service area issues. 7.13.3 Roaming requirements for service .. 25 7.14 Acknowledgement of eCal ... 7.15 Continuing availability 25 7.16 PSAP response 25 7.17 eCall termination 7.17.1 General 25 7.17.2 IVS redial.. 7.17.3 PSAP cal..back.. 7.17.4 Record transaction... .26 8 Defences against attack 8.1 Call line security... 8.2 Hoax calls..... ..27 8.3 False generation of eCa