ETSI TS 103 650-1 V1.2.1 (2022-08)

EMTEL; Testing - Conformance test specifications for core elements for network independent access to emergency services (NG112); Part 1: Protocol Implementation Conformance Statement (PICS), Test Suite Structure and Test Purposes (TSS & TP)

RTS/EMTEL-00060-1

General Information

• Status: Not Published
• Technical Committee: EMTEL - Emergency Communications
• Current Stage: 12 - Completion
• Due Date: 30-Jul-2022
• Completion Date: 01-Aug-2022

Standards Content (Sample)

TECHNICAL SPECIFICATION
EMTEL;
Testing - Conformance test specifications for
core elements for network independent access to
emergency services (NG112);
Part 1: Protocol Implementation
Conformance Statement (PICS),
Test Suite Structure and Test Purposes (TSS & TP)

2 ETSI TS 103 650-1 V1.2.1 (2022-08)

Reference
RTS/EMTEL-00060-1
Keywords
conformance, emergency, emergency services,
interoperability, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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

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

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

© ETSI 2022.
All rights reserved.
ETSI
3 ETSI TS 103 650-1 V1.2.1 (2022-08)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Protocol Implementation Conformance Statement (PICS) . 8
4.1 Introduction . 8
4.2 Entities . 8
4.3 LIS features . 9
4.4 ESRP features . 9
4.5 ECRF features . 10
4.6 PSAP features . 10
4.7 BCF features . 10
4.8 Mnemonics for PICS reference . 11
5 Test Configurations . 12
5.1 LIS Test Configurations . 12
5.1.1 CFG_LIS_01. 12
5.2 ESRP Test Configurations . 12
5.2.1 CFG_ESRP_01 . 12
5.3 ECRF Test Configurations . 12
5.3.1 CFG_ ECRF_01 . 12
5.4 PSAP Test Configurations . 13
5.4.1 CFG_PSAP_01 . 13
5.5 BCF Test Configurations . 13
5.5.1 CFG_BCF_01 . 13
6 Test Suite Structure (TSS) . 13
6.1 Structure for NG112 tests . 13
6.2 Test groups . 13
6.2.1 Root . 13
6.2.2 Test group . 13
6.2.3 Test sub-group . 13
6.2.4 Categories . 13
7 Test Purposes (TP) . 14
7.1 Introduction . 14
7.1.1 TP definition conventions . 14
7.1.2 TP Identifier naming conventions . 15
7.1.3 Rules for the behaviour description . 15
7.1.4 Pre-defined initial conditions . 16
7.1.4.1 ESRP initial conditions . 16
7.1.4.2 SIP initial conditions . 18
7.1.5 Sources of TP definitions . 19
7.1.6 Mnemonics for PICS reference . 19
7.2 Test purposes . 19
7.2.1 LIS . 19
7.2.1.1 HELD . 19
7.2.1.2 Error . 23
ETSI
4 ETSI TS 103 650-1 V1.2.1 (2022-08)
7.2.1.3 Subscription/Notifications . 24
7.2.1.4 Advanced Mobile Location . 28
7.2.1.5 Security . 30
7.2.2 ESRP . 31
7.2.2.1 FindService . 31
7.2.2.2 Fixed Target . 34
7.2.2.3 SIP REGISTER Target . 35
7.2.2.4 'Dequeue Registration Target . 35
7.2.2.5 QueueState . 36
7.2.2.6 Subscriptions/Notifications . 39
7.2.2.7 Security . 42
7.2.2.8 Headers . 43
7.2.3 ECRF . 44
7.2.3.1 LoST . 44
7.2.3.2 Errors . 53
7.2.3.3 Subscriptions/Notifications . 54
7.2.3.4 Security . 56
7.2.4 PSAP . 57
7.2.4.1 Invite . 57
7.2.4.2 Ack . 61
7.2.4.3 Bye . 62
7.2.4.4 Message . 63
7.2.4.5 Options . 64
7.2.4.6 Cancel . 64
7.2.4.7 Info . 65
7.2.4.8 Dequeue registration/deregistration . 65
7.2.4.9 HELD . 67
7.2.4.10 LoST . 68
7.2.4.11 Security . 69
7.2.5 BCF . 69
7.2.5.1 Invite . 69
7.2.5.2 Message . 72
7.2.5.3 Security . 74
History . 75

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

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This Technical Specification (TS) has been produced by ETSI Special Committee Emergency Communications
(EMTEL).
The present document is part 1 of a multi-part deliverable covering Conformance test specifications for core elements
for network independent access to emergency services (NG112), as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS), Test Suite Structure and Test Purposes
(TSS & TP)";
Part 2: "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 650-1 V1.2.1 (2022-08)
1 Scope
The present document provides the Protocol Implementation Conformance Statement (PICS) and Test Suite Structure
and Test Purposes (TSS & TP) for core elements for network independent access to emergency services (NG112) as
defined in standards listed in clause 2.1 of the present document.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 103 479 (V1.2.1): "Emergency Communications (EMTEL); Core elements for network
independent access to emergency services".
[2] Void.
[3] IETF RFC 5985: "HTTP-Enabled Location Delivery (HELD)".
NOTE: Available at https://tools.ietf.org/html/IETF RFC 5985.
[4] IETF RFC 6753: "A Location Dereference Protocol Using HTTP-Enabled Location Delivery
(HELD)".
NOTE: Available at https://tools.ietf.org/html/rfc6753.
[5] IETF RFC 5222: "LoST: A Location-to-Service Translation Protocol".
NOTE: Available at https://tools.ietf.org/html/IETF RFC 5222.
[6] IETF RFC 3261: "SIP: Session Initiation Protocol".
NOTE: Available at https://tools.ietf.org/html/IETF RFC 3261.
[7] IETF RFC 5031: "A Uniform Resource Name (URN) for Emergency and Other Well-Known
Services".
NOTE: Available at https://tools.ietf.org/html/rfc5031.
[8] IETF RFC 5491: "GEOPRIV Presence Information Data Format Location Object (PIDF-LO)
Usage Clarification, Considerations, and Recommendations".
NOTE: Available at https://tools.ietf.org/html/rfc5491.
[9] Void.
[10] IETF RFC 6442: "Location Conveyance for the Session Initiation Protocol".
NOTE: Available at https://datatracker.ietf.org/doc/html/rfc6442.
[11] ETSI TS 103 698 (V1.1.1): "Emergency Communications (EMTEL); Lightweight Messaging
Protocol for Emergency Service Accessibility (LMPE)".
ETSI
7 ETSI TS 103 650-1 V1.2.1 (2022-08)
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ISO/IEC 9646-1 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 1: General concepts".
[i.2] ISO/IEC 9646-7 (1995): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 7: Implementation Conformance
Statements".
[i.3] EENA: "Next Generation 112 Long Term Definition", Version 1.1, March 2013.
NOTE: Available at https://eena.org/document/ng112-long-term-definition-standard-for-emergency-services/.
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ISO/IEC 9646-1 [i.1] and ISO/IEC 9646-7 [i.2] apply.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACK Acknowledge
AML Advanced Mobile Location
ATS Abstract Test Suite
BCF Border Control Function
BI Invalid Behavior
BV Valid Behaviour
ECRF Emergency Call. Routing Function
EENA European Emergency Number Association
EES European Emergency Services
ESRP Emergency Service Routing Proxy
HELD HTTP Enabled Location Discovery
HTTP Hyper-text Transfer Protocol
ICS Implementation Conformance Statement
ID Identity
IM Instant Messaging
ISO International Organization for Standardization
IUT Implementation Under Test
LI Location Information
LIS Location Information Server
LO Location Object
LoST Location to Service Translation
ETSI
8 ETSI TS 103 650-1 V1.2.1 (2022-08)
LTD Long Term Definition
PICS Protocol Implementation Conformance Statement
PIDF Presence Information Data Format
PIXIT Protocol Implementation eXtra Information for Testing
PSAP Public Safety Answer Point
SDP Session Description Protocol
SIP Session Initiation Protocol
SMS Short Message Service
TCP Transmission Control Protocol
TLS Transport Layer Security
TP Test Purposes
TS Test Suite
TSS Test Suite Structure
UDP User Datagram Protocol
URI Uniform Resource Identifier
URN Universal Resource Name
4 Protocol Implementation Conformance Statement
(PICS)
4.1 Introduction
The purpose of a PICS is to identify those standardized functions which an IUT shall support, those which are optional
and those which are conditional on the presence of other functions. It helps to identify which functions an IUT will
support when performing conformance testing. It is possible that with different choices in an ICS proforma, several
different sets of TPs will be necessary.
In the following clauses assessments are made on whether requirements, features, components and other capabilities are
required according to a referenced standard and in order to achieve compliance. This assessment provides the following
options:
m mandatory - the capability is required to be supported.
o optional - the capability may, or may not, be supported.
c.i conditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on the support of
other optional or conditional items. "i" is an integer identifying a unique conditional status
expression which is defined immediately following the table.
n/a not applicable - in the given context, it is not possible to use the capability.
x prohibited (excluded) - there is a requirement not to use this capability in the given context.
o.i qualified optional - for mutually exclusive or selectable options from a set: "i" is an integer which
identifies a unique group of related optional items and the logic of their selection which is defined
immediately following the table.
4.2 Entities
Table 1: Entities
Item Name of field Reference Status Support
1 LIS ETSI TS 103 479 [1], clause 5.5 o.1
2 ESRP ETSI TS 103 479 [1], clause 5.2 o.1
3 ECRF ETSI TS 103 479 [1], clause 5.3 o.1
4 PSAP ETSI TS 103 479 [1], clause 5.4 o.1
5 BCF ETSI TS 103 479 [1], clause 5.1 o.1
o.1: At least one of the items shall be supported.

