Intelligent transport systems - ESafety - Pan-European eCall operating requirements

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 'Public Land Mobile Networks'(PLMN) (such as GSM and UMTS), which supports the European pre-assigned emergency destination address (see normative references) and to provide a means of manually triggering the notification of an incident.
This document specifies the general operating requirements and intrinsic procedures for in-vehicle emergency call (eCall) services in order to transfer an emergency message from a vehicle to a Public Safety Answering Point (PSAP) in the event of a crash or emergency, via an eCall communication session and to establish a voice channel between the in-vehicle equipment and the PSAP.
Private third party in-vehicle emergency supporting services may also provide a similar eCall function by other means. The provision of such services are defined in EN 16102, and are outside the scope of this document.
The communications protocols and methods for the transmission of the eCall message are not specified in this document.
This document specifies the operating requirements for an eCall service. An important part of the eCall service is a Minimum Set of Data (MSD). The operating requirements for the MSD are determined in this document, but the form and data content of the MSD is not defined herein. A common European MSD is determined in EN 15722.
This document does not specify whether eCall is provided using embedded equipment or other means (for example in the case of aftermarket equipment).

Intelligente Verkehrssysteme - eSicherheit - Betriebsanforderungen für den gesamteuropäischen eCall

Systèmes de transport intelligents - eSafety - Exigences opérationnelles du service eCall paneuropéen

Inteligentni transportni sistemi - e-Varnost - Zahteve za delovanje vseevropskega elektronskega klica v sili

General Information

Status
Not Published
Publication Date
02-Apr-2025
Current Stage
4599 - Dispatch of FV draft to CMC - Finalization for Vote
Start Date
09-Sep-2024
Due Date
03-May-2025
Completion Date
09-Sep-2024

Relations

Buy Standard

Draft
prEN 16072:2024 - BARVE
English language
30 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)


SLOVENSKI STANDARD
01-julij-2024
Inteligentni transportni sistemi - e-Varnost - Zahteve za delovanje vseevropskega
elektronskega klica v sili
Intelligent transport systems - ESafety - Pan-European eCall operating requirements
Intelligente Verkehrssysteme - eSicherheit - Betriebsanforderungen für den
gesamteuropäischen eCall
Systèmes de transport intelligents - eSafety - Exigences opérationnelles du service eCall
paneuropéen
Ta slovenski standard je istoveten z: prEN 16072
ICS:
03.220.20 Cestni transport Road transport
13.200 Preprečevanje nesreč in Accident and disaster control
katastrof
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

DRAFT
EUROPEAN STANDARD
prEN 16072
NORME EUROPÉENNE
EUROPÄISCHE NORM
May 2024
ICS Will supersede EN 16072:2022
English Version
Intelligent transport systems - ESafety - Pan-European
eCall operating requirements
Systèmes de transport intelligents - eSafety - Exigences Intelligente Verkehrssysteme - eSicherheit -
opérationnelles du service eCall paneuropéen Betriebsanforderungen für den gesamteuropäischen
eCall
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/TC 278.
If this draft becomes a European Standard, CEN members are bound to comply with the CEN/CENELEC Internal Regulations
which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.

This draft European Standard was established by CEN in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC
Management Centre has the same status as the official 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, Türkiye and
United Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.

Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.

EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2024 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 16072:2024 E
worldwide for CEN national Members.

prEN 16072:2024 (E)
Contents Page
European foreword . 4
Introduction . 5
1 Scope . 7
2 Normative references . 7
3 Terms and definitions . 8
4 Symbols and abbreviations . 13
5 Conformance . 13
6 High level functional requirements . 13
6.1 General high level functional requirements . 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 . 15
6.2 eCall service chain . 15
6.2.1 General . 15
6.2.2 Actors in eCall service provision . 15
6.2.3 Privacy aspects . 16
6.2.4 Use of location and heading at PSAP . 16
7 Operational requirements . 16
7.1 General . 16
7.2 Liability . 17
7.3 Routing of an eCall . 17
7.3.1 General . 17
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 Location and direction . 19
7.6.1 Location data . 19
7.6.2 Data concerning direction and location . 19
7.7 Minimum Set of Data (MSD) . 20
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 of operation for automatic triggered 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 . 22
prEN 16072:2024 (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.1 Transport protocol . 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 . 24
7.12.5 Performance criteria – PSAP . 24
7.13 Establish voice channel . 24
7.13.1 General . 24
7.13.2 Service area issues . 25
7.13.3 Roaming requirements for service . 25
7.13.4 Acknowledgement of eCall . 25
7.14 Continuing availability . 25
7.15 PSAP response . 25
7.16 eCall termination . 25
7.16.1 General . 25
7.16.2 IVS redial . 25
7.16.3 PSAP call-back . 26
7.16.4 Record transaction . 26
8 Defences against attack . 26
8.1 Call line security . 26
8.2 Hoax calls . 27
8.3 False generation of eCalls . 27
8.4 End of life management . 27
8.5 Denial of service attack . 27
8.6 Malicious attack on PSAP . 27
9 Different and additional requirements for specific UNECE vehicle categories . 28
10 Test and conformance requirements . 28
10.1 General .
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.