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

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.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à laSous-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 athttps://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 andof the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members andof 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 ........................................................................................................................................................62

References ................................................................................................................................................6

2.1
2.2

3
3.1
3.2
3.3

4
4.1
4.1.1
4.1.2
4.1.3
4.2
4.3
4.4

5
5.1
5.2

6
6.0
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8

7
7.0
7.1
7.1.1
7.1.2
7.1.3
7.1.4
7.1.5
7.1.6
7.1.7
7.1.8
7.1.9
7.1.107.1.117.1.127.1.137.1.14
7.2
7.2.1
7.2.2

Normative references ......................................................................................................................................... 6
Informative references ........................................................................................................................................ 7

Definition of terms, symbols and abbreviations .......................................................................................7
Terms.................................................................................................................................................................. 7
Symbols .............................................................................................................................................................. 8
Abbreviations ..................................................................................................................................................... 8

Conventions ..............................................................................................................................................9Interoperability test process ................................................................................................................................ 9
Principles ...................................................................................................................................................... 9
The test description proforma ....................................................................................................................... 9Interoperable Functions Statement ............................................................................................................... 9
Tooling ............................................................................................................................................................. 10
Test Description naming convention ................................................................................................................ 10
Test Summary .................................................................................................................................................. 10

Test Bed Architecture.............................................................................................................................12
Test site layout ................................................................................................................................................. 12
NG eCall HLAP flow diagram ......................................................................................................................... 14

Test Configurations ................................................................................................................................16
Introduction ...................................................................................................................................................... 16
Home Interoperability Test Configuration ....................................................................................................... 16
Home Interoperability Test Configuration with fallback to legacy eCall ......................................................... 17
Visited Interoperability Test Configuration ..................................................................................................... 17
Multiple IVS Interoperability Test Configuration ............................................................................................ 18
Home Interoperability Test Configuration rerouting to another PSAP ............................................................ 18
Home Interoperability Test Configuration without VoIMS support ................................................................ 18
Default pre-test conditions ............................................................................................................................... 19
Interoperable Functions Statement (IFS) .......................................................................................................... 19

NG eCall test scenarios/descriptions ......................................................................................................20
Introduction ...................................................................................................................................................... 20
Basic test scenarios ........................................................................................................................................... 21
Initiation of manual eCall ........................................................................................................................... 21
Initiation of automatic eCall ....................................................................................................................... 21
Initiation of test eCall ................................................................................................................................. 22
MSD transfer to PSAP supporting IMS eCall............................................................................................. 22
MSD transfer to PSAP supporting IMS eCall in roaming scenario ............................................................ 23
PSAP initiated callback to IVS and MSD update ....................................................................................... 24
PSAP initiated call clear-down ................................................................................................................... 26
IVS initiated call clear-down not allowed................................................................................................... 27
Verification of audio interfaces of IVS and PSAP...................................................................................... 27
MSD update on request from PSAP ........................................................................................................... 28
IVS behaviour after unsuccessful MSD update .......................................................................................... 28
IVS behaviour after unacknowledged MSD update.................................................................................... 29
Format of encoded and decoded MSD in accordance with CEN EN 15722:2015...................................... 30
MSD transfer via in-band modem to PSAP supporting IMS eCall ............................................................. 31
Advanced test scenarios ................................................................................................................................... 32
MSD transfer to PSAP supporting IMS eCall over IPv4 ............................................................................ 32
MSD transfer to PSAP supporting IMS eCall over IPv6 ............................................................................ 32

ETSI

4

7.2.3
7.2.4
7.2.5
7.2.6
7.2.7
7.3
7.3.1
7.3.2
7.3.3
7.3.4
7.3.5
7.3.6
7.3.7
7.3.8
7.3.9
7.3.107.3.11
7.4
7.4.1
7.4.2
7.4.3
7.4.4

MSD transfer to PSAP supporting IMS eCall over IPv4(IVS)/IPv6(PSAP) .............................................. 33
MSD transfer to PSAP not supporting IMS eCall ...................................................................................... 34
IMS eCall establishment with IMS emergency registration ....................................................................... 36
IMS eCall establishment without IMS emergency registration .................................................................. 38
IMS eCall establishment without IMS emergency registration GIBA supported ....................................... 38
Advanced IVS test scenarios ............................................................................................................................ 39
Fallback to legacy eCall following busy during call setup ......................................................................... 39
Fallback to legacy eCall following unavailable response during call setup ................................................ 41
Fallback to legacy eCall following no-answer during call setup ................................................................ 42
Dropped eCall after MSD has been acknowledged .................................................................................... 44
Dropped eCall before call has been established .......................................................................................... 45
IVS configured for 'eCall only' service (restricted) .................................................................................... 46
eCall is attempted when no networks are available (limited service condition with forbidden PLMN
on SIM/USIM) ............................................................................................................................................ 46
MSD transfer to PSAP supporting IMS eCall via PLMN without VoIMS support .................................... 47
Termination of manually triggered eCall by vehicle occupant ................................................................... 47
Termination of automatically triggered eCall by vehicle occupant not allowed/not possible .................... 48
Ongoing eCall shall not be disconnected if new trigger is received ........................................................... 48
Advanced PSAP test scenarios ......................................................................................................................... 49
PSAP handling of more than 1 eCall simultaneously ................................................................................. 49
PSAP correct MSD additional data decoding ............................................................................................. 49
Rerouting to another PSAP/emergency control centre ............................................................................... 50
PSAP operator user interface ...................................................................................................................... 50

Annex A (informative):
A.1

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

Source code of MSC figures ..........................................................................51

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 foundin 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 noright 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 ofprovisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI

6

1

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

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 thereferenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found athttps://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

2.2

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

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 thereferenced 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 theuser 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, orinformation 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
servicesNOTE:

The IVS is not permitted to register on a PLMN except for the purpose of making an eCall, or atest/reconfiguration call to a designated non-emergency number, in accordance with ETSITS 122 101 [11]. Following power-up the IVS may perform a PLMN search and maintain a list ofavailable 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 accessother 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 orother 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 theirimplementation
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 aset 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
ACK
CEN
CFG
CS
CSCF
E-CSCF
E-UTRAN
ECL
EMS
ETR
ETSI
EU
EUT
GIBA
GSM
HLAP
HMI
HPLMN
HSS
I-CSCFIFS
IFS_ID
IMEI

Third Generation Partnership Project
ACKnowledgement
Comité Européen de Normalisation
ConFiGuration
Circuit Switched
Call Session Control Function
Emergency CSCF
Enhanced UMTS Terrestrial Radio Access Network
eCall Over IMS support
IMS Emergency Services
ETSI Technical Report
European Telecommunications Standards InstituteEuropean Union
Equipment Under Test
GPRS-IMS-Bundled-Authentication
Global System of Mobile telecommunications
High Level Application Protocol
Human Machine Interface
Home PLMN
Home Subscriber ServerInterrogating CSCF
Interoperable Functions Statement
IFS Identifier
International Mobile Equipment Identity

ETSI

9

IMS
IVS
LTE
MNO
MSD
NACK
NG
P-CSCF
PLMN
PS
PSAP
S-CSCF
SIP
TD
TS11
TS12
UMTS
URN
VoIMS
VoLTE
VPLMN

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

IP Multimedia Subsystem
In Vehicle System
Long Term Evolution
Mobile Network Operator
Minimum Set of Data
Negative Acknowledgement
Next Generation
Proxy CSCF
Public Land Mobile Network
Packet Switched
Public Service Answering Point
Serving CSCF
Session Initiation Protocol
Test Description
Teleservice No 11 (Telephony)Teleservice No 12 (Emergency Calls)
Universal Mobile Telecommunications System
Unique Resource Name
Voice over IMS
Voice over LTE
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] andETSI 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, likesending 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 wheninteroperating 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 implicitlymeans "is <item description> 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:mmandatory - the capability is required to be supported.

ooptional - 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.iqualified 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 isdefined immediately following the table.

c.iconditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on the support ofother optional or conditional items. "i" is an integer identifying an unique conditional status
expression which is defined immediately following the table.

iirrelevant (out-of-scope) - capability outside the scope of the reference specification. No answer isrequested 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 ysupported by the implementation.

N or nnot 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

4.3

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

Test Description naming convention
Table 1: TD naming convention
TD_<root>_[gr]_<nn><root> = root applicability[gr] = group<nn> = sequential number

4.4

BAS
ADV
IVS
PSAP
01 to 99

Basic test
Advanced test
IVS eCall terminal
PSAP eCall server
IVS or PSAP
Sequential numbers

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
TD_BAS_01
TD_BAS_02
TD_BAS_03
TD_BAS_04
TD_BAS_05
TD_BAS_06
TD_BAS_07
TD_BAS_08
TD_BAS_09
TD_BAS_10
TD_BAS_11
TD_BAS_12
TD_BAS_13
TD_BAS_14

