CEN/TS 17234:2018

Intelligent transport systems - eSafety - eCall: Tests to enable PSAPs to demonstrate conformance and performance

The scope of this document is to define conformance and performance tests to demonstrate whether a PSAPis in compliance with the eCall Regulations and Standards.
This deliverable:
a) identifies the MANDATORY tests specified within EN 16454 that are appropriate for a PSAP to demonstrate its conformance to EN 16454 in accordance with European Commission Delegated Regulation (EU) No 305/2013;
b) specifies tests to verify that a PSAP has procedures in place to identify and decode registered optional additional data concepts (3.5) included in the Minimum set of data (3.15);
c) provides OPTIONAL tests to measure aspects of PSAP performance in handling aspects of eCall.

Intelligente Verkehrssysteme - eSicherheit - eCall: Prüfungen, die Rettungsleitstellen die Darstellung von Konformität und Leistung ermöglichen

Der Zweck dieses Dokuments ist es, Konformitäts- und Leistungsprüfungen festzulegen, um zu belegen, ob eine Notrufzentrale die Bestimmungen und Normen für eCall erfüllt.
Dieses Dokument:
a)   bezeichnet die VERPFLICHTENDEN, von EN 16454 vorgegebenen Prüfungen, die für eine Notrufzentrale geeignet sind, um ihre Konformität mit EN 16454 nach der delegierten Verordnung (EU) Nr. 305/2013 der Europäischen Kommission zu belegen;
b)   legt die Prüfungen fest, um zu bestätigen, dass eine Notrufzentrale über Verfahren für die Identifizierung und Entschlüsselung registrierter ergänzender Datenkonzepte (3.5) verfügt, die im minimalen Datensatz (3.15) enthalten sind;
c)   bietet OPTIONALE Prüfungen zur Messung von Aspekten der Leistung der Notrufzentrale bei der Handhabung von eCall-Aspekten.

Systèmes de transport intelligents - eSécurité - eCall: Essais pour permettre aux PSAPs de démontrer leur conformité et leur performance

Inteligentni transportni sistemi - e-Varnost - e-Klic: Preizkusi, ki centrom za usklajevanje reševanja (PSAPs) omogočajo prikaz skladnosti in zmogljivosti

Namen tega dokumenta je določiti preizkuse skladnosti in zmogljivosti, ki pokažejo, ali so centri za usklajevanje reševanja (PSAPs) v skladu s predpisi in standardi e-Klica.
Ta dokument:
a) določa OBVEZNE preizkuse, določene v standardu EN 16454, ki so primerni za centre za usklajevanje reševanja, ki pokažejo, ali so skladni s standardom EN 16454 v skladu z Delegirano uredbo Komisije (EU) št. 305/2013;
b) določa preizkuse za preverjanje, ali ima center za usklajevanje reševanja določene postopke za identifikacijo in dekodiranje registriranih dodatnih podatkovnih konceptov (3.5), vključenih v »minimalni nabor podatkov« (3.15);
c) ponuja IZBIRNE preizkuse za merjenje vidikov delovanja centra za usklajevanje reševanja pri obravnavanju vidikov e-Klica.

General Information

• Status: Published
• Publication Date: 27-Nov-2018
• ICS: 03.220.20 - Road transport
• 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: 6060 - Definitive text made available (DAV) - Publishing
• Start Date: 28-Nov-2018
• Due Date: 17-Mar-2019
• Completion Date: 28-Nov-2018
• Ref Project: SIST-TS CEN/TS 17234:2019 - Intelligent transport systems - eSafety - eCall: Tests to enable PSAPs to demonstrate conformance and performance

Standards Content (Sample)

SLOVENSKI STANDARD
01-februar-2019
,QWHOLJHQWQLWUDQVSRUWQLVLVWHPLH9DUQRVWH.OLF3UHL]NXVLNLFHQWURP]D
XVNODMHYDQMHUHãHYDQMD36$3VRPRJRþDMRSULND]VNODGQRVWLLQ]PRJOMLYRVWL
Intelligent transport systems - eSafety - eCall: Tests to enable PSAPs to demonstrate
conformance and performance
Intelligente Verkehrssysteme - eSicherheit - eCall: Prüfungen, die Rettungsleitstellen die
Darstellung von Konformität und Leistung ermöglichen
Systèmes de transport intelligents - eSécurité - eCall: Essais pour permettre aux PSAPs
de démontrer leur conformité et leur performance
Ta slovenski standard je istoveten z: CEN/TS 17234:2018
ICS:
03.220.20 Cestni transport Road transport
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.

