ETSI TS 103 428 V1.2.2 (2021-04)

Mobile Standards Group (MSG); eCall HLAP Interoperability Testing

RTS/MSG-001131

General Information

• Status: Not Published
• Technical Committee: MSG - Mobile Standards Group
• Current Stage: 12 - Completion
• Due Date: 23-Apr-2021
• Completion Date: 16-Apr-2021

Standards Content (Sample)

TECHNICAL SPECIFICATION
Mobile Standards Group (MSG);
eCall HLAP Interoperability Testing

2 ETSI TS 103 428 V1.2.2 (2021-04)

Reference
RTS/MSG-001131
Keywords
ecall, interoperability, testing

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2021.
All rights reserved.
ETSI
3 ETSI TS 103 428 V1.2.2 (2021-04)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Conventions . 9
4.1 Interoperability test process . 9
4.1.1 Principles . 9
4.1.2 The test description proforma . 9
4.1.3 Interoperable Functions Statement (IFS) . 9
4.2 Tooling . 10
4.3 Test Description naming convention . 10
4.4 Test Summary . 10
5 Test Bed Architecture . 12
5.1 Test site layout . 12
5.2 PSAP modes . 13
6 Test Configurations . 14
6.1 Basic Interoperability Test Configuration . 14
6.2 Optional Interoperability Test Configurations. 14
6.2.1 eCall_CFG_02 . 14
6.2.2 eCall_CFG_03 . 14
6.2.3 eCall_CFG_04 . 15
6.2.4 eCall_CFG_05 . 15
6.3 Default pre-test conditions . 15
6.4 Interoperable Functions Statement (IFS) . 16
6.5 Test Configuration parameters . 16
7 eCall test scenarios . 16
7.0 Introduction . 16
7.1 Basic test scenarios . 17
7.1.1 MSD transmission/reception/acknowledgement with PSAP in Pull mode . 17
7.1.2 MSD transmission/reception/acknowledgement with PSAP in Push mode. 18
7.1.3 Voice communication after receipt of AL-ACK . 18
7.1.4 Retransmission of MSD on request from PSAP . 19
7.1.5 Voice Communication after retransmission of MSD . 19
7.1.6 Clear-down/PSAP initiated network clear-down . 20
7.1.7 Clear-down/PSAP initiated application layer AL-ACK clear-down . 20
7.1.8 Call Back/PSAP initiated call back to IVS and re-send MSD . 21
7.1.9 PSAP correct handling of voice call in case of in-band modem resources busy or out of service . 21
7.1.10 MSD activation type indicator set to 'Automatic' . 22
7.1.11 MSD activation type indicator set to 'Manual' . 22
7.1.12 MSD call type indicator set to 'Test Call ' . 23
7.1.13 Mute IVS audio during MSD transmission and un-mute after application layer acknowledgement . 23
7.1.14 Mute PSAP audio during MSD request/MSD transfer and un-mute after application layer
acknowledgement . 24
7.1.15 Format of encoded and decoded MSD in accordance with EN 15722:2015 . 25
7.1.16 MSD transmission following NEC disabling tone with PSAP in Pull mode . 26
ETSI
4 ETSI TS 103 428 V1.2.2 (2021-04)
7.1.17 MSD transmission following NEC disabling tone with PSAP in Push mode . 26
7.1.18 Format of encoded and decoded MSD in accordance with EN 15722:2020 . 27
7.2 Advanced IVS test scenarios . 28
7.2.1 Auto redial following busy during call set-up . 28
7.2.2 Auto redial following no-answer during call set-up . 28
7.2.3 IVS configured for 'eCall only' service (restricted) . 29
7.2.4 eCall deactivated during TPS call . 29
7.2.5 Fall-back to 112-based eCall when TPS is not functional . 30
7.2.6 IVS privacy protection from PSAP call-back . 30
7.3 Advanced PSAP test scenarios . 31
7.3.1 Un-mute PSAP audio when Initiation Signal not received within 5 s (T4 expired) . 31
7.3.2 PSAP handling of more than 1 eCall simultaneously . 31
7.3.3 PSAP correct MSD additional data decoding . 32
7.4 Performance test scenarios . 32
7.4.0 Introduction. 32
7.4.1 PSAP handling a number of parallel random eCalls from different IVS . 33
7.4.2 KPI 1 Success rate of eCall . 33
7.4.3 KPI 2 Success rate of call backs using eCall . 34
7.4.4 KPI 3 Success rate of correct MSDs . 35
7.4.5 KPI 4 Success rate of correct re-transmitted MSDs . 36
7.4.6 KPI 5 Duration of voice channel blocking . 37
Annex A (normative): HLAP timers . 39
Annex B (informative): Bibliography . 40
History . 41

