Manual Msoftx3000

BOM Code
MSOFTX3000 V200R008 Mobile SoftSwtich Center

Product Description
Issue V1.0
Date 2009-05-15
HUAWEI TECHNOLOGIES CO., LTD.

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service.
Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, 518129, People’s Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
HUAWEI MSOFTX3000 Mobile SoftSwtich Center
Product Description Contents
Contents
1 Introduction.................................................................................................................................1-1
1.1 Product Orientation .......................................................................................................................................1-1
1.1.1 Introduction to Huawei Mobile Softswitch Solution ...........................................................................1-1
1.1.2 Introduction to the MSOFTX3000.......................................................................................................1-3
1.1.3 Customer Value of the MSOFTX3000.................................................................................................1-4
2 Product Feature...........................................................................................................................2-1
2.1 Advanced OSTA2.0 Platform........................................................................................................................2-1
2.2 New Solution.................................................................................................................................................2-1
2.2.1 Embedded VIG ....................................................................................................................................2-1
2.2.2 SIP-I Based Nc.....................................................................................................................................2-2
2.2.3 Calling Name Presentation...................................................................................................................2-2
2.2.4 Non-Interrupting Upgrade....................................................................................................................2-2
2.2.5 Intelligent Power Consumption Control of the UMG8900 ..................................................................2-2
2.2.6 Disaster Handling.................................................................................................................................2-2
2.2.7 Direct Short Message Delivery ............................................................................................................2-3
2.2.8 Multi-Operator Core Network..............................................................................................................2-3
2.2.9 BSC Local Switching...........................................................................................................................2-3
2.2.10 Voice Quality Enhancement ...............................................................................................................2-3
2.3 IP ...................................................................................................................................................................2-4
2.3.1 IP-Based A Interface ............................................................................................................................2-4
2.3.2 IP-Based Iu Interface ...........................................................................................................................2-4
2.3.3 IP over E1.............................................................................................................................................2-4
2.3.4 RTP Multiplexing.................................................................................................................................2-4
2.3.5 SCTP Multi-Homing............................................................................................................................2-5
2.3.6 IP CAC.................................................................................................................................................2-5
2.3.7 BFD......................................................................................................................................................2-5
2.4 Reliability......................................................................................................................................................2-6
2.4.1 Equipment-Level Redundancy.............................................................................................................2-6
2.4.2 Network-Level Redundancy ................................................................................................................2-6
2.5 Services .........................................................................................................................................................2-8
2.5.1 Mobile Number Portability ..................................................................................................................2-8
2.5.2 Lawful Interception..............................................................................................................................2-8
Huawei Proprietary and Confidential

Issue V1.0 (2009-05-15) i
Copyright © Huawei Technologies Co., Ltd.
2.5.3 Call Simulation & Inspection System ..................................................................................................2-9
2.5.4 INAP-M ...............................................................................................................................................2-9
2.5.5 CHR .....................................................................................................................................................2-9
2.5.6 IWF ....................................................................................................................................................2-11
2.6 Evolution .....................................................................................................................................................2-11
2.6.1 Embedded MGCF ..............................................................................................................................2-11
3 Architecture .................................................................................................................................3-1
3.1 Hardware Structure .......................................................................................................................................3-1
3.1.1 Physical Structure ................................................................................................................................3-1
3.1.2 Logical Structure..................................................................................................................................3-6
3.2 Software Structure.........................................................................................................................................3-6
4 Networking .................................................................................................................................4-1
4.1 VMSC Networking .......................................................................................................................................4-1
4.2 GMSC Networking .......................................................................................................................................4-2
4.3 TMSC Networking ........................................................................................................................................4-3
4.4 Dual Homing Networking .............................................................................................................................4-3
4.5 MSC POOL Networking ...............................................................................................................................4-4
4.6 Solution for Huawei NGN Interworking with the CS Domain .....................................................................4-5
4.7 Evolution Strategy of Huawei Mobile Core Network ...................................................................................4-5
5 Technical Specifications ...........................................................................................................5-1

5.1 Performance Specifications...........................................................................................................................5-1
5.1.1 System Capacity...................................................................................................................................5-1
5.1.2 System Processing Capability ..............................................................................................................5-2
5.1.3 Protocol Processing Capability ............................................................................................................5-2
5.1.4 CDR Processing Capability .................................................................................................................5-2
5.1.5 Number Analysis Capability ................................................................................................................5-3
5.1.6 Environmental Specifications ..............................................................................................................5-3
5.1.7 Cabinet Specifications..........................................................................................................................5-4
5.1.8 Power Supply Specifications ...............................................................................................................5-4
5.1.9 Power Consumption Specifications .....................................................................................................5-4
5.2 Clock Specifications......................................................................................................................................5-5
5.3 EMC Specifications ......................................................................................................................................5-6
5.4 Environmental Requirements ........................................................................................................................5-7
5.4.1 Storage Environment............................................................................................................................5-7
5.4.2 Transportation Environment ................................................................................................................5-9
5.4.3 Operation Environment......................................................................................................................5-11
6 Acronyms and Abbreviations..................................................................................................6-1

Product Description Figures
Figures
Figure 1-1 Huawei mobile softswitch solution...................................................................................................1-2

Figure 2-1 BFD networking ...............................................................................................................................2-5
Figure 2-2 Dual-homing networking..................................................................................................................2-7

Figure 2-3 Networking for CHR implementation ............................................................................................2-10
Figure 3-1 Appearance of the N68E-22 cabinet .................................................................................................3-2
Figure 3-2 Cabinet configuration .......................................................................................................................3-3
Figure 3-3 Front view of a subrack ....................................................................................................................3-4
Figure 3-4 Rear view of a subrack......................................................................................................................3-5
Figure 3-5 Logical structure of the MSOFTX3000............................................................................................3-6
Figure 3-6 Software structure of the MSOFTX3000..........................................................................................3-7
Figure 4-1 Typical VMSC networking ...............................................................................................................4-1
Figure 4-2 Typical GMSC networking ...............................................................................................................4-2
Figure 4-3 Typical TMSC networking................................................................................................................4-3
Figure 4-4 1+1 assistant networking ..................................................................................................................4-4
Figure 4-5 MSC Pool networking ......................................................................................................................4-4
Figure 4-6 Networking of the solution for Huawei NGN interworking with the CS domain.............................4-5
Figure 4-7 Evolution strategy of Huawei mobile CN.........................................................................................4-6
Figure 4-8 Huawei 3GPP R5 solution ................................................................................................................4-7

Figure 5-1 Maximum allowed input jitter and lower threshold of wander .........................................................5-6
Figure 5-2 Climatic requirements for storing the MSOFTX3000 ......................................................................5-7

Issue V1.0 (2009-05-15) iii
Product Description Tables
Tables
Table 1-1 Customer value of the MSOFTX3000................................................................................................1-4

Table 3-1 Typical configuration of the MSOFTX3000.......................................................................................3-4
Table 3-2 Boards.................................................................................................................................................3-5

Table 5-1 System capacity of the MSOFTX3000...............................................................................................5-1
Table 5-2 Reference traffic model of the MSOFTX3000 ...................................................................................5-1
Table 5-3 System processing capability of the MSOFTX3000 ..........................................................................5-2
Table 5-4 Protocol processing capability of the MSOFTX3000.........................................................................5-2
Table 5-5 CDR processing capability of the MSOFTX3000 ..............................................................................5-2
Table 5-6 Number analysis capability of the MSOFTX3000 .............................................................................5-3
Table 5-7 Environmental adaptation of the MSOFTX3000 (long-term operation) ............................................5-3
Table 5-8 Noise specifications of the MSOFTX3000.........................................................................................5-3
Table 5-9 Cabinet specifications of the MSOFTX3000......................................................................................5-4
Table 5-10 Power supply specifications of the MSOFTX3000 ..........................................................................5-4
Table 5-11 Overall power consumption of the MSOFTX3000...........................................................................5-4
Table 5-12 Technical specifications of the clock synchronization system of the MSOFTX3000.......................5-5
Table 5-13 Density requirements of mechanically active substances for storing the MSOFTX3000.................5-7
Table 5-14 Density requirements of chemically active substances for storing the MSOFTX3000 ....................5-8
Table 5-15 Waterproofing requirements for storing the MSOFTX3000.............................................................5-8

Table 5-16 Climatic requirements for transporting the MSOFTX3000..............................................................5-9
Table 5-17 Density requirements of mechanically active substances for transporting the MSOFTX3000 ......5-10
Table 5-18 Density requirements of chemically active substances for transporting the MSOFTX3000 ..........5-10
Table 5-19 Mechanical stress requirements of equipment transportation for transporting the MSOFTX3000 5-10
Table 5-20 Temperature and humidity requirements for the operation of the MSOFTX3000..........................5-11
Table 5-21 Other climatic environmental requirements for the operation of the MSOFTX3000.....................5-12
Table 5-22 Density requirements of mechanically active substances for the operation of the MSOFTX3000 5-13
Table 5-23 Density requirements of chemically active substances for the operation of the MSOFTX3000 ....5-13

Issue V1.0 (2009-05-15) v
Table 5-24 Mechanical stress requirements for the operation of the MSOFTX3000 .......................................5-13
Product Description Error! Style not defined.Error! Style not defined.
1 Introduction
1.1 Product Orientation

1.1.1 Introduction to Huawei Mobile Softswitch Solution
At present, most carriers choose the sofswitch technology to build mobile core networks
(CNs). They focus on the high reliability of the network, protecting the investment when the
network is evolved to the IMS, adopting the IP technology, and reducing the operating
expenditure (OPEX). By using the distributed networking mode and IP bearer, mobile
softswitches provide carriers with the following benefits:
Reducing operation costs by improving the efficiency of network transmission
Protecting the carrier investment by supporting smooth network evolution
The mobile softswitch solution of Huawei provides a 2G and 3G convergence networking
scheme, which is easy to operate and maintain, to address the networking requirements of
carriers. The solution supports the networking schemes of the GSM, 3GPP R99, 3GPP R4,
and 3GPP R5. Figure 1-1 shows a typical networking model of the mobile softswitch solution
of Huawei for 3GPP R4.

