Product Description PDF

HUAWEI MSOFTX3000 Product Description
Contents
Contents
1 Introduction.................................................................................................................................1-1
1.1 Product Orientation .......................................................................................................................................1-2 1.1.1 Introduction to the Mobile Softswitch Solution of Huawei .................................................................1-2 1.1.2 Features of Huawei's Mobile Softswitch Solution ...............................................................................1-3 1.1.3 Introduction to the MSOFTX3000.......................................................................................................1-6 1.2 Product Features............................................................................................................................................1-8 1.2.1 Dynamic Service Provision Capabilities..............................................................................................1-8 1.2.2 Powerful and Flexible Networking Capabilities ..................................................................................1-9 1.2.3 Large Capacity and High Integration .................................................................................................1-10 1.2.4 Powerful Processing Capabilities.......................................................................................................1-10 1.2.5 Highly Reliable .................................................................................................................................. 1-11 1.2.6 Capabilities for Smooth Expansion.................................................................................................... 1-11 1.2.7 Advanced Charging Capabilities........................................................................................................1-12 1.2.8 Excellent Performance Measurement Function .................................................................................1-12 1.2.9 Convenient and Useful O&M Function .............................................................................................1-13 1.2.10 Support for 2G/3G Integration .........................................................................................................1-13
2 System Structure ........................................................................................................................2-1

2.1 Hardware Structure .......................................................................................................................................2-2 2.1.1 Appearance...........................................................................................................................................2-2 2.1.2 Physical Structure ................................................................................................................................2-2 2.1.3 Logical Structure..................................................................................................................................2-5 2.2 Software Structure.........................................................................................................................................2-8 2.2.1 Overview..............................................................................................................................................2-8 2.2.2 Host Software.......................................................................................................................................2-9 2.2.3 BAM Software ...................................................................................................................................2-10 2.3 Capacity Expansion.....................................................................................................................................2-12 2.3.1 Cabinet Configuration........................................................................................................................2-12 2.3.2 Expansion Configuration ...................................................................................................................2-13
3 Interfaces, Signaling, and Protocols .......................................................................................3-1

3.1 Physical Interfaces ........................................................................................................................................3-2 3.1.1 Classification........................................................................................................................................3-2
Issue 03 (2006-09-30)
Huawei Technologies Proprietary
Contents
HUAWEI MSOFTX3000 Product Description 3.1.2 Interface Specifications........................................................................................................................3-3
3.2 Protocol Interface ..........................................................................................................................................3-4 3.2.1 Standard Interface ................................................................................................................................3-4 3.2.2 CDR Interface ......................................................................................................................................3-8 3.2.3 Interception Interface ...........................................................................................................................3-8 3.3 Signaling and Protocols.................................................................................................................................3-9
4 O&M System...............................................................................................................................4-1
4.1 Overview of O&M ........................................................................................................................................4-2 4.1.1 Basic Concept ......................................................................................................................................4-2 4.1.2 Terminal System ..................................................................................................................................4-2 4.1.3 Network Management Networking......................................................................................................4-4 4.1.4 Introduction to MML Command Line..................................................................................................4-4 4.2 O&M Function ..............................................................................................................................................4-4 4.2.1 Configuration Management .................................................................................................................4-4 4.2.2 Fault Management ...............................................................................................................................4-5 4.2.3 Performance Measurement ..................................................................................................................4-7 4.2.4 Security Management ..........................................................................................................................4-7 4.2.5 CDR Management ...............................................................................................................................4-7 4.2.6 Environment Monitoring......................................................................................................................4-8
5 Services and Functions..............................................................................................................5-1

5.1 Basic Services ...............................................................................................................................................5-2 5.1.1 Teleservices..........................................................................................................................................5-2 5.1.2 Supplementary Services.......................................................................................................................5-3 5.1.3 ODB Services.......................................................................................................................................5-6 5.1.4 IN Services...........................................................................................................................................5-7 5.1.5 Value Added Services...........................................................................................................................5-8 5.2 Basic Functions ...........................................................................................................................................5-10 5.2.1 Mobility Management........................................................................................................................5-10 5.2.2 Security Management ........................................................................................................................ 5-11 5.2.3 Handover............................................................................................................................................5-13 5.2.4 Call Processing...................................................................................................................................5-14 5.2.5 Charging.............................................................................................................................................5-16 5.2.6 SSP.....................................................................................................................................................5-21 5.3 Description of New Features.......................................................................................................................5-22 5.3.1 List of New Features..........................................................................................................................5-22 5.3.2 V100R005 Version .............................................................................................................................5-24 5.3.3 V100R003 Version .............................................................................................................................5-31
6 Networking and Application...................................................................................................6-1

6.1 Typical Networking.......................................................................................................................................6-2 6.1.1 MSC Networking .................................................................................................................................6-2 6.1.2 GMSC Networking ..............................................................................................................................6-4
ii
Issue 03 (2006-09-30)
Contents
6.1.3 TMSC Networking...............................................................................................................................6-6 6.1.4 Dual-Homing Networking ...................................................................................................................6-7 6.1.5 Multi-Area Networking......................................................................................................................6-10 6.1.6 Solution for Huawei IMS Interworking with CS Domain ................................................................. 6-11 6.1.7 Solution for Huawei NGN Interworking with CS Domain ................................................................6-12 6.1.8 Evolution Strategy of Huawei Mobile Core Network........................................................................6-13 6.2 Network Application Cases .........................................................................................................................6-15 6.2.1 Multi-area Commercial Network of Company A...............................................................................6-15 6.2.2 Dual-Homing Commercial Network of Company B .........................................................................6-17
7 Reliability and Security Design ..............................................................................................7-1

7.1 Reliability Design..........................................................................................................................................7-2 7.1.1 Hardware Reliability ............................................................................................................................7-2 7.1.2 Software Reliability .............................................................................................................................7-3 7.1.3 Reliability of Charging System............................................................................................................7-5 7.2 Security Design .............................................................................................................................................7-6 7.2.1 Networking Application Security.........................................................................................................7-6 7.2.2 Data Security........................................................................................................................................7-6 7.2.3 O&M Security......................................................................................................................................7-6 7.2.4 Security Authentication Information....................................................................................................7-7
8 Technical Specifications and Environmental Requirements ............................................8-1

8.1 Technical Specifications................................................................................................................................8-2 8.1.1 System Capacity...................................................................................................................................8-2 8.1.2 System Processing Capability ..............................................................................................................8-2 8.1.3 Protocol Processing Capability ............................................................................................................8-3 8.1.4 CDR Processing Capability .................................................................................................................8-3 8.1.5 Number Analysis Capability ................................................................................................................8-4 8.1.6 Reliability Specifications .....................................................................................................................8-4 8.1.7 Environmental Specifications ..............................................................................................................8-4 8.1.8 Mechanical Data of Cabinet.................................................................................................................8-5 8.1.9 Power Supply.......................................................................................................................................8-6 8.1.10 Power Consumption...........................................................................................................................8-6 8.2 EMC Specifications ......................................................................................................................................8-8 8.2.1 Electromagnetic Interference Specifications........................................................................................8-8 8.2.2 Electromagnetic Susceptibility Specifications .....................................................................................8-8 8.3 Environmental Requirements ...................................................................................................................... 8-11 8.3.1 Storage Environment.......................................................................................................................... 8-11 8.3.2 Transportation Environment ..............................................................................................................8-13 8.3.3 Running Environment ........................................................................................................................8-15
9 Compliant Specifications .........................................................................................................9-1

9.1 3GPP Specifications ......................................................................................................................................9-2 9.2 ITU-T Specifications.....................................................................................................................................9-6
Issue 03 (2006-09-30)
iii
Contents
9.3 Other Technical Specifications......................................................................................................................9-9
10 Installation...............................................................................................................................10-1
iv
Issue 03 (2006-09-30)
Figures
Figures
Figure 1-1 Mobile softswitch solution of Huawei..............................................................................................1-2 Figure 1-2 MSOFTX3000 in 2G/3G integration networking ...........................................................................1-13 Figure 2-1 Appearance of an MSOFTX3000 cabinet.........................................................................................2-2 Figure 2-2 Overall structure of the OSTA subrack .............................................................................................2-3 Figure 2-3 Hardware structure of the MSOFTX3000 ........................................................................................2-4 Figure 2-4 Logical structure of the MSOFTX3000 hardware ............................................................................2-6 Figure 2-5 Software structure of the MSOFTX3000..........................................................................................2-8 Figure 2-6 Relationship between BAM server software, operating system, and database ............................... 2-11 Figure 2-7 Configuration of MSOFTX3000 cabinets ......................................................................................2-12 Figure 2-8 Expansion configuration of the MSOFTX3000..............................................................................2-13 Figure 3-1 Protocol interfaces provided by the MSOFTX3000 in a mobile network ........................................3-5 Figure 3-2 Protocol interfaces provided by the MSOFTX3000 in an IMS network. .........................................3-7 Figure 4-1 Network structure of the terminal system .........................................................................................4-3 Figure 5-1 Networking model of Overlay network mode ................................................................................5-21 Figure 5-2 Networking model of target network mode ....................................................................................5-22 Figure 5-3 Mini-A-Flex networking.................................................................................................................5-32 Figure 5-4 Mini-Iu-Flex networking ................................................................................................................5-33 Figure 5-5 Iu-Flex network architecture...........................................................................................................5-34 Figure 5-6 Ordinary encoding and decoding speech operation ........................................................................5-37 Figure 5-7 Encoding and decoding speech operation after activating TFO .....................................................5-37 Figure 5-8 Encoding and decoding speech operation after activating TrFO ....................................................5-38 Figure 6-1 MSC networking...............................................................................................................................6-2 Figure 6-2 GMSC networking............................................................................................................................6-5 Figure 6-3 TMSC networking ............................................................................................................................6-6 Figure 6-4 1+1 backup networking ....................................................................................................................6-8 Figure 6-5 1+1 mutual assistance networking....................................................................................................6-8
Issue 03 (2006-09-30)
Figures
Figure 6-6 N+1 backup networking (N = 2).......................................................................................................6-9 Figure 6-7 N+1 mutual assistance networking (N = 2) ....................................................................................6-10 Figure 6-8 MA networking............................................................................................................................... 6-11 Figure 6-9 Networking structure for Huawei IMS interworking with the CS domain .....................................6-12 Figure 6-10 Networking structure for Huawei NGN interworking with the CS domain..................................6-13 Figure 6-11 Evolution strategy of Huawei mobile core network......................................................................6-14 Figure 6-12 Solution of Huawei R5 .................................................................................................................6-14 Figure 6-13 Multi-area commercial network of company A ............................................................................6-16 Figure 6-14 Dual-homing commercial network of company B........................................................................6-17
vi
Issue 03 (2006-09-30)
Tables
Tables
Table 1-1 Functions of the MSC server and the MGW ......................................................................................1-3 Table 1-2 Benefits offered by softswitch networks.............................................................................................1-5 Table 1-3 Full names of protocols ......................................................................................................................1-7 Table 1-4 Abbreviations and their full names .....................................................................................................1-8 Table 1-5 Protocols, links, and signaling modes supported and interfaces provided by the MSOFTX3000 to interwork with other NEs ....................................................................................................................................1-9 Table 1-6 Measures in the design of the MSOFTX3000 .................................................................................. 1-11 Table 3-1 Numbers and functions of physical interfaces ....................................................................................3-2 Table 3-2 Specifications of FE electrical interfaces............................................................................................3-3 Table 3-3 Specifications of E1 interfaces ...........................................................................................................3-3 Table 3-4 Specifications of clock interfaces .......................................................................................................3-4 Table 3-5 Interfaces and protocols supported by the MSOFTX3000 in a mobile network ................................3-5 Table 3-6 Interfaces and protocols supported by the MSOFTX3000 in an IMS network. .................................3-7 Table 3-7 Signaling and protocols supported by the MSOFTX3000..................................................................3-9 Table 5-1 Original CDR generation scenario....................................................................................................5-16 Table 5-2 List of the new features supported by the MSOFTX3000 ................................................................5-22 Table 7-1 Security authentications......................................................................................................................7-7 Table 8-1 System capacity ..................................................................................................................................8-2 Table 8-2 Reference traffic model ......................................................................................................................8-2 Table 8-3 System processing capability..............................................................................................................8-2 Table 8-4 Protocol processing capability............................................................................................................8-3 Table 8-5 CDR processing capability .................................................................................................................8-3 Table 8-6 Number analysis capability ................................................................................................................8-4 Table 8-7 Reliability specifications ....................................................................................................................8-4 Table 8-8 Environmental adaptation (long term operation)................................................................................8-4 Table 8-9 Noise specifications............................................................................................................................8-5 Table 8-10 Mechanical data of cabinet ...............................................................................................................8-5
Issue 03 (2006-09-30)
vii
Tables
HUAWEI MSOFTX3000 Product Description Table 8-11 Power supply ....................................................................................................................................8-6 Table 8-12 Overall power consumption..............................................................................................................8-6 Table 8-13 Power consumption (functional units)..............................................................................................8-7 Table 8-14 CE specifications through the 48 V power supply port ..................................................................8-8 Table 8-15 RE specifications ..............................................................................................................................8-8 Table 8-16 CS specifications ..............................................................................................................................8-9 Table 8-17 RS specifications ..............................................................................................................................8-9 Table 8-18 ESD specifications............................................................................................................................8-9 Table 8-19 EFT specifications ..........................................................................................................................8-10 Table 8-20 Surge specifications ........................................................................................................................8-10 Table 8-21 Climate environment requirements (for storage)............................................................................ 8-11 Table 8-22 Density requirements for mechanically active materials (for storage) ........................................... 8-11 Table 8-23 Density requirements for chemically active materials (for storage) ...............................................8-12 Table 8-24 Mechanical stress requirements (for storage) .................................................................................8-12 Table 8-25 Waterproof requirements ................................................................................................................8-13 Table 8-26 Climate environment requirements (for transportation) .................................................................8-13 Table 8-27 Density requirements for mechanically active materials (for transportation).................................8-14 Table 8-28 Density requirements for chemically active materials (for transportation).....................................8-14 Table 8-29 Mechanical stress requirements (for transportation).......................................................................8-14 Table 8-30 Temperature and humidity requirements ........................................................................................8-15 Table 8-31 Other climate environment requirements .......................................................................................8-16 Table 8-32 Density requirements for mechanically active materials (for equipment running).........................8-16 Table 8-33 Density requirements for chemically active materials (for equipment running).............................8-16 Table 8-34 Mechanical stress requirements (for equipment running)...............................................................8-17 Table 9-1 The compliant 3GPP R4 specifications (2004.12) of the MSOFTX3000...........................................9-2 Table 9-2 The compliant ITU-T specifications of the MSOFTX3000................................................................9-6 Table 9-3 The other technical specifications.......................................................................................................9-9
viii
Issue 03 (2006-09-30)
1 Introduction
1
About This Chapter
The following table lists the contents of this chapter. Title 1.1 Product Orientation 1.2 Product Features Description
Introduction
This section describes the mobile softswitch solution of Huawei and the orientation of the MSOFTX3000. This section describes features of the MSOFTX3000.
Issue 03 (2006-09-30)
1-1
1 Introduction
1.1 Product Orientation

1.1.1 Introduction to the Mobile Softswitch Solution of Huawei
By separating the bearer from the control, a networking model with the softswitch technology as the core can use bearer networks such as the IP and TDM. This is a key feature of the softswitch technology. At present, the softswitch technology is chosen by most carriers to build mobile core networks (CNs). By using distributed networking mode and IP bearers, mobile softswitches offer carriers the following benefits:
! !
Reducing operating costs by improving the efficiency of network transmission Retaining the value of the carriers' investment by providing seamless upgrades from one model to another as the subscriber base and traffic increases
The mobile softswitch solution of Huawei is based on the networking requirements and network features of carriers. It provides a 2G or 3G integration networking scheme that is easy to maintain and manage. The solution supports networking schemes of the GSM, 3GPP, R99, 3GPP R4, and 3GPP R5. Figure 1-1 shows a typical networking diagram of mobile softswitch solution of Huawei for 3GPP R4: Figure 1-1 Mobile softswitch solution of Huawei
Bearer Signaling MSC Server (MSOFTX3000) CN GMSC Server (MSOFTX3000) Other Networks
BSS 2G Access PSTN 3G Access MGW (UMG8900) MGW (UMG8900)
CS PS
HLR UTRAN SGSN GGSN Internet
GGSN: Gateway GPRS Support Node MSC Server: Mobile Switching Center Server SGSN: Serving GPRS Support Node UTRAN: UMTS Terrestrial Radio Access Network
HLR: Home Location Register CN: Core Network PS: Packet Switched domain BSS: Base Station Subsystem
MGW: Media Gateway CS: Circuit Switched domain PSTN: Public Switched Telephone Network
1-2
Issue 03 (2006-09-30)
1 Introduction
Based on the upgrade strategy of the CS domain of the mobile CN and the need for an all IP network, the MSC in the GSM and 3GPP R99 is divided into two parts (the MSC server and the MGW) in the 3GPP R4 and later versions. As shown in Table 1-1, the MSC server and the MGW perform different functions. Table 1-1 Functions of the MSC server and the MGW Network Element MSC server Function It connects with the BSS or the UTRAN and performs such control functions of the CS domain as:
! ! ! ! ! !
Product The MSOFTX3000 provided by Huawei serves as an MSC server, as shown in Figure 1-1.
Mobility management Security management Handover processing Signaling processing Call processing Subscriber data management (function of the VLR)
MGW
It is the endpoint of the MSOFTX3000's connection with the PSTN or the PLMN, and performs such functions as:
! ! ! ! !
The UMG8900 provided by Huawei serves as an MGW, as shown in Figure 1-1.
Media transformation Bearer management Coding/Decoding of digital signals Echo cancellation Conference bridging
Note: PLMN = Public Land Mobile Network
1.1.2 Features of Huawei's Mobile Softswitch Solution

Support for 2G/3G Integration
The carriers who have owned or will own both 2G and 3G networks must consider how to retain the value of their investment in the 2G network when expanding it. Huawei offers a combined GSM/UMTS solution to help carriers solve the problem. This solution supports both BSS and UTRAN access, so as to provide services for both 2G and 3G subscribers at the same time. Both 2G and 3G networks can share equipment resources, so this solution can offer the following benefits:
! ! ! !
Reducing the capital expenditure (CAPEX) of carriers Improving subscribers' degree of satisfaction Unifying network operation Simplifying network topology
Issue 03 (2006-09-30)
1-3
1 Introduction
!
Saving network resources
This solution can be upgraded online and configured dynamically during the evolution from the GSM to the UMTS, so the network can be smoothly upgraded.
High Efficiency
In the mobile softswitch solution of Huawei, MGWs can be located in many cities, and IP bearers can be used between MGWs. This simplifies the network interconnection topology and network management, and saves transmission resources for carriers. The softswitch equipment of Huawei enjoys:
! ! !
High integration Large capacity Powerful processing capability
It saves the space of equipment room and electricity costs. Carriers can focus O&M (O&M) on a small quantity of softswitch offices and hence reduce the network O&M costs. On the basis of a more open architecture and distributed software technology, the softswitch system of Huawei helps you develop services quickly. Statistics shows that the development cycle of services based on softswitch networks is 50% shorter than that based on conventional switching equipment.
Highly Reliable
The dual homing solution provided by Huawei enables redundancy function (such as 1+1 mutual aid and N +1 backup) for MSC Servers. It supports the Mini-Flex scheme and the Iu-Flex scheme, as well as multiple backup modes of HLR. Based on specific conditions, Huawei is able to use these modes flexibly. With the call access control method, Huawei ensures that the conversation is not affected when the IP bearer network is congested. The advanced traffic control mechanism ensures that the network remains highly reliable when the traffic is heavy.
Smooth Evolution
Fixed mobile convergence (FMC) is the trend of network development. In this process, it is important to integrate the equipment of fixed and mobile networks. At present, Huawei provides a number of devices that can be used in both fixed and mobile networks and provides integrated services. In the future, the fixed and mobile networks can be integrated through the IMS subsystem at the network level. Huawei softswitch equipment MSC Server and MGW can be evolved to equipment in IMS smoothly in the future. This saves the CAPEX for carriers.
More Benefits
Compared with conventional switched circuit network (SCNs), the carriers the benefits listed in Table 1-2: softswitch networks offer
1-4
Issue 03 (2006-09-30)
1 Introduction
Table 1-2 Benefits offered by softswitch networks Benefit The CAPEX is lowered. Description In contrast to the closed structure of the conventional SCN, a softswitch network uses the following to provide services:
! ! !
A control core Open interfaces Universal protocols
It helps the carriers to build an open and low cost network and improve the speed of service deployment. The softswitch technology also enables smooth migration of 2G, 3G and IMS networks. This decreases the CAPEX for network migration. The centralized softswitch equipment with large capacity has higher equipment resource utilization in the following aspects:
!
The distributed media gateway reduces alternative routes in local transmission.
The flat networking mode does not require the construction of tandem layer. IP bearer cuts down the transmission costs for the whole network.
Statistics shows that the CAPEX of a softswitch network is 20% to 30% lower than that of a conventional SCN. The OPEX is lowered. Compared with the conventional switching equipment, the softswitch equipment enjoys:
! ! !
Much better processing capability A higher level of integration Lower power consumption
This helps decrease 60% to 70% of the equipment room area and 30% power consumption. With the bearer separated from the control, the core of the softswitch network can be located and managed in a centralized manner. This reduces the network O&M costs. The security of the network is enhanced. The softswitch network uses network-level reliability mechanisms such as the following:
! !
Dual homing Iu-Flex
This makes the network more reliable. The dual homing mode realizes the backup of softswitch equipment. When a softswitch is faulty, the system can smoothly switch the service to the standby softswitch. This ensures that the service is not affected. The Iu-Flex technology enables networks to share multiple CN equipment nodes. Hence, services are not affected when a single MGW is faulty and the network is more secure.
Issue 03 (2006-09-30)
1-5
1 Introduction
Benefit New services can be offered quickly and easily.
Description New services can be provided on the softswitch layer without affecting MGW in the bearer layer. Hence, the softswitch network allows users to develop and offer new services more flexibly and quickly:
!
The open network structure shortens the cycle of developing services. Centralized service management makes service deployment easy. The network supports SIP. This enhances the capability of providing multimedia services.
Note: CAPEX = Capital Expenditure; OPEX = Operational Expenditure; SIP = Session Initiation Protocol
1.1.3 Introduction to the MSOFTX3000

Overview
The HUAWEI MSOFTX3000 Mobile SoftSwitch Center (called MSOFTX3000 in this manual) is a large capacity mobile softswitch developed by Huawei. It provides:
! ! !
Advanced software and hardware technologies Dynamic service provision capabilities Powerful networking functions
The MSOFTX3000 serves as the MSC server at the control layer of the CS domain in the WCDMA core network. It implements functions such as call control and connection management for voice and data services based on IP or TDM. By supporting protocols and functions of both the GSM and the WCDMA, the MSOFTX3000 can upgrade from the GSM to the WCDMA. With the bearer separated from the control, the MSOFTX3000 can function as the core of a network with different bearer networks such as IP and TDM. During the upgrade of the CN of the mobile network (GSM -> 3GPP R99 -> 3GPP R4 -> 3GPP R5), the MSOFTX3000 can serve as many network elements (NEs), including the following:
! ! ! ! !
VMSC Server/VLR GMSC Server TMSC Server MSC/SSP MGCF
VMSC Server/VLR
The MSOFTX3000 supports many protocols, including H.248, BICC, CAP, BSSAP, RANAP, MAP, ISUP, TUP, and BSSAP+. It can provide the function of a VMSC server and a VLR. When connected with the UMG8900 and the shared interworking function (SIWF) of Huawei, the MSOFTX3000 supports the BSS/UTRAN access and can serve as a 2G VMSC, a 3G VMSC, or a 2G/3G integrated VMSC.
1-6
Issue 03 (2006-09-30)
1 Introduction
Table 1-3 lists the protocols and their full names. Table 1-3 Full names of protocols Abbreviation BICC CAP BSSAP RANAP MAP ISUP TUP BSSAP+ Full Name Bearer Independent Call Control Protocol CAMEL Application Part Base Station Subsystem Application Part Radio Access Network Application Part Mobile Application Part Integrated Services Digital Network User Part Telephone User Part Base Station Subsystem Application Part+
When the MSOFTX3000, UMG8900, and SIWF of Huawei are used together in the GSM or 3GPP R99, they are called the MSC9880.
GMSC Server
The GMSC server is a node between the CS domain of the CN and external networks. the GMSC server, a mobile network can exchange signaling with the following:
! ! !
With
PSTN Integrated services digital network (ISDN) Other PLMNs
The GMSC server performs important functions, including:

! ! !
Serving as a mobile gateway office between networks Analyzing routing Implementing call connection and settlement between networks
The MSOFTX3000 supports H.248, MAP, and ISUP. It provides functions such as:
! ! ! !
Black and white lists Call authentication Call interception Storage of a large number of CDRs
When connected with the UMG8900 of Huawei, the MSOFTX3000 can serve as a GMSC server.
TMSC Server
As a toll tandem office, the TMSC server performs the following functions:
Issue 03 (2006-09-30)
1-7
1 Introduction
! !
Routing analysis Intra-network toll call convergence
In applications, a layered structure is used in a large network. The MSOFTX3000 supports H.248, ISUP, and BICC. When connected with the UMG8900 of Huawei, the MSOFTX3000 can serve as a TMSC server. It provides a large number of TDM trunks or IP bearer channels.
MSC/SSP
The MSOFTX3000 can provide the functions of a gsmSSF. It supports CAP, CAMEL 1, CAMEL 2, and CAMEL 3. In the target network mode, the MSOFTX3000 can serve as an SSP, an auxiliary SSP, or an IP of the mobile IN. The MSOFTX3000 can also support the Overlay network mode and trigger mobile IN services based on number segments. Table 1-4 lists the abbreviations and their full names: Table 1-4 Abbreviations and their full names Abbreviation SSF CAP INAP CAMEL SSP IP IN Full Name Service Switching Function CAMEL Application Part Base Station Subsystem Application Part Customized Applications for Mobile Network Enhanced Logic Service Switching Point Intelligent Peripheral Intelligent Network
MGCF
The MSOFTX3000 supports H.248, SIP, ISUP, and BICC. When connected with the UMG8900 of Huawei, the MSOFTX3000 can serve as a media gateway control function (MGCF). It enables the interworking between the IP multimedia subsystem (IMS) and the CS domain.
1.2 Product Features

1.2.1 Dynamic Service Provision Capabilities
The MSOFTX3000 supports protocols and functions of both the GSM and the WCDMA. It can serve as many types of NEs. Therefore, the MSOFTX3000 can provide various services, including:
!
Basic services: voice, SMS, GSM fax, GSM bearer, and UMTS bearer
1-8
Issue 03 (2006-09-30)

!
1 Introduction
Supplementary services: call forwarding, call restriction, number identification, call completion, multiparty, unstructured data transfer, closed user group, explicit call transfer, and enhanced multi level precedence and preemption Operator determined barring services: barring of all outgoing calls, barring of outgoing international calls, barring of outgoing international calls except those directed to the home PLMN country, barring of all incoming calls, barring of supplementary management, and barring of incoming calls when roaming outside home PLMN country IN services: prepaid and mobile virtual private network Value-added service: multimedia, mobile location, ring back tone, equal access, charging based on time and area, enhanced roaming restriction, alternate line service, and voice and video double number
! !
1.2.2 Powerful and Flexible Networking Capabilities

