ETSI TS 134 229-3 V15.4.0 (2020-04)

Universal Mobile Telecommunications System (UMTS); LTE; Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 3: Abstract test suite (ATS) (3GPP TS 34.229-3 version 15.4.0 Release 15)

RTS/TSGR-0534229-3vf40

General Information

• Status: Published
• Publication Date: 16-Apr-2020
• Technical Committee: 3GPP RAN 5 - Mobile Terminal Conformance Testing (formely T1)
• Current Stage: 12 - Completion
• Completion Date: 17-Apr-2020

Standards Content (Sample)

TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Internet Protocol (IP) multimedia call control protocol based on
Session Initiation Protocol (SIP)
and Session Description Protocol (SDP);
User Equipment (UE) conformance specification;
Part 3: Abstract test suite (ATS)
(3GPP TS 34.229-3 version 15.4.0 Release 15)


3GPP TS 34.229-3 version 15.4.0 Release 15 1 ETSI TS 134 229-3 V15.4.0 (2020-04)

Reference
RTS/TSGR-0534229-3vf40
Keywords
LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 2 ETSI TS 134 229-3 V15.4.0 (2020-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
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
3GPP TS 34.229-3 version 15.4.0 Release 15 3 ETSI TS 134 229-3 V15.4.0 (2020-04)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 9
4 Requirements on the TTCN development . 9
5 Test method and test model . 9
5.1 Test method . 9
5.2 IMS CC test model . 9
5.2.1 Transport protocol . 15
5.2.2 IMS CC test cases over IP-CAN test model . 15
5.3 Upper Tester (UT) . 16
5.4 TTCN-3 . 16
5.5 Support of XCAP . 16
5.5.1 XCAP Server . 16
5.5.2 HTTP Signalling . 17
5.6 Void . 18
6 ASP definitions . 18
6.1 Void . 18
6.2 Void . 18
6.3 Void . 18
6.4 Void . 18
6.5 XCAP server ASP definitions . 18
7 Codec definitions for IP User Data . 19
7.1 Introduction . 19
7.2 General Aspects . 19
7.3 Requirements on abstract message syntax for IMS (SIP, SDP) . 19
7.3.1 Type definition - Syntax / Semantic aspects . 19
7.3.2 Deviations of the type definition semantic . 20
7.3.3 Additional requirements for codec implementations (SIP/IMS Message . 21
7.3.3.1 Differences between BNF - TTCN-3 Type Mapping . 21
7.3.3.2 URL Encoding . 24
7.3.4 Additional requirements for codec implementations (Message Body) . 25
7.3.5 Additional requirements for codec implementations (SDP Body) . 25
7.3.5.1 Differences between BNF - SDP Type Mapping . 25
7.3.5.2 Defined attributes . 26
7.3.6 Additional requirements for codec implementations (HTTP) . 28
7.3.7 Additional requirements for codec implementations (XML) . 28
7.4 Requirements for codec implementations (DHCP, DNS) . 28
8 Design consideration . 28
8.1 Void . 28
8.2 Void . 28
8.3 Void . 28
8.4 AT commands . 28
8.5 Timer Tolerances . 29
8.6 Bearer information for UTRAN . 29
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 4 ETSI TS 134 229-3 V15.4.0 (2020-04)
Annex A (normative): Abstract Test Suites (ATS) . 30
A.1 Version of specifications . 30
A.2 IMS-CC AT S . 30
A.2.1 Void . 34
A.2.2 Void . 34
A.2.3 Void . 34
Annex B (normative): Partial IXIT proforma . 35
B.0 Introduction . 35
B.1 Parameter values . 35
B.1.1 PIXITs . 35
B.2 MMI Commands . 37
Annex C: Void . 38
Annex D: Void . 39
Annex E (informative): TTCN3 style guide for 3GPP IMS ATS . 40
Annex F (informative): BNF Message Definitions . 41
Annex G (Normative): SIP Type Definitions and XSD References . 42
G.0 References of XSD and SIP Type Definitions . . 42
G.0.1 XML Schema Definitions (XSD) . 42
G.0.2 Common TTCN-3 Libraries . 43
G.1 LibSip_MessageBodyTypes . 44
G.1.1 MIMETypes . 44
G.2 References to TTCN-3 . 46
Annex H (informative): TTCN-3 Definitions of Common Interfaces . 47
H.1 IMS_PTC_CoordMsg . 47
H.2 IMS_ASP_TypeDefs . 50
H.3 HTTP_ASP_TypeDefs . 53
H.3.1 HTTP_ASP_Definitions . 53
H.3.2 HTTP_Port_Definitions . 56
H.4 References to TTCN-3 . 56
Annex I (informative): Change history . 57
History . 76

ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 5 ETSI TS 134 229-3 V15.4.0 (2020-04)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
Z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
rd
The present document is 3 part of a multi-part conformance test specification for UE and is valid for 3GPP Release 5
and above. The specification contains a TTCN design frame work and the detailed test specifications in TTCN for the
UE conformance at the Gm reference point.
3GPP TS 34.229-1 [5] contains a conformance test description in prose.
3GPP TS 34.229-2 [6] contains a pro-forma for the UE Implementation Conformance Statement (ICS).
3GPP TS 34.229-3 the present document.
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 6 ETSI TS 134 229-3 V15.4.0 (2020-04)
1 Scope
The present document specifies the protocol conformance testing in TTCN for the 3GPP User Equipment (UE) at the
Gm interface.
rd
The present document is the 3 part of a multi-part test specification, 3GPP TS 34.229. The following TTCN test
specification and design considerations can be found in the present document:
- the overall test suite structure;
- the testing architecture;
- the test methods and PCO definitions;
- the test configurations;
- the design principles, assumptions, and used interfaces to the TTCN tester (System Simulator);
- TTCN styles and conventions;
- the partial PIXIT proforma;
- the TTCN files for the mentioned protocols tests.
The Abstract Test Suites designed in the document are based on the test cases specified in prose
(3GPP TS 34.229-1 [5]).
The present document is valid for UE implemented according 3GPP Releases starting from Release 5 up to the Release
indicated on the cover page of the present document.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document unless the context in which the reference is made suggests a different Release is
relevant (information on the applicable release in a particular context can be found in e.g. test case title,
description or applicability, message description or content).
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 34.123-1: "User Equipment (UE) conformance specification; Part 1: Protocol
conformance specification".
[3] 3GPP TS 34.123-2: "User Equipment (UE) conformance specification; Part 2: Implementation
Conformance Statement (ICS) proforma specification".
[4] 3GPP TS 34.123-3: "User Equipment (UE) conformance specification; Part 3: Abstract Test Suites
(ATS)".
[5] 3GPP TS 34.229-1: "Internet Protocol (IP) multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE)
conformance specification; Part 1: Protocol conformance specification ".
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 7 ETSI TS 134 229-3 V15.4.0 (2020-04)
[6] 3GPP TS 34.229-2: "Internet Protocol (IP) multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE)
conformance specification; Part 2: Implementation Conformance Statement (ICS) specification".
[7] 3GPP TS 34.108: "Common test environments for User Equipment (UE) conformance testing".
[8] ISO/IEC 9646-1: "Information technology - Open systems interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[9] ISO/IEC 9646-7: "Information technology - Open systems interconnection - Conformance testing
methodology and framework - Part 7: Implementation Conformance Statements".
[10] ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[11] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP)
and Session Description Protocol (SDP); Stage 3".
[12] ETSI ES 201 873: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3".
[13] IETF RFC 3320: "Signalling Compression (SigComp)".
[14] IETF RFC 3485: "The Session Initiation Protocol (SIP) and Session Description Protocol (SDP)
Static Dictionary for Signalling Compression (SigComp)".
[15] IETF RFC 3486: "Compressing the Session Initiation Protocol (SIP)".
[16] IETF RFC 3261: "SIP: Session Initiation Protocol".
[17] IETF RFC 4566: "SDP: Session Description Protocol".
[18] IETF RFC 1035: "Domain names - implementation and specification".
[19] IETF RFC 1533: "DHCP Options and BOOTP Vendor Extensions".
[20] IETF RFC 2131: "Dynamic Host Configuration Protocol".
[21] IETF RFC 3315: "Dynamic Host Configuration Protocol for Ipv6 (DHCPv6)".
[22] IETF RFC 3319: "Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation
Protocol (SIP) Servers".
[23] IETF RFC 3361: "Dynamic Host Configuration Protocol (DHCP-for-Ipv4) Option for Session
Initiation Protocol (SIP) Servers".
[24] IETF RFC 3680: "A Session Initiation Protocol (SIP) Event Package for Registrations".
[25] 3GPP TS 24.173: "IMS multimedia telephony communication service and supplementary services;
Stage 3".
[26] IETF RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol
(XCAP)".
[27] IETF RFC 2616: "Hypertext Transfer Protocol – HTTP/1.1".
[28] 3GPP TS 36.523-1: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet
Core (EPC); User Equipment (UE) conformance specification; Part 1: Protocol conformance
specification".
[29] 3GPP TS 36.523-2: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet
Core (EPC); User Equipment (UE) conformance specification; Part 2: Implementation
Conformance Statement (ICS) proforma specification".
[30] 3GPP TS 36.523-3: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet
Core (EPC); User Equipment (UE) conformance specification; Part 3: Test suites".
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 8 ETSI TS 134 229-3 V15.4.0 (2020-04)
[31] 3GPP TS 36.508: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet
Core (EPC); Common test environments for User Equipment (UE) conformance testing".
[32] 3GPP TS 24.173: "IMS Multimedia telephony communication service and supplementary
services; Stage 3".
[33] 3GPP TS 24.109: "Bootstrapping interface (Ub) and network application function interface (Ua);
Protocol details".
[34] 3GPP TS 33.220: "Generic Authentication Architecture (GAA); Generic Bootstrapping
Architecture".
[35] 3GPP TS 33.222: "Generic Authentication Architecture (GAA); Access to network application
functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS)".
[36] 3GPP TS 24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
over the Ut interface for Manipulating Supplementary Services ".
[37] RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication".
[38] RFC 3966: "The tel URI for Telephone Numbers".
[39] RFC 2141: “URN Syntax”.
[40] 3GPP TS 24.604: "Communication Diversion (CDIV) using IP Multimedia (IM) Core Network
(CN) subsystem; Protocol specification".
[41] 3GPP TS 24.607: "Originating Identification Presentation (OIP) and Originating Identification
Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol
specification".
[42] 3GPP TS 24.608: "Terminating Identification Presentation (TIP) and Terminating Identification
Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol
specification".
[43] 3GPP TS 24.611: “Anonymous Communication Rejection (ACR) and Communication Barring
(CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[44] IETF RFC 4119 "A Presence-based GEOPRIV Location Object Format".
[45] IETF RFC 4575: "A Session Initiation Protocol (SIP) Event Package for Conference State".
[46] IETF RFC 5628: "Registration Event Package Extension for Session Initiation Protocol (SIP)
Globally Routable User Agent URIs (GRUUs)".
[47] IETF RFC 3863 "Presence Information Data Format (PIDF)".
[48] IETF RFC 4745: "Common Policy: A Document Format for Expressing Privacy Preferences".
[49] 3GPP TS 27.007: "AT command set for 3G User Equipment (UE)".
[50] 3GPP TS 34.229-4: “User Equipment (UE) conformance specification; Part 4: Enabler for IP
multimedia applications testing”.
[51] 3GPP TS 24.237: "IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem
(IMS) Service Continuity".
[52] 3GPP TS 31.121: “UICC-terminal interface; Universal Subscriber Identity Module (USIM)
application test specification”.
[53] 3GPP TS 24.390: “Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM)
Core Network (CN) subsystem IMS”.
[54] 3GPP TS 38.523-3: "5GS; UE conformance specification; Part 3: Protocol Test Suites".
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 9 ETSI TS 134 229-3 V15.4.0 (2020-04)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and
3GPP TS 34.229-1 [5] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and 3GPP TS 34.229-1 [5]
apply.
4 Requirements on the TTCN development
A number of requirements are identified for the development and production of TTCN specification for 3GPP UE at the
Gm reference point.
1. Top-down design, following 3GPP 34.229-1 [5], 3GPP TS 34.123-1 [2], 3GPP TS 34.108 [7].
2. A unique testing architecture and test method for testing all protocol layers of UE.
3. Uniform TTCN style and naming conventions.
4. Improve TTCN readability.
5. Using TTCN-3 (ES 201 873-1 [12]).
6. TTCN specification feasible, implementable and compilable.
7. Test cases shall be designed in a way for easily adaptable, upwards compatible with the evolution of the 3GPP
core specifications and the future Releases.
8. The test declarations, data structures and data values shall be largely reusable.
9. Modularity and modular working method.
10. Minimizing the requirements of intelligence on the emulators of the lower testers.
11. Giving enough design freedom to the test equipment manufacturers.
12. Maximizing reuse of RFC BNF definitions from the relevant IETF core specifications.
In order to fulfil these requirements and to ensure the investment of the test equipment manufacturers having a stable
testing architecture for a relatively long period, a unique testing architecture and test method are applied to the 3GPP
UE protocol tests.
5 Test method and test model
5.1 Test method
5.2 IMS CC test model
The test model over E-UTRA is shown in Figure 5.2-1a, the test model over UTRAN is shown in figure 5.2-1b, the test
model over WLAN is shown in figure 5.2-1c, the test model over fixed access is shown in figure 5.2-1d (NOTE: the
IPsec is not used by this model), and the test model over NR5GC is shown in Figure 5.2-1e.
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 10 ETSI TS 134 229-3 V15.4.0 (2020-04)
The IMS CC test cases are executed on top of the multi-testers test model according to TS 36.523-3 [30] for E-UTRA,
TS 34.123-3 [4] clause 6A for UTRAN and TS 38.523-3 [54] for NR5GC.

