BSC6900 Configuration Principle (Global) (V900R017C10 06) (PDF) - EN PDF

SRAN10.1&GBSS17.1&RAN17.
1 BSC6900
Configuration Principle (Global)
Issue 06
Date 2016-03-31
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2016. 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 06 (2016-03-31) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
SRAN10.1&GBSS17.1&RAN17.1 BSC6900
Configuration Principle (Global) Contents
Contents
1 Change History.............................................................................................................................. 1
2 Introduction.................................................................................................................................... 5
2.1 Overview........................................................................................................................................................................ 5
2.2 Version Differences........................................................................................................................................................ 5
3 Application Overview.................................................................................................................. 8
4 Product Configurations.............................................................................................................. 12
4.1 BSC6900 GSM Product Configurations.......................................................................................................................12
4.1.1 Hardware Specification Redundancy........................................................................................................................ 13
4.1.2 Cabinets..................................................................................................................................................................... 13
4.1.3 Subracks.....................................................................................................................................................................14
4.1.4 Hardware Capacity License.......................................................................................................................................16
4.1.5 Service Processing Units........................................................................................................................................... 16
4.1.6 Interface Boards.........................................................................................................................................................23
4.1.7 Clock Boards............................................................................................................................................................. 29
4.1.8 General Principles for Board Configurations............................................................................................................ 29
4.1.9 Auxiliary Materials....................................................................................................................................................31
4.1.10 Example BSC6900 GSM Configuration................................................................................................................. 32
4.1.11 BSC6900 GSM Recommended Capacity for Delivery........................................................................................... 34
4.2 BSC6900 UMTS Product Configurations.................................................................................................................... 35
4.2.1 Cabinets..................................................................................................................................................................... 35
4.2.2 Subracks.....................................................................................................................................................................36
4.2.3 Hardware Capacity License.......................................................................................................................................38
4.2.4 Service Processing Units........................................................................................................................................... 41
4.2.5 Interface Boards.........................................................................................................................................................48
4.2.6 Clock Boards............................................................................................................................................................. 56
4.2.7 General Principles for Board Configurations............................................................................................................ 56
4.2.8 Auxiliary Material Configurations............................................................................................................................ 57
4.2.9 Restrictions on Inter-Subrack Switching................................................................................................................... 58
4.2.10 Example of Typical BSC6900 UMTS Configuration..............................................................................................59
4.2.11 BSC6900 UMTS Recommended Capacity for Delivery.........................................................................................66
4.3 BSC6900 GU Product Configurations......................................................................................................................... 67
4.4 Built-in ECO6910 Product Configurations.................................................................................................................. 67
Issue 06 (2016-03-31) Huawei Proprietary and Confidential ii

Configuration Principle (Global) Contents
5 Hardware Expansion and Upgrade Configurations............................................................. 69

5.1 BSC6900 GSM............................................................................................................................................................. 69
5.1.1 Hardware Expansion and Upgrade Configurations................................................................................................... 69
5.1.2 Hardware Capacity License Expansion..................................................................................................................... 82
5.1.3 Examples of Hardware Expansion............................................................................................................................ 82
5.2 BSC6900 UMTS...........................................................................................................................................................84
5.2.1 Hardware Expansion and Upgrade Configurations................................................................................................... 85
5.2.2 Hardware Capacity License Expansion..................................................................................................................... 86
5.2.3 Examples of Hardware Expansion............................................................................................................................ 86
5.2.4 Examples of Hardware Capacity License Expansion................................................................................................87
5.3 BSC6900 GU................................................................................................................................................................ 88
6 Spare Parts Configurations........................................................................................................89

6.1 BOM of Spare Parts......................................................................................................................................................89
6.2 Configuration Principles for Spare Parts...................................................................................................................... 89
6.2.1 Poisson Algorithm..................................................................................................................................................... 89
6.2.2 Percentage Algorithm................................................................................................................................................ 90
6.2.3 Notes.......................................................................................................................................................................... 90
7 Appendix....................................................................................................................................... 91
7.1 GSM Configuration Reference..................................................................................................................................... 91
7.1.1 GSM Traffic Model................................................................................................................................................... 91
7.1.2 GSM Board Specifications........................................................................................................................................ 96
7.1.3 GSM Board Usage Efficiency................................................................................................................................. 100
7.1.4 Ater RSL Configuration Calculation Tool...............................................................................................................100
7.1.5 Suggestions for Lb Interface Configuration............................................................................................................ 100
7.2 UMTS Configuration Reference................................................................................................................................ 101
7.2.1 UMTS Traffic Model...............................................................................................................................................101
7.2.2 UMTS Hardware Specifications..............................................................................................................................105
7.3 List of Board Power Consumption............................................................................................................................. 110
8 Acronyms and Abbreviations................................................................................................. 113
Issue 06 (2016-03-31) Huawei Proprietary and Confidential iii

Configuration Principle (Global) 1 Change History
1 Change History
This chapter describes changes in different document versions.
06 (2016-03-31)
Compared with Issue 05 (2015-12-31), this issue includes the following changes.
Change Description
Added Added 7.3 List of Board Power Consumption.

Added the description about single-subrack power consumption. For
details, see 4.1.3 Subracks.
Modified Modified the UMTS processing capability of BSC6900 GU. For details,
see 3 Application Overview.
Added the description that the POUc board specification varies according
to the DPU configuration. For details, see 4.1.6 Interface Boards.
Modified the formal for calculating the number of SPUc boards, changed
the default proportion of SRB over DCH users to 82%, and changed the
NIU configuration (from N+1 to N). For details, see 4.2.4 Service
Processing Units and 4.2.10 Example of Typical BSC6900 UMTS
Configuration.
Deleted Deleted the BSC_Power_Consumption_Tool.xls attachment from 4.1.2

Cabinets and 4.2.1 Cabinets.
Deleted the description that SAU boards are delivered by default in GO
mode. For details, see 4.1.3 Subracks.
05 (2015-12-31)
Change Description
Added Added 4.1.1 Hardware Specification Redundancy.
Issue 06 (2016-03-31) Huawei Proprietary and Confidential 1

Change Description
Modified Modified the method for calculating the number of XPUs required by
IBCA. For details, see 4.2.4 Service Processing Units.
Reorganized 4.4 Built-in ECO6910 Product Configurations.
Deleted Deleted descriptions about laws and regulations because this product
complies with the uniform Huawei regulations.
Deleted descriptions about the impacts of traffic models on product
configurations because such impacts are subject to network conditions.
Moved the hardware list to the "Version Differences" section.
04 (2015-09-10)
Change Description
Added None
Modified Added the description that an interface board cannot be shared by multiple
interfaces. For details, see 4.1.6 Interface Boards.
Deleted None
03 (2015-06-30)
Change Description
Added None
Modified Deleted descriptions about N+1 backup because NIU boards no longer
support this redundancy mode. For details, see 4.2.4 Service Processing
Units and 4.2.10 Example of Typical BSC6900 UMTS Configuration.
Deleted None
02 (2015-05-08)
Change Description
Added None

Change Description
Modified Removed N+1 backup from "Interface board backup mode and board
calculation rules in 4.2.5 Interface Boards because UMTS interface
boards, such as the FG2c, GOUc, and GOUe boards, no longer support N
+1 backup.
Deleted None
01 (2015-03-25)
Compared with Draft A (2015-01-15), this issue includes the following changes.
Change Description
Added None
Modified l Changed the resource allocation algorithm for service processing units
(DPU on the CS service plane)processing services carried on TRXs
connected to interface boards. For details, see 4.1.8 General Principles
for Board Configurations.
l Changed UMTS NIUa specifications to 1.6 Gbit/s when the experience
oriented network planning and optimization function or the
WRFD-171210 Radio-Aware Video Precedence feature is enabled, and
updated the calculation methods and configuration principles for NIUa
boards. For details, see 4.2.4 Service Processing Units, 4.2.7 General
Principles for Board Configurations, and 7.2.2 UMTS Hardware
Specifications.
l Changed the DEUa specifications from 208,000 Erlang to 260,000
Erlang when WRFD-171201 Crystal Voice in Deep Coverage is
enabled.
Deleted None
Draft A (2015-01-15)
Compared with Issue 05 (2014-10-29) of V900R016C00, this issue includes the following
changes.
Change Description
Added Added 4.4 Built-in ECO6910 Product Configurations.

Change Description
Modified l Added DEUa boards to support the optional features WRFD-170201

Seamless Crystal Voice and WRFD-171201 Crystal Voice in Deep
Coverage, and added the corresponding capacity plan and hardware
configurations related to features.
l Updated the configuration principles for SAU boards for UMTS and
added descriptions about how to determine GU TS configurations. For
details, see 4.2.4 Service Processing Units.
Deleted None

Configuration Principle (Global) 2 Introduction
2 Introduction
2.1 Overview
This document describes the product specifications, configuration principles, upgrade, and
capacity expansion regarding the BSC6900 V900R017C10.
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 mode and functions as a GSM BSC.
l A BSC6900 UMTS works in UMTS Only mode and functions as a UMTS RNC.
l A BSC6900 GU works in GSM&UMTS (GU) mode and functions as a GSM BSC and
UMTS RNC.
2.2 Version Differences

The BSC6900 V900R017C10 GU supports the following hardware versions: HW60 R8/
HW68 R11, HW69 R11, HW69 R13, HW69 R15, HW69 R16, HW69 R17.
A BSC6000, BSC6810, or BSC6900 can be upgraded to BSC6900 V900R017C10 by
upgrading software. When HW60 R8, HW68 R11, 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 BSC6900 is upgraded
to BSC6900 V900R017C10, the capacity remains unchanged after the upgrade.
Table 2-1 describes the version differences between HW69 R16 and later versions.

Table 2-1 Version differences between HW69 R16 and later versions
Hardware Version Difference

Version
HW69 R16 HW69 R16 has introduced new boards SPUc, GOUe, GCUb, and GCGb,
which can coexist with the corresponding old boards SPUb, GOUc,
GCUa, and GCGa. 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.
HW69 R17 HW69 R17 has introduced DEUa boards to support WRFD-170201
Seamless Crystal Voice and WRFD-171201 Crystal Voice in Deep
Coverage.
This document describes the configuration principles of the BSC6900 using HW69 R17
hardware.
BSC6900 V900R017C10 has the same basic specifications as BSC6900 V900R016C00.
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.
The following table describes HW R17 hardware.
Table 2-2 HW R17 hardware
Model Board Name Working

Mode
(GSM/
UMTS)
QM1P00UMPS01 MPS Main Processing Subrack GSM&UMT

S
QM1P00UEPS01 EPS Extended Processing Subrack GSM&UMT

S
WP1D000SPU03 SPUc Signal Processing Unit GSM&UMT

S
WP1D000DPU03 DPUe Data Processing Unit (335 Mbit/s/3350 GSM&UMT

Erl) S
WP1D000NIU00 NIUa Network Intelligence Unit GSM&UMT

S
WP1D000AEU00 AEUa ATM Interface Unit (32 E1) UMTS
WP1D000PEU01 PEUc IP Interface Unit (32 E1) GSM&UMT

S
WP1D000AOU01 AOUc ATM Interface Unit (4 STM-1, UMTS

Channelized)

Model Board Name Working

Mode
(GSM/
UMTS)
WP1D000POU01 POUc IP Interface Unit (4 STM-1, Channelized) GSM&UMT

S
WP1D000UOI01 UOIc ATM Interface Unit (8 STM-1, UMTS

Unchannelized)
WP1D000GOU03 GOUe IP Interface Unit (4 GE, Optical) GSM&UMT

S
WP1D000FG201 FG2c IP Interface Unit (12 FE/4 GE, Electric) GSM&UMT

S
WP1D000SAU01 SAUc Service Aware Unit GSM&UMT

S
WP1D000GCU02 GCUb General Clock Unit GSM&UMT

S
QW1D000GCG02 GCGc GPS&Clock Processing Unit GSM&UMT

S
WP1D000DPU05 DPUf CS Data Processing Unit (1920 CIC/3840 GSM

IWF(TDM&IP)/7680IWF(IP&IP))
WP1D000DPU06 DPUg PS Data Processing Unit (1024 PDCH) GSM
WP1D000DPU03 DPUe PS Data Processing Unit (1024 PDCH) GSM&UMT

S
WP1D000NIU00 NIUa Network Intelligence Unit GSM&UMT

S
WP1D000XPU03 XPUc Expansion Processing Unit (640) GSM
WP1D000EIU01 EIUb TDM Interface Unit (32 E1/T1) GSM
WP1D000OIU01 OIUb TDM Interface Unit (1 GSM

STM-1,Channelized)
WP1X000OMU02 OMUc Operation and Maintenance Unit GSM&UMT

S
WP1D000TNU01 TNUb TDM switching Unit GSM
WP1D000DEU00 DEUa Data Enhancement Processing Uint UMTS

Configuration Principle (Global) 3 Application Overview
3 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 and Figure 3-2 show a single BSC6900 cabinet appearance and its
configurations, respectively.
Figure 3-1 BSC6900 N68E-22 cabinet appearance

Figure 3-2 Configurations of a BSC6900 cabinet (front view and rear view)
Table 3-1 describes the maximum and minimum BSC6900 configurations in different
working modes.
Table 3-1 Maximum and minimum BSC6900 configurations in different working modes
Working Mode Minimum Configuration Maximum configuration
BSC6900 GSM 1 cabinet 2 cabinets

1 subrack (MPS) 4 subracks (1 MPS + 3 EPSs)
BSC6900 UMTS 1 cabinet 2 cabinets

1 subrack (MPS) 6 subracks (1 MPS + 5 EPSs)
BSC6900 GU 1 cabinet 2 cabinets

2 subracks (one for UMTS 6 subracks (1 MPS + 5 EPSs) Each
and the other for GSM) subrack can be configured as
required.
Table 3-2 describes the maximum BSC6900 specifications.

Table 3-2 Maximum BSC6900 specifications

Working Mode Maximum Specification
BSC6900 GSM l Maximum GSM specifications (TDM): 4096 TRXs, 24,000

Erlang, 5,900,000 BHCA, 16,384 activated PDCHs, and 1536
Mbit/s bandwidth over the Gb interface
l Maximum GSM specifications (all-IP): 8192 TRXs, 45,000
BSC6900 UMTS l 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.
BSC6900 GU l Maximum GSM specifications (TDM): 4096 TRXs, 24,000

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): 8192 TRXs, 45,000
When the maximum GSM specifications are reached, the UMTS
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 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
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. The preceding specifications are provided by full
configuration of UMTS boards in five subracks and GSM boards
in one subrack.
Table 3-3 describes the BSC6900 structural and power specifications.

Table 3-3 BSC6900 structural specifications

Item N68E-22 Specification N68E-21-N Specification
Cabinet dimensions (H x 2200 mm x 600 mm x 800 2130 mm x 600 mm x 800 mm

W x D) mm (86.61 in. x 23.62 in. x (83.86 in. x 23.62 in. x 31.50
31.50 in.) in.)
Available height inside 46 U 44 U

the cabinet
Weight per cabinet 320 kg (705.6 lb) 380 kg (837.9 lb)
Load-bearing capability 450 kg/m2 (0.64 bf/in.2)

of the floor
Table 3-4 describes the BSC6900 power specifications.
Table 3-4 BSC6900 power specifications

Item Value
Power input -48 V DC power supply
Power range 57 V to 40 V
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. 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. 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 7.2.1 UMTS
Traffic Model.

Configuration Principle (Global) 4 Product Configurations
4 Product Configurations
4.1 BSC6900 GSM Product Configurations

A BSC6900 GSM consists of hardware configurations and capacity licenses.
l Hardware configurations include the configurations of cabinets, subracks, data service

processing modules, signaling processing modules, network intelligence modules,
service awareness modules, interface modules, and clock modules.
l Hardware capacity licenses include Network Intelligence Throughput License, Mega
BSC License, and Packet Service Hardware Capacity.
Table 4-1 Mapping between hardware versions and GBSS versions
Hardw BSC6000 BSC6900

