BSC6910 Configuration Principles (V100R025C10 - 01) (PDF) - EN

SRAN19.1&GBSS25.1&RAN25.
1 BSC6910
Configuration Principles
Issue 01
Date 2023-03-07
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2023. 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: https://www.huawei.com
Email: support@huawei.com
Issue 01 (2023-03-07) Copyright © Huawei Technologies Co., Ltd. i

SRAN19.1&GBSS25.1&RAN25.1 BSC6910
Configuration Principles Contents
Contents
1 BSC6910 Configuration Principles....................................................................................... 1

1.1 Change History......................................................................................................................................................................... 2
1.2 Introduction............................................................................................................................................................................... 2
1.2.1 Overview................................................................................................................................................................................. 2
1.2.2 Version Differences and Hardware List........................................................................................................................ 2
1.3 Application Overview............................................................................................................................................................. 7
1.4 Product Configurations....................................................................................................................................................... 12
1.4.1 BSC6910 GSM Product Configurations...................................................................................................................... 12
1.4.1.1 Hardware Specification Redundancy.......................................................................................................................12
1.4.1.2 Cabinets............................................................................................................................................................................. 13
1.4.1.3 Subracks............................................................................................................................................................................ 13
1.4.1.4 License............................................................................................................................................................................... 17
1.4.1.5 Service Processing Modules........................................................................................................................................ 18
1.4.1.6 Interface Module............................................................................................................................................................ 27
1.4.1.7 General Principles for Slot Configurations............................................................................................................ 31
1.4.1.8 Auxiliary Material Configurations............................................................................................................................ 32
1.4.1.9 Example BSC6910 GSM Configuration................................................................................................................... 33
1.4.2 BSC6910 UMTS Product Configurations.................................................................................................................... 35
1.4.2.1 Cabinets............................................................................................................................................................................. 36
1.4.2.2 Subracks............................................................................................................................................................................ 37
1.4.2.3 Hardware Capacity License.........................................................................................................................................41
1.4.2.4 Service Processing Modules........................................................................................................................................ 43
1.4.2.5 Interface Boards..............................................................................................................................................................63
1.4.2.6 Configuration Principles for Interface Boards and Service Boards................................................................70
1.4.2.7 Board Redundancy Modes.......................................................................................................................................... 70
1.4.2.8 Auxiliary Materials......................................................................................................................................................... 72
1.4.2.9 Restrictions on Inter-Subrack Switching.................................................................................................................73
1.4.2.10 BSC6910 UMTS Configuration Example.............................................................................................................. 74
1.4.2.11 BSC6910 UMTS Recommended Capacity for Delivery....................................................................................84
1.4.3 BSC6910 GU Product Configurations......................................................................................................................... 85
1.5 Hardware Expansion and Upgrade Configurations................................................................................................... 87
1.5.1 BSC6910 GSM..................................................................................................................................................................... 87
1.5.1.1 Precautions....................................................................................................................................................................... 87
Issue 01 (2023-03-07) Copyright © Huawei Technologies Co., Ltd. ii

Configuration Principles Contents
1.5.1.2 Hardware Capacity License Expansion................................................................................................................... 93

1.5.1.3 Examples of Hardware Expansion............................................................................................................................ 93
1.5.2 BSC6910 UMTS...................................................................................................................................................................95
1.5.2.1 Hardware Expansion and Upgrade Configurations............................................................................................ 95
1.5.2.2 Examples of Hardware Expansion............................................................................................................................ 96
1.6 Spare Parts Configurations................................................................................................................................................ 97
1.6.1 BOM of Spare Parts.......................................................................................................................................................... 97
1.6.2 Configuration Principles for Spare Parts....................................................................................................................97
1.6.2.1 Poisson Algorithm.......................................................................................................................................................... 97
1.6.2.2 Percentage Algorithm................................................................................................................................................... 98
1.6.2.3 Notes.................................................................................................................................................................................. 98
1.7 Appendix.................................................................................................................................................................................. 99
1.7.1 GSM Configuration Reference.......................................................................................................................................99
1.7.1.1 GSM Traffic Model........................................................................................................................................................ 99
1.7.1.2 GSM Hardware Specifications................................................................................................................................. 101
1.7.2 UMTS Configuration Reference..................................................................................................................................104
1.7.2.1 UMTS Traffic Model....................................................................................................................................................104
1.7.2.2 UMTS Hardware Specifications...............................................................................................................................110
1.7.3 List of Board Power Consumption.............................................................................................................................118
1.8 Acronyms and Abbreviations.......................................................................................................................................... 120
Issue 01 (2023-03-07) Copyright © Huawei Technologies Co., Ltd. iii

Configuration Principles 1 BSC6910 Configuration Principles
1 BSC6910 Configuration Principles
Overview
This document describes the configuration principles of the BSC6910
V100R025C10.
Product Version
The following table lists the mapping between product versions and solution
versions.
Product Name Product Version Solution Version
BSC6910 V100R025C10 SRAN19.1

GBSS25.1
RAN25.1
Intended Audience
This document is intended for:
● Network operators
Organization
1.1 Change History
1.2 Introduction
1.3 Application Overview
1.4 Product Configurations
1.5 Hardware Expansion and Upgrade Configurations
1.6 Spare Parts Configurations
1.7 Appendix
1.8 Acronyms and Abbreviations
Issue 01 (2023-03-07) Copyright © Huawei Technologies Co., Ltd. 1

1.1 Change History

This section describes changes in different document versions.
01 (2023-03-07)
Compared with Draft A (2022-12-30), this issue does not include any changes.
Draft A (2022-12-30)
Compared with Issue 01 (2022-03-07) of V100R024C10, this issue does not include
any changes.
1.2 Introduction
1.2.1 Overview
This document describes the product specifications, configuration principles,
upgrade, and capacity expansion regarding BSC6910 V100R025C10.
To adapt to different application scenarios, the BSC6910 supports the following
modes:
● A BSC6910 GSM works in GSM Only (GO) mode and functions as a GSM BSC.
● A BSC6910 UMTS works in UMTS Only (UO) mode and functions as a UMTS
RNC.
● A BSC6910 GU works in GSM&UMTS (GU) mode and functions as a GSM BSC
and UMTS RNC.
1.2.2 Version Differences and Hardware List

The mobile broadband network is experiencing an exponential growth of traffic
volume, with urgent requirement of intense coordination among different services
and pacing evolution toward cloud computing system for wireless network
equipment (NE). To meet this challenge, Huawei launches its new base station
controller product, the BSC6910. It uses a hardware structure based on HW6910
R25 and a new BSC6900-based software structure.
Table 1-1 describes the version differences between HW6910 R15 and later
versions.

Table 1-1 Version differences between HW6910 R15 and later versions
Hardware Version Difference
Version
HW6910 GOUe, GCUb, and GCGb boards (in versions later than
R15 R15C00SPC580) are supported.
These boards can co-exist with GOUc, GCUa, and GCGa boards.
They have the same specifications. However, an old board and its
corresponding new board cannot work in active/standby mode.
HW6910 Added SCUc boards to expand the switching bandwidth between

R16 extension subracks and slot bandwidth.
An old board and its corresponding new board (for example,
GOUc and GOUe, GCGa and GCGb, and GCUa and GCUb) can
work in active/standby mode.
HW6910 Added the DEUa board.

R17
HW6910 Added the DEUa board.

R17 EGPUb and EXPUb boards are introduced. EGPUb boards function
as the evolved version of EGPUa boards as they have the same
specifications. The same is true for EXPUb and EXPUa boards.
HW6910 EGPUb boards are introduced. EGPUb boards function as the

R18 evolved version of ENIUa boards as they have the same
specifications.
HW6910 EXOUb boards function as the evolved version of EXOUa boards

R19 as they have the same specifications. They also can work in
active/standby mode. FG2e boards function as the evolved
version of FG2c boards as they have the same specifications.
They also can work in active/standby mode.
EOMUb boards function as the evolved version of EOMUa boards
as they have the same specifications. They also can work in
active/standby mode.
ESAUb boards function as the evolved version of ESAUa boards
as they have the same specifications. They can be housed in the
same subrack.
HW6910 EOMUb boards function as the evolved version of EOMUa boards

R20 as they have the same specifications. They also can work in
active/standby mode.
ESAUb boards function as the evolved version of ESAUa boards
as they have the same specifications. They can be housed in the
same subrack.
HW6910 Added the GOUf, GCUc, and GCGc boards. The GOUf cannot be
R22 used in pair with the GOUe/GOUc. The GCUc cannot be used in
pair with the GCUb/GCUa. The GCGc cannot be used in pair with
the GCGb/GCGa.

In the UMTS network, an RNC pool can be configured by using BSC6910s alone or
BSC6910s and BSC6900s (the RNC in Pool Node Redundancy feature). RNCs within
an RNC pool work in node redundancy and resource sharing modes.
The following table describes HW6910 R25 hardware.
Table 1-2 HW6910 R25 hardware
Model Name Description Function Application

Scenario
QM1D00EGP EGPUa Evolved General Processes GSM & UMTS

U00 Processing Unit services and
REV:a allocates
services on the
GSM UP and
CP.
QM1D0EGPU EGPUb Evolved General Processes GSM & UMTS

B00 Processing Unit services and
REV:b allocates
services on the
UP and CP, and
provides service
awareness and
PS service
quality
measurement.
QM1D00EXP EXPUa Evolved Extensible Processes GSM

U00 Processing Unit services and
REV:a allocates
services on the
GSM UP and
CP.
WP11EXPUb EXPUb Evolved Extensible Finished board- GSM

Processing Unit PARC-
REV:b WP11EXPUb-
GSM evolved
extensible
processing unit
REV: b
WP1D000DP DPUf CS Data Processing Provides TC GSM

U05 Unit (1920 CICs) processing of
CS services and
works in N+1
backup mode
QM1D00EOM EOMU Evolved Operation Provides the GSM & UMTS

U00 a and Maintenance evolved
Unit operation and
maintenance
function.


Scenario
WP11EOMUb EOMU Evolved Operation Provides the GSM & UMTS

b and Maintenance evolved
Unit operation and
maintenance
function.
QM1D00E ESAUa Evolved Service Provides GSM & UMTS

00 Aware Unit evolved service
awareness.
WP11ESAUb ESAUb Evolved Service Provides GSM & UMTS

Aware Unit evolved service
awareness.
QM1D00EXO EXOUa Evolved 10GE Evolved 10GE GSM & UMTS

U00 Optical interface optical port
Unit REV:a processing unit
WP11EXOUb EXOU Evolved 10GE Evolved 10GE GSM & UMTS

b Optical interface optical port
Unit REV:b processing unit
QM1D00ENIU ENIUa Evolved Network Provides GSM & UMTS

00 Intelligence Unit enhanced
REV:a network
intelligence
(REV: a).
WP1D000DE DEUa Data Enhancement Data UMTS

U00 Processing Unit Enhancement
Processing Unit
version a
WP1D000SCU SCUb GE Switching Provides packet GSM & UMTS

01 network and switching and
Control Unit REV:b network control
(REV: b).
WP1D000SCU SCUc GE Switching Provides packet GSM & UMTS

03 network and switching and
Control Unit REV:c network control
(REV: c).
WP1D000FG2 FG2c IP Interface Unit IP: A/ GSM & UMTS

01 REV:c (12 FE/4 GE, Abis/Lb/Gb/Iur-
Electric) g
IP: Iu/Iub/Iur/
Iur-g


Scenario
WP11FG2e FG2e IP Interface Unit IP: A/ GSM & UMTS

REV:e (12 FE/4 GE, Abis/Lb/Gb/Iur-
Electric) g
IP: Iu/Iub/Iur/
Iur-g
WP1D000GO GOUe IP Interface Unit (4 IP: A/ GSM & UMTS

U03 GE, Optical) Abis/Lb/Gb/Iur-
g
IP: Iu/Iub/Iur/
Iur-g
WP11PGOUF GOUf IP Interface Unit(4 IP: A/ GSM & UMTS

0 GE, Optical) Abis/Lb/Gb/Iur-
g
IP: Iu/Iub/Iur/
Iur-g
WP1D000AO AOUc ATM Interface Unit ATM: Iub UMTS

U01 (4 STM-1,
Channelized)
WP1D000UOI UOIc ATM Interface Unit ATM: Iu- UMTS

01 (8 STM-1, CS/Iub/Iur
Unchannelized)
WP1D000PO POUc TDM or IP Interface TDM: A/Abis GSM

U01 Unit (4 STM-1, IP over STM-1:
Channelized) Abis
WP1D000GC GCUb General Clock Unit Obtains the GSM & UMTS
U02 system clock
source,
performs the
functions of
phase-lock and
holdover, and
provides clock
signals.
QW1D000GC GCGb GPS & Clock Obtains the GSM & UMTS
G02 Processing Unit system clock
source,
performs the
functions of
phase-lock and
holdover, and
provides clock
signals.


Scenario
WP1D000GC GCUc General Clock Unit Obtains the GSM & UMTS
U03 system clock
source,
performs the
functions of
phase-lock and
holdover, and
provides clock
signals.
QW1D000GC GCGc GPS&Clock Obtains the GSM & UMTS

G03 Processing Unit system clock
source,
performs the
functions of
phase-lock and
holdover, and
provides clock
signals.
QM1B0PBCD N/A Assembly Cabinet N68E-22 GSM & UMTS

P00 cabinet
WP2B06PBCD N/A Assembly Cabinet A68-22 cabinet GSM & UMTS

P
QM1K00PBCS N/A Backplane Subrack, Subrack GSM & UMTS

00 PARCb
NOTE
A BSC6900 cannot be upgraded to the BSC6910 by upgrading the software.

New software versions are compatible with old hardware versions. For example, RAN25
software versions can work with HW6910 R15, HW6910 R16, HW6910 R21, and HW6910
R22 hardware versions.
1.3 Application Overview

The hardware platform of the BSC6910 is characterized by high integration, high
performance, and modular structure. These characteristics enable the BSC6910 to
meet networking requirements in different scenarios and provide operators with a
high-quality network at a low cost. Figure 1-1 and Figure 1-2 show the exterior
of a single-cabinet BSC6910. Figure 1-3 shows the configurations of a single-
cabinet BSC6910.

Figure 1-1 Exterior of a single-cabinet BSC6910 (N68E-22)
Figure 1-2 Exterior of a single-cabinet BSC6910 (A68-22)

Figure 1-3 BSC6910 configurations (front view and rear view)
Table 1-3 describes the maximum and minimum BSC6910 configurations in

different working modes.
Table 1-3 Maximum and minimum BSC6910 configurations in different working

modes
Working Mode Minimum Configuration Maximum Configuration
BSC6910 GSM 1 cabinet 1 cabinet

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

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

2 subracks (one for UMTS and 6 subracks (1 MPS + 5 EPSs)
the other for GSM)

Table 1-4 describes the BSC6910 specifications.
Table 1-4 BSC6910 specifications

Workin Maximum Specification Per Maximum Specification for Two
g Mode Cabinet Cabinets
BSC691 In all-IP transmission mode: N/A

0 GSM 8000 BTSs, 8000 cells, 24,000
TRXs, 150,000 Erl, 96,000
PDCHs, 52,000,000 integrated
BHCA, 8 Gbit/s PS throughput
TDM: 7000 BTSs, 7000 cells,

7000 TRXs, 43,750 traffic (Erl),
28,000 PDCHs, 15,000,000
integrated BHCA, 2.688 Gbit/s
PS throughput
BSC691 10000 NodeBs, 20000 cells, 10000 NodeBs, 20000 cells,

0 UMTS 32,000,000 BHCA, 60 Gbit/s PS 64,000,000 BHCA, 120 Gbit/s PS
throughput/125000 CS Erlang throughput/250000 CS Erlang
BSC691 UMTS (2 subracks: 1 MPS and 1 UMTS (one MPS and four EPSs)
0 GU EPS): 10,000 NodeBs, 20,000 cells,
3330 NodeBs, 6660 cells, 53,300,000 BHCA, 99.8 Gbit/s PS
21,300,000 BHCA, 39.3 Gbit/s throughput or 208,000 CS traffic
PS throughput or 82,000 CS (Erl)
traffic (Erl) GSM (three subracks: three EPSs
GSM (1 EPS): that can be configured across
● In all-IP transmission mode: cabinets):
8000 BTSs, 8000 cells, 8000 ● In all-IP transmission mode:
TRXs, 50,000 traffic (Erl), 8000 BTSs, 8000 cells, 24,000
32,000 PDCHs, 17,300,000 TRXs, 150,000 Erl, 96,000
integrated BHCA, 3 Gbit/s PS PDCHs, 52,000,000 integrated
throughput BHCA, 8 Gbit/s PS throughput
● In TDM mode: 3000 BTSs, ● In TDM mode: 7000 BTSs, 7000
3000 cells, 3000 TRXs, 18,750 cells, 7000 TRXs, 43,750 traffic
traffic (Erl), 12,000 PDCHs, (Erl), 28,000 PDCHs, 15,000,000
6,500,000 integrated BHCA, integrated BHCA, 2.688 Gbit/s
1.1 Gbit/s PS throughput PS throughput
Table 1-5 describes the BSC6910 structural specifications.

Table 1-5 BSC6910 structural specifications

Item A68-22 N68E-22 N68E-21-N
Specification Specification Specification
Dimensions (H x 2200 mm x 2200 mm x 600 2130 mm x 600 mm x

W x D) 600 mm x 800 mm x 800 mm 800 mm (83.86 in. x
mm (86.61 in. (86.61 in. x 23.62 23.62 in. x 31.50 in.)
x 23.62 in. x in. x 31.50 in.)
31.50 in.)
Weight per ≤ 400 kg (882 ≤ 400 kg (882 lb) ≤ 430 kg (948.2 lb)
cabinet lb)
Load-bearing ≥ 450 kg/m2 (0.64 bf/in.2)

capability of the
floor
Table 1-6 describes the BSC6910 power specifications.
Table 1-6 BSC6910 power specifications

Item Value
Power input –48 V DC power supply (Each subrack requires four 60 A

inputs.)
Power range –57 V to –40 V
Power consumption The cabinet power consumption equals the sum of

of a single cabinet power consumption of all subracks in the cabinet. The
maximum of power consumption per cabinet is 12000 W.
The power consumption of a typically configured cabinet
should be equal to or less than 7100 W to reduce the
impact of cabinet heat dissipation on the equipment
room.

NOTE
● The BSC specifications cannot be obtained by accumulating specifications of boards.

● The BSC 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 considered to define an equivalent
system specification.
● The specifications for each version may change.
● 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 BHCA under
Huawei traffic model. All user activities, including CS location updates, CS handovers, PS
TBF setups, PS TBF releases, and PS paging, can be converted into equivalent BHCA. This
better reflects the impact of the traffic-model change on system performance. In full
configuration, if BHCA, Erlang, and PDCH specifications reach the maximum, the
average GCUP CPU usage cannot exceed 75%, which is the flow control threshold.
● The UMTS BHCA capacity is based on smartphone traffic model, and the UMTS PS
throughput capacity is based on high-PS traffic model. For details about traffic models,
see 1.7.2.1 UMTS Traffic Model.
1.4 Product Configurations
1.4.1 BSC6910 GSM Product Configurations

This section describes hardware configurations and how to calculate the number
of required licenses when the BSC6910 is working in the GO mode.
The configurations of the BSC6910 can be divided as follows:
● Configurations of hardware, including the cabinets, subracks, general

processing units, operation and maintenance units, network intelligent units,
interface boards, and clock boards
● Hardware capacity licenses include Evolved Network Intelligence Throughput.
1.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 for processing CS user-
plane data in A over TDM mode:
Redundancy Formula for Calculating the Number of DPUf Boards
No redundancy RoundUp(MaxACICPerBSCTDM/TCNoPerDPUf,0) – Number

of existing DPUf boards + 1

Redundancy Formula for Calculating the Number of DPUf Boards
30% RoundUp(MaxACICPerBSCTDM/(TCNoPerDPUf x 70%),0) –

redundancy Number of existing DPUf boards + 1
1.4.1.2 Cabinets
Table 1-7 Cabinet configurations

Part Number Description Remarks
QM1B0PBCDP00 Cabinet N68E-22 cabinet
WP2B06PBCDP Cabinet A68-22 cabinet
To achieve maximum capacity, a BSC6910 GSM can be configured with up to three

subracks in a single cabinet. In GU mode, the three subracks can be distributed
across two cabinets.
For details about the power consumption of each board, see 1.7.3 List of Board
Power Consumption.
1.4.1.3 Subracks
Table 1-8 Subrack configurations

Part Number Name Description Function Description
QM1K00PBCS00 Subrack Unified service Processes basic

architecture basic services.
subrack
WP1M00EPEM00 Power Power input module Each subrack has its

Distributi (version: a) own power supply,
on Box which is provided by
two power distribution
boxes.
1. Provides power
supply, surge
protection, and
filtering.
2. Detects the input
power and input
voltage of a subrack.
3. Monitors the status
of air circuits and of
surge protection
circuits.

The MPS and EPS of the BSC6910 have the same physical structure. They both use
PARCb subracks. The difference is that the MPS houses the EOMUa/EOMUb/
GCUb/GCUc/GCGb/GCGc, and EGPUa/EXPUa/EGPUb/EXPUb boards (logical
function: RMP), which are not housed in the EPS.
The following table lists fixed boards in the BSC6910.
Table 1-9 Fixed board configurations

Board Logical Description Function Configuration Principle
Functio Description
n
EGPUa RMP Resource Provides the One pair of boards is

/ Management resource configured on the BSC
EXPUa Processing management in 1+1 backup mode.
/ function. The board is the same
EGPUb as that used by the
/ universal service
EXPUb processor (USP).
EOMU OMU Evolved Provides the One pair of boards is

a/ Operation and evolved configured on the BSC
EOMU Maintenance operation and in 1+1 backup mode.
b Unit maintenance Each EOMUa/EOMUb
function. board occupies two
slots.
SCUb/ SCU GE Switching Provides the PS One pair of boards is

