7 Barring of incoming calls other than Anonymous Call Rejection
23.0883GPPCall Barring (CB) supplementary servicesRelease 17Stage 2TS
7.1 Handling of barring of incoming calls
7.1.0 Applicability
The user control defined in this clause is only applicable in CS domain.
For MME, only MMEs supporting the SMS in MME option described in 3GPP TS 23.272 [10] may handle barring of MT SMS.
7.1.1 Registration
If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password", he has to register a password at provision time. Furthermore the served mobile subscriber can change the password by an appropriate control procedure at any time. The control procedure consists of three steps: first, the old password has to be provided. Secondly, the new password has to be given, after which it has to be verified by providing it once more, see 3G TS 23.011.
If the served mobile subscriber at provision time has selected the subscription option "control of barring services by the service provider" an attempt to register a password will be denied and the served mobile subscriber should receive a notification.
The subscriber can register a new password, thus causing the previous registration to be overridden, see 3G TS 23.011.
7.1.2 Activation
7.1.2.1 General
The procedure for activation of Barring of outgoing calls, described in clause 1.1.2.1, is valid also for activation of Barring of incoming calls.
The information flow for activation of barring of incoming calls is shown in figure 7.3. For more details see 3G TS 23.011.
7.1.2.2 Interactions between barring of incoming call programs
If the mobile subscriber activates barring of all incoming calls and barring of incoming calls when roaming outside the home PLMN country was already activated, barring of incoming calls when roaming outside the home PLMN country will be deactivated and barring of all incoming calls will be activated.
The SDL diagram in figure 7.1 shows the function to be performed in the HLR in order to deal with this interaction between call barring services.
See clause 8.2.3.2 for the interactions with the ACR supplementary service.
7.1.2.3 Interactions with call forwarding supplementary services
This clause is not applicable for SMS.
For interactions with call forwarding supplementary services see 3G TS 22.082.
The SDL diagram in figure 7.2 shows the function to be performed in the HLR in order to deal with the interactions with call forwarding services.
Figure 7.1: BI1 Interaction between call barring programs
Figure 7.2: BI2 Interaction between call forwarding supplementary services and barring of incoming calls programs
Figure 7.3: Activation of barring of incoming calls
NOTE: BX indicates any of the barring programs.
PW1 and PW2 indicate password handling programs, see 3G TS 23.011.
7.1.3 Deactivation
The procedure for activation of Barring of outgoing calls, described in clause 1.1.2.1, is valid also correspondingly for deactivation of Barring of incoming calls with the addition that a barring supplementary service, i.e. the Incoming barring service, or All barring services can be signalled.
The information flow for deactivation of barring of incoming calls is shown in figure 7.4. For more details see 3G TS 23.011.
Figure 7.4: Deactivation of barring of incoming calls
NOTE: BI indicates the general code for barring of incoming calls.
PW1 and PW2 indicate password handling programs, see 3G TS 23.011.
7.1.4 Interrogation
The interrogation procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return a list of all basic services to which the given program is active.
The information flow for interrogation of barring of incoming calls is shown in figure 7.5.
Figure 7.5: Interrogation of barring of incoming calls
NOTE: BX indicates any of the barring programs.
7.2 Functions and information flows
The following Mobile Additional Functions have been identified:
MAF022
Barring of all incoming calls related authorizations examination
The ability of a PLMN component to determine the authorizations relating to barring of incoming calls. See figure 7.6.
Location: HSS/HLR
MAF023
Barring of incoming calls when roaming outside the home PLMN country related authorizations examination
The ability of a PLMN component to determine the authorizations relating to barring of incoming calls when roaming outside the home PLMN country. See figure 7.7.
Location: HSS/HLR
The information flow for barring of incoming circuit switched calls is shown in figure 7.8A. The information flow for barring of MT SMS is shown in figure 7.8B.
Figure 7.6: MAF022 Barring of all incoming circuit switched calls and MT SMS related authorisations examination (HSS/HLR)
Figure 7.7: MAF023 Barring of incoming circuit switched calls and MT SMS when roaming outside the home PLMN country related authorisations examination (HSS/HLR)
NOTE: info req: information request
info ack: information acknowledge
OR1: call barred Y: yes
N: no.
Figure 7.8A: Information flow for barring of incoming circuit switched calls
NOTE: info req: information request
info ack: information acknowledge
OR1: call barred Y: yes
N: no.
Figure 7.8B: Information flow for barring of MT SMS
7.3 Information stored in the HSS/HLR
For all call barring supplementary services in the HSS/HLR must be stored:
– the subscription option "control of barring services" on per subscriber basis.
This subscription option takes one of the following values:
– by subscriber using password;
– by the service provider.
If the subscription option "control of barring services" has been set to "by subscriber using password" for barring of incoming calls in the HLR must be stored on a per subscriber basis:
– the registration parameter "call barring password".
The password is valid for all basic services to which barring of incoming calls applies;
– the status parameter "wrong password attempts counter" associated with the password.
Note that the subscription option and the call barring password are parameters which are associated with all call barring services.
The incoming calls barring program may have the following logical states (refer to 3G TS 23.011 for an explanation of the notation):
|
Provisioning State |
Registration State |
Activation State |
HSS/HLR Induction State |
|
(Not Provisioned, |
Not Applicable, |
Not Active, |
Not Induced) |
|
(Provisioned, |
Not Applicable, |
Not Active, |
Not Induced) |
|
(Provisioned, |
Not Applicable, |
Active and Operative, |
Not Induced) |
The program of barring of incoming call when roaming outside the home PLMN country may also have the following logical state:
|
Provisioning State |
Registration State |
Activation State |
HSS/HLR Induction State |
|
(Provisioned, |
Not Applicable, |
Active and Quiescent, |
Not Induced) |
The activation and HSS/HLR induction states may be different for each applicable elementary basic service group.
The provisioning state shall be on a per subscriber basis, and hence the same for all basic service groups.
The HSS/HLR shall also store the logical state of the incoming calls barring program (which shall be one of the valid states listed above) for each applicable elementary basic service group.
7.4 State transition model
The following figures show the successful cases of transition between the applicable logical states of the call barring program. The state changes are either caused by actions of the service provider, the mobile user or the network.
Note that error cases are not shown in the diagrams as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence, they are not shown in the diagrams.
The diagrams only show operations on an elementary basic service group.
Figure 7.9: State transition model for BAIC
Figure 7.10: State transition model for BIC-Roam
NOTE: SS-I: SS Interaction started or Subscriber in HPLMN country.
SS-I/E: SS Interaction ended or Subscriber not in HPLMN country.
7.5 Transfer of information from HSS/HLR to VLR/SGSN/MME
No information is transferred from HSS/HLR to VLR/SGSN/MME for the incoming calls barring program.
7.6 Information stored in the VLR/SGSN/MME
No information is stored in the VLR/SGSN/MME.
7.7 Handover
Handover will have no impact on the control procedures and the operation of the service.
7.8 Cross Phase compatibility
7.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber
In response to a Barring of incoming calls interrogation request, if the MS or any network element involved is of Phase 1, only information concerning basic service groups for which Barring of incoming calls is active will be returned.
In Phase 1 the state active and quiescent is not used in the HLR.
In Phase 2 the HLR will support the quiescent state.
As this quiescent state is only relevant within the HLR a Phase 1 MSC/VLR and a Phase 1 MS can support the Phase 2 interrogation even if the service becomes quiescent, i.e. there is no functional cross Phase compatibility problem.
Note that the interrogation result received by the user will be in Phase 1 and 2 a list of basic services. The only difference is that in Phase 1 it contains the active basic services irrespective of whether it is operative or quiescent.
7.8.2 HLR only supports Phase 1 updating of subscriber information
In Phase 1 the VLR stores the activation status also for barring of incoming calls.
In Phase 2 no information is stored in the VLR in case of barring of incoming calls. The VLR may receive subscription information for barring of incoming calls from a Phase 1 HLR. In this case the VLR shall ignore this information.