CEN/TS 17234
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
November 2018
TECHNISCHE SPEZIFIKATION
ICS 03.220.20; 35.240.60
English Version
Intelligent transport systems - eSafety - eCall: Tests to
enable PSAPs to demonstrate conformance and
performance
Systèmes de transport intelligents - eSécurité - eCall: Intelligente Verkehrssysteme - eSicherheit - eCall:
Essais pour permettre aux PSAPs de démontrer leur Prüfungen, die Rettungsleitstellen die Darstellung von
conformité et leur performance Konformität und Leistung ermöglichen
This Technical Specification (CEN/TS) was approved by CEN on 15 July 2018 for provisional application.

The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to
submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard.

CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS
available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in
parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey 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
© 2018 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 17234:2018 E
worldwide for CEN national Members.

Contents Page
European foreword . 4
Introduction . 5
1 Scope . 6
2 Normative references . 6
3 Terms and definitions . 7
4 Abbreviations . 11
5 Technical requirements . 12
5.1 Overview of eCall service provision . 12
5.2 Technical set-up of GSM/UMTS eCall . 12
5.3 Technical set-up of an IMS eCall . 13
6 Conformity assessment procedures for PSAPs . 13
6.1 Legal requirements . 13
6.2 Procedures . 14
7 Generic conformity assessment procedures for PSAPs — Generic eCall
component assessment — Conformance test . 14
8 CS conformity assessment procedures for PSAPs (GSM/UMTS) — eCall
Component Assessment — Conformance Test . 15
9 PS conformity assessment procedures for PSAPs (IMS) — eCall Component
Assessment — Conformance Test . 16
10 Optional Additional Data — Context . 16
10.1 General . 16
10.2 CTP 3.3.1 — PSAP supports OAD . 17
10.3 CTP 3.3.2 — PSAP supports most recent OAD . 18
11 Performance testing . 18
11.1 General . 18
11.2 Key performance indicators . 20
11.2.1 General . 20
11.2.2 Performance levels . 20
11.3 Tests for suppliers of equipment to PSAPs. 21
11.4 MSD transmission time for different channel conditions (GSM/UMTS CS)
(OPTIONAL) . 21
12 Conformance Requirements . 22
12.1 GSM/UMTS MSD transmission time (OPTIONAL) . 22
12.1.1 General . 22
12.1.2 Test purpose . 24
12.1.3 Method of test . 24
12.2 Suitability for use (OPTIONAL) . 26
12.2.1 General . 26
12.2.2 PSAP Key Performance Indicators (KPIs) (OPTIONAL) . 26
13 Security — Context . 31
14 Test Procedures — Definition of Test plan . 31
14.1 Planning of Test drives . 31
14.2 IVS . 31
14.3 Number of Calls . 31
14.4 PSAP . 32
14.5 Location . 32
14.6 Execution . 32
14.7 Result and analysis. 32
Bibliography . 33
European foreword
This document (CEN/TS 17234:2018) has been prepared by Technical Committee CEN/TC 278
“Intelligent transport systems”, the secretariat of which is held by NEN.
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 is complementary to EN 15722, EN 16072, EN 16062, and EN 16454.
According to the CEN/CENELEC Internal Regulations, the national standards organisations of
the following countries are bound to announce this Technical Specification: Austria, Belgium,
Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic
of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia,
Spain, Sweden, Switzerland, Turkey and the United Kingdom.
Introduction
eCall is an emergency call generated either automatically via activation of in-vehicle sensors or
manually by the vehicle occupants ; when activated it provides notification and relevant
(3.23)
location information to the most appropriate Public Safety Answering Point , by means of
(3.21)
mobile wireless communications networks , carries a defined standardized minimum set of
(3.16)
data (MSD) notifying that there has been an incident that requires response from the
(3.15)
emergency services, and establishes an audio channel between the occupants of the vehicle and
the most appropriate Public Safety Answering Point. eCall has been regulated to be installed and
available in all new model vehicles in Europe from 2018. Mobile Network operators have agreed
to forward these calls, and ‘Public Safety Answering Points’ are required by European Regulation
to be able to receive eCalls by 2017. A large aftermarket is also expected, and vehicle
manufacturers are also expected to voluntarily equip their existing model vehicles as well as
new models. eCall currently only covers light vehicles, but is expected to be expanded to cover
HGVs, long distance coaches, and powered two vehicle vehicles in the near future. eCall is
expected to be a significant contributor in the fight to reduce road deaths and serious injuries.
eCall is regulated in the European Commission Recommendation 2011/750/EU of
8 September 2011 on support for an EU-wide eCall service in electronic communication
networks for the transmission of in-vehicle emergency calls based on 112 (112-eCall),
(3.1)
Decision no 585/2014/EU of the European Parliament and of the council of 15 May 2014 on the
deployment of the interoperable EU-wide eCall service ; Commission Delegated
(3.9)
Regulation (EU) no 305/2013 of 26 November 2012 supplementing Directive 2010/40/EU of
the European Parliament and of the council with regard to the harmonized provision for an
interoperable EU-wide eCall, and Regulation (EU) 2015/758 of the European Parliament and of
the Council of 29 April 2015 concerning type-approval requirements for the deployment of the
eCall in-vehicle system based on the 112 service and amending Directive 2007/46/EC.
(3.14) (3.1)
These Regulations refer to, and are dependent on, the CEN Standards EN 15722:2015, Intelligent
transport systems — eSafety — eCall minimum set of data (MSD); EN 16062:2015, Intelligent
transport systems — ESafety — eCall high level application requirements (HLAP) using GSM/UMTS
circuit switched networks; EN 16072:2015, Intelligent transport systems — ESafety — Pan-
European eCall operating requirements; EN 16102:2011, Intelligent transport systems — eCall —
Operating requirements for third party support; EN 16454:2015, Intelligent transport systems —
ESafety — ECall end to end conformance testing. Standards are also in development to support
eCall using packet switched networks using IMS, eCall using cooperative ITS ‘ITS Stations, and
standards to broaden the scope of eCall to other classes of vehicle. ETSI standards deliverables
for communications networks provide the communications specifications that underpin these
application level standards.
EN 16454 provides the basis for conformance tests for all actors in the eCall chain.
Crucial to the success of eCall is the response offered by the 1st level PSAP and subsequent
responses from the emergency response chain.
Building on, and consistent to EN 16454, this deliverable provides a suite of conformance and
performance tests to enable PSAPs to claim conformance to the regulations and eCall Standards.
Unlike EN 16454, this standards deliverable also takes into account standards deliverables in
development to carry eCall over packet switched networks using IMS.
1 Scope
The scope of this document is to define conformance and performance tests to demonstrate
whether a PSAPis in compliance with the eCall Regulations and Standards.
This deliverable:
a) identifies the MANDATORY tests specified within EN 16454 that are appropriate for a PSAP
to demonstrate its conformance to EN 16454 in accordance with European Commission
Delegated Regulation (EU) No 305/2013;
b) specifies tests to verify that a PSAP has procedures in place to identify and decode
registered optional additional data concepts (3.5) included in the Minimum set of data (3.15);
c) provides OPTIONAL tests to measure aspects of PSAP performance in handling aspects of
eCall.
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:2015, Intelligent transport systems — eSafety — eCall minimum set of data (MSD)
EN 16062:2015, Intelligent transport systems — ESafety — eCall high level application
requirements (HLAP) using GSM/UMTS circuit switched networks
EN 16072:2015, Intelligent transport systems — ESafety — Pan-European eCall operating
requirements
EN 16102:2011, Intelligent transport systems — eCall — Operating requirements for third party
support
EN 16454:2015, Intelligent transport systems — ESafety — ECall end to end conformance testing
CEN/TS 17148, Intelligent Transport Systems — eSafety — ProForma eCall Agreement between
TPSP and PARES
CEN/TS 17184, Intelligent transport systems — eSafety — eCall High level application Protocols
(HLAP) using IMS packet switched networks
CEN/TS 17240, Intelligent transport systems — eSafety — eCall end to end conformance testing
for IMS packet switched based systems
ETSI TS 100 910 V8.20.0 (2005-11), Digital cellular telecommunications system (Phase 2+); Radio
Transmission and Reception (3GPP TS 05.05 version 8.20.0 Release 1999)
ETSI TS 103 412 V1.1.1 (2016-04), Mobile Standards Group (MSG); Pan-European eCall end to end
and in-band modem conformance testing; Prose test specification
ETSI TS 121 133, Universal Mobile Telecommunications System (UMTS); 3G Security; Security
Threats and Requirements (3G TS 21.133 version 3.1.0 Release 1999)
ETSI TS 122 101, Universal Mobile Telecommunications System (UMTS); Service aspects; Service
principles (3G TS 22.101 version 3.10.0 Release 1999)
ETSI TS 126 269, Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); eCall data transfer; In-band modem solution; Conformance
testing (3GPP TS 26.269 version 8.0.0 Release 8)
ETSI TR 126 969, Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); eCall data transfer; In-band modem solution;
Characterization report (3GPP TR 26.969 version 9.0.0 Release 9)
ETSI TS 151 010-1 V12.5.0 (2015-09), Digital cellular telecommunications system (Phase 2+);
Mobile Station (MS) conformance specification; Part 1: Conformance specification
(3GPP TS 51.010-1 version 12.5.0 Release 12)
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
single European emergency call number supporting Teleservice 12
[SOURCE: ETSI TS 122 003]
3.2
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.3
Conformity Assessment procedures for PSAPs
procedures as defined in the delegated regulation No. 305/2013 (Article 4) whereby 'Member
States shall designate the authorities that are competent for assessing the conformity of the
operations of the eCall PSAPs with the requirements listed in Article 3 and shall notify them to
the Commission' and whereby 'Conformity assessment shall be based on the part of the standard
‘Intelligent transport systems — eSafety — eCall end to end conformance testing’ (EN 16454)
that relates to PSAPs conformance to pan-European eCall'
3.4
data
representations of static or dynamic objects in a formalized manner suitable for communication,
interpretation, or processing by humans or by machines
Note 1 to entry: In packet switched networks, voice is carried in packets of data.
3.5
data concept
any of a group of data structures (i.e. object class, property, value domain, data elements ,
(3.4) (3.6)
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 ,
(3.1)
which is enhanced with location information of the calling user and which is not actually used
directly in the communication but sets indicators in the IMS call header that identifies the call as
an emergency call of type ‘eCall’ to the MNO
3.8
eCall
emergency call which is generated either automatically via activation of in-vehicle sensors or
manually by the vehicle occupants and which, when activated, provides notification and
(3.23)
relevant location information to the most appropriate Public Safety Answering Point , by
(3.21)
means of mobile wireless communications networks , carries a defined standardized minimum
(3.16)
set of data (MSD) notifying that there has been an incident that requires response from the
(3.15)
emergency services, and establishes an audio channel between the occupants of the vehicle and
the most appropriate Public Safety Answering Point
3.9
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
(3.17)
set of data to the PSAP
(3.15)
3.10
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
(3.24) (3.15)
to a Public Safety Answering Point and the establishment of an audio channel between the
(3.21)
vehicle and the PSAP
3.11
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 mobilize the needed resources to deal with
the emergency in question
3.12
emergency call response centre
term used in ITS Implementation Directive to mean Public Safety Answering Point (PSAP)
(3.21)
3.13
in-vehicle equipment
equipment within the vehicle that provides or has access to in-vehicle data required for the
(3.4)
minimum set of data and any other data that is to be sent as part of or complementary to the
(3.15)
minimum set of data to effect the eCall transaction via a public mobile wireless
(3.10)
communications network providing a link between the vehicle and a means of enacting the
(3.20)
eCall service via a public mobile wireless communications network
(3.9)
3.14
in-vehicle system
IVS
in-vehicle equipment together with the means to trigger, manage and effect the eCall
(3.13)
transaction
(3.10)
3.15
minimum set of data
standardized data concept comprising data elements of relevant vehicle generated data
(3.5) (3.6)
essential for the performance of the eCall service
(3.4) (3.9)
[SOURCE: EN 15722:2015]
3.16
mobile wireless communications network
wireless communications network with homogeneous handover between network access
(3.24)
points
(3.19)
3.17
most appropriate PSAP
destination for eCall 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 European
Standards Deliverable. A PSAP can be a Public Authority or a private service provider (3.22) operating on
behalf of the responsible authorities.
3.18
network access device
NAD
see mobile wireless communications network device
(3.16)
3.19
network access point
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.20
public mobile wireless communications network
mobile wireless communications network with access to a public telecommunications
(3.16)
network
3.21
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 .
(3.17)
Note 2 to entry: A number of different instantiations of PSAP service are supported within this European
Standards Deliverable.
3.22
service provider
physical and functional component responsible for providing telematics based services to its
subscribers
3.23
vehicle occupant(s)
person(s) inside the vehicle
3.24
wireless communications network
network operating using an air-interface capable of bi-directional transfer of data and or
(3.4)
voice
Note 1 to entry: There are different types of wireless communications such as PAN, LAN, cellular network
(3.2), etc. Particularly, some wireless communications are circuit switched (e.g. GSM,m UMTS), while others
are packet switched (e.g. E-UTRAN, LTE, 4G, etc.).
4 Abbreviations
For the purposes of this document, the following abbreviations and acronyms apply:
3GPP 3rd Generation Partnership Project
ACK ACKnowledgement
C/I carrier to interference ratio
COST207 channel model
CS circuit switched
CTP conformance test procedure
DTX discontinuous transmission exchange
EC European Commission
EN European standard
ETSI European Telecommunications Standards Institute
GSM global system for mobile communications
IMS Internet Protocol Multimedia Service
IVS in-vehicle system
(3.14)
KPI Key Performance Indicator
LAN local area network
LTE long term evolution (of 3G UMTS access network)
MNO mobile network operator
MSC mobile switching centre
MSD minimum set of data (3.15) (EN 15722)
NAD network access device (e.g. a GSM or UMTS module)
(3.18)
OAD Optional Additional Data (EN 15722)
PAN personal area network
PLMN public land mobile network
PS packet switched
PSAP Public Safety Answering Point (3.21)
RNC Radio Network Controller
TC# Test Case Number
Tk Timer to send MSD data
t Upper Bound timer
UB
TPS third party service
TPSP third party service provider
(3.22)
TS (i) technical specification
TS (ii) teleservice
TS12 Teleservice 12 ETSI TS 122 003
UE User equipment
UMTS universal mobile telecommunication system
USIM universal subscriber identity module
VLR visited location register
5 Technical requirements
5.1 Overview of eCall service provision
Figure 1 shows the overview of traditional (GSM/UMTS) eCall service provision:
(3.9)
Figure 1 — Overview of eCall service provision (Source: EN 16072)
5.2 Technical set-up of GSM/UMTS eCall
Figure 2 shows the technical set-up for circuit switched (CS) eCall using TS12 procedures as
specified in 3GPP Release 8 (ETSI TS 126 269). See EN 16062 for definition of these high level
application protocols, and EN 16072 for definition of the Requirements for eCall service
(3.9)
provision.
Figure 2 — CS eCall via GSM/UMTS (Source: EN 16062)
This specification provides a conformance test regime for 112-eCall (Pan European eCall). The
lower part in Figure 2 above shows the third party service (TPS) call with the optional
connection between a privately operated call centre and a PSAP. Conformance tests for so called
“Third Party System Provider” eCall are out with the scope of these specifications. For TPS eCall
see EN 16102, EN 16454 and CEN/TS 17148.
5.3 Technical set-up of an IMS eCall
Figure 3 shows the technical set-up for packet switched (PS) 112-eCall using IMS procedures as
specified in 3GPP Release 14 (ETSI TS 126 269). See CEN/TS 17184 for definition of these high
level application protocols, and EN 16072 for definition of the requirements for eCall service
(3.9)
provision.
Figure 3 — PS eCall via IMS (Source: CEN/TS 17184)
6 Conformity assessment procedures for PSAPs
6.1 Legal requirements
Commission Delegated Regulation (EU) No 305/2013, Article 3 defines the following eCall PSAP
requirements:
— Any eCall PSAP is equipped to handle eCalls and receive the MSD originating from the in-
vehicle equipment according to the standards EN 16072 and EN 16062.
(3.13)
— The eCall PSAP shall handle eCalls as expeditiously and effectively as any other call made to
the single European emergency number 112 . The eCall PSAP shall process eCalls in line
(3.1)
with the requirements of national regulations for emergency call processing.
— The eCall PSAP shall be able to receive the data contents of the MSD and present them to
(3.4)
the eCall PSAP operator clearly and understandably.
— The eCall PSAP shall have access to an appropriate Geographical Information System (GIS)
or equivalent system allowing the eCall PSAP operator to identify the position and heading
of the vehicle to a minimum degree of accuracy as defined in EN 15722 for the MSD
coordinates.
— The eCall PSAP shall be able to handle two way audio communication with the vehicle and
handle the eCall data .
(3.4)
— The eCall PSAP may reroute the call and MSD data to another PSAP, emergency control
(3.4)
centre or service partner.
(3.11)
6.2 Procedures
While many of the procedures for a PSAP to confirm conformance are common to both circuit
switched GSM/UMTS (EN 16062) systems and packet switched IMS systems, there are also some
different requirements.
Further, as IMS-eCall will only operate where there is an appropriate PLMN available (e.g. E-
UTRAN, UTRAN, GERAN, LAN, DOCSIS®, WiMAX™, cdma2000® and DVB-RCS2),
ETSI TS 122 101 provides a facility where, if such a network is not available or viable at the time
of the call, the eCall reverts to a GSM/UMTS circuit switched eCall, as specified in EN 16062, and
this also, in the event of failure, defaults to a standard 112 emergency voice call. PSAPs are
(3.1)
therefore required to support both circuit switched and packet switched eCall. The requirements
of Regulation (EU) No 305/2013 provide the framework for circuit switched systems.
At the time of developing this deliverable, EU Regulation does not yet require the support of
CEN/TS 17184 and particularly CEN/TS 17240.
At the time of developing this Standards deliverable, it is up to the Member State to determine if
IMS-eCall is supported within that country, and the procedures describing the support of IMS
packet switched networks are only relevant where the Member State has elected to offer eCall
support via IMS. Where this is not the case, tests relating to support of IMS-eCall are provided as
optional tests without any influence on success or failure for the assessment.
Where a Member State has elected to offer IMS eCall support, or in the event of an EU Regulation
requiring IMS support, these tests become mandatory in order to claim compliance with this
deliverable.
Generic conformance procedures which are applicable to both CS and PS routed eCalls are
defined in 7 below.
Conformance procedures specific for PSAPs receiving circuit switched eCalls are defined in 8
below.
Conformance procedures specific for PSAPs receiving packet switched eCalls are defined in 9
below.
7 Generic conformity assessment procedures for PSAPs — Generic eCall
component assessment — Conformance test
PSAP Conformity test cases for circuit switched 112-eCall are referenced to EN 16454.
PSAP Conformity test cases for packet switched 112-eCall (IMS-eCall) are referenced in
CEN/TS 17240.
Procedures for circuit switched 112-eCall shall be undertaken as specified in the referenced
conformance test procedures (CTP) specified in EN 16454:2015:
Procedures for packet switched 112-eCall shall be undertaken as specified in the referenced
conformance test procedure (CTP) specified in CEN/TS 17240. See Table 1:
Table 1 — Test case descriptions -General procedures
TC# Test Case Description Applicability
Provide MNOs with appropriate routing data
CTP 3.1.0.1 N/A
(3.4)
covered by suitability for use
CTP 3.1.0.2 Maintain map geo-information
KPI
8 CS conformity assessment procedures for PSAPs (GSM/UMTS) — eCall
Component Assessment — Conformance Test
Generic PSAP Conformity test cases are referenced in EN 16454.
Procedures shall be undertaken as specified in the referenced conformance test procedure (CTP)
specified in EN 16454:2015. See Table 2:
Table 2 — Test case descriptions - eCall communication components - GSM/UMTS
TC# Test Case Description Applicability
CTP 3.1.1.1 Receive automatically initiated eCall Applicable – PSAP equipped to detect eCall Flag
CTP 3.1.1.2 Receive manually initiated eCall Applicable – PSAP equipped to detect eCall Flag
CTP 3.1.2 Receive TS12 data (3.4): Caller ID and location Applicable
CTP 3.1.3.1 Recognize eCall and route to in-band modem Applicable
CTP 3.1.3.2 PSAP equipment failure Applicable
CTP 3.1.3.3 PSAP modem failure before link layer ACK is sent Applicable
CTP 3.1.4 eCall received at in-band modem Applicable
CTP 3.1.5.1 Validate initiation signal Applicable
CTP 3.1.5.2 Route to operator after T4 expiration Applicable
CTP 3.1.6 Request MSD Applicable
CTP 3.1.7.1 Receive MSD Applicable
CTP 3.1.7.2 Verify status bit in AL-ACK upon positive ACK Applicable
CTP 3.1.7.3 Verify MSD transfer upon T8 expiration Applicable
CTP 3.1.7.4 Verify transfer of corrupted MSD Applicable
CTP 3.1.7.5 Verify PSAP behaviour when MSD format check fails Applicable
CTP 3.1.9 Route voice and MSD to operator Applicable
CTP 3.1.10 Display TS12 eCall data (3.4) and MSD to operator Applicable
CTP 3.1.11 Decode VIN Applicable
CTP 3.1.12 Talk to vehicle occupants (3.23) Applicable
CTP 3.1.13 Request new MSD before call cleardown Applicable
CTP 3.1.14.1 Call cleardown Applicable
CTP 3.1.14.2 Verify status bit in AL-ACK upon cleardown Applicable
CTP 3.1.15 Call-back to vehicle Applicable
CTP 3.1.16 Request new MSD after call cleardown Applicable
9 PS conformity assessment procedures for PSAPs (IMS) — eCall
Component Assessment — Conformance Test
PSAP Conformity test cases are referenced in CEN/TS 17240.
Procedures shall be undertaken as specified in the referenced conformance test procedure (CTP)
specified in CEN/TS 17240. See Table 3.
Table 3 — Test case descriptions - eCall communication components for IMS
TC# Test Case Description Applicability
Applicable – PSAP equipped
CTP 3.1.1.1 IMS Receive automatically initiated eCall
to handle IMS
Applicable – PSAP equipped
CTP 3.1.1.2 IMS Receive manually initiated eCall
to handle IMS
Interpret IMS emergency eCall data
CTP 3.1.2 IMS Applicable
: Caller ID & location
(3.4)
CTP 3.1.3.2 IMS PSAP equipment failure Applicable
CTP 3.1.7.1 IMS Verify MSD transfer - Receive MSD Applicable
Verify status bit in AL-ACK upon Applicable
CTP 3.1.7.2 IMS
positive ACK
CTP 3.1.7.4 IMS Verify transfer of corrupted MSD Applicable
Verify PSAP behaviour when MSD Applicable
CTP 3.1.7.5 IMS
format check fails
CTP 3.1.9 IMS Route voice and MSD to operator Applicable
Display IMS eCall data and MSD to Applicable
(3.4)
CTP 3.1.10 IMS
operator
CTP 3.1.11 IMS Decode VIN Applicable
CTP 3.1.12 IMS Talk to vehicle occupants Applicable
(3.23)
Request new MSD before call Applicable
CTP 3.1.13 IMS
cleardown
CTP 3.1.14.1 IMS Call cleardown Applicable
CTP 3.1.15 IMS Call-back to vehicle Applicable
Request new MSD after call Applicable
CTP 3.1.16 IMS
cleardown
NOTE The applicability of this table will reviewed as soon as the final version of CEN/TS 17240 is
available.
PSAP network / ICT failure may be addressed at a later stage.
10 Optional Additional Data — Context
10.1 General
The Regulations require the MSD to be sent to/read by the PSAP. The MSD comprises the data
defined in EN 15722 and also makes provision to provide one or a number of ‘optional
(3.4)
additional data’ elements. Most of these are not standardized, but are defined in an available
data registry (currently www.esafetydata.com at the time of development of this Standards
Deliverable). Examples of OAD may be to provide the temperature of the battery of electric or
hybrid vehicles; a link to a website where wiring diagrams or other vehicle technical
specifications/diagrams can be obtained; in the case of HGVs, a link to a URL where the contents
of the cargo can be identified; identification of any ADR (Accord européen relatif au transport
international des marchandises Dangereuses par Route [dangerous goods]) goods on board;
(optionally and with consent) to a link to the number of a mobile telephone linked to the vehicle
at the time of the incident to the PSAP; etc.
This information is only helpful if it can be read/interpreted by the PSAP. This performance test
is to ensure that the PSAP can read, decode, and find by reference, the content of OAD data
concepts . This test does not prove interpretation of any particular OAD concept, but of the
(3.5)
mechanics to obtain OAD data See Tables 4 and 5.
(3.4).
10.2 CTP 3.3.1 — PSAP supports OAD
Table 4 — Test case descriptions - PSAP OAD interpretation
SUT reference PSAP OAD interpretation
CTP/ Verify whether PSAP can interpret OAD received
PSAP/CLR/3.1.15
SUT test objective The PSAP operator shall be able to access a recognized OAD database,
and obtain interpretation for OAD data concepts
(3.5)
CTP origin I_HeERO Conformity Assessment
Reference EN 16072:2015, 7.7.2
requirement
Initial conditions PSAP eCall software support system is operational
Stimulus and expected behaviour
Test point  Tester action Pass condition

IVS test point 1 TInitiate an eCall

MNO test point 2 eCall routed to the most appropriate PSAP
R(3.17)
PSAP SUT 3 eCall recognized as such, routed to in-band
modem, MSD correctly received, eCall
routed to an operator
PSAP SUT 4 Using OAD information in MSD, PSAP
system access to eCall OAD database (such
as www.esafetydata.com)
PSAP SUT 5 TVerify OAD information is correctly OAD information displayed
displayed in the PSAP operator’s interface in operator’s interface
If ALL individual pass
conditions listed in this
column above have been
met
THEN CTP PASS
ELSE CTP FAIL
10.3 CTP 3.3.2 — PSAP supports most recent OAD
Table 5 — 10.1.2.1 PSAP most recent OAD interpretation
SUT reference PSAP OAD interpretation
CTP/ Verify whether PSAP can interpret most recent OAD received
PSAP/CLR/3.1.15
SUT test objective The PSAP operator shall be able to access a recognized OAD database, and
obtain interpretation for OAD data concepts
(3.4)
CTP origin I_HeERO Conformity Assessment
Reference EN 16072:2015, 7.7.2
requirement
Initial conditions PSAP eCall software support system is operational
Stimulus and expected behaviour
Test point Tester action Pass condition
IVS test point 1 Initiate an eCall
MNO test point 2 eCall routed to the most appropriate PSAP R(3.17)
PSAP SUT 3 eCall recognized as such, routed to in-band
modem, MSD correctly received, eCall routed to
an operator
PSAP SUT 4 Using OAD information in MSD, PSAP system
access to eCall OAD database (such as
www.esafetydata.com)
PSAP SUT 5 PSAP SUT can demonstrate how it regularly Most recent OAD
updates its knowledge of OAD data R R information displayed
(3.4)
concepts or demonstrates subscription to a in operator’s interface
services that provides it with updates.
If ALL individual pass
Verify most recent OAD information is correctly
conditions listed in
displayed in the PSAP operator’s interface this column above
have been met
THEN CTP PASS
ELSE CTP FAIL
11 Performance testing
11.1 General
While the Regulation (Commission Delegated Regulation (EU) No 305/2013 of
26 November 2012 [DR 305/2013]) requires conformance, which can be achieved by the
EN 16454 tests specified in Clause 8 above in the case of GSM/UMTS communications, and in
Clause 9 above in the case of IMS communications; and whilst the provisions in Clause 10 above
provide assurance regarding ‘optional additional data’ content of the MSD, Regulation (EU)
No 305/2013 also requires an acceptable level of performance, as well as simple conformance.
While EN 16454 Intelligent transport systems — ESafety — ECall end to end conformance
testing, takes the approach to identify every stage transition of the eCall process, from triggering
within the vehicle, preparation of data , connection via the cellular telephone network, via the
(3.4)
MNO, to the PSAP, and handling and processing by the PSAP with a binary PASS/FAIL test which
is provided for every stage transition, Regulation (EU) No 305/2013 additionally infers and
requires satisfactory performance, which cannot be ensured by the EN 16454 tests alone.
Regulation (EU) No 305/2013 references (3) “Article 26 of Directive 2002/22/EC of the
European Parliament and of the Council of 7 March 2002 on universal service and users’ rights
relating to electronic communications networks and services (Universal Service Directive) (2)
requires that calls to the single European emergency call number 112 are answered
(3.1)
appropriately and handled in a manner that is best suited to the national organisation of
emergency systems, including the emergency call response centres (Public Safety Answering
(3.12)
Points )”
(3.21)
: (4) “The Communication from the Commission to the European Parliament, the Council,
the European Economic and Social Committee and the Committee of the Regions ‘eCall:
Time for deployment’ (3), envisages new regulatory measures to speed up the deployment of
an in-vehicle emergency call service in the Union. One of the proposed measures is to make the
necessary upgrading of the Public Safety Answering Point (PSAP) infrastructure required
(3.21)
for proper receipt and handling of eCalls mandatory.”
: (6) “It is expected that, by reducing the response time of the emergency services, the
interoperable EU-wide eCall will reduce the number of fatalities in the Union as well as the
severity of injuries caused by road accidents.”
: (7) “The interoperable EU-wide eCall is also expected to bring savings to society by
improving incident management and by reducing road congestion and secondary accidents.”
: (11) “It is important that all Member States should develop common technical solutions and
practices for the provision of emergency call services. The development of common technical
solutions should be pursued in particular through the European standardisation
organisations, in order to facilitate the introduction of the eCall service , ensure the
(3.9)
interoperability and continuity of the service throughout the Union, and reduce the costs of
implementation for the Union as a whole.”
And, while the issues of strict conformance to the regulation:
(Article 7.1) The eCall PSAPs must be able to demonstrate to the competent authorities that
they meet all specified conformance requirements of the eCall standards listed in Article 3(1) in
respect of the part(s) of the system under their design and/or control. They shall be liable only
for that part of the eCalls for which they are r
...