ETSI
5 ETSI TS 103 428 V1.2.2 (2021-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Mobile Standards Group (MSG).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI
6 ETSI TS 103 428 V1.2.2 (2021-04)
1 Scope
The present document defines Interoperability Test Descriptions for the eCall High Level Application Protocol (HLAP).
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 122 101: "Universal Mobile Telecommunications System (UMTS); LTE; Service
aspects; Service principles (3GPP TS 22.101)".
[2] ETSI TS 124 008: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; 5G; Mobile radio interface Layer 3
specification; Core network protocols; Stage 3 (3GPP TS 24.008)".
[3] EN 15722:2015: "Intelligent transport systems - eSafety - eCall minimum set of data", (produced
by CEN).
[4] EN 16062:2015: "Intelligent transport systems - eSafety - eCall high level application
requirements (HLAP) using GSM/UMTS circuit switched networks", (produced by CEN).
[5] EN 16072:2015: "Intelligent transport systems - eSafety - Pan-European eCall operating
requirements", (produced by CEN).
[6] ETSI TS 134 123-1: "Universal Mobile Telecommunications System (UMTS); User Equipment
(UE) conformance specification; Part 1: Protocol conformance specification (3GPP TS 34.123-1)".
[7] 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)".
[8] ETSI TS 122 003: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; Circuit Teleservices supported by a Public
Land Mobile Network (PLMN) (3GPP TS 22.003)".
[9] ETSI TS 102 936-1: "eCall Network Access Device (NAD) conformance specification; Part 1:
Protocol test specification".
[10] Commission Delegated Regulation (EU) 2017/79 of 12 September 2016 establishing detailed
technical requirements and test procedures for the EC type-approval of motor vehicles with respect
to their 112-based eCall in-vehicles systems, of 112-based eCall in-vehicle separate technical units
and components and supplementing and amending Regulation (EU) 2015/758 of the European
Parliament and of the Council with regard to the exemptions and applicable standards.
[11] TS 17234:2018: "Intelligent transport systems - eSafety - eCall: Tests to enable PSAPs to
demonstrate conformance and performance", (produced by CEN).
[12] EN 15722:2020: "Intelligent transport systems - eSafety - eCall minimum set of data", (produced
by CEN).
ETSI
7 ETSI TS 103 428 V1.2.2 (2021-04)
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI ETR 266: "Methods for Testing and Specification (MTS); Test Purpose style guide".
[i.2] EN 16062:2011: "Intelligent Transport Systems - eSafety - eCall - high level application
requirements (HLAP)", (produced by CEN).
[i.3] ETSI EG 202 798 (V1.1.1): "Intelligent Transport Systems (ITS); Testing; Framework for
conformance and interoperability testing".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
base specification: specification of a protocol, telecommunication service, interface, abstract syntax, encoding rules, or
information object
eCall: manually or automatically initiated emergency call, (TS12) from a vehicle, supplemented with a minimum set of
emergency related data (MSD)
NOTE: As defined under the EU Commission's eSafety initiative.
implementation: instance of the reference specification for which conformity to that reference specification is claimed
IVS configured for eCall only service (restricted): eCall capable IVS that is not subscribed to other non-emergency
services
NOTE: The IVS is not permitted to register on a PLMN except for the purpose of making an eCall, or a
test/reconfiguration call to a designated non-emergency number, in accordance with ETSI
TS 122 101 [1]. Following power-up the IVS may perform a PLMN search and maintain a list of
available networks upon which to register, when an eCall or test/reconfiguration call is activated.
Following an eCall or test/reconfiguration call, the IVS de-registers from the serving network within
12 hours.
IVS configured for eCall and other services (unrestricted): eCall capable IVS that has valid subscriptions to access
other non-emergency services
NOTE: The IVS may register on a PLMN at anytime and may remain registered on a serving network
indefinitely.
Minimum Set of Data (MSD): data component of an eCall sent from a vehicle to a Public Safety Answering Point or
other designated emergency call centre
NOTE: The MSD has a maximum size of 140 bytes and includes, for example, vehicle identity, location
information and time-stamp.
PSAP eCall Modem-server: PSAP equipment used to receive, validate and acknowledge the MSD sent from an IVS,
to manage the voice call transfer to the PSAP operator and to facilitate call-back to the vehicle
NOTE: The eCall modem-server may also support other functions.
ETSI
8 ETSI TS 103 428 V1.2.2 (2021-04)
PSAP Pull mode: mode in which the PSAP is configured to immediately transmit the SEND-MSD (START) message
without waiting for the INITIATION message send by the IVS
PSAP Push mode: mode in which the PSAP is configured to wait for the INITIATION message send by the IVS
NOTE: After reception of the INITIATION message the PSAP transmits the SEND-MSD (START) message.
reference specification: standard which provides a base specification, or a set of base specifications, or a profile, or a
set of profiles, and for conformance to which the ICS proforma and test specifications are written
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
3GPP Third Generation Partnership Project
AL-ACK Application Layer - Acknowledgement (also called HL-ACK)
ANSI-C American National Standard Programming Language C
CEN Comité Européen de Normalisation
CFG Configuration
CLI Calling Line Identity
CRC Cyclic Redundancy Check
CS Circuit Switch
EMC ElectroMagnetic Compatibility
ETSI European Telecommunications Standards Institute
EU European Union
EUT Equipment Under Test
GSM Global System of Mobile telecommunications
HLAP High Level Application Protocol
HMI Human Machine Interface
IE Information Element
IFS Interoperable Functions Statement
IFS_ID IFS Identifier
ISDN Integrated Services Digital Network
ITS Intelligent Transport Systems
IVS In Vehicle System
NOTE: eCall terminal and associated sub-systems in vehicle.
KPI Key Performance Indicators
LL-ACK Link Layer - ACK
LV Low Volltage
MNO Mobile Network Operator
MSD Minimum Set of Data
NACK Negative Acknowledgement
NAD Network Access Device
NEC Network Echo Canceller
PLMN Public Land Mobile Network
PSAP Public Service Answering Point
R&TTE Radio and Telecommunications Terminal Equipment
SIP Session Initiation Protocol
TD Test Description
TPS Third Party Service
TPSP Third Party Service Provider
TS11 Teleservice No 11 (Telephony)
TS12 Teleservice No 12 (Emergency Calls)
UL Uplink
UMTS Universal Mobile Telecommunications System
ETSI
9 ETSI TS 103 428 V1.2.2 (2021-04)
4 Conventions
4.1 Interoperability test process
4.1.1 Principles
The goal of interoperability tests is to check that devices resulting from protocol implementations are able to work
together and provide the functionalities provided by the protocols. As necessary, one message may be checked during a
test, when a successful functional verification may result from an incorrect behaviour for instance. Detailed protocol
checks are part of the conformance testing process and are thus avoided during the Interoperability tests.
The test sessions will be mainly executed between 2 devices (IVS and PSAP eCall modem-server) from different
vendors.
In the present document, test description is provided to guide the test process during the test sessions.
4.1.2 The test description proforma
The test descriptions are provided in proforma tables following the format described in ETSI EG 202 798 [i.3] and
ETSI ETR 266 [i.1]. The following different test events are considered during the test execution:
• A stimulus corresponds to an event that enforces an EUT to proceed with a specific protocol action, like
sending a message for instance.
• A verify consists of verifying that the EUT behaves according to the expected behaviour (for instance the EUT
behaviour shows that it receives the expected message).
• A configure corresponds to an action to modify the EUT configuration.
• A check ensures the receipt of protocol messages on reference points, with valid content. This "check" event
type corresponds to the interoperability testing with conformance check method.
For the execution of the interoperability test sessions, the following conventions apply:
• Optional (check) tests should be performed using High Level Application Protocol (HLAP) monitor tools (see
clause 4.2 'Tooling') and may be skipped due to time restrictions.
4.1.3 Interoperable Functions Statement (IFS)
The Interoperable Functions Statement (IFS) identifies the standardized functions of an EUT. These functions can be
mandatory, optional or conditional (depending on other functions), and depend on the role played by the EUT.
The IFS can also be used as a pro-forma by a vendor to identify the functions that its EUT will support when
interoperating with corresponding functions from other vendors.
Item column
The item column contains a number which identifies the item.
Item description column
The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly
means "is supported by the implementation?".
IFS ID column
The IFS ID column defines an identifier for this particular IFS item. The IFS ID is in the Test Description field
"Applicability" to select/deselect the execution of a test.
ETSI
10 ETSI TS 103 428 V1.2.2 (2021-04)
Status column
The following notations are used for the status column:
m mandatory - the capability is required to be supported.
o optional - the capability may be supported or not.
n/a not applicable - in the given context, it is impossible to use the capability.
x prohibited (excluded) - there is a requirement not to use this capability in the given context.
o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which identifies an
unique group of related optional items and the logic of their selection which is defined immediately following
the table.
c.i conditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on the support of other optional
or conditional items. "i" is an integer identifying an unique conditional status expression which is defined
immediately following the table.
i irrelevant (out-of-scope) - capability outside the scope of the reference specification. No answer is requested
from the supplier.
NOTE: This use of "i" status is not to be confused with the suffix "i" to the "o" and "c" statuses above.
Support column
The support column shall be filled in by the supplier of the implementation using the following notations:
Y or y supported by the implementation.
N or n not supported by the implementation.
N/A or n/a no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional
status).
4.2 Tooling
Message monitoring solutions, including audio recording and event logging, where supported, may be used to facilitate
the resolution of any interoperability and/or performance issues that may be encountered during interoperability testing.
4.3 Test Description naming convention
Table 1: TD naming convention
TD/// Identifier Description
= root applicability BAS Basic tests
ADV Advanced tests
PER Performance tests
= group IVS eCall terminal
PSAP PSAP eCall modem-server
IVS or PSAP
= sequential number 01 to 99 Sequential numbers

