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.10 Media Flow Replication by network 6a.10.1 Replicating media in network from Controller UE to another UE belonging to same IMS subscription 6a.10.2 Replicating media in network from Controller UE to another UE belonging to different IMS subscription 6a.10.3 Replicating media in network from Controller UE to another UE belonging to same IMS subscription - pull mode 6a.10.4 Replicating media in network from Controller UE to another UE belonging to different IMS subscription - pull mode
...

6a.10 Media Flow Replication by network |R10| p. 158

6a.10.1 Replicating media in network from Controller UE to another UE belonging to same IMS subscription p. 158

The information flow in Figure 6a.10.1-1 illustrates a scenario in which the Controller UE of a Collaborative Session requests that the network replicate a media flow towards another UE that belongs to the same subscription. In this scenario, UE-2 is currently not involved in the Collaborative Session until after Media-A is replicated towards it.

Reproduction of 3GPP TS 23.237, Fig. 6a.10.1-1: Replicating media in network from Controller UE to another UE belonging to same IMS subscription

Figure 6a.10.1-1: Replicating media in network from Controller UE to another UE belonging to same IMS subscription

There is Media-A between Controller UE-1 and remote party.

Step 1.

Controller UE-1 sends a request towards SCC AS-1 to replicate Media-A to UE-2. The session setup request includes enough information for the network to:

identify that the media flow to be replicated is Media-A;
identify that the source of the media flow to be replicated is the remote party;
identify that the target of the media flow to be replicated is Controllee 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 allocates media resource in MRF for the Media-A to be replicated.

Step 5.

SCC AS-1 sends a request to establish an Access Leg at UE-2 for Media-A.

Step 6.

SCC AS-1 updates the Access Leg on Controller UE-1 for the replicated media flow (Media-A) with MRF.

Step 7.

SCC AS-1 updates the Remote Leg to communicate Media-A with MRF.

After the above operation, Media-A is established between Controller UE-1 and MRF, from MRF to Controllee UE-2, and between remote party and MRF.

6a.10.2 Replicating media in network from Controller UE to another UE belonging to different IMS subscription p. 159

The information flow in Figure 6a.10.2-1 illustrates a scenario in which a Collaborative Session is established in the context of an ongoing IMS session and as a result of UE-1 requesting to replicate media to another UE. The Controller UE requests that the network replicate a media flow towards a UE that belongs to a different subscription.

Reproduction of 3GPP TS 23.237, Fig. 6a.10.2-1: Replicating media in network from Controller UE to another UE belonging to different IMS subscription

Figure 6a.10.2-1: Replicating media in network from Controller UE to another UE belonging to different IMS subscription

There is Media-A between UE-1 and remote party.

Step 1.

UE-1 sends a request towards SCC AS-1 to replicate Media-A to UE-2. The Collaborative Session request includes enough information for the network to:

identify that the media flow to be replicated is Media-A;
identify that the source of the media flow to be replicated is the remote party;
identify that the target of the media flow to be replicated 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 allocates media resource for the replicated Media-A in MRF.

Step 5.

SCC AS-1 sends a request towards UE-2 to set up the replicated Media-A between UE-2 and the MRF. 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 replicated media flow is Media-A;
identify the media resource information of SCC AS-1;
identify that the target of the replicated media flow is UE-2.

Step 5a.

S-CSCF-1 routes the request towards UE-2.

Step 6.

If UE-2 is an IUT subscriber, the request is routed via SCC AS-2. 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 toward 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 7.

S-CSCF-2 forwards the Session Setup request towards UE-2.

Step 8.

UE-2 sends the Session Setup response towards SCC AS-1.

Step 9 - 10.

S-CSCF-2 routes the response back toward SCC AS-1 via SCC AS-2 if UE-2 is an IUT subscriber.

Step 11.

S-CSCF-1 forwards the response to SCC AS-1.

Step 12.

SCC AS-1 updates Access Leg in UE-1, finishes Access Leg establishment in UE-2, and updates Remote Leg to communicate Media-A with MRF.

After the above operation, a Collaborative Session is established where UE-1 is the Controller UE and UE-2 is a Controllee UE. Media-A is established between Controller UE-1 and MRF, from MRF to Controllee UE-2 and MRF, and between remote party and MRF.

6a.10.3 Replicating media in network from Controller UE to another UE belonging to same IMS subscription - pull mode p. 161

