ETSI TS 137 579-5 V18.5.0 (2026-04)

LTE; 5G; Mission Critical (MC) services; Part 5: Abstract test suite (ATS) (3GPP TS 37.579-5 version 18.5.0 Release 18)

RTS/TSGR-0537579-5vi50

General Information

• Status: Not Published
• Technical Committee: 3GPP RAN 5 - Mobile Terminal Conformance Testing (formely T1)
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Completion Date: 02-Apr-2026

Standards Content (Sample)

TECHNICAL SPECIFICATION
LTE;
5G;
Mission Critical (MC) services;
Part 5: Abstract test suite (ATS)
(3GPP TS 37.579-5 version 18.5.0 Release 18)


3GPP TS 37.579-5 version 18.5.0 Release 18 1 ETSI TS 137 579-5 V18.5.0 (2026-04)

Reference
RTS/TSGR-0537579-5vi50
Keywords
5G,LTE
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 the
ETSI Search & Browse Standards application.
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 on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
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
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
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 2026.
All rights reserved.
ETSI
3GPP TS 37.579-5 version 18.5.0 Release 18 2 ETSI TS 137 579-5 V18.5.0 (2026-04)
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 IPR online database.
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™, LTE™ and 5G™ logo 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.
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 at 3GPP to ETSI numbering cross-referencing.
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 37.579-5 version 18.5.0 Release 18 3 ETSI TS 137 579-5 V18.5.0 (2026-04)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 7
2 References . 7
3 Definitions of terms, symbols and abbreviations . 10
3.1 Terms . 10
3.2 Symbols . 11
3.3 Abbreviations . 11
4 Test system architecture . 11
4.1 General system architecture . 11
4.2 Component architecture . 11
5 Test models . 12
5.1 MCX test model with TTCN based E-UTRA/EPC implementation (MCX EUTRA test model) . 12
5.1.1 MCX Client on-network test model (EUTRA) . 12
5.1.2 MCX Client off-network test model (EUTRA) . 13
5.2 MCX test model with SS based E-UTRA/EPC or NR/5GC implementation (MCX IPCAN test model) . 13
5.2.1 MCX Client on-network test model . 13
5.3 MCX test model with TTCN based NR/5GC implementation (MCX NR5GC test model) . 16
5.3.1 MCX Client on-network test model (NR5GC) . 16
5.3.2 MCX Client off-network test model (NR5GC) . 17
6 System interface . 18
6.1 Upper tester interface . 18
6.2 Abstract system primitives . 18
7 Test methods and design considerations . 18
7.0 Introduction . 18
7.1 Media plane signalling . 18
7.1.0 Introduction. 18
7.1.1 MCPTT . 18
7.1.1.1 Void. 18
7.1.1.2 UDP/IP handling . 18
7.1.1.3 RTP/RTCP handling . 19
7.1.1.4 Media Control handling . 19
7.1.1.5 SS pseudo-algorithm for RTP / RTCP / Media Plane Control handling . 19
7.1.2 MCVideo . 19
7.1.3 MCData . 20
7.2 MCX functional architecture: HTTP, SIP . 20
7.2.1 HTTP-Signalling . 20
7.2.2 SIP-Signalling . 21
7.3 Interactive connectivity establishment (ICE) for pre-established session . 22
8 Other SS requirements with TTCN-3 impact . 23
8.1 Codec requirements . 23
8.2 External function definitions . 23
9 IXIT Proforma . 28
9.1 General . 28
9.2 MCX . 30
9.2.1 MCX Client PIXIT . 30
9.2.2 MCX Server PIXIT . 35
9.2.3 MCX Constant PIXIT Definitions . 35
9.3 MCX IPCAN test model . 39
ETSI
3GPP TS 37.579-5 version 18.5.0 Release 18 4 ETSI TS 137 579-5 V18.5.0 (2026-04)
10 Postambles . 39
10.1 Introduction . 39
10.2 MCX . 39
Annex A (normative): Test Suites . 40
A.1 Introduction . 40
A.2 Baseline of specifications . 40
A.3 MCX Client Test Suites . 40
A.3.1 MCPTT Client Test Suites . 40
A.3.2 MCVideo Client Test Suites . 44
A.3.3 MCData Client Test Suites . 44
Annex B (informative): Style Guide . 46
B.1 Introduction . 46
Annex C (normative): Common TTCN-3 Definitions . . 47
C.0 Introduction . 47
C.1 SRTP_ASP_TypeDefs . 47
C.1.1 Type_Definitions . 47
C.1.2 System_Interface . 50
C.2 IP_ASP_TypeDefs . 50
C.2.1 IP_Common . 50
C.3 CommonDefs . 52
C.4 References to TTCN-3 . 52
Annex D (normative): SIP Type Definitions and XSD References . 53
D.1 XML Schema Definitions (XSD) . 53
D.2 Common TTCN-3 Libraries . 59
Annex E (normative): TTCN-3 Definitions for the MCX IPCAN test model . 60
E.0 Introduction . 60
E.1 MCX_IPCAN_ASP_TypeDefs . 60
E.2 MCX_CommonIPCAN . 69
E.3 CommonDefs . 69
E.4 References to TTCN-3 . 71
Annex F (informative): Procedures of the MCX IPCAN test model . 72
F.1 Introduction . 72
F.2 Procedures . 72
F.2.1 Initialisation . 72
F.2.2 Initial Registration . 72
F.2.3 MO RRC connection setup . 75
F.2.4 MT RRC connection setup . 75
F.2.5 MO communication establishment . 76
F.2.6 MT communication establishment . 77
F.2.7 Connection release . 77
Annex G (informative): Change history . 79
History . 83