Issue V1.0 (2009-05-15) 1-1
Error! Style not defined.Error! Style not defined. Product Description
Figure 1-1 Huawei mobile softswitch solution
Other
CN
Networks
Bearer MSC Server MSC Server
Signaling (MSOFTX3000) (MSOFTX3000)
BSS
2G Access PSTN
3G Access
MGW MGW
(UMG8900) (UMG8900) CS
PS
HLR
Internet
UTRAN
SGSN GGSN
GGSN: Gateway GPRS Support HLR: Home Location MGW: Media Gateway
Node Register
MSC server: Mobile Switching CN: Core Network CS: Circuit Switched domain
Center Server
SGSN: Serving GPRS Support PS: Packet Switched PSTN: Public Switched
Node domain Telephone Network
UTRAN: UMTS Terrestrial BSS: Base Station
Radio Access Network Subsystem
Based on the evolution strategy of the CS domain of the mobile CN and the requirement for
constructing an all IP networking, the MSC in the GSM and 3GPP R99 is divided into two
parts in the 3GPP R4 and later versions, that is, the MSC server and the MGW.
The MSC server is connected to the BSS or the UTRAN, and performs the control
functions of the CS domain, that is, mobility management, security management,
handover processing, signaling processing, call processing, and subscriber data
management (function of the VLR).
The MGW, as the endpoint of the PSTN or the PLMN, is connected to the
MSOFTX3000 and performs functions such as media transformation, bearer
management, coding/decoding of digital signals, echo cancellation, and conference
bridging.
Support for 2G/3G Convergence

Huawei offers a converged GSM/UMTS solution to help carriers to protect their investment in
the 2G network. This solution supports the simultaneous connection of the BSS and the

1-2 Issue V1.0 (2009-05-15)
UTRAN to the network, to provide services for 2G and 3G subscribers at the same time. The
2G and 3G networks can share equipment resources. Thus, carriers can reduce capital
expenditure (CAPEX) and save network resources. Besides, the network topology is
simplified. During the evolution from the GSM to the UMTS, this solution can be upgraded
online and configured dynamically. This ensures a smooth evolution process.
High Efficiency
In the Huawei mobile softswitch solution, the MGWs can be located in different cities, and IP
bearers can be used between MGWs. This simplifies the network interconnection topology
and network management, and saves transmission resources for carriers.
Huawei mobile softswitch equipment features high integration, large capacity, and powerful
processing capability. It saves equipment footprint, and reduces power consumption. Carriers
can focus their O&M on a small number of softswitch offices, thereby reducing OPEX.
The advanced IP O&M solution of Huawei provides the carriers with a visualized O&M mode
for IP networks with a capability of self-diagnosis and self-recovery.
High Reliability
The MSC Pool solution of Huawei enables automatic data backup between MSCs and thereby
implements disaster tolerance of the MSCs. In addition, the MSC server provided by Huawei
also supports the multiple backup modes of the HLR. Based on specific conditions, Huawei
uses these modes flexibly.
With the network-level flow control mechanism, Huawei ensures the service quality of
ongoing calls when the IP bearer network is congested. The advanced flow control
mechanism ensures high network reliability even when traffic is heavy.
Smooth Evolution
The fixed mobile convergence (FMC) is the trend of network development. At present,
Huawei provides integrated services, and also a number of devices that can be used in both
fixed and mobile networks.
In future, the fixed and the mobile networks can be converged through the IMS at the network
level. Huawei MSOFTX3000 V200 series are developed based on the ATCA platform and
inherit software functions completely from the CPCI platform. This enables the
MSOFTX3000 to evolve smoothly into the IMS MGCF, thus minimizing CAPEX of carriers.
1.1.2 Introduction to the MSOFTX3000

By supporting protocols and functions of both the GSM and the WCDMA, the MSOFTX3000
enables smooth evolution from the GSM to the WCDMA. The MSOFTX3000 can function as
multiple network elements (NEs) such as the VMSC server/VLR, GMSC server, TMSC
server, MSC/SSP, MGCF, and IM-SSF.
VMSC Server/VLR
The MSOFTX3000 supports many protocols, including H.248, BICC, SIP, CAP, BSSAP,
RANAP, MAP, ISUP, TUP, and BSSAP+. It can provide the functions of a VMSC server and
a VLR. When connected to the UMG8900 (functions as the MGW) and the shared
interworking function (SIWF) of Huawei, the MSOFTX3000 supports the BSS/UTRAN
access and serves as a 2G VMSC, a 3G VMSC, or a 2G/3G integrated VMSC.

Issue V1.0 (2009-05-15) 1-3
GMSC Server
The GMSC server serves as a mobile gateway office between networks and implements
functions such as route analysis and inter-network call connection and settlement. The
MSOFTX3000 provides functions such as black and white lists, call authentication, call
interception, and storage of a large number of call detail records (CDRs). When connected to
the UMG8900 of Huawei, the MSOFTX3000 can serve as a GMSC server.
TMSC Server
As a toll tandem office, the TMSC server performs functions such as route analysis and
intra-network toll call assembling. If the network is deployed on a large scale, it is
recommended that the TMSC servers be deployed in layers.
MSC/SSP
The MSOFTX3000 also provides the functions of a gsmSSF. It supports the intelligent
network (IN) control protocols such as CAP. To be specific, the MSOFTX3000 supports
CAMEL 4 and CAMEL 3 (compatible with CAMEL 1 and CAMEL 2). When the target
networking mode is adopted, the MSOFTX3000 serves as an SSP.
1.1.3 Customer Value of the MSOFTX3000

Table 1-1 Customer value of the MSOFTX3000
Benefit Description
CAPEX is Unlike the closed structure of the legacy switched circuit network (SCN),
reduced. a mobile softswitch network provides services through a centralized
control core. Besides, it helps carriers to build an open and low-cost
network and improve the speed of service deployment by supporting open
interfaces and universal protocols. The mobile softswitch technology also
enables smooth migration from 2G to 3G and IMS networks. This reduces
the CAPEX for network migration.
The centralized mobile softswitch equipment with large capacity has
higher usage rate of equipment resources in the following aspects:
The distributed media gateway reduces alternative routes in local
transmission. The flat networking mode does not require the
construction of the tandem layer.
The IP bearer reduces the transmission cost by 50% for the whole
network.
Statistics show that the CAPEX of a mobile softswitch network is 20% to
30% lower than that of a legacy SCN.
OPEX is Compared with the legacy switching equipment, the mobile softswitch
reduced. equipment is more advantageous in processing capability, high level of
integration, and low power consumption. This helps to save 60% to 70%
of the equipment room area and 30% of the power consumption.
With the bearer separated from the control, the core of the mobile
softswitch network can be located and managed in a centralized manner.
This reduces the network O&M costs.

1-4 Issue V1.0 (2009-05-15)
Benefit Description
Network The mobile softswitch network uses network-level reliability mechanisms
reliability is such as the dual homing and MSC Pool.
enhanced. The dual homing networking mode realizes the mutual backup of the
mobile softswitch equipment. In an MSC Pool network, the MSCs are in
the load sharing mode and can share resources. This enhances the usage
rate of core network resources, reduces network investment, and avoids
network congestion. The networking mode also provides an automatic
data backup mechanism to the MSCs for disaster tolerance.
New services Due to the separation of the mobile softswitch equipment and bearer
can be offered equipment, the provisioning of new services requires the configuration on
promptly. only the softswitch equipment, and the MGW in the bearer layer is not
affected. Thus, the mobile softswitch network allows users to develop and
provide new services more flexibly and quickly because the open network
structure shortens the development cycle of services and centralized
service management makes service deployment easy.

Issue V1.0 (2009-05-15) 1-5
2 Product Feature
2.1 Advanced OSTA2.0 Platform

Composed of a series of PCI Industrial Computer Manufacturers Group (PICMG3.X)
specifications, the ATCA standards are widely accepted as the standards for the
next-generation telecommunication hardware platforms.
The high integration feature of the ATCA-based products (including the MSOFTX3000)
substantially decreases the power consumption per user (compared with the CPCI platform,
the power consumption of the ATCA-based product is 50% lower per user). This is
completely in line with the increasing focus on providing eco-friendly solutions. The capacity
specifications of the ATCA-based MSOFTX3000 are the best among all the ATCA-based
products in the telecom industry.
The ATCA-based MSOFTX3000 features in large capacity and high integration. CS8.0 is the
initial release of the ATCA-based MSOFTX3000 in commercial deployment. Compared with
the traditional CPCI platform, the performance of ATCA-based boards is greatly improved.
For example, the CPU is upgraded from single core to eight cores, and the memory of the
CCU board is upgraded from 1 GB (750B) to 24 GB. Thereby, the performance, integration,
and capacity of the MSOFTX3000 are enhanced to a large extent.
The MSOFTX3000 functioning as the VMSC has the ability equivalent to up to 30
million BHCA.
The MSOFTX3000 functioning as the GMSC or TMSC has the ability equivalent to up
to 60 million BHCA.
The MSOFTX3000 functioning as the VMSC in full configuration (two cabinets and
four subracks) supports up to 12 million subscribers.
2.2 New Solution

CS8.0 has new solutions such as embedded VIG, SIP-I based Nc, calling name presentation,
and disaster handling.
2.2.1 Embedded VIG

The video interactive gateway (VIG) is used to implement conversion between the
multiplexing flow and the separate flow for the interworking between the CS domain and the
IMS, NGN, SIP terminal, or other video devices. In a legacy network, the VIG is deployed as

