ETSI TS 103 683 V1.1.1 (2020-02)

Mobile Standards Group (MSG); Testing; Next Generation eCall High Level Application Protocol (HLAP) Interoperability Testing

DTS/MSG-001128

General Information

• Status: Published
• Publication Date: 26-Feb-2020
• Technical Committee: MSG - Mobile Standards Group
• Current Stage: 12 - Completion
• Due Date: 02-Mar-2020
• Completion Date: 27-Feb-2020

Standards Content (Sample)

TECHNICAL SPECIFICATION
Mobile Standards Group (MSG);
Testing;
Next Generation eCall High Level Application Protocol (HLAP)
Interoperability Testing

2 ETSI TS 103 683 V1.1.1 (2020-02)

Reference
DTS/MSG-001128
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 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

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
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 2020.
All rights reserved.
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.
ETSI
3 ETSI TS 103 683 V1.1.1 (2020-02)
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 . 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 NG eCall HLAP flow diagram . 14
6 Test Configurations . 16
6.0 Introduction . 16
6.1 Home Interoperability Test Configuration . 16
6.2 Home Interoperability Test Configuration with fallback to legacy eCall . 17
6.3 Visited Interoperability Test Configuration . 17
6.4 Multiple IVS Interoperability Test Configuration . 18
6.5 Home Interoperability Test Configuration rerouting to another PSAP . 18
6.6 Home Interoperability Test Configuration without VoIMS support . 18
6.7 Default pre-test conditions . 19
6.8 Interoperable Functions Statement (IFS) . 19
7 NG eCall test scenarios/descriptions . 20
7.0 Introduction . 20
7.1 Basic test scenarios . 21
7.1.1 Initiation of manual eCall . 21
7.1.2 Initiation of automatic eCall . 21
7.1.3 Initiation of test eCall . 22
7.1.4 MSD transfer to PSAP supporting IMS eCall. 22
7.1.5 MSD transfer to PSAP supporting IMS eCall in roaming scenario . 23
7.1.6 PSAP initiated callback to IVS and MSD update . 24
7.1.7 PSAP initiated call clear-down . 26
7.1.8 IVS initiated call clear-down not allo wed . 27
7.1.9 Verification of audio interfaces of IVS and PSAP . 27
7.1.10 MSD update on request from PSAP . 28
7.1.11 IVS behaviour after unsuccessful MSD update . 28
7.1.12 IVS behaviour after unacknowledged MSD update . 29
7.1.13 Format of encoded and decoded MSD in accordance with CEN EN 15722:2015. 30
7.1.14 MSD transfer via in-band modem to PSAP supporting IMS eCall . 31
7.2 Advanced test scenarios . 32
7.2.1 MSD transfer to PSAP supporting IMS eCall over IPv4 . 32
7.2.2 MSD transfer to PSAP supporting IMS eCall over IPv6 . 32
ETSI
4 ETSI TS 103 683 V1.1.1 (2020-02)
7.2.3 MSD transfer to PSAP supporting IMS eCall over IPv4(IVS)/IPv6(PSAP) . 33
7.2.4 MSD transfer to PSAP not supporting IMS eCall . 34
7.2.5 IMS eCall establishment with IMS emergency registration . 36
7.2.6 IMS eCall establishment without IMS emergency registration . 38
7.2.7 IMS eCall establishment without IMS emergency registration GIBA supported . 38
7.3 Advanced IVS test scenarios . 39
7.3.1 Fallback to legacy eCall following busy during call setup . 39
7.3.2 Fallback to legacy eCall following unavailable response during call setup . 41
7.3.3 Fallback to legacy eCall following no-answer during call setup . 42
7.3.4 Dropped eCall after MSD has been acknowledged . 44
7.3.5 Dropped eCall before call has been established . 45
7.3.6 IVS configured for 'eCall only' service (restricted) . 46
7.3.7 eCall is attempted when no networks are available (limited service condition with forbidden PLMN
on SIM/USIM) . 46
7.3.8 MSD transfer to PSAP supporting IMS eCall via PLMN without VoIMS support . 47
7.3.9 Termination of manually triggered eCall by vehicle occupant . 47
7.3.10 Termination of automatically triggered eCall by vehicle occupant not allowed/not possible . 48
7.3.11 Ongoing eCall shall not be disconnected if new trigger is received . 48
7.4 Advanced PSAP test scenarios . 49
7.4.1 PSAP handling of more than 1 eCall simultaneously . 49
7.4.2 PSAP correct MSD additional data decoding . 49
7.4.3 Rerouting to another PSAP/emergency control centre . 50
7.4.4 PSAP operator user interface . 50
Annex A (informative): Source code of MSC figures . 51
A.1 Overview . 51
History . 52

