huawei umts ran12.0 dimensioning rules v1.0

7/24/2019 Huawei UMTS RAN12.0 Dimensioning Rules V1.0

1/77

Huawei UMTS RAN12.0

Dimensioning Rules

Issue V1.0

Date 2009-12-28

HUAWEI TECHNOLOGIES CO., LTD.


2/77

Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without priorwritten consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respectiveholders.

Notice

The purchased products, services, and features are stipulated by the commercial contract made between

Huawei and the customer. All or partial products, services, and features described in this document may not

be within the purchased scope or the usage scope. Unless otherwise agreed by the contract, all statements,

information, and recommendations in this document are provided AS IS without warranties, guarantees orrepresentations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents; but all statements, information, and

recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial BaseBantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]


3/77

Huawei UMTS RAN12.0 Dimensioning Rules

Issue V1.0 (2009-12-28)Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.Page 3 of 77

Contents

1 Introduction....................................................................................................................................4

2 NodeB..............................................................................................................................................5

2.1 NodeB V100R012.......................................................... ........................................................... ....................... 5

2.2 NodeB V200R012.......................................................... ........................................................... ..................... 21

2.3 UMTS Capacity Dimensioning Procedure................................................... .................................................. 34

2.4 UMTS CE Dimensioning Procedure............................................................ .................................................. 44

2.5 UMTS Iub Dimensioning Procedure.................... ........................................................... ............................... 51

2.6 Counters Related to Capacity................................................... ........................................................... ........... 57

3 RNC................................................................................................................................................59

3.1 Configurations standards of BSC6800 ......................................................... .................................................. 59

3.2 Configurations standards of BSC6900 ......................................................... .................................................. 62

3.3 RNC Interface Dimensioning............................................................. ........................................................... . 66

3.4 Counters Related to Capacity................................................... ........................................................... ........... 70

4 UTRAN OMC ..............................................................................................................................72

4.1 Complete architecture of the O&M solution .......................................................... ........................................ 724.2 O&M solution dimensioning rules ..................................................... ........................................................... . 73

4.3 O&M hardware and software configuration................................................. .................................................. 75


4/77




1 IntroductionThis document is to introduce the Dimensioning rules for Huaweis RAN product includingNodeB (Macro and DNBS) and RNC. It is based on release RAN12.0 including theintroduction of capacity of baseband board and transmission of NodeB, the traffic processing

capability of RNC and interface capability (Iub, Iur, Iu-CS and Iu-PS).


5/77




2 NodeBRAN12.0 includes two NodeB versions: NodeB V100R012 and NodeB V200R012.

NodeB V100R012 includes BTS3812E, BTS3812AE and DBS3800 products.

NodeB V200R012 includes BTS3900, BTS3900A and DBS3900 products.

2.1 NodeB V100R012

2.1.1 BTS3812E/BTS3812AE Basic Module ConfigurationThe BTS3812E/BTS3812AE has the following subsystems:

Transport SubsystemBaseband SubsystemRF SubsystemControl SubsystemAntenna SubsystemPower Subsystem (BTS3812AE Only)Environment Monitoring Subsystem (BTS3812AE Only)


6/77




Figure 2-1Logical structure of the BTS3812E/BTS3812AE

The BTS3812E/BTS3812AE supports smooth evolution to subsequent 3GPP protocols, which can be configured

with different boards and modules to support future capacity expansion and evolution.

In BTS3812E/BTS3812AE V100R010, the EBBI, EBOI, EULP, and WRFU are added.

In BTS3812E/BTS3812AE V100R011, the EDLP is added.

In BTS3812E/BTS3812AE V100R012, the EULPd is added.

Transport Unit Configurations

The transport unit consists of Iub interface boards, such as NUTIs or NDTIs.

The Iub interface boards can be positioned in slots 12 to 15, as shown in Figure 2-2. One

BTS3812E/BTS3812AE can be configured with a maximum of four Iub interface boards. Slots 12 and 13 can be

configured with NUTIs or NDTIs. Slots 14 and 15 can be configured with only NUTIs that are cabled from the

front of the subrack.

Figure 2-2Boards in the BTS3812E/BTS3812AE baseband subrack

Table 2-1BTS3812E/BTS3812AE Iub interface boards Specification

Board type E1 forATM

E1 forIP

FE

electrical

unchannelized STM-1

ChannelizedSTM-1

NDTI 8

NUTI 8 2

NUTI with E1 sub

board16 2

NUTI with un-

channelized STM-1 sub

board

8 2 2

NUTI with channelized

STM-1 sub board8 2 1


7/77




Baseband Unit Configurations

The baseband unit consists of the HULP or EULP or EULPd, HDLP or EDLP, and HBBI/EBBI/HBOI/EBOI.

The baseband subsystem processes digital baseband signals. Figure 2-2 shows the positions of the HULP or

EULP or EULPd, HDLP or EDLP, and HBBI/EBBI/HBOI/EBOI in the baseband subrack.

In V100R010, the EBBI, EBOI and EULP are supported.

In V100R011, the EDLP is added.

In V100R012, the EULPd is added.

The boards in the baseband subrack are described as follows:

The HBBI/HBOI can Process uplink and downlink baseband signals. Support HSDPA, and support for

HSUPA phase1 (10 ms TTI).

The EBBI/EBOI can Process uplink and downlink baseband signals. Support HSDPA and HSPA+ downlink

feature, and support for HSUPA phase2 (2 ms TTI).

The EDLP can Process downlink baseband signals. Support HSDPA and HSPA+ feature.

The EULP can Process uplink baseband signals, support for HSUPA phase2 (2 ms TTI).

The EULPd can Process uplink baseband signals. Support HSPA+ UL 16QAM, IC (Interference

Cancellation) feature and FDE (Frequency Domain Equalization) feature.

The HBOI or EBOI has the same function as the HBBI or EBBI. The HBOI or EBOI is configured only

when the macro NodeB is connected to the RRU. The HBOI or EBOI and the HBBI or EBBI share slots 0

and 1. One Board provides 3 CPRI interfaces.

When the NodeB is configured with more than six cells, the resource pool for processing uplink baseband

signals is split into several resource groups. Each resource group can process data for a maximum of six

cells. Each cell belongs to only one uplink resource group at a time.

Table 2-2BTS3812E/BTS3812AE Baseband boards Specification

Board Type Cell

Uplink

R99/HSUPA CE

Downlink

R99 CE

HSDPA

Capacity Feature Support

