MSC Pool User Manual

HUAWEI MSOFTX3000 Mobile Softswitch Center
V100R006C05
MSC Pool User Manual
Issue
02
Date
2008-04-10
Part Number
00400181
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Copyright Huawei Technologies Co., Ltd. 2008. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.


Contents
Contents
About This Document.....................................................................................................................1
1 Overview......................................................................................................................................1-1
1.1 Introduction.....................................................................................................................................................1-2
1.2 Concept............................................................................................................................................................1-2
1.3 Technical Principle..........................................................................................................................................1-6
1.3.1 Load Balancing......................................................................................................................................1-7
1.3.2 Handover................................................................................................................................................1-8
1.3.3 Disaster Tolerance..................................................................................................................................1-8
1.3.4 Paging Control......................................................................................................................................1-14
1.3.5 Location Update with Gs Interface......................................................................................................1-14
1.3.6 Subscriber Migration Between MSCs..................................................................................................1-14
1.3.7 Load Balancing at the MGW...............................................................................................................1-17
1.3.8 A-Flex Function Proxy on the MGW...................................................................................................1-18
1.3.9 MGW Managing Circuits of the A Interface........................................................................................1-22
1.3.10 Charging Principle..............................................................................................................................1-24
1.4 M2000 Application in the MSC Pool............................................................................................................1-26
1.4.1 M2000 Function...................................................................................................................................1-26
1.4.2 M2000 Application Scenario...............................................................................................................1-27
2 Networking Description...........................................................................................................2-1
2.1 Signaling Networking Scheme of an MSC Pool (BSC/RNC Providing the A-Flex/Iu-Flex Function).........2-2
2.1.1 TDM-Based A Interface.........................................................................................................................2-2
2.1.2 ATM-Based Iu Interface........................................................................................................................2-3
2.2 Signaling Networking Scheme of an MSC Pool (MGW Providing the A-Flex Function).............................2-4
2.3 Networking Scheme for Connecting CN NEs Inside and Outside an MSC Pool...........................................2-4
2.4 Networking Scheme for Subscriber Data Backup...........................................................................................2-5
2.5 Networking Scheme for Voice Channels Related to an MSC Pool................................................................2-5
3 MSC Pool Network Planning..................................................................................................3-1

3.1 Limitations......................................................................................................................................................3-2
3.2 MSC Pool Network Specifications.................................................................................................................3-2
3.3 General Principles of the MSC Pool Planning................................................................................................3-4
4 Commands and Parameters Related to MSC Pool...............................................................4-1

4.1 Commands Used on the MSC Server..............................................................................................................4-2
Issue 02 (2008-04-10)

Contents

4.2 Commands Used on the MGW.......................................................................................................................4-4

4.3 Global Data and Software Parameters.............................................................................................................4-5
5 New MSC Pool in the 2G Network........................................................................................ 5-1

5.1 New Target Network Description...................................................................................................................5-2
5.2 Data Configuration Flow.................................................................................................................................5-4
5.3 Data Planning..................................................................................................................................................5-5
5.4 Data Configuration..........................................................................................................................................5-9
5.4.1 Configuring the Basic Data of NEs........................................................................................................5-9
5.4.2 Presetting Data for the MSC Pool..........................................................................................................5-9
5.4.3 Building an MSC Pool in the Core Network........................................................................................5-15
5.4.4 Integration with the Access Network...................................................................................................5-21
5.5 Other Data Configuration..............................................................................................................................5-24
5.6 System Commissioning.................................................................................................................................5-30
6 2G Network Evolution to Support MSC Pool......................................................................6-1

6.1 Evolution Scenario..........................................................................................................................................6-2
6.1.1 Description of the Existing Network......................................................................................................6-2
6.1.2 Description of the Target Network.........................................................................................................6-3
6.2.1 Data Planning.........................................................................................................................................6-6
6.3 Evolution of the Core Network.......................................................................................................................6-9
6.3.1 Overview................................................................................................................................................6-9
6.3.2 Making MSC Server 1 and MGW 1 as an MSC Pool..........................................................................6-10
6.3.3 Adding MSC Server 2 into the MSC Pool...........................................................................................6-12
6.3.4 Adding MGW 2 into the MSC Pool.....................................................................................................6-16
6.3.5 Adding MSC Server 3 into the MSC Pool...........................................................................................6-19
6.3.6 Adding MGW 3 into the MSC Pool.....................................................................................................6-24
6.4 Integration with the Access Network............................................................................................................6-30
6.4.1 Adding BSC 1 into the MSC Pool.......................................................................................................6-30
6.4.2 Connecting BSC 1 to MSC Server 2 in the MSC Pool........................................................................6-35
6.4.3 Connecting BSC 1 to MSC Server 3 in the MSC Pool........................................................................6-37
6.4.4 Adding BSC 2 into the MSC Pool ......................................................................................................6-37
6.4.5 Adding BSC 3 into the MSC Pool.......................................................................................................6-37
6.4.6 Adding BSC4 into the MSC Pool........................................................................................................6-37
7 New MSC Pool in the 3G Network........................................................................................ 7-1

7.1 New Target Network.......................................................................................................................................7-2
7.3 Data Planning..................................................................................................................................................7-5
ii

Issue 02 (2008-04-10)

Contents
7.4.1 Configuring the Basic Data of NEs........................................................................................................7-8

7.4.3 Building an MSC Pool in the Core Network..........................................................................................7-9
7.4.4 Adding BSCs to the MSC Pool Area...................................................................................................7-15
8 3G Network Evolution to Support MSC Pool......................................................................8-1

8.1 Evolution Scenario..........................................................................................................................................8-2
8.1.1 Description of the Existing Network......................................................................................................8-2
8.1.2 Description of Target Network..............................................................................................................8-3
8.2.1 Data Planning.........................................................................................................................................8-6
8.2.2 Presetting Data for the MSC Pool........................................................................................................8-10
8.3 Evolution of the Core Network.....................................................................................................................8-10
8.3.1 Overview..............................................................................................................................................8-11
8.3.2 Adding MSC Server 2 to the MSC Pool..............................................................................................8-11
8.3.3 Adding MGW 2 to the MSC Pool........................................................................................................8-14
8.3.4 Adding MSC Server 3 to the MSC Pool..............................................................................................8-17
8.3.5 Adding MGW 3 to the MSC Pool........................................................................................................8-22
8.4 Access of the Access Network......................................................................................................................8-27
8.4.1 Connecting RNC 1 to MSC Server 1 in the MSC Pool.......................................................................8-27
8.4.4 Adding RNC 2 to the MSC Pool..........................................................................................................8-32
8.4.5 Adding RNC 3 to the MSC Pool .........................................................................................................8-32
8.4.6 Adding RNC 4 to the MSC Pool..........................................................................................................8-32
9 Routine Maintenance................................................................................................................9-1
9.1 Setting the Attribute Parameters of an MSC Pool...........................................................................................9-2
9.1.1 Description of the MSC Pool Attribute Parameters...............................................................................9-2
9.1.2 Reviewing the Attribute Parameters of an MSC Pool............................................................................9-5
9.1.3 Adding NRI for an MSC Pool................................................................................................................9-7
9.1.4 Setting the Mapping Between the NRI and the CN ID..........................................................................9-8
9.1.5 Setting NRI Length and Null NRI........................................................................................................9-10
9.1.6 Setting the Parameters Relating to Load Balancing of the MSC Pool.................................................9-11
9.1.7 Setting the Non-broadcast LAI of the MSC Pool................................................................................9-13
9.1.8 Setting the Maintenance Status of an NE in the MSC Pool.................................................................9-14
9.2 Checking the Alarms of the MSC Pool.........................................................................................................9-15
9.2.1 Checking the Fault Alarms of the MSC Pool.......................................................................................9-15
9.2.2 Checking the Event Alarms of the MSC Pool......................................................................................9-18
9.3 Monitoring MSC Pool Load in Real Time....................................................................................................9-19
Issue 02 (2008-04-10)

iii
Contents

9.3.1 Setting the Real-Time Monitoring of the MSC Pool...........................................................................9-20
9.3.2 Counters of MSC Pool Real-time Monitoring.....................................................................................9-22
9.4 Reviewing the MSC Server which Is Serving the Specified Subscriber.......................................................9-22
9.5 Querying the Performance Report of the MSC Pool.....................................................................................9-24
9.6 Manual Migration of Subscribers..................................................................................................................9-26
9.7 Auditing MSC Pool Data..............................................................................................................................9-30
9.7.1 Reviewing the Result of an MSC Pool Data Check.............................................................................9-30
9.7.2 Manually Checking MSC Pool Data....................................................................................................9-33
9.7.3 Synchronizing MSC Pool Data............................................................................................................9-36
10 MSC Pool Performance Metrics Reference.......................................................................10-1

10.1 Total Traffic in MSC Pool..........................................................................................................................10-4
10.2 Incoming/Outgoing MSC Pool Traffic.......................................................................................................10-5
10.3 Handover to and Out of the MSC Pool.......................................................................................................10-6
10.4 All VLR Subscribers in the MSC Pool.......................................................................................................10-7
10.5 Success Paging Rate (Traffic Measurement For MTC SUCC Rate)..........................................................10-7
10.6 LAI In the MSC Pool..................................................................................................................................10-8
10.7 GSM Call Drop...........................................................................................................................................10-9
10.8 UMTS Call Drop.........................................................................................................................................10-9
10.9 MSC Pool Traffic Measurement Of GSM Assignment............................................................................10-10
10.10 MSC Pool Traffic Measurement Of WCDMA Assignment...................................................................10-10
10.11 Success SMS Rate...................................................................................................................................10-10
10.12 Traffic Measurement For LOC Up..........................................................................................................10-11
Index.................................................................................................................................................i-1
iv

Issue 02 (2008-04-10)

Figures
Figures
Figure 1-1 MSC Pool and MSC Pool area...........................................................................................................1-2
Figure 1-2 RNC/BSCs outside MSC Pool area....................................................................................................1-3
Figure 1-3 Structure of the TMSI.........................................................................................................................1-4
Figure 1-4 Load balancing ..................................................................................................................................1-7
Figure 1-5 MSC failure in the MSC Pool ............................................................................................................1-9
Figure 1-6 Centralized backup networking........................................................................................................1-10
Figure 1-7 Chain backup networking.................................................................................................................1-10
Figure 1-8 Backing up PRN signaling messages through route priority............................................................1-11
Figure 1-9 Back up PRN signaling messages through load balancing of SCCP signaling points.....................1-12
Figure 1-10 Backing up subscriber data ............................................................................................................1-13
Figure 1-11 Subscriber migration between MSCs ............................................................................................1-15
Figure 1-12 A-Flex function proxy on the MGW (M3UA agent networking)..................................................1-19
Figure 1-13 A-Flex function proxy on the MGW (M3UA forward networking)..............................................1-20
Figure 1-14 Mixed networking of A-Flex function proxy on MGW and Iu/A-Flex function proxy on the RNC/
BSC (1)................................................................................................................................................................1-21
Figure 1-15 Mixed networking of A-Flex function proxy on MGW and Iu/A-Flex function proxy on the RNC/
BSC (2) ...............................................................................................................................................................1-21
Figure 1-16 Mixed networking of MGW used for providing A-Flex function and RNC/BSC providing Iu/A-Flex
function (M3UA forward networking)................................................................................................................1-22
Figure 1-17 MSC server managing A-interface circuits....................................................................................1-23
Figure 1-18 MGW managing A-interface circuits.............................................................................................1-24
Figure 1-19 Charging based on virtual MSC ID................................................................................................1-25
Figure 1-20 Application of the M2000 in the MSC Pool...................................................................................1-27
Figure 2-1 MSC Pool networking adopted when the A interface between the BSC and the MGW is based on TDM
...............................................................................................................................................................................2-3
Figure 2-2 MSC Pool networking adopted when the Iu interface between the RNC and the MGW is based on ATM
...............................................................................................................................................................................2-4
Figure 5-1 Networking diagram of a new target network....................................................................................5-2
Figure 5-2 SPCs used in the target network.........................................................................................................5-4
Figure 5-3 Overall data configuration process for an MSC Pool.........................................................................5-5
Figure 6-1 Networking diagram of an existing 2G network................................................................................6-2
Figure 6-2 Networking diagram of a target network............................................................................................6-4
Figure 6-3 Basic data configuration flow of the MSC Pool.................................................................................6-6
Figure 6-4 MSC Pool composed of MSC server 1 and MGW 1........................................................................6-10
Figure 6-5 MSC Pool including MSC server 2 .................................................................................................6-13
Issue 02 (2008-04-10)


Figures
Figure 6-6 MSC Pool including MGW 2...........................................................................................................6-16

Figure 6-7 MSC Pool including MSC Server 3.................................................................................................6-20
Figure 7-1 Networking diagram of a new target network....................................................................................7-2
Figure 7-3 Overall data configuration process for an MSC Pool.........................................................................7-4
Figure 8-1 Networking diagram of a typical existing 3G network...................................................................... 8-2
Figure 8-2 Networking diagram of a target network............................................................................................8-4
Figure 8-4 Basic data configuration flow of the MSC Pool.................................................................................8-6
Figure 8-5 MSC Pool including MSC server 2 .................................................................................................8-12
Figure 8-7 MSC Pool including MSC server 3..................................................................................................8-18
Figure 9-1 MSC Pool Management interface.......................................................................................................9-6
Figure 9-2 Parameter Setting dialog box..............................................................................................................9-7
Figure 9-3 Add dialog box................................................................................................................................... 9-8
Figure 9-4 Modify dialog box (1).........................................................................................................................9-9
Figure 9-5 Modify dialog box (2).......................................................................................................................9-11
Figure 9-9 Set Status dialog box........................................................................................................................9-15
Figure 9-10 Filter dialog box..............................................................................................................................9-17
Figure 9-11 Alarm Source tab............................................................................................................................9-17
Figure 9-12 Base Setting tab..............................................................................................................................9-18
Figure 9-13 Create a Monitor Task dialog box..................................................................................................9-21
Figure 9-14 Search for subscribers dialog box...................................................................................................9-23
Figure 9-15 Set report conditions dialog box.....................................................................................................9-25
Figure 9-16 Filter Counter dialog box................................................................................................................9-26
Figure 9-17 Load re-distribution-Select a type dialog box................................................................................9-28
Figure 9-18 Automatic Check dialog box..........................................................................................................9-31
Figure 9-19 View Check Result tab...................................................................................................................9-32
Figure 9-20 Manual Check dialog box...............................................................................................................9-34
Figure 9-21 Data Consistency Check dialog box (1).........................................................................................9-35
Figure 9-22 Data Consistency Check dialog box (2).........................................................................................9-35
Figure 9-23 Data Synchronization dialog box...................................................................................................9-37
Figure 9-24 Generated MML commands...........................................................................................................9-37
vi

Issue 02 (2008-04-10)

Tables
Tables
Table 3-1 MSC Pool network specifications........................................................................................................3-2
Table 3-2 NRI planning reference data................................................................................................................3-3
Table 3-3 Items of an MSC Pool planning ..........................................................................................................3-6
Table 5-1 Data planning for MSC servers in an MSC Pool network...................................................................5-5
Table 5-2 Data planning for MGWs in an MSC Pool network............................................................................5-8
Table 5-3 Data planning for BSCs in an MSC Pool network...............................................................................5-9
Table 6-1 Data planning example of the MSC servers in an MSC Pool network................................................6-6
Table 6-2 Data planning example of the MGWs in an MSC Pool network.........................................................6-8
Table 6-3 Data planning example of the BSCs in an MSC Pool network............................................................6-9
Table 6-4 Changing status of MSC servers........................................................................................................6-38
Table 7-1 Data planning for MSC servers in an MSC Pool network...................................................................7-5
Table 7-2 Data planning for MGWs in an MSC Pool network............................................................................7-7
Table 7-3 Data planning for RNCs in an MSC Pool network..............................................................................7-8
Table 7-4 Changing status of MSC servers........................................................................................................7-18
Table 8-1 Data planning of the MSC servers in an MSC Pool network..............................................................8-6
Table 8-2 Data planning of the MGWs in an MSC Pool network.......................................................................8-9
Table 8-3 Data planning of the RNCs in an MSC Pool network.......................................................................8-10
Table 9-1 Description of the parameters relating to the attributes of the MSC Pool...........................................9-3
Table 9-2 Meaning of the add and remove operations.........................................................................................9-9
Table 9-3 Mapping between the maintenance operations and the NE status.....................................................9-14
Table 9-4 Counters relating to the real-time load monitoring task.....................................................................9-22
Table 9-5 Mapping between the migration modes and the operations...............................................................9-29
Table 9-6 Mapping between the update result and the operation.......................................................................9-35
Table 9-7 Command send modes.......................................................................................................................9-38
Issue 02 (2008-04-10)

vii

About This Document
About This Document
Purpose
This manual describes the concepts, working principle, signaling networking, network planning,
2G network evolving to MSC Pool, new MSC Pool in 2G network, routine maintenance, and
performance metrics reference of the MSC Pool feature of the Huawei MSOFTX3000 Mobile
SoftSwitch Center (hereinafter referred to as MSOFTX3000).
Related Versions
The following table lists the product versions related to this document.
Product Name
Version
MSOFTX3000
V100R006C05
Intended Audience
This document is intended for:
l
Marketing technical engineers
Telecommunications management staff
Mobile network maintenance engineers
Organization
This document consists of 10 chapters and is organized as follows.
Issue 02 (2008-04-10)
Chapter
Description
1 Overview
This chapter describes the concepts and working principle of the

MSC Pool feature.

About This Document
Chapter
Description
2 Networking
Description
This chapter describes the signaling networking of the MSC

Pool.
3 MSC Pool Network

Planning
This chapter describes the network planning principles and

system specifications of the MSC Pool.
4 Commands and
Parameters Related to
MSC Pool
This chapter describes the commands, parameters, and software

parameters about the MSC Pool feature.
5 New MSC Pool in the

2G Network
This chapter describes the data planning and data configuration

process of a new MSC Pool in a 2G network.
6 2G Network Evolution
to Support MSC Pool

process of a 2G network evolving to an MSC Pool network.
7 New MSC Pool in the

3G Network

process of a new MSC Pool in a 3G network.
8 3G Network Evolution
to Support MSC Pool

process of a 3G network evolving to an MSC Pool network.
9 Routine Maintenance
This chapter describes the routine maintenance operations of the

MSC Pool, including setting the attributes of an MSC Pool,
checking the alarms of an MSC Pool, monitoring the MSC Pool
load in real time, querying the performance report of the MSC
Pool, manual redistribution of subscribers, and checking MSC
Pool data.
10 MSC Pool
Performance Metrics
Reference
This chapter describes the commonly used KPI for use with the
MSC Pool networking feature.
Conventions
Symbol Conventions
The following symbols may be found in this document. They are defined as follows.
Symbol
Description
DANGER
WARNING
Indicates a hazard with a high level of risk which, if not

avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk which,
if not avoided, could result in minor or moderate injury.

Issue 02 (2008-04-10)

Symbol
About This Document
Description
CAUTION
Indicates a potentially hazardous situation that, if not

avoided, could cause equipment damage, data loss, and
performance degradation, or unexpected results.
TIP
Indicates a tip that may help you solve a problem or save

your time.
NOTE
Provides additional information to emphasize or

supplement important points of the main text.
General Conventions
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in boldface. For

example, log in as user root.
Italic
Book titles are in italics.
Courier New
Terminal display is in Courier New.
Command Conventions
Issue 02 (2008-04-10)
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italic.
[]
Items (keywords or arguments) in square brackets [ ] are

optional.
{ x | y | ... }
Alternative items are grouped in braces and separated by

vertical bars. One is selected.
[ x | y | ... ]
Optional alternative items are grouped in square brackets

and separated by vertical bars. One or none is selected.
{ x | y | ... } *
Alternative items are grouped in braces and separated by

vertical bars. A minimum of one or a maximum of all can
be selected.


About This Document
GUI Conventions
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles are in

boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">" signs. For
example, choose File > Create > Folder.
Keyboard Operation
Format
Description
Key
Press the key. For example, press Enter and press Tab.
Key 1+Key 2
Press the keys concurrently. For example, pressing Ctrl+Alt+A means the
three keys should be pressed concurrently.
Key 1, Key 2
Press the keys in turn. For example, pressing Alt, A means the two keys
should be pressed in turn.
Mouse Operation
Action
Description
Click
Select and release the primary mouse button without moving the pointer.
Double-click
Press the primary mouse button twice continuously and quickly without
moving the pointer.
Drag
Press and hold the primary mouse button and move the pointer to a certain
position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 02 (2008-04-10)

Incorporate technical updates.
Updates in Issue 01 (2008-02-25)

Initial release.
4

Issue 02 (2008-04-10)

1 Overview
Overview
About This Chapter

This section describes the concepts and working principle of the MSC Pool feature.
1.1 Introduction
This section describes the background information of the MSC Pool feature.
1.2 Concept
This section describes the common concepts used in the MSC Pool feature.
1.3 Technical Principle
This section describes the principles related to the MSC Pool feature, including the principle of
the load balancing, handover, disaster tolerance, subscriber migration, MGW load balancing,
provision of A-Flex by the MGW, management of circuits on the A interface by the MGW, and
charging.
1.4 M2000 Application in the MSC Pool
This section describes the application of the M2000 in the MSC Pool feature.
Issue 02 (2008-04-10)

1-1

1 Overview
1.1 Introduction
This section describes the background information of the MSC Pool feature.
In a traditional mobile network, one RNC/BSC can be connected to one MSC only. In the MSC
Pool networking mode, one RNC/BSC can be connected to multiple MSCs. Compared with the
traditional networking mode, the MSC Pool networking mode has the following advantages:
l
Multiple MSCs share the load of a network. This design helps to improve the utilization of
resources of the core network and saves investment on equipment.
Data can be backed up amongst the MSCs to make the MSC pool more disaster tolerant
and improve the reliability of the network.
Inter-MSC location update times and signaling traffic on the C/D interface are reduced.
Inter-MSC handovers are reduced and subscribers' conversation quality is improved.
1.2 Concept
This section describes the common concepts used in the MSC Pool feature.
MSC Pool and MSC Pool Area

As shown in Figure 1-1, a group of MSCs comprise an MSC Pool. The area served by an MSC
Pool is called an MSC Pool area. From the perspective of the RNC/BSC, if one or more RNC/
BSCs belong to an MSC Pool, all the service areas of the RNC(s)/BSC(s) comprise an MSC
Pool area. All subscribers in the Pool area are served together by the MSCs in the MSC Pool.
Figure 1-1 MSC Pool and MSC Pool area
MSC Pool
MSC2
MSC1
RNC1/
BSC1
RNC2/
BSC2
RNC3/
BSC3
MSC Pool area
RNC/BSC Outside the MSC Pool Area

The MSCs in an MSC Pool can serve one or more RNC/BSC service areas at the same time.
The served RNC/BSCs are called RNC/BSCs outside the MSC Pool area, as shown in Figure
1-2.
1-2

Issue 02 (2008-04-10)

1 Overview
Figure 1-2 RNC/BSCs outside MSC Pool area

MSC Pool
MSC1
RNC1/
BSC1
MSC2
RNC2/
BSC2
RNC3/
BSC3
RNC4/
BSC4
MSC Pool area
NRI
A network resource identifier (NRI) is used to identify an MSC node serving a specified MS/
UE. When an MS/UE registers with an MSC in the MSC Pool for the first time, the MSC allocates
a TMSI containing the local NRI for the MS/UE. When the MS/UE initiates a service again, the
NRI is contained in the service initiation request message. The RNC/BSC routes the service to
the MSC based on the contained NRI. In this way, each service initiated by the MS/UE in the
MSC Pool area can be routed to the corresponding MSC with which the MS/UE registered. In
this case, when an MS/UE roams within the MSC Pool area, the serving MSC need not be
changed. Compared with traditional networking, the number of location update signaling
messages through the C/D interface is reduced.
An NRI value defines a unique MSC in an MSC Pool. In order to have an active MSC Pool
feature, each MSC Pool member must be assigned at least one NRI value with a length different
from zero. If the NRI length is zero, the MSC does not assign any NRI values to the TMSI and
the MSC Pool feature is not operational (the MSC is not an MSC Pool member).
More than one NRI value can be assigned to an MSC serving an MSC Pool area. The subscriber
capacity in an MSC can be increased by assigning a new additional NRI value to the MSC. All
NRI values must have the same length if they belong to the same MSC Pool.
TMSI
The TMSI is a temporary identifier that is assigned to the mobile subscriber when it is registered
in an MSC. The TMSI is used to increase subscriber confidentiality by avoiding sending the
International Mobile Subscriber Identity (IMSI) on the air interface. Once a TMSI has been
assigned to a User Equipment (UE), the TMSI is used by the UE to identify itself in the network.
Figure 1-3 shows the TMSI structure. The TMSI contains an NRI in bits 2314. The NRI is
defined with a length and with a corresponding set of values. The NRI length has a range of 0
to 10 bits. For example, if the NRI has a length of 10 bits, it occupies bits 2314 (including bit
23 and bit 14) of the TMSI.
Issue 02 (2008-04-10)

1-3

1 Overview
The implementation of the MSC Pool function depends on the TMSI reallocation function
enabled by the MSC in the MSC Pool, including the allocation of TMSI during location update
and the allocation of TMSI during service access.
Figure 1-3 Structure of the TMSI
31 30
29
CS/PS
VLR
restart
28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13
...
NRI range
Bits 31-30
CS/PS service indicator
Bit 29
VLR restart count
Bits 23-n (n14)
NRI
Other bits
User IDs
Null NRI
It is a special NRI. This NRI is encoded with common NRIs on a unified basis. During subscriber
migration, a null-NRI is used to instruct the RNC/BSC to reselect a serving MSC for the MS/
UE. For details about the function of the null-NRI in subscriber migration, see Principle.
Non-broadcast LAI
It is a special LAI and is encoded with common LAIs on a unified basis. During subscriber
migration, it is used to trigger the MS/UE to perform location update immediately after
completing the current service procedure. In addition, the Non-broadcast LAI can be used to
identify each MSC in an MSC Pool. For details about the function of the non-broadcast LAI in
subscriber migration, see Principle.
Each MSC in the MSC Pool has a unique Non-broadcast LAI. Each MSC in an MSC Pool must
be configured with the Non-broadcast LAIs of other MSCs in the MSC Pool because the target
MSC determines the address of original MSC serving the MS/UE based on the Non-broadcast
LAI and obtains the subscriber information (subscriber's IMSI and unused encryption
parameters) from the original MSC during inter-MSC subscriber migration in the MSC Pool.
MSC Server
The MSC server is applicable to the R4 networking structure. The MSOFTX3000 functions as
the MSC server in an MSC Pool. The MSC server is also called Server or SoftSwitch (SX). In
the following context, unless otherwise specified, the name Server or SX refers to the MSC
server.
Virtual MGW
One MGW is managed by one MSC server. One MGW can be divided into many virtual MGWs
which are managed by different MSC servers.
1-4

Issue 02 (2008-04-10)

1 Overview
Iu-Flex
Intra-domain connection of RAN nodes to multiple CN nodes (Iu-Flex) indicates that one RAN
node can be connected to multiple CN nodes in the same CS/PS domain. Iu-Flex function has
the following advantages:
l
Multiple CN nodes share the load of the RAN node, this can:
Improve the utilization of the CN node.
Improve the disaster recovery capability of the network.
Reduce the loss caused by the CN node failure.
The service area of a single CN node is enlarged, this can:
Reduce the number of handovers when crossing CN nodes.
Reduce the number of CN node updates when subscribers roam.
Thus, the signaling traffic of the CN is reduced.

l
An efficient networking structure can be provided to operators for sharing the RAN.
IuFlex and the MSC Pool comply with the same protocols. Different from the Iu-Flex, the MSC
Pool is used in the CS domain of the CN.
Using MGW to Provide the A-FLEX Function

