ZXG10 IBSC (V6.10) Technical Manual

ZXG10 iBSC
Base Station Controller
Technical Manual
Version 6.10
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn
LEGAL INFORMATION
Copyright 2006 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
Date
Revision No.
Serial No.
Reason for Revision
Apr. 28, 2008
R1.0
sjzl20081436
First edition
Aug. 19, 2008
R1.1
sjzl20081436
Updated
Sep. 25, 2008
R1.0
sjzl20083710
Updated
ZTE CORPORATION
Values Your Comments & Suggestions!
Your opinion is of great value and will help us improve the quality of our product
documentation and offer better services to our customers.
Please fax to: (86) 755-26772236; or mail to Technical Delivery Department, ZTE
University, Dameisha, Yantian District, Shenzhen, Guangdong, P.R. China 518083.
Thank you for your cooperation!
Document
Name
ZXG10 iBSC (V6.10) Base Station Controller Technical Manual
Product Version
V6.10
Document Revision
Number
Serial No.
sjzl20083710
Equipment
Installation Date
R1.0
Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good
Your evaluation
of this
documentation
Fair
Average
Poor
Bad
N/A
Accessibility:
(Contents, Index, Headings, Numbering, Glossary)
Good
Fair
Average
Poor
Bad
N/A
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good
Fair
Average
Poor
Bad
N/A
Please check the suggestions which you feel can improve this documentation:
Improve the overview/introduction
Your
suggestions for
improvement of
this
documentation
Make it more concise/brief
Improve the Contents
Add more step-by-step procedures/tutorials
Improve the organization
Add more troubleshooting information
Include more figures
Make it less technical
Add more examples
Add more/better quick reference aids
Add more detail
Improve the index
Other suggestions
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name
Company
Postcode
Address
Telephone
E-mail
This page is intentionally blank.
Contents
About this Manual ............................................................. i
Purpose ................................................................................ i
Intended Audience ................................................................. i
Prerequisite Skill and Knowledge .............................................. i
What is in This Manual ............................................................ i
Related Documentation.......................................................... ii
Conventions ........................................................................ iii
How to Get in Touch............................................................. iv
Declaration of RoHS Compliance..................................... v

Chapter 1.......................................................................... 1
System Overview ............................................................. 1
System Background .............................................................. 1
Position of iBSC in Network .................................................... 2
System Features................................................................... 3
System Functions ................................................................. 4
Standards Complied ............................................................ 10
Chapter 2........................................................................ 13
System Indices .............................................................. 13
Physical Indices .................................................................. 13
Clock Indices...................................................................... 14
Power Supply Indices .......................................................... 15
Environmental Conditions..................................................... 15
Reliability Indices................................................................ 16
Interface Indices................................................................. 17
Capacity Indices ................................................................. 18
Chapter 3........................................................................ 21
System Architecture ...................................................... 21
System Composition............................................................ 21
Hardware System................................................................21
Shelves..............................................................................23
Boards...............................................................................23
Software System.................................................................25
Chapter 4........................................................................ 29
Interfaces and Protocols ............................................... 29
External Interfaces ........................................................ 29
A-Interface.........................................................................31
Ater Interface (TC is External)............................................... 31
Abis Interface .....................................................................31
Gb Interface .......................................................................32
Foreground-Background Interface..........................................32
Protocols ..................................................................... 32
Protocols in CS domain ........................................................32
Protocols in PS Domain ........................................................37
Chapter 5........................................................................ 41
Data Flow Direction ....................................................... 41
System Clock Signal Flow .....................................................41
User Plane Data Flow ...........................................................42
Control Plane Data Flow .......................................................44
Chapter 6........................................................................ 47
Networking Modes and System Configuration .............47
Networking Modes......................................................... 47
Abis Interface Networking Modes ........................................... 47
A-Interface Networking Mode ................................................ 51
Ater Interface Networking Mode ............................................ 51
Gb Interface Networking Mode .............................................. 51
Operation and Maintenance System Networking....................... 52
System Configuration .................................................... 55

Cabinet Configuration ..........................................................55
Shelf Configuration ..............................................................57
NM Configuration ................................................................62
Appendix A ..................................................................... 63
Abbreviations ................................................................. 63
Appendix B ..................................................................... 69
Figures............................................................................ 69
Tables ............................................................................. 71
Index .............................................................................. 73
About this Manual

Purpose
The purpose of this manual is to introduce the technical
specifications and working of ZXG10 iBSC (V6.10). In addition,
to provide information about the technology involved in the
designing of ZXG10 iBSC (V6.10) system.
Intended Audience
This document is intended for engineers and technicians who
perform operation activities on the ZXG10 iBSC Base Station
Controller.
Prerequisite Skill and Knowledge

To use this document effectively, users should have a general
understanding of wireless telecommunications technology.
Familiarity with the following is helpful:
The ZXG10 system and its various components
User Interface on Base Station Controller (BSC)
Local operating procedures
What is in This Manual

This manual contains the following chapters.
TABLE 1 M ANUAL SUMMARY
Section
Summary
Chapter 1, System Overview
This chapter describes the

system background, features,
and standards complied in ZXG10
iBSC (V6.10) system.
Chapter 2, System Indices
This chapter describes the

physical, clock, power, capacity,
Confidential and Proprietary Information of ZTE CORPORATION
Section
Summary
and interface indices of ZXG10
iBSC (V6.10).
Chapter 3, System Architecture
This chapter describes the ZXG10

iBSC (V6.10) hardware system,
software system, shelves, and
boards.
Chapter 4, Interfaces and

Protocols
This chapter describes external

interfaces and protocols of
ZXG10 iBSC (V6.10).
Chapter 5, Data Flow Direction
This chapter describes data flows

of the control plane and the user
plane.
Chapter 6, Networking Modes

and System Configuration
This chapter describes about the

networking modes and system
configuration of ZXG10 iBSC
(V6.10).
Appendix A, Abbreviations
List of abbreviations used in this

manual.
Appendix B, Figures and Tables
List of figures and tables included

in this manual.
Index
Index of important terms and

definition in this manual.
Related Documentation
The following documents are related to this manual:
ii
ZXG10 iBSC (V6.10) Base Station Controller Documentation

Guide
ZXG10 iBSC (V6.10) Base Station Controller Hardware
Manual
ZXG10 iBSC (V6.10) Base Station Controller Installation
Manual
ZXG10 iBSC (V6.10) Base Station Controller Performance
Counter Manual Volume I
ZXG10 iBSC (V6.10) Base Station Controller Performance
Counters Manual Volume II
ZXG10 iBSC (V6.10) Base Station Controller KPI Reference
Manual
ZXG10 iBSC (V6.10) Base Station Maintenance Manual
(Troubleshooting)
ZXG10 iBSC (V6.10) Base Station Maintenance Manual
(Emergency Maintenance)
ZXG10 iBSC (V6.10) Base Station Controller Maintenance
Manual (Routine Maintenance)
About this Manual
ZXG10 BSS (V6.10) Base Station Subsystem Alarm Handling

Manual
ZXG10 BSS (V6.10) Base Station Subsystem Notification

Handling Manual
Conventions
Typographical
Conventions
ZTE documents employ the following typographical conventions.

TABLE 2 TYPOGRAPHIC AL CONVENTIONS
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, dropdown lists, dialog box names, window names.
CAPS
Keys on the keyboard and buttons on screens

and company name.
Constant width
Text that you type, program code, files and

directory names.
[]
Optional parameters.
{}
Mandatory parameters.
Select one of the parameters that are delimited

by it.
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.
Mouse
Operation
Conventions
TABLE 3 MOUSE OPERATION CONVENTIONS
Typeface
Meaning
Click
Refers to clicking the primary mouse button (usually

the left mouse button) once.
Double-click
Refers to quickly clicking the primary mouse button

(usually the left mouse button) twice.
Right-click
Refers to clicking the secondary mouse button

(usually the right mouse button) once.
Drag
Refers to pressing and holding a mouse button and

moving the mouse.
iii
How to Get in Touch

The following sections provide information on how to obtain
support for the documentation and the software.
Customer
Support
Documentation
Support
iv
If you have problems, questions, comments, or suggestions

regarding
your
product,
contact
us
by
e-mail
at
support@zte.com.cn. You can also call our customer support
center at (86) 755 26771900 and (86) 800-9830-9830.
ZTE welcomes your comments and suggestions on the quality
and usefulness of this document. For further questions,
comments, or suggestions on the documentation, you can
contact us by e-mail at doc@zte.com.cn; or you can fax your
comments and suggestions to (86) 755 26772236. You can also
browse our website at http://support.zte.com.cn, which contains
various interesting subjects like documentation, knowledge base,
forum, and service request.
Declaration of RoHS
Compliance
To minimize the environmental impact and take more
responsibility to the earth we live, this document shall serve as
formal declaration that the ZXG10 iBSC (V6.10) Base Station
Controller manufactured by ZTE CORPORATION is in compliance
with the Directive 2002/95/EC of the European Parliament RoHS (Restriction of Hazardous Substances) with respect to the
following substances:
Lead (Pb)
Mercury (Hg)
Cadmium (Cd)
Hexavalent Chromium (Cr(VI))
PolyBrominated Biphenyls (PBBs)
PolyBrominated Diphenyl Ethers (PBDEs)
The usage of the above substances in ZXG10 iBSC (V6.10) is

explained in Table 4.
TABLE 4 USAGE EXPLANATION OF THE HAZ ARDOUS SUBSTANCES IN ZXG10
IBSC (V6.10)
Hazardous substances
Names of Parts
Pb
Hg
Cd
Cr(VI)
PBBs
PBDEs
System
Cables and Assembly
Auxiliary Equipment
Table Explanation:
0: The usage of the substance in all of the components is less
than the allowed values given by 2002/95/EC standard.
: The usage of the substance in at least one of the components
is beyond the allowed values given by 2002/95/EC standard.
The ZXG10 iBSC (V6.10) Base Station Controller manufactured

by ZTE CORPORATION meet the requirements of EU
2002/95/EC; however, some assemblies are customized to client
specifications. Addition of specialized, customer-specified
materials or processes which do not meet the requirements of
EU 2002/95/EC may negate RoHS compliance of the assembly.
To guarantee compliance of the assembly, the need for
compliant product must be communicated to ZTE CORPORATION
in written form.
This declaration is issued based on our current level of
knowledge. Since conditions of use are outside our control, ZTE
CORPORATION makes no warranties, express or implied, and
assumes no liability in connection with the use of this
information.
vi
Chapter
System Overview
This chapter contains following topics:
System Background
Position of iBSC in Network
System Features
System Functions
Standards Complied
System Background
The idea of developing ZXG10 iBSC (V6.10) is to improve the
capacity and make it compatible with 3G networks in the future.
ZXG10 iBSC (V6.10) is highly integrated system and has five
times more capacity than ZXG10-BSC (2.96). It provides E1 and
Fast Ethernet based Abis interface, which is a new feature.
ZXG10 iBSC (V6.10) is a part of GERAN (GSM/EDGE Ground
Radio Access Network), which includes one or more BSS.
Structure of iBSC is based on the hardware structure of ZXWR
RNC (WCDMA Radio Network Controller).
Future Usage
ZXG10 iBSC (V6.10) can be upgraded in future to support and

work together with WCDMA. It can work as an intermediate BSC
between the GSM and WCDMA networks. Following features of
GERAN and iBSC can be provided in future:
To provide smooth access to mobile subscribers from

GSM/EDGE network to UMTS.
GERAN can be accepted into the network system of UMTS,
and provides the same service as UMTS network to end users,
including various services such as session, streaming, and
interactivity.
The connection of GERAN with CN (Core Network) through
A/Gb/Iu interfaces.
The connection of iBSC with the WCDMA RNC through Iur-g

