Huawei UMTS RAN12.0 Dimensioning Rules V1.0

Huawei UMTS RAN12.
0
Dimensioning Rules
Issue
V1.0
Date
2009-12-28
HUAWEI TECHNOLOGIES CO., LTD.
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 prior
written 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 respective
holders.
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 or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation 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 Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Huawei UMTS RAN12.0 Dimensioning Rules
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 .................................................................................................. 72
4.2 O&M solution dimensioning rules ................................................................................................................. 73
4.3 O&M hardware and software configuration................................................................................................... 75
Issue V1.0 (2009-12-28)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Page 3 of 77
Introduction
This document is to introduce the Dimensioning rules for Huaweis RAN product including
NodeB (Macro and DNBS) and RNC. It is based on release RAN12.0 including the
introduction 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).
Issue V1.0 (2009-12-28)

Page 4 of 77
NodeB
RAN12.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 Configuration
The BTS3812E/BTS3812AE has the following subsystems:
Transport
Subsystem
Baseband Subsystem
RF Subsystem
Control Subsystem
Antenna Subsystem
Power
Subsystem (BTS3812AE Only)

Monitoring Subsystem (BTS3812AE Only)
Environment
Issue V1.0 (2009-12-28)

Page 5 of 77

Figure 2-1 Logical 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-2 Boards in the BTS3812E/BTS3812AE baseband subrack

Table 2-1 BTS3812E/BTS3812AE Iub interface boards Specification
Board type
E1 for
ATM
E1 for
IP
FE
electrical
NDTI
NUTI
NUTI with E1 sub

board
16
NUTI with unchannelized STM-1 sub

board
NUTI with channelized

STM-1 sub board
Issue V1.0 (2009-12-28)
unchanneliz
ed STM-1
Channelized
STM-1

Page 6 of 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-2 BTS3812E/BTS3812AE Baseband boards Specification

Board Type
Cell
Uplink
R99/HSUPA CE
Downlink
R99 CE
HSDPA
Capacity
HBBI
3 cells
128CE
256CE
45 codes
HULP
3 cells
128CE
HSDPA
HDLP
6 cells
384CE
90 codes
HSUPA 10ms TTI
EBBI/EBOI
6 cells
384CE
384CE
90 codes
HSUPA 2ms
EDLP
6 cells
512CE
90 codes
HSPA+ DL 64QAM
EULP
6 cells
384CE
EULPd
6 cells
384CE
Feature Support
HSPA+DL MIMO
HSPA+ DL DC-HSDPA
HSPA+ UL 16QAM
IC
FDE
Issue V1.0 (2009-12-28)

Page 7 of 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-3 Boards in the BTS3812E/BTS3812AE RF subrack

RF Unit
Output power
carriers
MTRU
40W
WRFU
80W
Table 2-3 BTS3812E/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.
Issue V1.0 (2009-12-28)

Page 8 of 77
(1) MAFU subrack

(4) Busbar
(2) MTRU subrack

(5) Baseband subrack
(3) Fan subrack
Figure 2-4 BTS3812E(-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 maximum
of 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 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 NodeB. The NodeB with shared baseband boards only
requires RF modules at different bands.
Table 2-4 Recommended configurations of the BTS3812E
configuration
MTRU
MAFU
NMPT
NUTI
NMON
EBBI
1x1
2x1
Issue V1.0 (2009-12-28)

Page 9 of 77

2x2
3x1
3x2
3x3
3x4
The diagram for connection of S111, S222 and S333 configurations are shown below.
Figure 2-5 The S111, S222 and S333 configurations

Figure2-6 shows the BTS3812AE in full configuration.
Issue V1.0 (2009-12-28)

Page 10 of 77
Figure 2-6 BTS3812AE in full configuration

The BTS3812AE has the following configuration features:

The BTS3812AE supports the configuration of 1 to 6 sectors. Each sector supports a maximum
of four carriers. The BTS3812AE can be connected to the RRUs.
A single BTS3812AE can support 3 x 4 (sector x carrier) or 6 x 2 in no transmit diversity mode.
You may select one of the configurations, depending on the locations and the number of UEs.
The BTS3812AE supports a smooth capacity expansion from 1 x 1 to 6 x 2 or 3 x 4.
The capacity of the modular BTS3812AE 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 omni configuration and 3 x 1. With the increase in the number of UEs,
you can smoothly upgrade the system to large-capacity configurations such as 3 x 2 and 3 x 4.
The combined cabinets can support any two of the frequency bands (850 MHz, 900 MHz, 1800
MHz, 1900 MHz, and 2100 MHz). The combined cabinets with shared baseband boards only
require RF modules at different bands.
Table 2-5 Recommended configurations of the BTS3812AE
configuration
MTRU
MAFU
NMPT
NUTI
NMON
EBBI
PSU
1x1
2x1
2x2
3x1
3x2
Issue V1.0 (2009-12-28)

Page 11 of 77

3x3
3x4
2.1.3 BTS3812E/BTS312AE 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 HSUPA 2ms TTI

Table 2-6 Upgrade to HSUPA 2ms TTI (3 x 1 configuration, 20 W per carrier)
Basic Hardware/Software
Original Configuration
Additional Configuration
Transport Interface Unit
1NUTI
Baseband Processing Unit
1HBBI
1EBBI
RF Module
3MTRU+3MAFU
WCDMA Main Control Unit
1NMPT+1NMON
HSUPA Introduction Package (per NodeB)
HSUPA Phase2 (per NodeB)
Upgrade to HSPA+ 64QAM

Table 2-7 Upgrade to HSPA+ 64QAM (3 x 2 configuration, 20 W per carrier)
1NUTI
1HBBI+1EBBI
RF Module
3MTRU+3MAFU
1NMPT+1NMON
DL 64QAM Function (per Cell)
The Baseband Processing Unit (6Cell) supports six cells in the downlink and thus supports six
64QAM cells.
Upgrade to HSPA+ MIMO

Table 2-8 Upgrade to HSPA+ MIMO (10W+10W/C) (3 x 2 configuration)
1NUTI
Issue V1.0 (2009-12-28)

Page 12 of 77

1HBBI+1 EBBI
1EBBI
RF Module
3MTRU+3MAFU
3MTRU+3MAFU
1NMPT+1NMON
2*2 MIMO Function (per Cell)
Table 2-9 Upgrade to HSPA+ MIMO (10W+10W/C) (3 x 2 configuration, WRFU)

1NUTI
1HBBI+1EBBI
1EBBI
RF Module
3MTRU+3MAFU
3WRFU
1NMPT+1NMON
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-10 Upgrade from 64QAM to DC-HSDPA+64QAM (3 x 2 configuration, 20 W per carrier)
1NUTI
1HBBI+1EBBI
RF Module
3MTRU+3MAFU
1NMPT+1NMON
DC-HSDPA Function
Upgrade to UL 16QAM
Table 2-11 Upgrade from HSUPA phase2 (20W/C) to UL 16QAM (3 x 2 configuration)
1NUTI
1HBBI+1EBBI
1EULPd
RF Module
3MTRU+3MAFU
Issue V1.0 (2009-12-28)

Page 13 of 77
1NMPT+1NMON
UL 16QAM Function
Upgrade to IC
Table 2-12 Upgrade from HSUPA phase2 (20W/C) to IC (3 x 2 configuration)
1NUTI
1HBBI+1EBBI
1EULPd
RF Module
3MTRU+3MAFU
1NMPT+1NMON
IC Function
Upgrade to FDE
Table 2-13 Upgrade from HSPA (20W/C) to FDE (3 x 2 configuration)
1NUTI
1HBBI+1EBBI
1EULPd
RF Module
3MTRU+3MAFU
1NMPT+1NMON
FDE Function
Upgrade to DL 64QAM+MIMO
Table 2-14 Upgrade from DL 64QAM(20W/C) to DL 64QAM+MIMO (10W+10W/C) (3 x 2
configuration)
1NUTI
1HBBI+1EBBI
1EDLP
RF Module
3MTRU+3MAFU
3MTRU+3MAFU
1NMPT+1NMON
Issue V1.0 (2009-12-28)

Page 14 of 77

DL 64QAM+MIMO Function

configuration, WRFU)
1NUTI
1HBBI+1EBBI
1EDLP
RF Module
3MTRU+3MAFU
3WRFU
1NMPT+1NMON
2.1.4 DBS3800 Basic Module Configuration

The 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.
Issue V1.0 (2009-12-28)

Page 15 of 77

Figure 2-7 Function modules of the DBS3800
Table 2-16 Function 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
RRU3801E
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-17 DBS3800 Iub interface boards Specification

Board type
E1 for ATM
E1 for IP
FE
unchannelized STM-1
electrical
BBU3806
UBTI

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.
Issue V1.0 (2009-12-28)

Page 16 of 77

