Content for TS 23.237 Word version: 18.0.0

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.7 Remote party initiated add new media 6a.4.8 Remote party initiated release media 6a.4.9 Remote party initiated media modification
...

6a.4.7 Remote party initiated add new media p. 131

The following is an example of an information flow where remote party wants to modify an existing session with UE-1 to add Media Flow-B. In this information flow, UE-1 and UE-2 belong to the same user subscription. UE-1 is the Controller UE and UE-2 is a Controllee UE. If UE-2 is not involved in the Collaborative Session controlled by UE-1 before the media addition, there is at least another Controllee UE involved in the Collaborative Session before the media addition which is not shown in the information flow.

Reproduction of 3GPP TS 23.237, Fig. 6a.4.7-1: Remote party initiated add new media

Figure 6a.4.7-1: Remote party initiated add new media

Step 1.

Remote party sends an Add Media request to add Media Flow-B to an existing session between UE-1 and remote party as per TS 23.228.

Step 2.

SCC AS forwards the Add Media request to UE-1 according to the procedures defined in TS 23.228.

Step 3a is for the case Controller UE wants to add Media Flow-B to itself.

Step 3a.

The session setup is completed. The new Media Flow-B will after this be established between UE-1 and remote party, and be involved in the Collaborative Session controlled by UE-1.

Steps 3b and 5b are for the case Controller UE wants to add Media Flow-B to a different UE while retaining control for the added media.

Step 3b.

Controller UE-1 sends an IUT-Redirect-Media request to SCC AS. The IUT-Redirect-Media request needs to include at least the following information:

identify that Media Flow-B needs to be redirected to UE-2.

Step 4b.

SCC AS performs authorization as specified in clause 6a.12, then sends an Add Media Flow-B to UE-2.

Step 5b.

The session setup is completed. When the add media operation is completed, there is Media Flow-B between UE-2 and remote party. There is a Collaborative Session established between UE-1 and UE-2. The Media-B is controlled by UE-1.

6a.4.8 Remote party initiated release media p. 133

The following is an example of an information flow where remote party wants to remove one of media flows, Media Flow-B from an ongoing session. In this information flow, UE-1 and UE-2 belong to the same user subscription. UE-1 is a Controller UE and UE-2 is a Controllee UE.

Reproduction of 3GPP TS 23.237, Fig. 6a.4.8-1: Remote party initiated release media

Figure 6a.4.8-1: Remote party initiated release media

Step 1.

Remote party uses standard IMS procedures defined in TS 23.228 to remove Media Flow-B from the session.

Step 2a is for the case the released media is bound to Controller UE.

Step 2a.

The removal of Media Flow-B between Controller UE-1 and remote party is completed.

Steps 2b and 3b are for the case the released media is bound to Controllee UE.

Step 2b.

The removal of Media Flow-B between Controllee UE-2 and remote party is completed.

Step 3b.

SCC AS informs Controller UE-1 that the Media Flow-B on UE-2 was removed.

6a.4.9 Remote party initiated media modification p. 134

A Collaborative Session is already established using procedures shown in clause 6a.2. The following is an example of an information flow where remote party wants to modify one of media flows, Media Flow-B from an ongoing session. In this information flow, UE-1 and UE-2 belong to the same user subscription. UE-1 is a Controller UE and UE-2 is a Controllee UE.

Reproduction of 3GPP TS 23.237, Fig. 6a.4.9-1: Remote party initiated media modification

Figure 6a.4.9-1: Remote party initiated media modification

Step 1.

Remote party uses standard IMS procedures defined in TS 23.228 to modify Media Flow-B from the session.

Step 2a is for the case the modified media is bound to Controller UE.

Step 2a.

The modification of Media Flow-B between Controller UE-1 and remote party is completed.

Steps 2b - 3b are for the case the modified media is bound to Controllee UE.

Step 2b.

The modification of Media Flow-B between Controllee UE-2 and remote party is completed.

Step 3b.

If the media modification is hold or resume, SCC AS informs Controller UE-1 that the Media Flow-B on UE-2 was modified.