SJ-20120730093520-002-ZXUN ICX (MSCS) (V4.12.10) MSC Server Product Description

ZXUN iCX(MSCS)
MSC Server
Product Description
Version: V4.12.10
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2012 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by
contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
2012-10-31
First edition
Serial Number: SJ-20120730093520-002

Publishing Date: 2012-10-31 (R1.0)
SJ-20120730093520-002|2012-10-31 (R1.0)
ZTE Proprietary and Confidential
Contents
About This Manual ......................................................................................... I
Chapter 1 Production Positioning and Features ..................................... 1-1
1.1 Product Positioning ............................................................................................ 1-1
1.2 Product Features................................................................................................ 1-2
Chapter 2 Product Architecture ................................................................ 2-1

2.1 Hardware Architecture ........................................................................................ 2-1
2.1.1 Product Overview..................................................................................... 2-2
2.1.2 Board List ................................................................................................ 2-3
2.2 Software Structure.............................................................................................. 2-4
Chapter 3 Operation and Maintenance..................................................... 3-1

3.1 Network Structure .............................................................................................. 3-1
3.2 OMM Functions.................................................................................................. 3-2
3.3 Charging Management Functions ........................................................................ 3-4
Chapter 4 Services and Functions............................................................ 4-1

4.1 Mobility Management Service ............................................................................. 4-1
4.2 Relocation and Handover Service ....................................................................... 4-1
4.3 Mobile Call Service............................................................................................. 4-2
4.4 Supplementary Service....................................................................................... 4-3
4.5 Short Message Service....................................................................................... 4-4
4.6 Mobile Data Service ........................................................................................... 4-5
4.7 Mobile Intelligent Service .................................................................................... 4-5
4.8 Location Service ................................................................................................ 4-5
4.9 Multimedia Ring Back Tone Service..................................................................... 4-5
4.10 Enhanced IMEI Check Function ........................................................................ 4-6
4.11 Load-Based Switching Function ........................................................................ 4-6
4.12 Iu-CS/A over IP ................................................................................................ 4-6
Chapter 5 Networking Modes .................................................................... 5-1

5.1 VMSCS/GMSCS Networking Mode ..................................................................... 5-1
5.2 TMSCS Networking Mode................................................................................... 5-3
5.3 MGCF Networking Mode .................................................................................... 5-4
5.4 Region Networking Mode.................................................................................... 5-5
5.5 Dual-Homing Networking Mode........................................................................... 5-6
5.6 MSC Pool Networking Mode ............................................................................... 5-9
I
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 6 Interfaces and Protocols .......................................................... 6-1

6.1 Introduction to Interfaces .................................................................................... 6-1
6.2 Iu-CS Interface................................................................................................... 6-3
6.3 A Interface ......................................................................................................... 6-4
6.4 Mc Interface....................................................................................................... 6-5
6.5 Mn Interface....................................................................................................... 6-5
6.6 Nc Interface ....................................................................................................... 6-6
6.7 MAP Interface .................................................................................................... 6-7
6.8 CAP Interface .................................................................................................... 6-7
6.9 Gs Interface ....................................................................................................... 6-8
6.10 Mj/Mg Interface ................................................................................................ 6-9
6.11 Billing Interface................................................................................................. 6-9
6.12 O&M Interface................................................................................................ 6-10
Chapter 7 Networking Specifications ....................................................... 7-1

7.1 Physical Indices ................................................................................................. 7-1
7.2 Performance Indices........................................................................................... 7-1
7.3 Power Consumption ........................................................................................... 7-2
7.4 Clock Indices ..................................................................................................... 7-3
7.5 Reliability Indices ............................................................................................... 7-4
7.6 Equipment Power Indices ................................................................................... 7-4
7.7 Interface Types .................................................................................................. 7-4
7.8 Modules and Units Indices .................................................................................. 7-5
7.8.1 Indices of Billing Module ........................................................................... 7-5
7.8.2 Indices of Power Module........................................................................... 7-6
7.8.3 Indices of Monitoring Module..................................................................... 7-6
7.8.4 Indices of Fan Unit ................................................................................... 7-7
7.8.5 Indices of Alarm Box................................................................................. 7-8
Chapter 8 Environmental Requirements .................................................. 8-1

8.1 Grounding Requirements .................................................................................... 8-1
8.2 Temperature and Humidity Requirements ............................................................ 8-1
8.3 Cleanness Requirements.................................................................................... 8-2
8.4 Air Pollution Requirements.................................................................................. 8-2
Chapter 9 Compliance Standard ............................................................... 9-1

Glossary .......................................................................................................... I
II
SJ-20120730093520-002|2012-10-31 (R1.0)
About This Manual

Purpose
The purpose of this manual is to let operators master the production and feature, the
product architecture, services and functions, networking modes, interfaces and protocols,
and networking specifications of the ZXUN iCX(MSCS).
Intended Audience
This manual is intended for:
l
l
Network planning engineers

Market engineers
Prerequisite Skill and Knowledge

To use this manual effectively, users should have a general understanding of wireless
telecommunications technology. Familiarity with the following is helpful:
The ZXUN iCX(MSCS) system and its various components
What Is in This Manual

This manual contains the following chapters:
Chapter
Summary
1, Production Positioning and
Describes the network position, role, and features of the ZXUN
Features
iCX(MSCS).
2, Product Architecture
Describes the hardware architecture and software architecture of

the ZXUN iCX(MSCS).
3, Operation and Maintenance
Describes the operation and maintenance of the ZXUN iCX(MSCS).
4, Services and Functions
Describes the services and functions of the ZXUN iCX(MSCS).
5, Networking Modes
Describes the networking modes of the ZXUN iCX(MSCS).
6, Interfaces and Protocols
Describes the interfaces and protocols of the ZXUN iCX(MSCS).
7, Networking Specifications
Describes the networking specifications of the ZXUN iCX(MSCS),

for physical specifications, performance specifications.
8, Environmental
Describes the environmental requirements of the ZXUN iCX(MSCS)
Requirements
for grounding, temperature and humidity.
9, Compliance Standard
Describes the compliance standard of the ZXUN iCX(MSCS).
Related Documentation
The following documentation is related to this manual:
I
SJ-20120730093520-002|2012-10-31 (R1.0)
l
l
ZXUN iCX(MSCS) MSC Server Signaling Description

ZXUN iCX(MSCS) MSC Server Hardware Description
FCC Compliance Statement

This device complies with part 15 of the FCC Rules. Operation is subject to the following
two conditions.
1. This device may not cause harmful interference.
2. This device must accept any interference received, including interference that may
cause undesired operation.
Changes or modifications not expressly approved by the party responsible for compliance
could void the user's authority to operate the equipment.
Conventions
This manual uses the following typographical conventions:
Typeface
Meaning
Italics
Variables in commands. It may also refer to other related manuals and documents.
Bold
Menus, menu options, function names, input fields, option button names, check
boxes, drop-down lists, dialog box names, window names, parameters, and
commands.
Constant
Text that you type, program codes, filenames, directory names, and function names.
width
[]
Optional parameters.
{}
Mandatory parameters.
Separates individual parameter in series of parameters.

Note: Provides additional information about a certain topic.
II
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 1
Production Positioning and

Features
Table of Contents
Product Positioning ....................................................................................................1-1
Product Features........................................................................................................1-2
1.1 Product Positioning

Role of ZXUN iCX(MSCS) in the Network
The ZXUN iCX(MSCS) implements the functions of the Mobile Switching Center Server
(MSCS), the Visitor Location Register (VLR) and the Service Switching Point (SSP). At the
same time, the ZXUN iCX(MSCS) can act as a Media Gateway Control Function (MGCF),
constituting an IP Multimedia Subsystem (IMS) network with other NEs.
l
Being the core of the CN system, the ZXUN iCX(MSCS) controls Mobile Stations
(MS) within its coverage and implements speech channel switching. The ZXUN
iCX(MSCS) also serves as an interface between mobile communication systems
and circuit switching networks such as PSTN, ISDN and PSPDN. It implements
functions such as network interface, common channel system and billing. Also, it
manages SS7, auxiliary radio resources and mobility management between RNS
and CN. To establish call routes to MSs, each MSCS can function as a Gateway
MSCS (GMSCS).
The VLR is a database, storing the required information for the ZXUN iCX(MSCS)
processing incoming and outgoing calls of MSs within its coverage, such as subscriber
numbers, ID of the location area where subscribers are located, and services provided
to subscribers.
The SSP is a service switching point of the intelligent network, providing measures
for identifying the call request processing of the CAMEL OSS service, interacting with
the ZXUN iCX(MSCS) call processing and call services, modifying call/connection
processing function as required, and processing requests of the intelligent services
under the Service Control Point (SCP).
The MGCF is the NE of implementing interworking between IMS services, and CS
domain services and PSTN services, implementing conversation between the control
signaling SIP in the IMS domain and the signaling BICC/ISUP in the CS domain.
1-1
SJ-20120730093520-002|2012-10-31 (R1.0)
ZXUN iCX(MSCS) Product Description
Position of the ZXUN iCX(MSCS) in the Network

For the position of the ZXUN iCX(MSCS) in the network, see Figure 1-1.
Figure 1-1 Position of ZXUN iCX(MSCS) in the Network
The ZXUN iCX(MSCS), MGW, HLR, SGSN, GGSN and other NEs constitutes the network
and standard signaling interfaces are adopted between these NEs (internal interfaces are
adopted between SCP and SMP, SCE and SMP).
1.2 Product Features

It cannot complete the billing function for the ZXUN iCX(MSCS). Instead, it provides
accurate and detailed billing data.
l
Advanced design philosophy
1-2
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 1 Production Positioning and Features
The ZXUN iCX(MSCS) product is designed strictly in accordance with 3GPP R4

specifications and compatible with R99.
Software development conforms strictly to software engineering design

requirements, and follows a top-down, layered, and modular design to make the
software easier to maintain and expand.
Inside the system, bearer is separated from control. Also system is capable
of smooth transition to R5 and downward compatible with R99 mode, protect
customers investments.
All NEs are built on unified all-IP software/hardware platform.
Flexible networking capability
Series products can either integrate functions of VMSC Server,GMSC

Server,TMSC Server, SGW, SSP, IW/GMSC and MGCF into one, or extract
some function individually, and provide open interfaces.
System supports a wide variety of signaling interfaces such as China No.1