ETSI
9 ETSI TS 103 650-1 V1.2.1 (2022-08)
4.3 LIS features
Table 2: LIS features
Prerequisite: Table 1/1
Item Name of field Reference Status Support
1 HELD by Value IETF RFC 5985 [3], clause 4.2 m
2 HELD by Reference IETF RFC 5985 [3], clause 4.3 m
3 HELD by Reference GET ETSI TS 103 479 [1], clause 8 o
4 Does the IUT support Point IETF RFC 5985 [3], clause 6.2 m
IETF RFC 5491 [8], clause 5.2.1
5 Does the IUT support Circle IETF RFC 5985 [3], clause 6.2 m
IETF RFC 5491 [8], clause 5.2.3
6 Does the IUT support Civic Address IETF RFC 5985 [3], clause 6.2 m
IETF RFC 5491 [8], clause 3.2
7 Does the IUT support SIP Subscriptions ETSI TS 103 479 [1], clause 5.5 o
8 Does the IUT support subscriptions to ETSI TS 103 479 [1], clause 5.5 o
Element State
9 Does the IUT support subscriptions to ETSI TS 103 479 [1], clause 5.5 o
Service State
10 Does the IUT support subscriptions to ETSI TS 103 479 [1], clause 5.5 o
Security Posture
11 Does the IUT support AML via HTTP ETSI TS 103 479 [1], clause 5.5 o
12 Does the IUT support AML via Data SMS ETSI TS 103 479 [1], clause 5.5 o
13 Does the IUT support AML via Text SMS ETSI TS 103 479 [1], clause 5.5 o
14 Does the IUT support mutual TLS ETSI TS 103 479 [1], clause 6.1.1 m
authentication
4.4 ESRP features
Table 3: ESRP features
Prerequisite: Table 1/2
Item Name of field Reference Status Support
1 Does the IUT support SIP o.1
SUBSCRIPTION
2 Does the IUT support dequeue o.1
registration
3 Does the IUT support fixed target o.1
4 Does the IUT support queue state o
5 Does the IUT support security posture o
6 Does the IUT support element stats o
7 Does the IUT support service state o
8 Does the IUT support LoST protocol ETSI TS 103 479 [1], clause 5.2.2 m
9 Does the IUT support LoST protocol ETSI TS 103 479 [1], clause 5.2.2 o
with redirection
10 Does the IUT support HELD protocol ETSI TS 103 479 [1], clause 5.2.2 o
11 Does the IUT support HELP protocol ETSI TS 103 479 [1], clause 5.2.2 o
with location reference
12 Does the IUT support TLS mutual ETSI TS 103 479 [1], clause 5.5 o
authentication
13 Does the IUT support adding Call ETSI TS 103 479 [1], clause 6.1.2.7 m
Identifier
14 Does the IUT support adding Incident ETSI TS 103 479 [1], clause 6.1.2.7 m
Identifier
o.1: At least one of the items shall be supported.

