SJ-20110412153554-002-ZXUN iMG (MGW - W) (V4.10.20) Media Gat

ZXUN iMG (MGW_W)
Media Gateway
Product Description
Version: V4.10.20
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 2011 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.2 2011-10-15 Update the section of 3.10
R1.1 2011-05-30 Added contents related to VIG.
R1.0 2011-04-30 First edition.
Serial Number: SJ-20110412153554-002
Publishing Date: 2011-10-15 (R1.2)

Contents
About This Manual ......................................................................................... I
Chapter 1 Product Overview ..................................................................... 1-1
1.1 Location of ZXUN iMG in a Network .................................................................... 1-1
1.2 Main Functions of ZXUN iMG.............................................................................. 1-2
1.3 ZXUN iMG Product Features............................................................................... 1-4
1.3.1 Unified ETCA Platform.............................................................................. 1-4
1.3.2 Strong Cascading Capability ..................................................................... 1-4
1.3.3 Variety of Physical Interfaces .................................................................... 1-6
1.3.4 Environmentally Friendly Design ............................................................... 1-7
1.3.5 Capability of Smooth Upgrade and Capacity Expansion.............................. 1-7
1.3.6 Excellent Reliability .................................................................................. 1-7
1.3.7 Manageability and Easy Maintenance........................................................ 1-8
1.4 ZXUN iMG Compliance Standard ........................................................................ 1-9
Chapter 2 System Architecture ................................................................. 2-1

2.1 Hardware Architecture ........................................................................................ 2-1
2.1.1 Physical Architecture ................................................................................ 2-1
2.1.2 Logical Architecture .................................................................................. 2-3
2.2 Software Architecture ......................................................................................... 2-5
Chapter 3 Interfaces ................................................................................... 3-1

3.1 Interface Overview ............................................................................................. 3-1
3.2 Iu-CS Interface................................................................................................... 3-2
3.2.1 Iu-CS Interface Based on ATM .................................................................. 3-3
3.2.2 Iu-CS Interface Based on IP...................................................................... 3-4
3.3 Mc Interface....................................................................................................... 3-5
3.4 Nb Interface ....................................................................................................... 3-6
3.5 A Interface ......................................................................................................... 3-8
3.6 Ai Interface ........................................................................................................ 3-8
3.7 Mn Interface....................................................................................................... 3-8
3.8 Mb Interface....................................................................................................... 3-9
3.9 Mp interface..................................................................................................... 3-10
3.10 O&M Interface................................................................................................ 3-10
3.10.1 OMM Interface ......................................................................................3-11
3.10.2 CORBA Interface.................................................................................. 3-12
I
3.10.3 SNMP Interface.................................................................................... 3-12
Chapter 4 Service Functions ..................................................................... 4-1

4.1 Introduction to Service Functions......................................................................... 4-1
4.2 Media Gateway Control Function ........................................................................ 4-2
4.2.1 Call-Related Service................................................................................. 4-2
4.2.2 Global Service ......................................................................................... 4-3
4.3 Bearer Control Function...................................................................................... 4-4
4.3.1 ATM Bearer Control.................................................................................. 4-4
4.3.2 IP Bearer Control ..................................................................................... 4-4
4.4 User Plane Processing Function.......................................................................... 4-5
4.4.1 Radio Network Layer Processing............................................................... 4-5
4.4.2 Non-Access Stratum Application ............................................................... 4-8
4.4.3 Bearer Function ....................................................................................... 4-9
4.4.4 Interworking Between the IM-MGW and the CS........................................ 4-10
4.4.5 Interworking Between the IM-MGW and the PSTN ................................... 4-12
4.4.6 MRFP Providing IMS AS with Tone Playing Function ................................ 4-12
4.4.7 VIG Implementing Video Interworking Between CS and IMS ..................... 4-13
4.5 Built-in Signaling Gateway Function................................................................... 4-13
4.6 VMGW Function............................................................................................... 4-14
Chapter 5 Networking Applications.......................................................... 5-1

5.1 Networking Modes.............................................................................................. 5-1
5.2 Networking as an End Office (VMGW) ................................................................. 5-1
5.3 Networking as a Gateway Office (GMGW) ........................................................... 5-2
5.4 Networking as an End Office and Gateway Office Combination ............................. 5-3
5.5 Networking as a Tandem Office (TMGW) ............................................................. 5-3
5.6 Networking by Being Combined with the ZXWN MSCS to a MSC NE in a GSM
Network ........................................................................................................... 5-4
5.7 Networking as an IM-MGW ................................................................................. 5-5
5.8 Networking as an MRFP ..................................................................................... 5-6
5.9 Networking as a VIG........................................................................................... 5-6
5.10 Dual-Homing Networking Mode ......................................................................... 5-7
5.11 MSC Pool Networking Mode.............................................................................. 5-8
Chapter 6 Technical Specifications .......................................................... 6-1

6.1 Product Specifications ........................................................................................ 6-1
6.1.1 Power Supply Specifications ..................................................................... 6-1
6.1.2 Interface Specifications............................................................................. 6-1
6.1.3 Clock Specifications ................................................................................. 6-2
II
6.1.4 Reliability Specifications ........................................................................... 6-2
6.1.5 Performance Specifications....................................................................... 6-3
6.2 Component Specifications .................................................................................. 6-4
6.2.1 Specifications for the Operation & Maintenance Module.............................. 6-5
6.2.2 Specifications for the Power Module .......................................................... 6-6
6.2.3 Specifications for the Environment-Monitoring Module ................................ 6-6
6.2.4 Specifications for the Fan Unit Module....................................................... 6-7
6.2.5 Specifications for Board Power Consumption ............................................. 6-8
6.2.6 Specifications for the Alarm Box ................................................................ 6-8
Chapter 7 Environmental Requirements .................................................. 7-1

7.1 Grounding Requirements .................................................................................... 7-1
7.2 Temperature and Humidity Requirements ............................................................ 7-1
7.3 Cleanness Requirements.................................................................................... 7-2
7.4 Air Pollution Requirements.................................................................................. 7-2
Glossary .......................................................................................................... I
III
IV
About This Manual
Purpose
This manual provides an overall introduction to ZXUN iMG, including system architecture,
interfaces, service functions, networking applications, technical specifications and
environmental requirements.
Intended Audience
This manual is intended for:
l Technical and maintenance personnel who have mastered the principles of mobile
network communications
l Engineers who need to know the working principle, interfaces, service function,
networking application, and technical specifications of ZXUN iMG
What Is in This Manual

This manual contains the following chapters:
Chapter Summary
Chapter 1, Product Overview Briefly describes the ZXUN iMG system, the product
features and the working principle.
Chapter 2, System Architecture Describes the system architecture of ZXUN iMG.
Chapter 3, Interfaces Describes the interfaces used in ZXUN iMG.
Chapter 4, Service Functions Describes the service functions of ZXUN iMG.
Chapter 5, Networking Applications Describes the networking applications of ZXUN iMG.
Chapter 6, Technical Specifications Describes the technical specifications of ZXUN iMG.
Chapter 7, Environmental Requirements Describes the environmental requirements of ZXUN iMG.
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
ZTE documents employ the following typographical conventions.
I
Typeface Meaning
Italics References to other manuals and documents.
Quotes Links on screens.
Bold Menus, menu options, function names, input fields, radio button names,
check boxes, drop-down lists, dialog box names, window names.
CAPS Keys on the keyboard and buttons on screens and company name.
Note: Provides additional information about a certain topic.
Checkpoint: Indicates that a particular step needs to be checked before

proceeding further.
Tip: Indicates a suggestion or hint to make things easier or more productive

for the reader.
II
Chapter 1
Product Overview
Table of Contents
Location of ZXUN iMG in a Network ...........................................................................1-1
Main Functions of ZXUN iMG .....................................................................................1-2
ZXUN iMG Product Features......................................................................................1-4
ZXUN iMG Compliance Standard ...............................................................................1-9
1.1 Location of ZXUN iMG in a Network

ZXUN iMG is an NE in the access layer in soft-switch network as a carrier-class media
gateway. It implements the conversation between the information format in mobile
networks and the information format in PSTN networks. In addition, it supports a variety
of voices and data services.
ZXUN iMG supports service bearing of VMSC, TMSC, and GMSC in GSM/UMTS
networks, and smooth evolution to the IM-MGW/MRFP NE in IP Multimedia Subsystem
(IMS) networks.
The built-in signaling gateway SGW/STP of ZXUN iMG can construct networks in various
signaling bearer connection modes. It is also available to set an independent SGW/STP
according to the actual networking requirements.
Figure 1-1 shows the location of ZXUN iMG in a GSM/UMTS mobile soft-switch network.
1-1
SJ-20110412153554-002|2011-10-15 (R1.2) ZTE Proprietary and Confidential

ZXUN iMG (MGW_W) Product Description
Figure 1-1 Location of ZXUN iMG in a GSM/UMTS Mobile Soft-Switch Network
1.2 Main Functions of ZXUN iMG

ZXUN iMG provides the following main functions in networks:
l Bearer access and switching function
The MGW supports media flows over three formats of bearers: Time Division
Multiplexing (TDM) bearer, IP bearer and Asynchronous Transfer Mode (ATM)
bearer. It supports interworking between these media flows over these bearers.
l Bearer control function
In the case of IP bearer and ATM bearer, the media flows of the MGW communicate
in asynchronous communication method. In this situation, the MGW controls bearers,
including establishing and releasing bearers, and modifying the attributes of bearers.
l Built-in SGW function
Serving as an end office, the MGW introduces an ATM bearer at the Iu interface or a
TDM at the A interface, while the Mc interface usually uses the IP bearer. When the
Mc interface uses the IP bearer, the MGW must has the SGW function to implement
conversion from the traditional Signaling System No.7 (SS7) signaling network to the
IP signaling network.
l Interworking function
The MGW has the interworking function with the traditional SS7 signaling network,
channel associated network, IP packet network and the PSTN network. Meanwhile,
1-2

Chapter 1 Product Overview
the MGW can function as an IM-MGW to implement interworking between an IMS

network and an CS network.
l Resource library function
The MGW has the functions of playing the call service tone and intelligent tone,
and playing and detecting the Dual-Tone Multi-Frequency (DTMF) tone and the
Multi-Frequency Control (MFC) tone. For the MSC Server, the MGW is a tone
resource library.
l Voice processing function
The MGW has the voice coding/decoding function in multiple modes, including
PCM-A, PCM-, AMR-NB, , AMR-WB, FR-AMR, HR-AMR, GSM-FR, GSM-HR,
GSM-EFR, G.723, and G.729. It also supports the TFO/TrFO function.
l Data service function
The MGW supports a variety of data services in a CS domain, including:

Non-transparent data service at rates of 14.4 kbit/s, 28.8 kbit/s, and 57.6 kbit/s
Transparent data service at rates of 28.8 kbit/s, 32 kbit/s, and 33.6 kbit/s
Transparent synchronous Circuit Switched Data (CSD) service, transparent
asynchronous CSD service, and G3 fax service of the GSM
3G-324M video service
l Network management function
The MGW provides the functions such as dynamic and static configuration
management, signaling trace and failure observation.
l Video Interactive Gateway (VIG) function
VIG is the video gateway device between a CS network and an IMS network. It
implements interworking between 3G-324M video mobile phones and the SIP video
terminals of the IMS network. It provides the following elementary functions:
Interworking of call control signaling: interworking between the BICC/ISUP call
signaling in the CS domain and the SIP call signaling in the IMS network
Interworking of the system control signaling: interworking between the H.245
signaling at the H324 side and the H.245 signaling at the SIP side
System control at both ends of SIP and those of H324: process of master/slave
determination, process of capability exchange, process of opening logical
channel, process of closing logical channel, process of mode request, and
process of loop delay.
Terminal access: 3G-324M and SIP terminals
Speech encoding and decoding: The VIG gateway supports conversion of AMR
and G.723.1 at the H324 end, and conversion of G.723.1, G.711, G.729, and
AMR at the SIP end.
1-3

