All rights reserved.

Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

COVER SHEET
MOBILE COMMUNICATION GROUP

Title

Supplementary Services: Call Barring

Classification

A5020 Spatial ATRIUM Softswitch GSM/UMTS CS CORE NETWORK SYSTEM DOCUMENTATION TECHNICAL REQUIREMENT SPECIFICATION

Edition Date Change Note

02 2007/05/31 update

3BL76551AAAA DSZZA

EDITION

02

En

1/2

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Originator(s) Approval(s)

Jian Lu

ABSTRACT REVIEW HISTORY

Reviewed on YY/MM/DD Minutes= http://dbs01.usa.alcatel.com:7778/ACE/ace.main meeting #46529

01 on 2006-01-20 02 on 2006-02-15 03 on 2006-06-22 04 on 2006-06-23 05 ob 2007-05-31

Mnemonic

Creation: Update after review By Karlheinz Stadler: Barring of SMS calls added (chapter 3.2.2) By Karlheinz Stadler: Correction after internal review By Harinder Lakhian to update the TRS for RDS6546 and RDS5592 <mnemonic>

INTERNAL REFERENCED DOCUMENTS

None.

END OF COVERSHEET

3BL76551AAAA DSZZA

EDITION

02

En

2/2

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

3BL76551AAAADSZZA

Supplementary Service

Call Barring

A5020 Spatial ATRIUM Softswitch

TECHNICAL REQUIREMENT SPECIFICATION

EDITION 02

En

1/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

CONTENTS
1 2 INTRODUCTION .................................................................................................................... 5 FUNCTIONAL DESCRIPTION .................................................................................................. 6 2.1 BARRING OF OUTGOING CALLS........................................................................................................... 6 2.2 BARRING OF INCOMING CALLS ............................................................................................................ 6 2.3 CALL BARRING SERVICE CONTROL PROCEDURES...................................................................................... 7 2.3.1 Registration............................................................................................................................... 7 2.3.2 Activation.................................................................................................................................. 7 2.3.3 Deactivation ............................................................................................................................. 8 2.3.4 Invocation and Erasure ............................................................................................................. 9 2.3.5 Interrogation............................................................................................................................. 9 3 CALL BARRING ON ATRIUM WSS ........................................................................................ 11 3.1 3.2 3.2.1 3.2.2 3.3 3.4 4 4.1 5 5.1 5.2 5.3 6 6.1 6.2 6.3 6.4 7 8 9 CALL BARRING ON GMSC ............................................................................................................... 11 CALL BARRING ON VMSC/VLR ......................................................................................................... 13 Barring of Outgoing Voice Calls.............................................................................................. 13 Special Barring Procedures for SMS-MO.................................................................................. 14 MSC AND VLR TRANSMIT CB SS CONTROL MESSAGES TO HLR .............................................................. 14 CALL BARRING DATA IN VLR DB ........................................................................................................ 14

CALL BARRING SPECIAL TREATMENT .................................................................................. 16 CALL BARRING NOTIFICATION BY ANNOUNCEMENT .............................................................................. 16 SYSTEM INTERFACE.............................................................................................................. 18 MAP INTERFACE ON GMSC- HLR ..................................................................................................... 18 D INTERFACE (VLR- HLR) ................................................................................................................. 19 B INTERFACE (VMSC- VLR) .............................................................................................................. 21 INTERACTION WITH OTHER FEATURES................................................................................ 22 INTERACTION BETWEEN BARRING OF INCOMING CALL ............................................................................ 22 OPERATOR DETERMINED CALL BARRING (ODB) .................................................................................... 22 CALL FORWARDING ......................................................................................................................... 22 CUG CLOSED USER GROUP .......................................................................................................... 23 CALL BARRING CHARGING (BILLING) ................................................................................ 24 MEASUREMENT (PEG COUNTERS AND KPI) ........................................................................ 27 PERFORMANCE AND DIMENSIONING ................................................................................ 27

3BL76551AAAADSZZA

EDITION 02

En

2/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

HISTORY
Ed01 on 2006-01-20 Creation

REFERENCED DOCUMENTS
[1] 3GPP TS 23.018: Basic Call Handling [2] 3GPP TS 22.088: Call Barring (CB) Supplementary Service; Stage 1 [3] 3GPP TS 23.088: Call Barring (CB) Supplementary Service; Stage 2 [4] 3GPP TS 24.088:Call Barring (CB) Supplementary Service; Stage 3 [5] 3GPP TS 22.082: Call Forwarding (CF) Supplementary Services; Stage 1 [6] 3GPP TS 23.082: Call Forwarding (CF) Supplementary Services; Stage 2 [7] 3GPP TS 22.083: "Call Waiting (CW) and Call Hold (CH) Supplementary Services - Stage 1 [8] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (CH) Supplementary Services - Stage 2 [9] 3GPP TS 22.004: General on Supplementary Services [10] 3GPP TS 22.041: Operator Determined Call Barring [11] 3GPP TS 23.015: Technical realization of Operator Determined Barring (ODB) [12] 3GPP TS 22.085: Closed User Group (CUG) supplementary services; Stage 1 [13] 3GPP TS 29.002: Mobile Application Part (MAP) Specification [14] Internal document Spatial CDR Format [15] Internal document Performance Data Measurements for Operation Administration and Maintenance [16] 3BL61721AAAAPBZZA: TRS SAS Call scenario : Supplementary services [17] RDS6546 [18] RDS5592