ETSI
10 ETSI TS 103 650-1 V1.2.1 (2022-08)
4.5 ECRF features
Table 4: ECRF features
Prerequisite: Table 1/3
Item Name of field Reference Status Support
1 Does the IUT support Find Service IETF RFC 5222 [5], clause 14 m
2 Does the IUT support List Services ETSI TS 103 479 [1], clause 6.4 m
3 Does the IUT support List Services by Location
4 Does the IUT support Point IETF RFC 5222 [5], clause 12.2 m
IETF RFC 5491 [8], clause 5.2.1
5 Does the IUT support Circle IETF RFC 5222 [5], clause 12.2 m
IETF RFC 5491 [8], clause 5.2.3
6 Does the IUT support Ellipse IETF RFC 5222 [5], clause 12.2 o
IETF RFC 5491 [8], clause 5.2.3
7 Does the IUT support Arcband IETF RFC 5222 [5], clause 8.2 o
IETF RFC 5491 [8], clause 3.2
8 Does the IUT support Polygon IETF RFC 5222 [5], clause 12.2 o
IETF RFC 5491 [8], clause 5.2.3
9 Does the IUT support Loop detection IETF RFC 5222 [5], clause 6 m
10 Does the IUT support Redirection IETF RFC 5222 [5], clause 8.3.3 m
11 Does the IUT support subscriptions to Element ETSI TS 103 479 [1], clause 5.3 o
State
12 Does the IUT support subscriptions to Security ETSI TS 103 479 [1], clause 5.3 o
Posture
13 Does the IUT support subscriptions to Service ETSI TS 103 479 [1], clause 5.3 o
State
14 Does the IUT support TLS mutual authentication ETSI TS 103 479 [1], clause 5.5 o

