|
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 14.2.0 Release 14)
---------------------- Page: 1 ----------------------
3GPP TS 36.579-7 version 14.2.0 Release 14 1 ETSI TS 136 579-7 V14.2.0 (2021-04)
Reference
RTS/TSGR-0536579-7ve20
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 - 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 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
If you find errors in the present document, please send your comment to one of the following services:
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 2021.
All rights reserved.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 36.579-7 version 14.2.0 Release 14 2 ETSI TS 136 579-7 V14.2.0 (2021-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 Web server (https://ipr.etsi.org/).
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™ 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.
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 .
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-7 version 14.2.0 Release 14 3 ETSI TS 136 579-7 V14.2.0 (2021-04)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 6
1 Scope . 7
2 References . 7
3 Definitions of terms, symbols and abbreviations . 9
3.1 Terms . 9
3.2 Symbols . 10
3.3 Abbreviations . 10
4 General . 11
4.1 Test methodology . 11
4.1.1 Testing of optional functions and procedures . 11
4.1.2 Test interfaces and facilities. 11
4.2 Implicit testing . 11
4.3 Repetition of tests . 11
4.4 Handling of differences between conformance requirements in different releases of cores specifications . 11
4.5 Reference conditions . 11
4.6 Generic setup procedures . 12
5 MCData Client Configuration . 12
5.1 Configuration / Authentication / User Authorization / UE Configuration / User Profile / Key Generation . 12
5.2 Configuration / Group Creation / Group ReGroup Creation / Group ReGroup Teardown . 28
5.3 Configuration / Group Affiliation / Remote change / De-affiliation / Home MCData system . 36
5.4 Configuration / Determination of MCData Service Settings / Current Active MCData Settings / De-
subscribe . 56
6 On-Network Test Scenarios . 63
6.1 Short Data Service . 63
6.1.1 On-network / Short Data Service (SDS) / Standalone SDS Using Signalling Control Plane / One-to-
one Standalone SDS / Client Originated (CO) . 63
6.1.2 On-network / Short Data Service (SDS) / Standalone SDS Using Signalling Control Plane / One-to-
one Standalone SDS / Client Terminated (CT) . 76
6.1.3 On-network / Short Data Service (SDS) / Standalone SDS Using Signalling Control Plane / Group
Standalone SDS / Client Originated (CO) . 90
6.1.4 On-network / Short Data Service (SDS) / Standalone SDS Using Signalling Control Plane / Group
Standalone SDS / Client Terminated (CT) . 96
6.1.5 On-network / Short Data Service (SDS) / Standalone SDS Using Media Plane / One-to-one
Standalone SDS / Client Originated (CO) . 102
6.1.6 On-network / Short Data Service (SDS) / Standalone SDS Using Media Plane / One-to-one
Standalone SDS / Client Terminated (CT) . 114
6.1.7 On-network / Short Data Service (SDS) / Standalone SDS Using Media Plane / Group Standalone
SDS / Client Originated (CO) . 126
6.1.8 On-network / Short Data Service (SDS) / Standalone SDS Using Media Plane / Group Standalone
SDS / Client Terminated (CT) . 138
6.1.9 On-network / Short Data Service (SDS) / SDS Session / One-to-one SDS Session / Client Originated
(CO) . 149
6.1.10 On-network / Short Data Service (SDS) / SDS Session / One-to-one SDS Session / Client
Terminated (CT) . 162
6.1.11 On-network / Short Data Service (SDS) / SDS Session / Group SDS Session / Client Originated
(CO) . 176
6.1.12 On-network / Short Data Service (SDS) / SDS Session / Group SDS Session / Client Terminated
(CT) . 192
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 36.579-7 version 14.2.0 Release 14 4 ETSI TS 136 579-7 V14.2.0 (2021-04)
6.2 File Distribution . 205
6.2.1 On-network / File Distribution (FD) / FD Using HTTP / One-to-one Standalone FD / Non-
Mandatory Download / Before TDU2 Timers Expires / FILE DOWNLOAD REQUEST
ACCEPTED / FILE DOWNLOAD COMPLETED / FILE DOWNLOAD REQUEST REJECTED /
FILE DOWNLOAD DEFERRED / Client Originated (CO) . 205
6.2.2 On-network / File Distribution (FD) / FD Using HTTP / One-to-one Standalone FD / Non-
Mandatory Download / Before TDU2 Timers Expires / FILE DOWNLOAD REQUEST
ACCEPTED / FILE DOWNLOAD COMPLETED / FILE DOWNLOAD REQUEST REJECTED /
FILE DOWNLOAD DEFERRED / FD Client Terminated (CT) . 226
6.2.3 On-network / File Distribution (FD) / FD Using HTTP / Group Standalone FD / Non-Mandatory
Download / After TDU2 Timers Expires / FILE DOWNLOAD REQUEST ACCEPTED / FILE
DOWNLOAD COMPLETED / FILE DOWNLOAD REQUEST REJECTED / Client Originated
(CO) . 244
6.2.4 On-network / File Distribution (FD) / FD Using HTTP / Group Standalone FD / Non-Mandatory
Download / After TDU2 Timers Expires / FILE DOWNLOAD REQUEST ACCEPTED / FILE
DOWNLOAD COMPLETED / FILE DOWNLOAD REQUEST REJECTED / Client Terminated
(CT) . 262
6.2.5 On-network / File Distribution (FD) / FD Using HTTP / One-to-one Standalone FD / Mandatory
Download / With Disposition Request / Client Originated (CO) . 277
6.2.6 On-network / File Distribution (FD) / FD Using HTTP / One-to-one Standalone FD / Mandatory
Download / With Disposition Request / Client Terminated (CT) . 292
6.2.7 On-network / File Distribution (FD) / FD Using HTTP / Group Standalone FD / Mandatory
Download / Without Disposition Request / Client Originated (CO) . 303
6.2.8 On-network / File Distribution (FD) / FD Using HTTP / Group Standalone FD / Mandatory
Download / Without Disposition Request / Client Terminated (CT) . 315
6.2.9 On-network / File Distribution (FD) / FD Using Media Plane / One-to-one Standalone FD / Client
Originated (CO) . 323
6.2.10 On-network / File Distribution (FD) / FD Using Media Plane / One-to-one Standalone FD / Client
Terminated (CT) . 336
6.2.11 On-network / File Distribution (FD) / FD Using Media Plane / Group Standalone FD / Client
Originated (CO) . 347
6.2.12 On-network / File Distribution (FD) / FD Using Media Plane / Group Standalone FD / Client
Terminated (CT) . 360
7 Off-Network Test Scenarios . 370
Annex A (informative): Change history . 371
History . 372
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 36.579-7 version 14.2.0 Release 14 5 ETSI TS 136 579-7 V14.2.0 (2021-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
---------------------- Page: 6 ----------------------
3GPP TS 36.579-7 version 14.2.0 Release 14 6 ETSI TS 136 579-7 V14.2.0 (2021-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
---------------------- Page: 7 ----------------------
3GPP TS 36.579-7 version 14.2.0 Release 14 7 ETSI TS 136 579-7 V14.2.0 (2021-04)
1 Scope
The present document specifies the protocol conformance testing for testing a MCData Client for compliance to the
Mission Critical Video (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 mentioned in the
deliverable. This reference is not used within the document and thus shall be removed from references clause.
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.
[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-3: " Mission Critical (MC) services over LTE; Part 3: Mission Critical Push To
Talk (MCPTT) Server Application test specification".
[4] 3GPP TS 36.579-4: " Mission Critical (MC) services over LTE; Part 4: Test Applicability and
Implementation Conformance Statement (ICS).
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 36.579-7 version 14.2.0 Release 14 8 ETSI TS 136 579-7 V14.2.0 (2021-04)
[5] 3GPP TS 36.579-5: "Mission Critical (MC) services over LTE; Part 5: Abstract test suite (ATS)".
[6] 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".
[7] Void
[8] Void
[9] 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; Protocol specification".
[10] Void
[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) over LTE ".
[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.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage
3".
[18] Void
[19] 3GPP TS 36.509: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
Terrestrial Radio Access Network (E-UTRAN); Special conformance testing functions for User
Equipment (UE)".
[20] 3GPP TS 36.508: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
Terrestrial Radio Access (E-UTRAN); Common Test Environments for User Equipment (UE)
Conformance Testing".
[21] OpenID Connect 1.0: "OpenID Connect Core 1.0 incorporating errata set 1",
http://openid.net/specs/openid-connect-core-1_0.html.
[22] 3GPP TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".
[23] Void
[24] 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".
[25] 3GPP TS 36.579-6: "Mission Critical (MC) services over LTE; Part 6: Mission Critical Video
(MCVideo) User Equipment (UE) Protocol conformance specification ".
[26] Void
[27] Void
[28] Void
[29] Void
[30] 3GPP TS 33.180: "Security of the mission critical service".
[31] 3GPP TS 24.282: "Mission Critical Data (MCData) signalling control; Protocol specification".
[32] 3GPP TS 24.582: "Mission Critical Data (MCData) media plane control; Protocol specification".
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 36.579-7 version 14.2.0 Release 14 9 ETSI TS 136 579-7 V14.2.0 (2021-04)
[33] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data
(MCData); Stage 2".
[34] 3GPP TS 22.282: "Mission Critical Data over LTE. Status: Under change control".
[35] Void
[36] IETF RFC 4826 (May 2007): "Extensible Markup Language (XML) Formats for Representing
Resource Lists".
[37] IETF RFC 4122 (July 2005): "A Universally Unique IDentifier (UUID) URN Namespace".
3 Definitions of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in 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].
For the purpose of the present document, the following terms given in TS 23.282 [33] apply:
Auto-receive
Conversation identifier
Data stream
FD disposition
MCData client
MCData group
MCData group affiliation
MCData group communication
MCData group de-affiliation
MCData ID
MCData server
MCData service
MCData UE
MCData user
Reception control
Reply identifier
SDS data
SDS disposition
Standalone communication
Transaction identifier
Transmission control
For the purpose of the present document, the following terms given in TS 22.282 [34] apply:
Conversation
Conversation ID
MCData Conversation Hang Time
MCData System
For the purpose of the present document, the following terms given in 3GPP TS 33.180 [30] apply:
Client Server Key (CSK)
Private Call Key (PCK)
Signalling Protection Key (SPK)
XML Protection Key (XPK)
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 36.579-7 version 14.2.0 Release 14 10 ETSI TS 136 579-7 V14.2.0 (2021-04)
3.2 Symbols
For the purposes of the present document, the following symbols apply
...