SJ-20100603155704-007-ZXWR RNC (V3[1].09.30) System Description

ZXWR RNCRadio Network Controller

System Description

Version 3.09.30

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright © 2010 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-RATION 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 CORPORATIONor of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,the user of this document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 20100712 First Edition (V3.09.30.03)

R1.1 20100827 Modify:

1. 1.5 Appearance

2. 1.6 Characteristics

3. 2.2 Interface Indices

4. 2.8 Environmental Requirements

5. 3.2.1 Positioning Function

6. 3.2.2 HSDPA Function

7. 3.2.3 HSUPA Function

8. 3.2.4 HSPA+ Function

9. 3.4 Radio Resource Management

10. 3.4.1 Radio Measurement Function

11. 3.4.2 AC Function

12. 3.4.4 PC Function

13. 3.4.5 HC Function

14. 3.4.7 DRBC Function

15. 4.1.1 Logic Structure

16. 4.1.3 Logic Unit Description

17. 4.2.1 Shelves

18. 4.2.2 Boards

19. 4.2.3 Cables

20. 6.2.2 Transmission Networking Mode Based onSDH

Revision No. Revision Date Revision Reason

21. 6.2.3 Transmission Networking Mode Based onIP

22. 6.2.4 Hybrid Transmission Mode

Delete: 3.4.6 PS Function

Add:

1. 3.4.7 Congestion Control Function

2. 3.4.8 Code Resource Control Function

3. 3.4.9 Load Balancing Function

4. 7.1 Hardware Reliability Design

5. 7.2 Software Reliability Design

Serial Number: SJ-20100603155704-007

This page is intentionally blank.

Contents

Preface.............................................................. I

Overview...........................................................1Name............................................................................ 1

Nameplate..................................................................... 1

Location in Network ........................................................ 1

Type ............................................................................. 2

Appearance ................................................................... 3

Characteristics ............................................................... 4

Indices ..............................................................7ZXWR RNC Performance Indices ....................................... 7

ZXWR RNC Interface Indices ............................................ 7

ZXWR RNC Clock Indices ................................................. 9

ZXWR RNC Reliability Indices ..........................................10

ZXWR RNC EMC Indices..................................................10

ZXWR RNC Dimensions and Weight..................................11

ZXWR RNC Power Supply Requirements............................11

ZXWR RNC Environmental Requirements ..........................12

ZXWR RNC Safety Protection Instructions .........................12

Services and Functions....................................15Functions .....................................................................15

Services .......................................................................15

Positioning Function ...................................................15

HSDPA Function ........................................................16

HSUPA Function ........................................................16

HSPA+ Function ........................................................16

MBMS Function .........................................................16

Interface Signaling Processing.........................................16

Allocation and Release of Radio Access Loading

Function ...........................................................17

Node B Logic Operation and Maintenance Function .........17

Security Mode Control Function ...................................17

Confidential and Proprietary Information of ZTE CORPORATION I

ZXWR RNC System Description

Synchronization Function............................................18

NAS Message Forwarding Function ...............................18

System Message Broadcast Function ............................18

Paging Function.........................................................18

Radio Resource Management...........................................18

Radio Measurement Function.......................................18

AC Function ..............................................................19

LC Function ..............................................................19

PC Function ..............................................................19

HC Function..............................................................20

DRBC Function ..........................................................21

Congestion Control Function........................................22

Code Resource Control Function ..................................22

Load Balancing Function .............................................23

User Data Transmission ..................................................23

Compositions...................................................25Logic Compositions ........................................................25

Logic Structure..........................................................25

Logic Unit Allocation of ZXWR RNC System....................25

ZXWR RNC Logic Unit Description ................................26

Hardware Compositions..................................................27

ZXWR RNC Shelves....................................................27

ZXWR RNC Boards.....................................................29

ZXWR RNC Cables .....................................................37

Software Compositions...................................................44

Overall Structure of ZXWR RNC Software System...........44

Subsystems ..............................................................45

Operating Environment ...................................49RNC/NM Software Overview ............................................49

Software Types .............................................................50

Version Software ...........................................................50

Version Software Definition .........................................50

Version Software Types and Operating Environ-

ment ...............................................................50

Lower Layer Frozen Software ..........................................51

Lower Layer Frozen Software Definition ........................51

Lower Layer Frozen Software Compositions...................51

Networking .....................................................53NM Networking Plan.......................................................53

Iub,Iur Interface Networking Mode ..................................54

II Confidential and Proprietary Information of ZTE CORPORATION

Transmission Networking Mode Based on ATM

Switch..............................................................54

Transmission Networking Mode Based on SDH ...............54

Transmission Networking Mode Based on IP ..................55

Hybrid Transmission Mode ..........................................55

Iub Interface Networking Mode........................................56

Star Networking Mode................................................56

Chain Networking Mode..............................................56

Ring Networking Mode ...............................................57

Hybrid Networking Mode of Star and Chain ...................57

Iu Interface Networking Mode .........................................58

Reliability ........................................................61Hardware Reliability Design.............................................61

Backup Mode Classification .........................................61

Board Backup Modes..................................................62

Software Reliability Design..............................................64

EMC.............................................................................65

Whole-Equipment Heating ..............................................65

Heating ....................................................................65

Heat Dissipation ........................................................65

International Certificates ................................67TUV Certificate ..............................................................67

CE Certificate................................................................68

Figures ............................................................71

Tables .............................................................73

Glossary ..........................................................75

Confidential and Proprietary Information of ZTE CORPORATION III



IV Confidential and Proprietary Information of ZTE CORPORATION

Preface

Purpose Thank you very much for choosing the UMTS wireless access sys-tem of ZTE Corporation!

The UMTS wireless access system of ZTE is a 3G mobile commu-nication system developed on a basis of the UMTS technology. Itfeatures strong capability in CS and PS service processing and pro-vides diversified services. Compared with GSM, UMTS delivers awider range of telecommunication services, including such multi-media services as voice, data, and image transmission, with higherrate and resource utilization ratio.

ZXWR RNC, a new generation radio network controller in the ZTEUMTS V3 family, delivers functions of system access control, secu-rity mode control, mobility management, and radio resource man-agement and control.

ZXWR RNC provides all the functions defined in the 3GPPR99/R4/R5/R6/R7 protocol, and offers Iu, Iub, and Iur seriesstandard interfaces, which enable it to connect with CNs, RNCs,and Node Bs from different manufacturers.

Developed on a basis of ZTE all IP unified hardware platform,ZXWR RNC features a distributed design, separating control planeand user plane as well as interface and application. It supportsATM/IP dual protocol stack and can smoothly evolve to full IPUTRAN.

What is in ThisManual

This manual contains the following chapters:

Chapter Summary

Chapter 1, Overview Introduces the name, nameplate, type,appearance and characteristics of ZXWR RNCproducts.

Chapter 2, Indices Introduces the system indices of ZXWR RNCproducts.

Chapter 3, Serviceand Function

Introduces the services and functions thatZXWR RNC products provide.

Chapter 4,Compositions

Introduces the compositions of ZXWR RNCproducts, including the hardware equipmentand the software modules.

Chapter 5, OperatingEnvironment

Introduces the operating environment ofZXWR RNC products, referring the hardwareplatform that the software operates.

Chapter 6, Networking Introduces the networking of ZXWR RNCinterfaces.

Confidential and Proprietary Information of ZTE CORPORATION I


Chapter Summary

Chapter 7, Reliability Introduces the reliability design of ZXWR RNCproducts.

Chapter 8,InternationalCertificates

Introduces the international certificates ofZXWR RNC products.

IntendedAudience

� System engineer

� Maintenance engineer

II Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 1

Overview

Table of ContentsName ............................................................................... 1Nameplate......................................................................... 1Location in Network ............................................................ 1Type ................................................................................. 2Appearance ....................................................................... 3Characteristics ................................................................... 4

NameZXWR RNC WCDMA Radio Network Controller

NameplateThe ZXWR RNC nameplate is as shown in Figure 1.

FIGURE 1 ZXWR RNC NAMEPLATE

Location in NetworkThe location of ZXWR RNC in the whole WCDMA system is as shownin Figure 2.

Confidential and Proprietary Information of ZTE CORPORATION 1


FIGURE 2 LOCATION OF ZXWR RNC IN WCDMA SYSTEM

As shown in Figure 2, WCDMA system consists of CN, UTRAN andUE.

CN falls into CS domain and PS domain.

1. MSC Server and MGW form the circuit domain based onTDM/ATM/IP core network.

� In CS domain, MSC Server is the control center of the mo-bile core network, implementing the call connection andcontrol.

� MGW, as the media gateway, implementing the radio accessof 2G and 3G, the conversion of the transmission streamand media stream.

2. SGSN, GGSN, and CG (not directly connected with ZXWR RNC)form the PS domain based on IP core network.

� In PS domain, SGSN is the control centre of the mobile corenetwork, implementing the network access control, routeselecting and forwarding, mobility management, sessionmanagement, and collecting the charging information.

� GGSN is the gateway of the mobile network and the Inter-net.

ZXWR RNC belongs to UTRAN. UTRAN includes one or several RNSsand one RNS consists of one ZXWR RNC and one or several NodesB.

Therefore, in WCDMA, ZXWR RNC is between Node B and CN. Inthe radio access network, it plays an important role in the radioaccess and network optimization.

TypeZXWR RNC is a type of mobile access equipment.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Overview

AppearanceZXWR RNC uses the standard 19” cabinet. Its dimensions are2,000 mm × 600 mm × 800 mm (H × W × D).

The appearance of ZXWR RNC is as shown in Figure 3.

FIGURE 3 ZXWR RNC APPEARANCE

The physical specifications that ZXWR RNC cabinet complies withare as shown in Table 1.

TABLE 1 ZXWR RNC CABINET PHYSICAL SPECIFICATIONS

