Content for &nbsp; TS 23.282 &nbsp; Word version:&nbsp; 19.4.0

The user at the media storage client initiates a file upload request of the chosen file. If MCData emergency state is already set for the media storage client (due to previously triggered MCData emergency alert), the media storage client sets emergency indicator in the request. The media storage client verifies that the size of the file is within the maximum data size for FD for the intended MCData FD request (by checking the group configuration for a group FD request and by checking the service configuration for a one-to-one FD request).

The file to be uploaded is received by the media storage client and sent to the media storage function on the MCData content server for storing using the MCData upload data request.

Figure 7.5.2.2.3-1: Uploading of the file residing in MCData message store using HTTP

The MCData content server stores the file and provides a MCData upload data response indicating success (along with file URL to the media storage client) or failure.

7.5.2.2.3 Procedure for uploading the file residing in the MCData message store |R17| p. 111

The procedure in Figure 7.5.2.2.3-1 describes the case where an MCData user is uploading a file to media storage function on the MCData content server from his or her MCData message store account.

Pre-conditions:

The Media storage client knows the URL of the file residing in the MCData message store account of the user.

Reproduction of 3GPP TS 23.282, Fig. 7.5.2.2.3-1: Uploading of the file residing in MCData message store using HTTP

The user at the media storage client initiates a file upload request of the file residing in his MCData message store account.

The URL of the file which needs to be retrieved from the MCData message store account of the user is sent to the media storage function on the MCData content server using the MCData upload data request.

The MCData content server fetches the file from the MCData message store account of the user using the URL provided in the MCData upload data request.

The MCData content server stores the retrieved file content into its repository.

Figure 7.5.2.2.4-1: File upload using HTTP over network resources with required QoS

The MCData content provides a MCData upload data response indicating success (along with file URL to the media storage client) or failure.

7.5.2.2.4 Procedure for file upload including request of network resources with required QoS |R17| p. 112

The procedure in Figure 7.5.2.2.4-1 describes the case where an MCData client sends a request to the MCData server for the upload of a file from the media storage client on the MCData client to the media storage function on the MCData content server. The MCData server can, therefore, request network resources with the required QoS for the corresponding file upload.

Pre-conditions:

The MCData user on the MCData client is registered on the MCData server for receiving MCData service.
The MCData client is required to upload a file to the MCData content server over network resources with required QoS.
The MCData client knows its IP address/port to be used for the file upload as well as the URI or IP address/port of the target MCData content server.

Reproduction of 3GPP TS 23.282, Fig. 7.5.2.2.4-1: File upload using HTTP over network resources with required QoS

The MC user on the MCData client intends to upload a file to the MCData content server for file distribution. The MCData client verifies that the size of the file is within the maximum data size for FD for the intended MCData FD request (e.g., by checking the group configuration for a group FD request or the service configuration for a one-to-one FD request). If the MCData emergency state is already set for the MCData client, the MCData client sets the emergency indicator in the request.

The MCData client sends the MCData file upload request to the MCData server. This request contains information about the MCData client (including IP address and port to be used for the file upload), and the target MCData content server (including associated URI or IP address, and port).

The MCData server verifies that the corresponding MCData client is authorized to upload files to the corresponding MCData content server.

If the MCData client is authorized for the file upload, the MCData server sends a request to the 3GPP system for the allocation of network resources with the required QoS for the corresponding file upload communication between the MCData client and the MCData content server. For that, the MCData server performs policy and charging control (PCC) procedures, e.g., over the Rx reference point as described in TS 23.203 for the case of an EPS system.

The MCData server sends a MCData file upload response to the MCData client indicating if it can proceed with the file upload to the MCData content server.

The media storage client on the MCData client sends an MCData upload data request to the media storage function on the MCData content server to upload the file.

The MCData content server provides an MCData upload data response to the MCData client indicating if the file was successfully stored (along with file URL) or failure.

The MCData client provides to the MCData server an MCData file upload completion status indicating that the file upload is completed.

Figure 7.5.2.3.2-1: File download using HTTP

Based on the MCData file upload completion status, the MCData server requests to the 3GPP system to release the network resources allocated for the corresponding file upload.

7.5.2.3 File download using HTTP p. 114