The MSOFTX3000 provides open and standard interfaces. It supports GSM, 3GPP R99, and 3GPP R4 networking, and allows smooth upgrades and expansion. Table 1-5 lists the protocols, links, and signaling modes supported and interfaces provided by the MSOFTX3000 to interwork with other NEs: Table 1-5 Protocols, links, and signaling modes supported and interfaces provided by the MSOFTX3000 to interwork with other NEs Protocol, Link and Signaling Mode H.248 BSSAP RANAP MTP, TUP, and ISUP MAP CAP SIP BICC BSSAP+ SIGTRAN (M2UA, M3UA, and IUA) R2 DSS1 Gs C, D, E, G, and Lg Interface Interworking and Benefits
Mc A Iu
Interconnecting with the MGW Interconnecting with the BSC when the MSOFTX3000 is connected with the MGW Interconnecting with the RNC in a WCDMA network when the MSOFTX3000 is connected with the MGW Interconnecting with the STP and PSTN switches Interconnecting with the HLR, VLR, MSC, SMC, and GMLC in a GSM or WCDMA network Interconnecting with the SCP in an IN Interconnecting with the IMS or NGN Interconnecting with the MSC server Interconnecting with the SGSN in the PS domain Interconnecting with the SG and the MGW with built-in SG function
Interconnecting with PSTN switches that support only R2 Interconnecting with the PBX
Issue 03 (2006-09-30)
1-9
1 Introduction
Protocol, Link and Signaling Mode Supporting virtual multiple signaling point codes TDM 2-Mbit/s links ATM 2-Mbit/s links
Interface
Interworking and Benefits
Meeting the requirements of a large number of trunks in the case of GMSC networking Improving reliability of networking by using load sharing networking mode between virtual multiple signaling points and remote signaling points Improving the traffic capacity between two signaling points, simplifying signaling networking, and lowering network construction costs Supporting ATM bearer through E1 demultiplexing, providing flexible networking schemes, reusing existing equipment and transmission resources, and reducing network construction costs Mc and Iu Making networking more flexible and networks more adaptive to ground conditions Interconnecting with the billing center Interconnecting with the network management center (NMC)
Satellite transmission links FTP and FTAM MML
1.2.3 Large Capacity and High Integration

The MSOFTX3000 provides advanced hardware technology, featuring modular hardware structure, large capacity, and high integration:
! ! !
All boards use advanced integrated circuits such as the ASIC, PLD, and FPGA. This simplifies the MSOFTX3000 and improves the integration of the system. In full configuration, the MSOFTX3000 can support up to 1.8 million subscribers (serving as a VMSC) or 450 thousand TDM circuits (serving as a TMSC). The MSOFTX3000 in full configuration requires only three cabinets, thus occupying fewer areas. In addition, the power consumption of the MSOFTX3000 is low (less than six kW).
1.2.4 Powerful Processing Capabilities

With a distributed hardware structure, high performance chips, high speed buses, and high speed PowerPC processors, the MSOFTX3000 provides powerful processing capabilities (the following data is based on the full configuration):
! ! !
When serving as a VMSC server, the MSOFTX3000 supports up to 2700k BHCA. When serving as a GMSC server, the MSOFTX3000 supports up to 7200k BHCA. When serving as a TMSC server, the MSOFTX3000 supports up to 9000k BHCA.
1-10
Issue 03 (2006-09-30)
1 Introduction
1.2.5 Highly Reliable

The MSOFTX3000 is highly reliable because it takes measures in designing the following:
! ! !
Hardware Software Billing system
Table 1-6 lists details: Table 1-6 Measures in the design of the MSOFTX3000 Item Hardware design Measure
!
Active/standby backup, load sharing, and redundancy techniques for boards Optimized fault detection and isolation techniques which improve the maintainability of the system Dual connections for key parts and dual plane and mesh connection design which ensure that the system is not affected when a single node is faulty
Software design Billing
Layered modular structures which enable the protection, fault tolerance, and fault monitoring functions of the software The billing gateway of the MSOFTX3000 is the iGWB of Huawei. The iGWB uses dual system hot backup and Hot RAID5 hard disk array. This enables dual backup of billing data and mass storage.
The reliability assessment method generally adopted shows the following:

! ! !
The MTBF of the MSOFTX3000 reaches 24 years (in full configuration). The MTBF of the MSOFTX3000 reaches 42 years (when configured with only one subrack). The MTTR of the MSOFTX3000 is smaller than one hour (not considering the preparation time).
MTBF is short for Mean Time Between Failure. MTTR is short for Mean Time To Repair.
1.2.6 Capabilities for Smooth Expansion

The designs of the hardware and the system processing function of the MSOFTX3000 take future network expansion into account. The MSOFTX3000 supports smooth expansion of networks:
!
Hardware design: The MSOFTX3000 uses the open standards telecom architecture (OSTA) platform as the hardware platform. The OSTZ provides modular overlay structure. The number of subracks ranges from 1 to 10 and the subracks are connected through LAN Switches. This supports smooth expansion. System processing function design: The MSOFTX3000 reserves spaces for future service expansion.
Issue 03 (2006-09-30)
1-11
1 Introduction
1.2.7 Advanced Charging Capabilities

The MSOFTX3000 supports the charging of many services, including the following:
! ! ! ! !
Voice service Data service Video service SMS Supplementary services
With over 40 types of original CDRs, the MSOFTX3000 allows various charging. The features of charging of the MSOFTX3000 are listed as follows:
!
Supporting CDR types such as mobile-originated call ticket, mobile-terminated call ticket, call forwarding ticket, transit ticket, mobile-originated SMS ticket, mobile-terminated SMS ticket, outgoing gateway exchange ticket, incoming gateway exchange ticket, roaming ticket, supplementary service ticket, IN mobile-originated call ticket, IN mobile-terminated call ticket, IN call forwarding ticket, and IN pickup ticket Supporting the storage of CDRs based on modules, services, or time Supporting standard FTP and FTAM charging interfaces Supporting a charging accuracy of 10 milliseconds Supporting the generation of intermediate CDRs Supporting the call restriction function in the case of CDR pool threshold crossing Supporting hot billing Supporting Advice of Charge Supporting IN announcement charging
! ! ! ! ! ! ! !
1.2.8 Excellent Performance Measurement Function

The MSOFTX3000 provides performance measurement (PM) functions. It supports many PM entities and tasks. It uses tables and figures to display data in real time and report service loading and system running status. The performance measurement features of the MSOFTX3000 are listed as follows:
!
Supporting the measurement and record of traffic (up to 400 tasks and 3,000 short or 1,000 long subtasks can be run at the same time, and up to 3,000 measurement objects are supported) Predefining measurement items and time, auto starting and stopping measurement at specified time on specified dates, canceling predefined items, and measuring one or many items based on the actual requirements Supporting at least four measurement periods every day for predefined measurement items and auto exporting measurement results to terminals and network management centers Supporting the measurement of the number of times that a supplementary service is activated or cancelled Supporting the performance measurement of the IP port traffic of the softswitch system
! !
1-12
Issue 03 (2006-09-30)
1 Introduction
1.2.9 Convenient and Useful O&M Function

The MSOFTX3000 provides convenient and useful O&M functions:
!
The MSOFTX3000 provides many O&M modes. The terminal system of the MSOFTX3000 is based on the Client/Server distributed structure. It provides several maintenance modes such as the graphic user interface (GUI) and man machine language (MML) commands. Local and remote clients can access the MSOFTX3000 at the same time. Carriers can set up management network based on network components, management requirements and investment scale. The MSOFTX3000 provides the GUI with a special navigation tree. The GUI is visual, which minimizes the need for memory. The GUI features graphic topology views of network components and device panel views. The MSOFTX3000 provides call tracing, signaling tracing, and interface tracing functions, as well as message explanation function. The trace viewer tool of the MSOFTX3000 allows operators to analyze and locate faults easily. The MSOFTX3000 supports the real time fault management function based on H.248. The system receives and displays fault reports of network equipment in real time. This helps operators to find the source of a fault quickly and take measures to restore the services. The MSOFTX3000 supports online software patches, online commissioning, remote maintenance, and dynamic data setting.
1.2.10 Support for 2G/3G Integration

The MSOFTX3000 supports mixed networking and interworking of GSM, 3GPP R99, 3GPP R4, and 3GPP R5 networks. That is, the MSOFTX3000 supports the 2G/3G integration networking. It can connect with the BSS and UTRAN and provide services for 2G and 3G subscribers at the same time. Figure 1-2 shows a typical networking diagram: Figure 1-2 MSOFTX3000 in 2G/3G integration networking
MSC MSOFTX3000 A GMSC MSOFTX3000
BSS
TUP/ISUP BICC
TUP/ISUP
PSTN/ PLMN
Iu-CS UMG8900 UTRAN UMG8900
In the 2G/3G integration networking structure, the MSOFTX3000 and the UMG8900 can be used as an MSC (GMSC or TMSC) function entity:
Issue 03 (2006-09-30)
1-13
1 Introduction
!
The MSC provides A and Iu-CS interfaces to support the access of GSM and UMTS subscribers. One MSOFTX3000 can be connected with many UMG8900s. The UMG8900 can be placed remotely. The MSOFTX3000 allows subscribers to hand over between GSM and UMTS systems. The MSOFTX3000 enable the network to control the access of subscribers. GSM and UMTS subscribers can access the MSOFTX3000 at the same time. This makes network upgrades smooth and services of original subscribers of the network are not affected by upgrades.
! !
1-14
Issue 03 (2006-09-30)
2 System Structure
2
About This Chapter
The following table lists the contents of this chapter. Title 2.1 Hardware Structure 2.2 Software Structure 2.3 Capacity Expansion Description
System Structure
This section describes the physical and logical structures of the MSOFTX3000 hardware. This section describes the logical structure of the MSOFTX3000 software. This section describes the normal and expanded configuration of the MSOFTX3000 cabinets.
Issue 03 (2006-09-30)
2-1
2 System Structure
2.1 Hardware Structure

2.1.1 Appearance
The MSOFTX3000 is composed of the N68-22 cabinets of Huawei. Figure 2-1 shows the appearance of an N68-22 cabinet: Figure 2-1 Appearance of an MSOFTX3000 cabinet
The N68-22 cabinet is a 19-inch standard cabinet that complies with the following international standards:
! ! !
IEC60297-1, Dimensions of mechanical structures of the 482.6 mm (19 in) series Part 1:Panels and racks IEC60297-2, Dimensions of mechanical structures of the 482.6 mm (19 in) series Part 2:Cabinets and pitches of rack structures IEC60297-3, Dimensions of mechanical structures of the 482.6 mm (19 in) series Part 3:Subracks and associated plug-in units
2.1.2 Physical Structure

Introduction to OSTA Platform
The OSTA platform is used in the MSOFTX3000 as the hardware platform. The platform uses the Ethernet bus as the bus of the backplane. This ensures high reliability of the
2-2
Issue 03 (2006-09-30)
2 System Structure
MSOFTX3000. As a result, the MSOFTX3000 can exchange and transfer data packets of variable lengths. The OSTA platform is structured in a standard subrack, which is 19 inches wide and 9U high. Front boards and back boards are installed, as shown in Figure 2-2. Figure 2-2 Overall structure of the OSTA subrack
(2) (3) (2) (1)
(4)
(5)
(6)
(7)
(8)
(7)
(9)
(1)
(1) Power boards (4) Back boards (7) Service boards
(2) Interface boards (5) Backplane (8) System management boards
(3) Ethernet communication boards (6) Front boards (9) Alarm board
In the OSTA subrack, the front boards are:

! ! !
Service boards System management boards Alarm boards
In the OSTA subrack, the back boards are:

! !
Interface boards Ethernet communication boards
Power boards can be installed either at the front or at the back. The front and back installation mode separates the functions of the front boards from those of the back boards. The advantages are:
! ! ! ! ! !
Simplifying the board design Unifying the board functions Simplifying the hardware structure Improving reliability of the system Improving versatility of the boards Enhancing flexibility of system configuration
In the MSOFTX3000, all subracks share the same hardware structure. Each subrack is designed in the width of 21 standard board slots. The following boards must be configured in the fixed slots of the subrack, occupying the width of nine standard board slots:
! !
System management boards Ethernet communication boards
Issue 03 (2006-09-30)
2-3
2 System Structure
! !
Alarm boards Power boards (each occupies two standard slots)
The remaining 12 slots are used for service boards and interface boards.
Hardware Structure of the MSOFTX3000

The MSOFTX3000 hardware mainly consists of three parts:
! ! !
OSTA subrack BAM iGWB (it is the billing gateway)
BAM is short for Back Administration Module. The OSTA subracks form the host of the MSOFTX3000. The host provides the functions of signaling and service processing and resource management. The BAM, the local maintenance terminals (LMTs) and the iGWB build up the background of the MSOFTX3000. The background offers the OAM functions and CDR management. Figure 2-3 shows the hardware structure of the MSOFTX3000. Figure 2-3 Hardware structure of the MSOFTX3000
FE FE
To Billing Center
0# Subrack
FE
Active iGWB To Billing Center
1# Subrack
0# LAN Switch
2FE
Standby iGWB
1# LAN Switch 2# Subrack
BAM Background LAN Switch To NMC
9# Subrack Host
EWS
LMT LMT LMT
FE: Fast Ethernet EWS: Emergency Workstation
2 x FE: Two FE cables
LMT: Local Maintenance Terminal
2-4
Issue 03 (2006-09-30)
2 System Structure
Inter-Device Communication
The inter-device communication of the MSOFTX3000 system is as follows:
! !
The subracks communicate with each other through the internal Ethernet. Each subrack is connected to LAN Switches 0 and 1 through two network cables. The subracks communicate with the BAM and iGWB through the internal Ethernet. The BAM and the iGWB are connected to the LAN Switches 0 and 1 through two network cables. The BAM and the iGWB are each connected to a LAN Switch through a network cable. The LMTs interact with the BAM and the iGWB through TCP/IP in the client/server mode.
System Capacity
The system capacity is determined by the number of service processing subracks which ranges from 1 to 10 in the MSOFTX3000. Hence, the MSOFTX3000 can smoothly expand its capacity.
Complying With International Standards

The OSTA subracks and boards comply with the following international standards:
! ! !
IEEE1101.1-1991, IEEE stand for Mechanical Core Specification for Microcomputers Using IEC 60603-2 connectors IEEE1101.10-1996, IEEE stand for Additional Mechanical Core Specification for Microcomputers Using IEEE Std 1101.1-1991 Equipment Practice IEEE1101.11-1998, IEEE stand for Mechanical Rear Plug-in Units Specification for Microcomputers Using IEEE 1101.10 Equipment Practice
2.1.3 Logical Structure

The logical structure of the MSOFTX3000 hardware system includes five modules:
! ! ! ! !
System support module (SSM) Interface module (IM) Signaling lower-layer processing module (SLLPM) Service processing module (SPM) Operation & maintenance module (OMM)
Figure 2-4 shows the logical structure of the MSOFTX3000 hardware.
Issue 03 (2006-09-30)
2-5
2 System Structure
Figure 2-4 Logical structure of the MSOFTX3000 hardware

Interface Module BITS WCKI WEPI Signaling Lower-Layer Processing Module CPC Service Processing Module
E1/T1 Interface ATM-2M Interface FE Interface
WCCU WVDB WCDB
WEPI/ WEAM WBFI/ WIFM WBSG
WMGC
LAN bus OSTAbus NMS WS BC BAM WSIU/WSMU iGWB Operation & Maintenance Module System Support Module
System Support Module

The SSM implements such functions as follows:
! ! !
Software and data loading Device management and maintenance Inter-board communications
It comprises the following units:

! ! ! !
System management unit (WSMU) System interface unit (WSIU) Hot-swap and control unit (WHSC) Core LAN Switch
The WSMU is the main control board of a subrack. Through the system buses and the serial port, the WSMU is responsible for the following for all the devices in the system:
! ! !
Loading control Data configuration Working status control
The WHSC implements the following functions:

! ! !
Bridge connection between the left shared resource bus and the right one Board hot swappability control Intra-subrack LAN bus switching
2-6
Issue 03 (2006-09-30)
2 System Structure
The signaling traffic streams are formed through the LAN bus provided by the WHSC. The WHSC is not configured with a CPU. Therefore, the WHSC is directly configured and maintained by the WSMU through the Ethernet bus. The core LAN Switch implements the following functions:
! !
Interconnection of multiple subracks Connection between these subracks and management devices
Interface Module
The IM provides various physical interfaces to meet the system networking demands, including:
!
Narrowband interface: The E1_pool interface unit (WEPI) provides eight E1/T1 interfaces to realize the framing and line interfacing function (MTP1 function). The WEPI interworks with the MTP2 processing unit WCPC (subboard of the WCSU) of the signaling lower layer processing module through internal HW. ATM-2M interface: The WEPI provides eight E1/T1 interfaces and two 8-Mbit/s HW signal cables to connect with the WEAM. The WEAM segments and reassembles the ATM cells in the data streams, and transfers signaling to the WBSG through internal LAN bus. FE interface: The WIFM provides the 100-Mbit/s Ethernet electrical interface through configuring the FEP subboard and WBFI. It implements distributing and converging broadband signaling information streams, and distributes them to the specified processing unit based on the IP address and the port number. The narrowband signaling requires clock synchronization. The MSOFTX3000 provides two kinds of clock sources, BITS and E1, and the WCKI provides external interfaces.
Signaling Lower-Layer Processing Module

The SLLPM offers the lower layer protocol processing function. It includes SS7 MTP2 processing unit (WCPC) and SCTP processing unit (WBSG):
!
The WCPC processes SS7 MTP2 over narrowband E1 and communicates with the service processing unit (WCSU) through the internal bus. The WCPC is a subboard of the WCSU. The WBSG handles lower layer signaling processing over IP and ATM, and distributes them to the upper layer service processing board.
Service Processing Module

The SPM is composed of the service processing unit (WCCU/WCSU), central database unit (WCDB), VLR database unit (WVDB) and media gateway control unit (WMGC):
!
The WCCU processes the signaling protocols on Layer 3 or a higher layer (such as MTP3, M3UA, ISUP, SCCP, TCAP, MAP and CAP) necessary for service features. It also implements call control on the application layer and processes intelligent CAMEL services. In this system, two WCPCs pinched on the WCCU make a WCSU. As the central database unit, the WCDB stores centralized resources, such as inter-office trunk resources, local office subscriber data, and gateway capability status. It also provides the call resource query service for the service processing unit. The WVDBis a dynamic database. It provides the funcitons of the VLR. The WMGC controls the H.248 media gateways.
! !
Issue 03 (2006-09-30)
2-7
2 System Structure
The WCCU/WCSU, WCDB, WBSG, WMGC, WIFM and WAFM are all universal processing boards in the system. They are pinched with different subboards and loaded with different software. They communicate with each other through Ethernet.
Operation & Maintenance Module

The OMM has the following functions:
! ! !
Implementing operation, maintenance and management to the equipment Providing man-machine interfaces to users to implement local O&M Providing interfaces for the Network Management System (NMS)
To provide CDRs, the iGWB must be configured in the MSOFTX3000 to manage CDRs and provide billing interfaces for the billing center.
2.2 Software Structure

2.2.1 Overview
The MSOFTX3000 adopts a distributed software structure. The system distributes software functions and features to boards and servers. You can configure flexibly to meet the actual needs. Based on locations, the MSOFTX3000 software consists of two parts:
! !
Host software BAM software
Figure 2-5 shows the software structure of the MSOFTX3000. Figure 2-5 Software structure of the MSOFTX3000
Host software BAM software
Service processing Database Protocol processing Signaling bearer Device mgmt Middleware
Performance Bill Alarm Maintenance Communication
Performance Bill Alarm Maintenance Exchange Database software
GUI MML
Operating system
Operating system
2-8
Issue 03 (2006-09-30)
2 System Structure
2.2.2 Host Software

The host software runs on boards in the OSTA subracks of the MSOFTX3000. It performs the following functions:
! ! ! ! !
Signaling access and processing Call processing Service control Resource management Charging information generation
Along with the BAM software, the host software can also perform a number of operations on the host in response to commands, including:
! ! ! ! ! !
Data management Equipment management Alarm management Performance measurement Signaling trace CDR management
The host software adopts a layered modular design and consists of the following parts:
! ! !
Operating system Middleware Various application software
Operating system
The operating system of the host software is VxWorks, a kind of real-time software.
Middleware
The MSOFTX3000 adopts the middleware technology (DOPRA_C), so the high level service software becomes irrelevant with the operating system. The use of middleware facilitates the migration of software functions between different platforms. This ensures that new and stable product versions can be quickly released.
Application Software
The application software is the functional part of the MSOFTX3000 software. Loaded with different software, boards can provide different functions. The MSOFTX3000 application software can be divided into five types:
! ! !
The signaling bearer software is configured on WEPI, WIFM, WAFM, and WBSG. It accesses broadband and narrowband signaling, and processes bottom layer protocols. The service processing software is configured on WCCU/WCSU and WMGC. It carries out signaling and call processing, mobility management, and resource management. The database software is configured on the WCDB and WVDB. It manages the data of MSOFTX3000 and dynamic subscriber data.
Issue 03 (2006-09-30)
2-9
2 System Structure
! !
The system support software is configured on the WSMU and WHSC. It carries out system management and device interworking. The O&M software is configured in the WSMU and other boards. It receives instructions from the BAM and returns results.
2.2.3 BAM Software

The BAM software runs on the BAM, the iGWB and the LMTs. Along with the host software, it enables the maintenance staff to implement the following functions:
! ! ! ! ! !
Data management Equipment management Alarm management Performance measurement Signaling tracing CDR management
The BAM software adopts the client/server mode, and consists of four parts:
! ! ! !
BAM server software, installed on the BAM, the server side Emergency workstation software, installed on the emergency workstation, the server side Billing gateway software, installed on the iGWB, the server side LMT software, installed on LMTs, the client side
BAM Server Software

The BAM server software is the core of the terminal OAM software. As an integrated communication server and the database server, the BAM server software can:
! !
Forward the OAM commands from all workstations (WS) to the host. Direct the response or operation results from the host to the workstations.
The BAM server software is based on the Windows 2000 Server. It uses the SQL Server 2000 as the database platform. It provides the functions of the terminal OAM software through multiple parallel service processes, such as:
! ! ! !
Maintenance process Data management process Alarm process Performance measurement process
Figure 2-6 shows the relationship between the BAM server software, the operating system, and the database:
2-10
Issue 03 (2006-09-30)
2 System Structure
Figure 2-6 Relationship between BAM server software, operating system, and database
BAM server software
Applicaiton program layer Operating system layer SQL Server 2000 Windows 2000 Server
Emergency Workstation Software

The EWS software is the same as the BAM server software. The EWS is a backup of the BAM and is not connected with the host at ordinary times. When the BAM is faulty, you can use the EWS to replace the BAM. Switch back to the BAM after the EWS is restored.
Billing Gateway Software

The billing gateway software is the core component of the CDR management system. It runs on the iGWB and performs the following functions:
! !
It stores and backs up CDRs generated by the service processing modules (that is, the WCCUs/WCSUs) of the MSOFTX3000 to the hard disks. It provides billing interfaces to the billing center through FTP or FTAM.
LMT Software
The LMT software runs on the WSs. It connects to the BAM and iGWB servers as a client in the client/server mode, and provides subscribers with graphical terminals based on the MML. WSs can be located locally or remotely. For example, a WS is connected with the BAM server by using the dialup access through a wide area network (WAN). You can use the following maintenance functions on the WSs:
! ! ! ! ! ! !
Data maintenance Equipment management Alarm management Performance measurement Call and signaling tracing CDR management Report functions
Issue 03 (2006-09-30)
2-11
2 System Structure
2.3 Capacity Expansion

2.3.1 Cabinet Configuration
Based on the configurations inside cabinets, the MSOFTX3000 cabinets fall into two categories:
! !
Integrated configuration cabinets Service processing cabinets
The MSOFTX3000 in full configuration has one integrated configuration cabinet and two service processing cabinets, as shown in Figure 2-7: Figure 2-7 Configuration of MSOFTX3000 cabinets
Integrated configuration cabinet
Power distribution subrack (2U)
Service processing cabinet

Power distribution subrack (2U) Expansion subrack (9U)
Service processing cabinet

Power distribution subrack (2U) Expansion subrack (9U)
Basic subrack (9U)
Air deflector (2U)
Air deflector (2U)
Air deflector (2U)
Expansion subrack (9U)
Air deflector (2U) Blank filler panel ( 1U) KVMS (1U) LANSwitch (1U) Cabling trough (1U) LANSwitch (1U) Cabling trough ( 1U) Disk Array(3U) Blank filler panel (1U) BAM (2U) Blank filler panel (1U) iGWB (2U) Blank filler panel (1U) iGWB (2U) Blank filler panel (1U) Blank filler panel (2U) Blank filler panel (1U)
Air deflector (2U)
Air deflector (2U)
Air deflector (2U)
Air deflector (2U)
Blank filler panel ( 2U)
Blank filler panel (2U)
An integrated configuration cabinet is mandatory to the MSOFTX3000 and includes the following component:
! ! ! !
Power distribution subrack Service processing subrack (up to two) Air deflector KVMS (Keyboard, Video, Mouse, and Switcher)
2-12
Issue 03 (2006-09-30)

! ! !
2 System Structure
Core LAN Switch (up to two) iGWB (configured for charging, usually two) BAM
Service processing cabinets are configured based on the capacity requirements of carriers. A service processing cabinet includes the following components:
! ! !
Power distribution subrack Service processing subrack (up to four) Air deflector
2.3.2 Expansion Configuration

You can add subracks to increase the capacity of the MSOFTX3000. The MSOFTX3000 supports up to 1.8 million subscribers. Figure 2-8 shows a typical configuration of the MSOFTX3000: Figure 2-8 Expansion configuration of the MSOFTX3000
0 - 200 k 200 k - 1 M 1 M - 1.8 M
The configuration principles are as follows:

! !
If only the basic subrack is configured, the basic subrack supports 50 thousand subscribers. If both the basic subrack and expansion subracks are configured, service processing board cannot be configured in the basic subrack. Each expansion subrack supports 200
Issue 03 (2006-09-30)
2-13
2 System Structure
thousand subscribers. With all nine expansion subracks, the MSOFTX3000 supports up to 1.8 million subscribers.
2-14
Issue 03 (2006-09-30)
3 Interfaces, Signaling, and Protocols
3
Title
Interfaces, Signaling, and Protocols
About This Chapter

The following table lists the contents of this chapter. Description This section describes physical interfaces supported by the MSOFTX3000. This section describes protocol interfaces supported by the MSOFTX3000. This section describes signaling and protocols supported by the MSOFTX3000.
3.1 Physical Interfaces 3.2 Protocol Interface 3.3 Signaling and Protocols
Issue 03 (2006-09-30)
3-1
3.1 Physical Interfaces

3.1.1 Classification
The MSOFTX3000 supports physical interfaces such as FE, E1, and clock interfaces. Table 3-1 lists the numbers of interfaces and their functions. Table 3-1 Numbers and functions of physical interfaces Interface FE electrical interface Maximum Number Host: 8 (4 pairs, each including an active interface and a standby one) BAM: 3 Function To provide bearer channels for IP-based service signaling or protocols, such as H.248, BICC, M2UA, M3UA, IUA, SIP, and SIP-T To provide bearer channels for TCP/IP-based network management or file transfer protocols, such as SNMP, MML, FTP, and FTAM (The FE electrical interfaces are provided by the BAM and the iGWB for the networking of network management and billing) To provide 64-kbit/s and 2-Mbit/s MTP links for SS7 To receive 2.048-Mbit/s input clock signals (line clock) from the BITS equipment or E1 interface boards To receive 2.048-MHz input clock signals from the BITS equipment To provide 8 kHz output clock signals (internal interface) for E1 interface boards of the service subracks
End office: 288 E1 interface Gateway office : 360 Tandem office: 360 2.048 Mbit/s interface: 2 Clock interface
2.048 MHz interface 2
RS422 interface: 16
3-2
Issue 03 (2006-09-30)
3.1.2 Interface Specifications