Table 2-18 DBS3800 Baseband boards Specification
Board Type
Cell
Uplink
R99/HSUPA
Downlink
R99 CE
HSDPA
Capacity
BBU3806
3 cells
192CE
256CE
45 codes
HSDPA
(When BBU active

HSUPA, 128CE)
BBU3806+EBBC
6 cells
384CE
Feature Support
HSUPA 10ms TTI

512CE
90 codes
HSUPA 2ms
HSPA+ DL 64QAM
(When BBU active

HSUPA, 320CE)
HSPA+DL MIMO
HSPA+ DL DC-HSDPA
BBU3806+EBBCd
6 cells
384CE
512CE
90 codes
HSPA+ UL 16QAM
IC
(When BBU active

HSUPA, 320CE)
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-19 DBS3800 RRU Specification

RRU Type
Maximum Output
Power
Number of
Supported Carriers
RRU3804
RRU3801C
RRU3801E
RRU3808
60W
40W
40W
2*40W
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 Configuration

The 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.
Issue V1.0 (2009-12-28)

Page 17 of 77

Table 2-20 Configuration of the DBS3800 configured with 40 W RRU (not supporting HSUPA
phase 2 and HSPA+)
20 W per Carrier
Minimum Number
of BBU3806s
Minimum
of EBBCs
Number
Minimum Number
of 40 W RRUs
1x1
2x1
2x2
3x1
3x2
3x3
3x4
Table 2-21 Configuration of the DBS3800 configured with 60 W RRU (not supporting HSUPA
phase 2 and HSPA+)
20 W per Carrier
Minimum Number
of BBU3806s
Minimum
of EBBCs
Number
Minimum Number
of 60 W RRUs
1x1
2x1
2x2
3x1
3x2
3x3
3x4
2.1.6 DBS3800 Feature Upgrade Configurations

Upgrade to HSUPA 2ms TTI
Table 2-22 Upgrade to HSUPA 2ms TTI (3 x 1 configuration, 20 W per carrier)
BBU Unit
1BBU3806
1EBBC
RF Module
3RRU3801C
HSUPA Introduction Package (per NodeB)
HSUPA Phase2 (per NodeB)
Issue V1.0 (2009-12-28)

Page 18 of 77

BBU Unit
2BBU3806
1EBBC
RF Module
3RRU3801C
64QAM cells.

BBU Unit
2BBU3806
2EBBC
RF Module
3RRU3801C
3RRU3804 or RRU3801E
Table 2-25 Upgrade to HSPA+ MIMO (10W+10W/C) (3 x 2 configuration,RRU3808)

BBU Unit
2BBU3806
2EBBC
RF Module
3RRU3801C
Upgrade to DC-HSDPA
BBU Unit
2BBU3806
1EBBC
RF Module
3RRU3801C
DC-HSDPA Function
Issue V1.0 (2009-12-28)

Page 19 of 77
Upgrade to UL 16QAM
BBU Unit
2BBU3806
1EBBCd
RF Module
3RRU3801C
UL 16QAM Function
Upgrade to IC
BBU Unit
2BBU3806
1EBBCd
RF Module
3RRU3801C
IC Function
Upgrade to FDE
BBU Unit
2BBU3806
1EBBCd
RF Module
3RRU3801C
FDE Function
configuration)
BBU Unit
2BBU3806+1EBBC
1EBBC
RF Module
3RRU3801C
Issue V1.0 (2009-12-28)

Page 20 of 77

configuration, RRU3808)
BBU Unit
2BBU3806+1EBBC
1EBBC
RF Module
3RRU3801C
3RRU3808 swap 3RRU3801C
2.2 NodeB V200R012

The 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.
Issue V1.0 (2009-12-28)

Page 21 of 77

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

Different combinations of the units and auxiliary devices form the following 3900 series NodeBs:
Cabinet macro NodeB
Issue V1.0 (2009-12-28)

Page 22 of 77

The cabinet macro NodeB, integrating the BBU3900 and the WRFU, consists of the indoor BTS3900 and
the 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 distributed
installation, 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 no
equipment 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. 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-10 Structure of the BBU3900 Subrack

Table 2-32 The board supported in the slots
Board
Slot 0
Slot 1
Slot 2
Slot 3
Slot 4
Slot 5
WMPT
Issue V1.0 (2009-12-28)

Slot 6
Slot 7
available
available
Page 23 of 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 8
E1 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-33 Transmission Card Specification

Type
WMPT
UTRP3
UTRP4
UTRP6
UTRP9
UTRP2
E1
for
ATM
E1 for
IP
4
8
0
FE
electr
ical
1
FE
optical
unchanne
lized
STM-1
FE/GE
electrical
FE/GE
Optical
8
1
4
2

The 3900 series NodeB supports smooth evolution to subsequent 3GPP protocols, which can be configured with
different 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.
Issue V1.0 (2009-12-28)

Page 24 of 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-34 Baseband Card Specification
Cell
Uplink
R99/HSUP
A CE
Downlink
R99 CE
HSDPA
Capacity
WBBPa
WBBPb1
WBBPb2
WBBPb3
3 cells
3 cells
3 cells
6 cells
128
64
128
256
256
64
128
256
45 codes
45 codes
45 codes
90 codes
WBBPb4
WBBPd1
6 cells
6 cells
384
192
384
192
90 codes
90 codes
WBBPd2
6 cells
384
384
90 codes
Board
Type
Feature Support
HSDPA
HSUPA 10ms TTI
HSUPA 2ms
HSPA+ DL 64QAM
HSPA+DL MIMO
HSPA+ DL DCHSDPA
HSPA+ UL 16QAM
IC
FDE
In the case of 2 x 2 MIMO, TX Diversity or 4-way RX diversity configurations , the WBBP

that 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 BB
capacity 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 be
implemented 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
Issue V1.0 (2009-12-28)

Page 25 of 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-35 RRU Specification

RRU Type
Maximum Output
Power
Number of
Supported Carriers
RRU3804
RRU3801C
RRU3801E
RRU3808
60W
40W
40W
2*40W
One RRU3801C/RRU3801E can support 2 contiguous carriers. DBS3900 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. 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 following
figure shows the BTS3900 (-48V DC).
Issue V1.0 (2009-12-28)

Page 26 of 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-36 Recommended configurations of the BTS3900
Per carrier
20W
Minimum # of
Indoor Cabinet
Minimum # of
WMPT
Minimum # of
WBBPd
Minimum # of
RFU
11
12
13
14
21
22
23
Issue V1.0 (2009-12-28)

Page 27 of 77

Per carrier
20W
Minimum # of
Indoor Cabinet
Minimum # of
WMPT
Minimum # of
WBBPd
Minimum # of
RFU
24
31
32
33
34
61
62
35
36
37
38
63
64
BTS3900A
If the BBU3900 is housed in APM30 or TMC, RFU module are housed in outdoor RF cabinet,
they form a NodeB BTS3900A.
Issue V1.0 (2009-12-28)

Page 28 of 77
Figure 2-11 BTS3900A in full configuration

The capacity, CE resource of BTS3900A is the same as BTS3900.
Table 2-37 Recommended configurations of the BTS3900A
Per carrier
20W
Minimum # of
Cabinet
Minimum # of
WMPT
Minimum # of
WBBPd
Minimum # of
WRFU
11
One APM30,
12
One 6RF
cabinet,
13
One battery
cabinet
21
22
23
24
31
32
14
Issue V1.0 (2009-12-28)

Page 29 of 77

Per carrier
20W
Minimum # of
Cabinet
Minimum # of
WMPT
Minimum # of
WBBPd
Minimum # of
WRFU
33
34
61
62
35
36
37
38
63
64
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 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-12 DBS3900 full configuration

The capacity, CE resource of DBS3900 is also the same as BTS3900.
2.
Recommended configurations of the DBS3900
Per carrier 20W
Issue V1.0 (2009-12-28)
Minimum # of
WMPT
Minimum # of
WBBPd

Minimum # of
RRU3804
Page 30 of 77

Per carrier 20W
Minimum # of
WMPT
Minimum # of
WBBPd
Minimum # of
RRU3804
11
12
13
21
22
23
31
32
33
61
62
35
36
63
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 capacity
can be expanded simply through additional modules or license upgrade. The step of license
expansion 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.

RF Module
1 WBBPb (6Cell)
Issue V1.0 (2009-12-28)

Page 31 of 77
64QAM cells.

RF Module (Except RRU3808)
1 WBBPb (6Cell)
1 WBBPb or WBBPd
Table 2-40 Upgrade to HSPA+ MIMO (10W+10W/C) (3 x 2 configuration, RRU3808)

RRU3808
1 WBBPb (6Cell)
1 WBBPb or WBBPd
Upgrade to DC-HSDPA
RF Module
1 WBBPb (6Cell)
WMPT
DC-HSDPA Function
Issue V1.0 (2009-12-28)

Page 32 of 77

