The procedure in Figure 184.108.40.206.3-1 describes the case where an MCData user removes the file that was previously uploaded to the primary MCData system MCData content server, and where the file has been made available in the partner MCData system MCData content server.
The MCData user on the media storage client is registered for receiving MCData service.
The file has previously been uploaded to the MCData content server in the primary MCData system of MCData client 1.
The file has been successfully transferred to the MCData content server in the partner MCData system.
As the primary MCData content server has recorded that the file has previously been sent to the partner MCData system, the primary MCData content server sends the MCData remove file request by user to the partner MCData content server, containing the URL of the file which was stored on the primary MCData content server.
The initiation of a group standalone FD to a selected group results in affiliated group members receiving the file data over MBMS.
The first steps of the procedure are identical to the procedure Group standalone file distribution using HTTP (220.127.116.11). Based on the density and distribution of target group members, the MCData server may decide to deliver the file over MBMS.
The MBMS download delivery method is described in clause 7 of TS 26.346.
The procedure in Figure 18.104.22.168.2-1 describes the case where a MCData user is initiating group standalone data communication for sending a file to multiple MCData users, with or without download completed report request.
The MCData users on the MCData client 1 to n belong to the same group and are already registered for receiving MCData service and affiliated.
The file to be distributed is uploaded to the media storage function on the MCData content server using the procedure defined in subclause 22.214.171.124.
The MCData server executes the procedure described in subclause 7.3.5. The MCData server defines, in the MBMS session properties (subclause 5.4 of TS 26.348), the ingest mode to provide the file into the BM-SC via xMB-U. As described in clause 126.96.36.199.3, the MCData server decides how the file stored in the MCData content server is provided for distribution over the MBMS session.
If the pull ingest mode is defined, the MCData server may provide in this step the file list. As described in TS 26.348, the file list includes, among other information, the file URL to be used by the BM-SC to fetch the file and the earliest fetch time. The earliest fetch time may be configured with a long enough delay so that the MBMS session is established and steps 6 to 8 are executed before the delivery over MBMS. The MCData server can also update the MBMS session with the file list in a later step.
If the push ingest mode is defined, the MCData server obtains the URL from the BM-SC to be used to push the file via xMB-U. The MCData server ingests the content into the BM-SC after the MBMS session is established and steps 6 to 8 are performed.
The MCData server initiates the MCData group standalone FD over MBMS request towards each MCData user determined in step 3. The request is sent over unicast or within an MBMS bearer for application level control signalling.
The MCData file download completed reports from the MCData clients may be stored by the MCData server for download history interrogation from authorized MCData users. The MCData file download completed report from each MCData user may be aggregated.