EN 16062:2022

Intelligent transport systems - ESafety - eCall high level application requirements (HLAP) using GSM/UMTS circuit switched networks

In respect of pan-European eCall (operating requirements defined in EN 16072), this European Standard defines the high level application protocols, procedures and processes required to provide the eCall service using a TS12 emergency call over a 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.

Intelligente Transportsysteme - ESicherheit - Anforderungen an High-Level-Anwendungsprotokolle für eCall (HLAP) unter Verwendung von geschalteten GSM/UTMS-Netzwerken

Diese Europäische Norm legt die für den gesamteuropäischen eCall (Betriebsanforderungen festgelegt in EN 16072) geltenden übergeordneten Anwendungsprotokolle (en: high level application protocols, HLAP), Verfahrensweisen und Prozesse fest, die erforderlich sind, um den eCall-Dienst mit Hilfe eines über ein Mobilfunknetz erfolgenden TS12-Notrufs zu erbringen.
ANMERKUNG 1 Das Ziel der Implementierung des gesamteuropäischen fahrzeuginternen Notrufsystems (eCall) besteht darin, die Benachrichtigung über den Eintritt eines Verkehrsunfallereignisses europaweit mit denselben technischen Normen und denselben Dienstgütezielen durch Nutzung eines PLMN (wie z. B. primäres ETSI-Medium), welches die europäische harmonisierte 112/E112-Nutrufnummer (TS12 ETSI/TS 122 003) unterstützt, zu automatisieren. Zusätzlich soll ein Hilfsmittel für die manuelle Auslösung der Benachrichtigung über den Eintritt eines Notfalls zur Verfügung gestellt werden.
ANMERKUNG 2 HLAP-Anforderungen für „Drittparteiendienste, die eCall unterstützen“ können EN 16102 entnommen werden. Sie wurden im Zusammenhang mit der vorliegenden Arbeitseinheit entwickelt und sind im Hinblick auf die Schnittstelle mit der PSAP widerspruchsfrei. Das vorliegende Dokument nimmt Bezug auf diese Vorgaben, enthält aber keine Wiederholungen.

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

Dans le cadre de l’eCall paneuropéen (exigences de fonctionnement définies dans l’EN 16072), le présent document définit les protocoles d’application de haut niveau, les procédures et les processus nécessaires pour proposer le service eCall en utilisant un appel d’urgence TS12 via un réseau de communication pour mobiles.
NOTE 1 La mise en oeuvre du système paneuropéen d’appel d’urgence embarqué (eCall) a pour objectif d’automatiser la notification d’un accident de la route, partout en Europe, avec les mêmes normes techniques et les mêmes objectifs de niveau de service en utilisant un PLMN (tel qu’un réseau ETSI) qui prend en charge le numéro d’urgence européen 112/E112 harmonisé (TS12 ETSI/TS 122 003), mais également de fournir un moyen de déclenchement manuel de notification d’un incident.
NOTE 2 Les exigences HLAP relatives aux services privés prenant en charge l’eCall peuvent être consultées dans l’EN 16102. Elles ont été développées conjointement au présent document et en cohérence avec l’interface du PSAP. Le présent document fait référence à ces dispositions, mais ne fait pas double emploi.

Inteligentni transportni sistemi - e-Varnost - Zahteve za visoko stopnjo prednosti aplikacijskega protokola elektronskega klica v sili (HLAP) z uporabo komutiranega omrežja GSM/UMTS (2020)

General Information

