ETSI TS 103 321 V1.1.1 (2015-04)

Mobile Standards Group (MSG); eCall HLAP Conformance Testing Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)

DTS/MSG-0015

General Information

• Status: Published
• Publication Date: 29-Apr-2015
• Technical Committee: MSG - Mobile Standards Group
• Current Stage: 13 - TB decision to make document historical
• Completion Date: 07-Sep-2017

Standards Content (Sample)

TECHNICAL SPECIFICATION
Mobile Standards Group (MSG);
eCall HLAP Conformance Testing;
Abstract Test Suite (ATS) and
Protocol Implementation eXtra Information for Testing (PIXIT)

�
2 ETSI TS 103 321 V1.1.1 (2015-04)

Reference
DTS/MSG-0015
Keywords
ATS, eCall, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
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.

© European Telecommunications Standards Institute 2015.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 103 321 V1.1.1 (2015-04)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Test Method . 8
4.1 Abstract test method (ATM) . 8
4.1.1 ATM used by the ATS in the present document . 8
4.1.2 ATM used by the ATSs for GSM and UMTS protocol conformance testing . 8
4.2 Test Configuration . 8
4.2.1 Configuration 1: IVS SUT . 8
4.2.1.1 General configuration. 8
4.2.1.2 TTCN configuration . 9
4.2.2 Configuration 2: PSAP SUT . 10
4.2.2.1 General configuration. 10
4.2.2.2 TTCN configuration . 10
4.3 Ports . 11
4.4 Messages . 11
4.4.1 In Messages . 11
4.4.2 Out Messages . 15
4.5 Primitives . 16
5 Test Purposes Coverage . 17
6 ATS conventions . 21
6.0 Introduction . 21
6.1 Testing conventions . 21
6.1.1 Testing states . 21
6.1.1.1 Initial state . 21
6.1.1.2 Final state . 22
6.1.2 ASN.1 definitions . 22
6.1.3 Specific TTCN-3 naming conventions . 22
6.1.4 Test Case (TC) identifier . 22
6.2 On line documentation . 22
6.3 Timer . 23
6.3.1 Timer Checking . 23
6.3.2 Timer Tolerances . 23
7 Support of optional features . 23
8 MSD Version . 23
Annex A (normative): TTCN-3 library modules . 24
A.0 Introduction . 24
A.1 TTCN-3 files and other related modules . 24
Annex B (normative): Partial PIXIT proforma for eCall HLAP . 25
B.0 Introduction . 25
B.1 Identification summary. 25
ETSI
4 ETSI TS 103 321 V1.1.1 (2015-04)
B.2 ATS summary . 25
B.3 Test laboratory . 25
B.4 Client identification . 26
B.5 SUT . 26
B.6 Protocol layer information. 26
B.6.1 Protocol identification . 26
B.6.2 IUT information . 27
Annex C (normative): PCTR Proforma for eCall HLAP . 29
C.0 Introduction . 29
C.1 Identification summary. 29
C.1.1 Protocol conformance test report . 29
C.1.2 IUT identification . 29
C.1.3 Testing environment . 29
C.1.4 Limits and reservation . 30
C.1.5 Comments. 30
C.2 IUT Conformance status . 30
C.3 Static conformance summary . 30
C.4 Dynamic conformance summary . 31
C.5 Static conformance review report . 31
C.6 Test campaign report . 32
C.7 Observations . 33
History . 34