interface.
Position of iBSC in Network

When TC is internal, the position of iBSC in the network is shown
in Figure 1.
FIGURE 1 POSITION OF IBSC IN THE NETWORK (TC IS INTERNAL)
When TC is external, the position of iBSC in the network is

shown in Figure 2.
FIGURE 2 POSITION OF IBSC IN THE NETWORK (TC IS EXTERNAL)
GERAN
BSS
Iur-g
MS
Um
Ater
BTS
iTC
iBSC
MS
Gb
GSM/ UMTS Core Network
BTS
Iu
BSS
Iur-g
UTRAN
RNC
Chapter 1 - System Overview
ZXG10 iBSC (V6.10) is a part of GERAN (the GSM EDGE Radio

Access Network). GERAN includes one or multiple BSS, and one
BSS consists of one BSC and one or multiple BTS. BSC is
connected with BTS via Abis interface, and BSC-BSC, BSC-RNC
are connected with each other via Iur-g interface.
If TC is internal, GERAN is connected with GSM/UMTS Core
Network via A/Gb/Iu interface. GERAN has two working modes:
A/Gb mode and Iu mode and can work in these two modes at
the same time. In this case, the 2G MS uses A/Gb working mode,
the working mode used by the MS supporting Iu mode depends
on GERAN and MS together.
System Features
ZXG10 iBSC (V6.10) is the high capacity base station controller
developed by ZTE cooperation independently, and the following
are the main features:
All IP hardware platform

ZXG10 iBSC employs the all IP hardware platform the same
as the 3G products of ZTE Corporation. The hardware
platform based on all IP ensures powerful PS service support
capability and facilitates to realize IP Abis interface and IP Gb
interface.
High capacity and strong processing capability

ZXG10 iBSC (V6.10) supports maximum 1536 sites and 3072
carriers with strong processing capability. High capacity and
strong processing capability can reduce the complexity of
networking, improve network quality and save the
investment on equipment room.
Standard A interface
ZXG10 iBSC (V6.10) provides completely open A interface to
ensure the interconnection of the equipment from different
vendors.
Modularization, easy capacity expansion

ZXG10 iBSC (V6.10) employs modularized design, which
facilitates the capacity expansion. Smooth expansion can be
realized by module overlay.
Flexible networking mode

ZXG10 iBSC (V6.10) supports star, link, tree and ring
networking of Abis interface, and also supports transmission
equipment such as E1, satellite, microwave and optical fiber.
High integration and low power consumption

ZXG10 iBSC (V6.10) is highly integrated and occupies less
area, which saves the investment in the equipment room.
ZXG10 iBSC (V6.10) has low overall power consumption,

which reduces the operators investment on auxiliary power
and air conditioning.
High reliability
The key components of ZXG10 iBSC (V6.10) employs 1+1
redundancy backup, which increases the system reliability.
System Functions
ZXG10 iBSC (V6.10) supports the service functions of base
station controller in GSM Phase II and Phase II+ standards. Its
main functions are as follows:
Supports GSM 900, GSM 850, GSM 1800 and GSM 1900
network.
Supports the base station management functions in the
standard. It can manage the hybrid access of ZXG10 BTS
series products.
Connects with OMC by foreground/background interface to
realize the operation and maintenance management of BSS.
Supports various types of services.
i.
Circuit Voice Services
Full rate voice service
Advanced full rate voice service
Half rate voice service
AMR voice service

AMR is one of the voice coding algorithms with variable
rate. It adjusts the voice coding rate automatically
according to the C/I value to ensure the best voice
quality under different C/I.
According to the protocol, there are 8 AMR-FR voice
coding rates. ZXG10 iBSC (V6.10) supports all 8 modes.
And there are 5 AMR-HR voice coding rates (7.4 kbps,
6.7 kbps, 5.9 kbps, 5.15 kbps, 4.75 kbps), all supported
by ZXG10 iBSC (V6.10).
ii. Circuit Data Services

f
14.4 kbps full rate data service
iii. Short Message Service, Chinese SMS supported
Point to point SMS in case that MS is the called party
Point to point SMS in case that MS is the calling party
Cell broadcast service from SMS center or OMC
iv. GPRS Service

At present, main services available are point to point
interactive telecommunication services, such as access
database, session service, Tele-action service and so on.
v. EDGE Service
Supports channel management, including ground channel

management, service channel management and control
channel management.
f
Ground channel management

It includes the ground channel management between
MSC and BSC, the ground channel management between
BSC and BTS and the channel management between BSC
and SGSN.
Service channel management includes channel allocation,

link monitoring, channel release, and function control
determination.
Available channels: FCCH, SCH, BCCH, PCH, AGCH, RACH,
SDCCH, SACCH, FACCH, PACCH, PAGCH, PBCCH, PCCCH,
PPCH, PRACH, and PTCCH.
Supports frequency hopping
Supports DTX and VAD
Supports various handover types

f
f
f
Supports the handover intra 900 MHZ frequency band,

1800 MHZ frequency band and between 900 MHZ and
1800 MHZ frequency band.
Handles handover measurement and switch over.
Supports the handover originated by network since
service or interference management.
Supports the handover between
different voice coding rate.
the
Supports the handover when using DTX.
Supports the handover caused by traffic.
Supports
synchronous
handover,
non-synchronous
handover and pseudo-synchronous handover.
channels
with
Supports the concentric ring handover based on carrierto-interference ratio.
Supports 6-level static power control and 15-level dynamic

power control of MS and BTS. Supports fast power control
based on reception quality.
Supports overload and flow control
iBSC is able to locate and analyze the overload, and send the
cause to the background. If the traffic is too heavy, control
the flow at A interface, Abis interface, and/or Gb interface to

reduce the flow and guarantee maximum network utilization.
Supports call-reestablishment when radio link is faulty

iBSC supports call queuing and forced call release during
assignment and handover.
High end user preferential access
High end user preferential access, also called high priority
user preferential access or EMLPP. It is used to divide the
users into different priorities, and allocate the channel
resource to the users according to the priority. The higher
the priority of the user is, the easier to access the network.
Supports Co-BCCH.
Co-BCCH is usually used in dual-frequency common cell.
Dual-frequency common cell is a cell that supports the
carriers of two frequency bands, and the carriers of different
carrier bands share one BCCH.
Co-BCCH networking has the following advantages:
f
f
Save one BCCH time slot

Configure the 1800 MHz carrier directly in 900 MHz cell.
There is no need to change the original cell adjacent
relation, re-arrange network, and no need to consider the
reselection and handover between the dual-frequency cell
with common site.
Supports dynamic HR channel conversion

ZXG10 iBSC supports dynamic HR channel conversion.
System is able to adjust HR/FR channel dynamically
according to the traffic, and realize the conversion between
HR/FR channels automatically.
Supports flow control

Flow control is a method to protect the system. It controls
the overload by limiting some services to ensure that the
system runs normally.
Supports dynamic radio channel allocation

ZXG10 iBSC supports the dynamic allocation of CS and PS
channels.
In dynamic radio channel allocation, the logic type of radio
channel is generated according to the current call type rather
than configured at background NM. The advantage of
dynamic radio channel is that it uses the radio resource the
best according to the service type.
ZXG10 iBSC allocates the channel according to various
factors, such as channel rate selection, carrier priority,
interference band, the channel allocation in intra-cell
handover, allocation of reservation channel, and the selection
of sub-cell channel.
Supports voice version selection

ZXG10 iBSC provides the function of setting prior voice
version; one prior voice version can be set for full rate and
half rate channel. Full rate voice version is one of version I
(FR), version II (EFR) and version III (AMR); half rate voice
rate voice version is one of version I (HR) and version III
(AMR).
Supports 3 digits network number

ZXG10 iBSC supports 3 digits network number. The current
network number can be set as 2 or 3 digits. It interprets the
MNC in the received signaling message at A interface and Gb
interface, confirms the MNC format in the transmitted
signaling, and confirms the MNC format in the broadcast
message at Um interface according to the network number.
Supports the handover between 2G/3G system

f
Support handover from 3G to 2G in CS service
Support handover from 2G to 3G in CS service
Supports full dynamic Abis

Full dynamic Abis is that the corresponding relation of radio
channel and Abis transmission channel is not generated in
OMC, but is configured dynamically in service process.
Dynamic Abis is to provide more bandwidth in case the Abis
transmission bandwidth is fixed.
Supports coding control

Compared with GPRS, the measurement report of EDGE is
improved a lot. The EDGE measurement is based on each
pulse, which means the measurement is performed by the
granularity of Burst.
The fast measurement of EDGE makes the network is able to
respond the change of the radio environment rapidly so that
it can select the most proper coding mode and carry out
power control.
In downlink direction, iBSC supports selecting the coding
mode by time slot and by TBF.
In uplink direction, iBSC selects the uplink TBF coding mode
according to the measurement parameters of the uplink
channel reported by BTS.
Supports retransmission
In packet service, the negative feedback is employed to
control the retransmission, which means that the transmitter
finds out the packets that are not received correctly by the
receiver according to the bitmap fed back from the receiver,
then determines if to retransmit the corresponding packet.
In GPRS, the packet data is retransmitted in original
transmission coding mode, for example, the block
transmitted in CS4 coding is retransmitted in CS4 mode.
In EDGE, there are two new retransmission methods:

segmentation and reassembly, and incremental redundancy.
Optimization of packet channel allocation algorithm

ZXG10 iBSC supports the multiple time slot ability of the MS.
It allocates GPRS TBF or EDGE TBF to the MS according to
the different GPRS/EDGE availability of MS.
When ZXG10 iBSC allocates the PDTCH channel to the MS, it
selects the carrier with lower load first; after selecting the
carrier, it selects the most proper PDTCH channel
combination in the carrier according to the MS requirement.
Supports satellite Abis and satellite Gb

There is a bi-directional time delay about 540 ms, which
impacts the GRPS and EDGE services a lot. ZXB10 iBSC
eliminates this impact as much as possible and ensures that
the GPRS and EDGE services run normally.
Supports various interfaces

ZXG10 iBSC supports STM-1 interface, Fast Ethernet (FE)
interface, and E1 interface.
Supports UMTS QoS

After the GSM network evolves into GERAN, operators can
provide more powerful services for users due to the highspeed packet data transmission brought by EDGE. These
services include conversational service, stream media service,
and interactive service. ZXG10 iBSC supports various service
quality requirements of different services, i.e. QoS.
Supports extended uplink dynamic TBF

Before the extended uplink dynamic allocation is applied in
GPRS system, the number of uplink channels available for
uplink TBF is always less than the number of occupied
downlink channels. ZXG10 iBSC supports the extended uplink
dynamic TBF and realizes that the number of uplink channels
is larger than the number of downlink channels, which better
satisfies the service requirement.
Supports multi-signaling-point connection

According to the ITU-T specification, the maximum number
of signaling links between two signaling points is 16, and the
maximum number of circuits is 4096. With the development
of mobile network, the number of users increases greatly.
The maximum number of signaling links and the maximum
number of circuits can not satisfy the on-site service
requirement.
ZXG10 iBSC adopts the unified 3G platform to support multisignaling-point connection. In other words, one iBSC can
connect multiple MSCs.
Supports intelligent power-off
When the system performance data reaches the threshold

value for power-on/off, ZXG10 iBSC sends message to notify
BTS to perform the power-on/off operation.
Supports TFO
Tandem Free operation (TFO) refers to the following process:
After a call is established, the two Transcoders (TC) perform
in-band negotiation for the Codec used, to avoid unnecessary
voice coding conversion at the sending end and the receiving
end during the call process.
TFO improves the voice quality and reduces the transmission
delay.
Supports transparent channel

The
transparent
channel
realizes
transparent
data
transmission between a timeslot of E1 at one ends interface
and that at the other ends interface.
f
If E1 cables at the two ends of the transparent channel

