Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.282  Word version:  19.5.0

Top   Top   Up   Prev   Next
1…   5…   6…   6.6…   7…   7.4…   7.4.2.7…   7.4.3…   7.5…   7.5.2.5…   7.5.2.10…   7.5.3…   7.6…   7.7…   7.8…   7.9…   7.13…   7.13.3.14…   7.13.4…   7.14…   7.17…   7.17.3.1.4…   7.17.3.2…   7.17.3.2.5…   7.17.4…   7.17.6…   A…   B… 
7.17.4 Ad hoc group short data service data communication procedures  7.17.4.1 General  7.17.4.2 Information flows for short data service specific  7.17.4.3 Ad hoc group short data service data communication procedures in single MCData system  7.17.4.4 Ad hoc group short data service data communication procedures involving multiple MC systems  7.17.5 Ad hoc group file distribution communication procedures  7.17.5.1 General  7.17.5.2 Information flows for file distribution specific  7.17.5.3 Ad hoc group file distribution communication procedures in single MCData system  7.17.5.4 Ad hoc group file distribution communication procedures involving multiple MC systems 
...

 

7.17.4  Ad hoc group short data service data communication procedures  p. 259

7.17.4.1  General  p. 259

This subclause contains procedures for ad hoc group short data service data communication across a single MCData system, and uses the common procedures defined in the subclause 7.17.3 in conjuction with the procedures defined in this subclause. Other common procedures specified in the clause7.17.3 are used at any time after Ad hoc group short data service data communication establishment based on the need of it. These procedures are applicable for Group standalone short data service using media plane and Group short data service session as specified in the subclause 7.4.2.6 and subclause 7.4.2.7 respectively.
Up

7.17.4.2  Information flows for short data service specific  p. 259

Table 7.17.4.2-1 describes the information elements that are specific to short data service and are used along with the common information flows defined in the subclause 7.17.2 for the Ad hoc group short data service data communication. These information elements are included when an Ad hoc group data session request sent from the MCData client to the MCData server, between the MCData servers, and from the MCData server to the MCData client.
Information element Status Description
Conversation IdentifierMIdentifies the conversation.
Transaction IdentifierMIdentifies the MCData transaction.
Reply IdentifierOIdentifies the original MCData transaction to which the current transaction is a reply to.
Transaction typeMSession based transactions.
Disposition TypeOIndicates the disposition type expected from the receiver (i.e., delivered or read or both).
Payload Destination TypeMIndicates whether the SDS payload is for application consumption or MCData user consumption.
Application identifier (see NOTE 1)OIdentifies the application for which the payload is intended (e.g. text string, port address, URI).
Application metadata containerOImplementation specific information that is communicated to the recipient.
NOTE 1:
The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption.
Up

7.17.4.3  Ad hoc group short data service data communication procedures in single MCData system  p. 260

7.17.4.3.1  General  p. 260
The initiation of Ad hoc group SDS session results in ad hoc group participants exchanging SDS data.
7.17.4.3.2  Procedure  p. 260
The procedure in Figure 7.17.4.3.2-1 describes the case where an MCData user is initiating SDS data communication session with an MCData ad hoc group for exchanging SDS data transactions between the ad hoc group participants, with or without disposition request.
Pre-conditions:
  1. As defined in the subclause 7.17.3.1.1.
Reproduction of 3GPP TS 23.282, Fig. 7.17.4.3.2-1: Ad hoc group SDS data communication session
Figure 7.17.4.3.2-1: Ad hoc group SDS data communication session
Up
Step 1.
User at MCData client 1 initiate an ad hoc group data communication as specified in the subclause 7.17.3.1.1.
Step 2.
MCData client 1 and the ad hoc group data session request accepted clients have successfully established media plane for data communication and either MCData client can transmit SDS data. The MCData data request may contain disposition request if indicated by the client sending data. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the SDS data receiving MCData users may be notified, otherwise those MCData users shall not be notified.
Step 3.
If MCData data disposition was requested by the user, then the SDS data receiving MCData client initiates a MCData data disposition notification for delivery, read reports to the disposition requesting user. The MCData data disposition notification from the receiving MCData clients may be stored by the MCData server for disposition history interrogation from authorized users.
Step 4.
Based on the MCData user action or conditions to release, the established media plane for SDS data exchange is released as specified in the subclause 7.17.3.1.2.
Up

7.17.4.4  Ad hoc group short data service data communication procedures involving multiple MC systems  p. 261

7.17.4.4.1  General  p. 261
The initiation of Ad hoc group SDS session results in ad hoc group participants exchanging SDS data.
7.17.4.4.2  Procedure  p. 261
The procedure in Figure 7.17.4.4.2-1 describes the case where an MCData user is initiating SDS data communication session with an MCData ad hoc group for exchanging SDS data transactions between the ad hoc group participants, with or without disposition request.
Pre-conditions:
  1. As defined in the Common Ad hoc group data communication procedures of subclause 7.17.3.2.1 or subclause 7.17.3.2.3.
