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.5 Controllee UE initiated release media on itself  6a.4.6 Controllee UE initiated modify media on itself  6a.4.6.0 General  6a.4.6.1 Controller UE and Controllee UE belong to the same IMS subscription  6a.4.6.2 Controller UE and Controllee UE belong different IMS subscriptions under the same operator  6a.4.6a Controllee UE initiated add new media on another Controllee UE 
...

 

6a.4.5  Controllee UE initiated release media on itself  p. 127

As per standard IMS UE behaviour, a Controllee UE may initiate a release of a media flow that it terminates. In this case, this media release on the access leg is notified to the Controller UE, which may decide to transfer this media flow to another UE under the same subscription, or to remove it from the Collaborative Session (i.e. remove it on the remote leg).
The following information flow shows a Controllee UE initiating the release of a media flow that it terminates, and Controller UE being informed of this release by the SCC AS. As a pre-requisite, there exists a Collaborative Session of which UE-1 is the Controller UE and UE-2 is a Controllee UE terminating a media flow, Media Flow A. There may be other media flows (on UE 1, UE-2 or other UEs) within the Collaborative Session; such media flows and UEs are not shown on this information flow; they shall not be impacted by this operation.
Reproduction of 3GPP TS 23.237, Fig. 6a.4.5-1: Controllee UE initiated release media flow on itself
Figure 6a.4.5-1: Controllee UE initiated release media flow on itself
Up
Step 1.
Controllee UE-2 sends a request to release Media Flow A (that it terminates), using standard IMS procedure.
Step 2.
The SCC AS identifies that Media Flow A is under Collaborative Session control of UE-1. The SCC AS indicates to Controller UE-1 that Controllee UE-2 has released Media Flow A.
Step 3.
Controller UE-1 initiates one of the following procedures, in order to transfer Media Flow A to another UE under the same subscription, or to remove it from the Collaborative Session:
  • Controller UE initiated media transfer from Controllee UE to Controller UE, specified in clause 6a.3.2;
  • Controller UE initiated media transfer from Controllee UE to another Controllee UE, specified in clause 6a.3.3;
  • Controller UE initiated release media (media flow on the Controllee UE), specified in clause 6a.4.3;
  • Controller UE initiated release Collaborative Session, specified in clause 6a.5.1.
Step 4.
The SCC AS updates the Remote Leg while executing the procedure initiated by Controller UE-1 at step 3.
Up

6a.4.6  Controllee UE initiated modify media on itself  p. 128

6a.4.6.0  General |R10|  p. 128

As per standard IMS UE behaviour, a Controllee UE may initiate a modification of a media flow that it terminates.

6a.4.6.1  Controller UE and Controllee UE belong to the same IMS subscription |R10|  p. 128

The following information flow shows a Controllee UE initiating the modification of a media flow that it terminates. As a pre-requisite, there exists a Collaborative Session of which UE-1 is the Controller UE and UE-2 is a Controllee UE terminating a media flow, Media Flow A. There may be other media flows (on UE-1, UE-2 or other UEs) within the Collaborative Session; such media flows and UEs are not shown on this information flow; they shall not be impacted by this operation.
Reproduction of 3GPP TS 23.237, Fig. 6a.4.6.1-1: Controllee UE initiated modify media flow on itself (same IMS subscription)
Figure 6a.4.6.1-1: Controllee UE initiated modify media flow on itself (same IMS subscription)
Up
Step 1.
Controllee UE-2 sends a request to modify the characteristics of Media Flow-A (that it terminates), using standard IMS procedure.
Step 2.
The SCC AS updates the Remote Leg for allowed media changes, providing the new media flow characteristics from UE-2.
Step 3.
The SCC AS sends a successful response to the request sent by UE-2 at step 1.

6a.4.6.2  Controller UE and Controllee UE belong different IMS subscriptions under the same operator |R10|  p. 129

The information flow shows a Controllee UE modifying a Media Flow that is originated from or terminated at the same Controllee UE. 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.4.6.2-1: Controllee UE initiated media modify on itself (different IMS subscriptions under the same operator)
Figure 6a.4.6.2-1: Controllee UE initiated media modify on itself (different IMS subscriptions under the same operator)
Up
Step 1.
UE-2 sends a Modify media request to modify Media Flow-B on itself. 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; and
  • identify the modification requested to Media Flow-B.
Step 2.
The SCC AS-2 forwards the Media Modification Request to SCC AS-1 that serves the controller via S-CSCF-2 and S-CSCF-1.
Step 3.
The SCC AS-1 authorizes the Media Modification Request as specified in clause 6a.12.
Step 3a~3b.
If SCC AS-1 cannot authorize Media Modification Request, it queries controller UE-1 for authorization.
Step 4.
SCC AS-1 identifies Media Flow-B as associated with UE-2 and sends Modify Media Request to UE-2 via S-CSCF-1 and S-CSCF-2. UE-2 modifies the Media Flow. The SCC AS-1 updates the Remote Leg with Media Flow-B modified.
Step 5.
The SCC AS-1 sends result of modify media request to UE-2.
Up

6a.4.6a  Controllee UE initiated add new media on another Controllee UE |R10|  p. 130

This information flow shows the Controllee UE-2 adding a media flow to another Controllee (UE-3). As a pre-requisite, there exists a Collaborative Session with a media flow, Media-A, on the Controllee UE (UE-2). UE-3 might or might not be part of the Collaborative Session before the media addition. Furthermore, Controller UE 1 and Controllee UE-2 profiles are served by different IUT SCC AS: SCC AS-1 and SCC AS-2, which are in turn attached to S-CSCF-1 and S-CSCF-2 respectively. For simplicity, these S-CSCFs are not shown in the following Figure.
Reproduction of 3GPP TS 23.237, Fig. 6a.4.6a-1: Controllee initiated addition of media to another Controllee UE (Controller and Controllees belong to different IMS subscriptions)
Figure 6a.4.6a-1: Controllee initiated addition of media to another Controllee UE (Controller and Controllees belong to different IMS subscriptions)
Up
Step 1.
UE-2 sends a Collaborative session request to SCC AS-2 to add Media-B to UE-3. The Collaborative Session request includes enough information for the network to:
  • identify that the media to be added is Media-B;
  • identify that the target for the media to be added to is UE-3;
  • identify the session that contains of the media flow to be added;
  • Controller of the Collaborative Session is UE-1.
Step 2.
SCC AS-2 authorizes the request from UE-2 as specified in clause 6a.12 and identifies that the session is a Collaborative Session anchored at SCC AS-1.
Step 3.
SCC AS-2 then forwards the Collaborative session request to SCC AS-1 which is the SCC AS for the Controller UE in order to add Media-B to UE-3.
Step 4-6.
SCC AS-1 sends a Collaborative session request to the Controller UE-1, and the Controller UE-1 authorizes the media addition request.
Step 7.
SCC AS-1 sends Session request to add Media-B to UE-3 via S-CSCF-3. The Session request includes enough information for the network to:
  • identify the source of the addition request as UE-1;
  • identify the remote party;
  • identify that the media flow to be added is Media-B;
  • identify that the target of the media flow to be added is UE-3;
Step 8.
S-CSCF-3 forwards the Session request to UE-3.
Step 9.
UE-3 sends a Session response to S-CSCF-3.
Step 10.
S-CSCF-3 forwards Session response to SCC AS-1.
Step 11.
SCC AS-1 updates remote leg with Remote Leg Update Procedure.
Step 12.
SCC AS-2 sends the Collaborative session response to UE-2.
When the Inter-UE Transfer is completed, UE-1 keeps the Collaborative Session Control.
Up

Up   Top   ToC