HBBI 3 cells 128CE 256CE 45 codes

HULP 3 cells 128CE 0 0

HDLP 6 cells 0 384CE 90 codes

HSDPA

HSUPA 10ms TTI

EBBI/EBOI 6 cells 384CE 384CE 90 codesEDLP 6 cells 0 512CE 90 codes

EULP 6 cells 384CE 0 0

HSUPA 2msHSPA+ DL 64QAM

HSPA+DL MIMO

HSPA+ DL DC-HSDPA

EULPd 6 cells 384CE 0 0 HSPA+ UL 16QAM

IC

FDE


8/77




RF Unit Configurations

The RF unit consists of MTRUs and MAFUs. The MTRU subrack houses the MTRUs and the MAFU subrack

houses the MAFUs. A pair of MTRU and MAFU processes the signals of two carriers over one TX channel and

two RX channels.

In RAN10.0, Huawei provides WRFU integrating MTRU and MAFU into one unit.

Figure 2-3Boards in the BTS3812E/BTS3812AE RF subrack

RF Unit Output power carriers

MTRU 40W 2

WRFU 80W 4

Table 2-3BTS3812E/BTS3812AE RF Unit Specification

Control Unit Configurations

The control unit consists of the NMPT and NMON. The control subsystem controls and manages the entire

NodeB system. Figure 2-2 shows the positions of the NMPT and NMON in the baseband subrack.

2.1.2 BTS3812E/BTS312AE Typical Configuration

Figure 2-4 shows the BTS3812E in full configuration.


9/77




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

(4) Busbar (5) Baseband subrack

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

The BTS3812E has the following configuration features:

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

A single BTS3812E 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 supports a smooth capacity expansion from 1 x 1 to 6 x 2 or 3 x 4. The capacity of the modular BTS3812E 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 capacityrequirement increasing, you can smoothly upgrade the system to large-capacity configurationssuch as 3 x 2 and 3 x 4.

Any combination of the two frequency bands (850 MHz, 900 MHz, 1800 MHz, 1900 MHz, and2100 MHz) can be supported in one NodeB. The NodeB with shared baseband boards onlyrequires RF modules at different bands.

Table 2-4Recommended configurations of the BTS3812E

configuration MTRU MAFU NMPT NUTI NMON EBBI

1 x 1 1 1 1 1 1 1

2 x 1 2 2 1 1 1 1


10/77




2 x 2 2 2 1 1 1 1

3 x 1 3 3 1 1 1 1

3 x 2 3 3 1 1 1 1

3 x 3 6 6 1 1 1 2

3 x 4 6 6 1 1 1 2

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

Figure 2-5The S111, S222 and S333 configurations

Figure2-6 shows the BTS3812AE in full configuration.


11/77


12/77




3 x 3 6 6 1 1 1 2 3

3 x 4 6 6 1 1 1 2 3

2.1.3 BTS3812E/BTS312AE Feature Upgrade ConfigurationsThe hardware listed in the table is the basic hardware, and the software listed is the software influenced by the

capacity expansion or introduction of new features.

Upgrade to HSUPA 2ms TTI

Table 2-6Upgrade to HSUPA 2ms TTI (3 x 1 configuration, 20 W per carrier)

Basic Hardware/Software Original Configuration Additional Configuration

Transport Interface Unit 1NUTI 0

Baseband Processing Unit 1HBBI 1EBBI

RF Module 3MTRU+3MAFU 0

WCDMA Main Control Unit 1NMPT+1NMON 0

HSUPA Introduction Package (per NodeB) 1 0

HSUPA Phase2 (per NodeB) 0 1

Upgrade to HSPA+ 64QAM

Table 2-7Upgrade to HSPA+ 64QAM (3 x 2 configuration, 20 W per carrier)



Baseband Processing Unit 1HBBI+1EBBI 0



DL 64QAM Function (per Cell) 0 6

The Baseband Processing Unit (6Cell) supports six cells in the downlink and thus supports six64QAM cells.

Upgrade to HSPA+ MIMO

Table 2-8Upgrade to HSPA+ MIMO (10W+10W/C) (3 x 2 configuration)




13/77




Baseband Processing Unit 1HBBI+1 EBBI 1EBBI

RF Module 3MTRU+3MAFU 3MTRU+3MAFU


2*2 MIMO Function (per Cell) 0 6

Table 2-9Upgrade to HSPA+ MIMO (10W+10W/C) (3 x 2 configuration, WRFU)



Baseband Processing Unit 1HBBI+1EBBI 1EBBI

RF Module 3MTRU+3MAFU 3WRFU



In MIMO mode, both the Baseband Processing Unit (6Cell) and the Baseband Processing Unit(3Cell) support MIMO on a maximum of three cells.

Upgrade to DC-HSDPA

Table 2-10Upgrade from 64QAM to DC-HSDPA+64QAM (3 x 2 configuration, 20 W per carrier)



Baseband Processing Unit 1HBBI+1EBBI 0




DC-HSDPA Function 0 6

Upgrade to UL 16QAM

Table 2-11Upgrade from HSUPA phase2 (20W/C) to UL 16QAM (3 x 2 configuration)



Baseband Processing Unit 1HBBI+1EBBI 1EULPd



14/77






UL 16QAM Function 0 6

Upgrade to IC

Table 2-12Upgrade from HSUPA phase2 (20W/C) to IC (3 x 2 configuration)






IC Function 0 6

Upgrade to FDE

Table 2-13Upgrade from HSPA (20W/C) to FDE (3 x 2 configuration)






FDE Function 0 6

Upgrade to DL 64QAM+MIMO

Table 2-14Upgrade from DL 64QAM(20W/C) to DL 64QAM+MIMO (10W+10W/C) (3 x 2configuration)



Baseband Processing Unit 1HBBI+1EBBI 1EDLP

RF Module 3MTRU+3MAFU 3MTRU+3MAFU



15/77






DL 64QAM+MIMO Function 0 6

Table 2-15Upgrade from DL 64QAM(20W/C) to DL 64QAM+MIMO (10W+10W/C) (3 x 2configuration, WRFU)



Baseband Processing Unit 1HBBI+1EBBI 1EDLP

RF Module 3MTRU+3MAFU 3WRFU





2.1.4 DBS3800 Basic Module ConfigurationThe DBS3800, a distributed NodeB, consists of the BBU3806 and RRU.

The BBU3806 is a 19-inch box, which can be configured with an Enhanced Baseband Card (EBBC) or an

extended transmission card. The extended card cannot be used independently. It must be installed on the