Title
Initiation of manual eCall
Initiation of automatic eCall
Initiation of test eCall
MSD transfer to PSAP supporting IMS eCall
MSD transfer to PSAP supporting IMS eCall in roaming scenario
PSAP initiated callback to IVS and MSD update
PSAP initiated call clear-down
IVS initiated call clear-down not allowed
Verification of audio interfaces of IVS and PSAP
MSD update on request from PSAP
IVS behaviour after unsuccessful MSD update
IVS behaviour after unacknowledged MSD update
Format of encoded and decoded MSD in accordance with CEN EN 15722:2015 [10]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
TD_ADV_01
TD_ADV_02
TD_ADV_03
TD_ADV_04
TD_ADV_05
TD_ADV_06
TD_ADV_07

Title
MSD transfer to PSAP supporting IMS eCall over IPv4
MSD transfer to PSAP supporting IMS eCall over IPv6
MSD transfer to PSAP supporting IMS eCall over IPv4(IVS)/IPv6(PSAP)
MSD transfer to PSAP not supporting IMS eCall
IMS eCall establishment with IMS emergency registration
IMS eCall establishment without IMS emergency registration
IMS eCall establishment without IMS emergency registration GIBA supported

Table 4: Advanced Tests for IVS
Test case ID
TD_ADV_IVS_01
TD_ADV_IVS_02
TD_ADV_IVS_03
TD_ADV_IVS_04
TD_ADV_IVS_05
TD_ADV_IVS_06
TD_ADV_IVS_07
TD_ADV_IVS_08
TD_ADV_IVS_09
TD_ADV_IVS_10
TD_ADV_IVS_11

Title
Fallback to legacy eCall following busy during call setup
Fallback to legacy eCall following unavailable response during call setup
Fallback to legacy eCall following no-answer during call setup
Dropped eCall after MSD has been acknowledged
Dropped eCall before call has been established
IVS configured for 'eCall only' service (restricted)
eCall is attempted when no networks are available (limited service condition withforbidden PLMN on SIM/USIM)
MSD transfer to PSAP supporting IMS eCall via PLMN without VoIMS support
Termination of manually triggered eCall by vehicle occupant
Termination of automatically triggered eCall by vehicle occupant not allowed/not
possible
Ongoing eCall shall not be disconnected if new trigger is received

Table 5: Advanced Tests for PSAP
Test case ID
TD_ADV_PSAP_01
TD_ADV_PSAP_02
TD_ADV_PSAP_03
TD_ADV_PSAP_04

Title
PSAP handling of more than 1 eCall simultaneously
PSAP correct MSD additional data decoding
Rerouting to another PSAP/emergency control centre
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

PLMN

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

National
NG PSAP(VoIMS, EMS, ECL
supported)

NG IVS...

Local
NG PSAPNG PSAP +PLMN
simulator

...

Local
NG PSAP

Remote NG PSAP...

NG IVS
Remote NG PSAP

CS Fallback

The NG PSAPs are reached by predefined URNs andshall be assigned by the PLMN

Legacy eCallrefer 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 theninterpreted 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 tocarry 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
ManualNG eCall URNs
IETF RFC 8147 [8]urn:service:sos.ecall.manual

Proposed Plugfest URNs

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

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 update1)

The emergency call establishment is completed. The established media channel supports bidirectional voicecommunication.

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 ETSITS 123 167 [2].

6.1Home Interoperability Test Configuration

Interoperability tests will be performed using the setup shown in Figure 5. The HPLMN shall indicate support of Voiceover IMS over PS sessions (VoIMS), IMS Emergency Services (EMS) and eCall Over IMS (ECL). Ancillarymeasurement and message logging equipment is not shown but may be used, with the agreement of the participants, tohelp identify the likely cause of any interoperability test failures that may arise.

ETSI

17

NG IVSETSI TS 103 683 V1.1.1 (2020-02)

HMI

HPLMN

