zxg10 ibsc (v6.10) technical manual

ZXG10 iBSCBase 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: [email protected]

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 R1.0

Serial No. sjzl20083710 Equipment Installation Date

Presentation: (Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization, Appearance)

Good Fair Average Poor Bad N/A

Accessibility: (Contents, Index, Headings, Numbering, Glossary)


Your evaluation of this documentation

Intelligibility: (Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)


Your suggestions for improvement of this documentation

Please check the suggestions which you feel can improve this documentation: Improve the overview/introduction 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

Confidential and Proprietary Information of ZTE CORPORATION i

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.

T AB L E 1 – M AN U AL S U M M AR Y

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,

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

ii 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:

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

Confidential and Proprietary Information of ZTE CORPORATION iii

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

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

Conventions

ZTE documents employ the following typographical conventions.

T AB L E 2 – TY P O G R AP H I C A L C O N V E N T I O N S

Typeface Meaning

Italics References to other Manuals and documents.

“Quotes” Links on screens.

Bold Menus, menu options, function-names, input fields, radio button names, check boxes, drop-down lists, dialog box names, window names.

CAPS Keys on the keyboard and buttons on screens and company name.

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.

T AB L E 3 – M O U S E OP E R AT I O N C O N V E N T I O N S

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.

Typographical Conventions

Mouse Operation

Conventions


iv Confidential and Proprietary Information of ZTE CORPORATION

How to Get in Touch

The following sections provide information on how to obtain support for the documentation and the software.

If you have problems, questions, comments, or suggestions regarding your product, contact us by e-mail at [email protected]. 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 [email protected]; 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.

Customer Support

Documentation Support

Confidential and Proprietary Information of ZTE CORPORATION v

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 (PBB’s)

PolyBrominated Diphenyl Ethers (PBDE’s)

The usage of the above substances in ZXG10 iBSC (V6.10) is explained in Table 4.

T AB L E 4 – U S AG E E X P L A N A T I O N O F T H E H AZ AR D O U S S U B S T AN C E S I N ZXG10 I BSC (V6.10 )

Hazardous substances

Names of Parts

Pb Hg Cd Cr(VI) PBB’s PBDE’s

System × 0 0 0 0 0

Cables and Assembly 0 0 0 0 0 0

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.


vi Confidential and Proprietary Information of ZTE CORPORATION

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.

Confidential and Proprietary Information of ZTE CORPORATION 1

C h a p t e r 1

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).

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.

Future Usage


2 Confidential and Proprietary Information of ZTE CORPORATION

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.

F I G U R E 1 – PO S I T I O N O F I BSC I N T H E N E T W O R K (TC I S I N T E R N AL )

When TC is external, the position of iBSC in the network is shown in Figure 2.

F I G U R E 2 – PO S I T I O N O F I BSC I N T H E N E T W O R K (TC I S E X T E R N AL )

GERAN

Gb

Ater

IuGSM/ UMTS Core Network

MSUm

Iur-g

iBSC

BTS

BTS

BSS

BSS

MS

Iur-g

UTRANRNC

iTC A

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 operator’s 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

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.

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

Supports synchronous handover, non-synchronous handover and pseudo-synchronous handover.

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 the channels with different voice coding rate.

Supports the handover when using DTX.

Supports the handover caused by traffic.

Supports the concentric ring handover based on carrier-to-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:

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

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 high-speed 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 multi-signaling-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 end’s interface and that at the other end’s interface.

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:

The transparent channel between Abis interface and A-interface

The transparent channel between Abis interface and Abis interface

The transparent channel between A-interface and A-interface

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 user’s 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:

3GPP 23.060 – General Packet Radio Service (GPRS) – Service description – Stage 2 (Release 5) – version V5.10.0

3GPP 44.160 – General Packet Radio Service (GPRS) – 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

3GPP 44.060 – General Packet Radio Service (GPRS) – 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


C h a p t e r 2

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.

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.

Size



F I G U R E 3 – PH Y S I C AL S T R U C T U R E O F ZXG10 I BSC (V6 .10)