signaling, R2 signaling, PRI signaling, broadband/narrowband SS7 signaling,
SIGTRAN and SIP signaling.
System supports multiple signaling points and 2 M high-speed signaling,

applicable for networking of large-capacity system.
System supports many transmission technologies such as TDM, ATM and IP.
Flexible configuration can be done for user requirements.
The SIP protocol supports multiple transmission modes, such as UDP, TCP and
SCTP.
Built-in dynamic routing function makes IP networking much flexible.
The ZXUN iCX(MSCS) supports region networking function.
Powerful service functionalities
Providing roaming and mobility management, relocation processing,

authentication, troubleshooting and O&M functions for mobile subscribers.
Providing telephone service and mobile data service between mobile subscribers
and subscribers of PSTN, ISDN, and other mobile subscribers.
Providing supplementary services, including call forward, call restriction, call

completion, number identification, call waiting, call hold, multi-party call, charge
information, CUG, call deflection, direct call transfer, enhanced multiple priorities
and preemption.
Providing circuit data services and supporting multimedia services in line with the
H.324M standard.
Providing CAMEL services such as pre-payment, virtual private networks, and

mobile banks, and supporting 100 % CAMEL subscribers.
Supporting LCS services such as MO-LDR and MT-LDR.

1-3
SJ-20120730093520-002|2012-10-31 (R1.0)
Supporting interworking between IMS and CS.
Compatibility and expandability
System fully complies with technical specifications of 3GPP, MTNet and ITU-T ,
and provides standard interfaces with PLMN, PSTN, ISDN and PSPDN.
Employment of multi-layer and modularization structure in the system design is

convenient for expansion and application. Flexible configuration can be done for
user requirements.
High availability and performance guarantee
Reasonable system architecture ensures high availability and performance of

equipment. The ZXUN iCX(MSCS) adopts distributed processing design, where
control plane is separated from user plane and protocol processing units are
running independently so that once a processing unit fails, it will not interrupt
others, protect system performance.
High-performance processor chip enhances system processing capability.

System employs network processor, general processor, and embedded RISC
processor, which provide great power and expandable communication function
for the system.
Redundant design ensures high reliability of telecom equipment. The ZXUN

iCX(MSCS) is equipped with many measures to protect its stability. All common
resource and protocol processing boards are in 1+1 redundant backup. Interface
board and user plane processing board are in N+M backup. All boards are hot
swappable, providing system with carrier-class working stability.
System supports dual-home networking, where two ZXUN iCX(MSCS)s are

mutually backed up. When one the ZXUN iCX(MSCS) fails, backup the ZXUN
iCX(MSCS) will take over services of failed one.
System supports MSC Pool networking.
Complete O&M system
Browser/Server(B/S) architecture provides system with good networking

capability and expendability.
OMM Server adopts CGSL and Firebird+SQLite database which provides

telcom-level reliability.
Browser uses the Windows OS which provides a friendly interface and flexible,
convenient and reliable operation.
Multiple remote and local system access modes are provided. Operation and
maintenance can be fulfilled not only locally but also remotely through network
system. Operation and maintenance are accessible not only to the entire system,
but also to specific entity.
System is of reliable security and employs multi-level authority protection.
1-4
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 1 Production Positioning and Features
System supports many functions such as performance measurement, security

management, fail observer, signaling trace, data configuration and fault
management. Also, system can be added with functions according to actual
network running conditions and customer requirements.
NMS features user-friendly interfaces and complete functions .
1-5
SJ-20120730093520-002|2012-10-31 (R1.0)
This page intentionally left blank.
1-6
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 2
Product Architecture
Table of Contents
Hardware Architecture................................................................................................2-1
Software Structure......................................................................................................2-4
2.1 Hardware Architecture

For the hardware system of the ZXUN iCX(MSCS) that contains service processing
subsystem and local maintenance terminal, see Figure 2-1.
Figure 2-1 ZXUN iCX(MSCS) Hardware Architecture
2-1
SJ-20120730093520-002|2012-10-31 (R1.0)
Based on requirement,
SWBB0 can replace
SWBB1.
Service Processing Subsystem

The service processing subsystem is mainly composed of SLB, GPBB0, GPBX1 and
SWBB0/SWBB1. For the detail information of boards, refer to 2.1.2 Board List.
Local Maintenance Terminal

The local maintenance terminal completes the management, operation and
maintenance. It uses a common PC.
2.1.1 Product Overview

Rack Hardware Structure
The cabinet adopts a B6080-22 rack , which has a maximum internal space of 47 U. Its
dimensions: 2,200 mm (H) 600 mm (W) 800 mm (D).
For the structure of the ZXUN iCX(MSCS) cabinet, see Figure 2-2.
Figure 2-2 Rack Hardware Structure
Function of Each Shelf

For the functions of each shelf, refer to Table 2-1.
2-2
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 2 Product Architecture
Table 2-1 Shelf Functions

Shelf
Functions
Power distribution shelf
It outputs -48 V or -60 V power to each shelf. A sub-rack accesses

two channels of -48 V or -60 V power input.
It has the lightning-proof and over-current protection functions, checks

the input power voltage and the distributed output power statuses, and
gives alarm signal if necessary.
It effectively monitors the rack running environment, fan heat

dissipation system, access control etc., and reports through the RS485
interface.
E4140 shelf
Prevents damages from external causes, and supplies power for

boards and fan plug-in boxes.
Constructs an independent working unit by combining the inserted

boards through a backplane. For the boards of the ZXUN iCX(MSCS),
refer to 2.1.2 Board List.
Provides heat dissipation channels for the system.
Configured with cabling troughs that are used for the cabling of
external cables of the interface board, which facilitates maintenance.
2.1.2 Board List

For the boards of the ZXUN iCX(MSCS), refer to Table 2-2.
Table 2-2 Board List of the ZXUN iCX(MSCS)
Front
Name of Front
Board
Board
GPBB0
General
A GPBB0 board is a service processing
processing blade
blade of the ZXUN iCX(MSCS). OMP,
boards for
B0
GPBX1
Functions of Front Board
Rear
Name of Rear
Board
Board
GPI1
Interface
SMP, and other processing modules
general
can be configured on the GPBB0
processing
board.
blades
General
As the background server of the ZXUN
processing blade
iCX(MSCS), a GPBX1 board includes
boards for
X1
an OMM server, a billing server, and
general
an LIS.
processing
GPI1
Interface
blades
SLB
Narrowband
An SLB board provides 32 E1/T1 links
SLI
Interface
signaling
for the ZXUN iCX(MSCS) to connect
boards for
processing blade
to the SS7 network, implementing the
narrowband
processing on HDLC or layers lower
signaling
than MTP2 of SS7.
processing
blades
2-3
SJ-20120730093520-002|2012-10-31 (R1.0)
Front
Name of Front
Board
Board
Functions of Front Board
Rear
Name of Rear
Board
Board
SWBB0
Switching blade
As the Gigabit Ethernet switching
SWI1
Interface
B0
board, an SWBB0 realizes the Gigabit
boards 1
Ethernet switching function on the
for switching
Base layer, and it can provide the clock
blades
distribution function.
SWBB1
Switching blade
As the Gigabit Ethernet switching
B1
board, an SWBB1 realizes the Gigabit
boards 2
Ethernet switching function on Base
for switching
plane and Fabric plane, and it can
blades
SWI2
Interface
provide the clock distribution function.
2.2 Software Structure

Software Architecture
The ZXUN iCX(MSCS) software system is composed of nine subsystems.
relationship among these software subsystems, see Figure 2-3.
l
l
l
l
l
l
l
l
l
For the
Service Oriented Driver Architecture (SODA) subsystem

Telecom Universal Integrated Platform (TULIP) subsystem
System Control Subsystem (SCS)
DataBase Subsystem (DBS)
Bear Subsystem (BRS)
Multicore and MicroCode Media Carring Subsystem (MCS)
Signal (SIG) Subsystem
Service Processing Subsystem (SPS)
Operation & Maintenance (OMM) Subsystem
Figure 2-3 ZXUN iCX(MSCS) Software Structure
2-4
SJ-20120730093520-002|2012-10-31 (R1.0)
SODA Subsystem
The SODA subsystem provides the whole hardware system with BOOT, device drivers,
and CPU small-system functions. It shields hardware details from other software
systems, and makes the software systems above the operating system independent of
the bottom-layer hardware equipment.
TULIP Subsystem
The TULIP subsystem provides a unified telcom-level software platform, shielding
the differences between different commercial operating systems. Providing a unified
programming environment and mode for the upper-layer applications, it meets the
requirements for flexibility and fast development of the application layer. It is in charge of
dispatching, communication, timer management, memory management, file management,
multi-core management.
SCS
The SCS is in charge of system control and monitoring, and version loading.
DBS
The DBS it provides the data configuration and storage function related to services,
signaling, and protocols. It provides other subsystems with database access/storage
interfaces. It also stores and manages the subscribers in the VLR.
BRS
The BRS is the software for the built-in router. It provides the function of processing various
bearer protocols such as IP, and the route management function. It provides the system
with IP exchange and management processing.
MCS
As the extension of the BRS, the MCS is has similar functions with the BRS. It works on
the mini-engine of the network processor and is independent of the operating system. It
provides interfaces for the BRS.
SIG Subsystem
The SIG subsystem implements various signaling functions, including narrowband SS7
signaling, broadband SS7 signaling, SIP signaling, IP signaling (SIGTRAN), and gateway
control signaling (H.248). It also provides services for the SPS. For the link-layer protocols
of broadband/narrowband SS7 signaling, the link layers of the signaling implement
link-level load sharing. When the capacity of the system is large, it supports load
sharing of multiple pairs of SMP modules. For the narrowband SS7 signaling, the SIG
subsystem supports 64 kbps, 2 Mbps and n64 kbps signaling links. It also supports the
multiple-signaling-point function in different signaling networks.
2-5
SJ-20120730093520-002|2012-10-31 (R1.0)
SPS
The SPS implements various services and VLR function provided by the ZXUN
iCX(MSCS). As the core of the ZXUN iCX(MSCS) , the SPS works above the OMM
subsystem, DBS, BRS, and the SIG subsystem. The SPS consists of the following
functional modules:
l
l
l
l
Call control module: performs paging access, channel assignment, and call
connection for mobile subscribers. And it provides the call connection function for
inter-network interworking.
Mobility management and security management module: performs location area
registration and validity check for mobile subscribers. It also processes services
when the location area of the subscriber changes during the call.
Supplementary service module:
performs registration, deletion, activation,
deactivation, query, password addition and acquisition of supplementary services.
Short message processing module: processes transmission and receipt of short
messages.
Mobile intelligent services module: implements the SSP function.
OMM Subsystem
The OMM subsystem works above all other subsystems. The operation and maintenance
personnel performs configuration, analysis, billing, diagnostic tests, and gets alarm and
statistics information of the running equipment in the network through the OMM subsystem.
The OMM subsystem consists of four functional modules:
l
Foreground module: resides on each managed NE and exchanges NE operation

