|
TECHNICAL SPECIFICATION
LTE;
Mission Critical Data (MCData) signalling control;
Protocol specification
(3GPP TS 24.282 version 15.3.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 24.282 version 15.3.0 Release 15 1 ETSI TS 124 282 V15.3.0 (2018-10)
Reference
RTS/TSGC-0124282vf30
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:
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 only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
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:
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 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 24.282 version 15.3.0 Release 15 2 ETSI TS 124 282 V15.3.0 (2018-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.
Foreword
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, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 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 24.282 version 15.3.0 Release 15 3 ETSI TS 124 282 V15.3.0 (2018-10)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 13
1 Scope . 14
2 References . 14
3 Definitions, symbols and abbreviations . 16
3.1 Definitions . 16
3.2 Abbreviations . 16
4 General . 16
4.1 MCData overview . 16
4.2 Identity, URI and address assignments . 17
4.2.1 Public Service identi ties . 17
4.2.2 MCData session identity . 17
4.2.3 MCData client ID . 18
4.3 Pre-established sessions . 18
4.4 Emergency Alerts . 18
4.5 MCData Protocol . 18
4.6 Protection of sensitive XML application data . 18
4.7 Protection of TLV signalling and media content . 21
4.8 MCData client ID . 21
4.9 Warning Header Field . 21
4.9.1 General . 21
4.9.2 Warning texts . 22
5 Functional entities . 25
5.1 Introduction . 25
5.2 MCData client . 25
5.3 MCData server . 26
5.3.1 General . 26
5.3.1 SIP failure case . 27
6 Common procedures. 27
6.1 Introduction . 27
6.2 MCData client procedures . 28
6.2.1 Distinction of requests at the MCData client . 28
6.2.1.1 SIP MESSAGE request . 28
6.2.2 MCData conversation items . 28
6.2.2.1 Generating an SDS Message . 28
6.2.2.2 Generating an FD Message for FD using HTTP . 29
6.2.2.3 Generating an FD Message for FD using media plane . 30
6.2.2.4 Client generating message to terminate FD over HTTP. 31
6.2.3 Disposition Notifications . 31
6.2.3.1 Generating an SDS Notification . 31
6.2.3.2 Generating an FD Notification . 32
6.2.4 Sending SIP requests and receiving SIP responses . 32
6.2.4.1 Generating a SIP MESSAGE request towards the originating participating MCData function . 32
6.3 MCData server procedures . 33
6.3.1 Distinction of requests at the MCData server . 33
6.3.1.1 SIP MESSAGE request . 33
6.3.1.2 SIP INVITE request . 34
6.3.2 Sending SIP requests and receiving SIP responses . 36
6.3.2.1 Generating a SIP MESSAGE request towards the terminating MCData client . 36
6.3.3 Retrieving a group document . 36
6.3.4 Determining targeted group members for MCData communications . 36
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 24.282 version 15.3.0 Release 15 4 ETSI TS 124 282 V15.3.0 (2018-10)
6.3.5 Affiliation check . 36
6.3.6 MCData conversation items . 37
6.3.6.1 Server generating a FD HTTP TERMINATION message for FD over HTTP . 37
6.4 Handling of MIME bodies in a SIP message. 37
6.5 Confidentiality and Integrity Protection of sensitive XML content . 38
6.5.1 General . 38
6.5.1.1 Applicability and exclusions . 38
6.5.1.2 Performing XML content encryption . 38
6.5.1.3 Performing integrity protection on an XML body . 38
6.5.1.4 Verifying integrity of an XML body and decrypting XML elements . 38
6.5.2 Confidentiality Protection . 39
6.5.2.1 General . 39
6.5.2.2 Keys used in confidentiality protection procedures . 39
6.5.2.3 Procedures for sending confidentiality protected content . 39
6.5.2.3.1 MCData client . 39
6.5.2.3.2 MCData server. 39
6.5.2.3.3 Content Encryption in XML elements . 40
6.5.2.3.4 Attribute URI Encryption . 40
6.5.2.4 Procedures for receiving confidentiality protected content . 40
6.5.2.4.1 Determination of confidentiality protected content . 40
6.5.2.4.2 Decrypting confidentiality protected content in XML elements . 41
6.5.2.4.3 Decrypting confidentiality protected URIs in XML attributes . 41
6.5.2.5 MCData server copying received XML content . 41
6.5.3 Integrity Protection of XML documents . 42
6.5.3.1 General . 42
6.5.3.2 Keys used in integrity protection procedures . 43
6.5.3.3 Sending integrity protected content . 44
6.5.3.3.1 MCData client . 44
6.5.3.3.2 MCData server. 44
6.5.3.3.3 Integrity protection procedure . 44
6.5.3.4 Receiving integrity protected content. 45
6.5.3.4.1 Determination of integrity protected content . 45
6.5.3.4.2 Verification of integrity protected content. 45
6.6 Confidentiality and Integrity Protection of TLV messages . 45
6.6.1 General . 45
6.6.2 Derivation of master keys for media and media control . 46
6.6.3 Protection of MCData Data signalling and MCData Data messages . 46
6.6.3.1 General . 46
6.6.3.2 The MCData client . 47
6.6.3.3 The participating MCData function . 47
6.6.3.4 The controlling MCData function . 47
7 Registration and service authorisation . 47
7.1 General . 47
7.2 MCData client procedures . 48
7.2.1 SIP REGISTER request for service authorisation . 48
7.2.1AA SIP REGISTER request without service authorisation . 49
7.2.1A Common SIP PUBLISH procedure . 49
7.2.2 SIP PUBLISH request for service authorisation and MCData service settings . 50
7.2.3 Sending SIP PUBLISH for MCData service settings only . 51
7.2.4 Determination of MCData service settings . 51
7.3 MCData server procedures . 52
7.3.1 General . 52
7.3.1A Confidentiality and Integrity Protection . 52
7.3.2 SIP REGISTER request for service authorisation . 54
7.3.3 SIP PUBLISH request for service authorisation and service settings . 54
7.3.4 Receiving SIP PUBLISH request for MCData service settings only . 55
7.3.5 Receiving SIP PUBLISH request with "Expires=0" . 56
7.3.6 Subscription to and notification of MCData service settings . 57
7.3.6.1 Receiving subscription to MCData service settings . 57
7.3.6.2 Sending notification of change of MCData service settings . 57
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 24.282 version 15.3.0 Release 15 5 ETSI TS 124 282 V15.3.0 (2018-10)
8 Affiliation . 57
8.1 General . 57
8.2 MCData client procedures . 58
8.2.1 General . 58
8.2.2 Affiliation status change procedure . 58
8.2.3 Affiliation status determination procedure . 59
8.2.4 Procedure for sending affiliation status change request in negotiated mode to target MCData user . 60
8.2.5 Procedure for receiving affiliation status change request in negotiated mode from authorized
MCData user . 60
8.3 MCData server procedures . 61
8.3.1 General . 61
8.3.2 Procedures of MCData server serving the MCData user . 61
8.3.2.1 General . 61
8.3.2.2 Stored information . 61
8.3.2.3 Receiving affiliation status change from MCData client procedure . 62
8.3.2.4 Receiving subscription to affiliation status procedure . 65
8.3.2.5 Sending notification of change of affiliation status procedure . 66
8.3.2.6 Sending affiliation status change towards MCData server owning MCData group procedure . 66
8.3.2.7 Affiliation status determination from MCData server owning MCData group procedure . 68
8.3.2.8 Procedure for authorizing affiliation status change request in negotiated mode sent to served
MCData user . 70
8.3.2.9 Forwarding affiliation status change towards another MCData user procedure . 70
8.3.2.10 Forwarding subscription to affiliation status towards another MCData user procedure . 71
8.3.2.11 Affiliation status determination . 72
8.3.2.12 Affiliation status change by implicit affiliation. 72
8.3.2.13 Implicit affiliation status change completion . 74
8.3.2.14 Implicit affiliation status change cancellation . 74
8.3.2.15 Implicit affiliation to configured groups procedure . 74
8.3.3 Procedures of MCData server owning the MCData group . 76
8.3.3.1 General . 76
8.3.3.2 Stored information . 76
8.3.3.3 Receiving group affiliation status change procedure . 76
8.3.3.4 Receiving subscription to affiliation status procedure . 78
8.3.3.5 Sending notification of change of affiliation status procedure . 79
8.3.3.6 Implicit affiliation eligibilty check procedure . 79
8.3.3.7 Affiliation status change by implicit affiliation procedure . 80
8.4 Coding . 80
8.4.1 Extension of application/pidf+xml MIME type . 80
8.4.1.1 Introduction . 80
8.4.1.2 Syntax . 81
8.4.2 Extension of application/simple-filter+xml MIME type . 82
8.4.2.1 Introduction . 82
8.4.2.2 Syntax . 82
9 Short Data Service (SDS) . 83
9.1 General . 83
9.2 On-network SDS . 84
9.2.1 General . 84
9.2.1.1 Sending an SDS message . 84
9.2.1.2 Handling of received SDS messages with or without disposition requests . 84
9.2.1.3 Handling of disposition requests . 86
9.2.2 Standalone SDS using signalling control plane . 86
9.2.2
...