Video encoding and decoding: The VIG gateway supports conversion of H.263,
MPEG4, and H.264 both at the H324 end and at the SIP end.
1.3 ZXUN iMG Product Features

ZXUN iMG has the following distinct features:
1.3.1 Unified ETCA Platform

ZXUN iMG uses the Enhanced Telecommunications Computing Architecture (ETCA)
hardware platform. ZTE's ETCA platform is an open and general teleservice platform,
with the Advanced Telecommunications Computing Architecture (ATCA) technology.
Designed for the requirements for the high performance, high reliability, high scalability,
and high maintainability of the carrier-class service application, it is a unified platform
developed by ZTE for the next-generation network.
ZTE's ETCA platform is widely applied by various NEs, including IP Multimedia Subsystem
(IMS), mobile softswitch, and HLR. The ETCA hardware platform has the following
features:
l Openness: It follows the ATCA design specifications, and standards PICMG3.0 R2.0
and IPMI 1.5.
l Modularized and slot design: Boards, power modules, fan subracks and other
components are all inserted in an ETCA shelf.
l Good expansibility: With good performance, I/O interfaces and expansion of storage
capability, the system can be smoothly updated.
l Economy: By saving the installation space, transmission resources and power
consumption, it greatly reduces the cost of equipment and maintenance.
l Carrier-class availability: With high expandability, high reliability, and high
maintainability, it meets the requirements for high availability of a carrier-class
network.
1.3.2 Strong Cascading Capability

The TDM switching network, the control-plane IP switching network, media-plane IP
switching network are provided in a single ZXUN iMG shelf. With strong cascading
and interconnection capability, a single cabinet provides the industry-leading capacity,
effectively saving the construction cost at the initial stage and maintenance cost at a later
stage of carriers.
With rear boards TSWA0, FSWA1 and BSWA0, ZXUN iMG implements the inter-shelf
cascade of TDM, media-plane packet data, and control-plane services. Where, the
TSWA0 is used for cascade and interconnection of TDM, the FSWA1 board is used for
the packet cascade of the media plane, and the BSWA0 board is used for cascade of the
control plane.
1-4

l Figure 1-2 illustrates cascade of the media plane. Each shelf is configured with a
pair of FSWA1 boards, each of which provides two 10 GE cascading interfaces to
implement multi-shelf cascade.
Figure 1-2 Multi-Shelf Cascade of Media Plane
l Figure 1-3 illustrates cascade of the control plane. Each shelf is configured with a pair
of BSWA0 boards, each of which provides four GE cascading interfaces to implement
multi-shelf cascade.
Figure 1-3 Multi-Shelf Cascade of Control Plane
1-5

l In terms of TDM interconnection, the TSWA0 boards in each shelf externally provide
64 K cascading capability for inter-shelf TDM interconnection to meet the requirement
for a large-capacity TDM network. Figure 1-4 is a diagrammatic drawing of three-shelf
interconnection.
Figure 1-4 TDM Interconnection of ZXUN iMG
1.3.3 Variety of Physical Interfaces

ZXUN iMG provides open and standard interfaces for meeting the GSM and 3GPP
R4/R5/R6 networking requirements. It is easy for smooth evolution to Long Time Evolution
(LTE) and capacity expansion of equipment.
The ZXUN iMG can support IP, TDM and ATM transmission modes simultaneously, and
existing NE interfaces and protocols. With this feature, ZXUN iMG can conveniently
interwork with any existing networks.
ZXUN iMG is equipped with a variety of hardware interfaces to meet the networking
requirements in all environments, including E1/T1 access, STM-1 access, CSTM-1
access and GE access. It can support STM-4 (CSTM-4) access and 10 GE access in the
future. With rear boards, E1/T1, E1/T1 and CSTM-1 accesses support multiple bearing
modes such as TDM, IP and ATM.
ZXUN iMG leads in the external clock reference, and extracts clock from the BITS device. It
provides BITS, GPS, and PTP clock access, extracts line clock, implements clock genlock,
and generates intra-shelf/inter-shelf clock reference.
1-6

1.3.4 Environmentally Friendly Design

ZXUN iMG uses a highly efficient energy saving policy, facilitating energy saving and
emission reduction and constructing a green network.
l The ETCA shelf is equipped with highly effective power modules with a power output
efficiency of 99.5%.
l It uses the industry-leading low-consumption multi-core processors.
l With a collaboration between the Intelligent Platform Management Interface (IPMI)
and the shelf manager, the function of board power-off is achieved, which effectively
avoids resource wastes caused by the tidal effect.
l It automatically adjusts the fan speed according to the ambient temperature, saving
the power consumption of fans.
l Unique high-density design saves the occupied area of the equipment room.
1.3.5 Capability of Smooth Upgrade and Capacity Expansion

With the modular and distributed design, ZXUN iMG is available for flexible capacity
configuration according to the requirements of customers.
l When equipment requires expansion, you can add the corresponding boards
according to the new capacity requirements, without interrupting services.
l When service upgrade is required, you can upgrade software or add new service
boards without interrupting services, implementing smooth expansion and upgrade
without being noticed by subscribers.
1.3.6 Excellent Reliability

ZXUN iMG provides sophisticated reliability-guaranteed mechanism to avoid single point
failures and improve the system reliability.
l System-level reliability
With a distributed design, ZXUN iMG is equipped with dual-channel power
supplies. Either interface boards, switching boards and processing boards all
work in 1+1 backup mode, or N+M resource pool backup mode is used.
Both boards and interfaces have an automatic changeover function to ensure the
uninterrupted operation of the system.
The service processing units operate in load-sharing mode. The load is
automatically transferred to other nodes once a node fails.
Control streams are separated from media streams in the entire system, without
mutual interference.
l Hardware-level reliability
The stability of hardware devices are verified by high temperature aging tests.
Strict technological control is exercised over the production process.
The protective design for the external interfaces relieves the impact on the boards.
1-7

The power-on self-test of boards assists you to detect and locate problems in the
earliest time.
The OMM system has the capability to diagnose and test hardware.
Boards support hot plugging, which ensure a safe and reliable process of
replacing boards.
l Software-level reliability
With the modular design, software engineering design idea, and loop coupling
between modules reduce the possibility of software making errors.
It supports user-mode operating system and independence of process space.
Therefore, the fault of a process does not directly affect other processes.
It provides the software and the data with multilevel protection and has
self-detection and self-recovery functions.
Multilevel overload control and alarm mechanism further guarantees the system
reliability. In case of a heavy system load, the system is protected from the impact
of heavy load by abandoning some services by a certain proportion.
Internal resources and data areas are provided with the deadlock detection
mechanism, which prevents the system from producing accumulative effect after
long-time operation.
It supports lossless upgrade and quick restoration of data in case of unsuccessful
upgrade.
1.3.7 Manageability and Easy Maintenance

ZXUN iMG has a sophisticated operation management and maintenance system with the
following features:
l The Browser/Server structure ensures perfect networking capability and scalability of

the system.
l The OMM server uses the blade server, which is convenient for deployment and the
occupied area of the equipment room.
l The OMM clients provide friendly interfaces, flexible, easy and reliable for operation.
In addition, it provides multiple remote and local access modes, and allows you to
perform local operation and maintenance or remote operation and maintenance with
the network system.
l The system is of reliable security and employs multilevel authority protection.
l The system supports functions such as performance measurement, traffic statistics,
security management, traffic observation, subscriber (equipment) trace, signaling
trace, configuration, version upgrade, alarm, loading, data backup and transmission.
The system provides multiple accurate, reliable, practical and convenient operation
and maintenance means. Furthermore, the system can add functions according to
actual network running conditions and user requirements.
1-8

1.4 ZXUN iMG Compliance Standard

ZXUN iMG conforms strictly to the following standards.
l 3GPP R99 technical specification series
l ITU-T recommendation series
l IETF related protocols
l GB001-900, Chinese Domestic Telephony Network No.7 Signaling Mode Technical
Specifications
l YD/T627-93, Digital Switch Trunk Interface (2048 Kbit/s) Parameters and
Transmission Features between Digital Interfaces and Testing Methods.
l GB 4943-1995, Safety of Information Technology Equipment
l General Technical Requirements for Softswitch Equipment
l General Technical Requirements for Mobile Softswitch Equipment
1-9

This page intentionally left blank.
1-10

Chapter 2
System Architecture
Table of Contents
Hardware Architecture................................................................................................2-1
Software Architecture .................................................................................................2-5
2.1 Hardware Architecture

2.1.1 Physical Architecture
Description
This topic describes a standard-type cabinet architecture, functions of each part, weight of
the integrated equipment, and bearing of the equipment room floor.
Architecture
The cabinet is a 19-inch B6080-22 cabinet, and follows the international standard IEC
60297-2. It has a maximum internal space of 47 U (1 U=44.45 mm). Its dimensions: 2200
mm (H) 600 mm (W) 800 mm (D).
A cabinet consists of one rack, three service shelves (E8280 shelf), one dual-channel
power distribution subrack (unified PDU), one ventilation subrack, and two 1 U blank
shelves.
The architecture layout of the cabinet is shown in Figure 2-1.
2-1

Figure 2-1 Cabinet Layout
Component Functions
Table 2-1 lists the functions of each component.
2-2

Chapter 2 System Architecture
Table 2-1 Component Functions
Component Function
Power distribution sub- l Installed on the top of the cabinet, distributes -48 V DC power in the
rack cabinet and provides security protection.
l A dual-10-channel unified Power Distribution Unit (PDU) boasts power
distribution, power status and environment monitoring, short circuit
protection and lightning protection.
l The PDU detects the input voltage and the status of the allocated out-
put power. If the PDU detects a fault, it generates an alarm.
l The PDU monitors the temperature sensor, the humidity sensor, and
the smoke sensor in an equipment room, controls the access of the
rack and the equipment room, monitors fans, and performs lightning-
protection monitoring.
l It provides a set of RS485 interfaces for communicating with the pro-
cessing boards in the service shelves.
E8280 shelf l Front fan subracks are placed above the front panel of the shelf. A
E8280 shelf supports up to two front fan subracks, each of which is
composed of six fan modules.
l Rear fan subracks are placed above the rear panel of the shelf. A
E8280 shelf supports one rear fan subrack, which is composed of eight
fan modules.
l 14 front board slots and 14 rear board slots are provided in the shelf.
l A power supply box is at the bottom at the back of the shelf. The
shelf uses two groups of redundant input power supplies. Each group
of power supply provides two power cables for supplying power, with
four power cables totally.
Ventilation subrack Discharges the hot wind out of the cabinet.
Rear horizontal routing Arranges the cables from the rear of the cabinet.
subrack
Cabinet 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.
2.1.2 Logical Architecture

Description
Figure 2-2 shows the logical architecture of the ZXUN iMG hardware system. In terms of
logical functions, the hardware system is divided into the control processing and switching
2-3

modules, packet handling interface and switching modules, TMD interface and switching
modules, and service processing modules.
Figure 2-2 Hardware System Architecture of ZXUN iMG
Logical Functions
l Control processing and switching modules
Control plane processing unit GPBB0
implements the control-plane processing, high-layer signaling processing, call
control processing, resource management, and operation and maintenance.
Control-plane switching unit BSWA0
implements switching and processing of the control-plane data, and provides
other shelves with the control-plane cascade ports.
l Packet processing interface and switching modules
IP/ATM interface units IPIA0, IPIA1, APIA0 and APIA1
The interface part leads in the interfaces such as STM-1, E1, FE, and GE.
The IP switching part uses two sets of switching channels. One set provides the
media stream channels for switching the service streams for the resource boards
to process, receiving and processing of the AAL2/ATM or IP media plane data,
and sending the media packet after processing to the service processing unit.
The other set provides the signaling streams and the command and parameter
2-4