Name Description

Standard The structure design complies withIEC60297.

Dimensions 2,000 mm × 600 mm × 800 mm (H × W ×D)

Color Black cabinet door and navy cabinet body

Structure Four layers of subracks, 17 slots on eachlayer



Name Description

Qty. of Cabinets 1–3 (either a single cabinet or two/threecabinets combined, according to the traffic)

Weight when fullyconfigured 870 kg (three cabinets)

Bearing requirementsof the equipment roomground

450 kg/m2

CharacteristicsZXWR RNC product is developed to reduce clients’ investment dur-ing the whole 3G product life period. Its design of directly pro-viding large-capacity linear expansion helps the users to considerabout the requirements for the equipment performance in the caseof 3G service blossom in advance. Its distributed design helpsto separate the process on the control plane from on the userplane, and separate the interface from the applications. In ad-dition, ZXWR RNC product supports the IP UTRAN transmissionmode.

� Large capacity, strong expansibility

ZXWR RNC can provide the expansible large-capacity productsto meet the increase of the services and to suit different trafficsurroundings. The control plane and the user plane are de-signed in the distributed mode, which enables the whole sys-tem free of any bottleneck for the centralized processing. Theprocessing resources on the control plane and the user planecan be linearly expanded with the capacity.

� IP structure design, highly effective and flexible

ZXWR RNC adopts the IP-based switching platform. IP struc-ture enables the data to transmit highly-effective and flexibly.The high-performance packet data processing platform equipsthe system with non-blocking data switching capacity.

ZXWR RNC supports the VLAN technology, which helps to ef-fectively isolate the broadcast storm on Ethernet, increase thenetwork security, and manage users more conveniently andhigh-effectively.

Compared with the platform with ATM structure, IP switchingmanagement is easy to maintain, simple to configure, flexibleto expand, and highly effective to transmit. The transmissionsystem is flexible too. Therefore, IP structure can better meetthe rapid increase of the future mobile services.

� High reliability

ZXWR RNC has a very high reliability. All key parts of the sys-tem are in 1_1 M/S mode, and other parts are at least in N+1backup mode. The system supports the on-line software down-loading.

� Excellent radio resource management


Chapter 1 Overview

ZXWR RNC occupies scores of special technologies in the ra-dio resource management. ZXWR RNC supports the auto opti-mization of the radio parameters. In addition, ZXWR RNC canallocate and schedule the radio resources according to the net-work load and QoS level.

� Abundant interfaces and flexible networking

ZXWR RNC supports ATM/IP dual-protocol stack, supportingphysical interfaces, such as E1/T1, STM-1, channelized STM-1,IP Over E1, FE, GE, and POS. In different phases, users canmake different networking flexibly according to the actualcases, easily and smoothly transiting to all-IP UTRAN plan.

� Diversified network management functions

The RNC provides a full range of network management inter-faces for the access of network management software and CTSwhole-network signaling tracing software.

By using network management software, users can conve-niently manage the configuration, performance, and alarm ofthe RNC. The RNC provides interfaces for the access of signal-ing tracing software to support inter-NE signaling tracing.





C h a p t e r 2

Indices

Table of ContentsZXWR RNC Performance Indices ........................................... 7ZXWR RNC Interface Indices ................................................ 7ZXWR RNC Clock Indices ..................................................... 9ZXWR RNC Reliability Indices ..............................................10ZXWR RNC EMC Indices .....................................................10ZXWR RNC Dimensions and Weight......................................11ZXWR RNC Power Supply Requirements................................11ZXWR RNC Environmental Requirements ..............................12ZXWR RNC Safety Protection Instructions .............................12

ZXWR RNC PerformanceIndicesThe performance indices of ZXWR RNC are shown in Table 2.

TABLE 2 PERFORMANCE INDICES

Index Name Index Value

Maximum traffic 76800 Erl

Maximum data traffic (UL + DL) 9600 Mbps

Maximum number of Node Bs 1960

Maximum number of cells 5880

Maximum BHCA 7000 K

ZXWR RNC InterfaceIndicesThe interface indices of ZXWR RNC are shown in Table 3.



TABLE 3 INTERFACE INDICES

Transmis-sion Type

Standard InterfaceBoard

Port Type Remarks

DTA DB68 Providing 32E1s / T1sfor the ATMtransmis-sion at theIub inter-face

E1/T1 ITU-T G.703/G.704

DTI DB68 Providing 32E1s / T1s forthe IP trans-mission atthe Iub in-terface

ITU-T G.957

ITU-TI.432.1

SDTA2 LC/PC Provid-ing twochannel-ized STM-1/OC-3 op-tical interfa-ces for theATM trans-mission atthe Iub in-terface

ChannelizedSTM-1/OC-3

ITU-TI.432.2

SDTI LC/PC Provid-ing twochannel-ized STM-1/OC-3 op-tical interfa-ces for theIP transmis-sion at theIub inter-face

ITU-T G.957

ITU-TI.432.1

APBE LC/PC Providingfour non-channel-ized STM-1/OC-3c op-tical inter-faces forthe ATMtransmis-sion at theIub/Iu/Iurinterface

Non-Channelized

STM-1/OC-3c

ITU-TI.432.2

POSI LC/PC Providingfour non-channel-ized STM-1/OC-3c op-tical interfa-ces for theIP transmis-


Chapter 2 Indices

Transmis-sion Type

Standard InterfaceBoard

Port Type Remarks

sion at theIub/Iu/Iurinterface

FE IEEE 802.3 GIPI3configuredwith FEelectricalinterface

RJ45 Providingfour FEports for theIP transmis-sion at theIub/Iu/Iurinterface

GIPI3configuredwith GEelectricalinterface

RJ45 Providingtwo GE elec-trical inter-faces for theIP transmis-sion at theIub/Iu/Iurinterface

GE IEEE 802.3

GIPI3configuredwith GEopticalinterface

LC/PC Providingtwo GE op-tical interfa-ces for theIP transmis-sion at theIub/Iu/Iurinterface

ZXWR RNC Clock IndicesThe clock indices of ZXWR RNC are shown in Table 4.

TABLE 4 CLOCK INDICES


Synchronization level Class A, Stratum 2

Clock working mode Fast pull-in, locked, holdover,and free run

(1) Incoming signal jitterand wander ≥ 1.5 UI (0.02

kHz - 2.4 kHz)

(2) Outgoing signal jitterand wander ≤ 1.5 UI (0.02

kHz - 10 kHz)

Clock synchronization linkinterface