Table 5 describes the weight of ZXG1 iBSC (V6.10) equipment and load bearing capacity of equipment room floor.

T AB L E 5 – W E I G H T O F I BSC C AB I N E T

Weight

Weight of a single cabinet

≤ 350 kg

Clock Indices

ZXG10 iBSC (V6.10) clock indices are given in Table 6.

T AB L E 6 – C L O C K I N D I C E S O F ZXG10 I BSC (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 frequency deviation

2×10-8/day

Overall Weight

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 synchronization mode

External clock synchronization, extracting from the line clock

2MBITS 2

2 MHz 2 Clock synchronization interfaces Line 8

kbps 2

Power Supply Indices

Table 7 describes the power supply ranges for ZXG10 iBSC (V6.10).

T AB L E 7 – P O W E R S U P P L Y R AN G E

Power Supply Range

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).

T AB L E 8 – P O W E R C O N S U M P T I O N O F ZXG10 I BSC (V6 .10)

Power Consumption

Power consumption of fully-configured single cabinet

2360 W

Power consumption of fully-configured dual-cabinet

5360 W

Environmental Conditions

The ZXG10 iBSC (V6.10) cabinet can be upper-grounded or lower-grounded.

Table 9 describes ZXG10 iBSC grounding indices:

T AB L E 9 – GR O U N D I N G R E Q U I R E M E N T S O F ZXG10 I BSC (V6 .10)

Index Range

Cabinet grounding resistance 0.1 Ω ~ 0.3 Ω

Power Supply Range

Power Consumptions

Index

Grounding Requirements



Index Range

Equipment room grounding resistance < 1 Ω

Table 10 describes the temperature and humidity requirements.

T AB L E 10 – TE M P E R AT U R E A N D H U M I D I T Y R E Q U I R E M E N T S F O R I BSC(V6 .10)

Requirement Range

Long-term operating temperature: 0˚C ~ 40˚C Operating temperature Short-term operating temperature: -5˚C ~ 45˚C

Relative humidity for long-term operation: 20% ~ 90%

Relative humidity

Relative humidity for short-term operation: 5% ~ 95%

Air inside the equipment room must be free of magneto-conductive, conductive, and corrosive gases that may corrode metallic parts and degrade insulation. Table 11 describes the air pollution requirements of ZXG10 iBSC (V6.10).

T AB L E 11 – AI R P O L L U T I O N AN D AT M O S P H E R I C P R E S S U R E R E Q U I R E M E N T S

Requirement Range

Density of dust particles with a diameter larger than 5 µm

≤3×104 grains/m3

Reliability Indices

Reliability indices of ZXG10 iBSC (V6.10) are shown in Table 12.

T AB L E 12 – RE L I AB I L I T Y I N D I C E S O F ZG10 I BSC (V6 .10 )

Index Value

Mean Time Between Failure (MTBF) ≥ 100,000 hours

Mean Time To Repair (MTTR) ≤ 30 minutes

System restart time <10 minutes

Temperature and Humidity Requirements

Air Pollution Requirements



Interface Indices

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 A-interface connects MSC.

T AB L E 13 – A- I N T E R F AC E I N D E X (F O R IN T E R N AL TC)

Maximum Capacity Index

Single Cabinet Dual Cabinet

E1 224 672 A-interface

STM-1 4 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.

T AB L E 14 – AT E R I N T E R F AC E I N D E X (F O R E X T E R N AL TC)



E1 64 192 Ater interface

STM-1 1 3

Abis interface uses following media:

E1 link

Fast Ethernet (FE) link

The Abis interface connects BTS. Table 15 describes the Abis interface index.

T AB L E 15 – AB I S I N T E R F AC E I N D E X



Abis E1 208 624

A-Interface Index

Ater Interface Index

Abis Interface Index





FE + E1 4 FE + 104 E1 12 FE + 312 E1 interface

FE 4 12

Gb interface uses the following media:

E1 link

FE link

The Gb interface connects SGSN. Table 16 describes the Gb-interface index.