NG PSAP(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:

6.2

To switch between NG_eCall_CFG_01 (Home) and NG_eCall_CFG_03 (Visited) configuration simply
change the NG IVS USIM card.

Home Interoperability Test Configuration with fallback tolegacy 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.

NG IVSHMIHPLMNNG PSAP(VoIMS, EMS,ECL supported)

Audio
interface

PLMN

PSAP

(CS domain)

Legacy (CS) eCall

HMI

Audio
interface

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 theagreement of the participants, to help identify the likely cause of any interoperability test failures that may arise.

NG IVSHMIVPLMNNG PSAP(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

6.4

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

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 androute them to a certain number of operator phones.
NG IVS 1
NG IVS 2HMIHPLMN orVPLMNNG PSAP(VoIMS, EMS,ECL supported)

Audio
Interface

NG IVS n
Figure 8: NG_eCall_CFG_04

6.5

Home Interoperability Test Configuration rerouting toanother 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.

NG IVSHMIHPLMNNG PSAP 1(VoIMS, EMS,ECL supported)

Audio
interface
HMI
NG PSAP 2
Audiointerface

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.6Home Interoperability Test Configuration without VoIMS
supportFollowing 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

NG IVSETSI TS 103 683 V1.1.1 (2020-02)

HMI

HPLMN

NG PSAP(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 anothernumbered reference.
Table 7: PSAP features
Item
1
2
3
4
5
6
7
8
9

EntityPSAP supports IMS-eCall
PSAP supports legacy CS in-band eCall
PSAP supports IPv4
PSAP supports IPv6
PSAP supports voice communication
PSAP supports simultaneous eCalls
PSAP supports callback
PSAP supports request MSD update or
new MSD
PSAP supports reception of MSD via
in-band modem within the IMS eCall

IFS_ID
PSAP_ims_eCall
PSAP_legacy_eCall
PSAP_IPv4
PSAP_IPv6
PSAP_speech
PSAP_simult_eCalls
PSAP_callback
PSAP_MSD_update
PSAP_MSD_usingInBand_
via_VoLTE

ETSIReference
7.1.3
7.1.3
7.1.3
7.1.3
7.1.
7.8.1
7.11
7.7.1 item 1

Status
m
m
m
m
m
o
m
m

7.3.6

m

Support20

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

Table 8: IVS features
Item
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

EntityIVS supports IMS-eCall
IVS supports legacy CS in-band eCall
IVS supports automatic eCall activation
IVS supports manual eCall activation
IVS supports test call
IVS supports eCall only
IVS supports IPv4
IVS supports IPv6
IVS supports voice communication
IVS supports MSD version 2
IVS supports additional MSD data
IVS supports PSAP callback
IVS supports transfer of MSD update or new
MSD
IVS supports transfer of MSD via in-band
modem within the IMS eCall
IVS supports GIBA procedure

IFS_ID
IVS_ims_eCall
IVS_legacy_eCall
IVS_auto_eCall
IVS_man_eCall
IVS_test_eCall
IVS_eCall_only
IVS_IPv4
IVS_IPv6
IVS_speech
IVS_MSDv2
IVS_add_MSD_data
IVS_callback
IVS_MSD_update
IVS_MSD_usingInBand_
via_VoLTEIVS_GIBA

Reference
7.1.2
7.1.2
7.3.6
7.3.6
7.1.5
7.1.4
7.1.2
7.1.2
7.1.
7.5.1
7.5.1
7.11
7.7.1 item 3

Status
m
m
m
m
m
o
m
m
m
m
o
m
m

7.3.6

m

ETSI
TS 124 229 [1]o7NG eCall test scenarios/descriptions

7.0

Introduction

Support

The tests defined in the present document shall be performed according to the test applicability. The test applicability isdefined in each test in the field 'Applicability' and is expressed with IFS statements. The tests apply to IVS and PSAP aswell as to IVS and PSAP simulators.
Following test descriptions are covering IMS eCall scenarios and some CS eCall fallback scenarios. Legacy CS eCall
test descriptions are specified in ETSI TS 103 428 [9].

ETSI

21

7.1

Basic test scenarios

7.1.1

Initiation of manual eCall

Identifier:Objective:

Configuration:
References:

Applicability:

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

Interoperability Test Description
TD_BAS_01
Verify that the IVS is able to initiate a manual eCall containing INVITE request
indicating service URN value. Verify that the received MSD contains the correct eCallinitiation indicator for a manually triggered eCall.
NG_eCall_CFG_01
Clauses 7.1.2 and 7.3.6 of CEN TS 17184:2018 [4]Clause 14.2 of IETF RFC 8147 [8]Clause 6.3.2 of CEN EN 15722:2015 [10]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_man_eCall

Pre-test conditions: Default see clause 6.7(see note 2)
Test Sequence:

Description
IVS initiates a manual eCall
Open the received INVITE request and check if service URN
contains "urn:service:sos.ecall.manual" (see note 1)
3
verifyPSAP verifies the MSD (in an INVITE request) is received
4
checkOpen the received MSD and check if block 3 contains an
indication that the eCall was manually initiated(automaticActivation = false)
NOTE 1: Test step 2 is only relevant, if the URN value "urn:service:sos.ecall.manual" is used.
NOTE 2: If the PSAP is only reachable via test URN, for testing purposes the URN value"urn:service:test.sos.ecall" should be used instead of the URN value"urn:service:sos.ecall.manual".

7.1.2

Step
1
2

Type
stimulus
check

Initiation of automatic eCall

Identifier:Objective:

Configuration:
References:

Applicability:

Interoperability Test Description
TD_BAS_02
Verify that the IVS is able to initiate an automatic eCall containing INVITE request
indicating service URN value. Verify that the received MSD contains the eCallinitiation indicator for an automatic triggered eCall.
NG_eCall_CFG_01
Clauses 7.1.2 and 7.3.6 of CEN TS 17184:2018 [4]Clause 14.2 of IETF RFC 8147 [8]Clause 6.3.2 of CEN EN 15722:2015 [10]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_auto_eCall

Pre-test conditions: Default see clause 6.7(see note 2)
Test Sequence:

Step
1
2

Type
stimulus
check

Description
IVS initiates an automatic eCall
Open the received INVITE request and check if service URN
contains "urn:service:sos.ecall.automatic" (see note 1)
3
verifyPSAP verifies the MSD (in an INVITE request) is received
4
checkOpen the received MSD and check if block 3 contains an
indication that the eCall was automatically initiated(automaticActivation = true)
NOTE 1: Test step 2 is only relevant, if the URN value "urn:service:sos.ecall.automatic" is used.
NOTE 2: If the PSAP is only reachable via test URN, for testing purposes the URN value"urn:service:test.sos.ecall" should be used instead of the URN value"urn:service:sos.ecall.automatic".

ETSI

22

7.1.3

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

Initiation of test eCall

Applicability:

Interoperability Test Description
TD_BAS_03
Verify that the IVS is able to initiate a test eCall containing INVITE request indicating
service URN value "urn:service:test.sos.ecall". Verify that the received MSD contains
the correct test eCall indicator for a test eCall (see note).
NG_eCall_CFG_01
Clause 7.2.2 of CEN TS 17184:2018 [4]Clause 14.2 of IETF RFC 8147 [8]Clause 6.3.2 of CEN EN 15722:2015 [10]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_test_eCall

Pre-test conditions:Default see clause 6.7

Test Sequence:

Step
1
2

Identifier:Objective:

Configuration:
References:

NOTE:

7.1.4

Type
stimulus
check

Description
IVS initiates a test eCall
Open the received INVITE request and check if service URN
contains "urn:service:test.sos.ecall"3
verifyPSAP verifies the MSD (in an INVITE request) is received (see
note)
4
check
Open the received MSD and check if block 3 contains an indicationthat the eCall is a test eCall (testCall = true) (see note)
The second test objective and the test steps 3 to 4 are optional until detailed requirements for the MSD
transfer in a test eCall become available.

MSD transfer to PSAP supporting IMS eCall

Identifier:Objective:
Configuration:
References:
Applicability:

Interoperability Test Description
TD_BAS_04
Verify that the IVS is able to transfer the MSD (in an INVITE request) to a PSAP
supporting IMS eCall.
NG_eCall_CFG_01
Clauses 7.4.1 and 7.4.2 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall

Pre-test conditions: Default see clause 6.7:•
PSAP operator knows the content of the transmitted MSD
Test Sequence:

Step
1
2
3
4

Type
stimulus
verifyverifyverify56checkverifyDescription
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded
IVS receives a 200 OK INVITE response with a positive
acknowledgment for the MSD
MSD content at PSAP is identical to content transmitted by IVS
PSAP receives ACK request on 200 OK INVITE response

ETSI

23

7.1.5

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

MSD transfer to PSAP supporting IMS eCall in roaming scenario

Identifier:Objective:
Configuration:
References:
Applicability:

Interoperability Test Description
TD_BAS_05
Verify that the IVS is able to transfer the MSD (in an INVITE request) to a PSAP
supporting IMS eCall in roaming scenario.
NG_eCall_CFG_03
Clauses 7.3.2, 7.4.1 and 7.4.2 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall

Pre-test conditions: Default see clause 6.7:•
PSAP operator knows the content of the transmitted MSD
Test Sequence:

Step
1
2
3
4

Type
stimulus
verifyverifyverify56checkverifyDescription
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded
IVS receives a 200 OK INVITE response with a positive
acknowledgment for the MSD
MSD content at PSAP is identical to content transmitted by IVS
PSAP receives ACK request on 200 OK INVITE response

ETSI

24

7.1.6

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

PSAP initiated callback to IVS and MSD update

Identifier:Objective:
Configuration:
References:
Applicability:

Interoperability Test Description
TD_BAS_06
Verify that if an eCall has been successfully terminated by the PSAP, then the IVS
shall answer a PSAP callback and send a MSD update on request of the PSAP.
NG_eCall_CFG_01
Clauses 7.7.2 and 7.11 of CEN TS 17184:2018 [4]Clause 7.17.3 of CEN EN 16072:2015 [7]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_speech AND PSAP_speech AND
IVS_callback AND PSAP_callback AND IVS_MSD_update AND PSAP_MSD_update

Pre-test conditions: Default see clause 6.7
Test Sequence:

Step
1
2
3
4

Type
stimulus
verifycheck
verifyDescription
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded (MSD ID = 1)
IVS receives a 200 OK INVITE response with a positive
acknowledgment for the MSD
5verifyPSAP receives ACK request on 200 OK INVITE response6
verify2-way speech can be exchanged
7
stimulus PSAP clears down the call (via BYE request)
8
verifyIVS has cleared down the call (confirmed with 200 OK BYE
response)
9stimulus PSAP initiates a callback (via INVITE request) using IVS callback
number, SIP identifier or IP address
10
verifyIVS confirms the call with a 200 OK INVITE response11
verifyPSAP sends ACK request on 200 OK INVITE response
12
verify2-way speech can be exchanged
13
stimulus PSAP sends request (in an INFO request) for MSD update whilethe 2-way conversation is in progress
14
verifyPSAP receives 200 OK INFO response15
verifyPSAP verifies the MSD update (in an INFO request) is received(see note 1)
16
check
PSAP verifies the MSD is correctly decoded (MSD ID = 2)17verifyIVS receives a 200 OK INFO response with a positive
acknowledgment for the MSD
18
verify2-way speech can be exchanged
19
stimulus PSAP clears down the call (via BYE request)
20
verifyIVS has cleared down the call (confirmed with a 200 OK BYE
response)
NOTE 1: Step 15 is currently optional, due to the following note in clause 7.7.2 of CEN TS 17184:2018 [4]:"The IMS eCall solution currently defined in ETSI TS 122 101, ETSI TS 123 167 and IETF eCall
RFC 8147 does not support authentication by a vehicle IVS that an incoming call is from a PSAP or
use of the procedures defined in 7.4 and 7.5 to enable a PSAP Operator to obtain an updated MSD
from an IVS as part of callback from the PSAP."
NOTE 2: MSC of callback scenario after successfully terminated eCall is shown in Figure 11.

ETSI

25

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

Figure 11: Callback scenario after successfully terminated eCall
1)

After NG IVS was registered and the NG eCall was successfully released NG PSAP triggers a callback.

2)

An initial INVITE is sent to the PLMN.

3)

The PLMN network routes the INVITE towards the NG IVS.

4)The NG IVS returns a 200 OK INVITE to the PLMN.

5)The PLMN network sends the 200 OK INVITE to the NG PSAP.

6)The NG PSAP sends ACK for the 200 OK INVITE.

7)

The NG IVS receives ACK for the 200 OK INVITE from the PLMN.

8)

The callback establishment is completed. Media channels are established.

9)

NG PSAP trigger MSD update request.

10) NG PSAP sends a request for an MSD in an INFO request towards NG IVS.
11) NG IVS receives request for an MSD update.
12) NG IVS confirms the reception of the request with 200 OK INFO.

ETSI

26

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

13) NG PSAP receives 200 OK INFO.
14) NG IVS sends new INFO with updated MSD towards NG PSAP.
15) NG PSAP receives INFO with updated MSD and validate it.
16) NG PSAP sends 200 OK INFO, which includes a positive or negative acknowledgement for the update MSD.
17) The PLMN network routes the 200 OK INFO to the NG IVS.
18) Only NG PSAP is able to release the session.
19) The NG PSAP sends BYE towards PLMN.
20) PLMN routes BYE towards NG IVS.
21) NG IVS confirm session release and sends the 200 OK BYE to the PLMN.
22) PLMN forwards 200 OK to the NG PSAP.

7.1.7

PSAP initiated call clear-down

Identifier:Objective:
Configuration:
References:
Applicability:

Interoperability Test Description
TD_BAS_07
Verify that when the PSAP clears down the call, the IVS also clears down the callfollowing receipt of a BYE request.
NG_eCall_CFG_01
Clause 7.10 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_speech AND PSAP_speechPre-test conditions: Default see clause 6.7
Test Sequence:

NOTE:

Step
1
2
3
4
5
6

Type
stimulus
verifyverifyverifystimulus
verifyDescription
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded
2-way speech can be exchanged
PSAP clears down the call (via BYE request)
IVS has cleared down the call (confirmed with a 200 OK BYE
response)
An application layer clear-down as defined in CEN EN 16062:2015 [i.2] is not applicable for IMS
eCall.