≤0.2 UI (18 kHz - 100 kHz



Note:

� Each clock board supports seven channels of clock signal in-puts, including four channels of equipment room clock signals(2 MHz or 2 Mbit), two channels of line clock signals (8 KHz,available from the Iu interface), and one channel of GPS clocksignals. In practice, one of these seven channels of clock signalinputs is set to be the active clock source through software con-figuration. The remaining six serve as standby clock sources.

� When these seven clock sources are all lost, the clock boardcan work at the free oscillation status and provide a clock forthe RNC.

� A clock source obtained, or a clock source generated by freeoscillation, can be used by Node Bs.

ZXWR RNC ReliabilityIndicesThe reliability indices of ZXWR RNC are shown in Table 5.

TABLE 5 RELIABILITY INDICES


Mean time between failures(MTBF) (h)

≥ 240,000 hours

Mean time to repair (MTTR) (h) 0.5 hour

Availability (A) ≥ 99.999792%

Downtime (DT) (m/year) ≤1.09 minutes/year

ZXWR RNC EMC IndicesThe electromagnetic compatibility (EMC) indices of ZXWR RNC areshown in Table 6.


Chapter 2 Indices

TABLE 6 EMC INDICES


Antistatic protection Contact discharge protection:±6000 V; air discharge protection:±8000 V; both meeting antistatic

protection requirements

Anti-surge relative to the ground Anti-surge voltage of thepower supply relative to the

ground: ±2000 V

ZXWR RNC Dimensions andWeightThe dimensions and weight of ZXWR RNC are shown in Table 7.

TABLE 7 DIMENSIONS AND WEIGHT


Cabinet dimensions (H × W × D) 2000 mm × 600 mm × 800 mm

Cabinet footprint 0.84 m2/Cabinet

Cabinet weight 350 Kg/Cabinet

Floor requirement for bearinga cabinet

>450 Kg/m2

ZXWR RNC Power SupplyRequirementsThe power supply requirements of ZXWR RNC are shown in Table8.

TABLE 8 POWER SUPPLY REQUIREMENTS


Power input -48 V DC

Acceptable voltage range -57 V DC – -40 V DC

Maximum cabinet powerconsumption

3700 W/Cabinet



ZXWR RNC EnvironmentalRequirementsThe environmental requirements of ZXWR RNC are shown in Table9.

TABLE 9 ENVIRONMENTAL REQUIREMENTS


Long-term operation:0 ℃ - +45 ℃

Temperature

Short-term operation:-5 ℃ - +50 ℃

Long-term operation:5 % - 85 %

Humidity

Short-term operation:5 % - 90 %

Overall noise The overall noise levelof the equipment in itsfull power output at anambient temperatureof 43 ℃ ± 2 ℃ is nohigher than 6.5 Bel.

Operation

Atmospheric pressure 70 kPa - 106 kPa

Temperature -45 ℃ - 70 ℃;indoor packed storage

required

Storage

Humidity 10 % - 90 %;indoor packed storage

required

Transportation Under 2K4P/2B2/2C3/2S3/2M3 conditions,the transportationshall not last morethan 30 consecutivedays, with the pack-ing box being intact

Mechanical vibration ETSI 300019-1-4ClassM4.1

ZXWR RNC SafetyProtection Instructions1. Optical Protection


Chapter 2 Indices

The design and selection of the optical interface comply withBS EN 60825-2-2000.

2. Rack Stability

The rack is structurally symmetrical. Its center of gravity is aslow as possible to improve the overall stability on the premisethat performance indices and heat dissipation design require-ments are met. In normal use, the rack will not turn over whenbeing placed on a tilting platform with a gradient of up to 10degrees. The enclosure is capable of withstanding strong ex-ternal shocks. The cabinet, shelf, and cabinet enclosure aresecurely tightened.

3. Rack Protection Class

The protection class is IP20. (The number “2” means prevent-ing solid objects larger than 12 mm in diameter (for example,fingers) from entering the rack; the number “0” means provid-ing no water protection).

4. Ball Test

A ball test should be made as follows to the whole enclosure,or the largest possible unreinforced part, of the equipment.First, let a 500 g steel ball fall freely from 1.3 m above tohit the surface of the equipment. No obvious dent should beresulted in. Second, attach a 1.3 m string to the steel ball,and then let the ball fall freely like a pendulum swing to hit theside of the equipment. No danger should be resulted in. Theequipment should be deemed to pass the ball test as long asthe resulting surface damages, cracks, dents, and defects (ifany) do not seriously affect the safety and water resistance andthe equipment can still provide the required dielectric strength.

5. Lightning Protection

The system is equipped with lightning protection devices. Theworking ground and the protective ground are reliable and thegrounding resistance of the protective ground is less than 1ohm. The protective grounding terminal is corrosion-resis-tant. The insulation layer of the grounding conductor is yel-low-green. Toothed washers are used for the screw-connectedprotective ground and enclosure (or PCB) to ensure the relia-bility and stability of the protective ground.

6. Leakage Current

The leakage current of the equipment is not more than 3.5 mA.

7. Safety Marks

There are long-lasting, legible marks and labels on the equip-ment to make sure that boards are inserted and cables areconnected correctly. All indicators, switches, and buttons onthe equipment have different colors, which have their respec-tive meanings in practice.

8. Heat Resistance and Fire Retardance

The enclosure of the equipment is heat-resistant and fire-re-tardant. All compartments are fire-proof, explosion-proof, andfire-retardant. All parts are made of fire-retardant materials.All materials and components have a flammability class of V-2or HF-2 above.

9. Input Current



Under the rated input voltage, the input current is not higherthan 110% rated current.

10.Abnormalities

No danger will arise from such abnormalities as RNC over-load, output short circuit, inversely-connected power supply,fan lock, or from man-made mistakes caused by operationsagainst procedures.

11.Communication Network Isolation from the Ground

An insulation against ground of 1000 V AC (without breakdown)is provided between the lines connected to the telecommunica-tion network and the grounded parts, or between these lines,to ensure that the components correctly bridged to the insula-tors will not be damaged.

12. Permanent Dielectric Strength for Network Overvoltage Protec-tion

The TNV-1 circuit, whether accessible or not, meet the per-manent dieletric strength requirement for network overvoltageprotection.

13.Safety-Related Devices

All RNC devices relating to safety are certified.

14. Earthquake Resistance

The RNC equipment can withstand 7.0 magnitude earthquakes.


C h a p t e r 3

Services and Functions

Table of ContentsFunctions .........................................................................15Services ...........................................................................15Interface Signaling Processing.............................................16Radio Resource Management...............................................18User Data Transmission ......................................................23

FunctionsZXWR RNC implements the following functions:

� Services

� Interface signaling processing

� Radio resource management

� User data transmission.

ServicesBesides implementing the basic telecom services, ZXWR RNC pro-vides the service of positioning, R99, HSDPA, HSUPA, HSPA+ andMBMS.

Positioning Function

ZXWR RNC provides three positioning methods: CellID, Cel-lID+RTT, and AGPS, to determine the current location of UE.AGPS supports two working modes: UEB (the mobile console asthe master) and UEA (the mobile console as the standby).



HSDPA Function

HSDPA supports the background, interactive and streaming ser-vices. The cell downlink peak rate reaches 7.2 Mbps.

HSUPA Function

ZXWR RNC contains HSUPA basic services and HSUPA mobility.The cell uplink peak rate reaches 5.76 Mbps.

HSPA+ Function

HSPA+ is the bridge for the smooth transition from UMTS versionto LTE.

With HSPA+ technology, the following services are enhanced:

� Supporting higher rate PS service. The peak downlink rate ofthe cell reaches 21.6 Mbps. The peak uplink rate of the cellreaches 11.52 Mbps.

� Reducing the previous channel overhead when implementingVoIP

� Making it possible for the user to be always online, implement-ing IM type communication and VoIP communication services.

MBMS Function

ZXWR RNC supports the broadcasting and the multicasting. Themulticasting supports the counting, PtP (Point-to-Point), PtM(Point-to-Multiple), and mobility management. In addition, ZXWRRNC supports the streaming and background MBMS services.

Interface SignalingProcessingThe interface signaling processing includes the control plane pro-cessing of each interface.

� Allocation and release of the radio access loading

� Security mode control

� Node B logic operation and maintenance


Chapter 3 Services and Functions

� Synchronization

� NAS message forwarding

� System message broadcast

� Paging.

Allocation and Release of RadioAccess Loading Function

During the call connection setup, ZXWR RNC allocates the radiochannel resource and the terrestrial bearer resources accordingto the QoS requirements of the radio access bearer. In addition,ZXWR RNC releases the resource after the use, sets up and re-leases the signaling connection at the radio access side.

Node B Logic Operation andMaintenance Function

This function provides the logic operation and maintenance of NodeB radio network resource, including the cell and common channelconfigurations, logic resource blocking/unblocking of the equip-ment running, the consistence with Node B checking configura-tions.

Security Mode Control Function

Security mode control function includes the radio channel encryp-tion, decryption, and integrity protection.

� The radio channel encryption and decryption are to protect theuser data information that is transmitted in the air, to preventthe message from being obtained by the unauthorized thirdparty. The encryption and decryption are based on the infor-mation and key related to the session and the related encryp-tion algorithm. The encryption algorithm uses F8 and KASUMIaccording to 3GPP.

� Integrity protection is to protect the signalling that is trans-mitted in the air, to prevent the third party from obtaining theillegal advantages with the disguised UE or network device.The integrity protection is based on the information and keyrelated to the session and the related encryption algorithm.The encryption algorithm uses F9 and KASUMI according to3GPP.



Synchronization Function

The synchronization function in UTRAN includes the networksynchronization, node synchronization, transmission channelsynchronization, and the radio interface synchronization.

NAS Message Forwarding Function

ZXWR RNC forwards the NAS (GMM, MM, CC) messages betweenUE and CN. When the massages are forwarded on the uplink,ZXWR RNC decides which CN to forward according to the CN do-main ID in the message.

System Message Broadcast Function

The system message broadcast function is to directly provide UEwith the access layer and non access layer information that is re-quired to obtain UMTS services.

Paging Function

The paging function enables the UE to receive the note of beingcalled in different statuses, to connecting with the network finally.

Radio ResourceManagementThe RRM function manages the allocation and usage of air interfaceresources, ensures the QoS of the system, obtains the plannedcoverage, and increases system capacity.

The RRM function includes radio measurement, AC (AdmissionControl), LC (Load Control), PC (Power Control), HC (HandoverControl), DRBC, congestion control, code resource management,and load balancing.

Radio Measurement Function

The radio measurement function is designed to measure the qual-ity of the radio channel, including the receiving signal strength of



the serving cell and its adjacent cells, the error bit rate of the serv-ing cell and its adjacent cells, the receiving interference level, andthe total DL transmitting power and range, Doppler offset, andsynchronization status of each cell. Measurement results are usedfor the handover judgment, admission control, and load control.

AC Function

The admission control (AC) function is designed to:

� Admit new services as many as possible to make the most ofsystem resources and ensure the QoS when there are enoughresources; and

� Reject new service requests to avoid system overloading andkeep system stability when the requested resources for cellservices (such as the access of new services to a cell, rateincrease of DCH PS services, FACH-DCH service switchover,and DCH-HSPA switchover) exceed the available resources.

The service requests include RRC connection setup, RAB setup,RAB modification, SRNC relocation, Iur-interface handover, intra-RNC handover, and dynamic channel allocation. After the RNC re-ceives any of these services, it will select the transport channelaccording to service attribute and equipment capability before de-ciding whether to admit the service according to the requested re-sources and the occupancy rate of the target channel in the servingcell, so that it can prevent resource shortage or cell overloading.

The RANs provided by ZTE Corporation carry out priority-basedadmission control, which enables those users and services withhigh priority to obtain more system resources and higher QoS.

LC Function

LC function is to monitor the loading of the system. When thesystem is nearly overloading or already overloaded, LC helps thesystem to come back to the stable status smoothly. When thesystem is in stable status, LC controls the services to achieve thebetter QoS services, such as, obtaining the higher rate or trans-mission reliability.

PC Function

The power control (PC) function includes the DL open loop powercontrol, power balance, UL outer loop power control, UL open looppower control.

� DL open loop PC is that ZXWR RNC sets the initial transmissionpower for the BTS DL channel according to the UE DL measure-ment report.



� Power balance is that ZXWR RNC balances the transmissionpower of several DL radio links when realizing the balancingmacro diversity. Power balance helps to eliminate power float-ing.

� UL outer loop PC is that ZXWR RNC sets the quality targetvalue for Node B UL inner loop PC by monitoring the differencebetween the actual quality in the transmission channel and thefluttering on QoS. UL outer loop PC helps to control the UL radiochannel quality.

� UL open loop PC is that, in the case of random access, ZXWRRNC sets the initial transmission power for UE according to theUE measurement report.

� DL outer loop PC is that UE sets the quality target value forits DL inner loop PC by monitoring the difference between theactual quality in the transmission channel and the fluttering onQoS. ZXWR RNC sets some parameters used in DL outer loopPC.

HC Function

The handover control (HC) function is to manage the mobility onradio interfaces. It is based on radio measurement, ensuring theQoS of the CN. It includes the following types.

� Intra-RNC soft handover

The intra-RNC soft handover refers to the soft handover be-tween Node Bs under the same RNC.

� Intra-RNC softer handover

The intra-RNC softer handover refers to the handover betweenmultiple cells under the same Node B. Those cells that arelinked with the same UE at the same time form a macro di-versity.

� Inter-RNC soft handover

The inter-RNC soft handover refers to the soft handover be-tween sectors with the same frequency under different basestations, or between Node Bs under different RNCs. The softhandover between RNCs can only be achieved through the Iurinterface.

� Intra-RNC hard handover

The intra-RNC hard handover refers to the hard handover be-tween Node Bs under the same RNC.

� Inter-RNC hard handover

The inter-RNC hard handover refers to the hard handover be-tween Node Bs under different RNCs.

� Reverse handover

The reverse handover refers to the handover controlled by theUE in the case of configuration failure and harsh radio envi-ronment, such as CELL UPDATE and URA UPDATE. It includesintra-RNC reverse handover and inter-RNC reverse handover.



� SRNS re-positioning

The SRNS re-positioning refers to the transfer of the Iu-inter-face connection from the SRNC to the DRNC after all radio linksare transferred to the DRNC.

� Inter-system handover

The inter-system handover refers to the mobility managementof the UE from a radio access system to another, that is, fromthe UTRAN access system to the GERAN system. For this func-tion, the UE must support WCDMA and GSM, and the GSMsystem must provide the corresponding functions to supportinter-system handover.

� Change of HSDPA and HSUPA serving cell

There is only one serving cell when HSDPA or HSUPA is used.In intra-system soft handover, if there is any HS-PDSCH be-fore and after the handover when the best cell changes, theHS-PDSCH serving cell will change. In hard handover, if thereis any HS-PDSCH before and after the handover, the HS-PDSCHserving cell must change.

DRBC Function

The DRBC function helps ZXWR RNC to allocate the resources rea-sonably according to users’ requirements and the occupancy ofsystem resources during system operation to make full use of thebandwidth.

The DRBC module dynamically adjusts the bearer channel andreal-time rate of PS and CS services, maximizes the use of systemradio resources, and ensures system stability and QoS.

The DRBC includes:

� Initial channel allocation, which refers to the channel allocationand rate configuration according to the service requirementand system status when a channel is initially established. Itincludes the channel allocations for signaling, initial services,and concurrent services.

� Channel transfer, which refers to configuring proper transportchannels according to the actual rate of PS services. If therate of PS services changes, the channel will also change. Inthe rate monitoring of PS services, when the bandwidth occu-pied by the data traffic of a UE is lower than the bandwidthallocated to the UE by the system, the system will reduce theallocated bandwidth to spare more resources; when the band-width occupied by the data traffic of the UE is nearly reachits allocated bandwidth, the system will increase the allocatedbandwidth to avoid affecting the services of the UE. During con-versations, the DRBC function will make real-time bandwidthadjustments and inter-channel handovers according to mea-surement results. Conversational CS services use downlinkDCHs and uplink DCHs. Streaming services use DCHs. Inter-active and background services use FACHs and DCHs. Channeltransfers from PCH to DCH are not supported, but status trans-fers between PCH, FACH and DCH are supported.



Congestion Control Function

The congestion control function can re-allocate the radio resourcesof the system and take a string of control measures based on ser-vice attributes to relieve the congestion in the system, increase callcompletion rate, and reasonably use system resources for servicesof different priorities.

When the uplink or downlink loads approach or exceed the admis-sion control threshold, new service requests cannot access the sys-tem due to resource shortage. This results in congestions, whichneed the RNC to carry out congestion control. These service re-quests include RAB setup, RAB modification or negotiation/re-ne-gotiation, SRNC incoming relocation, cross-Iur interface RL setup,intra-RNC handover (incoming handover), incoming inter-systemhandover, inter-frequency handover (incoming handover), inter-RNC soft handover (incoming handover), two times of RAB setupsfor the same user, and service rate increase triggered by dynamicradio bearer adjustment.

When a congestion occurs in the system, the resource preemptionfunction can be activated to differentiate high-priority users andincrease call completion rate. This function includes the followingtwo aspects:

� Forced release, which means that high-priority services canrelease low-priority services by force and preempt the re-sources of low-priority users to differentiate services amongthese users.

� Rate reduction, which means reducing the data rate of the on-line users to increase call completion rate.

Code Resource Control Function

The code resource control function refers to dynamically allocatingdownlink channelized codes to cells according to a certain standardto make the most of code resources and improve system capacity.

During service setups, the RNC calculates the SF based on the ser-vice rate and allocates channelized codes accordingly. After a ser-vice is released, the corresponding channelized code should alsobe released and allocated to other users. For every cell, the RNCmaintains a channelized code table that records the status of eachcode, such as idle, allocated, or shielded. When code resourcesare allocated, the shielding of idle code resource blocks in codeallocation should be minimized.

When HSDPA and R99 services use the same carrier frequency,the traffic of HSDPA services in each cell is affected by the numberof HS-PDSCHs, namely, the number of codes that are allocatedto the HS-PDSCH and whose SF is 16. ZTE RNC can staticallyor dynamically allocate the number of HS-PDSCHs. The dynamicallocation can reflect the change of system loads more flexibly andquickly.



Load Balancing Function

Load balancing includes intra-system load balancing (load-basedand service-based inter-operations between multiple carrier fre-quencies) and inter-system load balancing. It helps to effectivelyuse system resources and improve system capacity and QoS byreasonably distributing traffic among cells according to intra-cellloads and inter-cell adjacent relations.

The preferred frequency selection function decides whether to sup-port HSDPA or HSUPA for all cells, and decides to preferably acceptspeech services, data services, or all services. During RRC con-nection setups, RAB assignments, handovers, cell re-selections,and channel transfers, the RNC will select a proper cell as the tar-get cell for access or handover according to the service type andUE capacity.

Through the RNC, users can set various attributes to different cells,for example, setting some cells to only support HSDPA servicesinstead of R99 services; that is, only HS-DSCH-borne services,instead of DCH-borne services, can be used.

With the HSUPA capability, the RNC supports the load balancing ofHSUPA services between multiple carrier frequencies in the UMTSnetwork or between the UMTS and the GSM.

User Data TransmissionThe user data transmission includes the signaling data trans-mission and the user data transmission, implementing theIUUP/RLC/MAC/FP processing. ZXWR RNC contains the functionsof the data encryption, Mac-C and Mac-hs streaming control.ZXWR RNC provides the end-to-end data transmission for users.





C h a p t e r 4

Compositions

Table of ContentsLogic Compositions ............................................................25Hardware Compositions......................................................27Software Compositions.......................................................44

Logic CompositionsLogic Structure

The logic structure of ZXWR RNC is as shown in Figure 4.

FIGURE 4 ZXWR RNC LOGIC STRUCTURE

Logic Unit Allocation of ZXWR RNCSystem

Functionally, ZXWR RNC falls into six parts: access unit, switchunit, processing unit, operating & maintenance (O & M) unit, pe-ripheral monitor unit, and OMM. The detailed board allocation isshown in Figure 5.



FIGURE 5 SYSTEM LOGIC UNIT ALLOCATION

ZXWR RNC Logic Unit Description

Logically, except OMM, ZXWR RNC falls into five functional units,whose functions are described in Table 10.


Chapter 4 Compositions

TABLE 10 LOGIC UNIT DESCRIPTION

Logic Unit Function

ROMUProviding global control, O & M,global clock, and GPS for theZXWR RNC system

RAU

Providing STM-1, E1, T1, CSTM-1,and IP access for the Iu, Iub andIur interfaces of the ZXWR RNCsystem

RPUProcessing upper-layer protocolsat the control plane and the userplane of the ZXWR RNC system

RSU

Providing a large-capacity andnon-blocking switching unit forZXWR RNC control management,communication between serviceprocessing boards, and serviceflow connection among RAUs.

RPMU

Detecting the cabinet power sup-ply and the environment of ZXWRRNC, giving alarms, and detectingand control cabinet fans

Hardware CompositionsZXWR RNC Shelves

By function, ZXWR RNC shelves fall into control shelf, switchingshelf, resource shelf (Gigabit resource shelf), and interface shelf(Gigabit interface shelf). With difference configurations, theseshelves can form ZXWR RNC systems with different performances.

The types and functions of these shelves are described in Table 11.



TABLE 11 ZXWR RNC SHELVES

Shelf Type Function

Control shelfProcessing control-plane signals;providing O & M and clock-relatedfunctions

Switching shelf

Providing the level-1 IP switchingplatform of the system for the in-terconnection between resourceshelf and interface shelf and theuser-plane expansion between re-source shelves

Gigabit resource shelfproviding the user-plane process-ing pool and IP-based Ethernet ac-cess of Iu, Iur, and Iub interfaces

Gigabit interface shelf

Only being used for Iub inter-face access; providing ATM- andIP-based (low-rate IP interface)Iub interface access



ZXWR RNC Boards

ZXWR RNC boards are described in Table 12.

TABLE 12 ZXWR RNC BOARDS

Logic Unit

FunctionalName (FrontBoard/RearBoard)

Full Name ofFunctionalBoard

PCB Name

Functionsof Front

Boards (RearBoards Provide

ExternalInterfaces forFront Boards)

ROMB/RMPBRNC Operating& MaintenanceBoard

MPX86 &MPX86/2

Processing theglobal processand controllingthe O & M ofthe whole sys-tem (includingO & M agent);connecting withOMC-R through100 M Ethernet;separating inter-nal and exter-nal network sec-tions; serving asthe core of theO & M of ZXWRRNC; monitor-ing and manag-ing boards in thesystem directlyor indirectly; andproviding Ether-net interface andRS-485 interfaceto manage theconfiguration ofall boards andother compo-nents in the sys-tem

CLKG/RCKG1 &RCKG2 Clock Generator ICM

Providing andexternally syn-chronizing theclock for the sys-tem; extractingthe clock refer-ence through theIu interface anddriving multi-ple channels oftiming referencesignals for in-terface shelvesafter synchro-nizing the clock;and supportingother externalreferences, such

ROMU



Logic Unit



PCB Name

Functionsof Front


ExternalInterfaces forFront Boards)as GPS, 2Mbits,and 2MHz