Specifications of FE Electrical Interfaces
Table 3-2 lists specifications of FE electrical interfaces: Table 3-2 Specifications of FE electrical interfaces Item Compliant recommendation or standard Transfer rate Transferable distance Frame format Interface type Nominal impedance Value IEEE 802.3u 10/100Mbit/s self-adaptation 100 m 10BASE-T / 100BASE-TX RJ-45 100 ohm
Specifications of E1 Interfaces
Table 3-3 lists specifications of E1 interfaces: Table 3-3 Specifications of E1 interfaces Item Compliant recommendation or standard Transfer rate Line code type Transferable distance Transmission channel Nominal impedance Interface type Value ITU-T I.431, G.703, G.736, G.823, G.704, G.706, Q.703, G.732 ANSI T1.403 2.048Mbit/s HDB3 300m 32 (31 transmission channels and one synchronization channel) 75 ohm coaxial cable or 120 ohm twisted pair cable SMB (when coaxial cables are used)
Specifications of Clock Interfaces

Table 3-4 lists specifications of clock interfaces:
Issue 03 (2006-09-30)
3-3
Table 3-4 Specifications of clock interfaces Item Compliant recommendation or standard Interface type Signal type Detection threshold Impedance matching Balance mode Electrical isolation 2.048 MHz Clock Interface ITU-T G.703 SMB G.703.10 -24dB 75 ohm Unbalanced 300 V / 50 Hz, > 1 minute 2.048 Mbit/s Clock Interface ITU-T G.703 SMB G.703.6 -24dB 75 ohm Unbalanced 300 V / 50 Hz, > 1 minute
3.2 Protocol Interface

3.2.1 Standard Interface
Protocol interfaces in Mobile Network
The MSOFTX3000 provides open and standard protocol interfaces to support signaling and protocols. It can interwork with many types of equipment. Figure 3-1 shows the protocol interfaces provided by the MSOFTX3000 when it serves as a VMSC Sever, GMSC Sever, TMSC Sever, or SSP in a mobile network:
3-4
Issue 03 (2006-09-30)
Figure 3-1 Protocol interfaces provided by the MSOFTX3000 in a mobile network

HLR BC
FTP/ FTAM
SCP
Lg
GMLC
MML
SMC
C/D CAP/ L E
M2000
Service Layer
PSTN PLMN
TUP/ISUP
Nc / E
MSOFTX 3000
SIGTRAN Mc Gs lu-CS A
MSC Server
Control Layer
SG SGSN
BSC RNC
MGW
Access Layer
BSC: Base Station Controller BC: Billing Center SG: Signaling Gateway MGW: Media Gateway
GMLC: Gateway Mobile Location Center SCP: Service Control Point SGSN: Serving GPRS Support Node PLMN: Public Land Mobile Network
HLR: Home Location Register SMC: Short Message Center RNC: Radio Network Controller
Table 3-5 lists interfaces and protocols supported by the MSOFTX3000 in a mobile network: Table 3-5 Interfaces and protocols supported by the MSOFTX3000 in a mobile network Connected Entities MSC ServerMGW MSC ServerRNC MSC ServerBSC (GSM) MSC ServerVLR MSC ServerHLR VLRHLR MSC ServerMSC Server MSCMSC (GSM) MSC ServerSMC MSC ServerVLR Interface Mc Iu-CS A B C D Nc E E G Protocol H.248 RANAP BSSAP Internal protocol MAP MAP MAP, TUP/ISUP/BICC MAP, TUP/ISUP/BICC MAP MAP
Issue 03 (2006-09-30)
3-5
Connected Entities MSC ServerGMLC SSPSCP GMSC ServerPSTN GMSC ServerPLMN MSC ServerSGSN MSC ServerNMS MSC ServerBC
Interface Lg Gs -
Protocol MAP CAP TUP/ISUP BSSAP+ MML FTP/FTAM
Protocol interfaces in IMS Network

The MSOFTX3000 provides open and standard protocol interfaces to support signaling and protocols. It can interwork with many types of equipment. Figure 3-2 shows the protocol interfaces provided by the MSOFTX3000 when it serves as both an MSC server and an MGCF in an IMS network:
3-6
Issue 03 (2006-09-30)
Figure 3-2 Protocol interfaces provided by the MSOFTX3000 in an IMS network.

CS network BC
FTP/FTAM Mj
IMS Domain
BGCF
Mg MML
M2000
CSCF
PSTN/ PLMN
BICC/ISUP
Rf
MSOFTX3000
Mb SIGTRAN Mn
CCF
MRFP
Mb
SGW
IM-MGW
GGSN: Gateway GPRS Support Node BGCF: Breakout Gateway Control Function CSCF: Call Session Control Function PLMN: Public Land Mobile Network MGCF: Media Gateway Control Function SGW: Signaling Gateway MRFP: Multimedia Resource Function Processor CCF: Charging Collection Function
GGSN
IM-MGW: IP Multimedia Media Gateway CS domain: Circuit Switched domain IMS: IP Multimedia Subsystem
Table 3-6 lists interfaces and protocols supported by the MSOFTX3000 when it serves as an MGCF in an IMS network. Table 3-6 Interfaces and protocols supported by the MSOFTX3000 in an IMS network. Connected Entities MGCFIM-MGW MGCFPSTN MGCFPLMN MGCFBGCF MGCFCSCF MGCFNMS Mj Mg SIP SIP MML Interface Mn Protocol H.248 BICC/ISUP
Issue 03 (2006-09-30)
3-7
Connected Entities MGCFBC MGCFCCF
Interface Rf
Protocol FTP/FTAM Diameter
3.2.2 CDR Interface

CDR Transfer Protocol
The MSOFTX3000 supports standard FTP/FTAM. By interworking with the billing center, the MSOFTX3000 allows its iGWB to send CDR data to the billing center through the FTP or FTAM interface.
CDR File Format

The MSOFTX3000 supports CDR files in ASN.1 and binary formats:
!
ASN.1 format: ASN.1 is short for Abstract Syntax Notation One. ASN.1 is widely used as the standard for the protocol syntax at the application layer, because it can be used to clearly describe complex data structures. The CDR interface in ASN.1 format is recommended by both Huawei and 3GPP. Binary format: The MSOFTX3000 provides the CDR interface in binary format for 2G equipment in current network. The format is used by 2G offices and certain special offices. It is not recommended to you in normal cases.
CDR Content Format

By configuring database files of CDR content formats, supports CDR content formats defined by 3GPP. the iGWB of the MSOFTX3000
3.2.3 Interception Interface

The MSOFTX3000 supports four standard interception interface protocols:
! ! ! !
LICI (Lawful Interception Center Interface) ETSI (European Telecommunications Standards Institute) SOSM (System of Operative-Search Measures) SPBX (Special Private Branch Exchange)
By interworking with the lawful interception center, the MSOFTX3000 allows national security bodies to intercept certain mobile subscribers in real time. SPBX is developed by Huawei based on mobile communication protocols and requirements of security bodies. It is applicable to the lawful interception systems in most countries. To use SPBX interception interfaces, carriers must sign a contract with Huawei because SPBX is a private protocol of Huawei.
3-8
Issue 03 (2006-09-30)
3.3 Signaling and Protocols

The MSOFTX3000 provides open and standard protocol interfaces to support signaling and protocols. It can interwork with many NEs. Table 3-7 shows the signaling and protocols supported by the MSOFTX3000: Table 3-7 Signaling and protocols supported by the MSOFTX3000. Signaling or Protocol H.248 SCTP Function Compliant Recommendation or Standard 3GPP TS 29.232 V4.7.0 IETF, RFC2960, Stream Control Transmission Protocol (SCTP)
Media gateway control protocol, used by the MSOFTX3000 to control the MGW Stream control transmission protocol, used to provide reliable data packet transfer services for the adaptation protocols of IP-based switched circuit network (SCN) signaling MTP2 user adaptation layer, used by the MSOFTX3000 to interwork with MGWs with built-in M2UA SG functions MTP3 user adaptation layer, used by the MSOFTX3000 to interwork with M3UA SGs ISDN Q.921 user adaptation protocol, used by the MSOFTX3000 to interwork with MGWs with built-in IUA SG functions Message transfer part, used for the interworking between the MSOFTX3000 and the SS7 signaling network so that the MSOFTX3000 can interwork with SPs or STPs in the SS7 signaling network Telephone user part, used for the interworking between the MSOFTX3000 and the PSTN or other MSCs so that the MSOFTX3000 can provide TUP trunks through MGWs Integrated services digital network user part, used for the interworking between the MSOFTX3000 and the PSTN or other MSCs so that the MSOFTX3000 can provide ISUP trunks through MGWs Signaling connection control part, used to bear the MAP and CAP protocols so that circuit-independent signaling connections can be established between the MSOFTX3000 and entities such as the VLR, HLR, EIR, MSC, SMC, GMLC, and
M2UA
IETF, RFC3331, SS7 MTP2 User Adaptation Layer (M2UA) IETF, RFC3332, SS7 MTP3-User Adaptation Layer (M3UA) IETF, RFC3057, ISDN Q.921-User Adaptation Layer (IUA) ITU-T Q.701~Q.707
M3UA
IUA
MTP
TUP
ITU-T Q.721~Q.725
ISUP
ITU-T Q.761~Q.764, Q.730
SCCP
ITU-T Q.711~Q.716
Issue 03 (2006-09-30)
3-9
Signaling or Protocol TCAP
Function
Compliant Recommendation or Standard ITU-T Q.771~Q.775
SCP through the SS7 signaling network Transaction capability application part, used to provide functions and routines not related to specific applications so that the MSOFTX3000 can establish MAP or CAP dialogs with entities such as the VLR, HLR, EIR, MSC, SMC, GMLC, and SCP Mobile application part, used to define the information exchanging mode between network entities to implement roaming of MSs so that the MSOFTX3000 can interwork with network entities such as the VLR, HLR EIR, MSC, SMC, and GMLC through the C, D, E, G, and Lg interfaces CAMEL application part, use to define standard communication routines between network entities so that the MSOFTX3000 can perform the SSF, CCF, SRF, and CCAF functions and serve as the SSP in an IN Base station subsystem application part, use to define the A interface between the MSC and the BSC so that the MSOFTX3000 can interwork with the BSC through the MGW Radio access network application part, used to define the Iu interface between the MSC server and the RNC so that the MSOFTX3000 can interwork with the RNC through the MGW Base station subsystem application part+, used to define the Gs interface between the SGSN in the PS domain and the MSC in the CS domain so that the MSOFTX3000 can interwork with the SGSN Standard channel associated signaling, used for the interworking between the MSOFTX3000 and exchanges of old mode so that the MSOFTX3000 can provide CAS trunks through the MGW ISDN subscriber network signaling, used for the interworking between the MSOFTX3000 and PBXs so that the MSOFTX3000 can provide primary rate interfaces (PRIs) through the MGW
MAP
3GPP TS 29.002 V4.11.0
CAP
3GPP TS 29.078 V4.7.0
BSSAP
3GPP TS 48.008 V4.8.0 3GPP TS 24.008 V4.9.0
RANAP
3GPP TS 25.413 V4.7.0 3GPP TS 24.008 V4.9.0
BSSAP+
3GPP TS 29.018 V4.4.0
R2
ITU-T, Q.400~Q.499
DSS1
ITU-T I.430, I.431, Q.921, Q.931
3-10
Issue 03 (2006-09-30)
Signaling or Protocol BICC
Function
Compliant Recommendation or Standard 3GPP TS 23.205 V4.6.0 ITU-T, Q.1902
Bearer independent call control protocol, used to establish, modify, and end calls so that the MSOFTX3000 can send call control signaling to other MSC servers through the E interface Session initiation protocol, used for the interconnection between the MSOFTX3000 and other softswitches or SIP application servers, and to access SIP multimedia packet terminals Extension protocol of SIP, used for the transparent transmission of ISUP signaling File transfer protocol, used to support the interconnection between the MSOFTX3000 and billing centers so that the MSOFTX3000 can provide FTP interfaces File transfer access and management protocol, used to support the interconnection between the MSOFTX3000 and billing centers so that the MSOFTX3000 can provide FTAM interfaces Used to support the clock synchronization between the MSOFTX3000 BAM and the NTP Server so that the time of all devices in the network is synchronized
SIP
IETF, RFC3261, Session Initiation Protocol (SIP)
SIP-T
IETF, RFC3372, Session Initiation Protocol for Telephones (SIP-T) IETF, RFC0959, File Transfer Protocol (FTP)
FTP
FTAM
ISO, ISO8571, File Transfer Access and Management Protocol (FTAM)
NTP
IETF,RFC1305,Network Time Protocol (NTP)
Issue 03 (2006-09-30)
3-11
4 O&M System
4
About This Chapter
The following table lists the contents of this chapter. Title 4.1 Overview of O&M 4.2 O&M Function Description
O&M System
This section describes the structure of the MSOFTX3000 terminal system. This section describes the O&M functions supported by the MSOFTX3000.
Issue 03 (2006-09-30)
4-1
4 O&M System
4.1 Overview of O&M

4.1.1 Basic Concept
O&M (O&M) refers to tasks that carriers perform on running softswitch systems. O&M ensures normal operation of the system and the quality of the teleservices. The MSOFTX3000 provides a graphical Man Machine Language (MML) environment in which a number of O&M functions can be provided. The O&M functions include:
! ! ! ! ! !
Configuration management Fault management Performance measurement Security management CDR management Environment monitoring
4.1.2 Terminal System

The O&M functions of the MSOFTX3000 can be performed on the local maintenance terminal (LMT) or the local maintenance center of Huawei iManager M2000. The terminal system is the key hardware platform to carry out O&M functions. The terminal system consists of the following parts, as shown in Figure 4-1.
! ! ! !
BAM iGWB Emergency workstation LMTs
4-2
Issue 03 (2006-09-30)
4 O&M System
Figure 4-1 Network structure of the terminal system
MSOFTX3000 host
LAN Switch
To BC WAN Active iGWB Standby iGWB To NMC
BAM
HUB
WAN iManager M2000
LMT
LMT
LMT
LMT
Emergency workstation
BAM: Back administration module BC: Billing center
iGWB: Charging gateway of Huawei NMC: Network management center
The terminal system works in the client/server mode. The BAM and the iGWB function as the servers. They are connected to the MSOFTX3000 host and the external computer network through the Ethernet. The LMTs function as the clients and can be configured as the following based on the requirements:
! ! ! ! !
Maintenance console Data management console Alarm console Performance measurement console CDR console
In the terminal system, the BAM is the core hardware to achieve the O&M functions. It forwards the O&M commands from the LMTs to the host, and directs the response from the host to the mapping LMT. To ensure the reliability of the terminal system, the MSOFTX3000 has the following features:
! !
Two Ethernet connections working in active/standby mode, which connect the BAM/iGWB and the host. Two iGWBs working in active/standby mode, which ensures the security of CDRs.
Issue 03 (2006-09-30)
4-3
4 O&M System
!
An emergency workstation (EW) is designed as the online backup of the BAM. When the BAM is faulty, the EW can replace the BAM; at the same time, it can restore the BAM with the backup data stored in its hard disk.
4.1.3 Network Management Networking

The MSOFTX3000 provides external MML network management (NM) interface through the BAM, which can be connected to the NMC. If the NMC adopts Huawei iManager M2000 as the NM part of the network, the carrier can connect the NMC to the BAM through the MML interface, as shown in Figure 4-1. In this case, the iManager M2000 works as a remote workstation of the MSOFTX3000 terminal system.
4.1.4 Introduction to MML Command Line

MML command line is also known as MML. It is a set of human-machine interface that is based on the ITU-T Z.301 to Z.341. MML provides a command set to operate and query the MSOFTX3000. By using the command set, you can monitor and manage the data on the MSOFTX3000. In normal cases, the BAM can process ten MML commands in one second. The features of MML are as follows:
! !
The MML command set encapsulates the services of the MSOFTX3000. A command maps a function, but not an operation. The MML command set is equal to a group of application programming interfaces (APIs) in terms of the MSOFTX3000. All other application programs are based on it. For a GUI terminal, the interface operations are translated into commands, and then transferred to the MML system. The MML system runs the commands and returns the results in text format. The results are exported by the GUI terminal to the operation terminal of subscribers. Thus, the stability of the system is ensured and the running of the whole system is not affected by a single application program issue. The MML system performs strict data consistency check. When a function is executed, the MML system checks mappings between the tables. This is an effective way to avoid producing junk data. The input and output of the MML system are based on pure character streams. Programs such as TELNET are supported to interact with the MSOFTX3000. Therefore, the client can override all types of platforms, for example, supporting a dumb terminal without processing capabilities. This is beneficial to a centralized network management, and follows the development trends of telecommunication products. The MML system supports the search function and standard Windows search functions such as keyword search and fuzzy search. It also provides complete online help documents for subscribers to study and use MML commands.
4.2 O&M Function

4.2.1 Configuration Management
The MSOFTX3000 provides the following database operation methods:
! ! !
Addition Deletion Modification
4-4
Issue 03 (2006-09-30)

! ! ! !
4 O&M System
Query Storage Backup Restoration
With these methods, you can effectively manage and maintain the following data of the MSOFTX3000:
! ! ! ! ! ! ! !
Hardware data Office information data Gateway data Signaling data Routing data Number analysis data Mobile service data IN service data
In addition, the MSOFTX3000 configuration management provides the following functions:

! ! ! !
Offline or online data configuration Local and remote configuration Online upgrade of data Data verification (ensuring consistency of host data and BAM data)
4.2.2 Fault Management

Overview
Fault management function helps you check, locate and fix the MSOFTX3000 system faults during its operation. This funciton provides tools for the routine maintenance of the system. The tools can also prevent the occurrence of faults. Fault management includes the following items:
! ! ! !
System self-test Alarm management Maintenance management Trace management
System Self-Test
The MSOFTX3000 regularly tests the resource occupation of itself. The MSOFTX3000 also performs the following:
! ! !
Checking the occurrence and severity of overload, and processing the overload Arranging the interior work of the system Minimizing the impact of the faults on the system
Issue 03 (2006-09-30)
4-5
4 O&M System
Alarm Management
The alarm management system of the MSOFTX3000 can perform the following alarm management operations:
! ! !
Detect and report in real time any fault or abnormity of the equipment Generate audio and visual alarm signals through the alarm terminal devices (such as alarm box and alarm console) based on the type and level of the alarm Send the alarm information after explanation to the NMC through the NM interface.
In addition, the alarm management provides the following functions:

!
Store the alarm information, query the alarm record, configure the troubleshooing method, and provide CPU threshold data in the reported alarm information when the CPU usage rate is too high Present the alarm information as well as handling suggestion at the local maintenance terminal to help users troubleshoot the faults efficiently
Maintenance Management
The maintenance management function provides the following maintenance control methods through the MML commands:
! ! ! ! ! ! !
Query Display Switchover Reset Isolation Block Activation
Using these methods, you can effectively and efficiently manage and maintain:
! ! ! ! !
Hardware components of the MSOFTX3000 System resources Signaling links Physical ports Gateways controlled by the MSOFTX3000 and the related bearer resources
Tracing management
Tracing management of the MSOFTX3000 offers the graphic interface. It provides the following functions:
! ! ! !
Connection tracing Signaling tracing Interface tracing Message interpretation
Using these functions, real time and dynamic tracing can be conducted on the following items related to the terminal subscribers, trunk circuits, signaling links, and interface protocols:
!
Connection process
4-6
Issue 03 (2006-09-30)

! ! ! !
4 O&M System
State transition Resource occupancy Telephone number information transfer Control information streams
The tracing information can be stored for future reference, enabling the two powerful functions of:
! !
Fault analysis Location capabilities
4.2.3 Performance Measurement

To help subscribers know the equipment operation status, equipment management situation and network optimization, the performance measurement (PM) system provides original data by measuring the following items:
! ! ! !
Traffic Connection process QoS Cause of failure
The PM tasks can be created, modified, carried out, suspended, deleted and queried. The system can present the measurement results in the bar chart or the fold-line graph, and then conduct data analysis based on the result.
4.2.4 Security Management

Authority Management
The O&M system of the MSOFTX3000 can be used by many operators. The authorities of operators are divided by levels. This ensures the secure running of the system. Whether an operator can run a certain MML command depends on his authority.
Log Management
It enables the query of MML operation records. By querying the log, you can check whether any operation that may affect the operation of the system has been performed.
4.2.5 CDR Management

The iGWB Server provides CDR management features in the MSOFTX3000. Here are some principal functions of the iGWB Server.
Real time Receipt of CDR Data Generated by MSOFTX3000

The generated CDRs are stored in the host CDR pool, and then sent to the iGWB Server through the LAN immediately to avoid the overflow of the CDR pool.
Issue 03 (2006-09-30)
4-7
4 O&M System
Reliable Storage and Backup of Original CDR Data

The hard disk of iGWB Server can be expanded conveniently. It can store a large amount of CDR data for a long time. The CDR data stored in the iGWB Server can be backed up in the network.
Preprocessing of Original CDR Data

The iGWB Server performs pre-processing such as format conversion, CDR sorting and CDR filtering on original CDRs to generate the final ones and store them in the local hard disk array. It is possible to operate and query the CDRs in local through the iGWB Server.
Providing FTP/FTAM Interface for Billing Center

The billing center fetches CDRs through the FTP or the FTAM interface. The iGWB Server supports automatic fetching of CDRs.
Providing CDR Operation Log

The iGWB Server logs user operations for future reference in troubleshooting, including:
! ! ! !
Operator account Operation time Operation data Detailed operation
4.2.6 Environment Monitoring

By default, the MSOFTX3000 presets the following external environment alarm types during initialization:
! ! ! ! ! ! ! ! ! !
High temperature Low temperature High humidity Low humidity Access control Smoke detection Fire Water Commercial power supply fault Low voltage
The preceding alarm types can meet the requirements of most carriers.
4-8
Issue 03 (2006-09-30)
5 Services and Functions
5
About This Chapter
Title 5.1 Basic Services
! ! ! !
Services and Functions
The following table lists the contents of this chapter. Description The service functions consist of circuit switched domain services, such as the following: Teleservices Supplementary services IN services Value added services Mobility management Security management Call control Location services Service switching function
5.2 Basic Functions
The mobile network functions consist of thefollowing:

! ! ! ! !
5.3 Description of New Features
This section introduces new features and functions except the basic services and the functions.
Issue 03 (2006-09-30)
5-1
5.1 Basic Services

5.1.1 Teleservices
Overview
Huawei MSOFTX3000 supports the basic teleservices listed as follows:
! ! ! ! !
Speech services Short Message Service (SMS) GSM fax services GSM bearer services UMTS bearer services
Huawei MSOFTX3000 provides bidirectional communication capability for:

! !
Mobile subscribers of local office Other connected subscribers (such as mobile subscribers of other offices and fixed network subscribes)
Speech Services
The speech service is the basic function of telecom network, including telephony (TS 11), emergency call (TS 12) and emergency call for special service:
! !
Telephony: The carriers provide the telephony service for the subscribers among PSTN, ISDN, and PLMN through the function. Emergency call: When the mobile subscribers press an emergency key or dial 112, the call is connected to the answer phone notice equipment. The answer phone tells the subscribers how to call the emergency center. The subscribers can make the emergency calls even without a SIM or USIM. Emergency call for special service: When dialing 119 (fire alarm center), 110 (mobster alarm center), 120 (first-aid center) and 122 (traffic accident center), the mobile subscribers access the nearest special service centers based on the BTS where the subscribers are located. The above calls can generate the alarms. Whether to charge the subscribers can be set as required.
SMS
Short message (SM) means that the length of cell content transferred each time is short in the SMS. Based on the definition of relevant technical specifications (ETSI GSM 03.40 and ETSI GSM 03.41) in current ETSI GSM, each Point-to-Point (PTP) SM includes a maximum of 140 bytes. That is, 160 ASCII characters or 70 Chinese characters. Each broadcast SM includes a maximum of 82 bytes/page, that is, 92 ASCII characters or 41 Chinese characters, and a maximum of 15 pages macro broadcast messages can be sent continuously. The PTP SMS allows the subscribers to send or receive the SM at any time. The broadcast SMS allows the subscribers to receive the public messages regularly and selectively. The SMS includes PTP SMS, and point-to-multipoint SMS. The former includes the following:
5-2
Issue 03 (2006-09-30)

!
Originating SMS: This service transmits a short message from user equipment (UE) to a message handling system (service centre). After receiving it, the service center sends back an acknowledgement message. Terminating SMS: This service transmits a short message from a service centre to UE. After receiving it, the UE sends an acknowledgement message.
GSM Fax Services

Huawei MSOFTX3000 supports GSM G3 transparent fax that complies with 3GPP TS 03.45 and ITU-T T.30. The rate can be 9.6 kbit/s, 7.2 kbit/s, 4.8 kbit/s or 2.4 kbit/s during the fax service. Service types consist of TS61 and TS62.
! !
TS61: Huawei MSOFTX3000 supports the alternate of G3 transparent digital fax and speech. The rate can be 2.4 kbit/s, 4.8 kbit/s or 9.6 kbit/s during the fax service. TS62: Huawei MSOFTX3000 supports image fax but not file fax and ECM error correction mode. The rate can be 2.4 kbit/s, 4.8 kbit/s or 9.6 kbit/s during the fax service.
GSM Bearer Services

Huawei MSOFTX3000 supports the following BS20 bearer services of which the fixed network user rate can be 2.4 kbit/s, 4.8 kbit/s or 9.6 kbit/s:
! ! ! !
Transparent asynchronous bearer services-3.1kHz audio Transparent asynchronous bearer services-UDI of which the rate adaptation is V.110 Non-transparent asynchronous bearer services-3.1kHz audio Non-transparent asynchronous bearer services-UDI of which the rate adaptation is V.110
UMTS Bearer Services

Huawei MSOFTX3000 supports the following BS20 and BS30 bearer services:
! ! ! !
Non-transparent asynchronous bearer services-3.1kHz audio, and under the UMTS, fixed network user rate is 9.6/14.4/19.2/28.8 kbit/s Non-transparent asynchronous bearer services-UDI, and under the UMTS, the fixed network user rate is 9.6/14.4/19.2/28.8 kbit/s, and the rate adaptation is V.110/V.120 Transparent synchronous bearer services-UDI, fixed network user rate is 64 kbit/s Transparent synchronous bearer services-multimedia, fixed network user rate is 64 kbit/s, the rate adaptation is H.223 and H.245
5.1.2 Supplementary Services

Overview
The supplementary services (SSs) are the supplement and conversion of the basic teleservices. The SSs provided for the subscribers are based on the basic teleservices, and they must be provided for the subscribers to use together with basic services. Huawei MSOFTX3000 supports multiple SSs defined in the 3GPP specification and listed as follows:
Issue 03 (2006-09-30)
5-3
Call Forwarding Services

Call forwarding (CF) services indicates that the system forwards calls to third parties based on requirements of:
! ! !
Carriers Networks Subscribers
Call forwarding services consist of the following services:

!
Call Forwarding Unconditional (CFU): When a mobile subscriber is a called party, all the calls are forwarded to the third party. The third party here either can be any subscriber in the PLMN, PSTN and ISDN or the service console (such as Voice Mailbox). Call Forwarding Busy (CFB): When a called mobile subscriber is busy, the call is forwarded to the third party. The CFB can be divided into Network Determined User Busy (NDUB) and User Determined User Busy (UDUB) based on the forwarding cause. Call Forwarding on No Reply (CFNRy): When the mobile subscribers do not answer the call after receiving network ALERTING message for a long time, and the No reply duration timer expires, the calls are forwarded to the third party. Call Forwarding on Mobile Subscriber Not Reachable (CFNRc): If the network is disconnected with radio channel of mobile subscriber, and the mobile subscriber is the called party, all the calls are forwarded to the third party. The Not Reachable conditions include paging no reply, radio channel allocation failure, and subscriber power-off. The CFNRc is classified into the home CF and destination CF based on the forwarding places.
Call Barring Services

