Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.282  Word version:  18.2.0

Top   Top   Up   Prev   Next
1…   5…   6…   6.6…   7…   7.4…   7.4.2.1.10…   7.4.2.2…   7.4.2.5…   7.4.2.8…   7.4.3…   7.5…   7.5.2.1.12…   7.5.2.2…   7.5.2.4…   7.5.2.6…   7.5.2.8…   7.5.2.11…   7.5.2.14…   7.5.3…   7.6   7.7…   7.7.2.3…   7.8…   7.9…   7.13…   7.13.3.1.19…   7.13.3.2…   7.13.3.8…   7.13.3.16…   7.13.4…   7.14…   7.14.2.2…   A…   B…

 

7.5.3  File distribution for off-network |R15|p. 137

7.5.3.1  General |R17|p. 137

Off-network file distribution communications are based on ProSe capabilities as described in clause 7.16.

7.5.3.2  Information flows for file distributionp. 137

7.5.3.2.1  MCData FD request (using media plane)p. 137
Table 7.5.3.2.1-1 describes the information flow for the MCData FD request sent from the MCData client to another MCData client.
Information Element Status Description
MCData IDMThe identity of the MCData user sending the file
MCData IDMThe identity of the MCData user receiving the file
Conversation IdentifierMIdentifies the conversation
Transaction IdentifierMIdentifies the MCData transaction
Reply IdentifierOIdentifies the original MCData transaction to which the current transaction is a reply to
Disposition indicationOIndicates whether file download completed report is expected or not
Download indicationOIndicates mandatory download. (i.e. auto accept this media plane setup request)
Application metadata containerOImplementation specific information that is communicated to the recipient
SDP offer (see NOTE)MMedia parameters offered
NOTE:
Includes file metadata.
Up
7.5.3.2.2  MCData FD response (using media plane)p. 138
Table 7.5.3.2.2-1 describes the information flow for the MCData FD response sent from the MCData client to another MCData client.
Information Element Status Description
MCData IDM
MCData IDM
Conversation IdentifierM
SDP answerM
Acceptance confirmationM
Up
7.5.3.2.3  MCData download completed reportp. 138
Table 7.5.3.2.3-1 describes the information flow for the MCData download completed report sent from the MCData client to another MCData client.
Information Element Status Description
MCData IDMThe identity of the MCData user sending FD request
MCData IDMThe identity of the MCData user sending response
Conversation IdentifierMIdentifies the conversation
Transaction IdentifierMIdentifies the MCData transaction
Disposition associationMIdentifies the original MCData transaction
Disposition confirmationMAn indication that the client has completed downloading file
Up
7.5.3.2.4  MCData group standalone FD request (using media plane)p. 138
Table 7.5.3.2.4-1 describes the information flow for the MCData group standalone FD request sent from the MCData client to another MCData client.
Information Element Status Description
MCData IDMThe identity of the MCData user sending the file
MCData group IDMThe MCData group ID to which the data is to be sent
Conversation IdentifierMIdentifies the conversation
Transaction IdentifierMIdentifies the MCData transaction
Reply IdentifierOIdentifies the original MCData transaction to which the current transaction is a reply to
Disposition indicationOIndicates whether file download completed report is expected or not
Download indicationOIndicates mandatory download. (i.e. auto accept this media plane setup request)
Application metadata containerOImplementation specific information that is communicated to the recipient
SDP offer (see NOTE)MMedia parameters offered
NOTE:
Includes file metadata.
Up
7.5.3.2.5  MCData group standalone FD response (using media plane)p. 139
Table 7.5.3.2.5-1 describes the information flow for the MCData group standalone FD response sent from the MCData client to another MCData client.
Information Element Status Description
MCData IDMThe identity of the MCData user sending FD request
MCData group IDMThe MCData group ID to which the file is to be sent
MCData IDMThe identity of the MCData user sending response
Conversation IdentifierMIdentifies the conversation
SDP answerMMedia parameters selected
Acceptance confirmationMAn indication whether the client has positively accepted the request
Up

7.5.3.3  One-to-one standalone file distribution using media planep. 139