ICM/RCKG1 &RCKG2

Integrated ClockModule ICM

Receiving sys-tem clock andGPS signals andsupporting GPSreference clock

ICMG/RCKG1 &RCKG2

Integrated ClockModule (GPS) ICM

Receiving systemclock and GPSsignals and sup-porting AGPS po-sitioning

SBCX/RSVB X86 Single BoardComputer SBCX

The SBCXprovides thefollowingfunctions:

� Storing logs;� Storing

performancedata; and

� Serving asan OMMserver.

RCBRNC Controlplane processingBoard

MPX86 &MPX86/2

Processing con-trol-plane proto-cols at Iu, Iub,and Iur interfa-ces

RPU

RUB RNC User planeprocessing Board VTCD & VTCD/2

Processing FP/M-AC/RLC/UP for C-S-domain servic-es and FP/MAC-/RLC/PDCP for P-S-domain servic-es

APBE/RGIM1 ATM ProcessBoard Enhanced APBE & APBE/2

Providing fourSTM-1 interfa-ces; supportinga traffic of 622M;and terminatingAAL2 and AAL5of the ZXWR RNCsystem

APBI/RGIM1 ATM ProcessBoard with IMA

APBE/2 Providing fourexternal STM-1interfaces;supporting atraffic of 622M;terminating AAL2and AAL5 ofthe ZXWR RNC

