SIST EN 16062:2023

SLOVENSKI STANDARD
01-november-2023
Nadomešča:
SIST EN 16062:2015
Inteligentni transportni sistemi - e-Varnost - Zahteve za visokokakovostni
aplikacijski protokol elektronskega klica v sili (HLAP) z uporabo komutiranega
omrežja GSM/UMTS
Intelligent transport systems - ESafety - eCall high level application requirements (HLAP)
using GSM/UMTS circuit switched networks
Intelligente Transportsysteme - ESicherheit - Anforderungen an High-Level-
Anwendungsprotokolle für eCall (HLAP) unter Verwendung von geschalteten
GSM/UTMS-Netzwerken
Systèmes de transport intelligents - ESafety - Exigences de protocole d'application de
haut niveau (HLAP) relatives à l'eCall via des réseaux commutés de circuits GSM/UMTS
Ta slovenski standard je istoveten z: EN 16062:2023
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.

EN 16062
EUROPEAN STANDARD
NORME EUROPÉENNE
August 2023
EUROPÄISCHE NORM
ICS 03.220.20; 13.200; 35.240.60 Supersedes EN 16062:2015
English Version
Intelligent transport systems - ESafety - eCall high level
application requirements (HLAP) using GSM/UMTS circuit
switched networks
Systèmes de transport intelligents - ESafety - Intelligente Transportsysteme - ESicherheit -
Exigences de protocole d'application de haut niveau Anforderungen an High-Level-Anwendungsprotokolle
(HLAP) relatives à l'eCall via des réseaux commutés de für eCall (HLAP) unter Verwendung von geschalteten
circuits GSM/UMTS GSM/UTMS-Netzwerken
This European Standard was approved by CEN on 24 July 2022.

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. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists 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.
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
© 2023 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 16062:2023 E
worldwide for CEN national Members.

Contents Page
European foreword . 4
Introduction . 5
1 Scope . 7
2 Normative references . 7
3 Terms and definitions . 8
4 Symbols and abbreviations .11
5 Conformance .12
6 General overview of the eCall transaction for Pan European eCall .14
7 Requirements .18
7.1 General requirements .18
7.1.1 General .18
7.1.2 USIM .18
7.1.3 Enabled PSAP .18
7.1.4 IVS configured only for eCall .18
7.1.5 Self-test .19
7.1.6 Standby mode applicable to IVS configured for eCall only .19
7.2 Activation .19
7.2.1 Activation of pan-European eCall .19
7.2.2 Activation of a test eCall .20
7.3 Call set-up.20
7.3.1 General .20
7.3.2 IVS network access device (NAD) already registered on PLMN .20
7.3.3 eCall in progress .20
7.3.4 Network selection and registration .20
7.3.5 Authentication of the subscriber .21
7.3.6 eCall establishment .21
7.3.7 Cell localization (by network) .21
7.3.8 Manual termination of eCall by vehicle occupants before trigger confirmation .22
7.4 MSD transfer .22
7.4.1 General .22
7.4.2 Send initiation signal from IVS eCall modem to PSAP.23
7.4.3 eCall modem synchronization .23
7.4.4 Request MSD by PSAP eCall modem to IVS eCall modem .24
7.4.5 Send MSD from vehicle IVS to PSAP eCall modem .24
7.4.6 Link layer error check .24
7.4.7 Link layer ACK from PSAP eCall modem to IVS eCall modem .24
7.5 Application layer acknowledgement (AL- ACK) .25
7.5.1 Following transmission of the MSD to the eCall PSAP application .25
7.5.2 PSAP acknowledges the MSD .25
7.5.3 No receipt of application layer ACK .25
7.5.4 Form of presentation of the AL-ACK .25
7.6 PSAP request “SEND MSD” .27
7.6.1 General .27
7.6.2 Before call clear-down .27
7.6.3 After call clear-down . 29
7.7 (void) . 29
7.8 Audio link to vehicle occupants . 29
7.9 eCall clear-down. 29
7.10 PSAP call back . 30
7.11 Rerouting to another PSAP/emergency control centre . 30
7.12 Handling non equipped situations / error cases . 31
7.12.1 MSD not transmitted correctly . 31
7.12.2 Network registration fails . 31
7.12.3 Call failure before the MSD is sent and acknowledged . 31
7.12.4 Mobile network not supporting eCall flag or not provided with routing tables . 31
7.12.5 PSAP modem failure . 32
7.12.6 PSAP network/ICT failure . 32
7.12.7 PSAP application failure . 32
7.12.8 PSAP operator does not respond . 32
7.12.9 No response if line engaged . 33
7.12.10 MSD not sent . 33
7.12.11 MSD not received . 33
7.12.12 Audio link not established . 33
7.12.13 Audio link established but subsequently fails . 34
7.12.14 Re-attempt in case of interrupted call . 34
7.12.15 Automatic repeat attempts . 34
7.12.16 IVS NAD does not receive call clear-down . 34
8 Third party services supported eCall (TPS-eCall) . 34
9 Defences against attack (Security provisions) . 35
10 Quality of service requirements . 35
11 Test and conformance requirements . 35
12 Marking, labelling and packaging . 35
13 Declaration of patents and intellectual property . 35
Annex A (normative) Table of timings . 36
Annex B (informative) (void) . 39
Annex C (informative) Test system strategies. 40
C.1 General . 40
C.2 Vehicle and PSAP equipment life cycle . 40
C.3 Laboratory environment . 41
C.4 OEM or third party test systems . 41
Bibliography . 43

