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 ConfidentialCopyright © Huawei Technologies Co., Ltd

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

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

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 writtenconsent 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. NoticeThe information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but the statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

http://www.huawei.com

mailto:[email protected]

Contents

About This Document.....................................................................................................................1

1 Overview......................................................................................................................................1-11.1 Introduction.....................................................................................................................................................1-21.2 Concept............................................................................................................................................................1-21.3 Technical Principle..........................................................................................................................................1-6

1.3.1 Load Balancing......................................................................................................................................1-71.3.2 Handover................................................................................................................................................1-81.3.3 Disaster Tolerance..................................................................................................................................1-81.3.4 Paging Control......................................................................................................................................1-141.3.5 Location Update with Gs Interface......................................................................................................1-141.3.6 Subscriber Migration Between MSCs..................................................................................................1-141.3.7 Load Balancing at the MGW...............................................................................................................1-171.3.8 A-Flex Function Proxy on the MGW...................................................................................................1-181.3.9 MGW Managing Circuits of the A Interface........................................................................................1-221.3.10 Charging Principle..............................................................................................................................1-24

1.4 M2000 Application in the MSC Pool............................................................................................................1-261.4.1 M2000 Function...................................................................................................................................1-261.4.2 M2000 Application Scenario...............................................................................................................1-27

2 Networking Description...........................................................................................................2-12.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-22.1.2 ATM-Based Iu Interface........................................................................................................................2-3

2.2 Signaling Networking Scheme of an MSC Pool (MGW Providing the A-Flex Function).............................2-42.3 Networking Scheme for Connecting CN NEs Inside and Outside an MSC Pool...........................................2-42.4 Networking Scheme for Subscriber Data Backup...........................................................................................2-52.5 Networking Scheme for Voice Channels Related to an MSC Pool................................................................2-5

3 MSC Pool Network Planning..................................................................................................3-13.1 Limitations......................................................................................................................................................3-23.2 MSC Pool Network Specifications.................................................................................................................3-23.3 General Principles of the MSC Pool Planning................................................................................................3-4

4 Commands and Parameters Related to MSC Pool...............................................................4-14.1 Commands Used on the MSC Server..............................................................................................................4-2

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual Contents

Issue 02 (2008-04-10) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

i

4.2 Commands Used on the MGW.......................................................................................................................4-44.3 Global Data and Software Parameters.............................................................................................................4-5

5 New MSC Pool in the 2G Network........................................................................................ 5-15.1 New Target Network Description...................................................................................................................5-25.2 Data Configuration Flow.................................................................................................................................5-45.3 Data Planning..................................................................................................................................................5-55.4 Data Configuration..........................................................................................................................................5-9

5.4.1 Configuring the Basic Data of NEs........................................................................................................5-95.4.2 Presetting Data for the MSC Pool..........................................................................................................5-95.4.3 Building an MSC Pool in the Core Network........................................................................................5-155.4.4 Integration with the Access Network...................................................................................................5-21

5.5 Other Data Configuration..............................................................................................................................5-245.6 System Commissioning.................................................................................................................................5-30

6 2G Network Evolution to Support MSC Pool......................................................................6-16.1 Evolution Scenario..........................................................................................................................................6-2

6.1.1 Description of the Existing Network......................................................................................................6-26.1.2 Description of the Target Network.........................................................................................................6-3

6.2 Data Configuration Flow.................................................................................................................................6-56.2.1 Data Planning.........................................................................................................................................6-66.2.2 Presetting Data for the MSC Pool..........................................................................................................6-9

6.3 Evolution of the Core Network.......................................................................................................................6-96.3.1 Overview................................................................................................................................................6-96.3.2 Making MSC Server 1 and MGW 1 as an MSC Pool..........................................................................6-106.3.3 Adding MSC Server 2 into the MSC Pool...........................................................................................6-126.3.4 Adding MGW 2 into the MSC Pool.....................................................................................................6-166.3.5 Adding MSC Server 3 into the MSC Pool...........................................................................................6-196.3.6 Adding MGW 3 into the MSC Pool.....................................................................................................6-24

6.4 Integration with the Access Network............................................................................................................6-306.4.1 Adding BSC 1 into the MSC Pool.......................................................................................................6-306.4.2 Connecting BSC 1 to MSC Server 2 in the MSC Pool........................................................................6-356.4.3 Connecting BSC 1 to MSC Server 3 in the MSC Pool........................................................................6-376.4.4 Adding BSC 2 into the MSC Pool ......................................................................................................6-376.4.5 Adding BSC 3 into the MSC Pool.......................................................................................................6-376.4.6 Adding BSC4 into the MSC Pool........................................................................................................6-37


7 New MSC Pool in the 3G Network........................................................................................ 7-17.1 New Target Network.......................................................................................................................................7-27.2 Data Configuration Flow.................................................................................................................................7-47.3 Data Planning..................................................................................................................................................7-57.4 Data Configuration..........................................................................................................................................7-8

ContentsHUAWEI MSOFTX3000 Mobile Softswitch Center


ii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-04-10)

7.4.1 Configuring the Basic Data of NEs........................................................................................................7-87.4.2 Presetting Data for the MSC Pool..........................................................................................................7-87.4.3 Building an MSC Pool in the Core Network..........................................................................................7-97.4.4 Adding BSCs to the MSC Pool Area...................................................................................................7-15


8 3G Network Evolution to Support MSC Pool......................................................................8-18.1 Evolution Scenario..........................................................................................................................................8-2

8.1.1 Description of the Existing Network......................................................................................................8-28.1.2 Description of Target Network..............................................................................................................8-3

8.2 Data Configuration..........................................................................................................................................8-58.2.1 Data Planning.........................................................................................................................................8-68.2.2 Presetting Data for the MSC Pool........................................................................................................8-10

8.3 Evolution of the Core Network.....................................................................................................................8-108.3.1 Overview..............................................................................................................................................8-118.3.2 Adding MSC Server 2 to the MSC Pool..............................................................................................8-118.3.3 Adding MGW 2 to the MSC Pool........................................................................................................8-148.3.4 Adding MSC Server 3 to the MSC Pool..............................................................................................8-178.3.5 Adding MGW 3 to the MSC Pool........................................................................................................8-22

8.4 Access of the Access Network......................................................................................................................8-278.4.1 Connecting RNC 1 to MSC Server 1 in the MSC Pool.......................................................................8-278.4.2 Connecting RNC 1 to MSC Server 2 in the MSC Pool.......................................................................8-298.4.3 Connecting RNC 1 to MSC Server 3 in the MSC Pool.......................................................................8-318.4.4 Adding RNC 2 to the MSC Pool..........................................................................................................8-328.4.5 Adding RNC 3 to the MSC Pool .........................................................................................................8-328.4.6 Adding RNC 4 to the MSC Pool..........................................................................................................8-32


9 Routine Maintenance................................................................................................................9-19.1 Setting the Attribute Parameters of an MSC Pool...........................................................................................9-2

9.1.1 Description of the MSC Pool Attribute Parameters...............................................................................9-29.1.2 Reviewing the Attribute Parameters of an MSC Pool............................................................................9-59.1.3 Adding NRI for an MSC Pool................................................................................................................9-79.1.4 Setting the Mapping Between the NRI and the CN ID..........................................................................9-89.1.5 Setting NRI Length and Null NRI........................................................................................................9-109.1.6 Setting the Parameters Relating to Load Balancing of the MSC Pool.................................................9-119.1.7 Setting the Non-broadcast LAI of the MSC Pool................................................................................9-139.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-159.2.1 Checking the Fault Alarms of the MSC Pool.......................................................................................9-159.2.2 Checking the Event Alarms of the MSC Pool......................................................................................9-18

9.3 Monitoring MSC Pool Load in Real Time....................................................................................................9-19

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual Contents


iii

9.3.1 Setting the Real-Time Monitoring of the MSC Pool...........................................................................9-209.3.2 Counters of MSC Pool Real-time Monitoring.....................................................................................9-22

9.4 Reviewing the MSC Server which Is Serving the Specified Subscriber.......................................................9-229.5 Querying the Performance Report of the MSC Pool.....................................................................................9-249.6 Manual Migration of Subscribers..................................................................................................................9-269.7 Auditing MSC Pool Data..............................................................................................................................9-30

9.7.1 Reviewing the Result of an MSC Pool Data Check.............................................................................9-309.7.2 Manually Checking MSC Pool Data....................................................................................................9-339.7.3 Synchronizing MSC Pool Data............................................................................................................9-36

10 MSC Pool Performance Metrics Reference.......................................................................10-110.1 Total Traffic in MSC Pool..........................................................................................................................10-410.2 Incoming/Outgoing MSC Pool Traffic.......................................................................................................10-510.3 Handover to and Out of the MSC Pool.......................................................................................................10-610.4 All VLR Subscribers in the MSC Pool.......................................................................................................10-710.5 Success Paging Rate (Traffic Measurement For MTC SUCC Rate)..........................................................10-710.6 LAI In the MSC Pool..................................................................................................................................10-810.7 GSM Call Drop...........................................................................................................................................10-910.8 UMTS Call Drop.........................................................................................................................................10-910.9 MSC Pool Traffic Measurement Of GSM Assignment............................................................................10-1010.10 MSC Pool Traffic Measurement Of WCDMA Assignment...................................................................10-1010.11 Success SMS Rate...................................................................................................................................10-1010.12 Traffic Measurement For LOC Up..........................................................................................................10-11

Index.................................................................................................................................................i-1

ContentsHUAWEI MSOFTX3000 Mobile Softswitch Center


iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-04-10)

Figures

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

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual Figures


v

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

FiguresHUAWEI MSOFTX3000 Mobile Softswitch Center


vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-04-10)

Tables

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

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual Tables


vii

About This Document

PurposeThis manual describes the concepts, working principle, signaling networking, network planning,2G network evolving to MSC Pool, new MSC Pool in 2G network, routine maintenance, andperformance metrics reference of the MSC Pool feature of the Huawei MSOFTX3000 MobileSoftSwitch Center (hereinafter referred to as MSOFTX3000).

Related VersionsThe following table lists the product versions related to this document.

Product Name Version

MSOFTX3000 V100R006C05

Intended AudienceThis document is intended for:

l Marketing technical engineers

l Telecommunications management staff

l Mobile network maintenance engineers

OrganizationThis document consists of 10 chapters and is organized as follows.

Chapter Description

1 Overview This chapter describes the concepts and working principle of theMSC Pool feature.

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual About This Document


1

Chapter Description

2 NetworkingDescription

This chapter describes the signaling networking of the MSCPool.

3 MSC Pool NetworkPlanning

This chapter describes the network planning principles andsystem specifications of the MSC Pool.

4 Commands andParameters Related toMSC Pool

This chapter describes the commands, parameters, and softwareparameters about the MSC Pool feature.

5 New MSC Pool in the2G Network

This chapter describes the data planning and data configurationprocess of a new MSC Pool in a 2G network.

6 2G Network Evolutionto Support MSC Pool

This chapter describes the data planning and data configurationprocess of a 2G network evolving to an MSC Pool network.

7 New MSC Pool in the3G Network

This chapter describes the data planning and data configurationprocess of a new MSC Pool in a 3G network.

8 3G Network Evolutionto Support MSC Pool

This chapter describes the data planning and data configurationprocess of a 3G network evolving to an MSC Pool network.

9 Routine Maintenance This chapter describes the routine maintenance operations of theMSC Pool, including setting the attributes of an MSC Pool,checking the alarms of an MSC Pool, monitoring the MSC Poolload in real time, querying the performance report of the MSCPool, manual redistribution of subscribers, and checking MSCPool data.

10 MSC PoolPerformance MetricsReference

This chapter describes the commonly used KPI for use with theMSC Pool networking feature.

Conventions

Symbol ConventionsThe following symbols may be found in this document. They are defined as follows.

Symbol Description

DANGERIndicates a hazard with a high level of risk which, if notavoided, will result in death or serious injury.

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

About This DocumentHUAWEI MSOFTX3000 Mobile Softswitch Center


2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-04-10)

Symbol Description

CAUTIONIndicates a potentially hazardous situation that, if notavoided, could cause equipment damage, data loss, andperformance degradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or saveyour time.

NOTE Provides additional information to emphasize orsupplement important points of the main text.

General ConventionsConvention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in boldface. Forexample, log in as user root.

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

Command ConventionsConvention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[ ] Items (keywords or arguments) in square brackets [ ] areoptional.

{ x | y | ... } Alternative items are grouped in braces and separated byvertical bars. One is selected.

[ x | y | ... ] Optional alternative items are grouped in square bracketsand separated by vertical bars. One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated byvertical bars. A minimum of one or a maximum of all canbe selected.

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual About This Document


3

GUI Conventions

Convention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titles are inboldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">" signs. Forexample, 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 thethree keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keysshould 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 withoutmoving the pointer.

Drag Press and hold the primary mouse button and move the pointer to a certainposition.

Update HistoryUpdates between document versions are cumulative. Therefore, the latest document versioncontains 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.

About This DocumentHUAWEI MSOFTX3000 Mobile Softswitch Center


4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-04-10)

1 Overview

About This Chapter

This section describes the concepts and working principle of the MSC Pool feature.

1.1 IntroductionThis section describes the background information of the MSC Pool feature.

1.2 ConceptThis section describes the common concepts used in the MSC Pool feature.

1.3 Technical PrincipleThis section describes the principles related to the MSC Pool feature, including the principle ofthe 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, andcharging.

1.4 M2000 Application in the MSC PoolThis section describes the application of the M2000 in the MSC Pool feature.

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual 1 Overview


1-1

1.1 IntroductionThis 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 MSCPool networking mode, one RNC/BSC can be connected to multiple MSCs. Compared with thetraditional 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 ofresources of the core network and saves investment on equipment.

l Data can be backed up amongst the MSCs to make the MSC pool more disaster tolerantand improve the reliability of the network.

l Inter-MSC location update times and signaling traffic on the C/D interface are reduced.

l Inter-MSC handovers are reduced and subscribers' conversation quality is improved.

1.2 ConceptThis section describes the common concepts used in the MSC Pool feature.

MSC Pool and MSC Pool AreaAs shown in Figure 1-1, a group of MSCs comprise an MSC Pool. The area served by an MSCPool 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 MSCPool 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

MSC2MSC1

RNC1/BSC1

RNC2/BSC2

RNC3/BSC3

MSC Pool

MSC Pool area

RNC/BSC Outside the MSC Pool AreaThe 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 Figure1-2.

1 OverviewHUAWEI MSOFTX3000 Mobile Softswitch Center


1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-04-10)

Figure 1-2 RNC/BSCs outside MSC Pool area

MSC2MSC1

RNC1/BSC1

RNC2/BSC2

RNC3/BSC3

MSC Pool

MSC Pool area

RNC4/BSC4

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 allocatesa TMSI containing the local NRI for the MS/UE. When the MS/UE initiates a service again, theNRI is contained in the service initiation request message. The RNC/BSC routes the service tothe MSC based on the contained NRI. In this way, each service initiated by the MS/UE in theMSC Pool area can be routed to the corresponding MSC with which the MS/UE registered. Inthis case, when an MS/UE roams within the MSC Pool area, the serving MSC need not bechanged. Compared with traditional networking, the number of location update signalingmessages 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 Poolfeature, each MSC Pool member must be assigned at least one NRI value with a length differentfrom zero. If the NRI length is zero, the MSC does not assign any NRI values to the TMSI andthe 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 subscribercapacity in an MSC can be increased by assigning a new additional NRI value to the MSC. AllNRI 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 registeredin an MSC. The TMSI is used to increase subscriber confidentiality by avoiding sending theInternational Mobile Subscriber Identity (IMSI) on the air interface. Once a TMSI has beenassigned 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 23–14. The NRI isdefined with a length and with a corresponding set of values. The NRI length has a range of 0to 10 bits. For example, if the NRI has a length of 10 bits, it occupies bits 23–14 (including bit23 and bit 14) of the TMSI.



1-3

The implementation of the MSC Pool function depends on the TMSI reallocation functionenabled by the MSC in the MSC Pool, including the allocation of TMSI during location updateand the allocation of TMSI during service access.

Figure 1-3 Structure of the TMSI

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 ... 0

CS/PS VLRrestart NRI range

Bits 31-30 CS/PS service indicator

Bit 29 VLR restart count

Bits 23-n (n≥14) NRI

Other bits User IDs

Null NRI

It is a special NRI. This NRI is encoded with common NRIs on a unified basis. During subscribermigration, 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 subscribermigration, it is used to trigger the MS/UE to perform location update immediately aftercompleting the current service procedure. In addition, the Non-broadcast LAI can be used toidentify each MSC in an MSC Pool. For details about the function of the non-broadcast LAI insubscriber migration, see Principle.

Each MSC in the MSC Pool has a unique Non-broadcast LAI. Each MSC in an MSC Pool mustbe configured with the Non-broadcast LAIs of other MSCs in the MSC Pool because the targetMSC determines the address of original MSC serving the MS/UE based on the Non-broadcastLAI and obtains the subscriber information (subscriber's IMSI and unused encryptionparameters) 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 asthe MSC server in an MSC Pool. The MSC server is also called Server or SoftSwitch (SX). Inthe following context, unless otherwise specified, the name Server or SX refers to the MSCserver.

Virtual MGW

One MGW is managed by one MSC server. One MGW can be divided into many virtual MGWswhich are managed by different MSC servers.




Issue 02 (2008-04-10)

Iu-FlexIntra-domain connection of RAN nodes to multiple CN nodes (Iu-Flex) indicates that one RANnode can be connected to multiple CN nodes in the same CS/PS domain. Iu-Flex function hasthe 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.

l The service area of a single CN node is enlarged, this can:l – 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.

Iu–Flex and the MSC Pool comply with the same protocols. Different from the Iu-Flex, the MSCPool is used in the CS domain of the CN.

Using MGW to Provide the A-FLEX FunctionWhen the MSC Pool networking mode is applied to the present network, you need to upgradeBSCs 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 toupgrade 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 theMSC Pool without upgrade. For details, see 1.3.8 A-Flex Function Proxy on the MGW.

Default MSCWhen a subscriber roams out of the MSC Pool area and registers with an MSC outside the MSCPool, the MSC outside the MSC Pool obtains the subscriber information from the original MSCwhere the subscriber is registered. In this case, the MSC outside the MSC Pool should be ableto identify the subscriber's original MSC address based on the original LAI of the subscriberand the NRI in the TMSI (because an LA in an MSC Pool area is served by all the MSCs in theMSC Pool, the subscriber's original MSC can not be identified through the LAI only). In thiscase, the MSC outside the MSC Pool should configure the mapping relations between LAIs andNRIs 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.

l MSCs outside the MSC Pool should obtain the planning of NRIs in the MSC Pool and youneed configure large amount of data.

To solve this problem, the concept of a default MSC is adopted in the MSC Pool standardsdefinition.

An MSC outside the MSC Pool identifies the default MSC based on the original LAI of thesubscriber. The default MSC identifies the originally registered MSC according to the NRI in



1-5

the TMSI (the mapping between NRIs of all MSCs in the Pool and corresponding MSC addressesneeds be configured in the default MSC) and transfers the subscriber information between MSCsoutside the MSC Pool and the originally registered-to MSC.

Call Termination RecoveryWhen 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 onlyafter they update their Location Area Code to the HLR or are registered in other valid MSCs inthe MSC Pool by originating calls.

When the failed MSC recovers, it needs to initiate paging in the whole network to obtainsubscriber information because it does not contain the LAIs of subscribers. In MSC Poolnetworking mode, whole network paging is not initiated usually because the MSC Pool area isvery large. This may also cause call termination failure.

To solve these problems, some special signaling processing is required during an MSC failurein the pool, which is called Call Termination Recovery. For details, see Call TerminationRecovery Principle.

CN-IDIt is the ID of an MSC node. A CN-ID uniquely identifies an MSC in the MSC Pool.

1.3 Technical PrincipleThis section describes the principles related to the MSC Pool feature, including the principle ofthe 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, andcharging.

1.3.1 Load BalancingThis section describes the basic principle of the load balancing.

1.3.2 HandoverThis section describes the principle of handover in MSC Pool feature.

1.3.3 Disaster ToleranceThis section describes the principle of disaster tolerance in MSC Pool feature.

1.3.4 Paging ControlThis section describes the principle of the paging control in MSC Pool feature.

1.3.5 Location Update with Gs InterfaceThis section describes location update with Gs interface.

1.3.6 Subscriber Migration Between MSCsThis section describes the principle of subscriber migration in MSC Pool feature.

1.3.7 Load Balancing at the MGWThis section describes the principle of MGW load balancing in MSC Pool feature.

1.3.8 A-Flex Function Proxy on the MGWThis 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 InterfaceThis section describes the principle of MGW managing circuits of the A interface.




Issue 02 (2008-04-10)

1.3.10 Charging PrincipleThis section describes the principle of charging in MSC Pool feature.

1.3.1 Load BalancingThis 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 toselect an MSC for the service. The function which selects a serving MSC for an MS/UE is calledthe NAS node selection function (NNSF).

l When an MS/UE initiates a service based on IMSI/IMEI, the RNC/BSC follows theprinciple of load balancing. It selects a valid MSC to serve the MS/UE according to theproportion of subscriber capacity of each valid MSC in the MSC Pool. When the MS/UEinitiates a service using the IMSI/IMEI, the selected MSC allocates a TMSI containing theNRI of the MSC for the MS/UE.

Figure 1-4 Load balancing

MSC2MSC1

RNC1/BSC1

RNC2/BSC2

RNC3/BSC3

MSC Pool

MSC Pool areaMS/UEMS/UE

MS/UE

l When an MS/UE initiates a service using a TMSI, the RNC/BSC selects a serving MSCfor 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, theRNC/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. Theselected MSC allocates a TMSI containing the NRI of the MSC for the MS/UE.

l When the MSC sends a paging message to the called MS/UE, the RNC/BSC temporarilystores 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 anMSC 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 betweenthe temporarily stored IMSI and the MSC. In this case, the paging response can be sent tothe MSC sending the paging message, and the call can be connected successfully. Whenthe selected MSC is invalid or an MSC cannot be selected according to the mapping, the



1-7

RNC/BSC follows the principle of load balancing to select a valid MSC, as shown in Figure1-4.

NOTE

l When the RNC/BSC detects that the signaling point of the MSC is inaccessible, the RNC/BSC considersthe MSC to be faulty or invalid.

l The proportion of subscriber capacity of MSCs needs to be configured statically on the RNC/BSCconnected with the MSCs. In addition, the MSCs can notify the RNC/BSC of the proportion ofsubscriber capacity regularly, and the RNC/BSC dynamically adjusts the proportion of subscribercapacity 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 areHuawei equipment. For other modes, the RNC/BSC can only configure the subscriber capacity ofMSCs statically.

l 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/BSCsoutside the MSC Pool, the subscriber capacity reserved for these RNCs/BSCs needs to be subtractedfrom the total capacity as for calculation of subscriber capacity of the MSC.