ETSI
5 ETSI TS 103 683 V1.1.1 (2020-02)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is 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 IPR Policy, no investigation, 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.
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 683 V1.1.1 (2020-02)
1 Scope
The present document defines Interoperability Test Descriptions for the NG 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 124 229 (V14.10.0): "Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol
based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP
TS 24.229 version 14.10.0 Release 14)".
[2] ETSI TS 123 167 (V14.6.0): "Universal Mobile Telecommunications System (UMTS); LTE; IP
Multimedia Subsystem (IMS) emergency sessions (3GPP TS 23.167 version 14.6.0 Release 14)".
[3] ETSI TS 123 228 (V14.6.0): "Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS);
Stage 2 (3GPP TS 23.228 version 14.6.0 Release 14)".
[4] CEN TS 17184:2018: "Intelligent transport systems - eSafety - eCall High level application
Protocols (HLAP) using IMS packet switched networks".
[5] EENA Technical Committee Document: "Next Generation eCall".
[6] ETSI TS 123 401 (V14.10.0): "LTE; General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (3GPP TS 23.401
version 14.10.0 Release 14)".
[7] CEN EN 16072:2015: "Intelligent transport systems - eSafety - Pan European eCall - Operating
requirements".
[8] IETF RFC 8147: "Next-Generation Pan-European eCall".
[9] ETSI TS 103 428 (V1.1.1): "Mobile Standards Group (MSG); eCall HLAP Interoperability
Testing".
[10] CEN EN 15722:2015: "Intelligent transport systems - ESafety - Ecall minimum set of data".
[11] ETSI TS 122 101 (V14.7.0): "Universal Mobile Telecommunications System (UMTS); LTE;
Service aspects; Service principles (3GPP TS 22.101 version 14.7.0 Release 14)".
ETSI
7 ETSI TS 103 683 V1.1.1 (2020-02)
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] CEN EN 16062:2011: "Intelligent Transport Systems - eSafety - eCall - High Level Application
Requirements (HLAP)".
[i.3] ETSI EG 202 798 (V1.1.1): "Intelligent Transport Systems (ITS); Testing; Framework for
conformance and interoperability testing".
[i.4] PlantUML.
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), as defined under the EU Commission's eSafety initiative
eCall Over IMS support (ECL): As indicated by the eCall support indicator defined in ETSI TS 123 401 [6].
implementation: instance of the reference specification for which conformity to that reference specification is claimed
IMS eCall: eCall deployed using IMS emergency call in 3GPP Release-14, instead of in-band modem and circuit
switched 112
NOTE: This definition is taken from EENA Technical Committee Document [5].
IMS Emergency Service support (EMS): IMS Emergency Services supported as indicated by Emergency Service
Support indicator as defined in ETSI TS 123 401 [6].
In-band modem eCall: eCall deployed using in-band modem and circuit switched 112 according to CEN
EN 16062:2011 [i.2] and CEN EN 16072:2015 [7]
NOTE: This definition is based on definition in EENA Technical Committee Document [5].
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 [11]. 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.
ETSI
8 ETSI TS 103 683 V1.1.1 (2020-02)
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 any time 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, as defined in CEN EN 15722:2015 [10].
Next Generation eCall (NG eCall): based on IMS eCall and offering data, multimedia and two-way data
NOTE: This definition is based on definition in EENA Technical Committee Document [5].
Plugfest: interoperability testing event about a standard or a profile where the participants test each other their
implementation
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 callback to the vehicle
NOTE: The eCall modem-server may also support other functions.
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
VoIMS: voice over IMS over PS sessions support as indicated by IMS Voice over PS session supported indication as
defined in ETSI TS 123 401 [6]
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
3GPP Third Generation Partnership Project
ACK ACKnowledgement
CEN Comité Européen de Normalisation
CFG ConFiGuration
CS Circuit Switched
CSCF Call Session Control Function
E-CSCF Emergency CSCF
E-UTRAN Enhanced UMTS Terrestrial Radio Access Network
ECL eCall Over IMS support
EMS IMS Emergency Services
ETR ETSI Technical Report
ETSI European Telecommunications Standards Institute
EU European Union
EUT Equipment Under Test
GIBA GPRS-IMS-Bundled-Authentication
GSM Global System of Mobile telecommunications
HLAP High Level Application Protocol
HMI Human Machine Interface
HPLMN Home PLMN
HSS Home Subscriber Server
I-CSCF Interrogating CSCF
IFS Interoperable Functions Statement
IFS_ID IFS Identifier
IMEI International Mobile Equipment Identity
ETSI
9 ETSI TS 103 683 V1.1.1 (2020-02)
IMS IP Multimedia Subsystem
IVS In Vehicle System
LTE Long Term Evolution
MNO Mobile Network Operator
MSD Minimum Set of Data
NACK Negative Acknowledgement
NG Next Generation
P-CSCF Proxy CSCF
PLMN Public Land Mobile Network
PS Packet Switched
PSAP Public Service Answering Point
S-CSCF Serving CSCF
SIP Session Initiation Protocol
TD Test Description
TS11 Teleservice No 11 (Telephony)
TS12 Teleservice No 12 (Emergency Calls)
UMTS Universal Mobile Telecommunications System
URN Unique Resource Name
VoIMS Voice over IMS
VoLTE Voice over LTE
VPLMN Visited PLMN
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.
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 event types 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.
4.1.3 Interoperable Functions Statement
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.
ETSI
10 ETSI TS 103 683 V1.1.1 (2020-02)
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.
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.
ETSI
11 ETSI TS 103 683 V1.1.1 (2020-02)
4.3 Test Description naming convention
Table 1: TD naming convention
TD__[gr]_
= root applicability BAS Basic test
ADV Advanced test
[gr] = group IVS IVS eCall terminal
PSAP PSAP eCall server
IVS or PSAP
= sequential number 01 to 99 Sequential numbers