channels for the system to control, configure, maintain and manage the boards.
It also processes the access of ATM/IP broadband signaling, and sends the
signaling packets after processing to the control modules.
Media-plane switching unit FSWA1
implements switching and processing of the media-plane data, and provides other
shelves with the media-plane cascade ports.
l TDM interface and switching modules:
Trunk interface units DTIA0, DTIA1, SDIA0, and SDIA1
The interface part leads in the circuit/optical interfaces such as E1, T1, and
STM-1/4, and then demultiplexes/multiplexes them into internal HW signals and
transfers them to the T network switching unit.
The control-plane switching part as the interface between this part and the
external control streams functions in channeling and connection. It provides the
signaling streams for the trunk interface boards to process and the command
and parameter channels for the system to control, configure, maintain, and
manage the boards. It processes the narrowband SS7 layer-2 signaling, and
sends the signaling packets after processing to the control modules.
Circuit switching unit TSWA0
It is used for switching of the TDM circuits.
l Service processing module:
The service processing units MPBA0 and MPBA1 provide the service functions
including RTP session processing, 3GPP UP protocol processing, encoding
and decoding conversion, tone playing, Dual-Tone Multifrequency (DTMF) digit
transmitting and receiving, Multi-Frequency Control (MFC) processing, audio mixing
processing, InterWorking Function (IWF) processing, and IP fax T38 processing.
2.2 Software Architecture

Overview
ZXUN iMG adopts the idea of modularization and hierarchy in software design. It consists
of nine subsystems.
l Service Oriented Driver Architecture subsystem (SODA)
l Telecom Universal Integrated Platform (TULIP)
l System Control Subsystem (SCS)
l DataBase Subsystem (DBS)
l Bear Subsystem (BRS)
l Multicore and MicroCode Media Carring Subsystem (MCS)
l Signalling (SIG) Subsystem
l MGW application subsystem
l Operation & Maintenance Subsystem (OMM/OAM)
2-5

Figure 2-3 Software Architecture of ZXUN iMG
SODA Subsystem
The SODA subsystem provides the whole hardware system with BOOT, device drivers,
and CPU minimum system functions. It shields hardware details from other software
subsystems, abstracts the logical functions of hardware, and makes the software
subsystems above the operating system independent of the bottom-layer hardware
equipment.
TULIP Platform
The TULIP platform provides a unified telecom-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,
and multi-core management.
SCS Subsystem
The SCS subsystem is in charge of system monitoring, startup and version loading.
DBS Subsystem
The DBS subsystem provides the configuration and storage function related to services,
signaling, and protocols. It also manages the NE resources and the configuration
information about services, signaling and protocols, and provides other subsystems with
database access/storage interfaces.
BRS Subsystem
The BRS subsystem is the built-in router software. 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.
On one hand, the BRS subsystem manages the external IP and ATM interfaces of the
NE, and provides services for the IP packet and ATM cell communication between NEs.
2-6

On the other hand, based on database configuration data, it manages the interface
for internal user plane communications and provides services for user plane IP packet
communications between boards inside the NE.
MCS Subsystem
As the extension of the BRS subsystem, the MCS subsystem distributes the media plane
packets entering the NE from the external, and transmits the internal packets out of the
NE.
SIG Subsystem
The SIG subsystem implements various signaling functions, including narrowband
Signaling System No.7 (SS7), broadband SS7, and Signalling Transport (SIGTRAN)
signaling. It also provides services for the MGW application layer. For the link-layer
protocols of broadband/narrowband SS7, the link layers of the signaling implement
link-level load sharing. When the capacity of the system is large, it supports load
sharing of signaling processing between boards. For the narrowband SS7, the SIG
subsystem supports 64 kbps, n64 kbps and 2 Mbps signaling links. It also supports the
multiple-signaling-point function in different signaling networks.
MGW Application Subsystem

This subsystem includes the control-layer plane and the media-layer plane. The
control-layer plane processes the gateway control signaling, manages the call resources
on the gateway, and implements the call control on the gateway.
The media-layer plane provides the following functions:
l Bearer access: supports three types of bearer accesses, ATM, IP and TDM.
l Frame protocol processing: supports NbUP and IuUP protocols, and versions 1 and
2 of the UP mode.
l Voice code/decode: supports AMR_NB, AMR_WB, G729, G723, G711A, G711U,
GSM_FR, GSM_EFR, GSM_HR, FR_AMR, HR_AMR, OHR_AMR, OFR_AMR-WB,
OHR_AMR-WB, and FR_AMR-WB.
l TrFO/TFO processing.
l Rate adaptation of the circuit bearer data service.
l Announcement playing processing, DTMF digit sending/receiving, and conference
audio mixing
OMM/OAM Subsystem
Based on the application scenarios and administrative capability, the OMM/OAM
subsystem is divided into the Local Maintenance Terminal (LMT) system and the network
Element Management System (EMS).
The LMT system consists of the server and the operating terminal. The server blade works
together with the service boards in the same shelf, reducing the floor space. The operating
terminal works in Web mode. Installation is not required.
2-7

The OMM/OAM subsystem provides sophisticated security management policy plus the
measures such as authentication access control and data link encryption. This ensures
the system-wide data security, and prevents the data from being illegally accessed and
maliciously modified.
The OMM/OAM subsystem is in compliance with the Telecommunication Management
Network (TMN) structure.
In function, the subsystem consists of the modules including configuration management,
performance management, fault management, diagnostic test management, service
observation, signaling trace, security variable management and charging management.
2-8

Chapter 3
Interfaces
Table of Contents
Interface Overview .....................................................................................................3-1
Iu-CS Interface ...........................................................................................................3-2
Mc Interface ...............................................................................................................3-5
Nb Interface ...............................................................................................................3-6
A Interface..................................................................................................................3-8
Ai Interface.................................................................................................................3-8
Mn Interface ...............................................................................................................3-8
Mb Interface ...............................................................................................................3-9
Mp interface .............................................................................................................3-10
O&M Interface ..........................................................................................................3-10
3.1 Interface Overview

Interface Diagram
ZXUN iMG acts as a core network NE in the Universal Mobile Telecommunication System
(UMTS) system. Its interfaces are shown in Figure 3-1.
Figure 3-1 Main Interfaces of ZXUN iMG
Interfaces
ZXUN iMG has the following interfaces , as shown in Table 3-1.
3-1

Table 3-1 Main Interfaces
Interface Type Description
Iu-CS It supports the RNC access at the user plane, with the signaling
interface bearer type being ATM or IP, and the data interface bearer
type being ATM or IP.
Mc It is the signaling interface between the MGW and the MSCS, with
the interface bearer type being ATM or IP.
Nb It is the interface between the MGW and other MGWs in the core
network, with the interface bearer type being ATM, TDM or IP.
A It is the interface between the MGW and the BSC, with the interface
type being TDM.
Ai It is the interface between the MGW and the PSTN, with the interface
type being TDM.
Mn It is the interface between the MGCF and the IM-MGW. It belongs to

the control signaling interface and supports H.248.
Mb It is a user plane interface of the IMS network, providing the speech

coding based on the VoIP encapsulation mode.
Mp It is the interface between the MRFC and the MRFP and uses the
H.248.
O&M interface OMM It provides the MSCS with such functions as centralized maintenance,
(not shown in interface monitoring and network management. This interface is based on
the figure) TCP/IP.
CORBA It is the interface between the NMC (Network Management Center)

and the OMM provided by the equipment manufactures.
SNMP It is the interface between the NMC and the OMM provided by the
equipment manufactures.
3.2 Iu-CS Interface

The Iu-CS interface is an interface between the Radio Network Subsystem (RNS) and the
CN circuit domains.
In R4, the Iu-CS interface is connected over ATM.
In the 3GPP protocol of R5 and later releases, it is specified that the bearer mode can be
ATM bearer or IP bearer.
ZXUN iMG supports both ATM and IP bearer modes.
3-2

Chapter 3 Interfaces
3.2.1 Iu-CS Interface Based on ATM

Protocol Stack in 3GPP Specification 25.410
The Iu-CS interface protocol stack (based on ATM) described in 3GPP Specification 25.410
is shown in Figure 3-2.
Figure 3-2 Iu-CS Interface Protocol Stack (Based on ATM)
According to Iu-CS protocol stack (based on ATM) structure, the Iu-CS interface protocols
include:
l Control plane protocol: This protocol includes control signaling RANAP and signaling
bearer (TS25.412).
l User plane protocol: This protocol includes user plane protocol Iu UP and data bearer
(TS25.414).
l Bearer control plane protocol: This protocol includes control signaling ALCAP and
signaling bearer (TS25.414).
For the MGW, the involved Iu-CS interface protocols are the last two types.
3-3

User Plane Interface Protocol

In R4 network, the Iu-CS interface transmits user plane data based on AAL2. The user
plane protocol stack is as shown in Figure 3-3. The user-plane protocol stack of the Iu-CS
interface is identical with that of Nb interface over ATM.
Figure 3-3 Iu-CS User Plane Protocol Stack (Based on ATM)
Bearer Control Signaling Interface

In R4, the Iu-CS bearer control signaling interface is used for establishing AAL2 connection
at user plane. AAL2 signaling adopts broadband No.7 signaling. Protocol stack is shown
in Figure 3-4. Bearer control signaling protocol stack of Iu-CS interface is identical with
that of Nb interface over ATM.
Figure 3-4 Iu-CS Bearer Control Plane Protocol Stack (Based on ATM)
3.2.2 Iu-CS Interface Based on IP

Application
Iu-CS interface is an interface between the RNS and the CN circuit domains. In R4, the
Iu-CS interface is connected over ATM. In the 3GPP protocol of R5 and later releases, it is
specified that the bearer mode can be ATM bearer or IP bearer. The following introduces
the protocol stack based on IP.
User Plane Interface Protocol

Figure 3-5 shows the Iu-CS user plane protocol stack based on IP, adopting the UDP
bearing RTP to transfer user-plane information.
3-4

Figure 3-5 Iu-CS User Plane Protocol Stack (Based on IP)

Figure 3-6 shows the Iu-CS bearer control plane protocol stack based on IP.
Figure 3-6 Iu-CS Bearer Control Plane Protocol Stack (Based on IP)
3.3 Mc Interface
Overview
The Mc interface provides the protocol interaction between the MSC Server and the MGW.
It belongs to the control signaling interface and supports the H.248 protocol.
Protocol Stack
Figure 3-7 shows the protocol stack of the Mc interface.
Figure 3-7 Mc Interface Protocol Stack
3-5

The MGW supports H.248 protocol, conforming to the 3GPP TS 29.232 standard. The
signaling bearer mode can be ATM or IP:
l Mc interface over ATM based on the broadband SS7. ATM bears the upper-layer
signaling through the AAL5 adaptation. The signaling protocol stack is the broadband
signaling protocol stack composed of SSCOP/SSCF/MTP3b. The address of the
MGW is shown as an SS7 address.
l Mc interface over IP based on the IP signaling transmission protocol stack. The
signaling protocol stack is IP/SCTP/M3UA. The transmission is implemented on the
IP network, but the address of the MGW is shown as an SS7 address.
l In a full IP network, the Mc interface over IP based on the IP signaling transmission
protocol stack. The signaling protocol stack is IP/SCTP, and the address of the MGW
is shown as an IP address.
3.4 Nb Interface
Application
Nb interface is responsible for media stream transmission between MGWs. When Nb
interface carries data based on ATM/IP, it is divided into user plane and bearer control
plane. Bearer control plane of Nb interface uses bearer signaling protocol to establish
bearer channel.

