Professional Documents
Culture Documents
Huawei Msoftx3000 Product Description
Huawei Msoftx3000 Product Description
Contents
1 Introduction.................................................................................................................................1-1
1.1 Product Orientation ..........................................................................................................................................1-2
1.1.1 Introduction to Huawei Mobile Softswitch Solution .............................................................................1-2
1.1.2 Features of Huawei 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 mobile softswitch networks ..................................................................................1-5
Table 1-3 Protocols ................................................................................................................................................1-7
Table 1-4 Related abbreviations ............................................................................................................................1-8
Table 1-5 Protocols, links, and signaling modes supported and interfaces provided by the MSOFTX3000 ......1-9
Table 1-6 Measures taken in designing the MSOFTX3000................................................................................ 1-11
Table 3-1 Numbers and functions of physical interfaces ......................................................................................3-2
Table 3-2 Specifications of FE electrical interfaces..............................................................................................3-3
Table 3-3 Specifications of E1 interfaces..............................................................................................................3-3
Table 3-4 Specifications of clock interfaces..........................................................................................................3-4
Table 3-5 Interfaces and protocols supported by the MSOFTX3000 in a mobile network .................................3-5
Table 3-6 Signaling and protocols supported by the MSOFTX3000. ..................................................................3-7
Table 5-1 Original CDR generation scenario ......................................................................................................5-16
Table 5-2 List of the features supported by the MSOFTX3000 .........................................................................5-22
Table 7-1 Security authentications ........................................................................................................................7-7
Table 8-16 Density requirements for mechanically active materials (for storage) ............................................ 8-11
Table 8-17 Density requirements for chemically active materials (for storage) ................................................ 8-11
Table 8-18 Mechanical stress requirements (for storage) ................................................................................... 8-11
1 Introduction
Section Describes
parts, namely, the MSC server and the MGW, in the 3GPP R4 and later versions. Table 1-1
describes the function of the MSC server and the MGW.
MSC It connects with the BSS or the UTRAN, The MSOFTX3000 provided by
server and performs the following control Huawei serves as an MSC
functions of the CS domain: server, as shown in Figure 1-1.
z Mobility management
z Security management
z Handover processing
z Signaling processing
z Call processing
z 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, Huawei serves as an MGW, as
and performs the following functions: shown in Figure 1-1.
z Media transformation
z Bearer management
z Coding/Decoding of digital signals
z Echo cancellation
z Conference bridging
This solution can be upgraded online and configured dynamically during the evolution from
the GSM to the UMTS.
High Efficiency
In Huawei mobile softswitch solution, 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 Huawei mobile softswitch equipment enjoys:
z High integration
z Large capacity
z Powerful processing capability
It saves equipment room space, and reduces the power consumption. Carriers can focus their
O&M on a small number of softswitch offices, thereby reducing the operation expenditure
(OPEX).
On the basis of an open architecture and distributed software technology, the Huawei mobile
softswitch solution helps carriers quickly develop services. Statistics shows that the
development cycle of services based on mobile softswitch networks is 50% shorter than that
based on conventional switching equipment.
Highly Reliable
The innovative dual homing solution provided by Huawei ensures the high reliability (1+1
mutual aid and N + 1 backup) for MSC Servers. It supports 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 network-level flow control mechanism, Huawei ensures that the voice quality is not
affected when the IP bearer network is congested. The advanced flow control mechanism
ensures that the network remains highly reliable even when traffic is heavy.
Smooth Evolution
The fixed mobile convergence (FMC) is the trend of network development. During 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
also provides integrated services.
In the future, the fixed and mobile networks can be integrated through the IMS subsystem at
the network level. The Huawei mobile softswitch equipment MSC Server and MGW can also
be evolved to the equipment in IMS smoothly. This saves the capital expenditure (CAPEX)
for carriers.
More Benefits
Compared with the conventional switched circuit network (SCNs), mobile softswitch
networks offer carriers the benefits, as listed in Table 1-2:
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 Server CN: Core Network CS: Circuit Switched domain
SGSN: Serving GPRS Support Node PS: Packet Switched domain PSTN: Public Switched Telephone Network
UTRAN: UMTS Terrestrial Radio Access Network BSS: Base Station 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
Benefit Description
Benefit Description
New services can be New services can be provided on the mobile softswitch layer
offered quickly and without affecting the MGW in the bearer layer. Therefore, the
easily mobile softswitch network allows users to develop and offer new
services more flexibly and quickly in the following ways:
z The open network structure shortens the cycle of developing
services.
z Centralized service management makes service deployment
easy.
z 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, SIP, CAP, BSSAP,
RANAP, MAP, ISUP, TUP, and BSSAP+. It can provide the functions 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:
z PSTN
z NGN
z Integrated services digital network (ISDN)
z Other PLMNs
The GMSC server performs the following functions:
z Serving as a mobile gateway office between networks
z Analyzing routing
z Implementing call connection and settlement between networks
The MSOFTX3000 supports H.248, MAP, and ISUP. It provides the following functions:
z Black and white lists
z Call authentication
z Call interception
z 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:
z Routing analysis
z 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, CAMEL 3, and CAMEL 4. In the target network mode, the MSOFTX3000 can
serve as an SSP.
The MSOFTX3000 can also support the Overlay network mode and trigger mobile IN
services based on number segments.
Table 1-4 lists related abbreviations.
PLMN country, barring of all incoming calls, barring of supplementary management, and
barring of incoming calls when roaming outside home PLMN country
z IN services: prepaid and mobile virtual private network
z Value-added service: multimedia, mobile location, ring back tone, equal access, charging
based on time and area, enhanced roaming restriction, alternate line service, and voice
and video double number
Table 1-5 Protocols, links, and signaling modes supported and interfaces provided by the
MSOFTX3000
Note:
NMC: Network management center
Item Measure
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:
z 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 located remotely.
z The MSOFTX3000 allows subscribers' handover between GSM and UMTS systems.
The MSOFTX3000 enables the network to control the subscriber access.
z 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 during the upgrades.
2 System Structure
Section Describes
2.1 Hardware Structure The physical and logical structures of the MSOFTX3000
hardware.
2.2 Software Structure The logical structure of the MSOFTX3000 software.
2.3 Capacity Expansion 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:
z IEC60297-1, Dimensions of mechanical structures of the 482.6 mm (19 in) series Part
1:Panels and racks
z IEC60297-2, Dimensions of mechanical structures of the 482.6 mm (19 in) series Part
2:Cabinets and pitches of rack structures
z IEC60297-3, Dimensions of mechanical structures of the 482.6 mm (19 in) series Part
3:Subracks and associated plug-in units
z Alarm boards
z Power boards (each occupies two standard slots)
The remaining 12 slots are used for service boards and interface boards.
FE To IP MAN
FE
0#
0# Subrack FE To Billing Center
主用iGWB
Active iGWB
2×FE
LAN Switch 1
BAM
2#
2# Subrack
机框 Background
后台部分
LAN Switch
To network
management
center
9# Subrack
机框
Host
主机部分 EWS
WS WS WS
Inter-Device Communication
The inter-device communication of the MSOFTX3000 system is as follows:
z The subracks communicate with each other through the internal Ethernet. Each subrack
is connected to LAN Switches 0 and 1 through two network cables.
z 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.
z 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 the TCP/IP protocols in
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 expand its capacity
smoothly.
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
Interface Signaling
Module Service
Lower-Layer Processing
BITS WCKI Processing Module
Module
E1/T1 WEPI CPC
Interface WCCU
WCDB
FE WBFI/ WBSG
Interface WIFM WHSC
WMGC
LAN bus
OSTA bus
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:
z Interconnection of multiple subracks
z Connection between these subracks and management devices
Interface Module
The IM provides various physical interfaces to meet the system networking demands,
including:
z Narrowband interface: The E1_pool interface unit (WEPI) provides eight E1 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 the internal HW.
z ATM-2M interface: The WEPI provides eight E1 interfaces and two 8-Mbit/s HW signal
cables to connect with the WEAM. The WEAM segments and re-assembles the ATM
cells in the data streams, and transfers signaling to the WBSG through internal LAN bus.
z FE interface: The WIFM provides the 100-Mbit/s Ethernet electrical interface by
configuring the FEP subboard and the WBFI. It distributes and brings together
broadband signaling information streams, and distributes them to the specified
processing unit based on the IP address and the port number.
z 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 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, real-time software.
Middleware
The MSOFTX3000 adopts the middleware technology (DOPRA_C), so the high level service
software becomes irrelevant to 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 released quickly.
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:
z The signaling bearer software: It is configured on WEPI, WIFM, WAFM, and WBSG. It
accesses broadband and narrowband signaling, and processes bottom layer protocols.
z The service processing software: It is configured on WCCU/WCSU and WMGC. It
carries out signaling and call processing, mobility management, and resource
management.
z The database software: It is configured on the WCDB and WVDB. It manages the data
of MSOFTX3000 and dynamic subscriber data.
z The system support software: It is configured on the WSMU and WHSC. It carries out
system management and device interworking.
z The O&M software: It 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 and connects with the BAM and iGWB servers as a client
in client/server mode. It 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:
z Data maintenance
z Equipment management
z Alarm management
z Performance measurement
z Call and signaling tracing
z CDR management
z Report functions
Figure 2-7 Configuration of MSOFTX3000 cabinets (when the NET Switch is configured in the
integrated configuration cabinet)
Integrated configuration Service processing Service processing
cabinet cabinet 1 cabinet 2
Power distribution subrack (2U) Power distribution subrack (2U) Power distribution subrack (2U)
Expansion subrack (01) (9U) Expansion subrack (05) (9U) Expansion subrack (09) (9U)
Basic subrack (00) (9U) Expansion subrack (04) (9U) Expansion subrack (08) (9U)
Figure 2-8 Configuration of MSOFTX3000 cabinets (when the NET Switch is configured outside
the cabinet)
An integrated configuration cabinet is mandatory for the MSOFTX3000 and includes the
following components:
z Power distribution subrack
z Up to two service processing subracks
z Air deflector
z KVMS (Keyboard, Video, Mouse, and Switcher)
z Core LAN Switch (up to two)
z iGWB (configured for charging, usually two)
z BAM
A service processing cabinet is configured based on the capacity requirements of carriers. It
includes the following components:
z Power distribution subrack
z Up to four service processing subracks
z Air deflector
0 - 200 k
200 k - 1 M
1 M - 1.8 M
Section Describes
Item Value
Specifications of E1 Interfaces
Table 3-3 lists the specifications of E1 interfaces:
Item Value
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 Center HLR: Home Location Register
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 the 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
4 O&M System
Section Describes
MSOFTX3000 host
LAN Switch
To BC
WAN
Active Standby
BAM
iGWB iGWB
To NMC
HUB WAN
iManager
M2000
z 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.
z Query
z Storage
z Backup
z Restoration
With these methods, you can effectively manage and maintain the following data of the
MSOFTX3000:
z Hardware data
z Office information data
z Gateway data
z Signaling data
z Routing data
z Number analysis data
z Mobile service data
z IN service data
The MSOFTX3000 configuration management also provides the following functions:
z Offline or online data configuration
z Local and remote configuration
z Online upgrade of data
z Data verification (ensuring consistency of host data and BAM data)
System Self-Test
The MSOFTX3000 tests its resource occupation regularly. The MSOFTX3000 also performs
the following functions:
z Checking the occurrence and severity of overload, and processing the overload
z Coordinating the usage of the system software
z Minimizing the impact of faults on the system
Alarm Management
The alarm management system of the MSOFTX3000 performs the following alarm
management operations:
z Detects and reports in real time any fault or abnormity of the equipment
z Generates 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
z Sends the alarm information after resolution to the NMC through the NM interface.
z Stores the alarm information, query the alarm record, configures the troubleshooing
method, and provides CPU threshold data in the reported alarm information when the
CPU usage rate is too high
z Presents the alarm information as well as handling suggestions 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:
z Query
z Display
z Switchover
z Reset
z Isolation
z Block
z Activation
Using these methods, you can effectively and efficiently manage and maintain the following:
z Hardware components of the MSOFTX3000
z System resources
z Signaling links
z Physical ports
z Gateways controlled by the MSOFTX3000 and the related bearer resources
Tracing management
The tracing management of the MSOFTX3000 offers the graphic interface, and provides the
following functions:
z Connection tracing
z Signaling tracing
z Interface tracing
z Message interpretation
With these functions, you can conduct real time and dynamic tracing on the following items
related to the terminal subscribers, trunk circuits, signaling links, and interface protocols:
z Connection process
z State transition
z Resource occupancy
z Telephone number information transfer
z Control information streams
The tracing information can be stored for future reference, enabling the two functions of:
z Fault analysis
z Location capabilities
Log Management
It helps in querying MML operation records. By querying the log, you can check whether any
operation that may affect the operation of the system has been performed.
Section Describes
5.1 Basic Services The service functions consisting of circuit switched domain
services, such as, teleservices, supplementary services, IN
services, and value added services.
5.2 Basic Functions The mobile network functions consisting of the mobility
management, security management, call control, location
services, and service switching function.
5.3 Description of Features Features and functions except the basic services and the
functions.
z Originating SMS: This service transmits a short message from user equipment (UE) to a
message handling system (service center). After the service center receives the message,
it sends an acknowledgement message.
z Terminating SMS: This service transmits a short message from a service center to UE.
After the UE receives the message, it sends an acknowledgement message.
Speech Services
The speech service is the basic function of the telecom network, including telephony (TS 11),
emergency call (TS 12) and emergency call for special service:
z Telephony: The carriers provide the telephony service for PSTN, ISDN, and PLMN
subscribers through the function.
z Emergency call: When a mobile subscriber presses an emergency key or dials 112, the
call is connected to the answer phone notice equipment. The answer phone tells
subscribers how to call the emergency center. The subscribers can make emergency calls
even without a SIM or USIM.
z 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 that the
subscribers are located in. These calls can generate the alarms. The carriers can decide
whether to charge the subscribers, and then performs related settings.
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 the 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 subscribers to send or receive the SM at any time. The broadcast SMS allows
subscribers to receive public messages regularly and selectively.
The SMS includes PTP SMS and point-to-multipoint SMS. The PTP SMS includes the
following:
z BAIC-ROAM: When the service is activated and the mobile subscribers are roaming
outside the home PLMN country, they cannot receive incoming calls from other
subscribers.
Multiparty Service
A mobile subscriber who registers this service can organize a multiparty telephone conference
(MPTY) (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 the remote subscriber. Here ‘isolate’ means the chairman of the MPTY
isolates one subscriber from the meeting temporarily.
z The ODB can be activated automatically, while call barring service is activated by
carriers or subscribers.
5.1.4 IN Services
Overview
The Huawei MSOFTX3000 provides the gsmSSF function. The MSOFTX3000 supports
CAMEL 3, Prepaid Service (PPS) and Mobile Virtual Private Network (MVPN), and it is
compatible with CAMEL 2 and CAMEL 1.
PPS
The PPS is a card number service. To set up an account, the PPS subscriber must pay some
money in advance or purchase the capital card with a fixed face value (rechargeable card,
storable card and renewable card) for the conversation fees.
The carriers do not identify the ID of the subscriber. The carriers and the subscribers share
only a prepaid agreement relation. The PPS is convenient for both carriers and subscribers.
The system determines whether to connect or disconnect the call based on the account balance.
Once the call is connected, the system performs real-time charge and deducts the PP money
from the subscriber account. If the account balance is used up, the call is disconnected. Thus,
the PPS helps carriers avoid loss of conversation fees.
MVPN
The carriers establish the private network of logic voice channel on the PLMN and PSTN.
This enables the convenient communication among an enterprise and group subscribers
through the following ways:
z Private numbering plan
z Abbreviated dialing
If the MVPN service is activated in the PLMN, it provides a private network service similar to
the 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:
z In-net calling
z Off-net calling
z Private label
z Abbreviated label
z Group access number
z Override
The MVPN service provides a preferential charging rate for groups and enterprises. This helps
mobile carriers not lose VIP customers. Based on specifications, the MVPN service requires
the following:
z All MSCs/GMSCs/HLRs support the MAP2+.
z All MSCs/GMSCs have the SSP function and they can trigger IN services through
O-CSI/T-CSI.
service is displayed as the caller ID on the terminal of the called party. The same applies to
videophone calls. When a caller calls a mobile subscriber, either the MSISDN for voice
service or videophone service can be used.
IMSI Attach/Detach
If the network allows the MS to access the network, the VLR automatically 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 automatically 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:
z Implicit IMSI detach: After the implicit IMSI detach timer times out, the VLR
automatically sets the status of subscriber to detach.
z 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:
z Location update
z Call setup
z 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 MSC 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:
z Intra-GSM handover
z Intra-UMTS handover
z Handover between the UMTS and the GSM
In respect of the MSC, the handovers performed by the MSC consists of the following:
z Intra-MSC handover
z Inter-MSC basic handover
z 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:
z Subsequent handover back to controlling MSCa
z 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 MSCa informs MSCb' of preparing for the handover.
Step 4 MSCb' instructs the local BSS and the RNS to allocate the resources.
Step 5 MSCb' notifies MSCb to send a handover command.
Step 6 MSCb releases the bearer between MSCa and MSCb.
----End
Number Analysis
The MSOFTX3000 provides a powerful number analysis function that has various
applications:
z Supports receiving and storing numbers with up to 32 digits
z Supports number analysis of up to 32 digits
z Supports 30000 called number prefixes
z Supports 4096 GT codes
z Supports service check function
z Supports call authority check function
z Supports pre-processing function for incoming number and outgoing number
z Supports caller number discrimination function
z Supports black and white list call barring function
z Supports the restriction of minimum number length and maximum number length
z Supports changing numbers (caller numbers, callee numbers and roaming numbers)
based on number location or specified characters
z Supports changing caller number or callee number based on association relationship
between them in number analysis range
z Supports changing caller type, caller address property indicator and callee address
property indicator in the sent inter-office originated address message IAM/IAI.
Route Selection
The MSOFTX3000 can select the route to connect calls based on the number analysis result
and caller information. The route selection function supports the following:
z Intra-office route selection function (to the BSC/RNC that the MSC belongs to) and
inter-office route selection function (to other office)
z Route selection function according to sequence or percentage
z Dynamic route selection based on time
z Avoidance peer route alternative function
z Multi-gateway static route function, and inter-gateway route selection based on random,
percentage and alternate selection policy
z 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 describes the generation scenarios of various original
CDRs.
Mobile originated call If a non-IN mobile subscriber originates a call, and the call is
(MOC) record answered, the MSC generates a CDR called mobile-originated
call record or MOC CDR for the caller when the call ends or the
timer of long time call CDRs expires.
Mobile terminated call If a non-IN mobile subscriber receives a call, the MSC generates
(MTC) record a CDR called mobile-terminated call record or MTC CDR for the
callee when the call ends or the timer of long time call CDRs
expires.
Mobile originated call During a call connection, assume that:
forwarding attempt z B is a non-IN mobile subscriber.
z B registers the call forwarding service.
z 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, the MSC generates an MOC CDR for A, a CFW
CDR for B, and an MTC CDR for C when the call ends or the
timer of long time call CDRs expires.
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 an 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", the MSC generates a CDR called transit
record or TRANSIT CDR when the call ends or the timer of long
time call CDRs expires.
Inter-network transit When an incoming trunk originates a call, the MSC (TMSC)
call attempt connects the call to an outgoing trunk after analyzing the call.
That is, the call is neither originated nor terminated in the local
MSC. If the types of incoming and outgoing office directions are
"Other network" (Other PLMN or PSTN), the MSC generates a
CDR called inter-network transit call record or OT_TRANSIT
CDR, when the call ends or the timer of long time call CDRs
expires.
OutGtewayRecord When an incoming trunk originates a call, the MSC (GMSC)
connects the call to an outgoing trunk after analyzing the call.
That is, the call is neither originated nor terminated in the local
MSC. If the type of incoming office direction is "Local network",
and the type of outgoing office direction is "Other network"
(Other PLMN or PSTN), the MSC generates a CDR called
outgoing gateway record or GWO CDR when the call ends or the
timer of long time call CDRs expires.
IncGatewayRecord When an incoming trunk originates a call, the MSC (GMSC)
connects the call to an outgoing trunk after analyzing the call.
That is, the call is neither originated nor terminated in the local
MSC. If the type of incoming office direction is "Other network"
(Other PLMN or PSTN), and the type of outgoing office
direction is "Local network", the MSC generates a CDR called
incoming gateway record or GWI CDR when the call ends or the
timer of long time call CDRs expires.
Roaming record Note:
The MSOFTX3000 provides the roaming record only for the 3G network
subscribers.
Assume that a non-IN roaming mobile subscriber is called The
call must be routed and connected to the GMSC of the home
PLMN. When the call ends, or the timer of long time call CDRs
expires, the GMSC generates a CDR called roaming record or
ROAM CDR for the callee.
Call attempt record Determining that a call type is a transfer call, an inter-network
transit call, an outgoing gateway exchange call, or incoming
gateway exchange call, the MSC generates a CDR called call
attempt record or ATTEMP CDR if the call fails to be set up.
The ATTEMP CDR is used to record the network resources
occupation for an unsuccessful call. That is, the ATTEMP CDR
is a TRANSIT CDR, an OT_TRANSIT CDR, a GWO CDR or a
GWI CDR. The only difference is that the release cause value in
the ATTEMP CDR is unsuccessfulCallAttempt. Based on the
value, the billing center can pick up the ATTEMP CDR.
calculates the charge. Subscribers can obtain the present call charge and the accumulated
call charge through the menu. CDR charges of AoCI services are settled at the network
side. Mobile subscribers only obtain charging information of this call.
z AoCC: CDR charges of AoCC services are settled at the terminal MS. The MSC is
responsible for delivering the rate information. Coordination of the terminal MS that
supports Phase2 standard and a special SIM card is required. AoCC is a simple mode that
helps realize leased phone or prepaid services.Hot Billing
After the MSOFTX3000 sends the original CDR generated during a call to the iGWB, the
iGWB allocates one single channel to store the final CDR and sends them to the billing center
in real time to realize the billing for the subscriber.
5.2.6 SSP
Overview
The MSOFTX3000 supports the mobile SSP functions, including the following
z Call control function (CCF)
z Service switching function (SSF)
z 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.
IP Facsimile V100R005
Multiple Time Zones V100R005
Paging Classification V100R005
Dual Transfer Mode V100R005
LCS Services V100R005
INClassMark Trigger IN Service V100R005
Configuration Rollback V100R005
Alarm Association Service V100R005
Management of Area-based Authority V100R005
Device Archive Management V100R005
Client Software Automatic Adaptation Management V100R005
M2000 Online Monitor and Management for Logging V100R005
Subscriber
Mini-A-Flex Networking V100R003
Iu-Flex Networking V100R003
Network Sharing In Connected Mode V100R003
SCCP Policing V100R003
MAP Policing V100R003
ECT Service V100R003
SOR Function V100R003
TFO Function V100R003
TrFO Function V100R003
IN Announcement Charging V100R003
IN DCH Setting V100R003
2G/3G Network Access Control Based on Different V100R003
Subscribers
Half-Rate-Based Subscriber Access Classification V100R003
Specified Circuit Dialing Test V100R003
z 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.
z 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.
z 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 subscription
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 subscription
network are cut over to the new subscription network. At the same time, the current
subscription network assigns a new IMSI number to the MNP subscriber.
In the same subscription 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:
z No need to change MSISDN: The MSISDN does not vary with carriers or subscription
networks.
z 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.
z 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.
z Independent service: It does not conflict with any other mobile service.
IP Facsimile
IP facsimile is the facsimile service over IP. It is important to ensure the quality of data
transmission, because the quality of data transmission determines the facsimile 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, and also determines
whether to notify the MGW to perform facsimile event detection after the call is started. After
the MGW reports the facsimile tone detection event or facsimile 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 function to store location
information of subscribers.
z Mobile callee location service: The external device can locate a mobile terminal.
z Mobile caller location service: The mobile terminal originates the locating request.
z Emergency call location service: The network side can locate the subscriber in an
emergency call.
z Subscriber privacy protection: The party who requests locating can be restricted based on
the requirement on the subscriber privacy.
z 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. The MSOFTX3000 supports configuration rollback to avoid
traffic loss due to mistakes and improve the network security.
There are examples as follows:
z 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.
z Swiftly to be effective: After your confirmation, the configured data can be effective
within the designated time, and enter the state of trial-run and observation.
z Swift rollback: When errors of configured data occur and cause abnormal operations
during trial-run, the system can be swiftly rolled back to the state of original data, so as
to avoid large-scale impacts on the system service.
z Comparison of configured data: You can compare the data before modification with the
data after modification to make sure what has changed. This can help you locate the
errors easily.
z 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.
z Gateway alarm correlation: Alarms for gateway faults and alarms for faults of links and
circuits of the gateway are correlated.
z The alarm correlation function can be enabled or disabled by using configuration
commands.
MSOFTX3000
MGW 1 MGW 3
MGW 2
BSC 1 BSC 3
BSC 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 multiple CN nodes in a same domain. In
the CS domain, Iu-Flex is also called MSC Pool. Figure 5-4 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-4, 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:
z 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.
z 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:
z 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.
z Avoid the congestion and overload of signaling links between the MSOFTX3000 and the
HLR, VLR, MSC, SMC and SCP.
z Ensure the signaling network security.
The local MSC can start the SCCP shielding control in the SCCP layer when the following
requirements are met:
z The MSOFTX3000 enables the SCCP Policing function.
z 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:
z Decrease the call alternative route between two networks and increase the network usage
ratio.
z Cut down call costs for callers.
The SOR function has the following three flows:
z 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.
z 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.
z 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 negotiation 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-5.
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-6.
Figure 5-6 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-7.
Figure 5-7 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.
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:
z Play announcement.
z Receive number and play announcement.
z Play announcement and receive number.
z Play announcement and connect call.
z 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:
z Provide the charging service of IN resources usage for subscribers
z 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:
z Release the call by force.
z Continue the call by force.
z Use the default call handling method subscribed by the IN subscriber.
The IN DCH setting function has the following functions:
z 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.
z 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.
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.
Section Describes
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
and subscription data. It is a TDM-based or IP-based interface directly inherited from the
R99 stage. It adopts the SIGTRAN protocols.
z 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.
z MSOFTX3000<->SMC: E interface. Adopting the MAP protocol, it transfers the mobile
originated and mobile terminated short messages between the SMC and the
MSOFTX3000.
z 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.
z 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.
z MSOFTX3000<->BC: The interface adopts the FTP/FTAM protocol and enables the BC
to automatically fetch CDRs from the iGWB of the MSOFTX3000.
z 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 the following interfaces
as follows:
z 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.
z 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.
z 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.
z 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.
z 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 commands of the SCP
Thus, 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.
z MSOFTX3000<->BC: The interface adopts the FTP/FTAM protocol and enables the BC
to automatically fetch CDRs from the iGWB of the MSOFTX3000.
z MSOFTX3000<->M2000: The interface adopts the MML protocol and supports the
MSOFTX3000 to access the 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 does
not require hierarchical processing. In this case, the media gateway (MGW, such as
UMG8900) is not required 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 MSOFTX3000 A breaks down or an emergency occurs, MSOFTX3000 B takes over
the service control of the MSC areas A and B. In this case 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, only MGWs 1
and 2 register with MSOFTX3000 A. MSOFTX3000 B controls the services in MSC area B.
MGWs 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. In this case MGWs 1 and 2 register with MSOFTX3000 B.
When MSOFTX3000 B breaks down or an emergency occurs, MSOFTX3000 A takes over
the service control of MSC area B. In this case MGWs 3 and 4 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 an emergency occurs, MSOFTX3000 B takes over
the service control of MSC area A and B. In this case MGW 1 to MGW 4 register with
MSOFTX3000 B. When MSOFTX3000 C breaks down or an emergency occurs,
MSOFTX3000 B takes over the service control of MSC area C. In this case 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 an emergency occurs, MSOFTX3000 B takes over
the service control of MSC area A. In this case MGWs 1 and 2 register with MSOFTX3000 B.
When MSOFTX3000 C breaks down or an 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 manage the service control
of two or more MSOFTX3000s at the same time. Besides, the assistant MSOFTX3000 can
work in 1+1 mutual assistance mode with any other MSOFTX3000 in the network.
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 an intra-office or inter-office call.
The MA network structure is applied to the following kinds of networking solutions:
z High density and large capacity local network: For 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.
z Wide coverage local network: For 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 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 describe 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 is elaborated. The solution of Huawei R5 is as shown in
Figure 6-11.
CS MSS/MGCF IMS
CSCF
T-MSS SG
MSS
IP / 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. This
ensures investment protection.
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
Section Describes
Redundancy Design
The hardware of the MSOFTX3000 adopts designs, such as active/standby mode, load
sharing mode, and redundancy configuration, to ensure reliability of the hardware system.
z The main 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 processor to control the
operation of the system without interrupting the service.
z The service boards and interface boards of the MSOFTX3000 adopt 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.
z The IP interface of the MSOFTX3000 supports physical backup, ensuring reliability of
the IP routes between the MSOFTX3000 and the IP bearer network.
Derating Design
It is to lower 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:
z Postponing degeneration of the parameters
z Prolonging their service lives
z Enhancing their reliability
Maintainability Design
The maintainability design aims to meet the specified quantity and quality demands on
maintainability, especially the demand on reducing maintenance time. The maintenance
design covers the following:
z Product design and maintenance simplification
z Reachability
z Standardization and exchangeability
z Modularization
z Error prevention design and identifier
Power Reliability
To improve the reliability of the power supply system, the following are employed in the
MSOFTX3000:
z Distributed power supply: Distributes power separately to each subrack or functional
module through high-frequency DC/DC secondary power modules, ensuring efficiency
and stability.
z 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, it does not affect the operation of the system.
z 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.
z Code walk-through
z Inspection
z Review
z Unit test
z System test
Protection Measures
The modular design is used for the software. The software modules are based on the loose
coupling mechanism, where the failure of one module does not affect other modules. 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 must eliminate certain defects found in the
system, and add new features. Traditionally, you halt the running of the host software to
upgrade, thus affecting the services provisioning. The MSOFTX3000 however supports the
hot patch function. By patching the host software, the software can be upgraded in the
in-service state, without affecting the quality of the provided communication services.
Software Reliability
The charging system software of the MSOFTX3000 is reliable, as described as follows:
z 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.
z 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 consistency between the original
CDR data and the final CDR data.
− Data backup: The iGWB Server backs up CDR files and other important data in it
regularly.
z CDR error tolerance
− A protective mechanism of the CDR pool.
− The system can automatically create the CDR directory for recovery when it is
deleted intentionally.
− Offline repair of error CDRs is provided.
z Transmission reliability
The iGWB Server transmits CDRs to the billing center through FTP or FTAM. Both
retransmission and broken retransmission are supported.
z Automatic backup in iGWB Server: The iGWB Server adopts 1+1 backup mode. The
active server regularly backs up the CDR data in the hard disk to the standby server to
carry out the level-four buffer.
Item Standard
EMC EN 55022
FCC part 15
VCCI
AS/NZS 3548
GR-1089
Safety EN/IEC 60950
UL60950
IEC60950
GR-1089
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 32000 packets/second
board
Clock stratum Stratum-2 A
Item Specification
Section Describes
Parameter Specification
Parameter Specification
Requirement Specification
Item Specification/Model
Item Specification
The specifications listed in Table 8-11 are for reference only. They can be changed as needed.
Item Specification
Item Specification
z Lowest accuracy is the maximum value of the offset to the nominal frequency in a long term (20
years) in the case of no external reference frequency (free-run mode).
z Maximum frequency offset is the maximum value of the relative frequency offset in a unit period
during the consecutive running of the clock.
z Pull-in range is the maximum frequency bandwidth of the input clock signals that the clock can lock.
z MRTIE refers to the maximum peak-peak delay change of the tested clock to an actual reference
clock during the test.
Figure 8-1 Maximum allowed input jitter and lower limit 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)
For example, if the jitter frequency of an input signal is 1 kHz, and the amplitude is greater
than 1.5 UI, and the system can still work normally, it indicates that the signal meets the
requirements.
UI is the unit interval. The reciprocal of the frequency of the digital signal is one UE. For example, the
UI of 2.048-Mbit/s signal is 488 ns.
Item Range
Biological Environment
The biological environment for storing the MSOFTX3000 system requires the following:
z Ensure that the equipment is kept in a place free from epiphyte, mildew and other
microorganisms.
z Prevent rodents from damaging the equipment.
Air Cleanness
The air quality for storing the MSOFTX3000 system requires the following:
z The air must be free from explosive, conductive, magneto-conductive, or corrosive dust.
z The density of mechanically active materials complies with the requirements listed in
Table 8-16.
Table 8-16 Density requirements for mechanically active materials (for storage)
z The density of chemically active materials complies with the requirements listed in
Table 8-17.
Table 8-17 Density requirements for chemically active materials (for storage)
Mechanical Stress
z 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.
z Payload: It refers to the amount of pressure from the equipment piled that the equipment with
package can bear according to the prescribed piling mode.
Waterproof Requirements
Item Requirements
To place the equipment in z There is no water on the ground and no water flows into
the equipment room the package.
(recommended) z Keep the equipment away from devices such as automatic
fire extinguishers and heating pipes.
To place the equipment z The package is stored properly.
outside the equipment room z Measures are taken to prevent water from entering the
package.
z The package is not exposed to sun.
z There is no water on the ground where the package is
placed and no water flows into the package.
Item Range
Item Range
Biological Environment
The biological environment for transporting the MSOFTX3000 system requires the following:
z Ensure that the equipment is kept in a place free from epiphyte, mildew and other
microorganisms.
z Prevent rodents from damaging the equipment.
Air Cleanness
The air quality for transporting the MSOFTX3000 system requires the following:
z The air must be free from explosive, conductive, magneto-conductive, or corrosive dust.
z The density of mechanically active materials complies with the requirements listed in
Table 8-21.
Table 8-21 Density requirements for mechanically active materials (for transportation)
z The density of chemically active materials complies with the requirements listed in
Table 8-22.
Table 8-22 Density requirements for chemically active materials (for transportation)
Mechanical Stress
z 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.
z Payload: It refers to the amount of pressure from the equipments piled that the equipment with
package can bear according to the prescribed piling mode.
Waterproof Requirements
While transporting the equipment, ensure that the following requirements are met:
z The package is stored properly.
z Measures are taken in the transportation vehicles to prevent rain from entering the
package.
z There is no water inside the transportation vehicles.
z 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.
z Short term means that the consecutive working duration is not more than 48 hours or the continuous
working duration in a year is not more than 15 days.
Item Range
Biological Environment
The biological environment for running the MSOFTX3000 system requires the following:
z Ensure that the equipment is kept in a place free from epiphyte, mildew and other
microorganisms.
z Prevent rodents from damaging the equipment.
Air Cleanness
The air quality for running the MSOFTX3000 system requires the following:
z The air must be free from explosive, conductive, magneto-conductive, or corrosive dust.
z The density of mechanically active materials complies with the requirements listed in
Table 8-26.
Table 8-26 Density requirements for mechanically active materials (for equipment running)
z The density of chemically active materials complies with the requirements listed in
Table 8-27.
Table 8-27 Density requirements for chemically active materials (for equipment running)
Mechanical Stress
z 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.
z Payload: It refers to the amount of pressure from the equipments piled that the equipment with
package can bear according to the prescribed piling mode.
9 Compliant Specifications
Section Describes
G.812 Timing requirements of slave clocks suitable for the user as ITU-T
node clocks in synchronization networks
G.823 The control of jitter and wander within digital networks which ITU-T
are based on the 2048 kbit/s hierarchy
I.150 B-ISDN asynchronous transfer mode functional ITU-T
characteristics
I.361 B-ISDN ATM layer specification ITU-T
I.430 Basic user-network interface - Layer 1 specification ITU-T
I.431 Primary rate user-network interface - Layer 1 specification ITU-T
I.432 B-ISDN User-Network Interface - Physical layer specification ITU-T
I.610 B-ISDN O&M principles and functions ITU-T
Q.1218 Recommendation Q.1218 (10/95) - Interface ITU-T
Recommendation for intelligent network CS-1
Q.1912.5 Session Initiation Protocol for Telephones (SIP-T) ITU-T
Q.1950 Bearer independent call bearer control protocol ITU-T
Q.2110 B-ISDN ATM adaptation layer - Service specific connection ITU-T
oriented protocol (SSCOP)
Q.2140 B-ISDN ATM adaptation layer - Service specific coordination ITU-T
function for signaling at the network node interface (SSCF at
NNI)
Q.2144 B-ISDN Signaling ATM adaptation layer - Layer ITU-T
management for the SAAL at the network node interface
Q.2210 Message transfer part level 3 functions and messages using ITU-T
the services of ITU-T Recommendation Q.2140
Q.4xx Specifications of Signaling System R2 - Provision of a ITU-T
forward-transfer Signaling facility
Q.701 Functional description of the message transfer part (MTP) of ITU-T
Signaling System No.7
Q.702 Signaling Data Link ITU-T
Q.703 Message Transfer Part Signaling Link ITU-T
Q.704 Message Transfer Part - Signaling network functions and ITU-T
messages
Q.705 Signaling network structure ITU-T
Q.706 Message Transfer Part - Signaling performance ITU-T
Q.707 Message Transfer Part - Testing and maintenance ITU-T
RFC2833 RTP Payload for DTMF Digits, Telephony Tones and IETF
Telephony Signals
RFC2960 Stream Control Transmission Protocol (SCTP) IETF
RFC3057 ISDN Q.921-User Adaptation Layer (IUA) IETF
RFC3261 Session Initiation Protocol (SIP) V2.0 IETF
RFC3309 Stream Control Transmission Protocol (SCTP) Checksum IETF
Change
RFC3331 SS7 MTP2 User Adaptation Layer (M2UA) IETF
RFC3332 SS7 MTP3-User Adaptation Layer (M3UA) IETF
RFC3372 Session Initiation Protocol for Telephones (SIP-T) IETF
RFC3551 RTP Profile for Audio and Video Conferences with Minimal IETF
Control
ISO8571 File Transfer Access and Management Protocol (FTAM) ISO
IEC 60297 Mechanical structures for electronic equipment - Dimensions IEC
of mechanical structures of the 482,6 mm (19 in) series
10 Installation
The MSOFTX3000 cabinet has been assembled and debugged before delivery. Its internal
cables are connected according to customer requirement. On site, you need to fix the cabinet,
install boards, connect external cables, and install and load the 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. The boards are hot
swappable, to facilitate cabinet expansion and board replacement. The external interfaces for
cables (including power cable, transmission cable, and signal cable) are positioned on the 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 method of installing the hardware and software is simple and can greatly reduce
installation time, and quicken network buildup and service provisioning.