BSC6900 Configuration Principle (Global) (V900R016C00 - 05) (PDF) - en

SRAN9.0&GBSS16.0&RAN16.
0 BSC6900
Configuration Principles (Global)

Issue
05
Date
2014-10-29
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the 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.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 05 (2014-10-29)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Contents
Contents
1 Change History..............................................................................................................................1
2 Introduction....................................................................................................................................6
2.1 Overview........................................................................................................................................................................6
2.2 Version Difference.........................................................................................................................................................6
2.2.1 BSC6900 GSM............................................................................................................................................................6
2.2.2 BSC6900 UMTS..........................................................................................................................................................7
2.2.3 BSC6900 GU...............................................................................................................................................................7
2.3 Laws and Regulations.....................................................................................................................................................7
2.3.1 Cyber Security Requirements......................................................................................................................................7
2.3.2 Export Control.............................................................................................................................................................7
3 Application Overview..................................................................................................................9
4 Product Configurations..............................................................................................................13
4.1 BSC6900 GSM Product Configurations.......................................................................................................................13
4.1.1 Hardware Capacity License.......................................................................................................................................14
4.1.2 Service Processing Units...........................................................................................................................................14
4.1.3 Interface Boards.........................................................................................................................................................22
4.1.4 Clock Boards.............................................................................................................................................................28
4.1.5 General Principles for Board Configuration..............................................................................................................28
4.1.6 Subracks.....................................................................................................................................................................29
4.1.7 Cabinets.....................................................................................................................................................................31
4.1.8 Auxiliary Materials....................................................................................................................................................31
4.1.9 Example of Typical BSC6900 GSM Configuration..................................................................................................32
4.1.10 BSC6900 GSM Recommended Capacity for Delivery...........................................................................................35
4.2 BSC6900 UMTS Product Configurations....................................................................................................................35
4.2.1 Impact of Traffic Model on Configurations..............................................................................................................36
4.2.2 Hardware Capacity License.......................................................................................................................................38
4.2.3 Service Processing Units...........................................................................................................................................40
4.2.4 Interface Boards.........................................................................................................................................................46
4.2.5 Clock Boards.............................................................................................................................................................54
4.2.6 Principles for Board Configurations..........................................................................................................................54
4.2.7 Subracks.....................................................................................................................................................................55
Issue 05 (2014-10-29)

ii
Contents
4.2.8 Cabinets.....................................................................................................................................................................57
4.2.9 Auxiliary Materials....................................................................................................................................................57
4.2.10 Restrictions on Inter-Subrack Switching.................................................................................................................58
4.2.11 Example of Typical BSC6900 UMTS Configuration.............................................................................................59
4.2.12 BSC6900 UMTS Recommended Capacity for Delivery.........................................................................................66
4.3 BSC6900 GU Product Configurations.........................................................................................................................66
5 Expansion and Upgrade Configurations.................................................................................68

5.1 BSC6900 GSM Hardware Expansion and Upgrade Configurations............................................................................68
5.1.1 Hardware Expansion and Upgrade Configurations...................................................................................................68
5.1.2 Hardware Capacity License Expansion.....................................................................................................................85
5.1.3 Examples of Hardware Expansion............................................................................................................................85
5.2 BSC6900 UMTS Hardware Expansion and Upgrade Configurations.........................................................................88
5.2.1 Hardware Expansion and Upgrade Configurations...................................................................................................88
5.2.2 Hardware Capacity License Expansion.....................................................................................................................89
5.2.3 Examples of Hardware Expansion............................................................................................................................89
5.2.4 Examples of Hardware Capacity License Expansion................................................................................................90
5.3 BSC6900 GU Hardware Expansion and Upgrade Configurations...............................................................................91
6 Spare Parts Configuration..........................................................................................................93

6.1 BOM of Spare Parts......................................................................................................................................................93
6.2 Configuration Principles for Spare Parts......................................................................................................................93
6.2.1 Poisson Algorithm.....................................................................................................................................................93
6.2.2 Percentage Algorithm................................................................................................................................................94
6.2.3 Notes..........................................................................................................................................................................94
7 Appendix.......................................................................................................................................95
7.1 Hardware Version.........................................................................................................................................................95
7.2 GSM Configuration Reference.....................................................................................................................................96
7.2.1 GSM Traffic Model...................................................................................................................................................96
7.2.2 GSM Board Specifications......................................................................................................................................100
7.2.3 GSM Board Usage Efficiency.................................................................................................................................104
7.2.4 Ater RSL Configuration Calculation Tool..............................................................................................................104
7.2.5 Suggestions for Lb Interface Configuration............................................................................................................105
7.3 UMTS Configuration Reference................................................................................................................................105
7.3.1 UMTS Traffic Model...............................................................................................................................................105
7.3.2 UMTS Hardware Specifications..............................................................................................................................109
8 Acronyms and Abbreviations.................................................................................................114
Issue 05 (2014-10-29)

iii
1 Change History
Change History
This chapter describes changes in different document versions.

05 (2014-10-29)
This issue incorporates the following changes.
Change
Type
Change Description
Editorial
change
Added
None.
Modified
l Added descriptions about new boards SPUc, GOUe, GCGb,

and GCUb and stated that the new boards and their
corresponding old boards can coexist and be inserted into
each other's slots in 2.2 Version Difference.
l Updated the rules for calculating the number NIU boards
required by PRS KQI related features in 4.2.3 Service
Processing Units.
l Updated the method of calculating the number of DPUe
boards (N+1 redundancy recommended) in 4.2.3 Service
Processing Units.
l Added WB-AMR specifications of interface boards in 4.2.4
Interface Boards.
Deleted
None.
04 (2014-09-10)
Issue 05 (2014-10-29)
Change
Type
Change Description
Editorial
change
Added
None.

1 Change History
Change
Type
Change Description
Modified
l Added the description that SPUb and SPUc boards, GOUc

and GOUe boards, and clock boards can be placed in a pair
of active and standby slots. For details, see 2.2.2 BSC6900
UMTS.
l Added low voltage differential signal (LVDS) restrictions
imposed on the POUc calculation to 4.1.3 Interface
Boards.
l Added SPUb, NIUa, and SAUc boards as examples of
evenly configured boards. For details, see 4.2.10
Restrictions on Inter-Subrack Switching.
l Added basic configuration principles. For details, see 5.3
BSC6900 GU Hardware Expansion and Upgrade
Configurations.
Deleted
None.
03 (2014-06-30)
Change Type
Change Description
Editorial
change
Added
None.
Modified
l Modified the method of calculating the number of DPUf

boards. For details, see 4.1.2 Service Processing
Unitsand5.1.1 Hardware Expansion and Upgrade
Configurations.
l Added restrictions imposed on interface boards in Abis over
TDM networking mode. For details, see 4.1.3 Interface
Boards.
Deleted
None.
02 (2014-05-31)
Issue 05 (2014-10-29)
Change Type
Change Description
Editorial
change
Added
None.

1 Change History
Change Type
Change Description
Modified
l Added the impacts of key quality indicator (KQI) features

on DPUe and NIUa boards. For details, see 4.2.3 Service
Processing Units.
l Optimized descriptions throughout the document.
Deleted
None.
01 (2014-04-29)
Change Type
Change Description
Editorial
change
Added
None.
Modified
Converted some descriptions to tables. For details, see 4.2.7

Subracks.
Deleted
None.
Draft C (2014-04-21)
Change Type
Change Description
Editorial
change
Added
2.3 Laws and Regulations
Modified
l Modified the method of calculating the number of SPUc

boards. For details, see 4.2.11 Example of Typical
BSC6900 UMTS Configuration.
l Modified some descriptions. For details, see 5.1.1
Hardware Expansion and Upgrade Configurations.
l Added the capacity in different transmission modes. For
details, see 7.2.1 GSM Traffic Model.
Deleted
None.
Draft B (2014-02-28)
Issue 05 (2014-10-29)

1 Change History
Change
Type
Change Description
Editorial
change
Added
None.
Modified
l Added descriptions about board replacement. For details,

see 2.2.2 BSC6900 UMTS.
l Optimized the document organization. For details, see 4.1.9
Example of Typical BSC6900 GSM
Configurationand4.2.11 Example of Typical BSC6900
UMTS Configuration.
l Modified some descriptions. For details, see 4.2.1 Impact
of Traffic Model on Configurations,4.2.2 Hardware
Capacity License,4.2.3 Service Processing Units,4.2.4
Interface Boards, and7.3.2 UMTS Hardware
Specifications.
l Modified the configuration principles for SAU boards. For
details, see 4.2.6 Principles for Board Configurations.
l Canceled the restrictions imposed on MPU-related
configurations. For details, see 4.2.10 Restrictions on
Inter-Subrack Switching.
Deleted
Laws and Regulations.
Draft A (2014-01-27)
Compared with Issue 02 (2013-06-16) of V900R015C00, this issue incorporates the following
changes.
Change
Type
Change Description
Editorial
change
Added
l 2.3 Laws and Regulations

l 6 Spare Parts Configuration
l 7.2.4 Ater RSL Configuration Calculation Tool
l 7.3.2 UMTS Hardware Specifications
Modified
l Modified the configuration principles for XPUc processing

units and modified the XPUb board specifications for
eGBTSs. For details, see 4.1.2 Service Processing Units.
l Added information about power consumption. For details,
see 4.1.7 Cabinetsand4.2.8 Cabinets.
l Added GOUe and XPUc board specifications. For details,
see 4.1.3 Interface Boards.
l Added GOUe board specifications. For details, see 4.2.4
Interface Boards.
Issue 05 (2014-10-29)

Change
Type
1 Change History
Change Description
Deleted
Issue 05 (2014-10-29)
None.

2 Introduction
Introduction
2.1 Overview
This document describes the configuration principles of the BSC6900 V900R016C00.
The BSC6900 can be configured as a BSC6900 GSM, BSC6900 UMTS, or BSC6900 GSM
+UMTS (GU) to adapt to various application scenarios.
l
A BSC6900 GSM works in GSM Only (GO) mode and functions as a GSM BSC.
A BSC6900 UMTS works in UMTS Only (UO) mode and functions as a UMTS RNC.
A BSC6900 GU works in GSM&UMTS (GU) mode and functions as a GSM BSC and
UMTS RNC.
This document covers topics, such as product specifications, configuration principles, and
capacity expansion and upgrade configurations of the BSC6900 GSM, BSC6900 UMTS, and
BSC6900 GU.
2.2 Version Difference

2.2.1 BSC6900 GSM
The BSC6900 GSM in the minimum configuration consists of one cabinet, in which one subrack,
the main processing subrack (MPS), is configured. The BSC6900 GSM in the maximum
configuration consists of two cabinets, in which one MPS and three extended processing
subracks (EPSs) are configured. The BSC6900 V900R016GSM supports five hardware
versions: HW60 R8, HW69 R11, HW69 R13, HW69 R15, HW69 R16.
A BSC6000 or BSC6900 GSM can be upgraded to BSC6900 V900R016 by upgrading software.
When HW60 R8 or HW69 R11 hardware is used, software must be upgraded version by version.
Configuration principles and capacity expansion principles remain unchanged after the upgrade.
If only the software of a BSC6000 or BSC6900 GSM is upgraded to GBSS16.0, capacity remains
unchanged after the upgrade.
This document describes the configuration principles of the BSC6900 GSM using HW69 R16
hardware.
Issue 05 (2014-10-29)

2 Introduction
2.2.2 BSC6900 UMTS

The BSC6900 UMTS in the minimum configuration consists of one cabinet, in which one
subrack (MPS) is configured. The BSC6900 UMTS in the maximum configuration consists of
two cabinets, in which one MPS and five EPSs are configured. The BSC6900
V900R016C00UMTS supports five hardware versions: HW68 R11, HW69 R11, HW69 R13,
HW69 R15, HW69 R16.
A BSC6810 or BSC6900 UMTS can be upgraded to a BSC6900 V900R016C00by upgrading
software. When HW60 R8 or HW69 R11 hardware is used, software must be upgraded version
by version. Configuration principles and capacity expansion principles remain unchanged after
the upgrade. If only the software is upgraded toRAN16.0 capacity remains unchanged after the
upgrade.
HW69 R16 introduces new boards SPUc, GOUe, GCUb, and GCGb, which can coexist with
the corresponding old boards SPUb, GOUc, GCUa, and GCGa. The new and old boards have
the same capabilities and specifications. An old board and its corresponding new board (for
example, SPUb and SPUc, GOUc and GOUe, GCGa and GCGb, and GCUa and GCUb) can
work in active/standby mode.
BSC6900 V900R016C00 has the same basic specifications as BSC6900 V900R015C00.
BSC6900 UMTS supports the RNC in Pool feature to pool BSC6900s and BSC6910s. RNCs in
a resource pool share resources and back up for each other.
This document describes the configuration principles of the BSC6900 UMTS using HW69
R16 hardware.
2.2.3 BSC6900 GU
The BSC6900 GU in the minimum configuration consists of one cabinet, in which two subracks
are configured: one subrack is used for UMTS and the other for GSM. The BSC6900 GU in the
maximum configuration consists of two cabinets, in which one MPS and five EPSs are
configured. The BSC6900 V900R016 GU supports the following hardware versions: HW60 R8/
HW68 R11, HW69 R11, HW69 R13, HW69 R15, HW69 R16.
A BSC6000, BSC6810, or BSC6900 GU can be upgraded to BSC6900 V900R016C00 by
upgrading software. When HW60 R8, HW68 R11, or HW69 R11 hardware is used, is used,
software must be upgraded version by version. Configuration principles and capacity expansion
principles remain unchanged after the upgrade. If only the software version is upgraded to
SRAN9.0, capacity remains unchanged after the upgrade.
2.3 Laws and Regulations

2.3.1 Cyber Security Requirements
The BSC6900 meets A1, A2, and B security requirements and newly-added features are not
security-sensitive.
2.3.2 Export Control

The BSC6900 contains an embargoed item, which is listed in the following table.
Issue 05 (2014-10-29)

Issue 05 (2014-10-29)
2 Introduction
Item
Description
ECCN
Control
Reason
Measure
Rem
arks
05330231
System Application
Software, Light
Application Data
Management Software
Package(5.5 S), 1 Year
Standard Product
Services
5D002
Laws and
regulations
Do not sell the

MySQL
database in
class-A
countries.
N/A
(upon
vendor's
requirements)

3 Application Overview
Application Overview
The hardware platform of the BSC6900 is characterized by high integration, high performance,
and a modular structure to adapt to different scenarios and provide operators with a high-quality
network at a low cost. In addition, the network is easy to expand and maintain. Figure 3-1 shows
a single BSC6900 cabinet.
Figure 3-1 BSC6900 N68E-22 cabinet
Figure 3-2 shows the configuration of a BSC6900 cabinet.
Issue 05 (2014-10-29)

Figure 3-2 Configuration of a BSC6900 cabinet (front view and rear view)
Table 3-1 describes the BSC6900 specifications.

Table 3-1 BSC6900 specifications
Performance
Specifications
BSC6900
GSM
l Maximum number of cabinets: 2

l Maximum number of subracks: 4
l Maximum GSM specifications (all-TDM transmission):
4096 TRXs, 24,000 Erlang, 5,900,000 BHCA, 16,384
activated PDCHs, and 1536 Mbit/s bandwidth on the Gb
interface
l Maximum GSM specifications (all-IP transmission for
GSM): 8192 TRXs, 45,000 Erlang, 11,000,000 BHCA,
32,768 activated PDCHs, and 3072 Mbit/s bandwidth
over the Gb interface
BSC6900
UMTS
Issue 05 (2014-10-29)
l Maximum number of cabinets: 2

l Maximum number of subracks: 6
The maximum specifications are 3060 NodeBs, 5100
cells, 5,300,000 BHCA (7,000,000 BHCA including
SMS), and 40 Gbit/s or 167,500 Erlang.

