11 Transmission and Reception Control

24.2823GPPMission Critical Data (MCData) signalling controlProtocol specificationRelease 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

11.1 General

The MCData functional entities (as specified in clause 5.2 and clause 5.3) check if the MCData user is allowed to initiate MCData communications by following the procedures specified below:

1) if the MCData user wishes to send one-to-one MCData communications and the <allow-transmit-data> element of an <actions> element is not present in the MCData user profile document or is present with the value "false" (see the MCData user profile document in 3GPP TS 24.484 [12]), , the MCData client and participating MCData function shall determine that the MCData user is not allowed to send MCData communications and shall not continue with the rest of the steps;

1A) if the MCData user wishes to initiate one-to-one MCData communications, the <One-to-One-Communication> element exists in the MCData user profile document with one more <entry> elements, and the "uri" attribute of the <entry> element in a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body does not match with one of the <entry> elements of the <One-to-One-Communication> element of the MCData user profile document (see the MCData user profile document in 3GPP TS 24.484 [12]), the MCData client and participating MCData function shall determine that the MCData user is not allowed to initiate MCData communication to the targeted user and shall not continue with the rest of the steps;

2) if the MCData user wishes to send group MCData communications on an MCData group identity and the <mcdata-allow-transmit-data-in-this-group> element of an <actions> element is not present in the MCData group document or is present with the value "false" as specified in 3GPP TS 24.481 [11], the MCData client and controlling MCData function shall determine that the MCData user is not allowed to send group MCData communications on this group identity, and shall not continue with the rest of the steps;

3) if the MCData user wishes to send one-to-one SDS communications and the size of the payload is greater than the value contained in the <max-data-size-sds-bytes> element in the MCData service configuration document as specified in 3GPP TS 24.484 [12], the MCData client and controlling MCData function shall determine that the MCData user is not allowed to send SDS communications due to message size and shall not continue with the rest of the steps;

4) if the MCData user wishes to send one-to-one FD communications and the size of the data that the MCData user wishes to send is greater than the value contained in the <max-data-size-fd-bytes> element in the MCData service configuration document as specified in 3GPP TS 24.484 [12], the MCData client and controlling MCData function shall determine that the MCData user is not allowed to send FD communications due to file size and shall not continue with the rest of the steps;

5) if the MCData user wishes to send group SDS communications on an MCData group identity and the size of the data that the MCData user wishes to send is greater than the value contained in the <mcdata-on-network-max-data-size-for-SDS> element in the MCData group document for the MCData group ID as specified in 3GPP TS 24.481 [11], then the MCData client and the controlling MCData function shall determine that the MCData user is not allowed to send SDS communications on this group identity due to message size and shall not continue with the rest of the steps;

6) if the MCData user wishes to send group FD communications on an MCData group identity and the size of the data that the MCData user wishes to send is greater than the value contained in the <mcdata-on-network-max-data-size-for-FD> element in the MCData group document for the MCData group ID as specified in 3GPP TS 24.481 [11], then the MCData client and the controlling MCData function shall determine that the MCData user is not allowed to send FD communications on this group identity due to file size and shall not continue with the rest of the steps;

7) if the MCData user wishes to send one-to-one MCData communications to another MCData user and the size of the payload is greater than the maximum amount of data that the MCData user can transmit in a single request during one-to-one communications contained in the <MaxData1To1> element of the MCData user profile document (see the MCData user profile document in 3GPP TS 24.484 [12]), the MCData client and participating MCData function shall determine that the MCData user is not allowed to send one-to-one MCData communications due to exceeding the maximum amount of data that can be sent in a single request and shall not continue with the rest of the steps;

8) if the MCData user wishes to send group MCData communications on an MCData group identity and the size of the payload is greater than the maximum amount of data that the MCData user can transmit in a single request during group communications in the group identified by the MCData group identity in the request contained in the <mcdata-max-data-in-single-request> element of the <entry> element of the MCData group document as specified in 3GPP TS 24.481 [11], the MCData client and the controlling MCData function shall determine that the MCData user is not allowed to send group MCData communications on this group identity due to exceeding the maximum amount of data that can be sent in a single request and shall not continue with the rest of the steps;

9) if the MCData user wishes to initiate a SDS session for later use with one-to-one MCData communications there are no further checks for the MCData client which shall continue at step 11). If, for either the originating user or the terminating user, the <allow-transmit-data> element of an <actions> element is not present in the MCData user profile document or is present with the value "false" (see the MCData user profile document in 3GPP TS 24.484 [12]), the participating MCData function shall determine that the MCData user is not allowed to initiate a SDS session and shall not continue with the rest of the steps;

10) if the MCData user wishes to initiate a SDS session on an MCData group identity and the <mcdata-allow- short-data-service> element of a <list-service> element is not present in the MCData group document or is present with the value "false" as specified in 3GPP TS 24.481 [11], the MCData client and controlling MCData function shall determine that the MCData user is not allowed to initiate a SDS session on this group identity and shall not continue with the rest of the steps;

11) if the MCData user wishes to initiate an IP Connectivity session with one-to-one MCData communications and the <allow-transmit-data> element of an <actions> element is not present in the MCData user profile document or is present with the value "false" as specified in 3GPP TS 24.484 [12], the MCData client and controlling MCData function shall determine that the MCData user is not allowed to initiate an IP Connectivity session and shall not continue with the rest of the steps; and

12) the MCData functional entity shall determine that the MCData user is allowed to initiate MCData communications.