European foreword
This document (EN 16062:2023) has been prepared by Technical Committee CEN/TC 278 “Intelligent
transport systems”, the secretariat of which is held by NEN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by February 2024, and conflicting national standards shall
be withdrawn at the latest by February 2024.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document supersedes EN 16062:2015.
The following changes have been introduced in this revision:
— Improvements in the precision of technical description and update of references;
— Improvements in (the readability of) certain figures, notably Figures 3 and 6;
— Contents in clause 7.7 was generic and was moved to EN 16072;
— Annex B had been voided, as it served no purpose.
Any feedback and questions on this document should be directed to the users’ national standards body.
A complete listing of these bodies can be found on the CEN website.
According to the CEN-CENELEC Internal Regulations, the national standards organisations of the
following countries are bound to implement this European Standard: 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 the United
Kingdom.
Introduction
An eCall is an emergency call generated either automatically via activation of in-vehicle sensors or
manually by the vehicle occupants; when activated, to provide notification and relevant location
information to the most appropriate Public Safety Answering Points (PSAP), by means of mobile wireless
communications networks and carries a defined standardized minimum set of data, notifying that there
has been an incident that requires response from the emergency services and establishes an audio
channel between the occupants of the vehicle and the most appropriate PSAP.
EN 15722 specifies a standardized MSD for eCall, and EN 16072 specifies pan-European eCall operating
requirements. (For third-party systems, EN 16102 specifies third-party services supporting eCall
operating requirements. See EC Communication on eCall Implementation 2009 [COM(2009) 434 final]
and Official Journal eCall Recommendation C_2011_6269, for more information).
The operating requirements for pan-European eCall are made using Public Land Mobile Networks
(PLMN) (such as GSM and 3G), as specified in a number of ETSI standards and technical specifications.
In order to provide the eCall service across a wireless network, high level application protocols are
required as an important essential element to effect this service provision. This document specifies the
protocols to put into effect the pan-European eCall operating requirements using GSM/UMTS circuit
switched PLMNs, and also identifies common elements that can be used in the link between third-party
services supporting eCall and PSAPs.
NOTE The term PSAP, which is most widely used in the eCall documentation, European Commission documents
etc., is used throughout this document and equates to the term emergency call response centre used in the ITS
Implementation Directive.
The European Committee for Standardization (CEN) draws attention to the fact that it is claimed that
compliance with this document may involve the use of patents concerning eCall given in this document.
The patents held may refer to the implementation of eCall in general using the specifications in this
document, but do not specifically directly refer to specifications of any of the clauses defined herein.
CEN takes no position concerning the evidence, validity and scope of these patent rights.
The holder of these patent rights has ensured to CEN that they are willing to negotiate licenses under
reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this
respect, the statement of the holder of these patent rights is registered with CEN. Information may be
obtained from:
Mr. Thomas R. Rouse VP QTL Patent Counsel QUALCOMM Incorporated
5775 Morehouse Drive
San Diego, California 92121. USA
Phone: +1-858-587-1121
Fax: +1-858-658-2503
Email: trouse@qualcomm.com
URL: www.qualcomm.com
and:
Mr. Thomas W. Davis Jr. General Council AIRBIQUITY Incorporated
1011 Western Avenue, Suite 600
Seattle, Washington 98104. USA
Phone: +1.206.219.2700
Fax: +1.206.842.9259
Toll-Free:+1.888.334.7741
Email: tdavis@airbiquity.com
URL: www.airbiquity.com
1 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 using
a TS12 emergency call over a circuit-switched mobile communications network.
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) 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, and have been
developed in conjunction with the development of this work item, and is consistent in respect of the interface to the
PSAP. This deliverable makes reference to those provisions but does not duplicate them.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
EN 15722:2020, Intelligent transport systems - ESafety - ECall minimum set of data
EN 16072, Intelligent transport systems - eSafety - Pan-European eCall operating requirements
EN 16102, Intelligent transport systems - eCall - Operating requirements for third party support
EN 16454, Intelligent transport systems - ESafety - ECall end to end conformance testing
ETSI TS 122 101, Universal Mobile Telecommunications System (UMTS); LTE; Service aspects; Service
principles (3GPP TS 22.101 [Release 8 or later]
ETSI TS 124 008, Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; Mobile radio interface Layer 3 specification; Core network
protocols; Stage 3 [Release 8 or later]
ETSI TS 126 267, Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); eCall data transfer; In-band modem solution; General description
[Release 8 or later]
ETSI TS 126 268, Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); eCall data transfer; In-band modem solution; ANSI-C reference code
[Release 8 or later]
ETSI TS 126 269, Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); eCall data transfer; In-band modem solution; Conformance testing
[Release 8 or later]
ETSI TS 122 003, Digital cellular communications system (Phase 2+); Universal Mobile Telecommunications
System (UMTS); LTE; Circuit Teleservices supported by a Public Land Mobile Network (PLMN) (Teleservice
12/TC12) /E12) [Release 8 or later]
ETSI TS 122 011, Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; Service accessibility [Release 8 or later]
ETSI TS 127 007, Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); AT command set for user equipment [Release 8 or later]
ETSI TS 122 071, Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; Location Services (LCS); Service description; Stage 1 [Release 8
or later]
ITU-T Recommendation G.168, Digital network echo cancellers
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at https://www.electropedia.org/
— ISO Online browsing platform: available at https://www.iso.org/obp
3.1
single European emergency call number supporting Teleservice 12
[SOURCE: ETSI TS 122 003]
3.2
call clear-down
termination of call and freeing up of line (usually achieved by hanging up the receiver or pressing ‘end
call’ or similar on screen)
3.3
cellular network
wireless communications network consisting of multiple adjacent access points (cells) with the capability
of homogeneous transfer of a communications session instance to an adjacent cell without significant
interruption to the session
3.4
data
representations of static or dynamic objects in a formalized manner suitable for communication,
interpretation, or processing by humans or by machines
3.5
data concept
any of a group of data structures (i.e. object class, property, value domain, data elements, message,
interface dialogue, association) referring to abstractions or things in the natural world that can be
identified with explicit boundaries and meaning and whose properties and behaviour all follow the same
rules
3.6
data element
single unit of information of interest about some (entity) class of interest considered to be indivisible in
a particular context
Note 1 to entry: a unit of information of interest can be a fact, proposition, observation, etc. Examples of an
(entity) class of interest are persons, places, processes, properties, concepts, states and events.
3.7
E112
emergency communications service using the single European emergency call number, 112, which is
enhanced with location information of the calling user TS12
3.8
eCall
emergency call generated either automatically via activation of in-vehicle sensors or manually by the
vehicle occupants
Note 1 to entry: when activated it provides notification and relevant location information to the most appropriate
Public Safety Answering Point, by means of mobile wireless communications networks, carries a defined standardized
minimum set of data (MSD) notifying that there has been an incident that requires response from the emergency
services, and establishes an audio channel between the occupants of the vehicle and the most appropriate Public
Safety Answering Point
3.9
eCall generator
occupant of a vehicle or equipment within a vehicle that has cause to trigger an eCall transaction by
automatic or manual means
3.10
eCall identifier
one of two information element bits (flags) included in the emergency call set-up message that may be
used by the mobile network to filter and route automatically and manually initiated eCalls to a designated
PSAP
3.11
eCall service
end-to-end emergency service to connect occupants of an affected vehicle to the most appropriate PSAP
via an audio link across a PLMN together with the transfer of a minimum set of data to the PSAP
3.12
eCall transaction
establishment of a mobile wireless communications session across a public wireless communications
network and the transmission of a minimum set of data from a vehicle to a public safety answering point
and the establishment of an audio channel between the vehicle and the PSAP
3.13
emergency control centre
unit which deals with emergency calls and which has the capacity to consider professionally the need for
response, and which has the provision to mobilise the needed resources to deal with the emergency in
question
3.14
emergency call response centre
term used in ITS Implementation Directive to mean Public Safety Answering Point (PSAP)
3.15
identifier
any label, symbol or token that names or identifies an entity or a collection of data or the means of
designating or referring to a specific instance of a data concept
3.16
in-vehicle equipment
equipment within the vehicle that provides or has access to in-vehicle data required for the minimum set
of data and any other data that is to be sent as part of or complementary to the minimum set of data to
effect the eCall transaction via a public mobile wireless communications network providing a link
between the vehicle and a means of enacting the eCall service via a public mobile wireless
communications network
3.17
in-vehicle equipment provider
provider of eCall in-vehicle equipment
Note 1 to entry: The in-vehicle equipment provider can be the vehicle manufacturer or the provider of
aftermarket equipment.
3.18
in-vehicle system
in-vehicle equipment together with the means to trigger, manage and effect the eCall transaction
3.19
minimum set of data
standardized data concept, defined in EN 15722, comprising data elements of relevant vehicle generated
data essential for the performance of the eCall service
3.20
mobile wireless communications network
wireless communications network with homogeneous handover between network access points
3.21
mobile wireless communications network device
device providing communications to a mobile wireless communications network with homogeneous
handover between network access points
3.22
most appropriate PSAP
PSAP defined beforehand by responsible authorities to cover emergency calls from a certain area or for
emergency calls of a certain type
Note 1 to entry: See also PSAP.
Note 2 to entry: A number of different instantiations of PSAP service are supported within this document. A PSAP
can be a Public Authority or a private service provider operating on behalf of the responsible authorities.
3.23
network access device (NAD)
see mobile wireless communications network device
3.24
network access points
beacon, antenna or similar source of signal propagation and receipt together with equipment to manage
communication sessions with users operating within the operating reach of the network access point and
provide connectivity for the users within the operating reach of the single access point to a wider
communications network
Note 1 to entry: A network access point may but does not need to provide homogeneous or heterogeneous
handover to another network access point.
3.25
public mobile wireless communications network
mobile wireless communications network with access to a public telecommunications network
3.26
Public Safety Answering Point (PSAP)
physical location working on behalf of the national authorities where emergency calls are first received
under the responsibility of a public authority or a private organization recognized by the national
government
Note 1 to entry: See also most appropriate PSAP.
Note 2 to entry: A number of different instantiations of PSAP service are supported within this document.
3.27
service provider
physical and functional component responsible for providing telematics-based services to its subscribers
3.28
vehicle manufacturer
entity which first assembles the vehicle and provides eCall equipment as part of its specification and
subsequently sells the vehicle directly or via an agent
3.29
vehicle occupant(s)
person(s) inside the vehicle
3.30
wireless communications network
network operating using an air-interface capable of bi-directional transfer of data and or voice
Note 1 to entry: There are different types of wireless communications such as PAN, LAN, cellular network, etc.
4 Symbols and abbreviations
3G third generation mobile telecommunication system
ACK ACKnowledgement
AIeC automatic initiated eCall
AT attention (part of modem instruction to dial as specified in ETSI TS 127 007)
BS bearer services
CAN controller-area network
CRC cyclic redundancy check
EC European Commission
ETSI European Telecommunications Standards Institute
GSM global system for mobile communications
HLR home location registry
HPLMN home public land mobile network
IAM initial address message
IMSI international mobile subscriber identity
IVS in-vehicle system
LAN local area network
LTE long term evolution (of 3G UMTS access network)
MIeC manually initiated eCall
MSC mobile switching centre
MNO mobile network operator
MSISDN mobile subscriber ISDN (integrated services digital network)
MSD minimum set of data (EN 15722)
NAD network access device (e.g. a GSM or UMTS module)
PAN personal area network
PLMN public land mobile network
PSAP public safety answering point
REQ REQuest
SUT system under test
TPS third party service
TPSP third party service provider
TS (i) technical specification
TS (ii) teleservice
TS12 Teleservice 12 ETSI TS 122 003
Tx transmit
UMTS universal mobile telecommunication system
USIM universal subscriber identity module
VLR visited location register
5 Conformance
This document makes no conformance specifications or requirements in respect of TPS eCall operating
requirements, and conformance requirements in respect of TPS eCall can be found in EN 16102.
The first step enabling the interoperability of the pan-European eCall system elements is to verify the
conformity of each element to the relevant pan-European eCall set of standards. In such cases, each
element becomes a system under test (SUT) which is tested against a reference conformance test system.
Two levels of conformity have to be achieved:
— conformity of the SUT to the network access standards, including support by the network of the eCall
identifier (flag) in accordance with ETSI TS 124 008, being used to achieve the routing and end to
end transport of information between the IVS responsible for the eCall system and the PSAP, and the
establishment maintenance and termination of an audio link between both using the 112 emergency
number;
— conformity of the SUT to the high level application protocol as specified in this document and
conformity to both EN 15722 and EN 16072.
Any test between a given vehicle type and/or communication network and/or PSAP shall be achieved
without interference to an operational emergency system, unless by prior arrangement.
The eCall system is composed of three distributed main subsystems comprising IVS responsible for the
eCall system, mobile network and PSAP, corresponding to SUT1, SUT2 and SUT3 respectively. Each SUT
shall be tested for conformance using the necessary subsystem simulators, as shown in Figure 1.