information with the OMM server. The operation information includes collection
and report of alarm messages, synchronization of alarm messages, execution
of man-machine commands, execution of diagnostic commands, processing of
configuration management data, collection of performance statistics data, and
collection of service and signaling information.
Foreground programs communicate with the OMM server through the Ethernet
interface, and respond to the commands from the server and feedback the results.
Server module: is the core of OMM subsystem, which executes operation commands
from the client module, sends them to the foreground after processing them, and then
transfers feedback results to the client module.
It implements the functions such as network management, network proxy, NE
centralization and adaptation, upper-level network management access and FTP
server. The server module is the network management center to implement
performance management, configuration management, alarm management, network
diagnosis, and the local maintenance.
Client module: is the user interface of the OMM subsystem, which provides visual
interfaces for the client. It operates and controls the interfaces of various maintenance
NEs in a centralized manner, and generates and sends operation commands to the
server.
2-6
SJ-20120730093520-002|2012-10-31 (R1.0)
Billing management module: collects and transfers CDRs. Based on functions, the
billing module divides into three parts: Collection of CDRs, processing and backup
of CDRs, and transfer of CDRs. The ZXUN iCX(MSCS) cannot complete the billing
function. Instead, it provides accurate and detailed billing data.
2-7
SJ-20120730093520-002|2012-10-31 (R1.0)
2-8
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 3
Operation and Maintenance

Table of Contents
Network Structure ......................................................................................................3-1
OMM Functions..........................................................................................................3-2
Charging Management Functions...............................................................................3-4
3.1 Network Structure

The network management system (NMS) comprises operation & maintenance (OMM)
management parts and charging management parts. Figure 3-1 displays the network
management (NM) structure of the system.
Figure 3-1 O&M System Structure of the ZXUN iCX(MSCS)
3-1
SJ-20120730093520-002|2012-10-31 (R1.0)
3.2 OMM Functions

Description
The OMM comprises the OMM server and local maintenance terminal.
In software structure, the OMM consists of the foreground module, server-side module and
client-side module. The whole software frame complies with telecommunication network
management (TMN) structure.
The OMM is powerful in management. It provides centralized control of the ZXUN
iCX(MSCS) NE with powerful networking capability. It also provides the cascading control
and the reverse operation. It implements remote access by accessing WAN via routers.
Q3 NM interface standard provides powerful interface control for NM centers, and
integrates graphic interface and command line processing methods in it.
Functionally, the OMM comprises the following modules:
l
l
l
l
l
l
l
l
l
Configuration Management
Fault Management
Performance Management
Diagnosis and Test
Signaling Trace
Failure Observation
Variable Management
Security Management
Log Management
Configuration Management System

The configuration management system employs user-friendly interfaces for the
configuration and management of network resources. It provides centralized configuration
and management of the ZXUN iCX(MSCS) NE, such as the configuration and
management of physical equipment, exchange, and signaling. It is also a tool for data
transmission, data backup and recovery.
Fault Management System

The fault management system consists of two parts: real-time display of current alarms
and alarm-related operation.
Current alarms of the device, communication, service and processor are displayed through
interfaces to catch attention. Real-time display provides details about each alarm in list,
including alarm source, alarm level, alarm time, alarm content, alarm cause, alarm type,
and additional information.
Performance Management System

The performance management system provides statistic data about some performance
parameters and traffic data of the mobile system for reference to operation departments.
3-2
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 3 Operation and Maintenance
The maintenance terminal can define performance measurement tasks flexibly.

A performance measurement task includes the start/end time, duration in days,
measurement object set and granularity period. The maintenance terminal allows you to
create, delete, modify and observe the performance measurement tasks.
The performance measurement has a wide scope of content, ranging from traffic and
signaling performances, service quality measurement, network configuration verification,
availability measurement, throughput measurement and switching function measurement.
Diagnosis Test System

The diagnosis test system, a part of fault management, provides routine test and instant
test for the devices of the core network, to ensure normal and stable operation of the entire
system.
l
In daily maintenance, the diagnosis test system tests the physical devices and
communication links through routine test. If the test result is likely to be abnormal,
the system can raise the engineering personnels attention to take proper measures
to prevent fault from taking place.
In case of any fault, the diagnosis test system helps the engineering personnel find
the fault cause and locate the fault precisely through the instant test so as to remove
the fault as soon as possible.
After the fault is eliminated, this system can also help the engineering personnel to
judge whether the equipment and the entire system resumes normal operation.
The ZXUN iCX(MSCS) adopts a multi-module & fully distributed control structure.
Each module consists of a series of basic units. The diagnosis test function includes
intra-module test and inter-module test. The intra-module test is used to test the
functions of the component units of the module, links between the units and MPs, voice
channels between units and switching networks; the inter-module test is used to test the
communication and voice channels between the adjacent modules.
Signaling Trace System

The signaling trace system is used to trace the signaling data of the network operation and
to analyze the service operation.
ZXUN iCX(MSCS) signaling trace covers:
l
Tracing in real time and displaying signaling , such as MSC MAP/VLR MAP/HLR
MAP, SCCP/BSSAP/DTAP signaling at the A interface, RANAP/SCCP signaling at
the Iu-CS interface, TUP/ISUP signaling at the Ai interface, H.248 signaling at the Mc
interface and BICC signaling at the Nc interface.
Showing explanation for the signaling display.
Failure Observation System

The failure observation system, a part of the O&M system, is used to check the service
operation status of the NEs for analysis and processing in accordance.
3-3
SJ-20120730093520-002|2012-10-31 (R1.0)
It includes MSC failure observation, RANAP failure observation, VLR failure observation,
release of falsely occupied data area, service failure observation, and subscriber failure
observation.
Variable Management System

The variable management system maintains the service parameters that require dynamic
modification.
The variable management function modifies data on the background subsystem and
transfers them to synchronize with the foreground subsystem, thus to achieve flexible
service parameter configuration.
The security variable system configures the following parameters:
l
l
l
l
l
System control parameters

Security parameters
Iu interface parameters
Call control parameters
CS domain NE configuration parameters
Security Management System

The OMM has an independent user management system. Users' permission can be
managed.
User roles include three levels: the power user role, operator role, and the supervisor role.
Users of different roles can be created.
Log Management System

The OMM system requires an advanced security level. All operations are recorded. A tool
is provided for querying the operations.
3.3 Charging Management Functions

The charging management parts comprises CU, charging operation terminal and charging
operation server.
The charging operation server allows the CS/PS configuration and processing in a
centralized way. The charging mechanism provides the charging functions based on
contents, traffic, QoS, and services. This charging system uses a dual-server cluster,
which avoids the possible faults in operating. Various interfaces are provided. By using
the X.25 and TCP protocols, file transmission in FTP and FTAM modes are supported.
3-4
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 4
Services and Functions

Table of Contents
Mobility Management Service.....................................................................................4-1
Relocation and Handover Service ..............................................................................4-1
Mobile Call Service.....................................................................................................4-2
Supplementary Service ..............................................................................................4-3
Short Message Service ..............................................................................................4-4
Mobile Data Service ...................................................................................................4-5
Mobile Intelligent Service............................................................................................4-5
Location Service.........................................................................................................4-5
Multimedia Ring Back Tone Service ...........................................................................4-5
Enhanced IMEI Check Function .................................................................................4-6
Load-Based Switching Function ................................................................................4-6
Iu-CS/A over IP ..........................................................................................................4-6
4.1 Mobility Management Service

The location of a mobile subscriber always changes due to mobility of the subscriber. To
obtain location information of mobile subscribers during processing of call service, SMS
and supplementary services and meanwhile to improve valid utility of radio resources,
mobile subscribers must register their location information and report activity status on
network, that is, subscribers must originate location update service.
Location update service falls into the following three categories:
l
l
l
General location update: Used for registering new location information on the network.
It can be further divided into three types: VLR location update, GPRS location update
and joint location update.
Periodic location update: Used for periodically notifying network of the availability of
mobile subscribers.
IMSI (GPRS) attachment/detachment: Used for indicating attachment or detachment
of IMSI subscriber status.
4.2 Relocation and Handover Service

When a mobile subscriber moves to a boundary area of two cells, if BTS detects that
signal of mobile subscriber is too weak, BS will automatically initiate a relocation request
to MSC/VLR and perform relocation, to sustain existing service.
4-1
SJ-20120730093520-002|2012-10-31 (R1.0)
Related Concepts
Relocation or handover between different BSs within an MSCS is called intra-MSCS
relocation or handover. Relocation or handover between different MSCSs is called
inter-MSCS external relocation or handover.
According to the criterion whether there is a subsequent relocation or handover after a
relocation or handover, external relocation or handover between MSCSs can be divided
into two types: basic relocation or handover and subsequent relocation or handover.
Category (Based on System Type of Relocation or Handover)

Relocation or handover can be divided into 4 types according to system type:
l
l
l
l
Intra-system handover from GSM to GSM: Includes intra-office handover and

inter-office handover.
Inter-system relocation or handover from GSM to UMTS: Includes intra-office
relocation or handover and inter-office relocation or handover.
Inter-system relocation or handover from UMTS to GSM: Includes intra-office
relocation or handover and inter-office relocation or handover.
Intra-system relocation from UMTS to UMTS: Includes intra-office relocation and
inter-office relocation.
Category (Based on Whether the Circuit is Established)

Relocation or handover can be divided into 4 types according to whether the circuit is
established:
l
l
l
l
Basic relocation or handover with a circuit

Basic relocation or handover without a circuit
Subsequent relocation or handover with a circuit
Subsequent relocation or handover without a circuit
Major difference between relocation without a circuit and relocation with a circuit is that
whether bearer planes are set up in MSCS A and MSCS B before or after relocation. If
circuit is set up before relocation, it is called relocation with a circuit; otherwise, it is called
relocation without a circuit.
During relocation without a circuit, MS has been relocated to MSCS/VLR-B. However,
bearer plane between MSCS/VLR-A and MSCS/VLR-B has not been set up.
Subsequent relocation or handover can also be further divided into following types:
l
l
l
Subsequent relocation or handover handed over back to the MSCS A.