4.4 Test Summary
The detailed test descriptions are defined in the clause 7. It is recommended to conduct all test cases supported by PSAP
and IVS. Some of test cases require a fallback to CS (legacy) eCall. The interoperability test cases for CS domain are
specified in ETSI TS 103 428 [9].
The test scenarios of the present document are split in 4 groups:
1) The basic scenarios, which shall be executed during all interoperability test sessions, covering the mandatory
features of a NG eCall device (IVS and PSAP).
2) The advanced test scenarios, to do additional testing which goes beyond the basic test scenarios. These
scenarios are focusing on IVS and PSAP features.
3) The advanced IVS test scenarios, to do additional testing which goes beyond the basic test scenarios. These
scenarios are focusing only on IVS features.
4) The advanced PSAP test scenarios, to do additional testing which goes beyond the basic test scenarios. These
scenarios are focusing only on PSAP features.
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 Title
TD_BAS_01 Initiation of manual eCall
TD_BAS_02 Initiation of automatic eCall
TD_BAS_03 Initiation of test eCall
TD_BAS_04 MSD transfer to PSAP supporting IMS eCall
TD_BAS_05 MSD transfer to PSAP supporting IMS eCall in roaming scenario
TD_BAS_06 PSAP initiated callback to IVS and MSD update
TD_BAS_07 PSAP initiated call clear-down
TD_BAS_08 IVS initiated call clear-down not allowed
TD_BAS_09 Verification of audio interfaces of IVS and PSAP
TD_BAS_10 MSD update on request from PSAP
TD_BAS_11 IVS behaviour after unsuccessful MSD update
TD_BAS_12 IVS behaviour after unacknowledged MSD update
TD_BAS_13 Format of encoded and decoded MSD in accordance with CEN EN 15722:2015 [10]
TD_BAS_14 MSD transfer via in-band modem to PSAP supporting IMS eCall