There are two kinds of Nb bearer control signaling interfaces: ATM-based interface and
IP-based interface.
Figure 3-8 shows protocol stack when user plane data bearer of Nb interface is based on
ATM and bearer control signaling protocol is ALCAP.
Figure 3-8 Control Plane Protocol Stack of Nb Interface (ATM Bearer)
When Nb interface bears user plane data over IP, bearer control signaling protocol is
IPBCP. IPBCP is transmitted via tunnel that is made by H.248 of Mc and BICC of Nc.
Transmission status is as shown in Figure 3-9. Tunnel part complies with BCTP, that
3-6

is, ITU-T Q.1990. BCTP transmission part at Mc interface complies with application
description of H.248 in 3GPP TS 29.232, and BCTP transmission part at Nc interface
complies with BICC Q.765.5.
Figure 3-9 IPBCP of Nb Interface via Tunnel Transmission
User Plane Interface

Nb interface can bear user plane data over ATM, IP or TDM. Three modes are described
below:
1. ATM mode:
When Nb interface bears user data over ATM, user plane protocol stack is as shown in
Figure 3-10. ATM adaptation layer adopts AAL2, which is connected to an ATM virtual
circuit for transmission. The virtual circuit is Permanent Virtual Circuit (PVC).
Figure 3-10 User Plane Protocol Stack of Nb Interface (ATM Bearer)
2. IP mode:
Figure 3-11 shows user plane protocol stack of Nb interface when user data is over IP.
User panel information is transferred in mode of RTP over UDP. RTCP is optional. In
the receiving end, RTCP data unit can be neglected.
3-7

Figure 3-11 User Plane Protocol Stack of Nb Interface (IP Bearer)
3. TDM mode: When Nb interface bears user data over TDM, user data is transmitted
via PCM code. In this case, there is no user plane protocol.
3.5 A Interface
The user-plane data of the A interface can be over TDM and IP.
l Over TDM
When the A interface adopts the TDM bearer, user data are transmitted through PCM
codes. In this case, there is no user-plane protocol.
l Over IP
When the A interface adopts the IP bearer, the user-plane protocol stack is shown in
Figure 3-12, adopting the UDP bearing RTP to transfer user-plane information.
Figure 3-12 User Plane Protocol Stack of A Interface (Based on IP)
3.6 Ai Interface
The Ai interface between MGW and PSTN is based on TDM connections. User data are
transmitted through PCM codes. In this case, there is no user-plane protocol.
3.7 Mn Interface
Overview
The Mn interface provides the protocol interaction between MGCF and IM-MGW. As a
signaling control interface, it supports H.248 protocol.
3-8

Protocol Architecture
The protocol stack of the H.248 protocol is shown in Figure 3-13.
Figure 3-13 Protocol Stack of the H.248 Protocol
The signaling of the H.248 protocol supported by the IM-MGW complies with the standard
3GPP TS 29.332. The signaling bearer supports two kinds of IP modes:
1. One mode is based on the IP signaling transfer protocol stack, and applied to the
situation where the Mn interface is over IP. The signaling stack is IP/SCTP/M3UA.
This mode implements transfer of the SS7 signaling in the IP network, and the MGW
NE address is embodied by the SS7 address.
2. The other mode is based on the IP signaling transfer protocol stack, and applied to
the situation where the Mn interface is over IP. The signaling stack is IP/SCTP and the
MGW NE address is embodied by the IP address.
3.8 Mb Interface
Overview
The Mb interface is a user plane interface of the IMS network, providing the speech coding
based on the VoIP encapsulation mode.
The protocol stack of the Mb interface is shown in Figure 3-14.
Figure 3-14 Protocol Stack of the Mb Interface
3-9

Involved NEs
In an IMS network that supports the Mb interface, the NEs include IMS terminals, MRFP,
IM-MGW and next-generation AS combining bearer and control.
Encapsulation Format of the Codec

For the specific packet encapsulation format of each kind of Codec, the Mb interface
directly adopts the related RFC to realize. For example, the encapsulation format of the
AMR adopts RFC3267, and that of the G.723 adopts RFC3551.
3.9 Mp interface
Application
The Mp interface between the MRFC and the MRFP uses the H.248 protocol. The MRFC
controls the MRFP through this interface to process media resource, such as tone playing,
conference, DTMF transmitting/receiving.
Mp Protocol Stack
Figure 3-15 shows the Mp protocol stack.
Figure 3-15 Protocol Stack of Mp Interface
The MRFP supports H.248 protocol, conforming to the 3GPP TS 29.332 standard, and
supports two IP modes for bearing the signaling.
1. The Mp interface over IP based on the IP signaling transmission protocol stack. The
signaling protocol stack is IP/SCTP/M3UA. The transmission is implemented on the
IP network, but the address of the MRFP is shown as an SS7 address.
2. The Mp interface over IP based on the IP signaling transmission protocol stack. The
signaling protocol stack is SCTP/IP, and the address of the MRFP is shown as an IP
address.
3.10 O&M Interface

O&M interface includes the following three types.
3-10

l OMM Interface
l CORBA Interface
l SNMP Interface
3.10.1 OMM Interface

Overview
The OMM system of ZXUN iMG adopts the TMN architecture, and its interfaces include
N interface, client-oriented MML interface and interface between the OMM system and
ZXUN iMG NE.
l N interface describes such application protocols as CORBA/SNMP, to implement
interconnection between the OMM system and the NMC .
l As an interface between the LMT terminal and the OMM server, MML interface
describes commands and command responses between an LMT terminal and the
OMM server.
l Internal message interface or SNMP protocol interface is used between the OMM
server and ZXUN iMG NE.
The structure of OMM interface protocol is shown in Figure 3-16.
Figure 3-16 Structure of OMM Interface
Features
l Belonging to the application layer, all interfaces of the OMM system are responsible
for interconnection and interoperation between systems and devices. They run over
TCP/IP.
l These interfaces do not involve specific communication protocols, but use connection
specifications.
l The TMN protocol does not stipulate specific command form for the MML interface.
In this OMM system, the MML interface uses XML text form.
3-11

3.10.2 CORBA Interface

Definition
The CORBA interface is a communication interface supported by the CORBA technology.
In a communication network management system, it is the interface between the NMC of
the operator and the OMM provided by the equipment vendor for multilevel management
of a communication network.
Physical Location
Figure 3-17 shows the position of the CORBA interface in a network management network.
Figure 3-17 Position of the CORBA Interface
Connection between CORBA Interface and Upper-level Network Management

The connection between the CORBA interface and the upper-level network management
system is usually in naming service mode and IOR file mode.
l If the naming service mode is used, it is required to provide the upper-layer network
management system with the IP address used for the interconnection between the
upper-layer network management and the ZTE OMM.
l If the IOR file mode is used, it is required to provide the upper-layer network
management system with the IOR file ending with EPIRPImpl among the object
persistence files.
3.10.3 SNMP Interface

Definition
The SNMP interface is the interface between the NMC of the operator and the OMM
provided by equipment manufactures.
3-12

Application
Figure 3-18 shows the position of the CORBA interface in a network management network.
NMC gives management operation commands, while the OMM executes management
operations, returns the execution result to the NMC, and may report the related notification
to the NMC.
Figure 3-18 Position of the SNMP Interface
Functions
l Getting the version number of ALARM IRP
This function enables the upper-layer network management to query the version No.
of the ALARM IRP object.
l Getting the version number of CS IRP
This function enables the upper-layer network management to query the version No.
of the CS IRP object.
l Getting the current heartbeat value
This function enables the upper-layer network management to monitor and manage
the links to the lower-layer network management to get the current heartbeat value.
l Setting a new heartbeat value
This function enables the upper-layer network management to monitor and manage
the links to the lower-layer network management to set a new heartbeat value. The
range of the heartbeat value is [1, 60] and 0, and the unit is minute. Where, 0 means
that no heartbeat value is set. A heartbeat notification will be reported when the
heartbeat value is set to 0 for the first time, and no heartbeat notification will be report
when the heartbeat value is set to 0 again.
l Reporting the heartbeat notification
This function enables the alarm heartbeat events generated on the NE to be sent to
the NMC according to the TRAP destination information.
l Managing the TRAP destination: including adding a new TRAP trace address,
deleting a TRAP trace address, and querying TRAP trace address information
3-13

This function enables upper-layer network management to manage and maintain

TRAP addresses.
l Reporting alarms according to TRAP
This function enables the newly-generated alarms and recovered alarms on the NE
to be reported to the NMC according to the TRAP destination information.
3-14

Chapter 4
Service Functions
Table of Contents
Introduction to Service Functions................................................................................4-1
Media Gateway Control Function ...............................................................................4-2
Bearer Control Function .............................................................................................4-4
User Plane Processing Function.................................................................................4-5
Built-in Signaling Gateway Function .........................................................................4-13
VMGW Function.......................................................................................................4-14
4.1 Introduction to Service Functions

Overview
As the media gateway equipment, ZXUN iMG completes the format conversion for media
streams over IP/ATM/TDM, composes the mobile switching center of the CS domain in the
3G core network together with the MSCS, and cooperates with other equipment to provide
abundant 3G services.
Service Functions
The service functions provided by ZXUN iMG can be divided into three types:
l Media Gateway Control Function
l Bearer Control Function
l User Plane Service Processing Function
Also, ZXUN iMG supports embedded Signaling Gateway (SGW) function. It also supports
adaptation and forwarding of signaling of UMTS access network and external networks.
Details of service functions are as follows:
l Media gateway control function
Media Gateway control function is a service function provided by the MGW in the
Mc interface. This function is defined by H.248 protocol module. This function can
be divided into call-related service function and global service function. Services
implemented by call-related service function are related with media. For detailed
description, refer to 4.2.1 Call-Related Service and 4.2.2 Global Service.
l Bearer control service function
Bearer control service function is a service function provided by the MGW in the Nb
interface control panel and Iu interface control panel. It is defined by the IPBCP
protocol module and the ALCAP protocol module, which corresponds to user panel
4-1

bearer over IP and ATM. For detailed description, refer to 4.3.2 IP Bearer Control and
4.3.1 ATM Bearer Control.
l User plane service processing function
User plane service processing function is a service function provided by MGW in Nb
interface user plane and Iu interface user plane. This function can be further divided
into several parts: radio network layer processing, non-access layer application and
bearer function. Radio network layer user plane includes Iu UP processing and Nb
UP processing. Non-access layer application includes voice service and circuit bearer
data service. Bearer function includes HDLC driver, ATM and IP bearer.
l Embedded signaling gateway function
ZXUN iMG supports SGW built-in function in MGW. When SGW function is built
in MGW, MGW provides signaling interfaces from SGW to PSTN, PLMN and the
IP network. It also supports adaptation and transfer function of signaling between
different networks. For detailed description, refer to 4.5 Built-in Signaling Gateway
Function .
l VMGW (Virtual MGW) function
For detailed description, refer to 4.6 VMGW Function .
4.2 Media Gateway Control Function

