Professional Documents
Culture Documents
Product Description PDF
Product Description PDF
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
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
10 Installation...............................................................................................................................10-1
Figures
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 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
1 Introduction
Title Description
1.1 Product Orientation This section describes the mobile softswitch solution of
Huawei and the orientation of the MSOFTX3000.
1.2 Product Features This section describes features of the MSOFTX3000.
BSS
2G Access
PSTN
3G Access
MGW MGW
(UMG8900) (UMG8900)
CS
PS
HLR
Internet
UTRAN
SGSN GGSN
GGSN: Gateway GPRS Support Node HLR: Home Location Register MGW: Media Gateway
MSC Server: Mobile Switching Center CN: Core Network CS: Circuit Switched domain
Server
SGSN: Serving GPRS Support Node PS: Packet Switched domain PSTN: Public Switched
Telephone Network
UTRAN: UMTS Terrestrial Radio BSS: Base Station Subsystem
Access Network
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.
MSC It connects with the BSS or the UTRAN and The MSOFTX3000 provided
server performs such control functions of the CS by Huawei serves as an MSC
domain as: server, as shown in Figure
! Mobility management 1-1.
! Security management
! Handover processing
! Signaling processing
! Call processing
! Subscriber data management (function of
the VLR)
MGW It is the endpoint of the MSOFTX3000's The UMG8900 provided by
connection with the PSTN or the PLMN, and Huawei serves as an MGW,
performs such functions as: 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
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), softswitch networks offer
the carriers the benefits listed in Table 1-2:
Benefit Description
Benefit Description
New services can be New services can be provided on the softswitch layer without
offered quickly and affecting MGW in the bearer layer. Hence, the softswitch network
easily. 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
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.
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. With
the GMSC server, a mobile network can exchange signaling with the following:
! 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:
! 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:
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.
Table 1-5 Protocols, links, and signaling modes supported and interfaces provided by the
MSOFTX3000 to interwork with other NEs
MSC GMSC
MSOFTX3000 MSOFTX3000
A
BSS TUP/ISUP
BICC TUP/ISUP PSTN/
PLMN
Iu-CS
UMG8900 UMG8900
UTRAN
In the 2G/3G integration networking structure, the MSOFTX3000 and the UMG8900 can be
used as an MSC (GMSC or TMSC) function entity:
! 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.
2 System Structure
Title Description
2.1 Hardware Structure This section describes the physical and logical structures
of the MSOFTX3000 hardware.
2.2 Software Structure This section describes the logical structure of the
MSOFTX3000 software.
2.3 Capacity Expansion This section describes the normal and expanded
configuration of the MSOFTX3000 cabinets.
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
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.
(4)
(5)
(6)
(1) Power boards (2) Interface boards (3) Ethernet communication boards
(4) Back boards (5) Backplane (6) Front boards
(7) Service boards (8) System management boards (9) Alarm board
! Alarm boards
! Power boards (each occupies two standard slots)
The remaining 12 slots are used for service boards and interface boards.
FE FE To Billing Center
0# Subrack
FE Active iGWB
To Billing Center
1# LAN Switch
BAM
2# Subrack Background
LAN Switch
To NMC
EWS
9# Subrack
LMT LMT LMT
Host
FE: Fast Ethernet 2 x FE: Two FE cables LMT: Local Maintenance Terminal
EWS: Emergency Workstation
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.
WBFI/ WCDB
FE WBSG
Interface WIFM
WMGC
LAN bus
OSTAbus
NMS
BAM
WS WSIU/WSMU
BC iGWB
Operation & System Support Module
Maintenance Module
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.
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.
Performance Performance
Service processing
Database Bill Bill
Alarm Alarm GUI
Protocol processing
Maintenance Maintenance MML
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.
! 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.
Figure 2-6 Relationship between BAM server software, operating system, and database
Applicaiton
program layer
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
0 - 200 k
200 k - 1 M
1 M - 1.8 M
thousand subscribers. With all nine expansion subracks, the MSOFTX3000 supports up
to 1.8 million subscribers.
Title Description
Item Value
Specifications of E1 Interfaces
Table 3-3 lists specifications of E1 interfaces:
Compliant ITU-T I.431, G.703, G.736, G.823, G.704, G.706, Q.703, G.732
recommendation or
standard ANSI T1.403
Compliant
recommendation ITU-T G.703 ITU-T G.703
or standard
Interface type SMB SMB
Signal type G.703.10 G.703.6
Detection
≤-24dB ≤-24dB
threshold
Impedance
75 ohm 75 ohm
matching
Balance mode Unbalanced Unbalanced
Electrical isolation 300 V / 50 Hz, > 1 minute 300 V / 50 Hz, > 1 minute
SMC
MML
C/D CAP/ L E Service
M2000 Layer
PSTN TUP/ISUP Nc / E
PLMN
MSOFTX 3000 MSC Server Control
Layer
SIGTRAN A
Mc
lu-CS
SG Gs BSC
RNC
SGSN
Access
MGW Layer
BSC: Base Station Controller GMLC: Gateway Mobile Location HLR: Home Location Register
Center
BC: Billing Center SCP: Service Control Point SMC: Short Message Center
SG: Signaling Gateway SGSN: Serving GPRS Support Node RNC: Radio Network Controller
MGW: Media Gateway PLMN: Public Land Mobile Network
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 Interface Protocol
FTP/FTAM
BGCF
Mg
MML
CSCF
M2000
Rf
PSTN/ BICC/ISUP
PLMN
MSOFTX3000 CCF
Mb
SIGTRAN
Mn
MRFP
SGW
Mb
IM-MGW GGSN
GGSN: Gateway GPRS Support Node MGCF: Media Gateway Control IM-MGW: IP Multimedia Media
Function Gateway
BGCF: Breakout Gateway Control SGW: Signaling Gateway CS domain: Circuit Switched
Function domain
CSCF: Call Session Control Function MRFP: Multimedia Resource IMS: IP Multimedia Subsystem
Function Processor
PLMN: Public Land Mobile Network CCF: Charging Collection
Function
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 Interface Protocol
MGCF—IM-MGW Mn H.248
MGCF—PSTN - BICC/ISUP
MGCF—PLMN
MGCF—BGCF Mj SIP
MGCF—CSCF Mg SIP
MGCF—NMS - MML
MGCF—BC - FTP/FTAM
MGCF—CCF Rf Diameter
4 O&M System
Title Description
4.1 Overview of O&M This section describes the structure of the MSOFTX3000
terminal system.
4.2 O&M Function This section describes the O&M functions supported by
the MSOFTX3000.
MSOFTX3000 host
LAN Switch
To BC
WAN
Active Standby
BAM
iGWB iGWB
To NMC
HUB WAN
iManager
M2000
! 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.
! 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)
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
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
! 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
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.
Title Description
5.1 Basic Services The service functions consist of circuit switched domain
services, such as the following:
! Teleservices
! Supplementary services
! IN services
! Value added services
5.2 Basic Functions The mobile network functions consist of thefollowing:
! Mobility management
! Security management
! Call control
! Location services
! Service switching function
5.3 Description of New This section introduces new features and functions except
Features the basic services and the functions.
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:
! 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.
! 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.
Multiparty Service
The mobile subscriber who registers this service can organize multiparty telephone
conference, providing the conversation among multiparty (this mobile subscriber included).
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.
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.
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.
! 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.
! 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.
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.
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.
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.
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.
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
! 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
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:
Mobile originated call If a non-IN mobile subscriber originates a call, and the call is
(MOC) record 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.
Mobile terminated call If a non-IN mobile subscriber receives a call, when the call ends
(MTC) record 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.
Mobile originated call During a call connection, assume that:
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.
Transit call attempt 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
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.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.
SS7 signaling
network
SSP SSP
SS7 signaling
network
GMSC/ GMSC/
SSP 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.
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.
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.
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.
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.
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.
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.
! 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.
MSOFTX3000
MGW 1 MGW 3
MGW 2
BSC 1 BSC 3
BSC 2
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:
MSOFTX3000
MGW 1 MGW 3
MGW 2
RNC 1 RNC 3
RNC 2
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:
CS pool-
CS pool-
area 2
area 1
PS pool-area 1 PS pool-area 2
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.
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:
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:
PLMN A
Transcoding Transcoding
PLMN B
Function Function
MS/UE MS/UE
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
Transcoding Transcoding
PLMN B
Function Function
MS/UE MS/UE
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:
Figure 5-8 Encoding and decoding speech operation after activating TrFO
Transcoding Functions
Bypassed
PLMN A
Transcoding Transcoding
PLMN B
Function Function
MS/UE
MS/UE
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
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.
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.
Title Description
6.1 Typical Networking This section describes the typical networking solutions of
the MSOFTX3000.
6.2 Network Application This section describes the typical network application
Cases cases of the MSOFTX3000.
UMG8900 UMG8900
H.248 H.248
PSTN/
PLMN
BSSAP ISUP/BICC TUP/ISUP
BSS MSOFTX3000
GMSC
(MSC)
FTP/
FTAM
IP backbone network/ BC
RANAP
No.7 signaling network MML
UTRAN M2000
BSSAP+ CAP MAP MAP MAP
Bearer
SGSN SCP GMLC SMC HLR channel
Signaling
Access network Core network channel
BSS: GSM Base station subsystem UTRAN: UMTS terrestrial radio access GMSC: Gateway mobile switching
network center
BC: Billing center HLR: Home location register SMC: Short message center
GMLC: Gateway mobile location center SCP: Service control point SGSN: Serving GPRS support node
PSTN: Public switched telephone network PLMN: Public land mobile network
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
! 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.
UMG8900 UMG8900
H.248 H.248
PSTN/
PLMN
ISUP/BICC TUP/ISUP
MSC/VLR MSOFTX3000
(GMSC)
FTP/
FTAM
IP backbone network/ BC
No.7 signaling network MML
M2000
CAP MAP
Bearer
channel
SCP HLR
Signaling
channel
MSC: Mobile switching center VLR: Visitor location register BC: Billing center
HLR: Home location register SCP: Service control point PSTN: Public switched
telephone network
PLMN: Public land mobile 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.
! 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.
MSOFTX3000 MSOFTX3000
(TMSC) (TMSC)
ISUP/BICC
H.248 H.248
TUP/ISUP TUP/ISUP
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.
Heartbeat link
MSOFTX3000 A MSOFTX3000 B
Active
control channel
Standby
control channel
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.
Heartbeat link
MSOFTX3000 A MSOFTX3000 B
Active
control channel
Standby
control channel
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.
Active
control channel
Standby
control channel
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.
Active
control channel
Standby
control channel
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.
BSC BSC
MGW1 MGW2
RNC RNC
PSTN PSTN
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.
Figure 6-9 Networking structure for Huawei IMS interworking with the CS domain
Mj
MSC Server / MGCF BGCF
MSC Server (MSOFTX3000)
A
Nc Mg
BSS I-CSCF
Mc Mn
Iu
Nb Mb
GGSN
UTRAN MGW MGW / IM-MGW Mb
CS domain
MRFP
Bearer channel
Signaling channel IMS domain
GGSN: Gateway GPRS support node MGCF: Media gateway control IM-MGW: IMS-Media gateway
function function
CSCF: Call session control function SGW: Signaling gateway CS: Circuit switched domain
BGCF: Breakout gateway control MRFP: Multimedia resource function CCF: Offline charging gateway in IMS
function processor 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.
Figure 6-10 Networking structure for Huawei NGN interworking with the CS domain
IMS Core
I-CSCF
BGCF
Audio
IMS-UE Video
MGW
IM-MGW
Audio
Video
Signaling channel
Bearer channel Terminal
MSC
MSOFTX 3000/ UMG 8900 MSC
MSOFTX 3000/ UMG 8900
MGW/IM MGW
MGW UMG 8900
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.
CS MSS/MGCF IMS
CSCF
T-MSS SG
MSS
IP / ATM / TDM
PS
GGSN
BSS RAN
PSTN NGN PLMN
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.
MSOFTX3000
Bearer channel
Signaling channel Central office of the
provincial capital
TMSC1 TMSC2
GMSC1 GMSC2
MGW1 MGW3
BSS11 MGW2
BSS3
BSS12
Local network
Local network in city F
in city C
BSS2
Local network
in city J
and takes over the MGWs and services controlled by the faulty MSOFTX3000. Then,
the MGWs send registration requests to the activated MSOFTX3000.
Title Description
7.1 Reliability Design This section describes the reliability design of the
MSOFTX3000 system.
7.2 Security Design This section describes the security design of the
MSOFTX3000 product.
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
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.
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.
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.
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.
! CDR error tolerance
− 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.
! Transmission reliability
The iGWB Server transmits CDRs to the billing center through FTP or FTAM. Both
retransmission and broken retransmission are supported.
! 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 operator’s 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.
Item Standard
EMC EN 55022
FCC part 15
VCCI
AS/NZS 3548
GR-1089
Safety EN/IEC 60950
UL60950
IEC60950
GR-1089
Title Description
Parameter Specification
Parameter Specification
Item Specification
Supported signaling point coding types 14-bit and 24-bit coding types
Maximum source signaling points 16 by default (256 at maximum)
Maximum destination signaling points 256 by default (64000 at maximum)
Maximum IP signaling bandwidth 4 × 100 Mbit/s
Maximum 64-kbit/s MTP links 1728
Maximum 2-Mbit/s MTP links 108
Maximum SCTP links 2304
Maximum 64-kbit/s MTP links on a single WCSU 32
board
Maximum 2-Mbit/s MTP links on a single WCSU 2
board
Maximum SCTP links on a single WBSG board 128
Maximum TCP/UDP links on a single WBSG 1500
board
Maximum dispatched packets on a single WIFM 15,000 packets/second
board
Clock stratum Stratum-2 A
Item Specification
Parameter Specification
Parameter Specification
Item Specification/Model
Item Specification
The specifications listed in Table 8-11 are for reference only. They can be changed as needed.
The CE tests are designed to show the interference signals of the product that are conducted through the
cable port.
30 to 230 40
230 to 1000 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.
The CS tests are designed to show the endurance of the product on the external interference through
cable port coupling.
The RS tests are designed to show the endurance of the product on the external interference through
shell port coupling.
Air discharge 8 kV B
15 kV R
Contact discharge 6 kV B
8 kV 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.
AC side 2 kV B
DC side 2 kV B
Signal side 1 kV 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).
! 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.
Item Range
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)
! The density of chemically active materials complies with the requirements listed in
Table 8-23:
Table 8-23 Density requirements for chemically active materials (for storage)
Mechanical Stress
! 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.
Waterproof Requirements
Item Requirements
To place the equipment in ! There is no water on the ground and no water flows into
the equipment room the package.
(recommended) ! Keep the equipment away from devices such as automatic
fire extinguishers and heating pipes.
To place the equipment ! The package is stored well.
outside the equipment room ! 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.
Item Range
Biological Environment
! 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
! 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-27:
Table 8-27 Density requirements for mechanically active materials (for transportation)
! The density of chemically active materials complies with the requirements listed in Table
8-28:
Table 8-28 Density requirements for chemically active materials (for transportation)
Mechanical Stress
! 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.
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.
! 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.
Item Range
Biological Environment
! 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
! 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-32:
Table 8-32 Density requirements for mechanically active materials (for equipment running)
! The density of chemically active materials complies with the requirements listed in
Table 8-33:
Table 8-33 Density requirements for chemically active materials (for equipment running)
Mechanical Stress
! 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.
9 Compliant Specifications
Title Description
9.1 3GPP Specifications This section describes the compliant 3GPP specifications
of the MSOFTX3000.
9.2 ITU-T Specifications This section describes the compliant ITU-T specifications
of the MSOFTX3000.
9.3 Other Technical This section describes the other compliant specifications
Specifications of the MSOFTX3000.
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.