SCUc network and switching and installed in each
Control Unit control subrack in 1+1 backup
function. mode. A maximum of
three pairs can be
configured on the BSC.
GCUb/ GCU General Clock Provides the One pair of boards is

GCUc/ unit (with general clock. configured on the BSC
GCGb/ GPS) The GCGb/ in 1+1 backup mode.
GCGc GCGc supports
the GPS
function.
Configuration Principles for the MPS

A BSC6910 must be equipped with one MPS only. The MPS configurations are as
follows:
● Slot allocation: slots 8 and 9 for boards with the logical function being RMP
(fixed); slots 10 to 13 for the EOMUa/EOMUb board (recommended); slots 14
and 15 for the GCUb/GCUc/GCGb/GCGc board; slots 20 and 21 for the SCUb/
SCUc board (fixed).
● If the GPS clock is not required, each BSC6910 is configured with two GCUb or
GCUc boards, working in 1+1 redundancy mode. If the GPS clock is required,

each BSC6910 is configured with two GCGb or GCGc boards, working in 1+1
redundancy mode.
● If the customer uses Huawei Nastar or SON equipment, one to two ESAUa
boards are required in the MPS of the BSC6910. It is recommended that the
ESAUa/ESAUb boards be installed in slots 0 to 3. Slots 0 to 3 in the MPS
should be reserved for ESAUa/ESAUb boards even if they are not configured.
● The EGPUa/EGPUb/EXPUa/EXPUb boards can be inserted in any vacant slots
that are not fixed slots. An MPS can provide 14 slots for the EGPUa/EGPUb/
EXPUa/EXPUb boards.
● The DPUf board can be inserted in any vacant slots that are not fixed slots.
The MPS can provide 14 slots for the DPUf board.
● Interface boards can be inserted only in slots 16 to 19 and slots 22 to 27. Do
not insert EGPUa/EGPUb/EXPUa/EXPUb/ESAUa/ESAUb boards into these slots.
● If the switch board SCUb and the interface board GOUe/GOUf/FG2c/FG2e/
EXOUa/EXOUb/POUc are used, the EXOUa/EXOUb board can be inserted only
to slots 16 to 19 and slots 22 to 25, and GOUe/GOUf/FG2c/FG2e/POUc is
preferentially inserted into slots 16 to 19 and slots 22 to 25, and can also
inserted to slots 26 to 27. If the SCUc is used, all interface boards GOUe/
GOUf/FG2c/FG2e/EXOUa/EXOUb/POUc can be inserted in any slot among
slots 16 to 19 and 22 to 27.
● An MPS provides 18 universal slots and 10 interface board slots. If the SCUb is
used, EXOUa/EXOUb can be inserted only in slots 16 to 19 and slots 22 to 25.
If the SCUc is used, EXOUa/EXOUb can be inserted in any slot among slots 16
to 19 and slots 22 to 27.
Configuration Principles for the EPS

● Slots 20 and 21 are reserved for the SCUb/SCUc board.
● The EGPUa/EGPUb/EXPUa/EXPUb boards can be inserted in other vacant slots.
An EPS can provide 26 slots for EGPUa/EGPUb/EXPUa/EXPUb boards.
● The DPUf board can be inserted in any vacant slots that are not fixed slots.
The EPS can provide 26 slots for the DPUf board.

● Interface boards can be inserted only in slots 14 to 19 and slots 22 to 27. Do

not insert EGPUa/EGPUb/EXPUa/EXPUb/ESAUa/ESAUb/DPUf boards into
these slots.
● If the switch board SCUb and the interface board EXOUa/EXOUb/FG2c/FG2e/
GOUe/GOUf/POUc are used, the EXOUa/EXOUb board can be inserted only in
slots 16 to 19 and slots 22 to 25, and FG2c/FG2e/GOUe/GOUf/POUc is
preferentially inserted into slots 16 to 19 and slots 22 to 25, and can also be
inserted to slots 14 to 15 and slots 26 to 27. If the SCUc is used, all interface
boards EXOUa/EXOUb/FG2c/FG2e/GOUe/GOUf/POUc can be inserted in any
slots among slots 14 to 19 and slots 22 to 27.
● An EPS provides 26 universal slots and 12 interface board slots. If the SCUb is
used, EXOUa/EXOUb can be inserted only in slots 16 to 19 and slots 22 to 25.
If the SCUc is used, EXOUa/EXOUb can be inserted in any slot among slots 14
to 19 and slots 22 to 27.
Configuration Methods for the Number of EPSs

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_1 = ROUNDUP[(Number of required EXOUa/EXOUb
boards – Number of EXOUa/EXOUb boards that can be housed in an MPS)/
Number of EXOUa/EXOUb boards that can be housed in an EPS]
Number of required EPSs_2 = ROUNDUP[(Number of required interface boards –
Number of interface boards that can be housed in an MPS)/Number of interface
boards that can be housed in an EPS]
Number of required EPSs_3 = ROUNDUP[(Number of required EGPUa/EXPUa
boards + Number of required interface boards – Number of universal slots
provided by the MPS)/Number of universal slots provided by one EPS]
NOTE
Calculate the number of EPS boards based on the SCUb configuration, regardless of
whether the SCUb or SCUc is installed.

Table 1-10 List of EPS counters
Counter Value Description
Number of EXOUa/EXOUb boards 8 N/A

housed in MPS
Number of EXOUa/EXOUb boards 8

housed in EPS
Number of interface boards housed in 10 The number of required

MPS interface boards includes
the number of EXOUa/
Number of interface boards housed in 12 EXOUb boards.
EPS
Number of universal slots in MPS 14 N/A
Number of universal slots in EPS 26
Capacity expansion
Number of required EPSs = Number of EPSs required after capacity expansion –

Number of EPSs configured before capacity expansion
Cabinet power consumption calculation
The maximum power supply of a subrack is 4000 W. The maximum power

consumption of a cabinet is 12000 W.
NOTE
● 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.
● Maximum subrack power consumption is 4000 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 4000 W per subrack. This can
save power distribution adjustment upon future capacity expansion.
● For details about the power consumption of each board, see 1.7.3 List of Board Power
Consumption.
1.4.1.4 License
Table 1-11 Hardware capacity licenses for BSC6910 V100R025C10
Abbreviation Name Description Value

Range
LGMIBHTC BSC TRX hardware Number of 0 to 24000

capacity (per TRX) simultaneously
activated carriers

Abbreviation Name Description Value

Range
LGMIBHDC BSC PDCH hardware Number of 0 to 96000

capacity (per PDCH) simultaneously
activated PDCHs
LGW1DPIHC02 Evolved Network ENIUa/EGPUb(NIU) N/A

Intelligence Processing hardware capacity
Throughput(per license
50Mbit/s)
The ENIUa/EGPUb(NIU) does not have hardware processing capability. The

Resource-BSC6910-LGW1DPIHC02-Evolved Network Intelligence Processing
Throughput(per 50Mbit/s) license must be loaded for the board. Each license
provides a processing capability of 50 Mbit/s. A maximum number of N licenses
can be loaded, where N is equal to the result of NIU processing capability divided
by 50 Mbit/s. The ENIUa/EGPUb(NIU) can process the services that require service
type awareness on GSM and UMTS sides at one time. The traffic carried on the
ENIUa/EGPUb(NIU) is the sum of traffic over GSM Gb interfaces and UMTS Iu
interfaces.
If the BSC6900 is replaced by a BSC6910, the BSC license cannot be used and
needs to be quoted again. However, the existing BTS license can be directly used
by using license adjusting tools after the BSC6910 is used.
1.4.1.5 Service Processing Modules
Table 1-12 Service processing modules

Board Logic Description Function Specificatio Remarks
al Description ns
Funct
ion
EGPUa RMP Resource Provides the This function One pair of

/ Management resource allows the boards is
EGPU Processing management resource configured on
b function. management the BSC.
of systems.


al Description ns
Funct
ion
GCUP GSM BSC Processes CS This board is The BHCA is

Control plane and PS used for calculated
and User services on control- based on
plane both the user plane and Huawei
Processing plane (UP) user-plane default traffic
and control integration. model.
plane (CP). The
specifications
are as
follows:
TRX: 1000
BTS: 600
Cell: 600
PDCH: 3000
GMC GSM BSC Provides the None If the IBCA

P Mathematics IBCA feature is
Calculation calculation required,
Processing function. GMCP boards
are required.
NASP Network Performs None If the

Assisted network Intelligent
Service Process assisted Wi-Fi
service Detection and
processing. Selection is
required,
NASP boards
must be
configured.
EGPU NIU Evolved Provides PS If the

b Network intelligent throughput enhanced
Intelligence service supported by intelligent
Unit identification. each EGPUb service
board: 8000 awareness
Mbit/s function is
required,
EGPUb
boards must
be
configured.


al Description ns
Funct
ion
EGPU GUEP Data Provides Supports Optional

b Enhancement enhanced Uplink CoMP configuration.
Processing data joint Configured
Unit processing. decoding for only for
8000 ERL GBFD-191201
NB-AMR FR Uplink CoMP
(7.4 kbit/s (Joint RX).
services) or The board
4000 ERL capacity is
WB-AMR planned
(12.65 based on the
kbit/s) Uplink CoMP
services. traffic
volume.
EXPUa RMP Resource Performs This function One pair of

/ Management resource allows the boards is
EXPUb Processing management. resource configured on
management the BSC.
of systems.
GCUP GSM BSC Processes CS This board is The BHCA is

Control plane and PS used for calculated
and User services on control- based on
plane both the user plane and Huawei
Processing plane (UP) user-plane default traffic
and control integration. model.
plane (CP). The
specifications
are as
follows:
TRX: 1000
BTS: 600
Cell: 600
PDCH: 3000


al Description ns
Funct
ion
GMC GSM BSC Provides the None The number

P Mathematics IBCA of the GMCP
Calculation calculation board is
Processing function. calculated
based on
IBCA
requirements
at network
deployment.
If the IBCA
feature is
required,
GMCP boards
are required.
ENIUa NIU Evolved Provides PS If the

Network intelligent throughput enhanced
Intelligence service supported by intelligent
Unit identification. each ENIUa service
board: 8000 awareness
Mbit/s function is
required,
ENIUa boards
must be
configured.
ESAUa SAU Evolved Provides The SAU If the

/ Service Aware evolved collects and customer has
ESAUb Unit service filters data purchased the
awareness. of service Nastar or
boards. The SON
ESAUa equipment,
reports the the SAU
data to the needs to be
Nastar. The configured on
ESAUb does the BSC. A
not support maximum of
the Nastar. two SAU
boards can be
configured on
the BSC. The
ESAUb does
not support
the Nastar.


al Description ns
Funct
ion
DPUf DPU CS Data Provides CS TC function: The DPUf

Processing service 1920 CIC board
Unit (1920 processing circuits (A supports 1920
CICs) and works in over TDM) CIC circuits
N+1 backup when non-
mode wideband
AMR coding
schemes are
used. When
wideband
AMR coding
schemes are
used, the
DPUf board
supports 960
CIC circuits.
That is, the
multi-core
board
processing
capabilities
consumed by
wideband
AMR services
are twice
those
consumed by
non-
wideband
AMR services.
WP1D DEUa Data Data Supports Optional

000DE Enhancement Enhancement Uplink CoMP configuration.
U00 Processing Processing joint Configured
Unit Unit version a decoding for only for
3000 ERL GBFD-191201
services. Uplink CoMP
(Joint RX).
The board
capacity is
planned
based on the
Uplink CoMP
traffic
volume.
By default, the following boards are delivered: EGPUb, EXPUb, and DPUf.

Configuration Principles for the Finished Board EGPUa/EGPUb/EXPUa/EXPUb

BSC6910 universal service processing boards (finished boards) consist of four types
of boards: EGPUa/EGPUb and EXPUa/EXPUb. EXPUa/EXPUb is used only for GSM
networks. A universal service processing board has logical functions of RMP, GCUP,
GMCP, and NASP, as shown in the preceding table.
● EGPUa/EGPUb/EXPUa/EXPUb can be used in both GO and GU modes. By

default, EGPUb is used.
● In UO mode, EGPUa/EGPUb can be used but EXPUa/EXPUb cannot be used.
Principles for configuring EGPUa/EGPUb/EXPUa/EXPUb (logical function type:
RMP): In GO mode, EXPUa/EXPUb/EGPUa/EGPUb can be configured as RMP.
By default, the EGPUb is configured as RMP. In GU or UO mode, only the
EGPUa/EGPUb board can function as RMP.
● Principles for configuring EGPUa/EGPUb/EXPUa/EXPUb (logical function type:
GMCP): In GO or GU mode, EXPUa/EXPUb/EGPUa/EGPUb can be configured
as GMCP. By default, the EGPUb is configured as GMCP.
● Principles for configuring EGPUa/EGPUb/EXPUa/EXPUb (logical function type:
NASP): EGPUa/EGPUb can be configured as NASP, but EXPUa/EXPUb cannot.
EGPUb (GUEP) Configuration Principles

The following table describes the network requirements during the configuration
of EGPUb (GUEP).
Item Description comment
Vco Traffic volume per CoMP Calculated based on the

user total traffic volume and the
percentage of CoMP UEs.
The specifications of EGPUb (GUEP) boards for WB-AMR and NB-AMR FR are
different, as listed in the following table.
Model NB-AMR FR (7.4 kbit/s) WB-AMR (12.65

kbit/s)
WP1D000DEU00 8000 Erlang 4000 Erlang
To deploy GBFD-191201 Uplink CoMP (Joint TX), EGPUb (GUEP) boards need to
be configured. The calculation method is as follows:
If the voice services in the network are all NB-AMR FR (7.4 kbit/s), the number of
EGPUb (GUEP) boards is calculated as follows: Number of EGPUb (GUEP) boards
= ROUNDUP(Vco/8000) + 1
If there are WB-AMR voice services on the live network, the number of EGPUb
(GUEP) boards is calculated as follows:

Number of EGPUb (GUEP) boards = ROUNDUP[Vco x Proportion of WB-AMR/

4000 + Vco x (1 – Proportion of WB-AMR)/8000] + 1
NOTE
It is recommended that EGPUb (GUEP) boards work in N+1 redundancy mode.
Configuration Principles for RMP

Only one pair of RMPs is installed in the MSP subrack in 1+1 backup mode for the
entire system.
Configuration Principles for GCUP

Configure the GCUP board based on the BSC capacity plan. The BSC6900 and
BSC6910 calculate the required number of service processing units using different
methods.
The BSC6900 calculates the numbers of CP boards (XPUa and XPUb) based on
either the number of planned TRXs or the BHCA. The numbers of PS UP boards
(DPUd and DPUg) are calculated based on the number of planned PDCHs. The
numbers of CS UP boards (DPUc and DPUf) are calculated based on the predicted
traffic.
For the BSC6910, the CP board and UP board are integrated on the GCUP board.
To calculate the number of GCUP boards, divide the site specifications and the
predicted specifications separately by the number of TRXs, number of PDCHs,
BHCA, or traffic. The maximum number among the obtained four numbers is the
number of GCUP boards. The number of standby GCUP boards can be manually
configured (recommended redundancy mode: N+1). By default, no standby GCUP
board is configured. A minimum of two GCPU boards are configured.
Item Value Description
TRX 1000 N/A

(TRXNoPerEGPU)
Cell 600
BTS 600
Traffic Volume 6250 6.25 Erl per TRX

(VoiceErlPerEGPU)
PDCH 3000 3 PDCHs per TRX

(PDCHPerEGPU)
PS Throughput 300 Mbit/s EGPUa/EGPUb/EXPUa/EXPUb: 3000 x 100

kbit/s, EGRPS2A

Equivalent BHCA 2,200,000 Calculated based on the actual Benchmark

(BHCAPerEGPU) weights (including PS)
The BHCA is calculated based on Huawei
default traffic model.
EGPUa/EGPUb/EXPUa/EXPUb supports
22,000,000 BHCAs.
By default, GCUP can be configured in N+1 redundancy mode. You can manually
configure the number of redundant GCUP boards. One BSC is configured with a
minimum of two GCUP boards.
1. Calculating the number of required EGPU boards based on the number of
TRXs:
Number of required EGPUs = ROUNDUP(TotalTRXNo/TRXNoPerEGPU, 0) –
Number of existing EGPUs + 1
Number of TRXs (TotalTRXNo): calculated based on the network plan
2. Calculating the number of required EGPU boards based on the CS user-plane
traffic volume:
Number of required EGPU boards = ROUNDUP(TotalVoiceErl/VoiceErlPerEGPU, 0)
– Number of existing EGPUs + 1
Total traffic volume (TotalVoiceErl): calculated based on the network plan
NOTE
When the VAMOS feature is enabled, the traffic volume supported by a single TRX
increases. Therefore, the number of EGPUs calculated by using the preceding formula
increases.
3. Calculating the number of required EGPU boards based on the number of PS
user-plane PDCHs:
Number of required EGPUs = ROUNDUP(TotalPDCH/PDCHPerEGPU, 0) – Number
of existing EGPUs + 1
Maximum number of activated PDCHs (TotalPDCH): calculated based on number
of users and traffic model
4. Calculating the number of required EGPU boards based on the signaling-
plane BHCA:
Number of required EGPUs = ROUNDUP(TotalBHCA/BHCAPerEGPU, 0) – Number
of existing EGPUs + 1
BHCA (TotalBHCA): calculated based on the number of users and traffic model
cells:
Number of required EGPUs = ROUNDUP(TotalCellNo/CellNoPerEGPU, 0) –


BTSs:
Number of required EGPUs = ROUNDUP(TotalBTSNo/BTSNoPerEGPU, 0) –

7. The number of required EGPU boards to be configured is equal to the

maximum value of all the values.
Configuration Principles for DPUf (A over TDM)

In A over TDM, DPUf boards must be configured to process CS user-plane data.
The number of required DPUf boards is determined based on the number of CIC
circuits. DPUf boards can work in N+1 backup mode.
Number of DPUf boards = ROUNDUP(MaxACICPerBSCTDM/TCNoPerDPUf, 0) –

Number of existing DPUf boards + 1
MaxACICPerBSCTDM indicates the maximum number of CIC circuits required for

the A interface of a BSC. It is calculated based on the traffic model.
Configuration Principles for GMCP

The GMCP board is configured based on IBCA requirements at network
deployment. If the IBCA function is enabled, the number of GMCP boards depends
on the number of TRXs that have been enabled with the IBCA function. At least
two GMCPs must be configured. A maximum of eight GMCPs are allowed.
Generally, one GMCP board in the BSC6910 supports 2000 TRXs. In this version,
the BSC6910 supports a maximum of 6000 TRXs enabled with the IBCA function.
When the IBCA function is used between BSCs, a maximum of 3000 TRXs (TRXs
for external neighboring cells that are enabled with the IBCA function) for
external neighboring cells are supported. The total number of GMCP boards is
calculated using the following formula:
Number of required GMCP boards = ROUNDUP(TotalTRXNo/2000, 0) – Number of

existing GMCP boards.
Number of TRXs Number of TRXs in Number of MCPs

External Neighboring
Cells
2000 3000 2
4000 3000 2
6000 3000 3
Configuration Principles for NASP

The NASP board is configured based on Intelligent Wi-Fi Detection and Selection
requirements at network deployment. If this feature is required, one NASP board
must be configured in each BSC.

Configuration Principles for ENIUa/EGPUb (NIU)

If the service awareness function is enabled, one ENIUa/EGPUb (NIU) board needs
to be configured for each BSC.
Configuration Principles for ESAUa/ESAUb

If the customer has purchased the Nastar/SON/RAN Service Visibility Based on
PRS equipment, the SAU needs to be configured on the BSC. A maximum of two
SAU boards can be configured on the BSC. The ESAUb board does not support
Nastar services.
1.4.1.6 Interface Module

The BSC6910 supports FE electrical ports, GE optical ports, and 10GE optical ports
in IP networking, and supports channelized STM-1 ports in TDM networking.
Table 1-13 Interface module
Model Name Description Interface Remarks
WP1D000FG201/ FG2c/ IP Interface Unit (12 IP: A/ N/A

WP11FG2e FG2e FE/4 GE, Electric) Abis/Lb/Gb/
Iur-g
WP1D000GOU03 GOUe IP Interface Unit(4 N/A
GE, Optical)
WP11PGOUF0 GOUf IP Interface Unit(4 N/A

GE, Optical)
QM1D00EXOU00 EXOUa/ Evolved 10GE Optical N/A

/WP11EXOUb EXOUb interface Unit Rev:a/b
WP1D000POU01 POUc TDM or IP Interface TDM: A/Abis N/A

Unit (4 IP over
STM-1,Channelized) STM-1: Abis
By default, the following boards are delivered: FG2e, GOUe, EXOUb, and POUc.
Table 1-14 Interface module specifications
Part Number Tran Port Port TRX A Ater Gb

smis Type No. CIC(64 CIC(16 Throug
sion K) K) hput(M
Type bit/s)
WP1D000FG2 IP FE/GE 12/4 2048 23040 N/A 2000

01/ electrical
WP11FG2e port
(FG2c/FG2e)

Part Number Tran Port Port TRX A Ater Gb

smis Type No. CIC(64 CIC(16 Throug
sion K) K) hput(M
Type bit/s)
WP1D000GO IP GE 4 2048 23040 N/A 2000

U03 (GOUe) optical
port
WP11PGOUF IP GE 4 2048 23040 N/A 2000

0 (GOUf) optical
port
QM1D00EXO IP 10 GE 2 8000 75000 N/A 8000

U00/ optical
WP11EXOUb port
(EXOUa/
EXOUb)
WP1D000PO TDM CSTM-1 4 1024 7680 N/A N/A

U01 (POUc) port
IP IP 4 2048 N/A N/A N/A