10
BSC6900
GU
l Maximum GSM specifications (all-TDM transmission for

When the maximum GSM specifications are reached, the
UMTS processing capabilities of the BSC6900
V900R017 are 1440 NodeBs, 2400 cells, 1,675,000
BHCA, and 12.8 Gbit/s or 53,600 Erlang.
The preceding specifications are provided by full
configuration of GSM boards in four subracks and UMTS
boards in two subracks.
l Maximum GSM specifications (all-IP transmission for
When the maximum GSM specifications are reached, the
UMTS processing capabilities of the BSC6900
V900R017 are 1440 NodeBs, 2400 cells, 1,675,000
BHCA, and 12.8 Gbit/s or 53,600 Erlang.
configuration of GSM boards in four subracks and UMTS
boards in two subracks.
l Maximum UMTS specifications: 3060 NodeBs, 5100
cells, 4,430,000 BHCA, and 33.6 Gbit/s or 140,700
Erlang.
When the maximum UMTS specifications are reached,
the GSM processing capabilities of the BSC6900
V900R017 are 1536 TRXs, 9750 Erlang, 6144 PDCHs,
576 Mbit/s over the Gb interface, and 2,625,000 BHCA
in all-TDM transmission mode, and 3584 TRXs, 22,750
Erlang, 14,336 PDCHs, 1344 Mbit/s over the Gb
interface, and 6,125,000 BHCA in all-IP transmission
mode.
configuration of UMTS boards in five subracks and GSM
boards in one subrack.
Structural
Specifications
Dimensions of the BSC6900 N68E-22 cabinet (H x W x D): 2200 mm x

600 mm x 800 mm (86.61 in. x 23.62 in. x 31.50 in.)
Single cabinet weight 320 kg (705.6 lb); load-bearing capability of the
floor 450 kg/m2 (0.64 bf/in.2)
Power Supply
Specifications
Issue 05 (2014-10-29)
48 V DC
Input voltage range: 40 V to 57 V

11
NOTE
l BSC6900 specifications are not equal to the sum of board specifications.

l BSC6900 specifications are designed based on customers' requirements and the product plan. During
product specification design, business factors and technical factors, such as system load and board
quantity limitations, are taken into consideration to define an equivalent system specification.
l Specifications vary with different versions.
l The definition of BHCA in GSM is different from that in UMTS. The BHCA defined in UMTS is the
number of call attempts and the BHCA capability varies with the traffic model.
l The BHCA defined in GSM is the maximum number of equivalent BHCAs under the Huawei traffic
model. All user activities, including CS location updates, CS handovers, PS TBF setups, PS temporary
block flow (TBF) releases, and PS pagings, can be converted into equivalent BHCAs. This better
reflects the impact of the traffic model change on system performance. In full configuration, when the
BHCA reaches the maximum, the system reaches the designed maximum processing capability if the
average CPU usage does not exceed 75% of the average flow control threshold.
l In GSM, if 5,900,000 (or 11,000,000) equivalent BHCA defined in GSM are converted from only CS
services in the Huawei default CS traffic model, the corresponding BHCA for calls only is 1,440,000
(or 2,680,000) in the industry traffic model. If the equivalent BHCA are converted from both CS and
PS services in Huawei default PS traffic model, the corresponding BHCA for only calls is 1,000,000
(or 2,120,000) in the industry traffic model.
l The UMTS BHCA is based on the balanced traffic model, and the UMTS PS throughput is based on
the high-PS traffic model. For details about the definitions of the traffic models, see section 7.3.1 UMTS
Traffic Model.
Issue 05 (2014-10-29)

12
4 Product Configurations
Product Configurations
4.1 BSC6900 GSM Product Configurations

A BSC6900 GSM consists of hardware and hardware capacity licenses. The hardware includes
cabinets, subracks, data processing units, signaling processing units, network intelligence units,
service aware units, interface boards, and clock boards. The hardware capacity licenses includes
the Network Intelligence Throughput license, Mega BSC license, and BBU Carrier Capacity
license.
Table 4-1 lists the mapping between hardware versions and GBSS versions.
Table 4-1 Mapping between hardware versions and GBSS versions
Hardwa
re
Version
BSC6000
BSC6900
GBSS6.1/
GBSS7.0/
GBSS8.0/
GBSS8.1
GBSS9.
0
GBSS1
2.0
GBSS1
3.0
GBSS1
4.0
GBSS15
.0
GBSS1
6.0
HW60
R8
Supported
Support
ed
Support
ed
Support
ed
Support
ed
Supporte
d
Support
ed
HW69
R11
Support
ed
Support
ed
Support
ed
Support
ed
Supporte
d
Support
ed
HW69
R13
Support
ed
Support
ed
Supporte
d
Support
ed
HW69
R15
Supporte
d
Support
ed
HW69
R16
Support
ed
Note that if two boards work in active/standby mode, the two boards must be identical.
Issue 05 (2014-10-29)

13
To replace a single-core board with a multi-core board, you must configure data related to board
removal and addition before replacing the board. Do not directly remove the single-core board
and then insert the multi-core board into the slot.
The following BSC6900 UMTS boards can also be used in BSC6900 GSM mode (these GSM
boards cannot be used in UMTS mode):
l
UMTS SPUb board with the same capacity as GSM XPUb/XPUc board
UMTS SPUc board with the same capacity as GSM XPUb/XPUc board
UMTS DPUe board with the same capacity as GSM DPUg board
UMTS DPUb board with the same capacity as GSM DPUc or DPUd board
NOTICE
For two boards to work in active/standby mode, the two boards must be identical. To replace a
single-core board in a slot with a multi-core board, you must first remove the single-core board
from the slot and then insert the multi-core board into the slot.
Section 4.1.1 Hardware Capacity Licensedescribes the configuration principles of hardware
capacity licenses. Sections4.1.2 Service Processing Unitsthrough4.1.8 Auxiliary Materials
cover the configuration principles of the BSC6900 GSM hardware and relevant restrictions.
4.1.1 Hardware Capacity License

No new licenses are provided by the BSC6900 V900R016C00 GSM.
4.1.2 Service Processing Units

Table 4-2 lists service processing unites in GBSS17.0.
Issue 05 (2014-10-29)

14
Table 4-2 Service processing units

Model
Board
Name
Descriptio
n
Specification
s
Remarks
WP1D00
0DPU05
DPUf
CS Data
Processing
Unit
(1920CIC/
3840 IWF
(TDM&IP)/
7680IWF
(IP&IP))
Provides CS
service
processing
(including
the TC
function and
IWF
function)
and works in
N+1 backup
mode
TC function:
1920 CICs (A
over TDM)
For the TC
function, the
specifications of
WP1D000DPU05
are 1920 CICs
when nonwideband AMR
coding schemes
are used. When
wideband AMR
coding schemes
are used, the
specifications of
WP1D000DPU05
are 50% of 1920
CICs (960 CICs),
equivalent to 2
times of a common
call.
IWF function:
3840 channels
(Abis over IP
and Ater over
TDM, or Abis
over TDM and
A over IP)
7680 CICs
(Abis over IP
and A over IP)
For the IWF

function, the
specifications of
the DPUf are
unchanged
regardless of
whether nonwideband or
wideband AMR
coding schemes
are used. This is
because TC
coding is not
involved in the
IWF function.
WP1D00
0DPU06
Issue 05 (2014-10-29)
DPUg
PS Data
Processing
Unit (1024
PDCH)
Provides PS
service
processing
and works in
N+1 backup
mode
1024 activated
PDCHs
The specifications
remain unchanged
110 PDCHs per regardless of the
coding schemes
DSP
(CS1 to CS4,
MCS1 to MCS9,
and EDGE+).

15
Model
Board
Name
Descriptio
n
Specification
s
WP1D00
0DPU03
DPUe
PS Data
Processing
Unit (1024
PDCH)
Provides PS
service
processing
and works in
N+1 backup
mode
1024 activated
PDCHs
WP1D00
0NIU00
NIUa
Network
Intelligence
Unit
Provides
intelligent
service
awareness
PS throughput:
50 Mbit/s
A maximum of
3200 Mbit/s is
supported. If the
Gb throughput is
higher than 50
Mbit/s, network
intelligence
throughput
licenses must be
purchased.
Network
Intelligence
Throughput
License
Provides
intelligent
service
awareness
PS throughput:
50 Mbit/s
One NIUa
provides 50 Mbit/s
PS throughput.
Extended
Processing
Unit (640)
Provides
signaling
processing
and works in
active/
standby
mode
l GBTS:
The BHCA is
based on Huawei
default traffic
model.
QM1SNI
U50M00
WP1D00
0XPU03
XPUc
Remarks
The specifications
remain unchanged
110 PDCHs per regardless of the
coding schemes
DSP
(CS1 to CS4,
MCS1 to MCS9,
and EDGE+).
640 TRXs
3900 Erlangs
1,050,000
BHCA
l eGBTS:
640 TRXs
3900 Erlangs
950,000 BHCA
Issue 05 (2014-10-29)

16
Model
Board
Name
Descriptio
n
Specification
s
Remarks
WP1D00
0XPU03
XPUc
(XPUI)
GSM
Extensible
Processing
Unit for
Computation
Service
Provides the
IBCA
function and
works in
independent
mode
None
Calculated based
on IBCA
requirements at
network
deployment.
Generally, two
WP1D000XPU03
s are configured by
default. (A
maximum of eight
WP1D000XPU03
s can be
configured based
on the network
requirements.)
WP1D00
0SPU03
SPUc
(NASP
)
Network
Assisted
Service
Process
Provides a
service
processing
unit to assist
the network
10 AC
The number of
QM1M000SPU00
is calculated based
on GBFD-511609
Intelligent Wi-Fi
Detection and
Selection
requirements at
network
deployment. One
QM1M000SPU00
is configured in
each BSC by
default.
NOTE
IWF: The interworking function (IWF) implements transmission format conversion. When Abis over IP
and Ater over TDM, or A over IP are used, the IWF performs format conversion between TDM and IP or
between IP and IP.
By default, the following boards are delivered: DPUf, DPUg, NIUa, XPUc, and SPUc (NASP).
The following table describes the network requirements during the configuration of
WP1D000DPU05 (DPUf).
Issue 05 (2014-10-29)

17
Item
Description
Remarks
Networking mode on the

A interface
Board
configurations are
affected by A over
IP transmission and
BM/TC separated
mode
In A over IP mode, the TC function is

implemented by the CN. Therefore, the
BSC provides the IWF function, not the
TC function.
APortType
In BM/TC separated mode, DPUf in the

TC subrack provides the TC function.
Whether the BM subrack provides the
IWF function depends on the
transmission mode. The BM subrack
needs to provide the IWF function only
when TDM transmission is used on the
Ater interface and IP transmission is used
on the Abis interface.
In BM/TC combined mode, the DPU
board provides both the TC and IWF
functions. Therefore, no extra board is
required to implement the IWF function.
Issue 05 (2014-10-29)
MaxACICPerBSC,
WbAMRRate
Number of CICs on
the A interface (nonwideband AMR
coding scheme):
includes the FR, HR,
and all types of
AMR coding
schemes
Calculated based on the actual number of

calls in the network
MaxACICPerBSC, (1
WbAMRRate)
Number of CICs on
the A interface
(wideband AMR
coding scheme):
includes all types of
wideband AMR
coding schemes

MaxACICPerBSCTDM
Number of CICs on
the A interface when
TDM transmission
is used on the A
interface in BM/TC
combined or BM/
TC separated mode

MaxACICPerBSCIP
Number of CICs on
the A interface in A
over IP mode


18
Item
Description
Remarks
MaxIWFPerBSCTDMIP
Number of CICs in
Abis over IP and
Ater over TDM or in
Abis over TDM and
A over IP
Calculated based on the network

structure and the traffic model.
MaxIWFPerBSCIPIP
Number of CICs in
A over IP and Abis
over IP
Calculated based on the network

structure and the traffic model.
Configuration principles for the WP1D000DPU05 (DPUf):

The number of WP1D000DPU05s to be configured depends on the number of required CICs.
WP1D000DPU05s can work in N+1 backup mode. Depending on the mode in use, there are 4
different ways to calculate the number of DPUf boards to be configured:
l
In BM/TC separated mode (or TDM/IP hybrid transmission in A over IP)

On the BM side:
The number of DPUf to be configured depends on the number of CICs that require IWF
conversion between TDM and IP and between IP and IP.
Number of DPUf = Roundup (MAXIWFPerBSCTDMIP/3840 + Max
(MAXIWFPerBSCIPIP - MAXIWFPerBSCTDMIP, 0)/7680,0) + 1
On the TC side:
Number of DPUf = Roundup (MaxACICPerBSCTDM/1920) + 1
In BM/TC combined mode (or TDM/IP hybrid transmission in A over IP)

The DPUf providing the TC function can support the IWF function of the same
specifications as TC.
Extra DPUf should be configured to provide the IWF function for the A-interface CIC
circuits in A over IP transmission.
Number of DPUf = Roundup (MaxACICPerBSCTDM/1920,0) + Roundup
(MAXIWFPerBSCTDMIP/3840 + Max (MAXIWFPerBSCIPIP MAXIWFPerBSCTDMIP, 0)/7680,0) + 1
A over IP
The number of DPUf to be configured depends on the number of CIC circuits that require
IWF conversion between TDM and IP and between IP and IP.
Number of DPUf = Roundup(MAXIWFPerBSCTDMIP/3840 + Max
(MAXIWFPerBSCIPIP - MAXIWFPerBSCTDMIP, 0)/7680,0) + 1
All IP
Number of DPUf = Roundup (MaxACICPerBSCIP/7680,0) + 1
Configuration principles for the WP1D000DPU06 (DPUg):

The following table describes the network requirements during the configuration of
WP1D000DPU06 (DPUg).
Issue 05 (2014-10-29)

19
Item
Description
Remarks
MaxActivePDCHPerBSC
Maximum number of activated

PDCHs
Calculated based on the number

of users and the traffic model.
If the PS function is configured, the number of DPUg to be configured depends on the number
of activated PDCHs that are configured. DPUg can work in N+1 backup mode.
Number of DPUg = Roundup (MaxActivePDCHPerBSC/1024, 0) + 1
NOTICE
The number of PDCHs activated on each DSP of the DPUg cannot exceed 110.
Configuration principles for the WP1D000NIU00 (NIUa) and the QM1SNIU50M00 (Network
Intelligence Throughput License):
The following table describes the network requirements that should be considered during the
configuration of WP1D000NIU00 (NIUa) and QM1SNIU50M00.
Item
Description
Remarks
Gb throughput
Throughput on the Gb interface

If intelligent service identification is required to improve efficiency of instant messaging (IM)

services, web browsing services, email services, streaming services, and P2P services, NIUa
must be configured. One NIUa board is always configured on a network.
Number of NIUa required in a network = 1
One NIUa provides 50 Mbit/s throughput processing capability. If Gb throughput is higher than
50 Mbit/s, you must apply for the Network Intelligence Throughput License and ensure that:
N_QM1SNIU50M00 = Roundup [(Gb throughput 50)/50, 0].
Otherwise,
N_QM1SNIU50M00 = 0
The following table describes the network requirements during the configuration of XPUc.
Issue 05 (2014-10-29)
Item
Description
Remarks
BHCA requirement
BHCA that need to be supported

in the network


20
Item
Description
Remarks
TRX Number
Total number of TRXs
Determined based on the

network plan
ERL Number
CS traffic volume (Erlang) that

needs to be supported in the
network

network plan
The number of XPUc boards to be configured depends on the total number of TRXs, BHCA
requirement, and CS traffic volume (Erlang) requirement. The number of XPUc boards to be
configured can be calculated as follows:
l
If the BSC manages only GBTSs:
Number of (XPUc) = 2 x Roundup (max [TRX Number/640, BHCA requirement/1,050,000,

ERL Number/3900], 0)
l
If the BSC manages only eGBTSs:
Number of (XPUc) = 2 x Roundup (max [TRX Number/640, BHCA requirement/950,000, ERL

Number/3900], 0)
l
If the BSC manages both GBTSs and eGBTSs:
Number of (XPUc) = 2 x Roundup (max [TRX Number/640, BHCA requirement x GBTS TRX
Number/TRX Number/1,050,000 + BHCA requirement x eGBTS TRX Number/TRX Number/
950,000, ERL Number/3900], 0)
NOTICE
When the VAMOS feature is enabled, the traffic volume supported by a single TRX increases.
Based on the preceding formula, more XPUc boards are required.
The following table describes the network requirements during the configuration of XPUI.
Item
Description
Remarks
IBCA requirement
Whether the network

requires the IBCA function
Calculated based on the number of

users and the traffic model.
A pair of XPUI boards are configured by default. A maximum of four pairs of XPUI boards can
be configured based on the network requirements.
If the IBCA function is required, an extra pair of XPUc boards must be configured to work as
XPUI.
The following table lists the network factors during the configuration of NASP.
Issue 05 (2014-10-29)

21
Item
Description
comment
NASP requirement
Whether the network requires

the GBFD-511609 Intelligent
Wi-Fi Detection and Selection
function
One NASP board is configured

for each BSC.
If the GBFD-511609 Intelligent Wi-Fi Detection and Selection feature is required, you must
configure one extra SPUc to work as NASP.
4.1.3 Interface Boards

The BSC6900 provides diversified interfaces to meet the requirements of different networking
modes.
Table 4-3 lists the interface boards required by the BSC6900 GSM.
Table 4-3 Interface boards
Model
Abbreviat
ion
Name
Where to Apply
WP1D000EIU
00
EIUb
TDM Interface Unit (32 E1/T1)
TDM transmission:
A/Ater/Abis/Lb
WP1D000OI
U01
OIUb
TDM Interface Unit (1 STM-1,

Channelized)
TDM transmission:
A/Ater/Abis/Lb
WP1D000PO
U01
POUc
TDM or IP Interface Unit (4 STM-1,

Channelized)
TDM/FR
transmission: A/Ater/
Abis/Lb/Gb
IP transmission: A/
Abis/Lb
WP1D000PE
U01
PEUc
IP Interface Unit (32 E1/T1)
FR or IP
transmission: A/
Abis/Lb/Gb
WP1D000FG
201
FG2c
IP Interface Unit (12 FE/4 GE,

Electrical)
IP transmission: A/
Abis/Lb/Gb/Iur-g
WP1D000GO
U03
GOUe
IP Interface Unit (4 GE, Optical)
IP transmission: A/
Abis/Lb/Gb/Iur-g
By default, the following boards are delivered: EIUb, OIUb, POUc, PEUc, FG2c, and GOUe.
Table 4-4 lists the specifications of interface boards on different interfaces.
Issue 05 (2014-10-29)

22
Table 4-4 Specifications of interface boards on different interfaces

Model
Transmissi
on Type
Port
Typ
e
Port
No.
Numb
er of
TRXs
Number
of CIC
circuits
(64 kbit/
s) on the
A
Interface
Numb
er of
CIC
circuits
(16
kbit/s)
on the
Ater
Interfa
ce
Gb
Through
put
(Mbit/s)
WP1D000
EIU00
(EIUb)
TDM
TD
M E1
32
384
960
3840
N/A
WP1D000
OIU00
(OIUb)
TDM
TD
M
CST
M-1
384
1920
7168
N/A
WP1D000
PEU00
(PEUc)
TDM
TD
M
CST
M-1
32
N/A
N/A
N/A
64
IP
IP E1
32
384
6144
N/A
N/A
TDM
TD
M
CST
M-1
512
7680
7168
504
IP
IP
CST
M-1
2048
23,040
N/A
N/A
WP1D000
FG201
(FG2c)
IP
FE/
GE
elect
rical
port
12/4
2048
23,040
N/A
1024
WP1D000
GOU03
(GOUe)
IP
GE
optic
al
port
2048
23,040
N/A
1024
WP1D000
POU01
(POUc)
Issue 05 (2014-10-29)

23
NOTE
In Abis over TDM, the EIUb supports a maximum of 384TRXs, the OIUb supports a maximum of 384
TRXs, and the POUc supports a maximum of 512 TRXs when all of the following conditions are met:
l The EIUb/OIUb/POUc is configured to work in active/standby mode. If these boards work in
independent mode, the number of TRXs supported is halved. For details, see the REDparameter in
theADD BRD command.
l Traffic model: The traffic volume is 5.86 Erlangs per TRX; three PDCHs are configured on each TRX
on average and the MCS-7 is used, or two PDCHs are configured on each TRX on average and the
MCS-9 is used.
l In fixed Abis networking, idle timeslots and monitoring timeslots are properly configured. Otherwise,
the number of TRXs supported by the EIUb/OIUb/POUc cannot reach the maximum specification.
l After the VAMOS feature is enabled, extra Abis bandwidth is required, which also affects the TRX
specifications of interface boards in GBSS17.0. GBSS16.0
The configuration principles of interface boards are as follows:

The total number of required interface boards is equal to the number of interface boards required
by each interface. Interface boards work in active/standby mode. In BM/TC separated mode, A
and Ater interface boards must be configured on the TC side, and Ater, Gb, and Abis interface
boards must be configured on the BM side. In other networking modes, A, Gb, and Abis interface
boards must be configured on the BM side.
1.
Number of interface boards required by the Abis interface

Select the types of interface board based on the network plan. The number of required Abis
interface boards can be calculated based on either of the service capability (number of TRXs
supported) or number of required ports. Use the larger value of the two values to determine
the number of required Abis interface boards.
The following table describes the network requirements during the configuration of Abis
interface boards.
Item
Sub_Item
Description
Remarks
AbisTRXNum
ber
TRXNoTDME
1
Number of TRXs in Abis over

TDM over E1 mode
TRXNoIPE1
Number of TRXs in Abis over IP

over E1 mode
Determined
based on the
network plan
TRXNoTDMS
TM1
Number of TRXs in Abis over

TDM over STM-1 mode
TRXNoIPSTM
1
Number of TRXs in Abis over IP

over STM-1 mode
AbisTDME1N
o
Maximum number of TDMbased E1 ports required by a BSC

on the Abis interface
AbisIPE1No
Maximum number of IP-based

E1 ports required by a BSC on the
Abis interface
AbisPortNum
ber
Issue 05 (2014-10-29)

Calculated
based on the
traffic model
24
Item
Sub_Item
Description
AbisTDMSTM
1No
Maximum number of TDMbased STM-1 ports required by a

BSC on the Abis interface (one
STM-1 is equivalent to 63 E1s)
AbisIPSTM1N
o
Maximum number of IP-based

STM-1 ports required by a BSC
on the Abis interface (one STM-1
is equivalent to 63 E1s)
Remarks
To determine the number of Abis interface boards, you can use the following formula:
Number of Abis interface boards = 2 x Roundup (MAX(Number of TRXs in the current
transmission mode/Number of TRXs supported by the interface board, Number of ports in
the current transmission mode/Number of ports supported by the interface board), 0)
NOTE
l The number of Abis interface boards to be configured is determined by the number of TRXs and
the number of ports. If a base station uses TDM transmission over the Abis interface, the base
station requires one E1 port by default.
l If monitoring timeslots are requied by a base station for transmission optimization but the BSC
is not configured with any TDM over E1 interface boards, you must configure two pairs of EIUb
or EIUa boards.
If Abis over TDM is used, either of the following conditions must be met:
l Active/standby mode: Number of TRXs supported by the TDM interface board x
(Average traffic volume per TRX + Average number of PDCHs per TRX x Number of
timeslots required for PS transmission) 7680
l Independent mode: Number of TRXs supported by the TDM interface board x (Average
traffic volume per TRX + Average number of PDCHs per TRX x Number of timeslots
required for PS transmission) 4096
The following table lists the number of timeslots required for PS transmission.
Issue 05 (2014-10-29)
Number of Timeslots Required for PS

Transmission
Value
CS-1
CS-2
CS-3
CS-4
MCS-1
MCS-2
MCS-3
MCS-4
2
25
Number of Timeslots Required for PS

Transmission
Value
MCS-5
MCS-6
MCS-7
MCS-8
MCS-9
For example:
l Assume that the POUc supports 512 TRXs, the average traffic volume per TRX is 5.86,
the average number of PDCHs per TRX is 3, and the number of timeslots required for
PS transmission is 3 when MCS-7 is used. Then, the calculation result is 7608, which
is less than 7680.
l Assume that the POUc supports 512 TRXs, the average traffic volume per TRX is 5.86,
the average number of PDCHs per TRX is 4, and the number of timeslots required for
PS transmission is 4 when MCS-9 is used. Then, the calculation result is 11192, which
is greater than 7680. Therefore, the number of TRXs supported by the POUc must be
reduced to 351.
2.
Number of interface boards required by the A interface

Select the types of interface board based on the network plan. The number of required A
interface boards can be calculated based on the service capability (number of CICs
supported).
The following table describes the network requirements during the configuration of A
interface boards.
Item
Sub_Item
Description
Remarks
ACICNumber
MaxACICPe
rBSCTDM
Maximum number of CICs

required by a BSC on the A
interface (TDM transmission)
Calculated based on
the traffic model
MaxACICPe
rBSCIP

required by a BSC on the A
interface (IP transmission)
To determine the number of A interface boards, you can use the following formula:
Number of A interface boards = 2 x Roundup (ACICNumber/Number of CICs supported
by an A interface board, 0
NOTE
If the A interface supports multiple transmission modes, you must calculate the number of interface
boards of each type.
Issue 05 (2014-10-29)

26
3.
Number of interface boards required by the Ater interface

Select the types of interface board based on the network plan. The number of required Ater
interface boards can be calculated based on the service capability (number of CICs
supported).
The following table describes the network requirements during the configuration of Ater
interface boards.
Item
Sub_Item
Description
Remarks
AterCICNum
ber
MaxAterCICPe
rBSC

required by a BSC on the
Ater interface
Calculated based on
the traffic model
To determine the number of Ater interface boards, you can use the following formula:
Number of Ater interface boards = 2 x Roundup (AterCICNumber/Number of CIC circuits
supported by an Ater interface board, 0)
NOTE
If the Ater interface supports multiple transmission modes, you must calculate the number of interface
4.
Number of interface boards required by the Gb interface
Select the types of interface board based on the network plan. The number of required Gb
interface boards can be calculated based on the service capability (bandwidth supported).
The following table describes the network requirements during the configuration of Gb interface
boards.
Item
Sub_Item
Description
Remarks
GbThroughput
GbFRTputPerBSC
Overall traffic volume of a

BSC on the Gb interface in
FR transmission mode
Calculated based on
the traffic model
GbIPTputPerBSC
Overall traffic volume of a

BSC on the Gb interface in
IP transmission mode
To determine the number of Gb interface boards, you can use the following formula:
Number of Gb interface boards = 2 x Roundup (Gb throughput/Bandwidth supported by a Gb
interface board, 0)
NOTE
If the Gb interface supports multiple transmission modes, you must configure the number of interface
Issue 05 (2014-10-29)

27
4.1.4 Clock Boards

Table 4-5 Clock boards
Model
Abbreviatio
n
Name
Function
WP1D000GCU02
GCUb
General Clock Unit
Provides general
clock signals
QW1D000GCG02
GCGb
GPS&Clock Processing Unit
Provides GPS clock

signals (including
the antenna system)
By default, both GCUb and GCGb are delivered.

The GCUb is optional. When a BSC6900 GSM does not use GPS clock signals, a pair of GCUb
boards can be configured for the BSC6900 GSM.
The GCGb is optional. When a BSC6900 GSM needs to use GPS clock signals, a pair of GCGb
boards can be configured for the BSC6900 GSM.
4.1.5 General Principles for Board Configuration

Service processing units, such as XPUs and DPUs, of a BSC6900 GSM work in resource pool
mode. Services (CS user plane, PS user plane, and signaling plane) of TRXs connected to
interface boards in a subrack are preferentially processed by service processing units in the same
subrack. If the resources required by a subrack exceed the specified threshold, load sharing is
implemented between subracks of the BSC. The purpose is to reduce resources used for intersubrack switching. The clock boards, switching boards, OMU, and SAU board are configured
in fixed slots. Other boards are configured according to the following principles:
l
Interface boards and service processing units should be distributed as evenly as possible
among subracks. This reduces the consumption of processor resources and switching
resources by inter-subrack switching. Interface boards can be configured only in rear slots,
and service processing units can be configured in front or rear slots. It is recommended that
service processing units be configured in front slots.
Under a BSC, A interface boards, Ater interface boards, Abis interface boards, XPU, DPUf,
and DPUg must be distributed as evenly as possible among subracks. Configuring the same
type of board in the same subrack lowers system reliability.
If POUc boards are used as A interface boards, DPUf should be configured in proportion
to the number of POUc boards in the same subrack. In full configuration, the ratio of the
number of POUc boards to the number of DPUf should be 1:4 in the same subrack, and the
maximum ratio should be 1:2. If traffic volume is light, a pair of POUc boards and one
DPUf must be configured in a subrack.
No.7 signaling links must be configured on different A and Ater interface boards. This
reduces the impact of transmission faults and board faults on the system.
If there are multiple pairs of No.7 signaling links, distribute them evenly among interface
boards based on the quantities of A and Ater interface boards. In principle, the bandwidth
of the signaling links carried on a pair of single-core interface boards cannot exceed 2 Mbit/
Issue 05 (2014-10-29)

28
s, and the bandwidth of the signaling links carried on a pair of multi-core interface boards
cannot exceed 8 Mbit/s.
For stability purposes, at least two No.7 signaling links must be configured.
l
The number of XPU boards used for signaling processing cannot exceed 20 pairs. The
number of XPUI boards used for implementing the IBCA function cannot exceed eight.
It is recommended that one MPU be configured for each two pairs of XPU.
General principles of network planning:

The basic principles for network planning and design do not vary with devices. The basic
principles include but are not limited to the following:
Each location area (LA) can receive more than 120 paging requests per second over the
Um interface when a single CCCH is used for paging. Therefore, it is recommended
512 TRXs be configured for each LA in the case of a single CCCH. The TRX number
can be reduced with the increase in traffic volume.
Consecutive PDCHs are configured so that MSs can use multiple consecutive timeslots.
Other basic principles during GSM network planning.
1.
General principles of board configuration:

l The TNUb boards are always installed in slots 4 and 5. The SCUb boards are always
installed in slots 6 and 7. The GCUb/GCGb boards are always installed in slots 12 and
13.
l The DPUe/DPUf/DPUg/NIUa boards can be installed in front or rear slots. It is
recommended that they be installed in front slots.
l The EIUb/PEUc/AEUa/OIUb/AOUc/UOIc/POUc/FG2c/GOUe boards are interface
boards. They can be installed only in rear slots.
2.
The OMUc board is always configured in slots 24 and 25 of the MPS.
3.
The clock processing boards are always configured in slots 12 and 13 of the MPS.
4.
The SCUb boards are always configured in slots 6 and 7 of the MPS and EPS.
5.
The SAUc board is always configured in the MPS. A maximum of one SAUc board should
be configured for a BSC6900 GSM, and a maximum of one to two SAUc boards should
be configured for a BSC6900 GU. SAU board redundancy is not required. Each SAUc
board requires one slot. If no SAUc board is configured, one slot in the MPS of a BSC6900
GSM should be reserved for SAU, and two slots in the MPS of a BSC6900 GU should be
reserved for SAUs.
NOTE
MPU is a logical unit of XPU board. The MPU implements board management and transfer internal
messages to other boards.
4.1.6 Subracks
Table 4-6 BSC6900 subracks
Issue 05 (2014-10-29)
Model
Abbreviation
Name
QM1P00UMPS01
MPS
Main Processing Subrack
QM1P00UEPS01
EPS
Extended Processing Subrack

29
Model
Abbreviation
Name
WP1D000TNU01
TNUb
TDM Switching Unit
WP1X000OMU02
OMUc
Operation and Maintenance Unit
WP1D000SAU01
SAUc
Service Aware Unit
WP1D000SCU01
SCUb
GE Switching Network and Control

Unit
By default, the following boards are delivered: TNUb, OMUc, SAUc, and SCUb.
l
Configuration principles for the MPS
One MPS must be configured in a BSC6900 GSM. If IP transmission is used on all interfaces
of a BSC6900 GSM, a pair of TNUb boards is not required. If an interface of the BSC6900 GSM
does not use IP transmission, a pair of TNUb boards needs to be configured in the MPS. For a
BSC6900 GSM or a BSC6900 GU in BM/TC separated mode, the MPS must work in GSM
mode.
l
Configuration principles for the EPS
A maximum of three EPSs can be configured in a BSC6900 GSM. If an interface of the BSC6900
GSM does not use IP transmission, a pair of TNUb boards needs to be configured in each EPS.
Adhere to the following principles when configuring EPSs for a BSC6900 GSM:
l
All interface boards must be configured in the rear slots of an EPS. Service processing units
can be configured in either the front or rear slots of an EPS.
10 rear slots of the GSM MPS are used to house GSM service processing units and interface
boards, and 8 front slots are used to house GSM service processing units.
14 rear slots of a GSM EPS are used to house GSM service processing units and interface
boards, and 10 front slots are used to house GSM service processing units.
The number of GSM subracks cannot exceed 4.
The number of EPSs is calculated based on the number of service processing units and the
number of interface boards.
Number of GSM_EPSs = MAX((Total number of interface boards Number of slots for
interface boards in MPS)/14, (Total number of interface boards + Total number of service
processing boards Total number of slots in MPS)/24)
The number of slots for interface boards in the MPS is 10, and the total number of slots in the
MPS is 18. If no TNUb board is configured, the total number of slots in the MPS is 20. The
number of slots for interface boards in an EPS is 14, and the total number of slots in the EPS is
24. If no TNUb board is configured, the total number of slots in an EPS is 26.
Maximum number of TNUb = 2 x (Number of GSM_EPSs + 1)
When the BSC uses all-IP transmission, a pair of TNUb boards is not required, and therefore
two additional slots in each subrack can be used for service processing boards.
Issue 05 (2014-10-29)

30
4.1.7 Cabinets
Table 4-7 Cabinets
Model
Name
Function
WP1B4PBCBN00
BSC6900 Cabinet
Cabinet
A maximum of two cabinets and four subracks can be configured for a BSC6900 GSM.
Number of cabinets = Roundup ((Number of MPSs + Number of EPSs)/3)
where, Number of MPSs = 1.
Calcualtion of cabinet power consumption:
The maximum power consumption of BSC6900 MPS and EPS is 1400 W, and that of TCS is
1000 W; the maximum power consumption of a single cabinet is 5100 W.
The calculation formula:
BSC_Power_Consumption_Tool.xls
NOTE
l Average power consumption (Pavg) is the estimated value in a typical operating environment. The
maximum power consumption mentioned in hardware description is obtained when all devices on
boards are full-loaded. This maximum power consumption cannot be obtained under the actual system
running conditions. Therefore, Pavg is provided for power consumption calculation.
l The maximum power consumption for a single subrack is 1700 W (including the power consumption
of fans) which is obtained when all slots of the subrack are configured with boards. It is recommended
that power distribution be configured as 1700 W per subrack. This can save power distribution
adjustment upon future capacity expansion.
4.1.8 Auxiliary Materials

Table 4-8 lists the auxiliary materials for installing a BSC6900 GSM.
Table 4-8 Auxiliary materials
Issue 05 (2014-10-29)
Model
Name
Function
QW1P8D442000
Trunk Cable
75-ohm trunk cable
QW1P8D442003
Trunk Cable
120-ohm trunk cable
QW1P0STMOM00
STM-1 Optical Connector
STM-1 optical unit
QW1P00GEOM00
GE Optical Connector
GE optical unit
QW1P0FIBER00
Optical Fiber
Optical cable
QW1P0000IM00
Installation Material
Package
Installation material suite

31
Model
Name
Function
QMAI00EDOC00
Documentation
Electronic documentation
Configuration principles for 75-ohm trunk cables (QW1P8D442000):

The 75-ohm trunk cables must be in full configuration for a board.
Number of trunk cables = [Number of TDM interface units (32 E1s) + Number of IP
interface units (32 E1s)] x 2
NOTE
One trunk cable provides eight E1s. 32 E1s/8 E1s = 4. A trunk cable is a Y-shaped cable, which is
connected to both the active and standby boards.

The 120-ohm trunk cables must be in full configuration for a board.
Number of trunk cables = [Number of TDM interface units (32 E1s) + Number of IP
interface units (32 E1s)] x 2
NOTE
One trunk cable provides eight E1s. 32 E1s/8 E1s = 4. A trunk cable is a Y-shaped cable, which is
connected to both the active and standby boards.
Configuration principle for STM-1 optical units (QW1P0STMOM00)

The STM-1 optical units are fully configured for active and standby optical interface boards.
Number of STM-1 optical units = Number of OIUa boards + Number of POUc boards x 4
Configuration principle for GE optical unit (QW1P00GEOM00):

The GE optical units are fully configured for active and standby optical interface boards.
Number of GE optical units = Number of WP1D000GOU01s or WP1D000GOU03s x 4
Configuration principle for optical cables (QW1P0FIBER00):

The optical cables are configured based on the number of active and standby interface
boards and the number of optical ports required in the BSC6900.
Number of optical cables = (Number of STM optical ports + Number of GE optical ports)
+1
Configuration principle for installation material suite (QW1P0000IM00):

One installation material suite (QW1P0000IM00) is configured for each BSC6900 cabinet
(WP1B4PBCBN00).
Configuration principle for electronic documentation (QMAI00EDOC00):

A set of electronic documentation (QMAI00EDOC00) is delivered with each BSC6900.
4.1.9 Example of Typical BSC6900 GSM Configuration

The following figure illustrates the typical procedure for configuring a BSC6900 GSM.
Issue 05 (2014-10-29)

32
Step 1 Input requirements.

The operator provides the network requirements which should include the information contained
in the following figure.
An example is given here. The following table lists input information.
Issue 05 (2014-10-29)
Network Parameter
Value
TRX QTY
1024
HR Ratio
50%
A Erl: Um Erl
80%
Gos in Um interface
0.02
Gos in A interface
0.001
GPRS Active Sub
100,000
Static PDCH per Cell
Dynamic PDCH per Cell
Built-in PCU
Yes
33
Network Parameter
Value
BM/TC model (Separated or Combined)
Separated
Whether to support GPS in BSC
No
Whether to support TC Pool (if TC Pool is required, input the

number of required CIC circuits)
No
Step 2 Perform the measurements.

The following figure shows the dimensions that are used for calculating the configurations
Item
Name
Specification
TRX support capability
A1
Abis E1 quantity
A2
A CIC quantity
A3
IWF quantity
A4
BHCA
A5
Gb throughput
A6
Step 3 Obtain the network capacity requirements to calculate the hardware requirements.
Issue 05 (2014-10-29)
Item
Name
Configuration Before
Capacity Expansion
Subracks (MPS, EPS)
B1
Data Processing Units (DPUf)
B2
Data Processing Units (DPUg)
B3

34
Item
Name
Configuration Before
Capacity Expansion
Extended Processing Units (XPUc)
B4
Interface boards
B5
Cabinets
B6
----End
4.1.10 BSC6900 GSM Recommended Capacity for Delivery

For the sake of network security, the actual capacity of a configured BSC6900 is much lower
than the specified maximum capacity.
It is recommended that each BSC6900 GSM be configured with less than 3072 TRXs.
To ensure reliability of a large-scale network, the GBFD-113725 BSC Node Redundancy feature
must be configured when the number of GSM TRXs ranges from 3072 to 6144.
4.2 BSC6900 UMTS Product Configurations

A BSC6900 UMTS consists of hardware and hardware capacity licenses.
The main hardware components of the BSC6900 UMTS are service processing units, interface
boards, clock boards, subracks, and cabinets. The following sections describe the hardware
configuration scenarios and configuration methods.
The hardware includes cabinets, subracks, data processing units, signaling processing units,
network intelligence units, interface boards, and clock boards. The hardware capacity licenses
includes the Hardware Capacity License (165 Mbit/s), Gardware Capacity License (300 Mbit/
s), and Network Intelligence Throughput License.
Issue 05 (2014-10-29)

35
All the product specifications can be reached when the CPU load of the hardware is 70%.
The SPUb, GOUc, GCUa, and GCGb boards can be replaced with the SPUc, GOUe, GCUb,
and GCGb boards, respectively. The specifications of the old and new boards are the same, and
therefore the configurations of an old board also apply to the corresponding new board.
NOTICE
Note that if two boards work in active/standby mode, the two boards must be identical. To replace
a single-core board in a slot with a multi-core board, you must first remove the single-core board
from the slot and then insert the multi-core board into the slot.
4.2.1 Impact of Traffic Model on Configurations

The capacity of UMTS BSC6900 depends on the number of SPUc and DPUe boards and the
actual processing capacity in the traffic model. A UMTS BSC6900 can be configured with a
maximum of 50 pairs of SPUc boards and 50 pairs of DPUe boards. However because the number
of slots is limited, you cannot simultaneously configure the maximum board quantities of SPUb/
SPUc and DPUe.
Under Huawei smartphone traffic model, the maximum BHCA throughput reaches 12.8 Mbit/
s on the control plane. Under Huawei heavy PS traffic model, the maximum BHCA throughput
reaches 40 Gbit/s on the user plane. However, the control and user planes cannot simultaneously
reach their maximum throughput.
The maximum traffic volumes on the control and user planes are closely related to the traffic
model. Therefore, technical specifications of the BSC6900 are subject to the traffic model.
l
On the user plane

The CPU overload threshold of the BSC6900 is 70%.
The promoted capability of the DPUe (for the user plane) is calculated based on the PS
RAB uplink/downlink (UL/DL) rate (64/384 kbit/s), which is the average rate of PS services
and is independent from specific bearer type (R99 or HSPA). Under this circumstance, the
PS throughput of DPUe is 800 Mbit/s, which is the maximum design specification.
In practice, due to rapid development of smartphones, the user plane of the network features
a large number of small packet interactions. On the live network, the actual PS throughput
of the DPUe depends on the mean data rate of UEs in the CELL_DCH or CELL_FACH
state (PS RAB mean data rate in active state). When the mean data rate of UEs in the
CELL_DCH or CELL_FACH state is low, the PS throughput of the DPUe is low. The
following figure shows the relationship between the PS throughput of the DPUe and the
mean data rate of UEs in the CELL_DCH or CELL_FACH state.
Issue 05 (2014-10-29)

36
PS RAB mean data rate in active state indicates the average data rate of PS services in the
activated states (including the CELL_DCH and CELL_FACH states). It can be calculated
by using the following formula based on the traffic model:
PS RAB mean data rate in active state (UL+DL) = PS throughput per subscriber during
busy hours x 3600/(PS call per subscriber per busy hour x Mean hold time in
Cell_DCH&Cell_FACH per PS call)
Table 4-9 Typical PS RAB mean data rate in active state and the corresponding PS
throughput of the DPUe
PS RAB mean data rate in
active state (UL+DL) (kbit/
s)
16
40
64
128
196
448
PS throughput capacity per

DPUe (Mbit/s)
90
250
300
430
530
800
The actual PS throughput of DPUe is estimated by using the following methods:

If the PS RAB mean data rate in active state (UL+DL) (kbit/s) takes a value in the
interval (0, 16], PS Throughput Capacity per DPUe (Mbit/s) = PS RAB Mean data rate
x 5.625.
interval (16, 40], PS Throughput Capacity per DPUe (Mbit/s) = 90 + (PS RAB Mean
data rate 16) x 6.67.
interval (40, 64], PS Throughput Capacity per DPUe (Mbit/s) = 250 + (PS RAB mean
Issue 05 (2014-10-29)

37
interval (448, ), PS Throughput Capacity per DPUe (Mbit/s) = 800.
l
On the control plane

The CPU overload threshold of the BSC6900 is 70% and base load is 10%. There are 8
CPUs per SPUb/SPUc board.
BHCA supported by an SPUc board = (70% - 10%) x 8/CPU usage consumed by a call
The CPU usage consumed by a single call is associated with the traffic model. When the
traffic model is changed, the available CPU usage of one SPUc board remains unchanged,
but the CPU usage consumed by a single call changes. Therefore, the BHCA supported by
an SPUc board varies according to the traffic model.
The traffic model on a live network changes with time and UE behavior. Therefore, the
system may be congested because of limited control plane processing resources, even when
the traffic in the network does not reach the claimed capacity (Erl or throughput). When
the traffic model changes, recalculate the control-plane processing resources required by
the network. Then, add required processing modules and interface boards.
4.2.2 Hardware Capacity License

The BSC6900 V900R016 supports the Hardware Capacity license (165 Mbit/s), Hardware
Capacity license (300 Mbit/s), and Network Intelligence Throughput license.
The hardware capacity license (165 Mbit/s) and hardware capacity license (300 Mbit/s) are
superposed on the hardware capacity of the DPUe hardware (335 Mbit/s) to increase the userplane processing capabilities.
The Network Intelligence Throughput license is superposed on the hardware capacity of the
NIUa board (50 Mbit/s) to provide service awareness when any of the following features is
enabled: WRFD-020132 Web Browsing Acceleration, WRFD-020133 P2P Downloading Rate
Control during Busy Hour, WRFD-150252 Video Service Rate Adaption, WRFD-150253 VoIP
Application Management, and WRFD-150254 Differentiated Service Based on Application
Resource Reservation.
The following describes the application scenarios and configuration principles of these hardware
capacity licenses.
l
Hardware Capacity License (165 Mbit/s)

The hardware capacity license (165 Mbit/s) is applicable to HW69 R11, HW69 R13, HW69
R15, HW69 R16 hardware.
The hardware capacity license (165 Mbit/s) can be configured only for a data processing
unit DPUe (WP1D000DPU03). It increases the PS throughput of DPUe in the BSC6900
UMTS without requiring hardware replacement (it cannot increase the CS voice capacity).
The increased processing capability is an integral multiple of 165 Mbit/s. The maximum
increase in the processing capability depends on the number of configured DPUe boards.
l
Issue 05 (2014-10-29)
Hardware Capacity License (300 Mbit/s)

38
The hardware capacity license (300 Mbit/s) is applicable to the HW69 R11, HW69 R13,
HW69 R15, HW69 R16 hardware.
The hardware capacity license (300 Mbit/s) can be configured only for a data processing
unit DPUe (WP1D000DPU03). It increases the PS throughput of DPUe in the BSC6900
UMTS without requiring hardware replacement (it cannot increase the CS voice capacity).
The increased processing capability is an integral multiple of 300 Mbit/s. The maximum
increase in the processing capability depends on the number of configured DPUe boards
and the number of configured hardware capacity licenses (300 Mbit/s).
NOTICE
l When the number of configured hardware capacity licenses is smaller than the number
of configured DPUe boards, hardware capacity licenses can be shared among the DPUe
boards of a single BSC6900 UMTS to form a resource pool and improve resource usage
efficiency. Each DPUe supports a maximum PS throughput of 800 Mbit/s.
l Hardware capacity licenses are not automatically moved with hardware. For example,
when a DPUe is moved from one BSC6900 UMTS to another, its hardware capacity
licenses are not moved.
Assume that two DPUe boards are configured. Table 4-10 lists the comparison results of
the PS throughput before and after hardware capacity licenses are configured.
Table 4-10 Comparison of PS throughput before and after hardware capacity licenses are
configured
Number of
Configured
WP1D000DPU03s
(DPUe)
Number of
Configure
d
Hardware
Capacity
Licenses
(165 Mbit/
s)
User Plane
Processing
Capability
(Mbit/s/
Erlang)
Number of
Configured
Hardware
Capacity
Licenses (300
Mbit/s)
User Plane
Processing
Capability
(Mbit/s/
Erlang)
670/6700
670/6700
835/6700
835/6700
1135/6700
1000/6700
1300/6700
1600/6700
Issue 05 (2014-10-29)
1000/6700

39

NOTE
User plane processing capability (Mbit/s/Erlang): indicates the maximum processing capability of
DPUe boards that process either CS services or PS services. Take two DPUe boards for example.
When the user plane processing capability is 670/6700 (Mbit/s/Erlang):
If the two DPUe boards process only PS services, the processing capability of the DPUe boards is
670 Mbit/s.
If the two DPUe boards process only CS services, the processing capability of the DPUe boards is
6700 Erlang.
If the two DPUe boards process both PS services and CS services, the two DPUe boards can meet
the user plane capacity requirements when the following condition is fulfilled:
CS traffic volume/6700 Erlang + PS throughput/670 Mbit/s 1
Two hardware capacity licenses (165 Mbit/s) and two hardware capacity licenses (300
Mbit/s) must be added to meet the user plane capacity requirements if the following
condition is fulfilled:
CS traffic volume in the network/6700 Erlang + PS throughput in the network/1600 Mbit/
s1
Minimum hardware should be configured in a BSC6900 on the precondition that the
network capacity requirements are met. Therefore, hardware capacity licenses are
preferentially configured before more hardware is added.
NOTE
With the development of mainstream smartphone networks, there are a large number of small packets
transferred on the user plane. The actual PS throughput of the DPUe may be less than 335Mbit/s
supported by DPUe itself. In this case, the Hardware Capacity License (165Mbps) and Hardware
Capacity License (300Mbps) do not take effect and should not be configured. Therefore, whether to
configure these two hardware capacity licenses depends on the traffic model. You need to evaluate
the actual PS throughput of DPUe and then determine whether to configure these two hardware
capacity licenses.
Network Intelligence Throughput License

The network intelligence throughput license is applicable to the HW69 R13, HW69 R15,
HW69 R16 hardware.
This license can be configured for a network intelligence unit NIUa(WP1D000NIU00) to
increase the service awareness processing capability. A maximum of 63 network
intelligence throughput licenses can be configured for one NIUa. Network intelligence
throughput licenses can be shared among the NIUa boards of a single BSC6900 UMTS.
That is, network intelligence throughput licenses form a resource pool and are not bound
to specific boards. Each NIUa provides a maximum PS throughput of 3200 Mbit/s. Network
intelligence throughput licenses are not automatically moved with hardware. For example,
when a NIUa is moved from one BSC6900 UMTS to another, its network intelligence
throughput licenses are not moved.
4.2.3 Service Processing Units

Service processing units consist of control-plane processing units and user-plane processing
units. Control-plane processing units consist of SPUc boards. User-plane processing units
consist of the DPUe, NIUa, and the following hardware licenses: Hardware Capacity License
(165Mbps), Hardware Capacity License (300Mbps), and Network Intelligence Throughput
license.
Issue 05 (2014-10-29)

40
Table 4-11 Service processing units

Model
Abbrevia
tion
Name
Function
Specification
Condition
WP1D00
0SPU03
SPUc
Signaling
Processing
Unit
Signaling
processing
124,000 BHCA,
180 NodeBs, 600
cells, 9600 active
users, and 24,000
online users
Mandatory
WP1D00
0DPU03
DPUe
Data
Processing
Unit (335
Mbit/s/
3350
Erlang)
Data
processing
enhancemen
t
PS Throughput
335 Mbit/s
(depending on the
traffic model) or
3350 Erlang, 300
cells, and 5880
active uers
Mandatory
Hardware
Capacity
License
(165 Mbit/
s)
Data
processinge
nhancement
PS throughput:
165 Mbit/s
Optional
QM1SH
W165M0
0
Issue 05 (2014-10-29)

124,000 BHCA
based on the
balanced traffic
model
described in
7.3.1 UMTS
Traffic Model.
The actual
BHCA capacity
must be
calculated
based on the
actual traffic
model.
The PS
throughput of
the DPUe board
depends on the
traffic model.
For
specification
evaluation, see
described in
4.2.1 Impact of
Traffic Model
on
Configuration
s.
Whether to
configure this
hardware
capacity license
depends on the
PS throughput
of the DPUe
board under the
actual traffic
model.
41
Model
Abbrevia
tion
QM1SH
W300M0
0
WP1D00
0NIU00
NIUa
Name
Function
Specification
Condition
Hardware
Capacity
License
(300 Mbit/
s)
Data
processing
enhancemen
t
PS throughput:
300 Mbit/s
Optional
Network
Intelligenc
e Unit
Intelligent
service
awareness
Hardware
capacity: 3200
Mbit/s
Optional. Used
for any of the
following
features:
WRFD-020132
Web Browsing
Acceleration,
WRFD-020133
P2P
Downloading
Rate Control
during Busy
Hour,
WRFD-150252
Video Service
Rate Adaption,
WRFD-150253
VoIP
Application
Management,
and
WRFD-150254
Differentiated
Service Based
on Application
Resource
Reservation
PS throughput
provided by the
NIUa hardware:
50 Mbit/s
QM1SNI
U50M00
Issue 05 (2014-10-29)
Network
Intelligenc
e
Throughpu
t License
Intelligent
service
awareness
PS throughput: 50
Mbit/s

Whether to
configure this
hardware
capacity license
depends on the
PS throughput
of the DPUe
board under the
actual traffic
model.
Optional
Required only
when NIUa
boards are
configured.
42

NOTE
l Active users: specify the users in the CELL_DCH or CELL_FACH state.

l Online users: specify the users in the RRC connection, including CELL_DCH, CELL_FACH,
CELL_PCH, and URA_PCH users.
By default, the following boards are delivered: DPUe, NIUa, and SPUc.
l
Configuration principles of WP1D000SPU03 (SPUc):
configuration of WP1D000SPU03 (SPUc).
Table 4-12 Network requirements for SPUc configuration
Item
Description
Remarks
BHCA requirement
BHCA that need to be supported

in the network

Active users
Number of concurrent active

users that need to be supported
by the BSC6900 UMTS control
plane

Online users
Number of concurrent online

users that need to be supported
by the BSC6900 UMTS control
plane

NodeB number
Number of NodeBs that need to

be managed by the BSC6900
UMTS

network plan
Cell number
Number of cells that need to be

managed by the BSC6900
UMTS

network plan
1.
In a newly deployed network:

Number of SPUc boards = Roundup (MAX (BHCA required by the target network/BHCA
supported by one SPUc, Number of active users/Number of active users supported by one
SPUc, Number of online users/Number of online users supported by one SPUc, Number
of NodeBs required by the target network/Number of NodeBs supported by one SPUc,
Number of cells in the target network/Number of cells supported by one SPUc))
The BHCA supported by one SPUc depend on the traffic model. If the actual traffic model
of a network differs greatly from the traffic model described in section 7.3.1 UMTS Traffic
Model. BHCA supported by one SPUc must be recalculated based on the actual traffic
model.
2.
In capacity expansion scenarios:

Number of SPUc boards = Number of SPUc boards after capacity expansion Number of
SPUc boards before capacity expansion
Issue 05 (2014-10-29)

43
Before capacity expansion, SPUb and SPUa boards may be used in the BSC6900 UMTS.
Given the same service model, the old and new SPU capability conversion formula is: SPUc
= SPUb = 1.55 SPUa.
Configuration principle for WP1D000DPU03(DPUe) and hardware capacity licenses
configuration of DPUe and hardware capacity licenses.
Table 4-13 Network requirements for DPUe configuration
Item
Description
Remarks
Iub PS throughput
PS throughput required on the

Iub interface

Iub CS traffic
CS Erlang required on the Iub

interface

Active users

users required by the BSC6900
UMTS user plane

Cell number
Number of cells that need to be

managed by the BSC6900
UMTS
Determined based on the network

plan

Assume that the user plane capacity requirements on the Iub interface of a network are
aMbit/s (PS throughput),bErlang (Iub CS traffic volume),c(number of cells), andn (number
of active users). Active users are UEs in the CELL_DCH or CELL_FACH state.
The actual PS throughput of the DPUe board depends on the average user-plane data rate
of PS services in the CELL_DCH and CELL_FACH states:
- If the PS RAB mean data rate in active state (UL+DL) (kbit/s) takes a value in the interval
[0, 16], PS Throughput Capacity per DPUe (Mbit/s) = PS RAB mean data rate x 5.625.
[16, 40], PS Throughput Capacity per DPUe (Mbit/s) = 90 + (PS RAB Mean data rate
16) x 6.67.
40) x 2.08.
64) x 2.03.
128) x 1.47.
128) x 1.07.
Issue 05 (2014-10-29)

