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.237  Word version:  18.0.0

Top   Top   Up   Prev   Next
0…   4…   5…   5.4…   6…   6.2…   6.2.2…   6.3…   6.3.2…   6.3.2.1.3…   6.3.2.1.7…   6.3.2.1.9…   6.3.2.2…   6.3.2.3…   6.3.2.3.6…   6.3.3…   6.4…   6a…   6a.3…   6a.4…   6a.4.3…   6a.4.5…   6a.4.7…   6a.4a…   6a.5…   6a.6…   6a.7…   6a.8…   6a.9…   6a.10…   6a.11…   6c…   7…   A…   B…   C… 
6a.5 Collaborative Session release  6a.5.1 Controller UE Initiated Release Collaborative Session  6a.5.2 Remote Party Initiated Release Collaborative Session 
...

 

6a.5  Collaborative Session release  p. 141

6a.5.1  Controller UE Initiated Release Collaborative Session  p. 141

The following information flow shows the Controller UE releasing a Collaborative Session to release all the media flows with remote party. As a pre-requisite, there exists a Collaborative Session with two media flows, Media Flow-A on the Controller UE (UE-1) and Media Flow-B on the Controllee UE (UE-2).
Reproduction of 3GPP TS 23.237, Fig. 6a.5.1-1: Controller UE initiated Collaborative Session release
Figure 6a.5.1-1: Controller UE initiated Collaborative Session release
Up
Step 1.
UE-1 sends a Release Collaborative Session request to the SCC AS to release the Collaborative Session and to release the Media Flow-B on UE-2: UE-1 removes Media Flow-A that is participating in the Collaborative Session.
Step 2.
The SCC AS identifies the Collaborative Session and the participating Access Leg from Controllee UE. SCC AS sends the Release Access Leg request to UE-2. The request identifies the Access Leg that needs to be released.
Step 3.
UE-2 releases the Access Leg and sends back Release Access Leg response to SCC AS.
Step 4.
The SCC AS releases the Remote Leg using IMS session release procedure as specified in TS 23.228.
Step 5.
The SCC AS sends Release Collaborative Session response to UE-1.
Up

6a.5.2  Remote Party Initiated Release Collaborative Session  p. 142

The following shows the information flow where the remote party initiates the release of the session, which causes the SCC-AS to release the Collaborative Session.
UE-1 is a Controller UE and the other UEs are Controllee UEs.
Reproduction of 3GPP TS 23.237, Fig. 6a.5.2-1: Remote Party Initiated Release Collaborative Session
Figure 6a.5.2-1: Remote Party Initiated Release Collaborative Session
Up
Step 1.
The Remote Party decides to release the session, and therefore a Session Release Request is sent by the remote party to the SCC-AS.
Step 2.
The SCC-AS releases the Access Leg(s) towards the Controller UE-1.
Step 3.
The SCC-AS releases the Access Leg(s) towards the different Controllee UEs. This occurs in parallel with step 2.
Step 4.
When all Access Legs that belonged to the Collaborative Session have been released, the SCC-AS responds to the remote party.

Up   Top   ToC