CSTM-1
NOTE
In Abis over TDM, a POUc board supports a maximum of 1024 TRXs when both of the
following conditions are met:
● The traffic model is 6.25 Erlangs per TRX. Three PDCHs are configured on each TRX on
the average and the MCS-7 is used, or two PDCHs are configured on each TRX on the
average and the MCS-9 is used.
● In fixed Abis networking, idle timeslots and monitoring timeslots must be properly
configured. Otherwise, the number of TRXs supported by the POUc cannot reach the
maximum specification.
After the VAMOS feature is enabled, extra Abis bandwidth is required, which also affects
the TRX specifications of interface boards.
Configuration principle of interface boards: The total number of required interface

boards equals the sum of interface boards required on each interface. Interface
boards work in 1+1 active/standby mode. The BSC6910 does not support the
BM/TC separated mode and therefore does not have the Ater interface. The A, Gb,
and Abis interfaces must be configured on the BM side. You are advised to
configure the A, Gb, and Abis interfaces on different interface boards.
Calculation of Abis Interface Modules

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.
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 a transmission mode/Number of TRXs supported by the interface board,

Number of ports in a transmission mode/Number of ports supported by the
interface boards), 0)
Configuration precautions:
In Abis over TDM networking, the BSC6910 supports only the POUc board, and
does not support TDM over E1/T1 interface board. If the BSC uses TDM over E1/T1
on the Abis interface, an optical-to-electrical conversion module (for example,
Huawei OSN) must be installed to convert E1/T1 signals to STM-1 signals.
The POUc must meet the following requirements:
Number of TRXs supported by the POUc x (Average number of Erlangs per TRX +
Average number of PDCHs per TRX x Number of timeslots required for PS
transmission) ≤ 16,384
The following table lists the number of timeslots required for PS transmission.
Number of Timeslots Required for Value

PS Transmission
CS-1 1
CS-2 1
CS-3 2
CS-4 2
MCS-1 1
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 1024 TRXs, the average number of Erlangs
per TRX is 6.25, 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 15,616, which is less than 16,384.
2. If a POUc supports 1024 TRXs, the average number of Erlangs per TRX is 6.25,
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 22,784, which is greater than 16,384. In this case, the number of TRXs
supported by the POUc must be reduced to 736.
3. If the BTS provides IP over E1 links, the BSC provides IP transmission links, and
the transmission equipment provides Abis interfaces for IP over E1 links, only
GE interface boards FG2c/FG2e/GOUe/GOUf, instead of the 10GE interface
board EXOUa/EXOUb, can be configured on the BSC6910.
4. If the BSC provides IP over E1 links, the POUc board must be configured in the
BSC6910.
Calculation of A Interface Modules

Select the types of interface boards based on the network plan. The number of A
interface boards is calculated based on the service capability (number of
supported CICs) using the following formula:
Number of A interface boards = 2 x ROUNDUP(ACICNumber/Number of CICs

supported by an A interface board, 0)
Configuration precautions:
In A over TDM networking, the BSC6910 supports only the POUc board (TDM over
STM-1), and does not support TDM over E1/T1 interface board. If the BSC uses
TDM over E1/T1 on the A interface, an optical-to-electrical conversion module (for
example, Huawei OSN) must be installed to convert E1/T1 signals to STM-1
signals.
Calculation of Gb Interface Modules

Select the types of interface boards based on the network plan. The number of Gb
interface boards is calculated based on the service capability (bandwidth) using
the following formula:
Number of Gb interface boards = 2 x ROUNDUP(Gb Throughput/BSC data flow

over Gb interface supported by the interface board, 0)
Calculation of Total Interface Modules

Calculate the total number of interface boards using the following formula:
Number of interface boards = Number of Abis interface boards + Number of A

interface boards + Number of Gb interface boards
Calculation of Total Interface Modules When Multiple Interfaces Share One

Interface Board
For GSM, each interface uses its own interface boards by default. The following
table lists the boards that can be shared by multiple interfaces.
Board Logical Function Interface Board Shared by Multiple

Interfaces
EXOUa/ IP (2x10GE) Can be shared by the Abis, A, and Gb

EXOUb interfaces

Board Logical Function Interface Board Shared by Multiple

Interfaces
GOUe/ IP (4xPacket over Can be shared by the Abis, A, and Gb

GOUf GE) interfaces
FG2c/FG2e IP (12xFE or 4xGE) Can be shared by the Abis, A, and Gb

interfaces
To calculate the total interface modules when multiple interfaces share one
interface board, use the following formula:
Total number of interface boards = 2 x ROUNDUP(Number of calculated Abis
interface boards + Number of calculated A interface boards + Number of
calculated Gb interface boards, 0)
Number of calculated Abis interface boards = Max (Number of TRXs in a
transmission mode/Number of TRXs supported by the interface board, Number of
ports in a transmission mode/Number of ports supported by the interface boards)
Number of calculated A interface boards = ACICNumber/Number of CICs
supported by an A interface board
Number of calculated Gb interface boards = Gb Throughput/BSC data flow over
Gb interface supported by the interface board
1.4.1.7 General Principles for Slot Configurations

In the BSC6910, EGPUa/EGPUb/EXPUa/EXPUb boards work in intra-BSC resource
pool mode. Services of TRXs connected to interface boards in a subrack are
preferentially processed by service processing units in the same subrack. If the
resources required by a subrack exceed the specified threshold, load sharing is
implemented between subracks of the BSC. The purpose is to reduce resources
used for inter-subrack switching. Boards are configured according to the following
principles:
● Ensure that interface boards and processing boards are distributed evenly
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
non-fixed slots. It is recommended that service processing units be configured
in front slots. Under a BSC, A interface boards, Abis interface boards, and
service processing units must be distributed as evenly as possible among
subracks. Configuring the same type of board in the same subrack lowers
system reliability.
● You do not have to specify the subrack and slot number for configuring M3UA
links. The number of M3UA links are greater than or equal to (recommended)
the number of EGPUa/EGPUb/EXPUa/EXPUb boards (logical function: GCUP).
● General principles for board configuration: The basic principles during
network plan and design do not change by 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 uses can use multiple
consecutive slots.
– Other basic principles during GSM network plan.
● General principles for slot restrictions: The GCGb/GCGc/GCUb/GCUc, EOMUa/
EOMUb, SCUb/SCUc, and EGPUa/EGPUb/EXPUa/EXPUb (logical function type:
RMP) boards are inserted in fixed slots. The interface boards and service
boards can be inserted in slots within a specific range. For details, see the
descriptions about subrack configurations.
1.4.1.8 Auxiliary Material Configurations

The following table lists auxiliary materials.
Table 1-15 Auxiliary materials and configuration methods

Part Number Name Description Configuration
Method
QW1P0STMOM0 STM-1 Optical Connector STM-1 Full

0 optical configuration
module (active/standby)
QW1P00GEOM00 GE Optical Connector GE optical

module
QM1P00GEOM01 10 GE Optical Connector 10GE optical Full

module configuration
QW1P0FIBER00 Optical Fiber Optical fiber Configured

based on the
number of
optical modules
QW1P0000IM00 Installation Material Installation One installation

Package material material suite
suite configured for
each BSC6910
cabinet
(WP1B4PBCBN0
0)
QMAI00EDOC00 Documentation Electronic A set of

documentati electronic
on documentation
delivered with
each BSC6910
The methods for calculating auxiliary materials are as follows:

● Number of STM-1 optical connectors (QW1P0STMOM00) = Number of POUc
boards x 4

● Number of GE optical connectors (QW1P00GEOM00) = WP1D000GOU03

quantity x 4
● Number of 10GE optical connectors (QM1P00GEOM01) = QM1D00EXOU00
quantity x 2
● Number of optical fibers (QW1P0FIBER00) = (Number of STM-1 optical
connectors + Number of GE optical connectors + Number of 10GE optical
connectors) x 2
1.4.1.9 Example BSC6910 GSM Configuration

The process for typical configuration can be carried out as follows:
Step 1 Input requirements.
The operator provides the network requirements which must include the
information contained in the following figure. Here is an example.
The input information is as follows:
Parameter Value
voice traffic /sub/BH (Erlang) 0.02
voice call duration (seconds) 60

Parameter Value
SMS/LA setup duration(seconds) 0
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
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)
Step 2 Perform the measurements.
The following figure shows the dimensions that are used for calculating the
configurations.

Item Name Specifications
1 TRX support capability A1
2 Abis GE QTY A2
3 A CIC QTY A3
4 IWF QTY A4
5 BHCA A5
6 Gb data flow A6
7 PDCH QTY A7
Step 3 Get the network capacity requirements to calculate the hardware requirements.
Item Name Configuration Before
Capacity Expansion
1 Subracks (MPS and EPS) B1
2 Evolved General Processing Unit B2

(EGPUa/EGPUb) or Evolved Extensible
Processing Unit (EGPUa/EGPUb)
3 Interface board B3
4 Cabinet B4
----End
1.4.2 BSC6910 UMTS Product Configurations

This section describes how to configure hardware and calculate the number of
required licenses when the BSC6910 works in UMTS mode.
The configurations of the BSC6910 can be divided as follows:
● Configurations of hardware, including the cabinets, subracks, general
processing units, operation and maintenance units, network intelligent units,
service awareness unit, enhanced processing unit, interface boards, and clock
boards
● Configurations of hardware capacity licenses, including licenses for "Iub Total
Throughput", "Active User" and "Evolved Network Intelligence Throughput".
The capacity of BSC6910 UMTS depends on the number of EGPUb boards, the
power consumption, and the actual hardware processing capacity under a specific
traffic model. BSC6910 UMTS with two cabinets can be configured with a
maximum of 128 EGPUb boards (excluding a pair of EGPU boards used for
resource management and the EGPUb boards used for NIU). EGPUb boards are
used for both control-plane and user-plane processing, and also function as NIU
for service awareness and PS quality evaluation. Under Huawei smartphone traffic
model, the maximum BHCA reaches 64,000,000 on the CP. Under Huawei high-PS

traffic model, the maximum PS throughput reaches 120 Gbit/s on the UP. However
the CP and UP cannot reach the maximum value at one time. The maximum
traffic volumes on the CP and UP are closely related to the traffic model. Figure
1-4 shows the relationship between the BHCA and the PS throughput.
Figure 1-4 Relationship between capacity of control plane and use plane
1.4.2.1 Cabinets
The following table describes cabinet configurations.
Table 1-16 Cabinet configurations

Part Number Description Remarks
QM1B0PBCDP00 Cabinet N68E-22 cabinet
WP2B06PBCDP Cabinet A68-22 cabinet
A BSC6910 can be configured with a maximum of two cabinets. A maximum of

three subracks can be configured in each cabinet. The number of cabinets required
is calculated as follows:
New deployment
Number of cabinets = Roundup [(Number of MPSs + Number of EPSs)/3]
The number of MPSs is 1.
Power consumption per cabinet = Roundup [SUM(Power consumption of all
boards within the cabinet + power consumption of the fan box within the
cabinet)]
When the power consumption per cabinet is higher than 7100 W, confirm with
customers whether the heat dissipation capability of the equipment room is

sufficient. where Power consumption of all boards refers to the average power
consumption.
The power consumption per subrack on the BSC6910 is 4000 W. The maximum
power consumption per cabinet on the BSC6910 is 12000 W.
NOTE
● 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.
● Maximum subrack power consumption is 4000 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 4000 W per subrack. This can
save power distribution adjustment upon future capacity expansion.
● Every subrack contains 2 fan Assemblies, each fan assembly costs 100 W.
● For details about the power consumption of each board, see 1.7.3 List of Board Power
Consumption.
Capacity expansion
Number of cabinets = Number of cabinets required after capacity expansion –
Number of cabinets configured before capacity expansion
1.4.2.2 Subracks
Table 1-17 describes subrack configurations.
Table 1-17 Subrack configurations

Part Number Nam Description Function
e Description
QM1K00PBCS00 Subra Unified service Processes basic

ck architecture basic services.
subrack

Part Number Nam Description Function

e Description
WP1M00EPEM00 Powe Power input module Each subrack of

r (version: a) the BSC6910 has
Distri its own power
butio supply, which is
n Box provided by two
power distribution
boxes.
1. Provides power
supply, surge
protection, and
filtering.
2. Detects the
input power and
input voltage of a
subrack.
3. Monitors the
status of air
circuits and of
surge protection
circuits.
The MPS and EPS of the BSC6910 have the same physical structure. They both use
the PARCb subrack. The difference is that the MPS houses the EOMUa/EOMUb/
GCUb/GCUc/GCGb/GCGc boards and EGPUa/EGPUb boards (used for resource
management), which are not housed in the EPS.
Configuration Principles for the MPS

A BSC6910 must be equipped with one MPS only. The MPS configurations are as
follows:
Slot assignment:
● Slot allocation: slots 8 and 9 for the EGPU board (fixed); slots 10 to 13 for the
EOMUa/EOMUb board (recommended); slots 14 and 15 for the GCUb/GCUc/
GCGb/GCGc board (fixed); slots 20 and 21 for the SCUb/SCUc board (fixed).
Reserve a pair of slots for the EOMUa/EOMUb board.
● If the GPS clock is not required, each BSC6910 is configured with two GCUb or
GCUc boards, working in 1+1 redundancy mode. If the GPS clock is required,
each BSC6910 is configured with two GCGb or GCGc boards, working in 1+1
redundancy mode.
● By default, one SAU board is configured for the UMTS only mode or GU mode
for EBC. If the customer uses Huawei Nastar or the features requiring the
ESAU logical function, such as EBC and SON/RAN Service Visibility Based on
PRS, additional SAU boards are required. The ESAUb board does not support
Nastar services. A maximum of two ESAUa/ESAUb boards can be configured.
The specific quantity is determined by the features requiring the ESAU logical

function. ESAUa/ESAUb boards can be inserted in any vacant slots except the
fixed slots in the MPS and the EPS. Each ESAUa/ESAUb board occupies two
slots. In the MPS, it is recommended that ESAUa/ESAUb boards be inserted
into slots 0, 1, 2, and 3. Reserve slots 0, 1, 2, and 3 for ESAUa/ESAUb boards
in the MPS.
● EGPU boards can be inserted in any vacant slots except the fixed slots. EGPU
can be EGPUa or EGPUb.
● If the SCUc is used, an ENIU board can be configured in any vacant slot
except the fixed slots. If the SCUb is used, it is recommended that an ENIU
board be configured in any slot among slots 0 to 7, 16 to 19, and 22 to 25.
ENIU can be either ENIUa or EGPUb (NIU).
● Interface boards can be inserted into only slots 16 to 19 and slots 22 to 27 in
the MPS. Therefore, install EGPU/ESAUa/ESAUb/ENIU in other slots if possible.
● If the SCUc is used, all interface boards AOUc/UOIc/GOUe/GOUf/FG2c/FG2e/
EXOUa/EXOUb can be inserted into 10 slots, including slots 16 to 19 and slots
22 to 27. If the SCUb is used and AOUc/UOIc/GOUe/GOUf/FG2c/FG2e/
EXOUa/EXOUb boards function as interface boards, EXOUa/EXOUb can be
inserted into 8 slots, including slots 16 to 19 and slots 22 to 25. GOUe/GOUf/
FG2c/FG2e is preferentially inserted into slots 16 to 19 and slots 22 to 25, and
can also be inserted into slots 26 and 27. AOUc/UOIc is preferentially inserted
into slots 26 and 27, and can also be inserted to slots 16 to 19 and slots 22 to
25.
● If the SCUc is used, the MPS can provide 10 slots for interface boards (slots 16
to 19 and slots 22 to 27 for AOUc/UOIc/GOUe/GOUf/FG2c/FG2e/EXOUa/
EXOUb). If the SCUb is used, the MPS can provide 8 slots for EXOUa/EXOUb
and 10 slots for AOUc/UOIc/GOUe/GOUf/FG2c/FG2e.
● It is recommended that DEUa boards be configured according to the number
ratio of EGPU boards. That is, configured more DEUa boards in the subrack
with more EGPU boards.
● An MPS provides 14 universal slots.
● It is recommended that the Iur-p interface board be configured in the MPS.

Configuration Principles for the EPS

● Slots 20 and 21 are reserved for the SCUb/SCUc board.
● EGPU boards can be inserted in any vacant slots except the fixed slots. The
EPS can provide 26 slots for the EGPU boards. EGPU can be EGPUa or EGPUb.
● If the SCUc is used, an ENIU board can be configured in any vacant slot
except the fixed slots. If the SCUb is used, it is recommended that an ENIU
board be configured in any slot among slots 0 to 7, 16 to 19, and 22 to 25.
ENIUs include ENIUa and EGPUb(NIU) boards.
● If the SCUb is used and AOUc/UOIc/GOUe/GOUf/FG2c/FG2e/EXOUa/EXOUb
boards function as interface boards, EXOUa/EXOUb can be inserted into 8
slots (including slots 16 to 19 and slots 22 to 25), GOUe/GOUf/FG2c/FG2e
can be inserted into 12 slots (slots 16 to 19 and slots 22 to 25 preferred, and
slots 14 and 15, and slots 26 and 27 allowed). AOUc/UOIc boards can be
preferentially inserted into slots 14 and 15, and slots 26 and 27, and can also
be inserted into slots 16 to 19 and slots 22 to 25. If the SCUc is used, all
interface boards AOUc/UOIc/GOUe/GOUf/FG2c/FG2e/EXOUa/EXOUb can be
inserted into 12 slots on the backplane, including slots 14 to 19 and slots 22
to 27.
● If the SCUb is used, the EPS can provide 8 slots for EXOUa/EXOUb and 12
slots for AOUc/UOIc/GOUe/GOUf/FG2c/FG2e. If the SCUc is used, the EPS can
provide 12 slots for AOUc/UOIc/GOUe/GOUf/FG2c/FG2e/EXOUa/EXOUb
interface boards, including slots 14 to 19 and slots 22 to 27.
● It is recommended that DEUa boards be configured according to the number
ratio of EGPU boards. That is, configured more DEUa boards in the subrack
with more EGPU boards.
● An EPS provides 26 universal slots.
NOTICE
The ENIUa, EGPUa/EGPUb, and interface boards not working in active/standby

mode can be inserted in a pair of active and standby slots.

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_1 = ROUNDUP[(Number of required EGPUa boards +

Number of required interface boards + Number of required ENIUa boards +
Number of required DEU boards – Number of universal slots provided by the
MPS)/Number of universal slots provided by the EPS]
Number of required EPSs_2 = ROUNDUP[(Number of required EXOUa/EXOUb

boards – Number of EXOUa/EXOUb boards that can be housed in an MPS)/
Number of EXOUa/EXOUb boards that can be housed in an EPS]
Number of required EPSs_3 = ROUNDUP[(Number of required interface boards –

Number of interface boards that can be housed in an MPS)/Number of interface
boards that can be housed in an EPS]
NOTE
The number of required EGPU boards does not include the number of the fixed EGPU
boards in the MPS for resource management.
Number of required EGPU boards include the number of EGPUb (NIU) boards.
Calculate the number of EPS boards based on the SCUb configuration, regardless of
whether the SCUb or SCUc is installed.
Table 1-18 List of EPS counters
Number of universal slots in MPS 14 N/A
Number of universal slots in EPS 26

housed in MPS

housed in EPS
Number of interface boards 10 The number of required

housed in MPS interface boards includes
the number of EXOUa/
Number of interface boards 12 EXOUb boards.
housed in EPS
Capacity expansion
Number of required EPSs = Number of EPSs required after capacity expansion –

Number of EPSs configured before capacity expansion
1.4.2.3 Hardware Capacity License

The BSC6910 depends on the hardware licenses listed in the following table.

Table 1-19 List of BSC6910 hardware licenses
License License Type Related Description

Identifier Board
LQW1HWCL RNC Throughput Basic EGPUa and Including CS and

03 Hardware Capacity EGPUb user- PS traffic over
license (per plane the Iub interface
50Mbit/s) capacity Max: 120 Gbit/s;
Step: 50 Mbit/s
LQW1HWCL RNC Active User Basic EGPUa and Including the

04 Hardware Capacity EGPUb number of UEs
license (per 1000 control- in Cell_DCH
Active Users) plane state and in
capacity Cell_FACH state
Max: 1,000,000;
Step: 1000
LGW1DPIHC Evolved Network Option ENIUa and Max: 120 Gbit/s;

02 Intelligence al EGPUb Step: 50 Mbit/s
Throughput (NIU)
License(per capacity
50Mbit/s)
RNC Throughput Hardware Capacity license (per 50Mbit/s)

This license corresponds to the total traffic on the service layer over the Iub
interface, including both CS and PS traffic. This license is attached to EGPU boards.
Adding this license helps increase RNC throughput on the condition that EGPU
hardware allows. Each license increases RNC throughput by 50 Mbit/s. This license
can be shared among EGPU boards working in resource pool mode under a single
RNC. It is not bound to any specific EGPU board.
If this license is unavailable, EGPU boards cannot work properly.
RNC Active User Hardware Capacity license (per 1000 Active Users)
The control item "Active User" refers to the number of users in the CELL_DCH or
CELL_FACH state. It is attached to EGPU boards. Configuring this license helps
increase the number of active users on the condition that EGPU hardware allows.
Each license increases the number of active users by 1000. This license can be
shared among EGPU boards working in resource pool mode under a single RNC. It
is not bound to any specific EGPU board.
If this license is unavailable, EGPU boards cannot work properly.
Evolved Network Intelligence Throughput License(per 50Mbit/s)
This license is intended for ENIUa/EGPUb (NIU) hardware capacity. Adding this
license helps increase the RNC capability of enhancing network intelligence on the
condition that the existing hardware capability allows. This license can be shared
among ENIUa/EGPUb (NIU) boards working in resource pool mode under a single
RNC. It is not bound to any specific ENIUa/EGPUb (NIU) board.

If this license is unavailable, ENIUa/EGPUb (NIU) boards cannot work properly.
1.4.2.4 Service Processing Modules
Table 1-20 Service processing modules
Name Descri Function Specifications Remarks