BBU3806 and work with the BBU3806.


16/77




Figure 2-7Function modules of the DBS3800

Table 2-16Function modules of the DBS3800

Function Module Description

BBU3806 Indoor baseband unit that processes baseband signals

BBU3806C Outdoor baseband unit that processes baseband signals

RRU3801C Remote radio unit. 2 carriers, 40W output power

RRU3804 Remote radio unit. 4 carriers, 60W output power

RRU3801E Remote radio unit. 2 carriers, 40W output power

RRU3808 Remote radio unit. 4 carriers, 2*40W output power

The BBU3806/BBU3806C consists of the transport subsystem, baseband subsystem, control subsystem, interface

module and power module.

The RRU consists of the interface module, TRX, Power Amplifier (PA), filter, Low Noise Amplifier (LNA),

extension interface and power module.


The transport unit consists of BBU3806 and extension Transmission Card (UBTI).

The optical sub-board is an extension plugboard for the BBU3806, which share the slot with extension baseband

Card.

Table 2-17DBS3800 Iub interface boards Specification

Board type E1 for ATM E1 for IP FE

electrical

unchannelized STM-1

BBU3806 8 2

UBTI 2


The Baseband unit consists of BBU3806 and extension baseband Card (EBBC or EBBCd).

The EBBC or EBBCd is an extension plugboard for the BBU3806, which share the slot with extension

Transmission Card.

In V100R010, the EBBC are supported. It supports HSUPA 2ms TTI feature.

In V100R012, the EBBCd is added. It supports HSPA+ UL 16QAM, IC (Interference Cancellation) feature and

FDE (Frequency Domain Equalization) feature.

The DBS3800 can be configured with one or two BBUs. A maximum of three RRUs can be connected to one

BBU.


17/77




Table 2-18DBS3800 Baseband boards Specification

Board Type Cell

UplinkR99/HSUPA

DownlinkR99 CE

HSDPACapacity Feature Support

BBU3806 3 cells 192CE(When BBU active

HSUPA, 128CE)

256CE 45 codes HSDPA

HSUPA 10ms TTI

BBU3806+EBBC 6 cells 384CE

(When BBU active

HSUPA, 320CE)

512CE 90 codes HSUPA 2ms

HSPA+ DL 64QAM

HSPA+DL MIMO

HSPA+ DL DC-HSDPA

BBU3806+EBBCd 6 cells 384CE

(When BBU active

HSUPA, 320CE)

512CE 90 codes HSPA+ UL 16QAM

IC

FDE

RF Unit Configurations

The RRU is classified into the RRU3804, RRU3801C, RRU3801E, and RRU3808 based on different output

power and processing capabilities. The RRU3808 supports two RX channels and two TX channels.

DBS3800 support RRU3808 in V100R011.

Table 2-19DBS3800 RRU Specification

RRU Type RRU3804 RRU3801C RRU3801E RRU3808

Maximum OutputPower 60W 40W 40W 2*40W

Number of

Supported Carriers 4 2 2 4

One RRU3801C/RRU3801E can support 2 contiguous carriers. DBS3800 can support smooth capacity

expansion from 1 x 1 to 1 x 2 without adding RF module. Two RRU3801Cs/RRU3801Es in parallel

connection within one sector can support the 1 x 4 configuration.

One RRU3804 can support 4 contiguous carriers. With 20W per carrier configuration, it can support 3 non

contiguous carriers (for example 1101, 1011), which is applicable to RAN sharing with 2 operators has non

contiguous carriers.

The RRU3808 supports 2T2R with two TX channels. The maximum radio output power per channel is 40 W.

One RRU3808 can support 4 carriers within 60M frequency bandwidth, per carrier 20W.

For MIMO, transmit diversity configuration, two RRU3804s/RRU3801Cs /RRU3801Es should be

configured within one sector, or one RRU3808 should be configured within one sector.

For 4-way receive diversity configuration, two RRUs should be configured within one sector.

2.1.5 DBS3800 Typical ConfigurationThe DBS3800 supports up to 12 cells, 768 CEs in the uplink, and 1,024 CEs in the downlink. The DBS3800

supports configurations of one, two, three, or six sectors. It also supports a smooth capacity expansion from 1 x 1

to 6 x 2 or 3 x 4. The following table lists the typical configurations for the variable capacities of the equipment.


18/77




Table 2-20Configuration of the DBS3800 configured with 40 W RRU (not supporting HSUPAphase 2 and HSPA+)

20 W per Carrier Minimum Number

of BBU3806s

Minimum Number

of EBBCs

Minimum Number

of 40 W RRUs

1 x 1 1 0 1

2 x 1 1 0 2

2 x 2 2 0 2

3 x 1 1 0 3

3 x 2 2 0 3

3 x 3 2 1 6

3 x 4 2 2 6

Table 2-21Configuration of the DBS3800 configured with 60 W RRU (not supporting HSUPAphase 2 and HSPA+)

20 W per Carrier Minimum Number

of BBU3806s

Minimum Number

of EBBCs

Minimum Number

of 60 W RRUs

1 x 1 1 0 1

2 x 1 1 0 2

2 x 2 2 0 2

3 x 1 1 0 3

3 x 2 2 0 3

3 x 3 2 1 3

3 x 4 2 2 6

2.1.6 DBS3800 Feature Upgrade Configurations

Upgrade to HSUPA 2ms TTI

Table 2-22Upgrade to HSUPA 2ms TTI (3 x 1 configuration, 20 W per carrier)


BBU Unit 1BBU3806 1EBBC

RF Module 3RRU3801C 0

HSUPA Introduction Package (per NodeB) 1 0

HSUPA Phase2 (per NodeB) 0 1


19/77


20/77




Upgrade to UL 16QAM



BBU Unit 2BBU3806 1EBBCd



Upgrade to IC





IC Function 0 6

Upgrade to FDE





FDE Function 0 6




BBU Unit 2BBU3806+1EBBC 1EBBC

RF Module 3RRU3801C 3RRU3804 or RRU3801E





21/77




Table 2-31Upgrade from DL 64QAM(20W/C) to DL 64QAM+MIMO (10W+10W/C) (3 x 2configuration, RRU3808)


BBU Unit 2BBU3806+1EBBC 1EBBC

RF Module 3RRU3801C 3RRU3808 swap 3RRU3801C




2.2 NodeB V200R012The 3900 series NodeB 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.


22/77




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

Figure 2-9Application scenarios of the 3900 series NodeBs

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