44
[448, ], PS Throughput Capacity per DPUe (Mbit/s) = 800.
The number of DPUe boards required in the network, represented by N_DPUe, can be
calculated using the following formula:
N_DPUe = Roundup (MAX (a/Actual PS throughput of DPUe + b/3350, c/300, n/5880,
2)) + 1
NOTE
l A minimum of two DPUe boards can be configured. A maximum of 50 DPUe boards can be
configured.
l It is recommended that DPUe boards be configured in N+1 redundancy mode.
The number of DPUe boards required by PS services in the network, represented by

N_DPUe_PS, can be calculated using the following formula:
N_ DPUe _PS = Roundup (a/Actual PS throughput of DPUe)
If N_DPUe_PS x 335 a, no hardware capacity license needs to be configured.
Otherwise, hardware capacity licenses need to be configured. The number is calculated
using the following formula:
Number of required hardware capacity licenses (165 Mbit/s) (represented by N_165) = Min
(N_DPUe, Roundup ((a N_DPUe_PS x 335)/165))
If N_165 x 165 + N_DPUe_PS x 335 a, no hardware capacity license (300 Mbit/s) needs
to be configured. Otherwise, hardware capacity licenses need to be configured. The number
is calculated using the following formula:
Number of required hardware capacity licenses (300 Mbit/s) (represented by N_300) = Min
(N_165, Roundup ((a N_DPUe_PS x 335 N_165 x 165)/300))
N_ DPUe _PS = Roundup ( a/DPUe PS throughput actual processing capacity x (1 + 10%))
If the KQI-related features are required on the PRS side, the DPUe board configuration is
also affected. If the KQI-related features are enabled, additional DPUe boards need to be
configured. The number of additional DPUe boards is equal to 5% multiplied by the KQI
deployment rate. For example, if the KQI deployment rate is 30%, KQI evaluation will be
performed on 30% of all PS services on the entire network. This does not affect the DPUe
hardware license.
N_ DPUe _PS_KQI = a x Ratio_KQI x 5%/Actual PS throughput of DPUe
where, Ratio_KQI = KQI deployment rate
The total number of DPUe boards used for processing PS services can be calculated using
the following formula:
N_ DPUe _PS = Roundup (a/Actual PS throughput of DPU + N_ DPUe _PS_KQI)
l

