6.5 Execution of supplementary services

23.2373GPPIP Multimedia Subsystem (IMS) Service ContinuityRelease 17Stage 2TS

6.5.1 General

This clause describes the SCC AS and UE procedures for execution of supplementary service as described in TS 22.173 [15].

The related interactions apply to scenarios when the media components for the UE are split into multiple Access Legs due to IMS Service Continuity procedures. The Remote Leg is presented with one session including all the media components.

For Access Leg where CS media is used, the interaction described in the following clauses still applies and the service request should be sent via PS Access Leg. The operations on the CS media flows shall be handled based on the service request and shall follow the procedures as described in TS 23.292 [5].

When service invocation fails on one Access Leg, the UE and the SCC AS may retry on a different Access Leg.

6.5.2 Originating Identification Presentation (OIP)

The OIP service is not impacted.

6.5.3 Originating Identification Restriction (OIR)

The OIR service is not impacted.

6.5.4 Terminating Identification Presentation (TIP)

The TIP service is not impacted.

6.5.5 Terminating Identification Restriction (TIR)

The TIR service is not impacted.

6.5.6 Communication Diversion (CDIV)

Upon receiving an incoming session split across multiple Access Legs, if an UE wants to invoke the CDIV service, the UE may use any of the Access Legs to invoke the CDIV service following the procedures defined in TS 24.604 [21].

When the SCC AS splits an incoming session into multiple Access Legs and receives a CDIV request from the UE on any of the Access Legs, the SCC AS shall terminate the other Access Leg(s) and shall invoke the CDIV service following the procedures defined in TS 24.604 [21].

6.5.7 Communication Hold (HOLD)

If the UE wants to invoke the HOLD service on one or more media component(s) and the UE has multiple Access Legs, the UE shall invoke the HOLD procedures, as defined in TS 24.610 [16] on all the Access Legs which contain the affected media component(s). The SCC AS shall update the remote Access Leg using the procedures defined in TS 24.610 [16].

If the remote end initiates the HOLD service on one or more media component(s) and the UE has multiple Access Legs, the SCC AS shall forward the HOLD request on all the Access Legs which contain the affected media component(s).

6.5.8 Communication Barring (CB)

The CB service is not impacted.

6.5.9 Message Waiting Indication (MWI)

The MWI service is not impacted.

6.5.10 Conference (CONF)

When the UE wants to invoke the CONF services and has multiple Access Legs, the UE may send any CONF related requests, e.g. subscribe request for conference package or refer request to the conference, as defined in TS 24.605 [17], on any of the Access Legs.

When the UE has multiple Access Legs and the remote end sends a request for the CONF service to replace an existing session within the same dialog, the SCC AS may deliver the request for CONF service on any of the Access Legs.

When the UE has multiple Access Legs and receives a request on one of the Access Legs for a CONF service to replace an existing session, the UE shall follow the procedures specified in TS 24.605 [17] to establish a new session to the conference focus.

When the UE has multiple Access Legs and receives a request for a CONF service to replace an existing session outside the dialog, the UE shall follow the procedures specified in TS 24.605 [17] to establish a new session to the conference focus.

6.5.11 Explicit Communication Transfer (ECT)

When the UE acts as the transferor UE and has multiple Access Legs, the UE may send the request for ECT service, as specified in TS 24.629 [18], on any of the Access Legs.

When the UE acts as the transferee UE and has multiple Access Legs, the SCC AS may deliver the request for ECT service on any of the Access Legs.

When the UE has multiple Access Legs and receives an ECT request on one of the Access Legs, the UE shall follow the procedures specified in TS 24.629 [18] to establish a new session to the Transfer Target.

6.5.12 Advice of Charge (AOC)

When the AOC service specified in TS 24.647 [19] is active and the UE has multiple Access Legs, the SCC AS may deliver charging information during the communication to the UE over any of the Access Legs.

6.5.13 Closed User Groups (CUG)

The CUG service is not impacted.

6.5.14 Three-Party (3PTY)

The 3PTY service in TS 24.605 [17] is considered as a special case of CONF service and the interaction with Session Transfer is the same as that specified in clause 6.5.10 for CONF service.

6.5.15 Flexible Alerting (FA)

The FA service is not impacted.

6.5.16 Communication Waiting (CW)

Upon receiving an incoming session split across multiple Access Legs, if an UE wants to invoke the CW service, the UE may use any of the Access Legs to invoke the CW service following the procedures defined in TS 24.615 [22].

When the SCC AS splits an incoming session into multiple Access Legs and receives a CW request from the UE on any of the Access Legs, the SCC AS shall invoke the CW service following the procedures defined in TS 24.615 [22].

6.5.17 Completion of Communications to Busy Subscriber (CCBS)/Completion of Communications by No Reply (CCNR)

The CCBS/CCNR service is not impacted.

6.5.18 Customized Alerting Tones (CAT)

The CAT service is not impacted.

6.5.19 Malicious Communication IDentification (MCID)

When invoking the MCID service in temporary subscription mode and there are multiple active Access Legs for the session, the UE may send the re-INVITE request for invoking MCID service as defined in TS 24.616 [20] on any of the Access Legs.

6.5.20 Reverse Charging

The Reverse Charging service is not specified.

6.5.21 Personal Network Management (PNM)

The PNM service is not specified.

6.5.22 Customized Ringing Signal (CRS)

The CRS service is not specified.