• Status: Not Published
• Publication Date: 21-Aug-2022
• ICS: 03.220.20 - Road transport
• ICS: 13.200 - Accident and disaster control
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: CEN/TC 278 - Road transport and traffic telematics
• Drafting Committee: CEN/TC 278/WG 15 - eSafety
• Current Stage: 6055 - CEN Ratification completed (DOR) - Publishing
• Start Date: 24-Jul-2022
• Due Date: 20-Jun-2022
• Completion Date: 24-Jul-2022
• Directive: 2010/40/EU - 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 Text with EEA relevance
• Mandate: M/546 - [C(2016)808 Urban ITS (Intelligent Transport Systems in the field of road transport and for interfaces with other modes of transport)
• Ref Project: kSIST FprEN 16062:2022 - Intelligent transport systems - ESafety - eCall high level application requirements (HLAP) using GSM/UMTS circuit switched networks (2020)

Relations

• Revises: EN 16062:2015 - Intelligent transport systems - ESafety - eCall high level application requirements (HLAP) using GSM/UMTS circuit switched networks
• Effective Date: 19-Jan-2023

Standards Content (Sample)

SLOVENSKI STANDARD
oSIST prEN 16062:2021
01-januar-2021

Inteligentni transportni sistemi - e-Varnost - Zahteve za visoko stopnjo prednosti

aplikacijskega protokola elektronskega klica v sili (HLAP) z uporabo komutiranega

omrežja GSM/UMTS (2020)

Intelligent transport systems - ESafety - eCall high level application requirements (HLAP)

using GSM/UMTS circuit switched networks (2020)
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: prEN 16062
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
oSIST prEN 16062:2021 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
oSIST prEN 16062:2021
---------------------- Page: 2 ----------------------
oSIST prEN 16062:2021
DRAFT
EUROPEAN STANDARD
prEN 16062
NORME EUROPÉENNE
EUROPÄISCHE NORM
October 2020
ICS 03.220.20; 13.200 Will supersede EN 16062:2015
English Version
Intelligent transport systems - ESafety - eCall high level
application requirements (HLAP) using GSM/UMTS circuit
switched networks (2020)

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 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, Turkey 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

© 2020 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 16062:2020 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
oSIST prEN 16062:2021
prEN 16062:2020 (E)
Contents Page

European foreword ............................................................................................................................................. 4

Introduction .......................................................................................................................................................... 5

1 Scope .......................................................................................................................................................... 7

2 Normative references .......................................................................................................................... 7

3 Terms and definitions ......................................................................................................................... 8

4 Symbols and abbreviations .............................................................................................................12

5 Conformance .........................................................................................................................................13

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 ...........................................................................................................19

7.1.5 Self-test ...................................................................................................................................................19

7.1.6 Standby mode applicable to IVS configured for eCall only ..................................................19

7.2 Activation ...............................................................................................................................................20

7.2.1 Activation of pan-European eCall ..................................................................................................20

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 .........................................21

7.3.3 eCall in progress ..................................................................................................................................21

7.3.4 Network selection and registration ..............................................................................................21

7.3.5 Authentication of the subscriber ...................................................................................................21

7.3.6 eCall establishment ............................................................................................................................22

7.3.7 Cell localization (by network) ........................................................................................................22

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 ........................................................................................................24

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

---------------------- Page: 4 ----------------------
oSIST prEN 16062:2021
prEN 16062:2020 (E)

7.6.2 Before call clear-down ...................................................................................................................... 27

7.6.3 After call clear-down ......................................................................................................................... 29

7.7 PSAP application features ............................................................................................................... 29

7.7.1 General requirements ....................................................................................................................... 29

7.7.2 MSD display to the PSAP operator ................................................................................................ 29

7.7.3 PSAP operator user interface ......................................................................................................... 30

7.8 Audio link to vehicle occupants ..................................................................................................... 30

7.9 eCall clear-down.................................................................................................................................. 30

7.10 PSAP call back ...................................................................................................................................... 31

7.11 Rerouting to another PSAP/emergency control centre ........................................................ 31

7.12 Handling non equipped situations / error cases .................................................................... 32

7.12.1 MSD not transmitted correctly ...................................................................................................... 32

7.12.2 Network registration fails ............................................................................................................... 32

7.12.3 Call failure before the MSD is sent and acknowledged ......................................................... 32

7.12.4 Mobile network not supporting eCall flag or not provided with routing tables .......... 32

7.12.5 PSAP modem failure .......................................................................................................................... 33

7.12.6 PSAP network/ICT failure ............................................................................................................... 33

7.12.7 PSAP application failure ................................................................................................................... 33

7.12.8 PSAP operator does not respond .................................................................................................. 33

7.12.9 No response if line engaged ............................................................................................................ 34

7.12.10 MSD not sent ................................................................................................................................. 34

7.12.11 MSD not received ........................................................................................................................ 34

7.12.12 Audio link not established ...................................................................................................... 34

7.12.13 Audio link established but subsequently fails ................................................................. 35

7.12.14 Re-attempt in case of interrupted call ................................................................................ 35

7.12.15 Automatic repeat attempts ..................................................................................................... 35

7.12.16 IVS NAD does not receive call clear-down ......................................................................... 35

8 Third party services supported eCall (TPS-eCall) .................................................................. 35

9 Defences against attack (Security provisions) ......................................................................... 36

10 Quality of service requirements .................................................................................................... 36

11 Test and conformance requirements .......................................................................................... 36

12 Marking, labelling and packaging ................................................................................................. 36

13 Declaration of patents and intellectual property ................................................................... 36

Annex A (normative) Table of timings ....................................................................................................... 37

Annex B (informative) Summary abstracts of normative referenced documents ..................... 40

B.1 Objective ................................................................................................................................................ 40

B.2 Summary abstracts ............................................................................................................................ 40

Annex C (informative) Test system strategies......................................................................................... 51

C.1 General ................................................................................................................................................... 51

C.2 Vehicle and PSAP equipment life cycle ....................................................................................... 51

C.3 Laboratory environment ................................................................................................................. 52

C.4 OEM or third party test systems .................................................................................................... 52

Bibliography ....................................................................................................................................................... 54

---------------------- Page: 5 ----------------------
oSIST prEN 16062:2021
prEN 16062:2020 (E)
European foreword

This document (prEN 16062:2020) has been prepared by Technical Committee CEN/TC 278 “Intelligent

transport systems”, the secretariat of which is held by NEN.
This document is currently submitted to the CEN Enquiry.
This document will supersedes EN 16062:2015.
The following changes have been introduced in this revision:

— Improvements in the precision of technical description and update of references;

---------------------- Page: 6 ----------------------
oSIST prEN 16062:2021
prEN 16062:2020 (E)
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 European Standard

specifies the protocols to put into effect the pan-European eCall operating requirements using 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 European Standard may involve the use of patents concerning eCall given in this

European Standard.

The patents held may refer to the implementation of eCall in general using the specifications in this

European Standard, 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: [phone]
Fax: [phone]
Email: [e-mail]
URL: www.qualcomm.com
and:
Mr. Thomas W. Davis Jr. General Council AIRBIQUITY Incorporated
1011 Western Avenue, Suite 600
---------------------- Page: 7 ----------------------
oSIST prEN 16062:2021
prEN 16062:2020 (E)
Seattle, Washington 98104. USA
Phone: [phone]
Fax: [phone]
Toll-Free:+1.888.334.7741
Email: [e-mail]
URL: www.airbiquity.com

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights other than those identified above. CEN shall not be held responsible for identifying any or

all such patent rights.
---------------------- Page: 8 ----------------------
oSIST prEN 16062:2021
prEN 16062:2020 (E)
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 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 (MSD)

EN 16072:2020, Intelligent transport systems — eSafety — Pan-European eCall operating requirements

EN 16102:2020, Intelligent transport systems — eCall — Operating requirements for third party support

CEN/TS 16454:2020, 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]