T AB L E 16 – GB I N T E R F AC E I N D E X



A-interface adopts E1

32 Mbps 96 Mbps Gb interface flow (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.

T AB L E 17 – CAP AC I T Y I N D E X O F ZXG10 IBSC (V6.10 )

Index Maximum Capacity

E1 672 A-Interface

STM-1 12

E1 624

FE + E1 12 FE + 312 E1

Abis Interface

FE 12

E1 192 Ater Interface

STM-1 3

Gb Interface A-interface adopts 96 Mbps

Gb Interface Index

Foreground- Background

Interface Index



Index Maximum Capacity

E1

A-interface adopts STM-1

160 Mbps

64 kbps link 16 Number of No.7 link

2 Mbps No.7 link 16

Number of Carriers 3072

Number of Sites 1536

BHCA 4200 K

Traffic 15000 Erlang


C h a p t e r 3

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

Figure 4 shows the structure of ZXG10 iBSC (V6.10) hardware system.

Overview



F I G U R E 4 – ZXG10 I BSC (V6 .10 ) H AR D W AR E S Y S T E M D I AG R AM

电源、风扇

处理单元

操作维护单元

外围设备监控单元

接入单元

交换单元

ZXG10 iBSC

BTS

MSC

SGSN

ZTE

TC单元

Processing unit

TC unit

O&M unit

Power, Fan

Peripheral device monitoring unit

Logically, ZXG10 iBSC (V6.10) consists of six units:

Access unit

This unit provides the following interface access processing for iBSC:

A-interface/Ater interface

Abis interface

Gb interface

This unit includes:

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 a large-capacity platform without congestion.

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 foreground-background 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.

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.

T AB L E 18 – SH E L V E S D E S C R I P T I O N

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.



T AB L E 19 – ZXG10 I BSC (V6 .10 ) BO AR D S L I S T

Board Name

Functions Board Function Name

Corresponding Rear Board

BIPI Provide FE interface for iBSC system, there are 4 FE interfaces on each BIPI.

IPBB,

IPAB,

IPGB

RMNIC

CHUB

CHUB and UIMC/UIMU together control the exchange and convergence of the system internal control plane data.

CHUB RCHB1

RCHB2

CLKG Implement the clock function of iBSC system.

CLKG RCKG1

RCKG2

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.

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.

SPB,

GIPB,

LAPD

RSPB

SVR

Store some files needed by OMP, and organize these files according to the requirement of OMC.

SVR RSVB



Board Name

Functions Board Function Name

Corresponding Rear Board

UIMC Provide switching plane for control shelf and packet switching unit shelf.

UIMC RUIM2,

RUIM3

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 -

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.

F I G U R E 5 - ZXG10 I BSC S O F T W AR E S T R U C T U R E

iBSC设备后台网管

前台软件后台软件TCP/IP

iBSC Equipment

Foreground Software

Background Software

Background NM

Foreground Software

The foreground software system structure of ZXG10 iBSC (V6.10) is shown in Figure 6.



F I G U R E 6 – FO R E G R O U N D SO F T W AR E S Y S T E M S T R U C T U R E

HARDWARE

BSP& DRIVER

系统控制子系统（SCS）

数据库子系统

（DBS）

操作维护子系统

（OMS）

信令子

系统

RAN控制

面子系统

（RANC）

承载子系统

（BRS）操作支撑子系统（OSS）

VxWorks

RAN业务支撑子系统

（RANSS）

RAN用户面子系统

（RANU）SCS DBS OMSSignaling Sub-system

RANCRANS

S

RANU

BRS

OSS

Description of the main parts of software system is as follows:

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.

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.

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.

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.

Operation & Maintenance Subsystem (OMS) is a foreground realization of OMCR and LMT. It performs following functions:

Performance management

BSP Subsystem

OSS

DBS

BRS

OMS



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 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.

RAN Control Plane Subsystem (RANC) performs the following functions:

Implements processing of layer-3 control plane protocols at Um, Abis, A, and Gb interface.

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:

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.

SCS

Signaling Subsystem

RANC

RANU

RANSS



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:

Configuration management

Fault management

Performance management

System management


C h a p t e r 4

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.

F I G U R E 7 – EX T E R N AL I N T E R F AC E S O F ZXG10 I BSC (TC I S I N T E R N A L )

MSC

BTS

iBSC

SGSN

A口 Gb口

Abis口

MSC

A口

BTS iOMCR

Abis口前后台接口

When TC is external, the external interfaces of ZXG10 iBSC (V6.10) are shown in Figure 8.



F I G U R E 8 – EX T E R N AL I N T E R F AC E S O F ZXG10 I BSC (TC I S E X T E R N AL )

The functional description of ZXG10 iBSC external interfaces is given in Table 20.

T AB L E 20 – FU N C T I O N AL D E S C R I P T I O N O F ZXG10 I BSC E X T E R N AL I N T E R F AC E S

External System

External System Function

Relative Interfaces

BTS 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.

MSC (TC is internal)

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.

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.

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.

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.

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.

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.

E1 Interface

STM-1 Interface

E1 Interface

STM-1 Interface



The Abis interface of iBSC supports two kinds of interfaces.

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.

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.

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.

E1 Interface

FE Interface

E1 Interface

FE Interface



User Plane Protocol Stack in CS Domain

Figure 9 shows the user plane stack protocol in CS domain.

F I G U R E 9 – US E R P L AN E P R O T O C O L ST AC K I N CS D O M A I N

G.711/TFO

AUm

MS

Relay

GERAN 2G-MSC

L1L1PHY

AMR/FR/EFR/HR

PHY

Transcoding /TRAU “Relay”

RLPRLP

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).