Figure 5.2-1a: Multi-TestersTest Model to support E-UTRA SS interface

ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 11 ETSI TS 134 229-3 V15.4.0 (2020-04)

Figure 5.2-1b: Multi-Testers Test Model to support UTRAN SS interface
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 12 ETSI TS 134 229-3 V15.4.0 (2020-04)

Figure 5.2-1c: Multi-Testers Test Model to support WLAN SS interface
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 13 ETSI TS 134 229-3 V15.4.0 (2020-04)

Figure 5.2-1d: Multi-Testers Test Model to support fixed access SS interface

ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 14 ETSI TS 134 229-3 V15.4.0 (2020-04)
Figure 5.2-1e: Multi-Testers Test Model to support NR5GC SS interface

The IMS CC test cases run on the IMS-PTC which controls the IPCanEmu and the IP-PTC. IPCanEmu is responsible
for cell setup and DRB/RAB establishment and the IP-PTC controls the IP related configurations. IPCanEmu and IP-
PTC interface to the SS according to TS 36.523-3 [30] or TS 34.123-3 [4] or TS 38.523-3 [54].
Clauses 4.2.4, 4.2.5 and 4.4.1.1 of TS 36.523-3 [30] describe the common handling of IP data in the multi-testers model
regarding IMS signalling. In addition to support HTTP over TLS a TCP server may be established with additional
parameters for TLS which may be required for XCAP (depending on the authentication mechanism to be applied for
XCAP test case).
The test model extensions for support of XCAP are shown in Figure 5.2-2. Clause 5.5 provides further information
regarding support of XCAP.
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 15 ETSI TS 134 229-3 V15.4.0 (2020-04)