Relocation or handover handed over to the third party MSCS B
Relocation or handover handed over to the internal MSCS B.
4.3 Mobile Call Service

Mobile call service contains local call, outgoing call, incoming call and tandem call.
4-2
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 4 Services and Functions
Local calls are supported by the signaling system similar to ISDN (Call control signaling
differs from that specified in Q.931 but works in the same logic. Lower layer transmission
signaling used is different from that for ISDN).
Outgoing call, incoming call and tandem call are supported by inter-office signaling that is
divided into Channel Associated Signaling (CAS) and Common Channel Signaling (CCS).
4.4 Supplementary Service

Supplementary services are supplements and modifications to basic services. They allow
subscribers to modify incoming/outgoing call processing by network according to their own
requirements, or to provide subscribers with some kinds of information via network, so that
subscribers can make use of some conventional services on an intelligent basis.
The CS-related supplementary services in UMTS contain 21 types of 9 categories, refer
to Table 4-1.
Table 4-1 UMTS Supplement Services
Number
Category
Number identification
Type
Abbreviation
Calling line identification
CLIP
presentation
2
Calling line identification restriction
CLIR
Connected line identification
COLP
presentation
4
Connected line identification
COLR
restriction
5
Call forwarding unconditional
CFU
Call forwarding on busy
CFB
Call Forwarding on No Reply
CFNRy
Call forwarding on mobile subscriber
CFNRc
Call Forwarding
not reachable
9
Call completion
10
Call waiting
CW
HOLD
HOLD
11
Multiparty Service
Multiparty Service
MPTY
12
Closed user group
Closed user group
CUG
13
Advice of charge
Advice of charge (information)
AOCI
Advice of charge (charging)
AOCC
14
4-3
SJ-20120730093520-002|2012-10-31 (R1.0)
Number
Category
Type
Abbreviation
15
Call barring
Barring of All Outgoing Calls
BAOC
Barring of Outgoing International
BOIC
16
Calls
17
Barring of Outgoing International
BOIC-Exhc
Calls except those directed to the

home PLMN
18
Barring of All Incoming Calls
BAIC
19
Barring of Incoming Calls when
BIC-Roam
Roaming outside the home PLMN

country
20
Explicit call transfer
Explicit call transfer
ECT
21
Call deflection
Call deflection
CD
In the ZXUN iCX(MSCS), functional blocks involving supplementary services fall into
two major categories. The first category refers to basic operations of supplementary
services such as provision and register. The second category refers to supplementary
and modification functions to basic services by supplementary services, including such
functions as call-relevant supplementary services, call-irrelevant supplementary services,
and password management.
4.5 Short Message Service

SMS falls into two parts: Point-to-point SMS and broadcast SMS. However, only
point-to-point SMS is involved in mobile switching center.
Point-to-point SMS is a service to transmit length-limited messages between UMTS PLMN
mobile stations and Short Message Entity (SME) through a Short Center (SC). SC can
store and forward messages, constituting a short message processing entity that integrates
storing, exchanging and trunk functions. However, function of UMTS PLMN is to support
short message transfer between SC and MSs.
Point-to-point SMS falls into mobile-originated short message (SM MO) and
mobile-terminated short message (SM MT). SM MO means MS sends short messages to
SC, and these messages may also be sent to other MSs or subscribers of fixed network.
SM MT means the SC forwards short messages to MS, and these messages may come
from MS (SM MO), voice channel, telegraph, or fax.
Point-to-point SMS processing flows are divided into three parts:
l
l
l
SM MO processing flow SM
MT processing flow
Transmission of alert messages
The ZXUN iCX(MSCS) supports the above flows.

4-4
SJ-20120730093520-002|2012-10-31 (R1.0)
4.6 Mobile Data Service

The ZXUN iCX(MSCS) product provides the data service function.
Mobile data service is implemented by inter-working unit of the MGW, and the MSCS
invokes it based on provision and subscriber-originated service. All data services can be
provided, covering G3/G4 fax, intelligent telegraph, videography, computer data, etc. The
system provides the circuit bearer service required in the UMTS protocols. In addition,
the system also supports inter-working with all kinds of networks such as PSTN, ISDN,
CSPDN, PSPDN, DDN and Internet.
4.7 Mobile Intelligent Service

The ZXUN iCX(MSCS) product provides the following mobile intelligent service.
l
l
l
l
l
l
l
l
l
MPPS(Mobile Pre-Paid Service)

MVPN(Moblie Virtual Private Network)
FNS(Familiar Numbers Service)
MAD(Mobile ADvertisement)
SCS(Specialized Charging Service)
MSP(Multiple Subscriber Profile)
MBKS(Mobile Bank Service)
BAS(Business Assistant Service)
Other mobile intelligent service, such as FPH(Freephone), CTD(Cell and Time
Distribution).
4.8 Location Service

The ZXUN iCX(MSCS) product provides the Location Service.
Location Service (LCS) is a kind of standard services provided for the convenient of
developing the services based on location. The LCS could obtain the geography location
information of MS and the precision of the information according to the alternation of the
LCS client, the LCS server and the target MS. Under the supporting platform of electric
map, it provides subscribers with the corresponding value-added service.
The mobile location service confirms the real location information (coordinate data of
longitude and latitude and cell information ) of a mobile subscriber according to the
cooperation between the mobile phone and the wireless network. So it could provide the
required services relevant to location and direction to the subscribers.
4.9 Multimedia Ring Back Tone Service

Multimedia Ring Back Tone (MRBT) service is a 3G CS service. This service is used by
the called subscriber. When a caller makes a video call to a called, the caller hears the
ring back tone instead of the common dialing tone. The called can set the favorite tones
by subscribing this service.
4-5
SJ-20120730093520-002|2012-10-31 (R1.0)
The ZXUN iCX(MSCS) MRBT service of full connection is supported.

For the full connection mode, video calls is connected through the MRBT. Both the caller
and the called are connected to the MRBT.
4.10 Enhanced IMEI Check Function

The enhanced IMEI check function is used to check the legality of a user device and the
legality of the user IMSI.
l
This function is used to prevent frauds or fix a user to a specific terminal. In some
cases, the carrier needs to fix a user to a specific terminal, for example, the carrier
provides a user with subsidy. Without this function, users can use other terminal by
inserting the SIM card to the new terminal.
This function can be used by the public safety department for analyzing illegal cases.
Both the IMEI and the IMSI are uploaded to the EIR. The EIR records users using the
IMSI and records terminals using the IMEI. Thus the relation between the user and
the terminal can be checked out.
Generally, when the IMEI check function is enabled, the IMEI is sent to the EIR. After EIR
checked the IMEI, it returns the related information to the ZXUN iCX(MSCS) system. The
ZXUN iCX(MSCS) system then decides whether to access the terminal to the network.
4.11 Load-Based Switching Function

During switching, the source service BSC A sends the cell ID and the cell load to the
destination BSC B. The BSC B saves the load information, and maintains a cell ID and the
corresponding load information list. When a UE is switched from the BSC B, this BSC B
can select a destination cell based on the load information. A cell of low load is selected.
Thus, the success rate for switching is increased.
Load-based switching can be implemented in 3G redirecting, between 2G networks, and
between a 2G network and a 3G network. This switching includes two steps which might
operate simultaneously:
l
Load information collecting: During switching, the source service BSC A sends the cell
ID and the cell load to the destination BSC B. The BSC B saves the load information,
and maintains a cell ID and the corresponding load information list.
Load-based switching: When a UE is switched from the BSC B, this BSC B can select
a destination cell based on the load information. A cell of low load will be selected.
4.12 Iu-CS/A over IP

There are two options for the transport layer for data streams over Iu-CS:
l
l
ATM-based transport
IP-based transport
There are two options for the transport layer for data streams over A:
4-6
SJ-20120730093520-002|2012-10-31 (R1.0)
l
l
TDM-based transport
IP-based transport
The advantages of the Iu-CS/A over IP are described as follows:

l
l
The operator can deploy an all IP network.

Because the IP bearer is easily managed, Iu-CS/A over IP can reduce the OPEX.
4-7
SJ-20120730093520-002|2012-10-31 (R1.0)
4-8
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 5
Networking Modes
Table of Contents
VMSCS/GMSCS Networking Mode ............................................................................5-1
TMSCS Networking Mode ..........................................................................................5-3
MGCF Networking Mode ............................................................................................5-4
Region Networking Mode ...........................................................................................5-5
Dual-Homing Networking Mode ..................................................................................5-6
MSC Pool Networking Mode.......................................................................................5-9
5.1 VMSCS/GMSCS Networking Mode

Descriptions
In the R4 phase, based on the principle of separating controlling from bearer, MSC NE
can be divided into the MSCS and the MGW. The MSCS is to implement service and call
control, while the MGW is to implement bearing functions. The MSCS can act as the Virtual
MSCS (VMSCS) to provide access for mobile subscribers. The MSCS can also act as the
Gateway MSCS (GMSCS) to interconnect with other networks, such as with PSTN. Also,
the MGW can also function as the MGW and the Gateway MGW (GMGW).
Networking model
For the VMSCS/GMSCS networking model, see Figure 5-1.
5-1
SJ-20120730093520-002|2012-10-31 (R1.0)
Figure 5-1 Networking of VMSCS/GMSCS
Real lines indicate bearer

connections, and dashed
lines indicate signaling

connections.
Interface Description 1 (as the VMSCS)

As a VMSCS, the MSCS provides interfaces with following NEs:
l
l
l
l
Iu/A interface with UTRAN/BSS, providing access for mobile subscribers. The
interface between the VMSCS and UTRAN is Iu interface, with the bottom layer
bearer being AAL5/ATM, where service and call related control signaling is borne.
The interface between VMSCS and BSS is A interface, with the bottom layer bearer
being TDM, where service and call related control signaling is borne.
MAP interface with SC, with the bottom layer bearer based on TDM, for transmitting
and receiving SMS-related signaling.
MAP interface with HLR, with the bottom layer bearer based on TDM, for obtaining
the routes of terminating subscribers.
CAP interface with SCP, with the bottom layer bearer based on TDM, for exchanging
with SCP when subscribers trigger intelligent services. In this case, the SSP function
is built in VMSCS.
Nc interface with GMSCS and other VMSCSs, with the bottom layer bearer based
on TDM/ATM/IP, for bearing semi-call signaling in case of inter-office calls, and fixed
network calling the mobile or mobile calling the fixed network, and for bearing BICC
signaling in R4 networking.
Mc interface with MGW, with the bottom layer bearer based on TDM/IP, for bearing
standard H.248 signaling. A MSCS can manage multiple MGWs.
Interface Description 2 (as the GMSCS)

