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.4.3 Controller UE Initiated Release Media (media flow on the Controller UE)  6a.4.4 Controller UE Initiated Release Media (media flow on the Controllee UE)  6a.4.4.1 Controller UE and Controllee UE belong to the same subscription  6a.4.4.2 Controller UE and Controllee UE belong to different subscriptions  6a.4.4a Controller UE initiated modify media (media flow on the Controllee UE)  6a.4.4a.1 Controller UE and Controllee UE belong to the same IMS subscription  6a.4.4a.2 Controller UE and Controllee UE belong to different IMS subscriptions under the same operator 
...

 

6a.4.3  Controller UE Initiated Release Media (media flow on the Controller UE)  p. 122

The information flow shows the Controller UE releasing a media flow that is originated from the Controller UE. As a pre-requisite, there exists a Collaborative Session with two media flows, flow-A on the Controller UE (UE-1) and Flow-B on the Controllee UE (UE-2).
Reproduction of 3GPP TS 23.237, Fig. 6a.4.3-1: Controller UE Initiated Media release - media on Controller UE
Figure 6a.4.3-1: Controller UE Initiated Media release - media on Controller UE
Up
Step 1.
UE-1 sends a Release Media request to the SCC AS to remove Media-A from the Collaborative Session. The IUT media release request shall include enough information for the SCC AS to:
  • identify that the media is Media Flow-A;
  • identify that the released media is on UE-1;
  • keep the control of Collaborative Session in UE-1.
Step 2.
The SCC AS updates the Remote Leg with media flow -A removed.
Step 3.
The SCC AS sends release media response to UE-1. UE-1 releases media flow - A at its end.
The Collaborative Session continues to exist after the procedure is complete.
Up

6a.4.4  Controller UE Initiated Release Media (media flow on the Controllee UE)  p. 123

6a.4.4.1  Controller UE and Controllee UE belong to the same subscription |R10|  p. 123

The information flow shows the Controller UE releasing a media flow from a Controllee UE. As a pre-requisite, there exists a Collaborative Session with two media flows, flow-A on the Controller UE (UE-1) and Flow-B on the Controllee UE (UE-2).
Reproduction of 3GPP TS 23.237, Fig. 6a.4.4.1-1: Controller UE Initiated Media release - media flow on Controllee UE (Controller and Controllee belong to the same IMS subscription)
Figure 6a.4.4.1-1: Controller UE Initiated Media release - media flow on Controllee UE (Controller and Controllee belong to the same IMS subscription)
Up
Step 1.
UE-1 sends a Release Media request to the SCC AS to remove Media-A from the Collaborative Session. The request includes the information pertaining to media flow -B:
  • identify that the released media is Media Flow-B;
  • identify that the released media is on UE-2;
  • keep the control of Collaborative Session in UE-1.
Step 2.
The SCC identifies media flow B as associated with UE-2 (controllee UE) and sends the Release Media Request to UE-2. The request identifies the media flow-B that needs to be removed and the media flow is removed. If no more media flows remain on UE-2 that are participating in the Collaborative Session, the SCC AS releases the access leg from UE-2.
Step 3.
UE-2 sends back Release Media response back to SCC AS.
Step 4.
The SCC AS updates the Remote Leg with media flow-B removed.
Step 2 and step 4 may be executed in any order.
Step 5.
The SCC AS sends release media response to UE-1.
If UE-2 has left the Collaborative Session at step 2 and no other Controllee UE remain in this Collaborative Session, this Collaborative Session becomes a normal IMS session.
Up

6a.4.4.2  Controller UE and Controllee UE belong to different subscriptions |R10|  p. 124

The following information flow shows the Controller UE releasing a media flow from the Controllee UE that belongs to different subscriptions. As a pre-requisite, there exists a Collaborative Session with two media flows, Media-A on the Controller UE (UE-1) and Media-B on the Controllee UE (UE-2). Furthermore, Controller UE and Controllee UE profiles are stored on different S-CSCFs, S-CSCF-1 and S-CSCF-2, respectively.
Reproduction of 3GPP TS 23.237, Fig. 6a.4.4.2-1: Controller initiated Release of media from Controllee UE (Controller and Controllee belong to different IMS subscriptions)
Figure 6a.4.4.2-1: Controller initiated Release of media from Controllee UE (Controller and Controllee belong to different IMS subscriptions)
Up
Step 1.
Controller UE-1 sends a Release media request to SCC AS-1 to release Media-B on Controllee UE-2. The Collaborative Session request includes enough information for the network to:
  • identify that the media to be released is Media-B;
  • identify that the media to be held is on Controllee UE-2;
  • identify the session that contains of the media flow to be released;
  • keep the control of the Collaborative Session in Controller UE-1.