Calls barring services consist of two types:
! !
Barring of outgoing calls (BO) Barring of incoming calls (BI)
The BO service includes:

! ! !
Barring of All Outgoing Calls (BAOC) Barring of All Outgoing International Calls (BOIC) Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC-exHC)
The BI service includes:

! !
Barring of All Incoming Calls (BAIC) Barring of Incoming Calls When Roaming Outside Home PLMN Country (BIC-ROAM)
The following lists the meanings of BO and BI services.

! !
BAOC: When the service is activated, the subscribers cannot originate the calls except the emergency calls. BOIC: If the mobile subscribers are roaming in the home PLMN, they are not allowed to originate calls to the overseas subscriber. If the mobile subscribers are roamed outside the home PLMN, they can originate calls to local subscribers only.
5-4
Issue 03 (2006-09-30)

! ! !
BOIC-exHC: When the service is activated, the subscribers are unable to originate the international toll calls except calls in home country. BAIC: When the service is activated, the subscribers are unable to answer all the incoming calls. BAIC-ROAM: When the service is activated and the mobile subscribers are roaming outside the home PLMN country, they are unable to receive the incoming calls from other subscribers.
Line Identification Services

The system provides the following functions:
! !
Calling number
presentation or restriction for called party.
Called number presentation or restriction for calling party
Line identification services include:

! ! ! !
Calling Line Identification Presentation (CLIP) Calling Line Identification Restriction (CLIR) Connected Line Identification Presentation (COLP) Connected Line Identification Restriction (COLR)
The following lists the meanings of line identification services:

!
CLIP: CLIP is a service provided for called mobile subscriber. When a mobile subscriber receives a call, the system shows calling number to the subscriber. The subscriber can know the calling party, and then determine whether to connect, reject or forward the call. CLIR: CLIR is a service provided for calling mobile subscriber. When a mobile subscriber is a calling party, the system is not allowed to show the calling number to the called party. COLP: When a mobile subscriber calls, the system shows the called number to the caller. When the callee activates CF service, the caller communicates with the forwarded subscriber instead of the original callee. The system shows the forwarded number to the caller. COLR: When a mobile subscriber is the callee, the system is not allowed to show the called number to the caller. When the calleer is the forwarded one, the system is not allowed to provide the forwarded number to the caller.
Call Completion Services

Call completion services consist of Call Waiting (CW)
!
and Call Hold (HOLD):
CW: When the mobile subscribers are in a conversation, they are allowed to connect another call. At that time, the system prompts that another call is waiting, and the called subscriber can determine whether to connect this call. HOLD: A subscriber terminates the current call temporarily and connects a new incoming call. After the new call is connected, the subscriber can shift between the old and new one, and another call is in HOLD state.
Multiparty Service
The mobile subscriber who registers this service can organize multiparty telephone conference, providing the conversation among multiparty (this mobile subscriber included).
Issue 03 (2006-09-30)
5-5
Up to 6 subscribers can have a conversation at the same time through the MPTY. During the MPTY, the main control subscriber can add, disconnect, or isolate remote subscriber. Here isolate means the chairman of the MPTY holds one subscriber to isolate him from the meeting temporally.
Unstructured Supplementary Service Data

Unstructured Supplementary Service Data (USSD) contains the following cases:
! !
The subscriber enters operation command of the un-standardized supplementary service consistent with USSD format and originates a special service request to the network. The network side sends a USSD command to the network to carry out a special service.
Compared with SMS, USSD service can exchange messages in real time. It is convenient for services such as stock query. USSD center provides the following services:
! ! ! ! ! !
Airline information Finance and stock information foreign exchange information Gymnasium match result Cinema ticket information Bank account information
In addition, the USSD is used by mobile subscribers to query and manage their service data, for example:
! !
After the MSC is connected to IN network, subscribers can manage IN service data by using the USSD. Subscribes can query data (such as MSISDN number) in the VLR and HLR.
Closed User Group Service

Closed User Group (CUG): One or several users with the same attributes forms a group. The members have the same call attribute. CUG service is applicable for a small group with several members or a large enterprise with thousands of subscribers.
5.1.3 ODB Services

Overview
Operator Determined Barring (ODB) is controlled by network carriers. It is carried out through HLR data management. Carriers restrict the call capabilities of subscribers based on different characteristics, especially economic capability. This ensures that carriers do not suffer serious loss in conversation fees. ODB can be used in all the user terminal service and bearer service except the emergency calls. Compared with the preceding mentioned SSs, ODB enjoys higher priority. When two services conflict, the preceding mentioned SS will be prohibited.
5-6
Issue 03 (2006-09-30)
Relationship Between ODB and Call Barring Services

Both ODB and call barring services implement barring service. The differences are as follows:
! !
The former subscriber state is controlled by carriers, but that of the latter is controlled by the subscriber himself or the carrier. The former can be activated when it is provided. The latter is activated after the subscriber activates it.
Supported ODB Services

Huawei MSOFTX3000 supports the following ODB services:
! ! ! ! ! ! ! ! ! !
Barring outgoing calls Barring outgoing international calls Barring outgoing international calls except those directed to the home PLMN country Barring of outgoing calls when roaming outside the home PLMN country Barring incoming calls Barring incoming calls when roaming outside the home PLMN country Barring of Roaming outside the home PLMN country Barring of outgoing Premium Rate Calls (information) Barring of outgoing Premium Rate Calls (Entertainment) Barring of Supplementary Services Management
5.1.4 IN Services
Overview
Huawei MSOFTX3000 provides the gsmSSF function. The MSOFTX3000 supports CAMEL 3 and it is compatible with CAMEL 2 and CAMEL 1. It supports IN services such as the following:
! ! ! !
Prepaid Service (PPS) Mobile Virtual Private Network (MVPN) Prepaid IP Service (PPIP) Familiarity Number
PPS
PPS is a card number service. The PPS subscriber should pay some money in advance or purchase the capital card with fixed face value (such as rechargeable card, storable card and renewable card) for the conversation fees to set up an account. The carriers do not identify the ID of the subscriber. There is only the prepaid agreement relation between the carriers and the subscribers. The PPS are convenient for both carriers and subscribers. The system determines whether to connect or disconnect the call based on the account balance when the call is setting up. Once the call is connected, the system performs real-time charge and reduces the PP money on the subscriber account. If the account balance is used up, the call will be disconnected. So PPS helps the carriers avoid the loss of conversation fees.
Issue 03 (2006-09-30)
5-7
MVPN
Establish a private network of logic voice channel on the PLMN and PSTN. This enables the convenient communication among enterprise and group subscribers through the following ways:
! !
Private numbering plan Abbreviated dialing
If the MVPN service is activated in the PLMN, we provide a private network service similar to PSTN Private Branch Exchange (PBX) for the mobile subscriber of the group registering this service. The MVPN service provides the following functions for MVPN subscribers:
! ! ! ! ! !
In-net calling Off-net calling Private label Abbreviated label Group access number Override
The MVPN service provides preferential charging rate for groups and enterprises. This helps mobile carriers not lose VIPs. Based on specifications, the MVPN service requires that all MSCs/GMSCs/HLRs support the MAP2+ and all MSCs/GMSCs have the SSP function and they can trigger IN services through O-CSI/T-CSI. Thus, the MVPN service must be realized in target network.
5.1.5 Value Added Services

Multimedia Services
Supported by the UDI bearer service, multimedia services realize video communication in Circuit Switched (CS) domain. It supports the following services:
! ! ! !
Videotelephony Video conference Video On Demand (VOD) Mobile television
Mobile Location Services

With the gateway mobile location center (GMLC) , the MSOFTX3000 can:
! ! !
Supports the Lg interface. Stores the mobile subscriber location information. Provides the information at any time.
The services include:

! !
Mobile called subscriber location service: The external device can locate a mobile terminal. Mobile calling subscriber location service: The mobile terminal sends a location request.
5-8
Issue 03 (2006-09-30)

! !
Emergency call location service: The network locates the subscriber in case of emergency. Subscriber privacy protection: The location requester will be restricted based on the request of subscribers to protect private.
Ring Back Tone Service

The MSOFTX3000 supports the Ring Back Tone (RBT) service. The RBT service replaces the traditional ring back tone with the customized music and other special tones and voices.
Equal Access Service

The mobile subscriber can select the network of each toll carrier. This realizes the equal competition of toll carriers. To carry out the equal access, each toll carrier is allocated with a carrier identification code (CIC). After signing an agreement with a toll carrier, the mobile subscriber can select the toll network of this toll carrier to originate a call through adding the CIC of this toll carrier. There are two modes to use the service are: Preset CIC and Dial up freely CIC. Mobile subscriber can add the function of network selection through preset. The mobile subscriber can select toll carrier through the preset function. After that, mobile subscriber can select a preset toll network channel of one carrier to originate a toll call without dialing the CIC.
Enhanced Roaming Restriction Service

Enhanced roaming restriction (ERR) is compared to the common roaming restriction (CRR). In CRR, the VLRs which a subscriber can roam to are configured directly on an HLR. The minimum restriction area is on a VLR area basis. This kind of restriction is not flexible, because the subscribers must be configured one by one, and the restricted areas may be too wide. The ERR does not require HLR subscription and the roaming restriction data is configured directly on the MSC or VLR. You can restrict the roaming of a specific subscriber or even subscribers within a number segment in the MSC/VLR area. The minimum restriction area is on a cell basis.
Alternate Line Service

For Alternate Line Service (ALS), a mobile subscriber can use one mobile terminal and one SIM card, and the two MSISDNs can be charged separately. The service requires to be supported by MSC/VLR as well as mobile terminals that can set Line1 and Line2. The features of the service are as follows:
! !
Two MSISDNs are for Line1 and Line2. If a mobile terminal originates a call with a line, its MSISDN is displayed as the caller ID. A mobile terminal can only originate or answer a call through either Line1 or Line2 at a given time. Therefore, a caller can only dial one MSISDN that corresponds to Line1 or Line2. Otherwise, the call connection fails. For example, if a mobile terminal uses Line1, but a caller dials the MSISDN that corresponds to Line2, the call connection fails. For the two MSISDNs, you can subscribe to different supplementary services such as call forwarding, call barring and call waiting.
Issue 03 (2006-09-30)
5-9

! !
When a mobile subscriber uses the MSISDN that matches Line1, speech services and related supplementary services are allowed. ODB is used to bar services. When a mobile subscriber uses the MSISDN that matches Line2, short messages can only be received but not sent. USSD operation cannot be performed.
Voice and Video Double Number

Voice and Video Double Number (VVDN): The service enables the setting of different MSISDNs for both voice and videophone services. The MSISDN is displayed as the caller ID. For example, if a mobile subscriber originates a voice call, the MSISDN related to voice service is displayed as the caller ID on the terminal of the called party. The same applies to videophone calls. When a caller calls a mobile subscriber, either the MSISDN for voice service or videophone service can be used.
5.2 Basic Functions

5.2.1 Mobility Management
Overview
Through the mobility management function, namely location management (LM) function, the network can trace current location of MS and store location information in the following:
! ! ! !
HLR MSC VLR MS (SIM/USIM card)
LM flow ensures that the location information stored in the three entities is the same. The LM function of network devices realizes the roaming function for mobile subscribers.
Common Location Update

During powering on or movement, if the location area identifier received by the MS is inconsistent with that in the MS, the MS originates location update request to the network to update the location area identifier. The MSOFTX3000 supports the following location update flows:
! ! !
Location update in the same MSC Server/VLR area Location update cross different MSC Server/VLR areas and originated by the IMSI Location update cross different MSC Server/VLR areas and originated by the TMSI
Periodic Location Update

The MS originates location update periodically, whether it moves to new location area or not. If the MS does not originate periodic location update flow after a specified period expires, the VLR sets the status of the IMSI to detach. Thus, the waste of circuit resource and wireless resource can be reduced.
5-10
Issue 03 (2006-09-30)
IMSI Attach/Detach
If the network allows the MS to access the network, the VLR auto sets the status of subscriber IMSI to attach. It indicates that the subscriber is activated and valid. When the MS is switched off for a long time, the VLR auto sets the status of subscriber to detach. When a subscriber who is in detach status is called, the system does not originate call attempt to the subscriber. Thus, wireless channel resources are saved. The MSOFTX3000 supports the following IMSI detach types:
! !
Implicit IMSI detach: After the implicit IMSI detach timer times out, the VLR auto sets the status of subscriber to detach. Explicit IMSI DETACH: The MS originates the IMSI detach flow and the VLR sets status of subscriber to detach.
Combined Location Update

When the network is configured with Gs interface and the MS supports both CS services and PS services, the combined location update flow is originated in the following cases:
! ! !
The MS moves to a new route area. A mobile phone that has attached GPRS attach originates IMSI attach. Both GPRS attach and IMSI attach are originated at the same time.
Association is established between the SGSN and the VLR. Either of them saves the ISDN number of the other.
5.2.2 Security Management

Overview
The MSOFTX3000 supports the security management (SM) function defined by the 3GPP specifications, such as the following:
! ! ! ! ! !
Authentication Encryption Integrity protection TMSI reallocation IMSI identification IMEI identification
The SM function can perform the following:

! ! !
Preventing prohibited subscribers from connecting the network Preventing fraud network from spoofing subscribers Ensuring the reliable transmission of the subscriber signaling data
GSM Authentication and Encryption

The MSOFTX3000 supports the authentication encryption algorithm and flow defined by the GSM.
!
Supporting general authentication
Issue 03 (2006-09-30)
5-11

!
Supporting 1/N authentication Through data configuration, only one authentication flow is performed for multiple location updates and services accesses.
Supporting authentication parameter multiplex An authentication flow requires a group of authentication parameters (APs). If the APs used for each authentication flow are different, the signaling load from the MSC to the HLR increases and the processing capacity of the HLR decreases. You can configure the AP multiplex function and count. Therefore, the same AP is used for multiple authentication flows, which decreases the network load and increases the processing capacity of the HLR.
Supporting all the encryption defined by the GSM
UMTS Authentication and Encryption

The MSOFTX3000 supports authentication encryption algorithm and authentication flow defined by the UMTS. The authentication triplet for the GSM evolves into authentication quintuple for the UMTS.
Second Authentication
If the first authentication of the mobile subscriber fails (for example, the SRES sent to the MS/UE side is different from that on the switch side), the network side must originate the second authentication request in the same event and use RAND2 that is different from RAND1 in the first authentication request. If the second authentication fails, the network side sends an Authentication_Reject message to the terminal.
Conversion Between Authentication Triplet and Quintuple

The MSOFTX3000 supports the conversion between the triplet encryption for the GSM and quintuple encryption for the UMTS. This facilitates the roaming and handover between the GSM and the UMTS.
TMSI Reallocation
The temporary mobile subscriber identity (TMSI) indicates a string of numbers allocated to subscribers temporarily and identifies an MS in a location area. TMSI managed by the MSC/VLR is allocated to the MS when the MS registers for the first time in a location area, and deregistered when the MS is out of the location area. The TMSI rather than the IMSI is transmitted in the radio channel, which can prevent the third party from identifying and tracing the mobile subscriber by eavesdropping the signal in the radio channel. The MSOFTX3000 supports the TMSI reallocation during:
! ! !
Location update Call setup SS operations
IMSI Identification
The IMSI identification indicates that the network originates an IMSI identification flow if it cannot identify the TMSI used for the network access of the mobile subscriber. After receiving the identification response, the network can allocate a new TMSI.
5-12
Issue 03 (2006-09-30)
IMEI Identification
The MSOFTX3000 can coordinate with the EIR to perform the IMEI check to the MS. By querying the IMEI record (white list, grey list, and black list) in the database, the MSOFTX3000 determines whether to provide service for the MS.
Embedded EIR
The embedded EIR indicates that a virtual EIR is configured with illegal IMEI information in the MSC to enable the Check IMEI function for the carrier. The Check IMEI function enables the MSOFTX3000 to obtain the IMEI from the mobile devices and sends the IMEI to the EIR for the device status check. The embedded EIR of the MSOFTX3000 can save up to 20.000 records.
5.2.3 Handover
Overview
Handover indicates the MS hands over from one radio channel to another because of the network signal problem or subscriber's removal during the call. In respect of the GSM network and the UMTS network, the handovers provided by MSOFTX3000 for network side consist of the following:
! ! !
Intra-GSM handover Intra-UMTS handover Handover between the UMTS and the GSM
In respect of the MSC, the handovers performed by the MSC consists of the following:
! ! !
Intra-MSC handover Inter-MSC basic handover Subsequent handover.
Intra-MSC Handover
Intra-MSC handover indicates that the radio channel of a mobile subscriber hands over from the current BSS/RNS to another BSS/RNS of the same MSC. The whole handover is controlled by one MSC. The intra-MSC handover can be divided into intra-MSCa handover and intra-MSCb handover. The MSC in which a call is established firstly is called a controlling MSC (Anchor MSC). The handover that occurs in the controlling MSC is called intra-MSCa handover. The handover that occurs in the non-controlling MSC is called intra-MSCb handover.
Inter-MSC Basic Handover

Inter-MSC handover indicates that the handover occurs when a mobile subscriber moves from the BSS/RNS coverage area of one MSC to the BSS/RNS coverage area of another MSC during communication. In the inter-MSC basic handover, the controlling MSC (MSCa) controls the whole handover procedure, and it must perform the following:
! !
Sending handover request from the RNC Selecting the destination MSC
Issue 03 (2006-09-30)
5-13