Reproduction of 3GPP TS 23.282, Fig. 7.17.4.4.2-1: Ad hoc group SDS data communication session
Figure 7.17.4.4.2-1: Ad hoc group SDS data communication session
Up
Step 1.
User at MCData client 1 initiate an ad hoc group data communication as specified in the subclause 7.17.3.2.1 or subclause 7.17.3.2.3.
Step 2.
MCData client 1 and the ad hoc group data session request accepted clients have successfully established media plane for data communication and either MCData client can transmit SDS data. The MCData data request may contain disposition request if indicated by the client sending data. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the SDS data receiving MCData users may be notified, otherwise those MCData users shall not be notified.
Step 3.
If MCData data disposition was requested by the user, then the SDS data receiving MCData client initiates a MCData data disposition notification for delivery, read reports to the disposition requesting user. The MCData data disposition notification from the receiving MCData clients may be stored by the MCData server for disposition history interrogation from authorized users.
Step 4.
Based on the MCData user action or conditions to release, the established media plane for SDS data exchange is released as specified in the subclause 7.17.3.2.2 or subclause 7.17.3.2.5.
Up

7.17.5  Ad hoc group file distribution communication procedures  p. 262

7.17.5.1  General  p. 262

This subclause contains procedures for ad hoc group file distribution communication across a single MCData system, and uses the common procedures defined in the subclause 7.17.3 in conjuction with the procedures defined in this subclause. Other common procedures specified in the clause 7.17.3 are used at any time after Ad hoc group file distribution communication establishment based on the need of it.
Up

7.17.5.2  Information flows for file distribution specific  p. 262

Table 7.17.5.2-1 describes the information elements that are specific to file distribution and are used along with the common information flows defined in the subclause 7.17.2 for the Ad hoc group short data service data communication. These information elements are included when an Ad hoc group data session request sent from the MCData client to the MCData server, between the MCData servers, and from the MCData server to the MCData client.
Information element Status Description
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.
Up

7.17.5.3  Ad hoc group file distribution communication procedures in single MCData system  p. 262

7.17.5.3.1  General  p. 262
The initiation of Ad hoc group standalone FD using media plane results in ad hoc group participants exchanging SDS data.
7.17.5.3.2  Procedure  p. 262
The procedure in Figure 7.17.5.3.2-1 describes the case where an MCData user is initiating ad hoc group standalone data communication for sending file to multiple MCData users, with or without download completed report request.
Pre-conditions:
  1. As defined in the Common Ad hoc group data communication procedures of subclause 7.17.3.1.1.
Reproduction of 3GPP TS 23.282, Fig. 7.17.5.3.2-1: Ad hoc group SDS data communication session
Figure 7.17.5.3.2-1: Ad hoc group SDS data communication session
Up
Step 1.
User at MCData client 1 initiate an ad hoc group data communication as specified in the subclause 7.17.3.1.1.
Step 2.
MCData client 1 and MCData server have successfully established media plane for file transmission and the MCData client 1 transmits the file data. MCData server distributes the file received from MCData client 1 to MCData clients 2 to n over the established media plane. Distribution of file can be via unicast or via MBMS bearer(s).
Step 3.
The dispositions notifications are handled as specified in the subclause 7.5.2.7.
Step 4.
Based on the MCData user action or conditions to release, the established media plane for FD communication is released as specified in the subclause 7.17.3.1.2.
Up

7.17.5.4  Ad hoc group file distribution communication procedures involving multiple MC systems  p. 263

7.17.5.4.1  General  p. 263
The initiation of Ad hoc group standalone FD using media plane results in ad hoc group participants exchanging FD data.
7.17.5.4.2  Procedure  p. 263
The procedure in Figure 7.17.5.4.2-1 describes the case where an MCData user is initiating ad hoc group standalone data communication for sending file to multiple MCData users, with or without download completed report request.
Pre-conditions:
  1. As defined in the Common Ad hoc group data communication procedures of subclause 7.17.3.2.1 or subclause 7.17.3.2.3.
Reproduction of 3GPP TS 23.282, Fig. 7.17.5.4.2-1: Ad hoc group FD data communication session
Figure 7.17.5.4.2-1: Ad hoc group FD data communication session
Up
Step 1.
User at MCData client 1 initiate an ad hoc group data communication as specified in the subclause 7.17.3.2.1 or subclause 7.17.3.2.3.
Step 2.
MCData client 1 and MCData server have successfully established media plane for file transmission and the MCData client 1 transmits the file data. MCData server distributes the file received from MCData client 1 to MCData clients 2 to n over the established media plane. Distribution of file can be via unicast or via MBMS bearer(s).
Step 3.
The dispositions notifications are handled as specified in the subclause 7.5.2.7.
Step 4.
Based on the MCData user action or conditions to release, the established media plane for FD communication is released as specified in the subclause 7.17.3.2.2 or subclause 7.17.3.2.5.
Up

Up   Top   ToC