are in the same shelf, this function can be realized by the
circuit switching of UIMU of the shelf.
If E1 cables at the two ends of the transparent channel
are in different shelves, this function is realized by
transparent data forwarding through DSP (the DSP is
used to process user plane data).
ZXG10 iBSC supports the following transparent channels:

f
The transparent channel between Abis interface and Ainterface

The transparent channel between Abis interface and Abis
interface
The transparent channel between A-interface and Ainterface
The transparent channel between Abis interface and Ater
interface (if TC is remote)
Supports EGPRS and GPRS channel scheduling

Take GPRS MS for example. The channel scheduling process
is as follows:
Allocate the GPRS channel for GPRS MS first. If the EGPRS
channel is idle and the GPRS channel load is heavy, the GPRS
MS can be allocated with EGPRS channel. If the EGPRS
channel load becomes heavy or the GPRS channel is idle, the
GPRS MS can migrate to the GPRS channel.
Supports Dual Transfer Mode (DTM)

ZXG10 iBSC supports the Dual Transfer Mode (DTM). ZXG10
iBSC can perform CS/PS service simultaneously under A/Gb
mode.
Supports user tracing function
ZXG10 iBSC realizes single-user signaling-tracing function

according to users identification IMSI, TMSI, or TLLI.
Supports PS paging coordination

ZXG10 iBSC supports PS paging coordination, that is, under
the packet transmission state, iBSC can make MS intercept
the circuit paging message.
Standards Complied
ZXG10 iBSC (V6.10) development standards are given below:
10
3GPP 23.060 General Packet Radio Service (GPRS)

Service description Stage 2 (Release 5) version V5.10.0
Mobile Station (MS) Base Station System (BSS) interface
Radio
Link
Control/Medium
Access
Control
(RLC/MAC)protocol Iu mode(Release 5) version V5.8.0
3GPP 43.051 Radio Access Network Overall description
Stage 2 (Release 5) version V5.10.0
3GPP 23.221 Technical Specification Group Services and
System Aspects Architectural requirements(Release 5)
version V5.11.0
3GPP 23.236 Intra-domain connection of Radio Access
Network (RAN) nodes to multiple Core Network (CN) nodes
(Release 5) version V5.3.0
3GPP 24.008 Mobile radio interface Layer 3 specification
Core network protocols Stage 3(Release 5) V5.13.0
3GPP 25.323 Packet Data Convergence Protocol (PDCP)
specification (Release 5) Version V5.4.0
3GPP 48.016 General Packet Radio Service (GPRS) Base
Station System (BSS) Serving GPRS Support Node (SGSN)
interface Network service Version V5.4.0
3GPP 48.018 General Packet Radio Service (GPRS) Base
Station System (BSS) Serving GPRS Support Node (SGSN)
BSS GPRS protocol (BSSGP) version V5.13.0
3GPP 44.018 - Mobile radio interface layer 3 specification
Radio Resource Control (RRC) protocol (Release 5) version
V5.20.0
Mobile Station (MS) Base Station System (BSS) interface
Radio Link Control/Medium Access Control (RLC/MAC)
protocol(Release 5) version V5.10.0
3GPP 44.118 Mobile radio interface layer 3 specification
Radio Resource Control (RRC) protocol Iu Mode (Release 6)
version V6.4.1
3GPP 44.008 Technical Specification Group GSM/EDGE

Radio Access Network Radio subsystem link control
(Release 5) version V5.19.0
3GPP 43.130 Iur-g interface Stage 2 version V5.0.0
3GPP 23.271 Functional stage 2 description of Location
Services (LCS) version V5.13.0
3GPP 45.002 Multiplexing and multiple access on the radio
path version V5.13.0
3GPP 43.059 Functional stage 2 description of Location
Services (LCS) in GERAN version V5.5.0
3GPP 49.031 Location Services (LCS) Base Station
System Application Part LCS Extension (BSSAP-LE) version
V5.4.0
3GPP 48.071 - Location Services (LCS); Serving Mobile
Location Centre - Base Station System (SMLC-BSS) interface;
Layer 3 specification version V5.1.0
3GPP 44.031 - Location Services (LCS); Mobile Station (MS)
- Serving Mobile Location Centre (SMLC) Radio Resource LCS
Protocol (RRLP) version V5.13.0
3GPP 44.071 - Location Services (LCS); Mobile Radio
Interface Layer 3 LCS Specification version V5.0.1
3GPP 48.008 Mobile Switching Centre Base Station
System(MSC-BSS) interface Layer 3 specification(Release 5)
version V5.12.0
11
12
Chapter
System Indices
This chapter contains following topics:
Physical Indices
Clock Indices
Power Supply Indices
Environmental Conditions
Reliability Indices
Interface Indices
Capacity Indices
Physical Indices
Physical structure of ZXG10 iBSC (V6.10) is the same as ZXWR
RNC. Structure of ZXG10 iBSC cabinet is shown in Figure 3.
Size
Excluding left & right side door panel: H X W X D = 2000 mm X

600 mm X 800 mm
Including left & right side door panel: H X W X D = 2000 mm X
650 mm X 800 mm
Note:
Outline dimension for whole cabinet: 2000 mm X 600 mm X 800
mm (H X W X D), width for single side panel is 25 mm.
13
FIGURE 3 PHYSICAL STRUCTURE OF ZXG10 IBSC (V6.10)
Overall Weight
Table 5 describes the weight of ZXG1 iBSC (V6.10) equipment

and load bearing capacity of equipment room floor.
TABLE 5 WEIGHT OF IBSC CABINET
Weight
Weight of a single
cabinet
350 kg
Clock Indices
ZXG10 iBSC (V6.10) clock indices are given in Table 6.
TABLE 6 CLOCK INDICES OF ZXG10 IBSC (V6.10)
Index
Value
Clock level
Level 3 class-A clock
Minimum clock accuracy
4.6 10-6
Pull-in range
4.6 10-6
Maximum
deviation
14
frequency
210-8/day
Chapter 2 - System Indices
Index
Value
Maximum initial frequency

deviation
1 10-8
Clock working mode
Fast pull-in, trace, hold, and free run
Clock
mode
External
clock
synchronization,
extracting from the line clock
synchronization
Clock
synchronization
interfaces
2MBITS
2 MHz
Line
kbps
Power Supply Indices

Power Supply
Range
Table 7 describes the power supply ranges for ZXG10 iBSC

(V6.10).
TABLE 7 POWER SUPPLY RANGE
Power Supply Range
Power
Consumptions
Index
Rated input voltage
-48 V DC
Voltage fluctuation range
-57 V DC ~ - 40 V DC
Table 8 describes the power consumptions of ZXG10 iBSC

(V6.10).
TABLE 8 POWER CONSUMPTION OF ZXG10 IBSC (V6.10)
Power Consumption
Power consumption of fullyconfigured single cabinet
2360 W
Power consumption of fullyconfigured dual-cabinet
5360 W
Environmental Conditions
Grounding
Requirements
The ZXG10 iBSC (V6.10) cabinet can be upper-grounded or

lower-grounded.
Table 9 describes ZXG10 iBSC grounding indices:
TABLE 9 GROUNDING REQUIREMENTS OF ZXG10 IBSC (V6.10)
Index
Range
Cabinet grounding resistance
0.1 ~ 0.3
15
Temperature
and Humidity
Requirements
Index
Range
Equipment room grounding resistance
<1
Table 10 describes the temperature and humidity requirements.

TABLE 10 TEMPERATURE AND HUMIDITY REQUIREMENTS FOR IBSC(V6.10)
Requirement
Range
Operating
temperature
Long-term operating temperature: 0C ~ 40C
Relative
humidity
Relative humidity for long-term operation: 20% ~

90%
Short-term operating temperature: -5C ~ 45C
Relative humidity for short-term operation: 5% ~

95%
Air Pollution
Requirements
Air inside the equipment room must be free of magnetoconductive, conductive, and corrosive gases that may corrode
metallic parts and degrade insulation. Table 11 describes the air
pollution requirements of ZXG10 iBSC (V6.10).
TABLE 11 AIR POLLUTION AND ATMOSPHERIC PRESSURE REQUIREMENTS
Requirement
Density of dust particles
diameter larger than 5 m
Range
with
3104 grains/m3
Reliability Indices
Reliability indices of ZXG10 iBSC (V6.10) are shown in Table 12.
TABLE 12 RELIABILITY INDICES OF ZG10 IBSC (V6.10)
16
Index
Value
Mean Time Between Failure (MTBF)
100,000 hours
Mean Time To Repair (MTTR)
30 minutes
System restart time
<10 minutes
Interface Indices
A-Interface
Index
The A-interface connects MSC. A-interface uses the following

media:
E1 link
STM-1 link
Table 13 describes the A-interface index for internal TC. The Ainterface connects MSC.
TABLE 13 A-INTERFACE INDEX (FOR INTERNAL TC)
Maximum Capacity
Index
Ainterface
Ater Interface
Index
Single Cabinet
Dual Cabinet
E1
224
672
STM-1
12
The Ater interface connects iTC. Ater interface uses the following
media:
E1 link
STM-1 link
Table 14 describes the Ater interface index for external TC. The
Ater interface connects iTC.
TABLE 14 ATER INTERFACE INDEX (FOR EXTERNAL TC)
Maximum Capacity
Index
Ater
interface
Abis Interface
Index
Single Cabinet
Dual Cabinet
E1
64
192
STM-1
Abis interface uses following media:
E1 link
Fast Ethernet (FE) link
The Abis interface connects BTS. Table 15

interface index.
describes the Abis
TABLE 15 ABIS INTERFACE INDEX
Maximum Capacity
Index
Abis
E1
Single Cabinet
Dual Cabinet
208
624
17
Maximum Capacity
Index
interface
Gb Interface
Index
Single Cabinet
Dual Cabinet
FE + E1
4 FE + 104 E1
12 FE + 312 E1
FE
12
Gb interface uses the following media:
E1 link
FE link
The Gb interface connects SGSN. Table 16 describes the Gbinterface index.

TABLE 16 GB INTERFACE INDEX
Maximum Capacity
Index
Gb
interface
flow
(Mbps)
ForegroundBackground
Interface
Index
Single Cabinet
Dual Cabinet
A-interface
adopts E1
32 Mbps
96 Mbps
A-interface
adopts
STM-1
32 Mbps
160 Mbps
Foreground-background interface uses the following media:
FE link
Capacity Indices
Table 17 describes the capacity index of ZXG10 iBSC (V6.10)
configuration.
TABLE 17 CAPACITY INDEX OF ZXG10 IBSC (V6.10)
Maximum Capacity
Index
A-Interface
Abis Interface
Ater Interface
Gb Interface
18
E1
672
STM-1
12
E1
624
FE + E1
12 FE + 312 E1
FE
12
E1
192
STM-1
A-interface adopts
96 Mbps
Maximum Capacity
Index
E1
Number of No.7 link
A-interface adopts
STM-1
160 Mbps
64 kbps link
16
2 Mbps No.7 link
16
Number of Carriers
3072
Number of Sites
1536
BHCA
4200 K
Traffic
15000 Erlang
19
20
Chapter
System Architecture
This chapter explains the following topics:
System Composition
Hardware System
Shelves
Boards
Software System
System Composition
ZXG10 iBSC (V6.10) works smoothly in the GSM system and is
compatible to all parts of GSM network. It consists of the
hardware system and software system.
The hardware system contains the cabinet, shelves, and boards.
The software system includes the foreground software and the
background software.
Hardware System
Overview
Figure 4 shows the structure of ZXG10 iBSC (V6.10) hardware

