UE-1, UE-2 are engaged in a Collaborative Session established using procedures shown in
clause 6a.2 for which UE-1 is the Controller UE and UE-2 is a Controllee UE, the following flows shows how the Controller UE-1 adds a media flow to Controllee UE-2 which could result in a new Access Leg for the Controllee UE-2, or it could be an additional media flow for an already existing session for the Controllee UE-2. The following information flow also applies to case in which UE-2 may not be part of Collaborative Session before the media addition. In this case, there is at least another Controllee UE involved in the Collaborative Session before the media addition, which is not shown in the information flow.
Step 1.
Controller UE-1 decides to add a new media flow to Controllee UE-2, and performs an IUT add media request for the particular media requested. The IUT add media request shall include enough information for the SCC AS to:
-
identify that the added media flow is Media Flow-A;
-
identify that the target of the added media flow is Controllee UE-2.
Step 2.
The SCC AS performs authorization as specified in
clause 6a.12. Then, the new Media Flow-A is setup for Controllee UE-2. The Remote Leg is updated as well with the newly added media flow using the Remote Leg Update procedure as specified in
clause 6a.1.2. After this, the new media flow will be established between Controllee UE-2 and the Remote Party.
Step 3.
The IUT addition of media is completed.
The information flow below illustrates a scenario in which UE-1, the Controller UE of a Collaborative Session, invites a UE that belongs to a second user to participate in the Collaborative Session by adding a new media flow towards it; control of the Collaborative Session remains with UE-1.
There is Media-A between Controller UE-1 and remote party.
Step 1.
Controller UE-1 sends a request towards SCC AS-1 to add Media-B on UE-2, as part of the same Collaborative Session of Media-A. The request includes enough information for the network to:
-
identify that the added media flow is Media-B and the requested media type associated with Media-B (e.g. video);
-
identify that the target of the added media flow is UE-2.
Step 2.
S-CSCF-1 forwards the request to SCC AS-1.
Step 3.
SCC AS-1 authorizes the request from UE-1 as specified in
clause 6a.12.
Step 4.
SCC AS-1 sends a request towards UE-2 for adding Media-B to Controllee UE-2. The request includes enough information for the network to:
-
identify the source of the request as UE-1;
-
identify the remote party;
-
identify that the added media flow is Media-B and the media type associated with Media-B (e.g., video);
-
identify that the source of the added media flow is Controller UE-1;
-
identify that the target of the added media flow is Controllee UE-2.
Step 4a.
S-CSCF-1 forwards the request towards UE-2.
Step 5.
If UE-2 is an IUT subscriber, the request is routed via SCC AS-2 which authorizes the request. SCC AS-2 notes that this request relates to the establishment of a Collaborative Session so that any requests by UE-2 related to this Collaborative Session will be forwarded back towards SCC AS-1. A Session Setup 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 6.
S-CSCF-2 forwards the Session Setup request towards UE-2.
Step 7.
UE-2 sends a Session Setup response towards SCC AS-1. This request contains the full media description of Media-B.
Step 8 - 9.
S-CSCF-2 routes the response back towards SCC AS-1 via SCC AS-2 if UE-2 is an IUT subscriber.
Step 10.
S-CSCF-1 forwards the Session Setup response to SCC AS-1.
Step 11.
SCC AS-1 updates Remote Leg and finishes Access Leg establishment for adding Media-B to UE-2, and updates the media information in Controller UE-1.
After the above operation, Media-B is established between Controllee UE-2 and remote party.