huawei umts ran10 0 dimensioning rules v1.2

2008-08-29 All rights reserved i

Huawei UMTS RAN10.0 Dimensioning Rules

Huawei Technologies Co., Ltd.

Aug, 2008

2008-08-29 All rights reserved iii

Table of Contents

2.1 Node B V100R010 Macro Node B BTS3812E/BTS3812AE.................................................................................6 2.1.2 Transport Module Configuration ................................................................................................................9 2.1.3 Baseband Subsystem Configuration ..........................................................................................................11 2.1.4 RF Subsystem Configuration .....................................................................................................................12 2.1.5 Control Subsystem Configuration .............................................................................................................13 2.1.6 BTS3812E/BTS3812AE Typical Configurations .......................................................................................13 2.1.7 BTS3812E/BTS3812AE Capacity ..............................................................................................................16

2.2 Distributed Node B DBS3800 System Description .............................................................................................17 2.2.2 Baseband Module Configuration ...............................................................................................................18 2.2.3 RRU Configurations...................................................................................................................................19 2.2.4 DBS3800 Typical Configurations...............................................................................................................19 2.2.5 DBS3800 Capacity......................................................................................................................................21

2.3 Node B V200R010...............................................................................................................................................22 2.3.1 Baseband Module Configuration ...............................................................................................................25 2.3.2 RF Module Configurations ........................................................................................................................28 2.3.3 3900 Series Node B typical configuration ..................................................................................................29

2.4 UMTS Capacity Dimensioning Procedure.........................................................................................................37 2.4.1 Introduction ................................................................................................................................................37 2.4.2 CS Capacity Dimensioning Principle .......................................................................................................38 2.4.3 PS Capacity Dimensioning Principle........................................................................................................41 2.4.4 HSDPA Capacity Dimensioning ...............................................................................................................41 2.4.5 HSUPA Capacity Dimensioning ...............................................................................................................42 2.4.6 MBMS Capacity Dimensioning.................................................................................................................43 2.4.7 Mixed Services Capacity Dimensioning...................................................................................................45

2.5 UMTS CE Dimensioning Procedure ..................................................................................................................45 2.5.1 Introduction ................................................................................................................................................45 2.5.2 CE Dimensioning for CS Service .............................................................................................................47 2.5.3 CE Dimensioning for PS service ..............................................................................................................49 2.5.4 CE Dimensioning for HSDPA ...................................................................................................................49 2.5.5 CE Dimensioning for HSUPA ...................................................................................................................51 2.5.6 CE Dimensioning for MBMS.....................................................................................................................52 2.5.7 Total Number of Channel Elements.........................................................................................................53

2.6 UMTS Iub Dimensioning Procedure..................................................................................................................54 2.6.1 Introduction ................................................................................................................................................54 2.6.2 Iub Bandwidth Dimensioning for Traffic ...................................................................................................55 2.6.2.1 CS Peak Iub Bandwidth .........................................................................................................................56 2.6.2.2 CS Average Iub Bandwidth.................................................................................................................58 2.6.2.3 PS Iub Bandwidth.................................................................................................................................58 2.6.2.4 HSPA Iub Bandwidth ...........................................................................................................................59 2.6.2.5 MBMS Iub Bandwidth ..........................................................................................................................60 2.6.3 Iub Bandwidth Dimensioning for Others ..................................................................................................61 2.6.3.1 Iub Bandwidth for Common Channel ...............................................................................................61 2.6.3.2 Iub Bandwidth for Signaling...............................................................................................................61 2.6.3.3 Iub Bandwidth for O&M.......................................................................................................................61

2008-08-29 All rights reserved iv

3.1 Configurations standards of BSC6800 ...............................................................................................................61

3.2 Configurations standards of BSC6810 ...............................................................................................................66

3.3 Function Upgrade...............................................................................................................................................71 3.3.1 HSDPA upgrade ........................................................................................................................................71 3.3.2 HSUPA upgrade ........................................................................................................................................71 3.3.3 IP Upgrade .................................................................................................................................................71 3.3.4 Other Functional Upgrades.......................................................................................................................72

3.4 RNC interface Dimensioning..............................................................................................................................73 3.4.1 Iub Dimensioning.......................................................................................................................................73 3.4.2 Iur Interface Dimensioning (RNC RNC)..............................................................................................73 3.4.3 Iu-CS Interface Dimensioning (RNC MGW) .......................................................................................73 3.4.4 Iu-PS Interface Dimensioning (RNC SGSN) ......................................................................................76

4.1 Complete architecture of the O&M solution......................................................................................................81 4.1.1 Physical architecture .................................................................................................................................81

4.2 O&M solution dimensioning rules .....................................................................................................................82 4.2.1 System capacity of M2000........................................................................................................................82 4.2.2 Bandwidth ..................................................................................................................................................83 4.2.3 Performance Data Storage Capacity .......................................................................................................83 4.2.4 Performance Data Processing Capacity..................................................................................................84 4.2.5 Alarm Data Storage Capacity ...................................................................................................................84 4.2.6 Alarm Processing Capacity.......................................................................................................................85 4.2.7 Number of Clients Simultaneously Started on the Server......................................................................86

4.3 O&M hardware and software configuration .....................................................................................................86 4.3.1 Typical M2000 Server Configuration........................................................................................................86 4.3.2 Common Networking Equipment..............................................................................................................87 4.3.3 Typical M2000 Client Configuration .........................................................................................................88

2008-08-29 All rights reserved v

Revision Record

Date Revision Description Author

2008-03-03 1.0 Initial release Tang wenqing, Zhang hua, Li hong, Hu guang

2008-03-21 1.1 Add contents of V2 NodeB Tang wenqing

2008-08-21 1.2 Update NodeB borads and M2000 servers specification Zhang jianhua, Guanwei

Huawei UMTS RAN10.0 Dimensioning Rules Confidential

2008-8-29 Commercial in Confidence , Total 88

1 Introduction

This document is to introduce the Dimensioning rules for Huawei¡s RAN product

including Node B (Macro and DNBS) and RNC. It is based on release RAN10.0

including the introduction of capacity of baseband board and transmission of Node B,

the traffic processing capability of RNC and interface capability (Iub, Iur, Iu-CS and

Iu-PS).

2 Node B

2.1 Node B V100R010 Macro Node B BTS3812E/BTS3812AE

The BTS3812E/BTS3812AE has the following subsystems:

Transport Subsystem Baseband Subsystem RF Subsystem Control Subsystem Antenna Subsystem Heat Dissipation

PA: Power Amplifier

RF subsystem: radio frequency subsystem

RNC: Radio Network Controller

RX: Receive channel

TMA: Tower Mounted Amplifier



TX: Transmit channel

Figure 2-1 Logical structure of the BTS3812E/BTS3812AE

In RAN10.0, a new RF module WRFU can be supported. In Logical structure, WRFU

includes MTRU and MAFU function.

Figure below shows the BTS3812E in full configuration.

(1) MAFU subrack (2) MTRU subrack (3) Fan subrack



(4) Busbar (5) Baseband subrack

Figure 2-2 BTS3812E (-48V DC) in full configuration

Figure below shows the BTS3812AE in full configuration.

(1) MAFU subrack

(2) MTRU subrack

(3) Fan subrack

(4) Power busbar

(5) Baseband subrack

(6) Power subrack

(7) Transmission device subrack

(8) Surge protector subrack (for transmission devices)

(9) AC power distribution subrack

(10) Surge protector and filter subrack

(11) Built-in battery cabin

Figure 2-3 BTS3812AE in full configuration

Table below lists the major boards and modules in the BTS3812E/BTS3812AE.

Abbreviation Full Spelling

HBBI Node BHSDPA Supported Baseband Processing and Interface Unit

EBBI Enhanced Baseband Processing and Interface Unit

EBOI Enhanced Node BHSDPA Supported Baseband Processing and Optical



Abbreviation Full Spelling

Interface Unit

HDLP Node B HSDPA Supported Downlink Processing Unit

HULP Node B HSUPA Supported Uplink Processing Unit

EULP Enhanced Uplink Processing Unit

MAFU Node B Multi-Carrier Antenna Filter Unit

MTRU Node B Multi-Carrier Transceiver Unit

WRFU WCDMA RF and Filter Unit

NCCU Node B Cable Connected Unit

NFAN Node B Fan Box

NMON Node B Monitor Unit

NMPT Node B Main Processing & Timing Unit

NUTI Node B Universal Transmission Interface Unit

2.1.2 Transport Module Configuration

The Transport Module connects to the RNC to exchange information on the Iub

interface.

One BTS3812E/BTS3812AE provides up to 4 slots for Transport Module NUTI.

The NUTI in the subsystem provides E1/T1 and FE ports. Different sub-boards can be

added to support a larger number of E1/T1 ports, FE ports and also support 2

unchannelized STM-1 ports or 1 channelized STM-1. The NUTI performs ATM and IP

switching.

Board type Interface Number Rate Standard Remark

T1 8 pairs 1.5Mbit/s

ETS300 420

ITU G.703/704

ANSI-G.703/704

E1 8 pairs 2Mbit/s

ETS300 420

ITU G.703/704

ANSI-G.703/704

E1 and

T1

share

the

same

ports.

NUTI

100 M Fast

Ethernet 2 100Mbit/s IEEE 802.3





ETS300 420

ITU G.703/704

ANSI-G.703/704

E1 16 pairs 2Mbit/s

ETS300 420

ITU G.703/704

ANSI-G.703/704

E1 and

T1

share

the

same

ports.

NUTI with E1

sub board

100 M Fast



ETS300 420

ITU G.703/704

ANSI-G.703/704

E1 8 pairs 2 Mbit/s

ETS300 420

ITU G.703/704

ANSI-G.703/704

E1 and

T1

share

the

same

ports.

100 M Fast


NUTI with

un-channelized

STM-1 sub

board

un-channelized

STM-1/ OC3 2 155Mbit/s

ANSI

T1.105-1995

ITU I.432.2

G.703

ITU G.957

ANSI T1.105

NUTI with

channelized

STM-1 sub


ETS300 420

ITU G.703/704

ANSI-G.703/704

E1 and

T1

share




E1 8 pairs 2Mbit/s

ETS300 420

ITU G.703/704

ANSI-G.703/704

the

same

ports.

100 M Fast


board

channelizd

STM-1/OC3 1 155Mbit/s

ANSI

T1.105-1995

ITU I.432.2

G.703

ITU G.957

ANSI T1.105

2.1.3 Baseband Subsystem Configuration

The baseband subsystem consists of the EBBI, HBBI, EULP, HULP, HDLP and EBOI.

On physical layer, the baseband subsystem processes uplink and downlink signals and

handles closed loops. The CE license in base band board (EBBI, HBBI, HDLP, HULP,

EBOI) is controlled at the step of 16 CE.

One BTS3812E/BTS3812AE provides up to 2 slots for HBBI, EBBI or EBOI. HBBI, EBBI

and EBOI share the 2 slots.

The EBBI has the following functions:

Forwarding and controlling baseband signals and RF signals Processing uplink and downlink baseband signals Supporting the HSDPA, HSUPA Phase II and R99 Provide electrical CPRI ports connected with MTRU 1 EBBI supports 6 cells, 384CE in uplink and 384CE in downlink.

The HBBI has the following functions:

Forwarding and controlling baseband signals and RF signals Processing uplink and downlink baseband signals Supporting the HSDPA, HSUPA Phase I and R99 Provide electrical CPRI ports connected with MTRU 1 HBBI supports 3 cells, 128CE in uplink and 256CE in downlink.



The EBOI is required when the BTS3812E/BTS3812AE is connected to RRUs. The

board has the following functions:

Forwarding and controlling baseband signals and RF signals Processing uplink and downlink baseband signals Supporting the HSDPA, HSUPA phase II and R99 1 EBOI Provide 3 optical CPRI ports connected with RRU 1 EBOI supports 6 cells, 384CE in uplink and 384CE in downlink.

One BTS3812E/BTS3812AE provides up to 6 slots for HULP or EULP. HULP and EULP

share the 6 slots.

The HULP has the following functions:

Processing uplink baseband signals Supporting the HSDPA, HSUPA Phase I and R99 1 HULP supports 3 cells and 128 CE in uplink.

The EULP has the following functions:

Processing uplink baseband signals Supporting the HSDPA, HSUPA Phase1, HSUPA Phase2 and R99 1 EULP supports 6 cells and 384 CE in uplink.

One BTS3812E/BTS3812AE provides up to 2 slots for HDLP.

The HDLP has the following functions:

Processing downlink baseband signals Supporting the HSDPA and R99 1 HDLP supports 6 cells and 512 CE in downlink.

2.1.4 RF Subsystem Configuration

The RF subsystem consists of MTRUs and MAFUs. In RAN10.0, Huawei provides

WRFU integrating MTRU and MAFU function into one unit.

One BTS3812E/BTS3812AE provides up to 6 slots for MTRU or WRFU. MTRU and

WRFU share the 6 slots.

One BTS3812E/BTS3812AE provides up to 6 slots for MAFU.

The MTRU supports RF signal processing for 2 receiving channel and 1 transmitting

channel. One module supports 1 sector and 2 carriers, 40W output power, the output

power is measured at the NodeB RF module antenna ports.

Each MAFU consists of one duplex filter, one receiving filter, and two Low Noise

Amplifiers (LNAs). It provides one transmitting channel and two receiving channels. It

supports 1 sector.



The WRFU supports RF signal processing for 2 receiving channel and 1 transmitting

channel, including duplex filter, one receiving filter, and Low Noise Amplifiers (LNAs).

One module supports 1 sector and 4 carriers, 80W output power, the output power is

measured at the NodeB RF module antenna ports.

2.1.5 Control Subsystem Configuration

The control subsystem consists of the NMPT and the NMON.

The NMPT is the core of the BTS3812E/BTS3812AE. It controls the entire

BTS3812E/BTS3812AE, processes various signals, and provides the system clock.

One BTS3812E/BTS3812AE provides up to 2 slots for NMPT. One NMPT is required,

two NMPT can support system backup.

The NMON has the following functions:

Providing Boolean signal ports for external alarms and output control Modulating and demodulating AISG signals Controlling the RET antenna

The NMON is optional configuration.

2.1.6 BTS3812E/BTS3812AE Typical Configurations

A single BTS3812E/BTS3812AE can support a maximum of 12 cells. Table below

shows the typical configurations of a single BTS3812E/BTS3812AE.

Typical configurations of a single BTS3812E/BTS3812AE

Configuration Transmit Diversity

1 x 1 Optional

3 x 1 Optional

3 x 2 Optional

3 x 3 Optional

3 x 4 Optional

6 x 1 Optional

6 x 2 Optional

Note:

N x M = sector x carrier

3 x 1 indicates that each of the three sectors has one carrier.

The BTS3812E/BTS3812AE has the following configuration features

The BTS3812E/BTS3812AE supports the configuration of 1 to 6 sectors. Each sector supports a maximum of four carriers. The BTS3812E/BTS3812AE can be connected to RRUs.



A single BTS3812E/BTS3812AE can support 3 x 4 (sector x carrier) or 6 x 2 without transmit diversity. You may select one of the configurations, depending on the requirement of capacity.

The BTS3812E/BTS3812AE supports a smooth capacity expansion from 1 x 1 to 6 x 2 or 3 x 4.

One MTRU supports 2 carriers and 40 W output power at the NodeB RF module antenna port. No additional RF modules are required when 1-carrier configuration is upgraded to 2-carrier configuration.

For some RAN sharing scenario, one NodeB shall support more carriers, for example3 x 6 (sector x carrier). The WRFU should be configured. One WRFU supports 4 carriers and 80 W output power at the NodeB RF module antenna port. No additional RF modules are required when 1-carrier configuration is upgraded to 4-carrier configuration. With 6 WRFU, one BTS3812E/BTS3812AE can support 3 x 8 (sector x carrier) configuration.

The capacity of the modular BTS3812E/BTS3812AE can be expanded simply through additional modules or license expansion. In the initial phase of network deployment, some small capacity configurations such as Omni 1 configuration or 3 x 1 can be used. With the capacity requirement increasing, you can smoothly upgrade the system to large-capacity configurations such as 3 x 2 and 3 x 4.

Any combination of the two frequency bands (850 MHz, 900 MHz, 1800 MHz, 1900 MHz, and 2100 MHz) can be supported in one Node B. The Node B with shared baseband boards only requires RF modules at different bands.

The Node B configuration with supporting HSUPA phase 1 is listed below (with MTRU):

configur

ation

MTRU MAFU WRFU NMPT NUTI NMON HBBI HULP HDLP

1 1 1 NA 1 1 1 1 NA NA

1+1 2 2 NA 1 1 1 1 NA NA

2+2 2 2 NA 1 1 1 2 NA NA

1+1+1 3 3 NA 1 1 1 1 NA NA

2+2+2 3 3 NA 1 1 1 2 NA NA

3+3+3 6 6 NA 1 1 1 2 1 1

4+4+4 6 6 NA 1 1 1 2 2 1

The Node B configuration with supporting HSUPA phase 2 is listed below (with MTRU):

configur MTRU MAFU WRFU NMPT NUTI NMON EBBI EULP HDL



ation P

1 1 1 NA 1 1 1 1 NA NA

1+1 2 2 NA 1 1 1 1 NA NA

2+2 2 2 NA 1 1 1 1 NA NA

1+1+1 3 3 NA 1 1 1 1 NA NA

2+2+2 3 3 NA 1 1 1 1 NA NA

3+3+3 6 6 NA 1 1 1 2 NA NA

4+4+4 6 6 NA 1 1 1 2 1 1

The Node B configuration with supporting HSUPA phase 1 is listed below (with WRFU):

configur

ation

MTRU MAFU WRFU NMPT NUTI NMON HBBI HULP HDLP

1 0 0 1 1 1 1 1 NA NA

1+1 0 0 2 1 1 1 1 NA NA

2+2 0 0 2 1 1 1 2 NA NA

1+1+1 0 0 3 1 1 1 1 NA NA

2+2+2 0 0 3 1 1 1 2 NA NA

3+3+3 0 0 3 1 1 1 2 1 1

4+4+4 0 0 3 1 1 1 2 2 1

6+6+6 0 0 6 1 1 1 2 4 2

The Node B configuration with supporting HSUPA phase 2 is listed below (with WRFU):

configur

ation

MTRU MAFU WRFU NMPT NUTI NMON EBBI EULP HDL

P

1 0 0 1 1 1 1 1 NA NA

1+1 0 0 2 1 1 1 1 NA NA

2+2 0 0 2 1 1 1 1 NA NA

1+1+1 0 0 3 1 1 1 1 NA NA

2+2+2 0 0 3 1 1 1 1 NA NA

3+3+3 0 0 3 1 1 1 2 NA NA



4+4+4 0 0 3 1 1 1 2 1 1

6+6+6 0 0 6 1 1 1 2 1 1

The diagram for connection of S111, S222 and S333 configurations are shown below.

Figure 2-4 The S111, S222 and S333 configurations

2.1.7 BTS3812E/BTS3812AE Capacity

The number of channel elements can be set, depending on the number of UEs and the

types of services. Table below defines the maximum baseband capability of the

baseband subrack in the BTS3812E/BTS3812AE in 3 x 4 configurations.

The Maximum Capacity of the BTS3812E/BTS3812AE depends on the baseband card

configuration. With 2 EBBI boards, 6 HULP and 2 HDLP configuration, the Capacity listed

in the following table.

Capacity Type Quantity of CEs

Uplink capacity 1536

Downlink capacity 1792

HSDPA capacity 360 HS-PDSCH codes

HSUPA PH1 1536

HSUPA PH2 1536

Dual

Polarization

1 Carrier 2 Carriers 3 Carriers

PA

TRX

Rx: Rx: f1

PA

TRX

Rx: Rx: f1,f2

Tx: f1,f2

PA

TRX

PA

TRX

Rx: f1,f2,f3 Rx: f1,f2,f3

MAFU

MTRU

Splitter

Duplexer

Dual

Polarization

Splitter

Duplexer

Splitter

Duplexer

Splitter

Duplexer



2.2 Distributed Node B DBS3800 System Description

The DBS3800 basically comprise the following three units:

The indoor baseband processing unit BBU3806 The outdoor baseband processing unit BBU3806C The outdoor Remote Radio Unit (RRU)

The BBU3806 (indoor unit) and the BBU3806C (outdoor unit) have a similar logical

structure. In RAN10.0, EBBC and EBBM are introduced as enhanced base band card

for BBU3806 and BBU3806C. Using BBU3806+EBBC or BBU3806C+EBBM can realize

the larger capacity of base band.

Figure below shows the functional modules in the BBU.

Figure 2-5 Functional modules in the BBU

The BBU consists of the following functional parts:

Transport subsystem Baseband subsystem Control subsystem Interface modules

There are 2 kinds of RRU for DBS3800:

RRU3801C (or RRU3801E): 40W output power on the top of cabinet, 2 carriers

RRU3804: 60W output power on the top of cabinet, 4 carriers

RRU3801C and RRU3804 have the same functional modules. Figure below shows the

functional modules in the RRU.



Figure 2-6 Functional modules in the RRU

The functional modules are as follows:

Interface module. The interface module receives downlink baseband data from the

BBU, transmits uplink baseband data to the BBU, and forwards data from the

cascaded RRUs.

MTRX. The MTRX has two RX channels and one TX channel for RF signals. The

RX channel down-converts the receive signals into Intermediate Frequency (IF)

signals and performs amplification, analog-to-digital (A/D) conversion, digital

down-conversion, matched filtering, and Digital Automatic Gain Control (DAGC).

The TX channel performs shape filtering of downlink spreading signals,

digital-to-analog (D/A) conversion, and up-conversion of RF signals into transmit

band signals.

PA. The Power Amplifier (PA) implements the DPD and E-Doherty technologies to

amplify low-power RF signals from the MTRX.

Duplexer. The duplexer multiplexes receive signals and transmit signals, which

enables the receive signals and transmit signals to share the same antenna path.

The duplexer also filters receive signals and transmit signals.

LNA. The LNA amplifies the signals received from antennas.

2.2.2 Baseband Module Configuration

The BBU33806 is an indoor base band unit. The maximum configuration is 2 BBU3806

in one Node B. The BBU3806 consists of the boards for the baseband, control, switching

and Iub transmission interface functionalities.

The BBU3806, powered with ¨ 48 V/ 24V DC, provides environmental protection and

cooling functions.



One BBU3806 provides 2 FE interface and 8 E1/T1 interface for the Iub connections.

One BBU3806 provides 3 optical CPRI interface for RRU connections.

One BBU3806 supports 3 cells, 192CE in uplink and 256CE in downlink. One BBU also

provides 1 slot for extension card EBBC. One BBU3806 with EBBC supports 6 cells,

384CE in uplink and 512CE in downlink.

2.2.3 RRU Configurations

The RRU is divided into two types according to output power and carries:

40 W RRU3801C (or RRU3801E), 40W output power on the antennal port, 2

carriers

60 W RRU3804, 60W output power on the antennal port, 4 carriers

One 40W RRU can support 2 continuous carriers in 1 sector. DBS3900 can support

smooth capacity expansion from 1 x 1 to 1 x 2 without adding RF module.

Two 40W RRUs in parallel connection within one sector can support the 1 x 4

configuration.

One 60W RRU can support 4 continuous carriers in 1 sector. With 20W per carrier

configuration, it can support 3 non continuous carriers (for example 1101, 1011),

which is applicable to RAN sharing with 2 operators has non continuous carriers.


configuration.

Two RRUs in parallel connection within one sector can support transmit diversity and

4-way receive diversity.

2.2.4 DBS3800 Typical Configurations

Table below lists some recommended configurations of the DBS3800.

Recommended configurations of the DBS3800 with RRU3801C and supporting HSUPA

phase1.

Qty. of BBUs

Qty. of EBBC/EBB

M

Qty. of RRU3801C Configuration

No TX

Diversity

TX Diversity

1 x 1 1 0 1 2

1 x 2 1 0 1 2

2 x 1 1 0 2 4



2 x 2 2 0 2 4

3 x 1 1 0 3 6

3 x 2 2 0 3 6

3 x 3 2 1 6 Not supported



Recommended configurations of the DBS3800 with RRU3804 and supporting HSUPA