When the Baseband Processing Unit (3Cell), that is, WBBPb1 or WBBPb2, is configured for
six cells DC-HSDPA, two WBBPb1 or WBBPb2 boards are required.
Upgrade to UL 16QAM
RF Module
1 WBBPb (6Cell)
1 WBBPd
WMPT
UL 16QAM Function
Upgrade to IC
RF Module
1 WBBPb (6Cell)
1 WBBPd
WMPT
Power License (per 20W)
IC Function
Upgrade to FDE
RF Module
1 WBBPb (6Cell)
1 WBBPd
WMPT
FDE Function
Issue V1.0 (2009-12-28)

Page 33 of 77
configuration)
RF Module (Except RRU3808)
1 WBBPb (6Cell)
1 WBBPb or WBBPd
WMPT

configuration, RRU3808)
RRU3808
1 WBBPb (6Cell)
1 WBBPb or WBBPd
WMPT
2.3 UMTS Capacity Dimensioning Procedure

2.3.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, circuitswitched 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
Issue V1.0 (2009-12-28)

Page 34 of 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
Assumed Subscribers per cell

Traffic model
Load per connection
Multidimensional ErlangB
calculate Peak load of CS
Calculate average
load of PS
Calculate load of
HSDPA
Calculate load of
HSUPA
Calculate
average load of CS
Calculate total cell

load
No
=Target Cell Load?
Yes
Dimensioning End
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 Principle

In RAN12.0, CS over HSPA and VOIP over HSPA are introduced, which have impact on the total capacity
dimensioning.
Issue V1.0 (2009-12-28)

Page 35 of 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 Load CS peak
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:
Calls
arrival
Fixed cell load
multiservice
Calls
completion
Blocked
calls
Figure 2-14 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-15 Partitioning Resources vs Resources Shared
Issue V1.0 (2009-12-28)

Page 36 of 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 of
various CS services
CS peak cell load
MDE
Subscribers per cell
Figure 2-16 Estimate CS Capacity with Multidimensional Erlang B Model
2.
Calculation of CS average cell load
Load CS avg
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:
TrafficPerCell i = TrafficPerUseri N user
(1)
Load CS avg = TrafficPerCelli LoadPerConnectioni (1 + RSHO ) (2)

i
Where,
N user : The number of subscribers per cell

TrafficPerUseri : The traffic per subscriber of CS service i .
RSHO : Soft handover ratio.
Load CS peak
The
threshold.
and
Load CS avg
here are used to decide whether the total R99 traffic exceed loading
2.3.2.2 Final CS capacity dimensioning
Issue V1.0 (2009-12-28)

Page 37 of 77
1.
Calculation of all CS services peak cell load Load ERL peak
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
Load ERL peak .
2.
Calculation of ERL average cell load Load ERL avg
ERL average cell load here means the average loading consumption of R99 CS services and traffic from
CS/VOIP over HSPA.
Load ERL avg = Load CS avg + Load CSoverHSPA avg + Load VOIPoverHSPA avg
(3)
Where,
Load CS avg is the average loading of R99 CS services

Load CSoverHSPA avg is the average loading of CS over HSPA services
Load VOIPoverHSPA avg is the average loading of VOIP over HSPA services.
Calculation of
Load CS avg
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 :
TrafficPerCell i = TrafficPerUseri N user
(4)
CS average cell load:
Uplink:
Load CS avg = TrafficPerCell i LoadPerConnectionUL i

i
(5)
Downlink:
On downlink the calculation of load should consider the ratio of SHO.
Load CS avg = TrafficPerCell i LoadPerConnection DL i (1 + RSHO )

i
(6)
Where,
N user : The number of subscribers per cell
Issue V1.0 (2009-12-28)

Page 38 of 77
TrafficPerUseri
: The traffic per subscriber of CS service
i.
R SHO : Soft handover ratio.
Calculation of average loading of CS over HSPA services Load CSoverHSPA avg
Detailed capacity dimensioning is depicted as following.

Traffic per cell of CS over HSPA service:
Traffic Cell _ i = Traffic User _ i UserNum Cell
(7)
Where,
TrafficUser _ i is the traffic model of CS over HSPA users in one cell, unit: Erlang
UserNumCell is the total CS over HSPA users number in one cell

Uplink:
Load CSoverHSPA avg = TrafficCell i LoadPerConnectionUL i
(8)
Downlink:
Load CSoverHSPA avg = TrafficCell i LoadPerConnection DL i
(9)
Calculation of average loading of VOIP over HSPA services Load VOIPoverHSPA avg
Detailed capacity dimensioning is depicted as following.

Traffic per cell of CS/VOIP over HSPA service:
Traffic Cell _ i = Traffic User _ i UserNum Cell
(10)
Where,
TrafficUser _ i
UserNumCell
is the traffic model of VOIP over HSPA users in one cell, unit: Erlang
is the total VOIP over HSPA users number in one cell
Uplink:
Load VOIPoverHSPA avg = TrafficCelli LoadPerConnectionUL i

i
(11)
Downlink:
Issue V1.0 (2009-12-28)

Page 39 of 77
Load VOIPoverHSPA avg = TrafficCelli LoadPerConnection DL i

i
(12)
2.3.3 PS Capacity Dimensioning Principle

The following shows us how to calculate the average cell load caused by PS services.
1.
Load PS Avg
Calculation of PS average cell load for UL
Load PS Avg = N channels i LoadPerConnectionUL i
(13)
Where
N channels i
is the number of equivalent channels for service i
N channels i =
N user Throughput PerUseri (1 + RRe transmissi on i ) (1 + R Burstiness )

i Ri 3600
(14)
ThroughputPerUseri : Throughput per user for service i .

RRe transmission i : The ratio of data retransmission for service i because of block error.
R Burstiness : 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 {

Load CS peak
Load CS avg Load PS Avg

+
} (15)
Uplink
Total R99 uplink loading = max {
Load CS peak
Load CS avg Load PS Avg

+
}
(16)
Either of them exceeds the threshold would drive the iteration procedure.
Issue V1.0 (2009-12-28)

Page 40 of 77
2.3.5 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 average cell radius. The following figure shows the
procedure.
Cell coverage
radius
Simulation
Power and
Code for
HSDPA
Ior/Ioc distribution
Ec/Io distribution
Ec/Io =>throughput
Cell average
throughput
Figure 2-17 HSDPA capacity dimensioning

Based on the input cell radius, the Ior/Ioc (Ior and Ioc are the received power spectrum density of own cell
and other cell respectively and hence the ratio of Ior/Ioc reflects the distance between UE and NodeB) and
its 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:
Ec
Ec
Ec / Ior
=
=
Io * Ior + Ioc + Ioc / Ior
Once the Ec/Io is calculated, the corresponding throughput can be gotten based on the relation simulation
results between Ec/Io and throughput.
Therefore, the cell average throughput can be calculated by the following formula:
ThCell =
Ratek Pr obIocIor _ k
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.
Issue V1.0 (2009-12-28)

Page 41 of 77

The following figure shows the procedure of calculating HSUPA cell throughput from input load.
Figure 2-18 HSUPA capacity dimensioning

Given the distance between UE and NodeB, the Ec/N0 can be calculated with the same procedure of
HSUPA link budget. HSUPA user data rate could be gotten by the relations between cell radius and the
HSUPA throughput, and then we need to calculate the uplink HSUPA cell throughput by the following
formulas:
ThCell = Ratek
Sk
S
Where,
Ratek is the HSUPA throughput at specified cell radius

Sk is coverage area of infinitesimal circles at specified cell radius
S is the total coverage area of the cell
The basic principle of this formula are: if we divide the cell coverage area into many concentric circles
with infinitesimal radius, then the coverage area of all given concentric circles Sk and the whole cell
coverage area S could also be calculated. Consequently, HSUPA cell average throughput can be
calculated.
It should be noted that maximum transmission power of UE should be a limit for the calculation of Ec/No
calculation. If we assume maximum available uplink load for HSUPA is HSUPA , then the maximum
Ec/No achieved with this maximum given loading could be calculated by this formula:
HSUPA =
1+ f
1
1+
Ec / N 0
So the final Ec/N0 of HSUPA would be the minimum value of both of them. As a result, the final Ratek for
HSUPA cell average throughout calculation in the above formula should be the minimum value of them.
Issue V1.0 (2009-12-28)

Page 42 of 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 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:
Figure 2-19 MBMS Dimensioning Procedure

Power consumption for each MBMS channel at air interface can be calculated by the following formula:
AMBMS = (10 PL MBMS / 10 ) /(10 PBS / 10 )
(17)
Where,
AMBMS is the loading for each MBMS channel at air interface

PL MBMS is the power consumption for per MBMS channel, this can be calculated via link budget with
specified bearer and cell radius requirement.
PBS is the total power of NodeB

If we take N links 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 N links / carriers.
Thus the total loading of all the MBMS channels within one cell can be calculated by the following
formula:
Load MBMS = AMBMS * ( N links / carriers )
(18)
Where,
Load MBMS is the total loading consumption of MBMS services
Issue V1.0 (2009-12-28)

Page 43 of 77
2.3.8 Total Capacity Calculation

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.
Figure 2-20 Resource Shared by CS and PS