ption
EGPUa Evolve Processes Used only for the The PS throughput

(QM1D d services and user plane: 2000 specifications are
00EGP Genera allocates Mbit/s PS throughput given at the 64 kbit/s
U00) l services on or 10,050 CS Erlang, uplink rate and 384
the GSM 28,000 active users, kbit/s downlink rate
Proces UP and CP. and 70,000 online in high PS traffic
sing users model.
Unit
REV:a Used only for the The BHCA is
control plane: calculated based on
1,668,000 BHCA, Huawei Smartphone
35,000 active users, traffic model.
and 70,000 online
users
Each EGPUa board has 14 subsystems. CP and

UP occupy their respective subsystems to
provide CP and UP processing, respectively.
When the CP and UP share the same EGPUa
board, the specification of the EGPUa board is
determined based on the ratio of the CP CPU
usage to the UP CPU usage. For example, if
the CP occupies p% of the EGPUa CPU, then
PS throughput: 2000 Mbit/s x (1 – p%) (based
on high-PS traffic model) or 10050 CS Erlang
x (1 – p%)
Active users: Min (35000 x p%, 28000 x (1 – p
%))
Online users: 70,000 x p%
Cell: 700 (p% between 30% and 70%)
NodeB: 700 (p% higher than 30%)
EGPUb Evolve Processes Used only for the PS throughput is

(QM1D d services and user plane: 2000 calculated based on
0EGPU Genera allocates Mbit/s PS throughput the UL/DL rate
B00) l services on or 10,050 CS Erlang, 64/384 kbit/s.
the GSM 28,000 active users,
Proces
UP and CP. and 70,000 online
sing
users
Unit
REV:b


ption
Used only for the The BHCA is

control plane: calculated based on
1,668,000 BHCA, Huawei Smartphone
35,000 active users, traffic model.
and 70,000 online
users
Provides the service The following

awareness and PS features require the
service quality service awareness
measurement function:
functions. WRFD-020132 Web
When used for service Browsing
awareness, this Acceleration,
feature provides 8000 WRFD-020133 P2P
Mbit/s PS throughput. Downloading Rate
Control during Busy
When used for PS Hour, WRFD-150252
service quality Video Service Rate
measurement, this Adaption,
feature provides 4800 WRFD-150253 VoIP
Mbit/s PS throughput. Application
Management, and
WRFD-150254
Differentiated Service
Based on Application
Resource Reservation,
and WRFD-190202
Video Accelerator
Phase1.
The following
features require the
PS service quality
measurement
function: offline user
experience
evaluation,
WRFD-171210 Radio-
Aware Video
Precedence,
WRFD-180210 Service
Experience-based
Admission Control,
and WRFD-181203
User Experience
Improvement on
APPs.


ption
Each EGPUb board has 14 subsystems. CP and

UP occupy their respective subsystems to
provide CP and UP processing, respectively.
When the control plane and user plane share
the same EGPUb board, the specification of
the EGPUb board is determined based on the
ratio of the control-plane CPU usage to the
user-plane CPU usage. For example, if the
control plane occupies p% of the CPU of the
EGPUb board, then
PS throughput: 2000 Mbit/s x (1 – p%) (based
on high-PS traffic model) or 10050 CS Erlang
x (1 – p%)
Active users: Min (35000 x p%, 28000 x (1 – p
%))
Online users: 70,000 x p%
Cell: 700 (p% between 30% and 70%)
NodeB: 700 (p% higher than 30%)


ption
EGPUb Evolve Performs 1. Supports 34000 1. Used to support

(QM1D d enhanced Erlang CS voice WRFD-170201
0EGPU Genera data services (NB-AMR) or Seamless Crystal
B00) l processing. 16000 Erlang CS Voice. The capacity is
voice services (WB- only affected by the
Proces AMR) seamless traffic in soft
sing crystal voice coding handover state (not
Unit processing. including softer
REV:b handover).
2. Supports 164000
Erlang for Crystal 2. Used to support
Voice in Deep WRFD-171201 Crystal
Coverage. Voice in Deep
3. Supports Improved Coverage. The
Uplink Coverage for capacity is affected
SRB over DCH for by CS traffic over the
100000 users. Iub interface.
4. Supports 1600 3. Used to support
Erlang for eTrFO WRFD-180201
(enhancement of Improved Uplink
TFO/TrFO). Coverage for SRB
over DCH. The
5. Supports Uplink capacity is affected
Coverage by the number of
Improvement During CELL_DCH users.
Access for 23000
cells. 4. Used for
WRFD-011600 TFO/
6. Supports Crystal TrFO. The capacity is
Voice Coverage affected by CS traffic
Improvement by Rate over the Iu interface.
Adaption for 1500
Erlang CS voice 5. Used for
services (NB-AMR) or WRFD-181201 Uplink
750 Erlang CS voice Coverage
services (WB-AMR). Improvement During
Access. The capacity
is affected by the
number of weak-
coverage cells during
uplink access.
6. Used for
WRFD-190208 Crystal
Voice Coverage
Improvement by Rate
Adaption. The
capacity is affected
by CS traffic over the
Iu interface.


ption
ENIUa Evolve Provides Provides the service The following

(QM1D d enhanced awareness and PS features require the
00ENIU Netwo network service quality service awareness
00) rk intelligence measurement function:
Intellig (REV: a). functions. WRFD-020132 Web
ence When used for service Browsing
Unit awareness, this Acceleration,
REV:a feature provides 8000 WRFD-020133 P2P
Mbit/s PS throughput. Downloading Rate
Control during Busy
When used for PS Hour, WRFD-150252
service quality Video Service Rate
measurement, this Adaption,
feature provides 4800 WRFD-150253 VoIP
Mbit/s PS throughput. Application
Management, and
WRFD-150254
Differentiated Service
Based on Application
Resource Reservation,
and WRFD-190202
Video Accelerator
Phase1.
The following
features require the
PS service quality
measurement
function: offline user
experience
evaluation,
WRFD-171210 Radio-
Aware Video
Precedence,
WRFD-180210 Service
Experience-based
Admission Control,
and WRFD-181203
User Experience
Improvement on
APPs.


ption
ESAUa( Evolve Provides The SAU is used to If the customer has

QM1D0 d evolved collect service board purchased
0ESAU0 Service service data, filter and Nastar/SON devices
0)/ Aware awareness. aggregate data, and and the RAN service
ESAUb( Unit periodically report the visibility based on
WP11E data to the Nastar/ PRS function, the
SAUb) SON. Only ESAUa RNC must be
supports Nastar. configured with the
SAU. In UMTS only
mode or GU mode,
one SAU board is
configured by default,
and a maximum of
two SAU boards can
be configured. The
ESAUb board does
not support Nastar
services.


ption
DEUa Data Data 1. Supports 9000 1. Used to support

(WP1D Enhan Enhanceme Erlang CS voice WRFD-170201
000DE cemen nt services (NB-AMR) or Seamless Crystal
U00) t Processing 3600 Erlang CS voice Voice. The capacity is
Proces Unit version services (WB-AMR) only affected by the
sing a seamless crystal voice traffic in soft
Unit coding processing. handover state (not
2. Supports 260000 including softer
Erlang for Crystal handover).
Voice in Deep 2. Used to support
Coverage. WRFD-171201 Crystal
3. Supports Improved Voice in Deep
Uplink Coverage for Coverage. The
SRB over DCH for capacity is affected
38400 users. by CS traffic over the
Iub interface.
4. Supports 1000
Erlang for eTrFO 3. Used to support
(enhancement of WRFD-180201
TFO/TrFO). Improved Uplink
Coverage for SRB
5. Supports Uplink over DCH. The
Coverage capacity is affected
Improvement During by the number of
Access for 5000 cells. CELL_DCH users.
6. Supports Crystal 4. Used for
Voice Coverage WRFD-011600 TFO/
Improvement by Rate TrFO. The capacity is
Adaption for 1000 affected by CS traffic
Erlang CS voice over the Iu interface.
services (NB-AMR) or
500 Erlang CS voice 5. Used for
services (WB-AMR). WRFD-181201 Uplink
Coverage
Improvement During
Access. The capacity
is affected by the
number of weak-
coverage cells during
uplink access.
6. Used for
WRFD-190208 Crystal
Voice Coverage
Improvement by Rate
Adaption. The
capacity is affected
by CS traffic over the
Iu interface.

By default, EGPUb is delivered. If network intelligent units are required, EGPUb

boards are delivered by default. If enhanced service awareness units are required,
ESAUa/ESAUb boards are delivered by default. If enhanced data processing units
are required, DEUa boards are delivered by default.
NOTE
● Active User refers to users whose status is CELL_DCH or CELL_FACH.

● Online users refer to the users in the CELL_DCH, CELL_FACH, CELL_PCH, or URA_PCH
state.
The EGPU board can process services on both the user plane and control plane.
You can calculate the number of EGPU boards required by the control plane and
the number required by the user plane, and then add the two numbers to obtain
the total number of required EGPU boards. Finally, you need to check whether the
number of EGPU boards meets the requirements of NodeB quantity and cell
quantity.
NOTE
The calculated number of EGPU boards does not include the EGPU boards used for resource
management.
The calculated number of EGPU boards does not include the EGPUb(NIU) boards.

Configuration Principles for EGPU Boards Required by the User Plane and
Hardware Capacity License
Item Descrip Comment Prerequisites Calculation of
tion the Board
Quantity
Iub PS PS a Mbit/s Estimate the EGPU EGPUb_ps = a

throu through capability based on the Mbit/s/
ghput put traffic model using the Throughput
over the following method: Capacity per
Iub The calculation formula EGPUb
interfac for the EGPUb board, UP(Mbit/s)
e which has the same
specifications as the
EGPUa board, is the same
as that for the EGPUa
board.
If PS RAB mean data rate
in active state (UL+DL)
(kbit/s) takes a value in
the interval (0, 16], PS
Throughput Capacity per
EGPUb UP(Mbit/s) = PS
RAB mean data rate x 15.
If the value of PS RAB
Mean data rate in active
state (UL+DL)(kbit/s)
falls into the range (16,
40], PS Throughput
Capacity per EGPUb UP
(Mbit/s) = 240 + (PS RAB
Mean data rate – 16) x
15.4.
64], PS Throughput
9.58.
128], PS Throughput


tion the Board
Quantity

6.4.
196], PS Throughput
(Mbit/s) = 1250 + (PS
RAB Mean data rate –
128) x 4.26.
320], PS Throughput
(Mbit/s) = 1540 + (PS
RAB Mean data rate –
196) x 3.7.
If PS RAB mean data rate
in active state (UL+DL)
(kbit/s) takes a value in
the interval (320, ∞], PS
Throughput Capacity per
EGPUb UP (Mbit/s) =
2000.
Iub CS CS b Erl. N/A For EGPUb,

Traffic traffic EGPUb_cs = b/
over the 10050
Iub
interfac
e
Active Number n N/A For EGPUb,

users of EGPUb_au = n/
active 28000
users
support
ed by
the Iub
interfac
e


tion the Board
Quantity
Cell Number c. It is N/A EGPUb_cell = c/

numb of cells determined 2800
er manage based on the
d by the network
RNC plan.
NOTE
On-line user represents the number of users in the RRC connected state, including those in
the Cell_DCH, Cell_FACH, Cell_PCH, and URA_PCH states.
The number of required EGPUb UP boards is calculated using the following

formula: N_EGPUb_UP = MAX(EGPUb_ps + EGPUb_cs, EGPUb_au, EGPUb_cell)
The required RNC Throughput Hardware Capacity license is calculated using the
following formula:
N_ EGPU_Iub_License = ROUNDUP[(a + b x 12.2 x 2/1000)/50 Mbit/s]
Configuration Principles for EGPU Boards Required by the Control Plane and
Hardware Capacity License
Item Description Comment Prerequisi Calculation
tes of the Board
Quantity
BHCA BHCA required b. It is calculated The EGPUb_bhca

requirement by the based on the EGPUb = b/x
network number of users BHCA
and traffic under this
model. traffic
model is
x.
Active users Number of n. It is calculated N/A EGPUb_au =

active users based on the n/35000
supported by number of users
the Iub and traffic
interface model.
Online users Number of m. It is N/A EGPUb_ou =

online users calculated based m/70000
supported on on the number
the control of users and
plane over the traffic model.
Iu interface

Item Description Comment Prerequisi Calculation

tes of the Board
Quantity
NodeB Number of nb (It is N/A EGPUb_nb =

number NodeBs determined nb/2520
managed by based on the
the RNC network plan.)
Cell number Number of c. It is N/A EGPUb_cell =

cells managed determined c / 2800;
by the RNC based on the
network plan.
The number of EGPUb boards required for the control plane is calculated using the
following formula:
N_EGPUb_CP = Max(EGPUb_bhca, EGPUb_au, EGPUb_ou, EGPUb_nb, EGPUb_cell)
N_EGPUb_nodeb_cell = Max(nb/700, c/700)
N_EGPUb = ROUNDUP(max(N_EGPUb_CP + N_EGPUb_UP, N_EGPUb_nodeb_cell))
+1
"+1" indicates that one additional EGPUa board is required for redundancy.
The required RNC Active User Hardware Capacity is calculated using the following
formula:
N_ EGPU_ ActiveUser_License = ROUNDUP(n/1000)
Methods for configuring service processing module redundancy:
The EGPU board can process services on both the control plane and user plane. All
the EGPU boards (for both the user plane and control plane) form a resource pool.
The EGPU boards work in N+1 redundancy mode.
NOTE
EGPU boards for resource management (RMP) work in 1+1 redundancy mode.

Methods for Configuring EGPUb (NIU) Boards and the Network Intelligence
Throughput License
Item Descriptio Comment Prerequisites Calculation of
n the Board
Quantity
Iub PS PS a Mbit/s. Specifications EGPUb (NIU)_ps

throughput throughput vary = a/EGPUb
over the according to (NIU) board
Iub the function specifications
interface or feature
enabled on
the ENIU.
The EGPUb (NIU) provides the service awareness and PS service quality
measurement functions.
Functions PS Throughput Feature/Function
Service awareness 8000 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, WRFD-150254
Differentiated Service Based on
Application Resource Reservation,
and WRFD-190202 Video Accelerator
Phase1.
PS service quality 4800 Mbit/s Offline user experience evaluation,

measurement WRFD-171210 Radio-Aware Video
Precedence, WRFD-180210 Service
Experience-based Admission Control,
and WRFD-181203 User Experience
Improvement on APPs.
If the EGPUb (NIU) board is used for only the service awareness function:
Number of EGPUb (NIU) boards required: N_EGPUb (NIU) = ROUNDUP(a/8000)
+1
Network Intelligence Throughput License = ROUNDUP(a/50)
If the EGPUb (NIU) board is used for both the service awareness and PS service
quality measurement functions:
Number of EGPUb (NIU) boards required: N_EGPUb (NIU) = ROUNDUP(a/4800)
+1

Network Intelligence Throughput License = ROUNDUP(a/50)
Table 1-21 Proportions of traffic volume delivered by major bearer types and
application types (assumed conditions)
Bearer Type HTTPS HTTP (Web HTTP HTTP Others
and Browsing) (Video) (File
Application Access)
Type
Traffic 60% 22% 5% 3% 10%

Volume
Proportion
NOTICE
● The ENIUa/EGPUb (NIU) board must be configured with the Evolved Network
Intelligence Processing Throughput(per 50 Mbit/s) license to provide hardware
processing capabilities. Each license has a processing capability of 50 Mbit/s.
● When the ENIUa/EGPUb (NIU) 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.
● It is recommended that ENIUa/EGPUb (NIU) boards be configured in N+1
redundancy mode.
● The PS service quality measurement function applies to traffic carried by HTTP
and HTTPS. On most commercial networks, the proportion of traffic carried by
HTTPS is greater than 50%. When such traffic is measured, the CPU load
significantly increases.
Configuration Principles for ESAUa/ESAUb Boards

By default, one ESAUa/ESAUb board is configured for the UMTS only mode or GU
mode for EBC. If the customer uses Huawei Nastar data processing enhancement
features, such as SON/RAN Service Visibility Based on PRS, additional ESAUa/
ESAUb boards are required. A maximum of two SAU boards can be configured.
The ESAUb board does not support Nastar services. The specific quantity of
ESAUa/ESAUb boards is determined by the features requiring the data processing
enhancement features.
In terms of the deployment scenarios, the ESAUa/ESAUb board supports co-
deployment of the EBC and SON. However, the co-deployment of the two
functions and Nastar is not supported. To deploy Nastar besides the two functions,
add a new ESAUa board.

SN Deployment Number of ESAUa Number of ESAUb Boards

Scenario Boards
a Deploying only the 1 NA

Nastar
b Deploying only the 1 0

EBC or SON, or both
the EBC and SON 0 1
c Deploying the 2 NA
Nastar on the basis
of scenario b 1 1
Configuration Principles for DEUa/EGPUb (UUEP) Boards

Item Description Comment Calculation of
the Board
Quantity
Iub CS Iub CS Vco_b(Erlang) = IuCS Voice Number of DEUa

Voice traffic in Traffic x Ratio of SHO user x boards = Vco_b
Traffic in soft Iub RL number per SHO user (Erlang) x
Soft HO handover This applies only to (Proportion of
state state WRFD-170201 Seamless Crystal WB-AMR)/3600
(excluding Voice. + Vco_b(Erlang)
softer x (1 – Proportion
handover) of WB-AMR)/
(Erlang) 9000
Number of
EGPUb(UUEP)
boards = Vco_b
(Erlang) x
(Proportion of
WB-AMR) /
16000 +
Vco_b(Erlang) x
(1 – Proportion
of WB-AMR)/
34000
Iub CS CS traffic b Erl, Iub CS Erlang requirement Number of DEUa

Traffic over the Iub This applies only to boards = b/
interface WRFD-171201 Crystal Voice in 260000
Deep Coverage. Number of
EGPUb(UUEP)
boards = b/
164000


the Board
Quantity
CELL_DCH Number of This item applies only to Number of DEUa

UE UEs in the WRFD-180201 Improved Uplink boards = Total
CELL_DCH Coverage for SRB over DCH. Active users
state requirement x
Proportion of
SRB over DCH x
Proportion of
Weak Coverage
User/38400
Number of
EGPUb(UUEP)
boards = Total
Active users
requirement x
Proportion of
SRB over DCH x
Proportion of
Weak Coverage
User/100000


the Board
Quantity
Iu-CS CS traffic This item applies only to eTrFO Number of DEUa

Traffic over the Iu (enhancement of boards = Total
interface WRFD-011600 TFO/TrFO) and IuCS Erlang
WRFD-190208 Crystal Voice requirement x
Coverage Improvement by Rate Proportion of
Adaption. eTrFO Active
users/1000 +
Total IuCS Erlang
requirement x
Proportion of
Downlink Weak
Coverage CS
Users x
Proportion of
WB-AMR/500 +
Total IuCS Erlang
requirement x
Proportion of
Downlink Weak
Coverage CS
Users x (1-
Proportion of
WB-AMR)/1000
Number of
EGPUb(UUEP)
boards = Total
IuCS Erlang
requirement x
Proportion of
eTrFO Active
users/1600 +
Total IuCS Erlang
requirement x
Proportion of
Downlink Weak
Coverage CS
Users x
Proportion of
WB-AMR/750 +
Total IuCS Erlang
requirement x
Proportion of
Downlink Weak
Coverage CS
Users x (1 –
Proportion of
WB-AMR)/1500


the Board
Quantity
Weak Number of Configured only when Number of DEUa

Coverage weak- WRFD-181201 Uplink Coverage boards = Total
Cell Num coverage Improvement During Access is Cell number
cells required. requirement x
100 x Integrate
coefficient/7500
where, 100
indicates the
number of
packets sent
over the RACH
per second, and
7500 indicates
the number of
packets
processed by the
DEU per second.
Number of
EGPUb(UUEP)
boards = Total
Cell number
requirement x
100 x Integrate
coefficient/
35000
where, 100
indicates the
number of
packets sent
over the RACH
per second, and
35000 indicates
the number of
packets
processed by the
EGPUb (UUEP)
per second.


the Board
Quantity
Note:
● 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.
● Ratio of SHO user indicates the ratio of users in the soft handover state to
total users. The default value is 0.25. You can set it based on actual network
conditions.
● Iub RL number per SHO user indicates the average number of radio links
used by users in the soft handover state. The default value is 2.8, which can
be set based on network conditions.
● Proportion of SRB over DCH = 82% (default value)
● Proportion of Weak Coverage User = 30% (default value)
● Proportion of eTrFO Active users = 10% (default value)
● Integrate coefficient = 1.5% (provided that the signaling packets over RACH
accounts for 70%, RACH bandwidth usage is 43%, and the RACH packet
BLER is 5%.)
● Proportion of Downlink Weak Coverage CS Users = 10% (default value)
The specifications of DEUa boards for WB-AMR and NB-AMR are different, as
listed in the following table.
Mode Sea Seaml Crysta Improve eTrF Upli Crystal Crystal

l mles ess l d uplink O nk Voice Voice
s Crysta Voice coverage Cov Coverag Covera
Cryst l in for SRB era e ge
al Voice Deep over ge Improve Improv
Voice (WB- Cover DCH Imp ment by ement
(AM AMR) age rove Rate by Rate
R) me Adaptio Adapti
nt n on
Duri (AMR) (WB-
ng AMR)
Acc
ess
WP1 9000 3600 26000 38400 1000 500 1000 500

D000 Erlan Erlang 0 CELL_DC Erlan 0 Erlang Erlang
DEU0 g Erlang H users g cells
0
The specifications of EGPUb (UUEP) boards for different features are listed in the
following table.

Mo Seamles Seamle Crys Improve eTrFO Uplink Crys Crys