11.2 Auto-receive for File Distribution

If the controlling MCData function receives a one-to-one file distribution using HTTP or a group standalone file distribution using HTTP without the mandatory download indication the controlling MCData function:

1) if the file distribution request contained metadata, shall retrieve the filesize contained in the fileselector of the Metadata IE in the FD request;

2) if the file distribution request did not contain metadata, shall determine the size of the file referenced by the file URL contained in FD request;

3) for one-to-one file distribution using HTTP, shall determine if the filesize is less than or equal to the value contained in the <max-data-size-auto-recv-bytes> element of the MCData service configuration document as specified in 3GPP TS 24.484 [12];

4) for group standalone file distribution using HTTP, shall determine if the filesize is less than or equal to the value contained in the <mcdata-on-network-max-data-size-auto-recv> element of the MCData group document associated with the MCData group identity in the request, as specified in 3GPP TS 24.481 [11]; and

5) ifcondition 3) or 4) is true, shall determine that the mandatory download indication needs to be included in the file distribution request sent to the terminating MCData client.

If the controlling MCData function receives a one-to-one file distribution using media plane or a group standalone file distribution using media plane without the mandatory download indication the controlling MCData function:

1) if the file distribution request contained metadata, shall retrieve the filesize contained in the fileselector attribute contained in the "m=message" media-level section for the MCData media stream of SDP offer in the FD request;

2) for one-to-one file distribution using media plane, shall determine if the filesize is less than or equal to the value contained in the <max-data-size-auto-recv-bytes> element of the MCData service configuration document as specified in 3GPP TS 24.484 [12];

3) for group standalone file distribution using media plane, shall determine if the filesize is less than or equal to the value contained in the <mcdata-on-network-max-data-size-auto-recv> element of the MCData group document associated with the MCData group identity in the request, as specified in 3GPP TS 24.481 [11]; and

4) if condition 1) is true and 2) or 3) is true, shall determine that the mandatory download indication needs to be included in the file distribution request sent to the terminating MCData client.

11.3 Accessing list of deferred data group communications

11.3.1 General

Accessing list of deferred data group communication allows a MCData user to request for the list of files that have been deferred for future download. The procedures are applicable for FD using HTTP and FD using media plane.

11.3.2 MCData client procedures

11.3.2.1 Sending a request to access a list of deferred group communications

Upon receiving a request from the MCData user to access the list of deferred data group communications, the MCData client:

1) shall build the SIP MESSAGE request as specified in clause 6.2.4.1;

2) shall generate DEFERRED DATA REQUEST message as specified in clause 15.1.11.1;

3) shall include in the SIP request, the DEFERRED DATA GROUP COMM message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in clause E.1; and

4) shall send the SIP MESSAGE request towards the participating MCData function according to rules and procedures of 3GPP TS 24.229 [5].

11.3.2.2 Receiving a list of deferred group communications

Upon receipt of a "SIP MESSAGE response for the list of deferred group communications request", the MCData client:

1) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [5];

2) shall send the SIP 200 (OK) response towards the MCData server according to rules and procedures of 3GPP TS 24.229 [5];

3) shall decode the contents of the application/vnd.3gpp.mcdata-signalling MIME body:

a) if the application/vnd.3gpp.mcdata-signalling MIME body contains DEFERRED DATA RESPONSE message as specified in clause 15.1.12:

i) for each deferred FD signalling payload, if payload type is set to "FILEURL", shall store the required data or entire FD signalling payload and the Group ID information; and

4) shall present to MCData user, the list of file URLs which were deferred with other information optional such as Originator, Group ID, Conversation ID, Message ID, InReplyTo message ID and Date and time etc.

11.3.3 Participating MCData function procedures

11.3.3.1 Receiving a request to access a list of deferred group communications

Upon receipt of a "SIP MESSAGE request for the list of deferred group communications", the participating 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 MCData client according to 3GPP TS 24.229 [5]; and

3) shall follow the procedure described in clause 11.3.3.2 to send response.

11.3.3.2 Sending a list of deferred group communications

To send the list of deferred group communications, the participating MCData function:

1) shall build the SIP MESSAGE request as specified in clause 6.3.2.1;

2) shall generate DEFERRED DATA RESPONSE message as specified in clause 15.1.12.1;

3) shall include in the SIP request, the DEFERRED DATA RESPONSE message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in clause E.1; and

4) shall send the SIP MESSAGE request towards the MCData client according to rules and procedures of 3GPP TS 24.229 [5].

When generating a DEFERRED DATA RESPONSE message as specified in clause 15.1.12, the participating MCData function:

1) shall set the number of payloads IE to the number of FD using HTTP or FD using media plane communication which are deferred as per the stored file list:

a) for each deferred file from the list, shall copy the payload IE value from the stored list to the payload IE value of the outgoing message being generated; or

2) shall set the number of payloads IE to the number of FD using HTTP or FD using media plane communication which are deferred as per the stored deferred group communications:

a) for each deferred group communication, shall copy the deferred FD signalling payload IE value(s) from the stored list to the deferred FD signalling payload IE value(s) of the outgoing message being generated; and

b) shall copy the MCData group ID(s) from the stored list to the MCData group ID IE value(s) of the outgoing message.

NOTE: Only the ‘payload’ IE and its value population from the stored list of ‘payload’ IE and its value as described in step 1) applicability were specified in early versions of the present document from release 13 to release 16. The continued support for Payload element and its value is for backwards compatibility.