Area Network User Manual PDF

Chapter 1 Introduction .................................................................................... 1.1 Background Information ......................................................................... 1.2 Definition of Multi-Area Networking ........................................................ 1.2.
1 Basic Model of Multi-Area Networking ........................................... 1.2.2 Schemes of Multi-Area Networking................................................ 1.3 Features of Multi-Area Networking ......................................................... 1.3.1 Large Capacity ............................................................................... 1.3.2 Wide Coverage .............................................................................. 1.3.3 Advantages over Traditional 2G Networking ................................. 1.3.4 Limitations of Multi-Area Networking ............................................. Chapter 2 Networking Principles ................................................................... 2.1 Basic Principles of Multi-Area Networking .............................................. 2.2 Principles of Voice Channel Networking ................................................ 2.2.1 Multiple MSC Numbers and Single MGW ...................................... 2.2.2 Multiple MSC Numbers and Multiple MGWs Without Intermediate Bearer ................................................................................ 2.2.3 Multiple MSC Numbers and Multiple MGWs with Intermediate Bearer ..................................................................................................... 2.3 Principles of Signaling Networking ......................................................... 2.3.1 Classification According to Amounts of MSC Numbers and Signaling Points ...................................................................................... 2.3.2 Classification According to Signaling Transmission Network Between MSOFTX3000 and MGW ......................................................... 2.3.3 Classification According to Signaling Networking Between MSOFTX3000 and External Network Elements ...................................... Chapter 3 Service Implementation Principles ............................................... 3.1 Principle of Multiple Virtual MSC/VLR Numbers .................................... 3.2 Principle of Multiple Area Code Function ............................................... 3.3 Principle of Roaming Feature ................................................................. 3.3.1 Location Update ............................................................................. 3.3.2 Roaming Types .............................................................................. 3.3.3 Roaming Restriction ....................................................................... 3.4 Principle of Roaming Number Assignment............................................. 3.5 Principles of Call and Route Selection ................................................... 3.5.1 Call Data Obtaining ........................................................................ 3.5.2 Call Routing ................................................................................... 3.6 Principles of Paging Optimization ........................................................... 3.7 Principle of Handover ............................................................................. 3.8 Principles of IN Service .......................................................................... 3.8.1 Destination Network Mode .............................................................
1-1 1-1 1-1 1-2 1-2 1-3 1-3 1-4 1-4 1-4 2-1 2-1 2-2 2-2 2-3 2-4 2-8 2-8 2-14 2-16 3-1 3-1 3-2 3-4 3-4 3-5 3-5 3-5 3-6 3-6 3-7 3-8 3-9 3-9 3-10
3.8.2 Non-Destination Network Mode ..................................................... 3.9 Principle of Lawful Interception Service ................................................. 3.10 Principle of Charging ............................................................................ 3.10.1 Principles for the Entry of MSC Numbers on the Caller/Callee Side in Bills ............................................................................................. 3.10.2 Principles for Saving Bill Files in the iGWB .................................. 3.11 Principle of Traffic statistics .................................................................. 3.11.1 Basic Principles ............................................................................ 3.11.2 Ways for Obtaining Multi-Area Statistics Index ............................ 3.11.3 Traffic statistics Units ................................................................... Chapter 4 Data Configuration ......................................................................... 4.1 Scheme of Data Configuration ............................................................... 4.2 Planning Data Configuration .................................................................. 4.2.1 Deployment Recommendations ..................................................... 4.2.2 Locating Principles of Network Elements....................................... 4.2.3 Principles of Data Planning ............................................................ 4.3 Setting Related Software Parameters .................................................... 4.3.1 Setting Location Update Mode ....................................................... 4.3.2 Setting Duration of Protecting Location Update Data by Timer ..... 4.3.3 Setting Parameter of Optimizing Paging in Entire Multi-area Network ................................................................................................... 4.3.4 Setting Monitoring Parameter in Multi-area Network ..................... 4.3.5 Setting Local Number Length ........................................................ 4.4 Configuring Basic Information in Local Office ........................................ 4.5 Configuring Signaling Data..................................................................... 4.6 Configuring Bearer Data Between MGWs .............................................. 4.6.1 TDM Bearer Network Between MGWs in Area Network ................ 4.6.2 IP Bearer Network Between MGWs in Area Network .................... 4.7 Configuring Service Data ....................................................................... 4.7.1 Configuring LAI and Office Direction Trunk ................................... 4.7.2 Configuring Mobile Service Management ...................................... 4.7.3 Configuring Service Data Handover .............................................. 4.7.4 Configuring Roaming Number Data ............................................... 4.7.5 Configuring Number Analysis and Route Selection ....................... 4.8 Data Configuration Examples ................................................................. 4.8.1 Implementation .............................................................................. 4.8.2 Script .............................................................................................. Chapter 5 System Commissioning ................................................................ 5.1 Subscriber Location Update ................................................................... 5.2 Ordinary Call Flow ..................................................................................
3-10 3-11 3-11 3-11 3-13 3-14 3-14 3-14 3-15 4-1 4-1 4-2 4-2 4-2 4-2 4-5 4-5 4-5 4-5 4-6 4-6 4-7 4-8 4-8 4-9 4-9 4-9 4-9 4-10 4-10 4-12 4-12 4-17 4-17 4-19 5-1 5-1 5-2
5.3 IN Related Service ................................................................................. 5.4 Supplementary Service Registration ...................................................... 5.5 Forwarding Call Authentication .............................................................. 5.6 Text Message Service ............................................................................ 5.7 Handover Process .................................................................................. 5.8 Traffic statistics....................................................................................... 5.9 Other Services ........................................................................................ Chapter 6 Test Items ....................................................................................... Chapter 7 Network Upgrade ........................................................................... 7.1 Upgrade Notes ....................................................................................... 7.2 Upgrade Steps ....................................................................................... 7.2.1 Applying for License ....................................................................... 7.2.2 Setting Hardware Data ................................................................... 7.2.3 Setting Multi-Area Network Flags .................................................. 7.2.4 Setting Local SP and MSC Number and Loading License ............ 7.2.5 Setting Mutual-Assistance Relation ............................................... 7.2.6 Setting MGW Data ......................................................................... 7.2.7 Setting Link Data ............................................................................ 7.2.8 Setting SCCP Data ........................................................................ 7.2.9 Setting Data for Access Side and Trunk Side ................................ 7.2.10 Setting Number Analysis, Trunk Group and Trunk Circuit Data ........................................................................................................ 7.2.11 Setting Service Data .................................................................... Chapter 8 Handling of Common Problems ................................................... 8.1 How to Measure Traffic of Local Networks............................................. 8.2 How to Store Bills of Multi-Area Network ............................................... 8.3 How to Set Routing Data ........................................................................ 8.4 How to Set Trunk Group Data in Multi-SP Networking........................... 8.5 How to Set Interworking Data ................................................................. 8.6 How to Set Source GT Data in SCP Messages ..................................... 8.7 How to Set Number of Local Networks .................................................. 8.8 How to Set Local Number Length .......................................................... 8.9 How to Set Area Code of Local Network ................................................ 8.10 How to Set National Toll Prefix and International Toll Prefix ................ 8.11 How to Intercept Subscribers of Multi-Area Network ............................ Chapter 9 Acronyms and Abbreviations ....................................................... Index .................................................................................................................
5-2 5-3 5-3 5-4 5-4 5-4 5-4 6-1 7-1 7-1 7-2 7-2 7-3 7-3 7-3 7-4 7-4 7-4 7-4 7-5 7-6 7-6 8-1 8-1 8-1 8-1 8-2 8-2 8-3 8-3 8-3 8-4 8-4 8-4 9-1
HUAWEI
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Multi-Area Network User Manual V100R003
Huawei Technologies Proprietary
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Multi-Area Network User Manual

Manual Version Product Version BOM T2-030106-20060425-C-3.05 V100R003 31016106
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd., Bantian, Longgang District, Shenzhen, P. R. China Postal Code: 518129 Website: http://www.huawei.com Email: support@huawei.com
Copyright 2006 Huawei Technologies Co., Ltd.
All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET,
, ViewPoint, INtess, ETS, DMC,
TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800, TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN, HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye, Lansway, SmartAX, infoX, and TopEng are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this manual are the property of their respective holders.
Notice
The information in this manual is subject to change without notice. Every effort has been made in the preparation of this manual to ensure accuracy of the contents, but all statements, information, and recommendations in this manual do not constitute the warranty of any kind, express or implied.
About This Manual

Release Notes
The manual applies to HUAWEI MSOFTX3000 Mobile SoftSwitch Center V100R003.
Organization
This manual describes the principles and data planning of the multi-area feature of HUAWEI MSOFTX3000 Mobile SoftSwitch Center (hereinafter referred to as MSOFTX3000). This manual contains nine chapters.
z
Chapter 1 Introduction describes the background information, concepts, and features of multi-area networking. Chapter 2 Networking Principles details the principles of voice channel networking and signaling networking. Chapter 3 Service Implementation Principles explains the implementation principles of services such as roaming, handover, and charging of multi-area networks.
Chapter 4 Data Configuration describes the schemes, principles, and steps of data configuration for multi-area networks. Examples are provided to explain special data configuration related to multi-area networks.
Chapter 5 System Commissioning describes the system commissioning procedure and expected results of multi-area networks. Chapter 6 Test Items lists basic test cases for multi-area networks. Chapter 7 Network Upgrade describes data configuration steps and principles when non-multi-area offices are upgraded to multi-area ones. Chapter 8 Handling of Common Problems describes common problems and corresponding handling methods. Chapter 9 Acronyms and Abbreviations lists the full names of the acronyms and abbreviations used in the manual.
z z
Intended Audience
The manual is intended for the following readers:
z z
Operation and maintenance engineers Marketing technical personnel
Engineering technical personnel
Conventions
The manual uses the following conventions:
I. General conventions
Convention Arial Boldface Courier New Description Normal paragraphs are in Arial. Headings are in Boldface. Terminal Display is in Courier New.
II. Command conventions

Convention Boldface Description The keywords of a command line are in Boldface.
III. GUI conventions

Convention [] Description Parameter names are inside square brackets. For example, [Trunk group number].
IV. Mouse operation

Action Click Right-click Double-click Description Press the left button quickly. Press the right button quickly. Press the left button twice continuously and quickly.
V. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of special attention during the operation. They are defined as follows:
Caution: Means reader be extremely careful during the operation.

Note: Means a complementary description.
Multi-Area Network User Manual HUAWEI MSOFTX3000 Mobile SoftSwitch Center
Table of Contents
Table of Contents
Chapter 1 Introduction .................................................................................................................. 1-1 1.1 Background Information..................................................................................................... 1-1 1.2 Definition of Multi-Area Networking ................................................................................... 1-1 1.2.1 Basic Model of Multi-Area Networking .................................................................... 1-2 1.2.2 Schemes of Multi-Area Networking......................................................................... 1-2 1.3 Features of Multi-Area Networking .................................................................................... 1-3 1.3.1 Large Capacity ........................................................................................................ 1-3 1.3.2 Wide Coverage........................................................................................................ 1-4 1.3.3 Advantages over Traditional 2G Networking .......................................................... 1-4 1.3.4 Limitations of Multi-Area Networking....................................................................... 1-4 Chapter 2 Networking Principles ................................................................................................. 2-1 2.1 Basic Principles of Multi-Area Networking......................................................................... 2-1 2.2 Principles of Voice Channel Networking............................................................................ 2-2 2.2.1 Multiple MSC Numbers and Single MGW............................................................... 2-2 2.2.2 Multiple MSC Numbers and Multiple MGWs Without Intermediate Bearer ............ 2-3 2.2.3 Multiple MSC Numbers and Multiple MGWs with Intermediate Bearer .................. 2-4 2.3 Principles of Signaling Networking .................................................................................... 2-8 2.3.1 Classification According to Amounts of MSC Numbers and Signaling Points........ 2-8 2.3.2 Classification According to Signaling Transmission Network Between MSOFTX3000 and MGW ............................................................................................... 2-14 2.3.3 Classification According to Signaling Networking Between MSOFTX3000 and External Network Elements............................................................................................ 2-16 Chapter 3 Service Implementation Principles ............................................................................ 3-1 3.1 Principle of Multiple Virtual MSC/VLR Numbers................................................................ 3-1 3.2 Principle of Multiple Area Code Function .......................................................................... 3-2 3.3 Principle of Roaming Feature ............................................................................................ 3-4 3.3.1 Location Update ...................................................................................................... 3-4 3.3.2 Roaming Types ....................................................................................................... 3-5 3.3.3 Roaming Restriction................................................................................................ 3-5 3.4 Principle of Roaming Number Assignment........................................................................ 3-5 3.5 Principles of Call and Route Selection .............................................................................. 3-6 3.5.1 Call Data Obtaining ................................................................................................. 3-6 3.5.2 Call Routing............................................................................................................. 3-7 3.6 Principles of Paging Optimization ...................................................................................... 3-8 3.7 Principle of Handover ........................................................................................................ 3-9 3.8 Principles of IN Service...................................................................................................... 3-9 3.8.1 Destination Network Mode .................................................................................... 3-10
Huawei Technologies Proprietary i
Table of Contents
3.8.2 Non-Destination Network Mode ............................................................................ 3-10 3.9 Principle of Lawful Interception Service........................................................................... 3-11 3.10 Principle of Charging ..................................................................................................... 3-11 3.10.1 Principles for the Entry of MSC Numbers on the Caller/Callee Side in Bills....... 3-11 3.10.2 Principles for Saving Bill Files in the iGWB......................................................... 3-13 3.11 Principle of Traffic statistics ........................................................................................... 3-14 3.11.1 Basic Principles ................................................................................................... 3-14 3.11.2 Ways for Obtaining Multi-Area Statistics Index................................................... 3-14 3.11.3 Traffic statistics Units .......................................................................................... 3-15 Chapter 4 Data Configuration ...................................................................................................... 4-1 4.1 Scheme of Data Configuration........................................................................................... 4-1 4.2 Planning Data Configuration.............................................................................................. 4-2 4.2.1 Deployment Recommendations .............................................................................. 4-2 4.2.2 Locating Principles of Network Elements................................................................ 4-2 4.2.3 Principles of Data Planning ..................................................................................... 4-2 4.3 Setting Related Software Parameters ............................................................................... 4-5 4.3.1 Setting Location Update Mode................................................................................ 4-5 4.3.2 Setting Duration of Protecting Location Update Data by Timer .............................. 4-5 4.3.3 Setting Parameter of Optimizing Paging in Entire Multi-area Network ................... 4-5 4.3.4 Setting Monitoring Parameter in Multi-area Network .............................................. 4-6 4.3.5 Setting Local Number Length.................................................................................. 4-6 4.4 Configuring Basic Information in Local Office.................................................................... 4-7 4.5 Configuring Signaling Data ................................................................................................ 4-8 4.6 Configuring Bearer Data Between MGWs......................................................................... 4-8 4.6.1 TDM Bearer Network Between MGWs in Area Network......................................... 4-9 4.6.2 IP Bearer Network Between MGWs in Area Network ............................................. 4-9 4.7 Configuring Service Data................................................................................................... 4-9 4.7.1 Configuring LAI and Office Direction Trunk ............................................................ 4-9 4.7.2 Configuring Mobile Service Management ............................................................. 4-10 4.7.3 Configuring Service Data Handover...................................................................... 4-10 4.7.4 Configuring Roaming Number Data ...................................................................... 4-12 4.7.5 Configuring Number Analysis and Route Selection .............................................. 4-12 4.8 Data Configuration Examples .......................................................................................... 4-17 4.8.1 Implementation...................................................................................................... 4-17 4.8.2 Script ..................................................................................................................... 4-19 Chapter 5 System Commissioning .............................................................................................. 5-1 5.1 Subscriber Location Update .............................................................................................. 5-1 5.2 Ordinary Call Flow ............................................................................................................. 5-2 5.3 IN Related Service............................................................................................................. 5-2 5.4 Supplementary Service Registration ................................................................................. 5-3 5.5 Forwarding Call Authentication.......................................................................................... 5-3 5.6 Text Message Service ....................................................................................................... 5-4
Huawei Technologies Proprietary ii
Table of Contents
5.7 Handover Process ............................................................................................................. 5-4 5.8 Traffic statistics .................................................................................................................. 5-4 5.9 Other Services ................................................................................................................... 5-4 Chapter 6 Test Items ..................................................................................................................... 6-1 Chapter 7 Network Upgrade ......................................................................................................... 7-1 7.1 Upgrade Notes................................................................................................................... 7-1 7.2 Upgrade Steps ................................................................................................................... 7-2 7.2.1 Applying for License................................................................................................ 7-2 7.2.2 Setting Hardware Data............................................................................................ 7-3 7.2.3 Setting Multi-Area Network Flags............................................................................ 7-3 7.2.4 Setting Local SP and MSC Number and Loading License ..................................... 7-3 7.2.5 Setting Mutual-Assistance Relation ........................................................................ 7-4 7.2.6 Setting MGW Data .................................................................................................. 7-4 7.2.7 Setting Link Data ..................................................................................................... 7-4 7.2.8 Setting SCCP Data ................................................................................................. 7-4 7.2.9 Setting Data for Access Side and Trunk Side......................................................... 7-5 7.2.10 Setting Number Analysis, Trunk Group and Trunk Circuit Data ........................... 7-6 7.2.11 Setting Service Data ............................................................................................. 7-6 Chapter 8 Handling of Common Problems ................................................................................. 8-1 8.1 How to Measure Traffic of Local Networks........................................................................ 8-1 8.2 How to Store Bills of Multi-Area Network........................................................................... 8-1 8.3 How to Set Routing Data ................................................................................................... 8-1 8.4 How to Set Trunk Group Data in Multi-SP Networking...................................................... 8-2 8.5 How to Set Interworking Data ............................................................................................ 8-2 8.6 How to Set Source GT Data in SCP Messages ................................................................ 8-3 8.7 How to Set Number of Local Networks.............................................................................. 8-3 8.8 How to Set Local Number Length...................................................................................... 8-3 8.9 How to Set Area Code of Local Network ........................................................................... 8-4 8.10 How to Set National Toll Prefix and International Toll Prefix........................................... 8-4 8.11 How to Intercept Subscribers of Multi-Area Network....................................................... 8-4 Chapter 9 Acronyms and Abbreviations..................................................................................... 9-1 Index ................................................................................................................................................ i-1
Huawei Technologies Proprietary iii
Chapter 1 Introduction
1.1 Background Information
In a non-multi-area network, traditional 2G equipment has the following defects:
I. For Areas with High Subscriber Density