According to the previous calculation we can obtain the actual total cell load by the formulas:
Load cell total _ UL = max{Load ERL peak , Load ERL avg + Load PS avg + Load HSUPA }
Load cell total _ DL = max{Load ERL peak , Load ERL avg + Load PS avg + Load HSDPA } + Load CCH + Load MBMS
When the actual total cell load Load cell total 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 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.
Issue V1.0 (2009-12-28)

Page 44 of 77
Dimensioning Start
Subscribers per NodeB
Traffic model
Multidimensional ErlangB
calculate Peak CE of CS
Calculate average CE
of PS
Calculate CE for
A-DCH of HSDPA
Calculate CE for HSUPA

and A-DCH of HSUPA
Calculate
average CE of CS
Total Channel
Elements
Dimensioning End
Figure 2-21 CE 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-47 CE Map of each connection

Each Connection
TTI = 10ms
TTI = 2ms
CS over HSPA
VoIP over HSPA
2.4.3 CE Dimensioning for Erlang Service

Erlang 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(
N users )
Subscribers per Node B= total number of subscribers/number of NodeBs.
Issue V1.0 (2009-12-28)

Page 45 of 77

Total number of subscribers and the required number of NodeBs are obtained through capacity dimensioning, for
both uplink and downlink.
Calculating the peak number of CEs for Eralng service ( CE Erl _ Peak )
2.
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 (
CE Erl _ Average
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:
CE Erl _ Average = (1 + RSHO ) TrafficPerUseri N users i
(1.)
TrafficPerUseri is traffic per user for service i .

R SHO
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.
is the CE factors and shown in Table 2-47, 2-48.
Table 2-48 CE Map for RAB

Bearer Type
CE Consumption on UL
CE Consumption on DL
AMR 12.2kbps
CS 64kbps
PS 64kbps
PS 128kps
PS 144kps
PS 384kbps
10
Issue V1.0 (2009-12-28)

Page 46 of 77
2.4.4 CE Dimensioning for PS services ( CE PS _ Avg )

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:
CE PS _ Avg = (1 + R
SHO
) (1 + RBurstrate )
i
N users ThroughputPerUseri
(1 + RRe tranrate _ i ) i
Ri i 3600
(2.)
Where,
RBurstrate
: The burst margin.
ThroughputPerUseri (kbit): The busy hour throughput per user for service i .
i : The channel utilization for service i .

RRe tranrate _ i : The retransmission ratio for service i .
Ri
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 (
CE HSDPA _ UL
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 (
CE HSDPA _ UL
) can be calculated according to number of simultaneously
connected HSDPA users ( N HSDPA _ Links ) 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
Throughput Tr _ HSDPA
N HSDPA _ Links
Rate Avg _ HSDPA _ Data
(3.)
Where,
N HSDPA _ Links
is the online HSDPA links number
Issue V1.0 (2009-12-28)

Page 47 of 77
Throughput Tr _ HSDPA
Rate Avg _ HSDPA _ Data
is the total traffic of HSDPA services
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 following
formulas:
CE HSDPA _ UL
Where
= N HSDPA _ Links *
(4.)
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)
2.
UL A-DCH
Bearer Rate
UL A-DCH CE
(over DCH)
UL A-DCH CE
(over HSUPA)
128
16
1.00
384
32
1.5
1.00
3600
64
1.85
7200
128
3.17
14400
384
10
5.59
HSDPA Downlink CE dimensioning (
CE HSDPA _ DL
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 HSUPA

The following table shows the CE factors consumed by HSUPA service
Table 2-50
MinSF
Issue V1.0 (2009-12-28)
CE Mapping for HSUPA Services

HSUPA Rate(kbps)

RAN 12.0
Page 48 of 77
10ms TTI
2ms TTI
SF32
32
SF16
64
SF8
128
SF4
672
640
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.)
CE HSUPA _ Traffic = Links HSUPA * CEFactor HSUPA

Wherein,
Links HSUPA =
ThroughputPerNodeB HSUPA (kbit )

* (1 + SHOfactor ) * (1 + Re transmissi on)
(6.)
AverageThroughputPerUserHSUPA (kbit )
* (1 + Burstratio )
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.
CEFactorHSUPA 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 ( CE HSUPA _ AUL )
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 ADCH in uplink will consume one CE per link, calculated by the following formulas:
CE HSUPA _ AUL = Links HSUPA *1
(7.)
Links HSUPA is simultaneous connected HSUPA link, can be calculated by formulas (6).
(2)In Downlink ( CE HSUPA _ ADL )
Issue V1.0 (2009-12-28)

Page 49 of 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 ( CEMBMS )

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-51 CE consumption for MBMS
MBMS Bearer
16kbps
32kbps
64kbps
128kbps
256kbps
OVSF
SF128
SF64
SF32
SF16
SF8
CE
consumption
CE MBMS = N links _ j * CE Bearer

j
Where,
CEMBMS is the total CE consumption for all MBMS channels per Node B.
N links _ j is the MBMS channel number for each Node B, this is the sum of all the MBMS
channels at each cell within Node B.
CE Bearer is the CE consumption of each MBMS bearer, as showed in the table 2-51.
2.4.8 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.
Issue V1.0 (2009-12-28)

Page 50 of 77
CE Resource
Total CE
CE Peak for CS
CE occupied by PS
CE Average for CS
CE occupied by CS
Time
Figure 2-22 CE 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:
CE Total _ UL = max{CE Erl _ Peak , CE Erl _ Avg + CE PS _ Avg + CE HSDPA _ UL + CE HSUPA _ UL }

CETotal _ DL = max{CEErl _ Peak , CEErl _ Avg + CEPS _ Avg + CEHSDPA _ DL + CEHSUPA _ DL + CEMBMS }
2.5 UMTS Iub Dimensioning Procedure

2.5.1 Introduction
Iub, as shown in Figure 2-23 , is the interface between RNC and Node B.
Issue V1.0 (2009-12-28)

Page 51 of 77
Core Network
Iu
Iu
RNS
RNS
UTRAN
Iur
RNC
Iub
Node B
RNC
Iub
Iub
Node B
Node B
Iub
Node B
Figure 2-23 UTRAN 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.
Input
Iub Dimensiong
Output
CS Traffic
Voice Traffic
CS data Traffic
GoS Requirements
CS Iub
Bandwidth
Bandwidth
for Traffic
Subscribes
Subs. per NodeB
PS Traffic
PS64 throughput
PS128 throughput
PS384 throughput
PS retransmission
Iub
Bandwidth
PS Iub
Bandwidth
HSDPA Iub
Bandwidth
HSDPA Traffic
Common Channel
Bandwidth
Signalling
Bandwidth
O&M Bandwidth
Figure 2-24 Iub 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.
Issue V1.0 (2009-12-28)

Page 52 of 77
2.5.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-25 illustrates sharing of Iub bandwidth by CS and
PS, HSPA.
Figure 2-25 CS 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:
Iubtraffic = max(IubErl _ Peak , IubErl _ Avg + IubPS _ Avg + IubHSPA )

2.5.2.1 Erlang Services Peak Iub Bandwidth (
IubErl _ Peak
(8.)
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 multidimensional
ErlangB (MDE) model. This idea is shown in following figure.
Issue V1.0 (2009-12-28)

Page 53 of 77

Traffic of every CS
service per NodeB;
Iub factors
GoS requirements of
various CS services
MDE
CS peak Iub bandwidth
Figure 2-26 Estimate CS peak Iub Bandwidth with Multidimensional Erlang B Model
2.5.2.2 Erlang Services Average Iub Bandwidth (
IubErl _ Average
IubErl _ Average 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:
IubErl _ Average = IubCS _ Average + IubCSoverHSPA _ Average + IubVOIPoverHSPA _ Average
(9.)
IubCS _ Average = IubTraffic PerNodeB i * R Iub _ i

i
(10.)
= N user * IubTraffic PerUseri * R Iub _ i

i
Where:
IubTrafficPerUseri = TrafficPerUseri * (1 + RSHO )
(11.)
TrafficPerUseri : traffic per user for CS service i;

RSHO : Soft handover ratio which does not include softer handover;
RIub _ i : Iub factors for CS service i, including FP, AAL2 and ATM over head;
N user : Number of Subscribers per NodeB;
IubCSoverHSPA _ Average = = N user * IubTrafficPerUseri * RIub ( a ) _ i
(12.)
Where,
TrafficPerUseri : traffic per user for CS over HSPA service I, no SHO traffic included;
RIub ( a ) _ i : Iub factors for CS over HSPA service i, all overhead included;
IubVOIPoverHSPA _ Average = = N user * IubTrafficPerUseri * RIub ( b ) _ i
(13.)
Where,
TrafficPerUseri : traffic per user for CS over HSPA service i, no SHO traffic included;
Issue V1.0 (2009-12-28)

Page 54 of 77
R Iub (b ) _ i : Iub factors for VOIP over HSPA service i, all overhead included;

Please be noted that the Iub factors mentioned above including R Iub _ i , R Iub ( a ) _ i and R Iub (b ) _ i are related
with 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
IubPS _ Average 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:
IubPS _ Average = IubTraffic PerNodeB i * R Iub _ i

i
= N user * IubTraffic PerUseri * R Iub _ i
(14.)
Where:
IubTrafficPerUseri =
ThroughputPerUseri * (1 + RSHO ) * (1 + RRe transmission _ i ) * (1 + RBurstiness )

3600 * Ri
(15.)
ThroughputPerUseri : Throughput per user for PS service i;

RSHO : Soft handover ratio and does not include softer handover;
RRe transmission _ i
RBurstiness
: The ratio of data retransmission because of block error for PS service i;
: The ratio of traffic burstiness;
Ri : 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:
IubHSDPA = TrafficHSDPA / Sub * Num _ Subs / NodeB * (1 + HSDPA _ Overhead )

* (1 + Re transmissionHSDPA) * (1 + Burst _ RatioHSDPA)
(16.)
Where:
Issue V1.0 (2009-12-28)

Page 55 of 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:
IubHSUPA = TrafficHSUPA / Sub * Num _ Subs / NodeB * (1 + HSUPA _ Overhead )

* (1 + Re transmissionHSUPA) * (1 + Burst _ RatioHSUPA) * (1 + SHO _ ratio)
(17.)
2.5.2.5 MBMS Iub Bandwidth

MBMS Iub bandwidth per Node B can be calculated by the following formula:
IubMBMS =
links _ i
*RMBMS _ i
Where,
RMBMS _ i is the Iub bandwidth consumption for each MBMS bearer, this value is different with different
Iub transport technology from ATM to IP.
N links _ i 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, twothird of Iub bandwidth is saved by the improved Iub transport.
CN
CRNC
MBMS stream
Node B
Iub transport bearer
Figure 2-27 Iub transmission sharing for MBMS
2.5.3 Iub Bandwidth Dimensioning for Others ( IubOthers _ DL , IubOthers _ UL )

Iub bandwidth of other is composed of 3 parts: Iub Bandwidth for Common Channel, Iub bandwidth for
signaling 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.
Issue V1.0 (2009-12-28)

Page 56 of 77

Table 2-52 Typical Iub bandwidth for common channel
Iub Bandwidth of Common Channels
ATM
IP
UL Bandwidth for RACH
60 kbps
50 kbps
DL Bandwidth for SCCPCH(FACH/PCH)
73 kbps
70 kbps
The Iub bandwidth for common channel based on ATM is a little bigger than that based on IP.
2.5.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.5.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.
2.5.4 Final Iub Bandwidth Calculation

Final Iub Bandwidth is calculated as below:
Iub DL = IubTraffic _ DL + IubOthers _ DL
IubUL = IubTraffic _ UL + IubOthers _ UL

Where,
IubTraffic _ DL = max(IubErl _ Peak _ DL , IubErl _ Avg _ DL + IubPS _ Avg _ DL + IubHSDPA )

IubTraffic _ UL = max(IubErl _ Peak _ UL , IubErl _ Avg _ UL + IubPS _ Avg _ UL + IubHSUPA )
2.6 Counters Related to Capacity

There are following main counters (not limited to) related to capacity which will help you to better understand
your networks status.
Traffic related
VS.AMR.Ctrl.DL12.2
VS.RB.DLConvCS.64
VS.HSUPA.MeanChThroughput.TotalBytes
VS.HSDPA.MeanChThroughput.TotalBytes
VS.HSUPA.UE.Mean.Cell
VS.HSDPA.UE.Mean.Cell
Base band resources: CE related

VS.LC.ULMean.LicenseGroup.Shared
VS.LC.DLMean.LicenseGroup.Shared
RF resources: Codes related
Issue V1.0 (2009-12-28)

Page 57 of 77
VS.RAB.SFOccupy
VS.RAB.SFOccupy.MAX
RF resources: Power related

VS.MeanTCP
VS.RRC.Rej.Power.Cong
VS.RAB.FailEstCs.Power.Cong
VS.RABFailEstPs.Power.Cong
RF resources: RTWP related

VS.MinRTWP
VS.MeanRTWP
Iub resources related

VS.ATMDLAvgUsed.1
VS.ATMDLAvgUsed.2
VS.ATMDLAvgUsed.3
VS.ATMDLAvgUsed.4
VS.IPDLAvgUsed.1
VS.IPDLAvgUsed.2
VS.IPDLAvgUsed.3
VS.IPDLAvgUsed.4
Issue V1.0 (2009-12-28)

Page 58 of 77
RNC
RAN12.0 is supported by RNC BSC6800 and BSC6900.
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
RNC Type 2
200
600
252
64
120/5000
RNC Type 3
300
900
384
64
180/7500
RNC Type 4
400
1,200
507
64
240/10k
RNC Type 5
500
1,500
630
64
300/12.5k
RNC Type 6
600
1,800
756
64
360/15k
RNC Type 7
700
2,100
882
64
420/17.5k
RNC Type 8
800
2,400
1, 008
64
480/20k
RNC Type 9
900
2,700
1, 134
64
540/22.5k
RNC Type10
1,000
3,000
1, 260
64
600/25k
RNC Type11
1,100
3,300
1, 386
64
660/27.5k
RNC Type12
1,200
3,600
1, 512
64
720/30k
RNC Type13
1,300
3,900
1, 638
64
780/32.5k
RNC Type14
1,400
4,200
1, 764
64
840/35k
RNC Type15
1,500
4,500
1, 890
64
900/37.5k
RNC Type16
1,600
4,800
2, 016
64
960/40k
The BSC6800 configuration can be calculated by following formula:
Issue V1.0 (2009-12-28)

Page 59 of 77

1 BSC6800 = 1 WRSS + n WRBS
WRSS (Wireless RNC Switching Sub rack) 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) 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 is the WOSEc
Issue V1.0 (2009-12-28)

Page 60 of 77

optical port version which is the latest version.
- 4 WFMRc are plugged in slot 2, 4, 5 and slot 13. One 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 / RAN11.0 / RAN12.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.
Supports 625Erl or 30 Mbit/s data

streams and 90 cells.
WRBS
Supports 2500Erl or 60 Mbit/s data streams

and 300 cells.
Supports 2500Erl or 60 Mbit/s data

streams and 300 cells.
Therefore, in RAN12.0 up to 4 WFMRc boards are needed to support one WRBS capacity. One WFMRc can
support HSDPA 28Mbps 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 calculated as the following formula:
Capacity = Min{One WRBS capacity, (WFMRb number * One WFMRb capacity + WFMRb number * One
WFMRb 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.
Issue V1.0 (2009-12-28)

Page 61 of 77

The configuration diagram is shown below:
3.2 Configurations standards of BSC6900

3.2.1 Evolution of BSC6810 to BSC6900
The BSC6900 is Huawei multi-mode BSC. The BSC6900 can be flexibly configured as a BSC6900 GSM,
BSC6900 UMTS, or BSC6900 GU mode as required in different networks. The BSC6900 UMTS is compatible
with the hardware configuration of the BSC6810. Through software loading, the BSC6810 in the existing
network can be upgraded to the BSC6900 UMTS.
Following is the compare of BSC6810 to BSC6900.
1) BSC6810 can be upgraded to BSC6900 with only software upgrade without hardware change.
2) Naming changes
RNC
BSC6810
BSC6900
Main Process Subrack
RSS
MPS
Extended Subrack
RBS
EPS
3) New boards are introduced while legacy boards are compatible.

User Plane
DPUb -> DPUe
Control Plane
SPUa -> SPUb
Transmission
Transport
BSC6900
Board
BSC6810&BSC6900
Ports
Board
Ports
IP
FG2c
12 FE / 4 GE electrical
FG2a
8/2
IP
GOUc
4 GE optical
GOUa
IP over E1/T1
POUc
4 optical cSTM-1/OC-3
POUa
ATM over E1/T1
AOUc
4 optical cSTM-1/OC-3
AOUa
Issue V1.0 (2009-12-28)

Page 62 of 77

ATM over SDH
8 optical STM-1/OC-3
UOIc
UOIa
The BSC6900 supports following hardware versions. The boards of HW68 R11 are the same as boards used in
BSC6810.
Hardware Version
Corresponding Board
HW68 R11
DPUb, SPUa, SCUa, GCGa, GCUa, OMUa, AEUa, AOUa,

FG2a, GOUa, PEUa, POUa, and UOIa
HW69 R11
DPUe, SPUb, SCUa, GCGa, GCUa, OMUa, AEUa, AOUc,

FG2c, GOUc, PEUa, POUc, UOIa, and UOIc
3.2.2 BSC6900 Hardware Architecture
Classification of BSC6900 UMTS cabinets:

Cabinet
Contained Subrack
Configuration Principle
MPR
1 MPS, 02 EPSs
Only one MPR is configured.
EPR
13 EPSs
Based on the requirement for traffic capacity,

01 EPR is configured.
Classification of BSC6900 UMTS subracks:

Subrack
Quantity
Function
MPS
The MPS performs centralized switching and

provides service paths for other subracks. It
also provides the service processing interface,
OM interface, and system clock interface.
EPS
0-5
The EPS performs the functions of user plane

processing and signaling control.
3.2.3 BSC6900 Basic Models

The BSC6900 UMTS supports 25 basic models as follows when HW68 R11 boards are used.
Issue V1.0 (2009-12-28)

Page 63 of 77
Basic Model
Iub User Plane

Capacity*
(Mbit/s/Erlang)
Number of
Supported
BHCAs*
Number
of
Supported
NodeBs
Number
of
Supported
Cells
Number
of Slots
for
Interface
Boards
BSC6810/6900 Model 230 A
230/3,600
80,000
100
300
10
BSC6810/6900 Model 230 B
230/3,600
160,000
100
300
10
BSC6810/6900 Model 460 A
460/7,200
160,000
200
600
10
BSC6810/6900 Model 460 B
460/7,200
320,000
200
600
BSC6810/6900 Model 690 A
690/10,800
240,000
300
900
24
BSC6810/6900 Model 690 B
690/10,800
480,000
300
900
24
BSC6810/6900 Model 920 A
920/14,400
320,000
400
1,200
24
BSC6810/6900 Model 920 B
920/14,400
640,000
400
1,200
22
BSC6810/6900 Model 1150 A
1,150/18,000
400,000
500
1,500
24
BSC6810/6900 Model 1150 B
1,150/18,000
720,000
500
1,500
18
BSC6810/6900 Model 1380 A
1,380/21,600
480,000
600
1,800
38
BSC6810/6900 Model 1380 B
1,380/21,600
880,000
600
1,800
38
BSC6810/6900 Model 1610 A
1,610/25,200
560,000
700
2,100
38
BSC6810/6900 Model 1610 B
1,610/25,200
960,000
700
2,100
34
BSC6810/6900 Model 1840 A
1,840/28,800
640,000
800
2,400
38
BSC6810/6900 Model 1840 B
1,840/28,800
1,040,000
800
2,400
30
BSC6810/6900 Model 2070
2,070/32,400
720,000
900
2,700
52
BSC6810/6900 Model 2300
2,300/36,000
800,000
1,000
3,000
52
BSC6810/6900 Model 2530
2,530/39,600
1,360,000
1,100
3,300
42
BSC6810/6900 Model 2760
2,760/43,200
960,000
1,200
3,600
66
BSC6810/6900 Model 2990
2,990/46,800
1,040,000
1,300
3,900
66
BSC6810/6900 Model 3220
3,220/50,400
1,680,000
1,400
4,200
54
BSC6810/6900 Model 3450
3,450/54,000
1,200,000
1,500
4,500
80
BSC6810/6900 Model 3680
3,680/57,600
1,280,000
1,600
4,800
80
BSC6810/6900 Model 3910
3,910/61,200
2,000,000
1,700
5,100
66
The BSC6900 UMTS supports 23 basic models as follows when HW69 R11 boards are used.
Number of
Supported
Basic Model
Iub User Plane Capacity*
Issue V1.0 (2009-12-28)
Number of Supported
Number of
Slots for
Number of Supported

Page 64 of 77

(Mbit/s/Erlang)
BHCAs*
Without
Capacity
Enhancement
With Capacity
Enhancement
Without
Additional
Signaling
Processing
Unit
With
Additional
Signaling
Processing
Unit
Without
Additional
Signaling
Processing
Unit
With
Additional
Signaling
Processing
Unit
Cells
Interface
Boards
BSC6900 UMTS
Model 670
670/6,700
1,000/6,700
140,000
420,000
180
540
600
10
BSC6900 UMTS
Model 1005
1,005/10,050
1,500/10,050
280,000
420,000
360
540
900
10
BSC6900 UMTS
Model 1340
1,340/13,400
2,000/13,400
280,000
420,000
360
540
1,200
10
BSC6900 UMTS
Model 1675
1,675/16,750
2,500/16,750
420,000
980,000
540
1,260
1,500
24
BSC6900 UMTS
Model 2010
2,010/20,100
3,000/20,100
420,000
980,000
540
1,260
1,800
24
BSC6900 UMTS
Model 2345
2,345/23,450
3,500/23,450
560,000
980,000
720
1,260
2,100
24
BSC6900 UMTS
Model 2680
2,680/26,800
4,000/26,800
560,000
980,000
720
1,260
2,400
24
BSC6900 UMTS
Model 3015
3,015/30,150
4,500/30,150
700,000
1,540,000
900
1,980
2,700
38
BSC6900 UMTS
Model 3350
3,350/33,500
5,000/33,500
700,000
1,540,000
900
1,980
3,000
38
BSC6900 UMTS
Model 3685
3,685/36,850
5,500/36,850
840,000
1,540,000
1,080
1,980
3,300
38
BSC6900 UMTS
Model 4020
4,020/40,200
6,000/40,200
840,000
1,540,000
1,080
1,980
3,600
38
BSC6900 UMTS
Model 4355
4,355/43,550
6,500/43,550
980,000
2,100,000
1,260
2,700
3,900
52
BSC6900 UMTS
Model 4690
4,690/46,900
7,000/46,900
980,000
2,100,000
1,260
2,700
4,200
52
BSC6900 UMTS
Model 5025
5,025/50,250
7,500/50,250
1,120,000
2,100,000
1,440
2,700
4,500
52
BSC6900 UMTS
Model 5360
5,360/53,600
8,000/53,600
1,120,000
2,100,000
1,440
2,700
4,800
52
BSC6900 UMTS
Model 5695
5,695/56,950
8,500/56,950
1,260,000
2,660,000
1,620
3,060
5,100
66
6,030/60,300
9,000/60,300
1,260,000
2,660,000
1,620
3,060
5,100
66
BSC6900 UMTS
Issue V1.0 (2009-12-28)
NodeBs

Page 65 of 77

Model 6030
BSC6900 UMTS
Model 6365
6,365/63,650
9,500/63,650
1,400,000
2,660,000
1,800
3,060
5,100
66
6,700/67,000
10,000/67,000
1,400,000
2,660,000
1,800
3,060
5,100
66
7,035/70,350
10,500/70,350
1,540,000
3,220,000
1,980
3,060
5,100
80
7,370/73,700
11,000/73,700
1,540,000
3,220,000
1,980
3,060
5,100
80
7,705/77,050
11,500/77,050
1,680,000
3,220,000
2,160
3,060
5,100
80
8,040/80,400
12,000/80,400
1,680,000
3,220,000
2,160
3,060
5,100
80
BSC6900 UMTS
Model 6700
BSC6900 UMTS
Model 7035
BSC6900 UMTS
Model 7370
BSC6900 UMTS
Model 7705
BSC6900 UMTS
Model 8040
Iub User Plane Capacity (Mbit/s/Erlang): Refers to the maximum value when the model only processes CS
services or PS services.
Without Capacity Enhancement: This column specifies the user plane specifications of a basic model.
With Capacity Enhancement: This column specifies the maximum user plane specifications after a basic model
is configured with a Hardware Capacity License (165Mbit/s) for each DPUe board.
Without Additional Signaling Processing Unit: This column specifies the control plane specifications of the
basic model.
With Additional Signaling Processing Unit: This column specifies the maximum specifications of the control
plane with additional signaling processing units added to the basic model.
3.3 RNC Interface Dimensioning

3.3.1 Iub Interface Dimensioning
Iub interface is the interface between RNC and NodeB. It is used to transfer data flow in both control plane and
user plane.
1
Iub traffic volume
The Iub traffic volume at RNC side includes CS voice traffic, CS VP traffic, PS throughput and MBMS
throughput.
Iub
IubCS
CSvoice
voice
Iub
IubCS
CSVP
VP
Iub
Iubtraffic
traffic
Iub
IubPS
PSthroughput
throughput
Iub
IubMBMS
MBMSthroughput
throughput
Iub voice traffic volume (Erlang) = Total number of subscribers * CS voice penetration ratio * CS voice call
traffic per sub per BH * (1 + Proportion of SHO for CS voice call)
Issue V1.0 (2009-12-28)

Page 66 of 77

Iub VP traffic volume (Erlang) = Total number of subscribers * CS data penetration ratio * CS Data Traffic per
sub per BH * (1 + Proportion of SHO for CS data call)
Iub DL PS Throughput (Mbit/s) = Total number of subscribers * PS (Including R99 and HSPA) Penetration Ratio
* Total PS throughput (HSPA and R99, UL + DL) per sub * Proportion of DL PS throughput * (1 + Proportion of
SHO for PS call * R99 share of DL PS throughput per sub)
Iub UL PS Throughput (Mbit/s) = Total number of subscribers * PS (Including R99 and HSPA) Penetration Ratio
* Total PS throughput (HSPA and R99, UL+DL) per sub * Proportion of UL PS throughput * (1+Proportion of
SHO for PS call)
Iub MBMS throughput (Mbit/s) = Total number of cells * MBMS penetration ratio (Cell) * MBMS Iub
throughput per cell (kbps)/1000
Iub PS Throughput (Mbit/s) = Iub DL PS Throughput + Iub UL PS Throughput + Iub MBMS throughput (Mbit/s)
2
Iub transmission bandwidth
The Iub transmission bandwidth at RNC side includes traffic bandwidth, signaling bandwidth and OAM
bandwidth.
Iub
Iubtraffic
trafficbandwidth
bandwidth
Iub
Iubsignaling
signalingbandwidth
bandwidth
Iub
Iubbandwidth
bandwidth
Iub
IubOAM
OAMbandwidth
bandwidth
Iub DL Traffic Transmission Bandwidth = (Iub voice traffic volume * 12.2 kbit/s * CS voice active factor)/Iub
voice service transmission efficiency + (Iub VP traffic volume * 64 kbit/s)/Iub VP service transmission efficiency
+ (Iub PS DL throughput + Iub MBMS throughput)/Iub PS traffic transmission efficiency
Iub DL Signaling Transmission Bandwidth = Iub DL Traffic Transmission Bandwidth * Iub signaling throughput
ratio per site
Iub UL Traffic Transmission Bandwidth = (Iub voice traffic volume * 12.2 kbit/s * CS voice active factor)/Iub
voice service transmission efficiency + (Iub VP traffic volume * 64 kbit/s)/Iub VP service transmission efficiency
+ Iub PS UL throughput/Iub PS service transmission efficiency
Iub UL Signaling Transmission Bandwidth = Iub UL Traffic Transmission Bandwidth * Iub signaling throughput
ratio per site
Iub OAM transmission bandwidth = Number of BTS sites * Iub OAM throughput per site (kbit/s)/Iub PS service
transmission efficiency
Iub transmission bandwidth = MAX((Iub DL Traffic Transmission Bandwidth + Iub DL Signaling Transmission
Bandwidth + Iub OAM transmission bandwidth), (Iub UL Traffic Transmission Bandwidth + Iub UL Signaling
Transmission Bandwidth + Iub OAM transmission bandwidth))
Generally, the Iub signaling bandwidth can be simplified as approximately 10% of Iub traffic bandwidth.
Iub OAM bandwidth is configurable and the typical recommended value is 64kbps for both uplink and downlink.
The transmission efficiency is related with the transport techniques such as ATM (ATM over E1/T1 or ATM over
STM-1) or IP( IP over E1/T1, IP over STM-1 or IP over FE/GE). For the same services, the transmission
efficiency will be different with different transport techniques.
The following table lists the standard protocol stack for Iub user plane.
Issue V1.0 (2009-12-28)

Page 67 of 77

Iub - ATM (user plane)
PDCP
RLC
Radio Network MAC
Layer
Iub FP
AAL2
Transmission ATM
Network Layer Physical Layer
Iub - IP (user plane)
PDCP
RLC
Radio Network MAC
Layer
Iub FP
UDP
Transmission IP
Network Layer Physical Layer
3.3.2 Iur Interface Dimensioning

Usually we calculate the throughput based on Iub interface throughput as shown in following figure:
Iur transmission bandwidth = Iub transmission bandwidth * 10%.
Notes:
Iur interface throughput is estimated to be 10% of Iub interface throughput.
3.3.3 Iu-CS Interface Dimensioning

Iu-CS interface is the interface between RNC and CN CS domain. It is used to transfer data flow in both control
plane and user plane of CN CS domain.
1
Iu-CS traffic volume
The Iu-CS traffic volume at RNC side includes CS voice traffic and CS VP traffic.
Iu-CS
Iu-CSvoice
voice
Iu-CS
Iu-CStraffic
traffic
Iu-CS
Iu-CSVP
VP
Iu-CS voice traffic volume (Erlang) = Total number of subscribers * CS voice penetration ratio * CS voice call
traffic per sub per BH
Iu-CS VP traffic volume (Erlang) = Total number of subscribers * CS data penetration ratio * CS Data Traffic per
sub per BH
2
Iu-CS transmission bandwidth
The Iu-CS transmission bandwidth at RNC side includes traffic bandwidth and signaling bandwidth.
Iu-CS
Iu-CStraffic
trafficbandwidth
bandwidth
Iu-CS
Iu-CSbandwidth
bandwidth
Iu-CS
Iu-CSsignaling
signalingbandwidth
bandwidth
Issue V1.0 (2009-12-28)

Page 68 of 77

Iu-CS DL Traffic Transmission Bandwidth = (Iu-CS voice traffic volume * 12.2 kbit/s * CS voice active
factor)/(Iu-CS voice service transmission efficiency) + (Iu-CS VP traffic volume * 64 kbit/s)/Iu-CS VP service
Iu-CS DL Signaling Transmission Bandwidth = Iu-CS DL Traffic Transmission Bandwidth * Iu-CS signaling
throughput ratio
Iu-CS UL Traffic Transmission Bandwidth = (Iu-CS voice traffic volume * 12.2 kbit/s * CS voice active
factor)/(Iu-CS voice service transmission efficiency) + (Iu-CS VP traffic volume * 64 kbit/s)/Iu-CS VP service
Iu-CS UL Signaling Transmission Bandwidth = Iu-CS UL Traffic Transmission Bandwidth * Iu-CS signaling
throughput ratio
Iu-CS transmission bandwidth = MAX((Iu-CS DL Traffic Transmission Bandwidth + Iu-CS DL Signaling
Transmission Bandwidth), (Iu-CS UL Traffic Transmission Bandwidth + Iu-CS UL Signaling Transmission
Bandwidth))
Generally, the Iu-CS signaling bandwidth can be simplified as approximately 1% of Iu-CS traffic bandwidth.
The transmission efficiency is related with the transport techniques such as ATM (ATM over STM-1) or IP(IP
over STM-1 or IP over FE/GE). For the same services, the transmission efficiency will be different with different
transport techniques.
The following table lists the standard protocol stack for Iu-CS user plane.
Iu CS - ATM (user plane)

Radio Network Layer Iu UP
AAL2
Transmission
ATM
Network Layer
Physical Layer
Iu CS - IP (user plane)
RTP
UDP
IP
Transmission
Data Link Layer
Network Layer
Physical Layer
3.3.4 Iu-PS Interface Dimensioning

Iu-PS interface is the interface between RNC and CN PS domain. It is used to transfer data flow in both control
plane and user plane of CN PS domain.
1
Iu-PS traffic volume
The Iu-PS traffic volume at RNC side includes PS throughput and MBMS throughput. The MBMS service is
transmitted over the Iu-PS interface. Thus, the MBMS throughput is incorporated into the Iu-PS throughput.
Iu-PS
Iu-PSthroughput
throughput
Iu-PS
Iu-PStraffic
traffic
Iu-PS
Iu-PSMBMS
MBMSthroughput
throughput
Iu-PS DL PS Throughput (Mbit/s) = Total number of subscirbers * PS (Including R99 and HSPA) Penetration
Ratio * Total PS throughput (HSPA and R99, UL + DL) per sub * Proportion of DL PS throughput
Issue V1.0 (2009-12-28)

Page 69 of 77

Iu-PS UL PS Throughput (Mbit/s) = Total number of subscirbers * PS (Including R99 and HSPA) Penetration
Ratio * Total PS throughput (HSPA and R99, UL + DL) per sub * Proportion of UL PS throughput
Iu-PS MBMS throughput (Mbit/s) = MBMS Iu-PS throughput (kbit/s)/1000
2
Iu-PS transmission bandwidth
The Iu-PS transmission bandwidth at RNC side includes traffic bandwidth and signaling bandwidth.
Iu-PS
Iu-PStraffic
trafficbandwidth
bandwidth
Iu-PS
Iu-PSbandwidth
bandwidth
Iu-PS
Iu-PSsignaling
signalingbandwidth
bandwidth
IuPS DL Traffic Transmission Bandwidth = (Iu-PS DL traffic + Iu-PS MBMS throughput)/Iu-PS service
IuPS DL signaling Transmission Bandwidth = IuPS DL Traffic Transmission Bandwidth * Iu-PS signaling
throughput ratio
IuPS UL Traffic Transmission Bandwidth = Iu-PS UL traffic/Iu-PS service transmission efficiency
IuPS UL signaling Transmission Bandwidth = IuPS UL Traffic Transmission Bandwidth * Iu-PS signaling
throughput ratio
IuPS transmission bandwidth = MAX((IuPS DL Traffic Transmission Bandwidth + IuPS DL signaling
Transmission Bandwidth), (IuPS UL Traffic Transmission Bandwidth + IuPS UL signaling Transmission
Bandwidth))
Generally, the Iu-PS signaling bandwidth can be simplified as approximately 1% of IuPS traffic bandwidth.
The transmission efficiencies is related with the transport techniques such as ATM (ATM over E1/T1 or ATM
over STM-1), IP( IP over E1/T1, IP over STM-1, or IP over FE/GE). For the same services, the transmission
efficiency will be different with different transport techniques.
Iu PS - ATM (user plane)

AAL5
Transmission Network ATM
Layer
Physical Layer
Iu PS - IP (user plane)
GTP-U
UDP
IP
Transmission Network Data Link Layer
Layer
Physical Layer
3.4 Counters Related to Capacity

There are following main counters (not limited to) related to capacity which will help you to better understand
your networks status.
VS.CSLoad.Erlang.Equiv.RNC
VS.CSLoad.MaxErlang.Equiv.RNC
VS.R99PSLoad.ULThruput.RNC;
Issue V1.0 (2009-12-28)

Page 70 of 77

VS.R99PSLoad.MaxULThruput.RNC;
VS.HSUPAPSLoad.ULThruput.RNC;
VS.HSUPAPSLoad.MaxULThruput.RNC
VS.R99PSLoad.DLThruput.RNC;
VS.R99PSLoad.MaxDLThruput.RNC;
VS.HSDPAPSLoad.DLThruput.RNC;
VS.HSDPAPSLoad.MaxDLThruput.RNC;
VS.MBMSPSLoad.DLThruput.RNC;
VS.MBMSPSLoad.MaxDLThruput.RNC
Issue V1.0 (2009-12-28)

Page 71 of 77
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.
PSTN
Alarm box
Client 1
Dial-up server
Client 2
Server
Issue V1.0 (2009-12-28)

Page 72 of 77
4.2 O&M solution dimensioning rules

The typical computers for the M2000 server are Sun T5220, Sun M4000, or Sun M5000.
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.
Hardware Platform
1 CPU Sun T5220
Management Capability (Number of

Equivalent NEs)
35
2 CPU Sun M4000
100
4 CPU Sun M4000
190
4 CPU Sun M5000
190
6 CPU Sun M5000
270
8 CPU Sun M5000
340
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.
Number of
NodeBs
Bandwidth requirement (kbit/s)

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:
Issue V1.0 (2009-12-28)

Page 73 of 77

Configuration Level
Sever Configuration
Performance
Space(MB)
Middle configuration
Sun T5220
46,080
Sun T5220
286,720
Large configuration
Sun M4000
286,720
Super configuration
Sun M5000
286,720
Database
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/second)
Sun T5220
90
Sun M4000(2CPU)
400
Sun M4000(4CPU)
510
Sun M5000(4CPU)
700
Sun M5000(6CPU)
940
Sun M5000(8CPU)
1,200
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 T5220
800 000
800 000
100 000
100 000
Sun T5220
(12*450G)
7 000 000
7 000 000
800 000
800 000
Sun M4000
7 000 000
7 000 000
800 000
800 000
Issue V1.0 (2009-12-28)

