RNC Product Description-(V200R010_03)

RNC

V200R010

Product Description

Issue 03

Date 2008-08-30

Part Number

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For anyassistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Copyright © Huawei Technologies Co., Ltd. 2008. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but the statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

http://www.huawei.com

mailto:[email protected]

Contents

About This Document.....................................................................................................................1

1 RNC Hardware Configuration Types....................................................................................1-1

2 RNC Structure.............................................................................................................................2-12.1 RNC Physical Structure..................................................................................................................................2-22.2 RNC Logical Structure....................................................................................................................................2-32.3 RNC Software Structure..................................................................................................................................2-4

3 RNC Logical Subsystems..........................................................................................................3-13.1 RNC Switching Subsystem.............................................................................................................................3-2

3.1.1 Functions of the RNC Switching Subsystem.........................................................................................3-23.1.2 Components of the RNC Switching Subsystem.....................................................................................3-2

3.2 RNC Service Processing Subsystem...............................................................................................................3-43.2.1 Functions of the RNC Service Processing Subsystem...........................................................................3-43.2.2 Components of the RNC Service Processing Subsystem.......................................................................3-5

3.3 RNC Transport Subsystem..............................................................................................................................3-63.3.1 Functions of the RNC Transport Subsystem..........................................................................................3-73.3.2 Components of the RNC Transport Subsystem.....................................................................................3-7

3.4 RNC OM Subsystem.......................................................................................................................................3-83.4.1 Components of the RNC OM Subsystem..............................................................................................3-93.4.2 Working Principles of the RNC OM Subsystem.................................................................................3-103.4.3 RNC OM Functions.............................................................................................................................3-133.4.4 RNC Active/Standby Workspaces.......................................................................................................3-133.4.5 RNC Security Management.................................................................................................................3-163.4.6 RNC Log Management........................................................................................................................3-163.4.7 RNC Configuration Management........................................................................................................3-173.4.8 RNC Performance Management..........................................................................................................3-223.4.9 RNC Alarm Management.....................................................................................................................3-223.4.10 RNC Loading Management...............................................................................................................3-243.4.11 BOOTP and DHCP on the Iub Interface............................................................................................3-283.4.12 RNC Upgrade Management...............................................................................................................3-29

3.5 RNC Clock Synchronization Subsystem.......................................................................................................3-313.5.1 RNC Clock Sources.............................................................................................................................3-313.5.2 Structure of the RNC Clock Synchronization Subsystem....................................................................3-32

RNCProduct Description Contents

