Tech-invite  3GPPspace  IETF RFCs  SIP
index  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:  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 Communication release  7.7.1 General  7.7.2 Communication release for on-network  7.7.2.1 Information flows for communication release  7.7.2.1.1 MCData communication release request (one-to-one communication using media plane)  7.7.2.1.2 MCData communication release response (one-to-one communication using media plane)  7.7.2.1.3 MCData communication release request (group communication using media plane)  7.7.2.1.4 MCData communication release response (group communication using media plane)  7.7.2.1.8 MCData server communication release request (one-to-one communication using media plane)  7.7.2.1.9 MCData server communication release response (one-to-one communication using media plane)  7.7.2.1.10 MCData server communication release request (group communication using media plane)  7.7.2.1.11 MCData server communication release response (group communication using media plane)  7.7.2.1.13 MCData release intent request (one-to-one communication using media plane)  7.7.2.1.14 MCData more information response (one-to-one communication using media plane)  7.7.2.1.15 MCData release intent request (group communication using media plane)  7.7.2.1.16 MCData more information response (group communication using media plane)  7.7.2.1.17 MCData auth user communication release request (one-to-one communication using media plane)  7.7.2.1.18 MCData auth user communication release response (one-to-one communication using media plane)  7.7.2.1.19 MCData auth user communication release request (group communication using media plane)  7.7.2.1.20 MCData auth user communication release response (group communication using media plane)  7.7.2.1.21 MCData request for extension  7.7.2.1.22 MCData response for extension  7.7.2.2 MCData user initiated communication release 
...

 

7.7  Communication release  p. 148

7.7.1  General  p. 148

The subclauses below describe the MCData communication release procedures, which may be initiated either by the sender or the MCData server or the authorized MCData user.

7.7.2  Communication release for on-network  p. 148

7.7.2.1  Information flows for communication release  p. 148

7.7.2.1.1  MCData communication release request (one-to-one communication using media plane)  p. 148
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.
Information Element Status Description
MCData IDMThe identity of the MCData user uploading data
MCData IDMMCData ID on which the communication is to be released
Up
7.7.2.1.2  MCData communication release response (one-to-one communication using media plane)  p. 148
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.
Information Element Status Description
MCData IDMThe identity of the MCData user requesting to upload data
MCData IDMMCData ID on which the communication is released
Release confirmationMCommunication released or not indication
Up
7.7.2.1.3  MCData communication release request (group communication using media plane)  p. 149
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.
Information Element Status Description
MCData IDMThe identity of the MCData user uploading data
MCData group IDMMCData group ID on which the communication is to be released
Up
7.7.2.1.4  MCData communication release response (group communication using media plane)  p. 149
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.
Information Element Status Description
MCData IDMThe identity of the MCData user requesting to upload data
MCData group IDMMCData group ID on which the communication is released
Release confirmationMCommunication released or not indication
Up
7.7.2.1.5  Void
7.7.2.1.6  Void
7.7.2.1.7  Void
7.7.2.1.8  MCData server communication release request (one-to-one communication using media plane) |R15|  p. 149
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.
Information Element Status Description
MCData IDMThe identity of the MCData user to which communication is released
Conversation IdentifierMIdentifies the conversation
Release ReasonMIndicates reason for the release
Up
7.7.2.1.9  MCData server communication release response (one-to-one communication using media plane) |R15|  p. 150
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.
Information Element Status Description
MCData IDMMCData ID to which the communication is released
Conversation IdentifierMIdentifies the conversation
Release confirmationMCommunication released or not indication
Up
7.7.2.1.10  MCData server communication release request (group communication using media plane) |R15|  p. 150
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.
Information Element Status Description
MCData IDMThe identity of the MCData user to which communication is released
MCData group IDMMCData group ID on which the communication is released
Conversation IdentifierMIdentifies the conversation
Release ReasonMIndicates reason for the release
Up
7.7.2.1.11  MCData server communication release response (group communication using media plane) |R15|  p. 150
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.
Information Element Status Description
MCData IDMMCData ID to which the communication is released
MCData group IDMMCData group ID on which the communication is released
Conversation IdentifierMIdentifies the conversation
Release confirmationMCommunication released or not indication
Up
7.7.2.1.12  Void
7.7.2.1.13  MCData release intent request (one-to-one communication using media plane) |R15|  p. 151
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.
Information Element Status Description
MCData IDMThe identity of the MCData user who is originator of the one-to-one communication
Conversation IdentifierMIdentifies the conversation
Request for more infoOIndicates what MCData server needs more information (e.g. to know the remaining data volume to transmit) about the communication which has been identified to be released
Up
7.7.2.1.14  MCData more information response (one-to-one communication using media plane) |R15|  p. 151
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.
Information Element Status Description
MCData IDMThe identity of the MCData user who is originator of the one-to-one communication
Conversation IdentifierMIdentifies the conversation
More infoMInformation as requested by MCData server
Up
7.7.2.1.15  MCData release intent request (group communication using media plane) |R15|  p. 151
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.
Information Element Status Description
MCData IDMThe identity of the MCData user who is the originator of the group communication
Conversation IdentifierMIdentifies the conversation
MCData group IDMMCData group ID on which the communication is released
Request for more infoOIndicates what MCData server needs more information about the communication which has been identified to be released
Up
7.7.2.1.16  MCData more information response (group communication using media plane) |R15|  p. 151
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.
Information Element Status Description
MCData IDMThe identity of the MCData user who is originator of the group communication
Conversation IdentifierMIdentifies the conversation
MCData group IDMMCData group ID on which the communication is released
More infoMInformation as requested by MCData server
Up
7.7.2.1.17  MCData auth user communication release request (one-to-one communication using media plane) |R15|  p. 152
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.
Information Element Status Description
Conversation IdentifierMIdentifies the conversation
Request for more infoOIndicates what MCData server needs more information about the communication which has been identified to be released
Release ReasonMIndicates reason for the release
Up
7.7.2.1.18  MCData auth user communication release response (one-to-one communication using media plane) |R15|  p. 152
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.
Information Element Status Description
Conversation IdentifierMIdentifies the conversation
Release confirmationMCommunication released or not indication
Up
7.7.2.1.19  MCData auth user communication release request (group communication using media plane) |R15|  p. 152
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.
Information Element Status Description
Conversation IdentifierMIdentifies the conversation
MCData group IDMMCData group ID on which the communication is to be released
Request for more infoOIndicates what MCData server needs more information about the communication which has been identified to be released
Release ReasonMIndicates reason for the release
Up
7.7.2.1.20  MCData auth user communication release response (group communication using media plane) |R15|  p. 153
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.
Information Element Status Description
Conversation IdentifierMIdentifies the conversation
MCData group IDMMCData group ID on which the communication is to be released
Release confirmationMCommunication released or not indication
Up
7.7.2.1.21  MCData request for extension |R15|  p. 153
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.
Information Element Status Description
Conversation IdentifierMIdentifies the conversation
Up
7.7.2.1.22  MCData response for extension |R15|  p. 153
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.
Information Element Status Description
Conversation IdentifierMIdentifies the conversation
Extension responseMIndicates whether request for extension has been accepted or not
Up