Page 74 of 77

Server
hardware
Event alarm
History fault
alarm
Current fault
alarm
Shielded
alarm
Sun M5000
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 T5220
20
Sun M4000(2CPU)
50
Sun M4000(4CPU)
85
Sun M5000(4CPU)
90
Sun M5000(6CPU)
100
Sun M5000(8CPU)
125
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
T5220
25
M4000 (2 CPU)
30
M4000 (4 CPU)
60
M5000 (4 CPU)
60
M5000 (6 CPU)
80
M5000 (8 CPU)
100
4.3 O&M hardware and software configuration

4.3.1 Typical M2000 Server Configuration
The typical computers for the M2000 server are Sun T5220, Sun M4000, or Sun M5000. 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.
Issue V1.0 (2009-12-28)

Page 75 of 77

1.
2.
Typical configuration of the M2000 server (single-server system, Sun)

T5220
M4000
M5000
Number of
CPUs
Main
frequency
of the CPU
(GHz)
1.2
2.4
2.4
2.4
2.4
2.4
Memory
(GB)
16
32
32
48
64
Hard disk
(GB)
4 * 146 GB
2 * 146 GB
2 * 146 GB
Disk array
(GB)
N/A
1 x S2600
1 x S2600
(An S2600 disk

array consists of
twelve 450 GB hard
disks)
(An S2600 disk array consists

of twelve 450 GB hard disks)
Accessories
DVD/ Ethernet adapter/DATA 72/ English documentation
Operating
system
Solaris 10/ English documentation
Database
Sybase 15.0.2 or above
Application
software
M2000 server application software
Typical configuration of M2000 server (HA system, Sun)

