Content for  TS 23.237  Word version:  18.0.0

Even though the media components for the Collaborative Session are split onto multiple Access Legs of different UEs, the remote end is presented with one session including all the media components. This clause describes the SCC AS and IUT UE procedures for handling supplementary services as described in TS 22.173. Whether or not the UEs involved in a Collaborative Session pertain to multiple IMS subscriptions, the Controllee UEs can be under a different service profile than the Controller UE. The service profile of the Controller UE shall determine the set of Application Servers and services that are invoked for the overall session with the remote end. For a Controllee UE's Access Leg where CS media is used, the interaction described in the following clauses still apply. However, the operations on the CS media follow the procedures as described in TS 23.292. With respect to identification presentation services (e.g. Originating Identification Presentation), the identifying information provided to the remote end is that of the Controller UE.

The OIP service is not impacted by IUT.

The OIR service is not impacted by IUT.

The TIP service is not impacted by IUT.

The TIR service is not impacted by IUT.

The CDIV service is not impacted by IUT.

If the Controller UE wants to invoke the HOLD service on one or more media component(s), the Controller UE shall invoke the HOLD procedures, as defined in TS 24.610. The Hosting SCC AS shall act on the HOLD requests by updating all the Controllee UEs whose media status are changed and shall update the Remote Leg using the procedures defined in TS 24.610. If a Controllee UE wants to invoke the HOLD service on one or more media component(s) that it hosts, the request to do so must be authorized by the Controller UE (or by the network on behalf of the Controller UE). If the request is authorized, the Controllee UE shall invoke the HOLD procedures, as defined in TS 24.610.

The CB service is not impacted by IUT.

The MWI service is not impacted by IUT.

Only the Controller UE can invoke the CONF service for the Collaborative Session and it shall follow the procedures as defined in TS 24.605 for any CONF service related operations. The SCC AS associated with a Controllee UE shall reject a request from the Controllee UE to invoke the CONF service. When the remote end sends a request for the CONF service to replace an existing session which is locally a Collaborative Session, the SCC AS shall deliver the request for CONF service to the Controller UE, which then sets up a new session following the procedures defined in TS 24.605. If the user intends to invoke the CONF service for an ongoing Collaborative Session, the Controller UE shall establish a new Collaborative Session towards the conferencing AS using the procedure of Establish Collaborative Session at originating IMS session setup as specified in clause 6a.2.3, while the existing Access Legs between the SCC AS and the Controllee UE(s) can be reused (i.e. updated to be bound to the new Collaborative Session between the Controller UE and the conferencing AS).

Only the Controller UE can invoke the ECT service on behalf of the Collaborative Session and it shall follow the procedures as specified in TS 24.629. Upon receiving notification that ECT has been performed successfully, the Controller UE shall terminate the previous active session with the transferee UE by terminating all related media control sessions on the Controllee UEs. The SCC AS associated with a Controllee UE shall reject a request from the Controllee UE to invoke the ECT service. Upon receiving an ECT transfer request from the remote end to transfer the Collaborative Session, the SCC AS shall deliver the request to the Controller UE. Upon receiving an ECT transfer request to transfer the Collaborative Session, the Controller UE shall establish a new session towards the transfer target following the procedures defined in TS 24.629. If the communication to be transferred is a Collaborative Session (i.e. the transferee intends to use the Collaborative Session to communicate with the transfer target), the Controller UE shall establish a new Collaborative Session towards the transfer target using the procedure of Establish Collaborative Session at originating IMS session setup as specified in clause 6a.2.3, while the existing Access Legs between the SCC AS and the Controllee UE(s) can be reused (i.e. updated to be bound to the new Collaborative Session between the Controller UE and the transfer target).

When the AOC service specified in TS 24.647 is active, the SCC AS shall deliver charging information during the communication to the Controller UE.

The CUG service is not impacted by IUT.

The 3PTY service in TS 24.605 is considered as a special case of CONF service and the interaction with IUT is the same as that specified in clause 4.8.10 for CONF service.

The FA service is not impacted by IUT.

The CW service is not impacted.

The CCBS/CCNR service is not impacted.

For Collaborative Sessions established concurrently with terminating IMS session setup, the CAT provided by the network (under the control of the SCC AS associated with the Controller UE) to the remote party is the CAT associated with the Controller UE.

The MCID service is not impacted by IUT.

The Reverse Charging service is not impacted by IUT.

The PNM service is not impacted by IUT.

For Collaborative Sessions established concurrently with terminating IMS session setup, the Customized Ringing Signal (CRS) provided to the Controller UE is the CRS associated with the remote party. For Collaborative Sessions established concurrently with originating IMS session setup, the CRS provided to the remote party is the CRS associated with the Controller UE.