When traditional 2G equipment is used to form a network in areas with high subscriber density, it has the following defects on the core network (CN) side:
z z z
Too many offices, each with small capacity Complicated network structure and waste of resources It is difficult to offer new services. To provide a new service, multiple entities need to be upgraded at the same time. This is difficult and risky.
II. For Areas with Lower Subscriber Density

When traditional 2G equipment is used to form a network in areas with lower subscriber density, it has the following defects on the CN side:
z
Several local networks share the same MSC. This causes serious alternate routing. Equipment integrates both the bearer and control functions cannot achieve large capacity, wide coverage, and fine routing at the same time. To meet the requirement of wide coverage, a network must have a great deal of alternate routing. To avoid alternate routing, a network must have many small-capacity offices.
The utilization rate of equipment and staff is low. It is difficult to develop new services.
To overcome the above defects, Huawei Technologies Co., Ltd. (hereinafter referred to as Huawei) provides a multi-area (MA) networking scheme that separates the bearer from the control.
1.2 Definition of Multi-Area Networking

The MA networking means that an MSOFTX3000 controls multiple local networks with the bearer separated from the control. The MSOFTX3000 controls all services in the MA network. Wireless network equipment of each local network is connected with a media gateway (MGW) dedicated to the area. Each local network interworks with entities of other local networks through an MGW. A local network refers to an area controlled by a virtual MSC server in an MA network.
Huawei Technologies Proprietary 1-1
1.2.1 Basic Model of Multi-Area Networking

Figure 1-1 shows a basic model of the MA networking:
TMSC1 TMSC2
MSOFTX3000
BSC MGW1 RNC MGW2
BSC
RNC PSTN PSTN Virtual MSC2/VLR2 DPC2
Virtual MSC1/VLR1 DPC1 Voice channel Signaling
RNC: Radio Network Controller BSC: Base Station Controller PSTN: Public Switched Telephone Network
TMSC: Tandem MSC MGW: Media Gateway
Figure 1-1 Basic model of the MA networking As shown in Figure 1-1, the MSOFTX3000 is placed in one area, and MGWs are distributed to different areas in an MA network. The PSTN network of each area accesses the MA network through a local MGW. Whether MGWs of two local networks are directly connected or not does not matter. The calls between mobile subscribers of two local networks are regarded as intra-office or inter-office. The handover of them is also regarded as intra-office or inter-office.
Note: In MA networking, you can use disaster tolerance measures such as dual homing backup and Mini-Flex to ensure the network security.
1.2.2 Schemes of Multi-Area Networking

There are two schemes of MA networking. They are designed for areas with high and lower subscriber density respectively, as shown in Table 1-1.
Table 1-1 Schemes of MA networking Item Suitable subscriber density distribution Multi-area networking scheme for area with high subscriber density High subscriber density and narrow coverage Large capacity and less offices
z
Multi-area networking scheme for area with lower subscriber density Lower subscriber density and wide coverage Centralized control and nearby access
and
Networking mode
NE deployment
Use R99 structure in which the MSOFTX3000 and the MGW are combined. Use PreR4 structure in which the MSOFTX3000 and the MGW are located in different areas.
The MSOFTX3000 is located in the center of different areas. One or more MGWs are placed in each local PSTN network.
Advantage
It makes the network topology simple. It improves the quality of the network. New services can be developed quickly.
Large capacity, wide coverage, and fine routing are achieved at the same time. The number of MSOFTX3000s is minimized. New services can be carried out quickly and easily. The cost of network construction is low. Wide coverage is achieved in an economical way.
Note: NE = Network Entity
1.3 Features of Multi-Area Networking

1.3.1 Large Capacity
For 10% areas that have a high subscriber density, capacity is the key factor for the construction of networks. Compared with the MSC in a 2G network, the MSOFTX3000 has larger capacity. It enables a simple network topology with large capacity and less offices. It overcomes the capacity barrier in areas that has a high subscriber density.
1.3.2 Wide Coverage

For 90% areas that have a lower subscriber density, to achieve wide coverage economically is the major goal for the construction of networks. Huawei offers a solution that separates the bearer from the control. In this solution, the MSOFTX3000 and the MGW (that is, the UMG8900) carries out the functions of control and bearer respectively. In the actual networking, the policy of centralized control and nearby access is used to construct an MA network. This achieves large capacity, wide coverage, and fine routing at the same time.
1.3.3 Advantages over Traditional 2G Networking

Compared with traditional 2G networking, MA networking has the following advantages:
z
The network topology is simple. This makes routing arrangement and optimization easy. The number of MSOFTX3000s is small. This helps you to develop new services. The nearby access feature avoids alternate routing. Functions of the MSOFTX3000 are centralized. This makes the network management and maintenance easy and efficient, and helps to improve the quality of operation, administration and maintenance (OAM).
z z z
The network structure is based on the next generation network (NGN). This enables seamless network expansion.
1.3.4 Limitations of Multi-Area Networking

I. Limitations of System Capacity
In MA networking, the capacity of the MSOFTX3000 is as follows:
z
When the MSOFTX3000 acts as a visited MSC (VMSC) server, it can support 2,700K BHCA, or 1.8 million subscribers at most. When the MSOFTX3000 acts as a gateway MSC (GMSC) server, it can support 7,200K BHCA at most. When the MSOFTX3000 acts as a TMSC server, it can support 9,000K BHCA at most.
Note: BHCA refers to Busy Hour Call Attempt.
II. Limitation of the Number of Local Networks

An MA network can support 16 local networks at most. To avoid complicated data configuration, you are recommended to attach no more than three local networks to one MSOFTX3000.
III. Limitation of the Capacity of Data Tables
Note:
z
When you plan MA networking, note the limitation of the capacity of data tables related to the number analysis, office directions, trunks, and routes. In the actual application, you may need to expand the call source table, LAI information table, dialing check table, and called number special processing table. Modifying data tables may greatly affect the system. Before you modify a data table, contact a technical support engineer of Huawei.
Table 1-2 shows the capacity of data tables. Table 1-2 Capacity of data tables related to MA networking Name of data table Local office table Mobile local office table LAI information table Called table number analysis Table ID TID51 TID52 TID54 TID105 TID119 TID126 Default maximum number of tuples 16 16 1,024 30,000 4,096 1,024
Caller number analysis table Calling line presentation table identification processing
Incoming number pre-processing table Outgoing number pre-processing table Office direction table Route table Route analysis table Trunk SS7 data table
TID134 TID137 TID300 TID301 TID302 TID305
1,024 1,024 2,048 2,000 512 4,000
Name of data table Trunk group and sub-route table Trunk group table Sub-route table SCCP DPC table SCCP sub-system table SCCP global title table BSC table RNC table Call source table Dialing check table Called number processing table Note: special
Table ID TID306 TID307 TID310 TID366 TID367 TID368 TID801 TID807 TID116 TID819 TID106
Default maximum number of tuples 20,000 4,000 2,000 512 1,024 4,096 64 64 255 512 1,024
LAI = Location Area Identification; SS7 = Signaling System Number 7; SCCP = Signaling Connection Control Part; DPC = Destination Point Code
IV. Limitation of the Number of Trunk Circuits

In MA networking, the number of trunk circuits configured in an MSOFTX300 is as follows:
z
For SS7 trunk circuits, the MSOFTX3000 can support 200 thousand circuit identification codes (CICs) at most. This is equal to 6,250 E1s. For A interface circuits, the MSOFTX3000 can support 288 thousand CICs (36 x 8 thousand) at most. This is equal to 10 thousand E1s considering redundancy. For Bearer Independent Call Control Protocol (BICC) trunk circuits, the MSOFTX3000 can support 360 thousand CICs at most.
When planning an MA network, estimate the number of CICs required by trunk circuits, A interface circuits, or BICC signaling in each local network. Make sure that the number of CICs does not exceed the limit.
Chapter 2 Networking Principles

2.1 Basic Principles of Multi-Area Networking
Figure 2-1 shows a typical model of the MA networking.
MSOFTX3000 Virtual MSC1/ VLR1 DPC1 Virtual MSC2/ VLR2 DPC2
MGW1
MGW2
MGW3
Figure 2-1 Typical model of the MA networking Basic principles of MA networking are as follows:
z
With multiple MSC numbers, several logical entities map to the same physical entity. For external physical entities, the MSOFTX3000 provides several MSC servers.
Multiple MSC/VLR (visitor location register) numbers are used. One or more signaling points are used at the same time. Roaming numbers are assigned according to virtual MSC numbers. An MA network is divided according to virtual MSC numbers only. If the LAI of each local network is assigned separately and an LAI is used by one MSC only, you can assign roaming numbers according to LAIs.
For external physical entities, virtual MSC servers of an MA network can be regarded as real MSC servers. Therefore, you can enable all functions of the system without changing NEs or the network structure.
Note: External NEs often do not use LAIs to assign roaming numbers. In this case, do not assign roaming numbers according to LAIs.
2.2 Principles of Voice Channel Networking

2.2.1 Multiple MSC Numbers and Single MGW
Figure 2-2 shows a model of the MA networking with one MSOFTX3000, one MGW, and multiple MSC numbers.
MGW
BSC1: MSC1/VLR1/LAI1
BSC2: MSC2/VLR2/LAI2
Figure 2-2 MA networking with one MSOFTX3000, one MGW, and multiple MSC numbers The principles of the networking mode are shown in Table 2-1. Table 2-1 Principles of MA networking with one MSOFTX3000, one MGW, and multiple MSC numbers Item Principle The networking mode is suitable for the following network reconstruction cases:
z
Suitable situation
z
In a traditional network, several areas share one set of equipment. In this case, you do not need to change the network topology. You can set up multiple MSC servers logically to identify different areas. The networking mode enables you to distinguish between different areas when charging the fees and measuring the traffic.
MSC number Call processing and bearer control Billing
You can set multiple virtual MSC numbers to identify different areas. For external NEs, virtual MSC servers of an MA network are regarded as real MSC servers. Services of different areas are processed by one MGW. Without going through a toll office, the calls between different areas are connected through one MGW. Bills are sorted according to different MSC numbers.
Item Traffic statistics
Principle Different MSC numbers map to different multi-area statistics indexes. This is used to distinguish between the traffic of different areas.
2.2.2 Multiple MSC Numbers and Multiple MGWs Without Intermediate Bearer
Figure 2-3 shows a model of the MA networking with one MSOFTX3000, multiple MSC numbers, and multiple MGWs. There is no intermediate bearer between MGWs.
MGW1
MGW2
Figure 2-3 MA networking with one MSOFTX3000, multiple MSC numbers, multiple MGWs, and no intermediate bearer The principles of the networking mode are shown in Table 2-2. Table 2-2 Principles of MA networking with one MSOFTX3000, multiple MSC numbers, and multiple MGWs Item Principle The networking mode is designed for the initial stage of MA network construction, and is suitable for the following network reconstruction cases: Suitable situation
z
Existing switches are placed in different areas. This helps network operators to make full use of their existing networks. In the reconstructed network structure, one MSOFTX3000 controls multiple MGWs. One or more MGWs belong to one area. That is, each MGW belongs to a logical MSC server.
MSC number
You can set multiple virtual MSC numbers to identify different areas. For external NEs, the virtual MSC servers are equal to real MSC servers because the call models do not change.
z z
Call processing and bearer control
There is no intermediate bearer between MGWs. The network structures of different areas do not change. The calls between local networks are transferred by TMSCs. The handover between them is regarded as inter-office.
Item Billing Traffic statistics
Principle Bills are sorted according to different MSC numbers. Different MSC numbers map to different multi-area statistics indexes. This is used to distinguish between the traffic of different areas.
2.2.3 Multiple MSC Numbers and Multiple MGWs with Intermediate Bearer
Figure 2-4 shows a model of the MA networking with one MSOFTX3000, multiple MSC numbers, and multiple MGWs. There are intermediate bearers between the MGWs.
MGW1
MGW2
Figure 2-4 MA networking with one MSOFTX3000, multiple MSC numbers, multiple MGWs, and intermediate bearers The principles of the networking mode are shown in Table 2-3. Table 2-3 Principles of MA networking with one MSOFTX3000, multiple MSC numbers, and multiple MGWs Item Principle The networking mode is designed for the later stage of MA network construction. It is preferred if network operators want to transit from the current networks to future ones. Suitable situation Bearers used between MGWs of different local networks are as follows:
z z z
TDM IP Other bearers
MSC number
You can set multiple virtual MSC numbers to identify different areas. For external NEs, the virtual MSC servers are equal to real MSC servers.
Item
Principle There are two cases according to different bearer modes:

z
Call processing and bearer control
When IP bearers are used between MGWs, a mesh network is set up. There is no special requirement on network topology. When TDM bearers are used between MGWs, mesh connections can be set up if there are no more than three cities. If there are more than three cities, you are recommended to connect local networks with a virtual hub city to form a star network so that the network topology is simplified. Otherwise, the network topology is complicated, and makes maintenance difficult.
Billing Traffic statistics
Bills are sorted according to different MSC numbers. Different MSC numbers map to different multi-area statistics indexes. This is used to distinguish between the traffic of different areas.
The following are two typical kinds of bearers between local networks of MA networking:
z z
IP bearer TDM bearer
Note: To make subsequent network optimization and expansion easy, you are recommended to use IP bearers between MGWs.
I. IP Bearer
Figure 2-5 shows a model of the MA networking with one MSOFTX3000, multiple MSC numbers, and multiple MGWs. There are IP bearers between local networks.
IP Backbone
MGW3 MGW1 MGW2
Local PLMN1
Local PLMN2
Local PLMN3
Figure 2-5 MA networking with IP bearers between local networks As shown in the above figure, MGWs of local networks are connected through an IP backbone network. In this bearer mode, the switching layer forms a plane. Table 2-4 shows advantages and disadvantage of the IP bearer mode. Table 2-4 Advantages and disadvantages of the IP bearer mode Item
z
Description Local networks share the bandwidth of the IP backbone network. The calls and routing between local networks are optimized. The speed of network construction is high. The network structure is based on NGN. This enables seamless network expansion.
Advantage
z z z
Disadvantage
You may need to build a new IP backbone network before setting up an MA network. This affects the network structure.
II. TDM Bearer

When an MA network contains one MSOFTX3000, multiple MSC numbers, multiple MGWs, and TDM bears between MGWs, the network topology of local networks falls into two modes:
z
Mesh topology
Figure 2-6 shows a model of the MA networking with one MSOFTX3000, multiple MSC numbers, and multiple MGWs. TDM bearers are set up between MGWs, forming a mesh topology.
MSOFTX3000 Virtual MSC1/ VLR1 DPC1 Virtual MSC2/ VLR2 DPC2 Virtual MSC3/ VLR3 DPC3
MGW3
MGW1
MGW2
Figure 2-6 MA networking with TDM bearers between local networks (mesh topology)
z
Star topology
Figure 2-7 shows a model of the MA networking with one MSOFTX3000, multiple MSC numbers, and multiple MGWs. TDM bearers are set up between MGWs, forming a star topology.
MSOFTX3000 Virtual MSC1/ VLR1 DPC1 Virtual MSC2/ VLR2 DPC2 Virtual MSC3/ VLR3 DPC3
MGW3 MGW1 MGW2
Figure 2-7 MA networking with TDM bearers between local networks (star topology) In this mode, all calls of local networks are transferred to the MSOFTX3000 through MGW3, where the hub city mapping to MSC3 is located. Table 2-5 shows advantages and disadvantages of the TDM bearer mode.
Table 2-5 Advantages and disadvantages of the TDM bearer mode Item
z
Description You can make full use of existing TDM transmission equipment and resources. You do not need to set up a new bearer network. This makes the existing network construction and maintenance easy. You can set up an MA network quickly. No IP backbone network is needed. In a network with the earlier mentioned mesh topology, some voice channels are wasted. In a network with the earlier mentioned star topology, transit routing through a hub city wastes resources. This impairs advantages of the MA network.
Advantage
z
Disadvantage
2.3 Principles of Signaling Networking

Table 2-6 shows the classification of signaling networking. Table 2-6 Classification of signaling networking Classification rule Classification according to amounts of MSC numbers and signaling points (SPs) Classification according to signaling transmission network between MSOFTX3000 and MGW Subcategory Multiple MSC numbers and single SP Multiple MSC numbers and multiple SPs IP signaling transmission network between MSOFTX3000 and MGW TDM signaling transmission network between MSOFTX3000 and MGW Signaling networking between MSOFTX3000 and other core NEs Classification according to signaling networking between MSOFTX3000 and external NEs Signaling networking between MSOFTX3000 and local BSC Signaling networking between MSOFTX3000 and local RNC
2.3.1 Classification According to Amounts of MSC Numbers and Signaling Points

According to the amounts of MSC numbers and signaling points (SPs), signaling networking falls into the following two modes:
z z
Multiple MSC numbers and single SP Multiple MSC numbers and multiple SPs
Table 2-7 shows the comparison of the two modes.

Table 2-7 Comparison of the two signaling networking modes Item Multiple MSC numbers and single SP Multiple virtual MSC/VLR numbers are configured. The same physical entity maps to multiple logical entities. For external NEs, the logical MSC servers are equal to real MSC servers, but with only one originating signaling point code (OPC). Multiple MSC numbers and multiple SPs Multiple virtual MSC/VLR numbers are configured. The same physical entity maps to multiple logical entities. For external NEs, the logical MSC servers are equal to real MSC servers, and with multiple OPCs.
Rules for assigning MSC numbers and SPs
Note: The MSOFTX3000 is configured with only one SP. A unique MSC number is assigned to each local network.
Only one record is configured for both the mobile local office table and the local office table. z Mainly set parameters such as National prefix and International number prefix for the mobile local office table. z Each multi-area statistics index in the multi-area statistics index table maps to an MSC number. z Multiple records of SCCP GT (global title) data for multiple MSC numbers map to the local office. Note: The record in the mobile local office table and the local office table includes the virtual MSC server directly connected with the signaling transfer point (STP).
z z
Note: This mode requires the MSOFTX3000 to support the functions of multi-SP and roaming number assignment according to MSC numbers.
Effect on data configuratio n
You need to set multiple records for both the mobile local office table and local office table. The records map to MSC numbers in the multi-area statistics index table. SCCP GT data of each MSC number maps to a virtual MSC server SPs.
Effect on billing
For local networks, bills are sorted and traffic is measured according to virtual MSC numbers. For external NEs, the virtual MSC servers are equal to real MSC servers. All existing system functions can be carried out without changing external NEs.
For local networks, bills are sorted and traffic is measured according to virtual MSC numbers. For external NEs, the virtual MSC servers are equal to real MSC servers. All existing system functions can be carried out without changing external NEs.
Item Effect on resources utilization
Multiple MSC numbers and single SP The mode needs to use multiple MSC/VLR numbers.
Multiple MSC numbers and multiple SPs The mode needs to use multiple MSC/VLR numbers and multiple SPs at the same time.
z
Effect on other NEs

