Tech-invite  3GPPspace  IETFspace
◀  ▶  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

TS 24.282
MCData Signalling Control

3GPP‑Page   ETSI‑search   fToC↓   Partial Content →
V19.4.0 (PDF)  2025/09  … p.
V18.11.0  2025/06  649 p.
V17.12.0  2025/03  531 p.
V16.12.0  2025/03  380 p.
V15.10.0  2024/09  238 p.
V14.11.0  2024/09  208 p.
Rapporteur:
Mr. Setty, Adinarayana K
Motorola Solutions UK Ltd.

full Table of Contents for  TS 24.282  Word version:  19.4.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
1Scope  p. 27
2References  p. 27
3Definitions, symbols and abbreviations  p. 31
3.1Definitions  p. 31
3.2Abbreviations  p. 32
4General  p. 33
4.1MCData overview  p. 33
4.2Identity, URI and address assignments  p. 35
4.2.1Public Service identities  p. 35
4.2.2MCData session identity  p. 35
4.2.3MCData client ID  p. 35
4.3Pre-established sessions  p. 35
4.4Emergency Alerts  p. 36
4.5MCData Protocol  p. 36
4.6Protection of sensitive XML application data  p. 36
4.7Protection of TLV signalling and media content  p. 39
4.7ASignalling security when using MBMS |R16|  p. 39
4.8MCData client ID  p. 40
4.9Warning Header Field  p. 41
4.9.1General  p. 41
4.9.2Warning texts  p. 41
4.10MCData emergency groups and emergency group communications |R16|  p. 46
4.11MCData imminent peril group communications |R17|  p. 47
4.12MCData emergency private communications |R17|  p. 48
4.13MCData Resource Management |R18|  p. 49
5Functional entities  p. 49
5.1Introduction  p. 49
5.2MCData client  p. 49
5.3MCData server  p. 50
5.3.0General |R15|  p. 50
5.3.1SIP failure case |R15|  p. 51
5.3.1ASIP provisional response |R17|  p. 52
5.3.2Management of MBMS bearers |R16|  p. 52
5.3.3Management of MBS sessions |R18|  p. 52
5.4MCData gateway server |R17|  p. 52
5.4.1General  p. 52
5.5MCData gateway UE |R18|  p. 53
5.5.1General  p. 53
5.5.2Functional connectivity models  p. 53
5.5.3QoS for MCData gateway UE  p. 54
6Common procedures  p. 55
6.1Introduction  p. 55
6.2MCData client procedures  p. 55
6.2.1Distinction of requests at the MCData client  p. 55
6.2.1.1SIP MESSAGE request  p. 55
6.2.1.2SIP INVITE request |R16|  p. 56
6.2.2MCData conversation items  p. 57
6.2.2.1Generating an SDS Message  p. 57
6.2.2.2Generating an FD Message for FD using HTTP  p. 58
6.2.2.3Generating an FD Message for FD using media plane  p. 59
6.2.2.4Client generating message to terminate FD over HTTP |R15|  p. 60
6.2.3Disposition Notifications  p. 60
6.2.3.1Generating an SDS Notification  p. 60
6.2.3.2Generating an FD Notification  p. 61
6.2.4Sending SIP requests and receiving SIP responses  p. 61
6.2.4.1Generating a SIP MESSAGE request towards the originating participating MCData function  p. 61
6.2.5Location information |R16|  p. 62
6.2.5.1Location information for location reporting  p. 62
6.2.6Void  p. …
6.2.7Handling of in-progress emergency and imminent peril conditions |R17|  p. 63
6.2.7.1MCData upgrade to in-progress emergency or in-progress imminent peril  p. 63
6.2.7.2MCData in-progress emergency cancel  p. 64
6.2.7.3MCData in-progress imminent peril cancel  p. 66
6.2.7.4MCData client receives SIP re-INVITE request  p. 67
6.2.7.5MCData group in-progress emergency group state cancel  p. 68
6.2.8Priority communication conditions |R17|  p. 70
6.2.8.1MCData emergency group communication and imminent peril communication conditions  p. 70
6.2.8.1.1SIP INVITE request or SIP REFER request for originating MCData emergency group communications  p. 70
6.2.8.1.2Resource-Priority header field for MCData emergency group communications  p. 71
6.2.8.1.3SIP re-INVITE request for cancelling MCData in-progress emergency group state  p. 71
6.2.8.1.4Receiving a SIP 2xx response to a SIP request for a priority communication  p. 72
6.2.8.1.5Receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to a SIP request for a priority group communication  p. 73
6.2.8.1.6Determining authorisation for initiating or cancelling an MCData emergency alert  p. 73
6.2.8.1.7Determining authorisation for cancelling the in-progress emergency state of an MCData group  p. 74
6.2.8.1.8Determining authorisation for originating a priority group communication  p. 74
6.2.8.1.9SIP request for originating MCData imminent peril group communications  p. 75
6.2.8.1.10Determining authorisation for cancelling an imminent peril group communication  p. 75
6.2.8.1.11SIP re-INVITE request for cancelling MCData in-progress imminent peril group state  p. 75
6.2.8.1.12Resource-Priority header field for MCData imminent peril group communications  p. 76
6.2.8.1.13Receiving a SIP INFO request in the dialog of a SIP request for a priority group communication  p. 76
6.2.8.1.14SIP re-INVITE request for cancelling the in-progress emergency group state of a group by a third-party  p. 77
6.2.8.1.15Retrieving Resource-Priority header field values  p. 78
6.2.8.1.16Handling receipt of a SIP re-INVITE request for priority group communication origination status within a pre-established session  p. 78
6.2.8.1.17Priority group communication conditions upon receiving communication release  p. 79
6.2.8.1.18Emergency private (one-to-one) communication conditions upon receiving communication release  p. 79
6.2.8.1.19Determining authorisation for initiating or cancelling an MCData adhoc group emergency alert |R18|  p. 80
6.2.8.2Void  p. …
6.2.8.3MCData emergency private (one-to-one) communication conditions  p. 80
6.2.8.3.1Authorisations  p. 80
6.2.8.3.1.1Determining authorisation for initiating an MCData emergency private communication  p. 80
6.2.8.3.1.2Determining authorisation for cancelling an MCData emergency private communication  p. 81
6.2.8.3.1.3Determining authorisation for initiating or cancelling an MCData emergency alert to a MCData user  p. 81
6.2.8.3.2SIP request for originating MCData emergency private communications  p. 81
6.2.8.3.3Resource-Priority header field for MCData emergency private communications  p. 82
6.2.8.3.4Receiving a SIP 2xx response to a SIP request for an MCData emergency private communication  p. 82
6.2.8.3.5Receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to a SIP request for an MCData emergency private communication  p. 82
6.2.8.3.6SIP re-INVITE request for cancelling MCData emergency private communication state  p. 83
6.2.8.3.7Receiving a SIP INFO request in the dialog of a SIP request for a priority private communication  p. 84
6.2.8.3.8SIP re-INVITE request for cancelling the MCData emergency private communication state by a third-party  p. 84
6.2.8.3.9Retrieving a KMS URI associated with an MCData ID  p. 85
6.2.8.4Procedures for modifying ongoing communications  p. 85
6.2.8.4.1Cancelling or ending ongoing client terminating procedures  p. 85
6.2.8.4.2Client terminating procedures for handling SIP re-INVITE for an existing one-to-one communication session  p. 86
6.2.8.4.3MCData in-progress emergency one-to-one communication cancellation  p. 87
6.2.8.4.4Upgrade to MCData emergency one-to-one communication  p. 88
6.3MCData server procedures  p. 89
6.3.1Distinction of requests at the MCData server  p. 89
6.3.1.1SIP MESSAGE request  p. 89
6.3.1.2SIP INVITE request  p. 94
6.3.1.3SIP SUBSCRIBE request |R18|  p. 96
6.3.2Sending SIP requests and receiving SIP responses  p. 96
6.3.2.1Generating a SIP MESSAGE request towards the terminating MCData client  p. 96
6.3.2.2Generating a SIP MESSAGE request towards the controlling MCData function |R17|  p. 96
6.3.2.3Generating a SIP NOTIFY request |R18|  p. 97
6.3.3Retrieving a group document  p. 98
6.3.4Determining targeted group members for MCData communications  p. 98
6.3.5Affiliation check  p. 99
6.3.6MCData conversation items |R15|  p. 99
6.3.6.1Server generating a FD HTTP TERMINATION message for FD over HTTP  p. 99
6.3.7Procedures referenceable from other procedures |R16|  p. 99
6.3.7.1Emergency alert and emergency communications procedures  p. 99
6.3.7.1.1Sending a SIP re-INVITE request for MCData emergency alert or emergency group communication  p. 99
6.3.7.1.2Generating a SIP MESSAGE request for notification of in-progress emergency status change  p. 100
6.3.7.1.3Populate mcdata-info and location-info MIME bodies for emergency alert  p. 101
6.3.7.1.4Retrieving Resource-Priority header field values for emergency communications  p. 102
6.3.7.1.5Generating a SIP MESSAGE request to indicate successful receipt of an emergency alert or emergency cancellation  p. 102
6.3.7.1.6Generating a SIP MESSAGE request for notification of entry into or exit from an emergency alert area |R17|  p. 103
6.3.7.1.7Generating a SIP MESSAGE request for notification of entry into or exit from a group geographic area |R17|  p. 104
6.3.7.1.8Sending a SIP re-INVITE request for MCData imminent peril group communication |R17|  p. 105
6.3.7.1.9Validate priority request parameters |R17|  p. 105
6.3.7.1.10Sending a SIP INFO request in the dialog of a SIP request for a priority communication |R17|  p. 106
6.3.7.1.11Sending a SIP INVITE request for MCData emergency group communication |R17|  p. 106
6.3.7.1.12Sending a SIP UPDATE request for Resource-Priority header field correction |R17|  p. 107
6.3.7.1.13Generating a SIP re-INVITE request |R17|  p. 108
6.3.7.1.14Generating a SIP re-INVITE request to cancel an in-progress emergency |R17|  p. 108
6.3.7.1.15Receipt of SIP re-INVITE request by terminating participating function |R17|  p. 109
6.3.7.1.16Generating a SIP re-INVITE request for emergency private (one-to-one) communication origination within a pre-established session |R17|  p. 109
6.3.7.1.17Receiving a SIP re-INVITE request by the terminating participating function |R17|  p. 111
6.3.7.1.18Receipt of SIP re-INVITE for MCData one-to-one communication from the served user |R17|  p. 111
6.3.7.1.19Controlling MCData function receiving a SIP re-INVITE for upgrade to emergency one-to-one communication |R17|  p. 112
6.3.7.1.20Controlling MCData function receiving a SIP re-INVITE for cancellation of emergency one-to-one communication |R17|  p. 113
6.3.7.1.21Controlling MCData function sending a SIP re-INVITE for upgrade to emergency one-to-one communication |R17|  p. 115
6.3.7.1.22Controlling MCData function sending a SIP re-INVITE for cancellation of emergency one-to-one communication |R17|  p. 115
6.3.7.1.23Controlling MCData function generates a SIP 200 (OK) response |R17|  p. 116
6.3.7.1.24Populate mcdata-info and location-info MIME bodies for adhoc group emergency alert |R18|  p. 117
6.3.7.1.25Generating a SIP MESSAGE request to containing the participant lists of an MCData adhoc group emergency alert |R18|  p. 117
6.3.7.2Authorisations  p. 118
6.3.7.2.1Determining authorisation for initiating an MCData emergency alert  p. 118
6.3.7.2.2Determining authorisation for cancelling an MCData emergency alert  p. 119
6.3.7.2.3Determining authorisation for cancelling an MCData emergency communication  p. 120
6.3.7.2.4Determining authorisation for initiating an MCData imminent peril communication |R17|  p. 120
6.3.7.2.5Determining authorisation for cancelling an MCData imminent peril communication |R17|  p. 121
6.3.7.2.6Determining authorisation for initiating an MCData emergency group or private communication |R17|  p. 121
6.3.7.2.7Generating a SIP 403 response for priority communication request rejection |R17|  p. 122
6.3.7.2.8Determining authorisation for initiating an MCData adhoc group emergency alert |R18|  p. 122
6.3.7.2.9Determining authorisation for cancelling an MCData adhoc group emergency alert |R18|  p. 123
6.3.7.2.10Determining MCData users that are authorized for receiving MCData adhoc group emergency alert participant information |R18|  p. 123
6.3.8Disposition Notifications |R17|  p. 123
6.3.8.1Generating an FD Notification  p. 123
6.4Handling of MIME bodies in a SIP message  p. 124
6.5Confidentiality and Integrity Protection of sensitive XML content  p. 125
6.5.1General  p. 125
6.5.1.1Applicability and exclusions  p. 125
6.5.1.2Performing XML content encryption  p. 125
6.5.1.3Performing integrity protection on an XML body  p. 125
6.5.1.4Verifying integrity of an XML body and decrypting XML elements  p. 125
6.5.2Confidentiality Protection  p. 126
6.5.2.1General  p. 126
6.5.2.2Keys used in confidentiality protection procedures  p. 126
6.5.2.3Procedures for sending confidentiality protected content  p. 126
6.5.2.3.1MCData client  p. 126
6.5.2.3.2MCData server  p. 126
6.5.2.3.3Content Encryption in XML elements  p. 127
6.5.2.3.4Attribute URI Encryption  p. 127
6.5.2.4Procedures for receiving confidentiality protected content  p. 127
6.5.2.4.1Determination of confidentiality protected content  p. 127
6.5.2.4.2Decrypting confidentiality protected content in XML elements  p. 128
6.5.2.4.3Decrypting confidentiality protected URIs in XML attributes  p. 128
6.5.2.5MCData server copying received XML content  p. 128
6.5.3Integrity Protection of XML documents  p. 129
6.5.3.1General  p. 129
6.5.3.2Keys used in integrity protection procedures  p. 130
6.5.3.3Sending integrity protected content  p. 131
6.5.3.3.1MCData client  p. 131
6.5.3.3.2MCData server  p. 131
6.5.3.3.3Integrity protection procedure  p. 131
6.5.3.4Receiving integrity protected content  p. 132
6.5.3.4.1Determination of integrity protected content  p. 132
6.5.3.4.2Verification of integrity protected content  p. 132
6.6Confidentiality and Integrity Protection of TLV messages  p. 132
6.6.1General  p. 132
6.6.2Derivation of master keys for media and media control  p. 133
6.6.3Protection of MCData Data signalling and MCData Data messages  p. 134
6.6.3.1General  p. 134
6.6.3.2The MCData client  p. 134
6.6.3.3The participating MCData function  p. 134
6.6.3.4The controlling MCData function  p. 134
6.7Stored files operational procedures |R17|  p. 135
6.7.1General  p. 135
6.7.2Retrieve the stored file procedure  p. 135
6.7.2.1General client procedures  p. 135
6.7.2.2General server procedures  p. 135
6.7.3Verify the stored file availability procedure  p. 136
6.7.3.1General client procedures  p. 136
6.7.3.2General server procedures  p. 136
6.8Procedures at the MCData gateway |R17|  p. 136
6.8.1General  p. 136
6.8.2MCData gateway server acting as an exit point from an MCData system  p. 137
6.8.3MCData gateway server acting as an entry point in an MCData system  p. 137
6.8.4Local policies enforcement  p. 137
7Registration and service authorisation  p. 138
7.1General  p. 138
7.2MCData client procedures  p. 138
7.2.1SIP REGISTER request for service authorisation  p. 138
7.2.1AASIP REGISTER request without service authorisation  p. 140
7.2.1ACommon SIP PUBLISH procedure  p. 140
7.2.2SIP PUBLISH request for service authorisation and MCData service settings  p. 141
7.2.3Sending SIP PUBLISH for MCData service settings only  p. 142
7.2.4Determination of MCData service settings  p. 142
7.2.5Receiving a CSK key download message |R16|  p. 143
7.3MCData server procedures  p. 144
7.3.1General  p. 144
7.3.1AConfidentiality and Integrity Protection  p. 144
7.3.2SIP REGISTER request for service authorisation  p. 146
7.3.3SIP PUBLISH request for service authorisation and service settings  p. 147
7.3.4Receiving SIP PUBLISH request for MCData service settings only  p. 148
7.3.5Receiving SIP PUBLISH request with "Expires=0"  p. 149
7.3.6Subscription to and notification of MCData service settings  p. 150
7.3.6.1Receiving subscription to MCData service settings  p. 150
7.3.6.2Sending notification of change of MCData service settings  p. 150
7.3.7Sending a CSK key download message |R16|  p. 150
7AMigration procedures |R18|  p. 151
7A.1General  p. 151
7A.2MCData client procedures  p. 151
7A.2.1SIP REGISTER request for migration service authorization  p. 151
7A.2.2Receiving a CSK key download message  p. 153
7A.2.3Receiving a SIP MESSAGE for migration service deauthorization notification  p. 153
7A.3Partner MCData server procedures  p. 153
7A.3.1General  p. 153
7A.3.2Confidentiality and integrity protection  p. 153
7A.3.3SIP REGISTER request for initial authorization  p. 154
7A.3.4Sending a CSK key download message  p. 155
7A.3.5SIP MESSAGE request for migration service authorization response  p. 155
7A.3.6Sending SIP MESSAGE for MCData service authorization notification  p. 155
7A.3.7SIP MESSAGE request for migration service deauthorization notification  p. 156
7A.4Partner MCData gateway server procedures  p. 156
7A.4.1SIP MESSAGE from the partner MCData server  p. 156
7A.4.2SIP MESSAGE request from the primary MCData gateway server  p. 156
7A.5Primary MCData gateway server procedures  p. 157
7A.5.1SIP MESSAGE from the partner MCData gateway  p. 157
7A.5.2SIP MESSAGE request from the primary MCData server  p. 157
7A.6Primary MCData server procedures  p. 157
7A.6.1SIP MESSAGE request for migration service authorization request  p. 157
7A.6.2Receiving SIP MESSAGE for MCData service authorization notification  p. 158
7A.6.3SIP MESSAGE request for migration service deauthorization notification  p. 158
8Affiliation  p. 158
8.1General  p. 158
8.2MCData client procedures  p. 159
8.2.1General  p. 159
8.2.2Affiliation status change procedure  p. 159
8.2.3Affiliation status determination procedure  p. 160
8.2.4Procedure for sending affiliation status change request in negotiated mode to target MCData user  p. 161
8.2.5Procedure for receiving affiliation status change request in negotiated mode from authorized MCData user  p. 162
8.2.6Rules based affiliation status change procedure |R16|  p. 162
8.2.6.1General |R17|  p. 162
8.2.6.2User profile defined rules |R17|  p. 162
8.2.6.3Group configuration defined rules |R17|  p. 162
8.2.7Subscription to group dynamic data |R19|  p. 163
8.3MCData server procedures  p. 163
8.3.1General  p. 163
8.3.2Procedures of MCData server serving the MCData user  p. 164
8.3.2.1General  p. 164
8.3.2.2Stored information  p. 164
8.3.2.3Receiving affiliation status change from MCData client procedure  p. 165
8.3.2.4Receiving subscription to affiliation status procedure  p. 168
8.3.2.5Sending notification of change of affiliation status procedure  p. 168
8.3.2.6Sending affiliation status change towards MCData server owning MCData group procedure  p. 169
8.3.2.7Affiliation status determination from MCData server owning MCData group procedure  p. 171
8.3.2.8Procedure for authorizing affiliation status change request in negotiated mode sent to served MCData user  p. 173
8.3.2.9Forwarding affiliation status change towards another MCData user procedure  p. 174
8.3.2.10Forwarding subscription to affiliation status towards another MCData user procedure  p. 175
8.3.2.11Affiliation status determination  p. 176
8.3.2.12Affiliation status change by implicit affiliation  p. 176
8.3.2.13Implicit affiliation status change completion  p. 178
8.3.2.14Implicit affiliation status change cancellation  p. 178
8.3.2.15Implicit affiliation to configured groups procedure  p. 178
8.3.3Procedures of MCData server owning the MCData group  p. 180
8.3.3.1General  p. 180
8.3.3.2Stored information  p. 180
8.3.3.3Receiving group affiliation status change procedure  p. 180
8.3.3.4Receiving subscription to affiliation status procedure  p. 182
8.3.3.5Sending notification of change of affiliation status procedure  p. 183
8.3.3.6Implicit affiliation eligibilty check procedure  p. 183
8.3.3.7Affiliation status change by implicit affiliation procedure  p. 184
8.3.3.8Forwarding subscription to group dynamic data towards the controlling MCData server procedure |R19|  p. 184
8.3.3.9Receiving subscription to group dynamic data procedure |R19|  p. 186
8.3.3.10Sending notification of change of group dynamic data procedure |R19|  p. 186
8.4Coding  p. 187
8.4.1Extension of application/pidf+xml MIME type  p. 187
8.4.1.1Introduction  p. 187
8.4.1.2Syntax  p. 187
8.4.2Extension of application/simple-filter+xml MIME type  p. 189
8.4.2.1Introduction  p. 189
8.4.2.2Syntax  p. 189
9Short Data Service (SDS)  p. 190
9.1General  p. 190
9.2On-network SDS  p. 190
9.2.1General  p. 190
9.2.1.1Sending an SDS message  p. 190
9.2.1.2Handling of received SDS messages with or without disposition requests  p. 191
9.2.1.3Handling of disposition requests  p. 192
9.2.2Standalone SDS using signalling control plane  p. 193
9.2.2.1General  p. 193
9.2.2.2MCData client procedures  p. 193
9.2.2.2.1MCData client originating procedures  p. 193
9.2.2.2.2MCData client terminating procedures  p. 195
9.2.2.3Participating MCData function procedures  p. 196
9.2.2.3.1Originating participating MCData function procedures  p. 196
9.2.2.3.2Terminating participating MCData function procedures  p. 198
9.2.2.4Controlling MCData function procedures  p. 199
9.2.2.4.1Originating controlling MCData function procedures  p. 199
9.2.2.4.2Terminating controlling MCData function procedures  p. 201
9.2.2.5Non-controlling function of an MCVideo group procedures |R18|  p. 204
9.2.2.5.1Terminating procedure  p. 204
9.2.2.5.2Originating procedure  p. 205
9.2.3Standalone SDS using media plane  p. 208
9.2.3.1General  p. 208
9.2.3.2MCData client procedures  p. 209
9.2.3.2.1SDP offer generation  p. 209
9.2.3.2.2SDP answer generation  p. 209
9.2.3.2.3MCData client originating procedures  p. 209
9.2.3.2.4MCData client terminating procedures  p. 212
9.2.3.3Participating MCData function procedures  p. 213
9.2.3.3.1SDP offer generation  p. 213
9.2.3.3.2SDP answer generation  p. 214
9.2.3.3.3Originating participating MCData function procedures  p. 214
9.2.3.3.4Terminating participating MCData function procedures  p. 216
9.2.3.4Controlling MCData function procedures  p. 218
9.2.3.4.1SDP offer generation  p. 218
9.2.3.4.2SDP answer generation  p. 219
9.2.3.4.3Originating controlling MCData function procedures  p. 219
9.2.3.4.4Terminating controlling MCData function procedures  p. 220
9.2.4SDS session  p. 222
9.2.4.1General  p. 222
9.2.4.2MCData client procedures  p. 223
9.2.4.2.1SDP offer generation  p. 223
9.2.4.2.2SDP answer generation  p. 223
9.2.4.2.3MCData client originating procedures  p. 223
9.2.4.2.4MCData client terminating procedures  p. 227
9.2.4.2.5MCData client initiates cancellation for an in-progress emergency one-to-one communication using SDS session |R17|  p. 229
9.2.4.2.6MCData client initiates upgrade to emergency for an ongoing one-to-one communication using SDS session |R17|  p. 229
9.2.4.2.7Terminating procedures for MCData client to upgrade or cancel an emergency one-to-one communication using SDS session |R17|  p. 229
9.2.4.3Participating MCData function procedures  p. 229
9.2.4.3.1SDP offer generation  p. 229
9.2.4.3.2SDP answer generation  p. 230
9.2.4.3.3Originating participating MCData function procedures  p. 230
9.2.4.3.4Terminating participating MCData function procedures  p. 233
9.2.4.3.5Processing of request from the served user to upgrade or cancel an emergency one-to-one communication using SDS session |R17|  p. 235
9.2.4.3.6Processing of request from controlling MCData function to upgrade or cancel an emergency one-to-one communication using SDS session |R17|  p. 235
9.2.4.4Controlling MCData function procedures  p. 235
9.2.4.4.1SDP offer generation  p. 235
9.2.4.4.2SDP answer generation  p. 235
9.2.4.4.3Originating controlling MCData function procedures  p. 235
9.2.4.4.4Terminating controlling MCData function procedures  p. 237
9.2.4.4.5Controlling MCData function receiving a request for upgrade to emergency of a one-to-one communication using SDS session |R17|  p. 240
9.2.4.4.6Controlling MCData function receiving a request for cancellation of an emergency one-to-one communication using SDS session |R17|  p. 240
9.2.4.4.7Controlling MCData function sending a request for upgrade to emergency of a one-to-one communication using SDS session |R17|  p. 240
9.2.4.4.8Controlling MCData function sending a request for cancellation of an emergency one-to-one communication using SDS session |R17|  p. 240
9.2.5SDS communication using pre-established session |R16|  p. 241
9.2.5.1Common procedure  p. 241
9.2.5.1.1Generating an INVITE request on receipt of a REFER request  p. 241
9.2.5.1.2Generating Re-INVITE request towards originating MCData client within pre-established session  p. 242
9.2.5.1.3Generating Re-INVITE request towards terminating MCData client within pre-established session  p. 242
9.2.5.2Initiating one-to-one SDS communication  p. 242
9.2.5.2.0General |R17|  p. 242
9.2.5.2.1MCData client procedures  p. 242
9.2.5.2.2Participating MCData function procedures  p. 246
9.2.5.2.3Controlling MCData function procedures |R17|  p. 249
9.2.5.3Initiating group SDS communication  p. 250
9.2.5.3.0General |R17|  p. 250
9.2.5.3.1MCData client procedures  p. 250
9.2.5.3.2Participating MCData function procedures  p. 253
9.2.5.4Leaving SDS communication  p. 256
9.2.5.4.1MCData client procedures  p. 256
9.2.5.4.2Participating MCData function procedures  p. 257
9.2.6SDS session using MBMS delivery in the media plane |R16|  p. 258
9.2.7SDS session using MBS delivery in the media plane |R18|  p. 258
9.3Off-network SDS  p. 258
9.3.1General  p. 258
9.3.1.1Message transport to a MCData Client  p. 258
9.3.1.2Message transport to a MCData Group  p. 258
9.3.2Standalone SDS using signalling control plane  p. 259
9.3.2.1General  p. 259
9.3.2.2Sending SDS message  p. 259
9.3.2.3Retransmitting SDS message  p. 260
9.3.2.4Receiving SDS message  p. 261
9.3.2.5SDS Read while TFS3 (delivery and read) is running  p. 262
9.3.2.6Timer TFS3 (delivery and read) expires  p. 262
10File Distribution (FD)  p. 262
10.1General  p. 262
10.2On-network FD  p. 262
10.2.1General  p. 262
10.2.1.1Sending an FD message  p. 262
10.2.1.2Handling of received FD messages  p. 263
10.2.1.2.1Initial processing of the received FD message  p. 263
10.2.1.2.2Mandatory Download  p. 263
10.2.1.2.3Non-Mandatory download  p. 264
10.2.1.3Discovery of the Absolute URI of the media storage function  p. 266
10.2.1.3.1General  p. 266
10.2.1.3.2Void  p. …
10.2.1.3.3Participating MCData function procedures  p. 266
10.2.1.3.4Controlling MCData function procedures  p. 268
10.2.2File upload using HTTP  p. 269
10.2.2.1Media storage client procedures  p. 269
10.2.2.2Media storage function procedures  p. 271
10.2.3File download using HTTP  p. 272
10.2.3.1Media storage client procedures  p. 272
10.2.3.2Media storage function procedures  p. 273
10.2.4FD using HTTP  p. 273
10.2.4.1General  p. 273
10.2.4.2MCData client procedures  p. 274
10.2.4.2.1MCData client originating procedures  p. 274
10.2.4.2.2MCData client terminating procedures  p. 275
10.2.4.3Participating MCData function procedures  p. 275
10.2.4.3.1Originating participating MCData function procedures  p. 275
10.2.4.3.2Terminating participating MCData function procedures  p. 277
10.2.4.4Controlling MCData function procedures  p. 278
10.2.4.4.1Originating controlling MCData function procedures  p. 278
10.2.4.4.2Terminating controlling MCData function procedures  p. 279
10.2.5FD using media plane  p. 284
10.2.5.1General  p. 284
10.2.5.2MCData client procedures  p. 284
10.2.5.2.1SDP offer generation  p. 284
10.2.5.2.2SDP answer generation  p. 285
10.2.5.2.3MCData client originating procedures  p. 285
10.2.5.2.4MCData client terminating procedures  p. 289
10.2.5.2.5MCData client initiates cancellation for an in-progress emergency one-to-one communication using FD media plane |R17|  p. 292
10.2.5.2.6MCData client initiates upgrade to emergency for an ongoing one-to-one communication using FD media plane |R17|  p. 292
10.2.5.2.7Terminating procedures for MCData client to upgrade or cancel an emergency one-to-one communication using FD media plane |R17|  p. 292
10.2.5.3Participating MCData function procedures  p. 292
10.2.5.3.1SDP offer generation  p. 292
10.2.5.3.2SDP answer generation  p. 293
10.2.5.3.3Originating participating MCData function procedures  p. 293
10.2.5.3.4Terminating participating MCData function procedures  p. 296
10.2.5.3.5Processing of request from the served user to upgrade or cancel an emergency one-to-one communication using FD media plane |R17|  p. 300
10.2.5.3.6Processing of request from controlling MCData function to upgrade or cancel an emergency one-to-one communication using FD media plane |R17|  p. 300
10.2.5.4Controlling MCData function procedures  p. 300
10.2.5.4.1SDP offer generation  p. 300
10.2.5.4.2SDP answer generation  p. 301
10.2.5.4.3Originating controlling MCData function procedures  p. 301
10.2.5.4.4Terminating controlling MCData function procedures  p. 303
10.2.5.4.5Controlling MCData function receiving a request for upgrade to emergency of a one-to-one communication using FD media plane |R17|  p. 307
10.2.5.4.6Controlling MCData function receiving a request for cancellation of an emergency one-to-one communication using FD media plane |R17|  p. 307
10.2.5.4.7Controlling MCData function sending a request for upgrade to emergency of a one-to-one communication using FD media plane |R17|  p. 307
10.2.5.4.8Controlling MCData function sending a request for cancellation of an emergency one-to-one communication using FD media plane |R17|  p. 308
10.2.6FD using MBMS delivery via MB2 interface |R17|  p. 308
10.2.7FD using MBS delivery via MB2 interface |R18|  p. 308
11Transmission and Reception Control  p. 308
11.1General  p. 308
11.2Auto-receive for File Distribution  p. 310
11.3Accessing list of deferred data group communications |R15|  p. 310
11.3.1General  p. 310
11.3.2MCData client procedures  p. 310
11.3.2.1Sending a request to access a list of deferred group communications  p. 310
11.3.2.2Receiving a list of deferred group communications  p. 311
11.3.3Participating MCData function procedures  p. 311
11.3.3.1Receiving a request to access a list of deferred group communications  p. 311
11.3.3.2Sending a list of deferred group communications  p. 311
12Dispositions and Notifications  p. 312
12.1General  p. 312
12.2On-network disposition notifications  p. 312
12.2.1MCData client procedures  p. 312
12.2.1.1MCData client sends a disposition notification message  p. 312
12.2.1.2MCData client receives a disposition notification message  p. 313
12.2.2Participating MCData function procedures  p. 313
12.2.2.1Participating MCData function receives disposition notification from a MCData user  p. 313
12.2.2.2Participating MCData function receives disposition notification from a Controlling MCData function  p. 315
12.2.2.3Participating MCData function sends a disposition notification message |R17|  p. 316
12.2.3Controlling MCData function procedures  p. 316
12.3Off-network dispositions  p. 319
12.3.1General  p. 319
12.3.2Sending off-network SDS delivery notification  p. 319
12.3.3Sending off-network SDS read notification  p. 319
12.3.4Sending off-network SDS delivered and read notification  p. 320
12.3.5Off-network SDS notification retransmission  p. 320
12.4Network-triggered notifications for FD  p. 321
12.4.1General  p. 321
12.4.1.1File availability expiry  p. 321
12.4.2Controlling MCData function procedures  p. 321
12.4.2.1Generation of a SIP MESSAGE request for notification  p. 321
12.4.2.2Expiry of timer TDC2 (file availability timer) |R16|  p. 322
12.4.3Participating MCData function procedures  p. 323
12.4.4MCData client terminating procedures  p. 323
13Communication Release  p. 323
13.1General  p. 323
13.2On-network  p. 323
13.2.1General  p. 323
13.2.1.1Server generating message for release of communication over HTTP towards participating MCData function |R15|  p. 323
13.2.1.2Authorised user generating FD HTTP TERMINATION MESSAGE towards participating MCData function |R15|  p. 324
13.2.2MCData originating user initiated communication release  p. 325
13.2.2.1General  p. 325
13.2.2.2Release of MCData communication over media plane  p. 325
13.2.2.2.1General  p. 325
13.2.2.2.2MCData client procedures  p. 325
13.2.2.2.2.1MCData client originating procedures  p. 325
13.2.2.2.2.2MCData client terminating procedures  p. 325
13.2.2.2.3Participating MCData function procedures  p. 325
13.2.2.2.3.1Originating participating MCData function procedures  p. 325
13.2.2.2.3.2Terminating participating MCData function procedures  p. 326
13.2.2.2.4Controlling MCData function procedures  p. 326
13.2.2.2.4.1Communication release policy for group MCData communication  p. 326
13.2.2.2.4.2Communication release policy for one-to-one MCData communication  p. 326
13.2.2.2.4.3Receiving a SIP BYE request  p. 326
13.2.2.2.4.4Sending a SIP BYE request  p. 327
13.2.2.3Release of MCData communication over HTTP |R15|  p. 327
13.2.2.3.1General  p. 327
13.2.2.3.2MCData client procedures  p. 327
13.2.2.3.2.1MCData client originating procedures  p. 327
13.2.2.3.2.1.1Initiating Release  p. 327
13.2.2.3.2.1.2Receiving Release Response Type from server  p. 328
13.2.2.3.2.2MCData client terminating procedures  p. 328
13.2.2.3.3Participating MCData function procedures  p. 328
13.2.2.3.3.1Originating participating MCData function procedures  p. 328
13.2.2.3.3.2Terminating participating MCData function procedures  p. 328
13.2.2.3.4Controlling MCData function procedures  p. 328
13.2.3MCData server initiated communication release without prior indication  p. 328
13.2.3.1General  p. 328
13.2.3.2Release of MCData communication over media plane  p. 329
13.2.3.2.1General  p. 329
13.2.3.2.2MCData client procedures  p. 329
13.2.3.2.3Participating MCData function procedures  p. 329
13.2.3.2.4Controlling MCData function procedures  p. 329
13.2.3.3Release of MCData communication over HTTP |R15|  p. 329
13.2.3.3.1General  p. 329
13.2.3.3.2MCData client procedures  p. 329
13.2.3.3.2.1MCData client originating procedure  p. 329
13.2.3.3.2.2MCData client terminating procedure  p. 330
13.2.3.3.3Participating MCData function procedures  p. 330
13.2.3.3.4Controlling MCData function procedures  p. 330
13.2.4MCData server initiated communication release with prior indication  p. 330
13.2.4.1General  p. 330
13.2.4.2MCData client procedures for communication over media plane  p. 330
13.2.4.2.1Receiving intent to release the communication  p. 330
13.2.4.2.2Request for extension of communication  p. 331
13.2.4.2.3Receiving response to communication extension request  p. 331
13.2.4.3Participating MCData function procedures for communication over media plane  p. 332
13.2.4.3.1Receiving SIP INFO request from the controlling MCData function  p. 332
13.2.4.3.2Receiving SIP INFO request from the MCData client  p. 332
13.2.4.4Controlling MCData function procedures for communication over media plane  p. 332
13.2.4.4.1Sending intent to release a communication  p. 332
13.2.4.4.2Receiving more information  p. 333
13.2.4.4.3Receiving request for extension of communication  p. 333
13.2.4.4.4Sending response to communication extension request  p. 333
13.2.4.5Release of MCData communication over HTTP |R15|  p. 334
13.2.4.5.1General  p. 334
13.2.4.5.2MCData client procedures  p. 334
13.2.4.5.2.1Receiving intent to release the communication  p. 334
13.2.4.5.2.2Request for extension of communication  p. 335
13.2.4.5.2.3Receiving response to communication extension request  p. 335
13.2.4.5.3Participating MCData function procedures  p. 335
13.2.4.5.3.1Originating participating MCData function procedures  p. 335
13.2.4.5.3.2Terminating participating MCData function procedures  p. 335
13.2.4.5.4Controlling MCData function procedures  p. 335
13.2.4.5.4.1Sending intent to release a communication  p. 335
13.2.4.5.4.2Receiving request for extension of communication  p. 336
13.2.4.5.4.3Sending response to communication extension request  p. 336
13.2.5Authorized MCData user initiated communication release without prior indication |R15|  p. 336
13.2.5.1General  p. 336
13.2.5.2Release of MCData communication over media plane  p. 337
13.2.5.2.1General  p. 337
13.2.5.2.2Authorized MCData client procedures  p. 337
13.2.5.2.2.1Sending communication release request  p. 337
13.2.5.2.3Participating MCData function procedures  p. 337
13.2.5.2.3.1Receiving SIP INFO request from the authorized MCData client  p. 337
13.2.5.2.4Controlling MCData function procedures  p. 338
13.2.5.2.4.1Receiving request to release the communication from authorized MCData user  p. 338
13.2.5.3Release of MCData communication over HTTP  p. 338
13.2.5.3.1General  p. 338
13.2.5.3.2Authorized MCData client procedures  p. 338
13.2.5.3.2.1Sending communication release request  p. 338
13.2.5.3.2.2Receiving Release Response Type from server  p. 339
13.2.5.3.3Participating MCData function procedures  p. 339
13.2.5.3.3.1Originating participating MCData function procedures  p. 339
13.2.5.3.3.2Terminating participating MCData function procedures  p. 339
13.2.5.3.4Controlling MCData function procedures  p. 339
13.2.5.3.4.1Receiving request to release the communication from authorized MCData user  p. 339
13.2.6Authorized MCData user initiated communication release with prior indication |R15|  p. 340
13.2.6.1General  p. 340
13.2.6.2Release of MCData communication over media plane  p. 340
13.2.6.2.1General  p. 340
13.2.6.2.2Authorized MCData client procedures  p. 340
13.2.6.2.2.1Sending intent to release a communication  p. 340
13.2.6.2.2.2Receiving more information  p. 341
13.2.6.2.2.3Receiving request for extension of communication  p. 341
13.2.6.2.2.4Sending response to communication extension request  p. 341
13.2.6.2.3Participating MCData function procedures  p. 342
13.2.6.2.3.1Receiving SIP INFO request from the authorized MCData client  p. 342
13.2.6.2.3.2Receiving SIP INFO request from the controlling MCData function  p. 342
13.2.6.2.4Controlling MCData function procedures  p. 342
13.2.6.2.4.1Receiving request to release the communication from authorized MCData user  p. 342
13.2.6.2.4.2Receiving more information  p. 343
13.2.6.2.4.3Receiving request for extension of communication  p. 343
13.2.6.2.4.4Receiving response to communication extension request  p. 344
13.2.6.3Release of MCData communication over HTTP  p. 344
13.2.6.3.1General  p. 344
13.2.6.3.2Authorized MCData client procedures  p. 344
13.2.6.3.2.1Sending intent to release a communication  p. 344
13.2.6.3.2.2Receiving request for extension of communication  p. 345
13.2.6.3.2.3Sending response to communication extension request  p. 345
13.2.6.3.2.4Receiving Release Response from server  p. 346
13.2.6.3.3Participating MCData function procedures  p. 346
13.2.6.3.3.1Originating participating MCData function procedures  p. 346
13.2.6.3.3.2Terminating participating MCData function procedures  p. 346
13.2.6.3.4Controlling MCData function procedures  p. 346
13.2.6.3.4.1Receiving request to release the communication from authorized MCData user  p. 346
13.2.6.3.4.2Receiving request for extension of communication  p. 347
13.2.6.3.4.3Receiving response to communication extension request  p. 347
14Enhanced Status (ES)  p. 348
14.1General  p. 348
14.2On-network ES  p. 348
14.2.1MCData client procedures |R15|  p. 348
14.2.1.1MCData client originating procedures  p. 348
14.2.1.2MCData client terminating procedures  p. 348
14.2.2Participating MCData function procedures |R15|  p. 348
14.2.2.1Originating participating MCData function procedures  p. 348
14.2.2.2Terminating participating MCData function procedures  p. 348
14.2.3Controlling MCData function procedures |R15|  p. 348
14.2.3.1Originating controlling MCData function procedures  p. 348
14.2.3.2Terminating controlling MCData function procedures  p. 349
14.3Off-network ES  p. 349
14.3.1Sending enhanced status message |R15|  p. 349
14.3.2Receiving enhanced status message |R15|  p. 349
15Message Formats  p. 349
15.1MCData message functional definitions and contents  p. 349
15.1.1General  p. 349
15.1.2SDS SIGNALLING PAYLOAD message  p. 349
15.1.2.1Message definition  p. 349
15.1.3FD SIGNALLING PAYLOAD message  p. 350
15.1.3.1Message definition  p. 350
15.1.4DATA PAYLOAD message  p. 351
15.1.4.1Message definition  p. 351
15.1.5SDS NOTIFICATION message  p. 352
15.1.5.1Message definition  p. 352
15.1.6FD NOTIFICATION message  p. 352
15.1.6.1Message definition  p. 352
15.1.7SDS OFF-NETWORK MESSAGE message  p. 353
15.1.7.1Message definition  p. 353
15.1.8SDS OFF-NETWORK NOTIFICATION message  p. 354
15.1.8.1Message definition  p. 354
15.1.9FD NETWORK NOTIFICATION message  p. 355
15.1.9.1Message definition  p. 355
15.1.10COMMUNICATION RELEASE message  p. 355
15.1.10.1Message definition  p. 355
15.1.11DEFERRED DATA REQUEST message |R15|  p. 356
15.1.11.1Message definition  p. 356
15.1.12DEFERRED DATA RESPONSE message |R15|  p. 356
15.1.12.1Message definition  p. 356
15.1.13FD HTTP TERMINATION |R15|  p. 357
15.1.13.1Message definition  p. 357
15.1.14GROUP EMERGENCY ALERT message |R16|  p. 357
15.1.14.1Message definition  p. 357
15.1.15GROUP EMERGENCY ALERT ACK message |R16|  p. 358
15.1.15.1Message definition  p. 358
15.1.16GROUP EMERGENCY ALERT CANCEL message |R16|  p. 358
15.1.16.1Message definition  p. 358
15.1.17GROUP EMERGENCY ALERT CANCEL ACK message |R16|  p. 359
15.1.17.1Message definition  p. 359
15.2General message format and information elements coding  p. 359
15.2.1General  p. 359
15.2.2Message type  p. 360
15.2.3SDS disposition request type  p. 360
15.2.4FD disposition request type  p. 361
15.2.5SDS disposition notification type  p. 361
15.2.6FD disposition notification type  p. 362
15.2.7Application ID  p. 362
15.2.8Date and time  p. 362
15.2.9Conversation ID  p. 363
15.2.10Message ID  p. 363
15.2.11InReplyTo message ID  p. 363
15.2.12Number of payloads  p. 364
15.2.13Payload  p. 364
15.2.14MCData group ID  p. 365
15.2.15MCData user ID  p. 366
15.2.16Mandatory download  p. 366
15.2.17Metadata  p. 367
15.2.18Notification type  p. 367
15.2.19Data query type  p. 368
15.2.20Comm release Information type  p. 368
15.2.21Extension response type  p. 368
15.2.22Termination Information type |R15|  p. 369
15.2.23Release Response Type |R15|  p. 369
15.2.24Extended application ID |R15|  p. 370
15.2.25User location |R16|  p. 371
15.2.26Organization name |R16|  p. 371
15.2.27Deferred FD signalling payload |R17|  p. 372
15.2.28Application metadata container |R17|  p. 372
16Emergency Alert |R16|  p. 373
16.1General  p. 373
16.2On-network emergency alert  p. 374
16.2.1Client procedures  p. 374
16.2.1.1Emergency alert origination  p. 374
16.2.1.2Emergency alert cancellation  p. 375
16.2.1.3MCData client receives an MCData emergency alert or communication notification  p. 377
16.2.1.4MCData client receives notification of entry into or exit from a group geographic area |R17|  p. 379
16.2.1.5MCData client receives notification of entry into or exit from an emergency alert area |R17|  p. 379
16.2.2Participating MCData function procedures  p. 380
16.2.2.1Receipt of a SIP MESSAGE request for emergency notification from the served MCData client  p. 380
16.2.2.2Receipt of a SIP MESSAGE request for emergency notification for terminating MCData client  p. 381
16.2.2.3Receipt of a SIP MESSAGE request indicating successful delivery of emergency notification  p. 382
16.2AOn-network MCData adhoc group emergency alert |R18|  p. 383
16.2A.1Client procedures  p. 383
16.2A.1.1Ad hoc group emergency alert origination  p. 383
16.2A.1.2Ad hoc group emergency alert cancellation  p. 384
16.2A.1.3MCData client receives an MCData adhoc group emergency alert notification  p. 386
16.2A.1.4Sending a "SIP MESSAGE request to modify participant criteria for ad hoc group emergency alert to participating MCData function" |R19|  p. 386
16.2A.1.5Receiving a "SIP MESSAGE request for participant criteria modification response for ad hoc group emergency alert from participating MCData function" |R19|  p. 387
16.2A.2Participating MCData function procedures  p. 388
16.2A.2.1Receipt of a SIP MESSAGE request for adhoc group emergency notification from the served MCData client  p. 388
16.2A.2.2Receipt of a SIP MESSAGE request for adhoc group emergency notification for terminating MCData client  p. 389
16.2A.2.3Receipt of a SIP MESSAGE request indicating successful delivery of adhoc group emergency notification of originating MCData client  p. 389
16.2A.2.4Adhoc group emergency alert participants modify procedure initiated by participating MCData function  p. 390
16.2A.2.5Receiving a "SIP MESSAGE request to modify participant criteria for ad hoc group emergency alert to participating MCData function" |R19|  p. 390
16.2A.2.6Receiving a "SIP MESSAGE request for participant criteria modification response for ad hoc group emergency alert from controlling MCData function" |R19|  p. 391
16.2A.3Controlling MCData function procedures  p. 392
16.2A.3.1Handling of adhoc group emergency alert notification  p. 392
16.2A.3.2Handling of adhoc group emergency alert cancellation  p. 393
16.2A.3.3Handling of ongoing adhoc group emergency alert  p. 395
16.2A.3.4Handling of adhoc group emergency alert participants modify procedure initiated by participating MCData function  p. 395
16.2A.3.5Receiving a "SIP MESSAGE request to modify participant criteria for ad hoc group emergency alert to controlling MCData function" |R19|  p. 396
16.2.3Controlling MCData function procedures |R16|  p. 397
16.2.3.1Handling of a SIP MESSAGE request for emergency notification  p. 397
16.2.3.2Handling of a SIP MESSAGE request for emergency alert cancellation  p. 398
16.2.3.3Late emergency alert initiated by controlling MCData function |R18|  p. 401
16.3Off-network emergency alert  p. 401
16.3.1General  p. 401
16.3.2Basic state machine  p. 401
16.3.2.1General  p. 401
16.3.2.2Emergency alert state machine  p. 401
16.3.2.3Emergency alert states  p. 402
16.3.2.3.1E1: Not in emergency state  p. 402
16.3.2.3.2E2: Emergency state  p. 402
16.3.3Procedures  p. 402
16.3.3.1Originating user sending emergency alert  p. 402
16.3.3.2Emergency alert retransmission  p. 403
16.3.3.3Terminating user receiving emergency alert  p. 403
16.3.3.4Terminating user receiving retransmitted emergency alert  p. 403
16.3.3.5Originating user cancels emergency alert  p. 404
16.3.3.6Terminating user receives GROUP EMERGENCY ALERT CANCEL message  p. 404
16.3.3.7Implicit emergency alert cancel  p. 404
17Location procedures |R16|  p. 405
17.1General  p. 405
17.2Participating MCData function location procedures  p. 405
17.2.1General  p. 405
17.2.2Location reporting configuration  p. 405
17.2.2ALocation reporting configuration requested by authorized MCData client |R18|  p. 406
17.2.2BLocation reporting configuration request from another MCData server |R18|  p. 407
17.2.3Location information request  p. 407
17.2.3.1Location information request to MCData client |R18|  p. 407
17.2.3.2Location information request from authorized MCData client |R18|  p. 408
17.2.3.3Location information request from another MCData server |R18|  p. 410
17.2.4Location information report  p. 411
17.2.4.1Location information report from an MCData client |R18|  p. 411
17.2.4.2Location information report from another MCData server |R18|  p. 411
17.2.5Abnormal cases  p. 411
17.3MCData client location procedures  p. 412
17.3.1General  p. 412
17.3.2Location reporting configuration  p. 412
17.3.2.1MCData client receiving location reporting configuration |R18|  p. 412
17.3.2.2Authorized MCData client sending location reporting configuration |R18|  p. 413
17.3.3Location information request  p. 413
17.3.3.1Location information request to MCData client |R18|  p. 413
17.3.3.2Location information request from authorized MCData client |R18|  p. 413
17.3.4Location information report  p. 414
17.3.4.1Report triggering  p. 414
17.3.4.2Sending location information report  p. 414
18Pre-established session |R16|  p. 415
18.1General  p. 415
18.2Participating MCData function use of resource sharing  p. 415
18.3Pre-established session for MCData SDS communication  p. 416
18.3.1General  p. 416
18.3.1.1SDP offer generation  p. 416
18.3.1.2SDP answer generation  p. 416
18.3.2Session establishment  p. 416
18.3.2.1MCData client procedures  p. 416
18.3.2.2Participating MCData function procedures  p. 417
18.3.3Session release  p. 418
18.3.3.1MCData client procedures  p. 418
18.3.3.1.1MCData client initiated release  p. 418
18.3.3.1.2Participating MCData function initiated release  p. 419
18.3.3.2Participating MCData function procedures  p. 419
18.3.3.2.1MCData client initiated release  p. 419
18.3.3.2.2Participating MCData function initiated release  p. 419
18.3.4Session modification  p. 420
18.3.4.1MCData client procedures  p. 420
18.3.4.1.1MCData client initiated  p. 420
18.3.4.1.2MCData client receives SIP UPDATE or SIP re-INVITE request  p. 420
18.3.4.2Participating MCData function procedures  p. 420
18.3.4.2.1Reception of a SIP UPDATE or SIP re-INVITE request from served MCData client  p. 420
18.3.4.2.2Participating MCData function initiated  p. 421
19MBMS transmission usage procedure |R16|  p. 421
19.1General  p. 421
19.2Participating MCData function MBMS usage procedures  p. 421
19.2.1General  p. 421
19.2.2Sending MBMS bearer announcement procedures  p. 422
19.2.2.1General  p. 422
19.2.2.2Sending an initial MBMS bearer announcement procedure  p. 422
19.2.2.3Updating an announcement  p. 424
19.2.2.4Cancelling an MBMS bearer announcement  p. 425
19.2.2.5Sending a MuSiK download message  p. 425
19.2.3Receiving an MBMS bearer listening status from an MCData client  p. 426
19.2.4Abnormal cases  p. 427
19.3MCData client MBMS usage procedures  p. 427
19.3.1General  p. 427
19.3.2Receiving an MBMS bearer announcement  p. 427
19.3.3The MBMS bearer listening status and suspension report procedures  p. 429
19.3.3.1Conditions for sending an MBMS listening status report  p. 429
19.3.3.2Sending the MBMS bearer listening or suspension status report  p. 430
19.3.4Receiving a MuSiK download message  p. 432
19AUse of 5G MBS transmission (on-network) |R18|  p. 433
19A.1General  p. 433
19A.2MCData client procedures  p. 433
19A.2.1General  p. 433
19A.2.2Receiving an MBS session announcement  p. 433
19A.2.3Sending an MBS listening status report  p. 434
19A.2.3.1Conditions for sending an MBS listening status report  p. 434
19A.2.3.2Sending the MBS listening status report  p. 434
19A.2.4Receiving a MuSiK download message  p. 434
19A.2.5Sending a UE session join notification  p. 434
19A.2.5.1Conditions for sending the UE session join notification  p. 434
19A.2.5.2Sending the UE session join notification  p. 435
19A.2.6Sending an MBS session de-announcement acknowledgement  p. 436
19A.3Participating MCData server procedures  p. 437
19A.3.1General  p. 437
19A.3.2Sending an MBS session announcement to the MCData client  p. 437
19A.3.2.1General  p. 437
19A.3.2.2Sending an initial MBS session announcement procedure  p. 437
19A.3.2.3Updating an announcement  p. 438
19A.3.2.4Deleting an MBS session announcement  p. 438
19A.3.2.5Sending a MuSiK download message  p. 438
19A.3.3Receiving an MBS listening status report from the MCData client  p. 438
19A.3.4Receiving a UE session join notification from the MCData client  p. 439
19A.3.5Receiving an MBS session de-announcement from the MCData client  p. 439
20IP Connectivity |R16|  p. 440
20.1General  p. 440
20.1.1Void  p. …
20.1.2Void  p. …
20.1.3Void  p. …
20.2MCData Client Procedures  p. 440
20.2.0aSDP offer generation |R17|  p. 440
20.2.0bSDP answer generation |R17|  p. 440
20.2.1MCData client originating procedures  p. 441
20.2.2MCData client terminating procedures  p. 442
20.3Participating MCData function procedures  p. 443
20.3.0aSDP offer generation |R17|  p. 443
20.3.0bSDP answer generation |R17|  p. 444
20.3.1Originating participating MCData function procedures  p. 444
20.3.2Terminating participating MCData function procedures  p. 446
20.4Controlling MCData function procedures  p. 448
20.4.0aSDP offer generation |R17|  p. 448
20.4.0bSDP answer generation |R17|  p. 448
20.4.1Originating procedures  p. 448
20.4.2Terminating procedures  p. 449
21MCData Message Store |R16|  p. 451
21.1General  p. 451
21.2MCData message store functions and client procedures  p. 452
21.2.1Object retrieval procedure  p. 452
21.2.1.1Message store client procedures  p. 452
21.2.1.2Message store function procedures  p. 452
21.2.2Object search procedure  p. 452
21.2.2.1Message store client procedures  p. 452
21.2.2.2Message store function procedures  p. 453
21.2.3Update object(s) procedure  p. 453
21.2.3.1Message store client procedures  p. 453
21.2.3.2Message store function procedures  p. 453
21.2.4Delete stored object(s) procedure  p. 454
21.2.4.1Message store client procedures  p. 454
21.2.4.2Message store function procedures  p. 454
21.2.5Void  p. …
21.2.5ADeposit an object procedure  p. 454
21.2.5A.1MCData server procedures  p. 454
21.2.5A.2Message store function procedures  p. 455
21.2.6Object and folder copy procedure  p. 455
21.2.6.1Message store client procedures  p. 455
21.2.6.2Message store function procedures  p. 456
21.2.7Deleting a folder procedure  p. 456
21.2.7.1Message store client procedures  p. 456
21.2.7.2Message store function procedures  p. 456
21.2.8Create a folder procedure  p. 456
21.2.8.1Message store client procedures  p. 456
21.2.8.2Message store function procedures  p. 457
21.2.9Void  p. …
21.2.10Moving object(s) and folder(s) procedure  p. 457
21.2.10.1Message store client procedures  p. 457
21.2.10.2Message store function procedures  p. 457
21.2.11Folder search procedure  p. 458
21.2.11.1Message store client procedures  p. 458
21.2.11.2Message store function procedures  p. 458
21.2.12Void  p. …
21.2.12ACreate a subscription to notifications procedure  p. 458
21.2.12A.1Message store client procedures  p. 458
21.2.12A.2Message store function procedures  p. 459
21.2.13Void  p. …
21.2.13ADelete a subscription to notifications procedure  p. 459
21.2.13A.1Message store client procedures  p. 459
21.2.13A.2Message store function procedures  p. 459
21.2.14Void  p. …
21.2.14AUpdate a subscription to notifications procedure  p. 460
21.2.14A.1Message store client procedures  p. 460
21.2.14A.2Message store function procedures  p. 460
21.2.15Object(s) upload procedure  p. 460
21.2.15.1Message store client procedures  p. 460
21.2.15.2Message store function procedures  p. 461
21.2.16Synchronization notifications procedure  p. 461
21.2.16.1Message store function procedures  p. 461
21.2.16.2Message store client procedures  p. 461
21.2.16.3MCData Notification server procedures |R17|  p. 462
21.2.17Search-based synchronization procedure  p. 462
21.2.17.1Message store client procedures  p. 462
21.2.17.2Message store function procedures  p. 462
21.2.18Retrieve content of a given folder procedure  p. 462
21.2.18.1Message store client procedures  p. 462
21.2.18.2Message store function procedures  p. 463
21.2.19Create notification channel procedure |R17|  p. 463
21.2.19.1Message notification client procedures  p. 463
21.2.19.2MCData Notification server procedures  p. 463
21.2.20Delete notification channel procedure |R17|  p. 464
21.2.20.1Message notification client procedures  p. 464
21.2.20.2MCData Notification server procedures  p. 464
21.2.21Update notification channel procedure |R17|  p. 464
21.2.21.1Message notification client procedures  p. 464
21.2.21.2MCData Notification server procedures  p. 465
21.2.22Open notification channel procedure |R17|  p. 465
21.2.22.1Message notification client procedures  p. 465
21.2.22.2MCData Notification server procedures  p. 466
21.2.23List folder hierarchy procedure |R17|  p. 466
21.2.23.1Message store client procedures  p. 466
21.2.23.2Message store function procedures  p. 466
21.2.24Retrieve file to store locally procedure |R17|  p. 467
21.2.24.1Message store client procedures  p. 467
21.2.24.2Message store function procedures  p. 467
21.3Control of communications storage procedures |R17|  p. 468
21.3.1General  p. 468
21.3.2MCData Client procedures  p. 468
21.3.2.1General  p. 468
21.3.2.2Enable communications storage into message store procedures.  p. 468
21.3.2.3Disable communications storage into message store procedures.  p. 469
21.3.3Participating MCData function procedures  p. 470
21.3.3.1General  p. 470
21.3.3.2Control communications storage into message store procedures.  p. 470
22Functional alias |R16|  p. 472
22.1General  p. 472
22.2Procedures  p. 472
22.2.1MCData client procedures  p. 472
22.2.1.1General  p. 472
22.2.1.2Functional alias status change procedure  p. 473
22.2.1.3Functional alias status determination procedure  p. 474
22.2.1.4Location based functional alias status change procedure  p. 475
22.2.2MCData server procedures  p. 475
22.2.2.1General  p. 475
22.2.2.2Procedures of MCData server serving the MCData user  p. 475
22.2.2.2.1General  p. 475
22.2.2.2.2Stored information  p. 475
22.2.2.2.3Receiving functional alias status change from MCData client procedure  p. 476
22.2.2.2.4Receiving subscription to functional alias status procedure  p. 478
22.2.2.2.5Sending notification of change of functional alias status procedure  p. 479
22.2.2.2.6Sending functional alias status change towards MCData server owning the functional alias procedure  p. 479
22.2.2.2.7Functional alias status determination from MCData server owning functional alias procedure  p. 481
22.2.2.2.8Functional alias resolution from MCData server owning the functional alias procedure |R17|  p. 483
22.2.2.2.9Forwarding subscription to functional alias status towards another MCData server procedure |R17|  p. 484
22.2.2.3Procedures of MCData server owning the functional alias  p. 485
22.2.2.3.1General  p. 485
22.2.2.3.2Stored information  p. 485
22.2.2.3.3Receiving functional alias status change procedure  p. 486
22.2.2.3.4Receiving subscription to functional alias status procedure  p. 488
22.2.2.3.5Sending notification of change of functional alias status procedure  p. 488
22.2.2.3.6Functional alias status automatic deactivation procedure  p. 489
22.2.2.3.7Receiving subscription to functional alias resolution procedure |R17|  p. 489
22.2.2.3.8Sending notification to functional alias resolution procedure |R17|  p. 490
22.3Coding  p. 490
22.3.1Extension of application/pidf+xml MIME type  p. 490
22.3.1.1Introduction  p. 490
22.3.1.2Syntax  p. 490
22.3.2Extension of application/simple-filter+xml MIME type  p. 492
22.3.2.1Introduction  p. 492
22.3.2.2Syntax  p. 492
22.4Functional alias to group binding for the MCData user procedures |R17|  p. 493
22.4.1General  p. 493
22.4.2On-network functional alias to group binding  p. 493
22.4.2.1Client procedures  p. 493
22.4.2.1.1General  p. 493
22.4.2.1.2Functional alias to group binding  p. 493
22.4.2.1.3Functional alias to group unbinding  p. 494
22.4.2.2Participating MCData function procedures  p. 495
22.4.2.2.1General  p. 495
22.4.2.2.2Receipt of a SIP MESSAGE request for binding/unbinding of a functional alias with the MCData group(s) for the MCData user  p. 495
22.4.2.3Controlling MCData function procedures  p. 497
22.4.2.3.1General  p. 497
22.4.2.3.2Receipt of a SIP MESSAGE request for binding/unbinding of a functional alias with the MCData group(s) for the MCData user  p. 497
23Regroup using a preconfigured group |R17|  p. 498
23.1General  p. 498
23.2Group regroup using a preconfigured group  p. 498
23.2.1Client procedures  p. 498
23.2.1.1Requesting a group regroup using a preconfigured group  p. 498
23.2.1.2Removing a regroup using preconfigured group  p. 499
23.2.1.3Receiving a notification of creation of a regroup using preconfigured group  p. 500
23.2.1.4Receiving notification of removal of a regroup using preconfigured group  p. 501
23.2.2Participating MCData function procedures  p. 501
23.2.2.1General  p. 501
23.2.2.2Requesting a group regroup using a preconfigured group  p. 501
23.2.2.3Removing a regroup using preconfigured group  p. 502
23.2.2.4Notification of creation of a regroup using preconfigured group  p. 504
23.2.2.5Notification of removal of a regroup using preconfigured group  p. 504
23.2.3Controlling MCData function procedures  p. 505
23.2.3.1Request to create a group regroup using preconfigured group  p. 505
23.2.3.2Request to remove a regroup using preconfigured group  p. 507
23.2.3.3Decision to remove a regroup using preconfigured group  p. 509
23.2.4Non-controlling MCData function procedures  p. 510
23.2.4.1Notification of creation of a group regroup using preconfigured group  p. 510
23.2.4.2Notification of removal of a group regroup using preconfigured group  p. 511
23.2.4.3Notification of additional members of a group regroup using preconfigured group  p. 512
23.3User regroup using a preconfigured group  p. 512
23.3.1Client procedures  p. 512
23.3.1.1Requesting a user regroup using a preconfigured group  p. 512
23.3.1.2Removing a regroup using preconfigured group  p. 513
23.3.1.3Creating a user regroup using preconfigured group  p. 513
23.3.1.4Removing a user regroup using preconfigured group  p. 513
23.3.2Participating MCData function procedures  p. 514
23.3.2.1General  p. 514
23.3.2.2Requesting a user regroup using a preconfigured group  p. 514
23.3.2.3Removing a regroup using preconfigured group  p. 515
23.3.2.4Notification of creation of a user regroup using preconfigured group  p. 515
23.3.2.5Notification of removal of a user regroup using preconfigured group  p. 516
23.3.3Controlling MCData function procedures  p. 516
23.3.3.1Request to create a user regroup using preconfigured group  p. 516
23.3.3.2Request to remove a user regroup using preconfigured group  p. 518
23.3.3.3Decision to remove a regroup using preconfigured group  p. 518
24Adhoc group data communication |R18|  p. 518
24.1General  p. 518
24.2MCData client procedures  p. 518
24.2.1General  p. 518
24.2.2Adhoc group data communication setup  p. 518
24.2.2.1Data communication setup procedures using on-demand session  p. 519
24.2.2.1.1Client originating procedures  p. 519
24.2.2.1.2Client terminating procedures  p. 522
24.2.2.2Data communication setup procedures using pre-established session  p. 524
24.2.2.2.1Client originating procedures  p. 524
24.2.2.2.2Client terminating procedures  p. 528
24.2.3Adhoc group data communication release  p. 528
24.2.3.1Data communication release procedures using on-demand session  p. 528
24.2.3.1.1Client originating procedures  p. 528
24.2.3.1.2Client terminating procedures  p. 528
24.2.3.2Data communication release procedures using pre-established session  p. 528
24.2.3.2.1Client originating procedures  p. 528
24.2.4Adhoc group data communication leave  p. 529
24.2.4.1Data communication leave procedures using on-demand session  p. 529
24.2.4.1.1Client originating procedures  p. 529
24.2.4.1.2Client terminating procedures  p. 529
24.2.4.2Data communication leave procedures using pre-established session  p. 530
24.2.4.2.1Client originating procedures  p. 530
24.2.5Adhoc group data communication rejoin  p. 530
24.2.5.1Data communication rejoin procedures using on-demand session  p. 530
24.2.5.1.1Client originating procedures  p. 530
24.2.5.2Data communication rejoin procedures using pre-established session  p. 531
24.2.5.2.1Client originating procedures  p. 531
24.2.6Adhoc group data communication participants modify  p. 531
24.2.6.1Modification of the participant list or criteria for the participant list procedures using on-demand session  p. 531
24.2.6.1.1Client originating procedures  p. 531
24.2.7Ad hoc group determination |R19|  p. 532
24.2.7.1General  p. 532
24.2.7.2Sending a SIP MESSAGE request for ad hoc group determination  p. 532
24.2.8Ad hoc group data communication notifications |R19|  p. 533
24.2.8.1Receiving notification of ad hoc group data communication redirection  p. 533
24.3Participating MCData function procedures  p. 533
24.3.1General  p. 533
24.3.2Adhoc group data communication setup  p. 533
24.3.2.1Data communication setup procedures using on-demand session  p. 533
24.3.2.1.1Originating procedures  p. 533
24.3.2.1.2Terminating procedures  p. 536
24.3.2.2Data communication setup procedures using pre-established session  p. 540
24.3.2.2.1Originating procedures  p. 540
24.3.2.2.2Terminating procedures  p. 543
24.3.3Adhoc group data communication release  p. 543
24.3.3.1Data communication release procedures using on-demand session  p. 543
24.3.3.1.1Originating procedures  p. 543
24.3.3.1.2Terminating procedures  p. 543
24.3.3.2Data communication release procedures using pre-established session  p. 543
24.3.3.2.1Originating procedures  p. 543
24.3.3.2.2Terminating procedures  p. 544
24.3.4Adhoc group data communication rejoin  p. 544
24.3.4.1Data communication rejoin procedures using on-demand session  p. 544
24.3.4.1.1Originating procedures  p. 544
24.3.4.2Data communication rejoin procedures using pre-established session  p. 545
24.3.4.2.1Originating procedures  p. 545
24.3.5Adhoc group data communication participants modify  p. 545
24.3.5.1Data communication participants modify procedures using on-demand session  p. 545
24.3.5.1.1Originating procedures  p. 545
24.3.5.2Data communication participants modify procedures initiated by participating MCData function  p. 546
24.3.5.2.1Originating procedures  p. 546
24.3.6Adhoc group data communication participants determination  p. 547
24.3.6.1Data communication participants determination procedures  p. 548
24.3.6.2Data communication participants determination stop procedures  p. 549
24.3.7Ad hoc group determination |R19|  p. 549
24.3.7.1General  p. 549
24.3.7.2Receiving a SIP MESSAGE request for ad hoc group determination  p. 549
24.3.8Notification of ad hoc group data communication redirection |R19|  p. 551
24.4Controlling MCData function procedures  p. 551
24.4.1General  p. 551
24.4.2Adhoc group data communication setup  p. 552
24.4.2.1Originating Procedures  p. 552
24.4.2.1.1INVITE targeted to an MCData client  p. 552
24.4.2.2Terminating Procedures  p. 554
24.4.3Adhoc group data communication release  p. 557
24.4.3.1Originating Procedures  p. 557
24.4.3.1.1SIP BYE request for releasing MCData session |R19|  p. 557
24.4.3.1.2SIP BYE request for releasing MCData client from MCData session |R19|  p. 557
24.4.3.2Terminating Procedures  p. 558
24.4.4Adhoc group data communication rejoin  p. 558
24.4.4.1Data communication rejoin procedures using on-demand session  p. 558
24.4.4.1.1Terminating procedures  p. 558
24.4.5Adhoc group data communication participants modify  p. 559
24.4.5.1Modification of the participant list or criteria for the participant list procedures using on-demand session  p. 559
24.4.5.1.1Terminating procedures  p. 559
24.4.5.2Data communication participants modify procedures initiated by participating MCData function  p. 561
24.4.5.2.1Terminating procedures  p. 561
24.4.6Adhoc group data communication participants determination  p. 562
24.4.6.1Data communication participants determination procedures  p. 562
24.4.6.2Data communication participants determination stop procedures  p. 563
24.4.6.3Generating a SIP MESSAGE request to the participant lists of an MCData adhoc group with redirection information |R19|  p. 564
24.4.7Ad hoc group determination |R19|  p. 564
24.4.7.1General  p. 564
24.4.7.2Receiving a SIP MESSAGE request for ad hoc group determination  p. 565
25Subscription to the conference event package |R18|  p. 565
25.1General  p. 565
25.2MCData client  p. 566
25.3Participating MCData function  p. 567
25.4Controlling MCData function  p. 568
25.4.1Receiving a subscription to the conference event package  p. 568
25.4.2Sending notifications to the conference event package  p. 568
25.4.3Terminating a subscription  p. 569
25.6Coding  p. 569
25.6.1Extension of application/conference-info+xml MIME type  p. 569
25.6.1.1Introduction  p. 569
25.6.1.2Schema  p. 569
ASignalling flows  p. 570
B(Normative)  Media feature tags within the current document  p. 571
B.1General |R17|  p. 571
B.2Definition of media feature tag for Mission Critical Data (MCData) communications Short Data Service (SDS)  p. 571
B.3Definition of media feature tag for Mission Critical Data (MCData) communications File Distribution (FD)  p. 571
B.4Definition of media feature tag for Mission Critical Data (MCData) communications IP Connectivity (IPCONN) |R16|  p. 572
C(Normative)  ICSI values defined within the current document  p. 573
C.1General |R17|  p. 573
C.2Definition of ICSI value for the Mission Critical Data (MCData) service  p. 573
C.2.1URN  p. 573
C.2.2Description  p. 573
C.2.3Reference  p. 573
C.2.4Contact  p. 573
C.2.5Registration of subtype  p. 573
C.2.6Remarks  p. 573
C.3Definition of ICSI value for the Mission Critical Data (MCData) communications Short Data Service (SDS)  p. 574
C.3.1URN  p. 574
C.3.2Description  p. 574
C.3.3Reference  p. 574
C.3.4Contact  p. 574
C.3.5Registration of subtype  p. 574
C.3.6Remarks  p. 574
C.4Definition of ICSI value for Mission Critical Data (MCData) communications File Distribution (FD)  p. 574
C.4.1URN  p. 574
C.4.2Description  p. 574
C.4.3Reference  p. 575
C.4.4Contact  p. 575
C.4.5Registration of subtype  p. 575
C.4.6Remarks  p. 575
C.5Definition of ICSI value for Mission Critical Data (MCData) communications IP Connectivity (IPCONN) |R16|  p. 575
C.5.1URN  p. 575
C.5.2Description  p. 575
C.5.3Reference  p. 575
C.5.4Contact  p. 575
C.5.5Registration of subtype  p. 575
C.5.6Remarks  p. 576
D(Normative)  XML schemas  p. 577
D.1XML schema for transporting MCData identities and general services information  p. 577
D.1.1General  p. 577
D.1.2XML schema  p. 577
D.1.3Semantic  p. 579
D.1.4IANA registration template  p. 585
D.2Void  p. …
D.3XML schema for MCData (de)-affiliation requests  p. 587
D.3.1General  p. 587
D.3.2XML schema  p. 587
D.3.3Semantic  p. 587
D.3.4IANA registration template  p. 588
D.4XML schema for MCData location information |R16|  p. 589
D.4.1General  p. 589
D.4.2XML schema  p. 589
D.4.3Semantic  p. 598
D.4.4IANA registration template  p. 608
D.5XML schema for MBMS usage information |R16|  p. 609
D.5.1General  p. 609
D.5.2XML schema  p. 609
D.5.3Semantic  p. 611
D.5.4IANA registration template  p. 613
D.6XML schema for regroup using preconfigured group |R17|  p. 615
D.6.1General  p. 615
D.6.2XML schema  p. 615
D.6.3Semantic  p. 616
D.6.4IANA registration template  p. 617
D.7XML schema for control of communications storage |R17|  p. 618
D.7.1General  p. 618
D.7.2XML schema  p. 618
D.7.3Semantic  p. 619
D.7.4IANA registration template  p. 619
D.8XML schema for 5G MBS usage information |R18|  p. 621
D.8.1General  p. 621
D.8.2XML schema  p. 621
D.8.3Semantic  p. 624
D.8.4IANA registration template  p. 626
E(Normative)  IANA registration forms  p. 628
E.1MIME type for transporting MCData signalling content  p. 628
E.2MIME type for transporting MCData payload content  p. 629
F(Normative)  Timers  p. 632
F.1General  p. 632
F.2On-network timers  p. 632
F.2.1Timers in the participating MCData function  p. 632
F.2.2Timers in the controlling MCData function  p. 633
F.2.3Timers in the MCData UE  p. 634
F.3Off-network timers  p. 634
F.3.1Timers in off-network SDS  p. 634
F.3.2Timers in off-network emergency alert |R16|  p. 635
G(Normative)  Counters and states  p. 637
G.1General  p. 637
G.2On-network counters  p. 637
G.3Off-network counters  p. 637
G.3.1Counters in off-network SDS  p. 637
G.4On-network emergency related states |R16|  p. 637
G.4.1MCData emergency alert state  p. 637
G.4.2MCData emergency state  p. 638
G.4.3In-progress emergency group state  p. 639
G.4.4MCData emergency group state  p. 639
G.4.5MCData emergency group communication state  p. 640
G.4.6In-progress imminent peril group state |R17|  p. 641
G.4.7MCData imminent peril group state |R17|  p. 641
G.4.8MCData imminent peril group communication state |R17|  p. 642
G.4.9In-progress emergency private communication state |R17|  p. 643
G.4.10MCData emergency private priority state |R17|  p. 643
G.4.11MCData emergency private communication state |R17|  p. 644
G.4.12MCData private emergency alert state |R17|  p. 645
G.4.13MCData adhoc group emergency alert state |R18|  p. 646
HINFO packages defined in the present document  p. 648
H.1Info package for indication of communication release  p. 648
H.1.1Scope  p. 648
H.1.2g.3gpp.mcdata-com-release info package  p. 648
H.1.2.1Overall description  p. 648
H.1.2.2Applicability  p. 648
H.1.2.3Appropriateness of INFO Package Usage  p. 648
H.1.2.4Info package name  p. 648
H.1.2.5Info package parameters  p. 649
H.1.2.6SIP options tags  p. 649
H.1.2.7INFO message body parts  p. 649
H.1.2.8Info package usage restrictions  p. 649
H.1.2.9Rate of INFO Requests  p. 649
H.1.2.10Info package security considerations  p. 649
H.1.2.11Implementation details and examples  p. 649
I(Normative)  MCData session control specific concepts for the support of mission critical services over 5GS |R17|  p. 649
I.1General  p. 649
I.3Mapping of EPS-specific terms to 5GS  p. 650
I.3.1Session aspects  p. 650
I.3.2Bearer aspects  p. 650
I.3.3Resource sharing  p. 650
I.3.4Mapping of MBMS terms to MBS |R18|  p. 650
I.3.5Mapping of ProSe terms to 5G ProSe |R18|  p. 650
I.2Aspects not applicable to 5GS  p. 651
$Change history  p. 652

Up   Top