When the MSC Pool networking mode is applied to the present network, you need to upgrade
BSCs on the present network to enable the A-Flex function. BSCs on the present network,
however, do not support the A-Flex function. There are too many BSCs in the present network.
BSCs of different vendors may not support the A-Flex function. Therefore, it is difficult to
upgrade BSCs on the present network to support the A-Flex function.
To solve the above problem, Huawei MGW can be used to provide the A-Flex function. Thus,
when a Huawei MGW is deployed in the network, BSCs on the current network can access the
MSC Pool without upgrade. For details, see 1.3.8 A-Flex Function Proxy on the MGW.
Default MSC
When a subscriber roams out of the MSC Pool area and registers with an MSC outside the MSC
Pool, the MSC outside the MSC Pool obtains the subscriber information from the original MSC
where the subscriber is registered. In this case, the MSC outside the MSC Pool should be able
to identify the subscriber's original MSC address based on the original LAI of the subscriber
and the NRI in the TMSI (because an LA in an MSC Pool area is served by all the MSCs in the
MSC Pool, the subscriber's original MSC can not be identified through the LAI only). In this
case, the MSC outside the MSC Pool should configure the mapping relations between LAIs and
NRIs of the MSC Pool and MSCs.
The above process has the following two disadvantages:
l
MSCs outside the MSC Pool need develop above mapping functions.
MSCs outside the MSC Pool should obtain the planning of NRIs in the MSC Pool and you
need configure large amount of data.
To solve this problem, the concept of a default MSC is adopted in the MSC Pool standards
definition.
An MSC outside the MSC Pool identifies the default MSC based on the original LAI of the
subscriber. The default MSC identifies the originally registered MSC according to the NRI in
Issue 02 (2008-04-10)

1-5

1 Overview
the TMSI (the mapping between NRIs of all MSCs in the Pool and corresponding MSC addresses
needs be configured in the default MSC) and transfers the subscriber information between MSCs
outside the MSC Pool and the originally registered-to MSC.
Call Termination Recovery

When an MSC in the MSC Pool fails, the HLR cannot send the PRN to this MSC. In this case,
subscribers registered at this MSC cannot be reached. In this case, subscribers can be called only
after they update their Location Area Code to the HLR or are registered in other valid MSCs in
the MSC Pool by originating calls.
When the failed MSC recovers, it needs to initiate paging in the whole network to obtain
subscriber information because it does not contain the LAIs of subscribers. In MSC Pool
networking mode, whole network paging is not initiated usually because the MSC Pool area is
very large. This may also cause call termination failure.
To solve these problems, some special signaling processing is required during an MSC failure
in the pool, which is called Call Termination Recovery. For details, see Call Termination
Recovery Principle.
CN-ID
It is the ID of an MSC node. A CN-ID uniquely identifies an MSC in the MSC Pool.
1.3 Technical Principle

This section describes the principles related to the MSC Pool feature, including the principle of
the load balancing, handover, disaster tolerance, subscriber migration, MGW load balancing,
provision of A-Flex by the MGW, management of circuits on the A interface by the MGW, and
charging.
1.3.1 Load Balancing
This section describes the basic principle of the load balancing.
1.3.2 Handover
This section describes the principle of handover in MSC Pool feature.
1.3.3 Disaster Tolerance
This section describes the principle of disaster tolerance in MSC Pool feature.
1.3.4 Paging Control
This section describes the principle of the paging control in MSC Pool feature.
1.3.5 Location Update with Gs Interface
This section describes location update with Gs interface.
1.3.6 Subscriber Migration Between MSCs
This section describes the principle of subscriber migration in MSC Pool feature.
1.3.7 Load Balancing at the MGW
This section describes the principle of MGW load balancing in MSC Pool feature.
1.3.8 A-Flex Function Proxy on the MGW
This section describes the principle of A-Flex function proxy on the MGW in MSC Pool feature.
1.3.9 MGW Managing Circuits of the A Interface
This section describes the principle of MGW managing circuits of the A interface.
1-6

Issue 02 (2008-04-10)

1 Overview
1.3.10 Charging Principle

This section describes the principle of charging in MSC Pool feature.
1.3.1 Load Balancing

This section describes the basic principle of the load balancing.
In the MSC Pool networking, an RNC/BSC connects with multiple MSCs in the MSC Pool.
When an MS/UE in the service area of an RNC/BSC initiates a service, the RNC/BSC needs to
select an MSC for the service. The function which selects a serving MSC for an MS/UE is called
the NAS node selection function (NNSF).
l
When an MS/UE initiates a service based on IMSI/IMEI, the RNC/BSC follows the
principle of load balancing. It selects a valid MSC to serve the MS/UE according to the
proportion of subscriber capacity of each valid MSC in the MSC Pool. When the MS/UE
initiates a service using the IMSI/IMEI, the selected MSC allocates a TMSI containing the
NRI of the MSC for the MS/UE.
Figure 1-4 Load balancing

MSC Pool
MSC2
MSC1
RNC1/
BSC1
RNC2/
BSC2
RNC3/
BSC3
MS/UE
MS/UE
MS/UE
MSC Pool area
When an MS/UE initiates a service using a TMSI, the RNC/BSC selects a serving MSC
for the MS/UE according to its mapping table between NRIs and MSCs in the MSC Pool.
When the selected MSC is invalid or there is no mapping between NRIs and MSCs, the
RNC/BSC follows the principle of load balancing. It selects a valid MSC to serve the MS/
UE according to the proportion of subscriber capacity of valid MSCs in the MSC Pool. The
selected MSC allocates a TMSI containing the NRI of the MSC for the MS/UE.
When the MSC sends a paging message to the called MS/UE, the RNC/BSC temporarily
stores the mapping index between the IMSI and the MSC that sends the paging message.
When the called MS/UE responds to the network using an IMSI, the RNC/BSC selects an
MSC according to mapping between NRIs and MSCs if the response contains an NRI.
Otherwise, the RNC/BSC selects an MSC for the MS/UE according to the mapping between
the temporarily stored IMSI and the MSC. In this case, the paging response can be sent to
the MSC sending the paging message, and the call can be connected successfully. When
the selected MSC is invalid or an MSC cannot be selected according to the mapping, the
Issue 02 (2008-04-10)

1-7

1 Overview
RNC/BSC follows the principle of load balancing to select a valid MSC, as shown in Figure
1-4.
NOTE
When the RNC/BSC detects that the signaling point of the MSC is inaccessible, the RNC/BSC considers
the MSC to be faulty or invalid.
The proportion of subscriber capacity of MSCs needs to be configured statically on the RNC/BSC
connected with the MSCs. In addition, the MSCs can notify the RNC/BSC of the proportion of
subscriber capacity regularly, and the RNC/BSC dynamically adjusts the proportion of subscriber
capacity of MSCs according to the capacity of subscribers in the notification. This mode, however,
only applies to the case that all MSCs in the MSC Pool and RNCs/BSCs in the MSC Pool area are
Huawei equipment. For other modes, the RNC/BSC can only configure the subscriber capacity of
MSCs statically.
The subscriber capacity of an MSC described above is the total number of subscribers of the MSC
(number of licensed subscribers for the MSC). However, when an MSC connects with RNCs/BSCs
outside the MSC Pool, the subscriber capacity reserved for these RNCs/BSCs needs to be subtracted
from the total capacity as for calculation of subscriber capacity of the MSC.
1.3.2 Handover
This section describes the principle of handover in MSC Pool feature.
Handover within the MSC Pool Area

As any LA in the MSC Pool area is served by all MSCs in the MSC Pool, only inter-LA handover
is performed for the MS/UE that moves in the MSC Pool area during conversation. (Compared
with traditional networking, the number of inter-MSC handovers can be reduced, and the quality
of calls can be improved.)
Handover to the MSC Pool Area

MSCs outside the MSC Pool can use any MSC in the MSC Pool as the target MSC during
handover. To avoid concentration of inter-MSC handover work load on one pooled MSC and
reduce the impact of MSC single-point failure, the handover targets MSCs for outside MSC
must be set to different MSCs in the MSC Pool through data configuration.
Handover out of the MSC Pool Area

For neighboring LAs outside the MSC Pool area, any MSC-served subscribers in the MSC Pool
area can shift to an adjacent MSC outside the MSC Pool area during handover. In this case, the
adjacent MSC is set to the destination MSC of MSCs in the MSC Pool during handover (it is
the same as the handover configuration for the MSC on the present network).
1.3.3 Disaster Tolerance

This section describes the principle of disaster tolerance in MSC Pool feature.
In fact, the above load-balancing mechanism makes the networking of MSC Pool have the
disaster recovery capability based on MSC. When an MSC in the MSC Pool is faulty, the RNC/
BSC identifies the MSC failure and transfers the services allocated to this MSC to another valid
MSC in this MSC Pool, thus implementing the disaster tolerance between MSCs in the MSC
Pool.
1-8

Issue 02 (2008-04-10)

1 Overview
For Call Origination

When an MSC in the MSC Pool is invalid due to failure, the service requests initiated by
subscribers in the MSC are routed to other valid MSCs (new MSCs) through the load-balancing
algorithm. As a result, disaster recovery can be achieved.
l
In the case that an MS/UE initiates location update, a new MSC directly updates the location
of the MS/UE to register the MS/UE in the MSC and allocates a TMSI containing the NRI
of the MSC for the MS/UE.
In the case that a subscriber initiates a call, the new MSC indicates that the MS/UE is an
unknown subscriber. In this case, the MS/UE registers with a valid MSC in the MSC Pool.
If implicit location update is allowed, the new MSC updates the location of the MS/UE on
an implicit basis (location update to the HLR on interface C/D) to register the MS/UE in
the MSC. Then, the MSC allocates a TMSI containing the NRI of the MSC for the MS/UE
and connects the call.
The above load-balancing algorithm cannot achieve disaster recovery for call termination cases.
For Call Termination

When an MSC in the MSC Pool is failed, the HLR cannot send the PRN to the MSC. In this
case, subscribers registered in that MSC cannot be called. The subscribers can be called only
after they update their locations or are registered in other valid MSCs in the MSC Pool by
originating calls.
Figure 1-5 MSC failure in the MSC Pool
HLR
STP
MSC1
MSC 2
MSC3
MSC Pool
When the faulty MSC recovers, it needs to initiate paging in the whole network to obtain
subscriber information because it does not contain LAIs of subscribers. In MSC Pool networking
mode, whole network paging is not initiated usually because the MSC Pool area is very large.
This may also cause call termination failure, as shown in Figure 1-5.
To solve these problems, some special processing is required. The following describes the
networking and principle of the solution to call termination failure.
Issue 02 (2008-04-10)

1-9

1 Overview
Call Termination Recovery Networking

The system supports two networking solutions, that is, chain backup networking and centralized
backup networking.
l
Centralized backup networking

Figure 1-6 Centralized backup networking
HLR
STP
MSC1/
VLR1
MSC 2/
VLR2
MSC4/
VLR4
MSC3/
VLR3
MSC Pool
In this mode, a dedicated centralized standby MSC/VLR is used. The centralized standby
MSC/VLR is responsible for recovering call termination only. It does not process any other
service.
l
Chain backup networking

Figure 1-7 Chain backup networking
HLR
STP
MSC1/
VLR1
MSC 2/
VLR2
MSC3/
VLR3
MSC Pool
1-10

Issue 02 (2008-04-10)

1 Overview
There is not a dedicated backup MSC/VLR in this mode. Each MSC/VLR in the MSC Pool
is the active MSC/VLR and also serves as the standby MSC/VLR for other MSC/VLRs.
As shown in the preceding figure, MSC/VLR1 is the standby MSC/VLR of MSC/VLR3;
MSC/VLR2 is the standby MSC/VLR of MSC/VLR1; MSC/VLR3 is the standby MSC/
VLR of MSC/VLR2.
Call Termination Recovery Principle

When an MSC in the MSC Pool fails, the following functions need to be enabled to recover call
termination:
1.
Backing up PRN signaling messages (route PRN signaling messages to other valid MSCs).
2.
Backing up subscriber data (that is, LAI). When the standby MSC pages a called MS/UE,
the MSC can obtain the LAI of the called MS/UE from the backup subscriber data.
Otherwise, the MSC has to page the called MS/UE in the whole network.
Backing up PRN signaling messages
Back up PRN signaling messages through route priority, as shown in Figure 1-8.
Figure 1-8 Backing up PRN signaling messages through route priority
HLR
STP
MSC1
(AA)
MSC2
(BB, AA)
MSC Pool
When MSC2 serves as the standby MSC of MSC1, two routes need to be configured
on the STP: Set the direct route between STP and signaling point AA of MSC1 to a
route with higher priority and the bypass route between STP and AA through signaling
point BB of MSC2 to a route with lower priority. In addition, the addressing mode of
STP and MSCs in the MSC Pool must be set to DPC addressing. Signaling point BB
must be set to a mutual-aid signaling point for signaling point AA on MSC2.
When MSC1 works normally, signaling messages sent to signaling point AA from STP
are sent to MSC1 through the direct route with higher priority. When MSC1 fails, the
signaling messages are sent to MSC2 through the bypass route. Because signaling point
BB on MSC2 is the mutual-aid signaling point of signaling point AA, the signaling
messages are processed on MSC2.
NOTE
If the local HLR is directly connected with the MSC, a standby route must be configured on the
HLR. This configuration is the same as the STP mode in processing logic.
Issue 02 (2008-04-10)

1-11

1 Overview
Back up PRN signaling messages through load balancing of SCCP signaling points, as
shown in Figure 1-9.
Figure 1-9 Back up PRN signaling messages through load balancing of SCCP signaling
points
HLR
STP
MSC1
(AA, GT1)
MSC2
(BB)
MSC Pool
Plan the data on the STP as follows:

Set the addressing mode of GT1 to AA+SSN and set signaling point BB to an SCCP
load-balancing signaling point of AA. The priority of BB is lower than that of AA.
In this case, signaling messages sent to GT1 from STP are sent signaling point AA with
higher priority (that is, MSC1) normally. When MSC1 fails, the signaling messages are
sent to the load-balancing signaling point BB with lower priority (that is, MSC2). The
signaling messages are then processed on MSC2.
NOTE
If the local HLR is directly connected to the MSC, GT must be configured on the HLR. This
configuration is the same as the STP mode in processing logic.
l
1-12
Backing up subscriber data

Issue 02 (2008-04-10)

1 Overview
Figure 1-10 Backing up subscriber data

HLR
STP
MSC1/
VLR1
MSC2/
VLR2
Backup
MSC Pool
To back up subscriber data in the VLR in the MSC Pool on real-time basis:
1.
When the attach/detach status and LAIs of subscribers in the MSC Pool are changed,
the VLR need to back up subscriber data to the standby VLR (the VLR backs up IMSIs,
LAIs and subscriber status only), as shown in Figure 1-10.
2.
When the location of a subscriber in the MSC Pool is canceled, the VLR informs the
standby VLR to delete the corresponding subscriber data.
The call termination recovery solution has the following limitations:

l
Additional M3UA signaling links must be added between the standby MSC and the active
MSC for the backup of subscriber data in the VLR.
In the case of networking based on routing priority, the standby MSC cannot serve as an
STP.
Only Phase 2 and later versions of MAP are supported.
Call Termination Recovery Flow

MSC2 (standby MSC) receives a PRN message sent by the HLR to the MSC1 (active MSC). If
the VLR in MSC2 does not have subscriber data, MSC2 retrieves the subscriber's LAI and
subscriber status from the standby VLR. Then MSC2 sends a paging message to the switchedon MS/UE once only (it terminates the call directly for switched-off MS/UE) and terminates the
call. The call is terminated without waiting for paging response message because the paging
response message may be sent to another MSC in the MSC Pool rather than MSC2.
When an MSC in the MSC Pool receives a paging response, the MSC checks whether the
subscriber data is in the local VLR. If no subscriber data is found, the MSC updates the location
of the MS/UE on an implicit basis. Then, the MS/UE can register with the MSC. The MSC also
allocates a TMSI containing the NRI of the MSC for the MS/UE.
After MSC1 recovers, when it receives a PRN message from the HLR, MSC1 retrieves the LAI
of the subscriber and subscriber status from the standby VLR. Then it updates the location of
the subscriber on an implicit basis and allocates an MSRN for the MS/UE. After a call is routed
in the incoming direction, MSC1 follows the normal call termination procedure to page the called
MS/UE.
Issue 02 (2008-04-10)

1-13

1 Overview
1.3.4 Paging Control

This section describes the principle of the paging control in MSC Pool feature.
An MSC Pool area is comprised of many MSC service areas. The area of an MSC Pool may be
as large as several times of an MSC service area. If the paging in the entire network is allowed,
the paging channels will be possibly congested. In this case, you must determine whether the
paging in the entire network is allowed when constructing an MSC Pool with multiple MSCs.
The paging in the entire network is restricted by the following means:
1.
You can configure data to control whether the paging in the entire network is allowed.
2.
If the paging in the entire network is allowed, the paging rate must be controlled, such as
2 times per second.
3.
If the paging of the subscriber receives no response in the current LA, the system must
allow the paging in the adjacent LA instead of paging in the entire network.
1.3.5 Location Update with Gs Interface

This section describes location update with Gs interface.
When an MS/UE sends cooperation location update request to an MSC in the MSC Pool through
the Gs interface, the MSC allocates the TMSI containing the local NRI to the MS/UE. In this
case, when the MS/UE initiates the CS service, the system can route the service to the originally
registered MSC of this MS/UE.
When the MSC addresses the called MS/UE based on the IMSI through the Gs interface, the
paging message contains the Global CN-ID. This ensures that the paging response is routed to
the MSC that initiated the paging.
1.3.6 Subscriber Migration Between MSCs

This section describes the principle of subscriber migration in MSC Pool feature.
Principle
Operation center staff may trigger subscriber migration between MSCs in the MSC Pool through
O&M commands.
In this way, operators can maintain MSCs in the MSC Pool without service impact. For example,
if an MSC needs to be upgraded, maintenance engineers can transfer all the subscriber data in
this MSC to other MSCs in the MSC Pool before upgrade. After the upgrade is completed, the
maintenance engineers transfer the subscriber data in other MSCs of the MSC Pool back to the
upgraded MSC, as shown in Figure 1-11.
1-14

Issue 02 (2008-04-10)

1 Overview
Figure 1-11 Subscriber migration between MSCs

O&M
MSC Pool
MSC1
RNC1/
BSC1
MSC2
RNC2/
BSC2
MS/UE
RNC3/
BSC3
MSC Pool area
Subscriber migration is implemented based on two modes.

l
When bit 11 of P401 is set to 0, the E interface redirection mode is used.
When bit 11 of P401 is set to 1, the mode specified in the 3GPP TS 23.236 protocol is used.
1.
The mode specified in the 3GPP TS 23.236 protocol
2.
Issue 02 (2008-04-10)
Configure the status of MSC on MSCs and RNC/BSCs (set the status of the MSC from
which subscribers are to be transited to off-load).
When an MS/UE which registered in the off-load MSC initiates a service, the MSC
allocates a TMSI containing null-NRI for the MS/UE. The MSC also instructs the MS/
UE that the current LAI is the Non-broadcast LAI of the MSC.
After the MS/UE finishes the current service, the Non-broadcast LAI enables the MS/
UE to trigger immediate location update (this is because the Non-broadcast LAI differs
from the LAI broadcasted by the RNC/BSC serving the MS/UE).
Upon receiving a location update message containing null-NRI from the MS/UE, the
RNC/BSC selects a valid MSC according to the proportion of subscriber capacity of
valid MSCs in the MSC Pool (not including the off-load MSC) and routes the service
to the selected MSC. The selected MSC registers the MS/UE and allocates a TMSI
containing its NRI for the MS/UE. During registration, the selected MSC determines
the original MSC where the MS/UE is registered according to the Non-broadcast LAI
carried by the MS/UE and obtains subscriber data (IMSI and unused encryption
parameters) from the original MSC. In this way, an MS/UE is transferred from one MSC
to another.
After migration is completed, stop migration through the O&M command and restore
the MSC status on the MSCs and RNC/BSCs.
Inter-office E interface redirection mode

1-15

1 Overview
l
Configure the status of MSC on MSCs and RNC/BSCs (set the status of the MSC from
which subscribers are to be transited to off-load).
When an MS/UE registered in the off-load MSC initiates a location update request or
service release request, the MSC initiates the location update request to the target MSC
based on the redirection message.
Upon receiving a location update request, the target MSC encrypts the authentication,
obtains the ID, checkimei, and TMSI reallocation information from the MS/UE, and
then sends the information to the originating MSC. The originating MSC interacts with
the MS/UE. The target MSC initiates the location update to the HLR and allocates a
TMSI containing the NRI of the target MSC for the MS/UE. Thus, the subsequent
location update and service request can be directly sent to the target MSC. In this way,
an MS/UE is transited from one MSC to another.
After migration is completed, stop migration through the O&M command and restore
the MSC status on MSCs and RNC/BSCs.
CAUTION
l
On the RNC/BSC, the status of an MSC can be set based on data configuration or notified
by the MSC. However, in this case all MSCs in the MSC Pool and RNC/BSCs in the MSC
Pool area are all Huawei equipment.
The status of MSC configured on the RNC/BSC can be normal, off-load or disabled.
Normally, the status of an MSC is normal. When subscribers are transited from an MSC, the
originating MSC is set to the off-load status. The disabled status is used for isolating or
upgrading MSCs in the MSC Pool. The RNC/BSC does not send any service data to a disabled
MSC.
Control for the migration speed: To avoid link congestion due to quick migration, the MSC
from which subscribers are transited can control the migration speed. The migration speed
falls into three types: high speed (migration is completed within one to two cycles of location
update), medium speed (migration is completed within two to three cycles of location update),
and low speed (migration is completed within four to five cycles of location update).
Migration involves multiple network elements (NEs) in the MSC Pool. To facilitate
operation, Huawei provides unified migration on the M2000, which can also monitor the
migration process. The M2000 can monitor whether subscriber migration in the MSCs in the
MSC Pool are completed.
Subscriber migration between MSCs has the following limitations:
1-16
The RNCs/BSCs outside the MSC Pool area are connected to only one MSC in the MSC
Pool. Therefore, subscribers in the service area of an RNC/BSC outside the MSC Pool area
cannot be redistributed between the MSCs in the MSC Pool.
Subscribers who are in the progress of combined location updates cannot be redistributed
between MSCs in the MSC Pool.
Mobile phones of certain models do not support the 3GPP TS 23.236. To redistribute the
subscribers who use these mobile phones, you must enable the inter-office redirection
function.
Subscribers who are in the progress of emergency calls cannot be redistributed between
the MSCs in the MSC Pool. This is because emergency calls do not require authentication,
Issue 02 (2008-04-10)

1 Overview
encryption, and TMSI reallocation and subscribers can make emergency calls with the IMEI
(no need to insert the SIM card).
l
Subscribers may not be fully redistributed in a certain period for reasons such as calls in
progress. In this case, you can determine whether the redistribution is complete and proceed
with the next step.
The E interface redirection must be based on Phase 2 and later versions of MAP.
Application Scenarios
Subscriber migration between MSCs in the MSC Pool can be applied in the following scenarios:
l
Transferring all subscribers

Before upgrading one or more MSCs in the MSC Pool, you need to transfer all the
subscribers in the MSC or MSCs to other MSCs in the MSC Pool to avoid impact on
subscriber services.
Transferring part of subscribers

In the example above, after the MSC or MSCs are upgraded, need to transfer part of
subscribers from other MSCs back to the upgraded MSC or MSCs.
You must specify the number of subscribers or the proportion (to the current registered
subscribers) of subscribers to be transited. When the number of transited subscribers
reaches the specified number or proportion, the migration is stopped automatically.
Transiting subscribers in the specified RNC/BSC

To avoid impact on subscriber services in the RNC/BSC when the RNC/BSC in MSC Pool
1 is to be taken over by MSC Pool 2, connect the RNC/BSC to MSC Pool 2 (all the MSCs
in the RNC/BSC, MSC Pool 1 and MSC Pool 2 actually form a new pool) and transit
subscribers of MSCs in MSC Pool 1 to MSCs in MSC Pool 2. After transiting subscribers,
disconnect the RNC/BSC with MSC Pool 1.
MSCs can transit subscribers in the specified RNC/BSC area through O&M configuration.
The system supports migration of subscribers in up to 10 RNC/BSC areas at the same time.
Transiting subscribers in the specified LA

Through O&M configuration, MSCs can transit subscribers in the specified LA only. The
system supports migration of subscribers in up to 10 LAs at the same time.
Transiting specified subscribers

To conduct the dialing test, you need to transit subscribers registered in MSC1 in the MSC
Pool to MSC2.
Through O&M configuration, an MSC can transit specified subscribers based on the
MSISDNs and IMSI numbers. The system supports migration of up to 10 subscribers at
the same time.
CAUTION
In the above scenarios, subscribers can be transited to one or more MSC in the MSC Pool.
1.3.7 Load Balancing at the MGW

This section describes the principle of MGW load balancing in MSC Pool feature.
Issue 02 (2008-04-10)

1-17

1 Overview
Selecting MGW Based on Load Balancing

When an MSC server controls multiple MGWs which are connected to the same RNC/BSC, the
MSC server selects an MGW for a subscriber who initiates a service request in the RNC/BSC
area based on load balancing.
1.
For a 2G subscriber: The MSC server selects an MGW based on the ratio of the statically
configured MGW circuit number to the available idle circuit number.
2.
For a 3G subscriber: The MSC server selects an MGW based on the bearer capacity that is
statically configured on the MGW.
Preferred MGW
For intra-MSC calls in the MSC Pool, if one MGW serves the calling party and the called party
simultaneously, the system selects the same MGW as a preferred MGW to establish the call to
avoid using too many voice circuits between MGWs.
For inter-MSC calls in the MSC Pool, if one MGW serves the calling party and the called party
simultaneously (two VMGWs of a physical MGW serve the calling party and called party), the
originating and terminating MSCs select the same MGW as a preferred physical MGW to
establish the call to avoid using too many voice circuits between MGWs.
1.3.8 A-Flex Function Proxy on the MGW

This section describes the principle of A-Flex function proxy on the MGW in MSC Pool feature.
Background
The 3GPP TS 23.236 protocol requires the BSC in the MSC Pool supporting the A-flex function
(that is, the BSC must be able to identify all MSCs in the MSC Pool and select MSC to share
the load of subscriber services.)
When the MSC Pool networking mode is applied to the present network, you need to upgrade
BSCs on the present network to enable the A-Flex function. BSCs on the present network,
however, may not support the A-Flex function. There are too many BSCs in the present network.
BSCs of different vendors may not support the A-Flex function. Therefore, it is difficult to
upgrade BSCs on the present network to support the A-Flex function.
To solve the above problem, Huawei MGW can be used to provide the A-Flex function proxy.
When Huawei MGW is deployed in the network, BSCs on the present network can access the
MSC Pool without upgrade.
Implementation Principle
A BSC on the present network can connect with one MSC server (a signaling point) only. To
enable the BSC to access the MSC Pool without being upgraded (connect multiple signaling
points), the MGW must shield different MSC servers for the BSC. The MGW needs to provide
the BSC with a unified signaling point. To achieve this purpose, the following two signaling
networking modes can be used: M3UA agent networking and M3UA forward networking, as
shown in Figure 1-12 and Figure 1-13. In addition, the networking of using MGW to provide
the A-flex function can coexist with the networking of using RNC/BSC to provide the Iu/A-flex
function.
1.
1-18
3UA agent networking

Issue 02 (2008-04-10)

1 Overview
Figure 1-12 A-Flex function proxy on the MGW (M3UA agent networking)
MSOFTX3000 A
MSOFTX3000 B
AA,XX
AA,YY
MGW2
AA
MGW1
AA
BSC1
2.
Issue 02 (2008-04-10)
BSC2
BSC3
BSC3
MSC servers in the MSC Pool establish signaling connections with BSCs through the
same signaling point code AA (signaling point codes XX and YY are used to establish
signaling connections with NEs of the core network).
The MGW adopts the M3UA agent mode. It shares the same signaling point code with
MSC servers, that is, AA.
The MGW is divided into several virtual MGWs whose numbers are the same as those
of the MSC servers. Each VMGW is registered in an MSC server. Allocation of
VMGWs is invisible to BSCs.
A BSC is allowed to be connected with multiple (a maximum of five) physical MGWs

(It is suggested to connect a BSC to one MGW when the A interface is used between
the BSC and the MGW over TDM). When a BSC is connected with multiple physical
MGWs, the BSC selects different MGW to set up signaling links based on the link
balancing principle. The MSC server selects a preferred MGW to set up the voice
channel based on the load balancing principle.
The signaling point configured on the BSC to interwork with the MSC server is AA.
Using the MGW to provide the A-flex function: After resolving the IMSI/IMEI from
the subscriber message or the TMSI from the NRI, the MGW routes the subscriber
message to the corresponding MSC server based on the IMSI/IMEI or NRI. The
algorithm for the MGW to select the MSC server is the same as that for the BSC to
implement the A-flex function.
M3UA forward networking

1-19

1 Overview
Figure 1-13 A-Flex function proxy on the MGW (M3UA forward networking)
MSOFTX3000 A
MSOFTX3000 B
BB,XX
CC,YY
MGW1
AA,DD
MGW2
BSC1
AA,EE
BSC2
BSC3
BSC3
MSC servers in the MSC Pool establish signaling connections with BSCs through
signaling point codes BB and CC.
The MGW adopts the M3UA signaling forward mode. It uses signaling points DD and
EE for MSC servers and the same singling point AA for BSCs.
The MGW is divided into several VMGWs whose numbers are the same as those of
MSC servers. Each VMGW is registered in an MSC server. Allocation of VMGWs is
invisible to BSCs.
A BSC is allowed to be connected with multiple (a maximum of five) physical MGWs

(It is suggested to connect a BSC to one MGW when the A interface is used between
the BSC and the MGW over TDM). When a BSC is connected with multiple physical
MGWs, the BSC selects different MGW to set up signaling links based on the link
balancing principle. The MSC server selects a preferred MGW to set up the voice
channel based on the load balancing principle.
The signaling point configured on the BSC to interwork with the MSC server is AA.
Using the MGW to provide the A-flex function: After resolving the IMSI/IMEI from
the subscriber message or the TMSI from the NRI, the MGW routes the subscriber
message to the corresponding MSC server based on the IMSI/IMEI or NRI. The
algorithm for the MGW to select the MSC server is the same as that for the BSC to
implement the A-flex function.
In addition, the networking of using MGW to provide the A-flex function can coexist with the
networking of using RNC/BSC to provide the Iu/A-flex function, as shown in Figure 1-14 and
Figure 1-15.
1-20

Issue 02 (2008-04-10)

1 Overview
Figure 1-14 Mixed networking of A-Flex function proxy on MGW and Iu/A-Flex function proxy
on the RNC/BSC (1)
MSOFTX3000 A
MSOFTX3000 B
AA,CC,YY
AA,BB,XX
MGW1
BSC1
MGW2
AA,EE
AA,DD
BSC2
BSC3
RNC1
MSC servers use multiple signaling points for BSCs on the access network. Signaling point
AA shared by MSC servers is used for BSCs that do not support the A-Flex function.
Signaling points BB and CC for MSC servers are used for the RNC/BSCs that support the
Iu/A-Flex function. Signaling points XX and YY are used for HLR and STP.
The MGW uses the same signaling point (AA) to connect with the BSCs that do not support
the A-Flex function. The MGW also uses different signaling points (DD and EE) to connect
with the BSCs that support the Lu/A-Flex function. It decides whether to enable the A-Flex
function according to configuration of signaling points at the access network.
The MGW connects with the BSCs that do not support the A-Flex function through the
M3UA signaling agent mode and M3UA signaling forward mode. The MGW connects
with the BSCs that support the Iu/A-Flex function through M3UA signaling forward mode.
Figure 1-15 Mixed networking of A-Flex function proxy on MGW and Iu/A-Flex function proxy
on the RNC/BSC (2)
MSOFTX3000 A
MSOFTX3000 B
AA,CC,YY
AA,BB,XX
MGW1
BSC1
Issue 02 (2008-04-10)
MGW2
EE
AA
BSC2
BSC3
RNC1

1-21

1 Overview
l
MSC servers use multiple signaling points for BSCs on the access network. Signaling point
AA shared by MSC servers is used for BSCs that do not support the A-Flex function.
Signaling points BB and CC for MSC servers are used for the RNC/BSCs that support the
Iu/A-Flex function. Signaling points XX and YY are used for HLR and STP.
MGW1 only connects with the BSC that does not support the A-Flex function. It enables
the A-Flex agent function.
MGW2 only connects with the RNC that supports the Iu-Flex function. It implements
signaling transfer only.
Networking Suggestion
It is recommended to use M3UA forward mode first for networking of A-Flex function proxy
on MGW.
The M3UA forward mode is better than the M3UA agent mode in the case of mixed networking
mode. For example, Figure 1-16 the mixed networking in the M3UA agent mode, and Figure
1-14 shows the mixed networking in the M3UA forward mode. For the former, two sets of
signaling point need be configured and two sets of independent M3UA data configuration on
MSC servers are required, which obviously complicates networking. Therefore, use the M3UA
forward mode for the networking mode in which use A-Flex function proxy on the MGW.
In the case of Non-mixed networking, the M3UA agent mode can be used if the number of
signaling points is limited.
Figure 1-16 Mixed networking of MGW used for providing A-Flex function and RNC/BSC
providing Iu/A-Flex function (M3UA forward networking)
MSOFTX3000 A
MSOFTX3000 B
CC,YY
BB,XX
MGW1
BSC1
MGW2
AA,EE
AA,DD
BSC2
BSC3
RNC1
1.3.9 MGW Managing Circuits of the A Interface

This section describes the principle of MGW managing circuits of the A interface.
The current circuits on the A interface are managed by MSC servers. In the MSC Pool networking
mode, the A-interface circuits of one BSC are managed by multiple MSC servers. This design
causes inconvenience on resource utilization and maintenance. To solve this problem, Ainterface circuits need to be shared among MSC servers. In this case, the circuits need to be
managed by the MGW, as shown in Figure 1-17 and Figure 1-18.
1-22

Issue 02 (2008-04-10)

1.
1 Overview
In the MSC Pool networking, the following problems occur when MSC servers manage Ainterface circuits.
Figure 1-17 MSC server managing A-interface circuits
MSOFTX3000 A
MSOFTX3000 B
MGW1
BSC1
2.
Issue 02 (2008-04-10)
After the MSC Pool is formed, A-interface circuits are used less efficiently. The Ainterface TDM circuits of a BSC originally managed by one MSC server are managed
by different MSC servers. Each MSC server use resources allocated for it, which
degrades the re-use efficiency for A-interface circuits. To support the traffic before
BSCs access the MSC Pool, A-interface TDM circuits need to be added.
The following example can help to understand degradation of re-use efficiency:

Suppose, there are 100 people in a company, and 10 vehicles can just meet the demand.
When the company is divided into 10 subsidiaries with 10 people and one vehicle
allocated for each subsidiary, the vehicles of some subsidiaries may not meet demands
whereas the vehicles of some subsidiaries may be idle.
After the MSC Pool is formed, it is complicated to plan and adjust A-interface circuits.
When an MSC server is added in the MSC Pool, the A-interface TDM circuits of all the
MSC servers in the MSC Pool must be planned and adjusted again.
After the MSC Pool is formed, it is complicated to maintain A-interface circuits on a

routine basis. When blocking a circuit, the operator must find the MSC server that
manages the circuit. If the circuit to be blocked is managed by different MSC servers,
the operator has to block the circuit on the MSC servers respectively.
Solution to management of A-interface circuits

1-23

1 Overview
Figure 1-18 MGW managing A-interface circuits

MSOFTX3000 A
MSOFTX3000 B
MGW1
BSC1
MSC servers do not configure or manage A-interface circuits. The MGW is responsible
for configuring and managing A-interface circuits. The data of signaling and A-interface
trunks from the MSC servers to the BSCs is configured on the MSC servers for
performance measurement purposes.
When MSC servers send A-interface circuits request to the MGW, the MGW is
responsible for distributing and managing A-interface circuits.
Routine circuit operation & maintenance commands are transferred from the MSC
server to the MGW. The MGW is responsible for maintaining and managing A-interface
circuits on a routine basis.
In this way (that is, the MGW manages A-interface circuits), A-interface circuits can
be shared among MSC servers in the MSC Pool.
1.3.10 Charging Principle

This section describes the principle of charging in MSC Pool feature.
Charging Based on Virtual MSC ID

Charging based on virtual MSC ID is to allocate an MSC ID (a physical MSC is divided into
multiple virtual MSCs based on charge areas) for each charge area (that is, LAN). When a
subscriber is in a charge area, the subscriber is registered in the virtual MSC of the charge area.
The MSC ID of the subscriber stored in the HLR is the virtual MSC ID of the charge area. In
this way, the system can identity the charge areas of the calling and called subscribers. As a
result, it can charge subscribers according to their charge areas, as shown in Figure 1-19.
1-24

Issue 02 (2008-04-10)

1 Overview
Figure 1-19 Charging based on virtual MSC ID

MSC Pool
MSC1
(MSCa, MSCb)
RNC1/
BSC1
MSC2
(MSCc, MSCd)
RNC2/
BSC2
MS/UE
RNC3/
BSC3
MS/UE
Charging area 1
Charging area 2
MSC Pool area
This charging mode is the same as the charging based on multi-area network.
The charging based on virtual MSC ID has the following limitations:
l
An RNC/BSC cannot belong to two charging areas.
When a subscriber roams from one charging area to another, the inter-MSC location update
is required. In this case, the MSOFTX3000 must interwork with the HLR through the C/D
interface and the virtual MSC ID on the HLR is updated.
Charging Based on Location Area

As for charging based on location area, LAIs are filled in MOC and MTC bills generated by the
local MSC, and the local MSC allocates MSRNs according to LAIs. In this case, the GMSC can
obtain location information of the called party through the MSRN allocated for the called party.
In this way, subscribers can be charged. In addition, to implement charging for intelligent
subscribers in the case of Free Roaming to Same City, the SCP needs to use the ATI process
during the call origination or call termination to obtain locations of the calling and called parties.
As a result, the calling and called parties can be charged correctly.
It is recommended to select charging based on location area by preference.
Compared with charging based on virtual MSC ID, charging based on location area helps to
save MSC IDs and simplify data configuration and planning. If the SCP and HLR do not support
the ATI and PSI processes or the BOSS system does not support charging based on location
area, charging based on virtual MSC ID can be adopted.
The charging based on location area has the following limitations:
l
The SCP and the HLR must support the ATI process. The HLR and the MSC must support
the PSI process.
One LA can belong to only one multi-area network.
Issue 02 (2008-04-10)

1-25

1 Overview
l
If the performance measurement and charging based on the multi-area networking are both
enabled, the area covered by the local networks for the charging must contain (or at least
level) the area covered by the local networks for the performance measurement.
Cross-Time Zone
When an MSC Pool area covers multiple time zones, MSCs in the MSC Pool can send the correct
time zones (the time zones can be accurate to LA or cell) where subscribers are located currently
to subscribers.
1.4 M2000 Application in the MSC Pool

This section describes the application of the M2000 in the MSC Pool feature.
1.4.1 M2000 Function
This section describes the main functions of M2000 in MSC Pool network.
1.4.2 M2000 Application Scenario
This section describes the application scenario of M2000.
1.4.1 M2000 Function

This section describes the main functions of M2000 in MSC Pool network.
In the MSC Pool networking, the M2000 supports the following:
1-26
Parameter management related to the MSC Pool feature: It supports centralized

configuration and management on the parameters related to the MSC Pool feature.
Real-time traffic monitoring with the shortest interval of 30 seconds: It supports the
monitoring of the number of idle subscribers, number of power-off subscribers, total
number of subscribers, and CPU usage rate of the MSC server, and the context information
of the MGW, with the shortest interval of 30 seconds.
Performance measurement for whole MSC Pool: It collects the commonly used KPI indexes
at the MSC Pool level and provides the general KPI indexes for whole MSC Pool.
Data consistency check and synchronization: It periodically checks whether the data of the
NEs in the MSC Pool is consistent. If not, it generates a data synchronization script to
synchronize the data.
Subscriber migration within the MSC Pool: It supports subscriber migration in the MSC
Pool. You can generate a migration task and monitor the status of the migration.

Issue 02 (2008-04-10)

1 Overview
Figure 1-20 Application of the M2000 in the MSC Pool

M2000 system
WAN/LAN
MSOFTX3000 A
MSOFTX3000 B
MGW 1
BSC1
MGW2
BSC2
BSC3
BSC4
1.4.2 M2000 Application Scenario

This section describes the application scenario of M2000.
For details, see 9 Routine Maintenance.
Issue 02 (2008-04-10)

1-27

2 Networking Description
Networking Description
About This Chapter

This section describes the signaling networking scheme of an MSC Pool.
In the MSC Pool network, if the BSC/RNC can provide the A-Flex/Iu-Flex function, the MGW
does not provide the A-Flex function. For the signaling networking scheme in this case, see
section 2.1 Signaling Networking Scheme of an MSC Pool (BSC/RNC Providing the AFlex/Iu-Flex Function).
If the BSC cannot provide the A-Flex function, the MGW must provide the A-Flex function.
For the networking scheme in this case, see section 2.2 Signaling Networking Scheme of an
MSC Pool (MGW Providing the A-Flex Function).
2.1 Signaling Networking Scheme of an MSC Pool (BSC/RNC Providing the A-Flex/Iu-Flex
Function)
This section describes the signaling networking schemes of the MSC Pool based on TDM, IP,
and ATM.
2.2 Signaling Networking Scheme of an MSC Pool (MGW Providing the A-Flex Function)
This section describes the typical signaling networking scheme adopted for an MSC Pool in the
case that the MGW provides the A-Flex function.
2.3 Networking Scheme for Connecting CN NEs Inside and Outside an MSC Pool
This section describes the connection between the core network (CN) NEs inside an MSC Pool
and the CN NEs outside of the MSC Pool.
2.4 Networking Scheme for Subscriber Data Backup
This section describes the networking scheme for subscriber data backup.
2.5 Networking Scheme for Voice Channels Related to an MSC Pool
This section describes the network scheme for voice channels related to an MSC Pool.
Issue 02 (2008-04-10)

2-1

2.1 Signaling Networking Scheme of an MSC Pool (BSC/

RNC Providing the A-Flex/Iu-Flex Function)
This section describes the signaling networking schemes of the MSC Pool based on TDM, IP,
and ATM.
When the BSC/RNC instead of the MGW provides the A-Flex or Iu-Flex function, the signaling
networking schemes of an MSC Pool are determined based on the bearer network mode on the
Iu/A interface between the access network and the CN.
2.1.1 TDM-Based A Interface
This section describes the networking scheme when the A interface between the BSC and the
MGW is based on TDM.
2.1.2 ATM-Based Iu Interface
This section describes the networking scheme when the Iu interface between the RNC and MGW
is based on ATM.
2.1.1 TDM-Based A Interface

This section describes the networking scheme when the A interface between the BSC and the
MGW is based on TDM.
When the A interface between the BSC and the MGW is borne on TDM, the networking scheme
as shown in Figure 2-1 must be adopted.
This networking scenario is as follows:
2-2
Each BSC has a unique signaling point code (SPC).
The TDM bearer is adopted for the interworking between the BSC and the MGW.
The MGW has a unique SPC.
The IP bearer is adopted for the interworking between MGWs and between the MGW and
the MSC server.
Each MSC server has a unique SPC.
The MTP3 data must be configured for the interworking between the BSC and the MGW.
The M3UA data must be configured for the interworking between the MGW and the MSC
server.
Data must be configured for transferring the signaling between the MSC server and the
BSC.

Issue 02 (2008-04-10)

Figure 2-1 MSC Pool networking adopted when the A interface between the BSC and the MGW
is based on TDM
MSOFTX3000 A
MSOFTX3000 B
MGW1
BSC1
MGW2
BSC2
BSC3
IP bearer
BSC4
TDM bearer
2.1.2 ATM-Based Iu Interface

This section describes the networking scheme when the Iu interface between the RNC and MGW
is based on ATM.
When the Iu interface between the RNC and the MGW is based on ATM, the networking scheme
as shown in Figure 2-2 must be adopted.
This networking scenario is as follows:
l
Each RNC has a unique SPC.
The ATM bearer is adopted for the interworking between the RNC and the MGW.
The MGW has a unique SPC.
The IP bearer is adopted for the interworking between the MGW and the MSC server.
Each MSC server has a unique SPC.
The M3UA data must be configured for the interworking between the MGW and the MSC
server.
Data must be configured for transferring the signaling between the MSC server and the
RNC.
Issue 02 (2008-04-10)

2-3

Figure 2-2 MSC Pool networking adopted when the Iu interface between the RNC and the MGW
is based on ATM
MSOFTX3000 A
MSOFTX3000 B
MGW2
MGW1
RNC1
RNC2
IP bearer
RNC3
RNC4
ATM bearer
2.2 Signaling Networking Scheme of an MSC Pool (MGW

Providing the A-Flex Function)
This section describes the typical signaling networking scheme adopted for an MSC Pool in the
case that the MGW provides the A-Flex function.
A BSC in the existing network can be connected to only one MSC server (a single signaling
point). To enable the BSC to be connected to the MSC Pool (multiple MSC servers) without a
need to upgrade the BSC, the MGW must provide the BSC with a uniform signaling point so
that the BSC has no knowledge about which MSC server it is interworking with. To achieve this
purpose, the following two signaling networking modes can be used:
l
M3UA agent mode
M3UA forwarding mode
If the available signaling points are insufficient for the MSC pool to use the M3UA forwarding
mode, the M3UA agent mode can be used. If the signaling points are sufficient for the M3UA
forwarding mode, then this mode is preferred. For details about the networking schemes, see
1.3.8 A-Flex Function Proxy on the MGW.
2.3 Networking Scheme for Connecting CN NEs Inside and

Outside an MSC Pool
This section describes the connection between the core network (CN) NEs inside an MSC Pool
and the CN NEs outside of the MSC Pool.
The networking scheme for connecting CN NEs inside and outside an MSC Pool is the same as
the networking scheme for connecting CN NEs without an MSC Pool except that certain changes
2-4

Issue 02 (2008-04-10)

must be made to the networking of the STP and the HLR for connecting CN NEs inside and
outside an MSC Pool.
In an MSC Pool network, to enable the restoration of the call termination, the PRN signaling
must be backed up. The backup can be implemented with the following methods:
l
Configure the route priorities
Enable load sharing of the SCCP signaling points
For details about the networking schemes, see the description related to the backup of PRN
signaling messages in Call Termination Recovery Principle. For details about the
configuration examples, see Configuring PRN Signaling Backup Data.
2.4 Networking Scheme for Subscriber Data Backup

This section describes the networking scheme for subscriber data backup.
To enable the call termination recovery in an MSC Pool network, subscriber data must be backed
up. The backup can be implemented by using the following methods:
l
Centralized backup
The data configuration for the centralized backup is simple. An additional MSC, however,
is required for the backup in this method.
Chain backup
The data configuration for the chain backup is complex. MSCs in the MSC Pool can back
up subscriber data for one another, thus reducing the number of MSCs.
In applications, the networking scheme must be determined based on existing network conditions
and customer requirements. For details about the networking scheme, see the related description
for subscriber data backup in Call Termination Recovery Networking. For details about the
configuration examples, see Configuring Chain Backup Data and Configuring Centralized
Backup Data.
2.5 Networking Scheme for Voice Channels Related to an

MSC Pool
This section describes the network scheme for voice channels related to an MSC Pool.
Voice channels related to an MSC Pool are classified into two types, voice channels in the MSC
Pool and voice channels between the MSC Pool and the PSTN, other PLMN, or other VMSCs.
Voice Channels in the MSC Pool

Voice channels in the MSC Pool refer to the voice channels between the MGW and the BSC/
RNC. The networking scheme for voice channels in the MSC Pool is as follows:
l
The MGW is directly connected to the BSC. Voice channels between the MGW and the
BSC are based on TDM bearer.
The MGW is directly connected to the RNC. Voice channels between the MGW and the
RNC are based on ATM bearer.
Voice channels between MGWs are based on IP bearer.
Issue 02 (2008-04-10)

2-5

Voice Channels Between the MSC Pool and the PSTN, Other PLMN, or Other
VMSCs
Direct voice channels are set up between all MGWs in the MSC Pool and the GMSC (TMSC).
The MGW interworks with external networks through the GMSC. The MGW interworks with
local or remote MSCs through the TMSC.
2-6

Issue 02 (2008-04-10)

3 MSC Pool Network Planning
MSC Pool Network Planning
About This Chapter

This section describes the network planning principles and system specifications of the MSC
Pool.
3.1 Limitations
This section describes the limitations that affect the network planning of an MSC Pool.
3.2 MSC Pool Network Specifications
This section describes the relevant specifications of an MSC Pool network.
3.3 General Principles of the MSC Pool Planning
This section describes the principles of the planning of an MSC Pool network.
Issue 02 (2008-04-10)

3-1

3.1 Limitations
This section describes the limitations that affect the network planning of an MSC Pool.
The limitations that affect the network planning of an MSC Pool are as follows:
l
The MSC Pool feature described in this document is applicable to only the GSM/UMTS
networks.
The MSC Pool feature conflicts with the dual-homing feature. You cannot have both
features active.
3.2 MSC Pool Network Specifications

This section describes the relevant specifications of an MSC Pool network.
Table 3-1 lists the relevant specifications of an MSC Pool network.
Table 3-1 MSC Pool network specifications
Item
Index
Value
Maximum capacity supported by

an MSC Pool
Number of MSC servers
32
Number of MGWs
300
Number of RNCs/BSCs
128
Number of LAs/cells
30,000
Number of local networks
16
Number of intercepted
subscribers
If the number of intercepted

subscribers is set on all the
MSCs of an MSC Pool, up to
40,000 subscribers are
supported (if the
interception data is
configured on the specified
MSC, there is no such
restriction).
Number of virtual MGWs
32 (A MGW can be
connected to 32 MSC
servers at the same time.)
Number of connected
RNCs (ATM networking
mode)
50
Number of connected
BSCs (TDM networking
mode)
50

an MGW
3-2

Issue 02 (2008-04-10)

Item

an RNC

a BSC
Index
Value
Number of connected
BSCs/RNCs (IP
networking mode)
128
Number of connected
MSC servers
32
Number of connected
MGWs (ATM networking
mode)
32
Number of connected
MSC servers
32
Number of connected
MGWs (TDM networking
mode)
NOTE
When the centralized backup method is used for the VLR data backup solution, the maximum number of
active MSC servers in an MSC Pool is 31.
Table 3-2 lists the length of an NRI, number of NRIs, and the maximum number of subscribers
that are supported by an MSC server.
Table 3-2 NRI planning reference data
Issue 02 (2008-04-10)
Length of NRI
Number of NRIs
Maximum Number of Subscribers
<=6 bits
3,200,000
7 bits
1,600,000
7 bits
3,200,000
8 bits
800,000
8 bits
1,600,000
8 bits
2,400,000
8 bits
3,200,000
9 bits
400,000
9 bits
800,000
9 bits
1,200,000
9 bits
1,600,000
9 bits
2,000,000
9 bits
2,400,000

3-3

Length of NRI
Number of NRIs
Maximum Number of Subscribers
9 bits
2,800,000
9 bits
3,200,000
10 bits
20 x N x 10,000
NOTE
The VLR on the MSC server adopts the distributed structure and is composed of multiple WVDBs (up to
10 pairs). Each WVDB can support up to 500,000 TMSI numbers and 200,000 subscribers.
3.3 General Principles of the MSC Pool Planning

This section describes the principles of the planning of an MSC Pool network.
Planning of the Target Network

A prerequisite for building an MSC Pool is that IP transmission is adopted for connection
between the MSC servers and the MGWs, in a pool and also IP transmission is adopted between
MGWs. The following descriptions are all based on this prerequisite.
The MSC Pool feature implements its service distribution based on the number of subscribers;
MSC Pool networking is applicable only to the VMSCs. (It is not recommended that the MSCs
in an MSC Pool function as GMSCs or TMSCs.)
The target network topology of a 2G office is the same as that of a 3G office. The following
planning principles are employed:
3-4
The access networks must be connected in mesh mode for an MSC Pool networking to
achieve the traffic balance and reduce the handover of the inter-MSC roaming.
IP-based Nb interface is a basis for the MSC Pool networking. It requires that all VMSCs
within an MSC Pool adopt the softswitch architecture and the VMSCs must support the
same services and functions.
The capacity of each MSC server within an MSC Pool is suggested to be the same. It is not
recommended that MSC servers cannot serve BSCs/RNCs which are outside the MSC Pool.
All BSCs/RNCs must be connected to all MSC servers within an MSC Pool through
signaling. When the BSC/RNC cannot support the A/Iu-Flex function in the preliminary
stage, the A/Iu-Flex function is implemented by the MGW. For a 3G system, it is
recommended to build an MSC Pool after the implementation of the Iu-Flex function by
the RNC. In the case of non-IP-based A/Iu interface, the BSC/RNC must be connected to
two MGWs at most, unless certain special requirements are raised. Either the M3UA agent
mode or M3UA forward mode can be adopted, but the M3UA agent mode is recommended.
MSC servers within an MSC Pool should be installed in two or more physical locations to
accommodate disaster recovery cases. If a BSC/RNC is connected to two or more MGWs,
the MGWs should be installed in different locations to meet the transmission requirements.
For signaling networking, MSC servers within an MSC Pool must be connected to pure
signaling point NEs, such as the SMC, SCP, and HLR in STP forward mode. The STP must
be directly connected to the MSC servers. The BICC trunk signaling is transmitted to the
MSC server directly while the ISUP or TUP trunk signaling are transferred by the MGW.
Issue 02 (2008-04-10)

The connection mode of the ISUP or TUP trunk signaling is generally the same as that of
speech path.
l
For voice trunk networking, all the NEs within an MSC Pool must be connected to the
TMSC to which the traffic is transmitted, and connected to the GMSC that serves the MSC
Pool. When the TMSC/GMSC supports the VoIP, the direct connection over IP is adopted.
Otherwise, the TMSC/GMSC must be connected to a pair of MSC servers and a pair of
MGWs within the MSC Pool. In the case of network evolution to support the MSC Pool,
the TMSC/GMSC is already connected to all MSCs in the MSC Pool, and the original
connection mode an be retained.
An MSC Pool must be connected to VMSCs outside the MSC Pool of the local network.
If the voice channel of the VMSC support the VoIP, the direction connection mode over
IP is adopted; otherwise, the traffic is transferred by the GMSC or TMSC.
An MSC Pool must be connected to VMSCs out of the local network and the original
connection mode can be retained.
The signaling and voice circuits between the MSC servers within an MSC Pool and the
PSTN can be transferred through the GMSC. For the original direct connection between
the PSTN and the MSC servers, you must change the direct connection to the connection
through the GMSC. If no GMSC is present, you are advised to connect the PSTN to a pair
of MSC servers and a pair of MGWs. In the case of network evolution to the MSC Pool,
no GMSC is present, the PSTN is already connected to all MSCs in the MSC Pool, and the
original connection mode can be retained.
The MSCs within an MSC Pool must not function as the GMSC/TMSC. The reasons are
as follows:
The VMSC functioning as the GMSC/TMSC does not follow the evolution tendency
that an NE plays a single role.
The VMSC functioning as the GMSC/TMSC may cause the unbalance of load within
an MSC Pool.
If the VMSC functions as the GMSC/TMSC, the MGW requires a large number of TC
resources.
Planning Items for the MSC Pool Feature

Table 3-3 lists the items of an MSC Pool planning.
Issue 02 (2008-04-10)

3-5

Table 3-3 Items of an MSC Pool planning

Items
Description
MSC Pool area planning
The area with heavy traffic and the adjacent area with light
traffic should be distributed into the same MSC Pool area.
For an area, where residents move frequently, such as a

city and its suburbs, build a single MSC Pool. Thus, the
number of updates between CN nodes can be reduced.
It is recommended to configure 4 to 16 MSC servers

within an MSC Pool. The MSC Pool should be able to
support 4,000,000 to 24,000,000 subscribers. The capacity
of an MSC server within an MSC Pool should support
1,000,000 to 1,500,000 subscribers.
Generally, the MSCs within an MSC Pool cannot serve

the RNCs/BSCs outside the MSC Pool.
Each CN node within an MSC Pool should provide the

same service and adopt the same charging strategy.
Each MSC server within an MSC Pool should have the

same capacity, and thus simplifying the maintenance and
planning.
Actual installation rate = Actual number of subscribers on

an MSC server / MSC server capacity (Usually, the value
of the actual installation rate cannot be more than 80% as
required by a carrier. You can configure the actual
installation rate based on actual conditions.)
The capacity of the MGW is calculated based on the

capacity of the total number of RANs/BSCs which are
connected to the MGW.
Certain capacity should be reserved because more RANs/

BSCs may be accessed into the MGW.
The NRI is bit 23 through bit 14 of the TMSI. The length

of the NRI ranges from 0 bit to 10 bits.
The NRIs in the neighboring MSC Pool areas should be

unique and have the same length. The NRIs in the whole
network should be planned on a uniform basis.
See Table 3-1 for the details on the relationship between

the length and number of NRIs and the supportable
number of subscribers.
The Null-NRI and the NRI should be planned on a uniform

basis. The maximum or minimum value of the NRI in an
NRI set within an MSC Pool can be selected based on the
actual conditions.
The Null-NRI within an MSC Pool must be unique.
NE
capacity
planning
MSC server
MGW
MSC Pool
common
attribute
planning
3-6
NRI planning

Issue 02 (2008-04-10)

Items
Description
Default MSC
planning
The default MSC could be any one MSC within an MSC

Pool. If only one MSC is set to the default MSC, the MSC
might be affected by heavy traffic and thus the single-point
failure may occur. Therefore, configure all the MSCs in an
MSC Pool to the default MSC.
Non-broadcast
LAI planning
The non-broadcast LAI is encoded together with ordinary

NRIs on a uniform basis, but it cannot be the same as any
LAI already configured in the MSC Pool. You can
configure the non-broadcast LAI according to the
descending order or ascending order based on actual
configuration of the LAI.
Each MSC in an MSC Pool should be configured with a

non-broadcast LAI of the local office and an MSC maps
a unique non-broadcast LAI.
Bandwidth planning of
signaling network
MSC ID planning
MSC server backup planning

during the VLR data backup
Issue 02 (2008-04-10)
The planning of the signaling network bandwidth consists of

the planning of the following:
l
A/Iu interface
Mc interface
E interface
Nc interface
C/D interface
ISUP signaling
When charging based on virtual MSC ID is adopted, the

formula of calculating the number of MSC IDs planned
for each MSC Pool is as follows: Number of MSC IDs of
each MSC Pool = Number of MSC IDs configured on each
MSC server in the MSC Pool x Number of MSC servers
in the MSC Pool Note that the number of MSC IDs
configured on each MSC server equals to the number of
charging areas of an MSC server.
One MSC server is configured with one MSC ID in the

case of no special requirement.
Centralized backup of the WVDB configuration: 2 x

Roundup (backup subscriber quantity/6,000,000). In this
case, the whole memory is used for backup, but the
capacity of 6,000,000 subscribers is recommended.
Chain backup of the WVDB configuration: 2*Roundup

(backup subscriber quantity/500,000). A pair of backup
WVDBs can process the services of 200,000 subscribers.
Therefore, if the MSC server is configured with more than
four pairs of VDBs, you need not configure other backup
boards.

3-7

Items
Description
Bandwidth planning of voice

trunk network
The planning of the voice trunk network bandwidth consists

of the planning of the following:
Bandwidth planning of bearer

network
3-8
A/Iu interface
Nb interface
Relevant parameters of the MGW
Bandwidth for ISUP TDM traffic
The planning of the bearer network bandwidth consists of the

planning of the following:
l
Nb interface
Nc interface
Mc interface
Reserved bandwidth of the VDB

Issue 02 (2008-04-10)

4 Commands and Parameters Related to MSC Pool
Commands and Parameters Related to MSC

Pool
About This Chapter

This section describes the commands and parameters related to the MSC Pool feature, in
particular the key parameters, global data, and values of software parameters. The information
in this chapter guides you to correctly and promptly understand and configure the data about the
MSC Pool feature.
4.1 Commands Used on the MSC Server
This section describes commands and parameters used on the MSC server to implement the
MSC Pool feature.
4.2 Commands Used on the MGW
This section describes commands and parameters used on the MGW to implement the MSC Pool
feature.
4.3 Global Data and Software Parameters
This section describes important global data and software parameters used on the MSC server
to implement the MSC Pool feature.
Issue 02 (2008-04-10)

4-1

4.1 Commands Used on the MSC Server

This section describes commands and parameters used on the MSC server to implement the
MSC Pool feature.
SET POOLINFO
Descr
iption
This command is used to set the MSC Pool function information.
Script
SET POOLINFO: MSCPOOL=NO, SERVER=YES, MSCIDX=1, BACKUP=NO,

USRNUM=100, NRILEN=6;
Rema
rk
If the Function flag of MSC POOL parameter is set to Yes, the MSOFTX3000
can directly interwork with the BSC that supports the NNSF function. If the MGW
provides the A-Flex function, set the parameter to No.
If the Flag of MGW providing MSC POOL function parameter is set to Yes, the
MGW can provides the A-Flex function. If the MSC Pool interworks with ordinary
BSCs, set the parameter to Yes.
The value of the MSC Identity in MSC POOL parameter must be consistent with
the value of the MSC Index parameter in the ADD CNNODE command used on
the MGW.
The Length of NRI bit parameter is set to 6, indicating that six bits in the TMSI
are reserved for the NRI. The NRI of all network elements in the Pool must have
the same length.
ADD NRIMSC
Descr
iption
This command is used to set the NRI information of the MSC server.
Script
ADD NRIMSC: DESC="SZPLSRV_1", NRIV=24, MSCNO=K'8613507001,

VLRNO=K'8613507001, MSCNM="SZPLSRV_1", NNRI=FALSE;
Rema
rk
The NRI value parameter is set to 24, indicating that the NRI value is 24. This
parameter works together with the Length of NRI bit parameter (set to 6) in the
SET POOLINFO command to determine the NRI. For example, if the TMSI is 80
60 00 01 in hexadecimal format and 0100 0000 0110 0000 0000 0000 0000 0001
in binary format, the middle six bits (011000) starting from the 24th bit represent
the NRI. Therefore, the NRI value is 24 in decimal format.
The Null NRI flag parameter is set to NO, indicating that the NRI is not a Null NRI.
A Null NRI, which is unique in the Pool area, is used by the BSC/RNC to select an
MSC for migrated subscribers according to the offload mode specified in the 3GPP
TS 23.236.
4-2

Issue 02 (2008-04-10)

ADD LAIGCI
Descr
iption
This command is used to set the non-broadcast LAI information of the MSC server.
Script
ADD LAIGCI: GCI="45419FFFF", MSCN="8613507001",

VLRN="8613507001", NONBCLAI=NO;
Rema
rk
The Non Broadcast LAI parameter specifies whether the LAI is a non-broadcast
LAI. A non-broadcast LAI is used by the terminal to trigger location update
according to the offload mode specified in the 3GPP TS 23.236.
SET OFFLDCTRL
Descr
iption
This command is used to set the offload mode for the MSC server.
Script
SET OFFLDCTRL: OFFLDTYPE=OFFLDMSISDN;
Rema
rk
Before starting another offload mode, stop the existing offload mode.
Descr
iption
This command is used to set the value of the MSC Pool broadcast timer for the MSC
server.
Script
SET POOLBC: TMRVAL=60, STARTTIME=16&19;
Rema
rk
This command is used to set the value and startup time of the MSC Pool broadcast
timer. Based on the configured value and startup time of the MSC Pool broadcast
timer, the MSC broadcasts its current load to the connected RNC/BSC by sending
a message on the private interface. The information provided by the broadcast
message includes the currently available subscriber capacity (available resources in
the current MSC) and designed capacity of servers in the MSC Pool (not including
subscribers of the RNCs/BSCs outside the MSC Pool).
The offload can be performed based on the offload mode specified in the 3GPP TS
23.236 or the E interface redirection mode defined by the private protocol of
Huawei. Bit 11 of P401 (VLR Part2 Software Parameter 02) determines which
offload mode is to be used.
SET POOLBC
A broadcast message can be delivered only when bit 0 of P195 is set to 0 by using
the MOD MSFP command.
SET POOLBKPCTRL
Descr
iption
Issue 02 (2008-04-10)
This command is used to set the MSC Pool backup configuration.

4-3

Script
SET POOLBKPCTRL: ENABLEBKP=YES, SPFTMBK=YES, BKPERI=DAILY,

BKSTDT=2008&02&03, BKSTTM=16&17&54;
Rema
rk
The Support backup parameter is set to YES, indicating that the MSC Pool backup
is enabled. If the active MSC server initiates the mobility management procedure,
data backup is triggered, and subscriber data is backed up to the standby MSC server
through the backup path. To prevent the standby MSC server from sending paging
messages globally, only the basic information (such as the IMSI, subscriber status,
and LAI) of subscribers is backed up.
ADD POOLBKPRT
Descr
iption
This command is used to set the MSC Pool backup route.
Script
ADD POOLBKPRT: MN="MSCGS1", ROLETYPE=HOMEMSC, RTNAME="GS1-GS4";
Rema
rk
M3UA routes are used as backup routes between the active MSC server and the
standby MSC server. You are advised to use the 14-digit standby SPCs of the active
and standby MSC servers for the M3UA routes.
The route configuration is different for the active MSC server and the standby MSC
server. For the active MSC server, only one backup route must be configured. For
the standby MSC server, multiple backup routes must be configured to interwork
with various active MSC servers.
4.2 Commands Used on the MGW

This section describes commands and parameters used on the MGW to implement the MSC Pool
feature.
SET POOLINFO
Descr
iption
This command is used to set the MSC Pool function.
Script
SET POOLINFO: MSCPOOLFLAG=YES, NRILEN=6, NULLNRI=63;
Rema
rk
The MSC Pool Control Flag parameter is set to Open, indicating that the MGW
can serve as the NNSF.
The NRI Length parameter is set to 6, indicating that the length of the NRI bits is
six. The NRI of all network elements in the Pool must have the same length.
The NULLNRI parameter is set to 63, indicating that the NRI whose value is 63 is
a Null NRI.
The settings of the NRI must be consistent between the MGW and the MSC server.
4-4

Issue 02 (2008-04-10)

ADD NRIMSC
Descr
iption
This command is used to set the mapping between the NRI and the MSC server.
Script
ADD NRIMSC: NRIV=24, CNID=1;
Rema
rk
The NRI Value parameter is set to 24, indicating that the NRI (whose value is 24)
in the CR message maps the MSC server whose node ID is 1. After obtaining the
NRI from the TMSI in the CR message, the NNSF forwards the CR message to the
MSC server whose node ID is 1.
The CN node here cannot be a standby node, that is, Flag of independent backup
office of the CN node must be set to No. Multiple NRIs can map the same CN node,
but one NRI cannot map multiple CN nodes.
ADD CNNODE
Descr
iption
This command is used to set the mapping between the NRI and the MSC server.
Script
ADD CNNODE: CNID=1, CNNAME="SRV1", MSCIDX=1, M3DEIDX=0,

INITCAP=100, BACKUPFLAG=NO, MNGSTA=NORMAL;
Rema
rk
The CNNode ID parameter specifies the ID of a CN node.

For the description of the MSC Index parameter, see the descriptions about SET
POOLINFO, a command used on the MSC server.
The M3DE Index specifies the mapping between the CN node and the M3DE
destination entity.
The Backup Flag parameter specifies whether the destination entity is a standby
MSC server.
The Manage Status parameter specifies the management status of a CN node.
4.3 Global Data and Software Parameters

This section describes important global data and software parameters used on the MSC server
to implement the MSC Pool feature.
SET MAPACCFG
Issue 02 (2008-04-10)
Descr
iption
This command is used to set the MAP feature configuration.
Script
SET MAPACCFG: IFALTMSILU=YES, IFALTMSISA=YES;

4-5
Rema
rk

The Allocate TMSI upon location update parameter must be set to Yes, indicating
that the MSC allocates the updated TMSI and location area through the LU ACCEPT
message sent on the A interface after the location update.
The Allocate TMSI upon service access parameter must be set to Yes, indicating
that the MSC allocates the updated TMSI and location area through the TMSI
REALL message sent on the A interface after calling or called service is completed.
SET MAPPARA
Descr
iption
This command is used to set the auxiliary MAP feature configuration.
Script
SET MAPPARA: ULFORUNUSRMO=YES;
Rema
rk
The Send UL when subscriber is unknown in MO parameter must be set to

Yes, indicating that the VLR initiates the network-side implicit location update on
behalf of a subscriber after receiving a service request from the subscriber who does
not have registered data in the VDB. This function of the VLR is used in an MSC
Pool network during the call termination recovery and the offload based on the E
interface redirection.
MOD PGCTRL
Descr
iption
This command is used to set the paging control information.
Script
MOD PGCTRL: TYPE=ALL, TIMES=1, FIRSTD=6, IMSI=FIRST-1;
Rema
rk
When you run this command on the active MSC server, configure the data based on
the actual conditions. The recommended settings are as follows:
l
Only the last paging is based on the IMSI.
The total paging duration in the case of multiple times of paging cannot exceed
20 seconds.
When you run this command on the standby MSC server, configure the data to
initiate paging based on the IMSI and only once.
P401 - VLR Part2 Software Parameter 02

Bit 11
The default value (recommended) is 0.

= 0: to control the load reallocation based on the E-interface redirection mode
= 1: to control the load reallocation based on the mode defined in the 3GPP 23.236
4-6

Issue 02 (2008-04-10)

Bit 12
Bit 12 determines whether to select the local MSC or other MSCs within the same
pool area in the following scenarios: When the MS/UE enters the MSC pool area,
and the NRI of the TMSI is the same as that of the MSC, the MS/UE is redirected
to another MSC forcibly. When the load reallocation based on the E interface
redirection mode is used, the callee data is recovered, and the paging response is
received, the MS is directed to another MSC forcibly. The default value
(recommended) is 0.
= 0: to select the local MSC
= 1: to select other MSCs
Rema
rk
The preceding bits are used to control the functions of the active MSC server.
P195 - A/Iu INTERFACEPARA2

Bit 0
Bit 0 determines whether each MSC server within the Pool broadcasts its current
load to the BSC/RNC. Based on the load of each MSC server, the NNSF selects an
MSC server to realize dynamic load balancing. The default value (recommended)
is 1.
= 1: not to send the broadcast messages
= 0: to send the broadcast messages
Bit 1
Bit 1 determines whether to perform special processing to the RESET message sent
by the BSC or RNC when the pool function (such as MSC Pool, server pool, or both
of them) and the A FLEX/IU FLEX function are enabled. The default value is 1.
= 1: to process the RESET message in the original mode
= 0: to perform special processing to the reset message. If the signaling point of the
BSC becomes reachable, the MSC server sends the RESET CIRCUIT message
instead of the RESET message. The RESET message controlled by the client is
processed in the original mode. When the MGW manages the A interface circuits,
the MSC server does not deliver the RESET and RESET CUIRCUIT messages. The
MSC server does not deliver the RESET message to the RNC any more.
P144 - Call Internal Parameter 9

Bit 8
Bit 8 determines whether to restrict the non-CMN calls incoming from and outgoing
to the BICC trunk during outgoing route selection. This bit is used to disable the
restriction of non-CMN calls incoming from and outgoing to the BICC trunk for
the MSC Pool feature when a call (all calls between MSC servers in the MSC Pool
are BICC calls) is forwarded between MSC servers in the MSC Pool.
= 1: not to restrict the non-CMN calls incoming from and outgoing to the BICC
trunk during outgoing route selection
= 0: to restrict the non-CMN calls incoming from and outgoing to the BICC trunk
during outgoing route selection
The default value (recommended) is 1.
Issue 02 (2008-04-10)

4-7
4-8


Issue 02 (2008-04-10)

5 New MSC Pool in the 2G Network
New MSC Pool in the 2G Network
About This Chapter

This section describes the data planning and data configuration process of a new MSC Pool in
a 2G network.
5.1 New Target Network Description
This section describes typical application scenarios of a new MSC Pool in the 2G network.
5.2 Data Configuration Flow
This section describes the overall data configuration process, data planning, and data presetting
for an MSC Pool in the scenario of new MSC Pool in 2G network.
5.3 Data Planning
This section describes the data planning for an MSC Pool network.
5.4 Data Configuration
This section describes the data configuration procedures of a new MSC Pool in the 2G network.
5.5 Other Data Configuration
This section describes other data configuration in the scenario of a new MSC Pool in a 2G
network.
5.6 System Commissioning
This section describes the system commissioning of a new MSC Pool in the 2G network.
Issue 02 (2008-04-10)

5-1

5.1 New Target Network Description

This section describes typical application scenarios of a new MSC Pool in the 2G network.
If required, a new MSC Pool can be built in a 2G network. Normally, the characteristics of a 2G
network with a new MSC Pool are as follows:
l
The core network adopts the softswitch solution, that is, an MSC is divided into an MSC
server and an MGW.
The access network adopts the BSS solution. The BSC in the BSS does not support the AFlex function.
To build a 2G network with a new MSC Pool, the MGW must provide the A-Flex function. The
details of the networking scenarios are described in the following sections.
Figure 5-2 shows the networking of a new target network.
Figure 5-1 Networking diagram of a new target network
SX 1
SX 2
SX 3
SX 4
HLR/SCP/SMSC
STP
MGW1
MGW2
MGW3
GMSC (TMSC)
BSC1
BSC2
BSC3
VPLMN or other MSCs

in the HPLMN
BSC4
IP bearer
TDM bearer
The networking of a new target network is as follows:
5-2
The Mc-interface is based on IP and the A-interface signaling is forwarded by the MGW
in M3UA forward mode.
The A-interface signaling and voice circuits between the MGW and the BSC are borne over
the TDM.
The Nb-interface between the MGWs is borne over IP and all MGWs are connected with
each other.
All voice channels of the MGW are directly connected to the GMSC (or TMSC). The
signaling and speech channels are based on TDM.
Issue 02 (2008-04-10)

The MSC server is connected to the pure signaling point NEs, such as the HLR, SCP, and
SMC in STP forward mode. The MSC server is connected to the STP directly and the
signaling is borne over IP.
The A-interface circuits are based on TDM bearers. The MGW manages the A-interface
circuits so that the circuits are shared by all BSCs in the MSC Pool.
Direct speech channels are configured between all MGWs in the MSC Pool and the GMSC
(or TMSC). Signaling and speech channels between them are based on TDM. The MSC
Pool interworks with external networks through the GMSC. The MSC Pool interworks with
local MSCs or toll MSCs in the network through the TMSC.
Chain backup is used. SX2 is the backup server of SX1, SX3 is the backup server of SX2,
and SX1 is the backup server of SX3.
For details on the networking principles, see 3.3 General Principles of the MSC Pool
Planning.
Function Description
The function description of a new target network is as follows:
l
The A-Flex function is enabled on the MSC server and MGW, but the BSC does not support
the A-Flex function.
The MGW manages the A-interface circuits.
The virtual MGW function is enabled on the MGW.
Signaling Point Codes Description

Based on the description in 1.3.8 A-Flex Function Proxy on the MGW, you are advised to use
the M3UA forwarding networking mode.
As shown in Figure 5-2, the principles of the signaling point code (SPC) planning are as follows:
l
MSC server 1 uses two SPCs: AA (for national network) and DD (for national reserved
network).
MSC server 2 uses two SPCs: BB (for international network) and EE (for international
reserved network).
MSC server 3 uses two SPCs: CC (for national network) and FF (for national reserved
network).
MGW1 uses an SPC (GG) and a public SPC (XX). GG for national network is used to
interwork with the MSC server. XX for national reserved network is used to interwork with
the access network.
MGW2 uses an SPC (HH) and a public SPC (XX). HH for national reserved network is
used to interwork with the MSC server. XX for national reserved network is used to
interwork with the access network.
MGW3 uses an SPC (JJ) and a public SPC (XX). JJ for national reserved network is used
to interwork with the MSC server. XX for national reserved network is used to interwork
with the access network.
Issue 02 (2008-04-10)

5-3

Figure 5-2 SPCs used in the target network

BB
AA
SX 1
DD
SX 3
EE
GG
MGW
2
MGW
1
BSC
1
CC
SX 2
BSC
2
FF
HH
MGW
3
BSC
3
JJ
BSC
4
For detailed data planning, see Table 5-1, Table 5-2, and Table 5-3.
Analysis of the Message Flow

l
BSC 1 (OPC: 10B) sends the first uplink message (that is, the SCCP CR message) to MGW
1 (SPC: XX).
GG is the assistant SPC of XX. Therefore, the message between XX and DD is transmitted
through the M3UA link set between GG and DD.
After receiving the message, the MGW (SPC: XX) judges that an MSC Pool network is
used and starts the NNSF function. The MGW resolves the NRI and sends the message to
the MSC server according to the mapping between GG and DD (the M3UA destination
entity). In this message, the DPC is changed to DD and the OPC 10B is retained.
The MSC server receives the message through the link set between DD and GG.
After the service processing is completed, the MSC server sends an SCCP CC message
(OPC: DD; DPC: 10B) to the MGW through the link set between DD and GG. The MSC
ID is included in the local reference number of this message.
The MGW receives the message through GG. The message indicates that an MSC Pool
network is used. By utilizing the assistant relationship between XX and GG, the MGW
sends the message to the BSC through the N7 link set between XX and 10B. In this message,
the OPC is changed to XX.
The BSC receives the message in which the OPC is XX and DPC is 10B. In this way, the
SPC of the MSC server is hidden from the BSC through the MGW.
By now, the transmission of the SCCP CR and CC messages is completed. Subsequent A

interface signaling is transmitted through the SCCP connection established between the
local and destination reference numbers.

Figure 5-3 shows the overall data configuration process for an MSC Pool.
5-4

Issue 02 (2008-04-10)

Figure 5-3 Overall data configuration process for an MSC Pool

Start
Preparation
Presetting data for MSC Pool
Evolution of
the Core
Network
Adding MSC servers to MSC

Pool
Adding MGWs to MSC Pool
Access of the
Access Network
Adding BSCs to MSC Pool

Configuring number analysis data
Configuring
service
data
Configuring mobile service data

Configuring IN service data
End
The data configuration for an MSC Pool is classified into data planning, evolution of the core
network (CN), access of the access network, and configuration of service data. The detailed
configuration procedures are described in the following sections.
5.3 Data Planning

Only the data planning related to the MSC Pool is described in this section. All other data
planning is outside the scope of this document. Table 5-1, Table 5-2, and Table 5-3 list the data
planning for an MSC Pool network.
Table 5-1 Data planning for MSC servers in an MSC Pool network
Issue 02 (2008-04-10)
Name
MSC Server 1
MSC Server 2
MSC Server 3
Node
name
SX1
SX2
SX3
SPC
National network:
A80001
National network:
A80002
National network:
A80003
National reserved
network: 801
National reserved
network: 802
National reserved
network: 803

5-5

5-6
Name
MSC Server 1
MSC Server 2
MSC Server 3
IP
address
(IP
address
of the
WIFM)
192.168.153.1
192.168.155.2
192.168.151.3
Length
of the
NRI
(bits)
6 (recommended)
6 (recommended)
6 (recommended)
Value
of the
NRI
1 (recommended)
2 (recommended)
3 (recommended)
Default
MSC
You are advised to set all MSC servers in the MSC Pool to default MSCs.
Chargin
g mode
Charging based on MSC IDs (recommended)
Capacit
y of an
MSC
server
in the
MSC
Pool
1 million (recommended)
Value
of Null
NRI
10 (recommended)
10 (recommended)
10 (recommended)
CN ID
1 (recommended)
2 (recommended)
3 (recommended)
Nonbroadca
st LAI
460004444
460005555
460006666

Issue 02 (2008-04-10)

Issue 02 (2008-04-10)
Name
MSC Server 1
MSC Server 2
MSC Server 3
Data of
H.248
links
betwee
n the
MSC
server
and the
MGW
MGW1:
MGW1:
MGW1:
SLOCIP1="192.168.153
.1"
SLOCIP1="192.168.155
.2"
SLOCIP1="
192.168.151.3"
SLOCPORT=5000
SLOCPORT=5100
SLOCPORT=3300
SRMTIP1="192.168.167
.21"
SRMTIP1="192.168.167
.21"
SRMTIP1="192.168.167
.21"
SRMTPORT=5000
SRMTPORT=5100
SRMTPORT=3300
MGW2:
MGW2:
MGW2:
SLOCIP1="192.168.153
.1"
SLOCIP1="192.168.155
.2"
SLOCIP1="
192.168.151.3"
SLOCPORT=2300
SLOCPORT=5200
SLOCPORT=3400
SRMTIP1="192.168.172
.41"
SRMTIP1="192.168.172
.41"
SRMTIP1="192.168.172
.41"
SRMTPORT=2300
SRMTPORT=5200
SRMTPORT=3400
MGW3:
MGW3:
MGW3:
SLOCIP1="192.168.153
.1"
SLOCIP1="192.168.155
.2"
SLOCIP1="
192.168.151.3"
SLOCPORT=2203
SLOCPORT=5300
SLOCPORT=4600
SRMTIP1="192.168.175
.42"
SRMTIP1="192.168.175
.42"
SRMTIP1="192.168.175
.42"
SRMTPORT=2203
SRMTPORT=5300
SRMTPORT=4600

5-7

Name
MSC Server 1
MSC Server 2
MSC Server 3
Data of
M3UA
links
betwee
n the
MSC
server
and the
MGW
MGW1:
MGW1:
MGW1:
LOCIP1="192.168.153.1
"
SLOCIP1="192.168.155
.2"
SLOCPORT=4100
SLOCIP1="
192.168.151.3"
PEERIP1="192.168.167.
21"
PEERPORT=6001
PEERIP1="192.168.167.
21"
PEERPORT=4100
MGW2:
MGW2:
MGW2:
LOCIP1="192.168.153.1
"
LOCIP1="192.168.155.2
"
LOCIP1="
192.168.151.3"
LOCPORT=2302
LOCPORT=4200
LOCPORT=3600
PEERIP1="192.168.172.
41"
PEERIP1="192.168.172.
41"
PEERIP1="192.168.172.
41"
PEERPORT=2302
PEERPORT=4200
PEERPORT=3600
MGW3:
MGW3:
MGW3:
LOCIP1="192.168.153.1
"
LOCIP1="192.168.155.2
"
LOCIP1="
192.168.151.3"
LOCPORT=2204
LOCPORT=4300
LOCPORT=4700
PEERIP1="192.168.175.
42"
PEERIP1="192.168.175.
42"
PEERIP1="192.168.175.
42"
PEERPORT=2204
PEERPORT=4300
PEERPORT=4700
LOCPORT=6001
PEERIP1="192.168.167.
21"
SLOCPORT=3500
PEERPORT=3500
Table 5-2 Data planning for MGWs in an MSC Pool network

Name
MGW1
MGW2
MGW3
Node name
MGW1
MGW2
MGW3
SPC
2A (for interworking
with the MSC server)
2C (for interworking
2D (for interworking
902 (for interworking

with the access
network)

with the access
network)

with the access
network)
192.168.167.21
192.168.172.41
192.168.175.42
IP address (the
MGW adopts the
centralized
forwarding mode
for IP addresses)
5-8

Issue 02 (2008-04-10)

Name
MGW1
MGW2
MGW3
Mapping between
the VMGW IDs and
the MSC servers
SX1:
SX1:
SX1:
VMGWID=0
VMGWID=1
VMGWID=1
SX2:
SX2:
SX2:
VMGWID=1
VMGWID=0
VMGWID=2
SX3:
SX3:
SX3:
VMGWID=2
VMGWID=2
VMGWID=0
Table 5-3 Data planning for BSCs in an MSC Pool network

Name
BSC1
BSC2
BSC3
BSC4
Node name
BSC1
BSC2
BSC3
BSC4
SPC
10B
A61
B04
B05
LAI
460000011
460000012
460000060
460000070
CGI
4600000110012
4600000120012
4600000600060
4600000600070

5.4.1 Configuring the Basic Data of NEs
This section describes the basic data configuration of NEs.
5.4.2 Presetting Data for the MSC Pool
This section describes the presetting data configuration for an MSC Pool.
5.4.3 Building an MSC Pool in the Core Network
This section describes the configuration procedure for building an MSC Pool in the core network.
5.4.4 Integration with the Access Network
This section describes the configuration procedure for integrating an MSC Pool with the access
network.

The procedures for configuring the basic data of NEs in an MSC Pool are the same as that for
configuring NEs in a network without an MSC Pool. For details, see the relevant data
configuration in the MSOFTX3000 Mobile Switch Center Configuration Examples.

This section describes the presetting data configuration for an MSC Pool.
Issue 02 (2008-04-10)

5-9

Configuring Data on the MSC Server

To preset the data on the MSC servers, perform the following steps:
1.
2.
3.
Set the MSC servers on the M2000.

Descriptio
n
Connect the MSC servers to the O&M system of the M2000. Thus, you
can maintain the MSC servers in a centralized manner on the M2000.
Script
Remark
The data configuration is performed on the M2000. For details, refer to

the relevant part in the electronic documentation of the M2000.
For all MSC servers, load the MSC server license file with MSC Pool feature enabled.
Descr
iptio
n
Apply for and load the MSC Pool license of all MSC servers.
Scrip
t
LOD LICENSE;
Rema
rk
Activate the A-FLEX function of all MSC servers.

Descriptio
n
On each MSC server, run ADD CDBFUNC to activate the A-FLEX

function of the MSC server.
Script
SX1:
ADD CDBFUNC: CDBMN= 110, FUNC=AFLEX-1;
SX2:
SX3:
Remark
4.
Only an MSC server that supports the A-FLEX function can be added
to the MSC Pool.
Set the NRI and default MSCs.

Descriptio
n
5-10
On each MSC server, run ADD NRIMSC to set the NRI (adding the
NRI, Null NRI, and neighboring NRI). Thus, all MSC servers in the MSC
Pool are set to default MSCs.

Issue 02 (2008-04-10)

Script
SX1:
ADD NRIMSC: DESC="SX1", NRIV=1, MSCNO=K'861390801,
VLRNO=K'861390801, MSCNM="SX1";
ADD NRIMSC: DESC="NULL NRI", NRIV=10,
MSCNO=K'861390801, VLRNO=K'861390801, MSCNM="SX1",
NNRI=TRUE;
ADD NRIMSC: DESC="SX2_NRI", NRIV=2, MSCNO=K'861390802,
VLRNO=K'861390802, MSCNM="SX2", LOCMSC=FALSE;
SX2:
ADD NRIMSC: DESC="NULL NRI", NRIV=10,
NNRI=TRUE;
SX3:
ADD NRIMSC: DESC="NULL_NRI", NRIV=10,
NNRI=TRUE;
Remark
This command is used to set the NRI.

The Null NRI flag parameter is set to YES, indicating that the NRI is a
Null NRI. A Null NRI is used by the NNSF to reallocate the CN node
for subscribers according to the offload mode specified in the 3GPP TS
23.236.
5.
Set the Non-broadcast LAI parameter.

Descriptio
n
On each MSC server, set the Non-broadcast LAI parameter.
Script
SX1:
ADD LAISAI: SAI="460004444", LAISAINAME="Nonbroadcast", MSCN="861390801", VLRN="861390801",
NONBCLAI=YES, NONBCLAIT=HVLR;
SX2:
ADD LAIGCI: SAI="460005555", LAIGCINAME="Nonbroadcast", MSCN="861390802", VLRN="861390802",
NONBCLAI=YES;
SX3:
ADD LAIGCI: SAI="460006666", LAIGCINAME="Nonbroadcast", MSCN="861390803", VLRN="861390803",
NONBCLAI=YES;
Issue 02 (2008-04-10)

5-11

Remark
6.
The Non-broadcast LAI parameter specifies whether the LAI is a nonbroadcast LAI. A non-broadcast LAI is used by the terminal to trigger
location update according to the offload mode specified in the 3GPP TS
23.236.
Set the MSC Pool function information.

Descriptio
n
On each MSC server, run SET POOLINFO to set the MSC Pool
function information.
Script
SX1:
SET POOLINFO: MSCPOOL=YES, SERVER=YES, MSCIDX=1,
SX2:
SX3:
Remark

The Function flag of MSC POOL parameter is set to Yes, indicating
that the MSOFTX3000 can directly interwork with the BSC that supports
the NNSF function. If the MGW serves as the NNSF, set the parameter
to No.
The Flag of MGW providing MSC POOL function parameter is set
to Yes, indicating that the MGW can serve as the NNSF. If the MSC
Pool interworks with ordinary BSCs, set the parameter to Yes.
The value of the MSC Identity in MSC POOL parameter must be
consistent with the value of the MSC Index parameter in the ADD
CNNODE command used on the MGW. Subsequent connection-mode
SCCP messages can be successfully sent on the A interface only when
correct local and destination reference numbers are configured. The
destination reference number for the connection-mode message sent by
a CN node is carried in the CR message sent by the BSC. The MSC
Identity in MSC POOL parameter is included in the local reference
number. If the value of the MSC Identity in MSC POOL parameter is
inconsistent with the value of the MSC Index parameter in the ADD
CNNODE command used on the MGW, subsequent connection-mode
messages (except for the CR request messages) sent on the A interface
are incorrectly routed by the MGW.
The Length of NRI bit parameter is set to 6, indicating that six bits in
the TMSI are reserved for the NRI. The NRI of all network elements in
the Pool must have the same length.
7.
Set all BSCs under each MSC server to support the MGW proxy A-Flex function.
Descriptio
n
5-12
On each MSC server, run MOD BSC to set all BSCs of the MSC server
to support the MGW proxy A-Flex function".

Issue 02 (2008-04-10)

Script
SX1:
MOD BSC: DPC="10B", OPC="801", BSCNM="BSC1",
CAPABILITY=MGWPROXYAFLEX-1;
SX2:
MOD BSC: DPC="A61", OPC="802", BSCNM="BSC2",
SX3:
MOD BSC: DPC="B04", OPC="803", BSCNM="BSC3",
MOD BSC: DPC="B05", OPC="803", BSCNM="BSC4",
8.
Set the CN IDs of all MSC servers.

Descriptio
n
On each MSC server, run SET OFI to set the CN IDs.
Script
SX1:
SET OFI: OFN="SX1", LOT=LOCMSC, NN=YES, NN2=YES,
SN1=NAT, SN2=NATB, NPC="A80001", NP2C="801", NNS=SP24,
NN2S=SP14, LAC="0755", LNC=K'86, CNID=1;
SX2:
SX3:
Remark
9.
A CN ID uniquely identifies an MSC server in an MSC Pool.
Set the parameters of the MSC Pool broadcast timer.

Descriptio
n
On each MSC server, run SET POOLBC to set the parameters of the
MSC Pool broadcast timer.
Script
SET POOLBC: TMRVAL=60, STARTTIME=16&30;
Remark
This command is used to set the value and startup time of the timer. Based
on the value and startup time of the timer, the MSC server broadcasts the
load of the MSC server to associated BSCs or RNCs through private
interface messages. The information provided in the broadcast messages
includes how many more subscribers the MSC server can support
(remaining resources of the MSC server) and capacity of the MSC server
in the MSC Pool (not including the number of subscribers supported by
the BSCs or RNCs outside the MSC Pool area).
A broadcast message can be properly sent only when bit 0 of P195
(controlling whether to send the broadcast message) is set to 0 by running
MOD MSFP.
10. Enable the TMSI reallocation function.

Issue 02 (2008-04-10)

5-13

Descriptio
n
On each MSC server, run SET MAPACCFG to enable the TMSI

reallocation function.
Script
SET MAPACCFG: IFALTMSILU=YES, IFALTMSISA=YES;
----End
Configuring Data on the MGW

To preset the data on the MGWs, perform the following steps:
1.
2.
Set the MGWs on the M2000.

Descriptio
n
Connect the MGWs to the O&M system of the M2000. Thus, you can
maintain the MGWs in a centralized manner on the M2000.
Script
Remark
The data in this step is configured on the M2000. For details, refer to the
online Help of the M2000.
Add new signaling points for each MGW.

Descriptio
n
On each MGW, run SET OFI to add new signaling points.
Script
MGW1:
SET OFI: NAME="MGW1", INTVLD=NO, INTRESVLD=NO,
NATVLD=YES, NATRESVLD=YES, SERACH0=NAT, SERACH1=NATB,
NATOPC=H' 2A, NATRESOPC=H'902, NATLEN=LABEL24,
NATRESLEN=LABEL14;
MGW2:
NATOPC=H' 2C, NATRESOPC=H'902, NATLEN=LABEL24,
NATRESLEN=LABEL14;
MGW3:
NATOPC=H' 2D, NATRESOPC=H'902, NATLEN=LABEL24,
NATRESLEN=LABEL14;
----End
Replacing TMSIs
Start the IMSI reallocation process in the case that the A-FLEX function is enabled on the MSC
servers and the MGWs. Then, wait for the time required by two periodical location updates (the
interval of the location updates can be set on the BSC) for the replacing of TMSIs to be
completed. (You are advised to set the start time of the TMSI replacing to a time when there are
a significant number of online subscribers). To replace a TMSI is to add the corresponding NRI
to the TMSI. This enables the subscribers to be still homed to the original MSC server after the
2G network evolves into an MSC Pool. The purpose of the operation is to keep the target network
5-14

Issue 02 (2008-04-10)

as similar to the existing network as possible and thus to minimize the impact of the network
evolution on the network operation.
As long as you have run SET MAPACCFG to enable the TMSI reallocation function, the
MSOFTX3000 automatically replaces the TMSIs of subscribers.
Ending the Presetting

After two periodical location updates, randomly select 10 subscribers and check whether their
TMSIs are replaced. If nine or more TMSIs are replaced, you can proceed with subsequent steps.
Otherwise, wait until more TMSIs are replaced.

Configuring the Data on MSC server 1

To configure the data of the Mc interface over M3UA links between the MSC server and the
MGW, perform the following steps:
1.
Add MGW1/MGW2/MGW3 on MSC server 1, and configure the H.248 links from MGW1/
MGW2/MGW to MSC server 1.
(1) On MSC server 1, add MGW 1 and configure the H.248 links between MSC server 1
and MGW 1.
Issue 02 (2008-04-10)
Descriptio
n
On MSC server 1, add MGW 1 and configure the H.248 links

between MSC server 1 and MGW 1.
Script
ADD MGW: MGWNAME="MGW1", TRNST=SCTP, CTRLMN=133,

BCUID=1,
BNCC=TDM-1&IP-1&AAL1STRUCT-1&AAL2-1&AAL1-1,
SPCATTR=SDPHEX-1&NOBNC-1&NOEC-1&NOJTTR-1&NOFAX-1&NOM
ODEM-1&LOCSDPP-1&SUPH248V2-1&NOVERNEG-0&SUPCODECCFG1, ENCT=NSUP,
CPB=TONE-1&PA-1&SENDDTMF-1&DETECTDTMF-1&MPTY-1&IWF-1
, ECRATE=300, IWFRATE=300, TONERATE=300,
MPTYRATE=300, DETDTMFRATE=300, SNDDTMFRATE=300,
HRAMRR=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RATE7
40-1&RATE795-1,
UMTSAMR2R=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RA
TE740-1&RATE795-1&RATE102-1&RATE122-1,
FRAMRR=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RATE7
40-1&RATE795-1&RATE102-1&RATE122-1,
UMTSAMRR=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RAT
E740-1&RATE795-1&RATE102-1&RATE122-1,
MODEMLST=GSMMT-1&GSMV21-1&GSMV22-1&GSMV22BIS-1&GSMV2
3-1&GSMV26TER-1&GSMV32-1&GSMMTAUTO-1&GSMV34-1,
TC=GSMEFR-1&GSMHR-1&TDMAEFR-1&PDCEFR-1&HRAMR-1&UMTSA
MR2-1&FRAMR-1&PCMA-1&PCMU-1&UMTSAMR-1&G7231-1&G729A1&GSMFR-1;
ADD H248LNK: MGWNAME="MGW1", TRNST=SCTP,
LNKNAME="MGW1", MN=134, SLOCIP1="192.168.155.2",
SLOCPORT=5000, SRMTIP1="192.168.167.21",
SRMTPORT=5000, QOSFLAG=TOS;

5-15

and MGW 2.
Descriptio
n

Script

BCUID=1,
SPCATTR=SDPHEX-1&NOBNC-1&NOEC-1&NOJTTR-1&NOFAX-1&NO
MODEM-1&LOCSDPP-1&SUPH248V2-1&NOVERNEG-0&SUPCODECCF
G-1, ENCT=NSUP,
CPB=TONE-1&PA-1&SENDDTMF-1&DETECTDTMF-1&MPTY-1&IWF1, ECRATE=300, IWFRATE=300, TONERATE=300,
HRAMRR=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RATE
740-1&RATE795-1,
UMTSAMR2R=RATE475-1&RATE515-1&RATE590-1&RATE670-1&R
ATE740-1&RATE795-1&RATE102-1&RATE122-1,
FRAMRR=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RATE
740-1&RATE795-1&RATE102-1&RATE122-1,
UMTSAMRR=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RA
TE740-1&RATE795-1&RATE102-1&RATE122-1,
MODEMLST=GSMMT-1&GSMV21-1&GSMV22-1&GSMV22BIS-1&GSMV
TC=GSMEFR-1&GSMHR-1&TDMAEFR-1&PDCEFR-1&HRAMR-1&UMTS
AMR2-1&FRAMR-1&PCMA-1&PCMU-1&UMTSAMR-1&G7231-1&G729
A-1&GSMFR-1;
SLOCPORT=2300, SRMTIP1="192.168.172.41",
and MGW 3.
Descriptio
n
5-16


Issue 02 (2008-04-10)

Script
2.

BCUID=1,
G-1, ENCT=NSUP,
740-1&RATE795-1,
740-1&RATE795-1&RATE102-1&RATE122-1,
TE740-1&RATE795-1&RATE102-1&RATE122-1,
A-1&GSMFR-1;
SLOCPORT=2203, SRMTIP1="192.168.175.42",
Add the relevant data of the M3UA configuration from MSC server 1 to MGW1/MGW2/
MGW3.
(1) On MSC server 1, add the data of M3UA configuration from MSC server 1 to MGW
1.
Descriptio
n
On MSC server 1, add the data of M3UA configuration from MSC

server 1 to MGW 1.
Script
ADD M3LE: LENM="SX1_NATB", NI=NATB, OPC="801",

LET=AS;
ADD M3DE: DENM="TO_MGW1_NATB", NI=NATB, DPC="2A",
STPF=TRUE, DET=SG;
ADD M3LKS: LSNM="TO_MGW1_NATB",
ADNM="TO_MGW1_NATB", WM=ASP;
ADD M3LNK: MN=134, LNKNM="TO_MGW1_NATB",
LOCIP1="192.168.153.1", LOCPORT=6001,
PEERIP1="192.168.167.21", PEERPORT=6001, CS=C,
LSNM="TO_MGW1_NATB", QoS=TOS;
ADD M3RT: RTNM="TO_MGW1_NATB", DENM="TO_MGW1_NATB",
LSNM="TO_MGW1_NATB";
Remark
Add the M3UA data for MSC server 1 (SPC: 801) to interwork with
MGW 1 (SPC: 2A).
2.
Descriptio
n
Issue 02 (2008-04-10)

server 1 to MGW 2.

5-17

Script
ADD M3DE: DENM="TO_MGW2_NATB", NI=NATB, DPC="2C",

STPF=TRUE, DET=SG;
LOCIP1="192.168.153.1", LOCPORT=2302,
Remark
MGW 2 (SPC: 2C).
3.
Descriptio
n

server 1 to MGW 3.
Script
ADD M3DE: DENM="TO_MGW3_NATB", NI=NATB, DPC="2D",

STPF=TRUE, DET=SG;
LOCIP1="192.168.153.1", LOCPORT=2204,
Remark
MGW 3 (SPC: 2D).
----End

The procedure for configuring the data of MSC server 2 is similar to the procedure for
configuring the data of MSC server 1 described in Configuring the Data on MSC server 1.

Configuring the Data on MGW 1

To configure the data on MGW 1, perform the following steps:
1.
Configure the MGW1 SPC based on the general planning of the MSC Pool.
Descriptio
n
5-18
Add an SPC for MGW 1.

Issue 02 (2008-04-10)

Script
2.

NATOPC=H' 2A, NATRESOPC=H'902, NATLEN=LABEL24,
NATRESLEN=LABEL14;
Configure the relevant information of the MSC Pool.

Descriptio
n
On MGW 1, configure the relevant information of the MSC Pool.
Script
Remark
This command is use to set the MSC Pool function information.

The MSC Pool Control Flag parameter is set to Open, indicating that
the MGW can serve as the NNSF.
3.
Configure the Mc interface and the M3UA data between MGW 1 and MSC server1/ MSC
server2/ MSC server3.
(1) Add a virtual MGW on MGW 1. Add an H.248 link to MSC server 1.
Desc
ripti
on
Add a virtual MGW on MGW 1. Add an H.248 link between MGW 1 and
MSC server 1.
Scrip
t
SET VMGW: VMGWID=0, MIDTYPE=IP,

MID="192.168.167.21:5000", RPTIMES=3, RPINTV=3,
RLSINTV=30, LNKFAILLEN=30, IPNUM=86016, TDMNUM=400384,
ATMNUM=221184, AUTOSWP=YES, LNKHBTIME=3, LNKMAXHBLOSS=5,
MWDMODE=STATIC, MWDVAL=0, CISTT=1000, NETTYPE=WCDMA,
ROOTLENGTH=8, NONROOTLENGTH=8, CODEC=G.711A,
MASTERMGCDETECTFLAG=NO, MASTERMGCDETECTTIME=5;
ADD MGC: VMGWID=0, MGCIDX=0, MIDTYPE=IP,
MID="192.168.167.21:5000", MSS=MASTER, H248VER=V1,
PRONEGO=NO, CONTCTRLASSN=NO, DWRAP=NO, ANNEXC=1,
OUTADA=1, PERMANENTREQID=0, STREAMMODE=Inactive;
ADD H248LNK: LINKID=48, VMGWID=0, MGCIDX=0, TT=SCTP,
LOCALIP="192.168.167.21", LOCALPORT=5000,
PEERIP="192.168.153.1", PEERPORT=5000, FN=1, SN=11,
BP=BACK;
(2) Add an M3UA destination signaling point and related M3UA configuration for
interworking with MSC server 1.
Desc
ripti
on
Issue 02 (2008-04-10)
On MGW 1, add an M3UA destination signaling point and related M3UA

configuration for interworking with MSC server 1.

5-19

Scrip
t
ADD M3LE: LEX=0, LEN="MGW1_NATB", LET=SG, NI=NATB,

OPC=H'2A;
ADD M3LE: LEX=1, LEN="MGW1_NATB_1", LET=SG, NI=NATB,
OPC=H902;
ADD M3DE: DEX=0, DEN="SX1", DET=AS, NI=NATB, DPC=H'801,
LEX=0, NETTYPE=MSCPOOL;
ADD M3DE: DEX=1, DEN="SX1", DET=AS, NI=NATB, DPC=H'801,
LEX=1, NETTYPE=MSCPOOL;
ADD M3LKS: LSX=0, LSN="SX1", ADX=0;
ADD M3RT: RN="SX1", DEX=0, LSX=0;
ADD M3LNK: LNK=0, BT=SPF, BN=1, LKN="SX1",
LIP1="192.168.167.21", LP=6001, RIP1="192.168.153.1",
RP=6001, LSX=0, ASF=ACTIVE;
Rem
ark
Add two M3UA local entities for the MGW.

Add the M3UA destination entity (that is, an MSC server) for one M3UA
local entity of the MGW. The network type is MSC Pool. A corresponding
M3UA route must be added.
Add the M3UA destination entity (that is, an MSC server) for the other
M3UA local entity of the MGW. It is not required to add M3UA route data.
(3) The procedure for configuring the Mc interface and the M3UA data between MGW
1 and MSC server 2/MSC server 3 is the similar to the procedure for configuring the
Mc interface and the M3UA data between MGW 1 and MSC server 1.
4.
On MGW 1, add the corresponding CN nodes and mapping between the NRIs and MSC
server1/ MSC server2/ MSC server3.
(1) On MGW 1, add a CN node of MSC server 1 and the mapping between the NRI and
MSC server 1.
Desc
ripti
on
On MGW 1, add a CN node of MSC server 1 and the mapping between

the NRI and MSC server 1.
Scrip
t
ADD CNNODE: CNID=1, CNNAME="SX1", MSCIDX=1, M3DEIDX=1,

MNGSTA=INHIBITED;
(2) The procedure for configuring the corresponding CN nodes and mapping between the
NRIs and MSC server 2/MSC server 3 is similar to the procedure for configuring the
corresponding CN node and mapping between the NRI and MSC server 1.
----End

The procedure for configuring the data of MGW 2 is similar to the procedure for configuring
the data of MGW 1 described in Configuring the Data on MGW 1.

5-20

Issue 02 (2008-04-10)

5.4.4 Integration with the Access Network

network.

To configure the data on MSC server 1, perform the following steps:
1.
Add BSC 1 on MSC server 1.

(1) Add an M3UA destination entity for BSC 1.
Descriptio
n
Add an M3UA destination entity for BSC 1.
Script
ADD M3DE: DENM="BSC1", LENM="SX1_NATB", NI=NATB,

DPC="10B", DET=SP;
Remark
BSC 1 (SPC: 10B).
(2) Add an office direction for BSC 1.

Descriptio
n
Add an office direction for BSC 1.
Script
ADD OFC: ON="BSC1", OOFFICT=BSC, DOL=LOW, DOA=BSC,

BOFCNO=1,OFCTYPE=COM, SIG=NONBICC/NONSIP, NI=NATB,
DPC1="10B", CONFIRM=Y;
(3) Add BSC 1 on MSC server 3.

Descriptio
n
Script
ADD BSC: NI=NATB, DPC="10B", OPC="801",

BSCNM="BSC1",
CAPABILITY=CCPAGING-1&SMSPAGING-1&SSPAGING-1&PSIPAG
ING-1&LCS-1&SERVICEHO-1&DTM-1&LOADHO-1&MGWPROXYAFLE
X-1&PRIVATEMSG-1&SupportActiveTrace-1,
RSSCNAME="SX1", MLAIF=YES, MGWMAC=YES;
(4) Add an M3UA route to BSC 1.

Descriptio
n
Add an M3UA route to BSC 1.
Script
ADD M3RT: RTNM="BSC1", DENM="BSC1", LSNM="MGW1";
(5) Add an SCCP DSP for BSC 1.
Issue 02 (2008-04-10)

5-21

Descriptio
n
Add an SCCP DSP for BSC 1.
Script
ADD SCCPDSP: DPNM="BSC1", NI=NATB, DPC="10B",

OPC="801";
(6) Add SCCP subsystems for BSC 1.

Descriptio
n
Add SCCP subsystems for BSC 1.
Script
ADD SCCPSSN: SSNNM="BSC1_SCMG", NI=NATB, SSN=SCMG,

SPC="10B", OPC="801";
ADD SCCPSSN: SSNNM="BSC1_BSSAP", NI=NATB,
SSN=BSSAP, SPC="10B", OPC="801";
(7) Add an A-interface trunk group.
2.
3.
Descriptio
n
Add an A-interface trunk group to facilitate performance

measurements relevant to trunk groups on MSC server 1.
Script
ADD AIETG: TGNAME="BSC1", MGWNAME="MGW1",

SOPC="801", SDPC="10B", CPNAME="BSC1" , BTG=1;
On MSC server 1, configure the paging data of the location areas controlled by BSC 1.
Description
On MSC server 1, configure the paging data of the location areas

controlled by BSC 1.
Script
ADD PGCTRL: LAI="460000011", TYPE=ALL;
On MSC server 1, disable the circuit management switch of BSC 1.

Description
On MSC server 1, disable the circuit management switch of BSC 1. That

is, the MGW is enabled to manage the A-interface circuits.
Script

MGWMAC=YES;
The procedure for adding BSC 2, BSC 3, and BSC 4 on MSC server 1 is similar to the
procedure for adding BSC 1 on MSC server 1 described in "Add BSC 1 on MSC server 1".
Therefore, it is not described in this document.
----End

5-22

Issue 02 (2008-04-10)



1.
2.
Add the TDMIU configuration for BSC 1. Set Relay type to ATRUNK.
Description
Add the TDMIU configuration for BSC 1. Set Relay type to ATRUNK.
Script
ADD TDMIU: BT=E32, BN=6, TIDFV=64, TIDLV=127, VMGWID=0,

RT=ATRUNK;
Add narrowband signaling data such as N7DSP for BSC 1. Set Network Type to MSC
Pool.
Description
Add narrowband signaling data such as N7DSP for BSC 1. Set Network
Type to MSC Pool.
Script
ADD N7DSP: INDEX=0, NAME="BSC1", NI=NATB, DPC=H'10b,

OSPINDEX=0, NETTYPE=MSCPOOL;
ADD N7DSP: INDEX=1, NAME="BSC1_1", NI=NATB, DPC=H'10b,
OSPINDEX=1, NETTYPE=MSCPOOL;
ADD N7LKS: INDEX=0, NAME="TO_BSC1", DSPIDX=0;
ADD MTP2LNK: LNKNO=0, LNKNAME="TO_BSC1", IFBT=E32,
IFBN=6, E1T1N=2, STRTTS=18, ENDTS=18, SPFBN=1,
SUBBN=0, SUBBCID=0, LNKTYPE=MTP364K;
ADD N7LNK: INDEX=0, NAME="TO_BSC1", LKSIDX=0, SLC=2,
SNDSLC=2, TESTCODE=170, MTP2NO=0;
Remark
Add the MTP2 link from the SPC (902) of MGW 1 to the BSC.
Add the MTP3 link from the SPC (2A) of MGW 1 to the BSC. No MTP
route must be configured because the SP with the SPC 2A is assisted by
the SP with the SPC 902.
3.
Add the data relevant to A-interface circuit management.

Description
Add the data relevant to A-interface circuit management. The data

includes the A-interface circuit pool, BSC, A-interface trunk group, and
A-interface circuits.
Script
ADD ACPOOL: ACN=0,

BC=SFR1-1&SFR2-1&SFR3-1&SHR1-1&SHR2-1&SHR3-1&DFR-1&DHR
-1;ADD BSC: BSCID=0, BSCN="BSC1", DPC=H'10b, NI=NATB,
ACN=0, MEN=ON;
ADD AIETG: TGN=0, TGM="BSC1", DPC=H'10b, NI=NATB;
ADD AIETKC: TGN=0, TIDS=64, TIDNUM=32, CIC=64;
The procedure for adding BSC 2, BSC 3, and BSC 4 on MGW 1 is similar to the procedure
for adding BSC 1 on MGW 1. Therefore, it is not described in this document.
----End
Issue 02 (2008-04-10)

5-23



Configuring the Data on the BSC

The data configuration on the BSC varies according to the BSC supplier. For details on the
commands, refer to relevant data configuration manuals of the BSC.

This section describes other data configuration in the scenario of a new MSC Pool in a 2G
network.
Other data configuration is related to subsequent commissioning. You need to configure other
data for the NEs that require service commissioning only. To avoid the impact on existing
services, do not configure below data for the NEs that do not require MSC Pool feature
commissioning. If the commissioning is interrupted, restore the location area, cell, and service
data to the original values.
Configuring the Consistency Data
CAUTION
Configure the consistency data for the NEs that require service commissioning only. Do not
configure the consistency data for the NEs that do not required during commissioning.
To configure the consistency data of an MSC server, perform the following steps:
1.
Add location areas.

Description
5-24
Run ADD LAIGCI to add location areas. Modify the data of the
neighboring location area.

Issue 02 (2008-04-10)

Script
SX1:
ADD LAIGCI: GCI="460000012", LAIGCINAME="BSC2_LAI",
MSCN="861390801", VLRN="861390801", NONBCLAI=NO,
LAICAT=LAI, LAIT=HVLR, BSCDPC1="A61", CSNAME="SX1";
LAICAT=LAI, LAIT=HVLR, BSCDPC1="B04", CSNAME="SX1";
SX2:
LAICAT=LAI, LAIT=HVLR, BSCDPC1="10B", CSNAME="SX2";
SX3:
LAICAT=LAI, LAIT=HVLR, BSCDPC1="10B", CSNAME="SX3";
LAICAT=LAI, LAIT=HVLR, BSCDPC1="A61", CSNAME="SX3";
2.
Add cells.
Description
Issue 02 (2008-04-10)
Run ADD LAIGCI to add cells.

5-25

Script
SX1:
ADD LAIGCI: GCI="4600000120012",
LAIGCINAME="BSC2_GCI", MSCN="861390801",
VLRN="861390801", NONBCLAI=NO, LAICAT=GCI, LAIT=HVLR,
BSCDPC1="A61", CSNAME="SX1";
ADD LAIGCI: GCI="4600000600060",
BSCDPC1="B04", CSNAME="SX1";
ADD LAIGCI: GCI="4600000600070",
SX2:
ADD LAIGCI: GCI="4600000110012",
BSCDPC1="10B", CSNAME="SX2";
ADD LAIGCI: GCI="4600000600060",
ADD LAIGCI: GCI="4600000700070",
SX3:
ADD LAIGCI: GCI="4600000110012",
BSCDPC1="10B", CSNAME="SX3";
ADD LAIGCI: GCI="4600000120012",
BSCDPC1="A61", CSNAME="SX3";
----End
Configuring the Service Data

Plan the following service data on a global basis according to actual requirements (See the
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Examples.
l
Mobile service data
IN service data
Flow control data
CDR and charging data
Time parameters
The service data must be planned on a global basis in an MSC Pool. The service data configured
for each MSC server in an MSC Pool must be the same.
5-26

Issue 02 (2008-04-10)

Configuring Signaling and Voice Channels Between MSC Pool and External NEs
For details about the configuration principles of the signaling and voice channels between the
MSC Pool and the external NEs, such as the HLR, SMSC, STP, SCP, and GMSC, see 2.3
Networking Scheme for Connecting CN NEs Inside and Outside an MSC Pool.
Configuring PRN Signaling Backup Data

This section describes the steps for configuring PRN signaling backup data by taking the route
priority mode as an example. For details about the principles, see Call Termination Recovery
Principle. In the following text, the PRN signaling of SX1 is backed up by SX2.
1.
2.
3.
4.
Configure two routes for the STP.

Descr
iptio
n
The direct route from the STP to SX1 (SPC: A80001) is configured as a highpriority route. The indirect route from the STP to SX2 (SPC: A80002) and then
to SX1 (SPC: A80001) is configured as a low-priority route. Assume that the
SPC of the STP is 000028.
Scrip
t
ADD
ADD
ADD
ADD
ADD
ADD
ADD
On the standby MSC server (SX2), add the SPC of the active MSC server (SX1).
Descr
iptio
n
On SX2, run ADD OFI to add the SPC of SX1.
Scrip
t
ADD OFI: IDX=2, NATC="A80001";
On the standby MSC server (SX2), run MOD OFI to set SCCP loop flag of node 0 and
node 2 to False and set node 0 as the assistant node of node 2.
Descr
iptio
n
On SX2, run MOD OFI to set SCCP loop flag of node 0 and node 2 to False
and set node 0 as the assistant node of node 2.
Scrip
t
MOD OFI: SN="SX2_NAT", IDX="0", SCCPLF=NO;

MOD OFI: SN="SX2_NAT", IDX="2", PAC1="0", SCCPLF=NO;
On the standby MSC server (SX2), configure the SCCP SSN of SX1. PRN messages can
be handled only after the VLR SSN is configured. Redirection can be performed only after
the MSC SSN is configured.
Descr
iptio
n
Issue 02 (2008-04-10)
M3LE: LEX=0, LENAME="STP", OPC="000028", LET=SG;

M3DE: DEX=0, LENAME="SX1_NAT", DPC="A80001", LET=AS;
M3DE: DEX=1, LENAME="SX2_NAT", DPC="A80002", LET=AS;
M3LKS: LSX=0, LSNAME="STP-SX1", ADX=0, WM=SGP;
M3LKS: LSX=1, LSNAME="STP-SX2", ADX=1, WM=SGP;
M3RT: RTNAME ="STP-SX1", DEX=0,LSX=0;
M3RT: RTNAME ="STP-SX1-BK", DEX=0,LSX=1, PRI=128;
On SX2, run ADD SCCPSSN to configure the SCCP SSN of SX1. PRN
messages can be handled only after the VLR SSN is configured. Redirection
can be performed only after the MSC SSN is configured.
5-27

Scrip
t
5.
ADD SCCPSSN: SSNNM="SX2_BK_SX1_MSC", NI=NAT, SSN=MSC,

SPC="A80001", OPC=" A80001";
ADD SCCPSSN: SSNNM="SX2_BK_SX1_SCMG", NI=NAT, SSN=SCMG,
SPC="A80001", OPC=" A80001";
ADD SCCPSSN: SSNNM="SX2_BK_SX1_VLR", NI=NAT, SSN=VLR,
SPC="A80001", OPC=" A80001";
On the standby MSC server (SX2), add the M3UA local entity of the active MSC server
(SX1). This local entity is assisted by the M3UA local entity of SX2.
Descr
iptio
n
On SX2, add the M3UA local entity of SX1. This local entity is assisted by the
M3UA local entity of SX2.
Scrip
t
ADD M3LE: LENM="SX2_BK_SX1", OPC="A80001", LET=AS;

MOD M3LE: LENM="SX2_BK_SX1", ASLE=LE0-1;
----End
The PRN signaling backup of MSC server 2 and MSC server 3 is similar to that of MSC server
1, and therefore is not described here.
Configuring Chain Backup Data

In applications, chain backup is usually used. This section describes the steps for configuring
chain backup data.
1.
2.
Set the MSC Pool backup configuration.

Descr
iptio
n
On MSC server 1, MSC server 2, and MSC server 3, run SET

POOLBKPCTRL to set the MSC Pool backup configuration.
Scrip
t
SET POOLBKPCTRL: ENABLEBKP=YES;
Set the MSC Pool backup route.

Descr
iptio
n
5-28
On MSC server 1, MSC server 2, and MSC server 3, run ADD

POOLBKPRT to set the MSC Pool backup route. MSC server 2 is the backup
server of MSC server 1, MSC server 3 is the backup server of MSC server 2,
and MSC server 1 is the backup server of MSC server 3.

Issue 02 (2008-04-10)

Scrip
t
SX1
ADD M3DE: DENM="SX2_NAT", DPC="A80002", DET=AS;
ADD M3LKS: LSNM="SX1_SX2", ADNM="SX2_NAT", WM=IPSP;
ADD M3RT: RTNM="SX1_SX2", DENM="SX2_NAT", LSNM="SX1_SX2";
ADD POOLBKPRT: MN="SX2_NAT", ROLETYPE=HomeMSC,
RTNAME="SX1_SX2";
ADD POOLBKPRT: MN="SX3_NAT", ROLETYPE=BakMSC,
RTNAME="SX1_SX3";
SX2
RTNAME="SX2_SX3";
RTNAME="SX2_SX1";
SX3
RTNAME="SX3_SX1";
RTNAME="SX3_SX2";
----End
Configuring Centralized Backup Data

When the networking in the centralized backup mode is adopted, you must configure the standby
MSC server for centralized backup. The standby MSC server handles the call termination failure
problem only and does not handle services. Therefore, you need to configure only the following
data on the standby MSC server:
l
Hardware data
Local office data
Data for interworking with the MGW
Data for interworking with the BSC
Data for interworking with the HLR
Data for interworking with other MSCs through M3UA
LAI or GCI data
For details on how to configure the preceding data, refer to the HUAWEI MSOFTX3000 Mobile
SoftSwitch Center Configuration Examples.
Issue 02 (2008-04-10)

5-29

Besides the data of the standby MSC server, you also need to add on each MGW M3UA
destination signaling points (including M3UA links) to the standby MSC server. For details on
how to configure the data of M3UA signaling points (SPs) and M3UA links between the MGW
and the MSC server, see Configuring the Data on MSC server 1 in 5.4.3 Building an MSC
Pool in the Core Network.

Only the new and changed commissioning testing introduced by the MSC Pool feature is
described in this section. Other common commissioning must be performed based on the basic
procedures. The commissioning can be performed during the whole evolution process. The
following sections provide a commissioning example. You can make adjustments according to
the actual requirements.
Preparations
l
On the M2000, set the available capacity of all MGWs in the MSC Pool.
On the MGW to be commissioned, set all CN nodes in Inhibited state to Offload state based
on the commissioning plan. As shown in the following table, the CN nodes MSC server 1,
MSC server 2, and MSC server 3 corresponding to MGW 1 must be changed from Normal/
Inhibited/Inhibited to Normal/Offload/Offload if MGW 1 and the CN nodes are to be
commissioned.
NE
MSC Server 1
(Current/
Commissioning)
MSC Server 2
(Current/
Commissioning)
MSC Server 3
(Current/
Commissioning)
MGW1
Normal/Normal
Inhibited/Offload
Inhibited/Offload
MGW2
Inhibited/Offload
Normal/Normal
Inhibited/Offload
MGW3
Inhibited/Offload
Inhibited/Offload
Normal/Normal
Disable the paging over the entire network.

Description
Run MOD MSFP to disable the paging over the entire network.
Script
MOD MSFP: ID=P1151, MODTYPE=P1, BIT=1, BITVAL=1;
On the M2000, check whether the signaling links are normal.

On the M2000, check whether the status of all signaling links is normal.
5-30
Check whether the voice channels are normal.

1.
Connect a commissioning subscriber to BSC 1 and MSC server 1
2.
On the M2000, run ADD TKTEST to notify MSC server 1 to use the existing Ainterface specified dialing test function to test the voice channels. Specify the MGW
name in the specified dialing test table.
3.
Check whether the voice channels are properly set up and the quality of the voice.
Issue 02 (2008-04-10)

4.
Go through substeps 2 to 3 repeatedly for all voice channels that the subscriber may
use.
5.
Connect a commissioning subscriber to BSC 2, BSC 3, or BSC 4. Repeat substeps 1

to 4 until the function is tested for all BSCs in the MSC Pool area.
Checking Load Redistribution in MSC Pool

To check whether the load redistribution in the MSC Pool is normal, perform the following steps:
1.
Connect a subscriber to BSC 1 and MSC server 1.
2.
The M2000 sends a message to MSC server 1 to redistribute the commissioning subscribers
to MSC server 2.
3.
After the subscribers are redistributed, the M2000 sends a message to MSC server 2 to
redistribute the subscribers to MSC server 3.
4.
Connect a commissioning subscriber to BSC 2/BSC 3/BSC 4. Repeat steps 1 to 3 until the
function is tested for all BSCs in the MSC Pool area.
Checking Roaming Handover by Using the Default MSC

To check whether the roaming handover by using the default MSC in the MSC Pool is normal,
perform the following steps:
1.
Connect a subscriber to BSC 1 and MSC server 1
2.
After the subscriber roams out of the MSC Pool area, call the subscriber. Check whether
the voice channel can be set up correctly.
3.
Commissioning Disaster Recovery upon Call Termination Failure

To check whether the disaster recovery upon call termination failure in the MSC Pool is normal,
1.
Add the data for the commissioning subscriber to the GT table of the STP. Thus, when the
subscriber is called, the STP sends a PRN request to the standby MSC server based on the
configured data.
2.
3.
Make two calls to the subscriber. The first call shall fail. The second call shall be successful.
Check whether the voice channel is set up correctly.
4.
Trial Run
To carry out trial run, perform the following steps:
1.
On the MGW, run MOD CNNODE to set the status of all MSC servers to Normal.
2.
After the system runs for two location update periods or longer, check the load of the MSC
servers in the MSC Pool.
3.
Check the load sharing (number of registered subscribers) between MSC servers and the
CPU usage of them by using the real-time monitoring function of the M2000.
Issue 02 (2008-04-10)

5-31
4.

According to the actual requirements, balance the load of the MSC servers by using the
subscriber redistribution function of the M2000. This step is optional.
NOTE
The items related to the MSC Pool, such as the performance measurement, charging, and CDR, are not
described in this section. These items are checked based on the basic procedures.
5-32

Issue 02 (2008-04-10)

6 2G Network Evolution to Support MSC Pool
2G Network Evolution to Support MSC Pool
About This Chapter

This section describes the data planning and data configuration process of a 2G network evolving
to an MSC Pool network.
6.1 Evolution Scenario
This section describes the scenario of a 2G network evolving to an MSC Pool network.
This section describes the overall data configuration procedure, data planning, and MSC Pool
presetting when a 2G network evolves to an MSC Pool network.
6.3 Evolution of the Core Network
This section describes the evolution process of the core network when a 2G network evolves to
an MSC Pool network.
6.4 Integration with the Access Network
This section describes the integration process of the access network when a 2G network evolves
This section describes the configuration of other data in the scenario of 2G network evolution
to support MSC Pool.
This section describes the system commissioning when a 2G network evolves to an MSC Pool
network.
Issue 02 (2008-04-10)

6-1


An MSC Pool may be evolved from a 2G network. The characteristics of a typical 2G network
are as follows:
l
The core network adopts the softswitch solution, that is, the MSC is divided into the MSC
server and the MGW.
The access network adopts the BSS solution. The BSC in the BSS does not support the AFLEX function.
To evolve a typical 2G network into an MSC Pool, the MGW must, instead of the BSC, provide
the A-FLEX function. The details of the evolution of a 2G network into an MSC Pool are
described in the following sections.
6.1.1 Description of the Existing Network
This section describes the typical existing network.
6.1.2 Description of the Target Network
This section describes the target network evolving from a 2G network to an MSC Pool network.

This section describes the typical existing network.
Figure 6-1 shows the networking diagram of a typical existing 2G network.
Figure 6-1 Networking diagram of an existing 2G network
SX 2
SX 1
HLR/SCP/SMSC
SX 3
STP
MGW3
MGW2
MGW1
GMSC(TMSC)
BSC1
BSC2
IP bearer
BSC3
BSC4
VPLMN or other
MSCs in the HPLMN
TDM bearer
This chapter describes how a 2G network evolves into an MSC Pool by taking this network as
an example.
6-2

Issue 02 (2008-04-10)

The networking of the existing 2G network is as follows:
l
The Mc interface is based on the IP bearer. The A-interface signaling is forwarded by the
MGW, which has a built-in SG, through M2UA.
The A-interface signaling and voice channels between the MGW and BSC are based on
the TDM bearer.
The Nb interface between MGWs is based on the TDM bearer. Not all MGWs are directly
connected.
The voice channels leading from the MGW are directly connected to the GMSC (TMSC)
in the outgoing direction. The signaling and the voice are carried by the TDM bearer.
The signaling from the MSC servers is forwarded by the MGWs to the STP (M3UA is used
for communication between an MGW and an MSC server), and then to the HLR/SCP/
SMSC. The signaling is carried by the TDM bearer.
The function of the existing 2G network is as follows:
l
The A-FLEX function is not enabled on any of the NEs.
The MSC server is responsible for managing all A-interface circuits.
The virtual MGW function is not enabled on any of the MGWs.

The signaling point codes (SPCs) in existing network are used as follows:
l
MSC server 1 uses two SPCs (AA for national network and DD for national reserved
network).
MSC server 2 uses two SPCs (BB for national network and EE for national reserved
network).
MSC server 3 uses two SPs (CC for national network and FF for national reserved network).
The MGW does not use any SPC. Each BSC uses an SPC.
6.1.2 Description of the Target Network

This section describes the target network evolving from a 2G network to an MSC Pool network.
Figure 6-2 shows the networking diagram of a target network.
Issue 02 (2008-04-10)

6-3

Figure 6-2 Networking diagram of a target network

SX 1
SX 3
SX 2
SX 4
HLR/SCP/SMSC
STP
MGW1
MGW3
MGW2
GMSC (TMSC)
BSC1
BSC2
BSC3
VPLMN or other MSCs

in the HPLMN
BSC4
IP bearer
TDM bearer
As shown in Figure 6-2, the MGWs are fully connected. The signaling channels between the
MSC servers and the STP, and the voice channels between the MGWs and the GMSC (TMSC)
are based on the IP bearer. The following sections describe the networking of the target network
in further details.
The networking of the target network is as follows:
6-4
The MSC servers in the MSC Pool are fully connected. The links between them are based
on the IP bearer. The MSC servers communicate with each other using the BICC signaling.
The Nc interface between the MSC servers adopts the protocol stack BICC/M3UA/SCTP/
IP.
The Mc interface is based on the IP bearer. It adopts the protocol stack H.248/SCTP/IP.
The A-interface signaling and voice channels between the MGW and BSC are based on
the TDM bearer. The A interface adopts the protocol stack PCM/TDM (E1).
The control plane signaling transmitted over an A interface is forwarded by the built-in SG
of the MGW. The build-in SG of the MGW communicates with the MSC server over the
IP bearer. The signaling transmission between the SG and the MSC server adopts the
protocol stack BSSAP/SCCP/M3UA/SCTP/IP.
The Nb interface between MGWs is based on the IP bearer. The MGWs are fully connected.
The signaling from the MSC servers is forwarded to the STP, and then to the HLR/SCP/
SMC. The signaling is carried by the IP bearer.
The configurations of the A-interface circuits remain the same as those of the existing 2G
network. The A-interface circuits are based on the TDM bearer. The MGWs are used to
manage the A-interface circuits so that the A-interface circuits are shared by all BSCs in
the MSC Pool area.
Direct voice channels are established between each MGW in the MSC Pool and the GMSC
(TMSC). The signaling and voice channels between the MGWs and the GMSC (TMSC)
are based on the TDM bearer. The MSC Pool communicates with external networks through
Issue 02 (2008-04-10)

the GMSC; it communicates with local MSCs or toll MSCs in the local network through
the TMSC.
l
For details about the networking principles, see 3.3 General Principles of the MSC Pool
Planning.
The function of the target network is as follows:
l
The A-FLEX function is enabled on the MSC server and MGW. The BSC does not support
the A-FLEX function.
The MGW is responsible for managing the A-interface circuits.

The principles of SPCs planning related to the MSC Pool for the scenario of 2G network
evolution to support MSC Pool are the same as those for the scenario of new MSC Pool in 2G
network. In this document, the same SPCs planning is used for the scenario of 2G network
evolution to support MSC Pool and the scenario of new MSC Pool in 2G network. For details
about the SPCs planning for the scenario of 2G network evolution to support MSC Pool, see
Signaling Point Codes Description.

This section describes the overall data configuration procedure, data planning, and MSC Pool
presetting when a 2G network evolves to an MSC Pool network.
Figure 6-3 shows the basic data configuration flow of the MSC Pool.
Issue 02 (2008-04-10)

6-5

Figure 6-3 Basic data configuration flow of the MSC Pool

Start
Preparation
Evolution of
the Core
Network

Pool
Access of the
Access Network

Configuring
service
data

End
As shown in Figure 6-3, the basic data configuration of the MSC Pool consists of data planning,
evolution of the core network (CN), access of the access network, and configuration of service
data. The detailed configuration steps are described in the following sections.
6.2.1 Data Planning
This section describes the data planning in MSC Pool networking.
This section describes the data presetting procedure of an MSC Pool.
6.2.1 Data Planning

This section describes the data planning in MSC Pool networking.
Only the data planning related to the MSC Pool is described in this section. All other data
planning is outside the scope of this document. Table 6-1 lists the data planning example of the
MSC servers in an MSC Pool network.
Table 6-1 Data planning example of the MSC servers in an MSC Pool network
6-6
Name
MSC Server 1
MSC Server 2
MSC Server 3
Node name
SX1
SX2
SX3
SPC
National network:
A80001
National network:
A80002
National network:
A80003

Issue 02 (2008-04-10)

Name
Issue 02 (2008-04-10)
MSC Server 1
MSC Server 2
MSC Server 3
National reserved
network: 801
National reserved
network: 802
National reserved
network: 803
IP address
(IP address
of the
WIFM)
192.168.153.1
192.168.155.2
192.168.151.3
Length of
the NRI
(bits)
6 (recommended)
6 (recommended)
6 (recommended)
Value of
the NRI
1 (recommended)
2 (recommended)
3 (recommended)
Default
MSC
You are advised to set all MSC servers in the MSC Pool to default MSC.
Charging
mode
Capacity of
each MSC
server in
the MSC
Pool
1 million subscribers (recommended)
Value of
Null NRI
10 (recommended)
10 (recommended)
10 (recommended)
CN ID
1 (recommended)
2 (recommended)
3 (recommended)
Nonbroadcast
LAI
460004444
460005555
460006666
Data of H.
248 links
between
the MSC
server and
MGW
MGW1:
MGW1:
MGW1:
SLOCIP1="192.168.1
53.1"SLOCPORT=5000
SRMTIP1="192.168.1
67.21"SRMTPORT=500
0
SLOCIP1="192.168.1
55.2"SLOCPORT=5100
SRMTIP1="192.168.1
67.21"SRMTPORT=510
0
SLOCIP1="
192.168.151.3"SLOC
PORT=3300SRMTIP1="
192.168.167.21"SRM
TPORT=3300
MGW2:
MGW2:
MGW2:
SLOCIP1="192.168.1
53.1"SLOCPORT=2300
SRMTIP1="192.168.1
72.41"SRMTPORT=230
0
SLOCIP1="192.168.1
55.2"SLOCPORT=5200
SRMTIP1="192.168.1
72.41"SRMTPORT=520
0
SLOCIP1="
192.168.151.3"SLOC
PORT=3400SRMTIP1="
192.168.172.41"SRM
TPORT=3400
MGW3:
MGW3:
MGW3:
SLOCIP1="192.168.1
53.1"SLOCPORT=2203
SRMTIP1="192.168.1
75.42"SRMTPORT=220
3
SLOCIP1="192.168.1
55.2"SLOCPORT=5300
SRMTIP1="192.168.1
75.42"SRMTPORT=530
0
SLOCIP1="
192.168.151.3"SLOC
PORT=4600SRMTIP1="
192.168.175.42"SRM
TPORT=4600

6-7

Name
MSC Server 1
MSC Server 2
MSC Server 3
Data of
M3UA
links
between
the MSC
server and
MGW
MGW1:
MGW1:
MGW1:
LOCIP1="192.168.15
3.1"LOCPORT=6001PE
ERIP1="192.168.167
.21"PEERPORT=6001
SLOCIP1="192.168.1
55.2"SLOCPORT=4100
PEERIP1="192.168.1
67.21"PEERPORT=410
0
SLOCIP1="
192.168.151.3"SLOC
PORT=3500PEERIP1="
192.168.167.21"PEE
RPORT=3500
MGW2:
MGW2:
LOCIP1="192.168.15
5.2"LOCPORT=4200PE
ERIP1="192.168.172
.41"PEERPORT=4200
LOCIP1="
192.168.151.3"LOCP
ORT=3600PEERIP1="1
92.168.172.41"PEER
PORT=3600
MGW2:
LOCIP1="192.168.15
3.1"LOCPORT=2302PE
ERIP1="192.168.172
.41"PEERPORT=2302
MGW3:
LOCIP1="192.168.15
3.1"LOCPORT=2204PE
ERIP1="192.168.175
.42"PEERPORT=2204
MGW3:
LOCIP1="192.168.15
5.2"LOCPORT=4300PE
ERIP1="192.168.175
.42"PEERPORT=4300
MGW3:
LOCIP1="
192.168.151.3"LOCP
ORT=4700PEERIP1="1
92.168.175.42"PEER
PORT=4700
Table 6-2 lists the data planning example of the MGWs in an MSC Pool network.
Table 6-2 Data planning example of the MGWs in an MSC Pool network
Name
MGW 1
MGW 2
MGW 3
Node name
MGW1
MGW2
MGW3
SPC
For MSC server: 2A
For MSC server: 2C
For MSC server: 2D
For access network:

902
For access network:

902
For access network:

902
IP address (the
MGW adopts the
centralized
forwarding mode
for IP addresses)
192.168.167.21
192.168.172.41
192.168.175.42
Mapping between
the VMGWIDs and
the MSC servers
SX1:
SX1:
SX1:
VMGWID=0
VMGWID=1
VMGWID=1
SX2:
SX2:
SX2:
VMGWID=1
VMGWID=0
VMGWID=2
SX3:
SX3:
SX3:
VMGWID=2
VMGWID=2
VMGWID=0
Table 6-3 lists the data planning example of the BSCs in an MSC Pool network.
6-8

Issue 02 (2008-04-10)

Table 6-3 Data planning example of the BSCs in an MSC Pool network
Name
BSC 1
BSC 2
BSC 3
BSC 4
Node name
BSC1
BSC2
BSC3
BSC4
SPC
10B
A61
B04
B05
LAI
460000011
460000012
460000060
460000070
CGI
4600000110012
4600000120012
4600000600060
4600000600070

For details, see 5.4.2 Presetting Data for the MSC Pool in "New MSC Pool in 2G Network."

This section describes the evolution process of the core network when a 2G network evolves to
an MSC Pool network.
6.3.1 Overview
This section describes the evolution of the core network.
6.3.2 Making MSC Server 1 and MGW 1 as an MSC Pool
This section describes the data configuration in the evolution of the core network.
6.3.3 Adding MSC Server 2 into the MSC Pool
6.3.4 Adding MGW 2 into the MSC Pool
6.3.1 Overview
This section describes the evolution of the core network.
The evolution process consists of:
l
Evolution of the core network
Access of the access network
System commissioning
The following two solutions are available for the evolution:

l
Issue 02 (2008-04-10)
Solution 1:
6-9

1.
Use SX1, SX2, MGW 1, and MGW 2 to form a simplest MSC Pool.
2.
Add BSC 1 and BSC 2 to the MSC Pool.
3.
Commission the network.
4.
Add SX3, MGW 3, BSC 3, and BSC 4 to the MSC Pool.
Solution 2:
1.
Evolve the entire core network into an MSC Pool.
2.
Add BSC 1, BSC 2, BSC 3, and BSC 4 into the MSC Pool.
This document describes the evolution of the network by taking solution 2 as an example.
6.3.2 Making MSC Server 1 and MGW 1 as an MSC Pool

Figure 6-4 shows an MSC Pool composed of MSC server 1 and MGW 1.
Figure 6-4 MSC Pool composed of MSC server 1 and MGW 1
SX1
MSC
Pool
MGW
1
BSC
1
SX2
MGW
2
BSC
2
H248 link
SX3
MGW
3
BSC
3
BSC
4
M3UA link
Key Points of the Entire Configuration

Key points of the entire configuration are as follows:
l
Configure related M3UA data on MGW 1 and MSC server 1.
After configuring the data of the newly added M3UA, add mapping information on MGW
1. Set Manage Status corresponding to MSC server 1 to Inhibited.

Add related configuration of the M3UA on MSC server 1 for interworking with MGW 1.
6-10

Issue 02 (2008-04-10)

Description
Add an M3UA local entity, M3UA destination entity, M3UA link, and
M3UA route.
Script
ADD M3LE: LENM="SX1_NATB", NI=NATB, OPC="801", LET=AS;

ADD M3DE: DENM="TO_MGW1_NATB", NI=NATB, DPC="2A", DET=SG;
ADD M3LKS: LSNM="TO_MGW1_NATB", ADNM="TO_MGW1_NATB",
WM=ASP;
LOCIP1="192.168.153.1", LOCPORT=6001,
Remark
Add the M3UA data for MSC server 1 (SPC: 801) to interwork with MGW
1 (SPC: 2A).

To configure the data on the MGW, perform the following steps:
1.
Set MSC Pool function information.

Description
Set MSC Pool function information.
Script
Remark

The MSC Pool Control Flag parameter is set to Open, indicating that
the MGW can serve as the NNSF.
2.
Issue 02 (2008-04-10)
Add the SIGTRAN configuration to MSC server 1.

Description
Add the SIGTRAN configuration on MGW 1 for interworking with

MSC server 1 where Network Type is MSC Pool.
Script

OPC=H'2A;
OPC=H'902;
ADD M3DE: DEX=0, DEN="SX1", DET=AS, NI=NATB,
DPC=H'801, LEX=0, NETTYPE=MSCPOOl;
LIP1="192.168.167.21", LP=6001, RIP1="192.168.153.1",

6-11
Remark

Add two M3UA local entities for the MGW.

Add the M3UA destination entity (that is, an MSC server) for one
M3UA local entity of the MGW. The network type is MSC Pool. A
corresponding M3UA route must be added.
Add the M3UA destination entity (that is, an MSC server) for the other
M3UA local entity of the MGW. It is not required to add M3UA route
data.
3.
Add a CN node of MSC server 1 and the mapping between NRI and MSC server 1.
Description
Add a CN node of MSC server 1 and the mapping between NRI and
MSC server 1 where Manage Status is Inhibited.
Script

MNGSTA=INHIBITED;
----End
NOTE
All above data is newly added data. If you need to roll back the data configuration, delete the added data.
Ending the Data Configuration

After all the data is configured, run M3UA link maintenance commands of the MSC server and
the MGW on the M2000 to check all the M3UA links.
You can proceed with the next step, if the following conditions are met:
l
No fault alarm occurs.
The service dialing test is normal.
Entire system runs well after at least one periodic location update.

Figure 6-5 shows an MSC Pool including MSC server 2.
6-12

Issue 02 (2008-04-10)

Figure 6-5 MSC Pool including MSC server 2

SX1
SX2
SX3
unavailable
MGW
1
BSC
1
MGW
2
MGW
3
BSC
2
H248 link
BSC
3
BSC
4
M3UA link

l
Configure related data of the newly added H.248 link and M3UA link on MGW 1 and MSC
server 2.
After configuring the data of the newly added M3UA link and H.248 link, add mapping
information on MGW 1. Set Manage Status corresponding to MSC server 2 to Inhibited.

To configure the data on the MSC server, perform the following steps:
1.
Add MGW 1 on MSC server 2 and an H.248 link from MSC server 2 to MGW 1.
Description
Issue 02 (2008-04-10)
Add MGW 1 on MSC server 2 and an H.248 link from MSC server 2
to MGW 1.

6-13
Script
2.


BCUID=1, BNCC=TDM-1&IP-1&AAL1STRUCT-1&AAL2-1&AAL1-1,
SPCATTR=SDPHEX-1&NOBNC-1&NOEC-1&NOJTTR-1&NOFAX-1&NOMOD
EM-1&LOCSDPP-1&SUPH248V2-1&NOVERNEG-0&SUPCODECCFG-1,
ENCT=NSUP,
CPB=TONE-1&PA-1&SENDDTMF-1&DETECTDTMF-1&MPTY-1&IWF-1,
ECRATE=300, IWFRATE=300, TONERATE=300, MPTYRATE=300,
DETDTMFRATE=300, SNDDTMFRATE=300,
-1&RATE795-1,
UMTSAMR2R=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RATE
740-1&RATE795-1&RATE102-1&RATE122-1,
-1&RATE795-1&RATE102-1&RATE122-1,
UMTSAMRR=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RATE7
40-1&RATE795-1&RATE102-1&RATE122-1,
MODEMLST=GSMMT-1&GSMV21-1&GSMV22-1&GSMV22BIS-1&GSMV231&GSMV26TER-1&GSMV32-1&GSMMTAUTO-1&GSMV34-1,
TC=GSMEFR-1&GSMHR-1&TDMAEFR-1&PDCEFR-1&HRAMR-1&UMTSAMR
2-1&FRAMR-1&PCMA-1&PCMU-1&UMTSAMR-1&G7231-1&G729A-1&GS
MFR-1;
SLOCPORT=5100, SRMTIP1="192.168.167.21",
Add related data configuration of the M3UA on MSC server 2 for interworking with MGW
1.
Description
Add related data configuration of the M3UA on MSC server 2 for

interworking with MGW 1.
Script

STPF=TRUE, DET=SG;
WM=ASP;
LOCIP1="192.168.155.2", LOCPORT=4100,
----End

1.
Set a virtual MGW on MGW 1, and add an H.248 link for interworking with MSC server
2.
Description
6-14
Set a virtual MGW on MGW 1, and add an H.248 link for interworking
with MSC server 2.

Issue 02 (2008-04-10)

Script
2.
3.

RLSINTV=30, LNKFAILLEN=30, IPNUM=86016,
TDMNUM=400384, ATMNUM=221184, AUTOSWP=YES,
LNKHBTIME=3, LNKMAXHBLOSS=5, MWDMODE=STATIC,
MWDVAL=0, CISTT=1000, NETTYPE=WCDMA, ROOTLENGTH=8,
NONROOTLENGTH=8, CODEC=G.711A,
BP=BACK;
Add an M3UA destination signaling point for interworking with MSC server 2 and related
M3UA configuration.
Description
Add an M3UA destination signaling point for interworking with MSC

server 2 and related M3UA configuration.
Script

LIP1="192.168.167.21", LP=6001, RIP1="192.168.155.2",
Add a CN node of MSC server 2 and the mapping between NRI and MSC server 2 on MGW
1 where Manage Status is Inhibited.
Description
MSC server 2 on MGW 1.
Script

MNGSTA=INHIBITED;
----End
NOTE

After all the data is configured, run M3UA and H.248 link maintenance commands of the MSC
server and the MGW on the M2000 to check all the M3UA and H.248 links.
Issue 02 (2008-04-10)

6-15


l
Entire system runs well for at least one periodic location update.

Figure 6-6 shows an MSC Pool including MGW 2.
Figure 6-6 MSC Pool including MGW 2
SX1
SX2
SX3
unavailable
MGW
1
BSC
1
MGW
2
MGW
3
BSC
2
H248 link
BSC
3
BSC
4
M3UA link

l
Configure related M3UA data on MGW 2 and MSC server 2, and use the existing H.248
data.
server 1.
After configuring the data of the newly added H.248 link and M3UA link, add mapping
information on MGW 2. Set Manage Status corresponding to MSC server 1 to Inhibited.

1.
Add related M3UA data on MSC server 2 to interwork with MGW 2.

Description
6-16
Add an M3UA destination entity, M3UA linkset, M3UA link and

M3UA route.

Issue 02 (2008-04-10)

Script
2.
3.
Issue 02 (2008-04-10)

STPF=TRUE, DET=SG;
WM=ASP;
LOCIP1="192.168.155.2", LOCPORT=4100,
Add MGW 2 on MSC server 1 and an H.248 link from MGW 2 to MSC server 1.
Description
Add MGW 2 on MSC server 1 and an H.248 link from MGW 2 to MSC
server 1.
Script

ENCT=NSUP,
-1&RATE795-1,
740-1&RATE795-1&RATE102-1&RATE122-1,
-1&RATE795-1&RATE102-1&RATE122-1,
40-1&RATE795-1&RATE102-1&RATE122-1,
MFR-1;
SLOCPORT=2300, SRMTIP1="192.168.172.41",
Add related data configuration of the M3UA on MSC server 1 to interwork with MGW 2.
Description
Add related data configuration of the M3UA on MSC server 1 to

interwork with MGW 2.
Script

STPF=TRUE, DET=SG;ADD M3LKS: LSNM="TO_MGW2_NATB",
LOCIP1="192.168.153.1", LOCPORT=2302,

6-17

----End

1.
2.
3.
6-18
Set MSC Pool function information on MGW 2.

Description
Script
Set a virtual MGW on MGW 2, and add an H.248 link to interwork with MSC server 1.
Description
Set a virtual MGW on MGW 2, and add an H.248 link to interwork with
MSC server 1.
Script

ATMNUM=221184, AUTOSWP=YES, LNKHBTIME=3,
LNKMAXHBLOSS=5, MWDMODE=STATIC, MWDVAL=0, CISTT=1000,
NETTYPE=WCDMA, ROOTLENGTH=8, NONROOTLENGTH=8, CODEC=G.
711A, MASTERMGCDETECTFLAG=NO, MASTERMGCDETECTTIME=5;
BP=BACK;
Add the configuration of the SIGTRAN on MGW 2 to interwork with MSC server 1 and
MSC server 2 where Network Type is MSCPOOl.
Description
Add the configuration of the SIGTRAN on MGW 2 to interwork with

Script

OPC=H'2C;
OPC=H'902;
LIP1="192.168.172.41", LP=2300, RIP1="192.168.153.1",

Issue 02 (2008-04-10)

4.
Description
Add the configuration of the SIGTRAN on MGW 2 to interwork with

Script

LIP1="192.168.172.41", LP=5200, RIP1="192.168.155.2",
Add CN nodes of MSC server 1 and MSC server 2 and the mapping between NRI and MSC
server 1 and between NRI and MSC server 2 on MGW 2 where Manage Status is Inhibited.
Description
Script

MNGSTA=INHIBITED;
Description
Script

MNGSTA=INHIBITED;
----End
NOTE

l

Figure 6-7 shows an MSC Pool including MSC Server 3.
Issue 02 (2008-04-10)

6-19

Figure 6-7 MSC Pool including MSC Server 3

SX1
SX2
unavailable
unavailable
MGW
1
BSC
1
SX3
MGW
2
MGW
3
BSC
2
BSC
3
BSC
4
M3UA link
H248 link

l
Configure related data of the newly added H.248 link and M3UA link on MGW 1, MGW
2, and MSC server 3.
information on MGW 1 and MGW 2. Set Manage Status corresponding to MSC server 3
to Inhibited.

1.
Add MGW 1 and MGW 2 on MSC server 3 and H.248 links from MGW 1 to MSC server
3 and MGW 2 to MSC server 3.
Description
6-20
server 3.

Issue 02 (2008-04-10)

2.
Issue 02 (2008-04-10)
Script

ENCT=NSUP,
-1&RATE795-1,
740-1&RATE795-1&RATE102-1&RATE122-1,
-1&RATE795-1&RATE102-1&RATE122-1,
40-1&RATE795-1&RATE102-1&RATE122-1,
MFR-1;
SLOCPORT=3300, SRMTIP1="192.168.167.21",
Description
server 3.
Script

ENCT=NSUP,
-1&RATE795-1,
740-1&RATE795-1&RATE102-1&RATE122-1,
-1&RATE795-1&RATE102-1&RATE122-1,
40-1&RATE795-1&RATE102-1&RATE122-1,
MFR-1;
SLOCPORT=3400, SRMTIP1="192.168.172.41",
Add related data configuration of the M3UA on MSC server 3 to interwork with MGW 1
and MGW 2.
6-21

Description

Script

STPF=TRUE, DET=SG;
WM=ASP;
LOCIP1="192.168.151.3", LOCPORT=3500,
Description

Script

STPF=TRUE, DET=SG;
WM=ASP;
LOCIP1="192.168.151.3", LOCPORT=3600,
----End

1.
Add virtual MGWs on MGW 1 and MGW 2, and add an H.248 link to interwork with MSC
server 3.
Description
6-22
Set a virtual MGW on MGW 1, and add an H.248 link to interwork

with MSC server 3.

Issue 02 (2008-04-10)

2.
Issue 02 (2008-04-10)
Script

BP=BACK;
Description
Set a virtual media gateway on MGW 2, and add an H.248 link to

interwork with MSC server 3.
Script

BP=BACK;
Add M3UA destination signaling points to interwork with MSC server 3 and related M3UA
configuration on MGW 1 and MGW 2.
Description
Add an M3UA destination signaling point to interwork with MSC

server 3 and related M3UA configuration on MGW 1.
Script

ADD M3LKS: LSX=2, LSN="SX3", ADX=2;ADD M3RT: RN="SX3",
DEX=2, LSX=2;
LIP1="192.168.167.21", LP=3500, RIP1="192.168.151.3",

6-23
3.

Description

Script

ADD M3LKS: LSX=2, LSN="SX3", ADX=2;ADD M3RT: RN="SX3",
DEX=2, LSX=2;
LIP1="192.168.172.41", LP=3600, RIP1="192.168.151.3",
Add CN nodes of MSC server 3 and the mapping between NRI and MSC server 3 on MGW
1 and MGW 2 where Manage Status is Inhibited.
Description
Add a CN node of MSC server 3 and the mapping relation between NRI
and MSC server 3 on MGW 1.
Script

MNGSTA=INHIBITED;
Description
Script

MNGSTA=INHIBITED;
----End
NOTE

l

6-24

Issue 02 (2008-04-10)


SX1
SX3
SX2
unavailable
MGW
1
BSC
1
MGW
2
MGW
3
BSC
2
H248 link
BSC
3
BSC
4
M3UA link

l
Configure related M3UA data on MGW 3 and MSC server 3, and use the existing H.248
data.
Configure related data of the newly added H.248 link and M3UA link on MGW 3, MSC
server 1 and MSC server 2.
information on MGW 3. Set Manage Status corresponding to MSC server 1 and MSC server
2 to Inhibited.

1.
2.
Issue 02 (2008-04-10)
Add related M3UA data on MSC server 3 for interworking with MGW 3.
Description
Add an M3UA destination entity, M3UA linkset and M3UA route.
Script

STPF=TRUE, DET=SG;
WM=ASP;
LOCIP1="192.168.151.3", LOCPORT=4700,
Add MGW 3 on MSC server 1 and MSC server 2 and H.248 links from MGW 3 to MSC
6-25
6-26

Description
server 1.
Script

ENCT=NSUP,
-1&RATE795-1,
740-1&RATE795-1&RATE102-1&RATE122-1,
-1&RATE795-1&RATE102-1&RATE122-1,
40-1&RATE795-1&RATE102-1&RATE122-1,
MFR-1;
SLOCPORT=2203, SRMTIP1="192.168.175.42",
Description
server 2.
Script

ENCT=NSUP,
-1&RATE795-1,
740-1&RATE795-1&RATE102-1&RATE122-1,
-1&RATE795-1&RATE102-1&RATE122-1,
40-1&RATE795-1&RATE102-1&RATE122-1,
MFR-1;
SLOCPORT=5300, SRMTIP1="192.168.175.42",

Issue 02 (2008-04-10)

3.
Add related data configuration of the M3UA on MSC server 1 and MSC server 2 for
Description

Script

STPF=TRUE, DET=SG;
WM=ASP;
LOCIP1="192.168.153.1", LOCPORT=2204,
Description

Script

STPF=TRUE, DET=SG;
WM=ASP;
LOCIP1="192.168.155.2", LOCPORT=4300,
----End

1.
2.

Description
Script
Set a virtual media gateway on MGW 3, and add an H.248 link for interworking with MSC
Description
Issue 02 (2008-04-10)
Set a virtual media gateway on MGW 3, and add an H.248 link for

6-27
3.
6-28

Script

BP=BACK;
Description
Script

BP=BACK;
Add the configuration of the SIGTRAN on MGW 3 for interworking with MSC server 1,
MSC server 2, and MSC server 3 where Network Type is MSCPOOl.
Description
Add the configuration of the SIGTRAN on MGW 3 for interworking

with MSC server 1 where Network Type is MSCPOOl.
Script

OPC=H'2D;
OPC=H'902;
DPC=H'801, LEX=0, NETTYPE=MSCPOOL;
LIP1="192.168.175.42", LP=2204, RIP1="192.168.153.1",

Issue 02 (2008-04-10)

4.
Issue 02 (2008-04-10)
Description

Script

LIP1="192.168.175.42", LP=4300, RIP1="192.168.155.2",
Description

Script

LIP1="192.168.175.42", LP=4700, RIP1="192.168.151.3",
Add CN nodes of MSC server 1, MSC server 2 and MSC server 3 and the mapping between
NRI and MSC server 1, NRI and MSC server 2, and NRI and MSC server 3 on MGW 2
where Manage Status is Inhibited.
Description
Script

MNGSTA=INHIBITED;
Description
Script

MNGSTA=INHIBITED;
Description

6-29
Script


MNGSTA=INHIBITED;
----End
NOTE

l
6.4 Integration with the Access Network

This section describes the integration process of the access network when a 2G network evolves
6.4.1 Adding BSC 1 into the MSC Pool
This section describes the data configuration in the access process of the access network.
6.4.2 Connecting BSC 1 to MSC Server 2 in the MSC Pool
6.4.6 Adding BSC4 into the MSC Pool

The BSC is added into the MSC Pool by following mode:
l
6-30
Mode 1: Allocate timeslots in the preliminary physical trunks and links. During the
evolution of the core network, delete preliminary links and configure new links.
Issue 02 (2008-04-10)

l
Mode 2: Add the physical trunks for the BSC. Configure links on the new trunk. During
the evolution of the core network, change physical trunks of the BSC, and delete preliminary
links.
NOTE
For mode 1, the duration of the service interruption is long, and you are advised to use mode 1 when the
trunk resources of the current networking are limited. In mode 1, the signaling point modification of the
access side and the data modification can be performed simultaneously. Mode 2 is used only when the
trunk resources of the current networking are sufficient.

l
Add the M3UA destination entity and M3UA route on MSC server 1 for interworking with
BSC 1.
If the BSC is added to the MSC Pool by mode 1, perform the following steps:
1.
Modify the timeslots of physical trunks for MGW 1 and BSC 1 simultaneously.
2.
Complete the management configuration of the A-interface circuit on MGW 1.
3.
Enable the circuit management function on MGW 1.
4.
Disable the circuit management function of BSC 1 on MSC server 1.
5.
Modify the destination signaling point of BSC 1, and connect BSC 1 to the MSC Pool.
----End
l
If BSC2 is added into the MSC Pool by mode 2, perform the following steps:
1.
Add timeslots of physical trunks between MGW 1 and BSC 1.
2.
Complete the management configuration of the A-interface circuit on MGW 1.
3.
Enable the circuit management function on MGW 1.
4.
Disable the circuit management function of BSC 1 on MSC server 1.
5.
Modify the destination signaling point of BSC 1, and connect BSC 1 to the MSC Pool.
----End
l
Set Manage Status corresponding to MSC server 1 to Normal, and Manage Status
corresponding to MSC server 2 and MSC server 3 to Inhibited.

1.
Issue 02 (2008-04-10)
Add the M3UA destination entity and M3UA route on MSC server 1 for interworking with
BSC 1.
Description
Add the M3UA destination entity and M3UA route.
Script
ADD M3DE: DENM="TO_BSC1_NATB", NI=NATB, DPC="10B",

DET=SP;
ADD M3RT: RTNM="TO_BSC1_NATB", DENM="TO_BSC1_NATB",

6-31
Remark
2.

BSC 1 (SPC: 10B). The M3UA route adopts the link set to MGW 1 for
the quasi-associated networking.
Disable the circuit management switch of BSC 1 on MSC server 1.

Description
Disable the circuit management switch of BSC 1 on MSC server 1. That

is, set MGW manage A interface circuit to Supported.
Script

MGWMAC=YES;
Remark
After enabling the circuit management switch on MGW 1, disable the

circuit management switch of BSC 1 on MSC server 1.
----End
Configuring Data on the MGW Based on Mode 1

To configuring data on the MGW based on mode 1, perform the following steps:
6-32
1.
Set Manage Status corresponding to MSC server 1 to Normal on MGW 1. Activate the
MGW. Set the BSC to be in management state. Manage Status corresponding to MSC
server 1 is set to Normal, while Manage Status corresponding to MSC server 2 and MSC
server 3 is set to Inhibited.
2.
Delete the configuration of the preliminary signaling of BSC 1 on MGW 1. (The signaling
adopts the M2UA bearer or TDM semipermanent connection bearer.)
3.
Delete the TDMIU data that is for interworking with BSC 1. Then add the TDMIU data,
and set Relay type to ATRUNK.
4.
Add configurations of narrowband signaling (N7DSP) for interworking with BSC 1, and
set Network Type corresponding to N7DSP to MSCPOOl.
Description
Add configurations of narrowband signaling (N7DSP) for interworking

with BSC 1, and set Network Type corresponding to N7DSP to
MSCPOOl.
Script

OSPINDEX=0, NETTYPE=MSCPOOl;

Issue 02 (2008-04-10)

Remark
Add the MTP3 link from the SPC (2A) of MGW 1 to the BSC. No MTP
route must be configured because the SP with the SPC 2A is assisted
by the SP with the SPC 902.
5.
Add related configurations of A-interface circuit management.

Description
Add related configurations of A-interface circuit management, such as

A-interface circuit pool, BSC configuration, A-interface circuit trunk
group, and A-interface circuit.
Script
ADD ACPOOL: ACN=0,

-1;
ADD BSC: BSCID=0, BSCN="BSC 1", DPC=H'10b, NI=NATB,
ACN=0, MEN=ON;
----End
Configuring Data on the MGW Based on Mode 2

To configuring data on the MGW based on mode 2, perform the following steps:
1.
Set Manage Status corresponding to MSC server 1 to Normal on MGW 1. Activate the
MGW. Set the BSC to be in management state. Manage Status corresponding to MSC
server 1 is set to Normal, while Manage Status corresponding to MSC server 2 and MSC
server 3 is set to Inhibited.
2.
Add the TDMIU data for interworking with BSC 1, and set Relay type to ATRUNK.
3.
Description
Add the TDMIU data for interworking with BSC 1, and set Relay
type to ATRUNK.
Script
ADD TDMIU: BT=E32, BN=6, TIDFV=64, TIDLV=127,

VMGWID=0, RT=ATRUNK;
Add configurations of narrowband signaling (N7DSP) for interworking with BSC 1, and
set Network Type corresponding to N7DSP is MSCPOOl.
Description
Issue 02 (2008-04-10)
Add configurations of narrowband signaling (N7DSP) for interworking

with BSC 1, and set Network Type corresponding to N7DSP is
MSCPOOl.

6-33
4.
5.

Script

Remark
Before adding the destination signaling points of MSC Pool type, you
must delete preliminary N7DSP signaling points unless the new
signaling points are added for the interworking BSC.
Add related configurations of A-interface circuit management.

Description
Add related configurations of A-interface circuit management, such as

A-interface circuit pool, BSC configuration, A-interface circuit trunk
group, and A-interface circuit.
Script
ADD ACPOOL: ACN=0,

-1;
ADD BSC: BSCID=0, BSCN="BSC 1", DPC=H'10b, NI=NATB,
ACN=0, MEN=ON;
Change the trunk lines of BSC 1, enable the BSC management switch, and perform the
system commissioning.
----End
Configuring Data on the BSC

Configure the data on BSC 1 by using either of the following modes:
l
Mode 1: Change the destination signaling point of BSC 1 by from "DD" to "XX", and add
BSC 1 into the MSC Pool.
Mode 2: Change the destination signaling point of BSC 1 by from "DD" to "XX". Modify
the trunk timeslot of BSC 1 for interworking with MGW 1 and add BSC 1 into the MSC
Pool.

After all the data is configured, run signaling link and trunk circuit maintenance commands of
the MSC server, MGW, and BSC on the M2000 to check all the signaling links and trunk circuits.
6-34
Entire system runs well for at least one Periodic Location Update.
Issue 02 (2008-04-10)



l
Add BSC 1on MSC server 2.
Add paging control data on MSC server 2.
Disable the A-interface circuit switch of BSC 1 on MSC server 2, which disables MSC
server 2 to manage A-interface circuit of BSC 1.
Activate the virtual MGW corresponding to MSC server 2 on MGW 1.

1.
Add related data of BSC 1 on MSC server 2.

(1) Add an M3UA destination entity of BSC 1.
Descriptio
n
Add an M3UA destination entity of BSC 1.
Script
ADD M3DE: DENM="BSC1", LENM="SX2_NATB", NI=NATB,

DPC="10B", DET=SP;
(2) Add an office direction of BSC 1.

Descriptio
n
Add an office direction of BSC 1.
Script
ADD OFC: ON="BSC1", OOFFICT=BSC, DOL=LOW, DOA=BSC,

BOFCNO=1,OFCTYPE=COM, SIG=NONBICC/NONSIP, NI=NATB,
(3) Add related data of BSC 1 on MSC server 2.

Descriptio
n
Script
ADD BSC: NI=NATB, DPC="10B", OPC="802", BSCNM="BSC

1",
CAPABILITY=CCPAGING-1&SMSPAGING-1&SSPAGING-1&PSIPAG
ING-1&LCS-1&SERVICEHO-1&DTM-1&LOADHO-1&MGWPROXYAFLE
X-1&PRIVATEMSG-1&SupportActiveTrace-1,
RSSCNAME="SX2", MLAIF=YES, MGWMAC=YES;
(4) Add an M3UA route for interworking with BSC 1.

Descriptio
n
Issue 02 (2008-04-10)
Add an M3UA route for interworking with BSC 1.

6-35

Script
ADD M3RT: RTNM="BSC1", DENM="BSC1",

(5) Add an SCCP destination signaling point.

Descriptio
n
Add an SCCP destination signaling point.
Script
ADD SCCPDSP: DPNM="BSC1", NI=NATB, DPC="10B",

OPC="802";
(6) Add SCCP subsystems.

Descriptio
n
Add SCCP subsystems.
Script
ADD SCCPSSN: SSNNM="BSC1_SCMG", NI=NATB, SSN=SCMG,

SPC="10B", OPC="802";
ADD SCCPSSN: SSNNM="BSC1_BSSAP", NI=NATB,
SSN=BSSAP, SPC="10B", OPC="802";
(7) Add an A-interface trunk group.
2.
3.
Descriptio
n
Add an A-interface trunk group for the performance measurement

of the trunk group on MSC server 2.
Script
ADD AIETG: TGNAME="BSC1", MGWNAME="MGW1",

SOPC="802", SDPC="10B", CPNAME="BSC1", BTG=1;
Add paging control information of the location area served by BSC 1 on MSC server 2.
Description
Add paging control information of the location area served by BSC 1

on MSC server 2.
Script
Disable the circuit management switch of BSC 1 on MSC server 2.

Description
Disable the circuit management switch of BSC 1 on MSC server 2. That

is, set MGW manage A interface circuit to Supported.
Script

MGWMAC=YES;
----End

6-36

Issue 02 (2008-04-10)

Description
Script
ACT VMGW: VMGWID=1;
Configuring Data on the BSC

None

After all the data is configured, run signaling link and trunk circuit maintenance commands of
the MSC server, MGW, and BSC on the M2000 to check all the signaling links and trunk circuits.
l

For detailed configuration, see 6.4.2 Connecting BSC 1 to MSC Server 2 in the MSC Pool.

For detailed configuration, see 6.4.1 Adding BSC 1 into the MSC Pool, 6.4.2 Connecting BSC
1 to MSC Server 2 in the MSC Pool, and 6.4.3 Connecting BSC 1 to MSC Server 3 in the
MSC Pool.

MSC Pool.
6.4.6 Adding BSC4 into the MSC Pool

MSC Pool.
Issue 02 (2008-04-10)

6-37


This section describes the configuration of other data in the scenario of 2G network evolution
to support MSC Pool.
The procedure for configuring other data in this scenario is the same as the procedure for
configuring other data in the scenario of new MSC Pool in 2G Network. For details, see the
related description in 5.5 Other Data Configuration in the "New MSC Pool in 2G Network"
chapter.

This section describes the system commissioning when a 2G network evolves to an MSC Pool
network.
Only the new and changed commissioning testing introduced by the MSC Pool feature is
described in this section. Other common commissioning must be performed based on the basic
procedures. The commissioning can be performed during the whole evolution process. The
following sections provide a commissioning example. You can make adjustments according to
the actual requirements.
Preparations
Make the following preparations:
1.
On the M2000, set the available capacity of all MGWs in the MSC Pool.
2.
On the MGW to be commissioned, set all CN nodes in Inhibited state to Offload state based
on the commissioning plan. As shown in Table 6-4, the CN nodes MSC server 1, MSC
server 2, and MSC server 3 corresponding to MGW 1 must be changed from Normal/
Inhibited/Inhibited to Normal/Offload/Offload if MGW 1 and the CN nodes are to be
commissioned.
Table 6-4 Changing status of MSC servers
3.
6-38
NE
MSC server 1
(Current/
Commissioning)
MSC server 2
(Current/
Commissioning)
MSC server 3
(Current/
Commissioning)
MGW 1
Normal/Normal
Inhibited/Offload
Inhibited/Offload
MGW 2
Inhibited/Offload
Normal/Normal
Inhibited/Offload
MGW 3
Inhibited/Offload
Inhibited/Offload
Normal/Normal

Description
Script

Issue 02 (2008-04-10)

4.
On the M2000, check whether the signaling links are normal.

5.

(1) Connect a commissioning subscriber to BSC 1 and MSC server 1.
(2) On the M2000, run ADD TKTEST to instruct MSC server 1 to use the existing Ainterface specified dialing test function to test the voice channels. Specify the MGW
name in the specified dialing test table.
(3) Check whether the voice channels are properly set up and the quality of the voice.
(4) Go through substeps 2 to 3 repeatedly for all voice channels that the subscriber may
use.
(5) Connect a commissioning subscriber to BSC 2/BSC 3/BSC 4. Repeat substeps 1 to 4
until the function is tested for all BSCs in the MSC Pool area.
----End

1.
2.
to MSC server 2.
3.
4.

1.
2.
3.

1.
configured data.
2.
3.
Issue 02 (2008-04-10)

6-39
4.

Removing Invalid Data

After the commissioning testing is completed, remove the following invalid data:
l
Remove the invalid data from the MSC server.

1.
Run RMV M2LNK to remove M2UA links.
2.
Run RMV M2LKS to remove M2UA linksets.
3.
Run RMV AIETKC to remove the A-interface trunk circuits of the BSC.
Remove the invalid data on the MGW.

If the BSC is connected to the MSC Pool base on mode 2 (see 6.4.1 Adding BSC 1 into
the MSC Pool), perform the following steps:
1.
Run RMV MTP2LNK to remove the original signaling connections of the BSC. If
the original signaling of the BSC is transmitted by TDM semi-permanent links, run
RMV SPC to remove the original BSC semi-permanent connections of the BSC.
2.
Run RMV L2UALNK to remove M2UA links.
3.
Run RMV L2UALKS to remove M2UA linksets.
4.
Run RMV TDMIU to remove the TDMIU to the BSC office direction.
5.
If a new TDM interface board to the BSC is added, the original interface board does
not have any data. Therefore, run RMV BRD to remove the original interface board.
If the BSC is connected to the MSC Pool based on mode 1 (see 6.4.1 Adding BSC 1 into the
MSC Pool), you need not remove any data as the M2UA links and TDMIU to the BSC office
direction are removed during the configuration.
Trial Run
1.
On the MGW, run MOD CNNODE to set the status of all MSC servers to Normal.
2.
3.
4.
subscriber redistribution function of the M2000.
This step is optional.
----End
NOTE
6-40

Issue 02 (2008-04-10)

New MSC Pool in the 3G Network
About This Chapter

This section describes the data planning and data configuration process of a new MSC Pool in
a 3G network.
7.1 New Target Network
This section describes the target networking and data planning of a new MSC Pool in the 3G
network.
7.3 Data Planning
This section describes the configuration of other data in the scenario of new MSC Pool in 3G
network.
This section describes the system commissioning of a new 3G network in MSC Pool mode.
Issue 02 (2008-04-10)

7-1

7.1 New Target Network

This section describes the target networking and data planning of a new MSC Pool in the 3G
network.
If required, you can build a new 3G network in MSC Pool mode. A typical new 3G network of
this kind highlights the following networking features:
l
The core network adopts the softswitch solution in which an MSC is divided into an MSC
server and an MGW.
The access network adopts the RAN solution in which the RNC supports the Iu-Flex
function and load sharing.
For details about the networking scenarios of the typical new 3G network, see subsequent
descriptions.
Figure 7-1 shows the networking of a new target network.
Figure 7-1 Networking diagram of a new target network
SX 1
SX 2
SX 3
SX 4
HLR/SCP/SMSC
STP
MGW1
MGW2
MGW3
GMSC (TMSC)
RNC1
RNC2
IP bearer
RNC3
RNC4
TDM bearer
VPLMN or other
MSCs in the HPLMN
ATM bearer
The networking of a new target network is as follows:
7-2
MSC servers in an MSC Pool are connected with each other through IP bearers (full-mesh
connection). They communicate with each other by using BICC signaling. The protocol
stack is BICC/M3UA/SCTP/IP.
The Mc interface is based on IP. The protocol stack is H.248/SCTP/IP.
Iu interface signaling and speech channels between the MGW and the RNC are based on
TDM. The protocol stack is RANAP/SCCP/MTP3b/SAAL/ATM.

Issue 02 (2008-04-10)

The control plane of the Iu interface is transferred by the SG embedded in the MGW. IP
bearers are adopted between the SG embedded in the MGW and the MSC server. The
protocol stack is RANAP/SCCP/M3UA/SCTP/IP.
The Nb interface between the MGWs is based on IP and all MGWs are connected with
each other.
The MSC server is connected to the pure signaling point NEs, such as the HLR, SCP, and
SMC in STP forward mode. The MSC server is connected to the STP directly and the
signaling is based on IP.
Direct speech channels are configured between all MGWs and the GMSC (or TMSC).
Signaling and speech channels between them are based on IP. The MSC Pool interworks
with external networks through the GMSC. The MSC Pool interworks with local MSCs or
remote MSCs in the network through the TMSC.
For details on the networking solutions, see the section "3.3 General Principles of the MSC
Pool Planning."
The function description of a new target network is as follows:
l
The Iu-Flex function is enabled on the RNC.
Usage Description of Signaling Point Codes

Use the standard M3UA forwarding networking mode.
The principles of the signaling point code (SPC) planning are as follows:
l
MSC server 1 uses two SPCs: AA (for national network) and DD (for national reserved
network).
MSC server 2 uses two SPCs: BB (for international network) and EE (for international
reserved network).
MSC server 3 uses two SPCs: CC (for national network) and FF (for national reserved
network).
MGW 1 uses one SPC: GG.
MGW 2 uses one SPC: HH.
MGW 3 uses one SPC: JJ.
The RNC retains the existing SPCs.
Issue 02 (2008-04-10)

7-3


AA
BB
SX 1
CC
SX 2
DD
SX 3
EE
GG
MGW
2
MGW
1
RNC
1
RNC
2
FF
HH
MGW
3
JJ
RNC
4
RNC
3
For detailed data planning, see Table 7-1, Table 7-2, and Table 7-3.

Figure 7-3 shows the overall data configuration process for an MSC Pool.
Figure 7-3 Overall data configuration process for an MSC Pool
Start
Preparation
Evolution of
the Core
Network

Pool
Access of the
Access Network

Configuring
service
data

End
7-4

Issue 02 (2008-04-10)

The data configuration for an MSC Pool is classified into data planning, evolution of the core
network (CN), access of the access network, and configuration of service data. The detailed
configuration procedures are described in the following sections.
7.3 Data Planning

The following tables list the data planning for an MSC Pool network.
Table 7-1 Data planning for MSC servers in an MSC Pool network
Issue 02 (2008-04-10)
Name
MSC Server 1
MSC Server 2
MSC Server 3
Node
name
SX1
SX2
SX3
SPC
National network:
A80001
National network:
A80002
National network:
A80003
National reserved
network: 801
National reserved
network: 802
National reserved
network: 803
IP
Addres
s
192.168.153.1
192.168.155.2
192.168.151.3
Length
of the
NRI
(bits)
6 (recommended)
6 (recommended)
6 (recommended)
Value
of the
NRI
1 (recommended)
2 (recommended)
3 (recommended)
Default
MSC
You are advised to set all MSC servers in the MSC Pool to default MSCs.
Chargin
g mode
Capacit
y of an
MSC
server
in the
MSC
Pool
1 million (recommended)
Value
of Null
NRI
10 (recommended)
10 (recommended)
10 (recommended)
CN ID
1 (recommended)
2 (recommended)
3 (recommended)

7-5

7-6
Name
MSC Server 1
MSC Server 2
MSC Server 3
Nonbroadca
st LAI
460004444
460005555
460006666
Data of
H.248
links
betwee
n the
MSC
server
and the
MGW
MGW1:
MGW1:
MGW1:
SLOCIP1="192.168.153
.1"
SLOCIP1="192.168.155
.2"
SLOCIP1="
192.168.151.3"
SLOCPORT=5000
SLOCPORT=5100
SLOCPORT=3300
SRMTIP1="192.168.167
.21"
SRMTIP1="192.168.167
.21"
SRMTIP1="192.168.167
.21"
SRMTPORT=5000
SRMTPORT=5100
SRMTPORT=3300
MGW2:
MGW2:
MGW2:
SLOCIP1="192.168.153
.1"
SLOCIP1="192.168.155
.2"
SLOCIP1="
192.168.151.3"
SLOCPORT=2300
SLOCPORT=5200
SLOCPORT=3400
SRMTIP1="192.168.172
.41"
SRMTIP1="192.168.172
.41"
SRMTIP1="192.168.172
.41"
SRMTPORT=2300
SRMTPORT=5200
SRMTPORT=3400
MGW3:
MGW3:
MGW3:
SLOCIP1="192.168.153
.1"
SLOCIP1="192.168.155
.2"
SLOCIP1="
192.168.151.3"
SLOCPORT=2203
SLOCPORT=5300
SLOCPORT=4600
SRMTIP1="192.168.175
.42"
SRMTIP1="192.168.175
.42"
SRMTIP1="192.168.175
.42"
SRMTPORT=2203
SRMTPORT=5300
SRMTPORT=4600

Issue 02 (2008-04-10)

Name
MSC Server 1
MSC Server 2
MSC Server 3
Data of
M3UA
links
betwee
n the
MSC
server
and the
MGW
MGW1:
MGW1:
MGW1:
LOCIP1="192.168.153.1
"
SLOCIP1="192.168.155
.2"
SLOCIP1="
192.168.151.3"
LOCPORT=6001
SLOCPORT=4100
SLOCPORT=3500
PEERIP1="192.168.167.
21"
PEERIP1="192.168.167.
21"
PEERIP1="192.168.167.
21"
PEERPORT=6001
PEERPORT=4100
PEERPORT=3500
MGW2:
MGW2:
MGW2:
LOCIP1="192.168.153.1
"
LOCIP1="192.168.155.2
"
LOCIP1="
192.168.151.3"
LOCPORT=2302
LOCPORT=4200
LOCPORT=3600
PEERIP1="192.168.172.
41"
PEERIP1="192.168.172.
41"
PEERIP1="192.168.172.
41"
PEERPORT=2302
PEERPORT=4200
PEERPORT=3600
MGW3:
MGW3:
MGW3:
LOCIP1="192.168.153.1
"
LOCIP1="192.168.155.2
"
LOCIP1="
192.168.151.3"
LOCPORT=2204
LOCPORT=4300
LOCPORT=4700
PEERIP1="192.168.175.
42"
PEERIP1="192.168.175.
42"
PEERIP1="192.168.175.
42"
PEERPORT=2204
PEERPORT=4300
PEERPORT=4700
Table 7-2 Data planning for MGWs in an MSC Pool network
Issue 02 (2008-04-10)
Name
MGW1
MGW2
MGW3
Node name
MGW1
MGW2
MGW3
SPC
901
902
903
IP address (the
MGW adopts the
centralized
forwarding mode
for IP addresses)
192.168.167.21
192.168.172.41
192.168.175.42
Mapping between
the VMGW IDs and
the MSC servers
SX1:
SX1:
SX1:
VMGWID=0
VMGWID=1
VMGWID=1
SX2:
SX2:
SX2:
VMGWID=1
VMGWID=0
VMGWID=2
SX3:
SX3:
SX3:
VMGWID=2
VMGWID=2
VMGWID=0

7-7

Table 7-3 Data planning for RNCs in an MSC Pool network

Name
RNC1
RNC2
RNC3
RNC4
RNC ID
RNC1
RNC2
RNC3
RNC4
SPC
10B
A61
B04
B05
LAI
460000011
460000012
460000060
460000070
SAI
4600000110012
4600000120012
4600000600060
4600000600070

7.4.4 Adding BSCs to the MSC Pool Area
network.

The procedures for configuring the basic data of NEs in an MSC Pool are the same as that for
configuring NEs in a network without an MSC Pool. For details, see the relevant data
configuration in the HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide.


For details, see the section "Configuring Data on the MSC Server" in the "New MSC Pool in
the 2G Network" chapter.

To preset the data on the MGWs, set the MGWs on the M2000.
Description
7-8
Connect the MGWs to the O&M system of the M2000. Thus, you can
maintain the MGWs in a centralized manner on the M2000.
Issue 02 (2008-04-10)

Script
Remark
The data configuration is performed on the M2000. For details, refer to the
online Help of the M2000.
Replacing TMSIs
Start the TMSI reallocation process in the case that the TMSI reallocation function is enabled
on the MSC server. Then, wait for the time required by two periodical location updates (the
interval of location updates can be set on the RNC) for the replacing of TMSIs to be completed.
(You are advised to set the start time of the TMSI replacing to a time when there are a significant
number of online subscribers). To replace a TMSI is to add the corresponding NRI to the TMSI.
This enables the subscribers to be still homed to the original MSC server after the 3G network
evolves into an MSC Pool. The purpose of the operation is to keep the target network as similar
to the existing network as possible. As a result, the impact of the network evolution on the
network operation is minimized.
To allow automatic replacement of TMSIs, you only need to enable the TMSI re-allocation
function by running the SET MAPACCFG command at appropriate time.
Ending the Presetting

After two periodical location updates, randomly select 10 subscribers and check whether their
TMSIs are replaced. If nine or more TMSIs are replaced, you can proceed with subsequent steps.
Otherwise, wait until more TMSIs are replaced.

Configuring the Data of MSC server 1

To configure the data of the Mc interface over M3UA links between the MSC server and the
MGW, perform the following steps:
1.
On MSC server 1, add MGW1/MGW2/MGW3 and configure the H.248 links from MGW1/
MGW2/MGW to MSC server 1.
and MGW 1.
Descriptio
n
Issue 02 (2008-04-10)


7-9

Script

BCUID=1,
G-1, ENCT=NSUP,
740-1&RATE795-1,
740-1&RATE795-1&RATE102-1&RATE122-1,
TE740-1&RATE795-1&RATE102-1&RATE122-1,
A-1&GSMFR-1;
SLOCPORT=5000, SRMTIP1="192.168.167.21",
and MGW 2.
7-10
Descriptio
n

Script

BCUID=1,
G-1, ENCT=NSUP,
740-1&RATE795-1,
740-1&RATE795-1&RATE102-1&RATE122-1,
TE740-1&RATE795-1&RATE102-1&RATE122-1,
A-1&GSMFR-1;
SLOCPORT=2300, SRMTIP1="192.168.172.41",

Issue 02 (2008-04-10)

and MGW 3.
2.
Descriptio
n

Script

BCUID=1,
SPCATTR=SDPHEX-1&NOBNC-1&NOEC-1&NOJTTR-1&NOFAX-1&NOM
ODEM-1&LOCSDPP-1&SUPH248V2-1&NOVERNEG-0&SUPCODECCFG1, ENCT=NSUP,
CPB=TONE-1&PA-1&SENDDTMF-1&DETECTDTMF-1&MPTY-1&IWF-1
, ECRATE=300, IWFRATE=300, TONERATE=300,
40-1&RATE795-1,
UMTSAMR2R=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RA
TE740-1&RATE795-1&RATE102-1&RATE122-1,
40-1&RATE795-1&RATE102-1&RATE122-1,
UMTSAMRR=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RAT
E740-1&RATE795-1&RATE102-1&RATE122-1,
MODEMLST=GSMMT-1&GSMV21-1&GSMV22-1&GSMV22BIS-1&GSMV2
TC=GSMEFR-1&GSMHR-1&TDMAEFR-1&PDCEFR-1&HRAMR-1&UMTSA
MR2-1&FRAMR-1&PCMA-1&PCMU-1&UMTSAMR-1&G7231-1&G729A1&GSMFR-1;
SLOCPORT=2203, SRMTIP1="192.168.175.42",
On MSC server 1, add the data of M3UA configuration from MSC server 1 to MGW1/
MGW2/MGW3.
1.
Descriptio
n

server 1 to MGW 1.
Script
ADD M3LE: LENM="SX1_NATB", NI=NATB, OPC="801",

LET=AS;
ADD M3DE: DENM="TO_MGW1_NATB", NI=NATB, DPC="901",
STPF=TRUE, DET=SG;
LOCIP1="192.168.153.1", LOCPORT=6001,
2.
Issue 02 (2008-04-10)

7-11

Descriptio
n

server 1 to MGW 2.
Script

STPF=TRUE, DET=SG;
LOCIP1="192.168.153.1", LOCPORT=2302,
3.
Descriptio
n

server 1 to MGW 3.
Script

STPF=TRUE, DET=SG;
LOCIP1="192.168.153.1", LOCPORT=2204,
----End

configuring the data of MSC server 1 described in Configuring the Data of MSC server 1.

configuring the data of MSC server 1 described in Configuring the Data of MSC server 1.
Configuring the Data of MGW 1

To configure the data of MGW 1, perform the following steps:
1.
7-12
Configure the local office SPC based on the general planning of the MSC Pool.
Description
Configure the local office SPC of MGW 1.
Script

NATVLD= NO, NATRESVLD=YES, NATRESOPC="H'901",
NATRESLEN=LABEL14, SPFLAG=NO, STPFLAG=YES,
RESTARTFLAG=NO;

Issue 02 (2008-04-10)

2.
Configure the Mc interface and the M3UA data between MGW 1 and MSC server1/ MSC
server2/ MSC server3.
(1) On MGW 1, add a virtual MGW and the data of H.248 links and M3UA configuration
from MGW 1 to MSC server 1.
Descriptio
n
On MGW 1, add virtual MGWs and the data of H.248 links and
M3UA configuration from MGW 1 to MSC server 1.
Script

ADD H248LNK: LINKID=48, VMGWID=0, MGCIDX=0,
TT=SCTP, LOCALIP="192.168.167.21", LOCALPORT=5000,
BP=BACK;
OPC="901";
LIP1="192.168.167.21", LP=5000,
RIP1="192.168.153.1", RP=5000, LSX=0, ASF=ACTIVE;
(2) On MGW 1, add virtual MGWs and the data of H.248 links and M3UA configuration
Descriptio
n
Issue 02 (2008-04-10)

7-13

Script

BP=BACK;
ADD M3LKS: LSX=0, LSN="SX2", ADX=0;ADD M3RT:
RN="SX2", DEX=0, LSX=0;
LIP1="192.168.167.21", LP=4100,
(3) On MGW 1, add virtual MGWs and the data of H.248 links and M3UA configuration
Descriptio
n
Script

BP=BACK;
LIP1="192.168.167.21", LP=3500,
----End
7-14

Issue 02 (2008-04-10)


the data of MGW 1 described in Configuring the Data of MGW 1.

the data of MGW 1 described in Configuring the Data of MGW 1.
7.4.4 Adding BSCs to the MSC Pool Area

network.

To configure the data of MSC server 1, perform the following steps:
1.
Add RNC 1 on MSC server 1.

(1) Set RNC 1 as an M3UA destination entity of MSC server 1.
Descriptio
n
Set RNC 1 as an M3UA destination entity of MSC server 1.
Script
ADD M3DE: DENM="RNC1", LENM="SX1_NATB", NI=NATB,

DPC="10B", DET=SP;
(2) Add an office direction for RNC 1.

Descriptio
n
Add an office direction for RNC 1.
Script
ADD OFC: ON="RNC1", OFFICT=RNC, DOL=LOW, DOA=RNC,

BOFCNO=1, OFCTYPE=COM, SIG=NONBICC/NONSIP, NI=NATB,
(3) Add access MGWs for RNC 1.

Descriptio
n
Add access MGWs for RNC 1.
Script
ADD RANMGW: OFFICENAME="RNC1", MGWNAME="MGW1";

(4) Add M3UA routes to RNC 1.

Descriptio
n
Issue 02 (2008-04-10)
Add M3UA routes to RNC 1.

7-15

Script
ADD M3RT: RTNM="RNC1", DENM="RNC1", LSNM="MGW1";

(5) Add an SCCP DSP for RNC 1.

Descriptio
n
Add an SCCP DSP for RNC 1.
Script
ADD SCCPDSP: DPNM="RNC1", NI=NATB, DPC="10B",

OPC="801";
(6) Add RNC 1 on MSC server 1.

Descriptio
n
Script
ADD RNC: RNCID=1, NI=NATB, OPC="801", DPC="10B",

RNCNM="RNC1",
CAPABILITY=IUFLEX-1&MGWPROXYIUFLEX-1&PRIVATEMSG-1,
MLAIF=YES;
(7) On MSC server 1, configure RNC 1 to support the Iu-Flex function.

Descriptio
n
On MSC server 1, configure RNC 1 to support the Iu-Flex function.
Script
MOD RNC: RNCID=1, CAPABILITY=IUFLEX-1, MLAIF=NO;
(8) Add an SCCP subsystem.
2.
Desc
ripti
on
Add an SCCP subsystem
Scrip
t
ADD SCCPSSN: SSNNM="RNC1_SCMG", NI=NATB, SSN=SCMG,

SPC="10B", OPC="801";
ADD SCCPSSN: SSNNM="RNC1_RANAP", NI=NATB, SSN=RANAP,
SPC="10B", OPC="801";
On MSC server 1, configure the paging data of the location areas controlled by RNC 1.
Description
On MSC server 1, configure the paging data of the location areas

controlled by RNC 1.
Script
----End
The procedure for adding RNC 2, RNC 3, and RNC 4 on MSC server 1 is similar to the procedure
for adding RNC 1 on MSC server 1.
7-16

Issue 02 (2008-04-10)


configuring the data of MSC server 1 described in "Configuring the Data of MSC server 1."

configuring the data of MSC server 1 described in "Configuring the Data of MSC server 1."

To configure the data of MGW 1, perform the following steps:
1.
2.
Activate all virtual MGWs.

Description
On MGW 1, activate all virtual MGWs.
Script
ACT VMGW: VMGWID=0;

ACT VMGW: VMGWID=1;
ACT VMGW: VMGWID=2;
Configure the data of signaling and speech channels from MGW 1 to RNC1, RNC2, RNC3,
and RNC4. For details, refer to the UMG8900 Configuration Example.
----End

the data of MGW 1 described in "Configuring the Data of MGW 1."

the data of MGW 1 described in "Configuring the Data of MGW 1."
Configuring the Data of the RNC

To configure the data of the RNC, perform the following steps:
1.
Enable the Iu-Flex function.
2.
Configure the length of the NRI and the value of the Null-NRI.
3.
Add the relevant CN nodes and set the relevant parameters, including the CN carrier index,
the CN-Id, the CN node, the Off-load status, and the CN node capacity.
4.
Add the mappings between the relevant CN nodes and the NRIs.
5.
Configure the data of the signaling and speech channels following the path of RNC > MGW
> MSC server.
----End
NOTE
The data configuration on the RNC varies according to the RNC supplier. For details on the commands,
refer to relevant data configuration manuals of the RNC.
Issue 02 (2008-04-10)

7-17


This section describes the configuration of other data in the scenario of new MSC Pool in 3G
network.
The procedure for configuring other data in this scenario is the same as the procedure for
configuring other data in the scenario of new MSC Pool in 2G Network. For details, see the
related description in 5.5 Other Data Configuration in the "New MSC Pool in 2G Network"
chapter.

This section describes the system commissioning of a new 3G network in MSC Pool mode.
Only the new and changed commissioning introduced by the MSC Pool feature is described in
this section. Other commissioning must be performed based on the basic procedures. The
commissioning can be performed during the evolution of the core network and access of the
access network. The following sections provide a commissioning example. You can make
adjustments according to the actual requirements.
Preparations
Make the following preparations:
1.
On the M2000, set the load balancing algorithm parameter for all the RNCs.
2.
On the RNC to be commissioned, set all CN nodes in Inhibited state to Offload state based
on the commissioning plan. As shown in Table 7-4, the CN nodes MSC server 1, MSC
server 2, and MSC server 3 corresponding to RNC 1 must be changed from Normal/
Inhibited/Inhibited to Normal/Offload/Offload if RNC 1 and the CN nodes are to be
commissioned.
Table 7-4 Changing status of MSC servers
3.
7-18
NE
MSC server 1
(Current/
Commissioning)
MSC server 2
(Current/
Commissioning)
MSC server 3
(Current/
Commissioning)
RNC 1
Normal/Normal
Inhibited/Offload
Inhibited/Offload
RNC 2
Inhibited/Offload
Normal/Normal
Inhibited/Offload
RNC 3
Inhibited/Offload
Inhibited/Offload
Normal/Normal
RNC 4
Inhibited/Offload
Inhibited/Offload
Normal/Normal

Description
Script

Issue 02 (2008-04-10)

4.
On the M2000, check whether the status of the signaling links is normal.
5.

(1) Connect a commissioning subscriber to RNC 1 and MSC server 1.
(2) Check whether the voice channels are properly set up and the quality of the voice.
(3) Go through substeps 2 to 3 repeatedly for all voice channels that the subscriber may
use.
(4) Connect a commissioning subscriber to RNC 2/RNC 3/RNC 4. Repeat substeps 1 to
4 until the function is tested for all the RNCs in the MSC Pool area.
----End

1.
Connect a subscriber to RNC 1 and MSC server 1.
2.
to MSC server 2.
3.
4.
Connect a commissioning subscriber to RNC 2/RNC 3/RNC 4. Repeat steps 1 to 3 until

the function is tested for all RNCs in the MSC Pool area.

1.
2.
3.
Connect a commissioning subscriber to RNC2/RNC3/RNC4. Repeat steps 1 to 2 until the

function is tested for all RNCs in the MSC Pool area.

1.
configured data.
2.
3.
4.
Connect a commissioning subscriber to RNC2/RNC3/RNC4. Repeat steps 2 to 3 until the

function is tested for all RNCs in the MSC Pool area.
Issue 02 (2008-04-10)

7-19

Trial Run
1.
On the MGW, set the status of all MSC servers to Normal.
2.
3.
4.
subscriber redistribution function of the M2000.
This step is optional.
----End
NOTE
7-20

Issue 02 (2008-04-10)

3G Network Evolution to Support MSC Pool
About This Chapter

This section describes the data planning and data configuration process of a 3G network evolving
This section describes the overall data configuration flow, data planning, and MSC Pool
presetting of a 3G network evolving to an MSC Pool network.
This section describes the evolution of the core network of a 3G network evolving to an MSC
Pool network.
8.4 Access of the Access Network
This section describes the access of the access network of a 3G network evolving to an MSC
Pool network.
This section describes other data configuration of a 3G network evolving to an MSC Pool
network.
Issue 02 (2008-04-10)

8-1


Evolution of an existing 3G network into an MSC Pool is a way in which the MSC Pool solution
is applied. A typical 3G network has the following characteristics:
l
The core network adopts the softswitch networking structure, which consists of MCS
servers and MGWs.
The access network adopts the radio access network (RAN) system. The RNC supports the
Iu-Flex function and has the load distribution capability.
This section describes how a typical existing 3G network evolves into an MSC Pool.
This section describes the existing network.
8.1.2 Description of Target Network
This section describes the target network.

This section describes the existing network.
Figure 8-1 shows the networking diagram of a typical existing 3G network.
Figure 8-1 Networking diagram of a typical existing 3G network
SX 1
SX 2
HLR/SCP/SMSC
SX 3
STP
MGW2
MGW1
MGW3
GMSC (TMSC)
RNC1
RNC2
IP bearer
RNC3
RNC4
TDM bearer
VPLMN or other
MSCs in the HPLMN
ATM bearer
This chapter describes how an existing 3G network evolves into an MSC Pool by taking the
network shown in Figure 8-1 as an example.
8-2

Issue 02 (2008-04-10)

The networking of the existing network is as follows:
l
The Mc interface is based on the IP bearer. The Iu-interface signaling is forwarded by the
MGW (as the SG) through M3UA links.
The Iu-interface signaling and voice channels between the MGW and RNC are based on
the ATM bearer.
The Nb interface between MGWs is based on the TDM bearer. Not all MGWs are directly
connected.
Based on the TDM bearer, the signaling and voice channels of the MGW are directly
connected to the GMSC (TMSC) in the outgoing direction.
Based on IP bearer, the signaling of the MSC server is transferred through the STP and
then is routed to the HLR/SCP/SMSC.
The function of the existing network is as follows:
l
None of the NEs has the Iu-Flex function enabled.
The virtual MGW function is not enabled on the MGW.

The signaling point codes (SPCs) are used as follows:
l
network).
network).
MSC server 3 uses two SPCs (CC for national network and FF for national reserved
network).
Each MGW uses an SPC.
Each RNC uses an SPC.
8.1.2 Description of Target Network