Cabinet macro NodeB


23/77




The cabinet macro NodeB, integrating the BBU3900 and the WRFU, consists of the indoor BTS3900 andthe outdoor BTS3900A. The cabinet macro NodeB applies to centralized installation, where the BTS3900

and the BTS3900A, as mentioned above, are recommended for indoor application and outdoor application

respectively.

Distributed NodeB

The distributed NodeB, known as the DBS3900, consists of the BBU3900 and the RRU. For the distributedinstallation, the RRU is placed close to the antenna. This can reduce feeder loss and improve NodeB

performance.

Compact mini NodeB

The compact mini NodeB is also of two types, which is applies to the new outdoor 3G sites where noequipment room exists, hot spots, marginal networks, and blind spots such as tunnels.

2.2.1 3900 Series NodeB Basic Module Configuration

The 3900 series NodeB consists of the BBU3900 and RF unit (RRU or WRFU).

The BBU3900 is an indoor base band unit. The maximum is 1 BBU3900 in one NodeB. It is used for all

3900 series WCDMA NodeB 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. Ithas 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 unitand universal BBU fan unit. Theseunits are plug in a backplane of the subrack.

The BBU3900 also provides 8 slots for WMPT, UTRP, WBBP, UELPandUFLP. Every slot of BBU subracksupports to plug in several kinds of board flexibly.

Figure 2-10Structure of the BBU3900 Subrack

Table 2-32The board supported in the slots

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

WMPT available available


24/77




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.

Control Unit Configurations

The WMPT integrated the control and transport subsystem manages the entire NodeB 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 NodeB, 2 WMPT can provide 8E1 and 2 electrical FE and 2 optical FE interfaces.


One BBU3900 can plug in 4 UTRP maximally for NodeB.

In V200R010, the UTRP3, UTRP4 and UTRP6 are supported.

In V200R011, the UTRP9 and UTRP2 are added.

Table 2-33Transmission Card Specification

TypeE1forATM

E1 forIP

FEelectrical

FEoptical

unchannelizedSTM-1

FE/GEelectrical

FE/GEOptical

WMPT 4 1 1

UTRP3 8

UTRP4 0 8

UTRP6 1

UTRP9 4

UTRP2 2


The 3900 series NodeB supports smooth evolution to subsequent 3GPP protocols, which can be configured withdifferent boards and modules to support future capacity expansion and evolution.

In V200R010, the WBBPa and WBBPb are supported.

In V200R012, the WBBPd is added.

The WBBPa can Process uplink and downlink baseband signals. Support HSDPA (2 ms TTI), and support

for HSUPA phase1 (10 ms TTI).

The WBBPb can Process uplink and downlink baseband signals. Support HSDPA (2 ms TTI), and support

for HSUPA phase2 (2 ms TTI).

The WBBPd can Process uplink and downlink baseband signals. Support HSPA+ UL 16QAM, IC

(Interference Cancellation) feature and FDE (Frequency Domain Equalization) feature.


25/77




One WBBPa or WBBPb provides 3 CPRI interfaces. One WBBPd provides 6 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.

Table 2-34Baseband Card Specification

Board

Type Cell

Uplink

R99/HSUP

A CE

Downlink

R99 CE

HSDPA

Capacity Feature Support

WBBPa 3 cells 128 256 45 codesHSDPAHSUPA 10ms TTI

WBBPb1 3 cells 64 64 45 codes




HSUPA 2ms

HSPA+ DL 64QAMHSPA+DL MIMOHSPA+ DL DC-HSDPA

WBBPd1 6 cells 192 192 90 codes

WBBPd2 6 cells 384 384 90 codes

HSPA+ UL 16QAMICFDE

In the case of 2 x 2 MIMO, TX Diversity or 4-way RX diversity configurations , the WBBPthat originally support six cells can support only three cells; the processing capabilities of the

WBBP that support three cells remain unchanged.

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 BBcapacity for R99 services.

Capacity expansion. NodeB 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 beimplemented separately. The step of license expansion is 16 CEs according to the customers

Lighting Protection Unit Configurations

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.

RF Unit Configurations (WRFU)

For cabinet NodeBBTS3900 and BTS3900A, the RF module is WRFU.

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


26/77




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.

One 80W WRFU can support 4 contiguous carriers in 1 sector and it also can support non contiguous carriers(for example 1101, 1011, 1001, 1010, 1100), which can be applicable to RAN sharing with 2 operators has non

contiguous carriers.

For MIMO, transmit diversity or 4-way receive diversity configuration, two WRFUs should be configured within

one sector.

RF Unit Configurations (RRU)

For distributed NodeB and BTS3900C, the RF module is RRU3808, RRU3804, RRU3801E, or RRU3801C.

In V200R010, the RRU3804, RRU3801E, and RRU3801C are supported.

In V200R011, the RRU3808 is added.

The RRU is classified into the RRU3804, RRU3801C, RRU3801E, and RRU3808 based on different output

power and processing capabilities. The RRU3808 supports two RX channels and two TX channels.

Table 2-35RRU Specification

RRU Type RRU3804 RRU3801C RRU3801E RRU3808

Maximum Output

Power 60W 40W 40W 2*40W

Number ofSupported Carriers 4 2 2 4

One RRU3801C/RRU3801E can support 2 contiguous carriers. DBS3900 can support smooth capacityexpansion from 1 x 1 to 1 x 2 without adding RF module. Two RRU3801Cs/RRU3801Es in parallel

connection within one sector can support the 1 x 4 configuration.

One RRU3804 can support 4 contiguous carriers. With 20W per carrier configuration, it can support 3 non

contiguous carriers (for example 1101, 1011), which is applicable to RAN sharing with 2 operators has non

contiguous carriers. Two RRU3804s in parallel connection within one sector can support the 1 x 8

configuration.

The RRU3808 supports 2T2R with two TX channels. The maximum radio output power per channel is 40 W.

One RRU3808 can support 4 carriers within 60M frequency bandwidth, per carrier 20W.

For MIMO, transmit diversity configuration, two RRU3804s/RRU3801Cs /RRU3801Es should be

configured within one sector, or one RRU3808 should be configured within one sector.

For 4-way receive diversity configuration, two RRUs should be configured within one sector.

2.2.2 3900 Series NodeB Typical Configurations

BTS3900

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


27/77




Step 1 BTS3900 (-48V DC) 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-36Recommended configurations of the BTS3900

Per carrier

20W

Minimum # of

Indoor Cabinet