ETSI
5 ETSI TS 103 321 V1.1.1 (2015-04)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://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.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Mobile Standards Group (MSG).
The present document is a single-part deliverable covering the "Abstract Test Suite (ATS) and Protocol Implementation
eXtra Information for Testing (PIXIT)".
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI
6 ETSI TS 103 321 V1.1.1 (2015-04)
1 Scope
The present document contains the Abstract Test Suite (ATS) for eCall (Higher Layer Application Protocols) HLAP for
the test purposes (TPs) as defined in CEN EN 16454 [i.1] in compliance with the relevant requirements and in
accordance with the relevant guidance given in ISO/IEC 9646-7 [i.11].
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [i.8] and ISO/IEC 9646-2 [i.9]) as well
as the ETSI rules for conformance testing (ETSI ETS 300 406 [i.12]) are used as a basis for the test methodology.
The TPs defined in CEN EN 16454 [i.1] are implemented by different ATSs. The eCall HLAP ATS is defined in the
present document. The relevant eCall tests related to GSM and UMTS technologies are identified in
ETSI TS 102 936-1 [i.4] and ETSI TS 102 936-2 [i.5].
The eCall HLAP ATS of this present document contains only tests which do not require the MNO test point and hence
the ATS implements only a subset of all available TPs. The detailed ATS coverage is defined in clause 5.
The support of optional features is defined by the Protocol Implementation Conformance Statement (PICS) in clause 7.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://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.
Not applicable.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] CEN EN 16454:2012: "Intelligent transport systems - eSafety - eCall end to end conformance
testing".
[i.2] CEN EN 15722:2012: "Intelligent transport systems - eSafety - eCall minimum set of data".
[i.3] CEN EN 16062:2012: "Intelligent transport systems - eSafety - eCall high level application
requirements (HLAP) using GSM/UMTS circuit switched networks".
[i.4] ETSI TS 102 936-1 V1.1.1: "eCall Network Access Device (NAD) conformance specification;
Part 1: Protocol test specification".
[i.5] ETSI TS 102 936-2 V1.1.1: "eCall Network Access Device (NAD) conformance specification;
Part 2: Test suites".
ETSI
7 ETSI TS 103 321 V1.1.1 (2015-04)
[i.6] ETSI TS 134 123-3: "Universal Mobile Telecommunications System (UMTS); User Equipment
(UE) conformance specification; Part 3: Abstract test suite (ATS) (3GPP TS 34.123-3
version 11.4.0 Release 11)".
[i.7] ETSI TS 151 010-3: " Digital cellular telecommunications system (Phase 2+); Mobile Station
(MS) conformance specification; Part 3: Layer3 (L3) Abstract Test Suite (ATS) (3GPP
TS 51.010-3 version 6.3.0 Release 6)".
[i.8] ISO/IEC 9646-1 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 1: General concepts".
[i.9] ISO/IEC 9646-2 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 2: Abstract Test Suite specification".
[i.10] ISO/IEC 9646-6 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 6: Protocol profile test specification".
[i.11] ISO/IEC 9646-7 (1995): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 7: Implementation Conformance
Statements".
[i.12] ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[i.13] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 1: TTCN-3 Core Language".
[i.14] ETSI ES 201 873-7: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 7: Using ASN.1 with TTCN-3".
[i.15] ETSI TS 122 011: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; Service accessibility (3GPP TS 22.011)".
[i.16] ETSI TS 123 122: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Non-Access-Stratum (NAS) functions related to Mobile
Station (MS) in idle mode (3GPP TS 23.122)".
[i.17] ETSI TS 126 267: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); eCall data transfer; In-band modem solution; General
description (3GPP TS 26.267)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in CEN EN 16454 [i.1],
ISO/IEC 9646-1 [i.11] and ISO/IEC 9646-7 [i.11] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in CEN EN 16454 [i.1] and the following apply:
AL  Application Layer
AL-ACK Application Layer Acknowledgement
ATM Abstract Test Method
ATS Abstract Test Suite
CTP Conformance Test Purpose
GIS Geographic Information System
GSM Global System for Mobile communications
HLAP Higher Layer Application Protocols
IUT Implementation Under Test
IVS In-Vehicle System
LL-ACK Link Layer Acknowledgement
ETSI
8 ETSI TS 103 321 V1.1.1 (2015-04)
MNO Mobile Network Operator
MSD Minimum Set of Data
MSISDN Mobile Subscriber ISDN number
PICS Protocol Implementation Conformance Statement
PIXIT Partial Protocol Implementation Extra Information for Testing
PSAP Public Safety Answering Point
SCS System Conformance Statement
SUT System Under Test
TC Test Case
TTCN Testing and Test Control Notation
UMTS Universal Mobile Telecommunications System
4 Test Method
4.1 Abstract test method (ATM)
4.1.1 ATM used by the ATS in the present document
The ATM used is the single layer distributed test method.
4.1.2 ATM used by the ATSs for GSM and UMTS protocol conformance
testing
The ATM used for the UMTS TCs is the single layer distributed test method and is identified in
ETSI TS 134 123-3 [i.6], clause 6.3.1.
The ATM used for the GSM TCs is the single layer distributed test method and is identified in ETSI TS 151 010-3 [i.7],
clause 6.
4.2 Test Configuration
4.2.1 Configuration 1: IVS SUT
4.2.1.1 General configuration
Figure 1 describes the general configuration for IVS SUT.
ETSI
9 ETSI TS 103 321 V1.1.1 (2015-04)