Issue V1.0 (2009-05-15) 2-1
an independent network element, which requires alternative signaling and routes between the
VIG and the MSOFTX3000 and also incurs high maintenance costs. These problems are
solved in CS8.0. The embedded VIG solution is provided to enable the MGW to implement
the VIG functions (the MSC server requires new software, and the MGW requires both new
hardware and software). This solution can simplify the network structure, improve the
network efficiency, and reduce the CAPEX and OPEX. Therefore, the GSM&UMTS carriers
can implement video interworking with the IMS or NGN with only a small amount of
investment and thereby provide abundant multimedia services for subscribers.
2.2.2 SIP-I Based Nc

According to 3GPP specifications, SIP-I based Nc implements SIP-I interworking over the Nc
interface (used between MSC servers) on the basis of the existing Nc-interface functions,
including handover, basic calls between SIP-I and BICC/ISUP/mobile/external SIP network,
precondition, SIP-I multi-country adaptation, data services (such as the fax and VP service),
and DTMF.
2.2.3 Calling Name Presentation

It is an enhancement of the calling line identification presentation (CLIP) service. The calling
name presentation solution provides detailed information about a caller, such as the name,
position, working site, and customized signature, to the callee, instead of only the telephone
number. This enriches the displayed contents for subscribers.
The calling name presentation solution provided by Huawei is not a 3GPP-specific solution
and must be implemented with the cooperation of the service platform XCALL of Huawei
A&S product line.
2.2.4 Non-Interrupting Upgrade

In the versions earlier than CS8.0, non-interrupting upgrade has been achieved for the
MSOFTX3000. For CS8.0, the UMG8900 is optimized on the basis of original design, so that
the UMG8900 can be upgraded without service interruption. Therefore, the stable-state
services are not affected by the upgrade; while the newly accessed services are affected only
within the limit of 10 seconds.
2.2.5 Intelligent Power Consumption Control of the UMG8900

The VPU and ECU boards are powered off when traffic is light and are powered on again
when traffic increases. It is estimated that a maximum of 22% power (about 970 W) can be
saved under the assumption that a 2G all-IP visited MGW (VMGW) serves 500,000
subscribers.
2.2.6 Disaster Handling

The disaster handling solution enables carriers to maximize the handling capability of the
system if a major disaster occurs when the traffic is excessively high. In addition, this solution
allows the system to preferentially ensure the call completion rate of VIP subscribers. That is,
the system can preferentially allocate resources, including wireless resources, terrestrial
transmission resources, and internal resources of NEs, to provide network access and call
services for VIP subscribers.
The solution has multiple features, including the eMLPP, standby resources provisioning in
emergency, service function control in emergency (SCP BYPASS, HLR BYPASS,
authentication/cipher and RBT cancellation, ODB conversation allowed, secondary LAC

2-2 Issue V1.0 (2009-05-15)
paging, and shortening of paging duration), and optimization of roaming number release
(shortening timeout release duration when the idle rate of roaming numbers is low).
2.2.7 Direct Short Message Delivery

The direct short message delivery solution enables the originating MSC server to directly send
a short message to the terminating MSC server upon the receipt of routing information from
the HLR, and then to the terminating MS. If the direct delivery fails, the originating MSC
server transmits the short message to the SMSC, and the SMSC sends the short message to
the terminating MS.
This function provides efficient redundancy for the SMSC without adding any node to the
network. In addition, 25% signaling traffic can be reduced in comparison with the traditional
transmission mode of the SMSC after this function is used throughout the network, especially
in economically undeveloped areas where short messages are very popular. The
implementation of the function is simple. Only the upgrade of the software of the short
message originating MSC is required, and other network nodes need not be changed.
2.2.8 Multi-Operator Core Network

The multi-operator core network (MOCN) solution enables core networks of different carriers
to share one RNC. The typical application scenarios are as follows:
In isolated areas with low subscriber base, a complete 3G access network of each carrier
is not a cost-effective investment option. A shared RNC helps the carriers to reduce their
investment and the maintenance costs.
In some countries, almost all the 3G radio frequency bands are occupied. In this case,
carriers who intend to enter the 3G market cannot be allocated with 3G radio frequency
bands and thus cannot obtain the 3G license. The MOCN solution, however, can solve
this problem.
This MOCN solution is designed in accordance with the 3GPP specification. By using MOCN
solution, the MOSFTX3000 can interwork with any RNC that complies with 3GPP 23.251.
2.2.9 BSC Local Switching

The BSC local switching function enables the BSC to directly handle calls between
subscribers served by the BSC. Thus, voice signals need not be delivered to the MGW. This
helps in saving transmission resources for carriers. If the MSC server and MGW are required
to process voice signals for a certain service (for example, lawful interception, IN
announcement playing and digit collection, call wait, and call hold), the MSC server sends a
message instructing the BSC to deliver the voice to the MGW, thus ensuring that there is no
negative impact on the service.
2.2.10 Voice Quality Enhancement

The voice quality enhancement (VQE) functions are provided by UG-MVQE0. These
functions include noise reduction (NR), noise compensation (NC), automatic gain control
(AGC), and acoustic echo cancellation (AEC). Here, the AEC function cancels the acoustic
echo whereas the other three functions help to improve the voice quality in the IP network.
The CS8.0 and later versions support large-scale delivery of the UG-MVQE0.

Issue V1.0 (2009-05-15) 2-3
2.3 IP
2.3.1 IP-Based A Interface
The implementation of IP-based A interface is important to an all-IP mobile network and an
MSC Pool network. The IP-based A interface function helps to achieve the following goals:
Implementation of End-to-end TrFO for enhancing the voice quality
Saving of transmission resources: The IP network uses the statistical multiplexing
technology. During network access, the bandwidth is allocated according to the
requirements. When a compressed codec is transmitted, the IP-based A interface function
can reduce 50% of bandwidth usage.
Reduced OPEX: When the core network is based on IP, IP transformation of the A
interface and the BSS enables the networks to be unified to a single type. This decreases
the requirements on the technical capability of maintenance personnel and reduces the
operating expenditure.
2.3.2 IP-Based Iu Interface

IP-based Iu interface is designed for IP transmission over the Iu interface according to 23205,
29232, and 25414 of R6 protocols. It supports both the ATP protocol stack and the IP protocol
stack. This feature can help carriers to implement network evolution from ATM to IP and
provide mature IP industry chain for their devices, thus securing the investment.
2.3.3 IP over E1
IP over E1 is a technology that provides transmission channels for IP packets by binding
multiple timeslots or E1 lines. In addition, the cRTP/IVC compression technology is used,
which improves the efficiency of using voice bandwidth at a maximum of 16 times the
efficiency of TDM transmission. IP over E1 can efficiently reduce the operating expenditure
by providing the VoIP service through the existing TDM network, instead of deploying a new
network. In this case, the high reliability of the TDM network can still be ensured.
The MSOFTX3000 supports IP over E1 bearer between gateways but does not provide
interfaces for IP over E1. Instead, the MSOFTX3000 still adopts the FE interface to connect
to a near-end router or multi-service transport platform (MSTP). If IP over E1 is required for
the Mc/SIGTRAN interface, the corresponding equipment that supports conversion between
E1 and FE must be added.
The MSTP scheme must be used together with the SCTP multi-homing scheme.
For the IP over E1 solution, the MSOFTX3000 supports only the BICC protocol on the Nc
interface. It supports three bearer setup modes of the BICC: forward quick setup, forward
delay setup, and backward delay setup. BICC signaling is transferred by a gateway.
2.3.4 RTP Multiplexing

As defined in 3GPP TS 29.414, RTP multiplexing is a multiplexing mechanism used for IP
packet headers. Compared with TDM multiplexing, a maximum of 60% of the bandwidth can
be saved. (The bandwidth saving scale varies with the codec decompression effects.)
The working principle is to multiplex payload of multiple voice packets with the same source
and destination IP addresses to a single IP packet. Thus, the IP packet header can be shared by
the payload of multiple voice packets. In the VoIP service, IP packet headers occupy a large
amount of bandwidth resources, and the payload in voice packets is always small. By using

2-4 Issue V1.0 (2009-05-15)
the shared IP packet header, the number of IP packet headers to be sent is reduced, and thus
bandwidth resources are saved. In addition, the number of packets to be transmitted is reduced
and the load on routes is thus reduced.
2.3.5 SCTP Multi-Homing

The SCTP multi-homing function enables an SCTP association to support multiple pairs of IP
addresses in order to provide multiple paths. Different paths are carried on different bearer
planes. This ensures that backup paths are available and improves transmission reliability. At
present, an SCTP association of the MSOFTX3000 supports two pairs of IP addresses (two
local IP addresses and two peer IP addresses), thus providing two paths. Normally, the data is
sent over the active path. If the active path is inaccessible, the data is switched to the standby
path. After the active path is restored, data is switched back to the active path.
2.3.6 IP CAC
In common cases, bandwidth of the IP bearer network may be reduced due to various causes,
which may lead to the QoS being affected if no mechanism is available to notify the
MSOFTX3000. Therefore, IP CAC is designed so that the MGW can collect end-to-end QoS
data (delay, packet loss, and jittering) based on related information of the RTCP/RTP and
report the data to the MSS in real time. Then, the MSS can control the traffic of the bearer
network through preferential routing and flow control to guarantee the high voice quality of
the network.
2.3.7 BFD
By using periodically transmitted UDP-based fault detection packets, the Bidirectional
Forwarding Detection (BFD) protocol enables the detection of not only physical interruptions
in the transmission links, optical interface, and electrical interface, but also failures at the link
layer and network layer, such as packet loss, error codes, and forwarding errors. Without the
BFD protocol, however, only the failures at the physical layer can be detected. The BFD
mechanism enables detection of failures in 50 milliseconds. This failure detection function is
mandatory for the new generation routers. With other protection measures against failures, the
BFD mechanism lays a solid foundation for a highly reliable IP network. With the deployment
of BFD mechanism, the UMG8900 can complete switchover between the active and the
standby links within 200 ms, without any call drop during this period. Figure 2-1 shows the
BFD networking.
Figure 2-1 BFD networking
For example, if the VRRP is deployed between the MGW and the PE, it takes one second, by
default, for link fault detection. If the enhanced VRRP protocol is applied and the BFD
mechanism is implemented, the detection cycle of link faults (by default, 10 ms) can be
substantially shortened.

