ETSI TS 124 282 V18.13.0 (2026-03)

LTE; Mission Critical Data (MCData) signalling control; Protocol specification (3GPP TS 24.282 version 18.13.0 Release 18)

RTS/TSGC-0124282vid0

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 1 - MM/CC/SM [lu] (formely CN1)
• Current Stage: 8 - Draft receipt by ETSI Secretariat
• Completion Date: 10-Mar-2026

Standards Content (Sample)

TECHNICAL SPECIFICATION
LTE;
Mission Critical Data (MCData) signalling control;
Protocol specification
(3GPP TS 24.282 version 18.13.0 Release 18)

3GPP TS 24.282 version 18.13.0 Release 18 1 ETSI TS 124 282 V18.13.0 (2026-03)

Reference
RTS/TSGC-0124282vid0
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 2026.
All rights reserved.
ETSI
3GPP TS 24.282 version 18.13.0 Release 18 2 ETSI TS 124 282 V18.13.0 (2026-03)
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 24.282 version 18.13.0 Release 18 3 ETSI TS 124 282 V18.13.0 (2026-03)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 25
1 Scope . 27
2 References . 27
3 Definitions, symbols and abbreviations . 30
3.1 Definitions . 30
3.2 Abbreviations . 32
4 General . 33
4.1 MCData overview . 33
4.2 Identity, URI and address assignments . 34
4.2.1 Public Service identi ties . 34
4.2.2 MCData session identity . 34
4.2.3 MCData client ID . 35
4.3 Pre-established sessions . 35
4.4 Emergency Alerts . 35
4.5 MCData Protocol . 36
4.6 Protection of sensitive XML application data . 36
4.7 Protection of TLV signalling and media content . 39
4.7A Signalling security when using MBMS . 39
4.8 MCData client ID . 40
4.9 Warning Header Field . 40
4.9.1 General . 40
4.9.2 Warning texts . 41
4.10 MCData emergency groups and emergency group communications . 46
4.11 MCData imminent peril group communications . 46
4.12 MCData emergency private communications . 47
4.13 MCData Resource Management . 48
5 Functional entities . 49
5.1 Introduction . 49
5.2 MCData client . 49
5.3 MCData server . 50
5.3.0 General . 50
5.3.1 SIP failure case . 51
5.3.1A SIP provisional response . 51
5.3.2 Management of MBMS bearers . 52
5.3.3 Management of MBS sessions . 52
5.4 MCData gateway server . 52
5.4.1 General . 52
5.5 MCData gateway UE . 53
5.5.1 General . 53
5.5.2 Functional connectivity models . 53
5.5.3 QoS for MCData gateway UE . 54
6 Common procedures. 54
6.1 Introduction . 54
6.2 MCData client procedures . 54
6.2.1 Distinction of requests at the MCData client . 54
6.2.1.1 SIP MESSAGE request . 54
6.2.1.2 SIP INVITE request . 56
6.2.2 MCData conversation items . 56
6.2.2.1 Generating an SDS Message . 56
ETSI
3GPP TS 24.282 version 18.13.0 Release 18 4 ETSI TS 124 282 V18.13.0 (2026-03)
6.2.2.2 Generating an FD Message for FD using HTTP . 58
6.2.2.3 Generating an FD Message for FD using media plane . 58
6.2.2.4 Client generating message to terminate FD over HTTP. 59
6.2.3 Disposition Notifications . 60
6.2.3.1 Generating an SDS Notification . 60
6.2.3.2 Generating an FD Notification . 60
6.2.4 Sending SIP requests and receiving SIP responses . 61
6.2.4.1 Generating a SIP MESSAGE request towards the originating participating MCData function . 61
6.2.5 Location information . 62
6.2.5.1 Location information for location reporting . 62
6.2.6 Void . 63
6.2.7 Handling of in-progress emergency and imminent peril conditions . 63
6.2.7.1 MCData upgrade to in-progress emergency or in-progress imminent peril . 63
6.2.7.2 MCData in-progress emergency cancel . 64
6.2.7.3 MCData in-progress imminent peril cancel . 65
6.2.7.4 MCData client receives SIP re-INVITE request . 66
6.2.7.5 MCData group in-progress emergency group state cancel . 68
6.2.8 Priority communication conditions . 69
6.2.8.1 MCData emergency group communication and imminent peril communication conditions . 69
6.2.8.1.1 SIP INVITE request or SIP REFER request for originating MCData emergency group