F I G U R E 10 – C O N T R O L PL AN E P R O T O C O L S T AC K I N CS D O M AI N

CM

MM

RR

LapDm

MS

RR

LapDm

Um

LapD

BTSM

LapD

Abis

RRBTSM SCCP

MTP3

BSSAP

BTS iBSC

MTP2

SCCP

MTP3

BSSAP

MTP2

CM

MM

MSC

A物理层

RUDP RUDP

PhysicalLayer

Protocol layers of control plane in CS domain at UM interface are shown in Figure 11.

Um Interface



F I G U R E 11 – C I R C U I T S E R V I C E P R O T O C O L S T R U C T U R E AT U M I N T E R F AC E

CM

MM

RR

LAPDm

Layer1 Layer1

LAPDm

RR

MS BTS

Um接口Um Interface

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.

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.

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.

Abis Interface



F I G U R E 12 – H I E R AR C H I C A L S T R U C T U R E O F C O N T R O L P L AN E P R O T O C O L AT AB I S I N T E R F AC E

Abis接口

BTS

BTSM

LAPD

Layer1

iBSC

Layer1

RUDP

BTSM

RR

RUDP LAPD

Abis Interface

Layer1 – Physical Layer

It could employ 2 Mbps E1 cable or Cat-5 network cable.

Layer2 – Data Link Layer

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 are shown in Figure 13.

A-Interface (TC is Internal)



F I G U R E 13 – H I E R AR C H I C A L S T R U C T U R E O F C O N T R O L P L AN E P R O T O C O L I N CS D O M AI N A T A- I N T E R F AC E

BSC

MTP3

MTP2

Layer1

MSC

A-Interface

Layer1

MTP2

MTP3

RR

SCCP SCCP

BSSAP

BSSAP

MM

CM


It defines the physical layer structure of MSC and BSC, including physical and electrical parameters and channel structure.

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

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 includes BSS application rules and BSSAP.

It maintains and manages the resource and connection of BTS subsystem, controls the service connection and release.

The layers of control plane protocol in CS domain at Ater interface are shown in Figure 14.

Ater Interface (TC is External)



F I G U R E 14 – H I E R AR C H I C A L S T R U C T U R E O F C O N T R O L P L AN E P R O T O C O L I N CS D O M AI N A T AT E R I N T E R F AC E

iBSC