! ! !
Originating a handover resources request to the non-controlling MSC (MSCb) through the MAP signaling Establishing the inter-MSC bearer Call control after the handover
The MSCb must establish the wireless side resources required for the handover, and coordinate with the controlling MSC to perform the call control after the handover.
Subsequent Handover
The subsequent handover indicates the inter-MSC handover originated by the non-controlling MSC after the inter-MSC basic handover. The subsequent handover consists of:
! !
Subsequent handover back to controlling MSCa Subsequent handover to the third party (non-controlling MSCb')
The procedures of the subsequent handover back to MSCa are as follows: Step 1 MSCb responds to the handover request of the BSS or the RNS. Step 2 MSCb originates the "subsequent handover back to MSCa" to MSCa through the MAP signaling. Step 3 MSCa instructs the local BSS and the RNS to allocate the resources. Step 4 MSCa notifies MSCb to send a handover command. Step 5 MSCb releases the bearer between MSCa and MSCb. ----End The procedures of the subsequent handover to the third party (MSCb') are as follows: Step 1 MSCb responds to the handover request of the BSS or the RNS. Step 2 MSCb originates the "subsequent handover to the third party (MSCb')" to MSCa through the MAP signaling. Step 3 MSCb' instructs the local BSS and the RNS to allocate the resources. Step 4 MSCb' notifies MSCb to send a handover command. Step 5 MSCb releases the bearer between MSCa and MSCb. ----End
5.2.4 Call Processing

Call Connection
The MSOFTX3000 supports incoming and outgoing call connection functions of both common services and IN services. The MSOFTX3000 provides the following call connection functions of local call, outgoing call, incoming call and incoming tandem office call:
!
Querying MSRN number of mobile subscriber based on an MSISDN number and then connects the call to the VMSC according to the MSRN number
5-14
Issue 03 (2006-09-30)

! ! ! ! ! !
Originating call attempt based on IMSI/TMSI number of mobile subscriber and location area/service area where the subscriber is roaming Pre-paging function Emergency calls and special service calls defined by carriers Alarm function for emergency calls or malicious calls DN tone sending and failure tone sending Delay ringing function
Number Analysis
The MSOFTX3000 provides powerful number analysis function that has various applications:
! ! ! ! ! ! ! ! ! ! ! ! !
Supports receiving and storing at most 32-digit number Supports at-most 32-digit number analysis Supports 30000 called number prefixes Supports 4096 GT codes Supports service check function Supports call authority check function Supports preprocessing function for incoming number and outgoing number Supports caller number discrimination function Supports black and white list call barring function Supports the restriction of minimum number length and maximum number length Supports changing numbers (caller numbers, callee numbers and roaming numbers) based on number location or specified characters Supports changing caller number or callee number based on association relationship between them in number analysis range Supports changing caller type, caller address property indicator and callee address property indicator in the sent inter-office originate address message IAM/IAI
Route Selection
The MSOFTX3000 can select route to connect calls based on number analysis result and caller information. The route selection function includes:
! ! ! ! ! !
Supports intra-office route selection function (to the BSC/RNC that the MSC belongs to) and inter-office route selection function (to other office) Supports route selection function according to sequence or percentage Supports dynamic route selection based on time Supports avoidance peer route alternative function Supports multi-gateway static route function, and inter-gateway route selection based on random, percentage and alternate selection policy Supports support optimal route function
Issue 03 (2006-09-30)
5-15
5.2.5 Charging
Types of CDRs
The MSOFTX3000 supports more than 40 types of original CDRs, and meets various requirements of carriers. Table 5-1 lists scenarios of various original CDRs: Table 5-1 Original CDR generation scenario Type Of Original CDR Mobile originated call (MOC) record Generation Scenario If a non-IN mobile subscriber originates a call, and the call is answered, when the call ends or the timer of long time call CDRs expires, the MSC generates a CDR called mobile-originated call record or MOC CDR for the caller. If a non-IN mobile subscriber receives a call, when the call ends or the timer of long time call CDRs expires, the MSC generates a CDR called mobile-terminated call record or MTC CDR for the callee. During a call connection, assume that:
! ! !
Mobile terminated call (MTC) record
Mobile originated call forwarding attempt
B is a non-IN mobile subscriber. B registers the call forwarding service. C is the forwarded-to destination code.
A calls B, and the call is forwarded to C by the MSC serving B. C answers the call. When the call ends or the timer of long time call CDRs expires, the MSC generates a CDR called call forwarding record or CFW CDR for B. If A, B, and C are mobile subscribers served by the same MSC/VLR, when the call ends or the timer of long time call CDRs expires, the MSC generates an MOC CDR for A, a CFW CDR for B, and an MTC CDR for C. SMS MOC record If a mobile subscriber sends an SM to the SMC successfully, the MSC generates a CDR called SMS MOC record or MO_SMS CDR. Short message communication uses the signaling channel to transfer characters. Compared with the common call CDR, the short message CDR consists of SM content, SM operation result, number of SM bytes, and SMSC address. SMS MTC record If a mobile subscriber receives an SM from the SMC successfully, the MSC generates a CDR called SMS MTC record or MT_SMS CDR. When an incoming trunk originates a call, the MSC (TMSC) connects the call to certain outgoing trunk after analyzing the call. That is, the call is neither originated nor terminated in the local MSC. If the type of incoming and outgoing office directions is "Local network", when the call ends or the timer of long time call CDRs expires, the MSC generates a CDR called transit
Transit call attempt
5-16
Issue 03 (2006-09-30)
Type Of Original CDR Inter-network transit call attempt
Generation Scenario record or TRANSIT CDR. When an incoming trunk originates a call, the MSC (TMSC) connects the call to certain outgoing trunk after analyzing the call. That is, the call is neither originated nor terminated in the local MSC. If the types of incoming and outgoing office directions are "Other network" (Other PLMN or PSTN), when the call ends or the timer of long time call CDRs expires, the MSC generates a CDR called inter-network transit call record or OT_TRANSIT CDR. When an incoming trunk originates a call, the MSC (GMSC) connects the call to certain outgoing trunk after analyzing the call. That is, the call is neither originated nor terminated in the local MSC. If the type of incoming office direction is "Local network", and type of outgoing office direction is "Other network" (Other PLMN or PSTN), when the call ends or the timer of long time call CDRs expires, the MSC generates a CDR called outgoing gateway record or GWO CDR. When an incoming trunk originates a call, the MSC (GMSC) connects the call to certain outgoing trunk after analyzing the call. That is, the call is neither originated nor terminated in the local MSC. If the type of incoming office direction is "Other network" (Other PLMN or PSTN), and type of outgoing office direction is "Local network", when the call ends or the timer of long time call CDRs expires, the MSC generates a CDR called incoming gateway record or GWI CDR.
Note: The MSOFTX3000 only provides the roaming record for the 3G network subscribers.
OutGtewayRecord
IncGatewayRecord
Roaming record
Assume that a non-IN roaming mobile subscriber is called, and the call must be routed and connected to the GMSC of the home PLMN. When the call ends or the timer of long time call CDRs expires, the GMSC generates a CDR called roaming record or ROAM CDR for the callee. Call attempt record Determining that a call type is transfer call, inter-network transit call, outgoing gateway exchange call, or incoming gateway exchange call, the MSC generates a CDR called call attempt record or ATTEMP CDR if the call fails to be set up. The ATTEMP CDR is used to record the network resources occupation for an unsuccessful call. In essence, the ATTEMP CDR is a TRANSIT CDR, an OT_TRANSIT CDR, a GWO CDR or a GWI CDR. The only difference is that the release cause value in the ATTEMP CDR is unsuccessfulCallAttempt. Based on the value, the billing center can pick up the ATTEMP CDR.
Issue 03 (2006-09-30)
5-17
Type Of Original CDR IN pickup record
Generation Scenario Assume that:

! ! !
The MSC in office A cannot function as the SSP. The MSC in office B can function as the SSP. Office A routes the IN calls in office A to office B through the Overlay mode. The MSC in office B triggers the IN service.
When a non-IN subscriber in office A or incoming trunk calls IN subscriber X (non-forwarding call), office A routes the call to office B. Therefore, office A cannot get the precise location of IN mobile subscriber X. After triggering the IN service, office B can get the precise location of IN mobile subscriber X. If subscriber X answers the call, when the call ends or the timer of long time call CDRs expires, the MSC in office B generates a CDR called IN pickup record or AI_MOI CDR. The CDR is provided for the billing center, and used to charge the caller precisely. The AI_MOI CDR is generated only after the incoming trunk in Overlay mode triggers the called IN service. When the mobile IN network adopts networking of the destination network, the MSC does not generate the AI_MOI CDR. IN mobile-originated call record If an IN subscriber originates a call, and the call is answered, when the call ends or the timer of long time call CDRs expires, the MSC (SSP) triggering the IN service generates a CDR called IN mobile-originated call record or AI_MOC CDR for the caller. In essence, the AI_MOC CDR is an MOC CDR. The only difference is that the subscriber type in the AI_MOC CDR is CAMEL user. Based on the value, the billing center can pick up the AI_MOC CDR. IN mobile-terminated call record If an IN subscriber receives a call, and the call is answered, when the call ends or the timer of long time call CDRs expires, the MSC (SSP) triggering the IN service generates a CDR called IN mobile-terminated call record or AI_MTC CDR for the callee. In essence, the AI_MTC CDR is an MTC CDR. The only difference is that the subscriber type in the AI_MTC CDR is CAMEL user. Based on the value, the billing center can pick up the AI_MTC CDR. IN call forwarding record Assume that:
! ! !
B is an IN mobile subscriber. B registers the CFW service. C is the forwarded-to destination code.
A calls B and the call is forwarded to C. C answers the call. When the call ends or the timer of long time call CDRs expires, the MSC triggering the IN service generates a CDR called call forwarding record or CFW CDR for B. In essence, the AI_CFW CDR is a CFW CDR. The only
5-18
Issue 03 (2006-09-30)
Type Of Original CDR
Generation Scenario difference is that the subscriber type in the AI_CFW CDR is CAMEL user. Based on the value, the billing center can pick up the AI_CFW CDR.
Location request
If the MSC receives a location request of any type from the BSC or the RNC, the MSC generates a CDR called location request record or LCS CDR for the location operation. The LCS CDR records the location method, location time, and location results.
Supplementary service actions
When a non-IN mobile subscriber executes call unrelated operation, such as registering, cancelling, activating and deactivating the SS, the MSC generates a CDR called supplementary service actions or SS_ACT CDR for the operation. When confirming that a mobile subscriber has registered the hot billing service, the MSC generates a CDR called hot billing record or HOTBILL CDR if the subscriber succeeds in originating any call, such as MOC, MTC, SMS-MO, and SMS-MT. For a subscriber who has registered the hot billing service, the MSC sends the CDRs related to the call to the billing center immediately. In essence, the HOTBILL CDR is an MOC CDR, MTC CDR, MO_SMS CDR, or MT_SMS CDR. The only difference is that the hot billing flag in the HOTBILL CDR is true. Based on the information, the billing center can pick up the HOTBILL CDR.
Hot billing record
Check IMEI record
If the MSC executes the Check IMEI flow in the process of the location update and the service access, the MSC generates a CDR called check IMEI record or CHECK_IMEI CDR. During a call connection, assume that:
! !
HLR interrogation
The callee is a non-IN mobile subscriber. The MSC requests route information from the HLR through The MAP signaling. The HLR returns the MSRN to the MSC through the MAP signaling.
The MSC generates a CDR called HLR interrogation record or QUERY_HLR CDR. In the example, if the callee is an IN mobile subscriber, the MSC needs to query the HLR twice. By default, the MSC generates a QUERY_HLR CDR when querying the HLR for the second time. If you set Ticket control flag to Generate HLR interrogation record after getting T-CSI with MOD GBILLCTRL, the MSC generates a QUERY_HLR CDR when querying the HLR for the first time. That is, the MSC generates two QUERY_HLR CDRs.
Issue 03 (2006-09-30)
5-19
Type Of Original CDR TCAMEL callee record
Generation Scenario During a call connection, if a mobile subscriber that has registered the CAMEL service (with the T-CSI), receives a call, and answers the call, when the call ends or the timer of long time call CDRs expires, the GMSC (SSP) triggering the IN service generates a CDR called TCAMEL callee record or TCAMEL CDR. During a call connection or a call, if the MSC in office A uses the public device resources (such as conference resources) in office A or in the MSC of office B, the MSC in office A generates a CDR called common equipment usage record or COMMONEQUIP CDR. If the MSC achieves call related handover, call hold, call waiting, multiparty call establishment, and multiparty call split, the MSC generates a CDR called handover event record or HO_EVENT CDR. The HO_EVENT CDR exists in the format of an original CDR. Although the iGWB merges the HO_EVENT CDR into the MOC CDR and MTC CDR, there is no HO_EVENT CDR in the final CDR.
Common equipment usage record
Handover event record
Failure record
When a mobile subscriber fails to activate the location service, SS, or USSD service, the MSC generates a CDR called failure record.
Charge Advice Services

Charge advice services consist of Advice of Charge Information supplementary service (AoCI) and Advice of Charge Charging supplementary service (AoCC):
!
AoCI: This service provides real-time display of charge. After subscribers register AoCI services, network side delivers rate information and MS auto calculates the charge. Subscribers can display charge through menu and accumulate charge. CDR charges of AoCI services are settled at network side. Mobile subscribers only obtain charging information of this call. AoCC: CDR charges of AoCC services are settled at terminal MS. MSC is responsible for delivering rate information. Coordination of terminal MS supporting Phase2 standard and a special SIM card is required. AoCC is a simple mode to realize leased phone or prepaid services.
Hot Billing
After the MSOFTX3000 sends the original CDR generated during call to the iGWB, the iGWB allocates one single channel to store the final CDR and sends them to the billing centre at real time to realize the billing for the subscriber.
5-20
Issue 03 (2006-09-30)
5.2.6 SSP
Overview
The MSOFTX3000 supports the mobile SSP functions,
! ! !
including the following:
Call control function (CCF) Service switching function (SSF) Specialized resource function (SRF)
The MSOFTX3000 supports CAMEL 4 and is compatible with CAMEL 3, CAMEL 2, and CAMEL 1.
Overlay Networking Mode

The Overlay network mode is suitable for the transitional stage when the VMSC/GMSC cannot or does not need to act as an SSP. In this mode, the VMSC/GMSC routes IN calls to the SSP (the process is called Overlay) and then the SSP triggers IN services. In Overlay network mode, the MSOFTX3000 acts as a VMSC/GMSC and does not need to provide the SSP function in Overlay network mode. Figure 5-1 shows the networking diagram: Figure 5-1 Networking model of Overlay network mode
SCP
SS7 signaling network
SSP
SSP
VMSC
VMSC
GMSC
GMSC
Target Networking Mode

The target networking mode is the best choice when all local MSCs can act as SSPs. In this mode, the MSC triggers IN services based on the CAMEL subscription information (CSI) in the HLR. Figure 5-2 shows the networking diagram:
Issue 03 (2006-09-30)
5-21
Figure 5-2 Networking model of target network mode

SCP
SS7 signaling network
GMSC/ SSP VMSC/ SSP VMSC/ VMSC/ SSP SSP
GMSC/ SSP VMSC/ SSP
In this mode, the VMSC acts as the SSP to trigger MO, MF, and MVT calls. The GMSC acts as the SSP to trigger MT and MF calls. MO, MT, MF, MVT are short for Mobile Originating, Mobile Terminating, Mobile Forwarding, and Mobile VMSC Terminating.
5.3 Description of New Features

5.3.1 List of New Features
Table 5-2 lists the new features supported by the MSOFTX3000. Table 5-2 List of the new features supported by the MSOFTX3000 Name of Feature User Differentiated Service Enhanced Flow Control Inter-System Handover Based on Services Mobile Virtual Network Operator Call Failure Short Message Indication MNP Service IP Fax Multiple Time Zones Paging Classification Dual Transfer Mode Earliest Supporting Version V100R005 V100R005 V100R005 V100R005 V100R005 V100R005 V100R005 V100R005 V100R005 V100R005
5-22
Issue 03 (2006-09-30)
Name of Feature LCS Services INClassMark Trigger IN Service Configuration Rollback Alarm Association Service Management of Area-based Authority Device Archive Management Client Software Automatic Adaptation Management M2000 Online Monitor and Management for Logging Subscriber Mini-A-Flex Networking Mini-Iu-Flex Networking Iu-Flex Networking Network Sharing In Connected Mode SCCP Policing MAP Policing ECT Service SOR Function TFO Function TrFO Function eMLPP Function IN Announcement Charging IN DCH Setting 2G/3G Network Access Control Based on Different Subscribers Half-Rate-Based Subscriber Access Classification Specified Circuit Dialing Test Continuity Check
Earliest Supporting Version V100R005 V100R005 V100R005 V100R005 V100R005 V100R005 V100R005 V100R005 V100R003 V100R003 V100R003 V100R003 V100R003 V100R003 V100R003 V100R003 V100R003 V100R003 V100R003 V100R003 V100R003 V100R003 V100R003 V100R003 V100R003
Issue 03 (2006-09-30)
5-23
5.3.2 V100R005 Version

User Differentiated Service
With the development of the market and the change of the competition environment, carriers must provide services of different levels to subscribers with different requirements. The user differentiated service is designed to meet the requirements of carriers. The service provides a specific service strategy for subscribers in a specific group. For example, high quality services are offered to subscribers of high priority. The MSOFTX3000 determines the priority of a call based on the following information:
! ! !
Subscription information (Category, eMLPP, CARP and E-category) Call type (such as MO, MT and SMS) Access network type (2G and 3G)
Carriers can provide the following service strategies that correspond to the priority level:
!
The call can be set up quickly in the radio channel. To shorten the time for setting up the call, the system skips some processes including the authentication, encryption and TMSI reassignment. The ability of contention of a channel is offered. During congestion, the system allows the call to pre-empt the call resource that can be occupied. The system prefers the resource of calls of the lowest priority for contention. The queuing ability is offered when the system fails to select a route. When the system fails to select a route, the call is retained. The system arranges the call to wait for an idle circuit in the queue. As soon as an idle circuit is available, the call is connected; or the call is released because of timeout. When the system handles the calls in the queue, calls of high priority level are set up faster than those of low priority level. It is assured that a subscriber of high priority can obtain better network services, because the differentiated access function based on half rate is provided for the 2G networking. Access priority is offered when the system performance is unsatisfying. This can ensure that subscribers with high-end services can obtain better network services.
! !
Enhanced Flow Control

The MSOFTX3000 may be overloaded for some reasons, such as the following:
! ! !
The traffic becomes heavy. The bandwidth for transferring signaling becomes less because of link faults. Many services become invalid due to overload at peer network element.
The enhanced flow control function helps the MSOFTX3000 to detect the overloads, and carry out effective traffic balance and flow control. This can ensure the MSOFTX3000 to run at a high service processing rate in a secure way. The enhanced flow control supports differentiated processing for subscribers of different priority levels in the case of overload. It allows the subscribers of high priority to connect to the network. There are examples as follows:
!
The traffic load causes that the CPU occupation rate of the service processing boards (such as the WCCU, WCSU and WCDB) of the MSOFTX3000 exceeds the overload threshold. The enhanced flow control function helps the MSOFTX3000 detect the overload and activate flow control at the preliminary stage of overload. As a result, the
5-24
Issue 03 (2006-09-30)
CPU occupation rate of the board does not increase, and a high service success rate and a stable CPU occupation rate can be retained.
!
When the MSOFTX3000 is upgraded or cut over, there may be a large number of location update requests. The links of the HLR are congested because the location update flow occupies a large scale of bandwidth of the links from the MSOFTX3000 to the HLR. This leads to many location update failures and slows down the service recovery. The enhanced flow control function helps the MSOFXT3000 to detect the Hard To Reach (HTR) occurring to location update flows at some HLRs and activate flow control. This can retain a relatively high success rate of location updates when the load of the links is reduced. When processing service requests from the BSC/RNC, the MSOFTX3000 can distribute resources in a balanced way based on the current load of the WCCU and WCSU. This can ensure secure operation and make full use of the processing capability of the boards.
Inter-System Handover Based on Services

The inter-system handover indicates that the handover occurs when mobile subscribers in the network move from a 3G coverage area to a 2G coverage area, or from a 2G coverage area to a 3G coverage area. The inter-system handover provides carriers with a solution to balance the service load between the GSM network and the UMTS network. For the MSOFTX3000, whether the inter-system handover is allowed, and the preferred network type (GSM or UMTS) are determined by the following:
! ! !
IMSI segment Subscriber category Service type
If the current network is not the preferred network in configuration (for example, a subscriber registers to the GSM network at present, but the UMTS network is selected as the preferred network for data service when the carrier configures data), when the mobile subscriber uses the data service, the MSOFTX3000 sends the assignment request message to require the BSC or RNC to start the handover. That is, to hand the call over to the UMTS network. The service-based inter-system handover supported by the MSOFTX3000 provides the following services:
! ! ! ! ! ! ! !
Service handover from 2G speech service to the UMTS network Service handover from 3G speech service to the GSM network Service handover from 2G nontransparent transmission data service to the UMTS network Service handover from 3G nontransparent transmission data service to the GSM network Service handover from 2G transparent transmission data service to the UMTS network Service handover from 3G transparent transmission data service to the GSM network Service handover from 2G VP service support fallback to the UMTS network Service handover from 3G VP service support fallback to the GSM network
Mobile Virtual Network Operator

The mobile virtual network operator (MVNO) is a networking mode. In this mode, carriers provide their services by sharing all or part of their network resources. For subscribers, the MVNO service is transparent and realizes smooth service provision. For carriers, the MVNO
Issue 03 (2006-09-30)
5-25
service reduces the cost on network construction and helps build a network quickly in a densely populated area. The MVNO feature supported by the MSOFTX3000 provides the following functions:
! !
The network name can be set on the MSC side and is sent to mobile stations by using the MM_information message. The MVNO CDR can be sorted. That is, when the iGWB generates CDRs, the NetworkOperatorId is filled in the CDR to identify CDRs of local subscribers or MVNO subscribers. In this case, when sorting the CDRs, the iGWB saves the CDRs to different directories based on the NetworkOperatorId information. The charging centers of different carriers obtain the required CDRs from the directories assigned to them.
Call Failure Short Message Indication

The call failure short message (SM) indication is to prompt the callee that there is a missed call through the SM. That is, when a caller originates a call, the call may fail because of the following causes:
! ! ! !
The phone of the callee is powered off. The callee is unreachable. The callee does not answer the call. The network is busy.
When the call fails, the network side sends a specified SM to the callee to prompt the date, the time and the calling number of the missed call. The call failure SM indication service is excluded from the call forwarding service and the voice mailbox (VM) service. That is, the system can trigger the call failure SM indication service only when the call forwarding service and the VM service are not employed. When the MSOFTX3000 serves as the GMSC or terminating VMSC, the system triggers the SM indication service in the following abnormal cases:
! ! ! ! ! !
GMSC: After obtaining the route information, it is found that the callee is absent (for example, the phone is powered off). Terminating VMSC: During an incoming call to the office, it is found that the callee's phone is powered off or does not have the roaming authority. Terminating VMSC: During an incoming call to the office, it is found that the callee does not respond the paging, or the response times out. Terminating VMSC: During an incoming call to the office, it is found that the callee is in conversation. Terminating VMSC: During an incoming call to the office, it is found that the network is congested. Terminating VMSC: After an incoming call to the office, it is found that the callee does not answer the call.
MNP Service
The mobile number portability (MNP) allows a mobile subscriber to change the network in a country or an area. In addition, the subscriber can retain the original MSISDN. When the subscriber uses the MNP service, all services provided by the original network are handed over to the new network. At the same time, the current network assigns a new IMSI number to the MNP subscriber.
5-26
Issue 03 (2006-09-30)
In the same network, MNP subscribers are not different from non-MNP subscribers in service application. There are, however, some differences in quality service, such as additional call setup delay for MNP subscribers. The MNP service supported by the MSOFTX3000 provides the following functions:
! !
No need to change MSISDN: The MSISDN does not vary with carriers or networks. Independent subscription service: The original network does not have any impact upon services of the subscriber. If the services supported by the original network are not supported by the new network, the subscribers in the new network can choose the services. Ported many times: A network allows its numbers to be ported out and numbers of another network to be ported in. One MSISDN can be ported many times. It can also be ported back and forth among multiple networks. Independent service: It does not conflict with any other mobile service.
IP Fax
IP fax is the fax service over IP. It is important to ensure the quality of data transmission, because the quality of data transmission determines the fax quality. The data stream redundancy is a solution to the data packet loss during transmission. The MSOFTX3000 supports the transmission of data redundancy. This can effectively enhance the transmission quality, and reduce or avoid service interruptions due to low quality of data transmission. During a call process, the MSOFTX3000 determines whether to send redundancy parameter 2198 of data service to the MGW based on the data configuration. It also determines whether to notify the MGW to perform fax event detection after the call is started. After the MGW reports the fax tone detection event or fax status detection event, the MSOFTX3000, based on the report, can send the CODEC attribute modification request to the MGW to support the data service redundancy.
Multiple Time Zones

The MSOFTX3000 can work for multiple time zones or areas deploying different daylight saving time (DST) schedules in one time zone. The multiple time zones provide the following functions:
!
The time stamp in CDRs is consistent with the actual time in the place where the subscriber is located, because auto time adjustment is performed in CDRs based on information like, the subscriber location and whether the DST is adopted. The time stamp reported to the SCP is allowed to contain the DST information to ensure that the SCP can charge calls accurately. The accuracy of time report is ensured. The terminal time can be changed based on the subscriber location.
! ! !
Paging Classification
In 3GPP 48.008 specifications, the optional IE Channel Needed is defined in the paging message. This IE indicates the radio channel type that may be used in the subsequent service flows. When the BSC supports the Channel Needed IE in the paging message, if the traffic is heavy, the MSOFTX3000 performs flow control for the services of low priority, such as short message service. This can reduce the load of the BSC and ensure access of services of high priority. Based on the Channel Needed IE, the BSC can also reduce unnecessary occupation of the TCH bearer channel.
Issue 03 (2006-09-30)
5-27
There are examples as follows:

!
During a mobile termination call, the MSOFTX3000 can identify whether the full rate channel or dual rate channel is used in subsequent services by using the Channel Needed IE in the paging message. For the SMS reception service, USSD service or the LCS, the MSC identifies that the SDCCH bearer channel is used in subsequent services by using the Channel Needed IE in the Paging message. If the BSC does not support the Channel Needed IE, the Paging message is not required to carry the IE.
Dual Transfer Mode

The MSOFTX3000 supports the dual transfer mode (DTM) function defined in the 3GPP TS 03.55 specifications. The DTM indicates that in the 2G network, a terminal supports both CS and PS domains to trigger services at the same time. That is, the terminal can retain the calls of the CS domain as well as the data transmission of the PS domain.
LCS Services
By working with other devices, such as the BSC, RNC and GMLC, the MSOFTX3000 can support not only the LCS services based on the Iu interface, but also LCS services based on the A interface. This can allow the MSOFTX3000 to provide the following function to store location information of subscribers:
! ! ! !
Mobile callee location service: The external device can locate a mobile terminal. Mobile caller location service: The mobile terminal originates the locating request. Emergency call location service: The network side can locate the subscriber in an emergency call. Subscriber privacy protection: The party who requests locating can be restricted based on the requirement on the subscriber privacy.
INClassMark Trigger IN Service

The INClassMark trigger IN service function uses the SS-CODE IE in the forwarding information of a subscriber to identify whether the subscriber is an IN one. If SS-CODE is plmn-specificSS-4 (0xF4) in the subscription information, the subscriber is an IN subscriber; otherwise, the subscriber is a common one. During location update, the HLR sends the data to the VLR for record. During a call connection, if the subscriber data contains the SS-CODE with the extended option, the MSOFTX3000 adds a service attribute SERVICE13 for the subscriber. By using the caller character handle data and caller character analysis data configured on the MSOFTX3000 side, the MSOFTX3000 can trigger IN services for the subscriber. If a subscriber uses INClassMark to trigger IN services and subscribes forwarding services, the application scenario is as follows:
!
In the early forwarding process, when the MSOFTX3000 requests the HLR to provide the roaming number, the HLR returns the subscription data to the MSOFTX3000 through an SRI. After call forwarding occurs, the MSOFTX3000 judges whether the IN flow needs to be triggered for the subscriber based on the SS-CODE with the extended option. If it is required to trigger the IN flow, the MSOFTX3000 triggers the MF IN flow based on the caller attribute. If it is not required to trigger the IN flow, the MSOFTX3000 forwards the call based on common flow.
5-28
Issue 03 (2006-09-30)

!
In the late forwarding, the subscriber data is sent to the VLR through location update. After call forwarding occurs, the MSOFTX3000 judges whether the IN flow needs to be triggered for the subscriber based on the SS-CODE IE. If it is required to trigger the IN flow, the MSOFTX3000 triggers the MF IN flow based on the caller attribute. If it is not required to trigger the IN flow, the MSOFTX3000 forwards the call based on common flow.
Configuration Rollback
During deployment or maintenance, some errors of data configuration may occur. In this case, a function is required to return the configuration to the state before the errors. The function is called configuration rollback (CR). The MSOFTX3000 supports CR to avoid traffic loss due to mistakes and improve the security of the network. There are examples as follows:
!
Configuration in advance: Data can be configured before preset cutover, and the configurations are not effective at once. You can determine the time for validating the configurations. Swiftly to be effective: After confirmation, the configured data can be effective within the designated time, and enter the state of trial run and observation. Swift rollback: When errors of configured data occur and cause abnormal operations during trial run, the system can be swiftly rolled back to the original data, so as to avoid impacts on the system service. Comparison of configured data: You can compare the data before and after the modification to make sure what is changed. This can help you locate the errors easily. Activation/rollback table: When data configuration is performed by several teams, the MSOFTX3000 supports that each team has the specific data table for configuration, so each team can work independently, and activate or roll back its own configured table.
! !
! !
Alarm Association Service

The alarm association service helps O&M staff to quickly locate and analyze a problem. The MSOFTX3000 provides the following functions:
! !
Filtering and shielding the child alarm. After receiving the parent alarm, the MSOFTX3000 can shield the received child alarm within a specified period. Reactivating the child alarm: If the recovery information of the child alarm is not received within a specified period, the MSOFTX3000 reactivates the child alarm that is processed in related recovery. Querying alarm-related information: If you query the information relevant to an alarm, the MSOFTX3000 lists all alarms relevant to the alarm. This helps you locate and analyze problems easily. Hardware alarm correlation:

Alarms for faults of upper level boards and alarms for faults of lower level boards can be correlated. Alarms for board faults, network port faults, and faults of internal communication links can be correlated. Alarms for CPC faults and faults of links provided by the CPC can be correlated.
Gateway alarm correlation: Alarms for gateway faults and faults of links and circuits of the gateway are correlated.
Issue 03 (2006-09-30)
5-29

!
The alarm correlation function can be enabled or disabled by using configuration commands.
Management of Area-based Authority

The MSOFTX3000 terminal system supports the management of area-based authority. That is, the system resource of the MSOFTX3000 is divided into sections based on geographical areas. Operators in each area can use the system resource independently. The system resource operations in one area do not affect those in another area. In this case, operators in one area can only perform configurations and alarms for the area only, and cannot affect the information in another area. This can ensure the security of the system resource operation.
Device Archive Management

Through the NMS, the MSOFTX3000 can obtain the detailed information,
! ! ! ! ! ! ! ! !
such as:
Basic information of device Connection information Module information Configuration information Peer devicet information Host version information Cabinet information Frame information Information of boards and the Flash electronic label of boards
After receiving the command from the NMS (M2000), the BAM creates XML files of device archives. Then, the NMS can send a command to the BAM, instructing it to upload the files to a specified folder of the NMS.
Client Software Automatic Adaptation Management

For maintenance, the client software is distributed to different types of workstations at different places. The MSOFTX3000 supports the function of the client software automatic adaptation. This function enables carriers to control the distributed client software versions in a centralized way and improve the efficiency of the maintenance. The MSOFTX3000 establishes a version control mechanism on the BAM to achieve the function of the client software automatic adaptation. When O&M staff logs on to the BAM from a client and detects that the version of the client software differs from that of the BAM, the client prompts users to download the version that matches that of the BAM. Then there are two cases:
!
The subscriber confirms the loading. The system auto upgrades the client software, and then uses the upgraded version to log on to the BAM.
The subscriber refuses the loading. The system can use the mismatched version to log on to the BAM forcibly.
5-30
Issue 03 (2006-09-30)
M2000 Online Monitor and Management for Logging Subscriber

The MSOFTX3000 can cooperate with the Huawei iManager M2000 (M2000 for short) to provide the function of the online monitor and management for logging subscriber. The function has the following features:
!
The M2000 manages the following:

IP port Port status Version of network elements (NEs) Number of NEs of the same version Number of boards Faulty boards Cell status Distribution condition Resources capacity of each port (such as the number of 2-Mbit/s ports, signaling ports, GE interfaces, FE interfaces, and CPUs)
! ! !
The M2000 manages the input information of users, for example, the information of leased circuits. You can refresh managed the resources data at the MSOFTX3000 side manually or at a set time. After refreshing the managed resources data, the M2000 can show the changed information in audio and visual way. For example, it can show added, deleted and modified information with different colors. The M2000 can export information.
5.3.3 V100R003 Version

Mini-A-Flex Networking
Mini-A-Flex is also called intra-MSC A-FLEX. It is a GSM networking mode that can enhance the reliability of A interface. Normally, the MSOFTX3000 is connected with the BSC through the MGW and one BSC can only be connected with one MGW. If the MGW connected with the BSC is faulty, all the services handled by the BSC are completely interrupted. To avoid the BSC service failure caused by the MGW upgrade and MGW failure, the MSOFTX3000 supports the Mini-A-FLEX networking, which allows one BSC to connect with multiple MGWs controlled by a same MSC. These MGWs adopt the load sharing mode for service management. When one MGW is faulty, other MGWs can take up the service. Figure 5-3 shows the Mini-A-Flex networking:
Issue 03 (2006-09-30)
5-31
Figure 5-3 Mini-A-Flex networking

MSOFTX3000
MGW 1
MGW 3
MGW 2
BSC 1 BSC 2
BSC 3
The Mini-A-Flex networking performs the following functions:

!
One BSC can be connected with many MGWs. The MSOFTX3000 can select the circuit resources of the corresponding MGW as needed. Thus the system disaster recovery function is provided based on the bearer network layer. When the BSCs where a caller and a callee are located are connected with a same MGW, the MSOFTX3000 selects corresponding A interface circuits on the same MGW first. This can avoid wasting the circuit resources between MGWs. During the incoming and the outgoing trunk call, handover and call reconnection, if the MGW of one call party is settled, the MSOFTX3000 can optimize the selection of the MGW for selecting A interface circuits. That is, the MSOFTX3000 selects the common MGW first. This can avoid wasting the speech channel resources between MGWs.
Mini-Iu-Flex Networking
Mini-Iu-Flex is also called intra-MSC Iu-FLEX. It is a WCDMA networking mode that can enhance the reliability of Iu interface. Normally, the MSOFTX3000 is connected with the RNC through the MGW and one RNC can only be connected with one MGW. If the MGW connected with the RNC is faulty, all the services handled by the RNC are completely interrupted. To avoid the RNC service failure caused by the MGW upgrade and MGW failure, the MSOFTX3000 supports the Mini-Iu-FLEX networking, which allows one RNC to connect with multiple MGWs controlled by a same MSC. These MGWs adopt the load sharing mode for service management. When one MGW is faulty, other MGWs can take up the service. Figure 5-4 shows the Mini-Iu-Flex networking:
5-32
Issue 03 (2006-09-30)
Figure 5-4 Mini-Iu-Flex networking

MSOFTX3000
MGW 1
MGW 3
MGW 2
RNC 1 RNC 2
RNC 3
The Mini-Iu-Flex performs the following functions:

!
One RNC can be connected with many MGWs. The MSOFTX3000 can select the circuit resources of the corresponding MGW as needed. Thus the system disaster recovery function is provided based on the bearer network layer. When the RNCs where a caller and a callee are located are connected with a same MGW, the MSOFTX3000 selects corresponding bearer resources on the same MGW first. This can avoid wasting the bearer resources between MGWs. During the incoming and the outgoing trunk calls, handover and call reconnection, if the MGW of one call party is settled, the MSOFTX3000 can optimize the selection of the MGW for selecting bearer resources. That is, the MSOFTX3000 selects the common MGW first. This can avoid wasting the bearer resources between MGWs.
Iu-Flex Networking
The intra domain connection of RAN nodes to multiple CN nodes (Iu-Flex) is a networking mode where one RAN node can be connected with many CN nodes in a same domain. In the CS domain, Iu-Flex is also called MSC Pool. Figure 5-5 shows the Iu-Flex network architecture:
Issue 03 (2006-09-30)
5-33
Figure 5-5 Iu-Flex network architecture

MSC 3 MSC 2 MSC 1 MSC 6 MSC 5 MSC 4 MSC 7
CS poolarea 1 RAN node Area 1 RAN node Area 2
CS poolarea 2
RAN node Area 3
RAN node Area 4
RAN node Area 5
RAN node Area 6
RAN node Area 7
RAN node Area 8
PS pool-area 1
PS pool-area 2
SGSN 1 SGSN 2
SGSN 3 SGSN 4 SGSN 5
SGSN 6
As shown in Figure 5-5, MSC 1, MSC 2 and MSC 3 make up of one MSC pool, while MSC 4, MSC 5 and MSC 6 make up of another MSC pool. Each RAN node in an MSC pool is connected with all MSCs in the pool and the service load is shared among these MSCs. The Iu-Flex network allows multiple carriers to share the RAN resources. This networking mode has the following advantages:
! !
Multiple CN nodes can share the load of an RAN. This can improve the usage ratio of CN nodes and reduce the loss resulted from the fault of a single CN node. The service area of a single CN node is expanded. The number of CN node updates during roaming and the number of cross-CN node handovers are reduced. This subsequently cuts down the signaling flow of the core network.
Network Sharing In Connected Mode

The network sharing in connected mode provides the handover restriction function that restricts the subscriber access to the network in connected mode. At present, the roaming restriction of the mobile network means the roaming restriction controlled by the CN side in idle mode, such as ZC roaming restriction and enhanced roaming restriction. However, in the case that a subscriber is moving during a call, CN cannot restrict the roaming area. Thus during a call, the subscriber can enter the area where the subscriber cannot enter when idle. The networking sharing in connected mode can solve the problem. For example,
5-34
Issue 03 (2006-09-30)
when two 2G carriers share one 3G network, the carriers can control their subscribers to use their own 2G networks respectively by using the function. The function needs the cooperation of the MSOFTX3000 and the RNC. On the MSOFTX3000 side, the operator configures the information of roaming restriction that is in connected mode and the information of the share network. The MSOFTX3000 sends the roaming restriction information to the RNC. Based on the information, the RNC then completes the roaming restriction in connected mode. The share network information is used to set share network areas, which is the minimal roaming unit. The subscriber roaming restriction information is configured based on the IMSI number segment of a subscriber. The operator can achieve the roaming restriction function in connected mode by configuring the allowed share network area group.
SCCP Policing
When interconnecting with the HLR, VLR, MSC, SMC and SCP in the mobile network, the MSOFTX3000 can achieve the following by using the SCCP Policing function:
! ! !
Control the traffic of incoming signaling messages such as the MAP and the CAP messages generated by the HLR, VLR, MSC, SMC and SCP within a specified range. Avoid the congestion and overload of signaling links between the MSOFTX3000 and the HLR, VLR, MSC, SMC and SCP. Ensure the security of the signaling network.
The local MSC can start the SCCP shielding control in the SCCP layer when the following requirements are met:
! !
The MSOFTX3000 enables the SCCP policing function. The local MSC receives incoming signaling messages such as the MAP and CAP messages generated by other devices.
The SCCP shielding control is enabled based on the SPC, SSN and GT information in the SCCP calling and called addresses contained in the message. If the number of SCCP signaling packets received by the local MSC within a unit time exceeds a specified threshold, the MSOFTX3000 will discard the extra SCCP signaling messages and reject the subsequent message processing operations.
MAP Policing
The MSOFTX3000 supports the MAP Policing function. With this function, a local MSC can shield a given MAP operation request (such as getting MSRN or inserting subscriber data) from a given network element (NE) in the receiving direction. That is, when a given NE sends a given MAP operation request to a local MSC, the MSOFTX3000 can return a MAP dialogue reject response to the peer end. The function aims to shield unexpected incoming MAP messages sent to a local MSC, achieve self-protection and prevent resources exhaustion.
ECT Service
The explicit call transfer (ECT) is a supplementary service. It is applicable to the UMTS and the GSM network. Suppose that A calls B and C respectively. In any of the following two cases, A can make B and C connected and then quit the conversation by using the ECT function:
Issue 03 (2006-09-30)
5-35

! !
Both B and C are in conversation with A. Either B or C in conversation with A and the other is hearing the ringing of the call made by A.
The following are requirements of the ECT service:

! ! !
B and C can be local mobile subscribers, non-local mobile subscribers or PSTN subscribers. A has the authority of call hold supplementary service. A is not an IN service subscriber.
SOR Function
The support optimal route (SOR) is a routing selection function applicable to inter-network calls. The function has the following advantages:
! !
Decreasing the call alternative route between two networks and increasing the network usage ratio Cutting down call costs for callers
The SOR function has the following three flows:

!
Basic SOR flow: When a mobile subscriber calls a mobile subscriber, the GMSC of the PLMN where the caller is located fetches the called MSRN from the HLR to which the callee belongs. The GMSC then routes the call to the VMSC of the PLMN where the callee is located. Early forwarding SOR flow: If early forwarding occurs to the call between two mobile subscribers and the SOR charging rule is applicable to the call, the GMSC of the PLMN where the caller is located fetches the forwarded-to number of the callee from the HLR to which the callee belongs. The GMSC then routes the call to the MSC to which the forwarded-to number belongs. Late forwarding SOR flow: If late forwarding occurs to the call between two mobile subscribers and the SOR charging rule is applicable to the call, the GMSC of the PLMN where the caller is located fetches the forwarded-to number of the callee from the VLR to which the callee belongs. The GMSC then routes the call to the MSC to which the forwarded-to number belongs.
TFO Function
The tandem free operation (TFO) is an operation without the second encoding and decoding operations. It is a process of inband negociation of the adopted Codec mode between two Transcoders (TC) after the call is set up. For calls between two mobile subscribers, unnecessary speech encoding and decoding conversion can be avoided in the sending end and the receiving end. Thus the speech quality is promoted. However, without the TFO function, four encoding and decoding operations are needed for one call channel, as shown in Figure 5-6:
5-36
Issue 03 (2006-09-30)
Figure 5-6 Ordinary encoding and decoding speech operation

Transcoding Functions
PLMN A
Transcoding Function
PLMN B
MS/UE
MS/UE
ENCODING
Compressed Speech
DECODING
ENCODING ITU-T G.711 A-Law/u-Law
Compressed Speech
DECODING
The speech encoding performed by TC is lossy compression. Each encoding and decoding operation will decrease the speech quality and increase the transit delay. Though the TFO function does not require TC to perform encoding and decoding conversion, the TC is still required to work, such as monitoring signaling in the TFO message, and transparently transmitting speech stream. Therefore, the TFO function does not save the TC resources. On each call channel, there is only one encoding and decoding operation, as shown in Figure 5-7: Figure 5-7 Encoding and decoding speech operation after activating TFO
Transcoding Functions
PLMN A
PLMN B
MS/UE
MS/UE
ENCODING
Compressed Speech
Transparent transmission
Compressed Speech
Transparent transmission
Compressed Speech
DECODING
The TFO function is applicable to the GSM and the UMTS networks. Because the TFO adopts the inband signaling TC control function, the TFO is suitable for the speech call between two mobile subscribers only.
TrFO Function
The transcoder free operation (TrFO) is an operation without any encoding and decoding operation. During the speech transmission, TC is not required for speech processing. For calls between two mobile subscribers, the end to end speech transmission function of high fidelity and low delay can be provided. Compared with the TFO function, TrFO does not need TC for speech transmission. No related conversion or encoding and decoding operation is needed and thus the speech quality is promoted. On each call channel, there is only one encoding and decoding operation, as shown in Figure 5-8:
Issue 03 (2006-09-30)
5-37
Figure 5-8 Encoding and decoding speech operation after activating TrFO
Transcoding Functions Bypassed
PLMN A
PLMN B
MS/UE
MS/UE
ENCODING
Compressed Speech
DECODING
The TrFO function is applicable to the UMTS network only. Because the TrFO function adopts the outband signaling TC control function, the TrFO function is suitable for the speech call between mobile subscribers and between the mobile subscriber and the subscriber of external networks.
eMLPP Function
The enhanced multi level precedence and preemption service (eMLPP) is used to configure calls with multiple priorities. Calls of a higher priority have more advantages, such as channel preemption and fast setup. For the operation strategy, the eMLPP enables the carriers to fractionize subscriber groups, and provide subscribers of different priorities with services of different levels. With the eMLPP function, each subscriber is configured with a given priority authority. A subscriber can only make calls of a given priority within the authority. Calls with different priorities have different priorities of preempting network resources. In addition, calls with different priorities can be connected in different call establishment modes.
IN Announcement Charging
During the IN announcement process, carriers can determine whether to generate the call detail record (CDR) in the end office based on announcement devices (end office or independent IP) and announcement flows. The following are announcement flows:
! ! ! ! !
Play announcement. Receive number and play announcement. Play announcement and receive number. Play announcement and connect call. Play announcement, receive number and connect call.
After determining the charging rule of IN resources, carriers can use the IN announcement charging function to make the MSOFTX3000 perform the following:
! !
Provide the charging service of IN resources usage for subscribers Flexibly specify the IN resources service to be charged.
IN DCH Setting
The subscription information of IN subscriber in the HLR contains Default Call Handling (DCH) that indicates which handling mode is adopted by the MSC when abnormal IN call occurs. The MSOFTX3000 support the DCH setting function to define different handling
5-38
Issue 03 (2006-09-30)
modes at the MSC side for different service keys and abnormal situations. The handling modes include:
! ! !
Release the call by force. Continue the call by force. Use the default call handling method subscribed by the IN subscriber.
The IN DCH setting function has the following functions:

! !
Carriers can set the data so as to continue the call by force for high-end IN subscribers or to release the call by force for low-end IN subscribers. When the traffic is in the peak hours and the SCP response speed is reduced, such setting can realize differential service, increase the call completion rate of high-end subscribers, and improve the service quality.
2G/3G Network Access Control Based on Different Subscribers

For GSM/UMTS dual-mode subscribers, this function allows the MSOFTX3000 to control the access of subscriber to the BSS or UTRAN network. Provision of this function requires the collaboration of the MSOFTX3000 and HLR and the HLR must support the Access Restriction Data (ARD) subscription function. The MSOFTX3000 controls the authority needed by subscribers for accessing the GERAN or UTRAN network. For example, the GERAN Allowed/UTRAN NOTAllowed service is configured upon the subscription of ARD in the HLR, if the local MSOFTX3000 supports the ARD 3G function:
!
If a subscriber originates location update to the local MSOFTX3000 from the 2G BSS, and the local office does not restrict ARD 2G roaming, the MSOFTX3000 allows the subscriber to access the 2G network. If a subscriber originates location update to the local MSOFTX3000 from the 3G UTRAN, and the local office restricts ARD 2G roaming, the MSOFTX3000 rejects the subscriber to access the 2G network.
Half-Rate-Based Subscriber Access Classification

The half-rate-based subscriber access classification service ensures the QoS of high-priority GSM subscribers in heavy-traffic hours. Leveled subscriber indicates the MSOFTX3000 grants different priorities for each type of subscriber of the HLR. Half rate indicates the MSOFTX3000 controls the BSC to distribute speech channels for mobile subscribers according to the following policies in the condition that the service is available when the reported handset capability is either full rate or half rate.
! !
The MSOFTX3000 sets the channel type to full rate channel for the high-priority subscribers. The BSC will always assign full-rate channels for these subscribers. The MSOFTX3000 sets the channel type to both (full rate and half rate) for low-priority subscribers. The BSC will assign full-rate channels to these subscribers when there are sufficient resources, and will assign half-rate channels when otherwise.
Specified Circuit Dialing Test

This function allows maintenance staff to test the availability of the circuits through the A interface. The maintenance staff can find such problems as self-loop and one-way audio by unblocking trunk circuits. In this way, the means to locate faults is improved.
Issue 03 (2006-09-30)
5-39
The MSOFTX3000 supports the dialing test on circuits both on the caller side and the callee side.
!
Dialing test on circuits on the caller side: The caller who initiates the test call must be a mobile subscriber. The callee can be a mobile subscriber, PSTN subscriber or virtual subscriber. If the callee is a virtual subscriber, the MSC can play announcements to continue the test. Dialing test on circuits on the callee side: The callee who receives the test call must be a mobile subscriber. The caller can be a mobile subscriber or a PSTN subscriber.
In practice, in the dialing test on circuits on the caller side, the callee can be a virtual subscriber. This makes the means flexible, the location process simple, and the maintenance convenient.
Continuity Check
The continuity check is a feature in the circuit management of TUP/ISUP. You can use a message in the TUP/ISUP to check the continuity of the voice channel in the trunk circuit. This will detect false seizures of trunk circuits. Classified by start party, there are two types of continuity checks:
!
Maintenance continuity check You can type command on the maintenance console to instruct the system to start continuity check or end continuity check to trunk circuits. At present, the MSOFTX3000 realizes two modes of continuity check, that is, continuity checks based on specified trunk and office direction. Call continuity check It is realized through data configuration. During call setup, the system auto originates continuity check through the continuity check indication in IAM message. Based on different originating parties of the continuity check function during a call, the MSOFTX3000 supports both active continuity check and passive continuity check functions.
Active continuity check: The local office generates the continuity check request and plays continuity check tone. Then the peer office is required to respond by looping. Thus, you can perform voice judgment on connectivity of corresponding trunk circuits at the peer office. Passive continuity check: It is opposite to the active continuity check. The peer office generates the continuity check request and plays continuity check tone. Then the local office is required to respond by looping. Thus, you can perform voice judgment on connectivity of corresponding trunk circuits at the peer office.
5-40
Issue 03 (2006-09-30)
6 Networking and Application
6
About This Chapter
Title
Networking and Application
The following table lists the contents of this chapter. Description This section describes the typical networking solutions of the MSOFTX3000. This section describes the typical network application cases of the MSOFTX3000.
6.1 Typical Networking 6.2 Network Application Cases
Issue 03 (2006-09-30)
6-1
6.1 Typical Networking

6.1.1 MSC Networking
The MSOFTX3000 supports various protocols, such as the H.248, BSSAP, RANAP, MAP, CAP, ISUP, TUP, and BSSAP+. It can work as the mobile switching center (MSC) server and the VLR in the network. When deployed with Huawei UMG8900 and the Shared InterWorking Function (SIWF), the MSOFTX3000 supports the BSS/UTRAN accessing mode and can function as the 2G VMSC, 3G VMSC, or 2G/3G integrated VMSC in the network. The typical networking is as shown in Figure 6-1: Figure 6-1 MSC networking
UMG8900 UMG8900
H.248 BSSAP BSS ISUP/BICC MSOFTX3000 (MSC)
H.248 PSTN/ PLMN TUP/ISUP GMSC FTP/ FTAM
RANAP
IP backbone network/ No.7 signaling network
BC MML
UTRAN
BSSAP+
M2000 CAP MAP MAP MAP
SGSN
SCP
GMLC
SMC
HLR
Bearer channel Signaling channel
Access network
Core network
BSS: GSM Base station subsystem BC: Billing center GMLC: Gateway mobile location center PSTN: Public switched telephone network
UTRAN: UMTS terrestrial radio access network HLR: Home location register SCP: Service control point PLMN: Public land mobile network
GMSC: Gateway mobile switching center SMC: Short message center SGSN: Serving GPRS support node
In the networking as shown in Figure 6-1, the MSOFTX3000 terminates the mobile subscriber/network signaling defined by the R99 24.008 and R98 04.08 specifications, and converts the signaling to the inter-office signaling transferred on the Nc interface. In addition, the MSOFTX3000 has an embedded VLR to store the subscription data of mobile subscribers and the related CAMEL data. The interworking between the MSOFTX3000 and the
6-2
Issue 03 (2006-09-30)
PSTN/PLMN is realized by the GMSC. Through the Mc interface, the MSOFTX3000 controls the bearer terminal and media stream at the access network and backbone network side in the UMG8900.
!
MSOFTX3000 <-> UMG8900: Mc interface. It is the standard interface of the control layer and bearer layer in the core network. It adopts the extended H.248 protocol defined by the ITU-T. Through the Mc interface, the MSOFTX3000 controls the bearer resources at the radio access side and trunk side. The interface is an IP-based interface added in the R4 stage. MSOFTX3000 <-> BSC: A interface. It is the standard interface in the control layer between the core network and the BSS radio access network based on the GSM. It adopts the BSSAP protocol and realizes the termination of the controlling signaling messages for the service access in the circuit switched (CS) domain for the 2G mobile subscribers. The A interface provides the following functions:

Mobility management Call control Circuit allocation Circuit reset Handover Short message processing
It is a TDM-based interface adopting the BSSAP protocol for the GSM MSC. It can also be connected through the UMG8900 with the SIGTRAN function. In this case, it adopts the M2UA protocol.
!
MSOFTX3000 <-> RNC: Iu interface. It is the standard interface in the control layer between the core network and the UTRAN based on the WCDMA. It adopts the RANAP protocol and realizes termination of the controlling signaling messages for the service access in the CS domain for the 3G mobile subscribers. The Iu interface provides the following functions:

Mobility management Call control RAB allocation Reset and overload control RNC re-allocation Short message processing
This interface inherits the functions in the R99 stage. It can be an IP-based (M3UA) interface. When there is no direct interface between the MSOFTX3000 and the RNC, the Iu interface can be connected through the UMG8900.
!
MSOFTX3000 <-> GMSC/GMSC Server: The MSOFTX3000 adopts the ISUP/TUP protocol for interworking with the GMSC. When the MSOFTX3000 interworks with the GMSC Server, the interface is called the Nc interface. The Nc interface is the inter-office signaling interface in the control layer of the CS domain. It is an IP-based or TDM-based interface adopting the ISUP/TUP or BICC protocol. It is added in the R4 stage. MSOFTX3000 <-> MSC: E/G interface. It is only adopted between the neighboring MSCs (not shown in the figure). It is a TDM-based or IP-based interface adopting the MAP protocol, used for inter-office handover and location update. MSOFTX3000 <-> HLR: C/D interface. Adopting the MAP protocol, it is used for the location update of network level in the CS domain, and the management of routing data and subscription data. It is a TDM-based or IP-based interface directly inherited from the R99 stage. It adopts the SIGTRAN protocols.
Issue 03 (2006-09-30)
6-3

!
MSOFTX3000 <-> SCP: The interface adopts the CAP protocol. It provides the following functions:

Realizing the standard connection between the SSP and SCP in the CS domain integrated in the MSOFTX3000 Reporting the O/T-BCSM call state event and executing the commands from the SCP
Therefore, in the R4 stage, the intelligent services in the R99 and GSM stage can be realized in the transparent subscriber mode. The interface is a TDM-based or IP-based interface directly inherited from the R99 stage.
!
MSOFTX3000<->SMC: E interface. Adopting the MAP protocol, it transfers the mobile originated and mobile terminated short messages between the SMC and the MSOFTX3000. MSOFTX3000<->GMLC: Lg interface. Adopting the MAP protocol, the Lg interface between the MSOFTX3000 and the GMLC supports the location application out of the PLMN to exchange the subscriber authentication data required by the location service and the data (such as the IMSI) required by the network resource allocation with the MSC through the GMLC and locate the QoS. MSOFTX3000<->SGSN: Gs interface. Adopting the BSSAP+ protocol, the Gs interface between the MSOFTX3000 and the SGSN integrates some functions of the packet switched (PS) domain and the CS domain (such as the united location update) to effectively save the wireless resources. MSOFTX3000<->BC: The interface adopts the FTP/FTAM protocol and enables the BC to auto fetch CDRs from the iGWB of the MSOFTX3000. MSOFTX3000<->M2000: The interface adopts the MML protocol and supports the MSOFTX3000 to access Huawei iManager M2000 network management system.
! !
6.1.2 GMSC Networking

The MSOFTX3000 supports various protocols, such as the H.248, MAP, CAP, ISUP, and TUP. It provides abundant functions, such as:
! ! ! !
Black and white list Call authentication Call intercept Mass storage of CDRs
When deployed with Huawei UMG8900, the MSOFTX3000 can function as the GMSC in the network. The typical networking is as shown in Figure 6-2:
6-4
Issue 03 (2006-09-30)
Figure 6-2 GMSC networking

UMG8900 UMG8900
H.248 ISUP/BICC MSC/VLR
H.248 TUP/ISUP MSOFTX3000 (GMSC) FTP/ FTAM PSTN/ PLMN
IP backbone network/ No.7 signaling network
BC MML M2000
CAP
MAP Bearer channel
SCP
HLR
Signaling channel
MSC: Mobile switching center HLR: Home location register PLMN: Public land mobile network
VLR: Visitor location register SCP: Service control point
BC: Billing center PSTN: Public switched telephone network
In the networking as shown in Figure 6-2, the MSOFTX3000 terminates the signaling (such as the BICC) on the Nc interface with other MSCs and the call control ISUP/TUP signaling with the traditional external network (PSTN/PLMN). It realizes the route search for the called mobile subscriber and the number change between the mobile network and fixed network. Through the Mc interface, the MSOFTX3000 controls the bearer terminal (IP) at the core network side in the UMG8900 and the bearer terminal (TDM trunk) at the traditional fixed network side. In the GMSC networking, the MSOFTX3000 provides various interfaces as follows:
!
MSOFTX3000 <-> UMG8900: Mc interface. It is the standard interface of the control layer and bearer layer in the core network. It adopts the extended H.248 protocol defined by the ITU-T. Through the Mc interface, the MSOFTX3000 controls the bearer resources at the radio access side and trunk side. The interface is an IP-based interface added in the R4 stage. MSOFTX3000 <-> MSC/MSC Server: The MSOFTX3000 adopts the ISUP/TUP protocol for interworking with the MSC. When the MSOFTX3000 interworks with the MSC Server, the interface is called the Nc interface. The Nc interface is the inter-office signaling interface in the control layer of the CS domain. It is an IP-based or TDM-based interface adopting the ISUP/TUP or BICC protocol. It is added in the R4 stage.
Issue 03 (2006-09-30)
6-5

!
MSOFTX3000 <-> PSTN/PLMN: Adopting the TUP or ISUP protocol, the interface sends and receives the call control messages between the mobile network of the local CS domain and the PSTN/PLMN. It is a TDM-based (MTP3) interface directly inherited from the R99 stage. MSOFTX3000 <-> HLR: C/D interface. Adopting the MAP protocol, the interface is used to obtain the routing information for the called mobile subscriber from the PSTN/PLMN. It is a TDM-based or IP-based interface directly inherited from the R99 stage. It adopts the SIGTRAN protocols. MSOFTX3000 <-> SCP: The interface adopts the CAP protocol. It provides the following functions:

Realizing the standard connection between the SSP and SCP in the CS domain integrated in the MSOFTX3000 Reporting the O/T-BCSM call state event and executing the commands of the SCP
Therefore, in the R4 stage, the intelligent services in the R99 and GSM stage can be realized in the transparent subscriber mode. The interface is a TDM-based or IP-based interface directly inherited from the R99 stage.
! !
MSOFTX3000<->BC: The interface adopts the FTP/FTAM protocol and enables the BC to auto fetch CDRs from the iGWB of the MSOFTX3000. MSOFTX3000<->M2000: The interface adopts the MML protocol and supports the MSOFTX3000 to access Huawei iManager M2000 network management system.
6.1.3 TMSC Networking

The MSOFTX3000 supports various protocols, such as the H.248, ISUP, and BICC. When deployed with Huawei UMG8900, it provides TDM trunks or IP bearer channels of large capacity. It can function as the tandem mobile switching center (TMSC) in the hierarchical network. The typical networking is as shown in Figure 6-3: Figure 6-3 TMSC networking
BC M2000 Bearer channel FTP/ FTAM MSOFTX3000 (TMSC) ISUP/BICC TUP/ISUP H.248 H.248 TUP/ISUP MML Signaling channel
MSOFTX3000 (TMSC)
Other MSC
UMG8900
UMG8900
Other MSC
6-6
Issue 03 (2006-09-30)
The networking as shown in Figure 6-3 is suitable for the GSM and 3GPP R99 hierarchical network structures, in which, the call signaling and bearer connection are connected through the TMSC hierarchically. The MSOFTX3000 realizes the call connection and route selection functions in the PLMN and controls the bearer terminal (IP) at the core network side in the UMG8900 and the bearer terminal (TDM trunk) at the traditional fixed network side. In the 3GPP R4 all-IP network, the MSOFTX3000 realized the end-to-end bearer connection between the originating end and the terminating end through the BICC signaling, that is, the call signaling messages are transferred hierarchically through the TMSC, but the bearer do not need hierarchical processing. In this case, the media gateway (MGW, such as UMG8900) is not needed in the networking as shown in Figure 6-3.
6.1.4 Dual-Homing Networking

Overview
Dual-homing is a mechanism that in the networking of 3GPP R4 or later, one MGW belongs to two MSC Servers. Normally, each MGW only registers with the active MSC Server. When the active MSC Server breaks down or an emergent disaster of the system occurs, this MGW can register with the standby MSC Server so that the network can continue providing services. In the networking structure of 3GPP R4 or later, the MSC Server:
! ! !
Plays an important role. Controls multiple MGWs. Covers a large area.
If the MSC Server breaks down or an emergent disaster of the system occurs, the following cases take place:
! ! !
All MGWs are out of control. Services are interrupted widely. Huge Loss of data occurs.
To ensure secure and reliable operation of the mobile network, the MSOFTX3000 provides the dual-homing mechanism to support the remote disaster tolerance feature of the MSC Server. The MSOFTX3000 supports the following four kinds of dual-homing networking solutions:
! ! ! !
1+1 backup networking 1+1 mutual assistance networking N+1 backup networking N+1 mutual assistance networking
1+1 Backup Networking

In 1+1 backup networking, two MSOFTX3000s work in active/standby mode as MSC Servers. That is, one MSOFTX3000 works as the active MSC Server, the other as the standby MSC Server. Figure 6-4 shows the networking:
Issue 03 (2006-09-30)
6-7
Figure 6-4 1+1 backup networking

Heartbeat link MSOFTX3000 A MSOFTX3000 B Active control channel Standby control channel
MGW1
MGW2
MGW3
MGW4
MSC area A
MSC area B
In Figure 6-4, MSOFTX3000 A works as the active MSC Server. Normally, it controls the services in MSC areas A and B. MGWs 1 to 4 register only with MSOFTX3000 A while MSOFTX3000 B does not process any service. When the MSOFTX3000 A breaks down or any emergency occurs, the MSOFTX3000 B takes over the service control of MSC areas A and B. Then MGWs 1 to 4 register with MSOFTX3000 B.
1+1 Mutual Assistance Networking

In 1+1 mutual assistance networking, two MSOFTX3000s work as MSC Servers in mutual assistance mode. Each MSOFTX3000 works as the active MSC Server and as the standby MSC Server for the other at the same time. Figure 6-5 shows the networking: Figure 6-5 1+1 mutual assistance networking
Heartbeat link MSOFTX3000 A MSOFTX3000 B Active control channel Standby control channel
MGW1
MGW2
MGW3
MGW4
MSC area A
MSC area B
6-8
Issue 03 (2006-09-30)
In Figure 6-5, MSOFTX3000 A controls the services in MSC area A. That is, MGWs 1 and 2 only register with MSOFTX3000 A. MSOFTX3000 B controls the services in MSC area B. MGW 3 and 4 register with MSOFTX3000 B. When MSOFTX3000 A breaks down or any emergency occurs, MSOFTX3000 B takes over the service control of MSC area A. MGW 1 and 2 turn to register with MSOFTX3000 B. Conversely, when MSOFTX3000 B breaks down or any emergency occurs, MSOFTX3000 A takes over the service control of MSC area B. MGWs 3 and 4 turn to register with MSOFTX3000 A.
N+1 Backup Networking

In N+1 backup networking, N + 1 MSOFTX3000s work in "N active, one standby" mode. That is, N MSOFTX3000s work as active MSC Servers, one as the standby MSC Server. Figure 6-6 shows the networking: Figure 6-6 N+1 backup networking (N = 2)
MSOFTX3000 A Heartbeat link MSOFTX3000 B Heartbeat link Active control channel Standby control channel MSOFTX3000 C
MGW1
MGW2
MGW3
MGW4 MSC area B
MGW5
MGW6 MSC area C
MSC area A
In Figure 6-6, MSOFTX3000 A and MSOFTX3000 C work as active MSC Servers while MSOFTX3000 B works as the standby MSC Server. Normally, MSOFTX3000 A controls the services in MSC areas A and B. MGW 1 to MGW 4 register with MSOFTX3000 A. MSOFTX3000 C controls the services in MSC area C. MGWs 5 and 6 register with MSOFTX3000 C. When MSOFTX3000 A breaks down or any emergency occurs, MSOFTX3000 B takes over the service control of MSC area A and B. MGW 1 to MGW 4 register with MSOFTX3000 B. When MSOFTX3000 C breaks down or any emergency occurs, MSOFTX3000 B takes over the service control of MSC area C. MGWs 5 and 6 register with MSOFTX3000 B.
N+1 Mutual Assistance Networking

In N+1 mutual assistance networking, N + 1 MSOFTX3000s work in "all active, one standby" mode. That is, all the MSOFTX3000 work as active MSC Servers, one of them as the standby MSC Server for the others. Figure 6-7 shows the networking:
Issue 03 (2006-09-30)
6-9
Figure 6-7 N+1 mutual assistance networking (N = 2)

MSOFTX3000 A MSOFTX3000 B Heartbeat link MSOFTX3000 C Heartbeat link Active control channel Standby control channel
MGW1
MGW2
MGW3
MGW4 MSC area B
MGW5
MGW6 MSC area C
MSC area A
In Figure 6-7, MSOFTX3000 A controls the services in MSC area A. That is, MGWs 1 and 2 register only with MSOFTX3000 A. MSOFTX3000 B controls the services in MSC area B. MGWs 3 and 4 register only with MSOFTX3000 B. MSOFTX3000 C controls the services in MSC area C. MGWs 5 and 6 register only with MSOFTX3000 C. In networking, MSOFTX3000 B works as the assistant server for MSOFTX3000s A and C. When MSOFTX3000 A breaks down or any emergency occurs, MSOFTX3000 B takes over the service control of MSC area A. That is, MGWs 1 and 2 register with MSOFTX3000 B. When MSOFTX3000 C breaks down or any emergency occurs, MSOFTX3000 B takes over the service control of MSC area C. MGWs 5 and 6 register with MSOFTX3000 B. Note that in N+1 backup and mutual assistance networking, the assistant MSOFTX3000 can help control the services of one MSOFTX3000 at a time. It cannot take the service control of two or more MSOFTX3000s at the same time. Besides, the assistant MSOFTX3000, with any other MSOFTX3000 in the network, can work in 1+1 mutual assistance mode.
6.1.5 Multi-Area Networking

In the networking of 3GPP R4 or later, the multi-area (MA) networking means that an MSC Server controls multiple local networks. The MSC Server controls all services in the MA network. Wireless network equipment of each local network is connected with an MGW dedicated to the area. Each local network interworks with entities of other local networks through an MGW. The MSOFTX3000 supports the MA networking solution, as shown in Figure 6-8:
6-10
Issue 03 (2006-09-30)
Figure 6-8 MA networking

TMSC1 TMSC2 MSOFTX3000 Voice channel Signaling channel
BSC MGW1 RNC MGW2
BSC
RNC PSTN PSTN Virtual MSC2/VLR2 DPC2
Virtual MSC1/VLR1 DPC1
RNC: Radio network controller BSC: Base station controller PSTN: Public switched telephone network
TMSC: Tandem mobile switching center MGW: Media gateway
As shown in Figure 6-8, the MSOFTX3000 is placed in one area, and the MGWs are in different areas in an MA network. The PSTN of each area connects to the MA network through a local MGW. It does not matter if the MGWs of two local networks are directly connected. A call between two mobile subscribers of two local networks or a handover between the two local networks is regarded as intra-office or inter-office. The MA network structure is applied to the following two kinds of networking solutions:
!
High density and large capacity local network: For the densely populated areas that take about 10% of the total area, use a strategy of "fewer MSCs, but of large capacity" to build a network. Wide coverage local network: For the less populated areas that take about 90% of the total area, use a strategy of "central control and near access" to build a network.
6.1.6 Solution for Huawei IMS Interworking with CS Domain

Huawei MSOFTX3000 can function as the MGCF. It is responsible for communicating with the CSCF in the IMS domain and controls the connection of media channel in the IM-MGW. In the networking of 3GPP R5, the MSOFTX3000 can also function as the STP to realize the interworking between the SIP signaling in the IMS domain and the BICC/ISUP signaling in the CS domain. Figure 6-9 shows the typical networking structure for Huawei IMS interworking with the CS domain:
Issue 03 (2006-09-30)
6-11
Figure 6-9 Networking structure for Huawei IMS interworking with the CS domain
Mj MSC Server A BSS Mc Iu Nb Mb GGSN UTRAN MGW CS domain Bearer channel Signaling channel
GGSN: Gateway GPRS support node CSCF: Call session control function BGCF: Breakout gateway control function MGCF: Media gateway control function SGW: Signaling gateway MRFP: Multimedia resource function processor
MSC Server / MGCF (MSOFTX3000) Nc Mg
BGCF
I-CSCF Mn
MGW / IM-MGW
Mb
MRFP
IMS domain
IM-MGW: IMS-Media gateway function CS: Circuit switched domain CCF: Offline charging gateway in IMS domain
The MSOFTX3000 realizes the interworking between the IMS domain and the CS domain. It provides the maintainable, exercisable, and manageable network solution for interworking between the IMS domain and the CS domain to meet network carriers' requirements based on their network features. In this way, the MSOFTX3000 helps the carriers make more profits.
6.1.7 Solution for Huawei NGN Interworking with CS Domain

Huawei MSOFTX3000 can realize the interworking of audio and video services between the CSCF in the IMS domain and the next generation network (NGN). Figure 6-10 shows the typical networking structure for Huawei NGN interworking with the CS domain:
6-12
Issue 03 (2006-09-30)
Figure 6-10 Networking structure for Huawei NGN interworking with the CS domain
IMS Core I-CSCF P-CSCF S-CSCF MSOFTX3000 Fixed SS
Audio IMS-UE Video
BGCF
IM-MGW
MGW Audio Video
Signaling channel Bearer channel Terminal
P-CSCF: Proxy-CSCF BGCF: Breakout gateway control function MGW: Media gateway
S-CSCF: Serving-CSCF Fixed SS: NGN network element IMS-UE: Multimedia terminal
I-CSCF: Interrogating-CSCF IM-MGW: IMS-Media gateway function
6.1.8 Evolution Strategy of Huawei Mobile Core Network

The MSOFTX3000 supports the application of the 3GPP R4 CS CN and is compatible with the GSM and 3GPP R99 networking. It enables the R4 networking to evolve smoothly to the 3GPP R5/R6. The network evolution strategy is as shown in Figure 6-11:
Issue 03 (2006-09-30)
6-13
Figure 6-11 Evolution strategy of Huawei mobile core network

GSM 3GPP R99 3GPP R4 3GPP R5/R6
MSC Server MSOFTX 3000
MSC Server/MGCF MSOFTX 3000
MSC MSOFTX 3000/ UMG 8900
MSC
MSOFTX 3000/ UMG 8900
MGW UMG 8900
MGW/IM MGW UMG 8900
The previous paragraphs detail the applications of the MSOFTX3000 in the GSM, 3GPP R99, and 3GPP R4. In the following paragraphs, the evolution solution of the MSOFTX3000 towards the IMS of 3GPP R5/R6 will be elaborated. The solution of Huawei R5 is as shown in Figure 6-12. Figure 6-12 Solution of Huawei R5
APP Server HLR/HSS SMC SCP
CS
MSS/MGCF
IMS CSCF
T-MSS MSS
SG IP / ATM / TDM
PS GGSN
G-MSS
MGW
MGW SGSN
PSTN
BSS NGN PLMN
RAN
6-14
Issue 03 (2006-09-30)
In the Huawei 3GPP R5 solution, as a service control network over the PS, the IMS is always networked with the CS CN of 3GPP R4 and the two networks can supplement each other. It also integrates mobile networks and fixed networks. For the PS air interface, the IP-based real time service QoS is improving and the IP at the wireless terminal is developing increasingly in its processing capability. After the end-to-end QoS of the IMS bearer network used for session becomes mature, the IMS will gradually replace the CS R4 in the 3G access domain. The MSOFTX3000 can be expanded smoothly into the equipment with the MGCF, and the UMG8900 can be upgraded to the IM MGW. These ensure the investments protected efficiently.
6.2 Network Application Cases

6.2.1 Multi-area Commercial Network of Company A
Company A adopts Huawei MSOFTX3000 and UMG8900s to build an MA commercial network. In the first stage of the project, three local networks are built. In the networking structure as shown in Figure 6-13, the MSOFTX3000 is deployed in the central office of the provincial capital as the MSC Server; three UMG8900s are deployed in city C, city J, and city F respectively as the remote access gateways in each local network.
Issue 03 (2006-09-30)
6-15
Figure 6-13 Multi-area commercial network of company A

Bearer channel Signaling channel MSOFTX3000 Central office of the provincial capital TMSC2
TMSC1
GMSC1
GMSC2
MGW1
MGW3
BSS11
MGW2
BSS3 BSS12 Local network in city C BSS2 Local network in city J Local network in city F
The MA commercial network of company A has the following features:

! !
The MGWs in the three local networks share one MSOFTX3000. Therefore, the cost of network construction is low. The MSC function of the three local networks is provided by the MSOFTX3000 in the central office of the provincial capital. In this way, the network is controlled and managed in a centralized way, and the maintenance cost is reduced. The MSOFTX3000 allocates an independent signaling point code (SPC) and MSC number to each local network. Therefore, the logical MSC in each local network works independently and does not influence other logical MSCs. Each MGW is connected to the TMSC and GMSC in each local network. The routing scheme and numbering scheme are unchanged. Therefore, the equipment utilization of the current network is improved, and the smooth evolution of the network is ensured. The system determines the destination of the CDRs of the subscribers in each local network based on the MSC number. The system measures the traffic of each local network based on the traffic statistics index corresponding to the MSC number in the MA network.
! !
6-16
Issue 03 (2006-09-30)
6.2.2 Dual-Homing Commercial Network of Company B

Company B adopts Huawei MSOFTX3000s and UMG8900s to build a dual-homing commercial network. In the first stage of the project, 4 MSOFTX3000s (in dual-homing mode) and 10 UMG8900s are deployed as the T/G integrated office to interwork with the PSTN, MSCs in the local network, and MSCs in other network. Figure 6-14 shows the networking: Figure 6-14 Dual-homing commercial network of company B
The dual-homing commercial network of company B has the following features:

!
The MSOFTX3000s with mutual assistant function are deployed in different places. As shown in Figure 6-14, SX1 and SX4, and SX2 and SX3 work in 1+1 mutual assistance dual-homing mode. In this way, the network reliability is greatly improved. The UMG8900s are deployed in different cities. The IP backbone network is adopted as the bearer network among the UMG8900s. Therefore, the network topology is simplified, the local alternative routes are decreased, and the transmission cost of the whole network is reduced. In actual networking, the heartbeat link is configured between two MSOFTX3000 in mutual assistance mode, detecting whether the peer MSOFTX3000 is working normally. In normal cases, each MGW only sends registration request to the active homing MSOFTX3000 based on the MGC data configured on the MGW. When an MSOFTX3000 is faulty, the standby MSOFTX3000 cannot detect the heartbeat signal from the faulty MSOFTX3000. The MGWs controlled and managed by the faulty MSOFTX3000 generates alarms indicating registration failure. If the system adopts the automatic switchover mode, the standby MSOFTX3000 is auto activated immediately
Issue 03 (2006-09-30)
6-17
and takes over the MGWs and services controlled by the faulty MSOFTX3000. Then, the MGWs send registration requests to the activated MSOFTX3000.
6-18
Issue 03 (2006-09-30)
7 Reliability and Security Design
7
About This Chapter
Title
Reliability and Security Design
The following table lists the contents of this chapter. Description This section describes the reliability design of the MSOFTX3000 system. This section describes the security design of the MSOFTX3000 product.
7.1 Reliability Design 7.2 Security Design
Issue 03 (2006-09-30)
7-1
7.1 Reliability Design

7.1.1 Hardware Reliability
Distributed Hardware Structure
The MSOFTX3000 adopts a distributed hardware structure. The modular design of the functions realizes the distributed processing. The functions of the modules are independent from one another, and are controlled by different processors. The fault of one processor does not affect the operation of the whole system.
Redundancy Design
The hardware of the MSOFTX3000 adopts various designs, such as active/standby mode, load sharing mode, and redundancy configuration, to ensure the reliability of the hardware system.
!
The key parts in the MSOFTX3000 adopt the multi-processor backup design. For example, the WSMU, WCCU, WCDB, WCKI, WMGC, and iGWB have two processors working in active/standby mode. In normal conditions, the active processor controls the running of the module, and the standby processor synchronizes with the active one in real time. When the active processor is faulty, the standby one is brought into service at once. The standby processor takes the place of the faulty active one to control the operation of the system without interrupting the service. The service boards and interface boards of the MSOFTX3000 adopt the load sharing mode. That is, two or more boards share the related functions during normal working. Once a board becomes faulty, the other boards take over the tasks of the faulty board on the premise that certain performance indexes, such as call loss, must be ensured. The IP interface of the MSOFTX3000 supports physical backup, ensuring the reliability of the IP routes between the MSOFTX3000 and the IP bearer network.
Derating Design
It is to derate the electric stress and heat stress to the values under the rated values when the electronic components run. As a result, the following purposes can be achieved:
! ! !
Postponing the degeneration of the parameters Prolonging their service lives Enhancing their reliability
Maintainability Design
The maintainability design aims to meet the specified quantity and quality demands on maintainability, especially the demand on reducing the maintenance time. The maintenance design covers the following:
! ! ! !
Product design and maintenance simplification Reachability Standardization and exchangeability Modularization
7-2
Issue 03 (2006-09-30)

! ! !
Error prevention design and identifier Testing and diagnosis technology Human and environment factors
The detailed are described as follows:

! ! ! !
The boards are designed to be hot-pluggable to reduce the time for board replacement. No cable is outlet from the front panel, thus facilitating board removal and assembly and decreasing the maintenance time. When a module in the system is faulty, the maintenance terminal can detect the fault and report it. There is a local maintenance MML operation terminal, which is convenient and practical for maintenance staff to locate and remove faults fast.
Selection and Usage of Components

Selection and usage of components are the keys to ensure the component reliability.
!
For the MSOFTX3000, component types, specifications, and suppliers are selected according to the demands on the product reliability, with the component replacing and unification focused. The component unification and reliability model analysis is used to reduce the number of components used and improve the system usability. The components of the MSOFTX3000 are strictly selected and pass the aging test. Thus, the components are of high quality, which ensures the reliability of the hardware system.
Power Reliability
The following plans are employed in the MSOFTX3000 to improve the reliability of the power supply system:
!
Distributed power supply: Distributes power separately to each subrack or functional module through high-frequency DC/DC secondary power modules, ensuring efficiency and stability. The power module of the subrack adopts 2+2 backup design. The power module of the BAM and the iGWB adopts 1+1 redundancy design. Therefore, when one power module is faulty, the operation of the system is not influenced. Overvoltage and overcurrent protection measures are applied to +5 V / 48 V power input and external interfaces (such as E1 interfaces). These measures comply with Appendix B of ITU-T Recommendation G.703 and relative specifications.
7.1.2 Software Reliability

Complying with the CMM Flow
The MSOFTX3000 software development process consists of several stages,
! ! !
which include:
Requirement analysis System design Software test
All stages comply with the Capability Maturity Model (CMM) flow.
Issue 03 (2006-09-30)
7-3
Quality assurance measures improve the reliability of the software, to a great extent, in the development of the MSOFTX3000, which include:
! ! ! ! !
Code walk-through Inspection Review Unit test System test
Protection Measures
The modular design is used for the software. The software modules are based on the loose coupling mechanism, for which other modules will not be affected in case that one module fails. In addition, error detection, error isolation and error recovery are added to avoid potential problems.
Error Tolerance Ability

The error tolerance of the software system can avoid the breakdown of the entire system in case of the failure occurring to a software portion. That is, the system has the self-healing ability when errors occur. The software error tolerance capabilities include the following aspects:
! ! ! ! !
Periodical check of key resources Task monitoring Storage protection Data check Operation log storage
Fault Monitoring and Processing

The MSOFTX3000 can auto detect and process the faults occurring in the software and hardware system by performing the following measures:
! ! ! !
Auto isolation Switchover Restart Reload
Hot Patch
Sometimes adaptive and corrective modifications to the host software are required during the running of the MSOFTX3000. For example, you need to eliminate some found defects from the system, and add some new features. Traditionally, you halt the running of the host software to upgrade. However, it affects services provisioning. The MSOFTX3000 supports the hot patch function. By patching the host software, the software can be upgraded in the in-service state, which does not affect the quality of the provided communication services.
7-4
Issue 03 (2006-09-30)
7.1.3 Reliability of Charging System

Hardware Reliability
The iGWB Server developed by Huawei functions as the charging gateway of the MSOFTX3000. It adopts the dual-system and achieves the dual backup and mass storage of the CDR data. The network cards of the iGWB Server are in different network segments, and there is no message transfer among them. In this way, external subscribers are separated from internal private networks. This ensures the security of operations on the CDR data.
Software Reliability
!
Program reliability The iGWB Server can transfer detailed alarm information to the alarm box through the BAM in real time for centralized alarming. This helps to remove faults of the iGWB Server in time.
Reliability of CDR data
Against CDR loss or CDR repetition: After saving the original CDR data, the iGWB Server sends a confirmation message to the host. At the same time, the current CDR confirmation state is recorded in detail against CDR loss or CDR repetition. The iGWB Server is restored after each start to ensure the consistency between the original CDR data and the final CDR data. Data backup: The iGWB Server regularly backs up CDR files and other important data in it. A protective mechanism of the CDR pool is provided. The system can auto create the CDR directory for recovery when it is intentionally deleted. Offline repair of error CDRs is provided.
CDR error tolerance

Transmission reliability The iGWB Server transmits CDRs to the billing center through FTP or FTAM. Both retransmission and broken retransmission are supported.
Four-Level Buffer of CDR Information

From the completion of a call to the transfer of CDR information to the billing center, there are four levels of CDR buffer against CDR data loss due to abnormal causes. The four levels are host CDR pool buffer, original CDR file buffer, final CDR file buffer and automatic CDR file backup on the iGWB server.
! ! ! !
Host CDR pool buffer: The host CDR pool can store the original CDRs. Original CDR file buffer: After being transferred from the host CDR pool to the iGWB Server, the original CDRs are stored first in the hard disk as the level-two buffer. Final CDR file buffer: After processing the original CDRs, the iGWB Server saves the final CDR data to be sent to the billing center to carry out the level-three buffer. Automatic backup in iGWB Server: The iGWB Server adopts the 1+1 backup mode. The active server regularly backs up the CDR data in the hard disk to the standby server to carry out the level-four buffer.
Issue 03 (2006-09-30)
7-5
Security of CDR Console

!
CDR console lock: Subscriber name and password are protected by the CDR console. The CDR console auto logs off if no operation is performed for a long time to prevent unauthorized access. Operation restriction of CDR client: CDR data and logs can be viewed at the CDR client, but cannot be deleted or modified. This is to ensure the security of CDR data. IP address restriction of CDR client: By configuring the Web Server, the IP address of the CDR client (WS) can be restricted to prevent the access of unauthorized nodes.
! !
7.2 Security Design

7.2.1 Networking Application Security
Protocol Interface Security
The MSOFTX3000 provides protocol interfaces externally. Except necessary services, such as H.248 and SIP, the other network services such as HTTP are disabled. This is to prevent unauthorized access through invalid services.
Protocol Packet Security

The MSOFTX3000 supports the security processing of the H.248 and SIP protocols, as well as the encryption of the H.248 and SIP packets. This ensures the security of the protocol packets.
7.2.2 Data Security

The MSOFTX3000 provides strict data protection mechanisms:
!
The MSOFTX3000 supports a synchronous data backup mechanism between the active and standby boards in real time. Whenever an active board is down, the standby board is auto switched to be the active one. All programs and data on the board are immediately brought into effect. The MSOFTX3000 supports the backup of the data from the database of the active processor to a flash memory. This enables quick restart of the active processor after acquiring data from the flash memory. The MSOFTX3000 supports an automatic CDR backup mechanism. The BAM conducts a regular CRC check of the mainframe data. If the data of the mainframe is inconsistent with that of the background, the BAM starts a setting procedure to the foreground. If the setting procedure fails after preset attempts, an alarm is generated to remind the operation staff to restore the data.
! !
7.2.3 O&M Security

The following measures are taken in the MSOFTX3000 to ensure the O&M security of the system:
!
The MSOFTX3000 supports the multi-level subscriber authority management to prevent unauthorized access.
7-6
Issue 03 (2006-09-30)

! ! ! !
All operations performed by the maintenance staff are recorded in a log to ensure the ability to locate and trace the history operations. Prompting alarms are available against system exceptions due to accidental errors. A check function is provided for the operators configuration activities, and an unauthorized configuration is refused. The maintenance and operation system protects subscriber names and passwords. The system auto logs off if no operation is performed for a long time to prevent unauthorized access.
7.2.4 Security Authentication Information

The MSOFTX3000 passed the security authentications as listed in Table 7-1: Table 7-1 Security authentications Item EMC Standard EN 55022 FCC part 15 VCCI AS/NZS 3548 GR-1089 Safety EN/IEC 60950 UL60950 IEC60950 GR-1089
Issue 03 (2006-09-30)
7-7
8 Technical Specifications and Environmental Requirements
8
About This Chapter
Title
Technical Specifications and Environmental Requirements
The following table lists the contents of this chapter. Description This section describes the technical specifications of the MSOFTX3000. This section describes the EMC specifications of the MSOFTX3000. This section describes the environmental requirements of the MSOFTX3000.
8.1 Technical Specifications 8.2 EMC Specifications 8.3 Environmental Requirements
Issue 03 (2006-09-30)
8-1
8.1 Technical Specifications

8.1.1 System Capacity
Table 8-1 System capacity Parameter Maximum subscribers (VMSC Server) Maximum controllable MGWs Maximum accessible RNCs Maximum accessible BSCs Specification 1,800,000 (0.025 Erl) 300 128 128
Table 8-2 Reference traffic model Parameter Average traffic of mobile subscribers in busy hours Average call duration of mobile subscribers Location registration and update times of a mobile subscriber per busy hour Handover times of a mobile subscriber per call SMSs of a mobile subscriber per busy hour Typical Value 0.025 Erl 60s 2 0.2 2
8.1.2 System Processing Capability

Table 8-3 System processing capability Parameter BHCA for VMSC Server BHCA for GMSC Server BHCA for TMSC Server Specification 2700k 7200k 9000k
8-2
Issue 03 (2006-09-30)
8.1.3 Protocol Processing Capability

Table 8-4 Protocol processing capability Item Supported signaling point coding types Maximum source signaling points Maximum destination signaling points Maximum IP signaling bandwidth Maximum 64-kbit/s MTP links Maximum 2-Mbit/s MTP links Maximum SCTP links Maximum 64-kbit/s MTP links on a single WCSU board Maximum 2-Mbit/s MTP links on a single WCSU board Maximum SCTP links on a single WBSG board Maximum TCP/UDP links on a single WBSG board Maximum dispatched packets on a single WIFM board Clock stratum Specification 14-bit and 24-bit coding types 16 by default (256 at maximum) 256 by default (64000 at maximum) 4 100 Mbit/s 1728 108 2304 32 2 128 1500 15,000 packets/second Stratum-2 A
8.1.4 CDR Processing Capability

Table 8-5 CDR processing capability Item Average length of an original CDR CDR buffer capacity on a single WCCU/WCSU board Maximum original CDRs on a single WCCU/WCSU board Maximum CDRs transferred through a single WCCU/WCSU board Storage capacity for CDRs on the iGWB CDR processing capability of the iGWB Specification 810 bytes 190 MB 246,000 70 per second 730 GB (RAID 5) 2300 CDR/s
Issue 03 (2006-09-30)
8-3
8.1.5 Number Analysis Capability

Table 8-6 Number analysis capability Parameter Maximum length of a number for analysis Maximum call prefixes Maximum roaming/handover numbers Maximum GT codes Maximum GT capability on a single 64-kbit/s MTP link Specification 32 digits 30000 10000 4096 by default (8192 at maximum) 60 GTT/s
8.1.6 Reliability Specifications

Table 8-7 Reliability specifications Parameter System availability (A) Mean Time Between Failure (MTBF) Mean Time To Repair (MTTR) DOWN duration Board restart duration Board swapping duration Single subrack startup duration Fully configured system restart duration Dual-homing switchover duration Specification 99.99953% 24 years (fully configured) 42 years (single subrack) 1 hour (excluding preparation time) < 3 minutes/year < 1.5 minutes < 6 seconds < 6 minutes < 30 minutes < 3 minutes
8.1.7 Environmental Specifications

Table 8-8 Environmental adaptation (long term operation) Item Height above sea level Atmospheric pressure Adaptation Specification 4,000 m 70 kPa to 106 kPa
8-4
Issue 03 (2006-09-30)
Item Temperature Relative humidity Earthquake-proof performance
Adaptation Specification +5C to +45C 5% to 85% Able to sustain Richter scales 7 to 9
Table 8-9 Noise specifications Requirement NEBS ETS Specification 65 dBA (internally limited to 60 dBA) 7.2 bels
8.1.8 Mechanical Data of Cabinet

Table 8-10 Mechanical data of cabinet Item Model Dimensions (W D H) Number of cabinets when fully configured Weight of integrated configuration cabinet (empty) Weight of integrated configuration cabinet (fully configured) Weight of service processing cabinet (empty) Weight of service processing cabinet (fully configured) Designed bearing capacity of the floor in the equipment room Available height Specification/Model N68-22 (complies with IEC 297 and NEBS requirements) 600 mm 800 mm 2200 mm 3 135 kg 400 kg 135 kg 400 kg 600 kg/m2 46 U (1 U = 44.45 mm)
Issue 03 (2006-09-30)
8-5
8.1.9 Power Supply

Table 8-11 Power supply Item Working voltage (standard) Specification Rated voltage Voltage fluctuations Working voltage (in Commonwealth of Independent States) Working current Impulse current Fuse of DC Power Distribution Box (PDB) Rated voltage Voltage fluctuations 48 V DC 40 V to 57 V 60 V DC 51 V to 69 V
40 A@48 V (a fully configured cabinet) > 1.5 times of rated current 63 A
The specifications listed in Table 8-11 are for reference only. They can be changed as needed.
8.1.10 Power Consumption

Table 8-12 Overall power consumption Functional Unit Power Consumption (kW) 2 4 6 Calculation
1 cabinet 2 cabinets 3 cabinets (fully configured)
Most boards in a subrack work in active/standby mode. That is, the standby board is not fully loaded when the active one is working normally. For one fully configured subrack, the maximum power consumption is considered as 90% of standard power consumption. In an integrated configuration cabinet, the server, disk array and expansion subrack do not work in the fully loaded mode. For one fully configured cabinet, the maximum power consumption is considered as 85% of standard power consumption. To get the power consumption in the unit of BTU, convert the values based on 1 W = 3.413 BTU.
8-6
Issue 03 (2006-09-30)
Table 8-13 Power consumption (functional units) Functional Unit Power Consumption (W) 20 100 250 250 250 200 40 50 16 2 16 18 18 26 16 Configuration
PDF OSTA subrack BAM iGWB XPTU Disk array LAN Switch LCD monitor WSMU + WSIU WALU WHSC WIFM + WBFI WAFM + WBAI WCSU and WSGU WBSG, WCCU, WCDB, WVDB, and WMGC WEPI WCKI
One PDF The backplane, the fan shelf and the UPWR An HP/IBM/HUAWEI DC Power Server An HP/IBM/HUAWEI DC Power Server An HP/IBM/HUAWEI DC Power Server On an IBM server, 10 hot swappable SCSI hard disks are needed. A Huawei Quidway S3026C Ethernet switch
4 15
Issue 03 (2006-09-30)
8-7
8.2 EMC Specifications

8.2.1 Electromagnetic Interference Specifications
Conducted Emission (CE)
Table 8-14 CE specifications through the 48 V power supply port Frequency Range Limits (dBV) Average Limit 0.02 MHz to 0.15 MHz 0.15 MHz to 0.50 MHz 0.50 MHz to 30 MHz 66 60 Quasi-Peak Limit 79 79 73
The CE tests are designed to show the interference signals of the product that are conducted through the cable port.
Radiated emission (RE)

Table 8-15 RE specifications Frequency Band (MHz) 30 to 230 230 to 1000 Quasi-Peak Limit (dBV/m) 40 47
The RE tests are designed to show the interference signals of the product radiated from the shell port. The measurement point is 10 meters away from the MSOFTX3000.
8.2.2 Electromagnetic Susceptibility Specifications

Conducted Susceptibility (CS)
These items are applicable to 48 V DC supply cable side and signal side (when the connection line between the ports exceeds 3 meters).
8-8
Issue 03 (2006-09-30)
Table 8-16 CS specifications Measured Port DC side Signal side Frequency Range 150 kHz to 230 MHz Voltage Criterion 10 V 10 V Performance Criterion A A
The CS tests are designed to show the endurance of the product on the external interference through cable port coupling.
Radiated Susceptibility (RS)

Table 8-17 RS specifications Frequency Range 80 MHz to 1 GHz Voltage Criterion 10 V/m Performance Criterion A
The RS tests are designed to show the endurance of the product on the external interference through shell port coupling.
Electrostatic Discharge (ESD)

These items are applicable to ESD sources, including humans, which may damage the components of the product. Table 8-18 ESD specifications Discharge Mode Air discharge Voltage Criterion 8 kV 15 kV Contact discharge 6 kV 8 kV Performance Criterion B R B R
The ESD tests are designed to show the endurance of the product on electrostatic interference. There are two discharge modes: contact discharge and air discharge.
Electrical Fast Transient (EFT)

These items are applicable to DC side and certain signal side (when the connection line between the ports exceeds 3 meters).
Issue 03 (2006-09-30)
8-9
Table 8-19 EFT specifications Measured Port AC side DC side Signal side Voltage Criterion 2 kV 2 kV 1 kV Performance Criterion B B B
The EFT tests are designed to show the impact of high and low frequency energy pulses on the product caused by an inductive load changeover.
Surge
These items are applicable to DC supply cable side and signal side (such as the port of an indoor signal line or E1 cable). Table 8-20 Surge specifications Measured Port DC side Signal side Indoor (cabling inside the system) Voltage Criterion 1 kV (differential mode) 2 kV (common mode) 1 kV B Performance Criterion B
Performance criterion A: The MSOFTX3000 continues to operate during and after the test without any change of software or equipment data, or any reduction in performance. The equipment related data refers to all the data stored in the memory as well as the data being processed. Performance criterion B: The MSOFTX3000 continues to operate after the test. During the test, a certain reduction in performance as defined by the product is allowed, but the software data and the data in the memory is not changed, and the established communication links are not interrupted. After the test, the MSOFTX3000 auto recovers to the normal performance without manual intervention. Performance criterion C: Temporary loss of function is allowed during the test, which can be restored after the test, typically after the shortest time required by system restart. The physical damage or reduction in performance of system OS software, however, does not occur. Performance criterion R: The MSOFTX3000 is not damaged or faulty (including software damage) after the test. Damage of protective components caused by external interference signals is allowed to a certain extent. After the damaged components are replaced and the relative operation parameters are reset, the equipment can operate normally.
8-10
Issue 03 (2006-09-30)
8.3 Environmental Requirements

8.3.1 Storage Environment
Climate Environment
Table 8-21 Climate environment requirements (for storage) Item Height above sea level Atmospheric pressure Temperature Temperature change rate Relative humidity Solar radiation Heat radiation Wind speed Range 5,000 m 70 kPa to 106 kPa 40C to +70C 1C/min 10% to 100% 1,120 W/s 600 W/s 30 m/s
Biological Environment
! !
Ensure that the equipment is kept in a place free from epiphyte, mildew and other microorganisms. Prevent rodents, such as mice, to avoid damage to the equipment.
Air Cleanness
! !
The air must be free from explosive, conductive, magneto-conductive, or corrosive dust. The density of mechanically active materials complies with the requirements listed in Table 8-22:
Table 8-22 Density requirements for mechanically active materials (for storage) Mechanically Active Material Suspending dust Deposited dust Sand Unit mg/m mg/mh mg/m Content 5.00 20.0 300 Diameter 75 m 75 m to 150 m 150 m to 1,000 m
The density of chemically active materials complies with the requirements listed in Table 8-23:
Issue 03 (2006-09-30)
8-11
Table 8-23 Density requirements for chemically active materials (for storage) Chemically Active Material SO2 H2S NO2 NH3 Cl2 HCl HF O3 Unit mg/m mg/m mg/m mg/m mg/m mg/m mg/m mg/m Content 0.30 to 1.00 0.10 to 0.50 0.50 to 1.00 1.00 to 3.00 0.10 to 0.30 0.10 to 0.50 0.01 to 0.03 0.05 to 0.10
Mechanical Stress
Table 8-24 Mechanical stress requirements (for storage) Item Sinusoidal vibration Sub-item Offset Accelerated speed Frequency range Non-stable impulse Impulse response spectrum II Payload Range 7.0 mm 2 Hz to 9 Hz 250 m/s 5 kPa 20.0 m/s 9 Hz to 200 Hz
Impulse response spectrum: It refers to the maximum response curve of the accelerated speed generated by the equipment under the specified impulse motivation. Impulse response spectrum II means that the duration of half-sine impulse response spectrum is 6 ms. Payload: It refers to the bearable pressure from the upper piled equipment with package in prescribed piling mode.
8-12
Issue 03 (2006-09-30)
Waterproof Requirements
Table 8-25 Waterproof requirements Item To place the equipment in the equipment room (recommended) To place the equipment outside the equipment room Requirements
!
There is no water on the ground and no water flows into the package. Keep the equipment away from devices such as automatic fire extinguishers and heating pipes. The package is stored well. Waterproof measures are taken to prevent rain from entering the package. The package is not exposed to sun. There is no water on the ground where the package is placed and no water flows into the package.
! !
! !
8.3.2 Transportation Environment

Climate Environment
Table 8-26 Climate environment requirements (for transportation) Item Height above sea level Atmospheric pressure Temperature Temperature change rate Relative humidity Solar radiation Heat radiation Wind speed Rain Range 5,000 m 70 kPa to 106 kPa 40C to +70C 3C/min 10% to 100% 1,120 W/s 600 W/s 30 m/s 6 mm/min
! !
Ensure that the equipment is kept in a place free from epiphyte, mildew and other microorganisms. Prevent rodents, such as rats from damaging the equipment.
Issue 03 (2006-09-30)
8-13
Air Cleanness
! !
Table 8-27 Density requirements for mechanically active materials (for transportation) Mechanically Active Material Suspending dust Deposited dust Sand Unit mg/m mg/mh mg/m Content No requirement 3.0 100 Diameter 75 m 75 m to 150 m 150 m to 1,000 m
Table 8-28 Density requirements for chemically active materials (for transportation) Chemically Active Material SO2 H2S NO2 NH3 Cl2 HCl HF O3 Unit mg/m mg/m mg/m mg/m mg/m mg/m mg/m mg/m Content 1.00 0.50 1.00 3.00 0.30 0.05 0.03 0.10
Mechanical Stress
Table 8-29 Mechanical stress requirements (for transportation) Item Sinusoidal vibration Sub-item Offset Accelerated speed Frequency range Range 7.5 mm 2 Hz to 9 Hz 20.0 m/s 9 Hz to 200 Hz 40.0 m/s 200 Hz to 500 Hz
8-14
Issue 03 (2006-09-30)
Item Random vibration
Sub-item Spectrum density of accelerated speed Frequency range
Range 10 m/s 2 Hz to 9 Hz 300 m/s 10 kPa 3 m/s 9 Hz to 200 Hz 1 m/s 200 Hz to 500 Hz
Non-stable impulse
Impulse response spectrum II Payload
Waterproof Requirements
While transporting the equipment, ensure that the following requirements are met:
! ! !
The package is stored properly. Waterproof measures are taken in the transportation vehicles to prevent rain from entering the package. There is no water inside the transportation vehicles.
8.3.3 Running Environment

Climate Environment
Table 8-30 Temperature and humidity requirements Equipment Temperature Working for a Long Term MSOFTX3000 +5C to +45C Working for a Short Term 5C to +55C Relative Humidity Working for a Long Term 5% to 85% Working for a Short Term 5% to 95%
The measurement points of temperature and humidity of the MSOFTX3000 refer to the values measured 1.5 meters above the floor and 0.4 meter away from the front of the MSOFTX3000 rack when there are no protection panels in the front and back of the MSOFTX3000 rack. Short term means that the consecutive working duration is not more than 48 hours or that the continuous working duration in a year is not more than 15 days.
Issue 03 (2006-09-30)
8-15
Table 8-31 Other climate environment requirements Item Height above sea level Atmospheric pressure Temperature change rate Solar radiation Heat radiation Wind speed IP level Range 4,000 m 70 kPa to 106 kPa 5 C/h 700 W/s 600 W/s 1 m/s IP50
! !
Ensure that the equipment is kept in a place free from epiphyte, mildew and other microorganisms. Prevent rodents, such as rats from damaging the equipment.
Air Cleanness
! !
Table 8-32 Density requirements for mechanically active materials (for equipment running) Mechanically Active Material Dust particle Suspending dust Deposited dust Sand Unit particle/m mg/m mg/mh mg/m Content 3 105 0.2 1.5 30 Diameter 5 m 75 m 75 m to 150 m 150 m to 1,000 m
Table 8-33 Density requirements for chemically active materials (for equipment running) Chemically Active Material SO2 H2S Unit mg/m mg/m Content 0.30 to 1.00 0.10 to 0.50
8-16
Issue 03 (2006-09-30)
Chemically Active Material NO2 NH3 Cl2 HCl HF O3 CO
Unit mg/m mg/m mg/m mg/m mg/m mg/m mg/m
Content 0.50 to 1.00 1.00 to 3.00 0.10 to 0.30 0.10 to 0.50 0.01 to 0.03 0.05 to 0.10 5.0
Mechanical Stress
Table 8-34 Mechanical stress requirements (for equipment running) Item Sinusoidal vibration Sub-item Offset Accelerated speed Frequency range Non-stable impulse Impulse response spectrum II Payload Range 5.0 mm 5 Hz to 62 Hz 50 m/s 0 2.0 m/s 62 Hz to 200 Hz
Issue 03 (2006-09-30)
8-17
9 Compliant Specifications
9
About This Chapter
Title 9.1 3GPP Specifications 9.2 ITU-T Specifications 9.3 Other Technical Specifications
Compliant Specifications
The following table lists the contents of this chapter. Description This section describes the compliant 3GPP specifications of the MSOFTX3000. This section describes the compliant ITU-T specifications of the MSOFTX3000. This section describes the other compliant specifications of the MSOFTX3000.
Issue 03 (2006-09-30)
9-1
9.1 3GPP Specifications

The MSOFTX3000 conforms to the following 3GPP R4 specifications: Table 9-1 The compliant 3GPP R4 specifications (2004.12) of the MSOFTX3000 Serial No. TS 21.133 TS 22.001 TS 22.002 TS 22.003 TS 22.004 TS 22.011 TS 22.016 TS 22.024 TS 22.041 TS 22.053 TS 22.066 TS 22.067 TS 22.071 TS 22.078 TS 22.081 TS 22.082 TS 22.083 TS 22.084 TS 22.085 TS 22.086 TS 22.088 TS 22.090 TS 22.101 Specifications 3G security; Security threats and requirements Principles of Circuit Telecommunication Services Supported by a Public Land Mobile Network (PLMN) Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN) Circuit Teleservices supported by a Public Land Mobile Network (PLMN) General on supplementary services Service accessibility International Mobile Equipment Identities (IMEI) Description of Charge Advice Information (CAI) Operator Determined Call Barring Tandem Free Operation (TFO); Service description; Stage 1 Support of Mobile Number Portability (MNP); Stage 1 enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 1 Location Services (LCS); Stage 1 Customized Applications for Mobile network Enhanced Logic (CAMEL); Service description; Stage 1 Line Identification supplementary services; Stage 1 Call Forwarding (CF) Supplementary Services; Stage 1 Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 1 MultiParty (MPTY) supplementary service; Stage 1 Closed User Group (CUG) supplementary services; Stage 1 Advice of Charge (AoC) supplementary services; Stage 1 Call Barring (CB) supplementary services; Stage 1 Unstructured Supplementary Service Data (USSD); Stage 1 Service aspects; Service principles Issued By 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP
9-2
Issue 03 (2006-09-30)
Serial No. TS 22.105 TS 22.115 TS 22.129 TS 23.002 TS 23.003 TS 23.007 TS 23.008 TS 23.009 TS 23.011 TS 23.012 TS 23.014 TS 23.015 TS 23.016 TS 23.018 TS 23.038 TS 23.040 TS 23.053 TS 23.066 TS 23.067 TS 23.078 TS 23.081 TS 23.082 TS 23.083 TS 23.084 TS 23.085 TS 23.086 TS 23.087
Specifications Services and service capabilities Service Aspects Charging and billing Handover requirements between UTRAN and GERAN or other radio systems Network architecture Numbering, Addressing and Identification Restoration procedures Organization of subscriber data Handover procedures Technical realization of Supplementary Services Location management procedures Support of Dual Tone Multi Frequency (DTMF) signaling Technical realization of Operator Determined Barring (ODB) Subscriber data management; Stage 2 Basic Call Handling; Technical realization Alphabets and language-specific information Technical realization of Short Message Service (SMS) Tandem Free Operation (TFO); Service description; Stage 2 Support of GSM Mobile Number Portability (MNP) stage 2 Enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 Customized Applications for Mobile network Enhanced Logic (CAMEL); Stage 2 Line Identification supplementary services; Stage 2 Call Forwarding (CF) Supplementary Services; Stage 2 Call Waiting (CW) and Call Hold (HOLD) Supplementary Service; Stage 2 MultiParty (MPTY) Supplementary Service; Stage 2 Closed User Group (CUG) Supplementary Service; Stage 2 Advice of Charge (AoC) Supplementary Service; Stage 2 User-to-User Signaling (UUS) supplementary service; Stage 2
Issued By 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP
Issue 03 (2006-09-30)
9-3
Serial No. TS 23.088 TS 23.090 TS 23.101 TS 23.107 TS 23.108 TS 23.146 TS 23.153 TS 23.205 TS 23.221 TS 23.271 TS 24.002 TS 24.007 TS 24.008 TS 24.010 TS 24.011 TS 24.030 TS 24.067 TS 24.080 TS 24.081 TS 24.082 TS 24.083 TS 24.084 TS 24.085 TS 24.086 TS 24.088
Specifications Call Barring (CB) Supplementary Service; Stage 2 Unstructured Supplementary Service Data (USSD); Stage 2 General UMTS Architecture Quality of Service (QoS) concept and architecture Mobile radio interface layer 3 specification core network protocols; Stage 2 (structured procedures) Technical realization of fax Group 3 service non-transparent Out of Band Transcoder Control; Stage 2 Bearer-independent circuit-switched core network; Stage 2 Architectural requirements Location Services (LCS); Functional description; Stage 2 GSM-UMTS Public Land Mobile Network (PLMN) Access Reference Configuration Mobile radio interface signaling layer 3; General Aspects Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 Mobile Radio Interface Layer 3 - Supplementary Services Specification - General Aspects Point-to-Point (PP) Short Message Service (SMS) Support on Mobile Radio Interface Location Services (LCS); Supplementary service operations; Stage 3 Enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 3 Mobile radio Layer 3 supplementary service specification; Formats and coding Line Identification Supplementary Service; Stage 3 Call Forwarding supplementary service; Stage 3 Call Waiting (CW) and Call Hold (HOLD) Supplementary Service; Stage 3 MultiParty (MPTY) Supplementary Service; Stage 3 Closed User Group (CUG) Supplementary Service; Stage 3 Advice of Charge (AoC) Supplementary Service; Stage 3 Call Barring (CB) Supplementary Service; Stage 3
Issued By 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP
9-4
Issue 03 (2006-09-30)
Serial No. TS 24.090 TS 24.096 TS 25.410 TS 25.413 TS 29.002 TS 29.007
Specifications Unstructured Supplementary Service Data (USSD); Stage 3 Name Identification Supplementary Service; Stage 3 UTRAN Iu Interface: General Aspects and Principles UTRAN Iu interface Radio Access Network Application Part (RANAP) signaling Mobile Application Part (MAP) specification General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) Information Element Mapping between Mobile Station Base Station System (MS - BSS) and Base Station System Mobile-services Switching Centre (BSS - MCS) Signaling Procedures and the Mobile Application Part (MAP) Signaling Interworking for Supplementary Services Serving GPRS Support Node SGSN - Visitors Location Register (VLR); Gs Interface Network Service Specification General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification Customized Applications for Mobile network Enhanced Logic (CAMEL); CAMEL Application Part (CAP) specification Application of the Radio Access Network Application Part (RANAP) on the E-interface Mobile Application Part (MAP) specification for Gateway Location Register (GLR); Stage 3 Signaling System No. 7 (SS7) signaling transport in core network; Stage 3 Application of Q.1900 series to bearer-independent circuit-switched core network architecture; Stage 3 Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3 Telecommunication management; Charging management; Charging principles Telecommunication management; Charging management; Charging data description for the Circuit Switched (CS) domain 3G security; Security architecture
Issued By 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP
TS 29.010
3GPP
TS 29.011 TS 29.016 TS 29.018
3GPP 3GPP 3GPP
TS 29.078
3GPP
TS 29.108 TS 29.120 TS 29.202 TS 29.205 TS 29.232 TS 32.200 TS 32.205
3GPP 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP
TS 33.102
3GPP
Issue 03 (2006-09-30)
9-5
Serial No. TS 33.103 TS 33.105 TS 33.106 TS 33.107 TS 33.120 TS 48.006
Specifications 3G security; Integration guidelines Cryptographic Algorithm requirements Lawful interception requirements 3G security; Lawful interception architecture and functions Security Objectives and Principles Signaling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS MSC) interface Mobile Switching Centre - Base Station system (MSC-BSS) Interface Layer 3 Specification
Issued By 3GPP 3GPP 3GPP 3GPP 3GPP 3GPP
TS 48.008
3GPP
9.2 ITU-T Specifications