This section describes the target network.
Figure 8-2 shows the networking diagram of a target network which has adopted the MSC Pool
solution and has evolved from an existing 3G network.
Issue 02 (2008-04-10)

8-3

Figure 8-2 Networking diagram of a target network

SX 1
SX 3
SX 2
SX 4
HLR/SCP/SMSC
STP
MGW2
MGW1
MGW3
GMSC (TMSC)
RNC1
RNC2
IP bearer
RNC3
RNC4
TDM bearer
VPLMN or other
MSCs in the HPLMN
ATM bearer
As shown in Figure 8-2, the MGWs are fully connected. The signaling channels between the
MGWs and the STP, and the voice channels between the MGWs and the GMSC (TMSC) are
based on the IP bearer. The following describes the networking of the target network in further
details.
The networking of the target network is as follows:
8-4
The MSC servers in the MSC Pool are fully connected. The links between them are based
on the IP bearer. The MSC servers communicate using the BICC signaling. The Nc interface
between the MSC servers adopts the protocol stack BICC/M3UA/SCTP/IP.
The Mc interface is based on the IP bearer. It adopts the protocol stack H.248/SCTP/IP.
The Iu-interface signaling and voice channels between the MGW and RNC are based on
the ATM bearer. The Iu interface adopts the protocol stack RANAP/SCCP/MTP3b/SAAL/
ATM.
The control plane signaling transmitted over the Iu interface is forwarded by the built-in
SG of the MGW. The build-in SG of the MGW communicates with the MSC server over
the IP bearer. It adopts the protocol stack RANAP/SCCP/M3UA/SCTP/IP.
The Nb interface between MGWs is based on the IP bearer. The MGWs are fully connected.
Based on IP bearer, the signaling from the MSC servers is transferred through the STP and
then is routed to the HLR/SCP/SMC.
Direct voice channels are established between each MGW in the MSC Pool and the GMSC
(TMSC). The signaling and voice channels between the MGWs and the GMSC (TMSC)
are based on the IP bearer. When the NEs in the MSC Pool are connected to the GMSC
through the MGWs, they can communicate with the external network; when they are
connected to the TMSC through the MGWs, they can communicate with the other local
MSCs or toll MSCs in the local network.
Issue 02 (2008-04-10)