system.
21
FIGURE 4 ZXG10 IBSC (V6.10) HARDWARE SYSTEM DIAGR AM
ZXG10 iBSC
Processing
unit
BTS
Z
T
E
TC unit
TC
O&M unit
Peripheral device
MSC
monitoring unit
Power,
Fan
SGSN
Logically, ZXG10 iBSC (V6.10) consists of six units:
Access unit
This unit provides the following interface access processing
for iBSC:
f
A-interface/Ater interface
Abis interface
Gb interface
This unit includes:

f
A-Interface Unit (AIU) (when TC is external, AIU belongs

to iTC system, and the Ater interface unit NSMU is added
between iBSC and iTC)
Abis Interface Unit (BIU)
Gb Interface Unit (GIU)
Switching unit
This unit provides
congestion.
large-capacity
platform
without
Processing unit
This unit performs upper-level protocol processing for system
control plane and user plane.
O&M unit
This unit performs management for iBSC system, and
provides global configuration data storage and foregroundbackground interfaces.
Peripheral device monitoring unit

This unit performs detecting and alarm for iBSC cabinet
power and environment, and detecting and controlling for the
cabinet fan.
22
Chapter 3 - System Architecture
TC unit
This unit performs transcoding and rate adaptation. When TC
is external, this part is realized by iTC.
Shelves
ZXG10 iBSC (V6.10) system includes three shelves: control shelf,
resource shelf, and packet switching shelf. The functional
description of each shelf is given in Table 18.
TABLE 18 SHELVES DESCRIPTION
Shelf Type
Functions
Control Shelf
Implements the system global operation and

maintenance, global clock function, control plane
processing, and control plane Ethernet switching
functions.
Resource Shelf
Implements the system access and form various

common service processing sub-systems.
Packet
Switching
Shelf
Provides non-blocking IP switching platform with

large-capacity.
Refer to ZXG10 iBSC (V6.10) Base Station Controller Hardware

Manual for details about shelves.
Boards
The boards configured in the shelves are classified into front
board and back board according to the assembly relation. The
front board and back board are inserted in the slot on the
backplane. The indicators for board running status are installed
on the front board panel. The back board assists the front board
to lead out the external signal interface (the optical fiber is led
out from front board panel) and debugging port to realize the
connection between different shelves on the same rack, between
different racks, and between the system and the external NE.
The description of the boards in ZXG10 iBSC (V6.10) is given in
Table 19.
23
TABLE 19 ZXG10 IBSC (V6.10) BOARDS LIST
Board
Name
Functions
BIPI
Provide FE interface for

iBSC system, there are 4
FE interfaces on each BIPI.
Corresponding
Rear Board
IPBB,
IPAB,
RMNIC
IPGB
CHUB
CHUB and UIMC/UIMU

together control the
exchange and convergence
of the system internal
control plane data.
CHUB
CLKG
Implement the clock

function of iBSC system.
CLKG
CMP
Implement the service call

control management in
PS/CS domain, the
resource management in
sub-layer, such as BSSAP,
BSSGP, and system itself.
CMP
DTB
Each DTB provides 32 E1

interfaces.
DTB
RDTB
GLI
Provide interface and

processing function for the
interconnection of each
resource shelf.
GLI
GUP
Realize the Abis interface

processing, transcoding
and rate adaptation.
RCHB1
RCHB2
RCKG1
RCKG2
BIPB
DRTB
TIPB
OMP
Implement the system

global processing, provide
an external FE interface
and iOMCR connection;
monitor and manage the
boards in the system
directly or indirectly.
OMP
RMPB
PSN
Implement the exchange of

user plane data with large
capacity.
PSN
SDTB
Provide a standard 155M

STM-1 interface.
SDTB
RGIM1
SPB
Implement the signal

processing and external
interface function.
SVR
24
Board
Function
Name
Store some files needed by

OMP, and organize these
files according to the
requirement of OMC.
SPB,
GIPB,
RSPB
LAPD
SVR
RSVB
Board
Name
Functions
Board
Function
Name
UIMC
Provide switching plane for

control shelf and packet
switching unit shelf.
UIMC
UIMU
Provide internal platform

for resource shelf.
UIMU
RUIM1
UPPB
Implement the PS service

processing in A/Gb mode
and user plane service
processing in Iu mode.
UPPB
Corresponding
Rear Board
RUIM2,
RUIM3
Note:
Each board has two names: board hardware name and board
function name. The board hardware name is the board name,
and board function name reflects the function that the board
implements after loading the software. The same hardware
board can realize a different function by loading different
software.
Refer to ZXG10 iBSC (V6.10) Base Station Controller Hardware

Manual for details on boards.
Software System
The software system of ZXG10 iBSC (V6.10) includes foreground
software and background software. The foreground software
runs on ZXG10 iBSC equipment, and the background software
runs on the NM server and client.
The software structure of ZXG10 iBSC is shown in Figure 5.
FIGURE 5 - ZXG10 IBSC SOFTWARE STRUCTURE
iBSC
iBSC
Equipment
Foreground
Software
Background
NM
TCP/IP
Background
Software
Foreground Software
The foreground software system structure of ZXG10 iBSC (V6.10)
is shown in Figure 6.
25
FIGURE 6 FOREGROUND SOFTWARE SYSTEM STRUCTURE
SCS
SCS
DBS
DBS
OMS
OMS
Signalin RAN
g Sub-
RANC
system RANC
OSS
OSS
RAN
RANS
S
RANSS
RAN
RANU
RANU
BR
S
BRS
VxWorks
BSP& DRIVER
HARDWARE
Description of the main parts of software system is as follows:

BSP
Subsystem
BSP subsystem implements the hardware drivers of the whole

system. It shields the upper level software module from the
operation details of hardware device, extracts the hardware
function and only provides the logic function level of the
hardware device to the other software module.
OSS
Operation Support Subsystem (OSS) works above the BSP

subsystem and below all other subsystems, it shields the user
process from all device driver interfaces. The main tasks of OSS
include process communication, file management, device driver
and process scheduling.
DBS
Database Subsystem (DBS) works above the OSS. It manages

the physical resources of NE, manages the configuration
information of services, signaling and protocol, and provides the
database access interface to other subsystems.
BRS
Bearer Subsystem (BRS) provides the bearer services of IP and

TDM for the service support subsystem, signaling subsystem and
OMS, and implements LAPD function and Frame Relay (FR)
function.
OMS
Operation & Maintenance Subsystem (OMS) is a foreground

realization of OMCR and LMT. It performs following functions:
26
Performance management
SCS
Signal tracing
Performance statistic of radio service
Service alarm, and dynamic observation of service data
System Control Subsystem (SCS) works above the OSS and DBS.
It performs the monitoring, startup, and version download of the
whole system.
Signaling
Subsystem
Signaling subsystem works above OSS, DBS, and bearer

subsystem. It realizes the narrow band No. 7 signaling,
broadband No. 7 signaling, calling signaling, IP signaling and
gateway control signaling, and it provides services to RANC and
RANSS.
RANC
RAN Control Plane Subsystem (RANC) performs the following

functions:
RANU
Implements function of calling signaling connection control,

including; radio resource management, dynamic channel
resource adjustment, load control, acceptance control,
handover, and signaling connection management.
RAN User Plane Subsystem (RANU) performs the following

functions:
RANSS
Implements processing of layer-3 control plane protocols at

Um, Abis, A, and Gb interface.
For the PS in A/Gb mode and Iu mode, it provides data

forwarding and scheduling at radio interface, Gb interface,
and Iu interface according to the QoS demand.
For CS in A/Gb mode, it provides the TC function on GUP
board.
RAN Service Support Subsystem (RANSS) provides support to

control plane and user plane subsystem and performs the
following functions:
Guarantees the proper process of service.
Provides monitoring of various services.
Implements iBSC global processing, including signaling

tracing, load control, acceptance control, and performance
measurement.
27
Background Software
Background software runs on the NM server and client, it is
called ZXG10 NetNumen-G and it communicates with iBSC by
TCP/IP protocol. The main functions of ZXG10 NetNumen-G are
as follows:
28
Configuration management
Fault management
Performance management
System management
Chapter
Interfaces and Protocols

This chapter describes the following topics:
A-interface
Ater Interface
Abis interface
Gb interface
Foreground-Background Interface
Protocols in CS Domain
Protocols in PS Domain
External Interfaces
When TC is internal, the external interfaces of ZXG10 iBSC
(V6.10) are shown in Figure 7.
FIGURE 7 EXTERNAL INTERFACES OF ZXG10 IBSC (TC IS INTERNAL)
MSC
MSC
A
SGSN
G b
iBSC
Abis
BTS
Abis
BTS
iOMCR
When TC is external, the external interfaces of ZXG10 iBSC

(V6.10) are shown in Figure 8.
29
FIGURE 8 EXTERNAL INTERFACES OF ZXG10 IBSC (TC IS EXTERNAL)
The functional description of ZXG10 iBSC external interfaces is

given in Table 20.
TABLE 20 FUNCTIONAL DESCRIPTION OF ZXG10 IBSC EXTERNAL
INTERFACES
External
System
External System
Function
Relative Interfaces
Establish the radio

environment under the
control of iBSC.
Abis interface, providing the

control and maintenance
information of BTS, and
providing the transmission of
voice information and GPRS
data at Abis interface.
Control iBSC and MS to

establish voice radio
channel, implement the
function of voice
exchange.
A-interface, providing relative

message about connection
establishment and deleting at
A interface, forwarding the
higher-level message
between MS and MSC
transparently, and also
transmitting voice
information.
SGSN
Control iBSC and MS to

establish the GPRS radio
channel, and implement
the function of data
information exchange.
Gb interface, providing
relative message about
connection establishment and
deleting at Gb interface,
forwarding the higher-level
message between MS and
MSC transparently, and also
transmitting GPRS data
information.
iTC (TC is
external)
Perform the transcoding

function
Ater interface, providing

signaling interaction between
iBSC and iTC.
iOMCR
The system operators

maintain and control the
iBSC through iOMCR.
Foreground-background
interface, providing the
control and maintenance of
iBSC through iOMCR.
BTS
MSC (TC
is
internal)
30
Chapter 4 - Interfaces and Protocols
A-Interface
The interface between BSC and MSC is called A-interface. More
accurately, A-interface is the interface between TC and MSC.
Transcoder implements the voice transformation between voice
coding and 64 kbps A law PCM coding. At the same time, it
performs the data rate adaptation in the circuit data service. TC
can be either at BSC side or MSC side.
The iBSC A-interface supports two kinds of interfaces.
E1 Interface
In this case, iBSC is connected with MSC by 75 coaxial cable

or 120 twisted pair.
At A-interface, data link layer employs MTP2 protocol, network
layer employs MTP3 and SCCP protocol, and application layer
employs BSSMAP protocol.
STM-1
Interface
In this case, iBSC is connected with MSC by optical fiber.
Ater Interface (TC is External)

The interface between iBSC and iTC is called Ater interface. TC is
separated from iBSC, and exists as an independent system iTC,
which facilitates dynamic TC resource sharing. For more details,
refer to ZXG10 iTC (V6.10) Transcoder Pool Technical Manual.
The iBSC Ater interface supports two kinds of interfaces.
E1 Interface
In this case, iBSC is connected with iTC by 75 coaxial cable or

120 twisted pair.
At Ater interface, data link layer employs MTP2 protocol,
network layer employs MTP3
and SCCP protocol, and
application layer employs Ater interface application layer
protocol.
STM-1
Interface
In this case, iBSC is connected with iTC by optical fiber.
Abis Interface
The interface between BSC and BTS is called Abis interface. BSC
is connected with BTS via Abis interface. Abis interface is the
internal user-defined interface of ZXG10 iBSC. When using E1
for transmission, Abis interface supports various networking
modes such as star, chain, tree, and ring.
31
The Abis interface of iBSC supports two kinds of interfaces.