1.3.2 HandoverThis 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 handoveris performed for the MS/UE that moves in the MSC Pool area during conversation. (Comparedwith traditional networking, the number of inter-MSC handovers can be reduced, and the qualityof 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 duringhandover. To avoid concentration of inter-MSC handover work load on one pooled MSC andreduce the impact of MSC single-point failure, the handover targets MSCs for outside MSCmust 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 Poolarea can shift to an adjacent MSC outside the MSC Pool area during handover. In this case, theadjacent MSC is set to the destination MSC of MSCs in the MSC Pool during handover (it isthe same as the handover configuration for the MSC on the present network).

1.3.3 Disaster ToleranceThis 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 thedisaster 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 validMSC in this MSC Pool, thus implementing the disaster tolerance between MSCs in the MSCPool.




Issue 02 (2008-04-10)

For Call Origination

When an MSC in the MSC Pool is invalid due to failure, the service requests initiated bysubscribers in the MSC are routed to other valid MSCs (new MSCs) through the load-balancingalgorithm. 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 locationof the MS/UE to register the MS/UE in the MSC and allocates a TMSI containing the NRIof the MSC for the MS/UE.

l In the case that a subscriber initiates a call, the new MSC indicates that the MS/UE is anunknown subscriber. In this case, the MS/UE registers with a valid MSC in the MSC Pool.

l If implicit location update is allowed, the new MSC updates the location of the MS/UE onan implicit basis (location update to the HLR on interface C/D) to register the MS/UE inthe MSC. Then, the MSC allocates a TMSI containing the NRI of the MSC for the MS/UEand 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 thiscase, subscribers registered in that MSC cannot be called. The subscribers can be called onlyafter they update their locations or are registered in other valid MSCs in the MSC Pool byoriginating calls.

Figure 1-5 MSC failure in the MSC Pool

MSC 2MSC1

MSC Pool

STP

MSC3

HLR

When the faulty MSC recovers, it needs to initiate paging in the whole network to obtainsubscriber information because it does not contain LAIs of subscribers. In MSC Pool networkingmode, 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 thenetworking and principle of the solution to call termination failure.



1-9

Call Termination Recovery NetworkingThe system supports two networking solutions, that is, chain backup networking and centralizedbackup networking.

l Centralized backup networking

Figure 1-6 Centralized backup networking

MSC 2/VLR2

MSC1/VLR1

MSC Pool

STP

MSC3/VLR3

HLR

MSC4/VLR4

In this mode, a dedicated centralized standby MSC/VLR is used. The centralized standbyMSC/VLR is responsible for recovering call termination only. It does not process any otherservice.

l Chain backup networking

Figure 1-7 Chain backup networking

MSC 2/VLR2

MSC1/VLR1

MSC Pool

STP

MSC3/VLR3

HLR




Issue 02 (2008-04-10)

There is not a dedicated backup MSC/VLR in this mode. Each MSC/VLR in the MSC Poolis 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 PrincipleWhen an MSC in the MSC Pool fails, the following functions need to be enabled to recover calltermination:

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.

l 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

MSC1(AA)

MSC Pool

STP

MSC2(BB, AA)

HLR

When MSC2 serves as the standby MSC of MSC1, two routes need to be configuredon the STP: Set the direct route between STP and signaling point AA of MSC1 to aroute with higher priority and the bypass route between STP and AA through signalingpoint BB of MSC2 to a route with lower priority. In addition, the addressing mode ofSTP and MSCs in the MSC Pool must be set to DPC addressing. Signaling point BBmust 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 STPare sent to MSC1 through the direct route with higher priority. When MSC1 fails, thesignaling messages are sent to MSC2 through the bypass route. Because signaling pointBB on MSC2 is the mutual-aid signaling point of signaling point AA, the signalingmessages are processed on MSC2.

NOTE

If the local HLR is directly connected with the MSC, a standby route must be configured on theHLR. This configuration is the same as the STP mode in processing logic.



1-11

– Back up PRN signaling messages through load balancing of SCCP signaling points, asshown in Figure 1-9.

Figure 1-9 Back up PRN signaling messages through load balancing of SCCP signalingpoints

MSC1(AA, GT1)

MSC Pool

STP

MSC2(BB)

HLR

Plan the data on the STP as follows:Set the addressing mode of GT1 to AA+SSN and set signaling point BB to an SCCPload-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 withhigher priority (that is, MSC1) normally. When MSC1 fails, the signaling messages aresent to the load-balancing signaling point BB with lower priority (that is, MSC2). Thesignaling messages are then processed on MSC2.

NOTE

If the local HLR is directly connected to the MSC, GT must be configured on the HLR. Thisconfiguration is the same as the STP mode in processing logic.

l Backing up subscriber data




Issue 02 (2008-04-10)

Figure 1-10 Backing up subscriber data

MSC1/VLR1

MSC Pool

STP

MSC2/VLR2

HLR

Backup

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 thestandby 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 activeMSC for the backup of subscriber data in the VLR.

l In the case of networking based on routing priority, the standby MSC cannot serve as anSTP.

l Only Phase 2 and later versions of MAP are supported.

Call Termination Recovery FlowMSC2 (standby MSC) receives a PRN message sent by the HLR to the MSC1 (active MSC). Ifthe VLR in MSC2 does not have subscriber data, MSC2 retrieves the subscriber's LAI andsubscriber status from the standby VLR. Then MSC2 sends a paging message to the switched-on MS/UE once only (it terminates the call directly for switched-off MS/UE) and terminates thecall. The call is terminated without waiting for paging response message because the pagingresponse 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 thesubscriber data is in the local VLR. If no subscriber data is found, the MSC updates the locationof the MS/UE on an implicit basis. Then, the MS/UE can register with the MSC. The MSC alsoallocates 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 LAIof the subscriber and subscriber status from the standby VLR. Then it updates the location ofthe subscriber on an implicit basis and allocates an MSRN for the MS/UE. After a call is routedin the incoming direction, MSC1 follows the normal call termination procedure to page the calledMS/UE.



1-13

1.3.4 Paging ControlThis 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 beas 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 thepaging 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 InterfaceThis section describes location update with Gs interface.

When an MS/UE sends cooperation location update request to an MSC in the MSC Pool throughthe Gs interface, the MSC allocates the TMSI containing the local NRI to the MS/UE. In thiscase, when the MS/UE initiates the CS service, the system can route the service to the originallyregistered MSC of this MS/UE.

When the MSC addresses the called MS/UE based on the IMSI through the Gs interface, thepaging message contains the Global CN-ID. This ensures that the paging response is routed tothe MSC that initiated the paging.

1.3.6 Subscriber Migration Between MSCsThis section describes the principle of subscriber migration in MSC Pool feature.

PrincipleOperation center staff may trigger subscriber migration between MSCs in the MSC Pool throughO&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 inthis MSC to other MSCs in the MSC Pool before upgrade. After the upgrade is completed, themaintenance engineers transfer the subscriber data in other MSCs of the MSC Pool back to theupgraded MSC, as shown in Figure 1-11.




Issue 02 (2008-04-10)

Figure 1-11 Subscriber migration between MSCs

MSC2MSC1

RNC1/BSC1

RNC2/BSC2

RNC3/BSC3

MSC Pool

MSC Pool area

O&M

MS/UE

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.

l 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

l Configure the status of MSC on MSCs and RNC/BSCs (set the status of the MSC fromwhich subscribers are to be transited to off-load).

l When an MS/UE which registered in the off-load MSC initiates a service, the MSCallocates 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.

l 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 differsfrom the LAI broadcasted by the RNC/BSC serving the MS/UE).

l Upon receiving a location update message containing null-NRI from the MS/UE, theRNC/BSC selects a valid MSC according to the proportion of subscriber capacity ofvalid MSCs in the MSC Pool (not including the off-load MSC) and routes the serviceto the selected MSC. The selected MSC registers the MS/UE and allocates a TMSIcontaining its NRI for the MS/UE. During registration, the selected MSC determinesthe original MSC where the MS/UE is registered according to the Non-broadcast LAIcarried by the MS/UE and obtains subscriber data (IMSI and unused encryptionparameters) from the original MSC. In this way, an MS/UE is transferred from one MSCto another.

l After migration is completed, stop migration through the O&M command and restorethe MSC status on the MSCs and RNC/BSCs.

2. Inter-office E interface redirection mode



1-15

l Configure the status of MSC on MSCs and RNC/BSCs (set the status of the MSC fromwhich subscribers are to be transited to off-load).

l When an MS/UE registered in the off-load MSC initiates a location update request orservice release request, the MSC initiates the location update request to the target MSCbased on the redirection message.

l Upon receiving a location update request, the target MSC encrypts the authentication,obtains the ID, checkimei, and TMSI reallocation information from the MS/UE, andthen sends the information to the originating MSC. The originating MSC interacts withthe MS/UE. The target MSC initiates the location update to the HLR and allocates aTMSI containing the NRI of the target MSC for the MS/UE. Thus, the subsequentlocation 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.

l After migration is completed, stop migration through the O&M command and restorethe MSC status on MSCs and RNC/BSCs.

CAUTIONl 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 MSCPool area are all Huawei equipment.

l 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, theoriginating MSC is set to the off-load status. The disabled status is used for isolating orupgrading MSCs in the MSC Pool. The RNC/BSC does not send any service data to a disabledMSC.

l Control for the migration speed: To avoid link congestion due to quick migration, the MSCfrom which subscribers are transited can control the migration speed. The migration speedfalls into three types: high speed (migration is completed within one to two cycles of locationupdate), 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).

l Migration involves multiple network elements (NEs) in the MSC Pool. To facilitateoperation, Huawei provides unified migration on the M2000, which can also monitor themigration process. The M2000 can monitor whether subscriber migration in the MSCs in theMSC Pool are completed.

Subscriber migration between MSCs has the following limitations:

l The RNCs/BSCs outside the MSC Pool area are connected to only one MSC in the MSCPool. Therefore, subscribers in the service area of an RNC/BSC outside the MSC Pool areacannot be redistributed between the MSCs in the MSC Pool.

l Subscribers who are in the progress of combined location updates cannot be redistributedbetween MSCs in the MSC Pool.

l Mobile phones of certain models do not support the 3GPP TS 23.236. To redistribute thesubscribers who use these mobile phones, you must enable the inter-office redirectionfunction.

l Subscribers who are in the progress of emergency calls cannot be redistributed betweenthe MSCs in the MSC Pool. This is because emergency calls do not require authentication,




Issue 02 (2008-04-10)

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 inprogress. In this case, you can determine whether the redistribution is complete and proceedwith the next step.

l The E interface redirection must be based on Phase 2 and later versions of MAP.

Application ScenariosSubscriber migration between MSCs in the MSC Pool can be applied in the following scenarios:

l Transferring all subscribersBefore upgrading one or more MSCs in the MSC Pool, you need to transfer all thesubscribers in the MSC or MSCs to other MSCs in the MSC Pool to avoid impact onsubscriber services.

l Transferring part of subscribersIn the example above, after the MSC or MSCs are upgraded, need to transfer part ofsubscribers from other MSCs back to the upgraded MSC or MSCs.You must specify the number of subscribers or the proportion (to the current registeredsubscribers) of subscribers to be transited. When the number of transited subscribersreaches the specified number or proportion, the migration is stopped automatically.

l Transiting subscribers in the specified RNC/BSCTo avoid impact on subscriber services in the RNC/BSC when the RNC/BSC in MSC Pool1 is to be taken over by MSC Pool 2, connect the RNC/BSC to MSC Pool 2 (all the MSCsin the RNC/BSC, MSC Pool 1 and MSC Pool 2 actually form a new pool) and transitsubscribers 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.

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

l Transiting specified subscribersTo conduct the dialing test, you need to transit subscribers registered in MSC1 in the MSCPool to MSC2.Through O&M configuration, an MSC can transit specified subscribers based on theMSISDNs and IMSI numbers. The system supports migration of up to 10 subscribers atthe same time.

CAUTIONIn the above scenarios, subscribers can be transited to one or more MSC in the MSC Pool.

1.3.7 Load Balancing at the MGWThis section describes the principle of MGW load balancing in MSC Pool feature.



1-17

Selecting MGW Based on Load BalancingWhen an MSC server controls multiple MGWs which are connected to the same RNC/BSC, theMSC server selects an MGW for a subscriber who initiates a service request in the RNC/BSCarea based on load balancing.

1. For a 2G subscriber: The MSC server selects an MGW based on the ratio of the staticallyconfigured 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 isstatically configured on the MGW.

Preferred MGWFor intra-MSC calls in the MSC Pool, if one MGW serves the calling party and the called partysimultaneously, the system selects the same MGW as a preferred MGW to establish the call toavoid 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 partysimultaneously (two VMGWs of a physical MGW serve the calling party and called party), theoriginating and terminating MSCs select the same MGW as a preferred physical MGW toestablish the call to avoid using too many voice circuits between MGWs.

1.3.8 A-Flex Function Proxy on the MGWThis section describes the principle of A-Flex function proxy on the MGW in MSC Pool feature.

BackgroundThe 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 sharethe load of subscriber services.)

When the MSC Pool networking mode is applied to the present network, you need to upgradeBSCs 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 toupgrade 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 theMSC Pool without upgrade.

Implementation PrincipleA BSC on the present network can connect with one MSC server (a signaling point) only. Toenable the BSC to access the MSC Pool without being upgraded (connect multiple signalingpoints), the MGW must shield different MSC servers for the BSC. The MGW needs to providethe BSC with a unified signaling point. To achieve this purpose, the following two signalingnetworking modes can be used: M3UA agent networking and M3UA forward networking, asshown in Figure 1-12 and Figure 1-13. In addition, the networking of using MGW to providethe A-flex function can coexist with the networking of using RNC/BSC to provide the Iu/A-flexfunction.

1. 3UA agent networking




Issue 02 (2008-04-10)

Figure 1-12 A-Flex function proxy on the MGW (M3UA agent networking)

MSOFTX3000 A

MGW1

BSC1 BSC2 BSC3

MSOFTX3000 B

MGW2AA AA

AA,XX AA,YY

BSC3

l MSC servers in the MSC Pool establish signaling connections with BSCs through thesame signaling point code AA (signaling point codes XX and YY are used to establishsignaling connections with NEs of the core network).

l The MGW adopts the M3UA agent mode. It shares the same signaling point code withMSC servers, that is, AA.

l The MGW is divided into several virtual MGWs whose numbers are the same as thoseof the MSC servers. Each VMGW is registered in an MSC server. Allocation ofVMGWs is invisible to BSCs.

l 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 betweenthe BSC and the MGW over TDM). When a BSC is connected with multiple physicalMGWs, the BSC selects different MGW to set up signaling links based on the linkbalancing principle. The MSC server selects a preferred MGW to set up the voicechannel based on the load balancing principle.

l The signaling point configured on the BSC to interwork with the MSC server is AA.

l Using the MGW to provide the A-flex function: After resolving the IMSI/IMEI fromthe subscriber message or the TMSI from the NRI, the MGW routes the subscribermessage to the corresponding MSC server based on the IMSI/IMEI or NRI. Thealgorithm for the MGW to select the MSC server is the same as that for the BSC toimplement the A-flex function.

2. M3UA forward networking



1-19

Figure 1-13 A-Flex function proxy on the MGW (M3UA forward networking)MSOFTX3000 A

MGW1

BSC1 BSC2 BSC3

MSOFTX3000 B

MGW2AA,DD AA,EE

BB,XX CC,YY

BSC3

l MSC servers in the MSC Pool establish signaling connections with BSCs throughsignaling point codes BB and CC.

l The MGW adopts the M3UA signaling forward mode. It uses signaling points DD andEE for MSC servers and the same singling point AA for BSCs.

l The MGW is divided into several VMGWs whose numbers are the same as those ofMSC servers. Each VMGW is registered in an MSC server. Allocation of VMGWs isinvisible to BSCs.

l 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 betweenthe BSC and the MGW over TDM). When a BSC is connected with multiple physicalMGWs, the BSC selects different MGW to set up signaling links based on the linkbalancing principle. The MSC server selects a preferred MGW to set up the voicechannel based on the load balancing principle.

l The signaling point configured on the BSC to interwork with the MSC server is AA.

l Using the MGW to provide the A-flex function: After resolving the IMSI/IMEI fromthe subscriber message or the TMSI from the NRI, the MGW routes the subscribermessage to the corresponding MSC server based on the IMSI/IMEI or NRI. Thealgorithm for the MGW to select the MSC server is the same as that for the BSC toimplement the A-flex function.

In addition, the networking of using MGW to provide the A-flex function can coexist with thenetworking of using RNC/BSC to provide the Iu/A-flex function, as shown in Figure 1-14 andFigure 1-15.




Issue 02 (2008-04-10)

Figure 1-14 Mixed networking of A-Flex function proxy on MGW and Iu/A-Flex function proxyon the RNC/BSC (1)

MSOFTX3000 A

MGW1

BSC1 BSC2 BSC3 RNC1

MSOFTX3000 B

MGW2AA,DD AA,EE

AA,BB,XX AA,CC,YY

l MSC servers use multiple signaling points for BSCs on the access network. Signaling pointAA 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 theIu/A-Flex function. Signaling points XX and YY are used for HLR and STP.

l The MGW uses the same signaling point (AA) to connect with the BSCs that do not supportthe A-Flex function. The MGW also uses different signaling points (DD and EE) to connectwith the BSCs that support the Lu/A-Flex function. It decides whether to enable the A-Flexfunction according to configuration of signaling points at the access network.

l The MGW connects with the BSCs that do not support the A-Flex function through theM3UA signaling agent mode and M3UA signaling forward mode. The MGW connectswith 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 proxyon the RNC/BSC (2)

MSOFTX3000 A

MGW1

BSC1 BSC2 BSC3 RNC1

MSOFTX3000 B

MGW2AA EE

AA,BB,XX AA,CC,YY



1-21

l MSC servers use multiple signaling points for BSCs on the access network. Signaling pointAA 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 theIu/A-Flex function. Signaling points XX and YY are used for HLR and STP.

l MGW1 only connects with the BSC that does not support the A-Flex function. It enablesthe A-Flex agent function.

l MGW2 only connects with the RNC that supports the Iu-Flex function. It implementssignaling transfer only.

Networking SuggestionIt is recommended to use M3UA forward mode first for networking of A-Flex function proxyon MGW.

The M3UA forward mode is better than the M3UA agent mode in the case of mixed networkingmode. For example, Figure 1-16 the mixed networking in the M3UA agent mode, and Figure1-14 shows the mixed networking in the M3UA forward mode. For the former, two sets ofsignaling point need be configured and two sets of independent M3UA data configuration onMSC servers are required, which obviously complicates networking. Therefore, use the M3UAforward 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 ofsignaling points is limited.

Figure 1-16 Mixed networking of MGW used for providing A-Flex function and RNC/BSCproviding Iu/A-Flex function (M3UA forward networking)

MSOFTX3000 A

MGW1

BSC1 BSC2 BSC3 RNC1

MSOFTX3000 B

MGW2AA,DD AA,EE

BB,XX CC,YY

1.3.9 MGW Managing Circuits of the A InterfaceThis 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 networkingmode, the A-interface circuits of one BSC are managed by multiple MSC servers. This designcauses inconvenience on resource utilization and maintenance. To solve this problem, A-interface circuits need to be shared among MSC servers. In this case, the circuits need to bemanaged by the MGW, as shown in Figure 1-17 and Figure 1-18.




Issue 02 (2008-04-10)

1. In the MSC Pool networking, the following problems occur when MSC servers manage A-interface circuits.

Figure 1-17 MSC server managing A-interface circuits

MSOFTX3000 A

MGW1

BSC1

MSOFTX3000 B

l After the MSC Pool is formed, A-interface circuits are used less efficiently. The A-interface TDM circuits of a BSC originally managed by one MSC server are managedby different MSC servers. Each MSC server use resources allocated for it, whichdegrades the re-use efficiency for A-interface circuits. To support the traffic beforeBSCs access the MSC Pool, A-interface TDM circuits need to be added.

l 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 vehicleallocated for each subsidiary, the vehicles of some subsidiaries may not meet demandswhereas the vehicles of some subsidiaries may be idle.

l 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 theMSC servers in the MSC Pool must be planned and adjusted again.

l After the MSC Pool is formed, it is complicated to maintain A-interface circuits on aroutine basis. When blocking a circuit, the operator must find the MSC server thatmanages 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.

2. Solution to management of A-interface circuits



1-23

Figure 1-18 MGW managing A-interface circuits

MSOFTX3000 A

MGW1

BSC1

MSOFTX3000 B

l MSC servers do not configure or manage A-interface circuits. The MGW is responsiblefor configuring and managing A-interface circuits. The data of signaling and A-interfacetrunks from the MSC servers to the BSCs is configured on the MSC servers forperformance measurement purposes.

l When MSC servers send A-interface circuits request to the MGW, the MGW isresponsible for distributing and managing A-interface circuits.

l Routine circuit operation & maintenance commands are transferred from the MSCserver to the MGW. The MGW is responsible for maintaining and managing A-interfacecircuits on a routine basis.

l In this way (that is, the MGW manages A-interface circuits), A-interface circuits canbe shared among MSC servers in the MSC Pool.

1.3.10 Charging PrincipleThis section describes the principle of charging in MSC Pool feature.

Charging Based on Virtual MSC IDCharging based on virtual MSC ID is to allocate an MSC ID (a physical MSC is divided intomultiple virtual MSCs based on charge areas) for each charge area (that is, LAN). When asubscriber 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. Inthis way, the system can identity the charge areas of the calling and called subscribers. As aresult, it can charge subscribers according to their charge areas, as shown in Figure 1-19.




Issue 02 (2008-04-10)

Figure 1-19 Charging based on virtual MSC ID

MSC1(MSCa, MSCb)

RNC1/BSC1

RNC2/BSC2

RNC3/BSC3

MSC Pool

MSC Pool area

MS/UE MS/UE

Charging area 1 Charging area 2

MSC2(MSCc, MSCd)

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.

l When a subscriber roams from one charging area to another, the inter-MSC location updateis required. In this case, the MSOFTX3000 must interwork with the HLR through the C/Dinterface and the virtual MSC ID on the HLR is updated.

Charging Based on Location AreaAs for charging based on location area, LAIs are filled in MOC and MTC bills generated by thelocal MSC, and the local MSC allocates MSRNs according to LAIs. In this case, the GMSC canobtain 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 intelligentsubscribers in the case of Free Roaming to Same City, the SCP needs to use the ATI processduring 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 tosave MSC IDs and simplify data configuration and planning. If the SCP and HLR do not supportthe ATI and PSI processes or the BOSS system does not support charging based on locationarea, 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 supportthe PSI process.

l One LA can belong to only one multi-area network.



1-25

l If the performance measurement and charging based on the multi-area networking are bothenabled, the area covered by the local networks for the charging must contain (or at leastlevel) the area covered by the local networks for the performance measurement.

Cross-Time ZoneWhen an MSC Pool area covers multiple time zones, MSCs in the MSC Pool can send the correcttime zones (the time zones can be accurate to LA or cell) where subscribers are located currentlyto subscribers.

1.4 M2000 Application in the MSC PoolThis section describes the application of the M2000 in the MSC Pool feature.

1.4.1 M2000 FunctionThis section describes the main functions of M2000 in MSC Pool network.

1.4.2 M2000 Application ScenarioThis section describes the application scenario of M2000.

1.4.1 M2000 FunctionThis section describes the main functions of M2000 in MSC Pool network.

In the MSC Pool networking, the M2000 supports the following:

l Parameter management related to the MSC Pool feature: It supports centralizedconfiguration and management on the parameters related to the MSC Pool feature.

l Real-time traffic monitoring with the shortest interval of 30 seconds: It supports themonitoring of the number of idle subscribers, number of power-off subscribers, totalnumber of subscribers, and CPU usage rate of the MSC server, and the context informationof the MGW, with the shortest interval of 30 seconds.

l Performance measurement for whole MSC Pool: It collects the commonly used KPI indexesat the MSC Pool level and provides the general KPI indexes for whole MSC Pool.

l Data consistency check and synchronization: It periodically checks whether the data of theNEs in the MSC Pool is consistent. If not, it generates a data synchronization script tosynchronize the data.

l Subscriber migration within the MSC Pool: It supports subscriber migration in the MSCPool. You can generate a migration task and monitor the status of the migration.




Issue 02 (2008-04-10)

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

MSOFTX3000 A

BSC1 BSC2 BSC3

MSOFTX3000 B

BSC4

MGW 1 MGW2

M2000 system

WAN/LAN

1.4.2 M2000 Application ScenarioThis section describes the application scenario of M2000.

For details, see 9 Routine Maintenance.



1-27