The advanced test scenarios in Tables 3, 4 and 5 are foreseen to do additional testing which goes beyond the basic test
scenarios.
ETSI
12 ETSI TS 103 683 V1.1.1 (2020-02)
Table 3: Advanced Tests for PSAP and IVS
Test case ID Title
TD_ADV_01 MSD transfer to PSAP supporting IMS eCall over IPv4
TD_ADV_02 MSD transfer to PSAP supporting IMS eCall over IPv6
TD_ADV_03 MSD transfer to PSAP supporting IMS eCall over IPv4(IVS)/IPv6(PSAP)
TD_ADV_04 MSD transfer to PSAP not supporting IMS eCall
TD_ADV_05 IMS eCall establishment with IMS emergency registration
TD_ADV_06 IMS eCall establishment without IMS emergency registration
TD_ADV_07 IMS eCall establishment without IMS emergency registration GIBA supported

Table 4: Advanced Tests for IVS
Test case ID Title
TD_ADV_IVS_01 Fallback to legacy eCall following busy during call setup
TD_ADV_IVS_02 Fallback to legacy eCall following unavailable response during call setup
TD_ADV_IVS_03 Fallback to legacy eCall following no-answer during call setup
TD_ADV_IVS_04 Dropped eCall after MSD has been acknowledged
TD_ADV_IVS_05 Dropped eCall before call has been established
TD_ADV_IVS_06 IVS configured for 'eCall only' service (restricted)
TD_ADV_IVS_07 eCall is attempted when no networks are available (limited service condition with
forbidden PLMN on SIM/USIM)
TD_ADV_IVS_08 MSD transfer to PSAP supporting IMS eCall via PLMN without VoIMS support
TD_ADV_IVS_09 Termination of manually triggered eCall by vehicle occupant
TD_ADV_IVS_10 Termination of automatically triggered eCall by vehicle occupant not allowed/not
possible
TD_ADV_IVS_11 Ongoing eCall shall not be disconnected if new trigger is received

Table 5: Advanced Tests for PSAP
Test case ID Title
TD_ADV_PSAP_01 PSAP handling of more than 1 eCall simultaneously
TD_ADV_PSAP_02 PSAP correct MSD additional data decoding
TD_ADV_PSAP_03 Rerouting to another PSAP/emergency control centre
TD_ADV_PSAP_04 PSAP operator user interface

5 Test Bed Architecture
5.1 Test site layout
The generic test bed used to carry out interoperability tests, is summarized in the below Figure 1.
ETSI
13 ETSI TS 103 683 V1.1.1 (2020-02)
National
PLMN
NG PSAP
(VoIMS, EMS, ECL
supported)
NG IVS
...
Local
Local
...
NG PSAP
NG PSAP
NG PSAP +
Remote NG PSAP
PLMN
simulator
...
NG IVS
Remote NG PSAP
The NG PSAPs are reached by predefined URNs and
shall be assigned by the PLMN
CS Fallback
Legacy eCall
refer to ETSI TS 103 428 [9]
Figure 1: Architecture
In normal operation conditions, the NG IVS establishes an NG eCall via correct URN. This call setting is then
interpreted by the mobile network (PLMN) as a requirement to connect the NG IVS with the most appropriate NG
PSAP, able to handle NG eCalls, accordingly to CEN TS 17184:2018 [4].
However, during an NG eCall interoperability event, an NG IVS needs to be connected to a given NG PSAP in order to
carry out pairing test sessions, following the test scenarios provided in the present document. The selection of the NG
PSAP is therefore achieved by the use of the pre-defined URNs (see Table 6), if supported (configured) by the PLMN
operator.
For the purpose of carrying out tests under real conditions, different options are available:
• Using test systems providing PLMN and NG PSAP simulation (connection in shielded cases or via cable).
• Using different non-standardized URNs, if the local authorities do not allow using the standardized URNs
connections and thus reaching the real PSAP.
ETSI
14 ETSI TS 103 683 V1.1.1 (2020-02)
Table 6: NG eCall Types and related URNs
NG eCall Type NG eCall URNs Proposed Plugfest URNs
IETF RFC 8147 [8]
Manual urn:service:sos.ecall.manual urn:service:test.sos.ecall.manual.psap1
urn:service:test.sos.ecall.manual.psap2
..
urn:service:test.sos.ecall.manual.psapn
Automatic urn:service:sos.ecall.automatic urn:service:test.sos.ecall.automatic.psap1
urn:service:test.sos.ecall.automatic.psap2
..
urn:service:test.sos.ecall.automatic.psapn
Test urn:service:test.sos.ecall urn:service:test.sos.ecall.psap1
urn:service:test.sos.ecall.psap2
..
urn:service:test.sos.ecall.psapn
NOTE: Not every IVS may support proposed Plugfest URNs.