RAU



Logic Unit



PCB Name

Functionsof Front



system; andsupporting 64E1s and 31 IMAgroups at mostand working withDTB and SDTB toprocess IMA atE1 and CSTM-1interfaces

GIPI Gigabit IPInterface

MNIC/2 Providing one1 G or fourFE Ethernetelectricalinterfacesexternally andproviding oneGE and fourFE Ethernetelectricalinterfacesinternally

DTB/RDTB Digital TrunkBoard

DTEC Providing 32 E1interfaces, E1cable interfacefor the ZXWRRNC system andworking withAPBI or IMAB

� One APBIand twoDTBs worktogetherto providecompleteE1 accessand ATMtermination.

� One IMABand twoDTBs worktogetherto providecompleteE1 accessand ATMtermination.

EIPI E1 IP Interface MNIC/2 ProvidingE1-based IPaccess (workingwith DTB orSDTB2 becauseEIPI itself hasno externalinterface)



Logic Unit



PCB Name

Functionsof Front



� One EIPIand twoDTBs worktogetherto provide64-126 E1interfaces atmost.

� One EIPIand oneSDTB2 worktogetherto providetwo CSTM-1interface.

IMAB IMA Board IMAB Working withDTB/SDTB2 toprovide completeE1 access andATM termination.Each IMABsupports 30IMA groups.Each IMA groupsupports 32 E1links at most.

� One IMABand twoDTBs forma group.

� Two IMABsand oneSDTB2 forma group.

SDTA Sonet DigitalTrunk Board ATMversion

DTA Providingtwo CSTM-1interfaces;supporting 126channels ofE1s; processingIMA and ATM;and providingCSTM-1 accessand ATMterminationwithout workingwith APBI

SDTB2 Sonet DigitalTrunk Board 2

SDTB/2 Providingtwo CSTM-1interfaces;supporting 126channels ofE1s. Two APBIsand one SDTBform a group to



Logic Unit



PCB Name

Functionsof Front


ExternalInterfaces forFront Boards)provide CSTM-1access and ATMtermination.

GIPI3 Gigabit IP Inter-face 3 MNIC/3

Providing two GEelectrical interfa-ces both exter-nally and inter-nally

DTA/RDTADigital TrunkBoard ATM ver-sion

DTA

Providing 32 E1/T1 interfaces;supporting 60IMA groups; andproviding ATME1/T1 access andATM termination

DTI Digital TrunkBoard IP version DTI

Providing 32 E1/T1 interfaces atmost and proce-ssing HDLC/PPP-/MLPPP

POSI/RGIM1 POS InterfaceBoard MNIC/2

Providing twoSTM-1/OC-3-based POS in-terfaces or oneOC-12-basedPOS interface

SDTISonet DigitalTrunk Board IPversion

DTI

Supporting twoCSTM-1 interfa-ces and process-ing HDLC/PPP/M-LPPP

SDTA2Sonet DigitalTrunk Board ATMversion 2

DTA

Providing fourCSTM-1 interfa-ces; supporting252 channels ofE1s; and pro-cessing IMA andATM



Logic Unit



PCB Name

Functionsof Front



UIMC/RUIM2 &RUIM3

Universal Inter-face Module ofBCTC

UIM/2

providing switch-ing platforms forcontrol shelvesand switchingshelves

THUB/RCHB1 &RCHB2

Control PlaneHUB THUB

Converging theEthernet data atthe control plane

PSN Packet SwitchNetwork PSN4V/2

Performinglarge-capacitycore switching

GLI Gigabit Line In-terface GLIQV/2

Serving as theline interfaceboard at theGE interface toprovide inter-faces betweenthe switchingshelf and all re-source shelves;performing suchfunctions asphysical layeradaptation, IPpacket tablechecking, seg-mentation, for-warding, andtraffic manage-ment

RSU

GUIM/RGUM1 &RGUM2

GE Universal In-terface Module GUIM

� Providing16 K circuitswitchingfor the Gigaresourceshelf andprovidingswitchingHUBs toperformcontrol-planeswitchingand user-planeswitching

� Driving theclock in theresourceshelf;inputting 8K and 16M signals;



Logic Unit



PCB Name

Functionsof Front


ExternalInterfaces forFront Boards)distributingsuch signalsto all slots inthe resourceshelf afterphase-lockand driving;and provides16 M and 8K clocks tothe boards inthe resourceshelf

PWRD Power Distribu-tion Board PWRDB

Collecting infor-mation aboutperipheral andenvironmentboards in thecabinet, includ-ing power dis-tributor andfan status, airswitch status,and such envi-ronment alarmsas tempera-ture, humidity,smoke, water-logging, and in-frared; and beingmonitored andmanaged by theROMB throughthe RS-485 bus

PEMBPower & Envi-ronment MonitorBackboard

PEMB

The PEMB isin the set-toppower distribu-tion subrack,serving as atransit board forthe outgoing ca-bles of the PWRDand monitoringother racks andfan subracks.

FBC Fan Box Connect FBC

Being used bysub-fan modulesof fan subracksto collect alarmsfrom these sub-fan modules

FCB Fan ControlBoard FCB

Being used byfan subracks toprovide physi-

RPMU



Logic Unit



PCB Name

Functionsof Front


ExternalInterfaces forFront Boards)cal support andpower supply forsub-fan modulesand provide in-terfaces for thecables connectedto the PEMB

PWRDL PWRD FAN LED PWRDL

Providing frontpanel indicatorsfor the sub-fanmodules of fansubracks

ALB Alarm Box ALB

The alarm boxis outside of therack. It com-municates withOMC-R throughEthernet andgives differentlevels of alarmsaccording to thefailures arising inthe system forthe convenienceof timely inter-ference and han-dling.

BCTC Backplane ofConTrol Center BCTC

Serving as thebackplane of thecontrol shelf

BPSNBackplane ofPacket SwitchNetwork

BPSNServing as thebackplane of theswitching shelf

Backplane

BGSNBackplane OfGiga UniversalService Network

BGSN

Serving as thebackplane of theGiga resourceshelf

Serving as thebackplane of theGiga interfaceshelf



ZXWR RNC Cables

The cables used in ZXWR RNC include clock cable, Ethernet cable,E1/T1 cable, monitoring cable, and optical connector, as describedin Table 13.


ZXWRRNCSystem

Descrip

tion

TABLE 13 ZXWR RNC CABLES

Type Name S.N. Model Terminal End A End B Application

Line clock cable H-CLK-004 4-core singleround cable RJ45®RJ45

Connecting tothe end witha silk screenmark “8KOUT/DEBUG-232” onthe RGIM1 orthe RDTB

Connecting tothe end witha silk screenmark “8KIN1”or “8KIN2” onthe RCKG1/2

It is usedto input linereference clockto CLKG, ICMG,and ICM boards.

BITS clock cable(120 Ω) H-CLK-005 2 × 4-core 120

Ω PCM cableAir connec-

tion®DB9 (pin)

Connectingwith the BITSclock resourceof the office,with terminalsbeing used asrequired

Connecting tothe end with asilk screen mark“2MBps/ 2MHz”on the RCKG1/2

It is used toinput externalBITS clockreference toCLKG, ICMG,and ICM boards.

BITS clock cable(75 Ω) H-CLK-006

4 × 1-core 75 Ωmicro coaxial

cable

Air connec-tion®DB9 (pin)

Connectingwith the BITSclock resourceof the office,with terminalsbeing used asrequired

Connecting tothe end with asilk screen mark“2MBps/ 2MHz”on the RCKG1/2

It is used toinput externalBITS clockreference toCLKG, ICMG,and ICM boards.

Clock cable

System clockdistributioncable

H-CLK-0036 × 8-coresingle round

cable

DB44 (pin)®6×DB9 (pin)