2 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 MGWdoes not provide the A-Flex function. For the signaling networking scheme in this case, seesection 2.1 Signaling Networking Scheme of an MSC Pool (BSC/RNC Providing the A-Flex/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 anMSC Pool (MGW Providing the A-Flex Function).

2.1 Signaling Networking Scheme of an MSC Pool (BSC/RNC Providing the A-Flex/Iu-FlexFunction)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 thecase that the MGW provides the A-Flex function.

2.3 Networking Scheme for Connecting CN NEs Inside and Outside an MSC PoolThis section describes the connection between the core network (CN) NEs inside an MSC Pooland the CN NEs outside of the MSC Pool.

2.4 Networking Scheme for Subscriber Data BackupThis section describes the networking scheme for subscriber data backup.

2.5 Networking Scheme for Voice Channels Related to an MSC PoolThis section describes the network scheme for voice channels related to an MSC Pool.

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual 2 Networking Description


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 signalingnetworking schemes of an MSC Pool are determined based on the bearer network mode on theIu/A interface between the access network and the CN.

2.1.1 TDM-Based A InterfaceThis section describes the networking scheme when the A interface between the BSC and theMGW is based on TDM.

2.1.2 ATM-Based Iu InterfaceThis section describes the networking scheme when the Iu interface between the RNC and MGWis based on ATM.

2.1.1 TDM-Based A InterfaceThis section describes the networking scheme when the A interface between the BSC and theMGW is based on TDM.

When the A interface between the BSC and the MGW is borne on TDM, the networking schemeas shown in Figure 2-1 must be adopted.

This networking scenario is as follows:

l Each BSC has a unique signaling point code (SPC).

l The TDM bearer is adopted for the interworking between the BSC and the MGW.

l The MGW has a unique SPC.

l The IP bearer is adopted for the interworking between MGWs and between the MGW andthe MSC server.

l Each MSC server has a unique SPC.

l The MTP3 data must be configured for the interworking between the BSC and the MGW.

l The M3UA data must be configured for the interworking between the MGW and the MSCserver.

l Data must be configured for transferring the signaling between the MSC server and theBSC.

2 Networking DescriptionHUAWEI MSOFTX3000 Mobile Softswitch Center



Issue 02 (2008-04-10)

Figure 2-1 MSC Pool networking adopted when the A interface between the BSC and the MGWis based on TDM

MSOFTX3000 A

MGW1

BSC1 BSC2 BSC3 BSC4

MSOFTX3000 B

MGW2

IP bearer TDM bearer

2.1.2 ATM-Based Iu InterfaceThis section describes the networking scheme when the Iu interface between the RNC and MGWis based on ATM.

When the Iu interface between the RNC and the MGW is based on ATM, the networking schemeas shown in Figure 2-2 must be adopted.

This networking scenario is as follows:

l Each RNC has a unique SPC.

l The ATM bearer is adopted for the interworking between the RNC and the MGW.

l The MGW has a unique SPC.

l The IP bearer is adopted for the interworking between the MGW and the MSC server.

l Each MSC server has a unique SPC.

l The M3UA data must be configured for the interworking between the MGW and the MSCserver.

l Data must be configured for transferring the signaling between the MSC server and theRNC.



2-3

Figure 2-2 MSC Pool networking adopted when the Iu interface between the RNC and the MGWis based on ATM

MSOFTX3000 A

MGW1

RNC1 RNC2 RNC3 RNC4

MSOFTX3000 B

MGW2

IP bearer ATM bearer

2.2 Signaling Networking Scheme of an MSC Pool (MGWProviding the A-Flex Function)

This section describes the typical signaling networking scheme adopted for an MSC Pool in thecase that the MGW provides the A-Flex function.

A BSC in the existing network can be connected to only one MSC server (a single signalingpoint). To enable the BSC to be connected to the MSC Pool (multiple MSC servers) without aneed to upgrade the BSC, the MGW must provide the BSC with a uniform signaling point sothat the BSC has no knowledge about which MSC server it is interworking with. To achieve thispurpose, the following two signaling networking modes can be used:

l M3UA agent mode

l M3UA forwarding mode

If the available signaling points are insufficient for the MSC pool to use the M3UA forwardingmode, the M3UA agent mode can be used. If the signaling points are sufficient for the M3UAforwarding mode, then this mode is preferred. For details about the networking schemes, see1.3.8 A-Flex Function Proxy on the MGW.

2.3 Networking Scheme for Connecting CN NEs Inside andOutside an MSC Pool

This section describes the connection between the core network (CN) NEs inside an MSC Pooland the CN NEs outside of the MSC Pool.

The networking scheme for connecting CN NEs inside and outside an MSC Pool is the same asthe networking scheme for connecting CN NEs without an MSC Pool except that certain changes




Issue 02 (2008-04-10)

must be made to the networking of the STP and the HLR for connecting CN NEs inside andoutside an MSC Pool.

In an MSC Pool network, to enable the restoration of the call termination, the PRN signalingmust be backed up. The backup can be implemented with the following methods:

l Configure the route priorities

l Enable load sharing of the SCCP signaling points

For details about the networking schemes, see the description related to the backup of PRNsignaling messages in Call Termination Recovery Principle. For details about theconfiguration examples, see Configuring PRN Signaling Backup Data.

2.4 Networking Scheme for Subscriber Data BackupThis section describes the networking scheme for subscriber data backup.

To enable the call termination recovery in an MSC Pool network, subscriber data must be backedup. The backup can be implemented by using the following methods:

l Centralized backupThe data configuration for the centralized backup is simple. An additional MSC, however,is required for the backup in this method.

l Chain backupThe data configuration for the chain backup is complex. MSCs in the MSC Pool can backup subscriber data for one another, thus reducing the number of MSCs.

In applications, the networking scheme must be determined based on existing network conditionsand customer requirements. For details about the networking scheme, see the related descriptionfor subscriber data backup in Call Termination Recovery Networking. For details about theconfiguration examples, see Configuring Chain Backup Data and Configuring CentralizedBackup Data.

2.5 Networking Scheme for Voice Channels Related to anMSC 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 MSCPool and voice channels between the MSC Pool and the PSTN, other PLMN, or other VMSCs.

Voice Channels in the MSC PoolVoice 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 theBSC are based on TDM bearer.

l The MGW is directly connected to the RNC. Voice channels between the MGW and theRNC are based on ATM bearer.

l Voice channels between MGWs are based on IP bearer.



2-5

Voice Channels Between the MSC Pool and the PSTN, Other PLMN, or OtherVMSCs

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 withlocal or remote MSCs through the TMSC.




Issue 02 (2008-04-10)

3 MSC Pool Network Planning

About This Chapter

This section describes the network planning principles and system specifications of the MSCPool.

3.1 LimitationsThis section describes the limitations that affect the network planning of an MSC Pool.

3.2 MSC Pool Network SpecificationsThis section describes the relevant specifications of an MSC Pool network.

3.3 General Principles of the MSC Pool PlanningThis section describes the principles of the planning of an MSC Pool network.

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual 3 MSC Pool Network Planning


3-1

3.1 LimitationsThis 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/UMTSnetworks.

l The MSC Pool feature conflicts with the dual-homing feature. You cannot have bothfeatures active.

3.2 MSC Pool Network SpecificationsThis 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 byan 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 interceptedsubscribers

If the number of interceptedsubscribers is set on all theMSCs of an MSC Pool, up to40,000 subscribers aresupported (if theinterception data isconfigured on the specifiedMSC, there is no suchrestriction).

Maximum capacity supported byan MGW

Number of virtual MGWs 32 (A MGW can beconnected to 32 MSCservers at the same time.)

Number of connectedRNCs (ATM networkingmode)

50

Number of connectedBSCs (TDM networkingmode)

50

3 MSC Pool Network PlanningHUAWEI MSOFTX3000 Mobile Softswitch Center



Issue 02 (2008-04-10)

Item Index Value

Number of connectedBSCs/RNCs (IPnetworking mode)

128

Maximum capacity supported byan RNC

Number of connectedMSC servers

32

Number of connectedMGWs (ATM networkingmode)

32

Maximum capacity supported bya BSC

Number of connectedMSC servers

32

Number of connectedMGWs (TDM networkingmode)

2

NOTE

When the centralized backup method is used for the VLR data backup solution, the maximum number ofactive 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 subscribersthat are supported by an MSC server.

Table 3-2 NRI planning reference data

Length of NRI Number of NRIs Maximum Number of Subscribers

<=6 bits 1 3,200,000

7 bits 1 1,600,000

7 bits 2 3,200,000

8 bits 1 800,000

8 bits 2 1,600,000

8 bits 3 2,400,000

8 bits 4 3,200,000

9 bits 1 400,000

9 bits 2 800,000

9 bits 3 1,200,000

9 bits 4 1,600,000

9 bits 5 2,000,000

9 bits 6 2,400,000



3-3

Length of NRI Number of NRIs Maximum Number of Subscribers

9 bits 7 2,800,000

9 bits 8 3,200,000

10 bits N 20 x N x 10,000

NOTE

The VLR on the MSC server adopts the distributed structure and is composed of multiple WVDBs (up to10 pairs). Each WVDB can support up to 500,000 TMSI numbers and 200,000 subscribers.

3.3 General Principles of the MSC Pool PlanningThis section describes the principles of the planning of an MSC Pool network.

Planning of the Target NetworkA prerequisite for building an MSC Pool is that IP transmission is adopted for connectionbetween the MSC servers and the MGWs, in a pool and also IP transmission is adopted betweenMGWs. 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 MSCsin 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 followingplanning principles are employed:

l The access networks must be connected in mesh mode for an MSC Pool networking toachieve the traffic balance and reduce the handover of the inter-MSC roaming.

l IP-based Nb interface is a basis for the MSC Pool networking. It requires that all VMSCswithin an MSC Pool adopt the softswitch architecture and the VMSCs must support thesame services and functions.

l The capacity of each MSC server within an MSC Pool is suggested to be the same. It is notrecommended that MSC servers cannot serve BSCs/RNCs which are outside the MSC Pool.

l All BSCs/RNCs must be connected to all MSC servers within an MSC Pool throughsignaling. When the BSC/RNC cannot support the A/Iu-Flex function in the preliminarystage, the A/Iu-Flex function is implemented by the MGW. For a 3G system, it isrecommended to build an MSC Pool after the implementation of the Iu-Flex function bythe RNC. In the case of non-IP-based A/Iu interface, the BSC/RNC must be connected totwo MGWs at most, unless certain special requirements are raised. Either the M3UA agentmode or M3UA forward mode can be adopted, but the M3UA agent mode is recommended.

l MSC servers within an MSC Pool should be installed in two or more physical locations toaccommodate 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.

l For signaling networking, MSC servers within an MSC Pool must be connected to puresignaling point NEs, such as the SMC, SCP, and HLR in STP forward mode. The STP mustbe directly connected to the MSC servers. The BICC trunk signaling is transmitted to theMSC 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 ofspeech path.

l For voice trunk networking, all the NEs within an MSC Pool must be connected to theTMSC to which the traffic is transmitted, and connected to the GMSC that serves the MSCPool. 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 ofMGWs 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 originalconnection mode an be retained.

l 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 overIP is adopted; otherwise, the traffic is transferred by the GMSC or TMSC.

l An MSC Pool must be connected to VMSCs out of the local network and the originalconnection mode can be retained.

l The signaling and voice circuits between the MSC servers within an MSC Pool and thePSTN can be transferred through the GMSC. For the original direct connection betweenthe PSTN and the MSC servers, you must change the direct connection to the connectionthrough the GMSC. If no GMSC is present, you are advised to connect the PSTN to a pairof 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 theoriginal connection mode can be retained.The MSCs within an MSC Pool must not function as the GMSC/TMSC. The reasons areas 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 FeatureTable 3-3 lists the items of an MSC Pool planning.



3-5

Table 3-3 Items of an MSC Pool planning

Items Description

MSC Pool area planning l The area with heavy traffic and the adjacent area with lighttraffic should be distributed into the same MSC Pool area.

l For an area, where residents move frequently, such as acity and its suburbs, build a single MSC Pool. Thus, thenumber of updates between CN nodes can be reduced.

l It is recommended to configure 4 to 16 MSC serverswithin an MSC Pool. The MSC Pool should be able tosupport 4,000,000 to 24,000,000 subscribers. The capacityof an MSC server within an MSC Pool should support1,000,000 to 1,500,000 subscribers.

l Generally, the MSCs within an MSC Pool cannot servethe RNCs/BSCs outside the MSC Pool.

l Each CN node within an MSC Pool should provide thesame service and adopt the same charging strategy.

NEcapacityplanning

MSC server l Each MSC server within an MSC Pool should have thesame capacity, and thus simplifying the maintenance andplanning.

l Actual installation rate = Actual number of subscribers onan MSC server / MSC server capacity (Usually, the valueof the actual installation rate cannot be more than 80% asrequired by a carrier. You can configure the actualinstallation rate based on actual conditions.)

MGW l The capacity of the MGW is calculated based on thecapacity of the total number of RANs/BSCs which areconnected to the MGW.

l Certain capacity should be reserved because more RANs/BSCs may be accessed into the MGW.

MSC Poolcommonattributeplanning

NRI planning l The NRI is bit 23 through bit 14 of the TMSI. The lengthof the NRI ranges from 0 bit to 10 bits.

l The NRIs in the neighboring MSC Pool areas should beunique and have the same length. The NRIs in the wholenetwork should be planned on a uniform basis.

l See Table 3-1 for the details on the relationship betweenthe length and number of NRIs and the supportablenumber of subscribers.

l The Null-NRI and the NRI should be planned on a uniformbasis. The maximum or minimum value of the NRI in anNRI set within an MSC Pool can be selected based on theactual conditions.

l The Null-NRI within an MSC Pool must be unique.




Issue 02 (2008-04-10)

Items Description

Default MSCplanning

The default MSC could be any one MSC within an MSCPool. If only one MSC is set to the default MSC, the MSCmight be affected by heavy traffic and thus the single-pointfailure may occur. Therefore, configure all the MSCs in anMSC Pool to the default MSC.

Non-broadcastLAI planning

l The non-broadcast LAI is encoded together with ordinaryNRIs on a uniform basis, but it cannot be the same as anyLAI already configured in the MSC Pool. You canconfigure the non-broadcast LAI according to thedescending order or ascending order based on actualconfiguration of the LAI.

l Each MSC in an MSC Pool should be configured with anon-broadcast LAI of the local office and an MSC mapsa unique non-broadcast LAI.

Bandwidth planning ofsignaling network

The planning of the signaling network bandwidth consists ofthe planning of the following:l A/Iu interface

l Mc interface

l E interface

l Nc interface

l C/D interface

l ISUP signaling

MSC ID planning l When charging based on virtual MSC ID is adopted, theformula of calculating the number of MSC IDs plannedfor each MSC Pool is as follows: Number of MSC IDs ofeach MSC Pool = Number of MSC IDs configured on eachMSC server in the MSC Pool x Number of MSC serversin the MSC Pool Note that the number of MSC IDsconfigured on each MSC server equals to the number ofcharging areas of an MSC server.

l One MSC server is configured with one MSC ID in thecase of no special requirement.

MSC server backup planningduring the VLR data backup

l Centralized backup of the WVDB configuration: 2 xRoundup (backup subscriber quantity/6,000,000). In thiscase, the whole memory is used for backup, but thecapacity of 6,000,000 subscribers is recommended.

l Chain backup of the WVDB configuration: 2*Roundup(backup subscriber quantity/500,000). A pair of backupWVDBs can process the services of 200,000 subscribers.Therefore, if the MSC server is configured with more thanfour pairs of VDBs, you need not configure other backupboards.



3-7

Items Description

Bandwidth planning of voicetrunk network

The planning of the voice trunk network bandwidth consistsof the planning of the following:l A/Iu interface

l Nb interface

l Relevant parameters of the MGW

l Bandwidth for ISUP TDM traffic

Bandwidth planning of bearernetwork

The planning of the bearer network bandwidth consists of theplanning of the following:l Nb interface

l Nc interface

l Mc interface

l Reserved bandwidth of the VDB




Issue 02 (2008-04-10)

4 Commands and Parameters Related to MSCPool

About This Chapter

This section describes the commands and parameters related to the MSC Pool feature, inparticular the key parameters, global data, and values of software parameters. The informationin this chapter guides you to correctly and promptly understand and configure the data about theMSC Pool feature.

4.1 Commands Used on the MSC ServerThis section describes commands and parameters used on the MSC server to implement theMSC Pool feature.

4.2 Commands Used on the MGWThis section describes commands and parameters used on the MGW to implement the MSC Poolfeature.

4.3 Global Data and Software ParametersThis section describes important global data and software parameters used on the MSC serverto implement the MSC Pool feature.

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual 4 Commands and Parameters Related to MSC Pool


4-1

4.1 Commands Used on the MSC ServerThis section describes commands and parameters used on the MSC server to implement theMSC Pool feature.

SET POOLINFODescription

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;

Remark

If the Function flag of MSC POOL parameter is set to Yes, the MSOFTX3000can directly interwork with the BSC that supports the NNSF function. If the MGWprovides the A-Flex function, set the parameter to No.If the Flag of MGW providing MSC POOL function parameter is set to Yes, theMGW can provides the A-Flex function. If the MSC Pool interworks with ordinaryBSCs, set the parameter to Yes.The value of the MSC Identity in MSC POOL parameter must be consistent withthe value of the MSC Index parameter in the ADD CNNODE command used onthe MGW.The Length of NRI bit parameter is set to 6, indicating that six bits in the TMSIare reserved for the NRI. The NRI of all network elements in the Pool must havethe same length.

ADD NRIMSCDescription

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;

Remark

The NRI value parameter is set to 24, indicating that the NRI value is 24. Thisparameter works together with the Length of NRI bit parameter (set to 6) in theSET POOLINFO command to determine the NRI. For example, if the TMSI is 8060 00 01 in hexadecimal format and 0100 0000 0110 0000 0000 0000 0000 0001in binary format, the middle six bits (011000) starting from the 24th bit representthe 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 anMSC for migrated subscribers according to the offload mode specified in the 3GPPTS 23.236.

4 Commands and Parameters Related to MSC PoolHUAWEI MSOFTX3000 Mobile Softswitch Center



Issue 02 (2008-04-10)

ADD LAIGCIDescription

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;

Remark

The Non Broadcast LAI parameter specifies whether the LAI is a non-broadcastLAI. A non-broadcast LAI is used by the terminal to trigger location updateaccording to the offload mode specified in the 3GPP TS 23.236.

SET OFFLDCTRLDescription

This command is used to set the offload mode for the MSC server.

Script SET OFFLDCTRL: OFFLDTYPE=OFFLDMSISDN;

Remark

Before starting another offload mode, stop the existing offload mode.The offload can be performed based on the offload mode specified in the 3GPP TS23.236 or the E interface redirection mode defined by the private protocol ofHuawei. Bit 11 of P401 (VLR Part2 Software Parameter 02) determines whichoffload mode is to be used.

SET POOLBCDescription

This command is used to set the value of the MSC Pool broadcast timer for the MSCserver.

Script SET POOLBC: TMRVAL=60, STARTTIME=16&19;

Remark

This command is used to set the value and startup time of the MSC Pool broadcasttimer. Based on the configured value and startup time of the MSC Pool broadcasttimer, the MSC broadcasts its current load to the connected RNC/BSC by sendinga message on the private interface. The information provided by the broadcastmessage includes the currently available subscriber capacity (available resources inthe current MSC) and designed capacity of servers in the MSC Pool (not includingsubscribers of the RNCs/BSCs outside the MSC Pool).A broadcast message can be delivered only when bit 0 of P195 is set to 0 by usingthe MOD MSFP command.

SET POOLBKPCTRLDescription

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;

Remark

The Support backup parameter is set to YES, indicating that the MSC Pool backupis 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 serverthrough the backup path. To prevent the standby MSC server from sending pagingmessages globally, only the basic information (such as the IMSI, subscriber status,and LAI) of subscribers is backed up.

ADD POOLBKPRTDescription

This command is used to set the MSC Pool backup route.

Script ADD POOLBKPRT: MN="MSCGS1", ROLETYPE=HOMEMSC, RTNAME="GS1-GS4";

Remark

M3UA routes are used as backup routes between the active MSC server and thestandby MSC server. You are advised to use the 14-digit standby SPCs of the activeand standby MSC servers for the M3UA routes.The route configuration is different for the active MSC server and the standby MSCserver. For the active MSC server, only one backup route must be configured. Forthe standby MSC server, multiple backup routes must be configured to interworkwith various active MSC servers.

4.2 Commands Used on the MGWThis section describes commands and parameters used on the MGW to implement the MSC Poolfeature.

SET POOLINFODescription

This command is used to set the MSC Pool function.

Script SET POOLINFO: MSCPOOLFLAG=YES, NRILEN=6, NULLNRI=63;

Remark

The MSC Pool Control Flag parameter is set to Open, indicating that the MGWcan serve as the NNSF.The NRI Length parameter is set to 6, indicating that the length of the NRI bits issix. 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 isa Null NRI.The settings of the NRI must be consistent between the MGW and the MSC server.




Issue 02 (2008-04-10)

ADD NRIMSCDescription

This command is used to set the mapping between the NRI and the MSC server.

Script ADD NRIMSC: NRIV=24, CNID=1;

Remark

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 theNRI from the TMSI in the CR message, the NNSF forwards the CR message to theMSC server whose node ID is 1.The CN node here cannot be a standby node, that is, Flag of independent backupoffice 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 CNNODEDescription

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;

Remark

The CNNode ID parameter specifies the ID of a CN node.For the description of the MSC Index parameter, see the descriptions about SETPOOLINFO, a command used on the MSC server.The M3DE Index specifies the mapping between the CN node and the M3DEdestination entity.The Backup Flag parameter specifies whether the destination entity is a standbyMSC server.The Manage Status parameter specifies the management status of a CN node.

4.3 Global Data and Software ParametersThis section describes important global data and software parameters used on the MSC serverto implement the MSC Pool feature.

SET MAPACCFGDescription

This command is used to set the MAP feature configuration.

Script SET MAPACCFG: IFALTMSILU=YES, IFALTMSISA=YES;



4-5

Remark

The Allocate TMSI upon location update parameter must be set to Yes, indicatingthat the MSC allocates the updated TMSI and location area through the LU ACCEPTmessage sent on the A interface after the location update.The Allocate TMSI upon service access parameter must be set to Yes, indicatingthat the MSC allocates the updated TMSI and location area through the TMSIREALL message sent on the A interface after calling or called service is completed.

SET MAPPARADescription

This command is used to set the auxiliary MAP feature configuration.

Script SET MAPPARA: ULFORUNUSRMO=YES;

Remark

The Send UL when subscriber is unknown in MO parameter must be set toYes, indicating that the VLR initiates the network-side implicit location update onbehalf of a subscriber after receiving a service request from the subscriber who doesnot have registered data in the VDB. This function of the VLR is used in an MSCPool network during the call termination recovery and the offload based on the Einterface redirection.

MOD PGCTRLDescription

This command is used to set the paging control information.

Script MOD PGCTRL: TYPE=ALL, TIMES=1, FIRSTD=6, IMSI=FIRST-1;

Remark

When you run this command on the active MSC server, configure the data based onthe actual conditions. The recommended settings are as follows:l Only the last paging is based on the IMSI.

l The total paging duration in the case of multiple times of paging cannot exceed20 seconds.

When you run this command on the standby MSC server, configure the data toinitiate paging based on the IMSI and only once.

P401 - VLR Part2 Software Parameter 02Bit 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




Issue 02 (2008-04-10)

Bit 12 Bit 12 determines whether to select the local MSC or other MSCs within the samepool 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 redirectedto another MSC forcibly. When the load reallocation based on the E interfaceredirection mode is used, the callee data is recovered, and the paging response isreceived, 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

Remark

The preceding bits are used to control the functions of the active MSC server.

P195 - A/Iu INTERFACEPARA2Bit 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 anMSC 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 sentby the BSC or RNC when the pool function (such as MSC Pool, server pool, or bothof 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 theBSC becomes reachable, the MSC server sends the RESET CIRCUIT messageinstead of the RESET message. The RESET message controlled by the client isprocessed in the original mode. When the MGW manages the A interface circuits,the MSC server does not deliver the RESET and RESET CUIRCUIT messages. TheMSC server does not deliver the RESET message to the RNC any more.

P144 - Call Internal Parameter 9Bit 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 therestriction of non-CMN calls incoming from and outgoing to the BICC trunk forthe MSC Pool feature when a call (all calls between MSC servers in the MSC Poolare 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 BICCtrunk during outgoing route selection= 0: to restrict the non-CMN calls incoming from and outgoing to the BICC trunkduring outgoing route selectionThe default value (recommended) is 1.



4-7




Issue 02 (2008-04-10)

5 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 ina 2G network.

5.1 New Target Network DescriptionThis section describes typical application scenarios of a new MSC Pool in the 2G network.

5.2 Data Configuration FlowThis section describes the overall data configuration process, data planning, and data presettingfor an MSC Pool in the scenario of new MSC Pool in 2G network.

5.3 Data PlanningThis section describes the data planning for an MSC Pool network.

5.4 Data ConfigurationThis section describes the data configuration procedures of a new MSC Pool in the 2G network.

5.5 Other Data ConfigurationThis section describes other data configuration in the scenario of a new MSC Pool in a 2Gnetwork.

5.6 System CommissioningThis section describes the system commissioning of a new MSC Pool in the 2G network.

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual 5 New MSC Pool in the 2G Network


5-1

5.1 New Target Network DescriptionThis 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 2Gnetwork with a new MSC Pool are as follows:

l The core network adopts the softswitch solution, that is, an MSC is divided into an MSCserver and an MGW.

l The access network adopts the BSS solution. The BSC in the BSS does not support the A-Flex function.

To build a 2G network with a new MSC Pool, the MGW must provide the A-Flex function. Thedetails 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 2

MGW1

BSC1 BSC2 BSC3 BSC4

MGW2


MGW3

SX 3 SX 4

GMSC (TMSC)

STP

HLR/SCP/SMSCSX 1

VPLMN or other MSCsin the HPLMN

Networking Description

The networking of a new target network is as follows:

l The Mc-interface is based on IP and the A-interface signaling is forwarded by the MGWin M3UA forward mode.

l The A-interface signaling and voice circuits between the MGW and the BSC are borne overthe TDM.

l The Nb-interface between the MGWs is borne over IP and all MGWs are connected witheach other.

l All voice channels of the MGW are directly connected to the GMSC (or TMSC). Thesignaling and speech channels are based on TDM.

5 New MSC Pool in the 2G NetworkHUAWEI MSOFTX3000 Mobile Softswitch Center



Issue 02 (2008-04-10)

l The MSC server is connected to the pure signaling point NEs, such as the HLR, SCP, andSMC in STP forward mode. The MSC server is connected to the STP directly and thesignaling is borne over IP.

l The A-interface circuits are based on TDM bearers. The MGW manages the A-interfacecircuits so that the circuits are shared by all BSCs in the MSC Pool.

l 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 MSCPool interworks with external networks through the GMSC. The MSC Pool interworks withlocal MSCs or toll MSCs in the network through the TMSC.

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

Function DescriptionThe 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 supportthe A-Flex function.

l The MGW manages the A-interface circuits.

l The virtual MGW function is enabled on the MGW.

Signaling Point Codes DescriptionBased on the description in 1.3.8 A-Flex Function Proxy on the MGW, you are advised to usethe 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 reservednetwork).

l MSC server 2 uses two SPCs: BB (for international network) and EE (for internationalreserved network).

l MSC server 3 uses two SPCs: CC (for national network) and FF (for national reservednetwork).

l MGW1 uses an SPC (GG) and a public SPC (XX). GG for national network is used tointerwork with the MSC server. XX for national reserved network is used to interwork withthe access network.

l MGW2 uses an SPC (HH) and a public SPC (XX). HH for national reserved network isused to interwork with the MSC server. XX for national reserved network is used tointerwork with the access network.

l MGW3 uses an SPC (JJ) and a public SPC (XX). JJ for national reserved network is usedto interwork with the MSC server. XX for national reserved network is used to interworkwith the access network.



5-3

Figure 5-2 SPCs used in the target network

SX 1

MGW1

BSC1

SX 2 SX 3

MGW2 MGW

3

BSC2

BSC3

BSC4

AA BB CC

DD EE FF

GGHH

JJ

For detailed data planning, see Table 5-1, Table 5-2, and Table 5-3.

Analysis of the Message Flowl BSC 1 (OPC: 10B) sends the first uplink message (that is, the SCCP CR message) to MGW

1 (SPC: XX).

l GG is the assistant SPC of XX. Therefore, the message between XX and DD is transmittedthrough the M3UA link set between GG and DD.

l After receiving the message, the MGW (SPC: XX) judges that an MSC Pool network isused and starts the NNSF function. The MGW resolves the NRI and sends the message tothe MSC server according to the mapping between GG and DD (the M3UA destinationentity). In this message, the DPC is changed to DD and the OPC 10B is retained.

l The MSC server receives the message through the link set between DD and GG.

l 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 MSCID is included in the local reference number of this message.

l The MGW receives the message through GG. The message indicates that an MSC Poolnetwork is used. By utilizing the assistant relationship between XX and GG, the MGWsends the message to the BSC through the N7 link set between XX and 10B. In this message,the OPC is changed to XX.

l The BSC receives the message in which the OPC is XX and DPC is 10B. In this way, theSPC of the MSC server is hidden from the BSC through the MGW.

l By now, the transmission of the SCCP CR and CC messages is completed. Subsequent Ainterface signaling is transmitted through the SCCP connection established between thelocal and destination reference numbers.


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




Issue 02 (2008-04-10)

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

Start

Preparation

Presetting data for MSC Pool

Adding MSC servers to MSCPool

Adding MGWs to MSC Pool

Configuring number analysis data

Configuring mobile service data

Configuring IN service data

End

Evolution ofthe CoreNetwork

Access of theAccess Network

Configuringservice

data

Adding BSCs to MSC Pool

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


Only the data planning related to the MSC Pool is described in this section. All other dataplanning is outside the scope of this document. Table 5-1, Table 5-2, and Table 5-3 list the dataplanning for an MSC Pool network.

Table 5-1 Data planning for MSC servers in an MSC Pool network

Name MSC Server 1 MSC Server 2 MSC Server 3

Nodename

SX1 SX2 SX3

SPC National network:A80001

National network:A80002


National reservednetwork: 801





5-5


IPaddress(IPaddressof theWIFM)

192.168.153.1 192.168.155.2 192.168.151.3

Lengthof theNRI(bits)

6 (recommended) 6 (recommended) 6 (recommended)

Valueof theNRI


DefaultMSC

You are advised to set all MSC servers in the MSC Pool to default MSCs.

Charging mode

Charging based on MSC IDs (recommended)

Capacity of anMSCserverin theMSCPool

1 million (recommended)

Valueof NullNRI


CN ID 1 (recommended) 2 (recommended) 3 (recommended)

Non-broadcast LAI

460004444 460005555 460006666




Issue 02 (2008-04-10)


Data ofH.248linksbetween theMSCserverand theMGW

MGW1:SLOCIP1="192.168.153.1"SLOCPORT=5000SRMTIP1="192.168.167.21"SRMTPORT=5000MGW2:SLOCIP1="192.168.153.1"SLOCPORT=2300SRMTIP1="192.168.172.41"SRMTPORT=2300MGW3:SLOCIP1="192.168.153.1"SLOCPORT=2203SRMTIP1="192.168.175.42"SRMTPORT=2203





5-7


Data ofM3UAlinksbetween theMSCserverand theMGW

MGW1:LOCIP1="192.168.153.1"LOCPORT=6001PEERIP1="192.168.167.21"PEERPORT=6001MGW2:LOCIP1="192.168.153.1"LOCPORT=2302PEERIP1="192.168.172.41"PEERPORT=2302MGW3:LOCIP1="192.168.153.1"LOCPORT=2204PEERIP1="192.168.175.42"PEERPORT=2204

MGW1:SLOCIP1="192.168.155.2"SLOCPORT=4100

PEERIP1="192.168.167.21"PEERPORT=4100

MGW2:LOCIP1="192.168.155.2"LOCPORT=4200PEERIP1="192.168.172.41"PEERPORT=4200MGW3:LOCIP1="192.168.155.2"LOCPORT=4300PEERIP1="192.168.175.42"PEERPORT=4300

MGW1:SLOCIP1="192.168.151.3"SLOCPORT=3500PEERIP1="192.168.167.21"PEERPORT=3500MGW2:LOCIP1="192.168.151.3"LOCPORT=3600PEERIP1="192.168.172.41"PEERPORT=3600MGW3:LOCIP1="192.168.151.3"LOCPORT=4700PEERIP1="192.168.175.42"PEERPORT=4700

Table 5-2 Data planning for MGWs in an MSC Pool network

Name MGW1 MGW2 MGW3

Node name MGW1 MGW2 MGW3

SPC 2A (for interworkingwith the MSC server)

2C (for interworkingwith the MSC server)

2D (for interworkingwith the MSC server)

902 (for interworkingwith the accessnetwork)



IP address (theMGW adopts thecentralizedforwarding modefor IP addresses)

192.168.167.21 192.168.172.41 192.168.175.42




Issue 02 (2008-04-10)

Name MGW1 MGW2 MGW3

Mapping betweenthe VMGW IDs andthe MSC servers

SX1:VMGWID=0SX2:VMGWID=1SX3:VMGWID=2



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 NEsThis section describes the basic data configuration of NEs.

5.4.2 Presetting Data for the MSC PoolThis section describes the presetting data configuration for an MSC Pool.

5.4.3 Building an MSC Pool in the Core NetworkThis section describes the configuration procedure for building an MSC Pool in the core network.

5.4.4 Integration with the Access NetworkThis section describes the configuration procedure for integrating an MSC Pool with the accessnetwork.


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

5.4.2 Presetting Data for the MSC PoolThis section describes the presetting data configuration for an MSC Pool.



5-9

Configuring Data on the MSC ServerTo preset the data on the MSC servers, perform the following steps:

1. Set the MSC servers on the M2000.

Description

Connect the MSC servers to the O&M system of the M2000. Thus, youcan maintain the MSC servers in a centralized manner on the M2000.

Script -

Remark The data configuration is performed on the M2000. For details, refer tothe relevant part in the electronic documentation of the M2000.

2. For all MSC servers, load the MSC server license file with MSC Pool feature enabled.

Description

Apply for and load the MSC Pool license of all MSC servers.

Script

LOD LICENSE;

Remark

-

3. Activate the A-FLEX function of all MSC servers.

Description

On each MSC server, run ADD CDBFUNC to activate the A-FLEXfunction of the MSC server.

Script SX1:ADD CDBFUNC: CDBMN= 110, FUNC=AFLEX-1;SX2:ADD CDBFUNC: CDBMN= 102, FUNC=AFLEX-1;SX3:ADD CDBFUNC: CDBMN= 103, FUNC=AFLEX-1;

Remark Only an MSC server that supports the A-FLEX function can be addedto the MSC Pool.

4. Set the NRI and default MSCs.

Description

On each MSC server, run ADD NRIMSC to set the NRI (adding theNRI, Null NRI, and neighboring NRI). Thus, all MSC servers in the MSCPool 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;ADD NRIMSC: DESC="SX3_NRI", NRIV=3, MSCNO=K'861390803, VLRNO=K'861390803, MSCNM="SX3", LOCMSC=FALSE;SX2:ADD NRIMSC: DESC="SX2", NRIV=2, MSCNO=K'861390802, VLRNO=K'861390802, MSCNM="SX2";ADD NRIMSC: DESC="NULL NRI", NRIV=10, MSCNO=K'861390802, VLRNO=K'861390802, MSCNM="SX2", NNRI=TRUE;ADD NRIMSC: DESC="SX1_NRI", NRIV=1, MSCNO=K'861390801, VLRNO=K'861390801, MSCNM="SX1", LOCMSC=FALSE;ADD NRIMSC: DESC="SX3_NRI", NRIV=3, MSCNO=K'861390803, VLRNO=K'861390803, MSCNM="SX3", LOCMSC=FALSE;SX3:ADD NRIMSC: DESC="SX3", NRIV=3, MSCNO=K'861390803, VLRNO=K'861390803, MSCNM="SX3";ADD NRIMSC: DESC="NULL_NRI", NRIV=10, MSCNO=K'861390803, VLRNO=K'861390803, MSCNM="SX3", NNRI=TRUE;ADD NRIMSC: DESC="SX1_NRI", NRIV=1, MSCNO=K'861390801, VLRNO=K'861390801, MSCNM="SX1", LOCMSC=FALSE;ADD NRIMSC: DESC="SX2_NRI", NRIV=2, MSCNO=K'861390802, VLRNO=K'861390802, MSCNM="SX2", LOCMSC=FALSE;

Remark This command is used to set the NRI.The Null NRI flag parameter is set to YES, indicating that the NRI is aNull NRI. A Null NRI is used by the NNSF to reallocate the CN nodefor subscribers according to the offload mode specified in the 3GPP TS23.236.

5. Set the Non-broadcast LAI parameter.

Description

On each MSC server, set the Non-broadcast LAI parameter.

Script SX1:ADD LAISAI: SAI="460004444", LAISAINAME="Non-broadcast", MSCN="861390801", VLRN="861390801", NONBCLAI=YES, NONBCLAIT=HVLR;SX2:ADD LAIGCI: SAI="460005555", LAIGCINAME="Non-broadcast", MSCN="861390802", VLRN="861390802", NONBCLAI=YES;SX3:ADD LAIGCI: SAI="460006666", LAIGCINAME="Non-broadcast", MSCN="861390803", VLRN="861390803", NONBCLAI=YES;



5-11

Remark The Non-broadcast LAI parameter specifies whether the LAI is a non-broadcast LAI. A non-broadcast LAI is used by the terminal to triggerlocation update according to the offload mode specified in the 3GPP TS23.236.

6. Set the MSC Pool function information.

Description

On each MSC server, run SET POOLINFO to set the MSC Poolfunction information.

Script SX1:SET POOLINFO: MSCPOOL=YES, SERVER=YES, MSCIDX=1, USRNUM=1000, NRILEN=6;SX2:SET POOLINFO: MSCPOOL=YES, SERVER=YES, MSCIDX=2, USRNUM=1000, NRILEN=6;SX3:SET POOLINFO: MSCPOOL=YES, SERVER=YES, MSCIDX=3, USRNUM=1000, NRILEN=6;

Remark This command is used to set the MSC Pool function information.The Function flag of MSC POOL parameter is set to Yes, indicatingthat the MSOFTX3000 can directly interwork with the BSC that supportsthe NNSF function. If the MGW serves as the NNSF, set the parameterto No.The Flag of MGW providing MSC POOL function parameter is setto Yes, indicating that the MGW can serve as the NNSF. If the MSCPool interworks with ordinary BSCs, set the parameter to Yes.The value of the MSC Identity in MSC POOL parameter must beconsistent with the value of the MSC Index parameter in the ADDCNNODE command used on the MGW. Subsequent connection-modeSCCP messages can be successfully sent on the A interface only whencorrect local and destination reference numbers are configured. Thedestination reference number for the connection-mode message sent bya CN node is carried in the CR message sent by the BSC. The MSCIdentity in MSC POOL parameter is included in the local referencenumber. If the value of the MSC Identity in MSC POOL parameter isinconsistent with the value of the MSC Index parameter in the ADDCNNODE command used on the MGW, subsequent connection-modemessages (except for the CR request messages) sent on the A interfaceare incorrectly routed by the MGW.The Length of NRI bit parameter is set to 6, indicating that six bits inthe TMSI are reserved for the NRI. The NRI of all network elements inthe Pool must have the same length.

7. Set all BSCs under each MSC server to support the MGW proxy A-Flex function.

Description

On each MSC server, run MOD BSC to set all BSCs of the MSC serverto 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", CAPABILITY=MGWPROXYAFLEX-1;SX3:MOD BSC: DPC="B04", OPC="803", BSCNM="BSC3", CAPABILITY=MGWPROXYAFLEX-1;MOD BSC: DPC="B05", OPC="803", BSCNM="BSC4", CAPABILITY=MGWPROXYAFLEX-1;

8. Set the CN IDs of all MSC servers.

Description

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:SET OFI: OFN="SX2", LOT=LOCMSC, NN=YES, NN2=YES, SN1=NAT, SN2=NATB, NPC="A80002", NP2C="802", NNS=SP24, NN2S=SP14, LAC="0755", LNC=K'86, CNID=2;SX3:SET OFI: OFN="SX3", LOT=LOCMSC, NN=YES, NN2=YES, SN1=NAT, SN2=NATB, NPC="A80003", NP2C="803", NNS=SP24, NN2S=SP14, LAC="0755", LNC=K'86, CNID=3;

Remark A CN ID uniquely identifies an MSC server in an MSC Pool.

9. Set the parameters of the MSC Pool broadcast timer.

Description

On each MSC server, run SET POOLBC to set the parameters of theMSC 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. Basedon the value and startup time of the timer, the MSC server broadcasts theload of the MSC server to associated BSCs or RNCs through privateinterface messages. The information provided in the broadcast messagesincludes how many more subscribers the MSC server can support(remaining resources of the MSC server) and capacity of the MSC serverin the MSC Pool (not including the number of subscribers supported bythe 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 runningMOD MSFP.

10. Enable the TMSI reallocation function.



5-13

Description

On each MSC server, run SET MAPACCFG to enable the TMSIreallocation function.

Script SET MAPACCFG: IFALTMSILU=YES, IFALTMSISA=YES;

----End

Configuring Data on the MGWTo preset the data on the MGWs, perform the following steps:

1. Set the MGWs on the M2000.

Description

Connect the MGWs to the O&M system of the M2000. Thus, you canmaintain 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 theonline Help of the M2000.

2. Add new signaling points for each MGW.

Description

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:SET OFI: NAME="MGW2", INTVLD=NO, INTRESVLD=NO, NATVLD=YES, NATRESVLD=YES, SERACH0=NAT, SERACH1=NATB, NATOPC=H' 2C, NATRESOPC=H'902, NATLEN=LABEL24, NATRESLEN=LABEL14;MGW3:SET OFI: NAME="MGW3", INTVLD=NO, INTRESVLD=NO, NATVLD=YES, NATRESVLD=YES, SERACH0=NAT, SERACH1=NATB, NATOPC=H' 2D, NATRESOPC=H'902, NATLEN=LABEL24, NATRESLEN=LABEL14;

----End

Replacing TMSIsStart the IMSI reallocation process in the case that the A-FLEX function is enabled on the MSCservers and the MGWs. Then, wait for the time required by two periodical location updates (theinterval of the location updates can be set on the BSC) for the replacing of TMSIs to becompleted. (You are advised to set the start time of the TMSI replacing to a time when there area significant number of online subscribers). To replace a TMSI is to add the corresponding NRIto the TMSI. This enables the subscribers to be still homed to the original MSC server after the2G network evolves into an MSC Pool. The purpose of the operation is to keep the target network




Issue 02 (2008-04-10)

as similar to the existing network as possible and thus to minimize the impact of the networkevolution on the network operation.

As long as you have run SET MAPACCFG to enable the TMSI reallocation function, theMSOFTX3000 automatically replaces the TMSIs of subscribers.

Ending the Presetting

After two periodical location updates, randomly select 10 subscribers and check whether theirTMSIs 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 theMGW, 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 1and MGW 1.

Description

On MSC server 1, add MGW 1 and configure the H.248 linksbetween 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&NOMODEM-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, HRAMRR=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RATE740-1&RATE795-1, UMTSAMR2R=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RATE740-1&RATE795-1&RATE102-1&RATE122-1, FRAMRR=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RATE740-1&RATE795-1&RATE102-1&RATE122-1, UMTSAMRR=RATE475-1&RATE515-1&RATE590-1&RATE670-1&RATE740-1&RATE795-1&RATE102-1&RATE122-1, MODEMLST=GSMMT-1&GSMV21-1&GSMV22-1&GSMV22BIS-1&GSMV23-1&GSMV26TER-1&GSMV32-1&GSMMTAUTO-1&GSMV34-1, TC=GSMEFR-1&GSMHR-1&TDMAEFR-1&PDCEFR-1&HRAMR-1&UMTSAMR2-1&FRAMR-1&PCMA-1&PCMU-1&UMTSAMR-1&G7231-1&G729A-1&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


Description



(3) On MSC server 1, add MGW 3 and configure the H.248 links between MSC server 1

and MGW 3.

Description





Issue 02 (2008-04-10)


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

Description

On MSC server 1, add the data of M3UA configuration from MSCserver 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 withMGW 1 (SPC: 2A).


Description




5-17

Script ADD M3DE: DENM="TO_MGW2_NATB", NI=NATB, DPC="2C", STPF=TRUE, DET=SG;ADD M3LKS: LSNM="TO_MGW2_NATB", ADNM="TO_MGW2_NATB", WM=ASP;ADD M3LNK: MN=134, LNKNM="TO_MGW2_NATB", LOCIP1="192.168.153.1", LOCPORT=2302, PEERIP1="192.168.172.41", PEERPORT=2302, CS=C, LSNM="TO_MGW2_NATB", QoS=TOS;ADD M3RT: RTNM="TO_MGW2_NATB", DENM="TO_MGW2_NATB", LSNM="TO_MGW2_NATB";

Remark Add the M3UA data for MSC server 1 (SPC: 801) to interwork withMGW 2 (SPC: 2C).

(3) On MSC server 1, add the data of M3UA configuration from MSC server 1 to MGW

3.

Description


Script ADD M3DE: DENM="TO_MGW3_NATB", NI=NATB, DPC="2D", STPF=TRUE, DET=SG;ADD M3LKS: LSNM="TO_MGW3_NATB", ADNM="TO_MGW3_NATB", WM=ASP;ADD M3LNK: MN=134, LNKNM="TO_MGW3_NATB", LOCIP1="192.168.153.1", LOCPORT=2204, PEERIP1="192.168.175.42", PEERPORT=2204, CS=C, LSNM="TO_MGW3_NATB", QoS=TOS;ADD M3RT: RTNM="TO_MGW3_NATB", DENM="TO_MGW3_NATB", LSNM="TO_MGW3_NATB";

Remark Add the M3UA data for MSC server 1 (SPC: 801) to interwork withMGW 3 (SPC: 2D).

----End

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


Configuring the Data on MGW 1To configure the data on MGW 1, perform the following steps:

1. Configure the MGW1 SPC based on the general planning of the MSC Pool.

Description

Add an SPC for MGW 1.




Issue 02 (2008-04-10)

Script 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;

2. Configure the relevant information of the MSC Pool.

Description

On MGW 1, configure the relevant information of the MSC Pool.


Remark This command is use to set the MSC Pool function information.The MSC Pool Control Flag parameter is set to Open, indicating thatthe 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.

Description

Add a virtual MGW on MGW 1. Add an H.248 link between MGW 1 andMSC server 1.

Script

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.

Description

On MGW 1, add an M3UA destination signaling point and related M3UAconfiguration for interworking with MSC server 1.



5-19

Script

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=H’902;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;

Remark

Add two M3UA local entities for the MGW.Add the M3UA destination entity (that is, an MSC server) for one M3UAlocal entity of the MGW. The network type is MSC Pool. A correspondingM3UA route must be added.Add the M3UA destination entity (that is, an MSC server) for the otherM3UA 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 theMc 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 MSCserver1/ MSC server2/ MSC server3.

(1) On MGW 1, add a CN node of MSC server 1 and the mapping between the NRI andMSC server 1.

Description

On MGW 1, add a CN node of MSC server 1 and the mapping betweenthe NRI and MSC server 1.

Script

ADD CNNODE: CNID=1, CNNAME="SX1", MSCIDX=1, M3DEIDX=1, MNGSTA=INHIBITED;ADD NRIMSC: NRIV=1, CNID=1;

(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 thecorresponding CN node and mapping between the NRI and MSC server 1.

----End

Configuring the Data on MGW 2

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

Configuring the Data on MGW 3

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




Issue 02 (2008-04-10)

5.4.4 Integration with the Access NetworkThis section describes the configuration procedure for integrating an MSC Pool with the accessnetwork.


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.

Description

Add an M3UA destination entity for BSC 1.

Script ADD M3DE: DENM="BSC1", LENM="SX1_NATB", NI=NATB, DPC="10B", DET=SP;

Remark Add the M3UA data for MSC server 1 (SPC: 801) to interwork withBSC 1 (SPC: 10B).

(2) Add an office direction for BSC 1.

Description

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.

Description

Add BSC 1 on MSC server 3.

Script ADD BSC: NI=NATB, DPC="10B", OPC="801", BSCNM="BSC1", CAPABILITY=CCPAGING-1&SMSPAGING-1&SSPAGING-1&PSIPAGING-1&LCS-1&SERVICEHO-1&DTM-1&LOADHO-1&MGWPROXYAFLEX-1&PRIVATEMSG-1&SupportActiveTrace-1, RSSCNAME="SX1", MLAIF=YES, MGWMAC=YES;

(4) Add an M3UA route to BSC 1.

Description

Add an M3UA route to BSC 1.

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

(5) Add an SCCP DSP for BSC 1.



5-21

Description

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.

Description

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.

Description

Add an A-interface trunk group to facilitate performancemeasurements relevant to trunk groups on MSC server 1.

Script ADD AIETG: TGNAME="BSC1", MGWNAME="MGW1", SOPC="801", SDPC="10B", CPNAME="BSC1" , BTG=1;

2. 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 areascontrolled by BSC 1.

Script ADD PGCTRL: LAI="460000011", TYPE=ALL;

3. 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. Thatis, the MGW is enabled to manage the A-interface circuits.

Script MOD BSC: DPC="10B", OPC="801", BSCNM="BSC1", MGWMAC=YES;

The procedure for adding BSC 2, BSC 3, and BSC 4 on MSC server 1 is similar to theprocedure 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


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




Issue 02 (2008-04-10)


Configuring the Data on MGW 11. 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;

2. 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 NetworkType 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 (902) of MGW 1 to the BSC.Add the MTP3 link from the SPC (2A) of MGW 1 to the BSC. No MTProute must be configured because the SP with the SPC 2A is assisted bythe 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 dataincludes the A-interface circuit pool, BSC, A-interface trunk group, andA-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 procedurefor adding BSC 1 on MGW 1. Therefore, it is not described in this document.

----End



5-23

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

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

Configuring the Data on the BSCThe data configuration on the BSC varies according to the BSC supplier. For details on thecommands, refer to relevant data configuration manuals of the BSC.

5.5 Other Data ConfigurationThis section describes other data configuration in the scenario of a new MSC Pool in a 2Gnetwork.

Other data configuration is related to subsequent commissioning. You need to configure otherdata for the NEs that require service commissioning only. To avoid the impact on existingservices, do not configure below data for the NEs that do not require MSC Pool featurecommissioning. If the commissioning is interrupted, restore the location area, cell, and servicedata to the original values.

Configuring the Consistency Data

CAUTIONConfigure the consistency data for the NEs that require service commissioning only. Do notconfigure 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 Run ADD LAIGCI to add location areas. Modify the data of theneighboring 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";ADD LAIGCI: GCI="460000060", LAIGCINAME="BSC3_LAI", MSCN="861390801", VLRN="861390801", NONBCLAI=NO, LAICAT=LAI, LAIT=HVLR, BSCDPC1="B04", CSNAME="SX1";ADD LAIGCI: GCI="460000070", LAIGCINAME="BSC4_LAI", MSCN="861390801", VLRN="861390801", NONBCLAI=NO, LAICAT=LAI, LAIT=HVLR, BSCDPC1="B05", CSNAME="SX1";SX2:ADD LAIGCI: GCI="460000011", LAIGCINAME="BSC1_LAI", MSCN="861390802", VLRN="861390802", NONBCLAI=NO, LAICAT=LAI, LAIT=HVLR, BSCDPC1="10B", CSNAME="SX2";ADD LAIGCI: GCI="460000060", LAIGCINAME="BSC3_LAI", MSCN="861390802", VLRN="861390802", NONBCLAI=NO, LAICAT=LAI, LAIT=HVLR, BSCDPC1="B04", CSNAME="SX2";ADD LAIGCI: GCI="460000070", LAIGCINAME="BSC4_LAI", MSCN="861390802", VLRN="861390802", NONBCLAI=NO, LAICAT=LAI, LAIT=HVLR, BSCDPC1="B05", CSNAME="SX2";SX3:ADD LAIGCI: GCI="460000011", LAIGCINAME="BSC1_LAI", MSCN="861390803", VLRN="861390803", NONBCLAI=NO, LAICAT=LAI, LAIT=HVLR, BSCDPC1="10B", CSNAME="SX3";ADD LAIGCI: GCI="460000012", LAIGCINAME="BSC2_LAI", MSCN="861390803", VLRN="861390803", NONBCLAI=NO, LAICAT=LAI, LAIT=HVLR, BSCDPC1="A61", CSNAME="SX3";

2. Add cells.

Description 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", LAIGCINAME="BSC3_GCI", MSCN="861390801", VLRN="861390801", NONBCLAI=NO, LAICAT=GCI, LAIT=HVLR, BSCDPC1="B04", CSNAME="SX1";ADD LAIGCI: GCI="4600000600070", LAIGCINAME="BSC4_GCI", MSCN="861390801", VLRN="861390801", NONBCLAI=NO, LAICAT=GCI, LAIT=HVLR, BSCDPC1="B05", CSNAME="SX1";SX2:ADD LAIGCI: GCI="4600000110012", LAIGCINAME="BSC1_GCI", MSCN="861390802", VLRN="861390802", NONBCLAI=NO, LAICAT=GCI, LAIT=HVLR, BSCDPC1="10B", CSNAME="SX2";ADD LAIGCI: GCI="4600000600060", LAIGCINAME="BSC3_GCI", MSCN="861390802", VLRN="861390802", NONBCLAI=NO, LAICAT=GCI, LAIT=HVLR, BSCDPC1="B04", CSNAME="SX2";ADD LAIGCI: GCI="4600000700070", LAIGCINAME="BSC4_GCI", MSCN="861390802", VLRN="861390802", NONBCLAI=NO, LAICAT=GCI, LAIT=HVLR, BSCDPC1="B05", CSNAME="SX2";SX3:ADD LAIGCI: GCI="4600000110012", LAIGCINAME="BSC1_GCI", MSCN="861390803", VLRN="861390803", NONBCLAI=NO, LAICAT=GCI, LAIT=HVLR, BSCDPC1="10B", CSNAME="SX3";ADD LAIGCI: GCI="4600000120012", LAIGCINAME="BSC2_GCI", MSCN="861390803", VLRN="861390803", NONBCLAI=NO, LAICAT=GCI, LAIT=HVLR, BSCDPC1="A61", CSNAME="SX3";

----End

Configuring the Service DataPlan the following service data on a global basis according to actual requirements (See theHUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Examples.

l Mobile service data

l IN service data

l Flow control data

l CDR and charging data

l Time parameters

The service data must be planned on a global basis in an MSC Pool. The service data configuredfor each MSC server in an MSC Pool must be the same.




Issue 02 (2008-04-10)

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

Configuring PRN Signaling Backup DataThis section describes the steps for configuring PRN signaling backup data by taking the routepriority mode as an example. For details about the principles, see Call Termination RecoveryPrinciple. In the following text, the PRN signaling of SX1 is backed up by SX2.

1. Configure two routes for the STP.

Description

The direct route from the STP to SX1 (SPC: A80001) is configured as a high-priority route. The indirect route from the STP to SX2 (SPC: A80002) and thento SX1 (SPC: A80001) is configured as a low-priority route. Assume that theSPC of the STP is 000028.

Script

ADD M3LE: LEX=0, LENAME="STP", OPC="000028", LET=SG;ADD M3DE: DEX=0, LENAME="SX1_NAT", DPC="A80001", LET=AS;ADD M3DE: DEX=1, LENAME="SX2_NAT", DPC="A80002", LET=AS;ADD M3LKS: LSX=0, LSNAME="STP-SX1", ADX=0, WM=SGP;ADD M3LKS: LSX=1, LSNAME="STP-SX2", ADX=1, WM=SGP;ADD M3RT: RTNAME ="STP-SX1", DEX=0,LSX=0;ADD M3RT: RTNAME ="STP-SX1-BK", DEX=0,LSX=1, PRI=128;

2. On the standby MSC server (SX2), add the SPC of the active MSC server (SX1).

Description

On SX2, run ADD OFI to add the SPC of SX1.

Script

ADD OFI: IDX=2, NATC="A80001";

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

Description

On SX2, run MOD OFI to set SCCP loop flag of node 0 and node 2 to Falseand set node 0 as the assistant node of node 2.

Script

MOD OFI: SN="SX2_NAT", IDX="0", SCCPLF=NO;MOD OFI: SN="SX2_NAT", IDX="2", PAC1="0", SCCPLF=NO;

4. 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 afterthe MSC SSN is configured.

Description

On SX2, run ADD SCCPSSN to configure the SCCP SSN of SX1. PRNmessages can be handled only after the VLR SSN is configured. Redirectioncan be performed only after the MSC SSN is configured.



5-27

Script

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";

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

Description

On SX2, add the M3UA local entity of SX1. This local entity is assisted by theM3UA local entity of SX2.

Script

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 server1, and therefore is not described here.

Configuring Chain Backup DataIn applications, chain backup is usually used. This section describes the steps for configuringchain backup data.

1. Set the MSC Pool backup configuration.

Description

On MSC server 1, MSC server 2, and MSC server 3, run SETPOOLBKPCTRL to set the MSC Pool backup configuration.

Script

SET POOLBKPCTRL: ENABLEBKP=YES;

2. Set the MSC Pool backup route.

Description

On MSC server 1, MSC server 2, and MSC server 3, run ADDPOOLBKPRT to set the MSC Pool backup route. MSC server 2 is the backupserver 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)

Script

SX1ADD M3DE: DENM="SX2_NAT", DPC="A80002", DET=AS;ADD M3DE: DENM="SX3_NAT", DPC="A80003", DET=AS;ADD M3LKS: LSNM="SX1_SX2", ADNM="SX2_NAT", WM=IPSP;ADD M3LKS: LSNM="SX1_SX3", ADNM="SX3_NAT", WM=IPSP;ADD M3RT: RTNM="SX1_SX2", DENM="SX2_NAT", LSNM="SX1_SX2";ADD M3RT: RTNM="SX1_SX3", DENM="SX3_NAT", LSNM="SX1_SX3";ADD POOLBKPRT: MN="SX2_NAT", ROLETYPE=HomeMSC, RTNAME="SX1_SX2";ADD POOLBKPRT: MN="SX3_NAT", ROLETYPE=BakMSC, RTNAME="SX1_SX3";SX2ADD M3DE: DENM="SX3_NAT", DPC="A80003", DET=AS;ADD M3DE: DENM="SX1_NAT", DPC="A80001", DET=AS;ADD M3LKS: LSNM="SX2_SX3", ADNM="SX3_NAT", WM=IPSP;ADD M3LKS: LSNM="SX2_SX1", ADNM="SX1_NAT", WM=IPSP;ADD M3RT: RTNM="SX2_SX3", DENM="SX3_NAT", LSNM="SX2_SX3";ADD M3RT: RTNM="SX2_SX1", DENM="SX1_NAT", LSNM="SX2_SX1";ADD POOLBKPRT: MN="SX3_NAT", ROLETYPE=HomeMSC, RTNAME="SX2_SX3";ADD POOLBKPRT: MN="SX1_NAT", ROLETYPE=BakMSC, RTNAME="SX2_SX1";SX3ADD M3DE: DENM="SX1_NAT", DPC="A80001", DET=AS;ADD M3DE: DENM="SX2_NAT", DPC="A80002", DET=AS;ADD M3LKS: LSNM="SX3_SX1", ADNM="SX1_NAT", WM=IPSP;ADD M3LKS: LSNM="SX3_SX2", ADNM="SX2_NAT", WM=IPSP;ADD M3RT: RTNM="SX3_SX2", DENM="SX1_NAT", LSNM="SX3_SX1";ADD M3RT: RTNM="SX3_SX3", DENM="SX2_NAT", LSNM="SX3_SX2";ADD POOLBKPRT: MN="SX1_NAT", ROLETYPE=HomeMSC, RTNAME="SX3_SX1";ADD POOLBKPRT: MN="SX2_NAT", ROLETYPE=BakMSC, RTNAME="SX3_SX2";

----End

Configuring Centralized Backup Data

When the networking in the centralized backup mode is adopted, you must configure the standbyMSC server for centralized backup. The standby MSC server handles the call termination failureproblem only and does not handle services. Therefore, you need to configure only the followingdata on the standby MSC server:

l Hardware data

l Local office data

l Data for interworking with the MGW

l Data for interworking with the BSC

l Data for interworking with the HLR

l Data for interworking with other MSCs through M3UA

l LAI or GCI data

For details on how to configure the preceding data, refer to the HUAWEI MSOFTX3000 MobileSoftSwitch Center Configuration Examples.



5-29

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


Only the new and changed commissioning testing introduced by the MSC Pool feature isdescribed in this section. Other common commissioning must be performed based on the basicprocedures. The commissioning can be performed during the whole evolution process. Thefollowing sections provide a commissioning example. You can make adjustments according tothe actual requirements.

Preparationsl On the M2000, set the available capacity of all MGWs in the MSC Pool.

l On the MGW to be commissioned, set all CN nodes in Inhibited state to Offload state basedon 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 becommissioned.

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

l 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;

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

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

l 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 A-interface specified dialing test function to test the voice channels. Specify the MGWname 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 mayuse.

5. Connect a commissioning subscriber to BSC 2, BSC 3, or BSC 4. Repeat substeps 1to 4 until the function is tested for all BSCs in the MSC Pool area.

Checking Load Redistribution in MSC PoolTo 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 MSCTo 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 12. After the subscriber roams out of the MSC Pool area, call the subscriber. Check whether

the voice channel can be set up correctly.3. Connect a commissioning subscriber to BSC 2/BSC 3/BSC 4. Repeat steps 1 to 2 until the


Commissioning Disaster Recovery upon Call Termination FailureTo check whether the disaster recovery upon call termination failure in the MSC Pool is normal,perform the following steps:

1. Add the data for the commissioning subscriber to the GT table of the STP. Thus, when thesubscriber is called, the STP sends a PRN request to the standby MSC server based on theconfigured data.

2. Connect a subscriber to BSC 1 and MSC server 1.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. Connect a commissioning subscriber to BSC 2/BSC 3/BSC 4. Repeat steps 2 to 3 until the


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



5-31

4. According to the actual requirements, balance the load of the MSC servers by using thesubscriber 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 notdescribed in this section. These items are checked based on the basic procedures.




Issue 02 (2008-04-10)

6 2G Network Evolution to Support MSC Pool

About This Chapter

This section describes the data planning and data configuration process of a 2G network evolvingto an MSC Pool network.

6.1 Evolution ScenarioThis section describes the scenario of a 2G network evolving to an MSC Pool network.

6.2 Data Configuration FlowThis section describes the overall data configuration procedure, data planning, and MSC Poolpresetting when a 2G network evolves to an MSC Pool network.

6.3 Evolution of the Core NetworkThis section describes the evolution process of the core network when a 2G network evolves toan MSC Pool network.

6.4 Integration with the Access NetworkThis section describes the integration process of the access network when a 2G network evolvesto an MSC Pool network.

6.5 Other Data ConfigurationThis section describes the configuration of other data in the scenario of 2G network evolutionto support MSC Pool.

6.6 System CommissioningThis section describes the system commissioning when a 2G network evolves to an MSC Poolnetwork.

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual 6 2G Network Evolution to Support MSC Pool


6-1


An MSC Pool may be evolved from a 2G network. The characteristics of a typical 2G networkare as follows:

l The core network adopts the softswitch solution, that is, the MSC is divided into the MSCserver and the MGW.

l The access network adopts the BSS solution. The BSC in the BSS does not support the A-FLEX function.

To evolve a typical 2G network into an MSC Pool, the MGW must, instead of the BSC, providethe A-FLEX function. The details of the evolution of a 2G network into an MSC Pool aredescribed in the following sections.

6.1.1 Description of the Existing NetworkThis section describes the typical existing network.

6.1.2 Description of the Target NetworkThis section describes the target network evolving from a 2G network to an MSC Pool network.

6.1.1 Description of the Existing NetworkThis 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 1

MGW1

BSC1 BSC2 BSC3 BSC4

MGW2


MGW3

SX 2 SX 3

GMSC(TMSC)

STP

HLR/SCP/SMSC

VPLMN or otherMSCs in the HPLMN

This chapter describes how a 2G network evolves into an MSC Pool by taking this network asan example.

6 2G Network Evolution to Support MSC PoolHUAWEI MSOFTX3000 Mobile Softswitch Center



Issue 02 (2008-04-10)

Networking DescriptionThe 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 theMGW, which has a built-in SG, through M2UA.

l The A-interface signaling and voice channels between the MGW and BSC are based onthe TDM bearer.

l The Nb interface between MGWs is based on the TDM bearer. Not all MGWs are directlyconnected.

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

l The signaling from the MSC servers is forwarded by the MGWs to the STP (M3UA is usedfor communication between an MGW and an MSC server), and then to the HLR/SCP/SMSC. The signaling is carried by the TDM bearer.

Function DescriptionThe function of the existing 2G network is as follows:

l The A-FLEX function is not enabled on any of the NEs.

l The MSC server is responsible for managing all A-interface circuits.

l The virtual MGW function is not enabled on any of the MGWs.

Signaling Point Codes DescriptionThe 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 reservednetwork).

l MSC server 2 uses two SPCs (BB for national network and EE for national reservednetwork).

l MSC server 3 uses two SPs (CC for national network and FF for national reserved network).

l The MGW does not use any SPC. Each BSC uses an SPC.

6.1.2 Description of the Target NetworkThis 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.



6-3

Figure 6-2 Networking diagram of a target network

SX 2

MGW1

BSC1 BSC2 BSC3 BSC4

MGW2


MGW3

SX 3 SX 4

GMSC (TMSC)

STP

HLR/SCP/SMSCSX 1

VPLMN or other MSCsin the HPLMN

As shown in Figure 6-2, the MGWs are fully connected. The signaling channels between theMSC 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 networkin further details.


The networking of the target network is as follows:

l The MSC servers in the MSC Pool are fully connected. The links between them are basedon 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.

l The Mc interface is based on the IP bearer. It adopts the protocol stack H.248/SCTP/IP.

l The A-interface signaling and voice channels between the MGW and BSC are based onthe TDM bearer. The A interface adopts the protocol stack PCM/TDM (E1).

l The control plane signaling transmitted over an A interface is forwarded by the built-in SGof the MGW. The build-in SG of the MGW communicates with the MSC server over theIP bearer. The signaling transmission between the SG and the MSC server adopts theprotocol stack BSSAP/SCCP/M3UA/SCTP/IP.

l The Nb interface between MGWs is based on the IP bearer. The MGWs are fully connected.

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

l The configurations of the A-interface circuits remain the same as those of the existing 2Gnetwork. The A-interface circuits are based on the TDM bearer. The MGWs are used tomanage the A-interface circuits so that the A-interface circuits are shared by all BSCs inthe MSC Pool area.

l 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 throughthe TMSC.


For details about the networking principles, see 3.3 General Principles of the MSC PoolPlanning.

Function DescriptionThe 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 supportthe A-FLEX function.

l The MGW is responsible for managing the A-interface circuits.


Signaling Point Codes DescriptionThe principles of SPCs planning related to the MSC Pool for the scenario of 2G networkevolution to support MSC Pool are the same as those for the scenario of new MSC Pool in 2Gnetwork. In this document, the same SPCs planning is used for the scenario of 2G networkevolution to support MSC Pool and the scenario of new MSC Pool in 2G network. For detailsabout the SPCs planning for the scenario of 2G network evolution to support MSC Pool, seeSignaling Point Codes Description.

6.2 Data Configuration FlowThis section describes the overall data configuration procedure, data planning, and MSC Poolpresetting when a 2G network evolves to an MSC Pool network.

Figure 6-3 shows the basic data configuration flow of the MSC Pool.



6-5

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

Start

Preparation







End



Configuringservice

data


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 servicedata. The detailed configuration steps are described in the following sections.

6.2.1 Data PlanningThis section describes the data planning in MSC Pool networking.

6.2.2 Presetting Data for the MSC PoolThis section describes the data presetting procedure of an MSC Pool.

6.2.1 Data PlanningThis 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 dataplanning is outside the scope of this document. Table 6-1 lists the data planning example of theMSC servers in an MSC Pool network.

Table 6-1 Data planning example of the MSC servers in an MSC Pool network


Node name SX1 SX2 SX3







Issue 02 (2008-04-10)





IP address(IP addressof theWIFM)

192.168.153.1 192.168.155.2 192.168.151.3

Length ofthe NRI(bits)


Value ofthe NRI


DefaultMSC

You are advised to set all MSC servers in the MSC Pool to default MSC.

Chargingmode


Capacity ofeach MSCserver inthe MSCPool

1 million subscribers (recommended)

Value ofNull NRI



Non-broadcastLAI

460004444 460005555 460006666

Data of H.248 linksbetweenthe MSCserver andMGW



MGW1:SLOCIP1=" 192.168.151.3"SLOCPORT=3300SRMTIP1="192.168.167.21"SRMTPORT=3300MGW2:SLOCIP1=" 192.168.151.3"SLOCPORT=3400SRMTIP1="192.168.172.41"SRMTPORT=3400MGW3:SLOCIP1=" 192.168.151.3"SLOCPORT=4600SRMTIP1="192.168.175.42"SRMTPORT=4600



6-7


Data ofM3UAlinksbetweenthe MSCserver andMGW



MGW1:SLOCIP1=" 192.168.151.3"SLOCPORT=3500PEERIP1="192.168.167.21"PEERPORT=3500MGW2:LOCIP1=" 192.168.151.3"LOCPORT=3600PEERIP1="192.168.172.41"PEERPORT=3600MGW3:LOCIP1=" 192.168.151.3"LOCPORT=4700PEERIP1="192.168.175.42"PEERPORT=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


SPC For MSC server: 2A For MSC server: 2C For MSC server: 2D

For access network:902




192.168.167.21 192.168.172.41 192.168.175.42

Mapping betweenthe VMGWIDs andthe MSC servers




Table 6-3 lists the data planning example of the BSCs in an MSC Pool network.




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

6.3 Evolution of the Core NetworkThis section describes the evolution process of the core network when a 2G network evolves toan MSC Pool network.

6.3.1 OverviewThis section describes the evolution of the core network.

6.3.2 Making MSC Server 1 and MGW 1 as an MSC PoolThis section describes the data configuration in the evolution of the core network.

6.3.3 Adding MSC Server 2 into the MSC PoolThis section describes the data configuration in the evolution of the core network.

6.3.4 Adding MGW 2 into the MSC PoolThis section describes the data configuration in the evolution of the core network.



6.3.1 OverviewThis section describes the evolution of the core network.

The evolution process consists of:

l Evolution of the core network

l Access of the access network

l System commissioning

The following two solutions are available for the evolution:

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

l 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 PoolThis section describes the data configuration in the evolution of the core network.

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

MGW1

BSC1

SX2 SX3

MGW2 MGW

3

BSC2

BSC3

BSC4

MSCPool

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

l After configuring the data of the newly added M3UA, add mapping information on MGW1. Set Manage Status corresponding to MSC server 1 to Inhibited.

Configuring Data on the MSC Server

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




Issue 02 (2008-04-10)

Description Add an M3UA local entity, M3UA destination entity, M3UA link, andM3UA 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;ADD M3LNK: MN=132, 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 MGW1 (SPC: 2A).

Configuring Data on the MGWTo configure the data on the MGW, perform the following steps:

1. Set MSC Pool function information.

Description Set MSC Pool function information.


Remark This command is used to set the MSC Pool function information.The MSC Pool Control Flag parameter is set to Open, indicating thatthe MGW can serve as the NNSF.

2. Add the SIGTRAN configuration to MSC server 1.

Description Add the SIGTRAN configuration on MGW 1 for interworking withMSC server 1 where Network Type is MSC Pool.

Script 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=H'902;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;



6-11

Remark Add two M3UA local entities for the MGW.Add the M3UA destination entity (that is, an MSC server) for oneM3UA local entity of the MGW. The network type is MSC Pool. Acorresponding M3UA route must be added.Add the M3UA destination entity (that is, an MSC server) for the otherM3UA local entity of the MGW. It is not required to add M3UA routedata.

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 andMSC server 1 where Manage Status is Inhibited.

Script ADD CNNODE: CNID=1, CNNAME="SX1", MSCIDX=1, M3DEIDX=1, MNGSTA=INHIBITED;ADD NRIMSC: NRIV=1, CNID=1;

----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 ConfigurationAfter all the data is configured, run M3UA link maintenance commands of the MSC server andthe 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.

l The service dialing test is normal.

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


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




Issue 02 (2008-04-10)

Figure 6-5 MSC Pool including MSC server 2

SX1

MGW1

BSC1

SX2 SX3

MGW2 MGW

3

BSC2

BSC3

BSC4

H248 link M3UA link

unavailable

Key Points of the Entire ConfigurationKey points of the entire configuration are as follows:

l Configure related data of the newly added H.248 link and M3UA link on MGW 1 and MSCserver 2.

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

Configuring Data on the MSC ServerTo 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 Add MGW 1 on MSC server 2 and an H.248 link from MSC server 2to MGW 1.



6-13


2. Add related data configuration of the M3UA on MSC server 2 for interworking with MGW1.

Description Add related data configuration of the M3UA on MSC server 2 forinterworking with MGW 1.


----End

Configuring Data on the MGW

To configure the data on the MGW, perform the following steps:

1. Set a virtual MGW on MGW 1, and add an H.248 link for interworking with MSC server2.

Description Set a virtual MGW on MGW 1, and add an H.248 link for interworkingwith MSC server 2.




Issue 02 (2008-04-10)

Script SET VMGW: VMGWID=1, MIDTYPE=IP, MID="192.168.167.21:5100", 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=1, MGCIDX=0, MIDTYPE=IP, MID="192.168.167.21:5100", MSS=MASTER, H248VER=V1, PRONEGO=NO, CONTCTRLASSN=NO, DWRAP=NO, ANNEXC=1, OUTADA=1, PERMANENTREQID=0, STREAMMODE=Inactive;ADD H248LNK: LINKID=48, VMGWID=1, MGCIDX=0, TT=SCTP, LOCALIP="192.168.167.21", LOCALPORT=5100, PEERIP="192.168.155.2", PEERPORT=5100, FN=1, SN=11, BP=BACK;

2. 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 MSCserver 2 and related M3UA configuration.

Script ADD M3DE: DEX=2, DEN="SX2", DET=AS, NI=NATB, DPC=H'802, LEX=0, NETTYPE=MSCPOOl;ADD M3DE: DEX=3, DEN="SX2", DET=AS, NI=NATB, DPC=H'802, LEX=1, NETTYPE=MSCPOOl;ADD M3LKS: LSX=1, LSN="SX2", ADX=1;ADD M3RT: RN="SX2", DEX=1, LSX=1;ADD M3LNK: LNK=1, BT=SPF, BN=1, LKN="SX2", LIP1="192.168.167.21", LP=6001, RIP1="192.168.155.2", RP=4100, LSX=1, ASF=ACTIVE;

3. 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 Add a CN node of MSC server 2 and the mapping between NRI andMSC server 2 on MGW 1.


----End

NOTE


Ending the Data Configuration

After all the data is configured, run M3UA and H.248 link maintenance commands of the MSCserver and the MGW on the M2000 to check all the M3UA and H.248 links.




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

MGW1

BSC1

SX2 SX3

MGW2 MGW

3

BSC2

BSC3

BSC4

H248 link M3UA link

unavailable



l Configure related M3UA data on MGW 2 and MSC server 2, and use the existing H.248data.

l Configure related data of the newly added H.248 link and M3UA link on MGW 2 and MSCserver 1.

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


To configure the data on the MSC server, perform the following steps:

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

Description Add an M3UA destination entity, M3UA linkset, M3UA link andM3UA route.




Issue 02 (2008-04-10)


2. 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 MSCserver 1.


3. 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 tointerwork with MGW 2.




6-17

----End


1. Set MSC Pool function information on MGW 2.

Description Set MSC Pool function information on MGW 2.


2. 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 withMSC server 1.


3. 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 withMSC server 1 where Network Type is MSCPOOl.

Script ADD M3LE: LEX=0, LEN="MGW2_NATB", LET=SG, NI=NATB, OPC=H'2C;ADD M3LE: LEX=1, LEN="MGW2_NATB_1", LET=SG, NI=NATB, OPC=H'902;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.172.41", LP=2300, RIP1="192.168.153.1", RP=2300, LSX=0, ASF=ACTIVE;




Issue 02 (2008-04-10)

Description Add the configuration of the SIGTRAN on MGW 2 to interwork withMSC server 2 where Network Type is MSCPOOl.


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





----End

NOTE


Ending the Data ConfigurationAfter all the data is configured, run M3UA and H.248 link maintenance commands of the MSCserver and the MGW on the M2000 to check all the M3UA and H.248 links.






Figure 6-7 shows an MSC Pool including MSC Server 3.



6-19

Figure 6-7 MSC Pool including MSC Server 3

SX1 SX2 SX3

H248 link

MGW1

BSC1

MGW2 MGW

3

BSC2

BSC3

BSC4

M3UA link

unavailable unavailable


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

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


1. Add MGW 1 and MGW 2 on MSC server 3 and H.248 links from MGW 1 to MSC server3 and MGW 2 to MSC server 3.





Issue 02 (2008-04-10)




2. Add related data configuration of the M3UA on MSC server 3 to interwork with MGW 1

and MGW 2.



6-21





----End


1. Add virtual MGWs on MGW 1 and MGW 2, and add an H.248 link to interwork with MSCserver 3.

Description Set a virtual MGW on MGW 1, and add an H.248 link to interworkwith MSC server 3.




Issue 02 (2008-04-10)


Description Set a virtual media gateway on MGW 2, and add an H.248 link tointerwork with MSC server 3.


2. 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 MSCserver 3 and related M3UA configuration on MGW 1.




6-23

Description Add an M3UA destination signaling point for interworking with MSCserver 3 and related M3UA configuration on MGW 2.


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 NRIand MSC server 3 on MGW 1.




----End

NOTE


Ending the Data ConfigurationAfter all the data is configured, run M3UA and H.248 link maintenance commands of the MSCserver and the MGW on the M2000 to check all the M3UA and H.248 links.










Issue 02 (2008-04-10)


MGW1

BSC1

SX2 SX3

MGW2 MGW

3

BSC2

BSC3

BSC4

H248 link M3UA link

SX1

unavailable


l Configure related M3UA data on MGW 3 and MSC server 3, and use the existing H.248data.

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

l After configuring the data of the newly added H.248 link and M3UA link, add mappinginformation on MGW 3. Set Manage Status corresponding to MSC server 1 and MSC server2 to Inhibited.


1. Add related M3UA data on MSC server 3 for interworking with MGW 3.

Description Add an M3UA destination entity, M3UA linkset and M3UA route.


2. Add MGW 3 on MSC server 1 and MSC server 2 and H.248 links from MGW 3 to MSC

server 1 and MSC server 2.



6-25








Issue 02 (2008-04-10)

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

interworking with MGW 3.





----End


1. Set MSC Pool function information on MGW 3.

Description Set MSC Pool function information on MGW 3.


2. Set a virtual media gateway on MGW 3, and add an H.248 link for interworking with MSC

server 1 and MSC server 2.

Description Set a virtual media gateway on MGW 3, and add an H.248 link forinterworking with MSC server 1.



6-27




3. 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 interworkingwith MSC server 1 where Network Type is MSCPOOl.

Script ADD M3LE: LEX=0, LEN="MGW3_NATB", LET=SG, NI=NATB, OPC=H'2D;ADD M3LE: LEX=1, LEN="MGW3_NATB_1", LET=SG, NI=NATB, OPC=H'902;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.175.42", LP=2204, RIP1="192.168.153.1", RP=2204, LSX=0, ASF=ACTIVE;




Issue 02 (2008-04-10)


Script ADD M3DE: DEX=2, DEN="SX2", DET=AS, NI=NATB, DPC=H'802, LEX=0, NETTYPE=MSCPOOL;ADD M3DE: DEX=3, DEN="SX2", DET=AS, NI=NATB, DPC=H'802, LEX=1, NETTYPE=MSCPOOL;ADD M3LKS: LSX=1, LSN="SX2", ADX=1;ADD M3RT: RN="SX2", DEX=1, LSX=1;ADD M3LNK: LNK=1, BT=SPF, BN=1, LKN="SX2", LIP1="192.168.175.42", LP=4300, RIP1="192.168.155.2", RP=4300, LSX=1, ASF=ACTIVE;


Script ADD M3DE: DEX=4, DEN="SX3", DET=AS, NI=NATB, DPC=H'803, LEX=0, NETTYPE=MSCPOOL;ADD M3DE: DEX=5, DEN="SX3", DET=AS, NI=NATB, DPC=H'803, LEX=1, NETTYPE=MSCPOOL;ADD M3LKS: LSX=2, LSN="SX3", ADX=2;ADD M3RT: RN="SX3", DEX=2, LSX=2;ADD M3LNK: LNK=2, BT=SPF, BN=1, LKN="SX3", LIP1="192.168.175.42", LP=4700, RIP1="192.168.151.3", RP=4700, LSX=2, ASF=ACTIVE;

4. 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 2where Manage Status is Inhibited.








6-29


----End

NOTE



After all the data is configured, run M3UA and H.248 link maintenance commands of the MSCserver and the MGW on the M2000 to check all the M3UA and H.248 links.





6.4 Integration with the Access NetworkThis section describes the integration process of the access network when a 2G network evolvesto an MSC Pool network.

6.4.1 Adding BSC 1 into the MSC PoolThis 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 PoolThis section describes the data configuration in the access process of the access network.




6.4.6 Adding BSC4 into the MSC PoolThis section describes the data configuration in the access process of the access network.


The BSC is added into the MSC Pool by following mode:

l Mode 1: Allocate timeslots in the preliminary physical trunks and links. During theevolution 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. Duringthe evolution of the core network, change physical trunks of the BSC, and delete preliminarylinks.

NOTE

For mode 1, the duration of the service interruption is long, and you are advised to use mode 1 when thetrunk resources of the current networking are limited. In mode 1, the signaling point modification of theaccess side and the data modification can be performed simultaneously. Mode 2 is used only when thetrunk resources of the current networking are sufficient.



l Add the M3UA destination entity and M3UA route on MSC server 1 for interworking withBSC 1.

l 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 Statuscorresponding to MSC server 2 and MSC server 3 to Inhibited.


To configure the data on the MSC server, perform the following steps:

1. Add the M3UA destination entity and M3UA route on MSC server 1 for interworking withBSC 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", LSNM="TO_MGW1_NATB";



6-31

Remark Add the M3UA data for MSC server 1 (SPC: 801) to interwork withBSC 1 (SPC: 10B). The M3UA route adopts the link set to MGW 1 forthe quasi-associated networking.

2. 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. Thatis, set MGW manage A interface circuit to Supported.


Remark After enabling the circuit management switch on MGW 1, disable thecircuit management switch of BSC 1 on MSC server 1.

----End

Configuring Data on the MGW Based on Mode 1To configuring data on the MGW based on mode 1, perform the following steps:

1. Set Manage Status corresponding to MSC server 1 to Normal on MGW 1. Activate theMGW. Set the BSC to be in management state. Manage Status corresponding to MSCserver 1 is set to Normal, while Manage Status corresponding to MSC server 2 and MSCserver 3 is set to Inhibited.

2. Delete the configuration of the preliminary signaling of BSC 1 on MGW 1. (The signalingadopts 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, andset Network Type corresponding to N7DSP to MSCPOOl.

Description Add configurations of narrowband signaling (N7DSP) for interworkingwith BSC 1, and set Network Type corresponding to N7DSP toMSCPOOl.

Script 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 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;




Issue 02 (2008-04-10)

Remark Add the MTP2 link from the SPC (902) of MGW 1 to the BSC.Add the MTP3 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 MTProute must be configured because the SP with the SPC 2A is assistedby 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 asA-interface circuit pool, BSC configuration, A-interface circuit trunkgroup, and A-interface circuit.

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="BSC 1", 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;

----End

Configuring Data on the MGW Based on Mode 2To 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 theMGW. Set the BSC to be in management state. Manage Status corresponding to MSCserver 1 is set to Normal, while Manage Status corresponding to MSC server 2 and MSCserver 3 is set to Inhibited.

2. Add the TDMIU data for interworking with BSC 1, and set Relay type to ATRUNK.

Description Add the TDMIU data for interworking with BSC 1, and set Relaytype to ATRUNK.

Script ADD TDMIU: BT=E32, BN=6, TIDFV=64, TIDLV=127, VMGWID=0, RT=ATRUNK;

3. Add configurations of narrowband signaling (N7DSP) for interworking with BSC 1, and

set Network Type corresponding to N7DSP is MSCPOOl.

Description Add configurations of narrowband signaling (N7DSP) for interworkingwith BSC 1, and set Network Type corresponding to N7DSP isMSCPOOl.



6-33

Script 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 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 N7LNK: INDEX=0, NAME="TO_BSC1", LKSIDX=0, SLC=2, SNDSLC=2, TESTCODE=170, MTP2NO=0;

Remark Before adding the destination signaling points of MSC Pool type, youmust delete preliminary N7DSP signaling points unless the newsignaling points are added for the interworking BSC.

4. Add related configurations of A-interface circuit management.

Description Add related configurations of A-interface circuit management, such asA-interface circuit pool, BSC configuration, A-interface circuit trunkgroup, and A-interface circuit.

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="BSC 1", 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;

5. Change the trunk lines of BSC 1, enable the BSC management switch, and perform the

system commissioning.

----End

Configuring Data on the BSCConfigure 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 addBSC 1 into the MSC Pool.

l Mode 2: Change the destination signaling point of BSC 1 by from "DD" to "XX". Modifythe trunk timeslot of BSC 1 for interworking with MGW 1 and add BSC 1 into the MSCPool.

Ending the Data ConfigurationAfter all the data is configured, run signaling link and trunk circuit maintenance commands ofthe MSC server, MGW, and BSC on the M2000 to check all the signaling links and trunk circuits.




l Entire system runs well for at least one Periodic Location Update.




Issue 02 (2008-04-10)




l Add BSC 1on MSC server 2.

l Add paging control data on MSC server 2.

l Disable the A-interface circuit switch of BSC 1 on MSC server 2, which disables MSCserver 2 to manage A-interface circuit of BSC 1.

l Activate the virtual MGW corresponding to MSC server 2 on MGW 1.

Configuring Data on the MSC Server1. Add related data of BSC 1 on MSC server 2.

(1) Add an M3UA destination entity of BSC 1.

Description

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.

Description

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, DPC1="10B", CONFIRM=Y;

(3) Add related data of BSC 1 on MSC server 2.

Description

Add BSC 1 on MSC server 2.

Script ADD BSC: NI=NATB, DPC="10B", OPC="802", BSCNM="BSC 1", CAPABILITY=CCPAGING-1&SMSPAGING-1&SSPAGING-1&PSIPAGING-1&LCS-1&SERVICEHO-1&DTM-1&LOADHO-1&MGWPROXYAFLEX-1&PRIVATEMSG-1&SupportActiveTrace-1, RSSCNAME="SX2", MLAIF=YES, MGWMAC=YES;

(4) Add an M3UA route for interworking with BSC 1.

Description

Add an M3UA route for interworking with BSC 1.



6-35

Script ADD M3RT: RTNM="BSC1", DENM="BSC1", LSNM="TO_MGW1_NATB";

(5) Add an SCCP destination signaling point.

Description

Add an SCCP destination signaling point.

Script ADD SCCPDSP: DPNM="BSC1", NI=NATB, DPC="10B", OPC="802";

(6) Add SCCP subsystems.

Description

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.

Description

Add an A-interface trunk group for the performance measurementof the trunk group on MSC server 2.

Script ADD AIETG: TGNAME="BSC1", MGWNAME="MGW1", SOPC="802", SDPC="10B", CPNAME="BSC1", BTG=1;

2. 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 1on MSC server 2.


3. 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. Thatis, set MGW manage A interface circuit to Supported.


----End


Activate the virtual MGW corresponding to MSC server 2 on MGW 1.




Issue 02 (2008-04-10)

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

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 ofthe MSC server, MGW, and BSC on the M2000 to check all the signaling links and trunk circuits.






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 BSC1 to MSC Server 2 in the MSC Pool, and 6.4.3 Connecting BSC 1 to MSC Server 3 in theMSC Pool.



6.4.6 Adding BSC4 into the MSC PoolThis section describes the data configuration in the access process of the access network.




6-37

6.5 Other Data ConfigurationThis section describes the configuration of other data in the scenario of 2G network evolutionto support MSC Pool.

The procedure for configuring other data in this scenario is the same as the procedure forconfiguring other data in the scenario of new MSC Pool in 2G Network. For details, see therelated description in 5.5 Other Data Configuration in the "New MSC Pool in 2G Network"chapter.

6.6 System CommissioningThis section describes the system commissioning when a 2G network evolves to an MSC Poolnetwork.

Only the new and changed commissioning testing introduced by the MSC Pool feature isdescribed in this section. Other common commissioning must be performed based on the basicprocedures. The commissioning can be performed during the whole evolution process. Thefollowing sections provide a commissioning example. You can make adjustments according tothe 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, MSCserver 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 becommissioned.

Table 6-4 Changing status of MSC servers

NE MSC server 1(Current/Commissioning)

MSC server 2(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

3. Disable the paging over the entire network.






Issue 02 (2008-04-10)

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

5. 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 instruct MSC server 1 to use the existing A-

interface specified dialing test function to test the voice channels. Specify the MGWname 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

Checking Load Redistribution in MSC PoolTo 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


Checking Roaming Handover by Using the Default MSCTo 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. Connect a commissioning subscriber to BSC 2/BSC 3/BSC 4. Repeat steps 1 to 2 until the


Commissioning Disaster Recovery upon Call Termination FailureTo check whether the disaster recovery upon call termination failure in the MSC Pool is normal,perform the following steps:


2. Connect a subscriber to BSC 1 and MSC server 1.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.



6-39

4. Connect a commissioning subscriber to BSC 2/BSC 3/BSC 4. Repeat steps 2 to 3 until thefunction is tested for all BSCs in the MSC Pool area.

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.

l 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 intothe MSC Pool), perform the following steps:

1. Run RMV MTP2LNK to remove the original signaling connections of the BSC. Ifthe original signaling of the BSC is transmitted by TDM semi-permanent links, runRMV 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 doesnot 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 theMSC Pool), you need not remove any data as the M2UA links and TDMIU to the BSC officedirection are removed during the configuration.

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 MSCservers in the MSC Pool.

3. Check the load sharing (number of registered subscribers) between MSC servers and theCPU usage of them by using the real-time monitoring function of the M2000.

4. According to the actual requirements, balance the load of the MSC servers by using thesubscriber redistribution function of the M2000.

This step is optional.

----End

NOTE





Issue 02 (2008-04-10)

7 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 ina 3G network.

7.1 New Target NetworkThis section describes the target networking and data planning of a new MSC Pool in the 3Gnetwork.




7.5 Other Data ConfigurationThis section describes the configuration of other data in the scenario of new MSC Pool in 3Gnetwork.

7.6 System CommissioningThis section describes the system commissioning of a new 3G network in MSC Pool mode.



7-1

7.1 New Target NetworkThis section describes the target networking and data planning of a new MSC Pool in the 3Gnetwork.

If required, you can build a new 3G network in MSC Pool mode. A typical new 3G network ofthis kind highlights the following networking features:

l The core network adopts the softswitch solution in which an MSC is divided into an MSCserver and an MGW.

l The access network adopts the RAN solution in which the RNC supports the Iu-Flexfunction and load sharing.

For details about the networking scenarios of the typical new 3G network, see subsequentdescriptions.

Figure 7-1 shows the networking of a new target network.

Figure 7-1 Networking diagram of a new target network

SX 2

MGW1

RNC1 RNC2 RNC3 RNC4

MGW2


MGW3

SX 3 SX 4

GMSC (TMSC)

STP

HLR/SCP/SMSCSX 1


ATM bearer


The networking of a new target network is as follows:

l MSC servers in an MSC Pool are connected with each other through IP bearers (full-meshconnection). They communicate with each other by using BICC signaling. The protocolstack is BICC/M3UA/SCTP/IP.

l The Mc interface is based on IP. The protocol stack is H.248/SCTP/IP.

l Iu interface signaling and speech channels between the MGW and the RNC are based onTDM. The protocol stack is RANAP/SCCP/MTP3b/SAAL/ATM.




Issue 02 (2008-04-10)

l The control plane of the Iu interface is transferred by the SG embedded in the MGW. IPbearers are adopted between the SG embedded in the MGW and the MSC server. Theprotocol stack is RANAP/SCCP/M3UA/SCTP/IP.

l The Nb interface between the MGWs is based on IP and all MGWs are connected witheach other.

l The MSC server is connected to the pure signaling point NEs, such as the HLR, SCP, andSMC in STP forward mode. The MSC server is connected to the STP directly and thesignaling is based on IP.

l 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 interworkswith external networks through the GMSC. The MSC Pool interworks with local MSCs orremote MSCs in the network through the TMSC.


For details on the networking solutions, see the section "3.3 General Principles of the MSCPool Planning."

Function DescriptionThe 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 CodesUse 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 reservednetwork).

l MSC server 2 uses two SPCs: BB (for international network) and EE (for internationalreserved network).

l MSC server 3 uses two SPCs: CC (for national network) and FF (for national reservednetwork).

l MGW 1 uses one SPC: GG.

l MGW 2 uses one SPC: HH.

l MGW 3 uses one SPC: JJ.

l The RNC retains the existing SPCs.



7-3


SX 1

MGW1

RNC1

SX 2 SX 3

MGW2 MGW

3

RNC2

RNC3

RNC4

AA BB CC

DD EE FF

GG HHJJ

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







End



Configuringservice

data





Issue 02 (2008-04-10)

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


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


Nodename

SX1 SX2 SX3







IPAddress

192.168.153.1 192.168.155.2 192.168.151.3

Lengthof theNRI(bits)


Valueof theNRI


DefaultMSC

You are advised to set all MSC servers in the MSC Pool to default MSCs.

Charging mode


Capacity of anMSCserverin theMSCPool

1 million (recommended)

Valueof NullNRI





7-5


Non-broadcast LAI

460004444 460005555 460006666

Data ofH.248linksbetween theMSCserverand theMGW







Issue 02 (2008-04-10)


Data ofM3UAlinksbetween theMSCserverand theMGW




Table 7-2 Data planning for MGWs in an MSC Pool network

Name MGW1 MGW2 MGW3


SPC 901 902 903


192.168.167.21 192.168.172.41 192.168.175.42

Mapping betweenthe VMGW IDs andthe MSC servers






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 AreaThis section describes the configuration procedure for integrating an MSC Pool with the accessnetwork.


The procedures for configuring the basic data of NEs in an MSC Pool are the same as that forconfiguring NEs in a network without an MSC Pool. For details, see the relevant dataconfiguration 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 inthe 2G Network" chapter.


To preset the data on the MGWs, set the MGWs on the M2000.

Description Connect the MGWs to the O&M system of the M2000. Thus, you canmaintain 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 theonline Help of the M2000.

Replacing TMSIsStart the TMSI reallocation process in the case that the TMSI reallocation function is enabledon the MSC server. Then, wait for the time required by two periodical location updates (theinterval 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 significantnumber 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 networkevolves into an MSC Pool. The purpose of the operation is to keep the target network as similarto the existing network as possible. As a result, the impact of the network evolution on thenetwork operation is minimized.

To allow automatic replacement of TMSIs, you only need to enable the TMSI re-allocationfunction by running the SET MAPACCFG command at appropriate time.

Ending the PresettingAfter two periodical location updates, randomly select 10 subscribers and check whether theirTMSIs 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 1To configure the data of the Mc interface over M3UA links between the MSC server and theMGW, 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.


Description




7-9



Description






Issue 02 (2008-04-10)

(3) On MSC server 1, add MGW 3 and configure the H.248 links between MSC server 1

and MGW 3.

Description



2. On MSC server 1, add the data of M3UA configuration from MSC server 1 to MGW1/

MGW2/MGW3.


Description


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;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";


2.



7-11

Description


Script ADD M3DE: DENM="TO_MGW2_NATB", NI=NATB, DPC="902", STPF=TRUE, DET=SG;ADD M3LKS: LSNM="TO_MGW2_NATB", ADNM="TO_MGW2_NATB", WM=ASP;ADD M3LNK: MN=134, LNKNM="TO_MGW2_NATB", LOCIP1="192.168.153.1", LOCPORT=2302, PEERIP1="192.168.172.41", PEERPORT=2302, CS=C, LSNM="TO_MGW2_NATB", QoS=TOS;ADD M3RT: RTNM="TO_MGW2_NATB", DENM="TO_MGW2_NATB", LSNM="TO_MGW2_NATB";


3.

Description



----End

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

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

Configuring the Data of MGW 1To configure the data of MGW 1, perform the following steps:

1. Configure the local office SPC based on the general planning of the MSC Pool.

Description Configure the local office SPC of MGW 1.

Script SET OFI: NAME="MGW01", INTVLD=NO, INTRESVLD=NO, 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 configurationfrom MGW 1 to MSC server 1.

Description

On MGW 1, add virtual MGWs and the data of H.248 links andM3UA configuration from MGW 1 to MSC server 1.

Script 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;ADD M3LE: LEX=0, LEN="MGW1_NATB", LET=SG, NI=NATB, OPC="901";ADD M3DE: DEX=0, DEN="SX1", DET=AS, NI=NATB, DPC=H'801, LEX=0, 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=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

from MGW 1 to MSC server 2.

Description




7-13

Script SET VMGW: VMGWID=1, MIDTYPE=IP, MID="192.168.167.21:5100", 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=1, MGCIDX=0, MIDTYPE=IP, MID="192.168.167.21:5100", MSS=MASTER, H248VER=V1, PRONEGO=NO, CONTCTRLASSN=NO, DWRAP=NO, ANNEXC=1, OUTADA=1, PERMANENTREQID=0, STREAMMODE=Inactive;ADD H248LNK: LINKID=48, VMGWID=1, MGCIDX=0, TT=SCTP, LOCALIP="192.168.167.21", LOCALPORT=5100, PEERIP="192.168.155.2", PEERPORT=5100, FN=1, SN=11, BP=BACK;ADD M3DE: DEX=0, DEN="SX2", DET=AS, NI=NATB, DPC=H'802, LEX=0, NETTYPE=MSCPOOL;ADD M3LKS: LSX=0, LSN="SX2", ADX=0;ADD M3RT: RN="SX2", DEX=0, LSX=0;ADD M3LNK: LNK=0, BT=SPF, BN=1, LKN="SX2", LIP1="192.168.167.21", LP=4100, RIP1="192.168.155.2", RP=4100, LSX=0, ASF=ACTIVE;

(3) On MGW 1, add virtual MGWs and the data of H.248 links and M3UA configuration

from MGW 1 to MSC server 3.

Description


Script SET VMGW: VMGWID=2, MIDTYPE=IP, MID="192.168.167.21:3300", 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=2, MGCIDX=0, MIDTYPE=IP, MID="192.168.167.21:3300", MSS=MASTER, H248VER=V1, PRONEGO=NO, CONTCTRLASSN=NO, DWRAP=NO, ANNEXC=1, OUTADA=1, PERMANENTREQID=0, STREAMMODE=Inactive;ADD H248LNK: LINKID=48, VMGWID=1, MGCIDX=0, TT=SCTP, LOCALIP="192.168.167.21", LOCALPORT=3300, PEERIP="192.168.151.3", PEERPORT=3300, FN=1, SN=11, BP=BACK;ADD M3DE: DEX=0, DEN="SX3", DET=AS, NI=NATB, DPC=H'803, LEX=0, NETTYPE=MSCPOOL;ADD M3LKS: LSX=0, LSN="SX3", ADX=0;ADD M3RT: RN="SX3", DEX=0, LSX=0;ADD M3LNK: LNK=0, BT=SPF, BN=1, LKN="SX3", LIP1="192.168.167.21", LP=3500, RIP1="192.168.151.3", RP=3500, LSX=0, ASF=ACTIVE;

----End




Issue 02 (2008-04-10)

Configuring the Data of MGW 2

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

Configuring the Data of MGW 3

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

7.4.4 Adding BSCs to the MSC Pool AreaThis section describes the configuration procedure for integrating an MSC Pool with the accessnetwork.

Configuring the Data of MSC server 1

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.

Description

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.

Description

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, DPC1="10B", CONFIRM=Y;

(3) Add access MGWs for RNC 1.

Description

Add access MGWs for RNC 1.

Script ADD RANMGW: OFFICENAME="RNC1", MGWNAME="MGW1"; ADD RANMGW: OFFICENAME="RNC1", MGWNAME="MGW2"; ADD RANMGW: OFFICENAME="RNC1", MGWNAME="MGW3";

(4) Add M3UA routes to RNC 1.

Description

Add M3UA routes to RNC 1.



7-15

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

(5) Add an SCCP DSP for RNC 1.

Description

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.

Description

Add RNC 1 on MSC server 1.

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.

Description

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.

Description

Add an SCCP subsystem

Script

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";

2. 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 areascontrolled by RNC 1.


----End

The procedure for adding RNC 2, RNC 3, and RNC 4 on MSC server 1 is similar to the procedurefor adding RNC 1 on MSC server 1.




Issue 02 (2008-04-10)

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

Configuring the Data of MSC server 3The procedure for configuring the data of MSC server 3 is similar to the procedure forconfiguring the data of MSC server 1 described in "Configuring the Data of MSC server 1."

Configuring the Data of MGW 1To configure the data of MGW 1, perform the following steps:

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

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

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

Configuring the Data of MGW 3The procedure for configuring the data of MGW 3 is similar to the procedure for configuringthe data of MGW 1 described in "Configuring the Data of MGW 1."

Configuring the Data of the RNCTo 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.



7-17

7.5 Other Data ConfigurationThis section describes the configuration of other data in the scenario of new MSC Pool in 3Gnetwork.

The procedure for configuring other data in this scenario is the same as the procedure forconfiguring other data in the scenario of new MSC Pool in 2G Network. For details, see therelated description in 5.5 Other Data Configuration in the "New MSC Pool in 2G Network"chapter.

7.6 System CommissioningThis 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 inthis section. Other commissioning must be performed based on the basic procedures. Thecommissioning can be performed during the evolution of the core network and access of theaccess network. The following sections provide a commissioning example. You can makeadjustments according to the actual requirements.

PreparationsMake 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, MSCserver 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 becommissioned.

Table 7-4 Changing status of MSC servers

NE MSC server 1(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

3. Disable the paging over the entire network.






Issue 02 (2008-04-10)

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

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

5. Check whether the voice channels are normal.

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

(4) Connect a commissioning subscriber to RNC 2/RNC 3/RNC 4. Repeat substeps 1 to4 until the function is tested for all the RNCs in the MSC Pool area.

----End

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 RNC 1 and MSC server 1.

2. The M2000 sends a message to MSC server 1 to redistribute the commissioning subscribersto MSC server 2.

3. After the subscribers are redistributed, the M2000 sends a message to MSC server 2 toredistribute the subscribers to MSC server 3.

4. Connect a commissioning subscriber to RNC 2/RNC 3/RNC 4. Repeat steps 1 to 3 untilthe function is tested for all RNCs 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:


2. After the subscriber roams out of the MSC Pool area, call the subscriber. Check whetherthe voice channel can be set up correctly.

3. Connect a commissioning subscriber to RNC2/RNC3/RNC4. Repeat steps 1 to 2 until thefunction is tested for all RNCs in the MSC Pool area.

Commissioning Disaster Recovery upon Call Termination Failure

To check whether the disaster recovery upon call termination failure in the MSC Pool is normal,perform the following steps:



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. Connect a commissioning subscriber to RNC2/RNC3/RNC4. Repeat steps 2 to 3 until thefunction is tested for all RNCs in the MSC Pool area.



7-19

Trial RunTo carry out trial run, perform the following steps:

1. On the MGW, 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.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.

----End

NOTE





Issue 02 (2008-04-10)

8 3G Network Evolution to Support MSC Pool

About This Chapter

This section describes the data planning and data configuration process of a 3G network evolvingto an MSC Pool network.


8.2 Data ConfigurationThis section describes the overall data configuration flow, data planning, and MSC Poolpresetting of a 3G network evolving to an MSC Pool network.

8.3 Evolution of the Core NetworkThis section describes the evolution of the core network of a 3G network evolving to an MSCPool network.

8.4 Access of the Access NetworkThis section describes the access of the access network of a 3G network evolving to an MSCPool network.

8.5 Other Data ConfigurationThis section describes other data configuration of a 3G network evolving to an MSC Poolnetwork.




8-1


Evolution of an existing 3G network into an MSC Pool is a way in which the MSC Pool solutionis applied. A typical 3G network has the following characteristics:

l The core network adopts the softswitch networking structure, which consists of MCSservers and MGWs.

l The access network adopts the radio access network (RAN) system. The RNC supports theIu-Flex function and has the load distribution capability.

This section describes how a typical existing 3G network evolves into an MSC Pool.

8.1.1 Description of the Existing NetworkThis section describes the existing network.

8.1.2 Description of Target NetworkThis section describes the target network.

8.1.1 Description of the Existing NetworkThis 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

MGW1

RNC1 RNC2 RNC3 RNC4

MGW2


MGW3

SX 2 SX 3

GMSC (TMSC)

STP

HLR/SCP/SMSC


ATM bearer

This chapter describes how an existing 3G network evolves into an MSC Pool by taking thenetwork shown in Figure 8-1 as an example.




Issue 02 (2008-04-10)

Networking DescriptionThe 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 theMGW (as the SG) through M3UA links.

l The Iu-interface signaling and voice channels between the MGW and RNC are based onthe ATM bearer.

l The Nb interface between MGWs is based on the TDM bearer. Not all MGWs are directlyconnected.

l Based on the TDM bearer, the signaling and voice channels of the MGW are directlyconnected to the GMSC (TMSC) in the outgoing direction.

l Based on IP bearer, the signaling of the MSC server is transferred through the STP andthen is routed to the HLR/SCP/SMSC.

Function DescriptionThe function of the existing network is as follows:

l None of the NEs has the Iu-Flex function enabled.

l The virtual MGW function is not enabled on the MGW.

Usage Description of Signaling Point CodesThe signaling point codes (SPCs) are used as follows:



l MSC server 3 uses two SPCs (CC for national network and FF for national reservednetwork).

l Each MGW uses an SPC.

l Each RNC uses an SPC.

8.1.2 Description of Target NetworkThis section describes the target network.

Figure 8-2 shows the networking diagram of a target network which has adopted the MSC Poolsolution and has evolved from an existing 3G network.



8-3

Figure 8-2 Networking diagram of a target network

SX 2

MGW1

RNC1 RNC2 RNC3 RNC4

MGW2


MGW3

SX 3 SX 4

GMSC (TMSC)

STP

HLR/SCP/SMSCSX 1


ATM bearer

As shown in Figure 8-2, the MGWs are fully connected. The signaling channels between theMGWs and the STP, and the voice channels between the MGWs and the GMSC (TMSC) arebased on the IP bearer. The following describes the networking of the target network in furtherdetails.

Networking DescriptionThe networking of the target network is as follows:

l The MSC servers in the MSC Pool are fully connected. The links between them are basedon the IP bearer. The MSC servers communicate using the BICC signaling. The Nc interfacebetween the MSC servers adopts the protocol stack BICC/M3UA/SCTP/IP.

l The Mc interface is based on the IP bearer. It adopts the protocol stack H.248/SCTP/IP.

l The Iu-interface signaling and voice channels between the MGW and RNC are based onthe ATM bearer. The Iu interface adopts the protocol stack RANAP/SCCP/MTP3b/SAAL/ATM.

l The control plane signaling transmitted over the Iu interface is forwarded by the built-inSG of the MGW. The build-in SG of the MGW communicates with the MSC server overthe IP bearer. It adopts the protocol stack RANAP/SCCP/M3UA/SCTP/IP.

l The Nb interface between MGWs is based on the IP bearer. The MGWs are fully connected.

l Based on IP bearer, the signaling from the MSC servers is transferred through the STP andthen is routed to the HLR/SCP/SMC.

l 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 GMSCthrough the MGWs, they can communicate with the external network; when they areconnected to the TMSC through the MGWs, they can communicate with the other localMSCs 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 PoolPlanning.

Function DescriptionThe function of the target network is as follows:

l The Iu-Flex function is enabled on the RNCs.

l The virtual MGW function is enabled on the MGWs.

Usage Description of Signaling Point CodesThe standard M3UA forwarding networking mode is adopted.

The SPCs are used as follows:



l MSC server 3 uses two SPCs (CC for national network and FF for national reservednetwork).

l MGW 1 uses an SPC (GG).

l MGW 2 uses an SPC (HH).

l MGW 3 uses an SPC (JJ).

l 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 SPCsused in the target network.


SX 1

MGW1

RNC1

SX 2 SX 3

MGW2 MGW

3

RNC2

RNC3

RNC4

AA BB CC

DD EE FF

GGHH

JJ

8.2 Data ConfigurationThis section describes the overall data configuration flow, data planning, and MSC Poolpresetting of a 3G network evolving to an MSC Pool network.



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







End



Configuringservice

data


As shown in Figure 8-4, the basic data configuration of the MSC Pool is classified into dataplanning, evolution of the core network (CN), access of the access network, and configurationof service data. The detailed configuration steps are described in the following sections.

8.2.1 Data PlanningThis section describes the data planning of the MSC Pool.


8.2.1 Data PlanningThis 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


Node name SX1 SX2 SX3







Issue 02 (2008-04-10)





IP address 192.168.153.1 192.168.155.2 192.168.151.3

Length ofthe NRI(bits)


Value ofthe NRI


DefaultMSC

You are advised to set all MSC servers in the MSC Pool to default MSC.

Chargingmode


Capacity ofthe MSCserver inthe MSCPool

1 million

Value ofNull NRI

10 (recommendedvalue)



CN ID 1 (recommended value) 2 (recommended value) 3 (recommended value)

Non-broadcastLAI

460004444 460005555 460006666



8-7


Data of H.248 linksbetweenthe MSCserver andMGW







Issue 02 (2008-04-10)


Data ofM3UALinksbetweenthe MSCserver andMGW




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



SPC 901 902 903


192.168.167.21 192.168.172.41 192.168.175.42



8-9


Mapping betweenthe VMGWIDs andthe MSC servers




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 inthe 3G Network" chapter.

8.3 Evolution of the Core NetworkThis section describes the evolution of the core network of a 3G network evolving to an MSCPool network.

8.3.1 OverviewThis section describes the evolution process of the core network.

8.3.2 Adding MSC Server 2 to the MSC PoolThis section describes the data configuration in the evolution process of the core network.

8.3.3 Adding MGW 2 to the MSC PoolThis section describes the data configuration in the evolution process of the core network.






Issue 02 (2008-04-10)

8.3.1 OverviewThis section describes the evolution process of the core network.

The evolution process consists of:

l Evolution of the core network

l Access of the access network

l System commissioning

You can perform the evolution of the core network, and then connect the NEs to the MSC Poolone by one. After the evolution of the core network is completed, you can perform the systemcommissioning on the CN side (optional). You must perform the commissioning of the wholeMSC Pool system after each NE of the access network is connected to the MSC Pool. Thismanual describes only the commissioning tasks specific to the MSC Pool solution. The commoncommissioning tasks, such as the commissioning that is performed after an NE is added, are notdescribed.

The process of evolution into an MSC Pool for an existing 3G core network is similar to that foran existing 2G core network. The difference is that the data of M3UA links between MSC server1 and MGW 1 in the existing 3G network is already configured. (The data of M3UA linksbetween MSC server 2 and MGW 2, and that between MSC server 3 and MGW 3 is alsoconfigured.) Therefore, for the evolution of the existing 3G network, the relevant configurationis not required anymore.

Now that the data of the M3UA links between MSC server 1 and MGW 1 in the existing 3Gnetwork is configured, MSC server 1 and MGW 1 can be considered as an MSC Pool. Thus, theevolution 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.

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





8-11


SX1

MGW1

RNC1

SX2 SX3

MGW2 MGW

3

RNC2

RNC3

RNC4

H248 link M3UA link

unavailable

Key Points of the Entire ConfigurationConfigure related data of the newly added H.248 links and M3UA links on MGW 1 and MSCserver 2.


1. Add MGW 1 on MSC server 2 and an H.248 link between MGW 1 and MSC server 2.

Description Add MGW 1 on MSC server 2 and an H.248 link between MGW 1 andMSC server 2.




Issue 02 (2008-04-10)


2. Add related data configuration of the M3UA on MSC server 2 for interworking with MGW

1.



----End


1. Set a virtual media gateway on MGW 1, and add an H.248 link for interworking with MSCserver 2.




8-13


2. Add an M3UA destination signaling point for interworking with MSC server 2 and relatedM3UA configuration.

Description Add an M3UA destination signaling point for interworking with MSCserver 2 and related M3UA configuration.

Script ADD M3DE: DEX=2, DEN="SX2", DET=AS, NI=NATB, DPC=H'802, LEX=0, NETTYPE=MSCPOOL;ADD M3LKS: LSX=1, LSN="SX2", ADX=1;ADD M3RT: RN="SX2", DEX=1, LSX=1;ADD M3LNK: LNK=1, BT=SPF, BN=1, LKN="SX2", LIP1="192.168.167.21", LP=4100, RIP1="192.168.155.2", RP=4100, LSX=1, ASF=ACTIVE;

----End

NOTE

The current data is newly added data. If you need to roll back the data configuration, delete the added data.


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



l The services pass the dialing test.

l In the entire system, at least one periodic location update is completed normally.






Issue 02 (2008-04-10)


SX1

MGW1

RNC1

SX2 SX3

MGW2 MGW

3

RNC2

RNC3

RNC4

H248 link M3UA link

unavailable

Key Points of the Entire ConfigurationConfigure related data of the newly added H.248 link and M3UA link on MGW 2 and MSCserver 1.

Configuring Data on the MSC ServerTo 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.




8-15



2.



----End


1. Set a virtual media gateway on MGW 2, and add an H.248 link for interworking with MSCserver 1.





Issue 02 (2008-04-10)


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

Description Add the configuration of the SIGTRAN on MGW 2 for interworkingwith MSC server 1 where Network Type is MSC Pool.


----End

NOTE



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









8-17


SX1 SX2 SX3

H248 link

MGW1

RNC1

MGW2 MGW

3

RNC2

RNC3

RNC4

M3UA link


Key Points of the Entire ConfigurationConfigure related data of the newly added H.248 link and M3UA link on MGW 1, MGW 2, andMSC server 3.


1. Add MGW 1 and MGW 2 on MSC server 3 and H.248 links between MSC server 3 andMGW 1, and between MSC server 3 and MGW 2.





Issue 02 (2008-04-10)





1 and MGW 2.



8-19





----End


1. Add virtual media gateways on MGW 1 and MGW 2, and add an H.248 link forinterworking with MSC server 3.





Issue 02 (2008-04-10)




2. Add M3UA destination signaling points for interworking with MSC server 3 and related

M3UA configuration on MGW 1 and MGW 2.





8-21



----End

NOTE




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




MGW1

RNC1

SX2 SX3

MGW2 MGW

3

RNC2

RNC3

RNC4

H248 link M3UA link

SX1





Issue 02 (2008-04-10)

Key Points of the Entire ConfigurationConfigure related data of the newly added H.248 link and M3UA link on MGW 3, MSC server1 and MSC server 2.


1. Add MGW 3 on MSC server 1 and MSC server 2 and H.248 links from MGW 3 to MSCserver 1 and MSC server 2.






8-23


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

interworking with MGW 3.







Issue 02 (2008-04-10)


----End


1. Set a virtual media gateway on MGW 3, and add an H.248 link for interworking with MSCserver 1 and MSC server 2.






8-25


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


Script ADD M3LE: LEX=1, LEN="MGW3_NATB_1", LET=SG, NI=NATB, OPC=H'903;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.175.42", LP=2204, RIP1="192.168.153.1", RP=2204, LSX=0, ASF=ACTIVE;



----End

NOTE






Issue 02 (2008-04-10)





8.4 Access of the Access NetworkThis section describes the access of the access network of a 3G network evolving to an MSCPool network.

8.4.1 Connecting RNC 1 to MSC Server 1 in the MSC PoolThis section describes the data configuration in the access process of the access network.



8.4.4 Adding RNC 2 to the MSC PoolThis section describes the data configuration in the access of the access network.


8.4.6 Adding RNC 4 to the MSC PoolThis section describes the data configuration in the access process 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 theMSOFTX3000s and the RNCs. The signaling between an MSOFTX3000 and an MGW istransmitted over the IP bearer and the signaling between the MGW and the RNC is transmittedover the ATM bearer. New links need to be configured with the evolution of the network.

General Configuration ItemsGeneral configuration items are as follows:

l On the MSC server 1, modify configuration of RNC 1 so that it supports the Iu-Flexfunction.

l On the MSC server 1, add an access media gateway and a route from MSC server 1 to RNC1.

l On the MGW, activate the virtual MGW corresponding to MSC server 1.

Configuring Data on the MSC ServerFor 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



8-27

MSC server 1 > MGW 2 > RNC 1 and MSC server 1 > MGW 3 > RNC 1 is configured whenMGW 2 and MGW 3 is being added to the MSC Pool. Thus, the data of the M3UA links fromMSC server 1 to RNC 1 need not be configured. The corresponding MGWs and the signalingroutes, however, need to be added.

1. Configure the access media gateway.

Description Configure the access media gateway.

Script ADD RANMGW: OFFICENAME="RNC1", MGWNAME="MGW2"; ADD RANMGW: OFFICENAME="RNC1", MGWNAME="MGW3";

2. Add a route.

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

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

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


----End

Configuring Data on the MGWTo configure data on the MGW, perform the following steps:

1. Activate the virtual MGW corresponding to MSC server 1 on MGW 2.

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


2. Configure the data of the signaling and voice channels from MGW 2 to RNC 1.

For details, refer to the UMG8900 Configuration Example.3. Activate the virtual MGW corresponding to MSC server 1 on MGW 3.

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


4. Configure the data of the signaling and voice channels from MGW 3 to RNC 1.

For details, refer to the UMG8900 Configuration Example.

----End




Issue 02 (2008-04-10)

Configuring Data on the RNCNOTE

The commands used to configure the data of the RNC vary with the manufacturers of the equipment usedin 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 andRNC on the M2000 to check all the links.








l Add RNC 1on MSC server 2.

l Add paging control data on MSC server 2.

l Activate the virtual MGW corresponding to MSC server 2 on MGW 1.


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.

Description

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.

Description

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.

Description

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.

Description

Configure the M3UA routes between MSC server 2 and RNC 1.

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

(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 Add RNC 1 on MSC server 2.

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.

Description On MSC server 2, configure RNC 1 to support the Iu-Flex function.





Issue 02 (2008-04-10)

(8) Add an SCCP subsystem.

Description

Add an SCCP subsystem.

Script

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";

2. 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 onMSC server 2.


--------End


The procedure for configuring data on the MGW when connecting RNC 1 to MSC server 2 inthe MSC Pool is similar to that when connecting RNC 1 to MSC server 1 in the MSC Pool. Fordetails, 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 > MGW1 > 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, andBSC on the M2000 to check all the links.

You can proceed with the next step if the following conditions are met:





The process of connecting RNC 1 to MSC server 3 in the MSC Pool is similar to that forconnecting RNC 1 to MSC server 2. For details, see section 8.4.2 Connecting RNC 1 to MSCServer 2 in the MSC Pool.



8-31


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


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

8.4.6 Adding RNC 4 to the MSC PoolThis section describes the data configuration in the access process of the access network.

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

8.5 Other Data ConfigurationThis section describes other data configuration of a 3G network evolving to an MSC Poolnetwork.

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.6System Commissioning in the "New MSC Pool in the 3G Network" chapter.




Issue 02 (2008-04-10)

9 Routine Maintenance

About This Chapter

This section describes the routine maintenance operations of the MSC Pool, including settingthe attributes of an MSC Pool, checking the alarms of an MSC Pool, monitoring the MSC Poolload in real time, querying the performance report of the MSC Pool, manual redistribution ofsubscribers, and checking MSC Pool data.

9.1 Setting the Attribute Parameters of an MSC PoolThis section describes how to set or modify the attribute parameters of the MSC Pool throughthe M2000.

9.2 Checking the Alarms of the MSC PoolThis section describes how to check the alarm information on the MSC Pool through theM2000.

9.3 Monitoring MSC Pool Load in Real TimeThis section describes how to monitor the load of the MSC Pool in real-time through theM2000.

9.4 Reviewing the MSC Server which Is Serving the Specified SubscriberThis section describes how to review the MSC server serving the specified subscriber throughthe M2000.

9.5 Querying the Performance Report of the MSC PoolThis section describes how to query the performance report of the MSC Pool through theM2000.

9.6 Manual Migration of SubscribersThis section describes how to perform manual migration of subscribers through the M2000.

9.7 Auditing MSC Pool DataThis section describes how to auditing MSC Pool data through the M2000.

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual 9 Routine Maintenance


9-1

9.1 Setting the Attribute Parameters of an MSC PoolThis section describes how to set or modify the attribute parameters of the MSC Pool throughthe M2000.

The setting of the parameters closely relating to the MSC Pool attributes, such as NRI and theparameters pertaining to load balancing, must be consistent with the access network (AN) andthe core network (CN) sides. Using the centralized management function provided by theM2000, 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 ParametersThis section describes the parameters relating to the attributes of the MSC Pool. It also describeshow the setting of each of the parameters affects the operation of the MSC Pool.

9.1.2 Reviewing the Attribute Parameters of an MSC PoolThis section describes how to review the parameters relating to the MSC Pool attributes on theM2000.

9.1.3 Adding NRI for an MSC PoolThe NRI is a part of the TMSI. When the length of existing TMSIs is insufficient for the numberof subscribers, you can increase the number of subscribers that can be served by an MSC serverin 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 IDThis section describes how to set the mapping between the NRI and the CN ID.

9.1.5 Setting NRI Length and Null NRIThis section describes how to set the NRI length and Null NRI.

9.1.6 Setting the Parameters Relating to Load Balancing of the MSC PoolThis 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 PoolThis 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 PoolThis section describes how to set the maintenance status of an NE in the MSC Pool.

9.1.1 Description of the MSC Pool Attribute ParametersThis section describes the parameters relating to the attributes of the MSC Pool. It also describeshow 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 alsodescribes 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 Routine MaintenanceHUAWEI MSOFTX3000 Mobile Softswitch Center



Issue 02 (2008-04-10)

Table 9-1 Description of the parameters relating to the attributes of the MSC Pool

Parameter Description Effect on the Operation of the MSCPool

CN ID The identity of a CN node. It uniquely identifies an MSC server in the MSCPool.

NRI The network resource identifier.It identifies the MSC serverserving a specified mobilestation (MS)/user equipment(UE). Bits 14 to 23 of the TMSIare reserved for the NRI. TheNRI has a configurable length of0 through 10 bits.l When the length of the NRI is

not 0, the NRI must start at bit23 of the TMSI.

l When the length of the NRI is0, you can infer that thesystem does not support theMSC Pool function.

When an MS/UE registers on an MSCserver in the MSC Pool for the first time,the MSC server assigns a TMSIcontaining the NRI of the local MSCserver to the MS/UE. Later, when theMS/UE initiates a service, it includes theNRI in the service request sent to theNAS node selection function (NNSF)node (MGW or RNC), which then routesthe service request to the correspondingMSC server based on the NRI. In thisservice implementation mode, when anMS/UE roams within the MSC Pool, itsserving MSC server remains the sameone. Comparing with the traditionalnetwork, this can reduce the amount oflocation update signaling traffic over theC/D interface greatly.

Non-broadcastLAI

A special location area identity(LAI).It is uniformly codedtogether with the ordinary LAI.The non-broadcast LAI is usedto identify an MSC server in theMSC Pool. Each MSC server inthe MSC Pool has a unique non-broadcast LAI.

Each MSC server within the MSC Poolmust be configured with the non-broadcast LAI of every other MSCserver in the MSC Pool. The function ofthe non-broadcast LAI is as follows:l When MSs/UEs are migrating to

another MSC server, the non-broadcast LAI is used to trigger theimmediate location update to theMSs/UEs served by the original MSCserver.

l When MSs/UEs are migrating toanother MSC server, the target MSCserver determines the address of theoriginal MSC server based on thenon-broadcast LAI of the originalMSC server, and then obtains thesubscriber information (such as theIMSI and the unused encryptionparameters) from the original MSCserver.



9-3


Pool AvailableCapacity

The capacity of an MSC serverin the MSC Pool minus thenumber of subscribers of anRNC/BSC which is outside theMSC Pool area and is served bythe MSC server, if any.NOTE

NOTE

An MSC server in the MSC Poolcan also serve an RNC/BSCoutside the MSC Pool areaindependently of other MSCservers in the MSC Pool. The valueof the parameter Pool AvailableCapacity should be the capacity ofthe MSC server minus the numberof subscribers of the RNC/BSCoutside the MSC Pool area.

The system distributes the subscribertraffic to different MSC servers based onthe value of Pool Available Capacity ofeach MSC server in the MSC Poolevenly.

MGWSegregateStatus

The state of an MGW when theMGW is isolated. At this time,the MGW continues processingthe ongoing service but does notaccept any new service request.NOTE

NOTE

l The MGWs mentioned hererefers to the VMGWs providingthe Iu-Flex function.

l A physical MGW is dividedinto several virtual MGWsbased on its logical functions.

Setting an MGW into isolated stateensures smooth exit of an MGW fromthe system and avoids impact on theservice provisioning.

CN NodeStatus

The state of an MSC server inthe MSC pool. Its value can beNormal, OffLoad, Forbidden,and Unknown.

In normal cases, the MSC server is inNormal state. When MSs/UEs aremigrating to another MSC server, youneed to set the state of the MSC serveroriginally serving the subscribers toUninstall. Set the state of an MSC serverin an MSC pool to Forbidden when youwant to upgrade the MSC server after theMSC server is isolated. When an MSCserver is in Forbidden state, the RNCdoes not send any service request to theMSC server.

Iu-FlexActivatedStatus

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.

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




Issue 02 (2008-04-10)


Length of NRI The length of the NRI. The NRIis contained in the TMSIassigned to an MS/UE by anMSC server. The number ofdigits occupied by the NRI in theTMSI is the length of the NRI.

Setting the NRI length is a prerequisitefor the NNSF node (such as the MGWor RNC) to obtain the NRI informationfrom the TMSI, and then sends the MS/UE request to the corresponding MSCserver.NOTE

NOTE

Setting of Length of NRI on the MSCservers in the MSC Pool and the setting ofthe parameter on the RNCs in the servedMSC Pool area must be the same.

Null NRI The special NRI. It is uniformlycoded with the ordinary NRI.

When subscribers are migrating toanother MSC server in the MSC Pool,this parameter is used to instruct theRNC/BSC to select the correct MSCserver for the subscribers. Null NRI isunique in an MSC Pool.

9.1.2 Reviewing the Attribute Parameters of an MSC PoolThis section describes how to review the parameters relating to the MSC Pool attributes on theM2000.

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

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



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 Settingdialog box appears.




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 PoolThe NRI is a part of the TMSI. When the length of existing TMSIs is insufficient for the numberof subscribers, you can increase the number of subscribers that can be served by an MSC serverin 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 prerequisitesare 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 serverthrough the M2000.

NOTE

Changing the NRIs affects the service provisioning greatly. Therefore, it is recommended to plan the NRIsin advance, and then add them through the M2000 Client.

To add NRI for an MSC Pool, perform the following steps:



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.


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

Step 8 Click Apply. The NRI you just added is applied and 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 IDThis 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 (suchas the MGW and the RNC) to send the MS/UE request to the corresponding MSC server basedon the NRI. Generally, the mapping between the NRI and the CN ID is determined at the networkplanning of the MSC Pool. If the network planning has some defects or needs adjusting, you canreset the mapping between the NRI and the CN ID through the M2000.




Issue 02 (2008-04-10)

Before you set the mapping between the NRIs and the CN IDs, ensure that the followingprerequisites are fulfilled:



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 theNRI and the CN ID.


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 withthe mapping between the CN IDs and the NRIs of all the MSC servers in the MSC Pool. Themeaning of the add and remove operations vary with the networking types of the MSC Pool, asshown in Table 9-2.

Table 9-2 Meaning of the add and remove operations

Networking Type ofthe MSC Pool

Meaning of the Operation

MSC Pool consists of CNNEs 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 ofthe MSC Pool

Meaning of the Operation

MSC Pool consists ofaccess network (AN) NEsonly

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

MSC Pool consists of bothCN and AN NEs

Modify: Modify the NRIs of a specified MSC server and modifythese NRIs on all the RNCs/BSCs.Remove: Remove the NRIs of a specified MSC server andremove 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 clickUndo on the NRI Setting tab to cancel the modification of the NRI.

----End

9.1.5 Setting NRI Length and Null NRIThis 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 alack of NRI resource, you can reset Length of NRI through the M2000. The NNSF node (suchas the MGW or RNC) obtains the NRI information from the TMSI based on the NRI length, andthen sends the MS/UE request to the corresponding MSC server. You can set the Null NRI todifferent 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:



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 networkbefore performing the operation.

To set Length of NRI and Null NRI, perform the following steps:

Procedure





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


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

Step 7 Click OK.

The new NRI length or Null NRI is displayed in the list on the Advanced Setting tab withat 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 MSCPool

This section describes how to set the parameters relating to load balancing of MSC Pool.



9-11

PrerequisiteAfter an MSC Pool is established, you need to set the capacity of each MSC server in the MSCPool. This setting serves as a guide for the RNC to distribute the accessed subscribers to differentMSC servers in the MSC Pool.

Before you set the parameters relating to the load balancing of the MSC Pool, ensure that thefollowing prerequisites are fulfilled:



To set the parameters relating to the load balancing of the MSC Pool, perform the followingsteps:

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

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.




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 PoolThis section describes how to set the non-broadcast LAI of the MSC Pool.

PrerequisiteWhen the subscribers of an MSC Pool are migrating, the target MSC server determines theaddress of the original MSC server serving the subscribers based on the non-broadcast LAI, andthen obtains the subscriber information from the original MSC server. The non-broadcast LAIof each MSC server in the MSC Pool is determined at the network planning. If the networkplanning requires changed, you can modify non-broadcast LAI of each MSC server through theM2000.

Before you set the non-broadcast LAI of the MSC Pool, ensure that the following prerequisitesare fulfilled:



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 Non-broadcast LAI.

Step 3 Right-click the MSC Pool and choose Pool Parameter Setting.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.




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

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 PoolThis section describes how to set the maintenance status of an NE in the MSC Pool.

PrerequisiteTo isolate the MGW for subscriber migration, set the maintenance status of an NE in the MSCPool through the M2000. The maintenance status of an NE can be MGW Segregate Status orCN Node Status.

Before you set the maintenance status of an NE in the MSC Pool, ensure that the followingprerequisites are fulfilled:



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

Step 3 Right-click the MSC Pool and choose Pool Parameter Setting.

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

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 PoolThis section describes how to check the alarm information on the MSC Pool through theM2000.

By checking the alarms generated for the MSC Pool, you can monitor the status of the MSCPool 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 PoolThis section describes how to check the fault alarms of the MSC Pool.

9.2.2 Checking the Event Alarms of the MSC PoolThis section describes how to check the event alarms of the MSC Pool.

9.2.1 Checking the Fault Alarms of the MSC PoolThis section describes how to check the fault alarms of the MSC Pool.



9-15

PrerequisiteThe M2000 generates a fault alarm when the load is unevenly distributed among the MSC serversin the MSC Pool. By setting various query conditions, you can quickly detect any unbalancedload 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 arefulfilled:



ContextFault alarms refer to the alarms generated when the load of the MSC Pool is distributed unevenlyamong 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 iconcorresponding to the required IE and the alarm bubble chart on the topology of the M2000 orthe MSC Pool. When a fault alarm is generated for an NE, the icon of the NE is displayed in thecolor of critical alarm. Additionally, an alarm bubble chart showing the alarm level identifierand 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.l Choose Fault > Current Fault Alarms.

l Click on the toolbar.Figure 9-10 shows the Filter dialog box.




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. Click the Base Setting tab, and then set Occurrence Time Range of the alarm.



9-17

Figure 9-12 Base Setting tab

CAUTIONCritical in the Level area and Internal in the Type area must be selected. By default, all theoptions 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 PoolThis 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 theMSC Pool is inconsistent. By setting various query conditions, you can quickly detect any datainconsistency on the MSC servers and/or MGWs in the MSC Pool of your concern and takeadequate 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 arefulfilled:






Issue 02 (2008-04-10)

ContextThe M2000 generates the event alarms on automatic detection of data inconsistency. The alarmtype 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.l Choose Fault > Event Alarm.

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


Step 4 Click OK.The query results are displayed in Current Fault Alarms interface.

----End

9.3 Monitoring MSC Pool Load in Real TimeThis section describes how to monitor the load of the MSC Pool in real-time through theM2000.

During normal operation, the system uses the MSC Pool load-balancing algorithm to keep abalanced distribution of the load among the MSC servers in an MSC Pool. Whereas, the loaddistribution of the MSC Pool might be unbalanced when the NE/links are faulty, the network isbeing adjusted, or the subscribers are migrating. Therefore, you need to monitor the loaddistribution of the MSC Pool in real time and take adequate measures, such as subscribermigration, to ensure constant balance of the load distribution.

9.3.1 Setting the Real-Time Monitoring of the MSC PoolThis section describes how to set the real-time monitoring of the MSC Pool.

9.3.2 Counters of MSC Pool Real-time Monitoring



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 PoolThis 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 distributionvariation of the MSC servers in the MSC Pool in a histogram or curve graph. By checking thesecharts, you can obtain real-time information on the number of subscribers, the CPU usage of theMSC servers, and the number of MGW contexts.

Before you set the real-time monitoring of the MSC Pool, ensure that the following prerequisitesare fulfilled:



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; thehorizontal coordinate represents the time of the monitoring.

l Bar graph: The vertical coordinate represents the value of the monitoring counter; thehorizontal coordinate represents the monitored object.

When you monitor multiple MSC servers at the same time, you can learn the information on theload 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 loadbalancing of the MSC Pool by checking the subscriber quantity histogram.

l If the capacity varies with the MSC server, place the cursor on an MSC server object. TheM2000 displays the ratio of the used MSC server capacity. Through the ratio of the usedMSC server capacity and the actual load of the MSC sever in the histogram, you can learnabout 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.




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 tobe 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 themonitoring period you specified. The monitor period can be 30 seconds, 1, 2, 5, 10, or 20minutes.


Step 5 Click OK.

The query results are displayed in Current Fault Alarms interface.

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.

l Export Data: To export the monitoring data into a file of .csv format.

l Print: To print the graph.



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 secondmonitor 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 MonitoringThis 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, CPUOccupancy 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 Description

SubscriberQuantity

Total The total number of subscribers on the MSC server.

Conversation The number of subscribers in conversation on the MSCserver.

Idle The number of subscribers in idle state on the MSC server.

Power-Off The number of subscribers in power-off state on the MSCserver.

CPU Occupancy Rate CPU usage of the MSC server.

Number of MGW Contexts The total number of contexts created by the MSC serverunder the control of the VMGW.

9.4 Reviewing the MSC Server which Is Serving theSpecified Subscriber

This section describes how to review the MSC server serving the specified subscriber throughthe M2000.

Prerequisite

In the MSC Pool, there is no mapping between the RNC and the MSC server. Subscribers servedby the same RNC may be served by different MSC servers. Through the subscriber searchfunction of the M2000, you can locate the MSC server serving the specified subscriber in theMSC Pool.

Before you view the MSC serving the specified subscriber, ensure that the followingprerequisites are fulfilled:




Issue 02 (2008-04-10)



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 areas follows:



9-23

l MSISDN: It is short for mobile station international ISDN number. It refers to the numberrequired for calling a mobile subscriber.

l IMSI: It is short for international mobile subscriber identify. It refers to the unique identityallocated 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.l 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.l 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 PoolThis section describes how to query the performance report of the MSC Pool through theM2000.

PrerequisiteAfter an MSC Pool is created, certain measurement entities of a single NE, such as mobile officedirection traffic, call connection ratio, call drop rate, and local network traffic, fail to serve asthe performance measurement information of the entire network. By querying the performancereport of the MSC Pool, you can summarize the performance measurement results reported byNEs and obtain the entity data that provides global reference for routine operation andmaintenance and network adjustment.

Before you query the performance report of the MSC Pool, ensure that the followingprerequisites are fulfilled:



To query the performance report of the MSC Pool, perform the followings steps:

ProcedureStep 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.l 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 thereport or right-click the report and choose Query.




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 bequeried based on the time dimension. For example, if you select 15 Minutes from the Timedimension drop-down list box, the M2000 summarizes the performance entity measurementresults every 15 minutes.

l 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 NEsin the same MSC Pool. For example, Call attempt times of local network 1 (all) = Callattempt 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 indifferent networks in an MSC Pool. For example, Call attempt times of MSC1 = Callattempt 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 sameMSC Pool. For example, Call attempt times of an MSC Pool = Call attempt times ofMSC1 + Call attempt times of MSC2.

l Select an object to be queried in the Object range area.

l Choose a time period in the Time range area.



9-25

l Click Filter counter to display the Filter Counter dialog box as shown in Figure 6-16, andthen 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 SubscribersThis 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 MSCservers to other MSC servers in the same MSC Pool. Thus, you can perform maintenanceoperations on the MSC servers and subscribers can still keep the services properly at the sametime.

Before you perform manual migration of subscribers, ensure that the following prerequisites arefulfilled:





Issue 02 (2008-04-10)


l Before you perform subscriber migration, ensure that you have viewed the load of NEs inthe current network through the real-time load monitor function of the M2000 so that youcan select a proper migration mode.

ContextThe migration modes are as follows:

l Mode 1: The cooperation of the NE (such as RNC or MGW) that provides the Iu-Flexfunction is required. You must set the status of the MSC server from which subscribersmigrate 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.

l Mode 2: The cooperation of the NE that provides the Iu-Flex function is not required. Youonly need to specify a destination MSC server, and the system routes data of the subscriberswho migrate to the specified MSC server.

NOTE

l After you complete subscriber migration in mode 1, restore the status of the MSC server configuredon the MSC server and the RNC to Normal through the M2000 Client.

l In mode 2, you can designate the NRI of the specified destination MSC server on the M2000, and thusthe operation can be implemented in only the core network without the cooperation of the accessnetwork.

When mode 1 is adopted, the principles of subscriber migration between MSC servers are asfollows:

l On the MSC server and the RNC, configure the status of the MSC server from which thesubscribers migrate to Offload.

l 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 theMS/UE that the LAI is the Non-broadcast LAI of the local office.

l After the MS/UE terminates the current service, the Non-broadcast LAI causes immediatelocation update of the MS/UE because the Non-broadcast LAI differs from the LAIbroadcast by the RNC that serves the MS/UE.

l 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 configuredto Offload) that supports the maximum subscriber capacity in the MSC Pool. The RNCthen routes the service to the selected MSC server. The selected MSC server completes theregistration of the MS/UE, and allocates the TMSI containing the NRI of the local officeto the MS/UE. During registration, the selected MSC server determines the MSC server inwhich the subscriber is registered based on the Non-broadcast LAI that is contained in thelocation update message sent by the MS/UE, and obtains the IMSI of the subscriber andinformation about unused encrypted parameters.

l After the subscriber migration is completed, restore the status of the MSC server configuredon the MSC server and the RNC to Normal through the M2000 Client. For the detailedprocedures 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




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 Confirmdialog box, asking you to confirm that the status of the CN node in the radio access network is correctlyconfigured. 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.




Issue 02 (2008-04-10)

Table 9-5 Mapping between the migration modes and the operations

Migration Mode Operations

Re-distribution allsubscribers on theMSC to other MSCs

1. Select the MSC server from which the subscribers migrate in theSource 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 andthe system automatically generates the load sharing ratio of thespecified destination MSC server.

4. Select a subscriber migration speed from the Re-distributionspeed drop-down list box.

Re-distribution acertain ratio ofsubscribers on theMSC to other MSCs

The operation procedures are similar to the procedures performedwhen the migration mode Re-distribution all subscribers on the MSCto other MSCs is selected. In addition, you need to set Re-distribution ratio.

Re-distribution acertain number ofsubscribers on theMSC to other MSCs

The operation procedures are similar to the procedures performedwhen the migration mode Re-distribution all subscribers on the MSCto other MSCs is selected. In addition, you need to set Subscribers.

Re-distribution thesubscribers withspecified RNC on theMSC to other MSCs

Select an RNC under Candidate RNC, and then click Next. Theother operation procedures are the same as the procedures performedwhen the migration mode Re-distribution all subscribers on the MSCto other MSCs is selected.

Re-distribution thesubscribers withspecified BSC on theMSC to other MSCs

Select a BSC in the Candidate BSC frame, and then click Next.The other operation procedures are the same as the proceduresperformed when the migration mode Re-distribution all subscriberson the MSC to other MSCs is selected.

Re-distribution thesubscribers withspecified LAI on theMSC to other MSCs

Select an LAI in the Candidate LAIs frame, and then click Next.The other operation procedures are the same as the proceduresperformed when the migration mode Re-distribution all subscriberson the MSC to other MSCs is selected.

Re-distribution thesubscribers on theMSC to other MSC

1. Select the number type of the subscribers who migrate from theNumber type drop-down list box.

2. Select the MSC server from which the subscribers migrate fromthe Resource NE drop-down list box.

3. Enter the subscriber number in the Enter the subscribernumber 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 MSCserver.

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



9-29

CAUTIONl 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.l 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 DataThis 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 MSCPool cannot run properly. The M2000 provides the data check function, so that you can performmaintenance operations on the network based on the check result to ensure the consistency ofthe data.

9.7.1 Reviewing the Result of an MSC Pool Data CheckThis section describes how to review the result of an MSC Pool data check.

9.7.2 Manually Checking MSC Pool DataThis section describes how to check the MSC Pool data manually.

9.7.3 Synchronizing MSC Pool DataThis section describes how to synchronize MSC Pool data.

9.7.1 Reviewing the Result of an MSC Pool Data CheckThis 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 thedata 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 prerequisitesare 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:




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.



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 Managementwindow. 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 whoseResult 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 notacknowledged.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 ofthe inconsistent data.

l You can view the detailed check results in the box beside the Inconsistency Data tree. Theinconsistent data is in red.

l Click Save to save the check results to a file.

----End




Issue 02 (2008-04-10)

9.7.2 Manually Checking MSC Pool DataThis section describes how to check the MSC Pool data manually.

PrerequisiteIn the MSC Pool, certain data configured on all NEs must be the same; otherwise, the MSC Poolcannot run properly. You can manually check the data on the M2000. After selecting NEs anddata items to be checked, you can review the data check results so that you can take relatedmeasures to ensure the data consistency.

Before you check MSC Pool data manually, ensure that the following prerequisites are fulfilled:



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 > ManualCheck&Synchronize Data.

The Manual Check dialog box is displayed, as shown in Figure 9-20



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 Resultof 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 theprogress of updating the NE data in the cache of the server.




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

UpdateResult

Operation

Succeeded Go to Step 9.

Failed Click Cancel.The Message dialog box is displayed, indicating that the data update failed andasking 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.

l 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

PostrequisiteIf inconsistent data exists, the details of the data are displayed in the area under Choose NE.



9-35

l The Inconsistency Data tree displays the data items and key values of the inconsistentdata.

l The detailed check results are displayed beside the Inconsistency Data tree. Theinconsistent data is in red.

If the NE data is consistent, the Data Consistency Check dialog box showing that the data isconsistent 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 DataThis section describes how to synchronize MSC Pool data.

PrerequisiteIn an MSC Pool network, certain data configured on NEs must be consistent. Otherwise, it mayaffect the normal operation of the MSC Pool. If the data is inconsistent, you can ensure the dataconsistency 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.

l You have the rights to perform operations on the MSC Pool.

l You have checked the data and found that the data configured on NEs is inconsistent. (Fordetails on the data check, see section 9.7.2 Manually Checking MSC Pool Data)

ContextBased on the inconsistent data, the M2000 generates MML commands to adjust the data andsends the commands to the related NEs for execution. Thus, the data can be adjusted to theconsistency.

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.




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 dialogbox, as shown in Figure 9-24

Figure 9-24 Generated MML commands



9-37

NOTE

l You can modify the MML commands displayed or click Save MML to save the commands to a filefor the subsequent execution.

l If the key values of the chosen destination NE(s) is the same as the values of the reference NE, promptinformation indicating data consistency and the related key values are displayed in the right pane.

l If a key value does not support a generated MML command, the corresponding prompt information isalso displayed in the right pane. In this case, you need to adjust the data on the LMT of the involvedNE.

l Up to 500 MML command lines can be displayed in the right pane. If the number of the command linesis 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 commandswhen an error occurs.

Table 9-7 Command send modes

Whether to SendCommands Whenan Error Occurs

Command Send Modes

Yes During the sending of MML commands, if an error occurs in acommand, the system continues to send the remaining commands.

No During the sending of MML commands, if an error occurs in acommand, the system stops sending the remaining commands.

When the MML commands are sent, the system shows the progress in the DataSynchronization 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




Issue 02 (2008-04-10)

10 MSC Pool Performance MetricsReference

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 theMSC Pool and each BSC/RNC belongs to the different MSC servers. In this case, theperformance specification of a single NE cannot completely reflect the network loading in aspecified area; thus, the performance measurement entities of each NE should be collected tothe M2000 to obtain a general entity data, which provides the reference for the routine operationand maintenance, and the network adaptation.

The following lists measurement entities collected to the M2000 based on each area:

l 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

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual 10 MSC Pool Performance Metrics Reference


10-1

l Each local network– Call Attempt Times

– Seizure Times

– Call Connected Times

– Answer Times

– Seizure Traffic

– Connected Traffic

– Answer Traffic

– Average Seizure Duration


– Connected Ratio

– Answer Ratio

l 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 thefollowing 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

l Call Attempt Times, Seizure Times, Call Connected Times, Answer Times, Seizure Traffic,Connected Traffic, Answer Traffic, Average Seizure Duration, Average Seizure TrafficPer Line, Connected Ratio, and Answer Ratio

l VLR Subscriber of IMSI_DETACH, VLR Subscriber of Local, VLR Subscriber ofIMSI_ATTACH, VLR Subscriber of Local, and VLR Subscriber of Roaming

The general performance measurement supports the periodical collection of all the measuredresults of preceding measurement entities reported by MSC servers within an MSC Pool to theMSC level Pool. The measured results can be queried through the GUI or exported into a reportfor querying.

The M2000 provides the performance monitoring function for general KPIs. After receiving themeasured results from the MSC level Pool, the performance monitoring module can display the

10 MSC Pool Performance Metrics ReferenceHUAWEI MSOFTX3000 Mobile Softswitch Center



Issue 02 (2008-04-10)

results in the performance monitor window in real time, in the format of table, graph, orhistogram.

NOTE

In the MSC Pool networking, the performance measurements of a single NE are retained to measure thesingle NE.

The following sections describe measurement entities of each performance measurement indetails.

10.1 Total Traffic in MSC PoolThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit Total Traffic in MSC Pool.

10.2 Incoming/Outgoing MSC Pool TrafficThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit Mobile Office Direction Incoming/Outgoing MSC Pool Traffic.

10.3 Handover to and Out of the MSC PoolThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit Measurement For MSC Pool HO.

10.4 All VLR Subscribers in the MSC PoolThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit Traffic Measurement For ALL VLR Subscriber in MSC Pool.

10.5 Success Paging Rate (Traffic Measurement For MTC SUCC Rate)This section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit MSC Pool Traffic Measurement For MTC SUCC Rate (TrafficMeasurement For MTC SUCC Rate).

10.6 LAI In the MSC PoolThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit Traffic Measurement For LAI In MSC Pool.

10.7 GSM Call DropThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit GSM Call Drop.

10.8 UMTS Call DropThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit UMTS Call Drop.

10.9 MSC Pool Traffic Measurement Of GSM AssignmentThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit MSC Pool Traffic Measurement Of GSM Assignment.

10.10 MSC Pool Traffic Measurement Of WCDMA AssignmentThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit for MSC Pool Traffic Measurement Of WCDMA Assignment.

10.11 Success SMS RateThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit for MSC Pool Traffic Measurement Of SMS.

10.12 Traffic Measurement For LOC UpThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit for MSC Pool Traffic Measurement For LOC Up.



10-3

10.1 Total Traffic in MSC PoolThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit Total Traffic in MSC Pool.

This measurement unit is used to measure total traffic of an MSC Pool. The system registers theIncoming Office Traffic, BSS Originate Call, and UTRAN Originate Call of each MSC Serverwithin one MSC Pool and then collects the measurement entities in each MSC Server to theM2000.

NOTE

In the actual implementation process, the system registers a measurement task on the M2000 and thendelivers the task to the MSC Server. After that, the MSC Server is responsible for reporting the entities tothe 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 measuremententities are the same as those for Call Attempt Times.

Formula:

Call Attempt Times = ∑(Call Attempt Times of Incoming Office Traffic of all MSC serverswithin an MSC Pool) + ∑(Call Attempt Times of BSS Originate Call of all MSC servers withinan MSC Pool) + ∑(Call Attempt Times of UTRAN Originate Call of all MSC servers withinan MSC Pool)

The description of the specific measurement entities is as follows:

l Answer Times = Answer Times of Incoming Office Traffic + Answer Times of BSSOriginate Call + Answer Times of UTRAN Originate Call

l Call Attempt Times = Call Attempt Times of Incoming Office Traffic + Call Attempt Timesof BSS Originate Call + Call Attempt Times of UTRAN Originate Call

l Call Connected Times = Call Connected Times of Incoming Office Traffic + CallConnected Times of BSS Originate Call + Call Connected Times of UTRAN OriginateCall

l Answer Traffic = Answer Traffic of Incoming Office Traffic + Answer Traffic of BSSOriginate Call + Answer Traffic of UTRAN Originate Call

l Seizure Traffic = Seizure Traffic of Incoming Office Traffic + Seizure Traffic of BSSOriginate Call + Seizure Traffic of UTRAN Originate Call

l Connect Traffic = Connect Traffic of Incoming Office Traffic + Connect Traffic of BSSOriginate Call + Connect Traffic of UTRAN Originate Call

l Answer Ratio = (Answer Times of Incoming Office Traffic + Answer Times of BSSOriginate Call + Answer Times of UTRAN Originate Call)/(Seizure Times of IncomingOffice Traffic + Seizure Times of BSS Originate Call + Seizure Times of UTRAN OriginateCall) x 100

l Connected Ratio = (Call Connected Times of Incoming Office Traffic + Call ConnectedTimes of BSS Originate Call + Call Connected Times of UTRAN Originate Call)/(SeizureTimes of Incoming Office Traffic + Seizure Times of BSS Originate Call + Seizure Timesof UTRAN Originate Call) x 100




Issue 02 (2008-04-10)

10.2 Incoming/Outgoing MSC Pool TrafficThis section describes the measurement object, calculation formula, and measurement entitiesof 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 anMSC Pool.

Incoming MSC Pool Traffic

The system registers Mobile Office Direction Incoming Office Traffic and the office directionnumber is configured in the LA/Cell table. The system requires that the office direction numberconfigured in each LA must be the same and the configuration must be consistent with that onthe 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 OfficeTraffic of all MSC servers within an MSC Pool)

Average Seizure Traffic Per Line = Total traffic of Mobile Office Direction Incoming OfficeTraffic/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

l Call Connected Times

l Answer Times

l Seizure Traffic

l Connected Traffic

l Connected Traffic

l Answer Traffic

l Installed Circuit Num

l Avail Circuit Num

l Blocked Circuit Num

l Connected Ratio

l Answer Ratio

l Average Seizure Traffic Per Line



10-5

Outgoing MSC Pool TrafficThe system registers Mobile Office Direction Outgoing Office Traffic and the office directionnumber is configured in the LA/Cell table. The system requires that the office direction numberconfigured in each LA must be them same and the configuration must be consistent with thaton 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 OfficeTraffic of all MSC servers within an MSC Pool)

Average Seizure Traffic Per Line = Total traffic of Mobile Office Direction Incoming OfficeTraffic/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

l Call Connected Times

l Answer Times

l Seizure Traffic

l Connected Traffic

l Answer Traffic

l Installed Circuit Num

l Avail Circuit Num

l Blocked Circuit Num

l Connected Ratio

l Answer Ratio

l Average Seizure Traffic Per Line

10.3 Handover to and Out of the MSC PoolThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit Measurement For MSC Pool HO.

This measurement unit is used to measure the in-pool and out-pool traffic. The system registersMeasurement for MSC HO of each MSC Server within one MSC Pool and then collectsmeasurement entities of the MSC servers to the M2000.

Measurement object: local MSC

Formula:




Issue 02 (2008-04-10)

Request inter MSC Basic HO in = ∑(Request inter MSC Basic HO in of Measurement For MSCHO of all MSC servers within an MSC Pool)

This measurement contains the following measurement entities:

l Request inter MSC Basic HO in

l Request inter MSC Basic HO out

l Successfully inter MSC Basic HO in

l Successfully inter MSC Basic HO out

l Handover success ratio

10.4 All VLR Subscribers in the MSC PoolThis section describes the measurement object, calculation formula, and measurement entitiesof 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 oneMSC 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 VLRSubscriber of all MSC servers within an MSC Pool)


l VLR Subscriber of IMSI_DETACH

l VLR Subscriber of Total

l VLR Subscriber of IMSI_ATTACH

l VLR Subscriber of Local

l VLR Subscriber of Roaming

10.5 Success Paging Rate (Traffic Measurement For MTCSUCC Rate)

This section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit MSC Pool Traffic Measurement For MTC SUCC Rate (TrafficMeasurement For MTC SUCC Rate).

The system registers Traffic Measurement For MTC SUCC Rate of all MSC servers within theMSC Pool and then collects measurement entities of MSC servers to the M2000.


Formula: sum of values of each measurement entity


l MTC Succ Rate Paging



10-7

l MTC Succ Rate Paging Resp

l MTC Succ Rate Alert

l MTC Succ Rate MO Alert

l MTC Succ Rate Land Alert

l MTC Succ Rate Alert Rate = MTC Succ Rate Alert/MTC Succ Rate Paging x 100

l MTC Succ Rate Success Paging Rate = MTC Succ Rate Paging Resp/MTC Succ RatePaging x 100

10.6 LAI In the MSC PoolThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit Traffic Measurement For LAI In MSC Pool.

The system registers Traffic Measurement For LAI of all MSC servers within one MSC Pooland 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 measuremententities 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 allMSC servers within an MSC Pool)