Issue V1.0 (2009-05-15) 2-5
2.4 Reliability
In CS8.0, the equipment-level reliability of the ACTA platform is as high as 99.999%. With
robust network-level redundancy solutions of Huawei, for example, MSC Pool and
dual-homing networking, the entire network has the reliability of 99.9999%. This meets the
reliability requirements of carriers.
2.4.1 Equipment-Level Redundancy

The ATCA platform of Huawei MSOFTX3000 is designed in full accordance with the NEBS
L3/ETSI and PICMG 3.0/3.1 standards. It also supports isolation, detection, and rectification
of faults in chips, modules, and the overall system for hardware management. The backup
mechanism is also used for boards. Therefore, the reliability of Huawei ATCA platform
reaches 99.999%.
2.4.2 Network-Level Redundancy

The advanced MSC Pool and dual-homing networking solutions of Huawei can provide
carriers with real-time switchover and data backup functions, without requiring any upgrade
at the access side. This enables the carriers to deploy networks rapidly and conduct O&M
easily while enjoying a high-reliability network.
Dual Homing
The MSC server is located in a high position in the system architecture and normally serves a
large area. A serious accident, such as an improper operation, an equipment fault, or a natural
disaster, leads to interruption of a large volume of services. To ensure the security and
reliability of the mobile network, Huawei provides the remote MSC server redundancy
solution, that is, an MSC server is deployed, dedicated to the backup of the existing MSC
servers. In normal conditions, the active MSC server controls the MGW and processes the
signaling and services. When the active MSC server fails, the standby MSC server takes over
services, thus ensuring the normal operation of the mobile network.
Dual homing is applied on the R4 network (with the call control being separated from the
bearer control), where one MGW is controlled by two MSC servers. In normal conditions, the
MGW is registered only on one MSC server. When this MSC server is faulty, the MGW can
be registered on the other MSC server, so that the MGW can continue to provide services for
subscribers.
At present, the dual-homing networking is recommended for the GMSC and TMSC, in 1+1
assistant mode. Figure 2-2 shows the typical networking.

2-6 Issue V1.0 (2009-05-15)
Figure 2-2 Dual-homing networking
The MSC server supports four dual-homing switch modes: automatic switchover, manual
switchover, automatic switchback, and manual switchback. For automatic switchover and
automatic switchback, heartbeat signaling is required between active and standby MSC
servers to detect faults and ensure timely switchover.
The MSC server supports backup of VLR data. The active MSC server backs up the
subscriber data in the VDB to the VDB of the standby MSC server in real time through
M3UA links. Thus, when the standby MSC server takes over the services of the active MSC
server, the subscriber data backed up in the VDB of the standby MSC server can be directly
used. This protects the A/Iu and C/D interfaces against the impact caused by the automatic
recovery of subscriber data. In addition, the MSC server supports switchback of subscriber
data from the standby MSC server. This, however, must be performed manually.
MSC Pool
An MSC Pool is composed of multiple MSC servers. Each RAN node in the MSC Pool area
is connected to all the MSCs in the pool, and services are evenly distributed among the MSCs.
Through the MSC Pool networking, the following can be achieved:
Multiple CN nodes share the load of the RAN node. This increases the usage of the CN
nodes, reduces the possible loss caused by the CN node failure, and thus improves the
disaster recovery capability of the network.
The service area of a single CN node is expanded. This reduces the number of handovers
among CN nodes and the number of CN node updates for subscriber roaming, and thus
reduces the signaling traffic of the CN.
Carriers share the RAN.
The advantages of Huawei MSC Pool solution are as follows:

Issue V1.0 (2009-05-15) 2-7
The traffic to an MSC Pool can be distributed automatically or manually to ensure load
sharing among the MSCs.
The MGW is responsible for managing A-interface circuits. The service distribution
function is transferred to the MGW, and thus the BSC need not be connected to multiple
MGWs. Therefore, a large number of A-interface transmission resources are saved. In
addition, the BSC need not be upgraded to support MSC Pool, which makes fast
deployment available and reduces costs for carriers.
After the serving MSC is changed because of an MSC failure, the first call terminated by
a subscriber can be connected.
TC is not required during a session between different VMGWs on the same physical
MGW.
The ATCA platform of CS8.0 inherits all the MSC Pool functions of the original CPCI
platform and is further optimized in the following aspects:
Load balancing among MGWs: The MGW divides the IP bearer bandwidth over the
A/Iu interface (IP-based) into multiple virtual circuits and periodically reports the
bandwidth usage of the A/Iu interface to the MSC server. The MSC server evenly
allocates traffic among the MGWs based on the bandwidth usage.
Preferential selection of the local MGW: In the Mini-Iu-Flex or Mini-A-Flex network,
one BSC/RNC is connected to the MGWs of different cities. In a network where both the
MSC Pool networking mode and the Mini-Iu-Flex/Mini-A-Flex networking mode is
applied, the MSC server route the call preferentially to the local MGW, thus achieving
the shortest path transmission.
Dialing test of designated IP/ATM bearer: During deployment or routine maintenance,
maintenance engineers can conduct a dialing test, through the LMT, on the IP address or
ATM address of the designated BSC or RNC or on the IP address of the intra-MSC or
inter-MSC bearer plane.
End-to-end tracing: By invoking the MML of the MSC server on the M2000,
end-to-end tracing of a specified subscriber can be conducted on each NE (MSC or
BSC/RNC), and the tracing result can be sent to the M2000.
2.5 Services
2.5.1 Mobile Number Portability
The mobile number portability (MNP) enables a mobile subscriber to change the subscription
network within a country and to retain the original MSISDN at the same time. All the services
of the mobile subscriber are provided by the new network. The mobile subscriber also enjoys
the same supplementary services and value-added services as other mobile subscribers in the
network. In a network, MNP subscribers enjoy the same services and functions as non-MNP
subscribers.
2.5.2 Lawful Interception

The MSOFTX3000 supports lawful interceptions for both voice calls and video calls. At
present, the following lawful interceptions have been implemented:
SOSM lawful interception
Huawei-proprietary SPBX lawful interception
LICI lawful interception (for China security system only)

2-8 Issue V1.0 (2009-05-15)
ETSI lawful interception

− MSOFTX3000 R005C10 supports the ETSI interception protocol (V1.26)
2.5.3 Call Simulation & Inspection System

The call simulation & inspection system (CSIS) enables maintenance through remote login.
Maintenance engineers can use any telephone (a fixed-line or mobile phone) as a monitoring
phone anywhere to remotely log in to the designated switch through the LMT and conduct
tests on new services or on the switch through the GUI interface in order to identify the faults
based on the test output.
The CSIS provides three functions, namely, specified resource test, specified subscriber test,
and call simulator.
Specified resource test: It is used to test the quality of voice channels and detect
problems, such as long-lasting ringing, abnormally loud noise, timeslot suspension,
one-way audio, and no audio.
Specified subscriber test: It is used to test new services, for example, this test is
conducted after capacity expansion.
Call simulator: When handling subscriber complaints about call connection failures, the
call simulator can be used to make a simulated call to a real subscriber number. By
analyzing the simulated call flow, the cause of call connection failure can be identified.
The call simulator is also helpful in verifying service migration in the absence of the
connected RNC/BSCs.
2.5.4 INAP-M
The INAP-M service enables network interface adaptation. With this service active, the
MSOFTX3000 can convert the ETSI CORE-INAP CS1/CS2-based IN services initiated from
other NEs (MSC, SCP, or HLR) to CAMEL2/3/4-based IN services and thus implements the
interworking between the MSOFTX3000 and the private INAP-based SCPs provided by other
vendors.
2.5.5 CHR
The call history record (CHR) service enables the recording of key information about a call
regardless of whether the call is successful. The key information includes phone numbers and
causes for disconnection. The CHR feature enables the MSOFTX3000 to provide detailed
information of calls and handover procedures in real time. Thus, analysis data can be obtained
for complaint handling, real-time monitoring of the network, analysis of network operation
state, and fault location.
Figure 2-3 shows the networking for implementing the CHR feature.

Issue V1.0 (2009-05-15) 2-9
Figure 2-3 Networking for CHR implementation
Network Management Center Network

management layer
OMC Device
Analysis tool Central server
management
layer
NE layer
Local server MSOFTX3000
The functions of the equipment in the network are as follows:

The MSOFTX3000 generates CHR bills and transmits the CHR bills to the local server.
The information in a CHR bill includes subscriber numbers, office direction (incoming
or outgoing), trunk group, call phase points (such as service request point, call setup
point, and alerting point), and disconnection cause value.
The local server stores data such as CHR bills in files or in the database and provides the
FTP or database interface for external access. The local server also filters and queries the
local data according to the instructions from the NMS or the analysis tool and
preprocesses the data such as collecting KPI statistics.
The central server stores the original or filtered CHR bills transmitted from the local
servers through the FTP interface and provides the CHR data to the analysis tool through
FTP interface for centralized analysis.
The analysis tool (client) provides an FTP interface to the local server and central server.
The analysis tool can analyze the CHRs in the local server and central server, and
provide carriers with reference for the following:
− Customer complaint handling: When receiving customer complaints, the carrier can
query the CHRs to determine whether the problem is caused by a network fault.
− Real-time network monitoring: The network performance and fault information are
dynamically displayed and updated in real time.
− Analysis of network operation state: The analysis tool automatically generates
network analysis results through daily, weekly, and monthly reports.
− In-depth topical analysis: The CHR data helps to identify problems, troubleshoot the
equipment, and determine the causes of the problems.