T5220
M4000
Number of
CPUs
Main
frequency
of the CPU
(GHz)
1.2
2.4
2.4
2.4
2.4
2.4
Memory
(GB)
16
32
32
48
64
Hard disk
(GB)
4 * 146 GB
2 * 146 GB
2 * 146 GB
Disk array
(GB)
2 x S2600
2 x S2600
2 x S2600
(An S2600
disk array
consists of
twelve 450
GB hard
(An S2600 disk

array consists of
twelve 450 GB hard
disks)
(An S2600 disk array consists

of twelve 450 GB hard disks)
Issue V1.0 (2009-12-28)
M5000

Page 76 of 77

disks)
Accessories
DVD/ Ethernet adapter/DATA 72/ English documentation
Operating
system
Solaris 10/ English documentation
Database
Sybase 15.0.2 or above
Application
software
M2000 server application software, SUN Cluster
4.3.2 Common Networking Equipment

The common networking equipments used in the M2000 system are listed below.
Item
Configuration
Router
Quidway AR46-20 and Quidway R28-10/AR28-11
Switch
Quidway S3328TP
Timeslot cross multiplexer
Mecury 3600
4.3.3 Typical M2000 Client Configuration

M2000 client runs on Windows XP. The recommended PC configuration for M2000 client is listed
below.
Item
Configuration
CPU
Intel Core 2 Duo processors.2.5GHz or above
Memory
2 GB
Hard disk
80 GB
Accessories
DVDRW/Ethernet adapter/Sound card/Sound box/19" LCD