Figure 1
4.2.1.2 TTCN configuration
Figure 2 describes the TTCN configuration for IVS SUT

Figure 2
ETSI
10 ETSI TS 103 321 V1.1.1 (2015-04)
4.2.2 Configuration 2: PSAP SUT
4.2.2.1 General configuration
Figure 3 describes the general configuration for PSAP SUT.

Figure 3
4.2.2.2 TTCN configuration
Figure 4 describes the TTCN configuration for PSAP SUT.

Figure 4
ETSI
11 ETSI TS 103 321 V1.1.1 (2015-04)
4.3 Ports
The UIPort handles the interaction with the operator by providing a means to display information about required
operator actions as well as a way of capturing input from the operator.
Table 1: UIPort
UIPort
in ShowMessageBox, MessageBoxSelection
out ShowMessageBox, MessageBoxSelection

The LogMessagePort is intended for debugging information from the adaptation. Debug messages are processed by the
log component to separate them from the main body of the test case and also to provide an efficient means of filtering
them out.
Table 2: LogMessagePort
LogMessagePort
in LogMessage
out -
Table 3: ModemPort
ModemPort
in ModemEvent, LogMessage
out SetConfigCmd, InbandRequestMsdCmd, InbandSendAlAckCmd

Table 4: CallControlPort
CallControlPort
in CallEvent
out CallAcceptCmd, CallHangUpCmd, CallRejectBusyCmd,
CallCreateCmd, CallCancelCmd
Table 5: AdapterControlPort
AdapterControlPort
in AdapterEvent
out SetConfigCmd
4.4 Messages
4.4.1 In Messages
Table 6: ModemEvent
ModemEvent
Port: ModemPort
InbandMsdReceivedEvent, InbandLlAckSentEvent, InbandLlAckReceivedEvent,
InbandAlAckSentEvent, InbandAlAckReceivedEvent, InbandSendSignalReceivedEvent,
InbandNackSentEvent, InbandNackReceivedEvent,
CallVoiceConnectionEstablishedEvent, InbandStartSignalReceivedEvent,
TimerExpiredEvent.
ETSI
12 ETSI TS 103 321 V1.1.1 (2015-04)
Table 7: CallEvent
CallEvent
Port: CallControlPort
CallCanceledEvent, CallIncomingEvent, CallOutgoingEvent, CallEstablishedEvent,
CallRejectedEvent, CallHangUpEvent, CallAbortedEvent

Table 8: AdapterEvent
AdapterEvent
Port: AdapterControlPort
ConfigChangedEvent
Table 9: LogMessage
LogMessage
Port: LogMessagePort , ModemPort
instanceId integer ID of the instance emitting the log message
time charstring Timestamp of the log message
level e_debug, e_info Level of criticality of the log message
text charstring Text of the log message

Table 10: InbandMsdReceivedEvent
Port: ModemPort IUT: PSAP
Indicates the successful reception of an MSD
instanceId integer ID of the instance that generated the event
time charstring Event timestamp
level ECallMessageUnion Received raw message

Table 11: InbandLlAckSentEvent
Port: ModemPort IUT: PSAP
Generated when sending a LL-ACK indicating successful reception of an MSD to the IVS
instanceId integer ID of the instance that generated the event
time charstring Event timestamp
count AckNumberType count
Table 12: InbandLlAckReceivedEvent
Port: ModemPort IUT: IVS
Generated when sending a LL-ACK indicating successful reception of an MSD to the IVS
instanceId integer ID of the instance that generated the event
time charstring Event timestamp
count AckNumberType count
reliable boolean reliable
Table 13: InbandAlAckSentEvent
Port: ModemPort IUT: PSAP
Generated when sending an AL-ACK indicating the format of the MSD is ok
instanceId integer ID of the instance that generated the event
time charstring Event timestamp
count AckNumberType count
val AckValueType AL ACK value sent