For details about the networking principles, see 3.3 General Principles of the MSC Pool
Planning.
The function of the target network is as follows:
l
The Iu-Flex function is enabled on the RNCs.
The virtual MGW function is enabled on the MGWs.

The standard M3UA forwarding networking mode is adopted.
The SPCs are used as follows:
l
network).
network).
MSC server 3 uses two SPCs (CC for national network and FF for national reserved
network).
MGW 1 uses an SPC (GG).
MGW 2 uses an SPC (HH).
MGW 3 uses an SPC (JJ).
The SPC of the RNC does not change.
For details of the data planning, see Table 8-1,Table 8-2, Table 8-3. Figure 8-3shows the SPCs
used in the target network.
BB
AA
SX 1
SX 2
DD
EE
GG
MGW
2
MGW
1
RNC
1
RNC
2
CC
SX 3
FF
HH
MGW
3
RNC
3
JJ
RNC
4

This section describes the overall data configuration flow, data planning, and MSC Pool
presetting of a 3G network evolving to an MSC Pool network.
Issue 02 (2008-04-10)

8-5

Figure 8-4 shows the basic data configuration flow of the MSC Pool.
Figure 8-4 Basic data configuration flow of the MSC Pool
Start
Preparation
Evolution of
the Core
Network

Pool
Access of the
Access Network