display
Operating system
Windows XP professional (or a later version)
Application
software
M2000 client application software
Issue V1.0 (2009-12-28)

Page 77 of 77

Huawei UMTS RAN12.0 Dimensioning Rules V1.0

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Huawei UMTS RAN12.0 Dimensioning Rules V1.0

Transféré par

Droits d'auteur :

Formats disponibles

Huawei UMTS RAN12.

HUAWEI TECHNOLOGIES CO., LTD.

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

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei UMTS RAN12.0 Dimensioning Rules

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

Issue V1.0 (2009-12-28)

Huawei Proprietary and Confidential

Huawei UMTS RAN12.0 Dimensioning Rules

Issue V1.0 (2009-12-28)

Huawei Proprietary and Confidential

Huawei UMTS RAN12.0 Dimensioning Rules

2.1 NodeB V100R012

Subsystem (BTS3812AE Only)

Issue V1.0 (2009-12-28)

Huawei Proprietary and Confidential

Huawei UMTS RAN12.0 Dimensioning Rules

Transport Unit Configurations

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

NUTI with E1 sub

NUTI with unchannelized STM-1 sub

NUTI with channelized

Issue V1.0 (2009-12-28)

Huawei Proprietary and Confidential

Huawei UMTS RAN12.0 Dimensioning Rules