l Total user number (LAI)

l Local user number (LAI)

l Roaming user number (LAI)

l Switch on user number (LAI)

l Switch off user number (LAI)

l Update location request times (LAI)

l MO connect times (LAI)

l MO response times (LAI)

l LAI paging times (LAI)

l Paging response times (LAI)

l MT connect traffic (LAI)

l MT response traffic (LAI)

l LAI paging times (LAI)

l Paging response times (LAI)

l MTC succ rate success paging rate




Issue 02 (2008-04-10)

10.7 GSM Call DropThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit GSM Call Drop.

The system registers GSM Call Drop of all MSC servers within one MSC Pool and then collectsmeasurement entities of the MSC servers to the M2000.

Measurement object: local MSCC

Formula:

2G Call Drop Rate Call Drop = ∑(2G Call Drop Rate Call Drop of GSM Call Drop of all MSCservers within an MSC Pool)


l 2G Call Drop Rate Connect

l 2G Call Drop Rate MT Connect

l 2G Call Drop Rate MO Connect

l 2G Call Drop Rate MO Call Drop

l 2G Call Drop Rate MT Call Drop

l 2G Call Drop Rate HO Call Drop

l 2G Call Drop Rate

10.8 UMTS Call DropThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit UMTS Call Drop.

The system registers UMTS Call Drop of all MSC servers within one MSC Pool and then collectsmeasurement entities of the MSC servers to the M2000.