As a GMSCS, the MSCS provides the following interfaces with the following NEs:
l
MAP interface with SC, with the bottom layer bearer based on TDM, for transmitting
and receiving SMS related signaling.
5-2
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 5 Networking Modes
l
l
l
l
MAP interface with HLR, with the bottom layer bearer based on TDM, for obtaining
routing information of the terminating subscribers.
CAP interface with SCP, with the bottom layer bearer based on TDM, for exchanging
with the SCP when subscribers trigger intelligent services. In this case, SSP function
is built in VMSCS.
Nc interface with GMSCS and other VMSCS, with the bottom layer bearer based on
TDM/ATM/IP, for bearing semi-call signaling when fixed subscribers call mobile ones
or mobile subscribers call fixed ones, and for bearing BICC signaling in R4 networking.
Mc interface with GMGW, with the bottom layer bearer based on ATM/IP, for bearing
standard H.248 signaling.
Ai interface with PSTN, with the bottom layer bearer based on TDM, for transmitting
inter-office TUP/ISUP signaling.
5.2 TMSCS Networking Mode

Descriptions
The MSCS can work as a TMSCS for networking. In the networking for a region, the
TMSCS can transfer the signaling of the MSCS in the local network to reduce the signaling
traffic between MSCSs in the region. It can also transfer the signaling routes between
regions.
Networking Model
For the TMSCS networking model, see Figure 5-2.
Figure 5-2 Networking of TMSCSs
5-3
SJ-20120730093520-002|2012-10-31 (R1.0)
Interface Description
As a TMSCS, the MSCS provides interfaces with the following NEs:
l
l
Mc interface with the TMGW, with the bottom layer based on ATM/IP.
Nc interface with the TMSCS of another region, with the bottom layer based on ATM/IP,
for transferring signaling traffic between regions.
5.3 MGCF Networking Mode

Descriptions
For the IMS system, one MGCF/IM-MGW must be configured to act as the interworking
gateway between the IMS network, and CS and PSTN networks. The MGCF can be
combined with the GMSCS or set separately.
Networking model
For the MGCF networking model, see Figure 5-3.
Figure 5-3 Networking of the MGCF
Interface Description
As a MGCF, the MSCS provides the following interfaces:
l
l
l
l
Mg interface: The MGCF connects to the CSCF through the Mg interface of the SIP
protocol.
Mj interface: The MGCF connects to the BGCF through the Mj interface of the SIP
protocol.
Nc interface: The MGCF connects to the R4 CS network through the Nc interface of
the BICC protocol.
Ai interface: The MGCF connects to the PSTN network through the Ai interface of the
ISUP protocol.
5-4
SJ-20120730093520-002|2012-10-31 (R1.0)
Mn interface: The MGCF connects to the IM-MGW through the Mn interface of the
H.248 protocol.
5.4 Region Networking Mode

Descriptions
In the R4 networking, a single MSC can be divided into control plane-based MSCS and
bearer plane-based MGW.
The MSCS is only to process signaling and services of mobile network control plane,
therefore, it is simple and centralized in function. As an independent device, the MSCS
improves capacity and integrity greatly if compared with bearing & controlling combined
in MSC. It can be positioned in regional or provincial office network to control multiple
small-capacity MGWs dispersed in local networks and to control the access of UTRANs
connected by MGWs.
For the 3G R4, the most apparent difference is that capacity and networking position of
the MSCS is beyond the limits of local network, and the MSCS can provide cross-region
management and virtual MSC concept.
The virtual MSCS is created to realize that one MSCS can manage different local networks.
One physical MSCS can be allocated with multiple virtual MSC/VLR numbers, and it will
be logically considered as multiple virtual MSCSs.
In R99, there are one or more MSCs in a local network, that is, the MSCs only manage
resources of one local network. In R4, a single MSCS can manage resources of multiple
local networks, see Figure 5-4.
One MSCS controls two local networks. In fact, the MSCS is required to be divided into
two virtual MSCSs, with one for each local network. Each local network can maintain
its own virtual MSCS. The billing, performance statistics and configuration management
can embody the concept of having multiple local networks. The alarm can be reported to
the software/hardware alarm box of the local network maintenance point according to the
virtual MSCS. This is the authority division and area division function.
5-5
SJ-20120730093520-002|2012-10-31 (R1.0)
Figure 5-4 Region Networking
Functions
The ZXUN iCX(MSCS) supports the following region network functions:
l
l
l
l
In one MSCS, different VLR numbers and their corresponding MSC numbers and
MSRN kilo-digit number sections can be set according to subscriber location.
For the intra-VLR location update between different location areas within same VLR
area, location update is not initiated to HLR.
For the inter-VLR location update within the same MSCS, location update is initiated
to HLR.
Supports special services such as 119 in each local network.
5.5 Dual-Homing Networking Mode

Descriptions
Centralized management of subscriber information and service control depends on high
reliability of network . Therefore, for a great-capacity MSCS , its reliability needs to be
improved, otherwise, its collapse will bring tremendous impact.
Besides enhancing MSCS in reliability, different networking modes can be adopted to
improve reliability of network.
The dual-home networking can provide remote disaster recovery function for the MSCS.
For two MSCSs mutually homing to each other, when one MSCS suffers from faults , the
other MSCS will take over the services of the MSCS to ensure the service uninterrupted .
When the faults in the previously active MSCS are eliminated, switch over to the previous
active MSCS .
ZXUN iCX(MSCS) fully supports the dual-homing networking modes when it serves as an
end office, gateway office, and a tandem office.
5-6
SJ-20120730093520-002|2012-10-31 (R1.0)
Working Mode
The working mode of the dual-homing networking mode is divided into four types according
to the working status of the standby NE: 1+1 active/standby mode, N+1 active/standby
mode, 1+1 mutual backup mode, and N+1 mutual backup mode.
l
1+1 active/standby mode

In this mode, the active MSCS is responsible for processing all the services, and the
standby one is idle without processing any service. The standby MSCS monitors the
status of the active one all the time, will immediately take over the services of the
active one when there is something wrong with the active one, and will become the
active MSCS. For the networking, see Figure 5-5.
Figure 5-5 1+1 Active/Standby-Mode Networking
N+1 active/standby mode

In this mode, one standby MSCS monitors the statuses of N active ones all the time.
If there is something wrong with one active MSCS, the standby one will immediately
take over the services of the exceptional MSCS. The N+1 active/standby mode only
supports the situation where only one MSCS is faulty. For the networking, see Figure
5-6.
5-7
SJ-20120730093520-002|2012-10-31 (R1.0)
Figure 5-6 N+1 Active/Standby-Mode Networking
1+1 mutual backup mode

In this mode, two MSCSs process services during normal working. Both MSCSs
monitor status of each other all the time, and are ready to take over the services
of the other NE in case the other NE is faulty and processes its own services at the
same time. For the networking, see Figure 5-7.
Figure 5-7 1+1 Mutual-Backup-Mode Networking
N+1 mutual backup mode

In this mode, the disaster recovery MSCS processes the services of the local office,
and monitors the statuses of N active MSCSs. If any of these active MSCSs fails, the
disaster recovery MSCS will immediately take over the services of the faulty MSCS.
For the networking, see Figure 5-8.
5-8
SJ-20120730093520-002|2012-10-31 (R1.0)
Figure 5-8 N+1 Mutual-Backup-Mode Networking
5.6 MSC Pool Networking Mode

Description
The MSC Pool networking mode is a new networking mode, which breaks the restriction
that one BSC/RNC can connect with only one serving MSCS in the traditional network.
In the MSC Pool networking, one BSC/RNC can connect with multiple serving MSCS
Servers. These serving MSCS Servers composes one resource pool, providing services
to the connected BSC/RNC.
Networking Mode
In the MSC Pool networking, the signaling from one BSC/RNC to multiple MSCSs is
accessible, and all MSCSs in a MSC Pool together serve all BSC/RNCs in this MSC Pool.
The BSC/RNC can switch the signaling to each MSCS in the MSC Pool through one MGW,
see Figure 5-9. The BSC/RNC can connect to each MGW in the MSC Pool to transfer
signaling to the corresponding MSCS, see Figure 5-10.
5-9
SJ-20120730093520-002|2012-10-31 (R1.0)
Figure 5-9 MSC Pool Networking Mode (1)
Figure 5-10 MSC Pool Networking Mode (2)
5-10
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 6
Interfaces and Protocols

Table of Contents
Introduction to Interfaces ............................................................................................6-1
Iu-CS Interface ...........................................................................................................6-3
A Interface..................................................................................................................6-4
Mc Interface ...............................................................................................................6-5
Mn Interface ...............................................................................................................6-5
Nc Interface................................................................................................................6-6
MAP Interface ............................................................................................................6-7
CAP Interface.............................................................................................................6-7
Gs Interface ...............................................................................................................6-8
Mj/Mg Interface ..........................................................................................................6-9
Billing Interface...........................................................................................................6-9
O&M Interface ..........................................................................................................6-10
6.1 Introduction to Interfaces

Function Description
The ZXUN iCX(MSCS) product is embedded with the VLR and SG functions, and
integrated with the SSP function. Therefore, in the mobile communication network, the
ZXUN iCX(MSCS) can act as the following NEs at the same time:
l
l
l
l
l
l
VMSCS: responsible for processing MO and MT traffic, roaming and relocation traffic,
SMS, supplementary service unrelated with calls, and location-based services of the
MS under its coverage.
GMSCS: responsible for processing traffic between a PLMN and other PLMNs, PSTN
and ISDN networks.
TMSCS: responsible for processing tandem traffic in a PLMN.
MGCF: responsible for processing traffic between the IMS and the CS/PSTN.
SC/GMSCS: responsible for processing MO-SMS and MT-SMS traffic between a
PLMN and other a SC.
SSP: responsible for accessing the mobile Intelligent Network (IN), implementing the
service switching function and processing the intelligent services.
Interface Schematic Diagram

