ran controller tech brief

8/4/2019 RAN Controller Tech Brief

1/40

Horizon RAN controller

Technical Brief

TECHNICAL BRIEF


2/40

Summary

This document provides information on Motorolas WCDMA Radio Network Controller (RNC).

This document includes:

Chapter Details1 Introduction to the RNC Describes the position of the RNC in the

WCDMA network.

2 Key Benefits Describes the key benefits of the RNC.

3 System Architecture Describes the hardware structure, logical

structure and hardware configuration of the

RNC.

4 Operation and

Maintenance

Describes the OM structure and OM functions

of the RNC.

5 Reliability Describes the system reliability, hardware

reliability and software reliability of the RNC.6 Technical Specifications Describes the technical specifications for the

RNC.

7 Installation Describes the hardware and software installation

requirements for the RNC.


3/40

Contents

1 Introduction to the RNC 4

2 Key Benefits 5

3 System Architecture 10

4 Operation and Maintenance 17

5 Reliability 25

6 Technical Specifications 27

7 Installation 35

A Acronyms and Abbreviations 36


4/40

4 TECHNICAL BRIEF: Horizon RAN controller

1 Introduction to the RNC

1.1 UMTS Network Topology

The RNC is a vital element of all UMTS/HSxPA

networks; the number deployed in a given network

depends on the size, capacity and geographical

coverage, of the network. RNCs and Node Bs

compose the UMTS Terrestrial Radio Access

Network (UTRAN).

Figure 1-1 shows the position of the RNC in a

UMTS/HSxPA network.

CN: Core Network CBC: Cell Broadcast

Center

MGW: Media Gateway MSC server: Mobile

Switching Center server

RNC: Radio Network

Controller

SGSN: Serving GPRS

Support Node

UE: User Equipment UTRAN: UMTS

Terrestrial Radio Access

Network

As shown in Figure 1-1, each RNC can be

connected to:

Node Bs through the lub interface

The MSC (or the MSC server and MGW in

R4/R5/R6), which processes Circuit Switched

(CS) services through the Iu-CS interface

The SGSN, which processes Packet

Switched (PS) services through the Iu-PS

interface

The CBC, which processes broadcast

services through the Iu-BC interface

Another RNC through the Iur interface

1.2 Main Functions of the RNC

The RNC provides the following main functions:

Broadcasting system information and controllingUE access

Performing mobility management, such ashandover and Serving Radio Network Subsystem

(SRNS) relocation

Performing radio resource management, such asMacro Diversity Combining (MDC), power contro

and cell resource allocation

Providing radio bearer services for both CSand PS domains

Providing transport channels between the CNand UEs

Ciphering and deciphering the signaling anddata on radio channels

Motorolas RNC solution is known as the Horizon

RAN controller and is referenced as such throughou

this document. All its interfaces, including the Iub,

Iur, Iu-CS, Iu-PS and Iu-BC are standard interfaces,

which enable the Horizon RAN controller to connect

to the Node B, RNC, MSC, SGSN and CBC of othernetwork equipment vendors.

Figure 1-1: Position of the RNC in a UMTS/HSxPA network


5/40


2 Key Benefits

2.1 Introduction

The RNC is a vital element of all UMTS/HSxPA

networks; the number deployed in a given network

depends on the size, capacity and geographical

coverage, of the network. RNCs and Node Bs

compose the UMTS Terrestrial Radio Access

