## 1 Barring of outgoing calls

04.883GPPCall Barring (CB) supplementary servicesStage 3TS

## 1.1 Normal operation

When a barring program relating to outgoing calls is active and operative for a basic service, each call set up related to that basic service and not allowed by the barring program will be refused by the network. In this case a NotifySS operation containing the SS-Status indicating that a barring program relating to outgoing calls is currently active and operative will be sent to the served mobile subscriber in a clearing message (see figure 1.1).

MS Network

SETUP

————————————————————————————————————————>

DISCONNECT/RELEASE/RELEASE COMPLETE

<————————————————————————————————————————

Facility (Invoke = NotifySS (SS-Code, SS-Status))

NOTE 1: The SS-Code will be the common code for outgoing barring services.

NOTE 2: $(CAMEL2)$ The DISCONNECT and RELEASE messages were introduced because of CAMEL Phase 2.

Figure 1.1: Notification to the served mobile subscriber that barring of outgoing calls is active

When a barring program is active (operative or quiescent), the ability of the served mobile subscriber to set up emergency calls is not affected, irrespective of the basic service to which the barring program applies.

When a barring program relating to outgoing calls is active (operative or quiescent), the ability of the served mobile subscriber to receive calls is not affected.

## 1.2 Registration

If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the subscriber has to register a call barring password at provision time. Furthermore the served mobile subscriber can change the call barring password by a registration procedure at any time.

If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to register a new call barring password will be denied.

The procedure to register a new password is specified in GSM 04.10.

## 1.3 Activation

If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the supplementary service is activated for a basic service if the subscriber has requested so by means of an activation procedure for that basic service. If the subscriber does not indicate a specific basic service, the activation applies to all basic services. The subscriber may use the call barring password at activation (see figure 1.2).

If the activation is successful, the service will be activated. The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below:

– The result includes the Basic Service group Code(s) to which the service is activated. The result may also contain an SS-Code and SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then these parameters shall be presented in the result. If the MS does send an SS Version Indicator in the invocation request then these parameters are optional in the result. If the SS-Status is included the network shall set it to reflect the state of the service. If the SS-Code is included then it shall contain the SS-Code of the service which has been activated. The MS shall ignore the contents of the SS-Code and SS-Status parameters if they are received.

Note that the use of SS-Code and SS-Status is to provide backwards compatibility with GSM Phase 1.

– If the request did not include a BasicServiceCode, and the activation was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS.

If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to activate the service will be denied and the served mobile subscriber receives an error indication (see figure 1.3).

Error values are specified in GSM 04.80.

MS Network

REGISTER

————————————————————————————————————————>

Facility (Invoke = ActivateSS (SS-Code, BasicServiceCode))

Password procedure according to GSM 04.10

RELEASE COMPLETE

<————————————————————————————————————————

Facility (Return result = ActivateSS (SS-Code, BasicServiceCode, SS-Status))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Return error (Error))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Reject (Invoke_problem))

NOTE: The SS-Code will be one of the specific outgoing barring codes. If BasicServiceCode is not included it applies to all basic services. The SS-Code and SS-Status may not be included in the result in all cases (see text).

Figure 1.2: Activation of a barring program

## 1.4 Deactivation

If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the supplementary service is deactivated for a basic service if the subscriber has requested deactivation by means of a deactivation procedure for that basic service. The subscriber may use the call barring password at deactivation (see figure 1.3).

The deactivation request of a barring program may specify the basic service. If the subscriber does not indicate a specific basic service, the deactivation applies to all basic services (see figure 1.3).

If the deactivation is successful, the service will be deactivated. The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below:

– The result includes the Basic Service group Code(s) to which the service is deactivated. The result may also contain an SS-Code and SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then these parameters shall be presented in the result. If the MS does send an SS Version Indicator in the invocation request then these parameters are optional in the result. If the SS-Status is included the network shall set it to reflect the state of the service. If the SS-Code is included then it shall contain the SS-Code of the service which has been deactivated. The MS shall ignore the contents of the SS-Code and SS-Status parameters if they are received.

Note that the use of SS-Code and SS-Status is to provide backwards compatibility with GSM Phase 1.

– If the request did not include a BasicServiceCode, and the deactivation was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS.

If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to deactivate the supplementary service will be denied and the served mobile subscriber receives an error indication (see figure 1.3). Error values are specified in GSM 04.80.

MS Network

REGISTER

————————————————————————————————————————>

Facility (Invoke = DeactivateSS (SS-Code, BasicServiceCode))

Password procedure according to GSM 04.10

RELEASE COMPLETE

<————————————————————————————————————————

Facility (Return result = DeactivateSS (SS-Code, BasicServiceCode, SS-Status))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Return error (Error))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Reject (Invoke_problem))

NOTE: The SS-Code may be one of the specific outgoing barring codes, the common code for the outgoing barring services, or the SS-Code for all call barring services. If BasicServiceCode is not included it applies to all basic services. The SS-Code and SS-Status may not be included in the result in all cases (see text).

Figure 1.3: Deactivation of barring of outgoing calls

## 1.5 Interrogation

The interrogation procedure enables the mobile subscriber to obtain information about data stored in the PLMN. After having requested this procedure the network shall return a list of all basic service groups for which the service is active (see figure 1.4).

If there is no basic service group for which the service is active, an SS-Status will be returned indicating that the service is "deactivated".

MS Network

REGISTER

————————————————————————————————————————>

Facility (Invoke = InterrogateSS (SS-Code))

RELEASE COMPLETE

<————————————————————————————————————————

Facility (Return result = InterrogateSS (BasicServiceCode))

or

RELEASE COMPLETE

<————————————————————————————————————————

Facility (Return result = InterrogateSS (SS-Status))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Return error (Error))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Reject (Invoke_problem))

NOTE: The SS-Code may be one of the specific outgoing barring codes.

Figure 1.4: Interrogation of a barring program

## 1.6 Invocation and erasure

Invocation and erasure are not applicable to barring programs.

## 1.7 Cross phase compatibility

### 1.7.1 Network only supports GSM Phase 1 control of SS by the subscriber

In this case there is no relevant cross phase compatibility problem.

### 1.7.2 MS only supports protocol version 1 control of SS by the subscriber

In this case there is no relevant cross phase compatibility problem.