Configuring
service
data

End
As shown in Figure 8-4, the basic data configuration of the MSC Pool is classified into data
planning, evolution of the core network (CN), access of the access network, and configuration
of service data. The detailed configuration steps are described in the following sections.
8.2.1 Data Planning
This section describes the data planning of the MSC Pool.
8.2.1 Data Planning

This section describes the data planning of the MSC Pool.
Table 8-1 lists the data planning of the MSC servers in an MSC Pool network.
Table 8-1 Data planning of the MSC servers in an MSC Pool network
8-6
Name
MSC Server 1
MSC Server 2
MSC Server 3
Node name
SX1
SX2
SX3
SPC
National network:
A80001
National network:
A80002
National network:
A80003

Issue 02 (2008-04-10)

Name
Issue 02 (2008-04-10)
MSC Server 1
MSC Server 2
MSC Server 3
National reserved
network: 801
National reserved
network: 802
National reserved
network: 803
IP address
192.168.153.1
192.168.155.2
192.168.151.3
Length of
the NRI
(bits)
6 (recommended)
6 (recommended)
6 (recommended)
Value of
the NRI
1 (recommended)
2 (recommended)
4 (recommended)
Default
MSC
You are advised to set all MSC servers in the MSC Pool to default MSC.
Charging
mode
Capacity of
the MSC
server in
the MSC
Pool
1 million
Value of
Null NRI
10 (recommended
value)
10 (recommended
value)
10 (recommended
value)
CN ID
1 (recommended value)
Nonbroadcast
LAI
460004444
460005555
460006666