4.4 Test Summary
Test scenario with a detailed test description, are provided in the present document to provide guidance to the
participants and to ensure consistent testing among the different test sessions and participants. The detailed test
descriptions are in the clause 7. It is recommended to conduct all test cases for all technologies supported by the IVS,
e.g. a dual mode GSM and UMTS IVS should conduct all tests with both technologies.
ETSI
11 ETSI TS 103 428 V1.2.2 (2021-04)
The test scenarios are split in 3 groups:
• The basic scenarios, which shall be executed during all test sessions, covering the basic features of an eCall
devices (IVS or PSAP).
• The advanced test scenarios, which are provided to do additional testing according to the time left during the
test sessions. These scenarios are focusing either on IVS or PSAP features.
• The performance test scenarios, similar to a real eCall service, dedicated to check some performance issues
from PSAP side. These scenarios are focusing on some performance checks relating to repetitive or parallel
calls from different IVS or IVS simulator to the same PSAP.
The basic test scenarios in Table 2 are foreseen to be executed during all interoperability test sessions, either with real
IVS and PSAP, but also with testing devices simulating an IVS or a PSAP.
Table 2: Basic Tests
Test case ID Summary
TD_BAS_01 MSD transmission/reception/acknowledgement with PSAP in Pull mode
TD_BAS_02 MSD transmission/reception/acknowledgement with PSAP in Push mode
TD_BAS_03 Voice communication after receipt of AL-ACK
TD_BAS_04 Retransmission of MSD on request from PSAP
TD_BAS_05 Voice communication after retransmission of MSD
TD_BAS_06 Clear-down/PSAP initiated network clear-down
TD_BAS_07 Clear-down/PSAP initiated application layer AL-ACK clear-down
TD_BAS_08 Call Back/PSAP initiated call back to IVS and re-send MSD
TD_BAS_09 PSAP correct handling of voice call in case of in-band modem resources busy or out of service
TD_BAS_10 MSD activation type indicator set to 'Automatic'
TD_BAS_11 MSD activation type indicator set to 'Manual'
TD_BAS_12 MSD call type indicator set to 'Test Call'
TD_BAS_13 Mute IVS audio during MSD transmission and un-mute after application layer acknowledgement
TD_BAS_14 Mute PSAP audio during MSD request/MSD transfer and un-mute after application layer
acknowledgement
TD_BAS_15 Format of encoded and decoded MSD in accordance with EN 15722 [3]
TD_BAS_16 MSD transmission following NEC disabling tone with PSAP in Pull mode
TD_BAS_17 MSD transmission following NEC disabling tone with PSAP in Push mode
TD_BAS_18 Format of encoded and decoded MSD in accordance with EN 15722 [12]

