Beruflich Dokumente
Kultur Dokumente
Dimensioning Rules
Issue
01
Date
2012-07-06
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in 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 a warranty of any kind, express or implied.
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2012-07-06)
UMTS RAN14.0
Dimensioning Rules
Change History
Change History
SN
Date
Revision Description
2012-7-6
RAN14.0 version
Version
Author
Yaoyao 42671
Liyuanjun 50545
Wangyanling 00200183
Yueguojun 37848
Issue 01 (2012-07-06)
ii
UMTS RAN14.0
Dimensioning Rules
Contents
Contents
1 Introduction to UMTS RAN Dimensioning ............................................................................ 1
1.1 Basic Concepts ................................................................................................................................................. 1
1.2 Dimensioning relevant factors.......................................................................................................................... 2
1.3 Impact of the Penetration Rate of Smart Phones and User Behaviors on the Traffic Model ............................ 2
Issue 01 (2012-07-06)
iii
UMTS RAN14.0
Dimensioning Rules
Issue 01 (2012-07-06)
UMTS RAN14.0
Dimensioning Rules
Product
specification
model
Network
configuration
User
Num
feature
The network configuration depends on the following factors. The change of any factor will
necessitate the change of network configuration:
Traffic model: The change in the penetration rate of smart phones and the change in user
behaviors will have an impact on the traffic model.
Number of users: With the development of the network, the number of users will keep
increasing.
Product specification: When a new module or a new board emerges, the product
specification will be improved. As a result, the number of boards on the network will be
reduced.
Feature provisioning: Certain features can enhance the network resource usage. Whether
a feature is provisioned affects the network configuration to some extent.
Canada: The single-user signaling consumption (BHCA) varies with different UE types.
Motorola, HTC, and Samsung generate the largest amount of signaling, up to 14.1, 15.6, and
12.1 respectively.
Issue 01 (2012-07-06)
UMTS RAN14.0
Dimensioning Rules
Issue 01 (2012-07-06)
UMTS RAN14.0
Dimensioning Rules
RAN14.0 includes two NodeB versions: NodeB V100R014 and NodeB V200R014.
NodeB V100R014 includes BTS3812E, BTS3812AE and DBS3800 products.
NodeB V200R014 includes BTS3900, BTS3900A, BTS3900L, BTS3900AL and DBS3900
products.
Transport Subsystem
Baseband Subsystem
RF Subsystem
Control Subsystem
Antenna Subsystem
Issue 01 (2012-07-06)
UMTS RAN14.0
Dimensioning Rules
Figure 2-1
Issue 01 (2012-07-06)
UMTS RAN14.0
Dimensioning Rules
Board type
E1 for
IP
FE
electrica
l
NDTI
NUTI
16
unchanneli
zed STM-1
Channelized
STM-1
Issue 01 (2012-07-06)
UMTS RAN14.0
Dimensioning Rules
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
HBBI
3 cells
128CE
256CE
45 codes
HULP
3 cells
128CE
HSDPA 14.4M
HDLP
6 cells
384CE
90 codes
EBBI/EBOI
6 cells
384CE
384CE
90 codes
EDLP
6 cells
512CE
90 codes
HSPA+ DL 64QAM
EULP
6 cells
384CE
Downlink
R99 CE
HSDPA
Capacity
Feature Support
HSPA+DL MIMO
HSPA+ DL DC-HSDPA
HSPA+ DL DCHSDPA+MIMO(RAN13.0)
EULPd
6 cells
384CE
HSPA+ UL 16QAM
IC
FDE
E-boosting(RAN13.0)
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.
Issue 01 (2012-07-06)
UMTS RAN14.0
Dimensioning Rules
Output power
carriers
MTRU
40W
WRFU
80W
Issue 01 (2012-07-06)
UMTS RAN14.0
Dimensioning Rules
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.
Issue 01 (2012-07-06)
UMTS RAN14.0
Dimensioning Rules
MTRU
MAFU
NMPT
NUTI
NMON
EBBI
1x1
2x1
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
Issue 01 (2012-07-06)
10
UMTS RAN14.0
Dimensioning Rules
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.
MTRU
MAFU
NMPT
NUTI
NMON
EBBI
PSU
1x1
2x1
Issue 01 (2012-07-06)
11
UMTS RAN14.0
Dimensioning Rules
configuration
MTRU
MAFU
NMPT
NUTI
NMON
EBBI
PSU
2x2
3x1
3x2
3x3
3x4
Original Configuration
Additional
Configuration
1NUTI
1HBBI
1EBBI or 1 EULP
RF Module
3MTRU+3MAFU
1NMPT+1NMON
Original Configuration
Additional Configuration
1NUTI
1HBBI+1EBBI
RF Module
3MTRU+3MAFU
1NMPT+1NMON
Issue 01 (2012-07-06)
12
UMTS RAN14.0
Dimensioning Rules
The Baseband Processing Unit (6Cell) supports six cells in the downlink and thus supports six
64QAM cells.
Original Configuration
Additional Configuration
1NUTI
1HBBI+1 EBBI
Add 1EDLP
RF Module
3MTRU+3MAFU
3MTRU+3MAFU
1NMPT+1NMON
Original Configuration
Additional Configuration
1NUTI
1HBBI+1EBBI
Add 1EDLP
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)
Basic Hardware/Software
Original Configuration
Additional Configuration
1NUTI
1HBBI+1EBBI
RF Module
3MTRU+3MAFU
1NMPT+1NMON
DC-HSDPA Function
Issue 01 (2012-07-06)
13
UMTS RAN14.0
Dimensioning Rules
Upgrade to UL 16QAM
Table 2-11 Upgrade from HSUPA phase2 (20W/C) to UL 16QAM (3 x 2 configuration)
Basic Hardware/Software
Original Configuration
Additional Configuration
1NUTI
1HBBI+1EBBI
1EULPd
RF Module
3MTRU+3MAFU
1NMPT+1NMON
UL 16QAM Function
Upgrade to IC
Table 2-12 Upgrade from HSUPA phase2 (20W/C) to IC (3 x 2 configuration)
Basic Hardware/Software
Original Configuration
Additional 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)
Basic Hardware/Software
Original Configuration
Additional Configuration
1NUTI
1HBBI+1EBBI
1EULPd
RF Module
3MTRU+3MAFU
1NMPT+1NMON
FDE Function
Issue 01 (2012-07-06)
14
UMTS RAN14.0
Dimensioning Rules
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)
Basic Hardware/Software
Original Configuration
Additional Configuration
1NUTI
1HBBI+1EBBI
Add 1EDLP
RF Module
3MTRU+3MAFU
3MTRU+3MAFU
1NMPT+1NMON
DL 64QAM+MIMO Function
Original Configuration
Additional Configuration
1NUTI
1HBBI+1EBBI
Add 1EDLP
RF Module
3MTRU+3MAFU
3WRFU
1NMPT+1NMON
DL 64QAM+MIMO Function
Upgrade to DL DC-HSDPA+2xMIMO(RAN13.0)
Table 2-16 Upgrade from DL 64QAM+MIMO(2x10W/C) to DL DC-HSDPA+2xMIMO
(2x10W/C) (3 x 2 configuration, WRFU)
Basic Hardware/Software
Original Configuration
Additional Configuration
1NUTI
1HBBI+1EBBI
ADD 2EDLP+1EULPd
RF Module
6WRFU
Issue 01 (2012-07-06)
15
UMTS RAN14.0
Dimensioning Rules
Basic Hardware/Software
Original Configuration
Additional Configuration
1NMPT+1NMON
DL DC-HSDPA Function
DL DC-HSDPA+MIMO function
Original Configuration
Additional Configuration
1NUTI
1HBBI+1EBBI
Add 2EDLP+1EULPd
RF Module
3WRFU
Add 3WRFU
1NMPT+1NMON
DL DC-HSDPA Function
DL DC-HSDPA+MIMO function
Original Configuration
Additional Configuration
1NUTI
1HBBI+1EBBI
RF Module
3MTRU+3MAFU
1NMPT+1NMON
HSUPA Function
DC-HSUPA Function
Issue 01 (2012-07-06)
16
UMTS RAN14.0
Dimensioning Rules
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.
Figure 2-7 Function modules of the DBS3800
Description
BBU3806
BBU3806C
RRU3801C
RRU3804
RRU3801E
RRU3808
Issue 01 (2012-07-06)
17
UMTS RAN14.0
Dimensioning Rules
E1 for ATM
E1 for IP
FE
unchannelized STM-1
electrical
BBU3806
UBTI
Cell
Uplink
R99/HSUPA
BBU3806
3 cells
192CE
Downlink
R99 CE
HSDPA
Capacity
256CE
45 codes
(When BBU
active HSUPA,
128CE)
BBU3806+EBBC
6 cells
384CE
Feature Support
HSDPA 14.4M
HSUPA 10ms TTI
512CE
90 codes
(When BBU
active HSUPA,
320CE)
BBU3806+EBBCd
6 cells
384CE
512CE
90 codes
(When BBU
active HSUPA,
320CE)
Issue 01 (2012-07-06)
HSPA+ UL 16QAM
IC
FDE
E-boosting(RAN13.0)
18
UMTS RAN14.0
Dimensioning Rules
RF Unit Configurations
The RRU is classified into the RRU3804, RRU3801C, RRU3801E, RRU3808, RRU3828,
RRU3829 based on different output power and processing capabilities. The
RRU3808,RRU3828 and RRU3829 support two RX channels and two TX channels.
DBS3800 support RRU3808 in V100R011, and RRU3828, RRU3829 in V100R013
Table 2-22 DBS3800 RRU Specification
RRU Type
RRU3804
RRU3801C
RRU3801E
RRU3808
RRU3828
RRU3829
Maximum Output
Power
60W
40W
40W
2x40W
2x40W
2x60W
Number of Supported
Carriers
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.
The RRU3828 supports 2T2R with two Tx channels. The maximum radio output power per
channel is 40 W. One RRU3828 can support 4 carriers within 60M frequency bandwidth, per
carrier 20W.
The RRU3829 supports 2T2R with two Tx channels. The maximum radio output power per
channel is 60 W. One RRU3829 can support 4 carriers within 60M frequency bandwidth, per
carrier 30W.
For MIMO, transmit diversity configuration, two RRU3804s/RRU3801Cs /RRU3801Es
should be configured within one sector, or one RRU3808/RRU3829 should be configured
within one sector.
For 4-way receive diversity configuration, two RRUs should be configured within one sector.
Issue 01 (2012-07-06)
19
UMTS RAN14.0
Dimensioning Rules
Table 2-23 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
Number of EBBCs
Minimum
Number of 40 W
RRUs
1x1
2x1
2x2
3x1
3x2
3x3
3x4
Table 2-24 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
Number of EBBCs
Minimum
Number of 60 W
RRUs
1x1
2x1
2x2
3x1
3x2
3x3
3x4
Original Configuration
Additional
Configuration
BBU Unit
1BBU3806
1EBBC
RF Module
3RRU3801C
Issue 01 (2012-07-06)
20
UMTS RAN14.0
Dimensioning Rules
Basic Hardware/Software
Original Configuration
Additional
Configuration
Original Configuration
Additional Configuration
BBU Unit
2BBU3806
1EBBC
RF Module
3RRU3801C
The Baseband Processing Unit (6Cell) supports six cells in the downlink and thus supports six
64QAM cells.
Original Configuration
Additional Configuration
BBU Unit
2BBU3806
2EBBC
RF Module
3RRU3801C
3RRU3804 or RRU3801E
Original Configuration
Additional Configuration
BBU Unit
2BBU3806
2EBBC
RF Module
3RRU3801C
3RRU3804 or RRU3801E
In MIMO mode, both the Baseband Processing Unit (6Cell) and the Baseband Processing
Unit (3Cell) support MIMO on a maximum of three cells.
Issue 01 (2012-07-06)
21
UMTS RAN14.0
Dimensioning Rules
Upgrade to DC-HSDPA
Table 2-29 Upgrade from 64QAM to DC-HSDPA+64QAM (3 x 2 configuration, 20 W per carrier)
Basic Hardware/Software
Original Configuration
Additional Configuration
BBU Unit
1BBU3806+1EBBC
RF Module
3RRU3801C
DC-HSDPA Function
Upgrade to UL 16QAM
Table 2-30 Upgrade from HSUPA phase2 (20W/C) to UL 16QAM (3 x 2 configuration)
Basic Hardware/Software
Original Configuration
Additional Configuration
BBU Unit
1BBU3806+1EBBC
1BBU3806+1EBBCd
RF Module
3RRU3801C
UL 16QAM Function
Upgrade to IC
Table 2-31 Upgrade from HSUPA phase2 (20W/C) to IC (3 x 2 configuration)
Basic Hardware/Software
Original Configuration
Additional Configuration
BBU Unit
1BBU3806+1EBBC
1BBU3806+1EBBCd
RF Module
3RRU3801C
IC Function
Upgrade to FDE
Table 2-32 Upgrade from HSPA phase2 (20W/C) to FDE (3 x 2 configuration)
Basic Hardware/Software
Original Configuration
Additional Configuration
BBU Unit
1BBU3806+1EBBC
1BBU3806+1EBBCd
RF Module
3RRU3801C
FDE Function
Issue 01 (2012-07-06)
22
UMTS RAN14.0
Dimensioning Rules
Upgrade to DL 64QAM+MIMO
Table 2-33 Upgrade from DL 64QAM(20W/C) to DL 64QAM+MIMO (10W+10W/C) (3 x 2
configuration)
Basic Hardware/Software
Original Configuration
Additional Configuration
BBU Unit
2BBU3806+1EBBC
1EBBC
RF Module
3RRU3801C
3RRU3804 or RRU3801E
DL 64QAM+MIMO Function
Original Configuration
Additional Configuration
BBU Unit
2BBU3806+1EBBC
1EBBC
RF Module
3RRU3801C
DL 64QAM+MIMO Function
Upgrade to DL DC-HSDPA+1*MIMO(RAN13.0)
Table 2-35 Upgrade from DL 64QAM+MIMO(2*10W/C) to DL DC-HSDPA+1*MIMO (3 x 2
configuration, RRU3808)
Basic Hardware/Software
Original Configuration
Additional Configuration
BBU Unit
1BBU3806+1EBBC
Add 1BBU3806+1EBBC
RF Module
3RRU3808
DC-HSDPA Function
DL DC-HSDPA+MIMO Function
Issue 01 (2012-07-06)
23
UMTS RAN14.0
Dimensioning Rules
Original Configuration
Additional Configuration
BBU Unit
2BBU3806+1EBBC
1EBBC
RF Module
3RRU3801C
DL DC-HSDPA+MIMO Function
Upgrade to DL DC-HSDPA+1xMIMO(RAN14.0)
Table 2-37 Upgrade from HSUPA to UL DC-HSUPA (3 x 2 configuration, 20W/carrier)
Basic Hardware/Software
Original Configuration
Additional Configuration
BBU Unit
1BBU3806+1EBBC
RF Module
3RRU3801C
HSUPA Function
DC-HSUPA Function
Issue 01 (2012-07-06)
24
UMTS RAN14.0
Dimensioning Rules
Figure 2-8 Units and auxiliary devices of the 3900 series NodeBs
Issue 01 (2012-07-06)
25
UMTS RAN14.0
Dimensioning Rules
Different combinations of the units and auxiliary devices form the following 3900 series
NodeBs:
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.
Issue 01 (2012-07-06)
26
UMTS RAN14.0
Dimensioning Rules
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.
Slot 0
Slot 1
Slot 2
Slot 3
Slot 4
Slot 5
Slot 6
Slot 7
WMPT
available
available
UMPTa1
available
available
UTRP
available
available
available
available
UTRPc
available
available
available
available
UCIU
available
available
WBBP
available
available
available
available
available
available
UELP
available
available
available
available
available
available
Issue 01 (2012-07-06)
available
available
27
UMTS RAN14.0
Dimensioning Rules
Board
Slot 0
Slot 1
Slot 2
Slot 3
Slot 4
Slot 5
Slot 6
Slot 7
UFLP
available
available
available
available
available
available
available
available
One WMPT/UMPT 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.
E1
for
AT
M
WMPT
UTRP3
UTRP4
UTRP6
E1 for
IP
FE
FE
elect
rical
optical
unchann
elized
STM-1
FE/GE
electrica
l
8
1
UTRP9
UTRP2
UTRPc
Issue 01 (2012-07-06)
FE/GE
Optical
28
UMTS RAN14.0
Dimensioning Rules
Cell
Upli
nk
R99/
HSU
PA
CE
Dow
nlin
k
R99
CE
HSDPA
Capacity
Feature Support
HSDPA
Users
HSUPA
Users(1
0ms
TTI,SR
B over
HSUPA
)
HSUPA
Users(2m
s
TTI,SRB
over
HSUPA)
WBBPa
3 cells
128
256
45 codes
96
60
Not
Support
HSDPA
WBBPb1
3 cells
64
64
45 codes
64
64
WBBPb2
3 cells
128
128
45 codes
HSPA+ DL 64QAM
128
96
144
96
32
144
96
48
HSPA+DL MIMO
WBBPb3
6 cells
256
256
90 codes
WBBPb4
6 cells
384
384
90 codes
HSPA+ DL DCHSDPA
DCHSDPA(RAN13.0)
WBBPd1
WBBPd2
6 cells
6 cells
192
384
192
384
90 codes
HSPA+ UL 16QAM
128
96
24
90 codes
IC
144
96
48
144
96
32
-*
-*
-*
FDE
WBBPd3
6 cells
256
256
90 codes
WBBPf1
6 cells
192
256
90 codes
Issue 01 (2012-07-06)
E-boosting(RAN13.0)
29
UMTS RAN14.0
Dimensioning Rules
Board
Type
Cell
Upli
nk
R99/
HSU
PA
CE
Dow
nlin
k
R99
CE
HSDPA
Capacity
HSDPA
Users
HSUPA
Users(1
0ms
TTI,SR
B over
HSUPA
)
HSUPA
Users(2m
s
TTI,SRB
over
HSUPA)
WBBPf2
6 cells
256
384
90 codes
-*
-*
-*
WBBPf3
6 cells
384
512
90 codes
-*
-*
-*
WBBPf4
6 cells
512
768
90 codes
-*
-*
-*
Feature Support
*: The number of HSDPA and HSUPA users of WBBPf board is in the planning.
Board Type
HSDPA
Capacity per
Cell
HSDPA
Capacity per
Cell with CPC
HSUPA Capacity
per Cell with CPC
WBBPa
64 users
Not Support
20 users
Not Support
WBBPb1
64 users
64 users
60 users
64 users
WBBPb2
64 users
96 users
60 users
96 users
WBBPb3
64 users
96 users
60 users
96 users
WBBPb4
64 users
96 users
60 users
96 users
WBBPd1
64 users
96 users
60 users
96 users
WBBPd2
64 users
128 users
60 users
128 users
WBBPd3
64 users
128 users
60 users
128 users
WBBPf1
64 users
128 users
60 users
128 users
WBBPf2
64 users
128 users
60 users
128 users
WBBPf3
64 users
128 users
60 users
128 users
WBBPf4
64 users
128 users
60 users
128 users
CCH R99 included, 16CE for downlink and 6 CE for uplink for 3 cells
TX diversity is no impact for CE consumption for both uplink and downlink direction.
Issue 01 (2012-07-06)
30
UMTS RAN14.0
Dimensioning Rules
Resources for HS-DSCH, HS-SCCH and HS-DPDCH included, HSDPA services not
affect BB capacity for R99 services.
DBS3900V200R
010C01SPC510/
DBS3900V200R
011C00SPC320
DBS3900V
200R012C0
0SPC200
DBS3900V2
00R012C00S
PC420(2011.
04)
DBS3900V200R01
3C00SPC200(2011.
05)
WMPT+1
WBBPb/d
30 CNBAP/s
40 CNBAP/s
45
CNBAP/s
55 CNBAP/s
60 CNBAP/s
WMPT+2
WBBPb/d
50 CNBAP/s
80 CNBAP/s
100
CNBAP/s
110
CNBAP/s
120 CNBAP/s
WMPT+3
WBBPb/d
50 CNBAP/s
80 CNBAP/s
100
CNBAP/s
130
CNBAP/s
170 CNBAP/s
WMPT+4
WBBPb/d
50 CNBAP/s
80 CNBAP/s
100
CNBAP/s
130
CNBAP/s
170 CNBAP/s
WMPT+5
WBBPb/d
NA
NA
NA
NA
170 CNBAP/s
WMPT+6
WBBPb/d
NA
NA
NA
NA
170 CNBAP/s
UTRP+W
MPT+1W
BBPb/d
30 CNBAP/s
40 CNBAP/s
45
CNBAP/s
55 CNBAP/s
60 CNBAP/s
UTRP+W
MPT+2W
BBPb/d
50 CNBAP/s
80 CNBAP/s
100
CNBAP/s
110
CNBAP/s
120 CNBAP/s
UTRP+W
MPT+3W
BBPb/d
60 CNBAP/s
130 CNBAP/s
130
CNBAP/s
165
CNBAP/s
180 CNBAP/s
UTRP+W
MPT+4W
BBPb/d
60 CNBAP/s
170 CNBAP/s
170
CNBAP/s
200
CNBAP/s
240 CNBAP/s
UTRP+W
MPT+5W
BBPb/d
NA
NA
NA
NA
250 CNBAP/s
Issue 01 (2012-07-06)
31
UMTS RAN14.0
Dimensioning Rules
760
UMPT+6xWBBPb/d
707
UMPT+6xWBBPf
1500
U
F
A
N
WBBP
WBBP
WBBP
WBBPf
UCIU
WBBP
WMPT
UPEU
U
F
A
N
WBBP
WBBPf
UMPT
UPEU
Issue 01 (2012-07-06)
32
UMTS RAN14.0
Dimensioning Rules
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.
In RAN13.0, the WRFUd module is added. The WRFUd supports 2T2R, 4 carriers, with two
Tx channels. The maximum radio output power per channel is 60W.
RRU3804
RRU3801C
RRU3801E
RRU3808
RRU3828
RRU3829
Maximum
Output
Power
60W
40W
40W
2x40W
2x40W
2x60W
Number
of
Supported
Carriers
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.
Issue 01 (2012-07-06)
33
UMTS RAN14.0
Dimensioning Rules
The RRU3828 supports 2T2R with two Tx channels. The maximum radio output power per
channel is 40 W. One RRU3828 can support 6 carriers within 60M frequency bandwidth, per
carrier 13W
The RRU3829 supports 2T2R with two Tx channels. The maximum radio output power per
channel is 60 W. One RRU3829 can support 6 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/RRU3829 should be configured
within one sector.
For 4-way receive diversity configuration, two RRUs should be configured within one sector.
BTS3900 /BTS3900 (Ver.C) Cabinet can support up to 24 cells. There can be configured
as Omni directional, 2-sector, 3-sector and 6-sector configurations.
BTS3900 /BTS3900 (Ver.C) Cabinet supports dual band configurations by a free mix of
WRFU types for any frequency band connected to the baseband Unit.
Issue 01 (2012-07-06)
34
UMTS RAN14.0
Dimensioning Rules
UEs, you can upgrade the system to large-capacity configurations such as 3 x 2 and 3 x 4
smoothly.
Table 2-44 Recommended configurations of the BTS3900
Per
carrier
20W
Minimum # of
Indoor Cabinet
Minimum #
of WMPT
Minimum # of
WBBPd
Minimum #
of RFU
1 1
1 2
1 3
1 4
2 1
2 2
2 3
2 4
3 1
3 2
3 3
3 4
6 1
6 2
3 5
3 6
3 7
3 8
6 3
6 4
Issue 01 (2012-07-06)
35
UMTS RAN14.0
Dimensioning Rules
Minimum # of
Cabinet
Minimum # of
WMPT
Minimum # of
WBBPd
Minimum #
of WRFU
1 1
One APM30,
1 2
One 6RF
cabinet,
1 3
One battery
cabinet
2 1
2 2
2 3
2 4
3 1
3 2
1 4
Issue 01 (2012-07-06)
36
UMTS RAN14.0
Dimensioning Rules
Per carrier
20W
Minimum # of
Cabinet
Minimum # of
WMPT
Minimum # of
WBBPd
Minimum #
of WRFU
3 3
3 4
6 1
6 2
3 5
3 6
3 7
3 8
6 3
6 4
Issue 01 (2012-07-06)
37
UMTS RAN14.0
Dimensioning Rules
Issue 01 (2012-07-06)
38
UMTS RAN14.0
Dimensioning Rules
Configuration
Number of Modules
Output Power of
Each Carrier
UMTS
S4/4/4
3 WRFU
20 W
S4/4/4 (MIMO)
3 WRFUd
30 W (2 x 15 W)
S4/4/4
3 MRFU
20 W
S4/4/4 (MIMO)
3 MRFUd
40 W (2 x 20 W)
Issue 01 (2012-07-06)
39
UMTS RAN14.0
Dimensioning Rules
The preceding configurations assume that each cell uses one dual-polarized antenna.
BTS3900L or BTS3900L (Ver.C) cabinets are mainly used in scenarios where multiple
frequency bands are applied and multiple modes co-exist. Table 2-46 lists typical
configurations of a multi-mode BTS3900L or BTS3900L (Ver.C) cabinet.
BTS3900AL
The BTS3900AL is introduced in V200R014.
A BTS3900AL cabinet performs power distribution and surge protection. It consists of
BBU3900s and RFUs. As a high-integration outdoor site solution, the BTS3900AL cabinet
houses a maximum of two BBU3900s and nine RFUs to save installation space and ensure
smooth evolution.
Figure 2-16 shows the internal structure of a BTS3900AL cabinet.
Figure 2-16 Internal structure of a BTS3900AL cabinet
Issue 01 (2012-07-06)
40
UMTS RAN14.0
Dimensioning Rules
Typical
Configurations
Number of RF
Modules
Output Power
of Each Carrier
GU
3 MRFUd (GO) + 3
MRFUd (GO) + 3
WRFU (UO)
20 W + 20 W +
40 W
3 MRFUd (GU) + 3
MRFUd (GO) + 3
WRFUd (UO)
20 W + 40 W +
20 W + 80 W (2
x 40 W)
3 GRFU (GO) + 3
GRFU (GO) + 3 LRFU
(LO)
20 W + 80 W (2
x 40 W)
6 MRFU (GL) + 3
LRFU (LO)
20 W + 2 x 20 W
+ 80 W (2 x 40
W)
3 MRFUd (GO) + 3
LRFU (LO)
20 W + 120 W (2
x 60 W)
3 WRFU + 3 MRFU
(LO)
40 W + 80 W (2
x 40 W)
GL
UL
3 MRFU (UO) + 3
MRFU (LO)
UMTS S2/2/2 (MIMO)
+ LTE 3 x 20 MHz
(4T4R)
3 WRFUd + 6 LRFU
GU+L/GL+U
(independent
BBUs)
3 MRFUd (UO) + 3
WRFUd + 3 MRFUd
(LO)
20 W + 80 W (2
x 40 W) + 120 W
(2 x 60 W)
GU+L/GL+U
(interconnecte
d BBUs)
3 MRFUd (GU) + 3
MRFUd (GL) + 3
WRFU
20 W + 40 W (2
x 20 W) + 20 W
+ 40 W (2 x 20
W) + 80 W (2 x
40 W)
Issue 01 (2012-07-06)
3 MRFUd (UO) + 6
MRFUd (LO)
80 W (2 x 40 W)
+ 80 W (2 x 40
W)
41
UMTS RAN14.0
Dimensioning Rules
The preceding configurations assume that each cell uses one dual-polarized antenna.
In Table 2-47, GU indicates that GSM and UMTS share one BBU, GL indicates that GSM and LTE
share one BBU, and UL indicates that UMTS and LTE share one BBU; GU+L indicates that GSM
and UMTS share one BBU and LTE uses another BBU, and GL+U indicates that GSM and LTE
share one BBU and UMTS uses another BBU.
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-17 DBS3900 full configuration
Minimum # of
WMPT
Minimum # of
WBBPd
Minimum # of
RRU3804
1 1
1 2
1 3
2 1
2 2
2 3
3 1
Issue 01 (2012-07-06)
42
UMTS RAN14.0
Dimensioning Rules
Per carrier
20W
Minimum # of
WMPT
Minimum # of
WBBPd
Minimum # of
RRU3804
3 2
3 3
6 1
6 2
3 5
3 6
6 3
BTS3900C
The compact mini NodeB known as the BTS3900C consists of one BBU3900C (BBU3900
with a mini outdoor cabinet) and one RRU3804.
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.
Original Configuration
Additional Configuration
RF Module
1 WBBPb (6Cell)
The Baseband Processing Unit (6Cell) supports six cells in the downlink and thus supports six
64QAM cells.
Issue 01 (2012-07-06)
43
UMTS RAN14.0
Dimensioning Rules
Original Configuration
Additional Configuration
1 WBBPb (6Cell)
1 WBBPb or WBBPd
Original Configuration
Additional Configuration
RRU3808
1 WBBPb (6Cell)
1 WBBPb or WBBPd
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-52 Upgrade from 64QAM to DC-HSDPA+64QAM (3 x 2 configuration, 20 W per carrier)
Basic Hardware/Software
Original Configuration
Additional Configuration
RF Module
1 WBBPb (6Cell)
WMPT
DC-HSDPA Function
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.
Issue 01 (2012-07-06)
44
UMTS RAN14.0
Dimensioning Rules
Upgrade to UL 16QAM
Table 2-53 Upgrade from HSUPA phase2 (20W/C) to UL 16QAM (3 x 2 configuration)
Basic Hardware/Software
Original Configuration
Additional Configuration
RF Module
1 WBBPb (6Cell)
1 WBBPd
WMPT
UL 16QAM Function
Upgrade to IC
Table 2-54 Upgrade from HSUPA phase2 (20W/C) to IC (3 x 2 configuration)
Basic Hardware/Software
Original Configuration
Additional Configuration
RF Module
1 WBBPb (6Cell)
1 WBBPd
WMPT
IC Function
Upgrade to FDE
Table 2-55 Upgrade from HSPA (20W/C) to FDE (3 x 2 configuration)
Basic Hardware/Software
Original Configuration
Additional Configuration
RF Module
1 WBBPb (6Cell)
1 WBBPd
WMPT
FDE Function
Issue 01 (2012-07-06)
45
UMTS RAN14.0
Dimensioning Rules
Upgrade to DL 64QAM+MIMO
Table 2-56 Upgrade from DL 64QAM(20W/C) to DL 64QAM+MIMO (10W+10W/C) (3 x 2
configuration)
Basic Hardware/Software
Original Configuration
Additional Configuration
1 WBBPb (6Cell)
1 WBBPb or WBBPd
WMPT
DL 64QAM+MIMO Function
Original Configuration
Additional Configuration
RRU3808
1 WBBPb (6Cell)
1 WBBPb or WBBPd
WMPT
DL 64QAM+MIMO Function
Upgrade to DL DC-HSDPA+2xMIMO(RAN13.0)
Table 2-58 Upgrade from DL 64QAM+MIMO(2x10W/C) to DL DC-HSDPA+2xMIMO
(2x10W/C) (3 x 2 configuration, RRU3808)
Basic Hardware/Software
Original Configuration
Additional Configuration
RF Module
2 WBBPb (6Cell)
1 WBBPb or 1WBBPd
WMPT
DL DC-HSDPA Function
Issue 01 (2012-07-06)
46
UMTS RAN14.0
Dimensioning Rules
Basic Hardware/Software
Original Configuration
Additional Configuration
DL DC-HSDPA+MIMO function
Original Configuration
Additional Configuration
RF Module
1 WBBPb (6Cell)
2 WBBPb or 2WBBPd
WMPT
DL DC-HSDPA Function
DL DC-HSDPA+MIMO function
Original Configuration
Additional Configuration
RF Module
1 WBBPd2
WMPT
HSUPA Function
DC-HSUPA Function
RAN13.0 includes two NodeB versions: NodeB V100R013 and NodeB V200R013.
NodeB V100R013 includes BTS3812E, BTS3812AE and DBS3800 products.
NodeB V200R013 includes BTS3900, BTS3900A and DBS3900 products.
Issue 01 (2012-07-06)
47
UMTS RAN14.0
Dimensioning Rules
Section 2.3.3, 2.3.4 introduces the main principle about PS and R99 capacity
dimensioning.
Section 2.3.6 introduces the main principle for HSUPA capacity dimensioning
Section 2.3.8 presents us the principle about mixed services capacity dimensioning.
Issue 01 (2012-07-06)
48
UMTS RAN14.0
Dimensioning Rules
the loading threshold of final CS service which includes the traffic Erlangs from CS/VOIP
/PTT over HSPA is 90% in downlink and 75% in uplink.
Step 1 Calculation of CS peak cell load LoadCS 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:
Figure 2-18 Multidimensional Erlang B Model
Calls
arrival
multiservice
Calls
completion
Blocked
calls
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.
Figure 2-19 Partitioning Resources vs. Resources Shared
ErlangB - Partitioning Resources
49
UMTS RAN14.0
Dimensioning Rules
MDE
LoadCS avg
i:
(1)
(2)
Where,
N user
TrafficPerUseri
Load
LoadCS avg
CS peak
The
and
exceed loading threshold.
Issue 01 (2012-07-06)
50
UMTS RAN14.0
Dimensioning Rules
ERL average cell load here means the average loading consumption of R99 CS services and
traffic from CS/VOIP /PTT over HSPA.
LoadERL avg
LoadPTToverHSP Aavg
(3)
Where,
LoadCS avg
LoadCSoverHSPA avg
LoadPTToverHSP Aavg
Calculation of
LoadCS avg
(4)
(5)
Downlink:
On downlink the calculation of load should consider the ratio of SHO.
(6)
Where,
N user
TrafficPerUseri
Issue 01 (2012-07-06)
51
UMTS RAN14.0
Dimensioning Rules
(7)
Where,
TrafficUser _ i
UserNumCell
is the traffic model of CS over HSPA users in one cell, unit: Erlang
is the total number of CS over HSPA users in one cell.
Uplink:
(8)
Downlink:
(9)
(10)
Where,
TrafficUser _ i
UserNumCell
is the traffic model of VOIP over HSPA users in one cell, unit: Erlang
is the total number of VOIP over HSPA users in one cell.
Uplink:
(11)
Downlink:
(12)
(13)
Where,
TrafficUser _ i
UserNumCell
Issue 01 (2012-07-06)
is the traffic model of PTT over HSPA users in one cell, unit: Erlang
is the total number of PTT over HSPA users in one cell.
52
UMTS RAN14.0
Dimensioning Rules
Uplink:
(14)
Downlink:
(15)
LoadPS Avg
(16)
Where
N channelsi
N channelsi
(17)
Downlink
LoadCS peak
}+
LoadCCH _ UL + LoadRRC
Issue 01 (2012-07-06)
LoadCS peak
}+
(19)
53
UMTS RAN14.0
Dimensioning Rules
LoadRRC is the loading during radio resource control success establish of RAB success
establish .
Either of them exceeds the threshold would drive the iteration procedure.
Cell coverage
radius
Simulation
Power and
Code for
HSDPA
Ior/Ioc distribution
Ec/Io distribution
Ec/Io =>throughput
Cell average
throughput
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
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
Issue 01 (2012-07-06)
Ratek Pr obIocIor _ k
54
UMTS RAN14.0
Dimensioning Rules
Of course, the required power of HSDPA to guarantee HSDPA cell average throughput
requirement can also be calculated.
Cell coverage
radius
User rate at
distance R
Ec/N0
Ec/N0
Uplink
load
HSUP Aactual
cell load
load of
per User
at random
location R
HS-DPCCH load
R99 load
A-HSDPA load
User Maximum
rate at the load
HSUPA cell
throughput
Code&Users
capacity
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
during of cell radius and the users throughput at average load and users capacity, then we
need to calculate the uplink HSUPA cell throughput by the following formulas:
ThCell Ratek
Sk
S
Where,
Ratek
, then the maximum Ec/No achieved with this maximum given loading could be
calculated by this formula:
Issue 01 (2012-07-06)
55
UMTS RAN14.0
Dimensioning Rules
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.
Power consumption for each MBMS channel at air interface can be calculated by the
following formula:
/ 10
) /(10 PBS / 10 )
(20)
Where,
Issue 01 (2012-07-06)
56
UMTS RAN14.0
Dimensioning Rules
Thus the total loading of all the MBMS channels within one cell can be calculated by the
following formula:
(21)
Where,
According to the previous calculation we can obtain the actual total cell load by the formulas:
Loadcell total _ UL max{ LoadERL peak , LoadERL avg LoadPS avg LoadHSUPA LoadAHSDPA _ UL }
+
LoadCCH _ UL
+ LoadRRC
Loadcell total _ DL max{ LoadERL peak , LoadERL avg LoadPS avg LoadHSDPA Load AHSUPA _ DL LoadSRB }
LoadCCH _ DL LoadMBMS
LoadRRC
LoadRRC is the loading during radio resource control success establish of RAB success
establish .
Issue 01 (2012-07-06)
57
UMTS RAN14.0
Dimensioning Rules
CE factors means: The number of CEs needed by one connection for each specific radio bearer.
TTI = 10ms
TTI = 2ms
CS over HSPA
1(V2 NodeB)
1.5(V1NodeB)
NOTE
Issue 01 (2012-07-06)
58
UMTS RAN14.0
Dimensioning Rules
N users )
CEErl _ 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:
TrafficPerUseri
(1)
R SHO
is Soft Handover ratio. Please be aware that the CS/VOIP over HSPA and PTT over
HSPA services dont support soft handover, thus this value should be zero for CS/VOIP over
HSPA and PTT over HSPA services.
CE Consumption on UL
CE Consumption on DL
AMR 12.2kbps
CS 64kbps
PS 64kbps
Issue 01 (2012-07-06)
59
UMTS RAN14.0
Dimensioning Rules
Bearer Type
CE Consumption on UL
CE Consumption on DL
PS 128kps
PS 144kps
PS 256kbps
10
PS 384kbps
10
CEPS _ Avg =
(1 RSHO ) (1 RBurstrate )
i
Nusers ThroughputPerUseri
(1 RRe tranrate _ i ) i
Ri i 3600
(2)
Where,
RBurstrate
ThroughputPerUseri (kbit): The busy hour throughput per user for service i .
CEHSDPA _ UL
On the uplink, uplink A-DCH (associated DCH) can be used for signaling 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.
CE
HSDPA _ UL
Number of uplink CEs for HSDPA (
) can be calculated according to number of
simultaneously connected HSDPA users ( N HSDPA _ Links ) and CE factors. Table 2-63 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:
ThroughputTr _ HSDPA
N HSDPA _ Links
(3)
Where,
Issue 01 (2012-07-06)
60
UMTS RAN14.0
Dimensioning Rules
N HSDPA _ Links
ThroughputTr _ HSDPA
RateAvg _ HSDPA _ Data
Thus the final CE consumption of the A-DCH links of HSDPA services could be calculated by
the following formulas:
CEHSDPA _ UL
Where
= N HSDPA _ Links x
(4)
Table 2-63 UL A-DCH bearer rate and CE factor of HSDPA services mapping
HSDPA
AveRate
(kbps)
UL A-DCH
Bearer Rate
128
16
384
32
1.5
3600
64
7200
128
14400
384
10
28000
512
42000
1024
16
UL A-DCH CE
(over DCH)
UL A-DCH
CE
(over HSUPA)
CEHSDPA _ 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.
Issue 01 (2012-07-06)
61
UMTS RAN14.0
Dimensioning Rules
HSUPA MAC-e
Rate(kbps)
CE
TTI = 10ms
TTI = 2ms
SF32
35.4
35.4
SF16
69
69
SF8
136.2
136.2
SF4
709.2
709.2
2xSF4
1448.4
1353
16
2xSF2
1986
2874
32
2xSF2+2xSF4
Cat6: 5730
48
Cat7: 4059
2xM2+2xM4
11498
64
For the HSUPA users without R99 services, the signaling is mapped to a DCH, thus one CE is
consumed. However, the signaling of the HSUPA will not consume any CE resources when
enabling SRB over HSUPA function.
For the HSUPA users with R99 services, the R99 services and signaling are mapped to one
DCH. Thus, the CE consumption of the R99 services channel includes the signaling CE
consumption.
When introducing HSUPA, the E-AGCH, E-RGCH and E-HICH are added in downlink
channels. The E-AGCH is the common channel. The E-RGCH and the E-HICH are dedicated
channels. However one code can be shared by multiple users. The processing of these three
channels is independent. Thus no R99 CE resource is consumed.
If the DL associated channel of the HSUPA is the R99 channels, the R99 CE resources is
consumed according to the actual speed rate. Considering when the UE UL channel uses the
HSUPA, the DL channel is using the HSDPA, and then the CE resources are not consumed.
The introduction of the HSUPA improves user satisfaction and the UL throughput. However,
due to the adoption of the hybrid automatic repeat request (HARQ) and SHO, the CE resource
consumption is largely increased. The fixed allocation mode means that allocating CE
resources according to the maximum set of E-DPDCHs no matter the actual rate of
subscribers. The maximum set of E-DPDCHs is configured on the RNC by the user when the
radio link is established.
The CE resources allocation based on the Maximum Set of the E-DPDCHs has two
disadvantages:
1. The CE resources are wasted.
2. The CE resources will become the bottleneck of the HSUPA performance.
Therefore, a more effective allocation method for the CE resources is required.
Huawei NodeB supports the dynamic CE resources management of the HSUPA, which helps
to use the CE resources effectively. The NodeB allocates the initial CE resources to each user
Issue 01 (2012-07-06)
62
UMTS RAN14.0
Dimensioning Rules
based on the GBR information. Then, the NodeB adjusts the CEs allocated to the users based
on the actual CE number, allocated CE number, priority of users, and actual rate of users.
When the CE resources are insufficient because of access of new users, the preemption is
triggered. To guarantee the equality of the preemption, factors such as the priority of users and
the GBR satisfaction degree are considered.
1.
(5)
Wherein,
Link sHSUPA
ThroughputPerNodeBHSUPA (k bit)
* (1 SHOfactor) * (1 Re transmission)
AverageThroughputPerUserHSUPA (k bit)
* (1 Burstratio)
(6)
Considering the impact on CE consumption of soft handover overhead, HSUPA traffic burst
and retransmission caused by error transmission, more CEs are needed by HSUPA traffic
channel.
CEFactorHSUPA is the CE mapping in table Table 2-64 (note: the MAC-e Rate in this table
should be changed to RLC rate).
2.
In Uplink (
CEHSUPA _ AUL
The same to HSDPA, when an HSUPA subscriber accesses the network, a uplink ADCH is set up, which will possibly consume CE. If SRB over HSUPA feature is
activated, then no CE will be consumed, otherwise this A-DCH in uplink will
consume one CE per link, calculated by the following formulas:
CEHSUPA _ AUL
LinksHSUPA
= Link sHSUPA *1
(7)
(6).
In Downlink (
CEHSUPA _ ADL
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.
(8)
ThroughputPerNodeBHSUPA (k bit)
* (1 SHOfactor) * (1 Re transmission)
AverageThroughputPerOnlineUserHSUPA (k bit)
* (1 Burstratio)
(9)
Issue 01 (2012-07-06)
63
UMTS RAN14.0
Dimensioning Rules
CEHSUPA _ OnlinenoData
LinkHSPA _ OnlineNoData
*1
(10)
16kbps
32kbps
64kbps
128kbps
256kbps
OVSF
SF128
SF64
SF32
SF16
SF8
CE
consumption
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.
CEBearer
is the CE consumption of each MBMS bearer, as showed in the above Figure 2-22
CE consumption for MBMS.
Issue 01 (2012-07-06)
64
UMTS RAN14.0
Dimensioning Rules
CE Resource
Total CE
CE Peak for CS
CE occupied by PS
CE Average for CS
CE occupied by CS
Time
Finally, the total number of channel elements per Node B for both R99 and HSPA can be
written as:
CETotal _ UL max{ CEErl _ Peak , CEErl _ Avg CEPS _ Avg CEHSDPA _ UL CEHSUPA _ UL }
CETotal _ DL max{ CEErl _ Peak , CEErl _ Avg CEPS _ Avg CEHSDPA _ DL CEHSUPA _ DL CEMBMS }
Core Network
Iu
Iu
RNS
RNS
UTRAN
Iur
RNC
Iub
Node B
Issue 01 (2012-07-06)
RNC
Iub
Iub
Node B
Node B
Iub
Node B
65
UMTS RAN14.0
Dimensioning Rules
Please be noted that the CS traffic here means: R99 CS + CS over HSPA+ VOIP over HSPA+
PTT over HSPA. We also call it Erlang services.
Therefore, the total Iub bandwidth for traffic can be obtained which is:
IubErl _ Peak
(11)
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
Issue 01 (2012-07-06)
66
UMTS RAN14.0
Dimensioning Rules
bandwidth can be calculated using multidimensional ErlangB (MDE) model. This idea is
shown in following figure.
Figure 2-28 Estimate CS peak Iub Bandwidth with Multidimensional Erlang B Model
Traffic of every CS
service per NodeB;
Iub factors
GoS requirements of
various CS services
MDE
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:
IubPTToverHSP A _ Average
(12)
(13)
Where:
(14)
RSHO : Soft handover ratio which does not include softer handover;
R Iub _ i : Iub factors for CS service i, including FP, AAL2 and ATM over head;
N user : Number of Subscribers per NodeB;
IubCSoverHSPA _ Average
user
* IubTrafficPerUseri * RIub( a ) _ i
(15)
Where,
TrafficPerUseri : traffic per user for CS over HSPA service I, no SHO traffic included;
Issue 01 (2012-07-06)
67
UMTS RAN14.0
Dimensioning Rules
RIub ( a ) _ i : Iub factors for CS over HSPA service i, all overhead included;
N user : Number of Subscribers per NodeB;
(16)
Where,
TrafficPerUseri : traffic per user for CS over HSPA service i, no SHO traffic included;
RIub (b ) _ i : Iub factors for VOIP over HSPA service i, all overhead included;
N user : Number of Subscribers per NodeB;
(17)
Where,
TrafficPerUseri : traffic per user for PTT over HSPA service i, no SHO traffic included;
RIub ( c ) _ i : Iub factors for PTT over HSPA service i, all overhead included;
R Iub _ i RIub ( a ) _ i
,
RIub (b ) _ i
and
RIub ( c ) _ i
are related to the transport techniques, such as ATM, IP (IP over E1/T1 or IP over FE). For the
same service, Iub factors will vary with different transport techniques.
Note that the preceding formulas are all for the downlink,the formulas of uplink will be added
SHO.
(18)
Where:
IubTrafficPerUseri
i 3600 * Ri
(19)
ThroughputPerUseri
RSHO
Issue 01 (2012-07-06)
68
UMTS RAN14.0
Dimensioning Rules
RRe transmission _ i
RBurstiness
Ri
hat the preceding formulas are all for the downlink, the formulas of uplink will be added SHO
(20)
Where:
Issue 01 (2012-07-06)
69
UMTS RAN14.0
Dimensioning Rules
(22)
It should be noted that the PeakRatePerNodeB is the application layer rate and the
relationship between application layer rate and physical layer rate is given in the following
table:
Table 2-66 Physical layer rate & application layer rate
Physical Layer Rate
3.6Mbps
3.2Mbps
7.2Mbps
6.4Mbps
14.4Mbps
12.7Mbps
NOTE
Since peak rate is used for Iub calculation, there is no need to consider additional burst ratio;
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 NodeB.
(Not per cell). To maximize saving of Iub bandwidth, the latest 3GPP provides FACH
transmission sharing for MBMS solution to share transport bearers. RNC transports only
single FACH data. Node B transport module performs data duplication and distributes them to
different FACH Channels in different cells, as shown in the following figure, where the
common transport bearer is shared over Iub. Thus, two-third of Iub bandwidth is saved by the
improved Iub transport.
Issue 01 (2012-07-06)
70
UMTS RAN14.0
Dimensioning Rules
CRNC
MBMS stream
Node B
Iub transport bearer
broad
ATM
IP
60 kbps
50 kbps
73 kbps
70 kbps
The Iub bandwidth for common channel based on ATM is a little bigger than that based on IP.
IubATM _ NBAP _ UL
1024
Issue 01 (2012-07-06)
71
UMTS RAN14.0
Dimensioning Rules
1024
N cell (285 10 H )
Where:
Traffic NodeB _ i _ UL
Traffic NodeB _ i _ DL
Li _ UL
Li _ DL
Where:
Traffic NodeB _ i _ UL
Traffic NodeB _ i _ DL
Li _ UL
Li _ DL
PBrust _ Iub
Iub signaling bandwidth can be simplified as approximately 10% of Iub traffic throughput.But
if there are more smart phones,the Iub signaling bandwidth will be more.
Issue 01 (2012-07-06)
72
UMTS RAN14.0
Dimensioning Rules
Description
CNBAP Corresponding
to Each Parameter
TOTAL USER
Issue 01 (2012-07-06)
73
UMTS RAN14.0
Dimensioning Rules
Issue 01 (2012-07-06)
74
UMTS RAN14.0
Dimensioning Rules
BSC6810 can be upgraded to BSC6900 with only software upgrade without hardware
change.
2.
Naming changes
RNC
BSC6810
BSC6900
RSS
MPS
Extended Subrack
RBS
EPS
3.
User Plane
DPUb -> DPUe
Control Plane
SPUa -> SPUb
Transmission
Transport
IP
Issue 01 (2012-07-06)
BSC6900
BSC6810&BSC6900
Board
Ports
Board
Ports
FG2c
12 FE / 4 GE electrical
FG2a
8/2
75
UMTS RAN14.0
Dimensioning Rules
Transport
BSC6900
BSC6810&BSC6900
Board
Ports
Board
Ports
IP
GOUc
4 GE optical
GOUa
IP over E1/T1
POUc
4 optical cSTM-1/OC-3
POUa
AOUc
4 optical cSTM-1/OC-3
AOUa
UOIc
8 optical STM-1/OC-3
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
HW69 R11
HW69 R13
Compared with the HW68R11, HW69R11 introduces new signaling processing boards
(SPUb), data processing boards (DPUe), and c series interface boards (AOUc, FG2c, GOUc,
POUc, and UOIc).
Compared with HW69R11, HW69R13 introduces new OMU boards (OMUc), switch boards
(SCUb), and the intelligent service identification and processing board (NIUa).
Table 3-1 Relationship between the RNC and hardware versions
Hardware
Version
BSC6810
BSC6810/BSC6900
RAN10.0/
RAN11.0
RAN11.1
RAN12.0
RAN13.0
RAN14.0
HW68R11
Supported
Supported
Supported
Supported
Supported
HW69R11
Supported
Supported
Supported
Supported
HW69R13
Supported
Supported
Issue 01 (2012-07-06)
76
UMTS RAN14.0
Dimensioning Rules
Contained Subrack
Configuration Principle
MPR
1 MPS, 02 EPSs
EPR
13 EPSs
Quantity
Function
MPS
EPS
0-5
NOTE
DPUe board in RAN11.1 and RAN12.0 is available as a single board and at least 2 pcs DPUe should
be configured in minimum configuration for reliability.
SPUb, SPUa and DPUb are configured per pair in RAN12.0 and previous releases.
The rules of mixed configuration of HW68 R11 boards and HW69 R11 boards, which may be applied in
the scenario that HW68 R11 boards are used in the existing network and HW69 R11 boards are used for
capacity expansion, are listed as follows.
When the service processing boards SPUb and DPUe of HW69 R11 are added during capacity
expansion, comply with the following principles:
Issue 01 (2012-07-06)
77
UMTS RAN14.0
Dimensioning Rules
When HW69 R11 boards and HW68 R11 boards are configured in the same subrack, comply with the
following principles during capacity expansion:
Number of configured SPUa boards + Number of configured SPUb boards 4 (unit: pair)
Number of configured DPUb boards + Number of configured DPUe boards 6 (unit: PCS)
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
Basic Model
Issue 01 (2012-07-06)
78
UMTS RAN14.0
Dimensioning Rules
Number of
Supported
BHCAs*
Number
of
Supported
NodeBs
Number
of
Supported
Cells
Number of
Slots for
Interface
Boards
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
Basic Model
RAN14.0: The BSC6900 UMTS supports 23 basic models (adopts HW69 R11 boards)
Basic
Model
Number of
Supported BHCAs*
Number of
Supported NodeBs
Without
Capacity
Enhancem
ent
Without
Additio
nal
Signalin
g
Processi
ng Unit
Without
Additio
nal
Signalin
g
Processi
ng Unit
Issue 01 (2012-07-06)
With
Capacity
Enhancem
ent
With
Additio
nal
Signalin
g
Processi
ng Unit
With
Additio
nal
Signalin
g
Processi
ng Unit
Numb
er of
Suppo
rted
Cells
Numb
er of
Slots
for
Interf
ace
Board
s
79
UMTS RAN14.0
Dimensioning Rules
Basic
Model
Number of
Supported BHCAs*
Number of
Supported NodeBs
Without
Capacity
Enhancem
ent
With
Capacity
Enhancem
ent
Without
Additio
nal
Signalin
g
Processi
ng Unit
With
Additio
nal
Signalin
g
Processi
ng Unit
Without
Additio
nal
Signalin
g
Processi
ng Unit
With
Additio
nal
Signalin
g
Processi
ng Unit
Numb
er of
Suppo
rted
Cells
Numb
er of
Slots
for
Interf
ace
Board
s
1600/6700
124000
6200000
180
540
600
10
360
540
900
10
360
540
1,200
10
540
1,260
1,500
24
540
1,260
1,800
24
720
1,260
2,100
24
720
1,260
2,400
24
900
1,980
2,700
38
900
1,980
3,000
38
BSC6900
UMTS
Model
670
670/6,700
BSC6900
UMTS
Model
1005
1,005/10,05
0
BSC6900
UMTS
Model
1340
1,340/13,40
0
BSC6900
UMTS
Model
1675
1,675/16,75
0
BSC6900
UMTS
Model
2010
2,010/20,10
0
BSC6900
UMTS
Model
2345
2,345/23,45
0
BSC6900
UMTS
Model
2680
2,680/26,80
0
BSC6900
UMTS
Model
3015
3,015/30,15
0
BSC6900
UMTS
Model
3350
3,350/33,50
0
Issue 01 (2012-07-06)
2400/10050
3200/13400
4000/16750
4800/20100
5600/23450
6400/26800
7200/30150
8000/33500
248000
248000
372000
372000
496000
496000
620000
620000
6200000
6200000
6200000
6200000
6200000
6200000
6200000
6200000
80
UMTS RAN14.0
Dimensioning Rules
Number of
Supported BHCAs*
Number of
Supported NodeBs
Basic
Model
Without
Capacity
Enhancem
ent
With
Capacity
Enhancem
ent
Without
Additio
nal
Signalin
g
Processi
ng Unit
With
Additio
nal
Signalin
g
Processi
ng Unit
Without
Additio
nal
Signalin
g
Processi
ng Unit
With
Additio
nal
Signalin
g
Processi
ng Unit
Numb
er of
Suppo
rted
Cells
Numb
er of
Slots
for
Interf
ace
Board
s
BSC6900
UMTS
Model
3685
3,685/36,85
0
8800/36850
744000
6200000
1,080
1,980
3,300
38
BSC6900
UMTS
Model
4020
4,020/40,20
0
1,080
1,980
3,600
38
BSC6900
UMTS
Model
4355
4,355/43,55
0
1,260
2,700
3,900
52
BSC6900
UMTS
Model
4690
4,690/46,90
0
1,260
2,700
4,200
52
BSC6900
UMTS
Model
5025
5,025/50,25
0
1,440
2,700
4,500
52
BSC6900
UMTS
Model
5360
5,360/53,60
0
1,440
2,700
4,800
52
1,620
3,060
5,100
66
1,620
3,060
5,100
66
1,800
3,060
5,100
66
BSC6900
UMTS
Model
5695
5,695/56,95
0
BSC6900
UMTS
Model
6030
6,030/60,30
0
BSC6900
UMTS
Model
6365
6,365/63,65
0
Issue 01 (2012-07-06)
9600/40200
10400/4355
0
11200/4690
0
12000/5025
0
12800/5360
0
13600/5695
0
14400/6030
0
15200/6365
0
744000
868000
868000
992000
992000
1116000
1116000
1240000
6200000
6200000
6200000
6200000
6200000
6200000
6200000
6200000
81
UMTS RAN14.0
Dimensioning Rules
Number of
Supported BHCAs*
Number of
Supported NodeBs
Basic
Model
Without
Capacity
Enhancem
ent
Without
Additio
nal
Signalin
g
Processi
ng Unit
With
Additio
nal
Signalin
g
Processi
ng Unit
Without
Additio
nal
Signalin
g
Processi
ng Unit
With
Additio
nal
Signalin
g
Processi
ng Unit
Numb
er of
Suppo
rted
Cells
Numb
er of
Slots
for
Interf
ace
Board
s
BSC6900
UMTS
Model
6700
6,700/67,00
0
1240000
6200000
1,800
3,060
5,100
66
BSC6900
UMTS
Model
7035
7,035/70,35
0
1,980
3,060
5,100
80
BSC6900
UMTS
Model
7370
7,370/73,70
0
1,980
3,060
5,100
80
BSC6900
UMTS
Model
7705
7,705/77,05
0
2,160
3,060
5,100
80
BSC6900
UMTS
Model
8040
8,040/80,40
0
2,160
3,060
5,100
80
With
Capacity
Enhancem
ent
16000/6700
0
16800/7035
0
17600/7370
0
18400/7705
0
19200/8040
0
1364000
1364000
1488000
1488000
6200000
6200000
6200000
6200000
Iub User Plane Capacity (Mbit/s/Erlang): Refers to the maximum value when the model
only processes CS services or PS services.
Unless otherwise specified, all the PS throughput mentioned in charter 3 is based on the traffic type
UL/DL64/384kbps, that is, the effective user throughput is 64 kbit/s in the uplink and 384 kbit/s in the
downlink (irrespective of the bearer type R99 or HSPA).
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.
Issue 01 (2012-07-06)
82
UMTS RAN14.0
Dimensioning Rules
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 (6200 000 BHCA corresponds to 50 pairs SPUb are configured).
RAN12.0: Specifications of the BSC6900 UMTS that adopts the HW69 R11 hardware
RAN14.0: Specifications of the BSC6900 UMTS (adopts HW69 R13 boards)
Performance
Specifications
2.
BSC6900 configuration adjustment (some time after network operation): Optimize the
network configuration according to the actual traffic model of the live network.
This document dwells upon the initial configuration of the BSC6900 for network deployment.
The required number of boards is calculated according to the network capacity. After the
calculation, for the purpose of coordinating the running and bringing into full play the
processing capability of network devices, configuring the BTS6900 must be subject to the
following constraints:
The hardware configuration procedure is as follows:
Obtain the traffic model, network parameters (number of UEs, number of NodeBs, and
number of cells), and interface requirements of the operator's network and perform network
dimensioning to obtain the user plane requirements (PS throughput and CS Erlang), control
plane requirements (BHCAs), and interface requirements.
Determine hardware configurations according to the network requirements.
1.
Calculate the number of required data processing units and hardware capacity licenses
based on the user plane requirements (PS throughput and CS Erlang), number of cells,
and processing capability of one data processing unit.
2.
Calculate the number of required signaling processing units based on the control plane
requirements (BHCAs), number of NodeBs, number of cells, and processing capability
of one signaling processing unit.
3.
Calculate the number of interface boards required on each interface based on the CS
Erlang requirement, PS throughput requirement, transmission type, port requirement,
number of NodeBs, and signaling processing requirement on the interface.
4.
Calculate the number of required subracks based on the number of data processing units,
number of signaling processing units, and number of interface boards.
5.
Issue 01 (2012-07-06)
83
UMTS RAN14.0
Dimensioning Rules
Unit
Total subscribers
Number
CS parameters
CS voice call per subscriber in BH
times
Erlang
times
times
Erlang
Issue 01 (2012-07-06)
84
UMTS RAN14.0
Dimensioning Rules
Item
Unit
times
PS parameters
PS call per subscriber in BH
times
bps
times
times
times
NAS
NAS signaling per subscriber per BH
Times
(1)NAS includes all CN-UE signaling (LA update, RA update, SMS, IMSI attach/detach, GPRS
attach/detach).
(2) The PS throughput of the DPU and the interface board is closely related to the PS service rate.
Generally, the throughput supported by the DPU and the interface board based on the UL/DL rate of
64/384 kbit/s is far higher than the throughput supported by the two boards based on the UL/DL rate of
32/32 kbit/s. Therefore, the proportion of PS throughput (based on the UL/DL rate of xx/yy kbit/s) must
be provided for configuration calculation.
(3) The preceding input information includes major parameters of the traffic model, but excluding
relocation and paging procedures. Generally, procedures such as relocation have a minor impact on the
device load.
(4) If the Push to Talk (PTT) service is available on the live network, input parameters must contain PTT
subscriber information and PTT traffic model parameters. For details, see the appendix.
Issue 01 (2012-07-06)
85
UMTS RAN14.0
Dimensioning Rules
Iub
interface
Control
plane
Item
Comment
Iub CS Traffic
Erlang
Iub PS Throughput
Mbps
Iub PS UL Throughput
Mbps
Iub PS DL Throughput
Mbps
Mbps
Mbps
Number
Times
Number
BHCA requirement
BHCA capacity of SPU based on given traffic model
User plane
Iu-CS
interface
Iu-PS
interface
Issue 01 (2012-07-06)
Erlang
Mbps
Number
Iu-CS CS Traffic
Erlang
Mbps
Mbps
Number
Times
Iu-PS Throughput
Mbps
Iu-PS UL Throughput
Mbps
Iu-PS DL Throughput
Mbps
Mbps
Mbps
Number
Times
86
UMTS RAN14.0
Dimensioning Rules
Iub interface
Issue 01 (2012-07-06)
87
UMTS RAN14.0
Dimensioning Rules
Iub active users include Iub CS active users and Iub PS active users.
Iub CS active users = Total Subscirbers * (CS Voice Traffic per subscriber in BH+ CS data
traffic per CS data subscriber in BH) * (1+Proportion of SHO for CS traffic)
Iub PS active users = Total Subscirbers * (PS call per sub per BH * MHT (mean hold time)
per PS call /3600) * (1+Proportion of SHO for PS call)
Iub session setup and release requirement = Total Subscirbers * (CS voice call per
subscriber in BH * 2 + CS voice call per subscriber in BH * Handover times per CS voice
call *1 +CS data call per subscriber in BH * 2 +CS data call per subscriber in BH *
Handover times per CS Data call *1 +PS call per subscriber in BH * 3 +PS call per
subscriber in BH * Handover times per PS call + PS call per subscriber in BH * PS
channel switch per PS call*1 + PS call per subscriber in BH * Cell update per PS call*1 +
NAS signaling per subscriber in BH*1)
2.
Control plane
Control plane active users = Total Subscirbers * (CS Voice Traffic per subscriber in BH +
CS data traffic per CS data subscriber in BH+PS call per sub per BH * Mean hold time per
PS call /3600)
BHCA requirement = Total Subscirbers * (CS voice call per sub + CS data call per sub per
BH+PS call per sub per BH)
BHCA capacity of SPU based on given traffic model
This is the calculation of the BHCA capacity of SPU based on given traffic model.
Table 3-6 Control plane traffic parameters
Key Control Plane Traffic Parameter
Unit
Traffic Model
CPU Value
times
W1
times/call
W2
times
W3
times/call
W4
times
W5
times/call
W6
times/call
W7
times/call
W8
times/per subscriber
W9
CS Domain Voice
CS Domain data
PS Domain
NAS procedure
NAS signaling per subscriber in BH
Issue 01 (2012-07-06)
88
UMTS RAN14.0
Dimensioning Rules
Above table only list mainly signaling procedure, not including paging, relocation etc.
"Wx" of "CPU Value" column means the SPU subsystem CPU value consumed by the signaling
procedure.
User plane
Iu-CS interface
Issue 01 (2012-07-06)
89
UMTS RAN14.0
Dimensioning Rules
Generally, the Iu-CS signaling bandwidth can be simplified as approximately 1% of Iu-CS traffic
bandwidth, that is, Iu-CS signaling throughput ratio is 1%.
For "Iu-CS voice service transmission efficiency" and "Iu-CS VP service transmission
efficiency, please refer to 3.1.3.
Iu-CS UL Transmission Bandwidth= Iu-CS DL Transmission Bandwidth
Iu-CS active users = Iu-CS Voice Traffic + Iu-CS Data Traffic
Iu-CS session setup and release requirement = Total Subscirbers * (CS voice call per
subscriber in BH + CS data call per subscriber in BH) * 2
Note: One CS call times corresponds to 2 times session setup and release.
5.
Iu-PS interface
Issue 01 (2012-07-06)
90
UMTS RAN14.0
Dimensioning Rules
The following table lists the standard protocol stack for Iu-CS user plane.
Iu C S - ATM (user plane)
Radio Network Layer Iu UP
AAL2
Transmission
ATM
Network Layer
Physical Layer
Iu C S - IP (user plane)
Radio Network Layer Iu UP
RTP
UDP
IP
Transmission
Data Link Layer
Network Layer
Physical Layer
The following table lists the standard protocol stack for Iu-PS user plane.
Iu PS - ATM (user plane)
Radio Network Layer Iu UP
AAL5
Transmission Network ATM
Layer
Physical Layer
Issue 01 (2012-07-06)
91
UMTS RAN14.0
Dimensioning Rules
Iu PS - IP (user plane)
Radio Network Layer Iu UP
GTP-U
UDP
IP
Transmission Network Data Link Layer
Layer
Physical Layer
About the transmission efficiency in different interface with different service, please refer to
below table.
Iub/Iur
CS Voice traffic
CS Data traffic
PS Traffic
55%
72%
72%
43%
57 %
56%
ATM over E1
52%
70%
69%
IP over FE/GE
28%
68%
65%
IP over E1
84%
89%
84%
based on
64K/64Kbps(DL/UL)
service
Comment
Iu CS
CS Voice traffic
CS Data traffic
55%
72%
IP over FE/GE
26%
49%
PS Traffic
Comment
76%
based on
64K/64Kbps(DL/UL)
service
IP over FE/GE
84%
Comment
Iu PS
Issue 01 (2012-07-06)
92
UMTS RAN14.0
Dimensioning Rules
Function
Process
Specification
Configuration
Specification
Remarks
DPUb
Data processing
PS throughput: 115
Mbit/s; or CS voice:
1800 Erl
PS throughput based
on UL/DL rate of
64/384 kbit/s
DPUe
Data processing
PS throughput: 335
Mbit/s; or CS voice:
3350 Erl
PS throughput based
on UL/DL rate of
64/384 kbit/s
Hardware
Capacity
License
(165Mbps)
Enhanced data
processing
PS throughput: 165
Mbit/s
PS throughput based
on UL/DL rate of
64/384 kbit/s
Hardware
Capacity
License
(300Mbps)
Enhanced data
processing
PS Throughput: 300
Mbit/s
PS throughput based
on UL/DL rate of
64/384 kbit/s
NIUa
Intelligently
identifying services
PS Throughput: 50
Mbit/s
PS throughput based
on UL/DL rate of
64/384 kbit/s
Network
Intelligence
Throughput
License
Intelligently
identifying services
PS Throughput: 50
Mbit/s
PS throughput based
on UL/DL rate of
64/384 kbit/s
Issue 01 (2012-07-06)
93
UMTS RAN14.0
Dimensioning Rules
The throughput specification and the CS Erlang specification cannot be both satisfied. In the mixed
traffic, the sum of relative loads of the two traffic types (CS, PS) has to be smaller than or equal to 1.
ARM (Erl)/MAX Iub AMR (Erl) + PS throughput (Mbit/s)/MAX Iub PS throughput (Mbit/s) 1
The process specification is mainly restricted by service processing resources of the board CPU. The
configuration specification is mainly restricted by the memory space.
The hardware capacity license (165 Mbit/s) and hardware capacity license (300 Mbit/s) can be
configured only on the DPUe and only when specified conditions are met. For details, see the
hardware capacity license configuration method presented subsequently.
Table 3-8 Network requirements to be considered during configuration of the service processing
module
Item
Description
Comment
Cell number
Assume that the user plane capacity requirements of the network are as follows:
User Plane PS throughput: a Mbit/s (assume that the PS data traffic types include UL/DL rate
of 32/32 kbit/s (w%), UL/DL rate of 64/64 kbit/s (x%), UL/DL rate of 64/128 kbit/s (y%), and
UL/DL rate of 64/384 kbit/s or above (z%), and w% + x% + y% + z% = 100%)
User Plane CS Traffic: b Erl
User plane active users: n ("User plane active users" here means any RRC connection with
RAB state DCH, HS, or FACH)
Cell number: c
If the DPUb is adopted, the configuration method is as follows:
0.6, 0.7, 1, and 1 are the relative weight coefficients for the following four traffic types:
UL/DL rate of 32/32 kbit/s, UL/DL rate of 64/64 kbit/s, UL/DL rate of 64/128 kbit/s, and
UL/DL rate of 64/384 kbit/s or above.
a = a x (w%/0.6 + x%/0.7 + y%/1 + z%/1)
Required number of DPUb: N_DPUb (pair) = MAX (a'/230 + b/3600, c/300, n/6600)
Note: At least one pair of DPUb should be configured. Up to 17 pairs of DPUb can be
configured.
If the DPUe is adopted, the configuration method of the DPUe and hardware capacity license
is as follows:
Issue 01 (2012-07-06)
94
UMTS RAN14.0
Dimensioning Rules
0.38, 0.53, 0.66, and 1 are the relative weight coefficients for the following four traffic types:
UL/DL rate of 32/32 kbit/s, UL/DL rate of 64/64 kbit/s, UL/DL rate of 64/128 kbit/s, and
UL/DL rate of 64/384 kbit/s or above.
a' = a x (w%/0.38 + x%/0.53 + y%/0.66 + z%/1)
Required number of DPUe: N_DPUe = ROUNDUP (MAX (a'/(335 + 165 + 330) + b/3350,
c/300, n/5880, 2))
Note: At least two DPUe boards should be configured. Up to 30 DPUe boards can be
configured.
The hardware capacity license needs to be configured only when the PS throughput is based
on the UL/DL rate of 64/384 kbit/s. The configuration method is as follows:
N_DPUe_PS = N_DPUe b/3350
If N_DPUe_PS x 335 >= a, the Hardware Capacity License does not need to be configured.
Otherwise, the number of hardware capacity licenses (165 Mbit/s) to be configured N_165 =
Min (N_DPUe, ROUNDUP ((a N_DPUe_PS x 335)/165)).
If N_165 x 165 + N_DPUe_PS x 335 > = a, the hardware capacity license (300 Mbit/s) does
not need to be configured. Otherwise, the number of hardware capacity licenses (300 Mbit/s)
to be configured N_300 = Min (N_165, ROUNDUP ((a N_DPUe_PS x 335) N_165 x
165)/300)).
The configuration method of the NIUa and QM1SNIU50M00 is as follows:
If the function of intelligently identifying services is required, the NIUa must be configured.
Required number of NIUa boards: N_ NIUa = ROUNDUP (a/3200, 0)
"a" stands for the user plane PS throughput. The NIUa provides the 50 Mbit/s throughput
processing capability. If a > 50, then
N_Network Intelligence Throughput License = ROUNDUP ((a 50)/50, 0);
Otherwise, N_ Network Intelligence Throughput License = 0.
Function
Process Specification
Configuration
Specification
Remarks
SPUa
Signaling
processing
67 500 BHCA
BHCA based on
the "Balanced
traffic model" table
Signaling
processing
90 000 BHCA
BHCA based on
the "Balanced
traffic model" table
Signaling
processing
BHCA based on
the "Balanced
traffic model" table
(with MPU)
SPUa
(without MPU)
SPUb
(with MPU)
Issue 01 (2012-07-06)
95
UMTS RAN14.0
Dimensioning Rules
Model
Function
Process Specification
Configuration
Specification
Remarks
SPUb
Signaling
processing
BHCA based on
the "Balanced
traffic model" table
(without MPU)
The BHCA specification of the SPU in Table 3-9 is based on Huawei's traffic model. If the traffic
model of the live network differs greatly from Huawei's traffic model, the BHCA specification of the
SPU must be recalculated based on the traffic model of the live network with the method described
in section 3.3.2 .
BHCA specifications:
Assume one MPU manages three SPUa boards, (67500 + 90000 + 90000)/3 80000
Assume one MPU manages three SPUb boards, (126000 + 147000 + 147000)/3 = 140000
Description
Comment
BHCA requirement
NodeB number
Cell number
Issue 01 (2012-07-06)
96
UMTS RAN14.0
Dimensioning Rules
Description
Applicable
Interface
CID/UDP*
AEUa
Iub
500
23000
PEUa
Iub
500
23000
AOUa
Iub
500
23000
POUa
Iub
500
23000
UOIa
Iub/Iu/Iur
500
23000
GOUa
Iub/Iu/Iur
1000
23000
FG2a
IP Interface Unit (2 GE /8
FE, Electric)
Iub/Iu/Iur
1000
23000
CID is short for channel identifier. A CID indicates an ATM channel. UDP is short for User Datagram
Protocol. A UDP indicates a UDP port in IP transmission mode.
Iub
NodeB
CS (Erlang)
UL (Mbit/s)
DL (Mbit/s)
UL+DL
(Mbit/s)
AEUa
2800
45
45
90
32
PEUa
2800
60
60
120
32
AOUa
9000
195
195
390
126
POUa
6000
120
120
240
126
UOIa
9000
225
225
450
300
GOUa
6000
840
840
840
300
FG2a
6000
840
840
840
300
Issue 01 (2012-07-06)
97
UMTS RAN14.0
Dimensioning Rules
Iu-CS
Iu-PS
CS (Erlang)
UL (Mbit/s)
DL
(Mbit/s)
UL+DL
(Mbit/s)
UOIa
9000
150
385
535
GOUa
6000
840
840
840
FG2a
6000
840
840
840
Description
Applicable
Interface
CID/UDP
AOUc
Iub
5000
79000
POUc
Iub
5000
129000
UOIc
Iub/Iu/Iur
5000
79000
GOUc
Iub/Iu/Iur
5000
129000
FG2c
Iub/Iu/Iur
5000
129000
Iub
NodeB
CS (Erlang)
UL
(Mbit/s)
DL
(Mbit/s)
UL+DL
(Mbit/s)
AOUc
18000
300
300
600
500
POUc
18000
400
400
800
252
UOIc
18000
800
800
1200
500
GOUc/FG2c
18000
1300
1300
2600
500
Issue 01 (2012-07-06)
98
UMTS RAN14.0
Dimensioning Rules
Iu-CS
Iu-PS
CS (Erlang)
UL
(Mbit/s)
DL
(Mbit/s)
UL+DL (Mbit/s)
UOIc
18000
900
900
1800
GOUc/FG2c
18000
1600
1600
3200
When the HW69R13 hardware is adopted: HW69R13 does not introduce new interface
boards, but introduces the SCUb switch board. The SCUb provides a better switching
capability for the slot where the interface board is inserted, to allow the GOUc/FG2c to
provide higher IUB UL PS throughput, IUB DL PS throughput, IU-PS UL PS throughput,
and IU-PS DL PS throughput.
Table 3-17 Iub specification of the interface unit
Board
Iub
GOUc/ FG2c
NodeB
CS (Erlang)
UL
(Mbit/s)
DL
(Mbit/s)
UL+DL
(Mbit/s)
18000
2600
2600
2600
500
GOUc/ FG2c
Iu-CS
Iu-PS
CS (Erlang)
UL
(Mbit/s)
DL
(Mbit/s)
UL+DL (Mbit/s)
18000
3200
3200
3200
In the preceding tables, UL (Mbit/s), DL (Mbit/s), and UL+DL (Mbit/s) are all based on the UL/DL
rate of 64/384 kbit/s.
An active CS user consumes two CIDs or UDP ports. An active PS user in H state consumes three
CIDs or UDP ports.
The "session setup and release times per second" indicates the signaling processing capability of the
interface board, applicable to Iub, Iu, and Iur interfaces. The signaling processing requirement of the
interface is related to the traffic module. Table 3-19 shows the relationship between them.
Table 3-19 Mapping of the setup and release procedure of the interface unit and the traffic model
Control Plane Traffic Parameter
Unit
Session Setup/Release
Times
Times
Times/call
Issue 01 (2012-07-06)
99
UMTS RAN14.0
Dimensioning Rules
Unit
Session Setup/Release
Times
Times
Times/call
Times/call
Times/per subscriber
The service processing specification of the Iur interface is the same as that of the Iub interface.
In the preceding tables, the service processing specification of a board means the maximum value
that the board can reach when processing the corresponding service independently. The "NodeB"
column lists the configuration specification.
Interface boards of the BSC6900 all adopt the 1+1 configuration. The configuration should be
multiplied according to the number of interface boards calculated based on the network
capacity.
Iub
Item
Description
Comment
Determined according to
network planning.
Iub CS Traffic
Iub PS throughput
Iub Transmission
Bandwidth
Transmission bandwidth
requirement for the Iub
interface, including the Iub DL
transmission bandwidth and
Iub UL transmission
bandwidth
Issue 01 (2012-07-06)
100
UMTS RAN14.0
Dimensioning Rules
Item
Description
NodeB number
Number of NodeBs to be
managed by the RNC
Comment
Determined according to
network planning.
The networking scenarios supported by the BSC6900 for Iub transmission include the
following:
CASE 1- hybrid Iub-E1 (ATM) && Iub-Ethernet (IP)
CASE 2- hybrid Iub - E1 (IP) && Iub-Ethernet (IP)
CASE 3-hybrid Iub -VC12-STM-1 (ATM) && Iub-Ethernet (IP)
CASE 4-hybrid Iub - VC4-STM-1 (ATM) && Iub-Ethernet (IP)
CASE 5-hybrid Iub -VC12-STM-1 (IP) && Iub-Ethernet (IP)
CASE 6 - E1 (ATM)
CASE 7 - VC12-STM-1 (ATM)
CASE 8 - VC4-STM-1 (ATM)
CASE 9 - E1 (IP)
CASE 10 Ethernet (IP)
CASE 11 - VC12-STM-1 (IP)
First, select an appropriate transmission interface according to network planning. The number
of Iub interface boards should be respectively calculated from the dimensions of the service
processing capability (Erlang and payload throughput), interface bandwidth, NodeB
specification, signaling processing capability and number of concurrent active users. Then
take the maximum value from the results calculated from the preceding dimensions.
Number of Iub interface board = MAX (Number of Iub interface board_Traffic, Number of
Iub interface board_Bandwidth, Number of Iub Interface Board_Active users, Number of Iub
Interface Board_Session set-up/release, Number of Iub interface board_NodeB)
Where,
Number of Iub interface board_Traffic = Iub CS Traffic/Iub CS specification + MAX (Iub
PS DL Throughput/Iub PS DL specification, Iub PS UL Throughput/Iub PS UL specification,
(Iub PS DL Throughput + Iub PS UL Throughput)/Iub PS DL+UL specification)
Note: Iub CS Traffic includes Iub CS voice traffic and Iub CS data traffic.
Number of Iub interface board_Bandwidth = (Iub OAM Transmission bandwidth + MAX
(Iub DL Transmission Bandwidth, Iub UL Transmission Bandwidth))/Transmission
Bandwidth per Interface port/port number per interface board
Note: The transmission bandwidth per interface port depends on the interface type. For
example, the transmission bandwidth of the STM-1 interface is 155 Mbit/s and that of the GE
interface is 1 Gbit/s.
Number of Iub Interface Board_ Active users
Issue 01 (2012-07-06)
101
UMTS RAN14.0
Dimensioning Rules
= (Iub CS active users*2 +Iub PS active users*3)/CID or DPU supported by per interface
board
Number of Iub Interface Board_Session setup/release
= Iub session set-up and release requirement / 3600/ capacity of session setup and session
release per second of interface board
Number of Iub interface board_NodeB = NodeB number / NodeB Capacity per Interface
Board
In the preceding formulas, Iub Voice specification, Iub CS data specification, Iub PS DL
specification, Iub PS UL specification, Iub PS DL +UL specification, port number per
interface board, NodeB capacity per interface board, capacity of session setup and release
times per second of interface board, and active users supported by per interface board are
interface board specifications. For details, see Table 3-12 and Table 3-15. Other items come
from the RNC dimensioning outputs. For details, see Table 3-20.
The BSC6900 supports up to 50 Iur interfaces. In other words, each BSC6900 can connect to
up to 50 RNCs.
Iu-CS
Item
Description
Comment
Determined according to
network planning.
Iu-CS CS Traffic
Iu-CS Transmission
Bandwidth
Issue 01 (2012-07-06)
102
UMTS RAN14.0
Dimensioning Rules
Item
Description
Comment
Issue 01 (2012-07-06)
103
UMTS RAN14.0
Dimensioning Rules
Iu-PS
Item
Description
Comment
Determined according to
network planning.
Iu-PS Throughput
Iu-PS Transmission
Bandwidth
Issue 01 (2012-07-06)
104
UMTS RAN14.0
Dimensioning Rules
Description
Function
GCUa
General clock
GCGa
GPS clock
(including the
antenna system)
GCUa configuration principle: Optional. When the GPS clock is not needed, configure one
piece of the GCUa for each RNC.
GCGa configuration principle: Optional. When the GPS clock is needed, configure one piece
of the GCGa for each RNC.
2. Subracks
Issue 01 (2012-07-06)
105
UMTS RAN14.0
Dimensioning Rules
Description
Function
QM1P00UMPS01
Main
processing
subrack (MPS)
QM1P00UEPS01
Extended
processing
subrack (EPS)
Standard configuration for the MPS: one pair of OMUa or OMUc, one pair of SCUa or SCUb,
and one pair of SCUa or GCGa
Standard configuration for the EPS: one pair of SCUa or SCUb
Configuration principle for the MPS: One MPS must be configured and at most one can be
configured for each RNC.
Configuration principle for the EPS: Up to five EPS can be configured for each RNC. The
configuration method is as follows:
Number of EPSs_1 = ROUNDUP ((Number of SPUb required by the network Number of
SPUb that can be housed in the MPS)/Number of SPUb that can be housed in the EPS)
If the number of SPUb required by the network is smaller than the number of SPUb that can
be housed in the MPS, the number of EPSs_1 = 0.
The MPS and the EPS each can house nine pairs of SPUb.
Number of EPSs_2 = ROUNDUP ((Number of DPUe required by the network Number of
DPUe that can be housed in the MPS)/Number of DPUe that can be housed in the EPS)
If the number of DPUe required by the network is smaller than the number of DPUe that can
be housed in the MPS, the number of EPSs_2 = 0.
The MPS and the EPS each can house nine DPUe boards.
Number of EPSs_3 = ROUNDUP ((Number of interface board slots required by the network
Number of slots provided by the MPS)/14)
If the number of interface board slots required by the network is smaller than the number of
slots provided by the MPS, the number of EPSs_3 = 0.
The MPS can provide 12 interface board slots and the EPS can provide 14 interface board
slots.
Number of EPSs_4 = ROUNDUP ((Number of SPUb required by the network + Number of
DPUe required by the network + Number of interface board slots required by the network +
Number of NIUa required by the network Number of slots provided by the MPS)/26)
If the sum of the number of SPUb, the number of DPUe, and the number of interface board
slots required by the network is smaller than the number of slots provided by the MPS, the
number of EPS_4 = 0.
The MPS provides 20 slots (reserve 2 slots for SAU boards).
Issue 01 (2012-07-06)
106
UMTS RAN14.0
Dimensioning Rules
If the customer buys and uses the Huawei Nastar, the SAU needs to be inserted in the MPS or
EPS of the BSC6900. The SAU requires a pair of active/standby slots in the BSC6900
subrack.
Number of EPSs = MAX (Number of EPSs_1, Number of EPSs_2, Number of EPSs_3,
Number of EPSs_4)
3. Cabinet
Table 3-25 Cabinet
Package Code
Description
Function
WP1B4PBCBN00
BSC6900 cabinet
Cabinet
Cabinet configuration principle: At most two pieces are configured for each RNC. Each
cabinet can house up to three subracks.
Issue 01 (2012-07-06)
107
UMTS RAN14.0
Dimensioning Rules
Iub
interface
Control
plane
Item
Comment
Iub CS Traffic
Erlang
Iub PS Throughput
Mbps
Iub PS UL Throughput
Mbps
Iub PS DL Throughput
Mbps
Mbps
Mbps
Mbps
Number
Times
Number
BHCA requirement
BHCA capacity of SPU based on given
traffic model
User
plane
Iu-CS
interface
Iu-PS
interface
Issue 01 (2012-07-06)
Required
Network
Capacity
Erlang
Mbps
Number
Iu-CS CS Traffic
Erlang
Mbps
Mbps
Number
Times
Iu-PS Throughput
Mbps
Iu-PS UL Throughput
Mbps
Iu-PS DL Throughput
Mbps
Mbps
Mbps
Number
Times
108
UMTS RAN14.0
Dimensioning Rules
Description
Cell number
Assume that the number of Iub DPUb on the live network is DPUb_N. After capacity
expansion, the relationships between the total required capacity and the capacity supported by
the DPUb and DPUe are as follows:
Item
Total Requirement
After Expansion
Capacity Supported by
Existing DPUb
Capacity to Be
Supported by DPUe
Iub CS Traffic
E1
E2
Iub PS throughput
T1
T2
U1
U2
Cell number
C1
C2
T1 + T2 T (the throughput supported by the DPUb and DPUe should meet the
requirements of the expanded network)
2.
E1 + E2 E (the Erlangs supported by the DPUb and DPUe should meet the
requirements of the expanded network)
3.
U1 + U2 U (the number of users supported by the DPUb and DPUe should meet the
requirements of the expanded network)
Issue 01 (2012-07-06)
109
UMTS RAN14.0
Dimensioning Rules
4.
C1 + C2 C (the number of cells supported by the DPUb and DPUe should meet the
requirements of the expanded network)
Assume that capacity expansion is implemented by adding the DPUb. Then the required
number of DPUb is:
DPUb_Total = MAX (T/230+E/3600, U/6600, C/300), DPUb_N is the number of the existing
DPUb.
Therefore, the ratio of the network capacity in the user plane to be supported by the DPUe to
the target network capacity in the user plane after expansion is: Ratio = (DPUb_Total
DPUb_N)/DPUb_Total.
T2 = T x Ratio
E2 = E x Ratio
U2 = U x Ratio
C2 = C x Ratio
Item
Description
E2
T2
U2
Cell number
C2
According to the preceding table, the required number of DPUe can be calculated with the
method described in section 3.4.1 .
Step 2 Mixed insertion of Iub boards: The GOUa is used on the live network. For capacity expansion,
the GOUc will be added.
Table 3-28 Network requirements to be considered during configuration of the Iub interface unit
(see Table 3-26)
Iub
Item
Description
Iub CS Traffic
Iub PS throughput
Iub Transmission
Bandwidth
Issue 01 (2012-07-06)
110
UMTS RAN14.0
Dimensioning Rules
Item
Description
NodeB number
Assume that the number of Iub GOUa on the live network is Iub_GOUa_N. After capacity
expansion, the relationships between the total required capacity and the capacity supported by
the GOUa and GOUc are as follows:
Item
Total Requirement
After Expansion
Capacity Supported by
Existing GOUa
Capacity to Be
Supported by GOUc
Iub CS Traffic
E1
E2
Iub PS throughput
T1
T2
Iub PS UL Throughput
TU
TU1
TU2
Iub PS DL Throughput
TD
TD1
TD2
BO
BO1
BO2
Iub DL Transmission
Bandwidth
BD
BD1
BD2
Iub UL Transmission
Bandwidth
BU
BU1
BU2
U1
U2
S1
S2
NodeB number
N1
N2
The network capacity supported by the GOUa and GOUc must meet the requirement of
capacity expansion. Therefore, the following relationships should exist:
(1) E1 + E2 E
(2) T1 + T2 T; TU1 + TU2 TU; TD1 + TD2 TD
(3) BO1 + BO2 BO; BU1 + BU2 BU; BD1 + BD2 BU
(4) U1 + U2 U
(5) S1 + S2 S
(6) N1 + N2 N
Assume that capacity expansion is implemented by adding the GOUa. Then the required
number of GOUa is:
Issue 01 (2012-07-06)
111
UMTS RAN14.0
Dimensioning Rules
Iub
Item
Description
Iub CS Traffic
E2
Iub PS throughput
Iub Transmission
Bandwidth
U2
S2
NodeB number
N2
Issue 01 (2012-07-06)
112
UMTS RAN14.0
Dimensioning Rules
According to the preceding table, the required number of GOUc can be calculated with the
method described in section 3.4.4 .
3.7 Constraints
3.7.1 Board Slot Configuration of the BSC6900
1. OMUa/OMUc:
For the BSC6810, slots 20 to 23 of the MPS are reserved for the OMUa.
For the BSC6900 RAN11.1, slots 20 to 23 of the MPS are reserved for the OMUa.
For the BSC6900 RAN12.0, the OMUa may be inserted in slots 20 to 23 or slots 24 to 27 of
the MPS.
For the BSC6900 RAN13.0/RAN14.0, the OMUc may be inserted in slots 24 to 25 of the
MPS.
Issue 01 (2012-07-06)
113
UMTS RAN14.0
Dimensioning Rules
2. GCUa/GCGa: This type of board can only be inserted in slots 12 and 13.
3. SCUa/SCUb: This type of board can only be inserted in slots 6 and 7 of the MPS and EPS.
4. DPUb/DPUe/SPUa/SPUb/NIUa:
For the BSC6810, the SPUa is inserted in a vacant slot of slots 0 to 11; the DPUb is inserted
in a vacant slot of slots of 8 to 19; the interface board is inserted in a vacant slot of slots 14 to
19. The slot number configured for the DPUb must be greater than that for the SPUa and
smaller than that for the interface board.
For the BSC6900, the interface board can only be inserted in slots 14 to 19. The
DPUb/DPUe/SPUa/SPUb/NIUa can be inserted in any vacant slot other than the reserved
ones. There is no sequence constraint technically. It is recommended that these boards be
preferentially inserted in slots of smaller numbers (that is, start from slot 0). Slots of larger
numbers should be reserved for interface units.
5. Interface board: The interface board should be inserted in a vacant slot of slots 14 to 19.
When the SCUa is used as the switch board in the subrack, restricted by the slot bandwidth
provided by the SCUa, the GOUc, FG2c, and UOIc can only be inserted in vacant slots of
slots 16 to 23.
Configuration principle:
Each subrack can be configured with up to5 MPUs. The BSC6900 can be configured with up
to 24 MPUs.
(2) All SPUs, DPUs, and interface boards must be configured under a certain MPU. The SPUs
managed by an MPU constitute a small control plane resource pool. The DPUs managed by
an MPU constitute a user plane resource pool. The MPUs within a BSC6900 regularly
communicate with each other on the load. When the load of an MPU exceeds the preset
threshold, the processing resources managed by other MPUs will share the load.
Issue 01 (2012-07-06)
114
UMTS RAN14.0
Dimensioning Rules
(3) One MPU is configured for every three pairs of SPUs. The resource allocation capability
of the MPU matches the resource allocation requirements (including allocation of SPUs,
DPUs, and interface boards) generated by the traffic volume supported by the three pairs of
SPUs.
When a UE originates a call, the BSC6900 allocates resources as follows:
The NodeB/cell can be configured on the Iub INT (Iub interface board) and the SPU with
MML commands.
When the UE under a certain NodeB/cell originates a call, the call is connected to the Iub INT
where the NodeB/cell is configured and then processed on the SPU where the NodeB/cell is
configured.
If the SPU is not overloaded, it applies to the manager, MPU, for a DPU. The MPU
preferentially assigns its own DPU to process the call. In this scenario, the interface board, the
SPU, and the DPU belong to the same MPU (as shown in the call flow of UE1).
If the SPU is overloaded, it applies to the manager, MPU, for a new SPU. The MPU
preferentially assigns its own SPU to process the call. If another SPU managed by the MPU is
available, the new SPU applies to the MPU for a DPU and the MPU preferentially assigns its
own DPU to process the call. In this scenario, the interface board, the SPU, and the DPU
belong to the same MPU.
If the SPU is overloaded and the SPU load within the MPU reaches the sharing threshold (the
threshold can be specified with an MML command), the MPU seeks for a light loaded SPU in
other MPUs to process the call (as shown in the following figure). The assigned SPU applies
to its MPU for a DPU. In this scenario, the UE call flow is processed across MPUs (as shown
in the call flow of UE2). If MPU1 and MPU2 are not in the same subrack, the call of UE2 is
processed across subracks.
Impact of cross-subrack call processing: This increases traffic between subracks. Therefore,
the inter-subrack switching capability should be considered.
If the SCUa is used as the switch board in the subrack, the inter-subrack bandwidth provided
by the SCUa is 4 Gbit/s at the physical layer and 2.4 Gbit/s at the application layer. If a large
Issue 01 (2012-07-06)
115
UMTS RAN14.0
Dimensioning Rules
amount of traffic flows across subracks, the inter-subrack switching capability may be
insufficient, affecting the normal flow of traffic.
If the SCUb is used as the switch board in the subrack, the inter-subrack bandwidth provided
by the SCUb is 40 Gbit/s at the physical layer. Generally, such a bandwidth is large enough to
ensure smooth flow of traffic.
The MPU efficiency can be maximized by reducing cross-MPU or cross-subrack load sharing.
Therefore, resources of the same MPU should be preferentially selected for processing
services of a single user. For this purpose, during module configuration and layout, it is
recommended that service processing modules and interface units be evenly distributed in
each MPU and subrack. That is, the processing capabilities of the signaling plane, the user
plane, and interface in all subracks should be at the same level. Assume that there are nine
DPUe boards, 12 SPUb boards, six interface units, and three subracks. Then it is
recommended that three DPUe boards, four SPUb boards, and two interface units be
configured for each subrack.
To prevent the inter-subrack traffic from exceeding the switching bandwidth threshold, you
are recommended to configure the SPUs, DPUs, and interface boards managed by the MPU in
the same physical subrack.
Issue 01 (2012-07-06)
116
UMTS RAN14.0
Dimensioning Rules
Principle 2: Evenly distribute NodeBs to SPU subsystems. During deployment, configure the
138 NodeBs on 138 SPU subsystems respectively.
Principle 3: Based on Principle 2, consider the difference between hot spot NodeBs and nonhot-spot NodeBs and the fact that the capability of subsystems 0 and 7 is not as good as that
of subsystems 1 to 6 on the SPUb (see Table 3-29). Then preferentially deploy hot spot
NodeBs on subsystems 1 to 6.
Principle 4: After the deployment conducted in line with Principle 2, on which SPU
subsystem the new NodeB (the 139th one) should be deployed depends on the following
factors: (1) The CPU load of the SPU subsystem during busy hours; (2) load generated by
users of similar NodeBs that have been deployed or load generated by users of NodeBs in
adjacent areas (after the deployment conducted in line with Principle 1, the load generated by
users of NodeBs to SPU subsystems can be obtained). If the sum of the two loads on a
subsystem does not exceed 50%, the new NodeB can be configured on this subsystem.
Table 3-29 Capability difference of SPUa and SPUb subsystems
SSN
SPUa
SPUb
60%
90%
90%
90%
90%
90%
90%
70%
Issue 01 (2012-07-06)
117
UMTS RAN14.0
Dimensioning Rules
DPU
b
Service Type
(UL/DL)
User Number
DSP CPU
Throughput
(Mbit/s)
58/384 kbit/s
450
80%
115/198
58/58 kbit/s
930
80%
111
32/32 kbit/s
1200
80%
80
8/42 kbit/s
1275
80%
72
2. DPUe
In RAN12.0, when all DPUe boards process the PS service, if the average rate of the PS RAB
is 64/384 kbit/s or above in the uplink/downlink, one hardware capacity license (165 Mbit/s)
can be configured for the DPUe, supporting up to 500 Mbit/s PS throughput. If the average
rate of the PS RAB is lower than 64/384 kbit/s in the uplink/downlink, the PS throughput
supported by the DPUe will vary. If the PS throughput supported by the DPUe is lower than
335 Mbit/s, the capacity license does not need to be configured because the hardware capacity
license (165 Mbit/s) cannot improve the processing capability of the DPUe.
The following table lists the DPUe V900R012 test data:
DPUe
Service Type
User Number
DSP CPU
Throughp
ut (Mbit/s)
58/340 kbit/s
1290
80%
535
58/58 kbit/s
2400
80%
298
32/32 kbit/s
3300
80%
226
8/42 kbit/s
3596
80%
196
V900R012
In RAN14.0, when all DPUe boards process the PS service, if the average rate of the PS RAB
is 64/384 kbit/s or above in the uplink/downlink, one hardware capacity license (165 Mbit/s)
and one hardware capacity license (300 Mbit/s) can be configured for the DPUe, supporting
up to 800 Mbit/s PS throughput. If the average rate of the PS RAB is lower than 64/384 kbit/s
in the uplink/downlink, the PS throughput supported by the DPUe will vary. If the PS
throughput supported by the DPUe is lower than 335 Mbit/s, the capacity licenses do not need
to be configured because they cannot improve the processing capability of the DPUe.
The following table lists the DPUe V900R013 test data:
DPUe
Service Type
User
Number
DSP CPU
Throughp
ut (Mbit/s)
64/384 kbit/s
2010
76%
807
64/128 kbit/s
3850
76%
528
64/64 kbit/s
3990
76%
419
32/32 kbit/s
5880
80%
302
V900R013C000
Issue 01 (2012-07-06)
118
UMTS RAN14.0
Dimensioning Rules
8/8 kbit/s
6700
72%
105
Issue 01 (2012-07-06)
119
UMTS RAN14.0
Dimensioning Rules
As a result, the signaling processing board is overloaded although the user plane traffic does
not reach the designed specification.
In this case, network requirements should be recalculated according to the current traffic
model and signaling processing boards must be added accordingly.
The interface board processes signaling and data. The interface board structure is shown in the
following figure. The interface board processes the session setup and release procedure and
the micro engine (ME) processes data (corresponding to the user plane traffic of the traffic
model). The initial configuration may meet the capacity requirement. However, after the
traffic model changes, the interface board CPU may be overloaded even if the network load
does not reach the maximum value initially designed.
Issue 01 (2012-07-06)
120
UMTS RAN14.0
Dimensioning Rules
VS.CSLoad.Erlang.Equiv.RNC
VS.CSLoad.MaxErlang.Equiv.RNC
VS.R99PSLoad.ULThruput.RNC;
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 01 (2012-07-06)
121
UMTS RAN14.0
Dimensioning Rules
Please contact Huawei engineers who can obtain the document "iManager M2000 V200R012
Network Management Capacity Specification".
Issue 01 (2012-07-06)
122
UMTS RAN14.0
Dimensioning Rules
Issue 01 (2012-07-06)
123
UMTS RAN14.0
Dimensioning Rules
6 FAQs
FAQs
NodeB part:
Q1: What is the maximum number of CPRI interfaces that can be supported by a BBU?
Which boards (in which slots) support connection to an RF module?
A: See section 2.5.1 .
Q2: In RAN13.0 and later versions, a BBU can support up to six WBBPs. In this case, what is
the restriction to board configuration?
A: When more than four WBBPs are configured, two WBBPd boards must be inserted in slot
2 and slot 3 respectively or one WBBPb and one WBBPd in slot 2 and slot 3.
Q3: Do HSDPA and HSUPA signaling and channel associated signaling consume CEs? Are
they covered by the CE license purchased by the customer?
A: See section 2.5.3 .
Q4: What should be considered in baseband configuration when the customer's network needs
to support DC + 2 x MIMO?
A: See the description of DC + 2 x MIMO configuration in section 2.5.4 .
RNC part:
The "RNC Dimensioning Guide" chapter describes procedures involved in BSC6900
configuration, answering the following questions:
1. How to calculate the network capacity requirement according to the traffic model: see
section 3.3 .
2. What should be considered in configuring the SPU: see section 3.4.1 .
3. What should be considered in configuring the DPU: see section 3.4.2 .
4. What should be considered in configuring the interface board: see section 3.4.3 .
5. How to implement capacity expansion through mixed insertion of boards: see section 3.5 .
6. How to configure boards and design the layout of NodeBs on boards to ensure the optimal
processing capability of hardware configurations: see section 3.7 .
RNC configurations depend on the traffic model. What if the traffic model provided by the
customer contains insufficient information?
Issue 01 (2012-07-06)
124
UMTS RAN14.0
Dimensioning Rules
6 FAQs
Traffic model parameters have a great impact upon the capacity calculation and network
configuration. In the initial period of network deployment, if traffic model information is
unavailable and it is impossible to determine initial values of relevant parameters, a
hypothetical traffic model (input information provided in section 3.3.1 ) should be developed
according to actual site conditions and by reference to the traffic model defined by Huawei.
This should be notified to and agreed by the customer. Sometime after the network is put into
operation, the network configuration will be adjusted according to the actual traffic model.
Case 1: Requirements provided by the customer cover only Erlangs, PS throughput, NodeBs,
and cells.
Requirements provided by the customer lack information in the following two aspects:
(1) No signaling requirement. Nowadays, smart phones are more and more widely used. The
low signaling processing capability tends to be the bottleneck of device performance.
(2) No average rate of the PS RAB. The throughput of boards is related to the average rate of
the PS RAB (the DPU specification and interface board specification are based on the UL/DL
rate of 64/384 kbit/s; if the average rate of the PS RAB is lower than this value, the
throughput of the DPU and interface board may be lower than the claimed specifications).
How to satisfy customer requirements: To provide relatively appropriate configurations,
develop a hypothetical traffic model according to the traffic models of other networks in the
same region.
Case 2: Requirements provided by the customer cover the throughput, Erlangs, RRC times,
NodeBs, and cells.
RRC procedures include non-service RRCs such as location update and route update, SMS
RRC, and call-related RRCs (CS call, VP call, and PS call). The BHCA specification of the
BSC6900 contains only call-related RRCs (CS call, VP call, and PS call). Therefore, the
BHCA of the BSC6900 can be taken as a subset of the RRC indicator.
Note that the consumption of device resources in an RRC procedure is not just the usage of
resources by the procedure, but includes usage of resources by all related signaling procedures
before the RRC procedure. For example, a UE originates a PS RRC request. After the PS
connection is established, m soft handovers and n channel switching procedures may take
place in the entire PS service procedure. After the PS service is completed, the RRC is
released. System usage in this RRC procedure includes the usage of resources by the RRC
connection establishment procedure, m soft handovers, n channel switching procedures, and
the RRC release procedure.
Issue 01 (2012-07-06)
125
UMTS RAN14.0
Dimensioning Rules
6 FAQs
The number of connected users generally covers Cell_DCH Connect users, Cell_FACH
Connect, Cell_PCH Connect users, and Cell_URA_PCH Connect users. The number of
Cell_DCH Connect users and that of Cell_FACH Connect users can be calculated based on
traffic model parameters (see Iub active users).
How to satisfy customer requirements:
(1) Communicate with the customer and ask the customer to provide the proportion of
Cell_Connect users and Cell_FACH Connect users to the number of connected users or
provide a hypothetical proportion on which a consensus has been reached with the customer.
(2) Develop a hypothetical traffic model according to traffic models of other networks in the
same region. The number of Iub active users calculated based on the hypothetical traffic
model should meet customer requirements.
Issue 01 (2012-07-06)
126