E1 Interface
If the Abis interface is an E1 interface, iBSC is connected with

BTS by 75 coaxial cable or 120 twisted pair.
At Abis interface, data link layer employs LAPD protocol, and the
upper layer employs application protocol such as RR.
FE Interface
In this case, iBSC is connected with BTS by network cable.

Date link layer employs RUDP protocol.
Gb Interface
The interface between BSC and SGSN is called Gb interface. BSC
is connected to SGSN via Gb interface.
Gb interface supports two kinds of interfaces.
E1 Interface
FE Interface
iBSC is connected with SGSN by E1 line, the data access rate

could be N 64 kbps (1 N 32). The time slot and
bandwidth used on E1 line is appointed by the operator.
At Gb interface, iBSC realizes FR protocol, NS protocol and
BSSGP protocol.
In this case, iBSC and SGSN is connected by network cable.
iBSC implements IP-related protocol, NS protocol and BSSGP
protocol.
Foreground-Background Interface
The foreground-background interface is the interface connecting
ZXG10 iBSC background NM and iBSC foreground equipment.
The background NM software can manage and configure the
iBSC foreground boards through this interface. The foreground
communicates with the background through TCP/IP protocol.
Protocols
Protocols in CS domain
CS domain protocol stack is used to process the protocol related
to voice data of each layer.
32
User Plane Protocol Stack in CS Domain

Figure 9 shows the user plane stack protocol in CS domain.
FIGURE 9 USER PLANE PROTOCOL STACK IN CS DOMAIN
MS
GERAN
2G-MSC
RLP
RLP
AMR/FR/
EFR/HR
G.711/TFO
Transcoding /TRAU Relay

Relay
Um
PHY
L1
PHY
L1
AMR/FR/EFR/HR coding can be used for transmitting voice

service and RLP protocol can be used for transmitting data
service.
Control Plane Protocol Stack in CS Domain

Figure 10 shows the control plane protocol stack in CS domain
(here, the case of TC being internal is taken for example).
FIGURE 10 CONTROL PLANE PROTOCOL STACK IN CS DOM AIN
BTS
MS
iBSC
MSC
CM
CM
MM
MM
RR
RR
LapDm
Physical
Layer
Um Interface
BTSM
LapDm LapD
Um
RUDP
RR
BSSAP
BTSM
SCCP
BSSAP
SCCP
MTP3
MTP3
MTP2
MTP2
RUDP
Abis
LapD
A
Protocol layers of control plane in CS domain at UM interface are

shown in Figure 11.
33
FIGURE 11 CIRCUIT SERVICE PROTOCOL STRUCTURE AT UM INTERFACE
Um
Um
Interface
CM
MM
RR
RR
LAPDm
LAPDm
Layer1
Layer1
BTS
MS
Transmission Layer (Physical Layer)

The first layer of UM interface. It provides the transmission
channel of the radio link, transmits the data by radio wave,
and provides channels with different functions for the upper
layers, including service channel and logic channel.
Data Link Layer

The second layer of Um interface. It provides reliable data
link between MS and BTS, employs LAPDm protocol that is
the dedicated protocol for GSM and the transformed version
of the ISDN D channel protocol LAPD.
Application Layer
The third layer of Um interface. It processes control and
management protocol, arranges the control process
information of the user and the system to the appointed logic
channels according to certain protocol group. It includes
three sub-layers: CM, MM and RR.
f
CM Layer
It
implements
the
communication
management:
establishes connection between users, holds and releases
the calls, which can be divided into CC, SSM and SMS.
MM Layer
It realizes mobility and security management and the
processing done by MS when it initiates location update.
RR Layer
It manages radio resources and establishes and releases
the connection between MS and MSC during the call.
Abis Interface
In iBSC this interface can transmit data in two ways: E1 and IP

The protocol layers of the control plane protocol stack at Abis
interface in CS domain are shown in Figure 12.
34
FIGURE 12 HIERARCHIC AL STRUCTURE OF CONTROL PLANE PROTOCOL AT

ABIS INTERFACE
Abis Abis
Interface
RR
BTSM
BTSM
LAPD RUDP
RUDP LAPD
Layer1
Layer1
iBSC
BTS
Layer1 Physical Layer

It could employ 2 Mbps E1 cable or Cat-5 network cable.
Layer2 Data Link Layer

f
When Abis interface employs E1 for transmission, the

data link layer employs LAPD protocol, which is a one to
many communication protocol and a subset of Q.921
standard, LAPD is frame structure, including flag field,
control field, information field, check field, and flag
sequence. The flag field includes SAPI and TEI, which
indicate the accessed service and entity.
When Abis interface employs IP for transmission, data
link layer employs RUDP protocol.
Layer3 Application Layer

It transmits the application part of BTS, including radio link
management function and operation & maintenance function.
The layers of control plane protocol in CS domain at A-interface

A-Interface
(TC is Internal) are shown in Figure 13.
35
FIGURE 13 HIERARCHIC AL STRUCTURE OF CONTROL PLANE PROTOCOL IN

CS DOM AIN AT A-INTERFACE
CM
R
MM
R
A-Interface
BSSA
P
SCCP
BSSAP
SCCP
MTP3
MTP3
MTP2
MTP2
Layer1
Layer1
MSC
BSC

f
It employs the first level of MTP in SS7 to realize, and

uses 2 Mbps PCM digital link as transmission link.
Layer2 Data Link Layer and Network Layer

f
It defines the physical layer structure of MSC and BSC,

including physical and electrical parameters and channel
structure.
MTP2 is a varied version of HDLC protocol. The frame

structure includes flag field, control field, information field,
check field and flag sequence.
MTP3 and SCCP implements functions such as signaling
route selection.

f
f
It includes BSS application rules and BSSAP.

It maintains and manages the resource and connection of
BTS subsystem, controls the service connection and
release.
Ater Interface
The layers of control plane protocol in CS domain at Ater
(TC is External) interface are shown in Figure 14.
36
FIGURE 14 HIERARCHIC AL STRUCTURE OF CONTROL PLANE PROTOCOL IN

C S D OM AI N AT AT E R I N T E R F AC E
Ater Interface
Ater Interface
Application
Layer
Ater Interface
Application
Layer
SCCP
SCCP
MTP3
MTP3
MTP2
MTP2
Layer1
Layer1
iTC
iBSC

f
It employs the first level of MTP in the Common Channel

Signaling No. 7 (CSS7), and uses 2 Mbps PCM digital link
as transmission link.
Layer2 Data Link Layer and Network Layer

f
It defines the physical layer structure of iTC and iBSC,

including physical and electrical parameters and channel
structure.
MTP2 is a varied version of HDLC protocol. The frame

structure includes flag field, control field, information field,
check field and flag sequence.
MTP3 and SCCP implements functions such as signaling
route selection.

It mainly includes Ater interface application layer protocol. It
performs Ater interface circuit management and TC resource
request and release.
Protocols in PS Domain
PS domain protocol stack is used to process the protocol of each
layer related with packet data.
User Plane Protocol Stack in PS Domain

Figure 15 shows the user plane protocol stack in PS domain.
37
FIGURE 15 USER PLANE PROTOCOL STACK IN PS DOM AIN
Um Interface
Figure 16 shows the protocol layer at Um interface.

FIGURE 16 - HIERARCHIC AL STRUCTURE OF PS PROTOCOL AT UM INTERFACE
MS
SNDCP
BSS
LLC
relay
RLC
RLC
MAC
MAC
PHY
PHY
Um
Um
Interface
GSM RF
The physical layer of Um interface is the RF interface part.
The RF part employs the same transmission mode as GSM
circuit service, specifying carrier characteristics, channel
structure, modulation mode and RF index and so on.
RLC/MAC Layer
RLC is the radio link control protocol of the air interface
between BTS and MS. The main functions are error detection
of data block, retransmission selection and confirmation of
error data block at Um interface and so on.
MAC controls the access signaling flow on radio channel. It
makes decision when a great deal of MSs access the common
media, and also it maps the LLC to the GSM physical channel.
Compared with the MAC function in A/Gb mode, the MAC of
GERAN has the following important differences:
38
Supports one MAC entity with many TBF
Supports MAC layer encryption
LLC Layer
LLC is a radio link protocol based on HDLC, which can
provide highly reliable encrypted logical link. LLC layer
generates LLC address and frame filed from the SDDC data
unit of upper layer SNDC layer for generating complete LLC
frame. In addition, LLC can realize the one to many
addressing and the retransmission control of data frame. LLC
is independent from the bottom layer radio interface protocol
for the least modification of NSS when introducing the other
optional GPRS radio resolution. GSM04.64 standardizes LLC.
SNDCP
As the transition between network layer and data link layer,
the main function of SNCDP is to packet the transmitted data
and sent it to the LLC layer for transmission to find out the
TCP/IP address and encryption method.
In SNDC layer, the transmitted data between MS and SGSN
is divided into one or more SNDC data packet units. SNDC
data packet unit is put into LLC frame after being generated.
Relay
Relay forwards the LLC PDU between Um and Gb interface.
Gb Interface
Layer1 (Physical and Transmission Layer)

This layer employs 2 Mbps E1 cable or catory-5 network
cable.
Network Service
Network service is based on frame relay, and it is used to
transmit the upper layer BSSGP PDU.
BSSGP
In
transmission
platform,
this
protocol
provides
connectionless link to transmit data without confirmation
between BSS and SGSN.
IP
It is the internet protocol defined in RFC 791, which is used
for routing user data and control signaling. When it employs
FE for transmission between iBSC and SGSN, the data link
layer at Gb interface uses IP protocol.
FR
Frame relay provides permanent virtual circuit, which
transmits the user data and signaling at Gb data. When it
employs E1 for transmission between iBSC and SGSN, the
data link layer at Gb interface uses FR protocol.
39
Control Plane Protocol Stack in PS Domain

Figure 17 shows the control plane protocol stack in PS domain.
FIGURE 17 CONTROL PLANE STACK PROTOCOL IN PS DOMAIN
GMM/SM implements GPRS mobility management and session

management protocol processing, such as attach/detach,
security management, route area update, location area update,
and PDP context activation/deactivation.
For the details of the other layers, refer to User Plane Protocol
Stack in PS Domain.
40
Chapter
Data Flow Direction

This chapter explains the following topics:
System Clock Signal Flow
User Plane Data Flow
Control Plane Data Flow
System Clock Signal Flow

Figure 18 shows the system clock signal flow of ZXG10 iBSC
(V6.10).
FIGURE 18 SYSTEM CLOCK SIGNAL FLOW
41
CLKG is responsible for following two functions:
CLKG board in the control unit of ZXG10 iBSC (V6.10) is

responsible for providing the clock signals to other parts.
CLKG takes the clock signal from A-interface. After
synchronization, CLKG provides separate clock signals to
resource unit and packet switching unit.
It provides clock signals to resource unit by the UIMU and
packet switching unit through UIMC.
User Plane Data Flow

User plane data flow is divided in to following two parts:
User Plane
Data Flow in
CS Domain
User plane data flow in CS domain
User plane data flow in PS domain
Figure 19 shows the user plane data flow when TC is internal.

FIGURE 19 USER PLANE DAT A FLOW IN CS DOM AIN (TC IS INTERNAL)
Taking uplink direction as an example, the downlink direction is

opposite.
BIU detaches the user plane data and control plane data, sends
the user plane data to TCU for processing. After the processing
of TCU, the data is sent to AIU. The flow direction is 12.
Figure 20 shows the user plane data flow when TC is external.
42
Chapter 5 - Data Flow Direction
FIGURE 20 USER PLANE DAT A FLOW IN CS DOM AIN (TC IS EXTERNAL)

opposite.
BIU detaches the user plane data and control plane data, sends
the user plane data to the Ater interface unit NSMU, and then
sends it to iTC for processing.
User Plane
Data Flow in
PS Domain
Figure 21 shows the user plane data flow in PS domain.