ETSI
13 ETSI TS 103 321 V1.1.1 (2015-04)
Table 14: InbandAlAckReceivedEvent
Port: ModemPort IUT: IVS
Generated when receiving an AL-ACK indicating the format of the MSD is ok
instanceId integer ID of the instance that generated the event
time charstring Event timestamp
count AckNumberType count
val AckValueType AL ACK value sent
reliable boolean reliable
Table 15: InbandSendSignalReceivedEvent
Port: ModemPort IUT: PSAP
Indicates the reception of a SEND signal
instanceId integer ID of the instance that generated the event
time charstring Event timestamp

Table 16: InbandNackSentEvent
Port: ModemPort IUT: PSAP
Generated when sending a NACK indicating that the MSD was not yet received
instanceId integer ID of the instance that generated the event
time charstring Event timestamp
count PositiveInteger count
Table 17: CallVoiceConnectionEstablishedEvent
Port: ModemPort IUT: PSAP, IVS
Generated whenever bidirectional voice communication is possible
instanceId integer ID of the instance that generated the event
time charstring Event timestamp

Table 18: InbandStartSignalReceivedEvent
Port: ModemPort IUT: IVS
Indicates the reception of a START signal
instanceId integer ID of the instance that generated the event
time charstring Event timestamp
count PositiveInteger count
reliable boolean reliable
Table 19: TimerExpiredEvent
Port: ModemPort IUT: PSAP, IVS
Generated when a timer expires
instanceId integer ID of the instance that generated the event
time charstring Event timestamp
name charstring The name of the timer
val float The value of the timer in seconds

Table 20: CallCanceledEvent
Port: CallControlPort IUT: PSAP, IVS
Generated when an incoming call is cancelled by the remote end before it was accepted or
rejected
instanceId integer ID of the instance that generated the event
time charstring Event timestamp

ETSI
14 ETSI TS 103 321 V1.1.1 (2015-04)
Table 21: CallIncomingEvent
Port: CallControlPort IUT: PSAP, IVS
Informs about an incoming call
instanceId integer ID of the instance that generated the event
time charstring Event timestamp
from_ TelephoneNumber Caller ID
to_ TelephoneNumber Calling ID

Table 22: CallOutgoingEvent
Port: CallControlPort IUT: PSAP, IVS
Informs about an outgoing call request
instanceId integer ID of the instance that generated the event
time charstring Event timestamp
from_ TelephoneNumber Caller ID
to_ TelephoneNumber Calling ID

Table 23: CallEstablishedEvent
Port: CallControlPort IUT: PSAP, IVS
Informs about an outgoing call request
instanceId integer ID of the instance that generated the event
time charstring Event timestamp

Table 24: CallRejectedEvent
Port: CallControlPort IUT: PSAP, IVS
Generated when a call was rejected
instanceId integer ID of the instance that generated the event
time charstring Event timestamp

Table 25: CallHangUpEvent
Port: CallControlPort IUT: PSAP, IVS
Informs about the end of a call
instanceId integer ID of the instance that generated the event
time charstring Event timestamp

Table 26: CallAbortedEvent
Port: CallControlPort IUT: PSAP, IVS
Generated when a call ends and neither call_hang_up nor call_cancelled nor call_rejected are
applicable
instanceId integer ID of the instance that generated the event
time charstring Event timestamp
reason charstring A hint to why the call was aborted

Table 27: ConfigChangedEvent
Port: AdapterControlPort IUT: PSAP, IVS
Generated whenever one or more configuration options changed
instanceId integer ID of the instance that generated the event
time charstring Event timestamp
parameters ModemConfiguration Configuration parameters

ETSI
15 ETSI TS 103 321 V1.1.1 (2015-04)
Table 28: ShowMessageBox
Port: UIPort IUT: PSAP, IVS
Message box request
title charstring title
msg charstring message
buttonLabels ButtonLabels button labels
defaultSelection integer default button selection
msgTimeout Integer - Optional the message box is hidden after msgTimeout
seconds if no button is selected by the user