del s Crystal ss tal d uplink Coverag tal tal
Voice Crystal Voic coverage e Voic Voic
(AMR) Voice e in for SRB Improv e e
(WB- Dee over ement Cov Cov
AMR) p DCH During era era
Cov Access ge ge
erag Imp Imp
e rove rove
men men
t by t by
Rat Rat
e e
Ada Ada
ptio ptio
n n
(AM (WB
R) -
AM
R)
QM 34000 16000 164 100000 1600 23000 150 750

1D0 Erlang Erlang 000 CELL_DC Erlang cells 0 Erla
EGP Erla H users Erla ng
UB0 ng ng
0
If the WRFD-170201 Seamless Crystal Voice feature is required, configure the

DEUa/EGPUb (UUEP) 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 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. The number of EGPUb (UUEP) boards is calculated as follows:
N_EGPUb_SeamlessCryV = ROUNDUP(Vco_b/18000) + 1.
If voice services use WB-AMR on the live 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
Alternatively, the number of EGPUb (UUEP) boards is calculated as follows:
N_EGPUb_SeamlessCryV = ROUNDUP[Vco_b x Proportion of WB-AMR/7200 +
Vco_b x (1 – Proportion of WB-AMR)/18000] + 1
If the WRFD-171201 Crystal Voice in Deep Coverage feature is used, configure the
DEUa or EGPUb (UUEP) board. The calculation method is as follows:
N_DEUa_CryVDeepC = ROUNDUP(b/260000) + 1

N_EGPUb_CryVDeepC = ROUNDUP(b/153600) + 1
To use the WRFD-180201 Improved Uplink Coverage for SRB over DCH feature,
configure the DEUa or EGPUb (UUEP) board. The calculation method is as follows:
N_DEUa_SrbODchCovEnh = ROUNDUP(Total Active users requirement x
Proportion of SRB over DCH x Proportion of Weak Coverage User/38400) + 1
N_EGPUb_SrbODchCovEnh = ROUNDUP(Total Active users requirement x
Proportion of SRB over DCH x Proportion of Weak Coverage User/69120) + 1
To use the WRFD-170201 Seamless Crystal Voice, WRFD-171201 Crystal Voice in
Deep Coverage, WRFD-180201 Improved Uplink Coverage for SRB over DCH,
eTrFO (enhancement of WRFD-011600 TFO/TrFO), WRFD-181201 Uplink Coverage
Improvement During Access, and WRFD-190208 Crystal Voice Coverage
Improvement by Rate Adaption features, 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 + Total Active users requirement x
Proportion of SRB over DCH x Proportion of Weak Coverage User/38400 + Total
IuCS Erlang requirement x Proportion of eTrFO Active users/1000 + Total Cell
number requirement x 100 x Integrate coefficient/7500 + Total IuCS Erlang
requirement x Proportion of Downlink Weak Coverage CS Users x Proportion of
WB-AMR/500 + Total IuCS Erlang requirement x Proportion of Downlink Weak
Coverage CS Users x (1- Proportion of WB-AMR)/1000] + 1
The number of EGPUb (UUEP) boards is calculated as follows:
N_EGPUb (UUEP) = ROUNDUP[MAX((Vco_b x Proportion of WB-AMR/16000 +
Vco_b x (1 – Proportion of WB-AMR)/34000 + b/164000 + Total Active users
requirement x Proportion of SRB over DCH x Proportion of Weak Coverage User/
100000 + Total Cell number requirement x 100 x Integrate coefficient/35000),
(Total IuCS Erlang requirement x Proportion of Downlink Weak Coverage CS Users
x (1 – Proportion of WB-AMR)/1500 + Total IuCS Erlang requirement x Proportion
of Downlink Weak Coverage CS Users x Proportion of WB-AMR/750 + Total IuCS
Erlang requirement x Proportion of eTrFO Active users/1600))] + 1
NOTE
It is recommended that DEUa/EGPUb (UUEP) boards work in N+1 redundancy mode.
1.4.2.5 Interface Boards

The BSC6910 supports the following interfaces: GE electrical interface GE optical
interface 10GE optical interface Channelized STM-1 interface Unchannelized
STM-1 interface
Table 1-22 Interface boards
Interface Board Description Interface Remarks
GOUc/GOUe IP Interface Unit (4 GE, Iub/Iu- NA

(WP1D000GOU03)/ Optical) CS/Iu-
GOUf PS/Iur/Iur-
(WP11PGOUF0) P

Interface Board Description Interface Remarks
FG2c/FG2e IP Interface Unit (12 Iub/Iu- NA

(WP1D000FG201/ FE/4 GE, Electric) CS/Iu-
WP11FG2e) PS/Iur/Iur-
P
AOUc ATM Interface Unit (4 Iub NA

(WP1D000AOU01) STM-1, Channelized)
UOIc ATM Interface Unit (8 Iub/Iu- NA

(WP1D000UOI01) STM-1, Unchannelized) CS/Iur
EXOUa Evolved 10GE Optical Iub/Iu-CS/ NA

(QM1D00EXOU00)/ interface Unit (2 10GE) IuP-S/Iur/
EXOUb Iur-P
(WP11EXOUb)
NOTE
The Iur-p interface is used when the RNC in Pool feature is enabled.
The following interface boards are delivered by default: GOUe, FG2e, AOUc, UOIc,
and EXOUb.
Table 1-23 Iub/Iur/Iur-p interface specifications

Board Iub/Iur/Iur-P Numb CID/
Type er of UDP(Iub/
Voice(Erl) VP(Erl UL(M DL(M UL Conne Iur)
(Iub/Iur) )(Iub/ bit/s) bit/s) +DL(M cted
(AMR&WB- Iur) bit/s) NodeB
AMR) s (Iub)
FG2c/ 18000 18000 2600 2600 2600 500 129000

FG2e/
GOUc/
GOUe/
GOUf
AOUc 18000 5500 300 300 600 500 79000
UOIc 18000 9000 800 800 1200 500 79000
EXOUa 75000 75000 8000 8000 10000 1500 1000000

/
EXOUb

Table 1-24 Iu-CS/Iu-PS interface specifications
Board IU CS IU PS
Type
Voice(Erl) VP(Er CID/U UL(M DL(M UL IU PS IU PS
(AMR&W l) DP bit/s) bit/s) +DL( on- Sessio
B-AMR) Mbit/ line n
s) users setup/
release
times
FG2c/ 18000 9000 12900 3200 3200 3200 20000 5000

FG2e/ 0 0
GOUc/
GOUe/
GOUf
UOIc 18000 9000 79000 900 900 1800 12000 5000

0
EXOUa 75000 37500 10000 10000 10000 1000 50000 50000

/ 00 0 0
EXOUb
NOTE
On-line user indicates the number of users in the RRC connected state, including users in
the Cell_DCH, Cell_FACH, Cell _PCH, and Ura_PCH state. Active user indicates the number of
users in the Cell _DCH and Cell _FACH state.
● In this table, the EXOUa/EXOUb specifications regarding UL(Mbit/s),
DL(Mbit/s), and UL+DL(Mbit/s) are based on UL/DL 64 kbit/s/384 kbit/s.
● The specifications of interface boards on the Iur interface are the same as
those of interface boards on the Iub interface.
● The preceding tables list the maximum processing capabilities of boards. For
example, values in the Number of Connected NodeBs indicate the maximum
numbers of NodeBs that can be connected. The actual number of NodeBs is
restricted by the throughput.
● VP in the table indicates 64 kbit/s video phone services.
● One active CS user consumes two Iub CIDs/UDPs, and one active HSPA PS
user consumes three Iub CIDs/UDPs.
● One active CS user consumes one CID/UDP on the Iu-CS interface board, and
one active HSPA PS user consumes one Tunnel Endpoint ID (TEID) on the Iu-
PS interface board.
● AMR represents the traditional 12.2 kbit/s CS services, and WBAMR represents
the typical 23.85 kbit/s CS services.
● "Session setup/release times" indicates the signaling processing capability of
an interface board. This item applies only to the Iu-PS interface boards. The
following table lists the mapping between the interface signaling processing
requirements and the traffic model.

Control plane traffic parameter Unit IuPS session

setup/release
times
CS voice call per subscriber per BH times -
Handover times per CS voice call (Inter/ times/call -

Intra RNC soft&softer handover)
PS call per subscriber per BH times 1
Handover times per PS call (Inter/Intra times/call -

RNC soft&softer handover)
PS channel switch per PS call times/call 0.5
Cell update per PS call times/call 0.5
NAS signaling per subscriber per BH times/per -

(times) subscriber
Table 1-25 Network Requirements for Configuration of Interface Board

Int Item Description Comment
erf
ace
Iub Iub transmission type Iub interface It is determined based

transmission type on the network plan.
The BSC6910 supports
the following Iub
networking modes: FE
Electronic(IP), GE
Optical(IP), 10GE
Optical(IP),
Unchannelized
STM-1(ATM), and
Channelized
STM-1(ATM).
Iub PS throughput PS throughput over They are calculated

the Iub interface based on the number of
users and the traffic
Iub CS Traffic CS traffic over the Iub model.
interface
Iub active users (CID/ Transmission bearers

UDP) for the active users
supported by the Iub
interface of the RNC
NodeB number Number of NodeBs It is determined based

managed by the RNC on the network plan.

Int Item Description Comment

erf
ace
IuC Iu-CS transmission Iu-CS interface It is determined based

S type transmission type on the network plan.
the following Iu-CS
Electronic(IP), GE
Optical(IP), 10GE
Optical(IP), and
Unchannelized
STM-1(ATM).
IuCS CS Traffic Iu interface CS service It is calculated based on

traffic the number of users and
the traffic model.
IuP Iu-PS transmission Iu-PS interface It is determined based

S type transmission type on the network plan.
the following Iu-PS
Electrical (IP) GE Optical
(IP) 10GE Optical (IP)
IuPS Throughput Iu interface PS service It is calculated based on

traffic the number of users and
the traffic model.
IuPS on-line users Number of online It is calculated based on

users over the Iu-PS the number of users and
connecting to the the traffic model.
RNC
IuPS session set-up Number of It is calculated based on

and release connections that need the number of users and
requirement in BH to be supported on the traffic model.
the Iu-PS interface of
the RNC
The following table describes how to configure the Iub interface board (Iur
interface is similar to Iub interface, without configuring NodeBs).

Item Description Prerequisites Calculation of the

Board Quantity
Iub transmission It is determined The board -

type based on the specification is
network plan. The determined based
BSC6910 supports on the interface
the following Iub type.
networking
modes: FE
Electronic(IP), GE
Optical(IP), 10GE
Optical(IP),
Unchannelized
STM-1(ATM), and
Channelized
STM-1(ATM).
Iub PS a Mbit/s Iub PS throughput (1) For EXOUa/

throughput of the EXOUa/ EXOUb: a' = a
EXOUb board Mpbs/EXOUa/
(Gbit/s) is EXOUb
calculated by using specification
the following (2) For GOUe,
formula: Iub PS GOUf, FG2c, FG2e
throughput = Min and ATM:
[Iub packet length
(Byte) x 8 x a' = a/ board
8400000 x 80%/ specification
1000000000, 10]
Alternatively, the
recommended
typical Iub PS
throughput of 8
Gbit/s is used,
which corresponds
to the average
packet length of
150 bytes on the
Iub interface.
Iub CS Traffic b Erl - b' = b/Board traffic

volume
specification (Erl)
Iub active an' (It refers to - an' = an/Board

users(CID/UDP) the number of CID/UDP
active users specification
supported by the
Iub interface.)


Board Quantity
NodeB number nb' (It is - nb' = nb/Board

determined based specification
on the network
plan.)
The number of Iub boards required by the network is calculated as follows:

N_IF_Iub = ROUNDUP[MAX(a' + b', an', nb')]
The configuration method of the Iur interface is similar to that of the Iub interface
(without considering the NodeB).
For Iur interface, if there are several Iur interfaces which do not share ports with
each other, the port requirement and port specification of each interface board
should be taken into account.
Configuration principles for Iu-CS/Iu-PS interface boards

Board Quantity
Iu IuPS IuPS_a Iu-PS throughput of (1) For EXOUa/

Throughput Mbit/s the EXOUa/EXOUb EXOUb: a' = IuPS_a
board (Gbit/s) is Mpbs/EXOUa/
calculated by using the EXOUb
following formula: Iu- specification
PS throughput = (2) For FG2c/
Min[Iu-PS packet FG2e/ATM board:
length (bytes) x 8 x
8400000 x 80%/ a' = IuPS_a/Iu-PS
1000000000, 10] board specification
Alternatively, the
recommended typical
Iu PS throughput of 10
Gbit/s is used.
IuCS Traffic IuCS_b Erl - b' = IuCS_b/Board

traffic volume
specification (Erl)
IuPS on-line IuPS_users - c' = IuPS_users/

users Board TEID
specification
IuPS session IuPS_sessio - d' = IuPS_sessions/

set-up and ns IuPS board
release connection
requiremen specification
t in BH

If the Iu-CS and Iu-PS interfaces use the same interface board:
N_INT_Iu (board pairs) = ROUNDUP[Max(a' + b', c', d')]
If the Iu-CS and Iu-PS interfaces use different interface boards:
N_INT_IuCS (board pairs) = ROUNDUP(b')
N_INT_IuPS (board pairs) = ROUNDUP[Max(a', c', d')]
N_INT_Iu (board pairs) = N_INT_IuCS + N_INT_IuPS
Redundancy Configuration for Interface Boards
BSC6910 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.
1.4.2.6 Configuration Principles for Interface Boards and Service Boards

Service boards and interface boards must be distributed evenly among subracks to
reduce the CPU and swapping resources consumed during inter-subrack swaps and
avoid traffic volume restrictions caused by limited inter-subrack bandwidths. For
example, if there are 12 EGPU boards (for the control plane), 9 EGPU boards (for
the user plane), 3 EXOUa/EXOUb boards, and 3 subracks, then is recommended
that 4 EGPU boards (for control plane), 3 EGPU boards (for the user plane), and 1
EXOUa/EXOUb board be configured in each subrack.
Iu interface boards in each subrack form a resource pool. A route to the core
network is configured on each Iu interface board.
Iub interface boards in each subrack form a transmission resource pool. Routes to
all the NodeBs are configured on each Iub interface board.
1.4.2.7 Board Redundancy Modes

Table 1-26 describes the redundancy modes for various boards.

Table 1-26 Board redundancy modes

Board Description Redundancy Number of
Mode Slots
EGPUa/ Evolved General N+1 backup in Any universal

EGPUb Processing Unit resource pool slots
(logical mode
function:
GCUP/UCUP/
UMSP) and
EGPUb
(logical
function:
NIU)
EOMUa/ Evolved Operation and Active/standby An EOMUa

EOMUb Maintenance Unit mode board is
installed in two
slots in the MPS
only. Active and
standby boards
are installed in
four consecutive
slots starting
with an odd-
numbered slot.
All the boards
are configured
in the same
plane (rear or
back plane).
ESAUa/ Evolved Service Aware Separately One or two

ESAUb Unit configured boards are
configured, each
occupying two
slots. Four slots
are reserved for
them.
EXOUa/ Evolved 10GE Optical Active/standby Any universal

EXOUb interface Unit mode slots
ENIUa Evolved Network N+1 backup in Any universal

Intelligence Unit REV:a resource pool slots
mode
SCUb GE Switching network Active/standby Fixed slots

and Control Unit REV:b mode
SCUc GE Switching and Control Active/standby Fixed slots

Unit REV:c mode

Board Description Redundancy Number of

Mode Slots
FG2c/FG2e IP Interface Unit (12 FE/4 Active/standby Any universal

GE, Electric) mode slots
GOUe/GOUf IP Interface Unit(4 GE, Active/standby Any universal

Optical) mode slots
AOUc ATM Interface Unit (4 Active/standby Of the two

STM-1, Channelized) mode boards in each
pair, one must
be installed in
an odd-
numbered slot
and the other in
an adjacent
even-numbered
slot.
UOIc ATM Interface Unit (8 Active/standby Of the two

STM-1, Unchannelized) mode boards in each
pair, one must
be installed in
an odd-
numbered slot
and the other in
an adjacent
even-numbered
slot.
GCUb/GCUc General Clock Unit Active/standby Fixed slots

mode
GCGb/GCGc GPS&Clock Processing Active/standby Fixed slots

Unit mode
DEUa Data Enhancement N+1 backup in Any universal

Processing Unit resource pool slots
mode
1.4.2.8 Auxiliary Materials
Table 1-27 Auxiliary materials

Part Number Description Remarks Configuration
Principle
QW1P00GEOM00 GE Optical GE optical Full configuration

Connector module

Part Number Description Remarks Configuration

Principle
QW1P0STMOM00 STM-1 Optical STM-1 optical

Connector module
QM1P00GEOM01 10 GE Optical 10GE optical

Connector module
QW1P0FIBER00 Optical Fiber Optical fiber Configured based

on onsite
requirements
QW1P0000IM00 Installation Material Installation One installation

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

documentation documentation
delivered with
each BSC6910
WP1B4PBCBN00 Cabinet Cabinet NA
● Number of GE optical connectors (QW1P00GEOM00) = WP1D000GOU01

quantity x 4
● Number of STM-1 optical connectors (QW1P0STMOM00) = WP1D000AOU01
quantity x 4 + WP1D000UOI01 quantity x 8
● Number of 10GE optical connectors (QM1P00GEOM01) = QM1D00EXOU00
quantity x 2
● Number of optical fibers (QW1P0FIBER00) = (Number of STM-1 optical
connectors + Number of 10GE optical connectors + Number of GE optical
connectors) x 2
1.4.2.9 Restrictions on Inter-Subrack Switching

A pair of active and standby SCUb boards can process data at 40 Gbit/s on the
physical layer. The SCUb boards in various subracks are connected in chain mode.
If either of the active and standby board becomes faulty, the processing capability
is halved.
A pair of active and standby SCUc boards can process data at 320 Gbit/s on the
physical layer. The SCUc 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 service processing boards (including EGPU and
ENIUa) and interface boards must be evenly configured among subracks. The
user-plane capacity of each subrack should be similar.
For example, 18 EGPUb boards, 2 ESAUa/ESAUb boards, 8 pairs of Iub GOUe/

GOUf boards, 6 pairs of Iu GOUe/GOUf boards, and 6 subracks. Complying with
the even-configuration principle, configure data as follows: Configure 2 or 3
EGPUb boards with the logical function UCUP for each subrack. Configure EGPUb
boards with NIU's logical functions in different subracks. Configure 1 or 2 pairs of
Iub GOUe/GOUf boards and 1 pair of Iu GOUe/GOUf boards. Configure more Iub
GOUe/GOUf boards and ENIUa boards or EGPUb (NIU) boards in the subrack with
more EGPU boards. ESAUa/ESAUb boards are configured in reserved slots in the
MPS. The following table lists a recommended configuration.
Table 1-28 Recommended board configuration
Subrac Number Number of Number of Number of Number of

k of EGPUb(NIU Iub GOUe/ Iu GOUe/ ESAUa/
EGPUa/ ) Boards GOUf Pairs GOUf Pairs ESAUb
EGPUb Boards
Boards
MPS 3 1 2 1 2
EPS1 3 1 2 1 0
EPS2 3 1 1 1 0
EPS3 2 0 1 1 0
EPS4 2 0 1 1 0
EPS5 2 0 1 1 0
Total 15 3 8 6 2
1.4.2.10 BSC6910 UMTS Configuration Example

The procedure of typical configuration is as follows.
Step 1 Input the traffic model and the user number
The operator provides the network capacity requirement which should include the
information listed in Table 1-29.
Table 1-29 Network specifications
Item Value
Total subscribers 800,000
Total NodeBs 600
Total cells 3000

Item Value
Voice traffic per CS voice subscriber in BH (Erlang) 0.02
CS voice call duration (sec.) 75
Handover times per CS call 8

CS voice call per subscriber per BH 0.96
PS call per subscriber per BH 2
Proportion of SHO for CS call 0.3
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
Iub interface type 10GE
Iu/Iur interface type 10GE
Ratio of traffic over Iur interfaces to Iub interfaces 8%
Intelligent service awareness or PS service quality Yes

measurement
ESAUa for the Nastar Yes
GPS support Yes
Features requiring the DEU or EGPUb (UUEP) board Yes
Ratio of WB-AMR to total CS services 5%
Step 2 Calculate the capacity requirements on the control plane, user plane, and
transmission plane, and the board capabilities under the traffic model.
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 sample input, the value is 16,000
Erl)
Total Iu-CS Erl = 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 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 = 800,000 x (52 + 0) x 2/3,600 = 23,111
4. Iu-PS session setup/release times requirement (based on sample input, the
value is 1778 times/s)
IuPS session setup/release times = 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
See Table 1-25 for the coefficient.
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 Iub CS Erlang = 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 BHCA = 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 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 active users = 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)] = 800,000 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) 2/3600 + 0.02] = 39111
12. Total Iub CID/UDP requirement (based on 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. In this traffic model, the BHCA of each EGPUa/EGPUb CP only board is
592,000.
EGPUa/EGPUb CP only resources 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 = 14.96%/3600 = 0.0042%
Number of subscribers supported by each EGPUa/EGPUb CP only board =
(70% – 10%) x 14/EGPUa/EGPUb CP only resource consumed per subscriber =
(70% – 10%) x 14/0.0042% = 200,000
BHCA supported by per EGPUa/EGPUb CP only board = Number of subscribers
supported by each EGPUa/EGPUb CP only board x (CS Voice call per
subscriber per BH + PS call per subscriber per BH) = 200,000 x (0.96 + 2) =
592,000
14. In this traffic model, the PS throughput of each EGPUa/EGPUb UP only board
is 13680 Mbit/s.
PS RAB mean data rate (UL+DL) (kbit/s) = [PS throughput (Including R99 and
HSPA, UL+DL) per PS subscriber in BH (bit/s) x 3600/1000] /[PS call per
subscriber per BH x Mean holding time (MHT) in DCH/H/FACH state per PS
call(sec)] = 4,500 x 3600/1000/(2 x 52) = 155.8
155.8 kbit/s is in the value range of [128, 196]. Therefore, PS Throughput
Capacity per EGPUa/EGPUb (Mbit/s) is calculated as follows: PS Throughput
Capacity per EGPUa/EGPUb (Mbit/s) = 1250 + (PS RAB Mean data rate – 128)
x 4.26 = 1250 + (155.8 - 128) x4.26 = 1368 Mbit/s
Step 3 Calculate the hardware configuration and capacity license configurations.
1. Calculate the number of EGPU boards required for the user plane.
Item Description Calculation of the Board Quantity
Iub PS PS throughput EGPUa/EGPUb_ps = Total Iub PS

throughpu over the Iub Throughput requirement /PS Throughput
t interface Capacity per EGPUa/EGPUb (Mbit/s) =
4680/1368 = 3.42
Iub CS CS traffic over the EGPUa/EGPUb_cs = Total Iub CS Erlang

traffic Iub interface requirement/Traffic volume supported by
each EGPUa/EGPUb UP only board =
20800/10050 = 2.07
Active Number of active EGPUa/EGPUb_au = Total active users

users users to be requirement/Number of active users
supported supported by each EGPUa/EGPUb UP only
board = 39111/28000 = 1.40
Cell Number of cells EGPUa/EGPUb_cell = Total cell number

number managed by the requirement/Number of cells supported
RNC by each EGPUa/EGPUb UP Only board =
3000/2800 = 1.07
N_EGPUa/EGPUb_UP = Max(EGPUa/EGPUb_ps + EGPUa/EGPUb_cs, EGPUa/

EGPUb_au, EGPUa/EGPUb_cell) = Max(3.42 + 2.07, 1.40, 1.07) = 5.49

The number of licenses required for "RNC Throughput HW Capacity License (per
50 Mbit/s)" is calculated as follows:
N_ EGPU_Iub_License = ROUNDUP[(Total Iub PS Throughput requirement + Total

Iub CS Erlang requirement x 12.2 x 2/1000)/50] = ROUNDUP[(4680 (Mbit/s)
+ 20800 (Erlang) x 12.2 (kbit/s) x 2/1000)/50 Mbit/s] = 104
2. Calculate the number of EGPU boards required for the control plane.
Item Description Calculation of the Board Quantity
BHCA BHCA required by Calculate the BHCA specification of the