z
For external NEs, the mode has only one SP. Therefore, there is only one lower layer MTP link. In data link layer, signaling of different MSC servers is sent to the peer NE through the same SP. For the SCCP layer, caller GTs of outgoing CAP and MAP contain MSC numbers to which the virtual MSC servers map.
For external NEs, different MSCs have different SPs. Therefore, lower layer MTP links go through the same SP that is assisted by other SPs. Or each SP has its own link to directly interconnect with the peer NE. For details, see the description of signaling route followed. For the SCCP layer, caller GTs of outgoing CAP and MAP contain MSC numbers and OPCs to which the virtual MSC servers map. Multiple virtual MSC servers fully interwork with external NEs and provide the function of multiple real MSC servers. If you want to expand the capacity of equipment or put it in other places during network upgrade or when subscriber number increases, you only need to modify the setting and connections of the MSOFTX3000. There is no need to modify data of external NEs.
Effect on network upgrade
The single SP setting cannot fully interwork with external NEs and provide the function of multiple real MSC servers. If you want to expand the capacity of equipment or put it in other places during network upgrade or when subscriber number increases, modify the data of external NEs and the setting and connections of the MSOFTX3000.
The networking mode is not recommended.
Note:
Because the networking mode uses only one SP, you need to modify the setting of some external NEs. The networking mode is not recommended because it limits network upgrade or expansion in the future. If you want to use the networking mode, contact Huawei.
Comparison
You are recommended to use this networking mode.
Note: Multiple SPs here means that each local network has a 24-digit national active SP and one or more 14-digit national standby SPs.
z z
In general, only one 14-digit national standby SP is configured. If the SPs of different BSCs are the same, local networks use different 14-digit national standby SPs to connect the BSCs so that you can keep the data configuration of the BSCs unchanged.
I. Multiple MSC Numbers and Single SP

Figure 2-8 shows a typical model of the networking mode.
MSOFTX3000 DPC1 Virtual MSC1/ VLR1 Virtual MSC2/ VLR2
MGW1
MGW2
Figure 2-8 Networking model with multiple MSC numbers and single SP
II. Multiple MSC Numbers and Multiple SPs

Figure 2-9 shows a typical model of the networking mode.
MGW1
MGW2
Figure 2-9 Multiple MSC numbers and multiple SPs In the actual networking, signaling routing is in two modes: assistant and direct connection.

z
Assistant mode
Caution: This mode cannot be used when the number of local networks is greater than three, because the assistance capability of SPs is limited and the mode requires to change signaling routing structure of the external network. This mode is not recommended in the actual networking.
When the assistant mode is used, the MSOFTX3000 provides only one SP to directly interconnect with the STP. Other SPs connect with the STP through the SP. They use GT direct connection mode to connect with the remote home location register (HLR) without being transferred by STPs. GT routing data of other SPs of the MA network must be modified. Otherwise, straight routes from other SPs to the HLR are created. If the signaling from the HLR back to the MSOFTX3000 is transferred by an low level STP (LSTP), external signaling routing structure is affected.
z
Direct connection mode
Figure 2-10 shows a typical model of the direct connection mode.

HLR1 HLR2 HLR3

SCP
H1/H2 T1/T2
MSOFTX3000
L1/L2 T1/T2
MGW1 MGW2 BSS11
MGW3
BSS3 BSS12 BSS21 Area A (MSC1/VLR1/LAI1) SPC: 06FE1E MSC number: 8613710001 BSS22 Area C (MSC3/VLR3/LAI3) SPC: 06FE1D MSC number: 8613710003
Area B (MSC2/VLR2/LAI2) SPC: 06FE1C MSC number: 8613710002
Narrowband signaling H.248 signaling Voice channel
H1/H2: high-level signaling transfer point (HSTP) BSS: Base Station Subsystem
L1/L1: Low-level signaling transfer point (LSTP)
Figure 2-10 Typical networking model of direct connection mode As shown in the preceding figure, the MSOFTX3000 provides three virtual SPs A, B, and C to interconnect with H1/H2 and L1/L1. In this process, link sets and SS7 links are set up. The three virtual SPs of the MSOFTX3000 do not work in the assistant mode. In HLR addressing, the signaling point code (SPC) and MSC numbers that the local networks belong to are used for local networks to interconnect with the HLRs to which the local networks are homed. In this mode, direct links are configured between multiple SPs and local HLRs. The DPC addressing mode and transfer through MTP layer are selected when the GT data of the SCCP layer is configured. The local office chooses different link sets for different OPCs so that direct links can be used for local HLRs and links through STP are used for remote HLRs.
The direct connection mode requires the STP to support SP transfer at the MTP layer. This is different from GT transfer at the SCCP layer. The routing is the same as that of the existing network. The only change you need to make in this mode is to configure data such as DSP and SSN at the SCCP layer on the HLR side. The data maps to multiple SPs of the local office.
Note: The direct connection mode is compatible with the structure of existing signaling network. Its routing is the same as that of the existing network. Therefore, you do not need to change the routing structure of the existing network. The direct connection mode has little impact on the existing network and you are recommended to use it.
2.3.2 Classification According to Signaling Transmission Network Between MSOFTX3000 and MGW
There are two kinds of signaling transmission networks between the MSOFTX3000 and the MGW:
z z
IP signaling transmission network TDM signaling transmission network
I. IP Signaling Transmission Network Between MSOFTX3000 and MGW

When an IP signaling transmission network is used between the MSOFTX3000 and the MGW, all signaling except broadband BICC and the Session Initiation Protocol (SIP) is sent from the MGW to the MSOFTX3000 through M2UA or M3UA agent. The networking mode used depends on whether both the feature of MA and the feature of dual-homing are used in a network:
z
If only the MA feature is used, you can connect some pure signaling NEs with the MSOFTX3000 directly or through STPs. This avoids the risks brought by signaling gateway (SG) transfer.
If both features are used, narrowband signaling cannot be switched over. You need to use the MGW to transfer all signaling. When pure signaling NEs can also transfer broadband signaling, you are recommended to use M3UA to connect these NEs with the MSOFTX3000. In all signaling transferred by the MGW, the BSC uses M2UA agent, the RNC and SS7 trunks use M3UA agent, and the agent of the PRA signaling is IUA. The R2 signaling is processed by H.248 of the Mc interface. Signaling of the Mc interface is borne over SCTP links directly. Other pure signaling NEs use M2UA or M3UA agent.
The IP signaling network with the MGW transferring signaling provides enough bandwidth, and makes future network expansion and upgrade easy. Network operators are recommended to use the IP signaling networking with a dedicated signaling bearer network. This helps network operators to directly transit to 3G networks in the future.
Note: If signaling is transferred by M3UA agent, you need to assign signaling point codes (SPCs) to the MGWs.
II. TDM Signaling Transmission Network Between MSOFTX3000 and MGW
Caution: This mode is not recommended in the actual networking.
In this mode, the existing TDM signaling transmission network is used to transmit signaling between the MSOFTX3000 and the MGW. Signaling of pure signaling NEs such as the short message service (SMS) center, HLR, service control point (SCP), and STP is sent to the MSOFTX3000 through STPs. The nearby access policy is used for networking to save transmission resources. For non-pure signaling NEs such as the BSC, RNC, SS7 trunks, R2 trunks, PRA trunks, and NEs using the Mc interface signaling, signaling is transferred by the MGW:
z z z
SS7 is transmitted through the use of TDM semi-permanent connections. The RNC uses ATM 2M bearers to transmit MTP3B signaling. The H.248 signaling of the Mc interface is transmitted by dedicated routes in the TDM mode or by MTP3B signaling over ATM 2M. R2 signaling is processed by the H.248 signaling of the Mc interface. The PRA signaling uses IUA agents. It is transmitted by dedicated routes in the TDM mode.
z z
This signaling transmission mode is often used in a 2G MA network without a separate signaling bearer network. Existing signaling transmission resources are used to set up a signaling network.
2.3.3 Classification According to Signaling Networking Between MSOFTX3000 and External Network Elements
I. Signaling Networking Between MSOFTX3000 and Other Core Network Elements
HLR, STP, and equipment such as MSC and SCP that are transferred by STPs are connected only with the MSOFTX3000. In general, they are in the same office as the MSOFTX3000. The traditional TDM mode is often used in existing networks. In the case of broadband signaling, you are recommended to use M2UA or M3UA so that broadband signaling can be transferred by the MGW. This makes future service development easy. When both the feature of MA and the feature of dual-homing are used in a network, external NEs must be connected through broadband signaling.
II. Signaling Networking Between MSOFTX3000 and Local BSC

The BSC is connected with a local MGW through E1 lines. The signaling is converted into M2UA by the MGW/SG for interconnecting with the MSOFTX3000.
III. Signaling Networking Between MSOFTX3000 and Local RNC

The RNC is connected with the local MGW through ATM. The signaling is converted into M3UA by the MGW/SG for interconnecting with the MSOFTX3000.
Chapter 3 Service Implementation Principles

3.1 Principle of Multiple Virtual MSC/VLR Numbers
Figure 3-1 shows a model of the MA networking with one MSOFTX3000, multiple SPs, and multiple MSC numbers.
HLR1 HLR2 HLR3 SCP
H1/H2 T1/T2
MSOFTX3000
L1/L2 T1/T2
MGW1 MGW2 BSS11
MGW3
BSS3 BSS12 BSS21 Area A (MSC1/VLR1/LAI1) SPC: 06FE1E MSC number: 8613710001 BSS22 Area C (MSC3/VLR3/LAI3) SPC: 06FE1D MSC number: 8613710003
Figure 3-1 MA networking with multiple MSC numbers and multiple SPs As shown in the preceding figure, each local network has its own MSC number and VLR number. In this way, the effect of the networking model on other NEs is minimized. The above networking mode makes it easy for you to collect billing and performance data and manage the operation of local networks. Figure 3-2 shows the logic principle for carrying out MA networking with multiple MSC numbers and multiple SPs.
MSC0/DPC0 MSC1/DPC1 MSC2/DPC2 MSC15/DPC15
MSOFTX3000 ...
MSC Server-0 Service subsystem MSC Server-1 Trunk subsystem MSC Server-2 MSC Server-15
Gateway subsystem
Signaling subsystem
Figure 3-2 Logic principle for carrying out MA networking with multiple MSC numbers and multiple SPs
3.2 Principle of Multiple Area Code Function

Figure 3-3 shows the principle for carrying out the multiple area code function in the MA networking.
TMSC
MSOFTX3000 MGW1 MGW2
BSS1
GW1
GW2
BSS2
Area code: 0414xxxxxxx
Area code: 0415xxxxxxx
Figure 3-3 Principle for carrying out the multiple area code function in MA networking Different call sources are configured according to the location areas (LAs) of the callers, or incoming trunk office directions. Different area codes of call sources are configured as caller area codes. Different number analysis modes are configured for different call sources to support multiple area codes. An MA network supports the multiple area code function because:
z
In the routing analysis of calls, the multiple area code function makes it easy for you to configure routes between local networks. The dialing habit of subscribers requires local networks to have different area codes. Thus, subscribers can use different ways to dial numbers. For example, when calling a mobile subscriber, a local fixed-line subscriber does not need to dial the area code, and a remote fixed-line subscriber needs to dial the area code.
If different local networks have different area codes, you can check the data of local network traffic statistics more conveniently. An MA network supports the routing according to caller numbers. This prevents number segments of fixed network from overlapping in the case of different area codes.
3.3 Principle of Roaming Feature

The roaming feature includes location update, roaming types, and roaming restriction.
3.3.1 Location Update

When a mobile subscriber roams from one local network to another in an MA network, a location update happens. After the location update, the data such as the MSC number, VLR number, and subscriber location changes. The MSOFTX3000 can set the roaming feature of subscribers in one of the following two modes:
z z
Inter-office location update Intra-office location update
Caution:
z
You are recommended to use the intra-office location update mode when a multi-are network is set up in a city with multiple districts. You are recommended to use the inter-office location update mode when an MA network is set up across multiple cities or regions. For the setting of the software parameter, see section 4.3.1 Setting Location Update Mode."
I. Inter-Office Location Update

In this mode, the processing procedures are the same as that of the traditional GSM inter-office location update. Location updates in this mode do not affect IN services and roaming number assignment when subscribers act as callees.
II. Intra-Office Location Update

When this mode is used, the MSOFTX3000 needs to update MSC numbers, VLR numbers, and subscriber locations stored in the VLR. Although this mode reduces the amount of location update messages transmitted between the MSOFTX3000 and the HLR, you need to note the following:
z
For IN services, MSC numbers and VLR numbers stored on the HLR and SCP sides are those of the original LA. This causes the billing of the called IN services to be inaccurate.
When a subscriber is called, the HLR uses the original MSC number to request the mobile station roaming number (MSRN) of the subscriber. The system can assign
a roaming number according to the MSC number or LAI of the actual LA of the subscriber. This ensures calls to be processed successfully.
III. Data Protection Measures of Location Update

According to the standard protocol, the MSC server does not follows a sequence when processing the messages for adding subscriber data sent from the HLR (message 1) or for removing original VLR subscriber data (message 2). As a result of this, after a location update between local networks, the subscriber data added by message 1 is removed by message 2 sent from the HLR. The MSOFTX3000 solves the problem by using a timer protection mechanism so that the system follows a specific sequence when processing messages 1 and 2. This ensures that the subscriber data is valid and correct, and improves system reliability.
Caution: The duration of the timer is controlled by a software parameter. For the setting of the software parameter, see section 4.3.2 Setting Duration of Protecting Location Update Data by Timer.
3.3.2 Roaming Types

The MSOFTX3000 uses the IMSI of a subscriber and the MSC number of the local network to judge the roaming type of the subscriber. The roaming type may be local subscriber or roaming subscriber.
3.3.3 Roaming Restriction

For the HLR, the virtual MSCs/VLRs are equal to real MSCs/VLRs. An LA in an MA network belongs to a VLR. Therefore, in the MA networking, you can use VLR list or ZoneCode to carry out the Local Smart service.
3.4 Principle of Roaming Number Assignment

In an MA network, the system assigns roaming numbers according to MSC numbers or LAI numbers. The former is often used. If you assign roaming numbers according to LAI numbers, make sure that the LAI assigned to each local network is unique.
Caution: MSC numbers are used to assign roaming numbers at present.
3.5 Principles of Call and Route Selection

3.5.1 Call Data Obtaining
This section describes how to obtain key data in a call.
I. Call Between Local Mobile Subscribers

To obtain key data in an intra-office call between local mobile subscribers, use the following modes:
z
The MSC number and the multi-area statistics index on the mobile side are obtained from the LAI information table. The area code is obtained by using the call source code of the caller or callee to query the call source table.
II. Mobile Originated Outgoing Call

To obtain key data in a mobile originated (MO) outgoing call, use the following modes:
z
The MSC number and the multi-area statistics index on the caller mobile side are obtained from the LAI information table. The area code is obtained by using the call source code of the caller to query the call source table. The multi-area statistics index on the called trunk side is obtained from the trunk group table of the callee. In the case of broadband signaling such as BICC and SIP, the data is obtained from the office direction table.
The MSC number and area code of the callee is obtained by using the call source code of the called trunk group to query the call source table. In the case of broadband signaling, the data is obtained from the office direction table of the callee.
III. Call from Incoming Trunk to Local Mobile Subscriber

To obtain key data in an call from an incoming trunk to a local mobile subscriber, use the following modes:
z
The multi-area statistics index of the caller is obtained from the trunk group table of the caller. In the case of broadband signaling such as BICC and SIP, the data is obtained from the office direction table.

z
The MSC number and area code of the caller is obtained by using the call source code of the calling trunk group to query the call source table. In the case of broadband signaling, the data is obtained from the office direction table of the caller.
The MSC number and the multi-area statistics index on the callee mobile side are obtained from the LAI information table. The area code is obtained by using the call source code of the caller or callee to query the call source table.
IV. Call from Incoming Trunk and Through Tandem Office

To obtain key data in a call from an incoming trunk and through a tandem office, use the following modes:
z
The multi-area statistics index of the caller is obtained from the trunk group table of the caller. In the case of broadband signaling such as BICC and SIP, the data is obtained from the office direction table.
The MSC number and area code of the caller is obtained by using the call source code of the calling trunk group to query the call source table. In the case of broadband signaling, the data is obtained from the office direction table of the caller.
The multi-area statistics index on the called trunk side is obtained from the trunk group table of the callee. In the case of broadband signaling such as BICC and SIP, the data is obtained from the office direction table.
The MSC number and area code of the callee is obtained by using the call source code of the called trunk group to query the call source table. In the case of broadband signaling, the data is obtained from the office direction table of the callee.
Note: For the above four call models, the data of the caller replaces that of the callee when a call fails to be connected and the call request is not sent to the callee side.
3.5.2 Call Routing

The principles of call routing in an MA network are as follows:
z
The basic dialing principles are the same as those of non-MA networks except that a fixed-line caller needs to dial 0 first when calling mobile subscribers of other local networks. You need to configure data so that a call is restricted according to the call source and an announcement is played if the caller does not dial 0 first.