4.2.1 Call-Related Service
ZXUN iMG is able to implement the following call-related service functions:
l Access and conversion of multiple voice media streams: The MGW can support
multiple voice coding compression modes including AMR_NB, AMR_WB, G729,
G723, G711A, G711U, GSM_FR, GSM_EFR, GSM_HR, FR_AMR, HR_AMR,
OHR_AMR, OFR_AMR-WB, OHR_AMR-WB and FR_AMR-WB9, and implement
mutual conversion among different kinds of voice stream.
l Media stream over TDM, IP and ATM, and conversion between different media
streams.
l Call management bearer by receiving commands from the MSC Server and
supporting to establish and release bearer in case of intra-office and inter-office
connection.
l Forward and backward bearer establishment, establishment by means of tunnels over
IP, and tunnel setup in a quick or delay manner.
l Intra-MGW handoff and inter-MGW handoff.
l Access on A interface, and handoff between GSM and WCDMA systems.
l Call functions involved in supplementary services, including call forwarding, call
barring, call holding and multi-party conference.
l Intelligent tone playing.
l Data service, including transparent data service, such as video phone service, and
3.1 kHz non-transparent data transmission service.
4-2

Chapter 4 Service Functions
l DTMF receiving and transmitting and DTMF in-band and out-of-band conversion.
l TrFO function of the voice call.
Transcoder Free Operation (TrFO): It is an out-band transcoder control operation.
In this mode, before a call is setup, the control plane completes the end-to-end
coordination. After the coordination, the number of transcoders is reduced, and
thereby the voice quality is improved.
In TrFO mode, if the negotiation is successful, TC resource is not allocated, and TC
does not need to be involved in the whole negotiation process.
l TFO function of the voice call.
Tandem Free Operation (TFO): It is an in-band transcoder control operation and it

is also a connection configuration between two Codecs that support TFO protocol.
When encoder/decoders between these two Codecs match each other, voice quality
is improved by in-band transcoder negotiation and reducing the transcoder processing
times of voice.
In TFO mode, each channel needs to occupy TC resource and negotiates through
TC resource. But the occupied TC resource does not need to involve in transcoder
operation.
4.2.2 Global Service

Global service contains two aspects of contents:
1. Register, deregister and recovery
An MGW can register with an MSC Server. It looks for the MSC Server with priority
in configuration and initiates a registration process under power-on initializing status.
In case registration fails, MGW can re-originate registration process with other MSC
Servers. MSC Server can accept registration of the MGW, or instruct MGW to register
with other MSC Servers.
In case the signaling line of the MGW is unavailable, its internal fault occurs, and
maintenance console forcibly closes it, MGW becomes invalid. If possible, fault
causes can be reported to MSC Server to cancel registration. If the above condition
disappears, MGW can re-originate registration process with MSC Server, and indicate
causes or MGW is out of service under control of MSC Server.
Physical terminal in MGW possessed independent media stream function also has
the report function of expiry and recovery. If physical terminal is unavailable due to
board breakdown, link blocking or force from the maintenance console, MGW reports
faulty state to MSC Server, and reports service recovery and indicates causes once
the service is recovered or physical terminal in MGW is out of service under the control
of MSC Server.
2. Audit
4-3

MGW can accept an audit command from MSC Server and give corresponding
response. Audits of attribute value and range of attribute value can be conducted.
Audit objects contain MGW office and terminals in MGW.
Except normal attributes and attribute sets, the following contents also can conduct
audit: MGW level, default attribute value of temporary terminal, all of physical terminal
IDs and all terminal IDs in a context. MGW gives correct response to these audits.
4.3 Bearer Control Function

4.3.1 ATM Bearer Control
Overview
When ZXUN iMG works in ATM bearer mode, ATM bears the media stream on user plane
via AAL2. Multiple AAL2 connections on a PVC construct a channel.
Functions
ATM bearer control function of MGW is implemented through ALCAP protocol module,
which implements the following bearer control functions on Nb interface and Iu interface,
including:
1. Setup and release of bearer: Set up an AAL2 connection and assign necessary
bandwidth resource for connection according to service requirement, and release
connection after the service ends.
2. Blocking and unblocking of AAL2 link: Block or unblock a channel according to service
or LMT requirement.
3. Reset: Implemented according to service or LMT requirement, including reset of an
AAL2 connection, reset of a channel and reset of global AAL2 resource.
4.3.2 IP Bearer Control

Overview
When ZXUN iMG works in IP bearer mode, IP bears media stream on user plane over
RTP/RTCP in UDP.
Functions
IP bearer control function of MGW is implemented through IPBCP protocol module, which
implements bearer control function on Nb interface and Iu interface, including setup and
release of the RTP stream.
4-4

4.4 User Plane Processing Function

4.4.1 Radio Network Layer Processing
Composition of User Plane at Radio Network Layer
User plane processing at the radio network layer contains IuUP and NbUP processing, as
shown in Figure 4-1.
Figure 4-1 Location of UP Protocol Layer in an NE
IuUP and NbUP Protocol

NbUP protocol is a user plane protocol used on Nb interface, and IuUP is a user plane
protocol used on Iu interface. They comply with 3GPP TS29.419 and 3GPP TS25.419,
and their contents are same. UPs mentioned blow contains IuUP and NbUP.
UP plane supports to process two types of operating modes: Transparent mode and mode
of supporting to predefine SDU length. UP layer adopts transparent mode for circuit bearer
data service.
A UP example only corresponds to a Radio Access Bearer (RAB). RAB is set up between
UE and CN, in which CN controls setup, modification and release of RAB through UTRAN,
and CN also selects type of transport bearer, such as ATM or IP. UP frame protocol mode
is selected by CN, a suitable UP version set is specified by RANAP, and final UP version
is selected in given versions during UP initialization. Generally, IuUP frame protocol is
initialized by UTRAN, or by CN in TrFO.
UP layer adopts the support mode of predefining SDU length for the voice service.
Functional Modules
Functional module of UP protocol layer in support mode is shown in Figure 4-2.
4-5

Figure 4-2 Functional Model of UP Protocol Layer in Support Mode
Functions
Functional modules perform the following functions:
l Frame Handling: Responsible for framing and frame releasing of UP. During frame
releasing, disassembly control fields of a UP frame header, and transport them to
the process control function module for processing, and then conduct CRC for frame
header. Do not process frame that fails to pass CRC any more. During framing,
control fields with sequence number of the frame are generated, CRC is conducted,
and accuracy of control part syntax of frame is ensured.
l Process Control: Contains the following processes.
Initialization is shown in Figure 4-3.
Figure 4-3 Successful Initialization Process
Its function is to control initial information exchange between two peer UP

examples, and initial information contains RFCI set, UP mode version and
interval between transmitting and receiving of UP service data frame (optional).
Rate control is shown in Figure 4-4.
4-6

Figure 4-4 Successful Rate Control Process
Its function is to control maximum transmission rate permitted by downlink UP in

allowable range.
Time alignment, as shown in Figure 4-5.
Figure 4-5 Successful Time Alignment Process
Its function is to control time of transmitting downlink service data of RNC,

indicating whether to pre-act or defer to transmit service data frame by peer UP
example at CN side.
Error event processing is shown in Figure 4-6.
Figure 4-6 Successful Error Event Processing
It is responsible for exchange of error event.

l Specific function of data stream at non-access stratum: Responsible for limited
processing of UP frame load and continuity check for sequence number of frame.
If sequence number of frame is not successive, it indicates there is loss of frame,
4-7

which should be reported to process control function. CRC check and calculation of
UP frame load and Frame Quality Classification (FQC) are also implemented during
function. It is also responsible for exchange of UP frame load at NAS layer, and filling
and de-filling of UP frame load.
4.4.2 Non-Access Stratum Application

It has the following applications:
l AMR_NB voice code/decode
Implement exchange between AMR_NB voice frame and A_law PCM (G.711).
According to mode indication and mode request of AMR frame, implement
corresponding 8 kinds of rates and codes/decodes to support VAD. Supported rate
standards are shown in Table 4-1.
Table 4-1 AMR_NB Voice Frame Rate Type
Frame Type Index Frame Content (AMR Mode, Comfort Noise or Other)
0 4, 75 kbit/s
1 5, 15 kbit/s
2 5, 90 kbit/s
3 6, 70 kbit/s (PDC-EFR)
4 7, 40 kbit/s (IS-641)
5 7, 95 kbit/s
6 10, 2 kbit/s
7 12, 2 kbit/s (GSM EFR)
8 AMR comfort noise frame
15 No transmission/no reception
There is no requirement for rates with Frame Type Index as 9, 10, 11, 12, 13, 14.
AMR_NB frame structure satisfies definition of TS26.101, as shown in Figure 4-7.
4-8

Figure 4-7 AMR_NB Frame Structure
l Circuit bearer data service

It works together with MPB to implement multimedia data service and traditional circuit
data service.
4.4.3 Bearer Function

Supported Functions
ZXUN iMG supports the following bearer functions:
l HDLC driving: Contain E1 driving and HW driving, and also supports 64 K timeslot
channel and super-channel (used for 2 M link).
l AAL2 SAR: Conduct AAL2 data adaptation during ATM bearer, and conduct data
packet and encapsulation processing.
l IP: Support to conduct data bearer transmission in the form of standard IP, and support
IP/UDP/RTP bearer externally.
RTP Processing Module

The RTP processing module accomplishes RTP protocol processing in compliance with
the regulation of RFC1889 specification. RTP is used to bear real-time data packet in IP
packet based network and detect and report transmission quality, and used for data bearer
on UP plane of Nb logical interface in MGW.
RTP Functions
RTP functions include:
l Point-to-point data transmission:
The RTP processing module works together with UDP to implement functions of
transport layer, including:
RTP load encapsulation
4-9

sequence number management

timestamp management
UDP encapsulation
CRC check
solution to SSRC conflict
transmission quality (sequence error and packet discard) detection
discrimination, sorting and buffer of the type of load
l Detection and report of data transmission quality
The RTP processing module checks the validity of RTCP packet, transmits sender
reports and receiver reports, and processes interval jitter evaluation.
4.4.4 Interworking Between the IM-MGW and the CS

Coding/Decoding Types
The coding/decoding types supported by the IM-MGW voice service include G.729, G.723,
G.711 and AMR.
The frame format of G.729, G.723 and G.711 is same with that of the VoIP network.
The AMR coding needs to encapsulate some message heads (RFC 3267), and sends them
over RTP, which equals the transparent AMR service mode. This mode has no initialization
procedure.
Interworking with CS (Interworking between Mb and Nb)

The Mb interface is the interface between the IM-MGW and the MRFP , the Nb interface
is the interface between the MGW and the IM-MGW.
The interworking between the Mb interface and the Nb interface is shown in Figure 4-8.
Figure 4-8 Interworking Between the Mb Interface and the Nb Interface (Suppose the
Code Configurations of Two Parties are the Same)
The features of the interworking between the Mb interface and the Nb interface are
described in seven aspects:
4-10

l Initialization
There is no initialization procedure between the Nb interface and the Mb interface of
the IM-MGW, that is, the Mb interface does not support the initialization procedure.
l Rate adjust
In the case of multi-rate configuration, the Nb interface has the rate adjust procedure.
The CMR field in the RFC 3267 protocol is used at the Mb interface to provide in-band
rate adjust. After receiving the CMR field from the Mb interface, the IM-MGW needs
to construct the Nb-interface rate adjust frame to send out.
l Time adjust
The Mb interface has no time adjust function, so it needs to respond to the NACK
frame after receiving the time adjust frame from the Nb interface.
l Frame quality
The mapping relationship between the Qbit field of the Mb interface and the FQC field
of the Nb interface is shown in Table 4-2 and Table 4-3.
Table 4-2 Mapping of Mb (Q bit) onto Nb (FQC)
Mb - Qbit Mb - FT Nb - FQC
1 x 0
0 x 1
Table 4-3 Mapping Nb onto Mb
Nb - FQC Mb - Qbit Mb FT
0 1 NC
1 0 NO_DATA
2 0 NC
l Frame encapsulation
The RFC 3267 is used to encapsulate the AMR frame at the Mb interface, while
the 3GPP Nb interface protocol encapsulation is adopted at the Nb interface. The
IM-MGW implements conversion between protocols. When the Nb is over TDM, there
is no corresponding frame format, with 64 K PCM transmission.
l Coding/decoding conversion
When the coding/decoding at the Mb interface is consistent with that at the Nb
interface, TC does not need to be inserted to perform coding/decoding conversion;
otherwise, insert TC to perform coding/decoding conversion.
l Codec related
When the compatible coding/decoding is used at the Mb interface and the Nb
interface, conversion can be avoided; otherwise, conversion needs to be performed.
4-11