ETSI

27

7.1.8

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

IVS initiated call clear-down not allowed

Identifier:Objective:
Configuration:
References:
Applicability:

Interoperability Test Description
TD_BAS_08
Verify that when the eCall was established an IVS initiated call clear-down is notallowed before expiry of timer T2.
NG_eCall_CFG_01
Clause 6 and Annex A of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_speech AND PSAP_speechPre-test conditions: Default see clause 6.7
Test Sequence:

NOTE:

7.1.9

Step
1
2
3
4
5

Type
stimulus
verifyverifyverifystimulus

Description
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded
2-way speech can be exchanged
IVS attempts to clears down the call (via BYE request) before
expiry of timer T2 (see note)
6
verifyeCall in progress was not disconnected
7
stimulus PSAP clears down the call (via BYE request)
8
verifyIVS has cleared down the call (confirmed with a 200 OK BYE
response)
A compliant IVS should not be able to clear down the call before expiry of timer T2. This 'negative'
test should ensure that the IVS can gracefully handle invalid input or unexpected user behaviour.

Verification of audio interfaces of IVS and PSAP

Identifier:Objective:

Configuration:
References:
Applicability:

Interoperability Test Description
TD_BAS_09
Verify that the PSAP sends acknowledgement (in the final response to the INVITE), if
MSD check is successful. Verify that the IVS and PSAP audio interfaces areconnected and 2-way speech is possible between the IVS and PSAP.
NG_eCall_CFG_01
Clauses 7.5.1 and 7.9 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_speech AND PSAP_speechPre-test conditions: Default see clause 6.7
Test Sequence:

Step
1
2
3
4

Type
stimulus
verifyverifyverify5
6

verifyverifyDescription
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded
IVS verifies the 200 OK INVITE response with positive
acknowledgement for the received MSD
PSAP receives ACK request on 200 OK INVITE response
2-way speech can be exchanged

ETSI

28

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

MSD update on request from PSAP

Identifier:Objective:
Configuration:
References:
Applicability:

Interoperability Test Description
TD_BAS_10
Verify that the IVS is able to recognize and act upon a request from the PSAP, duringongoing eCall, to send an updated MSD.
NG_eCall_CFG_01
Clause 7.7.1 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_speech AND PSAP_speech AND
IVS_MSD_update AND PSAP_MSD_update

Pre-test conditions: Default see clause 6.7
Test Sequence:

7.1.11

Step
1
2
3
4

Type
stimulus
verifycheck
verify5
67

verifyverifystimulus

8
9
10
11

verifyverifycheck
verifyDescription
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded (MSD ID = 1)
IVS receives a 200 OK INVITE response with a positive
acknowledgment for the MSD
PSAP receives ACK request on 200 OK INVITE response
2-way speech can be exchanged
PSAP sends request (in an INFO request) for MSD update
while the 2-way conversation is in progress
PSAP receives 200 OK INFO response
PSAP verifies the MSD update (in an INFO request) is received
PSAP verifies the MSD is correctly decoded (MSD ID = 2)
IVS receives a 200 OK INFO response with a positive
acknowledgment for the MSD

IVS behaviour after unsuccessful MSD update

Identifier:Objective:

Configuration:
References:
Applicability:

Interoperability Test Description
TD_BAS_11
Verify that the PSAP sends negative acknowledgement (in the final response to the
INFO), if MSD check is unsuccessful. Verify that the IVS does not attempt to re-send
the MSD unless requested by the PSAP.
NG_eCall_CFG_01
Clauses 7.5.2, 7.6 and 7.13.1 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_speech AND PSAP_speech AND
IVS_MSD_update AND PSAP_MSD_update

Pre-test conditions: Default see clause 6.7
Test Sequence:

NOTE:

Step
1
2
3
4

Type
stimulus
verifyverifyverifyDescription
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded
IVS receives the 200 OK INVITE response with positive
acknowledgement for the MSD
5verifyPSAP receives ACK request on 200 OK INVITE response6
verify2-way speech can be exchanged (see note)
7
stimulus
PSAP sends request (in an INFO request) for MSD update
while the 2-way conversation is in progress8
verifyPSAP receives 200 OK INFO response9
verifyPSAP verifies the MSD update (in an INFO request) is received
10
verifyPSAP verifies the MSD check fails
11
verifyIVS verifies the 200 OK INFO response with negative
acknowledgement for the MSD is received
12
verifyIVS does not attempt to re-send the MSD update
After test step 6 the PSAP should be configured to send 200 OK response with NACK for the MSD
update.

ETSI

29

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

IVS behaviour after unacknowledged MSD update

Identifier:Objective:

Configuration:
References:
Applicability:

Interoperability Test Description
TD_BAS_12
Verify that the IVS does not attempt to re-send the MSD unless requested by the
PSAP, if a 200 OK INFO response (without acknowledgement for the MSD) is
received as response to the MSD update (in an INFO request).
NG_eCall_CFG_01
Clauses 7.5.3 and 7.6¶2 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_speech AND PSAP_speech AND
IVS_MSD_update AND PSAP_MSD_update

Pre-test conditions: Default see clause 6.7
Test Sequence:

NOTE:

Step
1
2
3
4

Type
stimulus
verifyverifyverifyDescription
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded
IVS receives the 200 OK INVITE response with positive
acknowledgement for the MSD
5verifyPSAP receives ACK request on 200 OK INVITE response6
verify2-way speech can be exchanged (see note)
7
stimulus
PSAP sends request (in an INFO request) for MSD update
while the 2-way conversation is in progress8
verifyPSAP receives 200 OK INFO response9
verifyPSAP verifies the MSD update (in an INFO request) is
received
10
verifyIVS verifies the 200 OK INFO response (without
acknowledgement for the MSD) is received
11
verifyIVS does not attempt to re-send the MSD
After test step 6 the PSAP should be configured to send 200 OK response without ACK/NACK for
the MSD update.

ETSI

30

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

Format of encoded and decoded MSD in accordance with CEN
EN 15722:2015

Identifier:Objective:
Configuration:
References:
Applicability:

Interoperability Test Description
TD_BAS_13
Verify that the IVS formats the MSD in accordance with CEN EN 15722:2015 [10] andencodes it correctly, and that the PSAP decodes and displays the MSD correctly.
NG_eCall_CFG_01
Clause 6.3.2 of CEN EN 15722:2015 [10]Clause 7.5.1 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_MSDv2

Pre-test conditions: Default see clause 6.7:•
PSAP operator knows the content of the transmitted MSD
Test Sequence:

Step
1
2
3
4

Type
stimulus
verifyverifyverify5
6

verifycheck

Description
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded
IVS receives the 200 OK INVITE response with positive
acknowledgement for the MSD
PSAP receives ACK request on 200 OK INVITE response
Visually inspect format, content, logic and accuracy of MSD
when decoded and displayed PSAP on screen. Check all MSD
fields according to CEN EN 15722:2015 [10].
Mandatory MSD elements:•
msdVersion (shall be set to 2)•
messageIdentifier (shall be set to 1)•
automaticActivation•
testCall•positionCanBeTrusted•
vehicleType•vehicleIdentificationNumber•
gasolineTankPresent•
dieselTankPresent•
compressedNaturalGas•
liquidPropaneGas•
electricEnergyStorage•hydrogenStorage•
otherStorage•
timestamp•
vehicleLocation•
vehicleDirection
Optional MSD elements:•
recentVehicleLocationN1•
recentVehicleLocationN2•
numberOfPassengers•
optionalAdditionalData

ETSI

31

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

MSD transfer via in-band modem to PSAP supporting IMS eCall

Identifier:Objective:
Configuration:
References:
Applicability:

Interoperability Test Description
TD_BAS_14
Verify that the IVS is able to transfer the MSD via in-band modem to a PSAP
supporting IMS eCall.
NG_eCall_CFG_01
Clause 7.3.6 of CEN TS 17184:2018 [4]Clause 5.1.6.11.2 (2nd numbered list/item 1) of ETSI TS 124 229 [1]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_MSD_usingInBand_via_VoLTE AND
PSAP_MSD_usingInBand_via_VoLTE AND IVS_speech AND PSAP_speechPre-test conditions: Default see clause 6.7:•
The PSAP should be configured to send 200 OK INVITE response with anegative acknowledgment for the MSD after step 3•
PSAP operator knows the content of the transmitted MSD
Test Sequence:

Step
1
2
3
4