Connecting toany one endwith a silkscreen mark“CLKGOUT” onthe RCKG1/2

Connecting tothe end witha silk mark“CLKGIN” onthe RUIM2/3

It is used todistribute thesystem clockfrom CLKG,

ICMG, and ICMboards to allshelves.

38

Confidential

andPro

prietary

Informatio

nofZTECORPORATION

Chapter

4Compositio

ns


THUB cable H-ETH-008 8 × category- 5shielded cable

DB44(pin)®RJ45

Connectingto any oneend with asilk screenmark “FE1-8”,“FE9-16”,“FE17-24”,“FE25-32”,“FE33-40”, or“FE41-46” onthe RCHB1/2

panel

Connecting tothe end with asilk screen mark“FEn” (n=1~6)on the RUIM2/3

It is used toconnect theTHUB and theUIMC in thelocal shelf.

Connecting tothe end witha silk screen“FE1” on theRMNIC panel

Connecting withthe RSVB (rearboard of theSBCX) witha silk screenmark “OMC2”

It is used asa cable forthe Node Boperation andmaintenancecenter.

Connecting tothe end with asilk screen mark“OMC1” on theRSVB panel

Connecting theHUB to theNetNumen NM

server

It is usedas a cablefor the RNCoperation andmaintenancecenter.

Connecting tothe end with asilk screen mark“OMP1” on theRSVB panel

Connecting theHUB to the localNM server

It is used as aLMT network

cable.

Connecting tothe end with asilk screen mark“PD485” on theRMPB panel

Connecting tothe end witha silk screenmark “RS485”on the PEMB

It is used asa monitoringcable ofthe powerdistributionsubrack.

Ethernet cable

Shieldedstraight-

through cableH-ETH-009 Category- 5

shielded cable RJ45®RJ45

Confidential

andPro

prietary

Informatio

nofZTECORPORATION

39

ZXWRRNCSystem

Descrip

tion


Connecting tothe end with asilk screen mark“RS485” on theback panel ofthe fan subrack

FANBO X1:connecting tothe set-top fan

group;

FANBO X2:connecting tothe first-layerfan subrack;

FANBO X3:connecting tothe second-layer fan

subrack;

FANBO X4:connecting tothe third-layerfan subrack.

It is used asa monitoringcable of the fan

subrack.

External E1cable (75 Ω) H-E1-026

16-core 75 Ωmicro coaxialcable, with acore diameter

of 2.0

DB68 (pin)®airconnection

Connecting tothe end with asilk screen mark“T1/E1 1-16”or“T1/E1 17-32”on the RDTAand the RDTB

Connectingwith externalequipment,

with connectorsbeing mountedaccordingto field

applications.Odd-numberterminals

are used forsending; whileeven-numberterminals

are used forreceiving.

It is used toconnect withexternal E1transmissionequipment.

External E1cable (120 Ω) H-E1-015 32-core 120 Ω

PCM cableDB68 (pin)®airconnection

Connecting tothe end with asilk screen mark“T1/E1 1-16” or“T1/E1 17-32”


with connectorsbeing mounted

It is used toconnect withexternal E1

E1/T1 cable

40

Confidential

andPro

prietary

Informatio

nofZTECORPORATION

Chapter

4Compositio

ns


on the RDTAand the RDTB

accordingto field




transmissionequipment.

External T1cable (100 Ω,unshielded)

H-T1-00150-core

category- 5cable


Connecting tothe end with asilk screen mark“T1/E1 1-16” or“T1/E1 17-32”on the RDTAand the RDTB






It is used toconnect withexternal T1transmissionequipment.

External T1cable (100 Ω,shielded)

H-T1-0026 × Shieldedcategory- 5

cable


Connecting tothe end with asilk screen mark“T1/E1 1-16” or“T1/E1 17-32”on the RDTAand the RDTB




are used for

It is used toconnect withexternal T1transmissionequipment.

Confidential

andPro

prietary

Informatio

nofZTECORPORATION

41

ZXWRRNCSystem

Descrip

tion


sending; whileeven-numberterminals


Environmentmonitor adaptor

cableH-MON-009

2/4/8- coresingle round

cable

DB25(pin)®5×DB9

(hole)

Connecting tothe end with asilk screen mark“SENSORS” onthe back planeof the powerdistributionsubrack

Connecting toH-MON-010,H-MON-011,H-MON-012,H-MON-013,

H-MON-014 andthe backupcable.

It is usedto connectthe powerdistributionsubrack withaccess controlcables andsensor cables.

Front/ Reardoor accesscontrol cable

H-MON-010 2-core singleround cable

DB9(pin)®2×airconnection

H-MON-009

Connecting tothe front/reardoor statusswitches ofthe rack

It is used toconnect thefront/rear dooraccess controlsensors withthe monitoring

cable.

Machine roomaccess controlsensor cable

H-MON-011 2-core singleround cable

DB9(pin)®4×airconnection

H-MON-009

Connecting tothe door statusswitch of theequipmentroom

It is used toconnect themachine roomaccess controlsensor withthe monitoring

cable.

Infrared sensorcable H-MON-012 4-core single

round cable

DB9(pin)®infrared

sensorH-MON-009

It is usedto connectthe infraredsensor withthe monitoring

cable.

Monitoringcable

42

Confidential

andPro

prietary

Informatio

nofZTECORPORATION

Chapter

4Compositio

ns


Smoke sensorcable H-MON-013 2-core single

round cable

DB9(pin)®smoke

sensorH-MON-009

It is usedto connectthe smokesensor withthe monitoring

cable.

H/T sensorcable H-MON-014 4-core single

round cableDB9 (pin)®DB9

(hole) H-MON-009

Connecting tothe temperatureand humiditysensors

It is used toconnect thetemperatureand humiditysensors withthe monitoring

cable.

Opticalconnector

Single-modefiber optics

Single-modefiber optics Single-mode LC/PC®LC/PC

Connectingto the opticalinterface on theinterface board

Connecting toexternal NEs

It is usedto connectthe interfaceboard to

external opticaltransmissionequipment.

Confidential

andPro

prietary

Informatio

nofZTECORPORATION

43


Note:

See ZXWR RNC (V3.09.30) Radio Network Controller Hardware De-scription for the appearance and connection modes of these cables.

Software CompositionsOverall Structure of ZXWR RNCSoftware System

Overall structure of ZXWR RNC software system is as shown inFigure 6.



FIGURE 6 OVERALL STRUCTURE OF ZXWR RNC SOFTWARE SYSTEM

Subsystems

ZXWR RNC software susbsystems are as shown in Table 14.

TABLE 14 ZXWR RNC SOFTWARE SUBSYSTEM

SoftwareSubsystem

Home Logic Unit Function

OMM Operation andMaintenance Unit

Implementingall managementfunctions onthe system byinterconnecting withRMS, including ZXWRRNC configurations,performance



SoftwareSubsystem


management, andfault management.

RMS ROMU

Implementing allmanagement of NM(OMM) on the systemby interconnectingwith OMCR, includingthe configurationmanagement,performancemanagement andalarm management,etc.

DBS ROMU

Proving the queryand trigger of theconfiguration data forother subsystems.

RNLC RPU

Implementing radioapplication controlplane protocol, withthe characteristics ofcomplicated flow anddecision algorithm.

RNLU RPU

Implementing radioapplication userplane protocol withDSP core, with thecharacteristics ofsimple flow and largealgorithm capacity,and implementingradio user planeprotocol (FP, RLC,MAC, IUUP, PDCP)and data bearerprotocol GTP-U.

SIG RPU and RAU

Implementing ALCAPof TNL (includingA2SP, STC-NNI,STC-UNI) andSCCP, MTP3B,SAAL (SSCF-NNI,SSCF-UNI, SSCOP),which makes radionetwork layerindependent of thedifferent transmissiontechnology.

MCS RAU and RPU

ImplementingUDP, IP, IPoA,ATM adaptationlayer (AAL2, AAL5)protocol, ATM layerprotocol and internalcommunicationEthernet protocol



SoftwareSubsystem


Implementing IPapplication layerprotocols:

BRS falls into EPU andRPU:

1. EPU forwardsreports, synchronizesreceiving route, andseparates reports onthe control plane fromthe user plane, etc.BRS RAU and RPU

2. RPU is the maincontrol node of theprotocol stack. Itcontrols and managesthe protocol stackson all boards, suchas, configuringthe protocol stackdata, generatingand synchronizingthe dynamic routeprotocol and route.

OSS Lower layer support

Providing the isolationhardware, lowerlayer RTOS platformand multi-processordistributed operationplatform for othersubsystems. Itimplements theprocess scheduling,timer management,memory managementand processcommunication, etc.

SCS Lower layer support

Implementing thepower-on control ofthe whole system(including versionload), active/standbyhandover controland real-time statusdetection, etc.

GPSN Processing unit

Implementing theaccess an processingof SCS signals, andthe GPS applicationinformation requiredfor ICMG.





C h a p t e r 5

Operating Environment

Table of ContentsRNC/NM Software Overview ................................................49Software Types .................................................................50Version Software ...............................................................50Lower Layer Frozen Software ..............................................51

RNC/NM Software OverviewThe structure of ZXWR RNC and NM software is as shown in Figure7.

FIGURE 7 ZXWR RNC/NM SOFTWARE STRUCTURE

ZXWR RNC software consists of ZXWR RNC software, OMM andEMS software.

1. ZXWR RNC software

It runs on the boards of ZXWR RNC.

2. OMM

NM OMM system is in the server/client structure.

OMM server is installed and is running on the SBCX board onthe ZXWR RNC cabinet. NM server is based on Red Hat Linuxserver and Oracle database. The client is in Windows worksta-tion. The client is installed and is running on the normal PC.

OMM NMS provides NE management functions on ZXWR RNS,including the alarms, performance, and configurations.