Formula:

3G Call Drop Rate Call Drop = ∑(3G Call Drop Rate Call Drop of UMTS Call Drop of all MSCservers within an MSC Pool)


l 3G Call Drop Rate Connect

l 3G Call Drop Rate MT Connect

l 3G Call Drop Rate MO Connect

l 3G Call Drop Rate MO Call Drop

l 3G Call Drop Rate MT Call Drop

l 3G Call Drop Rate HO Call Drop

l 3G Call Drop Rate



10-9

10.9 MSC Pool Traffic Measurement Of GSM AssignmentThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit MSC Pool Traffic Measurement Of GSM Assignment.

The system registers Traffic Measurement Of GSM Assignment of all MSC servers within oneMSC Pool and then collects measurement entities of the MSC servers to the M2000.

Measurement object: specified BSC office direction



l Traffic Assign Request Times

l Traffic Assign Success Times

l Half Rate Traffic Assign Request Times

l Half Rate Traffic Assign Success Times

l Traffic Assign Success Ratio

10.10 MSC Pool Traffic Measurement Of WCDMAAssignment

This section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit for MSC Pool Traffic Measurement Of WCDMA Assignment.

The system registers Traffic Measurement Of WCDMA Assignment of all MSC servers withinone 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

l Assign 3G Assign Channel Success