For the main interfaces of ZXUN iCX(MSCS) product in the mobile communication network,
see Figure 6-1.
6-1
SJ-20120730093520-002|2012-10-31 (R1.0)
Figure 6-1 Main Interfaces of ZXUN iCX(MSCS) Product
Interface
For the main interfaces of the ZXUN iCX(MSCS), refer to Table 6-1.
Table 6-1 Main Interfaces
Interface Type
Description
Iu-CS
It is the interface between the RNC and the MSCS/VLR . It supports the
RNC access.
It is the interface between the BSC and the MSCS/VLR . It supports the
BSC access and is responsible for control plane processing of the 2G call
service.
Mc
It is the interface between the MSCS and the MGW . It applies for, releases
and changes MGW bearer resources.
Mn
It is the interface between the MGCF and the IM-MGW. It controls the
bearer resources of the IM-MGW.
Nc
It is the interface between the MSCS and (G)MSCS. It negotiates call

parameters of outgoing call services and controls bearer resources.
MAP
It is the interface between the MSCS/VLR and the HLR. It implements

location update, subscriber data insertion, supplementary service
processing and MT call routing.
CAP
It is the interface between the MSCS/VLR/SSP and the SCP. It implements

intelligent service access and control, supplementary service invoking
notification, and mobility management notification.
Gs
It is the interface between the MSCS/VLR and the SGSN. It implements

the combined united location update of the subscriber, and the association
of the CS and PS domains.
6-2
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 6 Interfaces and Protocols
Interface Type
Description
Mj/Mg
It is the interface between the MGCF and the BGCF/CSCF. It negotiates

call parameters of the call between the IMS and the CS, and controls
bearer resources.
Billing interface (not
It sends the CDRs of the ZXUN iCX(MSCS) to the billing center.
shown in Figure 6-1)

O&M interface (not
It implements centralized maintenance, monitoring and network
shown in Figure 6-1)
management for the ZXUN iCX(MSCS).
6.2 Iu-CS Interface

Application
The Iu-CS interface is the interface between the ZXUN iCX(MSCS) and the RNC. From the
R4 phase, the control plane is separated from the bearer plane, so the MSCS only handles
the messages of the control plane of the Iu-CS interface. This interface implements the
mobility management of the user, RNC access, control plane handling of a call service and
SMS service.
In the R4 phase, the Iu-CS adopts the ATM bearer mode.
In R5 phase or the later phase, 3GPP protocol specifies that the Iu-CS interface could use
the ATM bearer mode or the IP bearer mode. That is to say, the IP bearer mode is added.
Protocol Stack
l
For the protocol stack of the control plane of the Iu-CS interface that based on ATM,
see Figure 6-2.
Figure 6-2 Protocol Stack of the Iu-CS Control Plane
For the protocol stack of the control plane of the Iu-CS interface that based on IP, see
Figure 6-3.
6-3
SJ-20120730093520-002|2012-10-31 (R1.0)
Figure 6-3 Protocol Stack of the Iu-CS Control Plane
The protocol stack of the Iu-CS interface control plane can adopt two modes:
l
l
For
ATM
signaling
transmission
mode,
RANAP/SCCP/MTP3B/SSCF-NNI/SSCOP/AAL5.
For
IP
signaling
transmission
mode,
RANAP/SCCP/M3UA/SCTP/IP.
the
the
protocol
stack
is
protocol
stack
is
6.3 A Interface
Application
The interface between the MSCS and the BSC is A interface. The MSCS only processes
the control plane of the A interface. This interface implements subscriber mobility
management, BSS access, control plane processing of call service and SMS service.
This interface is physically based on TDM or IP.
Protocol Stack
For the protocol stack of the A interface, see Figure 6-4.
Figure 6-4 Protocol Stack of the A Interface Control Plane
The protocol stack of the A interface control plane can adopt two modes:
6-4
SJ-20120730093520-002|2012-10-31 (R1.0)
l
l
For narrowband SS7 signaling transmission mode, the protocol stack is

BSSAP/SCCP/MTP3/MTP2.
For SIGTRAN signaling transmission mode,
the protocol stack is
BSSAP/SCCP/M3UA/SCTP/IP.
6.4 Mc Interface
Application
The interface between the MSCS and the MGW is Mc interface. This interface can be
based on ATM or IP.
Protocol Stack
For the protocol stack of the Mc interface, see Figure 6-5.
Figure 6-5 Mc Interface Protocol Stack
The protocol stack of the Mc interface can adopt three modes.

l
l
l
For pure IP signaling transmission mode, H.248/SCTP/IP is preferred, and

H.248/M3UA/SCTP/IP is optional.
For ATM/IP mixed signaling transmission mode, H.248/M3UA/SCTP/IP is preferred,
and H.248/MTP3B/SSCF/SSCOP is optional.
For pure ATM signaling transmission mode, H.248/MTP3B/SSCF/SSCOP is selected.
6.5 Mn Interface
Application
The Mn interface between the MGCF and the IM-MGW is based on IP transmission.
Protocol Stack
For the protocol stack of the Mn interface, see Figure 6-6.
6-5
SJ-20120730093520-002|2012-10-31 (R1.0)
Figure 6-6 Protocol Stack of the Mn Interface
The protocol stack of the Mn interface can adopt two modes.

l
l
For pure IP links, H.248/SCTP/IP is preferred, and H.248/M3UA/SCTP/IP is optional.

For non-pure IP links, the protocol stack is H.248/M3UA/SCTP/IP.
6.6 Nc Interface
Application
The interface between MSCS and (G)MSCS is Nc Interface. This interface can be based
on ATM, IP or TDM.
Protocol Stack
For the protocol stack of the Nc interface, see Figure 6-7.
Figure 6-7 Protocol Stack of the Nc Interface
The protocol stack of the Nc interface can adopt three modes:

l
l
l

BICC/MTP3/MTP2.
BICC/M3UA/SCTP/IP.
For
ATM
signaling
transmission
mode,
the
protocol
stack
is
BICC/MTP3B/SSCF-NNI/SSCOP/AAL5.
6-6
SJ-20120730093520-002|2012-10-31 (R1.0)
6.7 MAP Interface

Application
The MAP interface is used for multiple interfaces, including:
l
l
l
l
C interface (interface between the GMSCS and the HLR)

D interface (interface between the VLR and the HLR)
E interface (interface between the MSCS and the SMC or between the MSCS and the
MSCS)
G interface (interface between VLRs)
This interface can be physically based on TDM or IP.
Protocol Stack
For the protocol stack of the MAP interface, see Figure 6-8.
Figure 6-8 Protocol Stack of the Map Interface
The protocol stack of the MAP interface can adopt two modes:
l
l

MAP/TCAP/SCCP/MTP3/MTP2.
MAP/TCAP/SCCP/M3UA/SCTP/IP.
6.8 CAP Interface

Application
The CAP interface implements transaction interaction between CAP entities, and is
physically based on TDM or IP interfaces. The CAP interface is used for the following
interfaces:
l
Interface between the SSP and the SCP (Completing mobile service access and call
control)
6-7
SJ-20120730093520-002|2012-10-31 (R1.0)
Independent IP-SCP interface (Completing the interaction between the subscriber and
the CSE).
Protocol Stack
For the protocol stack of the CAP interface, see Figure 6-9.
Figure 6-9 Protocol Stack of the Cap Interface
The protocol stack of the CAP interface can adopt two modes:
l
l

CAP/TCAP/SCCP/MTP3/MTP2.
CAP/TCAP/SCCP/M3UA/SCTP/IP.
6.9 Gs Interface
Application
The interface between the VLR and the SGSN is Gs interface. The Gs interface is used to
complete combined location update, paging and TMSI assignment in the CS/PS domain.
The Gs interface is based on TDM or IP interfaces physically.
Protocol Stack
For the protocol stack of the Gs interface, see Figure 6-10.
6-8
SJ-20120730093520-002|2012-10-31 (R1.0)
Figure 6-10 Protocol Stack of the Gs Interface
The protocol stack of the Gs interface can adopt two modes:

l
l

BSSAP+/SCCP/MTP3/MTP2.
BSSAP+/SCCP/M3UA/SCTP/IP.
6.10 Mj/Mg Interface

Application
The interface between the MGCF and the BGCF is Mj interface. The interface between
the MGCF and the CSCF is Mg interface. Through the Mj and Mg interfaces, interworking
between the CS domain and the IMS domain can be implemented. The signaling protocol
stack of the Mj/Mg interface is based on SIP.
Protocol Stack
For the protocol stack of the Mj/Mg interface, see Figure 6-11.
Figure 6-11 Protocol Stack of the Mj/Mg Interface
The protocol stack of the Mj/Mg interface is based on IP transmission, and can be over
UDP/TCP/SCTP.
6.11 Billing Interface

The billing interface is an internal interface.
6-9
SJ-20120730093520-002|2012-10-31 (R1.0)
The ZXUN iCX(MSCS) sends CDRs to the billing server through it, whose bottom layer
adopts the TCP/IP protocol for communication.
6.12 O&M Interface

Application
The OMM system of the ZXUN iCX(MSCS) adopts the TMN architecture, and its interfaces
include N interface, client-oriented MML interface and interface between the OMM system
and the ZXUN iCX(MSCS) NE.
l
l
The N interface describes such application protocols as CORBA/SNMP, to implement

interconnection between the OMM system and the NMC .
As an interface between the LMT and the OMM server, the MML interface describes
commands and command responses in text format between the LMT and the OMM
server.
The internal message interface or SNMP protocol interface is used between the OMM
server and the ZXUN iCX(MSCS) NE.
The O&M interface adapts IP protocol and the bottom communication is over the TCP/IP.
Protocol Architecture
For the structure of O&M interface, see Figure 6-12.
Figure 6-12 Structure of O&M Interface
6-10
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 7
Networking Specifications
Table of Contents
Physical Indices .........................................................................................................7-1
Performance Indices ..................................................................................................7-1
Power Consumption ...................................................................................................7-2
Clock Indices..............................................................................................................7-3
Reliability Indices .......................................................................................................7-4
Equipment Power Indices...........................................................................................7-4
Interface Types...........................................................................................................7-4
Modules and Units Indices .........................................................................................7-5
7.1 Physical Indices

For the physical indices of the cabinet, refer to Table 7-1.
Table 7-1 Physical Indices of the Cabinet
Parameter
Indices
Dimensions
2,200 mm (H) 600 mm (W) 800 mm (D)
Capability
The cabinet adopts a 19-inch cabinet structure, which has a