z
In the default normalization mode of caller number format, the caller area codes configured for different call sources can be used for processing. For such shared outgoing called numbers as fixed-line numbers and mobile numbers of other local networks, and such toll numbers of non-MA networks as fixed-line numbers of non-local networks, mobile numbers of other networks, and mobile roaming numbers of local networks, you need to configure route selection source codes according to call sources. This enables the system to select different outgoing routes in different conditions.
In an intra-office call between mobile subscribers of local networks, set the mobile network roaming number of the MA network as PLMN intra MSC if there are intermediate bearers between MGWs.
The calls and handover between mobile subscribers of the two virtual MSC servers in an MA network can be regarded as intra-office or inter-office depending on the requirement of network operators or whether there are intermediate bearers between MGWs of different local networks. If there are intermediate bearers between MGWs, the calls are regarded as intra-office. In this case, set roaming numbers and handover numbers of the number analysis data as PLMN intra MSC. If there are no intermediate bearers between MGWs, the system sends the roaming numbers obtained in calls between mobile subscribers of local networks from the local office to a gateway office or a tandem office that then sends them back to another virtual MSC server of the local office. This generally happens when existing bearer connections are used at the initial stage of MA network construction. The handover between local networks is regarded as inter-office. You can set the handover signaling to be processed at the local office. Set the handover speech path as follows: Handover numbers are sent from the local office to a gateway office or a tandem office that then sends them back to another virtual MSC server of the local office for processing.
3.6 Principles of Paging Optimization
Caution:
z
In the MA networking, enable paging optimization for the whole MA network. Paging is done only in the MSC/VLR LA where the callee is located. A software parameter controls whether to optimize paging. For the setting of the software parameter, see section 4.3.3 Setting Parameter of Optimizing Paging in Entire Multi-area Network.
Paging over the whole network needs to be started when there is no callee data (mainly LAI) in the local VLR. If paging optimization is not enabled, common paging in an MA network has the following impact on the system:
z
If paging over the whole MA network is done after switchover, multiple virtual MSC servers send paging requests at the same time. This causes the access network to be overloaded.
When the paging times entity is measured in a paging process, the VLR cannot obtain the LAI of the callee because of the lack of subscriber data. When the call completion times entity is measured, the VLR has obtained the LAI of the callee. As a result, paging times is counted into the multi-area statistics index of the caller, while call completion times into that of the callee LAI. It may happen that a multi-area statistics index contains call completions times, but not paging times.
The MSOFTX3000 can control whether to do paging in the control area of the virtual MSC server that maps to the MSC number contained in the PRN message sent from the HLR.
3.7 Principle of Handover

You can set the handover between two local networks as intra-office or inter-office. By using subscribers original and destination LAs contained in the handover request message, the MSOFTX3000:
z z
Queries system data configuration Obtains source and destination MSC numbers and writes them into handover bills
The principles of handover are as follows:

z
If the handover between two local networks is set to intra-office, MGWs of the two local networks must be directly connected. If the handover between two local networks is set to inter-office, outgoing routes need to be configured according to call sources and handover numbers so that voice circuits between MGWs of the two local networks are connected by a GMSC/TMSC.
To set a handover to intra-office or inter-office, configure the handover relationship between virtual MSC servers of the two local networks. By default, the system chooses intra-office handover.
3.8 Principles of IN Service

According to how an MA network affects the IN service, principles of the IN service in an MA network refer to the obtaining and entry of data such as Location Info, MSC Address, and Location Number. The data is required in the IN service. The data can be obtained and entered in the following two modes:

z z
Destination network mode Non-destination network mode
3.8.1 Destination Network Mode

The IN service principles in the destination network mode fall into two categories:
I. Caller IN Service Principles

The data such as Location Info, MSC Address, and Location Number is required in the caller IN service flow. It can be obtained in the following ways:
z
Location Info can be obtained according to the LA information contained in the service request message initiated by callers. MSC Address and Location Number can be obtained according to the system setting that can be queried by using caller LA information and the caller area code.
II. Callee IN Service Principles

The data required in the callee IN service flow can be obtained in the following ways:
z
The MSC Address on the caller side is used as the local office address sent to the SCP. Location Info can be obtained according to the IN data contained in the SRI_ACK message sent from the HLR.
3.8.2 Non-Destination Network Mode

Principles of the non-destination network mode are as follows:
z
In general, Location Info is contained in the caller IN service flow. It may not be contained in the callee IN service flow. When the data is sent at the detection point (DP) of caller and callee IN services, the system enters the MSC Address of the caller. When the data is sent at the DP of caller IN service, the system enters the Location number of the caller. According to specifications of some network operators for obtaining roaming numbers, when the data is sent at the DP of callee IN service, you can fill in the Location number with the callees VLR number contained in the SRI_ACK message. If no VLR number of the callee is contained in the SRI_ACK message, fill in the Location number with the MSC number on the caller side.
3.9 Principle of Lawful Interception Service

An MA network affects the lawful interception service in the following aspect: Area codes need to be analyzed in number analysis to achieve different routing for different fixed-line phones with the same number in different local networks. In general, the interception output number is a local fixed-line number.
Caution: Whether an output number of the number analysis contains the area code is controlled by a software parameter. For the setting of the software parameter, see section 4.3.4 Setting Monitoring Parameter in Multi-area Network.
3.10 Principle of Charging

The charging implementation in an MA network and that in a non-MA network are the same:
z
The MSOFTX3000 can distinguish between different areas according to the virtual MSC numbers. For external entities, the virtual MSC servers are independent. The charging principles are the same as that of a non-MA network. You do not need to do special data configuration at the billing center.
Toll charging can be carried out when subscribers of two local networks call each other. The system can use LAs or VLR numbers of callers or callees in IN calls to distinguish between different areas and charge the calls successfully. You do not need to change the setting of the SCP.
In the actual applications, note the following:

z z
Principles for the entry of MSC numbers on the caller/callee side in bills Principles for saving bill files in the iGWB
3.10.1 Principles for the Entry of MSC Numbers on the Caller/Callee Side in Bills
The system enters MSC numbers on the caller/callee side in bills according to the following principles:

z
In general, the system enters MSC numbers on the caller side for bills on the caller side (that is, bills for calls of callers or incoming calls). The system enters MSC numbers on the callee side for bills on the callee side (that is, bills for calls of callees or outgoing calls).
The system enters MSC numbers on the caller side in bills for mobile originated calls (MOCs) and mobile IN originated calls. The system enters MSC numbers on the callee side in bills for mobile terminated calls (MTCs) The system enters MSC numbers on the caller side in bills for tandem calls. The system enters MSC numbers on the caller side in bills for supplementary services and HLR query. The system enters MSC numbers on the caller side in gateway office incoming bills. The system enters MSC numbers on the callee side in gateway office outgoing bills. The system enters MSC numbers on the caller side (that is, GMSC) in callee IN bills (TCAMEL). The system enters MSC numbers on the caller side in bills for mobile originated short messages (SMs MO). The system enters MSC numbers on the callee side in bills for mobile terminated short messages (SMs MO).
z z
For example, in the Local Smart service provided by the networking in Figure 3-4:
z z
The MSC number entered in the bill for caller MOC is MSC1. The MSC number entered in the bill for callee MTC is MSC2.

HLR1 HLR2 HLR3

SCP
H1/H2 T1/T2
MSOFTX3000
L1/L2 T1/T2
(2)
(1)
MGW1
(3) MGW2
MGW3
BSS11
(4) BSS3 BSS12 BSS21 BSS22 Area C (MSC3/VLR3/LAI3) SPC: 06FE1D MSC number: 8613710003
Area A (MSC1/VLR1/LAI1) SPC: 06FE1E MSC number: 8613710001
Figure 3-4 Networking for the Local Smart service
3.10.2 Principles for Saving Bill Files in the iGWB

To meet the requirement of bill auditing and ensure the continuity of billing, bill files of an MA network must be generated based on areas. When saving bill files, the iGWB creates a path according to MSC numbers. The bills of different local networks are saved in the corresponding folder. The billing center can use MSC numbers in bills or paths to obtain bills. After sorting the bills, the billing center sends them to billing centers of local networks for processing.
Note: For details about bill saving, see HUAWEI iGateway Bill User Manual.
3.11 Principle of Traffic statistics

3.11.1 Basic Principles
The basic principles of traffic statistics of the MA networking are as follows:
z
In an MA network, the system uses the multi-area statistics index of subscribers to measure the traffic. The traffic of the whole MA network as well as that of a local network can be measured.
Each local network has a number. The measurement units are classified according to local networks that subscribers belong to. The multi-area statistics index determines the virtual MSC server to which each traffic statistics unit belongs. If mobile subscribers of two local networks call each other, the caller and callee area indexes are added into the intra-office traffic measurement to indicate the real traffic.
The traffic statistics unit of MSC handover measures the handover of global traffic. If the handover between two local networks is set to intra-office, the measurement unit measures the traffic only in the local network where the source handover cell is located.
An outgoing call is measured according to the caller area index. An incoming call is measured according to the area index of the incoming trunk. A tandem call is measured according to the area indexes of both the incoming and outgoing trunks, and so on.
3.11.2 Ways for Obtaining Multi-Area Statistics Index

You can obtain the multi-area statistics index in the following ways:
z
For office directions on the mobile side, the index can be obtained from the LAI information table. Because there are shared office directions, the index can be obtained from the trunk group table for narrowband trunk office directions such as ISUP, TUP, PRA, and R2. For 3G networks, set the index in the RNCID table for 3G inter-office handover.
If the local office has multiple SPs, and the peer office has only one SP, the local office has multiple office direction numbers. The data configuration is the same as that of a non-MA network. Because the peer office has only one office direction number, only trunk groups can be used to distinguish between different trunk circuits if the situation of trunk circuit usage needs to be provided. In the actual operations, configure one office direction from the local office to the peer office. Configure different trunk groups for different SPs of the local office. This happens when two local networks are connected to one TMSC.

z
If an office acts as both a local office and a gateway office, and has two MSC numbers and two MGWs, configure two trunk groups mapping to different CIC segments so that the two shared local office directions can be distinguished. For the peer office, the local office has only one trunk group.
For broadband trunk office directions such as BICC and SIP, the office direction table is used to obtain the index.
Note: You do not need to change the original way of distinguishing between traffic statistics units according to office directions, trunk groups, or location area cells. Using the index to distinguish between the units is not needed. To adapt to the external interfaces of the M2000, ensure that the multi-area statistics index can be displayed when you run related LST commands, or such data as MSC numbers and call source codes that are indirectly related to the multi-area statistics index can be obtained.
3.11.3 Traffic statistics Units

In an MA network, the following units can be measured:
z z z z z z z z z z z z z z z z z z z z
Count of VLR subscribers MS-originated traffic/UE-originated traffic Intra-office traffic MS-originated outgoing traffic/UE-originated outgoing traffic Incoming traffic/Outgoing traffic MS-terminated incoming traffic/UE-terminated incoming traffic Transit traffic MS-terminated traffic/UE-terminated traffic Office direction incoming traffic/Office direction outgoing traffic Trunk group incoming traffic/Trunk group outgoing traffic Destination traffic distribution Location update Authentication TMSI reallocation Ciphering mode setting GSM cell handover Paging GSM assignment WCDMA RNC handover WCDMA assignment

z z z z z
MSC handover Short message service Bearer services Location service Mobile-originated location service/Mobile-terminated location service/NI_LR location Multimedia service Location area traffic distribution Cell traffic distribution Supplementary service traffic
z z z z
Chapter 4 Data Configuration

This chapter describes data configuration related to MA network. It includes:
z z z z z z z z
Scheme of Data Configuration Planning Data Configuration Setting Related Software Parameters Configuring Basic Information in Local Office Configuring Signaling Data Configuring Bearer Data Between MGWs Configuring Service Data Data Configuration Examples
4.1 Scheme of Data Configuration

For the MSOFTX3000 to hold multiple virtual MSC servers, you need to configure data supporting the MA network in the local office table. During data configuration, you need to configure virtual MSC/VLR numbers and their call source area codes. Also, you need to assign a multi-area statistics index to a virtual MSC server for the purpose of traffic statistics according to MSC number. The data configuration scheme of an MA network is shown as follows: 1) 2) 3) 4) 5) Configure data to support an MA network in the local office table and SPCs mapping to virtual MSC Servers. Configure virtual MSC numbers, VLR numbers, SPCs and virtual MSC server indexes in the mobile local office table. Configure statistics indexes for virtual MSC servers in an MA network. Configure area statistics indexes for MSC/VLR numbers configured in the LAI information table. Configure MSC numbers in the roaming subscriber table to identify roaming relationship between subscribers in different virtual MSC servers for all types of roaming services. 6) Configure mapping relationship between MSC numbers and call resources in the call resource table for services such as incoming trunk call bill based on area, and IN call. Configure area codes in the call source table for the PSTN incoming trunk call number to be unified into that in the national format. 7) Configure multi-area statistics indexes in the office direction table, the BSC table, LAI information table and the RNC table for identifying their relationships with an MA network.
8)
Configure MSC numbers in the RNC table for internal handover inside the same virtual MSC server in an MA network when handover between RNCs occurs in the 3G network.
9)
Add configuration for signaling networking and voice channel networking related to an MA network.
4.2 Planning Data Configuration

4.2.1 Deployment Recommendations
Recommendation Areas are close to each other geographically. Areas are close to each other in respect of economy. The total number of subscribers supported by an MA network is suitable. The number of districts in an MA network is suitable. Explanation It eases transmission between MGWs and saves transmission resources. It improves the traffic between areas. Traffic between offices is changed into that within an office. Form one MA network for areas where there are 600,000 to 1,600,000 subscribers at the mid or late stage of network development. Do not include more than three districts in one MA network. Otherwise, the topology of network elements in the network is too complex, and does not favor network building or maintenance.
4.2.2 Locating Principles of Network Elements

I. Locating principles of MSC server:
In general, the MSC server is located in a province-level city or the center of an area. It can support 600 thousand to 1.2 million subscribers. In the case of 600 thousand to 800 thousand subscribers, it is suggested to adopt the 1+1 mutual assistant backup mode to ensure reliability; in the case of 800 thousand to 1.2 million subscribers, it is suggested to adopt the N+1 disaster tolerance backup mode to ensure reliability.
II. Locating Principles of MGW

In general, the MGW is located in a city with medium-sized population. It is better to locate it in the same office with the GW in the PSTN or MSOFTX3000. The MGW is located in an area with 50,000 to 1,000,000 subscribers.
4.2.3 Principles of Data Planning

Data planning involves multi-area statistics index, call source data, trunk data, call barring data and data table. See Table 4-1.
Table 4-1 Principles of data planning No. 1 Data type Multi-area statistics index data Command Use ADD MASI to add a multi-area statistic index. Requirement One virtual MSC server maps to one multi-area statistics index. One virtual MSC server maps to one route selection code and failure source code. If there is no nearby access data, one virtual MSC server maps to one call source code. Use ADD CALLSRC to set a call source code including a route selection code and a failure source code. If there is nearby access data, on the access side of each virtual MSC server are assigned different call sources according to a location area and on the trunk side was assigned one call source code. If a virtual MSC server is used as a gateway office, it is assigned different call source codes according to the conditions by different fixed-line carriers. To improve maintainability, It is suggested to do the following: Each virtual MSC server is assigned a segment of office direction numbers. The common office direction, such as toll transit office direction, of multiple virtual MSC servers is assigned a segment of office direction numbers separately.
Call source data
Office data
Use ADD OFC to add an office direction number.
No.
Data type
Command
Requirement Call barring data is mainly configured on a gateway office. When a fixed-line subscriber makes a call to a toll mobile subscriber, the call is barred if 0 is not added before the callee number. When a fixed-line subscriber makes a call to a toll mobile subscriber, the call is not barred if 0 is added before the callee number.
Call barring data
Use ADD PFXPRO or ADD CALLPRICHK to set call barring data.
Note: When there are multiple MA networks interacting with one another, a lot of call barring data occurs. So the data needs to be reflected in multiple tables. When a local fixed-line subscriber inside the multiple MA networks makes a call to a mobile subscriber outside the MA networks, the barring data of the call is configured in the outgoing call authority table. Other barring data is configured in the called number special processing table and the incoming number pre-processing table.
To improve maintainability, It is suggested to do the following: Each virtual MSC server is assigned a segment of office direction numbers. When the scheme of a single SPC mapping to multiple MSC numbers is adopted, you need to assign a segment of trunk group numbers uniquely to the trunk group with the common office direction number. For the number of trunk circuits barred, see section 1.3.4 IV. Limitation of the Number of Trunk Circuits.
Narrowband trunk group data
Use ADD N7TG, ADD PRATG or ADD CASTG to add a trunk group number.
Number of trunk circuits
No.
Data type Data table capacity
Command
Requirement For the capacity of data tables capacity, see section 1.3.4 III. Limitation of the Capacity of Data Tables.
4.3 Setting Related Software Parameters

In this section, use MOD MSFP to set software parameters related to an MA network.
Caution Wrong modification of software parameters may seriously affect the system. If you need to modify software parameters, contact a technical support engineer of Huawei.
4.3.1 Setting Location Update Mode

P140 bit 14 controls the location update mode.
z
=0: When the MA feature or the dual-homing feature is enabled in a network, start the location update to the HLR if a subscriber starts the location update between different MSCs. It is the default value.
=1: Not start the location update to the HLR.
4.3.2 Setting Duration of Protecting Location Update Data by Timer

P140 bits 1213 control the duration of protecting location update data by the timer.
z
=0: Sets the timer value to 5 seconds by default, indicating that the value of the timer ignoring the CancelLocation message is 5 seconds in an MA network. =1: Sets the timer value to 3 seconds. =2: Sets the timer value to 2 seconds. =3: Sets the timer value to 1 second.
z z z
4.3.3 Setting Parameter of Optimizing Paging in Entire Multi-area Network

P164 bit 14 controls whether to optimize paging in the entire MA network.
z z
=0: Yes. =1: No (by default).
You need to set it to 0 to optimize paging on the entire MA network, that is, to page in the location area mapping to the MSC/VLR where the callee is located.
4.3.4 Setting Monitoring Parameter in Multi-area Network

P179 bits 1415 control the monitoring mode in an MA network. Bit 14: Controls whether to fill the DN set of the monitored call in the DFUANA table according to the DN set of the monitored call or the ID in the monitor center. The default value is 1.
z
=0: Fills the DN set of the monitored call in the DFUANA table with the field of the DN set of the monitored call. =1: Fills the DN set of the monitored call in the DFUANA table with the ID in the monitor center.
Bit 15: Controls whether to transform the monitored number into a local number or national number. The default value is 1.
z
=0: Transforms the monitored number into a national number. For example, if the monitored number is a PSTN number, it is transformed in the format of a national number, National code prefix + area code + subscriber number, such as 07556661234. Set the monitoring access code in the DFUANA table in the number format above.
=1: Transforms the monitored number into a local number. For example, if the monitored number is a PSTN number and the area code of the monitored number is the same as that of the monitoring center, the monitored number is transformed in the format of a subscriber number, such as 6661234. In this case, you need to set the monitoring access code to 6661234 in the DFUANA table. If the monitored number is a PSTN number and the area code of the monitored number is not the same as that of the monitoring center, it is kept in the format, National code prefix + area code + subscriber number, such as 07556661234. In this case, you need to set the monitoring access code to 07556661234.
4.3.5 Setting Local Number Length

P76 controls the length of a local number. In an MA network with different areas, you need to set the maximum length of a local number if the length of a local number differs in areas. For example, if the number length is 7 digits in one area and the number length is 8 digits in another area, you need to set the local number length to 8 digits in the entire MA network.
4.4 Configuring Basic Information in Local Office