ETSI
3GPP TS 37.579-5 version 18.5.0 Release 18 5 ETSI TS 137 579-5 V18.5.0 (2026-04)
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 5 of a multi-part conformance test specification for Mission Critical services consisting of:
3GPP TS 37.579-1 [2]: "Mission Critical (MC) services; Part 1: Common test environment"
3GPP TS 37.579-2 [3]: "Mission Critical (MC) services; Part 2: Mission Critical Push To Talk (MCPTT) User
Equipment (UE) Protocol conformance specification"
3GPP TS 37.579-4 [5]: "Mission Critical (MC) services; Part 4: Test Applicability and Implementation
Conformance Statement (ICS) proforma specification"
3GPP TS 37.579-5: "Mission Critical (MC) services; Part 5: Abstract test suite (ATS)" (the present
specification)
3GPP TS 37.579-6 [59]: "Mission Critical (MC) services; Part 6: Mission Critical Video (MCVideo) User
Equipment (UE) Protocol conformance specification"
3GPP TS 37.579-7 [60]: "Mission Critical (MC) services; Part 7: Mission Critical Data (MCData) User
Equipment (UE) Protocol conformance specification"
In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in
Technical Reports.
The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided
insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced,
non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a
referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something
ETSI
3GPP TS 37.579-5 version 18.5.0 Release 18 6 ETSI TS 137 579-5 V18.5.0 (2026-04)
The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions
"might not" or "shall not" are used instead, depending upon the meaning intended.
can indicates that something is possible
cannot indicates that something is impossible
The constructions "can" and "cannot" are not substitutes for "may" and "need not".
will indicates that something is certain or expected to happen as a result of action taken by an agency
the behaviour of which is outside the scope of the present document
will not indicates that something is certain or expected not to happen as a result of action taken by an
agency the behaviour of which is outside the scope of the present document
might indicates a likelihood that something will happen as a result of action taken by some agency the
behaviour of which is outside the scope of the present document
might not indicates a likelihood that something will not happen as a result of action taken by some agency
the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact
is not (or any other negative verb in the indicative mood) indicates a statement of fact
The constructions "is" and "is not" do not indicate requirements.
ETSI
3GPP TS 37.579-5 version 18.5.0 Release 18 7 ETSI TS 137 579-5 V18.5.0 (2026-04)
1 Scope
The present document specifies the protocol and signalling conformance testing in TTCN-3 for the Mission Critical
services 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 37.579-2 [3], TS
37.579-6 [59] and TS 37.579-7 [60].
The applicability of the individual test cases is specified in the test ICS proforma specification in 3GPP TS 37.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] and TS 38.523-3 [72] for test requirements related to the 3GPP 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 14 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 37.579-1: "Mission Critical (MC) services; Part 1: Common test environment".
[3] 3GPP TS 37.579-2: "Mission Critical (MC) services; Part 2: Mission Critical Push To Talk
(MCPTT) User Equipment (UE) Protocol conformance specification".
[4] Void.
[5] 3GPP TS 37.579-4: "Mission Critical (MC) services; Part 4: Test Applicability and
Implementation Conformance Statement (ICS) proforma specification".
ETSI
3GPP TS 37.579-5 version 18.5.0 Release 18 8 ETSI TS 137 579-5 V18.5.0 (2026-04)
[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] Void.
[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".
[31] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 1: TTCN-3 Core Language".
ETSI
3GPP TS 37.579-5 version 18.5.0 Release 18 9 ETSI TS 137 579-5 V18.5.0 (2026-04)
[32] IETF RFC 3711: "The Secure Real-time Transport Protocol (SRTP)".
[33] 3GPP TS 27.007: "AT command set for User Equipment (UE)".
[34] IETF RFC 4661: "An Extensible Markup Language (XML)-Based Format for Event Notification
Filtering".
[34] IETF RFC 4826: "Extensible Markup Language (XML) Formats for Representing Resource
Lists".
[35] W3C: "XML Encryption Syntax and Processing Version 1.1", https://www.w3.org/TR/xmlenc-
core1/.
[36] W3C: "XML Signature Syntax and Processing (Second Edition)", http://www.w3.org/TR/xmldsig-
core/.
[37] Void.
[38] Void.
[39] Void.
[40] Void.
[41] W3C: "XML Encryption Syntax and Processing Version 1.1", https://www.w3.org/TR/xmlenc-
core1/.
[42] W3C: "XML Signature Syntax and Processing (Second Edition)", http://www.w3.org/TR/xmldsig-
core/.
[43] 3GPP TS 33.180: "Security of the mission critical service".
[44] IETF RFC 6507: "Elliptic Curve-Based Certificateless Signatures for Identity-Based Encryption
(ECCSI)".
[45] IETF RFC 6508: "Sakai-Kasahara Key Encryption (SAKKE)".
[46] IETF RFC 6509 (February 2012): ''MIKEY-SAKKE: Sakai-Kasahara Key Encryption in
Multimedia Internet KEYing (MIKEY)''.
[47] IETF RFC 3394: "Advanced Encryption Standard (AES) Key Wrap Algorithm".
[48] W3C: "XML Signature Syntax and Processing (Second Edition)", http://www.w3.org/TR/xmldsig-
core/.
[49] IETF RFC 7515: "JSON Web Signature (JWS)".
[50] IETF RFC 5261: "An Extensible Markup Language (XML) Patch Operations Framework Utilizing
XML Path Language (XPath) Selectors".
[51] IETF RFC 5874: "An Extensible Markup Language (XML) Document Format for Indicating a
Change in XML Configuration Access Protocol (XCAP) Resources".
[52] IETF RFC 4354: "A Session Initiation Protocol (SIP) Event Package and Data Format for Various
Settings in Support for the Push-to-Talk over Cellular (PoC) Service".
[53] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
[54] 3GPP TS 23.280: "Common functional architecture to support mission critical services".
[55] 3GPP TS 24.281: "Mission Critical Video (MCVideo) signalling control; Protocol specification"
[56] 3GPP TS 24.581: "Mission Critical Video (MCVideo) media plane control; Protocol specification"
[57] 3GPP TS 24.282: "Mission Critical Data (MCData) signalling control; Protocol specification"
[58] 3GPP TS 24.582: "Mission Critical Data (MCData) media plane control; Protocol specification"
ETSI
3GPP TS 37.579-5 version 18.5.0 Release 18 10 ETSI TS 137 579-5 V18.5.0 (2026-04)
[59] 3GPP TS 37.579-6: "Mission Critical (MC) services; Part 6: Mission Critical Video (MCVideo)
User Equipment (UE) Protocol conformance specification"
[60] 3GPP TS 37.579-7: "Mission Critical (MC) services; Part 7: Mission Critical Data (MCData) User
Equipment (UE) Protocol conformance specification"
[61] 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".
[62] IETF RFC 4122: "A Universally Unique IDentifier (UUID) URN Namespace"
[63] IETF RFC 5245: "Interactive Connectivity Establishment (ICE): A Protocol for Network Address
Translator (NAT) Traversal for Offer/Answer Protocols"
[64] IETF RFC 3830: "MIKEY: Multimedia Internet KEYing".
[65] IETF RFC 6509 (February 2012): ''MIKEY-SAKKE: Sakai-Kasahara Key Encryption in
Multimedia Internet KEYing (MIKEY)''.
[66] IETF RFC 6043: "MIKEY-TICKET: Ticket-Based Modes of Key Distribution in Multimedia
Internet KEYing (MIKEY)".
[67] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications".
[68] IETF RFC 4975: "The Message Session Relay Protocol (MSRP)".
[69] IETF RFC 2616: "Hypertext Transfer Protocol -- HTTP/1.1".
[70] ETSI ES 201 873-11: "Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3; Part 11: Using JSON with TTCN-3".
[71] OMA-TS-REST_NetAPI_NMS-V1_0-20190528-C: "RESTful Network API for Network
Message Storage".
[72] 3GPP TS 38.523-3: "5GS; User Equipment (UE) conformance specification; Part 3: Protocol Test
Suites".
[73] 3GPP TS 38.508-1: "5GS; User Equipment (UE) conformance specification; Part 1: Common test
environment".
[74] 3GPP TS 38.508-2: "5GS; User Equipment (UE) conformance specification; Part 2: Common
Implementation Conformance Statement (ICS) proforma".
[75] ETSI ES 201 873-9: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 9: Using XML schema with TTCN-3".
[76] OMA-TS-REST_NetAPI_NotificationChannel-V1_0-20200319-C: “RESTful Network API for
Notification Channel”.
3 Definitions of terms, symbols and abbreviations
3.1 Terms
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.
ETSI
3GPP TS 37.579-5 version 18.5.0 Release 18 11 ETSI TS 137 579-5 V18.5.0 (2026-04)
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
MCData Mission Critical Data
MCPTT Mission Critical Push To Talk
MCS Mission Critical Services
MCVideo Mission Critical Video
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
4 Test system architecture
4.1 General system architecture
The architecture specified in TS 36.523-3 [27] clause 4.1.1 applies to the present document.
4.2 Component architecture
The architecture specified in TS 36.523-3 [27] clause 4.1.2 and TS 38.523-3 [72] clause 4.2 applies to the present
document, with the clarification that only single RAT scenarios (E-UTRAN or NR/5GC) are considered by the test
model of the present document.
ETSI
3GPP TS 37.579-5 version 18.5.0 Release 18 12 ETSI TS 137 579-5 V18.5.0 (2026-04)
5 Test models
5.1 MCX test model with TTCN based E-UTRA/EPC
implementation (MCX EUTRA test model)
5.1.1 MCX Client on-network test model (EUTRA)
The MCX EUTRA 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 34.229-3 [28]. 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 IPCanEmu and the
NAS EMU are based on the TTCN implementation used for E-UTRA/EPC conformance testing according to TS
36.523-3 [27]. The IP PTC controls the IP related configurations as described in TS 36.523-3[27]. In addition, there is
an SRTP port at the MCX IMS PTC mapped to the system interface to configure SRTP/SRTCP for media streams and
media control messages (see clause 7.1.1.3). The media control messages are exchanged between TTCN and the system
simulator via the IP PTC's IP_SOCK port (see clause 7.1.1.4 and clause 7.1.1.5) whereas the media stream messages are
handled by the SS (see clause 7.1.1.5).

Figure 5.1.1-1: MCX Client on-network test model with TTCN based E-UTRA/EPC implementation
As described in TS 37.579-1 [2] clause 5.4.1A after switch on the UE may register to an internet PDN, an IMS PDN
and the MCX PDN. Table 5.1.1-1 shows which IP addresses are assigned to a particular PDN.
ETSI
3GPP TS 37.579-5 version 18.5.0 Release 18 13 ETSI TS 137 579-5 V18.5.0 (2026-04)
Table 5.1.1-1: Mapping of IP addresses to PDNs
PDN IP address Value Comment
MCX NW IP address px_IPv4_Address1_NW, px_IPv6_Address1_NW PDN_1 in TTCN
UE IP address px_IPv4_Address1_UE, px_IPv6_Address1_UE
IMS NW IP address px_IPv4_Address2_NW, px_IPv6_Address2_NW PDN_2 in TTCN
UE IP address px_IPv4_Address2_UE, px_IPv6_Address2_UE
Internet NW IP address px_IPv4_Address3_NW, px_IPv6_Address3_NW PDN_3 in TTCN
UE IP address px_IPv4_Address3_UE, px_IPv6_Address3_UE

5.1.2 MCX Client off-network test model (EUTRA)
An MCX Client off-network test model for EUTRA is not supported by the present version of the specification.
5.2 MCX test model with SS based E-UTRA/EPC or NR/5GC
implementation (MCX IPCAN test model)
5.2.1 MCX Client on-network test model
In contrast to the MCX EUTRA test model (specified in clause 5.1.1) or NR5GC test model (specified in clause 5.3.1)
the MCX IPCAN test model shown in figure 5.2.1-1 uses an external IPCAN (black-box) implementation which is
integrated in the system simulator. In general, this IPCAN implementation shall be conformant in terms of TS 36.508
[61] and TS 38.508-1 [73] but this is out of the scope for the MCX IPCAN test model as long as the IPCAN
implementation obeys the commands at the system interface as specified in annex E.
ETSI
3GPP TS 37.579-5 version 18.5.0 Release 18 14 ETSI TS 137 579-5 V18.5.0 (2026-04)

Figure 5.2.1-1: MCX Client on-network test model with SS based E-UTRA/EPC or NR/5GC
implementation
NOTE 1: Whether or how the MCX IPCAN test model may use other IP-connectivity access networks is out of
scope of this specification.
NOTE 2: The SYS_IND port shown in figure 5.2.1-1 is used only in case of NR5GC to indicate the PDU session id
in a system indication and to assign the QFI in the corresponding acknowledgement.
NOTE 3: In the rest of this clause the term "PDN" is used for a PDN connectivity in EUTRA or a PDU session in
NR5GC.
NOTE 4: The major procedures for configuration and control of the system simulator are illustrated in annex F.
As described in clauses 5.4.1A and 5.4.1B of TS 37.579-1 [2] after switch on the UE may register to an internet PDN,
an IMS PDN and the MCX PDN. Nevertheless, in TTCN the MCX IPCAN test model supports signalling for the MCX
PDN only: The IPCAN test model does not handle any signalling for the other PDNs and especially not the SIP
signalling for an IMS registration to the IMS PDN.
 It is up to SS implementation to handle the potential registrations to an internet PDN and/or an IMS PDN.
Tables 5.2.1-1 and 5.2.1-2 show the information provided to the SS for configuration of the PDNs for EUTRA and
NR5GC.
ETSI
3GPP TS 37.579-5 version 18.5.0 Release 18 15 ETSI TS 137 579-5 V18.5.0 (2026-04)
Table 5.2.1-1: PDN info for EUTRA
PDN Parameter Value/Comment
MCX EPS Bearer ID (NOTE 2) px_MCX_IPCAN_EpsBearerId_MCX (NOTE 1)
NW IP address px_IPv4_Address1_NW, px_IPv6_Address1_NW (NOTE 3)
UE IP address px_IPv4_Address1_UE, px_IPv6_Address1_UE (NOTE 3)
IMS EPS Bearer ID (NOTE 2) px_MCX_IPCAN_EpsBearerId_IMS (NOTE 1)
NW IP address px_IPv4_Address2_NW, px_IPv6_Address2_NW
UE IP address px_IPv4_Address2_UE, px_IPv6_Address2_UE
Internet EPS Bearer ID (NOTE 2) px_MCX_IPCAN_EpsBearerId_INTERNET (NOTE 1)
NW IP address px_IPv4_Address3_NW, px_IPv6_Address3_NW
UE IP address px_IPv4_Address3_UE, px_IPv6_Address3_UE
NOTE 1: Values depending on SS implementation
NOTE 2: The DRB associated with the EPS bearer shall have the DRB ID := EPS Bearer ID – 4.
NOTE 3: Even though for MCX the user plane signalling is handled in TTCN still the SS needs the IP addresses to
be provided to the UE in NAS signalling.

Table 5.2.1-2: PDU session info for NR5GC
PDN Parameter Value/Comment
MCX APN pc_APN_ID_MCX (NOTE 2)
NW IP address px_IPv4_Address1_NW, px_IPv6_Address1_NW (NOTE 3)
UE IP address px_IPv4_Address1_UE, px_IPv6_Address1_UE (NOTE 3)
QFI (NOT
...