Type
stimulus
verifyverifyverifyDescription
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded
IVS receives a 200 OK INVITE response with a negative
acknowledgment for the MSD
5verifyPSAP receives ACK request on 200 OK INVITE response6
verifyThe IVS shall attempt to transfer the MSD to the PSAP via
in-band modem within the IMS eCall (see note 1)
7
verifyPSAP immediately transmits SEND-MSD (START) message
without waiting for the valid Initiation Signal (see note 2)
8
verifyIf IVS had started to send an INITIATION message then IVS
stopped sending the INITIATION message on receipt of the
SEND-MSD message from the PSAP
9
verifyPSAP verifies MSD is received
10
verifyVerify the MSD is correctly decoded11check
MSD content at PSAP is identical to content transmitted by IVS
12
verifyPSAP sends acknowledgement
13
verifyVerify that the IVS has stopped transmitting the MSD
14
verify2-way speech can be exchanged
NOTE 1: The test steps 7 to 13 are copied from clause 7.1.1 of ETSI TS 103 428 [9]. Other tests from ETSITS 103 428 [9] could also be tested here.
NOTE 2: Step 7 is only applicable if the PSAP is configured in PULL mode and should be skipped, if PSAP isconfigured in PUSH mode.

ETSI

32

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

7.2

Advanced test scenarios

7.2.1

MSD transfer to PSAP supporting IMS eCall over IPv4

Identifier:Objective:
Configuration:
References:
Applicability:

Interoperability Test Description
TD_ADV_01
Verify that the IVS is able to transfer the MSD (in an INVITE request) to a PSAP
supporting IMS eCall, if IVS and PSAP are connected over IPv4.
NG_eCall_CFG_01
Clauses 7.1.2 and 7.1.3 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_IPv4 AND PSAP_IPv4

Pre-test conditions: Default see clause 6.7:•
PSAP operator knows the content of the transmitted MSD
Test Sequence:

7.2.2

Step
1
2
3

Type
stimulus
check
check

4
5

verifyverify6
7

verifycheck

Description
IVS initiates an eCall
IVS sends an INVITE request over IPv4
PSAP verifies the MSD (in an INVITE request) is received
over IPv4
PSAP verifies the MSD is correctly decoded
IVS receives a 200 OK INVITE response with a positive
acknowledgment for the MSD
PSAP receives ACK request on 200 OK INVITE response
MSD content at PSAP is identical to content transmitted by
IVS

MSD transfer to PSAP supporting IMS eCall over IPv6

Configuration:
References:
Applicability:

Interoperability Test Description
TD_ADV_02
Verify that the IVS is able to transfer the MSD (in an INVITE request) to a PSAP
supporting IMS eCall, if IVS and PSAP are connected over IPv6.
NG_eCall_CFG_01
Clauses 7.1.2 and 7.1.3 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_IPv6 AND PSAP_IPv6

Pre-test
conditions:Default see clause 6.7:•
PSAP operator knows the content of the transmitted MSD

Identifier:Objective:

Test Sequence:

Step
1
2
3

Type
stimulus
check
check

4
5

verifyverify6
7

verifycheck

Description
IVS initiates an eCall
IVS sends an INVITE request over IPv6
PSAP verifies the MSD (in an INVITE request) is received
over IPv6
PSAP verifies the MSD is correctly decoded
IVS receives a 200 OK INVITE response with a positive
acknowledgment for the MSD
PSAP receives ACK request on 200 OK INVITE response
MSD content at PSAP is identical to content transmitted by
IVS

ETSI

33

7.2.3

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

MSD transfer to PSAP supporting IMS eCall overIPv4(IVS)/IPv6(PSAP)

Configuration:
References:
Applicability:

Interoperability Test Description
TD_ADV_03
Verify that the IVS is able to transfer the MSD (in an INVITE request) to a PSAP
supporting IMS eCall, if IVS is connected over IPv4 and PSAP is connected over IPv6.
NG_eCall_CFG_01
Clauses 7.1.2 and 7.1.3 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_IPv4 AND PSAP_IPv6

Pre-test
conditions:Default see clause 6.7:•
PSAP operator knows the content of the transmitted MSD

Identifier:Objective:

Test Sequence:

Step
1
2
3

Type
stimulus
check
check

4
5

verifyverify6
7

verifycheck

Description
IVS initiates an eCall
IVS sends an INVITE request over IPv4
PSAP verifies the MSD (in an INVITE request) is received
over IPv6
PSAP verifies the MSD is correctly decoded
IVS receives a 200 OK INVITE response with a positive
acknowledgment for the MSD
PSAP receives ACK request on 200 OK INVITE response
MSD content at PSAP is identical to content transmitted by
IVS

ETSI

34

7.2.4

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

MSD transfer to PSAP not supporting IMS eCall

Identifier:Objective:
Configuration:
References:
Applicability:

Pre-test
conditions:

Test Sequence:

NOTE 1:NOTE 2:NOTE 3:
NOTE 4:

Interoperability Test Description
TD_ADV_04
Verify that the IVS is able to transfer the MSD via in-band modem to a PSAP not
supporting IMS eCall.
NG_eCall_CFG_02
Clause 7.4.3 of CEN TS 17184:2018 [4]Clause 5.1.6.11.2 (2nd numbered list/item 1) of ETSI TS 124 229 [1]IVS_ims_eCall AND PSAP_legacy_eCall AND IVS_MSD_usingInBand_via_VoLTEAND IVS_speech AND PSAP_speech
Default see clause 6.7:•
the PSAP shall not support IMS eCall•
MNO needs to support IMS eCall to legacy eCall transfer•
PSAP operator knows the content of the transmitted MSD
Step
1
2
3

Type
stimulus
verifyverify4verify5verify6verify7verify8verify9verify10

verifyDescription
IVS initiates an eCall
IVS sent an INVITE request (see note 1)
The IMS network routes the emergency INVITE request
towards the appropriate PSAP
The INVITE request is sent to a gateway function for interfacing
to the CS domain
The gateway function sends a notification request to theappropriate PSAP
The emergency voice call establishment is completed with avoice path only
The IVS receives a 200 (OK) response to the INVITE(generated by the gateway) that lacks an ACK for the MSD
The IVS shall attempt to transfer the MSD to the PSAP via
in-band modem within the IMS eCall (see note 2)
PSAP immediately transmits SEND-MSD (START) message
without waiting for the valid Initiation Signal (see note 3)
If IVS had started to send an INITIATION message then IVS
stopped sending the INITIATION message on receipt of the
SEND-MSD message from the PSAP
PSAP verifies MSD is received
Verify the MSD is correctly decoded
MSD content at PSAP is identical to content transmitted by IVS
PSAP sends acknowledgement
Verify that the IVS has stopped transmitting the MSD
2-way speech can be exchanged

11
verify12verify13
check
14
verify15
verify16
verifyThe INVITE request shall contain:- The eCall type of emergency service indication (automatic, manual) but shall not include theinitial MSD in case the PS access is available, but the IVS does not detect the "IMS eCall
supported" indicator.
- The initial MSD and the eCall type of emergency service indicator (automatic, manual) if the
IVS detected the "IMS eCall supported" indicator.
The test steps 9 to 15 are copied from clause 7.1.1 of ETSI TS 103 428 [9]. Other tests from ETSITS 103 428 [9] could also be tested here.
Step 9 is only applicable if the PSAP is configured in PULL mode and should be skipped, if PSAP
is configured in PUSH mode.
MSC of MSD transfer to a non IMS PSAP is shown in Figure 12.

ETSI

35

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

Figure 12: MSD transfer to a non IMS PSAP
1)The NG IVS sends an instruction to establish a manual or automatic NG eCall.

2)

An initial emergency INVITE is sent to the PLMN. The INVITE may optionally contain the initial MSD andthe eCall type of emergency service indicator (automatic, manual).

3)

The PLMN network routes the emergency INVITE towards the appropriate PSAP. In this call flow, theappropriate PSAP is accessed over the gateway function and the CS domain after translating the eCall type of
emergency service indication into the corresponding PSAP.

4)The Gateway forwards the request to the legacy PSAP.

5)

The PSAP answers the eCall to the gateway.

6)

The gateway sends the 200 OK to the PLMN.

7)The PLMN forwards the 200 OK to the NG IVS.

8)The NG IVS sends ACK for the 200 OK INVITE.

9)

The gateway receives ACK for the 200 OK INVITE from the PLMN.

10) The IVS shall attempt to transfer the MSD to the PSAP via the eCall in-band modem.

ETSI

36

7.2.5

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

IMS eCall establishment with IMS emergency registration

Identifier:Objective:
Configuration:
References:

Applicability:
Pre-test
conditions:
Test Sequence:

Interoperability Test Description
TD_ADV_05
Verify that the IVS is able to initiate an IMS emergency session with IMS emergency
registration.
NG_eCall_CFG_01
Clause 7.3.6 of CEN TS 17184:2018 [4]Clause 7.2 of ETSI TS 123 167 [2]Clause 5.2.2.3 of ETSI TS 123 228 [3]IVS_ims_eCall AND PSAP_ims_eCall
Default see clause 6.7

Step
1
2

Type
stimulus
verifyDescription
IVS initiates an eCall
IVS sends a REGISTER request to initiate IMS emergency
registration (see note 1)
3
check"sos" is present within the Contact header field of REGISTER
request (see note 2)
4
verifyIVS receives a 200 OK REGISTER response5
verifyIVS sends an INVITE request
6
verifyPSAP verifies the MSD (in an INVITE request) is received
7
verifyIVS receives a 200 OK INVITE response with a positive
acknowledgment for the MSD
8verifyPSAP receives ACK request on 200 OK INVITE response
NOTE 1: MSC of IMS emergency registration procedure (step 2) is shown in Figure 13.
NOTE 2: The test step 3 is optional, if there is no possibility to check the REGISTER message.