phase1.

Qty. of BBUs

Qty. of EBBC/EBB

M

Qty. of RRU3804s Configuration

No TX

Diversity

TX

Diversity

1 x 1 1 0 1 2

1 x 2 1 0 1 2

2 x 1 1 0 2 4

2 x 2 2 0 2 4

3 x 1 1 0 3 6

3 x 2 2 0 3 6

3 x 3 2 1 3 6

6 x 2 2 2 6 Not

supported

Recommended configurations of the DBS3800 with RRU3801C and supporting HSUPA

phase2.

Qty. of BBUs

Qty. of EBBC/EBB

M

Qty. of RRU3801C Configuration

No TX

Diversity

TX Diversity

1 x 1 1 1 1 2

1 x 2 1 1 1 2

2 x 1 1 1 2 4

2 x 2 1 1 2 4

3 x 1 1 1 3 6

3 x 2 1 1 3 6




Recommended configurations of the DBS3800 with RRU3804 and supporting HSUPA



phase2.

Qty. of BBUs

Qty. of EBBC/EBB

M

Qty. of RRU3804s Configuration

No TX

Diversity

TX

Diversity

1 x 1 1 1 1 2

1 x 2 1 1 1 2

2 x 1 1 1 2 4

2 x 2 1 1 2 4

3 x 1 1 1 3 6

3 x 2 1 1 3 6

3 x 3 2 1 3 6

6 x 2 2 2 6 Not

supported

2.2.5 DBS3800 Capacity

Table below list the capacities of the BBU3806, BBU3806C, and RRU3801C.

Capacity of the BBU3806 without HSUPA function

Configuration Uplink R99 CE Downlink

R99 CE

HSDPA Capacity

1 BBU 192 256 45 HS-PDSCH codes

2 BBUs 384 512 90 HS-PDSCH codes

2 BBUs with EBBC 768 1024 180 HS-PDSCH codes

Capacity of the BBU3806 with HSUPA function

Configuration Uplink R99/HSUPA CE Downlink R99 CE HSDPA Capacity


2 BBUs 256 512 90 HS-PDSCH codes

2 BBUs with

EBBC

640 including 384CE

support HSUPA ph2

1024 180 HS-PDSCH codes

Capacity of the BBU3806C without HSUPA function

Configuration Uplink R99 CE Downlink R99 CE HSDPA Capacity



Configuration Uplink R99 CE Downlink R99 CE HSDPA Capacity


1 BBU with EBBM 384 512 90 HS-PDSCH codes

Capacity of the BBU3806C with HSUPA function

Configuration Uplink R99/HSUPA CE

Downlink R99 CE

HSDPA Capacity


1 BBU with EBBM

320 including 192CE support HSUPA ph2

512 90 HS-PDSCH codes

Capacity of the RRU3801C

Item Value

Max. number of sectors 1

Max. number of carriers 2

Capacity of the RRU3804

Item Value

Max. number of sectors 1

Max. number of carriers 4

2.3 Node B V200R010

The 3900 series Node B basically comprise the following three units:

The indoor baseband processing unit BBU3900

The indoor radio frequency unit WRFU

The outdoor Remote Radio Unit (RRU)

Flexible combinations of the three units and auxiliary devices can provide different

NodeBs that apply to different scenarios such as indoor centralized installation, outdoor

centralized installation, outdoor distributed installation, site sharing of multiple network

systems, and multi-mode application. Figure 2-7 shows the three units and auxiliary

devices and Figure 2-8 shows the different application scenarios.



Figure 2-7 Units and auxiliary devices of the 3900 series NodeBs



Figure 2-8 Application scenarios of the 3900 series NodeBs

Different combinations of the units and auxiliary devices form the following 3900 series

NodeBs:

Cabinet macro NodeB

The cabinet macro NodeB, integrating the BBU3900 and the WRFU, consists of the



indoor BTS3900 and the outdoor BTS3900A. The cabinet macro Node B applies to

centralized installation, where the BTS3900 and the BTS3900A, as mentioned above,

are recommended for indoor application and outdoor application respectively.

Distributed Node B

The distributed NodeB, known as the DBS3900, consists of the BBU3900 and the RRU.

For the distributed installation, the RRU is placed close to the antenna. This can reduce

feeder loss and improve Node B performance.

Compact mini NodeB

The compact mini Node B is also of two types, which is applies to the new outdoor 3G

sites where no equipment room exists, hot spots, marginal networks, and blind spots

such as tunnels.

2.3.1 Baseband Module Configuration

The BBU3900 is an indoor base band unit. The maximum is 1 BBU3900 in one Node B.

It is used for all 3900 series WCDMA Node B products. The BBU3900 consists of the

boards for the base band, control, switching and Iub transmission interface

functionalities. All the boards support the plug-and-play function, and the capacity and

interface board can be expanded as required.

The BBU3900, powered with ¨ 48 V/ 24V DC, provides environmental protection and

cooling functions. It has FE and E1 connections for the Iub interface, for 6 optical CPRI

links, and for up to 16 external alarms.

The BBU3900 is 19 inch wide and 2 U high. It can be installed on the floor, on the wall,

or mounted in a 19-inch rack.

BBU3900 subrack is composed of power and environment interface unit and universal

BBU fan unit. These units are plug in a backplane of the subrack.

The BBU3900 also provides 8 slots for WMPT, UTRP, WBBP, UELP and UFLP. Every

slot of BBU subrack supports to plug in several kinds of board flexibly.



Figure 2-9 Figure 2-1 Structure of the BBU3900 Subrack

Board Slot 0 Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7

WMPT available available

UTRP available available available available available available

WBBP available available available available

UELP available available available available available available available available

UFLP available available available available available available available available

One WMPT is mandatory configuration. And one WBBP also must be configured as

BBU realizes baseband processing. Others such as UTRP, UELP and UFLP are

optional depended on requirements.

I. WMPT

The WMPT integrated the control and transport subsystem manages the entire Node

System. The subsystem performs operation and maintenance, processes various types

of signaling, provides system clocks, and provides transport interfaces. One BBU3900

can hold up to two WMPTs for 1+1 redundancy.

One WMPT provides 4 E1, 1 electrical FE and 1 optical FE interfaces. For one Node B,

2 WMPT can provide 8 E1 and 2 electrical FE and 2 optical FE interfaces.

II. UTRP

With the UTRP, the BBU can provide extra E1 interface. UTRP3 supports 8 E1 for ATM

and UTRP4 supports 8 E1 for IP. So the UTRP is regarded as extension transmission

Processing unit.

Maximum 5 UTRP can be supported in one BBU3900.



Type E1 for ATM E1 for IP Ethernet

10/100 electrical

Ethernet 10/100 optical

WMPT 4 1 1 UTRP3 8 0 0 0 UTRP4 0 8 0 0

III. Baseband Card Configurations (WBBP)

There are 2 kinds of Baseband card, WBBPa and WBBPb.

The WBBPa can Process uplink and downlink baseband signals. Support HSDPA

and HSUPA phase1 (10 ms TTI).

The WBBPb can Process uplink and downlink baseband signals. Support HSDPA

and HSUPA phase2 (2 ms TTI).

One WBBP provides 3 CPRI interfaces. The CPRI support electrical and optical port.

The electrical interface is provided for connection with WRFU, while the optical

interface is provided for connection with RRU.

Board Type Cell Uplink R99/HSUPA CE

Downlink R99 CE

HSDPA Capacity

WBBPa 3 cells 128 256 45 HS-PDSCH codes

WBBPb1 3 cells 64 64 45 HS-PDSCH codes




CCH R99 included, 16CE for downlink and 6 CE for uplink for 3 cells

Resources for Compressed Mode included

Resources for Softer handover included

TX diversity is no impact for CE consumption for both uplink and downlink direction.

Resources for HS-DSCH, HS-SCCH and HS-DPDCH included, HSDPA services

not affect BB capacity for R99 services.

Capacity expansion. Node B capacity can be expanded by adding more CE license

or by adding more channel boards. If the capacity of the existing hardware is



enough for capacity expansion, only license file need to be upgraded. Uplink and

downlink capacity expansion could be implemented separately. Otherwise, new

board and new license need to be added to meet the new requirement of capacity

expansion. Uplink and downlink capacity expansion could also be implemented

separately. The step of license expansion is 16 CEs according to the customer¡s

IV. Lighting Protection unit (UELP and UFLP)

Considering the issue of E1/T1 or FE interface protection, there are 2 kinds of

lighting protection unit developed: UELP and UFLP. Lighting protection unit can plug

into the slot of BBU3900 or additional signal lighting protection unit.

UELP provides protection for E1/T1 interface.

UFLP provides protection for FE interface.

2.3.2 RF Module Configurations

For cabinet Node BBTS3900 and BTS3900A, the RF module is WRFU.

For distributed Node Band BTS3900C, the RF module is RRU3804 /RRU3801C.

I. WRFU Configurations

The WRFU is divided into two types according to output power and carries:

40 W WRFU, 40W output power on the antennal port, 2 carriers

80W WRFU, 80W output power on the antennal port, 4 carriers

Two 40W WRFUs in parallel connection within one sector can support the 1 x 4

configuration.

Two 80W WRFUs in parallel connection within one sector can support the 1 x 8

configuration.

Two WRFUs in parallel connection within one sector can support transmit diversity

and 4-way receive diversity.

One 80W WRFU can support 4 continuous carriers in 1 sector and it also can

support non continuous carriers (for example 1101, 1011, 1001, 1010, 1100), which

can be applicable to RAN sharing with 2 operators has non continuous carriers.

II. RRU Configurations

The RRU is divided into two types according to output power and carries:

40 W RRU3801C (or RRU3801E), 40W output power on the antennal port, 2



carriers

60 W RRU3804, 60W output power on the antennal port, 4 carriers

One 40W RRU can support 2 continuous carriers in 1 sector. DBS3900 can support

smooth capacity expansion from 1 x 1 to 1 x 2 without adding RF module.


configuration.

One 60W RRU can support 4 continuous carriers in 1 sector. With 20W per carrier

configuration, it can support 3 non continuous carriers (for example 1101, 1011),

which is applicable to RAN sharing with 2 operators has non continuous carriers.


configuration.

Two RRUs in parallel connection within one sector can support transmit diversity and

4-way receive diversity.

2.3.3 3900 Series Node B typical configuration

I. BTS3900 typical configuration

If the BBU and RFU are housed in an indoor cabinet, they form a BTS3900. The following figure shows the BTS3900 (-48V DC).

Figure 2-10 BTS3900 in full configuration

BTS3900 can support up to 24 cells. There can be configured as Omni



directional, 2-sector, 3-sector and 6-sector configurations.

BTS3900 supports a smooth capacity expansion from 1 x 1 to 6 x 4 or 3 x 8.

BTS3900 supports dual band configurations by a free mix of WRFU types for

any frequency band connected to the baseband Unit.

The maximum capacity of the BTS3900 is up to UL 1536 CEs and DL 1536

CEs. The capacity can be expanded simply through additional modules or

license upgrade. In the initial phase of network deployment, you can use

some small capacity configurations such as 3 x 1 configurations. With the

increase in the number of UEs, you can upgrade the system to large-capacity

configurations such as 3 x 2 and 3 x 4 smoothly.

Table 2-1 Recommended configurations of the BTS3900 (WBBP4, 80W WRFU)

Per carrier

20W

Minimum # of

Indoor Cabinet

Minimum # of

WMPT

Minimum # of

WBBPb4

Minimum # of

80W WRFU

1 ¡ 1 1 1 1 1

1 ¡ 2 1 1 1 1

1 ¡ 3 1 1 1 1

1 ¡ 4 1 1 1 1

3 ¡ 1 1 1 1 3

3 ¡ 2 1 1 1 3

3 ¡ 3 1 1 2 3

3 ¡ 4 1 1 2 3

6 ¡ 1 1 1 2 6

6 ¡ 2 1 1 2 6

3 ¡ 6 1 1 3 6

3 ¡ 8 1 1 4 6

6 ¡ 3 1 1 3 6

6 ¡ 4 1 1 4 6

Table 2-2 Recommended configurations of the BTS3900 (WBBP2, 40W WRFU)



Per carrier

20W

Minimum # of

Indoor Cabinet