RELATED DOCUMENTS
See section REFERENCED DOCUMENTS.

PREFACE
None.

3BL76551AAAADSZZA

EDITION 02

En

3/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

3BL76551AAAADSZZA

EDITION 02

En

4/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

INTRODUCTION

The present document describes the supplementary services belonging to the group Call Restriction Supplementary Services on Atrium WSS. The group of Call Restriction Services includes two supplementary services: - barring of outgoing calls; barring of incoming calls.

By use of subscription options, the mobile subscriber can at provision time select a set of one or more barring programs to determine the categories of calls to be barred. The following categories are defined: all outgoing calls(BAOC); outgoing international calls(BOIC); outgoing international calls except those directed to the home PLMN country(BOIC-exHC); all incoming calls(BAIC); incoming calls when roaming outside the home PLMN country(BIC-Roam).

NOTE 1: Each category (barring program) is handled as a single supplementary service. NOTE 2: The call barring program "incoming calls when roaming outside the home PLMN country" is only relevant if as a general rule the called mobile subscriber pays the charges for the forwarded part of the call from his home PLMN country to any other country. Note 3: Skip barring is allowed for subscribers with BAOC for the following cases: - Emergency calls - for certain dialled number defined by operators - Combination of dialled number and calling subscriber's OSSS code or O-CSI trigger (whatever is the TDP or the triggering criteria). The barring services can be offered to a mobile subscriber with a password option allowing the activation and deactivation by the subscriber. One password per mobile subscriber is supported by the network for all barring services. The Call Barring service is applicable to all basic services except Emergency Call. Atrium WSS may act as a GMSC, a VMSC/ VLR, or both if GMSC and VMSC are collocated. The Call Barring impact on GMSC, VMSC and VLR are included in the following sections.

3BL76551AAAADSZZA

EDITION 02

En

5/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

FUNCTIONAL DESCRIPTION

2.1 Barring of Outgoing Calls

The mobile subscriber may determine by subscription of a set of one or more unique barring programs what kind of outgoing calls shall be barred. The following barring programs are defined: Barring of all outgoing calls: With this barring program there are no outgoing call set-up possibilities, except emergency calls and skip barring provisioned by the service provider. The service provider may define skip call barring for certain dialled number applicable to all subscribers. The skip call barring may also be allowed on a per subscriber basis using combination of certain dialled number, calling subscribers OSSS code and O-CSI trigger (whatever is the TDP or the triggering criteria). The decision whether call barring can apply or not will depend on the dialled number or combination of dialled number, OSSS code value, and presence of O-CSI for the calling subscriber. The following is a list of few examples for which calls will not be barred: - any subscriber dials 611, 615 (skip call barring for all subscribers when dialled digits are 611 or 615) - subscriber with no OSSS nor OCSI dials 500, 555, 290 or 700 - subscriber with OSSS 0xF1 or 0xF2 dials 222 or 290 - subscriber with OSSS 0xF4 whatever is the number dialed - subscriber with OSSS 0xF5 dials 290 - subscriber with OSSS 0xF6 dials 290 - subscriber with OCSI dials 290 For instance, if a subscriber with BAOC and OSSS 0xF1 dials 500, the call must be barred. If the same subscriber dials 222or 290, the call must not be barred. Barring of outgoing international calls: Outgoing call set-up possibilities exist only to subscribers of the PLMN(s) and the fixed network(s) of the country where the mobile subscriber is presently located. So the present PLMN may be the home PLMN or a visited PLMN, respectively the fixed network may be that of the home PLMN country or that of a visited PLMN country. Barring of all outgoing international calls except those directed to the home PLMN country: Outgoing call set-up possibilities exist only to subscribers of the PLMN(s) and the fixed network(s) of the country where the mobile subscriber is presently located or to mobile subscribers of the home PLMN country of the served mobile subscriber and to subscribers of the fixed network(s) in the home PLMN country. So the present PLMN may be the home PLMN or a visited PLMN, respectively the fixed network may be that of the home PLMN country or that of a visited PLMN country.

The PLMN will ensure that only one of the barring programs is active per basic service group. The activation of one specific barring program will override an already active one (i.e. the old one will be permanently deactivated). Barring of all outgoing calls examination logic is in VLR.

2.2 Barring of Incoming Calls

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.

3BL76551AAAADSZZA

EDITION 02

En

6/29