ETSI

37

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

Figure 13: IMS emergency registration - IVS not registered
1)

NG IVS sends REGISTER to the PLMN (P-CSCF).

2)

P-CSCF sends REGISTER to the I-CSCF.

3)

I-CSCF sends Diameter UA-Request to the HSS.

4)

HSS sends Diameter UA-Answer to the I-CSCF.

5)

I-CSCF send REGISTER to the S-CSCF.

6)

S-CSCF sends Diameter SA-Request to the HSS.

7)

S-CSCF receives Diameter SA-Answer from the HSS.

8)

After successful confirmation S-CSCF sends 200 OK REGISTER to the I-CSCF.

9)

I-CSCF forwards 200 OK REGISTER to the P-CSCF.

10) NG IVS receives 200 OK from the PLMN (P-CSCF).

ETSI

38

7.2.6

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

IMS eCall establishment without IMS emergency registration

Applicability:

Interoperability Test Description
TD_ADV_06
Verify that the IVS is able to initiate an IMS emergency session without IMS emergency
registration and includes the "anonymous user" indication in the emergency session
establishment, if GIBA is not supported.
NG_eCall_CFG_01
Clause 7.3.6 of CEN TS 17184:2018 [4]Clause 7.4 and Annex K of ETSI TS 123 167 [2]
IVS_ims_eCall AND PSAP_ims_eCall AND NOT IVS_GIBA

Pre-test
conditions:Default see clause 6.7:•
P-CSCF should not reject "anonymous user"

Identifier:Objective:

Configuration:
References:

Test Sequence:

7.2.7

Step
1
2

Type
stimulus
verify3
4

verifycheck

56verifyverify7verifyDescription
IVS initiates an eCall
IVS sends a REGISTER request to initiate IMS emergency
registration
IVS receives any 4XX response to REGISTERIVS sends an INVITE request with "anonymous user" indication
to establish the eCall after unsuccessful registration
PSAP verifies the MSD (in an INVITE request) is received
IVS receives a 200 OK INVITE response with a positive
acknowledgment for the MSD
PSAP receives ACK request on 200 OK INVITE response

IMS eCall establishment without IMS emergency registration GIBA
supported

Applicability:

Interoperability Test Description
TD_ADV_07
Verify that the IVS is able to initiate an IMS emergency session without IMS emergency
registration and includes the "anonymous user" indication in the emergency session
establishment, if GIBA is supported.
NG_eCall_CFG_01
Clause 7.3.6 of CEN TS 17184:2018 [4]Clause 7.4 and clause K.3 step 9 of ETSI TS 123 167 [2]Clauses 5.1.1.2.6 (c, d), 5.1.1.4.6 (c, d) and 5.1.1.6.6 (c, d) of ETSI TS 124 229 [1]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_GIBA

Pre-test
conditions:Default see clause 6.7:•
P-CSCF should not reject "anonymous user"

Identifier:Objective:

Configuration:
References:

Test Sequence:

Step
1
2

Type
stimulus
verify3
4

verifyverify5
6

verifycheck

78verifyverify9verifyDescription
IVS initiates an eCall
IVS sends a REGISTER request to initiate IMS emergency
registration
IVS receives 420 response to REGISTERIVS sends a new REGISTER request with temporary publicuser identity derived from the IMSI and without Authorization
header field
IVS receives 200 OK REGISTER response
IVS sends an INVITE request with "anonymous user" indication
to establish the eCall after unsuccessful registration
PSAP verifies the MSD (in an INVITE request) is received
IVS receives a 200 OK INVITE response with a positive
acknowledgment for the MSD
PSAP receives ACK request on 200 OK INVITE response

ETSI

39

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

7.3

Advanced IVS test scenarios

7.3.1

Fallback to legacy eCall following busy during call setup

Identifier:Objective:

Configuration:
References:
Applicability:

Interoperability Test Description
TD_ADV_IVS_01
Verify that the IVS is able to fallback to legacy eCall after the IVS receives a 486 (BusyHere), 600 (Busy Everywhere) or 603 (Decline) response with a positive
acknowledgment for the MSD to the INVITE request.
NG_eCall_CFG_02
Clauses 7.1.2, 7.1.4, 7.3.6 and Table 1 of CEN TS 17184:2018 [4]Clause 5.1.6.11.2 (2nd numbered list/item 3) of ETSI TS 124 229 [1]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_legacy_eCall AND
PSAP_legacy_eCall AND IVS_speech AND PSAP_speechPre-test conditions: Default see clause 6.7:•
The PSAP should be configured to send 486 (Busy Here), 600 (Busy
Everywhere) or 603 (Decline) response with a positive acknowledgment for the
MSD to the INVITE request•
PSAP operator knows the content of the transmitted MSD
Test Sequence:

Step
1
2
3
4

Type
stimulus
verifyverifyverifyDescription
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded
IVS receives a 486 (Busy Here), 600 (Busy Everywhere) or 603(Decline) response with a positive acknowledgment for the
MSD to the INVITE request
5
verifyPSAP receives ACK on 486 (Busy Here), 600 (Busy
Everywhere) or 603 (Decline) response6
verifyIVS re-attempts the eCall due to domain selection rules
7
verifyThe IVS shall attempt to transfer the MSD to the PSAP via
in-band modem in CS domain (see note 1)
8
verifyPSAP answers call and immediately transmits SEND-MSD(START) message without waiting for the valid Initiation Signal(see note 2)
9verifyIf IVS had started to send an INITIATION message then IVS
stopped sending the INITIATION message on receipt of the
SEND-MSD message from the PSAP
10
verifyPSAP verifies MSD is received
11
verifyVerify the MSD is correctly decoded
12check
MSD content at PSAP is identical to content transmitted by IVS
13
verifyPSAP sends acknowledgement
14
verifyVerify that the IVS has stopped transmitting the MSD
15
verify2-way speech can be exchanged
NOTE 1: The test steps 8-14 are copied from clause 7.1.1 of ETSI TS 103 428 [9]. Other tests from ETSITS 103 428 [9] could also be tested here.
NOTE 2: Step 8 is only applicable if the PSAP is configured in PULL mode and should be skipped, if PSAP
is configured in PUSH mode.
NOTE 3: MSC of fallback scenario is shown in Figure 14.

ETSI

40

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

Figure 14: Fallback scenario
1)

The NG IVS sends an instruction 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)

MSD is received and due to busy NG eCall the NG PSAP returns a response (486 or 600 or 603) which
includes a positive or negative acknowledgement for the initial MSD.

5)The PLMN network sends the response (486 or 600 or 603) to the NG IVS.

6)The NG IVS sends ACK for the response.

7)

The NG PSAP receives ACK for the response from the PLMN.

8)

IVS attempts call over CS domain.

ETSI

41

7.3.2

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

Fallback to legacy eCall following unavailable response during call
setup

Identifier:Objective:
Configuration:
References:
Applicability:

Pre-test
conditions:

Test Sequence:

Interoperability Test Description
TD_ADV_IVS_02
Verify that the IVS is able to fallback to legacy eCall after the IVS receives a 480(Temporarily Unavailable) response to the INVITE request.
NG_eCall_CFG_02
Clauses 7.1.2, 7.3.6 and Table 1 of CEN TS 17184:2018 [4]Clauses 5.1.6.11.2 (2nd numbered list/item 4) and 5.2.10.3 of ETSI TS 124 229 [1]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_legacy_eCall AND
PSAP_legacy_eCall AND IVS_speech AND PSAP_speech
Default see clause 6.7:•
The PSAP should be configured to send 480 (Temporarily Unavailable)
response for the MSD to the INVITE request•
PSAP operator knows the content of the transmitted MSD
Step
1
2
3

Type
stimulus
verifyverifyDescription
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
IVS receives a 480 (Temporarily Unavailable) response for
the MSD to the INVITE request
4
verifyPSAP receives ACK on 480 (Temporary Unavailable)
response
5
verifyIVS re-attempts the eCall due to domain selection rules
6
verifyThe IVS shall attempt to transfer the MSD to the PSAP via
in-band modem in CS domain (see note 1)
7
verifyPSAP answers call and immediately transmits SEND-MSD(START) message without waiting for the valid Initiation
Signal (see note 2)
8
verifyIf IVS had started to send an INITIATION message then IVS
stopped sending the INITIATION message on receipt of the
SEND-MSD message from the PSAP
9
verifyPSAP verifies MSD is received
10
verifyVerify the MSD is correctly decoded11check
MSD content at PSAP is identical to content transmitted by
IVS
12
verifyPSAP sends acknowledgement
13
verifyVerify that the IVS has stopped transmitting the MSD
14
verify2-way speech can be exchanged
NOTE 1: The test steps 7 to 13 are copied from clause 7.1.1 of ETSI TS 103 428 [9]. Other tests from ETSITS 103 428 [9] could also be tested here.
NOTE 2: Step 7 is only applicable if the PSAP is configured in PULL mode and should be skipped, if PSAP
is configured in PUSH mode.

