ETSI TS 136 579-7 V16.7.0 (2025-04)

LTE; Mission Critical (MC) services over LTE; Part 7: Mission Critical Data (MCData) User Equipment (UE) Protocol conformance specification (3GPP TS 36.579-7 version 16.7.0 Release 16)

RTS/TSGR-0536579-7vg70

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: 03-Apr-2025

Standards Content (Sample)

TECHNICAL SPECIFICATION
LTE;
Mission Critical (MC) services over LTE;
Part 7: Mission Critical Data (MCData) User Equipment (UE)
Protocol conformance specification
(3GPP TS 36.579-7 version 16.7.0 Release 16)

3GPP TS 36.579-7 version 16.7.0 Release 16 1 ETSI TS 136 579-7 V16.7.0 (2025-04)

Reference
RTS/TSGR-0536579-7vg70
Keywords
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 2025.
All rights reserved.
ETSI
3GPP TS 36.579-7 version 16.7.0 Release 16 2 ETSI TS 136 579-7 V16.7.0 (2025-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 36.579-7 version 16.7.0 Release 16 3 ETSI TS 136 579-7 V16.7.0 (2025-04)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 4
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions of terms, symbols and abbreviations . 6
4 General . 7
4.1 Test methodology . 7
5 to 7 Void . 7
Annex A (normative): Void . 8
Annex B (informative): Change history . 9
History . 12

ETSI
3GPP TS 36.579-7 version 16.7.0 Release 16 4 ETSI TS 136 579-7 V16.7.0 (2025-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.
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
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
ETSI
3GPP TS 36.579-7 version 16.7.0 Release 16 5 ETSI TS 136 579-7 V16.7.0 (2025-04)
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.
Introduction
The present document is part 7 of a multi-part deliverable covering conformance test specification for Mission Critical
Services over LTE consisting of:
3GPP TS 36.579-1 [2]: "Mission Critical (MC) services over LTE protocol conformance testing; Part 1:
Common test environment"
3GPP TS 36.579-2 [24]: " 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 [3]: " Mission Critical (MC) services over LTE; Part 3: Mission Critical Push To Talk
(MCPTT) Server Application test specification";
3GPP TS 36.579-4 [4]: " Mission Critical (MC) services over LTE; Part 4: Test Applicability and
Implementation Conformance Statement (ICS)";
3GPP TS 36.579-5 [5]: " Mission Critical (MC) services over LTE; Part 5: Abstract test suite (ATS)";
3GPP TS 36.579-6 [25]: " Mission Critical (MC) services over LTE; Part 6: Mission Critical Video (MCVideo)
User Equipment (UE) Protocol conformance specification";
3GPP TS 36.579-7: " Mission Critical (MC) services over LTE; Part 7: Mission Critical Data (MCData)
User Equipment (UE) Protocol conformance specification" (the present document).
ETSI
3GPP TS 36.579-7 version 16.7.0 Release 16 6 ETSI TS 136 579-7 V16.7.0 (2025-04)
1 Scope
The present document specifies the protocol conformance testing for testing a MCData Client for compliance to the
Mission Critical Data (MCData) over LTE protocol requirements defined by 3GPP.
In particular the present document contains:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The present document is valid for MCData Clients implemented according to 3GPP releases starting from Release 13
up to the Release indicated on the cover page of the present document.
The following information relevant to testing specified in the present document could be found in accompanying
specifications:
- default setting of the test parameters TS 36.579-1 [2];
- Implementation Conformance Statement (ICS) TS 36.579-4 [4] and Implementation eXtra Information for
Testing (IXIT) TS 36.579-5 [5];
- the applicability of each test case TS 36.579-4 [4].
The test cases are expected to be executed through the 3GPP radio interface. The present document does not specify the
protocol conformance testing for the EPS (LTE) bearers which carry the MCData data sent or received by the MCData
Client and which are required to be supported by the UE in which the MCData Client is installed. This is defined in
TS 36.523-1 [6].
According to 3GPP drafting rules, the references clause shall list only documents that are explicitly ment
...