Calculate the number of required DPUe boards, hardware capacity licenses (165 Mbit/s),
and hardware capacity licenses (300 Mbit/s) by referring to the calculation procedure
provided previously for a newly deployed network.
Number of DPUe boards = Number of DPUe boards after capacity expansion Number
of DPUe boards before capacity expansion
Number of hardware capacity licenses (165 Mbit/s) = Number of hardware capacity
licenses (165 Mbit/s) after capacity expansion Number of hardware capacity licenses
(165 Mbit/s) before capacity expansion
Issue 05 (2014-10-29)

45
Number of hardware capacity licenses (300 Mbit/s) = Number of hardware capacity

licenses (300 Mbit/s) after capacity expansion Number of hardware capacity licenses
(300 Mbit/s) before capacity expansion
NOTE
A minimum of two DPUe boards can be configured. A maximum of 50 DPUe boards can be
configured.
Configuration principles of WP1D000NIU00(NIUa) and QM1SNIU50M00(Network

intelligence throughput license):
This board is optional. It needs to be configured only when related optional features are required.
If the service awareness features (WRFD-020132 Web Browsing Acceleration, WRFD-020133
P2P Downloading Rate Control during Busy Hour, WRFD-150252 Video Service Rate
Adaption, WRFD-150253 VoIP Application Management, and WRFD-150254 Differentiated
Service Based on Application Resource Reservation) are required, an NIUa must be configured.
Assume that the Iub PS throughput is a Mbit/s.
Number of required NIUa boards (represented by N_NIUa) = Roundup (a/3200, 0)
Each NIUa provides 50 Mbit/s PS throughput. If the value a is larger than 50,
N_QM1SNIU50M00 = Roundup ((a N_NIUa x 50)/50, 0).
Otherwise, N_QM1SNIU50M00 is 0.
If the KQI-related features are required on the PRS side, the NIUa configuration is also affected.
If KQI evaluation needs to be performed for PS services on the entire network, the NIUa board
and hardware license quantities are calculated using the following formulas:
N_ NIUa_KQI = Roundup (a x Ratio_KQI/PS throughput of the NIUa)
PS throughput of the NIUa = 4 x PS throughput of the DPUe
Network Intelligence Throughput License = Roundup ((a x Ratio_KQI - 50)/50)
where
Ratio_KQI = KQI deployment rate
If both service awareness features and KQI-related features are enabled, the number of NIUa
boards and the number of Network Intelligence Throughput Licenses are the larger one under
the two conditions.
4.2.4 Interface Boards

The BSC6900 UMTS provides various interfaces to meet the requirements of different network
structures.
The interface board specifications include traffic volume, number of subscribers, number of
NodeBs, and number of session setups/releases. Table 4-14 lists the specifications of each
interface board on different interfaces (Iub, Iur, Iu-CS, and Iu-PS).
Issue 05 (2014-10-29)

46
Table 4-14 Interface boards required by the BSC6900 UMTS

Model
Abbre
viatio
n
Name
Where
to
Apply
Session
Setup/
Release
Times
CID/
UDP
(IUB
Active
Users)
WP1D000AEU00
AEUa
ATM Interface Unit

(32 E1)
Iub
500
23,000
WP1D000PEU00
PEUc
IP Interface Unit
(32 E1)
Iub
500
23,000
WP1D000AOU01
AOUc
ATM Interface Unit

(4 STM-1,
Channelized)
Iub
5000
79,000
WP1D000POU01
POUc
IP Interface Unit (4
STM-1,
Channelized)
Iub
5000
129,000
WP1D000UOI01
UOIc
ATM Interface Unit

(8 STM-1,
Unchannelized)
Iub/IuCS//IuPS/Iur
5000
79,000
WP1D000GOU03
GOUe
IP Interface Unit (4
GE, Optical)
Iub/IuCS//IuPS/Iur/
Iurpnote
5000
129,000
WP1D000FG201
FG2c
IP Interface Unit
(12 FE/4 GE,
Electrical)
Iub/IuCS//IuPS/Iur/
Iurpnote
5000
129,000
By default, the following boards are delivered: AEUa, PEUc, AOUc, POUc, UOIc, GOUe, and
FG2c.
NOTE
The Iur-p is a Huawei-prioportary interface between RNCs to facilitate the RNC in Pool feature in
RAN16.0 .
Table 4-15 Specifications of interface boards on the Iub/Iur interface

Model
Issue 05 (2014-10-29)
Iub/Iur

NodeB
47
Voice
(AMR
&
WBAMR)
VP
(Erlan
g)
UL (Mbit/
s)
DL (Mbit/
s)
UL+DL
(Mbit/s)
WP1D000AEU00
2800
680
45
45
90
32
WP1D000PEU00
2800
850
60
60
120
32
WP1D000AOU01
18,000
5500
300
300
600
500
WP1D000POU01
18,000
6000
400
400
800
252
WP1D000UOI01
18,000
9000
800
800
1200
500
WP1D000GOU03
18,000
9,000
2600
2600
2600
500
WP1D000FG201
18,000
9,000
2600
2600
2600
500
Table 4-16 Specifications of interface boards on the Iu-CS/Iu-PS interface

Iu-CS
Model
Issue 05 (2014-10-29)
Iu-PS
Voice
(Erlang)
(AMR
& WBAMR)
VP
(Erlang)
UL
(Mbit/
s)
DL
(Mbit/
s)
UL+DL
(Mbit/s)
IU PS Online
Users(TEID)
WP1D000UOI01
18,000
9000
900
900
1800
200,000
WP1D000GOU03
18,000
9000
3200
3200
3200
200,000
WP1D000FG201
18,000
9000
3200
3200
3200
200,000

48

NOTE
1. One active CS user consumes two Iub CIDs/UDPs, and one active HSPA PS user consumes three Iub
CIDs/UDPs.
2. One active CS user consumes one Iu-CS CID/UDP, and one online PS user consumes one Iu-PS Tunnel
Endpoint ID (TEID).
3. The specifications of interface boards on the Iur interface are the same as those of interface boards on
the Iub interface.
4. The processing capability specifications of each interface board are the maximum specifications when
the interface board processes only the corresponding type of service. The configured specifications are
listed in the NodeB column.
5. VP in the table indicates 64 kbit/s video phone services.
6. AMR indicates traditional 12.2 kbit/s CS services, and WB-AMR indicates WB-AMR CS services
with the typical rate of 23.85 kbit/s.
7. The number of session setups/releases indicates the signaling processing capability of interface boards
and is applicable to the Iub and Iu-PS interfaces.
Table 4-17 lists the mapping between the interface signaling processing requirements and the traffic model.
Table 4-17 Session setups/releases times of signaling procedure of control plane of traffic model
Control Plane Traffic
Parameter
Unit
Iub Session Setup/

Release Times
Iu-PS Session
Setup/Release
Times
CS voice call per subscriber

per BH
times
Handover times per CS

voice call (Inter/Intra RNC
soft and softer handover)
times/call
PS call per subscriber per

BH
times
Handover times per PS call

(Inter/Intra RNC soft and
softer handover)
times/call
PS channel switch per PS

call
times/call
0.5
Cell update per PS call
times/call
0.5
NAS signaling per

subscriber per BH (times)
times/per
subscriber
The following table describes the network requirements during the configuration of interface
boards.
Network requirements for configuration of interface board
Issue 05 (2014-10-29)

49
Interface
Item
Description
Remarks
Iub
Iub transmission
type
Transmission type used on

the Iub interface of the
network
Determined based on
the network plan
Iub PS throughput
PS throughput that needs to

be supported on the Iub
interface
Calculated based on the

number of users and the
traffic model.
Iub CS traffic
CS traffic that needs to be

supported on the Iub
interface
Iub session setup

and release
requirement in BH
Session setup and release

capacity that matches the
network BHCA capacity
Iub active users

(CID/UDP)

users (Iub CID/UDP)that
need to be supported the
BSC6900 UMTS
NodeB number
Number of NodeBs that

need to be managed by the
BSC6900 UMTS
Determined based on
the network plan
Iu-CS transmission
type

the Iu-CS interface of the
network
Determined based on
the network plan
Iu-CS CS traffic
CS traffic volume on the IuCS interface
Iu-CS active users

users that need to be
supported the Iu-CS
interface of the BSC6900
UMTS

traffic model.
Iu-CS session setup

and release
requirement in BH
Number of sessions that

need to be supported on the
Iu-CS interface of the
BSC6900 UMTS
Iu-PS transmission
type

the Iu-PS interface of the
network
Determined based on
the network plan
Iu-PS throughput
PS throughput that needs to

be supported on the Iu-PS
interface

traffic model.
Iu-CS
Iu-PS
Issue 05 (2014-10-29)

50
Interface
Item
Description
Iu-PS online users
Number of concurrent
online users that need to be
supported the Iu-PS
interface of the BSC6900
UMTS
Iu-PS session setup

and release
requirement in BH
Number of sessions that

need to be supported on the
Iu-PS interface of the
BSC6900 UMTS
Remarks
The configuration principles of Iub interface boards are as follows:

1.
The number of interface boards required on the Iub interface can be calculated in the
following way:
The Iub interface can use any of the following transmission modes:
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)
The number of required Iub interface boards can be calculated based on any of the following
aspects: service processing capability (Erlang and payload throughput), port bandwidth,
number of NodeBs, signaling processing capability, and number of concurrent active users.
The required number of Iub interface boards takes the maximum among these values
calculated from the preceding aspects.
Number of Iub interface boards = MAX(Number of Iub interface board_Traffic, Number
of Iub interface board_Bandwidth, Number of Iub interface board_NodeB, Number of Iub
Interface Board_Session setup/release, Number of Iub Interface Board_CIDUDP)
where,
l Number of Iub interface board_Traffic = Iub Voice Traffic/Iub Voice specification +
Iub CS Data Traffic/Iub CS data specification + MAX((Iub PS DL Throughput + MBMS
traffic)/Iub PS DL specification, Iub PS UL Throughput/Iub PS UL specification, (Iub
PS DL Throughput + MBMS traffic+ Iub PS UL Throughput)/Iub PS DL+UL
specification)
l Number of Iub interface board_Bandwidth = (Iub OAM Transmission bandwidth
requirement + MAX(Iub DL Transmission Bandwidth (data) +Iub DL Transmission
Issue 05 (2014-10-29)

51
Bandwidth (signaling) +Iub DL MBMS Transmission Bandwidth, Iub UL Transmission

Bandwidth (data) + Iub UL Transmission Bandwidth (signaling)))/Transmission
Bandwidth per Interface port/Number of ports per interface board
l Number of Iub interface board_NodeB = NodeB number/NodeB Capacity per Interface
Board
l Number of Iub Interface Board_Session setup/release = Iub session setup and release
requirement in BH/capacity of session setup and session release per second of interface
board/3600
l Number of Iub Interface Board_CIDUDP = Iub active users (CID/UDP)/Active users
supported by per interface board(CID/UDP)
In the preceding formulas, the following items are specifications of interface boards (CID/
UDP): Iub Voice specification, Iub CS data specification, Iub PS DL specification, Iub PS
UL specification, Iub PS DL + UL specification, Number of ports per interface board,
NodeB capacity per interface board, capacity of session setup and session release per second
of interface board, and active users supported by per interface board are specifications of
interface boards(CID/UDP). Other items are the results of BSC6900 dimensioning.
2.
The Iur, Iu-CS, and Iu-PS interfaces can use any of the following transmission modes:
Case 1: VC4-STM-1 (ATM);
Case 2: GE Electrical (IP);
Case 3: GE Optical (IP);
he numbers of required Iur, Iu-CS, and Iu-PS interface boards can be calculated based on
any of the following four aspects: service processing capability (Erlang and payload
throughput), port bandwidth, signaling processing capability, and number of concurrent
active users. The required numbers of Iur, IU-CS, and Iu-PS interface boards take the
maximum among the four values calculated from the preceding four aspects.
- For the Iu-CS interface
Number of Iu-CS interface board_Traffic = Iu-CS Voice Traffic/Iu-CS Voice specification
+ Iu-CS Data Traffic/Iu-CS data specification
Number of Iu-CS interface board_Bandwidth = MAX((Iu-CS DL Transmission Bandwidth
(data) + Iu-CS DL Transmission Bandwidth (signaling)), (Iu-CS UL Transmission
Bandwidth (data) + Iu-CS UL Transmission Bandwidth (signaling)))/Transmission
Bandwidth per Interface port/Number of ports per interface board
Number of Iu-CS Interface Board_Session setup/release = Iu-CS session setup and release
requirement in BH/Capacity of session setup and session release per second of interface
board/3600
Number of Iu-CS Interface Board_Active users = Iu-CS active users/Active users supported
by per interface board (CID/UDP)
Number of Iu-CS interface board = MAX (Number of Iu-CS interface board_Traffic,
Number of Iu-CS interface board_Bandwidth, Number of Iu-CS Interface Board_Session
setup/release, Number of Iu-CS Interface Board_Active users)
- For the Iu-PS interface
Number of Iu-PS interface board_Traffic = MAX (Iu-PS DL Throughput/Iu PS DL
specification, Iu-PS UL Throughput/Iu PS UL specification, (Iu-PS DL Throughput + IuPS UL Throughput)/Iu PS DL+UL specification)
Number of Iu-PS interface board_bandwidth = MAX(Iu-PS DL Transmission Bandwidth
(data) + Iu-PS DL Transmission Bandwidth (signaling), Iu-PS UL Transmission Bandwidth
Issue 05 (2014-10-29)

52
(data) + Iu-PS UL Transmission Bandwidth (signaling))/Transmission Bandwidth per

Interface port/Number of ports per interface board
Number of Iu-PS Interface Board_Session setup/release = Iu-PS session setup and release
board/3600
Number of Iu-PS Interface Board_Active users = Iu-PS active users/Active users supported
by per interface board
Number of Iu-PS interface board = MAX(Number of Iu-PS interface board_Traffic,
Number of Iu-PS interface board_bandwidth, Number of Iu-PS Interface Board_Session
setup/release, Number of Iu-PS Interface Board_Active users)
- For the Iur interface
Number of Iur interface board_Traffic = Iur Voice Traffic/Iub CS Voice_specification +
Iur CS Data Traffic/Iub CS data_specification + MAX(Iur PS DL Throughput/Iub PS
DL_specification, Iur PS UL Throughput/Iub PS UL_specification)
Number of Iur interface board_bandwidth = MAX(Iur DL Transmission Bandwidth (data)
+ Iur DL Transmission Bandwidth (signaling), Iur UL Transmission Bandwidth (data) +
Iur UL Transmission Bandwidth (signaling))/Transmission Bandwidth per Interface port/
Number of ports per interface board
Number of Iur Interface Board_Session setup/release = Iur session setup and release
board/3600
Number of Iur Interface Board_Active users = Total Iur active users(CID/UDP)/Active
users supported by per interface board(CID/UDP)
Number of Iur interface boards = MAX(Number of Iur interface board_Traffic, Number
of Iur interface board_bandwidth, Number of Iur Interface Board_Session setup/release,
Number of Iur Interface Board_Active users)
In the preceding formulas, the following items are the specifications for the interface
boards: Iu-CS voice specification, Iu-CS data specification, Iu-PS DL specification, Iu-PS
UL specification, Iu-PS DL + UL specification, Number of ports per interface board,
Transmission bandwidth per interface port, Number of session setups and releases per
second of interface board, and CID/UDP supported by per interface board. Other items are
the results of BSC6900 dimensioning.
3.
RNC interface boards supports the two backup modes:

a.
In 1+1 backup mode, the actual number of interface boards required is twice the
number calculated according to the network capacity requirements.
The number of interface boards is the sum of interface boards required on the Iub, IuCS, Iu-PS, and Iur interfaces: Sum (Iub, Iu-CS, Iu-PS, Iur) x 2
b.
The BSC6900 UMTS supports the N+1 backup mode on only the FG2c, GOUc, and
GOUe boards with resource pools enabled.
If the BSC6900 works in N+1 backup mode and the Iur, Iu-CS, and Iu-PS interfaces
share the same interface board, the number of interface boards can be calculated by
using the following formula:
Roundup (Iub) + 1 + Roundup (Sum(IuCS, IuPS, Iur)) + 1
If the BSC6900 works in N+1 backup mode and the Iur/Iu-CS (Iur and Iu-CS interfaces
share the same interface board) and Iu-PS interfaces use different interface boards,
the number of interface boards can be calculated by using the following formula:
Issue 05 (2014-10-29)

53
Sum(Roundup (Iub) + 1, Roundup (IuCS + Iur) + 1, Roundup (IuPS) +1)

The number of slots required by interface boards is equal to the total number of slots
required by interfaces Iub, IuCS, IuPS and Iur. Based on the number of required slots, the
number of required subracks can be calculated.
NOTICE
If the RNC in Pool function is enabled, Iur-p interface board must be configured in
RAN17.0. RAN16.0
4.2.5 Clock Boards

Table 4-18 Clock boards
Model
Abbreviatio
n
Name
Function
WP1D000GCU02
GCUb
General Clock Unit
Provides general clock

signals.
QW1D000GCG02
GCGb
GPS&Clock Processing
Unit
Provides GPS clock

signals (including the
antenna system).
By default, GCUb and GCGb are delivered.

The GCUb is optional. When a BSC6900 UMTS does not use GPS clock signals, a pair of GCUb
boards can be configured for the BSC6900 UMTS.
The GCGb is optional. When a BSC6900 UMTS needs to use GPS clock signals, a pair of GCGb
boards can be configured for the BSC6900 UMTS.
4.2.6 Principles for Board Configurations

Boards must be configured in slots according to the following principles:
1.
An OMUc board must be configured in slots 24 and 25 of the MPS.
2.
Clock boards (GCUb or GCGb) must be configured in slots 12 and 13 of the MPS.
3.
The SCUb boards must be configured in slots 6 and 7 of the MPS and EPS.
4.
Service processing units (DPUe/SPUc/NIUa) can be configured in any slots except the slots
for the OMUc, clock boards, and SCUb boards. It is recommended that service processing
units be configured in small-numbered slots (starting from slot 0) and large-numbered slots
be reserved for interface boards.
5.
Interface boards can be configured only in slots 14 to 27 (except slots 24 and 25 in the
MPS).
6.
Service processing units and interface boards must be distributed evenly among subracks
to reduce the CPU and switching resources consumed during inter-subrack switching and
Issue 05 (2014-10-29)

54
prevent limitions imposed by inter-subrack bandwidth on traffic volume. For example, if

there are 9 DPUe boards, 12 SPUc boards, 6 interface boards, and 3 subracks, it is
recommended that 3 DPUe boards, 4 SPUc boards, and 2 interface boards be configured
in each subrack.
7.
SPU boards must be configured in active/standby mode. DPU and NIU boards must be
configured in load sharing mode by using a resource pool. OMU, SCU, and GCU/GCG
boards must be configured in active/standby mode.
8.
It is recommended that SAU boards be configured in independent mode. One to two SAU
boards can be configured. It is recommended that SAU boards be configured in slots 0 and
1 of the MPS. By default, slots 0 and 1 in the MPS are reserved for SAU. One SAU board
is delivered by default in UMTS mode or GU mode for EBC.
9.
The MPS supports a maximum of 9 pairs of SPUc boards and 9 DPUe boards.
10. The EPS supports a maximum of 9 pairs of SPUc boards and 9 DPUe boards.
11. It is recommended that the Iur-p interface board used for the RNC in Pool feature be
configured in the MPS in RAN17.0.
For examples of configuration operations, see Examples of Typical Configurations in section
4.2.11 Example of Typical BSC6900 UMTS Configuration.
4.2.7 Subracks
Table 4-19 Subrack configurations
Model
Abbrevia
tion
Name
QM1P00UMPS01
MPS
QM1P00UEPS01
EPS
WP1X000OMU02
OMUc
Operation and Maintenance Unit
WP1D000SAU01
SAUc
Service Aware Unit
WP1D000SCU01
SCUb
GE Switching network and Control Unit
By default, the following boards are delivered: OMUc, SAUc, and SCUb.
l
Configuration principles for the MPS:
One MPS must be configured in a BSC6900 UMTS.

l
Configuration principles for the EPS:
A maximum of five EPSs can be configured in a BSC6900 UMTS.

1.

- Number of EPSs_1 = Roundup ((Number of required SPUc boards Number of SPUc
boards that can be housed by MPS)/9)
If the number of required SPUc boards is less than the number of SPUc boards that can be
housed by MPS, you do not need to configure any EPS_1.
Issue 05 (2014-10-29)