The MSOFTX3000 conforms to the following ITU-T specifications: Table 9-2 The compliant ITU-T specifications of the MSOFTX3000 Serial No. G.701 G.702 G.703 G.704 G.706 Specifications Vocabulary of digital transmission and multiplexing, and pulse code modulation (PCM) terms Digital hierarchy bit rates Physical/electrical characteristics of hierarchical digital interfaces Synchronous frame structures used at primary and secondary hierarchical levels Frame alignment and cyclic redundancy check (CRC) procedures relating to basic frame structures defined in Recommendation G.704 Interfaces for the Optical Transport Network (OTN) Characteristics of primary PCM multiplex equipment operating at 2048 kbit/s Characteristics of a synchronous digital multiplex equipment operating at 2048 kbit/s timing requirements of slave clocks suitable for user as node clocks in synchronization networks The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy Issued By ITU-T ITU-T ITU-T ITU-T ITU-T
G.709 G.732 G.736 G.812 G.823
ITU-T ITU-T ITU-T ITU-T ITU-T
9-6
Issue 03 (2006-09-30)
Serial No. I.150 I.361 I.430 I.431 I.432 I.610 Q.1218 Q.1912.5 Q.1950 Q.2110 Q.2140
Specifications B-ISDN asynchronous transfer mode functional characteristics B-ISDN ATM layer specification Basic user-network interface - Layer 1 specification Primary rate user-network interface - Layer 1 specification B-ISDN User-Network Interface - Physical layer specification B-ISDN O&M principles and functions Recommendation Q.1218 (10/95) - Interface Recommendation for intelligent network CS-1 Session Initiation Protocol for Telephones (SIP-T) Bearer independent call bearer control protocol B-ISDN ATM adaptation layer - Service specific connection oriented protocol (SSCOP) B-ISDN ATM adaptation layer - Service specific coordination function for signaling at the network node interface (SSCF at NNI) B-ISDN Signaling ATM adaptation layer - Layer management for the SAAL at the network node interface Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140 Specifications of Signaling System R2 - Provision of a forward-transfer Signaling facility functional description of the message transfer part (MTP) of Signaling System No.7 Signaling Data Link Message Transfer Part Signaling Link Message Transfer Part - Signaling network functions and messages Signaling network structure Message Transfer Part - Signaling performance Message Transfer Part - Testing and maintenance Functional description of the Signaling Connection Control Part Definition and function of signaling connection control part messages Signaling Connection Control Part formats and codes
Issued By ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T
Q.2144 Q.2210 Q.4xx Q.701 Q.702 Q.703 Q.704 Q.705 Q.706 Q.707 Q.711 Q.712 Q.713
ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T
Issue 03 (2006-09-30)
9-7
Serial No. Q.714 Q.715 Q.716 Q.721 Q.722 Q.723 Q.724 Q.725 Q.730 Q.761 Q.762 Q.763 Q.764 Q.767 Q.771 Q.772 Q.773 Q.774 Q.775 Q.787 Q.921 Q.931 X.208 X.209
Specifications Signaling Connection Control Part Procedures Signaling Connection Control Part User Guide Signaling System No.7 Signaling connection control part (SCCP) performance Recommendation Q.721 (11/88) - Functional description of the signaling system No. 7 Telephone User Part (TUP) General function of telephone messages and signals Telephone user part formats and codes Telephone user part signaling procedures Signaling performance in the telephone application ISDN user part supplementary services Functional description of the ISDN user part of Signaling System No.7 General function of messages and Signals of ISUP Formats and codes of ISUP Signaling procedures of ISUP Application of the ISDN user part of CCITT Signaling System No.7 for international ISDN interconnections Specifications of Signaling System No.7; Functional description of transaction capabilities (TC) Specifications of Signaling System No.7; Transaction capabilities information element definitions Specifications of Signaling System No.7; Transaction capabilities formats and encoding Specifications of Signaling System No.7; Transaction capabilities procedures Guidelines for using transaction capabilities Transaction Capabilities (TC) test specification ISDN user-network interface - Data link layer specification ISDN user-network interface layer 3 specification for basic call control Specification of Abstract Syntax Notation One (ASN.1) Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)
Issued By ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T ITU-T
9-8
Issue 03 (2006-09-30)
9.3 Other Technical Specifications