maximum internal space of 47 U.
Overall Weight
The weight of one cabinet in full configuration is less than or equal

to 350 kg.
Weight Bearing
The weight bearing requirement of the equipment room floor is

greater than 420 kg/m2.
7.2 Performance Indices

For the performance indices of the ZXUN iCX(MSCS), refer to Table 7-2. For the reference
traffic models, refer to Table 7-3.
7-1
SJ-20120730093520-002|2012-10-31 (R1.0)
Table 7-2 Typical Performance Indices of the ZXUN iCX(MSCS)

Main Performance
Parameter
Detailed Technical Indices
Processing capacity
VMSCS office
51 M
GMSCS office
78 M
CMN office
164 M
MGCF office
82 M (without Rf interface)
(Maximum BHCA)
54 M (with Rf interface)
User capacity
VMSCS office
20 M
Signaling indices
Maximum of 64 kbps links
4096
Maximum of 2 Mbps links
256
Maximum of SCTP links
2048
Maximum GT translation capability
464,000 GTT/S
Maximum signaling point code
256
TDM E1
512
GE
10
Maximum supported adjacent number
2048
Maximum supported MGW number
256
Maximum supported RNC number
256
Maximum supported BSC number
256
Interface indices
Adjacent capacity
Table 7-3 Reference Traffic Models of the ZXUN iCX(MSCS)

Parameter
Detailed Technical Indices
Busy hour average traffic of mobile subscribers
0.025 Erl
Busy hour calling amount
1.5 times/subscriber
Busy hour average traffic of trunk
0.8 Erl
Busy hour average calling amount of trunk
42/busy hour/incoming call circuit
7.3 Power Consumption

For the power consumption of the ZXUN iCX(MSCS) parts, refers to Table 7-4.
Table 7-4 Power Consumption of Parts
Names of Parts
Typical Power Consumption (W)
E4140
<150 (including that of the backplane, fans, power, and NCMMs)
SWBB0
<empty load 45, full load 60

7-2
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 7 Networking Specifications
Names of Parts
Typical Power Consumption (W)
SWI1
<empty load 12, full load 15 (including DACM subcard)
SWBB1
<empty load 60, full load 70
SWI2
<15 (including DACM subcard)
GPBB0
<200
GPBX1
<300
GPI1
<15
SLB
<empty load 76, full load 83 (including rear board)
SLI
<2
Disk array
<300 (full configuration with 12 disks)
Switch
<55
KVMS
<40
7.4 Clock Indices

For the clock indices of the ZXUN iCX(MSCS), refer to Table 7-5.
Table 7-5 Clock Indices of the ZXUN iCX(MSCS)
Categroy
Parameter
Specific Indices
Clock synchronous
Clock level
Stratum 2 class A clock
performance
Clock synchronization mode
External clock synchronization, extracting

clock from service code streams, and
internal clock synchronization
Clock
synchronization
2 Mbits
2 clock synchronization interfaces
2 MHz
Line 8 k
interface
Lowest clock accuracy
4 10-7
Pull-in range
4 10-7
Maximum frequency deviation
10-9 /day
Initial maximum frequency
5 10-10
deviation
Clock working mode
Catch, Trace, Hold and Free
7-3
SJ-20120730093520-002|2012-10-31 (R1.0)
Categroy
Parameter
Specific Indices
Time synchronous
Protocol
NTP/SNTP
Time synchronous precision
100 ms
Time synchronous interface
GE
Interface number
performance
7.5 Reliability Indices

For the reliability indices of the ZXUN iCX(MSCS), refer to Table 7-6.
Table 7-6 Reliability Indices of the ZXUN iCX(MSCS)
Parameter
Specific Indices
Basic failure rate
0.0000013/h
Mean Time Between Failures (MTBF)
91 year
Mean Time to Repair (MTTR)
<1 h
System availability
>99.9999 %
Annual average interruption duration
<1 min
7.6 Equipment Power Indices

For the power indices of the ZXUN iCX(MSCS), refer to Table 7-7.
Table 7-7 Power Indices of the ZXUN iCX(MSCS)
Parameters
Indices
Rated voltage
-48 V or -60 V
Voltage fluctuation range
-57 V~-40 V or -72 V~-50

V
Maximum power consumption (W) (One shelf with full configuration)
2,230 W
Heat dissipation capacity (W) (One rack with full configuration)
4,500 W
7.7 Interface Types

For the adopted standards and supported cable types of the ZXUN iCX(MSCS), refer to
Table 7-8.
7-4
SJ-20120730093520-002|2012-10-31 (R1.0)
Table 7-8 Adopted Standards and Supported Cable Types of the ZXUN iCX(MSCS)
Interfaces
Interface Type
Physical Standards
Cable Types
Narrowband SS7 signaling interface
E1/T1
Coaxial cable
SIGTRAN signaling interface
1000 Mbps Ethernet
Category-5 twisted pair
NM interface
100/1000 Mbps Ethernet
Billing interface
100/1000 Mbps Ethernet
Synchronous clock interface
E1/T1
Coaxial cable
7.8 Modules and Units Indices

7.8.1 Indices of Billing Module
Main function
The billing module of the ZXUN iCX(MSCS) collects CDRs and sends them to the billing
center. If the transmission link is interrupted, the collected CDRs can be buffered on the
hard disk of the service processor. After the transmission link is restored, the buffered
CDRs can be transmitted to the billing center in time.
Indices
For the indices of the billing module, refer to Table 7-9.
Table 7-9 Indices of Billing Module
Parameter
Specific Indices
Online CDR storage capability
More than 7 days, and the specific capability

is determined according to the capacity of the
storage device.
CDR storage capacity
300 GB
Maximum MP CDR storage capacity when the link
300 GB
between the foreground and the background is

broken
Maximum number of the CDRs stored
>30 M CDRs
CDR processing capability
64,000 CDRs/s
Interfaces and protocols
FTP/FTAM
Billing interface
GE
Number of interfaces
Basic configuration 2, 4 expansible
CDR format
ASN.1
7-5
SJ-20120730093520-002|2012-10-31 (R1.0)
Parameter
Specific Indices
Duration unit of the original CDR
0.1 s
Billing duration error of the original CDR
<1 s
Minimum time interval for outputting middle CDRs
15 min
7.8.2 Indices of Power Module

For the indices of the power module, refer to Table 7-10.
Table 7-10 Power Module Indices
Checked Item
DC Power of the Switch
Nominal value (V)
-48 V or -60 V
Voltage range (V)
-57 V~-40 V or -72 V~-50 V
Noise voltage
0 ~ 300 Hz
100 mV (peak-peak value)
300 Hz ~ 3400 Hz
2 mV (noise meter weighting noise)
3.4 kHz ~ 150 kHz
Single frequency 5 mV (valid value); broadband

100 mV (valid value)
150 kHz ~ 200 kHz

100 mV (valid value)
200 kHz ~ 500 kHz

30 mV (valid value)
500 kHz ~ 30 MHz

30 mV (valid value)
7.8.3 Indices of Monitoring Module

For the technical indices of the environmental parameter monitoring module, refer to Table
7-11.
Table 7-11 Technical Indices of the Monitoring Module
Checked Item
Range
Smoke sensor alarm protection
60 square meters/sensor
range
Infrared alarm protection range
15 m radius 90sector/sensor
Flooding alarm detection range
10 mm~1000 mm
Temperature detection range
0 ~+50 (frequency output: 1 kHz ~1.5 kHz), with the

measurement precision being 0.50C
7-6
SJ-20120730093520-002|2012-10-31 (R1.0)
Checked Item
Range
Humidity detection range
20 % ~ 100 % (frequency output: 1 kHz ~ 2 kHz, corresponding

to 0 % ~ 100 %), with a measurement precision of 3 %
Fan rev detection range
0 revolution per minute ~ 5000 revolutions per minute, with a

measurement precision of 1 %
Temperature upper limit alarm
Can be set by the program (by default, it is 30 ).
Temperature lower limit alarm
Can be set by the program (by default, it is 15 ).
Humidity upper limit alarm
Can be set by the program (by default, it is 60 %).
Humidity lower limit alarm
Can be set by the program (by default, it is 45 %).
-48 V power upper limit alarm
Can be set by the program (by default, it is -57 V), with a

measurement precision of 2 % .
-48 V power lower limit alarm

measurement precision of 2 %.
-60 V power upper limit alarm

measurement precision of 2 % .
-60 V power lower limit alarm

measurement precision of 2 %.
Fan rev alarm
Can be set by the program (by default, it is 80 % of the rated

rev) .
7.8.4 Indices of Fan Unit

For the indices of the fan unit, refer to Table 7-12.
Table 7-12 Technical Indices of the Fan Unit
Checked Item
Range
Input voltage
-48 V or -60 V
Input current
2A
Power
MAX 105 W
Blast volume
600.6 CFM
Blast pressure
35.87 mmH2O
Rev
5,500 rpm
Noise
66.5 dBA
Life span
70,000 h
Environment
-10 ~ +75
7-7
SJ-20120730093520-002|2012-10-31 (R1.0)
7.8.5 Indices of Alarm Box

Description
Generally, the alarm box is installed on the wall of the maintenance or monitoring
equipment room, and is connected to the background operation and maintenance system
through Ethernet, facilitating the on-duty personnel to view and operate it.
Outside View
For the alarm box outlook, see Figure 7-1.
Figure 7-1 Alarm Box Outlook
Dimensions
The outline dimensions of the alarm box is 323 mm 220 mm 58 mm (height width
depth).
Weight
The weight of an alarm box is 2 kg.
7-8
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 8
Environmental Requirements
Table of Contents
Grounding Requirements ...........................................................................................8-1
Temperature and Humidity Requirements...................................................................8-1
Cleanness Requirements ...........................................................................................8-2
Air Pollution Requirements .........................................................................................8-2
8.1 Grounding Requirements

Types of grounding cables
There are three types of grounding cables, which are:
l
l
l
-48 VGND (-48 V ground ) or -60 VGND (-60 V ground )

GNDP (System protection ground)
GND (Working ground)
Grounding mode
The ZXUN iCX(MSCS) adopts the joint grounding mode, which is described as follows:
l
l
GNDP and GND are connected with shelves through mechanical parts inside the
shelves, and with the DC grounding stake through the bus bar.
-48 VGND or -60 VGND cable is provided through the primary power supply and is
not connected with the GNDP, GND and the rack inside the rack .
Grounding resistance
The grounding resistance of the ZXUN iCX(MSCS) should be less than 1 .
8.2 Temperature and Humidity Requirements