Step 2a.
S-CSCF-1 forwards the Release Media request to SCC AS-1.
Step 2b.
SCC AS-1 verifies that UE-1 is a Controller and therefore is authorized to release the media from a Controllee UE with a user belonging to another subscription.
Step 2c.
SCC AS-1 sends a Release Media request towards UE-2 to release Media-B on UE-2. The Collaborative Session request includes enough information for the network to:
  • identify the source of the release media request as UE-1;
  • identify that the media flow to be released is Media-B;
  • identify that the source of the media flow to be released is Controllee UE-2.
Step 3.
S-CSCF-1 forwards the Release Media request towards S-CSCF-2.
Step 4.
S-CSCF-2 forwards the Release Media Request towards the Controllee.
Step 5.
Controllee UE-2 provides the Release Media Response to the S-CSCF-2.
Step 6-7.
S-CSCF-2 forwards the Release Media Response to SCC-AS-1.
Step 8.
The SCC AS-1 updates the remote leg of the collaborative session with Media-B released.
Step 9-10.
The SCC AS-1 informs the Controller UE-1 via the S-CSCF-1 of successfully releasing Media-B from Controllee UE 2. Steps 9-10 could be performed in parallel to Step 10.
Up

6a.4.4a  Controller UE initiated modify media (media flow on the Controllee UE) |R10|  p. 125

6a.4.4a.1  Controller UE and Controllee UE belong to the same IMS subscription  p. 125

The information flow shows a Controller UE modifying a Media Flow that is originated from or terminated at the Controllee UE belonging to the same IMS subscription. 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). Controller UE-1 can initiate re-negotiation of media information of Controllee UE-2 with remote party.
Reproduction of 3GPP TS 23.237, Fig. 6a.4.4a.1-1: Controller UE initiated media modify on a Controllee UE belonging to the same IMS subscription
Figure 6a.4.4a.1-1: Controller UE initiated media modify on a Controllee UE belonging to the same IMS subscription
Up
Step 1.
UE-1 sends a Modify Media Request to modify Media Flow-B on UE-2. The request includes media modification information pertaining to Media Flow-B. The IUT media modification request shall include enough information for the SCC AS to:
  • identify that the modified media is Media Flow-B;
  • identify that the modified media is on UE-2;
  • identify the modification requested to Media Flow-B;
  • keep the control of Collaborative Session in UE-1.
Step 2.
The SCC identifies Media Flow-B as associated with UE-2 and sends the Modify Media Request to UE-2. The request identifies the Media Flow-B that needs to be modified.UE-2 modifies the Media Flow-B. The SCC AS updates the Remote Leg with Media Flow-B modified.
Step 3.
The SCC AS sends Modify Media Response to UE-1.
Up

6a.4.4a.2  Controller UE and Controllee UE belong to different IMS subscriptions under the same operator  p. 126

The information flow shows a Controller UE modifying a Media Flow that is originated from or terminated at the Controllee UE belonging to different subscription. It is assumed that UE-1 and UE-2 belong to User-1 and User-2, respectively. 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). Controller UE-1 can initiate re-negotiation of media information of Controllee UE-2 with remote party.
Reproduction of 3GPP TS 23.237, Fig. 6a.4.4a.2-1: Controller UE initiated media modify on a Controllee UE belonging to different IMS subscription
Figure 6a.4.4a.2-1: Controller UE initiated media modify on a Controllee UE belonging to different IMS subscription
Up
Step 1.
UE-1 sends a Modify Media Request to SCC AS-1 serving UE-1 to modify Media Flow-B on UE-2. The request includes media modification information pertaining to Media Flow-B. The IUT media modification request shall include enough information for the SCC AS-1 to:
  • identify that the modified media is Media Flow-B;
  • identify that the modified media is on UE-2;
  • identify the modification requested to Media Flow-B;
  • keep the control of Collaborative Session in UE-1.
Step 2.
The SCC AS-1 authorizes the request from UE-1 as specified in clause 6a.12.
Step 3.
The SCC AS-1 sends the Modify Media Request to SCC AS-2 that serves UE-2 via S-CSCF-1 and S-CSCF-2.
Step 4.
If UE-2 is an IUT subscriber, the request is routed via SCC AS-2 which authorizes the request. The Modify Media Request is then routed on towards UE-2. If UE-2 is not an IUT subscriber, S-CSCF-2 routes the request according to normal procedures.
Step 5.
S-CSCF-2 forwards the Modify Media Request to UE-2. UE-2 modifies Media Flow-B.
Step 6.
The UE-2 sends a Modify Media Response towards SCC AS-1.
Step 7 - 8.
S-CSCF-2 routes the Modify Media Response back towards SCC AS-1 - via SCC AS-2 if UE-2 is an IUT subscriber.
Step 9.
The SCC AS-1 updates the Remote Leg with Media Flow-B modified upon receiving the Modify Media Response from UE-2.
Step 10.
The SCC AS-1 sends Modify Media Response to UE-1.
Up

Up   Top   ToC