13 Communication Release
24.2823GPPMission Critical Data (MCData) signalling controlProtocol specificationRelease 18TS
13.1 General
Communication Release allows MCData user or MCData server to release MCData communications on-demand or based on policies. These procedures are applicable for SDS and FD and can be initiated by communication originator or MCData server.
13.2 On-network
13.2.1 General
13.2.1.1 Server generating message for release of communication over HTTP towards participating MCData function
This procedure is only referenced from other procedures. In order to generate a SIP MESSAGE towards the participating MCData function, the MCData server:
1) shall generate SIP MESSAGE accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6];
2) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd" along with parameters "require" and "explicit" according to IETF RFC 3841 [8] in the outgoing SIP MESSAGE request;
3) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd";
4) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the participating MCData function associated to the originating MCData ID user; and
5) shall include an application/vnd.3gpp.mcdata-info+xml MIME body in the SIP MESSAGE request, following the rules specified in clause 6.4 for the handling of MIME bodies in a SIP message:
a) fill <mcdata-request-uri> element with the MCData ID of the target user.
6) shall include FD HTTP TERMINATION in application/vnd.3gpp.mcdata-signalling.
While generating an FD HTTP TERMINATION message as specified in clause 15.1.3.1, the MCData server:
1) shall set the Conversation ID IE to a value identifying the conversation, as specified in clause 15.2.9;
2) shall set the Message ID IE to a value identifying the message as specified in clause 15.2.10;
3) may set:
i) the Application ID IE to the stored value if applicable; or
ii) the Extended application ID IE to the stored value if applicable; and
4) shall include a Payload IE with:
a) the Payload content type set to "FILEURL" as specified in clause 15.2.13; and
b) Shall set the URL of the file same as of FD transmission.
13.2.1.2 Authorised user generating FD HTTP TERMINATION MESSAGE towards participating MCData function
This clause is referred from other clause only. In order to generate a SIP MESSAGE towards participating MCData function:
1) Shall generate SIP MESSAGE accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6];
2) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd" along with parameters "require" and "explicit" according to IETF RFC 3841 [8] in the outgoing SIP MESSAGE request;
3) shall include a P-preferred-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd";
4) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the participating MCData function associated to the MCData ID user; and
5) shall include an application/vnd.3gpp.mcdata-info+xml MIME body in the SIP MESSAGE request, following the rules specified in clause 6.4 for the handling of MIME bodies in a SIP message:
a) set <mcdata-request-uri> element to the MCData ID of the target user; and
b) shall include FD HTTP TERMINATION application/vnd.3gpp.mcdata-signalling. While including FD HTTP TERMINATION message according to clause E.1.
When generating an FD HTTP TERMINATION message as specified in clause 15.1.11, the MCData client:
1) shall set the Conversation ID IE to a value identifying the conversation, as specified in clause 15.2.9;
2) shall set the Message ID IE to a value identifying the message as specified in clause 15.2.10;
3) may set:
i) the Application ID IE ID to the stored value if applicable; or
ii) the Extended Application ID IE to the stored value if applicable; and
4) shall include a Payload IE with:
a) the Payload content type set to "FILEURL" as specified in clause 15.2.13; and
b) the URL of the file same as of FD transmission.
13.2.2 MCData originating user initiated communication release
13.2.2.1 General
The MCData client can release the communication to indicate MCData service that the user no longer wants to transmit.
13.2.2.2 Release of MCData communication over media plane
13.2.2.2.1 General
The procedures described in this clause are applicable to MCData SDS and MCData FD using media plane where originating MCData user initiates the communication release.
13.2.2.2.2 MCData client procedures
13.2.2.2.2.1 MCData client originating procedures
When the MCData client wants to release a MCData communication established over the media plane, the MCData client:
1) shall generate a SIP BYE request according to 3GPP TS 24.229 [5];
2) shall set the Request-URI to the MCData session identity to be released; and
3) shall send the SIP BYE request towards MCData server according to 3GPP TS 24.229 [5].
Upon receiving a SIP 200 (OK) response to the SIP BYE request, the MCData client shall release all media plane resources corresponding to the MCData communication being released.
13.2.2.2.2.2 MCData client terminating procedures
Upon receiving a SIP BYE request, the MCData client:
1) shall send SIP 200 (OK) response towards MCData server according to 3GPP TS 24.229 [5]; and
2) shall release all media plane resources corresponding to the MCData communication being released.
NOTE: Partially received data can be stored and processed.
13.2.2.2.3 Participating MCData function procedures
13.2.2.2.3.1 Originating participating MCData function procedures
Upon receiving a SIP BYE request from the MCData client, the originating participating MCData function:
1) shall generate a SIP BYE request as specified in 3GPP TS 24.229 [5];
2) shall set the Request-URI to the MCData session identity mentioned in the received SIP BYE request;
3) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP BYE request to the P-Asserted-Identity header field of the outgoing SIP BYE request; and
4) shall send the SIP BYE request toward the controlling MCData function, according to 3GPP TS 24.229 [5].
Upon receiving a SIP 200 (OK) response to the SIP BYE request the participating MCData function;
1) shall forward the SIP 200 (OK) response to the originating MCData client and release all media plane resources corresponding to the MCData communication with the originating MCData client; and
2) shall release all media plane resources corresponding to the MCData communication with the controlling MCData function.
13.2.2.2.3.2 Terminating participating MCData function procedures
Upon receiving a SIP BYE request from the controlling MCData function, the participating MCData function:
1) shall generate a SIP BYE request according to 3GPP TS 24.229 [5];
2) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP BYE request to the P-Asserted-Identity header field of the outgoing SIP BYE request; and
3) shall send the SIP BYE request to the MCData client according to 3GPP TS 24.229 [5].
Upon receiving a SIP 200 (OK) response to the SIP BYE request the participating MCData function:
1) shall send the SIP 200 (OK) response to the SIP BYE request received from the controlling MCData function according to 3GPP TS 24.229 [5] and release all media plane resources corresponding to the MCData communication with the controlling MCData function; and
2) shall release all media plane resources corresponding to the MCData communication with the terminating MCData client.
13.2.2.2.4 Controlling MCData function procedures
13.2.2.2.4.1 Communication release policy for group MCData communication
The controlling MCData function shall release the group MCData communication, if:
1) the controlling MCData function receives an indication from the media plane that the transmission time limit has reached;
2) the controlling MCData function receives an indication from the media plane that the transmission data limit per request has reached;
3) there are only one or no participants in the MCData communication;
4) according to a local policy, the initiator of the group call leaves the MCData communication; or
5) the minimum number of affiliated MCData group members is not present;
13.2.2.2.4.2 Communication release policy for one-to-one MCData communication
The controlling MCData function shall release the one-to-one MCData communication if:
1) the controlling MCData function receives an indication from the media plane that the transmission time limit has reached;
2) the controlling MCData function receives an indication from the media plane that the transmission data limit per request has reached; or
3) there are only one or no participants in the MCData communication.
13.2.2.2.4.3 Receiving a SIP BYE request
Upon receiving a SIP BYE request the controlling MCData function:
1) shall release all media plane resources corresponding to the MCData communication with the originating participating MCData function;
2) shall generate a SIP 200 (OK) response and send the SIP response towards the originating MCData client according to 3GPP TS 24.229 [5];
3) shall check the communication release policy as specified in clause 13.2.2.2.4.1 and clause 13.2.2.2.4.2 whether the MCData communication needs to be released for each participant of the MCData communication; and
4) if release of the MCData communication is required, perform the procedures as specified in the clause 13.2.2.2.4.4.
13.2.2.2.4.4 Sending a SIP BYE request
When a participant needs to be removed from the MCData communication, the controlling MCData function:
1) shall interact with the media plane as specified in 3GPP TS 24.582 [15] for the MCData communication release;
2) shall generate a SIP BYE request according to 3GPP TS 24.229 [5]; and
3) shall send the SIP BYE request to the MCData client according to 3GPP TS 24.229 [5].
If group MCData communication needs to be released, the controlling MCData function shall send SIP BYE requests as described in this clause to all the participants of the communication.
Upon receiving a SIP 200 (OK) response to a SIP BYE request, the controlling MCData function shall release all media plane resources corresponding to the MCData communication with the terminating participating MCData function.
13.2.2.3 Release of MCData communication over HTTP
13.2.2.3.1 General
The procedures described in this clause are applicable to MCData FD using HTTP where originating MCData user initiates the communication release. This procedure applicable after file upload happened successfully and originating client sends SDS message towards server.
13.2.2.3.2 MCData client procedures
13.2.2.3.2.1 MCData client originating procedures
13.2.2.3.2.1.1 Initiating Release
When MCData client wants to release MCData communication either one-to-one FD or group-FD established over HTTP, the MCData client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6] with the clarifications given below.
The MCData client:
1) shall build the SIP MESSAGE request as specified in clause 6.2.4.1;
2) if terminating one-to-one FD transmission, shall insert in the SIP MESSAGE request:
a) an application/resource-lists+xml MIME body with the MCData ID of the recipient of FD transmission in the "uri" attribute of the <entry> element of the <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body, according to rules and procedures of IETF RFC 4826 [9]; and
b) an application/vnd.3gpp.mcdata-info+xml MIME body with a <request-type> element set to a value of "one-to-one-fd";
3) if terminating group FD transmission:
a) shall insert in the SIP MESSAGE request an application/vnd.3gpp.mcdata-info+xml MIME body with:
i) the <request-type> element set to a value of "group-fd";
ii) the <mcdata-request-uri> element set to the MCData group identity for which FD transmission happening; and
iii) the <mcdata-client-id> element set to the MCData client ID of the originating MCData client;
4) shall generate a standalone FD message as specified in clause 6.2.2.4; and
5) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [5] towards originating particiapting function.
13.2.2.3.2.1.2 Receiving Release Response Type from server
Upon receiving SIP MESSAGE from server containing application/vnd.3gpp.mcdata-signalling MIME body with HTTP TERMINATION MESSAGE and FD signalling payload message identity value set as FD HTTP TERMINATION as described in clause 15.2.2 then
1) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5];
2) shall send SIP 200 (OK) response towards participating MCData function according to 3GPP TS 24.229 [5];
3) if FD HTTP TERMINATION message contains an Application ID or contains an Extended Application ID, shall deliver the FD HTTP TERMINATION message to the application; and
4) if Termination information type IE in HTTP TERMINATION MESSAGE is set to "TERMINATION RESPONSE" as specified in clause 15.2.22 and If Release Response Type IE present then:
a) set to "RELEASE SUCCESS" as described in clause 15.2.23 the notify user that termination request is successful; or
b) set to "RELEASE FAILED" as described in clause 15.2.23 then notify user that termination request failed.
13.2.2.3.2.2 MCData client terminating procedures
On receipt of a SIP MESSAGE request containing an application/vnd.3gpp.mcdata-signalling MIME body with a FD NETWORK NOTIFICATION message, the MCData client shall follow the procedure as described in clause 12.4.4.
13.2.2.3.3 Participating MCData function procedures
13.2.2.3.3.1 Originating participating MCData function procedures
Upon receipt of a "SIP MESSAGE request for FD using HTTP for originating participating MCData function", the participating MCData function should follow the procedure as describe in clause 10.2.4.3.1.
13.2.2.3.3.2 Terminating participating MCData function procedures
Upon receipt of a "SIP MESSAGE request for FD using HTTP for terminating participating MCData function", the participating MCData function should follow the procedure as describe in clause 10.2.4.3.2.
13.2.2.3.4 Controlling MCData function procedures
Upon receipt of a "SIP MESSAGE request for FD using HTTP for controlling MCData function", the controlling MCData function should follow the procedure as describe in clause 10.2.4.4.2.
13.2.3 MCData server initiated communication release without prior indication
13.2.3.1 General
Based on local policies and conditions explained in clause 13.2.2.2.4.1 and clause 13.2.2.2.4.2, MCData server can release an ongoing MCData communication. Based on the configuration, MCData server can decide to release the communication without prior notification to MCData client.
13.2.3.2 Release of MCData communication over media plane
13.2.3.2.1 General
The procedures described in this clause are applicable to MCData SDS and MCData FD using media plane where MCData server initiates communication release.
13.2.3.2.2 MCData client procedures
Upon receiving a SIP BYE request from the MCData server, the MCData client should follow the procedure described in clause 13.2.2.2.2.2 with following clarification:
1) shall notify the MCData user with reason for release of communication if SIP BYE request contains reason header.
13.2.3.2.3 Participating MCData function procedures
Upon receiving SIP BYE request from controlling MCData function, the participating MCData function should follow the procedure described in clause 13.2.2.2.3.2 with following clarification:
1) if reason header is present in the incoming SIP BYE request, shall copy the contents of the reason header field of the incoming SIP BYE request to the reason header field of the outgoing SIP BYE request.
13.2.3.2.4 Controlling MCData function procedures
Based on communication release policies and configuration, when controlling MCData function wants to release communication, the controlling MCData function should follow the procedure as described in clause 13.2.2.2.4.4 with following clarification:
1) shall add reason header with reason-text value as appropriate (e.g. data volume limit, time limit expiry).
13.2.3.3 Release of MCData communication over HTTP
13.2.3.3.1 General
This procedure described in this clause are applicable to MCData FD using HTTP where MCData server initiates communication release.
13.2.3.3.2 MCData client procedures
13.2.3.3.2.1 MCData client originating procedure
Upon receiving SIP MESSAGE from MCData server containing an application/vnd.3gpp.mcdata-signalling MIME body, the MCData client:
1) shall decode the contents of application/vnd.3gpp.mcdata-signalling MIME body;
2) if application/vnd.3gpp.mcdata-signalling MIME body contains a FD HTTP TERMINATION message as specified in clause 15.1.11 and if the Termination Information Type IE is set to "TRANSMISSION STOPPED", then:
a) shall generate a SIP 200 OK response according to 3GPP TS 24.229 [5]; and
b) shall send the SIP 200 (OK) response towards MCData server according to 3GPP TS 24.229 [5]; and
3) shall notify MCData user about file transmission being stopped by identifying the corresponding file transmission local database based on conversation id, message id and FILE URL received in FD HTTP TERMINATION message, along with reason.
13.2.3.3.2.2 MCData client terminating procedure
On receipt of a SIP MESSAGE request containing an application/vnd.3gpp.mcdata-signalling MIME body with a FD NETWORK NOTIFICATION message, the MCData client shall follow the procedures as described in clause 12.4.4.
13.2.3.3.3 Participating MCData function procedures
Upon receipt of a "SIP MESSAGE request for FD using HTTP for terminating participating MCData function", the participating MCData function shall follow the procedure as described in clause 10.2.4.3.2.
13.2.3.3.4 Controlling MCData function procedures
Base on communication release policies and configuration, when controlling MCData function wants to release communication, the controlling MCData function:
1) shall execute procedure as described in clause 12.4.2.1 to delete the file and notify to participants with following clarification:
a) shall set FD notification type IE as "FILE DELETED UNAVAILABLE TO DOWNLOAD" as specified in clause 15.2.18; and
2) shall generate SIP MESSAGE as described in clause 13.2.1.1 and
a) shall add reason header with reason-text value as appropriate (e.g. data volume limit, time limit expiry);
b) shall set Termination information type IE of FD HTTP TERMINATION MESSAGE to "TRANSMISSION STOPPED" as described in clause 15.2.22; and
c) shall send the SIP MESSAGE to MCData user who initiated the communication according to according to rules and procedures of 3GPP TS 24.229 [5].
13.2.4 MCData server initiated communication release with prior indication
13.2.4.1 General
Based on local policies and conditions as mentioned in clause 13.2.2.2.4.1 and clause 13.2.2.2.4.2, the MCData server can release an ongoing MCData communication.
If configured to, the MCData server can notify the originating MCData user about the intent to release communication and may request for more data about the communication it intends to release. The procedures described in this clause are applicable to MCData SDS and MCData FD using media plane where the MCData server initiates the communication release.
13.2.4.2 MCData client procedures for communication over media plane
13.2.4.2.1 Receiving intent to release the communication
Upon receiving a SIP INFO request within the SIP dialog of a MCData communication, with the Info-Package header field set to g.3gpp.mcdata-com-release package and containing an application/vnd.3gpp.mcdata-signalling MIME body associated with the Info-Package, the MCData client:
1) shall decode the contents of the application/vnd.3gpp.mcdata-signalling MIME body;
2) if the application/vnd.3gpp.mcdata-signalling MIME body contains a COMMUNICATION RELEASE message as specified in clause 15.1.10, with the Comm release information type IE set to "INTENT TO RELEASE", then:
a) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5];
b) shall send SIP 200 (OK) response towards MCData server according to 3GPP TS 24.229 [5]; and
c) if an Data query type IE is present and set to "REMAINING AMOUNT OF DATA", then:
i) shall generate a DATA PAYLOAD message as described in clause 15.1.4;
ii) shall generate a SIP INFO request according to 3GPP TS 24.229 [5] and IETF RFC 6086 [21];
iii) shall include in the SIP INFO request, the DATA PAYLOAD message in an application/vnd.3gpp.mcdata-payload MIME body as specified in clause E.2; and
A) shall set a Content-Disposition header field to "Info-Package" value; and
iv) shall send the SIP INFO request within the SIP dialog of the MCData communication, towards the participating MCData function according to 3GPP TS 24.229 [5]; and
3) shall notify MCData user and present the reason, if the reason header is present in incoming SIP INFO message.
When generating an DATA PAYLOAD message as specified in clause 15.1.4, the MCData client:
1) shall set the Number of payloads IE to 1:
a) shall set the Payload content type as "TEXT" as specified in clause 15.2.13; and
b) shall include the remaining amount of data in bytes to be sent in the Payload data.
Once the MCData user is notified about the MCData server’s intent to release the communication, the MCData user may request for extension of communication as described in clause 13.2.4.2.2.
13.2.4.2.2 Request for extension of communication
Upon receiving a request from MCData user for extension of the communication as a result of MCData server’s intent to release the communication, the MCData client:
1) shall generate a SIP INFO request according to 3GPP TS 24.229 [5] and IETF RFC 6086 [21];
2) shall include a Info-Package with header field set to g.3gpp.mcdata-com-release;
3) shall include in the SIP INFO request, a COMMUNICATION RELEASE message as specified in clause 15.1.10, in an application/vnd.3gpp.mcdata-signalling MIME body as specified in clause E.1; and
a) shall set a Content-Disposition header field to "Info-Package" value; and
4) shall send the SIP INFO request within the SIP dialog of the MCData communication, towards the participating MCData function according to 3GPP TS 24.229 [5].
When generating an COMMUNICATION RELEASE message as specified in clause 15.1.10, the MCData client:
1) shall set the Comm release information type to "EXTENSION REQUEST".
13.2.4.2.3 Receiving response to communication extension request
Upon receiving a SIP INFO request within the SIP dialog of a MCData communication, with the Info-Package header field set to g.3gpp.mcdata-com-release package and containing an application/vnd.3gpp.mcdata-signalling MIME body associated with the Info-Package, the MCData client:
1) shall decode the contents of application/vnd.3gpp.mcdata-signalling MIME body; and
2) if the application/vnd.3gpp.mcdata-signalling MIME body contains a COMMUNICATION RELEASE message as specified in clause 15.1.10, with the Comm release information type IE set to "EXTENSION RESPONSE", then:
a) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5];
b) shall send SIP 200 (OK) response towards MCData server according to 3GPP TS 24.229 [5]; and
c) shall notify user about extension response based on Extension Response Type IE.
13.2.4.3 Participating MCData function procedures for communication over media plane
13.2.4.3.1 Receiving SIP INFO request from the controlling MCData function
Upon receiving a SIP INFO request with the Info-Package header field set to g.3gpp.mcdata-com-release package, from controlling MCData function within the SIP dialog of the MCData communication, the participating MCData function:
1) shall generate a SIP INFO request according to 3GPP TS 24.229 [5] and IETF RFC 6086 [21];
2) shall copy the contents of the Info-Package header field of the incoming SIP INFO request to the Info-Package header field of the outgoing SIP INFO request;
3) shall copy the MIME bodies present in the incoming SIP INFO request to the outgoing SIP INFO request; and
4) shall send the SIP INFO request to the MCData client within the SIP dialog of the MCData communication according to 3GPP TS 24.229 [5].
Upon receiving a SIP 200 (OK) response from MCData client to the SIP INFO request, the participating MCData function:
1) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5]; and
2) shall send a SIP 200 (OK) response to the SIP INFO request received from the controlling MCData function according to 3GPP TS 24.229 [5].
13.2.4.3.2 Receiving SIP INFO request from the MCData client
Upon receiving a SIP INFO request with the Info-Package header field set to g.3gpp.mcdata-com-release package, from MCData client within the SIP dialog of the MCData communication, the participating MCData function:
1) shall generate a SIP INFO request according to rules and procedures of 3GPP TS 24.229 [5] and IETF RFC 6086 [21];
2) shall copy the contents of the Info-Package header field of the incoming SIP INFO request to the Info-Package header field of the outgoing SIP INFO request;
3) shall copy the MIME bodies present in the incoming SIP INFO request to the outgoing SIP INFO request; and
4) shall send the SIP INFO request to the controlling MCData function, within the SIP dialog of the MCData communication, according to 3GPP TS 24.229 [5].
Upon receiving a SIP 200 (OK) response from controlling MCData function to the SIP INFO request, the participating MCData function:
1) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5]; and
2) shall send a SIP 200 (OK) response to the SIP INFO request received from the MCData client according to 3GPP TS 24.229 [5].
13.2.4.4 Controlling MCData function procedures for communication over media plane
13.2.4.4.1 Sending intent to release a communication
To send an intent to release a MCData communication, the controlling MCData function:
1) shall generate a SIP INFO request according to rules and procedures of 3GPP TS 24.229 [5] and IETF RFC 6086 [21];
2) shall include the Info-Package header field set to g.3gpp.mcdata-com-release;
3) shall include in the SIP INFO request, a COMMUNICATION RELEASE message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in clause E.1:
a) shall set a Content-Disposition header field to "Info-Package" value;
4) may add reason header with reason-text value as appropriate (e.g. data volume limit, time limit expiry); and
5) shall send a SIP request towards participating MCData function within the SIP dialog of the MCData communication, according to 3GPP TS 24.229 [5].
When generating a COMMUNICATION RELEASE message, the controlling MCData function:
1) shall generate a COMMUNICATION RELEASE message as defined in clause 15.1.10. In the COMMUNICATION RELEASE message, the controlling MCData function:
a) shall set Comm Release Information type IE to "INTENT TO RELEASE"; and
b) if requesting for more information, shall include and set Data query type IE to the "REMAINING AMOUNT OF DATA".
Upon receiving SIP 200 OK, the controlling MCData function:
1) shall start Timer TDC3 (request for extension).
If timer TDC3 (request for extension) expires before controlling MCData function receives a request for extension of communication from the MCData client, the controlling MCData function shall release MCData communication as described in clause 13.2.2.2.4.4.
13.2.4.4.2 Receiving more information
Upon receiving a SIP INFO request within the SIP dialog of a MCData communication, with the Info-Package header field set to g.3gpp.mcdata-com-release package and containing an application/vnd.3gpp.mcdata-payload MIME body associated with the Info-Package, the controlling MCData function:
1) shall decode the contents of the application/vnd.3gpp.mcdata-payload MIME body; and
2) shall identify the number of Payload IEs in the DATA PAYLOAD message from the Number of payloads IE in the DATA PAYLOAD message:
a) For each Payload IE:
i) shall store the contents of the Payload IE as remaining data information associated with ongoing MCData communication;
13.2.4.4.3 Receiving request for extension of communication
Upon receiving a SIP INFO request within the SIP dialog of a MCData communication, with the Info-Package header field set to g.3gpp.mcdata-com-release package and containing an application/vnd.3gpp.mcdata-signalling MIME body associated with the Info-Package, the controlling MCData function:
1) shall decode the contents of application/vnd.3gpp.mcdata-signalling MIME body; and
2) if application/vnd.3gpp.mcdata-signalling MIME body contains COMMUNICATION RELEASE message with the comm release information type IE set to "EXTENSION REQUEST", the controlling MCData function:
a) shall stop the timer TDC3 (request for extension);
b) shall generate SIP 200 (OK) response and send it towards participating MCData function according to 3GPP TS 24.229 [5]; and
c) shall send response to communication extension request as described in clause 13.2.4.4.4.
13.2.4.4.4 Sending response to communication extension request
To send a response to communication extension request from MCData client, the controlling MCData function:
1) shall generate a SIP INFO request according to rules and procedures of 3GPP TS 24.229 [5] and IETF RFC 6086 [21];
2) shall include the Info-Package header field set to g.3gpp.mcdata-com-release;
3) shall include in the SIP INFO request, a COMMUNICATION RELEASE message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in clause E.1; and
a) Shall set a Content-Disposition header field to "Info-Package" value; and
4) shall send a SIP request towards participating MCData function within the SIP dialog of the MCData communication, according to 3GPP TS 24.229 [5].
When generating a COMMUNICATION RELEASE message, the controlling MCData function:
1) Shall generate a COMMUNICATION RELEASE message as defined in clause 15.1.10. In the COMMUNICATION RELEASE message, the controlling MCData function:
a) Shall set Comm Release Information type IE to "EXTENSION RESPONSE"; and
b) shall assert the local policy along with already stored remaining data information associated with the MCData communication:
i) If controlling MCData function decides to accept the request for extension, shall set extension request type information element to "ACCEPTED"; or
ii) If controlling MCData function, decides to reject the request for extension, shall set extension request type information element to "REJECTED";
Upon receiving a SIP 200 (OK) response,
1) shall release the MCData communication as described in clause 13.2.2.2.4.4, if controlling MCData function, decides to reject the request for extension.
13.2.4.5 Release of MCData communication over HTTP
13.2.4.5.1 General
Based on communication release policies and configuration, the MCData server can release an ongoing MCData communication.
If configured, the MCData server can notify the originating MCData user about the intent to release communication and may request for more data about the communication it intends to release. The procedures described in this clause are applicable to MCData FD using HTTP where the MCData server initiates the communication release.
13.2.4.5.2 MCData client procedures
13.2.4.5.2.1 Receiving intent to release the communication
Upon receiving a SIP MESSAGE request containing an application/vnd.3gpp.mcdata-signalling MIME body; the MCData client:
1) shall decode the contents of the application/vnd.3gpp.mcdata-signalling MIME body;
2) if the application/vnd.3gpp.mcdata-signalling MIME body contains a FD HTTP TERMINATION message as specified in clause 15.1.11, with the Termination information type IE set to "INTENT TO RELEASE COMM OVER HTTP" then:
a) shall identify file transmission request with Conversation ID, Message ID, and FILE URL in FD HTTP TERMINATION message, if identified any transmission:
i) shall generate SIP 200 (OK) according to 3GPP TS 24.229 [5];
ii) shall send SIP 200 (OK) response towards MCData server according to 3GPP TS 24.229 [5];
iii) shall store the public service identity of the controlling MCData function from <mcdata-controller-psi> element of application/vnd.3gpp.mcdata-signalling MIME body; and
iv) shall notify MCData user and present the reason; if the reason header is present in SIP MESSAGE.
Once the MCData user is notified about the MCData server’s intent to release the communication, the MCData user may request for extension of communication as described in clause 13.2.4.5.2.2
13.2.4.5.2.2 Request for extension of communication
Upon receiving a request from MCData user for extension of the communication as a result of MCData server’s intent to release the communication, the MCData client:
1) shall generate SIP MESSAGE request according to 3GPP TS 24.229 [5];
2) shall generated a standalone FD message as specified in clause 6.2.2.4 with following clarifications:
a) shall set Termination information type IE to "EXTENSION REQUEST FOR COMM OVER HTTP";
3) shall include an application/vnd.3gpp.mcdata-info+xml MIME body:
a) shall set <mcdata-controller-psi> element to the store public service identity of controlling MCData function; and
4) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [5] towards originating participating function.
13.2.4.5.2.3 Receiving response to communication extension request
Upon receiving a SIP MESSAGE request from MCData server containing application/vnd.3gpp.mcdata-signalling MIME body, the MCData client:
1) shall decode the contents of application/vnd.3gpp.mcdata-signalling MIME body; and
2) if the application/vnd.3gpp.mcdata-signalling MIME body contains a FD HTTP TERMINATION message as specified in clause 15.1.11, with the Termination information type IE set to "EXTENSION RESPONSE FOR COMM OVER HTTP", then:
a) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5];
b) shall send SIP 200 (OK) response towards MCData server according to 3GPP TS 24.229 [5]; and
3) shall notify user about extension response based on Extension response type IE.
13.2.4.5.3 Participating MCData function procedures
13.2.4.5.3.1 Originating participating MCData function procedures
Upon receipt of a "SIP MESSAGE request for FD using HTTP for originating participating MCData function", the participating MCData function shall follow the procedure described in clause 10.2.4.3.1.
13.2.4.5.3.2 Terminating participating MCData function procedures
Upon receipt of a "SIP MESSAGE network notification for FD using HTTP for terminating participating MCData function", the participating MCData function shall follow the procedure described in clause 10.2.4.3.2
13.2.4.5.4 Controlling MCData function procedures
13.2.4.5.4.1 Sending intent to release a communication
To send an intent to release a MCData communication, the controlling MCData function:
1) shall generate a SIP MESSAGE as described in clause 13.2.1.1;
2) shall include <mcdata-controller-psi> element in application/vnd.3gpp.mcdata-info+xml MIME body with public service identity of controlling function;
3) shall set Termination information type IE in FD HTTP TERMINATION of application/vnd.3gpp.mcdata-signalling MIME body to "INTENT TO RELEASE COMM OVER HTTP";
4) may add reason header with reason-text value as appropriate (e.g. data volume limit, time limit expiry); and
5) shall send a SIP request towards participating MCData function according to 3GPP TS 24.229 [5].
Upon receiving SIP 200 OK, the controlling MCData function:
1) shall start Timer TDC3 (request for extension).
If timer TDC3 (request for extension) expires before controlling MCData function receives a request for extension of communication from the MCData client, the controlling MCData function shall release MCData communication as described in clause 13.2.3.3.4.
13.2.4.5.4.2 Receiving request for extension of communication
Upon receiving a SIP MESSAGE request, the controlling MCData function:
1) shall decode the contents of application/vnd.3gpp.mcdata-signalling MIME body; and
2) if application/vnd.3gpp.mcdata-signalling MIME body contains FD HTTP TERMINATION message with the Termination information type IE set to "EXTENSION REQUEST FOR COMM OVER HTTP", the controlling MCData function:
a) shall stop the timer TDC3 (request for extension) for file transmission identified by Conversation ID and Message ID and FILE URL;
b) shall generate SIP 200 (OK) response and send it towards participating MCData function according to 3GPP TS 24.229 [5]; and
3) shall send response to communication extension request as described in clause 13.2.4.5.4.3.
13.2.4.5.4.3 Sending response to communication extension request
To send a response to communication extension request from MCData client, the controlling MCData function:
1) shall generate a SIP MESSAGE as described in clause 13.2.1.1;
2) shall set Termination information type IE in FD HTTP TERMINATION of application/vnd.3gpp.mcdata-signalling MIME body to "EXTENSION RESPONSE FOR COMM OVER HTTP";
3) shall assert the local policy associated with the MCData communication:
a) If controlling MCData function decides to accept the request for extension, shall set Extension response type IE to "ACCEPTED"; or
b) If controlling MCData function, decides to reject the request for extension, shall set Extension response type IE to "REJECTED"; and
4) shall send SIP MESSAGE towards participating MCData function according 3GPP TS 24.229 [5];
Upon receiving 200 OK response:
1) shall release the MCData communication as described in clause 13.2.3.3.4; if controlling MCData function decides to reject the request for extension.
13.2.5 Authorized MCData user initiated communication release without prior indication
13.2.5.1 General
An authorized MCData user at any point of time during an ongoing MCData communication decides to release communication. An authorized MCData user should be part of the ongoing MCData communication. The procedure in this clause describes the case where an authorized MCData user decides to release the communication without providing prior indication to originator MCData user.
13.2.5.2 Release of MCData communication over media plane
13.2.5.2.1 General
The procedures described in this clause are applicable to MCData SDS and MCData FD established using media plane.
13.2.5.2.2 Authorized MCData client procedures
13.2.5.2.2.1 Sending communication release request
Upon receiving request from an authorized MCData user to release the communication without prior indication to originating MCData user, the MCData client:
1) shall generate a SIP INFO request according to rules and procedures of 3GPP TS 24.229 [5] and IETF RFC 6086 [21];
2) shall include the Info-Package header field set to g.3gpp.mcdata-com-release;
3) shall include in the SIP INFO request, a COMMUNICATION RELEASE message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in clause E.1:
a) shall set a Content-Disposition header field to "Info-Package" value;
4) shall insert in the SIP INFO request an application/vnd.3gpp.mcdata-info+xml MIME body with
a) the <mcdata-client-id> element set to the MCData client ID of the authorized MCData client;
5) may add reason header with reason-text value as appropriate; and
6) shall send a SIP request towards participating MCData function within the SIP dialog of the MCData communication, according to 3GPP TS 24.229 [5].
When generating a COMMUNICATION RELEASE message, the MCData client:
1) shall generate a COMMUNICATION RELEASE message as defined in clause 15.1.10. In the COMMUNICATION RELEASE message, the MCData client:
a) shall set Comm Release Information type IE to "AUTH USER RELEASE REQ".
Upon receiving a SIP 200 (OK) response from participating MCData function to the SIP INFO request, the MCData client should inform the authorized MCData user about acceptance of communication release request by MCData server.
Upon receiving a SIP 403 (Forbidden) response from participating MCData function to the SIP INFO request, the MCData client should inform the authorized MCData user about rejection of communication release request by MCData server.
13.2.5.2.3 Participating MCData function procedures
13.2.5.2.3.1 Receiving SIP INFO request from the authorized MCData client
Upon receiving a SIP INFO request with the Info-Package header field set to g.3gpp.mcdata-com-release package, from MCData client within the SIP dialog of the MCData communication, the participating MCData function should follow the procedure described in clause 13.2.4.3.2.
Upon receiving a SIP 403 (Forbidden) response from controlling MCData function to the SIP INFO request, the participating MCData function:
1) shall generate a SIP 403 (Forbidden) response according to 3GPP TS 24.229 [5]; and
2) shall send a SIP 403 (Forbidden) response to the SIP INFO request received from the MCData client according to 3GPP TS 24.229 [5].
13.2.5.2.4 Controlling MCData function procedures
13.2.5.2.4.1 Receiving request to release the communication from authorized MCData user
Upon receiving a SIP INFO request within the SIP dialog of a MCData communication, with the Info-Package header field set to g.3gpp.mcdata-com-release package and containing an application/vnd.3gpp.mcdata-signalling MIME body associated with the Info-Package, the controlling MCData function:
1) shall decode the contents of the application/vnd.3gpp.mcdata-signalling MIME body;
2) if the application/vnd.3gpp.mcdata-signalling MIME body contains a COMMUNICATION RELEASE message as specified in clause 15.1.10, with the Comm release information type IE set to "AUTH USER RELEASE REQ", then:
a) shall validate whether MCData user from which communication release request is received is authorized or not based on configuration;
3) if MCData user validation is not successful,
a) shall generate a SIP 403 (Forbidden) response according to 3GPP TS 24.229 [5];
b) shall send SIP 403 (Forbidden) response towards participating MCData function according to 3GPP TS 24.229 [5];
c) shall skip further steps;
4) if MCData user validation is successful,
a) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5];
b) shall send SIP 200 (OK) response towards MCData server according to 3GPP TS 24.229 [5];
5) shall follow the procedure as described in clause 13.2.3.2.4 to terminate the ongoing communication;
13.2.5.3 Release of MCData communication over HTTP
13.2.5.3.1 General
The procedures described in this clause are applicable to MCData FD over HTTP.
13.2.5.3.2 Authorized MCData client procedures
13.2.5.3.2.1 Sending communication release request
Upon receiving request from an authorized MCData user to release the communication without prior indication to originating MCData user, the MCData client
1) shall generate a SIP MESSAGE as specified in clause 13.2.1.2, then:
a) shall set the Termination information type IE if FD HTTP TERMINATION message to "AUTH USER TERMINATION REQUEST FOR COMM OVER HTTP" as specified in clause 15.2.22;
2) shall add application/vnd.3gpp.mcdata-info+xml MIME body in SIP MESSAGE with:
a) shall set <mcdata-controller-psi> element to the value received in incoming SIP MESSAGE; and
b) shall add <mcdata-client-id> element set to the MCData client ID of the authorized MCData client;
3) may add reason header with reason-text value as appropriate; and
4) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [5] towards originating participating function.
Upon receiving a SIP 200 (OK) response from participating MCData function to the SIP MESSAGE request, the MCData client should inform the authorized MCData user about acceptance of communication release request by MCData server.
Upon receiving a SIP 403 (Forbidden) or SIP 404 (Not found) response from participating MCData function to the SIP MESSAGE request, the MCData client should inform the authorized MCData user about rejection of communication release request by MCData server.
13.2.5.3.2.2 Receiving Release Response Type from server
Upon receiving SIP MESSAGE from server containing application/vnd.3gpp.mcdata-signalling MIME body with HTTP TERMINATION MESSAGE and FD signalling payload message identity value set as FD HTTP TERMINATION as described in clause 15.2.2, the authorized MCData client shall follow the procedure as described in clause 13.2.2.3.2.1.2.
13.2.5.3.3 Participating MCData function procedures
13.2.5.3.3.1 Originating participating MCData function procedures
Upon receipt of a "SIP MESSAGE request for FD using HTTP for originating participating MCData function", the participating MCData function shall follow the procedure as described in clause 10.2.4.3.1.
13.2.5.3.3.2 Terminating participating MCData function procedures
Upon receipt of a "SIP MESSAGE network notification for FD using HTTP for terminating participating MCData function", the participating MCData function shall follow the procedure as described in clause 10.2.4.3.2.
13.2.5.3.4 Controlling MCData function procedures
13.2.5.3.4.1 Receiving request to release the communication from authorized MCData user
Upon receiving a SIP MESSAGE request and containing an application/vnd.3gpp.mcdata-signalling MIME body, the controlling MCData function:
1) shall decode the contents of the application/vnd.3gpp.mcdata-signalling MIME body;
2) if the application/vnd.3gpp.mcdata-signalling MIME body contains FD HTTP TERMINATION message as specified in clause 15.1.11 then:
a) if Termination information type IE set to "AUTH USER TERMINATION REQUEST FOR COMM OVER HTTP", then:
i) shall validate whether MCData user identified in <mcdata-calling-userid> element of application/vnd.3gpp.mcdata-info+xml, is authorized or not based on configuration;
b) if MCData user validation is not successful:
i) shall generate a SIP 403 (Forbidden) response according to 3GPP TS 24.229 [5];
ii) shall send SIP 403 (Forbidden) response towards participating MCData function according to 3GPP TS 24.229 [5]; and
iii) shall skip further steps;
c) if MCData user validation is successful:
i) if not able to identify file transmission using the Conversation ID, Message ID and file URL, shall send SIP 404 (Not Found) with reason with waring text set to "224 No transmission available" in a Warning header field as specified in clause 4.9, and shall not continue with the rest of the steps;
ii) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5]; and
ii) shall send SIP 200 (OK) response towards MCData server according to 3GPP TS 24.229 [5]; and
d) shall follow the procedure as described in clause 13.2.3.3.4 to terminate the ongoing communication.
The controlling MCData function should follow procedure as described in clause 6.3.6.1 to generate response to the authorized user initiated request for release of MCData communication with following clarifications:
1) shall set Release response type IE to:
a) "RELEASE SUCCESS" if communication release request is successful; or
b) "RELEASE FAILED" if communication release request is not successful; and
2) shall send the SIP MESSAGE request towards the authorized MCData client as specified in 3GPP TS 24.229 [5].
13.2.6 Authorized MCData user initiated communication release with prior indication
13.2.6.1 General
An authorized MCData user at any point of time during an ongoing MCData communication decides to release communication. An authorized MCData user should be part of the ongoing MCData communication. The procedure in this clause describes the case where an authorized MCData user decides to release the communication with providing prior indication to originator MCData user.
13.2.6.2 Release of MCData communication over media plane
13.2.6.2.1 General
The procedures described in this clause are applicable to MCData SDS and MCData FD established using media plane.
13.2.6.2.2 Authorized MCData client procedures
13.2.6.2.2.1 Sending intent to release a communication
Upon receiving request from an authorized MCData user to release the communication without prior indication to originating MCData user, the MCData client:
1) shall generate a SIP INFO request according to rules and procedures of 3GPP TS 24.229 [5] and IETF RFC 6086 [21];
2) shall include the Info-Package header field set to g.3gpp.mcdata-com-release;
3) shall include in the SIP INFO request, a COMMUNICATION RELEASE message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in clause E.1:
a) shall set a Content-Disposition header field to "Info-Package" value;
4) shall insert in the SIP INFO request an application/vnd.3gpp.mcdata-info+xml MIME body with:
a) the <mcdata-client-id> element set to the MCData client ID of the authorized MCData client;
5) may add reason header with reason-text value as appropriate; and
6) shall send a SIP request towards participating MCData function within the SIP dialog of the MCData communication, according to 3GPP TS 24.229 [5].
When generating a COMMUNICATION RELEASE message, the MCData client:
1) shall generate a COMMUNICATION RELEASE message as defined in clause 15.1.10. In the COMMUNICATION RELEASE message, the MCData client:
a) shall set Comm Release Information type IE to "INTENT TO RELEASE"; and
b) if requesting for more information, shall include and set Data query type IE to the "REMAINING AMOUNT OF DATA".
Upon receiving a SIP 200 (OK) response from participating MCData function to the SIP INFO request, the MCData client should inform the authorized MCData user about acceptance of communication release request by MCData server.
Upon receiving a SIP 403 (Forbidden) response from participating MCData function to the SIP INFO request, the MCData client should inform the authorized MCData user about rejection of communication release request by MCData server.
13.2.6.2.2.2 Receiving more information
Upon receiving a SIP INFO request within the SIP dialog of a MCData communication, with the Info-Package header field set to g.3gpp.mcdata-com-release package and containing an application/vnd.3gpp.mcdata-payload MIME body associated with the Info-Package, the authorized MCData client:
1) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5];
2) shall send SIP 200 (OK) response towards participating MCData function according to 3GPP TS 24.229 [5];
3) shall decode the contents of the application/vnd.3gpp.mcdata-payload MIME body; and
4) shall identify the number of Payload IEs in the DATA PAYLOAD message:
a) for each Payload IE:
i) shall store the contents of the Payload IE as remaining data information associated with ongoing MCData communication.
13.2.6.2.2.3 Receiving request for extension of communication
Upon receiving a SIP INFO request within the SIP dialog of a MCData communication, with the Info-Package header field set to g.3gpp.mcdata-com-release package and containing an application/vnd.3gpp.mcdata-signalling MIME body associated with the Info-Package, the authorized MCData client:
1) shall decode the contents of application/vnd.3gpp.mcdata-signalling MIME body; and
2) if application/vnd.3gpp.mcdata-signalling MIME body contains COMMUNICATION RELEASE message with the comm release information type IE set to "EXTENSION REQUEST", the MCData client:
a) shall generate SIP 200 (OK) response and send it towards participating MCData function according to 3GPP TS 24.229 [5]; and
b) shall notify authorized MCData user about extension request and also present more information received previously to authorized MCData user; and
3) based on authorized MCData user’s response, shall send response to communication extension request as described in clause 13.2.6.2.4.
13.2.6.2.2.4 Sending response to communication extension request
To send a response to communication extension request from originator MCData client, the authorized MCData client:
1) shall generate a SIP INFO request according to rules and procedures of 3GPP TS 24.229 [5] and IETF RFC 6086 [21];
2) shall include the Info-Package header field set to g.3gpp.mcdata-com-release;
3) shall include in the SIP INFO request, a COMMUNICATION RELEASE message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in clause E.1;
a) Shall set a Content-Disposition header field to "Info-Package" value; and
4) shall send a SIP request towards participating MCData function within the SIP dialog of the MCData communication, according to 3GPP TS 24.229 [5].
When generating a COMMUNICATION RELEASE message, the MCData client:
1) shall generate a COMMUNICATION RELEASE message as defined in clause 15.1.10. In the COMMUNICATION RELEASE message, the MCData client:
a) shall set Comm Release Information type IE to "EXTENSION RESPONSE"; and
b) shall set extension request type information element as follows:
i) if authorized MCData user decides to accept the request for extension, shall set extension request type information element to "ACCEPTED"; or
ii) if authorized MCData user decides to reject the request for extension, shall set extension request type information element to "REJECTED".
13.2.6.2.3 Participating MCData function procedures
13.2.6.2.3.1 Receiving SIP INFO request from the authorized MCData client
Upon receiving a SIP INFO request with the Info-Package header field set to g.3gpp.mcdata-com-release package, from MCData client within the SIP dialog of the MCData communication, the participating MCData function should follow the procedure described in clause 13.2.4.3.2.
Upon receiving a SIP 403 (Forbidden) response from controlling MCData function to the SIP INFO request, the participating MCData function:
1) shall generate a SIP 403 (Forbidden) response according to 3GPP TS 24.229 [5]; and
2) shall send a SIP 403 (Forbidden) response to the SIP INFO request received from the MCData client according to 3GPP TS 24.229 [5].
13.2.6.2.3.2 Receiving SIP INFO request from the controlling MCData function
Upon receiving a SIP INFO request with the Info-Package header field set to g.3gpp.mcdata-com-release package, from controlling MCData function within the SIP dialog of the MCData communication, the participating MCData function shall follow the procedure described in clause 13.2.4.3.1.
13.2.6.2.4 Controlling MCData function procedures
13.2.6.2.4.1 Receiving request to release the communication from authorized MCData user
Upon receiving a SIP INFO request within the SIP dialog of a MCData communication, with the Info-Package header field set to g.3gpp.mcdata-com-release package and containing an application/vnd.3gpp.mcdata-signalling MIME body associated with the Info-Package, the controlling MCData function:
1) shall decode the contents of the application/vnd.3gpp.mcdata-signalling MIME body;
2) if the application/vnd.3gpp.mcdata-signalling MIME body contains a COMMUNICATION RELEASE message as specified in clause 15.1.10, with the Comm release information type IE set to AUTH USER RELEASE REQ, then:
a) shall validate whether MCData user, from which communication release request is received, is authorized or not based on configuration;
3) if MCData user is not authorized to release the MCData communication,
a) shall generate a SIP 403 (Forbidden) response according to 3GPP TS 24.229 [5];
b) shall send SIP 403 (Forbidden) response towards participating MCData function according to 3GPP TS 24.229 [5]; and
c) shall skip further steps;
4) if MCData user is authorized to release the MCData communication,
a) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5]; and
b) shall send SIP 200 (OK) response towards participating MCData function according to 3GPP TS 24.229 [5]; and
5) shall follow the procedure as described in clause 13.2.4.4.1 with following clarifications;
a) shall copy reason header from SIP INFO message received from participant MCData function.
The controlling MCData function should store the information related to initiator of MCData communication release process.
13.2.6.2.4.2 Receiving more information
Upon receiving a SIP INFO request within the SIP dialog of a MCData communication, with the Info-Package header field set to g.3gpp.mcdata-com-release package and containing an application/vnd.3gpp.mcdata-payload MIME body associated with the Info-Package, the controlling MCData function:
1) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5];
2) shall send SIP 200 (OK) response towards participating MCData server according to 3GPP TS 24.229 [5].
If controlling MCDta function is not the initiator of the MCData communication release process, the controlling MCData function should send more information received in SIP INFO message to authorized MCData user who is the initiator of the MCData communication release process. The controlling MCData function:
1) shall generate a SIP INFO request according to 3GPP TS 24.229 [5] and IETF RFC 6086 [21];
2) shall generate a DATA PAYLOAD message as described in clause 15.1.4;
3) shall include in the SIP INFO request, the DATA PAYLOAD message in an application/vnd.3gpp.mcdata-payload MIME body as specified in clause E.2;
a) shall set a Content-Disposition header field to "Info-Package" value;
4) shall include in the application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing SIP INVITE request:
a) the <mcdata-request-uri> element set to the MCData ID of the authorized MCData user; and
5) shall send the SIP INFO request within the SIP dialog of the MCData communication, towards the participating MCData function according to 3GPP TS 24.229 [5].
When generating an DATA PAYLOAD message as specified in clause 15.1.4, the MCData client:
1) shall set the Number of payloads IE to the same number which it received in SIP INFO message from participating function:
a) shall copy every payload IE from SIP INFO message received from participating function.
13.2.6.2.4.3 Receiving request for extension of communication
Upon receiving a SIP INFO request within the SIP dialog of a MCData communication, with the Info-Package header field set to g.3gpp.mcdata-com-release package and containing an application/vnd.3gpp.mcdata-signalling MIME body associated with the Info-Package, the controlling MCData function:
1) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5]; and
2) shall send SIP 200 (OK) response towards participating MCData function according to 3GPP TS 24.229 [5].
If controlling MCDta function is not the initiator of the MCData communication release process, the controlling MCData function should send request for extension of communication received in SIP INFO message to authorized MCData user who is the initiator of the MCData communication release process. The controlling MCData function:
1) shall generate a SIP INFO request according to 3GPP TS 24.229 [5] and IETF RFC 6086 [21];
2) shall include a Info-Package with header field set to g.3gpp.mcdata-com-release;
3) shall include in the SIP INFO request, a COMMUNICATION RELEASE message as specified in clause 15.1.10, in an application/vnd.3gpp.mcdata-signalling MIME body as specified in clause E.1; and
a) shall set a Content-Disposition header field to "Info-Package" value;
4) shall include in the application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing SIP INVITE request:
a) the <mcdata-request-uri> element set to the MCData ID of the authorized MCData user;
5) shall send the SIP INFO request within the SIP dialog of the MCData communication, towards the participating MCData function according to 3GPP TS 24.229 [5].
When generating an COMMUNICATION RELEASE message as specified in clause 15.1.10, the MCData client:
1) shall set the Comm release information type to "EXTENSION REQUEST".
13.2.6.2.4.4 Receiving response to communication extension request
Upon receiving a SIP INFO request within the SIP dialog of a MCData communication, with the Info-Package header field set to g.3gpp.mcdata-com-release package and containing an application/vnd.3gpp.mcdata-signalling MIME body associated with the Info-Package, the controlling MCData function:
1) shall decode the contents of application/vnd.3gpp.mcdata-signalling MIME body; and
2) if the application/vnd.3gpp.mcdata-signalling MIME body contains a COMMUNICATION RELEASE message as specified in clause 15.1.10, with the Comm release information type IE set to "EXTENSION RESPONSE", then:
a) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5]; and
b) shall send SIP 200 (OK) response towards participating MCData function according to 3GPP TS 24.229 [5].
If controlling MCDta function is not the initiator of the MCData communication release process, the controlling MCData function should send response to request for extension of communication received in SIP INFO message to originator MCData user. The controlling MCData function should follow procedure described in clause 13.2.4.4.4 with following clarification:
1) while generating a COMMUNICATION RELEASE message;
a) shall copy the extension request type information element from SIP INFO message received from authorized MCData client.
After sending response to originator MCData user, the controlling MCData function:
1) shall release the MCData communication as described in clause 13.2.2.2.4.4, if authorized MCData user has rejected the request for extension.
13.2.6.3 Release of MCData communication over HTTP
13.2.6.3.1 General
The procedures described in this clause are applicable to MCData FD over HTTP.
13.2.6.3.2 Authorized MCData client procedures
13.2.6.3.2.1 Sending intent to release a communication
Upon receiving request from an authorized MCData user to release the communication without prior indication to originating MCData user, the MCData client:
1) shall generate a SIP MESSAGE as specified in clause 13.2.1.2, then:
a) shall set the Termination information type IE of FD HTTP TERMINATION message to "INTENT TO RELEASE COMM OVER HTTP";
2) shall add application/vnd.3gpp.mcdata-info+xml MIME body in SIP MESSAGE with:
a) shall set <mcdata-controller-psi> element to the value received in incoming SIP MESSAGE; and
b) shall add <mcdata-client-id> element set to the MCData client ID of the authorized MCData client;
3) may add reason header with reason-text value as appropriate; and
4) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [5] towards originating participating function.
Upon receiving a SIP 200 (OK) response from participating MCData function to the SIP MESSAGE request, the MCData client should inform the authorized MCData user about acceptance of communication release request by MCData server.
Upon receiving a SIP 403 (Forbidden) or SIP 404 (Not found) response from participating MCData function to the SIP MESSAGE request, the MCData client should inform the authorized MCData user about rejection of communication release request by MCData server.
13.2.6.3.2.2 Receiving request for extension of communication
Upon receiving a SIP MESSAGE containing application/vnd.3gpp.mcdata-signalling MIME body then MCData client:
1) shall decode contents of application/vnd.3gpp.mcdata-signalling;
2) if application/vnd.3gpp.mcdata-signalling MIME body contains FD HTTP TERMINATION message with the Termination information type IE set to "EXTENSION REQUEST FOR COMM OVER HTTP", the authorized MCData client:
a) shall generate SIP 200 (OK) response and send it towards participating MCData function according to 3GPP TS 24.229 [5]; and
b) shall notify authorized MCData user about extension request to authorized MCData user; and
3) based on authorized MCData user’s response, shall send response to communication extension request as described in clause 13.2.6.3.2.3.
13.2.6.3.2.3 Sending response to communication extension request
To send a response to communication extension request from originator MCData client, the authorized MCData client:
1) shall generate a SIP MESSAGE as specified in clause 13.2.1.2, then:
a) shall set the Termination information type IE if FD HTTP TERMINATION message to "EXTENSION RESPONSE FOR COMM OVER HTTP";
b) shall set Extension response type IE as follows:
i) if authorized MCData user decides to accept the request for extension, shall set to "ACCEPTED"; or
ii) if authorized MCData user decides to reject the request for extension, shall set to "REJECTED";
2) shall add application/vnd.3gpp.mcdata-info+xml MIME body in SIP MESSAGE with:
a) shall set <mcdata-controller-psi> element to the value received in incoming SIP MESSAGE of FD transmission message; and
b) shall add <mcdata-client-id> element set to the MCData client ID of the authorized MCData client;
3) may add reason header with reason-text value as appropriate; and
4) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [5] towards originating participating function.
13.2.6.3.2.4 Receiving Release Response from server
Upon receiving SIP MESSAGE from server containing application/vnd.3gpp.mcdata-signalling MIME body with HTTP TERMINATION MESSAGE and FD signalling payload message identity value set as FD HTTP TERMINATION as described in clause 15.2.2, the authorized MCData client shall follow the procedure as described in clause 13.2.2.3.2.1.2.
13.2.6.3.3 Participating MCData function procedures
13.2.6.3.3.1 Originating participating MCData function procedures
Upon receipt of a "SIP MESSAGE request for FD using HTTP for originating participating MCData function", the originating participating MCData function shall follow the procedure as described in clause 10.2.4.3.1.
13.2.6.3.3.2 Terminating participating MCData function procedures
Upon receipt of a "SIP MESSAGE network notification for FD using HTTP for terminating participating MCData function", the terminating participating MCData function shall follow the procedure as described in clause 10.2.4.3.2.
13.2.6.3.4 Controlling MCData function procedures
13.2.6.3.4.1 Receiving request to release the communication from authorized MCData user
Upon receiving SIP MESSAGE from authorized MCData client containing an application/vnd.3gpp.mcdata-signalling MIME body; the controlling MCData function:
1) shall decode the contents of the application/vnd.3gpp.mcdata-signalling MIME body;
2) if the application/vnd.3gpp.mcdata-signalling MIME body contains a FD HTTP TERMINATION message as specified in clause 15.1.11, with the Termination information type IE set to "INTENT TO RELEASE FOR COMM OVER HTTP", then:
a) shall get authorized MCData user identity from <mcdata-calling-userid> element of application/vnd.3gpp.mcdata-info+xml MIME body and validate whether authorized MCData user, from which communication release request is received, is authorized or not based on configuration;
3) if MCData user is not authorized to release the MCData communication,
a) shall generate a SIP 403 (Forbidden) response according to 3GPP TS 24.229 [5];
b) shall send SIP 403 (Forbidden) response towards participating MCData function according to 3GPP TS 24.229 [5]; and
c) shall skip further steps;
4) if MCData user is authorized to release the MCData communication:
a) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5]; and
b) shall send SIP 200 (OK) response towards participating MCData function according to 3GPP TS 24.229 [5]; and
5) shall follow the procedure as described in clause 13.2.4.5.3.1 with following clarifications;
a) shall copy reason header from SIP MESSAGE received from participant MCData function.
The controlling MCData function should store the information related to initiator of MCData communication release process.
13.2.6.3.4.2 Receiving request for extension of communication
Upon receiving SIP MESSAGE containing an application/vnd.3gpp.mcdata-signalling MIME body, the Controlling MCData function:
1) shall decode the contents of application/vnd.3gpp.mcdata-signalling MIME body; and
2) if the application/vnd.3gpp.mcdata-signalling MIME body contains a COMMUNICATION RELEASE message as specified in clause 15.1.10, with the Comm release information type IE set to "EXTENSION REQUEST FOR COMM OVER HTTP", then:
a) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5]; and
b) shall send SIP 200 (OK) response towards participating MCData function according to 3GPP TS 24.229 [5].
If controlling MCData function is not the initiator of the MCData communication release process, the controlling MCData function should send request for extension of communication received in SIP MESSAGE to authorized MCData user who is the initiator of the MCData communication release process. The controlling MCData function:
1) shall generate SIP MESSAGE as described in clause 13.2.1.1;
2) shall include application/vnd.3gpp.mcdata-info+xml MIME body, then:
a) shall set <mcdata-request-uri> element to authorized user MCData id;
3) shall set Termination information type IE of FD HTTP TERMINATION message to "EXTENSION REQUEST FOR COMM OVER HTTP" as specified in clause 15.2.22; and
4) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [5] towards participating function.
13.2.6.3.4.3 Receiving response to communication extension request
Upon receiving a SIP MESSAGE containing an application/vnd.3gpp.mcdata-signalling MIME body, the controlling MCData function:
1) shall decode the contents of application/vnd.3gpp.mcdata-signalling MIME body; and
2) if the application/vnd.3gpp.mcdata-signalling MIME body contains a FD HTTP TERMINATION message as specified in clause 15.1.11, with the Termination information type IE set to "EXTENSION RESPONSE FOR COMM OVER HTTP", then:
a) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5]; and
b) shall send SIP 200 (OK) response towards participating MCData function according to 3GPP TS 24.229 [5].
If controlling MCData function is not the initiator of the MCData communication release process, the controlling MCData function should send response to request for extension of communication received in SIP MESSAGE to originator MCData user. The controlling MCData function should follow procedure described in clause 13.2.4.2.3.2 with following clarification:
1) while generating a FD HTTP TERMINATION message;
a) shall copy the Extension response type information element from SIP MESSAGE received from authorized MCData client.
After sending response to originator MCData user, the controlling MCData function:
1) shall release the MCData communication as described in clause 13.2.3.3.4, if authorized MCData user has rejected the request for extension.
The controlling MCData function should follow procedure as described in clause 6.3.6.1 to generate response to the authorized user initiated request for release of MCData communication with following clarifications:
1) shall set Release response type IE to:
a) "RELEASE SUCCESS" if communication release request is successful; or
b) "RELEASE FAILED" if communication release request is not successful.
2) shall send the SIP MESSAGE request towards the authorized MCData client as specified in 3GPP TS 24.229 [5].