8-7
8-8

Name
MSC Server 1
MSC Server 2
MSC Server 3
Data of H.
248 links
between
the MSC
server and
MGW
MGW1:
MGW1:
MGW1:
SLOCIP1="192.168.15
3.1"
SLOCIP1="192.168.15
5.2"
SLOCIP1="
192.168.151.3"
SLOCPORT=5000
SLOCPORT=5100
SLOCPORT=3300
SRMTIP1="192.168.16
7.21"
SRMTIP1="192.168.16
7.21"
SRMTIP1="192.168.16
7.21"
SRMTPORT=5000
SRMTPORT=5100
SRMTPORT=3300
MGW2:
MGW2:
MGW2:
SLOCIP1="192.168.15
3.1"
SLOCIP1="192.168.15
5.2"
SLOCIP1="
192.168.151.3"
SLOCPORT=2300
SLOCPORT=5200
SLOCPORT=3400
SRMTIP1="192.168.17
2.41"
SRMTIP1="192.168.17
2.41"
SRMTIP1="192.168.17
2.41"
SRMTPORT=2300
SRMTPORT=5200
SRMTPORT=3400
MGW3:
MGW3:
MGW3:
SLOCIP1="192.168.15
3.1"
SLOCIP1="192.168.15
5.2"
SLOCIP1="
192.168.151.3"
SLOCPORT=2203
SLOCPORT=5300
SLOCPORT=4600
SRMTIP1="192.168.17
5.42"
SRMTIP1="192.168.17
5.42"
SRMTIP1="192.168.17
5.42"
SRMTPORT=2203
SRMTPORT=5300
SRMTPORT=4600

Issue 02 (2008-04-10)

Name
MSC Server 1
MSC Server 2
MSC Server 3
Data of
M3UA
Links
between
the MSC
server and
MGW
MGW1:
MGW1:
MGW1:
LOCIP1="192.168.153.
1"
SLOCIP1="192.168.15
5.2"
SLOCIP1="
192.168.151.3"
LOCPORT=6001
SLOCPORT=4100
SLOCPORT=3500
PEERIP1="192.168.16
7.21"
PEERIP1="192.168.16
7.21"
PEERIP1="192.168.16
7.21"
PEERPORT=6001
PEERPORT=4100
PEERPORT=3500
MGW2:
MGW2:
MGW2:
LOCIP1="192.168.153.
1"
LOCIP1="192.168.155.
2"
LOCIP1="
192.168.151.3"
LOCPORT=2302
LOCPORT=4200
LOCPORT=3600
PEERIP1="192.168.17
2.41"
PEERIP1="192.168.17
2.41"
PEERIP1="192.168.17
2.41"
PEERPORT=2302
PEERPORT=4200
PEERPORT=3600
MGW3:
MGW3:
MGW3:
LOCIP1="192.168.153.
1"
LOCIP1="192.168.155.
2"
LOCIP1="
192.168.151.3"
LOCPORT=2204
LOCPORT=4300
LOCPORT=4700
PEERIP1="192.168.17
5.42"
PEERIP1="192.168.17
5.42"
PEERIP1="192.168.17
5.42"
PEERPORT=2204
PEERPORT=4300
PEERPORT=4700
Table 8-2 lists the data planning of the MGWs in an MSC Pool network.
Table 8-2 Data planning of the MGWs in an MSC Pool network
Issue 02 (2008-04-10)
Name
MGW 1
MGW 2
MGW 3
Node name
MGW1
MGW2
MGW3
SPC
901
902
903
IP address (the
MGW adopts the
centralized
forwarding mode
for IP addresses)
192.168.167.21
192.168.172.41
192.168.175.42

8-9

Name
MGW 1
MGW 2
MGW 3
Mapping between
the VMGWIDs and
the MSC servers
SX1:
SX1:
SX1:
VMGWID=0
VMGWID=1
VMGWID=1
SX2:
SX2:
SX2:
VMGWID=1
VMGWID=0
VMGWID=2
SX3:
SX3:
SX3:
VMGWID=2
VMGWID=2
VMGWID=0
Table 8-3 lists the data planning of the RNCs in an MSC Pool network.
Table 8-3 Data planning of the RNCs in an MSC Pool network
Name
RNC 1
RNC 2
RNC 3
RNC 4
RNC ID
RNC1
RNC2
RNC3
RNC4
SPC
10B
A61
B04
B05
LAI
460000011
460000012
460000060
460000070
SAI
4600000110012
4600000120012
4600000600060
4600000600070

For details, see the section 7.4.2 Presetting Data for the MSC Pool in the "New MSC Pool in
the 3G Network" chapter.

This section describes the evolution of the core network of a 3G network evolving to an MSC
Pool network.
8.3.1 Overview
This section describes the evolution process of the core network.
8.3.2 Adding MSC Server 2 to the MSC Pool
This section describes the data configuration in the evolution process of the core network.
8.3.3 Adding MGW 2 to the MSC Pool
8-10

Issue 02 (2008-04-10)

8.3.1 Overview
This section describes the evolution process of the core network.
The evolution process consists of:
l
Evolution of the core network
Access of the access network
System commissioning
You can perform the evolution of the core network, and then connect the NEs to the MSC Pool
one by one. After the evolution of the core network is completed, you can perform the system
commissioning on the CN side (optional). You must perform the commissioning of the whole
MSC Pool system after each NE of the access network is connected to the MSC Pool. This
manual describes only the commissioning tasks specific to the MSC Pool solution. The common
commissioning tasks, such as the commissioning that is performed after an NE is added, are not
described.
The process of evolution into an MSC Pool for an existing 3G core network is similar to that for
an existing 2G core network. The difference is that the data of M3UA links between MSC server
1 and MGW 1 in the existing 3G network is already configured. (The data of M3UA links
between MSC server 2 and MGW 2, and that between MSC server 3 and MGW 3 is also
configured.) Therefore, for the evolution of the existing 3G network, the relevant configuration
is not required anymore.
Now that the data of the M3UA links between MSC server 1 and MGW 1 in the existing 3G
network is configured, MSC server 1 and MGW 1 can be considered as an MSC Pool. Thus, the
evolution of the core network starts from the adding of MSC server 2 to the MSC Pool.
The following two solutions are available for the evolution:
l
Solution 1:
1.
Use SX1, SX2, MGW 1, and MGW 2 to form a simplest MSC Pool.
2.
Add RNC 1 and RNC 2 to the MSC Pool.
3.
Add SX3, MGW 3, RNC 3, and RNC 4 to the MSC Pool.
Solution 2:
1.
Evolve the entire core network into the MSC Pool.
2.
Add RNC 1, RNC 2, RNC 3, and RNC 4 into the MSC Pool.
This document describes the evolution of the network by taking solution 2 as an example.

Issue 02 (2008-04-10)

8-11


SX1
SX2
SX3
unavailable
MGW
1
RNC
1
MGW
2
MGW
3
RNC
2
H248 link
RNC
3
RNC
4
M3UA link

Configure related data of the newly added H.248 links and M3UA links on MGW 1 and MSC
server 2.

1.
Add MGW 1 on MSC server 2 and an H.248 link between MGW 1 and MSC server 2.
Description
8-12
Add MGW 1 on MSC server 2 and an H.248 link between MGW 1 and
MSC server 2.

Issue 02 (2008-04-10)

Script
2.

ENCT=NSUP,
-1&RATE795-1,
740-1&RATE795-1&RATE102-1&RATE122-1,
-1&RATE795-1&RATE102-1&RATE122-1,
40-1&RATE795-1&RATE102-1&RATE122-1,
MFR-1;
SLOCPORT=5100, SRMTIP1="192.168.167.21",
1.
Description

Script

STPF=TRUE, DET=SG;
WM=ASP;
LOCIP1="192.168.155.2", LOCPORT=4100,
----End

1.
server 2.
Description
Issue 02 (2008-04-10)

8-13
Script
2.


BP=BACK;
Add an M3UA destination signaling point for interworking with MSC server 2 and related
M3UA configuration.
Description

server 2 and related M3UA configuration.
Script

LIP1="192.168.167.21", LP=4100, RIP1="192.168.155.2",
----End
NOTE
The current data is newly added data. If you need to roll back the data configuration, delete the added data.

l
The services pass the dialing test.
In the entire system, at least one periodic location update is completed normally.

8-14

Issue 02 (2008-04-10)