The advanced and performance test scenarios in Tables 3, 4 and 5 are foreseen to do additional testing which goes
beyond the basic test scenarios.
Table 3: Advanced IVS Tests
Test case ID Summary
TD_ADV_IVS_01 Auto redial following busy during call set-up
TD_ADV_IVS_02 Auto redial following no-answer during call set-up
TD_ADV_IVS_03 IVS configured for 'eCall only' service (restricted)
TD_ADV_IVS_04 eCall deactivated during TPS call
TD_ADV_IVS_05 Fall-back to 112-based eCall when TPS is not functional
TD_ADV_IVS_06 IVS privacy protection from PSAP call-back

Table 4: Advanced PSAP Tests
Test case ID Summary
TD_ADV_PSAP_01 Un-mute PSAP audio when Initiation Signal not received within 5 s (T4 expired)
TD_ADV_PSAP_02 PSAP handling of more than 1 eCall simultaneously
TD_ADV_PSAP_03 PSAP correct MSD additional data decoding

ETSI
12 ETSI TS 103 428 V1.2.2 (2021-04)
Table 5: Performance Tests
Test case ID Summary
TD_PER_PSAP_01 PSAP handling a number of parallel random eCalls from different IVS
TD_PER_PSAP_02 KPI 1 Success rate of eCall
TD_PER_PSAP_03 KPI 2 Success rate of call backs using eCall
TD_PER_PSAP_04 KPI 3 Success rate of correct MSDs
TD_PER_PSAP_05 KPI 4 Success rate of correct re-transmitted MSDs
TD_PER_PSAP_06 KPI 5 Duration of voice channel blocking