Minimum # of

WMPT

Minimum # of

WBBPd

Minimum # of

RFU

1 1 1 1 1 1

1 2 1 1 1 1

1 3 1 1 1 1

1 4 1 1 1 1

2 1 1 1 1 2

2 2 1 1 1 2

2 3 1 1 1 2


28/77




Per carrier

20W

Minimum # of

Indoor Cabinet

Minimum # of

WMPT

Minimum # of

WBBPd

Minimum # of

RFU

2 4 1 1 2 2

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 5 1 1 3 6

3 6 1 1 3 6

3 7 1 1 4 6

3 8 1 1 4 6

6 3 1 1 3 6

6 4 1 1 4 6

BTS3900A

If the BBU3900 is housed in APM30 or TMC, RFU module are housed in outdoor RF cabinet,they form a NodeB BTS3900A.


29/77




Figure 2-11BTS3900A in full configuration

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

Table 2-37Recommended configurations of the BTS3900A

Per carrier

20W

Minimum # of

Cabinet

Minimum # of

WMPT

Minimum # of

WBBPd

Minimum # of

WRFU

1 1 1 1 1

1 2 1 1 1

1 3 1 1 1

1 4 1 1 1

2 1 1 1 2

2 2 1 1 2

2 3 1 1 2

2 4 1 2 2

3 1 1 1 3

3 2

One APM30,

One 6RF

cabinet,

One battery

cabinet

1 1 3


30/77




Per carrier

20W

Minimum # of

Cabinet

Minimum # of

WMPT

Minimum # of

WBBPd

Minimum # of

WRFU

3 3 1 2 3

3 4 1 2 3

6 1 1 2 6

6 2 1 2 6

3 5 1 3 6

3 6 1 3 6

3 7 1 4 6

3 8 1 4 6

6 3 1 3 6

6 4 1 4 6

DBS3900

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 WCDMAnetwork 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-12DBS3900 full configuration

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

2. Recommended configurations of the DBS3900

Per carrier 20W Minimum # of

WMPT

Minimum # of

WBBPd

Minimum # of

RRU3804


31/77




Per carrier 20W Minimum # of

WMPT

Minimum # of

WBBPd

Minimum # of

RRU3804

1 1 1 1 1

1 2 1 1 1

1 3 1 1 1

2 1 1 1 2

2 2 1 1 2

2 3 1 1 2

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 5 1 3 6

3 6 1 3 6

6 3 1 3 6

BTS3900C

The compact mini NodeB known as the BTS3900C consists of one BBU3900C (BBU3900

with a mini outdoor cabinet) and one RRU3804.

BTS3900C can support up to 1*3 configurations.

The maximum capacity of the BTS3900C is up to UL 384 CEs and DL 384 CEs. The capacitycan be expanded simply through additional modules or license upgrade. The step of licenseexpansion is 16CEs according to the customers requirements.

2.2.3 3900 Series NodeB Feature Upgrade Configurations

The hardware listed in the table is the basic hardware, and the software listed is the software influenced by the

capacity expansion or introduction of new features.

Upgrade to HSPA+ 64QAM

Table 2-38Upgrade to HSPA+ 64QAM (3 x 2 configuration, 20 W per carrier)


RF Module 3 0

Baseband Processing Unit 1 WBBPb (6Cell) 0


32/77





WCDMA Main Control Unit 1 0


The Baseband Processing Unit (6Cell) supports six cells in the downlink and thus supports six64QAM cells.

Upgrade to HSPA+ MIMO

Table 2-39Upgrade to HSPA+ MIMO (10W+10W/C) (3 x 2 configuration)


RF Module (Except RRU3808) 3 3

Baseband Processing Unit 1 WBBPb (6Cell) 1 WBBPb or WBBPd



Table 2-40Upgrade to HSPA+ MIMO (10W+10W/C) (3 x 2 configuration, RRU3808)


RRU3808 3 0




In MIMO mode, both the Baseband Processing Unit (6Cell) and the Baseband Processing Unit(3Cell) support MIMO on a maximum of three cells.

Upgrade to DC-HSDPA

Table 2-41Upgrade from 64QAM to DC-HSDPA+64QAM (3 x 2 configuration, 20 W per carrier)


RF Module 3 0

Baseband Processing Unit 1 WBBPb (6Cell) 0

WMPT 1 0


DC-HSDPA Function 0 6


33/77




When the Baseband Processing Unit (3Cell), that is, WBBPb1 or WBBPb2, is configured forsix cells DC-HSDPA, two WBBPb1 or WBBPb2 boards are required.

Upgrade to UL 16QAM



RF Module 3 0

Baseband Processing Unit 1 WBBPb (6Cell) 1 WBBPd

WMPT 1 0


Upgrade to IC



RF Module 3 0


WMPT 1 0

Power License (per 20W) 3 0

IC Function 0 6

Upgrade to FDE



RF Module 3 0


WMPT 1 0

FDE Function 0 6


34/77







RF Module (Except RRU3808) 3 3


WMPT 1 0




Table 2-46Upgrade from DL 64QAM(20W/C) to DL 64QAM+MIMO (10W+10W/C) (3 x 2configuration, RRU3808)


RRU3808 3 0


WMPT 1 0




2.3 UMTS Capacity Dimensioning Procedure

2.3.1 IntroductionThe 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


35/77




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.

Otherwise the assumed subscribers need to be adjusted and drive the procedure again. The procedure of mixed

services capacity dimensioning is illustrated in Figure 2-13.

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-13 Capacity dimensioning principles and procedure

Please be aware that The CS loading here in RAN12.0 includes not only R99 CS but also CS/VOIP over HSPA

services, we also call it Erlang services. Multi-dimensional EralngB used to calculate the peak CS loading as well.

This chapter is organized as follows:

Section 2.3.2 introduces the main principle about CS capacity dimensioning.

Section 2.3.3, 2.3.4 introduces the main principle about PS and R99 capacity dimensioning.

Section 2.3.5introduces the main principle for HSDPA capacity dimensioning

Section 2.3.6 introduces the main principle for HSUPA capacity dimensioning

Section 2.3.7introduces MBMS capacity dimensioning

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

2.3.2 CS Capacity Dimensioning PrincipleIn RAN12.0, CS over HSPA and VOIP over HSPA are introduced, which have impact on the total capacity

dimensioning.


36/77




Since the traffic of CS over HSPA and VOIP over HSPA are described as Erlang, so these part of traffic from

