2 Barring of incoming calls
22.0883GPPCall Barring (CB) supplementary servicesStage 1TS
2.1 Definition
This service makes it possible for a mobile subscriber to have barring of certain categories of incoming calls according to a barring program which is selected from a set of one or more barring programs chosen at provision time and is valid for all incoming calls, or just those associated with a specific basic service group.
The ability of the served mobile subscriber to set-up outgoing calls remains unaffected.
2.2 General description
2.2.1 Description
The mobile subscriber may determine by subscription of a set of one or more barring programs what kind of incoming calls shall be barred.
The following barring programs are defined:
1) Barring of all incoming calls;
2) Barring of incoming calls when roaming outside the home PLMN country;
3) Anonymous Call Rejection.
The barring programs 2) and 3) may be active simultaneously per basic service group, but can not be active simultaneously with the barring program 1) per basic service group. The PLMN will ensure that exclusive barring programs are not active simultaneously per basic service group. The activation of one specific barring program will override an already active exclusive one (i.e. the old one will be permanently deactivated).
If barring programs 2) and 3) are active simultaneously for a specific basic service group, the barring program 2) shall apply when the called subscriber is roaming outside the home PLMN country.
Description of contents of barring programs:
Barring of all incoming calls:
With this barring program there will be no set-up of incoming calls to the served subscriber.
Barring of incoming calls when roaming outside the home PLMN country:
With this barring program, calls which are terminated for the served subscriber will be barred if the subscriber is roaming outside the home PLMN country (i.e. the program is active and operative). The ability to receive calls in the home PLMN country remains unaffected (i.e. the program is active and quiescent).
Anonymous Call Rejection:
With this barring program, calls which are terminated for the served subscriber will be barred when the CLI presentation is restricted according to CLIR. The calls are barred regardless of the current state (e.g. free or busy) of the served subscriber’s access. The calling user will be given an appropriate indication that the call has been rejected due to the application of the ACR supplementary service. Calls which are terminated for the served subscriber without a CLI or when CLI presentation is not available, is allowed, or is restricted by the network shall be allowed.
2.2.2 Applicability to telecommunication services
The applicability of this supplementary service is defined in 3GPP TS 22.004 [2].
2.2.3 Terminology
A barring program defines the subscribed barring condition and will determine the categories of calls to be barred.
2.3 Normal procedures with successful outcome
2.3.1 Provision
The supplementary service will be provided after pre-arrangement with the service provider. At provision, subscription options should be selected by the served mobile subscriber.
The service can be offered with two subscription options.
The first subscription option is the definition of the barring condition by a set of one or more barring programs. This subscription option applies to all basic services subscribed to. Only one value can be selected for the barring condition.
The second subscription option relates to the control of the call barring supplementary service(s). The subscriber may choose to have the control of the service(s) by use of a password, or may leave the control to the service provider. The value of this subscription option is valid collectively for all basic services and all call barring supplementary services to which the subscriber subscribes to.
Subscription options are summarized below:
|
Subscription option |
Value |
|
Barring condition |
– barring program 1 |
|
– barring program 2 |
|
|
– barring program 1 and |
|
|
barring program 2 |
|
|
Control of barring services |
– by subscriber using password |
|
– by the service provider |
|
NOTE: A service provider needs not offer the option "control of barring services" to his subscribers. However, the support of the password facility is mandatory in the network for visiting subscribers.
2.3.2 Withdrawal
The service will be withdrawn at the subscriber’s request or for administrative reasons.
2.3.3 Registration
If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password", the service provider has to register a password at provision time. Furthermore, the served mobile subscriber can change the password at any time by an appropriate control procedure which is described in 3GPP TS 22.004 [2].
2.3.4 Erasure
If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password", a password can be erased as described in 3GPP TS 22.004 [2].
2.3.5 Activation
Activation takes place with an appropriate control procedure by the subscriber or by the service provider. The activation of barring of incoming calls does not affect any current communication. Only one barring program may be activated at a time for one basic service group. The activation of the barring program will deactivate an already active one.
If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by subscriber using password", the supplementary service is activated if the subscriber provides the following information to the network:
– password;
– information as to whether all calls or calls of a specific basic service group should be barred.
NOTE: If no Basic Service code is inserted by the user this is interpreted as the group "All Basic Services".
– selected barring program.
If the served mobile subscriber at provision time has selected the subscription option "control of barring services by service provider", the supplementary service cannot be activated by the subscriber. The activation has to be performed by the service provider.
The activation status attached to different basic service groups can be modified separately.
2.3.6 Deactivation
Deactivation takes place by means of an appropriate control procedure by the subscriber, or by the service provider, or finally by activation of a new barring program for the same basic service group.
If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password", the supplementary service is deactivated if the subscriber provides the following information to the network:
– password;
– information as to whether barring of all calls or calls of a specific basic service group should be deactivated.
NOTE: If no Basic Service code is inserted by the user this is interpreted as the group "All Basic Services".
– selected barring program (i.e. the code for one specific Incoming Barring program given in 3GPP TS 22.030) or selected barring supplementary service (i.e. the code for Incoming Barring Service or the code for All Barring Services given in 3GPP TS 22.030).
If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by service provider", the supplementary service cannot be deactivated by the subscriber. The deactivation has to be performed by the service provider.
2.3.7 Invocation
The supplementary service is automatically invoked by the network upon a request for an incoming call for a basic service not allowed by an active and operative barring program for the corresponding basic service group.
2.3.8 Normal operation with successful outcome
When barring of incoming calls is active for a basic service group, each incoming call set-up not allowed by the barring program related to that basic service group will be refused by the network. In this case the calling mobile subscriber will receive an indication that the call is not permitted and has been barred.
When barring of incoming calls is active, the ability of the served mobile subscriber to originate calls is not affected.
2.3.11 Interrogation
The subscriber shall by an appropriate control procedure be given the possibility to get a list of all basic service groups for which the given barring program is active (irrespective of whether it is operative or quiescent).
2.4 Exceptional procedures or unsuccessful outcome
2.4.2 Registration
If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by service provider", an attempt to register a password will be denied and the served mobile subscriber should receive a notification.
When the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by subscriber using password", the handling of incorrect password entry is as described in 3GPP TS 22.004 [2].
2.4.4 Activation
If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by the service provider", an attempt to activate the barring services will be denied and the served mobile subscriber should receive a notification.
If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by the subscriber using password", the handling of incorrect password entry is as described in 3GPP TS 22.004 [2].
The barring of incoming calls activation request must specify the basic service group and the selected barring program. If the subscriber does not completely specify for which basic service (individual basic service group or all basic service groups) barring of incoming calls is to be activated and the selected barring program, the network will reject the activation request with appropriate cause.
NOTE: If no Basic Service group code is inserted by the user this is interpreted as the group "All Basic Services".
2.4.5 Deactivation
If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by the service provider", an attempt to deactivate will be denied and the served mobile subscriber should receive a notification.
If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by the subscriber using password", the handling of incorrect password entry is as described in 3GPP TS 22.004 [2].
The barring of incoming calls deactivation request must specify the basic service group and the selected barring program (i.e. the code for one specific Incoming Barring program given in 3GPP TS 22.030) or the selected barring supplementary service (i.e. the code for Incoming Barring Service or the code for All Barring Services given in 3GPP TS 22.030). If the subscriber does not completely specify for which basic service group (individual basic service group or all basic service groups) barring of incoming calls is to be deactivated and the selected barring program or supplementary service, the network will reject the deactivation request with appropriate cause.
NOTE: If no Basic Service group code is inserted by the user this is interpreted as the group "All Basic Services".
2.5 Alternate procedures
None identified.
2.6 Interactions with other supplementary services
2.6.82.1 Call forwarding unconditional
Except for ACR, see 3GPP TS 22.082 [4].
For ACR, if the served (forwarding) user has activated the ACR supplementary service, then the ACR supplementary service shall take precedence over the Call forwarding unconditional supplementary service, i.e. , a call which is terminated for the served subscriber when CLI presentation is restricted shall be rejected according to the ACR supplementary service.
2.6.82.2 Call forwarding on mobile subscriber busy
Except for ACR, see 3GPP TS 22.082 [4].
For ACR, i f the served (forwarding) user has activated the ACR supplementary service, then the ACR supplementary service shall take precedence over the Call forwarding on mobile subscriber busy supplementary service i.e. , a call which is terminated for the served subscriber when CLI is restricted shall be rejected according to the ACR supplementary service.
2.6.82.3 Call forwarding on no reply
Except for ACR , see 3GPP TS 22.082 [4].
For ACR, if the served (forwarding) user has activated the ACR supplementary service, then the ACR supplementary service shall take precedence over the Call forwarding on no reply supplementary service, i.e., a call which is terminated for the served subscriber when CLI is restricted shall be rejected according to the ACR supplementary service.
2.6.82.4 Call forwarding on mobile subscriber not reachable
Except for ACR, see 3GPP TS 22.082 [4].
For ACR, if the served (forwarding) user has activated the ACR supplementary service, then the ACR supplementary service shall take precedence over the Call forwarding on mobile subscriber not reachable supplementary service i.e., a call which is terminated for the served subscriber when CLI is restricted shall be rejected according to the ACR supplementary service.
2.6.83.2 Call hold
If barring of incoming calls is activated after a call hold is invoked on an incoming call, the held call can be retrieved. Any new incoming call not allowed by the barring program is barred.
2.6.81.1 Calling Line Identification
If the called user has subscribed to the override category according to the CLIP supplementary service [6], then the CLIP supplementary service shall take precedence over the ACR supplementary service, i.e., a call which is terminated for the served subscriber when CLI is restricted shall be offered to the served subscriber.
2.6.84 MultiParty service
See 3GPP TS 22.084 [5].
2.6.85.1 Closed user group
Except for ACR, barring of incoming calls takes precedence over the CUG restrictions. The activation of barring of incoming calls during an incoming call does not affect any current CUG call.
If the called user has activated the ACR supplementary service, then if a closed user group call is offered to a called user belonging to the same closed user group, the closed user group call shall take precedence over the ACR supplementary service. If the called user also has the incoming access capability within the closed user group supplementary service, and if the offered call to the called user is also a non-closed user group call or a closed user group call to which the called party does not belong, the ACR supplementary service shall take precedence over the closed user group supplementary service.
2.7 Interworking considerations
None identified.
Annex A (informative):
Change history
|
Change history |
|||||||||||
|
TSG SA# |
SA Doc. |
SA1 Doc |
Spec |
CR |
Rev |
Rel |
Cat |
Subject/Comment |
Old |
New |
WI |
|
Jun 1999 |
GSM 02.88 |
Transferred to 3GPP SA1 |
7.0.0 |
||||||||
|
SA#04 |
22.088 |
R99 |
Transferred to 3GPP SA1 |
3.0.0 |
|||||||
|
SP-05 |
SP-99479 |
S1-99635 |
22.088 |
001 |
R99 |
D |
Editorial changes for alignment |
3.0.0 |
3.0.1 |
Editorial changes |
|
|
22/05/00 |
22.088 |
None |
R99 |
Correction of wrong implementation of CR |
3.0.1 |
3.0.2 |
|||||
|
SP-11 |
SP-010065 |
S1-010258 |
22.088 |
Rel-4 |
Transferred to 3GPP Release 4 |
3.0.2 |
4.0.0 |
||||
|
SP-15 |
SP-020045 |
S1-020457 |
22.088 |
002 |
– |
Rel-4 |
F |
Editorial CR to correct terms and references |
4.0.0 |
4.1.0 |
CORRECT |
|
SP-16 |
SP-020267 |
S1-021043 |
22.088 |
Rel-5 |
Updated from Rel-4 to Rel5 |
4.1.0 |
5.0.0 |
||||
|
SP-26 |
SP-040744 |
S1-040997 |
22.088 |
Rel-6 |
Updated from Rel-5 to Rel-6 |
5.0.0 |
6.0.0 |
||||
|
SP-36 |
22.088 |
Rel-7 |
Updated from Rel-6 to Rel-7 |
6.0.0 |
7.0.0 |
||||||
|
SP-42 |
– |
– |
Rel-8 |
Updated from Rel-7 to Rel-8 |
7.0.0 |
8.0.0 |
|||||
|
SP-46 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-9 by MCC |
8.0.0 |
9.0.0 |
|
|
2011-03 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
9.0.0 |
10.0.0 |
|
|
SP-52 |
SP-110376 |
S1-111434 |
22.088 |
0003 |
4 |
Rel-11 |
B |
Addition of Anonymous Call Rejection as a SS |
10.0.0 |
11.0.0 |
ACR_CS |
|
SP-61 |
SP-130456 |
S1-134178 |
22.088 |
0006 |
4 |
Rel-11 |
F |
SMSC Usage Restriction in Roaming |
11.0.0 |
11.1.0 |
TEI11 |
|
2014-10 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-12 version (MCC) |
11.1.0 |
12.0.0 |
|
|
2015-12 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-13 by MCC |
12.0.0 |
13.0.0 |
|
|
2017-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-14 by MCC |
13.0.0 |
14.0.0 |
|
|
2018-06 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-15 by MCC |
14.0.0 |
15.0.0 |
|
|
SA#88e |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-16 by MCC |
15.0.0 |
16.0.0 |
|
|
2022-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-17 by MCC |
16.0.0 |
17.0.0 |
|