The ability of the served mobile subscriber to set-up outgoing calls remains unaffected.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

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: 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).

The PLMN will ensure that only one of the barring programs is active per basic service group. The activation of one specific barring program will override an already active one (i.e. the old one will be permanently deactivated). Barring of all incoming calls examination logic is in HLR.

2.3 Call Barring Service Control Procedures

The Call Barring supplementary service shall be provided after pre-arrangement with the service provider. User subscribe call barring service through service provide. The subscription data is stored in the HLR. Mobile subscriber can have operations from his handset to update subscription data.

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. 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.

The followings are the proper control procedures on Call Barring: 2.3.1 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.

2.3.2 Activation Activation takes place with an appropriate control procedure by the subscriber or by the service provider. The activation of barring of outgoing 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 a barring program will deactivate an already active one.

3BL76551AAAADSZZA

EDITION 02

En

7/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

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. If no Basic Service code is inserted by the user this is interpreted as the group "All Basic Services".

NOTE: -

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.

MT

Atrium
MSC/VLR
A-ITF: REGISTER Facility(Invoke=activateSS,SS-forBS: ssCode= BAOC, basicService=x) MAP: ACTIVATE SS Invoke(SS-Code= BAOC, basicService=x)

HLR

MAP: GET PASSWORD Invoke(Guidance Info) A-ITF: FACILITY Invoke(getPassword, guidanceInfo) A-ITF: FACILITY Result(getPassword, currentPassword) MAP: GET PASSWORD Result(Current Password)