To set basic information in the local office, follow the steps shown as in Table 4-2. Table 4-2 Steps of setting basic information Whether special configuration is needed in multi-area network Yes Yes Yes Yes
Step
Command
1 2 3 4
Use SET OFI/ADD OFI to set local office information. Use SET INOFFMSC/ADD INOFFMSC to set mobile local office information. Use ADD MASI to add a multi-area statistic index. Use ADD MARLATION to add multi-area relation between MSC numbers in an MA network.
For an MA network, you need special commands whose description is shown as follows:
z
SET OFI
It is used to configure the MSOFTX3000 for supporting MA networking. MULTAREAFLG: It is Multi-area flag. You need to set MULTAREAFLG to YES for an MA network.
z
SET INOFFMSC
It is used to set basic data, such as national toll prefix, international toll prefix and LAI, of the mobile local office.
Caution
z
Multi-area network index 0 is generated by default when you use SET INOFFMSC to set data for a mobile local office. Multi-area network index 0 maps to record 0 of the local office table and record 0 of the mobile local office table.
In the case of multiple SPCs, you need to set national toll prefix and international toll prefix defined in ADD INOFFMSC.

z
ADD MASI
It is used to set such parameters as multi-area statistics index, MSC number, VLR number and national area code for an MA network. The default record 0 maps to record 0 in the local office table.
z
ADD MARLATION
It specifies a handover mode between two virtual MSC servers in an area network. You can set the handover mode into intra-office handover or inter-office handover according to actual conditions or customers requirements.
4.5 Configuring Signaling Data

Signaling data configured on the MA network is basically the same as that configured on other networks. The differences lie in such aspects:
z z
HLR GT routing is achieved by DSP addressing. Each signaling point maps to a bottom link through the transfer functions of STP on the MTP layer. Whether special configuration is needed in multi-area network Yes Yes Yes Yes Yes
Step
Command
1 2 3 4 5
Use ADD N7DSP to add an MTP DSP. Use ADD N7RT to add an MTP route. Use ADD SCCPDSP to add an SCCP DSP. Use ADD SCCPSSN to add SCCP sub-system number. Use ADD SCCPSSN to add SCCP global title.
ADD SCCPGT
When configuring HLR GT to the local network, you need to adopt the DPC + original GT mode for addressing. The DPC is that of the local HLR.
4.6 Configuring Bearer Data Between MGWs
Note: You do not need to configure a bearer network if there is no bearer network between MGWs.
You need to configure bearer data according to the types of bearer networks between MGWs of local networks.
4.6.1 TDM Bearer Network Between MGWs in Area Network

Whether special configuration is needed in multi-area network No
Step
Command
Use ADD INTTDM to add an internal TDM circuit between two gateways, which are under the control of the same MSC server and whose bearer is TDM.
4.6.2 IP Bearer Network Between MGWs in Area Network

Step
Command
Use ADD MGWCONN to add connection between MGWs in the local office.
4.7 Configuring Service Data