---------------------- Page: 9 ----------------------
oSIST prEN 16062:2021
prEN 16062:2020 (E)

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 102 164, Telecommunications and Internet converged Services and Protocols for Advanced

Networking (TISPAN); Emergency Location Protocols (version 1.3.1)

ETSI/TS 151 010-1, Digital cellular telecommunications system (Phase 2+); Mobile Station (MS)

conformance specification; Part 1: Conformance specification (3GPP TS 51.010-1 version 8.1.0) [Release 8

or later]

ETSI/TS 121 133, Universal Mobile Telecommunications System (UMTS); 3G Security; Security Threats and

Requirements; (3GPP TS 21.133 version 4.1.0) [Release 4 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]

ISO/IEC 9646 (all parts), Information technology — Open Systems Interconnection — Conformance testing

methodology and framework
ITU–T:2009, 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 http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.1
112
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
---------------------- Page: 10 ----------------------
oSIST prEN 16062:2021
prEN 16062:2020 (E)
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 (such as a fact, proposition, observation, etc.) about some (entity)

class of interest (e.g. a person, place, process, property, concept, state, event) considered to be indivisible

in a particular context
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
---------------------- Page: 11 ----------------------
oSIST prEN 16062:2021
prEN 16062:2020 (E)
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 comprising data elements of relevant vehicle generated data essential for the

performance of the eCall service
[SOURCE: EN 15722:2011]
3.20
mobile wi
...