2-10 Issue V1.0 (2009-05-15)
2.5.6 IWF
The interworking function (IWF) enables the interworking between the PLMN and other
networks (such as PSTN, ISDN, and X.25 network) to implement various CS data services.
Logically, the IWF is composed of transmission equipment and protocol adaptation
equipment. It provides functions such as rate adaptation (RA), radio link protocol, and fax
adaptation (FA). The IWF is applicable when no fixed transmission network is available and
wireless terminals are used to implement CS data and fax services in radio access mode.
The shared interworking function (SIWF) is implemented through the connection between the
IWF entity and the MGW. It supports the asynchronous bearer services (BS20), videophone,
GSM fax services, and IP-based G3 fax services. It also conditionally supports the GSM fax
service carried by two-hop satellite links over the Abis/A interface.
2.6 Evolution
2.6.1 Embedded MGCF
The MSOFTX3000 provides MGCF functions and supports the interworking with the IMS
over SIP. The embedded MGCF function enables the following:
Fax interworking between the CS domain and the IMS domain, with G.711 and
G.711Red codecs adopted
SIP over SCTP, which is a connection-based transmission mode and helps to improve
transmission efficiency
Reserving voice resources in order to improve the call completion rate

Issue V1.0 (2009-05-15) 2-11
3 Architecture
3.1 Hardware Structure

3.1.1 Physical Structure
The MSOFTX3000 adopts Huawei OSTA 2.0 hardware platform. This platform consists of
the cabinet, subrack, and board.
Cabinet Appearance
The MSOFTX3000 uses the N68E-22 cabinets of Huawei. Figure 3-1 shows the appearance
of the N68E-22 cabinet.

Issue V1.0 (2009-05-15) 3-1
Figure 3-1 Appearance of the N68E-22 cabinet
The N68E-22 cabinet is a standard 19" cabinet and 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
2:Cabinets and pitches of rack structures
3:Subracks and associated plug-in units
Cabinet Configuration
In full configuration, the MSOFTX3000 is configured with two cabinets and four subracks.
Figure 3-2 shows the cabinet configuration.

3-2 Issue V1.0 (2009-05-15)
Figure 3-2 Cabinet configuration
Integrated configuration cabinet (46U) Service processing cabinet (46U)
Power distribution box (3U) Power distribution box (3U)
Filler panel (3U)
Filler panel (3U)
Subrack 1 (14U) Filler panel (3U)
Filler panel (3U)
Filler panel (2U)

MRMU (1U)
LAN Switch 1 (1U)
Cabling trough (1U)
LAN Switch 0 (1U)
Cabling trough (1U)
KVMS (1U)
Subrack 3 (14U)
Subrack 1 (14U)
Subrack 2 (14U)
Filler panel (3U)
Filler panel (3U)
Filler panel (3U)

Filler panel (1U)
MRMU: Master Rack Monitoring Unit
In the cabinet, power distribution boxes (PDFs), service processing subracks, and Keyboard &
Video & Mouse & Switcher (KVMS) are installed.
Typical Configuration of the MSOFTX3000

Table 3-1 provides the typical configuration of the MSOFTX3000.

Issue V1.0 (2009-05-15) 3-3
Table 3-1 Typical configuration of the MSOFTX3000

Number of Subscribers Total Number of Service Total Number of
in a Typical Traffic Processing Subracks Cabinets of the
Model (in 10,000) MSOFTX3000
200 1 1
500 2 1
800 3 2
1000 4 2
Expansion Configuration
The capacity of the MSOFTX3000 can be smoothly increased from 0 to 12 million
subscribers by adding modules.
The basic subrack supports 3.3 million subscribers (when the MSOFTX3000 functions as a
VMSC). To expand the capacity, you only need to add subracks or boards and load process
groups according to the requirements. In full configuration, the MSOFTX3000 (4 cabinets)
supports 12 million subscribers.
Subrack
A subrack contains 14 slots each at the front and the rear. Front boards and back boards are
inserted into the slots in pairs.
Figure 3-3 and Figure 3-4 show the front view and rear view of an OSTA 2.0 subrack
respectively.
Figure 3-3 Front view of a subrack
2
3
4
5
6
1. Backplane 2 Front slots 3 Upper fan box

4 Lower fan box 5. Air intake vent 6 Area for the SMM

3-4 Issue V1.0 (2009-05-15)
Figure 3-4 Rear view of a subrack
2
3
4
5
1. Air exhaust vent 2. Backplane 3 Back slots

4 Power entry module (PEM) 5 Area for the SDM
Board
Table 3-2 lists the boards.
Table 3-2 Boards
Physical Board Full Name Location Remarks

UPB Universal Process Front board Each subrack can be
Blade configured with a
maximum of 12
UPBs.
USI Universal Service Back board The USI serves as
Interface Unit the interface board
of the UPB. It is
optional.
SWU Switching Unit Front board Each subrack is
configured with a
maximum of two
SWU boards
working in
load-sharing mode.
SWI Switching Interface Back board The SWI serves as
Unit the interface board
of the SWU.
SMM Shelf Management Front board Each subrack is
Module configured with two
SMM boards
working in
active/standby
mode.

Issue V1.0 (2009-05-15) 3-5
Physical Board Full Name Location Remarks

SDM Subrack Data Module Back board Each subrack is
configured with two
SDM boards
working in
active/standby
mode. The SDM is
installed with the
SMM in pairs.
3.1.2 Logical Structure

The logical structure of the MSOFTX3000 consists of a processor subsystem, a switching
subsystem, an electromechanical subsystem, and an equipment management subsystem.
Figure 3-5 Logical structure of the MSOFTX3000
IPMB: Intelligent Platform Management Bus
In the whole system, the switching subsystem acts as the pivot and the processor subsystem
acts as the core. These subsystems, together with the electromechanical subsystem and
equipment management subsystem, form a powerful service processing platform.
3.2 Software Structure

The MSOFTX3000 adopts the distributed software structure. The software functions are
distributed among the server boards and can be configured flexibly to meet the actual
networking requirements. Based on the position, the software of the MSOFTX3000 is
classified into host software and background software, as shown in Figure 3-6.

3-6 Issue V1.0 (2009-05-15)
Figure 3-6 Software structure of the MSOFTX3000
iGWB: iGateway Bill XPTU: X Protocol Transfer Unit

GUI: Graphical User Interface MML: Human-Machine Language

Issue V1.0 (2009-05-15) 3-7
4 Networking
4.1 VMSC Networking

The MSOFTX3000 supports the H.248, BSSAP, RANAP, MAP, CAP, ISUP, TUP, and
BSSAP+ protocols. It can provide the functions of a VMSC server and a VLR. When
connected to the UMG8900 and SIWF of Huawei, the MSOFTX3000 supports the
BSS/UTRAN access and serves as a 2G visited mobile switching center (VMSC), a 3G
VMSC, or a 2G/3G converged VMSC. Figure 4-1 shows the typical VMSC networking.
Figure 4-1 Typical VMSC networking
UMG8900 UMG8900
PSTN/
H.248 H.248 PLMN
BSSAP ISUP/BICC
BSS BC
GMSC MSOFTX3000
GMSC
(MSC)
RANAP FTP/
FTAM
IP backbone
network/
MML
No.7 signaling
network
UTRAN M2000
BSSAP+ CAP MAP MAP MAP
SGSN SCP GMLC SMC HLR

Access Core
network network
Bearer channel
Signaling channel
BSS: GSM Base station UTRAN: UMTS terrestrial GMSC: Gateway mobile
subsystem radio access network switching center

Issue V1.0 (2009-05-15) 4-1
BC: Billing center HLR: Home location register SMC: Short message
center
GMLC: Gateway mobile SCP: Service control point SGSN: Serving GPRS
location center support node
PSTN: Public switched PLMN: Public land mobile
telephone network network
4.2 GMSC Networking

The MSOFTX3000 supports the H.248, MAP, CAP, ISUP, and TUP protocols and provides
functions such as black and white lists, call authentication, call interception, and storage of a
large number of CDRs. When connected to the Huawei UMG8900, the MSOFTX3000 can
function as a gateway mobile switching center (GMSC) server. Figure 4-2 shows the typical
GMSC networking
Figure 4-2 Typical GMSC networking
UMG8900 UMG8900
PSTN/
H.248 H.248 PLMN
ISUP/BICC
MSOFTX3000
(GMSC)
MSC/VLR
FTP/ BC
FTAM
IP backbone
network/
MML
No.7 signaling
network
M2000
CAP MAP
SCP HLR
Bearer channel
Signaling channel
MSC: Mobile switching center VLR: Visitor location BC: Billing center
register
HLR: Home location register SCP: Service control PSTN: Public switched
point telephone network
PLMN: Public land mobile network

4-2 Issue V1.0 (2009-05-15)
4.3 TMSC Networking

The MSOFTX3000 supports the H.248, ISUP, and BICC protocols. When connected to the
Huawei UMG8900, it provides TDM trunk circuits or IP bearer channels of large capacity. the
MSOFTX3000 can function as the tandem mobile switching center (TMSC) in the
hierarchical network. Figure 4-3 shows the typical TMSC networking.
Figure 4-3 Typical TMSC networking
BC M2000
FTP/FTAM MML
MSOFTX3000(TMSC) MSOFTX3000(TMSC)
ISUP/BICC
TUP/ISUP TUP/ISUP
H.248 H.248
Other MSC UMG8900 UMG8900 Other MSC
Bearer channel
Signaling chanell
4.4 Dual Homing Networking