3. EMS

EMS locates between OMM and NMS. It is an NM for the ded-icated network. It uniforms the internal dedicated network,implementing the centralized management of the internal ele-ments. Its functions include:

� Accessing dedicated network services for NMS



� Performing the centralized management for all OMM main-tenance terminals or elements in the local dedicated net-work.

ZXWR RNC (through the SBCX board) connects with OMMthrough TCP/IP, OMM connects with EMS through TCP/IP, too.

Software TypesAccording to actual application, the system software falls into twotypes:

� Version software

� Lower layer frozen software

Version SoftwareVersion Software Definition

The version software is the software whose version can be man-aged via the background, that is, the software supports dynamicupgrade.

Version Software Types andOperating Environment

All hardware boards in ZXWR RNC covers three types of the em-bedded processors.

1. Generic CPU

It deals with process type transaction.

2. DSP

It processes digital signals, mainly applicable to applicationswith intensive algorithm.

3. NP

It processes and forwards the data, mainly applicable to pro-tocols and functions related to Ethernet, ATM and IP, whichcovers data detection, data classification, data encapsulation,data encryption/decryption, protocol handover and data for-warding, etc.


Chapter 5 Operating Environment

Lower Layer FrozenSoftwareLower Layer Frozen SoftwareDefinition

The lower layer frozen software is the software that is frozen onthe chip. It is mainly related to the hardware.

Lower Layer Frozen SoftwareCompositions

The lower layer frozen software falls into three parts:

1. BSP subsystem that serves for all units (BOOTUP, versiondownload and load, hardware drive and active/standby com-petition)

2. The physical protocol implementation and monitoring softwarebelonging to RAU and RSU

3. The monitoring software belonging to RPMU.





C h a p t e r 6

Networking

Table of ContentsNM Networking Plan...........................................................53Iub,Iur Interface Networking Mode ......................................54Iub Interface Networking Mode ...........................................56Iu Interface Networking Mode .............................................58

NM Networking PlanZXWR RNC supports two types of NM: the local OMM NMS and EMSNetNumen NMS.

The NM server of the local OMM NMS is installed on the SBCXboard. To configure and manage the ZXWR RNC and Node B, theusers should connect to the NM server through the NM client onthe local ZXWR RNC.

Netnumen NMS can be installed at the local or at the remote. Whenoperating, the user can directly connect to the NetNument NMserver through the IP network on the NetNumen client no mat-ter where he is. Through the IP network, Netnumen NMS canaccess the telecommunication systems of different types, such as,WCDMA, TD-SCDMA, and GSM. Therefore, through the NetNumenNMS, users can configure and manage multiple NEs on differentnetwork systems.

Note:

It is recommended that the common user uses the NetNumen NMSand the superior user uses the OMM NMS.

At present, the common-used NM networking mode is as shown inFigure 8.



FIGURE 8 NM NETWORKING PLAN

Iub,Iur Interface NetworkingModeTransmission Networking ModeBased on ATM Switch

With the existing ATM network, the operator can access ZXWR RNCdirectly via ATM STM-1 interface, as shown in Figure 9.

FIGURE 9 ATM-BASED NETWORKING

Transmission Networking ModeBased on SDH

The networking of the narrowband E1/T1 interface, CSTM-1 inter-face, and CSTM-1 interface that the SDH transport network pro-vides is as shown in Figure 10.


Chapter 6 Networking

FIGURE 10 SDH-BASED NETWORKING

Transmission Networking ModeBased on IP

ZXWR RNC interconnects with IP backbone network via the in-terface shelf. If the IP backbone network directly provides GEhigh-speed interface, the operator can either directly access ZXWRRNC resource shelf or select other suitable access mode, as shownin Figure 11.

The VLAN technology helps to effectively isolate the broadcaststorm on Ethernet. Meanwhile, with BNAS being set on the net-work, ZXWR RNC can implement such functions as authenticationand security control.

FIGURE 11 IP-BASED NETWORKING

Hybrid Transmission Mode

By site, some sites can use IP network and others use the tra-ditional SDH transmission. By service, some circuit services useSDH network and others use IP backbone network. It is as shownin Figure 12.

FIGURE 12 HYBRID NETWORKING



Iub Interface NetworkingModeZXWR RNC supports multiple networking modes.

In terms of Iub interface networking topology, ZXWR RNC supportsstar networking, chain networking, ring networking (with the sup-port of transmission network), and hybrid networking.

Star Networking Mode

The star networking mode of ZXWR RNC is as shown in Figure 13.

In the star networking mode, ZXWR RNC connects to each NodeB directly. Node B serves as an end equipment. This networkingmode is very simple and convenient for maintenance and engi-neering services. As signals are transmitted through fewer inter-mediate links along the path, the reliability of transmission line ishigh. This networking mode is generally applicable to urban areaswith dense population.

FIGURE 13 STAR NETWORKING MODE

Chain Networking Mode

The chain networking mode of ZXWR RNC is as shown in Figure14.

FIGURE 14 CHAIN NETWORKING MODE



In the chain networking mode, signal passes through more links,so the line reliability is poor. This mode is applicable to areas withzonal distribution and sparse population. This mode is cost effec-tive and utilizes few transmission devices.

The chain networking mode is applicable to one site with multipleNodes B.

In actual application, because the sites are sparse, the transmis-sion devices are generally required between ZXWR RNC and NodesB to serve as intermediate connections. Commonly-used trans-mission media include microwave, fiber, HDSL and coaxial cable.

Ring Networking Mode

The ring networking mode of ZXWR RNC is as shown in Figure 15.

FIGURE 15 RING NETWORKING MODE

Note:

ZXWR RNC nd Node B cannot realize the ring networking modethemselves. They must depend on a transmission device for thering networking mode.

The ring networking mode involves two sets of active/standbylinks. Every node on the ring has two upper-level nodes, whichincreases the link reliability. If a site is damaged or a link fails, itslower-level node can select another link as the active link.

Hybrid Networking Mode of Star andChain

The hybrid networking mode (star and chain) of ZXWR RNC is asshown in Figure 16.



FIGURE 16 HYBRID NETWORKING MODE (STAR AND CHAIN)

The hybrid networking mode with multiple topologic structures hasfollowing advantages:

1. It is easy to suit the current networks of the carrier, so that thecarrier can make full use of the current network at the earlystage of WCDMA network construction. Carriers can save theconstruction cost, step up the construction speed, and seizegood business opportunities.

2. It supports the network construction in areas with complexlandforms. Since Nodes B of UTRAN part are widely distributedand scattered, the hybrid networking mode provides more flex-ibility to the network construction and reduces the complicacy.

3. It facilitates the form of abundant transmission routes and en-hances robust of the network.

Iu Interface NetworkingModeIu interface is between ZXWR RNC and MSC/SGSN/MGW, support-ing ATM protocol and IP. With MSTP technology, ATM VP-Ring canbe formed which can perform both the convergence and the statis-tics, which can transmit the service from ZXWR RNC to MSC/SGSNwith high efficiency. In addition, the ring protection function canenhance the transmission reliability. The Iu interface networkingmode is as shown in Figure 17.



FIGURE 17 IU INTERFACE NETWORKING





C h a p t e r 7

Reliability

Table of ContentsHardware Reliability Design.................................................61Software Reliability Design..................................................64EMC.................................................................................65Whole-Equipment Heating ..................................................65

Hardware Reliability DesignAll racks and shelves in the RNC have two ways of power supply.Dual-way cabling is used inside all racks. The control-plane boardsare in active/standby working mode and the user-plane boardshave a redundant resource pool. Interface boards are in 1+1 orload-sharing working mode. Therefore, the whole system can stillrun normally even when a piece of hardware fails in the RNC.

Backup Mode Classification

To ensure the reliability, the key boards of ZXWR RNC provide threebackup modes: 1+1 backup mode, 1:1 backup mode, and loadsharing mode.

� 1+1 backup

1+1 backup is the M/S backup. In this mode, only the masterboard is in working status. For the boards to be master andslave to be each other, only the master board can bear services,including the access and processing. The slave board does notbear any services.

When the master board gets faulty, the system performs theM/S switching immediately. The slave board switches into themaster board and the master board switches into the slaveboard. The system functions will not be affected.

� 1:1 backup

At the same time, only the master board can deal with the dataand the interface units can be located on the salve board.

When the master board gets faulty, the system performs theM/S switching immediately. The previous slave board starts todeal with data. The previous master board switches into theslave board and deals with the interface.



� Load sharing

Load sharing mode is to back up the service data running onthe board.

That is, when the service is running, the related service datais distributed on several boards evenly. When one board getsfaulty, the service data can be shared onto other service boardsquickly. The service operation will not be affected.

Board Backup Modes

Currently, the backup modes supported by ZXWR RNC boards aredescribed in Table 15.

TABLE 15 BOARD BACKUP MODES

FunctionalBoard

PhysicalBoard

Backup ModeSupported Description

ROMB MPX86/2 11 backup

As the centralcontrol point ofthe whole sys-tem, the OMPmust be in 1 1backup mode,which is un-changeable.

RCB MPX86/2 11 backup None

RUB VTCD/2 Load sharing None

UIMC UIM/2 11 backup None

GUIM GUIM 11 backup None

THUB CHUB 11 backup None

CLKG It only serves asa clock board.

ICM

It serves as aclock board andprovides GPSaccess.

ICMG

ICM 11 backup

It serves as aclock board andprovides GPSaccess.

POSI MNIC/2 1:1 backup None


Chapter 7 Reliability

FunctionalBoard

PhysicalBoard


APBE APBE/2 1:1 backup

It supports fourSTM–1 opticalinterfacessimultaneouslyand the 1:1backup.

It providesAPS protectionfor one pairof intra-board STM-1interfaces orfour pairsof inter-board STM-1interfaces.