7.7.2.2  MCData user initiated communication release  p. 153

7.7.2.2.1  General  p. 153
During MCData communication, a transmitting participant can at any time indicate to stop transmission to the MCData server.
7.7.2.2.2  Release of MCData communication using media plane  p. 153
7.7.2.2.2.1  General  p. 153
The subclause describes the procedure for MCData user initiated MCData communication release where MCData communication is established as SDS using media plane or SDS session or file distribution using media plane.
7.7.2.2.2.2  Procedure  p. 154
The procedure in Figure 7.7.2.2.2.2-1 describes signalling control plane procedure for the case where MCData communication is ongoing and transmitting participant initiates MCData communication release. The procedure is applicable for one-to-one and group MCData communications.
Pre-conditions:
  1. MCData users on MCData client 1 and client 2 are already registered for receiving MCData service.
  2. MCData communication is established between MCData client 1 and MCData client 2 and MCData client1 is the initiator of the MCData communication.
Copy of original 3GPP image for 3GPP TS 23.282, Fig. 7.7.2.2.2.2-1: Release of MCData communication using media plane
Figure 7.7.2.2.2.2-1: Release of MCData communication using media plane
(⇒ copy of original 3GPP image)
Up
Step 1.
MCData user at MCData client 1 requests to release ongoing MCData communication.
Step 2.
MCData client 1 sends MCData communication release request towards MCData server, for tearing down the communication with the other MCData client(s).
Step 3.
MCData server sends MCData communication release request to all the participants of the MCData communication.
Step 4.
Recipient MCData clients notifies respective MCData user about the release of MCData communication.
Step 5.
MCData clients receiving the MCData communication release request provide communication release response back towards MCData server.
Step 6.
MCData server sends MCData communication release response back to MCData client 1.
Step 7.
All participants of the MCData communication have successfully released the media plane resources associated with the MCData communication that is released.
Step 8.
MCData client 1 notifies the MCData user about the communication release.
Up
7.7.2.2.3  Release of MCData communication using HTTP  p. 154

Up   Top   ToC