To ensure the secure and reliable operation of the mobile network, the MSOFTX3000
functioning as the GMSC/TMSC supports remote disaster tolerance. Remote disaster
tolerance is achieved by adding a standby MSC server for the GMSC/TMSC.
In 1+1 assistant networking mode, two MSOFTX3000s work as MSC servers in assistance
mode. Each MSOFTX3000 is active and works as the standby MSC server of the other.
Figure 4-4 shows the 1+1 assistant networking.

Issue V1.0 (2009-05-15) 4-3
Figure 4-4 1+1 assistant networking
MSOFTX3000 A MSOFTX3000 B
Heartbeat link
MGW1 MGW2 MGW3 MGW4
MSC area A MSC area B

Active control
channel
Standby control
channel
4.5 MSC POOL Networking

In the traditional mobile telecommunications network, an RNC/BSC can be connected to only
one MSC. In the MSC Pool networking mode, however, one RNC/BSC can be connected to
multiple MSCs.
Figure 4-5 MSC Pool networking

4-4 Issue V1.0 (2009-05-15)
4.6 Solution for Huawei NGN Interworking with the CS

Domain
Figure 4-6 shows the typical networking of the solution for Huawei next generation network
(NGN) interworking with the circuit switched (CS) domain.
Figure 4-6 Networking of the solution for Huawei NGN interworking with the CS domain
SoftSwitch
SIP-I
GMSCServer
(IWU)
BICC/ISUP
IP bearer
AG/IAD VMSCServer
network
Iu-CS
POTS POTS POTS

UMG8900
UTRAN
NGN UMTS R4
4.7 Evolution Strategy of Huawei Mobile Core Network

The MSOFTX3000 is launched to target the 3GPP R4 CS network, but it is also designed
with capability to maintain compatibility with GSM and 3GPP R99 networks and migrate
smoothly to 3GPP R5 and 3GPP R6 networks. Figure 4-7 shows the staged evolution of
Huawei mobile CN.

Issue V1.0 (2009-05-15) 4-5
Figure 4-7 Evolution strategy of Huawei mobile CN
GSM 3GPP R99 3GPP R4 3GPP R5/R6
MSC Server MSC Server/

MSOFTX 3000 MGCF
MSOFTX 3000
MSC MSC
MSOFTX3000/ MSOFTX3000/ MGW MGW/IM MGW

UMG 8900 UMG 8900 UMG 8900 UMG 8900
Figure 4-8 shows Huawei 3GPP R5 solution.

4-6 Issue V1.0 (2009-05-15)
Figure 4-8 Huawei 3GPP R5 solution
APP Server HLR/HSS SMC SCP
CS IMS
MSS T-MSS SG MSS/MGCF CSCF

PS
IP / TDM
GGSN
G-MSS
MGW MGW
SGSN
PSTN NGN PLMN
BSS RAN

Issue V1.0 (2009-05-15) 4-7
5 Technical Specifications
5.1 Performance Specifications

5.1.1 System Capacity
Table 5-1 System capacity of the MSOFTX3000
Item Specification
Maximum subscribers (VMSC server) 12,000,000 (0.025 Erl/subscriber)
Maximum controllable MGWs 300
Maximum accessible RNCs 256
Maximum accessible BSCs 256
Table 5-2 Reference traffic model of the MSOFTX3000

Item Typical Value
Average traffic of mobile subscribers during 0.025 Erl
busy hours
Average call duration of mobile subscribers 60s
Number of location registrations and 2
updates of a mobile subscriber during busy
hours
Number of handovers of a mobile 0.2
subscriber per call
Number of SMSs of a mobile subscriber 2
during busy hours

Issue V1.0 (2009-05-15) 5-1
5.1.2 System Processing Capability

Table 5-3 System processing capability of the MSOFTX3000
Item Specification
BHCA for VMSC server 30,000,000
BHCA for GMSC server 60,000,000
BHCA for TMSC server 60,000,000
5.1.3 Protocol Processing Capability

Table 5-4 Protocol processing capability of the MSOFTX3000
Item Specification
Supported signaling point code types 14-bit and 24-bit code types
Maximum source signaling points 16 by default (256 at maximum)
Maximum destination signaling points 256 by default (64,000 at maximum)
Maximum IP signaling bandwidth 16 x 1000 Mbit/s
Maximum SCTP links 20,992
Maximum 64-kbit/s MTP links supported by 128
a single BSG process
Maximum 2-Mbit/s MTP links supported by 8
a single BSG process
Maximum SCTP links supported by a single 256
BSG process
Maximum packet dispatch capability of a 129,000 packets/second
single IFM process
Clock stratum Stratum 2
5.1.4 CDR Processing Capability

Table 5-5 CDR processing capability of the MSOFTX3000
Item Specification
Average length of original CDRs 400 bytes
Time precision of CDRs 10 ms
CDR storage capacity of the iGWB 5 x 146 GB

5-2 Issue V1.0 (2009-05-15)
Item Specification
CDR processing capability of the iGWB 7,200 CDR/second
5.1.5 Number Analysis Capability

Table 5-6 Number analysis capability of the MSOFTX3000
Item Specification
Maximum number length of analysis 32 digits
Maximum call prefixes 65,000
Maximum MSRNs/HONs 10,000
Maximum GT codes 60,000
Maximum GT translation capability on a 60 GTT/s
single 64-kbit/s MTP link
5.1.6 Environmental Specifications

Table 5-7 Environmental adaptation of the MSOFTX3000 (long-term operation)
Item Adaptation Specification
Height above sea level ≤ 3,000 m

Atmospheric pressure 70 kPa to 106 kPa
Temperature +5ºC to +40ºC
Relative humidity 5% to 85%
Earthquake-proof capability Able to sustain earthquakes of Richter
scales 7 to 9
Table 5-8 Noise specifications of the MSOFTX3000
Requirement Specification
NEBS ≤ 7.8 bels
ETSI ≤ 7.2 bels

Issue V1.0 (2009-05-15) 5-3
5.1.7 Cabinet Specifications

Table 5-9 Cabinet specifications of the MSOFTX3000
Item Description
Model N68E-22
Dimensions (W/D/H) 2200 mm x 600 mm x 800 mm
Weight (full configuration) 400 kg
Designed weight bearing capacity of the 417 kg/m2
floor in the equipment room
Space available in the cabinet in terms of 46 U (1 U = 44.45 mm)
height
5.1.8 Power Supply Specifications

Table 5-10 Power supply specifications of the MSOFTX3000
Item Specification
Working voltage (standard) Rated voltage –48 VDC
Voltage fluctuations –40 V to –57 V
Working voltage (in Rated voltage –60 VDC
Commonwealth of
Independent States) Voltage fluctuations –51 V to –69 V
Working current ≤ 63 A (single path)
5.1.9 Power Consumption Specifications

Table 5-11 Overall power consumption of the MSOFTX3000
Functional Maximum Power Calculation
Unit Consumption
1 subrack ≤ 2 kW To determine the power consumption in the unit of

BTU, convert the values based on the equation: 1
1 cabinet ≤ 6 kW W = 3.413 BTU.
(full
configuratio
n)

5-4 Issue V1.0 (2009-05-15)
5.2 Clock Specifications

Table 5-12 lists the technical specifications of the clock synchronization system of the
MSOFTX3000.
Table 5-12 Technical specifications of the clock synchronization system of the MSOFTX3000
Serial Item Specification
Number
1 Network access Lowest Stratum-2 clock: ±4 x 10-7

parameter accuracy Stratum-3 clock: ±4.6 x 10-6
Pull-in Stratum-2 clock: able to synchronize
range with the accuracy of ±4 x 10-7
Stratum-3 clock: able to synchronize
with the accuracy of ±4.6x10-6
Maximum Stratum-2 clock: 5x10-10/day
frequency Stratum-3 clock: 2x10-4/day
offset
Initial Stratum-2 clock: <5x10-10/day
maximum Stratum-3 clock: <1x10-8/day
frequency
offset
2 Long-term phase Ideal MRTIE ≤ 1 ms
variation working
status
Hold MRTIE (ns) ≤ a x s + (1/2) x b x s2 +
working c
status Where s indicates time in seconds.
The unit of MRTIE is nanosecond
(ns).
Stratum-2 clock:
a = 0.5, b = 1.16 x 10-5, c = 1000
Stratum-3 clock:
a = 10, b = 2.3 x 10-4, c = 1000
3 Clock working Fast capture, tracing, holdover, and free running
mode
4 Input jitter tolerance See Figure 5-1.

Issue V1.0 (2009-05-15) 5-5
Lowest accuracy is the maximum offset to the nominal frequency in a long term (20 years) if there is
no external reference frequency (free running mode).
Maximum frequency offset is the maximum value of the relative frequency offset in a unit period
during continuous running of the clock.
Pull-in range is the maximum frequency bandwidth of the input clock signals that the clock can lock.
MRTIE refers to the variation of maximum peak-to-peak delay of a tested clock relative to an actual
reference clock during the test.
Figure 5-1 Maximum allowed input jitter and lower threshold of wander
Y (UI)
Peak-to-peak jitter and wander amplitude (logarithm)
2
10
A 0 =36.9
10 1
Slope: 20dB / 10 times of frequency interval
A1=1.5
1
A2=0.2
10 -1
X
1.2 × 10- 5 10 20 2.4 k 18 k 100 k f (Hz)
Assume that the jitter frequency of an input signal is 1 kHz, and the amplitude is greater than
1.5 UI. If the system continues to work normally, it indicates that the input signal meets the
requirements.
UI is the unit interval. The reciprocal of the frequency of the digital signal is one UI. For example, the
UI of 2.048-Mbit/s signal is 488 ns.
5.3 EMC Specifications