Table 29: MessageBoxSelection
Port: UIPort IUT: PSAP, IVS
Selected button of the message box
integer
4.4.2 Out Messages
Table 30: SetConfigCmd
Port: ModemPort , AdapterControlPort IUT: PSAP, IVS
Change configuration options
instanceId integer Target instance process
parameters ModemConfiguration Configuration parameters

Table 31: CallAcceptCmd
Port: CallControlPort IUT: PSAP, IVS
Accept an incoming call
instanceId integer Target instance process

Table 32: CallHangUpCmd
Port: CallControlPort IUT: PSAP, IVS
End a call in progress. Always ends both the external call and the internal call
instanceId integer Target instance process

Table 33: CallRejectBusyCmd
Port: CallControlPort IUT: PSAP, IVS
Reject an incoming call with the busy signal
instanceId integer Target instance process

Table 34: CallCreateCmd
Port: CallControlPort IUT: PSAP, IVS
Create an outgoing external call request
instanceId integer Target instance process
to_ charstring Call destination

Table 35: CallCancelCmd
Port: CallControlPort IUT: PSAP, IVS
Cancel an outgoing external call request
instanceId integer Target instance process

ETSI
16 ETSI TS 103 321 V1.1.1 (2015-04)
Table 36: InbandRequestMsdCmd
Port: ModemPort IUT: PSAP
Request retransmission of an MSD. Only works if there is no MSD transmission already in
progress
instanceId integer Target instance process

Table 37: InbandSendAlAckCmd
Port: ModemPort IUT: PSAP
Send an application layer acknowledgment
instanceId integer Target instance process
val AckValueType Acknowledgement value

Table 38: ShowMessageBox
Port: UIPort IUT: PSAP, IVS
Message box request
title charstring title
msg charstring message
buttonLabels ButtonLabels button labels
defaultSelection integer default button selection
msgTimeout Integer - Optional the message box is hidden after msgTimeout
seconds if no button is selected by the user