requirement the network EGPUa/EGPUb board in the traffic model.
EGPUa/EGPUb_bhca = Total BHCA
requirement/BHCA capability supported by
each EGPUa/EGPUb CP only board =
2368000/592000 = 4
Active users Number of active EGPUa/EGPUb_au = Total active users

users that must be requirement/Number of active users
supported by the supported by each EGPUa/EGPUb CP Only
RNC board = 39111/35000 = 1.12
Online users Number of online EGPUa/EGPUb_ou = Total online users

users that must be requirement/Number of online subscribers
supported by the supported by each EGPUa/EGPUb CP only
RNC board = 39111/70000 = 0.56
NodeB Number of EGPUa/EGPUb_nb = Total NodeB number

number NodeBs managed requirement/Number of NodeBs supported
by the RNC by each EGPUa/EGPUb CP only board =
600/2520 = 0.24
Cell number Number of cells EGPUa/EGPUb_cell = Total cell number

managed by the requirement/Number of cells supported by
RNC each EGPUa/EGPUb UP Only board =
3000/2800 = 1.07
N_EGPUa/EGPUb_CP = Max(EGPUa/EGPUb_bhca, EGPUa/EGPUb_au,EGPUa/

EGPUb_ou, EGPUa/EGPUb_nb, EGPUa/EGPUb_cell) = Max(4, 1.12, 0.56, 0.24, 1.07)
=4
3. Calculate the number of required EGPUs.

Each EGPUa/EGPUb can be used for both CP and UP processing. The number
of NodeBs supported by each board is 700, and the number of cells supported
by each board is 700.
EGPUa/EGPUb_nodeb_cell = max(Total NodeB number requirement/700,Total
Cell number requirement/700) = max(600/700,3000/700) = 4.23
Finally, consider configuring N+1 backup. In this case,
N_EGPUa/EGPUb = ROUNDUP(max(N_EGPUa/EGPUb_CP + N_EGPUa/
EGPUb_UP, EGPUa/EGPUb_nodeb_cell)) + 1 = ROUNDUP(max(4 + 5.49,4.23))
+ 1 = 11

The number of licenses required for "RNC Active User HW Capacity License" is
calculated as follows:
N_ EGPU_ ActiveUser_License = ROUNDUP(39111/1000) = 40
NOTE
N_EGPU does not include the fixed EGPU boards for resource management.
4. Calculate the number of required EGPUb (NIU) boards and the corresponding
hardware license.
If EGPUb (NIU) boards work in resource pool mode for load sharing, configure
them in N+1 redundancy mode.
N_EGPUb(NIU) = ROUNDUP(4680/4800) + 1 = 2
Number of required Network Intelligence Throughput licenses:
N_Network_Intelligence_Throughput = ROUNDUP(4680/50) = 94
NOTE
If the corresponding optional software is not configured, N_EGPUb(NIU) = 0
5. Calculate the number of required DEUa or EGPUb (UUEP) or boards.

Feature Formula Example
WRFD-17020 DEUa: DEUa:

1 Seamless A = Total Iu-CS Erlang A = 16000 x 0.25 x 2.8 x
Crystal Voice requirement x Ratio of SHO user (5%/3600 + 95%/9000)
to total user x Iub RL number = 1.34
per SHO user x [Proportion of
WB-AMR/3600 + (1 - Proportion EGPUb (UUEP):
of WB-AMR)/9000] A = 16000 * 0.25 * 2.8 *
(5%/16000 + 95%/
EGPUb (UUEP): 34000) =0.35
A = Total Iu-CS Erlang
requirement x Ratio of SHO user
to total user x Iub RL number
per SHO user x [Proportion of
WB-AMR/16000 + (1 -
Proportion of WB-AMR)/34000]

1 Crystal B = Total Iub CS Erlang B = 20800/260000 = 0.08
Voice in requirement/260000
Deep EGPUb (UUEP):
Coverage EGPUb (UUEP): B = 20800/164000 = 0.13
B = Total Iub CS Erlang
requirement/164000


1 Improved C = Total active users C = 39111 x 82% x 30%/
Uplink requirement x Proportion of SRB 38400 = 0.251
Coverage for over DCH x Proportion of peak
SRB over coverage users/38400 EGPUb (UUEP):
DCH
C = 39111 x 82% x 30%/
EGPUb (UUEP): 100000 = 0.1
C = Total active users
requirement x Proportion of SRB
over DCH x Proportion of peak
coverage users/100000

0 TFO/TrFO D = Total IuCS Erlang D = 16000 x 10%/1000 =
(eTrFO) requirement x Proportion of 1.6
eTrFO active users/1000
EGPUb (UUEP):
EGPUb (UUEP): D = 16000 x 10%/1600 =
D = Total IuCS Erlang 1
requirement x Proportion of
eTrFO active users/1600

1 Uplink E = Total cell number E = 3000 x 100 x 1.5%/
Coverage requirement x 100 x Integrate 7500 = 0.6
Improvement coefficient/7500
During EGPUb (UUEP):
Access EGPUb (UUEP): E = 3000 x 100 x 1.5%/
E = Total cell number 35000 = 0.13
requirement x 100 x Integrate
coefficient/35000

8 Crystal F = Total IuCS Erlang F = 16000 x 10% x
Voice requirement x Proportion of [5%/500 + 95%/1000] =
Coverage Downlink Weak Coverage CS 1.68
Improvement Users x [Proportion of WB-
by Rate AMR/500 + (1 – Proportion of EGPUb (UUEP):
Adaption WB-AMR)/1000] F = 16000 x 10% x
[5%/750 + 95%/1500] =
EGPUb (UUEP): 1.12
F = Total IuCS Erlang
requirement x Proportion of
Downlink Weak Coverage CS
Users x [Proportion of WB-
AMR/750 + (1 – Proportion of
WB-AMR)/1500]
N_DEUa = (A + B + C + D + E + F) + 1 =7

N_EGPUb (UUEP) = (MAX((A + B + C + E), (D + F)) + 1 = 4

where
a. Proportion of WB-AMR = 5% (default value)
b. Ratio of SHO user = 0.25 (default value)
c. Iub RL number per SHO user = 2.8 (default value)
d. Proportion of SRB over DCH = 82% (default value)
e. Proportion of Weak Coverage User = 30% (default value)
f. Proportion of eTrFO Active users = 10% (default value)
g. Integrate coefficient = 1.5% (provided that the signaling packets over
RACH accounts for 70%, RACH bandwidth usage is 43%, and the RACH
packet BLER is 5%.)
h. Proportion of Downlink Weak Coverage CS Users = 10% (default value)
NOTICE
If the corresponding optional software is not configured, N_DEUa = 0.

If the corresponding optional software is not configured, N_EGPUb (UUEP) =
0
On the EGPUb (UUEP) board, the decoding of four features (Seamless Crystal
Voice, Crystal Voice in Deep Coverage, Improved Uplink Coverage for SRB over
DCH, and Uplink Coverage Improvement During Access) is performed on the
logical part, while the coding and decoding of voice services of other features
(eTrFO (enhancement of WRFD-011600 TFO/TrFO), Crystal Voice Coverage
Improvement by Rate Adaption) is performed on the CPU. Therefore, the
EGPUb (UUEP) board allows any two features from the two groups to reach
their respective specifications.
The number of EGPUb (UUEP) boards required by the two groups of features
is calculated separately, and the larger value indicates the number of EGPUb
(UUEP) boards to be configured.
6. Number of required EXOUa/EXOUb boards
Inte Item Specifications Description

rfac
e
Iub Iub transmission 10GE Optical EXOUa/EXOUb

type (IP)


rfac
e
Iub PS ba = 4680 Iub PS throughput of EXOUa/EXOUb

throughput Mbit/s (Gbit/s) = Min [Mean Iub packet
length (Bytes) x 8 x 8400000 pps x
80%/1000000000, 10]
Alternatively, use the default
recommended value of 8 Gbit/s.
When the default value of 8 Gbit/s
is used as the Iub PS throughput of
EXOUa/EXOUb:
ba' = ba/EXOUa/EXOUb Iub PS
Throughput UL+DL = 4680/1000/8 =
0.59
Iub CS traffic bb = 20800 bb' = bb/EXOUa/EXOUb traffic

volume = 20800/75000 = 0.28
NodeB number bn = 600 bn' = bn/NodeBs supported by

EXOUa/EXOUb = 600/1500 = 0.4
Iub active users an = 124,800 an' = an/Iub UDPs supported by one

(CID/UDP) EXOUa/EXOUb board =
124,800/500,000 = 0.25
Iu- Iu-CS 10GE Optical EXOUa/EXOUb

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

one EXOUa/EXOUb board =
16,000/75,000 = 0.21
Iu- Iu-PS 10GE Optical EXOUa/EXOUb

PS transmission (IP)
type
Iu-PS throughput pb = 3600 Iu-PS throughput of EXOUa/EXOUb

(Gbit/s) = Min [Mean Iu-PS packet
length (Bytes) x 8 x 8400000 pps x
80%/1000000000, 10]
Alternatively, use the default
recommended value of 10 Gbit/s.
Take 10 Gbit/s as the actual
capability of the Iu PS EXOUa/
EXOUb board.
pb' = pb/EXOUa/EXOUb Iu PS
Throughput UL+DL = 3600/1000/10
= 0.36


rfac
e
Iu-PS online pu = 23111 pu' = pu/ EXOUa/EXOUb Iu PS TEID

users = 23111/500000 = 0.05
Iu-PS session ps = 1778 ps' = ps/Number of connections

set-up and supported by EXOUa/EXOUb Iu-PS
release per second = 1778/50000 = 0.04
If Iub, Iu-CS (the Iu-CS and Iur interfaces share the same interface board), and Iu-
PS interface boards are configured separately and work in 1+1 backup mode, the
number of required interface boards is as follows:
1) N_IUB_IF = ROUNDUP[Max(ba'+bb', bn', an')] * 2 = ROUNDUP[Max(0.59

+ 0.28, 0.4, 0.25)] x 2 = 2
2) N_IUCSIUR_IF = ROUNDUP([cb'+ 8% x (ba' + bb')] x 2 = ROUNDUP[0.21 + 0.08

x (0.84 + 0.28)] x 2 = 2
3) N_IUPS_IF = ROUNDUP[Max(pb', pu', ps')] x 2 = ROUNDUP[Max(0.36, 0.05,

0.04)] x 2 = 2
N_EXOUa/EXOUb = N_IUB_IF + N_IUCSIUR_IF + N_IUPS_IF = 6
7. Number of required ESAUa/ESAUb boards
Four slots are required for two ESAUa/ESAUb boards. By default, one ESAUa/
ESAUb board is configured for the UMTS only mode for the EBC. If the customer
has purchased the Nastar service or other OSS services (such as SON or RAN
Service Visibility Based on PRS), additional ESAUa/ESAUb boards are required. A
maximum of two SAU boards can be configured. The ESAUb board does not
support Nastar services. The specific quantity of ESAUa/ESAUb boards is
determined by OSS features. Assume that one ESAUa/ESAUb board is required in
this example.
8. Number of required GCG boards
A pair of GCGb/GCGa/GCGc boards must be configured if the GPS positioning

function is required. A pair of GCGb/GCGa/GCGc boards must be configured if the
GPS positioning function is not required.
9. Calculate the number of EPSs (QM1P00UEPS01).
The number of fixed slots in the MPS is 14, and the remaining 14 slots are used
for holding service processing boards and interface boards. The fixed slots are
assigned as follows: four slots for two EOMUa/EOMUb boards; two slots for two
GCUb/GCUc/GCGb/GCGc boards; four slots reserved for two ESAUa/ESAUb boards;
two slots for two SCUc boards; two slots for two EGPU (logical function type:
RMP) boards
Number of EPSs = ROUNDUP[(N_EGPUa/EGPUb(11) + N_EXOUa/EXOUb(6) +

N_EGPUb(NIU)(2) - 14)/26] = 1

10. Number of required cabinets (WP1B4PBCBN00)
Number of cabinets = 1 Number of cabinets = ROUNDUP[(Number of MPSs +

Number of EPSs)/3] = ROUNDUP(2/3) = 1
In summary, the following table lists the configurations that can meet network
requirements.
Item Name Model Qua

ntity
Cabinet N/A WP1B4PBCBN00 1
Main processing subrack MPS QM1P00UMPS01 1
Extended processing subrack EPS QM1P00UEPS01 1
GE Switching and Control Unit SCUc WP1D000SCU03 4
Evolved Operation and Maintenance Unit EOMUa/ QM1D00EOMU0 2

EOMUb 0
Clock board GCUb WP1D000GCU02 2
Clock board GCUc WP1D000GCU03 2
Evolved General Processing Unit for User EGPU QM1D00EGPU01 11

Plane
RNC Throughput Hardware Capacity (per N/A QM1SRTHWCL0 103

50 Mbit/s) 0
RNC Active User Hardware Capacity (per N/A QM1SRAUHCL00 40

1000 Active Users)
Evolved 10GE Optical interface Unit EXOUa/ QM1D00EXOU0 6

EXOUb 0/WP11EXOUb
Data Enhancement Processing Unit DEUa WP1D000DEU00 3
Evolved Service Aware Unit ESAUa/ QM1D00ESAU00 1

ESAUb
Evolved Network Intelligence Processing N/A QM1S00ENIU00 94

Throughput (per 50 Mbit/s)
----End
1.4.2.11 BSC6910 UMTS Recommended Capacity for Delivery

For the sake of network security, the actual capacity of a configured BSC6910 is
much lower than the specified maximum capacity. BSC6910s with excessively large
capacity are not delivered in a large scale on the live network. Therefore, it is
recommended that the BSC6910 capacity be controlled for the initial network
deployment.

For per BSC6910 the NodeB number should less than 600. If the RNC in Pool
feature is enabled, the number of NodeBs served by a BSC6910 is increased to be
within 900.
Because network planning is a long-term action, the delivery of BSC capacity is on

per-phase basis. To ensure network reliability and security, active/standby
configuration must be used for large-capacity BSCs. Specifically, use the active/
standby configuration for to double the hardware capacity of the BSC6910. In
long-term network planning, if a single BSC serves 600 to 1200 NodeBs, the RNC
in Pool feature must be enabled to achieve 1+1 backup and ensure large-capacity
network security.
1.4.3 BSC6910 GU Product Configurations

The following principles apply to BSC6910 GU new deployment and capacity
expansion:

Table 1-30 BSC6910 GU basic configuration principles
Cabinet Subrack MPS Board Configuration

Configuration Configuration Configuration Specifications
Specifications Specifications Specifications
Number of GSM: a minimum Either GSM or GSM and UMTS each is

cabinets = of 1 and a UMTS subrack configured with ENIUa/
ROUNDUP[(N maximum of 3; A can function as EGPUb (NIU).
umber of GSM over TDM the MPS. By EGPUa/EGPUb can be
subracks + supported; BM/TC default, the shared by GSM and
Number of separated mode UMTS subrack is UMTS networks. On a
UMTS not supported. the MPS. newly-deployed GU
subracks)/3]. A UMTS: a network, this board is
maximum of minimum of 1 configured in the
two cabinets and a maximum UMTS subrack by
(excluding the of 5 default. On a
cabinets reconstructed GU
housing TC The total number
of GSM and network, this board is
subracks) can configured in the
be configured. UMTS subracks
should be less subrack that houses
than or equal to the original NASP
six. boards.
The ESAUa/ESAUb
board can be
configured in the
BSC6910 GU mode,
and therefore four slots
must be reserved for
holding two ESAUa/
ESAUb boards.
The procedure for configuring a newly deployed BSC6910 GU is as follows:
Step 1 Obtain the GSM and UMTS network parameter values.
Step 2 Perform dimensioning to obtain the GSM and UMTS network requirements.
Step 3 Calculate the UMTS configuration and GSM configuration based on the network
requirements. (The detailed configuration rules for and algorithm restrictions on
UMTS and GSM boards are consistent with the descriptions provided in 1.4.2
BSC6910 UMTS Product Configurations and 1.4.1 BSC6910 GSM Product
Configurations.)
If the capacity required by the GSM configuration and UMTS configuration does
not exceed the BSC6910 GU specifications (that is, the total number of GSM
subracks and UMTS subracks does not exceed six), then configuration calculation
is complete. If the total required capacity exceeds the maximum specifications of
one BSC6910 GU or the number of slots required for the interface boards exceeds
the limitation, an extra BSC6910 GU needs to be added.
----End

1.5 Hardware Expansion and Upgrade Configurations

The service processing capability is enhanced by expanding hardware capacity.
Follow the minimum hardware configuration principle during capacity expansion.
1.5.1 BSC6910 GSM

Capacity expansion can be performed using the following methods:
● Improving the service processing capability of the system through hardware
expansion
● Improving the service processing capability of the system by configuring
capacity licenses
You can use either of or both of the two methods based on the network traffic
model and traffic volume requirements.
Follow the minimum hardware configuration principle during capacity expansion.
1.5.1.1 Precautions
The BSC6900 cannot be upgraded to the BSC6910 by upgrading the software, and
can be upgraded only by migrating the hardware. If the BSC6900 is upgraded to
the BSC6910, the BSC license of BSC6900 can be used for the BSC 6910 only after
the license is quoted and applied for again. However, the BTS license of the
BSC6900 that has been quoted can be directly used for the BSC6910 using license
adjusting tools.
The BSC6910 supports the following boards: SCUb, SCUc, EOMUa/EOMUb, ESAUa/
ESAUb, GCUa, GCGa, GCUb, GCUc, GCGb, GCGc, EGPUa/EGPUb/EXPUa/EXPUb,
DPUf, FG2c, FG2d, FG2e, GOUc, GOUd, GOUe, GOUf, EXOUa/EXOUb, and POUc.
The BSC6910 does not support other BSC6900 boards.
In A over IP networking, the EGPUa/EGPUb/EXPUa/EXPUb boards with the logical
function type GCUP used in the BSC6910 replace the XPUb, DPUf (for A over IP),
and DPUg boards used in the BSC6900. In A over TDM networking, the EGPUa/
EGPUb/EXPUa/EXPUb and DPUf boards must be configured in the BSC6910.
In the BSC6910 V100R016C00, the Ater and Pb interfaces are removed. The Abis
and A interfaces support IP and TDM transmission modes, whereas other external
interfaces support only IP transmission mode.

Part Name Remarks

Number
WP1D000FG FG2c/ 1. Number of required A interface boards

201/ FG2e = 2 x ROUNDUP(MAX((TotalAIPFEGENo – Number
WP11FG2e of the FG2c boards on the A interface/2 x
GEPortPerFG2c)/GEPortPerFG2c, (TotalAIPCIC –
Number of FG2c boards on the A interface/2 x
AIPCICPerFG2c)/AIPCICPerFG2c), 0)
NOTE
The number of required A interface boards depends on
the number of ports and the number of equivalent CIC
circuits on the A interface. In capacity expansion
scenarios, the capacity specifications and number of ports
supported by the existing FG2c/FG2e boards must be
subtracted from the total required capacity.
2. Number of required Abis interface boards
= 2 x ROUNDUP(MAX((TotalAbisIPFEGENo –
Number of FG2c boards on the Abis interface/2 x
GEPortPerFG2c)/GEPortPerFG2c, (TotalTRXNoFEGE
– Number of FG2c boards on the Abis interface/2 x
TRXNoPerFG2c)/TRXNoPerFG2c), 0)
NOTE
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 number of originally
supported TRXs must be subtracted from the total
number of required TRXs. In addition, the number of ports
supported before capacity expansion must also be
considered.
3. Number of required Gb interface boards
= 2 x ROUNDUP(MAX((TotalGbIPFEGENo –
Number of FG2c boards on the Gb interface/2 x
GEPortPerFG2c)/GEPortPerFG2c, (TotalGbIPTput –
Number of FG2c boards on the Gb interface/2 x
GbTputPerFG2c)/GbTputPerFG2c), 0)
NOTE
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/FG2e boards to be configured
is equal to the total number of all the preceding
boards.
WP1D000G GOUe/ The GOUe/GOUf board has the same service capacity,
OU03/ GOUf GE port quantity, and configuration calculation
WP11PGOU formula as the FG2c board except the interface type.
F0