55
The MPS can house 9 pairs of SPUc boards, and the EPS can also house 9 pairs of SPUc
boards.
- Number of EPSs_2 = Roundup ((Number of required DPUe boards Number of DPUe
boards that can be housed by MPS)/9)
If the number of required DPUe boards is less than the number of DPUe boards that can
be housed by MPS, you do not need to configure any EPS_2.
The MPS can house 9 DPUe boards, and the EPS can also house 9 DPUe boards.
- Number of EPSs_3 = Roundup ((Number of slots required by interface boards Number
of slots for interface boards in MPS)/14)
If the number of slots required by interface boards is less than the number of slots for
interface boards in the MPS, you do not need to configure any EPS_3.
The MPS provides 12 slots for interface boards
- Number of EPSs_4 = Roundup ((Number of required SPUc boards x 2Note + Number of
required DPUe boards + Number of slots required by interface boards + Number of required
NIUa boards Number of slots in MPS)/26, 0)
If the following formula is met, you do not need to configure any EPS_4:
Number of required SPUc boards x 2 + Number of required DPUe boards + Number of
slots required by interface boards + Number of required NIUa boards < Number of slots
provided by the MPS
The MPS provides 20 slots, among which two slots are reserved for SAUc boards.
NOTE
Each pair of SPUc boards occupies two slots.
Number of EPSs = Max (Number of EPSs_1, Number of EPSs_2, Number of EPSs_3,

Number of EPSs_4)
2.

Number of EPSs = Number of EPSs after capacity expansion Number of EPSs before
capacity expansion
By default, one SAUc board is delivered for EBC in GU and UO mode. If the customer
has purchased and used Huawei Nastar or other OSS feature, such as SON/RAN Serveice
Visibility Based on PRS, one or two SAUc boards need to be configured in the MPS. The
number of SAUc boards is determined by the OSS features used, as described in the
following table.
Issue 05 (2014-10-29)
Scenario
Number of SAU
Boards
Nastar Only
Any of the following is deployed: EBC, SON, and RAN

Serveice Visibility Based on PRS
Nastar is deployed, and any of the following is deployed:

EBC, SON, and RAN Serveice Visibility Based on PRS

56
4.2.8 Cabinets
Table 4-20 Cabinets
Model
Name
Function
WP1B4PBCBN00
BSC6900 cabinet
Cabinet
A maximum of two cabinets can be configured for a BSC6900 UMTS. Each cabinet can
accommodate three subracks.
1.

Number of cabinets = Roundup ((Number of MPSs + Number of EPSs)/3, 0)
where, Number of MPSs is 1.
2.

Number of cabinets = Number of cabinets after capacity expansion Number of cabinets
before capacity expansion
3.
Cabinet power comsumption:

The maximum power consumption for a single cabinet is 5100 W, and the maximum power
consumption for a single subrack is 1700 W.
The calculation formula is as follows:
BSC_Power_Consumption_Tool.xls
NOTE
l Average power consumption (Pavg) is the estimated value in a typical operating environment.
The maximum power consumption mentioned in hardware description is obtained when all
devices on boards are full-loaded. This maximum power consumption cannot be obtained under
the actual system running conditions. Therefore, Pavg is provided for power consumption
calculation.
l The maximum power consumption for a single subrack is 1700 W (including the power
consumption of fans) which is obtained when all slots of the subrack are configured with boards.
It is recommended that power distribution be configured as 1700 W per subrack. This can save
power distribution adjustment upon future capacity expansion.
4.2.9 Auxiliary Materials

Table 4-21 Auxiliary materials
Issue 05 (2014-10-29)
Model
Name
Function
QW1P8D442000
Trunk Cable
75-ohm trunk cable
QW1P8D442003
Trunk Cable
120-ohm trunk cable
QW1P0STMOM00
STM-1 Optical Connector
STM-1 optical unit
QW1P00GEOM00
GE Optical Connector
GE optical unit
QW1P0FIBER00
Optical Fiber
Optical cable

57
Model
Name
Function
QW1P0000IM00
Installation Material
Package
Installation material suite
QMAI00EDOC00
Documentation
Electronic documentation
75-ohm trunk cables must be in full configuration for a board.

Number of trunk cables = [Number of ATM interface units (32 E1s) + Number of IP interface
units (32 E1s)] x 2
NOTE
One trunk cable provides eight E1s. 32 E1s/8 E1s = 4. A trunk cable is a Y-shaped cable, which is connected
to both the active and standby boards.
120-ohm trunk cables must be in full configuration for a board.

Number of trunk cables = [Number of ATM interface units (32 E1s) + Number of IP interface
units (32 E1s)] x 2
NOTE
One trunk cable provides eight E1s. 32 E1s/8 E1s = 4. A trunk cable is a Y-shaped cable, which is connected
to both the active and standby boards.
Configuration principle for STM-1 optical units (QW1P0STMOM00):

STM-1 optical units need to be in full configuration for an optical interface board.
Number of STM-1 optical units = (Number of WP1D000AOU01s + Number of
WP1D000POU01s) x 4 + Number of WP1D000UOI01s x 8
Configuration principle of the GE optical unit (QW1P00GEOM00):

The GE optical units need to be in full configuration for an optical interface board.
Number of GE optical units = Number of WP1D000GOU01s or WP1D000GOU03s x 4
Configuration principle for optical cables (QW1P0FIBER00):

Optical cables are configured based on the number of optical modules required in the
BSC6900. Number of optical cables = (Number of STM optical modules + Number of GE
optical modules) x 2
Configuration principle for installation material suite (QW1P0000IM00):

One installation material suite (QW1P0000IM00) is configured for each BSC6900 cabinet
(WP1B4PBCBN00).
Configuration principle for electronic documentation (QMAI00EDOC00):

A set of electronic documentation (QMAI00EDOC00) is delivered with each BSC6900.
4.2.10 Restrictions on Inter-Subrack Switching

Huawei BSC6900 V900R011 uses SCUa boards. A pair of active and standby SCUa boards can
process data at 4 Gbit/s on the physical layer. The SCUa boards in various subracks are connected
Issue 05 (2014-10-29)

58
in star networking mode. Huawei BSC6900 V900R013, V900R015, V900R016 use SCUb
boards. A pair of active and standby SCUb boards can process data at 40 Gbit/s on the physical
layer. The SCUb boards in various subracks are connected in chain mode.
If either of the active and standby board becomes faulty, the processing capability is halved.
If the service boards are not evenly configured among the subracks or services are not evenly
deployed among the subracks, the volume of inter-subrack data flows may sharply increase.
Once the volume exceeds the capacity, services are interrupted. Therefore, all types of boards
should be evenly configured among subracks, including SPU, DPU, interface board, NIU.
Services should be evenly deployed, and the user-plane capacity should be similar.
For example, if there are 12 pairs of SPUc boards, 15 DPUe boards, 4 NIUa boards, 3 pairs of
Iub GOUe boards, 2 pairs of Iu GOUe boards, and 6 subracks, based on the preceding
configuration principles, each subrack should be configured with 2 pairs of SPUc boards, 2 or
3 DPUe boards, 1 NIUa boards or no NIUa boards, 1 pair of Iub GOUe boards or no Iub GOUe
boards, 1 pair of Iu GOUe boards or no Iu GOUe boards. The subrack with more DPUe boards
should be configured with more GOUe and NIUa boards. SAUc boards are configured in
reserved slots in MPS. The following table lists a recommended configuration.
Subrac
k
SPUc
(pair)
DPUe
(pcs)
NIUa(pcs)
Iub GOUe
(pair)
Iu GOUe
(pair)
SAUc
(pcs)
MPS
EPS1
EPS2
EPS3
EPS4
EPS5
Total
12
15
4.2.11 Example of Typical BSC6900 UMTS Configuration

The procedure of typical configuration is as follows:
Step 1 Input requirements.
Operator provides the network requirement which should include the information as contained
in Table 4-22.
Table 4-22 Network specifications
Issue 05 (2014-10-29)
Network Parameter
Value
Total subscribers
800,000
Total NodeBs
600
59
Network Parameter
Value
Total cells
3000
Voice Traffic per CS voice subscriber in BH(Erlang )
0.02
CS voice call duration (sec)
75
Handover times per CS call
CS voice call per subscriber per BH
0.96
PS call per subscriber per BH
Proportion of SHO for CS call
0.3
Mean holding time (MHT) in DCH/H/FACH state per PS call(sec)
52
Mean holding time (MHT) in PCH per PS call(sec)
PS channel switch times per PS call
Cell update times per PS call
Proportion of SHO for PS call
0.3
PS throughput (Including R99 and HSPA, UL+DL) per PS subscriber in BH

(bit/s)
4500
NAS(Attach,Detach, LAU, RAU) and SMS per subscriber per BH
3.6
Iub interface type
IP GE
Iu/Iur interface type
IP GE
Ratio of Iur traffic to Iub traffic
8%
Whether to enable service awareness (WRFD-020132 Web Browsing

Acceleration, WRFD-020133 P2P Downloading Rate Control during Busy
Hour, WRFD-150252 Video Service Rate Adaption, WRFD-150253 VoIP
Application Management, and WRFD-150254 Differentiated Service Based
on Application Resource Reservation)
Yes
Whether a Nastar-related SAU board is needed?
Yes
Whether the GPS is needed?
Yes
Step 2 Calculate the capacity requirements.

By dimension procedure, the requirement of operator can be described as following:
l Total Iu-PS throughput requirement (based on the sample input, the value is 3600 Mbit/
s) = Total Subscribers x PS throughput (including R99 and HSPA, UL+DL) per PS
subscriber in BH (bit/s) = 800,000 x 4500 bit/s= 3600 Mbit/s
Issue 05 (2014-10-29)

60
Total Iu-CS Erlang requirement (based on the sample input, the value is 16,000 Erlang)
= Total Subscribers x Voice Traffic per CS voice subscriber in BH (Erlang) = 800,000 x
0.02 = 16000
Total Iu-PS TEID requirement (based on the sample input, the value is 23,111) = Total
Subscribers x [Mean holding time (MHT) in DCH/H/FACH state per PS call (sec) + Mean
holding time (MHT) in PCH per PS call (sec)] x PS call per subscriber per BH/3600 =
800000 x (52 + 0) x 2/3600 = 23,111
Iu-PS session setup/release times requirement (based on the sample input, the value is
1778 times per second) = Total Subscribers x [PS call per subscriber per BH x (1 + PS
channel switch times per PS call x 0.5 + Cell update times per PS call x 0.5)]/3600 =
800,000 x [2 x (1 + 3 x 0.5 + 3 x 0.5)]/3600 = 1778
Total Iub PS throughput requirement(based on sample input, the value is 4680 Mbit/s)
= Total Subscribers x PS throughput (Including R99 and HSPA, UL+DL) per PS
subscriber in BH (bps) x (1 + Proportion of SHO for PS call) = 800,000 x 4500 x (1 +
0.3) bit/s = 4680 Mbit/s
Total Iub CS Erlang requirement (based on sample input, the value is 20,800 Erl) = Total
Subscribers x Voice Traffic per CS voice subscriber in BH (Erlang) x (1 + Proportion of
SHO for CS call) = 800,000 x 0.02 x (1 + 0.3) = 20,800
Total BHCA requirement (based on the sample input, the value is 2,368,000) = Total
Subscribers x (CS voice call per subscriber per BH + PS call per subscriber per BH) =
800,000 x (0.96 + 2) = 2,368,000
Total NodeB number requirement (based on the sample input, the value is 600) = Total
NodeBs = 600
Total Cell number requirement (based on the sample input, the value is 3000) = Total
Cells= 3000
Total Active users requirement (based on sample input, the value is 39,111) = Total
Subscribers x [Mean holding time (MHT) in DCH/H/FACH state per PS call (sec) x PS
call per subscriber per BH/3600 + Voice Traffic per CS voice subscriber in BH (Erlang)]
= 800000 x (52 x 2/3600 + 0.02) = 39,111
Total Iub CID/UDP requirement(based on the sample input, the value is 124,800) = Total
Subscribers x {Mean holding time (MHT) in DCH/H/FACH state per PS call(sec) x PS
call per subscriber per BH/3600 x [1 + 2 x (1+Proportion of SHO for PS call)] + Voice
Traffic per CS voice subscriber in BH (Erlang) x 2 x (1 + Proportion of SHO for CS call)}
= 800000 x {52 x 2/3600 x [1 + 2 x (1 + 0.3)] + 0.02 x 2 x (1 + 0.3)} = 124,800
Total Iub Session setup/release times requirement (based on the sample input, the value is
10,951 times/s) = Total Subscribers x [PS call per subscriber per BH x (3 + Handover times
per PS call x 2 + PS channel switch times per PS call x 1 + Cell update times per PS call x
0) + CS voice call per subscriber per BH x (2 + Handover times per CS call x 2)]/3600 =
800000 x [2 x (3 + 5 x 2 + 3 x 1) + 0.96 x (2 + 8 x 2)]/3600 = 10,951
l Under this traffic model, the BHCA supported by each SPUc only board is 114,578:
CP Load per subscriber (unit: CPU usage) = [CS voice call per subscriber per BH x (W1 +
Handover times per CS call x W2) + PS call per subscriber per BH x (w3 + PS channel switch
times per PS call x w7 + Cell update times per PS call x w8 + Handover times per PS call x
w6) + NAS (Attach, Detach, LAU, RAU) and SMS per subscriber per BH x w9]/3600 =
44.6%/3600 = 0.0124%
Subscriber number supported by each SPUc board = (70%-10%) x 8/CP Load per subscriber
= (70% - 10%) x 8/0.0124% = 38709
Issue 05 (2014-10-29)

61
BHCA capacity supported by each SPUc board = Subscriber number supported by one SPUc
board x (CS voice call per subscriber per BH + PS call per subscriber per BH) = 38709 x
(0.96 + 2) = 114578.
l Under this traffic model, theactual PS throughput capacity supported by each DPUe board
is 470 Mbit/s.
PS RAB mean data rate (UL+DL) (kbit/s) = [PS throughput (Including R99 and HSPA, UL
+DL) per PS subscriber in BH (bit/s) x 3600/1000]/[PS call per subscriber per BH x Mean
holding time (MHT) in DCH/H/FACH state per PS call (sec)]= 4,500 x 3600/1000/(2 x 52)
= 155.8
155.8 kbit/ ranges in [128, 196], PS Throughput Capacity per DPUe(Mbit/s) = 430 + (PS
RAB Mean data rate - 128) x 1.47 =430 + (155.8 - 128) x 1.47 = 470 Mbit/s.
Step 3 Configure hardware and hardware capacity licenses.
1.
Calculate the number of required DPUe boards and hardware capacity licenses.
Item
Description
Calculation of Board Quantity
Iub PS
throughput
PS throughput over the

Iub interface
a' = Total Iub PS throughput requirement/

Real PS throughput capacity supported by
each EGPUa UP board = 4680/470 = 9.95
Iub CS
Traffic
CS traffic over the Iub

interface
b' = Total Iub CS Erlang requirement /Real

PS throughput(Mbit/s) supported by each
DPUe board = 20800/3350 = 6.21
Active users
Number of active users

supported by the Iub
interface
n' = Total Active users requirement/Number

of active users supported by each DPUe
board = 39111/5880 = 6.65
Cell number
Number of cells
managed by the RNC
c' = Total Cell quantity requirement /Number

of cells supported by each DPUe board =
3000/300 = 10
N_ DPUe = Roundup [Max(a' + b', n', c')] + 1 = Roundup [Max(9.95 + 6.21, 10, 6.65)] +
1 = 18.
Calculation for hardware license:
Number of DPUe boards can be used for PS throughput x 335 Mbit/s (PS throughput
capacity contains in each DPUe board) = (18 - 6.21) x 335 Mbit/s = 3950 Mbit/s < Total
Iub PS throughput requirement (4680 Mbit/s).
Therefore, hardware capacity licenses (165 Mbit/s) is calculated as follows:
N_165 = Min{N_DPUe, Roundup [(4680 - 3950)/165]} = 5.
3950 + 5 x 165 > 4680
Therefore, hardware capacity licenses (300 Mbit/s) are not required.
2.
Issue 05 (2014-10-29)
Calculate the number of required SPUc/SPUb boards.

62
Item
Description
BHCA
requirement
BHCA required by
the network
Calculate the BHCA capacity of SPUc board in

this traffic model.
b' = Total BHCA requirement/BHCA capacity
supported by SPUc board = 2368000/114578 =
20.66
Active users
Number of active
users supported on
the control plane
n' =Total Active users requirement/Number of

active users supported by each pair of SPUc
boards = 39111/9600 = 4.07
Online users
Number of online
users supported on
the control plane
m' = Total Online users requirement/Number of

online users supported by each pair of SPUc
boards = 39111/24000 = 1.62
NodeB
number
Number of NodeBs
managed by the
RNC
nb' = Total NodeB number requirement/Number

of NodeBs supported by each pair of SPUc boards
= 600/180 = 3.33
Cell number
Number of cells
managed by the
RNC
c' = Total Cell number requirement/Number of

cells supported by each pair of SPUc boards =
3000/600 = 5
SPUc/SPUb boards are configured in active/standby mode.