Minimum # of

WMPT

Minimum # of

WBBPb2

Minimum # of

40W WRFU

1 ¡ 1 1 1 1 1

1 ¡ 2 1 1 1 1

3 ¡ 1 1 1 1 3

3 ¡ 2 1 1 2 3

6 ¡ 1 1 1 2 6

6 ¡ 2 1 1 2 6

II. BTS3900A typical configuration

If the BBU3900 is housed in APM30 or TMC, RFU module are housed in outdoor RF cabinet, they form a Node B BTS3900A. The following figures show the BTS3900A with 3 RFU cabinet and 6 RFU cabinet.

Figure 2-11 Outdoor cabinet macro Node B (with three WRFUs)



Figure 2-12 Outdoor cabinet macro Node B (with six WRFUs)

The capacity, CE resource of BTS3900A is the same as BTS3900.

Table 2-3Recommended configurations of the BTS3900A (WBBP4, 80W WRFU)

Per carrier

20W

Minimum # of

Cabinet

Minimum # of

WMPT

Minimum # of

WBBPb4

Minimum # of

80W WRFU

1 ¡ 1 1 1 1

1 ¡ 2 1 1 1

1 ¡ 3 1 1 1

1 ¡ 4 1 1 1

3 ¡ 1 1 1 3

3 ¡ 2 1 1 3

3 ¡ 3 1 2 3

3 ¡ 4

One APM30,

One 3RF

cabinet with

internal battery

1 2 3



Per carrier

20W

Minimum # of

Cabinet

Minimum # of

WMPT

Minimum # of

WBBPb4

Minimum # of

80W WRFU

6 ¡ 1 1 2 6

6 ¡ 2 1 2 6

3 ¡ 6 1 3 6

3 ¡ 8 1 4 6

6 ¡ 3 1 3 6

6 ¡ 4

One APM30,

One 6RF

cabinet

One battery

cabinet 1 4 6

Table 2-4Recommended configurations of the BTS3900A (WBBP2, 40W WRFU)

Per carrier

20W

Minimum # of

Cabinet

Minimum # of

WMPT

Minimum # of

WBBPb2

Minimum # of

40W WRFU

1 ¡ 1 1 1 1

1 ¡ 2 1 1 1

3 ¡ 1 1 1 3

3 ¡ 2

One APM30,

One 3RF

cabinet with

internal battery 1 2 3

6 ¡ 1 1 2 6

6 ¡ 2

One APM30,

One 6RF

cabinet

One battery

cabinet

1 4 6

III. DBS3900 typical configuration

The BBU and RRU are the main parts of DBS3900. The two units support independent installation, capacity expansion, and evolution, thus meeting the requirements of WCDMA network construction. The two units can be connected by electrical or optical cables through the CPRI interface, thus facilitating site acquisition, device transportation, equipment room construction, and equipment installation.



Figure 2-13 DBS3900 full configuration

The capacity, CE resource of DBS3800 is also the same as BTS3900.

Table 2-5 Recommended configurations of the DBS3900 (WBBP4, RRU3804)

Per carrier 20W Minimum # of

WMPT

Minimum # of

WBBPb4

Minimum # of

RRU3804

1 ¡ 1 1 1 1

1 ¡ 2 1 1 1

1 ¡ 3 1 1 1

3 ¡ 1 1 1 3

3 ¡ 2 1 1 3

3 ¡ 3 1 2 3

6 ¡ 1 1 2 6

6 ¡ 2 1 2 6

3 ¡ 6 1 3 6

3¡ 8 1 4 6

6 ¡ 3 1 3 6

Table 2-6 Recommended configurations of the DBS3900 (WBBP2, RRU3801C)




WMPT

Minimum # of

WBBPb2

Minimum # of

RRU3801C

1 ¡ 1 1 1 1

1 ¡ 2 1 1 1

3 ¡ 1 1 1 3

3 ¡ 2 1 2 3

6 ¡ 1 1 2 6

6 ¡ 2 1 4 6

IV. BTS3900C typical configuration

The compact mini Node B known as the BTS3900C consists of one BBU3900C (BBU3900 with a mini outdoor cabinet) and one RRU (RRU3801C or RRU3804).

BTS3900C can support up to 1sector *3carriers configuration.

The maximum capacity of the BTS3900C is up to UL 384 CEs and DL 384 CEs. The capacity can be expanded simply through additional modules or license upgrade. The step of license expansion is 16CEs according to the customer¡s requirements.

Figure 2-14 Compact mini Node B with DC power



Figure 2-15 Compact mini Node B with AC power

Table 2-7 Recommended configurations of the BTS3900C (WBBP2, RRU3804)


WMPT

Minimum # of

WBBPb2

Minimum # of

RRU3804

1 ¡ 1 1 1 1

1 ¡ 2 1 1 1

1 ¡ 3 1 1 1

Table 2-8 Recommended configurations of the BTS3900C (WBBP2, RRU3801C)


WMPT

Minimum # of

WBBPb2

Minimum # of

RRU3801C

1 ¡ 1 1 1 1

1 ¡ 2 1 1 1



2.4 UMTS Capacity Dimensioning Procedure

2.4.1 Introduction

The main driver of 3G mobile networks is availability of wide range of multi-media

applications and services. This new multi-service aspect brings totally new requirements

into capacity dimensioning process.

The aim of WCDMA capacity dimensioning is to obtain the number of subscribers

supported by one cell by the given traffic model.

Traffic models like Erlang B, Erlang C, etc., are established models which can model

single service, circuit-switched traffic quite accurately. However, there are no

established ways for modeling multi-service traffic in UMTS. Huawei makes a great deal

of study in the field of multi-service capacity dimensioning and introduces

multidimensional Erlang B model as the approach to estimate the capacity of CS

multi-service. PS is best effort which is used in mixed services (CS and PS) capacity

dimensioning.

Assuming the number of subscribers, the traffic profile can be used to determine

whether the maximum permissible system load is exceeded or not by the overall system

load. We can get the overall system load from the CS peak cell load, CS average cell

load and PS average cell load. When the overall system load equals the maximum

permissible system load, the assumed number of subscribers is the capacity of one cell.

The procedure of mixed services capacity dimensioning is illustrated in Figure 1-1



Dimensioning Start

Multidimensional ErlangBcalculate Peak load of CS

Calculate averageload of PS

Calculateaverage load of CS

Dimensioning End

Calculate load ofHSDPA

Calculate load ofHSUPA

Calculate total cellload

=Target Cell Load?

Traffic modelLoad per connection

Assumed Subscribers per cell

No

Yes

Figure 2-16 Mixed Services Capacity Dimensioning Procedure

This chapter is organized as follows:

Section 2.4.2 introduces the main principle about CS capacity dimensioning.

Section 2.4.3 introduces the main principle about PS capacity dimensioning.

Section 2.4.4 introduces the main principle for HSDPA capacity dimensioning

Section 2.4.5 introduces the main principle for HSUPA capacity dimensioning

Section 2.4.6 introduces MBMS capacity dimensioning

Section 2.4.7 presents us the principle about mixed services capacity dimensioning.

2.4.2 CS Capacity Dimensioning Principle

1. Calculation of CS peak cell load peakCSLoad

CS peak cell load can be calculated by multidimensional ErlangB algorithm.

Multidimensional ErlangB can estimate the respective blocking probability of various CS

services. Under a fixed cell load, different services have different blocking probability,



which depends on the load of a single connection. Multidimensional ErlangB model is

illustrated in following figure:

multiservice

Blockedcalls

Callsarrival

Callscompletion

Fixed cell load

Figure 2-17 Multidimensional Erlang B Model

Multidimensional Erlang B model makes it possible to utilize the cell capacity effectively.

The resource is shared by all services in multidimensional ErlangB model, which makes

use of the fact that the probability of simultaneous bursts from many independent traffic

sources is very small. This idea is that according to the law of large numbers the

statistical fluctuation decreases in an aggregated flow of many burst and fluctuating

traffic flows when the number of combined flows increases. The following figure

illustrates the gain when resource is shared compared to the partitioned resource.

ErlangB - Partitioning Resources

Low Utilization of resources

Multidimensional ErlangB - Resources shared

High Utilization of resources

Figure 2-18 Partitioning Resources vs Resources Shared

In WCDMA CS capacity dimensioning, given respective GoS (blocking probability) of CS

services and designed load, number of subscribers supported by one cell can be

obtained using multidimensional Erlang B (MDE) model. Further more, given GoS and

number of subscribers per cell, CS peak cell load can be obtained; given number of

subscribers per cell and CS peak cell load, respective GoS of CS services can be

obtained also. This is shown in following figure.



GoS requirements ofvarious CS services CS peak cell load

Subscribers per cell

MDE

Figure 2-19 Estimate CS Capacity with Multidimensional Erlang B Model

2. Calculation of CS average cell load avgCSLoad

According to the average number of channel occupied by CS services, which is

approximately equals to the cell traffic when the blocking probability is relatively low, we

can obtain the average CS cell load.

Traffic per cell of CS service i :

userii NUserTrafficPerCellTrafficPer (3)

CS average cell load:

Uplink:

i

iULiavgCS nectionLoadPerConCellTrafficPerLoad (4)

Downlink:

On downlink the calculation of load should consider the ratio of SHO.

)1( SHOi

iDLiavgCS RnectionLoadPerConCellTrafficPerLoad

(5)

Where,

userN : The number of subscribers per cell

iUserTrafficPer : The traffic per subscriber of CS service i .



SHOR : Soft handover ratio.

2.4.3 PS Capacity Dimensioning Principle

The following shows us how to calculate the average cell load caused by PS services.

1. Calculation of PS average cell load for UL AvgPSLoad

iULi

ichannelsAvgPS nectionLoadPerConNLoad (6)

Where ichannelsN is the number of equivalent channels for service i

3600)1()1( Re

ii

Burstinessiontransmissiiuserichannels R

RRPerUserThroughputNN

(7)

iPerUserThroughput : Throughput per user for service i .

iontransmissiR Re : The ratio of data retransmission for service i because of block error.

BurstinessR : The ratio of traffic burstiness.

2. Calculation of PS average cell load for DL

Calculation of PS average cell load for DL is almost same as that for UL except that the

impact on the load due to SHO should be considered in DL.

2.4.4 HSDPA Capacity Dimensioning

For HSDPA capacity dimensioning, average HSDPA cell throughput can be calculated

based on available resources like power and codes for HSDPA and cell average radius.

The basic principle is to calculate the Ec/Io distribution in the cell due to the specified cell

range, power allocation to HSDPA and codes resources, and get the HSDPA cell

average throughput from the simulation result between Ec/Io and throughput.

The following figure shows the procedure.



Simulation

Ec/Io distribution

Ior/Ioc distribution

Cell coverageradius

Cell averagethroughputEc/Io =>throughput

Power andCode forHSDPA

Figure 2-20 HSDPA capacity dimensioning

The power allocation to HSDPA can be also calculated by the defined HSDPA cell

average throughput and cell radius, so as the cell radius with the defined HSDPA cell

average throughput and power allocation.

2.4.5 HSUPA Capacity Dimensioning

Similar to capacity dimensioning of HSDPA, average HSUPA cell throughput for input

loading or the loading needed by HSUPA to achieve certain throughput can be

calculated. The following figure shows the procedure of calculating HSUPA cell

throughput from the defined loading.



Figure 2-21 HSUPA capacity dimensioning

Where,

R is the cell range of the specified Ec/No.

User rate at the cell range R can be gotten by the simulation result between Ec/No and

R. HSUPA cell loading also leads to the specified HSUPA throughput as well, the final

HSUPA cell throughput should be the restricted value of the two results.

The loading needed by HSUPA to achieve certain throughput can also be calculated.

2.4.6 MBMS Capacity Dimensioning

MBMS service has two kind of working mode: PTP (point to point), PTM (point to

multi-point), PTP is borne on the DCH or HSDPA, so the capacity dimensioning of

PTP mode is the same to R99 and HSDPA. We just detail the PTM mode capacity

dimensioning here.

The procedure of MBMS capacity dimensioning is showed in the following figure:

Uplink load HSUPA actual

cell load Maximum rate of

single user

HSUPA cell

throughput

HS-DPCCH load

R99 load

A-DCH load

Cell Radius Ec/N0 Ec/N0R

User rate at

distance R



Figure 2-22 MBMS Dimensioning Procedure

Power consumption for each MBMS channel at air interface can be calculated by

the following formula:

)10/()10( 10/10/ BSMBMSL PPMBMSA

Where,

MBMSA is the loading for each MBMS channel at air interface

MBMSLP is the power consumption for per MBMS channel, this can be calculated

via link budget with specified bearer and cell radius requirement.

BSP is the total power of NodeB

If we take linksN as the MBMS channels at air interface per cell, assume that the

MBMS channels are average distributed in all carriers per cell, so the MBMS

channels per cell per carrier at air interface can be gotten by linksN / carriers.

Thus the total loading of all the MBMS channels within one cell can be calculated

by the following formula:

)/(* carriersNALoad linksMBMSMBMS

Where,

MBMSLoad is the total loading consumption of MBMS services



2.4.7 Mixed Services Capacity Dimensioning

PS services have best effort characteristic which is used in mixed services capacity

dimensioning. Best effort means that the packet service can utilize the resource that is

available, but there are no guarantees on ¡blocking probability¡. The part of resource

used by PS services is clearly visible in following figure.

Total Load

CS Peak Load

CS Average Load

Load occupied by CS

Load occupied by PS

Load

Time

Figure 2-23 Resource Shared by CS and PS

According to the previous calculation we can obtain the actual total cell load by the

formula:

},max{_ HSUPAavgPSavgCSpeakCSULtotalcell LoadLoadLoadLoadLoad

MBMSCCHHSDPAavgPSavgCSpeakCSDLtotalcell LoadLoadLoadLoadLoadLoadLoad },max{_

When the actual total cell load totalcellLoad equals to the cell target load, the number

of subscribers here is the maximum capacity of one cell.

2.5 UMTS CE Dimensioning Procedure

2.5.1 Introduction

CE (Channel Element) is defined as a fundamental base band processing element.

Generally, one channel element can be considered as the resources consumed by one

12.2kbps AMR service channel and one 3.4kbps signaling channel. CEs are pooled per

Node B, no additional CE are needed for either CCH or for signaling channels.



The number of channel elements is determined by three factors: traffic model, radio

bearers and CE factors.

Traffic models like Erlang B, Erlang C, etc., are established models which can model

single service, for instance, circuit-switched traffic. However, there are no established

ways for modeling multi-service traffic in UMTS. Huawei has done thorough research in

the field of multi-service capacity dimensioning and introduces multidimensional ErlangB

model as the approach to estimate the CE of circuit switched (CS) multi-service.

The figure below shows procedure of CE dimensioning.

Subscribers per NodeBTraffic model

Dimensioning Start

Multidimensional ErlangBcalculate Peak CE of CS

Calculate average CEof PS

Calculateaverage CE of CS

Total ChannelElements

Dimensioning End

Calculate CE forA-DCH of HSDPA

Calculate CE for HSUPAand A-DCH of HSUPA

Figure 2-24 CE Dimensioning Procedure

This section is organized as follows:

2.5.2 CE Dimensioning for CS Service

2.5.3 CE Dimensioning for PS Service

2.5.4 CE Dimensioning for HSDPA

2.5.5 CE Dimensioning for HSUPA

2.5.6 CE Dimensioning for MBMS

2.5.7 Total Number of Channel Elements



Note:

CE factors means: The number of CEs needed by one connection for each specific radio

bearer.

2.5.2 CE Dimensioning for CS Service

CE dimensioning for CS services is comprised 3 parts as follows:

1. Calculating the subscribers per Node B( usersN )

Subscribers per Node B= total number of subscribers/number of NodeBs.

Total number of subscribers and the required number of NodeBs are obtained through

capacity dimensioning, for both uplink and downlink.

2. Calculating the peak number of CEs for CS service ( PeakCSCE _ )

Multidimensional ErlangB algorithm is used to calculate the number of channel elements

needed during peak traffic at Busy Hour for CS services meeting the respective GoS

(grade of service) requirements.

Traditional single service (voice) adopts ErlangB formula. With only one service it is

sufficient to find the peak traffic of a given GoS.

In fact, each radio bearer of various services has different GoS requirement. So we

adopt Multidimensional ErlangB algorithm to calculate the blocking probability for

multiple services when accessing the system with limited resources, which is a way to

model multi-service systems where resources are shared by all services with different

GoS requirements. Multidimensional ErlangB algorithm model is shown in following

figure.

Figure 2-25 Multidimensional Erlang B Model



Multidimensional ErlangB model makes it possible to utilize the CE resources effectively.





traffic flows when the number of combined flows increases. The figure below shows gain

when resources are shared compared to when resources are pre-partitioned.

Figure 2-26 Partitioning Resources vs. Resources Shared

In CS peak CE dimensioning, Multidimensional ErlangB algorithm can calculate traffic,

blocking probability and the peak number of CEs for CS services, if any two of them is

known, the third one can be found.

1. Calculating the average number of CEs for CS service ( AverageCSCE _ )

In UMTS, more resources are allocated to CS service than PS service in order to

guarantee CS service coverage. In other words, CE resources will first have to satisfy

peak traffic during Busy Hour Traffic. Nevertheless, CS service consumes average

number of CEs due to the fact that CS traffic is not always at its peak

The average number of CEs needed at Busy Hour for CS services according to the

traffic is calculated as following formula:

iusersi

iSHOAverageCS NUserTrafficPerRCE )1(_ (1) (



iUserTrafficPer is traffic per user for service i .

SHOR is Soft Handover ratio.

i is the CE factors and shown as table 2-1.

Table 2-1 CE Map for RAB

Bearer Type CE Consumption on UL CE Consumption on DL

AMR 12.2kbps 1 1

CS 64kbps 3 2

PS 64kbps 3 2

PS 128kps 5 4

PS 144kps 5 4

PS 384kbps 10 8

2.5.3 CE Dimensioning for PS service

Calculating the average number of CEs needed at Busy Hour for PS service

( AveragePSCE _ ) is same as that of CS average CE service, it is according to the traffic

and should consider the PS characteristics in addition, e.g. burstiness, retransmission. It

is shown in the following formula:

iitranratei ii

iusersBurstrateSHOAveragePS R

RPerUserThroughputNRRCE

)1(3600

)1()1( _Re_ (2)

BurstrateR : The burst margin.

iPerUserThroughput (kbit): The busy hour throughput per user for service i .

i : The channel utilization for service i .

itranrateR _Re : The retransmission ratio for service i .

iR （kbps）: The bit rate for service i .

2.5.4 CE Dimensioning for HSDPA

1. HSDPA Uplink CE dimensioning ( ULHSDPACE _ )



On the uplink, uplink A-DCH (associated DCH) can be used for signalling and

transmission of HSDPA uplink traffic. A-DCH has variable SF of 4, 8 and 16 and its

corresponding data transmission rate is 384kbps, 128k and 64k, respectively.

Usually the UL total traffic model of R99 includes the HSDPA users, therefore the

number of CEs consumed by HSDPA users in uplink ( ULHSDPACE _ ) is already included

in R99 CE dimensioning, and CE consumed by A-DCH equals to that of DCH if the

bearing rate is same, so only the number of CEs consumed by HSDPA in downlink

should be considered.

If UL total traffic does not include HSDPA traffic, number of uplink CEs for HSDPA

( ULHSDPACE _ ) can be calculated according to number of simultaneously connected

HSDPA users ( LinksHSDPAN _ , show as formula (3)) and CE factors. For example, if the

bearing rate of UL A-DCH is 64kbps which requires 3 CEs according to CE factors, then

the number of CEs required by HSDPA users in uplink will be3_ LinksHSDPAN

.

2. HSDPA Downlink CE dimensioning ( DLHSDPACE _ )

The SF of A-DCH is 256 on downlink, with the rate of 3.4 kbps. When an HSDPA

subscriber accesses the network, a downlink A-DCH is set up, which consumes one CE.

Therefore CE resource consumed by HSDPA DL A-DCH depends on the number of

simultaneously connected HSDPA users, which can be calculated according to the

following formula:

HSDPA

usersHSDPALinksHSDPADLHSDPA GBR

NPerUserThroughputNCE __

(3)

LinksHSDPAN _ is the number of simultaneously connected users of HSDPA.

HSDPAPerUserThroughput is the throughput per user of HSDPA.

HSDPAGBR is the guaranteed bit rate for HSDPA user.

There is dedicated H/W in Huawei Node B (BTS3812E/BTS3812AE, DBS3800 and

BTS3812AE) to support HSDPA service processing, which does not consume the CE

for R99. Only the CEs for associated signaling need to be taken into account.



2.5.5 CE Dimensioning for HSUPA

The following table shows the CE factors consumed by HSUPA service.

CE Factors of HSUPA

CE Factors

MinSF HSUPA Rate

(kbps) HSUPA Phase1 HSUPA Phase2

SF64 <35.4 3 1

SF32 ~69 3.5 1.5

SF16 ~169.8 5 3

SF8 ~337.8 7 5

SF4 ~709.2 12 10

2*SF4 ~1448.4 22 20

2*SF2 Not Support 32

2*SF2 + 2*SF4 Not Support 48

Notes: For phase 1, CE factors already include the CE consumed by A-DCH of HSUPA in

uplink. For Phase 2, if A-DCH is over HSUPA in uplink, no extra CE resource should be

considered during the calculation, otherwise, one additional CE is needed by one

A-DCH in uplink.

1) CE consumed by HSUPA traffic

CE numbers consumed by HSUPA traffic channel depends on the simultaneous

connected links number.

HSUPAHSUPATrafficHSUPA CEFactorLinksCE *_

Wherein,



)1(*

)Re1(*)1(*)(

)(

Burstratio

ontransmissiSHOfactorkbitUseroughputPerAverageThr

kbitPerNodeBThroughputLinksHSUPA

HSUPAHSUPA

Considering the impact on CE consumption of soft handover overhead, HSUPA traffic

burst and retransmission caused by error transmission, more CEs are needed by

HSUPA traffic channel.

2) CE consumed by A-DCH of HSUPA

CE consumed by A-DCH of HSUPA depends on the number of A-DCH. One A-DCH is

needed for one HSUPA service link.

(1)In Uplink ( AULHSUPACE _ )

One A-DCH of HSUPA in uplink consumes one CE which is already included in CE

factors in Phase I. No extra CE should be taken into account for A-DCH of HSUPA in

uplink any more.

(2)In Downlink ( ADLHSUPACE _ )

If HSUPA shares the same carrier with HSDPA, A-DCH of HSUPA can be loaded on

HSDPA, thus on extra CE is needed for A-DCH of HSUPA.

2.5.6 CE Dimensioning for MBMS

Downlink CE consumption for MBMS only need to be concerned. CE consumption

for each MBMS channel is the same to R99 service, showed in the following table:

Table 2-2 CE consumption for MBMS

MBMS Bearer 16kbps 32kbps 64kbps 128kbps 256kbps

OVSF SF128 SF64 SF32 SF16 SF8

CE

consumption 1 1 2 4 8

Bearerj

jlinksMBMS CENCE *_



Where,

MBMSCE is the total CE consumption for all MBMS channels per Node B.

jlinksN _ is the MBMS channel number for each Node B, this is the sum of all the

MBMS channels at each cell within Node B.

BearerCE is the CE consumption of each MBMS bearer, as showed in the table

2-1.

2.5.7 Total Number of Channel Elements

R99 CE dimensioning method is the same for both uplink and downlink.

Since PS services have best effort characteristic, the part of resources which is not used

by CS services can be utilized by PS services. CE resources are shared by CS and PS

service per Node B is clearly visible in following figure.

Total CE

CE Peak for CS

CE Average for CS

CE occupied by CS

CE occupied by PS

Time

Figure 2-27 CE resource shared by PS and CS service

Therefore, according to the previous calculation we can obtain the number of R99 CEs