Figure 1 — End-to-End eCall system extended with conformance test system
Clause 11 provides the test and conformance requirements for both the IVS responsible for the eCall
system and the PSAP equipment. Network support for the eCall flag is necessary to ensure correct
filtering and optimal routing of eCalls to the required PSAP.
Consequently, at the transport network level, the conformance testing shall be simply achieved by
verifying that the eCalls are correctly routed to relevant PSAPs designated to handle them according to
their triggering sources (manual or automatic).
6 General overview of the eCall transaction for Pan European eCall
In the introduction to this document, eCall was described as “an emergency call generated either
automatically via activation of in-vehicle sensors or manually by the vehicle occupants (the eCall
generator); when activated, it establishes an audio channel between the occupants of the vehicle and the
most appropriate Public Safety Answering Point. This is achieved by means of mobile wireless
communications networks and carries a defined standardized minimum set of data, providing relevant
location information, notifying that there has been an incident that requires response from the
emergency services and opens the audio channel for dialogue between the occupants of the vehicle and
the most appropriate Public Safety Answering Point.
Pan-European eCall effects this service using a Circuit Teleservice supported by a Public Land Mobile
Network (PLMN) (Teleservice 12/TS12) ETSI TS 122 003.
NOTE 1 If the MSD is not sent or received for any reason then the eCall continues as a normal 112/E112
emergency call and is afforded the same protection and priority as a Teleservice 12 (ETSI TS 122 003) emergency
voice call. See 7.12.3.
Figure 2 shows an illustrative view of the pan-European eCall service, as defined in EN 16072; Figure 3
relates the existing standards to the eCall transaction.

