7.8 Interaction with Supplementary Services
23.0973GPPMultiple Subscriber Profile (MSP) Phase 2Release 17Stage 2TS
7.8.1 Line Identification services
7.8.1.1 CLIP
No interaction.
7.8.1.2 CLIR
CLIR can be provisioned per subscriber or per profile.
If CLIR is provisioned per subscriber and CLIR is active, it will be active for all profiles. Data for the CLIR Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. CLIR will function as specified in 3G TS 23.081 and will not distinguish between MSP and non-MSP subscribers.
If CLIR is provisioned per profile then the CLIR_flag shall be set in the HLR (see clause 6.8: CLIR_flag) and the CLIR subscription information for the default profile shall be stored in the HLR in the usual manner. For an MO call, if the CLIR subscription information for the Calling profile indicates that the CLI shall be restricted, the gsmSCF shall set the Calling Party Presentation Indicator to Presentation Restricted in the SII2 parameter.
7.8.1.3 COLP
No interaction.
7.8.1.4 COLR
No interaction.
7.8.2 Call Hold (HOLD)
Call Hold can be provisioned per subscriber or per profile.
If Call Hold is provisioned per subscriber and Call Hold is active, it will be active for all profiles. Data for the Call Hold Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. Call Hold will function as specified in 3G TS 23.083 and will not distinguish between MSP and non-MSP subscribers.
If Call Hold is provisioned per profile then the HOLD_flag shall be set in the HLR (see clause 6.3: HOLD_flag). On receipt of an Initial_DP message for an MO or MT call, the gsmSCF will check the subscription information for the profile in use for that call. If HOLD is not active and operative, then the SII2 will be included in the Connect message with the HOLD Treatment Indicator set to Reject HOLD Request.
7.8.3 Call Waiting (CW)
Call Waiting can be provisioned per subscriber or per profile.
If Call Waiting is provisioned per subscriber and Call Waiting is active, it will be active for all profiles. Data for the Call Waiting Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. Call Waiting will function as specified in 3G TS 23.083 and will not distinguish between MSP and non-MSP subscribers.
If Call Waiting is provisioned per profile then the CW_flag shall be set in the HLR (see clause 6.4: CW_flag). On receipt of an Initial_DP message for an MO or MT call, the gsmSCF will check the subscription information for the profile in use for that call. If Call Waiting is not active and operative, then the SII2 will be included in the Connect message with the CW Treatment Indicator set to CW Not Allowed. The subscriber shall be able to modify CW information per profile by making contact with the gsmSCF using USSD. However, the subscriber shall not be able to modify CW data for the default profile.
7.8.4 Call Forwarding
The Call Forwarding Supplementary Services, described in 3G TS 23.082, can only be provisioned per subscriber. However, services equivalent to the Call Forwarding Supplementary Services, implemented in the gsmSCF, will be available to the MSP subscriber per profile. This is described in clause 7.11.1: Call Forwarding.
If the Call Forwarding Supplementary Services are provisioned per subscriber, then Call Forwarding will function as specified in 3G TS 23.082 and will not distinguish between MSP and non-MSP subscribers.
NOTE 1: If Call Forwarding is provisioned per subscriber in the HLR then Call Forwarding should not be provisioned per profile in the gsmSCF, as this may cause unpredictable behaviour.
NOTE 2: If Call Forwarding is provisioned per subscriber in the HLR then Call Deflection should not be provisioned per profile in the gsmSCF, as this may cause unpredictable behaviour.
7.8.5 Multi Party Service (MPTY)
The Multi Party Supplementary Service can be provisioned per subscriber or per profile.
If MPTY is provisioned per subscriber and MPTY is active, it will be active for all profiles. Data for the MPTY Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. MPTY will function as specified in 3G TS 23.084 and will not distinguish between MSP and non-MSP subscribers.
If MPTY is provisioned per profile then the MPTY_flag shall be set in the HLR (see clause 6.5: MPTY_flag). On receipt of an Initial_DP message for an MO or MT call, the gsmSCF will check the subscription information for the profile in use for that call. If MPTY is not active and operative, then the SII2 will be included in the Connect message with the Conference Treatment Indicator set to Reject Conference Request.
7.8.6 Closed User Group (CUG)
The Closed User Group Supplementary Service can be provisioned per subscriber or per profile.
If CUG is provisioned per subscriber and CUG is active, it will be active for all profiles. Data for the CUG Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. CUG will function as specified in 3G TS 23.085 and will not distinguish between MSP and non-MSP subscribers. The interaction between CAMEL and CUG is defined in 3G TS 23.078.
CUG provisioning per profile is supported by CAMEL Phase 3 and is FFS.
7.8.7 Advice of Charge (AoC)
The Advice of Charge Supplementary Service can be provisioned per subscriber. However, services equivalent to the Advice of Charge supplementary services, implemented in the gsmSCF, will be available to the MSP subscriber per profile. This is described in clause 7.11.4: Advice of Charge (AoC). Signalling on the access interface will be as specified in 3G TS 24.086.
If AoC is active, it will be active for all profiles. Data for the AoC Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. AoC will function as specified in 3G TS 23.086 and will not distinguish between MSP and non-MSP subscribers.
7.8.8 Call Barring
The Call Barring Supplementary Services, described in 3G TS 23.088, can only be provisioned per subscriber. However, services equivalent to the Call Barring Supplementary Services, implemented in the gsmSCF, can be provided to the MSP subscriber per profile. This is described in clause 7.11.2: Call Barring. This requires the OCB_flag mechanism described in clause clause 6.1: OCB_flag.
7.8.9 Explicit Call Transfer (ECT)
The Explicit Call Transfer supplementary service can be provisioned per subscriber or per profile.
If ECT is provisioned per subscriber and ECT is active, it will be active for all profiles. Data for the ECT Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. ECT will function as specified in 3G TS 23.091 and will not distinguish between MSP and non-MSP subscribers.
If ECT is provisioned per profile then the ECT_flag shall be set in the HLR (see clause 6.6: ECT_flag). On receipt of an Initial_DP message for an MO or MT call, the gsmSCF will check the subscription information for the profile in use for that call leg. If ECT is not active and operative, then the SII2 will be included in the Connect message with the ECT Treatment Indicator set to Reject ECT Request.
7.8.10 Completion of Calls to Busy Subscriber (CCBS)
CCBS can be provisioned per subscriber or per profile.
If CCBS is provisioned per subscriber and CCBS is active, it will be active over all profiles. Data for the CCBS Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner.
If CCBS is provisioned per profile then the CCBS_flag shall be set in the HLR (see clause 6.7: CCBS_flag).
On receipt of an Initial_DP message for an MO call, the gsmSCF will check the subscription information for the calling profile. If CCBS is not active and operative, then the SII2 will be included in the Connect message with the Call Completion Treatment Indicator set to Call Completion Not Allowed.
On receipt of an Initial_DP message for an MT call, the gsmSCF will check the subscription information for the called profile. If CCBS is not active and operative, then the SII2 will be included in the Connect message with the Call Completion Treatment Indicator sent to Call Completion not allowed.
The subscriber shall be able to modify CCBS information per profile by making contact with the gsmSCF using USSD. However, the subscriber shall not be able to modify CCBS data for the default profile.
If a CFU-equivalent service is activated while there are queue entries in MS-B’s target queue, HLR-B will not know about this activation and will process these queue entries as normal. As a consequence, the CCBS calls related to these queue entries will be forwarded to the new destination. CCBS activation is not possible if this forwarded call meets NDUB. This results in expiry of recall timer T9 and deletion of the queue entry from MS-B’s target queue. For further details on the interaction between CCBS and CAMEL, refer to 3G TS 23.093.
The same applies to Incoming Call Barring-equivalent services which are activated while there are queue entries in MS-B’s target queue.
An MSP subscriber will have CCBS set in the SS-CSI. The gsmSCF will be informed of CCBS Request and CCBS Setup messages for the MSP subscriber. This allows the service logic in the gsmSCF to assign the correct profile to the CCBS call.
7.8.11 enhanced Multi-Level Precedence and Pre-emption (eMLPP)
eMLPP will be provisioned per subscriber. If eMLPP is active, it will be active for all profiles. Data for the eMLPP Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. eMLPP will function as specified in 3G TS 23.067 and will not distinguish between MSP and non-MSP subscribers.
7.8.12 User-to-User Signalling (UUS)
The User-to-User Supplementary Service will be provisioned per subscriber. If UUS is active, it will be active for all profiles. Data for the UUS Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. UUS will function as specified in 3G TS 23.087 and will not distinguish between MSP and non-MSP subscribers.
7.8.13 Call Deflection (CD)
The Call Deflection Supplementary Service will be provisioned per subscriber. If CD is active, it will be active for all profiles. Data for the CD Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. CD will function as specified in 3G TS 23.072 and will not distinguish between MSP and non-MSP subscribers.
When the MSP subscriber deflects an MT call, it triggers an interrogation of the gsmSCF for an MO Call. Using the call reference number, the gsmSCF can recognise that there is an ongoing dialogue for the MT call, and can then retrieve the profile to apply for the deflected call.
This gives the gsmSCF the opportunity to reject the call deflection per profile, providing the MSP subscriber is in a supporting network.
NOTE: Call Deflection should not be provisioned per profile if Call Forwardings are provisioned per subscriber in the HLR as unpredictable behaviour may occur.