l Assign 3G Assign Channel Success Ratio

10.11 Success SMS RateThis section describes the measurement object, calculation formula, and measurement entitiesof the measurement unit for MSC Pool Traffic Measurement Of SMS.

The system registers Traffic Measurement For SMS of all MSC servers within one MSC Pooland then collects measurement entities of the MSC servers to the M2000.

Measurement object: local network index

Formula:




Issue 02 (2008-04-10)

SMMO Success Ratio = ∑(SMMO Success Times of Traffic Measurement For SMS of all MSCservers within an MSC Pool)/∑(SMMO Times of Traffic Measurement For SMS of all MSCservers within an MSC Pool)


l SMMO Times

l SMMO Success Times

l SMMT Times

l SMMT Success Times

l SMMO Success Ratio

l SMMT Success Ratio

10.12 Traffic Measurement For LOC UpThis section describes the measurement object, calculation formula, and measurement entitiesof 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 MSCPool and then collects measurement entities of the MSC servers to the M2000.

Measurement object: specified LAI



l Number of Location Update request

l Number of Location Update reject

l Number of IMSI detach

l Number of IMSI attach

l Number of Location Update Intra_VLR Require

l Success No of Location Update Intra_VLR Require

l Number of Location Update Inter_VLR Require

l Success No of Location Update Inter_VLR Require