4.6 PSAP features
Table 5: PSAP features
Prerequisite: Table 1/4
Item Name of field Reference Status Support
1 PSAP service ETSI TS 103 479 [1], clause 5.4 m
2 UDP handling ETSI TS 103 479 [1], clause 6.1.1 o.1
3 TCP handling ETSI TS 103 479 [1], clause 6.1.1 o.1
4 Does the IUT support Dequeue ETSI TS 103 479 [1], clause 6.2.1 o
registration/deregistration
5 Does the IUT support HELD protocol ETSI TS 103 479 [1], clause 6.5.1 o
6 Does IUT support LoST protocol ETSI TS 103 479 [1], clause 6.4.1 o
7 Does the IUT support TLS mutual authentication ETSI TS 103 479 [1], clause 5.5 o
o.1: At least one of the items shall be supported.

4.7 BCF features
Table 6: BCF features
Prerequisite: Table 1/5
Item Name of field Reference Status Support
1 BCF service ETSI TS 103 479 [1], clause 5.1 m
2 UDP handling ETSI TS 103 479 [1], clause 6.1.1 o.1
3 TCP handling ETSI TS 103 479 [1], clause 6.1.1 o.1
4 Does the IUT support TLS mutual authentication ETSI TS 103 479 [1], clause 5.5
o.1: At least one of the items shall be supported.