5 Test Bed Architecture
5.1 Test site layout
The generic test bed used to carry out interoperability tests, is summarized in figure 1. In normal operation conditions,
the IVS calls the 112 called party number and shall set the Emergency Category IE of the Emergency Setup message as
defined in table 10.5.135d of ETSI TS 124 008 [2]. This call setting is then interpreted by the mobile network as a
requirement to connect the IVS with the most appropriate PSAP, able to handle pan EU eCalls, accordingly to
EN 16062 [4].
However, during an eCall interoperability event, IVS will need to be connected to a given PSAP in order to carry out
pairing test sessions, following the test scenario provided in the present document. The selection of the PSAP is
therefore achieved by the use of the called party number, corresponding to the access where the PSAP is connected
(ISDN or SIP trunk).
For the purpose of carrying out tests in more real conditions different options are available:
• Using test tool providing PLMN and PSAP simulation (connection in shield cases or with cable).
• Calling 112 in real conditions, if the local authorities allow using the 112 connection and thus reaching the real
PSAP.
• The IVS device has the ability to call TPSP or 112 eCall service over PLMN.
NOTE: Tests defined in the present document are applicable for aftermarket eCall devices as well as 112-based
eCall in-vehicle systems (OEM pre-installed).
ETSI
13 ETSI TS 103 428 V1.2.2 (2021-04)