MAP: ACTIVATE SS Acknowledge Result(SS-Info) RELEASE_COMPLETE Facility(Result=activateSS,ssInfo Insert Subscriber Data

Figure 2-1: Call Barring Activation - this figure is applicable to all CB ssCode, ssCode =BAOC is an example. Note: MAP messages (ActivateSS, GetPassord) and MAP ISD are handled in separate TCAP transaction. 2.3.3 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:

3BL76551AAAADSZZA

EDITION 02

En

8/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

password; information as to whether barring of all calls or calls of a specific basic service group should be deactivated. If no Basic Service code is inserted by the user this is interpreted as the group "All Basic Services".

NOTE: -

selected barring program (i.e. the code for one specific Outgoing Barring program given in GSM 02.30) or selected barring supplementary service (i.e. the code for Outgoing Barring Service or the code for All Barring Services given in 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.

MT

Atrium
MSC/VLR
A-ITF: REGISTER Facility(Invoke=deactivateSS,SS-forBS: ssCode= BAOC, basicService=x) MAP: DEACTIVATE SS Invoke(SS-Code= BAOC, basicService=x)

HLR

MAP: GET PASSWORD Invoke(Guidance Info) A-ITF: FACILITY Invoke(getPassword, guidanceInfo) A-ITF: FACILITY Result(getPassword, currentPassword) MAP: GET PASSWORD Result(Current Password)

MAP: DEACTIVATE SS Acknowledge Result(SS-Info) RELEASE_COMPLETE Facility(Result=deactivateSS,ssInfo Insert Subscriber Data

Figure 2-2: Call Barring Deactivation- this figure is applicable to all CB ssCode, ssCode=BAOC is an example. Note: GuidanceInfo =EnterPW. 2.3.4 Invocation and Erasure

Invocation and erasure are not applicable to barring programs.

2.3.5 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). In the situation when a subscriber has activated BOIC-exHC and is roaming in a PLMN not supporting this supplementary service, the local PLMN will return - as an answer to interrogation - the status "not supported".

3BL76551AAAADSZZA

EDITION 02

En

9/29

This information may be translated by the mobile station to inform the user about the replacement of BOICexHC with BOIC.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

If the served mobile subscriber wants to retrieve information from the local PLMN about the status of BOIC, she has to repeat the interrogation procedure with the supplementary service code for BOIC.

MT

Atrium
MSC/VLR
A-ITF: REGISTER Facility(Invoke=interrogateSS,ssCode= BAIC, basicService=x,)

HLR

MAP: INTERROGATE SS Invoke(SS-forBS: SS-Code= BAIC, basicService=x) MAP: INTERROGATE SS Acknowledge Result(InterrogateSS-Res: SS-Status) RELEASE_COMPLETE Facility(Result=registerSS,interrogateSSRes(ssStatus, basicService=x,)

Figure 2-3: Call Barring of Incoming Calls Interrogation

MT

Atrium
MSC/VLR
A-ITF: REGISTER Facility(Invoke=interrogateSS,ssCode= BAOC, basicService=x,)

HLR

RELEASE_COMPLETE Facility(Result=registerSS,interrogateSSRes(ssStatus, basicService=x,)

Figure 2-4: Call Barring of Outgoing Calls Interrogation

3BL76551AAAADSZZA

EDITION 02

En

10/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

CALL BARRING ON ATRIUM WSS

Atrium WSS is a combination of GMSC, VMSC/VLR. Call Barring shall be implemented on GMSC, VMSC/VLR.

3.1 Call Barring on GMSC

For the incoming call received on GMSC, the Barring decision is determined by the HLR when one of barring incoming call condition occurs: Barring of all incoming calls Barring of incoming calls when roaming outside the home PLMN country

In this case, the GMSC receives user cause (Call Barred) within SRI acknowledge. The GMSC performs the following: Release the call with cause ( call barred) Notification to Calling Party that Called mobile has call barring active Generate CDR on GMSC based on the barred call.

Figure 3-1: BAIC/BAIC-exHM (By HLR)

Barring Incoming Call( BAIC,BAIC-exHM)

WSS MSa/PSTNa
Setup ( BS= Speech)

WSS HLRb MSC/VLRb HLRc

GMSC

WSS MSC/VLRc

PSTNc

SRI (msisdn=B, IT=BasicCall, BSG=Telephony) SRI Ack ( callbarred-BAIC/BAIC-exHM) Disconnect/Release /Release Complete
Facility (Invoke = NotifySS (SS-Code, SS-Status))

Subscriber B has BAIC/BAIC-exHM activated

GMSC must release the call If no Call barring, call set up as normal to MS

If no call barring, call set up as normal to Fix

3BL76551AAAADSZZA

EDITION 02

En

11/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

3BL76551AAAADSZZA

EDITION 02

En

12/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

3.2 Call Barring on VMSC/VLR

3.2.1 Barring of Outgoing Voice Calls The condition shall detected on VMSC/VLR in case of: Barring of all outgoing calls, except emergency calls or specific dialed number defined by operator, or calling partys OSSS code or O-CSI trigger. Barring of outgoing international calls Barring of all outgoing international calls except those directed to the home PLMN country

Figure 3-2: Barring Outgoing Call (without call barring inhibition)

Barring Outgoing Call (BOC,BOIC,BOIC-exHC)

WSS MS
Setup ( BS= Speech)

MSC/VLR

MSb

HLRc

WSS MSC/VLRc

PSTNc

MSC/VLR detects BOC,BOIC,BOICexHM to reject call..

Disconnect/Release/Release Complete
Facility (Invoke = NotifySS (SS-Code, SS-Status))

If No Barring Outgoing Call, Call setup as normal to MS

If No Barring Outgoing Call, Call setup as normal to Fix

For outgoing call, the barring decision is determined by the MSC/VLR. The MSC performs the following on outgoing call barring: If call barring condition on BAOC,BOIC,BOIC-exHM, then release the call with cause Notification to Calling Party that Barring of outgoing call is active. If the call is emergency call, call setup as normal. If no barring to call, call setup as normal to MS or fix.

3BL76551AAAADSZZA

EDITION 02

En

13/29


All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Generate CDR on MSC based on the outgoing call.

3.2.2 Special Barring Procedures for SMS-MO For SMS-MO calls, the same barring procedures apply as in 3.2.1. The definition of the destination of an SMS-MO call is a bit special however. Atrium uses the SMS centre number as destination of the SMS-MO call. This is due to the fact, that the SMSC number is received in the CP_DATA message as destination of the SMS call. The final destination of the call, which is contained in the SMS message buffer, is transparent for Atrium. Provided, that a user establishes an SMS-MO call using his default SMSC number, i.e. the one from his HPLMN, this results in the following behavior: 1. BOIC - If the user is in his home country (MSC has same CC as SMSC), then the user can send SMS to all destinations, including international destinations. - If the user is roaming from a foreign country (MSC has different CC than users SMSC) then user cannot send SMS at all. 2. BOIC exHPLMN - The user can send SMS to all destinations, independent of whether he is in his home country or roaming from a foreign country, because the barring check is done against his SMSC number. This behavior is in line with the SMS-MO barring procedure of Evolium LM.

3.3 MSC and VLR transmit CB SS Control Messages to HLR

Once CB supplementary service has been provisioned in HLR, a Mobile Subscriber can initiate the control procedures from mobile handset to HLR to update the Call Barring Subscription information: When a supplementary control procedure is initiated by a Mobile Subscriber from MS, a message (DTAP protocol) is sent to the MSC with the information necessary to perform the procedure. This information consists of: the nature of the procedure Registration/Activation/Erase/Deactivation. the type of the S.S. (e.g. Barring incoming, Barring outgoing) and other relevant data (e.g. password..) MSC/VLR relays the message to HLR. The result of the operation is given by the specific S.S. function involved in the S.S. handling function, which sends it back from HLR to MSC/VLR, and finally from MSC/VLR to the Mobile Station. (message of the DTAP protocol). Atrium MSC/VLR shall transmit message regarding initiation of CB control procedure in HLR: RegisterSS ActivateSS DeactiveSS InterrogateSS The VLR shall update supplementary service information upon receiving the Insert_Subscriber_Data and Delete_Subscriber_Data message. Please refer to Section 2.3 for message flow.

3.4 Call Barring Data in VLR DB

Mobile Subscriber data related to Call Barring supplementary services are stored in the HLR. Updating of the VLR is immediately done if the mobile is registered in a VLR or later at updating location.

3BL76551AAAADSZZA

EDITION 02

En

14/29

No information is transferred from HLR to VLR for the incoming calls barring program.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

VLR shall support CB supplementary service Subscription data from HLR via following messages: 1. insert_subscriber_data 2. delete_subscriber_data VLR shall support VMSC query VLR DB to get CB related information. VLR Shall stores the activation status for barring of outgoing calls. In phase 1, VLR stores the activation status also for barring of incoming calls. In phase 2 VLR, no information is stored in the VLR in case of barring of incoming calls.

3BL76551AAAADSZZA

EDITION 02

En

15/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

CALL BARRING SPECIAL TREATMENT

4.1 Call Barring Notification by Announcement

This notification feature is Atrium specific to call treatment by announcement. This feature is independent from the notification subscribed in HLR. Atrium WSS supports MSC feature treatment by configurable announcement or tone upon call event or error event on VMSC. The configuration items for this feature are as followings: Event Specifies the feature event that requires an announcement treatment: Invoke Fail Invoke Success Deactivate Fail Deactivate Success Activate Fail Activate Success Erase Fail Erase Success Registration Fail Registration Success Default treatment Tone ID - Specified the tone ID, Max 10 digit integer. SS code two digit integers which compliance to SS code in the standard. The selection of supported CF supplementary service: ALL BARRING=144, BARRING OUTGOING CALL =145, BAOC=146, BOIC=147, BOIC EXHC=148, BARRING INCOMING CALL=153, BAIC=154, BIC ROAM= 155,

Step N treatment - Upon to 5 items can be taken for one chosen event. Each step treatment can be type of announcement, tone or no treatment. The sound files of announcement and tone shall be provided. Call forwarding notification announcement to calling party shall be utilized when configuring call treatment on invoke CF success. For example:

3BL76551AAAADSZZA

EDITION 02

En

16/29

Event Invoke success

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Tone ID number SS code BAIC, Step 1 treatment announcement. ie. Sound record is The call has been barred. When A calls to B, with announcement configured as above, the A party will hear The call has been barred upon forwarding invoke success.

3BL76551AAAADSZZA

EDITION 02

En

17/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

SYSTEM INTERFACE

Call Barring Service related messages shall be supported in the following system interfaces.

5.1 MAP interface on GMSC- HLR

Refer to 3GPP 29.002. The Gateway MSC server must interrogate the HLR of the required subscriber to obtain routing information for a call or a short message directed to that subscriber. o SRI
Request M M M M C C C C C C C C C C C C C C C C C C C C C C C C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) C C C C Confirm M(=) C(=) C(=) C(=) C(=)

Parameter name Invoke Id Interrogation Type GMSC or gsmSCF Address MSISDN OR Interrogation OR Capability CUG Interlock CUG Outgoing Access Number of Forwarding Network Signal Info Supported CAMEL Phases Suppress T-CSI Offered CAMEL 4 CSIs Suppression of Announcement Call Reference Number Forwarding Reason Basic Service Group Basic Service Group 2 Alerting Pattern CCBS Call Supported CCBS Phase Additional Signal Info IST Support Indicator Pre-paging supported Call Diversion Treatment Indicator Long FTN Supported Suppress VT-CSI Suppress Incoming Call Barring gsmSCF Initiated Call Network Signal Info 2 IMSI MSRN Forwarding Data Forwarding Interrogation Required VMSC address ReleaseResourcesSupported GMSC Camel Subscription Info Location Information Subscriber State Basic Service Code CUG Subscription Flag North American Equal Access preferred Carrier Id User error SS-List CCBS Target Keep CCBS Call Indicator IST Alert Timer Number Portability Status

C C C C C C C C C C C U C U C C C U

C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)

3BL76551AAAADSZZA

EDITION 02

En

18/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Parameter name Supported CAMEL Phases in VMSC Offered CAMEL 4 CSIs in VMSC MSRN 2 Forwarding Data 2 SS-List 2 Basic Service Code 2 Allowed Services Unavailability Cause Provider error

Request

Indication

Response C C C C C C C C

Confirm C(=) C(=) C(=) C(=) C(=) C(=) C(=) O

SRI Ack - User (cause) used by call barring: Call Barred

5.2 D interface (VLR- HLR)

HLR sends to the VLR all the data needed to support the service to the mobile subscriber. The HLR then instructs the previous VLR to cancel the location registration of this subscriber. Exchanges of data may occur when the mobile subscriber requires a particular service, when he wants to change some data attached to his subscription or when some parameters of the subscription are modified by administrative means. Refer to 3GPP 29.002. Message type: Insert Subscriber Data
Request M C C C C C C C C C C C C C C C C C C C C C C U C C C Indication M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

Parameter name Invoke Id IMSI MSISDN Category Subscriber Status Bearer service List Teleservice List Forwarding information List Call barring information List CUG information List SS-Data List eMLPP Subscription Data MC-Subscription Data Operator Determined Barring General data Operator Determined Barring HPLMN data Roaming Restriction Due To Unsupported Feature Regional Subscription Data VLR CAMEL Subscription Info Voice Broadcast Data Voice Group Call Data Network access mode GPRS Subscription Data Roaming Restricted In SGSN Due To Unsupported Feature North American Equal Access preferred Carrier Id List SGSN CAMEL Subscription Info LSA Information IST Alert Timer

C C

C(=) C(=)

C(=)

3BL76551AAAADSZZA

EDITION 02

En

19/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Parameter name SS-Code List LMU Identifier LCS Information CS Allocation/Retention priority Super-Charger Supported In HLR Subscribed Charging Characteristics Access Restriction Data Regional Subscription Response Supported CAMEL Phases Offered CAMEL 4 CSIs User error Provider error

Request C C C C C C

Indication C(=) C(=) C(=) C(=) C(=) C(=)

Response C

Confirm C(=)

C C C U

C(=) C (=) C (=) C(=) O

Note: Call barring information List includes a list of extensible call barring information parameters: SS-code, Basic Service Group, SS-Status. Delete Subscriber Data
Parameter name Invoke Id IMSI Basic service List SS-Code List Roaming Restriction Due To Unsupported Feature Camel Subscription Info Withdraw Specific CSI Withdraw Regional Subscription Data VBS Group Indication VGCS Group Indication GPRS Subscription Data Withdraw Roaming Restricted In SGSN Due To Unsupported Feature LSA Information Withdraw IST Information Withdraw Regional Subscription Response GMLC List Withdraw Subscribed Charging Characteristics Withdraw User error Request M M C C C C C C C C C C C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C C(=) C(=) C C(=) C(=) Response M(=) Confirm M(=)

Register SS
Parameter name Invoke id SS-Code Basic service Forwarded-to number with subaddress No reply condition time EMLPP default priority Long FTN Supported NbrUser Forwarding information User error Provider error Request M M C C C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C C C C

C(=) C(=) C(=) C(=) O

Deactivate SS, Erase SS

Parameter name Invoke id SS-Code Basic service Forwarding information Request M M C Indication M(=) M(=) C(=) Response M(=) Confirm M(=)

C(=)

3BL76551AAAADSZZA

EDITION 02

En

20/29

User error Provider error

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

C(=) O

Activate SS
Parameter name Invoke id SS-Code Long FTN Supported Basic service Forwarding information Call barring information SS-Data User error Provider error Request M M C C Indication M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)

C C C C

C(=) C(=) C(=) C(=) O

Interrogate SS
Parameter name Invoke id SS-Code Basic service Long FTN Supported SS-Status Basic service Group LIST Request M M C C Indication M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)

