Content for TS 24.282 Word version: 18.7.0
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.7 Stored files operational procedures
6.8 Procedures at the MCData gateway
...
...
6 Common procedures p. 53
6.1 Introduction p. 53
6.2 MCData client procedures p. 53
6.2.1 Distinction of requests at the MCData client p. 53
6.2.2 MCData conversation items p. 55
6.2.2.1 Generating an SDS Message p. 55
6.2.2.2 Generating an FD Message for FD using HTTP p. 56
6.2.2.3 Generating an FD Message for FD using media plane p. 57
6.2.2.4 Client generating message to terminate FD over HTTP |R15| p. 58
6.2.3 Disposition Notifications p. 58
6.2.4 Sending SIP requests and receiving SIP responses p. 60
6.2.4.1 Generating a SIP MESSAGE request towards the originating participating MCData function p. 60
6.2.5 Location information |R16| p. 60
6.2.6 Void
6.2.7 Handling of in-progress emergency and imminent peril conditions |R17| p. 61
6.2.7.1 MCData upgrade to in-progress emergency or in-progress imminent peril p. 61
6.2.7.2 MCData in-progress emergency cancel p. 63
6.2.7.3 MCData in-progress imminent peril cancel p. 64
6.2.7.4 MCData client receives SIP re-INVITE request p. 65
6.2.7.5 MCData group in-progress emergency group state cancel p. 67
6.2.8 Priority communication conditions |R17| p. 68
6.2.8.1 MCData emergency group communication and imminent peril communication conditions p. 68
6.2.8.1.1 SIP INVITE request or SIP REFER request for originating MCData emergency group communications p. 68
6.2.8.1.2 Resource-Priority header field for MCData emergency group communications p. 69
6.2.8.1.3 SIP re-INVITE request for cancelling MCData in-progress emergency group state p. 70
6.2.8.1.4 Receiving a SIP 2xx response to a SIP request for a priority communication p. 70
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 p. 71
6.2.8.1.6 Determining authorisation for initiating or cancelling an MCData emergency alert p. 71
6.2.8.1.7 Determining authorisation for cancelling the in-progress emergency state of an MCData group p. 72
6.2.8.1.8 Determining authorisation for originating a priority group communication p. 72
6.2.8.1.9 SIP request for originating MCData imminent peril group communications p. 73
6.2.8.1.10 Determining authorisation for cancelling an imminent peril group communication p. 73
6.2.8.1.11 SIP re-INVITE request for cancelling MCData in-progress imminent peril group state p. 74
6.2.8.1.12 Resource-Priority header field for MCData imminent peril group communications p. 74
6.2.8.1.13 Receiving a SIP INFO request in the dialog of a SIP request for a priority group communication p. 74
6.2.8.1.14 SIP re-INVITE request for cancelling the in-progress emergency group state of a group by a third-party p. 75
6.2.8.1.15 Retrieving Resource-Priority header field values p. 76
6.2.8.1.16 Handling receipt of a SIP re-INVITE request for priority group communication origination status within a pre-established session p. 76
6.2.8.1.17 Priority group communication conditions upon receiving communication release p. 77
6.2.8.1.18 Emergency private (one-to-one) communication conditions upon receiving communication release p. 78
6.2.8.2 Void
6.2.8.3 MCData emergency private (one-to-one) communication conditions p. 78
6.2.8.3.1 Authorisations p. 78
6.2.8.3.1.1 Determining authorisation for initiating an MCData emergency private communication p. 78
6.2.8.3.1.2 Determining authorisation for cancelling an MCData emergency private communication p. 78
6.2.8.3.1.3 Determining authorisation for initiating or cancelling an MCData emergency alert to a MCData user p. 79
6.2.8.3.2 SIP request for originating MCData emergency private communications p. 79
6.2.8.3.3 Resource-Priority header field for MCData emergency private communications p. 79
6.2.8.3.4 Receiving a SIP 2xx response to a SIP request for an MCData emergency private communication p. 80
6.2.8.3.5 Receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to a SIP request for an MCData emergency private communication p. 80
6.2.8.3.6 SIP re-INVITE request for cancelling MCData emergency private communication state p. 80
6.2.8.3.7 Receiving a SIP INFO request in the dialog of a SIP request for a priority private communication p. 81
6.2.8.3.8 SIP re-INVITE request for cancelling the MCData emergency private communication state by a third-party p. 82
6.2.8.3.9 Retrieving a KMS URI associated with an MCData ID p. 82
6.2.8.4 Procedures for modifying ongoing communications p. 83
6.2.8.4.1 Cancelling or ending ongoing client terminating procedures p. 83
6.2.8.4.2 Client terminating procedures for handling SIP re-INVITE for an existing one-to-one communication session p. 84
6.2.8.4.3 MCData in-progress emergency one-to-one communication cancellation p. 85
6.2.8.4.4 Upgrade to MCData emergency one-to-one communication p. 86
6.3 MCData server procedures p. 87
6.3.1 Distinction of requests at the MCData server p. 87
6.3.1.1 SIP MESSAGE request p. 87
6.3.1.2 SIP INVITE request p. 91
6.3.1.3 SIP SUBSCRIBE request |R18| p. 93
6.3.2 Sending SIP requests and receiving SIP responses p. 93
6.3.2.1 Generating a SIP MESSAGE request towards the terminating MCData client p. 93
6.3.2.2 Generating a SIP MESSAGE request towards the controlling MCData function |R17| p. 93
6.3.2.3 Generating a SIP NOTIFY request |R18| p. 94
6.3.3 Retrieving a group document p. 95
6.3.4 Determining targeted group members for MCData communications p. 95
6.3.5 Affiliation check p. 96
6.3.6 MCData conversation items |R15| p. 96
6.3.7 Procedures referenceable from other procedures |R16| p. 96
6.3.7.1 Emergency alert and emergency communications procedures p. 96
6.3.7.1.1 Sending a SIP re-INVITE request for MCData emergency alert or emergency group communication p. 96
6.3.7.1.2 Generating a SIP MESSAGE request for notification of in-progress emergency status change p. 97
6.3.7.1.3 Populate mcdata-info and location-info MIME bodies for emergency alert p. 98
6.3.7.1.4 Retrieving Resource-Priority header field values for emergency communications p. 99
6.3.7.1.5 Generating a SIP MESSAGE request to indicate successful receipt of an emergency alert or emergency cancellation p. 99
6.3.7.1.6 Generating a SIP MESSAGE request for notification of entry into or exit from an emergency alert area |R17| p. 100
6.3.7.1.7 Generating a SIP MESSAGE request for notification of entry into or exit from a group geographic area |R17| p. 101
6.3.7.1.8 Sending a SIP re-INVITE request for MCData imminent peril group communication |R17| p. 102
6.3.7.1.9 Validate priority request parameters |R17| p. 102
6.3.7.1.10 Sending a SIP INFO request in the dialog of a SIP request for a priority communication |R17| p. 103
6.3.7.1.11 Sending a SIP INVITE request for MCData emergency group communication |R17| p. 103
6.3.7.1.12 Sending a SIP UPDATE request for Resource-Priority header field correction |R17| p. 104
6.3.7.1.13 Generating a SIP re-INVITE request |R17| p. 105
6.3.7.1.14 Generating a SIP re-INVITE request to cancel an in-progress emergency |R17| p. 105
6.3.7.1.15 Receipt of SIP re-INVITE request by terminating participating function |R17| p. 106
6.3.7.1.16 Generating a SIP re-INVITE request for emergency private (one-to-one) communication origination within a pre-established session |R17| p. 106
6.3.7.1.17 Receiving a SIP re-INVITE request by the terminating participating function |R17| p. 108
6.3.7.1.18 Receipt of SIP re-INVITE for MCData one-to-one communication from the served user |R17| p. 108
6.3.7.1.19 Controlling MCData function receiving a SIP re-INVITE for upgrade to emergency one-to-one communication |R17| p. 109
6.3.7.1.20 Controlling MCData function receiving a SIP re-INVITE for cancellation of emergency one-to-one communication |R17| p. 110
6.3.7.1.21 Controlling MCData function sending a SIP re-INVITE for upgrade to emergency one-to-one communication |R17| p. 112
6.3.7.1.22 Controlling MCData function sending a SIP re-INVITE for cancellation of emergency one-to-one communication |R17| p. 112
6.3.7.1.23 Controlling MCData function generates a SIP 200 (OK) response |R17| p. 113
6.3.7.2 Authorisations p. 114
6.3.7.2.1 Determining authorisation for initiating an MCData emergency alert p. 114
6.3.7.2.2 Determining authorisation for cancelling an MCData emergency alert p. 115
6.3.7.2.3 Determining authorisation for cancelling an MCData emergency communication p. 115
6.3.7.2.4 Determining authorisation for initiating an MCData imminent peril communication |R17| p. 116
6.3.7.2.5 Determining authorisation for cancelling an MCData imminent peril communication |R17| p. 116
6.3.7.2.6 Determining authorisation for initiating an MCData emergency group or private communication |R17| p. 117
6.3.7.2.7 Generating a SIP 403 response for priority communication request rejection |R17| p. 118
6.3.8 Disposition Notifications |R17| p. 118
6.4 Handling of MIME bodies in a SIP message p. 119
6.5 Confidentiality and Integrity Protection of sensitive XML content p. 119
6.5.1 General p. 119
6.5.1.1 Applicability and exclusions p. 119
6.5.1.2 Performing XML content encryption p. 119
6.5.1.3 Performing integrity protection on an XML body p. 120
6.5.1.4 Verifying integrity of an XML body and decrypting XML elements p. 120
6.5.2 Confidentiality Protection p. 120
6.5.2.1 General p. 120
6.5.2.2 Keys used in confidentiality protection procedures p. 120
6.5.2.3 Procedures for sending confidentiality protected content p. 121
6.5.2.3.1 MCData client p. 121
6.5.2.3.2 MCData server p. 121
6.5.2.3.3 Content Encryption in XML elements p. 121
6.5.2.3.4 Attribute URI Encryption p. 122
6.5.2.4 Procedures for receiving confidentiality protected content p. 122
6.5.2.4.1 Determination of confidentiality protected content p. 122
6.5.2.4.2 Decrypting confidentiality protected content in XML elements p. 122
6.5.2.4.3 Decrypting confidentiality protected URIs in XML attributes p. 123
6.5.2.5 MCData server copying received XML content p. 123
6.5.3 Integrity Protection of XML documents p. 124
6.6 Confidentiality and Integrity Protection of TLV messages p. 127
6.6.1 General p. 127
6.6.2 Derivation of master keys for media and media control p. 128
6.6.3 Protection of MCData Data signalling and MCData Data messages p. 129
6.6.3.1 General p. 129
6.6.3.2 The MCData client p. 129
6.6.3.3 The participating MCData function p. 129
6.6.3.4 The controlling MCData function p. 129
6.7 Stored files operational procedures |R17| p. 130
6.7.1 General p. 130
6.7.2 Retrieve the stored file procedure p. 130
6.7.3 Verify the stored file availability procedure p. 131
6.8 Procedures at the MCData gateway |R17| p. 131