ET3A APBE/2 11 backup None

ET3I MNIC/2 11 backup None

GLI GLIQV/2 Load sharing None

PSN PSN4V/2 Load sharing None

SBCX SBCX 11 backup

Up to threeSBCXs can beconfigured,one for logmanagementand the othertwo for OMM.

It supports 11backup modeonly when itserves as theOMM NM server.

GIPI4 MNIC/3 1+1 backup orload sharing

The internal orexternal Ether-net interface onthe GIPI3 pro-vides 1–2 GE in-terfaces.

SDTA2 DTA 1:1 backup None

DTA DTA 1:1 backup None

DTI DTI 1:1 backup None

SDTI DTI 1:1 backup None



FunctionalBoard

PhysicalBoard


APBI APBE/2 1:1 backup or 11 backup

It providesAPS protectionfor two pairsof intra-boardSTM-1 interfa-ces or four pairsof inter-boardSTM-1 interfa-ces.

GIPI MNIC/2 11 backup None

EIPI MNIC/2 11 backup None

SDTA DTA 1:1 backup or 11 backup None

SDTB2 SDTB/2 1:1 backup None

Software Reliability DesignRNC software features a safe and reliable design. Except exter-nal operation and maintenance ports, the internal communicationof the whole system is completely separated from external net-works. The system has built-in firewall software that protects ex-ternal operation and maintenance ports and automatically detectsand prevents attacks. The operation and maintenance subsystemfeatures a strong authentication design that enables users to ob-tain authorities corresponding to their respective user names andpasswords.

ZTE Corporation’s software has a powerful error tolerance capabil-ity, which enables the following functions.

� The software can automatically detect the legality of the dataconfigured by users, rejects illegal or unreasonable data con-figurations, and ask users to make corrections.

� The software can back up key versions or data and automati-cally roll back such versions and data in case of loading failure.

� When running, the software provides such functions as watch-dog. If infinite loops or other errors occur during software run-ning, the software can automatically restart the board and re-cover working. Meanwhile, the black box function will recordthese errors for future analysis and handling.

� The software can automatically detect ports, links, or softwareand hardware faults according to hardware backup, and startor activate backup units to ensure the normal running of thesystem.


Chapter 7 Reliability

EMCEMC is mainly used for the shielding and grounding of the rackand the subracks. The shielding is designed according to the sub-rack level. When the frequency is between 30 MHz ~ 1 GHz, themin shielding characteristics are designed as 40 dB. The cabinetcontains the complete structure even when the shielding materialsare not installed.

The subracks must contain EMC shielding, so the surfaces are veryspecial. All are performed by electrolytic materials, ensuring thewell conductivity of the whole subrack. The joints of the sub-rack with the plugging component, and the plugging componentwith the plugging component are conducted with the conductivesprings, to eliminate the long gaps. Anti-static grounding deviceis installed on the subrack, connecting the subrack with the shelf,to ensure the grounding.

Whole-Equipment HeatingHeating

The subracks consume large power, so to dissipate the heat, blowinside the cabinet and wind at the top. The air goes in at thebottom and goes out at the top. The heat is dissipated forcedly.The air inlet is close to the ventilation hole at the bottom of thefront/rear door, where the dustproof measures are taken. Thereinstalls a group of fans on the rack, blowing to meet the ventilationon the rack.

Heat Dissipation

The heat dissipation of ZXWR RNC is as shown in Figure 18.



FIGURE 18 ZXWR RNC HEAT DISSIPATION


C h a p t e r 8

International Certificates

Table of ContentsTUV Certificate..................................................................67CE Certificate....................................................................68

TUV CertificateZXWR RNC products have passed TUV authentication. TUV certifi-cate is as shown in Figure 19.



FIGURE 19 TUV CERTIFICATE

CE CertificateZXWR RNC products have passed the security, EMC, and RF testsof CE authentication. CE certificate is as shown in Figure 20.


Chapter 8 International Certificates

FIGURE 20 CE CERTIFICATE





Figures

Figure 1 ZXWR RNC NAMEPLATE........................................... 1

Figure 2 LOCATION OF ZXWR RNC IN WCDMA SYSTEM............ 2

Figure 3 ZXWR RNC APPEARANCE......................................... 3

Figure 4 ZXWR RNC LOGIC STRUCTURE ...............................25

Figure 5 System Logic Unit Allocation ...................................26

Figure 6 Overall Structure of ZXWR RNC Software System ......45

Figure 7 ZXWR RNC/NM SOFTWARE STRUCTURE ...................49

Figure 8 NM NETWORKING PLAN .........................................54

Figure 9 ATM-BASED NETWORKING .....................................54

Figure 10 SDH-BASED NETWORKING ...................................55

Figure 11 IP-BASED NETWORKING ......................................55

Figure 12 HYBRID NETWORKING .........................................55

Figure 13 STAR NETWORKING MODE ...................................56

Figure 14 CHAIN NETWORKING MODE..................................56

Figure 15 RING NETWORKING MODE ...................................57

Figure 16 HYBRID NETWORKING MODE (STAR AND CHAIN) ....58

Figure 17 IU INTERFACE NETWORKING ................................59

Figure 18 ZXWR RNC HEAT DISSIPATION..............................66

Figure 19 TUV CERTIFICATE................................................68

Figure 20 CE CERTIFICATE..................................................69





Tables

Table 1 ZXWR RNC CABINET PHYSICAL SPECIFICATIONS......... 3

Table 2 Performance Indices................................................. 7

Table 3 Interface Indices ..................................................... 8

Table 4 Clock Indices .......................................................... 9

Table 5 Reliability Indices....................................................10

Table 6 EMC Indices ...........................................................11

Table 7 Dimensions and Weight ...........................................11

Table 8 Power Supply Requirements .....................................11

Table 9 Environmental Requirements....................................12

Table 10 Logic Unit Description............................................27

Table 11 ZXWR RNC Shelves ...............................................28

Table 12 ZXWR RNC Boards ................................................29

Table 13 ZXWR RNC Cables.................................................38

Table 14 ZXWR RNC SOFTWARE SUBSYSTEM ........................45

Table 15 Board Backup Modes .............................................62





Glossary

3GPP- 3rd Generation Partnership Project

A2SP- AAL2 Signalling Protocol

AAL2- ATM Adaptation Layer type 2

AAL5- ATM Adaptation Layer type 5

AGPS- Assisted Global Positioning System

ALCAP- Access Link Control Application Protocol

ATM- Asynchronous Transfer Mode

BHCA- Busy Hour Call Attempt

BNAS- Broadband Network Access Server

BSP- Board Support Package

BTS- Base Transceiver Station

CG- Charging Gateway

CN- Core Network

CPU- Central Processing Unit

CS- Circuit Switched

CTS- Call Trace System

CellID- Cell Identification

DCH- Dedicated Channel

DRBC- Dynamic Radio Bearer Control

DRNC- Drift Radio Network Controller

DSP- Digital Signal Processor



EMC- Electro-Magnetic Compatibility

EMS- Element Management System

EPU- Epilogue Process Unit

FACH- Forward Access Channel

FE- Fast Ethernet

FP- Frame Protocol

GE- Gigabit Ethernet

GERAN- GSM/EDGE Radio Access Network

GGSN- Gateway GPRS Supporting Node

GPS- Global Positioning System

GSM- Global System for Mobile Communication

GTP-U- GTP User Plane

HS-PDSCH- High-Speed Physical Downlink Shared Channel

HSDPA- High Speed Downlink Packet Access

HSPA- High Speed Packet Access

HSUPA- High Speed Uplink Packet Access

IM- Instant Message

IP- Internet Protocol

IPoA- IP over ATM

IUUP- Iu User Plane

LTE- Long Term Evolution

MAC- Medium Access Control

MBMS- Multimedia Broadcast/Multicast Service


Glossary

MGW- Media GateWay

MSC- Mobile Switching Center

MTBF- Mean Time Between Failures

MTP3B- B-ISDN Message Transfer Part level 3

MTTR- Mean Time To Recovery

NAS- Non-Access Stratum

NMS- Network Management System

NNI- Network Node Interface

NP- Network Processor

OMM- Operation & Maintenance Module

OMP- Operation & Maintenance Processor

PCB- Printed Circuit Board

PCH- Paging Channel

PDCP- Packet Data Convergence Protocol

POS- Packet Over SDH

PS- Packet Switched

QoS- Quality of Service

RAB- Radio Access Bearer

RAU- RNC Access Unit

RF- Radio Frequency

RLC- Radio Link Control

RNS- Radio Network Subsystem

ROMU- RNC Operating & Maintenance Unit



RPMU- RNC Peripheral Monitor Unit

RPU- RNC Processing Unit

RRC- Radio Resource Control

RRM- Radio Resource Management

RSU- RNC Switch Unit

RTT- Radio Transfer Technic

SAAL- Signaling ATM Adaptation Layer ATM

SBCX- X86 Single Board Computer

SCCP- Signaling Connection Control Part

SDH- Synchronous Digital Hierarchy

SF- Spreading Factor

SGSN- Service GPRS Supporting Node

SRNC- Serving Radio Network Controller

SRNS- Serving RNS

SSCF- Service Specific Coordination Function

STC- Signaling Transport Converter

STM- Synchronous Transfer Mode

TD-SCDMA- Time Division-Synchronization Code Division Multiple Access

TDM- Time Division Multiplexing

UDP- User Datagram Protocol

UE- User Equipment

UMTS- Universal Mobile Telecommunication System

UNI- User Network Interface


Glossary

UTRAN- UMTS Terrestrial Radio Access Network

VLAN- Virtual Local Area Network

VoIP- Voice over Internet Protocol

WCDMA- Wideband Code Division Multiple Access


Documents

SJ-20100603155704-007-ZXWR RNC (V3[1].09.30) System Description