MTP3

MTP2

Layer1

iTC

Ater Interface

Layer1

MTP2

MTP3

SCCP SCCP

Ater Interface Application

Layer

Ater Interface Application

Layer


It defines the physical layer structure of iTC and iBSC, including physical and electrical parameters and channel structure.

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

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.



F I G U R E 15 – U S E R P L AN E P R O T O C O L S T AC K I N PS D O M AI N

Figure 16 shows the protocol layer at Um interface.

F I G U R E 16 - H I E R AR C H I C AL S T R U C T U R E O F PS P R O T O C O L AT U M I N T E R F AC E

MS

Um 接口

BSS

RLC

MAC

relay

RLC

MAC

LLC

SNDCP

PHYPHYUm

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:

Um Interface



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.

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.

Gb Interface



Control Plane Protocol Stack in PS Domain

Figure 17 shows the control plane protocol stack in PS domain.

F I G U R E 17 – C O N T R O L PL AN E S T AC K P R O T O C O L I N PS D O M AI N

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.


C h a p t e r 5

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).

F I G U R E 18 – S Y S T E M C L O C K S I G N AL FL O W



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 PS domain

Figure 19 shows the user plane data flow when TC is internal.

F I G U R E 19 – U S E R P L AN E D AT A FL O W I N CS D O M AI N (TC I S I N T E R N A L )

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 1→2.

Figure 20 shows the user plane data flow when TC is external.

User Plane Data Flow in

CS Domain

Chapter 5 - Data Flow Direction


F I G U R E 20 – U S E R P L AN E D AT A FL O W I N CS D O M AI N (TC I S E X T E R N AL )


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.

Figure 21 shows the user plane data flow in PS domain.

F I G U R E 21 – U S E R P L AN E D AT A FL O W I N PS D O M AI N


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 1→2.

User Plane Data Flow in

PS Domain



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 PS domain

Figure 22 shows the control plane data flow in CS domain when TC is internal:

F I G U R E 22 – C O N T R O L PL AN E D AT A FL O W I N CS D O M A I N (TC I S I N T E R N AL )

The description of diagram is as follows:

Abis interface signaling flow

BIU separate the user plane data and control plane signaling data.

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 1→1.

The other part of signaling generates A interface signaling flow, which is sent to AIU. The flow direction is 1→2.

A-interface signaling flow

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.

Control Plane Data Flow in

CS Domain

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:

F I G U R E 23 – C O N T R O L PL AN E D AT A FL O W I N CS D O M A I N (TC I S E X T E R N AL )

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.

F I G U R E 24 – C O N T R O L PL AN E D AT A FL O W I N PS D O M A I N

BIU

User Plane Switching NetworkAbis

Interface

AIU

A-Interfac

e

GIU

Gb Interfac

e1

4

Control Plane Switching Network

CMPOMP

6

UPU TCU

2

35

Control Plane Data Flow in

PS Domain



The description of diagram is as follows:

Abis interface signaling flow

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.


C h a p t e r 6

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 price-performance ratio.



Using E1 for Transmission

The configuration of star networking is shown in Figure 25.

F I G U R E 25 – AB I S I N T E R F AC E S T AR N E T W O R K I N G

iBSC

SITE0

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.

The configuration of chain networking is shown in Figure 26.

F I G U R E 26 – AB I S I N T E R F AC E C H AI N -N E T W O R K I N G

SITE0iBSC 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.

The configuration of tree networking is shown in Figure 27.

Star Networking

Chain Networking

Tree Networking

Chapter 6 - Networking Modes and System Configuration


F I G U R E 27 – AB I S I N T E R F AC E TR E E N E T W O R K I N G

iBSC

SITE0

S IT E 1

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.

The configuration of ring networking is shown in Figure 28.

F I G U R E 28 – AB I S I N T E R F AC E R I N G N E T W O R K I N G

iBSC

SITE0

SITE2

SITE1

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

Ring Networking



networking mode the inter-site and iBSC communication becomes almost uninterruptible.

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.