FIGURE 21 USER PLANE DAT A FLOW IN PS DOMAIN

opposite.
The PCU frame detached by BIU interface is sent to UPU (i.e.
UPPB) via user plane switching network and then the user data
in PS domain is detached by UPPB for processing. After that, the
data is sent to GIU via user plane switching network. The flow
direction is 12.
43
Control Plane Data Flow

Control plane data flow is divided in to following two parts:
Control Plane
Data Flow in
CS Domain
Control plane data flow in CS domain
Control plane data flow in PS domain
Figure 22 shows the control plane data flow in CS domain when

TC is internal:
FIGURE 22 CONTROL PLANE DAT A FLOW IN CS DOMAIN (TC IS INTERNAL)
The description of diagram is as follows:
Abis interface signaling flow

f
BIU sends the control plane signaling data to CMP

through the LAPD channel via the control switching
network.
CMP process the control signaling data and send part of it
back to the BIU directly, the data flow direction is 11.
The other part of signaling generates A interface signaling
flow, which is sent to AIU. The flow direction is 12.
A-interface signaling flow

f
44
BIU separate the user plane data and control plane

signaling data.
A-interface unit (AIU) performs the MTP2 processing and

sends the control plane signaling data to the CMP for
MTP3 processing via control plane switching network.
CMP perform the MTP3 processing and also send some
data to the OMP for processing.
OMP send the process result to CMP. CMP send all the
processed data to the AIU via the control plane switching
network.
Chapter 5 - Data Flow Direction
Alternatively the control plane data flow direction can be

from AIU to the CMP via the control plane switching
network and vice versa.
The data flow direction is 2 3 3 2 or 2 2.
Figure 23 shows the control plane data flow in CS domain when

TC is external:
FIGURE 23 CONTROL PLANE DAT A FLOW IN CS DOMAIN (TC IS EXTERNAL)
Control Plane
Data Flow in
PS Domain
Abis interface signaling flow is the same as the case when TC

is internal.
Ater interface control plane signaling is sent from CMP to
NSMU, as shown in flow 2. It reaches iTC via NSMU. Some
global processes involve OMP, as shown in flow 3.
A-interface control plane signaling is sent from CMP to NSMU,
as shown in flow 2, and then sent to MSC via iTC.
Figure 24 shows the control plane data flow in PS domain.

FIGURE 24 CONTROL PLANE DAT A FLOW IN PS DOMAIN
UPU
TCU
4
Abis
Interface
User Plane
Switching Network
AIU
AInterfac
e
BIU
3
1
5
GIU
Control Plane
Switching Network
Gb
Interfac
e
CMP
OM
P
45
The description of diagram is as follows:
Abis interface signaling flow

f
BIU sends the control plane signaling data to the CMP for
processing. CMP process and send back some immediate
data (like immediate assignments) to BIU. The data flow
direction is 1 1.
Control data of some users containing more assignments
need to be sent to user plane/PCU processing unit via the
control plane switching network. User plane/PCU
processing unit process this data and send back to CMP.
CMP transfer this data to BIU through the control plane
switching network. The data flow direction is 1 3 3
1.
By LAPD board of Abis interface unit send user data
(PACCH uplink channel request) to the user plane/PCU
processing unit via the user plane switching network. Use
plane/PCU processing unit send the control signaling data
to CMP for processing. CMP process it and send back to
user plane /PCU processing unit. At the end the user
plane processing unit transfers back the processed data
by user plane switching network to the BIU. The data
flow direction is 2 3 3 2.
Gb interface signaling flow

PCU sends the control data to the corresponding board for
processing, including CMP, OMP and UPPB. After the
processing is finished, the data is sent to Gb interface via
PCU, the data flow direction is 4 4, 5 5 or 6 6.
46
Chapter
Networking Modes and

System Configuration
This chapter contains the following topics:
Abis Interface Networking Modes
A-Interface Networking Mode
Ater Interface Networking Mode
Gb interface networking mode
Operation and Maintenance System Networking
Cabinet Configuration
Shelf Configuration
NM Configuration
Networking Modes
There are interfaces on iBSC for OMC, BTS, MSC and SGSN.
ZXG10 iBSC provides various networking modes at each
interface. In actual practice, select the networking mode
according to the environment flexibly. The following topics
describes various networking modes supported by ZXG10 iBSC
according to the four interfaces respectively.
Abis Interface Networking Modes

ZXG10 iBSC (V6.10) supports all series of ZXG10-BTS models
and can configure corresponding BTS networking modes
including star, chain, tree, and ring types. In practice, these
modes are used in combination to achieve the best priceperformance ratio.
47
Using E1 for Transmission

Star
Networking
The configuration of star networking is shown in Figure 25.

FIGURE 25 ABIS INTERFACE STAR NETWORKING
SITE0
i
B
S
C
SITE1
.
.
.
SITEn
Each site is directly connected to BSC in a star network. The
networking mode is simple, links are reliable, and maintenance
and construction is convenient. This mode is applicable in a
densely populated region.
Chain
Networking
The configuration of chain networking is shown in Figure 26.

FIGURE 26 ABIS INTERFACE CHAIN-NETWORKING
iBSC
SITE0
SITE1
SITE2
A chain network uses less transmission equipment as the sites

are connected using the by-pass or straight through function. If
a shallow depth BTS encounters any broken link, the cascaded
BTS with deeper depth can be directly connected without
affecting normal operation. This mode is applicable in regions
with strip-shaped population distribution.
Tree
Networking
48
The configuration of tree networking is shown in Figure 27.
Chapter 6 - Networking Modes and System Configuration
FIGURE 27 ABIS INTERFACE TREE NETWORKING
S IT E 1
S
I
T
E
0
i
B
S
C
S IT E 2
.
.
.
S IT E n
Tree networking mode is more complex and signal passes

through more nodes with low link reliability. Any fault in upper
level site may affect the normal operation of a lower level site.
This mode is applicable for large areas with sparse population
but not frequently applied.
Ring
Networking
The configuration of ring networking is shown in Figure 28.

FIGURE 28 ABIS INTERFACE RING NETWORKING
iBSC
SITE0
SITE1
SITE2
SITE3
Ring networking is the most useful and advanced networking

mode in GSM communication structure. If any of site links is
broken, the communication starts from the opposite way. This
enhances the system performance and reliability. Due to ring
49
networking mode the inter-site

becomes almost uninterruptible.
and
iBSC
communication
Using IP for Transmission

When use IP for transmission, the BTS accessing iBSC include
macro cell BTS and micro cell BTS.
The typical application scenario of iBSC IP Abis is shown in
Figure 29.
FIGURE 29 ZXG10 IBSC TYPICAL IP ABIS ACCSESS
MS
ADSL MODEM
Micro
Cell BTS
ADSL MODEM
Micro
Cell BTS
Internet Public
INTERNET
Network
xDSL
Access Device
xDSL
MS
ZTE
Intranet
Intranet
Enterprise
Network
MS
Micro
Cell BTS
IP
iBSC
IDedic
CaP
at e
b le
d
Site1
MS
Site2
MS
Micro
Cell BTS
Macro
Cell BTS
MS
MS
Micro
Cell BTS
Generally, macro cell BTS access iBSC directly by IP

dedicated cable.
Micro cell BTS access iBSC in many ways, including:
f
f
50
Access via internet from family by ADSL.

Access the internet via enterprise gateway by deploying
the BTS inside the enterprise.
Access the iBSC via the IP dedicated cable of macro cell
BTS.
A-Interface Networking Mode

Figure 30 shows the ZXG10 iBSC (V6.10) A-interface networking
modes when using E1 for transmission.
FIGURE 30 ZXG10 IBSC (V6.10) A-INTERFACE SYSTEM NETWORKING
iBSC
TC
MSC
A A
Interface
Ater Interface Networking Mode

Figure 32 shows the ZXG10 iBSC (V6.10) Ater interface
networking modes when using E1 for transmission.
FI G U R E 3 1 Z X G 1 0 I B S C ( V 6 . 1 0 ) AT E R I N T E R F AC E S Y S T E M N E T W OR K I N G
Gb Interface Networking Mode

E1 and Fast Ethernet based frame relay protocol is used to
implement Gb interface function between ZXG10 iBSC (V6.10)
and SGSN. The Gb interface networking mode includes crossover
and BSC cascade modes. Figure 32 shows the Gb interface
crossover and BSC cascade networking modes.
51
FIGURE 32 ZXG10-IBSC (V6.10) GB INTERFACE SYSTEM NETWORKING
Multiple iBSCs can be cascaded and then connected to SGSN to

save Gb interface line resources if bandwidth permits. The iBSC
cascade mode is very convenient. For example, iBSC1 is directly
connected to SGSN. iBSC2 can be directly connected to the
other PCM ports of DTB via E1. A transparent transmission from
iBSC2 to SGSN can be implemented via configuration, saving
resource with no need for an E1 between iBSC2 and SGSN.
Operation and Maintenance System

Networking
The ZXG10 iBSC O&M system contains Operation and
Maintenance Module (OMM) and NetNumen M31. OMM is a part
of iBSC and is used for operation and maintenance of iBSC.
ZXG10 iBSC is connected with NetNumen M31 through OMM.
The hardware platform of OMM can be the SBCX board or the
SUN server. The former adopts SBCX configuration while the
latter adopts SVR+SUN server configuration.
ZXG10 iBSC (V6.10) supports two types of maintenance:
Local maintenance networking

ZXG10 iBSC interconnects NetNumen M31 through LAN.
Remote centralized maintenance networking

ZXG10 iBSC interconnects NetNumen M31 through DCN
(including PCM and IP backbone network).
52
Local
Maintenance
Networking
It is the simplest and most common mode. In this mode, the

iBSC and NetNumen M31 are located on the same LAN and
connected via Ethernet. NetNumen M31 and the iBSCs it
manages are physically present in the same location, and they
are connected by LAN.
Figure 33 shows the local maintenance networking when ZXG10
iBSC adopts the SBCX configuration. In this case, the OMC1 port
(it is recommended to set the IP address within network
segment 129) on the rear board of SBCX is connected with OMP
and LMT through LAN Switch. The user performs operation and
maintenance through the LMT terminal. The OMC4 port (it is
recommended to set the IP address within network segment 10)
on the rear board of SBCX is connected with the NetNumen M31
server through LAN Switch, realizing accessing the network
management system.
FIGURE 33 ZXG10 IBSC (V6.10) LOCAL M AINTENANCE NETWORKING
(SBCX CONFIGURATION)
Remote
Centralized
Maintenance
Networking
In the PCM networking mode for remote centralized

maintenance, the 2 Mbps PCM link (A-interface E1) available
between MSC and the iBSC or other dedicated PCM links can be
used to transmit NM information. In this mode, the timeslot in
PCM link is borrowed to transmit operation and maintenance
information at a rate of n x 64 kbps (n is the number of occupied
timeslots). PCM equipment is used to extract a certain number
of timeslots from the PCM links for operation and maintenance.
This approach is economical, practical, and fully utilizes available
53
resources. Figure 34 shows the PCM networking mode for

remote centralized maintenance.
FIGURE 34 ZXG10-IBSC (V6.10) REMOTE PCM NETWORKING MODE
NetNumen M31
Client 1
Client 2
LAN
Router
Router
Client 1
PCM
PCM
equipment equipment
Local iBSC1
Local iBSCn
LAN
MSC
Remote
iBSC-LAN
Remot
iBSC1
e
Figure 35 shows the IP backbone network transmission