Network (UTRA

The design of the Horizon RAN controller takes

into consideration the factors such as services,

capacity, transmission and Operation and

Maintenance (O&M).

The Horizon RAN controller brings the

following benefits:

All-IP Platform

High Integration and Large Capacity

Flexible Configurations Adapting to

Traffic Models

Resource Sharing Between Control Plane

and User Plane

Multiple Clock Sources

Diverse Transmission SolutionsDiverse

Transmission Solutions

Advanced RRM AlgorithmsAdvanced

RRM Algorithms

Advanced Solutions to Radio Data

ServicesAdvanced Solutions to Radio

Data Services

High Compatibility of Protocols

2.2 All-IP Platform

The Horizon RAN controller uses the all-IP Platform

of Advanced Radio Controller (PARC) developed by

Motorola. PARC unifies the switching system of

Asynchronous Transfer Mode (ATM), Time DivisionMultiplexing (TDM) and IP. Thus, it can serve as

a uniform platform of GSM, CDMA and WCDMA

controllers. This platform can meet the requirements

for the development of high-speed packet services

and fully protect network investment.

2.3 High Integration and Large Capacity

The Horizon RAN controller has the following

features:

The Horizon RAN controller is highly integrated.Based on the Gigabit Ethernet (GE) star non-blocking switching on the Medium Access Control

(MAC) sub-layer, the Horizon RAN controller

achieves a central switching capacity of 120 Gbps

The Horizon RAN controller supports up to 1,700Node Bs and 5,100 cells

The Horizon RAN controller supports up to 51,000Erlang voice traffic or a total of 3,264 Mbps PS

throughput in the uplink (UL) plus downlink (DL).

Such capacity, however, is implemented by only

two cabinets

The Horizon RAN controller provides a single-cabinet solution that supports 24,000 Erlang voice

traffic or 1,536 Mbps (UL + DL) PS throughput

2.4 Flexible Configurations Adaptingto Traffic Models

The number of signaling processing boards and that

of data processing boards are flexible so that the

quantity of resources on the user plane and control

plane can meet the requirements of traffic models.

In the case that a single set ratio of boardconfiguration is inconsistent with the actual traffic

model, the flexible configurations of boards in

the Horizon RAN controller help prevent wasting

resources. The waste of control plane resources may

attribute to the bottleneck at user plane resources

and the other way round.

2.5 Resource Sharing Between ControlPlane and User Plane

In the Horizon RAN controller, an SPUa board has

four independent subsystems. Each sub-rack has

a subsystem working as the Main Processing Unit(MPU) subsystem for the management of resources

on the user plane and resource allocation during

a call. The other subsystems work as Signaling

Process Unit (SPU) subsystems, which process


6/40

signaling messages on the Iu, Iur, Iub and Uu

interfaces to implement the signaling processing

function.

The SPU subsystems, working as the processor for

control plane data, form a control plane resource

pool; the DSPs, working as the processor for user

plane data, form a user plane resource pool.

The resources of control plane and user plane

within a sub-rack are managed and allocated by

the MPU subsystem. When a new call travels to

the sub-rack, the MPU subsystem forwards the

resources request to other sub-racks in case of

overload. If any sub-rack has enough resources of

control plane and user plane, the new call can be

successfully processed.

2.6 Multiple Clock Sources

Multiple clock sources are available for the Horizon

RAN controller. Thus, the Horizon RAN controller can

select the most convenient system synchronization

clocks.

The available clock sources are as follows:

Building Integrated Timing Supply System (BITS)

Global Positioning System (GPS)

Line clock extracted from the Iu interface

External 8kHz clock provided by an external device

The Horizon RAN controller can set a priority for

each clock source.

Note: If the Horizon RAN controller fails to obtain any externalclock, the Horizon RAN controller obtains its timing from its localoscillator. The timing signals generated by the local oscillator,however, do not meet the requirements of Node Bs in terms ofclock precision. In this instance, the associated Node Bs do notobtain their timing signals from the parent Horizon RAN controller.

2.7 Diverse Transmission Solutions

The Horizon RAN controller provides diverse

transmission solutions by supporting:

Multiple Iub Network Topologies

Multiple Types of Transmission Port

High Reliability of Transmission

Flexible Configuration of Interface Boards

IP Transport on the Iub/Iur/Iu Interfaces

Hybrid IP Transport on the Iub Interface

ATM/IP Dual Stack on the Iub Interface

Satellite Transmission on the Iub Interface

Efficient Transmission on the Iub Interface

Dynamic Management of Bandwidth

Inverse Multiplexing on ATM

Fractional Functions

Timeslot Cross Connection

Multilink PPP

2.7.1 Multiple Iub Network Topologies

The Horizon RAN controller supports multiple Iub

network topologies, such as star, chain and tree

topologies. The type of topology depends on the

site requirement.

2.7.2 Multiple Types of Transmission Port

The Horizon RAN controller provides multiple types

of physical transmission port for the Iub, Iur and Iu

interfaces.

The ATM transmission ports are of the following

types:

E1/T1

Unchannelized STM-1/OC-3c

Channelized STM-1/OC-3

The IP transmission ports are of the following

types:

E1/T1

Unchannelized STM-1/OC-3c

Channelized STM-1/OC-3

Fast Ethernet (FE)

GE



7/40

2.7.3 High Reliability of Transmission

To achieve high reliability of transmission, the

Horizon RAN controller uses the following

solutions:

Transmission port redundancy

Unchannelized optical ports support Multiplex

Section Protection (MSP) 1:1 or MSP 1+1

redundancy

Channelized optical ports support MSP 1:1

redundancy

FE or GE ports support redundancy and load

sharing between the ports

Diverse ways of fault detection:

Quick check based on Bi-directional ForwardingDetection (BFD)

Address Resolution Protocol (ARP) check

End-to-end ATM Continuous Check (CC) based

on the F5 protocol

2.7.4 Flexible Configuration of InterfaceBoards

The Horizon RAN controller does not place

restrictions on which slot holds interface boards for

the Iub, Iur or Iu. A sub-rack can host different types

of ATM and IP interface board at the same time.

2.7.5 IP Transport on the Iub/Iur/Iu Interfaces

In addition to ATM transport, the Horizon RAN

controller supports IP transport on the Iub, Iur and

Iu interfaces. This is consistent with the evolution

to an all-IP network, provides sufficient bandwidth

for high-speed and large-volume data services and

reduces the cost of construction, operation and

maintenance of transport networks.

2.7.6 Hybrid IP Transport on the Iub Interface

When IP transport is applied to the Iub interface,

data of different priorities can be transmitted

separately through E1/T1 ports and FE ports. The

transmission mode of a service depends on the

Quality of Service (QoS) requirement. Services with

high QoS requirements are transmitted through

E1/T1 ports and those with low QoS requirements

are transmitted on the Ethernet.

Hybrid IP transport guarantees the QoS and provides

sufficient interface bandwidth for high-speed PS

services such as High Speed Downlink Packet

Access (HSDPA) and High Speed Uplink Packet

Access (HSUPA), thus saving the transmission cost

and protecting Operator investment.

2.7.7 ATM/IP Dual Stack on the Iub Interface

ATM/IP dual stack is supported between the Horizon

RAN controller and a Node B. Services with high

QoS requirements are transmitted through ATM,

while those with low QoS requirements through IP.

Such data transmission guarantees the QoS and

provides sufficient interface bandwidth for high-speed PS services (HSDPA and HSUPA), thus

saving the transmission cost and protecting the

investment.

2.7.8 Satellite Transmission on theIub Interface

The Horizon RAN controller supports satellite

transmission on the Iub interface to cover isolated

geographical areas.

2.7.9 Efficient Transmission on theIub Interface

The Horizon RAN controller improves

transmission efficiency by supporting the

following techniques on the Iub interface:

Iub overbooking and Frame Protocol Multiplexing(FP MUX)

Without additional transmission devices, the

Horizon RAN controller improves the efficiency of

transmission on the Iub interface, thus increasing

the Operators revenue opportunities.

With Iub overbooking, the Horizon RAN controller

estimates the bandwidth of a service on the Iub

interface and allocates an appropriate bandwidth

to the service. In this way, the Iub transmission

efficiency increases greatly



8/40

With FP MUX, the Horizon RAN controller can

multiplex Iub FP data. That is, the Horizon RAN

controller multiplexes multiple User Datagram

Protocol (UDP) or IP packets into one data packet

in a specific format before transmitting it, thus

increasing the efficiency of IP transport on theIub interface

IP shaping/policing

Usually, the links on the Node B side are low-

speed ones. When a high-speed port on the

Horizon RAN controller connects to a low-speed

port on a Node B, packet loss may occur if the

Horizon RAN controller transmits packets to the

Node B. IP shaping/policing, however, can prevent

such packet loss, balance traffic and improve the

efficiency of transmission on the Iub interface

2.7.10 Dynamic Management of Bandwidth

The Horizon RAN controller detects the IP QoS

information, such as the packet loss rate, delay and

delay variation. Based on the QoS, the Horizon RAN

controller then adjusts the bandwidth of logical ports

and of resource groups; as a result, transmission

efficiency is enhanced.

2.7.11 Inverse Multiplexing on ATM

The Horizon RAN controller provides the Inverse

Multiplexing on ATM (IMA) function over E1/T1 links.

An ATM cell stream from a high-speed transport

link is multiplexed inversely onto multiple low-speed

E1/T1 links. Then, at the receiver end, the low-speed

cell streams are converged to the original high-

speed cell stream.

The IMA function enables high-speed transmission

through low-speed links. Thus, it broadens the

application scope of E1/T1 links. In addition, this

function has a relatively high fault tolerance.

Provided that the number of working links is not

smaller than the specified minimum number of

active links in an IMA group, services can continue.

Thus, the IMA function ensures high transmission

reliability.

2.7.12 Fractional Functions

The Horizon RAN controller provides the fractional

functions, that is, fractional ATM and fractional

IMA. The fractional functions enable 3G network

equipment to share the same E1/T1 links as the2G network, thus allowing 2G and 3G concurrent

transmissions.

With the fractional functions, Node Bs can quickly

be deployed, for instance at an early stage of UMTS

network roll-out by using existing 2G transmission

resources. Thus, the network can be launched at a

comparatively low cost and within a relatively short

period of time.

2.7.13 Timeslot Cross Connection

The Horizon RAN controller supports the timeslot

cross connection function. The 2G equipment

cross-connects the timeslots on a 2G link to the

Horizon RAN controller, so as to enable concurrent

transmission of 2G and 3G data. Such timeslot cros

connection does not require additional timeslot

cross connection equipment.

2.7.14 Multilink PPP

The Horizon RAN controller provides the Multilink

PPP (MLPPP) function. This function combines

physically independent links to form only one logical

channel. Thus, the network layer can send data

directly to this logical channel. The MLPPP functionprovides a relatively high bandwidth and implements

rapid data forwarding.

2.8 Advanced RRM Algorithms

The Horizon RAN controller uses Radio Resource

Management (RRM) algorithms in the following

functions:

Power control

Handover

Radio resource allocation

Call Admission Control (CAC)

Load control



9/40

In addition, the Horizon RAN controller applies these

algorithms in features such as HSDPA, HSUPA

and Multimedia Broadcast and Multicast Service

(MBMS). Thus, the Horizon RAN controller offers

optimum network coverage, capacity and quality.

2.8.1 Power Control

The Horizon RAN controller uses outer loop power

control algorithms. It aims to provide the required

quality for UEs when the radio environment changes

and to increase the usage of system capacity.

2.8.2 Handover

The Horizon RAN controller supports flexible

handover strategies and parameter configurations.

Based on different coverage areas, services and

loads, it performs different kinds of handover,

such as intra-frequency handover, inter-frequency

handover and inter-RAT handover. Thus, it improves

the speech quality, reduces the call drop rate and

implements traffic absorption in special areas.

2.8.3 Radio Resource Allocation

Based on the QoS requirements, actual traffic

volume and actual cell load, the Horizon RAN

controller can allocate resources dynamically. Thus,

it fulfills the communication requirements and

increases the efficiency of radio channel resources.

2.8.4 CAC and Load Control

The Horizon RAN controller applies multiple

technologies, such as load sharing and admission

based on rate downsizing, to balance loads between

cells and to control service access. Thus it increases

the system capacity and guarantees the current

QoS.

2.8.5 Service Differentiation Based onSubscriber Priorities

Based on the allocation retention priorities set at

the Core Network for subscribers, the Horizon RAN

controller can set the subscribers to three levels:

gold, silver and bronze. The Horizon RAN controller

then provides different services for the three levels

of subscribers.

Based on priorities of subscribers, the HorizonRAN controller sets different Guaranteed Bit

Rates (GBRs) for Best Effort (BE) services of

different subscribers. GBR guarantees that the

basic requirements of BE services are met

With the pre-emption algorithm, high-prioritysubscribers can pre-empt the resources over

low-priority subscribers

With the algorithm of rate downsizing againstcongestion, the Horizon RAN controller

preferentially downsizes the rates of low-priority

subscribers to their GBRs

With the scheduling algorithm, the HorizonRAN controller proportionally allocates

bandwidths to subscribers. This algorithm takes

subscriber priorities into account in the condition

that the GBRs of the subscribers are guaranteed

With the flow control algorithm, the HorizonRAN controller proportionally allocates

bandwidths to subscribers. This algorithm takes

subscriber priorities into account in the condition

that the GBRs of the subscribers are guaranteed

When radio resources are limited, the Horizon RAN

controller can guarantee GBRs of subscribers before

allocating the remaining resources proportionally.

2.9 Advanced Solutions to RadioData Services

The Horizon RAN controller supports advanced

technologies, such as HSDPA, HSUPA and MBMS,

to meet the requirements of different types of data

service.

2.9.1 HSDPA

The Horizon RAN controller supports HSDPA as the

solution for high-speed downlink data transmission.

The downlink (DL) rate for a single UE can reach up

to 14.4 Mbps on the physical sub-layer.

In addition, the Horizon RAN controller supports

Voice over IP (VoIP) over HSDPA and IP Multimedia

Subsystem (IMS) over HSDPA.



10/40

HSDPA enhances the performance of the UMTS

network in the following aspects:

Higher DL data rate

Shorter service delay and more pleasant userexperience in high-speed services

More efficient DL coding and power utilization

2.9.3 MBMS

The Horizon RAN controller supports MBMS to

provide the high-speed multimedia broadcast

service. The transmission rate of MBMS services

can reach up to 256 kbps.

MBMS enhances resource efficiency and provides

diversified multimedia services.

2.10 High Compatibility of Protocols

The Horizon RAN controller is developed according

to 3GPP R6 specifications. It is compatible with

other Network Elements (NEs) and UEs based on

3GPP R6, R5, R4, or R99 specifications.

3.1 Physical Structure

3.1.1 Cabinet Appearance

The Horizon RAN controller design complies with

IEC60297 and IEEE standards.

Figure 3-1 shows the cabinet.

3.1.2 Cabinet Components

TThe Horizon RAN controller comprises of the

following two types of cabinet:

RNC Switching Rack (RSR)

RNC Business Rack (RBR)

Figure 3-2 shows the components of the cabinets.

Note: The RINT refers to the interface board of the Horizon RANcontroller. Physically, there is no board named RINT.

RSR

The RSR provides the single-cabinet solution.

The RSR has the following components:

One RNC Switching Sub-rack (RSS)

Up to two RNC Business Sub-racks (RBSs)as required


Figure 3-1: Horizon RAN controller cabinet

Figure 3-2: Components of the Horizon RAN controller cabinets


11/40

RBR

The RBR is configured when the required service

processing capability exceeds the specifications for

the RSR. At most one RBR can be configured.

The RBR is configured with only RBSs. The number

of RBSs in the RBR ranges from 1 to 3. If the RBR is

configured with one or two RBSs, the RBSs should

be configured from the bottom to the top.

3.1.3 Subrack Components

The Horizon RAN controller has two types of sub-

rack, according to board configuration. They are the

RSS and the RBS. The Horizon RAN controller can

be configured with up to six sub-racks. Among the

sub-racks, one is the RSS and the others are RBSs.

The number of RBSs ranges from 0 to 5.

The sub-racks of the Horizon RAN controller have

a standard width of 19 inches, which complies

with the IEC60297 standard. The height of a single

sub-rack is 12 U. In a sub-rack, the backplane is

positioned in the middle and front and rear boards

are installed on both sides of the backplane, as

shown in Figure 3-3. The slots are of the same

length.

A: front boards B: backplane C: rear boards

Each sub-rack of the Horizon RAN controller provides

a total of 28 slots. The 14 slots on the front side of

the backplane are numbered from 0 to 13 and those

on the rear side from 14 to 27.

On each plane from leftmost to rightmost, every two

even- and odd-numbered neighboring slots have an

active/standby relationship. For example, slots 0 and

1 are active/standby slots. The same is true for slots

2 and 3. Only the boards that work in active/standby

mode must be installed in active/standby slots.

3.1.4 RSS Subrack

The mandatory RSS is configured at the bottom of

the RSR. The RSS is the central switching sub-rack

of the Horizon RAN controller.

This sub-rack has the following functions:

Connecting to each RBS and transferring databetween RBSs through data switching on the

` MAC sub-layer

Providing system timing signals

Providing the same service processing functionsas the RBS

Serving physical transmission on the Iub, Iur andIu interfaces

Performing O&M management of the BackAdministration Module (BAM)

Figure 3-4 shows the boards in the RSS.

Note: Figure 3-4 presents only an example of board configuration.The configuration may be changed as required.


Figure 3-3: Sub-rack of the Horizon RAN controller

Figure 3-4: Boards in the RSS


12/40

The RSS provides 28 slots. Table 3-1 describes the

boards in the RSS.

Table 3-1: Boards in the RSS

Board Full Spelling Function Configuration

DPUb RNC Data

Processing Unit

REV:b

Processing and distributing service data on

the user plane

The following slots

are available for the

DPUb:

Slots 811 and

1419 in the RSS

Slots 819 in an

RBS

GCUa RNC General Clock

Unit REV:a

Performing phase-lock and hold on

the system clock

Generating RNC Frame Number (RFN)

signals for the system

Two boards are

permanently

configured in slots

12 and 13 of the

RSS.GCGa RNC General Clock

with GPS Card

REV:a

Having all the functions of the GCUa; in

addition, receiving and processing GPS

signals

Two boards are

permanently

configured in slots

12 and 13 of the

RSS.

OMUa RNC Operation and

Maintenance Unit

REV:a

Performing configuration management,

performance management, fault

management, security management,

loading management and so on

Working as the O&M agent of the

OMC-S/T and Local Maintenance

Terminals (LMTs) to provide the

Horizon RAN controller O&M interface

for the OMC-S/T and LMTs and to

control communication between the

Horizon RAN controller and the

OMC-S/T/LMTs

One board is

permanently

configured in slots

20 and 21 of the

RSS and the other in

slots 22 and 23.

SCUa RNC GE Switching

and Control Unit

REV:a

Providing MAC switching and enabling

convergence of ATM and IP networks

Providing 60 Gbps switching capacity

Providing the port trunking function

Enabling inter-sub-rack connections

Providing configuration and maintenance

of a sub-rack or of the whole Horizon

RAN controller

Distributing timing signals and RFN

signals for the Horizon RAN controller

Two boards are

permanently

configured in slots 6

and 7.



13/40


SPUa RNC Signaling

Processing Unit

REV:a

Processing high-layer signaling of the

Uu, Iu, Iur and Iub interfaces

Processing transport layer signaling

Allocating and managing various resources

necessary to service setup and

establishing signaling and service

connections

Providing 4 independent processor

systems

Processing RFN signals

The following slots


SPUa:

Slots 05 and 811

in the RSS

Slots 05 and 811

in an RBS

AEUa RNC 32-port ATM

over E1/T1/J1

Interface Unit REV:a

Providing 32 E1s/T1s

Providing ATM over E1/T1

Providing 32 IMA groups or 32 UNI links

(Each IMA group contains a maximum of

32 IMA links.)

Providing the fractional ATM and fractional

IMA functions

Providing the timeslot cross connectionfunction

Providing ATM Adaptation Layer 2 (AAL2)

switching

Extracting the clock from E1/T1 links,

exporting 2 MHz signals and sending the

2 MHz timing signals to the GCUa/GCGa

The following slots


AEUa:

Slots 1419 and

2427 in the RSS

Slots 1427 in

an RBS

AOUa RNC 2-port ATM over

Channelized Optical

STM-1/OC-3 Interface

Unit REV:a

Providing 2 STM-1/OC-3 optical ports

Providing 126 E1s or 168 T1s

Providing ATM over E1/T1 over SDH

Providing the IMA and UNI functions

Providing 84 IMA groups, each of which

contains 32 E1s/T1s

Providing AAL2 switching

Receiving timing signals from upper-level

equipment and sending them to the

GCUa/GCGa

Providing timing signals for Node Bs

The following slots


AOUa:

Slots 1419 and

2427 in the RSS

Slots 1427 in

an RBS

UOIa RNC 4-port

ATM/Packet over

Unchannelized

Optical STM-1/OC-3c


Providing 4 STM-1/OC-3c optical ports

Providing ATM over SDH or IP over SDH



GCUa/GCGa


The following slots


UOIa:

Slots 1419 and

2427 in the RSS

Slots 1427 in

an RBS

SCUa RNC GE Switching

and Control Unit

REV:a

Providing MAC switching and enabling

convergence of ATM and IP networks

Providing 60 Gbps switching capacity

Providing the port trunking function

Enabling inter-sub-rack connections

Providing configuration and maintenance

of a sub-rack or of the whole Horizon RAN

controller

Distributing timing signals and RFN signals

for the Horizon RAN controller

Two boards are

permanently

configured in slots 6

and 7.

RINT



14/40


PEUa RNC 32-port Packet

over E1/T1/J1


Providing 32 E1s/T1s

Providing IP over PPP/MLPPP over E1/T1

Providing 128 Point-to-Point Protocol (PPP)

links or 64 MLPPP groups (Each MLPPP

group contains a maximum of 8 MLPPP

links.)

Providing the timeslot cross connection

function



GCUa/GCGa


The following slots


PEUa:

Slots 1419 and2427 in the RSS

Slots 1427 in

an RBS

POUa RNC 2-port IP over

Channelized Optical

STM-1/OC-3 Interface

Unit REV:a

Providing 2 STM-1/OC-3 optical ports

Providing 126 E1s or 168 T1s

Providing IP over E1/T1 over SDH



GCUa/GCGa Providing timing signals for Node Bs

The following slots


AEUa:

Slots 1419 and

2427 in the RSS

Slots 1427 in

an RBS

FG2a RNC Packet over

Electrical 8-port FE or

2-port GE Ethernet


Providing 8 FE ports or 2 GE

electrical ports

Providing IP over FE or IP over GE

The following slots


AEUa:

Slots 1419 and

2427 in the RSS

Slots 1427 in

an RBS

GOUa RNC 2-port Packet

over Optical GE

Ethernet Interface

Unit REV:a

Providing 2 GE optical ports

Providing IP over GE

The following slots


UOIa:

Slots 1419 and

2427 in the RSS

Slots 1427 in

an RBS

Note:The RSS can be configured with one or two OMUa boards.In the latter case, the two boards work in active/standby mode.

3.1.5 RBS Sub-rack

TThe optional RBS is configured in the RSR or

the RBR. The RBS is the basic service processing

sub-rack of the Horizon RAN controller. Working

as the extension sub-rack of the RSS, the RBS is

used to extend the service processing capability of

the Horizon RAN controller. This sub-rack has the

following functions:

Processing signaling on the control plane

Processing and distributing service data onthe user plane

Serving physical transmission on the Iub, Iurand Iu interfaces

Figure 3-5 shows the boards in the RBS.

Note: Figure 3-5 presents only an example of board configuration.The configuration may be changed as required.

Figure 3-5: Boards in the RBS



15/40


The RBS provides 28 slots. The RBS holds all types of

board in the RSS except the GCUa/GCGa and OMUa.

3.2 Logical Structure

The Horizon RAN controller consists of the

following functional modules:

Internal Switching Module

User Plane Data Processing Module

Control Plane Data Processing Module

Clock Module

Transmission Interface Module

O&M Module

3.2.1 Internal Switching Module

The internal switching module is mainly implemented

by the SCUa boards. The SCUa in the RSS performs

first-level switching and that in the RBS performs

second-level switching. Thus, the Horizon RAN

controller provides internal MAC switching at two

levels. The two-level switching enables full connection

between all modules of the Horizon RAN controller.

3.2.2 User Plane Data Processing Module

The user plane data processing module is mainlyimplemented by the DPUb boards. This module

performs protocol processing at each layer on the

user plane data for the RNC.

The DPUb boards perform the following protocol:

Frame Protocol (FP)

MDC

MAC

RLC

PDCP

Iu User Plane (Iu UP) protocols

GTP-U

3.2.3 Control Plane Data Processing Module

The control plane data processing module is mainly

implemented by the SPUa boards. This module

processes control plane signaling on each interface

for the RNC. The processed messages are of thefollowing types:

Radio Access Network Application Part (RANAP)

Node B Application Part (NBAP)

Radio Network Subsystem Application Part(RNSAP)

Radio Resource Control (RRC)

Service Area Broadcast Protocol (SABP)

The SPUa boards are configured in both the RSS

and RBSs.

3.2.4 Clock Module

The clock module is mainly implemented by the

GCUa/GCGa boards and the clock processing units

of other boards. This module provides the clock for

the operation of the RNC; generates RFN signals

and provides Node Bs with timing signals.

The GCUa/GCGa boards are configured only in the

RSS. If the RNC requires GPS signals, the GCGa is

required.

3.2.5 Transmission Interface Module

The transmission interface module is mainly

implemented by the AEUa, AOUa, UOIa, PEUa,

POUa, FG2a, or GOUa boards. This module provides

the transmission interface between the Horizon RAN

controller and other NEs. In addition, it performs

related protocol processing at the transport network

layer.

For ATM transport, the AAL2 and ATM Adaptation

Layer 5 (AAL5) messages are terminated at the

transmission interface module.

For IP transport, this module processes UDP and

IP messages on the user plane and forwards IP

messages on the control plane.


16/40


3.2.6 O&M Module

The O&M module is mainly implemented by the

LMT, BAM and related modules of host boards. This

module performs operation and maintenance on the

Horizon RAN controller.

3.3 Hardware Configuration

3.3.1 Minimum Configuration

In minimum configuration, the Horizon RAN

controller needs only one RSR that has only the

RSS. The minimum configuration applies to an early

stage of construction of a commercial network.

Figure 3-6 shows the minimum configuration of

the Horizon RAN controller.

Figure 3-6: Minimum configuration of the HorizonRAN controller

The maximum capacity of the Horizon RAN

controller in minimum configuration is as

follows:

6,000 Erlang voice traffic or 384 Mbps

(UL + DL) PS throughput

200 Node Bs

600 cells

3.3.2 Maximum Configuration

In maximum configuration, the Horizon RAN

controller requires two cabinets, that is, one RSR

and one RBR. Additional RBSs may be added to

expand and the system capacity without disruptingongoing services.

Figure 3-7 shows the maximum configuration of the

Horizon RAN controller.

Figure 3-7: Maximum configuration of the Horizon

RAN controller

The maximum capacity of the Horizon RAN

controller (maximum configuration) is as follows

51,000 Erlang voice traffic or 3,264 Mbps

(UL + DL) PS throughput

1,700 Node Bs

5,100 cells

3.3.3 Typical Configurations

Table 3-2 shows the typical configurations of the

Horizon RAN controller. The configuration may be

changed as required.

Table 3-2 Typical configurations of the Horizon

RAN controller

Number of Sub-racks BHCA Voice Traffic(Erlang)

(UL + DL) PSThroughput (Mbps)

Number of Node Bs Number of Cells

1 RSS 160,000 6,000 384 200 6001 RSS + 1 RBS 400,000 15,000 960 500 1,500

1 RSS + 2 RBSs 640,000 24,000 1,536 800 2,400

1 RSS + 3 RBSs 880,000 33,000 2,112 1,100 3,300

1 RSS + 4 RBSs 1,120,000 42,000 2,688 1,400 4,200

1 RSS + 5 RBSs 1,360,000 51,000 3,264 1,700 5,100

Note: BHCA: Busy Hour Call Attempt

Note: The values of BHCA and voice traffic are calculated based on a Motorola traffic model.


17/40

3.3.4 Hardware Expansion Schemes

The capacity of the Horizon RAN controller may be

increased by adding RBSs or service processing

boards. The addition of SPUa boards contributes

to the expansion of control plane resources andthe addition of DPUb boards contributes to the

expansion of user plane resources.

When adding boards, note the following items:

In the RSS, SPUa boards can be configured in

slots 05 and 811. The maximum number of

SPUa boards in the RSS is 10. In an RBS, SPUa

boards can be configured in slots 05 and 811.

The maximum number of SPUa boards in an

RBS is 10.

In the RSS, DPUb boards can be configured

in slots 811 and 1419. The maximum number

of DPUb boards in the RSS is 10. In an RBS,

DPUb boards can be configured in slots 819.

The maximum number of DPUb boards in an

RBS is 12.

Table 3-3 lists the processing capabilities of SPUa

and DPUb boards. The processing capability of the

SPUa can be calculated on the basis of the capability

of each SPU subsystem.

Table 3-3: Processing capability of a single SPU subsystem

or DPUb board


Board or Subsystem BHCA Voice Traffic (Erlang) (UL + DL) PS Throughput(Mbps)

SPU subsystem 20,000

DPUb 1,500 96

4 Operation and Maintenance

4.1 O&M Structure

Figure 4-1 shows the O&M system of the Horizon

RAN controller. The system consists of the Front

Administration Module (FAM), BAM, O&M

terminals and alarm box. These components

are described as follows:

The FAM consists of the boards in the RSS and

RBSs. It is the O&M object entity.

The physical entity of the BAM is the OMUa

boards in the RSS. The BAM collects and

processes O&M information and sends the

information to Local Maintenance Terminals

(LMTs) and the OMC-S/T.

The LMTs are O&M terminals on the Horizon

RAN controller side. The OMC-S/T is a centralized

O&M system.

The alarm box provides audible and visible alarms.

Figure 4-1: O&M system of the Horizon RAN controller

BAM: Back

Administration Module

FAM: Front

Administration Module

LMT: Local

Maintenance Terminal

IP: Internet Protocol

VLAN: Virtual Local Area

Network


18/40


The LMT is the O&M terminal on the NE side. It can

access the BAM through Virtual Local Area Network

(VLAN), an intranet and the Internet.

The LMT is an intelligent Man Machine Language

(MML) client working in Graphic User Interface (GUI)

mode. It provides the Horizon RAN controller with

O&M functions.

Through an external alarm box, the LMT can report

audible and visible alarms if faults are detected.

4.2 O&M Functions

The Horizon RAN controller provides MML

commands and GUIs as an interface for system

management, configuration, maintenance, alarm

management and so on. Such an interface is explicit

and easy to use. In addition, the Horizon RAN

controller can check the data integrity for an MMLcommand to be run.

This section describes the following OM

functions:

Security Management

Configuration Management

Maintenance Management

Fault Detection

Performance Management

Alarm Management

Loading Management

Status Monitoring

Message Tracing

Log Management

Software Management

4.2.1 Security Management

Horizon RAN controller security management

provides the following functions:

Grade-based operator right setting

You can set the operator right, operation time

limit and password to ensure system security

and operation flexibility.

Operator information protection

If no operation is performed for a certain period, the

user interface is automatically locked.

File Transfer Protocol (FTP) transmission based

on ciphering

This ensures the security of FTP transmission.

Encryption of the communication interface

between the Horizon RAN controller and the

Element Management System (EMS)

The Horizon RAN controller uses the Security

Socket Layer (SSL) protocol to fulfill transmission

of cipher-text over the O&M channel between the

Horizon RAN controller and the EMS. This ensures

data security.

4.2.2 Configuration Management

The Horizon RAN controller provides certain

functions for configuration management. These

functions are described in the following sections.

Automatic Data Configuration

The Horizon RAN controller can automatically

generate the configuration data that is necessary

for internal physical and logical connections and

configure the data for the corresponding parts. No

manual configuration is required. Only the data for

connections between the Horizon RAN controller

and external devices needs to be configured, thus

improving the serviceability of the Horizon RAN

controller.

Online and Offline Data Configuration

The Horizon RAN controller supports the

following configuration modes:

Offline data configuration

In offline data configuration mode, configuration

data is stored only in the BAM. The data is not

sent to the host before being loaded onto

the host. Therefore, this mode increases theefficiency of configuring a large amount of

data. The Horizon RAN controller also supports

offline data configuration based on host sub-racks

Therefore, it allows capacity expansion without

disrupting services.


19/40


Online data configuration

In online data configuration mode, configuration

data is sent to the host immediately after the

configuration. There is no need to reset the

Horizon RAN controller or to reload the data.

Thus, dynamic data configuration is enabled.

Dynamic Batch Data Configuration

The Horizon RAN controller supports dynamic

configuration of data in batches. With this function,

the batch data configuration scripts are executed

when the Horizon RAN controller is offline. After the

Horizon RAN controller switches to the online mode,

the BAM sends all the configuration data to the host

in batches. The data takes effect with no need to

restart or reset the sub-racks or boards. This avoids

disrupting ongoing services.

In the case of bulk data modification, such as

Node B re-parent and change of interface board

types, dynamic batch data configuration improves

efficiency.

Data Configuration Right Control

Under data configuration right control, only one

user has the right to perform data configuration

for the Horizon RAN controller at any time. The

configuration is allowed on only one configuration

console at a time, that is, either on the LMT or on

the OMC-S/T.

With the control, data configuration on the LMT and

that on the OMC-S/T are not allowed at the same

time, thus improving reliability of the Horizon RAN

controller.

Data Configuration Rollback

The Horizon RAN controller provides the data

configuration rollback function. If data configuration

fails to achieve the expectation or even causes

equipment or network exceptions, you can perform

rollback to restore the configurations quickly. Thisensures the correct function of the Horizon RAN

controller.

Data Backup

When two OMUa boards are configured, they

work in active/standby mode. The data on the

standby OMUa is synchronized with that on the

active OMUa. The Horizon RAN controller supports

automatic and manual data backup. It provides a

data backup and recovery tool.

Data Validity Check

The Horizon RAN controller can check the integrity

and consistency of configuration data, such as the

data of a cell.

Configuration Data Query

The Horizon RAN controller supports the object-

based query of configuration data.

Online Reconfiguration of the RINT and

Backup Mode

The Horizon RAN controller supports online

reconfiguration of the RINT and of the board

and port redundancy mode, thus facilitating

reconfiguration of services.

Dynamic Assignment of IP Addresses

to a Node B

When ATM transport is applied to the Iub interface,

the Horizon RAN controller uses the Bootstrap

Protocol (BOOTP) to automatically assign the O&M

IP address to a Node B.

When IP transport is applied to the Iub interface,

the Horizon RAN controller uses the Dynamic Host

Configuration Protocol (DHCP) to automatically

assign the OM IP address to the Node B.

Compared with BOOTP, DHCP has relatively

powerful functions. In addition, DHCP is compatible

with BOOTP.

Network Parameter Setting

There are two types of radio network parameters

of the Horizon RAN controller: RNC-oriented and

cell-oriented. They can adapt to different radio

environments.


20/40


4.2.3 Maintenance Management


functions for maintenance management. These

functions are described in the following topics.

Board Maintenance


following board maintenance functions:

Resets on different levels, including equipment

reset, sub-rack reset, board reset and

subsystem reset

Query of board reset causes

Hot swap

Setting of boards to the out-of-service statefor troubleshooting

Query of board status and version information

Board self-detection and board diagnosis test

Query of the Central Processing Unit (CPU)

usage of a board subsystem

Forced active/standby board switchover initiated

on the LMT

Object Status Query

The Horizon RAN controller supports the query

of the status of certain objects, the reasons for

status changes and the time when the status

changes. The objects are as follows:

Equipment objects, such as boards, subsystems,

Digital Signal Processors (DSPs), clocks, optical

ports and BAM

Physical transmission resource objects, such as

E1/T1 links, IMA links and UNI links

IP transport links, such as PPP links and

MLPPP links

Logical transmission resource objects, such as

Signaling ATM Adaptation Layer (SAAL) links,

Stream Control Transmission Protocol (SCTP)

links, Message Transfer Part level 3 - broadband

(MTP3-b) links, AAL2 paths, IP paths, Node B

Control Ports (NCPs) and Communication Control

Ports (CCPs)

Radio resource objects, such as cells

and channels

Panel Emulation

The emulated panel on the LMT interface can

display the status of boards, Light Emitting Diodes

(LEDs) on boards, external physical ports and DSPs.

Physical Link Maintenance

The Horizon RAN controller supports the status

query and loopback test of physical links.

Logical Link Maintenance


following logical link maintenance functions:

Status query, activation and deactivation of

Signaling System No. 7 (SS7) signaling links

Status query of SAAL links and SCTP links

Query about the status of IP traffic channels

and dynamic adjustment of the IP bandwidth

Status query, blocking, unblocking and reset

of AAL2 traffic channels

Status query and reset of PPP links, MLPPP

links and MLPPP groups

Status query of IMA groups, UNI links and

IMA links

Loopback test

ATM F5 end-to-end detection

SS7 Signaling Point Maintenance

The Horizon RAN controller supports maintenance

of SS7 signaling points. The maintenance includes

query, inhibit and un-inhibit of destination signaling

points.

Measurement of Out-of-Service Node Bs or Cells

If a Node B or cell is out of service, it is unavailable.


measurement of out-of-service duration and out-of-

service ratio. The measurement results can be used

to analyze the general serving states of Node Bs

or cells.


21/40


Node B Blocking and Unblocking

The Horizon RAN controller can block a Node B by

deactivating all the cells controlled by this Node B.

The Horizon RAN controller can also unblock a Node

B by activating all of the cells controlled by this

Node B.

Cell Blocking and Unblocking

The Horizon RAN controller can block or

unblock cells.

When a cell is blocked, all the connections to the cell

are released and the cell becomes unavailable. After

it is unblocked, the cell becomes available again.

Guarantee for VIP Cells and Node Bs

The Horizon RAN controller can provide O&M

guarantee and service guarantee for VIP cells and

Node Bs. Thus, the VIP cells and Node Bs can run

stably with high quality of service.

O&M guarantee means monitoring VIP cells

and Node Bs through detailed monitoring items

on a specific interface, so that the maintenance

engineers can identify faults rapidly and rectify

them efficiently.

Service guarantee means providing special

network planning and configuration for VIP

cells and Node Bs, so that they can providebetter services. The resources shared between

VIP cells, VIP Node Bs, common cells and

common Node Bs are offered preferentially to

VIP cells and VIP Node Bs.

Remote Maintenance

The Horizon RAN controller supports remote

maintenance by allowing remote access through the

Internet or Virtual Private Network (VPN).

Provision of O&M Channels for the Node Bs

The Horizon RAN controller provides the

following O&M channels for Node Bs:

Transparent O&M channels, through which Node

Bs can be operated and maintained via the LMT

of the Horizon RAN controller or on the OMC-S/T

Reverse O&M channels, through which other

Node Bs on the local Node B can be operated

and maintained

4.2.4 Fault Detection

The Horizon RAN controller provides physical layer

fault detection, data link layer fault detection and

other fault detection.

Physical layer fault detection covers the

following aspects:

Local E1 loopback test

Remote E1 loopback test

E1 Bit Error Rate (BER) test

E1 loopback detection

E1 misconnection test

SDH loopback detection

FE/GE port fault detection

Data link layer fault detection covers the

following aspects:

AAL2 path fault detection

IP path fault detection

SAAL fault detection

SCTP fault detection

PPP/MLPPP misconnection test

Node B OM IP over ATM (IPoA) fault detection

Iu-PS IPoA fault detection

Virtual Connect Link (VCL) CC

Other fault detection covers the following

aspects:

Inter-Process Communication (IPC)

connectivity check

Cell common channel fault detection

RFN fault detection

Clock fault detection

Board loading control fault detection


22/40


4.2.5 Performance Management

The Horizon RAN controller provides various

performance counters for the upper-layer

Network Management System (NMS) to facilitate

performance analysis and network optimization.

By default, the Horizon RAN controller supports two

measurement periods. One is the normal period

whose duration is 30 minutes and the other is the

short period whose duration is 5 minutes. The latter

is used to monitor Key Performance Indicators (KPIs)

in real time.

A measurement item supports both measurement

periods, that is, a measurement item can be

included in both a normal-period task and a short-

period task.

Various performance measurement tasks may

be registered on the OMC-S/T. The Horizon RANcontroller can store measurement results generated

in the past 72 hours.

4.2.6 Alarm Management

The Horizon RAN controller provides advanced fault

diagnosis and handling methods, performs relevance

analysis of alarms raised from the host and reports

valid alarms to the user.


functions for maintenance management. These


Alarm Processing

Alarm information may be browsed in real time,

query history alarm information and store alarm

information. The online help provides detailed

troubleshooting methods for each alarm.

The Horizon RAN controller can store the history

alarm information generated in the past 90 days and

up to 100,000 alarms.

Alarm Masking

The Horizon RAN controller allows the masking

of derivative alarms to reduce the number of the

reported alarms.

Alarm Filtering

The Horizon RAN controller can filter the alarms of

a specific object. If an object is filtered, the alarms

of this object are not sent to the alarm management

system.

Alarm Indication

When a fault alarm is generated, the Horizon RAN

controller can notify the operator in the following

ways: blinking of the icon, audible indication of the

terminal and audible and visible indications on the

alarm box.

Classified Alarm Management

The Horizon RAN controller supports classified

management of alarms raised from normal cells andNode Bs and from abnormal ones. The latter can

be the following cells and Node Bs: those under

commissioning and those not put into use.

4.2.7 Loading Management

The following modes are available for loading

program files and data files onto boards of the

Horizon RAN controller:

Loading from the flash memories of the boards

Loading from the BAM

The mode of loading program files and data files

onto a board depends on the consistency between

the files in the flash memory of the board and those

in the BAM. See specifics as follows:

If the files are consistent, the board loads the file

from its flash memory

If the files are inconsistent, the board loads the

files from the BAM and updates the files in the

flash memory of the active workspace on the

board, so as to ensure the program and data

consistency.


23/40


4.2.8 Status Monitoring

The Horizon RAN controller can monitor the

system status in real time, including CPU usage,

cell performance, connection performance, link

performance and board resources.


following cell performance:

Pilot transmit (TX) power of the Primary

Common Pilot Channel (P-CPICH)

UL Received Total Wideband Power (RTWP)

DL frequency TX power

Number of UEs, including UEs on Dedicated

Channels (DCHs), UEs on common channels,

HSDPA UEs and HSUPA UEs

Node synchronization

UL CAC

DL CAC

UL equivalent number of users

DL equivalent number of users

Usage of the code tree

Minimum High Speed Downlink Shared

Channel (HS-DSCH) power requirement

Bit rate provided by the HS-DSCH

Bit rate provided by the Enhanced Dedicated

Channel (E-DCH)


following connection performance:

Signal-to-Noise Ratio (SNR) and receive (RX)

signal code power of a cell

Measurement value of Signal-to-Interference

Ratio (SIR) of a UL radio link set

SIR target of a UL radio link set

SIR error value of a UL radio link set

Block Error Rate (BLER) of a UL transport channel

BLER of a DL transport channel

DL code TX power

UE TX power

BER of a UL physical channel

UL traffic volume

DL traffic volume

UL throughput and bandwidth

DL throughput and bandwidth

Handover delay

Adaptive Multi Rate (AMR) mode


following link performance:

IMA groups

UNI links

Fractional ATM links

SAAL links

IPoA Permanent Virtual Channels (PVCs)

IP path QoS

AAL2 paths

IP paths

FE/GE traffic

Traffic on PPP links

Traffic on MLPPP groups

Traffic on SCTP links

The Horizon RAN controller can monitor the board

resource, that is, the license.

4.2.9 Message Tracing

The Horizon RAN controller can perform the

following types of message tracing:

Message tracing on standard interfaces

Protocol message tracing on the transport layer

Call tracing

Tracing on missed neighboring cell configuration

Cell message tracing

Intra-system inter-module message tracing


24/40


Message tracing on the serial port

after redirection

IP tracing

Call Data Tracing (CDT)

CellDT message tracing

Location message tracing

The function of message tracing is integrated into

the LMT, which facilitates problem identification. The

Horizon RAN controller also provides a tool called

Trace Viewer, which allows the viewing of the stored

messages.

4.2.10 Log Management

Various logs are available that show the state

of the Horizon RAN controller and that facilitate

the troubleshooting of faults. The Horizon RAN

controller provides the following logs:

Operation log: records the operation information

of operators in real time

Running log: records the running information of

the Horizon RAN controller in real time

Subscriber log: records the calling procedure

information, which, in case of calling failure, is

exported to the BAM for problem identification

Cell log: records the cell procedure information,which, in case of cell abnormality, is exported to

the BAM for problem identification

4.2.11 Software Management


functions for software management. These


Online Patching

The Horizon RAN controller supports online patching

without disrupting ongoing services.

Patches are provided in patch packages. The Horizon

RAN controller supports totally and, in some cases,

partially one-push solution to facilitate the upgrade.

In addition, it supports version rollback, which

guarantees the stability of the system.

Remote Upgrade


upgrade, which can be effected via a remote

terminal. In addition, the Horizon RAN controller

provides automatic upgrade tools, which can reduce

human interference and errors.

Remote Patching


patching; the following operations may be

performed on a remote terminal:

Patching the BAM

The patches include Windows operating system

patches of hot-fix type and BAM software

patches.

Patching the host of the Horizon RAN controller.

The patches are specific for DSPs and .bin

program files

Querying all the patches on the Horizon RAN

controller through MML commands

Online Upgrade of BIOS

The Horizon RAN controller supports online upgrade

of the Basic Input Output System (BIOS). It can

load BootROM software onto boards through MML

commands without disrupting ongoing services.

Online Expansion

You can exp and the capacity of the Horizon RAN

controller by adding RBSs or service processing

boards. After startup, the new board can

automatically load programs, obtain intra-system

connection data and configuration data and enter

the serving state.

Batch Command Processing

The Horizon RAN controller supports the editing

and modification of commands in batches.

Scheduled Task Processing

TThe Horizon RAN controller supports scheduled

tasks. You can preset commands in the system. The

system will automatically run the commands at the

preset time.


25/40


Online Help

The Horizon RAN controller provides the GUI-based

online help.

5 Reliability

5.1 System Reliability

The design of the Horizon RAN controller takes

into account the following system reliability

techniques:

Load control

The system performs load control based on the

CPU usage, traffic over each interface and radio

resource load of the system. Thus, the Horizon

RAN controller can keep on working in case of

CPU overload and resource congestion. In this

way system reliability is enhanced.

Dynamic sharing of resources in the system

The DPUb boards and DSPs work in resource

pool mode, that is, all the DSPs in a sub-rack work

as a resource pool. The MPU in a sub-rack

manages and allocates all the user plane

resources within the sub-rack to fulfill intra-sub-

rack sharing of user plane resources.

In case of overload, the MPU forwards Radio

Resource Control (RRC) connection requests

to other sub-racks, so as to fulfill inter-sub-racksharing of user plane resources and intra- and

inter-sub-rack sharing of control plane resources.

Port trunking

SCUa boards support port trunking. This function

allows data backup in case of link failure, thus

preventing inter-plane switchover and cascading

switchover and improving the reliability of intra-

system communication.

Dual planes for timing signal transmission

The Horizon RAN controller provides the dual

planes for transmission of timing signals betweenthe GCUa/GCGa and SCUa boards.

The active and standby GCUa/GCGa boards are

connected to the active and standby SCUa boards

through the Y-shaped cables. This connection

mode ensures proper working of the timing

signals for the system if a single-point failure

occurs to the GCUa/GCGa, cable, or SCUa.

In addition, with the Y-shaped cable, switchover

between GCUa/GCGa boards does not affect the

SCUa boards.

Transmission port backup

Unchannelized optical ports support MSP 1:1 or

MSP 1+1 redundancy

Channelized optical ports support MSP 1:1 backup

FE or GE ports support port backup and load

sharing between the ports

All these improve the reliability of transmission.

O&M dual planes

To improve the reliability of O&M channels, the

Horizon RAN controller provides the O&M dual

planes, including dual OMUa boards, dual

Ethernet adapters and dual main control boards.

Crystal Aging Compensation technology

The Horizon RAN controller uses Crystal

Aging Compensation technology to compensate

for frequency deviation caused by the aging

of temperature-constant crystal oscillators. This

technology protects the clock precision from the

influence of the aging of the crystal oscillators

and ensures long-term stability and reliability of

the system clock.

Dual 48 V power supplies

The two independent 48 V power supplies

operate at the same time to ensure normal

operations in case either of them fails. The failed

supply can be restored without a power cut. This

improves the reliability and availability of the

power system.

5.2 Hardware Reliability

The Horizon RAN controller features high reliability

designs such as board and port backup and load

sharing. In addition, the Horizon RAN controller

improves the reliability and maintainability byoptimizing the fault detection and isolation

techniques for boards and the whole system.

The hardware reliability design of the Horizon

RAN controller takes into account the following

techniques:


26/40


The system uses the multi-level cascaded and

distributed cluster control mode. Several CPUs

form a cluster processing system. Each module

has distinct functions. The communication

channels between modules are based on a

backup design or anti-suspension/breakdowndesign.

The system uses the redundancy design shown

in Table 5-1, to support hot swap of boards and

backup of important modules. Therefore, the

system has good error tolerance.

Table 5-1: Parts redundancy

Part Redundancy Mode

GCUa/GCGa Board redundancy

DPUb Board redundancy +

port trunking on GE

ports

SPUa Board redundancy

DPUb Board resource pool

AOUa Board redundancy +

MSP 1:1 optical port

redundancy

POUa Board redundancy +

MSP 1:1 or MSP 1+1

optical port redundancy

UOIa Board redundancy +

MSP 1:1 or MSP 1+1

optical port redundancy

FG2a Board redundancy

GOUa Board redundancy

GE port on the FG2a or

GOUa

Port redundancy or load

sharing

FE port on the FG2a Port redundancy or load

sharing

OMUa Board redundancy

When an entity fails, the isolation mechanism

transfers the services to another entity for

processing. After the system finds a faulty board

in the resource pool, it isolates the board. Thenanother board in the resource pool will process

the subsequent services

When a board with a single function fails,

restarting the system might clear the fault

All boards support dual-BIOS. Faults at one BIOS

do not affect startup or operation of the boards

The system uses the non-volatile memory to

store important data

With advanced integrated circuits, the system

features high integration, good technology and

high reliability

All the parts of the system pass the aging test.

The process of hardware assembly is strictly

controlled. These methods ensure the high

stability and reliability for long-term operation.

5.3 Software Reliability

The error tolerance ability of the software

system indicates the software reliability. In other

words, the whole system can keep on working

in case of software failure. This indicates that the

system has self-healing ability. The Horizon RANcontroller derives this ability from the following

aspects:

Regular check of key resources

Usage check is provided for various software

resources in the system. If a resource is

unavailable because of a software error, the

unavailability lasts only a short time. The reason

is that the check mechanism ensures the release

of this resource and the output of logs and

alarms.

Task monitoring

During the running of software, the Horizon RAN

controller monitors the internal errors of all

software and some hardware faults, if any. It then

reports the errors and faults to the OM system.

Load sharing

The FG2a and GOUa boards support inter-board

load sharing between ports.

The DPUb boards work in resource pool mode.

If a DPUb board is faulty, other DPUb boards in

the same sub-rack take over the services carried

on the faulty board.

Data check

The system is able to perform regular or event-

driven check for data consistency and export the

related log records and alarms.


27/40


Dual versions

The boards of the Horizon RAN controller have

active/standby workspaces. The active workspace

stores the current version files and the standby

workspace stores the version files except those in

the active workspace.

Switchover between the active and standby

workspaces can be performed to upgrade or roll

back the RNC version. Therefore, the active and

standby workspaces facilitate the upgrade of and

rollback for the RNC and greatly reduce the time

of service disruption caused by the upgrade.

Data backup

The BAM data and FAM data can be backed up,

so that the reliability and consistency of the data

are ensured.

Storage of operation information

The Horizon RAN controller records the

operations performed and saves the records in

the operation log. The operation log may be

used to identify and clear errors or faults caused

by operations.

Flow control

The Horizon RAN controller automatically controls

the flows on the Iub, Iur and Iu interfaces to avoid

overload caused by heavy traffic.

6 Technical Specifications

6.1 Introduction

This chapter consists of the following sections:

Performance Specifications

Transmission Port Specifications

GPS Feeder Specifications

Reliability Specifications

Structural Specifications

Electrical Specifications

Power Consumption in Typical Configurations

Clock Precision Specifications

Noise and Safety Compliance

Environmental Protection Specifications

International Protection Specifications

Environmental Requirements

6.2 Performance Specifications

Table 6-1 describes the performance specifications


Table 6-1: Performance specifications

Item Specification

Maximum number of

cabinets

Board redundancy

Maximum number of

sub-racks

Board redundancy +

port trunking on GE

ports

BHCA Board redundancy

Maximum voice traffic Board resource pool

PS throughput (UL +

DL)

3,264 Mbps

Maximum number of

Node Bs

1,700

Maximum number of

cells

5,100


28/40


6.3 Transmission Port Specifications

Table 6-2 describes the transmission port

specifications of the Horizon RAN controller.

Table 6-2: Transmission port specifications

Transmission Type Standard Board or

Port Type

Connector

Type

Remarks

E1/T1 ITU-T G.703/G.704 AEUa DB44 The AEUa provides 32 E1s/T1s for

ATM transport on the Iub interface.

PEUa DB44 The PEUa provides 32 E1s/T1s for IP

transport on the Iub interface.

Channelized STM-

1/OC-3

ITU-T G.957

ITU-T I.432.1

ITU-T I.432.2

AOUa LC/PC The AOUa provides 2 channelized

STM-1/OC-3 optical ports for ATM


POUa LC/PC The POUa provides 2 channelized

STM-1/OC-3 optical ports for IP


Unchannelized

STM-1/OC-3c

ITU-T G.957

ITU-T I.432.1

ITU-T I.432.2

UOIa LC/PC The UOIa provides 4 unchannelized

STM-1/OC-3c optical ports for ATM

transport on the Iub, Iur and Iu

interfaces.

The UOIa provides 4 unchannelized

STM-1/OC-3c optical ports for IP

transport on the Iub, Iur and Iu

interfaces.

FE IEEE 802.3 FE port on

the FG2a

RJ45 The FG2a provides 8 FE ports for

IP transport on the Iub, Iur and Iu

interfaces.

GE IEEE 802.3 GE

electrical

port on the

FG2a

RJ45 The FG2a provides 2 GE electrical

ports for IP transport on the Iub, Iur

and Iu interfaces.

GE optical

port on the

GOUa

LC/PC The GOUa provides 2 GE optical ports

for IP transport on the Iub, Iur and Iu

interfaces.

The maximum transmission distances of the

different port types are as follows:

E1/T1 port: 500m

STM-1 port: 15km

FE port: 100m

GE electrical port on the FG2a: 100m

GE optical port on the GOUa: 10km


29/40


6.4 GPS Feeder Specifications

The Horizon RAN controller provides GPS

feeders that meet the following specifications:

Length of the GPS feeder: 100m

100 m < length of the GPS feeder: 300m

300 m < length of the GPS feeder: 500m

6.5 Reliability Specifications

Table 6-3 describes the reliability specifications of


Table 6-3: Reliability specifications

Item Specification

System inherent

availability

f99.999%

Mean Time Between

Failures (MTBF)

f347,700 h

System restarting time ~ 10 min

Mean Time To Repair

(MTTR)

~ 1 h

6.6 Structural Specifications

Table 6-4 describes the structural specifications of


Table 6-4: Structural specifications

Item Specification

Cabinet standard The structural design

conforms to the

IEC60297 standard and

IEEE standard.

Dimensions of a cabinet 2,200 mm (height) x 600

mm (width) x 800 mm

(depth)

Height of the available

space in a cabinet

N68E-22 cabinet: 46 U

Weight of a single

cabinet

N68E-22 cabinet: ~350

kg

Load bearing capacity of

the equipment room

f450 kg/m2

6.7 Electrical Specifications

Table 6-5 describes the electrical specifications of


Table 6-5: Electrical specifications

Item Specification

Power supply 48 V DC power

Input voltage range:

40 V to 57 V

Electromagnetic

Compatibility (EMC)

Meets the requirements

in ETSI EN300 386 and

Council directive 89/336/

EEC

RSS power

consumption

~ 1,530 W

RBS powerconsumption ~ 1,540 W

Power consumption

of the RSR in full

configuration

~ 4,650 W

Power consumption

of the RBR in full

configuration

~ 4,660 W


30/40


6.8 Power Consumption in TypicalConfigurations

Table 6-6 describes the specifications for power

consumption of the Horizon RAN controller in typical

configurations.

Table 6-6: Power consumption of the Horizon RAN

controller in typical configurations. see below.

Number of

Sub-racks

Iu/Iur/Iub

ATM Optical

Transport

with Ports in

Redundancy

Iu/Iur/Iub GE

Optical Transport

with Ports Not in

Redundancy

Voice Traffic

(Erlang)

(UL + DL) PS

Throughput

(Mbps)

Number of

Cells

1 RSS ~ 1,570 W ~1,260 W 6,000 384 600

1 RSS + 1 RBS ~ 3,110 W ~2,400 W 15,000 960 1,500

1 RSS + 2 RBSs ~ 4,650 W ~ 3,540 W 24,000 1,536 2,400

1 RSS + 3 RBSs ~ 6,230 W ~ 4,720 W 33,000 2,112 3,300

1 RSS + 4 RBSs ~ 7,770 W ~ 5,860 W 42,000 2,688 4,200

1 RSS + 5 RBSs ~ 9,310 W ~ 7,000 W 51,000 3,264 5,100

6.9 Clock Precision Specifications

The precision of the clock for the Horizon RAN controller

meets the associated requirements of the stratum 3 clock.

6.10 Noise and Safety Compliance

Table 6-7 describes the noise and safety compliance


Table 6-7: Noise and safety compliance

Item Specification

Noise < 72 dB; fulfilling the requirements

in EUROPEAN ETS 300 753

Safety Fulfilling the requirements in:

IEC 60950

EN 60950

UL60950

IEC 60825-1

IEC 60825-2

AS/NZS 60950-1

GB4943-2001

6.11 Environmental ProtectionSpecifications

The environmental protection specifications of

the Horizon RAN controller are as follows:

RoHS: Restriction of the Use of Certain

Hazardous Substances in Electrical and

Electronic Equipment

WEEE: The EU Directive on Waste of Electrical

and Electronic Equipment

94/62/EC Packaging and packaging waste.

6.12 International ProtectionSpecifications

The Horizon RAN controller is rated to IP50

standard.

6.13 Environmental Requirements

The storage, transportation and working

environments of the Horizon RAN controller

conform to the following standards:

GB2423.1-1989

GB2423.2-1989

GB2423.4-1993

GB2423.22-1987

GB/T13543

ETS 300 019

NEBS GR-63-core


31/40


6.13.1 Storage Environment

The Horizon RAN controller has storage

requirements for climate, waterproofing conditions,

biological environment, air purity and mechanical

stress.

Climatic Requirements

Table 6-8 describes the climatic requirements for

storing the Horizon RAN controller.

Table 6-8: Climatic requirements for storing the Horizon

RAN controller

Item Specification

Temperature 40C to +70C

Temperature change rate ~ 1C/min

Relative humidity 10% to 100% RH

Altitude ~ 5,000 m

Air pressure 70 kPa to 106 kPa

Solar radiation ~ 1,120 W/m

Thermal radiation ~600 W/m

Wind speed ~ 30 m/s

Waterproofing Requirements

The waterproofing requirements for storing the

Horizon RAN controller are as follows:

The equipment is usually stored in a room

There is no water on the floor or any water

entering the package

In the equipment room, there is no water

that may damage the equipment, such as water

from automatic fire protection devices or the

air conditioner

If the equipment has to be placed outdoors,

ensure that:

The package is intact

Waterproofing measures are taken to prevent

rainwater from entering the package

There is no water on the ground or any water

entering the package

The package is not exposed to direct sunlight

Biological Requirements

The biological requirements for storing the


No fungus or mildew may grow in the equipment

room or near the equipment

The location is free from rodents

Air Purity Requirements

The air purity requirements for storing the


The air is free from explosive, conductive,

magnetically conductive, or corrosive dust.

The density of physically active materials

must meet the requirements listed in Table 6-9.

The density of chemically active materials must

meet the requirements listed in Table 6-10.

Table 6-9: Storage requirements for physically active

materials

Physically Active Material Unit Density

Suspended dust mg/m 5.00

Falling dust mg/mh 20.0

Sand mg/m 300

Note: Suspended dust: diameter 75 um Falling dust: 75 um diameter 150 um Sand: 150 um diameter 1,000 um

Table 6-10: Storage requirements for physically

active materials

Chemically Active Material Unit Density

SO mg/m 0.30

HS mg/m 0.10

NO mg/m 0.50

NH mg/m 1.00

Cl mg/m 0.10

HCl mg/m 0.10

HF mg/m 0.01

O mg/m 0.05


32/40


Item Sub-item Specification

Sinusoidal vibration

Offset 7.0 mm

Accelerated speed 20.0 m/s

Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz

Unsteady impactImpact response spectrum II 250 m/s

Static payload 5 kPa

Climatic Requirements

Table 6-12 describes the climatic requirements for

transporting the Horizon RAN controller.

Table 6-12: Climatic requirements for transporting the

Horizon RAN controller

Item Specification

Temperature 40C to +70C

Temperature change rate ~ 1C/min

Relative humidity 10% to 100% RH

Altitude ~ 5,000 m

Air pressure 70 kPa to 106 kPa

Solar radiation ~ 1,120 W/m

Thermal radiation ~600 W/m

Wind speed ~ 30 m/s

Waterproofing Requirements

The waterproofing requirements for transporting

the Horizon RAN controller are as follows:

The package is intact

Waterproofing measures are taken to prevent

rainwater from entering the package

The inside of the vehicle is completely dry

Biological Requirements

The biological requirements for storing the


No fungus or mildew may grow in the equipment

room or near the equipment

The location is free from rodents

Air Purity Requirements

The air purity requirements for storing the


The air is free from explosive, conductive,

magnetically conductive, or corrosive dust.

The density of physically active materials

must meet the requirements listed in Table 6-13.

The density of chemically active materials must

meet the requirements listed in Table 6-14.

Table 6-13: Transportation requirements for physically

active materials

Physically Active

Material

Unit Density

Suspended dust mg/m No requirement

Falling dust mg/mh 3.0

Sand mg/m 100

Note: Suspended dust: diameter 75 um Falling dust: 75 um diameter 150 um Sand: 150 um diameter 1,000 um

Note: Impact response spectrum: maximum acceleration response curve generated by the equipment under specified impact excitation.

Impact response spectrum II means that the duration of semi-sine impact response spectrum is 6 ms. Static payload: capability of the equipment in package to bear the pressure from the top in normal pile-up method

Mechanical Stress RequirementsTable 6-11 describes the mechanical stress requirements for storing the Horizon RAN controller.

Table 6-11: Mechanical stress requirements for storing the Horizon RAN controller


33/40


Table 6-14: Transportation requirements for chemically

active materials

Chemically Active Material Unit Density

SO mg/m 0.30

HS mg/m 0.10

NO mg/m 0.50

NH mg/m 1.00

Cl mg/m 0.10

HCl mg/m 0.10

HF mg/m 0.01

O mg/m 0.05

Item Sub-item Specification

Sinusoidal vibration

Offset 7.5 mm

Accelerated speed 20.0 m/s 40.0 m/s

Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz 200 Hz to 500 Hz

Random vibrationSpectrum density of accelerated speed 10 m/s 3 m/s 1 m/s

Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz 200 Hz to 500 Hz

Unsteady impactImpact response spectrum II 300 m/s

Static payload 10 kPa

Mechanical Stress Requirements

Table 6-15 describes the mechanical stress requirements for transporting the Horizon RAN controller.

Table 6-15: Mechan

ran controller tech brief

Documents