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.7.2.3  MCData server initiated communication release without prior indicationp. 155

7.7.2.3.1  Generalp. 155
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.
Up
7.7.2.3.2  Release of MCData communication using media planep. 155
7.7.2.3.2.1  Generalp. 155
The subclause describes the procedure for MCData server initiated MCData communication release without prior indication, where MCData communication is established as SDS using media plane or file distribution using media plane.
7.7.2.3.2.2  Procedurep. 155
The procedure in Figure 7.7.2.3.2.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, based on communication release conditions, MCData server initiates the communication release. The procedure is applicable for one-to-one and group communication.
Pre-conditions:
  1. MCData users on MCData client 1, client 2 and client 3 are already registered for receiving MCData service.
  2. A 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. A MCData communication is ongoing between MCData client 1, client 2 and client 3.
Copy of original 3GPP image for 3GPP TS 23.282, Fig. 7.7.2.3.2.2-1: MCData server initiated release of MCData communication using media plane
Up
Step 1.
MCData server would like to release the ongoing MCData communication, identified by conversation identifier, since at least one of the release conditions are met e.g. lack of capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on configuration, MCData server decides to pre-empt the MCData communication without giving prior indication to MCData client 1.
Step 2.
MCData server identifies the participants of the ongoing MCData communication and generates communication release request to release ongoing MCData communication.
Step 3.
MCData server sends server MCData communication release request towards each participant of the MCData communication.
Step 4.
MCData users are notified about the release of the MCData communication.
Step 5.
MCData client at each MCData communication participant sends server MCData communication release response towards the MCData server.
Step 6.
All participants of the MCData communication have successfully released the media plane resources associated with the MCData communication that is released.
Up
7.7.2.3.3Void

7.7.2.4  MCData server initiated communication release with prior indicationp. 157

7.7.2.4.1  Generalp. 157
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.
7.7.2.4.2  Procedurep. 157
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.
Copy of original 3GPP image for 3GPP TS 23.282, Fig. 7.7.2.4.2-1: MCData server initiates communication release with prior indication
Up
Step 1.
MCData server releases the ongoing MCData communication, identified by the conversation identifier, since at least one of the release conditions are met e.g. lack of 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 notifies the intent to release MCData communication.
Step 2.
MCData server sends the MCData release intent request towards the communication initiating MCData client 1. MCData server may include request for more information (e.g. to know the remaining data volume to transmit).
Step 3.
MCData client 1 informs MCData user about the intent to release communication.
Step 4.
If request for more information is included in the received MCData release intent request, MCData client 1 sends MCData more information response including the remaining amount of data to transmit. Upon receiving more information response from MCData client 1, MCData server may wait for the request for extension until the time configured by the MCData administrator. If MCData server does not receive MCData request for extension within the configured timeout, the MCData server releases MCData communication as described in subclause 7.7.2.3. Otherwise, continue with remaining steps.
Step 5.
MCData user at MCData client 1 requests for extension of the ongoing MCData communication.
Step 6.
MCData client 1 sends MCData request for extension of the MCData communication.
Step 7.
Upon receiving the MCData request for extension of MCData communication from the MCData client 1, MCData server asserts policies to accept or reject the request for extension.
Step 8.
MCData server sends MCData response for extension with success or failure result to MCData client 1. MCData communication will continue if MCData server accepted the request for extension from MCData client 1. Otherwise, MCData communication is released according to procedures described in subclause 7.7.2.3.
Up

7.7.2.5  Authorized MCData user initiated communication release without prior indicationp. 158

7.7.2.5.1  Generalp. 158
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.
7.7.2.5.2  Procedurep. 158
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.
Copy of original 3GPP image for 3GPP TS 23.282, Fig. 7.7.2.5.2-1: An authorized MCData user initiates communication release without prior indication
Up
Step 1.
An authorized MCData user requests to release the ongoing MCData communication, without providing prior indication to the initiator of the MCData communication, MCData client 1.
Step 2.
An authorized MCData client sends MCData auth user communication release request towards MCData server identifying the MCData communication to release. The request also includes indication to the MCData server to release MCData communication without prior indication to the initiator of the MCData communication, MCData client 1.
Step 3.
MCData server validates the user from whom the MCData communication release request is received and checks whether the requesting MCData user is authorized to release communication or not.
Step 4.
If the user is authorized to release communication, then MCData server releases the ongoing MCData communication according to procedures described in subclause 7.7.2.3.
Step 5.
MCData server sends MCData auth user communication release response containing the result of MCData communication release back to authorized MCData client 1.
Up

7.7.2.6  Authorized MCData user initiated communication release with prior indicationp. 159

7.7.2.6.1  Generalp. 159
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.
7.7.2.6.2  Procedurep. 159
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.
Copy of original 3GPP image for 3GPP TS 23.282, Fig. 7.7.2.6.2-1: An authorized MCData user initiates communication release with prior indication
Up
Step 1.
An authorized MCData user requests to release the ongoing MCData communication by providing prior indication to the initiator of MCData communication, MCData client 1.
Step 2.
An authorized MCData client sends MCData auth user communication release request towards MCData server including the communication identifier identifying the MCData communication to release. Authorized MCData client may include request for more information (e.g. to know the remaining data volume to transmit). The request also includes indication to MCData server to release MCData communication with prior indication to the initiator MCData client.
Step 3.
MCData server validates the user from whom the communication release request is received and checks whether the requesting user is authorized to release communication or not.
Step 4.
If the user is authorized to release communication, then the MCData server sends MCData release intent request, may be including the reason for the release. MCData server may include request for more information as received in the request from the authorized MCData client.
Step 5.
MCData client informs MCData user about the intent to release communication by the authorized MCData user.
Step 6.
If request for more information is included in the received MCData release intent request, MCData client 1 sends MCData more information response including the remaining amount of data to transmit.
Step 7.
MCData server forwards the MCData more information response to the authorized MCData client.
Step 8.
MCData user at MCData client 1 decides to request for extension of the ongoing MCData communication.
Step 9 and 10.
MCData client sends MCData request for extension towards MCData server. And MCData server forwards the MCData request for extension towards the authorized MCData client.
Step 11.
Authorized MCData client notifies the authorized user about the incoming request for extension. An authorized MCData user decides to accept or reject the request for extension.
Step 12 and 13.
Authorized MCData user decision is sent in MCData response for extension request towards the MCData server. MCData server forwards the MCData response for extension request to MCData client 1.
Step 14.
MCData communication will continue if the authorized user accepted the request for extension from MCData client 1. Otherwise, MCData communication will be released according to procedures described in subclause 7.7.2.3.
Step 15.
After MCData communication is released, MCData server sends the MCData auth user communication release response back to the authorized MCData client.
Up

Up   Top   ToC