ETSI TS 136 579-2 V14.4.0 (2019-10)

TECHNICAL SPECIFICATION
LTE;
Mission Critical (MC) services over LTE;
Part 2: Mission Critical Push To Talk (MCPTT) User Equipment
(UE) Protocol conformance specification
(3GPP TS 36.579-2 version 14.4.0 Release 14)

3GPP TS 36.579-2 version 14.4.0 Release 14 1 ETSI TS 136 579-2 V14.4.0 (2019-10)

Reference
RTS/TSGR-0536579-2ve40
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:
http://www.etsi.org/standards-search
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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
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 2019.
All rights reserved.
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.
ETSI
3GPP TS 36.579-2 version 14.4.0 Release 14 2 ETSI TS 136 579-2 V14.4.0 (2019-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.
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 http://webapp.etsi.org/key/queryform.asp.
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-2 version 14.4.0 Release 14 3 ETSI TS 136 579-2 V14.4.0 (2019-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions, symbols and abbreviations . 9
3.1 Definitions . 9
3.2 Symbols . 9
3.3 Abbreviations . 10
4 General . 10
4.1 Test methodology . 10
4.1.1 Testing of optional functions and procedures . 10
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 . 11
5 MCPTT Client Configuration . 12
5.1 Configuration / Authentication / User Authorisation / UE Configuration / User Profile / Key Generation . 12
5.2 Configuration / Group Creation / Group Regroup Creation / Group Regroup Teardown . 29
5.3 Configuration / Group Affiliation / Remote change / De-affiliation / Home MCPTT system . 36
5.4 Configuration / Pre-established Session Establishment / Pre-established Session Modification / Pre-
established Session Release . 55
6 MCPTT Client on-network operation . 64
6.1 Group Calls . 64
6.1.1 Pre-arranged Group Call . 64
6.1.1.1 On-network / On-demand Pre-arranged Group Call / Automatic Commencement Mode / End-to-
end communication security / Floor Control / Upgrade to Emergency Group Call / Cancel
Emergency State / Upgrade to Imminent Peril Group Call / Cancel Imminent Peril State / Client
Originated (CO) . 64
6.1.1.2 On-network / On-demand Pre-arranged Group Call / Automatic Commencement Mode / Floor
Control / Upgrade to Emergency Group Call / Cancel Emergency State / Upgrade to Imminent
Peril Group Call / Cancel Imminent Peril State / Client Terminated (CT). 92
6.1.1.3 On-network / On-demand Pre-arranged Group Call / Manual Commencement Mode / Client
Originated (CO) . 113
6.1.1.4 On-network / On-demand Pre-arranged Group Call / Manual Commencement Mode / Client
Terminated (CT) . 118
6.1.1.5 On-network / Pre-arranged Group Call using pre-established session / Client originated Pre-
established Session Release with associated MCPTT session / Client Originated (CO) . 126
6.1.1.6 On-network / Pre-arranged Group Call using pre-established session / Automatic
Commencement Mode / Server originated Pre-established Session Release with associated
MCPTT session / Client Terminated (CT) . 130
6.1.1.7 On-network / Pre-arranged Group Call using pre-established session / Manual Commencement
Mode / Client Terminated (CT) . 133
6.1.1.8 On-network / Pre-arranged Broadcast Group Call / Client Originated (CO) . 139
6.1.1.9 On-network / Pre-arranged Broadcast Group Call / Client Terminated (CT) . 143
6.1.1.10 On-network / Broadcast Group Call with Temporary Group / Client Originated (CO) . 146
6.1.1.11 On-network / Pre-arranged Emergency Group Call / Client Originated (CO) . 150
6.1.1.12 On-network / Pre-arranged Emergency Group Call / Client Terminated (CT) . 154
6.1.1.13 On-network / Pre-arranged Imminent Peril Group Call / Client Originated (CO) . 158
ETSI
3GPP TS 36.579-2 version 14.4.0 Release 14 4 ETSI TS 136 579-2 V14.4.0 (2019-10)
6.1.1.14 On-network / Pre-Arranged Imminent Peril Group Call / Client Terminated (CT) . 162
6.1.1.15 On-network / Emergency Alert / Cancel Emergency Alert / Client Originated (CO) . 165
6.1.1.16 On-network / Emergency Alert / Client Terminated (CT) . 170
6.1.2 Chat Group Calls . 175
6.1.2.1 Void. 175
6.1.2.2 On-network / Chat Group Call Using Pre-established Session Including Emergency and
Imminent Peril Calls / Client Server originated Pre-established Session Release with associated
MCPTT session / Client Origination (CO) . 176
6.1.2.3 Void. 185
6.1.2.4 Void. 185
6.1.2.5 Void. 185
6.1.2.6 Void. 185
6.1.2.7 On-network / Chat Group Call / Emergency Group Call / Client Originated (CO) . 185
6.1.2.8 On-network / Chat Group Call / Emergency Group Call / Client Terminated (CT) . 190
6.1.2.9 On-network / Chat Group Call / Imminent Peril Group Call / Client Originated (CO) . 194
6.1.2.10 On-network / Chat Group Call / Imminent Peril Group Call / Client Terminated (CT) . 199
6.1.2.11 On-network / Chat Group Call / Join Chat Group Session / Upgrade to Emergency / Cancel
Emergency / Upgrade to Imminent Peril / Cancel Imminent Peril / Client Originated (CO) . 203
6.1.2.12 On-network / Chat Group Call / Join Chat Group Session / Upgrade to Emergency / Cancel
Emergency / Upgrade to Imminent Peril / Cancel Imminent Peril / Client Originated (CT) . 220
6.2 Private Calls . 232
6.2.1 On-network / Private Call / On-demand / Automatic Commencement Mode / With Floor Control /
Upgrade to Emergency Call / Cancellation of Emergency on User request / Client Originated (CO) . 232
6.2.2 On-network / Private Call / On-demand / Automatic Commencement Mode / With Floor Control /
Upgrade to Emergency Call / Cancellation of Emergency on User request / Client Terminated (CT) . 251
6.2.3 On-network / Private Call / On-demand / Automatic Commencement Mode / Without Floor Control

/ Client Originated (CO) . 266
6.2.4 On-network / Private Call / On-demand / Automatic Commencement Mode / Without Floor Control
/ Client Terminated (CT) . 272
6.2.5 On-network / Private Call / Emergency Private Call / On-demand / Automatic Commencement
Mode / Force of automatic commencement mode / Without Floor Control / Client Originated (CO) . 277
6.2.6 On-network / Private Call / Emergency Private Call / On-demand / Automatic Commencement

Mode / Force of automatic commencement mode / Without Floor Control / Client Terminated (CT) . 285
6.2.7 On-network / Private Call / On-demand / Manual Commencement Mode / Without Floor Control /
Client Originated (CO) . 290
6.2.8 On-network / Private Call / On-demand / Manual Commencement Mode / Without Floor Control /
Client Terminated (CT) . 296
6.2.9 On-network / Private Call / Within a pre-established session / Automatic Commencement Mode /

Without Floor Control / Client Originated (CO). 301
6.2.10 On-network / Private Call / Within a pre-established session / Automatic Commencement Mode /
Without Floor Control / Client Terminated (CT) . 307
6.2.11 On-network / Private Call / Within a pre-established session / Manual Commencement Mode /
Without Floor Control / Release of the Call and the pre-established session / Client Terminated (CT) . 314
6.2.12 On-network / Private Call / Private Call Call-Back Request / Private Call Call-Back Cancel Request

/ Client Originated (CO) / Private call call-back fulfilment . 322
6.2.13 On-network / Private Call / Private Call Call-Back Request / Private Call Call-Back Cancel Request
/ Client Terminated (CT) / Private call call-back fulfilment . 331
6.2.14 On-network / Private Call / Ambient listening call / Remotely initiated Ambient listening call /
Remotely initiated ambient listening call release / Success / Client Originated (CO) / Server initiated
ambient call release . 341
6.2.15 On-network / Private Call / Ambient listening call / Remotely initiated Ambient listening call /
Remotely initiated ambient listening call release / Success / Client Terminated (CT) . 350
6.2.16 On-network / Private Call / Ambient listening call / Locally initiated Ambient listening call / Locally
initiated ambient listening call release / Success / Client Originated (CO) / Server initiated ambient
call release . 355
6.2.17 On-network / Private Call / Ambient listening call / Locally initiated Ambient listening call / Locally
initiated ambient listening call release / Success / Client Terminated (CT) . 363
6.3 Location . 367
6.3.1 On-network / Location / Event Triggered Location Information report . 367
6.3.2 On-network / Location/ On-demand Location Information Request . 379
6.4 MBMS . 394
ETSI
3GPP TS 36.579-2 version 14.4.0 Release 14 5 ETSI TS 136 579-2 V14.4.0 (2019-10)
6.4.1 On-network / MBMS / MBMS Bearer Announcement / MBMS Bearer Listening Status / Transition
to MBMS from Unicast / MBMS Floor Control / Transition to Unicast from MBMS . 394
7 MCPTT Client off-network operation . 413
7.1 Off-network Group Calls . 413
7.1.1 Off-network / Group Call / Floor Control / Upgrade to Emergency Call / Downgrade from
Emergency / Upgrade to Imminent Peril / Downgrade from Imminent Peril / Release Call / Client
Originated (CO) . 413
7.1.2 Off-network / Group Call / Floor Control / Upgrade to Emergency Call / Downgrade from
Emergency / Upgrade to Imminent Peril / Downgrade from Imminent Peril / Release Call / Client
Terminated (CT) . 439
7.1.3 Off-network / Group Call / Leave Group Call when GROUP CALL PROBE sent / Initiate Group
Call for Released Call / Receive GROUP CALL ANNOUNCEMENT for Released call / No
GROUP CALL ANNOUNCEMENT for Released Call / Receive Response to GROUP CALL
PROBE . 464
7.1.4 Off-network / Group Call / MCPTT User Acknowledgement Required / With Confirm Indication /
MCPTT User Reject / MCPTT User Accept / Client Terminated (CT) . 472
7.1.5 Off-network / Group Call / MCPTT User Acknowledgement Required / Without Confirm Indication
/ MCPTT User Reject / MCPTT User Accept / Client Terminated (CT) . 478
7.1.6 Off-network / Group Call / Merge Two Calls . 483
7.1.7 Off-network / Group Call / Emergency Call / Imminent Peril Call / Client Originated (CO) . 490
7.1.8 Off-network / Group Call / Emergency Call / Imminent Peril Call / Client Terminated (CT) . 499
7.1.9 Off-network / Group Call / Emergency Alert / Emergency Alert Retransmission / Cancel Emergency
Alert / Client Originated (CO) . 508
7.1.10 Off-network / Group Call / Emergency Alert / Emergency Alert Retransmission / Cancel Emergency
Alert / Client Terminated (CT) . 512
7.1.11 Off-network / Group Call / Broadcast Group Call / Broadcast Group Call Retransmitting / Broadcast
Group Call Release / Client Originated (CO) . 517
7.1.12 Off-network / Group Call / Broadcast Group Call / MCPTT User Ack Not Required / Originator
Releases Call / Client Terminated (CT) . 522
7.1.13 Off-network / Group Call / Broadcast Group Call / MCPTT User Ack Required / MCPTT User
Reject / MCPTT User Accept / MCPTT User Releases Call / Client Terminated (CT) . 525
7.2 Off-network Private Calls . 531
7.2.1 Off-network / Private Call / On-demand / Automatic Commencement Mode / No Response to
Private Call Setup Request / Private call setup success / With Floor Control / Upgrade to Emergency
Call / Cancellation of Emergency on User request / Client Originated (CO) . 531
7.2.2 Off-network / Private Call / On-demand / Automatic Commencement Mode / No Response to
Private Call Setup Accept / Private call setup success / With Floor Control / Upgrade to Emergency
Call / Cancellation of Emergency on User request / Client Terminated (CT) . 549
7.2.3 Off-network / Private Call / On-demand / Automatic Commencement Mode / Upgrade to
Emergency Call Reject / Downgrade from Emergency Call Failure / Client Originated (CO) . 566
7.2.4 Off-network / Private Call / On-demand / Manual Commencement Mode / Call Released before
establishment completion / Call request Rejected / Call establishment successful / Client Originated
(CO) . 575
7.2.5 Off-network / Private Call / On-demand / Manual Commencement Mode / Call Released before
establishment completion / User does not answer to Ringing / User Rejects call request / Call
establishment successful / Client Terminated (CT) . 584
Annex A (informative): Change history . 595
History . 600

ETSI
3GPP TS 36.579-2 version 14.4.0 Release 14 6 ETSI TS 136 579-2 V14.4.0 (2019-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 2 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; Part 1: Common test environment"
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" (the present document);
3GPP TS 36.579-3 [3]: " Mission Critical (MC) services over LTE; Part 3: Mission Critical Push To Talk
(MCPTT) Server Application conformance specification";
3GPP TS 36.579-4 [4]: "Mission Critical (MC) services over LTE; Part 4: Test Applicability and
Implementation Conformance Statement (ICS) proforma specification";
3GPP TS 36.579-5 [5]: "Mission Critical (MC) services over LTE; Part 5: Abstract test suite (ATS)".
ETSI
3GPP TS 36.579-2 version 14.4.0 Release 14 7 ETSI TS 136 579-2 V14.4.0 (2019-10)
1 Scope
The present document specifies the protocol conformance testing for testing a MCPTT Client for compliance to the
Mission Critical Push To Talk (MCPTT) 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 MCPTT 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 MCPTT data sent or received by the MCPTT
Client and which are required to be supported by the UE in which the MCPTT Client is installed. This is defined in
TS 36.523-1 [6].
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).
[5] 3GPP TS 36.579-5: "Mission Critical (MC) services over LTE; Part 5: Abstract test suite (ATS)".
ETSI
3GPP TS 36.579-2 version 14.4.0 Release 14 8 ETSI TS 136 579-2 V14.4.0 (2019-10)
[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] 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) media plane 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) 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] Void.
[18] Void.
[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] Void.
[22] Void.
[23] 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)".
[24] 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".
[25] OpenID Connect 1.0: "OpenID Connect Core 1.0 incorporating errata set 1",
http://openid.net/specs/openid-connect-core-1_0.html.
[26] Void.
[27] Void
[28] Void.
[29] Void.
[30] 3GPP TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".
[31] Void.
[32] 3GPP TS 23.003: "Numbering, addressing and identification".
ETSI
3GPP TS 36.579-2 version 14.4.0 Release 14 9 ETSI TS 136 579-2 V14.4.0 (2019-10)
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].
For the purpose of the present document, the following terms and definitions given in 3GPP TS 24.379 [9] apply:
An MCPTT user is affiliated to an MCPTT group
An MCPTT user is affiliated to an MCPTT group at an MCPTT client
Affiliation status
Group identity
In-progress emergency private call state
In-progress imminent peril group state
MCPTT client ID
MCPTT emergency alert state
MCPTT emergency group state
MCPTT emergency group call state
MCPTT emergency private call state
MCPTT emergency private priority state
MCPTT imminent peril group call state
MCPTT imminent peril group state
MCPTT private emergency alert state
MCPTT speech
Media-floor control entity
Temporary MCPTT group identity
Trusted mutual aid
Untrusted mutual aid
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.179 [7] apply:
In-progress emergency
MCPTT emergency alert
MCPTT emergency group call
MCPTT emergency state
Partner MCPTT system
Primary MCPTT system
For the purpose of the present document, the following terms and definitions given in 3GPP TS 24.380 [10] apply:
MBMS subchannel
For the purpose of the present document, the following terms and definitions given in 3GPP TS 23.179 [8] apply:
Pre-selected MCPTT user profile