l Success No of National Roaming User Registration

l 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



10-11

Index

Symbols/Numerics2G existing network, 6-23G existing network, 8-2Cconfiguration procedure

access network, 5-21, 7-15core network, 5-15, 7-9

Ddata configuration

2G, 6-53G, 8-6access network, 6-30, 6-35, 6-37, 6-37, 6-37, 6-37,8-27, 8-29, 8-31, 8-32, 8-32, 8-32core network, 6-10, 6-12, 6-16, 6-19, 6-24, 8-11,8-14, 8-17, 8-22other, 5-24, 8-32

data planning, 6-6, 8-6

Eevolution of the core network, 6-9, 8-11evolution process of the core network

2G, 6-93G, 8-10

evolution scenario2G, 6-23G, 8-2

Iintegration process of the access network

2G, 6-303G, 8-27

MM2000

add NRI, 9-7auditing data, 9-30check alarm information, 9-15check event alarm, 9-18

check fault alarm, 9-15check the data manually, 9-33maintenance status, 9-14manual migration of subscriber, 9-26MSC Pool attribute parameter, 9-2query performance report, 9-24review the attribute of parameter, 9-5set non-broadcast LAI, 9-13set NRI length, 9-10set real-time monitoring, 9-20set the parameter of load balancing, 9-11synchronize data, 9-36

