|
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 14.5.0 Release 14)
---------------------- Page: 1 ----------------------
3GPP TS 34.229-3 version 14.5.0 Release 14 1 ETSI TS 134 229-3 V14.5.0 (2018-12)
Reference
RTS/TSGR-0534229-3ve50
Keywords
LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
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
If you find errors in the present document, please send your comment to one of the following services:
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 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
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
---------------------- Page: 2 ----------------------
3GPP TS 34.229-3 version 14.5.0 Release 14 2 ETSI TS 134 229-3 V14.5.0 (2018-12)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
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
---------------------- Page: 3 ----------------------
3GPP TS 34.229-3 version 14.5.0 Release 14 3 ETSI TS 134 229-3 V14.5.0 (2018-12)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 8
3.1 Definitions . 8
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 . 17
5.2.2 IMS CC test cases over IP-CAN test model . 18
5.3 Upper Tester (UT) . 18
5.4 TTCN-3 . 18
5.5 Support of XCAP . 18
5.5.1 XCAP Server . 18
5.5.2 HTTP Signalling . 19
5.6 Void . 20
6 ASP definitions . 20
6.1 Void . 20
6.2 Void . 20
6.3 Void . 20
6.4 Void . 20
6.5 XCAP server ASP definitions . 20
7 Codec definitions for IP User Data . 21
7.1 Introduction . 21
7.2 General Aspects . 21
7.3 Requirements on abstract message syntax for IMS (SIP, SDP) . 22
7.3.1 Type definition - Syntax / Semantic aspects . 22
7.3.2 Deviations of the type definition semantic . 22
7.3.3 Additional requirements for codec implementations (SIP/IMS Message . 23
7.3.3.1 Differences between BNF - TTCN-3 Type Mapping . 23
7.3.3.2 URL Encoding . 26
7.3.4 Additional requirements for codec implementations (Message Body) . 27
7.3.5 Additional requirements for codec implementations (SDP Body) . 27
7.3.5.1 Differences between BNF - SDP Type Mapping . 27
7.3.5.2 Defined attributes . 28
7.3.6 Additional requirements for codec implementations (HTTP) . 30
7.3.7 Additional requirements for codec implementations (XML) . 30
7.4 Requirements for codec implementations (DHCP, DNS) . 30
8 Design consideration . 30
8.1 Void . 30
8.2 Void . 30
8.3 Void . 30
8.4 AT commands . 30
8.5 Timer Tolerances . 31
8.6 Bearer information for UTRAN . 31
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 34.229-3 version 14.5.0 Release 14 4 ETSI TS 134 229-3 V14.5.0 (2018-12)
Annex A (normative): Abstract Test Suites (ATS) . 32
A.1 Version of specifications . 32
A.2 IMS-CC AT S . 32
A.2.1 Void . 36
A.2.2 Void . 36
A.2.3 Void . 36
Annex B (normative): Partial IXIT proforma . 36
B.0 Introduction . 37
B.1 Parameter values . 37
B.1.1 PIXITs . 37
B.2 MMI Commands . 39
Annex C: Void . 40
Annex D: Void . 41
Annex E (informative): TTCN3 style guide for 3GPP IMS ATS . 42
Annex F (informative): BNF Message Definitions . 43
Annex G (Normative): SIP Type Definitions and XSD References . 44
G.0 References of XSD and SIP Type Definitions . . 44
G.0.1 XML Schema Definitions (XSD) . 44
G.0.2 Common TTCN-3 Libraries . 45
G.1 LibSip_MessageBodyTypes . 45
G.1.1 MIMETypes . 45
G.2 References to TTCN-3 . 47
Annex H (informative): TTCN-3 Definitions of Common Interfaces . 48
H.1 IMS_PTC_CoordMsg . 48
H.2 IMS_ASP_TypeDefs . 51
H.3 HTTP_ASP_TypeDefs . 54
H.3.1 HTTP_ASP_Definitions . 54
H.3.2 HTTP_Port_Definitions . 56
H.4 References to TTCN-3 . 57
Annex I (informative): Change history . 58
History . 76
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 34.229-3 version 14.5.0 Release 14 5 ETSI TS 134 229-3 V14.5.0 (2018-12)
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
---------------------- Page: 6 ----------------------
3GPP TS 34.229-3 version 14.5.0 Release 14 6 ETSI TS 134 229-3 V14.5.0 (2018-12)
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 ".
[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".
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 34.229-3 version 14.5.0 Release 14 7 ETSI TS 134 229-3 V14.5.0 (2018-12)
[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".
[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".
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 34.229-3 version 14.5.0 Release 14 8 ETSI TS 134 229-3 V14.5.0 (2018-12)
[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”.
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.
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 34.229-3 version 14.5.0 Release 14 9 ETSI TS 134 229-3 V14.5.0 (2018-12)
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,
...