ETSI

42

7.3.3

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

Fallback to legacy eCall following no-answer during call setup

Identifier:Objective:
Configuration:
References:
Applicability:

Pre-test
conditions:

Test Sequence:

NOTE 1:NOTE 2:NOTE 3:
NOTE 4:

Interoperability Test Description
TD_ADV_IVS_03
Verify that the IVS is able to fallback to legacy eCall, if there is no-answer (e.g. 200 OK
INVITE response) from the PSAP except optional 100 (Trying) or 180 (Ringing).
NG_eCall_CFG_02
Clauses 7.1.2, 7.3.6 and Table 1 of CEN TS 17184:2018 [4]Clauses 5.1.6.11.2 (2nd numbered list/item 4) and 5.2.10.3 of ETSI TS 124 229 [1]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_legacy_eCall AND
PSAP_legacy_eCall AND IVS_speech AND PSAP_speech
Default see clause 6.7:•
The PSAP should be configured to send no-answer (e.g. 200 OK INVITE
response) except optional 100 (Trying) or 180 (Ringing)•
PSAP operator knows the content of the transmitted MSD
Step
1
2
3

Type
stimulus
verifyverify

4
5
6
7
8
9

verifyverifyverifyverifyverifyverify10

verify11

verify12
13
14

verifyverifycheck

Description
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
IVS receives no-answer (e.g. 200 OK INVITE response)
except optional 100 (Trying) or 180 (Ringing)
PSAP receives a CANCEL request (see note 1)
IVS receives 200 OK CANCEL response
IVS receives 487 (Request Terminated) response
PSAP receives ACK request
IVS re-attempts the eCall due to domain selection rules
The IVS shall attempt to transfer the MSD to the PSAP via
in-band modem in CS domain (see note 2)
PSAP answers call and immediately transmits SEND-MSD(START) message without waiting for the valid Initiation
Signal (see note 3)
If IVS had started to send an INITIATION message then IVS
stopped sending the INITIATION message on receipt of the
SEND-MSD message from the PSAP
PSAP verifies MSD is received
Verify the MSD is correctly decoded
MSD content at PSAP is identical to content transmitted by
IVS
PSAP sends acknowledgement
Verify that the IVS has stopped transmitting the MSD
2-way speech can be exchanged

15
verify16
verify17verifyThe test steps 4 to 7 are optional.
The test steps 10 to 16 are copied from clause 7.1.1 of ETSI TS 103 428 [9]. Other tests fromETSI TS 103 428 [9] could also be tested here.
Step 10 is only applicable if the PSAP is configured in PULL mode and should be skipped, if
PSAP is configured in PUSH mode.
MSC of no answer scenario is shown in Figure 15.

ETSI

43

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

Figure 15: No-answer scenario
1)

The NG IVS sends an instruction 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)NG PSAP may respond with 100 Trying to the PLMN.

5)PLMN may send 100 Trying to NG IVS.

6)

NG PSAP may send 180 Ringing to the PLMN.

7)PLMN may send 180 Ringing to the NG IVS.

8)

After no-answer is received NG IVS optionally sends CANCEL request to the PLMN.

9)PLMN resends CANCEL to the NG PSAP.

10) NG PSAP responds with 200 OK CANCEL to the PLMN.
11) PLMN resends 200 OK CANCEL to the NG IVS.
12) NG PSAP sends 487 Request Terminated response to the PLMN.
13) PLMN resends 487 Request Terminated response to the NG IVS.
14) NG IVS sends ACK request to the PLMN.

ETSI

44

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

15) The NG PSAP receives ACK for the response from the PLMN.
16) IVS attempts call over CS domain.

7.3.4

Dropped eCall after MSD has been acknowledged

Identifier:Objective:

Configuration:
References:
Applicability:
Pre-test
conditions:
Test Sequence:

Interoperability Test Description
TD_ADV_IVS_04
Verify that the IVS does not attempt to establish a new eCall, if the IMS eCall dropped
after the eCall has been successfully established and the MSD has been
acknowledged. Verify that the IVS answers a PSAP callback.
NG_eCall_CFG_01
Clauses 7.3.6, 7.10, 7.11 and 7.14.7 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_speech AND PSAP_speech
Default see clause 6.7

Step
1
2
3
4

Type
stimulus
verifyverifyverify56789verifyverifystimulus
verifystimulus

101112

verifyverifyverifyDescription
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded
IVS receives a 200 OK INVITE response with a positive
acknowledgment for the MSD
PSAP receives ACK request on 200 OK INVITE response
2-way speech can be exchanged
Simulate a call drop
IVS does not attempt to establish new eCall
PSAP initiates a callback (via INVITE request) using IVS
callback number, SIP identifier or IP address
IVS confirms the call with a 200 OK INVITE
PSAP sends ACK request on OK INVITE
2-way speech can be exchanged

ETSI

45

7.3.5

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

Dropped eCall before call has been established

Identifier:Objective:
Configuration:
References:
Applicability:

Pre-test
conditions:

Test Sequence:

Interoperability Test Description
TD_ADV_IVS_05
Verify that the IVS attempts a new eCall in CS domain, if the IMS eCall dropped before
the call has been established.
NG_eCall_CFG_02
Clauses 7.3.6 and 7.13.3 of CEN TS 17184:2018 [4]Clause 5.1.6.11.2 (2nd numbered list/item 4) of ETSI TS 124 229 [1]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_legacy_eCall AND
PSAP_legacy_eCall AND IVS_speech AND PSAP_speech
Default see clause 6.7:•
The PSAP should be configured to send no 200 OK INVITE response in step 3•
PSAP operator knows the content of the transmitted MSD
Step
1
2
3
4

Type
stimulus
verifystimulus
stimulus

Description
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP sends no 200 OK INVITE response
Simulate a call drop before the call has been established(before the IVS received a 200 OK INVITE response)5
verifyIVS re-attempt the eCall due to domain selection rules
6
verifyThe IVS shall attempt to transfer the MSD to the PSAP via
in-band modem in CS domain (see note 1)
7
verifyPSAP answers call and immediately transmits SEND-MSD(START) message without waiting for the valid Initiation Signal(see note 2)
8
verifyIf IVS had started to send an INITIATION message then IVS
stopped sending the INITIATION message on receipt of the
SEND-MSD message from the PSAP
9
verifyPSAP verifies MSD is received
10
verifyVerify the MSD is correctly decoded11check
MSD content at PSAP is identical to content transmitted by IVS
12
verifyPSAP sends acknowledgement
13
verifyVerify that the IVS has stopped transmitting the MSD
14
verify2-way speech can be exchanged
NOTE 1: The test steps 7 to 13 are copied from clause 7.1.1 of ETSI TS 103 428 [9]. Other tests from ETSITS 103 428 [9] could also be tested here.
NOTE 2: Step 7 is only applicable if the PSAP is configured in PULL mode and should be skipped, if PSAP isconfigured in PUSH mode.

ETSI

46

7.3.6

IVS configured for 'eCall only' service (restricted)

Identifier:Objective:
Configuration:
References:
Applicability:
Pre-test
conditions:

Test Sequence:

7.3.7

Interoperability Test Description
TD_ADV_IVS_06
Verify that the IVS does not attempt network registration until an eCall is initiated, if
configured for 'eCall only' service.
NG_eCall_CFG_01
Clauses 7.1.4 and 7.1.6 of CEN TS 17184:2018 [4]Clause 10.7 of ETSI TS 122 101 [11]IVS_ims_eCall AND IVS_eCall_only••••

IVS is configured for 'eCall only' service (restricted)
Ignition is OFF and NG IVS is in mobile network coverage
NG MNO and NG PSAP test points are available
NG IVS configured to support IMS communication profile

Step
1
2
3

Type
stimulus
verifystimulus

4
5
6

verifyverifyverifyDescription
IVS power on
IVS does not attempt to register on PLMN
IVS initiates an eCall (manual, automatic, test orreconfiguration)
IVS performs IMS emergency registration
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded

eCall is attempted when no networks are available (limited service
condition with forbidden PLMN on SIM/USIM)

Identifier:Objective:

Configuration:
References:
Applicability:
Pre-test
conditions:

Test Sequence:NOTE:

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

Interoperability Test Description
TD_ADV_IVS_07
Verify that an eCall is attempted when the IVS is in mobile network coverage but no
networks are available for registration (limited service condition due to forbidden PLMN
on SIM/USIM).
NG_eCall_CFG_03
Clauses 7.3.5 and 7.13.2 of CEN TS 17184:2018 [4]Clause 10.7 of ETSI TS 122 101 [11]IVS_ims_eCall AND PSAP_ims_eCall
•
•
•
•
Step
1
2