C C

C(=) C(=)

5.3 B Interface (VMSC- VLR)

Atrium WSS is VMSC/VLR combination, the message between VMSC-VLR is internal and proprietary.

3BL76551AAAADSZZA

EDITION 02

En

21/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

INTERACTION WITH OTHER FEATURES

6.1 Interaction between Barring of Incoming Call

In case 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. This interaction is handled by the SS control procedure on HLR at activation/deactivation. WSS relays a positive result or an error to MS.

6.2

Operator Determined Call Barring (ODB)

ODB takes precedence over Call Barring. The interaction between Operator Determined Barring and the Call Barring supplementary service is specified in 3GPP TS 22.041. In order to meet the service requirement, the checks of a call request in the HLR (for incoming calls) or VLR (for outgoing calls) against the Operator Determined Barring programme shall be carried out before the checks for the Call Barring supplementary service. If a call is barred due to both Operator Determined Barring and Subscriber Controlled Barring, then the message or notification returned towards the caller will be the same as if the barring was due solely to Operator Determined Barring. When the serving VLR/SGSN does not support call barring, the HLR/HSS may pass to the VLR/SGSN ODB data to bar outgoing circuit switched call or/and MO SMS.

6.3 Call Forwarding

Principles for interaction with the Barring of Outgoing Calls supplementary services. Numbers allowed to call according to the Barring of Outgoing call service condition are allowed as forwarded-to numbers for the served mobile subscriber. Numbers not allowed to call according to the Barring of Outgoing call service condition are not allowed as forwarded-to numbers for the served mobile subscriber. For Unconditional Call Forwarding the forwarded leg is treated as an outgoing call from the HPLMN country. For the Conditional Call Forwarding services the forwarded leg is treated as an outgoing call from the LPLMN (HPLMN or VPLMN) country. Principles for interaction with the Barring of Incoming Calls supplementary services. When Barring of all incoming calls is active for the served mobile subscriber - no Call forwarding services are allowed for her. When Barring of all incoming calls when roaming outside the HPLMN country is active and operative - i.e. the served mobile subscriber is roaming outside the HPLMN country, the Conditional Call Forwarding services are not allowed. On VMSC/VLR, Call Barring services shall take precedence over Call Forwarding service when VLR making routing decision. On HLR, the Call Forwarding control procedure is invoked when MS or operator Registration or Activation Call Forwarding when call barring service is active. FTN and service activation status will be examined against call barring services in the followings: Barring of all outgoing call: Barring of outgoing international call: Barring of outgoing international call except those directed to the HPLMN country: 3BL76551AAAADSZZA EDITION 02 En 22/29