The MSOFTX3000 complies with the following EMC specifications:
ETSI EN 300 386V1.3.3: 2005
AS/NZS CISPR 22: 2004
CISPR 22: 2002 CLASSA
EN 55022: 1998 + A1: 2000+A2: 2003 CLASSA
EN 55024:1998 + A1:2001 + A2:2003
FCC part 15:2006
VCCI V-3: 2006
CISPR 24: 1997

5-6 Issue V1.0 (2009-05-15)
5.4 Environmental Requirements

5.4.1 Storage Environment
Climatic Requirements
Figure 5-2 Climatic requirements for storing the MSOFTX3000
Item Range
Temperature –40ºC to +70ºC
Temperature variance rate ≤ 1ºC/min
Solar radiation ≤ 1120 W/s2
Heat radiation ≤ 600 W/s2
Wind speed ≤ 30 m/s
Biological Requirements
The requirements relating to the biological environment for storing the MSOFTX3000 are as
follows:
Ensure that the equipment room is protected against epiphyte, mildew and other
microorganisms.
There are no rodents, such as mice, in the equipment room.
Air Cleanness Requirements

The requirements on the air cleanness for storing the MSOFTX3000 system are as follows:
Ensure that the air is free of explosive, conductive, magnetic conductive or corrosive
dust.
The density of mechanically active substances complies with the requirements listed in
Table 5-13.
Table 5-13 Density requirements of mechanically active substances for storing the MSOFTX3000
Mechanically Active Unit Density
Substance
Suspended dust mg/m3 ≤ 5.00
Deposited dust mg/m2·h ≤ 20.0

Issue V1.0 (2009-05-15) 5-7

Substance
Sand mg/m3 ≤ 300
NOTE
Suspended dust: diameter ≤ 75 µm
Deposited dust: 75 µm ≤ diameter ≤ 150 µm

Sand: 150 µm ≤ diameter ≤ 1000 µm
The density of chemically active substances complies with the requirements listed in
Table 5-14.
Table 5-14 Density requirements of chemically active substances for storing the MSOFTX3000
Chemically Active Unit Density
Substance
SO2 mg/m3 0.30 to 1.00
H 2S mg/m3 0.10 to 0.50
NO2 mg/m3 0.50 to 1.00
NH3 mg/m3 1.00 to 3.00
Cl2 mg/m3 0.10 to 0.30
HCl mg/m3 0.10 to 0.50
HF mg/m3 0.01 to 0.03
3
O3 mg/m 0.05 to 0.10
Waterproofing Requirements
Table 5-15 Waterproofing requirements for storing the MSOFTX3000
Item Requirements
Placing the There is no water on the ground on which the equipment is placed and
equipment in there is no probability of water leaking into the package.
the The equipment is placed away from fire-extinguishing devices and heating
equipment pipes.
room
(recommende
d)

5-8 Issue V1.0 (2009-05-15)
Item Requirements
Placing the The package is stored properly.
equipment The package is covered, and adequate measures are taken to eliminate the
outside the probability of water leaking into the package.
equipment
room The package is not exposed to sunlight.
There is no water on the ground where the package is placed and no water
leaks into the package.
5.4.2 Transportation Environment

Table 5-16 Climatic requirements for transporting the MSOFTX3000
Item Range

Temperature –40ºC to +70ºC
Temperature variance rate ≤ 3ºC/min
Rain ≤ 6 mm/min
The requirements relating to the biological environment for transporting the MSOFTX3000
are as follows:
Ensure that the transportation vehicle is protected against epiphyte, mildew and other
microorganisms.
There are no rodents, such as mice, in the transportation vehicle.

The requirements on the air cleanness for transporting the MSOFTX3000 are as follows:
dust.

Issue V1.0 (2009-05-15) 5-9
Table 5-17.
Table 5-17 Density requirements of mechanically active substances for transporting the
MSOFTX3000
Substances
Suspended dust mg/m3 No requirements
Sand mg/m3 ≤ 100
NOTE

Table 5-18.
Table 5-18 Density requirements of chemically active substances for transporting the
MSOFTX3000
Chemically Active Unit Density
Substance
SO2 mg/m3 ≤ 1.00
H 2S mg/m3 ≤ 0.50
NO2 mg/m3 ≤ 1.00
NH3 mg/m3 ≤ 3.00
Cl2 mg/m3 ≤ 0.30
HCl mg/m3 ≤ 0.05
HF mg/m3 ≤ 0.03
O3 mg/m3 ≤ 0.10
Mechanical Stress Requirements
Table 5-19 Mechanical stress requirements of equipment transportation for transporting the
MSOFTX3000
Item Sub-item Range

Sinusoidal Offset ≤ 7.5mm - -

5-10 Issue V1.0 (2009-05-15)
Item Sub-item Range

oscillation Accelerated - ≤ 20.0m/s2 ≤ 40.0m/s2
speed
Frequency band 2 Hz to 9 Hz 9 Hzto 200 Hz 200 Hz to 500
Hz
Random Acceleration 10 m2/s3³ 3 m2/s3 1 m2/s3
vibration spectrum
density
Frequency band 2 Hz to 9 Hz 9 Hz to 200 Hz 200 Hz to 500
Hz
Non-stable Impulse ≤ 300 m/s2
impulse response
spectrum II
Payload ≤ 10 kPa
NOTE
Impulse response spectrum: It refers to the maximum acceleration response curve generated by the
equipment under the specified impulse excitation. Impulse response spectrum II means that the
duration of half-sine impulse response spectrum is 6 ms.
Payload: It refers to the load that a packed device can bear in specified piling mode.
Waterproofing Requirements
The waterproofing requirements for transporting the MSOFTX3000 are as follows:
The package is stored properly.
The transportation vehicle is covered, and adequate measures are taken to eliminate the
probability of water leaking into the package.
There is no water inside the transportation vehicles.
5.4.3 Operation Environment

Table 5-20 Temperature and humidity requirements for the operation of the MSOFTX3000
Device Name Temperature Relative Humidity
Long-term Short-term Long-term Short-term

Operation Operation Operation Operation
MSOFTX3000 +5ºC to +40ºC –5ºC to +50ºC 5% to 85% 5% to 95%

Issue V1.0 (2009-05-15) 5-11
Device Name Temperature Relative Humidity
Long-term Short-term Long-term Short-term

Operation Operation Operation Operation
NOTE
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 continuous working duration is not more than 96 hours and the continuous
working duration in a year is not more than 15 days.
Table 5-21 Other climatic environmental requirements for the operation of the MSOFTX3000
Item Range
Height above sea level ≤ 3000 m
Temperature variance rate ≤ 5ºC/h
IP level IP50
The requirements relating to the biological environment for the operation of the
MSOFTX3000 are as follows:
Ensure that the equipment room is protected against epiphyte, mildew and other
microorganisms.
There are no rodents, such as mice, in the equipment room.

The requirements on the air cleanness for the operation of the MSOFTX3000 system are as
follows:
dust.
Table 5-22.

5-12 Issue V1.0 (2009-05-15)
Table 5-22 Density requirements of mechanically active substances for the operation of the
MSOFTX3000
Substance
Dust particle Particle/m3 ≤ 3 x 105
Suspended dust mg/m3 ≤ 0.2
Sand mg/m3 ≤ 30
NOTE
Dust particle: diameter ≥ 5 µm

Table 5-23.
Table 5-23 Density requirements of chemically active substances for the operation of the
MSOFTX3000
Chemically Active Substance Unit Density

SO2 mg/m3 0.30 to 1.00
H 2S mg/m3 0.10 to 10.50
NO2 mg/m3 0.50 to 11.00
NH3 mg/m3 1.00 to 13.00
Cl2 mg/m3 0.10 to 10.30
HCl mg/m3 0.10 to 10.50
HF mg/m3 0.01 to 10.03
O3 mg/m3 0.05 to 10.10
CO mg/m3 ≤ 5.0
Mechanical Stress Requirements
Table 5-24 Mechanical stress requirements for the operation of the MSOFTX3000
Item Sub-item Range

Sinusoidal oscillation Offset ≤ 5.0 mm -

Issue V1.0 (2009-05-15) 5-13
Item Sub-item Range

Accelerated speed - ≤ 2.0 m/s2
Frequency band 5 Hz to 62 Hz 62 Hz to 200 Hz
Non-stable impulse Impulse response ≤ 50 m/s2
spectrum II
Payload 0
NOTE
Impulse response spectrum: It refers to the maximum acceleration response curve generated by the
equipment under the specified impulse excitation. Impulse response spectrum II means that the
duration of half-sine impulse response spectrum is 6 ms.
Payload: It refers to the load that a packed device can bear in specified piling mode.

5-14 Issue V1.0 (2009-05-15)
6 Acronyms and Abbreviations
Numeric
3GPP 3rd Generation Partnership Project
A
AIM Application Interface Module
AIP Advanced Intelligent Peripheral
ALU Alarm Unit
ANSI American National Standard Institute
AoC Advice of Charge
AoCC Advice of Charge (Charging)
AoCI Advice of Charge (Information)
API Application Program Interface
APM Application transport Mechanism
AS Application Server
ASCII American Standard Code for Information Interchange
ASIC Application Specific Integrated Circuit
ASN.1 Abstract Syntax Notation One
ATM Asynchronous Transfer Mode
B
BAM Back Administration Module
BC Bearer Control
BGCF Breakout Gateway Control Function
BHCA Busy Hour Call Attempt

Issue V1.0 (2009-05-15) 6-1
BICC Bearer Independent Call Control Protocol