Part Name Remarks

Number
QM1D00EX EXOUa/ ● EXOUa/EXOUb functioning as the interface board

OU00/ EXOUb before capacity expansion
WP11EXOUb 1. Number of required A interface boards
= 2 x ROUNDUP(Max ((TotalAIP10GENo –
Number of EXOUa boards functioning as A
interface boards/2 x 10GEPortPerEXOUa)/
10GEPortPerEXOUa, (TotalAIPCIC – Number of
EXOUa boards functioning as A interface
boards/2 x AIPCICPerEXOUa)/AIPCICPerEXOUa),
0)
NOTE
The number of required A interface boards depends on
the number of ports and the number of equivalent CIC
circuits on the A interface. In capacity expansion
scenarios, the capacity specifications and number of
ports supported by the existing EXOUa/EXOUb boards
must be subtracted from the total required capacity.
= 2 x ROUNDUP(Max ((TotalAbisIP10GENo –
Number of EXOUa boards functioning as Abis
interface boards/2 x 10GEPortPerEXOUa)/
10GEPortPerEXOUa, (TotalTRXNo10GE –
Number of EXOUa boards functioning as Abis
interface boards/2 x TRXNoPerEXOUa)/
TRXNoPerEXOUa), 0)
NOTE
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 number of
originally supported TRXs must be subtracted from the
total number of required TRXs. In addition, the number
of ports supported before capacity expansion must
also be considered.
3. Number of required Gb interface boards
= 2 x ROUNDUP(Max((TotalGbIP10GENo –
Number of EXOUa boards functioning as Gb
interface board/2 x 10GEPortPerEXOUa)/
10GEPortPerEXOUa, (TotalGbIPTput – Number
of EXOUa boards functioning as Gb interface
board/2 x GbTputPerEXOUa)/GbTputPerEXOUa),
0)
NOTE
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 EXOUa/EXOUb boards to be
configured is equal to the total number of all
the preceding boards.

Part Name Remarks

Number
● FG2c/FG2e/GOUc/GOUe/GOUf functioning as the

interface board before capacity expansion (The
calculation principle for GOUc/GOUe/GOUf is the
same as that for FG2c.)
1. Number of required A interface boards
= 2 x ROUNDUP(Max (((TotalAIPCIC – Number
of FG2c boards functioning as A interface
board/2 x AIPCICPerFG2c)/AIPCICPerEXOUa), 0)
NOTE
The quantity depends on the number of ports and the
number of equivalent CIC circuits on the A interface. In
capacity expansion scenarios, the capacity
specifications and number of ports supported by the
existing FG2c/FG2e/GOUc/GOUe/GOUf boards must
be subtracted from the total required capacity.
= 2 x ROUNDUP(Max ((TotalTRXNo – Number
of FG2c boards functioning as Abis interface
board/2 x TRXNoPerFG2c)/TRXNoPerEXOUa), 0)
NOTE
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.
3. Number of required Gb interface boards = 2 x
ROUNDUP(Max ((TotalGbIPTput – Number of
FG2c boards functioning as Gb interface board/2
x GbTputPerFG2c)/GbTputPerEXOUa), 0)
NOTE
traffic on the Gb interface. The originally supported
traffic must be subtracted from the total supported
traffic.
4. The number of EXOUa/EXOUb boards to be
configured is equal to the total number of all
the preceding boards.

Part Name Remarks

Number
WP1D000PO POUc 1. Number of required A interface boards (TDM) = 2 x

U01 ROUNDUP(MaxACICPerBSCTDM – Number of
POUc boards functioning as A interface board/2 x
ACICPerPOUcTDM)/ACICPerPOUcTDM, 0)
2. Number of required Abis interface boards (TDM) =
2 x ROUNDUP(Max ((TotalAbisTDMSTM1No –
Number of POUc boards functioning as Abis
interface board/2 x STM1PortPerPOUc)/
STM1PortPerPOUc, (TotalTRXNo – Number of POUc
boards functioning as Abis interface boards/2 x
TRXHRPerPOUcTDM)/ TRXHRPerPOUcTDM, 0))
NOTE
number of TRXs on the Abis interface. At least one E1 port
(which can be shared in cascading networking) must be
configured for each base station by default. 3.
3. Number of required Abis interface boards (IP) = 2 x
ROUNDUP(Max ((TotalAbisIPSTM1No – Number of
POUc boards functioning as Abis interface board/2
x STM1PortPerPOUc)/STM1PortPerPOUc,
(TotalTRXNo – Number of POUc boards functioning
as Abis interface board/2 x TRXPerPOUcIP)/
TRXPerPOUcIP, 0))
NOTE
The quantity depends on the number of base stations, the
number of ports, and the number of TRXs on the Abis
interface. Each BTS must be configured with at least one
E1 port by default. If the BTSs are cascaded on the live
network, only the BTS at the highest level is connected to
an E1 port on the BSC.

Part Name Remarks

Number
QM1D00EGP EGPUa/ 1. Calculating the number of required EGPU boards

U00/ EGPUb based on the number of TRXs:
QM1D0EGP Number of required EGPU boards =
UB00 ROUNDUP(TotalTRXNo/TRXNoPerEGPU, 0) –
Number of existing EGPU boards
2. Calculating the number of required EGPU boards
based on the CS user-plane traffic volume:
Number of required EGPU boards =
ROUNDUP(TotalVoiceErl/VoiceErlPerEGPU, 0) –
based on the number of PS user-plane PDCHs:
ROUNDUP(TotalPDCH/PDCHPerEGPU, 0) – Number
of existing EGPU boards
based on the signaling-plane BHCA:
ROUNDUP(TotalBHCA/BHCAPerEGPU, 0) – Number
of existing EGPU boards
BHCA (TotalBHCA): calculated based on the
number of users and traffic model
based on the number of cells:
ROUNDUP(TotalCellNo/CellNoPerEGPU, 0) –
based on the number of BTSs:
ROUNDUP(TotalBTSNo/BTSNoPerEGPU, 0) –
7. The number of required EGPU boards to be
configured is equal to the maximum value of all
the values.
WP1D000DP DPUf Number of DPUf boards =

U05 ROUNDUP(MaxACICPerBSCTDM/TCNoPerDPUf, 0) –
Existing number of DPUf boards
QM1D00EXP EXPUa/ Same as EGPUa/EGPUb

U00/ EXPUb
WP11EXPUb
GMIPEPRAC GEPS Number of processing subracks = ROUNDUP(Max

K00 (Total number of interface boards – 10/12, (Total
number of interface boards + Total number of EGPU
boards – 18)/26, 0))

Part Name Remarks

Number
QM1B0PBCB Cabinet 1
N00
1.5.1.2 Hardware Capacity License Expansion

Before hardware capacity expansion, sufficient hardware capacity licenses for "BSC
HW TRX Capacity (per TRX)" and "BSC HW PDCH Capacity (per PDCH)" must be
obtained. The number of licenses to be increased depends on the difference in TRX
or PDCH capacity before and after capacity expansion.
1.5.1.3 Examples of Hardware Expansion
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.
Ite Name Configurati Configurati Number of

m on Before on After Componen
Capacity Capacity ts to Be
Expansion Expansion Added
1 Subracks (MPS and EPS) A1 B1 B1 – A1
4 EGPUa/EGPUb/EXPUa/ A2 B2 B2 – A2
EXPUb
5 Interface boards A3 B3 B3 – A3
6 Cabinets A4 B4 B4 – A4
----End

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 procedure for the incremental algorithm is as follows:
Step 1 Fill in the UniSTAR calculation table with the quotation parameters of the new
hardware version after the capacity expansion. By doing this, you get the
configuration required after the capacity expansion. In the Dimension Calculator
window, you can view the capacity after 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, set the capacity increase on the
Gb interface to 0.
Ite Name Configurati Maximum Increased

m on 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 PDCH QTY A2 B2 B2 – A2
3 A CIC QTY A3 B3 B3 – A3
4 BHCA A5 B5 B5 – A5
5 Gb interface traffic A6 A6 B6 – A6
... ... ... ... ...
Step 4 Determine the boards required by the capacity expansion.

Process the initial result about the required hardware based on the configuration
principle.

Step 5 Calculate whether additional cabinets, subracks, and auxiliary materials are
required for the capacity expansion.
----End
1.5.2 BSC6910 UMTS
1.5.2.1 Hardware Expansion and Upgrade Configurations

The following table lists the BSC6910 V100R025C10 boards.
Hardw Board
are
Versio
n
HW691 EGPUa, EOMUa, ESAUa, SCUb, GCUa, GCGa, ENIUa, EXOUa, FG2c,
0 R15 FG2d, GOUc, GOUd, AOUc, UOIc, EXPUa, POUc
HW691 EGPUa, EOMUa, ESAUa, SCUb, SCUc, GCUa, GCUb, GCGa, GCGb,
0 R16 DPUf, ENIUa, EXOUa, FG2c, FG2d, GOUc, GOUd, GOUe, AOUc, UOIc,
EXPUa, POUc
HW691 EGPUa, EOMUa, ESAUa, SCUb, SCUc, GCUa, GCUb, GCGa, GCGb,
0 R17 DPUf, ENIUa, EXOUa, FG2c, FG2d, GOUc, GOUd, GOUe, AOUc, UOIc,
EXPUa, POUc, DEUa
HW691 EGPUa, EGPUb, EOMUa, ESAUa, SCUb, SCUc, GCUa, GCUb, GCGa,
0 R18 GCGb, DPUf, ENIUa, EXOUa, FG2c, FG2d, GOUc, GOUd, GOUe, AOUc,
UOIc, EXPUa, EXPUb, POUc, DEUa
HW691 EGPUa, EGPUb, EOMUa, EOMUb, ESAUa, ESAUb, SCUb, SCUc, GCUa,
0 R19 GCUb, GCGa, GCGb, DPUf, ENIUa, EXOUa, EXOUb, FG2c, FG2d, FG2e,
GOUc, GOUd, GOUe, AOUc, UOIc, EXPUa, EXPUb, POUc, DEUa
0 R22 GCUb, GCUc, GCGa, GCGb, GCGc, DPUf, ENIUa, EXOUa, EXOUb, FG2c,
FG2d, FG2e, GOUc, GOUd, GOUe, GOUf, AOUc, UOIc, EXPUa, EXPUb,
POUc, DEUa
0 R23 GCUb, GCUc, GCGa, GCGb, GCGc, DPUf, ENIUa, EXOUa, EXOUb, FG2c,
FG2d, FG2e, GOUc, GOUd, GOUe, GOUf, AOUc, UOIc, EXPUa, EXPUb,
POUc, DEUa

NOTE
No new board is added in HW6910 R18. The logical board type NIU is added for the EGPUb
board.
The following table lists the number of components to be added for the HW6910
R25 hardware capacity expansion.
Ite Name Configuratio Configuratio Added

m n Before n After Quantity
Capacity Capacity
Expansion Expansion
1 Cabinet A1 B1 B1 – A1
2 MPS A2 B2 B2 – A2
3 EPS A3 B3 B3 – A3
4 Clock board A4 B4 B4 – A4
5 Evolved General A5 B5 B5 – A5
Processing Unit (for
Control Plane)
6 Evolved General A6 B6 B6 – A6
Processing Unit for User
Plane
7 Interface boards A7 B7 B7 – A7
NOTE
A1 through A7 and B1 through B7 indicate the number of components.
1.5.2.2 Examples of Hardware Expansion

Assume that the network configurations before capacity expansion are as follows:
Traffic: 10,050 Erl Transmission rate: 2000 Mbit/s (based on the uplink and
downlink transmission rates 64 kbit/s and 384 kbit/s) BHCA: 1,668,000 (using the
Smartphone traffic model) Number of NodeBs: 700 Number of cells: 1400 IP
transmission (10GE optical port) over the Iub, Iu-CS, and Iu-PS interfaces Iub, Iu-
CS, and Iu-PS interface boards working in 1+1 active/standby mode
Assume that the network configurations after capacity expansion are as follows:
Traffic: 20,100 Erl Transmission rate: 4000 Mbit/s (based on the uplink and
downlink transmission rates 64 kbit/s and 384 kbit/s) BHCA: 3,336,000 (under
smartphone traffic model) Number of NodeBs: 1400 Number of cells: 2800 IP
transmission (10GE optical port) over the Iub, Iu-CS, and Iu-PS interfaces Iub, Iu-
CS, and Iu-PS interface boards working in 1+1 backup mode.
The numbers of hardware components to be added are calculated according to

the procedure described in section 1.4.2.2 Subracks.

Table 1-31 Capacity expansion from configuration 1 to configuration 2
Configuration Number Number Number Number of Number

of of of EGPU EGPU for of
Cabinets Subracks for User Control EXOUa/
Plane Plane EXOUb
Configuration 1 1 2 1 6
1 (before
capacity
expansion)
Configuration 1 1 4 2 6
2 (after
capacity
expansion)
Number of 0 0 2 1 0
components
to be added
The slot configurations are as follows:
1.6 Spare Parts Configurations
1.6.1 BOM of Spare Parts

BOM_List.xls
1.6.2 Configuration Principles for Spare Parts

Spare parts configurations are calculated 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.
1.6.2.1 Poisson Algorithm

The Poisson algorithm is integrated in the configurator, and therefore you do not
need to calculate the number of spare parts manually.
The Poisson algorithm is as follows:

x indicates the number of configured spare parts.

1. Pis the damage rate of boards acceptable for an operator. Generally, P(x) is
greater than or equal to 85% and less than 100%.
In the following figure, P(x) is 99%.
2. = 2.71828183
3. λ = Number of boards applied on the network x Annual damage rate of
boards x Replenishment period/365
a. The replenishment period is usually 60 days.
b. 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.
c. 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 backup boards (BOM:

02319428) is 4.
1.6.2.2 Percentage Algorithm

If the operator specifies the percentage algorithm, use the percentage algorithm
to calculate the number of spare parts.
1.6.2.3 Notes
The number of spare parts calculated using the Poisson algorithm satisfies only
basic requirements of the live network. If the operator requires the service level

agreement (SLA), persuade the operator to purchase Huawei spare parts

management services (SPMSs).
1.7 Appendix
1.7.1 GSM Configuration Reference
1.7.1.1 GSM Traffic Model

This section describes the GSM traffic model.
Table 1-32 GSM traffic model
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
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

Parameter Value
PS Paging / Sub/BH 1.25
1. Table 1-33 provides the capacity of a BSC6910 GSM in Abis over TDM, A over
TDM, and Gb over IP modes.
Table 1-33 Capacity of a BSC6910 GSM in Abis over TDM, A over TDM, and Gb
over IP modes
Name Typical Configuration
Number of subracks 1
Maximum number of TRXs 1024
Maximum number of equivalent 2200

BHCA (k)
Maximum traffic volume (Erlang) 6250
Maximum number of activated 4096

PDCHs (MCS-9)
2. Table 1-34 provides the capacity of a BSC6910 GSM in Abis over TDM, A over
IP, and Gb over IP modes.
Table 1-34 Capacity of a BSC6910 GSM in Abis over TDM, A over IP, and Gb over
IP modes

BHCA (k)

PDCHs (MCS-9)
3. Table 1-35 provides the capacity of a BSC6910 GSM in all-IP transmission

mode.

Table 1-35 Capacity of a BSC6910 GSM in all-IP transmission mode


BHCA (k)

PDCHs (MCS-9)
4. Table 1-36 provides the capacity of a BSC6910 GSM in all-IP transmission

mode with BSC Node Redundancy enabled.
Table 1-36 Capacity of a BSC6910 GSM in all-IP transmission mode with BSC
Node Redundancy

BHCA (k)

PDCHs (MCS-9)
1.7.1.2 GSM Hardware Specifications
GSM Board Specifications
Table 1-37 GSM board configurations

Parameter ID Meaning Specifi Board
cations
TrxPerEGPU Number of TRXs supported by 1000 EGPUa/

each EGPUa/EXPUa/EGPUb/ EXPUa/
EXPUb board EGPUb/
EXPUb


cations
BHCAPerEGPU BHCA supported by each 2200K

EGPUa/EXPUa/EGPUb/EXPUb
board
ErlPerEGPU Traffic volume (Erl) supported 6250

by each EGPUa/EXPUa/EGPUb/
EXPUb board
PDCHPerEGPU Number of PDCHs supported by 3000

each EGPUa/EXPUa/EGPUb/
EXPUb board
10GEPortPerEXOU Number of 10GE ports 2 EXOUa/

supported by each EXOUa/ EXOUb
EXOUb board
TRXNoPerEXOU Number of TRXs supported by 8000

each EXOUa/EXOUb board over
the Abis interface in IP
transmission mode
ACICPerEXOU Number of CIC circuits 75000

supported by each EXOUa/
EXOUb board over the A
interface in IP transmission
mode
GbTputPerEXOU Throughput (Mbit/s) supported 8000

by each EXOUa/EXOUb board
over the Gb interface in IP
transmission mode
LogicalPortPerEXOU Number of logical ports 1500

supported by the EXOUa/
EXOUb board in IP transmission
mode
TCNoPerDPUf TC processing capability 1920 DPUf

supported by each DPUf board
GEPortPerFG2c Number of GE ports supported 4 FG2c/FG2e

by each FG2c/FG2e board
FEPortPerFG2c Number of FE ports supported 12

by each FG2c/FG2e board
GEPortPerGOUc Number of GE ports supported 4 GOUc

by each GOUc board
GEPortPerGOUe Number of GE ports supported 4 GOUe/GOUf

by the GOUe/GOUf


cations
GbTputPerFG2c Throughput (Mbit/s) supported 2000 FG2c/FG2e/

by each FG2c/FG2e or GOUc/ GOUc/
GOUe/GOUf board over the Gb GOUe/GOUf
mode
TRXNoPerFG2c Number of TRXs supported by 2048

each FG2c/FG2e or GOUc/
GOUe/GOUf board over the
Abis interface in IP transmission
mode
ACICPerFG2c Number of CICs supported by 23040

each FG2c/FG2e or GOUc/
GOUe/GOUf board over the A
mode
LogicalPortPerFG2c Number of logical ports 490

supported by each FG2c/FG2e
or GOUc/GOUe/GOUf board in
IP transmission mode
STM1PortPerPOUc Number of STM-1 ports 4 POUc

supported by each POUc board
TRXHRPerPOUcTDM Number of TRXs supported by 1024 POUc:TDM

each POUc board in TDM
transmission mode
TRXPerPOUcIP Number of TRXs supported by 2048 POUc:IP

each POUc board over the Abis
mode
ACICPerPOUcTDM Number of CIC circuits 7680 POUc:TDM

supported by each POUc board
over the A interface in TDM
transmission mode
MaxInterSubrackIPS- Maximum switching capability 40G BSC

witch between subracks of the BSC
Board Utilization
Each type of board on the BSC6910 has its specifications, which are calculated by
collectively considering the capacity on various aspects (including BHCA capacity,
TRX capacity, CIC capacity, and bandwidth capacity).
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 to
represent the board capacity.
Board usage = Traffic volume on the BSC(BHCA and number of TRXs)/Maximum

board specification
For example:
The specification of the GOUe board over the A interface is 23,040 CICs, and the
number of serving CICs is 10,000. Therefore, the board usage is 43.4%
(10,000/23,040 x 100%).
1.7.2 UMTS Configuration Reference
1.7.2.1 UMTS Traffic Model

The BSC6910 UMTS supports the flexible configuration of CP and UP data in
different scenarios. In each scenario, the capacity configured for the BSC6910
UMTS depends on actual traffic models.
There are two traffic models for the BSC6910 UMTS:
● High-PS traffic model

This model is applicable in scenarios where subscribers use much more data
services than voice services. In this model, the average PS throughput per user
is high.
● Smartphone traffic model
In this model, CP signaling is frequently exchanged and UP data is transmitted
mainly through small packets.
The capacity under UMTS BSC6910 typical configurations in the high-PS traffic
model and smartphone traffic model are described as follows:
1. High-PS traffic model
Table 1-38 High-PS traffic model
Item Specification Description
CS voice 3 mE 0.144 BHCA, AMR voice service

traffic
volume in
BH
CS data 0.2 mE 0.01 BHCA, UL: 64 kbit/s, DL: 64

traffic kbit/s
volume
PS 43500 bit/s 3 BHCA, UL: 64 kbit/s, DL: 384

throughput kbit/s
in BH

Proportion 30% Proportion of calls using two

of soft channels simultaneously to all
handovers calls
Handover 8 N/A
times per CS
call (SHO)
(times/call)
Handover 5 N/A
times per PS
call (SHO)
(times/call)
NAS 3.6 Number of NAS procedures

signaling per between the CN and UEs,
subscriber including location area updates,
per BH IMSI attach/detach occurrences,
(times) routing area updates, GPRS
attach/detach occurrences, and
SMSs
Iur-to-Iub 8% N/A
traffic ratio
The following table lists the typical capacity of the BSC6910 UMTS configured
with HW6910 R25 boards under high-PS traffic model.
Table 1-39 Typical capacity of the BSC6910 UMTS under high-PS traffic
model (HW6910 R25 boards)
Number CS PS BHCA Number Numbe Number
of Service Service (k) of Active r of of
Subscrib Capacit Capacity Users Online Subrack
ers y (Iub UL Users Combin
Support (Erlang +DL) ation
ed ) (Mbit/s)
1,380,00 5,700 59,500 4,300 210,000 420,000 1MPS

