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.6 Inter-UE Transfer without establishing a Collaborative Session  6a.6.1 Inter-UE Transfer initiated by the source UE  6a.6.2 Inter-UE Transfer initiated by the target UE 
...

 

6a.6  Inter-UE Transfer without establishing a Collaborative Session  p. 142

6a.6.1  Inter-UE Transfer initiated by the source UE |R10|  p. 142

UE-1 and UE-2 are under the same user subscription. UE-1 is involved in IMS session with remote party. The information flow in Figure 6a.6.1-1 shows transfer of the session from UE-1 to UE-2. Since the entire session is transferred simultaneously, the roles of the Controller UE and Controllee UE are not applicable.
Reproduction of 3GPP TS 23.237, Fig. 6a.6.1-1: Inter-UE transfer without establishing Collaborative Session - initiated by the source UE
Figure 6a.6.1-1: Inter-UE transfer without establishing Collaborative Session - initiated by the source UE
Up
Step 1.
UE-1 sends IUT media and service control transfer request to the SCC AS to transfer the session that includes Media-A from UE-1 to UE-2. The IUT media and service control transfer request shall include enough information for the network to:
  • identify the transferred session;
  • identify that the target of the transferred session is UE-2;
  • identify the access leg of UE-1 to be transferred to UE-2.
Step 2.
If the SCC AS does not have the list of Public User Identities that share the service profile with the Public User Identity used by UE-1 for the Collaborative Session, the SCC AS retrieves this information. If the Collaborative Session Control transfer request indicates that UE-2 has the same Public User Identity (but different public GRUU) as UE-1, this step is skipped.
Step 3.
The SCC AS ensures that the Public User Identity used by UE-2 shares the service profile with the Public User Identity used by UE-1 for the Collaborative Session. The SCC AS performs authorization as specified in clause 6a.12, then initiates the media session setup procedure with UE-2 for the Media-A, and updates the Remote Party.
Step 4.
The SCC AS releases the session with UE-1.
When the above transfer is completed the SCC AS retains the service state (e.g. media flows status) of UE-2, and the UE-2 has the control of the IMS session.
Up

6a.6.2  Inter-UE Transfer initiated by the target UE |R10|  p. 144

UE-1 and UE-2 are under the same IMS subscription. UE-1 is involved in IMS session with remote party. Figure 6a.6.2-1 shows session transfer from UE-1 to UE-2 requested by UE-2. Since all the media flow(s) are transferred from UE-1 to UE-2 simultaneously, the roles of the Controller UE and the Controllee UE are not applicable.
Reproduction of 3GPP TS 23.237, Fig. 6a.6.2-1: Inter UE Transfer initiated by UE not participating in the session - no Collaborative Session established
Figure 6a.6.2-1: Inter UE Transfer initiated by UE not participating in the session - no Collaborative Session established
Up
Step 1.
UE-2 obtains information about the existing sessions and their media flows.
Step 2.
UE-2 sends IUT media and service control transfer request. The request shall include enough information for the network to:
  • identify the transferred session;
  • identify that the target of the transferred session is UE-2;
  • identify the access leg of UE-1 to be transferred to UE-2.
Step 3.
If the SCC AS does not have the list of Public User Identities that share the service profile with the Public User Identity used by UE-1 for the Collaborative Session, the SCC AS retrieves this information. If the Collaborative Session Control transfer request indicates that UE-2 has the same Public User Identity (but different public GRUU) as UE-1, this step is skipped.
Step 4.
The SCC AS ensures that the Public User Identity used by UE-1 shares the service profile with the Public User Identity used by UE-2 for the Collaborative Session. The SCC AS performs authorization as specified in clause 6a.12; in particular, the SCC AS requests the UE-1 to authorize the pull request or the SCC AS authorizes the request on behalf of UE-1 (e.g. pre-configured). The SCC AS will also authorize that the target UE is of the same subscription. If the request is authorized, SCC AS continues in accordance with step 2 of clause 6a.6.1, i.e. SCC AS establishes a session with UE-2 for the Media-A, removes Media-A from UE-1, and updates Remote Leg using the Remote Leg Update procedure.
Step 5.
The SCC AS sends IUT media and service control transfer response to UE-2.
Up

Up   Top   ToC