ETSI
11 ETSI TS 103 650-1 V1.2.1 (2022-08)
4.8 Mnemonics for PICS reference
To avoid an update of all related documents when the PICS document is changed, the table below introduces mnemonic
names and the correspondence with the PICS item number.
Table 7: Mnemonics for PICS reference
Mnemonic PICS item
PICS_LIS_HELD_BY_VALUE Table 2/1
PICS_LIS_HELD_BY_REFERENCE Table 2/2
PICS_LIS_HELD_BY_REFERENCE_GET Table 2/3
PICS_LIS_GEOMETRY_POINT Table 2/4
PICS_LIS_GEOMETRY_CIRCLE Table 2/5
PICS_LIS_CIVIC Table 2/6
PICS_LIS_SIP_SUBSCRIPTION Table 2/7
PICS_LIS_SIP_ELEMENT_STATE Table 2/8
PICS_LIS_SIP_SERVICE_STATE Table 2/9
PICS_LIS_SIP_SECURITY_POSTURE Table 2/10
PICS_LIS_AML_HTTP Table 2/11
PICS_LIS_AML_DATA_SMS Table 2/12
PICS_LIS_AML_TEXT_SMS Table 2/113
PICS_LIS_TLS_AUTHENTICATION Table 2/14
PICS_ESRP_TARGET_SIP_REGISTER_SUPPORT Table 3/1
PICS_ESRP_TARGET_DEQUEUE_REGISTRATION_SUPPORT Table 3/2
PICS_ESRP_FIXED_TARGET_SUPPORT Table 3/3
PICS_ESRP_QUEUE_STATE_SUPPORT Table 3/4
PICS_ESRP_SIP_SECURITY_POSTURE Table 3/5
PICS_ESRP_SIP_ELEMENT_STATE Table 3/6
PICS_ESRP_SIP_SERVICE_STATE Table 3/7
PICS_ESRP_LOST Table 3/8
PICS_ESRP_LOST_REDIRECT Table 3/9
PICS_ESRP_HELD Table 3/10
PICS_ESRP_HELD_LOCATION_REFERENCE Table 3/11
PICS_ESRP_TLS_AUTHENTICATION Table 3/12
PICS_ESRP_CALL_IDENTIFIER_SUPPORT Table 3/13
PICS_ESRP_INCIDENT_IDENTIFIER_SUPPORT Table 3/14
PICS_ECRF_FIND_SERVICE Table 4/1
PICS_ECRF_LIST_SERVICES Table 4/2
PICS_ECRF_LIST_SERVICES_BY_LOCATION Table 4/3
PICS_ECRF_GEOMETRY_POINT Table 4/4
PICS_ECRF_GEOMETRY_CIRCLE Table 4/5
PICS_ECRF_GEOMETRY_ELLIPSE Table 4/6
PICS_ECRF_GEOMETRY_ARCBAND Table 4/7
PICS_ECRF_GEOMETRY_POLYGON Table 4/8
PICS_ECRF_LOOP_DETECTION Table 4/9
PICS_ECRF_REDIRECT Table 4/10
PICS_ECRF_SIP_ELEMENT_STATE Table 4/11
PICS_ECRF_SIP_SECURITY_POSTURE Table 4/12
PICS_ECRF_SIP_SERVICE_STATE Table 4/13
PICS_ECRF_TLS_AUTHENTICATION Table 4/14
PICS_A_SIP_BSC1 Table 5/1
PICS_E_SIP_URN1 Table 5/1
PICS_E_SIP_URN2 Table 5/1
PICS_E_SIP_URN3 Table 5/1
PICS_PSAP_B_SDP_ULA1 Table 5/1
PICS_PSAP_B_SDP_ALA1 Table 5/1
PICS_PSAP_S_SIP_BYE1 Table 5/1
PICS_M_SIP_URN1 Table 5/1
PICS_E_SIP_OPT1 Table 5/1
PICS_E_SIP_ NO_REGISTRATION Table 5/1
PICS_PSAP_S_SIP_REGISTRATION Table 5/1
PICS_PSAP_S_SIP_UDP1 Table 5/2
PICS_PSAP_S_SIP_TCP1 Table 5/3
PICS_PSAP_S_HTTP_DEQUEUE_REGISTRATION Table 5/4
PICS_PSAP_S_HTTP_HELD Table 5/5
ETSI
12 ETSI TS 103 650-1 V1.2.1 (2022-08)
Mnemonic PICS item
PICS_PSAP_S_HTTP_LOST Table 5/6
PICS_PSAP_TLS_AUTHENTICATION Table 5/7
PICS_BCF_S_SIP_TCP1 Table 6/3
PICS_BCF_M_SIP_CALL_INFO Table 6/1
PICS_BCF_M_SIP_CALL_INFO_INCIDENT_TRACKING_ID Table 6/1
PICS_BCF_M_SIP_CALL_INFO_CALL_ID Table 6/1
PICS_BCF_M_SIP_CALL_INFO_SOURCE_ID Table 6/1
PICS_BCF_S_SIP_TCP1 Table 6/3
PICS_BCF_TLS_AUTHENTICATION Table 6/4

