Content for  TS 23.282  Word version:  19.4.0

Table 7.7.2.1.1-1 describes the information flow for the MCData communication release request (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client.

Table 7.7.2.1.2-1 describes the information flow for the MCData communication release response (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client.

Table 7.7.2.1.3-1 describes the information flow for the MCData communication release request (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client.

Table 7.7.2.1.4-1 describes the information flow for the MCData communication release response (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client.

Table 7.7.2.1.8-1 describes the information flow for MCData server communication release request (in subclause 7.7.2.3.2.2) sent from the MCData server to the MCData clients involved in one-to-one communication.

Table 7.7.2.1.9-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.3.2.2) sent from the MCData client to the MCData server.

Table 7.7.2.1.10-1 describes the information flow for MCData server communication release request (in subclause 7.7.2.3.2.2) sent from the MCData server to the MCData clients involved in group communication.

Table 7.7.2.1.11-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.3.2.2) sent from the MCData client to the MCData server.

Table 7.7.2.1.13-1 describes the information flow for MCData release intent request (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData server to the MCData client.

Table 7.7.2.1.14-1 describes the information flow for MCData more information response (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData client to the MCData server and from MCData server to authorized MCData user.

Table 7.7.2.1.15-1 describes the information flow for MCData release intent request (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData server to the MCData client.

Table 7.7.2.1.16-1 describes the information flow for MCData more information response (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData client to the MCData server and from MCData server to authorized MCData user.

Table 7.7.2.1.17-1 describes the information flow for MCData auth user communication release request (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the authorized MCData user to the MCData server.

Table 7.7.2.1.18-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the MCData server to the authorized MCData user.

Table 7.7.2.1.19-1 describes the information flow for MCData auth user communication release request (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the authorized MCData user to the MCData server.

Table 7.7.2.1.20-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the MCData server to the authorized MCData user.

Table 7.7.2.1.21-1 describes the information flow for the MCData request for extension (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData client to the MCData server and from MCData server to authorized MCData user.

Table 7.7.2.1.22-1 describes the information flow for the MCData response for extension (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the authorized MCData user to the MCData server and MCData client to the MCData server and from MCData server to MCData client.

During MCData communication, a transmitting participant can at any time indicate to stop transmission to the MCData server.

MCData server initiates the release of an ongoing MCData communication, since at least one of the communication release conditions are met e.g. lack of bearer capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on the configuration, MCData server either pre-empts the MCData communication without giving prior indication to MCData client or notifies the intent of release to the MCData client initiating communication. Latter scenario allows the MCData user to request for extension of MCData communication and defer the communication release.

The subclause describes the procedure for MCData server initiated MCData communication release with prior indication, where MCData communication is established as SDS using media plane or file distribution using media plane or file distribution using HTTP.

The procedure in Figure 7.7.2.4.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, based on communication release conditions, MCData server initiates communication release. As a result of configuration check, MCData server notifies the intent to release MCData communication, optionally requesting for more information (e.g. to know the remaining data volume to transmit) from the MCData client initiating MCData communication. Pre-conditions:

1. MCData user on MCData client 1 is already registered for receiving MCData service.
2. MCData administrator has configured the limits for the maximum amount of data and time that a participant transmits from a single request to transmit.
3. MCData communication may be ongoing between MCData participants and MCData client 1 is the initiator of the communication.
4. MCData administrator has configured the time for which MCData server needs to wait for extension request from the MCData user.

An authorized MCData user at any time during an ongoing MCData communication decides to release communication. The authorized user may decide to release MCData communication without prior indication to the initiator MCData client.

The procedure in Figure 7.7.2.5.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, authorized MCData user initiates MCData communication release without prior indication to the initiator MCData client. An authorized MCData user is part of the ongoing MCData communication. Pre-conditions:

1. An authorized MCData user on MCData client is already registered for receiving MCData service.
2. A MCData communication is ongoing between MCData participants and authorized MCData user is keeping track of which participants are receiving communication e.g. through "message delivered" and/or "message read" indications for the MCData communication.

An authorized MCData user at any time during an ongoing MCData communication decides to release communication. The authorized user may decide to release MCData communication with prior indication to the initiator MCData client. A prior indication allows initiator MCData client to request for extension for the MCData communication.

The procedure in Figure 7.7.2.6.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, authorized MCData user initiates MCData communication release with prior indication to the initiator MCData client. An authorized MCData user is part of the ongoing MCData communication. An initiator MCData user optionally decides to request for the extension of the ongoing communication. Pre-conditions:

1. An authorized MCData user on MCData client is already registered for receiving MCData service.
2. A MCData communication is ongoing between MCData participants and authorized MCData user is keeping track of which participants are receiving communication e.g. through "message delivered" and/or "message read" indications for the MCData communication
3. MCData client 1 is the initiator of the MCData communication.