in uplink and downlink respectively by the same formula as shown in the following:

),( ___99 AveragePSAverageCSPeakCSR CECECEMaxCE (4)

Finally, the total number of channel elements per Node B for both R99 and HSDPA can

be written as:



ULHSUPAULHSDPAULRULTotal CECECECE __99_ (5)

MBMSDLHSUPADLHSDPADLRDLTotal CECECECECE __99_ (6)

2.6 UMTS Iub Dimensioning Procedure

2.6.1 Introduction

Iub, as shown in Figure 2-28 figure, is the interface between RNC and Node B.

RNS

RNC

RNS

RNC

Core Network

Node B Node B Node B Node B

Iu Iu

Iur

Iub Iub Iub Iub

UTRAN

Figure 2-28 UTRAN Architecture

The purpose of Iub dimensioning is to calculate Iub bandwidth and then obtain the

required E1 pairs.

Traffic models like ErlangB, ErlangC, etc., are established models which can model

single service, circuit-switched traffic quite accurately. However, there are no

established ways for modeling multi-service traffic in UMTS. Huawei has carried out

thorough research in the field of multiservice network dimensioning and adopts

multidimensional ErlangB model to estimate the Iub bandwidth of CS multi-service. For

mixed CS, PS and HSDPA Iub bandwidth dimensioning, best effort characteristic of PS

and HSDPA is used. Apart from traffic bandwidth, Iub bandwidth dimensioning also

includes calculation of Iub bandwidth occupied by common channels, signaling and

O&M.

Figure 2-29 shows the Iub dimensioning procedure.



CS Traffic Voice Traffic CS data TrafficGoS Requirements

CS IubBandwidth

IubBandwidth

Input Iub Dimensiong Output

PS Traffic PS64 throughput PS128 throughput PS384 throughputPS retransmission

Subscribes Subs. per NodeB

Common ChannelBandwidth

PS IubBandwidth

O&M Bandwidth

SignallingBandwidth

Bandwidthfor Traffic +

+

HSDPA IubBandwidth

HSDPA Traffic

Figure 2-29 Iub Dimensioning Procedure

This chapter is organized as follows:

2.6.2 Iub Bandwidth Dimensioning for Traffic

2.6.3 Iub Bandwidth Dimensioning for Others

2.6.2 Iub Bandwidth Dimensioning for Traffic

Since PS services and HSDPA have best effort characteristic, the part of Iub bandwidth

which is not used by CS services can be utilized by PS services and HSDPA. Figure

2-30 illustrates sharing of Iub bandwidth by CS and PS, HSPA.



Figure 2-30 CS and PS Sharing Resource

Therefore, the total Iub bandwidth for traffic can be obtained which is:

),max( ___ HSPAAvgPSAvgCSPeakCStraffic IubIubIubIubIub (7)

2.6.2.1 CS Peak Iub Bandwidth

PeakCSIub _ is CS peak Iub bandwidth and can be calculated by multidimensional

ErlangB algorithm. Multidimensional ErlangB can estimate the respective blocking

probability of various CS services. Under a fixed Iub bandwidth, different services have

different blocking probability, which depends on its Iub bandwidth usage.

Multidimensional ErlangB model is illustrated in the following figure

multiservice

Blockedcalls

Callsarrival

Callscompletion

Fixed Iub bandwidth

Figure 2-31 Multidimensional ErlangB Model



Multidimensional ErlangB model makes it possible to utilize the Iub bandwidth effectively.





traffic flows when the number of combined flows increases. The following figure

illustrates the gain when the resource is shared compared to when the resource is

partitioned.

ErlangB - Partitioning Resources

Low Utilization of resources

Multidimensional ErlangB - Resources shared

High Utilization of resources

Figure 2-32 Partitioning Resources vs. Resources Shared

Once the Gos requirement of CS services, the CS traffic per NodeB, the Iub factors are

known, CS peak Iub bandwidth can be calculated using multidimensional ErlangB (MDE)

model. This idea is shown in Figure 2-33following figure.

Note: Iub factors means Iub bearer bandwidth including FP, AAL2 and ATM overhead for service i.



GoS requirements ofvarious CS services

MDE

Traffic of every CSservice per NodeB;

Iub factors

CS peak Iub bandwidth

Figure 2-33 Estimate CS peak Iub Bandwidth with Multidimensional Erlang B Model

2.6.2.2 CS Average Iub Bandwidth

AverageCSIub _ is the average Iub bandwidth for CS services, which does not guarantee

the GoS requirements. The formula below is used to calculate CS average bandwidth:

iiIubiuser

iiIubiAverageCS

RPerUserIubTrafficN

RPerNodeBIubTrafficIub

_

__

**

* (8)

Where:

)1(* SHOii RUserTrafficPerPerUserIubTraffic (9)

iUserTrafficPer : traffic per user for CS service i;

SHOR : Soft handover ratio which does not include softer handover;

iIubR _ : Iub factors for CS service i, including FP, AAL2 and ATM over head;

userN : Number of Subscribers per NodeB;

2.6.2.3 PS Iub Bandwidth

AveragePSIub _ is the PS Iub bandwidth, it is almost the same to the CS average Iub

bandwidth except that some PS characteristics, e.g. PS burstiness, retransmission need



to be considered during the dimensioning. The formula below is used to calculate PS Iub

bandwidth:

iiIubiuser

iiIubiAveragePS

RPerUserIubTrafficN

RPerNodeBIubTrafficIub

_

__

**

* (10)

Where:

i

BurstinessiontransmissiSHOii R

RRRPerUserThroughputPerUserIubTraffic

*3600)1(*)1(*)1(* _Re

(11)

iPerUserThroughput : Throughput per user for PS service i;

SHOR : Soft handover ratio and does not include softer handover;

iontransmissiR _Re : The ratio of data retransmission because of block error for PS service i;

BurstinessR : The ratio of traffic burstiness;

iR : Bearer bit rate for PS service i ;

_____________________________________________________________________

2.6.2.4 HSPA Iub Bandwidth

Since HSPA usually bears BE service, the calculation of Iub bandwidth for HSPA follows

almost the same procedure as that for PS. However, it should be noted that HSDPA

does not support SHO and therefore there is no Iub SHO overhead for HSDPA.

The formula below is used to calculate HSDPA Iub bandwidth:

)_1(*)Re1(*)_1(*/_*/

HSDPAHSDPA

HSDPAHSDPA

RatioBurstontransmissiOverheadHSDPANodeBSubsNumSubTrafficIub

(12)

Where:

HSDPA_Overhead is the difference between Iub bandwidth occupation of each HSDPA

service and the service bearer, for example, 1Mbps HSDPA service will use 1.35Mbps



Iub bandwidth, thus 35% is the overhead of this service.

HSUPA shares the same overhead compare to HSDPA for each service bearer. The

following formula is used to calculate the HSUPA Iub bandwidth:

)_1(*)_1(*)Re1(*)_1(*/_*/

ratioSHORatioBurstontransmissiOverheadHSUPANodeBSubsNumSubTrafficIub

HSUPAHSUPA

HSUPAHSUPA

(13)

2.6.2.5 MBMS Iub Bandwidth

MBMS Iub bandwidth per Node Bcan be calculated by the following formula:

MBMSIub = iMBMSi

ilinks RN __ *

Where,

iMBMSR _ is the Iub bandwidth consumption for each MBMS bearer, this value is

different with different Iub transmission technology from ATM to IP.

ilinksN _ is the MBMS channel number for each kind of MBMS bearer per Node B

(Not per cell). Because to maximize saving of Iub bandwidth, the latest 3GPP

provides FACH transmission sharing for MBMS solution to share transport bearers.

RNC transports only single FACH data. Node B transport module performs data

duplication and distributes them to different FACH Channels in different cells, as

shown in the following figure, where the common transport bearer is shared over Iub.

Thus, two-third of Iub bandwidth is saved by the improved Iub transport.

CRNC Node B

MBMS stream

CN

Iub transport bearer

Figure 2-34 Iub transmission sharing for MBMS



2.6.3 Iub Bandwidth Dimensioning for Others

2.6.3.1 Iub Bandwidth for Common Channel

Iub bandwidth for common channel mainly includes FACH and PCH for downlink while RACH for uplink.

The Iub bandwidth for downlink CCH depends on the configurations of FACH and PCH. FACH and PCH are mapped onto the same physical channel S-CCPCH, each cell has one S-CCPCH.

The uplink configuration of RACH can be 1 or 2 for each cell, generally each cell has one RACH.

The typical Iub bandwidth for common channel can showed as the following table.

70 kbps73 kbpsDL Bandwidth for SCCPCH(FACH/PCH)

50 kbps60 kbpsUL Bandwidth for RACH

IPATMIub Bandwidth of Common Channels

70 kbps73 kbpsDL Bandwidth for SCCPCH(FACH/PCH)

50 kbps60 kbpsUL Bandwidth for RACH

IPATMIub Bandwidth of Common Channels

The Iub bandwidth for common channel based on ATM is a little bigger than that based

on IP.

2.6.3.2 Iub Bandwidth for Signaling

Signaling including NCP, CCP and ALCAP also consumes Iub bandwidth. Iub bandwidth

for signaling generally depends on the actual traffic volume. For example, Iub bandwidth

for signaling becomes higher during busy hours.

Iub signaling bandwidth can be simplified as approximately 10% of Iub traffic throughput.

2.6.3.3 Iub Bandwidth for O&M

O&M Iub bandwidth is configurable and the typical recommended value is 64kbps for both

uplink and downlink.

3 RNC

3.1 Configurations standards of BSC6800

The BSC6800 is Huawei RNC product name. The BSC configuration models are described in

following table:



RNC Type #

Node B # Cell # E1 Ports

#

STM-1

Throughput

(Mbps/Erl)

#

Cabinet

RNC Type 1 100 300 126 64 60/2500 1

RNC Type 2 200 600 252 64 120/5000 2

RNC Type 3 300 900 384 64 180/7500 2

RNC Type 4 400 1,200 507 64 240/10k 2

RNC Type 5 500 1,500 630 64 300/12.5k 3

RNC Type 6 600 1,800 756 64 360/15k 3

RNC Type 7 700 2,100 882 64 420/17.5k 3

RNC Type 8 800 2,400 1, 008 64 480/20k 4

RNC Type 9 900 2,700 1, 134 64 540/22.5k 4

RNC Type10 1,000 3,000 1, 260 64 600/25k 4

RNC Type11 1,100 3,300 1, 386 64 660/27.5k 5

RNC Type12 1,200 3,600 1, 512 64 720/30k 5

RNC Type13 1,300 3,900 1, 638 64 780/32.5k 5

RNC Type14 1,400 4,200 1, 764 64 840/35k 6

RNC Type15 1,500 4,500 1, 890 64 900/37.5k 6

RNC Type16 1,600 4,800 2, 016 64 960/40k 6

The BSC6800 configuration can be calculated by following formula:

1 BSC6800 = 1 WRSS + n WRBS

WRSS: Wireless RNC Switching Sub rack.

WRSS is the ATM switching platform of BSC6800, which also provides Iu/Iur interfaces. Only 1

WRSS is configured for 1 BSC6800. The internal hardware components for 1 WRSS are fixed for

any model configuration.

WRBS: Wireless RNC Business Sub rack

WRBS is responsible for ATM frame processing and provides Iub interface. The internal hardware

components of 1 WRBS are fixed.

Their internal configurations are shown below



Notes：

- The WOSE in WRBS supports channelized STM-1.

- The WLPU in WRSS supports unchannelized STM-1.

Even we use unchannelized STM-1, the WOSE must be configured because Iub frame processing

is terminated on this board.

WRBS content:

- one WOSE board and one WFIE board are inserted in the two slots of WINT per WRBS subrack:

the WOSE and WFIE are configured in slot 0 and 15, or vice versa. WOSE used in the configuration

W

M P U

W M P U

W

L P U

W L P U

W L P U

W L P U

W N E T c

W N E T c

W H P U

W H P U

BAM server

BAM server

WRSR WRBR

WRSS

WRBS

WRBS

WRBS

WRBS

W I N T

W

I N T

W S P U b

W

S P U b

GRU suite

W I N T

W

I N T

W

S P U b

W

S P U b

W

I N T

W I N T

W

S P U b

W S P U b

W F M R c

W

F

M R c

W

F M R c

W F M R c

W

M U X b

W M U X b

W

F M R c

W

F

M R c

W F M R c

W

F

M R c

W

M U X b

W M U X b

W

F M R c

W F M R c

W

F M R c

W

F

M R c

W

M U X b

W

M U X b

W I N T

W

I N T

W S P U b

W

S P U b

W F M R c

W F M R c

W F M R c

W F M R c

W

M U X b

W M U X b

Power distribution box Power distribution box

LAN switch-1 LAN switch-0

LAN switch-3LAN switch-2

LAN Switch KVM



is the WOSEc optical port version which is the latest version.

- 4 WFMRc are plugged in slot 2, 4, 5 and slot 13. 1 WFMRc support 30 Mbps throughput.

- 2 WSPUb are plugged in slot 10 and 11

- 2 WMUXb are plugged in slot 7 and 8

The capacity of WFMRb, WFMRc and one WRBS are as below

Board RAN6.0 Processing Capability RAN10.0 Processing Capability

WFMRb Supports 320Erl or 6 Mbit/s data streams

and 30 cells.

Supports 320Erl or 8 Mbit/s data

streams and 39 cells.

WFMRc Supports 420Erl or 10Mbit/s data streams

and 50 cells.



WRBS Supports 2500Erl or 60 Mbit/s data




Therefore, in RAN10.0 up to 4 WFMRc boards are needed to support one WRBS capacity. One

WFMRc can support HSDPA 14.4Mbps per user or per cell. And 2 WFMRb boards can support

HSDPA 14.4Mbps per cell, but 14.4Mbps per user with WFMRb board is not supported.

Huawei BSC6800 supports mix configuration of WFMRc and WFMRb boards, the capacity of mix

configuration can be caculated as the following formular:

Capacity = Min{One WRBS capacity, (WFMRb number * One WFMRb capacity + WFMRc number *

One WFMRc capacity )}

WRSS content:

- One WLPU provides 16 unchannelized STM-1 ports and the configuration principle is 1+1. 2

WLPUs are

- configured for all RNC model configurations (RNC_01, RNC_02, RNC_03, RNC_04, RNC_05

and RNC_06). The 2 WLPU are plugged in slot 2 and 3. It is possible to use the 32 ports of the

2 WLPU without redundancy (Redundancy is optional).

- The WHPU configuration principle is N+1. 1 WHPU supports 4 WRBS. 3 WHPUs (2+1) are

configured for all RNC model configurations (RNC_01, RNC_02, RNC_03, RNC_04, RNC_05

and RNC_06). The 3 WHPU are plugged in slots 10, 11 and 12.

- 2 WMPU are plugged in slot 0 and 1



- 2 WNETc are plugged in slot 7 and 8,

WRSR content:

- 2 BAM Servers with 1:1 redundancy solution are configured for each RNC model configuration.

- A dedicated slot is defined to host GRU, but no installed in basic configuration.

- 2 LAN Switches (Huawei Quidway S3928P) with 1+1 redundancy solution are configured for

each RNC model configuration.

- The KVM is configured for each RNC model configuration, which is used for RNC local

maintenance for BAM

- servers. KVM = Keyboard Video Mouse (e.g. Computer/laptop)

- The LAN Switch allows to switch the KVM on the different BAM server; it is configured for each

RNC configuration

- - For each cabinet, there is one Power distribution Box to do the Board power supply.

The configuration diagram is shown below:

Cabinet 1

WRSS

BAM

WRBS

The configuration diagram is shown below:



3.2 Configurations standards of BSC6810

The BSC6810 is Huawei RNC product name. The BSC6810 uses the all-IP Platform of Advanced

Radio Controller (PARC) developed by Huawei. The BSC6810 configuration models are

described in following table:

RNC Type #Node B # Cell Throughput (UL+DL)

(Mbps/Erl)

BHCA

(k) # Cabinet

RNC Type 1 100 300 192/3000 80 1

RNC Type 2 200 600 384/6000 160 1

RNC Type 3 300 900 576/9000 240 1

RNC Type 4 400 1,200 768/12k 320 1

RNC Type 5 500 1,500 960/15k 400 1

RNC Type 6 600 1,800 1152/18k 480 1

RNC Type 7 700 2,100 1344/21k 560 1

RNC Type 8 800 2,400 1536/24k 640 1

RNC Type 9 900 2,700 1728/27k 720 2

RNC Type10 1,000 3,000 1920/30k 800 2

Cabinet 1 Cabinet 2 Cabinet 3

WRSS WRBS

BAM WRBS WRBS

WRBS WRBS WRBS

WRBS WRBS

WRBS

WRBS

WRBS

WRBS

WRBS

WRBS

WRBS

WRBS

Cabinet 4 Cabinet 5 Cabinet 6



RNC Type11 1,100 3,300 2112/33k 880 2

RNC Type12 1,200 3,600 2304/36k 960 2

RNC Type13 1,300 3,900 2496/39k 1040 2

RNC Type14 1,400 4,200 2688/42k 1120 2

RNC Type15 1,500 4,500 2880/45k 1200 2

RNC Type16 1,600 4,800 3072/48k 1280 2

RNC Type17 1,700 5,100 3264/51k 1360 2

The BSC6810 configuration can be calculated by following formula:

1 BSC6810 = 1 RSS + n RBS n 5

RSS: RNC Switching Subrack.

The RSS is the central switching subrack of the BSC6810. Only 1 RSS is configured for 1

BSC6810.

RBS: RNC Business Subrack

The RBS is the basic service processing subrack of the BSC6810.

Their internal configurations are shown below



RBS

RSR RBR

RBS

RBS

RBS

Power distribution box Power distribution box

RSS

RINT

RINT

RINT

RINT

RINT

RINT

GCUa

DPUb

DPUb

GCUa

SCUa

SPUa

SPUa

SPUa

SPUa

SCUa

DPUb

DPUb

RBS

SPUa

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

SPUa

DPUb

DPUb

DPUb

DPUb

SCUa

SPUa

SPUa

SPUa

SPUa

SCUa

DPUb

DPUb

SPUa

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

SPUa

DPUb

DPUb

DPUb

DPUb

SCUa

SPUa

SPUa

SPUa

SPUa

SCUa

DPUb

DPUb

SPUa

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

SPUa

DPUb

DPUb

DPUb

DPUb

SCUa

SPUa

SPUa

SPUa

SPUa

SCUa

DPUb

DPUb

SPUa

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

SPUa

DPUb

DPUb

DPUb

DPUb

SCUa

SPUa

SPUa

SPUa

SPUa

SCUa

DPUb

DPUb

SPUa

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

SPUa

DPUb

DPUb

DPUb

DPUb

SCUa

SPUa

SPUa

SPUa

SPUa

SCUa

DPUb

DPUb

OMUa

OMUa

RINT

RINT

RINT

RINT

SPUa

SPUa

Notes：

The RINT refers to the interface board of the BSC6810. Physically, there is no board named RINT.

The interface boards are configured according to the transmission mode (ATM or IP) and types of

transmission port including E1/TI, unchannelized STM-1/OC-3c, channelized STM-1/OC-3, FE and

GE.

RSS & RBS content

The following figure shows the boards in the RSS:



1311975310 2 4 6 8 10 12

2725232119171514 16 18 20 22 24

GCUa

DPUb

DPUb

GCUa

SCUa

SPUa

SPUa

SPUa

SPUa

SCUa

DPUb

DPUb

26

OMUa

OMUa

RINT

RINT

RINT

RINT

SPUa

SPUa

RINT

RINT

RINT

RINT

RINT

RINT

The following figure shows the boards in the RBS:

1311975310 2 4 6 8 10 12

2725232119171514 16 18 20 22 24 26

SPUa

SPUa

DPUb

DPUb

DPUb

DPUb

SCUa

SPUa

SPUa

SPUa

SPUa

SCUa

DPUb

DPUb

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

RINT

- Two SCUa boards are permanently configured both in RSS and RBS.

- Two GCUa or GCGa boards (GCGa boards are configured to replace the GCUa when GPS is

required) are permanently configured in RSS.

- Two OMUa board are permanently configured in RSS.

- SPUa can be configured both in RSS and RBS.

- DPUa can be configured both in RSS and RBS.

- RINT can be configured both in RSS and RBS.

RSR content



- One RSS and zero to two RBSs

RBR content

- One to Three RBSs

Minimum Configuration

The minimum configuration diagram is shown as below:

Maximum Configuration

The maximum configuration diagram is shown as below:

RSS

RSR

Empty

Empty

RBS

RBR

RBS

RBS

RSS

RSR

RBS

RBS



3.3 Function Upgrade

The HSDPA Ph4 (DL 14.4Mbps per user) and HSUPA Ph2 (UL 5.76Mbps per user) are supported

in Huawei UMTS RAN10.0 release, and the dependency on hardware are as below.

Board WFMRb WFMRc

HSDPA Ph4 Not support Support

HSUPA Ph2 Support Support

3.3.1 HSDPA upgrade

HSDPA phase 4 is supported in RAN10.0. The BSC6800 in RAN6.0 and BSC6810 in RAN6.1 are

all hardware ready to for HSDPA phase 4. Therefore, no additional hardware is required to

support HSDPA phase 4.

3.3.2 HSUPA upgrade

HSUPA phase 2 is supported in RAN10.0. The BSC6800 in RAN6.0 and BSC6810 in RAN6.1 are

all hardware ready for HSUPA phase 2. Therefore, no additional hardware is required to support

HSUPA phase 2.

3.3.3 IP Upgrade

In RAN10.0, all IP transmission, that is Iub/Iu/Iur over IP, is supported.

BSC6800

1) Iub over IP Upgrade

