When initiating Inter-UE Transfer procedures, the UE may use the following information:
-
other UEs belonging to the same IMS subscription;
-
the availability (e.g. online, offline etc) of the UEs;
-
the capabilities (e.g. support of audio/video formats, Controller UE capability, etc) of the UEs.
Determination of UEs belonging to the same IMS subscription is based on either or both of static list stored in the UE and based on IMS registration. When based on IMS registration, the UE gets notified when other UEs under the same Implicit Registration Set become available and their capabilities and contact details. The static list, which contains a list of eligible UEs for Inter-UE Transfer, can be created manually by the user.
The availability and capabilities of the target UE(s) can be determined by the information flow described in the subsequent clause.
Step 1.
UE-2 is IMS registered following the procedures defined in
TS 23.228.
Step 2.
UE-1 performs IMS registration following the procedures defined in
TS 23.228.
Step 3 ~ 4.
UE-1 is interested to discover the status and capabilities of other devices under the same subscription. It subscribes to an event package (e.g., reg-event, presence) for registration information and the capabilities information.
Step 5 ~ 6.
The IMS CN subsystem or presence AS notifies UE-1 of other devices (e.g. UE-2) status and, if available, capabilities information.
Step 7.
UE-3 performs IMS registration.
Step 8 ~ 9.
The IMS CN subsystem notifies UE-1 of UE-3's availability and, if available, capabilities information.
Optionally, if sufficient UE capabilities information is not included in step 8, then the following steps can be performed:
Step 10 ~ 13.
Among all the available devices, UE 1 is interested in performing Inter-UE transfer to UE-3. UE-1 performs capability query towards UE-3.
In order to solicit the IUT of media flows or control of an ongoing session from other UE(s) under the same or different subscriptions of the same operator, it shall be possible for a UE capable of IUT to discover ongoing session information on other UE(s) as follows:
-
Session information for the other UE(s), including session identifier, source UE identifier (e.g. GRUU or IMPU), remote end identifier, identity of the Controller UE for the related Collaborative Session;
-
Media flow information for the ongoing session(s) in other UE(s), including: type (voice, video, etc.), status (held, active, etc.), media flow identifier;
-
Service Identifier for the service the session is related to.
The UE may use the above information for IUT in addition to the availability and capabilities of other UE(s) as specified in
clause 6a.8.1.
The SCC AS which serves target UE(s) of session discovery shall filter information on some or all of the sessions or media flows composing the session on the target UE(s) based on user service configuration or operator policy before providing ongoing session information to the UE which has requested session discovery.
The Figure below shows an information flow of UE-1 requesting ongoing session information for the other UEs, assuming that UE-1, UE-2 and UE-3 belong to the same IMS subscription and there is a session with Media Flow-A between UE-2 and the remote party and another session with Media Flow-B between UE-3 and the remote party.
Step 1.
UE-1 sends the SCC AS a Session Discovery request for ongoing session information for the UEs belonging to the same IMS subscription. The Session Discovery request indicates the information requested to be provided in the response.
Step 2.
The SCC AS retrieves the requested information for all ongoing sessions for the user's UEs.
Step 3.
The SCC AS, if required, authorizes that UE-1 is allowed to receive the requested information, and sends the UE-1 a Session Discovery response containing the requested session related information for UE-2 and UE-3. The SCC AS performs filtering as specified in
clause 6a.8.3.1 before sending a Session Discovery response to the UE-1.
The Figure below shows an information flow of UE-1 requesting ongoing session information for the other UEs, assuming that UE-1 belongs to User-1 while UE-2 and UE-3 belong to User-2. It is also assumed that there is a session with Media Flow-A between UE-2 and the remote party, and another session with Media Flow-B between UE-3 and the remote party.
Step 1.
UE-1 sends SCC AS-1 a Session Discovery request for ongoing session information for User-2's UEs. The Session Discovery request indicates the information requested to be provided in the response.
Step 2.
SCC AS-1 sends a Session Information request for ongoing session information for User-2's UEs to S-CSCF-2 which serves User-2.
Step 3.
S-CSCF-2 forwards the Session Information request to SCC AS-2 which serves User-2.
Step 4.
SCC AS-2, if required, authorizes that UE-1 is allowed to receive ongoing session information for User-2's UEs, and sends a Session Information response containing ongoing session information for UE-2 and UE-3. The SCC AS-2 performs filtering as specified in
clause 6a.8.3.1 before sending a Session Information response.
Step 5.
S-CSCF-2 forwards the Session Information response to SCC AS-1.
Step 6.
SCC AS-1 sends UE-1 a Session Discovery response containing ongoing session information for UE-2 and UE-3.