4.4.5 Interworking Between the IM-MGW and the PSTN

Coding/Decoding Types
The coding/decoding types supported by the IM-MGW voice service include G.729, G.723,
G.711 and AMR.
The frame format of G.729, G.723 and G.711 is the same with that of the VoIP network.
The AMR coding needs to encapsulate some message heads (RFC 3267), and sends them
over RTP, which equals the transparent AMR service mode. This mode has no initialization
procedure .
Interworking with PSTN (Interworking between Mb and Ai)

The Mb interface is the interface between the IM-MGW and the MRFP , the Ai interface is
the interface between the IM-MGW and the PSTN, based on the TDM connection.
The interworking between the Mb interface and the Ai interface is shown in Figure 4-9.
Figure 4-9 Interworking Between the Mb Interface and the Ai Interface
As shown in Figure 4-9, the IP flow is terminated in the IM-MGW. The AMR is converted to
be of the G.711 coding format, and sent out through the TDM network. For the TDM flow
is converted to the AMR coding through coding the TDM flow within a certain of sampling
duration (such as 20 ms) and sent out through the IP packet.
4.4.6 MRFP Providing IMS AS with Tone Playing Function

Some IMS ASs have the ability of the SIP service control, but cannot independently provide
the processing and control function of the media plane, such as tone playing of the IMS,
DTMF receiving number, and multiparty service. Therefore, the MGW acts as an MRFP
to cooperate with the IMS AS to complete these functions. The IMS AS applies for the
resources of the MGW through the H.248 interface. The MRFP externally provides the
standard interface of the IMS media plane Mb interface.
The MRFP function can be independently configured in a physical MGW. With the help
of the capability of the Virtual Media Gateway (VMGW), the MRFP also can be combined
with the IM-MGW and the R4 MGW in a physical MGW to share media resources. Each
4-12

VMGW independently implements the registration of the MG on the corresponding MGC

(or IMS AS/MGCF/MSCS) through the H.248 interface. Each MGC node applies for and
controls the corresponding media resources on the VMGW registering to the local NE.
4.4.7 VIG Implementing Video Interworking Between CS and IMS

Functioning as a VIG, the MGW implements the video interworking between CS and IMS.
It supports encoding and decoding speech including G.729, G.723.1, G.711, and AMR,
and video encoding and decoding including H.263, MPEG4, and H.264.
Figure 4-10 shows the media-plane protocol stack inside a VIG.
Figure 4-10 Diagrammatic Drawing of Protocol Stack for Video Interworking Between
CS and IMS
4.5 Built-in Signaling Gateway Function

Overview
ZXUN iMG supports the built-in Signaling Gateway (SGW) function, providing signaling
interfaces from the SGW to the PSTN, PLMN and the IP network, supporting adaptation
and forwarding of signaling in the UMTS access network, and supporting adaptation and
forwarding of signaling in external PSTNs.
From the software function, ZXUN iMG provides the function of forwarding the signaling
messages from the PSTN/PLMN to the IP network, and node interworking NIF function.
Each signaling processing layer of the separated SGW has no upper-layer users, and
messages are not submitted. However, some signaling messages received by the MGW
are provided to the user of the local module, such as ALCAP, and these signaling messages
need to be submitted by the signaling layer.
Implementation Method
For the RANAP signaling from the UMTS access network, it introduces the signaling from
the UMTS access network based on RANAP/SCCP/MTP3b/SAAL/ATM protocol stack,
4-13

and forwards the signaling based on the RANAP/SCCP/M3UA/SCTP/IP protocol stack to

ZXWN MSCS.
For the SS7 signaling from an external PSTN, it introduces the signaling based on
SS7/MTP3/MTP2 protocol stack, and forwards the signaling to ZXWN MSCS based on
the SS7/M3UA/SCTP/IP protocol stack.
4.6 VMGW Function

Feature Description
One physical MGW can be divided into several different virtual MGWs (VMGW) from the
logical aspect. Each VMGW is identified by the VMGW ID, which is managed by different
MSCSs. The bearer resource of the MGW equipment can be allocated to different VMGWs
in the manner of resource monopolization or resource sharing, and thus the flexibility of
the equipment is improved. The VMGW function can reduce the network construction cost
of operators, and also can enable the running of virtual operators.
In the default case, all MGWs are embodied by VMGW. For a single MGW, the system
considers it as a special instance of VMGW, and the VMGW ID needs to be configured.
One physical MGW can be divided into several VMGWs. Each VMGW can share the
resource of the physical MGW. From the aspect of MGC, each VMGW is an independent
and complete MG, so it has its own signaling point, physical terminal group, and logical
terminal group. However, other resources are shared instead of being statically allocated.
If one MGW is not divided into multiple VMGWs, it is one VMGW, which is a special instance
of VMGW.
Caution!
The terminal resources at the physical gateway can be divided into physical terminal and
temporary terminal. Only temporary terminals can be shared, while physical terminals
cannot.
Typical Networking Diagram

Figure 4-11 shows the typical networking diagram of implementing the VMGW function.
4-14

Figure 4-11 Typical Networking of VMGW
The configuration for implementing the VMGW function contains two aspects:
configuration on the MSCS and configuration on the MGW.
Where, the VMGW configuration on the MGW mainly contains the following two items:
l Basic information of the MGW: Defining the ID and other information of the VMGW to
identify it.
l Basic information of the Media Gateway Controller (MGC): Defining the corresponding
relationship between each VMGW and the MSCS where it is registered.
As shown in Figure 4-11, one physical MGW is divided into VMGW 1 and VMGW 2. Where,
VMGW 1 is registered in MSC Server 1, while VMGW 2 is registered in MSC Server 2.
4-15

4-16

Chapter 5
Networking Applications
Table of Contents
Networking Modes......................................................................................................5-1
Networking as an End Office (VMGW)........................................................................5-1
Networking as a Gateway Office (GMGW)..................................................................5-2
Networking as an End Office and Gateway Office Combination ..................................5-3
Networking as a Tandem Office (TMGW)....................................................................5-3
Networking by Being Combined with the ZXWN MSCS to a MSC NE in a GSM
Network......................................................................................................................5-4
Networking as an IM-MGW ........................................................................................5-5
Networking as an MRFP.............................................................................................5-6
Networking as a VIG ..................................................................................................5-6
Dual-Homing Networking Mode ..................................................................................5-7
MSC Pool Networking Mode.......................................................................................5-8
5.1 Networking Modes

In R4 stage, CS of 3G core network adopts the architecture with separation of control and
bearer. As a bearer device, ZXUN iMG implements (G)MSC function of the mobile core
network together with ZXWN MSCS.
ZXUN iMG supports the following networking modes:
l Networking as an end office VMGW
l Networking as a gateway office Gateway MGW (GMGW)
l Networking with the combination of an end office and a gateway office
l Networking as a Tandem MGW (TMGW)
l Networking by being combined with ZXWN MSCS to an MSC NE in the GSM network
l Networking as an IM-MGW
l Networking as an MRFP
l Networking as a VIG
l Dual-home networking
l MSC Pool networking
5.2 Networking as an End Office (VMGW)

Networking Diagram
ZXUN iMG used as end office VMGW in the networking structure is shown in Figure 5-1.
5-1

Figure 5-1 End Office VMGW in Networking Structure
Provided Interfaces
In case of an end office, ZXUN iMG provides Mc interface, A interface circuit interface,
Iu-CS user plane interface, Iu-CS bearer control signaling interface and Nb interface.
5.3 Networking as a Gateway Office (GMGW)

Networking Diagram
ZXUN iMG used as a gateway office GMGW in networking structure is shown in Figure
5-2.
Figure 5-2 Gateway Office GMGW in the Networking Structure
Provided Interfaces
In case of a gateway office, ZXUN iMG provides Mc interface, Nb interface and Ai interface.
If Nb interface bears through AAL2, ALCAP bearer control signaling is also provided.
5-2

Chapter 5 Networking Applications
5.4 Networking as an End Office and Gateway Office

Combination
Networking Diagram
ZXUN iMG used as the combination of end office and gateway office in the networking
structure is shown in Figure 5-3.
Figure 5-3 Combination of End Office and GMGW in a Networking Structure
Provided Interfaces
In case of a combination of end office and gateway office, ZXUN iMG provides Mc
interface, Nb interface, Ai interface, Iu-CS interface, A interface and bearer control
signaling interface.
5.5 Networking as a Tandem Office (TMGW)

Overview
ZXUN iMG can be in the network as a TMGW, used for bearing toll traffic.
Networking Diagram
ZXUN iMG used as a TMGW in the networking structure is shown in Figure 5-4.
5-3

Figure 5-4 Typical Networking Scheme of TMGW
Provided Interfaces
In case of a TMGW, ZXUN iMG provides the interfaces with the following NEs:
l Mc interface with the Tandem MSC (TMSC) server, with the bottom layer bearer based
on ATM/IP.
l Nb interface with the TMGW in another region, with the bottom layer bearer based on
ATM/IP/TDM, for bearing services between regions. In Figure 5-4, the Nb interface is
based on the IP bearer.
l Ai interface with the 2G MSC in the same region, based on the TDM bearer. The
interface between MGWs in the same region is Nb interface, with the bottom layer
bearer based on ATM/IP/TDM.
5.6 Networking by Being Combined with the ZXWN

MSCS to a MSC NE in a GSM Network
Descriptions
Combining with ZXWN MSCS, ZXUN iMG can be used as a single NE equipment of ZXWN
MSC or any combination of VMSC/TMSC/GMSC networking entities in a GSM network.
5-4

Implementation Method
If ZXUN iMG is used as tandem office equipment in a GSM network, media bearer can
be implemented in IP or TDM network. In IP bear networking structure, TDM network of
GSM is liable to be evolved into IP packet network gradually. In addition, mobile softswitch
architecture in standard R4 mode adopted by ZXWN MSC is liable for the evolution of GSM
to UMTS core network.
5.7 Networking as an IM-MGW

Description
For the IMS system, one MGCF/IM-MGW must be configured to serve as the interworking
gateway between the IMS network, and CS and PSTN networks. The IM-MGW can be
combined with the GMGW or set separately.
Networking Diagram
Typical networking of the IM-MGW is shown in Figure 5-5.
Figure 5-5 Typical Networking Structure of the IM-MGW
Provided Interfaces
As an IM-MGW, the MGW provides the following interfaces:
l Nb interface with the R4CS: Its bottom layer can be based on TDM/ATM/IP, and it is
used for interworking with the CS Gateway.
l Mb interface with the IMS bearer: Its bottom layer is based on IP, and it is used for
interworking with the IMS Gateway.
l Mn interface with the MGCF: Adopting the H.248 protocol, it is used for the MGCF to
control the IM-MGW.
5-5

5.8 Networking as an MRFP

In the current IMS network, the MGW serves as tone playing equipment to implement
the MRFP tone playing, tone Transcoding and monitoring functions. Figure 5-6 shows its
position in the network.
Figure 5-6 Position of MGW/MRFP in an IMS Network
The MGW (MRFP) is controlled by the PSTN/ISDN Simulation Subsystem (PSS) to