Figure 1: Test site layout
5.2 PSAP modes
Figure 6 given by EN 16062 [4] shows the overall HLAP flow diagram. It depicts the PSAP PULL and PSAP PUSH
implementation variants in one diagram and requires some additional explanation for a better understanding.
In the PSAP PULL mode:
In PSAP PULL mode, the PSAP starts sending SEND-MSD (START) messages immediately after the eCall got
connected, while it can optionally prepend a network echo canceller (NEC) disabler tone (typically 3,6 s). As the IVS
cannot know in advance whether the PSAP is in PUSH or PULL mode, it always needs to send the PUSH-Req at the
start of the eCall but should stop sending it as soon as it detects the SEND-MSD from the PSAP and then starts with the
MSD transmission. Upon detection of UL sync, the PSAP should stop sending SEND-MSD and respond with NACK
messages until it can decode the MSD, i.e. the flow arrow from PSAP after the first UL sync would be NACKs and not
SEND-MSD in this case.
In the PSAP PUSH mode:
In PSAP PUSH mode, PSAP has to wait for UL sync of the PUSH-Req message (initiation signal) before it can start
with SEND-MSD messages, i.e. the first 3 flow arrows from PSAP are not used in this case. As in the PULL mode,
PSAP can optionally prepend a Network Echo Canceller (NEC) disabler tone before the SEND-MSD messages but
should not do this before the initiation signal is detected.
Once the MSD transmission has started, the HLAP flow is the very same for PSAP in PULL and PUSH modes.
The application layer acknowledgement sequence is shown in figure 7 from EN 16062 [4].
ETSI
14 ETSI TS 103 428 V1.2.2 (2021-04)
6 Test Configurations
6.1 Basic Interoperability Test Configuration
Interoperability tests will be performed using the set-up shown in figure 2. Ancillary measurement and message logging
equipment is not shown but may be used, with the agreement of the participants, to help identify the likely cause of any
interoperability test failures that may arise.
IVS, PLMN and PSAP can be either real devices or simulators. PSAP simulators are understood to be only simulating
the PSAP connected to the public network with ISDN.
Figure 2 shows the basic interoperability test configuration. IVS and PSAP can be either real equipment or simulators.
HMI
PLMN
PSAP eCall
IVS
modem-
server Audio
interface
Figure 2: eCall_CFG_01 - IVS and PSAP over PLMN
6.2 Optional Interoperability Test Configurations
6.2.1 eCall_CFG_02
With the interoperability test configuration eCall_CFG_02, a TELEPHONE (only) is used to simulated a PSAP that is
either not equipped with a PSAP eCall modem-server or a PSAP eCall modem server that fails to respond to the
incoming Initiation Tone from the IVS for any reason.
IVS PLMN Telephone
Figure 3: eCall_CFG_02 - Optional interoperability/diagnostic testing configuration
6.2.2 eCall_CFG_03
In the Interoperability test configuration eCall_CFG_03, a mobile phone is used instead of an IVS to simulate an
emergency call from an IVS, that fails to transmit an eCall Initiation Signal or transmits an invalid Initiation Tone, or
from a miss-routed mobile phone originated the emergency call. In all such cases, the PSAP modem-server shall not
respond with a request to 'SEND MSD' (START message) but is required, after the specified time, to transfer the
emergency call to a PSAP operator, so that 2-way speech can be established.
HMI
Mobile Public PSAP eCall
telephone GSM/UMTS modem-
Network server
Audio
Interface
Figure 4: eCall_CFG_03 - Optional interoperability/diagnostic testing configuration
ETSI
15 ETSI TS 103 428 V1.2.2 (2021-04)
6.2.3 eCall_CFG_04
In the Interoperability test configuration eCall_CFG_04, more than one IVS will repetitively call the same PSAP to
simulate a real service. The PSAP shall be able to handle a certain number of parallel emergency calls and route them to
a certain number of operator phones.
IVS 1 HMI
Public PSAP eCall
IVS 2
GSM/UMTS modem-
Network server
Audio
Interface
IVS n
Figure 5: eCall_CFG_04 - Optional interoperability/diagnostic testing configuration
6.2.4 eCall_CFG_05
In the Interoperability test configuration eCall_CFG_05, the IVS device has the ability to call TPSP or 112 eCall
service. If IVS is calling first the TPS then TPSP have the ability to forward the MSD data and call 112 eCall operator.
HMI
Public
PSAP eCall
IVS
GSM/UMTS
modem-
(TPS + 112eCall)
Network
server Audio
interface
TPSP
TPS eCall
Figure 6: eCall_CFG_05 - Optional interoperability/diagnostic testing configuration
6.3 Default pre-test conditions
The following default pre-test conditions apply to all tests unless otherwise stated in the test cases description:
• Ignition is ON and IVS is in mobile network coverage.
• MNO and PSAP test points are available.
• IVS has all the information needed to compile the MSD.
ETSI
16 ETSI TS 103 428 V1.2.2 (2021-04)
6.4 Interoperable Functions Statement (IFS)
Table 6: PSAP features
Item Entity IFS_ID Status Support
1 PSAP supports sending directly SEND-MSD message PSAP_PULL o.501
without waiting for INITIATION message (see note)
2 PSAP supports waiting for INITIATION Message prior to PSAP_PUSH o.501
sending the SEND-MSD message (see note)
3 PSAP supports 2-way speech PSAP_speech m
4 PSAP supports 2-way speech mute/unmute PSAP_speech_mute m
5 PSAP supports NEC PSAP_NEC o
6 PSAP supports MSD message version 2 PSAP_MSDv2 m
7 PSAP supports MSD message version 3 PSAP_MSDv3 o
8 PSAP supports simultaneous eCalls PSAP_simult_eCalls o
NOTE: o.501: It is mandatory to support at least one feature.