Barring of incoming call: Barring of incoming call when roaming outside the HPLMN country:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

FTN and service activation status will be examined against ODB services in the followings: Barring of all outgoing call: Barring of outgoing international call: Barring of outgoing international call except those directed to the HPLMN country: Barring of incoming call: Barring of incoming call when roaming outside the HPLMN country: Barring of outgoing inter-zone calls: Barring of registration of any forwarded-to number: Barring of registration of any international forwarded-to number : Barring of registration of any international forwarded-to number except a number within the HPLMN country : Barring of registration of any inter-zones forwarded-to number : For example: If Barring of all outgoing call service is active, a "Registration" or an "Activation" request for C.F. Unconditional service or a Conditional C.F. service shall be denied. The MS shall be notified. The execution of control procedure is transparent to VLR. The result of Call Forwarding Registration and Activation shall be transferred from HLR to VLR.

6.4 CUG Closed User Group

The call restriction Supplementary Services(CB, ODB), when active and operative, takes precedence over the CUG restrictions. The activation of a call restriction Supplementary Service does not affect any current CUG call.

3BL76551AAAADSZZA

EDITION 02

En

23/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

CALL BARRING CHARGING (BILLING)

MSC shall generate the CDR for the barring call with the following information: Call Barring flavor (i.e. BAIC,BOC, ) in Supplementary Service Used