networking mode for the remote centralized maintenance.
FIGURE 35 ZXG10-IBSC (V6.10) REMOTE IP NETWORKING MODE
54
System Configuration
In ZXG10 iBSC system, two resource shelves form a Resources
board Configuration Basal Unit (RCBU). It only needs to add
RCBU for capacity expansion.
Cabinet Configuration
ZXG10 iBSC supports single cabinet configuration and dual
cabinet configuration.
Single Cabinet
Configuration
For single cabinet configuration, the position of each shelf in the

cabinet is shown in Figure 36.
FIGURE 36 SINGLE CABINET CONFIGURATION
The description of single cabinet configuration is given in Table

21.
TABLE 21 SINGLE CABINET CONFIGURATION DESCRIPTION
Shelf Name
Whether Necessary
Position in the Cabinet
Control Shelf
Necessary
Position fixed, layer 2
Packet
Switching
Shelf
Necessary
Position fixed, layer 4
Resource
Shelf
Configure one layer or

two layers according to
requirements.
Either layer 1 or layer 3
55
Fully configured single cabinet capacity description is given in

Table 22.
TABLE 22 SINGLE CABINET CAP ACITY DESCRIPTION
Parameter Name
Value
Number of carriers supported
1024
Flow at Gb interface (Mbps)
32
Abis
interface
capacity
E1
208
FE + E1
104 E1+ 4 FE
A interface E1/STM-1
A interface
TC resource
224/4
E1
6792
STM-1
7812
Ater interface E1/STM-1
Dual Cabinet
Configuration
64/1
For dual cabinet configuration, the position of each shelf in the

cabinet is shown in Figure 37.
FIGURE 37 DUAL CABINET CONFIGURATION
The dual cabinet configuration description is given in Table 23.

TABLE 23 DUAL CABINET CONFIGURATION DESCRIPTION
56
Shelf
Name
Whether
Necessary
Control
Shelf
Necessary
Position fixed, at cabinet 1 shelf 2
Packet
Switching
Necessary
Position fixed, at cabinet 1 shelf 4
Shelf
Name
Whether
Necessary
Configure
according to
requirements.
In cabinet 1 it is in the first layer and

the third layer; in cabinet 2, it could be
in any layer.
Shelf
Resource
Shelf
Fully configured dual cabinet capacity description is given in

Table 24.
TABLE 24 DUAL CABINET CAPACITY DESCRIPTION
Parameter Name
Value
Number of carriers supported
3072
Flow at Gb
Interface (Mbps)
Abis Interface
Capacity
Use E1 for
transmission at Ainterface
96
Use STM-1 for

transmission at Ainterface
160
E1
624
FE + E1
312 E1+ 12 FE
A Interface E1/STM-1
A Interface TC
Resource
672/12
E1
20376
STM-1
23436
Ater interface E1/STM-1
192/3
Shelf Configuration
Packet
Switching
Shelf
Configuration
Packet switching configuration is shown in Figure 38.
57
FIGURE 38 P ACKET SWITCHING CONFIGURATION
Packet Switching Shelf

1
10
11
12
13
14
15
16
R
U
I
M
2
R
U
I
M
3
15
16
U
I
M
C
U
I
M
C
17
BPSN
1
G
L
I
G
L
I
G
L
I
G
L
I
P
S
N
P
S
N
10
11
12
13
14
17
The description of packet switching shelf configuration is shown

in Table 25.
TABLE 25 PACKET SWITCHING SHELF CONFIGURATION DESCRIPTION
Control Shelf
Configuration
58
Board Name
UIMC
PSN
GLI
Quantity
2~8
Remark
Necessary
Necessary
Configure
according to
requirements
Corresponding
rear board
RUIM2/RUIM3
UIMC implements the control plane switching function of

packet switching shelf. It is inserted in slot 15 and slot 16
fixedly and it is necessary to configure. The corresponding
back board is RUIM2/RUIM3, which are also necessary.
RUIM2 and RUIM3 are fixedly inserted into slot 15 and 16
respectively.
PSN implements the data switching between line cards
GLI implements GE line card function. It could be inserted in
slot 1~6 or slot 9~14, the quantity can be selected according
to configuration capacity and must appear in pair. The
configuration order principle is increasing from left to right.
The control shelf configuration is shown in Figure 39.
FIGURE 39 CONTROL SHELF CONFIGURATION
Control Shelf
1
R
S
V
B
10 11 12 13 14 15 16 17
R
U
I
M
2
R
U
I
M
3
R
M
P
B
R
M
P
B
R
C
K
G
1
R
C
K
G
2
R
C
H
B
1
R
C
H
B
2
BCTC
1
SVR/
SBCX
10 11 12 13 14 15 16 17
C
M
P
C
M
P
U
I
M
C
U O
I
M
M
C P
O
M
P
C
L
K
G
C
L
K
G
C
H
U
B
C
H
U
B
The control shelf configuration description is given in Table 26.

TABLE 26 CONTROL SHELF CONFIGURATION
Board
Name
Quantity
Remark
Corresponding
Rear Board
OMP
2
(Active/Standby)
Necessary
RMPB
SVR/SBCX
Necessary
RSVB
CMP
2~10
Quantity is
selected
according to
the capacity
UIMC
2
(Active/Standby)
Necessary
RUIM2/RUIM3
CLKG
2
(Active/Standby)
Necessary
RCKG1/RCKG2
CHUB
2
(Active/Standby)
Necessary
RCHUB1/RCHUB2
OMP is inserted in slot 11 and slot 12 fixedly, and it is

necessary. The corresponding rear board is RMPB, which is
necessary and inserted in slot 11 and slot 12 fixedly.
It is necessary to configure one SVR board or one SBCX
board. If SVR is used, it is inserted in slot 2 fixedly, and the
rear board RSVB is inserted in slot 2. If SBCX is used, it is
inserted in slot 1 fixedly, and the rear board RSVB is inserted
in slot 1. The position of RSVB in Figure 39 corresponds to
the case when SVR is used.
CMP could be inserted in slot 1~8 and slot 13~16, the
quantity can be selected according to the capacity.
59
Note: If processing performance needs capacity expansion,

CMP could be inserted in other shelves, and BPSN shelf is
recommended.
Resource Shelf
Configuration
CLKG is inserted in slot 13 and slot 14 fixedly and it is

necessary. The corresponding rear board is RCKG1/RCKG2,
which are necessary. RCKG1 is inserted in slot 13 fixedly and
RCKG2 is inserted in slot 14 fixedly.
CHUB is inserted in slot 15 and slot 16 fixedly and it is
necessary. The corresponding rear board is RCHB1/RCHB2,
which are necessary. RCHB1 is inserted in slot 15 fixedly and
RCHB2 is inserted in slot 16 fixedly.
UIMC is inserted in slot 9 and slot 10 fixedly and it is
necessary. The corresponding rear board is RUIM2/RUIM3,
which are necessary. RUIM2 is inserted in slot 9 fixedly and
RUIM3 is inserted in slot 10 fixedly.
There are various configurations of resource shelf. Take FE + E1

at Abis interface and E1 at A-interface for example, the resource
configuration is shown in Figure 40.
FIGURE 40 RESOURCE SHELF CONFIGURATION
The resource shelf configuration description is given in Table 27.

TABLE 27 RESOURCE SHELF CONFIGURATION DESCRIPTION
60
Board
Name
Quantity
Remark
Corresponding
Rear board
UIMU
Necessary
RUIM1
DTB
Configured
RDTB
Board
Name
Quantity
Remark
Corresponding
Rear board
according to
requirements
SDTB
Configured
according to
requirements
RGIM1, configured
according to
requirements
GUP
Configured
according to
requirements
BIPI
Configured
according to
requirements
RMNIC
UPPB
Configured
according to
requirements
SPB
Configured
according to
requirements
RSPB
The description of the board configuration in resource shelf is as

follows:
UIMU is inserted in slot 9 and slot 10 fixedly and it is

necessary. The corresponding rear board is RUIM1, which is
necessary and inserted into slot 9 and slot 10 fixedly.
DBT can be configured in any slot except slot 9, 10, 15 and
16. The corresponding rear board is RDTB, which is
necessary and inserted in the back board slot corresponding
with DTB.
SDTB can be configured in any slot except slot 9 and 10, but
slot 17 is preferential. If it is inserted in the other slot, the
adjacent slot for active/standby board should not be
configured as the board using HW cable resource, such as
DTB and GUP.
The rear board of SDTB is RGIM1. It is not needed to be
configured unless it needs to extract line 8K. Generally, one
piece of RGIM1 is configured in one system, inserting in the
backplane slot corresponding with SDTB.
When GUP is used as BIPB and TIPB, it is inserted in slot 5~8

and slot 11~14 preferentially. If it is inserted in slot 1~4 and
slot 15~16, the board that does not use the internal media
plane network interface (such as DTB and SDTB) could be
configured in the adjacent slot for GUP active/standby board.
When GUP is used as DRTB, it could be inserted in any slot
except slot 9 and slot 10.
SPB can be inserted in any slot except slot 9 and slot 10, but
only one board could be inserted in slot 15 and slot 16 at the
same time.
61
It is recommended to insert UPPB in slot 5~8 and slot 11~14.

If it is inserted in slot 1~4 and slot 15~16, the board that
does not use the internal media plane network interface
(such as DTB and SDTB) could be configured in the adjacent
slot for UPPB active/standby board.
BIPI is inserted in slot 5~8 and slot 11~14 preferentially.
NM Configuration
SBCX
Configuration
Table 28 shows the hardware configuration of SBCX board.

TABLE 28 HARDW ARE CONFIGURATION OF SBCX BOARD
Name
Configuration
CPU
Two Intel(R) Xeon 2G dual-core CPUs
Memory
4 GB
Hard Disk
Client
Configuration
One 40 GB SATA hard disk

Two 146 GB SAS hard disks; RAID1 mirror
External
Network
Interface
Two GE interfaces
Two FE interfaces
Serial Port
One RS232 serial port
USB
Interface
Two at the front and two at the back
Table 29 shows the hardware configuration of the client.

