|
TECHNICAL SPECIFICATION
LTE;
Mission Critical (MC) services over LTE;
Part 5: Abstract test suite (ATS)
(3GPP TS 36.579-5 version 13.1.0 Release 13)
---------------------- Page: 1 ----------------------
3GPP TS 36.579-5 version 13.1.0 Release 13 1 ETSI TS 136 579-5 V13.1.0 (2018-10)
Reference
RTS/TSGR-0536579-5vd10
Keywords
LTE
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 protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 36.579-5 version 13.1.0 Release 13 2 ETSI TS 136 579-5 V13.1.0 (2018-10)
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 36.579-5 version 13.1.0 Release 13 3 ETSI TS 136 579-5 V13.1.0 (2018-10)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 8
3.1 Definitions . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Test system architecture . 9
4.1 General system architecture . 9
4.2 Component architecture . 9
5 Test models . 9
5.1 MCPTT . 9
5.1.1 MCPTT Client on-network test model. 9
5.1.2 MCPTT Client off-network test model . 10
6 System interface . 10
6.1 Upper tester interface . 10
6.2 Abstract system primitives . 10
7 Test methods and design considerations . 11
7.1 MCPTT . 11
7.1.1 MCPTT Client . 11
7.1.1.1 Introduction . 11
7.1.1.2 UDP/IP handling . 11
7.1.1.3 RTP/RTCP handling . 11
7.1.1.4 Floor Control handling . 11
7.1.1.5 SS pseudo-algorithm . 11
8 Other SS requirements with TTCN-3 impact . 12
8.1 Codec requirements . 12
8.2 External function definitions . 12
9 IXIT Proforma . 12
9.1 General . 12
9.2 MCPTT . 13
9.2.1 MCPTT Client PIXIT . 13
9.2.2 MCPTT Server PIXIT . 18
10 Postambles . 20
10.1 Introduction . 20
10.2 MCPTT . 20
Annex A (normative): Test Suites . 21
A.1 Introduction . 21
A.2 Baseline of specifications . 21
A.3 MCPTT. 21
A.3.1 MCPTT Client Test Suites . 21
Annex B (informative): Style Guide . 22
B.1 Introduction . 22
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 36.579-5 version 13.1.0 Release 13 4 ETSI TS 136 579-5 V13.1.0 (2018-10)
Annex C (informative): Change history . 23
History . 24
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 36.579-5 version 13.1.0 Release 13 5 ETSI TS 136 579-5 V13.1.0 (2018-10)
Foreword
This Technical Specification has been produced by the 3rd 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.
The present document is part 1 of a multi-part conformance test specification for Mission Critical Push To Talk
(MCPTT) over LTE consisting of:
3GPP TS 36.579-1 [2]: "Mission Critical (MC) services over LTE; Part 1: Common test environment"
3GPP TS 36.579-2 [3]: "Mission Critical (MC) services over LTE; Part 2: Mission Critical Push To Talk
(MCPTT) User Equipment (UE) Protocol conformance specification"
3GPP TS 36.579-3 [4]: "Mission Critical (MC) services over LTE; Part 3: Mission Critical Push To Talk
(MCPTT) Server Application conformance specification"
3GPP TS 36.579-4 [5]: "Mission Critical (MC) services over LTE; Part 4: Test Applicability and
Implementation Conformance Statement (ICS) proforma specification"
3GPP TS 36.579-5: "Mission Critical (MC) services over LTE; Part 5: Abstract test suite (ATS)" (the
present specification)
In the present release of the specification only Mission Critical Push To Talk (MCPTT) services are considered. Future
releases may include other Mission Critical services.
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 36.579-5 version 13.1.0 Release 13 6 ETSI TS 136 579-5 V13.1.0 (2018-10)
1 Scope
The present document specifies the protocol and signalling conformance testing in TTCN-3 for the Mission Critical
services over LTE signalling and protocol requirements defined by 3GPP.
The following TTCN test specification and design considerations can be found in the present document:
- the test system architecture;
- the overall test suite structure;
- the test models and ASP definitions;
- the test methods and usage of communication ports definitions;
- the test configurations;
- the design principles and assumptions;
- TTCN styles and conventions;
- the partial Implementation eXtra Information for Testing (IXIT) proforma;
- the test suites.
The Abstract Test Suites designed in the document are based on the test cases specified in 3GPP TS 36.579-2 [3]. The
test cases specified in 3GPP TS 36.579-3 [4] are out of scope of the present document.
The applicability of the individual test cases is specified in the test ICS proforma specification in 3GPP TS 36.579-4
[5]). Where appropriate the Abstract Test Suites belonging to the present specification may refer to other Abstract Test
Suites e.g. 3GPP TS 36.523-3 [27] for test requirements related to the EPS (LTE) bearers which carry the Mission
Critical services data.
The present document is valid for TTCN development for Mission Critical services clients' conformance tests according
to 3GPP Releases starting from Release 13 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 36.579-1: "Mission Critical (MC) services over LTE; Part 1: Common test
environment".
[3] 3GPP TS 36.579-2: "Mission Critical (MC) services over LTE; Part 2: Mission Critical Push To
Talk (MCPTT) User Equipment (UE) Protocol conformance specification".
[4] 3GPP TS 36.579-3: "Mission Critical (MC) services over LTE; Part 3: Mission Critical Push To
Talk (MCPTT) Server Application conformance specification".
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 36.579-5 version 13.1.0 Release 13 7 ETSI TS 136 579-5 V13.1.0 (2018-10)
[5] 3GPP TS 36.579-4: "Mission Critical (MC) services over LTE; Part 4: Test Applicability and
Implementation Conformance Statement (ICS) proforma specification".
[6] 3GPP TS 36.523-1: "User Equipment (UE) conformance specification; Part 1: Protocol
conformance specification"
[7] 3GPP TS 22.179: "Mission Critical Push To Talk (MCPTT) over LTE; Stage 1".
[8] 3GPP TS 23.179: "Functional architecture and information flows to support mission critical
communication services; Stage 2".
[9] 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; Protocol specification".
[10] 3GPP TS 24.380: "Mission Critical Push To Talk (MCPTT) floor control; Protocol specification".
[11] 3GPP TS 24.481: "Mission Critical Services (MCS) group management; Protocol specification".
[12] 3GPP TS 24.482: "Mission Critical Services (MCS) identity management; Protocol specification".
[13] 3GPP TS 24.483: "Mission Critical Services (MCS) Management Object (MO)".
[14] 3GPP TS 24.484: "Mission Critical Services (MCS) configuration management; Protocol
specification".
[15] 3GPP TS 33.179: "Security of Mission Critical Push-To-Talk (MCPTT)".
[16] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP)
and Session Description Protocol (SDP); Stage 3".
[17] 3GPP TS 24.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 3".
[18] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2
Reference Point; Stage 3".
[19] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage
3".
[20] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage
3".
[21] 3GPP TS 23.003: "Numbering, addressing and identification".
[22] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[23] ISO/IEC 9646-7: "Information technology - Open systems interconnection - Conformance testing
methodology and framework - Part 7: Implementation Conformance Statements".
[24] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2".
[25] IETF RFC 4566 (July 2006): "SDP: Session Description Protocol".
[26] 3GPP TS 26.171: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband
(AMR-WB) speech codec; General description".
[27] 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".
[28] 3GPP TS 34.229-3: "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 Suites (ATS)".
[29] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[30] ISO/IEC 9646-7: "Information technology - Open systems interconnection - Conformance testing
methodology and framework - Part 7: Implementation Conformance Statements".
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 36.579-5 version 13.1.0 Release 13 8 ETSI TS 136 579-5 V13.1.0 (2018-10)
[31] ETSI ES 201 873: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3".
[32] IETF RFC 3711: "The Secure Real-time Transport Protocol (SRTP)".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP
TR 21.905 [1].
In addition for the purposes of the present document, the following terms, definitions, symbols and abbreviations apply:
- such given in ISO/IEC 9646-1 [22] and ISO/IEC 9646-7 [23]
NOTE: Some terms and abbreviations defined in [22] and [23] are explicitly included below with small
modification to reflect the terminology used in 3GPP.
Implementation eXtra Information for Testing (IXIT): A statement made by a supplier or implementer of an UEUT
which contains or references all of the information (in addition to that given in the ICS) related to the UEUT and its
testing environment, which will enable the test laboratory to run an appropriate test suite against the UEUT.
IXIT proforma: A document, in the form of a questionnaire, which when completed for an UEUT becomes an IXIT.
Protocol Implementation Conformance Statement (PICS): An ICS for an implementation or system claimed to
conform to a given protocol specification.
Protocol Implementation eXtra Information for Testing (PIXIT): An IXIT related to testing for conformance to a
given protocol specification.
3.2 Symbols
No specific symbols have been identified so far.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
ASP Abstract Service Primitive
ICS Implementation Conformance Statement
IXIT Implementation eXtra Information for Testing
MC Mission Critical
MCPTT Mission Critical Push To Talk
MCS Mission Critical Services
PTC Parallel Test Component
RTCP RTP Control Protocol
RTP Real-time Transport Protocol
SRTCP Secure RTCP
SRTP Secure RTP
SS System Simulator
SSRC Synchronization SouRCe
TC Test Case
UE User Equipment
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 36.579-5 version 13.1.0 Release 13 9 ETSI TS 136 579-5 V13.1.0 (2018-10)
4 Test system architecture
4.1 General system architecture
The architecture specified in TS 36.523-3 [27] applies to the present document.
4.2 Component architecture
The architecture specified in TS 36.523-3 [27] applies to the present document, with the exception that only one RAT,
E-UTRAN, is within the scope of the present document.
5 Test models
5.1 MCPTT
5.1.1 MCPTT Client on-network test model
The MCPTT Client on-network test model is depicted in figure 5.1.1-1. The test model consists of an IMS component
and an HTTP component, on top of the multi-testers test model (E-UTRA) specified in TS 36.523-3 [27]. These parallel
test components (PTCs) handle the IMS and HTTP signalling asynchronously.
The IMS PTC controls the IPCanEmu and the IP PTC. IPCanEmu is responsible for handling the E-UTRA cell(s)
configuration in the SS as well as the E-UTRA/EPC level signalling and related procedures. The IP PTC controls the IP
related configurations. IPCanEmu and IP PTC interface to the SS according to TS 36.523-3[27]. In addition, the IMS
PTC interfaces to the SS via a new port, SRTP, to support configuration of SRTP/SRTCP security in the SS and
transport of Floor Control messages, specified in TS 24.380 [10], from / to TTCN.
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 36.579-5 version 13.1.0 Release 13 10 ETSI TS 136 579-5 V13.1.0 (2018-10)
Figure 5.1.1-1: MCPTT Client on-network test model
5.1.2 MCPTT Client off-network test model
This test model is not supported by the present version of the specification.
6 System interface
6.1 Upper tester interface
The Upper Tester (UT) interface is the same as defined in TS 36.523-3 [27] clause 5, with additional IMS-specific AT
commands as specified in TS 34.229-3 [28] clause 8.4 and IMS-specific MMI commands as specified in TS 34.229-3
[28] annex B.2.
6.2 Abstract system primitives
This clause specifies the abstract system primitives (ASPs) used on the system interface to configure and control the SS.
The MCPTT test system interface re-uses the ASPs specified in TS 36.523-3 [27] (see clause 6 and Annex D) and TS
34.229-3 [28] (see clause 6).
ETSI
---------------------- Page: 11 ----------------------
3GPP TS 36.579-5 version 13.1.0 Release 13 11 ETSI TS 136 579-5 V13.1.0 (2018-10)
7 Test methods and design considerations
7.1 MCPTT
7.1.1 MCPTT Client
7.1.1.1 Introduction
Test cases for on-network operation are described in terms of IMS, Floor Control and HTTP signalling, see TS 36.379-2
[3]. Thus, on-network test cases are written in TTCN code running on the IMS and HTTP PTCs, see figure 5.1.1-1.
Floor Control messages are sent and received within the IMS PTC.
7.1.1.2 UDP/IP handling
The same mechanisms specified in TS 36.523-3 [27] for UDP/IP configuration and Routing Table configuration are
applied.
For MCPTT test cases with RTP/RTCP media streams, the TTCN shall configure the loopback mode specified in TS
36.523-3 [27] subclause 4.2.4.4.
7.1.1.3 RTP/RTCP handling
The RTP/RTCP loopback mechanism specified in TS 36.523-3 [27] applies as baseline.
MCPTT test cases require SRTP (secure RTP) for their media stream, which means that the loopback mechanism needs
to be enhanced: the RTP/RTCP packet in uplink needs to be decrypted with the Rx or uplink key, encrypted with the Tx
or downlink key and then sent back to the UE.
TTCN controls the usage of security for SRTP/SRTCP and provides the necessary security parameters to the SS via the
SRTP port. Once security has been configured by TTCN, the SS shall handle media plane encryption and decryption.
7.1.1.4 Floor Control handling
MCPTT requires that Floor Control messages are made available and handled in TTCN as structured messages.
The TTCN configures the SS, via the SRTP port, to filter Floor Control messages from the (S)RTCP traffic and provide
them to TTCN in uplink, also via the SRTP port. Similarly, when configured by TTCN, the TTCN may submit Floor
Control messages to the SS, via the SRTP port, for inclusion into the (S)RTCP stream and transmission (once
embedded in an RTCP APP packet) in downlink to the UE.
7.1.1.5 SS pseudo-algorithm
The following summarizes the requirements on the SS with regards to RTP / RTCP / Floor Control handling within the
SS:
- Uplink direction:
- Upon reception of an SRTP/SRTCP packet, the SS shall extract the UDP payload and decrypt it using the RX
crypto parameters.
- If SSRC is configured, the SS shall overwrite its value (octets 8 to 11 for SRTP and octets 4 to 7 for SRTCP,
see IETF RFC 3711 [32] clauses 3.1 and 3.4).
- If it is a RTCP APP packet containing a Floor Control message (RTCP packet with name field = "MCPT",
TS 24.380 [10] subclause 8.1.2), the SS shall extract and decode the Floor Control message and forward it to
TTCN via the SRTP port.
- Else the SS shall encrypt the packet using the Tx crypto parameters and send via UDP to the UE on the
remote port.
- Downlink direction:
ETSI
---------------------- Page: 12 ----------------------
3GPP TS 36.579-5 version 13.1.0 Release 13 12 ETSI TS 136 579-5 V13.1.0 (2018-10)
- Upon reception of a Floor Control message from TTCN on the SRTP port, the SS shall encode the message,
encrypt it and send it via UDP to the UE on the remote port.
8 Other SS requirements with TTCN-3 impact
8.1 Codec requirements
The requirements specified in TS 36.523-3 [27] clause 8.1 and TS 34.229-3 [28] clause 7 apply to the present
document.
8.2 External function definitions
The external functions specified in TS 36.523-3 [27] clause 8.2 apply to the present document.
9 IXIT Proforma
9.1 General
This partial IXIT proforma contained in the present document is provided for completion, when the related Abstract
Test Suite is to be used against the Implementation Under Test (IUT).
Text in italics is a comment for guidance for the production of an IXIT, and is not to be included in the actual IXIT.
The completed partial IXIT will normally be used in conjunction with the completed ICS, as it adds precision to the
information provided by the ICS.
ETSI
---------------------- Page: 13 ----------------------
3GPP TS 36.579-5 version 13.1.0 Release 13 13 ETSI TS 136 579-5 V13.1.0 (2018-10
...