0 +2EPS
2,760,00 11,400 120,000 8,600 420,000 840,000 1MPS

0 +5EPS

NOTE
● The CS voice service capacity, PS service capacity, and BHCA can reach the
maximum at the same time.
● The number of on-net users indicates the number of users who have accessed a
UMTS network within a busy hour.
● The number of active users indicates the total number of users who are in the
CELL_DCH and CELL_FACH states.
● The number of online users indicates the total number of users who are in the
CELL_DCH, CELL_FACH, CELL_PCH, and URA_PCH states.
The following figure shows the typical configuration (1 MPS + 2 EPSs) under
high-PS traffic model.
high-PS traffic model.

2. Smartphone traffic model
Table 1-40 Smartphone traffic model

CS voice traffic 30 mE 0.7 BHCA, AMR voice service

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

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

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

per PS call (SHO)
(times/call)
Inter-PDCH 2.3 Including all handovers

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

NAS signaling 2.8 Number of NAS procedures

per subscriber between the CN and UEs,
per BH (times) including location area
updates, IMSI attach/detach
occurrences, routing area
updates, GPRS attach/detach
occurrences, and SMSs
Iur-to-Iub traffic 8% N/A

ratio
The following table lists the capacity of a BSC6910 UMTS in typical

configurations. In this table, the BSC6910 UMTS is configured with HW6910
R25 boards under the smartphone traffic model.
Table 1-41 Typical capacity of the BSC6910 UMTS under smartphone traffic
model (HW6910 R25 boards)
Number CS PS BHCA (k) Numbe Numbe Numbe
of Service Service r of r of r of
Subscrib Capacity Capacit Active Online Subrac
ers (Erlang) y (Iub Users Users k
Supporte UL+DL) Combi
d (Mbit/s nation
)
3,600,000 122,000 5,800 32,000 665,000 1,000,0 1MPS

00 +2EPS
7,490,000 250,000 11,900 64,000 1,000,0 1,000,0 1MPS

00 00 +5EPS
NOTE
● The CS voice service capacity, PS service capacity, and BHCA can reach the
maximum at the same time.
● The number of on-net users indicates the number of users who have accessed a
UMTS network within a busy hour.
● The number of active users indicates the total number of users who are in the
CELL_DCH and CELL_FACH states.
● The number of online users indicates the total number of users who are in the
CELL_DCH, CELL_FACH, CELL_PCH, and URA_PCH states.
smartphone traffic model.

smartphone traffic model.

1.7.2.2 UMTS Hardware Specifications
Table 1-42 UMTS Hardware Specifications

Parameter ID Meaning Specifications Board
NodebPerEGP Number of NodeBs 700 EGPUb

UbCP supported by each EGPUb CP Only
board (CP: more than
30%)
CellPerEGPUb Number of cells supported 700 EGPUb

by each EGPUb board (CP:
between 30% and 70%)
ActiveUserPer Number of active users 35000 EGPUb

EGPUbCP supported by each EGPUb CP Only
CP only board
ActiveUserPer Number of active users 28000 EGPUb

EGPUbUP supported by each EGPUb UP Only
UP only board
ActiveUserPer Number of active users Min[35000*p, EGPUb

EGPUb supported by each EGPUb 28000*(1-p)] CP&UP
UP+CP board (CP: p%)

OnlineUserPer Number of online users 70000 EGPUb

EGPUbCP supported by each EGPUb CP Only
CP only board
OnlineUserPer Number of online users 70000 EGPUb

EGPUbUP supported by each EGPUb UP Only
UP only board
OnlineUserPer Number of online users Min[70000*p, EGPUb

EGPUb supported by each EGPUb 70000*(1-p)] CP&UP
BHCAPerEGP BHCA supported by each 1,668,000 in Huawei EGPUb

UbCP EGPUb CP Only typical smartphone CP Only
traffic model.
Calculated based on
the traffic model.
ErlPerEGPUbU Traffic volume (Erl) 10050 EGPUb

P supported by each EGPUb UP Only
UP only board
PsThtPerEGPU PS throughput supported Assume that x EGPUb

bUP by each EGPUb UP only represents PS Rab UP Only
board mean data rate in
active state, and y
represents
PsThtPerEGPUbUP.
If x in (0, 16], y = 15*x
If x in (16, 40], y = 240
+ (x - 16)* 15.4;
If x in (40, 64], y = 610
+ (x - 40) * 9.58;
If x in (64, 128], y =
840 + (x - 64) * 6.4;
If x in (128, 196], y =
1250 + (x - 128) * 4.26;
If x in (196, 320], y =
1540 + (x - 196) * 3.7;
If x in (320, ∞),
y=2000
BHCAPerEGP BHCA supported by each BHCAPerEGPUbCP*p% EGPUb

Ub EGPUb CP+UP board (CP CP&UP
accounts for p%, and CS
services occupy q% of UP)

ErlPerEGPUb Traffic volume (Erl) ErlPerEGPUbUP*(1-p EGPUb

supported by each EGPUb %)*q% CP&UP
CP+UP board (CP
PsThtPerEGPU PS throughput supported PsThtPerEGPUbUP*(1- EGPUb

b by each EGPUb CP+UP p%)*(1-q%) CP&UP
board (CP accounts for p
%, and CS services occupy
q% of UP)
NodebPerEGP Number of NodeBs 700 EGPUa

UaCP supported by each EGPUa CP Only
board (CP: more than
30%)
CellPerEGPUa Number of cells supported 700 EGPUa

by each EGPUa board (CP: CP&UP
between 30% and 70%)
ActiveUserPer Number of active users 35000 EGPUa

EGPUaCP supported by each EGPUa CP Only
CP only board
ActiveUserPer Number of active users 28000 EGPUa

EGPUaUP supported by each EGPUa UP Only
UP only board
ActiveUserPer Number of active users Min[35000*p, EGPUa

EGPUa supported by each EGPUa 28000*(1-p)] CP&UP
OnlineUserPer Number of online users 70000 EGPUa

EGPUaCP supported by each EGPUa CP Only
CP only board
OnlineUserPer Number of online users 70000 EGPUa

EGPUaUP supported by each EGPUa UP Only
UP only board
OnlineUserPer Number of online users Min[70000*p, EGPUa

EGPUa supported by each EGPUa 70000*(1-p)] CP&UP
BHCAPerEGP BHCA supported by each 1,668,000 in Huawei EGPUa

UaCP EGPUa CP only board typical smartphone CP Only
traffic model.
Calculated based on
the traffic model.
ErlPerEGPUaU Traffic (Erl) supported by 10050 EGPUa

P each EGPUa UP only UP Only
board

PsThtPerEGPU PS throughput supported Assume that x EGPUa

aUP by each EGPUa UP only represents PS Rab UP Only
board mean data rate in
active state, and y
represents
PsThtPerEGPUaUP.
If x in (0, 16], y = 15*x
If x in (16, 40], y = 240
+ (x - 16)* 15.4;
If x in (40, 64], y = 610
+ (x - 40) * 9.58;
If x in (64, 128], y =
840 + (x - 64) * 6.4;
If x in (128, 196], y =
1250 + (x - 128) * 4.26;
If x in (196, 320], y =
1540 + (x - 196) * 3.7;
If x in (320, ∞),
y=2000
BHCAPerEGP BHCA supported by each BHCAPerEGPUaCP*p% EGPUa

Ua EGPUa CP+UP board (CP CP&UP
ErlPerEGPUa Traffic volume (Erl) ErlPerEGPUaUP*(1-p EGPUa

supported by each EGPUa %)*q% CP&UP
CP+UP board (CP
PsThtPerEGPU PS throughput supported PsThtPerEGPUaUP*(1-p EGPUa

a by each EGPUa CP+UP %)*(1-q%) CP&UP
board (CP accounts for p
%, and CS services occupy
q% of UP)
MaxInterSubr Inter-subrack switching 40 SCUb

ackSwitchSCU capability (Gbit/s) of each
b pair of SCUb boards
MaxInterSubr Inter-subrack switching 320 SCUc

ackSwitchSCU capability (Gbit/s) of each
c pair of SCUc boards
NodebPerGO Number of NodeBs 500 GOUe/

Ue/ supported by each GOUe/ GOUf/
NodebPerFG2 GOUf/FG2c/FG2e board FG2c/
c FG2e

ErlPerGOUe/ Traffic (Erl) supported by 18000

ErlPerFG2c each GOUe/GOUf/FG2c/
FG2e board
IubUdpPerGO Iub UDPs supported by 129000

Ue/ each GOUe/GOUf/FG2c/
IubUdpPerFG FG2e board
2c
IuPSTeidPerG Iu-PS TEID supported by 200000

OUe/ each GOUe/GOUf/FG2c/
IuPSTeidPerFG FG2e board
2c
IuPSSessionsP Number of Iu-PS session 5000

erGOUe/ setups and releases
IuPSSessionsP supported by each GOUe/
erFG2c GOUf/FG2c/FG2e board
Iubit/ Iub UL+DL PS throughput 2600

sThrPerGOUe (Mbit/s) supported by
/Iubit/ each GOUe/GOUf/FG2c/
sThrPerFG2c FG2e board
IuPsThrPerGO Iu-PS UL+DL PS 3200

Ue/ throughput (Mbit/s)
IuPsThrPerFG supported by each GOUe/
2c GOUf/FG2c/FG2e board
NodebPerEXO Number of NodeBs 1500 EXOUa/

Ua/ supported by each EXOUb
NodebPerEXO EXOUa/EXOUb board
Ub
ErlPerEXOUa/ Traffic (Erl) supported by 75000

ErlPerEXOUb each EXOUa/EXOUb board
IubUdpPerEX Iub UDPs supported by 1000000

OUa/ each EXOUa/EXOUb board
IubUdpPerEX
OUb
IuPSTeidPerEX Iu-PS TEID supported by 500000

OUa/ each EXOUa/EXOUb board
IuPSTeidPerEX
OUb
IuPSSessionsP Number of Iu-PS session 50000

erEXOUa/ setups and releases
IuPSSessionsP supported by each
erEXOUb EXOUa/EXOUb board

Iubit/ Iub UL+DL PS throughput Min (Average packet

sThrPerEXOU (Gbit/s) supported by length on Iub x
a/Iubit/ each EXOUa/EXOUb board 8400000 x 80%/
sThrPerEXOU 1000000000, 10) or
b Use the default
recommended value 8
Gbit/s
IuPsThrPerEX Iu UL+DL PS throughput Min (Average packet

OUa/ (Gbit/s) supported by length on Iu-PS x
IuPsThrPerEX each EXOUa/EXOUb board 8400000 x 80%/
OUb 1000000000 Gbit/s,
10) or
Use the default
recommended value 10
Gbit/s
NodebPerAO Number of NodeBs 500 AOUc

Uc supported by each AOUc
board
ErlPerAOUc Traffic (Erl) supported by 18000

each AOUc board
IubUlPsThrPer Iub UL PS throughput 300

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

AOUc (Mbit/s) supported by
each AOUc board
IubUlDlPsThrP Iub DL and UL PS 600

erAOUc throughput (Mbit/s)
supported by each AOUc
board
NodebPerUOI Number of NodeBs 500 UOIc

c supported by each UOIc
board
ErlPerUOIc Traffic (Erl) supported by 18000

each UOIc board
IubUlPsThrPer Iub UL PS throughput 800

UOIc (Mbit/s) supported by
each UOIc board
IubDlPsThrPer Iub DL PS throughput 800

UOIc (Mbit/s) supported by
each UOIc board

IubUlDlPsThrP Iub DL and UL PS 1200

erUOIc throughput (Mbit/s)
supported by each UOIc
board
PortNumGOU Number of ports 4 GOUe/

e/ supported by each GOUe/ GOUf/
PortNumFG2c GOUf/FG2c/FG2e board FG2c/
FG2e
PortNumEXO Number of ports 2 EXOUa/

Ua/ supported by EXOUa/ EXOUb
PortNumEXO EXOUb
Ub
Stm1PortNum Number of STM-1 ports 4 AOUc

AOUc supported by each AOUc
board
Stm1PortNum Number of STM-1 ports 8 UOIc

UOIc supported by each UOIc
board
PsThtPerENIU PS throughput when the 8000 ENIUa

a ENIUa board is used for
service awareness (Mbit/s)
ENPsThtPerE PS throughput when the 4800 ENIUa

NIUa ENIUa board is used for
PS service quality
measurement (Mbit/s)
PsThtPerEGPU PS throughput when the 8000 EGPUb

b(NIU) EGPUb board is used for
service awareness (Mbit/s)
ENPsThtPerEG PS throughput when the 4800 EGPUb

PUb(NIU) EGPUb board is used for
PS service quality
measurement (Mbit/s)
NbAmrErlang Erlang supported by each 9000 DEUa

PerDEUa DEUa board enabled with
NB-AMR
WbAmrErlang Erlang supported by each 3600 DEUa

PerDEUa DEUa board enabled with
WB-AMR
SlvaErlangper Erlang supported by each 260000 DEUa

DEUa DEUa board enabled with
Crystal Voice in Deep
Coverage

SrboverDchUs Number of UEs supported 38400 DEUa

rNumPerDEU by each DEUa board
a enabled with Improved
Uplink Coverage for SRB
over DCH
eTrFOErlangP Erlang supported by each 1000 DEUa

erDEUa DEUa board enabled with
eTrFO (enhancement of
TFO/TrFO)
CellNumPerD Number of cells supported 5000 DEUa

EUa by each DEUa board
enabled with Improved
Uplink Coverage During
Access
NbAmrWeakC Erlang supported by each 1000 DEUa

overageErlang DEUa board enabled with
PerDEUa NB-AMR Crystal Voice
Coverage Improvement by
Rate Adaption
WbAmrWeak Erlang supported by each 500 DEUa

CoverageErlan DEUa board enabled with
gPerDEUa WB-AMR Crystal Voice
Coverage Improvement by
Rate Adaption
AlwaysHDVoi Erlang supported by each 200 DEUa

ceErlangPerD DEUa board enabled with
EUa Always HD-Voice
NbAmrErlang Erlang supported by each 34000 EGPUb

PerDEUa EGPUb board enabled
with Seamless Crystal
Voice NB-AMR (12.2
kbit/s) for enhanced data
processing
WbAmrErlang Erlang supported by each 16000 EGPUb

PerEGPUb EGPUb board enabled
with Seamless Crystal
Voice WB-AMR (23.85
kbit/s) for enhanced data
processing
SlvaErlangper Erlang supported by each 164000 EGPUb

EGPUb EGPUb board enabled
with Crystal Voice in Deep
Coverage for enhanced
data processing

SrboverDchUs Number of users 100000 EGPUb

rNumPerEGP supported by each EGPUb
Ub board enabled with
Improved Uplink Coverage
for SRB over DCH for
enhanced data processing
eTrFOErlangP Number of users 1000 EGPUb

erEGPUb supported by each EGPUb
board enabled with eTrFO
(enhancement of TFO/
TrFO) for enhanced data
processing
CellNumPerE Number of cells supported 23000 EGPUb

GPUb by each EGPUb board
enabled with Uplink
Coverage Improvement
During Access for
enhanced data processing
NbAmrWeakC Erlang supported by each 1500 EGPUb

overageErlang EGPUb board enabled
PerEGPUb with NB-AMR Crystal
Voice Coverage
Improvement by Rate
Adaption
WbAmrWeak Erlang supported by each 750 EGPUb

CoverageErlan EGPUb board enabled
gPerEGPUb with WB-AMR Crystal
Voice Coverage
Improvement by Rate
Adaption
1.7.3 List of Board Power Consumption

Table 1-43 lists the power consumption of BSC6910 boards.
Table 1-43 List of board power consumption
BOM Name Power Power Weight (kg)

Code Consumption Consumption
(W) (Max) (W)
(Average)
02113573 BSC6910 0 0 120.00

Cabinet
02114336 NEBSCabinet 0 0 150.00

BOM Name Power Power Weight (kg)

Code Consumption Consumption
(W) (Max) (W)
(Average)
02300708 BSC6910 1400 200 37.90

Subrack with
Fan box
03053067 SCUb 78 66 1.50
03053299 DPUf 70 60 1.40
03054296 EGPUa 130 111 2.50
03054588 EXPUa 130 111 2.50
03054298 EXOUa 130 111 2.50
03054297 ENIUa 130 111 2.50
03054294 EOMUa 140 119 3.87
03057627 EOMUb 140 119 3.57
03054295 ESAUa 140 119 3.87
03057628 ESAUb 140 119 3.57
03054333 GCUb 21 18 0.98
03059810 GCUc 21 18 0.98
03040122 GCGb 22 19 1.00
03040131 GCGc 22 19 1.00
03055293 GOUe 75 64 1.40
03058181 GOUf 89.3 76 1.60
03052761 FG2c 85 73 1.50
03057312 FG2e 85 73 1.50
03052759 AOUc 75 64 1.50
03052760 UOIc 87 74 1.50
03052748 POUc 77 66 1.50
03055858 DEUa 70 60 1.40
03056240 SCUc 136 116 2.40
03056563 EGPUb 115 98 2.30
03056564 EXPUb 115 98 2.30
03057017 EXOUb 115 98 2.50

1.8 Acronyms and Abbreviations

Table 1-44 Acronyms and abbreviations
Acronym or Abbreviation Full Name
AMR Adaptive Multirate
ATM asynchronous transfer mode
BH busy hour
CN core network
CP Control Plane
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
UP User Plane
WB-AMR wide band adaptive multirate

BSC6910 Configuration Principles (V100R025C10 - 01) (PDF) - EN

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

BSC6910 Configuration Principles (V100R025C10 - 01) (PDF) - EN

Uploaded by

Copyright:

Available Formats

SRAN19.1&GBSS25.1&RAN25.

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2023-03-07) Copyright © Huawei Technologies Co., Ltd. i

1 BSC6910 Configuration Principles....................................................................................... 1

Issue 01 (2023-03-07) Copyright © Huawei Technologies Co., Ltd. ii

1.5.1.2 Hardware Capacity License Expansion................................................................................................................... 93

Issue 01 (2023-03-07) Copyright © Huawei Technologies Co., Ltd. iii

1 BSC6910 Configuration Principles

Product Name Product Version Solution Version

BSC6910 V100R025C10 SRAN19.1

Issue 01 (2023-03-07) Copyright © Huawei Technologies Co., Ltd. 1

1.1 Change History

1.2.2 Version Differences and Hardware List

Issue 01 (2023-03-07) Copyright © Huawei Technologies Co., Ltd. 2

HW6910 Added SCUc boards to expand the switching bandwidth between

HW6910 Added the DEUa board.

HW6910 Added the DEUa board.

HW6910 EGPUb boards are introduced. EGPUb boards function as the

HW6910 EXOUb boards function as the evolved version of EXOUa boards

HW6910 EOMUb boards function as the evolved version of EOMUa boards

Issue 01 (2023-03-07) Copyright © Huawei Technologies Co., Ltd. 3

The following table describes HW6910 R25 hardware.

Table 1-2 HW6910 R25 hardware

Model Name Description Function Application

QM1D00EGP EGPUa Evolved General Processes GSM & UMTS

QM1D0EGPU EGPUb Evolved General Processes GSM & UMTS

QM1D00EXP EXPUa Evolved Extensible Processes GSM

WP11EXPUb EXPUb Evolved Extensible Finished board- GSM

WP1D000DP DPUf CS Data Processing Provides TC GSM

QM1D00EOM EOMU Evolved Operation Provides the GSM & UMTS

Issue 01 (2023-03-07) Copyright © Huawei Technologies Co., Ltd. 4

Model Name Description Function Application

WP11EOMUb EOMU Evolved Operation Provides the GSM & UMTS

QM1D00E ESAUa Evolved Service Provides GSM & UMTS

WP11ESAUb ESAUb Evolved Service Provides GSM & UMTS

QM1D00EXO EXOUa Evolved 10GE Evolved 10GE GSM & UMTS

WP11EXOUb EXOU Evolved 10GE Evolved 10GE GSM & UMTS

QM1D00ENIU ENIUa Evolved Network Provides GSM & UMTS

WP1D000DE DEUa Data Enhancement Data UMTS

WP1D000SCU SCUb GE Switching Provides packet GSM & UMTS

WP1D000SCU SCUc GE Switching Provides packet GSM & UMTS

WP1D000FG2 FG2c IP Interface Unit IP: A/ GSM & UMTS

Issue 01 (2023-03-07) Copyright © Huawei Technologies Co., Ltd. 5

Model Name Description Function Application

WP11FG2e FG2e IP Interface Unit IP: A/ GSM & UMTS

WP1D000GO GOUe IP Interface Unit (4 IP: A/ GSM & UMTS

WP11PGOUF GOUf IP Interface Unit(4 IP: A/ GSM & UMTS

WP1D000AO AOUc ATM Interface Unit ATM: Iub UMTS

WP1D000UOI UOIc ATM Interface Unit ATM: Iu- UMTS

WP1D000PO POUc TDM or IP Interface TDM: A/Abis GSM

Issue 01 (2023-03-07) Copyright © Huawei Technologies Co., Ltd. 6

Model Name Description Function Application

QW1D000GC GCGc GPS&Clock Obtains the GSM & UMTS

QM1B0PBCD N/A Assembly Cabinet N68E-22 GSM & UMTS

WP2B06PBCD N/A Assembly Cabinet A68-22 cabinet GSM & UMTS

QM1K00PBCS N/A Backplane Subrack, Subrack GSM & UMTS

A BSC6900 cannot be upgraded to the BSC6910 by upgrading the software.

1.3 Application Overview

Issue 01 (2023-03-07) Copyright © Huawei Technologies Co., Ltd. 7

Figure 1-1 Exterior of a single-cabinet BSC6910 (N68E-22)

Figure 1-2 Exterior of a single-cabinet BSC6910 (A68-22)