The MSOFTX3000 conforms to the following technical specifications: Table 9-3 The other technical specifications Serial No. T.111.1 T.111.2 T.111.3 T.111.4 T.111.5 T.111.6 T.111.7 T.111.8 RFC0768 RFC0791 RFC0792 RFC0793 RFC0959 RFC1305 RFC2198 RFC2327 RFC2543 RFC2719 RFC2833 RFC2960 RFC3057 RFC3261 RFC3309 RFC3331 RFC3332 Specifications Functional description of the message transfer part (mtp) of signaling system no.7 Signaling data link Signaling link Signaling network functions and messages Signaling system no.7 signaling network structure Signaling system no.7 message transfer part signaling performance Testing and maintenance Numbering of international signaling point codes User Datagram Protocol (UDP) Internet Protocol (IP) Internet Control Message Protocol (ICMP) Transmission Control Protocol (TCP) File Transfer Protocol (FTP) Network Time Protocol (NTP) RTP Payload for Redundant Audio Data SDP: Session Description Protocol SIP: Session Initiation Protocol Framework Architecture for Signaling Transport RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals Stream Control Transmission Protocol (SCTP) ISDN Q.921-User Adaptation Layer (IUA) Session Initiation Protocol (SIP) V2.0 Stream Control Transmission Protocol (SCTP) Checksum Change SS7 MTP2 User Adaptation Layer (M2UA) SS7 MTP3-User Adaptation Layer (M3UA) Issued By ANSI ANSI ANSI ANSI ANSI ANSI ANSI ANSI IETF IETF IETF IETF IETF IETF IETF IETF IETF IETF IETF IETF IETF IETF IETF IETF IETF
Issue 03 (2006-09-30)
9-9
Serial No. RFC3372 RFC3551 ISO8571 IEC 60297
Specifications Session Initiation Protocol for Telephones (SIP-T) RTP Profile for Audio and Video Conferences with Minimal Control File Transfer Access and Management Protocol (FTAM) Mechanical structures for electronic equipment - Dimensions of mechanical structures of the 482,6 mm (19 in) series
Issued By IETF IETF ISO IEC
9-10
Issue 03 (2006-09-30)
10 Installation
10
Installation
The MSOFTX3000 cabinet has been assembled and debugged before delivery, with its internal cables connected according to the customer's requirement. On site, you need to fix the cabinet, install boards, connect external cables, and install and load application software only. The cabinet can be installed either on the cement floor or on the ESD-preventive floor. The support and the guide rail are needed in the case of installation on the ESD-preventive floor. In the MSOFTX3000 cabinet, the cables adopt the rear leading-out mode, and the boards are hot swappable, to facilitate expansion and board replacement. In the MSOFTX3000 cabinet, the external interfaces for cables (including power cable, transmission cable, and signal cable) are positioned on top or bottom of the cabinet and printed with clear indications to make cabling more convenient. Before delivery, the MSOFTX3000 cabinet has been installed with lower layer software (operating system and database software). After the hardware installation, installation of BAM applications and import of configuration data, the MSOFTX3000 system can run normally. The simple and fast method for installing hardware & software can greatly reduce the installation time, and quicken network buildup and service provision.
Issue 03 (2006-09-30)
10-1