Baseband Unit Configurations

Table 2-2 BTS3812E/BTS3812AE Baseband boards Specification

HSUPA 10ms TTI

Issue V1.0 (2009-12-28)

Huawei Proprietary and Confidential

Huawei UMTS RAN12.0 Dimensioning Rules

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

Table 2-3 BTS3812E/BTS3812AE RF Unit Specification

Control Unit Configurations

2.1.2 BTS3812E/BTS312AE Typical Configuration

Issue V1.0 (2009-12-28)

Huawei Proprietary and Confidential

Huawei UMTS RAN12.0 Dimensioning Rules

(1) MAFU subrack

(2) MTRU subrack

(3) Fan subrack

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

Issue V1.0 (2009-12-28)

Huawei Proprietary and Confidential

Huawei UMTS RAN12.0 Dimensioning Rules

Figure 2-5 The S111, S222 and S333 configurations

Issue V1.0 (2009-12-28)

Huawei Proprietary and Confidential

Huawei UMTS RAN12.0 Dimensioning Rules

Figure 2-6 BTS3812AE in full configuration

Issue V1.0 (2009-12-28)

Huawei Proprietary and Confidential

Huawei UMTS RAN12.0 Dimensioning Rules

2.1.3 BTS3812E/BTS312AE Feature Upgrade Configurations

Upgrade to HSUPA 2ms TTI

Transport Interface Unit

Baseband Processing Unit

WCDMA Main Control Unit

HSUPA Introduction Package (per NodeB)

HSUPA Phase2 (per NodeB)

Upgrade to HSPA+ 64QAM

Transport Interface Unit

Baseband Processing Unit