4.7.1 Configuring LAI and Office Direction Trunk
Whether special configuration is needed in multi-area network
Step
Command
[1
Use ADD LAIGCI/MOD LAIGCI to add/modify 2G LAI or GCI information. Use ADD LAISAI/MOD LAISAI to add/modify 3G LAI or SAI information. For narrowband signaling:
z
Yes
Use ADD N7TG/MOD N7TG to add/modify an SS7 trunk group. Use ADD PRATG/MOD PRATG to add/modify a PRA trunk group. Use ADD CASTG/MOD CASTG to add/modify a CAS trunk group.
Yes
Step
Command
Whether special configuration is needed in multi-area network Yes
For broadband signaling: 3

z
Use ADD OFC/MOD OFC to add/modify an office direction.
ADD LAIGCI / MOD LAIGCI
Add a multi-area statistics index in the LAI information table. It is used to identify an MA network where a mobile subscriber call is originated or terminated.
4.7.2 Configuring Mobile Service Management

Step
Command
Use ADD ROAMUSRT to configure data to obtain a roaming type according to MSC number and an IMSI number for subscribers in different area networks.
4.7.3 Configuring Service Data Handover

Step
Command
Use ADD MARLATION to add multi-area relation, inter-office handover or intra-office handover between MSCs in an MA network. The default is intra-office handover. 1
Note: In the case of an MA network with dual-homing features, multiple virtual MSC servers under the same server index are processed as intra-office handover; multiple virtual MSC servers under different server indexes are processed as inter-office handover by default.
Yes
Step
Command
Use MOD RNC to modify the MSC number mapping to RNC to update the MSC number in the bill after 3G handover.
Yes
Note: No such configuration is needed in 2G network.

3 Use ADD CLDPREANA to add a special prefix for the destination handover numbers originated in different call sources. Use ADD HDOVPROC to remove the special prefix for a called number to be routed out. Yes
Yes
Handover data falls into three categories:
I. Intra-office Handover Data in a Virtual MSC Server

Intra-office handover refers to the handover between locations in a virtual MSC Server. Data configuration in an MA network is the same as that in other networks.
II. Handover Data Between Virtual MSC Servers

Because local VLR location area cells/service areas are configured in the location area of each virtual MSC server node, you do not need to configure adjacent cells for handover between virtual MSC servers. Currently, this handover can either be intra-office handover or inter-office handover. You need to set handover relation in an MA network separately.
z
For 3G network handover, you need to configure MSC numbers in the RNC table as well as handover relation in an MA network for the purpose of intra-office handover.
In the case of inter-office handover, the processing of number handover is the same as that of roaming numbers. That is, the system adds in the incoming number pre-processing table a prefix to the number for routing. After the routing is selected, the system removes the prefix to route the number out.
You do not need special configuration for GT signaling data as long as the GTs of two MSC servers map to the local office.
III. Handover Data Between the Local Office and Another Office
All data configuration is the same as previously.
4.7.4 Configuring Roaming Number Data

Whether special configuration is needed in multi-area network No Yes Yes
Step
Command
1 2 3
Use ADD VLRCFG/MOD VLRCFG to add the MSRN allocation mode. Use ADD MHSUFFIX to add an MSRN or HON suffix. Use ADD MHMSCCFG to add mapping between MSC and MSRN or HON.
See the following for the configuration of roaming number data: In an MA network, you need to assign a handover number and roaming number according to MSC number or switched-to-SMC number.
4.7.5 Configuring Number Analysis and Route Selection

Number analysis and route selection include:
z z z z z
Configuring Route Analysis Configuring Number Analysis Configuring Call Barring Data Configuring Forwarding Data Configuration Rules
I. Configuring Route Analysis

Whether special configuration is needed in multi-area network Yes No No No
Step
Command
1 2 3 4
Use ADD CALLSRC to add a call source code. Use ADD RTANA to add route analysis. Use ADD N7TG/MOD N7TG to add or modify an SS7 trunk group (ISUP/TUP trunk group). Use MOD OFC to modify an office direction.
In an MA network, you need special commands whose description is shown as follows:

z
ADD CALLSRC
It is used to set call parameters to identify different areas. These parameters include DN set, route selection source code (It is used for different route policies. In general, one route selection source code is selected for one area network), local code and local MSC number. In general, the call sources of different areas mapping to an MSC server are allocated on different call source area segments. At the same time, call sources in one MA network are divided based on the mobile network side and trunk side. When configuring nearby access data on the mobile network side (for example, the number 110 needs to access different numbers nearby), you need to allocate different call sources according to different location areas.
II. Configuring Number Analysis

Whether special configuration is needed in multi-area network Yes No number No No No
Step
Command
1 2 3 4 6
Use ADD CNACLD to add a call prefix in the caller number analysis table. Use ADD DNC to add number change. Use ADD CLDPREANA pre-analysis. to add called
Use ADD INNUMPREPRO to add incoming number pre-processing. Use ADD OUTNUMPREPRO to add outgoing number pre-processing. Use ADD HDOVPROC to add handover number processing, that is, to remove the special prefix of the called number.
No
ADD CLDPREANA
It is used to remove the country code of a fixed-line subscriber number and then add the national prefix when you want to set forwarding data; It is also used to set the mode of unifying the numbers sent back through the MAP or CAP interface, that is, remove the national code of a national mobile subscriber or remove the country code of a fixed-line subscriber and then add the national prefix.
Caution The pre-processing data forwarded through the MAP or CAP interface is processed in the called pre-processing mode.

z
ADD INNUMPREPRO
It is used to set the pre-processing mode of the called number coming from the mobile network side or the trunk side.
Caution It is suggested to set a related pre-processing mode for a call from the mobile network side or trunk side according to incoming trunk processing.
III. Configuring Call Barring Data

Whether special configurati on is needed in multi-area network
Step
Command
Note
The rules of configuring call prefix processing and call authority check are shown as follows: The barring data of a call made from local fixed-line subscriber to a subscriber from other mobile networks is configured in the outgoing call authority table. Other call barring data is configured as previously, that is, configured in called number special processing table or incoming number pre-processing table. 2 Use ADD CALLPRICHK to add call authority check. No -
Use ADD PFXPRO to add call prefix processing.
No
IV. Configuring Forwarding Data

Whether special configuration is needed in multi-area network Yes
Step
Command
Use ADD CLDPREANA to add called number pre-analysis.
ADD CLDPREANA
It is used to remove the country code prefix of the called number to identify the area where the called number is located. But, a fixed-line subscriber number needs to be added with a national prefix so that the analysis of the number with the area code can be done.
V. Configuration Rules
Caution This section describes an upgrade scheme, of transitional configuration, for offices with data. If this scheme is used in an upgrade, data configuration in all area networks may not be the same. This makes subsequent maintenance inconvenient. So it is not suggested.
The rules of service configuration such as number analysis and routing in an MA network are shown as follows:
z
The aim of route analysis configuration is to select different routes according to different route selection source codes for a call from a subscriber in an MA network when one number maps to one route selection code. So, you need to allocate different call sources and route selection source codes for PSTN trunks in an MA network. For different routes in one office direction, you need to map multiple route selection source codes to one outgoing route in route analysis data configuration.
z z
Number analysis configuration in an MA network is the same as in other networks. The aim of call barring data configuration is to bar a call from a PSTN subscriber in a certain area in an MA network to a mobile subscriber. For example, when you make a call to a remote mobile subscriber, you need to add 0 before the subscriber number; when a local fixed-line subscriber makes a call to local mobile subscriber, the caller need not to add 0 before the callee number.

z
When the forwarding data sent back from the HLR is in the international format, such as 8641487654321, it is invalid to use the default and previous processing of forwarding number. In this case, you need to use the called number pre-processing to change the number to 041487654321 by removing the prefix 86 and then adding the prefix 0. Then subsequent number analysis processing is done. For the format, such as that of a mobile subscriber number, 8613xxxxxxxx, you need to use the called number pre-processing to remove the prefix 86 and then do the number analysis processing. After the number analysis, the number is changed into a fixed-line subscriber number with an area code.
If a call or handover between areas in an MA network needs to be routed back to the local office through a transit office or gateway office, you need to configure special data. For an MSRN number or a handover number, you need to configure data in the incoming number pre-processing table to obtain from the HLR the roaming number of the virtual office or from the handover number, such as 8613911112222, of the other virtual office sent back through the MAP interface. The system needs to remove the prefix 86 and then add a special prefix before number analysis for the outgoing call is done. To save the other office from modifying data in the special number analysis, the system also needs to remove the added prefix after the number analysis before the number is routed out. For a subscriber number, such as the number of a subscriber in a mobile network belonging to another carrier or the number of a subscriber of a fixed-line network belonging to another carrier, you need to configure different route analysis data according to the route selection source codes mapping to different call sources. The different route analysis data are routed out through different gateway offices.
For the upgrade of offices with data, you need to configure data in the mode of a network other than an MA network. For example, a fixed-line subscriber number is without an area code for number analysis. If you upgrade the number data analysis in changing a network into an MA network, this system is seriously affected. In this case, you can adopt a transitional mode. In this mode, the system does called number pre-processing according to call source. That is, the system removes the country code of the number of a fixed-line subscriber that has been upgraded to the MA network and then adds the national code. In the subsequent number analysis, the upgraded subscriber number is changed into a fixed-line subscriber number with an area code; the number of a subscriber who has not been upgraded to the MA network still keeps the default unifying mode. In the number analysis, the upgraded subscriber number is changed into a local fixed-line subscriber number without an area code.
4.8 Data Configuration Examples

4.8.1 Implementation
Figure 4-1 shows a model of MA networking.
MSOFTX3000 Virtual MSCA 8613900414 MASI=0 area=0414 Virtual MSCB 8613900415 MASI=1 area=0415
MGW8
MGW9
PSTN
PSTN
BSC Area A
RNC
RNC Area B
BSC
Figure 4-1 MA network model A mobile carrier wants to set up an MA network covering area A and B. As shown in Figure 4-1, the MOFTX3000 is put in the hub city with an MGW distributed in area A and B respectively. The model adopts the R4 structure. Data configuration is to set different call sources according to different sources. In actual networking, data such as call source, office direction, trunk group and route number is configured according to different areas. Table 4-3 shows the basic configuration of an MA networking. Table 4-3 Basic configuration of an MA network Basic information Local MSC number Local SPC Toll area code Mobile subscriber Area A 861390414 BB0066, AA 0414 13904141234(IMSI:46000 0414001234) 861390415 AA0066, AA 0415 13904151234(IMSI:46000041 5001234) Area B
Basic information Local roaming or handover number in MA network The number of a subscriber of a mobile network belonging to another carrier (the number is inside MA network)
Area A 8613900414xxx
Area B 8613900415xxx
1300414xxxx
1300415xxxx
Call source: 0 BSC/RNC GCI: 4600000000001 Office direction number: 0 HLR numbers in all area networks Fixed-line subscriber number 861391414 Call source:2 Office direction number: 2 Route number: 2 Fixed-line subscriber Mobile roaming number outside MA network Fixed-line toll number outside MA network The number of a subscriber of a mobile network belonging to another carrier (the number is outside MA network)
Call source:10 GCI: 4601700240001 Office direction number: 10 861391415 Call source:15 Office direction number: 15 Route number: 15
876543219 (Both area A and B have this number or the number segment prefix. Here, this number or the number segment prefix is taken for an example.) 8613900413xxx
0756xxxxxxx
1300756xxxx
Local network roaming number: 0-9; fixed-line number: 1019 Number analysis route code The number of a subscriber in a mobile network belonging to another carrier: 2029; international toll network number: 3039
Basic information
Area A National code: 86
Area B
Local configuration of V9 MSC
Local area: 414 International prefix: 00 National prefix: 0
Note: Signaling point code (SPC)
4.8.2 Script
Note: This section describes only data configuration related to MA network features in constructing an MA network. It does not apply to complete configuration for new offices.
I. Setting the Offline Mode

//Set offline mode.
LOF:;
II. Configuring Basic Information Data in the Local Office

//Set local office information. Set Multi-area flag to YES.
SET OFI: MULTAREAFLG=YES;
//Add a local office signaling point code.

ADD OFI: IDX=1, NATC="AA0066", NATBC="AA";
//Add local mobile office information.

SET INOFFMSC: MSCN=K'8613900414, VLRN=K'8613900414, MCC=K'460, MNC=K'00, INNATIONPFX=K'00, NATIONPFX=K'0; ADD INOFFMSC: ID=1, MSCN=K'8613900415, VLRN=K'8613900415, MCC=K'460, MNC=K'00, INNATIONPFX=K'00, NATIONPFX=K'0;
Note: You need to set local SP information for networking with multiple signaling points.
//Remove a multi-area statistics index. Add two MSC/VLR numbers and related area codes (Multi-area statistics index 0 maps to the hub city by default).
RMV MASI: MSAI=0;
//Add a multi-area statistics index. Set Multi-area statistics index to 0, standing for the virtual hub city (It is required).
MOD MASI: MSAI=0, AN="0", MSCN=K'8613900414, VLRN=K'8613900414, AC=K'414;
//Add a multi-area network index. Set Multi-area statistics index to 1, standing for another peripheral city.
ADD MASI: MSAI=1, AN="1", MSCN=K'8613900415, VLRN=K'8613900415, AC=K'415;
III. Configuring Signaling Data

//Add an SCCP global title for a virtual MSC server.
ADD SCCPGT: GTX=1, GTNAME="local-1", ADDR=K'8613900414, RESULTT=LSPC2, SPC="aa0055"; ADD SCCPGT: GTX=8, GTNAME="local-2", ADDR=K'8613900415, RESULTT=LSPC2,
SPC="aa0066";
There are two kinds of external signaling route configuration modes, signaling point mutual assistant mode and signaling point direct connection mode, to meet carriers requirements.
z
Signaling point mutual assistant mode
Caution It is not suggested to adopt the signaling point mutual assistant mode.
//For the signaling point mutual assistant mode, you need to set the mutual assistant relationship between the other signaling points and points with MTP links on the bottom layer. For multiple signaling points in the local office, you need to configure all data, such as DSP, SSN and GT, on the SCCP layer of the local HLR in the MA network.

MOD OFI: IDX=1, PA1= NAT, PAC1="BB0066";
Signaling point direct connection mode
//For multiple signaling points, if each signaling point uses separate links to connect to external signaling points, you need to adopt the DPC addressing mode for destination GT data, and also you need to configure each bottom links from signaling point to HLR or STP. For multiple signaling points in a local office, you need to configure all data, such as DSP, SSN and GT on the SCCP layer of the local HLR in the MA network, as well as route data on the MTP link layer mapping to HLR signaling, including the local HLR inside the MA network, and the HLR in another area network (Route data is transferred through STP).
Caution When adopting this scheme, you need to configure DSP, SSN and GT data on the SCCP layer of another area network for peripheral HLRs.
//Add an MTP DSP.

ADD N7DSP: DPX=100, DPC="cc0088", OPC="bb0066", DPNAME="DDHLR", ADJF=FALSE; ADD N7DSP: DPX=101, DPC="dd0088", OPC="bb0066", DPNAME="DD-BXHLR",
ADJF=FALSE; ADD N7DSP: DPX=200, DPC="cc0088", OPC="aa0066", DPNAME="BX-DDHLR",
ADJF=FALSE; ADD N7DSP: DPX=201, DPC="dd0088", OPC="aa0066", DPNAME="BXHLR", ADJF=FALSE;
//Add an MTP destination signaling point. The destination signaling point is that of STP.
ADD N7DSP: DPX=300, DPC="ee0088", OPC="bb0066", DPNAME="DD-L1", ADJF=TRUE; ADD N7DSP: DPX=301, DPC="ee0088", OPC="aa0066", DPNAME="BX-L1", ADJF=TRUE;
//Configure link data between the signaling points of virtual MSC servers and linksets between virtual MSC servers and peer ends.
Note: The configuration is the same as that of ordinary links. No examples are taken here.
//Add an MTP route. Suppose to set Linkset index to area A to 100, Linkset index to the HLR of area B to 200, Linkset index to STP linkset 300 and 301.
ADD N7RT: LSX=100, DPX=100, RTNAME="DDHLR"; ADD N7RT: LSX=300, DPX=100, RTNAME="L1-BXHLR"; ADD N7RT: LSX=200, DPX=200, RTNAME="BXHLR"; ADD N7RT: LSX=301, DPX=200, RTNAME="L1-DDHLR";
//Add an SCCP destination signaling point.

ADD SCCPDSP: DPX=100, NI=NAT, DPC="CC0088", OPC="bb0066", DPNAME="DDHLR"; SHAREFLAG=NONE; ADD SCCPDSP: DPX=101, NI=NAT, DPC="DD0088", OPC="bb0066", DPNAME="DDL1-BXHLR"; SHAREFLAG=NONE; ADD SCCPDSP: DPX=200, NI=NAT, DPC="CC0088", OPC="aa0066", DPNAME="BXL1-DDHLR"; SHAREFLAG=NONE; ADD SCCPDSP: DPX=201, NI=NAT, DPC="DD0088", OPC="aa0066", DPNAME="BXHLR"; SHAREFLAG=NONE;
//Add a SCCP subsystem (HLR).

ADD SCCPSSN: SSNX=100, NI=NAT, SSN=HLR, SPC="CC0088", OPC="bb0066", SSNNAME="DDHLR"; ADD SCCPSSN: SSNX=101, NI=NAT, SSN=HLR, SPC="CC0088", OPC="aa0066",
SSNNAME="BX-DDHLR"; ADD SCCPSSN: SSNX=200, NI=NAT, SSN=HLR, SPC="DD0088", OPC="bb0066",
SSNNAME="DD-BXHLR"; ADD SCCPSSN: SSNX=201, NI=NAT, SSN=HLR, SPC="DD0088", OPC="aa0066",
SSNNAME="DDHLR";
//Configure SCCP global titles. The DPC is used for addressing.

ADD SCCPGT: GTX=100, GTNAME="DDHLR", ADDR=K'861391414, RESULTT=LSPC2, SPC="CC0088"; ADD SCCPGT: GTX=200, GTNAME="BXHLR", ADDR=K'861391415, RESULTT=LSPC2,
SPC="DD0088";
IV. Configuring Number Analysis Data

//Add different call source codes, route selection code, area codes and MSC codes for different area networks in an MA network.
ADD CALLSRC: CSC=0, CSCNAME="Area-a",AC=K'414, MSCN=K'8613900414, RSSC=0, FSC=0; ADD CALLSRC: CSC=2, CSCNAME="Area-a-pstn", AC=K'414, MSCN=K'8613900414,
RSSC=2, FSC=0;
ADD CALLSRC: CSC=10, CSCNAME="Area-b", AC=K'415, MSCN=K'8613900415, RSSC=10, FSC=0; ADD CALLSRC: CSC=15, CSCNAME="Area-b-pstn", RSSC=15, FSC=0, AC=K'415,
MSCN=K'8613900415;
V. Configuring Mobile Service Management Data

//Add the roaming subscriber type.
ADD ROAMUSRT: IMSIPFX=K'460000414, MSCN=K'8613900414; ADD ROAMUSRT: IMSIPFX=K'46000, MSCN=K'8613900415, MSTP=NATIONMS; ADD ROAMUSRT: IMSIPFX=K'460000415, MSCN=K'8613900415; ADD ROAMUSRT: IMSIPFX=K'46000, MSCN=K'8613900414, MSTP=NATIONMS;
VI. Configuring Roaming Number Data

//Add MSRN or HON allocation mode
MOD VLRCFG: MSRNAM=MSC, HONAM=MSC;
//Add the prefix and suffix of an MSRN or HON.

ADD MHPREFIX: ID=1, HPFX=K'8613900415; ADD MHSUFFIX: ID=2, PFXIDX=1, SFXS="0", SFXE="499", MSRNT=MSRN; ADD MHSUFFIX: ID=3, PFXIDX=1, SFXS="500", SFXE="999", MSRNT=HON; ADD MHPREFIX: ID=0, HPFX=K'8613900414; ADD MHSUFFIX: ID=4, PFXIDX=0, SFXS="0", SFXE="499", MSRNT=MSRN; ADD MHSUFFIX: ID=5, PFXIDX=0, SFXS="500", SFXE="999", MSRNT=HON;
//Add mapping between MSC and MSRN or HON.

ADD MHMSCCFG: MSCN=K'8613900414, PRESFX=4; ADD MHMSCCFG: MSCN=K'8613900414, PRESFX=5; ADD MHMSCCFG: MSCN=K'8613900415, PRESFX=2; ADD MHMSCCFG: MSCN=K'8613900415, PRESFX=3;
VII. Configuring Service Data

//Add Multi-area relation. Set RELATION between two virtual MSC servers to INTER.
ADD MARLATION: MSCN1="8613900414", MSCN2="8613900415", RELATION=INTER;
//Modify MSC number mapping to RNC to update MSC number in the bill after 3G handover.
Note: The configuration is not needed in 2G network.
MOD RNC: RNCID=6, MSCNO="8613900414"; MOD RNC: RNCID=80, MSAREAINDEX=1, MSCNO="8613900415";
VIII. Configuring Route Analysis Data

//Add route analysis.
ADD RTANA: RSC=6, RSSC=10, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=6, ISUP=NOCHG; ADD RTANA: RSC=6, RSSC=2, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=6, ISUP=NOCHG; ADD RTANA: RSC=6, RSSC=15, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=6, ISUP=NOCHG; ADD RTANA: RSC=16, RSSC=10, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=16,
ISUP=NOCHG; ADD RTANA: RSC=16, RSSC=2, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=16,
ISUP=NOCHG; ADD RTANA: RSC=16, RSSC=15, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=16,
ISUP=NOCHG;
//Modify an SS7 trunk group call source code. Set Trunk group to 2, standing for the PSTN of area A; Trunk group to 15, standing for the PSTN of area B.
MOD N7TG: TG=2, CSC=2; MOD N7TG: TG=15, CSC=15;
IX. Configuring LAI and Office Direction Trunk Data

//Add 2G LAI or GCI information. Home global cell numbers 460170024 and 4601700240001 to the number 8613900415 of the MSC.
Note:
z
Note that you need to modify the multi-area network index and the call source code. Their default values are 0. For 3G networking, you need to set LAISAI in 3G location area in the same mode.
ADD LAIGCI: GCI="460170024", LAIGCINAME="Area-b-bsc24", MSCN="8613900415", VLRN="8613900415", MSAREAID=1; LAICAT=LAI, LAIT=HVLR, BSCDPC1="0024", CSC=10,
ADD LAIGCI: GCI="4601700240001", LAIGCINAME="Area-b-bsc24", MSCN="8613900415", VLRN="8613900415", LAICAT=GCI, LAIT=HVLR, BSCDPC1="0024", CSC=10, MSAREAID=1;
//Modify an office direction. Set Office direction to 15 and Multi-area statistics index to 1. For all incoming trunks, the multi-area statistics index mapping to the PSTN in the MA network is needed.
MOD OFC: OFFICEDIR=15, MSAREA=1;
X. Configuring Bearer Data Between MGWs

//Add link connection between the MGW8 and MGW 9. If there is no bearer, you do not need the configuration. //If the bearer is TDM, you need to set the data as follows.
ADD INTTDM: E1NO=2, MGWIDX1=8, TID1="40000100", MGWIDX2=9, TID2="40000000";
//If the bearer is IP, you need to set the data as follows.
ADD MGWCONN: MGWIDX1=8, MGWIDX2=9;
//Service data configuration mainly depends on whether calls or handover is processed in the inter-office mode or intra-office mode in MA network; but it varies with different networking.
XI. Configuring Call Service Data (Bearer Between MGWs)

//You can configure call service data with reference to the following, but need minor adjustments according to actual requirements. //If there is bearer connection between MGWs in an MA network, the calls in the MA network are processed in the intra-office call mode. Set the data as follows:
z
Mobile subscriber calling local mobile subscriber

z
Called roaming number terminated in an MA network Three call processes are included: call in an area network, call between area networks, and call from a subscriber outside the MA network to a mobile subscriber in the MA network.
ADD CNACLD: PFX=K'13900414, CSA=MLCO, RSC=65535, MINL=11, MAXL=11, ICLDTYPE=MSRH; ADD CNACLD: PFX=K'13900415, CSA=MLCT, RSC=65535, MINL=11, MAXL=11, ICLDTYPE=MSRH;

z
For a called roaming number not terminated in the MA network, the call needs to be routed to the local toll office of the network when the call is terminated in a network.
ADD RTANA: RSC=3, RSSC=0, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=2, ISUP=NOCHG; ADD RTANA: RSC=3, RSSC=10, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=15, ISUP=NOCHG; ADD CNACLD: PFX=K'13900413, CSA=MLCO, RSC=3, MINL=11, MAXL=11, ICLDTYPE=MSRH;
Mobile subscriber calling local fixed-line subscriber or a subscriber in a mobile network belonging to another carrier When a mobile subscriber calls a local fixed-line subscriber or a subscriber in a mobile network belonging to another carrier, the mobile subscriber number carries no area code. The mobile subscriber is routed to the correct PSTN according to the call source configured. In general, if the call is forwarded, the system unifies the forwarded-to number in the called number pre-analysis table, that is, to add an area code with a national number prefix before the forwarded-to number. To keep consistency with the area code that is added to the forwarded-to number, the system adds an area code in the same form before the local fixed-line number in the called number pre-analysis table. This is convenient for the system to do the called number analysis uniformly.
ADD RTANA: RSC=20, RSSC=0, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=2, ISUP=NOCHG; ADD RTANA: RSC=20, RSSC=10, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=15, ISUP=NOCHG;
ADD DNC: DCX=1, DCT=TYPE1, ND=K'0414, DAI=NDN; ADD DNC: DCX=2, DCT=TYPE1, ND=K'0415, DAI=NDN;
ADD CLDPREANA: CSC=0, CS=MUSER, PFX=K'87654321, MINCLDLEN=8, CDADDR=ALL, CRP=ALL, CLDNCX=1, PT=DONTPROC; ADD CLDPREANA: CSC=2, CS=MUSER, PFX=K'87654321, MINCLDLEN=8, CDADDR=ALL, CRP=ALL, CLDNCX=2, PT=DONTPROC;
ADD
CNACLD:
PFX=K'1300414,
CSA=MLCT,
RSC=20,
MINL=11,
MAXL=11,
ICLDTYPE=PS; ADD CNACLD: PFX=K'1300415, CSA=MLCT, RSC=20, MINL=11, MAXL=11,
ICLDTYPE=PS;

z
Mobile subscriber calling toll fixed-line subscriber or subscriber in a toll mobile network belonging to another carrier or local fixed-line subscribers with an area code When a mobile subscriber calls a toll fixed-line subscriber or a subscriber in a toll mobile network belonging to another carrier or a local fixed-line subscriber with an area code, the call is directed according to the call sources configured for the mobile subscriber and the trunk.
z
If the called number is the number of a fixed-line subscriber in area A, the call is routed out through internal bearer.
ADD RTANA: RSC=11, RSSC=0, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=2, ISUP=NOCHG; ADD RTANA: RSC=11, RSSC=1, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=2, ISUP=NOCHG; ADD CNACLD: PFX=K'0414, CSA=LCT, RSC=11, MINL=11, MAXL=11,
ICLDTYPE=PS;
If the called number is the number of a fixed-line subscriber in area B, the call is routed out through internal bearer.
ICLDTYPE=PS;
If the called number is the number of a fixed-line subscriber or a mobile subscriber outside the MA network, the call is routed to the toll office of the area network when the call is terminated in an area network.
ADD RTANA: RSC=13, RSSC=0, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=2, ISUP=NOCHG; ADD RTANA: RSC=13, RSSC=10, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=15, ISUP=NOCHG; ADD RTANA: RSC=21, RSSC=0, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=2, ISUP=NOCHG; ADD RTANA: RSC=21, RSSC=10, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=15, ISUP=NOCHG; ADD CNACLD: PFX=K'0413, CSA=LCT, RSC=13, MINL=11, MAXL=32,
ICLDTYPE=PS; ADD CNACLD: PFX=K'1300413, CSA=MNTT, RSC=21, MINL=11, MAXL=11, ICLDTYPE=PS;

z
If the call is an international toll call, the call is routed to the local toll office of the area network when the call is terminated in an area network.
ADD CNACLD: PFX=K'00, CSA=ITT, RSC=30, MINL=3, MAXL=32, ICLDTYPE=PS;
//Remove the area code of an outgoing call.

ADD DNC: DCX=5, DCT=TYPE6, DCP=0, DCL=4;
ADD OUTNUMPREPRO: CSC=65534, TG=2, P=0, PFX=K'0414, ODDX=5; ADD OUTNUMPREPRO: CSC=65534, TG=15, P=0, PFX=K'0415, ODDX=5;
Fixed-line subscriber calling mobile subscriber (The MOSFTX3000 needs to be configured when it functions as both a mobile gateway office and a fixed-line gateway) //The configuration of the number analysis data is similar to that of a mobile subscriber calling another mobile subscriber. Their difference is that the MSOFTX3000 needs to bar the call made by a local fixed-line subscriber to a mobile subscriber if the number 0 is not added before the called number, when the MSOFTX3000 functions as a gateway office. A fixed-line subscriber calls a local mobile subscriber directly. The number 0 needs to be added before the called number when a fixed-line subscriber calls a mobile subscriber. If the number 0 is not added, the system prompts the subscriber to add 0. In this case, data is configured to do the number authority check.
//A fixed-line subscriber in area A is not allowed to call a mobile subscriber in area B directly.
ADD CALLPRICHK: CSC=2, PFX=K'1390415, CPFX=K'0414, PT=INHIBITED, FCC= CV110;
//A fixed-line subscriber in area B is not allowed to call a mobile subscriber in area A directly.
//A fixed-line subscriber in area A is not allowed to call a mobile subscriber in other areas directly.
ADD PFXPRO: CSC=2, PFX=K'1390755, STF=NSDT, PT=FAILPROC, FCC=CV110;
XII. Configuring Call Forwarding Data

The forwarding consists of three cases: forwarding to a mobile subscriber, a fixed-line subscriber and forwarding to a local fixed-line subscriber. You need to configure called number pre-processing for the three cases. If the forwarding number is a mobile subscriber number, such as a number beginning with 8613, then 86 is removed; if the forwarding number is a fixed-line subscriber number, such as a number beginning with 86, 86 is removed and then 0 is added. There are two records.
ADD DNC: DCX=8, DCT=TYPE6, DCP=0, DCL=2; ADD DNC: DCX=9, DCT=TYPE13, DCP=0, DCL=2, ND=K'0; ADD CLDPREANA: CSC=65534, CS=MAP, PFX=K'86, MINCLDLEN=9, CDADDR=IDN, CRP=ALL, CLDNCX=9, PT=DONTPROC; ADD CLDPREANA: CSC=65534, CS=MAP, PFX=K'8613, MINCLDLEN=13, CDADDR=IDN, CRP=ALL, CLDNCX=8, NP=255, PT=DONTPROC;
XIII. Configuring Call Service Data (No Bearer Connection Between MGWs)
//If there is no bearer connection between MGWs in an MA network, the calls in the MA network are processed in the inter-office mode. That is, the call needed to be routed out to another virtual MSC through another office.
z
Mobile subscriber calling local mobile subscriber

z
Called roaming number terminated in MA network Roaming calls in an MA network need to be added with prefixes before being routed out to another virtual MSC server in the MA network through another office for processing. To prevent another office from modifying data, you can configure data to remove prefixes before calls are routed out.
ADD CNACLD: PFX=K'13900414, CSA=MLCO, RSC=11, MINL=11, MAXL=11, ICLDTYPE=MSRH; ADD CNACLD: PFX=K'13900415, CSA=MLCO, RSC=11, MINL=11, MAXL=11, ICLDTYPE=MSRH;
The following applies to handover numbers. In the case of handover, the call source is the one that matches the location area of the subscriber on the handover initiation side.
ADD DNC: DCX=6, DCT=TYPE13, DCL=2, ND=K'd1; ADD DNC: DCX=7, DCT=TYPE13, DCL=2, ND=K'd2;

ADD CLDPREANA: CSC=0, CS=MAP,

PFX=K'8613900415, MINCLDLEN=13,
CDADDR=ALL, CRP=ALL, CLDNCX=6, PT=DONTPROC; ADD CLDPREANA: CSC=2, CS=MAP, PFX=K'8613900415, MINCLDLEN=13,
CDADDR=ALL, CRP=ALL, CLDNCX=7, PT=DONTPROC;
ADD CNACLD: PFX=K'd113900415, CSA=MLCO, RSC=1, MINL=13, MAXL=13, ICLDTYPE=PS; ADD CNACLD: PFX=K'd213900414, CSA=MLCO, RSC=2, MINL=13, MAXL=13, ICLDTYPE=PS;
The prefix needs to be removed before a call is routed out.

ADD DNC: DCX=10, DCT=TYPE6, DCL=2, DAI=NDN; ADD OUTNUMPREPRO: CSC=65534, TG=65534, P=0, PFX=K'd1, DDX=10; ADD OUTNUMPREPRO: CSC=65534, TG=65534, P=0, PFX=K'd2, DDX=10;
The prefix needs to be removed before handover is done for a call to be routed out. Note that you need to configure data according to an actual office direction because the office direction table does not match.
ADD HDOVPROC: CID=K'139, PFX=K'd1, PEEROFFICENO=100, DDCX=10; ADD HDOVPROC: CID=K'139, PFX=K'd2, PEEROFFICENO=100, DDCX=10;
For a called roaming number not terminated in the MA network, the call needs to be routed to the local toll office of the network where the call is terminated.
ADD CNACLD: PFX=K'13900413, CSA=MLCO, RSC=3, MINL=11, MAXL=11, ICLDTYPE=MSRH;
Mobile subscriber calling local fixed-line subscriber or subscriber of a mobile network belonging to another carrier
When a mobile subscriber calls a local fixed-line subscriber or a subscriber of a mobile network belonging to another carrier, the mobile subscriber number carries no area code. The mobile subscriber is routed to the correct PSTN according to the call source configured. In general, if the call is forwarded, the system unifies the forwarded-to number in the called number pre-analysis table, that is, to add an area code with a national number prefix before the forwarded-to number. To keep consistency with the area code that is added to the forwarded-to number, the system adds an area code in the same form before the local fixed-line number in the called number pre-analysis table. This is convenient for the system to do the called number analysis uniformly.
ADD DNC: DCX=3, DCT=TYPE1, ND=K'0414, DAI=NDN; ADD DNC: DCX=4, DCT=TYPE1, ND=K'0415, DAI=NDN;
ADD CLDPREANA: CSC=0, CS=MUSER, PFX=K'87654321, MINCLDLEN=8, CDADDR=ALL, CRP=ALL, CLDNCX=3, PT=DONTPROC; ADD CLDPREANA: CSC=2, CS=MUSER, PFX=K'87654321, MINCLDLEN=8, CDADDR=ALL, CRP=ALL, CLDNCX=4, PT=DONTPROC;
ADD
CNACLD:
PFX=K'1300414,
CSA=MLCT,
RSC=20,
MINL=11,
MAXL=11,
ICLDTYPE=PS; ADD CNACLD: PFX=K'1300415, CSA=MLCT, RSC=20, MINL=11, MAXL=11,
ICLDTYPE=PS;
Mobile subscriber calling toll fixed-line subscriber or subscriber of a toll mobile network belonging to another carrier or local fixed-line subscriber with an area code When a mobile subscriber calls a toll fixed-line subscriber or a subscriber of a toll mobile network belonging to another carrier or local fixed-line subscriber with an area code, the call is directed according to the configured call sources of the mobile subscriber and the trunk.
z
If the called number is a fixed-line subscriber number in area A, the call needs to be routed to the local toll office of the area network when the call is terminated in an area network.
ADD
CNACLD:
PFX=K'0414,
CSA=LCT,
RSC=11,
MINL=11,
MAXL=11,
ICLDTYPE=PS;
If the called number is a fixed-line subscriber number in area B, the call needs to be routed to the local toll office of the area network when the call is terminated in an area network.
ICLDTYPE=PS;
If the called number is the number of a fixed-line subscriber outside the MA network or a subscriber of a mobile network belonging to another carrier and outside the MA network, the call is routed to the local toll office of the network when the call is terminated in a network.
ADD RTANA: RSC=13, RSSC=0, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=2, ISUP=NOCHG; ADD RTANA: RSC=13, RSSC=10, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=15, ISUP=NOCHG; ADD RTANA: RSC=21, RSSC=0, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=2, ISUP=NOCHG; ADD RTANA: RSC=21, RSSC=10, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=15, ISUP=NOCHG; ADD CNACLD: PFX=K'0413, CSA=LCT, RSC=13, MINL=11, MAXL=32,
ICLDTYPE=PS; ADD CNACLD: PFX=K'1300413, CSA=MNTT, RSC=21, MINL=11, MAXL=11, ICLDTYPE=PS;
If the call is an international toll call, the call is routed to the local toll office of the network when the call is terminated in a network.
ADD RTANA: RSC=30, RSSC=0, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=2, ISUP=NOCHG; ADD RTANA: RSC=30, RSSC=10, CC=CAT254, ADI=ALL, TP=ALL, TMX=0, R=15, ISUP=NOCHG; ADD CNACLD: PFX=K'00, CSA=ITT, RSC=30, MINL=3, MAXL=32, ICLDTYPE=PS;
Remove the area code of an outgoing call.

ADD DNC: DCX=5, DCT=TYPE6, DCP=0, DCL=4; ADD OUTNUMPREPRO: CSC=65534, TG=2, P=0, PFX=K'0414, ODDX=5;
ADD OUTNUMPREPRO: CSC=65534, TG=15, P=0, PFX=K'0415, ODDX=5;
Fixed-line subscriber calling mobile subscriber (The MOSFTX3000 needs to be configured when it functions as a gateway office and a fixed-line gateway) //The configuration of the number analysis data is similar to that of a mobile subscriber calling another mobile subscriber. Their difference is that the MSOFTX3000 needs to bar the call made by a local fixed-line subscriber to a mobile subscriber of another area in the MA network if 0 is not added before the called number, when the MSOFTX3000 functions as a gateway office. A fixed-line subscriber calls a local mobile subscriber directly. 0 needs to be added before the called number when a fixed-line subscriber calls a mobile subscriber outside the MA network. If 0 is added, the system prompts the subscriber to add 0. In this case, data is configured to do the number authority check.
//A fixed-line subscriber in area A is not allowed to call a mobile subscriber in area B directly.
//A fixed-line subscriber in area B is not allowed to call a mobile subscriber in district A directly.
//A fixed-line subscriber in area A is not allowed to call a mobile subscriber in other areas directly.
ADD PFXPRO: CSC=2, PFX=K'1390755, STF=NSDT, PT=FAILPROC, FCC=CV110;
XIV. Configuring Call Forwarding Data

The forwarding consists of three cases: forwarding to a mobile subscriber in another network, forwarding to a fixed-line subscriber and forwarding to a local fixed-line subscriber. You need to configure called number pre-processing for the three cases. If the forwarding number is a mobile subscriber number, such as a number beginning with 8613, then 86 is removed; if the forwarding number is a fixed-line subscriber number, such as a number beginning with 86, 86 is removed and then 0 is added. There are two records.
ADD DNC: DCX=8, DCT=TYPE6, DCP=0, DCL=2; ADD DNC: DCX=9, DCT=TYPE13, DCP=0, DCL=2, ND=K'0;
ADD CLDPREANA: CSC=65534, CS=MAP, PFX=K'86, MINCLDLEN=9, CDADDR=IDN, CRP=ALL, CLDNCX=9, PT=DONTPROC; ADD CLDPREANA: CSC=65534, CS=MAP, PFX=K'8613, MINCLDLEN=13, CDADDR=IDN, CRP=ALL, CLDNCX=8, NP=255, PT=DONTPROC;
XV. Setting Online Mode

//Set format switch and set online mode.
FMT:; LON:;
Chapter 5 System Commissioning

For an MA network, you need to do commissioning on the following:
z z z z z z z z z
Subscriber Location Update Ordinary Call Flow IN Related Service Supplementary Service Registration Forwarding Call Authentication Text Message Service Handover Process Traffic statistics Other Services
Note: During commissioning, you need to select related traffic entities and observe them. And also you need to check that the bills are normal.
5.1 Subscriber Location Update

I. Commissioning Contents
Test subscriber location update and roaming restriction to see whether they are normal. This test is to check the basic location update process of a subscriber. The basic location update includes the following:
z z z z
Local location update in an MA network Location update between areas in one MA network Location update of a subscriber of another roaming to the local area Location update of a subscriber of a local area roaming to another area
II. Expected Results

The location of the subscriber is updated.
z z
A call can be made. The system sends a message requesting location update to the HLR. The caller MSC number contained in the message is correct.
5.2 Ordinary Call Flow

The caller and the callee are in the same MA network or a different MA network. Check an intra-office call, mobile outgoing call, incoming call and transit call according to call category and check that their bills are correct. In an MA network, when a fixed-line subscriber calls a mobile subscriber of another virtual MSC server without adding 0 before the called number, test whether there is a prompt tone to bar the call.

Basic calls succeed.
z
The calling MSC number, which maps to the location area where the call is originated, is correctly filled in the caller bill. The calling MSC number, which maps to the location area where the call is terminated, is correctly filled in the callee bill. The MSC number that goes through a gateway office is filled correctly. The MSC number is an MSC number in the call source mapping to an outgoing/incoming trunk group.
Check that there is an IAM message for the outgoing trunk call if a call between area networks is an outgoing trunk call. Check that the call is normal if a call between MA networks is an intra-office call. Call barring succeeds. The system sends a prompt tone indicating that 0 should be added if a fixed-line subscriber makes a call to a mobile subscriber of another virtual MSC server in the same MA network without 0 added before the callee number.
z z
5.3 IN Related Service

Check:
z
Whether IN call flows are normal, such as the caller call flow and the callee call flow; whether other flows are normal, such as charging flow Whether bills are normal Whether the subscriber balance is deducted properly
z z

Basic calls succeed.
z z z
IN calls are normal. The SCP deducts the balance of a subscriber properly when a call ends. Local IN bills are normal and MSC numbers are filled correctly in bills.

z
A mobile subscriber recharges fees and then makes a call successfully.
5.4 Supplementary Service Registration

Check that the registration of the supplementary service is normal. For example, check:
z z z
Whether the forwarded-to number registered is correct Whether the area code of the forwarded-to fixed-line subscriber number is correct Whether the forwarding is normal

The supplementary service is registered successfully:
z
When you use a mobile phone to query service registration, the HLR sends back a service registration result with a correct number. The forwarding call succeeds and the forwarded-to number is correct.
5.5 Forwarding Call Authentication

The caller and the callee are in the same MA network or the caller and the callee are in a different MA network. Check:
z
Whether the calls of various forwarding types are normal when the callee is a PSTN or mobile subscriber Whether the bills of various call types are normal and the fees are deducted properly

Forwarding calls are normal.
z z
Forwarding calls of various types are normal and the forwarding bills are normal. Check that the MSC number in the bill is the MSC number terminating on the forwarding party side when the callee is busy or makes no reply. In other cases, the MSC number is the MSC number on the caller side.
5.6 Text Message Service

The test of a text message includes the authentication of the text message on the caller side and the callee side.

When the caller sends a text message, the callee receives the text message successfully.
5.7 Handover Process

Check handover, such as:
z z z
Intra-office handover in an MA network Inter-office handover in an MA network Handover between an office in an MA network and an office outside an MA network

You can make a call after handover. You can see an IAM message routed out on the link during handover when handover in an MA network is inter-office handover.
5.8 Traffic statistics

Check that the network manager can obtain data related to traffic statistics.

Related traffic statistics indexes can be reported and the network manager can take control of the switch.
5.9 Other Services

Check that services in an MA network, and charging and traffic statistics are normal, for example, the charging of ringback tone service, and charging of the PPIP caller and callee.

Related services can be achieved. See the standards of related services for details.
Chapter 6 Test Items

Figure 6-1 shows a model of MA networking.
MSOFTX3000 Virtual MSCA 8613900414 MASI=0 area=0414 Virtual MSCB 8613900415 MASI=1 area=0415
MGW8
MGW9
PSTN
PSTN
BSC Area A
RNC
RNC Area B
BSC
Figure 6-1 MA networking model The following table lists the basic test cases for an MA network: Test item Description A subscriber of area A updates the location for the first time. A subscriber of area B updates the location in area A. 01 Location update The HLR of area A sends RESET to the VLR. A subscriber of area A makes a call. The HLR of area A sends RESET to the VLR. A subscriber of area B makes a Call. Expected output
The location is updated.
The first call fails, but the second succeeds.
The first call succeeds.
Test item
Description A local smart subscriber of area A initiates location update in area A. A local smart subscriber of area B initiates location update in area A. A subscriber of area A calls a PSTN subscriber of area A. A subscriber of area B who roams to area A calls a PSTN subscriber of area A. A subscriber of area A calls a PSTN subscriber of area B. A subscriber of area B who roams to area A calls a PSTN subscriber of area B. A PSTN subscriber of area A calls a subscriber of area A. A PSTN subscriber of area A calls a subscriber of area B who roams to area A. A PSTN subscriber of area B calls a subscriber of area A. A PSTN subscriber of area B calls a subscriber of area B who roams to area A. A subscriber of area A calls an MS subscriber of area A. A subscriber of area A calls an MS subscriber of area B who roams to area A. A subscriber of area B who roams to area A calls an MS subscriber of area A. A subscriber of area B who roams to area A calls an MS subscriber of area B who roams to area A.
Expected output
02 Roaming Restriction
The location update fails.
03 Basic Call
The call is connected, and the bill is correct. The call is connected, and the bill is correct. The call is connected, and the bill is correct. The call is connected, and the bill is correct. The call is connected, and the bill is correct. The call is connected, and the bill is correct. The call is connected, and the bill is correct. The call is connected, and the bill is correct. The call is connected, and the bill is correct. The call is connected, and the bill is correct. The call is connected, and the bill is correct.
The call is connected, and the bill is correct.
Test item
Description A subscriber of area A calls an MS subscriber of area A who roams to area B. A subscriber of area A calls an MS subscriber of area B. A subscriber of area B who roams to area A calls an MS subscriber of area A who roams to area B. A subscriber of area B who roams to area A calls an MS subscriber of area B. A subscriber of area A makes a police emergency call. A subscriber of area B who roams to area A makes a police emergency call. A subscriber of area A makes a national toll call. A subscriber of area B who roams to area A makes a national toll call.
Expected output The call is connected, and the bill is correct. The call is connected, and the bill is correct. The call is connected, and the bill is correct.
The call is connected, and the bill is correct. The call is connected to the nearest police station. The call is connected to the nearest police station. The call is connected, and the bill is correct. The call is connected, and the bill is correct. The call is connected, and the bill is correct.
A subscriber of area A calls a PSTN subscriber of area A without dialing the area code.
Note: Whether the call can be connected depends on whether the local dialing scheme allows subscribers to dial no local area code.
The call fails, and the announcement is played.
A subscriber of area B who roams to area A calls a PSTN subscriber of area A without dialing the area code. A subscriber of area B who roams to area A calls a PSTN subscriber of area B without dialing the area code.
The call fails, and the announcement is played.
Test item
Description A PPS subscriber of area A calls a PSTN subscriber of area A. A PPS subscriber of area B who roams to area A calls a PSTN subscriber of area A. A PSTN subscriber of area A calls a PPS subscriber of area A. A PSTN subscriber of area A calls a PPS subscriber of area B who roams to area A. A PPS subscriber of area A calls another PPS subscriber of area A. A PPS subscriber of area A calls a PPS subscriber of area B who roams to area A.
Expected output The call is connected, and the bill is correct. The call is connected, and the bill is correct. The call is connected, and the bill is correct.
04 Intelligent Call
A PPS subscriber of area B who roams to area A calls a PPS subscriber of area A. A PPS subscriber of area B who roams to area A calls a PPS subscriber of area B who roams to area A. A VPN subscriber of area A calls another VPN subscriber of area A by dialing the short number. A VPN subscriber of area A calls a VPN subscriber of area B who roams to area A by dialing the short number. A PPS subscriber of area A queries call charge, recharges value, and calls the attendant console. A PPS subscriber of area B who roams to area A queries call charge, recharges value, and calls the attendant console.
The operations are successful.
The operations are successful.
Test item
Description Call forwarding busy: A->B->C (B is a subscriber of area A). Call forwarding no reply: A->B->C (B is a subscriber of area A).
Expected output The call is connected, and the bill is correct. The call is connected, and the bill is correct.
05 Call Forwarding
Call forwarding on mobile subscriber not reachable: A->B->C (B does not respond; B is a subscriber of area A). Call forwarding on mobile subscriber not reachable: A->B->C (B powers off the phone; B is a subscriber of area A). When a subscriber of area A calls an MS subscriber of area A, the caller is handed over from area A to area B. When a subscriber of area A calls an MS subscriber of area A, the caller is handed over from area A to area B and then handed back from area B to area A.
The call and handover are both successful.
06 Handover
When a subscriber of area A calls an MS subscriber of area A, the caller is handed over from area A to area B and then handed over from one BSC to another BSC in area B. When a subscriber of area A calls an MS subscriber of area A, the caller is handed over from area A to an area covered by other MSC.
07 Short Message Service
A subscriber of area A sends a short message. A subscriber of area B who roams to area A sends a short message. A subscriber of area A receives a short message.
The short message is sent successfully, and the bill is correct. The short message is sent successfully, and the bill is correct. The short message is received successfully, and the bill is correct.
Test item
Description A subscriber of area B who roams to area A receives a short message.
Expected output The short message is received successfully, and the bill is correct. The call forwarding services are activated and deactivated successfully. The forwarded-to numbers are correct. For fixed line numbers, you need to check if the area codes are correct. The call waiting services are activated and deactivated successfully. The external NMS equipment can obtain the related traffic statistics entities successfully and the results are correct.
08 Supplementary Services and USSD
Activation and deactivation of call forwarding services
Activation and deactivation of call waiting services
09 Traffic Statistics
Set related tasks on the M2000 according to the traffic statistics entities required by the customer and check the results.
Note:
This test aims to verify the interaction with the upper-level NMS and to verify if the equipment is running well after cutover. There are many traffic statistics entities, which are not listed here.
10 Other Special Services
They include RBT, PPIP, collect call, and so on.
Note: This test should be carried out according to the requirements of different areas.
Chapter 7 Network Upgrade

7.1 Upgrade Notes
Pay attention to the following:
z
Impact on external NEs
External NEs may be affected if you modify the data configuration during upgrade. The involved external NEs include HLR, office direction of the newly added trunks, devices on the access side, STP, short message center, and SCP.
z
Impact on charging
The upgrade does not affect charging, but there are special requirements for the billing center after the upgrade. Because the bills of different virtual MSC Servers are stored in different folders of the iGWB, the billing center needs to obtain the bills from the folders of the newly added virtual MSC Servers. For a newly deployed office or an upgrade office, you need to negotiate the bill obtaining mode with the billing center.
z
Impact on traffic statistics
The upgrade of a non-MA-network office to an MA-network office will change the traffic statistics interface between the M2000 and the external NMS center. Therefore, you need to modify the traffic statistics interaction relation and adapt the M2000 with the external NMS center. Suppose one M2000 manages several MSOFTX3000s, and some MSOFTX3000s apply MA networking but some do not. In this case, you need to ensure all MSOFTX3000s support MA networking and the host versions are the same. Otherwise, traffic statistics cannot be carried out.
Caution:
z
For upgrade of an MA-network office, including upgrade of the patches related to traffic statistics and cutover of a new office, you need to contact a technical support engineer of Huawei in advance to confirm the traffic statistics interaction relation and version of the M2000.
For upgrade of an MA-network office, be sure to prepare for the change of the traffic statistics interaction relation beforehand. Otherwise, the cutover might be prolonged or traffic statistics might fail after cutover.
7.2 Upgrade Steps

This section only guides on the data configuration for MA network upgrade. For specific commands, see Chapter 4 Data Configuration. Figure 7-1 lists the data configuration steps for upgrading a network to an MA network.
Start
Apply for License
Set hardware data
Set multi-area network flags
Sett local SP and MSC number and loading License
Set mutual-assistance relation
Set MGW data
Set link data
Set SCCP data
Set data for access side and trunk side
Set number analysis, trunk group and trunk circuit data Set service data
End
Figure 7-1 Data configuration steps for upgrading a network to an MA network
7.2.1 Applying for License

The change of the local office table and the mobile local office table will lead to a License alarm and eventually system failure. Therefore, you need to apply for a License before the upgrade.
Note: For details about how to apply for a License, contact a technical support engineer of Huawei.
7.2.2 Setting Hardware Data

When setting hardware data, you need to consider the load sharing condition of the whole MA network and to achieve even sharing of the load among local networks.
7.2.3 Setting Multi-Area Network Flags

Follow the steps below: 1) 2) Enable the traffic statistics subsystem of the M2000 to support MA networking and adapt the interface between the M2000 and the NMS center. Enable the M2000 to support MA networking, for some multi-area statistics index conditions must be met to achieve interworking between the M2000 and the MSOFTX3000. 3) After changing the data of the M2000, register the traffic statistics entities again so that you can add a traffic statistics index for a new local network. Otherwise, only the traffic statistics data of the default local network numbered 0 will be contained in the measurement results of the M2000. If the multi-area statistics index of area A is 0, only 00 (intra-office traffic of area A) will be measured for intra-office traffic. After adding a local network of area B, you need to set traffic statistics entities for other intra- and inter-office call combination restriction conditions for 01 (out-office traffic from area A to area B), 10 (out-office traffic from area B to area A), and 11 (intra-office traffic of area B) of MA network intra-office traffic again. 4) Use SET OFI to set the multi-area flag of the local office table. After the change of the flag, the original traffic statistics entities related to the local office are not affected. However, only the traffic of the original MA network will be measured in this case. For example, only 00 (intra-office traffic of area A) will be measured for intra-office calls. Therefore, to measure several MA networks, you need to re-register local traffic statistics entities after setting all data.
7.2.4 Setting Local SP and MSC Number and Loading License