communications . 69
6.2.8.1.2 Resource-Priority header field for MCData emergency group communications . 70
6.2.8.1.3 SIP re-INVITE request for cancelling MCData in-progress emergency group state . 71
6.2.8.1.4 Receiving a SIP 2xx response to a SIP request for a priority communication. 72
6.2.8.1.5 Receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to a SIP request for a
priority group communication . 72
6.2.8.1.6 Determining authorisation for initiating or cancelling an MCData emergency alert . 73
6.2.8.1.7 Determining authorisation for cancelling the in-progress emergency state of an MCData
group . 73
6.2.8.1.8 Determining authorisation for originating a priority group communication . 73
6.2.8.1.9 SIP request for originating MCData imminent peril group communications . 74
6.2.8.1.10 Determining authorisation for cancelling an imminent peril group communication . 75
6.2.8.1.11 SIP re-INVITE request for cancelling MCData in-progress imminent peril group state . 75
6.2.8.1.12 Resource-Priority header field for MCData imminent peril group communications . 75
6.2.8.1.13 Receiving a SIP INFO request in the dialog of a SIP request for a priority group
communication . 76
6.2.8.1.14 SIP re-INVITE request for cancelling the in-progress emergency group state of a group by a
third-party . 76
6.2.8.1.15 Retrieving Resource-Priority header field values . 77
6.2.8.1.16 Handling receipt of a SIP re-INVITE request for priority group communication origination
status within a pre-established session . 78
6.2.8.1.17 Priority group communication conditions upon receiving communication release . 78
6.2.8.1.18 Emergency private (one-to-one) communication conditions upon receiving communication
release . 79
6.2.8.1.19 Determining authorisation for initiating or cancelling an MCData adhoc group emergency
alert . 79
6.2.8.2 Void. 80
6.2.8.3 MCData emergency private (one-to-one) communication conditions . 80
6.2.8.3.1 Authorisations . 80
6.2.8.3.2 SIP request for originating MCData emergency private communications . 81
6.2.8.3.3 Resource-Priority header field for MCData emergency private communications . 81
6.2.8.3.4 Receiving a SIP 2xx response to a SIP request for an MCData emergency private
communication . 82
6.2.8.3.5 Receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to a SIP request for an
MCData emergency private communication . 82
6.2.8.3.6 SIP re-INVITE request for cancelling MCData emergency private communication state . 82
6.2.8.3.7 Receiving a SIP INFO request in the dialog of a SIP request for a priority private
communication . 83
6.2.8.3.8 SIP re-INVITE request for cancelling the MCData emergency private communication state
by a third-party . 84
6.2.8.3.9 Retrieving a KMS URI associated with an MCData ID . 84
6.2.8.4 Procedures for modifying ongoing communications . 85
ETSI
3GPP TS 24.282 version 18.13.0 Release 18 5 ETSI TS 124 282 V18.13.0 (2026-03)
6.2.8.4.1 Cancelling or ending ongoing client terminating procedures . 85
6.2.8.4.2 Client terminating procedures for handling SIP re-INVITE for an existing one-to-one