5 Test Configurations
5.1 LIS Test Configurations
5.1.1 CFG_LIS_01
Test Component IUT
HELD client (ESRP/PSAP) LIS
Figure 1: CFG_LIS_01
5.2 ESRP Test Configurations
5.2.1 CFG_ESRP_01
Test Component
HELD server (LIS)
Test Component
LOST Server (ECRF)
IUT
eth
ESRP
Test Component
SIP server (PSAP)
Test Component
SIP client (BCF)
Figure 2: CFG_ESRP_01
5.3 ECRF Test Configurations
5.3.1 CFG_ECRF_01
Test Component IUT
LOST client (ESRP) ECRF
Figure 3: CFG_ECRF_01
ETSI
13 ETSI TS 103 650-1 V1.2.1 (2022-08)
5.4 PSAP Test Configurations
5.4.1 CFG_PSAP_01
Test Component IUT
SIP UA (ESRP) PSAP
Figure 4: CFG_PSAP_01
5.5 BCF Test Configurations
5.5.1 CFG_BCF_01
TS IUT TS
SIP UA (ESRP) BCF PSAP
Figure 5: CFG_BCF_01
6 Test Suite Structure (TSS)
6.1 Structure for NG112 tests
The test grouping is organized on three (3) levels. The first level is the the reference to the base Document that contains
the requirements for the tests. The second level is the Group and identifies the protocol (LIS, ESRP, ECRF, PSAP and
BCF) component that is providing the Service or Interface to be tested. The third level is called Subgroup and identifies
a set of functionalities.
Moreover, test purposes are identified and categorized by a sequential two-digits number (uniquely assigned upon
definition of the each test purpose) and by the type of test performed. The type of test helps quickly identify the type of
behaviour that is expected by the IUT in the test purpose.
6.2 Test groups
6.2.1 Root
The root identifies the entities to be tested.
6.2.2 Test group
This level contains the protocols and protocol operations.
6.2.3 Test sub-group
This level identifies the sub categories of each Group.
6.2.4 Categories
This level contains the standard conformance test categories: behaviour for valid, invalid, inopportune events and
timers.
ETSI
14 ETSI TS 103 650-1 V1.2.1 (2022-08)
7 Test Purposes (TP)
7.1 Introduction
7.1.1 TP definition conventions
The TPs are defined by the rules shown in table 8.
Table 8: TP definition rules
TP Header
TP ID The TP ID is a unique identifier. It shall be specified according to the TP naming
conventions defined in the above clause.
Test objective Short description of test purpose objective according to the requirements from the
base standard.
Reference The reference indicates the clauses of the reference standard specifications in which
the conformance requirement is expressed.
Config Id The Config Id references the GeoNetworking configuration selected for this TP.
PICS Selection Reference to the PICS statement involved for selection of the TP. Contains a
Boolean expression.
TP Behaviour
Initial conditions The initial conditions define in which initial state the IUT has to be to apply the actual
TP. In the corresponding Test Case, when the execution of the initial condition does
not succeed, it leads to the assignment of an Inconclusive verdict.
Expected behaviour (TP body) Definition of the events, which are parts of the TP objective, and the IUT are
expected to perform in order to conform to the base specification. In the
corresponding Test Case, Pass or Fail verdicts can be assigned there.