Follow the steps below: 1) 2) 3) Use ADD OFI to set the newly added SP in the local office table. Use ADD INOFFMSC to set the newly added MSC number in the mobile local office table. Use LOD LICENSE to load the License to the host and BAM.
4) 5)
Use ADD MASI to add a multi-area statistics index, area name, national area code, MSC number, and VLR number for the new MSC. Use MOD MASI to modify the multi-area statistics index in the original data table.
Caution: Different multi-area statistics indexes cannot be added for one MSC number, so they must be planned uniformly.
7.2.5 Setting Mutual-Assistance Relation

If several SPs can only be connected to the HLR through the SP mapped to one local MSC number, you need set the mutual-assistance relation between SPs. Use MOD OFI to set it.
7.2.6 Setting MGW Data

Follow the steps below: 1) 2) 3) Use ADD MGW to add MGW data. Use ADD H248LNK to add H.248 link data for the MGW. Use ADD ESG, ADD M2LKS, and ADD M2LNK to add M2UA links.
7.2.7 Setting Link Data

Follow the steps below: 1) 2) Use ADD N7DSP, ADD N7LKS, ADD N7LNK, and ADD N7RT to add MTP3 data for trunks. Add MTP3 data for the access side.
Caution: You need to set MTP DSP data for several OSPs mapping to several local SPs.
7.2.8 Setting SCCP Data