communication session . 85
6.2.8.4.3 MCData in-progress emergency one-to-one communication cancellation . 87
6.2.8.4.4 Upgrade to MCData emergency one-to-one communication . 88
6.3 MCData server procedures . 88
6.3.1 Distinction of requests at the MCData server . 88
6.3.1.1 SIP MESSAGE request . 88
6.3.1.2 SIP INVITE request . 93
6.3.1.3 SIP SUBSCRIBE request . 95
6.3.2 Sending SIP requests and receiving SIP responses . 95
6.3.2.1 Generating a SIP MESSAGE request towards the terminating MCData client . 95
6.3.2.2 Generating a SIP MESSAGE request towards the controlling MCData function . 96
6.3.2.3 Generating a SIP NOTIFY request . 96
6.3.3 Retrieving a group document . 97
6.3.4 Determining targeted group members for MCData communications . 98
6.3.5 Affiliation check . 98
6.3.6 MCData conversation items . 98
6.3.6.1 Server generating a FD HTTP TERMINATION message for FD over HTTP . 98
6.3.7 Procedures referenceable from other procedures . 99
6.3.7.1 Emergency alert and emergency communications procedures . 99
6.3.7.1.1 Sending a SIP re-INVITE request for MCData emergency alert or emergency group
communication . 99
6.3.7.1.2 Generating a SIP MESSAGE request for notification of in-progress emergency status change . 100
6.3.7.1.3 Populate mcdata-info and location-info MIME bodies for emergency alert . 100
6.3.7.1.4 Retrieving Resource-Priority header field values for emergency communications . 101
6.3.7.1.5 Generating a SIP MESSAGE request to indicate successful receipt of an emergency alert or
emergency cancellation . 101
6.3.7.1.6 Generating a SIP MESSAGE request for notification of entry into or exit from an emergency
alert area . 102
6.3.7.1.7 Generating a SIP MESSAGE request for notification of entry into or exit from a group
geographic area . 103
6.3.7.1.8 Sending a SIP re-INVITE request for MCData imminent peril group communication . 104
6.3.7.1.9 Validate priority request parameters . 104
6.3.7.1.10 Sending a SIP INFO request in the dialog of a SIP request for a priority communication . 105
6.3.7.1.11 Sending a SIP INVITE request for MCData emergency group communication . 105
6.3.7.1.12 Sending a SIP UPDATE request for Resource-Priority header field correction. 107
6.3.7.1.13 Generating a SIP re-INVITE request . 107
6.3.7.1.14 Generating a SIP re-INVITE request to cancel an in-progress emergency . 108
6.3.7.1.15 Receipt of SIP re-INVITE request by terminating participating function . 108
6.3.7.1.16 Generating a SIP re-INVITE request for emergency private (one-to-one) communication
origination within a pre-established session . 109
6.3.7.1.17 Receiving a SIP re-INVITE request by the terminating participating function . 110
6.3.7.1.18 Receipt of SIP re-INVITE for MCData one-to-one communication from the served user . 110
6.3.7.1.19 Controlling MCData function receiving a SIP re-INVITE for upgrade to emergency one-to-
one communication . 111
6.3.7.1.20 Controlling MCData function receiving a SIP re-INVITE for cancellation of emergency one-
to-one communication . 112
6.3.7.1.21 Controlling MCData function sending a SIP re-INVITE for upgrade to emergency one-to-one
communication . 114
6.3.7.1.22 Controlling MCData function sending a SIP re-INVITE for cancellation of emergency one-
to-one communication . 114
6.3.7.1.23 Controlling MCData function generates a SIP 200 (OK) response . 115
6.3.7.1.24 Populate mcdata-info and location-info MIME bodies for adhoc group emergency alert . 116
6.3.7.1.25 Generating a SIP MESSAGE request to containing the participant lists of an MCData adhoc
group emergency alert . 117
6.3.7.2 Authorisations . 117
6.3.7.2.1 Determining authorisation for initiating an MCData emergency alert . 117
6.3.7.2.2 Determining authorisation for cancelling an MCData emergency alert . 118
6.3.7.2.3 Determining authorisation for cancelling an MCData emergency communication . 119
6.3.7.2.4 Determining authorisation for initiating an MCData imminent peril communication . 119
6.3.7.2.5 Determining authorisation for cancelling an MCData imminent peril communication . 120
ETSI
3GPP TS 24.282 version 18.13.0 Release 18 6 ETSI TS 124 282 V18.13.0 (2026-03)
6.3.7.2.6 Determining authorisation for initiating an MCData emergency group or private
communication . 120
6.3.7.2.7 Generating a SIP 403 response for priority communication request rejection . 121
6.3.7.2.8 Determining authorisation for initiating an MCData adhoc group emergency alert . 121
6.3.7.2.9 Determining authorisation for cancelling an MCData adhoc group emergency alert . 122
6.3.7.2.10 Determining MCData users that are authorized for receiving MCData adhoc group
emergency alert participant information . 122
6.3.8 Disposition Notifications . 122
6.3.8.1 Generating an FD Notification . 122
6.4 Handling of MIME bodies in a SIP message. 123
6.5 Confidentiality and Integrity Protection of sensitive XML content . 124
6.5.1 General . 124
6.5.1.1 Applicability and exclusions . 124
6.5.1.2 Performing XML content encryption . 124
6.5.1.3 Performing integrity protection on an XML body . 124
6.5.1.4 Verifying integrity of an XML body and decrypting XML elements . 124
6.5.2 Confidentiality Protection . 125
6.5.2.1 General . 125
6.5.2.2 Keys used in confidentiality protection procedures . 125
6.5.2.3 Procedures for sending confidentiality protected content . 125
6.5.2.3.1 MCData client . 125
6.5.2.3.2 MCData server. 125
6.5.2.3.3 Content Encryption in XML elements . 126
6.5.2.3.4 Attribute URI Encryption . 126
6.5.2.4 Procedures for receiving confidentiality protected content . 126
6.5.2.4.1 Determination of confidentiality protected content . 126
6.5.2.4.2 Decrypting confidentiality protected content in XML elements . 127
6.5.2.4.3 Decrypting confidentiality protected URIs in XML attributes . 127
6.5.2.5 MCData server copying received XML content . 127
6.5.3 Integrity Protection of XML documents . 128
6.5.3.1 General . 128
6.5.3.2 Keys used in integrity protection procedures . 129
6.5.3.3 Sending integrity protected content . 130
6.5.3.3.1 MCData client . 130
6.5.3.3.2 MCData server. 130
6.5.3.3.3 Integrity protection procedure . 130
6.5.3.4 Receiving integrity protected content. 131
6.5.3.4.1 Determination of integrity protected content . 131
6.5.3.4.2 Verification of integrity protected content. 131
6.6 Confidentiality and Integrity Protection of TLV messages . 131
6.6.1 General . 131
6.6.2 Derivation of master keys for media and media control . 132
6.6.3 Protection of MCData Data signalling and MCData Data messages . 133
6.6.3.1 General . 133
6.6.3.2 The MCData client . 133
6.6.3.3 The participating MCData function . 133
6.6.3.4 The controlling MCData function . 133
6.7 Stored files operational procedures . 134
6.7.1 General . 134
6.7.2 Retrieve the stored file procedure . 134
6.7.2.1 General client procedures . 134
6.7.2.2 General server procedures . 134
6.7.3 Verify the stored file availability procedure . 135
6.7.3.1 General client procedures . 135
6.7.3.2 General server procedures . 135
6.8 Procedures at the MCData gateway. 135
6.8.1 General . 135
6.8.2 MCData gateway server acting as an exit point from an MCData system . 136
6.8.3 MCData gateway server acting as an entry point in an MCData system . 136
6.8.4 Local policies enforcement . 136
7 Registration and service authorisation . 137
ETSI
3GPP TS 24.282 version 18.13.0 Release 18 7 ETSI TS 124 282 V18.13.0 (2026-03)
7.1 General . 137
7.2 MCData client procedures . 137
7.2.1 SIP REGISTER request for service authorisation . 137
7.2.1AA SIP REGISTER request without service authorisation . 139
7.2.1A Common SIP PUBLISH procedure . 139
7.2.2 SIP PUBLISH request for service authorisation and MCData service settings . 140
7.2.3 Sending SIP PUBLISH for MCData service settings only . 141
7.2.4 Determination of MCData service settings . 141
7.2.5 Receiving a CSK key download message . 142
7.3 MCData server procedures . 143
7.3.1 General . 143
7.3.1A Confidentiality and Integrity Protection . 143
7.3.2 SIP REGISTER request for service authorisation . 145
7.3.3 SIP PUBLISH request for service authorisation and service settings . 146
7.3.4 Receiving SIP PUBLISH request for MCData service settings only . 147
7.3.5 Receiving SIP PUBLISH request with "Expires=0" . 148
7.3.6 Subscription to and notification of MCData service settings . 149
7.3.6.1 Receiving subscription to MCData service settings . 149
7.3.6.2 Sending notification of change of MCData service settings . 149
7.3.7 Sending a CSK key download message . 149
7A Migration procedures . 150
7A.1 General . 150
7A.2 MCData client procedures . 150
7A.2.1 SIP REGISTER request for migration service authorization . 150
7A.2.2 Receiving a CSK key download message . 152
7A.2.3 Receiving a SIP MESSAGE for migration service deauthorization notification . 152
7A.3 Partner MCData server procedures . 152
7A.3.1 General . 152
7A.3.2 Confidentiality and integrity protection . 152
7A.3.3 SIP REGISTER request for initial authorization . 153
7A.3.4 Sending a CSK key download message . 154
7A.3.5 SIP MESSAGE request for migration service authorization response . 154
7A.3.6 Sending SIP MESSAGE for MCData service authorization notification . 154
7A.3.6 SIP
...