implement the media tone playing of the IMS and the Transcoding, conference and
monitoring functions of tone media.
5.9 Networking as a VIG

Description
Because IMS networks are different from CS networks in session and transport protocols
on video communication, interworking between them must be implemented based on the
VIG gateway. The VIG gateway is responsible for transfer of the video phone signaling
between the CS networks and the IMS networks. The ISUP/BICC protocol is used between
the VIG gateway and the CS network. The SIP protocol is used between the VIG gateway
and the IMS network. In addition, the VIG gateway is responsible for conversion of speech
and video encoding and decoding between mobile terminals and IP terminals.
Networking Modes
Figure 5-7 shows a networking scheme of the VIG gateway in the entire system.
Cooperating with the entities (CSCF and BGCF) in the IMS network and the entities (MSC,
MSC Server, and MGW) in the CS domain, the VIG gateway implements interworking
between the IMS domain and the control plane and user plane in the CS domain.
5-6

Figure 5-7 VIG Networking Mode
The VIG gateway support the Mg and Mj interfaces based on the SIP protocol. It correctly
routes the calls entering the IMS domain from the CS domain to S-CSCF or I-CSCF through
the Mg interface.
The VIG supports the call control interfaces based on the ISUP/BICC protocol. It correctly
routes the calls entering the CS domain from the IMS domain.
5.10 Dual-Homing Networking Mode

Background
In the R4 networking, the MSC equipment is divided into the control-plane-based MSC
Server and the bearer-plane-based MGW. The MSC Server is only responsible for
processing signaling and services on the control plane in the mobile network. With more
single and centralized processing function, the capacity and the integration level of the
MSC Server are essentially improved through being compared with the MSC with bearer
combined with control. The MGW is only responsible for functions on the media plane.
After a large-capacity MSC Server is used, the reliability of the MSC Server greatly affects
the reliability of the network. Therefore, the dual-homing network emerges.
Concept
In a dual-homing network, one standby MSC Server is configured for the active MSC
Server. When the active MSC Server is faulty, the standby one will take over the services
from the active MSC Server to keep the normal running of services. When the original
active MSC Server is restored to be normal, the services will be switched back to the
original active MSC Server.
In the dual-homing network, one MGW needs to establish links with two MSC Servers, but
only one link between the MGW and one MSC Server is activated at the same time.
5-7

Networking Diagram
ZXUN iMG supports the dual-homing networking, that is, the MGW simultaneously
connects with the active and standby MSC Servers. The schematic diagram of a
dual-homing network is shown in Figure 5-8.
Figure 5-8 Dual-Homing Networking Structure
5.11 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 to only one serving MSC Server in a traditional network. In
a MSC Pool network, one BSC/RNC can connect to multiple serving MSC Servers. These
serving MSC Servers compose one resource pool, providing services to the connected
BSC/RNC.
Networking Mode
In the MSC Pool networking mode, the signaling from one BSC/RNC to multiple MSC
Servers is accessible, and all MSC Servers in a MSC Pool together serve all BSC/RNCs
in this MSC Pool.
The BSC/RNC can switch the signaling to each MSC Server in the MSC Pool through one
MGW, as shown in Figure 5-9. The BSC/RNC can connect to each MGW in the MSC Pool
to transfer signaling to the corresponding MSC Server, as shown in Figure 5-10.
5-8

Figure 5-9 MSC Pool Networking Mode (1)
Figure 5-10 MSC Pool Networking Mode (2)
5-9

5-10

Chapter 6
Technical Specifications
Table of Contents
Product Specifications ................................................................................................6-1
Component Specifications..........................................................................................6-4
6.1 Product Specifications

The main specifications of ZXUN iMG product include:
l Power supply specifications
l Interface specifications
l Clock specifications
l Reliability specifications
l Performance specifications
6.1.1 Power Supply Specifications

Table 6-1 lists the power supply specifications of ZXUN iMG.
Table 6-1 Power Supply Specifications of ZXUN iMG
Parameter Specification
Rated voltage -48 V DC
Voltage fluctuation range -57 V DC to 40 V DC
Maximum power consumption 7 kW
6.1.2 Interface Specifications

Table 6-2 lists the adopted standards and supported cable types of ZXUN iMG interfaces.
Table 6-2 Adopted Standards and Supported Cable Types of ZXUN iMG Interfaces
Interface Type Physical Standard Cable Type
Mc/Mn/Mp 10/100/1000 Mbps adaption super category-5 shielded twisted pair

1000Base-X Fiber jumper LC/PC-LC/PC
Nb/Mb 10/100/1000 Mbps adaption super category-5 shielded twisted pair

6-1

Interface Type Physical Standard Cable Type
Iu-CS 10/100/1000 Mbps adaption super category-5 shielded twisted pair

STM-1 Fiber jumper LC/PC-LC/PC
A E1 Coaxial cable
Ai E1 Coaxial cable
6.1.3 Clock Specifications

Table 6-3 lists the clock specifications for ZXUN iMG.
Table 6-3 Clock Specifications for ZXUN iMG
Clock level Stratum 2 class A clock
Lowest clock accuracy 4 10-7
Pull-in range 4 10-7
Maximum frequency deviation 10-9/day
Initial maximum frequency deviation 5 10-10
Clock working mode Catch, Trace, Hold and Free
Clock synchronization mode External clock synchronization, extracting clock

from service code streams, and internal clock
synchronization
Clock synchronization interface 2MBITS: 2

Line clock: 2
6.1.4 Reliability Specifications

Table 6-4 lists the reliability specifications for ZXUN iMG.
Table 6-4 Reliability Specifications for ZXUN iMG
System availability >99.9998 %
Mean Time Between Failures (MTBF) >55 years
System Mean Time to Repair (MTTR) <1 h
Basic failure rate 0.000002/h
6-2

Chapter 6 Technical Specifications
Annual average interruption duration <2 min
Active/standby changeover success rate 99 %
Active/standby board GPBB0 <6 s

changeover time
Other boards <500 ms
Board restart duration GPBB0 and GPBX1 <3 min
BSWA0, TSWA0, an FSWA1 <30 s
DTIA0, DTIA1, APIA0, APIA1, IPIA0, <1 min

IPIA1, MPBA0, and MPBA1
Restart duration of a single E8280 <5 min

shelf
Restart duration of a single rack <6 min
Restart duration in full configuration <8 min
6.1.5 Performance Specifications

Table 6-5 lists the performance specifications for ZXUN iMG.
Table 6-5 Performance Specifications for ZXUN iMG
Technical Feature Parameter Specification
Maximum number of TDM MGW TDM: 170 k

trunks
IP/TDM MGW TDM: 100 k TDM trunk
IP: 100 k equivalent IP trunk
ATM/IP MGW ATM (Iu-CS) <->IP (Nb)

ATM: 81 k equivalent IP trunk
IP: 75 k equivalent trunk
IP/IP MGW IP: 300 k equivalent trunk
Maximum traffic TDM MGW 68 kErl
IP/TDM MGW 100 kErl
ATM/IP MGW 75 kErl
IP/IP MGW 150 kErl
Switching network IP switching capacity 144 GB

capacity
TDM switching capacity 384 k384 k
6-3

Technical Feature Parameter Specification
Signaling specification Number of narrowband 64 kbps links 5760
Number of narrowband 2 Mbps links 384
Number of broadband SCTP links 4096
Number of multiple signaling point 256

codes
Office capacity Number of office directions 2048
Number of BSCs supported 256
Number of RNCs supported 256
Interface specifications TDM MGW 1280 E1 or 88 pairs of STM-1
IP/TDM MGW 1152 E1 or 64 pairs of STM-1

40GE
ATM/IP MGW 36 STM-1

24 GE
IP/IP MGW 96 GE
Table 6-6 lists the traffic model that the above performance specifications.
Table 6-6 Reference Traffic Model
Mobile subscriber average busy hour traffic 0.025 Erl
Busy hour call attempts 1.5 attempts/subscriber
Trunk average busy hour traffic 0.8 Erl
Trunk average busy hour call attempts 48/busy hour/incoming call circuit
6.2 Component Specifications

The component specifications of ZXUN iMG include:
l Specifications for the operation & maintenance module

l Specifications for the power module
l Specifications for the environment monitoring module
l Specifications for fan unit modules
l Specifications for board power consumption
l Specifications for the alarm box
6-4

6.2.1 Specifications for the Operation & Maintenance Module

General Feature
The OMM server and Local Maintenance Terminals (LMT) jointly implement the operation
and maintenance of ZXUN iMG. The GPBX1 board is a high-performance blade server,
functioning as the OMM server. It is equipped with dual-channel four-core CPU, 8 GB of
RAM, and two SAS hard disks of 146 GB. The LMT terminals are common computers.
Specifications
Table 6-7 lists the technical specifications for the operation & maintenance module.
Table 6-7 Technical Specifications for the Operation & Maintenance Module
Item Specification
Number of the maximum online LMT terminals performing 30

operations at the same time
Number of MML commands processed at the same time >10 commands/s
MML command processing response delay <1 s
Alarm report processing capability 50 alarms/s to 80 alarms/s
Alarm processing delay <5 s
Performance data warehousing capability 300 pieces/s to 600 pieces/s
Performance data processing delay <5 min
Duration of the NE downloading the software version <5 min
Duration of the NE downloading the software patch <5 min
Communication link fault detection delay <2 s
NE alarm synchronization delay <30 s
Storage capability of historical alarm data >1 month
Storage capability of historical performance data >15 days
Storage capability of historical operation logs >1 month
System availability >99.9997 %
Mean Time Between Failures (MTBF) 400,000 h
Mean Time to Repair (MTTR) <60 min
Annual average interruption duration <30 min
Restart duration of the OMM server <5 min
Bandwidth of the interface between the OMM server and the >64 kbps
upper-level Network Management System (NMS)
Bandwidth of the interface between the OMM server and the >128 kbps
LMT terminal (FE interface)
6-5

Item Specification
Delay of the first times of logging in the server (LMT terminal) <40 s
Delay of re-logging in the server after logout (LMT terminal) <10 s
Delay of starting the configuration window (LMT terminal) <10 s
Delay of starting the fault management window (LMT terminal) <10 s
Delay of starting the performance statistics window (LMT <30 s

terminal)
Delay of querying the historical record operations (LMT <10 s

terminal)
Rated voltage of the OMM server -48 VDC
Voltage fluctuation range of the OMM server -40 VDC~-57 VDC
6.2.2 Specifications for the Power Module

Table 6-8 lists the technical specifications for the power module.
Table 6-8 Technical Specifications for the Power Module
Checked Item DC Power of the Switch
Nominal value -48 V
Voltage range -57 V to -40 V
Noise voltage 0 Hz to 300 Hz 100 mV (peak-peak value)
300 Hz to 3,400 Hz 2 mV (noise meter weighting noise)
3.4 kHz to 150 kHz Single frequency 5 mV (valid value);

broadband 100 mV (valid value)
150 kHz to 200 kHz Single frequency 5 mV (valid value);

200 kHz to 500 kHz Single frequency 3 mV (valid value);

500 kHz to 30 MHz Single frequency 1 mV (valid value);

6.2.3 Specifications for the Environment-Monitoring Module

Table 6-9 lists the technical specifications for the environment-monitoring module.
6-6

Table 6-9 Technical Specifications for the Environment-Monitoring Module
Checked Item Range
Smoke sensor alarm protection 60 m2/sensor