7.5.2.3.1 General p. 114

The media storage client uses HTTP for a standalone data file download from the MCData content server.

7.5.2.3.2 Procedure for file download from the MCData content server without QoS p. 114

The procedure in Figure 7.5.2.3.2-1 describes the case where an MCData user is downloading a file from the media storage function of the MCData content server.

Pre-conditions:

The MCData user on the media storage client is registered for receiving MCData service.

Reproduction of 3GPP TS 23.282, Fig. 7.5.2.3.2-1: File download using HTTP

The user at the media storage client initiates a file download request available at the indicated URL.

The file available at the URL (received in MCData FD request or MCData group standalone FD request) is requested to be downloaded by the media storage client from the media storage function on the MCData content server using a MCData download data request. If emergency indicator is set in received in MCData FD request or MCData group standalone FD request, the media storage client sets emergency indicator in MCData download data request.

Figure 7.5.2.3.3-1: File download using HTTP over network resources with required QoS

The media storage function on the MCData content server may apply reception control policy and provides a MCData download data response including the file to the media storage client.

7.5.2.3.3 Procedure for file download including request of network resources with required QoS |R17| p. 114

The procedure in Figure 7.5.2.3.3-1 describes the case where an MCData client sends a request to the MCData server for the download of a file from the media storage client on the MCData client to the media storage function on the MCData content server. The MCData server can, therefore, request network resources with the required QoS for the corresponding file download.

Pre-conditions:

The MCData user on the MCData client is registered on the MCData server for receiving MCData service.
The MCData client has been requested to download a file using HTTP and has received the corresponding file URL (via an MCData FD request or MCData group standalone FD request).
The MCData client is required to download a file from the MCData content server over network resources with required QoS.

NOTE 1:
It is implementation specific whether an MCData system enables that network resources with required QoS are required for file downloads.
The MCData client knows its IP address/port to be used for the file download as well as the URI or IP address/port of the target MCData content server.

NOTE 2:
How the MCData client knows the IP addresses and ports to be used for the file download is implementation specific and out of the scope of this specification.

Reproduction of 3GPP TS 23.282, Fig. 7.5.2.3.3-1: File download using HTTP over network resources with required QoS

The MC user on the MCData client intends to download a file from the MCData content server based on a received MCData FD request or MCData group standalone FD request. If the MCData emergency state is already set for the MCData client, the MCData client sets the emergency indicator in the request.

The MCData client sends the MCData file download request to the MCData server. This request contains information about the MCData client (including IP address and port to be used for the file download), and the target MCData content server (including associated URI or IP address, and port). The request also contains the corresponding file URL on the MCData content server.

The MCData server may verify, based on the received file URL, whether the file is available in the MCData content server via the MCData-FD-5 reference point. For that, the MCData server sends an MCData file availability request to the MCData content server. Upon the receipt of the request, the MCData content server provides an MCData file availability response to the MCData server. If the MCData server identifies that the corresponding file is not available in the MCData content server, the MCData server provides a response to the MCData client indicating that the file download request cannot proceed due to the unavailability of the file in the MCData content server.

The MCData server verifies that the corresponding MCData client is authorized to download the file from the corresponding MCData content server.

If the MCData client is authorized for the file download, the MCData server sends a request to the 3GPP system for the allocation of network resources with the required QoS for the corresponding file download communication between the MCData client and the MCData content server. For that, the MCData server performs policy and charging control (PCC) procedures, e.g., over the Rx reference point as described in TS 23.203 for the case of an EPS system.

The MCData server sends a MCData file download response to the MCData client indicating whether it can proceed with the file download from the MCData content server.

The media storage client on the MCData client sends an MCData download data request to the media storage function on the MCData content server to download the corresponding file.

The MCData content server provides an MCData download data response to the MCData client including the file for the case of a successful response.

Figure 7.5.2.4.2-1: One-to-one file distribution using HTTP

The MCData client provides to the MCData server an MCData download completed report indicating that the file download is completed.

Step 10.

Based on the MCData download completed report, the MCData server requests to the 3GPP system to release the network resources allocated for the corresponding file download.

7.5.2.4 One-to-one file distribution using HTTP p. 116

7.5.2.4.1 General p. 116