7.5.3.3.1  Generalp. 139
The MCData client uses media plane for a standalone FD download from another MCData client in off-network.
7.5.3.3.2  Procedurep. 139
Figure 7.5.3.3.2-1 describes procedures for an off-network MCData client 1 initiating one-to-one MCData data communication for sending standalone FD data to other MCData client, with or without download completed report request.
Pre-conditions:
  1. MCData user 1 has initiated communication for sending standalone FD data to other MCData user 2.
  2. MCData client 1 and MCData client 2 are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable.
  3. MCData client 1 has discovered MCData client 2 in proximity, associated with MCData user 2, using ProSe Discovery procedures.
Copy of original 3GPP image for 3GPP TS 23.282, Fig. 7.5.3.3.2-1: One-to-one standalone file distribution using media plane
Up
Step 1.
MCData client 1 sends a MCData FD request towards the MCData client 2. File metadata information is included in the SDP. 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. MCData FD request may contain mandatory download indication. The MCData FD request may contain download completed report indication if selected by the user at MCData client 1.
Step 2.
On receiving a MCData FD request, the MCData client 2 checks whether any policy is to be asserted to limit certain types of message or content to certain members, for example, due to location or user privilege.
Step 3.
The receiving MCData client 2 notifies the user about the incoming MCData FD request which may be either accepted or rejected or ignored. MCData user may not be sought consent if the request includes mandatory download indication in the MCData FD request and instead only notify the MCData user about file downloading.
Step 4.
If the target MCData user 2 provides a response (accept or reject) to the notification, then the MCData client 2 sends the MCData FD response to the MCData client 1. MCData client 2 automatically sends accepted MCData FD response when the incoming request included mandatory download indication.
Step 5.
MCData client 1 distributes the file over the established media plane to MCData client 2.
Step 6.
The MCData client 2 records file download completed and notifies MCData user 2. MCData client 2 initiates a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1.
Up

7.5.3.4  Group standalone file distribution using media planep. 140

7.5.3.4.1  Generalp. 140
The initiation of a group standalone FD to a selected group results in off-network MCData group members receiving the file data.
7.5.3.4.2  Procedurep. 140
Figure 7.5.3.4.2-1 describes procedures for an off-network MCData client 1 initiating group MCData data communication for sending FD data to a MCData group, with or without download completed report request.
Pre-conditions:
  1. MCData user 1 has initiated group communication for sending FD data to the MCData group.
  2. Information for ProSe direct communications corresponding to the MCData group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCData client 1.
  3. MCData client 1 to MCData client N are members of the same MCData group.
Copy of original 3GPP image for 3GPP TS 23.282, Fig. 7.5.3.4.2-1: Group standalone file distribution using media plane
Up
Step 1.
MCData client 1 sends a MCData FD request towards the MCData group. File metadata information is included in the SDP. The MCData group standalone data request contains MCData group ID as selected by the user at MCData client 1. The MCData group standalone FD request contains conversation identifier for message thread indication. The MCData group standalone FD request may include additional implementation specific information in the application metadata container. MCData group standalone FD request may contain mandatory download indication. The MCData group standalone FD request may contain download completed report indication if selected by the user at MCData client 1.
Step 2.
On receiving a MCData FD request, the MCData clients check whether any policy is to be asserted to limit certain types of message or content to certain members, for example, due to location or user privilege.
Step 3.
If the policy assertion is positive, the receiving MCData clients 2 to n notifies the user about the incoming MCData group standalone FD request which may be either accepted or rejected or ignored. MCData user may not be sought consent if the request includes mandatory download indication in the MCData group standalone FD request and instead only notify the MCData user about file downloading.
Step 4.
If the target MCData user on MCData clients 2 to n provides a response (accept or reject) to the notification, then the respective MCData client sends the MCData group standalone FD response to the MCData client 1. MCData client 2 to n automatically sends accepted MCData group standalone FD response when the incoming request included mandatory download indication.
Step 5.
MCData client 1 and MCData client 2 to n have successfully established media plane for file transmission and the MCData client 1 transmits the file data.
Step 6.
The MCData client 2 to n successfully receiving the file, records file download completed and notifies MCData users.
Step 7.
MCData client 2 to n initiate a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1.
Up

Up   Top   ToC