Figure 5.2-2: Extended IP model to handle HTTP/XCAP data

NOTE: Figure 5.2-2 is just an example; further details are SS implementation dependent.
5.2.1 Transport protocol
For SIP requests originated by the UE, the transport protocol in UL is selected by the UE. This information is extracted
in the TTCN-3 and used in subsequent responses sent by the SS.
For SIP requests originated by the SS in DL UDP is used as transport protocol at the test. For the purpose of test
coverage, TCP is used in the specific test cases as specified.
NOTE: According to RFC 3261 [16] clause 18.1.1 the server side (UE) has to be able to cope with a maximum
datagram size of 65,535 bytes (independent of any guideline to restrict the maximum size of UDP packets
at the client side).
5.2.2 IMS CC test cases over IP-CAN test model
The "Enabler for IP multimedia applications testing" is described in TS 34.229-4 [50]. In general IMS CC test cases can
be run on this test model too as test case implementation - in general - is independent of the test model. The TTCN code
for IMS and HTTP PTC is the same for TS 34.229-3 and TS 34.229-4 implementations whereas the MTC
implementation is model specific. The implementation of the MTC, the IP-CAN/IP adaptor and the MMI system
interface is part of TS 34.229-4 and out of scope for this document. Common interfaces are documented in annex H of
this document.
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 16 ETSI TS 134 229-3 V15.4.0 (2020-04)
5.3 Upper Tester (UT)
The upper tester interface is the same as defined in TS 36.523-3 [30] clause 5 for E-UTRA or TS 34.123-3 [4] clause
6A.4 for UTRAN or TS 38.523-3 [54] clause 6.1 for NR5GC, with additional, IMS-specific AT commands as specified
in clause 8.4 and IMS-specific MMI commands as specified in annex B.2.
5.4 TTCN-3
TTCN is used as specification language. ES 201 873 [12] (TTCN-3) is applied to the notation.
5.5 Support of XCAP
MTSI supplementary services (TS 24.173[25]) like communication barring (CB) and communication diversion (CDIV)
require the XCAP protocol (RFC 4825[26]) for transporting and manipulating XML documents in the network
describing these services. Test cases for these services are specified in TS 34.229-1 [5] clause 15. As shown in figure
5.2-2 the SS shall provide an XCAP server to support XCAP test cases; the TTCN interface to this server is specified in
clause 6.5.
5.5.1 XCAP Server
Supplementary services are managed by the XCAP server in the simservs documents according to TS 24.623 [36]. Test
cases manipulating data related to supplementary services are specified in TS 34.229-1 [5] clause 15. For simplification
of the TTCN implementation, the XCAP server functionality shall be provided by the SS i.e. it is not implemented in
the TTCN. Access to the XCAP server can be distinguished into:
- HTTP based transaction between the UE and the XCAP server
- Initialisation and validation of the simservs document according to the test cases
In addition the UE may exchange HTTP messages for authentication (depending on the UE's security capabilities); see
figure 5.5.1-1.
Figure 5.5.1-1: IMS CC test model
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 17 ETSI TS 134 229-3 V15.4.0 (2020-04)

NOTE: In accordance to RFC 4825 clause 6.3 [26], the UE may use complex XPATH expressions to modify the
simservs document but this shall be handled by the XCAP server; in the TTCN these expressions are not
explicitly checked. Furthermore test case implementation itself does not use complex XPATH
expressions to access the simservs document, but always considers the whole document.
5.5.2 HTTP Signalling
RFC 4825 [26] specifies the protocol for accessing user data in the XCAP server via HTTP requests. An HTTP request
for an XCAP operation contains basically three components:
- Request line method, i.e. PUT, GET or DELETE
- Request line uri - The XCAP expression to be evaluated to access the XCAP document. The XCAP expression
consists of the document selector followed by the separator “~~” followed by the node selector pointing to the
user data to accessed or evaluated
- body - Describing the value (an xml fragment) referenced by the XCAP expression
Example 1
In order to set terminating-identity-presentation for user sip:[e-mail], the UE sends following HTTP request:
PUT http://XCAP- Server/simservs.ngn.etsi.org/users/sip%3Aob.stf160%40etsi.org/simservs.xml/~~
/simservs/terminating-identity-presentation/%40active
Body: true
If successful, the XCAP server responds with

HTTP/1.1 200 OK
Example 2
To get the value of terminating-identity-presentation for user sip:[e-mail], the UE sends following HTTP
request:
GET
/simservs/terminating-identity-presentation/%40active

If successful, the XCAP server responds with

HTTP/1.1 200 OK
Body: true
In this example
//XCAP-server/simservs.ngn.etsi.org/users/ sip%3Aob.stf160%40etsi.org/simservs.xml/–
Document selector for user .
~~ – Document selector separator, see RFC 4825
/simservs/terminating-identity-presentation/%40active – Node selector pointing to the information in
the XCAP server to be accessed. This is an XPATH expression, see RFC 4825 section 6.3.
true – Is the xml fragment (in this case very simple) to be set as value of the XPATH expression

Following operations shall be implemented in the XCAP server, see RFC 4825.
GET – Returns the requested data as an XML fragment to be send to the UE
input parameters: charstring documentSelector, charstring xpathExpr
returns: XML fragment or XML document

PUT – Builds an XML subtree or sets an attribute given by the xmlFragment at the position pointed by
the xpath expression
input parameters: charstring documentSelector, charstring xpathExpr, charstring xmlFragment or
xmlDocument
DELETE – Deletes an XML subtree or sets an attribute given by the xmlFragment at the position
pointed by the xpath expression
input parameters: charstring documentSelector, charstring xpathExpr
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 18 ETSI TS 134 229-3 V15.4.0 (2020-04)
5.6 Void
6 ASP definitions
This clause defines abstract system primitives (ASPs) for system interfaces which are used additionally to the system
interfaces defined in TS 36.523-3 [30], TS 34.123-3 [4] and TS 38.523-3 [54]. Further interfaces are documented in
annex H to support the IP-CAN test model according to TS 34.229-4 [50] but these interfaces are not system interfaces
in the scope of this document.
6.1 Void
6.2 Void
6.3 Void
6.4 Void
6.5 XCAP server ASP definitions
XCAP Layer ASPs are applicable to clause 5.2. and 5.6.
Name XCAP_REQ
Port XCAP_PORT
Comment ASP type for sending a request to the external XCAP server
according to RFC 4825 [26]
Parameter Name Parameter Type Comment
method charstring GET, PUT, DELETE or RESET
xcapExpression charstring XCAP expression sent by the UE
in its http request line
contentType charstring media type as contained in the
HTTP content type header
(optional)
xmlBody charstring XML fragment sent by the UE in
its http body or simservs
document initialised by the test
cases (optional)
Name
XCAP_RSP
Port XCAP_PORT
Comment ASP type for sending the response to the XCAP_REQ from the
XCAP server to TTCN
Parameter Name Parameter Type Comment
errorInfo charstring string indicating a system error
(optional)
contentType charstring media type as contained in the
HTTP content type header
(optional)
xmlBody charstring Result returned by the XCAP
server (optional)
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 19 ETSI TS 134 229-3 V15.4.0 (2020-04)
7 Codec definitions for IP User Data
7.1 Introduction
SIP is a text-based protocol, thus the message exchange between the UE and the SS are pure character strings. In the
TTCN-3 ATS the messages are structured and optimized to take the advantage of TTCN-3 functionality, and to make
the debugging and maintenance of the ATS easier.
7.2 General Aspects
IP user data for IMS conformance testing can be distinguished into:
1. text based: SIP (including SDP and XML messages), HTTP (see clause 7.4)
2. octetstring based: DHCP, DHCPv6, DNS (see clause 7.4)
In TTCN the following encoding information is used for user data:
Table 7.2-1
Type definitions Encoding
SMS Types Tabular notated (see note 1)
DHCPv4-Codec Tabular notated (see note 1)
DHCPv6-Codec Tabular notated (see note 1)
DNS-Codec Tabular notated (see note 1)
SIPCodec (see clause 7.3)
SDPCodec (see clause 7.3)
HttpCodec (see clause 7.3)
NOTE 1: Tabular notated is performed by concatenation of all the present fields in the TTCN-3 template.
NOTE 2: Encoding information is only needed for type definitions of peer-to-peer signalling; encoding of ASPs
used for system configuration or as co-ordination messages between PTCs is out of scope for this
document.
7.3 Requirements on abstract message syntax for IMS (SIP,
SDP)
7.3.1 Type definition - Syntax / Semantic aspects
All given defined BNF grammars (e.g. the ABNF of RFC 3261) are unique. Thus the syntax tree for each syntactically
correct message derived with these grammars are unique too and the parts of a message can be uniquely identified
(represented) by the terminal phrase belonging to a non terminal symbol and its derivation path in the syntax tree.
The syntax tree of all given messages can be used to uniquely identify and describe the parts of the messages. The
leaves are the part of every message and the nodes from the root to the leaves represent the sequence of rules to be
applied to derive that part
The IMS/SIP root message type is an ordered structured type, which is represented as a record type in TTCN-3. For
each grammar rule of the ABNF a TTCN-3 record type is declared with the specific name of the rule. The following
rules are applied to the fields within a record:
- A non-terminal symbol is declared as a record type for this symbol.
- The order of the symbols in the rule are represented by an equal order of the fields.
- Repetitions are declared as 'set of' or 'record of' types.
ETSI
3GPP TS 34.229-3 version 15.4.0 Release 15 20 ETSI TS 134 229-3 V15.4.0 (2020-04)
- Options are represented as optional record/set fields.
- Alternatives are declared as union types.
7.3.2 Deviations of the type definition semantic
- Most of the 'literals' of a message (for example: the string "Via" or "v" in the message header fields) are not
represented.
- The TTCN-3 charstring type is used where we stop structuring even if the ABNF uses structured types. More
details found in clause 8.3.3.
- Wherever possible parts are mapped to their best type representation, e.g. DIGIT based rules are mapped to
integer type not to a charstring type.
- All of the following delimiters (including preceding or following whitespace) defined by the ABNF grammar to
separate the parts of a message are not represented (see note).
STAR  = SWS "*" SWS ; asterisk
SLASH  = SWS "/" SWS ; slash
EQUAL  = SWS "=" SWS ; equal
LPAREN = SWS "(" SWS ; left parenthesis
RPAREN = SWS ")" SWS ; right parenthesis
RAQUOT = ">" SWS ; right angle quote
LAQUOT = SWS "<"; left angle quote
COMMA  = SWS "," SWS ; comma
SEMI  = SWS ";" SWS ; semicolon
COLON  = SWS ":" SWS ; colon
LDQUOT = SWS DQUOTE; open double quotation mark
RDQUOT = DQUOTE SWS ; close double quotation mark
HCOLON = *( SP / HTAB ) ":" SWS
SP   = single space
HTAB  = tab
SWS   = sep whitespace
NOTE: If they are present within a pure charstring they will be handled like a normal character and are still
included.
- Messages which are not of interest to the test suite are left undecoded as a charstring and will not be
further structured.
Further clarifications on the handling
...