Ignition is OFF and NG IVS is in mobile network coverage
NG MNO and NG PSAP test points are available
NG IVS configured to support IMS communication profile
NG IVS contains USIM with forbidden PLMN (limited service condition)Typestimulus
verifyDescription
IVS power on
IVS does not attempt to register on PLMN due to limited service
condition3
stimulus IVS initiates a test eCall4
verifyIVS does not attempt to register on PLMN due to limited service
condition
5
stimulus IVS initiates an eCall (manual or automatic)
6
verifyIVS performs IMS emergency registration
7
verifyPSAP verifies the MSD (in an INVITE request) is received
8
verifyPSAP verifies the MSD is correctly decoded
To test the IVS behaviour in limited service condition it is also possible to use a mobile network
simulator, which is rejecting the IVS attempts to register to the mobile network.

ETSI

47

7.3.8

MSD transfer to PSAP supporting IMS eCall via PLMN without
VoIMS support

Identifier:Objective:
Configuration:
References:
Applicability:
Pre-test
conditions:Interoperability Test Description
TD_ADV_IVS_08
Verify that the IVS is able to transfer the MSD (in an INVITE request) to a PSAP
supporting IMS eCall via a mobile network without VoIMS support.
NG_eCall_CFG_06
Clause 7.3.6 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall
•
•
•
•
•

Test Sequence:

7.3.9

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

The network shall indicate support of IMS Emergency Services (EMS) andeCall Over IMS (ECL) and shall not indicate support of Voice over IMS over PS
sessions (VoIMS).
Ignition is OFF and NG IVS is in mobile network coverage, but VoIMS is notsupportedNG MNO and NG PSAP test points are available
NG IVS configured to support IMS communication profile
NG IVS contains USIM

Step
1
2

Type
stimulus
verify3
4
5
6

stimulus
verifyverifyverifyDescription
IVS power on
IVS registers to the PLMN but does not attempt IMS
registration due to missing VoIMS support indication
IVS initiates an eCall
IVS performs IMS emergency registration
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded

Termination of manually triggered eCall by vehicle occupant

Applicability:

Interoperability Test Description
TD_ADV_IVS_09
Verify that the vehicle occupant is able to abort a manually triggered eCall before
expiry of timer T1.
NG_eCall_CFG_01
Clause 7.3.8 and Table A.1 of CEN TS 17184:2018 [4]Clause 7.10.3 of CEN EN 16072:2015 [7]IVS_ims_eCall AND PSAP_ims_eCall

Pre-test
conditions:Default see clause 6.7:•
IVS timer T1 shall not be set to 0.

Identifier:Objective:
Configuration:
References:

Test Sequence:

Step
1
2
3
4

Type
stimulus
verifystimulus
verifyDescription
IVS initiates a manual eCall
IVS does not send an INVITE request
Terminate the eCall before expiry of timer T1
eCall is terminated successfully

ETSI

48

7.3.10Termination of automatically triggered eCall by vehicle occupant notallowed/not possible

Identifier:Objective:
Configuration:
References:
Applicability:
Pre-test
conditions:
Test Sequence:

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

Interoperability Test Description
TD_ADV_IVS_10
Verify that the vehicle occupant is not able to abort an automatically triggered eCall.
NG_eCall_CFG_01
Clause 7.3.8 of CEN TS 17184:2018 [4]Clause 7.10.3 of CEN EN 16072:2015 [7]IVS_ims_eCall AND PSAP_ims_eCall
Default see clause 6.7

Step
1
2
3

Type
stimulus
stimulus
verifyDescription
IVS initiates an automatic eCall
Try to terminate or abort the eCall
eCall established successfully and was not terminatedOngoing eCall shall not be disconnected if new trigger is received

Identifier:Objective:

Configuration:
References:
Applicability:
Pre-test
conditions:
Test Sequence:

Interoperability Test Description
TD_ADV_IVS_11
Verify that the IVS does not attempt to establish a new eCall on new trigger duringongoing eCall, if the eCall has been successfully established and the MSD has been
acknowledged before.
NG_eCall_CFG_01
Clauses 7.3.3 and 7.3.6 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_speech AND PSAP_speech
Default see clause 6.7

Step
1
2
3
4

Type
stimulus
verifyverifyverify5678

verifyverifystimulus
verify9verifyDescription
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded
IVS receives a 200 OK INVITE response with a positive
acknowledgment for the MSD
PSAP receives ACK request on 200 OK INVITE response
2-way speech can be exchanged
Stimulate manual trigger or stimulate sensor
IVS does not attempt to establish new eCall and does notdisconnect the ongoing eCall
2-way speech can be exchanged

ETSI

49

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

7.4

Advanced PSAP test scenarios

7.4.1

PSAP handling of more than 1 eCall simultaneously

Identifier:Objective:
Configuration:
References:
Applicability:
Pre-test
conditions:

Test Sequence:

NOTE:

7.4.2

Interoperability Test Description
TD_ADV_PSAP_01
Verify that a PSAP is able to receive and process more than 1 eCall simultaneously
from different IVS devices.
NG_eCall_CFG_04
Clause 7.1 of CEN EN 16072:2015 [7]Clause 7.8.1(first dashed line) of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall AND PSAP_simult_eCalls
Default see clause 6.7:•
PSAP has the ability to answer and process more than 1 eCall simultaneously•
All involved IVS with ignition are ON and in mobile network coverage•
PSAP Operator/s ready to receive eCalls•
PSAP ready to collect MSD information and timing
Step
1

Type
stimulus

Description
All IVSs initiate an eCall to the same PSAP (using their
allocated numbers or URNs)
2
verifyPSAP verifies the calls are established3
verifyPSAP verifies that MSDs are correctly received andacknowledged (see note)
4
stimulus
The eCalls are queued for PSAP operator or routed todifferent operators5
stimulus
The eCalls are answered either in-turn or simultaneously
6
verifyEstablishment of voice communication between the PSAP
operator(s) and the IVS(s), and that the correct MSD
information is displayed for each call7
stimulus
PSAP operator(s) clears down calls (via BYE request)
8
verifyAll IVSs cleared down the calls (confirmed with 200 OK BYE
response)
The PSAP shall be able to collect the information about the successful MSD reception andrelated timing for the evaluation. The PSAP shall be able to queue multiple calls until an operator
answers the call.

PSAP correct MSD additional data decoding

Identifier:Objective:
Configuration:
References:
Applicability:

Interoperability Test Description
TD_ADV_PSAP_02
Verify that the PSAP is able to decode optional additional MSD data.
NG_eCall_CFG_01
Clause 7.7.2 of CEN EN 16072:2015 [7]Clause 6.1.5 of CEN EN 15722:2015 [10]IVS_ims_eCall AND PSAP_ims_eCall AND IVS_add_MSD_data

Pre-test conditions: Default see clause 6.7:•
PSAP operator knows the content of the transmitted MSD, including theoptional additional MSD data
Test Sequence:

Step
1
2
3
4

Type
stimulus
verifyverifycheck

Description
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded
MSD content (including the optional additional MSD data) at
PSAP is identical to content transmitted by IVS

ETSI

50

7.4.3

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

Rerouting to another PSAP/emergency control centre

Configuration:
References:
Applicability:

Interoperability Test Description
TD_ADV_PSAP_03
Verify that the PSAP is able to reroute the eCall to another PSAP/emergency control
centre and voice connection is established with new PSAP.
NG_eCall_CFG_05
Clause 7.12 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall

Pre-test
conditions:Default see clause 6.7:•
Execute the complete test TD_BAS_04

Identifier:Objective:

Test Sequence:

7.4.4

Step
1
2

Type
verifystimulus

3
4

verifyverifyDescription
2-way speech can be exchanged between IVS and PSAP
PSAP operator reroutes eCall to another PSAP or emergency
control centre
eCall is forwarded to new PSAP
2-way speech can be exchanged between IVS and new
PSAP

PSAP operator user interface

Identifier:Objective:
Configuration:
References:
Applicability:
Pre-test
conditions:
Test Sequence:

Interoperability Test Description
TD_ADV_PSAP_04
Verify that the PSAP user interface displays caller identity, caller location and MSD.
NG_eCall_CFG_01
Clause 7.8.3 of CEN TS 17184:2018 [4]IVS_ims_eCall AND PSAP_ims_eCall
Default see clause 6.7

Step
1
2
3
4

Type
stimulus
verifyverifyverify5
6

verifycheck

Description
IVS initiates an eCall
PSAP verifies the MSD (in an INVITE request) is received
PSAP verifies the MSD is correctly decoded
IVS receives the 200 OK INVITE response with positive
acknowledgement for the MSD
PSAP receives ACK request on 200 OK INVITE response
PSAP user interface displays caller identity, caller locationand MSDETSI51ETSI TS 103 683 V1.1.1 (2020-02)

Annex A (informative):
Source code of MSC figures
A.1

Overview

MSC figures were produced with the open-source tool PlantUML [i.4], which allows to create UML diagrams from aplain text language. Source code of the figures are contained in archive ts_103683v010101p0.zip which accompanies
the present document.

ETSI

52

History
Document history
V1.1.1February 2020

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