5.2 NG eCall HLAP flow diagram
An NG IVS should register to the network by performing the attach procedure. NG IVS may perform IMS registration
if used for other services then eCall. When NG eCall is triggered, an NG IVS will perform IMS emergency registration
procedure as shown in Figure 2.

Figure 2: IMS emergency registration
1) NG IVS sends REGISTER to the PLMN.
2) NG IVS receives 200 OK from the PLMN.
After the IMS emergency registration procedure the NG IVS initiates an IMS eCall as shown in Figure 3.
ETSI
15 ETSI TS 103 683 V1.1.1 (2020-02)

Figure 3: eCall session
1) The NG IVS receives a trigger to establish a manual or automatic NG eCall.
2) An initial emergency INVITE is sent to the PLMN. The INVITE shall contain the initial MSD and the eCall
type of emergency service indicator (automatic, manual).
3) The PLMN network routes the INVITE towards the appropriate NG PSAP.
4) The NG PSAP verifies the correctness of the initial MSD and returns a 200 OK, which includes a positive or
negative acknowledgement for the initial MSD.
5) The PLMN network sends the 200 OK to the NG IVS.
6) The NG IVS sends ACK for the 200 OK INVITE.
7) The NG PSAP receives ACK for the 200 OK INVITE from the PLMN.
8) The emergency call establishment is completed. The established media channel supports bidirectional voice
communication.
9) Only the NG PSAP is able to release the session.
10) The NG PSAP sends BYE towards PLMN.
11) PLMN routes BYE towards NG IVS.
12) NG IVS confirms session release and sends the 200 OK BYE to the PLMN.
13) PLMN forwards 200 OK to the NG PSAP.
Figure 4 illustrates when 2-way-speech is established and during the call, the NG PSAP sends a request for an MSD
update in an INFO request. The NG IVS sends the updated MSD in a new INFO request.
ETSI
16 ETSI TS 103 683 V1.1.1 (2020-02)