For the temperature and humidity requirements of the ZXUN iCX(MSCS), refer to Table
8-1.
Table 8-1 Temperature and Humidity Requirements
Items
Long-term working Condition
Short-term working Condition
Temperature
0 to 45
-5 to 55
Relative Humidity
5 % to 90 %
5 % to 95 %
8-1
SJ-20120730093520-002|2012-10-31 (R1.0)
8.3 Cleanness Requirements

For a dust particle with a diameter greater than 5 m, the concentration should be3104
particles/m3.
8.4 Air Pollution Requirements

There should be no explosive, conductive, magnetic or corrosive dust in the equipment
room. The equipment room should be free of gases that may corrode metal parts or
deteriorate insulation performance.
8-2
SJ-20120730093520-002|2012-10-31 (R1.0)
Chapter 9
Compliance Standard
ZXUN iCX(MSCS) conforms strictly to the following standards.
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
Specifications for 3G mobile communication technology test equipment-UMTS core

network subsystem
3GPP R4 relevant protocols
3GPP R5 relevant protocols
General Technical Specifications for 900MHz TDMA Digital Cellular Mobile
Communications System Equipment (Volume I) - Technical Specifications for
Switching System Equipment GF015.1-95
Technical Specifications for 900/1800MHz TDMA Digital Cellular Mobile
Communications Networks - Mobile Application Part (MAP)(Phase2+)
Technical Specifications of Signaling System SS7 for the National Telephone Network
of China (Interim Provisions) (GF001-900) and supplemental Specifications
of China - Transaction Capability Part (TC)
of China - Transaction Capability Application Part (TCAP)
of China - Signaling Connection Control Part (SCCP)
of China - Integrated Services User Part (ISUP)
of China - Mobile Application Part (MAP)
of China - 2Mbps/s High-Speed Signaling Links (Supplemental Provisions)
Supplemental Provisions for the Technical Specifications of STP Equipment for the
National Telephone Network of China (GF013-95)
ITU-T Q.720~Q.766 Signaling System SS7
ITU-T Q.400~Q.490 Signaling System R2
ITU-T I.36x ATM Interface Standard Protocol
ITU-T Q.2630.1 AAL type 2 Signaling Protocol
ITU-T Q.21xx ATM Broadband Signaling System
ITU-T H.248.x Signaling Protocol
ITU-T Q.1902.x Signaling Protocol
ITU-T Q.1950 Signaling Protocol
IETF RFC2960 SCTP Protocol
Load format for IETF RFC3267 RTP transmitting AMR and AMR-WB
IETF RFC3261 SIP Protocol and Its Expanded Protocols
9-1
SJ-20120730093520-002|2012-10-31 (R1.0)
9-2
SJ-20120730093520-002|2012-10-31 (R1.0)
Glossary
3GPP
- 3rd Generation Partnership Project
ATM
- Asynchronous Transfer Mode
BAIC
- Barring of All Incoming Calls
BAOC
- Barring of All Outgoing Calls
BGCF
- Breakout Gateway Control Function
BICC
- Bearer Independent Call Control protocol
BOIC
- Barring of Outgoing International Calls
BSC
- Base Station Controller
BSSAP
- Base Station Subsystem Application Part
CAMEL
- Customized Applications for Mobile Network Enhanced Logic
CAP
- CAMEL Application Part
CAS
- Channel Associated Signaling
CCS
- Common Channel Signaling
CD
- Call Deliver
CDR
- Call Detail Record
CFB
- Call Forwarding on Busy
CFNRc
- Call Forward No Reachable
I
SJ-20120730093520-002|2012-10-31 (R1.0)
CFNRy
- Call Forward No Reply
CFU
- Call Forwarding Unconditional
CLIP
- Calling Line Identification Presentation
CLIR
- Calling Line Identification Restriction
CN
- Core Network
COLP
- COnnected Line identification Presentation
COLR
- COnnected Line identification Restriction
CORBA
- Common Object Request Broker Architecture
CS
- Circuit Switched
CSCF
- Call Session Control Function
CSE
- CAMEL Service Environment
CTD
- Cell Transfer Delay
CUG
- Closed User Group supplementary service
CUG
- Closed User Group
EIR
- Equipment Identity Register
FPH
- Free phone
FTAM
- File Transfer Access and Management
FTP
- File Transfer Protocol
GGSN
- Gateway GPRS Support Node
II
SJ-20120730093520-002|2012-10-31 (R1.0)
Glossary
GMSC
- Gateway Mobile Switching Center
GPRS
- General Packet Radio Service
HDLC
- High-level Data Link Control
HLR
- Home Location Register
IM-MGW
- IP Multimedia-Media Gateway
IMEI
- International Mobile Equipment Identity
IMS
- IP Multimedia Subsystem
IMSI
- International Mobile Subscriber Identity
IP
- Internet Protocol
ISDN
- Integrated Services Digital Network
ISUP
- ISDN User Part
IW/GMSC
- InterWorking/Gateway MSC
LCS
- LoCation Services
MAP
- Mobile Application Part
MGCF
- MediaGateway Control Function
MO
- Mobile Originated
MPPS
- Mobile Pre-Paid Service
MPTY
- Multiparty
MRBT
- Multimedia Ring Back Tone
III
SJ-20120730093520-002|2012-10-31 (R1.0)
MSCS
- Mobile Switching Center Server
MT
- Mobile Terminated
MVPN
- Moblie Virtual Private Network
NMC
- Network Management Center
NMS
- Network Management System
OMM
- Operation & Maintenance Module
OSS
- Operation Support System
PLMN
- Public Land Mobile Network
PSPDN
- Packet Switched Public Data Network
PSTN
- Public Switched Telephone Network
RANAP
- Radio Access Network Application Protocol
RISC
- Reduced Instrument Set Computer
RNC
- Radio Network Controller
RNS
- Radio Network Subsystem
SC
- Short Message Center
SCCP
- Signaling Connection Control Part
SCE
- Service Creation Environment
SCP
- Service Control Point
SCS
- Specialized Charging Service
IV
SJ-20120730093520-002|2012-10-31 (R1.0)
Glossary
SCTP
- Stream Control Transmission Protocol
SGSN
- Serving GPRS Support Node
SGW
- Signaling GateWay
SIM
- Subscriber Identity Module
SIP
- Session Initiation Protocol
SMP
- Service Management Point
SMS
- Short Message Service
SNMP
- Simple Network Management Protocol
SS7
- Signaling System No. 7
SSP
- Service Switching Point
TCP
- Transfer Control Protocol
TDM
- Time Division Multiplexing
TMN
- Telecommunications Management Network
TMSC
- Tandem MSC
TUP
- Telephone User part
UDP
- User Datagram Protocol
UE
- User Equipment
UMTS
- Universal Mobile Telecommunication System
UTRAN
- Universal Terrestrial Radio Access Network
V
SJ-20120730093520-002|2012-10-31 (R1.0)
VLR
- Visitor Location Register
VMSC
- Visited Mobile Switching Center
VI
SJ-20120730093520-002|2012-10-31 (R1.0)

SJ-20120730093520-002-ZXUN ICX (MSCS) (V4.12.10) MSC Server Product Description

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

SJ-20120730093520-002-ZXUN ICX (MSCS) (V4.12.10) MSC Server Product Description

Caricato da

Copyright:

Formati disponibili

ZXUN iCX(MSCS)

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

Serial Number: SJ-20120730093520-002

ZTE Proprietary and Confidential

Chapter 2 Product Architecture ................................................................ 2-1

Chapter 3 Operation and Maintenance..................................................... 3-1

Chapter 4 Services and Functions............................................................ 4-1

Chapter 5 Networking Modes .................................................................... 5-1

ZTE Proprietary and Confidential

Chapter 6 Interfaces and Protocols .......................................................... 6-1

Chapter 7 Networking Specifications ....................................................... 7-1

Chapter 8 Environmental Requirements .................................................. 8-1

Chapter 9 Compliance Standard ............................................................... 9-1

ZTE Proprietary and Confidential

About This Manual

Network planning engineers

Prerequisite Skill and Knowledge

What Is in This Manual

1, Production Positioning and

Describes the network position, role, and features of the ZXUN

Describes the hardware architecture and software architecture of

3, Operation and Maintenance

Describes the operation and maintenance of the ZXUN iCX(MSCS).

4, Services and Functions

Describes the services and functions of the ZXUN iCX(MSCS).

Describes the networking modes of the ZXUN iCX(MSCS).

6, Interfaces and Protocols

Describes the interfaces and protocols of the ZXUN iCX(MSCS).

Describes the networking specifications of the ZXUN iCX(MSCS),

Describes the environmental requirements of the ZXUN iCX(MSCS)

for grounding, temperature and humidity.

Describes the compliance standard of the ZXUN iCX(MSCS).

ZTE Proprietary and Confidential

ZXUN iCX(MSCS) MSC Server Signaling Description

FCC Compliance Statement

Separates individual parameter in series of parameters.

ZTE Proprietary and Confidential

Production Positioning and

1.1 Product Positioning

ZTE Proprietary and Confidential

ZXUN iCX(MSCS) Product Description

Position of the ZXUN iCX(MSCS) in the Network

1.2 Product Features

Advanced design philosophy

ZTE Proprietary and Confidential

Chapter 1 Production Positioning and Features

The ZXUN iCX(MSCS) product is designed strictly in accordance with 3GPP R4

Software development conforms strictly to software engineering design

All NEs are built on unified all-IP software/hardware platform.

Flexible networking capability

Series products can either integrate functions of VMSC Server,GMSC

System supports a wide variety of signaling interfaces such as China No.1

System supports multiple signaling points and 2 M high-speed signaling,

Built-in dynamic routing function makes IP networking much flexible.

The ZXUN iCX(MSCS) supports region networking function.

Powerful service functionalities

Providing roaming and mobility management, relocation processing,

Providing supplementary services, including call forward, call restriction, call

Providing CAMEL services such as pre-payment, virtual private networks, and

Supporting LCS services such as MO-LDR and MT-LDR.

ZTE Proprietary and Confidential

ZXUN iCX(MSCS) Product Description

Supporting interworking between IMS and CS.