Refer to Spatial CDR format document for details. A CDR shall be generated on GMSC for in case of outgoing call barring: A CDR shall be generated on VMSC for in case of incoming call barring: Field Served IMSI Served IMEI Served MSISDN Description IMSI of the forwarding Subscriber The IMEI of the subscriber, The MSISDN of the subscriber, provided it is known. Note that for MTC calls this field generally would map to the Called Number in the context of traditional CDRs. Calling Party Number. Proprietary parameter - An indication of the source of the Calling Number. In the case where the connected party is an ISUP origination, this is extracted from the Calling Party Number parameter or the Redirecting Number parameter in the IAM message. In the case where the connected party is a mobile origination, this parameter will generally indicate Network Provided. This field is legitimate only if a Calling Number is present in the CDR. Proprietary parameter - An indication of whether Calling Number presentation is restricted or allowed. In the case where the connected party is an ISUP origination, this is extracted from the Calling Party Number parameter or the Redirecting Number parameter in the IAM message. In the case where the connected party is a mobile origination or aforwarding mobile, this will depend upon whether or not the originator has Calling Line Id restricted either by subscription or on a per-call basis. Please note that the indication of whether or not presentation is restricted or allowed is unaffected by whether or not the terminating subscriber is subscribed to the CLIP service or has CLIR-Override capability. Proprietary parameter 3GPP TS 32.005 parameter 3GPP TS 32.005 parameter 3GPP TS 32.005 parameter Proprietary parameter 3GPP TS 32.005 parameter En 24/29

M C C

Calling Number Screening Indicator

C C

Presentation Indicator

Jurisdiction Information Recording Entity (MSC address) Incoming TKGP (Partial) Outgoing TKGP (Partial) Interconnect Facility First Locations LAC and CellID 3BL76551AAAADSZZA

C M M C C C

EDITION 02

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Change of Location Basic Service/Transparency Indicator Supplementary Services MS Classmark

C C C C

3GPP TS 32.005 parameter 3GPP TS 32.005 parameter Call Barring This field contains the MS Classmark (Classmark Type 2) actually employed for call setup. This field is not used for MTC calls resulting in a forwarding and subsequent MOC record. 3GPP TS 32.005 parameter (Event time stamps) 3GPP TS 32.005 parameter (Event time stamps) 3GPP TS 32.005 parameter (Event time stamps) 3GPP TS 32.005 parameter This field indicates the speech version used for the call. It is not used for MTC calls that result in call forwarding. This field indicates the channel coding used for the call (if applicable). It is not used for MTC calls that result in call forwarding. This field indicates the reason for the release of the connection, or the fact that the connection is not yet released (partial record case). Call Barring indicated. 3GPP TS 32.005 parameter 3GPP TS 32.005 parameter 3GPP TS 32.005 parameter (Event time stamps) Proprietary parameter-This is an index of the destination call type for the last translated number defined by a Customer (or Service Provider) on the Number Translation GUI (WEM). This info can identify the type (National, International, Long Distance, National Operator, etc.) of a call. 3GPP TS 32.005 parameter In cases where the MTC results in a forwarding attempt captured in a subsequent MOC, this field will not be used ,the outgoing trunk group is part of another call and will be captured in the MOC-CF associated with that call. This field indicates whether the Originating or Terminating side that caused the call to end. The Cause Value is available in the next field. Proprietary parameter - This field indicates Alcatels Internal Cause Code Value that can help identify the reason for the termination of the call. These fields indicate the Mobile Country Code and Mobile Network Code of the first