Figure 2 — Illustrative view of pan-European eCall service
Figure 3 — Relationship of eCall transaction to standards
NOTE 2 For lists of standards referred to in Figure 3, see Clause 2.
After the establishment of an emergency voice call (112/E112) between a vehicle and a Public Safety
Answering Point (PSAP) the audio equipment comprising the microphone and loudspeaker in the vehicle
is disconnected from the line whilst the MSD is transmitted, within the voice band, to the PSAP data
processing equipment. An indication shall be given to the occupants of the vehicle that an eCall is in
progress. On completion of the MSD transfer the in-vehicle audio system is reconnected to the line and a
voice communication is established between the vehicle occupants and a PSAP operator. The incident
related information associated with the 112/E112 voice call, contained within the MSD, is made available
to the PSAP operator in the manner decided locally.
Following the initial resolution of the incident by the PSAP operator, the PSAP operator may clear-down
the call, however, the in-vehicle system (IVS responsible for the eCall system) remains registered on the
mobile network, for the period specified in EN 16072 and Annex A (see timer T9) to this document to
enable the PSAP or rescue services to call back the vehicle occupants.
The eCall service technical requirements, as they apply to the establishment of the TS12 emergency call
and the transfer of the in-band data, are as specified in ETSI TS 122 101 and ETSI TS 124 008. These
specifications also describe the use, by the mobile network, of the eCall flag identifier, needed to ensure
the correct filtering and routing of eCalls to a designated eCall capable PSAP. The eCall in-band modem,
used to transfer the MSD, is specified in ETSI TS 126 267 and ETSI TS 126 268.
Figure 4 provides a general overview of the process of sending an MSD from the IVS responsible for the
eCall system to the PSAP.
Figure 4 — General overview - MSD sent from IVS to PSAP – successful case
A more detailed explanation of the eCall transaction is contained within the following clauses together
with specific high-level application requirements.
Under normal circumstances, the stages of the pan-European eCall transaction that provide the service
can be described as comprising 9 steps:
a) Procedures following power-up and initialisation of the in-vehicle system;
b) Activation (of system);
c) Call set-up (including network selection and registration, authentication (home location registry),
cell localization (by network), identifying call type, make call, establish audio connection to PSAP
modem server);
d) MSD transfer (including disconnect microphone and loudspeaker in vehicle from the line, send
network echo canceller disabling tone (optional), send IVS INITIATION signal, synchronize, request
MSD, send MSD, error check), and link layer ACK (including stop MSD transmissions);
e) Application layer ACK;
f) Establish audio link (including check audio link to vehicle occupants, MSD visualization, rerouting to
another PSAP);
g) Clarification of the overall emergency situation and location;
h) Initiate incident resolution and inform vehicle occupants verbally that help is coming;
i) Call clear down.
Procedures also need to be defined by local or national authorities for failure exceptional causes such as:
— PSAP or rescue service call back (voice only) or 'SEND MSD’;
— MSD not transmitted correctly;
— false generation of eCalls;
— network registration fails;
— call failure;
— network not capable to support eCall flag;
— eCall routed to a non-equipped PSAP;
— PSAP modem failure;
— PSAP network/ICT failure;
— PSAP application failure;
— PSAP operator does not respond;
— MSD not sent;
— MSD not received;
— audio link not established;
— audio link established but subsequently fails;
— re-attempt in case of interrupted call;
— automatic repeat attempts;
— IVS responsible for the eCall system NAD does not receive clear-down;
— etc.
Procedures/protocols for other process features need also to be specified, such as:
— termination of manual eCall trigger before it has been confirmed by vehicle occupants;
— activation/deactivation of eCall equipment in the vehicle.
This document provides high level application protocols and procedures to enact the eCall service
provision in Clause 7. It specifies at “High Level”, because it is not the intention to determine how the
manufacturers detailed product design is affected, only the steps that need to be effected in order to
provide a consistent system in an interoperable open environment.
NOTE 3 Third party support for eCall provides the same end service (MSD + audio link between the occupants
of the vehicle and the PSAP), but by different means. Transitional arrangements for non-equipped MNOs and PSAPs
are also described.
7 Requirements
7.1 General requirements
7.1.1 General
The IVS responsible for the eCall system network access device (NAD) shall conform in all respects to the
applicable ETSI specifications and in particular to the requirements specified in ETSI TS 122 101 and
ETSI TS 124 008 with regard to this initial power-up procedure.
7.1.2 USIM
As specified in ETSI TS 122 101, an eCall IVS responsible for the eCall system NAD shall have a valid USIM.
The USIM enables the provision of the eCall service. The USIM can be configured only for eCall (in this
document referred to as “eCall only”), or a combination of eCall and commercial service provision.
7.1.3 Enabled PSAP
To be “eCall enabled”, a PSAP needs to be equipped with the necessary hardware and a software
application that can receive, process and make the MSD contents immediately available to its operators.
This can either be a dedicated eCall application or integration in the existing PSAP application. An eCall
enabled PSAP shall conform in all respects to the high-level application protocols as specified herein.
The eCall flag makes possible that the eCalls are routed to a dedicated number. This way, the PSAP can
distinguish the eCalls from the E112 calls. Figure 5 provides an illustration.

Figure 5 — Use of the eCall flag
The call-handling is to be achieved in line with local/national procedures/regulations, including the
regulations on confidentiality.
7.1.4 IVS configured only for eCall
If the IVS responsible for the eCall system is configured to make only eCalls then, in accordance with
ETSI TS 122 101 (Release 8 or later), the IVS responsible for the eCall system NAD shall not systematically
perform mobility management procedures, including registration on a PLMN, except when attempting to
initiate an eCall and during an emergency call, or to initiate a test or reconfiguration of the terminal during
a maintenance operation.
NOTE 1 The purpose of this restriction is to avoid network congestion due to large volumes of unnecessary
network registration, de-registration and location update signalling from terminals configured only to make eCalls.
NOTE 2 Manufacturers are advised to adopt strategies that do not overload the PLMN by simultaneously testing.
The access and use of test functions shall be as specified in UNECE regulation 144 (accident emergency
cal
...