Use ADD SCCPDSP, ADD SCCPSSN, and ADD SCCPGT to add SCCP data.
Caution: You need to set SCCP DSP and SCCP SSN data for several OSPs mapping to several local SPs.
For SCCP GT, you only need to add the GT data for a new MSC number. The other GT translation data is shared. The new SP working in mutual-assistance mode is directly connected by a link to the HLR of the area mapped to the new MSC number. The new SCCP GT translation data is sent to the destination HLR (that is, the local HLR) through the direct link. For connection between multiple SPs and the peer office,
z z
In non-MA networking, the DPC of GT data is set to STP SPC. In MA networking, the DPC of GT data is set to HLR SPC.
Signaling links route the GT data to the STP automatically at the MTP layer, and then the STP transfers the data to the HLR.
7.2.9 Setting Data for Access Side and Trunk Side

Follow the steps below: 1) 2) 3) 4) Use ADD CALLSRC to add call source data for the access side and the trunk side. Use ADD OFC to add office direction data for the access side and the trunk side. Use ADD BSC and ADD LAIGCI to add BSC and location area and cell data, including the data of the local and adjacent location areas. Use ADD MARLATION to add the inter-office relation data for the two new MA networks. If there is no circuit between two MGWs, the original routing mode is used to route the calls to the intra-province toll tandem office and then to another MGW. 5) 6) 7) Use ADD RANMGW to add radio access network MGW data. Use ADD SRT to add sub-route data. Use ADD RT and ADD RTANA to add route analysis data.
Caution: Be sure to add the related location area and cell data after adding a BSC. If you add a BSC but do not add location area and cell data for it, the new BSC will fail to send a paging message during paging in the whole network, thus affecting system efficiency.
7.2.10 Setting Number Analysis, Trunk Group and Trunk Circuit Data
Follow the steps below: 1) 2) 3) Use ADD CLDPREANA to add number analysis data. Use ADD AIETG, ADD N7TG, ADD PRATG, and ADD CASTG to add trunk group data for both the access side and the trunk side. Use ADD AIETKC, ADD N7TKC, ADD PRATKC and ADD CASTKC to add trunk circuit data. Follow the principles below:
z
Because there is too much number analysis data and it takes long to execute this data, to load it needs relatively long time. Therefore, after setting the number analysis data script, you need to execute the commands in batches and at most five commands can be executed at a time.
It is required to include area codes in local PSTN numbers. An area code is added in the PSTN number sent from the call source (mobile phone) during called number preprocessing.
Adding trunk group data with ADD AIETG and ADD N7TG will result in sharp rise of CPU usage, so trunk group data must be added or removed during night. Because there is much trunk circuit data and adding or removing circuits will increase CPU usage, you need to add or remove circuits when the traffic is light.
7.2.11 Setting Service Data

Follow the steps below: 1) 2) Add roaming number allocation data. Add other related service data.
Chapter 8 Handling of Common Problems

This chapter focuses on common problems and their handling methods.
8.1 How to Measure Traffic of Local Networks

The multi-area statistics index for outgoing calls can be set to any one of the local-network statistics indexes. In this case, there is only one statistics index for one office direction, so it is impossible to measure the traffic of each local network. To solve this problem, you need to configure several trunk groups, so that the traffic of different local networks can be measured by trunk group number. During data configuration, you can set different multi-area statistics indexes for trunk groups to achieve traffic statistics by local network. During upgrade, note to change the version relation and data. After upgrade, you need to set multi-area statistics index for trunk groups.
Caution:
z z
In MA networking, multi-area statistics index is not used in public office directions. For details about MA-network traffic statistics, see section 3.11 Principle of Traffic statistics.
8.2 How to Store Bills of Multi-Area Network

Bills are stored in different folders by MSC numbers of the charged entities.
Note: For storage of bills in the iGWB, see section 3.10.2 Principles for Saving Bill Files in the iGWB.
8.3 How to Set Routing Data

Different route selection source codes need be set for different call sources, but a same route selection code is used if the callee is the same. The system determines a route
according to the combination of a route selection source code and a route selection code in the route analysis table.
8.4 How to Set Trunk Group Data in Multi-SP Networking

In multi-SP networking, outgoing call data is decided according to the trunk group data set in the system:
z
If you do not enter OPC when adding No. 7 trunk group data, the first SPC in the local office table will be contained in the outgoing IAM message. If you have entered OPC when adding No. 7 trunk group data, the OPC will be contained in the outgoing IAM message.
8.5 How to Set Interworking Data

Data configuration for interworking with other NEs can be divided into the following two cases:
z z
New networking Compatible with original networking
I. New Networking
In this case, set the interworking data as follows: 1) 2) 3) Set a link set connected with the HLR by using the SP in the first record of the local office table. Use MOD OFI to set the SP as the mutual assistant SP for the other SPs to achieve interconnection between the other SPs and the peer HLR. On the HLR, set signaling routes that belong to one signaling link set for SPs.
II. Compatible with Original Networking

To keep the original signaling network structure unchanged, you need to set direct links between the SPs and the local HLR and to set GT data to use DPC addressing. By using the MTP layer for transfer, the local office selects different link sets based on different OSPs to achieve direct link to the local HLR and to use the original link relayed by the STP to a remote HLR. The STP transfer mode is different from the original GT transfer based on the SCCP layer, but the routing plan is the same as that of the original network. Different areas only need to maintain their own data, and the HLR of an area only maps to its home MSC SP. In STP transfer mode, MTP DSP data, SSCP DSP data, SCCP SSN data, and DPC addressing data of the HLR need be set on the virtual MSC in a local network. You also need to set MTP DSP data, SSCP DSP data, and SCCP SSN data of the virtual MSC on the HLR.
Note: By default, the STP uses signaling transfer at the SCCP layer. For compatibility with the original networking, if STP transfer is needed, the STP should support and enable signaling transfer at the MTP layer.
8.6 How to Set Source GT Data in SCP Messages

The CAP calling GT address sent to the SCP is the MSC number reported by the MSC to the SCP.
8.7 How to Set Number of Local Networks

In an MA network with only one MSOFTX3000, there can be 16 local networks at most.
Note: In actual networking, it is suggested to build no more than three local networks in an MA network in consideration of data volume and maintenance.
8.8 How to Set Local Number Length

For different areas in an MA network, if local numbers are not of the same length, you need to set the local number length to that of the longest number. For example, the number length of an area is 7 but that of another area is 8, set the local number length to 8 digits.
Caution: The local number length is controlled by a software parameter. For modification of the software parameter, see section 4.3.5 Setting Local Number Length.
8.9 How to Set Area Code of Local Network

When a mobile subscriber calls a local fixed subscriber, the caller needs to dial the area code before the called number. The principles are as follows:
z
If a call is forwarded to a fixed subscriber, the system removes the country code before the forwarded-to number and adds the national toll prefix 0 before the area code in the incoming number pre-processing table.
To keep data consistency, the system needs to add area codes before subscriber numbers according to call source in the called number pre-analysis table for calls from mobile subscribers of local networks to fixed subscribers.
If two subscribers of different local networks in an MA network share a same number, the system might not be able to distinguish the prefixes of calls to different subscribers of local networks if you just set the attributes by subscriber number in the called number analysis table.
During number processing, if the call source code is changed, the call to a subscriber of a local network will be routed to another local network and the call will fail. By adding area codes before prefixes during called number pre-analysis and processing, the system can route calls by area code.
8.10 How to Set National Toll Prefix and International Toll Prefix
Follow the principles below:
z
In single-SP mode, the system uses the national toll prefix and international toll prefix set by SET INOFMSC in the mobile local office table by default. In multi-SP mode, you need to use ADD INOFFMSC to set the national toll prefix and international toll prefix in the mobile local office table correctly. Otherwise, calling number processing will fail and a wrong number will be displayed on the callees phone set.
8.11 How to Intercept Subscribers of Multi-Area Network

In an MA network, the lawful interception center might be able to intercept the subscribers of the virtual MSC Servers that are not set in the interception data. For example, if an intercepted subscriber is in area A, the lawful interception center in area A can intercept the subscriber successfully. However, if the subscriber is intercepted from area B, the subscriber data will be returned too.
Chapter 9 Acronyms and Abbreviations

A ATM Asynchronous Transfer Mode
B BAM BHCA BICC BSC Back Administration Module Busy Hour Call Attempt Bearer Independent Call Control Protocol Base Station Controller
C CAP CIC CPU CAMEL Application Part Circuit Identification Code Center Processing Unit
D DPC Destination signaling Point Code
G GMSC GSM GT GW Gateway Mobile Switching Center Global System for Mobile Communications Global Title Gateway
H HLR HSTP Home Location Register High-level Signaling Transfer Point
I IAM ID Initial Address Message Identification

iGWB IMSI IP ISUP
iGateway Bill International Mobile Subscriber Identity Internet Protocol ISDN User Part
L LAI LCS LSTP Location Area Identity Location Service Low Level Signaling Transfer Point
M M2UA M3UA MAP MCC MGW MNC MOC MS MSC MSRN MTC MTP MTP3 MTP3B SS7 MTP2-User Adaptation Layer SS7 MTP3-User Adaptation Layer Mobile Application Part Mobile Country Code Media Gateway Mobile Network Code Mobile Originated Call Mobile Station Mobile Switching Center Mobile Station Roaming Number Mobile Terminated Call Message Transfer Part Message Transfer Part Layer 3 Message Transfer Part (Broadband)
N NGN Next Generation Network
O OPC Originating signaling Point Code
P PRA Primary Rate Adaptation

PSTN
Public Switched Telephone Network
R RNC Radio Network Controller
S SCCP SCP SCTP SG SIP SPC SS7 SSN STP Signaling Connection Control Part Service Control Point Simple Control Transmission Protocol Signaling Gateway Session Initiation Protocol Signaling Point Code CCITT Signaling System No.7 Sub-System Number Signaling Transfer Point
T TDM TMSC TMSI TUP Time Division Multiplex(ing) Tandem MSC Temporary Mobile Subscriber Identifier Telephone User Part
U USSD Unstructured Supplementary Service Data
V VLR VMSC VPN Visitor Location Register Visited MSC Virtual Private Network
W WCDMA Wideband CDMA
Index
Index
A
advantage, 1-4 area code, 3-2, 8-4 destination network mode, 3-10 non-destination network mode, 3-10 interworking data, 8-2
L B
background information, 1-1 bill, 8-1 bill file, 3-13, 8-1 lawful interception service, 3-11, 8-4 limitation, 1-4 local number length, 8-3 location update, 3-4
C
call data, 3-6 call routing, 3-7 charging, 3-11 common problem, 8-1
M
MSC number, 3-1 Multi-Area statistics index, 3-14
N
network upgrade note, 7-1 step, 7-2 networking signaling networking, 2-8 voice channel networking, 2-2 networking with intermediate bearer IP bearer, 2-6 TDM bearer, 2-6 number of local network, 8-3
D
data configuration basic information of local office, 4-7 bearer data, 4-8, 4-25 example, 4-17 planning, 4-2 scheme, 4-1 service data, 4-9, 4-10, 4-23 signaling data, 4-8, 4-20 software parameter, 4-5 data protection, 3-5 definition, 1-1
P
paging optimization, 3-8
F
feature, 1-3
R
roaming feature, 3-4 roaming number, 3-5 routing data, 8-1
H
handover, 3-9
S I
IN service scheme, 1-2 service data Huawei Technologies Proprietary i-1
Multi-Area Network User Manual HUAWEI MSOFTX3000 Mobile SoftSwitch Center handover data, 4-10 LAI and office direction trunk, 4-9, 4-24 mobile service management, 4-10, 4-23 number analysis and route selection, 4-12 roaming number data, 4-12, 4-23 signaling networking classified by signaling point, 2-8 classified by signaling transmission network towards MGW, 2-14 classified by signaling transmission network towards NE, 2-16 source GT data, 8-3 system commissioning forwarding call authentication, 5-3 handover process, 5-4 IN related service, 5-2 ordinary call flow, 5-2 other service, 5-4 subscriber location update, 5-1 supplementary service registration, 5-3 text message service, 5-4 VLR list, 3-5 voice channel networking
Index
T
test item, 6-1 toll prefix, 8-4 traffic measurement, 8-1 traffic statistics, 3-14, 8-1 traffic statistics unit, 3-15 trunk group data, 8-2
multiple MGWs with intermediate bearer, 2-4 multiple MGWs without intermediate bearer, 2-3 single MGW, 2-2
Z
ZoneCode, 3-5
i.
Huawei Technologies Proprietary i-2

Area Network User Manual PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Area Network User Manual PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Mobile SoftSwitch Center Multi-Area Network User Manual

Huawei Technologies Co., Ltd.

Huawei Technologies Proprietary

Copyright 2006 Huawei Technologies Co., Ltd.

All Rights Reserved

, HUAWEI, C&C08, EAST8000, HONET,

, ViewPoint, INtess, ETS, DMC,

Huawei Technologies Proprietary

About This Manual

Operation and maintenance engineers Marketing technical personnel

Huawei Technologies Proprietary

Engineering technical personnel

II. Command conventions

III. GUI conventions

IV. Mouse operation

Caution: Means reader be extremely careful during the operation.

Note: Means a complementary description.

Huawei Technologies Proprietary

Multi-Area Network User Manual HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Huawei Technologies Proprietary i

Multi-Area Network User Manual HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Multi-Area Network User Manual HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Huawei Technologies Proprietary iii

Multi-Area Network User Manual HUAWEI MSOFTX3000 Mobile SoftSwitch Center

I. For Areas with High Subscriber Density

II. For Areas with Lower Subscriber Density

1.2 Definition of Multi-Area Networking

Huawei Technologies Proprietary 1-1

Multi-Area Network User Manual HUAWEI MSOFTX3000 Mobile SoftSwitch Center

1.2.1 Basic Model of Multi-Area Networking

BSC MGW1 RNC MGW2

RNC PSTN PSTN Virtual MSC2/VLR2 DPC2

Virtual MSC1/VLR1 DPC1 Voice channel Signaling

TMSC: Tandem MSC MGW: Media Gateway

1.2.2 Schemes of Multi-Area Networking

Huawei Technologies Proprietary 1-2

Multi-Area Network User Manual HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Note: NE = Network Entity

1.3 Features of Multi-Area Networking

Huawei Technologies Proprietary 1-3

Multi-Area Network User Manual HUAWEI MSOFTX3000 Mobile SoftSwitch Center

1.3.2 Wide Coverage

1.3.3 Advantages over Traditional 2G Networking

1.3.4 Limitations of Multi-Area Networking

Note: BHCA refers to Busy Hour Call Attempt.

Huawei Technologies Proprietary 1-4

Multi-Area Network User Manual HUAWEI MSOFTX3000 Mobile SoftSwitch Center

II. Limitation of the Number of Local Networks

III. Limitation of the Capacity of Data Tables

TID134 TID137 TID300 TID301 TID302 TID305

1,024 1,024 2,048 2,000 512 4,000

Huawei Technologies Proprietary 1-5

Multi-Area Network User Manual HUAWEI MSOFTX3000 Mobile SoftSwitch Center

IV. Limitation of the Number of Trunk Circuits

Huawei Technologies Proprietary 1-6

Multi-Area Network User Manual HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 2 Networking Principles

Chapter 2 Networking Principles

Huawei Technologies Proprietary 2-1

Multi-Area Network User Manual HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 2 Networking Principles

2.2 Principles of Voice Channel Networking