Traffic Channel Seizure Time Answer Time Traffic Channel Release Time Radio Channel Used Speech Version Used/CTM Indication

C C C C C

Channel Coding Used

Cause for Termination

Sequence Number (Partial Record) Call Reference Time Offset Destination Call Type

C M C C

Incoming TKGP (Rest) Outgoing TKGP (Rest)

C C

Disconnecting Party

Diagnostics

First Locations MCC and MNC

3BL76551AAAADSZZA

EDITION 02

En

25/29

location from where the call was originated.

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Last Location

This field indicates MCC, MNC, LAC and Cell Identity of the location from where the call got terminated finally. This field may be the same as the first location if the subscriber had not moved or returned back to the same location during termination.

Note: There are no new or modified fields in this record type in Revision 3.0 of this document.

3BL76551AAAADSZZA

EDITION 02

En

26/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

MEASUREMENT (PEG COUNTERS AND KPI)

The system shall peg Operation Measurements (OM) based on the following criteria for CB invocation: Call reject peg counters:
Number of incoming call-attempts that were rejected due to call barring or other service restrictions. Number of outgoing call-attempts that were rejected by the call terminating switch due to call barring or other service restrictions.

INCOMINGREJECTED OUTGOINGREJECTED

Peg Supplementary service Registration, Activation..

ACTIVATIONATTEMPT ACTIVATIONSUCCESS DEACTIVATIONATTEMPT DEACTIVATIONSUCCESS REGISTRATTEMPT REGISTRSUCCESS DEREGISTRATTEMPT DEREGISTRSUCCESS Number of SS feature activation attempts. Number of SS feature activation succeeded. 1 Number of SS feature de-activation attempts. Number of SS feature de-activation succeeded. Number of SS feature Registration attempts. Number of SS feature Registration succeeded. 2 Number of SS feature de-registration attempts. Number of SS feature de-registration succeeded.

KPI for success rate on SS Registration/Activation The supplementary services success rate is derived using performance statistics from the CISSPERF group. This KPI is applicable to both GSM and UMTS networks. The KPI can be implemented in a performance server. ACTIVATION SUCCESS SSActivati onSuccessR ate = 100 * ACTIVATIONA TTEMPT

DEACTIVATI ONSUCCESS SSDeactiva tionSucces sRate = 100 * DEACTIVATIONA TTEMPT REGISTRSUC CESS SS Re gistraionS uccessRate = 100 * REGISTRATTE MPT DEREGISTRS UCCESS SSDeregist raionSucce ssRate = 100 * DEREGISTRATTE MPT

Refer to Performance Data Measurements for Operation Administration and Maintenance document for details.

PERFORMANCE AND DIMENSIONING

Adding CB feature to the network shall not impact the networks overall performance.

1 This field name has been changed to DEACTIVATIONATTEMPT from DEACTIVATION 2 This field name has been changed to DEREGISTRATIONATTEMPT from DEREGISTRATION

3BL76551AAAADSZZA

EDITION 02

En

27/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

LIST OF ABBREVIATIONS
Table 1 Abbreviations

CAMEL BAOC BOIC BOIC-exHC BAIC BIC-Roam CFB CFC CFNRc CFNRy CFU CSI FTN GMSC HLR HPLMN IP MAP MS PRBT PLMN PRN RCP SMS SMSC SMS-MO SRI SSF TC

Customized Application for Mobile Enhanced Logic Barring of All Outgoing Calls Barring Outgoing International Calls Barring of Outgoing International Calls EXCEPT those directed to the Home PLMN Country Barring All Incoming Calls Barring of Incoming Calls when Roaming outside the home PLMN country Call Forwarding on Busy Call Forwarding Conditional Call Forwarding on Not Reachable Call Forwarding on No Reply Call Forwarding Unconditional CAMEL Subscriber Information Forwarded-To Number Gateway MSC Home Location Register Home PLMN Internet Protocol Mobile Application Part Mobile Subscriber ( or Station ) Personalized Ring Back Tone Public Land Mobile Network Provide Roaming Number Radio Control Point Short Message Short Message Centre Short Message Mobile Initiated Send Routing Information Service Switch Function Termination Call

3BL76551AAAADSZZA

EDITION 02

En

28/29

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

VLR T-CSI

VMSC

3BL76551AAAADSZZA Visited Location Register Visited MSC Termination CSI

END OF DOCUMENT

EDITION 02

En

29/29