12 Supplementary service invocation for ICS
24.2923GPPIP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS)Release 17Stage 3TS
12.1 Supplementary service invocation for an ICS UE with IMS sessions using CS bearer
12.1.1 Overview
When the CS bearer is used for the media of the IMS Multimedia Telephony service and service control is provided using Gm, see 3GPP TS 22.173 [2], the procedures specified in subclause 12.1 apply.
3GPP TS 24.294 [11B] specifies the supplementary service procedures for service control using I1.
12.1.2 Use of Gm reference point
12.1.2.1 Line ID Services (OIP, OIR, TIP, TIR)
The procedures as defined in 3GPP TS 24.607 [14] and 3GPP TS 24.608 [15] apply with the addition of the SCC AS combining the description of the CS bearer with the service control signalling communicated over the Gm reference point as specified in subclause 7.4.2.
12.1.2.2 Communication Diversion Services
The procedures as defined in 3GPP TS 24.604 [12] apply with the addition of the SCC AS combining the description of the CS bearer with the service control signalling communicated over the Gm reference point as specified in subclause 7.4.2.
12.1.2.3 Communication Barring
The procedures as defined in 3GPP TS 24.611 [17] apply with the addition of the SCC AS combining the description of the CS bearer with the service control signalling communicated over the Gm reference point as specified in subclause 7.4.2.
12.1.2.4 Communication Hold/Resume
Invocation of Communication HOLD service for ICS UE using Gm reference point shall be as described in 3GPP TS 24.610 [16].
Upon receiving the re-INVITE request describe in subclause 4.5.2.1 of 3GPP TS 24.610 [16], which indicates that media streams shall be held, the SCC AS shall:
1) generate a new SDP offer that contains "inactive" attribute for the media streams that shall be put on held;
2) send the SDP offer in an UPDATE (or re-INVITE) request towards the MGCF or the MSC server enhanced for ICS in order to inactive RTP media;
Upon receiving the re-INVITE request describe in subclause 4.5.2.1 of 3GPP TS 24.610 [16], which indicates that media streams shall be resumed, the SCC AS shall:
1) send a re-INVITE request without SDP towards the MGCF or the MSC server enhanced for ICS.
2) after receiving a 200 (OK) response with SDP offer from the MGCF or the MSC server enhanced for ICS, send another re-INVITE request with the SDP offer to the held UE.
3) after receiving a 200 (OK) response with SDP answer from the held UE, send an ACK request with the SDP answer to the MGCF or the MSC server enhanced for ICS.
12.1.2.5 Explicit Communication Transfer
Invocation of ECT service for ICS UE using Gm reference point shall be as described in 3GPP TS 24.629 [19] for a transferor UE, transferee UE, and transfer target UE.
In the case of ICS UE as transferee, upon receiving an INVITE request from the transferee, the SCC AS shall:
1) send a re-INVITE request without SDP to MGCF;
2) after receiving a 200 (OK) response with SDP offer from the MGCF;
3) initiate an INVITE request with the SDP offer to the transfer target;
4) if, within a specific time, a response with an SDP answer from the transfer target is not received, send an ACK request to the MGCF with an SDP answer and repeat steps 1) and 2). The SDP answer shall contain the same media types as the SDP offer received from the MGCF;
5) after receiving a response with SDP answer from the transfer target, send an ACK request with the SDP answer to the MGCF.
12.1.2.6 Conferencing
Invocation of conferencing service for ICS UE using Gm reference point shall be as described in 3GPP TS 24.147 [8].
12.1.2.7 Communication Waiting
The procedures defined in 3GPP TS 24.615 [18] apply for invocation of Communication Waiting. The SCC AS shall update the session characteristics upon the existing session being put on hold or released, according to the procedures defined in subclauses 12.1.2.4 or 11.4.2, respectively.
In the case that a CS bearer shall be established for the waiting session, procedures described in subclause 10.4 shall be applied to the session.
12.1.3 Void
12.1.4 When use of Gm reference point is not possible due to VPLMN limitations
12.1.4.1 When attached to an MSC Server enhanced for ICS
Procedures specified in subclause 12.2 Supplementary service invocation for an ICS UE with IMS sessions using CS bearer apply.
12.1.4.2 When attached to an MSC Server not enhanced for ICS
Procedures specified in subclause 12.3 Supplementary service invocation for non ICS UE when attached to an MSC Server not enhanced for ICS apply.
12.2 Supplementary service invocation using the MSC Server enhanced for ICS
12.2.1 Line ID Services (OIP, OIR, TIP, TIR)
Invocation of line ID services at the MSC Server enhanced for ICS shall be as described in 3GPP TS 24.607 [14] and 3GPP TS 24.608 [15] for an originating UE and a terminating UE with the following exception:
– the MSC Server enhanced for ICS shall also apply the interworking procedures as specified in 3GPP TS 29.292 [24] for line ID services.
12.2.2 Communication Diversion (CDIV) Services
12.2.2.1 General
The following exception applies to the invocation of all CDIV services at the MSC Server enhanced for ICS acting as a diverting UA on behalf of the UE:
– the MSC Server enhanced for ICS shall not support the user subscription option of "served user receives indication that a communication has been forwarded (indication of communication diversion to the diverting user)".
12.2.2.2 Communication Forwarding Unconditional (CFU)
Invocation of CFU at the MSC Server enhanced for ICS shall be as described in 3GPP TS 24.604 [12] for an originating UA, diverted to UA and diverting UA.
12.2.2.3 Communication Forwarding Busy (CFB)
Invocation of CFB at the MSC Server enhanced for ICS shall be as described in 3GPP TS 24.604 [12] for an originating UA, diverted to UA and diverting UA with the following exception:
– for user determined user busy, invocation of CFB at the MSC Server enhanced for ICS acting as a diverting UA shall also apply the interworking procedures as specified in 3GPP TS 29.292 [24] for CFB.
12.2.2.4 Communication Forwarding No Reply (CFNR)
Invocation of CFNR at the MSC Server enhanced for ICS shall be as described in 3GPP TS 24.604 [12] for an originating UA, diverted to UA and diverting UA.
12.2.2.5 Communication Forwarding on Not Logged-in (CFNL)
Invocation of CFNL at the MSC Server enhanced for ICS shall be as described in 3GPP TS 24.604 [12] for an originating UA, diverted to UA and diverting UA.
12.2.2.6 Communication Deflection (CD)
Invocation of CD at the MSC Server enhanced for ICS shall be as described in 3GPP TS 24.604 [12] for an originating UA, diverted to UA and diverting UA with the following exception:
– invocation of CD at the MSC Server enhanced for ICS acting as a diverting UA shall also apply the interworking procedures as specified in 3GPP TS 29.292 [24] for CD.
12.2.2.7 Communication Forwarding on Subscriber Not Reachable (CFNRc)
Invocation of CFNRc at the MSC Server enhanced for ICS shall be as described in 3GPP TS 24.604 [12] for an originating UA, diverted to UA and diverting UA with the following exception:
– invocation of CFNRc at the MSC Server enhanced for ICS acting as a diverting UA shall also apply the interworking procedures as specified in 3GPP TS 29.292 [24] for CFNRc.
12.2.2.8 Void
12.2.2.9 Diversion notifications to originating users
Diversion notifications to originating users shall be supported at the MSC Server enhanced for ICS as described in 3GPP TS 29.292 [24].
12.2.3 Communication Barring (CB)
Invocation of CB at the MSC Server enhanced for ICS shall be as described in 3GPP TS 24.611 [17] for an originating and destination UE with the following exception:
– the MSC Server enhanced for ICS shall also apply interworking procedures as specified in 3GPP TS 29.292 [24] for CB.
12.2.4 Communication Hold/Resume
Invocation of Hold and Resume at the MSC Server enhanced for ICS shall be as described in 3GPP TS 24.610 [16] for an invoking and held UE with the following exception:
– the MSC Server enhanced for ICS shall also apply interworking procedures as specified in 3GPP TS 29.292 [24] for Hold and Resume.
12.2.5 Explicit Communication Transfer (ECT)
Invocation of ECT at the MSC Server enhanced for ICS shall be as described in 3GPP TS 24.629 [19] for a transferor UE, transferee UE and transfer target UE with the following exceptions:
– the MSC Server enhanced for ICS shall support the transferor role only when the MSC Server enhanced for ICS has a consultation communication with the transfer target (consultative transfer). The MSC Server enhanced for ICS shall not support the transferor role for blind or assured transfer.
– the MSC Server enhanced for ICS shall also apply interworking procedures as specified in 3GPP TS 29.292 [24] for ECT.
12.2.6 Conferencing
Invocation of Conferencing at the MSC server enhanced for ICS shall be as described in 3GPP TS 24.605 [13] for an originating UE and destination UE with the following exceptions:
– a Conference Factory URI shall be derived as specified in 3GPP TS 23.003 [4];
– conference creation by the MSC Server enhanced for ICS shall be as described in 3GPP TS 24.147 [8] subclause 5.3.1.3.3;
– the MSC server enhanced for ICS shall invite other users to the conference using one of the REFER method procedures as specified in 3GPP TS 24.147 [8] subclause 5.3.1.5.2 and subclause 5.3.1.5.3;
– if the MSC server enhanced for ICS invites other users to the conference using the procedures specified in 3GPP TS 24.147 [8] subclause 5.3.1.5.3, the MSC server shall send the REFER request outside a dialog and add a Target-Dialog header field to the REFER request populated with the dialog identifiers of the ongoing dialog towards the conference server;
– the MSC server enhanced for ICS may subscribe to the conference event package, as described in 3GPP TS 24.147 [7] subclause 5.3.1.2; and
– the MSC server enhanced for ICS shall also apply the interworking procedures as specified in 3GPP TS 29.292 [24] for Conferencing.
12.2.7 Communication Waiting (CW)
Invocation of Communication Waiting at the MSC Server enhanced for ICS shall be as described in 3GPP TS 24.615 [18] with the following exception:
– the MSC Server enhanced for ICS shall also apply interworking procedures as specified in 3GPP TS 29.292 [24] for Communication Waiting.
12.2.8 Communication completion services (CCBS/CCNR/CCNL)
Invocation of CCBS, CCNR and CCNL at the MSC server enhanced for ICS shall be as described in 3GPP TS 24.642 [47] for an originating and destination UE with the following exception:
– the MSC Server enhanced for ICS shall also apply interworking procedures as specified in 3GPP TS 29.292 [24] for CCBS, CCNR and CCNL.
12.3 Supplementary service invocation for non ICS UE when attached to an MSC Server not enhanced for ICS
12.3.1 Line ID Services (OIP, OIR, TIP, TIR)
The service control for the Line ID services may be provided by the CS domain if they are provisioned in the CS domain.
12.3.2 Communication Diversion services
12.3.2.1 Communication Diversion services; CFU, CFNL
The procedures as defined in 3GPP TS 24.604 [12] apply with the addition of the SCC AS presenting the SIP UA behaviour toward IM CN subsystem on behalf of the non ICS UE.
NOTE: If the UE is not registered in IMS but attached to an MSC server not enhanced for ICS, invoking CFNL would divert all calls.
12.3.2.2 Communication Diversion services: CFNR, CFB, CFNRc
The procedures as defined in 3GPP TS 24.604 [12] apply with the addition of the SCC AS presenting the SIP UA behaviour toward IM CN subsystem on behalf of the non ICS UE.
12.3.2.3 Communication Diversion services; Communication Deflection
The service control for the Call Deflection service may be provided by the CS domain if it is provisioned in the CS domain.
12.3.3 Communication Barring
The procedures as defined in 3GPP TS 24.611 [17] apply with the addition of the SCC AS presenting the SIP UA behaviour toward IM CN subsystem on behalf of the non ICS UE.
12.3.4 Communication Hold/Resume
The service control for the Call Hold and Retrieve services may be provided by the CS domain if they are provisioned in the CS domain.
12.3.5 Explicit Communication Transfer
The service control for the Explicit Call Transfer services may be provided by the CS domain if they are provisioned in the CS domain.
12.3.6 Conferencing
The service control for the Conferencing (Multiparty) services may be provided by the CS domain if they are provisioned in the CS domain.
12.3.7 User configuration of supplementary services
There are no special procedures for user configuration of supplementary services.
12.3.8 Communication completion services
The procedures as defined in 3GPP TS 24.642 [47] apply for the AS. At the MSC server no special interworking is required. As the MGCF normally does not support the REFER method, 3pcc procedures can be used when the originating user is in the CS domain.