are
Versio GBSS6.1/ GBS GBSS12. GBSS GBS GBS GBS GB GBS
n GBSS7.0/ S9.0 0 13.0 S14. S15. S16. SS1 S17.
GBSS8.0/ 0 0 0 7.0 1
GBSS8.1
HW60
R8
HW69
R11
HW69
R13
HW69
R15
HW69
R16
HW69
R17

: supported x: not supported
The following BSC6900 UMTS boards can also be used in BSC6900 GSM mode (these GSM
boards cannot be used in UMTS mode):
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
To set 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.
4.1.1 Hardware Specification Redundancy

To ensure the network emergency handling capability and meet the requirements of service
growth in a certain period of time, certain hardware redundancy must be taken into account
during calculation of hardware resources. Hardware specifications minus redundant
specifications is the actually required hardware specifications. Hardware modules consist of
service processing units and interface boards.
You must negotiate with customers about hardware redundancy. Generally, 30% redundancy
is recommended.
For example, when calculating the number of DPUf boards required in A over IP mode:
Redundancy Formula for Calculating the Number of DPUf Boards
No redundancy RoundUp(MAXIWFPerBSCTDMIP/3840 +
MAX(MAXIWFPerBSCIPIP MAXIWFPerBSCTDMIP, 0)/
7680,0) +1
30% redundancy RoundUp(MAXIWFPerBSCTDMIP/(3840 x 70%) + MAX

(MAXIWFPerBSCIPIP MAXIWFPerBSCTDMIP, 0)/(7680 x
70%),0) +1
4.1.2 Cabinets
Table 4-2 shows the configuration of a BSC6900 cabinet.

Table 4-2 Cabinets
Model Name Function
WP1B4PBCBN00 BSC6900 cabinet Cabinet
Configuration principles:
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 is 1.
Calculation 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.
NOTE
1. 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 will not be obtained under the actual
system running conditions. Therefore, Pavg is provided for power consumption calculation.
2. 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.
3. For details about the power consumption of each board, see 7.3 List of Board Power
Consumption.
4.1.3 Subracks
Table 4-3 describes BSC6900 subracks.
Table 4-3 BSC6900 subracks
Model Abbreviation Function
QM1P00UMPS01 MPS Main processing subrack
QM1P00UEPS01 EPS Extended processing subrack
WP1D000TNU01 TNUb TDM switching unit
WP1X000OMU02 OMUc Operation and maintenance unit
WP1D000SAU01 SAUc Service aware unit
WP1D000SCU01 SCUb Service control unit
By default, TNUb, OMUc, and SCUb boards are delivered.

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.
The total power consumption of all boards in a subrack cannot exceed the maximum power
consumption of the subrack. The maximum power consumption of each BSC6900 MPS or
EPS is 1400 W.
NOTE
Consumption.
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:
All interface boards must be configured in the rear slots of an EPS.
l Service processing units can be configured in either the front or rear slots of an EPS.
l 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.
l 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.
l The number of GSM subracks cannot exceed 4.
l The total power consumption of all boards in a subrack cannot exceed the maximum
power consumption of the subrack. The maximum power consumption of each BSC6900
MPS or EPS is 1400 W, and that of each TCS is 1000 W.
NOTE
Consumption.
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)
If the GSM subrack functions the basic subrack, two additional clock boards and OMUc
boards must be configured, and slots for SAUc (one for GO, and one or two for GU) must be
reserved. Therefore, 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.
4.1.4 Hardware Capacity License

No new hardware licenses are introduced by the BSC6900 V900R017C10 GSM.
4.1.5 Service Processing Units

Table 4-4 lists service processing unites.
Table 4-4 Service processing units
Model Board Name Descript Specifications Remarks

ion
WP1D00 DPUf CS Data Provides TC function: 1920 For the TC

0DPU05 Processing CS CICs (A over function, the
Unit (1920 service TDM) specifications of
CIC/3840 processin IWF function: 3840 WP1D000DPU0
IWF(TDM&I g channels (Abis 5are 1920 CICs
P)/ (includin over IP and Ater when non-
7680IWF(IP& g the TC over TDM, or Abis wideband AMR
IP)) function over TDM and A coding schemes
and IWF over IP) are used. When
function) wideband AMR
7680 (IP&IP) coding schemes
and
works in (Abis over IP and are used, the
N+1 A over IP) specifications of
backup WP1D000DPU0
mode 5 are 50% of
1920 CICs (960
CICs),
equivalent to 2
times of a
common call.
For the IWF
function, the
specifications of
the DPUf are
unchanged
regardless of
whether non-
wideband or
wideband AMR
coding schemes
are used.
This is because
TC coding is not
involved in the
IWF function.


ion
WP1D00 DPUg PS Data Provides 1024 activated The

0DPU06 Processing PS PDCHs specifications
Unit (1024 service 110 PDCHs per remain
PDCH) processin DSP unchanged
g and regardless of the
works in coding schemes
N+1 (CS1 to CS4,
backup MCS1 to MCS9,
mode and EDGE+).
WP1D00 DPUe PS Data Provides 1024 activated The

0DPU03 Processing PS PDCHs specifications
Unit (1024 service 110 PDCHs per remain
PDCH) processin DSP unchanged
g and regardless of the
works in coding schemes
N+1 (CS1 to CS4,
backup MCS1 to MCS9,
mode and EDGE+).
WP1D00 NIUa Network Provides PS throughput: A maximum of

0NIU00 Intelligence intelligen 50 Mbit/s 3200 Mbit/s is
Unit t service supported. If the
awarenes Gb throughput is
s higher than 50
Mbit/s, network
intelligence
throughput
licenses must be
purchased.
QM1SNI - Network Provides PS throughput: One NIUa

U50M00 Intelligence intelligen 50 Mbit/s provides 50
Throughput t service Mbit/s PS
License awarenes throughput.
s
WP1D00 XPUc Expansion Provides GBTS: The BHCA is

0XPU03 Processing signaling 640TRX based on Huawei
Unit(640) processin default traffic
g and 3900Erlang model.
works in 1050K BHCA
active/ eGBTS:
standby
mode 640TRX
3900Erlang
950K BHCA


ion
WP1D00 XPUc( GSM Provides None If the IBCA

0XPU03 XPUI) Extensible IBCA feature is
Processing calculatio required, XPUI
Unit for n and boards are
Computation works in required.
Service independ
ent mode.
WP1D00 SPUc( Network Provides 10 AC The number of

0SPU03 NASP Assisted a service QM1M000SPU0
) Service processin 0 is calculated
Process g unit to based on
assist the GBFD-511609
network Intelligent Wi-Fi
Detection and
Selection
requirements at
network
deployment. One
QM1M000SPU0
0 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 is 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).
Configuration Principles for DPUf

Table 2 Network requirements during the configuration of DPUf describes the network
requirements during the configuration of DPUf.

Table 4-5 Network requirements during the configuration of DPUf

Item Description Remarks
A-interface Board configurations are In A over IP mode, the TC

networking mode affected by A over IP function is implemented by the
APortType transmission and BM/TC CN. Therefore, the BSC
separated mode provides the IWF function, not
the TC function.
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.
MaxACICPerBSC, Number of CICs on the A Calculated based on the actual

WbAMRRate interface (non-wideband AMR number of calls in the network
coding scheme):
includes the FR, HR, and all
types of AMR coding schemes
MaxACICPerBSC, (1 Number of CICs on the A Calculated based on the actual

WbAMRRate) interface (wideband AMR number of calls in the network
coding scheme):
includes all types of wideband
AMR coding schemes
MaxACICPerBSCTD Number of CICs on the A Calculated based on the actual

M interface when TDM number of calls in the network
transmission is used on the A
interface in BM/TC combined
or BM/TC separated mode
MaxACICPerBSCIP Number of CICs on the A Calculated based on the actual

interface in A over IP mode number of calls in the network
MaxIWFPerBSCTD Number of CICs in Abis over Calculated based on the

MIP IP and Ater over TDM or in network structure and the
Abis over TDM and A over IP traffic model.

MaxIWFPerBSCIPIP Number of CICs in A over IP Calculated based on the

and Abis over IP network structure and the
traffic model.
The number of DPUf boards to be configured depends on the number of required CIC
circuits. DPUf boards can work in N+1 backup mode.
l Depending on the mode in use, there are 4 different ways to calculate the number of
DPUf boards to be configured: In BM/TC separated mode (including A over IP in the
case of TDM/IP hybrid transmission over the A interface)
On the BM side:
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 (MAXIWFPerBSCTDMIP/3840 + Max
(MAXIWFPerBSCIPIP MAXIWFPerBSCTDMIP, 0)/7680,0) + 1
On the TC side:
Number of DPUf = Roundup (MaxACICPerBSCTDM/1920) + 1
l In BM/TC combined mode (including A over IP in the case of TDM/IP hybrid
transmission over the A interface)
The DPUf providing the TC function can also support the IWF function.
Extra DPUf should be configured to provide the IWF function for the A-interface CICs
in A over IP transmission.
Number of DPUf boards = Roundup (MaxACICPerBSCTDM/1920,0) + Roundup
(MAXIWFPerBSCTDMIP/3840 + Max (MAXIWFPerBSCIPIP
MAXIWFPerBSCTDMIP, 0)/7680,0) + 1
l 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(MAXIWFPerBSCTDMIP/3840 + Max
(MAXIWFPerBSCIPIP MAXIWFPerBSCTDMIP, 0)/7680,0) + 1
l Configuration principles for the WP1D000DPU06 (DPUg):
All IP Number of DPUf boards = Roundup (MaxACICPerBSCIP/7680,0) + 1
Configuration Principles for DPUg

The following table describes the network requirements during the configuration of DPUg.
MaxActivePDCHPer Maximum number of activated Calculated based on the number

BSC PDCHs 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 NIUa

The following table describes the network requirements that should be considered during the
configuration of NIUa and Network Intelligence Throughput License.
Gb throughput Throughput on the Gb interface Calculated based on the number

of users and the traffic model.
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.
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:
If... Value of Network Intelligence Throughput License
The Gb throughput is Roundup [(Gb throughput 50)/50, 0]

more than 50 Mbit/s
The Gb throughput is 0
50 Mbit/s or less
Configuration Principles for XPUc

The following table describes the network requirements during the configuration of XPUc.
BHCA requirement BHCA that need to be Calculated based on the number

supported in the network of users and the traffic model.
TRX Number Total number of TRXs Determined based on the

network plan

ERL Number CS traffic volume (Erlang) that Determined based on the