Product Description PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Product Description PDF

Transféré par

Droits d'auteur :

Formats disponibles

HUAWEI MSOFTX3000 Product Description

2 System Structure ........................................................................................................................2-1

3 Interfaces, Signaling, and Protocols .......................................................................................3-1

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description 3.1.2 Interface Specifications........................................................................................................................3-3

5 Services and Functions..............................................................................................................5-1

6 Networking and Application...................................................................................................6-1

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

7 Reliability and Security Design ..............................................................................................7-1

8 Technical Specifications and Environmental Requirements ............................................8-1

9 Compliant Specifications .........................................................................................................9-1

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

9.3 Other Technical Specifications......................................................................................................................9-9

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

Huawei Technologies Proprietary

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

1.1 Product Orientation

BSS 2G Access PSTN 3G Access MGW (UMG8900) MGW (UMG8900)

HLR UTRAN SGSN GGSN Internet

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

The UMG8900 provided by Huawei serves as an MGW, as shown in Figure 1-1.

Note: PLMN = Public Land Mobile Network

1.1.2 Features of Huawei's Mobile Softswitch Solution

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

Saving network resources

High integration Large capacity Powerful processing capability

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

A control core Open interfaces Universal protocols

The distributed media gateway reduces alternative routes in local transmission.

Dual homing Iu-Flex

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

Benefit New services can be offered quickly and easily.

1.1.3 Introduction to the MSOFTX3000

VMSC Server/VLR GMSC Server TMSC Server MSC/SSP MGCF

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

PSTN Integrated services digital network (ISDN) Other PLMNs

The GMSC server performs important functions, including:

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

Routing analysis Intra-network toll call convergence

1.2 Product Features

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

1.2.2 Powerful and Flexible Networking Capabilities

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Product Description

Interworking and Benefits

Satellite transmission links FTP and FTAM MML