The information flow in Figure 6a.10.3-1 illustrates a Collaborative Session scenario in which a UE not participating in the session requests that the network replicate towards itself a media flow that pertains to a UE belonging to the same subscription. It is assumed that, prior to the scenario, UE-2 has discovered that there is an ongoing session between UE-1 and the remote party and that UE-1 is capable of supporting IUT related media procedures. If UE-1 does not support IUT related media procedures, SCC AS-1 or UE-1 will return an error. In the illustrated scenario, UE-2 is currently not involved in the Collaborative Session until after Media-A is replicated towards it.

Reproduction of 3GPP TS 23.237, Fig. 6a.10.3-1: Replicating media in network from Controller UE to another UE belonging to same IMS subscription - pull mode

Figure 6a.10.3-1: Replicating media in network from Controller UE to another UE belonging to same IMS subscription - pull mode

There is Media-A between Controller UE-1 and remote party.

Step 1.

UE-2 sends a request towards SCC AS-1 to replicate Media-A of an existing session to UE-2. The session setup request includes enough information for the network to:

identify the session that contains the media flow to be replicated;
identify that the media flow to be replicated is Media-A;
identify that the source of the media flow to be replicated is the remote party;
identify that the target of the replicated 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-2 as specified in clause 6a.12.

Step 4.

SCC AS-1 allocates media resource for the replicated Media-A.

Step 5.

SCC AS-1 sends response towards UE-2.

Step 6.

S-CSCF-1 forwards the response to UE-2.

Step 7.

SCC AS-1 updates the Access Leg on Controller UE-1 for the replicated media flow (Media-A) with MRF.

Step 8.

SCC AS-1 updates the Remote Leg to communicate Media-A with MRF.

After the above operation, Media-A is established between Controller UE-1 and MRF, from MRF to Controllee UE-2 and MRF, and between remote party and MRF.

6a.10.4 Replicating media in network from Controller UE to another UE belonging to different IMS subscription - pull mode p. 163

The information flow in Figure 6a.10.4-1 illustrates a Collaborative Session scenario in which a UE not participating in the session requests that the network replicate towards itself a media flow that pertains to a UE belonging to different subscription (User-1). It is assumed that User-1 is an IUT subscriber. It is also assumed that, prior to the scenario, the user that requests the media replication (User-2) has discovered that there is an ongoing session between UE-1 and the remote party. If UE-1 does not support IUT related media procedures or the user is not an IUT subscriber, SCC AS-1 or UE-1 will return an error. In the illustrated scenario, UE-2 is currently not involved in the Collaborative Session until after Media-A is replicated towards it.

Reproduction of 3GPP TS 23.237, Fig. 6a.10.4-1: Replicating media in network from Controller UE to another UE belonging to different IMS subscription - pull mode

Figure 6a.10.4-1: Replicating media in network from Controller UE to another UE belonging to different IMS subscription - pull mode

There is Media-A between Controller UE-1 and remote party.

Step 1.

UE-2 sends a request towards UE-1 to replicate Media-A to UE-2. The request includes enough information for the network to:

identify the session that contains the media flow to be replicated;
identify that the media flow to be replicated is Media-A;
identify that the source of the media flow to be replicated is the remote party;
identify that the target of the replicated media flow is UE-2.

Step 2.

S-CSCF-2 forwards the request to SCC AS-2.

Step 3.

SCC AS-2 authorizes the request from UE-2 as specified in clause 6a.12.

Step 4.

SCC AS-2 sends a request towards UE-1 to replicate Media-A from the remote party to UE-2. The request includes enough information for the network to:

identify the session that contains the media flow to be replicated;
identify the source of the request as UE-2;
identify that the replicated media flow is Media-A;
identify that the source of the media flow to be replicated is the remote party;
identify that the target of the replicated media flow is UE-2.

Step 4a.

S-CSCF-2 forwards the request towards UE-1.

Step 4b.

S-CSCF-1 forwards the request to SCC AS-1.

Step 5.

SCC AS-1 or UE-1 authorizes the request from UE-2.

Step 6.

SCC AS-1 allocates media resource for the replicated Media-A.

Step 7.

SCC AS-1 updates Access Leg in UE-1, finishes Access Leg establishment in UE-2, and updates Remote Leg to communicate Media-A with MRF.

After the above operation, Media-A is established between Controller UE-1 and MRF, from MRF to Controllee UE-2 and MRF, and between remote party and MRF.