Table 39: MessageBoxSelection
Port: UIPort IUT: PSAP, IVS
Selected button of the message box
integer
4.5 Primitives
Table 40: f_userAction primitives
f_userAction
IVS SUT
"With the vehicle ignition set to OFF, attempt to trigger an eCall automatically in accordance with the manufacturer's
instructions"
"Apply new trigger (manual or automatic) while eCall is in progress"
"Generate invalid trigger (below relevant threshold) for """ & PX_SUPPORTED_CRASH_TYPES[v_crashType] & """
crash-type"
"Apply new trigger (manual or automatic) while eCall is in progress"
"Attempt to disconnect eCall using vehicle HMI"
"Switch OFF ignition"
"Establish non eCall communication"
"Trigger test eCall (to the provisioned non-emergency number)"
PSAP SUT
"Request MSD data using PSAP application"
"Clear down PSAP"
"Clear down eCall"
"Initiate call back procedure"

ETSI
17 ETSI TS 103 321 V1.1.1 (2015-04)
Table 41: f_userVerify primitives
f_userVerify
IVS SUT
"Was visual and/or audible information of eCall activation provided?"
"Did the IVS initiate an automatic eCall?"
"Did the IVS attempt to establish a ""hands-free"" voice connection?"
"Was an audio/visual alert displayed to the occupants?"
"Did the IVS send data?"
"Did the IVS successfully clear-down?"
"Was the eCall in progress disconnected?"
"Was an HMI alert provided to occupants that an eCall is being started?"
"Are all components required for an eCall available and not influenced by the previously running communication?"
"Is voice communication possible?"
"Was audio muted during MSD transmission?"
"Was the call connected to the PSAP test point?"
"Was voice 2-way voice communication possible after receiving positive AL_ACK or within 5s of LL_ACK?"
"Is speech conversation in progress between the IVS and PSAP?"
"Was IVS audio muted during MSD transfer?"
"Was 2-way voice communication possible after T5 has expired?"
"Was 2-way voice communication possible after T6 has expired?"
"Was 2-way voice communication possible after T7 has expired?"
"Is the IVS cleared down?"
"Is a record of the received application layer acknowledgment (AL-ACK) and time stamp, sent from the PSAP test
point, stored in the IVS?"
"Was the call-back automatically answered by the IVS?"
"Was visual and/or audible information of eCall activation provided by the IVS?"
"Is 2-way speech possible?"
"Was visual and/or audible information of eCall activation provided by the IVS?"
"Was the IVS microphone muted during MSD transmission?"
"Was the entertainment system muted for the duration of the call?"
PSAP SUT
"Was the call correctly queued and routed to a free operator?"
"Is the TS12 and MSD data correctly displayed in the PSAP operator interface?"
"Was the call treated as a normal TS12 call and routed to operator?"
"Was audio-link established with vehicle occupants?"
"Was the call routed to the operator and audio link is established with vehicle occupants?"
"Is the car description information correctly displayed in the PSAP operator's interface?"
"Was the MSD correctly displayed on the operator's interface and audio link with vehicle was re-established?"
"Is the eCall routed to the most appropriate PSAP and routed to an operator?"
"Is the operator line free?"
"Is voice communication between PSAP operator and vehicle established?"
"Was two way speech possible after" & fx_float2str(PX_T4_TIMER) & " seconds of call establishment?"
"Was the eCall (voice and MSD) correctly routed to an available operator?"

5 Test Purposes Coverage
This clause lists all test purposes of CEN and indicates which are implemented and which are not implemented. A
reason is given for at least those test purposes which are not implemented.
ETSI
18 ETSI TS 103 321 V1.1.1 (2015-04)
Table 42: Test purposes of CEN
Test purpose Implemented Reason
Yes/No
CTP 1.1.0.1 No Out of scope (MNO test point required) of the present document.
Covered by ETSI TS 102 936-1 [i.4] and ETSI TS 102 936-2 [i.5] -
PE eCall IVS
CTP 1.1.0.2 No Out of scope (MNO test point required) - PE eCall
CTP 1.1.0.3 Yes CTP step indicates "PSAP test point or MNO test point". It is
possible to achieve the step by using the PSAP test point - PE eCall
IVS
CTP 1.1.1.1 No Out of scope (no protocol test) - PE eCall IVS
CTP 1.1.1.2 No Out of scope (MNO test point required) - PE eCall only IVS
CTP 1.1.1.3 No Out of scope (No test required) Covered by ETSI TS 122 011 [i.15]
and ETSI TS 123 122 [i.16] - PE eCall only IVS
CTP 1.1.2.1 No Out of scope (MNO test point required) - PE eCall IVS
CTP 1.1.2.2 Yes PE eCall IVS
CTP 1.1.2.3 Yes IVS
CTP 1.1.2.4 Yes IVS
CTP 1.1.2.5 Yes IVS
CTP 1.1.3.1 No Out of scope (MNO test point required). - PE eCall IVS
CTP 1.1.3.2 Yes PE eCall IVS
CTP 1.1.4.1 No PE eCall IVS
CTP 1.1.5.1 No Out of scope (MNO test point required). - PE eCall IVS
CTP 1.1.5.2 Yes PE eCall IVS
CTP 1.1.5.3 Yes PE eCall IVS
CTP 1.1.5.4 Yes PE eCall IVS
CTP 1.1.5.5 Yes PE eCall IVS
CTP 1.1.5.6 Yes CTP step indicates "PSAP test point or MNO test point". It is
possible to achieve the step by using the PSAP test point. - PE
eCall IVS
CTP 1.1.5.7 No Out of scope No test required - PE eCall IVS
CTP 1.1.6.1 Yes PE eCall IVS
CTP 1.1.7.1 No Out of scope (MNO test point required). TS12 automatic - PE eCall
IVS
CTP 1.1.8.1 No Out of scope (MNO test point required). TS12 manual - PE eCall
IVS
CTP 1.1.9.1 Yes CTP step indicates "PSAP test point or MNO test point". It is
possible to achieve the step by using the PSAP test point. - PE
eCall IVS
CTP 1.1.10.1 No Test purposes does not define parameters for limited service
condition. Out of scope (MNO test point required). - PE eCall IVS
CTP 1.1.10.2 Yes PE eCall IVS
CTP 1.1.10.3 Yes Timer 2 s - PE eCall IVS
CTP 1.1.10.4 No Out of scope (MNO test point required) - PE eCall only IVS
CTP 1.1.11.1 Yes PE eCall IVS
CTP 1.1.12.1 Yes PE eCall IVS
CTP 1.1.13.1 Yes PE eCall IVS
CTP 1.1.14.1 Yes T6 - T4 and T8 for pass condition - PE eCall IVS
CTP 1.1.14.2 Yes PE eCall IVS
CTP 1.1.15.1 Yes Timer 5 s. - PE eCall IVS
CTP 1.1.15.2 Yes T6, T7 and T8 used - PE eCall IVS
CTP 1.1.15.3 Yes T5 used - PE eCall IVS
CTP 1.1.15.4 Yes T6 used - PE eCall IVS
CTP 1.1.15.5 Yes T7 and T8 used - PE eCall IVS
CTP 1.1.16.1 Yes PE eCall IVS
CTP 1.1.16.2 Yes T2 used - PE eCall IVS
CTP 1.1.16.3 Yes PE eCall IVS
CTP 1.1.17.1 Yes PE eCall IVS
CTP 1.1.17.2 Yes PE eCall IVS
CTP 1.1.17.3 Yes T6 and T8 used - PE eCall IVS
CTP 1.1.17.4 Yes Note the CLI MSISDN - PE eCall IVS
CTP 1.1.17.5 No Out of scope (MNO test point required) Note the CLI MSISDN - PE
eCall only IVS
ETSI
19 ETSI TS 103 321 V1.1.1 (2015-04)
Test purpose Implemented Reason
Yes/No
CTP 1.2.0.1 No Out of scope -TPS-IVS
CTP 1.2.0.2 No Out of scope -TPS-IVS
CTP 1.2.1.1 No Out of scope -TPS-IVS
CTP 1.2.1.2 No Out of scope -TPS-IVS
CTP 1.2.2.1 No Out of scope -TPS-IVS
CTP 1.2.2.2 No Out of scope -TPS-IVS
CTP 1.2.2.3 No Out of scope -TPS-IVS
CTP 1.2.2.4 No Out of scope -TPS-IVS
CTP 1.2.2.5 No Out of scope -TPS-IVS
CTP 1.2.3.1 No Out of scope -TPS-IVS
CTP 1.2.4.1 No Out of scope -TPS-IVS
CTP 1.2.5.1 No Out of scope -TPS-IVS
CTP 1.2.5.2 No Out of scope -TPS-IVS
CTP 1.2.5.3 No Out of scope -TPS-IVS
CTP 1.2.5.4 No Out of scope -TPS-IVS
CTP 1.2.5.5 No Out of scope -TPS-IVS
CTP 1.2.6.1 No Out of scope -TPS-IVS
CTP 1.2.6.2 No Out of scope -TPS-IVS
CTP 1.2.6.3 No Out of scope -TPS-IVS
CTP 1.2.7.1 No Out of scope -TPS-IVS
CTP 1.2.8.1 No Out of scope -TPS-IVS
CTP 1.2.9.1 No Out of scope (MNO test point required) -TPS-IVS
CTP 1.2.9.2 No Out of scope -TPS-IVS
CTP 1.2.9.3 No Out of scope -TPS-IVS
CTP 2.0.1 No Out of scope (Test of PLMN network only) - MNO
CTP 2.0.2 No Out of scope (Test of PLMN network only) - MNO
CTP 2.0.3 No Out of scope (Test of PLMN network only) - MNO
CTP 2.0.4 No Out of scope (Test of PLMN network only) - MNO
CTP 2.1.1 No Out of scope (Test of PLMN network only) - MNO
CTP 2.1.2 No Out of scope (Test of PLMN network only) - MNO
CTP 2.2.1.1 No Out of scope (Test of PLMN network only) - MNO
CTP 2.2.1.2 No Out of scope (Test of PLMN network only) - MNO
CTP 2.2.1.3 No Out of scope (Test of PLMN network only) - MNO
CTP 2.2.2.1 No Out of scope (Test of PLMN network only) - MNO
CTP 2.2.3.1 No Out of scope (Test of PLMN network only) - MNO
CTP 2.2.3.2 No Out of scope (Test of PLMN network only) - MNO
CTP 2.2.3.3 No Out of scope (Test of PLMN network only) - MNO
CTP 2.3.1 No Out of scope No test required (Test of PLMN network only) - MNO
CTP 2.4.1 No Out of scope (Test of PLMN network only) - MNO
CTP 2.5.1 No Out of scope (Test of PLMN network only) - MNO
CTP 2.6.1 No Out of scope No test required- MNO
CTP 2.7.1 No Out of scope No test required- MNO
CTP 2.11.1 No Out of scope (Test of PLMN network only) - MNO
CTP 2.11.2 No Out of scope Capability included within CTP 2.11.1. - MNO
CTP 3.1.0.1 No Out of scope (MNO test point required) - PSAP PE eCall
CTP 3.1.0.2 No Out of scope (Geographic Information System (GIS) needed) -
PSAP PE eCall
CTP 3.1.1.1 No Out of scope (MNO test point required) - PSAP PE eCall
CTP 3.1.1.2 No Out of scope (MNO test point required) - PSAP PE eCall
CTP 3.1.2 No Out of scope (MNO test point required) - PSAP PE eCall
CTP 3.1.3.1 Yes MNO test point used in CTP step "eCall routed to the most
appropriate PSAP". For testing, the SUT shall be considered the
most appropriate PSAP, and hence the MNO test point is not
required.
CTP 3.1.3.2 Yes Timer 2 s - MNO test point used in CTP step "eCall routed to the
most appropriate PSAP". For testing, the SUT shall be considered
the most appropriate PSAP, and hence the MNO test point is not
required.
CTP 3.1.3.3 Yes Timer 2 s T4 - MNO test point used in CTP step "eCall routed to the
most appropriate PSAP". For testing, the SUT shall be considered
the most appropriate PSAP, and hence the MNO test point is not
required.
CTP 3.1.4 No Out of scope (MNO test point required)
ETSI
20 ETSI TS 103 321 V1.1.1 (2015-04)
Test purpose Implemented Reason
Yes/No
CTP 3.1.5.1 Yes Timer 2 s T4 - MNO test point used in CTP step "eCall routed to the
most appropriate PSAP". For testing, the SUT shall be considered
the most appropriate PSAP, and hence the MNO test point is not
required.
CTP 3.1.5.2 Yes Timer 2 s T4 - MNO test point used in CTP step "eCall routed to the
most appropriate PSAP". For testing, the SUT shall be considered
the most appropriate PSAP, and hence the MNO test point is not
required.
CTP 3.1.6 Yes Timer 2 s T4 - MNO test point used in CTP step "eCall routed to the
most appropriate PSAP". For testing, the SUT shall be considered
the most appropriate PSAP, and hence the MNO test point is not
required.
CTP 3.1.7.1 Yes T5 - T6 - T7 - Verify MSD - PSAP PE eCall
CTP 3.1.7.2 Yes Verify MSD - PSAP PE eCall
CTP 3.1.7.3 Yes Verify MSD -PSAP PE eCall
CTP 3.1.7.4 No T4,T& and T8 used - Out of scope Corrupted MSD - PSAP PE eCall
CTP 3.1.7.5 No Timer 5s - Out of scope MSD transfer fail - PSAP PE eCall
CTP 3.1.8 No Out of scope - Covered by CTP 3.1.7 - - PSAP PE eCall
CTP 3.1.9 Yes MNO test point used in CTP step "eCall routed to the most
appropriate PSAP". For testing, the SUT shall be considered the
most appropriate PSAP, and hence the MNO test point is not
required.
CTP 3.1.10 Yes MNO test point used in CTP step "eCall routed to the most
appropriate PSAP". For testing, the SUT shall be considered the
most appropriate PSAP, and hence the MNO test point is not
required.
CTP 3.1.11 Yes MNO test point used in CTP step "eCall routed to the most
appropriate PSAP". For testing, the SUT shall be considered the
most appropriate PSAP, and hence the MNO test point is not
required.
CTP 3.1.12 Yes MNO test point used in CTP step "eCall routed to the most
appropriate PSAP". For testing, the SUT shall be considered the
most appropriate PSAP, and hence the MNO test point is not
r
...