Tech-
invite
3GPP
space
IETF
RFCs
SIP
Quick
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TS 24.282
Word version: 17.4.0
1…
4…
6…
7…
8…
9…
10…
11…
12…
13…
14…
15…
16…
17…
18…
19…
20…
21…
22…
23…
A…
6
Common procedures
6.1
Introduction
6.2
MCData client procedures
6.3
MCData server procedures
6.4
Handling of MIME bodies in a SIP message
6.5
Confidentiality and Integrity Protection of sensitive XML content
6.5.1
General
6.5.2
Confidentiality Protection
6.5.3
Integrity Protection of XML documents
6.6
Confidentiality and Integrity Protection of TLV messages
...
6
Common procedures
Word‑p. 43
6.1
Introduction
Word‑p. 43
6.2
MCData client procedures
Word‑p. 43
6.2.1
Distinction of requests at the MCData client
Word‑p. 43
6.2.1.1
SIP MESSAGE request
Word‑p. 43
6.2.1.2
SIP INVITE request
|R16|
Word‑p. 44
6.2.2
MCData conversation items
Word‑p. 45
6.2.2.1
Generating an SDS Message
Word‑p. 45
6.2.2.2
Generating an FD Message for FD using HTTP
Word‑p. 46
6.2.2.3
Generating an FD Message for FD using media plane
Word‑p. 47
6.2.2.4
Client generating message to terminate FD over HTTP
|R15|
Word‑p. 47
6.2.3
Disposition Notifications
Word‑p. 48
6.2.3.1
Generating an SDS Notification
Word‑p. 48
6.2.3.2
Generating an FD Notification
Word‑p. 49
6.2.4
Sending SIP requests and receiving SIP responses
Word‑p. 49
6.2.4.1
Generating a SIP MESSAGE request towards the originating participating MCData function
Word‑p. 49
6.2.5
Location information
|R16|
Word‑p. 50
6.2.5.1
Location information for location reporting
Word‑p. 50
6.2.6
Void
6.2.7
Handling of in-progress emergency and imminent peril conditions
|R17|
Word‑p. 50
6.2.7.1
MCData upgrade to in-progress emergency or in-progress imminent peril
Word‑p. 50
6.2.7.2
MCData in-progress emergency cancel
Word‑p. 51
6.2.7.3
MCData in-progress imminent peril cancel
Word‑p. 53
6.2.7.4
MCData client receives SIP re-INVITE request
Word‑p. 54
6.2.7.5
MCData group in-progress emergency group state cancel
Word‑p. 55
6.2.8
Priority communication conditions
|R17|
Word‑p. 57
6.2.8.1
MCData emergency group communication and imminent peril communication conditions
Word‑p. 57
6.2.8.1.1
SIP INVITE request or SIP REFER request for originating MCData emergency group communications
Word‑p. 57
6.2.8.1.2
Resource-Priority header field for MCData emergency group communications
Word‑p. 58
6.2.8.1.3
SIP re-INVITE request for cancelling MCData in-progress emergency group state
Word‑p. 58
6.2.8.1.4
Receiving a SIP 2xx response to a SIP request for a priority communication
Word‑p. 59
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
Word‑p. 60
6.2.8.1.6
Determining authorisation for initiating or cancelling an MCData emergency alert
Word‑p. 60
6.2.8.1.7
Determining authorisation for cancelling the in-progress emergency state of an MCData group
Word‑p. 61
6.2.8.1.8
Determining authorisation for originating a priority group communication
Word‑p. 61
6.2.8.1.9
SIP request for originating MCData imminent peril group communications
Word‑p. 62
6.2.8.1.10
Determining authorisation for cancelling an imminent peril group communication
Word‑p. 62
6.2.8.1.11
SIP re-INVITE request for cancelling MCData in-progress imminent peril group state
Word‑p. 63
6.2.8.1.12
Resource-Priority header field for MCData imminent peril group communications
Word‑p. 63
6.2.8.1.13
Receiving a SIP INFO request in the dialog of a SIP request for a priority group communication
Word‑p. 63
6.2.8.1.14
SIP re-INVITE request for cancelling the in-progress emergency group state of a group by a third-party
Word‑p. 64
6.2.8.1.15
Retrieving Resource-Priority header field values
Word‑p. 65
6.2.8.1.16
Handling receipt of a SIP re-INVITE request for priority group communication origination status within a pre-established session
Word‑p. 65
6.2.8.1.17
Priority group communication conditions upon receiving communication release
Word‑p. 66
6.2.8.1.18
Emergency private (one-to-one) communication conditions upon receiving communication release
Word‑p. 67
6.3
MCData server procedures
Word‑p. 67
6.3.1
Distinction of requests at the MCData server
Word‑p. 67
6.3.1.1
SIP MESSAGE request
Word‑p. 67
6.3.1.2
SIP INVITE request
Word‑p. 70
6.3.2
Sending SIP requests and receiving SIP responses
Word‑p. 72
6.3.2.1
Generating a SIP MESSAGE request towards the terminating MCData client
Word‑p. 72
6.3.2.2
Generating a SIP MESSAGE request towards the controlling MCData function
|R17|
Word‑p. 72
6.3.3
Retrieving a group document
Word‑p. 73
6.3.4
Determining targeted group members for MCData communications
Word‑p. 73
6.3.5
Affiliation check
Word‑p. 73
6.3.6
MCData conversation items
|R15|
Word‑p. 74
6.3.6.1
Server generating a FD HTTP TERMINATION message for FD over HTTP
Word‑p. 74
6.3.7
Procedures referenceable from other procedures
|R16|
Word‑p. 74
6.3.7.1
Emergency alert and emergency communications procedures
Word‑p. 74
6.3.7.1.1
Sending a SIP re-INVITE request for MCData emergency alert or emergency group communication
Word‑p. 74
6.3.7.1.2
Generating a SIP MESSAGE request for notification of in-progress emergency status change
Word‑p. 75
6.3.7.1.3
Populate mcdata-info and location-info MIME bodies for emergency alert
Word‑p. 76
6.3.7.1.4
Retrieving Resource-Priority header field values for emergency communications
Word‑p. 76
6.3.7.1.5
Generating a SIP MESSAGE request to indicate successful receipt of an emergency alert or emergency cancellation
Word‑p. 77
6.3.7.1.6
Generating a SIP MESSAGE request for notification of entry into or exit from an emergency alert area
|R17|
Word‑p. 77
6.3.7.1.7
Generating a SIP MESSAGE request for notification of entry into or exit from a group geographic area
|R17|
Word‑p. 78
6.3.7.1.8
Sending a SIP re-INVITE request for MCData imminent peril group communication
|R17|
Word‑p. 79
6.3.7.1.9
Validate priority request parameters
|R17|
Word‑p. 79
6.3.7.1.10
Sending a SIP INFO request in the dialog of a SIP request for a priority communication
|R17|
Word‑p. 80
6.3.7.1.11
Sending a SIP INVITE request for MCData emergency group communication
|R17|
Word‑p. 80
6.3.7.1.12
Sending a SIP UPDATE request for Resource-Priority header field correction
|R17|
Word‑p. 81
6.3.7.1.13
Generating a SIP re-INVITE request
|R17|
Word‑p. 82
6.3.7.1.14
Generating a SIP re-INVITE request to cancel an in-progress emergency
|R17|
Word‑p. 82
6.3.7.2
Authorisations
Word‑p. 83
6.3.7.2.1
Determining authorisation for initiating an MCData emergency alert
Word‑p. 83
6.3.7.2.2
Determining authorisation for cancelling an MCData emergency alert
Word‑p. 84
6.3.7.2.3
Determining authorisation for cancelling an MCData emergency communication
Word‑p. 84
6.3.7.2.4
Determining authorisation for initiating an MCData imminent peril communication
|R17|
Word‑p. 84
6.3.7.2.5
Determining authorisation for cancelling an MCData imminent peril communication
|R17|
Word‑p. 85
6.3.7.2.6
Determining authorisation for initiating an MCData emergency group or private communication
|R17|
Word‑p. 85
6.3.7.2.7
Generating a SIP 403 response for priority communication request rejection
|R17|
Word‑p. 86
6.3.8
Disposition Notifications
|R17|
Word‑p. 87
6.3.8.1
Generating an FD Notification
Word‑p. 87
6.4
Handling of MIME bodies in a SIP message
Word‑p. 87
6.5
Confidentiality and Integrity Protection of sensitive XML content
Word‑p. 88
6.5.1
General
Word‑p. 88
6.5.1.1
Applicability and exclusions
Word‑p. 88
6.5.1.2
Performing XML content encryption
Word‑p. 88
6.5.1.3
Performing integrity protection on an XML body
Word‑p. 88
6.5.1.4
Verifying integrity of an XML body and decrypting XML elements
Word‑p. 88
6.5.2
Confidentiality Protection
Word‑p. 89
6.5.2.1
General
Word‑p. 89
6.5.2.2
Keys used in confidentiality protection procedures
Word‑p. 89
6.5.2.3
Procedures for sending confidentiality protected content
Word‑p. 89
6.5.2.3.1
MCData client
Word‑p. 89
6.5.2.3.2
MCData server
Word‑p. 90
6.5.2.3.3
Content Encryption in XML elements
Word‑p. 90
6.5.2.3.4
Attribute URI Encryption
Word‑p. 90
6.5.2.4
Procedures for receiving confidentiality protected content
Word‑p. 91
6.5.2.4.1
Determination of confidentiality protected content
Word‑p. 91
6.5.2.4.2
Decrypting confidentiality protected content in XML elements
Word‑p. 91
6.5.2.4.3
Decrypting confidentiality protected URIs in XML attributes
Word‑p. 91
6.5.2.5
MCData server copying received XML content
Word‑p. 92
6.5.3
Integrity Protection of XML documents
Word‑p. 92
6.5.3.1
General
Word‑p. 92
6.5.3.2
Keys used in integrity protection procedures
Word‑p. 94
6.5.3.3
Sending integrity protected content
Word‑p. 94
6.5.3.3.1
MCData client
Word‑p. 94
6.5.3.3.2
MCData server
Word‑p. 94
6.5.3.3.3
Integrity protection procedure
Word‑p. 95
6.5.3.4
Receiving integrity protected content
Word‑p. 95
6.5.3.4.1
Determination of integrity protected content
Word‑p. 95
6.5.3.4.2
Verification of integrity protected content
Word‑p. 95
6.6
Confidentiality and Integrity Protection of TLV messages
Word‑p. 96
6.6.1
General
Word‑p. 96
6.6.2
Derivation of master keys for media and media control
Word‑p. 97
6.6.3
Protection of MCData Data signalling and MCData Data messages
Word‑p. 97
6.6.3.1
General
Word‑p. 97
6.6.3.2
The MCData client
Word‑p. 97
6.6.3.3
The participating MCData function
Word‑p. 97
6.6.3.4
The controlling MCData function
Word‑p. 98