7.11 Equivalent services implemented by the gsmSCF
23.0973GPPMultiple Subscriber Profile (MSP) Phase 2Release 17Stage 2TS
7.11.1 Call Forwarding
Call Forwarding services will be provided in the gsmSCF per profile. An MT call to an MSP subscriber will be subject to the provided call forwardings for the called profile.
The Call Forwarding services, implemented by the gsmSCF, should operate in the same way as the Call Forwarding Supplementary Services. The MSP subscriber should have control over the call forwarding data (Registration, Erasure, Activation, Deactivation, and Interrogation). The method for controlling this data is a network option.
Figure 31: Information flow for a successful MT call to a profile
with some Call Forwardings Active and Operative
NOTE: Request_Report_BCSM_Event will contain the list Arm_DP_List (see figure 1). This list will contain the following elements:
T_Answer EDP-N
T_Abandon EDP-N
T_Busy EDP-N (Unless CFB and/or CFNRc are A&O for the called profile, in which case EDP-R)
T_No_Answer EDP-N (Unless CFNRy is A&O for the called profile, in which case EDP-R)
7.11.1.1 Call Forward Unconditional
Figure 32: Information flow for an MT call to a profile with CFU active
and operative in the gsmSCF
7.11.1.2 Call Forward on Busy
Figure 33: Information flow for an MT call to a profile with CFB active
and operative in the gsmSCF, where the called subscriber is NDUB or UDUB
7.11.1.3 Call Forward on No Reply
Figure 34: Information flow for an MT call to a profile with CFNRy active
and operative in the gsmSCF, where the called party does not answer
NOTE: The timer TNRy is started in the GMSC after the Address Complete Message has been received from the destination exchange. If this timer expires before an Answer message is received from the destination exchange, a release message is sent to the destination exchange and the detection point T_No_Answer is reached. This is specified in 3G TS 23.018 and 3G TS 23.078.
7.11.1.4 Call Forward on Not Reachable
7.11.1.5 Early CFNRc
Early Call Forwarding on Not Reachable will apply if the gsmSCF receives the parameter "subscriber state" set as Not Reachable. Due to the presence of the Location information / Subscriber state Interrogation parameter in the CAMEL data, stored in the HLR, the HLR sends a Provide Subscriber Information message to the VLR. This determines if the subscriber state is Not Reachable.
Figure 35: Information flow for an MT call to a profile with CFNRc active
and operative in the gsmSCF, where early CFNRc is invoked
7.11.1.6 Late CFNRc
Figure 36: Information flow for an MT call to a profile with CFNRc active
and operative in the gsmSCF, where late CFNRc is invoked
7.11.2 Call Barring
Call Barring services can be provided by the gsmSCF per profile. An MO call made by an MSP subscriber will be subject to the outgoing call barrings provided for the Calling profile. An MT call to an MSP subscriber will be subject to the incoming call barrings provided for the Called profile. If an MT call to an MSP subscriber is forwarded, the forwarded call will be subject to the outgoing call barrings provided for the Called profile.
The Call Barring services available per profile are:
– Barring of all outgoing calls (BAOC);
– Barring of outgoing international calls (BOIC);
– Barring of outgoing international calls except those directed to the home PLMN country (BOIC-exHC);
– Barring of all incoming calls (BAIC);
– Barring of incoming calls when roaming outside the home PLMN country (BIC-roam).
The Call Barring services, implemented by the gsmSCF, should operate in the same way as the Call Barring Supplementary Services. The MSP subscriber should have control over the call barring data (Registration, Erasure, Activation, Deactivation, and Interrogation). The method for controlling this data is a network option.
If the MSP subscriber changes the Outgoing Call Barrings for the default profile by contacting the gsmSCF, the gsmSCF will change the barrings stored in the gsmSCF and inform the HLR using ATM to change the barrings stored in the HLR. The Call Barring Supplementary Services may require a password before Call Barring data can be changed. For the Call Barring Services implemented in the gsmSCF, use of a password is a network option.
The operator should ensure that if the equivalent call barring service is provided then:
– the OCB_flag is set in the HLR (See clause 6.1:OCB_flag);
– if an equivalent outgoing call barring service is in a "Provisioned and Active" state in the gsmSCF for the default profile, that outgoing call barring supplementary service will be in a "Provisioned and Active" state in the HLR;
– if an equivalent outgoing call barring service is in a "Not Active" state in the gsmSCF for the default profile, that outgoing call barring supplementary service will be in a "Not Provisioned" state in the HLR;
– incoming Call Barrings shall not be provisioned in the HLR;
NOTE: Barrings will not apply to MT short messages.
7.11.3 Operator Determined Barring (ODB)
Operator Determined Barring will be available per profile in the gsmSCF for the following categories:
– Barring of outgoing calls;
– Barring of incoming calls;
– Barring of roaming;
– Barring of outgoing Premium Rate Calls;
– Barring specific to the home PLMN;
– Barring of registration of call forwarding;
– Barring of invocation of call transfer.
However, if zone related barring is implemented in the gsmSCF, the appropriate data will be needed in the gsmSCF as well as the HLR. For barring of incoming calls when roaming outside the zone of the home country, the gsmSCF will need to use Any Time Interrogation to establish the location of the called party.
Management of ODB data is operator specific.
The operator should ensure that if the equivalent ODB service for an ODB category is provided then:
– the ODB flag for the correct category is set in the HLR (See clause 6.2: ODB flags);
– the ODB data for that category for the default profile is duplicated in the HLR.
NOTE: Barring of incoming calls in the gsmSCF will not disallow MO or MT short messages.
7.11.4 Advice of Charge (AoC)
Advice of Charge is available per profile in the gsmSCF. This is detailed in the SDL diagrams in clause 7.5: Functions and Information flows.