SX1
SX3
SX2
unavailable
MGW
1
RNC
1
MGW
2
MGW
3
RNC
2
H248 link
RNC
3
RNC
4
M3UA link

server 1.

To configure data on the MSC server, perform the following steps:
1.
Add MGW 2 on MSC server 1 and an H.248 link between MGW 2 and MSC server 1.
Description
Issue 02 (2008-04-10)
MSC server 1.

8-15
Script
2.


ENCT=NSUP,
-1&RATE795-1,
740-1&RATE795-1&RATE102-1&RATE122-1,
-1&RATE795-1&RATE102-1&RATE122-1,
40-1&RATE795-1&RATE102-1&RATE122-1,
MFR-1;
SLOCPORT=2300, SRMTIP1="192.168.172.41",
2.
Description

Script

STPF=TRUE, DET=SG;
WM=ASP;
LOCIP1="192.168.153.1", LOCPORT=2302,
----End

1.
server 1.
Description
8-16

Issue 02 (2008-04-10)

Script
2.

BP=BACK;
Add the configuration of the SIGTRAN on MGW 2 for interworking with MSC server 1
where Network Type is MSC Pool.
Description

with MSC server 1 where Network Type is MSC Pool.
Script

LIP1="192.168.172.41", LP=2302, RIP1="192.168.153.1",
----End
NOTE

l

Issue 02 (2008-04-10)

8-17


SX1
SX2
unavailable
unavailable
MGW
1
RNC
1
SX3
MGW
2
MGW
3
RNC
2
H248 link
RNC
3
RNC
4
M3UA link

Configure related data of the newly added H.248 link and M3UA link on MGW 1, MGW 2, and
MSC server 3.

1.
Add MGW 1 and MGW 2 on MSC server 3 and H.248 links between MSC server 3 and
MGW 1, and between MSC server 3 and MGW 2.
Description
8-18
MSC server 3.

Issue 02 (2008-04-10)

2.
Issue 02 (2008-04-10)
Script

ENCT=NSUP,
-1&RATE795-1,
740-1&RATE795-1&RATE102-1&RATE122-1,
-1&RATE795-1&RATE102-1&RATE122-1,
40-1&RATE795-1&RATE102-1&RATE122-1,
MFR-1;
SLOCPORT=3300, SRMTIP1="192.168.167.21",
Description
MSC server 3.
Script

ENCT=NSUP,
-1&RATE795-1,
740-1&RATE795-1&RATE102-1&RATE122-1,
-1&RATE795-1&RATE102-1&RATE122-1,
40-1&RATE795-1&RATE102-1&RATE122-1,
MFR-1;
SLOCPORT=3400, SRMTIP1="192.168.172.41",
1 and MGW 2.
8-19

Description

Script

STPF=TRUE, DET=SG;
WM=ASP;
LOCIP1="192.168.151.3", LOCPORT=3500,
Description

Script

STPF=TRUE, DET=SG;
WM=ASP;
LOCIP1="192.168.151.3", LOCPORT=3600,
----End

1.
Add virtual media gateways on MGW 1 and MGW 2, and add an H.248 link for
Description
8-20

Issue 02 (2008-04-10)

2.
Issue 02 (2008-04-10)
Script

BP=BACK;
Description
Script

BP=BACK;
Add M3UA destination signaling points for interworking with MSC server 3 and related
M3UA configuration on MGW 1 and MGW 2.
Description

Script

LIP1="192.168.167.21", LP=3500, RIP1="192.168.151.3",

8-21

Description

Script

LIP1="192.168.172.41", LP=3600, RIP1="192.168.151.3",
----End
NOTE

l

SX1
unavailable
MGW
1
RNC
1
H248 link
8-22
SX3
SX2
MGW
2
RNC
2
unavailable
MGW
3
RNC
3
RNC
4
M3UA link

Issue 02 (2008-04-10)


Configure related data of the newly added H.248 link and M3UA link on MGW 3, MSC server
1 and MSC server 2.

1.
Issue 02 (2008-04-10)
Add MGW 3 on MSC server 1 and MSC server 2 and H.248 links from MGW 3 to MSC
Description
MSC server 1.
Script

ENCT=NSUP,
-1&RATE795-1,
740-1&RATE795-1&RATE102-1&RATE122-1,
-1&RATE795-1&RATE102-1&RATE122-1,
40-1&RATE795-1&RATE102-1&RATE122-1,
MFR-1;
SLOCPORT=2203, SRMTIP1="192.168.175.42",
Description
MSC server 2.

8-23
Script
2.
8-24


ENCT=NSUP,
-1&RATE795-1,
740-1&RATE795-1&RATE102-1&RATE122-1,
-1&RATE795-1&RATE102-1&RATE122-1,
40-1&RATE795-1&RATE102-1&RATE122-1,
MFR-1;
SLOCPORT=5300, SRMTIP1="192.168.175.42",
Add related data configuration of the M3UA on MSC server 1 and MSC server 2 for
Description

Script

STPF=TRUE, DET=SG;
WM=ASP;
LOCIP1="192.168.153.1", LOCPORT=2204,
Description


Issue 02 (2008-04-10)

Script

STPF=TRUE, DET=SG;
WM=ASP;
LOCIP1="192.168.155.2", LOCPORT=4300,
----End

1.
Issue 02 (2008-04-10)
Description
Script

BP=BACK;
Description

8-25
Script
2.


BP=BACK;
Add the configuration of the SIGTRAN on MGW 3 for interworking with MSC server 1
and MSC server 2 where Network Type is MSC Pool.
Description

Script

OPC=H'903;
A
DD M3RT: RN="SX1", DEX=0, LSX=0;
LIP1="192.168.175.42", LP=2204, RIP1="192.168.153.1",
Description

Script

LIP1="192.168.175.42", LP=4300, RIP1="192.168.155.2",
----End
NOTE

8-26

Issue 02 (2008-04-10)

l
8.4 Access of the Access Network

This section describes the access of the access network of a 3G network evolving to an MSC
Pool network.
8.4.1 Connecting RNC 1 to MSC Server 1 in the MSC Pool
8.4.4 Adding RNC 2 to the MSC Pool
This section describes the data configuration in the access of the access network.

The RANAP protocol is used for the communication between the MSOFTX3000 and the RNC.
The protocol can be based on the ATM or IP bearer.
Usually, on current network, MGWs are used to forward the signaling between the
MSOFTX3000s and the RNCs. The signaling between an MSOFTX3000 and an MGW is
transmitted over the IP bearer and the signaling between the MGW and the RNC is transmitted
over the ATM bearer. New links need to be configured with the evolution of the network.
General Configuration Items

General configuration items are as follows:
l
On the MSC server 1, modify configuration of RNC 1 so that it supports the Iu-Flex
function.
On the MSC server 1, add an access media gateway and a route from MSC server 1 to RNC
1.
On the MGW, activate the virtual MGW corresponding to MSC server 1.

For the original network, the data of the M3UA links following the path of MSC server 1 >
MGW 1 > RNC 1 is already configured. The data of the M3UA links following the paths of
Issue 02 (2008-04-10)

8-27

MSC server 1 > MGW 2 > RNC 1 and MSC server 1 > MGW 3 > RNC 1 is configured when
MGW 2 and MGW 3 is being added to the MSC Pool. Thus, the data of the M3UA links from
MSC server 1 to RNC 1 need not be configured. The corresponding MGWs and the signaling
routes, however, need to be added.
1.
2.
3.
Configure the access media gateway.

Description
Configure the access media gateway.
Script

Add a route.
Description
Add a route from MSC server 1 to RNC 1.
Script

On the MSC server, configure the RNC so that it supports the Iu-Flex function.
Description
On the MSC server, configure the RNC so that it supports the Iu-Flex
function.
Script
----End

To configure data on the MGW, perform the following steps:
1.
2.

Description
Activate the virtual MGW corresponding to MSC server 1 on MGW

2.
Script
ACT VMGW: VMGWID=1;
Configure the data of the signaling and voice channels from MGW 2 to RNC 1.
For details, refer to the UMG8900 Configuration Example.
3.
4.

Description
Activate the virtual MGW corresponding to MSC server 1 on MGW

3.
Script
ACT VMGW: VMGWID=1;
Configure the data of the signaling and voice channels from MGW 3 to RNC 1.
For details, refer to the UMG8900 Configuration Example.
----End
8-28

Issue 02 (2008-04-10)

Configuring Data on the RNC

NOTE
The commands used to configure the data of the RNC vary with the manufacturers of the equipment used
in the network. For details, refer to the data configuration manual of the RNC.
To configure data on the RNC1, perform the following steps:

1.
Enable the Iu-Flex function.
2.
Configure the length of the NRI and the value of the Null-NRI.
3.
Add the relevant CN nodes and set the relevant parameters, including the CN carrier index,
the CN-Id, the CN node, the Off-load status, and the CN node capacity.
4.
Add the mappings between the relevant CN nodes and the NRIs.
5.
Configure the data of the signaling and voice channels following the paths of RNC 1 >
MGW 2 > MSC server 1 and RNC 1 > MGW 3 > MSC server 1.
----End

After all the data is configured, run link maintenance commands of the MSC server, MGW and
RNC on the M2000 to check all the links.
l


l
Add RNC 1on MSC server 2.
Add paging control data on MSC server 2.

To configure data on the MSC server, perform the following steps:
1.
Add related data of RNC 1 on MSC server 2.

(1) Set RNC 1 as an M3UA destination entity of MSC server 2.
Descriptio
n
Issue 02 (2008-04-10)
Set RNC 1 as an M3UA destination entity of MSC server 2.

8-29

Script
ADD M3DE: DENM="RNC1", LENM="SX2_NATB", NI=NATB,

DPC="10B", DET=SP;
(2) Add an office direction between RNC 1 and MSC server 2.

Descriptio
n
Add an office direction between RNC 1 and MSC server 2.
Script
ADD OFC: ON="RNC1", OFFICT=RNC, DOL=LOW, DOA=RNC,

BOFCNO=1, OFCTYPE=COM, SIG=NONBICC/NONSIP,
NI=NATB, DPC1="10B", CONFIRM=Y;
(3) Configure the access MGW.

Descriptio
n
Configure the access MGW.
Script
ADD RANMGW: OFFICENAME="RNC1", MGWNAME="MGW1";ADD

RANMGW: OFFICENAME="RNC1", MGWNAME="MGW2";ADD
RANMGW: OFFICENAME="RNC1", MGWNAME="MGW3";
(4) Configure the M3UA routes between MSC server 2 and RNC 1.
Descriptio
n
Configure the M3UA routes between MSC server 2 and RNC 1.
Script

(5) Add an SCCP destination signaling point.

Description
Add an SCCP destination signaling point.
Script
ADD SCCPDSP: DPNM="RNC1", NI=NATB, DPC="10B",

OPC="802";
(6) Add RNC 1 on MSC server 2.

Description
Script
ADD RNC: RNCID=1, NI=NATB, OPC="802", DPC="10B",

RNCNM="RNC1",
CAPABILITY=IUFLEX-1&MGWPROXYIUFLEX-1&PRIVATEMSG-1,
MLAIF=YES;
(7) On MSC server 2, configure RNC 1 to support the Iu-Flex function.
8-30
Description
On MSC server 2, configure RNC 1 to support the Iu-Flex function.
Script

Issue 02 (2008-04-10)

(8) Add an SCCP subsystem.
2.
Desc
ripti
on
Add an SCCP subsystem.
Scrip
t
ADD SCCPSSN: SSNNM="RNC1_SCMG", NI=NATB, SSN=SCMG,

SPC="10B", OPC="802";
ADD SCCPSSN: SSNNM="RNC1_RANAP", NI=NATB, SSN=RANAP,
SPC="10B", OPC="802";
Configure the paging data of the location areas managed by RNC 1 on MSC server 2.
Description
Configure the paging data for the location areas managed by RNC 1 on
MSC server 2.
Script
--------End

The procedure for configuring data on the MGW when connecting RNC 1 to MSC server 2 in
the MSC Pool is similar to that when connecting RNC 1 to MSC server 1 in the MSC Pool. For
details, see the section 8.4.1 Connecting RNC 1 to MSC Server 1 in the MSC Pool.
Configuring Data on the RNC

Configure the data of the signaling and voice channels following the paths of RNC 1 > MGW
1 > MSC server 2, RNC 1 > MGW 2 > MSC server 2, and RNC 1 > MGW 3 > MSC server 2.

After all the data is configured, run link maintenance commands of the MSC server, MGW, and
BSC on the M2000 to check all the links.
You can proceed with the next step if the following conditions are met:
l

The process of connecting RNC 1 to MSC server 3 in the MSC Pool is similar to that for
connecting RNC 1 to MSC server 2. For details, see section 8.4.2 Connecting RNC 1 to MSC
Server 2 in the MSC Pool.
Issue 02 (2008-04-10)

8-31


The process of adding RNC 2 to the MSC Pool is similar to that of adding RNC 1 to the MSC
Pool. For details, refer to the data configuration for adding RNC 1 to the MSC Pool.

Pool. For details, refer to the data configuration of adding RNC 1 to the MSC Pool.

Pool. For details, refer to the data configuration of adding RNC 1 to the MSC Pool.

This section describes other data configuration of a 3G network evolving to an MSC Pool
network.
For details, see 5.5 Other Data Configuration in the "New MSC Pool in the 2G Network"
chapter.

This procedure is similar to that in the scenario of 3G networking evolution. For details, see 7.6
System Commissioning in the "New MSC Pool in the 3G Network" chapter.
8-32

Issue 02 (2008-04-10)

Routine Maintenance
About This Chapter

This section describes the routine maintenance operations of the MSC Pool, including setting
the attributes of an MSC Pool, checking the alarms of an MSC Pool, monitoring the MSC Pool
load in real time, querying the performance report of the MSC Pool, manual redistribution of
subscribers, and checking MSC Pool data.
9.1 Setting the Attribute Parameters of an MSC Pool
This section describes how to set or modify the attribute parameters of the MSC Pool through
the M2000.
9.2 Checking the Alarms of the MSC Pool
This section describes how to check the alarm information on the MSC Pool through the
M2000.
9.3 Monitoring MSC Pool Load in Real Time
This section describes how to monitor the load of the MSC Pool in real-time through the
M2000.
9.4 Reviewing the MSC Server which Is Serving the Specified Subscriber
This section describes how to review the MSC server serving the specified subscriber through
the M2000.
9.5 Querying the Performance Report of the MSC Pool
This section describes how to query the performance report of the MSC Pool through the
M2000.
9.6 Manual Migration of Subscribers
This section describes how to perform manual migration of subscribers through the M2000.
9.7 Auditing MSC Pool Data
This section describes how to auditing MSC Pool data through the M2000.
Issue 02 (2008-04-10)

9-1

9.1 Setting the Attribute Parameters of an MSC Pool

This section describes how to set or modify the attribute parameters of the MSC Pool through
the M2000.
The setting of the parameters closely relating to the MSC Pool attributes, such as NRI and the
parameters pertaining to load balancing, must be consistent with the access network (AN) and
the core network (CN) sides. Using the centralized management function provided by the
M2000, you can set these parameters for multiple NEs through the graphical user interface
(GUI). This setting mode can reduce your work load and improve your work accuracy greatly.
9.1.1 Description of the MSC Pool Attribute Parameters
This section describes the parameters relating to the attributes of the MSC Pool. It also describes
how the setting of each of the parameters affects the operation of the MSC Pool.
9.1.2 Reviewing the Attribute Parameters of an MSC Pool
This section describes how to review the parameters relating to the MSC Pool attributes on the
M2000.
9.1.3 Adding NRI for an MSC Pool
The NRI is a part of the TMSI. When the length of existing TMSIs is insufficient for the number
of subscribers, you can increase the number of subscribers that can be served by an MSC server
in a pool by increasing the number of NRIs of the MSC servers in the MSC Pool.
9.1.4 Setting the Mapping Between the NRI and the CN ID
This section describes how to set the mapping between the NRI and the CN ID.
9.1.5 Setting NRI Length and Null NRI
This section describes how to set the NRI length and Null NRI.
9.1.6 Setting the Parameters Relating to Load Balancing of the MSC Pool
This section describes how to set the parameters relating to load balancing of MSC Pool.
9.1.7 Setting the Non-broadcast LAI of the MSC Pool
This section describes how to set the non-broadcast LAI of the MSC Pool.
9.1.8 Setting the Maintenance Status of an NE in the MSC Pool
This section describes how to set the maintenance status of an NE in the MSC Pool.
9.1.1 Description of the MSC Pool Attribute Parameters

This section describes the parameters relating to the attributes of the MSC Pool. It also describes
how the setting of each of the parameters affects the operation of the MSC Pool.
The following describes the parameters relating to the attributes of the MSC Pool. It also
describes how the setting of each of the parameters affects the operation of the MSC Pool.
Table 9-1 describes the parameters relating to the attributes of the MSC Pool.
9-2

Issue 02 (2008-04-10)

Table 9-1 Description of the parameters relating to the attributes of the MSC Pool
Parameter
Description
CN ID
The identity of a CN node. It uniquely identifies an MSC server in the MSC

Pool.
NRI
The network resource identifier.

It identifies the MSC server
serving a specified mobile
station (MS)/user equipment
(UE). Bits 14 to 23 of the TMSI
are reserved for the NRI. The
NRI has a configurable length of
0 through 10 bits.
Non-broadcast
LAI
Issue 02 (2008-04-10)
When the length of the NRI is

not 0, the NRI must start at bit
23 of the TMSI.
When the length of the NRI is

0, you can infer that the
system does not support the
MSC Pool function.
A special location area identity

(LAI).It is uniformly coded
together with the ordinary LAI.
The non-broadcast LAI is used
to identify an MSC server in the
MSC Pool. Each MSC server in
the MSC Pool has a unique nonbroadcast LAI.
Effect on the Operation of the MSC

Pool
When an MS/UE registers on an MSC

server in the MSC Pool for the first time,
the MSC server assigns a TMSI
containing the NRI of the local MSC
server to the MS/UE. Later, when the
MS/UE initiates a service, it includes the
NRI in the service request sent to the
NAS node selection function (NNSF)
node (MGW or RNC), which then routes
the service request to the corresponding
MSC server based on the NRI. In this
service implementation mode, when an
MS/UE roams within the MSC Pool, its
serving MSC server remains the same
one. Comparing with the traditional
network, this can reduce the amount of
location update signaling traffic over the
C/D interface greatly.
Each MSC server within the MSC Pool
must be configured with the nonbroadcast LAI of every other MSC
server in the MSC Pool. The function of
the non-broadcast LAI is as follows:
l
When MSs/UEs are migrating to

another MSC server, the nonbroadcast LAI is used to trigger the
immediate location update to the
MSs/UEs served by the original MSC
server.
When MSs/UEs are migrating to

another MSC server, the target MSC
server determines the address of the
original MSC server based on the
non-broadcast LAI of the original
MSC server, and then obtains the
subscriber information (such as the
IMSI and the unused encryption
parameters) from the original MSC
server.

9-3

Parameter
Description

Pool
Pool Available
Capacity
The capacity of an MSC server

in the MSC Pool minus the
number of subscribers of an
RNC/BSC which is outside the
MSC Pool area and is served by
the MSC server, if any.
The system distributes the subscriber

traffic to different MSC servers based on
the value of Pool Available Capacity of
each MSC server in the MSC Pool
evenly.
NOTE
NOTE
An MSC server in the MSC Pool
can also serve an RNC/BSC
outside the MSC Pool area
independently of other MSC
servers in the MSC Pool. The value
of the parameter Pool Available
Capacity should be the capacity of
the MSC server minus the number
of subscribers of the RNC/BSC
outside the MSC Pool area.
MGW
Segregate
Status
The state of an MGW when the

MGW is isolated. At this time,
the MGW continues processing
the ongoing service but does not
accept any new service request.
Setting an MGW into isolated state

ensures smooth exit of an MGW from
the system and avoids impact on the
service provisioning.
NOTE
NOTE
l The MGWs mentioned here
refers to the VMGWs providing

the Iu-Flex function.
l A physical MGW is divided
into several virtual MGWs

based on its logical functions.
CN Node
Status
The state of an MSC server in

the MSC pool. Its value can be
Normal, OffLoad, Forbidden,
and Unknown.
In normal cases, the MSC server is in

Normal state. When MSs/UEs are
migrating to another MSC server, you
need to set the state of the MSC server
originally serving the subscribers to
Uninstall. Set the state of an MSC server
in an MSC pool to Forbidden when you
want to upgrade the MSC server after the
MSC server is isolated. When an MSC
server is in Forbidden state, the RNC
does not send any service request to the
MSC server.
Iu-Flex
Activated
Status
It indicates whether the NEs in the MSC Pool support the Iu-Flex function.
l
True: The NEs in the MSC Pool support the Iu-Flex function.
False: The NEs in the MSC Pool do not support the Iu-Flex function.
NOTE
The Iu-Flex function enables one RAN node to connect to multiple CN nodes.
9-4

Issue 02 (2008-04-10)

Parameter
Description

Pool
Length of NRI
The length of the NRI. The NRI

is contained in the TMSI
assigned to an MS/UE by an
MSC server. The number of
digits occupied by the NRI in the
TMSI is the length of the NRI.
Setting the NRI length is a prerequisite

for the NNSF node (such as the MGW
or RNC) to obtain the NRI information
from the TMSI, and then sends the MS/
UE request to the corresponding MSC
server.
NOTE
NOTE
Setting of Length of NRI on the MSC
servers in the MSC Pool and the setting of
the parameter on the RNCs in the served
MSC Pool area must be the same.
Null NRI
The special NRI. It is uniformly

coded with the ordinary NRI.
When subscribers are migrating to

another MSC server in the MSC Pool,
this parameter is used to instruct the
RNC/BSC to select the correct MSC
server for the subscribers. Null NRI is
unique in an MSC Pool.
9.1.2 Reviewing the Attribute Parameters of an MSC Pool

This section describes how to review the parameters relating to the MSC Pool attributes on the
M2000.
Prerequisite
Before you review the parameters relating to the attributes of the MSC Pool on the M2000,
ensure that the following prerequisites are fulfilled:
l
You have logged in to the M2000 Client successfully.
You have the right to perform operations on the MSC Pool.
To review the parameters relating to the attributes of the MSC Pool, perform the following steps:
Procedure
Step 1 Choose Configuration > Pool Management. The MSC Pool Management tab appears.
Issue 02 (2008-04-10)

9-5

Figure 9-1 MSC Pool Management interface
Step 2 In the navigation tree, choose the MSC Pool of which the attributes you want to view.
Step 3 Right-click the MSC Pool and choose Pool Parameter Setting. The Pool Parameter Setting
dialog box appears.
9-6

Issue 02 (2008-04-10)

Figure 9-2 Parameter Setting dialog box
Step 4 Click relevant tabs and view the parameters as required.

----End
9.1.3 Adding NRI for an MSC Pool

The NRI is a part of the TMSI. When the length of existing TMSIs is insufficient for the number
of subscribers, you can increase the number of subscribers that can be served by an MSC server
in a pool by increasing the number of NRIs of the MSC servers in the MSC Pool.
Prerequisite
Before you increase the number of NRIs of an MSC Pool, ensure that the following prerequisites
are fulfilled:
l
You have the right permission to perform operations on the MSC Pool.
Context
After adding an MSC server to an MSC Pool, you also need to add the NRI of the MSC server
through the M2000.
NOTE
Changing the NRIs affects the service provisioning greatly. Therefore, it is recommended to plan the NRIs
in advance, and then add them through the M2000 Client.
To add NRI for an MSC Pool, perform the following steps:

Issue 02 (2008-04-10)

9-7

Procedure
Step 1 Choose Configuration > Pool Management. The MSC Pool Management interface appears.
Step 2 In the navigation tree, choose the MSC Pool for which you want to add an NRI.
dialog box appears.
Step 4 Choose the NRI Setting tab and click Add. The Add dialog box appears.
Figure 9-3 Add dialog box
Step 5 Choose the MSC server for which you want to add an NRI in MSC Server.
Step 6 In NRI, enter the value of the NRI to be added.
NOTE
The value of the NRI should be unique in an MSC Pool.
For details of NRI, see section 9.1.1 Description of the MSC Pool Attribute Parameters.
Step 7 Click OK. The NRI you just added is displayed in the list on the NRI Setting tab with
the left.
Step 8 Click Apply. The NRI you just added is applied and
at
disappears.
NOTE
You can click Undo to cancel the adding of the NRI.
----End
9.1.4 Setting the Mapping Between the NRI and the CN ID

This section describes how to set the mapping between the NRI and the CN ID.
Prerequisite
Setting the mapping between the NRI and the CN ID is a prerequisite for the NNSF node (such
as the MGW and the RNC) to send the MS/UE request to the corresponding MSC server based
on the NRI. Generally, the mapping between the NRI and the CN ID is determined at the network
planning of the MSC Pool. If the network planning has some defects or needs adjusting, you can
reset the mapping between the NRI and the CN ID through the M2000.
9-8

Issue 02 (2008-04-10)

Before you set the mapping between the NRIs and the CN IDs, ensure that the following
prerequisites are fulfilled:
l
Context
NNSF nodes refer to the nodes that provide the NNSF function, such as the MGW and the RNC.
To set the mapping between the NRI and the CN ID, perform the following steps:
Procedure
Step 2 In the navigation tree, choose the MSC Pool for which you want to set the mapping between the
NRI and the CN ID.
dialog box appears.
Step 4 Click the NRI Setting tab and select the record you want to modify.
Step 5 Double-click the record or click Modify. The Modify dialog box appears.
Figure 9-4 Modify dialog box (1)
All the NEs (such as RNCs, proxy MGWs, MSC Servers) in an MSC Pool are configured with
the mapping between the CN IDs and the NRIs of all the MSC servers in the MSC Pool. The
meaning of the add and remove operations vary with the networking types of the MSC Pool, as
shown in Table 9-2.
Table 9-2 Meaning of the add and remove operations
Issue 02 (2008-04-10)
Networking Type of
the MSC Pool
Meaning of the Operation
MSC Pool consists of CN

NEs only
Modify: Modify only the NRIs on a specified MSC server.

Remove: Remove only the NRIs on a specified MSC server.

9-9

Networking Type of
the MSC Pool
Meaning of the Operation
MSC Pool consists of

access network (AN) NEs
only
Modify: Modify the NRIs of a specified MSC server on all the

RNCs/BSCs.
MSC Pool consists of both

CN and AN NEs
Modify: Modify the NRIs of a specified MSC server and modify

these NRIs on all the RNCs/BSCs.
Remove: Remove the NRIs of a specified MSC server from all

the RNCs/BSCs.
Remove: Remove the NRIs of a specified MSC server and

remove these NRIs from all the RNCs/BSCs.
Step 6 In NRI, enter the value of the NRI. The value of the NRI should be unique in an MSC Pool.
Step 7 Click OK. The new NRI is displayed in the list on the NRI Setting tab with
at the left.
Step 8 Click Apply. The new mapping between the NRIs and the CN IDs is applied. You can click
Undo on the NRI Setting tab to cancel the modification of the NRI.
----End
9.1.5 Setting NRI Length and Null NRI

This section describes how to set the NRI length and Null NRI.
Prerequisite
When the valid length of the NRI needs to be changed due to the change of network plan or a
lack of NRI resource, you can reset Length of NRI through the M2000. The NNSF node (such
as the MGW or RNC) obtains the NRI information from the TMSI based on the NRI length, and
then sends the MS/UE request to the corresponding MSC server. You can set the Null NRI to
different values to instruct the NNSF node to reselect a usable MSC server for the MS/UE.
Before you set NRI Length and Null NRI, ensure that the following prerequisites are fulfilled:
l
Context
Resetting Length of NRI may affect the service provisioning of neighboring MSC Pool areas.
Therefore, it is recommended to replan the NRIs of the MSC Pool areas of the entire network
before performing the operation.
To set Length of NRI and Null NRI, perform the following steps:
Procedure
9-10

Issue 02 (2008-04-10)

Step 2 In the navigation tree, choose the MSC Pool for which Length of NRI or Null NRI needs to be
reset.
dialog box appears.
Step 4 Click the Advanced Setting tab and select the record you want to modify.
Step 5 Double-click the record or click Modify. The Modify dialog box appears.
Step 6 Reset Length of NRI or Null NRI.

For details of Length of NRI and Null NRI, see section 9.1.1 Description of the MSC Pool
Attribute Parameters.
Step 7 Click OK.
The new NRI length or Null NRI is displayed in the list on the Advanced Setting tab with
at the left.
Step 8 Click Apply.
The new NRI length or Null NRI is applied.
----End
9.1.6 Setting the Parameters Relating to Load Balancing of the MSC

Pool
This section describes how to set the parameters relating to load balancing of MSC Pool.
Issue 02 (2008-04-10)

9-11

Prerequisite
After an MSC Pool is established, you need to set the capacity of each MSC server in the MSC
Pool. This setting serves as a guide for the RNC to distribute the accessed subscribers to different
MSC servers in the MSC Pool.
Before you set the parameters relating to the load balancing of the MSC Pool, ensure that the
following prerequisites are fulfilled:
l
To set the parameters relating to the load balancing of the MSC Pool, perform the following
steps:
Procedure
Step 1 Choose Configuration > Pool Management.
The MSC Pool Management interface appears.
Step 2 In the navigation tree, choose the MSC Pool for which you want to set the load balancing
parameters.
Step 3 Right-click the MSC Pool and choose Pool Parameter Setting.
The Pool Parameter Setting dialog box appears.
Step 4 Click the Load Balance Parameter tab and choose the record you want to modify.
Step 5 Double-click the record or click Modify.
The Modify dialog box appears.
Step 6 In New Pool Available Capacity(K), enter the new available capacity of the MSC server.
Step 7 Click OK.
The new available capacity of the MSC Server is displayed in the list on the Load Balance
Setting tab with
at the left.
Step 8 Click Apply.

9-12

Issue 02 (2008-04-10)

The new available capacity of the MSC Server is applied.

----End
9.1.7 Setting the Non-broadcast LAI of the MSC Pool

This section describes how to set the non-broadcast LAI of the MSC Pool.
Prerequisite
When the subscribers of an MSC Pool are migrating, the target MSC server determines the
address of the original MSC server serving the subscribers based on the non-broadcast LAI, and
then obtains the subscriber information from the original MSC server. The non-broadcast LAI
of each MSC server in the MSC Pool is determined at the network planning. If the network
planning requires changed, you can modify non-broadcast LAI of each MSC server through the
M2000.
Before you set the non-broadcast LAI of the MSC Pool, ensure that the following prerequisites
are fulfilled:
l
To set Non-broadcast LAI of the MSC Pool successfully, perform the following steps:
Procedure
Step 2 In the navigation tree, choose the MSC Pool for which you want to modify the value of Nonbroadcast LAI.
The Pool Parameter Setting dialog box appears.
Step 4 Click the Non-broadcast LAI Setting tab and select the record you want to modify.
Step 5 Double-click the record or click Modify.
The Modify dialog box appears.
Issue 02 (2008-04-10)

9-13

Step 6 In New Non-Broadcast LAI, enter the new value of Non-broadcast LAI.
For details of Non-broadcast LAI, see section 9.1.1 Description of the MSC Pool Attribute
Parameters.
Step 7 Click OK.
The new value of Non-broadcast LAI is displayed in the list on the Load Balance Setting tab
with
at the left.
Step 8 Click Apply.

The new value of Non-broadcast LAI is applied.
----End
9.1.8 Setting the Maintenance Status of an NE in the MSC Pool

This section describes how to set the maintenance status of an NE in the MSC Pool.
Prerequisite
To isolate the MGW for subscriber migration, set the maintenance status of an NE in the MSC
Pool through the M2000. The maintenance status of an NE can be MGW Segregate Status or
CN Node Status.
Before you set the maintenance status of an NE in the MSC Pool, ensure that the following
l
To set the maintenance status of an NE in the MSC pool, perform the following steps:
Procedure
Step 2 In the navigation tree, select the MSC Pool for which you want to set the maintenance status of
the NEs.
Step 4 The Pool Parameter Setting dialog box appears.
Step 5 Click the NE Status Maintenance tab and choose the NE status in Set Status as required by
the maintenance operation.
Table 9-3 lists the mapping between the maintenance operations and the NE status.
Table 9-3 Mapping between the maintenance operations and the NE status
9-14
Maintenance Operation
State
MGW segregation
MGW Segregate Status

Issue 02 (2008-04-10)

Maintenance Operation
State
Subscriber migration
CN Node Status
Step 6 In the list, double-click the record you want to modify or select the record and click Modify.
Step 7 In Set Status, set the NE status as required.
Figure 9-9 Set Status dialog box
Step 8 Click OK.

The modified NE status record is displayed in the list on the NE Status Maintenance tab with
at the left.
Step 9 Click Apply.
The modified NE status is applied.
----End
9.2 Checking the Alarms of the MSC Pool

This section describes how to check the alarm information on the MSC Pool through the
M2000.
By checking the alarms generated for the MSC Pool, you can monitor the status of the MSC
Pool and take appropriate measures in time. MSC Pool alarms consist of load unbalance alarms
(fault alarm) and data inconsistency alarms (event alarm).
9.2.1 Checking the Fault Alarms of the MSC Pool
This section describes how to check the fault alarms of the MSC Pool.
9.2.2 Checking the Event Alarms of the MSC Pool
This section describes how to check the event alarms of the MSC Pool.
9.2.1 Checking the Fault Alarms of the MSC Pool

This section describes how to check the fault alarms of the MSC Pool.
Issue 02 (2008-04-10)

9-15

Prerequisite
The M2000 generates a fault alarm when the load is unevenly distributed among the MSC servers
in the MSC Pool. By setting various query conditions, you can quickly detect any unbalanced
load distribution of the MSC Pool of your concern and take adequate measures in time.
Before you view the fault alarms of the MSC Pool, ensure that the following prerequisites are
fulfilled:
l
Context
Fault alarms refer to the alarms generated when the load of the MSC Pool is distributed unevenly
among different MSC server. The alarm belongs to internal alarms.
To check the current fault alarms of a specific NE in the MSC Pool, check the color of the icon
corresponding to the required IE and the alarm bubble chart on the topology of the M2000 or
the MSC Pool. When a fault alarm is generated for an NE, the icon of the NE is displayed in the
color of critical alarm. Additionally, an alarm bubble chart showing the alarm level identifier
and the alarm quantity is displayed beside the icon of the NE.
To check the fault alarms of the MSC Pool, perform the following steps:
Procedure
Step 2 Open the Filer dialog box in any one of the following methods:
l
In the navigation tree, right-click the MSC Pool for which you want to check the alarms and
choose Alarm Query > Fault Alarm from the short-cut menu.
Choose Fault > Current Fault Alarms.
Click
on the toolbar.
Figure 9-10 shows the Filter dialog box.
9-16

Issue 02 (2008-04-10)

Figure 9-10 Filter dialog box
Step 3 Set the query conditions.

1.
Click the Alarm Source tab and select By Topo in the Select area.
2.
Under Topology Root , select MSC Pool , and then select a specific MSC Pool.
Figure 9-11 Alarm Source tab
3.
Issue 02 (2008-04-10)
Click the Base Setting tab, and then set Occurrence Time Range of the alarm.

9-17

Figure 9-12 Base Setting tab
CAUTION
Critical in the Level area and Internal in the Type area must be selected. By default, all the
options in the Level area and the Type area are selected.
Step 4 Click OK.
The query results are displayed in Current Fault Alarms interface.
----End
9.2.2 Checking the Event Alarms of the MSC Pool

This section describes how to check the event alarms of the MSC Pool.
Prerequisite
The M2000 generates event alarms when the data on different MSC servers or MGWs of the
MSC Pool is inconsistent. By setting various query conditions, you can quickly detect any data
inconsistency on the MSC servers and/or MGWs in the MSC Pool of your concern and take
adequate measures in time. This ensures the smooth operation of the MSC Pool.
Before you check the event alarms of the MSC Pool, ensure that the following prerequisites are
fulfilled:
9-18

Issue 02 (2008-04-10)

Context
The M2000 generates the event alarms on automatic detection of data inconsistency. The alarm
type is Internal.
To check the event alarms of the MSC Pool, perform the following steps:
Procedure
Step 2 Open the Filer dialog box in either of the following methods:
l
In the navigation tree, right-click the MSC Pool for which you want to check the alarms and
choose Alarm Query Event Alarm from the short-cut menu.
Choose Fault > Event Alarm.
Click
on the toolbar.
Step 3 Set the query conditions.

1.
Click the Alarm Source tab and select By Topo in the Select area.
2.
Under Topology Root , select MSC Pool , and then select a specific MSC Pool.
3.
Click the Base Setting tab, and then set Occurrence Time Range of the alarm.
CAUTION
Step 4 Click OK.
----End
9.3 Monitoring MSC Pool Load in Real Time

This section describes how to monitor the load of the MSC Pool in real-time through the
M2000.
During normal operation, the system uses the MSC Pool load-balancing algorithm to keep a
balanced distribution of the load among the MSC servers in an MSC Pool. Whereas, the load
distribution of the MSC Pool might be unbalanced when the NE/links are faulty, the network is
being adjusted, or the subscribers are migrating. Therefore, you need to monitor the load
distribution of the MSC Pool in real time and take adequate measures, such as subscriber
migration, to ensure constant balance of the load distribution.
9.3.1 Setting the Real-Time Monitoring of the MSC Pool
This section describes how to set the real-time monitoring of the MSC Pool.
9.3.2 Counters of MSC Pool Real-time Monitoring
Issue 02 (2008-04-10)

9-19

This section describes the counters in the Create a Real-time Load Monitor Task dialog box.
You can refer to this section when creating a real-time load monitor task.
9.3.1 Setting the Real-Time Monitoring of the MSC Pool

This section describes how to set the real-time monitoring of the MSC Pool.
Prerequisite
After you set the real-time monitoring of the MSC Pool, the M2000 shows the load distribution
variation of the MSC servers in the MSC Pool in a histogram or curve graph. By checking these
charts, you can obtain real-time information on the number of subscribers, the CPU usage of the
MSC servers, and the number of MGW contexts.
Before you set the real-time monitoring of the MSC Pool, ensure that the following prerequisites
are fulfilled:
l
Context
The real-time monitoring charts of the MSC Pool consist of:
l
Curve graph: The vertical coordinate represents the value of the monitoring counter; the
horizontal coordinate represents the time of the monitoring.
Bar graph: The vertical coordinate represents the value of the monitoring counter; the
horizontal coordinate represents the monitored object.
When you monitor multiple MSC servers at the same time, you can learn the information on the
load balancing of the MSC Pool in this way:
l
If each of the MSC servers has the same capacity, you can learn information about the load
balancing of the MSC Pool by checking the subscriber quantity histogram.
If the capacity varies with the MSC server, place the cursor on an MSC server object. The
M2000 displays the ratio of the used MSC server capacity. Through the ratio of the used
MSC server capacity and the actual load of the MSC sever in the histogram, you can learn
about the information on the load balancing of the MSC Pool.
To set the real-time monitoring of the MSC Pool, perform the following steps:
Procedure
Step 2 In the navigation tree, right-click the MSC Pool that you want to monitor.
Step 3 Choose Real-time Monitor from the short-cut menu.
The Create a Monitor Task dialog box appears.
9-20

Issue 02 (2008-04-10)

Figure 9-13 Create a Monitor Task dialog box
Step 4 Set the monitor parameters.

1.
Choose the MSC server to be monitored in the MSC Server area or choose the MGW to
be monitored in the MGW area.
You can choose multiple objects to be monitored.
2.
In Select monitor counter, choose the monitoring counters.
3.
In Select monitor period, select the monitoring period.