Figure 4: PSAP requests MSD update
1) The emergency call establishment is completed. The established media channel supports bidirectional voice
communication.
2) NG PSAP triggers MSD update request.
3) NG PSAP sends a request for an MSD in an INFO request towards NG IVS.
4) NG IVS receives request for an MSD update.
5) NG IVS confirms the reception of the request with 200 OK INFO.
6) NG PSAP receives 200 OK INFO.
7) NG IVS sends new INFO with updated MSD towards NG PSAP.
8) NG PSAP receives INFO with updated MSD and validates it.
9) NG PSAP sends 200 OK INFO, which includes a positive or negative acknowledgement for the update MSD.
10) The PLMN network routes the 200 OK INFO to the NG IVS.
6 Test Configurations
6.0 Introduction
The following clauses define multiple test configurations, which reflect the cases A and D from the Table H.2 in ETSI
TS 123 167 [2].
6.1 Home Interoperability Test Configuration
Interoperability tests will be performed using the setup shown in Figure 5. The HPLMN shall indicate support of Voice
over IMS over PS sessions (VoIMS), IMS Emergency Services (EMS) and eCall Over IMS (ECL). 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.
ETSI
17 ETSI TS 103 683 V1.1.1 (2020-02)
HMI
HPLMN
NG PSAP
NG IVS
(VoIMS, EMS,
ECL supported)
Audio
interface
Figure 5: NG_eCall_CFG_01
NG IVS, HPLMN and NG PSAP can be either real devices or simulators. PSAP simulator is understood to be only
simulating the PSAP connected to the public network with fixed line connection (SIP trunk).
NOTE: To switch between NG_eCall_CFG_01 (Home) and NG_eCall_CFG_03 (Visited) configuration simply
change the NG IVS USIM card.
6.2 Home Interoperability Test Configuration with fallback to
legacy eCall
Interoperability tests will be performed using the setup shown in Figure 6. 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.
HMI
HPLMN
NG PSAP
NG IVS
(VoIMS, EMS,
ECL supported)
Audio
interface
HMI
PLMN
PSAP
(CS domain)
Audio
interface
Legacy (CS) eCall
Figure 6: NG_eCall_CFG_02
NG IVS, HPLMN, PLMN, NG PSAP and PSAP can be either real devices or simulators.
6.3 Visited Interoperability Test Configuration
This configuration is used to represent a roaming scenario. Interoperability tests will be performed using the setup
shown in Figure 7. 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.
HMI
VPLMN
NG PSAP
NG IVS
(VoIMS, EMS,
ECL supported)
Audio
interface
Figure 7: NG_eCall_CFG_03
NG IVS, VPLMN and NG PSAP can be either real devices or simulators. PSAP simulator is understood to be only
simulating the PSAP connected to the public network with fixed line connection (SIP trunk).
ETSI
18 ETSI TS 103 683 V1.1.1 (2020-02)
6.4 Multiple IVS Interoperability Test Configuration
In the Interoperability test configuration NG_eCall_CFG_04, more than one NG IVS will repetitively call the same NG
PSAP to simulate a real service. The NG PSAP shall be able to handle a certain number of parallel emergency calls and
route them to a certain number of operator phones.
NG IVS 1 HMI
HPLMN or
VPLMN NG PSAP
NG IVS 2
(VoIMS, EMS,
ECL supported)
Audio
Interface
NG IVS n
Figure 8: NG_eCall_CFG_04
6.5 Home Interoperability Test Configuration rerouting to
another PSAP
Interoperability tests will be performed using the setup shown in Figure 9. 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.
HMI
HPLMN
NG PSAP 1
NG IVS
(VoIMS, EMS,
ECL supported)
Audio
interface
HMI
NG PSAP 2
Audio
interface
Figure 9: NG_eCall_CFG_05
NG IVS, HPLMN, NG PSAP 1 and NG PSAP 2 can be either real devices or simulators. PSAP simulator is understood
to be only simulating the PSAP connected to the public network with fixed line connection (SIP trunk).
6.6 Home Interoperability Test Configuration without VoIMS
support
Following test configuration reflects the case D from Table H.2 in ETSI TS 123 167 [2]. The HPLMN shall indicate
support of IMS Emergency Services (EMS) and eCall Over IMS (ECL) and shall not indicate support of Voice over
IMS over PS sessions (VoIMS).
Interoperability tests will be performed using the setup shown in Figure 10. 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.
ETSI
19 ETSI TS 103 683 V1.1.1 (2020-02)
HMI
HPLMN
NG PSAP
NG IVS
(EMS, ECL
supported)
Audio
interface
Figure 10: NG_eCall_CFG_06
NG IVS, HPLMN and NG PSAP can be either real devices or simulators. PSAP simulator is understood to be only
simulating the PSAP connected to the public network with fixed line connection (SIP trunk).
6.7 Default pre-test conditions
The following default pre-test conditions apply to all tests unless otherwise stated in the test cases description:
1) Ignition is ON and NG IVS is in mobile network coverage
2) NG MNO and NG PSAP test points are available
3) NG IVS registered to the PLMN (HPLMN or VPLMN)
4) NG IVS has all the information needed to compile the MSD
5) NG IVS configured to support IMS communication profile
6) NG IVS contains USIM
6.8 Interoperable Functions Statement (IFS)
All IFS items referred to in this clause are as specified in CEN TS 17184:2018 [4] unless indicated otherwise by another
numbered reference.
Table 7: PSAP features
Item Entity IFS_ID Reference Status Support
1 PSAP supports IMS-eCall PSAP_ims_eCall 7.1.3 m
2 PSAP supports legacy CS in-band eCall PSAP_legacy_eCall 7.1.3 m
3 PSAP supports IPv4 PSAP_IPv4 7.1.3 m
4 PSAP supports IPv6 PSAP_IPv6 7.1.3 m
5 PSAP supports voice communication PSAP_speech 7.1. m
6 PSAP supports simultaneous eCalls PSAP_simult_eCalls 7.8.1 o
7 PSAP supports callback PSAP_callback 7.11 m
8 PSAP supports request MSD update or PSAP_MSD_update 7.7.1 item 1 m
new MSD
9 PSAP supports reception of MSD via PSAP_MSD_usingInBand_ 7.3.6 m
in-band modem within the IMS eCall via_VoLTE

ETSI
---------------------- Pag
...