Number of SPUc/SPUb boards (pair) = Roundup (MAX(b', n', m', nb', c')) = Roundup [Max
(20.67, 4.07, 1.62, 3.33, 5)] = 21.
3.
Calculate the number of required NIUa boards and QM1SNIU50M00s (Network

Intelligence Throughput License).
NIU boards are configured in load sharing mode by using a resource pool.
N_NIUa = Roundup (Total Iub PS throughput requirement/PS throughput (Mbit/s)
supported by each NIUa board) + 1 = Roundup (4680 / 3200, 0) + 1 = 3.
N_QM1SNIU50M00 = Roundup [(4680 50)/50] = 93.
If the corresponding optional feature is not configured, N_NIUa = 0.
4.
Issue 05 (2014-10-29)
Calculate the number of GOUe boards for the Iub interface.

Item
Capacity
Requirements
Iub transmission type
GE Optical(IP)
N/A
Iub PS throughput
ba = 4680 Mbit/s
ba' = Total Iub PS throughput

requirement / PS throughput (Mbit/s)
supported by the GOUe in Iub interface =
4680/2600=1.8
Iub CS Traffic
bb = 20800
bb' = Total Iub CS Erlang requirement /

Erlang supported by each GOUe board =
20800/18000 = 1.16

63
Item
Capacity
Requirements
NodeB number
bn = 600
bn' = Total NodeB quantity requirement /

Number of NodeBs supported by each
GOUe board = 600/500 = 1.2
Iub active users(CID/

UDP)
an = 124800
an' = Total Iub CID/UDP requirement /

Iub UDP number supported by each
GOUe board =124800/129000 = 0.97
Assume that GOUe boards are configured in active/standby mode.

N_IUB_GOUe (pair) = Roundup [Max(ba' + bb', bn', an')] = Roundup [Max(1.8 + 1.16,
1.2, 0.97)] = 3
5.
Calculate the number of GOUe boards for the Iu/Iur interface.

Interfac
e
Item
Capacity
Requirement
s
Iu-CS
Iu-CS
transmission
type
GE Optical(IP)
Iu-CS traffic
cb = 16,000
Iu-PS
transmission
type
GE Optical(IP)
Iu-PS throughput
pb = 3600
pb' = Total Iu PS throughput

requirement/PS throughput (Mbit/s)
supported by the GOUe in Iu-PS
interface = 3600/3200 = 1.13
Iu-PS online
users
pu = 23,111
pu' = Total Iu-PS on-line users/Iu-PS

TEID supported by GOUe
=23111/200000 = 0.12
Iu-PS session setup and release
ps = 1778
ps' = ps/ Board specification =

1778/5000 = 0.36
Iu-PS
cb' = Total IuCS Erlang requirement/

Traffic (Erl) supported by each GOUe
board = 16000/ 18000 = 0.89
Assume that the IU-PS and Iu-CS interfaces and Iur interface are configured on the same
GOUe board.
N_IUIUR_GOUe (pair) = Roundup [Max(pb' + cb', ps', pu') + (pb' + cb') x 8%] = Roundup
[Max(1.13 + 0.89, 0.36, 0.12) + (1.13 + 0.89) x 8%] = 3
Issue 05 (2014-10-29)

64
N_GOUe (pair) = N_IUB_ GOUe + N_IUIUR_GOUe = 3+3 = 6

6.
Configure SAU boards.

Reserve a pair of slots for SAU boards. In Uo mode, one SAU board is delivered for EBC
by default.
If a customer has purchased the OSS feature, such as Nastar/SON/RAN Serveice Visibility
Based on PRS, the customer must configure one or two SAU boards. The number of SAUc
boards to configured is determined by OSS features to enable.
7.
Configure GCG boards.

A pair of GCGb boards must be configured to support the GPS.
8.
Calculate the number of EPSs (QM1P00UEPS01).

Number of EPSs =
= Rounup [(N_SPU(23 x 2) + N_DPUe(18) + N_Iub_GOUc(3 x 2) + N_IUIUR_GOUc(3
x 2) + N_NIUa(3) - 20) /26 ] = 3
There are 20 slots in the MPS besides fixed slots (28 - 2OMU - 2GCU - 2SCU - 2SAU).
There are 26 slots in the EPS besides fixed slots (28 2 SCU).
9.
Calculate the number of required cabinets (WP1B4PBCBN00s)

Number of cabinets = Roundup ((Number of MPSs + Number of EPSs)/3) = Roundup (4/3)
=2
The following table lists the configurations of the BSC6900 UMTS.

Name
Abbreviation
Cabinet
Quanti
ty
WP1B4PBCBN00
MPS
QM1P00UMPS01
EPS
QM1P00UEPS01
Clock board (pair)
GCGb
WP1D000GCG02
Data Processing Unit
DPUe
WP1D000DPU03
18
Hardware Capacity License (165

Mbit/s)
QM1SHW165M00
Hardware Capacity License (300

Mbit/s)
QM1SHW300M00
Signaling Processing Unit (pair)
SPUc
WP1D000SPU03
21
Network Intelligence Unit
NIUa
WP1D000NIU00
QM1SNIU50M00
93
Network Intelligence Throughput

License
Issue 05 (2014-10-29)
Model
Iu/Iur Interface Board (Pair)
GOUe
WP1D000GOU03
Signaling Access Unit
SAUc
None
1 or 2

65
To avoid the volume of inter-subrack data flows exceeding the limitation, service boards must
be evenly deployed among subracks. The following figure shows a recommended configuration.
----End
4.2.12 BSC6900 UMTS Recommended Capacity for Delivery

For the sake of network security, the actual capacity of a configured BSC6900 is much lower
than the specified maximum capacity.
The number of NodeBs under each BSC6900 UMTS should be less than 300.
4.3 BSC6900 GU Product Configurations

The following describes the hardware configuration principles of the BSC6900 GU.
1.
Issue 05 (2014-10-29)
GSM boards and UMTS boards should not be configured in the same subrack. The MPS
must work in UMTS mode.
66
2.
One to four GSM subracks can be configured. One to five UMTS subracks can be
configured.
3.
The total number of GSM and UMTS subracks should be smaller than or equal to six.
4.
Number of cabinets = Roundup [(Number of GSM subracks + Number of UMTS subracks)/

3]. A maximum of two cabinets (excluding the cabinets housing TC subracks) can be
configured.
5.
When the BM/TC separated mode is used, the MPS must work in GSM mode.
6.
The NIUa boards providing the service awareness function must be configured separately
for GSM and UMTS modes.
7.
Two slots in the MPS of BSC6900 GU must be reserved for SAU boards.
The preceding principles apply to BSC6900 GU deployment and capacity expansion.

The procedure for configuring a newly deployed BSC6900 GU is as follows:
Step 1 Obtain GSM and UMTS network parameter values.
Step 2 Perform dimensioning to obtain the GSM and UMTS network requirements respectively.
Step 3 Calculate the UMTS configuration and GSM configuration based on the network
requirements.The detailed configuration principles and restrictions for UMTS boards and GSM
boards are consistent to the descriptions in 4.1 BSC6900 GSM Product Configurationsand4.2
BSC6900 UMTS Product Configurations.
l If the capacity required by the GSM configuration and UMTS configuration does not exceed
the BSC6900 GU specifications (that is, the total number of GSM subracks and UMTS
subrack does not exceed six), no further action is required.
l If the total required capacity exceeds the maximum specifications of one BSC6900 GU or
the number of slots required for the interface boards exceeds the limitation, an extra BSC6900
GU needs to be added.
----End
Issue 05 (2014-10-29)

67
5 Expansion and Upgrade Configurations
Expansion and Upgrade Configurations
5.1 BSC6900 GSM Hardware Expansion and Upgrade

Configurations
Capacity expansion can be performed using the following methods:
l
Hardware expansion.
Configuration of hardware capacity licenses.
You can use either of or both of the two methods based on the traffic model and traffic volume
requirements.
Capacity expansion complies with the "minimum hardware" principle.
5.1.1 Hardware Expansion and Upgrade Configurations

Two types of board can be used to support the same functions or transmission mode. For example,
to implement TDM over STM-1 on the Abis interface, OIUa and POUc boards can be installed.
This is known as mixed insertion of boards. The following table lists the HW60 R8, HW69 R11,
HW69 R13, HW69 R15, HW69 R16 boards.
Issue 05 (2014-10-29)
Hardware
Version
Board
HW60 R8
DPUc, DPUd, XPUa, SCUa, TNUa, GCUa, OMUb, EIUa, FG2a, GOUa,
OIUa, PEUa
HW69 R11
DPUc, DPUd, XPUb, SCUa, TNUa, GCUa, GCGa, OMUa, EIUa, FG2c,
GOUc, OIUa, PEUa, POUc
HW69 R13
DPUf, DPUg, XPUb, SCUb, TNUa, GCUa, GCGa, OMUc, EIUa, FG2c,
GOUc, PEUa, POUc, SAUc, NIUa
HW69 R15
DPUf, DPUg, XPUb, SCUb, TNUa, TNUb, GCUa, GCGa, OMUc, EIUb,
OIUb, FG2c, GOUc, PEUc, POUc, SAUc, NIUa

68
Hardware
Version
Board
HW69 R16
DPUf, DPUg, XPUc, SCUb, TNUb, GCUb, GCGb, OMUc, EIUb, OIUb,
FG2c, GOUe, PEUc, POUc, SAUc, NIUa
NOTE
TNUb was supported in V900R15SPC560.
In HW69 R16, XPUb is replaced with XPUc, TNUa is replaced with TNUb, GCUa is replaced
with GCUb, GCGa is replaced with GCGb, and GOUc is replaced with GOUe, but board
specifications remain unchanged. Therefore, the configuration principle and capacity expansion
principle of XPUc, TNUb, GCUb, GCGb, and GOUe remain the same as XPUb, TNUa, GCUa,
GCGa, GOUc, respectively.
l
Issue 05 (2014-10-29)
BM configuration

69
Model
Name
BM/TC Combined Mode
WP1D000FG201
FG2c
1. Number of FG2c boards as A interface boards

Number of FG2c boards as A interface boards = 2
x Roundup (((MaxACICPerBSCIP Number of
FG2a boards supported by the A interface/2 x
ACICPerFG2a)/ACICPerFG2c), 0)
NOTE
The quantity depends on the number of ports and the
number of equivalent CICs on the A interface. In capacity
expansion scenarios, the capacity specifications and
number of ports supported by the existing FG2a boards
must be subtracted from the total required capacity.
2. Number of FG2c boards as Abis interface boards

Number of FG2c boards as Abis interface boards =
2 x Roundup (MAX (Roundup ((AbisIPFEGENo Number of FG2a boards supported by the Abis
interface/2 x GEPortPerFG2a)/GEPortPerFG2c,
0), (TRXNoFEGE Number of FG2a boards
supported by the Abis interface/2 x
TRXNoPerFG2a)/TRXNoPerFG2c), 0)
If the inter-BSC soft synchronized network
function is enabled and the Abis interface does not
use IP transmission, a pair of FG2c boards are
configured by default.
NOTE
When the Abis interface uses IP transmission, the Abis
interface boards must be configured. The number of
required Abis interface boards depends on the number of
FE/GE ports and the number of TRXs. In capacity
expansion scenarios, the originally supported TRXs must
be subtracted from the total required TRXs. In addition,
the number of ports supported before capacity expansion
should also be considered.
3. Number of FG2c boards as Gb interface boards

Number of FG2c boards as Gb interface boards =
2 x Roundup ((MAX (Roundup (MAX
(GbIPFEGENo/GEPortPerFG2c, 0) x
GEPortPerFG2c Number of FG2a boards over
Gb interface/2 x GEPortPerFG2a)/
GEPortPerFG2c), (GbIPTputPerBSC Number of
FG2a boards over Gb interface/2 x
(GbTputPerFG2a/1024))/GbTputPerFG2c/1024),
0)
NOTE
When the built-in PCU is used, Gb interface boards must
be configured. The number of required Gb interface
boards depends on the number of ports and the traffic on
the Gb interface. The originally supported traffic must be
subtracted from the total supported traffic.
Issue 05 (2014-10-29)

70
Model
Name
BM/TC Combined Mode

4. The number of FG2c boards to be configured is
equal to the total number of all the preceding
boards.
Issue 05 (2014-10-29)

71
Model
Name
BM/TC Combined Mode
WP1D000GOU03
GOUe
1. Number of GOUe boards as A interface boards

Number of WP1D000GOU03s as A interface
boards = 2 x Roundup (((MaxACICPerBSCIP
Number of GOUa boards as A interface boards/2 x
ACICPerFG2a)/ACICPerFG2c - Number of
GOUc boards as A interface boards/2), 0)
NOTE
number of equivalent CICs on the A interface. In capacity
expansion scenarios, the configuration quantity equals
the calculated number minus the board capacity
specifications and port number before capacity
expansion.
2. Number of GOUe boards as Abis interface boards

Number of GOUe boards as Abis interface boards
= 2 x Roundup ((MAX(Roundu
((MAX(ROUNDUP(AbisIPFEGENo/
GEPortPerGOUc, 0) x GEPortPerGOUc Number
of GOUa boards as Abis interface boards/2 x
GEPortPerGOUa)/GEPortPerGOUc,
(TRXNoFEGE Number of GOUa boards as Abis
interface boards/2 x TRXNoPerFG2a)/
TRXNoPerFG2c), 0)
Number of WP1D000GOU03s as Abis interface
boards = 2 x ROUNDUP((MAX(ROUNDUP
(AbisIPFEGENo/GEPortPerGOUe, 0) x
GEPortPerGOUe Number of GOUa boards as
Abis interface boards/2 x GEPortPerGOUa Number of GOUc boards as Abis interface boards/
2 x GEPortPerGOUc)/GEPortPerGOUe,
(TRXNoFEGE - Number of GOUa boards as Abis
interface boards/2 x TRXNoPerGOUa - Number of
GOUc boards as Abis interface boards/2 x
TRXNoPerFG2c)/TRXNoPerFG2c), 0)
NOTE
When IP transmission is used on the Abis interface, this
board should be configured. The configuration quantity
depends on the number GE ports and the number of
TRXs. In capacity expansion scenarios, the configuration
quantity equals the calculated quantity minus the number
of originally supported TRXs. In addition, the number of
ports supported before capacity expansion should also be
considered.
3. Number of GOUe boards as Gb interface boards

Number of GOUe boards as Gb interface boards =
2 x Roundup (MAX(GbIPGEOpticNo Number
of GOUa boards as Gb interface boards/2 x
GEPortPerGOUe, GbIPTputPerBSC/
GbTputPerFG2c/1024), 0)
Issue 05 (2014-10-29)

72
Model
Name
BM/TC Combined Mode

Number of GOUe boards as Gb interface boards =
2 x Roundup (MAX(((GbIPGEOpticNo number
of GOUa boards as Gb interface boards/2 x
GEPortPerGOUa)/GEPortPerGOUe,
(GbIPTputPerBSC Number of GOUa boards as
Gb interface boards/2 x (GbTputPerGOUa/1024))/
GbTputPerFG2c/1024), 0)
NOTE
When a built-in PCU is used, Gb interface boards should
be configured. The configuration quantity depends on the
number of ports and the traffic on the Gb interface.
Generally, only GOUc and GOUe boards support Gb
over GE.
4. The number of GOUe boards to be configured is

boards.
Issue 05 (2014-10-29)

73
Model
Name
BM/TC Combined Mode
WP1D000POU01
POUc
1. Number of POUc boards as A interface boards

(TDM transmission) = 2 x Roundup ((MaxACICPerBSCTDM Number of OIUa and OIUb boards
as A interface boards/2 x ACICPerOIUa)/
ACICPerPOUcTDM, 0)
2. Number of POUc boards as Ater interface boards
(TDM transmission) = 2 x Roundup
((MaxAterCICPerBSC Number of OIUa and
OIUb boards as Ater interface boards/2 x
AterCICPerOIUa)/AterCICPerPOUcTDM, 0)
3. Number of POUc boards as Abis interface boards
(TDM transmission) = 2 x Roundup (MAX
(AbisTDMSTM1No/STM1PortPerPOUc,
TRXNoTDMSTM1/TRXHRPerPOUcTDM), 0)
NOTE
number of TRXs. An E1 port (which can be shared in
cascading networking) must be configured for each base
station by default.
4. Number of POUc boards as A interface boards (IP

transmission) = 2 x Roundup (MAX
(MaxACICPerBSCIP/ACICPerPOUcIP), 0)
NOTE
The quantity depends on the number of CICs on the A
interface.
5. Number of POUc boards as Abis interface boards

(IP transmission) = 2 x Roundup P(MAX
(SiteNoIPSTM1/STM1PortPerPOUc/63,
AbisIPSTM1No/STM1PortPerPOUc,
TRXNoIPSTM1/TRXPerPOUcIP), 0)
NOTE
interface.
6. Number of POUc boards as Gb interface boards =

2 x Roundup (MAX(SiteNoIPSTM1/
STM1PortPerPOUc/63, AbisIPSTM1No/
STM1PortPerPOUc, TRXNoIPSTM1/
TRXPerPOUcIP), 0)
NOTE
When the Abis interface uses IP transmission, this board
should be configured. The configuration quantity
depends on the number of base stations, the number of
ports, and the number of TRXs. An E1 port must be
configured for each base station by default.
7. The number of POUc boards to be configured is

boards.
Issue 05 (2014-10-29)

74
Model
Name
BM/TC Combined Mode

NOTE
In capacity expansion scenarios, the configuration
quantity equals the calculated number minus the OIUa
and OIUb board capacity specifications on the A, Ater
and Abis interfaces.
Issue 05 (2014-10-29)

75
Model
Name
BM/TC Combined Mode
WP1D000EIU01
EIUb
The EIUb has the same capacity with the EIUa, so that
the EIUb inherits the configuration and capacity
expansion principles of the EIUa.
1. Number of EIUb boards as Ater interface boards =
2 x Roundup (MaxAterCICPerBSC/
AterCICPerEIUa, 0)
NOTE
The quantity depends on the number of CICs on the Ater
interface. In the new site deployment scenario,
MaxAterCICPerBSC indicates the required number of
CICs on the Ater interface.
In the capacity expansion scenario, MaxAterCICPerBSC
indicates the additional number of CICs on the Ater
interface.
2. Number of EIUb boards as Abis interface boards =

2 x Roundup (MAX(SiteNoTDME1/
E1PortPerEIUa, AbisTDME1No/E1PortPerEIUa,
TRXNoTDME1/TRXFRPerEIUa,
(SiteNoTDME1 x Roundup ((1+TRXNoPerSite)/
LAPDMuxRate/255, 0), 0)+IF(AND(or
((TRXNoHDLCE1=0), (TRXNoIPE1=0),
TRXNoHDLCSTM1=0, TRXNoIPSTM1=0),
(Semi_PermanentNum=0)), 0, 2))
NOTE
The quantity depends on the number of sites, ports and
TRXs on the Abis interface. Each NodeB must be
separately configured with one E1 port by default. E1
ports on different NodeBs can be cascaded in networking
deployment.
In the capacity expansion scenario,
SiteNoTDME1,AbisTDME1No, andTRXNoTDME1
indicate the number of NodeBs, ports, and TRXs,
respectively.
Another two Abis interface boards are needed if
monitoring timeslots are configured on the NodeB to
optimize transmission efficiency.
LAPDMuxRate indicates the LAPD multiplex ratio,
whose range is (1:1, 2:1, 3:1, 4:1, 5:1, 6:1).
3. Number of EIUb boards as Pb interface boards = 2

x Roundup (MAX (PbTDME1No/E1PortPerEIUa,
0))
NOTE
The Pb interface board in configured only when an
external PCU is installed. The number of EIUb boards as
Pb interface boards depends on the number of ports. In
the capacity expansion scenario, PbTDME1No indicates
the additional number of ports.
Issue 05 (2014-10-29)

76
Model
Name
BM/TC Combined Mode

4. The number of EIUb boards to be configured is
boards.
WP1D000OIU01
OIUb
1. The OIUb has the same capacity with the OIUa,

and therefore the OIUb inherits the configuration
and capacity expansion principles of the OIUa.
Number of OIUb boards as Ater interface boards =
2 x Roundup (MaxAterCICPerBSC/
AterCICPerOIUa, 0)
NOTE
interface. In the capacity expansion scenario,
MaxAterCICPerBSC indicates the additional number
of CICs on the Ater interface.
2. Number of OIUb boards as Abis interface boards

= 2 x Roundup (MAX (AbisTDMSTM1No/
STM1PortPerOIUa,TRXNoTDMSTM1/
TRXHRPerOIUa), 0)
NOTE
number of TRXs on the Abis interface. In the capacity
expansion scenario, AbisTDMSTM1Noindicates the
additional number of ports andTRXNoTDMSTM1
indicates the additional number of TRXs.
Each NodeB must be separately configured with one E1
port by default. E1 ports on different NodeBs can be
cascaded in networking deployment.
3. Number of OIUb boards as Pb interface boards = 2

x Roundup (MAX (PbTDME1No/
E1PortPerOIUa, 0))
NOTE
In the capacity expansion scenario, PbTDMSTM1No
indicates the additional number of ports.
4. The number of OIUb boards to be configured is

equal to the total number of all the preceding boards
NOTE
In RAN13.0 and later versions, all OIUa boards are replaced
with POUc boards.
Issue 05 (2014-10-29)

77
Model
Name
BM/TC Combined Mode
WP1D000PEU01
PEUc
1. The PEUc has the same capacity with the PEUa,

and therefore the PEUa inherits the configuration
and capacity expansion principles of the PEUa.
Number of PEUc boards as A interface boards = 2
x Roundup (MaxACICPerBSCIP/
ACICperPEUaIP,0)
NOTE
The board quantity depends on the number of CICs. In
the capacity expansion scenario, MaxACICPerBSCIP
indicates the additional number of CICs on the A
interface.
2. Number of PEUc boards as Abis interface boards

(IP) = 2 x Roundup (MAX(SiteNoIPE1/
E1PortPerPEUa, AbisIPE1No/(E1PortPerPEUa IF((Semi_PermanentNum=0), 0, 1)),
TRXNoIPE1/TRXPerPEUaIP), 0)
NOTE
The Abis interface board is configured when the IP
transmission mode is used. The number of Abis interface
boards depends on the number of ports and TRXs. By
default, each NodeB is separately configured with one E1
port.
In the capacity expansion scenario,
SiteNoIPE1,AbisIPE1No, andTRXNoIPE1 indicate
the number of NodeBs, ports, and TRXs, respectively.
32 E1/T1 ports are configured on each pair of boards if
monitoring time slots are configured on the NodeB using
IP over E1.
Otherwise, 31 E1/T1 ports are configured.
3. Number of PEUc boards as Gb interface boards =2

x Roundup (MAX(GbFRE1No/E1PortPerPEUa,
GbFRTputPerBSC/GbTputPerPEUaFR/1024), 0)
NOTE
When a built-in PCU is used, Gb interface boards must
be configured. The number of required Gb interface
boards depends on the number of ports and the traffic on
the Gb interface.
In the network expansion scenario,
GbFRE1NoandGbFRTputPerBSC indicate the
additional number of Gb interfaces and traffic volume
over the Gb interface, respectively.
4. The number of PEUc boards to be configured is

boards.
Issue 05 (2014-10-29)

78
Model
Name
BM/TC Combined Mode
WP1D000XPU03
XPUc
1. If the number of eGBTS TRX is not enlarged (Only

GBTS TRX enlarged):
Number of required XPUc boards = 2 x Roundup
(MAX((Number of TRXs after capacity expansion
- Number of TRXs for XPUa boards)/640,
(Number of BHCA enlarged - Number of BHCA
for XPUa boards)/1050000, (Number of ERL
enlarged - Number of ERL for XPUa boards)/
3900), 0)
NOTE
If the IBCA function is enabled in the live network, the
number of XPUc boards used for the IBCA function will
be subtracted from the quantity before capacity
expansion.
Number of TRXs for XPUa boards: The maximum
number of TRXs is determined based on the number of
pairs of XPUa boards. The mapping between the number
of pairs of XPUa boards and the number of TRXs is as
follows:
1: 270; 2: 630; 3: 990; 4: 1350; 5: 1710; 6: 2070.
Number of BHCA for XPUa boards: The maximum
number of BHCA is determined based on the number of
of pairs of XPUa boards and the number of BHCA is as
follows:
1: 492000; 2: 1148000; 3: 1804000; 4: 2460000; 5:
3116000; 6: 3772000.
Traffic volume for XPUa boards: The maximum traffic
volume is determined based on the number of pairs of
XPUa boards. The mapping between the number of pairs
of XPUa boards and the trafffic volume is as follows:
1: 1720; 2: 4020; 3: 6320; 4: 8620; 5: 10920; 6: 13220.
2. If the number of eGBTS TRX is enlarged:

Number of required XPUc boards = 2 x Roundup
(MAX((Number of TRXs after capacity expansion
- Number of TRXs for XPUa boards)/640,
for XPUa boards) x Number of GBTS TRX
enlarged/Number of TRX enlarged /1050000 +
for XPUa boards) x Number of eGBTS TRX
enlarged/Number of TRX enlarged/950000,
(Traffic volume enlarged - Traffic volume for
XPUa boards)/3900), 0)
Issue 05 (2014-10-29)

79
Model
Name
BM/TC Combined Mode

NOTE
The methods for estimating the number of TRXs and
traffic volume for XPUa boards are the same as thosed
used when the number of eGBTS TRX is not enlarged.
Number of BHCA for XPUa boards: The maximum
number of BHCA is determined based on the number of
of pairs of XPUa boards and the number of BHCA is as
follows:
1: 492000 x Number of GBTS TRX enlarged/Number of
TRX enlarged + 492000 x Number of eGBTS TRX
enlarged/Number of TRX enlarged
2: 1148000 x Number of GBTS TRX enlarged/Number
of TRX enlarged + 1148000 x Number of eGBTS TRX
enlarged/Number of TRX enlarged.
If "Number of required WP1D000XPU03s" <= 0,

then there is no need to add XPUc board.
3. If the IBCA function will be used, one more pair of
XPUc boards should be used as XPUI.
WP1D000NIU00
Issue 05 (2014-10-29)
NIUa
Configure this board only when intelligent service

awareness is required. If intelligent service awareness
is required, configure one NIUa board.

80
Model
Name
BM/TC Combined Mode
WP1D000DPU05
DPUf
1. In BM/TC separated configuration mode (or TDM/

IP hybrid transmission in A over IP)
On the BM side:
The number of DPUf to be configured depends on
the number of CICs that require IWF conversion
between TDM and IP and between IP and IP.
Number of DPUf boards = Roundup
(MAXIWFPerBSCTDMIP/IWFNoPerDPUfTDMIP + Max (MAXIWFPerBSCIPIP MAXIWFPerBSCTDMIP, 0)/
IWFNoPerDPUfIPIP,0) + 1
On the TC side:
Number of DPUf boards = RoundUp(MaxACICPerBSCTDM/TCNoPerDPUf) +1
2. In BM/TC combined mode (or TDM/IP hybrid
transmission in A over IP)
The DPUf providing the TC function can support
the IWF function of the same specifications as
DPUf.
Extra DPUf baords should be configured to provide
the IWF function for the A-interface CICs in A over
IP mode.
Number of DPUf boards = Roundup (MaxACICPerBSCTDM/TCNoPerDPUf,0) + Roundup
3. A over IP
The number of DPUf boards to be configured
depends on the number of CICs that require IWF
conversion between TDM and IP and between IP
and IP.
Number of DPUf boards= Roundup
4. All IP
Number of DPUf boards = Roundup
(MaxACICPerBSCIP / IWFNoPerDPUfIPIP,0) +1
Issue 05 (2014-10-29)

81
Model
Name
BM/TC Combined Mode
WP1D000DPU06
DPUg
Number of DPUg boards = Roundup

(MaxPDCHPerBSC/PDCHNoPerDPUg, 0) + 1
Number of DPUd boards
NOTE
This module must be configured when a built-in PCU is used.
The configuration quantity depends on the maximum number
of PDCHs required by the BSC. DPUg boards work in N+1
redundancy mode.
GMIPEPRACK00
GEPS
1. Total number of interface boards

2. Total number of user-plane boards
Number of processing subracks = Roundup (MAX
(Total number of interface boards 10/14, (Total
number of interface boards + Total number of userplane boards 18)/24, 0))
QM1B0PBCBN00
Cabine
t
Number of cabinets = (Number of GMPSs + Number

of GEPSs)/3
Multiple transmission modes, such as TDM, HDLC, and IP, can be used on the Abis
interface within one BSC.
l
TC configuration
The following table describes the configurations of each module.
Issue 05 (2014-10-29)

82
Model
Name
BM/TC Combined Configuration Mode
WP1D000EI
U01
EIUb
1. The EIUb has the same capacity with the EIUa, and
therefore the EIUb inherits the configuration and
capacity expansion principles of the EIUa.
Number of EIUb boards as A interface boards = 2 x
Roundup (MaxACICPerBSCTDM/ACICPerEIUa,
0)
NOTE
MaxACICPerBSCTDM indicates the additional number
of CICs on the A interface.
2. Number of EIUb boards as Ater interface boards = 2

x Roundup (MaxAterCICPerBSC/AterCICPerEIUa,
0)
NOTE
interface. In the new site deployment scenario,
MaxAterCICPerBSC indicates the required number of
CICs on the Ater interface.
indicates the additional number of CICs on the Ater
interface.
3. The number of EIUb boards to be configured is equal

to the total number of all the preceding boards.
Issue 05 (2014-10-29)

83
Model
Name
WP1D000OI
U01
OIUb
1. The OIUb has the same capacity with the OIUa, and
therefore the OIUb inherits the configuration and
capacity expansion principles of the OIUa.
Number of OIUb boards as A interface boards = 2 x
Roundup (MaxACICPerBSCTDM / ACICPerOIUa,
0)
NOTE
MaxACICPerBSCTDM indicates the additional number
of CICs on the A interface.
2. Number of OIUb boards as Ater interface boards = 2

x Roundup (MaxAterCICPerBSC/AterCICPerOIUa,
0)
NOTE
interface.
indicates the additional number of CIC circuits on the Ater
interface.
3. The number of OIUb boards to be configured is equal

to the total number of all the preceding boards.
NOTE
In RAN13.0 and later versions, all OIUa boards are replaced
with POUc boards.
WP1D000PE
U01
PEUc
The PEUc has the same capacity with the PEUa, and
therefore the PEUa inherits the configuration and
capacity expansion principles of the PEUa.
Number of PEUc boards as A interface boards = 2 x
Roundup (MaxACICPerBSCTDM/ACICperPEUcIP, 0)
NOTE
The quantity depends on the number of CICs on the A interface.
In the capacity expansion scenario, MaxACICPerBSCTDM
indicates the additional number of CIC circuits on the A
interface.
Issue 05 (2014-10-29)

84
Model
Name
WP1D000PO
U01
POUc
1. Number of POUc boards as A interface boards (TDM

transmission) = 2 x Roundup ((MaxACICPerBSCTDM Number of OIUa boards as A
interface boards/2 x ACICPerOIUa)/
ACICPerPOUcTDM, 0)
2. Number of PEUc boards as Ater interface boards
(TDM transmission) = 2 x Roundup ((MaxAterCICPerBSC Number of OIUa boards as Ater interface
boards/2 x AterCICPerOIUa)/AterCICPerPOUcTDM, 0)
When a built-in PCU is used, Gb interface boards must
be configured. The configuration quantity depends on
the number of ports and the traffic on the Gb interface.
3. The number of PEUc boards to be configured is equal
to the total number of all the preceding boards
NOTE
In other scenarios of capacity expansion, the configuration
quantity equals the calculated number minus the OIUa board
capacity specifications on the Ater and Abis interfaces.
WP1D000DP
U05
DPUf
GMIPEPRAC
K00
GEPS
DPUf provides only the TC function.

Number of DPUf boards = Roundup ((MaxACICPerBSC
(DPUc 1) x TCNoPerDPUc)/TCNoPerDPUf, 0)
1. Total number of interface boards = EIUa + OIUa +
EIUb + OIUb + POUc
2. Total number of user-plane boards = DPUc + DPUf
3. Number of processing subracks = Roundup (MAX
(Total number of interface boards/14, (Total number
of interface boards + Total number of user plane
boards)/24, 0))
QM1B0PBC
BN00
Cabinet
Number of cabinets = (Number of GMPSs + Number of

GEPSs)/3
5.1.2 Hardware Capacity License Expansion

N/A
5.1.3 Examples of Hardware Expansion

l
Total replacement
An operator may want to increase equipment integration and achieve a larger capacity with
existing cabinets and subracks. In this case, a total replacement is recommended.
In a total replacement, capacity is considered first. The Unistar quotation template is used
to work out a BSC equipment list based on the specifications of the new hardware version.
The boards required for the capacity expansion are determined by comparing with existing
boards that can be reused. Boards that cannot be reused need to be removed.
Issue 05 (2014-10-29)

85
The procedure for a total replacement is as follows:

Step 1 Fill in the Unistar calculation table and calculate the configuration required after capacity
expansion.
Step 2 Record the board and equipment configurations before capacity expansion.
Step 3 The components required in capacity expansion are the components after capacity expansion
minus those before capacity expansion.
Item
Name
Configuration
Before
Capacity
Expansion
Configuration
After Capacity
Expansion
Number of
Components
to Be Added
Subracks (MPS, EPS)
A1
B1
B1 A1
Data Processing Units

(DPUf)
A2
B2
B2 A2
Data Processing Units

(DPUc, DPUg)
A3
B3
B3 A3
Extended Processing
Units (XPUc)
A4
B4
B4 A4
Interface boards
A5
B5
B5 A5
Cabinets
A6
B6
B6 A6
NOTICE
In this scenario, different versions require different points for attention.
In a capacity expansion for HW69 R11, XPUa, FG2a, and GOUa boards cannot be reused. If IP
interface boards are used only for the Gb interface and TDM networking is used on the entire
network, FG2a and GOUa boards over the Gb interface can be regarded as FG2c boards. FG2a,
GOUa, and FG2c boards have no difference in terms of supporting small-capacity Gb interfaces.
In a capacity expansion for HW69 R13, DPUc, DPUd, XPUa, FG2a, and OIUa boards cannot
be reused. If IP interface boards are used only for the Gb interface and TDM networking is used
on the entire network, FG2a and GOUa boards over the Gb interface can be regarded as FG2c
boards. FG2a, GOUa, and FG2c boards have no difference in terms of supporting small-capacity
Gb interfaces.
----End
l
Incremental algorithm
If an operator wants to keep the original equipment without large-scale modifications to
the legacy network, new boards are used only for newly added sites and carriers. If the new
quotation template does not support mixed insertion of boards and the frontline personnel
Issue 05 (2014-10-29)

86
want to simplify operations, use the original quotation template and the incremental
algorithm.
The core idea is to reuse as much legacy equipment as possible.
The purpose of mixed insertion is to use boards of different specifications in the same
logical or physical interface.
For example:
OIUa and POUc boards can provide TDM-based optical ports on the A interface, but they
have different specifications.
FG2a and FG2c boards can be used for Abis over IP over FE/GE transmission, but they
have different specifications.
For mixed insertion of boards, the old boards used on each interface before capacity
expansion must be calculated.
The procedure for using the incremental algorithm is as follows:
Step 1 Fill in the Unistar calculation table with the quotation parameters of the new hardware version
after the capacity expansion. By doing this, you get the configuration required after the capacity
expansion. In the Dimension Calculator window, you can view the capacity after capacity
expansion.
Step 2 Fill in the Unistar calculation table with the quotation parameters of the original hardware version
before the capacity expansion. By doing this, you can obtain the configurations of each interface
board before the capacity expansion. In the Dimension Calculator window, you can view the
capacity before capacity expansion.
Step 3 Subtract the hardware support capability before capacity expansion from the capacity required
after expansion. By doing this, you can obtain the capacity support capability required for
expansion.
Generally, the traffic volume over the Gb interface is light. One pair of boards can cope even
during a capacity expansion. Therefore, if the traffic volume on the Gb interface is not higher
than 64 Mbit/s in FR transmission mode or 128 Mbit/s in IP transmission mode, set the capacity
increase on the Gb interface to 0.
Issue 05 (2014-10-29)
Item
Name
Configuration
Required After
Capacity
Expansion
Maximum Support
Capability Before
Capacity Expansion
Increased
Support
Capability
Required by
Capacity
Expansion
TRX support
capability
A1
B1
B1 A1
Abis E1 quantity
A2
B2
B2 A2
A CIC quantity
A3
B3
B3 A3
IWF quantity
A4
B4
B4 A4
BHCA
A5
B5
B5 A5
Gb
A6
A6
B6 A6

87
Step 4 Determine the boards required by capacity expansion.

Process the initial result about the required hardware. Based on the configuration principle, DPUf
and DPUg boards work in N+1 backup mode. Therefore, one DPUf and one DPUg need to be
removed from the final hardware list.
Step 5 Calculate whether additional cabinets, subracks, and auxiliary materials are required for capacity
expansion.
----End
5.2 BSC6900 UMTS Hardware Expansion and Upgrade

Configurations
Capacity expansion can be performed using the following methods:
l
Hardware expansion
Configuration of hardware capacity licenses
You can use either of or both of the two methods based on the traffic model and traffic
requirements of the network.
Capacity expansion complies with the "minimum hardware" principle.
5.2.1 Hardware Expansion and Upgrade Configurations

The following table lists the HW69 R11, HW69 R13, HW69 R15, HW69 R16 boards.
Hardware Version
Board
HW69 R11
OMUa, SCUa, GCGa, GCUa, DPUe, SPUb, AEUa, PEUa, AOUc,

FG2c, GOUc, OIUa, POUc, UOIc
HW69 R13
OMUc, SAUc, SCUb, GCGa, GCUa, DPUe, SPUb, NIUa, AEUa,

AOUc, FG2c, GOUc, OIUa, POUc, UOIc
HW69 R15
OMUc, SAUc, SCUb, GCGa, GCUa, DPUe, SPUb, NIUa, AEUa,

PEUc, AOUc, FG2c, GOUc, OIUb, POUc, UOIc, SPUc, GCGb,
GCUb, GOUe
HW69 R16
OMUc, SAUc, SCUb, GCGb, GCUb, DPUe, SPUc, NIUa, AEUa,

PEUc, AOUc, FG2c, GOUe, OIUb, POUc, UOIc
The following table lists the number of components to be added to the BSC6900 UMTS that
adopts the HW69 R16 hardware for capacity expansion.
Issue 05 (2014-10-29)

88
Item
Name
Configuration
Before
Capacity
Expansion
Configuration
After Capacity
Expansion
Number of
Components
to Be Added
Cabinets
A1
B1
B1 A1
MPS
A2
B2
B2 A2
EPS
A3
B3
B3 A3
Clock board
A4
B4
B4 A4
Data Processing Unit
A5
B5
B5 A5
Signaling processing
unit
A6
B6
B6 A6
Interface board
A7
B7
B7 A7
NOTE
A1 through A7 and B1 through B7 indicate the number of components.
5.2.2 Hardware Capacity License Expansion

No new hardware capacity license is added in BSC6900 V900R016C00.
Previous hardware licenses, Hardware Capacity License (165 Mbit/s) and Hardware Capacity
License (300Mbit/s), are inherited.
5.2.3 Examples of Hardware Expansion

Assume that the network configurations before capacity expansion are 6700 Erlang, 670 Mbit/
s (based on the traffic type UL 64 kbit/s/DL 384 kbit/s), 248,000 BHCA (assume that the traffic
model is the balanced traffic model), 360 NodeBs, 1200 cells, and all-IP transmission (optical
GE).
Assume that the network configurations after capacity expansion are 13,400 Erlang, 1340 Mbit/
s (based on the traffic type UL 64 kbit/s/DL 384 kbit/s), 496,000 BHCA (assume that the traffic
model is the balanced traffic model), 720 NodeBs, and 2400 cells.
Table 5-1lists the hardware configurations before and after capacity expansion. The numbers
of hardware components to be added are calculated according to the procedure described in
chapter4.2 BSC6900 UMTS Product Configurations.
Issue 05 (2014-10-29)

89
Table 5-1 Capacity expansion from configuration 1 to configuration 2

Configuration
Number
of
Cabinets
Number
of
Subracks
Number
of DPUe
Boards
Number
of SPUc
Boards
Number
of GOUc/
GOUe
Boards
Configuration 1
(before capacity
expansion)
Configuration 2
(after capacity
expansion)
Number of
components to be
added
The slot configurations are as follows:

NOTE
It is recommended that boards be as evenly as possible distributed in every subrack, following the related
configuration principles.
5.2.4 Examples of Hardware Capacity License Expansion

Assume that the network configurations before capacity expansion are 670 Mbit/s (based on the
traffic type UL 64 kbit/s/DL 384 kbit/s), 248,000 BHCA (assume that the traffic model is the
same as the balanced traffic model), 180 NodeBs, and 600 cells.
Assume that the network configurations after capacity expansion are 1150 Mbit/s (based on the
traffic type UL 64 kbit/s/DL 384 kbit/s) (assume that the capacity needs to be expanded because
Issue 05 (2014-10-29)

90
data throughput in the network increases sharply and that other requirements of the network
remain unchanged).
On the user plane, two DPUe boards are configured. The maximum capacity can reach 1600
Mbit/s by configuring hardware capacity licenses. Therefore, network requirements can be met
by only configuring hardware capacity licenses.
Number of hardware capacity licenses (165 Mbit/s) N_165 = Min (2, Roundup ((1150 Mbit/s
670 Mbit/s)/165)) = 2
670 Mbit/s + 2 x 165 Mbit/s = 1000 Mbit/s < 1150 Mbit/s
Therefore, hardware capacity licenses (300 Mbit/s) need to be configured.
Number of hardware capacity licenses (300 Mbit/s) = Min (N_165, Roundup ((1150 Mbit/s
335 Mbit/s x 2 165 Mbit/s x 2)/300)) = 1
The user plane capacity provided by the system after capacity expansion is: 670 + 165 x 2 + 300
x 1 = 1300 Mbit/s > 1150 Mbit/s, which meets the service requirements.
During capacity expansion, two hardware capacity licenses (165 Mbit/s) and one hardware
capacity license (300 Mbit/s) are added. The following figures show the slot configurations
before and after capacity expansion with hardware unchanged.
Table 5-2 Capacity expansion from configuration 1 to configuration 2

Configuration
Number of
QM1SHW165M00s
Number of
QM1SHW300M00s
Configuration 1 (before capacity

expansion)
Configuration 2 (after capacity

expansion)
Number of capacity licenses to be

added
5.3 BSC6900 GU Hardware Expansion and Upgrade

Configurations
BSC6900 GU new deployment and capacity expansion comply with the following configuration
principles:
Issue 05 (2014-10-29)

91
If the BSC and RNC use different subracks, it is recommended that the RNC subrack serve
as the basic subrack.
The BSC is configured with one to four subracks, whereas the RNC is configured with one
to five subracks.
The total number of BSC and RNC subracks cannot exceed six.
A maximum of two cabinets can be configured, excluding the subracks accommodating

TC. The number of cabinets is calculated as follows:
Number of cabinets = RoundUp [(Number of BSC subracks + Number of RNC subracks)/
3]
If the BSC works in BM/TC separated mode, the MPS must serve as the GSM function
subrack.
In GU mode, NIUa boards, which provide the service awareness function, are configured
for both GSM and UMTS modes.
In GU mode, one SAU board is always configured.
In GU mode, boards of version higher than R13 must be used.
Capacity expansion of the BSC6900 GU involves expanding the capacity of GSM and UMTS
subracks. The general principles for capacity expansion are the same as the principles of new
BSC6900 GU deployment. For details about the capacity expansion methods, see 5.1 BSC6900
GSM Hardware Expansion and Upgrade Configurationsand5.2 BSC6900 UMTS
Hardware Expansion and Upgrade Configurations.
Issue 05 (2014-10-29)

92
6 Spare Parts Configuration
Spare Parts Configuration
6.1 BOM of Spare Parts

The BOM of spare parts is as follows:
BOM_List.xls
6.2 Configuration Principles for Spare Parts

Spare parts configurations are calculated by using the Poisson algorithm (recommended) and
the percentage algorithm.
Use the Poisson algorithm to calculate the number of spare parts, unless otherwise specified by
the customer.
6.2.1 Poisson Algorithm

The Poisson algorithm is integrated in the configurator, and therefore you do not need to
manually calculate the number of spare parts.
The Poisson algorithm is as follows:
where,
l
x indicates the number of configured spare parts.
Pis the damage rate of boards acceptable to an operator. Generally,P(x) is greater than or
equal to 85% and less than 100%.
In the following table, P(x) is 99%.
Issue 05 (2014-10-29)

93
6 Spare Parts Configuration
= 2.71828183
= Number of boards applied on the network x Annual damage rate of boards x

Replenishment period/365
NOTE
l The replenishment period is usually 60 days.

l Quantity of boards applied on the network is the number of boards inserted in both the active BSCs.
l There are 1000 boards (BOM: 02319428) applied on the network.
l The annual damage rates of boards are provided by the spare parts center. Each board has its own
annual damage rate.
For example, the annual damage rate of the board (BOM: 02319428) is 0.005000.
The value of the board (BOM: 02319428) is calculated as follows:
= 1000 x 0.005000 x 60/365 = 0.8219178
According to the Poisson algorithm, the number of spare 02319428 boards is 4.
6.2.2 Percentage Algorithm

If an operator specifies the percentage algorithm, use the percentage algorithm to calculate the
number of spare parts.
6.2.3 Notes
The number of spare parts calculated by using the Poisson algorithm satisfies only basic
requirements of the live network. If the operator requires the service level agreement (SLA), it
is a good practice for the operator to purchase Huawei spare parts management services (SPMSs).
Issue 05 (2014-10-29)

94
7 Appendix
Appendix
7.1 Hardware Version

The following table lists the boards of HW69 R16.
HW
69
R16
OMUc, SAUc, SCUb, GCGb, GCUb, DPUe, SPUc, NIUa, AEUa, PEUc, AOUc,
FG2c, GOUe, OIUb, POUc, UOIc, DPUf, DPUg, XPUc, TNUb, EIUb,
The following table describes the board models and functions.
Issue 05 (2014-10-29)
Model
Description
QM1P00UMPS01
QM1P00UEPS01
QM1M000SPU03
Signal Processing Unit
WP1D000DPU03
Data Processing Unit (335 Mbit/s/3350 Erl)
WP1D000NIU00
WP1D000AEU00
ATM Interface Unit (32 E1)
WP1D000PEU01
IP Interface Unit (32 E1)
WP1D000AOU01
ATM Interface Unit (4 STM-1, Channelized)
WP1D000POU01
IP Interface Unit (4 STM-1, Channelized)
WP1D000UOI01
ATM Interface Unit (8 STM-1, Unchannelized)
WP1D000GOU03
IP Interface Unit (4 GE, Optical)
WP1D000FG201
IP Interface Unit (12 FE/4 GE, Electrical)

95
7 Appendix
Model
Description
WP1D000SAU01
Service Aware Unit
WP1D000GCU02
General Clock Unit
QW1D000GCG02
GPS&Clock Processing Unit
WP1D000DPU05
CS Data Processing Unit (1920CIC/3840 IWF

(TDM&IP)/7680IWF(IP&IP))
WP1D000DPU06
PS Data Processing Unit (1024 PDCH)
WP1D000DPU03
PS Data Processing Unit (1024 PDCH)
WP1D000NIU00
WP1D000XPU03
Expansion Processing Unit (640)
WP1D000EIU01
TDM Interface Unit (32 E1/T1)
WP1D000OIU01
TDM Interface Unit (1 STM-1,Channelized)
7.2 GSM Configuration Reference

7.2.1 GSM Traffic Model
The BSC BHCA specifications in this document are based on a Huawei GSM traffic model.
Table 7-1 lists key parameters.
Table 7-1 Key parameters under Huawei GSM traffic volume
Issue 05 (2014-10-29)
Parameter Name
Parameter Value
voice traffic/sub/BH (Erlang)
0.02
voice call duration (seconds)
60
percent of Mobile originated calls
50%
percent of Mobile terminated calls
50%
average LUs/sub/BH
1.2
average IMSI Attach/sub/BH
0.15
average IMSI Detach/sub/BH
0.15
average MOCs/sub/BH
0.6
average MTCs/sub/BH
0.6
MR report/sub/BH
144

96
7 Appendix
Parameter Name
Parameter Value
average MO-SMSs /sub/BH
0.6
average MT-SMSs /sub/BH
average intra-BSC HOs /sub/BH
1.1
average inter-BSC HOs /sub/BH
0.1
paging retransfer /sub/BH
0.56
Grade of Service (GoS) on Um interface
0.01
Grade of Service (GoS) on A interface
0.001
percent of HR (percent of Um interface resources occupied by HR

voice call)
50%
Uplink TBF Est & Rel / Second/TRX
1.75
Downlink TBF Est & Rel / Second/TRX
0.9
PS Paging / Sub/BH
1.25
Hardware capacity configuration in BM/TC combined mode

1.
Table 7-2lists the capacity of a BSC6900 GSM in TDM transmission mode. In this table,
the BSC6900 GSM is configured with HW69R16 boards and works in BM/TC combined
mode.
Table 7-2 Capacity of a BSC6900 GSM in TDM transmission mode (HW69 R16 boards,
BM/TC combined mode)
Typical Configuration
1 MPS
1 EPS
1 MPS+1
EPS
1 MPS+2
EPSs
Maximum number of
cabinets
Maximum number of
equivalent BHCA (k)
1,750
2,625
4,375
5,900
Maximum traffic volume

(Erlang)
6500
9750
16,250
24,000
Maximum number of TRXs
1024
1536
2560
4096
Maximum number of
activated packet data
channels (PDCHs)
(MCS-9)
4096
6144
10,240
16,384
Specifications
Issue 05 (2014-10-29)

97
7 Appendix
2.
Table 7-3 lists the capacity of a BSC6900 GSM. In this table, the BSC6900 GSM works
in Abis over TDM and A over IP mode.
Table 7-3 Capacity of a BSC6900 GSM (HW69 R16 boards, Abis over TDM and A over
IP mode)
1 MPS
1 EPS
1 MPS+1
EPS
1 MPS+2
EPSs
Maximum number of
cabinets
Maximum number of
equivalent BHCA (k)
1,750
3,500
5,250
5,900

(Erlang)
6500
13,000
19,500
24,000
1024
2048
3072
4096
Maximum number of
activated PDCHs (MCS-9)
4096
8192
12,288
16,384
Specifications
3.
Table 7-4 lists the capacity of a BSC6900 GSM. In this table, the BSC6900 GSM works
in Abis over IP and A over IP mode.
Table 7-4 Capacity of a BSC6900 GSM (HW69 R16 boards, Abis over IP and A over IP
mode)
1 MPS
1 EPS
1 MPS+1
EPS
1 MPS+2
EPSs
Maximum number of
cabinets
Maximum number of
equivalent BHCA (k)
1,750
6,125
7,875
11,000

(Erlang)
6500
22,750
29,250
45,000
Maximum number of
TRXs
1024
3584
4608
8192
Maximum number of
4096
14,336
18,432
32,768
Specifications
Hardware capacity configuration in BM/TC ceparated mode

1.
Issue 05 (2014-10-29)
Table 7-5lists the capacity of a BSC6900 GSM. In this table, the BSC6900 GSM is
configured with HW69R16 boards and works in BM/TC separated mode with the Abis
interface not using IP transmission.
98
7 Appendix
Table 7-5 Capacity of a BSC6900 GSM (HW69 R16 boards, BM/TC separated mode, Abis
interface not using IP transmission)
1 MPS+1
TCS
1 EPS+1
TCS
1 MPS+1
EPS+2
TCS
1 MPS+2
EPSs+3
TCSs
Maximum number of
cabinets
Maximum number of
equivalent BHCA (k)
1,750
2,625
4,375
5,900

(Erlang)
6500
9750
16,250
24,000
1024
1536
2560
4096
Maximum number of
4096
6144
10,240
16,384
Specifications
2.
Table 7-6lists the capacity of a BSC6900 GSM. In this table, the BSC6900 GSM is
configured with HW69R16 boards and works in BM/TC separated mode and in Abis over
IP mode.
Table 7-6 Capacity of a BSC6900 GSM (HW69 R16 boards, BM/TC separated mode, Abis over
IP mode)
1 MPS+1
TCS
1 EPS+1
TCS
1 MPS+1
EPS+3
TCSs
1 MPS+2
EPSs+3
TCSs
Maximum number of
cabinets
Maximum number of
equivalent BHCA (k)
1,750
3,500
5,250
5,900

(Erlang)
6500
13,000
19,500
24,000
1024
2048
3072
4096
Maximum number of
4096
8192
12,288
16,384
Specifications
Issue 05 (2014-10-29)

99
7 Appendix
7.2.2 GSM Board Specifications

Table 7-7 Board specifications
Parameter Name
Meaning
Specificati
ons
Board
TrxPerXPUaWithMPU
TRX support capability of

the XPUa (with the MPU)
270
XPUa
BHCAPerXPUaWithMPU
BHCA supported by each

pair of XPUa boards (with
MPUs)
492,000 for
GBTS
XPUa
ErlPerXPUaWithMPU
Traffic supported by each

pair of XPUa boards (with
MPUs) (for reference only,
not used as a parameter for
calculating the number of
required boards)
1720
XPUa
TrxPerXPUaWithoutMPU

each pair of common XPUa
boards
360
XPUa
BHCAPerXPUaWithoutMPU

pair of common XPUa
boards
656,000 for
GBTS
XPUa
ErlPerXPUaWithoutMPU

pair of common XPUa
boards (for your reference
only, not used as a
calculation criterion)
2300
XPUa
TrxPerXPUc

the XPUc
640
XPUc
BHCAPerXPUc

pair of XPUc boards
1,050,000
for GBTS
XPUc:
BHCA
445,000 for
eGBTS
590,000 for
eGBTS
950,000 for
eGBTS
Issue 05 (2014-10-29)
ErlPerXPUc

pair of XPUc boards (for
your reference only, not
used as a calculation
criterion)
3900
XPUc:
Erlang
PDCHNoPerDPUd
PDCH support capability

of the DPUd
1024
DPUd

100
Issue 05 (2014-10-29)
7 Appendix
Parameter Name
Meaning
Specificati
ons
Board
PDCHNoPerDPUg
PDCH support capability

of the DPUg
1024
DPUg
IWFNoPerDPUc
IWF flow processing

capability of the DPUc
3740
DPUc
TCNoPerDPUc
TC processing capability of
the DPUc
960
DPUc
IWFNoPerDPUf(TDM*IP)
IWF flow processing

capability of the DPUf
(TDM and IP)
3840
DPUf
IWFNoPerDPUf(IP*IP)
IWF flow processing

capability of the DPUf (IP
and IP)
7680
DPUf
TCNoPerDPUf
TC processing capability of
the DPUf
1920
DPUf
STM1PortPerPOUc
Number of STM-1 ports on

the POUc
POUc
TRXHRPerPOUcTDM
Number of TRXs
supported by the POUc in
TDM transmission mode
Active/
Standby
mode: 512
POUc: TDM
ACICPerPOUcTDM
Number of CIC circuits

over the A interface
supported by the POUc (the
TDM over packet
technique is used only on
the DPUf) in TDM
transmission mode
7680
POUc: TDM
ACICPerPOUcTDM

over the A interface
supported by the POUc
(only DPUc is used or
DPUc and DPUf are used
together) in TDM
transmission mode
3906
POUc: TDM
AterCICPerPOUcTDM

over the Ater interface
7168
POUc: TDM
TRXPerPOUcIP
Number of TRXs
over the Abis interface in IP
transmission mode
2048
POUc: IP

101
Issue 05 (2014-10-29)
7 Appendix
Parameter Name
Meaning
Specificati
ons
Board
ACICPerPOUcIP
Number of CICs supported

by the POUc over the A
interface in IP transmission
mode
23,040
POUc: IP
GbTputPerPOUcFR
Throughput (Mbit/s)
over the Gb interface in FR
transmission mode
504
POUc: Gb
FR
E1PortPerEIUa/E1PortPerEIUb
Number of ports supported

by the EIUa/EIUb
32
EIUa/EIUb:
TDM
TRXHRPerEIUa/
TRXHRPerEIUb
Number of half-rate TRXs

over the Abis interface
supported by the EIUa/
EIUb
Active/
Standby
mode: 384
EIUa/EIUb:
TDM
AterCICPerEIUa/
AterCICPerEIUb

EIUb over the Ater
interface
3840
EIUa/EIUb:
TDM
ACICPerEIUa/ACICPerEIUb

EIUb over the A interface
960
EIUa/EIUb:
TDM
STM1PortPerOIUa/
STM1PortPerOIUb

by the OIUa/OIUb
OIUa/OIUb:
TDM
TRXHRPerOIUa/
TRXHRPerOIUb
Number of half-rate TRXs

supported by the OIUa/
OIUb over the Abis
interface
Active/
standby
mode: 384
OIUa/OIUb:
TDM
AterCICPerOIUa/
AterCICPerOIUb

by the OIUa/OIUb over the
Ater interface
7168
OIUa/OIUb:
TDM
ACICPerOIUa/ACICPerOIUb

by the OIUa/OIUb over the
A interface
1920
OIUa/OIUb:
TDM
E1PortPerPEUa/
E1PortPerPEUc

by the PEUa/PEUc
32
PEUa/PEUc
GbTputPerPEUaFR/
GbTputPerPEUcFR
Throughput (Mbit/s)
supported by the PEUa/
PEUc over the Gb interface
in FR transmission mode
64
PEUa/
PEUc: Gb
FR

102
Issue 05 (2014-10-29)
7 Appendix
Parameter Name
Meaning
Specificati
ons
Board
TRXPerPEUaIP/
TRXPerPEUcIP
Number of TRXs
supported by the PEUa/
PEUc over the Abis
mode
384
PEUa/
PEUc: IP
ACICperPEUaIP/
ACICperPEUcIP

by the PEUa/PEUc over the
A interface in IP
transmission mode
6144
PEUa/
PEUc: IP
GEPortPerFG2c
Number of GE ports
supported by the FG2c
FG2c
FEPortPerFG2c
Number of FE ports
supported by the FG2c
12
FG2c
GEPortPerGOUc
Number of GE ports
supported by the GOUc
GOUc
GEPortPerGOUe
Number of GE ports
supported by the GOUe
GOUe
GbTputPerFG2c
Throughput (Mbit/s)
supported by the FG2c/
GOUc/GOUe over the Gb
mode
1024
FG2c/
GOUc/
GOUe
TRXNoPerFG2c
Number of TRXs
GOUc/GOUe over the
Abis interface in IP
transmission mode
2048
FG2c/
GOUc/
GOUe
ACICPerFG2c

by the FG2c/GOUc/GOUe
over the A interface in IP
transmission mode
23,040
FG2c/
GOUc/
GOUe
LogicalPortPerFG2c
Number of logical ports

GOUc/GOUe in IP
transmission mode
490
FG2c/
GOUc/
GOUe
MaxSubrackTC
Maximum number of
supported TC subracks
TC subrack
MaxCICPerSubrackTC

supported by each TC
subrack
10,240
TC subrack

103
7 Appendix
Parameter Name
Meaning
Specificati
ons
Board
Max64KNo7linkPerBSC
Maximum number of 64
kbit/s signaling links
supported by each BSC
4 x 16
BSC/No.7
MaxHSLNo7linkPerBSC
Maximum number of highspeed signaling links

supported by each BSC
4x8
BSC/No.7
MaxInterSubrackTDMSwitch
Maximum switching
capability between
subracks of the BSC. By
default, two highways can
be configured between
every two subracks and the
switching capability of
each highway is 4000. A
maximum of three
highways can be
configured between two
subracks.
4000 x 2
BSC/LVDS
7.2.3 GSM Board Usage Efficiency

collectively considering the capacity on various aspects (including BHCA capacity, TRX
capacity, CIC capacity, and bandwidth capacity). The specification for a board indicates the
capability that a board can stably run for a long period.
When a board is processing services, its bandwidth capacity, service parsing and forwarding
capacity, and signaling parsing and forwarding capacity must be taken into consideration.
Therefore, Huawei uses the board usage efficiency to represent the board capability. The board
usage efficiency is calculated using the following formula:
Board usage efficiency = Traffic volume on the BSC/Maximum board specification
where,
Traffic volume on the BSC can be the BHCA capacity, TRX capacity, or any other board
capacity.
For example, if the GOUc board supports a maximum of 23,040 CICs over the A interface, and
the number of serving CICs is 10,000, the GOUc board usage is 43.4% (10,000/23,040 x 100%).
7.2.4 Ater RSL Configuration Calculation Tool

Ater_RSL_Configuration_Calculation_Tool.xls
Issue 05 (2014-10-29)

104
7 Appendix
7.2.5 Suggestions for Lb Interface Configuration

The Lb interface bandwidth is determined by the SMLC. The BSC provides transmission and
signaling forwarding. If the Lb interface bandwidth requirement is not specified by the SMLC,
the maximum bandwidth should be configured.
If the BSC is connected to the SMLC by using TDM transmission, the maximum Lb interface
bandwidth is calculated using the following formula:
Formual for low-speed SS7 links: 16 x 64 kbit/s = 1 Mbit/s
Formula for narrowband SS7 signaling links with a single signaling point: 16 x 64 kbit/s = 1
Mbit/s
Formula for wideband SS7 signaling links with a single signaling point: 2 x 2 Mbit/s = 4 Mbit/
s (the maximum Lb interface bandwidth consists of eight signaling links, and the total bandwidth
cannot exceed 4 Mbit/s)
7.3 UMTS Configuration Reference

7.3.1 UMTS Traffic Model
The BSC6900 UMTS supports the flexible configuration of control plane and user plane data
in different scenarios. In each scenario, the capacity configured for the BSC6900 UMTS depends
on actual traffic models.
There are three traffic models for the BSC6900 UMTS:
l
Balanced traffic model
This model applies when voice services and data services are balanced in a network.
l
High-PS traffic model
This model applies when subscribers use much more data services than voice services. In this
model, the average PS throughput per user is high.
l
Smartphone traffic model

In this model, control plane signaling is frequently exchanged and small-sized packets are
transmitted on the user plane.
The capacity under UMTS BSC6900 typical configurations in the balanced traffic model, highPS traffic model, and smartphone traffic model are described as follows:
l
Balanced traffic model
Table 7-8 Balanced traffic model for the BSC6900 UMTS (per user during busy hours)
Issue 05 (2014-10-29)
Item
Specificatio
ns
Description
Voice Traffic per CS voice

subscriber in BH
20 mE
AMR voice RAB, 0.96 BHCA

105
7 Appendix
Item
Specificatio
ns
Description
CS data traffic per CS data

subscriber in BH
1.5 mE
UL/DL 64 kbit/s CS RAB, 0.04 BHCA
PS throughput (Including
R99 and HSPA, UL+DL) per
PS subscriber in BH
4500 bit/s
2 BHCA, UL 64 kbit/s/DL 384 kbit/s
Proportion of soft handovers
30%
The number of calls(in percent) with 2

hangover legs(others have 1 leg)

(SHO) (times/call)
Average soft handover times per CS call

(SHO) (times/call)
Average soft handover times per PS call
NAS signaling per subscriber

per BH (times)
3.6
Number of NAS procedures between the CN

and UEs, including location area updates,
IMSI attach/detach occurrences, routing
area updates, GPRS attach/detach
occurrences, and SMSs
Iur-to-Iub traffic ratio
8%
Table 7-9lists the capacity of a BSC6900 UMTS in typical configurations. In this table, the
BSC6900 UMTS is configured with HW69R16boards under the balanced traffic model.
Table 7-9 Capacity of a BSC6900 UMTS in typical configurations (HW69 R16 boards)
Number of
Subscribers
CS Voice
Service
Capacity
(Erlang)
PS Service
Capacity (Iub
UL+DL) (Mbit/
s)
BHCA
Number
of Active
Users
Number
of Online
Users
1,760,000
45,738
7920
5,300,000
229,000
869,000
NOTE
l The CS voice service capacity and PS service capacity can reach the maximum at the same time.
l Number of Subscribers means the number of users connected to the network in one busy hour.
l Number of Active Users refers to the number of users that are simultaneously in the activated states,
including the CELL_DCH and CELL_FACH states.
l Number of Online Users refer to the users that are simultaneously online, including the users in the
CELL_DCH, CELL_FACH, CELL_PCH, and URA_PCH states..
Issue 05 (2014-10-29)
High-PS traffic model

106
7 Appendix
Table 7-10 High-PS traffic model for the BSC6900 UMTS (per user during busy hours)
Item
Specificati
ons
Description
CS voice traffic volume
3 mE
AMR speech service, 0.144 BHCA
CS data traffic volume
0.2 mE
UL/DL 64 kbit/s CS data service, 0.0053

BHCA
PS throughput
43,500 bit/s
UL 64 kbit/s/DL 384 kbit/s, 3 BHCA
Proportion of soft
handovers
30%
Proportion of calls using two or more

channels simultaneously to all calls

(SHO) (times/call)
Average number of handovers per CS call

(SHO) (times/call)
Average number of handovers per CS call
NAS signaling per

3.6
Number of NAS procedures between the

CN and UEs, including location area
updates, IMSI attach/detach occurrences,
routing area updates, GPRS attach/detach
occurrences, and SMSs
8%
BSC6900 UMTS is configured with HW69R16 boards under the high-PS traffic model.
Number of
Subscriber
s
CS Voice
Service
Capacity
(Erlang)
PS Service
Capacity (Iub
UL+DL)
(Mbit/s)
BHCA
Number of
Active
Users
Number of
Online
Users
925,000
3600
40,200
2,900,000
243,000
567,000
NOTE
The CS voice service capacity and PS service capacity can reach the maximum at the same
time.
SPUc specifications in high-PS traffic model are 112,000 BHCA.
Number of Subscribers means the number of users connected to the network in one busy
hour.
Number of ActiveUsers refers to the number of users that are simultaneously in the
activated states, including the CELL_DCH and CELL_FACH states.
Issue 05 (2014-10-29)

107
7 Appendix
Number of Online Users refer to the users that are simultaneously online, including the
users in the CELL_DCH, CELL_FACH, CELL_PCH, and URA_PCH states.
Smartphone traffic model
Table 7-12 Smartphone traffic model for the BSC6900 UMTS

Item
Specificatio
ns
Description
Voice Traffic per CS

voice subscriber in BH
30 mE
AMR voice RAB, 0.7 CS BHCA
PS throughput (Including
R99 and HSPA, UL+DL)
per PS subscriber in BH
1600 bps
8 PS BHCA
Proportion of soft
handover
34%
Number of calls with two or more hangover

legs
Handover times per CS

call (SHO) (times/call)
Average soft handover times per CS call
Handover times per PS

call (SHO) (times/call)
Average soft handover times per PS call
Inter-PDCH handovers
per PS call
2.3
Including all switching between different

connected RRC states and different channels
per PS call
NAS signaling per

2.8
Number of NAS procedures between the CN

and UEs, including location area updates, IMSI
attach/detach occurrences, routing area
updates, GPRS attach/detach occurrences, and
SMSs
8%
BSC6900 UMTS is configured with HW69R16 boards under the smartphone traffic model.
Issue 05 (2014-10-29)
Number of
Subscribers
CS Voice
Service
Capacity
(Erlang)
PS Service
Capacity (Iub
UL+DL)
(Mbit/s)
BHCA
Number
of Active
Users
Number
of Online
Users
1,440,000
47,000
1860
12,800,000
230,000
869,000

108
7 Appendix
NOTE
l The CS voice service capacity and PS service capacity can reach the maximum at the same time.
l SPUc specifications in High-PS traffic model are 266,000 BHCA.
l Number of Subscribers means the number of users connected to the network in one busy hour.
l Number of Active Users refers to the number of users that are simultaneously in the activated states,
including the CELL_DCH and CELL_FACH states.
l Number of Online Users refer to the users that are simultaneously online, including the users in the
CELL_DCH, CELL_FACH, CELL_PCH, and URA_PCH states.
7.3.2 UMTS Hardware Specifications

Table 7-14 UMTS board specifications
Issue 05 (2014-10-29)
Parameter
Parameter Description
Specifications
Board
BHCAPerSPUa
BHCA supported by each pair of

SPUa boards
80,000
SPUa
NodebPerSPUa
Number of NodeBs supported by

each pair of SPUa boards
100
SPUa
CellPerSPUa
Number of cells supported by each

pair of SPUa boards
300
SPUa
ActiveUsersPerSPUa
Number of active users supported by

4800
SPUa
OnlineUsersPerSPUa
Number of online users supported by

12,000
SPUa
BHCAPerSPUb
BHCA supported by each pair of

SPUc/SPUb boards
124,000
SPUc/
SPUb
NodebPerSPUb

each pair of SPUc/SPUb boards
180
SPUc/
SPUb
CellPerSPUb

pair of SPUc/SPUb boards
600
SPUc/
SPUb
ActiveUsersPerSPUb

9600
SPUc/
SPUb
OnlineUsersPerSPUb
Number of online users supported by

24,000
SPUc/
SPUb
CellPerDPUb

DPUb board
150
DPUb
ErlPerDPUb
Erlang supported by each DPUb

board
1800
DPUb
ActiveUsersPerDPUb

each DPUb board
3300
DPUb

109
7 Appendix
Parameter
Specifications
Board
CellPerDPUe

DPUe board
300
DPUe
ErlPerDPUe
Erlang supported by each DPUe

board
3350
DPUe
PsThtPerDPUe
Real PS throughput(Mbit/s)
supported by each DPUe board
x=PS Rab mean

data rate in active
state; y =
PsThtPerDPUe.
DPUe
If x in [0, 16], y=
5.625*x
If x in [16, 40],
y=90+6.67*x;
If x in [40, 64],
y=250+2.08*x;
If x in [64, 128],
y=300+2.03*x;
If x in [128, 196],
y=430+ 1.47*x;
If x in [196, 448],
y=530+ 1.07*x;
If x in [448, ],
y=800
Issue 05 (2014-10-29)
ActiveUsersPerDPUe

each DPUe board
5880
DPUe
MaxInterSubrackSwitchSCUa
Inter-subrack switching capability

(Gbit/s) of each pair of SCUa boards
SCUa
MaxInterSubrackSwitchSCUb
Inter-subrack switching capability

(Gbit/s) of each pair of SCUb boards
40
SCUb
NodebPerAOUc

each AOUc board
500
AOUc
ErlPerAOUc
Erlang supported by each AOUc

board
18,000
AOUc
IubUlPsThrPerAOUc
PS UL throughput (Mbit/s)
supported by the AOUc board
functioning as the Iub interface board
300
AOUc
IubDlPsThrPerAOUc
PS DL throughput (Mbit/s)
300
AOUc

110
Issue 05 (2014-10-29)
7 Appendix
Parameter
Specifications
Board
IubUlDlPsThrPerAOUc
PS throughput (Mbit/s) supported by

the AOUc board functioning as the
Iub interface board
600
AOUc
IuUlPsThrPerAOU
c
functioning as the Iu interface board
350
AOUc
IuDlPsThrPerAOU
c
350
AOUc
IuUlDlPsThrPerAOUc

the AOUc board functioning as the Iu
interface board
700
AOUc
NodebPerUOIc

each UOIc board
500
UOIc
ErlPerUOIc
Erlang supported by each UOIc

board
18,000
UOIc
IubUlPsThrPerUO
Ic
supported by the UOIc board
800
UOIc
IubDlPsThrPerUO
Ic
800
UOIc
IubUlDlPsThrPerUOIc

the UOIc board functioning as the Iub
interface board
1200
UOIc
IuUlPsThrPerUOI
c
900
UOIc
IuDlPsThrPerUOI
c
900
UOIc
IuUlDlPsThrPerUOIc

the UOIc board functioning as the Iu
interface board
1800
UOIc
NodebPerGOUc/
NodebPerFG2c

each GOUc/GOUe/FG2c board
500
GOUc/
GOUe/
FG2c
ErlPerGOUc/
ErlPerFG2c
Erlang supported by each GOUc/

GOUe/FG2c board
18,000
GOUc/
GOUe/
FG2c

111
Issue 05 (2014-10-29)
7 Appendix
Parameter
Specifications
Board
SessionsPerGOUc/
SessionsPerFG2c
IuPS Setup&Reconfigure Sessions

number supported by each GOUc/
GOUe/FG2c board
5000
GOUc/
GOUe/
FG2c
IubUdpPerGOUc/
IubUdpPerFG2c
Iub UDP number supported by each

GOUc/GOUe/FG2c board
129,000
GOUc/
GOUe/
FG2c
IuPSTeidPerGOUc
/IuPSTeidPerFG2c
Iu-PS TEID number supported by

each GOUc/GOUe/FG2c board
200,000
GOUc/
GOUe/
FG2c
IubUlPsThrPerGOUc/
IubUlPsThrPerFG
2c
supported by the GOUc/GOUe/FG2c
board functioning as the Iub interface
board
2600
GOUc/
GOUe/
FG2c
IubDlPsThrPerGOUc/
IubDlPsThrPerFG
2c
board functioning as the Iub interface
board
2600
GOUc/
GOUe/
FG2c
IubUlDlPsThrPerGOUc/
IubUlDlPsThrPerF
G2c

the GOUc/GOUe/FG2c board
2600
GOUc/
GOUe/
FG2c
IuUlPsThrPerGOU
c/
IuUlPsThrPerFG2
c
board functioning as the Iu interface
board
3200
GOUc/
GOUe/
FG2c
IuDlPsThrPerGOU
c/
IuDlPsThrPerFG2
c
board functioning as the Iu interface
board
3200
GOUc/
GOUe/
FG2c
IuUlDlPsThrPerGOUc/
IuUlDlPsThrPerF
G2c

the GOUc/GOUe/FG2c board
3200
GOUc/
GOUe/
FG2c
PortNumGOUe/
PortNumFG2c
Number of ports supported by

GOUc/GOUe/FG2c
GOUc/
GOUe/
FG2c
Stm1PortNumAO
Uc
Number of STM-1 ports supported

by AOUc
AOUc
E1PortNumAOUc/
T1PortNumAOUc
Number of E1/T1 ports supported by

AOUc
252/336
AOUc

112
Issue 05 (2014-10-29)
7 Appendix
Parameter
Specifications
Board
Stm1PortNumUOI
c

by UOIc
UOIc
Stm1PortNumPO
Uc

by POUc
POUc
E1PortNumPOUc/
T1PortNumPOUc
Number of E1/T1 ports supported by

POUc
252/336
POUc
PsThtPerNIUa

each NIUa board
3200
NIUa

113
8 Acronyms and Abbreviations
Acronyms and Abbreviations
Table 8-1 Acronyms and abbreviations
Issue 05 (2014-10-29)
Acronym or Abbreviation
Full Name
AMR
Adaptive Multirate
ATM
asynchronous transfer mode
BH
busy hour
CN
core network
GPS
Global Positioning System
Iu
Interface between RNC and CN
Iub
Interface between RNC and NodeB
Iur
Interface between RNC and RNC
NodeB
Base station in WCDMA networks
RNC
radio network controller
MPS
main processing subrack
EPS
mxtended processing subrack
STM-1
synchronous transfer mode 1
WB-AMR
wide band adaptive multirate

114

BSC6900 Configuration Principle (Global) (V900R016C00 - 05) (PDF) - en

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSC6900 Configuration Principle (Global) (V900R016C00 - 05) (PDF) - en

Uploaded by

Copyright:

Available Formats

SRAN9.0&GBSS16.0&RAN16.

Configuration Principles (Global)

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

Configuration Principles (Global)

Huawei Proprietary and Confidential

Configuration Principles (Global)

5 Expansion and Upgrade Configurations.................................................................................68

6 Spare Parts Configuration..........................................................................................................93

8 Acronyms and Abbreviations.................................................................................................114

Huawei Proprietary and Confidential

Configuration Principles (Global)

This chapter describes changes in different document versions.

l Added descriptions about new boards SPUc, GOUe, GCGb,

Huawei Proprietary and Confidential

Configuration Principles (Global)

l Added the description that SPUb and SPUc boards, GOUc

l Modified the method of calculating the number of DPUf

Huawei Proprietary and Confidential

Configuration Principles (Global)

l Added the impacts of key quality indicator (KQI) features

Converted some descriptions to tables. For details, see 4.2.7

2.3 Laws and Regulations

l Modified the method of calculating the number of SPUc

Huawei Proprietary and Confidential

Configuration Principles (Global)

l Added descriptions about board replacement. For details,

Laws and Regulations.

l 2.3 Laws and Regulations

l Modified the configuration principles for XPUc processing

Huawei Proprietary and Confidential

Configuration Principles (Global)

Huawei Proprietary and Confidential

Configuration Principles (Global)

2.2 Version Difference

Huawei Proprietary and Confidential

Configuration Principles (Global)

2.2.2 BSC6900 UMTS

2.3 Laws and Regulations

2.3.2 Export Control

Huawei Proprietary and Confidential

Configuration Principles (Global)

Do not sell the

Huawei Proprietary and Confidential

Configuration Principles (Global)

Figure 3-2 shows the configuration of a BSC6900 cabinet.

Huawei Proprietary and Confidential

Configuration Principles (Global)

Table 3-1 describes the BSC6900 specifications.

l Maximum number of cabinets: 2

l Maximum number of cabinets: 2

Huawei Proprietary and Confidential

Configuration Principles (Global)

l Maximum GSM specifications (all-TDM transmission for

Dimensions of the BSC6900 N68E-22 cabinet (H x W x D): 2200 mm x

Huawei Proprietary and Confidential

Configuration Principles (Global)

l BSC6900 specifications are not equal to the sum of board specifications.