Issue 03 (2008-08-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

i

3.5.3 Timing Signal Processing in the RNC.................................................................................................3-343.5.4 RFN Generation and Reception...........................................................................................................3-34

3.6 RNC Power Subsystem.................................................................................................................................3-353.6.1 Power Supply Requirements of the RNC.............................................................................................3-363.6.2 Layout of Power Switches on the RNC Cabinet .................................................................................3-403.6.3 Connections of Power Cables and PGND Cables in the RNC Cabinet...............................................3-42

3.7 RNC Environment Monitoring Subsystem...................................................................................................3-453.7.1 RNC Power Supply Monitoring...........................................................................................................3-453.7.2 RNC Fan Monitoring...........................................................................................................................3-463.7.3 RNC Cabinet Door Monitoring............................................................................................................3-473.7.4 RNC Water Monitoring........................................................................................................................3-47

4 RNC Signal Flow........................................................................................................................4-14.1 RNC Signal Flow on the Control Plane..........................................................................................................4-2

4.1.1 Control Message Flow on the Uu Interface...........................................................................................4-24.1.2 Control Message Flow on the Iub Interface...........................................................................................4-44.1.3 Control Message Flow on the Iu/Iur Interfaces......................................................................................4-5

4.2 RNC Signal Flow on the User Plane...............................................................................................................4-54.2.1 Data Flow Between Iub and Iu-CS/Iu-PS..............................................................................................4-64.2.2 Data Flow from Iu-BC to Iub.................................................................................................................4-8

5 RNC Transport and Networking.............................................................................................5-15.1 Transport and Networking on the Iub Interface..............................................................................................5-2

5.1.1 Interface Boards for the Iub....................................................................................................................5-25.1.2 ATM-Based Networking on the Iub Interface.......................................................................................5-35.1.3 IP-Based Networking on the Iub Interface.............................................................................................5-55.1.4 ATM/IP-Based Networking on the Iub Interface...................................................................................5-85.1.5 Satellite-Based Networking on the Iub Interface...................................................................................5-95.1.6 2G/3G Concurrent Transmission and Networking...............................................................................5-11

5.2 Transport and Networking on the Iu/Iur Interface........................................................................................5-145.2.1 Interface Boards for the Iu or Iur Interface..........................................................................................5-145.2.2 Networking Differences in 3GPP Protocol Releases...........................................................................5-155.2.3 ATM-Based Networking on the Iu or Iur Interface.............................................................................5-165.2.4 IP-Based Networking on the Iu/Iur Interface.......................................................................................5-21

5.3 Transport and Networking on the Iu-BC Interface.......................................................................................5-275.3.1 Interface Boards for the Iu-BC Interface..............................................................................................5-275.3.2 ATM-Based Networking on the Iu-BC Interface.................................................................................5-285.3.3 IP-Based Networking on the Iu-BC Interface......................................................................................5-29

5.4 RNC OM Networking...................................................................................................................................5-29

6 RNC Parts Reliability................................................................................................................6-16.1 Concepts Related to RNC Parts Reliability.....................................................................................................6-2

6.1.1 RNC Backup Types................................................................................................................................6-26.1.2 Resource Pool.........................................................................................................................................6-2

ContentsRNC

Product Description

ii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 03 (2008-08-30)

6.1.3 Port Trunking.........................................................................................................................................6-26.1.4 Load Sharing Between FE/GE Ports......................................................................................................6-3

6.2 RNC Board Redundancy.................................................................................................................................6-36.2.1 Backup of OMUa Boards.......................................................................................................................6-46.2.2 Backup of SCUa Boards........................................................................................................................6-56.2.3 Backup of SPUa Boards.........................................................................................................................6-56.2.4 Backup of GCUa/GCGa Boards............................................................................................................6-66.2.5 Backup of AEUa Boards........................................................................................................................6-76.2.6 Backup of PEUa Boards.........................................................................................................................6-86.2.7 Backup of AOUa Boards........................................................................................................................6-86.2.8 Backup of POUa Boards........................................................................................................................6-96.2.9 Backup of UOIa Boards.......................................................................................................................6-106.2.10 Backup of FG2a/GOUa Boards..........................................................................................................6-116.2.11 Resource Pool of DPUb Boards.........................................................................................................6-12

6.3 RNC Port Redundancy..................................................................................................................................6-126.3.1 Backup of AOUa Optical Ports............................................................................................................6-136.3.2 Backup of POUa Optical Ports.............................................................................................................6-146.3.3 Backup of UOIa Optical Ports.............................................................................................................6-156.3.4 Backup of FE/GE Ports........................................................................................................................6-166.3.5 Load Sharing on FE/GE Ports..............................................................................................................6-166.3.6 Port Trunking of GE Ports...................................................................................................................6-17

7 RNC Technical Specifications.................................................................................................7-17.1 RNC Capacity.................................................................................................................................................7-37.2 RNC Engineering Specifications....................................................................................................................7-37.3 RNC Ports.......................................................................................................................................................7-57.4 RNC Reliability...............................................................................................................................................7-77.5 RNC Noise and Safety Compliance................................................................................................................7-77.6 RNC Environmental Protection Specifications...............................................................................................7-87.7 RNC Clock Precision Requirements...............................................................................................................7-87.8 RNC Storage Requirements............................................................................................................................7-87.9 RNC Transportation Requirements...............................................................................................................7-117.10 RNC Working Environment Requirements................................................................................................7-137.11 Technical Specifications for RNC Parts......................................................................................................7-15

7.11.1 Technical Specifications for the RNC Power Distribution Box........................................................7-177.11.2 Technical Specifications for the RNC Fan Box.................................................................................7-187.11.3 Technical Specifications for the OMUa Board..................................................................................7-187.11.4 Technical Specifications for the SCUa Board....................................................................................7-197.11.5 Technical Specifications for the SPUa Board....................................................................................7-207.11.6 Technical Specifications for the DPUb Board...................................................................................7-217.11.7 Technical Specifications for the GCUa/GCGa Board........................................................................7-227.11.8 Technical Specifications for the AEUa Board...................................................................................7-227.11.9 Technical Specifications for the AOUa Board...................................................................................7-23

RNCProduct Description Contents


iii

7.11.10 Technical Specifications for the UOIa Board..................................................................................7-257.11.11 Technical Specifications for the POUa Board.................................................................................7-287.11.12 Technical Specifications for the PEUa Board..................................................................................7-307.11.13 Technical Specifications for the FG2a Board..................................................................................7-317.11.14 Technical Specifications for the GOUa Board.................................................................................7-327.11.15 Technical Specifications for the PFCU Board.................................................................................7-347.11.16 Technical Specifications for the PAMU Board................................................................................7-35

ContentsRNC

Product Description

iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 03 (2008-08-30)

Figures

Figure 1-1 RNC minimum configuration.............................................................................................................1-1Figure 1-2 RNC maximum configuration............................................................................................................1-2Figure 2-1 RNC physical structure.......................................................................................................................2-2Figure 2-2 RNC logical structure.........................................................................................................................2-3Figure 2-3 FAM software structure......................................................................................................................2-4Figure 2-4 BAM software structure.....................................................................................................................2-4Figure 2-5 LMT software structure......................................................................................................................2-5Figure 3-1 Components of the RNC switching subsystem..................................................................................3-3Figure 3-2 RNC inter-subrack switching.............................................................................................................3-4Figure 3-3 Components of the RNC service processing subsystem....................................................................3-5Figure 3-4 Components and physical connections of the RNC OM subsystem..................................................3-9Figure 3-5 Structure of the RNC OM subsystem...............................................................................................3-11Figure 3-6 OM dual planes.................................................................................................................................3-12Figure 3-7 Process of RNC online configuration...............................................................................................3-19Figure 3-8 Process of RNC offline configuration..............................................................................................3-19Figure 3-9 Process of RNC dynamic batch configuration..................................................................................3-20Figure 3-10 Process of performance measurement............................................................................................3-22Figure 3-11 Process of alarm management........................................................................................................3-23Figure 3-12 Process of driving the RNC alarm box...........................................................................................3-24Figure 3-13 Process of loading RNC program files...........................................................................................3-27Figure 3-14 Process of loading RNC data files..................................................................................................3-28Figure 3-15 RNC remote upgrade......................................................................................................................3-29Figure 3-16 Structure of the RNC clock synchronization subsystem................................................................3-32Figure 3-17 Clock cable connections between GCUa/GCGa boards and SCUa boards....................................3-33Figure 3-18 RFN generation and reception........................................................................................................3-35Figure 3-19 Power supply schemes of the RNC................................................................................................3-37Figure 3-20 Working mechanism of the power distribution box.......................................................................3-40Figure 3-21 Assignment of power switches on the power distribution box ......................................................3-41Figure 3-22 Connections of power cables and PGND cables in the N68E-22 cabinet......................................3-42Figure 3-23 Connections of power cables and PGND cables in the N68-21-N cabinet....................................3-44Figure 3-24 RNC power monitoring principles.................................................................................................3-46Figure 3-25 RNC fan monitoring principles......................................................................................................3-46Figure 3-26 RNC cabinet door monitoring principles........................................................................................3-47

RNCProduct Description Figures


v

Figure 3-27 RNC water monitoring principles...................................................................................................3-48Figure 4-1 Intra-RNC control message flow on the Uu interface .......................................................................4-2Figure 4-2 Inter-RNC control message flow on the Uu interface .......................................................................4-3Figure 4-3 Control message flow on the Iub interface.........................................................................................4-4Figure 4-4 Control message flow on the Iu/Iur interfaces....................................................................................4-5Figure 4-5 Intra-RNC data flow between Iub and Iu-CS/Iu-PS...........................................................................4-6Figure 4-6 Inter-RNC data flow between Iub and Iu-CS/Iu-PS...........................................................................4-7Figure 4-7 Data flow from Iu-BC to Iub..............................................................................................................4-8Figure 5-1 ATM networking based on PDH........................................................................................................5-3Figure 5-2 ATM networking based on ATM over E1/T1 over SDH...................................................................5-4Figure 5-3 ATM networking based on ATM over SDH......................................................................................5-4Figure 5-4 IP networking based on PDH/SDH....................................................................................................5-6Figure 5-5 IP networking based on ATM over E1/T1 over SDH........................................................................5-6Figure 5-6 IP networking based on MSTP...........................................................................................................5-7Figure 5-7 IP networking based on data network.................................................................................................5-7Figure 5-8 IP networking based on hybrid IP transport.......................................................................................5-8Figure 5-9 ATM/IP-based networking on the Iub interface.................................................................................5-9Figure 5-10 Satellite-based networking on the Iub interface.............................................................................5-10Figure 5-11 Fractional-based networking with timeslot cross connection on 2G equipment............................5-12Figure 5-12 Fractional-based networking with timeslot cross connection on 3G equipment............................5-13Figure 5-13 Fractional-based networking with timeslot cross connection on external equipment....................5-13Figure 5-14 Iu-CS networking in R99................................................................................................................5-15Figure 5-15 Iu-CS networking in R4/R5/R6......................................................................................................5-16Figure 5-16 Networking based on SDH with MSP backup between optical ports............................................5-17Figure 5-17 Networking based on SDH with load sharing between optical ports.............................................5-18Figure 5-18 Networking based on SDH with STM-1 shared by Iu and Iur.......................................................5-19Figure 5-19 Networking based on ATM............................................................................................................5-20Figure 5-20 Single-homing layer 3 networking.................................................................................................5-22Figure 5-21 Dual-homing layer 3 networking....................................................................................................5-23Figure 5-22 Direct connection with load sharing...............................................................................................5-23Figure 5-23 Networking based on SDH with MSP backup between optical ports............................................5-24Figure 5-24 Networking based on SDH with load sharing between optical ports.............................................5-25Figure 5-25 Networking based on SDH with STM-1 shared by Iu and Iur.......................................................5-26Figure 5-26 ATM-based networking on the Iu-BC interface.............................................................................5-28Figure 5-27 IP networking based on data network.............................................................................................5-29Figure 5-28 RNC OM networking.....................................................................................................................5-30

FiguresRNC

Product Description

vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 03 (2008-08-30)

Tables

Table 1-1 Other configurations.............................................................................................................................1-2Table 2-1 RNC hardware......................................................................................................................................2-2Table 3-1 RNC offline configuration commands...............................................................................................3-18Table 3-2 Program file names of RNC boards...................................................................................................3-24Table 3-3 Description of the data file names......................................................................................................3-25Table 3-4 Nominal voltage and frequency of low-voltage AC power...............................................................3-38Table 3-5 Specifications for the DC power supply............................................................................................3-39Table 3-6 Working mechanism of the power distribution box...........................................................................3-40Table 3-7 Relation between the switches and subracks......................................................................................3-41Table 3-8 Connections of power cables and PGND cables in the RNC cabinet................................................3-43Table 3-9 Connections of power cables and PGND cables in the RNC cabinet................................................3-44Table 5-1 Satellite transmission bands...............................................................................................................5-11Table 7-1 Specifications for RNC capacity..........................................................................................................7-3Table 7-2 Structural specifications.......................................................................................................................7-3Table 7-3 Electrical specifications.......................................................................................................................7-4Table 7-4 Choosing feeders according to the distance.........................................................................................7-5Table 7-5 Specifications for external transmission ports.....................................................................................7-5Table 7-6 Specifications for internal transmission ports......................................................................................7-6Table 7-7 Specifications for the satellite signal port and clock ports...................................................................7-7Table 7-8 Specifications for RNC reliability........................................................................................................7-7Table 7-9 RNC noise and safety compliance.......................................................................................................7-8Table 7-10 Climatic requirements for storing the RNC.......................................................................................7-8Table 7-11 Storage requirements for physically active materials......................................................................7-10Table 7-12 Storage requirements for chemically active materials.....................................................................7-10Table 7-13 Mechanical stress requirements for storing the RNC.......................................................................7-10Table 7-14 Climatic requirements for transporting the RNC.............................................................................7-11Table 7-15 Transportation requirements for physically active materials...........................................................7-12Table 7-16 Transportation requirements for chemically active materials..........................................................7-12Table 7-17 Mechanical stress requirements for transporting the RNC..............................................................7-13Table 7-18 Temperature and humidity requirements for operating the RNC....................................................7-13Table 7-19 Other climatic requirements for operating the RNC........................................................................7-14Table 7-20 Working environment requirements for physically active materials...............................................7-14Table 7-21 Working environment requirements for chemically active materials..............................................7-15

RNCProduct Description Tables


vii

Table 7-22 Mechanical stress requirements for operating the RNC...................................................................7-15Table 7-23 Technical specifications for the RNC power distribution box.........................................................7-17Table 7-24 Technical specifications for the RNC fan box.................................................................................7-18Table 7-25 Hardware specifications for the OMUa board.................................................................................7-18Table 7-26 Performance specifications for the OMUa board.............................................................................7-19Table 7-27 Technical specifications for the SCUa board...................................................................................7-20Table 7-28 Technical specifications for the SPUa board...................................................................................7-20Table 7-29 Technical specifications for the DPUb board..................................................................................7-21Table 7-30 Technical specifications for the GCUa/GCGa board.......................................................................7-22Table 7-31 Hardware specifications for the AEUa board..................................................................................7-22Table 7-32 Specifications for the processing capability of the AEUa board.....................................................7-23Table 7-33 Hardware specifications for the AOUa board..................................................................................7-24Table 7-34 Specifications for the processing capability of the AOUa board.....................................................7-24Table 7-35 Specifications for optical ports on the AOUa board........................................................................7-25Table 7-36 Hardware specifications for the UOIa board....................................................................................7-25Table 7-37 Specifications for the processing capability of the UOIa board (UOIa_ATM)...............................7-26Table 7-38 Specifications for the processing capability of the UOI board (UOI_IP)........................................7-27Table 7-39 Specifications for optical ports on the UOIa board..........................................................................7-27Table 7-40 Hardware specifications for the POUa board...................................................................................7-28Table 7-41 Specifications for the processing capability of the POUa board......................................................7-29Table 7-42 Specifications for optical ports on the POIa board..........................................................................7-29Table 7-43 Hardware specifications for the PEUa board...................................................................................7-30Table 7-44 Specifications for the processing capability of the PEUa board......................................................7-31Table 7-45 Hardware specifications for the FG2a board....................................................................................7-31Table 7-46 Specifications for the processing capability of the FG2a board.......................................................7-32Table 7-47 Hardware specifications for the GOUa board..................................................................................7-32Table 7-48 Specifications for the processing capability of the GOUa board.....................................................7-33Table 7-49 Specifications for optical ports on the GOUa board........................................................................7-34Table 7-50 Technical specifications for the PFCU board..................................................................................7-34Table 7-51 Technical specifications for the PAMU board.................................................................................7-35

TablesRNC

Product Description

viii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 03 (2008-08-30)

About This Document

PurposeThis document describes the RNC in terms of the physical, logical, and software structures, thephysical and logical components, and the working principles. In addition, this documentdescribes the signal flows, transport and networking, and technical specifications for the RNC.

VersionThe following table lists the product version related to this document.

Product Name Model Version

RNC BSC6810 V200R010

Intended AudienceThis document is intended for:l Network planners

l System engineers

l Field engineers

Change HistoryRefer to Changes in RNC Product Description.

Organization1 RNC Hardware Configuration Types

RNC hardware configuration is of the following types: minimum configuration, maximumconfiguration, and other configurations.

2 RNC Structure

This describes the RNC in terms of its physical structure, logical structure, and softwarestructure.

3 RNC Logical Subsystems

RNCProduct Description About This Document


1

The RNC logical subsystems consist of the following subsystems: switching subsystem, serviceprocessing subsystem, transport subsystem, clock synchronization subsystem, Operation andMaintenance (OM) subsystem, power subsystem, and environment monitoring subsystem.

4 RNC Signal Flow

This describes signal flows on the control planes and user planes of the Uu, Iub, Iur, and Iuinterfaces.

5 RNC Transport and Networking

This describes the networking modes on the RNC side in terms of the transport and networkingon the Iub, Iu-CS/Iu-PS/Iur, and Iu-BC interfaces and the RNC OM networking.

6 RNC Parts Reliability

The RNC guarantees its operation reliability by means of board redundancy and port redundancy.

7 RNC Technical Specifications

The RNC technical specifications cover the RNC capacity, engineering, physical ports,reliability, noise and safety compliance, environmental protection, clock precision, and so on.

Conventions

1. Symbol Conventions

The following symbols may be found in this document. They are defined as follows

Symbol Description

DANGERIndicates a hazard with a high level of risk that, if not avoided,will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk which, ifnot avoided, could result in minor or moderate injury.

CAUTIONIndicates a potentially hazardous situation that, if not avoided,could cause equipment damage, data loss, and performancedegradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or save yourtime.

NOTE Provides additional information to emphasize or supplementimportant points of the main text.

2. General Conventions

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

About This DocumentRNC

Product Description

2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 03 (2008-08-30)


Boldface Names of files,directories,folders,and users are in boldface. Forexample,log in as user root .

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

3. Command Conventions


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[ ] Items (keywords or arguments) in square brackets [ ] are optional.

{x | y | ...} Alternative items are grouped in braces and separated by verticalbars.One is selected.

[ x | y | ... ] Optional alternative items are grouped in square brackets andseparated by vertical bars.One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated by verticalbars.A minimum of one or a maximum of all can be selected.

[ x | y | ... ] * Alternative items are grouped in braces and separated by verticalbars.A minimum of zero or a maximum of all can be selected.

4. GUI Conventions


Boldface Buttons,menus,parameters,tabs,window,and dialog titles are inboldface. For example,click OK.

> Multi-level menus are in boldface and separated by the ">" signs.For example,choose File > Create > Folder .

5. Keyboard Operation


Key Press the key.For example,press Enter and press Tab.

Key1+Key2 Press the keys concurrently.For example,pressing Ctrl+Alt+Ameans the three keys should be pressed concurrently.

Key1,Key2 Press the keys in turn.For example,pressing Alt,A means the twokeys should be pressed in turn.

RNCProduct Description About This Document


3

6. Mouse Operation

Action Description

Click Select and release the primary mouse button without moving thepointer.

Double-click Press the primary mouse button twice continuously and quicklywithout moving the pointer.

Drag Press and hold the primary mouse button and move the pointerto a certain position.

About This DocumentRNC

Product Description

4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 03 (2008-08-30)

1 RNC Hardware Configuration Types

RNC hardware configuration is of the following types: minimum configuration, maximumconfiguration, and other configurations.

Minimum Configuration

The RNC supports the minimum configuration of a single cabinet, that is, an RSR cabinetconfigured with only an RSS subrack, as shown in Figure 1-1.

Figure 1-1 RNC minimum configuration

The maximum capacity of the RNC in minimum configuration is as follows:

l 6,000 Erlang voice traffic

l 384 Mbit/s (UL + DL) PS throughput

l 200 NodeBs and 600 cells

Maximum Configuration

Figure 1-2 shows the maximum configuration of the RNC. In maximum configuration, the RNCconsists of two cabinets: one RSR cabinet and one RBR cabinet. The two cabinets hold sixsubracks: one RSS subrack and five RBS subracks.

RNCProduct Description 1 RNC Hardware Configuration Types


1-1

Figure 1-2 RNC maximum configuration

The maximum capacity of the RNC in maximum configuration is as follows:l 51,000 Erlang voice traffic

l 3,264 Mbit/s (UL + DL) PS throughput

l 1,700 NodeBs and 5,100 cells

Other ConfigurationsTable 1-1 describes RNC configurations other than the minimum and maximum configurations.You can choose a configuration as required.

Table 1-1 Other configurations

Number ofSubracks

Number ofCabinets

VoiceTraffic(Erlang)

(UL + DL) PSThroughput(Mbit/s)

Number ofNodeBs

Numberof Cells

1 RSS + 1RBS

1 RSR 15,000 960 500 1,500

1 RSS + 2RBSs

1 RSR 24,000 1,536 800 2,400

1 RSS + 3RBSs

1 RSR + 1RBR

33,000 2,112 1,100 3,300

1 RSS + 4RBSs

1 RSR + 1RBR

42,000 2,688 1,400 4,200

NOTE

The previous data is calculated on the basis of the Huawei traffic model. The actual data can be calculatedon the basis of the operator's traffic model.

1 RNC Hardware Configuration TypesRNC

Product Description

1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 03 (2008-08-30)

2 RNC Structure

About This Chapter

This describes the RNC in terms of its physical structure, logical structure, and softwarestructure.

2.1 RNC Physical StructureThe RNC hardware consists of the cabinet, the cables, the GPS antenna system, the LMT PC,and the alarm box.

2.2 RNC Logical StructureLogically, the RNC consists of the following subsystems: switching subsystem, serviceprocessing subsystem, transport subsystem, clock synchronization subsystem, Operation andMaintenance (OM) subsystem, power subsystem, and environment monitoring subsystem.

2.3 RNC Software StructureThe RNC software has a distributed structure. It consists of Front Administration Module (FAM)software, Back Administration Module (BAM) software, and Local Maintenance Terminal(LMT) software.

RNCProduct Description 2 RNC Structure


2-1

2.1 RNC Physical StructureThe RNC hardware consists of the cabinet, the cables, the GPS antenna system, the LMT PC,and the alarm box.

Figure 2-1 shows the RNC physical structure.

Figure 2-1 RNC physical structure

(1) GPS: Global Positioning System (2) PDF: Power Distribution Frame (DC)

(3) LMT: Local Maintenance Terminal

Table 2-1 describes the components of the RNC.

Table 2-1 RNC hardware

Component Description

RSR cabinet For details, refer to RNC Cabinet.

RBR cabinet For details, refer to RNC Cabinet.

RNC cables For details, refer to RNC Cables.

2 RNC StructureRNC

Product Description


Issue 03 (2008-08-30)

Component Description

RNC GPS antennasystem

The system is composed of the antenna, feeder, jumper, and surgeprotector.The RNC GPS antenna system is used to receive GPS satellitesignals. It is optional.

RNC LMT PC The LMT PC refers to the Operation and Maintenance (OM)terminal that is installed with the Huawei Local MaintenanceTerminal software and is connected to the OM network of RNC. TheLMT is used to operate and maintain the RNC.For details, refer to the RNC LMT User Guide.

RNC alarm box For details, refer to RNC Alarm Box.

2.2 RNC Logical StructureLogically, the RNC consists of the following subsystems: switching subsystem, serviceprocessing subsystem, transport subsystem, clock synchronization subsystem, Operation andMaintenance (OM) subsystem, power subsystem, and environment monitoring subsystem.

Figure 2-2 shows the logical structure of the RNC.

Figure 2-2 RNC logical structure

NOTE

Figure 2-2 shows only the switching subsystem, service processing subsystem, transport subsystem, OMsubsystem, and clock synchronization subsystem. Besides these subsystems, the RNC has the powersubsystem and environment monitoring subsystem.



2-3

2.3 RNC Software StructureThe RNC software has a distributed structure. It consists of Front Administration Module (FAM)software, Back Administration Module (BAM) software, and Local Maintenance Terminal(LMT) software.

FAM Software

The FAM software is used in the host of the RNC. It enables the RNC to provide services.

The software is distributed in the FAM boards. It consists of the operating system, middleware,and application software, as shown in Figure 2-3.

Figure 2-3 FAM software structure

l Operating system: The operating system is VxWorks, which is a real-time operating system.

l Middleware: Middleware enables the upper-layer application software to be independentof the lower-layer operating system. This scenario is useful for the reuse of softwarefunctions of different platforms.

l Application software: The application software is a functional software of the RNC. It isused to implement the functions of different logical entities. Different types of boards maybe configured with different software. Application software includes operation andmaintenance software (OM), database software (DB), signaling processing software (SIG),user plane processing software (FMR), control plane processing software (RR), and radioresource management software (RRM).

BAM Software

The BAM software is installed on the OMUa board. The software consists of the operatingsystem, database software, and application software, as shown in Figure 2-4.

Figure 2-4 BAM software structure

l Operating system: The operating system is Windows Server 2003.

2 RNC StructureRNC

Product Description


Issue 03 (2008-08-30)

l Database software: The database software is SQL Server 2000.

l Application software: The application software is the BAM application. This applicationis the operation and maintenance software of the RNC. It is used to implement the functionsof different logical BAM entities.

LMT SoftwareThe LMT software is installed on the LMT PC. The software consists of the operating systemand application software, as shown in Figure 2-5.

Figure 2-5 LMT software structure

l Operating system: The operating system is Windows XP Professional.

l Application software: The application software is the LMT application. It provides theexecution entry to the operation and maintenance of the RNC. The software includes theLocal Maintenance Terminal, Trace Viewer, Monitor Viewer, Performance Browser Tool,FTP Client, Convert Management System, and LMT Service Manager.



2-5

3 RNC Logical Subsystems

About This Chapter

The RNC logical subsystems consist of the following subsystems: switching subsystem, serviceprocessing subsystem, transport subsystem, clock synchronization subsystem, Operation andMaintenance (OM) subsystem, power subsystem, and environment monitoring subsystem.

3.1 RNC Switching SubsystemThis describes the functions and components of the RNC switching subsystem.

3.2 RNC Service Processing SubsystemThis describes the functions and components of the RNC service processing subsystem.

3.3 RNC Transport SubsystemThis describes the functions and components of the RNC transport subsystem.

3.4 RNC OM SubsystemThe RNC OM subsystem is responsible for the operation and maintenance of the RNC.

3.5 RNC Clock Synchronization SubsystemThe RNC clock synchronization subsystem consists of the GCUa/GCGa boards in the RSSsubrack and the clock processing unit of each subrack. It provides timing signals for the RNC,generates the RFN, and provides reference clocks for NodeBs.

3.6 RNC Power SubsystemThe RNC power subsystem serves the entire equipment. This subsystem adopts the dual-circuitbackup and monitor-at-each-point solution, thus featuring high reliability.

3.7 RNC Environment Monitoring SubsystemThe RNC environment monitoring subsystem automatically monitors the working environmentof the RNC and reports faults in real time.

RNCProduct Description 3 RNC Logical Subsystems


3-1

3.1 RNC Switching SubsystemThis describes the functions and components of the RNC switching subsystem.

3.1.1 Functions of the RNC Switching SubsystemThe RNC switching subsystem mainly performs the switching of data in the RNC.

3.1.2 Components of the RNC Switching SubsystemThe RNC switching subsystem consists of the switching and control unit and high-speedbackplane channels in each subrack.

3.1.1 Functions of the RNC Switching SubsystemThe RNC switching subsystem mainly performs the switching of data in the RNC.

The switching subsystem has the following functions:l Provides internal Medium Access Control (MAC) switching for the RNC and enables

convergence of ATM and IP networks.l Provides port trunking for the RNC.

l Connects subracks of the RNC.

l Provides a service switching channel for the service processing subracks of the RNC.

l Provides an OM channel for the service processing subracks of the RNC.

l Distributes timing signals and RFN signals to the service processing boards of the RNC.

3.1.2 Components of the RNC Switching SubsystemThe RNC switching subsystem consists of the switching and control unit and high-speedbackplane channels in each subrack.

Figure 3-1 shows the components of the RNC switching subsystem.

3 RNC Logical SubsystemsRNC

Product Description


Issue 03 (2008-08-30)

Figure 3-1 Components of the RNC switching subsystem

Switching and Control UnitEach switching and control unit shown in Figure 3-1 is implemented by an SCUa board. Theboard provides a platform of GE switching and of maintenance and administration for the RNC.For functions of the SCUa board, refer to Functions of the SCUa Board.

Each subrack of the RNC can be configured with two SCUa boards. The SCUa boards enableconnection of subracks for the RNC.

NOTE

For details about the maintenance and administration functions of the SCUa board, refer to 3.4.1Components of the RNC OM Subsystem.

Intra-Subrack Data SwitchingThe intra-subrack data switching of the RNC adopts backplane-based communication. The intra-subrack switching channels provide port trunking. The GE switching between the SCUa boardand the other boards in the subrack is performed through the high-speed backplane channels.

Inter-Subrack Data SwitchingThe inter-subrack data switching of the RNC adopts star topology. In this topology, the RSS isthe main subrack and the RBSs are extension subracks. The SCUa boards in the RBS subracksare connected to the SCUa boards in the RSS subrack through Ethernet cables. The inter-subrackGE switching is performed through the RSS subrack. Figure 3-2 shows the inter-subrackconnections.



3-3

Figure 3-2 RNC inter-subrack switching

The RSS subrack and an RBS subrack are connected in full connection mode. Thus, the failureof any board does not affect data switching of the RNC. The GE ports on the SCUa board provideport trunking. As shown in Figure 3-2, four GE channels comprise a trunk group. Port trunkingenables bandwidth expansion and traffic balancing.

3.2 RNC Service Processing SubsystemThis describes the functions and components of the RNC service processing subsystem.

3.2.1 Functions of the RNC Service Processing SubsystemThe RNC service processing subsystem implements most RNC functions defined in the 3GPPprotocols and processes services of the RNC.

3.2.2 Components of the RNC Service Processing SubsystemThe RNC service processing subsystem consists of the signaling processing unit and dataprocessing unit.

3.2.1 Functions of the RNC Service Processing SubsystemThe RNC service processing subsystem implements most RNC functions defined in the 3GPPprotocols and processes services of the RNC.

The service processing subsystem has the following functions:l User data transfer

l System admission control

l Radio channel ciphering and deciphering

l Integrity protection

l Mobility management

l Radio resource management and control

l Multimedia broadcast

l Message tracing


Product Description


Issue 03 (2008-08-30)

l Radio Access Network (RAN) information management

Service processing subsystems can be increased as required, thus expanding the serviceprocessing capacity of the RNC.

Service processing subsystems communicate with each other through the switching subsystemto perform coordination tasks such as handover.

3.2.2 Components of the RNC Service Processing SubsystemThe RNC service processing subsystem consists of the signaling processing unit and dataprocessing unit.

Figure 3-3 shows the components of the RNC service processing subsystem.

Figure 3-3 Components of the RNC service processing subsystem

Signaling Processing UnitThe signaling processing unit is implemented by the SPUa board. An SPUa board has fourindependent subsystems. Each subrack has a subsystem working as the Main Processing Unit(MPU) subsystem for the management of resources on the user plane and resource allocationduring a call. The other subsystems work as Signaling Process Unit (SPU) subsystems, whichprocess signaling messages on the Iu, Iur, Iub, and Uu interfaces to implement the signalingprocessing function. For details about the functions of the SPUa board, refer to Functions ofthe SPUa Board.

The signaling processing unit has the radio network layer and the transport network layer interms of functions. The two layers have the following functions:l The radio network layer processes the signaling on the Uu, Iu, Iur, and Iub interfaces.

l The transport network layer provides bearer resources for the signaling on the Iu, Iur, andIub interfaces.



3-5

Data Processing UnitThe data processing unit is implemented by the DPUb board. A DPUb board has 22 DigitalSignal Processors (DSPs). The DPUb performs L2 processing on the data sent from the interfaceboard and separates CS and PS domain data and Uu signaling messages. For details about thefunctions of the DPUb board, refer to Functions of the DPUb Board.

The data processing unit has the following modules:l FP: Frame Protocol (FP) implements Iub and Iur signaling procedures, such as frame

processing, synchronization, and time adjustment.l MDC: Macro Diversity Combining (MDC) processes the uplink combining and downlink

distribution of the macro diversity for a UE during soft handover, thus improving thetransmission quality.

l MAC: Medium Access Control (MAC) implements certain functions during datatransmission. These functions are mapping of logical channels to transport channels,transport channel scheduling, radio resource reconfiguration, and traffic measurement.MAC entities are of three types: MAC-hs, MAC-d, and MAC-es. MAC-c entities processdata on common channels. MAC-d entities process data on dedicated channels. MAC-esentities process High Speed Uplink Packet Access (HSUPA) services.

l RLC: Radio Link Control (RLC) transfers upper-layer Service Data Units (SDUs) inTransparent Mode (TM), Unacknowledged Mode (UM), or Acknowledged Mode (AM).AM provides the sliding window mechanism to ensure error-free data transmission.

l PDCP: Packet Data Convergence Protocol (PDCP) processes PS data on the Iu interfaceand forwards the data during certain operations. These operations are PS data transmission,header compression and decompression of IP data streams, and lossless Serving RadioNetwork System (SRNS) relocation.

l Iu UP: Iu User Plane protocol (Iu UP) performs operations such as Iu UP in-band controlprocedures and Iu data conversion and transmission from Non-Access Stratum (NAS) atthe CN to the Access Stratum (AS) user plane at the RNC.

l BMC: Broadcast/Multicast Control protocol (BMC) saves cell broadcast messages,measures traffic, requests radio resources for the Cell Broadcast Service (CBS), schedulesBMC messages, and transmits scheduling messages and CBS messages to the BMC of theUE.

l GTP-U: GPRS Tunnelling Protocol for User Plane carries user packets and signalingmessages for path management and error indication.

Resource Sharing Between RNC Control Plane and User PlaneIn the RNC, the SPU subsystems, working as the processor for control plane data, form a controlplane resource pool; the DSPs, working as the processor for user plane data, form a user planeresource pool.

The resources of control plane and user plane within a subrack are managed and allocated bythe MPU subsystem on the controlling SPUa board. When a new service request arrives at thesubrack, the MPU subsystem forwards the resources request to other subracks in case ofoverload. If any subrack has enough resources of control plane and user plane, the new servicerequest can be successfully processed.

3.3 RNC Transport SubsystemThis describes the functions and components of the RNC transport subsystem.


Product Description


Issue 03 (2008-08-30)

3.3.1 Functions of the RNC Transport SubsystemThe RNC transport subsystem provides transmission ports and resources on the Iub, Iur, and Iuinterfaces for the RNC, processes transport network layer messages, and enables interactionbetween RNC internal data and external data.

3.3.2 Components of the RNC Transport SubsystemThe RNC transport subsystem consists of the transmission interface boards.

3.3.1 Functions of the RNC Transport SubsystemThe RNC transport subsystem provides transmission ports and resources on the Iub, Iur, and Iuinterfaces for the RNC, processes transport network layer messages, and enables interactionbetween RNC internal data and external data.

Providing Diverse Transmission PortsThe RNC transport subsystem provides the RNC with diverse transport solutions, supports ATMand IP transport at the same time, and meets networking requirements of different transportnetworks.

The transport subsystem provides the following types of transmission port:l E1/T1

l Channelized STM-1/OC-3 optical port

l Unchannelized STM-1/OC-3c optical port

l FE/GE electrical port

l GE optical port

Processing Transport Network Layer DataThe RNC transport subsystem processes transport network layer messages.l In ATM transport mode, the transport subsystem terminates AAL2/AAL5 messages.

l In IP transport mode, the transport subsystem terminates user plane UDP/IP messages andforwards control plane IP messages.

Through the transport subsystem, the RNC shields the differences between transport networklayer messages within the RNC.

The transport subsystem terminates transport network layer messages at the interface boards.Then, according to the configuration transfer table, the subsystem transfers user plane, controlplane, and management plane datagrams to the DPUb and SPUa boards in the RNC forprocessing.

3.3.2 Components of the RNC Transport SubsystemThe RNC transport subsystem consists of the transmission interface boards.

The RNC provides the following interface boards:l ATM interface boards:

– AEUa Board

– AOUa Board



3-7

– UOIa Board (UOI_ATM)

l IP interface boards:– FG2a Board

– GOUa Board

– PEUa Board

– POUa Board

– UOIa Board (UOI_IP)

NOTE

The UOI_ATM is the UOIa board used in ATM transport. The UOI_IP is the UOIa board used in IPtransport.

The RNC transport subsystem enables the processing of ATM and IP data through ATM and IPinterface boards respectively.

3.4 RNC OM SubsystemThe RNC OM subsystem is responsible for the operation and maintenance of the RNC.

3.4.1 Components of the RNC OM SubsystemThe RNC OM subsystem consists of the LMT, OMUa boards, SCUa boards, and OM moduleson other boards.

3.4.2 Working Principles of the RNC OM SubsystemThe RNC OM subsystem works in dual-plane mode through the OM network of the RNC.

3.4.3 RNC OM FunctionsThe RNC OM functions enable routine and emergency maintenance of the RNC.

3.4.4 RNC Active/Standby WorkspacesRNC active/standby workspaces consist of active/standby workspaces of the BAM and those ofFAM boards.

3.4.5 RNC Security ManagementRNC security management consists of authority management, operator information protection,File Transfer Protocol (FTP) transmission based on ciphering, and encryption of thecommunication interface between the RNC and the Element Management System (EMS).

3.4.6 RNC Log ManagementRNC log management enables you to query the information about the operation and running ofthe RNC, thus facilitating fault analysis and identification.

3.4.7 RNC Configuration ManagementRNC configuration management enables configuration and management of RNC data on theOM console (LMT or M2000).

3.4.8 RNC Performance ManagementRNC performance management enables the RNC to collect performance data.

3.4.9 RNC Alarm ManagementRNC alarm management facilitates you to monitor the running state of the RNC and informsyou of faults in real time so that you can take measures in time.

3.4.10 RNC Loading Management


Product Description


Issue 03 (2008-08-30)

RNC loading management enables you to manage the process of loading program and data filesonto boards after the FAM boards (or subracks) start or restart.

3.4.11 BOOTP and DHCP on the Iub InterfaceThe RNC and NodeB support the BOOTP and DHCP functions. By the BOOTP or DHCPfunction, a NodeB can automatically get an IP address from an RNC and create an OM channelbetween the NodeB and the RNC. The BOOTP and DHCP functions are applicable to ATM andIP transport on the Iub interface respectively.

3.4.12 RNC Upgrade ManagementRNC upgrade refers to a process where the RNC is upgraded to a later version.

3.4.1 Components of the RNC OM SubsystemThe RNC OM subsystem consists of the LMT, OMUa boards, SCUa boards, and OM moduleson other boards.

Figure 3-4 shows the components and physical connections of the RNC OM subsystem.

Figure 3-4 Components and physical connections of the RNC OM subsystem

NOTE

The RNC OM subsystem covers relevant modules on all boards of the RNC. Figure 3-4 shows only someof the boards.

LMT

The LMT is a computer installed with Huawei Local Maintenance Terminal software. It runsunder the Windows XP Professional operating system. The RNC can be configured with one ormore LMTs. The LMT is connected to the OMUa directly or through the hub and to the alarmbox through a serial cable.



3-9

OMUa BoardThe OMUa board is the Back Administration Module (BAM) of the RNC. The OMUa boardsare connected to external devices through Ethernet cables.

The OMUa board serves as a bridge between Front Administration Module (FAM) and BAMof the RNC. Based on the OMUa board, the OM network of the RNC is divided into the followingnetworks:l Internal network: serves the communication between the OMUa and the RNC host.

l External network: serves the communication between the OMUa board and the externaldevice, such as the OM terminal LMT or M2000.

NOTE

The RNC can be configured with one or two OMUa boards. In the latter case, the two boards work inactive/standby mode.

SCUa BoardThe SCUa is the switching and control board of the RNC. It is responsible for OM of its housingRSS subrack or RBS subrack. A subrack can be configured with two SCUa boards. In this case,the two boards work in active/standby mode.

The SCUa board performs OM on other boards in the same subrack through the backplanechannels. The SCUa boards in the RSS are connected to the SCUa boards in the RBSs throughEthernet cables.

NOTE

For details about the switching function of the SCUa board, refer to 3.1.2 Components of the RNCSwitching Subsystem.

3.4.2 Working Principles of the RNC OM SubsystemThe RNC OM subsystem works in dual-plane mode through the OM network of the RNC.

3.4.2.1 RNC OM SubnetsThe RNC OM network is divided into the external network, internal network, RSS network,RSS-RBS network, and RBS network. Each subnet is responsible for certain functions.

3.4.2.2 RNC OM Dual PlanesThe RNC adopts the OM dual-plane design to guarantee proper operation and maintenance inthe case of single-point failure.

RNC OM SubnetsThe RNC OM network is divided into the external network, internal network, RSS network,RSS-RBS network, and RBS network. Each subnet is responsible for certain functions.

Figure 3-5 shows the structure of the RNC OM subsystem.


Product Description


Issue 03 (2008-08-30)

Figure 3-5 Structure of the RNC OM subsystem

NOTE

The RINT in the figure refers to the Iu/Iur/Iub interface board. You can choose to use different interfaceboards based on the requirements.

External NetworkThe external network refers to the network between the OMUa board and the OM console (LMTor M2000). The external network provides the interface for the OM console to access the OMsubsystem.

Internal NetworkThe internal network refers to the network between the OMUa board and the SCUa board in theRSS subrack. The internal network provides a bridge for the communication between the OMUaand the FAM.

RSS NetworkThe RSS network refers to the OM network between the SCUa board in the RSS subrack andthe other boards in the same subrack. The backplane in the RSS subrack is used to connectentities on this network.



3-11

RSS-RBS NetworkThe RSS-RBS network refers to the network between the SCUa board in the RSS subrack andthe SCUa in each RBS subrack. The connections between the SCUa board in the RSS subrackand the SCUa board in each RBS subrack through Ethernet cables comprise the RSS-RBSnetwork.

Through this network, the RNC can transmit the OM information to the SCUa board in eachRBS subrack through the SCUa board in the RSS subrack.

RBS NetworkThe RBS network refers to the OM network between the SCUa board in an RBS subrack andthe other boards in the same subrack. The backplane in the RBS subrack is used to connectentities on this network.

RNC OM Dual PlanesThe RNC adopts the OM dual-plane design to guarantee proper operation and maintenance inthe case of single-point failure.

The RNC OM subsystem adopts the dual-plane design, as shown in Figure 3-6.

Figure 3-6 OM dual planes

This design is realized by the hardware that works in redundancy mode. When the active part isfaulty but the standby part works properly, the active and standby parts can be switched overautomatically to guarantee proper working of the OM channel. The involved hardware is asfollows:l Active/Standby OMUa boards (if two OMUa boards are configured)


Product Description


Issue 03 (2008-08-30)

l Active/Standby SCUa boards in the RSS subrack

l Active/Standby SCUa boards in an RBS subrack

The active/standby OMUa boards use one external virtual IP address when communicating withthe LMT or M2000 and use one internal virtual IP address when communicating with the SCUaboard. As shown in Figure 3-6, if the active OMUa board fails but the standby one worksproperly, the active and standby OMUa boards are switched over automatically. The standbyOMUa board takes the role of the active OMUa board to perform OM for the RNC. The internaland external virtual IP addresses remain unchanged. Thus, the proper communication betweenthe internal and external networks of the RNC is guaranteed.

3.4.3 RNC OM FunctionsThe RNC OM functions enable routine and emergency maintenance of the RNC.

The RNC has powerful OM functions, including security management, log management,configuration management, performance management, alarm management, message tracing,loading management, and upgrade management.

The OM software of the RNC can perform all-round management and maintenance of the RNC.

3.4.4 RNC Active/Standby WorkspacesRNC active/standby workspaces consist of active/standby workspaces of the BAM and those ofFAM boards.

3.4.4.1 Active/Standby Workspaces of the BAMThe active/standby workspaces of the BAM, that is, active/standby workspaces of the OMUaboard, are applied to upgrade and rollback of BAM and RNC versions, thus enabling quickswitching between versions.

3.4.4.2 Active/Standby Workspaces of RNC FAM BoardsRNC FAM boards refer to all the boards except the OMUa board. The active/standby workspacesof FAM boards are applied to file loading for the FAM boards, thus speeding up version upgradeand rollback.

Active/Standby Workspaces of the BAM

The active/standby workspaces of the BAM, that is, active/standby workspaces of the OMUaboard, are applied to upgrade and rollback of BAM and RNC versions, thus enabling quickswitching between versions.

Concept of BAM Active/Standby Workspaces

The active/standby workspaces of the BAM refer to the active and standby workspaces in theBAM divided to store different version files.

The active/standby workspaces are a relative concept. The active/standby relationship dependson the running version. The workspace that stores the running BAM version files is the activeworkspace, and the other is the standby workspace.

Working Principle of BAM Active/Standby Workspaces

The BAM version upgrade process is as follows:



3-13

1. The standby workspace of the active BAM is upgraded to a new version.2. The standby workspace of the standby BAM is synchronized with the standby workspace

of the active BAM.3. The active and standby workspaces of the active BAM switch over. The standby workspace

that stores the new version of files becomes active, and the other workspace becomesstandby.

4. The active BAM runs the upgraded version.5. The active and standby workspaces of the standby BAM switch over to ensure that the

versions of the workspaces are consistent with those of the active BAM.6. The BAM version upgrade ends.

After the BAM version is upgraded, it can be rolled back as required. The version rollbackprocess is as follows:

1. The active and standby workspaces of the active BAM switch over. The running versionof the active BAM is rolled back to the pre-upgrade version.

2. The active BAM runs the pre-upgrade version.3. The active and standby workspaces of the standby BAM switch over to ensure that the

versions of the workspaces are consistent with those of the active BAM.4. The BAM version rollback ends.

CAUTIONDuring the switchover between the BAM active and standby workspaces, the OM of the BAMis interrupted for about one minute.

Relationship Between Intra-BAM Active and Standby WorkspacesThe active workspace of the BAM is independent of the standby workspace, or the other wayround. The operations in the active workspace do not change any information in the standbyworkspace.

Relationship Between Inter-BAM Active and Standby WorkspacesThe active and standby workspaces of the active BAM correspond to the active and standbyworkspaces of the standby BAM respectively. Between the active and standby BAMs, the filesin the active workspaces are automatically synchronized in real time, but those in the standbyworkspaces need to be synchronized manually through an MML command.

NOTE

The SYN BAMAREA command can be used to manually synchronize the standby workspaces betweenthe active and standby BAMs.

Relationship Between the Active/Standby Workspaces of FAM Boards and theActive/Standby Workspaces of the BAM

On the active workspaces of the FAM boards, files can be loaded from only the active workspaceof the BAM. On the standby workspaces of the FAM boards, files can be loaded from only thestandby workspace of the BAM. When the FAM boards are loaded, the active and standby


Product Description


Issue 03 (2008-08-30)

workspaces of the FAM boards can be synchronized with the active and standby workspaces ofthe BAM respectively.

NOTE

l Run the SYN BRDAREA command, and then you can manually synchronize the active and standbyworkspaces of FAM boards with those of the BAM.

l Run the LOD BRD command, and you can forcibly load program files and data files of FAM boardsfrom the BAM and write the program files and data files to the active or standby workspaces of FAMboards.

Active/Standby Workspaces of RNC FAM BoardsRNC FAM boards refer to all the boards except the OMUa board. The active/standby workspacesof FAM boards are applied to file loading for the FAM boards, thus speeding up version upgradeand rollback.

Concept of FAM Board Active/Standby WorkspacesThe active/standby workspaces of FAM boards refer to the active and standby workspaces inthe board flash memory divided to store program, data, and patch files for different versions.

The active/standby workspaces are a relative concept. The active/standby relationship dependson the running version. The workspace that stores the running version files of a board is theactive workspace, and the other is the standby workspace.

Working Principles of FAM Board Active/Standby WorkspacesBefore loading program and data files, FAM boards choose the loading mode according to theloading control parameter. In the negotiation mode, to negotiate the loading mode for programfiles, the RNC compares the versions of the program files stored in the active and standbyworkspaces of FAM boards with the versions of current program files in the BAM. To negotiatethe loading mode for data files, the RNC compares the Cyclic Redundancy Check (CRC) valueof the data files in the active workspace of FAM boards with that in the BAM. For details aboutloading RNC FAM boards, refer to 3.4.10 RNC Loading Management.

Relationship Between Intra-Board Active and Standby WorkspacesThe active workspace of a FAM board is independent of the standby workspace of the sameboard, or the other way round. The operations in the active workspace do not change anyinformation in the standby workspace.

Relationship Between Inter-Board Active and Standby WorkspacesThe active and standby workspaces of an active FAM board are independent of those of theassociated standby FAM board, or the other way round. The operations in the workspaces of theactive board do not change any information in the workspaces of the standby board.

Relationship Between the Active/Standby Workspaces of FAM Boards and theActive/Standby Workspaces of the BAM

On the active workspaces of the FAM boards, files can be loaded from only the active workspaceof the BAM. On the standby workspaces of the FAM boards, files can be loaded from only thestandby workspace of the BAM. When the FAM boards are loaded, the active and standby



3-15

workspaces of the FAM boards can be synchronized with the active and standby workspaces ofthe BAM respectively.

NOTE

l Run the SYN BRDAREA command, and then you can manually synchronize the active and standbyworkspaces of FAM boards with those of the BAM.

l Run the LOD BRD command, and you can forcibly load program files and data files of FAM boardsfrom the BAM and write the program files and data files to the active or standby workspaces of FAMboards.

3.4.5 RNC Security ManagementRNC security management consists of authority management, operator information protection,File Transfer Protocol (FTP) transmission based on ciphering, and encryption of thecommunication interface between the RNC and the Element Management System (EMS).

Authority ManagementRNC authority management is performed to identify the user and define the authority of the user.

The RNC supports multi-user operation. It performs hierarchical authority management for usersto ensure security. In this mode, the RNC provides multiple authority levels, each of which isconfigured for a type of operator. To log in to the RNC OM subsystem through the LMT, a usermust enter the correct user name and password, through which the RNC identifies the user.

The users of the RNC are of the two types: local user and EMS user. For details, refer to RNCLMT User Types.

The RNC provides 32 command groups: G_0 to G_31. Each command group contains severalMML commands or binary commands. For details, refer to RNC Command Groups.

Operator Information ProtectionIf no operation is performed for a certain period, the user interface is automatically locked.

FTP Transmission Based on CipheringThis ensures the security of FTP transmission.

Encryption of the Communication Interface Between RNC and EMSThe RNC uses the Security Socket Layer (SSL) protocol to fulfill transmission of ciphertextover the OM channel between the RNC and the EMS. This ensures data security.

3.4.6 RNC Log ManagementRNC log management enables you to query the information about the operation and running ofthe RNC, thus facilitating fault analysis and identification.

The logs of the RNC are of three types: operation logs, running logs, and security logs.

Operation LogOperation logs refer to the operation data saved in the BAM database in real time. The logmanagement module in the BAM records all the operations performed on the RNC. It supportsacquisition and deletion of logs.


Product Description


Issue 03 (2008-08-30)

Running LogRunning log refers to the information recorded in the RNC about the running of the RNC host.

Security Log

Security log refers to security-related events recorded in the RNC. These events include userlogin, user management, and user authentication.

Cell Log

A cell log records the cell procedure information, which, in case of cell abnormality, is exportedto the log files for problem identification.

3.4.7 RNC Configuration ManagementRNC configuration management enables configuration and management of RNC data on theOM console (LMT or M2000).

3.4.7.1 RNC Online and Offline StatesThe RNC can be in either online or offline data configuration mode.

3.4.7.2 RNC Data Configuration ModesThe RNC supports three data configuration modes: online configuration, offline configuration,and dynamic batch configuration.

3.4.7.3 RNC Data Configuration Right ManagementRNC data configuration right management enables only one user to perform RNC dataconfiguration on only one configuration console at a time. The configuration console may bethe LMT or the M2000.

3.4.7.4 RNC Data Configuration RollbackRNC data configuration rollback is performed to restore configurations when errors occur. Ifdata configuration fails to achieve the expected result or even causes equipment or networkfaults, you can perform rollback to restore the configurations quickly. This ensures the properrunning of the RNC.

3.4.7.5 RNC Data Consistency CheckRNC data consistency check ensures consistency between the data in the BAM and that in theFAM. Data inconsistency between BAM and FAM affects the stable running of the RNC. Datainconsistency also leads to a scenario wherein a part of data configuration on the LMT does nottake effect at the host.

RNC Online and Offline States

The RNC can be in either online or offline data configuration mode.

RNC Online Mode

If data configuration is performed on the RNC in online state, the relevant configuration datacan take effect in the FAM in real time.

When the RNC is online, you can adopt the online data configuration mode. For details aboutthe mode, refer to 3.4.7.2 RNC Data Configuration Modes.



3-17

RNC Offline Mode

If data configuration is performed on the RNC in offline state, the relevant configuration datacan take effect only after the RNC is reset or switched to online state.

When the RNC is offline, you can adopt the offline data configuration and dynamic batchconfiguration modes. For details about the modes, refer to 3.4.7.2 RNC Data ConfigurationModes.

RNC Online Configuration Commands

When the RNC is online, you can run all the configuration commands except those describedin Table 3-1.

Table 3-1 RNC offline configuration commands

Run... To...

ADD RNCBASIC Add the basic information of the RNC.

MOD SUBRACK Modify the name of the subrack.

ADD OPC Add an originating signaling point.

MOD OPC Modify an originating signaling point.

MOD N7DPC Modify a destination signaling point.

RMV OPC Remove an originating signaling point.

SET SUBNET Set the number of the subnet of the RNC.

SET SCTPSRVPORT Set the service listening ports on the SCTP server.

NOTE

The commands described in Table 3-1 are executable only in offline state.

RNC Offline Configuration Commands

All the configuration commands are executable when the RNC is offline.

RNC Data Configuration Modes

The RNC supports three data configuration modes: online configuration, offline configuration,and dynamic batch configuration.

RNC Online Configuration

RNC online configuration can be performed only when the RNC is online. Such dataconfiguration is mainly applicable to dynamic configuration of RNC data.

Figure 3-7 shows the process of RNC online configuration.


Product Description


Issue 03 (2008-08-30)

Figure 3-7 Process of RNC online configuration

The process of RNC online configuration is as follows:

1. The RNC is switched to online state.2. The configuration console (LMT or M2000) sends MML commands to the configuration

management module of the BAM.3. The configuration management module sends the configuration data to the database of the

related FAM board and writes the data to the BAM database DB.

RNC Offline ConfigurationRNC offline configuration can be performed only when the RNC is offline. Such dataconfiguration is mainly applicable to RNC initial configuration.

Figure 3-8 shows the process of RNC offline configuration.

Figure 3-8 Process of RNC offline configuration

The process of RNC offline configuration is as follows:

1. The RNC is switched to offline state.2. The configuration console (LMT or M2000) sends MML commands to the configuration

management module of the BAM.3. The configuration management module only sends the configuration data to the BAM

database DB.4. When a subrack or the RNC is reset, the BAM formats the configuration data in the DB

into a .dat file, loads the file onto the relevant FAM boards, and validates the configurationdata.

NOTE

During RNC offline configuration, you can start the quick configuration mode to improve efficiency.



3-19

RNC Dynamic Batch Configuration

RNC dynamic batch configuration can be performed only when the RNC is offline. Such dataconfiguration is mainly applicable to RNC capacity expansion and NodeB reparent.

Figure 3-9 shows the process of RNC dynamic batch configuration.

Figure 3-9 Process of RNC dynamic batch configuration

The process of RNC dynamic batch configuration is as follows:

1. The RNC is switched to offline mode and dynamic batch configuration is enabled.

2. The configuration console (LMT or M2000) sends MML commands to the configurationmanagement module of the BAM.

3. The configuration management module sends the configuration data only to the BAMdatabase DB.

4. When the RNC is switched to online state and immediate validation of configuration datais enabled, the BAM sends the configuration data in the DB to the relevant FAM boardsand validates the data.

NOTE

Offline configuration commands cannot be run in dynamic batch configuration mode.

RNC Data Configuration Right Management

RNC data configuration right management enables only one user to perform RNC dataconfiguration on only one configuration console at a time. The configuration console may bethe LMT or the M2000.

In case of conflicts during data configuration, the BAM manages the configuration right asfollows:

l When the data configuration right control switch is ON, only one user has the dataconfiguration right at a time. When the switch is OFF, no data configuration right controlis applicable. You can run the SET CMCTRLSW command to set the switch to ON orOFF.

l Before data configuration, the data configuration right must be obtained. The dataconfiguration right is always occupied unless the user manually releases the right. That is,if the user is logged out and the right is not manually released, he or she can still has thedata configuration right at the next login. The ADMINISTRATOR-level operators,however, can obtain the data configuration right by running the FOC CMCTRL command.


Product Description


Issue 03 (2008-08-30)

With the control, different users cannot configure data for the RNC at the same time. A user canperform data configuration for the RNC only after the user is granted the data configurationright.

RNC Data Configuration Rollback

RNC data configuration rollback is performed to restore configurations when errors occur. Ifdata configuration fails to achieve the expected result or even causes equipment or networkfaults, you can perform rollback to restore the configurations quickly. This ensures the properrunning of the RNC.

Definition of Configuration Rollback

During data configuration, a rollback point is used to identify a data configuration status.Rollback points can be set by users or automatically allocated by the RNC.

Configuration rollback: By setting data configuration status to rollback points, the user canflexibly roll back or forward to any rollback point during the configuration, so as to roll back orforward to the expected data configuration status.

Operations of Configuration Rollback

Configuration rollback is applicable when the data configuration right control switch is ON. Youcan run the SET CMCTRLSW command to set the switch to ON.

RNC data configuration rollback consists of the following types of operation:

l Undoing a single configuration command: After undoing the command, the RNC rolls backto the configuration state that existed before the relevant command was run. This operationis applicable to only the previous ten configuration commands.

l Redoing a single configuration command: After redoing the command, the RNC returns tothe configuration state that existed after the relevant command was run. This operation isapplicable to only the previous ten configuration commands that were rolled back.

l Undoing configuration commands in batches: This operation is performed to undo all theconfiguration commands that were run after a specified rollback point. After the undoing,the RNC rolls back to the configuration of the specified rollback point.

l Redoing configuration commands in batches: This operation is performed to redo theconfigurations that were rolled back in batches. After the redoing, the RNC returns to eitherthe configuration of the specified rollback point or the configuration that existed before theundoing was performed.

RNC Data Consistency Check

RNC data consistency check ensures consistency between the data in the BAM and that in theFAM. Data inconsistency between BAM and FAM affects the stable running of the RNC. Datainconsistency also leads to a scenario wherein a part of data configuration on the LMT does nottake effect at the host.

RNC data consistency check can be initiated by an operator through the LMT, or it can beinitiated periodically by the MML Server module of the BAM through the configuration on theLMT. This task checks the data consistency between the BAM database and the databases ofFAM boards. The fundamental unit for the data consistency check is table records.



3-21

3.4.8 RNC Performance ManagementRNC performance management enables the RNC to collect performance data.

RNC Performance Management ProcessThe boards of the RNC collect performance measurement data and periodically report the datato the performance management module of the BAM. According to the task file, the performancemanagement module reports the measurement data to the M2000 periodically. The BAM storesthe performance measurement data generated in the last 168 hours, by deleting the earlierrecords.

Figure 3-10 shows the process of performance measurement.

Figure 3-10 Process of performance measurement

In the performance measurement process, the performance console on the M2000 controls theBAM to collect measurement data, based on a default measurement task file that is in .xmlformat. According to the task file, the RNC reports the measurement data at the granularityperiod of the measurement unit.

Measurement TypesPerformance measurement objects are of two types: default measurement objects and optionalmeasurement objects.l Default measurement objects

The RNC automatically measures all objects of this type. The default measurement taskfile supports dual periods. One is the normal measurement period with a default durationof 30 minutes. The other is the short measurement period with a default duration of fiveminutes. The latter one is used for real-time Key Performance Indicator (KPI) monitoring.The M2000 cannot add objects to the list of default measurement objects or remove objectsfrom the list.

l Optional measurement objectsBy default, the RNC does not measure the objects of this type. The purpose of defining thisobject type is to avoid measuring these objects, which are of a large quantity, every time.The M2000 can add objects to the list of optional measurement objects or remove objectsfrom the list.

3.4.9 RNC Alarm ManagementRNC alarm management facilitates you to monitor the running state of the RNC and informsyou of faults in real time so that you can take measures in time.


Product Description


Issue 03 (2008-08-30)

RNC Alarm Management Function

RNC alarm management covers the following functions:l Setting the storage capacity and generation period for alarm logs

The RNC can store the information of the alarms generated in the last 90 days and amaximum of 100,000 alarm logs. You can set the storage capacity and log generation periodas required.

l Setting alarm levelsThe RNC has the alarm level setting function. You can set a level for a specific alarm object.

l Masking alarms of certain objectsThe RNC can mask specific alarm objects. The alarms that satisfy the masking conditionsare masked, that is, they are not reported to the alarm console.

l Masking derivative alarmsThe RNC can mask derivative alarms, that is, the derivative alarms are not reported to thealarm console.

l Alarm indicationWhen a fault alarm is generated, the RNC informs you of the alarm in any of the followingways: blinking of the icon, audible indication of the terminal, and audible and visibleindication on the alarm box.

l Alarm information processingYou can browse real-time alarm information, query history alarm information, and handlealarms based on the handling suggestions available from the Online Help of the RNC.

RNC Alarm Management Mechanism

The alarm management process consists of alarm generation, alarm reporting, and alarmhandling. Figure 3-11 shows the process of alarm management.

Figure 3-11 Process of alarm management

Each board automatically detects alarms and reports the alarms to the BAM in acknowledgedmode.

The Warn module of the BAM has the following functions:l Alarm storage

The module stores the alarms in the database DB of the BAM.l Alarm processing



3-23

The module processes the commands sent from the alarm console and sends the responsesto the alarm console. The commands can be used to query active alarms or alarm logs orto modify alarm configurations.

RNC Alarm Box Driving

The RNC uses the universal alarm box of Huawei. The alarm box provides audible and visibleindications of alarms. For appearance and functions of the alarm box, refer to RNC AlarmBox.

Figure 3-12 shows the process of driving the alarm box.

Figure 3-12 Process of driving the RNC alarm box

The alarm box is connected to the LMT through the serial port. When an alarm is reported, theLMT transfers it to the alarm box. The alarm box then emits audible and visible indications.

NOTE

The RNC can control alarm reporting by the alarm box. Through settings on the alarm box, the RNC canmask specified alarm objects and all the alarms under the specified alarm level.

3.4.10 RNC Loading ManagementRNC loading management enables you to manage the process of loading program and data filesonto boards after the FAM boards (or subracks) start or restart.

RNC Files to Be Loaded

RNC files to be loaded include the program files and data files, which are stored in the directoryBAM active workspace installation directory\LoadData on the BAM. The program files havethe extension of .bin and the data files have the extension of .DAT.l All the boards of the RNC must be loaded with program files.

l The SCUa and SPUa boards must be loaded with data files, in addition to program files.

Table 3-2 lists the names of the program files of RNC boards.

Table 3-2 Program file names of RNC boards

Board/Subsystem Program File Name

SCUa board SCU00000.bin

MPU subsystem MPU00000.bin

SPU subsystem SPU00000.bin

GCUa/GCGa board GCU00000.bin


Product Description


Issue 03 (2008-08-30)

Board/Subsystem Program File Name

DPUb board DPU00000.bin

AEUa board AEU00000.bin

AOUa board AOU00000.bin

PEUa board PEU00000.bin

POUa board POU00000.bin

UOIa board (UOI_ATM) UOI00000.bin

UOIa board (UOI_IP) POS00000.bin

FG2a/GOUa board FG200000.bin

The data file names of an SCUa board or SPUa board are in the form of ABCXXYYZ.DAT.Table 3-3 describes the detailed meaning of the data file names.

Table 3-3 Description of the data file names

Parameter Meaning

ABC Board name or subsystem namel For an SCUa board, the content of ABC is

SCU.l For subsystem 0 on a controlling SPUa

board, the content of ABC is MPU.l For a non-controlling SPUa board and

subsystems 1, 2, and 3 on a controllingSPUa board, the content of ABC is SPU.

XX Subrack number

YY Slot number

Z Subsystem numberZ is valid only for an SPUa board. For anSCUa board, the value of Z is 0.

For example, SPU00040.DAT is the file name of the data file in SPU subsystem 0 on the SPUaboard in slot 4 of subrack 0; MPU05000.DAT is the file name of the data file in SPU subsystem0 on the SPUa board in slot 0 of subrack 5.

RNC Loading ModesYou can use the SET LODCTRL command to set the loading control parameter to specify theloading mode.

The following loading modes are applicable to RNC program and data files:



3-25

l Always loading from the BAM and writing to the flash memory of the board

NOTE

This mode is mainly applicable to loading patches.

l Negotiated loading

Negotiated LoadingThe loading of program files and that of data files differ in terms of the negotiation mode.

To negotiate the loading mode for program files, the RNC compares the versions of the programfiles stored in the active and standby workspaces of the flash memory of a board with the versionsof current program files in the BAM.l If the versions are inconsistent, the board loads program files from the BAM and writes the

files to the active workspace of the flash memory of the board.l If the versions are consistent, the board loads program files directly from the active or

standby workspace of the flash memory of the board.

NOTE

If the board loads program files from the standby workspace of the flash memory, the standby workspaceswitches to be active automatically, and the other workspace becomes standby.

To negotiate the loading mode for data files, the RNC compares the Cyclic Redundancy Check(CRC) value of the data files in the active workspace of the flash memory of a board with thatin the active workspace of the BAM.l If the CRC values are inconsistent, the board loads data files from the active workspace of

the BAM and writes the files to the active workspace of the flash memory of the board.l If the CRC values are consistent, the board loads data files directly from the active

workspace of the flash memory of the board.

NOTE

If a board fails to load program or data files from the flash memory after negotiation, the board loads thefiles from the BAM and writes the files to the flash memory.

Process of Loading RNC Program FilesFigure 3-13 shows the process of loading RNC program files. During the loading process, theRNC loads the SCUa boards in the RSS and RBSs before loading the other boards in the subracks.


Product Description


Issue 03 (2008-08-30)

Figure 3-13 Process of loading RNC program files

The process of loading RNC program files is as follows:

1. After starting up, the RNC boards broadcast BOOTP request messages to the BAM.2. After receiving the BOOTP request message from the SCUa, the BAM generates a BOOTP

response message and sends it to the SCUa board. The response message contains theloading control parameter, IP address, and version information.

3. The SCUa board receives the response message and then loads the program files accordingto the loading control parameter.

4. After the loading, the SCUa board forwards the BOOTP request messages of other boardsin the subrack to the BAM.

5. On receiving the BOOTP request messages from other boards, the BAM returns to theboards response messages, through the SCUa board.

6. The boards receive the response messages and then load the program files according to theloading control parameter.

7. The loading of RNC program files ends.

Process of Loading RNC Data FilesRNC data files are loaded after RNC program files are loaded. Figure 3-14 shows the processof loading RNC data files.



3-27

Figure 3-14 Process of loading RNC data files

The process of loading RNC data files is as follows:

1. After the RNC program files are loaded, the SCUa board loads the data files according tothe loading control parameter.

2. After the SCUa board finishes loading the data files, the SPUa board loads the data filesaccording to the loading control parameter.

3. The loading of RNC data files ends.

3.4.11 BOOTP and DHCP on the Iub InterfaceThe RNC and NodeB support the BOOTP and DHCP functions. By the BOOTP or DHCPfunction, a NodeB can automatically get an IP address from an RNC and create an OM channelbetween the NodeB and the RNC. The BOOTP and DHCP functions are applicable to ATM andIP transport on the Iub interface respectively.

Concept of BOOTP and DHCPThe Bootstrap Protocol (BOOTP) is usually used to boot diskless workstations.

In a TCP/IP network, DHCP provides configuration information for hosts on the Internet. DHCPis based on BOOTP. DHCP retains the relay function as provided by BOOTP and adds thecapability of automatic allocation of reusable network addresses and additional configurationoptions.

NOTE

Currently, the Iub interface is applied with static IP address allocation of DHCP instead of dynamicallocation of IP addresses.

BOOTP is similar to the Dynamic Host Configuration Protocol (DHCP), but the former can beimplemented more easily than the latter.

Working Mechanisms of BOOTP and DHCPBOOTP and DHCP work in client/server mode. The client applies towards the server forconfiguration parameters, including the requested IP address, subnet mask, and default gateway.


Product Description


Issue 03 (2008-08-30)

The server responds with relevant configuration information according to certain strategy. Theresponse messages are encapsulated by UDP.

NOTE

l DHCP is extended from BOOTP. A DHCP server can interoperate with a BOOTP client.

l In a RAN system, an RNC acts as a server and a NodeB acts as a client.

The UDP port number of the BOOTP/DHCP client is 68, and that of the BOOTP/DHCP serveris 67. BOOTP and DHCP are applicable to only the scenario where the client and the server arelocated in the same subnet. When the client and the server are located in different subnets, theDHCP/BOOTP relay is required in the subnet where the client resides. The DHCP/BOOTP relaycan be implemented by an Internet host or a router.

A BOOTP signaling procedure includes interaction of only a request and a response. Thesignaling interaction of DHCP is more complicated than that of BOOTP.

NOTE

l The DHCP server can receive at least the following datagrams from the client: DHCPDISCOVER,DHCPREQUEST, DHCPDECLINE, DHCPRELEASE, and DHCPINFORM.

l The DHCP client can receive at least the following datagrams from the server: DHCPOFFER,DHCPACK, and DHCPNAK.

Benefits of BOOTP and DHCPl In the case that the OM channel between the RNC and the NodeB is broken, BOOTP and

DHCP enable the channel to be automatically repaired.l BOOTP and DHCP reduce the necessity for local NodeB maintenance, thus increasing

maintainability of NodeBs and reducing the operation costs.

3.4.12 RNC Upgrade ManagementRNC upgrade refers to a process where the RNC is upgraded to a later version.

Upgrade ScenariosThe RNC may be developed to support new features, higher specifications, or later protocolstandards, or to have defects remedied. In such cases, an RNC needs to be upgraded to a laterversion so that it can provide better services.

Upgrade ModeThe RNC upgrade adopts the remote mode. You can use the dedicated upgrade tool to upgradean RNC remotely through the OM network of the RNC. Figure 3-15 shows the RNC remoteupgrade.

Figure 3-15 RNC remote upgrade



3-29

NOTE

The upgrade tool supports batch upgrade for RNCs.

Upgrade ToolThe RNC is upgraded remotely by the dedicated upgrade tool, which consists of the upgradeclient and the upgrade server. The upgrade tool has the following functions:l Checking data before upgrade: checks the BAM operating system, database, BAM

application, and user-input data.l Upgrading the BAM: upgrades the BAM application and data files.

l Upgrading host boards: upgrades loading program and data files of the RSS and RBSsubracks.

l Providing three types of upgrade: version upgrade, patch upgrade, and version+patchupgrade.

Methods of obtaining the RNC upgrade client: The upgrade client is released with associatedversions of the BAM application. For example, if the version number of the released BAMapplication is V200R010C01B061, the upgrade client is stored in the directoryV200R010C01B061\RemoteClient.

Process of Remote UpgradeThe remote upgrade process is as follows:

1. The user sends the version files required for the upgrade and the upgrade server programto the specified directories of the active and standby BAM through the upgrade network.

2. The user starts the upgrade client at the local end and sets up connection between theupgrade client and the upgrade server.

3. The user uses the upgrade client to remotely start the upgrade server.4. The upgrade server backs up the data in the active workspace of the active BAM before

the upgrade.5. The upgrade server upgrades the program and data files in the standby workspace of the

active BAM.6. The upgrade server issues a command to synchronize the standby workspace of the standby

BAM and that of the active BAM.7. The upgrade server issues a command to load the host program, DSP, BOOTROM, and

data files in the standby workspaces of the BAMs onto the standby workspaces of the boardsso that the standby workspaces of the boards are synchronized with those of the BAMs.

8. The upgrade server issues a command to switch over the active and standby workspacesof the active BAM so as to upgrade the active BAM.

9. The upgrade server issues a command to reset all the boards of the RNC.10. After the reset, the RNC boards negotiate the loading of version files with the BAMs. The

boards automatically load the program and data files from the standby workspaces of theirflash memories to upgrade the boards.

11. The upgrade server prompts the user to verify services.12. After the service verification is passed, the upgrade server issues a command to switch over

the active and standby workspaces of the standby BAM so as to upgrade the standby BAM.13. The RNC upgrade ends.


Product Description


Issue 03 (2008-08-30)

NOTE

The methods of remotely upgrading the RNC through the upgrade tool differ with the different versions.Therefore, for detailed upgrade operations, refer to the upgrade guide released with the associated versions.

3.5 RNC Clock Synchronization SubsystemThe RNC clock synchronization subsystem consists of the GCUa/GCGa boards in the RSSsubrack and the clock processing unit of each subrack. It provides timing signals for the RNC,generates the RFN, and provides reference clocks for NodeBs.

3.5.1 RNC Clock SourcesThe RNC has the following clock sources: Building Integrated Timing Supply System (BITS)clock, Global Positioning System (GPS) clock, line clock, and external 8 kHz clock.

3.5.2 Structure of the RNC Clock Synchronization SubsystemThe RNC clock synchronization subsystem consists of the clock module and other boards. Theclock module is implemented by the GCUa/GCGa board.

3.5.3 Timing Signal Processing in the RNCThe RNC processes foreign timing signals before sends the timing signals to the boards.

3.5.4 RFN Generation and ReceptionRNC Frame Number (RFN) is applicable to node synchronization for the RNC. The nodesynchronization frames that the RNC sends to the NodeB carry the RFN signals.

3.5.1 RNC Clock SourcesThe RNC has the following clock sources: Building Integrated Timing Supply System (BITS)clock, Global Positioning System (GPS) clock, line clock, and external 8 kHz clock.

BITS ClockThe BITS clock is of three types: 2 MHz, 2 Mbit/s, and 1.5 Mbit/s. The BITS clock has twoinput modes: BITS 1 and BITS 2. The RNC obtains the BITS timing signals through the timingsignal input ports on the GCUa/GCGa board.

NOTE

The 2 MHz and 2 Mbit/s timing signals are E1 timing signals, and the 1.5 Mbit/s timing signals are T1timing signals.

GPS ClockThe GPS clock provides 1 Pulse Per Second (PPS) timing signals. The RNC obtains the GPStiming signals from the GPS system. The GCGa board is configured with a GPS card, and theRNC receives the GPS signals at the ANT port on the GCGa.

NOTE

The GCUa board is not configured with a GPS card. Therefore, when the RNC is configured with the GCUainstead of the GCGa, the GPS clock is unavailable to the RNC.

Line ClockThe line clock is an 8 kHz clock that the Iu interface board in the RSS subrack provides for theGCUa/GCGa board through the backplane channels. The line clock has two input modes: line1 and line 2.



3-31

External 8 kHz Clock

Through the COM1 port on the GCUa/GCGa board, the RNC obtains 8 kHz standard timingsignals in RS-422 level mode from an external device.

Local Oscillator

If the RNC fails to obtain any external clock, the RNC can obtain its working timing signalsfrom the local oscillator.

NOTE

The timing signals generated by the local oscillator, however, do not meet the requirements of NodeBs forclock precision. Therefore, when the RNC uses such timing signals, the NodeBs fail to obtain the timingsignals that meet the precision requirements from the RNC.

3.5.2 Structure of the RNC Clock Synchronization SubsystemThe RNC clock synchronization subsystem consists of the clock module and other boards. Theclock module is implemented by the GCUa/GCGa board.

Figure 3-16 shows the structure of the RNC clock synchronization subsystem.

Figure 3-16 Structure of the RNC clock synchronization subsystem

l The RINT in the figure refers to the Iu/Iur/Iub interface board. You can choose to usedifferent interface boards based on the requirements.


Product Description


Issue 03 (2008-08-30)

l The RNC can use the GPS timing signals shown in Figure 3-16 only when the RNC isconfigured with the GCGa board, because the GCGa board is configured with a GPS cardbut the GCUa board is not.

l If the RINT (AEUa, PEUa, POUa, AOUa, or UOIa) that extracts the line clock from theCN is located in the RSS subrack, the timing signals travel to the GCUa/GCGa board eitherthrough a backplane channel in the RSS subrack or through the 2 MHz timing signal outputport on the panel of the RINT. In the former case, the channel can be either line 0 channelor line 1 channel. In the latter case, a clock cable connects the RINT to the GCUa/GCGaboard.

l If the RINT that extracts the clock from the CN is located in an RBS subrack, the timingsignals travel to the GCUa/GCGa board only through the 2 MHz timing signal output porton the panel of the RINT. In this case, a clock cable connects the RINT to the GCUa/GCGaboard.

When the RNC is configured with active/standby GCUa/GCGa boards and active/standby SCUaboards, the connections of clock cables between the boards follow certain rules. Figure 3-17shows the connections between the GCUa/GCGa boards in the RSS subrack and the SCUaboards in an RBS subrack.

Figure 3-17 Clock cable connections between GCUa/GCGa boards and SCUa boards

As shown in Figure 3-17, the active/standby GCUa/GCGa boards in the RSS subrack areconnected to the active/standby SCUa boards in the RBS subrack through the Y-shaped clockcables. This connection mode ensures proper working of the timing signals for the RNC systemif a single-point failure occurs to the GCUa/GCGa board, Y-shaped clock cable, or SCUa board.In addition, the Y-shaped cable protects the proper working of the SCUa boards from switchoverof the GCUa/GCGa boards.

NOTE

In the RSS subrack, the GCUa/GCGa boards send timing signals to the SCUa boards in the same subrackthrough the backplane channels. Therefore, the Y-shaped cables are not required.



3-33

3.5.3 Timing Signal Processing in the RNCThe RNC processes foreign timing signals before sends the timing signals to the boards.

The system timing signals are processed as follows:

1. The clock module of the GCUa/GCGa board receives timing signals.2. The clock module sends the timing signals to the SCUa board in the RSS subrack through

the backplane channel and to the SCUa board in each RBS subrack through the timingsignal output ports on the GCUa/GCGa board.

3. The SCUa board in the RSS subrack generates the 19.44 MHz, 32.768 MHz, and 8 kHzsystem timing signals and sends them to the boards in the subrack through the high-speedbackplane channel. The same is true for each RBS subrack.l The AEUa and PEUa boards obtain 32.768 MHz working timing signals.

l The AOUa and POUa boards obtain 19.44 MHz working timing signals.

l The UOIa board obtains 8 kHz working timing signals.

l The FG2a and GOUa boards do not use the timing signals provided by the clock module.

4. The RINT (AEUa, PEUa, POUa, AOUa, or UOIa) sends the timing signals to NodeBs.

3.5.4 RFN Generation and ReceptionRNC Frame Number (RFN) is applicable to node synchronization for the RNC. The nodesynchronization frames that the RNC sends to the NodeB carry the RFN signals.

Figure 3-18 shows the process of RFN generation and reception. This figure takes the GCUaboard as an example.


Product Description


Issue 03 (2008-08-30)

Figure 3-18 RFN generation and reception

As shown in Figure 3-18, the GCUa/GCGa board in the RSS subrack sends the 1 PPS signalsand synchronization time packets to the SCUa board in each subrack. The SCUa board thensends them to the other boards in each subrack. The boards generate the required RFN signalsaccording to the received 1 PPS signals and synchronization time packets.

NOTE

l The 1 PPS signals can be generated by the GCUa/GCGa board.

l When the RNC is configured with the GCGa board, the RNC can obtain GPS synchronization signalsthrough the GPS card to generate the 1 PPS signals that are synchronized with the satellite signals.

3.6 RNC Power SubsystemThe RNC power subsystem serves the entire equipment. This subsystem adopts the dual-circuitbackup and monitor-at-each-point solution, thus featuring high reliability.

3.6.1 Power Supply Requirements of the RNCThis describes the power supply schemes of the RNC and requirements for the AC power andDC power supplied to the RNC.

3.6.2 Layout of Power Switches on the RNC Cabinet



3-35

There is a fixed relation between outputs of the power distribution box of the RNC cabinet andthe intra-cabinet components.

3.6.3 Connections of Power Cables and PGND Cables in the RNC CabinetThe power cables and PGND cables in the RSR cabinet are connected in the same way as thosein the RBR cabinet.

3.6.1 Power Supply Requirements of the RNCThis describes the power supply schemes of the RNC and requirements for the AC power andDC power supplied to the RNC.

3.6.1.1 Power Supply Schemes of the RNCThis describes the power supply schemes of the RNC. The RNC power supply system consistsof the –48 V DC power system, PDF, and DC power distribution box configured on top of thecabinet.

3.6.1.2 AC Power Requirements of the RNCThis describes the AC power requirements of the RNC. The RNC has higher AC powerrequirements. The AC power of the equipment room should be ready before construction of theroom.

3.6.1.3 DC Power Requirements of the RNCThis describes the DC power requirements of the RNC. The RNC has high DC powerrequirements, Therefore, the equipment should be placed near the telecom equipment tominimize the DC feeder loss. In addition, the loop voltage drop from the battery port to theequipment port should be less than 3.2 V to reduce power consumption and installation cost.

Power Supply Schemes of the RNCThis describes the power supply schemes of the RNC. The RNC power supply system consistsof the –48 V DC power system, PDF, and DC power distribution box configured on top of thecabinet.

Use two or more independent power supply systems when there is heavy traffic or there are morethan two switching systems within the telecom office.

For a large-scale office, configure multiple power supply systems at different floors. The powersupply systems are used for different equipment rooms respectively.

Configure a centralized power room or battery room for an office with medium traffic, or adoptthe distributed power supply mode. Use the integrated power supply for an office with smalltraffic. Figure 3-19 shows the power supply schemes of the RNC.

CAUTIONNote that corrosive gas released by the batteries would erode the circuit boards.


Product Description


Issue 03 (2008-08-30)

Figure 3-19 Power supply schemes of the RNC

The PDF provides two DC power outputs in 1+1 backup mode. The outputs are connected tothe power distribution box on the RNC cabinet top to supply power to the RNC equipment.

NOTE

l Each RNC cabinet is configured with nine cables, that is four -48 V power cables, four RTN powercables, and one PGND cable.

l When the PDF is located far away from the RNC cabinet, for example, when they are not in the sameequipment room, connect the PGND cables of the RNC cabinets to the nearest grounding bar co-grounded with the PDF rather than connect the PGND cables directly with the PDF.

AC Power Requirements of the RNC

This describes the AC power requirements of the RNC. The RNC has higher AC powerrequirements. The AC power of the equipment room should be ready before construction of theroom.

WARNINGThe Uninterrupted Power Supply (UPS) must be configured to ensure proper working of themaintenance terminal in case of power failure.

The centralized power supply mode is preferred for the AC power supply system that consistsof a mains, UPS, and house generator set.

WARNINGThe AC backup power supply is in the same phase with the mains. The UPS–mains switchoverduration must be less than 10 ms. Otherwise, the equipment may be restarted or reset.

The three-phase or mono-phase mode is preferred for the low-voltage power supply system.Table 3-4 lists the nominal voltage and frequency of the low-voltage AC.



3-37

Table 3-4 Nominal voltage and frequency of low-voltage AC power

Nominal Voltage (V) Nominal Frequency (Hz)

110/127/200/220/230/240/380 50/60

NOTE

Different countries or different areas in a country may use different low-voltage power supply systems.The following is an example: three-phase three-wire of 200 V, three-phase four-wire of 200 V, and mono-phase three-wire of 200 V.

When determining the AC power distribution capacity in the equipment room, consider theworking current and fault current. Each individual equipment must have an independent ACdistribution protection device. The protection switch must be more powerful than those of thelower-level electricity devices. Cable outlet of the power distribution panel is determined by themaximum load capacity of the supplied power. This enables you to decide the type and size ofthe conducting wire. Cable type and specification can be determined accordingly.

Specifications for AC voltage of the communications and power supply equipment are asfollows:

l If the communications equipment uses the AC power supply, the permissible voltage rangeis +5% to -10% of the nominal voltage.

l If the power supply equipment and major buildings use the AC power supply, thepermissible voltage range is +10% to –15% of the nominal voltage. the permissible voltagerange is +10% to -15% of the nominal voltage.

l The permissible fluctuation range of AC frequencies is within ±4%. Sinusoidal distortionrate of the voltage waveform is no more than 5%.

The self-provided generator set on site should be automatic. The requirements for the generatorset are as follows:l No loud noise

l Automatic power-on and power-off, supply, and communication

l Remote control and mesurement

l Standard interface and communication protocols

Specifications for the AC power cables are as follows:

l Cross-sectional area of the AC power cables should be the same as that of the phase cable.

l The conducting wires should be fire-resistant. Their layout must comply with the localregulations.

The requirements for the AC power supplied to the RNC are as follows:

l Use the voltage regulator in the following two situations:– When the communications equipment is powered directly by the mains, the power

supply voltage exceeds the rated voltage by –10% to +5%, or exceeds the voltage rangepermitted for the communications equipment.

– When the communications equipment is not powered directly by the mains, the mainsvoltage exceeds the rated voltage by –15% to +10%, or the AC input voltage rangepermitted for the DC power equipment.


Product Description


Issue 03 (2008-08-30)

l To ensure stable power supply, use a UPS or inverter.

l Configure the generator set for the office to ensure proper communication in case of mainsfailure. The capacity of the generator set should be greater than or equal to 1.5–2 times thecapacity of the continuous power supply equipment.

l Capacity of the UPS or inverter must be larger than the total load power, preferably witha surplus of 80% of the total load power. Backup is required for the use of the UPS orinverter.

DC Power Requirements of the RNC

This describes the DC power requirements of the RNC. The RNC has high DC powerrequirements, Therefore, the equipment should be placed near the telecom equipment tominimize the DC feeder loss. In addition, the loop voltage drop from the battery port to theequipment port should be less than 3.2 V to reduce power consumption and installation cost.

Table 3-5 lists the specifications for the DC power supply.

Table 3-5 Specifications for the DC power supply

Item Specification

Permitted voltage range for the -48 VDC power

-40 V to -57 V

DC power capacity to support the surgecurrent

At least 1.5 times greater than the rated current

Regulated voltage precision If the AC input voltage is in the range of 85%–110% of the rated value, and the load current is inthe range of 5%–100% of the rated value, theoutput voltage of the rectifier is an integer in therange of –46.0 V to –56.4 V, with the regulatedvoltage precision not more than 1%.

Overshoot amplitude of switch on/off Within ±5% of the rated DC output voltage

Peak-to-peak noise voltage ≤ 200 mV

Dynamic response The recovery time is less than 200 ms. Theovershoot is within ±5% of the rated DC outputvoltage.

The requirements for the DC power supplied to the RNC are as follows:

l The power supply in the dispersed mode is preferred. Use multiple DC power supplysystems and place the power equipment in multiple positions.

l Use the standard DC power supply system, and set the output voltage of the power systemwithin the specified range.

l Improve the reliability of the DC power supply system, and reduce storage batteries. Forsmall offices, add batteries if it is difficult to enhance the reliability of the DC power supplysystem.



3-39

l The total capacity of the high frequency switch rectifier should meet the powerspecifications of the communication loading and battery charging. Configure the backuprectifier modules. If there are less than 10 active modules, configure one backup module.If there are more than 10 active modules, configure one backup module for every 10 activemodules.

l Install the storage batteries in two or more groups. The capacity is determined by theduration taken by the storage batteries to supply power to the load. For most offices, thebatteries must be able to supply power for at least one hour.

3.6.2 Layout of Power Switches on the RNC CabinetThere is a fixed relation between outputs of the power distribution box of the RNC cabinet andthe intra-cabinet components.

The power distribution box of the RNC cabinet provides six power outputs for the subracks. Thepower supply is divided into two groups: A and B. The switches related are A8 to A10 and B8to B10.

The working mechanism of the power distribution box is shown in Figure 3-20. Table 3-6describes the working mechanism of the power distribution box.

Figure 3-20 Working mechanism of the power distribution box

Table 3-6 Working mechanism of the power distribution box

PDF Output PDB Input PDB Output Subrack Input

-48 V 63 A DCoutput

Power inputterminal block A 1(-) and B 1(-)

A8 andB8

RTN(+) RTN input of subrack 2 or5


Product Description


Issue 03 (2008-08-30)

PDF Output PDB Input PDB Output Subrack Input

RTN output of thePDF

Power inputterminal block A 1(+) 3(+) and B 1(+) 3(+)

NEG(-) -48 V DC input of subrack2 or 5

-48 V 100 A DCoutput of the PDF

Power inputterminal block A 3(-) and B 3(-)

A9 andB9



A10 andB10



The assignment of power switches A8 to A10 and B8 to B10 on the power distribution box isshown in Figure 3-21. Table 3-7 describes the relation between the switches and subracks.

Figure 3-21 Assignment of power switches on the power distribution box

Table 3-7 Relation between the switches and subracks

RNC Subracks Power Switches

Subrack 2, subrack 5 A8, B8





3-41

3.6.3 Connections of Power Cables and PGND Cables in the RNCCabinet

The power cables and PGND cables in the RSR cabinet are connected in the same way as thosein the RBR cabinet.

Figure 3-22 shows the connections of the power cables and the PGND cables in the N68E-22cabinet.

Figure 3-22 Connections of power cables and PGND cables in the N68E-22 cabinet

Table 3-8 describes connections of the power cables and PGND cables in the RNC cabinet.


Product Description


Issue 03 (2008-08-30)

Table 3-8 Connections of power cables and PGND cables in the RNC cabinet

Number Description

5, 6; 11, 12 Power cable of the lowest subrack

3, 4; 9, 10 Power cable of the middle subrack

1, 2; 7, 8 Power cable of the highest subrack

13 PGND cable connecting the power distribution box andthe mounting bar

14, 15, 16; 17, 18, 19 PGND cables connecting the subracks and the mountingbar

24, 25, 26 PGND cables connecting the adjacent cabinets

50 to 57 PGND cables of cabinet doors

Figure 3-23 shows the connections of the power cables and the PGND cables in the N68-21-Ncabinet.



3-43

Figure 3-23 Connections of power cables and PGND cables in the N68-21-N cabinet

Table 3-9 describes connections of the power cables and PGND cables in the RNC cabinet.

Table 3-9 Connections of power cables and PGND cables in the RNC cabinet

Number Description

5, 6; 11, 12 Power cable of the lowest subrack

3, 4; 9, 10 Power cable of the middle subrack

1, 2; 7, 8 Power cable of the highest subrack


Product Description


Issue 03 (2008-08-30)

Number Description

13 PGND cable connecting the power distribution box andthe busbar

14, 15, 16; 17, 18, 19 PGND cables connecting subracks to busbars

20, 21 PGND cables of the cabinet busbar

24, 25, 26 PGND cables connecting the busbars of different cabinets

50 to 57 PGND cables of cabinet doors

3.7 RNC Environment Monitoring SubsystemThe RNC environment monitoring subsystem automatically monitors the working environmentof the RNC and reports faults in real time.

The RNC environment monitoring subsystem consists of the power distribution box and theenvironment monitoring parts in each subrack. This subsystem is responsible for power supplymonitoring, fan monitoring, cabinet door monitoring, and water monitoring.

3.7.1 RNC Power Supply MonitoringRNC power monitoring is performed to monitor the power subsystem in real time, report therunning state of the power supply, and generate alarms when faults occur.

3.7.2 RNC Fan MonitoringRNC fan monitoring is performed to monitor the fans in real time and adjust the speed of thefans based on the temperature in the subrack.

3.7.3 RNC Cabinet Door MonitoringRNC cabinet door monitoring is optional. When the RNC detects that the front or back door ofa cabinet is open, the RNC generates and reports an appropriate alarm.

3.7.4 RNC Water MonitoringRNC water monitoring is optional. When the RNC detects water immersion, the RNC generatesand reports an appropriate alarm.

3.7.1 RNC Power Supply MonitoringRNC power monitoring is performed to monitor the power subsystem in real time, report therunning state of the power supply, and generate alarms when faults occur.

Figure 3-24 shows the power monitoring principles.



3-45

Figure 3-24 RNC power monitoring principles

The RNC power monitoring process is as follows:

1. The PAMU in the power distribution box monitors the running state of the powerdistribution box and sends the monitoring results to the power distribution interface boardthrough the signal transfer board.

2. The power distribution box monitoring signal cable sends the monitoring signals to theSCUa board in the power monitoring subrack of the RNC.

3. The SCUa board processes the monitoring signals. If a fault occurs, the SCUa boardgenerates and reports an alarm to the OMUa board.

3.7.2 RNC Fan MonitoringRNC fan monitoring is performed to monitor the fans in real time and adjust the speed of thefans based on the temperature in the subrack.

The fans are integrated with the subrack. Every subrack has a fan box in which there are amaximum of nine fans. The temperature sensor beside the air outlet can detect the temperaturein the subrack.

Figure 3-25 shows the fan monitoring principles.

Figure 3-25 RNC fan monitoring principles


Product Description


Issue 03 (2008-08-30)

The RNC fan monitoring process is as follows:

1. The fan monitoring unit PFCU in the fan box monitors the running state of the fans in realtime and reports the monitoring signals to the SCUa board in the subrack.

2. The SCUa board processes the monitoring signals. If a fault occurs, the SCUa boardgenerates and reports an alarm to the OMUa board.

3.7.3 RNC Cabinet Door MonitoringRNC cabinet door monitoring is optional. When the RNC detects that the front or back door ofa cabinet is open, the RNC generates and reports an appropriate alarm.

Figure 3-26 shows the cabinet door monitoring principles.

Figure 3-26 RNC cabinet door monitoring principles

The door control sensor is installed on the doorhead of the RNC cabinet. The sensor is connectedto the power distribution interface board of a power distribution box through a cable.

The RNC cabinet door monitoring process is as follows:

1. The door control sensor monitors the front and back doors of the RNC cabinet in real time.If the front or back door is open, the door control sensor generates appropriate monitoringsignals.

2. The monitoring signals travel to the power distribution interface board of the powerdistribution box through the cable.

3. The power distribution interface board processes the monitoring signals and then send thesignals to the SCUa board in the power monitoring subrack of the RNC.

4. The SCUa board processes the signals, generates an appropriate door control alarm, andreports the alarm to the OMUa board.

3.7.4 RNC Water MonitoringRNC water monitoring is optional. When the RNC detects water immersion, the RNC generatesand reports an appropriate alarm.



3-47

Figure 3-27 shows the water monitoring principles.

Figure 3-27 RNC water monitoring principles

The water sensor of the RNC is placed on the floor of the equipment room. The sensor isconnected to the power distribution interface board of a power distribution box through a cable.

The RNC water monitoring process is as follows:

1. The water sensor monitors the environment of the equipment room in real time. If the watersensor detects water immersion in the equipment room, the sensor generates appropriatemonitoring signals.

2. The monitoring signals travel to the power distribution interface board of the powerdistribution box through the cable.

3. The power distribution interface board processes the monitoring signals and then send thesignals to the SCUa board in the power monitoring subrack of the RNC.

4. The SCUa board processes the signals, generates an appropriate water immersion alarm,and reports the alarm to the OMUa board.


Product Description


Issue 03 (2008-08-30)

4 RNC Signal Flow

About This Chapter

This describes signal flows on the control planes and user planes of the Uu, Iub, Iur, and Iuinterfaces.

4.1 RNC Signal Flow on the Control PlaneThe control plane in the RNC processes the control plane messages on the Uu, Iub, Iur, and Iuinterfaces. All control plane messages are terminated at the SPUa boards in the RNC.

4.2 RNC Signal Flow on the User PlaneThe user plane in the RNC processes the user plane messages on the Uu, Iub, Iur, and Iuinterfaces.

RNCProduct Description 4 RNC Signal Flow


4-1

4.1 RNC Signal Flow on the Control PlaneThe control plane in the RNC processes the control plane messages on the Uu, Iub, Iur, and Iuinterfaces. All control plane messages are terminated at the SPUa boards in the RNC.

4.1.1 Control Message Flow on the Uu InterfaceUu control messages are the Radio Resource Control (RRC) messages, which are signalingmessages that travel between the UE and the RNC when the UE accesses the network or whenthe UE communicates with the RNC. The RRC messages are used in the UE activities such aslocation updates and calls.

4.1.2 Control Message Flow on the Iub InterfaceIub control messages are the control plane messages between the RNC and the NodeB.

4.1.3 Control Message Flow on the Iu/Iur InterfacesIu/Iur control messages are the control plane messages between the RNC and the MSC, SGSN,or neighboring RNC. The MSC is divided into the MGW and the MSC server in R4, R5, or R6networking.

4.1.1 Control Message Flow on the Uu InterfaceUu control messages are the Radio Resource Control (RRC) messages, which are signalingmessages that travel between the UE and the RNC when the UE accesses the network or whenthe UE communicates with the RNC. The RRC messages are used in the UE activities such aslocation updates and calls.

Intra-RNC Control Message Flow on the Uu InterfaceFigure 4-1 shows the Uu control message flow that applies to the scenario where one RNCperforms radio resource management and provides radio links for the UE. See signal flows 1and 2 in the figure.

Figure 4-1 Intra-RNC control message flow on the Uu interface

4 RNC Signal FlowRNC

Product Description


Issue 03 (2008-08-30)

NOTE

l The RINT in the figure refers to the Iu/Iur/Iub interface board. You can choose to use different interfaceboards based on the requirements.

l The symbol of the RSS subrack in the figure indicates the switching unit in the RSS subrack.

In the uplink, the intra-RNC control message flow on the Uu interface is as follows:

1. The RRC messages sent from the UE are processed on the physical layer of the NodeB andthen sent to the Iub RINT of the RNC over the Iub interface.

2. The RINT processes the messages and then sends them to the DPUb board. See signal flow1 in Figure 4-1.

If the SPUa board that processes the RRC messages and the RINT that receives the RRCmessages are located in different subracks, the messages travel to the appropriate DPUbboard after the switching in the RSS subrack. See signal flow 2 in Figure 4-1.

3. The DPUb board performs FP, MDC, MAC, and RLC processing on the messages and thensends the messages to the appropriate SPUa board where the messages are terminated.

The downlink flow is the converse of the uplink flow.

Inter-RNC Control Message Flow on the Uu Interface

Figure 4-2 shows the Uu control message flow that applies to the scenario where the ServingRNC (SRNC) performs radio resource management and the Drift RNC (DRNC) provides radiolinks for the UE respectively.

Figure 4-2 Inter-RNC control message flow on the Uu interface

NOTE

The RINT in the figure refers to the Iu/Iur/Iub interface board. You can choose to use different interfaceboards based on the requirements.

In the uplink, the inter-RNC control message flow on the Uu interface is as follows:

1. The RRC messages sent from the UE are processed on the physical layer of the NodeB andthen sent to the Iub RINT of the DRNC over the Iub interface.

2. The Iub RINT and the DPUb board of the DRNC process the messages and then send themto the Iur RINT of the DRNC.



4-3

NOTE

When the UE performs a cell update across the Iur interface, the RRC messages travel to the IurRINT of the DRNC through the SPUa board of the DRNC. In any other case, the RRC messages donot need to travel through the SPUa board.

3. The Iur RINT of the DRNC processes the messages and then sends them to the Iur RINTof the SRNC over the Iur interface between the DRNC and the SRNC.

4. The Iur RINT of the SRNC processes the messages and then sends them to the DPUb board.5. The DPUb board performs FP, MDC, MAC, and RLC processing on the messages and then

sends the messages to the appropriate SPUa board where the messages are terminated.


4.1.2 Control Message Flow on the Iub InterfaceIub control messages are the control plane messages between the RNC and the NodeB.

Figure 4-3 shows the control message flow on the Iub interface.

Figure 4-3 Control message flow on the Iub interface

NOTE



In the uplink, the control message flow on the Iub interface is as follows:

1. The control plane messages sent from the NodeB travel to the Iub RINT of the RNC overthe Iub interface.

2. The Iub RINT processes the messages and then sends them to the SPUa board where themessages are terminated. See signal flow 1 in Figure 4-3.If the SPUa board that processes the messages and the RINT that receives the messagesare located in different subracks, the messages travel to the processing SPUa board afterthe switching in the RSS subrack. See signal flow 2 in Figure 4-3.


Product Description


Issue 03 (2008-08-30)


4.1.3 Control Message Flow on the Iu/Iur InterfacesIu/Iur control messages are the control plane messages between the RNC and the MSC, SGSN,or neighboring RNC. The MSC is divided into the MGW and the MSC server in R4, R5, or R6networking.

Figure 4-4 shows the control message flow on the Iu and Iur interfaces. See signal flows 1, 2and 3 in the figure.

Figure 4-4 Control message flow on the Iu/Iur interfaces

NOTE



In the downlink, the control message flow on the Iu/Iur interfaces is as follows:

1. The control plane messages sent from the MSC or SGSN travel to the Iu RINT of the RNCover the Iu interface, or the control plane messages sent from the neighboring RNC travelto the Iur RINT of the local RNC over the Iur interface.

2. The RINT processes the messages and then sends them to the SPUa board in the samesubrack for processing. See signal flow 1 in Figure 4-4.The RINT processes the messages, then sends them to the SPUa board in the same subrackfor processing, and finally sends them to another SPUa board for processing after theswitching in the RSS subrack. See signal flow 2 in Figure 4-4.The RINT processes the messages and then sends them to another SPUa board forprocessing after the switching in the RSS subrack. See signal flow 3 in Figure 4-4.

The uplink flow is the converse of the downlink flow.

4.2 RNC Signal Flow on the User PlaneThe user plane in the RNC processes the user plane messages on the Uu, Iub, Iur, and Iuinterfaces.

4.2.1 Data Flow Between Iub and Iu-CS/Iu-PS



4-5

Data between Iub and Iu-CS/Iu-PS is the user plane data between the RNC and the MSC orSGSN. The MSC is divided into the MGW and the MSC server in R4, R5, or R6 networking.

4.2.2 Data Flow from Iu-BC to IubData from Iu-BC to Iub refers to the BC domain data.

4.2.1 Data Flow Between Iub and Iu-CS/Iu-PSData between Iub and Iu-CS/Iu-PS is the user plane data between the RNC and the MSC orSGSN. The MSC is divided into the MGW and the MSC server in R4, R5, or R6 networking.

The data flow between Iub and Iu-CS/Iu-PS is categorized into the following types:l Intra-RNC data flow between Iub and Iu-CS/Iu-PS

l Inter-RNC data flow between Iub and Iu-CS/Iu-PS

Intra-RNC data flow between Iub and Iu-CS/Iu-PSIf the RNC that receives the data on the Iub interface sends the data directly to the MSC/SGSNthrough the Iu-CS/Iu-PS connection, the data flow is called an intra-RNC data flow between Iuband Iu-CS/Iu-PS. Figure 4-5 shows the intra-RNC data flow between Iub and Iu-CS/Iu-PS. Seedata flows 1 and 2.

Figure 4-5 Intra-RNC data flow between Iub and Iu-CS/Iu-PS

NOTE



In the uplink, the intra-RNC data flow between Iub and Iu-CS/Iu-PS is as follows:

1. The NodeB processes the data and sends it to the Iub RINT of the RNC over the Iubinterface.

2. The Iub RINT processes the data and sends it to the appropriate DPUb board. See data flow1 in Figure 4-5.


Product Description


Issue 03 (2008-08-30)

If the DPUb board that processes the user plane data and the RINT that receives the dataare located in different subracks, the data travels to the appropriate DPUb board throughswitching at the RSS subrack. See data flow 2 in Figure 4-5.

3. The DPUb board performs the FP, MDC, MAC, RLC, and Iu UP or PDCP/GTP-Uprocessing on the data, separates CS/PS user plane data from other data, and then sends thedata to the Iu-CS/Iu-PS RINT.

NOTE

If the DPUb board that processes the user plane data and the Iu-CS/Iu-PS RINT are located in differentsubracks, the data processed by the DPUb board travels to the Iu-CS/Iu-PS RINT through switchingat the RSS subrack.

4. The Iu-CS/Iu-PS RINT processes the data and then sends it to the MSC/SGSN.


Inter-RNC data flow between Iub and Iu-CS/Iu-PS

If the RNC that receives the data over the Iub interface sends the data to the MSC/SGSN throughanother RNC, the data flow is called an inter-RNC data flow between Iub and Iu-CS/Iu-PS.

Figure 4-6 shows the inter-RNC data flow between Iub and Iu-CS/Iu-PS. The Drift RNC(DRNC) and the Serving RNC (SRNC) are involved.

Figure 4-6 Inter-RNC data flow between Iub and Iu-CS/Iu-PS

NOTEThe RINT in the figure refers to the Iu/Iur/Iub interface board. You can choose to use different interfaceboards based on the requirements.

In the uplink, the inter-RNC data flow between Iub and Iu-CS/Iu-PS is as follows:

1. The NodeB processes the data and sends it to the Iub RINT of the DRNC.

2. The Iub RINT and the DPUb board of the DRNC process the data and then send it to theIur RINT of the DRNC.

NOTE

The DPUb board of the DRNC performs only FP and MDC processing on the data.

3. The Iur RINT of the DRNC processes the data and then sends it to the Iur RINT of theSRNC over the Iur interface between the DRNC and the SRNC.

4. The Iur RINT of the SRNC processes the data and then sends it to the DPUb board.



4-7

5. The DPUb board processes the data, separates CS/PS user plane data from other data, andthen sends the data to the Iu-CS/Iu-PS RINT.

6. The Iu-CS/Iu-PS RINT processes the data and then sends it to the MSC/SGSN.


4.2.2 Data Flow from Iu-BC to IubData from Iu-BC to Iub refers to the BC domain data.

Figure 4-7 shows the data flow from Iu-BC to Iub. See data flows 1 and 2 in the figure.

Figure 4-7 Data flow from Iu-BC to Iub

NOTE



The data flow from Iu-BC to Iub is as follows:

1. The Cell Broadcast Center (CBC) sends the broadcast data to the Iu-BC RINT of the RNCover the Iu-BC interface.

2. The Iu-BC RINT processes the data and then sends it to the SPUa board.3. The SPUa board processes the Service Area Broadcast Protocol (SABP) data and sends

relevant data to the appropriate DPUb board. See data flow 1 in Figure 4-7.If the Iub RINT that delivers the broadcast data and the Iu-BC RINT are located in differentsubracks, the data travels to the RSS subrack for switching. The RSS subrack then sendsthe data to the SPUa board in the same subrack as the Iub RINT that delivers the data. Afterthat, the data travels to the appropriate DPUb board. See data flow 2 in Figure 4-7.

4. The DPUb board performs the BMC, RLC, and MAC processing on the data and then sendsthe data to the Iub RINT.

5. The Iub RINT processes the data and then sends it to the NodeB.6. The NodeB broadcasts the data to the UEs in the cells controlled by the NodeB.


Product Description


Issue 03 (2008-08-30)

5 RNC Transport and Networking

About This Chapter

This describes the networking modes on the RNC side in terms of the transport and networkingon the Iub, Iu-CS/Iu-PS/Iur, and Iu-BC interfaces and the RNC OM networking.

5.1 Transport and Networking on the Iub InterfaceThis describes the interface boards and network solutions applicable to data transmissionbetween RNC and NodeB.

5.2 Transport and Networking on the Iu/Iur InterfaceThis describes the interface boards and network solutions applicable to data transmissionbetween the RNC and the CN or neighboring RNC.

5.3 Transport and Networking on the Iu-BC InterfaceThis part describes the interface boards and network solutions applicable to data transmissionbetween the RNC and the CBC.

5.4 RNC OM NetworkingThe RNC OM networking provides operation and maintenance for the RNC and NodeB.

RNCProduct Description 5 RNC Transport and Networking


5-1

5.1 Transport and Networking on the Iub InterfaceThis describes the interface boards and network solutions applicable to data transmissionbetween RNC and NodeB.

5.1.1 Interface Boards for the IubThe Iub interface supports data transmission based on ATM, IP, or ATM/IP dual stack. Differenttypes of interface board are applicable to different modes of data transmission.

5.1.2 ATM-Based Networking on the Iub InterfaceIn ATM-based networking on the Iub interface, the RNC and the NodeB communicate basedon the ATM protocol stack.

5.1.3 IP-Based Networking on the Iub InterfaceIn IP-based networking on the Iub interface, the RNC and the NodeB communicate based onthe IP protocol stack.

5.1.4 ATM/IP-Based Networking on the Iub InterfaceIn ATM/IP-based networking on the Iub interface, the RNC and the NodeB communicate basedon the ATM/IP dual stack, that is, based on the ATM and IP protocol stacks at the same time.

5.1.5 Satellite-Based Networking on the Iub InterfaceIn satellite-based networking on the Iub interface, the RNC and the NodeB communicate throughthe satellite.

5.1.6 2G/3G Concurrent Transmission and NetworkingIn 2G/3G concurrent transmission, the 2G and 3G information share transmission resources.This topic describes the networking for such transmission.

5.1.1 Interface Boards for the IubThe Iub interface supports data transmission based on ATM, IP, or ATM/IP dual stack. Differenttypes of interface board are applicable to different modes of data transmission.

ATM-Based Iub Interface Boards

The following types of board are applicable to the ATM-based Iub interface:

l AEUa board

l AOUa board

l UOIa board (UOI_ATM)

IP-Based Iub Interface Boards

The following types of board are applicable to the IP-based Iub interface:

l PEUa board

l POUa board

l FG2a board

l GOUa board

l UOIa board (UOI_IP)

5 RNC Transport and NetworkingRNC

Product Description


Issue 03 (2008-08-30)

ATM/IP-Based Iub Interface Boards

Over the Iub interface based on the ATM/IP dual stack, the RNC can communicate with a NodeBthrough ATM and IP transport at the same time.

The following types of interface board are applicable to the ATM transport option on the Iubinterface:

l AEUa board

l AOUa board


The following types of interface board are applicable to the IP transport option on the Iubinterface:

l POUa board

l FG2a board

l GOUa board


NOTE

When data transmission based on the ATM/IP dual stack applies, the IP transport option is mainly used tocarry high-speed large-throughput traffic, such as HSDPA and HSUPA. The PEUa board, however, doesnot meet the transmission requirements of such services. Therefore, the PEUa board is usually not appliedto ATM/IP dual stack–based transport.

5.1.2 ATM-Based Networking on the Iub InterfaceIn ATM-based networking on the Iub interface, the RNC and the NodeB communicate basedon the ATM protocol stack.

Scenario of the Networking

The RNC and the NodeB can communicate with each other through the existing PDH, SDH, orATM network.

ATM Networking Based on PDH

In this networking mode, the RNC uses the AEUa as the Iub interface board.

Figure 5-1 shows the ATM networking based on PDH. E1/T1 ports on the RNC serve the ATMtransport.

Figure 5-1 ATM networking based on PDH



5-3

NOTE

If the NodeBs are distributed on different PDH rings, additional ADM/DXC devices are required.

ATM Networking Based on ATM over E1/T1 over SDH

In this networking mode, the AOUa board of the RNC serves as the Iub interface board andsupports board backup and MSP 1:1 optical port backup.

Figure 5-2 shows the ATM networking based on ATM over E1 over SDH. Channelized STM-1optical ports on the RNC serve the ATM transport.

Figure 5-2 ATM networking based on ATM over E1/T1 over SDH

The SDH network converges the E1/T1 traffic, which travels from multiple NodeBs, to achannelized STM-1 optical port. The network then communicates with the RNC through achannelized STM-1 optical port.

NOTE

If the NodeBs are distributed on different SDH rings, additional ADM/DXC devices are required.

ATM Networking Based on ATM over SDH

In this networking mode, the UOIa board (UOI_ATM) of the RNC serves as the Iub interfaceboard and supports board backup and MSP 1+1 or MSP 1:1 optical port backup.

Figure 5-3 shows the ATM networking based on ATM over SDH. Unchannelized STM-1 opticalports on the RNC serve the ATM transport.

Figure 5-3 ATM networking based on ATM over SDH


Product Description


Issue 03 (2008-08-30)

The ATM network converges the E1/T1 traffic, which travels from multiple NodeBs, to anSTM-1 port. The ATM network then connects to the unchannelized optical port on the UOIaboard of the RNC.

Advantages of the NetworkingThe mature ATM-based networking on the Iub interface ensures ATM transmission bandwidth,has a QoS guarantee mechanism, and features security and reliability. The telecom operatorscan make efficient use of the existing PDH, SDH, or ATM transmission resources.

The advantages of each type of networking are as follows:l ATM Networking Based on PDH

This type of networking enables the telecom operators to use the existing PDH transmissionresources.

l ATM Networking Based on ATM over E1/T1 over SDHThis type of networking requires simple cable connections, features convenient equipmentinstallation and maintenance, and supports MSP 1:1 backup.

l ATM Networking Based on ATM over SDHThis type of networking requires simple cable connections, features convenient equipmentinstallation and maintenance, and supports MSP 1+1 backup. The ATM switch convergesE1/T1 traffic, which travels from multiple NodeBs, to an STM-1 device, thus enablingstatistical multiplexing, obtaining convergence gain, and saving transmission resources.

Disadvantages of the NetworkingCompared with IP-based networking, ATM-based networking on the Iub interface has a highcost.

5.1.3 IP-Based Networking on the Iub InterfaceIn IP-based networking on the Iub interface, the RNC and the NodeB communicate based onthe IP protocol stack.

Scenario of the NetworkingThe RNC and the NodeB can communicate with each other through the existing PDH, SDH,MSTP, or data network.

IP Networking Based on PDH/SDHIn this networking mode, the RNC uses the PEUa as the Iub interface board.

Figure 5-4 shows the IP networking based on PDH/SDH. E1/T1 ports on the RNC serve the IPtransport.



5-5

Figure 5-4 IP networking based on PDH/SDH

The RNC accesses the PDH/SDH networks through E1/T1 ports and transmits data in IP overMLPPP/PPP over E1/T1 mode. The NodeB can obtain timing signals from the E1/T1 links.

The PDH/SDH network allows transparent transport for E1/T1 data. The network guaranteesreliability, security, and QoS for the transmission of Iub interface data.

IP Networking Based on IP over E1/T1 over SDH

In this networking mode, the POUa board of the RNC serves as the Iub interface board andsupports board backup and MSP 1+1 or MSP 1:1 optical port backup.

Figure 5-5 shows the IP networking based on IP over E1/T1 over SDH. Channelized STM-1optical ports on the RNC serve the IP transport.

Figure 5-5 IP networking based on ATM over E1/T1 over SDH

The SDH network converges the E1/T1 traffic, which travels from multiple NodeBs, to achannelized STM-1 optical port. The network then communicates with the RNC through achannelized STM-1 optical port.

NOTE

If the NodeBs are distributed on different SDH rings, additional ADM/DXC devices are required.

IP Networking Based on MSTP

In this networking mode, the FG2a or GOUa board of the RNC serves as the Iub interface boardand supports board backup and FE/GE port backup.

Figure 5-6 shows the IP networking based on MSTP. FE/GE ports on the RNC serve the IPtransport.


Product Description


Issue 03 (2008-08-30)

Figure 5-6 IP networking based on MSTP

The MSTP device on the RNC side encapsulates Ethernet frames into a VC trunk and transmitsthem in transparent mode to the MSTP device on the NodeB side through the MSTP network.The MSTP device on the NodeB side then retrieves the Ethernet frames and sends them to theNodeB through the FE/GE ports.

IP Networking Based on Data Network

In this networking mode, the FG2a or GOUa board of the RNC serves as the Iub interface boardand supports board backup and FE/GE port backup.

Figure 5-7 shows the IP networking based on data network. FE/GE ports on the RNC serve theIP transport.

Figure 5-7 IP networking based on data network

The RNC accesses the router through the FE/GE port on the FG2a or GOUa board andcommunicates with the NodeBs through IP, Multiprotocol Label Switching (MPLS), or VirtualPrivate Network (VPN).

NOTE

MPLS and VPN help guarantee security of the IP transport.



5-7

IP Networking Based on Hybrid IP Transport

In this networking mode, the PEUa and FG2a/GOUa boards of the RNC serve as the Iub interfaceboards and support PEUa board backup, FG2a/GOUa board backup, and FE/GE port backup.

Figure 5-8 shows the IP networking based on hybrid IP transport. E1/T1 ports and FE/GE portson the RNC serve the hybrid IP transport.

Figure 5-8 IP networking based on hybrid IP transport

The RNC and the NodeB in this networking mode communicate with each other throughdifferent transport networks, which carry different types of data. The networks are described asfollows:

l The PDH or SDH network transmits data of real-time services with high QoS requirementson the Iub interface. The data can be NBAP signaling, RRC control signaling, and voiceservices. The NodeB obtains timing signals through the PDH or SDH network.

l The data network transmits data of services with low QoS requirements. The data can beHSDPA data, HSUPA data, or R99 background service data.

Advantages of the Networkingl IP-based access features lower cost than ATM-based access.

l IP networking provides high bandwidth to meet the requirements of high-speed dataservices, such as HSDPA and HSUPA.

l For data services, transport in IP over E1/T1 mode features higher efficiency than transportin ATM over E1/T1 mode.

l IP transport leads the development of transport technologies.

5.1.4 ATM/IP-Based Networking on the Iub InterfaceIn ATM/IP-based networking on the Iub interface, the RNC and the NodeB communicate basedon the ATM/IP dual stack, that is, based on the ATM and IP protocol stacks at the same time.

With the development of data services, especially with the introduction of High Speed DownlinkPacket Access (HSDPA) and High Speed Uplink Packet Access (HSUPA), the Iub interface hasan increasing demand for the bandwidth. A pure ATM network is expensive to operate. IPtransport saves the transmission cost but provides a lower guarantee of QoS than ATM transportdoes. Therefore, the ATM/IP dual stack is introduced. Services with different QoS requirementsare transmitted on different types of network.


Product Description


Issue 03 (2008-08-30)

Description of the NetworkingThe ATM/IP–based Iub interface allows hybrid transport of services that have different QoSrequirements. High-QoS services, such as voice services, streaming services, and the signaling,are transmitted on the ATM network. Low-QoS services, such as HSDPA and HSUPA services,are transmitted on the IP network.

Figure 5-9 shows the ATM/IP–based networking on the Iub interface.

Figure 5-9 ATM/IP-based networking on the Iub interface

To support this networking mode, the RNC is configured with both ATM and IP interface boards.l The ATM interface board connects to the ATM network through the E1/T1/channelized

STM-1 port.l The IP interface board connects to the IP network through the FE/GE/STM-1 port.

The NodeB is connected to the ATM and IP networks through its ATM and IP interface boardsrespectively.

Advantages of the Networkingl The ATM network guarantees the QoS.

l The IP network reduces the transmission cost and meets the requirement of high-speed dataservices for high bandwidth on the Iub interface.

Disadvantages of the NetworkingThe ATM/IP-based networking requires maintenance of both ATM and IP networks. Thisincreases the difficulty in and the cost for network maintenance to a certain extent.

5.1.5 Satellite-Based Networking on the Iub InterfaceIn satellite-based networking on the Iub interface, the RNC and the NodeB communicate throughthe satellite.

Scenario of the NetworkingUsually, the RNC and the NodeB communicate with each other through a land-based transportsystem, such as a PDH, SDH, MSTP, microwave, ATM, or IP network. On coastal islands or inremote, sparsely-populated, or uninhibited areas, no land-based transport system is available,



5-9

and it is difficult to deploy such a system. In such a situation, to enable the RNC to communicatewith remote NodeBs, satellite-based transmission applies.

Description of the NetworkingFigure 5-10 shows the satellite-based networking on the Iub interface.

Figure 5-10 Satellite-based networking on the Iub interface

The satellite transport network between the RNC and the NodeBs consists of the communicationssatellite and the earth stations. The RNC should be equipped with an earth station. The same istrue for each NodeB.l The communications satellite usually refers to a geosynchronous satellite.

l The earth station can be a large- or small-scaled station.– A large-scaled earth station, such as a large-scaled national or international

communication station, uses the large-aperture antenna to transmit high-speed data. Alarge-scaled earth station causes a high cost. User data should be converged on the earthstation through terrestrial communication networks before satellite communication.

– A small-scaled earth station, such as a Very Small Aperture Terminal (VSAT), uses thesmall-aperture antenna. The equipment features low cost and easy deployment.

NOTEThe interface between an earth station and the RNC or NodeB should comply with the ITU-T G.703recommendations.

Satellite Transmission BandsSatellite transmission usually uses the C or Ku band. Table 5-1 describes the frequency rangesand features of the two bands.


Product Description


Issue 03 (2008-08-30)

Table 5-1 Satellite transmission bands

Band Frequency Range Description

C l 3.7 GHz to 4.2 GHz

l 5.925 GHz to 6.425 GHz

l Small atmospheric absorption loss

l Little sensitivity to rainfall

l Sensitive to interference from terrestrialintra-band microwave communication

l Large antenna aperture

Ku l 11.7 GHz to 12.2 GHz

l 14 GHz to 14.5 GHz

l Sensitive to rainfall, snowfall, and fogs

l Sensitive to few intra-band interferencesources

l Flexible application zones

l Small antenna aperture

Advantages of the Networkingl This networking features wide coverage and easy deployment. It is insensitive to

topographic changes. The satellite receiver can be built almost anywhere on the earth.l The mobility is satisfactory. This networking can quickly satisfy the deployment demand

in special areas or emergency communication scenarios.l Bandwidth adjustment is flexible.

Disadvantages of the Networkingl The cost for building a satellite communication system and leasing satellite links is high.

l The transmission quality is sensitive to climatic and environmental changes. Errors intransmission may lead to degradation of voice or data service quality or sharp decline oftransmission efficiency.

l Compared with terrestrial transmission, satellite transmission has a high loopback delay of500 ms to 700 ms. A high delay may result in call failure.

5.1.6 2G/3G Concurrent Transmission and NetworkingIn 2G/3G concurrent transmission, the 2G and 3G information share transmission resources.This topic describes the networking for such transmission.

The fractional and timeslot cross connection functions provided by the AEUa board enable theRNC to share E1/T1 transmission resources with the 2G equipment.

Fractional FunctionThe fractional function converts ATM cells transmitted in the RNC to timeslot signals that aretransmitted through idle E1/T1 timeslots. One E1 frame has 32 timeslots numbered from 0 to31. All the timeslots except timeslot 0 are available for service data transmission. One T1 framehas 24 timeslots numbered from 1 to 24. All the timeslots are available for service datatransmission. The RNC should negotiate with the peer equipment about which timeslots carrythe ATM cells.



5-11

The fractional function consists of fractional ATM and fractional IMA. In fractional ATM mode,multiple idle timeslots can be selected to carry data. In fractional IMA mode, multiple fractionalIMA links are logically bound to a group and each fractional IMA link uses the same quantityof idle timeslots to carry data.

Timeslot Cross ConnectionTimeslot cross connection provides transfer connections between 2G and 3G equipment. Thus,the 2G and 3G data transmission share E1/T1 transmission resources. The networking modesfor 2G/3G concurrent transmission vary with the types of timeslot cross connection equipment.

Fractional-Based Networking with Timeslot Cross Connection on 2G EquipmentTo allow 2G/3G concurrent transmission in this networking mode, the 3G equipment (RNC andNodeB) provides the fractional function and the 2G equipment (BSC and BTS) provides thetimeslot cross connection function. Figure 5-11 shows the networking.

Figure 5-11 Fractional-based networking with timeslot cross connection on 2G equipment

The 3G equipment connects to the 2G equipment through the E1/T1 link. The 2G equipmentcross-connects the timeslots on the 3G E1/T1 link to the idle timeslots on the 2G E1/T1 link, soas to enable 2G/3G concurrent transmission.

Fractional-Based Networking with Timeslot Cross Connection on 3G EquipmentTo allow 2G/3G concurrent transmission in this networking mode, the 3G equipment (RNC andNodeB) provides the fractional and timeslot cross connection functions. Figure 5-12 shows thenetworking.


Product Description


Issue 03 (2008-08-30)

Figure 5-12 Fractional-based networking with timeslot cross connection on 3G equipment

The 2G equipment connects to the 3G equipment through the E1/T1 link. The 3G equipmentcross-connects the timeslots on the 2G E1/T1 link to the idle timeslots on the 3G E1/T1 link, soas to enable 2G/3G concurrent transmission.

Fractional-Based Networking with Timeslot Cross Connection on ExternalEquipment

To allow 2G/3G concurrent transmission in this networking mode, the 3G equipment (RNC andNodeB) provides the fractional function and the external equipment provides the timeslot crossconnection function. Figure 5-13 shows the networking.

Figure 5-13 Fractional-based networking with timeslot cross connection on external equipment

The 3G equipment and the 2G equipment connect to the Digital Cross-connect equipment (DXC)through the E1/T1 links. The DXC cross-connects the 2G and 3G E1/T1 timeslots to the timeslotson one E1/T1 link, so as to enable 2G/3G concurrent transmission.



5-13

5.2 Transport and Networking on the Iu/Iur InterfaceThis describes the interface boards and network solutions applicable to data transmissionbetween the RNC and the CN or neighboring RNC.

5.2.1 Interface Boards for the Iu or Iur InterfaceThe Iu and Iur interfaces support ATM transport and IP transport. Different types of interfaceboard are applicable to different modes of data transmission.

5.2.2 Networking Differences in 3GPP Protocol ReleasesThe networking on the Iu-CS interface varies with the CS domain equipment in the Core Network(CN) as specified by 3GPP R99 and R4/R5/R6.

5.2.3 ATM-Based Networking on the Iu or Iur InterfaceIn ATM-based networking on the Iu or Iur interface, the RNC and the CN or neighboring RNCcommunicate based on the ATM protocol stack.

5.2.4 IP-Based Networking on the Iu/Iur InterfaceIn IP-based networking on the Iu or Iur interface, the RNC and the CN or neighboring RNCcommunicate based on the IP protocol stack.

5.2.1 Interface Boards for the Iu or Iur InterfaceThe Iu and Iur interfaces support ATM transport and IP transport. Different types of interfaceboard are applicable to different modes of data transmission.

ATM-Based Iu/Iur Interface Boards

The following types of board are available for the ATM-based Iu-CS or Iur interface:


l AEUa board

l AOUa board

NOTE

Based on the traffic, the Iu-CS and Iur interfaces usually use the UOIa optical interface board that supportshigh traffic, and the Iub interface uses the AEUa or AOUa board that supports low traffic.

When ATM transport applies to the Iu-PS interface, the UOIa board (UOI_ATM) isrecommended to be used as the interface board.

IP-Based Iu/Iur Interface Boards

The following types of board are available for the IP-based Iu-CS or Iur interface:

l FG2a board

l GOUa board


l PEUa board

l POUa board


Product Description


Issue 03 (2008-08-30)

NOTE

Based on the traffic, the Iu-CS and Iur interfaces usually use the FG2a, GOUa, or UOIa board that supportshigh traffic, and the Iub interface uses the PEUa or POUa board that supports low traffic.

When IP transport applies to the Iu-PS interface, the FG2a, GOUa, or UOIa board (UOI_IP) isrecommended to be used as the interface board.

5.2.2 Networking Differences in 3GPP Protocol ReleasesThe networking on the Iu-CS interface varies with the CS domain equipment in the Core Network(CN) as specified by 3GPP R99 and R4/R5/R6.

Release 99As specified by 3GPP R99, the CS domain of the CN adopts the sole MSC to process CS controlplane and user plane data. The RNC directly connects to the MSC over the Iu-CS interface, asshown in Figure 5-14.

Figure 5-14 Iu-CS networking in R99

Releases 4/5/6As specified by 3GPP R4/R5/R6, the CS domain of the CN adopts the MSC server and the MGWto process CS control plane and user plane data respectively.l The MSC server performs the control function. It mainly processes RANAP signaling on

the Iu-CS control plane.l The MGW performs the bearer function. It mainly processes user plane data and ALCAP

signaling on the Iu-CS interface.

The only signaling communication between the RNC and the MSC server requires a lowbandwidth. Therefore, no direct connection between the RNC and the MSC server exists incommon cases. Instead, they communicate through the signaling forwarding at the MGW, asshown in Figure 5-15.



5-15

Figure 5-15 Iu-CS networking in R4/R5/R6

5.2.3 ATM-Based Networking on the Iu or Iur InterfaceIn ATM-based networking on the Iu or Iur interface, the RNC and the CN or neighboring RNCcommunicate based on the ATM protocol stack.

Scenario of the NetworkingThe RNC and the CN or neighboring RNC can communicate with each other through the existingSDH or ATM network.

Networking Based on SDH with MSP Backup Between Optical PortsIn this networking mode, the UOIa board (UOI_ATM) of the RNC serves as the Iu/Iur interfaceboard. The RNC accesses the SDH network through the unchannelized STM-1 optical port onthe UOIa board.

Figure 5-16 shows the networking based on SDH with MSP backup between optical ports.


Product Description


Issue 03 (2008-08-30)

Figure 5-16 Networking based on SDH with MSP backup between optical ports

In this networking mode, each Iu-CS, Iu-PS, or Iur interface requires a pair of STM-1 opticalcables for MSP 1+1 or MSP 1:1 backup. In a case other than direct connection between the RNCand the MSC or SGSN, the section-specific MSP backup at the RNC protects only the opticalchannels between the RNC and the ADM, instead of all those between the RNC and the MSCor SGSN.

Networking Based on SDH with Load Sharing Between Optical PortsIn this networking mode, the UOIa board (UOI_ATM) of the RNC serves as the Iu/Iur interfaceboard. The RNC accesses the SDH network through the unchannelized STM-1 optical port onthe UOIa board.

Figure 5-17 shows the networking based on SDH with load sharing between optical ports.



5-17

Figure 5-17 Networking based on SDH with load sharing between optical ports

In this networking mode, the two UOIa boards for the Iu or Iur interface are not configured forbackup. The Iu/Iur control plane PVCs are shared by two optical ports on different UOIa boards.The same is true for the Iu/Iur user plane PVCs. Thus, the two optical ports share the load. Ifone of the optical ports is faulty, it is isolated and the services carried on it are disrupted. Thenthe traffic on the Iu or Iur interface reduces by half.

Networking Based on SDH with STM-1 Shared by Iu and IurIn this networking mode, the UOIa board (UOI_ATM) of the RNC serves as the Iu/Iur interfaceboard. The RNC accesses the SDH network through the unchannelized STM-1 optical port onthe UOIa board.

Figure 5-18 shows the networking based on SDH with STM-1 shared by Iu and Iur.


Product Description


Issue 03 (2008-08-30)

Figure 5-18 Networking based on SDH with STM-1 shared by Iu and Iur

Usually, the traffic on the Iur interface is low. Therefore, when the RNC is connected to a numberof neighboring RNCs over Iur interfaces where traffic is low, the Iu and Iur interfaces can sharean STM-1 transmission resource to transmit data before the MGW separates the Iu PVC fromthe Iur PVC by using VC or VP switching.

Networking Based on ATMIn this networking mode, the UOIa board (UOI_ATM) of the RNC serves as the Iu/Iur interfaceboard. The RNC accesses the ATM network through the unchannelized STM-1 optical port onthe UOIa.

Figure 5-19 shows the networking based on ATM.



5-19

Figure 5-19 Networking based on ATM

In this networking mode, each Iu-CS, Iu-PS, or Iur interface requires a pair of STM-1 opticalcables for MSP 1+1 or MSP 1:1 backup. The MSP backup is section-specific. The RNC adoptsMSP backup to protect only the optical channels between the RNC and the ATM switch insteadof all those between the RNC and the MSC or SGSN. In the case of direct connection on the Iu-CS or Iu-PS interface, however, the MSP backup at the RNC protects all the connections betweenthe RNC and the MSC or SGSN.

NOTE

l STM-1 sharing between the Iu and Iur interfaces is applicable to the ATM-based networking. In thiscase, the Iu and Iur interfaces share a pair of STM-1 optical cables to transmit data before the ATMswitch separates the Iu PVC from the Iur PVC by using VC or VP switching.

l Load sharing is also applicable to the ATM-based networking. This networking mode is similar to theSDH-based networking with load sharing between optical ports.

Advantages of the Networking

The advantages of each type of networking are as follows:

l Networking based on SDH with MSP backup between optical ports

The transmission backup provided by this network solution helps guarantee hightransmission reliability.

l Networking based on SDH with load sharing between optical ports

This network solution saves the optical ports and cables that serve the data transmissionbetween the RNC and the ADM, thus improving the optical resource utilization.

l Networking based on SDH with STM-1 shared by Iu and Iur

In the case of a large number of Iur interfaces, if each Iur interface occupies one STM-1port, the demand for transmission resources is high and the resource utilization is low. TheSDH-based networking with STM-1 shared by Iu and Iur is resource-effective.


Product Description


Issue 03 (2008-08-30)

l Networking based on ATMThe Iu, Iur, and Iub interfaces can share a port or board for data transmission, thus savingthe transmission resources and improving the resource utilization.

Disadvantages of the NetworkingThe disadvantages of each type of networking are as follows:l Networking based on SDH with MSP backup between optical ports

For transmission backup, this network solution requires a double share of optical port andcable resources.

l Networking based on SDH with load sharing between optical portsThis network solution does not provide transmission backup, thus failing to achieve hightransmission reliability. If an optical port or cable is faulty, the ongoing services carried onthe faulty part are disrupted.

l Networking based on SDH with STM-1 shared by Iu and IurThis network solution requires VC/VP switching at the MGW, thus increasing the load ofthe MGW.

l Networking based on ATMATM equipment has a high cost and ATM networks take a shrinking share. It is notrecommended that extra ATM networks be built for Iu and Iur transmission.

5.2.4 IP-Based Networking on the Iu/Iur InterfaceIn IP-based networking on the Iu or Iur interface, the RNC and the CN or neighboring RNCcommunicate based on the IP protocol stack.

Scenario of the NetworkingThe RNC and the CN or neighboring RNC can communicate with each other through the IPnetwork.

Single-Homing Layer 3 NetworkingIn this networking mode, the FG2a or GOUa board of the RNC serves as the Iu or Iur interfaceboard and supports board backup and FE/GE port backup.

Figure 5-20 shows the single-homing layer 3 networking. FE/GE ports on the RNC serve theIP transport.



5-21

Figure 5-20 Single-homing layer 3 networking

In this networking mode, the FE/GE ports of the RNC are configured for backup. The activeand standby FE/GE ports of the RNC connect to the Provider Edge (PE), which further connectsto the data network. The active and standby FE/GE ports of the RNC share one IP address, thatis, IP1-1. The PE configures the active and standby ports of the RNC in one VLAN and usesone interface IP address of the VLAN, that is, IP1-0.

NOTE

The GE optical ports on the GOUa board are applicable to the scenario where the RNC is far away fromthe PE, and the FE/GE electrical ports on the FG2a board are applicable when the distance between theRNC and the PE is within 100 meters.

Dual-Homing Layer 3 NetworkingIn this networking mode, the FG2a or GOUa board of the RNC serves as the Iu or Iur interfaceboard and supports board backup and FE/GE port backup.

Figure 5-21 shows the dual-homing layer 3 networking. FE/GE ports on the RNC serve the IPtransport.


Product Description


Issue 03 (2008-08-30)

Figure 5-21 Dual-homing layer 3 networking

In this networking mode, the FE/GE ports of the RNC are configured for backup. The activeand standby FE/GE ports of the RNC connect to two PEs, which further connect to the datanetwork. Complying with the Virtual Router Redundancy Protocol (VRRP), the two PEs provideredundancy-based protection for the data transmitted from the RNC. One PE connects to theother through two GE ports. Link Aggregation (LAG) is applied to the interconnection linksbetween the PEs to increase the bandwidth and reliability of the links. The active and standbyFE/GE ports of the RNC share one IP address, that is, IP1-1. The PEs configure the active andstandby ports of the RNC in one VLAN and use one virtual VRRP IP address, that is, IP1-0.

NOTE

The GE optical ports on the GOUa board are applicable to the scenario where the RNC is far away fromthe PE, and the FE/GE electrical ports on the FG2a board are applicable when the distance between theRNC and the PE is within 100 meters.

Direct Connection with Load SharingIn this networking mode, the FG2a or GOUa board of the RNC serves as the Iu or Iur interfaceboard, which directly connects to the MGW, SGSN, or neighboring RNC.

Figure 5-22 shows the direct connection with load sharing. FE/GE ports on the RNC serve theIP transport.

Figure 5-22 Direct connection with load sharing

When the RNC and the MGW, SGSN, or neighboring RNC are located in the same equipmentroom, direct connection through FE/GE ports is applicable to the Iu or Iur interface. This network



5-23

solution does not involve any extra transport network or equipment. In this networking mode,the FG2a or GOUa boards can work in board backup mode, and the FE/GE ports work in loadsharing mode to carry services.

Networking Based on SDH with MSP Backup Between Optical Ports

In this networking mode, the UOIa board (UOI_IP) of the RNC serves as the Iu/Iur interfaceboard. The RNC accesses the SDH network through the unchannelized STM-1 optical port onthe UOIa board.

Figure 5-23 shows the networking based on SDH with MSP backup between optical ports.

Figure 5-23 Networking based on SDH with MSP backup between optical ports

In this networking mode, each Iu-CS, Iu-PS, or Iur interface requires a pair of STM-1 opticalcables for MSP 1+1 or MSP 1:1 backup. In a case other than direct connection between the RNCand the MSC or SGSN, the section-specific MSP backup at the RNC protects only the opticalchannels between the RNC and the ADM, instead of all those between the RNC and the MSCor SGSN.

Networking Based on SDH with Load Sharing Between Optical Ports

In this networking mode, the UOIa board (UOI_IP) of the RNC serves as the Iu/Iur interfaceboard. The RNC accesses the SDH network through the unchannelized STM-1 optical port onthe UOIa board.

Figure 5-24 shows the networking based on SDH with load sharing between optical ports.


Product Description


Issue 03 (2008-08-30)

Figure 5-24 Networking based on SDH with load sharing between optical ports

In this networking mode, the two UOIa boards for the Iu or Iur interface are not configured forbackup. The two optical ports share the load. If one of the optical ports is faulty, it is isolatedand the services carried on it are disrupted. Then the traffic on the Iu or Iur interface reduces byhalf.

Networking Based on SDH with STM-1 Shared by Iu and IurIn this networking mode, the UOIa board (UOI_IP) of the RNC serves as the Iu/Iur interfaceboard. The RNC accesses the SDH network through the unchannelized STM-1 optical port onthe UOIa board.

Figure 5-25 shows the networking based on SDH with STM-1 shared by Iu and Iur.



5-25

Figure 5-25 Networking based on SDH with STM-1 shared by Iu and Iur

Usually, the traffic on the Iur interface is low. Therefore, when the RNC is connected to a numberof neighboring RNCs over Iur interfaces where traffic is low, the Iu and Iur interfaces can sharean STM-1 transmission resource.

Advantages of the Networking

The advantages of each type of networking are as follows:

l Single-homing layer 3 networking

This network solution provides redundancy-based protection for FE/GE links. The singlePE saves networking cost.

l Dual-homing layer 3 networking

This network solution provides redundancy-based protection not only for FE/GE links butalso for PE devices.

l Direct connection with load sharing

This network solution does not require any LAN switch or router, thus featuring lownetworking cost and high transmission reliability.

l Networking based on SDH with MSP backup between optical ports

The transmission backup provided by this network solution helps guarantee hightransmission reliability.

l Networking based on SDH with load sharing between optical ports

This network solution saves the optical ports and cables that serve the data transmissionbetween the RNC and the ADM, thus improving the optical resource utilization.

l Networking based on SDH with STM-1 shared by Iu and Iur


Product Description


Issue 03 (2008-08-30)

In the case of a large number of Iur interfaces, if each Iur interface occupies one STM-1port, the demand for transmission resources is high and the resource utilization is low. TheSDH-based networking with STM-1 shared by Iu and Iur is resource-effective.

Disadvantages of the NetworkingThe disadvantages of each type of networking are as follows:l Single-homing layer 3 networking

The single PE cannot provide PE-level protection.l Dual-homing layer 3 networking

The dual PEs cause a high networking cost.l Direct connection with load sharing

This network solution does not provide redundancy for data transmission. A port failurewill lead to the decline of transmission capacity.

l Networking based on SDH with MSP backup between optical portsFor transmission backup, this network solution requires a double share of optical port andcable resources.

l Networking based on SDH with load sharing between optical portsThis network solution does not provide transmission backup, thus failing to achieve hightransmission reliability. If an optical port or cable is faulty, the ongoing services carried onthe faulty part are disrupted.

l Networking based on SDH with STM-1 shared by Iu and IurThis network solution increases the load of the MGW.

5.3 Transport and Networking on the Iu-BC InterfaceThis part describes the interface boards and network solutions applicable to data transmissionbetween the RNC and the CBC.

5.3.1 Interface Boards for the Iu-BC InterfaceThe Iu-BC interface supports ATM transport and IP transport. Different types of interface boardare applicable to different modes of data transmission.

5.3.2 ATM-Based Networking on the Iu-BC InterfaceIn ATM-based networking on the Iu-BC interface, the RNC and the CBC communicate basedon the ATM protocol stack.

5.3.3 IP-Based Networking on the Iu-BC InterfaceIn IP-based networking on the Iu-BC interface, the RNC and the CBC communicate based onthe IP protocol stack.

5.3.1 Interface Boards for the Iu-BC InterfaceThe Iu-BC interface supports ATM transport and IP transport. Different types of interface boardare applicable to different modes of data transmission.



5-27

ATM-Based Iu-BC Interface BoardsWhen applied with ATM transport, the Iu-BC interface shares the interface board UOIa(UOI_ATM) with the Iu-PS interface.

IP-Based Iu-BC Interface BoardsThe following types of board are available for the IP-based Iu-BC interface:l FG2a board

l GOUa board


5.3.2 ATM-Based Networking on the Iu-BC InterfaceIn ATM-based networking on the Iu-BC interface, the RNC and the CBC communicate basedon the ATM protocol stack.

Scenario of the NetworkingThe RNC and the CBC can communicate with each other through the SDH network.

Description of the NetworkingIn this networking mode, the UOIa board (UOI_ATM) of the RNC serves as the Iu-BC interfaceboard and supports board backup and MSP 1+1 or MSP 1:1 optical port backup.

Figure 5-26 shows the ATM-based networking on the Iu-BC interface. Unchannelized STM-1optical ports on the RNC serve the ATM transport.

Figure 5-26 ATM-based networking on the Iu-BC interface

In this networking mode, the RNC is connected to the CBC through the SGSN. On the Iu-BCinterface, usually only the FE port on the CBC server is connected to the SGSN, and an IPoAPVC is configured between the RNC and the SGSN. The SGSN performs route forwardingbetween the IPoA PVC and the FE link. When ATM transport is applied to the Iu-PS interface,


Product Description


Issue 03 (2008-08-30)

this network solution makes efficient use of the physical transmission resources on the Iu-PSinterface.

5.3.3 IP-Based Networking on the Iu-BC InterfaceIn IP-based networking on the Iu-BC interface, the RNC and the CBC communicate based onthe IP protocol stack.

Scenario of the NetworkingThe RNC and the CBC can communicate with each other through the data network.

IP Networking Based on Data NetworkIn this networking mode, the FG2a or GOUa board of the RNC serves as the Iu-BC interfaceboard and supports board backup and FE/GE port backup.

Figure 5-27 shows the IP networking based on the data network. FE/GE ports on the RNC servethe IP transport.

Figure 5-27 IP networking based on data network

When IP transport based on the data network is applied to the Iu interface, the RNC and the CBCcan be directly connected to the IP network, which provides connections on the Iu-BC interface.Physically, an Iu-BC interface can share an FE/GE port at the RNC with an Iu interface, becauseof the low traffic on the Iu-BC interface. For details about the physical connections for IPtransport on the Iu interface, refer to 5.2.4 IP-Based Networking on the Iu/Iur Interface.

5.4 RNC OM NetworkingThe RNC OM networking provides operation and maintenance for the RNC and NodeB.

Figure 5-28 shows the RNC OM networking.



5-29

Figure 5-28 RNC OM networking

As shown in Figure 5-28, either local or remote maintenance is applicable to the RNC andNodeB. Local maintenance is performed on the LMT, and remote maintenance is performedthrough the OM network. The RNC-NodeB OM channel is configurable. Through the OMchannel, remote maintenance of the NodeB can be performed on the Network ManagementSystem (NMS), M2000, or NodeB LMT.


Product Description


Issue 03 (2008-08-30)

6 RNC Parts Reliability

About This Chapter

The RNC guarantees its operation reliability by means of board redundancy and port redundancy.

6.1 Concepts Related to RNC Parts ReliabilityThe concepts related to RNC parts reliability are RNC board backup types, RNC port backuptypes, resource pool, port trunking, and port load sharing.

6.2 RNC Board RedundancyRNC board redundancy is of two types: board backup and resource pool.

6.3 RNC Port RedundancyRNC port redundancy is of three types: port backup, port load sharing, and port trunking.

RNCProduct Description 6 RNC Parts Reliability


6-1

6.1 Concepts Related to RNC Parts ReliabilityThe concepts related to RNC parts reliability are RNC board backup types, RNC port backuptypes, resource pool, port trunking, and port load sharing.

6.1.1 RNC Backup TypesRNC backup consists of board backup and port backup.

6.1.2 Resource PoolIn resource pool mode, the resource nodes with the same characteristics work as a resource pool.The resources in this pool are allocated and managed according to the negotiation on thecapabilities and status of each resource node.

6.1.3 Port TrunkingPort trunking enables multiple physical ports to be grouped into one logical port. This technologyhelps enhance reliability of data transmission.

6.1.4 Load Sharing Between FE/GE PortsWhen load sharing is implemented between FE/GE ports, the RNC distributes the data streamsthat have the same destination to different physical ports, so that the ports can share the load.

6.1.1 RNC Backup TypesRNC backup consists of board backup and port backup.

Board BackupWhen two boards work in backup mode, one board is active and the other is standby. Servicescan be processed by either the active board only or both the active and standby boards. If theactive board is faulty, the RNC automatically switches over the active and standby boards.

Port BackupWhen two ports work in backup mode, one port is active and the other is standby. Services canbe transmitted through either the active port only or both the active and standby ports. If theactive port is faulty, the RNC automatically switches over the active and standby ports.

6.1.2 Resource PoolIn resource pool mode, the resource nodes with the same characteristics work as a resource pool.The resources in this pool are allocated and managed according to the negotiation on thecapabilities and status of each resource node.

In resource pool mode, the RNC allocates the services accessing the resource pool tocorresponding resource nodes and provides appropriate service resources.

6.1.3 Port TrunkingPort trunking enables multiple physical ports to be grouped into one logical port. This technologyhelps enhance reliability of data transmission.

Port trunking works in trunk groups. Multiple physical links form a trunk group. If a physicallink in the trunk group becomes unavailable, the data carried on the faulty link is transmitted on

6 RNC Parts ReliabilityRNC

Product Description


Issue 03 (2008-08-30)

other links in the trunk group. Thus, the link failure does not disrupt proper communicationbetween both ends of the trunk group.

The traffic on the trunk group can reach a maximum of the total traffic on all the physical linksin the trunk group. Port trunking helps enhance transmission reliability and increase transmissionbandwidth.

6.1.4 Load Sharing Between FE/GE PortsWhen load sharing is implemented between FE/GE ports, the RNC distributes the data streamsthat have the same destination to different physical ports, so that the ports can share the load.

The FE/GE ports working in load sharing mode have an independent IP address for each, so thateach port can receive and transmit data packets. If a port is faulty, the RNC stops distributingdata to the faulty port and transfers the data to other ports.

6.2 RNC Board RedundancyRNC board redundancy is of two types: board backup and resource pool.

6.2.1 Backup of OMUa BoardsWhen the RNC is configured with two OMUa boards, the two boards work in active/standbymode.

6.2.2 Backup of SCUa BoardsThe RNC is configured with two SCUa boards in the RSS subrack and each RBS subrack. Thetwo boards work in active/standby mode.

6.2.3 Backup of SPUa BoardsWhen two SPUa boards are configured in active/standby slots in a subrack of the RNC, the twoboards work in active/standby mode.

6.2.4 Backup of GCUa/GCGa BoardsThe RNC is configured with two GCUa/GCGa boards in the RSS subrack. The two boards workin active/standby mode.

6.2.5 Backup of AEUa BoardsWhen two AEUa boards are configured in active/standby slots in a subrack of the RNC, the twoboards can be set to work in active/standby mode.

6.2.6 Backup of PEUa BoardsWhen two PEUa boards are configured in active/standby slots in a subrack of the RNC, the twoboards can be set to work in active/standby mode.

6.2.7 Backup of AOUa BoardsWhen two AOUa boards are configured in active/standby slots in a subrack of the RNC, the twoboards can be set to work in board and port backup mode.

6.2.8 Backup of POUa BoardsWhen two POUa boards are configured in active/standby slots in a subrack of the RNC, the twoboards can be set to work in board and port backup mode.

6.2.9 Backup of UOIa BoardsWhen two UOIa boards are configured in active/standby slots in a subrack of the RNC, the twoboards can be set to work in board and port backup mode.

6.2.10 Backup of FG2a/GOUa Boards



6-3

When two FG2a/GOUa boards are configured in active/standby slots in a subrack of the RNC,the two boards can be set to work in one of the following two modes: board backup with no portbackup and board backup with port backup.

6.2.11 Resource Pool of DPUb BoardsThe DPUb boards of the RNC and the Digital Signal Processors (DSPs) of each DPUb work inresource pool mode.

6.2.1 Backup of OMUa BoardsWhen the RNC is configured with two OMUa boards, the two boards work in active/standbymode.

Description of the Backup

When the OMUa boards work in backup mode, one OMUa is active and the other is standby.The active board processes services, and the standby board synchronizes its data with that onthe active board in real time.

Switchover Modesl Automatic switchover: The active and standby OMUa boards can be switched over

automatically.l Manual switchover: You can use the SWP BAM command to forcibly switch over the

active and standby OMUa boards.

Prerequisites for Switchoverl Automatic switchover: can be triggered only when a certain condition is fulfilled. Such a

condition can be one of the following:– The standby OMUa fails to detect the heartbeat information of the active OMUa for 5

minutes in succession.– The active OMUa fails to detect the virtual IP address for 3 minutes in succession, but

the standby OMUa works properly.– Both the active and standby OMUa boards work properly for one period, and no

switchover occurs during the period.

NOTE

The default period for automatic switchover between the active and standby OMUa boards is 90days. You can also use the SET ASWPARA command to set the period for automatic switchover.

l Manual switchover: can be performed only when the standby OMUa works properly andthe status of data synchronization between the active and standby OMUa boards isNormal.

NOTE

You can also use the DSP BAM command to query the status of data synchronization between theactive and standby OMUa boards.

Switchover Process

When the active and standby OMUa boards are switched over, the active OMUa becomesstandby, and the other OMUa becomes active.


Product Description


Issue 03 (2008-08-30)

Impact of Switchover on the System

The switchover between the active and standby OMUa boards takes about 1 minute. The datasynchronization after the switchover takes about 2 minutes. During the switchover, thecommunication between the OM terminal and the host boards is interrupted for about 1 or 2minutes. Then, you cannot perform operation and maintenance on the RNC. The switchover,however, does not affect ongoing services of the RNC.

6.2.2 Backup of SCUa BoardsThe RNC is configured with two SCUa boards in the RSS subrack and each RBS subrack. Thetwo boards work in active/standby mode.


The SCUa processes the data on the switching plane and the control plane. When the SCUaboards work in backup mode, one SCUa is active and the other is standby. The standby boardsynchronizes its data with that on the active board in real time. Control plane data is processedby the active SCUa, and switching plane data is processed by both the active and standby SCUaboards.

Switchover Modesl Automatic switchover: The active and standby SCUa boards can be switched over

automatically.

l Manual switchover: You can use the SWP BRD command to forcibly switch over the activeand standby SCUa boards.

Prerequisites for Switchover

The active and standby SCUa boards can be switched over only when one of the followingconditions is fulfilled:

l The active SCUa is reset, but the standby SCUa works properly.

l The active SCUa is faulty, but the standby SCUa works properly.

l The clock source of the active SCUa is faulty, but that of the standby SCUa works properly.

Switchover Process

When the active and standby SCUa boards are switched over, the active SCUa becomes standbyafter being reset, and the other SCUa becomes active.


The switchover between the active and standby SCUa boards does not affect ongoing services.

6.2.3 Backup of SPUa BoardsWhen two SPUa boards are configured in active/standby slots in a subrack of the RNC, the twoboards work in active/standby mode.



6-5


When the SPUa boards work in backup mode, one SPUa is active and the other is standby. Theactive board processes services, and the standby board synchronizes its data with that on theactive board in real time.

Switchover Modesl Automatic switchover: The active and standby SPUa boards can be switched over

automatically.l Manual switchover: You can use the SWP BRD command to forcibly switch over the active

and standby SPUa boards.


The active and standby SPUa boards can be switched over only when one of the followingconditions is fulfilled:l The active SPUa is reset, but the standby SPUa works properly.

l The active SPUa is faulty, but the standby SPUa works properly.

Switchover Process

When the active and standby SPUa boards are switched over, the active SPUa becomes standbyafter being reset, and the other SPUa becomes active.


The switchover between the active and standby SPUa boards does not affect ongoing services.

6.2.4 Backup of GCUa/GCGa BoardsThe RNC is configured with two GCUa/GCGa boards in the RSS subrack. The two boards workin active/standby mode.


When the GCUa/GCGa boards work in backup mode, one GCUa/GCGa is active and the otheris standby. The active board processes services, and the standby board synchronizes its data withthat on the active board in real time.

Switchover Modesl Automatic switchover: The active and standby GCUa/GCGa boards can be switched over


and standby GCUa/GCGa boards.


The active and standby GCUa/GCGa boards can be switched over only when one of the followingconditions is fulfilled:


Product Description


Issue 03 (2008-08-30)

l The active GCUa/GCGa is reset, but the standby GCUa/GCGa works properly.

l The active GCUa/GCGa is faulty, but the standby GCUa/GCGa works properly.

l The clock source of the active GCUa/GCGa is faulty, but that of the standby GCUa/GCGaworks properly.

NOTE

The active and standby GCGa boards can be switched over also when the GPS card of the active GCGa isfaulty but that of the standby GCGa works properly.

Switchover Process

When the active and standby GCUa/GCGa boards are switched over, the active GCUa/GCGabecomes standby after being reset, and the other GCUa/GCGa becomes active.


The switchover between the active and standby GCUa/GCGa boards does not affect ongoingservices.

6.2.5 Backup of AEUa BoardsWhen two AEUa boards are configured in active/standby slots in a subrack of the RNC, the twoboards can be set to work in active/standby mode.


When the AEUa boards are set to work in backup mode, one AEUa is active and the other isstandby. The standby board synchronizes its data with that on the active board in real time. Theactive and standby boards are connected to their peers through Y-shaped E1/T1 cables. Only theE1/T1 ports on the active board receive, transmit, and process data.

During the addition of a board through the ADD BRD command, the backup of the AEUa boardsis configurable.

Switchover Modes

You can use the SWP BRD command to forcibly switch over the active and standby AEUaboards.


The active and standby AEUa boards can be switched over only when one of the followingconditions is fulfilled:

l The active AEUa is reset, but the standby AEUa works properly.

l The active AEUa is faulty, but the standby AEUa works properly.

Switchover Process

When the active and standby AEUa boards are switched over, the active AEUa becomes standbyafter being reset, and the other AEUa becomes active.



6-7

Impact of Switchover on the SystemThe switchover between the active and standby AEUa boards slightly affects the datatransmission on IMA links but does not interrupt ongoing services.

6.2.6 Backup of PEUa BoardsWhen two PEUa boards are configured in active/standby slots in a subrack of the RNC, the twoboards can be set to work in active/standby mode.

Description of the BackupWhen the PEUa boards are set to work in backup mode, one PEUa is active and the other isstandby. The standby board synchronizes its data with that on the active board in real time. Theactive and standby boards are connected to their peers through Y-shaped E1/T1 cables. Only theE1/T1 ports on the active board receive, transmit, and process data.

During the addition of a board through the ADD BRD command, the backup of the PEUa boardsis configurable.

Switchover ModesYou can use the SWP BRD command to forcibly switch over the active and standby PEUaboards.

Prerequisites for SwitchoverThe active and standby PEUa boards can be switched over only when one of the followingconditions is fulfilled:l The active PEUa is reset, but the standby PEUa works properly.

l The active PEUa is faulty, but the standby PEUa works properly.

Switchover ProcessWhen the active and standby PEUa boards are switched over, the active PEUa becomes standbyafter being reset, and the other PEUa becomes active.

Impact of Switchover on the SystemThe switchover between the active and standby PEUa boards slightly affects the datatransmission on PPP/MLPPP links but does not interrupt ongoing services.

6.2.7 Backup of AOUa BoardsWhen two AOUa boards are configured in active/standby slots in a subrack of the RNC, the twoboards can be set to work in board and port backup mode.

Description of the BackupWhen the AOUa boards are set to work in backup mode, one AOUa is active and the other isstandby. The standby board synchronizes its data with that on the active board in real time. MSP1:1 applies to the backup between the optical ports. Services are processed by the board wherethe active port is located. Active ports, however, may be located on both the active and standby


Product Description


Issue 03 (2008-08-30)

boards, because the switchover between the optical ports on the active/standby boards does notaffect the active/standby relationship between the boards. In that case, both the active andstandby boards can process services. For details about the backup of AOUa optical ports, referto 6.3.1 Backup of AOUa Optical Ports.

During the addition of a board through the ADD BRD command, the backup of the AOUa boardsis configurable. If Backup is set to YES, the backup mode of the AOUa boards is board andport backup mode. Therefore, the backup mode of the optical ports does not need to be set again.

Switchover Modesl Automatic switchover: The active and standby AOUa boards can be switched over


and standby AOUa boards.


The active and standby AOUa boards can be switched over only when one of the followingconditions is fulfilled:l The active AOUa is reset, but the standby AOUa works properly.

l The active AOUa is faulty, but the standby AOUa works properly.

Switchover Process

When the active and standby AOUa boards are switched over, the active AOUa becomes standbyafter being reset, and the other AOUa becomes active.

NOTE

After the active and standby boards are switched over, the RNC performs active/standby arbitration on theports, based on the strategy specified by the MSP protocol.


The switchover between the active and standby AOUa boards slightly affects the datatransmission on IMA links but does not interrupt ongoing services.

6.2.8 Backup of POUa BoardsWhen two POUa boards are configured in active/standby slots in a subrack of the RNC, the twoboards can be set to work in board and port backup mode.


When the POUa boards are set to work in backup mode, one POUa is active and the other isstandby. The standby board synchronizes its data with that on the active board in real time.Optical ports on the POUa boards work in MSP 1:1 or MSP 1+1 mode. Services are processedby the board where the active port is located. Active ports, however, may be located on both theactive and standby boards, because the switchover between the optical ports on the active/standby boards does not affect the active/standby relationship between the boards. In that case,both the active and standby boards can process services. For details about the backup of POUaoptical ports, refer to 6.3.2 Backup of POUa Optical Ports.



6-9

During the addition of a board through the ADD BRD command, the backup of the POUa boardsis configurable. If Backup is set to YES, the backup mode of the POUa boards is board andport backup mode. Therefore, the backup mode of the optical ports does not need to be set again.

Switchover Modesl Automatic switchover: The active and standby POUa boards can be switched over

automatically.

l Manual switchover: You can use the SWP BRD command to forcibly switch over the activeand standby POUa boards.


The active and standby POUa boards can be switched over only when one of the followingconditions is fulfilled:

l The active POUa is reset, but the standby POUa works properly.

l The active POUa is faulty, but the standby POUa works properly.

Switchover Process

When the active and standby POUa boards are switched over, the active POUa becomes standbyafter being reset, and the other POUa becomes active.

NOTE



The switchover between the active and standby POUa boards slightly affects the datatransmission but does not interrupt ongoing services.

6.2.9 Backup of UOIa BoardsWhen two UOIa boards are configured in active/standby slots in a subrack of the RNC, the twoboards can be set to work in board and port backup mode.


When the UOIa boards are set to work in backup mode, one UOIa is active and the other isstandby. The standby board synchronizes its data with that on the active board in real time. MSP1:1 or MSP 1+1 applies to the backup between the optical ports. Services are processed by theboard where the active port is located. Active ports, however, may be located on both the activeand standby boards, because the switchover between the optical ports on the active/standbyboards does not affect the active/standby relationship between the boards. In that case, both theactive and standby boards can process services. For details about the backup of UOIa opticalports, refer to 6.3.3 Backup of UOIa Optical Ports.

During the addition of a board through the ADD BRD command, the backup of the UOIa boardsis configurable. If Backup is set to YES, the backup mode of the UOIa boards is board and portbackup mode. Therefore, the backup mode of the optical ports does not need to be set again.


Product Description


Issue 03 (2008-08-30)

Switchover Modesl Automatic switchover: The active and standby UOIa boards can be switched over


and standby UOIa boards.

Prerequisites for SwitchoverThe active and standby UOIa boards can be switched over only when one of the followingconditions is fulfilled:l The active UOIa is reset, but the standby UOIa works properly.

l The active UOIa is faulty, but the standby UOIa works properly.

Switchover ProcessWhen the active and standby UOIa boards are switched over, the active UOIa becomes standbyafter being reset, and the other UOIa becomes active.

NOTE


Impact of Switchover on the SystemWhen the traffic carried on the optical ports of the UOIa boards is high, the switchover betweenthe active and standby UOIa boards slightly affects the data transmission but does not interruptongoing services.

6.2.10 Backup of FG2a/GOUa BoardsWhen two FG2a/GOUa boards are configured in active/standby slots in a subrack of the RNC,the two boards can be set to work in one of the following two modes: board backup with no portbackup and board backup with port backup.

Description of the BackupWhen the FG2a/GOUa boards are set to work in backup mode, one FG2a/GOUa is active andthe other is standby. The standby board synchronizes its data with that on the active board inreal time.

During the addition of a board through the ADD BRD command, the backup of the FG2a/GOUaboards is configurable. If Backup is set to YES, the backup mode of the FG2a/GOUa boards isboard backup while no port backup mode.

When FG2a/GOUa boards work in board backup mode, you can use the ADDETHREDPORT command to set the backup of FE/GE ports. For details about backup of FE/GE ports, refer to 6.3.4 Backup of FE/GE Ports.

Switchover Modesl Automatic switchover: The active and standby FG2a/GOUa boards can be switched over

automatically.



6-11

l Manual switchover: You can use the SWP BRD command to forcibly switch over the activeand standby FG2a/GOUa boards.

Prerequisites for SwitchoverThe active and standby FG2a/GOUa boards can be switched over only when one of the followingconditions is fulfilled:l The active FG2a/GOUa is reset, but the standby FG2a/GOUa works properly.

l The active FG2a/GOUa is faulty, but the standby FG2a/GOUa works properly.

Switchover ProcessWhen the active and standby FG2a/GOUa boards are switched over, the active FG2a/GOUabecomes standby after being reset, and the other FG2a/GOUa becomes active.

NOTE

When the FG2a/GOUa boards work in board and port backup mode, after the active/standby switchover,the RNC performs active/standby arbitration on the ports and re-sets the port load sharing strategy.

Impact of Switchover on the Systeml When the FG2a/GOUa boards work in board backup while no port backup mode, the

switchover between the active and standby boards does not affect ongoing services.l When the FG2a/GOUa boards work in board and port backup mode, the switchover

between the active and standby boards slightly affects the data transmission but does notinterrupt ongoing services.

6.2.11 Resource Pool of DPUb BoardsThe DPUb boards of the RNC and the Digital Signal Processors (DSPs) of each DPUb work inresource pool mode.

Board Resource PoolAll the DPUb boards in a subrack work as a resource pool. The RNC can appropriately scheduleand allocate resources for the associated services between the boards.

DSP Resource PoolAll the DSPs on the DPUb boards in a subrack work as a resource pool. The states of the DSPsare managed by the Main Processing Unit (MPU) subsystem in the controlling SPUa board. TheMPU subsystem can appropriately schedule and allocate resources for the associated servicesbetween the DSPs.

6.3 RNC Port RedundancyRNC port redundancy is of three types: port backup, port load sharing, and port trunking.

6.3.1 Backup of AOUa Optical PortsWhen the AOUa boards work in board backup mode, the corresponding optical ports on theactive and standby AOUa boards, such as optical ports 0 on the boards, can be configured forMSP 1:1 backup.


Product Description


Issue 03 (2008-08-30)

6.3.2 Backup of POUa Optical PortsWhen the POUa boards work in board backup mode, the corresponding optical ports on theactive and standby POUa boards, such as optical ports 0 on the boards, can be configured forMSP 1:1 or MSP 1+1 backup.

6.3.3 Backup of UOIa Optical PortsWhen the UOIa boards work in board backup mode, the corresponding optical ports on the activeand standby UOIa boards, such as optical ports 0 on the boards, can be configured for MSP 1:1or MSP 1+1 backup.

6.3.4 Backup of FE/GE PortsWhen the FG2a/GOUa boards work in board backup mode, the corresponding FE/GE ports onthe active and standby boards, such as ports 0 on the boards, can be configured for backup.

6.3.5 Load Sharing on FE/GE PortsLoad sharing is applicable to the FE/GE ports on the FG2a/GOUa boards.

6.3.6 Port Trunking of GE PortsPort trunking is applicable to the GE ports on the SCUa boards.

6.3.1 Backup of AOUa Optical PortsWhen the AOUa boards work in board backup mode, the corresponding optical ports on theactive and standby AOUa boards, such as optical ports 0 on the boards, can be configured forMSP 1:1 backup.

Description of the BackupWhen the AOUa optical ports work in MSP 1:1 backup mode, one optical port is active and theother is standby. The active optical port is responsible for transceiving data.

Switchover Modesl Automatic switchover: The active and standby AOUa optical ports can be switched over

automatically.l Manual switchover: You can use the SET MSPCMD command to forcibly switch over

the active and standby AOUa optical ports.

Prerequisites for SwitchoverThe active and standby AOUa optical ports can be switched over only when one of the followingconditions is fulfilled:l The active optical port is faulty, but the standby optical port works properly.

l The optical transmission device of the active optical port is faulty, but that of the standbyoptical port works properly.

l The active AOUa is faulty, but the standby AOUa works properly.

l The active and standby optical ports at the peer end are switched over. (This may triggerthe switchover of the active and standby optical ports at the local end.)

l The board where the active optical port is located is reset.



6-13

Switchover ProcessWhen the active and standby AOUa optical ports are switched over, the active optical portbecomes standby after its data transceiver switch is set to off, and the other optical port becomesactive after its data transceiver switch is set to on.

Impact of Switchover on the SystemWhen the traffic carried on the optical port is high, the switchover between the active and standbyoptical ports slightly affects the data transmission but does not interrupt ongoing services.

6.3.2 Backup of POUa Optical PortsWhen the POUa boards work in board backup mode, the corresponding optical ports on theactive and standby POUa boards, such as optical ports 0 on the boards, can be configured forMSP 1:1 or MSP 1+1 backup.

Description of the BackupWhen the POUa optical ports work in MSP 1:1 backup mode, one optical port is active and theother is standby. The active optical port is responsible for transceiving data.

When the POUa optical ports work in MSP 1+1 backup mode, one optical port is active and theother is standby. Both the active and standby optical ports transmit data, but only the activeoptical port receives data.

The SET MSP command is available for setting the attributes for MSP backup.

Switchover Modesl Automatic switchover: The active and standby POUa optical ports can be switched over


the active and standby POUa optical ports.

Prerequisites for SwitchoverThe active and standby POUa optical ports can be switched over only when one of the followingconditions is fulfilled:l The active optical port is faulty, but the standby optical port works properly.


l The active POUa is faulty, but the standby POUa works properly.



Switchover ProcessWhen the active and standby POUa optical ports are switched over, the active optical portbecomes standby after its data receiver switch is set to off, and the other optical port becomesactive after its data receiver switch is set to on.


Product Description


Issue 03 (2008-08-30)


6.3.3 Backup of UOIa Optical PortsWhen the UOIa boards work in board backup mode, the corresponding optical ports on the activeand standby UOIa boards, such as optical ports 0 on the boards, can be configured for MSP 1:1or MSP 1+1 backup.

Description of the BackupWhen the UOIa optical ports work in MSP 1:1 backup mode, one optical port is active and theother is standby. The active optical port is responsible for transceiving data.

When the UOIa optical ports work in MSP 1+1 backup mode, one optical port is active and theother is standby. Both the active and standby optical ports transmit data, but only the activeoptical port receives data.

The SET MSP command is available for setting the attributes for MSP backup.

Switchover Modesl Automatic switchover: The active and standby UOIa optical ports can be switched over


the active and standby UOIa optical ports.

Prerequisites for SwitchoverThe active and standby UOIa optical ports can be switched over only when one of the followingconditions is fulfilled:l The active optical port is faulty, but the standby optical port works properly.


l The active UOIa is faulty, but the standby UOIa works properly.



Switchover ProcessWhen the active and standby UOIa optical ports are switched over, the active optical portbecomes standby after its data receiver switch is set to off, and the other optical port becomesactive after its data receiver switch is set to on.




6-15

6.3.4 Backup of FE/GE PortsWhen the FG2a/GOUa boards work in board backup mode, the corresponding FE/GE ports onthe active and standby boards, such as ports 0 on the boards, can be configured for backup.


When the FE/GE ports work in backup mode, one port is active and the other is standby. Theactive port is responsible for transceiving data.

When the FG2a/GOUa boards work in board backup mode, you must use the ADDETHREDPORT command to configure the corresponding FE/GE ports on the active andstandby boards, such as ports 0 on the boards, for backup.

Switchover Modesl Automatic switchover: The active and standby ports on the FG2a/GOUa boards can be

switched over automatically.

l Manual switchover: You can use the SWP ETHPORT command to forcibly switch overthe active and standby ports on the FG2a/GOUa boards.


The active and standby ports on the FG2a/GOUa boards can be switched over only when oneof the following conditions is fulfilled:

l The active port is faulty, but the standby port works properly.

l The active FG2a/GOUa is faulty, but the standby FG2a/GOUa works properly.

l The board where the active port is located is reset.

Switchover Process

When the active and standby ports on the FG2a/GOUa boards are switched over, the active portbecomes standby after its data transceiver switch is set to off, and the other port becomes activeafter its data transceiver switch is set to on.


When the traffic carried on the port is high, the switchover between the active and standby portsslightly affects the data transmission but does not interrupt ongoing services.

6.3.5 Load Sharing on FE/GE PortsLoad sharing is applicable to the FE/GE ports on the FG2a/GOUa boards.

Prerequisites

The RNC supports load sharing between FE/GE ports that are located either on the same boardor on active and standby boards.


Product Description


Issue 03 (2008-08-30)

NOTE

l The RNC does not support load sharing between FE/GE ports that are located on different boardsbetween whom there is no active/standby relationship.

l The RNC does not support load sharing between active and standby ports.

Working PrinciplesLoad sharing between FE/GE ports on the FG2a/GOUa boards is user-specific. The data of atype of user is carried on one FE/GE port, and that of another type of user is carried on anotherFE/GE port.

NOTE

The data of one user is transmitted through one FE/GE port, instead of being shared by ports.

Application ScenarioLoad sharing between FE/GE ports of the RNC is applicable to layer 3 networking between theRNC and other NEs, instead of layer 2 networking. To implement load sharing, the data towardsthe same IP address must be transmitted from multiple ports. This requires different IP routes.For example, load sharing between two FE/GE ports requires two IP routes that have the samedestination IP address, address mask and priority, but different next hops.

NOTE

l An IP route can be configured through the ADD IPRT command.

l The RNC supports load sharing between a maximum of three FE/GE ports.

Benefitsl The data traffic is shared by the ports to avoid the occurrence where some ports are busy

while others are idle.l Load sharing enhances reliability of data transmission.

6.3.6 Port Trunking of GE PortsPort trunking is applicable to the GE ports on the SCUa boards.

Application of Port Trunking in the RNCPort trunking is applied to the switching subsystem of the RNC.l In a subrack of the RNC, the ports serving the communication between the SCUa and the

other boards work as a trunk group to enable port trunking.l The ports serving the communication between the SCUa boards in the RSS and the SCUa

boards in an RBS work as a trunk group to enable port trunking.

Benefitsl In a trunk group, the bandwidth is evenly allocated to the GE ports, thus fulfilling load

balancing.l If a GE link in a trunk group is faulty, the data stream on the link is automatically switched

over.l If the SCUa or a service board is faulty, no associated switchover occurs.



6-17

7 RNC Technical Specifications

About This Chapter

The RNC technical specifications cover the RNC capacity, engineering, physical ports,reliability, noise and safety compliance, environmental protection, clock precision, and so on.

7.1 RNC CapacityThe RNC capacity specifications consist of the maximum configuration of the RNC hardware,maximum voice traffic, maximum PS data throughput, maximum number of NodeBs, and soon.

7.2 RNC Engineering SpecificationsThe RNC engineering specifications consist of structural specifications, electrical specifications,and GPS feeder specifications.

7.3 RNC PortsThe RNC ports can be external transmission ports, internal transmission ports, clock ports, andsatellite signal ports.

7.4 RNC ReliabilityThe RNC reliability specifications consist of system availability in typical configuration, MeanTime Between Failures (MTBF), and Mean Time To Repair (MTTR).

7.5 RNC Noise and Safety ComplianceRNC noise and safety compliance covers the noise specifications and the requirements that theRNC should meet in terms of noise control and safety.

7.6 RNC Environmental Protection SpecificationsThe environmental protection specifications of the RNC conform to associated internationalstandards.

7.7 RNC Clock Precision RequirementsTo guarantee proper operation, the RNC should meet specific clock precision requirements.

7.8 RNC Storage RequirementsThe RNC has storage requirements for climate, waterproofing conditions, biologicalenvironment, air purity, and mechanical stress.

7.9 RNC Transportation Requirements

RNCProduct Description 7 RNC Technical Specifications


7-1

The RNC has transportation requirements for climate, waterproofing conditions, biologicalenvironment, air cleanliness, and mechanical stress.

7.10 RNC Working Environment RequirementsThe RNC has working environment requirements for climate, biological environment, air purity,and mechanical stress.

7.11 Technical Specifications for RNC PartsThe technical specifications for RNC parts cover those for the power distribution box, fan box,and boards.

7 RNC Technical SpecificationsRNC

Product Description


Issue 03 (2008-08-30)

7.1 RNC CapacityThe RNC capacity specifications consist of the maximum configuration of the RNC hardware,maximum voice traffic, maximum PS data throughput, maximum number of NodeBs, and soon.

Table 7-1 describes the specifications for RNC capacity.

Table 7-1 Specifications for RNC capacity

Item Specification

Maximum number of cabinets 2, that is, 1 RSR and 1 RBR

Maximum number of subracks 6, that is, 1 RSS and 5 RBSs

Maximum voice traffic 51,000 Erlang

Maximum PS data throughput 3,264 Mbit/s (UL + DL)

Maximum number of NodeBs 1,700

Maximum number of cells 5,100

Busy Hour Call Attempts (BHCAs) 1,360,000

NOTE


7.2 RNC Engineering SpecificationsThe RNC engineering specifications consist of structural specifications, electrical specifications,and GPS feeder specifications.

Structural SpecificationsTable 7-2 describes the structural specifications.

Table 7-2 Structural specifications

Item Specification

Cabinet standard The structural design conforms to the IEC60297 standardand IEEE standard.

Dimensions of an N68E-22cabinet

2,200 mm (H) x 600 mm (W) x 800 mm (D)

Dimensions of an N68-21-Ncabinet

2,130 mm (H) x 600 mm (W) x 800 mm (D)



7-3

Item Specification

Height of the available space inan N68E-22 cabinet

46 U

Height of the available space inan N68-21-N cabinet

44 U

Weight of an N68E-22 cabinet Rack: ≤ 59 kg; Empty cabinet: ≤ 100 kg; Cabinet in fullconfiguration: ≤ 350 kg

Weight of an N68-21-N cabinet Rack: ≤ 105 kg; Empty cabinet: ≤ 155 kg; Cabinet infull configuration: ≤ 410 kg

Electrical SpecificationsTable 7-3 describes the electrical specifications.

Table 7-3 Electrical specifications

Item Specification

Power supply Four -48 V DC inputs

Electro MagneticCompatibility (EMC) ofan N68E-22 cabinet

l ETSI EN300 386

l Council directive 89/336/EEC

Electro MagneticCompatibility (EMC) ofan N68-21-N cabinet

l GR 1089

l ETSI EN300 386

l Council directive 89/336/EEC

RSS power consumption ≤ 1,530 W

RBS power consumption ≤ 1,540 W

Power consumption ofthe cabinet in fullconfiguration

RSR: ≤ 4,650 W; RBR: ≤ 4,660 W

GPS Feeder SpecificationsYou should choose appropriate feeders according to the distance between a satellite antenna anda cabinet. Table 7-4 lists the RNC GPS feeders specifications.


Product Description


Issue 03 (2008-08-30)

Table 7-4 Choosing feeders according to the distance

The distance between a satelliteantenna and a cabinet

Feeder

shorter than or equal to 100 m 1/2" feeder

Longer than 100 m and shorter than or equalto 300 m

7/8" feeder

Longer than 300 m and shorter than or equalto 500 m

5/4" feeder

7.3 RNC PortsThe RNC ports can be external transmission ports, internal transmission ports, clock ports, andsatellite signal ports.

Specifications for RNC External Transmission PortsThe external transmission ports of the RNC are applicable to data transmission on the Iu, Iur,and Iub interfaces. Table 7-5 describes the specifications for the ports.

Table 7-5 Specifications for external transmission ports

Port MaximumNumber ofPorts

Board Port Type Remarks

E1/T1 port 1152 AEUa DB44 Applicable to the Iu-CS, Iu-PS, Iur, and Iub interfaces, butmainly to the ATM-based Iubinterface

1152 PEUa DB44 Applicable to the Iu-CS, Iur,and Iub interfaces, but mainlyto the IP-based Iub interface

ChannelizedSTM-1/OC-3port

160 AOUa LC/PC Applicable to the Iu-CS, Iu-PS, Iur, and Iub interfaces, butmainly to the ATM-based Iubinterface

160 POUa LC/PC Applicable to the Iu-CS, Iur,and Iub interfaces, but mainlyto the IP-based Iub interface

Unchannelized STM-1/OC-3c port

320 UOIa(UOI_ATM)

LC/PC Applicable to the ATM-basedIu-CS, Iu-PS, Iu-BC, Iur, andIub interfaces



7-5

Port MaximumNumber ofPorts


320 UOIa(UOI_IP)

LC/PC Applicable to the IP-based Iu-CS, Iu-PS, Iu-BC, Iur, and Iubinterfaces

FE electricalport

640 FG2a RJ45 Applicable to the IP-based Iu-CS, Iu-PS, Iu-BC, Iur, and Iubinterfaces

GE electricalport

160 FG2a RJ45 Applicable to the IP-based Iu-CS, Iu-PS, Iu-BC, Iur, and Iubinterfaces

GE opticalport

160 GOUa LC/PC Applicable to the IP-based Iu-CS, Iu-PS, Iu-BC, Iur, and Iubinterfaces

Specifications for RNC Internal Transmission PortsThe internal transmission ports of the RNC are applicable to inter-subrack data transmission inthe RNC. Table 7-6 describes the specifications for the ports.

Table 7-6 Specifications for internal transmission ports

Port MaximumNumber ofPhysical Ports


GE electricalport

144 SCUa RJ45 Applicable tointerconnectionbetween the RSSsubrack and RBSsubracks in the RNC

Specifications for the Satellite Signal Port and Clock PortsTable 7-7 describes the specifications for the satellite signal port and clock ports of the RNC.


Product Description


Issue 03 (2008-08-30)

Table 7-7 Specifications for the satellite signal port and clock ports

Port Board Port Type Remarks

Port for the GPSantenna

GCGa SMA, male Receiving the timing signalsfrom the GPS systemNOTE

The GCUa also provides the port,which is unavailable because theGCUa is not configured with a GPScard.

Timing signaloutput port

GCUa/GCGa RJ45 Outputting 8 kHz and 1 PPStiming signals to the SCUa board

AEUa/PEUa/POUa/AOUa/UOIa

SMB, male Outputting 2 MHz timing signalsto the GCUa/GCGa board

Timing signalinput port

SCUa RJ45 Receiving the 8 kHz and 1 PPStiming signals from the GCUa/GCGa board

GCUa/GCGa SMB, male Receiving the timing signalsfrom the BITS clock or from theAEUa, PEUa, POUa, AOUa, orUOIa board

7.4 RNC ReliabilityThe RNC reliability specifications consist of system availability in typical configuration, MeanTime Between Failures (MTBF), and Mean Time To Repair (MTTR).

Table 7-8 describes the specifications for RNC reliability.

Table 7-8 Specifications for RNC reliability

Item Specification

System availability in typicalconfiguration

≥ 99.999%

MTBF ≥ 347,700 h

MTTR ≤ 1 h

7.5 RNC Noise and Safety ComplianceRNC noise and safety compliance covers the noise specifications and the requirements that theRNC should meet in terms of noise control and safety.

Table 7-9 describes the RNC noise and safety compliance.



7-7

Table 7-9 RNC noise and safety compliance

Item Specification

Noise < 72 dB; conforming to the requirements in EUROPEAN ETS 300 753

Safety Fulfilling the requirements in:l IEC60950-1

l EN60950-1

l UL60950-1

l EN60825-1

l EN60825-2

l AS/NZS60950-1

l GB4943

7.6 RNC Environmental Protection SpecificationsThe environmental protection specifications of the RNC conform to associated internationalstandards.

The RNC conforms to the environmental protection specifications stated in the followingstandards:l RoHS: Restriction of the Use of Certain Hazardous Substances in Electrical and Electronic

Equipmentl WEEE: The EU Directive on Waste of Electrical and Electronic Equipment

7.7 RNC Clock Precision RequirementsTo guarantee proper operation, the RNC should meet specific clock precision requirements.

The precision of the clock for the RNC meets the associated requirements of the stratum 3 clock.

7.8 RNC Storage RequirementsThe RNC has storage requirements for climate, waterproofing conditions, biologicalenvironment, air purity, and mechanical stress.

Climatic Requirements

Table 7-10 describes the climatic requirements for storing the RNC.

Table 7-10 Climatic requirements for storing the RNC

Item Specification

Temperature –40℃ to +70℃


Product Description


Issue 03 (2008-08-30)

Item Specification

Temperature change rate ≤ 1℃/min

Relative humidity 10% to 100%

Altitude ≤ 5,000 m

Air pressure 70 kPa to 106 kPa

Solar radiation ≤ 1,120 W/m2

Thermal radiation ≤ 600 W/m2

Wind speed ≤ 30 m/s

Waterproofing RequirementsThe waterproofing requirements for storing the RNC are as follows:l The equipment is usually stored in a room.

l There is no water on the floor or any water leakage into the package.

l In the equipment room, there is no water that may damage the equipment, such as waterfrom automatic fire protection devices or air conditioner.

If the equipment has to be placed outdoors, ensure that:l The package is intact.

l Waterproofing measures are taken to prevent rainwater from leaking into the package.

l There is no water on the ground or any water leakage into the package.

l The package is not exposed to direct sunlight.

Biological RequirementsThe biological requirements for storing the RNC are as follows:l No fungus or mildew may grow in the equipment room or near the equipment.

l The place is free from rodents, such as rats.

Air Purity RequirementsThe air purity requirements for storing the RNC are as follows:l The air is free from explosive, conductive, magnetically conductive, or corrosive dust.

l The density of physically active materials must meet the requirements listed in Table7-11.

l The density of chemically active materials must meet the requirements listed in Table7-12.



7-9

Table 7-11 Storage requirements for physically active materials

Physically ActiveMaterial

Unit Density

Suspended dust mg/m2 ≤ 5.00

Falling dust mg/m2·h ≤ 20.0

Sand mg/m3 ≤ 300

NOTE

l Suspended dust: diameter ≤ 75 μm

l Falling dust: 75 μm ≤ diameter ≤ 150 μm

l Sand: 150 μm ≤ diameter ≤ 1,000 μm

Table 7-12 Storage requirements for chemically active materials

Chemically Active Material Unit Density

SO2 mg/m3 ≤ 0.30

H2S mg/m3 ≤ 0.10

NO2 mg/m3 ≤ 0.50

NH3 mg/m3 ≤ 1.00

Cl2 mg/m3 ≤ 0.10

HCl mg/m3 ≤ 0.10

HF mg/m3 ≤ 0.01

O3 mg/m3 ≤ 0.05

Mechanical Stress RequirementsTable 7-13 describes the mechanical stress requirements for storing the RNC.

Table 7-13 Mechanical stress requirements for storing the RNC

Item Sub-item Specification

Sinusoidalvibration

Offset ≤ 7.0 mm –

Accelerated speed – ≤ 20.0 m/s2

Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz


Product Description


Issue 03 (2008-08-30)


Unsteady impact Impact responsespectrum II

≤ 250 m/s2

Static payload ≤ 5 kPa

NOTE

l Impact response spectrum: maximum acceleration response curve generated by the equipment underspecified impact excitation. Impact response spectrum II means that the duration of semi-sine impactresponse spectrum is 6 ms.

l Static payload: capability of the equipment in package to bear the pressure from the top in normal pile-up method

7.9 RNC Transportation RequirementsThe RNC has transportation requirements for climate, waterproofing conditions, biologicalenvironment, air cleanliness, and mechanical stress.

Climatic Requirements

Table 7-14 describes the climatic requirements for transporting the RNC.

Table 7-14 Climatic requirements for transporting the RNC

Item Specification

Temperature -40℃ to +70℃


Relative humidity 5% to 100%



Solar radiation ≤ 1,120 W/m2



Waterproofing Requirements

The waterproofing requirements for transporting the RNC are as follows:

l The package is intact.

l Waterproofing measures are taken to prevent rainwater from entering the package.

l There is no water on the floor of the transportation vehicle.



7-11

Biological Requirements

The biological requirements for transporting the RNC are as follows:

l No fungus or mildew may grow in the vehicle.


Air Cleanliness Requirements

The air cleanliness requirements for transporting the RNC are as follows:

l The air is free from explosive, conductive, magnetically conductive, or corrosive dust.

l The density of physically active materials meets the requirements listed in Table 7-15.

l The density of chemically active materials meets the requirements listed in Table 7-16.

Table 7-15 Transportation requirements for physically active materials


Unit Density

Suspended dust mg/m3 No requirement

Falling dust mg/m2·h ≤ 3.0

Sand mg/m3 ≤ 100

NOTE

l Suspended dust: diameter ≤ 75 μm

l Falling dust: 75 μm ≤ diameter ≤ 150 μm

l Sand: 150 μm ≤ diameter ≤ 1,000 μm

Table 7-16 Transportation requirements for chemically active materials


SO2 mg/m3 ≤ 0.30

H2S mg/m3 ≤ 0.10

NO2 mg/m3 ≤ 0.50

NH3 mg/m3 ≤ 1.00

Cl2 mg/m3 ≤ 0.10

HCl mg/m3 ≤ 0.10

HF mg/m3 ≤ 0.01

O3 mg/m3 ≤ 0.05


Product Description


Issue 03 (2008-08-30)

Mechanical Stress RequirementsTable 7-17 describes the mechanical stress requirements for transporting the RNC.

Table 7-17 Mechanical stress requirements for transporting the RNC


Sinusoidalvibration

Offset ≤ 7.5 mm - -

Accelerated speed - ≤ 20.0 m/s2 ≤ 40.0 m/s2

Frequency range 2 Hz to 9 Hz 9 Hz to 200Hz

200 Hz to 500Hz

Randomvibration

Spectrum densityof acceleratedspeed

10 m2/s3 3 m2/s3 1 m2/s3

Frequency range 2 Hz to 9 Hz 9 Hz to 200Hz

200 Hz to 500Hz

Unsteadyimpact

Impact responsespectrum II

≤ 300 m/s2

Static payload ≤ 10 kPa

NOTE



7.10 RNC Working Environment RequirementsThe RNC has working environment requirements for climate, biological environment, air purity,and mechanical stress.

Climatic RequirementsTable 7-18 and Table 7-19 describe the climatic requirements for operating the RNC.

Table 7-18 Temperature and humidity requirements for operating the RNC

Temperature Relative Humidity

Normal Safe Normal Safe

0℃ to 45℃ –5℃ to +55℃ 5% to 85% 5% to 95%



7-13

Temperature Relative Humidity

NOTE

l The values are measured 1.5 m above the floor and 0.4 m in front of the equipment, without protectivepanels in front of or behind the cabinet.

l Safe operation refers to continuous operation for not more than 96 hours or accumulated operation ofnot more than 15 days in a year.

Table 7-19 Other climatic requirements for operating the RNC

Item Specification




Solar radiation ≤ 700 W/m2



Biological RequirementsThe biological requirements for operating the RNC are as follows:l No fungus or mildew may grow in the area where the equipment is operated.


Air Purity RequirementsThe air purity requirements for operating the RNC are as follows:l The air is free from explosive, conductive, magnetically conductive, or corrosive dust.

l The density of physically active materials must meet the requirements listed in Table7-20.

l The density of chemically active materials must meet the requirements listed in Table7-21.

Table 7-20 Working environment requirements for physically active materials


Unit Density

Dust particles Particles/m3 ≤ 3 x 104 (no visible dust on thedesktop within 3 days)

NOTEDust particles: diameter ≥ 5 μm


Product Description


Issue 03 (2008-08-30)

Table 7-21 Working environment requirements for chemically active materials


SO2 mg/m3 ≤ 0.20

H2S mg/m3 ≤ 0.006

NH3 mg/m3 ≤ 0.05

Cl2 mg/m3 ≤ 0.01

Mechanical Stress RequirementsTable 7-22 describes the mechanical stress requirements for operating the RNC.

Table 7-22 Mechanical stress requirements for operating the RNC


Sinusoidal vibration Offset ≤ 3.5 mm –

Accelerated speed – ≤ 10.0 m/s2

Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz

Unsteady impact Impact response spectrumII

≤ 100 m/s2

Static payload 0

NOTE



7.11 Technical Specifications for RNC PartsThe technical specifications for RNC parts cover those for the power distribution box, fan box,and boards.

7.11.1 Technical Specifications for the RNC Power Distribution BoxThis describes the technical specifications for the input and output of the RNC power distributionbox.

7.11.2 Technical Specifications for the RNC Fan BoxThe technical specifications for the RNC fan box refer to the space height, power supply,maximum power, temperature range, and requirement for fan speed adjustment.

7.11.3 Technical Specifications for the OMUa Board



7-15

The technical specifications for the OMUa board include hardware specifications andperformance specifications. The hardware specifications refer to the dimension, power supply,power consumption, weight, operating temperature, and relative humidity.

7.11.4 Technical Specifications for the SCUa BoardThe technical specifications for the SCUa board refer to the dimension, power supply, powerconsumption, weight, operating temperature, relative humidity, and switching capacity.

7.11.5 Technical Specifications for the SPUa BoardThe technical specifications for the SPUa board refer to the dimension, power supply, powerconsumption, weight, operating temperature, relative humidity, and processing capability.

7.11.6 Technical Specifications for the DPUb BoardThe technical specifications for the DPUb board refer to the dimension, power supply, powerconsumption, weight, operating temperature, relative humidity, and processing capability.

7.11.7 Technical Specifications for the GCUa/GCGa BoardThe technical specifications for the GCUa/GCGa board refer to dimensions, power supply,power consumption, weight, operating temperature, relative humidity, and minimum clockprecision.

7.11.8 Technical Specifications for the AEUa BoardThe technical specifications for the AEUa board are hardware specifications and specificationsfor the processing capability of the AEUa board. The hardware specifications refer to thedimension, power supply, power consumption, weight, operating temperature, and relativehumidity.

7.11.9 Technical Specifications for the AOUa BoardThe technical specifications for the AOUa board include hardware specifications andspecifications for optical ports and board processing capability. The hardware specificationsrefer to the dimension, power supply, power consumption, weight, operating temperature, andrelative humidity.

7.11.10 Technical Specifications for the UOIa BoardThe technical specifications for the UOIa board include hardware specifications andspecifications for optical ports. The hardware specifications are the dimension, power supply,power consumption, weight, operating temperature, relative humidity, and board processingcapability.

7.11.11 Technical Specifications for the POUa BoardThe technical specifications for the POUa board are hardware specifications and specificationsfor board processing capability. The hardware specifications refer to the dimension, powersupply, power consumption, weight, operating temperature, and relative humidity.

7.11.12 Technical Specifications for the PEUa BoardThe technical specifications for the PEUa board are hardware specifications and specificationsfor board processing capability. The hardware specifications refer to the dimension, powersupply, power consumption, weight, operating temperature, and relative humidity.

7.11.13 Technical Specifications for the FG2a BoardThe technical specifications for the FG2a board are hardware specifications and specificationsfor board processing capability. The hardware specifications refer to the dimension, powersupply, power consumption, weight, operating temperature, and relative humidity.

7.11.14 Technical Specifications for the GOUa BoardThe technical specifications for the GOUa board include hardware specifications andspecifications for optical ports and board processing capability. The hardware specifications


Product Description


Issue 03 (2008-08-30)

refer to the dimension, power supply, power consumption, weight, operating temperature, andrelative humidity.

7.11.15 Technical Specifications for the PFCU BoardThe technical specifications for the PFCU board are the dimension, power supply, powerconsumption, temperature range, and requirement for fan speed adjustment.

7.11.16 Technical Specifications for the PAMU BoardThe technical specifications for the PAMU board refer to the dimension, power supply, powerconsumption, and weight.

7.11.1 Technical Specifications for the RNC Power Distribution BoxThis describes the technical specifications for the input and output of the RNC power distributionbox.

Table 7-23 describes the technical specifications for the RNC power distribution box.

Table 7-23 Technical specifications for the RNC power distribution box

Item Specification

Space height 3 U (1 U = 44.45 mm)

Input Rated inputvoltage

-48 V DC

Input voltagerange

-40 V DC to -57 V DC

Input mode The 4 (2 x 2) inputs (A1, A3, B1, B3) are provided. That is, A1and A2 share the same input power cable, and B1 and B2 alsoshare the same input power cable inside the power distributionbox. No power input is allowed at the A2 and B2 inputterminals.

Max. inputcurrent

100 A for each input

Output Rated outputvoltage

-48 V DC

Outputvoltage range

-40 V DC to -57 V DC

Rated outputpower

9600 W (-48 V DC input)



7-17

Item Specification

Output modeand current

l 20 (10 x 2) outputs are provided. A single output providesthe current of up to 50 A.

l A1 in Group A: The inputs to A1 are through outputdivisions 1 to 8, which match switches 1 to 8. A3: The inputsto A3 are through output divisions 9 and 10, which matchswitches 9 and 10 in Group A. The input and outputmatching in Group B is the same as that in Group A.

l Providing overcurrent protection. You need to manually setthe corresponding air-break switch back to the work modeafter the overcurrent protection.

7.11.2 Technical Specifications for the RNC Fan BoxThe technical specifications for the RNC fan box refer to the space height, power supply,maximum power, temperature range, and requirement for fan speed adjustment.

Table 7-24 describes the technical specifications for the RNC fan box.

Table 7-24 Technical specifications for the RNC fan box

Item Specification

Space height 1.5 U (1 U = 44.45 mm)

Input voltage range -40 V DC to -57 V DC

Maximum power 150 W

Temperature range -5℃ to +55℃ (basic requirement)

Requirement for fan speed adjustment The fan speed can be adjusted by 50% to 100%.

7.11.3 Technical Specifications for the OMUa BoardThe technical specifications for the OMUa board include hardware specifications andperformance specifications. The hardware specifications refer to the dimension, power supply,power consumption, weight, operating temperature, and relative humidity.

Table 7-25 describes the hardware specifications for the OMUa board.

Table 7-25 Hardware specifications for the OMUa board

Item Specification

Dimensions 366.7 mm x 220 mm


Product Description


Issue 03 (2008-08-30)

Item Specification

Power supply Two -48 V DC inputs working in active/standbymode. The backplane of the subrack providesthe power.

Power consumption 190 W

Weight 4.6 kg

Operating temperature (long-term) 0℃ to 45℃

Operating temperature (short-term) -5℃ to +55℃

Relative humidity (long-term) 5% to 85%

Relative humidity (short-term) 5% to 95%

Table 7-26 describes the performance specifications for the OMUa board.

Table 7-26 Performance specifications for the OMUa board

Item Description

Number of alarms to bestored

A maximum of 100,000 alarms can be recorded.

Time spent for datasynchronizationbetween the active andthe standby OMUaboards

In a normal situation, the data is automatically synchronized onceevery second. That is, the standby OMUa board synchronizes itsdata with that on the active OMUa board in real time.

Interval for filesynchronizationbetween the active andthe standby OMUaboards

Time spent for file synchronization between the active and thestandby OMUa boards is five minutes. The time actually spent forfile synchronization depends on the size and quantity of the filesto be synchronized.

Time spent for theswitchover between theactive and the standbyOMUa boards

In a normal state, the active/standby switchover of the OMUaboards takes about 2-5 seconds, in which the data synchronizationof the active/standby OMUa boards is not included.

Time spent for startingthe OMUa board

If the OMUa board is restarted owing to faults, the restartingprocess takes about two minutes.

7.11.4 Technical Specifications for the SCUa BoardThe technical specifications for the SCUa board refer to the dimension, power supply, powerconsumption, weight, operating temperature, relative humidity, and switching capacity.

Table 7-27 describes the technical specifications for the SCUa board.



7-19

Table 7-27 Technical specifications for the SCUa board

Item Specification



Power consumption 54.5 W

Weight 1.2 kg





Switching capacity 60 Gbit/s

7.11.5 Technical Specifications for the SPUa BoardThe technical specifications for the SPUa board refer to the dimension, power supply, powerconsumption, weight, operating temperature, relative humidity, and processing capability.

Table 7-28 describes the technical specifications for the SPUa board.

Table 7-28 Technical specifications for the SPUa board

Item Specification




Weight 1.6 kg





Processing capability of the main controlSPUa board

Supporting 100 NodeBs, 300 cells, and 67,500Busy Hour Call Attempt (BHCA)


Product Description


Issue 03 (2008-08-30)

Item Specification

Processing capability of the non maincontrol SPUa board

Supporting 100 NodeBs, 300 cells, and 90,000BHCA

NOTE


7.11.6 Technical Specifications for the DPUb BoardThe technical specifications for the DPUb board refer to the dimension, power supply, powerconsumption, weight, operating temperature, relative humidity, and processing capability.

Table 7-29 describes the technical specifications for the DPUb board.

Table 7-29 Technical specifications for the DPUb board

Item Specification




Weight 1.26 kg





Processing capability Supporting 96 Mbit/s (DL+UL) data streams;Supporting 1,500 Erlang CS voice services;Supporting 750 Erlang CS data services;Supporting 150 cells

NOTE

l The specifications stated previously refer to the maximum capability concerning the correspondingservice.

l The data service in the CS domain refers to the 64 kbit/s video phone service.



7-21

7.11.7 Technical Specifications for the GCUa/GCGa BoardThe technical specifications for the GCUa/GCGa board refer to dimensions, power supply,power consumption, weight, operating temperature, relative humidity, and minimum clockprecision.

Table 7-30 describes the technical specifications for the GCUa/GCGa board.

Table 7-30 Technical specifications for the GCUa/GCGa board

Item Specification



Power consumption GCUa: 20 W; GCGa: 25 W

Weight GCUa: 1.1 kg; GCGa: 1.18 kg





Clock precision grade Stratum 3

7.11.8 Technical Specifications for the AEUa BoardThe technical specifications for the AEUa board are hardware specifications and specificationsfor the processing capability of the AEUa board. The hardware specifications refer to thedimension, power supply, power consumption, weight, operating temperature, and relativehumidity.

Hardware Specifications for the AEUa BoardTable 7-31 describes the hardware specifications for the AEUa board.

Table 7-31 Hardware specifications for the AEUa board

Item Specification





Product Description


Issue 03 (2008-08-30)

Item Specification

Weight 1.2 kg





Specifications for the Processing Capability of the AEUa BoardTable 7-32 describes the specifications for the processing capability of the AEUa board.

Table 7-32 Specifications for the processing capability of the AEUa board

Item Specification

Iub Voice service in the CS domain 2,800 Erlang

Data service in the CS domain 680 Erlang

Maximum payload throughput(UL)

45 Mbit/s

Maximum payload throughput(DL)

45 Mbit/s

NOTE



7.11.9 Technical Specifications for the AOUa BoardThe technical specifications for the AOUa board include hardware specifications andspecifications for optical ports and board processing capability. The hardware specificationsrefer to the dimension, power supply, power consumption, weight, operating temperature, andrelative humidity.

Hardware Specifications for the AOUa BoardTable 7-33 describes the hardware specifications for the AOUa board.



7-23

Table 7-33 Hardware specifications for the AOUa board

Item Specification


Power supply Two -48 V DC inputs working in active/standby mode. The backplane ofthe subrack provides the power.

Powerconsumption

37.3 W

Weight 1.3 kg

Operatingtemperature(long-term)

0℃ to 45℃

Operatingtemperature(short-term)

-5℃ to +55℃

Relativehumidity (long-term)

5% to 85%

Relativehumidity (short-term)

5% to 95%

Specifications for the Processing Capability of the AOUa Board

Table 7-34 describes the specifications for the processing capability of the AOUa board.

Table 7-34 Specifications for the processing capability of the AOUa board

Item Specification


Data service in the CS domain 3,000 Erlang


195 Mbit/s


195 Mbit/s

NOTE




Product Description


Issue 03 (2008-08-30)

Specifications for Optical Ports on the AOUa Board

Table 7-35 describes the specifications for the optical ports on the AOUa board.

Table 7-35 Specifications for optical ports on the AOUa board

Item Specification

Optical Module155M-1310nm-2km-MM-SFP

Optical Module155M-1310nm-15km-SM-ESFP


Mode Multi-mode Single-mode Single-mode

Type LC/PC LC/PC LC/PC

Maximumopticaltransmissiondistance

2 km 15 km 40 km

Averageoutput opticalpower

-19.0 dBm to -14.0dBm

-15.0 dBm to -8.0 dBm -5.0 dBm to 0.0dBm

Minimumreceiversensitivity

-30.0 dBm -31.0 dBm -37.0 dBm

Overloadoptical power

-14.0 dBm -8.0 dBm -10.0 dBm

Centerwavelength

1,310 nm 1,310 nm 1,310 nm

Rate 155.52 Mbit/s 155.52 Mbit/s 155.52 Mbit/s

7.11.10 Technical Specifications for the UOIa BoardThe technical specifications for the UOIa board include hardware specifications andspecifications for optical ports. The hardware specifications are the dimension, power supply,power consumption, weight, operating temperature, relative humidity, and board processingcapability.

Hardware Specifications for the UOIa Board

Table 7-36 describes the hardware specifications for the UOIa board.

Table 7-36 Hardware specifications for the UOIa board

Item Specification




7-25

Item Specification

Power supply Two -48 V DC inputs working in active/standby mode. The backplaneof the subrack provides the power.


Weight 1.15 kg

Operatingtemperature (long-term)

0℃ to 45℃

Operatingtemperature (short-term)

-5℃ to +55℃

Relative humidity(long-term)

5% to 85%

Relative humidity(short-term)

5% to 95%

Specifications for the Processing Capability of the UOIa Board (UOIa_ATM)Table 7-37 describes the specifications for the processing capability of the UOIa board(UOIa_ATM).

Table 7-37 Specifications for the processing capability of the UOIa board (UOIa_ATM)

Item Specification



Maximum payload throughput (UL) 225 Mbit/s

Maximum payload throughput (DL) 225 Mbit/s

Iur Voice service in the CS domain 9,000 Erlang




Iu-CS Voice service in the CS domain 9,000 Erlang


Iu-PS Maximum payload throughput (UL) 150 Mbit/s



Product Description


Issue 03 (2008-08-30)

Table 7-38 describes the specifications for the processing capability of the UOI board (UOI_IP).

Table 7-38 Specifications for the processing capability of the UOI board (UOI_IP)

Item Specification











Iu-PS Maximum payload throughput (UL) 250 Mbit/s


NOTE



Specifications for Optical Ports on the UOIa BoardTable 7-39 describes the specifications for the optical ports on the UOIa board.

Table 7-39 Specifications for optical ports on the UOIa board

Item Specification







2 km 15 km 40 km



7-27

Item Specification





-19.0 dBm to -14.0dBm

-15.0 dBm to -8.0 dBm -5.0 dBm to 0.0 dBm


-30.0 dBm -31.0 dBm -37.0 dBm


-14.0 dBm -8.0 dBm -10.0 dBm

Centerwavelength

1,310 nm 1,310 nm 1,310 nm


7.11.11 Technical Specifications for the POUa BoardThe technical specifications for the POUa board are hardware specifications and specificationsfor board processing capability. The hardware specifications refer to the dimension, powersupply, power consumption, weight, operating temperature, and relative humidity.

Hardware Specifications for the POUa BoardTable 7-40 describes the hardware specifications for the POUa board.

Table 7-40 Hardware specifications for the POUa board

Item Specification




Weight 1.3 kg






Product Description


Issue 03 (2008-08-30)

Specifications for the Processing Capability of the POUa Board

Table 7-41 describes the specifications for the processing capability of the POUa board.

Table 7-41 Specifications for the processing capability of the POUa board

Item Specification




120 Mbit/s


120 Mbit/s

NOTE



Specifications for Optical Ports on the POUa Board

Table 7-42 describes the specifications for the optical ports on the POUa board.

Table 7-42 Specifications for optical ports on the POIa board

Item Specification







2 km 15 km 40 km


-19.0 dBm to -14.0dBm

-15.0 dBm to -8.0 dBm -5.0 dBm to 0.0 dBm


-30.0 dBm -31.0 dBm -37.0 dBm



7-29

Item Specification





-14.0 dBm -8.0 dBm -10.0 dBm

Centerwavelength

1310 nm 1310 nm 1310 nm


7.11.12 Technical Specifications for the PEUa BoardThe technical specifications for the PEUa board are hardware specifications and specificationsfor board processing capability. The hardware specifications refer to the dimension, powersupply, power consumption, weight, operating temperature, and relative humidity.

Hardware Specifications for the PEUa BoardTable 7-43 describes the hardware specifications for the PEUa board.

Table 7-43 Hardware specifications for the PEUa board

Item Specification




Weight 1.3 kg





Specifications for the Processing Capability of the PEUa BoardTable 7-44 describes the specifications for the processing capability of the PEUa board.


Product Description


Issue 03 (2008-08-30)

Table 7-44 Specifications for the processing capability of the PEUa board

Item Specification




60 Mbit/s


60 Mbit/s

NOTE



7.11.13 Technical Specifications for the FG2a BoardThe technical specifications for the FG2a board are hardware specifications and specificationsfor board processing capability. The hardware specifications refer to the dimension, powersupply, power consumption, weight, operating temperature, and relative humidity.

Hardware Specifications for the FG2a Board

Table 7-45 describes the hardware specifications for the FG2a board.

Table 7-45 Hardware specifications for the FG2a board

Item Specification




Weight 1.36 kg







7-31

Specifications for the Processing Capability of the FG2a Board

Table 7-46 describes the specifications for the processing capability of the FG2a board.

Table 7-46 Specifications for the processing capability of the FG2a board

Item Specification



Maximum payload throughput (UL+DL)

840 Mbit/s




840 Mbit/s



Iu-PS Maximum payload throughput (UL+DL)

840 Mbit/s

NOTE



7.11.14 Technical Specifications for the GOUa BoardThe technical specifications for the GOUa board include hardware specifications andspecifications for optical ports and board processing capability. The hardware specificationsrefer to the dimension, power supply, power consumption, weight, operating temperature, andrelative humidity.

Hardware Specifications for the GOUa Board

Table 7-47 describes the hardware specifications for the GOUa board.

Table 7-47 Hardware specifications for the GOUa board

Item Specification


Power supply Two -48 V DC inputs working in active/standby mode. The backplaneof the subrack provides the power.


Product Description


Issue 03 (2008-08-30)

Item Specification


Weight 1.2 kg

Operatingtemperature (long-term)

0℃ to 45℃

Operatingtemperature (short-term)

-5℃ to +55℃

Relative humidity(long-term)

5% to 85%

Relative humidity(short-term)

5% to 95%

Specifications for the Processing Capability of the GOUa BoardTable 7-48 describes the specifications for the processing capability of the GOUa board.

Table 7-48 Specifications for the processing capability of the GOUa board

Item Specification




840 Mbit/s




840 Mbit/s



Iu-PS Maximum payload throughput (UL+DL)

840 Mbit/s



7-33

NOTE



Specifications for Optical Ports on the GOUa Board

Table 7-49 describes the specifications for the optical ports on the GOUa board.

Table 7-49 Specifications for optical ports on the GOUa board

Item Specification

Optical Module2.125G-850nm-0.5km-MM-ESFP

Optical Module1.25G-1310nm-10km-SM-ESFP

Mode Multi-mode Single-mode

Type LC/PC LC/PC

Maximum opticaltransmissiondistance

0.5 km 10 km

Average outputoptical power

-9.05 dBm to -2.5 dBm -9.05 dBm to -3.0 dBm

Minimum receiversensitivity

-17.0 dBm -20.0 dBm

Overload opticalpower

0.0 dBm -3.0 dBm

Center wavelength 850 nm 1,310 nm

Rate 2.125 Gbit/s 1.25 Gbit/s

7.11.15 Technical Specifications for the PFCU BoardThe technical specifications for the PFCU board are the dimension, power supply, powerconsumption, temperature range, and requirement for fan speed adjustment.

Table 7-50 describes the technical specifications for the PFCU board.

Table 7-50 Technical specifications for the PFCU board

Item Specification

Dimensions 270 mm x 35 mm

Input voltage range -40 V DC to -57 V DC inputs


Product Description


Issue 03 (2008-08-30)

Item Specification

Frequency of Pulse Width Modulation(PWM) signals

1 kHz

Temperature range -5℃ to +55℃ (basic requirement)

Requirement for fan speed adjustment The fan speed can be adjusted by 50% to 100%.

7.11.16 Technical Specifications for the PAMU BoardThe technical specifications for the PAMU board refer to the dimension, power supply, powerconsumption, and weight.

Table 7-51 describes the technical specifications for the PAMU board.

Table 7-51 Technical specifications for the PAMU board

Item Specification

Dimensions 340 mm x 72 mm

Power supply Two -48 V DC inputs working in active/standbymode.


Weight 0.2 kg



7-35

Date post:	09-Apr-2016
Category:	Documents
Upload:	bright-kpodoh
View:	6 times
Download:	1 times

RNC Product Description-(V200R010_03)

Documents