The IP interface board for the Iub interface is needed. WEIE is needed to be configured in each

WRBS to support IP over E1 and WFIE board is needed to be configured in each WRBS to

support IP over Ethernet.

2) Iu/Iur over IP Upgrade

The BSC6800V100R010 supports Iu/Iur interfaces based on IP over Ethernet transmission mode

by using the built-in interface board (WFIE) and the convergence through the LAN switch solution.

Each WRBS must be configured with WFIEs and the FE ports of WFIEs are converged to GE port

through LAN switch.

There is no new IP interface board is introduced in V100R010 (RAN10.0), and the smooth



evolution to Iu/Iur IP solution is supported with WFIE board as below.

1. Iu/Iur IP can only be supported with WFIE board.

2. Each WRBS should be configured with WFIE board in slt 1 and 14. In RAN10.0, only 8 WFMRb

boards or 4 WFMRc boards are needed instead of 10 WFMRb boards in RAN6.0 and the capacity

is not affected, therefore, slot 1 and 14 can be configured with WFIE board.

3. If WRBS has already been configured with WFIE board in slot 1 or slot 15 which used for Iub

interface, no additional WFIE board is needed, and the existing WFIE board can process the Iu/Iu

r IP traffic as well as Iub IP traffic without capacity downgraded.

4. The lanswitch in the switching cabinet is used to concentrate the Iu IP traffic distributed in each

WRBS, and provides GE optical/electrical port to CN nodes.

BSC6810

The BSC6810 is hardware and software ready for Iub/Iu/Iur over IP.

Compared with BSC6810V200R009 in RAN6.1, IP over E1/T1 over SDH (CPOS) and IP over

SDH (POS) are added in RAN10.0 for BSC6810V200R010.

The CPOS is supported by interface board POUa, the new interface board provided

since RAN10.0. That means, when upgrade from RAN6.1 to RAN10.0 to support

CPOS, new interface board POUa is required.

The POS is supported by interface board UOIa, the interface board provided since

RAN6.1. That means only software upgrade from RAN6.1 to RAN10.0 is needed to

support POS.

3.3.4 Other Functional Upgrades

The Supplier does not foresee any functional requirements that require hardware upgrade to the

RNC except those noted in previous sections.



3.4 RNC interface Dimensioning

3.4.1 Iub Dimensioning

Please refer to 2.7 and 2.8

3.4.2 Iur Interface Dimensioning (RNC RNC)

Usually we calculate the throughput based on Iub interface throughput as shown in following figure:

Iur Interface Throughput/RNC = 10% * Iub interface Throughput / RNC.

Notes:

Iur interface throughput is estimated to be 10% of Iub interface throughput.

3.4.3 Iu-CS Interface Dimensioning (RNC MGW)

Iu-CS interface is the bridge between UTRAN and CN CS domain. This interface is used to transfer data flow in both control plane and user plane of CN CS domain. Iu-CS interface protocol stack (ATM) can be illustrated in following figure:

Iu-CS Interface Protocol Stack (ATM)

Iu-CS interface data flow in user plane is separated into CS Voice and CS Data. Usually we only need to calculate 12.2kbps service in CS Voice and 64kbps in CS Data. The usage factors in different stack layers are listed in following table:

Necessary Traffic Parameters on Iub Interface under ATM

Unit Value* Network Parameter CS Voice CS Data

Service Bit Rate 12.2kbps 64kbps IUUP usage factor 88.57% 90.91% AAL2 usage factor 90.19% 91.67%



ATM usage factor 90.6% 90.6% subtotal of protocol usage factor 72.37% 75.50% Extension Ratio 1.38 1.32

Notes

Subtotal of usage factor = IUUP usage factor * AAL2 usage factor * ATM usage factor.

Extension Ratio = 1/Usage factor

Iu-CS interface protocol stack (IP over Ethernet) can be illustrated in following figure:

Iu-CS Interface Protocol Stack (IP over Ethernet)

Necessary Traffic Parameters on Iub Interface under IP over Ethernet

Unit Value* Network Parameter CS Voice CS Data

Service Bit Rate 12.2kbps 64kbps IUUP usage factor 88.57% 90.91% MAC usage factor 43% 69.3% subtotal of protocol usage factor 38% 63% Extension Ratio 2.63 1.44

Because Huawei RNC does not support IP transmission of Iu interface until 07Q2, the related dimension workshop is not suggested. Only the protocol stack and overhead ratio are provided for reference.

For the convenience of dimensioning on Iu-CS interface, the throughput on Iu-CS interface can be divided into different branches and calculated one by one as shown in following figure:



Composition of Iu-CS Interface Throughput

Following factors are required to be taken into consideration on Iu-CS interface Dimensioning:

1. Signalling overhead in control plane

2. Protocol overhead in user plane which include IUUP overhead, AAL2 overhead and ATM cell overhead

Iu-CS interface dimensioning in user plane can be illustrated in following figure:

Iu-CS Interface Dimensioning (ATM) in User Plane

Usually we estimate the throughput of signaling on Iu-CS interface to be 1-2% of the throughput of its user plane, so total throughput of Iu-CS interface can be illustrated in following figure:



Total Throughput on Iu-CS Interface (ATM)

3.4.4 Iu-PS Interface Dimensioning (RNC SGSN)

Iu-PS interface is the bridge between UTRAN and CN PS. This interface is used to transfer data flow in both control plane and user plane of CN PS.

The protocol stack and overhead in Iu-PS interface under ATM can be illustrated in following figure:

Protocol Stack and Overhead on Iu-PS Interface under ATM

The protocol stack and overhead in Iu-PS interface under IP over Ethernet can be



illustrated in following figure:

GTP-U

MACPHY

Service Bit Rate

Bit Rate under IP over E1/T1

UDPIP

Payload (Bytes)

56Total

18MAC

20IP

8UDP

8GTP-U

Payload (Bytes)

56Total

18MAC

20IP

8UDP

8GTP-U

Assume: GTP packet length is X bytes

Extension Ratio (ER) = (X + 56)/X

Protocol Stack and Overhead on Iu-PS Interface under IP over Ethernet

Because Huawei RNC does not support IP transmission of Iu interface until 07Q2, the related dimension workshop is not suggested. Only the protocol stack and overhead ratio are provided for reference.

The throughput on Iu-PS interface can be divided into two parts that are throughput of control plane and throughput of user plane as shown in following figure:

Composition of Iu-PS Interface

The dimensioning of throughput on Iu-PS interface should consider following factors:

1. Signalling overhead in control plane

2. Protocol overhead in user plane

3. Packet size

4. Peak ratio

The throughput of user plane can be calculated as shown in following figures:



Throughput Dimensioning of Iu-PS Interface (ATM) in User Plane

Throughput Dimensioning of Iu-PS Interface (ATM) in User Plane (Continued)

To calculate throughput of Iu-PS interface in control plane, we need to introduce the messages transferred in Iu-PS control plane. The signalling messages in Iu-PS control plane are shown in following figure:



Signalling Messages in Iu-PS Interface Control Plane

We can calculate throughput in Iu-PS control plane as shown in following table:

Throughput Dimensioning of Iu-PS Control Plane

Iu-PS Signalling Procedures

Traffic Model

(Trans per

Att. Sub./BH)

Message

Length

(Bytes)

Bytes/BH/Sub.

Attach 0.75 424 318

Detach 0.75 159 119.25

Service Request 2.7 159 429.3

PDP Context Activation 1.5 424 636

PDP Context Deactivation 1.5 265 397.5

PDP Context Modification 0.15 424 63.6

Iu Release 2.94 106 311.64

Routing Area Update 1.1 265 291.5

Paging 1.4 106 148.4

Total (Bytes) 2715.19

Iu-PS interface signalling throughput (bps) 6.03

Usually to simplify the dimensioning process, the throughput of Iu-PS control plane is estimated to be 1-2% of the throughput on Iu-PS user plane, so total throughput on Iu-PS interface is:



Total Throughput on Iu-PS Interface



4 UTRAN OMC

4.1 Complete architecture of the O&M solution

4.1.1 Physical architecture

A typical M2000 system includes:

Server(s)

Client(s)

Alarm box(es)

Other networking devices

Using a dial-up server, you can operate and maintain the M2000 system

through the Public Switched Telephone Network (PSTN).

The physical architecture of M2000 single server system is illustrated below.



Alarm box Client 1 Dial-up server

Server

PSTN

Client 2

4.2 O&M solution dimensioning rules

The typical computers for the M2000 server are Sun Netra 240, Sun Fire

V890, or Sun Fire E4900.

4.2.1 System capacity of M2000

For M2000V200R007, the capacity of M2000 differs from different M2000

Server. The system capacity of M2000 for different M2000 server types is

listed as below.

Configuration Management capacity Server hardware

OMC Type 1 900 cells (18 equivalent NEs) 1 server Sun Netra 240 (2 CPUs)

OMC Type 2 2500 cells (50 equivalent NEs) 1 server Sun Fire V890 (2 CPUs)

OMC Type 3 4500 cells (90 equivalent NEs) 1 server Sun Fire V890 (4 CPUs)

OMC Type 4 5500 cells (110 equivalent

NEs)

1 server Sun Fire E4900 (4 CPUs)

OMC Type 5 8500 cells (170 equivalent

NEs)

1 server Sun Fire V890 (8 CPUs)

OMC Type 6 10000 cells(200 equivalent

NEs)

1 server Sun Fire E4900 (8 CPUs)



Configuration Management capacity Server hardware

OMC Type 7 12500 cells(250 equivalent

NEs)

1 server Sun Fire E4900 (12

CPUs)

Notes: for RNC + NodeB, 50 cell is considered as 1 equivalent NE.It is based on the common performance counter measurement with period of half an hour.

4.2.2 Bandwidth

The bandwidth requirement between the M2000 and managed RNCs and NodeBs (Each Node B covers three cells.) is listed below.

Bandwidth requirement (kbit/s) Number of

NodeBs RNC

100 384

200 512

400 768

600 832

800 1024

1000 1152

4.2.3 Performance Data Storage Capacity

M2000 system stores the performance data of all the NEs for at least one

month. The number of the NEs that are managed and the performance data

that is stored vary based on the server model.

The details are as follows:

Configuration Level Sever Configuration Performance Database

Space(MB)

Netra240（2*73G HD) 10,000 Middle configuration

Netra240（2*146G HD) 25,000



V890 SE3320（8*73G HD） 92,160 Large configuration

V890 SE6140（16*146G HD） 286,720

E4900 SE6140（14*73G HD） 153,600 Super configuration

E4900 SE6140（16*146G HD） 286,720

4.2.4 Performance Data Processing Capacity

The number of managed NEs and the data processing capability vary based

on the server model. The processing capability of various servers is listed

below.

Server model Performance data processing (counter/hour)

Sun Netra 240 (2 CPUs) 1.26 million

Sun Fire V890 (2 CPUs) 4.68 million

Sun Fire V890 (4 CPUs) 9 million

Sun Fire E4900 (4 CPUs) 12.6 million

Sun Fire V890 (8 CPUs) 17.28 million

Sun Fire E4900 (8 CPUs) 21.6 million

Sun Fire E4900 (12 CPUs) 27 million

4.2.5 Alarm Data Storage Capacity

The M2000 system classifies alarms into the following categories:

Current fault alarms Current fault alarms are generated when faults occur in the system. When the faults are cleared and the system recovers, the corresponding fault alarms are labeled as cleared.

Event alarms Event alarms report the current status of the system during the system operation.

History fault alarms History fault alarms refer to the current fault alarms known and acknowledged, and labeled as cleared.



Shielded alarms Operator can shield alarms as required. The shielded alarms are not displayed on the client.

The M2000 stores the alarms for at least three months. The number of

managed NEs and the storage capacity depend on the server model.

Server

hardware

Event alarm History fault

alarm

Current fault

alarm

Shielded

alarm

Sun Netra240 800 000 800 000 100 000 100 000

Sun Fire V890 5 000 000 5 000 000 600 000 600 000

Sun Fire

E4900

7 000 000 7 000 000 800 000 800 000

4.2.6 Alarm Processing Capacity

Generally, M2000 client displays an alarm about five or six seconds after the

alarm is generated.

The hardware configuration of M2000 server determines the 5-minute-long

peak alarm-handling capacity. The alarm processing capability of various

servers is listed below.

Server Peak alarm processing capacity (record/second)

Sun Netra 240 (2 CPUs) 20

Sun Fire V890 (2 CPUs) 30


Sun Fire E4900 (4 CPUs) 55






4.2.7 Number of Clients Simultaneously Started on the Server

The number of clients that can be started simultaneously on the server varies

based on the server model.

Server configuration Number of clients

Sun Netra 240 25




Sun Fire V890(8 CPUs) 60



4.3 O&M hardware and software configuration

4.3.1 Typical M2000 Server Configuration

The typical computers for the M2000 server are Sun Netra 240, Sun Fire

V890, or Sun Fire E4900. The selection of the computer for an M2000 server

depends on the number of NEs in the network (See ¡System capacity of

M2000¡).

The typical server configuration of M2000 single server system is listed

below.

Sun Netra 240 Sun Fire V890 Sun Fire E4900

Number of

CPUs

2 2 4 8 4 8 12

Main

Frequency

of the CPU

1.5 1.8 1.8 1.8 1.8 1.8 1.8



Sun Netra 240 Sun Fire V890 Sun Fire E4900

(GHz)

Memory

(GB)

4 8 16 32 16 32 48

Hard disk

(GB)

2 x 146 6 x 146 2 x 146

Disk array

(GB)

None 1 x 6140

(A 6140 disk array consists

of sixteen 146 GB hard

disks.)

1 x 6140

(A 6140 disk array

consists of sixteen 146 GB

hard disks)

Accessorie

s

DVD/Ethernet

adapter/DATA

72 tape

drive/English

documentation

DVD/Ethernet

adapter/DATA72 tape

drive/English

documentation

DVD/Ethernet

adapter/DATA72 tape

drive/English

documentation

Operating

system

Solaris 10

/English

documentation

Solaris 10 /English

documentation

Solaris 10 /English

documentation

Database Sybase 15.0

/English

documentation

Sybase 15.0 /English

documentation

Sybase 15.0 /English

documentation

Application

software

M2000 server

application

software

M2000 server application

software

M2000 server application

software

4.3.2 Common Networking Equipment

The common networking equipments used in the M2000 system are listed

below.



Item Configuration

Router

Quidway AR46-40

Quidway R28-10

Quidway R28-10

Switch and Hub Quidway S3928P-EI

Quidway S2016HI

Timeslot cross multiplexer Mercury 3600

4.3.3 Typical M2000 Client Configuration

M2000 client runs on Windows 2000. The recommended PC configuration for

M2000 client is listed below.

Item Configuration

CPU P4/2.8 GHz

Memory 512 MB

Hard disk 80 GB

Accessories CDROM/Floppy Drive/Ethernet Adapter/Sound

Card/17¡ LCD Display

Operating system Windows 2000 professional SP02 (or a later version)

Application

software M2000 client application software

huawei umts ran10 0 dimensioning rules v1.2

Documents