The MCData client uses HTTP file distribution to download a file that is uploaded by another MCData client. The procedure is appropriate for both mandatory and non-mandatory download cases. The target MCData user may be addressed using the functional alias that can be shared with other MCData users.

7.5.2.4.2 Procedure for single MCData system p. 116

The procedure in Figure 7.5.2.4.2-1 describes the case where a MCData user is initiating one-to-one data communication for sending file to the other MCData user, with or without download completed report request.

Pre-conditions:

The MCData users on the MCData client 1 and the MCData client 2 are already registered for receiving MCData service.
The file to be distributed is uploaded to media storage function on MCData content server using the procedures defined in subclause 7.5.2.2.
The MCData client may have activated functional alias to be used.
The MCData server has subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates.

Reproduction of 3GPP TS 23.282, Fig. 7.5.2.4.2-1: One-to-one file distribution using HTTP

The user at the MCData client 1 initiates a file distribution request to the chosen MCData user.

The MCData client 1 sends a MCData FD request towards the MCData server. The MCData FD request contains content payload in the form of file URL and may contain the file metadata information. The MCData FD request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData FD request contains conversation identifier for message thread indication. The MCData FD request may include additional implementation specific information in the application metadata container. If MCData user at MCData client 1 has requested to mandatory download at the recipient side, then MCData FD request contains mandatory download indication. If the MCData user at MCData client has requested to deposit the file content into his/her MCData message store account, then MCData FD request contains deposit file indication set. The MCData FD request may contain download completed report indication if selected by the user at MCData client 1. The MCData user at MCData client 1 may include a functional alias within the FD data transfer and may address the target MCData client 2 using a functional alias.

If the MCData user at the MCData client 1 initiates an MCData emergency file distribution using HTTP or MCData emergency state is already set for the MCData client 1 (due to previously triggered MCData emergency alert):
1. The MCData FD request shall contain emergency indicator; and
2. If MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1.

MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData FD request and that the size of the file is below maximum data size for FD from the service configuration. MCData server verifies whether the provided functional alias of MCData client 1, if present, can be used and has been activated for the user. If functional alias is used to address that target MCData user, the MCData server resolves the functional alias to the corresponding MCData IDs for which the functional alias is active and proceed with step 4 otherwise proceed with step 6.

The MCData server may verify whether the corresponding file is available in the MCData content server (not shown in the figure) via the MCData-FD-5 reference point using the received file URL in the MCData FD request. For that, the MCData server sends an MCData file availability request to the MCData content server. Upon the receipt of the request, the MCData content server provides an MCData file availability response to the MCData server. If the MCData server identifies that the corresponding file is not available in the MCData content server, the MCData server provides a response to the MCData client 1 indicating that the file distribution request cannot proceed due to the unavailability of the file in the MCData content server.

The MCData server responds back to MCData client 1 with a functional alias resolution response message that contains the resolved MCData ID.

If the MCData server replies with a MCData functional alias resolution response message, the MCData client 1 assumes the MCData FD request in step 2 is rejected and sends a new MCData FD request towards the resolved MCData ID.

MCData server initiates the MCData FD request towards MCData client 2. The MCData FD request towards the MCData user contains an emergency indicator if it is present in the received MCData FD request from MCData client 1. If the deposit file indication information element is set to true in the received MCData FD request, MCData server shall follow the procedure as defined in the subclause 7.13.3.8 with the retrieve file indication element set to true while depositing this MCData communication to the MCData message store account of the user at MCData client 1.

The receiving MCData client 2 notifies the user about the incoming MCData FD request (including file metadata, if present) which may be either accepted or rejected or ignored.

Figure 7.5.2.4.3-1: One-to-one file distribution using HTTP with interconnection

The MCData user 2 may provide a response (accept or reject) or not (ignore) to the notification, then MCData client 2 sends the MCData FD response to the MCData server. The MCData client 2 automatically sends an accepted MCData FD response when the received request includes a mandatory download indication.

Step 10.

The MCData server forwards the MCData FD response to the MCData client 1.

Step 11.

The Media storage client on the MCData client 2 downloads the file from the MCData content server using the procedures defined in subclause 7.5.2.3, either automatically (for mandatory download) or based upon the MCData user 2 subsequent action. The MCData client 2 records file download completed and notifies the MCData user 2.