needs to be supported in the network plan
network
The number of XPUc boards to be configured depends on the total number of TRXs, BHCA
requirement, and CS traffic volume (Erlang) requirement.
If... Number of XPUc Boards
The BSC manages 2 x RoundUp(MAX[TRX Number/640, BHCA requirement/

only GBTSs 1050000, ERL Number/3900], 0)
The BSC manages 2 x RoundUp(MAX[TRX Number/640, BHCA requirement/950000,

only eGBTSs ERL Number/3900], 0)
The BSC manages 2 x RoundUp(MAX[TRX Number/640, BHCA requirement x GBTS

both GBTSs and TRX Number/TRX Number/1050K + BHCA requirement x eGBTS
eGBTSs TRX Number/TRX Number/950KERL, 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.
Configuration Principles for XPUI

The following table describes the network requirements during the configuration of XPUI.
IBCA Needs Whether the network requires 2 or more

the IBCA function
If the IBCA function is configured, XPUc boards must be configured to function as XPUI. By
default, two XPUc boards are configured. A maximum of eight XPUc boards are allowed.
The following describes the configuration principles.
For BSC6900, IBCA can be enabled on a maximum of 3072 TRXs, and inter-BSC IBCA can
be enabled on a maximum of 1200 TRXs in external neighboring cells.

Number of TRXs Number of TRXs in External Number of MCPs

Neighboring Cells
1024 1200 2
2048 1200 4
3072 1200 6
The following table lists the network factors during the configuration of NASP.
NASP Needs Whether the network requires One NASP board is configured
the GBFD-511609 Intelligent for each BSC.
Wi-Fi Detection and Selection
function
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.6 Interface Boards

The BSC6900 provides diversified interfaces to meet the requirements of different networking
modes.
Table 4-6 lists the interface boards required by the BSC6900 GSM.
Table 4-6 Interface boards
Model Abbreviat Name Where to Apply

ion
WP1D000E EIUb TDM Interface Unit (32 E1/T1) TDM transmission: A/

IU01 Ater/Abis/Lb
WP1D000O OIUb TDM Interface Unit (1 STM-1, TDM transmission: A/

IU01 Channelized) Ater/Abis/Lb
WP1D000P POUc TDM or IP Interface Unit (4 TDM/FR transmission:

OU01 STM-1, Channelized) A/Ater/Abis/Lb/Gb
IP transmission: A/
Abis/Lb
WP1D000P PEUc IP Interface Unit (32 E1/T1) FR or IP transmission:

EU01 A/Abis/Lb/Gb
WP1D000F FG2c IP Interface Unit (12 FE/4 GE, IP transmission: A/

G201 Electrical) Abis/Lb/Gb/Iur-g

Model Abbreviat Name Where to Apply

ion
WP1D000G GOUe IP Interface Unit (4 GE, Optical) IP transmission: A/

OU03 Abis/Lb/Gb/Iur-g
NOTE
An interface board cannot be shared by multiple interfaces.
By default, the following boards are delivered: EIUb, OIUb, POUc, PEUc, FG2c, and GOUe.
Table 4-7 lists the specifications of interface boards on different interfaces.
Table 4-7 Specifications of interface boards on different interfaces

Model Tran Port Port Num Numbe Numbe Gb
smis Type No. ber r of CIC r of CIC Throug
sion of circuits circuits hput(M
Type TRXs (64 (16 bit/s)
kbit/s) kbit/s)
on the on the
A Ater
Interfac Interfac
e e
EIUb TDM TDM E1 32 384 960 3840 N/A
OIUb TDM TDM 1 384 1920 7168 N/A

CSTM-1
PEUc TDM Gb FR E1 32 N/A N/A N/A 64
IP IP E1 32 384 6144 N/A N/A
POUc TDM TDM 4 512 DPUc 7168 504

CSTM-1 boards
configur
ed: 3680
DPUf
boards
configur
ed: 7680
IP IP 4 2048 23,040 N/A N/A

CSTM-1
FG2c IP FE/GE 12/4 2048 23,040 N/A 1024

electrical
port
GOUe IP GE 4 2048 23,040 N/A 1024

optical
port

NOTE
In Abis over TDM, the EIUb supports a maximum of 384 TRXs, 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:
1. 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 RED parameter in the
ADD BRD command.
2. Traffic model: The traffic volume is 5.86 Erlang 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.
3. 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.
4. After the VAMOS feature is enabled, extra Abis bandwidth is required, which also affects the TRX
specifications of interface boards.
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.
Number of interface boards required by the Abis interface

Select the types of interface boards based on the network plan. The number of required Abis
interface boards is calculated based on either the service capability (number of supported
TRXs) or number of required ports. Use the larger 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
AbisTRXNumber TRXNoTD Number of TRXs in Abis over Determined

ME1 TDM over E1 mode based on the
network plan
TRXNoIPE Number of TRXs in Abis over IP
1 over E1 mode
TRXNoTD Number of TRXs in Abis over

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

TM1 over STM-1 mode
AbisPortNumber AbisTDME Maximum number of TDM-based Calculated based

1No E1 ports required by a BSC on the on the traffic
Abis interface model
AbisIPE1N Maximum number of IP-based E1

o ports required by a BSC on the
Abis interface

AbisTDMS Maximum number of TDM-based

TM1No STM-1 ports required by a BSC on
the Abis interface (one STM-1 is
equivalent to 63 E1s)
AbisIPST Maximum number of IP-based

M1No STM-1 ports required by a BSC on
the Abis interface (one STM-1 is
equivalent to 63 E1s)
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 required by a base station for transmission optimization but the BSC is
not configured with any TDM over E1 interface boards, you must configure two EIUb or EIUa
boards.
If Abis over TDM is used, either of the following conditions must be met:
Mode Restrictions
Active/standby Number of TRXs supported by the Abis TDM interface board x

(Average number of Erlangs per TRX + Average number of PDCHs per
TRX x Number of timeslots required for PS transmission) 7680
Stand-alone Number of TRXs supported by the Abis TDM interface board x

(Average number of Erlangs 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.
Number of timeslots required for PS Specifications

transmission
CS-1 1
CS-2 1
CS-3 2
CS-4 2
MCS-1 1

Number of timeslots required for PS Specifications

transmission
MCS-2 1
MCS-3 2
MCS-4 2
MCS-5 2
MCS-6 2
MCS-7 3
MCS-8 4
MCS-9 4
For example:
1. 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, meeting the requirements when DPUf boards are configured.
2. 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, not meeting the requirements when DPUf boards are configured. Therefore, the
number of TRXs supported by the POUc must be reduced to 351.
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.
ACICNumber MaxACICPer Maximum number of CICs Calculated based on

BSCTDM required by a BSC on the A the traffic model
interface (TDM transmission)
MaxACICPer Maximum number of CICs

BSCIP 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.
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.
AterCICNum MaxAterCICPer Maximum number of CICs Calculated based on

ber BSC required by a BSC on the the traffic model
Ater interface
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
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.
GbThroughput GbFRTputPer Overall traffic volume of a Calculated based on

BSC BSC on the Gb interface in FR the traffic model
transmission mode
GbIPTputPerB Overall traffic volume of a

SC 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 calculate the number of interface
4.1.7 Clock Boards

Table 4-8 describes clock boards and configuration methods.
Table 4-8 Clock boards

Model Abbr Name Function Configuration Method
eviati
on
WP1D000 GCU General Clock Provides general Optional. When a BSC6900

GCU02 b Unit clock signals does not require GPS clock
signals, a pair of GCUb
boards can be configured for
the BSC6900.
QW1D00 GCG GPS&Clock Provides GPS Optional. When a BSC6900

0GCG02 b Processing Unit clock signals requires GPS clock signals, a
(including the pair of GCGb boards can be
antenna system) configured for the BSC6900.
By default, both GCUb and GCGb are delivered.
4.1.8 General Principles for Board Configurations

BSC6900 GSM service processing boards, such as XPU and DPU, work in resource pool
mode within in a BSC.
Services carried on TRXs connected to interface boards in a subrack are preferentially

processed by service processing units (XPU on the signaling plane and DPU on the PS service
plane) in the same subrack. If the resources required by a subrack exceed the specified
threshold, load sharing is implemented between subracks of the BSC.
Services carried on TRXs are processed by service processing units (DPU on theCS service
plane), which can work in resource pool mode with the following taken into account:
l In A over TDM, service processing units in the same subrack as the A interface board
are preferentially used.
l In A over IP and Abis over TDM mode, service processing units in the same subrack as
the Abis interface board are preferentially used.
l In A over IP and Abis over IP mode, intra-BSC resource pool is implemented, without
any subrack preferentially selected.
Other boards are configured according to the following principles:

1. 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 boards must be distributed as evenly as possible among subracks.
Configuring the same type of board in the same subrack lowers system reliability.
1. If POUc boards are used as A interface boards, DPUf boards 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 boards 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 board must be configured in a subrack.
2. 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/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.
3. 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.
4. It is recommended that one MPU be configured for each two pairs of XPU.
5. 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 LAC can receive more than 120 paging requests per second over the Um
interface when a single CCCH is configured. Therefore, it is recommended that 512
TRXs for each LAC be configured in the case of a single CCCH. The TRX number
can be adjusted by traffic.
Consecutive PDCHs are configured so that MSs can use multiple consecutive
timeslots.
Other basic principles during GSM network planning.
6. General principles of board configuration:
The TNUb boards are always installed in slots 4 and 5. The TNU board is not
required in all IP mode. In this case, you can configure DPU boards in slots 4 and 5.
However, you are advised not to configure XPU boards in these slots because
moving an XPU board requires site transfer. The SCUb boards are always installed
in slots 6 and 7. The GCUb/GCGb boards are always installed in slots 12 and 13.
The DPUe/DPUf/DPUg/NIUa boards can be installed in front or rear slots. It is
recommended that they be installed in front slots.
The EIUb/PEUc/AEUa/OIUb/AOUc/UOIc/POUc/FG2c/GOUe boards are interface
boards. They can be installed only in rear slots.
7. The OMUc board is always configured in slots 24 and 25 of the MPS.
8. The clock processing boards are always configured in slots 12 and 13 of the MPS.
9. The SCUb boards are always configured in slots 6 and 7 of the MPS and EPS.

10. 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 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. One SAU board is delivered by default in UMTS
mode or GU mode for EBC.
NOTE
MPU is a logical unit of XPU board. The MPU implements board management and transfer internal
messages to other boards.
4.1.9 Auxiliary Materials

Table 4-9 lists the auxiliary materials for installing a BSC6900 GSM.
Table 4-9 Auxiliary materials

Model Name Function Configuration
Method
QW1P8D442000 Trunk Cable 75-ohm trunk cable Full configuration
QW1P0STMOM0 STM-1 Optical STM-1 optical unit Full configuration

0 Connector (active/standby)
QW1P00GEOM0 GE Optical GE optical unit Full configuration

0 Connector (active/standby)
QW1P0FIBER00 Optical Fiber Optical cable Configured based on

the number of optical
modules
QW1P0000IM00 Installation Material Installation material One installation

Package suite material suite
configured for each
BSC6900 cabinet
(WP1B4PBCBN00)
QMAI00EDOC00 Documentation Electronic A set of electronic

documentation documentation
(QMAI00EDOC00)
delivered with each
BSC6900
The formulas for calculating auxiliary materials are as follows:
l Number of trunk cables (QW1P8D442000) = [Number of TDM interface units (32 E1s)
+ Number of IP interface units (32 E1s)] x 2
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.

l Number of trunk cables (QW1P8D442003) = [Number of TDM interface units (32 E1s)
l Number of STM-1 optical units (QW1P0STMOM00) = Number of OIUb boards +
Number of POUc boards x 4
l Number of GE optical connectors (QW1P00GEOM00) = WP1D000GOU01 or
WP1D000GOU03 quantity x 4
l Number of optical fibers (QW1P0FIBER00) = (Number of STM-1 optical connectors +
Number of GE optical connectors) x 2
4.1.10 Example BSC6900 GSM Configuration

The following figure illustrates the typical procedure for configuring a BSC6900 GSM.
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.

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 4
Dynamic PDCH per Cell 8
Built-in PCU Yes
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 No

the number of required CIC circuits)
Step 2 Perform the measurements.
The following figure shows the dimensions that are used for calculating the configurations
Item Name Specification
1 TRX support capability A1
2 Abis E1 quantity A2
3 A CIC quantity A3
4 IWF quantity A4

Item Name Specification
5 BHCA A5
6 Gb throughput A6
7 - -
Step 3 Obtain the network capacity requirements to calculate the hardware requirements.
Item Name Configuration Before
Capacity Expansion
1 Subracks (MPS, EPS) B1
2 Data Processing Units (DPUf) B2
3 Data Processing Units (DPUg) B3
4 Extended Processing Units (XPUc) B4
5 Interface boards B5
6 Cabinets B6
----End
4.1.11 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. BSC6900s with excessively large capacity are not
delivered in a large scale on the live network. Therefore, it is recommended that the BSC6900
capacity be controlled for the initial network deployment.
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. To use
this feature, ensure that the sum of activated TRXs and backup TRXs for the BSC6900 must
be less than 6144.

4.2 BSC6900 UMTS Product Configurations

A BSC6900 UMTS consists of hardware and hardware capacity licenses.
A BSC6900 UMTS consists of hardware configurations and capacity licenses.
l Hardware configurations include the configurations of cabinets, subracks, data service

processing modules, signaling processing modules, network intelligence modules,
service awareness modules, interface modules, and clock modules.
l Hardware capacity licenses include Hardware Capacity License (165Mbit/s), Hardware
Capacity License (300Mbit/s), and Network Intelligence Throughput License.
All the product specifications can be reached when the CPU load of the hardware is 70%.
SPUc functions as a substitute of SPUb as they have the same specifications. The same is true
for GOUe and GOUc, GCUb and GCUa, and GCGb and GCGa boards. The SPUc
configuration principles provided in the following sections apply to SPUb boards. The same is
true for GOUe/GOUc, GCUb/GCUa, and GCGb/GCGa boards.
NOTICE
To set 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.
SPUc and SPUb can work in active/standby mode, so do GOUe and GOUc, GCGa and
GCGb, and GCUa and GCUb.
4.2.1 Cabinets
Table 4-10 shows the configurations of cabinets.

Table 4-10 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.
l In a newly deployed network:

Number of cabinets = Roundup ((Number of MPSs + Number of EPSs)/3, 0)
where, Number of MPSs is 1.
l In capacity expansion scenarios:
Number of cabinets = Number of cabinets required after capacity expansion Number
of cabinets configured before capacity expansion
Calculation of cabinet power consumption:
The maximum power consumption for a single cabinet is 5100 W, and the maximum
power consumption for a single subrack is 1700 W.
NOTE
1. 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 will not be obtained
under the actual system running conditions. Therefore, Pavg is provided for power
consumption calculation.
2. 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.
Consumption.
4.2.2 Subracks
Table 4-11 describes subrack configurations.
Table 4-11 Subracks
Model Abbrev Function Function

iation
QM1P00UMPS01 MPS Main processing subrack Main processing subrack
QM1P00UEPS01 EPS Extended processing subrack Extended processing

subrack
WP1X000OMU02 OMUc Operation and Maintenance Operation and

Unit maintenance unit
WP1D000SAU01 SAUc Service Aware Unit REV:c Service aware unit REV:c

Model Abbrev Function Function

iation
WP1D000SCU01 SCUb GE Switching Network and GE switching network

Control Unit and control unit
By default, the following boards are delivered: OMUc, SAUc, and SCUb.
Configuration Principles for the MPS

One MPS must be configured in a BSC6900 UMTS.
Configuration Principles for the EPS

A maximum of five EPSs can be configured in a BSC6900 UMTS.
New deployment
Number of EPSs = MAX (Number of required EPSs_1, Number of required EPSs_2, Number
of required EPSs_3, Number of required EPSs_4)
Number of EPSs_1 = Roundup (MAX((Number of required SPUc pairs Number of SPUc

boards that can be housed by MPS)/9, 0))
Number of EPSs_2 = Roundup (MAX((Number of required DPUe boards Number of

DPUe boards that can be housed by MPS)/9, 0))
Number of EPSs_3 = Roundup (MAX((Number of slots required by interface boards

Number of slots for interface boards in MPS)/14, 0))
Number of EPSs_4 = Roundup (MAX((Number of required SPUc pairs x 2 + Number of

required DPUe boards + Number of slots required by interface boards + Number of required
NIUa boards Number of slots in MPS)/26, 0))
Table 4-12 List of EPS counters
Counter Value Description
Number of SPUc boards that can be 9 pairs Each pair of SPUc boards occupies
housed by MPS two slots.
Number of SPUc boards that can be 9 pairs

housed by EPS
Number of DPUe boards that can be 9 N/A

housed by MPS
Number of DPUe boards that can be 9 N/A

housed by EPS
Number of slots for interface boards in 10 N/A

MPS

Counter Value Description
Number of slots in MPS 12 Two slots are reserved for SAU

boards.
Capacity expansion
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 UMTS only
mode.
By default, one SAUc board is configured for EBC in UMTS only mode or GU mode. At
most two SAUc boards can be configured. The following tables provide the details.
Whether GU Scenario Number of SAU Boards

TS Is
Configured
No Only the Nastar is deployed. 1
Either EBC or SON is deployed. 1
The Nastar is deployed, and either EBC or 2

SON is deployed.
Yes Any OSS feature is deployed. 1
NOTE
TS refers to the U2000/Trace server.
4.2.3 Hardware Capacity License

The BSC6900 supports the Hardware Capacity License(165Mbit/s), Hardware Capacity
License(300Mbit/s), and Network Intelligence Throughput License(50Mbit/s).
License Function Hardware Version
Hardware Capacity Superimpose onto the Applicable to HW69 R11, HW69

License(165Mbit/s) hardware capacity of the R13, HW69 R15, HW69 R16,
DPUe board (335 Mbit/s) HW69 R17.
Hardware Capacity to increase the user-plane
License(300Mbit/s) data processing capability.
Network Intelligence Superposed on the The Network Intelligence

Throughput hardware capacity of the Throughput License is applicable
License(50Mbit/s) NIUa board (50 Mbit/s) to to HW69 R13, HW69 R15,
support service awareness. HW69 R16, HW69 R17.
The NIUa board provides the service awareness and PS service quality measurement
functions. The following features require the service awareness function: 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 features require the PS service quality measurement function:
offline user experience evaluation, WRFD-171210 Radio-Aware Video Precedence.
Hardware Capacity License (165Mbit/s) Configuration Principles

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.
Hardware Capacity License (300Mbit/s) Configuration Principles

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.
l The Hardware Capacity License (300Mbps) and Hardware Capacity License (165Mbps)
licenses cannot be necessarily used to increase the user-plane capability. They increase the
user-plane capability only when the DPUe hardware capability is higher than 335 Mbps.
The DPUe hardware capability varies with the traffic model. For details about how to
calculate the DPUe hardware capability, see 5.2.3.
Assume that two DPUe boards are configured. Table 4-13 lists the PS throughput before and
after hardware capacity licenses are configured.

Table 4-13 Comparison of PS throughput before and after hardware capacity licenses are
configured
Number of Number of User Plane Number of User Plane
Configured Configured Processing Configured Processing
WP1D000D Hardware Capability Hardware Capability
PU03s(DPU Capacity Licenses (Mbit/s/ Capacity (Mbit/s/
e) (165 Mbit/s) Erlang)* Licenses (300 Erlang)*
Mbit/s)
2 0 670/6700 0 670/6700
1 835/6700 0 835/6700
1 1135/6700
2 1000/6700 0 1000/6700
1 1300/6700
2 1600/6700
NOTE
l 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 DPUe boards process both PS and CS services, the processing capability must meet
the following inequality:
CS traffic volume/6700 Erl + PS traffic volume/670 Mbit/s <=1
If additional two Hardware Capacity License(165Mbit/s) and two Hardware Capacity
License(300Mbit/s) are configured, the processing capability must meet the following inequality:
CS traffic volume/6700 Erl + PS traffic volume/1600 Mbit/s <=1
If the PS throughput in a given traffic model is greater than 335 Mbit/s, the Hardware
Capacity License is configured by default. Also, 165 Mbit/s or the combination of 165 Mbit/s
and 300 Mbit/s can be used.
If the PS throughput in a given traffic model is less than 335 Mbit/s, the Hardware Capacity
License is optional. 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 (165 Mbit/s) and Hardware Capacity License (300 Mbit/s) 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 (50 Mbit/s) Configuration Principles

This license can be configured for a network intelligence unit NIUa(WP1D000NIU00) to
increase the service awareness processing capability. 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. The number of Network Intelligence Throughput Licenses varies with the traffic
volume contributed by service awareness features, but not with the number of configured
service awareness features.
4.2.4 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, DEUa, and the following hardware licenses: Hardware Capacity
License (165Mbit/s), Hardware Capacity License (300Mbit/s), and Network Intelligence
Throughput (50Mbit/s) license. Table 4-14 describes these processing units.
Table 4-14 Service processing units
Model Abbr Name Functio Specification Condition

eviat n
ion
WP1D000 SPUc Signaling Signalin 124,000 BHCA, 124,000 BHCA based

SPU03 Processin g 180 NodeBs, 600 on the balanced traffic
g Unit processi cells, 9600 active model described in
ng users, and 24,000 Table 7-8. The actual
online users BHCA capacity must
be calculated based on
the actual traffic model.
Mandatory
WP1D000 DPUe Data Data PS Throughput The PS throughput of

DPU03 Processin processi 335 Mbit/ the DPUe board
g Unit ng s(depending on depends on the traffic
(335 enhance the traffic model) model.
Mbit/s/ ment or 3350 Erlang, Mandatory
3350 Erl) 300 cells, and
5880 active users
QM1SHW - Hardware Data PS Throughput: Optional Whether to

165M00 Capacity processi 165 Mbit/s configure this hardware
License(1 ng capacity license
65Mbit/s) enhance depends on the PS
ment throughput of the DPUe
board under the actual
traffic model.
QM1SHW - Hardware Data PS Throughput: Optional Whether to

300M00 Capacity processi 300Mbit/s configure this hardware
License ng capacity license
(300Mbit/ enhance depends on the PS
s) ment throughput of the DPUe
board under the actual
traffic model.


eviat n
ion
WP1D000 NIUa Network Intellige Provides the The following features

NIU00 Intelligen nt service require the service
ce Unit service awareness and PS awareness function:
awarenes service quality WRFD-020132 Web
s measurement Browsing Acceleration,
functions. WRFD-020133 P2P
When used for Downloading Rate
service Control during Busy
awareness, this Hour, WRFD-150252
feature provides Video Service Rate
3200 Mbit/s PS Adaption,
throughput. WRFD-150253 VoIP
Application
When used for Management, and
PS service WRFD-150254
quality Differentiated Service
measurement, Based on Application
this feature Resource Reservation.
provides 1600
Mbit/s PS The following features
throughput. require the PS service
quality measurement
function: offline user
experience evaluation,
WRFD-171210 Radio-
Aware Video
Precedence.
QM1SNIU - Network Intellige PS Throughput: Optional Required only

50M00 Intelligen nt 50 Mbit/s when NIUa boards are
ce service configured.
Throughp awarenes
ut s
License


eviat n
ion
WP1D000 DEUa Data Data 1. Supports 9000 1. Required only when

DEU00 Enhance Enhance Erlang CS voice WRFD-170201
ment ment services (12.2 Seamless Crystal Voice
Processin Processi kbit/s) or 3600 feature is used. The
g Unit ng Unit Erlang CS voice capacity is only
(version: services (23.85 impacted by the traffic
a) kbit/s) seamless in soft handover state
crystal voice (not including softer
coding handover)
processing. 2. Required when
2. The DEUa WRFD-171201 Crystal
supports 260000 Voice in Deep
Erlang for Coverage feature is
Crystal Voice in used. The capacity is
Deep Coverage. impacted by CS voice
service traffic.
By default, DPUe and SPUc boards are delivered. If the intelligent service awareness unit is
required, NIUa boards are delivered by default.
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.
Configuration Principles for SPUc
Table 4-15 The following table describes the network requirements during the configuration
of SPUc.
BHCA BHCA required by the network It is calculated based on the number

requirement of users and traffic model.
Active users Number of concurrent active users It is calculated based on the number
who need to be supported by the of users and traffic model.
BSC6900 UMTS control plane
Online users Number of concurrent online users It is calculated based on the number
who need to be supported by the of users and traffic model.
BSC6900 UMTS control plane
NodeB Number of NodeBs that need to be Determined based on the network

number managed by the BSC6900 UMTS plan

Cell number Number of cells that need to be Determined based on the network
managed by the BSC6900 UMTS plan
In a newly deployed network:

Number of SPUc boards = Roundup (Max (BHCA requirement/SPUc BHCA, Active users/
Number of active users on SPUc, On-line users/Number of online users on SPUc, NodeB
number/Number of NodeBs supported by SPUc, Cell number/Number of cells supported by
SPUc)) x 2 (SPUc boards working in active/standby mode)
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.2.1 UMTS Traffic
Model. BHCA supported by one SPUc must be recalculated based on the actual traffic
model.
In capacity expansion scenarios:
Number of SPUc boards = Number of SPUc boards after capacity expansion Number of
SPUc boards before capacity expansion
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 Principles for DPUe and Hardware Capacity Licenses
Table 4-16 The following table describes the network requirements that should be considered
during the configuration of DPUe and hardware capacity licenses.
Iub PS PS throughput that needs to be It is calculated based on the number

throughput supported on the Iub interface of users and traffic model.
Iub CS CS traffic that needs to be It is calculated based on the number

traffic supported on the Iub interface of users and traffic model.
Active users Number of concurrent active users It is calculated based on the number
required by the BSC6900 UMTS of users and traffic model.
user plane
Cell number Number of cells that need to be Determined based on the network
managed by the BSC6900 UMTS plan
In a newly deployed network:

Assume that the user plane capacity requirements on the Iub interface of a network are
Iub PS throughput: a Mbit/s
b Erlang (Iub CS traffic volume), c (number of cells), and n (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:
"PS RAB Mean data rate in active "PS Throughput Capacity per
state (UL/+DL)(kbit/s)" Value DPUe(Mbit/s)" Calculation Method
Range
(0, 16] PS RAB Mean data rate x 5.625
(16, 40] 90 + (PS RAB Mean data rate 16) x 6.67
(448, ) 800
Iub CS Traffic is represented by b (Erl).

Cell number is represented by c.
Active users is represented by n, indicating the number of users in the Cell_DCH or
Cell_FACH state.
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
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 x165)/300]}
NOTE
A minimum of two DPUe boards can be configured. A maximum of 50 DPUe boards can be configured.
It is recommended that DPUe boards be configured in N+1 redundancy mode.
In capacity expansion scenarios:

Calculate the number of required DPUe boards, hardware capacity licenses (165 Mbit/s), and
hardware capacity licenses (300 Mbit/s) according to the calculation procedure provided
previously for a newly deployed network.

Module Before Expansion After Expansion
DPUe A1 A2
Hardware Capacity License(165Mbit/s) B1 B2
Hardware Capacity License(300Mbit/s) C1 C2
In capacity expansion scenarios, the calculation methods are as follows:

Number of DPUe boards = A2 A1
Hardware Capacity License(165Mbit/s) = B2 B1
Hardware Capacity License(300Mbit/s) = C2 C1
Configuration Principles for NIUa and Network Intelligence Throughput

License
The NIUa board provides the service awareness and PS service quality measurement
functions.
Function PS Throughput Features Involved
Service awareness 3200 Mbit/s 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 service quality 1600 Mbit/s Offline user experience evaluation,

measurement WRFD-171210 Radio-Aware Video
Precedence
a = Iub PS throughput (Mbit/s) Each NIUa provides 50 Mbit/s PS throughput.
If... Value of Network Intelligence Throughput License
a is more than 50 RoundUp ((a 50)/50, 0)

Mbit/s
a is 50 Mbit/s or less 0
If the NIUa board is used for only the service awareness function:
Number of ENIUa boards required: N_ ENIUa = Roundup (a/3200)

If the NIUa board is used for both the service awareness and PS service quality measurement
functions:
Number of ENIUa boards required: N_ ENIUa = Roundup (a/1600)
Table 4-17 Proportions of traffic volume delivered by major bearer types and application
types (assumed conditions)
Bearer Type HTTPS HTTP HTTP HTTP (File Others

and (Web (Video) Access)
Application Browsing)
Type
Traffic 60% 22% 5% 3% 10%

Volume
Proportion
NOTE
1. When the NIUa board is used for PS service quality measurement, the board specifications are
determined by the proportions of traffic delivered by different bearer types and application types. The
assumed conditions in this table apply to most commercial networks.
Configuration Principles for DEUa Boards

Item Description Calculation Remarks
Iub CS Voice CS traffic on Vco_b (Erlang) = Iu-CS voice Number of

Traffic in the Iub traffic x Ratio of SHO user x Iub RL required DEUa
Soft HO state interface in number per SHO user boards = Vco_b
soft handover This item is involved only if the (Erlang) x
state WRFD-170201 Seamless Crystal (Proportion of
(excluding Voice feature is enabled. WB-AMR)/3600 +
softer Vco_b (Erlang) x
handover) (1 Proportion of
WB-AMR)/9000
Iub CS CS service b Erl, Iub CS Erlang requirement Number of DEUa

Traffic requirements This item is involved only when the boards = b/260000
on the Iub WRFD-171201 Crystal Voice Deep
interface Coverage feature is enabled.
Note:
1. Proportion of WB-AMR indicates the radio of WB-AMR traffic to total CS traffic. The
default value is 0.05, which can be set based on network conditions.
2. Ratio of SHO user indicates the ratio of users in the soft handover state to total users.
The default value is 0.25, which can be set based on network conditions.
3. Iub RL number per SHO user indicates the average number of radio links occupied by
users in the soft handover. The default value is 2.8, which can be set based on network
conditions.

The specifications of DEUa boards for WB-AMR and NB-AMR are different, as listed in the
following table.
Model Seamless Crystal Seamless Crystal Crystal Voice in

Voice (AMR) Voice (WB-AMR) Deep Coverage
WP1D000DEU00 9000 Erlang 3600 Erlang 260000 Erlang
If the WRFD-170201 Seamless Crystal Voice feature is required, configure the DEUa board.
The calculation method is as follows:
If the voice services in the network are all NB-AMR (12.2 kbit/s), the number of DEUa
boards is calculated as follows: N_DEUa_SeamlessCryV = Roundup (Vco_b/9000) + 1
If there is WB-AMR in the network, the number of DEUa boards is calculated as follows:
N_DEUa_SeamlessCryV = ROUNDUP[Vco_b x Proportion of WB-AMR/3600 + Vco_b x (1
Proportion of WB-AMR)/9000] + 1
If the WRFD-171201 Crystal Voice in Deep Coverage feature is used, configure the DEUa
board. The calculation method is as follows:
N_DEUa_CryVDeepC = Roundup (b/260000) + 1
To use both the WRFD-170201 Seamless Crystal Voice and WRFD-171201 Crystal Voice
Deep Coverage features are used, configure more DEUa boards. The calculation method is as
follows:
N_DEUa = Roundup [Vco_b x Proportion of WB-AMR/3600 + Vco_b x (1 Proportion of
WB-AMR)/9000 + b/260000] + 1
NOTE
It is recommended that DEUa boards work in N+1 redundancy mode.
4.2.5 Interface Boards

The BSC6900 provides diversified interfaces to meet the requirements of different networking
modes.
The interface board specifications

include traffic volume, number of subscribers, number of NodeBs, and number of session
setups/releases. The following table lists the specifications of each interface board on different
interfaces (Iub, Iur, Iu-CS, and Iu-PS).

Table 4-18 Interface boards required by the BSC6900 UMTS
Model Abbre Name Where to Sessio CID/

viatio Apply n UDP(I
n Setup/ UB
Releas Active
e Users)
Times
WP1D000AE AEUa ATM Interface Unit (32 Iub 500 23,000

U00 E1)
WP1D000PE PEUc IP Interface Unit (32 E1) Iub 500 23,000

U01
WP1D000AO AOUc ATM Interface Unit (4 Iub 5000 79,000

U01 STM-1, Channelized)
WP1D000PO POUc IP Interface Unit (4 Iub 5000 129,00

U01 STM-1, Channelized) 0
WP1D000UO UOIc ATM Interface Unit (8 Iub/Iu- 5000 79,000

I01 STM-1, Unchannelized) CS//Iu-PS/Iur
WP1D000GO GOUe IP Interface Unit (4 GE, Iub/Iu- 5000 129,00

U03 Optical) CS//Iu- 0
PS/Iur/Iur-
pnote
WP1D000FG FG2c IP Interface Unit (12 FE/4 Iub/Iu- 5000 129,00

201 GE, Electrical) CS//Iu- 0
PS/Iur/Iur-
pnote
NOTE
The Iur-p is a Huawei-proprietary interface between RNCs to support the RNC in Pool feature.
By default, the following boards are delivered: AEUa, PEUc, AOUc, POUc, UOIc, GOUe,
and FG2c.
Specifications of interface boards
Table 4-19 Specifications of interface boards over the Iub/Iur/Iur-p interface
Model Iub/Iur/Iur-p NodeB
Voice (AMR VP UL DL UL
& WB- (Erlang) (Mbit/s) (Mbit/s) +DL
AMR) (Mbit/s
)
WP1D000AEU00 2800 680 45 45 90 32

WP1D000PEU01 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-20 Specifications of interface boards over the Iu-CS/Iu-PS interface

Model Iu-CS Iu-PS
Voice VP UL DL UL+DL IU PS
(Erlang) (Erlang) (Mbit/s) (Mbit/s (Mbit/s) Online
(AMR & ) Users(TEI
WB- D)
AMR)
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
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 represents the traditional 12.2 kbit/s CS services, and WBAMR represents the
typical 23.85 kbit/s CS services.
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-21 lists the
mapping between the interface signaling processing requirements and the traffic model.

Table 4-21 Session setups/releases times of signaling procedure of control plane of

traffic model
Control Plane Traffic Unit Iub Iu-PS Session
Parameter Session Setup/Release
Setup/ Times
Release
Times
CS voice call per subscriber times 2 -

per BH
Handover times per CS voice times/call 2 -

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

BH
Handover times per PS call times/call 2 -

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

call
Cell update per PS call times/call - 0.8
NAS signaling per subscriber times/per subscriber 1 -

per BH (times)
Configuration of interface boards
Table 4-22 Network requirements for configuration of interface boards

Interface Item Description Remarks
Iub Iub transmission type Transmission type used Determined based on

on the Iub interface of the network plan
the network
Iub PS throughput PS throughput that needs It is calculated based

to be supported on the on the number of
Iub interface users and traffic
model.
Iub CS traffic CS traffic that needs to
be supported on the Iub
interface
Iub session setup and Session setup and

release requirement in release capacity that
BH matches the network
BHCA capacity

Interface Item Description Remarks
Iub active users(CID/ Number of concurrent

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

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

type on the Iu-CS interface of the network plan
the network
Iu-CS CS traffic CS traffic volume on the It is calculated based

Iu-CS interface on the number of
users and traffic
Iu-CS active users Number of concurrent model.
active users who need to
be supported the Iu-CS
interface of the
BSC6900 UMTS
Iu-CS session setup and Number of sessions that

release requirement in need to be supported on
BH the Iu-CS interface of
the BSC6900 UMTS
Iu-PS Iu-PS transmission type Transmission type used Determined based on

on the Iu-PS interface of the network plan
the network
Iu-PS throughput PS throughput that needs It is calculated based

to be supported on the on the number of
Iu-PS interface users and traffic
model.
Iu-PS online users Number of concurrent
online users who need to
be supported the Iu-PS
interface of the
BSC6900 UMTS
Iu-PS session setup and Number of sessions that

release requirement in need to be supported on
BH the Iu-PS interface of
the BSC6900 UMTS
Configuration principles for Iub interface boards

The Iub interface can use any of the following transmission modes:
l Case 1: hybrid Iub - E1 (ATM) && Iub-Ethernet (IP)

l Case 2: hybrid Iub - E1(IP) && Iub-Ethernet(IP)

l Case 3: hybrid Iub - VC12-STM-1 (ATM) && Iub-Ethernet (IP)
l Case 4: hybrid Iub - VC4-STM-1(ATM) && Iub-Ethernet(IP)
l Case 5: hybrid Iub - VC12-STM-1 (IP) && Iub-Ethernet (IP)
l Case 6: E1 (ATM)
l Case 7: VC12 - STM-1 (ATM)
l Case 8: VC4 - STM-1 (ATM)
l Case 9: E1 (IP)
l Case 10: Ethernet (IP)
CASE11: 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,
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)
Number of Iub interface board_Bandwidth = (Iub OAM Transmission bandwidth requirement
+ MAX(Iub DL Transmission Bandwidth (data) +Iub DL Transmission 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
Number of Iub interface board_NodeB = NodeB number/NodeB Capacity per Interface Board
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
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.
Configuration principles for Iu/Iur interface boards

The Iur, Iu-CS, and Iu-PS interfaces can use any of the following transmission modes:

l Case 1: VC4-STM-1 (ATM);

l Case 2: GE Electrical (IP);
l Case 3: GE Optical (IP);
The 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
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 + Iu-PS 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 (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 requirement in BH/Capacity of session setup and session
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 requirement in BH/Capacity of session setup and session
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 Total Iur active users(CID/UDP)/Active users supported by
per interface board(CID/UDP)
= MAX(Number of Iur interface board_Traffic, Number of Iur interface board_bandwidth,

Number of Iur Interface Board_Session set-up/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.
Interface board backup mode and board calculation rules

1. BSC6900 interface boards support 1+1 backup mode. The number of interface boards is
calculated using the following formula: Sum(Iub, Iu-CS, Iu-PS, Iur) x 2.
2. The number of slots required by interface boards is equal to the total number of slots
required by interfaces Iub, Iu-CS, Iu-PS, and Iur.
NOTICE
When the RNC in Pool feature is used, Iur-p interface boars are also required. RAN17.1

4.2.6 Clock Boards
Table 4-23 Clock boards
Model Abbrev Name Function Configuration

iation Method
WP1D000GCU02 GCUb General Clock Provides Optional. When a

Unit general BSC6900 does not
clock require GPS clock
signals. signals, a pair of GCUb
boards can be
configured for the
BSC6900.
QW1D000GCG02 GCGb GPS&Clock Provides Optional. When a

Processing Unit GPS clock BSC6900 requires GPS
signals clock signals, a pair of
(including GCGb boards can be
the antenna configured for the
system). BSC6900.
By default, GCUb and GCGb are delivered.
4.2.7 General 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, GCUb/GCGb 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. If the SCUa board is used, it is
recommended that an NIUa board be configured in slots 2 to 5, 8 to 13, or 16 to 24.
5. Interface boards can be configured only in slots 14 to 27 (except slots 24 and 25 in the
MPS).
6. Service processing units (SPU, DPU, and NIU) and interface boards must be distributed
evenly among subracks to reduce the CPU and switching resources consumed during
inter-subrack switching and to prevent limitations imposed by inter-subrack bandwidth
on traffic volume. For example, if there are 9 DPUe boards, 12 SPUc pairs, 6 interface
boards, and 3 subracks, it is recommended that 3 DPUe boards, 4 SPUc pairs, and 2
interface boards be configured in each subrack. NIU boards are preferentially installed in
a subrack with a large number of DPUe boards provided that boards are evenly
distributed.
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. One SAU board is delivered by default in UMTS only or
GU mode. It is recommended that SAU boards be configured in slots 0 and 1 of the
MPS. In the MPS, slots 0 and 1 are always reserved for SAU boards.
9. It is recommended that DEUa boards be configured according to the number ratio of
DPU boards. That is, configured more DEUa boards in the subrack with more DPUe
boards.
10. The MPS supports a maximum of 9 pairs of SPUc boards and 9 DPUe boards.
11. The EPS supports a maximum of 9 pairs of SPUc boards and 9 DPUe boards.
12. It is recommended that the Iur-p interface board used for the RNC in Pool feature be
configured in the MPS.
For examples of configuration operations, see Examples of Typical Configurations in 4.2.10

Example of Typical BSC6900 UMTS Configuration.
4.2.8 Auxiliary Material Configurations

Table 4-24 describes auxiliary materials.
Table 4-24 Auxiliary materials

Model Name Function Configuration
Method
QW1P8D442003 Trunk Cable 120-ohm trunk Full configuration

cable
QW1P0STMOM00 STM-1 Optical STM-1 optical unit Full configuration

Connector
QW1P00GEOM00 GE Optical GE optical unit Full configuration

Connector
QW1P0FIBER00 Optical Fiber Optical cable Configured based on

onsite requirements
QW1P0000IM00 Installation Material Installation One installation

Package material suite material suite
configured for each
BSC6900 cabinet
(WP1B4PBCBN00)
QMAI00EDOC00 Documentation Electronic A set of electronic

documentation documentation
(QMAI00EDOC00)
delivered with each
BSC6900
l Number of trunk cables (QW1P8D442000) = [Number of ATM interface units (32 E1s)

l Number of trunk cables (QW1P8D442003) = [Number of ATM interface units (32 E1s)
l Number of STM-1 optical connectors (QW1P0STMOM00) = (WP1D000AOU01
quantity + WP1D000POU01 quantity) x 4 + WP1D000UOI01 quantity x 8
l Number of GE optical connectors (QW1P00GEOM00) = WP1D000GOU01 or
WP1D000GOU03 quantity x 4
l Number of optical fibers (QW1P0FIBER00) = (Number of STM-1 optical connectors +
Number of GE optical connectors) x 2
4.2.9 Restrictions on Inter-Subrack Switching

HW69 R11 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 in star
networking mode. HW69 R13, HW69 R15, and HW69 R16, HW69 R17 use SCUb boards. A
pair of active and standby SCUb boards can process data at 40 Gbit/s at 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, 2 SAUc
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 Iub GOUe and NIUa boards. In addition,
Iu GOUe boards are configured in the MPS as much as possible, and SAUc boards are
configured in reserved slots in MPS. The following table lists a recommended configuration.
Subrac SPUc(pa DPUe(p NIUa(pcs) Iub Iu GOUe SAUc

k ir) cs) GOUe (pair)
(pair)
MPS 2 3 1 1 1 2
EPS1 2 3 1 1 1 0
EPS2 2 3 1 1 0 0
EPS3 2 2 1 0 0 0
EPS4 2 2 0 0 0 0
EPS5 2 2 0 0 0 0

Subrac SPUc(pa DPUe(p NIUa(pcs) Iub Iu GOUe SAUc

k ir) cs) GOUe (pair)
(pair)
Total 12 15 4 3 2 2
4.2.10 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 contained in
Table 4-25.
Table 4-25 Network specifications
Specification Value
Total subscribers 800,000
Total NodeBs 600
Total cells 3000
Voice Traffic per CS voice subscriber in BH(Erlang) 0.02
CS Voice call per subscriber per BH 0.96
CS voice call duration (sec) 75
Handover times per CS call 8
Proportion of SHO for CS call 0.3
PS call per subscriber per BH 2
Handover times per PS call 5
Mean holding time (MHT) in DCH/H/FACH state per PS 52

call(sec)
Mean holding time (MHT) in PCH per PS call(sec) 0
PS channel switch times per PS call 3
Cell update times per PS call 3
Proportion of SHO for PS call 0.3
PS throughput (including R99 and HSPA, UL+DL) per PS 4500

subscriber in BH (bit/s)
NAS(Attach,Detach, LAU, RAU) and SMS per subscriber per 3.6

BH

Specification Value
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 Yes

Browsing Acceleration, WRFD-020133 P2P Downloading Rate
Control during Busy Hour, WRFD-150252 Video Service Rate
Adaption, WRFD-150253 VoIP Application Management,
WRFD-150254 Differentiated Service Based on Application
Resource Reservation, offline user experience evaluation,
WRFD-171210 Radio-Aware Video Precedence)
Experience oriented network planning and optimization required Yes
Nastar-related SAU board required Yes
GPS required Yes
WRFD-170201 Seamless Crystal Voice required Yes
WRFD-171201 Crystal Voice in Deep Coverage required Yes
Ratio of WB-AMR services 5%
Step 2 Calculate the capacity requirements. By dimension procedure, the requirement of operator can
be described as following:
1. Total Iu-PS throughput requirement (based on 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 4,500 bit/s= 3600 Mbit/s
2. 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
3. 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 = 23111
4. 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
5. 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 (bit/s) x (1 + Proportion of SHO for PS call)= 800,000 x 4,500 x (1
+ 0.3) bit/s = 4680 Mbit/s
6. 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
7. 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
8. Total NodeB number requirement (based on the sample input, the value is 600) = Total
NodeBs = 600
9. Total Cell number requirement (based on the sample input, the value is 3000)
= Total Cells= 3000
10. 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
11. Total online 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) + Mean holding time (MHT) in PCH 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 + 0) x 2/3600 + 0.02] = 39111
12. 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) } =
124800
13. 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
14. Under this traffic model, the BHCA supported by each SPUc only board is 114,578.
SPUc resources consumed per subscriber = [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
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.
15. Under this traffic model, the actual 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*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 PS throughput over The DPUe throughput in the traffic model is

throughput the Iub interface represented by a'.
a' = Total Iub PS Throughput requirement/PS
Throughput Capacity per DPUe(Mbit/s) =
4680/470 = 9.95
Iub CS CS service b' = Total Iub CS Erlang requirement/Traffic

Traffic requirements on the volume (Erl) supported by each DPUe board =
Iub interface 20800/3350 = 6.21
Active users Number of active n' = Total Active users requirement/Number of

users supported by active users supported by each DPUe board =
the Iub interface 39111/5880 = 6.65
Cell number Number of cells that c' = Total cell quantity requirement /Number of
need to be managed cells supported by each DPUe board =
by the BSC6900 3000/300 = 10
UMTS
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 license (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. Calculate the number of required SPUc/SPUb boards.
BHCA BHCA required by Calculate the BHCA capacity of SPUc board in

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

users supported on active users supported by each SPUc board =
the control plane 39111/9600 = 4.07

Online users Number of online m' = Total online users requirement/Number of

users supported on online users supported by each SPUc board =
the control plane 39111/24000 = 1.62
NodeB Number of nb' = Total NodeB number requirement/Number

number NodeBs that need of NodeBs supported by each SPUc board =
to be managed by 600/180 = 3.33
the BSC6900
UMTS
Cell number Number of cells c' = Total cell number requirement/Number of

that need to be cells supported by each SPUc board = 3000/600
managed by the =5
BSC6900 UMTS
Number of SPUc boards = Round up [Max(Total BHCA requirement/BHCA capability

supported by each SPUc board, Total active users requirement/Specifications of
activated users on an SPUc board, Number of target NodeBs/NodeB specifications on an
SPUc board, Number of target cells/Cell specifications on an SPUc board)] x2 =
Roundup [Max (20.66, 4.07, 1.62, 3.33, 5)] x 2 = 42 (SPUc boards working in active/
standby mode)
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.
Number of N_ NIUa boards = Roundup (Total Iub PS throughput requirement/NIU
specifications) = Roundup (4680/1600, 0) = 2
N_QM1SNIU50M00 = Roundup [(4680 50)/50] = 93.
NOTICE
If the corresponding optional software is not configured, N_NIUa = 0.
4. Calculate the number of DEUa boards

N_DEUa = ROUNDUP{Total IuCS Erlang requirement x Ratio of SHO user to total
user x Iub RL number per SHO user x [ Proportion of WBAMR/3600 + (1 Proportion
of WBAMR)/9000] + Total Iub CS Erlang requirement/260000 } + 1 =
ROUNDUP[16000 x 0.25 x 2.8 x (5%/3600 + 95%/9000) + 20800/260000] + 1 = 5
NOTICE
If the corresponding optional software is not configured, N_DEUa = 0.
5. Calculate the number of GOUe boards for the Iub interface.

Item Capacity Calculation of Board Quantity

Requiremen
ts
Iub transmission GE Optical N/A

type (IP)
Iub PS throughput ba = 4680 ba' = ba/PS throughput (Mbit/s) supported by

Mbit/s the GOUe in Iu-PS interface = 4680/2600 =
1.8
Iub CS Traffic bb = 20800 bb' = bb/Erlang supported by each GOUe

board = 20800/18000 = 1.16
NodeB number bn = 600 bn' = bn/Number of NodeBs supported by

each GOUe board = 600/500 = 1.2
Iub active an = 124800 an' = an/Iub UDP number supported by each

users(CID/UDP) GOUe board
=124800/129000 = 0.97
Assume that GOUe boards are configured in active/standby mode over the Iub interface.
N_IUB_ GOUe (pair) = Roundup [Max(Number of boards required for Iub PS
throughput + Number of boards required for Iub CS erlang, Number of boards required
for connections, Number of boards required for NodeBs)] = Roundup [Max(ba' + bb',
bn', an')] = Roundup [Max(1.8 + 1.16, 1.2, 0.97)] = 3 (pairs)
6. Calculate the number of GOUe boards for the Iu/Iur interface.
Inte Item Capacity Calculation of Board Quantity
rfac Requirem
e ents
Iu- Iu-CS GE Optical N/A

CS transmission type (IP)
Iu-CS traffic cb = 16,000 cb' = cb/Traffic (Erl) supported by each

GOUe board = 16000/18000 = 0.89
Iu- Iu-PS GE Optical N/A

PS transmission type (IP)
Iu-PS throughput pb = 3600 pb' = pb/PS throughput (Mbit/s) supported

by the GOUe in Iu-PS interface =
3600/3200 = 1.13
Iu-PS online users pu = 23,111 pu' = pu'/Iu-PS TEID supported by GOUe

=23111/200000 = 0.12
Iu-PS session set- ps = 1778 ps' = ps/Board specification = 1778/5000 =

up and release 0.36

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
N_GOUe (pair) = N_IUB_ GOUe + N_IUIUR_GOUe = 3+3 = 6
7. Configure SAU boards.
Reserve a pair of slots for SAU boards. By default, one SAUc board is configured for
EBC in UMTS only mode. If the customer uses Huawei Nastar or the OSS features like
SON or RAN Service Visibility Based on PRS, one or two SAUc boards are required and
can be inserted in any vacant slots.
8. Configure GCG boards.
A pair of GCGb/GCGa boards must be configured to support the GPS.
9. Calculate the number of EPSs (QM1P00UEPS01).
Number of EPSs =
Roundup [(N_SPU(23 x 2) + N_DPUe(18) + N_Iub_GOUc(6 x 2) + N_IUIUR_GOUc(3
x 2) + N_NIUa(3) + N_DEUa(2) 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).
10. 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 Abbrev Model Qua
iation ntity
Cabinet N/A WP1B4PBCBN00 2
Main Processing Subrack MPS QM1P00UMPS01 1
Extended Processing Subrack EPS QM1P00UEPS01 3
Clock board (pair) GCGb WP1D000GCU02 1
Data Processing Unit DPUe WP1D000DPU03 18
Hardware Capacity License (165 Mbit/s) N/A QM1SHW165M00 5
Hardware Capacity License (300 Mbit/s) N/A QM1SHW300M00 0
Signaling Processing Unit (pair) SPUc WP1D000SPU03 21
Network Intelligence Unit NIUa WP1D000NIU00 3
Network Intelligence Throughput License N/A QM1SNIU50M00 93
Data Enhancement Processing Unit DEUa WP1D000DEU00 3
Iub Interface Board (Pair) GOUe WP1D000GOU03 3
Iu/Iur Interface Board (Pair) GOUe WP1D000GOU03 3

Name Abbrev Model Qua

iation ntity
Signaling Access Unit SAUc WP1D000SAU01 1 or 2
To avoid inter-subrack data flow exceeding the limitation, service processing boards
must be evenly deployed among subracks. The following figure shows a recommended
configuration.
----End
4.2.11 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. 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 principles apply to BSC6900 GU new deployment and capacity expansion:
Table 4-26 BSC6900 GU basic configuration principles

Cabinet Subrack MPS Board Configuration
Configuration Configuration Configuration Specifications
Specifications Specifications Specifications
Number of GSM: a minimum of A UMTS subrack GSM and UMTS each

cabinets = 1 and a maximum of functions as the must be configured with
Roundup 4 MPS. GSM and their respective NIUa
[(Number of UMTS: a minimum UMTS boards are boards.
GSM subracks + of 1 and a maximum installed in different Two slots in the MPS
Number of of 5 subracks. must be reserved for
UMTS When the BM/TC SAU boards.
subracks)/3]. A The total number of
GSM and UMTS separated mode is
maximum of used, the MPS must
two cabinets subracks should be
less than or equal to work in GSM mode.
(excluding the
cabinets housing six.
TC subracks)
can be
configured.
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
Configurations and 4.2 BSC6900 UMTS Product Configurations.
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. 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.
The board configurations principles provided are recommended to prevent traffic flow
between subracks exceeding the bandwidth limitation between subracks.
----End
4.4 Built-in ECO6910 Product Configurations

The built-in ECO6910 can be configured in the host BSC6900 to support coordination
services and uses hardware configurations of the BSC6900. Based on the hardware

configurations of the BSC6900, calculate the number of ASUa boards and interface boards
supported by the built-in ECO6910. For details, see ECO6910 V100R004C10 Configuration
Principle.

Configuration Principle (Global) 5 Hardware Expansion and Upgrade Configurations
5 Hardware Expansion and Upgrade

Configurations
5.1 BSC6900 GSM

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

The following table lists the HW69 R17, HW69 R16, HW69 R15, HW69 R13, HW69 R11,
and HW60 R8 boards. For example, to implement TDM over STM-1 on the Abis interface,
OIUb and POUc boards can be installed. This is known as mixed insertion of boards. Note
that the SCUb and SCUa cannot be installed in the same BSC.
Hardware Board
Version
HW60 R8 DPUc, DPUd, XPUa, SCUa, TNUa, GCUa, OMUb, EIUa, FG2a, GOUa,
OIUa, and PEUa
HW69 R11 DPUc, DPUd, XPUb, SCUa, TNUa, GCUa, GCGa, OMUa, EIUa, FG2c,
GOUc, OIUa, PEUa, and POUc
HW69 R13 DPUf, DPUg, XPUb, SCUb, TNUa, GCUa, GCGa, OMUc, EIUa, FG2c,
GOUc, PEUa, POUc, SAUc, and NIUa
HW69 R15 DPUf, DPUg, XPUb, SCUb, TNUa, TNUb, GCUa, GCGa, OMUc, EIUb,
OIUb, FG2c, GOUc, PEUc, POUc, SAUc, and NIUa

Hardware Board
Version
HW69 R16 DPUf, DPUg, XPUc, SCUb, TNUb, GCUb, GCGb, OMUc, EIUb, OIUb,
FG2c, GOUe, PEUc, POUc, SAUc, and NIUa
HW69 R17 DPUf, DPUg, XPUc, SCUb, TNUb, GCUb, GCGb, OMUc, EIUb, OIUb,
FG2c, GOUe, PEUc, POUc, SAUc, and NIUa
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.
HW69 R17 inherits HW69 R16 hardware, without adding any new hardware.
l BM configuration

Model Name BM/TC Combined Mode
WP1D000FG FG2c 1. Number of FG2c boards as A interface boards = 2 x

201 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 is 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 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. The originally supported traffic must be subtracted
from the total supported traffic.
4. The number of FG2c boards to be configured is equal
to the total number of all the preceding boards.

WP1D000G GOUe 1. Number of GOUe boards as A interface boards

OU03 Number of GOUe boards as A interface boards = 2 x
ROUNDUP(((MaxACICPerBSCIP Number of
GOUa boards as A interface boards/2 x
ACICPerGOUa)/ACICPerFG2c Number of GOUc
boards as A interface boards/2), 0)
NOTE
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(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 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 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
interface. Generally, only GOUc and GOUe boards support
Gb over GE.
4. The number of GOUe boards to be configured is equal

WP1D000PO POUc 1. Number of POUc boards as A interface boards (TDM

U01 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
(MAX(AbisTDMSTM1No/STM1PortPerPOUc,
TRXNoTDMSTM1/TRXHRPerPOUcTDM), 0)
NOTE
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
When the Abis interface uses IP transmission, this board must
be configured. The quantity depends on the number of ports
and TRXs. An E1 port must be configured for each base
station by default.
6. Number of POUc boards as Gb interface boards =
2*ROUNDUP(MAX(GbFRSTM1No/
STM1PortPerPOUc,GbFRTputPerBSC/
GbTputPerPOUcFR/1024),0)
NOTE
depends on the number of base stations, the number of ports,
and the number of TRXs.
7. The number of POUc boards to be configured is equal
NOTICE
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.

WP1D000EI EIUb The EIUb has the same capacity with the EIUa, and
U01 therefore 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. An E1 port (which can be shared in
cascading networking) must be configured for each base
station by default.
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.
4. The number of EIUb boards to be configured is equal

WP1D000OI OIUb The OIUb has the same capacity with the OIUa, and
U01 therefore the OIUb inherits the configuration and capacity
expansion principles of the OIUa.
1. 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
of TRXs. In the capacity expansion scenario,
AbisTDMSTM1No indicates the additional number of ports
and TRXNoTDMSTM1 indicates the additional number of
TRXs.
An E1 port (which can be shared in cascading
networking) must be configured for each base station
by default.
3. Number of Pb interface boards = 2 x ROUNDUP
(MAX (PbTDMSTM1No/STM1PortPerOIUa, 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
NOTICE
In RAN13.0 and later versions, all OIUa boards are replaced
with POUc boards.

WP1D000PE PEUc The PEUc has the same capacity with the PEUa, and
U01 therefore the PEUa inherits the configuration and capacity
expansion principles of the PEUa.
1. 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
When the Abis interface uses IP transmission, this board must
be configured. The quantity depends on the number of ports
and TRXs. An E1 port must be configured for each base
station by default.
In the capacity expansion scenario,
SiteNoIPE1, AbisIPE1No, and TRXNoIPE1 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
interface.
In the network expansion scenario,
GbFRE1No and GbFRTputPerBSC 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 equal

WP1D000XP XPUc 1. If the number of eGBTS TRXs is not enlarged (Only

U03 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 pairs of XPUa boards. The mapping between the
number 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 traffic volume is as
follows: 1: 1720; 2: 4020; 3: 6320; 4: 8620; 5: 10920;
6: 13220. If the number of eGBTS TRXs is enlarged:
2. 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) x Number of GBTS TRX enlarged/
Number of TRX enlarged /1050000 + (Number of
BHCA enlarged - Number of BHCA for XPUa boards)
x Number of eGBTS TRXs enlarged/Number of TRX
enlarged/950000, (Traffic volume enlarged - Traffic
volume for XPUa boards)/3900), 0)
The methods for estimating the number of TRXs and
traffic volume for XPUa boards are the same as those
used when the number of eGBTS TRXs is not
enlarged.
Number of BHCA for XPUa boards: The maximum
number of BHCA is determined based on the
proportions of GBTS and eGBTS TRXs as follows:

l 1: 492000 x Number of GBTS TRXs enlarged/

Number of TRXs enlarged + 492000 x Number of
eGBTS TRXs enlarged/Number of TRXs enlarged
The methods for estimating the traffic volume for
XPUa boards are the same as those used when the
number of eGBTS TRXs is not enlarged.
If the total number of required XPUc boards after
capacity expansion is greater than the number of
existing XPUc boards, the number difference is equal
to the number of XPUc boards to be added.
WP1D000NI NIUa Configure this board only when intelligent service

U00 awareness is required. If intelligent service awareness is
required, configure one NIUa board in the MPS.

WP1D000DP DPUf 1. In BM/TC separated configuration mode (including A

U05 over IP in the case of TDM/IP hybrid transmission over
the A interface)
On the BM side:
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
(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 (including A over IP in the
case of TDM/IP hybrid transmission over the A
interface)
The DPUf providing the TC function can support the
IWF function of the same specifications as DPUf.
Extra DPUf boards should be configured to provide the
IWF function for the A-interface CICs in A over IP
mode.
(MaxACICPerBSCTDM/TCNoPerDPUf,0) + Roundup
Max (MAXIWFPerBSCIPIP -
+1
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.
Max (MAXIWFPerBSCIPIP
+1
4. All IP
Number of DPUf boards =
Roundup(MaxACICPerBSCIP / IWFNoPerDPUfIPIP,
0) +1

WP1D000DP DPUg Number of DPUg boards = Roundup (MaxPDCHPerBSC/

U06 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.
GMIPEPRA GEPS 1. Total number of interface boards

CK00 2. Total number of user-plane boards
3. Number of processing subracks =
ROUNDUP(MAX(Total number of interface boards
10/14, (Total number of interface boards + Total number of
user plane boards 18)/24, 0))
QM1B0PBC Cabinet Number of cabinets = (Number of GMPSs + Number of

BN00 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.
WP1D000EI EIUb The EIUb has the same capacity with the EIUa, and
U01 therefore the EIUb inherits the configuration and capacity
expansion principles of the EIUa.
1. 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. In the capacity expansion
scenario, MaxAterCICPerBSC indicates the additional
number of CICs on the Ater interface.
3. The number of EIUb boards to be configured is equal

WP1D000OI OIUb The OIUb has the same capacity with the OIUa, and
U01 therefore the OIUb inherits the configuration and
capacity expansion principles of the OIUa.
1. 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
MaxAterCICPerBSC indicates the additional number of
CICs on the Ater interface.
3. The number of OIUb boards to be configured is equal
NOTICE
In RAN13.0 and later versions, all OIUa boards are replaced
with POUc boards.
WP1D000PE PEUc The PEUc has the same capacity with the PEUa, and
U01 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 CICs on the A interface.
WP1D000PO POUc 1. Number of POUc boards as A interface boards (TDM

U01 transmission) = 2 x Roundup
((MaxACICPerBSCTDM Number of OIUa and
OIUb boards as A interface boards/2 x
ACICPerOIUa)/ACICPerPOUcTDM, 0)
2. Number of PEUc boards as Ater interface boards
((MaxAterCICPerBSC Number of OIUa and OIUb
boards as Ater interface boards/2 x AterCICPerOIUa)/
AterCICPerPOUcTDM, 0)
3. The number of PEUc boards to be configured is equal
WP1D000DP DPUf DPUf provides only the TC function.

U05 Number of DPUf boards = Roundup ((MaxACICPerBSC
(DPUc 1) x TCNoPerDPUc)/TCNoPerDPUf, 0)

GMIPEPRA GEPS 1. Total number of interface boards = EIUa + OIUa +

CK00 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 Cabinet Number of cabinets = (Number of GMPSs + Number of

BN00 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, the 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 through a comparison with existing boards that can be reused.
Boards that cannot be reused must be removed.
The procedure for a total replacement is as follows:
Step 1 Fill in the Unistar calculation table and calculate the configuration required after the capacity
expansion.
Step 2 Record the board and equipment configurations before the capacity expansion.
Step 3 The components required in the capacity expansion are the components after the capacity
expansion minus those before the capacity expansion.
Item Name Configuratio Configuratio Number of

n Before n After Component
Capacity Capacity s to Be
Expansion Expansion Added
1 Subracks (MPS, EPS) A1 B1 B1 A1
2 Data Processing Unit ( DPUf) A2 B2 B2 A2
3 Data Processing Unit (DPUg) A3 B3 B3 A3
4 Expansion Processing Unit A4 B4 B4 A4

(XPUc)
5 Interface boards A5 B5 B5 A5

Item Name Configuratio Configuratio Number of

n Before n After Component
Capacity Capacity s to Be
Expansion Expansion Added
6 Cabinet A6 B6 B6 A6
NOTICE
In this scenario, different versions require different points for attention.
In the case of HW69 R11 hardware capacity expansion, the following boards cannot be
reused: XPUa, FG2a and GOUa. 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. OIUa boards are replaced by POUc boards that provide higher specifications. 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 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.
The purpose of mixed insertion is to use boards of different specifications in the same
logical or physical interface.
For example,
OIUb and POUc boards can be used to 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 a total replacement 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
the 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 the capacity expansion.
Step 3 Subtract the hardware support capability before the capacity expansion from the capacity
required after the expansion. By doing this, you can obtain the capacity support capability
required for the 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.
Item Name Configuratio Maximum Increased

n Required Support Support
After the Capability Capability
Capacity Before the Required
Expansion Capacity by the
Expansion Capacity
Expansion
1 TRX support capability A1 B1 B1 A1
2 Abis E1 QTY A2 B2 B2 A2
3 A CIC QTY A3 B3 B3 A3
4 IWF QTY A4 B4 B4 A4
5 BHCA A5 B5 B5 A5
6 Gb interface traffic A6 A6 B6 A6
7 .. .. ..
Step 4 Determine the boards required by the 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

Capacity expansion can be performed using the following methods:
l Hardware expansion Configuration of hardware capacity licenses

l Configuration of hardware capacity licenses.

You can use either of or both of the two methods based on the network traffic model and
traffic volume requirements.
Capacity expansion complies with the "minimum hardware" principle.
5.2.1 Hardware Expansion and Upgrade Configurations

The following table lists the HW69 R17, HW69 R16, HW69 R15, HW69 R13, and HW69
R11 boards.
Hardware Board
Version
HW69 R11 OMUa, SCUa, GCGa, GCUa, DPUe, SPUb, AEUa, PEUa, AOUc, FG2c,
GOUc, OIUa, POUc, and 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, GCGb, GCUb, DPUe, SPUb, SPUc,
NIUa, AEUa, PEUc, AOUc, FG2c, GOUc, OIUb, POUc, UOIc, and GOUe
HW69 R16 OMUc, SAUc, SCUb, GCGb, GCUb, DPUe, SPUc, NIUa, AEUa, PEUc,
AOUc, FG2c, GOUe, OIUb, POUc, and UOIc
HW69 R17 OMUc, SAUc, SCUb, GCGb, GCUb, DPUe, SPUc, NIUa, AEUa, PEUc,
AOUc, FG2c, GOUe, OIUb, POUc, UOIc, DEUa
The following table lists the number of components to be added to the BSC6900 UMTS that
adopts the HW69 R17 hardware for capacity expansion.
Ite Name Configuration Configuration Number of

m Before After Components
Capacity Capacity to Be Added
Expansion Expansion
1 Cabinets A1 B1 B1 A1
2 MPS A2 B2 B2 A2
3 EPS A3 B3 B3 A3
4 Clock board A4 B4 B4 A4
5 Data Processing Unit A5 B5 B5 A5
6 Signaling processing unit A6 B6 B6 A6
7 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 licenses are required.
Previous hardware licenses, Hardware Capacity License (165Mbit/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.
According to the procedure described in 4.2 BSC6900 UMTS Product Configurations, the
hardware configurations before and after capacity expansion are listed in the following table.
Table 5-1 Capacity expansion from configuration 1 to configuration 2

Configuration Number Number Number Number Number
of of of DPUe of SPUc of GOUc/
Cabinets Subracks Boards Boards GOUe
Boards
Configuration 1 1 1 4 2 4
(before capacity
expansion)
Configuration 2 1 2 8 4 8
(after capacity
expansion)
Number of 0 1 4 2 4
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 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
As (670 + 2 x 165 = 1000 Mbit/s) is less than 1150 Mbit/s, Hardware Capacity License (300
Mbit/s) is required.
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 Number of
QM1SHW165M00s QM1SHW300M00s
Configuration 1 (before 0 0
capacity expansion)
Configuration 2 (after capacity 2 1

expansion)
Number of capacity licenses 2 1

to be added
5.3 BSC6900 GU
BSC6900 GU new deployment and capacity expansion comply with the following
configuration principles:
1. If the BSC and RNC use different subracks, it is recommended that the RNC subrack
serve as the basic subrack.
2. The BSC is configured with one to four subracks, whereas the RNC is configured with
one to five subracks.
3. The total number of BSC and RNC subracks cannot exceed six.
4. 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]
5. If the BSC works in BM/TC separated mode, the MPS must serve as the GSM function
subrack.
6. In GU mode, NIUa boards, which provide the service awareness function, are configured
for both GSM and UMTS modes.
7. In GU mode, one SAU board is always configured.
8. 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 and 5.2 BSC6900 UMTS.

Configuration Principle (Global) 6 Spare Parts Configurations
6 Spare Parts Configurations
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, 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%.

Configuration Principle (Global) 6 Spare Parts Configurations
(2) = 2.71828183
= Number of boards applied on the network x Annual damage rate of boards x
Replenishment period/365
The replenishment period is usually 60 days.
Quantity of boards applied on the network is the number of boards inserted in both the active
BSCs.
There are 1000 boards (BOM: 02319428) applied on the network.
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).

Configuration Principle (Global) 7 Appendix
7 Appendix
7.1 GSM Configuration Reference
7.1.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 GSM Traffic Model
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
average MO-SMSs /sub/BH 0.6
average MT-SMSs /sub/BH 1
average intra-BSC HOs /sub/BH 1.1
average inter-BSC HOs /sub/BH 0.1

Parameter Name Parameter Value
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 50%

occupied by HR voice call)
Uplink TBF Est & Rel / Second/TRX 1.75
Downlink TBF Est & Rel / Second/TRX 0.9
PS Paging / Sub/BH 1.25
1. Hardware capacity configuration in BM/TC combined mode

(1) The following table lists the capacity of a BSC6900 GSM in TDM transmission
mode. In this table, the BSC6900 GSM is configured with HW69 R17 boards and works
in BM/TC combined mode.
Table 7-2 Typical capacity of a BSC6900 GSM in TDM transmission mode (HW69 R17
boards, BM/TC combined mode)
Specifications 1 MPS 1 EPS 1 MPS+1 1 MPS+2

/Subrack EPS EPSs
Configuration
Maximum 1 1 1 1
number of
cabinets
Maximum 1,750 2,625 4,375 5,900

number of
equivalent
BHCA (k)
Maximum 6500 9750 16,250 24,000

traffic volume
(Erlang)
Maximum 1024 1536 2560 4096

number of
TRXs
Maximum 4096 6144 10,240 16,384

number of
activated packet
data channels
(PDCHs)
(MCS-9)

(2) The following table lists the capacity of a BSC6900 GSM in Abis over TDM and A
over IP mode. In this table, the BSC6900 GSM is configured with HW69 R17 boards
and works in BM/TC combined mode.
Table 7-3 Typical capacity of a BSC6900 GSM (HW69 R17 boards, Abis over TDM and
A over IP mode)
/Subrack EPS EPSs
Configuration
Maximum 1 1 1 1
number of
cabinets
Maximum 1,750 3,500 5,250 5,900

number of
equivalent
BHCA (k)
Maximum 6500 13,000 19,500 24,000

traffic volume
(Erlang)
Maximum 1024 2048 3072 4096

number of
TRXs
Maximum 4096 8192 12,288 16,384

number of
activated packet
data channels
(PDCHs)
(MCS-9)
(3) The following table lists the capacity of a BSC6900 GSM in Abis over IP and A over
IP mode. In this table, the BSC6900 GSM is configured with HW69 R17 boards and
works in BM/TC combined mode.
Table 7-4 Typical capacity of a BSC6900 GSM (HW69 R17 boards, Abis over IP and A
over IP mode)
/Subrack EPS EPSs
Configuration
Maximum 1 1 1 1
number of
cabinets


/Subrack EPS EPSs
Configuration
Maximum 1,750 6,125 7,875 11,000

number of
equivalent
BHCA (k)
Maximum 6500 22,750 29,250 45,000

traffic volume
(Erlang)
Maximum 1024 3584 4608 8192

number of
TRXs
Maximum 4096 14,336 18,432 32,768

number of
activated
PDCHs
(MCS-9)
2. Hardware capacity configuration in BM/TC separated mode

(1) The following table lists the capacity of a BSC6900 GSM. In this table, the BSC6900
GSM is configured with HW69 R17 boards and works in BM/TC separated mode with the
Abis interface not using IP transmission.
Table 7-5 Typical capacity of a BSC6900 GSM (HW69 R17 boards, BM/TC separated mode,
Abis interface not using IP transmission)
Specifications/ 1 MPS+1 TCS 1 EPS+1 TCS 1 MPS+1 EPS 1 MPS+2
Subrack +2 TCS EPSs+3 TCSs
Configuration
Maximum 2 2 2 2
number of
cabinets
Maximum 1,750 2,625 4,375 5,900

number of
equivalent
BHCA (k)
Maximum traffic 6500 9750 16,250 24,000

volume (Erlang)
Maximum 1024 1536 2560 4096

number of TRXs


Subrack +2 TCS EPSs+3 TCSs
Configuration
Maximum 4096 6144 10,240 16,384

number of
activated packet
data channels
(PDCHs)
(MCS-9)
(2) The following table lists the capacity of a BSC6900 GSM. In this table, the BSC6900
GSM is configured with HW69 R17 boards and works in BM/TC separated mode with the
Abis interface using IP transmission.
Table 7-6 Typical capacity of a BSC6900 GSM (HW69 R17 boards, BM/TC separated mode,
Abis interface using IP transmission)
Subrack +3 TCSs EPSs+3 TCSs
Configuration
Maximum 2 2 2 2
number of
cabinets
Maximum 1,750 3,500 5,250 5,900

number of
equivalent
BHCA (k)
Maximum traffic 6500 13,000 19,500 24,000

volume (Erlang)
Maximum 1024 2048 3072 4096

number of TRXs
Maximum 4096 8192 12,288 16,384

number of
activated packet
data channels
(PDCHs)
(MCS-9)

7.1.2 GSM Board Specifications

Table 7-7 Board specifications
Parameter Name Parameter Description Specificati Board
ons
TrxPerXPUaWithM- TRX support capability of the XPUa 270 XPUa

PU (with the MPU)
BHCAPerXPUaWith BHCA supported by each pair of 492,000 for

MPU XPUa boards (with MPUs) GBTS
445,000 for
eGBTS
ErlPerXPUaWithM- Traffic supported by each pair of 1720

PU XPUa boards (with MPUs) (for
reference only, not used as a
parameter for calculating the number
of required boards)
TrxPerXPUaWithout TRX support capability of each pair 360

MPU of common XPUa boards
BHCAPerXPUaWith BHCA supported by each pair of 656,000 for

outMPU common XPUa boards GBTS
590,000 for
eGBTS
ErlPerXPUaWithout Traffic supported by each pair of 2300

MPU common XPUa boards (for your
reference only, not used as a
calculation criterion)
TrxPerXPUc TRX support capability of the XPUc 640 XPUc
BHCAPerXPUc BHCA supported by each pair of 1,050,000 XPUc:

XPUc boards for GBTS BHCA
950,000 for
eGBTS
ErlPerXPUc Traffic supported by each pair of 3900 XPUc:

XPUc boards (for your reference Erlang
only, not used as a calculation
criterion)
PDCHNoPerDPUd PDCH support capability of the 1024 DPUd

DPUd
PDCHNoPerDPUg PDCH support capability of the 1024 DPUg

DPUg
IWFNoPerDPUc IWF flow processing capability of 3740 DPUc

the DPUc


ons
TCNoPerDPUc TC processing capability of the 960

DPUc
IWFNoPerDPUfTD IWF flow processing capability of 3840 DPUf

MIP the DPUf (TDM and IP)
IWFNoPerDPUfIPIP IWF flow processing capability of 7680

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

POUc
TRXHRPerPOUcTD Number of TRXs supported by the Active/ POUc:TD

M POUc in TDM transmission mode Standby M
mode: 512
ACICPerPOUcTDM Number of CIC circuits over the A 7680

interface supported by the POUc (the
TDM over packet technique is used
only on the DPUf) in TDM
transmission mode
ACICPerPOUcTDM Number of CIC circuits over the A 3906

interface supported by the POUc
(only DPUc is used or DPUc and
DPUf are used together) in TDM
transmission mode
AterCICPerPOUcTD Number of CIC circuits over the Ater 7168

M interface supported by the POUc
TRXPerPOUcIP Number of TRXs supported by the 2048 POUc: IP

POUc over the Abis interface in IP
transmission mode
ACICPerPOUcIP Number of CICs supported by the 23040

POUc over the A interface in IP
transmission mode
GbTputPerPOUcFR Throughput (Mbit/s) supported by 504 POUc:Gb

the POUc over the Gb interface in FR FR
transmission mode
E1PortPerEIUa Number of ports supported by the 32 EIUa:TD

EIUa/EIUb M
TRXHRPerEIUa Number of half-rate TRXs over the Active/

Abis interface supported by the Standby
EIUa/EIUb mode: 384


ons
AterCICPerEIUa Number of CIC circuits supported by 3840

the EIUa/EIUb over the Ater
interface
ACICPerEIUa Number of CIC circuits supported by 960

the EIUa/EIUb over the A interface
STM1PortPerOIUa Number of ports supported by the 1 OIUa:TD

OIUa/OIUb M
TRXHRPerOIUa Number of half-rate TRXs supported Active/

by the OIUa/OIUb over the Abis Standby
interface mode: 384
AterCICPerOIUa Number of CICs supported by the 7168

OIUa/OIUb over the Ater interface
ACICPerOIUa Number of CICs supported by the 1920

OIUa/OIUb over the A interface
E1PortPerPEUa Number of ports supported by the 32 PEUa

PEUa/PEUc
GbTputPerPEUaFR Throughput (Mbit/s) supported by 64 PEUa:Gb

the PEUa on the Gb interface in FR FR
transmission mode
TRXPerPEUaIP Number of TRXs supported by the 384 PEUa:IP

PEUa/PEUc over the Abis interface
in IP transmission mode
ACICperPEUaIP Number of CICs supported by the 6144

PEUa/PEUc over the A interface in
IP transmission mode
E1PortPerEIUb Number of ports supported by the 32 EIUb:TD

EIUb M
TRXHRPerEIUb Number of half-rate TRXs supported Active/

by the EIUb over the Abis interface Standby
mode: 384
AterCICPerEIUb Number of CIC circuits supported by 3840

the EIUb over the Ater interface
ACICPerEIUb Number of CIC circuits supported by 960

the EIUb over the A interface
STM1PortPerOIUb Number of ports supported by the 1 OIUb:TD

OIUb board M
TRXHRPerOIUb Number of half-rate TRXs supported Active/

by the OIUb over the Abis interface Standby
mode: 384


ons
AterCICPerOIUb Number of CIC circuits supported by 7168

the OIUb over the Ater interface
ACICPerOIUb Number of CIC circuits supported by 1920

the OIUb over the A interface
E1PortPerPEUc Number of ports supported by the 32 PEUc

PEUc board
GbTputPerPEUcFR Throughput (Mbit/s) supported by 64 PEUc:Gb

the PEUc on the Gb interface in FR FR
transmission mode
TRXPerPEUcIP Number of TRXs supported by the 384 PEUc:IP

PEUc board over the Abis interface
ACICperPEUcIP Number of CIC circuits supported by 6144

the PEUc board over the A interface
GEPortPerFG2c Number of GE ports supported by 4 FG2c

each FG2c board
FEPortPerFG2c Number of FE ports supported by the 12

FG2c
GEPortPerGOUc Number of GE ports supported by the 4 GOUc

GOUc
GEPortPerGOUe Number of GE ports supported by the 4 GOUe

GOUe
GbTputPerFG2c Throughput (Mbit/s) supported by 1024 FG2c/

each FG2c or GOUc/GOUe board GOUc/
over the Gb interface in IP GOUe
transmission mode
TRXNoPerFG2c Number of TRXs supported by the 2048

FG2c/GOUc/GOUe over the Abis
interface in IP transmission mode
ACICPerFG2c Number of CICs supported by the 23040

FG2c/GOUc/GOUe over the A
interface in IP transmission mode
LogicalPortPerFG2c Number of logical ports supported by 490

the FG2c/GOUc/GOUe in IP
transmission mode
MaxSubrackTC Maximum number of supported TC 4 TC

subracks Subrack


ons
MaxCICPerSubrackT Maximum number of CICs supported 10240

C by each TC subrack
Max64KNo7linkPerB Maximum number of 64 kbit/s 4 x 16 BSC/No.7

SC signaling links supported by each
BSC
MaxHSLNo7linkPer Maximum number of high-speed 4x8

BSC signaling links supported by each
BSC
MaxInterSubrackTD Maximum switching capability 4000 x 2 BSC/

MSwitch between subracks of the BSC. By LVDS
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.
7.1.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.
The specifications for a board indicate the capacity for a board running with long-term
stability. 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.1.4 Ater RSL Configuration Calculation Tool

Ater_RSL_Configuration_Calculation_Tool.xls
7.1.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:
Formula 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.2 UMTS Configuration Reference
7.2.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:

1. Balanced traffic model
This model applies when voice services and data services are balanced in a network.
2. 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.
3. 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,
high-PS traffic model, and smartphone traffic model are described as follows:
1. Balanced traffic model
Table 7-8 Balanced traffic model for the BSC6900 UMTS (per user during busy hours)
Item Specificati Description
ons
Voice Traffic per CS voice 20 mE 0.96 BHCA, AMR voice service

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

handovers hangover legs(others have 1 leg)


ons
Handover times per CS 8 N/A

call (SHO) (times/call)
Handover times per PS 5 N/A

NAS signaling per 3.6 Number of NAS procedures between the

subscriber per BH (times) 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% N/A
The following table lists the capacity of a BSC6900 UMTS in typical configurations. In
this table, the BSC6900 UMTS is configured with HW69 R17 boards under the balanced
traffic model.
Table 7-9 Capacity of a BSC6900 UMTS in typical configurations under the balanced
traffic model (HW69 R17 boards)
Number of CS Voice PS Service BHCA Number Numb
Subscribers Service Capacity (k) of Active er of
Capacity (Iub UL+DL) Users Online
(Erlang) (Mbit/s) Users
1,760,000 45,738 7920 5,300,00 229,000 869,000

0
NOTE
l The CS voice service capacity and PS service capacity can reach the maximum at the same
time.
l Number of Subscribers refers to the number of subscribers who have accessed the UMTS
network during peak hours.
l Number of Active Users refers to the number of users who are simultaneously in the active
state, including the CELL_DCH and CELL_FACH states.
l Number of Online Users refers to the number of users who are simultaneously online,
including the users in the CELL_DCH, CELL_FACH, CELL_PCH, and URA_PCH states.
2. High-PS traffic model

Table 7-10 High-PS traffic model for the BSC6900 UMTS (per user during busy hours)
Item Specificatio Description
ns
CS voice traffic 3 mE 0.144 BHCA, AMR voice service

volume
CS data traffic per CS 0.2 mE 0.0053 BHCA, UL: 64 kbit/s, DL: 64 kbit/s
data subscriber in BH
PS throughput 43500 bit/s 3 BHCA, UL: 64 kbit/s. DL: 384 kbit/s
Proportion of soft 30% Proportion of calls using two or more

handovers channels simultaneously to all calls
Handover times per 8 N/A

CS call (SHO) (times/
call)
Handover times per 5 N/A

PS call (SHO) (times/
call)

subscriber per BH CN and UEs, including location area
(times) updates, IMSI attach/detach occurrences,
routing area updates, GPRS attach/detach
occurrences, and SMSs
this table, the BSC6900 UMTS is configured with HW69 R17 boards under the high-PS
traffic model.
Table 7-11 Capacity of a BSC6900 UMTS in typical configurations under the high-PS
traffic model(HW69 R17 boards)
Number of CS Voice PS Service BHCA Number Number
Subscribers Service Capacity (Iub of Active of
Capacity UL+DL) Users Online
(Erlang) (Mbit/s) Users
925,000 3600 40,200 2,900,0 243,000 567,000

00

NOTE
time.
l SPUc specifications in high-PS traffic model are 112,000 BHCA.
3. Smartphone traffic model
Table 7-12 Smartphone traffic model for the BSC6900 UMTS

ons
Voice Traffic per CS voice 30 mE 0.7 BHCA, AMR voice service

subscriber in BH
PS throughput 1600 bit/s 8 BHCA
Proportion of soft 34% Proportion of calls using two or more

handovers channels simultaneously to all calls
Handover times per CS 4 N/A

Handover times per PS 1 N/A

Inter-PDCH handovers per 2.3 Including all handovers between

PS call different connected RRC states and
transmission channels per PS call

subscriber per BH (times) CN and UEs, including location area
updates, IMSI attach/detach occurrences,
routing area updates, GPRS attach/
detach occurrences, and SMSs
this table, the BSC6900 UMTS is configured with HW69 R17 boards under the
smartphone traffic model.

Table 7-13 Capacity of a BSC6900 UMTS in typical configurations under the

smartphone traffic model (HW69 R17 boards)
Number of CS Voice PS Service BHCA Number Number
Subscribers Service Capacity of Active of Online
Capacity (Iub UL Users Users
(Erlang) +DL)
(Mbit/s)
1,440,000 47,000 1860 12,800,000 230,000 869,000
NOTE
time.
l SPUc specifications in High-PS traffic model are 266,000 BHCA.
7.2.2 UMTS Hardware Specifications

Table 7-14 UMTS board specifications
Parameter Name Parameter Description Specifications Boar
d
BHCAPerSPUa BHCA supported by each 80,000 SPUa

pair of SPUa boards
NodebPerSPUa Number of NodeBs 100

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

by each pair of SPUa boards
ActiveUsersPerSPUa Number of active users 4800

SPUa boards
OnlineUsersPerSPUa Number of online users 12,000

SPUa boards
BHCAPerSPUb BHCA supported by each 124,000 SPUc/

pair of SPUc/SPUb boards SPUb


d
NodebPerSPUb Number of NodeBs 180

SPUc/SPUb boards
CellPerSPUb Number of cells supported 600

by each pair of SPUc/SPUb
boards
ActiveUsersPerSPUb Number of active users 9600

SPUc/SPUb boards
OnlineUsersPerSPUb Number of online users 24,000

SPUc/SPUb boards
CellPerDPUb Number of cells supported 150 DPUb

by each DPUb board
ErlPerDPUb Erlang supported by each 1800

DPUb board
ActiveUsersPerDPUb Number of active users 3300

supported by each DPUb
board
CellPerDPUe Number of cells supported 300 DPUe

by each DPUe board
ErlPerDPUe Erlang supported by each 3350

DPUe board
PsThtPerDPUe Real PS throughput(Mbit/s) x=PS Rab mean data

supported by each DPUe rate in active state; y =
board PsThtPerDPUe.
If x in [0, 16], y =
5.625*x
If x in [16, 40], y = 90
+ 6.67*(x-16)
If x in [40, 64], y = 250
+ 2.08*(x 40)
If x in [64, 128], y =
300 + 2.03*(x 64)
If x in [128, 196], y =
430 + 1.47*(x 128)
If x in [196, 448], y =
530+ 1.07*(x 196)
If x in [448, ], y =
800


d
ActiveUsersPerDPUe Number of active users 5880

supported by each DPUe
board
MaxInterSubrackS- Inter-subrack switching 4 SCUa

witchSCUa capability (Gbit/s) of each
pair of SCUa boards
MaxInterSubrackS- Inter-subrack switching 40 SCUb

witchSCUb capability (Gbit/s) of each
pair of SCUb boards
NodebPerAOUc Number of NodeBs 500 AOUc

supported by each AOUc
board
ErlPerAOUc Erlang supported by each 18,000

AOUc board
IubUlPsThrPerAOUc Iub UL PS throughput 300

(Mbit/s) supported by each
AOUc board
IubDlPsThrPerAOUc Iub DL PS throughput 300

AOUc board
IubUlDlPsThrPer- Iub DL and UL PS 600

AOUc throughput (Mbit/s)
supported by each AOUc
board
IuUlPsThrPerAOUc PS UL throughput (Mbit/s) 350

supported by the AOUc
board functioning as the Iu
interface board
IuDlPsThrPerAOUc PS DL throughput (Mbit/s) 350

supported by the AOUc
board functioning as the Iu
interface board
IuUlDlPsThrPerAOUc Iu DL and UL PS throughput 700

AOUc board
NodebPerUOIc Number of NodeBs 500 UOIc

supported by each UOIc
board
ErlPerUOIc Erlang supported by each 18,000

UOIc board


d
IubUlPsThrPerUOIc PS UL throughput (Mbit/s) 800

supported by the UOIc board
functioning as the Iub
interface board
IubDlPsThrPerUOIc PS DL throughput (Mbit/s) 800

interface board
IubUlDlPsThrPerUOIc PS DL and UL throughput 1200

(Mbit/s) supported by the
UOIc board functioning as
the Iub interface board
IuUlPsThrPerUOIc PS UL throughput (Mbit/s) 900

functioning as the Iu
interface board
IuDlPsThrPerUOIc PS DL throughput (Mbit/s) 900

interface board
IuUlDlPsThrPerUOIc PS DL and UL throughput 1800

(Mbit/s) supported by the
UOIc board functioning as
the Iu interface board
NodebPerGOUc/ Number of NodeBs 500 GOUc

NodebPerFG2c supported by each GOUc/ /
GOUe/FG2c board GOUe
/FG2c
ErlPerGOUc Erlang supported by each 18,000
/ErlPerFG2c GOUc/GOUe/FG2c board
SessionsPerGOUc/ IuPS Setup&Reconfigure 5000

SessionsPerFG2c Sessions number supported
by each GOUc/GOUe/FG2c
board
IubUdpPerGOUc/ Iub UDP number supported 129,000

IubUdpPerFG2c by each GOUc/GOUe/FG2c
board
IuPSTeidPerGOUc/ Iu-PS TEID number 200,000

IuPSTeidPerFG2c supported by each GOUc/
GOUe/FG2c board


d
IubUlPsThrPerGOUc/ PS UL throughput (Mbit/s) 2600

IubUlPsThrPerFG2c supported by the GOUc/
GOUe/FG2c board
interface board
IubDlPsThrPerGOUc PS DL throughput (Mbit/s) 2600

/IubDlPsThrPerFG2c supported by the GOUc/
GOUe/FG2c board
interface board
IubUlDlPsThrPer- PS throughput (Mbit/s) 2600

GOUc/ supported by the GOUc/
IubUlDlPsThrPerFG2c GOUe/FG2c board
interface board
IuUlPsThrPerGOUc/ PS UL throughput (Mbit/s) 3200

IuUlPsThrPerFG2c supported by the GOUc/
GOUe/FG2c board
interface board
IuDlPsThrPerGOUc PS DL throughput (Mbit/s) 3200

/IuDlPsThrPerFG2c supported by the GOUe/
GOUc/FG2c board
interface board
IuUlDlPsThrPerGOUc PS throughput (Mbit/s) 3200

/ supported by the GOUc/
IuUlDlPsThrPerFG2c GOUe/FG2c board
interface board
PortNumGOUc/ Number of ports supported 4

PortNumFG2c by GOUc/GOUe/FG2c
Stm1PortNumAOUc Number of STM-1 ports 4 AOUc

supported by AOUc
E1PortNumAOUc/ Number of E1/T1 ports 252/336

T1PortNumAOUc supported by AOUc
Stm1PortNumUOIc Number of STM-1 ports 8 UOIc

supported by UOIc
Stm1PortNumPOUc Number of STM-1 ports 4 POUc

supported by POUc


d
E1PortNumPOUc/ Number of E1/T1 ports 252/336

T1PortNumPOUc supported by POUc
PsThtPerNIUa PS throughput when the 3200 NIUa

NIUa board is used for
service awareness (Mbit/s)
ENPsThtPerNIUa PS throughput when the 1600

NIUa board is used for PS
service quality measurement
(Mbit/s)
NbAmrErlangPerDEU Erlang supported by each 9000 DEUa

a DEUa board enabled with
NB-AMR (12.2 kbit/s)
WbAmrErlangPerDEU Erlang supported by each 3600 DEUa

a DEUa board enabled with
WB-AMR (23.85 kbit/s)
SlvaErlangperDEUa Erlang supported by each 260000 DEUa

DEUa board enabled with
Crystal Voice in Deep
Coverage
7.3 List of Board Power Consumption

Table 7-15 lists the power consumption of BSC6900 boards.
Table 7-15 List of board power consumption
BOM Code Name Max Power Average Weight (kg)

Consumption Power
(W) Consumption
(W)
02112682 BSC6900 30 26 110.00

Cabinet
02300562 BSC6900 150 128 25.00

Subrack with
Fan box
02300636 BSC6900 150 128 7.00

Independent
Fan Subrack
03051116 GCUa 20 17 1.10
03040113 GCGa 25 21 1.18


Consumption Power
(W) Consumption
(W)
03051117 SCUa 55 46 1.20
02237111 OMUb 90 77 3.50
02237123 OMUa 120 102 4.00
02237127 OMUa 120 102 4.00
02238586 OMUa 120 102 4.00
02238587 OMUa 120 102 4.00
02238806 OMUa 120 102 4.00
02239582 SAUa 120 102 4.00
03051118 TNUa 31 27 1.00
03051816 DPUb 60 51 1.26
03051813 DPUc 49 42 1.26
03051120 DPUa 60 51 1.26
03051814 DPUd 49 42 1.26
03052799 DPUe 62 53 1.20
03051119 XPUa 75 64 1.60
03051730 SPUa 77 65 1.60
03052781 SPUb 52 44 1.50
03052780 XPUb 52 44 1.50
03052762 GOUc 66 56 1.40
03054105 GOUd 66 56 1.40
03052760 UOIc 87 74 1.50
03052759 AOUc 75 64 1.50
03052748 POUc 77 66 1.50
03052761 FG2c 85 73 1.50
03054014 FG2d 85 73 1.50
03051485 AOUa 37 32 1.30
03051488 FG2a 38 33 1.36
03051492 UOIa 30 26 1.15


Consumption Power
(W) Consumption
(W)
03051493 GOUa 37 32 1.20
03051517 POUa 43 37 1.30
03051122 OIUa 21 18 0.94
03051121 EIUa 29 24 1.16
03051484 AEUa 28 24 1.20
03051486 PEUa 28 23 1.30
03053461 OMUc 90 77 2.50
03053785 SAUc 90 77 2.50
03053067 SCUb 78 66 1.50
03053299 DPUf 70 60 1.40
03053369 DPUg 62 53 1.20
03053538 NIUa 62 53 1.20
03054112 PEUc 73 62 1.30
03054331 EIUb 26 22 1.16
03054332 OIUb 23 19 0.80
03054330 TNUb 34 29 1.23
03054333 GCUb 21 18 0.98
03040122 GCGb 22 19 1.00
03055288 XPUc 65 55 1.20
03055289 SPUc 65 55 1.20
03055293 GOUe 75 64 1.40
03055858 DEUa 70 60 1.40
03055857 ASUa 80 68 2.40

Configuration Principle (Global) 8 Acronyms and Abbreviations
8 Acronyms and Abbreviations
Table 8-1 Acronyms and Abbreviations

Acronym or Abbreviation Full Name
AMR Adaptive Multirate
ATM asynchronous transfer mode
BH busy hour
CN core network
EPS extended processing subrack
GPS Global Positioning System
Iu Interface between RNC and CN
Iub Interface between RNC and NodeB
Iur Interface between RNCs
MPS main processing subrack
NodeB Base station in WCDMA networks
Roundup The mathematical operation of rounding a number up to

the next higher integer
RNC radio network controller
STM-1 Synchronous Transfer Module level 1
TS U2000/Trace server
WB-AMR wide band adaptive multirate


BSC6900 Configuration Principle (Global) (V900R017C10 06) (PDF) - EN PDF

Uploaded by

Document Information

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) (V900R017C10 06) (PDF) - EN PDF

Uploaded by

Copyright:

Available Formats

SRAN10.1&GBSS17.1&RAN17.

Configuration Principle (Global)

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 06 (2016-03-31) Huawei Proprietary and Confidential i

Issue 06 (2016-03-31) Huawei Proprietary and Confidential ii

5 Hardware Expansion and Upgrade Configurations............................................................. 69

6 Spare Parts Configurations........................................................................................................89

8 Acronyms and Abbreviations................................................................................................. 113

Issue 06 (2016-03-31) Huawei Proprietary and Confidential iii

This chapter describes changes in different document versions.

Added Added 7.3 List of Board Power Consumption.

Deleted Deleted the BSC_Power_Consumption_Tool.xls attachment from 4.1.2

Added Added 4.1.1 Hardware Specification Redundancy.

Issue 06 (2016-03-31) Huawei Proprietary and Confidential 1

Issue 06 (2016-03-31) Huawei Proprietary and Confidential 2

Added Added 4.4 Built-in ECO6910 Product Configurations.

Issue 06 (2016-03-31) Huawei Proprietary and Confidential 3

Modified l Added DEUa boards to support the optional features WRFD-170201

Issue 06 (2016-03-31) Huawei Proprietary and Confidential 4

2.2 Version Differences

Issue 06 (2016-03-31) Huawei Proprietary and Confidential 5

Hardware Version Difference

BSC6900 V900R017C10 has the same basic specifications as BSC6900 V900R016C00.

The following table describes HW R17 hardware.

Table 2-2 HW R17 hardware

Model Board Name Working

QM1P00UMPS01 MPS Main Processing Subrack GSM&UMT

QM1P00UEPS01 EPS Extended Processing Subrack GSM&UMT

WP1D000SPU03 SPUc Signal Processing Unit GSM&UMT

WP1D000DPU03 DPUe Data Processing Unit (335 Mbit/s/3350 GSM&UMT

WP1D000NIU00 NIUa Network Intelligence Unit GSM&UMT

WP1D000AEU00 AEUa ATM Interface Unit (32 E1) UMTS

WP1D000PEU01 PEUc IP Interface Unit (32 E1) GSM&UMT

WP1D000AOU01 AOUc ATM Interface Unit (4 STM-1, UMTS

Issue 06 (2016-03-31) Huawei Proprietary and Confidential 6

Model Board Name Working

WP1D000POU01 POUc IP Interface Unit (4 STM-1, Channelized) GSM&UMT

WP1D000UOI01 UOIc ATM Interface Unit (8 STM-1, UMTS

WP1D000GOU03 GOUe IP Interface Unit (4 GE, Optical) GSM&UMT

WP1D000FG201 FG2c IP Interface Unit (12 FE/4 GE, Electric) GSM&UMT

WP1D000SAU01 SAUc Service Aware Unit GSM&UMT

WP1D000GCU02 GCUb General Clock Unit GSM&UMT

QW1D000GCG02 GCGc GPS&Clock Processing Unit GSM&UMT

WP1D000DPU05 DPUf CS Data Processing Unit (1920 CIC/3840 GSM

WP1D000DPU06 DPUg PS Data Processing Unit (1024 PDCH) GSM

WP1D000DPU03 DPUe PS Data Processing Unit (1024 PDCH) GSM&UMT

WP1D000NIU00 NIUa Network Intelligence Unit GSM&UMT

WP1D000XPU03 XPUc Expansion Processing Unit (640) GSM

WP1D000EIU01 EIUb TDM Interface Unit (32 E1/T1) GSM

WP1D000OIU01 OIUb TDM Interface Unit (1 GSM

WP1X000OMU02 OMUc Operation and Maintenance Unit GSM&UMT

WP1D000TNU01 TNUb TDM switching Unit GSM

WP1D000DEU00 DEUa Data Enhancement Processing Uint UMTS

Issue 06 (2016-03-31) Huawei Proprietary and Confidential 7

The hardware platform of the BSC6900 is characterized by high integration, high

Figure 3-1 BSC6900 N68E-22 cabinet appearance

Issue 06 (2016-03-31) Huawei Proprietary and Confidential 8

Working Mode Minimum Configuration Maximum configuration

BSC6900 GSM 1 cabinet 2 cabinets

BSC6900 UMTS 1 cabinet 2 cabinets

BSC6900 GU 1 cabinet 2 cabinets