F I G U R E 29 – ZXG10 I BSC TY P I C AL IP AB I S AC C S E S S

MS

ADSL MODEM

ADSL MODEM

MSxDSL接入设备

MS

MS

MS

MS

Site1

Site2

MS

iBSCIP专

线

ZTE

宏蜂窝基站

INTERNET公网

Intranet企业网

微蜂窝基站

微蜂窝基站

微蜂窝基站

微蜂窝基站

微蜂窝基站

Micro Cell BTS

Macro Cell BTS

Micro Cell BTS

Micro Cell BTS

Micro Cell BTS

Micro Cell BTS

IP DedicatedCable

IntranetEnterprise Network

Internet PublicNetwork

xDSL Access Device

Generally, macro cell BTS access iBSC directly by IP dedicated cable.

Micro cell BTS access iBSC in many ways, including:

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.

F I G U R E 30 – ZXG10 I BSC (V6 .10 ) A- I N T E R F AC E S Y S T E M NE T W O R K I N G

iBSC TC

A接口

MSC

A Interface

Ater Interface Networking Mode

Figure 32 shows the ZXG10 iBSC (V6.10) Ater interface networking modes when using E1 for transmission.

F I G U R E 31 – ZXG10 I BSC (V6 .10 ) AT E R I N T E R F AC E S Y S T E M N E T W O R 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.



F I G U R E 32 – ZXG10- I BSC (V6 .10 ) GB I N T E R F AC E S Y S T E M N E T W O R K I N G

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).



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.

F I G U R E 33 – ZXG10 I BSC (V6 .10 ) LO C AL M AI N T E N A N C E N E T W O R K I N G (SBCX C O N F I G U R AT I O N )

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

Local Maintenance Networking

Remote Centralized

Maintenance Networking



resources. Figure 34 shows the PCM networking mode for remote centralized maintenance.

F I G U R E 34 – ZXG10- I BSC (V6 .10 ) R E M O T E PCM NE T W O R K I N G M O D E

PCM equipment

Router

MSCRemot

eiBSC1

LAN

NetNumen M31 Client 1 Client 2

Local iBSC1 iBSCn

LAN

Local

Client 1Router

PCM equipment

RemoteiBSC-LAN

Figure 35 shows the IP backbone network transmission networking mode for the remote centralized maintenance.

F I G U R E 35 – ZXG10- I BSC (V6 .10 ) R E M O T E IP NE T W O R K I N G M O D E



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.

For single cabinet configuration, the position of each shelf in the cabinet is shown in Figure 36.

F I G U R E 36 – S I N G L E C AB I N E T C O N F I G U R AT I O N

分组交换框

层1

资源框

控制框

资源框

层4

层3

层2

The description of single cabinet configuration is given in Table 21.

T AB L E 21 – S I N G L E C AB I N E T C O N F I G U R AT I O N D E S C R I P T I O N

Shelf Name Whether Necessary Position in the Cabinet

Control Shelf Necessary Position fixed, layer 2


Necessary Position fixed, layer 4

Resource Shelf

Configure one layer or two layers according to requirements.

Either layer 1 or layer 3

Single Cabinet Configuration



Fully configured single cabinet capacity description is given in Table 22.

T AB L E 22 – S I N G L E C AB I N E T C AP AC I T Y D E S C R I P T I O N

Parameter Name Value

Number of carriers supported 1024

Flow at Gb interface (Mbps) 32

E1 208 Abis interface capacity FE + E1 104 E1+ 4 FE

A interface E1/STM-1 224/4

E1 6792 A interface TC resource STM-1 7812

Ater interface E1/STM-1 64/1

For dual cabinet configuration, the position of each shelf in the cabinet is shown in Figure 37.

F I G U R E 37 – D U AL C AB I N E T C O N F I G U R AT I O N

分组交换框

层1

1号机柜（主机柜） 2号机柜

资源框

控制框

资源框

资源框

资源框

资源框

资源框

层4

层3

层2

The dual cabinet configuration description is given in Table 23.

