Alcatel-Lucent GSM

Reconfigure BSC/MSC

BSS Document
Reconfiguration Method
Release B11

3BK 17438 0247 RJZZA Ed.07

BLANK PAGE BREAK

Status RELEASED

Short title MPI24 / MDR7

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

2 / 30 3BK 17438 0247 RJZZA Ed.07

 Contents

Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1.1 Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1.2 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1.3 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1.4 Grouped Task Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.2 Site Specific Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.3 External Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3 Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4 Telecom/Supervision Outage and Operating Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.5 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.5.1 Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.5.2 Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.5.3 Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2 Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1 Before Going Onsite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2.1 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2.2 Required Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3 Scenario Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3.1 Initial Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3.2 C1: Activate A-Flex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3.3 C2: Add New MSC (MSC Number 2 to 16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3.4 C3: Delete an MSC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3.5 C4: Split MSC Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3.6 C5: Increase MSC Traffic Preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.3.7 C6: Deactivate A-Flex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.3.8 C7: Re-parent a BSC onto a New MSC Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.3.9 C8: Re-include MSC Server in MSC Pool (Start Loading MSC) . . . . . . . . . . . . . 28
2.3.10 C9: Temporarily Remove MSC Server from MSC Pool (Stop Loading MSC) . . 28
2.3.11 Modify MSC (other Parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.3.12 Final Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.4 Reverse Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3BK 17438 0247 RJZZA Ed.07 3 / 30

Contents

4 / 30 3BK 17438 0247 RJZZA Ed.07

 Preface

Preface
Purpose This document describes how to configure and reconfigure an BSC/MSC.

Document Pertinence It applies to operational BSS from Release B11.

What’s New In Edition 07

The restriction 3BKA20FBR279093 was removed from the following sections:

C3: Delete an MSC Server (Section 2.3.4)

C7: Re-parent a BSC onto a New MSC Pool (Section 2.3.8).

In Edition 06
Improve Modify MSC (other Parameters) (Section 2.3.11) with new parameters’
rules.

In Edition 05
The following sections were updated:

C2: Add New MSC (MSC Number 2 to 16) (Section 2.3.3)

C3: Delete an MSC Server (Section 2.3.4)

C5: Increase MSC Traffic Preference (Section 2.3.6)

C7: Re-parent a BSC onto a New MSC Pool (Section 2.3.8).

In Edition 04
The restriction 3BKA20FBR279093 was introduced in:

C3: Delete an MSC Server (Section 2.3.4)

C7: Re-parent a BSC onto a New MSC Pool (Section 2.3.8).

Add new case for general Modify MSC.

In Edition 03
Editorial improvements.

In Edition 02

3BK 17438 0247 RJZZA Ed.07 5 / 30

Preface

The following sections were improved:

C2: Add New MSC (MSC Number 2 to 16) (Section 2.3.3)

C5: Increase MSC Traffic Preference (Section 2.3.6)

C1: Activate A-Flex (Section 2.3.2)

C3: Delete an MSC Server (Section 2.3.4)

C7: Re-parent a BSC onto a New MSC Pool (Section 2.3.8)

In Edition 01
First official release of the document.

6 / 30 3BK 17438 0247 RJZZA Ed.07

 Preface

Audience This document is intended for:

Field service technicians

Site administrators

Project managers

System support engineers.

Assumed Knowledge You must have a basic understanding of the following:

Planning:
Network architecture and reshuffling principles
Scheduling.

Implementation:
Alcatel-Lucent operations and maintenance (O&M) concepts for the BSS
GPRS concepts
9153 OMC-R operating in Release B11
NGN concepts.

3BK 17438 0247 RJZZA Ed.07 7 / 30

Preface

8 / 30 3BK 17438 0247 RJZZA Ed.07

 1 Overview

1 Overview

This Overview gives information needed by project managers and foremen, for
presentation to the customer and for site planning.

3BK 17438 0247 RJZZA Ed.07 9 / 30

1 Overview

1.1 Presentation
This document describes how to configure and reconfigure an BSC/MSC.
The A-Flex feature requires the A signalling over IP feature.
A-Flex is only implemented in the 9130 BSC Evolution.
Note that the A-Flex feature cannot be used when the Alcatel-Lucent BSS is
connected to a Legacy MSC.
The A-Flex feature provides extended connectivity by enabling a BSCs
to connect to up to 16 MSC servers, therefore enabling more operations
with these MSCs, including:
Creation

Deletion

Reconfiguration.

When A-Flex is applied, one or more MSCs serve a CS pool-area, but only one
of these MSCs serves each individual MS.
One and only one MSC server always controls an A interface circuit.

1.1.1 Cases
The following cases apply:

C1: Activate A-Flex

C2: Create a new MSC (MSC number 2 to 16)

C3: Delete an MSC server

C4: Split an MSC pool

C5: Increase MSC traffic preference

C6: Deactivate A-Flex

C7: Re-parent a BSC onto a new MSC pool

C8: Re-include an MSC server in an MSC pool (start the load of an MSC)

C9: Temporarily remove an MSC server from an MSC pool (stop the load of
an MSC)

C10: Modify MSC (other parameters).

10 / 30 3BK 17438 0247 RJZZA Ed.07

 1 Overview

The folowing figures are added values for cases’ explanation:

MSC1

BSC1 BSC2

Initial State

MSC1 MSCi

BSCi
BSC1 BSC2

Final State
Figure 1: Case C2: Create a New MSC (MSC Number 2 to 16)

MSC1 MSCi

BSCi
BSC1 BSC2

Initial State

MSC1

BSC1 BSC2

Final State
Figure 2: Case C3: Delete an MSCSserver

3BK 17438 0247 RJZZA Ed.07 11 / 30

1 Overview

MSC1 MSCi

BSC1 BSC2 BSCi

Initial State

MSC1 MSCi

BSC1 BSC2 BSCi

Final State
Figure 3: Case C4: Split an MSC Pool

MSC1 MSCi MSCi

BSC1 BSC2 BSCi BSCi

Initial State

MSC1 MSCi MSCi

BSC1 BSC2 BSCi BSCi

Final State
Figure 4: Case C7: Re-parent a BSC onto a New MSC Pool

12 / 30 3BK 17438 0247 RJZZA Ed.07

 1 Overview

1.1.2 Options
None.

1.1.3 Restrictions
None.

1.1.4 Grouped Task Sequence

None.

3BK 17438 0247 RJZZA Ed.07 13 / 30

1 Overview

1.2 Preparation
1.2.1 Prerequisites
The following prerequisites apply:

For C1, C2, C3, C7, the Signalling over IP feature is activated
For C1, C2, if the Media Gateway (MGW) is used, the MGW is cabled

For C2, C4, C5, C7, C8, the A-Flex feature is activated

For C1, the following must apply:

One unique NULL_NRI must be configured for a whole PLMN
For a given BSC, an MSC server has only one Signalling Point Code
(SPC).

1.2.2 Site Specific Information

You must have the following information to complete the scenario:

For C1, C2, C7

When creating a new MSC, you must have the following information:
’TRAFFIC_MODE’
’MSC_SPC’
’MSC_CN_ID’
’MSC_WEIGHT’
’OFFLOADED’
’NRI_LIST’
’NULL_NRI’
’NRI_LENGTH’
’PLMN Name’
’MSC_MCC’
’MSC_MNC’
’MIN_NB_ACTIVE_IPSP’.

When creating a new ASL, the following information is required:

’LOCAL_ASIG_SCTP_ENDPOINT_PORT’
’ASIG_SCTP_ENDPOINT_IP_Address_1’
’ASIG_SCTP_ENDPOINT_IP_Address_2’
’ASIG_SCTP_ENDPOINT_PORT’

For C3, C7, C6, when deleting one MSC, the MSC SBL number is required

For C5, the MSC_WEIGHT is required.

14 / 30 3BK 17438 0247 RJZZA Ed.07

 1 Overview

1.2.3 External Tasks

Ensure that the required external tasks are performed at the MSC site.

3BK 17438 0247 RJZZA Ed.07 15 / 30

1 Overview

1.3 Scheduling

Time based on technical constraints

The number of resources shown in the following table does not take into
account individual customer or safety requirements.

Grouped Task Site / Resource Time/Task

Initial Checks OMC-R 35 min.

C1: Activate A-Flex OMC-R 9 min.

C2: Create a New MSC (MSC number 2 to 16) OMC-R 4 min. + 9 min./MSC + 5
min./Ater Mux

C3: Delete an MSC Server OMC-R 7 min. + 10 min./Ater Mux

C4: Split an MSC Pool OMC-R 20 min./MSC

C5: Increase MSC Traffic Preference OMC-R 2 min.

C6: Deactivate A-Flex OMC-R 2 min. + ( 11 min. + 15 min./Ater

Mux ) / MSC

C7: Re-parent a BSC onto a New MSC Pool OMC-R 14 min. + 10 min./Ater Mux

C8: Re-include an MSC Server in an MSC Pool OMC-R 2 min.

(Start of the Load of an MSC)

C9: Temporarily Remove an MSC Server from an OMC-R 2 min.

MSC Pool (Stop of the Load of an MSC)

C10: Modify MSC (other parameters) OMC-R 2 min.

Final Checks OMC-R 30 min.

TOTAL TIME Total time, depending on the cases:

C1: 1h 14 min.

C2: 1h 9 min. + 9 min./MSC + 5 min./ Ater Mux

C3: 1h 12 min. + 10 min. / Ater Mux

C4: 1h 5 min. + 20 min./MSC

C5: 2 min.

C6: 1h 7 min. + ( 11 min. + 15 min./Ater Mux

) / MSC

C7: 1h 19 min. + 10 min./Ater Mux

C8: 1h 7 min.

C9: 1h 7 min.

C10: 1h 7 min.

16 / 30 3BK 17438 0247 RJZZA Ed.07

 1 Overview

ope. : OMC-R operator

com. : Commissioning Team

3BK 17438 0247 RJZZA Ed.07 17 / 30

1 Overview

1.4 Telecom/Supervision Outage and Operating Impact

The following table describes the traffic outage and loss of supervision caused
by each grouped task.

Out. Ref. Grouped Task Reduction / Impacts ...

Initial Checks None.

Reduction 1 C1: Activate A-Flex 9 min.

Reduction 2 C2: Create a New MSC (MSC number 2 4 min. + 2 min./MSC + 5 min. / Ater
to 16) Mux

Reduction 3 C3: Delete an MSC Server 6 min. + 10 min./Ater Mux

Reduction 4 C4: Split an MSC Pool None.

C5: Increase MSC Traffic Preference None.

Reduction 6 C6: Deactivate A-Flex 2 min. + ( 11 min. + 15 min./Ater Mux

) / MSC

Reduction 7 C7: Re-parent a BSC onto a New MSC 14 min. + 10 min./Ater Mux
Pool

Reduction 8 C8: Re-include an MSC Server in an MSC None.

Pool (Start of the Load of an MSC)

Reduction 9 C9: Temporarily Remove an MSC Server None.

from an MSC Pool (Stop of the Load of
an MSC)

C10: Modify MSC (Other parameters) None.

Final Checks None.

18 / 30 3BK 17438 0247 RJZZA Ed.07

 1 Overview

1.5 Resources
1.5.1 Tools
1.5.1.1 Hardware Tools
None.
1.5.1.2 Software Tools

Item Use at

Customer documentation CD with the version associated to the current document OMC-R
edition. Note that the document you are reading cannot be used as a paper version.
It is online documentation using hypertext links which take you to other parts of a
document on the same CD-ROM. All words in italics are hypertext links.

1.5.1.3 Forms
None.

3BK 17438 0247 RJZZA Ed.07 19 / 30

1 Overview

1.5.2 Supplies

Item Contents Use at

Site Documentation. - OMC-R

Topology regarding operation. Must be provided by customer. OMC-R

1.5.3 Applicable Documents

You must have the following documents or have electronic access to the
following documents:

BSS Methods Handbook

BSS Configuration Handbook

BSS Surveillance Handbook

Network Reconfiguration Recommendations.

20 / 30 3BK 17438 0247 RJZZA Ed.07

 2 Scenario

2 Scenario

This Scenario presents all checks needed before beginning the scenario, and
all detailed tasks to be performed on each site.

3BK 17438 0247 RJZZA Ed.07 21 / 30

2 Scenario

2.1 Before Going Onsite

Before going onsite, you must check that the following information and supplies
are available:

All Prerequisites (Section 1.2.1) are met

The customer is informed of the:

Date and time
Site name and address
Purpose of operation.

Personnel are available and ready for operation; refer to Scheduling

(Section 1.3)

Site Specific Information (Section 1.2.2) is available

Tools (Section 1.5.1) are available and ready for operation

Supplies (Section 1.5.2) are available and ready for operation

Applicable Documents (Section 1.5.3) are available.

Ensure that the technical release level of the delivered board is in accordance
with the BSS hardware technical release document.
Ensure that the method used at the BSS site is at the same level as at the
OMC-R.

2.2 Before You Start

2.2.1 Checks
Perform the following operations:

Check that all Prerequisites (Section 1.2.1) are met

Check the availability of all necessary Tools (Section 1.5.1) and Supplies
(Section 1.5.2)

Inform the operator.

Among the Cases (Section 1.1.1) and Options (Section 1.1.2), identify which
cases and options apply to you.

22 / 30 3BK 17438 0247 RJZZA Ed.07

 2 Scenario

2.2.2 Required Knowledge

You must be familiar with the following:

Safety Rules and Precautions

Telecom/Supervision Outage and Operating Impact (Section 1.4)

Reverse Procedure
Grouped Task Sequence (Section 1.1.4)

Operating Hints

How to document Faults and Anomalies.

2.3 Scenario Description

This section describes how to configure the MSC.

2.3.1 Initial Checks

Note Task Description Site Time/Task Reduction

CHECK Perform an Audit Alarm State on the BSS. OMC-R 5 min. None.

CHECK Perform BSC/BSS Logical Audit on the BSS. OMC-R 10 min. None.

CHECK Perform an Audit BSS Hardware on the BSS. OMC-R 10 min. None.

CHECK View Status of Managed Objects and Alarms (BSS, OMC-R 10 min. None.
ASL) and print them.

3BK 17438 0247 RJZZA Ed.07 23 / 30

2 Scenario

2.3.2 C1: Activate A-Flex

Note Task Description Site Time/Task Reduction

C1 Lock the Aters configured for the MSC to be modified, OMC-R 2 min. Reduction
using Lock Traffic on One Ater. 1.

C1 Activate A-Flex OMC-R 5 min. Reduction

1.

The correspondent parameters are:

Set the NULL_NRI parameter. The operator must check that the NULL_NRI parameter is
common inside all the BSSs of one PLMN.
Set the NRI_LENGTH parameter to a value greater than ’0’

Set the MSC_CN_ID parameter. All the MSCs connected to one BSC must have different
MSC_CN_ID. The default value is ’None’.

Set the NRI_LIST values (up to 8 values). If the operator inserts less than eight values, the
remaining fields must be empty. The NRI_LIST must not contain NULL_NRI.

C1 Unlock the Ater, using Unlock Traffic on One Ater. OMC-R 2 min. Reduction
1.

2.3.3 C2: Add New MSC (MSC Number 2 to 16)

Note Task Description Site Time/Task Reduction

C2 For the concerned BSC, Add an MSC. OMC-R 7 min. /MSC None.

C2 Lock the Aters configured for the MSC to be OMC-R 2 min. Reduction 2.
modified, using Lock Traffic on One Ater.

C2 For the selected A-Trunk of the Aters configured for OMC-R 2 min. /MSC Reduction 2.
the MSC to be modified, Modify MSC Number.

C2 Connect the A interface to the added MSC. MSC 5 min. /Ater Reduction 2.
Mux

C2 Unlock all ASLs for the new added MSCs, using OMC-R 1 min. Reduction 2.
Unlock ASL.

C2 Unlock the Ater, using Unlock Traffic on One Ater. OMC-R 2 min. Reduction 2.

24 / 30 3BK 17438 0247 RJZZA Ed.07

 2 Scenario

2.3.4 C3: Delete an MSC Server

Note Task Description Site Time/Task Reduction

C3 Lock the Aters configured for the MSC to be deleted, OMC-R 2 min. Reduction 3.
using Lock Traffic on One Ater.

C3 Lock all ASLs for the MSC to be deleted using Lock OMC-R 1 min. Reduction 3.
ASL. The established SCTP association between BSC
and MSC is shutdown. The ASL SBL is in the OPR
state.

C3 Modify MSC Number. OMC-R 2 min. Reduction 3.

Note: Each A-Trunk linked to the MSC to be removed should be moved to a remaining MSC or
set to ’0’.

C3 For the concerned BSC, Remove an MSC. OMC-R 2 min. Reduction 3.

C3 Disconnect the A interface between the BSC and the MSC 5 min. Reduction 3.
deleted MSC. /Ater Mux

C3 If necessary, reconnect links to the remaining MSCs. MSC 5 min. Reduction 3.

/Ater Mux

C3 Unlock the Ater. Use Unlock Traffic on One Ater. OMC-R 2 min. Reduction 3.

2.3.5 C4: Split MSC Pool

An MSC pool associated with two BSCs is split into two MSC pools. Each one
is associated with one BSC.

Note Task Description Site Time/Task Reduction

C4 For each MSC server to remove on BSC 1, use C3: OMC-R 10 min. None.
Delete an MSC Server (Section 2.3.4). /MSC

C4 For each MSC server to remove on BSC 2, use C3: OMC-R 10 min. None.
Delete an MSC Server (Section 2.3.4). /MSC

3BK 17438 0247 RJZZA Ed.07 25 / 30

2 Scenario

2.3.6 C5: Increase MSC Traffic Preference

If the MSC weight is increased, the number of A-trunks connected to that
MSC may also need to be increased.

Note Task Description Site Time/Task Reduction

C5 Modify MSC by modifying the ’MSC Weight’ MSC OMC-R 2 min. None.
application parameter.

2.3.7 C6: Deactivate A-Flex

Note Task Description Site Time/Task Reduction

C6 Repeat C3: Delete an MSC Server (Section 2.3.4) for OMC-R 10 min. Reduction 6
the all MSC, except the last one. /MSC

Note: During this task, the A-Trunk linked to the MSC to be removed, must be re-parented to
the remaining MSC, which sustains the A Signalling over IP. The MSC Number is in
the A Interface Circuit Panel. If the last MSC capacity is overloaded, the A-Trunk MSC
Number must be set to ’0’.
All A interface linked to the MSC to be removed must be disconnected from their MSC and
reconnected to the last MSC, unless its capacity is not overloaded.

C6 Deactivate A-Flex. OMC-R 2 min. Outage 6

2.3.8 C7: Re-parent a BSC onto a New MSC Pool

This section describes how to remove all MSC servers of the old pool and
add new MSC servers to the new pool. Perform all the tasks for each MSC
one by one.

Note Task Description Site Time/Task Reduction

C7 Lock the Aters configured for the MSC to be deleted, using OMC-R 2 min. Reduction
Lock Traffic on One Ater. 7.

C7 Lock all ASLs for the MSC to be deleted using Lock ASL. The OMC-R 1 min. Reduction
established SCTP association between BSC and MSC is 7.
shutdown. The ASL SBL is in the OPR state.

C7 Modify MSC Number. OMC-R 2 min. Reduction

7.

Note: Each A-Trunk linked to the MSC to be removed should be moved to a remaining MSC or
set to ’0’.

C7 For each MSC server of the old MSC pool, Remove an MSC. OMC-R 2 min. Reduction
7.

C7 For each MSC server of the new MSC pool, Add an MSC. OMC-R 2 min. Reduction
7.

26 / 30 3BK 17438 0247 RJZZA Ed.07

 2 Scenario

Note Task Description Site Time/Task Reduction

C7 For the selected A-Trunk, Modify MSC Number. OMC-R 2 min. Reduction
7.

C7 Disconnect the A interface between the BSC and the required BSC 5 min. Reduction
MSC. /Ater 7.
Mux

C7 Reconnect links to the MSCs from the new MSC Pool. BSC 5 min. Reduction
/Ater 7.
Mux

C7 Unlock all ASLs for the MSC to be modified, using Unlock OMC-R 1 min. Reduction
ASL. 7.

C7 Unlock the Aters, using Unlock Traffic on One Ater. OMC-R 2 min. Reduction
7.

3BK 17438 0247 RJZZA Ed.07 27 / 30

2 Scenario

2.3.9 C8: Re-include MSC Server in MSC Pool (Start Loading MSC)
If an MSC server is in high load situation, the operator can avoid the MSC
entering an overload situation by starting the load of an MSC.

Note Task Description Site Time/Task Reduction

C8 Modify MSC by modifying the MSC application parameter OMC-R 2 min. None.
(’mscloadstatus’) to ’onloaded’. The selected MSC server is
included in the load balancing function (i.e. included from the
load sharing between MSCs).

2.3.10 C9: Temporarily Remove MSC Server from MSC Pool (Stop
Loading MSC)
The operator can decide to re-include/include an MSC server in an MSC pool
by stopping the loading of an MSC.

Note Task Description Site Time/Task Reduction

C9 Modify MSC by modifying the MSC application parameter OMC-R 2 min. None.
(’mscloadstatus’) to ’offloaded’. The selected MSC server is
excluded from the load balancing function (i.e.excluded in the
load sharing between MSC).

2.3.11 Modify MSC (other Parameters)

Note Task Description Site Time/Task Reduction

C10 Before the next task Modify MSC for the following OMC-R 2 min. None.
parameters ’TRAFFIC_MODE’, ’MSC_SPC’ and
’MIN_NB_ACTIVE_IPSP’ do:

Set MSC application parameter (’mscloadstatus’) to

’offloaded’
Lock ASL

Lock BSS Traffic.

28 / 30 3BK 17438 0247 RJZZA Ed.07

 2 Scenario

Note Task Description Site Time/Task Reduction

C10 Modify MSC by modifying the MSC application parameters OMC-R 2 min. None.
’TRAFFIC_MODE’

’MSC_SPC’

’MSC_CN_ID’

’MSC_WEIGHT’

’OFFLOADED’
’NRI_LIST’

’MIN_NB_ACTIVE_IPSP’

’NRI_LENGTH’

’NULL_NRI’.

C10 If the following parameters ’TRAFFIC_MODE’, ’MSC_SPC’ OMC-R 2 min. None.

and ’MIN_NB_ACTIVE_IPSP’ were modifyed with Modify
MSC do:

Unlock BSS Traffic

Unlock ASL

Set MSC application parameter (’mscloadstatus’) to

’onloaded’.

2.3.12 Final Checks

Note Task Description Site Time/Task Reduction

CHECK Perform an Audit Alarm State on the BSS and compare alarms OMC-R 10 min. None.
and states with those generated during the Initial Checks
(Section 2.3.1).

CHECK Perform Audit BSS Hardware on the BSS. OMC-R 10 min. None.

CHECK View Status of Managed Objects and Alarms (BSS) and OMC-R 10 min. None.
compare with the printed values from the Initial Checks
(Section 2.3.1).

3BK 17438 0247 RJZZA Ed.07 29 / 30

2 Scenario

2.4 Reverse Procedure

Use this procedure to reverse the network modifications described in this
scenario if checks failed.
The reverse procedure to apply depends on the modifications that were
performed:

If C1 was performed with a failure, perform C6 to switch back

If C2 was performed with a failure, perform C3 to switch back

If C3 was performed with a failure, perform C2 to switch back

If C4 was performed with a failure, perform C7 to switch back

If C5 was performed with a failure, perform C5 with the initial values
to switch back

If C6 was performed with a failure, perform C1 to switch back

If C7 was performed with a failure, perform C7 by switching the old pool
with the new pool

If C8 was performed with a failure, perform C9 to switch back

If C9 was performed with a failure, perform C8 to switch back.

30 / 30 3BK 17438 0247 RJZZA Ed.07