TABLE 29 HARDW ARE CONFIGURATION OF CLIENT
62
Name
Configuration
CPU
Intel P4 or above, Intel Core2
Memory
1 GB or above
Hard Disk
80 GB or above
Appendix
Abbreviations
Abbreviation
Full Name
A
Abis
A-bis Interface
APB
ATM Process Board
AMP
Application Manage Process
AMR
Adaptive Multi Rate
AMREN
Adaptive Multi Rate Encoding
AMRFR
Adaptive Multi Rate Full Rate
AMRHR
Adaptive Multi Rate Half Rate
B
BCSN
Backplane of Circuit Switch Network
BPSN
Back Plane of Packet Switching Network
BCCH
Broadcast Control Channel
BUSN
Backplane of Universal Switch Network
BCTC
Backplane of Control Centre
BIE
Base station Interface Equipment
BIPP
Abis Interface Peripheral Processor
BIU
Abis Interface Unit
BNET
Backplane of Network Layer
BOSN
Bit Oriented Switching Network
BPCU
Packet Control Unit Shelf
BRP
BSSGP RLC/MAC Protocol
BSC
Base Station Controller
BSMU
Sub-multiplexing Interface Unit
BSS
Base Station Subsystem
BSSAP
Base Station Subsystem Application Part
BSSGP
Base Station Subsystem GPRS Protocol
63
Abbreviation
Full Name
BTS
Base Transceiver Station
BVC
BSSGP Virtual Connection.
C
CHUB
Control Hub
CI
Cell Identity
CLKG
Clock Generator
CMP
Control Main Processor
COMM
Communication Board
D
DPC
Destination Point Code
DRT
Dual Rate Transcoder
DSNI
Digital Switch Network Interface
DSP
Digital Signal Processor
DTB
Digital Trunk Board
DTE
Data Terminal Equipment
DTM
Dual Transfer Mode
E
E1
European Standard for Digital Transmission
EDRT
Enhanced DRT
EFR
Enhanced Full Rate
EFREN
Enhanced Full Rate Encoding
EGSM
Extended GSM
ETSI
European
Institute
Telecommunications
Standards
F
FACCH/F
Fast Associated Control Channel Full Rate
FACHH/H
Fast Associated Control Channel Half Rate
FE
Fast Ethernet
FR
Full Rate
FRP
Frame Relay Protocol
FSMU
Far Sub-multiplexing Unit
FSPP
Far Sub-multiplexing Peripheral Processor
FTP
File Transfer Protocol.
FUC
Frame Unit Controller
64
Gb
Gb Interface
GIPP
Gb Interface Peripheral Processor
Appendix A - Abbreviations
Abbreviation
Full Name
GIU
GPRS Interface Unit
GPP
General Peripheral Processor
GLI
GE Line Interface
GPRS
General Packet Radio Service
GSM
Global System for Mobile communication
H
HDLC
High-level Data Link Control
HMS
High Megabit Switch
HR
Half Rate
HREN
Half Rate Encoding
HSN
Hopping Sequence Number
HW
High Way
I
IMSI
International Mobile Subscriber Identity
IP
Internet Protocol
ISDN
Integrated Services Digital Network
ISUP
Integrated Services User Part
L
LAC
Location Area Code
LAPD
Link Access Protocol on D-Channel
LMT
Local Maintenance Terminal
M
MCC
Mobile Country Code
MMI
Man Machine Interface
MMIC
Multi-server Network Interface Card
MNC
Mobile Net Code
MPB
Main Processor Board
MS
Mobile Station
MSC
Mobile Switching Center
MSS
Mobile Switching System
MTP
Message Transfer Part
N
NC
Network Control
NS
Network Service
NSE
Network Service Entity
NSEI
Network Service Entity Identifier
65
Abbreviation
Full Name
NSMU
Near Sub-multiplexing Unit
NSPP
Near Sub-multiplexing Peripheral Processor
NSVC
Network Service Virtual Connection
NSVCI
Network Service Virtual Connection Identifier
O
OMP
Operation & Maintenance Processor
OMCR
Operation & Maintenance Center Radio
OPC
Operating Point Code
OSI
Open System Interconnection
P
PDP
Packet Data Protocol
R
RPB
Router Protocol Process Board
RCKG2
Rare Board 2 of CLKG
RCHB
Rare Board of CHB
RPSN
Rare Board of PSN
S
SACCH
Slow Associated Control Channel
SCCP
Signaling Connection Control Part
SDCCH
Stand-alone Dedicated Control Channel
SLC
Signaling Link Code
SGSN
Serving GPRS Support Node.
SDTB
Sonnet Digital Trunk Board
SPB
Signaling Process Board
SMS
Short Message Service
SMP
Signaling Main Processor
SS7
Signaling System 7
STD
Subscriber Trunk Dialing
SYCK
Synchronous Clock Board
66
TFI
TDM Fiber Interface
TC
Transcoder
TSNB
TDM Switch Network Board
TCH/F
Traffic Channel Full Rate
TCH/H
Traffic Channel Half Rate
TCP
Transmission Control Protocol
Appendix A - Abbreviations
Abbreviation
Full Name
TCPP
Transcoder Unit Peripheral Processor
TCU
Transcoder and Rate Adaptation Unit
TDMA
Time Division Multiple Access
TIC
Trunk Interface Circuit
TRAU
Transcoder and Rate Adaptor Unit
TRX
Transceiver
TS
Time Slot
U
UIM
Universal Interface Module
V
VTD
Voice Transcoder Card
VTCD
Voice Transcoder Card (DSP)
W
WPB
Wireless Protocol Process Board
67
68
Appendix
Figures
Figure 1 Position of iBSC in the Network (TC is Internal)........2
Figure 2 Position of iBSC in the Network (TC is External) .......2
Figure 3 Physical Structure of ZXG10 iBSC (V6.10) ............. 14
Figure 4 ZXG10 iBSC (V6.10) Hardware System Diagram .... 22
Figure 5 - ZXG10 iBSC Software Structure ........................... 25
Figure 6 Foreground Software System Structure ................ 26
Figure 7 External Interfaces of ZXG10 iBSC (TC is Internal) . 29
Figure 8 External Interfaces of ZXG10 iBSC (TC is External). 30
Figure 9 User Plane Protocol Stack in CS Domain................ 33
Figure 10 Control Plane Protocol Stack in CS Domain .......... 33
Figure 11 Circuit Service Protocol Structure at Um Interface 34
Figure 12 Hierarchical Structure of Control Plane Protocol at
Abis Interface .................................................................. 35
Figure 13 Hierarchical Structure of Control Plane Protocol in CS
Domain at A-Interface....................................................... 36
Figure 14 Hierarchical Structure of Control Plane Protocol in CS
Domain at Ater Interface ................................................... 37
Figure 15 User Plane Protocol Stack in PS Domain .............. 38
Figure 16 - Hierarchical Structure of PS Protocol at Um Interface
..................................................................................... 38
Figure 17 Control Plane Stack Protocol in PS Domain .......... 40
Figure 18 System Clock Signal Flow.................................. 41
Figure 19 User Plane Data Flow in CS Domain (TC is Internal)
..................................................................................... 42
Figure 20 User Plane Data Flow in CS Domain (TC is External)
..................................................................................... 43
Figure 21 User Plane Data Flow in PS Domain .................... 43
69
Figure 22 Control Plane Data Flow in CS Domain (TC is

Internal) ......................................................................... 44
Figure 23 Control Plane Data Flow in CS Domain (TC is
External)......................................................................... 45
Figure 24 Control Plane Data Flow in PS Domain ................ 45
Figure 25 Abis Interface Star Networking .......................... 48
Figure 26 Abis Interface Chain-Networking ........................ 48
Figure 27 Abis Interface Tree Networking .......................... 49
Figure 28 Abis Interface Ring Networking .......................... 49
Figure 29 ZXG10 iBSC Typical IP Abis Accsess ................... 50
Figure 30 ZXG10 iBSC (V6.10) A-Interface System Networking
..................................................................................... 51
Figure 31 ZXG10 iBSC (V6.10) Ater Interface System
Networking...................................................................... 51
Figure 32 ZXG10-iBSC (V 1.0) Gb Interface System
Networking...................................................................... 52
Figure 33 ZXG10 iBSC (V6.10) Local Maintenance Networking
(SBCX Configuration) ........................................................ 53
Figure 34 ZXG10-iBSC (V6.10) Remote PCM Networking Mode
..................................................................................... 54
Figure 35 ZXG10-iBSC (V6.10) Remote IP Networking Mode 54
Figure 36 Single Cabinet Configuration ............................. 55
Figure 37 Dual Cabinet Configuration................................ 56
Figure 38 Packet Switching Configuration .......................... 58
Figure 39 Control Shelf Configuration ............................... 59
Figure 40 Resource Shelf Configuration............................. 60
70
Tables
Table 1 Manual Summary ..................................................i
Table 2 Typographical Conventions.................................... iii
Table 3 Mouse Operation Conventions ............................... iii
Table 4 Usage Explanation of the Hazardous Substances in
ZXG10 iBSC (V6.10) ........................................................... v
Table 6 Weight of iBSC Cabinet........................................ 14
Table 7 Clock Indices of ZXG10 iBSC (V6.10)..................... 14
Table 8 Power Supply Range ........................................... 15
Table 9 Power Consumption of ZXG10 iBSC (V6.10) ........... 15
Table 10 Grounding Requirements of ZXG10 iBSC (V6.10) ... 16
Table 11 Temperature and Humidity Requirements for
iBSC(V6.10) .................................................................... 16
Table 12 Air Pollution and Atmospheric Pressure Requirements
..................................................................................... 16
Table 13 Reliability Indices of ZG10 iBSC (V6.10) ............... 16
Table 14 A-Interface Index (for Internal TC) ...................... 17
Table 15 Ater Interface Index (for External TC) .................. 17
Table 16 Abis Interface Index .......................................... 17
Table 17 Gb Interface Index ............................................ 18
Table 18 Capacity Index of ZXG10 iBSC (V6.10)................. 18
Table 19 Shelves Description ........................................... 23
Table 20 ZXG10 iBSC (V6.10) Boards List ......................... 24
Table 21 Functional Description of ZXG10 iBSC External
Interfaces........................................................................ 30
Table 22 Single Cabinet Configuration Description .............. 55
Table 23 Single Cabinet Capacity Description ..................... 56
Table 24 Dual Cabinet Configuration Description ................ 56
Table 25 Dual Cabinet Capacity Description ....................... 57
Table 26 Packet Switching Shelf Configuration Description ... 58
Table 27 Control Shelf Configuration................................. 59
Table 28 Resource Shelf Configuration Description.............. 60
71
Table 29 Hardware Configuration of SBCX Board ................ 62

Table 30 Hardware Configuration of Client......................... 62
72
Index
A interface networking modes
.................................... 51
BSC cascade networking modes
.................................... 51
capacity index .................... 18
chain network..................... 48
chain networking ................ 48
clock indices....................... 14
development standards ........ 10
DTM ....................................9
GERAN ................................1
grounding requirements ....... 15
Interface Indices ................. 17
Operating temperature ........ 16

Physical indices .................. 13
Relative humidity................ 16
Reliability indices ................ 16
ring networking .................. 49
Software system................. 25
star network ...................... 48
star networking .................. 48
Tree network...................... 49
Voltage ............................. 15
Voltage fluctuation .............. 15
ZXG10 iBSC .....................v, vi
73

ZXG10 IBSC (V6.10) Technical Manual

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ZXG10 IBSC (V6.10) Technical Manual

Hochgeladen von

Copyright:

Verfügbare Formate

ZXG10 iBSC

Base Station Controller

Reason for Revision

Apr. 28, 2008

Aug. 19, 2008

Sep. 25, 2008

ZXG10 iBSC (V6.10) Base Station Controller Technical Manual

Make it more concise/brief

Improve the Contents

Add more step-by-step procedures/tutorials

Improve the organization

Add more troubleshooting information

Include more figures

Make it less technical

Add more examples

Add more/better quick reference aids

Add more detail

Improve the index

This page is intentionally blank.

Declaration of RoHS Compliance..................................... v

System Configuration .................................................... 55

This page is intentionally blank.

About this Manual

Prerequisite Skill and Knowledge

The ZXG10 system and its various components

User Interface on Base Station Controller (BSC)

Local operating procedures

What is in This Manual

Chapter 1, System Overview

This chapter describes the

Chapter 2, System Indices

This chapter describes the

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10 iBSC (V6.10) Base Station Controller Technical Manual

Chapter 3, System Architecture

This chapter describes the ZXG10

Chapter 4, Interfaces and

This chapter describes external

Chapter 5, Data Flow Direction

This chapter describes data flows

Chapter 6, Networking Modes

This chapter describes about the

List of abbreviations used in this

Appendix B, Figures and Tables

List of figures and tables included

Index of important terms and

ZXG10 iBSC (V6.10) Base Station Controller Documentation

Confidential and Proprietary Information of ZTE CORPORATION

About this Manual

ZXG10 BSS (V6.10) Base Station Subsystem Alarm Handling

ZXG10 BSS (V6.10) Base Station Subsystem Notification

ZTE documents employ the following typographical conventions.

References to other Manuals and documents.

Menus, menu options, function-names, input

Keys on the keyboard and buttons on screens

Text that you type, program code, files and

Select one of the parameters that are delimited

TABLE 3 MOUSE OPERATION CONVENTIONS

Refers to clicking the primary mouse button (usually

Refers to quickly clicking the primary mouse button

Refers to clicking the secondary mouse button

Refers to pressing and holding a mouse button and

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10 iBSC (V6.10) Base Station Controller Technical Manual