Table 7: IVS features
Item Entity IFS_ID Status Support
1 IVS supports 2-way speech IVS_speech m
2 IVS supports MSD retransmission IVS_MSD_retransmission m
3 IVS supports network clear-down IVS_NW_clear-down m
4 IVS supports AL-ACK clear-down IVS_AL-ACK_clear-down m
5 IVS supports automatic eCall activation IVS_auto_eCall m
6 IVS supports manual eCall activation IVS_man_eCall m
7 IVS supports test call IVS_test_call o
8 IVS supports 2-way speech mute/unmute IVS_speech_mute o
9 IVS supports NEC IVS_NEC o
10 IVS supports MSD message version 2 IVS_MSDv2 m
11 IVS supports MSD message version 3 IVS_MSDv3 o
12 IVS supports additional MSD data IVS_add_MSD_data o
13 IVS supports auto_redial IVS_auto_redial m
14 IVS supports eCall only IVS_eCall_only o
15 IVS supports 112 eCall and TPS eCall IVS_eCall_and_TPS o

6.5 Test Configuration parameters
Table 8: Parameters
Item Entity Description Value
1 PSAP long number Called party number to be used to reach the
selected PSAP
7 eCall test scenarios
7.0 Introduction
The tests defined in the present document shall be performed according to the test applicability. The test applicability is
defined in each test in the field 'Applicability' and is expressed with IFS statements. The tests apply to IVS and PSAP as
well as to IVS or PSAP simulators.
In EN 16062 HLAP standard [i.2] the PUSH mode was mandatory and furthermore, the pull mode was not allowed.
ETSI
17 ETSI TS 103 428 V1.2.2 (2021-04)
However, following several trials, it showed that the PULL mode could significantly reduce the delay for sending the
MSD and thus establishing the voice connection. Therefore in EN 16062 [4], the PULL mode is mandatory, and the
PUSH is applied only when the PSAP cannot identify that the incoming call is an eCall. For more details, refer to
clause 5.2.
It is recommended to conduct all test cases for all technologies supported by the IVS, e.g. a dual mode GSM and UMTS
IVS should conduct all tests with both technologies.
7.1 Basic test scenarios
7.1.1 MSD transmission/reception/acknowledgement with PSAP in Pull
mode
Interoperability Test Description
Identifier: TD_BAS_01
Objective: To verify the eCall initiation with the PSAP sending a SEND-MSG message without
waiting for the INITIATION message.
Configura
...