M2000 application scenario, 1-27M2000 function, 1-26MSC Pool feature

backgroud, 1-2concept, 1-2

Nnetwork specification, 3-2networking scheme

ATM, 2-3CN NE inside and outside, 2-4MGW provide the A-Flex, 2-4TDM, 2-2

new target network2G, 5-23G, 7-2

Pperformance measurement entity, 10-1

GSM call drop, 10-9traffic measurement for LAI, 10-8traffic measurement for VLR subscriber, 10-7traffic measurement of SMS, 10-10UMTS call drop, 10-9

performance measurement entityhandover, 10-6

performance measurement entitytotal traffic, 10-4

planning, 3-4presetting data, 5-9, 7-8

HUAWEI MSOFTX3000 Mobile Softswitch CenterMSC Pool User Manual Index


i-1

principleA-Flex function proxy, 1-18charging, 1-24disaster tolerance, 1-8handover, 1-8load balancing, 1-7, 1-17location update with Gs interface, 1-14managing circuit, 1-22paging control, 1-14subscriber migration, 1-14

Rreal-time load monitor task, 9-22routine maintenance, 9-1

Ssignaling networking scheme, 2-2system commissioning

2G, 6-383G, 7-18

Ttarget network

2G, 6-33G, 8-3

IndexHUAWEI MSOFTX3000 Mobile Softswitch Center


i-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-04-10)

MSC Pool User Manual

Documents

Transcript of MSC Pool User Manual