The M2000 periodically refreshes the value of the monitoring counters at an interval of the
monitoring period you specified. The monitor period can be 30 seconds, 1, 2, 5, 10, or 20
minutes.
CAUTION
Step 5 Click OK.
The M2000 shows the variation of the MSC server load distribution in a curve or bar graph.
Right-click the graph and select any of the following options as required:
l
Save As Picture: To save the graph as a picture in .jpg format.
Export Data: To export the monitoring data into a file of .csv format.
Print: To print the graph.
Issue 02 (2008-04-10)

9-21

l
Filter curve: To display the monitoring data of only the specified NE in the curve graph.
NOTE
The monitor task is named in the format of Monitor Taskn. Here, n represents the serial number of the task.
It starts from 1. For example, the name of the first monitor task is Monitor Task1, the name of the second
monitor task is Monitor Task2, and so on. You can change the name of the monitor task as required.
----End
9.3.2 Counters of MSC Pool Real-time Monitoring

This section describes the counters in the Create a Real-time Load Monitor Task dialog box.
You can refer to this section when creating a real-time load monitor task.
The counters relating to the real-time load monitoring task are Subscriber Quantity, CPU
Occupancy Rate and Number of MGW Contexts.
Table 9-4 describes the counters relating to the real-time load monitoring task.
Table 9-4 Counters relating to the real-time load monitoring task
Counter
Subscrib
er
Quantity
Description
Total
The total number of subscribers on the MSC server.
Conversation
The number of subscribers in conversation on the MSC

server.
Idle
The number of subscribers in idle state on the MSC server.
Power-Off
The number of subscribers in power-off state on the MSC

server.
CPU Occupancy Rate
CPU usage of the MSC server.
Number of MGW Contexts
The total number of contexts created by the MSC server

under the control of the VMGW.
9.4 Reviewing the MSC Server which Is Serving the

Specified Subscriber
This section describes how to review the MSC server serving the specified subscriber through
the M2000.
Prerequisite
In the MSC Pool, there is no mapping between the RNC and the MSC server. Subscribers served
by the same RNC may be served by different MSC servers. Through the subscriber search
function of the M2000, you can locate the MSC server serving the specified subscriber in the
MSC Pool.
Before you view the MSC serving the specified subscriber, ensure that the following
9-22

Issue 02 (2008-04-10)

l
To view the MSC server serving the specified subscriber, perform the following steps:
Procedure
Step 1 Choose Configuration > Pool Management to display the MSC Pool Management window.
Step 2 Select the MSC Pool serving the subscriber in the Root navigation tree.
Step 3 Right-click the MSC Pool and choose Subscriber Search from the shortcut menu.
The Search for subscribers dialog box is displayed, as shown in Figure 9-14.
Figure 9-14 Search for subscribers dialog box
Step 4 Select the number type of the subscriber to be searched.

The number type is classified into MSISDN and IMSI. The meanings of the number types are
as follows:
Issue 02 (2008-04-10)

9-23

l
MSISDN: It is short for mobile station international ISDN number. It refers to the number
required for calling a mobile subscriber.
IMSI: It is short for international mobile subscriber identify. It refers to the unique identity
allocated to a mobile subscriber.
Step 5 Enter the number of the subscriber to be searched in the Number text box.
Step 6 Click Search.
l
The details of the subscriber are displayed in the Result dialog box. The details include the
registered MSC server, the IMSI, the MSISDN, and the subscriber type.
If the subscriber to be located is not in the MSC Pool, a dialog box is displayed, informing
you that no related information about the subscriber is found in the MSC Pool.
If no MSC server exists in the MSC Pool, a dialog box is displayed, informing you that there
is no MSC server in the MSC Pool.
----End
9.5 Querying the Performance Report of the MSC Pool

This section describes how to query the performance report of the MSC Pool through the
M2000.
Prerequisite
After an MSC Pool is created, certain measurement entities of a single NE, such as mobile office
direction traffic, call connection ratio, call drop rate, and local network traffic, fail to serve as
the performance measurement information of the entire network. By querying the performance
report of the MSC Pool, you can summarize the performance measurement results reported by
NEs and obtain the entity data that provides global reference for routine operation and
maintenance and network adjustment.
Before you query the performance report of the MSC Pool, ensure that the following
l
To query the performance report of the MSC Pool, perform the followings steps:
Procedure
Step 1 Open the Performance Report window.
You can open the Performance Report window according to either of the following methods:
l
Choose Performance > Performance Report.
Use the shortcut menu of the MSC Pool Management window.
Choose Configuration > Pool Management.
In the Root navigation tree, right-click the MSC Pool for which performance
measurement is to be set, and then choose Performance Query.
Step 2 In the navigation tree, select the performance report to be queried, and then double click the
report or right-click the report and choose Query.
9-24

Issue 02 (2008-04-10)

The Set report conditions dialog box is displayed, as shown in Figure 9-15.
Figure 9-15 Set report conditions dialog box
Step 3 Set conditions for querying the performance report.

l
Select a time dimension from the Time dimension drop-down list box.
The M2000 summarizes the performance entity measurement results of the object to be
queried based on the time dimension. For example, if you select 15 Minutes from the Time
dimension drop-down list box, the M2000 summarizes the performance entity measurement
results every 15 minutes.
Select an object to be queried from the Object dimension drop-down list box.
For the performance entities of the MSC Pool, Object dimension can be set to LocalZone,
NE, or Pool. The meanings of the object dimensions are as follows:
LocalZone: The M2000 summarizes the same performance entity data of different NEs
in the same MSC Pool. For example, Call attempt times of local network 1 (all) = Call
attempt times of local network 1 (msc1) + Call attempt times of local network 1 (msc2).
NE: The M2000 summarizes all performance entity data of the same MSC server in
different networks in an MSC Pool. For example, Call attempt times of MSC1 = Call
attempt times of local network 1 (msc1) + Call attempt times of local network 2 (msc1)
+ Call attempt times of local network 3 (msc1).
Pool: The M2000 summarizes performance entity data of all MSC servers in the same
MSC Pool. For example, Call attempt times of an MSC Pool = Call attempt times of
MSC1 + Call attempt times of MSC2.
Select an object to be queried in the Object range area.
Choose a time period in the Time range area.
Issue 02 (2008-04-10)

9-25

l
Click Filter counter to display the Filter Counter dialog box as shown in Figure 6-16, and
then deselect the performance entity that is not to be queried.
Figure 9-16 Filter Counter dialog box
By default, all performance entities are selected.

Step 4 Click Query.
The system displays the query result in a table.
----End
9.6 Manual Migration of Subscribers

This section describes how to perform manual migration of subscribers through the M2000.
Prerequisite
Through subscribers' migration, subscribers can migrate from one MSC server or multiple MSC
servers to other MSC servers in the same MSC Pool. Thus, you can perform maintenance
operations on the MSC servers and subscribers can still keep the services properly at the same
time.
Before you perform manual migration of subscribers, ensure that the following prerequisites are
fulfilled:
l
9-26

Issue 02 (2008-04-10)

Before you perform subscriber migration, ensure that you have viewed the load of NEs in
the current network through the real-time load monitor function of the M2000 so that you
can select a proper migration mode.
Context
The migration modes are as follows:
l
Mode 1: The cooperation of the NE (such as RNC or MGW) that provides the Iu-Flex
function is required. You must set the status of the MSC server from which subscribers
migrate to Offload on the NE. In this mode, you cannot specify a destination MSC server.
The system selects a destination MSC server according to the load sharing algorithm.
Mode 2: The cooperation of the NE that provides the Iu-Flex function is not required. You
only need to specify a destination MSC server, and the system routes data of the subscribers
who migrate to the specified MSC server.
NOTE
After you complete subscriber migration in mode 1, restore the status of the MSC server configured
on the MSC server and the RNC to Normal through the M2000 Client.
In mode 2, you can designate the NRI of the specified destination MSC server on the M2000, and thus
the operation can be implemented in only the core network without the cooperation of the access
network.
When mode 1 is adopted, the principles of subscriber migration between MSC servers are as
follows:
l
On the MSC server and the RNC, configure the status of the MSC server from which the
subscribers migrate to Offload.
When the MS/UE that is registered in the MSC server in offload state originates a service,
the MSC server allocates a TMSI containing a Null NRI to the MS/UE, and informs the
MS/UE that the LAI is the Non-broadcast LAI of the local office.
After the MS/UE terminates the current service, the Non-broadcast LAI causes immediate
location update of the MS/UE because the Non-broadcast LAI differs from the LAI
broadcast by the RNC that serves the MS/UE.
When the RNC receives the location update message carrying a Null NRI from the MS/
UE, the RNC selects the MSC server (except the MSC server whose status is configured
to Offload) that supports the maximum subscriber capacity in the MSC Pool. The RNC
then routes the service to the selected MSC server. The selected MSC server completes the
registration of the MS/UE, and allocates the TMSI containing the NRI of the local office
to the MS/UE. During registration, the selected MSC server determines the MSC server in
which the subscriber is registered based on the Non-broadcast LAI that is contained in the
location update message sent by the MS/UE, and obtains the IMSI of the subscriber and
information about unused encrypted parameters.
After the subscriber migration is completed, restore the status of the MSC server configured
on the MSC server and the RNC to Normal through the M2000 Client. For the detailed
procedures for restoring the status, see section 5.4.2 Presetting Data for the MSC Pool.
To perform manual migration of subscribers, perform the following steps:
Procedure
Issue 02 (2008-04-10)

9-27

Step 2 In the Root navigation tree, select the MSC Pool from which the subscribers migrate.
Step 3 Right-click the MSC Pool and choose Load-Redistribution from the shortcut menu.
The Load re-distribution-Select a type dialog box is displayed, as shown in Figure 9-17.
Figure 9-17 Load re-distribution-Select a type dialog box
NOTE
If the selected MSC Pool does not include NEs of the access network, the M2000 displays the Confirm
dialog box, asking you to confirm that the status of the CN node in the radio access network is correctly
configured. After you click Confirm, the Load re-distribution-Select a type dialog box is displayed.
Step 4 Select a subscriber migration mode as required, and then click Next.
Step 5 Perform the corresponding operations based on the subscriber migration mode.
Table 9-5 lists the mapping between the migration modes and the operations.
9-28

Issue 02 (2008-04-10)

Table 9-5 Mapping between the migration modes and the operations
Migration Mode
Operations
Re-distribution all
subscribers on the
MSC to other MSCs
1. Select the MSC server from which the subscribers migrate in the
Source NE column.
2. Select a destination MSC server in the Destination NE column.
3. Enter the load sharing ratio of the destination MSC server in the
Load Ratio column. You can also click Allocate load ratios and
the system automatically generates the load sharing ratio of the
specified destination MSC server.
4. Select a subscriber migration speed from the Re-distribution
speed drop-down list box.
Re-distribution a
certain ratio of
subscribers on the
MSC to other MSCs
The operation procedures are similar to the procedures performed

when the migration mode Re-distribution all subscribers on the MSC
to other MSCs is selected. In addition, you need to set Redistribution ratio.
Re-distribution a
certain number of
subscribers on the
MSC to other MSCs
The operation procedures are similar to the procedures performed

to other MSCs is selected. In addition, you need to set Subscribers.
Re-distribution the
subscribers with
specified RNC on the
MSC to other MSCs
Select an RNC under Candidate RNC, and then click Next. The
other operation procedures are the same as the procedures performed
to other MSCs is selected.
Re-distribution the
subscribers with
specified BSC on the
MSC to other MSCs
Select a BSC in the Candidate BSC frame, and then click Next.
Re-distribution the
subscribers with
specified LAI on the
MSC to other MSCs
Select an LAI in the Candidate LAIs frame, and then click Next.
Re-distribution the
subscribers on the
MSC to other MSC
1. Select the number type of the subscribers who migrate from the
Number type drop-down list box.
The other operation procedures are the same as the procedures

performed when the migration mode Re-distribution all subscribers
on the MSC to other MSCs is selected.
The other operation procedures are the same as the procedures

performed when the migration mode Re-distribution all subscribers
on the MSC to other MSCs is selected.
2. Select the MSC server from which the subscribers migrate from
the Resource NE drop-down list box.
3. Enter the subscriber number in the Enter the subscriber
number column.
4. Select a destination MSC server in the Destination NE column.
NOTE
l You can select only one source MSC server and one destination MSC
server.
l Up to 10 subscribers with the specified numbers can migrate.
l The number type of all the subscribers who will migrate must be set to the
same type.
Issue 02 (2008-04-10)

9-29

CAUTION
l
If the MSC server is running a subscriber migration task, the MSC server cannot serve as the
resource NE and destination NE of subscriber migration.
If the MSC server is serving as the destination NE of an ongoing subscriber migration task,
the MSC server can be designated as the destination NE of another subscriber migration task.
Step 6 Click Next to view the details of the subscriber migration.

Step 7 Click Finish.
----End
9.7 Auditing MSC Pool Data

This section describes how to auditing MSC Pool data through the M2000.
In the MSC Pool, many data items configured on all NEs must be the same; otherwise, the MSC
Pool cannot run properly. The M2000 provides the data check function, so that you can perform
maintenance operations on the network based on the check result to ensure the consistency of
the data.
9.7.1 Reviewing the Result of an MSC Pool Data Check
This section describes how to review the result of an MSC Pool data check.
9.7.2 Manually Checking MSC Pool Data
This section describes how to check the MSC Pool data manually.
9.7.3 Synchronizing MSC Pool Data
This section describes how to synchronize MSC Pool data.
9.7.1 Reviewing the Result of an MSC Pool Data Check

This section describes how to review the result of an MSC Pool data check.
Prerequisite
This section helps you to understand about the results of an automatic MSC Pool data check.
Based on the results, you can perform corresponding maintenance operations to ensure that the
data configured on the NEs in the MSC Pool, is consistent.
Before you view the result of an MSC Pool data check, ensure that the following prerequisites
are fulfilled:
l
At least one automatic data check task has been carried out.
To view the result of an MSC Pool data check, perform the following steps:
9-30

Issue 02 (2008-04-10)

Procedure
Step 2 In the Root navigation tree, select the MSC Pool whose data check result is to be viewed.
Step 3 Right-click the MSC Pool, and then choose Data Consistency Check > Automatic Check.
The Automatic Check dialog box is displayed, as shown in Figure 9-18
Figure 9-18 Automatic Check dialog box
Step 4 Click the View Check Result tab to view the check result.
Figure 9-19 shows the View Check Result tab.
Issue 02 (2008-04-10)

9-31

Figure 9-19 View Check Result tab
NOTE
You can also view the check results in the area about data consistency in the MSC Pool Management
window. By double-clicking a record, you can view the View Check Result tab.
The Result column lists the results of each automatic check. After you right-click a record whose
Result is Inconsistent or Abnormal, you can perform the following operations:
Operation
Description
Acknowledge
It indicates that the check result is processed.

This operation applies to only results that are not acknowledged.
Unacknowledge
It indicates that the acknowledged check results are identified as not

acknowledged.
This operation applies to only acknowledged results.
After you select a record whose Result is Inconsistent.

l
The Inconsistency Data tree below the result list displays the data items and key values of
the inconsistent data.
You can view the detailed check results in the box beside the Inconsistency Data tree. The
inconsistent data is in red.
Click Save to save the check results to a file.
----End
9-32

Issue 02 (2008-04-10)

9.7.2 Manually Checking MSC Pool Data

This section describes how to check the MSC Pool data manually.
Prerequisite
In the MSC Pool, certain data configured on all NEs must be the same; otherwise, the MSC Pool
cannot run properly. You can manually check the data on the M2000. After selecting NEs and
data items to be checked, you can review the data check results so that you can take related
measures to ensure the data consistency.
Before you check MSC Pool data manually, ensure that the following prerequisites are fulfilled:
l
To check MSC Pool data manually, perform the following steps:
Procedure
Step 2 In the Root navigation tree, select the MSC Pool whose data is to be checked.
Step 3 Right-click the MSC Pool and choose Data Consistency Check > Manual
Check&Synchronize Data.
The Manual Check dialog box is displayed, as shown in Figure 9-20
Issue 02 (2008-04-10)

9-33

Figure 9-20 Manual Check dialog box
NOTE
For details on the procedure for viewing the results of the manual check, see 9.7.1 Reviewing the Result
of an MSC Pool Data Check.
Step 4 Select the type of the NEs to be checked from the NE Type drop-down list box.
Step 5 Select the NEs to be checked in the NE tree.
You must select at least two NEs.
Step 6 Select the data items to be checked in the Data Item tree.
You can select multiple data items at the same time.
Step 7 Click Check.
The Data Consistency Check dialog box is displayed as shown in Figure 9-21, showing the
progress of updating the NE data in the cache of the server.
9-34

Issue 02 (2008-04-10)

Figure 9-21 Data Consistency Check dialog box (1)
Step 8 Perform the related operation based on the update result.

Table 9-6 lists the mapping between the update result and the operation.
Table 9-6 Mapping between the update result and the operation
Update
Result
Operation
Succeeded
Go to Step 9.
Failed
Click Cancel.
The Message dialog box is displayed, indicating that the data update failed and
asking you to determine whether to use the NE data in the cache of the server.
You can perform the following steps as required:
l
If you want to check the data, click Yes and then go to Step 9.
If you want to cancel the data check, click No.
Step 9 In the Data Consistency Check dialog box as shown in Figure 9-22, click OK.
Figure 9-22 Data Consistency Check dialog box (2)
----End
Postrequisite
If inconsistent data exists, the details of the data are displayed in the area under Choose NE.
Issue 02 (2008-04-10)

9-35

l
The Inconsistency Data tree displays the data items and key values of the inconsistent
data.
The detailed check results are displayed beside the Inconsistency Data tree. The
inconsistent data is in red.
If the NE data is consistent, the Data Consistency Check dialog box showing that the data is
consistent is displayed.
If inconsistent data exists, you must manually synchronize the data to ensure data consistency.
For details, see section 9.7.3 Synchronizing MSC Pool Data.
9.7.3 Synchronizing MSC Pool Data

This section describes how to synchronize MSC Pool data.
Prerequisite
In an MSC Pool network, certain data configured on NEs must be consistent. Otherwise, it may
affect the normal operation of the MSC Pool. If the data is inconsistent, you can ensure the data
consistency by using the synchronization function.
Before you synchronize data, ensure that the following prerequisites are fulfilled:
l
You have logged in to the M2000 client successfully.
You have the rights to perform operations on the MSC Pool.
You have checked the data and found that the data configured on NEs is inconsistent. (For
details on the data check, see section 9.7.2 Manually Checking MSC Pool Data)
Context
Based on the inconsistent data, the M2000 generates MML commands to adjust the data and
sends the commands to the related NEs for execution. Thus, the data can be adjusted to the
consistency.
To synchronize MSC Pool data, perform the following steps:
Procedure
Step 1 Choose a data item or key value in Choose data item in the Manual check dialog box.
You can choose only one data item or key value at a time.
Step 2 Click Synchronize.
The Data Synchronization dialog box appears, as shown in Figure 9-23.
9-36

Issue 02 (2008-04-10)

Figure 9-23 Data Synchronization dialog box
Step 3 Choose an NE in the Reference NE drop down list box.

During the synchronization, the data configured on the chosen NE is to be synchronized with.
Step 4 Choose an NE whose data is to be synchronized in the Destination NE(s) pane.
Step 5 Click Generate MML.
The command information is displayed in the right pane of the Data Synchronization dialog
box, as shown in Figure 9-24
Figure 9-24 Generated MML commands
Issue 02 (2008-04-10)

9-37

NOTE
You can modify the MML commands displayed or click Save MML to save the commands to a file
for the subsequent execution.
If the key values of the chosen destination NE(s) is the same as the values of the reference NE, prompt
information indicating data consistency and the related key values are displayed in the right pane.
If a key value does not support a generated MML command, the corresponding prompt information is
also displayed in the right pane. In this case, you need to adjust the data on the LMT of the involved
NE.
Up to 500 MML command lines can be displayed in the right pane. If the number of the command lines
is greater than 500, the system displays a message indicating that there are too many MML commands.
In this case, you need to modify the MML commands, and then the commands can be sent.
Step 6 Click Send MML and choose a send mode.

Table 9-7 describes the command send modes mapping the setting of whether to send commands
when an error occurs.
Table 9-7 Command send modes
Whether to Send
Commands When
an Error Occurs
Command Send Modes
Yes
During the sending of MML commands, if an error occurs in a

command, the system continues to send the remaining commands.
No
During the sending of MML commands, if an error occurs in a

command, the system stops sending the remaining commands.
When the MML commands are sent, the system shows the progress in the Data
Synchronization dialog box.
NOTE
During the sending of the MML commands, the system automatically filters the prompt information.
Step 7 Click Close.

Step 8 Repeat Step 1 through Step 6 to complete the synchronization of the other data.
You can click Export Result to save the result of sending the MML commands to a file.
----End
9-38

Issue 02 (2008-04-10)

10
10 MSC Pool Performance Metrics Reference
MSC Pool Performance Metrics

Reference
About This Chapter

This section describes the performance measurement entities of MSC Pool networking.
In the MSC Pool network, each MSC server within one MSC Pool serves all BSCs/RNCs in the
MSC Pool and each BSC/RNC belongs to the different MSC servers. In this case, the
performance specification of a single NE cannot completely reflect the network loading in a
specified area; thus, the performance measurement entities of each NE should be collected to
the M2000 to obtain a general entity data, which provides the reference for the routine operation
and maintenance, and the network adaptation.
The following lists measurement entities collected to the M2000 based on each area:
l
Issue 02 (2008-04-10)
Each office direction
Seizure Times
Call Connected Times
Answer Times
Seizure Traffic
Connected Traffic
Answer Traffic
Installed Circuit Num
Avail Circuit Num
Blocked Circuit Num
Average Seizure Traffic Per Line
Blocked Circuit Num
Connected Ratio
Answer Ratio
Seizure Ratio
10-1

l

Each local network
Call Attempt Times
Seizure Times
Answer Times
Seizure Traffic
Connected Traffic
Answer Traffic
Average Seizure Duration
Connected Ratio
Answer Ratio
Each LAI
Total user number (LAI)
Local user number (LAI)
Roaming user number (LAI)
Switch on user number (LAI)
Switch off user number (LAI)
Update location request times (LAI)
MO connect times (LAI)
MO response times (LAI)
MT connect traffic (LAI)
MT response traffic (LAI)
LAI paging times (LAI)
Paging response times (LAI)
MTC Succ Rate Success Paging Rate
In addition, the MSC Pool can be considered as a whole entity and the M2000 provides the
following key performance indexes (KPIs) to check the MSC Pool:
l
Handover Success Ratio, MTC Succ Rate Alert Rate, MTC Succ Rate Success Paging Rate,
and Traffic Assign Success Ratio
Call Attempt Times, Seizure Times, Call Connected Times, Answer Times, Seizure Traffic,
Connected Traffic, Answer Traffic, Average Seizure Duration, Average Seizure Traffic
Per Line, Connected Ratio, and Answer Ratio
VLR Subscriber of IMSI_DETACH, VLR Subscriber of Local, VLR Subscriber of

IMSI_ATTACH, VLR Subscriber of Local, and VLR Subscriber of Roaming
The general performance measurement supports the periodical collection of all the measured
results of preceding measurement entities reported by MSC servers within an MSC Pool to the
MSC level Pool. The measured results can be queried through the GUI or exported into a report
for querying.
The M2000 provides the performance monitoring function for general KPIs. After receiving the
measured results from the MSC level Pool, the performance monitoring module can display the
10-2

Issue 02 (2008-04-10)

results in the performance monitor window in real time, in the format of table, graph, or
histogram.
NOTE
In the MSC Pool networking, the performance measurements of a single NE are retained to measure the
single NE.
The following sections describe measurement entities of each performance measurement in

details.
10.1 Total Traffic in MSC Pool
This section describes the measurement object, calculation formula, and measurement entities
of the measurement unit Total Traffic in MSC Pool.
10.2 Incoming/Outgoing MSC Pool Traffic
of the measurement unit Mobile Office Direction Incoming/Outgoing MSC Pool Traffic.
10.3 Handover to and Out of the MSC Pool
of the measurement unit Measurement For MSC Pool HO.
10.4 All VLR Subscribers in the MSC Pool
of the measurement unit Traffic Measurement For ALL VLR Subscriber in MSC Pool.
10.5 Success Paging Rate (Traffic Measurement For MTC SUCC Rate)
of the measurement unit MSC Pool Traffic Measurement For MTC SUCC Rate (Traffic
Measurement For MTC SUCC Rate).
10.6 LAI In the MSC Pool
of the measurement unit Traffic Measurement For LAI In MSC Pool.
10.7 GSM Call Drop
of the measurement unit GSM Call Drop.
10.8 UMTS Call Drop
of the measurement unit UMTS Call Drop.
10.9 MSC Pool Traffic Measurement Of GSM Assignment
of the measurement unit MSC Pool Traffic Measurement Of GSM Assignment.
10.10 MSC Pool Traffic Measurement Of WCDMA Assignment
of the measurement unit for MSC Pool Traffic Measurement Of WCDMA Assignment.
10.11 Success SMS Rate
of the measurement unit for MSC Pool Traffic Measurement Of SMS.
10.12 Traffic Measurement For LOC Up
of the measurement unit for MSC Pool Traffic Measurement For LOC Up.
Issue 02 (2008-04-10)

10-3

10.1 Total Traffic in MSC Pool

of the measurement unit Total Traffic in MSC Pool.
This measurement unit is used to measure total traffic of an MSC Pool. The system registers the
Incoming Office Traffic, BSS Originate Call, and UTRAN Originate Call of each MSC Server
within one MSC Pool and then collects the measurement entities in each MSC Server to the
M2000.
NOTE
In the actual implementation process, the system registers a measurement task on the M2000 and then
delivers the task to the MSC Server. After that, the MSC Server is responsible for reporting the entities to
the M2000. The processes of other measurement units are the same as that of Total Traffic in MSC Pool.
Measurement object: local network index

NOTE
The following takes Call Attempt Times for an example and the calculation formulas for other measurement
entities are the same as those for Call Attempt Times.
Formula:
Call Attempt Times = (Call Attempt Times of Incoming Office Traffic of all MSC servers
within an MSC Pool) + (Call Attempt Times of BSS Originate Call of all MSC servers within
an MSC Pool) + (Call Attempt Times of UTRAN Originate Call of all MSC servers within
an MSC Pool)
The description of the specific measurement entities is as follows:
10-4
Answer Times = Answer Times of Incoming Office Traffic + Answer Times of BSS
Originate Call + Answer Times of UTRAN Originate Call
Call Attempt Times = Call Attempt Times of Incoming Office Traffic + Call Attempt Times
of BSS Originate Call + Call Attempt Times of UTRAN Originate Call
Call Connected Times = Call Connected Times of Incoming Office Traffic + Call
Connected Times of BSS Originate Call + Call Connected Times of UTRAN Originate
Call
Answer Traffic = Answer Traffic of Incoming Office Traffic + Answer Traffic of BSS
Originate Call + Answer Traffic of UTRAN Originate Call
Seizure Traffic = Seizure Traffic of Incoming Office Traffic + Seizure Traffic of BSS
Originate Call + Seizure Traffic of UTRAN Originate Call
Connect Traffic = Connect Traffic of Incoming Office Traffic + Connect Traffic of BSS
Originate Call + Connect Traffic of UTRAN Originate Call
Answer Ratio = (Answer Times of Incoming Office Traffic + Answer Times of BSS
Originate Call + Answer Times of UTRAN Originate Call)/(Seizure Times of Incoming
Office Traffic + Seizure Times of BSS Originate Call + Seizure Times of UTRAN Originate
Call) x 100
Connected Ratio = (Call Connected Times of Incoming Office Traffic + Call Connected
Times of BSS Originate Call + Call Connected Times of UTRAN Originate Call)/(Seizure
Times of Incoming Office Traffic + Seizure Times of BSS Originate Call + Seizure Times
of UTRAN Originate Call) x 100
Issue 02 (2008-04-10)

10.2 Incoming/Outgoing MSC Pool Traffic

of the measurement unit Mobile Office Direction Incoming/Outgoing MSC Pool Traffic.
These measurement units are used to measure the traffic to the specified RNC/BSC within an
MSC Pool.
Incoming MSC Pool Traffic

The system registers Mobile Office Direction Incoming Office Traffic and the office direction
number is configured in the LA/Cell table. The system requires that the office direction number
configured in each LA must be the same and the configuration must be consistent with that on
the M2000. Then, the system collects the measurement entities to the M2000.
Measurement object: specified RNC/BSC office direction
NOTE
Formula:
Call Connected Times = (Call Connected Times of Mobile Office Direction Incoming Office
Traffic of all MSC servers within an MSC Pool)
Average Seizure Traffic Per Line = Total traffic of Mobile Office Direction Incoming Office
Traffic/Avail Circuit Num
NOTE
When A-interfaces are managed by an MSC server, the number of available circuits can be accumulated;
if A-interfaces are managed by an MGW, the number of available circuits cannot be accumulated.
This measurement unit contains the following measurement entities:

l
Seizure Times
Answer Times
Seizure Traffic
Connected Traffic
Connected Traffic
Answer Traffic
Avail Circuit Num
Blocked Circuit Num
Connected Ratio
Answer Ratio
Issue 02 (2008-04-10)

10-5

Outgoing MSC Pool Traffic

The system registers Mobile Office Direction Outgoing Office Traffic and the office direction
number is configured in the LA/Cell table. The system requires that the office direction number
configured in each LA must be them same and the configuration must be consistent with that
on the M2000. Then, the system collects the measurement entities to the M2000.
Measurement object: specified RNC/BSC office direction
NOTE
Formula:
Call Connected Times = (Call Connected Times of Mobile Office Direction Incoming Office
Traffic of all MSC servers within an MSC Pool)
Average Seizure Traffic Per Line = Total traffic of Mobile Office Direction Incoming Office
Traffic/Avail Circuit Num
NOTE
When A-interfaces are managed by an MSC server, the number of available circuits can be accumulated;
if A-interfaces are managed by an MGW, the number of available circuits cannot be accumulated.
This measurement unit contains the following measurement entities:

l
Seizure Times
Answer Times
Seizure Traffic
Connected Traffic
Answer Traffic
Avail Circuit Num
Blocked Circuit Num
Connected Ratio
Answer Ratio
10.3 Handover to and Out of the MSC Pool

of the measurement unit Measurement For MSC Pool HO.
This measurement unit is used to measure the in-pool and out-pool traffic. The system registers
Measurement for MSC HO of each MSC Server within one MSC Pool and then collects
measurement entities of the MSC servers to the M2000.
Measurement object: local MSC
Formula:
10-6

Issue 02 (2008-04-10)

Request inter MSC Basic HO in = (Request inter MSC Basic HO in of Measurement For MSC
HO of all MSC servers within an MSC Pool)
This measurement contains the following measurement entities:
l
Request inter MSC Basic HO in
Request inter MSC Basic HO out
Successfully inter MSC Basic HO in
Successfully inter MSC Basic HO out
Handover success ratio
10.4 All VLR Subscribers in the MSC Pool

of the measurement unit Traffic Measurement For ALL VLR Subscriber in MSC Pool.
The system registers Traffic Measurement For VLR Subscriber of all MSC servers within one
MSC Pool and then collects measurement entities of the MSC servers to the M2000.
Measurement object: Local VLR
Formula:
VLR Subscriber of Total = (VLR Subscriber of Total of Traffic Measurement For VLR
Subscriber of all MSC servers within an MSC Pool)
l
VLR Subscriber of IMSI_DETACH
VLR Subscriber of Total
VLR Subscriber of IMSI_ATTACH
VLR Subscriber of Local
VLR Subscriber of Roaming
10.5 Success Paging Rate (Traffic Measurement For MTC

SUCC Rate)
of the measurement unit MSC Pool Traffic Measurement For MTC SUCC Rate (Traffic
Measurement For MTC SUCC Rate).
The system registers Traffic Measurement For MTC SUCC Rate of all MSC servers within the
MSC Pool and then collects measurement entities of MSC servers to the M2000.
Formula: sum of values of each measurement entity
l
Issue 02 (2008-04-10)
MTC Succ Rate Paging

10-7

MTC Succ Rate Paging Resp
MTC Succ Rate Alert
MTC Succ Rate MO Alert
MTC Succ Rate Land Alert
MTC Succ Rate Alert Rate = MTC Succ Rate Alert/MTC Succ Rate Paging x 100
MTC Succ Rate Success Paging Rate = MTC Succ Rate Paging Resp/MTC Succ Rate
Paging x 100
10.6 LAI In the MSC Pool

of the measurement unit Traffic Measurement For LAI In MSC Pool.
The system registers Traffic Measurement For LAI of all MSC servers within one MSC Pool
and then collects measurement entities of the MSC servers to the M2000.
Measurement object: specified LAI
NOTE
The following takes MO try call times (LAI) for an example and the calculation formulas for other measurement
entities are the same as that for MO try call times (LAI).
Formula:
MO try call times (LAI) = (MO try call times (LAI) of Traffic Measurement For LAI of all
MSC servers within an MSC Pool)
10-8
Total user number (LAI)
Local user number (LAI)
Roaming user number (LAI)
Switch on user number (LAI)
Switch off user number (LAI)
Update location request times (LAI)
MO connect times (LAI)
MO response times (LAI)
MT connect traffic (LAI)
MT response traffic (LAI)
MTC succ rate success paging rate

Issue 02 (2008-04-10)

10.7 GSM Call Drop

of the measurement unit GSM Call Drop.
The system registers GSM Call Drop of all MSC servers within one MSC Pool and then collects
Measurement object: local MSCC
Formula:
2G Call Drop Rate Call Drop = (2G Call Drop Rate Call Drop of GSM Call Drop of all MSC
servers within an MSC Pool)
l
2G Call Drop Rate Connect
2G Call Drop Rate MT Connect
2G Call Drop Rate MO Connect
2G Call Drop Rate MO Call Drop
2G Call Drop Rate MT Call Drop
2G Call Drop Rate HO Call Drop
2G Call Drop Rate
10.8 UMTS Call Drop

of the measurement unit UMTS Call Drop.
The system registers UMTS Call Drop of all MSC servers within one MSC Pool and then collects
Formula:
3G Call Drop Rate Call Drop = (3G Call Drop Rate Call Drop of UMTS Call Drop of all MSC
l
3G Call Drop Rate Connect
3G Call Drop Rate MT Connect
3G Call Drop Rate MO Connect
3G Call Drop Rate MO Call Drop
3G Call Drop Rate MT Call Drop
3G Call Drop Rate HO Call Drop
3G Call Drop Rate
Issue 02 (2008-04-10)

10-9

10.9 MSC Pool Traffic Measurement Of GSM Assignment

of the measurement unit MSC Pool Traffic Measurement Of GSM Assignment.
The system registers Traffic Measurement Of GSM Assignment of all MSC servers within one
MSC Pool and then collects measurement entities of the MSC servers to the M2000.
Measurement object: specified BSC office direction
l
Traffic Assign Request Times
Traffic Assign Success Times
Half Rate Traffic Assign Request Times
Half Rate Traffic Assign Success Times
Traffic Assign Success Ratio
10.10 MSC Pool Traffic Measurement Of WCDMA

Assignment
of the measurement unit for MSC Pool Traffic Measurement Of WCDMA Assignment.
The system registers Traffic Measurement Of WCDMA Assignment of all MSC servers within
one MSC Pool and then collects measurement entities of the MSC servers to the M2000.
Measurement object: specified RNC office direction
l
Assign 3G Assign Channel Request
Assign 3G Assign Channel Success
Assign 3G Assign Channel Success Ratio
10.11 Success SMS Rate

of the measurement unit for MSC Pool Traffic Measurement Of SMS.
The system registers Traffic Measurement For SMS of all MSC servers within one MSC Pool
and then collects measurement entities of the MSC servers to the M2000.
Measurement object: local network index
Formula:
10-10

Issue 02 (2008-04-10)

SMMO Success Ratio = (SMMO Success Times of Traffic Measurement For SMS of all MSC
servers within an MSC Pool)/(SMMO Times of Traffic Measurement For SMS of all MSC
l
SMMO Times
SMMO Success Times
SMMT Times
SMMT Success Times
SMMO Success Ratio
SMMT Success Ratio
10.12 Traffic Measurement For LOC Up

of the measurement unit for MSC Pool Traffic Measurement For LOC Up.
The system registers Traffic Measurement For LOC Up of all MSC servers within one MSC
Pool and then collects measurement entities of the MSC servers to the M2000.
Measurement object: specified LAI
l
Number of Location Update request
Number of Location Update reject
Number of IMSI detach
Number of IMSI attach
Number of Location Update Intra_VLR Require
Success No of Location Update Intra_VLR Require
Number of Location Update Inter_VLR Require
Success No of Location Update Inter_VLR Require
Success No of National Roaming User Registration
Success No of International Roaming User Registration
Formula for calculating Success Ratio of Location Update:

Success Ratio of Location Update = (Success No of Location Update Intra_VLR Require +
Success No of Location Update Inter_VLR Require)/Number of Location Update request
Issue 02 (2008-04-10)

10-11

Index
Index
Symbols/Numerics
2G existing network, 6-2
3G existing network, 8-2
C
configuration procedure
access network, 5-21, 7-15
core network, 5-15, 7-9
D
data configuration
2G, 6-5
3G, 8-6
access network, 6-30, 6-35, 6-37, 6-37, 6-37, 6-37,
8-27, 8-29, 8-31, 8-32, 8-32, 8-32
core network, 6-10, 6-12, 6-16, 6-19, 6-24, 8-11,
8-14, 8-17, 8-22
other, 5-24, 8-32
data planning, 6-6, 8-6
E
evolution of the core network, 6-9, 8-11
evolution process of the core network
2G, 6-9
3G, 8-10
evolution scenario
2G, 6-2
3G, 8-2
I
integration process of the access network
2G, 6-30
3G, 8-27
M
M2000
add NRI, 9-7
auditing data, 9-30
check alarm information, 9-15
check event alarm, 9-18
Issue 02 (2008-04-10)
check fault alarm, 9-15

check the data manually, 9-33
maintenance status, 9-14
manual migration of subscriber, 9-26
MSC Pool attribute parameter, 9-2
query performance report, 9-24
review the attribute of parameter, 9-5
set non-broadcast LAI, 9-13
set NRI length, 9-10
set real-time monitoring, 9-20
set the parameter of load balancing, 9-11
synchronize data, 9-36
M2000 application scenario, 1-27
M2000 function, 1-26
MSC Pool feature
backgroud, 1-2
concept, 1-2
N
network specification, 3-2
networking scheme
ATM, 2-3
CN NE inside and outside, 2-4
MGW provide the A-Flex, 2-4
TDM, 2-2
new target network
2G, 5-2
3G, 7-2
P
performance measurement entity, 10-1
GSM call drop, 10-9
traffic measurement for LAI, 10-8
traffic measurement for VLR subscriber, 10-7
traffic measurement of SMS, 10-10
UMTS call drop, 10-9
performance measurement entityhandover
, 10-6
performance measurement entitytotal traffic
, 10-4
planning, 3-4
presetting data, 5-9, 7-8

i-1

Index
principle
A-Flex function proxy, 1-18
charging, 1-24
disaster tolerance, 1-8
handover, 1-8
load balancing, 1-7, 1-17
location update with Gs interface, 1-14
managing circuit, 1-22
paging control, 1-14
subscriber migration, 1-14
R
real-time load monitor task, 9-22
routine maintenance, 9-1
S
signaling networking scheme, 2-2
system commissioning
2G, 6-38
3G, 7-18
T
target network
2G, 6-3
3G, 8-3
i-2

Issue 02 (2008-04-10)

MSC Pool User Manual

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

MSC Pool User Manual

Загружено:

Авторское право:

Доступные форматы

HUAWEI MSOFTX3000 Mobile Softswitch Center