3.2 Symbols
For the purposes of the present document, the following symbols apply:
None.
ETSI
3GPP TS 36.579-2 version 14.4.0 Release 14 10 ETSI TS 136 579-2 V14.4.0 (2019-10)
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].
ECGI E-UTRAN Cell Global Identification
FFS For Further Study
ICS Implementation Conformance Statement
IPEG In-Progress Emergency Group
IPEPC In-Progress Emergency Private Call
IPIG In-Progress Imminent peril Group
IUT Implementation Under Test
IXIT Implementation eXtra Information for Testing
MBMS Multimedia Broadcast and Multicast Service
MBSFN Multimedia Broadcast multicast service Single Frequency Network
MCPTT Mission Critical Push To Talk
MCPTT group ID MCPTT group IDentity
MEA MCPTT Emergency Alert
MEG MCPTT Emergency Group
MEGC MCPTT Emergency Group Call
MEPC MCPTT Emergency Private Call
MEPP MCPTT Emergency Private Priority
MES MCPTT Emergency State
MIME Multipurpose Internet Mail Extensions
MIG MCPTT Imminent peril Group
MIGC MCPTT Imminent peril Group Call
MONP MCPTT Off-Network Protocol
MPEA MCPTT Private Emergency Alert
NAT Network Address Translation
PLMN Public Land Mobile Network
QCI QoS Class Identifier
RTP Real-time Transport Protocol
SAI Service Area Identifier
SDP Session Description Protocol
SIP Session Initiation Protocol
SS System Simulator
SSRC Synchronization SouRCe
TGI Temporary MCPTT Group Identity
TMGI Temporary Mobile Group Identity
TP Transmission Point
TP Test Purpose
UE User Equipment
URI Uniform Resource Identifier
4 General
4.1 Test methodology
4.1.1 Testing of optional functions and procedures
Any function or procedure which is optional, may be subject to a conformance test if it is implemented in the MCPTT
Client.
A declaration by the MCPTT Client supplier (to use the Implementation Conformance Statement (ICS) proforma
specified in TS 36.579-4 [4]) is used to determine whether an optional function/procedure has been implemented.
ETSI
3GPP TS 36.579-2 version 14.4.0 Release 14 11 ETSI TS 136 579-2 V14.4.0 (2019-10)
4.1.2 Test interfaces and facilities
Detailed descriptions of the MCPTT Client test interfaces and special facilities for testing are provided in 3GPP
TS 36.509 [23].
4.2 Implicit testing
For some 3GPP MCPTT protocol features conformance is not verified explicitly in the present document. This does not
imply that correct functioning of these features is not essential, but that these are implicitly tested to a sufficient degree
in tests which are not explicitly dedicated to test the feature.
4.3 Repetition of tests
As a general rule, the test cases specified in the present document are highly reproducible and do not need to be
repeated unless otherwise stated.
4.4 Handling of differences between conformance requirements
in different releases of cores specifications
The conformance requirements which determine the scope of each test case are explicitly copy-pasted from relevant
core specifications in the especially dedicated for this clause of each test with the title 'Conformance requirements'.
NOTE: When in the copy/pasted text there are references to other specifications the reference numbers will not
match the reference numbers used in the present document. This approach has been taken in order to
allow easy copy and then search for conformance requirements in those specifications.
When differences between conformance requirements in different releases of the cores specifications have impact on
the Pre-test conditions, Test procedure sequence or/and the Specific message contents, the Conformance requirements
related to different releases are specified separately with clear indication of the Release of the spec from which they
were copied.
When there is no Release indicated for a conformance requirement text, this should be understood either as the
Conformance requirements in the latest version of the spec with release = the TC Applicability release (which can be
found in TS 36.579-4 [4], Table 4-1: Applicability of tests and additional information for testing, column 'Release'), or,
as the Conformance requirements in the latest version of the spec of the release when the feature was introduced to the
core specs.
4.5 Reference conditions
The reference environments used by all signalling and protocol tests is specified in TS 36.579-1 [2]. Where a test
requires an environment that is different, this will be specified in the test itself.
4.6 Generic setup procedures
A set of basic generic procedures for MCPTT Client-Server communication are described in TS 36.579-1 [2]. These
procedures will be used in numerous test cases throughout the present document.
ETSI
3GPP TS 36.579-2 version 14.4.0 Release 14 12 ETSI TS 136 579-2 V14.4.0 (2019-10)
5 MCPTT Client Configuration
5.1 Configuration / Authentication / User Authorisation / UE
Configuration / User Profile / Key Generation
5.1.1 Test Purpose (TP)
(1)
with { UE (MCPTT Client) attached to EPS services }
ensure that {
when { the MCPTT User activates an MCPTT application and requests MCPTT initialisation }
then { UE (MCPTT Client) performs MCPTT User Authentication }
}
(2)
with { UE (MCPTT Client) user authenticated }
ensure that {
when { the UE (MCPTT Client) has established a secure HTPP tunnel }
then { UE (MCPTT Client) performs key management authorization and obtains identity management
key material }
}
(3)
with { UE (MCPTT Client) has obtained identity management key material }
ensure that {
when { the UE (MCPTT Client) requests user service authorization }
then { UE (MCPTT Client) sends a user authorization request to the MCPTT Server }
}
(4)
with { UE (MCPTT Client) authorized for user services }
ensure that {
when { the UE (MCPTT Client) requests configuration management authorization}
then { UE (MCPTT Client) requests subscription to multiple documents simultaneously and request
the retrieval of the MCPTT UE Configuration document, the MCPTT User Profile Configuration Document
and the MCPTT Service Configuration Document }
}
(5)
with { UE (MCPTT Client) having obtained user configuration data }
ensure that {
when { the UE (MCPTT Client) requests group management authorization }
then { UE (MCPTT Client) receives the group profile including group traffic keys }
}
(6)
with { UE (MCPTT Client) having obtained all required configuration data }
ensure that {
when { the UE (MCPTT Client) requires to refresh its service settings }
then { UE (MCPTT Client) sends a SIP PUBLISH request }
}
ETSI
3GPP TS 36.579-2 version 14.4.0 Release 14 13 ETSI TS 136 579-2 V14.4.0 (2019-10)
5.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TR 24.980 clauses 4.2.1 and
4.3.1, TS 24.482 clause 6.2.1 and Annex A.2.1.2, TS 24.484 clauses 4.2.1, 4.2.2, 6.2.2, 6.3.1.1, 6.3.2.1, 6.3.2.2,
6.3.13.2.1 and 6.3.13.2.2, TS 24.481 clauses 6.2.2.2, 6.2.3, 6.3.3.2.1, 6.3.3.2.2 and 6.3.13.2.1, TS 24.379 clauses 7.2.1,
7.2.1A, 7.2.2 and 7.2.3, TS 33.179 clauses 5.6.1, 6.2, 7.2.3 and Annex D. Unless otherwise stated these are Rel-13
requirements.
[TR 24.980, clause 4.2.1]
The MCPTT UE follows the SIP registration procedures defined in 3GPP TS 24.229 [4]. In addition, when the
conditions for performing IMS registration in bullets 2, 3, 4, 5 and 6 in subclause L.3.1.2 of 3GPP TS 24.229 [4]
evaluate to true, the MCPTT UE registers with the IMS.
[TR 24.980, clause 4.3.1]
The MCPTT UE follows the procedures defined in 3GPP TS 24.229 [4] and 3GPP TS 33.203 [7] for authentication
with IMS Authentication and Key Agreement (IMS-AKA), Sec-Agree and IPSec. The MCPTT UE supports integrity
protection.
[TS 24.482, clause 6.2.1]
Upon an indication from the MCPTT client to initiate MCPTT user authentication, the IdM client shall perform the user
authentication procedure according to 3GPP TS 33.179 [2] with the following clarifications:
1) shall establish a TLS tunnel to the authorisation endpoint of the IdM server as specified in 3GPP TS 33.179 [2]
using the configured URL of the authorisation endpoint of the IdM server as specified in the
"//OnNetwork/AppServerInfo/IDMSAuthEndpoint" leaf node defined in 3GPP TS 24.383 [11] and the
clarifications in annex A;
2) shall generate an OIDC Authentication Request message as specified in the OpenID Connect 1.0 [6] and
IETF RFC 6749 [5] with the following clarifications:
a) shall generate an HTTP GET request method according to IETF RFC 2616 [4];
b) shall include the configured parameter IdM client id as the client_id parameter specified in
3GPP TS 33.179 [2] in the query component of the authorization endpoint’s URI using the "application/x-
www-form-urlencoded" format as specified in W3C.REC-html401-19991224 [7]; and
NOTE 1: The configuration of client_id is specified in 3GPP TS 24.383 [11].
c) shall include the remaining required parameters as specified in 3GPP TS 33.179 [2] in the query component
of the authorization endpoint’s URI using the "application/x-www-form-urlencoded" format as specified in
W3C.REC-html401-19991224 [7]; and
3) shall send the HTTP GET request method towards the IdM server.
NOTE 2: The OpenID Connect 1.0 [6] specification allows for an alternative mechanism for sending the OIDC
Authentication request message using an HTTP POST request method which can be used in place of steps
1, 2, and 3 above.
Upon receipt of an HTTP 200 (OK) response from the IdM server, the IdM client:
1) shall prompt the MCPTT user for their username and password;
NOTE 3: Other types of authentication are supported and are not defined by the OIDC specifications.
3GPP TS 33.179 [2] has defined username and password as a mandatory authentication method to be
supported; hence a procedure to realize that method is included here.
2) shall generate an HTTP POST request method containing the MCPTT user's username and password; and
3) shall send the HTTP POST request method towards the IdM server.
Upon receipt of an OIDC Authentication Response message, the IdM client:
ETSI
...