range
Infrared alarm protection range 15 m radius 90 sector/sensor
Flooding alarm detection range 10 mm to 1,000 mm
Temperature detection range 0 to 50 (frequency output: 1 kHz to 1.5 kHz), with the
measurement precision being 0.5
Humidity detection range 20% to 100% (frequency output: 1 kHz to 2 kHz, corresponding
to 0% to 100%), with a measurement precision of 3%
Fan rev detection range 0 revolution per minute to 5,000 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
-48 V power lower limit alarm Can be set by the program (by default, it is -40 V), with a
Fan revolution speed alarm Can be set by the program (by default, it is 80% of the rated
revolution speed)
6.2.4 Specifications for the Fan Unit Module

Table 6-10 lists the technical specifications for the fan unit module.
Table 6-10 Specifications for Fan Unit Modules
Category Item Technical Specification
Mechanical spec- Dimensions Front fan module: 437.2 mm321.91 mm43.6 mm

ifications (WidthDepthHeight)
Rear fan module: 435.2 mm275.71 mm42.6 mm
(WidthDepthHeight)
Number of fans Front fan subrack: six fan modules (per subrack)
Rear fan subrack: eight fan modules (per subrack)
Electrical charac- Power consump- Front fan subrack: 300 W (per subrack)
teristics tion Rear fan subrack: 218 W (per subrack)
6-7

6.2.5 Specifications for Board Power Consumption

Table 6-11 lists the power consumption of each boards of ZXUN iMG.
Table 6-11 Board Power Consumption
Board Name Power Consumption (at 70% CPU Usage)
GPBB0 160 W
GPBX1 145 W
MPBA0 175 W
MPBA1 120 W
IPIA0 65 W
IPIA1 65 W
DTIA0 60 W
DTIA1 70 W
SDIA0 80 W
SDIA1 80 W
BSWA0 65 W
FSWA1 55 W
TSWA0 70 W
APIA0 70 W
APIA1 70 W
6.2.6 Specifications for the Alarm Box

Table 6-12 lists the technical specifications for the alarm box of ZXUN iMG.
Table 6-12 Technical Specifications for the Alarm Box
Category Item Index Contents
Interfaces and Communication One RJ45 network interface, used to connect with the
peripheral interfaces background server.
equipment
One RS-232 serial interface, used for debugging the
alarm box.
Alarm indicators There are four alarm indicators on the panel, which are
yellow, orange, blue, and red respectively, and indicate
different alarm levels in ascending order.
Buttons There are nine buttons on the panel, which respectively

are:
6-8

Category Item Index Contents
l Up (moving the menu bar, and increasing the IP

address and port)
l Down (moving the menu bar, and decreasing the IP
address and port)
l Left (moving the cursor)
l Right (moving the cursor)
l OK (Confirming the operational result)
l MENU (functional key for opening main menu)
l C (Cancel, Return key for returning to the previous
level menu)
l Reset (Reset hole for resetting the alarm box)
l ACK (Confirm key for acknowledging the alarm
reported by the alarm server)
Speaker One speaker, used for giving audio alarms.
Power and Power The alarm box uses -48V DC power, and can extract
grounding power directly from the rack. It also supports 90V264V
AC power with an assorted power adapter.
Grounding The PCB is grounded through the grounding bolt.
- Power 40 W
consumption
- Size 323 mm (Length) 220 mm (Width) 58 mm (Height)
- Environment 0C to 45C
temperature
6-9

6-10

Chapter 7
Environmental Requirements
Table of Contents
Grounding Requirements ...........................................................................................7-1
Temperature and Humidity Requirements...................................................................7-1
Cleanness Requirements ...........................................................................................7-2
Air Pollution Requirements .........................................................................................7-2
7.1 Grounding Requirements

Types of Grounding Cables
ZXUN iMG has three types of grounding cables, which are:
l -48 VGND (-48 V ground)
l GNDP (System protection ground)
l GND (Working ground)
Grounding mode
ZXUN iMG adopts the joint grounding mode, which is described as follows:
l GNDP and GND are connected to shelves with structural parts inside the shelves,
and connected to the DC grounding post with the bus bar.
l Provided through the primary power supply, -48 VGND cable is not connected to the
GNDP, GND or the rack inside the rack.
Grounding Resistance
The grounding resistance of ZXUN iMG should be less than 1 .
7.2 Temperature and Humidity Requirements

Table 7-1 lists the requirements of ZXUN iMG for temperature and humidity.
Table 7-1 Requirements for Temperature and Humidity
Item Short-term Operating Condition Long-term operating Condition
Temperature 5 to 40 -5 to 40
Relative humidity 5% to 90% 5% to 85%
7-1

Note:
l The temperature and humidity inside the equipment room are measured at a spot
that is 1.5 m above the floor and 0.4 m in front of equipment rack when there is no
protective plate at front or back of the rack.
l The short-term operating condition means that the continuous operation period of the
equipment is no more than 96 hours, and the accumulated operation period in a year
is not more than 15 days.
7.3 Cleanness Requirements

For a dust particle with a diameter greater than 5 m, the concentration should be less
than or equal to 3104 particles/m3.
7.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.
7-2

Glossary
AAL5
- ATM Adaptation Layer type 5
AMR
- Adaptive Multiple Rate
ATCA
- Advanced Telecommunications Computing Architecture
ATM
- Asynchronous Transfer Mode
BGCF
- Breakout Gateway Control Function
BITS
- Building Integrated Timing Supply
BRS
- Bearer Subsystem
BSC
- Base Station Controller
CORBA
- Common Object Request Broker Architecture
CSCF
- Call Session Control Function
CSD
- Circuit Switched Data
DBS
- Database Subsystem
DTMF
- Dual-ToneMulti-Frequency
EMS
- Network Element Management System
ETCA
- Enhanced ATCA
FQC
- Frame Quality Classification
GMGW
- Gateway MGW
I
GSM
- Global System for Mobile Communication
I-CSCF
- Interrogating-Call Session Control Function
IM-MGW
- IP Multimedia-Media Gateway
IMS
- IP Multimedia Subsystem
IP
- Internet Protocol
IPMI
- Intelligent Platform Management Interface
IWF
- InterWorking Function
LMT
- Local Maintenance Terminal
LTE
- Long Term Evolution
MCS
- Multicore and MicroCode Media Carring Subsystem
MFC
- Multi-Frequency Control
MGC
- Media Gateway Controller
MGCF
- MediaGateway Control Function
MTBF
- Mean Time Between Failures
MTTR
- Mean Time To Repair
NE
- Network Element
NMC
- Network Management Center
NMS
- Network Management System
PCM
- Pulse Code Modulation
II
Glossary
PDU
- Power Distribution Unit
PSS
- PSTN Simulation Service
PSTN
- Public Switched Telephone Network
PVC
- Permanent Virtual Circuit
RAB
- Radio Access Bearer
RNC
- Radio Network Controller
RNS
- Radio Network Subsystem
S-CSCF
- Serving-Call Session Control Function
SCS
- System Control Subsystem
SGW
- Signaling GateWay
SIG
- SIGnal
SIGTRAN
- Signalling Transport
SNMP
- Simple Network Management Protocol
SODA
- Service Oriented Driver Architecture
SS7
- Signaling System No. 7
STP
- Signaling Transfer Point
TDM
- Time Division Multiplexing
TFO
- Tandem Free Operation
TMGW
- Tandem MGW
III
TMN
- Telecommunications Management Network
TMSC
- Tandem MSC
TULIP
- Telecom Universal Integrated Platform
TrFO
- Transcoder Free Operation
UMTS
- Universal Mobile Telecommunication System
VIG
- Video Interactive Gateway
VMGW
- Virtual Media Gateway
kbps
- kilo-bits per second
IV

SJ-20110412153554-002-ZXUN iMG (MGW - W) (V4.10.20) Media Gat

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

SJ-20110412153554-002-ZXUN iMG (MGW - W) (V4.10.20) Media Gat

Încărcat de

Drepturi de autor:

Formate disponibile

ZXUN iMG (MGW_W)

Revision No. Revision Date Revision Reason

R1.2 2011-10-15 Update the section of 3.10

R1.1 2011-05-30 Added contents related to VIG.

R1.0 2011-04-30 First edition.

Serial Number: SJ-20110412153554-002

Publishing Date: 2011-10-15 (R1.2)

Chapter 2 System Architecture ................................................................. 2-1

Chapter 3 Interfaces ................................................................................... 3-1

Chapter 4 Service Functions ..................................................................... 4-1

Chapter 5 Networking Applications.......................................................... 5-1

Chapter 6 Technical Specifications .......................................................... 6-1

Chapter 7 Environmental Requirements .................................................. 7-1

What Is in This Manual

Chapter 2, System Architecture Describes the system architecture of ZXUN iMG.

Chapter 3, Interfaces Describes the interfaces used in ZXUN iMG.

Chapter 4, Service Functions Describes the service functions of ZXUN iMG.

Chapter 5, Networking Applications Describes the networking applications of ZXUN iMG.

Chapter 6, Technical Specifications Describes the technical specifications of ZXUN iMG.

Chapter 7, Environmental Requirements Describes the environmental requirements of ZXUN iMG.

FCC Compliance Statement

Italics References to other manuals and documents.

Quotes Links on screens.

Note: Provides additional information about a certain topic.

Checkpoint: Indicates that a particular step needs to be checked before

Tip: Indicates a suggestion or hint to make things easier or more productive

1.1 Location of ZXUN iMG in a Network

SJ-20110412153554-002|2011-10-15 (R1.2) ZTE Proprietary and Confidential

Figure 1-1 Location of ZXUN iMG in a GSM/UMTS Mobile Soft-Switch Network

1.2 Main Functions of ZXUN iMG

SJ-20110412153554-002|2011-10-15 (R1.2) ZTE Proprietary and Confidential

the MGW can function as an IM-MGW to implement interworking between an IMS

The MGW supports a variety of data services in a CS domain, including:

SJ-20110412153554-002|2011-10-15 (R1.2) ZTE Proprietary and Confidential

1.3 ZXUN iMG Product Features

1.3.1 Unified ETCA Platform

1.3.2 Strong Cascading Capability

SJ-20110412153554-002|2011-10-15 (R1.2) ZTE Proprietary and Confidential

Figure 1-2 Multi-Shelf Cascade of Media Plane

Figure 1-3 Multi-Shelf Cascade of Control Plane

SJ-20110412153554-002|2011-10-15 (R1.2) ZTE Proprietary and Confidential

Figure 1-4 TDM Interconnection of ZXUN iMG

1.3.3 Variety of Physical Interfaces

SJ-20110412153554-002|2011-10-15 (R1.2) ZTE Proprietary and Confidential

1.3.4 Environmentally Friendly Design

1.3.5 Capability of Smooth Upgrade and Capacity Expansion

1.3.6 Excellent Reliability

SJ-20110412153554-002|2011-10-15 (R1.2) ZTE Proprietary and Confidential

1.3.7 Manageability and Easy Maintenance

l The Browser/Server structure ensures perfect networking capability and scalability of

SJ-20110412153554-002|2011-10-15 (R1.2) ZTE Proprietary and Confidential

1.4 ZXUN iMG Compliance Standard

SJ-20110412153554-002|2011-10-15 (R1.2) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20110412153554-002|2011-10-15 (R1.2) ZTE Proprietary and Confidential

2.1 Hardware Architecture

SJ-20110412153554-002|2011-10-15 (R1.2) ZTE Proprietary and Confidential

Figure 2-1 Cabinet Layout

SJ-20110412153554-002|2011-10-15 (R1.2) ZTE Proprietary and Confidential

Table 2-1 Component Functions

Ventilation subrack Discharges the hot wind out of the cabinet.

2.1.2 Logical Architecture

SJ-20110412153554-002|2011-10-15 (R1.2) ZTE Proprietary and Confidential