BIOS Basic Input/Output System
B-ISDN Broadband Integrated Services Digital Networks
BITS Building Integrated Timing Supply System
BNC Backbone Network Connection
BOIC Barring of Outgoing International Calls
BOIC-exHC Barring of Outgoing International Calls except those directed to
the Home PLMN Country
BS Bearer Service
BSC Base Station Controller
BSS Base Station Subsystem
BSSAP Base Station Subsystem Application Part
BSSAP+ Base Station Subsystem Application Part+
BSSMAP Base Station Subsystem Management Application Part
C
CAC Connection Admission Control
CAMEL Customized Applications for Mobile network Enhanced Logic
CAP CAMEL Application Part; Amplitude Phase modulation
CAPEX CapEx
CC Country Code
CDR Call Detail Record
CGI Cell Global Identification
CHR Call History Record
CI Cell Identity
CIC Circuit Identification Code
CIC Call Instance Code
CN Core Network
CPU Center Processing Unit
CRBT Color Ring Back Tone
CRC Cyclic Redundancy Check
CS Circuit Switched

6-2 Issue V1.0 (2009-05-15)
D
DB Data Base
DNS Domain Name Server
E
EC Echo Cancellation
ECT Explicit Call Transfer
EFR Enhanced full rate speech codec
EMC Electro Magnetic Compatibility
EMI Electro Magnetic Interference
eMLPP Multi-Level Precedence and Pre-emption service
ETS European Telecommunication Standards
ETSI European Telecommunications Standards Institute
F
FCC Federal Communications Commission
FE Fast Ethernet
FLASH FLASH memory
FR Full Rate
FTAM File Transfer Access and Management Protocol
FTP File Transfer Protocol
G
GCI Global Cell Identity
GE Gigabit Ethernet
GGSN Gateway GPRS Support Node
GMLC Gateway Mobile Location Center
GMSC Gateway Mobile Switching Center
GPRS General Packet Radio Service
GPS Global Position System
GSM Global System for Mobile Communications
gsmSCF gsm Service Control Function
GT Global Title

Issue V1.0 (2009-05-15) 6-3
GUI Graphic User Interface

GW GateWay
H
H.248 H.248/MECAMGO protocol
HF High Frequency
HLR Home Location Register
HOLD Call Hold
HTTP Hyper Text Transport Protocol
I
ICMP Internet Control Message Protocol
ID IDentification/IDentity
IEC International Electrotechnical Commission
IEEE Institute of Electrical and Electronics Engineers
IETF Internet Engineering Task Force
IFM IP Forwarding Module
iGWB iGateway Bill
IMEI International Mobile Equipment Identity
IMS IP Multimedia Subsystem
IMSI International Mobile Station Identity
IP Internet Protocol
IP Intelligent Peripherals
ISDN Integrated Services Digital Network
ISO International Standard Organization
ISUP ISDN User Part
ITU International Telecommunications Union
ITU-T International Telecommunication Union - Telecommunication
Standardization Sector
IUA ISDN Q.921-User Adaptation Layer
Iu-Flex Intra-domain connection of RAN nodes to multiple CN nodes

6-4 Issue V1.0 (2009-05-15)
KVM Keyboard & Video & Mouse

KVMS Keyboard & Video & Mouse & Switcher
L
LAC Location Area Code
LAI Location Area Identity
LAN Local Area Network
LCD Liquid Crystal Display
M
M2UA SS7 MTP2-User Adaptation Layer
M3UA SS7 MTP3-User Adaptation Layer
MAC Media Access Control
MAP Mobile Application Part
Mc Media Control
MGC Media Gateway Controller
MGW Media Gateway
MM Mobility Management
MML Man Machine Language
MS Mobile Station
MSC Mobile Service Switching Center
MSC Server Mobile Switching Center Server
MSISDN Mobile Station International ISDN Number
MSRN Mobile Station Roaming Number
MTP Message Transfer Part
MTP2 Message Transfer Part Level 2
MTP3 Message Transfer Part Level 3
MTP3B Message transfer part (broadband)
MVNO Mobile Virtual Network Operator
MVPN Mobile Virtual Private Network
N
NAT Network Address Translation

Issue V1.0 (2009-05-15) 6-5
NDC National Destination Code

NGN Next Generation Network
NI Network Indication
NIC Network Interface Card
NSS Network SubSystem
NTP Network Time Protocol
O
O&M Operation and Maintenance
OPC Originating Point Code
OPEX OPerating EXpenditure
OSI Open System(s) Interconnection
OSTA Open Standards Telecom Architecture
P
PLMN Public Land Mobile Network
PS Packet Switched
PSTN Public Switched Telephone Network
Q
QoS Quality of Service
R
RAN Radio Access Network
RANAP Radio Access Network Application Part
RBT Ring Back Tone
RN Roaming Number
RNC Radio Network Controller
S
SCCP Signaling Connection Control Part
SCP Service Control Point
S-CSCF Serving CSCF

6-6 Issue V1.0 (2009-05-15)
SCTP Stream Control Transmission Protocol

SG Signaling Gateway
SGSN Serving GPRS Support Node
SIGTRAN Signaling Transport
SIM Subscriber Identity Module
SIP Session Initiation Protocol
SSP Service Switching Point
STP Signaling Transfer Point
T
TCP Transport Control Protocol
T-CSI Terminated-CAMEL Subscription Information
TDM Time Division Multiple
TMSC Tandem Mobile Switching Center
TMSI Temporary Mobile Subscriber Identity
TrFO Transcoder Free Operation
TS Technical Specification
TUP Telephone User Part
U
UDP User Data gram Protocol
UE User Equipment
UMG Universal Media Gateway
UMTS Universal Mobile Telecommunications System
UTRAN UMTS Terrestrial Radio Access Network
V
VDB VLR Database
VLAN Virtual Local Area Network
VLR Visitor Location Register
VMGW Virtual Media Gateway
VMSC Visited Mobile Switching Center
VoIP Voice over IP

Issue V1.0 (2009-05-15) 6-7
VPN Virtual Private Network
W
WAN Wide Area Network
WCDMA Wideband Code Division Multiple Access
WIN Wireless Intelligent Network
X
XPTU X Protocol Transfer Unit

6-8 Issue V1.0 (2009-05-15)

Manual Msoftx3000

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual Msoftx3000

Uploaded by

Copyright:

Available Formats

BOM Code

MSOFTX3000 V200R008 Mobile SoftSwtich Center

HUAWEI TECHNOLOGIES CO., LTD.

Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

5 Technical Specifications ...........................................................................................................5-1

6 Acronyms and Abbreviations..................................................................................................6-1

Figure 1-1 Huawei mobile softswitch solution...................................................................................................1-2

Figure 2-2 Dual-homing networking..................................................................................................................2-7

Figure 3-1 Appearance of the N68E-22 cabinet .................................................................................................3-2

Figure 3-2 Cabinet configuration .......................................................................................................................3-3

Figure 3-3 Front view of a subrack ....................................................................................................................3-4

Figure 3-4 Rear view of a subrack......................................................................................................................3-5

Figure 3-5 Logical structure of the MSOFTX3000............................................................................................3-6

Figure 3-6 Software structure of the MSOFTX3000..........................................................................................3-7

Figure 4-1 Typical VMSC networking ...............................................................................................................4-1

Figure 4-2 Typical GMSC networking ...............................................................................................................4-2

Figure 4-3 Typical TMSC networking................................................................................................................4-3

Figure 4-4 1+1 assistant networking ..................................................................................................................4-4

Figure 4-5 MSC Pool networking ......................................................................................................................4-4

Figure 4-7 Evolution strategy of Huawei mobile CN.........................................................................................4-6

Figure 4-8 Huawei 3GPP R5 solution ................................................................................................................4-7

Figure 5-2 Climatic requirements for storing the MSOFTX3000 ......................................................................5-7

Huawei Proprietary and Confidential

Table 1-1 Customer value of the MSOFTX3000................................................................................................1-4

Table 3-2 Boards.................................................................................................................................................3-5

Table 5-2 Reference traffic model of the MSOFTX3000 ...................................................................................5-1

Table 5-3 System processing capability of the MSOFTX3000 ..........................................................................5-2

Table 5-4 Protocol processing capability of the MSOFTX3000.........................................................................5-2

Table 5-5 CDR processing capability of the MSOFTX3000 ..............................................................................5-2

Table 5-6 Number analysis capability of the MSOFTX3000 .............................................................................5-3

Table 5-7 Environmental adaptation of the MSOFTX3000 (long-term operation) ............................................5-3

Table 5-8 Noise specifications of the MSOFTX3000.........................................................................................5-3

Table 5-9 Cabinet specifications of the MSOFTX3000......................................................................................5-4

Table 5-10 Power supply specifications of the MSOFTX3000 ..........................................................................5-4

Table 5-11 Overall power consumption of the MSOFTX3000...........................................................................5-4

Table 5-15 Waterproofing requirements for storing the MSOFTX3000.............................................................5-8

Huawei Proprietary and Confidential

1.1 Product Orientation

Huawei Proprietary and Confidential

Figure 1-1 Huawei mobile softswitch solution

Support for 2G/3G Convergence

Huawei Proprietary and Confidential

1.1.2 Introduction to the MSOFTX3000

Huawei Proprietary and Confidential

1.1.3 Customer Value of the MSOFTX3000

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

2.1 Advanced OSTA2.0 Platform

2.2 New Solution

2.2.1 Embedded VIG

Huawei Proprietary and Confidential

2.2.2 SIP-I Based Nc

2.2.3 Calling Name Presentation

2.2.4 Non-Interrupting Upgrade

2.2.5 Intelligent Power Consumption Control of the UMG8900

2.2.6 Disaster Handling

Huawei Proprietary and Confidential

2.2.7 Direct Short Message Delivery

2.2.8 Multi-Operator Core Network

2.2.9 BSC Local Switching

2.2.10 Voice Quality Enhancement