Step 12.

The MCData client 2 provides an MCData download completed report for reporting file download completed, if requested by the user at MCData client 1.

Step 13.

The received MCData file download completed report from the MCData client 2 may be stored by the MCData server for download history interrogation from authorized MCData users. The MCData download completed report is sent by the MCData server to the MCData user at MCData client 1, if requested by the MCData client 1.

7.5.2.4.3 Procedure with interconnection between MCData systems |R16| p. 118

The procedure in Figure 7.5.2.4.3-1 describes the case where a MCData user initiates a one-to-one data communication for sending a file to another MCData user where that other MCData user is receiving MCData service on a partner MCData system, and where interconnection is in use between the two MCData systems. In this procedure, the file has not previously been downloaded in the partner MC system.

Pre-conditions:

The MCData users on the MCData client 1 and the MCData client 2 are already service authorized and receiving MCData service. MCData client 1 is receiving service on its primary MCData system, and MCData client 2 is receiving MCData service in the partner MCData system of MCData client 1.
The file to be distributed has been uploaded to the media storage function on the MCData content server in the primary MCData system of MCData client 1 using the procedures defined in subclause 7.5.2.2.
There is a service agreement between the primary and partner MCData systems to allow files to be shared between MCData content servers in the two systems.
The MCData client may have an activated functional alias to be used.
The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates.

Reproduction of 3GPP TS 23.282, Fig. 7.5.2.4.3-1: One-to-one file distribution using HTTP with interconnection

The user at the MCData client 1 initiates a file distribution request to the MCData user at MCData client 2.

MCData client 1 sends an MCData FD request towards the primary MCData server. The MCData FD request contains content payload in the form of a file URL with the necessary access authorization information and may contain the file metadata information. The MCData FD request indicates the target MCData user for the one-to-one data communication. The MCData FD request contains a conversation identifier for message thread indication. If the MCData user at MCData client 1 has requested to mandatory download at the recipient side, then the MCData FD request contains the mandatory download indication. The MCData FD request may contain a request for a download completed report indication if selected by the user at MCData client 1. The MCData user at MCData client 1 may include a functional alias within the FD data transfer and may address the target MCData client 2 using a functional alias.

MCData server checks whether the MCData user at MCData client 1 is authorized to send the MCData FD request and that the size of the file is below maximum data size for FD from the service configuration. MCData server verifies whether the provided functional alias of MCData client 1, if present, can be used and has been activated for the user.

The MCData server may verify whether the corresponding file is available in the MCData content server via the MCData-FD-5 reference point using the received file URL in the MCData FD request. For that, the MCData server sends an MCData file availability request to the MCData content server. Upon the receipt of the request, the MCData content server provides an MCData file availability response to the MCData server. If the MCData server identifies that the corresponding file is not available in the MCData content server, the MCData server provides a response to the MCData client 1 indicating that the file distribution request cannot proceed due to the unavailability of the file in the MCData content server.

The MCData server in the primary MCData system initiates the MCData FD request towards the MCData server in the partner MCData system, which contains the URL of the file which is stored in the primary MCData content server. The request includes the necessary access authorization information as MCData client 2 will retrieve the file while receiving service in the partner MCData system.

If functional alias is used to address that target MCData user, the MCData server in the partner MCData system resolves the MCData IDs of the functional alias. The resulting list contains all associated MCData IDs/MCData users that may share this functional alias. The MCData server in the partner MCData system now checks which MCData users have FD capabilities and which are authorized to receive a file. The partner MCData server sends the MCData FD request to the MCData users determined. The file URL being provided in MCData FD request to the MCData users determined is prepended with server URI of the partner MCData content server, such that the URL identifies a file location in the partner MCData content server.

The receiving MCData client 2 may notify the user about the incoming MCData FD request (including file metadata, if present) which may be either accepted, rejected or ignored.

The MCData user 2 may provide a response (accept or reject) or not (ignore) to the notification, then the MCData client 2 sends the MCData FD response to the partner MCData server. The MCData client 2 automatically sends an accepted MCData FD response when the received request includes a mandatory download indication