CS/VOIP over HSPA could combine with R99 CS traffic together to use multi-dimensional ElrangB to make the

loading dimensioning.

2.3.2.1 Separate R99 CS Capacity Dimensioning Principle

The purpose of separate R99 CS capacity dimensioning is help to decide whether the loading of R99 CS and PS

exceed the loading threshold (75% in downlink and 50% in uplink), since the loading threshold of final CS

service which includes the traffic Erlangs from CS/VOIP over HSPA is 90% in downlink and 75% in uplink.

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

Blocked

calls

Calls

arrival

Callscompletion

Fixed cell load

Figure 2-14Multidimensional 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-15Partitioning Resources vs Resources Shared


37/77




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-16Estimate 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 = (1)

)1( SHOi

iiavgCS RnectionLoadPerConCellTrafficPerLoad += (2)

Where,

userN : The number of subscribers per cell

iUserTrafficPer : The traffic per subscriber of CS service i .

SHOR : Soft handover ratio.

The peakCSLoad

and avgCSLoad

here are used to decide whether the total R99 traffic exceed loading

threshold.

2.3.2.2 Final CS capacity dimensioning


38/77




1. Calculation of all CS services peak cell load peakERLLoad

ERL peak cell load here means the peak loading consumption of R99 CS services and the traffic from CS/VOIP

over HSPA.

Same to CS peak loading dimensioning, multi-dimensional ErlangB model is used to make the calculation of

peakERLLoad .

2. Calculation of ERL average cell load avgERLLoad

ERL average cell load here means the average loading consumption of R99 CS services and traffic from

CS/VOIP over HSPA.

avgERLLoad = avgCSLoad + avgCSoverHSPALoad + avgPAVOIPoverHSLoad (3)

Where,

avgCSLoad is the average loading of R99 CS services

avgCSoverHSPALoad is the average loading of CS over HSPA services

avgPAVOIPoverHSLoad is the average loading of VOIP over HSPA services.

Calculation of 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 = (4)

CS average cell load:

Uplink:

=i

iULiavgCS nectionLoadPerConCellTrafficPerLoad

(5)

Downlink:

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

)1( SHOi

iDLiavgCS RnectionLoadPerConCellTrafficPerLoad += (6)

Where,

userN : The number of subscribers per cell


39/77




iUserTrafficPer : The traffic per subscriber of CS service i .

SHOR : Soft handover ratio.

Calculation of average loading of CS over HSPA services avgCSoverHSPALoad

Detailed capacity dimensioning is depicted as following.

Traffic per cell of CS over HSPA service:

CelliUseriCell UserNumTrafficTraffic = __ (7)

Where,

iUserTraffic _ is the traffic model of CS over HSPA users in one cell, unit: Erlang

CellUserNum is the total CS over HSPA users number in one cell

Uplink:

=i

iULiavgCSoverHSPA nectionLoadPerConlTrafficCelLoad (8)

Downlink:

=i

iDLiavgCSoverHSPA nectionLoadPerConlTrafficCelLoad (9)

Calculation of average loading of VOIP over HSPA services avgPAVOIPoverHSLoad

Detailed capacity dimensioning is depicted as following.

Traffic per cell of CS/VOIP over HSPA service:

CelliUseriCell UserNumTrafficTraffic = __ (10)

Where,

iUserTraffic _ is the traffic model of VOIP over HSPA users in one cell, unit: Erlang

CellUserNum is the total VOIP over HSPA users number in one cell

Uplink:

=i

iULiavgPAVOIPoverHS nectionLoadPerConlTrafficCelLoad

(11)

Downlink:


40/77




=i

iDLiavgPAVOIPoverHS nectionLoadPerConlTrafficCelLoad

(12)

2.3.3 PS Capacity Dimensioning PrincipleThe following shows us how to calculate the average cell load caused by PS services.

1. Calculation of PS average cell load for UL AvgPSLoad

iUL

i

ichannelsAvgPS nectionLoadPerConNLoad = (13)

Where

ichannelsN is the number of equivalent channels for service i

3600

)1()1( Re

++=

ii

Burstinessiontransmissiiuser

ichannelsR

RRPerUserThroughputNN

(14)

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.3.4 R99 CS+PS loading evaluation

From the calculation in 2.3.2.1 and 2.3.3, we need to tell whether the R99 CS+PS loading already exceed 75% in

downlink and 50% in uplink.

Downlink

Total R99 downlink loading = max { peakCSLoad

, avgCSLoad

+ AvgPSLoad

} (15)

Uplink

Total R99 uplink loading = max { peakCSLoad

, avgCSLoad

+ AvgPSLoad

} (16)

Either of them exceeds the threshold would drive the iteration procedure.


41/77




2.3.5 HSDPA Capacity Dimensioning

For HSDPA capacity dimensioning, average HSDPA cell throughput can be calculated based on availableresources like power and codes for HSDPA and average cell radius. The following figure shows the

procedure.

Simulation

Ec/Io distribution

Ior/Ioc distribution

Cell coverageradius

Cell averagethroughputEc/Io =>throughput

Power andPower andPower andPower andCode forCode forCode forCode for

HSDPAHSDPAHSDPAHSDPA

Figure 2-17HSDPA capacity dimensioning

Based on the input cell radius, the Ior/Ioc (Ior and Ioc are the received power spectrum density of own celland other cell respectively and hence the ratio of Ior/Ioc reflects the distance between UE and NodeB) andits probability distribution could be gotten from simulation. For any Ior/Ioc, the Ec/Io based on the input

HSDPA power could be calculated by the following formula:

IorIoc

IorEc

IocIor

Ec

Io

Ec

/

/

* ++++====

++++====

Once the Ec/Io is calculated, the corresponding throughput can be gotten based on the relation simulationresults between Ec/Io and throughput.

Therefore, the cell average throughput can be calculated by the following formula:

==== kIocIork obRateThCell _Pr Of course, the required power of HSDPA to guarantee HSDPA cell average throughput requirement can

also be calculated.

2.3.6 HSUPA Capacity Dimensioning

Similar with capacity dimensioning of HSDPA, average HSUPA cell throughput for input load or the load

needed by HSUPA to achieve certain throughput can be calculated.


42/77


43/77




2.3.7 MBMS Capacity Dimensioning

MBMS service has two kind of working mode: PTP (point to point), PTM (point to multi-point), PTP isborne 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:

Figure 2-19 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 = (17)

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 takelinksN 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 followingformula:

)/(* carriersNALoad linksMBMSMBMS = (18)

Where,

MBMSLoad is the total loading consumption of MBMS services


44/77




2.3.8 Total Capacity CalculationPS 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.

Figure 2-20Resource Shared by CS and PS

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

},max{_ HSUPAavgPSavgERLpeakERLULtotalcell

LoadLoadLoadLoadLoad ++=

MBMSCCHHSDPAavgPSavgERLpeakERLDLtotalcell LoadLoadLoadLoadLoadLoadLoad ++++= },max{_

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

of subscribers here is the maximum capacity of one cell.

2.4 UMTS CE Dimensioning Procedure

2.4.1 IntroductionCE (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.


45/77




Subscribers per NodeBTraffic model

Dimensioning Start

Multidimensional ErlangBcalculate Peak CE of CS

Calculate average CEof PS

Calculateaverage CE of CS

Total Channel

Elements

Dimensioning End

Calculate CE forA-DCH of HSDPA

Calculate CE for HSUPAand A-DCH of HSUPA

Figure 2-21CE Dimensioning Procedure

Note:

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

2.4.2 CE Dimensioning for CS/VOIP over HSPA services

The CE consumption of CS / VoIP over HSPA services is shown below:

Table 2-47CE Map of each connection

Each Connection TTI = 10ms TTI = 2ms

CS over HSPA 1 1

VoIP over HSPA 1 1

2.4.3 CE Dimensioning for Erlang ServiceErlang services here include: R99 CS services (voice, video phone), CS over HSPA and VOIP over HSPA

services. The same as capacity dimensioning, multi-dimensional Erlang B algorithm are applied to Erlang

services which includes both R99 CS services and CS/VOIP over HSPA services.

CE dimensioning for Erlang services is comprised with 3 parts as follows:

1. Calculating the subscribers per Node B( usersN

)

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


46/77




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 Eralng service ( PeakErlCE _ )

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

traffic at Busy Hour for all Erlang services meeting the respective GoS (grade of service) requirements.

The basic principle and procedure is the same to the CS capacity please refer to section 2.3.2 for the details of

multi-dimensional ErlangB algorithm to get the peak number of CE consumption.

3. Calculating the average number of CEs for Erlang service ( AverageErlCE _ )

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

experiences. In other words, CE resources will first have to satisfy traffic of Erlang services during Busy Hour

Traffic. Nevertheless, Erlang services may consume average number of CEs due to the fact that Erlang traffic is

not always at its peak.

The average number of CEs needed at Busy Hour for Erlang services according to the traffic is calculated as

following formula:

iusers

i

iSHOAverageErl NUserTrafficPerRCE += )1(_ (1.)

iUserTrafficPer is traffic per user for service i .

SHOR is Soft Handover ratio. Please be aware that the CS/VOIP over HSPA services dont support soft handover,

thus this value should be zero for CS/VOIP over HSPA services.

i is the CE factors and shown in Table 2-47, 2-48.

Table 2-48CE 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


47/77




2.4.4 CE Dimensioning for PS services ( AvgPSCE _ )Calculating the average number of CEs needed at Busy Hour for PS service is the same as that of Erlang

services average CE. It is according to the traffic and should consider the PS characteristics in addition, e.g.

burst, retransmission, shown in the following formulas:

AvgPSCE _ =iitranrate

i ii

iusersBurstrateSHO

RR

PerUserThroughputNRR +

++ )1(

3600)1()1( _Re

(2.)

Where,

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 .

i is the CE factors and shown in Table 2-48.

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

Number of uplink CEs for HSDPA ( ULHSDPACE _ ) can be calculated according to number of simultaneously

connected HSDPA users ( LinksHSDPAN _ ) and CE factors. Table 2-3 shows the UL A-DCH needed for specified

HSDPA bearers and related CE consumption per link.

HSDPA A-DCH links could be calculated by the following formulas

LinksHSDPAN _ = ata__

_

DHSDPAAvg

HSDPATr

Rate

Throughput

(3.)

Where,

LinksHSDPAN _ is the online HSDPA links number


48/77




HSDPATrThroughput _ is the total traffic of HSDPA services

DataHSDPAAvgRate __ is the online average HSDPA services throughput per user

Thus the final CE consumption of the A-DCH links of HSDPA services could be calculated by the followingformulas:

ULHSDPACE _ =LinksHSDPAN _ *

i (4.)

Where i

is the CE map in Table 2-49.

Table 2-49 UL A-DCH bearer rate and CE factor of HSDPA services mapping

HSDPA

AveRate

(kbps)

UL A-DCH

Bearer Rate

UL A-DCH CE

(over DCH)

UL A-DCH CE

(over HSUPA)

128 16 1 1.00

384 32 1.5 1.00

3600 64 3 1.85

7200 128 5 3.17

14400 384 10 5.59

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 will consume CE. A-DCH in downlink will consume one CE per

link.

If SRB over HSDPA feature is activated, then no CE will be consumed by HSDPA service in downlink. There is

dedicated H/W in Huawei Node B to support HSDPA service processing, so HSDPA traffic does not consume

any CE.

The HSDPA links in the downlink can be calculated by formulas (3) in this section.

2.4.6 CE Dimensioning for HSUPAThe following table shows the CE factors consumed by HSUPA service

Table 2-50 CE Mapping for HSUPA Services

MinSF HSUPA Rate(kbps) RAN 12.0


49/77




10ms TTI 2ms TTI

SF32 32 1

SF16 64 2

SF8 128 4

SF4 672 640 8

2*SF4 1399 1280 16

2*SF2 2886 2720 32

2*SF2+2*SF4 5742 5440 48

1) CE consumed by HSUPA traffic

CE numbers consumed by HSUPA traffic channel depends on the simultaneous connected links number.

(5.)

Wherein,

)1(*

)Re1(*)1(*)(

)(

Burstratio

ontransmissiSHOfactorkbitUseroughputPerAverageThr

kbitPerNodeBThroughputLinks

HSUPA

HSUPA

HSUPA

+

++=(6.)

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.

HSUPACEFactor is the CE mapping in table 2-50.

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

The same to HSDPA, when an HSDPA subscriber accesses the network, a uplink A-DCH is set up, which will

possibly consume CE. If SRB over HSUPA feature is activated, then no CE will be consumed, otherwise this A-

DCH in uplink will consume one CE per link, calculated by the following formulas:

AULHSUPACE _ = HSUPALinks *1 (7.)

HSUPALinks is simultaneous connected HSUPA link, can be calculated by formulas (6).

(2)In Downlink ( ADLHSUPACE _ )

HSUPAHSUPATrafficHSUPA CEFactorLinksCE *_ =


50/77




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

is needed for A-DCH of HSUPA in downlink.

2.4.7 CE Dimensioning for MBMS ( MBMSCE )

Downlink CE consumption for MBMS only need to be concerned. CE consumption for eachMBMS channel is the same to R99 service, showed in the following table:

Table 2-51CE consumption for MBMS

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

OVSF SF128 SF64 SF32 SF16 SF8

CEconsumption

1 1 2 4 8

Bearer

j

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

2.4.8 Total Number of Channel ElementsR99 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.


51/77




Total CE

CE Peak for CS

CE Average for CS

CE occupied by CS

CE occupied by PS

CE

Resource

Time

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

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

}max{ ____,__ ULHSUPAULHSDPAAvgPSAvgErlPeakErlULTotal CECECECECECE +++=

}max{ ____,__ MBMSDLHSUPADLHSDPAAvgPSAvgErlPeakErlDLTotal CECECECECECECE ++++=

2.5 UMTS Iub Dimensioning Procedure

2.5.1 IntroductionIub, as shown in Figure 2-23 , is the interface between RNC and Node B.


52/77




RNS

RNC

RNS

RNC

Core Network

Node B Node B Node B Node B

Iu Iu

Iur

Iub IubIub Iub

UTRAN

Figure 2-23UTRAN Architecture

The purpose of Iub dimensioning is to calculate Iub bandwidth.

Multidimensional ErlangB model are used to estimate the Iub bandwidth of CS multi-service as well. 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-24 shows the Iub dimensioning procedure.

CS Traffic Voice Traffic

CS data Traffic

GoS Requirements

CS IubBandwidth

IubBandwidth

Input Iub Dimensiong Output

PS Traffic PS64 throughput

PS128 throughput

PS384 throughput

PS retransmission

Subscribes Subs. per NodeB

Common ChannelBandwidth

PS IubBandwidth

O&M Bandwidth

SignallingBandwidth

Bandwidthfor Traffic ++++

++++

HSDPA Iub

BandwidthHSDPA Traffic

Figure 2-24Iub Dimensioning Procedure

Please be noted that the CS Iub bandwidth in above figure not only include R99 CS but also CS/VOIP over HSPA

services.


53/77




2.5.2 Iub Bandwidth Dimensioning for TrafficSince 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-25 illustrates sharing of Iub bandwidth by CS and

PS, HSPA.

Figure 2-25CS and PS Sharing Resource

Please be noted that the CS traffic here means: R99 CS + CS over HSPA+ VOIP over HSPA. We also call it

Erlang services.

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

),max( ___ HSPAAvgPSAvgErlPeakErltraffic IubIubIubIubIub ++= (8.)

2.5.2.1 Erlang Services Peak Iub Bandwidth ( PeakErlIub _ )

Peak Iub bandwidth and can be calculated by multidimensional ErlangB algorithm. The basic principle of

Multidimensional ErlangB can be referred to section 2.3.2. 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 multidimensionalErlangB (MDE) model. This idea is shown in following figure.


54/77




GoS requirements ofvarious CS services

MDE

Traffic of every CS

service per NodeB;Iub factors

CS peak Iub bandwidth

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

2.5.2.2 Erlang Services Average Iub Bandwidth ( AverageErlIub _ )

AverageErlIub _ is the average Iub bandwidth for all kinds of CS services, which does not guarantee the GoS

requirements. The formula below is used to calculate Erlang services average bandwidth:

AverageErlIub _ = AverageCSIub _ + AverageCSoverHSPAIub _ + AveragePAVOIPoverHSIub _ (9.)

=

=

i

iIubiuser

i

iIubiAverageCS

RPerUserIubTrafficN

RPerNodeBIubTrafficIub

_

__

**

*

(10.)

Where:

)1(* SHOii RUserTrafficPerPerUserIubTraffic += (11.)

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;

AverageCSoverHSPAIub _ = =i

iaIubiuser RPerUserIubTrafficN _)(** (12.)

Where,

iUserTrafficPer : traffic per user for CS over HSPA service I, no SHO traffic included;

iaIubR _)( : Iub factors for CS over HSPA service i, all overhead included;


AveragePAVOIPoverHSIub _ = =i

ibIubiuser RPerUserIubTrafficN _)(** (13.)

Where,

iUserTrafficPer : traffic per user for CS over HSPA service i, no SHO traffic included;


55/77




ibIubR _)( : Iub factors for VOIP over HSPA service i, all overhead included;


Please be noted that the Iub factors mentioned above including iIubR _ , iaIubR _)( and ibIubR _)( are relatedwith the transport techniques such as ATM, IP( IPover E1/T1 or IP over FE), for the same services, Iub

factors will be different with different transport techniques.

And the formulas shown above all are for downlink, only difference for uplink is SHO is not considered.

2.5.2.3 PS Iub Bandwidth

AveragePSIub _ is thePS 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:

=

=

i

iIubiuser

i

iIubiAveragePS

RPerUserIubTrafficN

RPerNodeBIubTrafficIub

_

__

**

* (14.)

Where:

i

BurstinessiontransmissiSHOi

iR

RRRPerUserThroughputPerUserIubTraffic

*3600

)1(*)1(*)1(* _Re +++=

(15.)

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 ;_____________________________________________________________________

Please be noted that the formulas shown above all are for downlink, only difference for uplink is SHO is not

considered.

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

RatioBurstontransmissi

OverheadHSDPANodeBSubsNumSubTrafficIub

++

+=(16.)

Where:


56/77




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. This overhead is different with different transport techniques.

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(*/_*/

ratioSHORatioBurstontransmissi

OverheadHSUPANodeBSubsNumSubTrafficIub

HSUPAHSUPA

HSUPAHSUPA

+++

+=(17.)

2.5.2.5 MBMS Iub Bandwidth

MBMS Iub bandwidth per Node B can 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 transport 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 transmissionsharing 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 differentcells, 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-27Iub transmission sharing for MBMS

2.5.3 Iub Bandwidth Dimensioning for Others ( DLOthersIub _

, ULOthersIub _

)Iub bandwidth of other is composed of 3 parts:Iub Bandwidth for Common Channel, Iub bandwidth forsignaling and Iub bandwidth for O&M.

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


57/77




Table 2-52Typical Iub bandwidth for common channel

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 t

huawei umts ran12.0 dimensioning rules v1.0

Documents