ETSI
15 ETSI TS 103 650-1 V1.2.1 (2022-08)
7.1.2 TP Identifier naming conventions
The identifier of the TP is built according to table 9.
Table 9: TP naming convention
Identifier: TP_____
= root LIS
ESRP
ECRF
PSAP
BCF
= group HELD
HELD_BY_REFERENCE
Error
LOST
AML
FindService
Fixed_TARGET
SIP_REGISTER_TARGET
HTTP_DEQUEUE_REGISTRATION
QUEUE_STATE
SIP
TLS
=sub-group GET
PUT
POST
INVITE
REGISTER
ACK
BYE
MESSAGE
OPTIONS
CANCEL
INFO
SECURITY
= type of testing BV
BI
= sequential number
7.1.3 Rules for the behaviour description
In the TP the following wordings are used:
• "receives": for packets coming from the network to the IUT
• "sends": for packets sent by the IUT to the network
• "forwards": forwards the previously received message to the next hop
• "generates": for internal event generation
• "rejects": connection rejected due to security issue
• "isRequestedToSend": an upper layer requests the IUT to send a packet
• "havingLocationMappingFor": IUT is provisioned with the relevant location data
• "havingReturnedLocationUriFor": IUT returned a locationURI for the relevant location data after a HELD
request
• "isConfiguredWith": IUT is configured to use a specific service/parameter set
• "isReachableWith": the IUT is reachable via the specified URI
ETSI
16 ETSI TS 103 650-1 V1.2.1 (2022-08)
• "isNotReachable": the PSAP is not reachable
• "havingServiceBoundaryFor": IUT is provisioned with the relevant service boundary
• "serviceMappingFor": IUT is provisioned with the relevant service mapping
• "receivedInitialInviteRequestAndSentLostQueryToEcrf" (for more detail see INIT_CON_1)
• "receivedInitialInviteRequestWithoutLocationAndSentHeldRequestToLisFor" (for more detail see
INIT_CON_2)
• "receivedInitialInviteRequestWithLocationReferenceAndSentGetRequestToLisFor" (for more detail see
INIT_CON_3)
• "sendsLostQueryToEcrfFor": IUT sends a LoST request to the LIs with the given LOCATION (for more detail
see INIT_CON_4)
• "receivesHeldResponseWith": IUT receives a HELD response with the give LOCATION (for more detail see
INIT_CON_5)
• "receivesLostResponseWith": IUT receives a LoST response with the give URN (for more detail see
INIT_CON_6)
• "receivesLocationResponseWith": IUT receives a Location response with the give LOCATION (for more
detail see INIT_CON_7)
• "acceptingIncomingCalls": IUT ready to receive incoming calls
• "establishesIncomingCall": The IUT establishes the incoming call (for more detail see INIT_CON_8)
• "inAnActiveIncomingCall": An incoming call is established (for more detail see INIT_CON_9)
• "isConnected": connection between the IUT and peer is established
• "isDisconnected": connection between the IUT and peer is NOT established
• acceptingIncomingCalls: The IUT is ready to receive incoming calls
• establishesIncomingCall: The IUT establishes the incoming call
• acceptingIM: The IUT is ready to receive IM (Instant messaging)
• isRequestedToGetLocationInfo: The IUT is requested to send a request for location information
• isRequestedToGetRouteEmergencyCalls: The IUT is requested to send a request for route emergency call
7.1.4 Pre-defined initial conditions
7.1.4.1 ESRP initial conditions
INIT_CON_1
the IUT entity receives a TCP SIP_INVITE containing
Request_URI indicating value SERVICE_URN_1,
Content_Type indicating value "multipart/mixed",
body containing
SDP_AND_PIDF_MULTIPART
and the IUT entity sends a POST containing
Content_type indicating value "application/lost+xml;charset=utf-8",
body containing
xmlMessage containing
version indicating value "1.0",
element "findService" inNamespace "urn:ietf:params:xml:ns:lost1" containing
element "location" containing
element "Point" inNamespace "http://www.opengis.net/gml" containing
attribute "srsName" indicating value "urn:ogc:def:crs:EPSG::4326",
element "pos" indicating value LOCATION_1
ETSI
17 ETSI TS 103 650-1 V1.2.1 (2022-08)
element "service" indicating value SERVICE_URN_1
to the ECRF entity
INIT_CON_2
the IUT entity receives a UDP SIP_INVITE containing
Request_URI indicating value SERVICE_URN_1,
Content_Type indicating value "application/sdp",
P-Asserted-Identity indicating value tel:DEVICE_NUMBER,
body containing
SDP
and the IUT entity sends a POST containing
Content_type indicating value "application/lost+xml;charset=utf-8",
body containing
xmlMessage containing
version indicating value "1.0",
element "locationRequest" inNamespace "urn:ietf:params:xml:ns:geopriv:held" containing
element "locationType" indicating value "geodetic" containing
attribute "exact" indicating value "true"
element "device" inNamespace "urn:ietf:params:xml:ns:geopriv:held:id" containing
element "uri" inNamespace "urn:ietf:params:xml:ns:geopriv:held:id" indicating value
DEVICE_NUMBER
to the LIS entity
INIT_CON_3
the IUT entity receives a UDP SIP_INVITE containing
Request_URI indicating value SERVICE_URN_1,
Content_Type indicating value "application/sdp",
Geolocation indicating value LOCATION_URI
body containing
SDP
and the IUT entity sends a GET to the LOCATION_URI

INIT_CON_4
the IUT entity sends a POST containing
Content_type indicating value "application/lost+xml;charset=utf-8",
body containing
xmlMessage containing
version indicating value "1.0",
element "findService" inNamespace "urn:ietf:params:xml:ns:lost1" containing
element "location" containing
element "Point" inNamespace "http://www.opengis.net/gml" containing
attribute "srsName" indicating value "urn:ogc:def:crs:EPSG::4326",
element "pos" indicating value LOCATION
element "service" indicating value SERVICE_URN_1
to the
...