T AB L E 23 – DU AL C AB I N E T C O N F I G U R AT I O N D E S C R I P T I O N

Shelf Name

Whether Necessary

Position in the Cabinet

Control Shelf

Necessary Position fixed, at cabinet 1 shelf 2

Packet Switching

Necessary Position fixed, at cabinet 1 shelf 4

Dual Cabinet Configuration



Shelf Name

Whether Necessary

Position in the Cabinet

Shelf

Resource Shelf

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.

Fully configured dual cabinet capacity description is given in Table 24.

T AB L E 24 – DU AL C AB I N E T C AP AC I T Y D E S C R I P T I O N

Parameter Name Value

Number of carriers supported 3072

Use E1 for transmission at A-interface

96

Flow at Gb Interface (Mbps) Use STM-1 for

transmission at A-interface

160

E1 624 Abis Interface Capacity FE + E1 312 E1+ 12 FE

A Interface E1/STM-1 672/12

E1 20376 A Interface TC Resource STM-1 23436

Ater interface E1/STM-1 192/3

Shelf Configuration

Packet switching configuration is shown in Figure 38. Packet Switching

Shelf Configuration



F I G U R E 38 – P AC K E T S W I T C H I N G C O N F I G U R AT I O N

RUIM2

RUIM3

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

GLI

GLI

GLI

GLI

PSN

PSN

UIMC

UIMC

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17


BPSN

The description of packet switching shelf configuration is shown in Table 25.

T AB L E 25 – PAC K E T S W I T C H I N G S H E L F CO N F I G U R AT I O N D E S C R I P T I O N

Board Name UIMC PSN GLI

Quantity 2 2 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. Control Shelf Configuration



F I G U R E 39 – C O N T R O L S H E L F C O N F I G U R AT I O N

RSVB

RUIM2

RUIM3

RMPB

RMPB

RCKG1

RCKG2

RCHB1

RCHB2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

SVR/SBCX

CMP

CMP

UIMC

UIMC

OMP

OMP

CLKG

CLKG

CHUB

CHUB

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

BCTC

Control Shelf

The control shelf configuration description is given in Table 26.

T AB L E 26 – CO N T R O L S H E L F C O N F I G U R AT I O N

Board Name

Quantity Remark Corresponding Rear Board

OMP 2 (Active/Standby)

Necessary RMPB

SVR/SBCX 1 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.



Note: If processing performance needs capacity expansion, CMP could be inserted in other shelves, and BPSN shelf is recommended.

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.

F I G U R E 40 – R E S O U R C E S H E L F C O N F I G U R AT I O N

The resource shelf configuration description is given in Table 27.

T AB L E 27 – RE S O U R C E S H E L F C O N F I G U R AT I O N D E S C R I P T I O N

Board Name

Quantity Remark Corresponding Rear board

UIMU 2 Necessary RUIM1

DTB - Configured RDTB

Resource Shelf Configuration



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.



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

Table 28 shows the hardware configuration of SBCX board.

T AB L E 28 – HAR D W AR E C O N F I G U R AT I O N O F SBCX B O AR D

Name Configuration

CPU Two Intel(R) Xeon 2G dual-core CPUs

Memory 4 GB

One 40 GB SATA hard disk Hard Disk

Two 146 GB SAS hard disks; RAID1 mirror

Two GE interfaces External Network Interface 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.

T AB L E 29 – HAR D W AR E C O N F I G U R AT I O N O F C L I E N T

Name Configuration

CPU Intel P4 or above, Intel Core2

Memory 1 GB or above

Hard Disk 80 GB or above

SBCX Configuration

Client Configuration


A p p e n d i x A

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




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 Telecommunications Standards Institute

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

G

Gb Gb Interface

GIPP Gb Interface Peripheral Processor

Appendix A - Abbreviations



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




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

T

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



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


A p p e n d i x B

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



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


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



Table 29 – Hardware Configuration of SBCX Board ................ 62

Table 30 – Hardware Configuration of Client......................... 62


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

zxg10 ibsc (v6.10) technical manual

Documents