BSC6900 Configuration Principle (Global) (V900R015C00 - 09) (PDF) - en

SRAN8.0&GBSS15.0&RAN15.
0 BSC6900
Configuration Principles (Global)

Issue
09
Date
2015-07-27
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

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

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 09 (2015-07-27)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
SRAN8.0&GBSS15.0&RAN15.0 BSC6900
Contents
Contents
1 Change History..............................................................................................................................1
2 Introduction....................................................................................................................................6
2.1 Overview........................................................................................................................................................................7
2.2 Version Difference.........................................................................................................................................................7
2.2.1 BSC6900 GSM Version Difference............................................................................................................................7
2.2.2 BSC6900 UMTS Version Difference..........................................................................................................................8
2.2.3 BSC6900 GU Version Difference...............................................................................................................................8
3 Application Overview................................................................................................................10
4 Product Configurations..............................................................................................................15
4.1 BSC6900 GSM Product Configurations.......................................................................................................................16
4.1.1 Hardware Capacity License Configurations..............................................................................................................16
4.1.2 Service Processing Units Configurations..................................................................................................................17
4.1.3 Interface Boards Configurations................................................................................................................................24
4.1.4 Clock Boards Configurations....................................................................................................................................29
4.1.5 General Principles of Configuring Boards in Slots...................................................................................................30
4.1.6 Subracks Configurations............................................................................................................................................31
4.1.7 Cabinets Configurations............................................................................................................................................33
4.1.8 Auxiliary Materials....................................................................................................................................................33
4.2 BSC6900 UMTS Product Configurations....................................................................................................................34
4.2.1 Impact of the Traffic Model on Configurations........................................................................................................35
4.2.2 Hardware Capacity License Configurations..............................................................................................................36
4.2.3 Service Processing Units Configurations..................................................................................................................39
4.2.4 Interface Boards Configurations................................................................................................................................43
4.2.5 Clock Boards Configurations....................................................................................................................................51
4.2.6 Principles for Board Configurations..........................................................................................................................51
4.2.7 Subracks Configurations............................................................................................................................................52
4.2.8 Cabinets Configurations............................................................................................................................................53
4.2.9 Auxiliary Materials....................................................................................................................................................54
4.2.10 Description of Restrictions......................................................................................................................................55
4.3 BSC6900 GU Product Configurations.........................................................................................................................56
4.4 Examples of Typical Configurations............................................................................................................................56
Issue 09 (2015-07-27)

ii
Contents
4.4.1 BSC6900 GSM Examples of Typical Configurations...............................................................................................56

4.4.2 BSC6900 UMTS Examples of Typical Configurations............................................................................................59
5 Expansion and Upgrade Configurations.................................................................................67

5.1 BSC6900 GSM Hardware Expansion and Upgrade Configurations Example.............................................................68
5.1.1 Hardware Expansion and Upgrade Configurations...................................................................................................68
5.1.2 Hardware Capacity License Expansion.....................................................................................................................84
5.1.3 Examples of Hardware Expansion............................................................................................................................84
5.2 BSC6900 UMTS Hardware Expansion and Upgrade Configurations.........................................................................86
5.2.1 Hardware Expansion and Upgrade Configurations...................................................................................................86
5.2.2 Hardware Capacity License Expansion.....................................................................................................................87
5.2.3 Examples of Hardware Expansion............................................................................................................................87
5.2.4 Examples of Hardware Capacity License Expansion................................................................................................89
5.3 BSC6900 GU Hardware Expansion and Upgrade Configurations...............................................................................90
6 Appendix.......................................................................................................................................91
6.1 Hardware Version.........................................................................................................................................................92
6.2 Traffic Model................................................................................................................................................................93
6.2.1 GSM Traffic Model...................................................................................................................................................93
6.2.2 UMTS Traffic Model.................................................................................................................................................94
6.3 GSM Ater RSL Configuration Calculation Tool..........................................................................................................98
6.4 Suggestions for GSM Lb Interface Configuration.......................................................................................................98
6.5 GSM Hardware Specifications.....................................................................................................................................98
6.5.1 Board Specifications..................................................................................................................................................98
6.5.2 Board Usage............................................................................................................................................................103
6.6 UMTS Hardware Specifications.................................................................................................................................104
7 Acronyms and Abbreviations.................................................................................................109
Issue 09 (2015-07-27)

iii
1 Change History
Change History
This chapter provides information about the changes in different versions of

SRAN8.0&GBSS15.0&RAN15.0 BSC6900 Configuration Principle (Global).
09 (2015-07-27)
This is the ninth commercial release of V900R015C00.
Compared with Issue 08 (2014-12-29), this issue does not include any new topics.
Compared with Issue 08 (2014-12-29), this issue incorporates the following changes.
Content
Change Description
4.1.5 General Principles

of Configuring Boards
in Slots
Changed the resource allocation algorithm for service processing

units (DPU on the CS service plane)processing services carried
on TRXs connected to interface boards.
Compared with Issue 08 (2014-12-29), this issue does not exclude any topics.
08 (2014-12-29)
This is the eighth commercial release of V900R015C00.
Add new board GCUb, GCGb, XPUc, SPUc and GOUe.
07 (2014-09-12)
This is the seventh commercial release of V900R015C00.
Issue 09 (2015-07-27)

1 Change History
Content
Change Description
4.1.3 Interface Boards

Configurations
Differentiated interface board specifications in Abis over TDM

mode between the independent mode and the active/standby
mode.
Added low voltage differential signal (LVDS) restrictions
imposed on the calculation of the number of POUc boards.
Updated the method of calculating the number of DPUf boards
when the Abis interface uses both IP and TDM transmission.
5.3 BSC6900 GU
Hardware Expansion
and Upgrade
Configurations
Added basic configuration principles.
4.2.3 Service Processing

Units Configurations
Added the description that only one SAU is delivered in GU or

UMTS mode.
4.2.7 Subracks
Configurations
06 (2014-06-09)
This is the sixth commercial release of V900R015C00.
Content
Change Description
4.1.6 Subracks Configurations
Optimized the method of calculating the number of

DPUf boards.
Added the TNUb board as a replacement for the TNUa
board.
05 (2014-04-30)
This is the fifth commercial release of V900R015C00.
Issue 09 (2015-07-27)

1 Change History
Content
Change Description
4.2.2 Hardware Capacity License

Configurations
Modified some descriptions.
Added a table.
04 (2014-03-28)
This is the fourth commercial release of V900R015C00.
Content
Change Description
4.2.1 Impact of the Traffic Model

on Configurations
Updated the method of estimating the number of

DPUe boards.
4.2.3 Service Processing Units

Configurations
4.4.2 BSC6900 UMTS Examples
of Typical Configurations
Optimized the procedure of typical configuration.
4.2.10 Description of Restrictions
Modified some descriptions.
6.6 UMTS Hardware

Specifications
Updated board specifications.
03 (2014-01-20)
This is the third commercial release of V900R015C00.
Issue 09 (2015-07-27)
Content
Change Description
4.2.6 Principles for Board

Configurations
Changed the default number of SAUs to be configured

for UMTS from 1 to 0.

1 Change History
Content
Change Description

Configurations
Updated XPUb specifications for eGBTSs and

modified the method of calculating the number of
XPUb boards on newly deployed networks and
capacity expansion scenarios.

Configurations
l Changed the value of "IuPS session setup/release

times" in Table 4-13.
l Added Iur interface board specifications.
6.2.2 UMTS Traffic Model
Updated "smartphone traffic model" and the

corresponding RNC capacity.
02 (2013-06-16)
This is the second commercial release of V900R015C00.
Content
Change Description
3 Application Overview
Added the notes for BHCA, PS throughput, and traffic

model for UMTS under Figure 3-1.
4.2.1 Impact of the Traffic Model

on Configurations
Corrected board names for UMTS.
Updated the configuration principles for SAU boards

for UMTS.

Configurations
l Added the rules for calculating the number of Iur

interface boards when Iur interfaces are carried on
different ports.
6.6 UMTS Hardware

Specifications
4.1.5 General Principles of
Configuring Boards in Slots
l Added specifications of ports on Iur interface

boards.
Updated of the configuration principles for SAU
boards for GSM.
01 (2013-02-16)
This is the first commercial release of V900R015C00.
Compared with Draft A (2014-01-27), this issue includes the following new topics:
Issue 09 (2015-07-27)

1 Change History
PEUc boards
Compared with Draft A (2014-01-27), this issue incorporates the following changes.
Content
Change Description

Configurations
Updated the configuration principles for XPUb boards

for eGBTSs.

Configurations
Modified the configuration principles for Iur-P

interface boards.
Compared with Draft A (2014-01-27), this issue excludes the following topics:
l
GCUb, GCGb, and TNUb boards
UMTS NASP boards
Draft A (2012-06-26)
This is a draft for V900R015C00.
Issue 09 (2015-07-27)

2 Introduction
Introduction
About This Chapter

2.1 Overview
2.2 Version Difference
Issue 09 (2015-07-27)

2 Introduction
2.1 Overview
This document describes the configuration principles of the BSC6900 V900R015.
The BSC6900 supports three working modes: BSC6900 GSM, BSC6900 UMTS, and BSC6900
GU. Therefore, the BSC6900 applies to various application scenarios.
l
BSC6900 GSM indicates that the BSC6900 works in GSM only mode, providing the same
functions as the GSM BSC.
BSC6900 UMTS indicates that the BSC6900 works in UMTS only mode, providing the
same functions as the UMTS RNC.
BSC6900 GU indicates that the BSC6900 works in GSM&UMTS (GU) mode, providing
the same functions as the GSM BSC and UMTS RNC.
This document covers topics, such as product specifications, configuration principles, and
capacity expansion and upgrade configurations of the BSC6900 in three working modes.
2.2 Version Difference

2.2.1 BSC6900 GSM Version Difference
The BSC6900 GSM in the minimum configuration consists of one cabinet, in which one subrack
(MPS) is configured. The BSC6900 GSM in the maximum configuration consists of two
cabinets, in which one MPS and three EPSs are configured. The BSC6900 V900R015 GSM
supports four hardware versions: HW60 R8, HW69 R11, HW69 R13, and HW69 R15.
l
HW60 R8 hardware: When using the HW60 R8 hardware, a BSC6000 or BSC6900 GSM
can be upgraded to BSC6900 V900R015 by upgrading software (version-by-version
upgrade may be required). The configuration principles and capacity expansion principles
remain unchanged after the upgrade. If only the software of a BSC6000 or BSC6900 GSM
is upgraded to BSC6900 V900R015, the capacity remains unchanged after the upgrade.
HW69 R11 hardware: When using the HW69 R11 hardware, a BSC6900 GSM can be
upgraded to BSC6900 V900R015 by upgrading software (version-by-version upgrade may
be required). The configuration principles and capacity expansion principles remain
unchanged after the upgrade. If only the software of a BSC6900 GSM is upgraded to
BSC6900 V900R015, the capacity remains unchanged after the upgrade.
upgraded to BSC6900 V900R015 by upgrading software. The configuration principles and
capacity expansion principles remain unchanged after the upgrade. If only the software of
a BSC6900 GSM is upgraded to BSC6900 V900R015, the capacity remains unchanged
after the upgrade.
a BSC6900 GSM is upgraded to BSC6900 V900R015, the capacity remains unchanged
after the upgrade.
The following sections describe the configuration principles of the BSC6900 GSM using HW69
R16 hardware.
Issue 09 (2015-07-27)

2 Introduction
2.2.2 BSC6900 UMTS Version Difference

The BSC6900 UMTS in the minimum configuration consists of one cabinet, in which one
subrack (MPS) is configured. The BSC6900 UMTS in the maximum configuration consists of
two cabinets, in which one MPS and five EPSs are configured. The BSC6900 V900R015 UMTS
supports four hardware versions: HW68 R11, HW69 R11, HW69 R13, and HW69 R15.
l
HW68 R11 hardware: When using the HW68 R11 hardware, a BSC6810 or BSC6900
UMTS can be upgraded to BSC6900 V900R015 by upgrading software (version-byversion upgrade may be required). The configuration principles and capacity expansion
principles remain unchanged after the upgrade. If only the software of a BSC6000 or
BSC6900 UMTS is upgraded to BSC6900 V900R015, the capacity remains unchanged
after the upgrade.
HW69 R11 hardware: When using the HW69 R11 hardware, a BSC6900 UMTS can be
unchanged after the upgrade. If only the software of a BSC6900 UMTS is upgraded to
a BSC6900 UMTS is upgraded to BSC6900 V900R015, the capacity remains unchanged
after the upgrade.
a BSC6900 UMTS is upgraded to BSC6900 V900R015, the capacity remains unchanged
after the upgrade.
SPUc, GOUe, GCUb and GCGb are introduced in HW69 R15 from patch version
R15C00SPC580. SPUc, GOUe, GCUb and GCGb can coexist with the corresponding old
boards SPUb, GOUc, GCUa, and GCGa.
The following sections describe the configuration principles of the BSC6900 UMTS using
HW69 R15 hardware.
Compared to V900R014, V900R015 BSC6900 products inherit the basic specifications.
A V900R015 BSC6900 UMTS supports the RNC in Pool feature to pool multiple RNCs, such
as BSC6900s only or BSC6900s and BSC6910s. RNCs in the resource pool share resources and
balance redundancies.
2.2.3 BSC6900 GU Version Difference

The BSC6900 GU in the minimum configuration consists of one cabinet, in which two subracks
are configured. One subrack is used for UMTS and the other for GSM. The BSC6900 GU in the
maximum configuration consists of two cabinets, in which one MPS and five EPSs are
configured. The BSC6900 V900R015 GU supports four hardware versions: HW60 R8/HW68
R11, HW69 R11, HW69 R13, and HW69 R15.
l
Issue 09 (2015-07-27)
HW60 R8/HW68 R11 hardware: When using the HW60 R8 hardware, a BSC6000,
BSC6810, or BSC6900 GU can be upgraded to BSC6900 V900R015 by upgrading software
(version-by-version upgrade may be required). The configuration principles and capacity
2 Introduction
expansion principles remain unchanged after the upgrade. If only the software of a
BSC6000 or BSC6900 GU is upgraded to BSC6900 V900R015, the capacity remains
unchanged after the upgrade.
l
HW69 R11 hardware: When using the HW69 R11 hardware, a BSC6900 GU can be
unchanged after the upgrade. If only the software of a BSC6900 GU is upgraded to
a BSC6900 GU is upgraded to BSC6900 V900R015, the capacity remains unchanged after
the upgrade.
a BSC6900 GU is upgraded to BSC6900 V900R015, the capacity remains unchanged after
the upgrade.
NOTE
Note that if two boards work in active/standby mode, the two boards must be identical. To replace a singlecore board in a slot with a multi-core board, you must first remove the single-core board from the slot and
then insert the multi-core board into the slot.
The following BSC6900 UMTS boards can also be used in BSC6900 GSM mode (but these
GSM boards cannot be used in UMTS mode):
l
UMTS SPUc board with the same capacity as GSM XPUc board
UMTS DPUg board with the same capacity as GSM DPUg board
UMTS DPUb board with the same capacity as GSM DPUc or DPUd board
Issue 09 (2015-07-27)

Application Overview
The hardware platform of the BSC6900 is characterized by high integration, high performance,
and modular structure. These characteristics meet the networking requirements in different
scenarios and provide operators with a high-quality network at a low cost. In addition, the
network is easy to expand and maintain. Figure 3-1shows a single BSC6900 cabinet and Figure
3-2 shows its configuration.
Figure 3-1 BSC6900 N68E-22 cabinet
Issue 09 (2015-07-27)

10
Figure 3-2 Configuration of a BSC6900 cabinet (front view and rear view)
The following table describes the specifications of the BSC6900 V900R015 that adopts the
HW69 R15 hardware.
Issue 09 (2015-07-27)

11
Table 3-1 Specifications of the BSC6900 V900R015 that adopts the HW69 R15 hardware
Performance
Specifications
BSC6900
GSM
Maximum number of cabinets: 2

Maximum number of subracks: 4
Maximum GSM specifications (all-TDM transmission for
GSM): 4096 TRXs, 24,000 Erlang, 5,900,000 BHCA, 16,384
activated PDCHs, and 1536 Mbit/s bandwidth on the Gb
interface
Maximum GSM specifications (all-IP transmission for
GSM): 8192 TRXs, 45,000 Erlang, 11,000,000 BHCA,
32,768 activated PDCHs, and 3072 Mbit/s bandwidth on the
Gb interface
Maximum GSM specifications (TDM/IP hybrid transmission
for GSM): 4096 TRXs, 24,000 Erlang, 5,900,000 BHCA,
16,384 activated PDCHs, and 1536 Mbit/s bandwidth on the
Gb interface
The overall specifications of TDM and IP base stations are
smaller than or equal to the following maximum
specifications: 8192 TRXs, 45,000 Erlang, 11,000,000
BHCA, 32,768 activated PDCHs, and 3072 Mbit/s bandwidth
on the Gb interface. The actual specifications depend on the
number of configured boards and slots.
BSC6900
UMTS
Maximum number of cabinets: 2

Maximum number of subracks: 6
The maximum specifications are 3060 NodeBs, 5100 cells,
5,300,000 BHCA(7,000,000 BHCA include SMS), and 40
Gbit/s or 167,500 Erlang.
Issue 09 (2015-07-27)

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

16,384 activated PDCHs, and 1536 Mbit/s bandwidth on
the Gb interface
When the maximum GSM specifications are reached, the
UMTS processing capabilities of the BSC6900
V900R015 are 1440 NodeBs, 2400 cells, 1675,000
BHCA, and 12.8 Gbit/s or 53,600 Erlang.
The preceding specifications are provided by full
configuration of GSM boards in four subracks and UMTS
boards in two subracks.
l Maximum GSM specifications (all-IP transmission for
32,768 activated PDCHs, and 3072 Mbit/s bandwidth on
the Gb interface
When the maximum GSM specifications are reached, the
UMTS processing capabilities of the BSC6900
V900R015 are 3060 NodeBs, 5100 cells, 1675,000
BHCA, and 12.8 Gbit/s or 53,600 Erlang.
configuration of GSM boards in four subracks and UMTS
boards in two subracks.
l Maximum UMTS specifications: 3060 NodeBs, 5100
cells, 4430,000 BHCA, and 33.6 Gbit/s or 140,700 Erlang.
When the maximum UMTS specifications are reached,
the GSM processing capabilities of the BSC6900
V900R015 are 1536 TRXs, 9750 Erlang,
and 2625000 BHCA. In all-TDM or all-IP transmission
mode, the BSC supports 3584 TRXs, 22750 Erlang,
and 6125000 BHCA.
configuration of UMTS boards in five subracks and GSM
boards in one subrack.
Structural
Specifications
Dimensions of the BSC6900 N68E-22 cabinet: 2200 mm (height) x 600

mm (width) x 800 mm (depth)
Single cabinet weight 320 kg; load-bearing capability of the floor 450
kg/m2
Power Supply
Specifications
Issue 09 (2015-07-27)
48 V DC
Input voltage range: 40 V to 57 V

13
NOTE
l The BSC6900 specifications cannot be accumulated by the specifications of boards.

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

14
4 Product Configurations
Product Configurations
About This Chapter

4.1 BSC6900 GSM Product Configurations
4.2 BSC6900 UMTS Product Configurations
4.3 BSC6900 GU Product Configurations
4.4 Examples of Typical Configurations
Issue 09 (2015-07-27)

15
4.1 BSC6900 GSM Product Configurations

A BSC6900 GSM consists of hardware and hardware capacity licenses. The hardware to be
configured includes cabinets, subracks, data processing units, signaling processing units,
network intelligence units, Service Aware Unit, interface boards, and clock boards. The
hardware capacity license to be configured is the network intelligence throughput license, Mega
BSC License and BBU Carrier Capacity License.
The following table lists the mapping between hardware versions and GBSS versions.
Table 4-1 Mapping between hardware versions and GBSS versions
Hardwa
re
Version
BSC6000
BSC6900
GBSS6.1/
GBSS7.0/
GBSS8.0/
GBSS8.1
GBSS9.0
GBSS12.0
GBSS13.0
GBSS14.0
GBSS15.0
HW60
R8
Supported
Supported
Supported
Supported
Supported
Supported
HW69
R11
Supported
Supported
Supported
Supported
Supported
HW69
R13
Supported
Supported
Supported
HW69
R15
Supported
NOTICE
If two boards work in active/standby mode, the two boards must be identical.
To replace a single-core board with a multi-core board, you must configure data related to board
removal and addition before replacing the board. Do not directly remove the single-core board
and then insert the multi-core board into the slot.
Section 4.1.1 Hardware Capacity License Configurations describes the configuration
principles of hardware capacity licenses. Sections 4.1.2 Service Processing Units
Configurations through 4.1.8 Auxiliary Materials cover the configuration principles of the
BSC6900 GSM hardware and relevant restrictions.
4.1.1 Hardware Capacity License Configurations

No new licenses are provided by the BSC6900 V900R015 GSM.
Issue 09 (2015-07-27)

16
4.1.2 Service Processing Units Configurations

The following table lists the service processing units required by the BSC6900 GSM that adopts
the HW69 R15 hardware.
Table 4-2 Service Processing Units
Model
Abbre
viatio
n
Name
Descriptio
n
Specification
Remarks
WP1D00
0DPU05
DPUf
CS Data
Processing
Unit
(1920CIC/
3840 IWF
(TDM&IP)/
7680IWF
(IP&IP))
Provides CS
service
processing
(including
the TC
function and
IWF
function)
and works in
N+1 backup
mode
TC function:
1920 CIC
circuits (A over
TDM)
For the TC
function, the
specification of
WP1D000DPU05
is 1920CIC when
non-wideband
AMR coding
schemes are used.
When wideband
AMR coding
schemes are used,
the specifications
of
WP1D000DPU05
are1/2 of those
listed in the left
column (960
CICs).
IWF function:
3840 channels
(Abis over IP
and Ater over
TDM, or Abis
over TDM and
A over IP)
7680 CIC
circuits (Abis
over IP and A
over IP)
For the IWF

function, the
specifications of
the DPUf are
unchanged
regardless of
whether nonwideband or
wideband AMR
coding schemes
are used. This is
because TC
coding is not
involved in the
IWF function.
Issue 09 (2015-07-27)

17
Model
Abbre
viatio
n
Name
Descriptio
n
Specification
Remarks
WP1D00
0DPU06
DPUg
PS Data
Processing
Unit (1024
PDCH)
Provides PS
service
processing
and works in
N+1 backup
mode
1024 activated
PDCHs
The specifications
remain unchanged
regardless of the
coding schemes
(CS1 to CS4,
MCS1 to MCS9,
and EDGE+).
PS Data
Processing
Unit (1024
PDCH)
Provides PS
service
processing
and works in
N+1 backup
mode
1024 activated
PDCHs
Network
Intelligence
Unit
Provides
intelligent
service
identificatio
n
PS throughput:
50 Mbit/s
If the Gb
throughput is
higher than 50
Mbit/s, network
intelligence
throughput
licenses should be
configured.
Network
Intelligence
Throughput
License
Provides
intelligent
service
identificatio
n
PS throughput:
50 Mbit/s
One NIUa
provides 50 Mbit/s
PS throughput.
Extended
Processing
Unit (640)
Provides
signaling
processing
and works in
active/
standby
mode
GBTS:
The BHCA is
based on Huawei
default traffic
model.
WP1D00
0DPU03
WP1D00
0NIU00
DPUe
NIUa
QM1SNI
U50M00
WP1D00
0XPU03
XPUc
110 PDCH per

DSP
110 PDCH per

DSP
640 TRXs
640 Cells
The specifications
remain unchanged
regardless of the
coding schemes
(CS1 to CS4,
MCS1 to MCS9,
and EDGE+).
640 BTSs
3900 Erlang
1050K BHCA
eGBTS:
640TRX
640 Cells
640 BTSs
3900 Erlang
950K BHCA
Issue 09 (2015-07-27)

18
Model
Abbre
viatio
n
Name
Descriptio
n
Specification
Remarks
WP1D00
0XPU03
XPUc
(XPUI)
GSM
eXtensible
Processing
Unit for
Computation
service
Provides the
IBCA
function and
works in
independent
mode
None
Calculated based
on IBCA
requirements at
network
deployment.
Generally, Two
WP1D000XPU03
s are configured by
default. (A
maximum of eight
WP1D000XPU03
s can be
configured based
on the network
requirements.)
WP1D00
0SPU03
SPUc
(NASP
)
Network
Assisted
Service
Process
Provides a
service
processing
unit to assist
the network
10 AC
The number of
QM1M000SPU00
is calculated based
on
"GBFD-511609In
telligent Wi-Fi
Detection and
Selection"
requirements at
network
deployment. One
QM1M000SPU00
is configured in
each BSC by
default.
NOTE
IWF: The inter-working function (IWF) implements transmission format conversion. When Abis over IP
and Ater over TDM or A over IP are used, the IWF performs format conversion between TDM and IP or
between IP and IP.
The following table describes the network requirements that should be considered during the
configuration of WP1D000DPU05(DPUf).
Issue 09 (2015-07-27)

19
Item
Description
Remarks
Networking mode on the

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

function is implemented by the CN.
Therefore, the BSC provides the IWF
function, not the TC function.
APortType
In BM/TC separated configuration

mode, DPUf in the TC subrack provides
the TC function. Whether the BM
subrack provides the IWF function
depends on the transmission mode. The
BM subrack needs to provide the IWF
function only when TDM transmission is
used on the Ater interface and IP
transmission is used on the Abis
interface.
In BM/TC combined configuration
mode, the DPU board provides both the
TC and IWF functions. Therefore, no
extra IWF function board is required.
Issue 09 (2015-07-27)
MaxACICPerBSC,
WbAMRRate
Number of CIC
circuits on the A
interface (nonwideband AMR
coding scheme):
including the FR,
HR, and all types of
AMR coding
schemes
Calculated based on the actual number of

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

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


20
Item
Description
Remarks
MaxACICPerBSCIP
Number of CIC
circuits on the A
interface when IP
transmission is used
on the A interface

MaxIWFPerBSCTDMIP
Number of CIC
circuits in Abis over
IP and Ater over
TDM or in Abis over
TDM and A over IP
Calculated based on the network

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

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

The number of WP1D000DPU05s to be configured depends on the number of required CIC
circuits. WP1D000DPU05s can work in N+1 backup mode.
1.
In BM/TC separated configuration mode (or TDM/IP hybrid transmission in A over IP)
On the BM side:
The number of DPUf to be configured depends on the number of CIC circuits that require
IWF conversion between TDM and IP and between IP and IP.
Number of DPUf = RoundUp( MAXIWFPerBSCTDMIP / 3840 + MAX
(MAXIWFPerBSCIPIP - MAXIWFPerBSCTDMIP, 0) / 7680,0)+1
On the TC side:
Number of DPUf = ROUNDUP(MaxACICPerBSCTDM/1920) + 1
2.
In BM/TC combined configuration mode (or TDM/IP hybrid transmission in A over IP)
The DPUf providing the TC function can support the IWF function of the same
specifications as DPUf.
Extra DPUf should be configured to provide the IWF function for the A-interface CIC
circuits in A over IP transmission.
Number of DPUf = RoundUp(MaxACICPerBSCTDM/ 1920,0) + RoundUp
( MAXIWFPerBSCTDMIP / 3840 + MAX (MAXIWFPerBSCIPIP MAXIWFPerBSCTDMIP, 0) / 7680,0)+1
3.
A over IP:
The number of DPUf to be configured depends on the number of CIC circuits that require
IWF conversion between TDM and IP and between IP and IP.
Number of DPUf = RoundUp(MAXIWFPerBSCTDMIP / 3840 + MAX
(MAXIWFPerBSCIPIP - MAXIWFPerBSCTDMIP, 0) / 7680,0) +1
4.
IP transmission on all interfaces of the BSC6900 GSM

Number of DPUf = ROUNDUP(MaxACICPerBSCIP/7680) + 1
Issue 09 (2015-07-27)

21
Configuration principles of WP1D000DPU06 (DPUg):

configuration of WP1D000DPU06 (DPUg).
Item
Description
Remarks
MaxActivePDCHPerBSC
Maximum number of activated

PDCHs
Calculated based on the number

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

If intelligent service identification is required, NIUa need to be configured.

Number of NIUa required in a network = 1
One NIUa provides 50 Mbit/s throughput processing capability. If Gb throughput is higher than
50 Mbit/s, you need to apply for the Network Intelligence Throughput License and ensure that:
N_QM1SNIU50M00 = ROUNDUP[(Gb throughput 50)/50, 0].
Otherwise,
N_QM1SNIU50M00 = 0
configuration of WP1D000XPU03 (XPUc).
Issue 09 (2015-07-27)
Item
Description
Remarks
BHCA requirement
BHCA that need to be supported

in the network


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

network plan
ERL Number
CS traffic volume (Erlang) that

needs to be supported in the
network

network plan
The number of XPUc to be configured depends on the total number of TRXs, BHCA
requirement, and CS traffic volume (Erlang) requirement.
If a BSC connects to GBTSs only:
Number of (XPUc) = 2*RoundUp(max[TRX Number/640, BHCA requirement /1050K, ERL
Number/3900], 0)
If a BSC connects to eGBTSs only:
Number of (XPUc) = 2*RoundUp( max[ TRX Number/640, BHCA requirement/950K,ERL
Number/3900], 0 )
If a BSC connects to GBTSs and eGBTSs:
Number of (XPUc) = 2*RoundUp( max ( TRX Number/640, BHCA requirement*GBTS TRX
Number/TRX Number/1050K + BHCA requirement*eGBTS TRX Number/TRX Number/
950K , ERL Number/3900), 0 )
configuration of WP1D000XPU03(XPUI).
Item
Description
Remarks
IBCA requirement
Whether the network

requires the IBCA function
Calculated based on the number of

users and the traffic model.
A pair of XPUI is configured by default. A maximum of three pairs of XPUI can be configured
based on the network requirements.
If the IBCA function is required, an extra pair of XPUc should be configured to work as XPUI.
The following table lists the network factors that must be considered during the configuration
of WP1D000SPU03 (NASP).
Issue 09 (2015-07-27)

23
Item
Description
comment
NASP Needs
Whether the network requires

the IBCA function
Calculated based on
"GBFD-511609Intelligent WiFi Detection and Selection"
requirements at network
deployment. One NASP board is
configured in each BSC.
4.1.3 Interface Boards Configurations

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

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

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

Electrical)
IP transmission: A/
Abis/Lb/Gb/Iur-g
WP1D000GO
U03
GOUe
IP Interface Unit (4 GE, Optical)
IP transmission: A/
Abis/Lb/Gb/Iur-g
The following table lists the specifications of interface boards on different interfaces.
Issue 09 (2015-07-27)

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

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

25
NOTE
In Abis over TDM, the EIUb supports a maximum of 384TRXs, the OIUb supports a maximum of 384
TRXs, and the POUc supports a maximum of 512 TRXs when all the following conditions are met:
l The EIUb/OIUb/POUc must be configured to work in active/standby mode. If these boards work in
independent mode, the number of TRXs supported needs to be reduced by half. For details, see the
RED parameter in the ADD BRD command.
l The traffic model is 5.86 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.
l In fixed Abis networking, idle timeslots and monitoring timeslots must be properly configured.
Otherwise, the number of TRXs supported by the EIUb/OIUb/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.
The configuration principles of interface boards are as follows:

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

You can first select the types of interface board based on the network plan. The number of
required Abis interface boards can be calculated on the basis of either of the following two
aspects: service capability (number of TRXs supported) and port requirement. The number
of required Abis interface boards is the larger one of the two values calculated from the
two aspects.
The following table describes the network requirements that should be considered during
the configuration of Abis interface boards.
Item
Sub_Item
Description
Remarks
AbisTRXNum
ber
TRXNoTDME
1
Number of TRXs in Abis over

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

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

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

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

on the Abis interface
AbisIPE1No
Maximum number of IP-based

E1 ports required by a BSC on the
Abis interface
AbisPortNum
ber
Issue 09 (2015-07-27)

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

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

STM-1 ports required by a BSC
on the Abis interface (one STM-1
is equal to 63 E1s)
Remarks
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 board), 0)
NOTE
The number of Abis interface boards to be configured is determined based on the number of TRXs
and the number of ports. If a base station uses TDM transmission on the Abis interface, the base
station requires one E1 port by default.
If Abis over TDM is used, either of the following conditions must be met:
l Active/standby mode: Number of TRXs supported by the TDM interface board x
(Average number of Erlangs per TRX + Average number of PDCHs per TRX x Number
of timeslots required for PS transmission) 7680
l Independent mode: Number of TRXs supported by the TDM interface board x (Average
number of Erlangs per TRX + Average number of PDCHs per TRX x Number of
timeslots required for PS transmission) 4096
The following table lists the number of timeslots required for PS transmission.
Issue 09 (2015-07-27)
Number of timeslots required for PS

transmission
Value
CS-1
CS-2
CS-3
CS-4
MCS-1
MCS-2
MCS-3
MCS-4
MCS-5
MCS-6

27
Number of timeslots required for PS

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

required A interface boards can be calculated based on the service capability (number of
CIC circuits supported).
the configuration of A interface boards.
Item
Sub_Item
Description
Remarks
ACICNumber
MaxACICPe
rBSCTDM
Maximum number of CIC

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

circuits required by a BSC on
the A interface (IP
transmission)
Number of A interface boards = 2 x ROUNDUP (AbisCICNumber/Number of CIC circuits

supported by an A interface board, 0)
NOTE
If the A interface supports multiple transmission modes, then the number of interface boards of each
type should be calculated.
3.
Number of interface boards required on the Ater interface

required Ater interface boards can be calculated based on the service capability (number
of CIC circuits supported).
Issue 09 (2015-07-27)

28
the configuration of Ater interface boards.
Item
Sub_Item
Description
Remarks
AterCICNum
ber
MaxAterCICPe
rBSC

circuits required by a BSC
on the Ater interface
Calculated based on
the traffic model
Number of Ater interface boards = 2 x ROUNDUP (AterCICNumber/Number of CIC

circuits supported by an Ater interface board, 0)
NOTE
If the Ater interface supports multiple transmission modes, then the number of interface boards of
each type should be calculated.
4.
Number of interface boards required on the Gb interface
required Gb interface boards can be calculated based on the service capability (bandwidth
supported).
configuration of Gb interface boards.
Item
Sub_Item
Description
Remarks
GbThroughput
GbFRTputPerBSC
Overall traffic volume of a

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

BSC on the Gb interface in
IP transmission mode
Number of Gb interface boards = 2 x ROUNDUP (GbThroughput/Bandwidth supported by a

Gb interface board, 0)
NOTE
If the Gb interface supports multiple transmission modes, then the number of interface boards of each type
should be calculated.
4.1.4 Clock Boards Configurations

The following table lists the clock boards required by the BSC6900 GSM that adopts the HW69
R15 hardware.
Issue 09 (2015-07-27)

29
Table 4-5 Clock boards

Model
Abbreviatio
n
Name
Function
WP1D000GCU02
GCUb
General Clock Unit
Provides general
clock signals
QW1D000GCG02
GCGb
GPS&Clock Processing Unit
Provides GPS clock

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

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

BSC6900 GSM service processing boards, such as XPU and DPU, work in resource pool mode
within in a BSC. Services carried on TRXs connected to interface boards in a subrack are
preferentially processed by service processing units (XPU on the signaling plane and DPU on
the PS service plane) in the same subrack. If the resources required by a subrack exceed the
specified threshold, load sharing is implemented between subracks of the BSC. Service
processing units (DPU on the CS service plane)processing services carried on TRXs connected
to interface boards work in resource pool mode: In A over TDM mode, services carried on TRXs
connected to interface boards are preferentially processed by service processing units in the same
subrack as the A interface board. In A overIP and Abis over TDM modes, services carried on
TRXs connected to interface boards are preferentially processed by service processing units in
the same subrack as the Abis interface board. In A over IP and Abis over IP modes, intra-BSC
resource pool mode is applied, without any subrack preferred. Other boards are configured
according to the following principles:
1.
Interface boards and service processing units should be distributed as evenly as possible
among subracks. This reduces the consumption of processor resources and switching
resources by inter-subrack switching. Interface boards can be configured only in rear slots,
and service processing units can be configured in front or rear slots. It is recommended that
service processing units be configured in front slots.
Under a BSC, A interface boards, Ater interface boards, Abis interface boards, XPUc,
DPUf, and DPUg should all be distributed as evenly as possible among subracks.
Configuring the same type of board in the same subrack lowers system reliability.
2.
If POUc boards are used as A interface boards, DPUf should be configured in proportion
to the number of POUc boards in the same subrack. In full configuration, the ratio of the
number of pairs of POUc boards to the number of DPUf should be 1:4 in the same subrack,
and the maximum ratio should be 1:2. If the traffic volume is small, a pair of POUc boards
and one DPUf can be configured in a subrack.
3.
No.7 signaling links should be configured on different A and Ater interface boards. This
reduces the impact of transmission faults and board faults on the system.
Issue 09 (2015-07-27)

30
If there are multiple pairs of No.7 signaling links, distribute them evenly among interface
boards based on the quantities of A and Ater interface boards. In principle, the bandwidth
of the signaling links carried on a pair of single-core interface boards cannot exceed 2 Mbit/
s, and the bandwidth of the signaling links carried on a pair of multi-core interface boards
cannot exceed 8 Mbit/s.
For stability purposes, at least two No.7 signaling links need to be configured.
4.
The number of XPU boards used for signaling processing should not exceed 20 pairs. The
number of XPUI boards used for implementing the IBCA function should not exceed eight.
5.
It is recommended that one MPU be configured for each two pairs of XPUc.
6.
General principles of network planning:

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

l The TNUb boards are always installed in slots 4 and 5.BSC using the Abis over IP and
A over IP mode(include A IP over E1 or Abis IP over E1), the TNU boards do not need
to be configured, and therefore slots 4 and 5 can be configured with other boards. The
SCUa/SCUb boards are always installed in slots 6 and 7. The GCUb/GCGb boards are
always installed in slots 12 and 13.
l The DPUb/DPUc/DPUd/DPUe/DPUf/DPUg/NIUa boards can be installed in front or
rear slots. It is recommended that they be installed in front slots.
l The EIUb/PEUc/AEUa/OIUb/AOUc/ UOIc/ POUc/ FG2c/GOUe boards are interface
boards. They can be installed only in rear slots.
2.
The OMUc board is always configured in slots 24 and 25 of the MPS.
3.
The clock processing boards are always configured in slots 12 and 13 of the MPS.
4.
The SCUb boards are always configured in slots 6 and 7 of the MPS and EPS.
5.
The SAUc board is always configured in a slot of the MPS. A maximum of one SAUc is
configured and board redundancy is not required. MPS need reserves one slot for SAUc.
NOTE
MPU is a logical unit of XPU board, MPU work as a management function for all other boards and
transferring function for the internal signaling.

The following table lists the configuration of the subsracks.
Issue 09 (2015-07-27)

31
Table 4-6 Subracks Configurations

Model
Abbrevi
ation
Name
Function
QM1P00UMPS01
MPS
Main Processing Subrack
Main processing
subrack
QM1P00UEPS01
EPS
Extended Processing Subrack
Extended processing
subrack
WP1D000TNU01
TNUb
TDM Switching Unit
TDM switching
WP1X000OMU02
OMUc
Operation and Maintenance

Unit
Operation and
Maintenance Unit
WP1D000SAU01
SAUc
Service Aware Unit
Service Aware Unit
WP1D000SCU01
SCUb
GE Switching network and

Control Unit
GE Switching network
and Control Unit
Configuration principles of the MPS:

One MPS must be configured in a BSC6900 GSM. If IP transmission is used on all interfaces
of a BSC6900 GSM, a pair of TNUb boards is not required. If an interface of the BSC6900 GSM
does not use IP transmission, a pair of TNUb boards needs to be configured in the MPS. For a
BSC6900 GSM or a BSC6900 GU in BM/TC separated configuration mode, the MPS must work
in GSM mode.
Configuration principles of the EPS:
A maximum of three EPSs can be configured in a BSC6900 GSM. If an interface of the BSC6900
GSM does not use IP transmission, a pair of TNUb boards needs to be configured in each EPS.
Adhere to the following principles when configuring EPSs for a BSC6900 GSM:
l
All interface boards must be configured in the rear slots of an EPS. Service processing units
can be configured in the front or rear slots of an EPS.
10 rear slots of the GSM MPS are used to house GSM service processing units and interface
boards, and 8 front slots are used to house GSM service processing units.
14 rear slots of a GSM EPS are used to house GSM service processing units and interface
boards, and 10 front slots are used to house GSM service processing units.
The number of GSM subracks cannot exceed 4.
The number of GSM subracks is calculated based on the number of service processing units and
the number of interface boards.
Number of GSM_EPSs = MAX((Total number of interface boards Number of slots for
interface boards in MPS)/14, (Total number of interface boards + Total number of service
processing boards Total number of slots in MPS)/24)
The number of slots for interface boards in the MPS is 10, and the total number of slots in the
MPS is 18. If no TNUb board is configured, the total number of slots in the MPS is 20. The
number of slots for interface boards in an EPS is 14, and the total number of slots in the MPS is
24. If no TNUb board is configured, the total number of slots in an EPS is 26.
Issue 09 (2015-07-27)

32
Maximum number of TNUb = 2 x (Number of GSM_EPSs + 1)

When the BSC uses all-IP transmission, a pair of TNUb boards is not required, and therefore
two additional slots in each subrack can be used for service processing boards.
4.1.7 Cabinets Configurations

The following table lists the configuration of the cabinets.
Table 4-7 Cabinets
Model
Name
Function
WP1B4PBCBN00
BSC6900 Cabinet
Cabinet
Configuration principles of cabinets:

A maximum of two cabinets and four subracks can be configured for a BSC6900 GSM.
Number of cabinets = ROUNDUP((Number of MPSs + Number of EPSs)/3)
Here, Number of MPSs = 1.
4.1.8 Auxiliary Materials

lists the auxiliary materials for installing a BSC6900 GSM.
Table 4-8 Auxiliary materials
Model
Name
Function
QW1P8D442000
Trunk Cable
75-ohm trunk cable
QW1P8D442003
Trunk Cable
120-ohm trunk cable
QW1P0STMOM00
STM-1 Optical Connector
STM-1 optical unit
QW1P00GEOM00
GE Optical Connector
GE optical unit
QW1P0FIBER00
Optical Fiber
Optical cable
QW1P0000IM00
Installation Material
Package
Installation material suite
QMAI00EDOC00
Documentation
Electronic documentation
Configuration principles of the 75-ohm trunk cables (QW1P8D442000):

The 75-ohm trunk cables need to be in full configuration for a board.
Number of trunk cables = [Number of TDM interface units (32 E1s) + Number of IP
interface units (32 E1s)] x 2
Issue 09 (2015-07-27)

33
NOTE
One trunk cable provides eight E1s. 32 E1s/8 E1s = 4. A trunk cable is a Y-shaped cable, which is
connected to both the active and standby boards.

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

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

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

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

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

A set of electronic documentation (QMAI00EDOC00) is delivered with each BSC6900.
4.2 BSC6900 UMTS Product Configurations

A BSC6900 UMTS consists of hardware and hardware capacity licenses.
The main hardware components of the BSC6900 UMTS are service processing units, interface
boards, clock boards, subracks, and cabinets. The following sections describe the hardware
configuration scenarios and configuration methods.
The hardware to be configured includes cabinets, subracks, data processing units, signaling
processing units, network intelligence units, interface boards, and clock boards. The hardware
capacity licenses to be configured are the hardware capacity license (165 Mbit/s), hardware
capacity license (300 Mbit/s), and network intelligence throughput license.
All the product specifications can be reached when the CPU load of the hardware is 70%.
The SPUb, GOUc, GCUa, and GCGa boards can be replaced with the SPUc, GOUe, GCUb, and
GCGb boards, respectively. The specifications of the old and new boards are the same, and
therefore the configurations of an old board also apply to the corresponding new board.
Section 4.2.2 Hardware Capacity License Configurationsdescribes the configuration
principles of hardware capacity licenses. Sections4.2.3 Service Processing Units
Issue 09 (2015-07-27)

34
Configurationsthrough4.2.10 Description of Restrictions cover the configuration principles

of the BSC6900 UMTS hardware and relevant restrictions.
4.2.1 Impact of the Traffic Model on Configurations

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

The CPU overload threshold of the BSC6900 is 70%.
The capability of the DPUe (for the user plane) is calculated based on the PS RAB uplink/
downlink (UL/DL) rate (64/384 kbit/s), which is the average rate of PS services and is
independent from specific bearer type. In this case, the PS throughput of the DPUe is 800
Mbit/s. 800Mbit/s is also the maximum design specification. But in the real commercial
networks, as the rapid growth up of smart phone penetration, user plane is characterized
by numerous small packets, which leads the real throughput capacity of DPUe cannot reach
800Mbit/s, but decreases with the decrement of PS data rate.
The PS throughput decreases with the decrement of PS RAB mean data rate in active state,
as shown in Figure 4-1.
Figure 4-1 Relationship between PS Throughput supported by DPUe and PS RAB mean
data rate in active state
Issue 09 (2015-07-27)

35
PS RAB mean data rate in active state(UL+DL) = PS throughput per subscriber in BH

*3600/( PS call per sub per BH * mean hold time in Cell_DCH&Cell_FACH per PS call).
Table 4-9 Some typical PS RAB mean data rates in active state and corresponding PS
Throughput supported by DPUe
PS RAB mean data rate in
active state (UL+DL)(kbps)
16
40
64
128
196
448
PS throughput capacity per

DPUe(Mbps)
90
250
300
430
530
800
If PS RAB Mean data rate in active state (UL+DL)(kbps) ranges (0, 16], PS Throughput
Capacity per DPUe(Mbps) = PS RAB Mean data rate * 5.625;
Capacity per DPUe(Mbps) = 90+(PS RAB Mean data rate 16)* 6.67;
Capacity per DPUe(Mbps) = 250 + (PS RAB Mean data rate 40) * 2.08;
If PS RAB Mean data rate in active state (UL+DL)(kbps) ranges (448, ], PS Throughput
Capacity per DPUe(Mbps) = 800.
l
On the control plane

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

The BSC6900 V900R015 supports the hardware capacity license (165 Mbit/s), hardware
capacity license (300 Mbit/s), and network intelligence throughput license. The following
paragraphs describe the usage scenarios and configuration principles of these licenses. For
Issue 09 (2015-07-27)

36
details about how to calculate the number of licenses to be configured, see section 4.2 BSC6900
UMTS Product Configurations.
The hardware capacity license (165 Mbit/s) and hardware capacity license (300 Mbit/s) are
superposed on the hardware capacity of the DPUe hardware (335 Mbit/s) to increase the userplane processing capabilities.
The Network Intelligence Throughput license is superposed on the hardware capacity of the
NIUa board (50 Mbit/s) to provide service awareness when any of the following features is
enabled: WRFD-020132 Web Browsing Acceleration, WRFD-020133 P2P Downloading Rate
Control.
l
Hardware Capacity License (165 Mbit/s)

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

The hardware capacity license (300 Mbit/s) is applicable to the HW69 R11, HW69 R13,
and HW69 R15 hardware.
The hardware capacity license (300 Mbit/s) can be configured only for a data processing
unit DPUe (WP1D000DPU03). It increases the PS throughput of DPUe in the BSC6900
UMTS without requiring hardware replacement (it cannot increase the CS voice capacity).
The increased processing capability is an integral multiple of 300 Mbit/s. The maximum
increase in the processing capability depends on the number of configured DPUe boards
and the number of configured hardware capacity licenses (300 Mbit/s).
NOTE
1. When the number of configured hardware capacity licenses is smaller than the number of
configured DPUe boards, hardware capacity licenses can be shared among the DPUe boards of
a single BSC6900 UMTS to form a resource pool and improve resource utilization. In BSC6900
V900R015, each DPUe supports a maximum PS throughput of 800 Mbit/s.
2. Hardware capacity licenses are not automatically moved with hardware. For example, when a
DPUe is moved from one BSC6900 UMTS to another, its hardware capacity licenses are not
moved.
Assume that two DPUe boards are configured. The following table compares the PS
throughput before and after hardware capacity licenses are configured.
Comparison of the PS throughput before and after hardware capacity licenses are
configured
Issue 09 (2015-07-27)

37
Number of
Configured
WP1D000DPU03s
(DPUe)
Number of
Configure
d
Hardware
Capacity
Licenses
(165 Mbit/
s)
User Plane
Processing
Capability
(Mbit/s/
Erlang)
Number of
Configured
Hardware
Capacity
Licenses (300
Mbit/s)
User Plane
Processing
Capability
(Mbit/s/
Erlang)
670/6700
670/6700
835/6700
835/6700
1135/6700
1000/6700
1300/6700
1600/6700
1000/6700
NOTE
l User plane processing capability (Mbit/s/Erlang): indicates the maximum processing capability
of DPUe boards that process either CS services or PS services. Take two DPUe boards configured
for example. When the user plane processing capability is 670/6700 (Mbit/s/Erlang):
If the two DPUe boards process only PS services, the processing capability of the DPUe boards
is 670 Mbit/s.
If the two DPUe boards process only CS services, the processing capability of the DPUe boards
is 6700 Erlang.
If the two DPUe boards process both PS services and CS services, the two DPUe boards can meet
the user plane capacity requirements when the following condition is fulfilled:
CS traffic volume in the network/6700 Erlang + PS throughput in the network/670 Mbit/s <= 1
Two hardware capacity licenses (165 Mbit/s) and two hardware capacity licenses (300
Mbit/s) must be added to meet the user plane capacity requirements if the following
condition is fulfilled:
CS traffic volume in the network/6700 Erlang + PS throughput in the network/1600 Mbit/
s <= 1
Minimum hardware should be configured in a BSC6900 on the precondition that the
network capacity requirements are met. Therefore, hardware capacity licenses are
preferentially configured before more hardware is added.
It is necessary to be emphasized that, with the development of mainstream smart phone
network, there are numerous small packets transferred in the user plane. The hardware
throughput capacity of DPUe might be in a relatively lower range, eg, not exceeds 335Mbit/
s contained by DPUe board. In this case, the Hardware Capacity License(165Mbps) and
Hardware Capacity License (300Mbps) will not work and should not be configured. So,
the configuration of these two hardware licenses depends on the real hardware throughput
capacity of DPUe in the specific traffic model.
l
Issue 09 (2015-07-27)
Network Intelligence Throughput License

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

The following table lists the service processing units.
Table 4-10 Service processing units
Issue 09 (2015-07-27)
Model
Abbre
viatio
n
Name
Function
Specification
Condition
WP1D00
0DPU03
DPUe
Data
Processing
Unit (335
Mbit/s/
3350
Erlang)
Data
processin
g
PS Throughput
335 Mbit/s or
3350 Erlang, 300
cells, and 5880
active users
Real PS throughput of
DPUe is based on the
real traffic model.
QM1SH
W165M0
0
Hardware
Capacity
License
(165 Mbit/
s)
Data
processin
g
PS throughput:
165 Mbit/s
The configuration of
this item should be
based on the real
hardware capacity of
DPUe which can be
estimated from traffic
model.
QM1SH
W300M0
0
Hardware
Capacity
License
(300 Mbit/
s)
Data
processin
g
PS throughput:
300 Mbit/s
The configuration of
this item should be
based on the real
hardware capacity of
DPUe which can be
estimated from traffic
model.

39
Model
Abbre
viatio
n
Name
Function
Specification
Condition
WP1D00
0NIU00
NIUa
Network
Intelligenc
e Unit
Intelligent
service
identificat
ion
Hardware
capacity: 3200
Mbit/s
Optional. Used for any

of the following
features:
WRFD-020132 Web
Browsing
Acceleration,
WRFD-020133 P2P
Downloading Rate
Control during Busy
Hour.
Network
Intelligenc
e
Throughpu
t License
Intelligent
service
identificat
ion
PS throughput:
50 Mbit/s
Optional
Signaling
Processing
Unit
Signaling
processin
g
124,000 BHCA,
180 NodeBs, 600
cells, and 9000
active users,
24000 on-line
users
124000 BHCA based

on the balanced traffic
model described in
6.2.2. BHCA capacity
per SPU board is
changed with traffic
model, the real BHCA
capacity should be
calculated according
to traffic model of real
network.
QM1SNI
U50M00
QM1M0
00SPU00
/
QM1M0
00SPU03
SPUb/
SPUc
PS throughput
provided by the
NIUa hardware:
50 Mbit/s
Required only when

NIUa boards are
configured.
NOTE
l Active users: specify the users in CELL_DCH or CELL_FACH status.

l On-line users: specify the users in the RRC connection, including CELL_DCH, CELL_FACH,
CELL_PCH, and URA_PCH users.
l The number of active users is calculated by consuming Iub interface resources, but the number of online
users is not.
1.
Configuration principles of WP1D000DPU03(DPUe) and hardware capacity licenses

the configuration of DPUe.
Issue 09 (2015-07-27)
Item
Description
Remarks
Iub PS
throughput
PS throughput required on the

Iub interface


40
Item
Description
Remarks
Iub CS traffic
CS Erlang required on the Iub

interface

Active users
Number of concurrent active

users required by the
BSC6900 UMTS user plane

Cell number
Number of cells that need to be

managed by the BSC6900
UMTS
Determined based on the network

plan
a.
In a newly deployed network:

Assume that the user plane capacity requirements on the Iub interface of a network
are aMbit/s (PS throughput),bErlang (Iub CS traffic volume),c(number of cells),
andn (number of active users).
The real PS throughput capacity of DPUe can be estimated from the PS RAB mean
data rate in active state:
If PS RAB Mean data rate in active state (UL+DL)(kbps) ranges (0, 16], PS
Throughput Capacity per DPUe(Mbps) = PS RAB Mean data rate * 5.625;
Throughput Capacity per DPUe(Mbps) = 90+(PS RAB Mean data rate 16)* 6.67;
Throughput Capacity per DPUe(Mbps) = 250 + (PS RAB Mean data rate 40) * 2.08;
Throughput Capacity per DPUe(Mbps) = 300 + (PS RAB Mean data rate 64) * 2.03;
Throughput Capacity per DPUe(Mbps) = 430 + (PS RAB Mean data rate 128) *
1.47;
Throughput Capacity per DPUe(Mbps) = 530 + (PS RAB Mean data rate 128) *
1.07;
If PS RAB Mean data rate in active state (UL+DL)(kbps) ranges (448, ], PS
Throughput Capacity per DPUe(Mbps) = 800.
Then, the number of DPUe boards required in the network, represented by N_DPUe,
can be calculated with the following formula: N_DPUe = ROUNDUP(MAX(a/PS
Throughput Capacity per DPUe + b/3350, c/300, n/5880, 2))
NOTE
A minimum of two DPUe boards can be configured. A maximum of 50 DPUe boards can be
configured.
N_DPUe_PS = ROUNDUP(a/PS Throughput Capacity per DPUe)

If
N_DPUe_PS x 335 a, no hardware capacity license needs to be configured.
Otherwise,
Issue 09 (2015-07-27)

41
Number of required hardware capacity licenses (165 Mbit/s) (represented by N_165)

= Min{N_DPUe, ROUNDUP[(a N_DPUe_PS x 335)/165]}
If N_165 x 165 + N_DPUe_PS x 335 a, no hardware capacity license (300 Mbit/
s) needs to be configured. Otherwise,
Number of required hardware capacity licenses (300 Mbit/s) (represented by N_300)
= Min{N_165, ROUNDUP[(a N_DPUe_PS x 335 N_165 x 165)/300]}
b.
In capacity expansion scenarios:

Calculate the number of required DPUe boards, hardware capacity licenses (165 Mbit/
s), and hardware capacity licenses (300 Mbit/s) by referring to the calculation
procedure provided previously for a newly deployed network.
Number of DPUe boards = Number of DPUe boards after capacity expansion
Number of DPUe boards before capacity expansion
Number of hardware capacity licenses (165 Mbit/s) = Number of hardware capacity
licenses (165 Mbit/s) after capacity expansion Number of hardware capacity licenses
(165 Mbit/s) before capacity expansion
Number of hardware capacity licenses (300 Mbit/s) = Number of hardware capacity
licenses (300 Mbit/s) after capacity expansion Number of hardware capacity licenses
(300 Mbit/s) before capacity expansion
2.
Configuration principles of WP1D000NIU00(NIUa) and QM1SNIU50M00(Network

intelligence throughput license):
If the Service awareness function needs to be provided, an NIUa must be configured.
Iub PS throughput: a Mbit/s
Number of required NIUa boards (represented by N_NIUa) = ROUNDUP(a/3200, 0)
One NIUa provides 50 Mbit/s PS throughput. If the value if a is larger than 50, then
N_QM1SNIU50M00 = ROUNDUP((a N_NIUa x 50)/50, 0).
Otherwise,
N_QM1SNIU50M00 = 0.
3.
Configuration principles of QM1M000SPU00 (SPUb)/QM1M000SPU03 (SPUc)

the configuration of QM1M000SPU00 (SPUb)/QM1M000SPU03 (SPUc).
Issue 09 (2015-07-27)
Item
Description
Remarks
BHCA requirement
BHCA that need to be

supported in the network
Calculated based on the

number of users and the traffic
model.
Active users

users that need to be supported
the BSC6900 UMTS control
plane

model.
On-line users
Number of concurrent on-line

users that need to be supported
the BSC6900 UMTS control
plane

model.

42
Item
Description
Remarks
NodeB number
Number of NodeBs that need

to be managed by the
BSC6900 UMTS

network plan
Cell number
Number of cells that need to be

managed by the BSC6900
UMTS

network plan
a.

Number of SPUb(SPUc) boards = ROUNDUP(MAX(BHCA required by the target
network/BHCA supported by one SPUb(SPUc), Number of active users /Number of
active users supported by one SPUb(SPUc), Number of on-line users /Number of online users supported by one SPUb(SPUc), Number of NodeBs required by the target
network/Number of NodeBs supported by one SPUb(SPUc), Number of cells in the
target network/Number of cells supported by one SPUb(SPUc)))
The BHCA supported by one SPUb(SPUc) depend on the traffic model. If the actual
traffic model of a network differs greatly from the balanced UMTS traffic model
described in section 6.2.2 UMTS Traffic Model. BHCA supported by one SPUb
(SPUc) need to be recalculated based on the actual traffic model.
b.

Number of SPUb(SPUc) boards = Number of SPUb(SPUc) boards after capacity
expansion Number of SPUb(SPUc) boards before capacity expansion
4.2.4 Interface Boards Configurations

The BSC6900 UMTS provides various interfaces to meet the requirements of different network
structures.
1.
Specification of Interface boards

Table 4-11 lists the interface boards required by the BSC6900 UMTS that adopts the HW69
R16 hardware.
Table 4-11 Interface boards required by the BSC6900 UMTS that adopts the HW69 R16
hardware
Issue 09 (2015-07-27)
Model
Abbre
viatio
n
Name
Wher
e to
Apply
Session
Setup/
Release
Times
CID/
UDP
(Activ
e
users)
WP1D000AEU00
AEUa
ATM Interface
Unit (32 E1)
Iub
500
23,000
WP1D000PEU00
PEUc
IP Interface Unit
(32 E1)
Iub
500
23,000

43
Model
Abbre
viatio
n
Name
Wher
e to
Apply
Session
Setup/
Release
Times
CID/
UDP
(Activ
e
users)
WP1D000AOU01
AOUc
ATM Interface
Unit (4 STM-1,
Channelized)
Iub
5000
79,000
WP1D000POU01
POUc
IP Interface Unit
(4 STM-1,
Channelized)
Iub
5000
129,000
WP1D000UOI01
UOIc
ATM Interface
Unit (8 STM-1,
Unchannelized)
Iub/Iu/
Iur
5000
79,000
WP1D000GOU01
/
WP1D000GOU03
GOUc/
GOUe
IP Interface Unit
(4 GE, Optical)
Iub/Iu/
Iur-p
5000
129,000
WP1D000FG201
FG2c
5000
129,000
note
IP Interface Unit
(12 FE/4 GE,
Electrical)
Iub/Iu/
Iur-p
note
NOTE
The Iur-p is a private interface connecting RNCs to facilitate the RNC in Pool feature.
Table 4-12 Specifications of interface boards on the Iub/Iur interface

Iub/Iur
Model
Issue 09 (2015-07-27)
Node
B
Voice
(Erlan
g)
VP
(Erlan
g)
UL
(Mbit/s)
DL
(Mbit/s)
UL+DL
(Mbit/s)
WP1D000AEU00
2800
680
45
45
90
32
WP1D000PEU00
2800
850
60
60
120
32
WP1D000AOU01
18,00
0
5500
300
300
600
500
WP1D000POU01
18,00
0
6000
400
400
800
252
WP1D000UOI01
18,00
0
9000
800
800
1200
500

44
WP1D000GOU01
/
WP1D000GOU03
/WP1D000FG201
18,00
0
9,000
2600
2600
2600
500
Table 4-13 Specifications of interface boards on the Iu-CS/Iu-PS interface

Model
Iu-CS
Iu-PS
Voice
(Erlang
)
VP
(Erlang
)
UL
(Mbit/
s)
DL
(Mbit/
s)
UL+DL
(Mbit/
s)
IU PS Online Users
(TEID)
WP1D000UOI01
18,000
9000
900
900
1800
200,000
WP1D000GOU0
1/
WP1D000GOU0
3/
WP1D000FG201
18,000
9000
3200
3200
3200
200,000
NOTE
l The specifications UL (Mbit/s), DL (Mbit/s), and UL+DL (Mbit/s) listed in Table 3-4 and Table
3-5 are based on the traffic type DL/UL64/384 kbit/s.
l One active CS user consumes two CIDs/UDPs, and one active HSPA PS user consumes three
CIDs/UDPs.
l One active CS user consumes one Iu-CS CID/UDP, and one active PS user consumes one Iu-PS
TEID(Tunnel Endpoint ID).
l The number of session setups/releases indicates the signaling processing capability of interface
boards and is applicable to the Iub and Iu interfaces. The following table lists the mapping
between the interface signaling processing requirements and the traffic model.
Table 4-14 Session setup/release times in Iub/Iu for every signaling procedure in traffic
model
Issue 09 (2015-07-27)
Control Plane Traffic

Parameter
Unit
Iub session
setup / release
times
Iu-PS session
setup/release
times
CS voice call per

subscriber per BH
times
Handover times per CS

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

BH
times

45
Control Plane Traffic

Parameter
Unit
Iub session
setup / release
times
Iu-PS session
setup/release
times
Handover times per PS

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

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

subscriber per BH (times)
times/per
subscriber
NOTE
The specifications of interface boards on the Iur interface are the same as those of interface boards
on the Iub interface.
The processing capability specifications of each interface board are the maximum specifications
when the interface board processes only the corresponding type of service. The configured
specifications are listed in the "NodeB" column.
2.
Configuration rules of interface boards
configuration of interface boards.
Issue 09 (2015-07-27)
Interface
Item
Description
Remarks
Iub
Iub transmission
type
Transmission type used on

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

be supported on the Iub
interface

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

supported on the Iub
interface
Iub session setup

and release
requirement in BH
Session setup and release

capacity that matches the
network BHCA capacity
Iub active users

(CID/UDP)

users (CID/UDP)that need
to be supported the
BSC6900 UMTS user plane.

46
Interface
Iu-CS
Iu-PS
Item
Description
Remarks
NodeB number
Number of NodeBs that

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

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

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

traffic model.
Iu-CS session setup

and release
requirement in BH
Number of sessions that

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

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

be supported on the Iu-PS
interface

traffic model.
Iu-PS on-line users
Number of concurrent online users that need to be

supported the Iu-PS
interface of the BSC6900
UMTS
Iu-PS session setup

and release
requirement in BH
Number of sessions that

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

1.
The number of interface boards required on the Iub interface can be calculated in the
following way:
The Iub interface can use any of the following transmission modes:
Case 1: hybrid Iub - E1 (ATM) && Iub-Ethernet (IP);
Case 2: hybrid Iub - E1 (IP) && Iub-Ethernet (IP);
Case 3: hybrid Iub - VC12-STM-1 (ATM) && Iub-Ethernet (IP);
Issue 09 (2015-07-27)

47
Case 4: hybrid Iub - VC4-STM-1 (ATM) && Iub-Ethernet (IP);

Case 5: hybrid Iub - VC12-STM-1 (IP) && Iub-Ethernet (IP);
Case 6: E1 (ATM);
Case 7: VC12 - STM-1 (ATM);
Case 8: VC4 - STM-1 (ATM);
Case 9: E1 (IP);
Case 10: Ethernet (IP);
Case 11: VC12 - STM-1 (IP)
The number of required Iub interface boards can be calculated on the basis of any of the
following aspects: service processing capability (Erlang and payload throughput), port
bandwidth, number of NodeBs, signaling processing capability, and number of concurrent
active users. The required number of Iub interface boards is the maximum among these
values calculated from the preceding aspects.
Number of Iub interface boards = MAX(Number of Iub interface board_Traffic, Number
of Iub interface board_Bandwidth, Number of Iub interface board_NodeB, Number of Iub
Interface Board_Session setup/release, Number of Iub Interface Board_CIDUDP)
where,
Number of Iub interface board_Traffic = Iub Voice Traffic/Iub Voice specification + Iub
CS Data Traffic/Iub CS data specification + MAX((Iub PS DL Throughput + MBMS
traffic)/Iub PS DL specification, Iub PS UL Throughput/Iub PS UL specification, (Iub PS
DL Throughput + MBMS traffic+ Iub PS UL Throughput)/Iub PS DL+UL specification)
Number of Iub interface board_Bandwidth = (Iub OAM Transmission bandwidth
requirement + MAX(Iub DL Transmission Bandwidth (data) +Iub DL Transmission
Bandwidth (signaling) +Iub DL MBMS Transmission Bandwidth, Iub UL Transmission
Bandwidth (data) + Iub UL Transmission Bandwidth (signaling)))/Transmission
Bandwidth per Interface port/Number of ports per interface board
Number of Iub interface board_NodeB = NodeB number/NodeB Capacity per Interface
Board
Number of Iub Interface Board_Session setup/release
= Iub session setup and release requirement in BH/capacity of session setup and session
release per second of interface board/3600
Number of Iub Interface Board_CIDUDP
= Iub active users (CID/UDP)/CIDUDP supported by per interface board
In the preceding formulas, Iub Voice specification, Iub CS data specification, Iub PS DL
specification, Iub PS UL specification, Iub PS DL + UL specification, Number of ports per
interface board, NodeB capacity per interface board, capacity of session setup and session
release per second of interface board, and active users supported by per interface board are
specifications of interface boards(CID/UDP). The other items are the results of BSC6900
dimensioning.
2.
The Iur, Iu-CS, and Iu-PS interfaces can use any of the following transmission modes:
Case 1: VC4-STM-1 (ATM);
Case 2: GE Electrical (IP);
Case 3: GE Optical (IP);
The numbers of required Iur, Iu-CS, and Iu-PS interface boards can be calculated on the
basis of any of the following four aspects: service processing capability (Erlang and payload
Issue 09 (2015-07-27)

48
throughput), port bandwidth, signaling processing capability, and number of concurrent

active users. The required numbers of Iur, IU-CS, and Iu-PS interface boards are the
maximum among the four values calculated from the preceding four aspects.
For the Iu-CS interface,
Number of Iu-CS interface board_Traffic
= Iu-CS CS Voice Traffic/Iu-CS Voice specification + Iu-CS CS Data Traffic/Iu-CS data
specification
Number of Iu-CS interface board_Bandwidth
= MAX((Iu-CS DL Transmission Bandwidth (data) + Iu-CS DL Transmission Bandwidth
(signaling)), (Iu-CS UL Transmission Bandwidth (data) + Iu-CS UL Transmission
Bandwidth (signaling)))/Transmission Bandwidth per Interface port/Number of ports per
interface board
Number of Iu-CS Interface Board_Session setup/release
= Iu-CS session setup and release requirement in BH/Capacity of session setup and session
Number of Iu-CS Interface Board_CIDUDP
= Iu-CS active users/CIDUDP supported by per interface board
Number of Iu-CS interface board
= MAX(Number of Iu-CS interface board_Traffic, Number of Iu-CS interface
board_Bandwidth, Number of Iu-CS Interface Board_Session setup/release, Number of IuCS Interface Board_CIDUDP)
For the Iu-PS interface,
Number of Iu-PS interface board_Traffic
= MAX[Iu-PS DL Throughput/Iu PS DL specification, Iu-PS UL Throughput/Iu PS UL
specification, (Iu-PS DL Throughput + Iu-PS UL Throughput)/Iu PS DL+UL specification]
Number of Iu-PS interface board_bandwidth
= MAX[Iu-PS DL Transmission Bandwidth (data) + Iu-PS DL Transmission Bandwidth
(signaling), Iu-PS UL Transmission Bandwidth (data) + Iu-PS UL Transmission Bandwidth
(signaling)]/Transmission Bandwidth per Interface port/Number of ports per interface
board
Number of Iu-PS Interface Board_Session setup/release
= Iu-PS session setup and release requirement in BH/Capacity of session setup and session
Number of Iu-PS Interface Board_on-line users
= Iu-PS on-line users/on-line users supported by per interface board
Number of Iu-PS interface board
= MAX(Number of Iu-PS interface board_Traffic, Number of Iu-PS interface
board_bandwidth, Number of Iu-PS Interface Board_Session setup/release, Number of IuPS Interface Board_on-line users)
For the Iur interface,
Number of Iur interface boards_Traffic
= Iur Voice Traffic/Iub CS Voice_specification + Iur CS Data Traffic/Iub CS
data_specification + MAX(Iur PS DL Throughput/Iub PS DL_specification, Iur PS UL
Throughput/Iub PS UL_specification)
Issue 09 (2015-07-27)

49
Number of Iur interface board_bandwidth

= MAX[Iur DL Transmission Bandwidth (data) + Iur DL Transmission Bandwidth
(signaling), Iur UL Transmission Bandwidth (data) + Iur UL Transmission Bandwidth
(signaling)]/Transmission Bandwidth per Interface port/Number of ports per interface
board
Number of Iur Interface Board_Session setup/release
= Iur session setup and release requirement in BH/Capacity of session setup and session
Number of Iur Interface Board_CIDUDP
= Total Iur active users(CID/UDP)/CIDUDP supported by per interface board
Number of Iur interface boards
= MAX(Number of Iur interface board_Traffic, Number of Iur interface board_bandwidth,
Number of Iur Interface Board_Session setup/release, Number of Iur Interface
Board_CIDUDP)
If there are several IUR interfaces, and it is not allowed that these IUR interfaces share
ports of interface board with each other, then:
Number of Iur Interface Board_port number
=Iur interface number/ port number per interface board
Number of Iur interface board
= MAX(Number of Iur interface board_Traffic, Number of Iur interface board_bandwidth,
Number of Iur Interface Board_Session set-up/release, Number of Iur Interface
Board_CIDUDP, Number of Iur Interface Board_port number)
In the preceding formulas, the following items are the specifications for the interface
boards: Iu-CS voice specification, Iu-CS data specification, Iu-PS DL specification, Iu-PS
UL specification, Iu-PS DL + UL specification, Number of ports per interface board,
Transmission bandwidth per interface port, Number of session setups and releases per
second of interface board, and active users supported by per interface board. The other
items are the results of BSC6900 dimensioning.
3.
RNC interface boards supports the two backup modes:

a.
In 1+1 backup mode, the actual number of interface boards required is twice the
number calculated according to the network capacity requirements.
The number of interface boards is the sum of interface boards required on the Iub, IuCS, Iu-PS, and Iur interfaces, SUM(N_IUB_INT, N_Iu-CS_INT, N_Iu-PS_INT,
N_Iur)*2
b.
The BSC6900 UMTS supports the N+1 backup mode on only the FG2c and GOUc/
GOUe boards with resource pools enabled.
If Iu-CS Iu-PS Iur share the interface board, the number of interface boards should be
calculated from: ROUNDUP(N_IUB_INT, 0)+1, ROUNDUP[SUM(Iu-CS, Iu-PS,
Iur, 0)] +1.
Issue 09 (2015-07-27)

50
4.2.5 Clock Boards Configurations

Table 4-15 Clock boards
Model
Abbreviatio
n
Name
Function
WP1D000GCU01/
WP1D000GCU02
GCUa/GCUb
General Clock Unit
Provides general clock

signals
QW1D000GCG01/
QW1D000GCG02
GCGa/GCGb
GPS&Clock Processing
Unit
Provides GPS clock

signals
The GCUa(GCUb) is optional. When a BSC6900 UMTS does not use GPS clock signals, a pair
of general clock units can be configured for the BSC6900 UMTS.
The GCGa(GCGb) is optional. When a BSC6900 UMTS needs to use GPS clock signals, a pair
of GPS&clock processing units can be configured for the BSC6900 UMTS.
4.2.6 Principles for Board Configurations

Boards must be configured in slots according to the following principles:
1.
An OMUc board must be configured in slots 24 and 25 of the MPS.
2.
Clock boards (GCU/GCG) must be configured in slots 12 and 13 of the MPS.
3.
The SCUb boards must be configured in slots 6 and 7 of the MPS and EPS.
4.
Service processing units (DPUe/SPUb/SPUc/NIUa) can be configured in any slots except

the slots for the OMUc, clock boards, and SCUb boards. It is recommended that service
processing units be configured in small-numbered slots (starting from slot 0) and largenumbered slots be reserved for interface boards.
5.
Interface boards can be configured only in slots 14 to 27 (except slots 24 and 25 in the
MPS).
6.
Service processing units and interface boards must be distributed evenly among subracks
to reduce the CPU and swapping resources consumed during inter-subrack switching and
avoid the inter-subrack bandwidth limiting the traffic volume. Assume that there are 9
DPUe boards, 12 SPUb(SPUc) boards, 6 interface boards, and 3 subracks. Then, it is
recommended that 3 DPUe boards, 4 SPUb(SPUc) boards, and 2 interface boards be
configured in each subrack.
7.
The SPU boards must be configured in active/standby mode. The DPU and NIU boards
must be configured in load sharing mode by using a resource pool. The OMU, SCU, and
GCU/GCG boards must be configured in active/standby mode. Two slots must be reserved
for the SAU boards (one or two SAU can be configured).
8.
The MPS supports a maximum of 9 pairs of SPU boards and 9 DPUe boards.
9.
The EPS supports a maximum of 9 pairs of SPU boards and 9 DPUe boards.
10. It is recommended that the SAU be configured in the MPS with two slots reserved.
11. It is recommended that the Iur-P interface board used for the RNC In Pool feature be
configured in the MPS.
Issue 09 (2015-07-27)

51
For the actual configuration operation, see Examples of Typical Configurations in section 4.4.2
BSC6900 UMTS Examples of Typical Configurations.

The following table lists the configuration of the subracks.
Table 4-16 Configuration of the Subracks
Model
Abbrevia
tion
Name
QM1P00UMPS01
MPS
QM1P00UEPS01
EPS
WP1X000OMU02
OMUc
Operation and Maintenance Unit
WP1D000SAU01
SAUc
Service Aware Unit
WP1D000SCU01
SCUb
GE Switching network and Control Unit
Configuration principles of the MPS:

One MPS must be configured in a BSC6900 UMTS.
Configuration principles of the EPS:
A maximum of five EPSs can be configured in a BSC6900 UMTS.
1.

Number of EPSs_1 = ROUNDUP[(Number of required SPU boards Number of SPU
boards that can be housed by MPS)/9]
If Number of required SPU boards < Number of SPU boards that can be housed by MPS,
then Number of EPSs_1 = 0.
Number of SPU boards that can be housed by MPS = 9
Number of SPU boards can be housed in the MPS: 9 pairs
Number of SPU boards can be housed in the EPS: 9 pairs
Number of EPSs_2 = ROUNDUP[(Number of required DPUe boards Number of DPUe
boards that can be housed by MPS)/9]
If Number of required DPUe boards < Number of DPUe boards that can be housed by MPS,
then Number of EPSs_2 = 0.
Number of DPUe boards that can be housed by MPS = 9
Number of DPUe boards can be housed in the EPS: 9
Number of EPSs_3 = ROUNDUP[((Number of slots required by interface boards Number
of slots for interface boards in MPS)/14), 0]
If Number of slots required by interface boards < Number of slots for interface boards in
MPS, then Number of EPSs_3 = 0.
Number of slots for interface boards in MPS = 12
Issue 09 (2015-07-27)

52
Number of EPSs_4 = ROUNDUP[(Number of required SPUb boards x 2Note + Number of

required DPUe boards + Number of slots required by interface boards + Number of required
NIUa boards Number of slots in MPS)/26]
If Number of required SPU boards x 2 + Number of required DPUe boards + Number of
slots required by interface boards + Number of required NIUa boards < Number of slots in
MPS, then Number of EPSs_4 = 0.
Number of slots in MPS = 20 (Two slots have been reserved for the SAUc.)
Number of EPSs = MAX(Number of EPSs_1, Number of EPSs_2, Number of EPSs_3,
Number of EPSs_4)
NOTE
The number of slots occupied by each pair of SPUb is 2.
The default number of SAU board is one for EBC. If the customer has purchased and used
Huawei Nastar or other OSS feature such as SON, one or two SAUc boards need to be
configured in the MPS of the BSC6900. The number of SAUc boards is up to OSS.
2.
Configuration Scenarios
Number of SAU
boards (pcs)
Nastar Only
At least one in EBC and SON
Nastar, and at least one in EBC and SON

Number of EPSs = Number of EPSs after capacity expansion Number of EPSs before
capacity expansion
4.2.8 Cabinets Configurations

The following table lists the configuration of the cabinets.
Table 4-17 Cabinets
Model
Name
Function
WP1B4PBCBN00
BSC6900 cabinet
Cabinet
Configuration principles of cabinets:

A maximum of two cabinets can be configured for a BSC6900 UMTS. Each cabinet can
accommodate three subracks.
1.

Number of cabinets = ROUNDUP((Number of MPSs + Number of EPSs)/3, 0)
Here, Number of MPSs = 1.
2.
Issue 09 (2015-07-27)

53
Number of cabinets = Number of cabinets after capacity expansion Number of cabinets

before capacity expansion
4.2.9 Auxiliary Materials

The following table lists the auxiliary materials.
Table 4-18 Auxiliary materials
Model
Name
Function
QW1P8D442000
Trunk Cable
75-ohm trunk cable
QW1P8D442003
Trunk Cable
120-ohm trunk cable
QW1P0STMOM00
STM-1 Optical Connector
STM-1 optical unit
QW1P00GEOM00
GE Optical Connector
GE optical unit
QW1P0FIBER00
Optical Fiber
Optical cable
QW1P0000IM00
Installation Material
Package
Installation material suite
QMAI00EDOC00
Documentation
Electronic documentation

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

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

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

The GE optical units need to be in full configuration for an optical interface board.
Issue 09 (2015-07-27)

54
Number of GE optical units = Number of WP1D000GOU01s x 4

l
Configuration principle of the optical cables (QW1P0FIBER00):

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

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

A set of electronic documentation (QMAI00EDOC00) is delivered with each BSC6900.
4.2.10 Description of Restrictions

Principles on inter-subrack switching
Huawei BSC6900 V900R011 uses the SCUa boards. A pair of active and standby SCUa boards
can process data at 4 Gbit/s on the physical layer. The SCUa boards in various subracks are
connected in star networking mode. Huawei BSC6900 V900R013 uses the SCUb boards. A pair
of active and standby SCUb boards can process data at 40 Gbit/s on the physical layer. The
SCUb boards in various subracks are connected in chain mode.
If either of the active and standby board becomes faulty, the processing capability is halved.
If the SCU boards are not evenly configured among the subracks or services are not evenly
deployed among the subracks, the volume of inter-subrack data flows may sharply increase.
Once the volume exceeds the capacity, services are interrupted. Therefore, all types of boards
should be evenly configured among subracks, services should be evenly deployed, and the userplane capacity should be similar.
For example,
if there are 12 pairs of SPUc boards, 15 DPUe boards, 4 NIUa boards, 3 pairs of Iub GOUe
boards, 2 pairs of Iu GOUe boards, and 6 subracks, based on the preceding configuration
principles, each subrack should be configured with 2 pairs of SPUc boards, 2 or 3 DPUe boards,
1 NIUa boards or no NIUa boards, 1 pair of Iub GOUe boards or no Iub GOUe boards, 1 pair
of Iu GOUe boards or no Iu GOUe boards. The subrack with more DPUe boards should be
configured with more GOUe and NIUa boards. SAUc boards are configured in reserved slots in
MPS. The following table lists a recommended configuration.
Issue 09 (2015-07-27)
Subrac
k
SPUc
(pair)
DPUe
(pcs)
NIUa(pcs)
Iub GOUe
(pair)
Iu GOUe
(pair)
SAUc
(pcs)
MPS
EPS1
EPS2
EPS3
EPS4
EPS5

55
Subrac
k
SPUc
(pair)
DPUe
(pcs)
NIUa(pcs)
Iub GOUe
(pair)
Iu GOUe
(pair)
SAUc
(pcs)
Total
12
15
4.3 BSC6900 GU Product Configurations

The following describes the hardware configuration principles of the BSC6900 GU.
1.
GSM boards and UMTS boards should not be configured in the same subrack.
2.
One to four GSM subracks can be configured. One to five UMTS subracks can be
configured.
3.
The total number of GSM and UMTS subracks should be smaller than or equal to six.
4.
Number of cabinets = ROUNDUP[(Number of GSM subracks + Number of UMTS

subracks)/3]. A maximum of two cabinets (excluding the cabinets housing TC subracks)
can be configured.
5.
When the BM/TC separated configuration mode is used, the MPS must work in GSM mode.
6.
The NIUa board providing the service awareness function can be shared between GSM and
UMTS and be configured both on the GSM and UMTS side.
7.
Zero, one or two SAU boards can be configured in the BSC6900 GU mode.
The preceding principles apply to BSC6900 GU deployment and capacity expansion.

The procedure for configuring a newly deployed BSC6900 GU is as follows:
Step 1 Obtain the GSM and UMTS network parameter values.
Step 2 Perform dimensioning to obtain the GSM and UMTS network requirements respectively.
Step 3 Calculate the UMTS configuration and GSM configuration based on the network requirements.
Step 4 If the capacity required by the GSM configuration and UMTS configuration does not exceed
the BSC6900 GU specifications (that is, the total number of GSM subracks and UMTS subrack
does not exceed six), then configuration calculation is complete. If the total required capacity
exceeds the maximum specifications of one BSC6900 GU or the number of slots required for
the interface boards exceeds the limitation, an extra BSC6900 GU needs to be added.
----End
4.4 Examples of Typical Configurations

4.4.1 BSC6900 GSM Examples of Typical Configurations
The following figure illustrates the typical procedure for configuring a BSC6900 GSM.
Issue 09 (2015-07-27)

56
Step 1 Input requirements.

Operator provides the network requirement which should include the information provided in
the following figure.
An example is given here. The input information is listed in the following table.
Issue 09 (2015-07-27)
Network Parameter
Value
TRX QTY
1024
HR Ratio
50%
A Erl: Um Erl
80%
Gos in Um interface
0.02
Gos in A interface
0.001
GPRS Active Sub
100,000
Static PDCH per Cell
Dynamic PDCH per Cell
Built-in PCU
yes
57
Network Parameter
Value
BM/TC model (Separated or Combined)
Separated
Whether to support GPS in BSC
No
Whether to support TC POOL (If TC POOL, Input the quantity of

needed CIC)
No
Step 2 Dimension.
Dimensioning will be carried out from three dimensions, as shown in the following figure.
Item
Name
Specification
TRX support capability
A1
Abis E1 quantity
A2
A CIC quantity
A3
IWF quantity
A4
BHCA
A5
Gb
A6
Step 3 Obtain the network capacity requirement to calculate the hardware requirement.
Issue 09 (2015-07-27)
Item
Name
Configuration Before
the Capacity
Expansion
Subracks (MPS, EPS)
B1
Data Processing Units (DPUf)
B2

58
Item
Name
Configuration Before
the Capacity
Expansion
Data Processing Units (DPUc, DPUg)
B3
Extended Processing Units (XPUb)
B4
Interface boards
B5
Cabinets
B6
----End
4.4.2 BSC6900 UMTS Examples of Typical Configurations

The procedure of typical configuration can be carried out as follow steps.
Step 1 Input requirements.
Operator provides the network requirement which should include the information as listed in
Table 4-19.
Table 4-19 Network specifications
Issue 09 (2015-07-27)
Network Parameter
Value
Total subscribers
800,000
Total NodeBs
600
Total cells
3000
Voice Traffic per CS voice subscriber in BH(Erlang )
0.02
CS voice call duration (sec)
75
Handover times per CS call
CS voice call per subscriber per BH
0.96
PS call per subscriber per BH
Proportion of SHO for CS call
0.3
Handover times per PS call
Mean holding time (MHT) in DCH/H/FACH state per PS call(sec)
52
Mean holding time (MHT) in PCH per PS call(sec)
PS channel switch times per PS call
Cell update times per PS call
Proportion of SHO for PS call
0.3

59
Network Parameter
Value
PS throughput (Including R99 and HSPA, UL+DL) per PS subscriber in BH

(bit/s)
4500
NAS(Attach,Detach, LAU, RAU) and SMS per subscriber per BH
3.6
Iub interface type
IP GE
Iu/Iur interface type
IP GE
Ratio of Iur traffic to Iub traffic
8%
Enable the SA (Service Awareness)
Yes
Whether a Nastar-related SAU board is needed?
Yes
Whether a GPS-support function is needed?
Yes
Step 2 Calculate the capacity requirements.

By dimension procedure, the requirement of operator can be described as following:
l Total Iu-PS throughput requirement (based on the sample input, the value is 3600 Mbit/s) =
Total Subscribers x PS throughput (including R99 and HSPA, UL+DL) per PS subscriber in
BH (bit/s) = 800,000 x 4500 bit/s= 3600 Mbit/s
l Total Iu-CS Erlang requirement (based on the sample input, the value is 16,000 Erlang) =
Total Subscribers x Voice Traffic per CS voice subscriber in BH (Erlang) = 800,000 x 0.02
= 16000
l Total Iu-PS TEID requirement (based on the sample input, the value is 23,111) = Total
Subscribers x [Mean holding time (MHT) in DCH/H/FACH state per PS call (sec) + Mean
holding time (MHT) in PCH per PS call (sec)] x PS call per subscriber per BH/3600 = 800000
x (52 + 0) x 2/3600 = 23,111
l Iu-PS session setup/release times requirement (based on the sample input, the value is 1778
times per second) = Total Subscribers x [PS call per subscriber per BH x (1 + PS channel
switch times per PS call x 0.5 + Cell update times per PS call x 0.5)]/3600 = 800,000 x [2 x
(1 + 3 x 0.5 + 3 x 0.5)]/3600 = 1778
l Total Iub PS throughput requirement(based on sample input, the value is 4680 Mbit/s) =
Total Subscribers x PS throughput (Including R99 and HSPA, UL+DL) per PS subscriber in
BH (bps) x (1 + Proportion of SHO for PS call) = 800,000 x 4500 x (1 + 0.3) bit/s = 4680
Mbit/s
l Total Iub CS Erlang requirement (based on sample input, the value is 20,800 Erl) = Total
Subscribers x Voice Traffic per CS voice subscriber in BH (Erlang) x (1 + Proportion of
SHO for CS call) = 800,000 x 0.02 x (1 + 0.3) = 20,800
l Total BHCA requirement (based on the sample input, the value is 2,368,000) = Total
Subscribers x (CS voice call per subscriber per BH + PS call per subscriber per BH) = 800,000
x (0.96 + 2) = 2,368,000
l Total NodeB number requirement (based on the sample input, the value is 600) = Total
NodeBs = 600
l Total Cell number requirement (based on the sample input, the value is 3000) = Total Cells=
3000
Issue 09 (2015-07-27)

60
l Total Active users requirement (based on sample input, the value is 39,111) = Total
Subscribers x [Mean holding time (MHT) in DCH/H/FACH state per PS call (sec) x PS call
per subscriber per BH/3600 + Voice Traffic per CS voice subscriber in BH (Erlang)] =
800000 x (52 x 2/3600 + 0.02) = 39,111
l Total Iub CID/UDP requirement(based on the sample input, the value is 124,800) = Total
Subscribers x {Mean holding time (MHT) in DCH/H/FACH state per PS call(sec) x PS call
per subscriber per BH/3600 x [1 + 2 x (1+Proportion of SHO for PS call)] + Voice Traffic
per CS voice subscriber in BH (Erlang) x 2 x (1 + Proportion of SHO for CS call)} = 800000
x {52 x 2/3600 x [1 + 2 x (1 + 0.3)] + 0.02 x 2 x (1 + 0.3)} = 124,800
Total Iub Session setup/release times requirement (based on the sample input, the value is
10,951 times/s) = Total Subscribers x [PS call per subscriber per BH x (3 + Handover times
per PS call x 2 + PS channel switch times per PS call x 1 + Cell update times per PS call x
0) + CS voice call per subscriber per BH x (2 + Handover times per CS call x 2)]/3600 =
800000 x [2 x (3 + 5 x 2 + 3 x 1) + 0.96 x (2 + 8 x 2)]/3600 = 10,951
l Under this traffic model, the BHCA supported by each SPUc only board is 114,578:
CP Load per subscriber (unit: CPU usage) = [CS voice call per subscriber per BH x (W1 +
Handover times per CS call x W2) + PS call per subscriber per BH x (w3 + PS channel switch
times per PS call x w7 + Cell update times per PS call x w8 + Handover times per PS call x
w6) + NAS (Attach, Detach, LAU, RAU) and SMS per subscriber per BH x w9]/3600 =
44.6%/3600 = 0.0124%
Subscriber number supported by each SPUc board = (70%-10%) x 8/CP Load per subscriber
= (70% - 10%) x 8/0.0124% = 38709
BHCA capacity supported by each SPUc board = Subscriber number supported by one SPUc
board x (CS voice call per subscriber per BH + PS call per subscriber per BH) = 38709 x
(0.96 + 2) = 114578.
l Under this traffic model, theactual PS throughput capacity supported by each DPUe board
is 470 Mbit/s.
PS RAB mean data rate (UL+DL) (kbit/s) = [PS throughput (Including R99 and HSPA, UL
+DL) per PS subscriber in BH (bit/s) x 3600/1000]/[PS call per subscriber per BH x Mean
holding time (MHT) in DCH/H/FACH state per PS call (sec)]= 4,500 x 3600/1000/(2 x 52)
= 155.8
155.8 kbit/ ranges in [128, 196], PS Throughput Capacity per DPUe(Mbit/s) = 430 + (PS
RAB Mean data rate - 128) x 1.47 =430 + (155.8 - 128) x 1.47 = 470 Mbit/s.
Step 3 Configure hardware and hardware capacity licenses. (HW69 R16 boards are used.)
1.
Issue 09 (2015-07-27)
Calculate the number of required DPUe boards and hardware capacity licenses.
Item
Description
Calculation of the Board Quantity
Iub PS
throughput
PS throughput over the

Iub interface
a' = Total Iub PS throughput requirement/

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

interface
b' = Total Iub CS Erlang requirement /Real

PS throughput(Mbit/s) supported by each
DPUe board = 20800/3350 = 6.21

61
Item
Description
Active users
Number of active users

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

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

of cells supported by each DPUe board =
3000/300 = 10
DPUe boards work in N+1 board redundancy Mode.

N_ DPUe = ROUNDUP[Max(a' + b', n', c')] + 1 = ROUNDUP[Max(9.95+6.21, 10, 6.65 )]
+ 1 = 18.
Calculation for hardware license:
Number of DPUes can be used for PS Throughput * 335Mbps(PS throughput capacity
contains in each DPUe board) = (18-6.21)*335Mbps = 3950 Mbps< Total Iub PS
throughput requirement(4680Mbps).
Therefore, hardware capacity licenses (165 Mbit/s) need to be configured.
N_165 = Min{N_ DPUe,ROUNDUP[(4680 - 3950)/165]} = 5.
3950+5*165 > 4680
Therefore, hardware capacity licenses (300 Mbit/s) are not required.
2.
Calculate the number of required SPUb(SPUc) boards.

Item
Description
BHCA
requirement
BHCA required by
the network
Calculate the BHCA capacity of SPUb(SPUc)

board in this traffic model.
b' = Total BHCA requirement / BHCA capacity
supported by SPUb(SPUc) board =
2368000/114582 = 20.67
Issue 09 (2015-07-27)
Active users
Number of active
users supported on
the control plane
n' =Total Active users requirement / Number of

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

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

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

cells supported by each pair of SPUb(SPUc)
boards = 3000/600 = 5

62
SPUb(SPUc) boards are configured in active/standby mode.

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

Intelligence Throughput License).
NIU boards are configured in load sharing mode by using a resource pool, and should be
configured and N+1 redundancy.
N_NIUa (pcs) = ROUNDUP(Total Iub PS Throughput requirement/PS throughput (Mbit/
s) supported by each NIUa board) + 1 = ROUNDUP(4680 / 3200, 0 ) + 1 = 3.
N_QM1SNIU50M00 = ROUNDUP[(Total Iub PS Throughput requirement - the PS
Throughput capacity contained in NIUa board)/50(Mbit/s)]ROUNDUP[(4680 50)/50] =
93.
If the corresponding optional feature is not configured, N_NIUa=0.
4.
Calculate the number of GOUc(GOUe) boards for the Iub interface.

Interfac
e
Item
Capacity
Requirement
s
Calculation of the Board

Quantity
Iub
Iub transmission
type
GE Optical(IP)
Iub PS
throughput
ba = 4680
Mbps.
ba' = Total Iub PS throughput

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

requirement /Erlang supported by
each GOUc(GOUe) board =
20,800/18,000 = 1.16
NodeB number
bn = 600
bn' = Total NodeB quantity

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

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

requirement /Iub UDP number
supported by each GOUc(GOUe)
board =124800/129000 = 0.97
Assuming GOUc(GOUe) boards are configured in active/standby mode,

N_IUB_GOUc (pair) = ROUNDUP[Max(ba' + bb', bn', an')] = ROUNDUP[Max(1.8 +
1.16, 1.2, 0.97)] = 3
5.
Issue 09 (2015-07-27)
Calculate the number of GOUc(GOUe) boards to be configured for the Iu/Iur interface.

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

requirement / PS throughput (Mbit/s)
supported by the GOUc(GOUe) in IuPS interface = 3600/3200 = 1.13
IuPS on-line
users
pu = 23111
pu' = Total Iu-PS on-line users/Iu-PS

TEID supported by GOUc(GOUe)
=23,111/200,000 = 0.12
Iu-PS session setup and release
ps = 1778
ps' = ps/ Board specification =

1778/5000 = 0.36
Iu-PS
Calculation of the Board

Quantity
cb' = Total IuCS Erlang requirement/

Traffic (Erl) supported by each GOUc
(GOUe) board = 16,000/ 18,000 =
0.89
Assuming the PS and CS Iu interfaces and Iur interface are configured on the same GOUc
(GOUe) board, and in active/standby mode,
N_IUIUR_GOUc (pair) = ROUNDUP[Max(pb' + cb', ps', pu') + (pb' + cb')*8%] =
ROUNDUP[Max(1.13 + 0.89, 0.36, 0.12) + (1.13 + 0.89)*8%] = 3
N_GOUc (pair)= N_IUB_ GOUc + N_IUIUR_GOUc = 3+3 = 6.
6.
Configure the SAU board.

Reserve a pair of slots for the SAU board. The default number of SAU board is 1 for EBC.
If a customer has purchased the OSS feature such as Nastar/SON and the SAU boards,
instruct the customer configure one or two SAU board (N_SAU, the number of SAU is
decided by OSS according to the configured OSS features).
7.
Configure the GCG board.

1 pair of GCGa(GCGb) boards.
8.
Calculate the number of EPSs to be configured (QM1P00UEPS01).

Number of EPSs = ROUNDUP[(N_SPU(23*2) + N_DPUe(18) + N_Iub_GOUc(6*2) +
N_IUIUR_GOUc(3*2) + N_NIUa(3) - 20) /26 ] = 3
Slots number of MPS besides fixed slots: 20. (28-2OMU-2GCU-2SCU-2SAU)
Slots number of EPS besides fixed slots: 26. (28 - 2SCU).
9.
Issue 09 (2015-07-27)
Calculate the number of required WP1B4PBCBN00s (Cabinets).

64
Number of cabinets = ROUNDUP((Number of MPSs + Number of EPSs)/3) = ROUNDUP

(4/3) = 1
The following table lists the configurations of the BSC6900 UMTS that adopts the HW69 R15
hardware.
Ite
m
Name
Abbreviation
Model
Quan
tity
Cabinet
WP1B4PBCBN00
MPS
QM1P00UMPS01
EPS
QM1P00UEPS01
Clock board (pair)
GCG
WP1D000GCG01
Data Processing Unit
DPUe
WP1D000DPU03
18
Hardware Capacity License (165

Mbit/s)
QM1SHW165M00
Hardware Capacity License (300

Mbit/s)
QM1SHW300M00
Signaling Processing Unit (pair)
SPUb
QM1M000SPU01
21
Network Intelligence Unit
NIUa
WP1D000NIU00
10
Network Intelligence Throughput

License
QM1SNIU50M00
93
11
Iub Interface Board (Pair)
GOUc
WP1D000GOU01
12
Iu Interface Board (Pair)
GOUc
WP1D000GOU01
13
Signaling Access Unit
SAUc
None
1,2
To avoid the volume of inter-subrack data flows exceeding the limitation, service boards must
be evenly deployed among subracks accordingly. The following figure shows a recommended
configuration.
Issue 09 (2015-07-27)

65
----End
Issue 09 (2015-07-27)

66
5 Expansion and Upgrade Configurations
Expansion and Upgrade Configurations
About This Chapter

5.1 BSC6900 GSM Hardware Expansion and Upgrade Configurations Example
5.2 BSC6900 UMTS Hardware Expansion and Upgrade Configurations
5.3 BSC6900 GU Hardware Expansion and Upgrade Configurations
Issue 09 (2015-07-27)

67
5.1 BSC6900 GSM Hardware Expansion and Upgrade

Configurations Example
Capacity expansion can be performed through the following methods:
1.
Improving the service processing capability of the system through hardware expansion.
2.
Improving the service processing capability of the system by configuring hardware capacity
licenses.
The two methods can be adopted separately or together based on the traffic model and traffic
requirements of the network.
5.1.1 Hardware Expansion and Upgrade Configurations

Two types of board can be used to support the same functions or transmission mode. For example,
to implement TDM over STM-1 on the Abis interface, OIUb and POUc boards can be installed.
This is known as mixed insertion of boards. The following table lists the HW60 R8, HW69 R11,
HW69 R13, and HW69 R15 boards.
Hardware
Version
Board
HW60 R8
DPUc, DPUd, XPUa, SCUa, TNUa, GCUa, OMUb, EIUa, FG2a, GOUa,
OIUa, PEUa
HW69 R11
DPUc, DPUd, XPUb, SCUa, TNUa, GCUa, GCGa, OMUa,EIUa, FG2c,

GOUc, OIUa, PEUa, POUc
HW69 R13
DPUf, DPUg, XPUb, SCUb, TNUa, GCUa, GCGa,OMUc,EIUa, FG2c,

GOUc, PEUa, POUc, SAUc, NIUa
HW69 R15
DPUf, DPUg, XPUc, SCUb, TNUb, GCUb, GCGb, OMUc, EIUb, OIUb,
FG2c, GOUe, PEUc, POUc, SAUc, NIUa
NOTE
TNUb was supported at V900R15SPC560.
In HW69 R15, XPUb is replaced by XPUc,EIUa is replaced by EIUb, OIUa is replaced by OIUb,
and PEUa is replaced by PEUc, GOUc is replaced by GOUe,but the board specifications are not
changed. Therefore, the configuration principle and capacity expansion principle of XPUc,EIUb,
OIUb, PEUc,GOUe remain the same as XPUb,EIUa, OIUa, PEUa, GOUc.
l
Issue 09 (2015-07-27)
BM Configuration

68
Model
Name
BM/TC Combined Configuration Mode
WP1D000FG201
FG2c
1. Number of WP1D000FG201s as A interface

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

boards = 2 x ROUNDUP ((MAX (ROUNDUP
(AbisIPFEGENo/GEPortPerFG2c, 0) x
GEPortPerFG2c Number of FG2a boards
supported by the Abis interface/2 x
GEPortPerFG2a)/GEPortPerFG2c,
(TRXNoFEGE Number of FG2a boards
supported by the Abis interface/2 x
TRXNoPerFG2a)/TRXNoPerFG2c), 0)
NOTE
When the Abis interface does not use IP transmission and
Um interface soft synchronization is not enabled between
different BSCs, a pair of S4020192 boards is configured
by default.
When the Abis interface uses IP transmission, the Abis
interface boards must be configured. The number of
required Abis interface boards depends on the number of
FE/GE ports and the number of TRXs. In capacity
expansion scenarios, the originally supported TRXs must
be subtracted from the total required TRXs. In addition,
the number of ports supported before capacity expansion
should also be considered.
3. Number of WP1D000FG201s as Gb interface

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

69
Model
Name

4. The number of FG2c boards to be configured is
equal to the total number of all the preceding
boards.
Issue 09 (2015-07-27)

70
Model
Name
WP1D000GOU03
GOUe
1. Number of A interface boards :

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

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

Number of WP1D000GOU01s as Gb interface
boards = 2 x ROUNDUP(MAX(GbIPGEOpticNo/
Issue 09 (2015-07-27)

71
Model
Name

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

number of all the preceding boards.
Issue 09 (2015-07-27)

72
Model
Name
WP1D000POU01
POUc
1. Number of WP1D000POU01s as A interface

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

boards (IP transmission) = 2 x ROUNDUP(MAX
(MaxACICPerBSCIP/ACICPerPOUcIP), 0)
NOTE
The quantity depends on the number of CIC circuits on
the A interface.
5. Number of WP1D000POU01s as Abis interface

boards (IP transmission) = 2 x ROUNDUP(MAX
(SiteNoIPSTM1/STM1PortPerPOUc/63,
AbisIPSTM1No/STM1PortPerPOUc,
TRXNoIPSTM1/TRXPerPOUcIP), 0)
NOTE
When IP transmission is used on the Abis interface, this
board should be configured. The configuration quantity
depends on the number of base stations, the number of
ports, and the number of TRXs. An E1 port must be
configured for each base station by default.
6. Number of WP1D000GOU01s as Gb interface

boards = 2 x ROUNDUP(MAX(GbFRSTM1No/
STM1PortPerPOUc, GbFRTputPerBSC/
GbTputPerPOUcFR/1024), 0)
NOTE
When a built-in PCU is used, Gb interface boards should
be configured. The configuration quantity depends on the
number of ports and the traffic on the Gb interface.
7. The quantity is equal to the total number of all the

preceding boards.
Issue 09 (2015-07-27)

73
Model
Name

NOTE
In scenarios of capacity expansion, the configuration quantity
equals the calculated number minus the OIUa and OIUb
board capacity specifications on the Ater and Abis interfaces.
Issue 09 (2015-07-27)

74
Model
Name
WP1D000EIU01
EIUb
The EIUb has the same capacity with the EIUa, so that
the EIUb inherits the configuration and capacity
expansion principles of the EIUa.
1. Number of Ater interface boards = 2 x ROUNDUP
(MaxAterCICPerBSC/AterCICPerEIUa, 0)
NOTE
the Ater interface. In the new site deployment scenario,
MaxAterCICPerBSC indicates the required number of
CIC circuits on the Ater interface.
In the capacity expansion scenario, MaxAterCICPerBSC
indicates the additional number of CIC circuits on the
Ater interface.
2. Number of Abis interface boards = 2 x ROUNDUP

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

(MAX (PbTDME1No/E1PortPerEIUa, 0))
NOTE
The Pb interface board in configured only when the PCU
is installed externally. The number of Pb interface boards
depends on the number of ports.In the capacity expansion
scenario, PbTDME1No indicates the additional number
of ports.
4. The number of EIUbc boards to be configured is

boards.
Issue 09 (2015-07-27)

75
Model
Name
WP1D000OIU01
OIUb
The OIUb has the same capacity with the OIUa, so that
the OIUb inherits the configuration and capacity
expansion principles of the OIUa.
(MaxAterCICPerBSC/AterCICPerOIUa, 0)
NOTE
the Ater interface.In the capacity expansion scenario,
MaxAterCICPerBSC indicates the additional number of
2. Number of Abis interface boards = 2 x ROUNDUP

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

(MAX (PbTDME1No/E1PortPerOIUa, 0))
In the capacity expansion scenario,
PbTDMSTM1No indicates the additional number
of ports.
4. The number of OIUb boards to be configured is
equal to the total number of all the preceding boards
NOTE
In RAN13.0 and later versions, all OIUa boards are replaced
by POUc boards. So OIUb boards are replaced by POUc
boards too. POUc is recommend.
Issue 09 (2015-07-27)

76
Model
Name
WP1D000PEU01
PEUc
The PEUc has the same capacity with the PEUa, so that
the PEUa inherits the configuration and capacity
expansion principles of the PEUa.
1. Number of A interface boards = 2 x ROUNDUP
(MaxACICPerBSCIP/ACICperPEUaIP,0)
NOTE
The board quantity depends on the number of CIC
circuits. In the capacity expansion scenario,
MaxACICPerBSCIP indicates the additional number of
2. Number of Abis interface boards (IP) = 2 x

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

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

boards.
Issue 09 (2015-07-27)

77
Model
Name
WP1D000XPU03
XPUc
1. If the number of eGBTS TRX is not enlarged (Only

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

Number of required XPUc = 2 x ROUNDUP(MAX
((Number of TRXs after capacity expansion Number of TRXs for XPUa boards)/640, (Number
of BHCA enlarged - Number of BHCA for XPUa
boards) x Number of GBTS TRX enlarged/Number
of TRX enlarged /1050000 + (Number of BHCA
enlarged - Number of BHCA for XPUa boards) x
Number of eGBTS TRX enlarged/Number of TRX
enlarged/950000, (Number of ERL enlarged Number of ERL for XPUa boards)/3900), 0)
Issue 09 (2015-07-27)

78
Model
Name

NOTE
Number of TRXs for XPUa boards: The maximum
number of TRXs is determined based on the number of
of pairs of XPUa boards and the number of TRXs is as
follows:
1: 270; 2: 630; 3: 990; 4: 1350; 5: 1710; 6: 2070.
Number of BHCA for XPUa boards: The maximum
number of BHCA is determined based on the number of
of pairs of XPUa boards and the number of BHCA is as
follows:
1: 492000 x Number of GBTS TRX enlarged/Number of
TRX enlarged + 492000 x Number of eGBTS TRX
enlarged/Number of TRX enlarged
2: 1148000 x Number of GBTS TRX enlarged/Number
of TRX enlarged + 1148000 x Number of eGBTS TRX
Number of ERL for XPUs: The maximum number of
BHCA is determined based on the number of pairs of
XPU boards. The mapping between the number of pairs
of XPU boards and the number of BHCA is as follows:
1: 1720; 2: 4020; 3: 6320; 4: 8620; 5: 10920; 6: 13220.
If "Number of required WP1D000XPU03s" <= 0,

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

identification is required. If intelligent service
identification is enabled, the number of required
WP1D000NIU00s is one.

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

IP hybrid transmission in A over IP)
On the BM side:
The number of DPUf to be configured depends on
the number of CIC circuits that require IWF
conversion between TDM and IP and between IP
and IP.
Number of DPUf = RoundUp( MAXIWFPerBSCTDMIP / IWFNoPerDPUfTDMIP + MAX
(MAXIWFPerBSCIPIP - MAXIWFPerBSCTDMIP, 0) / IWFNoPerDPUfIPIP,0)+1
On the TC side:
Number of DPUf = RoundUp(MaxACICPerBSCTDM/TCNoPerDPUf) +1
2. In BM/TC combined configuration mode (or TDM/
IP hybrid transmission in A over IP)
The DPUf providing the TC function can support
the IWF function of the same specifications as
DPUf.
Extra DPUf should be configured to provide the
IWF function for the A-interface CIC circuits in A
over IP transmission.
Number of DPUf = RoundUp(MaxACICPerBSCTDM/ TCNoPerDPUf,0) + RoundUp
( MAXIWFPerBSCTDMIP / IWFNoPerDPUfTDMIP + MAX (MAXIWFPerBSCIPIP MAXIWFPerBSCTDMIP, 0) /
IWFNoPerDPUfIPIP,0)+1
3. A over IP:
The number of DPUf to be configured depends on
the number of CIC circuits that require IWF
conversion between TDM and IP and between IP
and IP.
Number of DPUf = RoundUp
(MAXIWFPerBSCTDMIP / IWFNoPerDPUfTDMIP + MAX (MAXIWFPerBSCIPIP MAXIWFPerBSCTDMIP, 0) /
IWFNoPerDPUfIPIP,0) +1
4. IP transmission on all interfaces of the BSC6900
GSM
Number of DPUf = RoundUp
(MaxACICPerBSCIP / IWFNoPerDPUfIPIP,0) +1
Issue 09 (2015-07-27)

80
Model
Name
WP1D000DPU06
DPUg
Number of required WP1D000DPU06s = ROUNDUP

(MaxPDCHPerBSC/PDCHNoPerDPUg, 0) + 1
Number of DPUd boards
NOTE
This module must be configured when the built-in PCU is
used. The configuration quantity depends on the maximum
number of PDCHs required by the BSC. WP1D000DPU06
works in N+1 backup mode.
The DPUg and DPUd boards have identical

specifications.
GMIPEPRACK00
GEPS
1. Total number of interface boards = EIUa + EIUb +

OIUa + OIUb + PEUa + PEUc + POUc + FG2a +
GOUa + FG2c + GOUc
2. Total number of user plane boards = XPUa + DPUc
+ DPUd + DPUf + DPUg + XPUb
Number of processing subracks = ROUNDUP(MAX
(Total number of interface boards 10/14, (Total
number of interface boards + Total number of user
plane boards 18)/24, 0))
QM1B0PBCBN00
Cabine
t
Number of cabinets = (Number of GMPSs + Number

of GEPSs)/3
Multiple transmission modes, such as TDM, HDLC, and IP, can be used on the Abis
interface within one BSC.
l
TC Configuration
The following table describes the configurations of each module.
Issue 09 (2015-07-27)

81
Model
Name
WP1D000EI
U01
EIUb
The EIUb has the same capacity with the EIUa, so that
the EIUb inherits the configuration and capacity
expansion principles of the EIUa.
1. Number of Ar interface boards = 2 x ROUNDUP
(MaxACICPerBSCTDM / ACICPerEIUa, 0)
NOTE
The quantity depends on the number of CIC circuits on the
A interface. In the capacity expansion scenario,
MaxACICPerBSCTDM indicates the additional number of
CIC circuits on the A interface.

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

to the total number of all the preceding boards.
WP1D000OI
U01
OIUb
The OIUb has the same capacity with the OIUa, so that
the OIUb inherits the configuration and capacity
expansion principles of the OIUa.
1. Number of Ar interface boards = 2 x ROUNDUP
(MaxACICPerBSCTDM / ACICPerOIUa, 0)
NOTE
A interface. In the capacity expansion scenario,
MaxACICPerBSCTDM indicates the additional number of
CIC circuits on the A interface.

(MaxAterCICPerBSC/AterCICPerOIUa, 0)
NOTE
Ater interface. In the capacity expansion scenario,
MaxAterCICPerBSC indicates the additional number of
3. The number of OIUb boards to be configured is equal

to the total number of all the preceding boards
NOTE
In RAN13.0 and later versions, all OIUa boards are replaced by
POUc boards.
Issue 09 (2015-07-27)

82
Model
Name
WP1D000PE
U01
PEUc
The PEUc has the same capacity with the PEUa, so that
the PEUa inherits the configuration and capacity
expansion principles of the PEUa.
Number of Ar interface boards = 2 x ROUNDUP
(MaxACICPerBSCTDM / ACICIperPEUcIPACICPerEIUa, 0)
NOTE
The quantity depends on the number of CIC circuits on the A
interface. In the capacity expansion scenario,
MaxACICPerBSCTDM indicates the additional number of CIC
circuits on the A interface.
WP1D000PO
U01
POUc
1. Number of WP1D000POU01s as A interface boards

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

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

GEPSs)/3

83
5.1.2 Hardware Capacity License Expansion

N/A
5.1.3 Examples of Hardware Expansion

l
Total Replacement
An operator may want to increase equipment integration and achieve a larger capacity with
existing cabinets and subracks. In this case, a total replacement is recommended.
In a total replacement, the capacity is considered first. The Unistar quotation template is
used to work out a BSC equipment list based on the specifications of the new hardware
version. The boards required for the capacity expansion are determined through a
comparison with existing boards that can be reused. Boards that cannot be reused need to
be removed.
The procedure for a total replacement is as follows:
Step 1 Fill in the Unistar calculation table and calculate the configuration required after the capacity
expansion.
Step 2 Record the board and equipment configurations before the capacity expansion.
Step 3 The components required in the capacity expansion are the components after the capacity
expansion minus those before the capacity expansion.
Item
Name
Configuration
Before the
Capacity
Expansion
Configuration
After the
Capacity
Expansion
Number of
Components
to Be Added
Subracks (MPS, EPS)
A1
B1
B1 A1
Data Processing Units

(DPUf)
A2
B2
B2 A2
Data Processing Units

(DPUc, DPUg)
A3
B3
B3 A3
Extended Processing
Units (XPUb)
A4
B4
B4 A4
Interface boards
A5
B5
B5 A5
Cabinets
A6
B6
B6 A6
In this scenario, different versions require different points for attention.

In a capacity expansion for HW69 R11, XPUa, FG2a, and GOUa boards cannot be reused. If IP
interface boards are used only for the Gb interface and TDM networking is used on the entire
network, FG2a and GOUa boards over the Gb interface can be regarded as FG2c boards. FG2a,
GOUa, and FG2c boards have no difference in terms of supporting small-capacity Gb interfaces.
In a capacity expansion for HW69 R13, DPUc, DPUd, XPUa, FG2a, and OIUa boards cannot
be reused. If IP interface boards are used only for the Gb interface and TDM networking is used
Issue 09 (2015-07-27)

84
on the entire network, FG2a and GOUa boards over the Gb interface can be regarded as FG2c
boards. FG2a, GOUa, and FG2c boards have no difference in terms of supporting small-capacity
Gb interfaces.
----End
l
Incremental Algorithm
If an operator wants to keep the original equipment without large-scale modifications to
the legacy network, new boards are used only for newly added sites and carriers. If the new
quotation template does not support mixed insertion of boards and the frontline personnel
want to simplify operations, use the original quotation template and the incremental
algorithm.
The core idea is to reuse as much legacy equipment as possible.
The purpose of mixed insertion is to use boards of different specifications in the same
logical or physical interface.
For example:
OIUa/OIUb and POUc boards can provide TDM-based optical ports on the A interface,
but they have different specifications.
FG2a and FG2c boards can be used for Abis over IP over FE/GE transmission, but they
have different specifications.
For mixed insertion of boards, the old boards used on each interface before capacity
expansion must be calculated.
The procedure for 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, if the traffic volume on the Gb interface is not higher
than 64 Mbit/s in FR transmission mode or 128 Mbit/s in IP transmission mode, set the capacity
increase on the Gb interface to 0.
Issue 09 (2015-07-27)

85
Item
Name
Configuration
Required After
the Capacity
Expansion
Maximum Support
Capability Before
the Capacity
Expansion
Increased
Support
Capability
Required by
the Capacity
Expansion
TRX support
capability
A1
B1
B1 A1
Abis E1 quantity
A2
B2
B2 A2
A CIC quantity
A3
B3
B3 A3
IWF quantity
A4
B4
B4 A4
BHCA
A5
B5
B5 A5
Gb
A6
A6
B6 A6
Step 4 Determine the boards required by the capacity expansion.

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

Configurations
Capacity expansion can be performed through the following methods:
1.
Improving the service processing capability of the system through hardware expansion.
2.
Improving the service processing capability of the system by configuring hardware capacity
licenses.
The two methods can be adopted separately or together based on the traffic model and traffic
requirements of the network. The capacity expansion must match the description in section 4.2.6
Principles for Board Configurations
5.2.1 Hardware Expansion and Upgrade Configurations

The following table lists the HW69 R11, HW69 R13, and HW69 R15 boards.
Issue 09 (2015-07-27)
Hardware Version
Board
HW69 R11
OMUa, SCUa, GCGa, GCUa, DPUe, SPUb, AEUa, PEUa, AOUc,

FG2c, GOUc, OIUa, POUc, UOIa, UOIc
86
Hardware Version
Board
HW69 R13
OMUc, SCUb, GCGa, GCUa, DPUe, SPUb, AEUa, PEUa,

AOUc, FG2c, GOUc, POUc, UOIc, SAUc, NIUa
HW69 R15
OMUc, SAUc, SCUb, GCGa, GCGb, GCUa, GCUb, DPUe,

SPUb, SPUc, NIUa, AEUa, PEUc, AOUc, FG2c,
GOUc, GOUe, OIUb, POUc, UOIc
The following table lists the number of components to be added to the BSC6900 UMTS that
adopts the HW69 R15 hardware for capacity expansion.
Item
Name
Configuration
Before the
Capacity
Expansion
Configuration
After the
Capacity
Expansion
Number of
Components
to Be Added
Cabinets
A1
B1
B1 A1
MPS
A2
B2
B2 A2
EPS
A3
B3
B3 A3
Clock board
A4
B4
B4 A4
Data Processing Unit
A5
B5
B5 A5
Signaling processing
unit
A6
B6
B6 A6
Interface board
A7
B7
B7 A7
NOTE
A1 through A7 and B1 through B7 indicate the number of components.
5.2.2 Hardware Capacity License Expansion

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

Assume that the network configurations before capacity expansion are 6700 Erlang, 670 Mbit/
s (based on the traffic type UL/DL64/384 kbit/s), 248,000 BHCA (assume that the traffic model
is the balanced traffic model), 360 NodeBs, and 1200 cells. All-IP transmission (optical GE) is
adopted.
Issue 09 (2015-07-27)

87
Assume that the network configurations after capacity expansion are 13,400 Erlang, 1340 Mbit/
s (based on the traffic type UL/DL64/384 kbit/s), 496,000 BHCA (assume that the traffic model
is the balanced traffic model), 720 NodeBs, and 2400 Cells.
The following table lists the hardware configurations before and after capacity expansion. The
numbers of hardware components to be added are calculated according to the procedure
described in section 4.2 BSC6900 UMTS Product Configurations.
Table 5-1 Capacity expansion from configuration 1 to configuration 2
Configuration
Number
of
Cabinets
Number
of
Subracks
Number
of DPUe
Boards
Number
of SPUc
Boards
Number
of GOUc
Boards
Configuration 1
(before capacity
expansion)
Configuration 2
(after capacity
expansion)
Number of
components to be
added
The slot configurations are as follows:

NOTE
It is recommended that boards be as evenly as possible distributed in every subrack, following the related
configuration principles.
Issue 09 (2015-07-27)

88
5.2.4 Examples of Hardware Capacity License Expansion

Assume that the network configurations before capacity expansion are 670 Mbit/s (based on the
traffic type UL/DL64/384 kbit/s), 248,000 BHCA (assume that the traffic model is the same as
the balanced traffic model), 180 NodeBs, and 600 cells.
Assume that the network configurations after capacity expansion are 1,150 Mbit/s (based on the
traffic type UL/DL64/384 kbit/s) (assume that the capacity needs to be expanded because the
data throughput in the network increases sharply and that other requirements of the network
remain unchanged).
On the user plane, two DPUe boards are configured. The maximum capacity can reach 1600
Mbit/s by configuring hardware capacity licenses. Therefore, the network requirements can be
met by only configuring hardware capacity licenses.
Number of hardware capacity licenses (165 Mbit/s) N_165 = Min(2, ROUNDUP((1150 Mbit/
s 670 Mbit/s)/165)) = 2
670 Mbit/s + 2 x 165 Mbit/s = 1000 Mbit/s < 1150 Mbit/s
Therefore, hardware capacity licenses (300 Mbit/s) need to be configured.
Number of hardware capacity licenses (300 Mbit/s) = Min(N_165, ROUNDUP((1150 Mbit/s
335 Mbit/s x 2 165 Mbit/s x 2)/300)) = 1
The user plane capacity provided by the system after capacity expansion is: 670 + 165 x 2 + 300
x 1 = 1300 Mbit/s > 1150 Mbit/s. This indicates that the user plane capacity can meet the service
requirements.
During capacity expansion, two hardware capacity licenses (165 Mbit/s) and one hardware
capacity license (300 Mbit/s) are added. The following figures show the slot configurations
before and after capacity expansion with hardware unchanged.
Table 5-2 Capacity expansion from configuration 1 to configuration 2
Issue 09 (2015-07-27)
Configuration
Number of
QM1SHW165M00s
Number of
QM1SHW300M00s
Configuration 1 (before capacity

expansion)
Configuration 2 (after capacity

expansion)

89
Configuration
Number of
QM1SHW165M00s
Number of
QM1SHW300M00s
Number of capacity licenses to be

added
5.3 BSC6900 GU Hardware Expansion and Upgrade

Configurations
BSC6900 GU new deployment and capacity expansion comply with the following configuration
principles:
1.
If the BSC and RNC use different subracks, it is recommended that the RNC subrack serve
as the basic subrack.
2.
The BSC is configured with one to four subracks, whereas the RNC is configured with one
to five subracks.
3.
The total number of BSC and RNC subracks cannot exceed six.
4.
A maximum of two cabinets can be configured, excluding the subracks accommodating

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

90
6 Appendix
Appendix
About This Chapter

6.1 Hardware Version
6.2 Traffic Model
6.3 GSM Ater RSL Configuration Calculation Tool
6.4 Suggestions for GSM Lb Interface Configuration
6.5 GSM Hardware Specifications
6.6 UMTS Hardware Specifications
Issue 09 (2015-07-27)

91
6 Appendix
6.1 Hardware Version

The following table lists the boards of HW69 R15.
HW6
9 R15
OMUc, SAUc, SCUb, GCGa, GCGb, GCUa, GCUb, DPUe, SPUb, SPUc, NIUa,
AEUa, PEUc, AOUc, FG2c, GOUc, GOUe, EIUb, OIUb, POUc, UOIc
Hardware
Version
Model
Description
HW69 R15
hardware
QM1P00UMPS01
QM1P00UEPS01
QM1M000SPU00/
Signal Processing Unit
QM1M000SPU03
WP1D000DPU03
Data Processing Unit (335 Mbit/s/3350 Erl)
WP1D000NIU00
WP1D000AEU00
ATM Interface Unit (32 E1)
WP1D000PEU01
IP Interface Unit (32 E1)
WP1D000AOU01
ATM Interface Unit (4 STM-1, Channelized)
WP1D000POU01
IP Interface Unit (4 STM-1, Channelized)
WP1D000UOI01
ATM Interface Unit (8 STM-1,

Unchannelized)
WP1D000GOU01/
IP Interface Unit (4 GE, Optical)
WP1D000GOU03
WP1D000FG201
IP Interface Unit (12 FE/4 GE, Electric)
WP1D000SAU01
Service Aware Unit
WP1D000GCU01/
General Clock Unit
WP1D000GOU02
QW1D000GCG01/
GPS&Clock Processing Unit
QW1D000GCG02
Issue 09 (2015-07-27)
WP1D000DPU05
CS Data Processing Unit (1920CIC/3840

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

92
Hardware
Version
6 Appendix
Model
Description
WP1D000NIU00
WP1D000XPU01
Expansion Processing Unit (640)
WP1D000EIU01
TDM Interface Unit (32 E1/T1)
WP1D000OIU01
TDM Interface Unit (1 STM-1,Channelized)
6.2 Traffic Model

6.2.1 GSM Traffic Model
The BSC BHCA specifications in this document are based on a Huawei GSM traffic model. The
following table lists the key parameters.
Table 6-1 GSM traffic model
Issue 09 (2015-07-27)
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
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

93
6 Appendix
Parameter
Value
Grade of Service (GoS) on A interface
0.001
percent of HR (percent of Um interface resources occupied by HR

voice call)
50%
Uplink TBF Est & Rel / Second/TRX
1.75
Downlink TBD Est & Rel / Second/TRX
0.9
PS Paging / Sub/BH
1.25
6.2.2 UMTS Traffic Model

The BSC6900 UMTS supports the flexible configuration of control plane and user plane data
in different scenarios. In each scenario, the capacity configured for the BSC6900 UMTS depends
on actual traffic models.
There are three traffic models for the BSC6900 UMTS:
1.
Balanced traffic model

This model applies when voice services and data services are balanced in a network.
2.
High-PS traffic model

This model 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.
3.
Traffic model for mart phones

In this model, control plane signaling is frequently exchanged and user plane data is
transmitted mainly through small packets.
The capacity under UMTS BSC6900 typical configurations in the balanced traffic model, highPS traffic model, and smartphones traffic model are described as follows.
1.
Balanced Traffic Model

Table 6-2 Balanced traffic model for the BSC6900 UMTS (per user in busy hours)
Issue 09 (2015-07-27)
Property
Value
Description
Voice Traffic per CS voice

subscriber in BH
20 mE
AMR voice RAB, 0.96BHCA per

subscriber.
CS data traffic per CS data

subscriber in BH
1.5 mE
64/64 kbit/s CS RAB, 0.04 BHCA per

subscriber.
PS throughput (Including
R99 and HSPA, UL+DL)
per PS subscriber in BH
4500 bit/s
2 BHCA per subscriber, UL/DL64 kbit/s/

384 kbit/s
Proportion of soft
handovers
30%
The number of calls(in percent) with 2

hangover legs(others have 1 leg)

94
6 Appendix
Property
Value
Description

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

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

3.6
Including all CN-UE signaling: LA

update, RA update, IMSI attach/detach,
and GPRS attach/detach
Iur traffic
8%
The amount of Iub traffic(in percent) that

is directed to another RNC
The following table lists the capacity of a BSC6900 UMTS in typical configurations. In
this table, the BSC6900 UMTS is configured with HW69 R15 boards and uses the balanced
traffic model.
Table 6-3 Capacity of a BSC6900 UMTS in typical configurations (HW69 R15 boards) of
Balanced traffic model
Subscribers
CS Voice
Service
Capacity
(Erlang)
PS Service
Capacity (Iub
UL+DL)
(Mbit/s)
BHCA
(k)
Active
Users
Online
users
1,760,000
45,738
7920
5300
229,000
869,000
NOTE
l The CS voice service capacity and PS service capacity can reach the maximum at the same time.
l Subscribers means the number of users connected to the network in one busy hour.
l Active user means the number of user in active state simultaneously, active state includes
Cell_DCH and Cell_FACH.
l Online user means the number of user in online state simultaneously, online state includes
Cell_DCH, Cell_FACH, Cell_PCH and Ura_PCH.
2.
High-PS Traffic Model

Table 6-4 High-PS traffic model for the BSC6900 UMTS (per user in busy hours)
Issue 09 (2015-07-27)
Item
Specificati
on
Description
CS voice traffic volume
3 mE
AMR speech service, 0.144 BHCA
CS data traffic volume
0.2 mE
UL 64 kbit/s/DL 64 kbit/s CS data service,

0.0053 BHCA

95
6 Appendix
Item
Specificati
on
Description
PS throughput
43,500 bit/s
UL 64 kbit/s/DL 384 kbit/s, 3 BHCA
Proportion of soft
handovers
30%
Proportion of calls using two channels

simultaneously to all calls

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

(SHO) (times/call)
NAS signaling per

3.6
Including all CN-UE signaling: LA update,

RA update, IMSI attach/detach, and GPRS
attach/detach
Iur traffic
8%
The amount of Iub traffic(in percent) that

is directed to another RNC
The following table lists the capacity of a BSC6900 UMTS in typical configurations. In
this table, the BSC6900 UMTS is configured with HW69 R15 boards and uses the highPS traffic model.
Table 6-5 Capacity of a BSC6900 UMTS in typical configurations (HW69 R15 boards) of
High-PS traffic model
Subscriber
s
CS Voice
Service
Capacity
(Erlang)
PS Service
Capacity (Iub
UL+DL)
(Mbit/s)
BHCA
(k)
Active
Users
Online
Users
925,000
3600
40,200
2900
243,000
567,000
NOTE
l SPUb specifications in High-PS traffic model is 112K BHCA.
l Active user means the number of user in active state simultaneously, active state includes
Cell_DCH and Cell_FACH.
l Online user means the number of user in online state simultaneously, online state includes
Cell_DCH, Cell_FACH, Cell_PCH and Ura_PCH.
3.
Issue 09 (2015-07-27)
Smartphones Traffic Model

96
6 Appendix
Table 6-6 Smartphones traffic model for the BSC6900 UMTS

Item
Specificatio
n
Description
CS voice traffic volume
30mE
AMR speech service, 0.7 CS BHCA per

subscriber
PS throughput
1600 bit/s
8 PS BHCA per subscriber
Proportion of soft
handovers
34%
Proportion of calls using more two radio links

simultaneously to all calls
Handover times per CS

call (SHO) (times/call)
Handover times per PS

call (SHO) (times/call)
Average number of handovers per PS call
PS channel switch times

per PS call
2.3
Including all switch between different

connected RRC states and channels per PS call
NAS signaling per

2.8
Including all CN-UE signaling: LA update, RA

update, IMSI attach/detach, GPRS attach/
detach, and SMS
Iur traffic
8%
The amount of Iub traffic(in percent) that is

directed to another RNC
The following table lists the capacity of a BSC6900 UMTS in typical configurations. In this
table, the BSC6900 UMTS is configured with HW69 R15 boards and uses the traffic model for
smartphones.
Table 6-7 Capacity of a BSC6900 UMTS in typical configurations (HW69 R15 boards)
Issue 09 (2015-07-27)
Subscribers
CS Voice
Service
Capacity
(Erlang)
PS Service
Capacity
(Iub UL
+DL)
(Mbit/s)
BHCA
(k)
Active
Users
Online User
1,440,000
47,000
1860
12,800
230,000
869,000

97
6 Appendix
NOTE
l Active user means the number of user in active state simultaneously, active state includes Cell_DCH
and Cell_FACH.
l Online user means the number of user in online state simultaneously, online state includes Cell_DCH,
Cell_FACH, Cell_PCH and Ura_PCH.
6.3 GSM Ater RSL Configuration Calculation Tool

Ater_RSL_Configuration_Calculation_Tool.xls
6.4 Suggestions for GSM Lb Interface Configuration

The Lb interface bandwidth is determined by the SMLC. The BSC provides transmission and
signaling forwarding. If the Lb interface bandwidth requirement is not specified by the SMLC,
the maximum bandwidth should be configured.
If the BSC is connected to the SMLC by using TDM transmission, then the maximum Lb
interface bandwidth is:
For low-speed SS7 links, the maximum Lb interface bandwidth is:
16 x 64 kbit/s = 1 Mbit/s
For narrowband SS7 signaling links with a single signaling point, the maximum Lb interface
bandwidth is:
16 x 64 kbit/s = 1 Mbit/s
For wideband SS7 signaling links with a single signaling point, the maximum Lb interface
bandwidth consists of eight signaling links, and the total bandwidth should not exceed 4 Mbit/
s. Generally, the configuration is as follows:
2 x 2 Mbit/s = 4 Mbit/s
6.5 GSM Hardware Specifications

6.5.1 Board Specifications
The following table lists the board specifications.
Issue 09 (2015-07-27)
Parameter Name
Meaning
Specificat
ion
Board
TrxPerXPUaWithMPU
TRX support capability of

the XPUa (with the MPU)
270
XPUa

98
6 Appendix
Parameter Name
Meaning
Specificat
ion
Board
BHCAPerXPUaWithMPU
BHCA supported by each

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

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

each pair of ordinary XPUa
boards
360
XPUa
BHCAPerXPUaWithoutMPU

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

pair of ordinary XPUa
boards (not used as a
calculation criterion)
2300
XPUa
TrxPerXPUc

the XPUc
640
XPUc
BHCAPerXPUc

pair of XPUc boards
1,050,000
for GBTS
XPUc:
BHCA
445,000 for
eGBTS
590,000 for
eGBTS
950,000 for
eGBTS
Issue 09 (2015-07-27)
ErlPerXPUc

pair of XPUc boards (not
used as a calculation
criterion)
3900
XPUc:
Erlang
PDCHNoPerDPUd
PDCH support capability of

the DPUd
1024
DPUd
PDCHNoPerDPUg
PDCH support capability of

the DPUg
1024
DPUg
IWFNoPerDPUc
IWF flow processing

capability of the DPUc
3740
DPUc
TCNoPerDPUc
TC processing capability of
the DPUc
960
DPUc

99
Issue 09 (2015-07-27)
6 Appendix
Parameter Name
Meaning
Specificat
ion
Board
IWFNoPerDPUf(TDM*IP)
IWF flow processing

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

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

the POUc
POUc
TRXHRPerPOUcTDM
Number of TRXs supported

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

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

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

over the Ater interface
7168
POUc: TDM
TRXPerPOUcIP

by the POUc over the Abis
interface in IP transmission
mode
2048
POUc: IP
ACICPerPOUcIP

over the A interface in IP
transmission mode
23,040
POUc: IP

100
Issue 09 (2015-07-27)
6 Appendix
Parameter Name
Meaning
Specificat
ion
Board
GbTputPerPOUcFR
Throughput (Mbit/s)
over the Gb interface in FR
transmission mode
504
POUc: Gb
FR
E1PortPerEIUa
Number of ports supported

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

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

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

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

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

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

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

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

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

by the PEUa over the Abis
mode
384
PEUa: IP

101
Issue 09 (2015-07-27)
6 Appendix
Parameter Name
Meaning
Specificat
ion
Board
ACICperPEUaIP

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

by the FG2c/GOUc/GOUe
over the Abis interface in IP
transmission mode
2048
FG2c/
GOUc/
GOUe
ACICPerFG2c

GOUc/GOUe over the A
mode
23,040
FG2c/
GOUc/
GOUe
LogicalPortPerFG2c
Number of logical ports

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

circuits supported by each
TC subrack
10,240
TC subrack
Max64KNo7linkPerBSC
Maximum number of 64
kbit/s signaling links
supported by each BSC
4 x 16
BSC/No.7

102
6 Appendix
Parameter Name
Meaning
Specificat
ion
Board
MaxHSLNo7linkPerBSC
Maximum number of highspeed signaling links

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

Each type of board on the BSC6900 has its specification, which is calculated by collectively
considering the capacity on various aspects (including BHCA capacity, TRX capacity, CIC
capacity, and bandwidth capacity). The specification for a board indicates the capacity that a
board can stably run for a long period.
When a board is processing services, its bandwidth capacity, service parsing and forwarding
capacity, and signaling parsing and forwarding capacity must be taken into consideration.
Therefore, Huawei uses the board usage to represent the board capacity.
Board usage = Traffic volume on the BSC/Maximum board specification
where,
Traffic volume on the BSC can be the BHCA capacity, TRX capacity, or any other board
capacity.
For example,
The GOUe board supports a maximum of 23,040 CICs over the A interface, and the number of
serving CICs is 10,000. Therefore, the board usage is 43.4% (10,000/23,040 x 100%).
Issue 09 (2015-07-27)

103
6 Appendix
6.6 UMTS Hardware Specifications

Table 6-8 UMTS Board Specifications
Issue 09 (2015-07-27)
Parameter
Parameter Description
Specifications
Board
BHCAPerSPUa
BHCA supported by each pair of

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

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

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

4800
SPUa
OnlineUsersPerSPUa
Number of online users supported by

12,000
SPUa
BHCAPerSPUb
BHCA supported by each pair of

SPUc/SPUb boards
124,000
SPUc/
SPUb
NodebPerSPUb

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

pair of SPUc/SPUb boards
600
SPUc/
SPUb
ActiveUsersPerSPUb

9600
SPUc/
SPUb
OnlineUsersPerSPUb
Number of online users supported by

24,000
SPUc/
SPUb
CellPerDPUb

DPUb board
150
DPUb
ErlPerDPUb
Erlang supported by each DPUb

board
1800
DPUb
ActiveUsersPerDPUb

each DPUb board
3300
DPUb
CellPerDPUe

DPUe board
300
DPUe
ErlPerDPUe
Erlang supported by each DPUe

board
3350
DPUe

104
6 Appendix
Parameter
Specifications
Board
PsThtPerDPUe
Real PS throughput(Mbit/s)
supported by each DPUe board
x=PS Rab mean

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

each DPUe board
5880
DPUe
MaxInterSubrackSwitchSCUa
Inter-subrack switching capability

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

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

each AOUc board
500
AOUc
ErlPerAOUc
Erlang supported by each AOUc

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

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

105
Issue 09 (2015-07-27)
6 Appendix
Parameter
Specifications
Board
IuDlPsThrPerAOU
c
350
AOUc
IuUlDlPsThrPerAOUc

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

each UOIc board
500
UOIc
ErlPerUOIc
Erlang supported by each UOIc

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

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

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

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

GOUe/FG2c board
18,000
GOUc/
GOUe/
FG2c
SessionsPerGOUc/
SessionsPerFG2c
IuPS Setup&Reconfigure Sessions

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

GOUc/GOUe/FG2c board
129,000
GOUc/
GOUe/
FG2c

106
Issue 09 (2015-07-27)
6 Appendix
Parameter
Specifications
Board
IuPSTeidPerGOUc
/IuPSTeidPerFG2c
Iu-PS TEID number supported by

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

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

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

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

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

AOUc
252/336
AOUc

107
Issue 09 (2015-07-27)
6 Appendix
Parameter
Specifications
Board
Stm1PortNumUOI
c

by UOIc
UOIc
POUc
Stm1PortNumPO
Uc

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

POUc
3200
NIUa
PsThtPerNIUa

each NIUa board

108
7 Acronyms and Abbreviations
Acronyms and Abbreviations
Table 7-1 Acronyms and abbreviations
Issue 09 (2015-07-27)
Acronym and abbreviation
Full Name
ATM
Asynchronous Transfer Mode
CN
Core Network
GPS
Global Positioning System
Iu
Interface between RNC and CN
Iub
Interface between RNC and NodeB
Iur
Interface between RNC and RNC
NodeB
Base station in WCDMA networks
RNC
Radio Network Controller
MPS
EPS
STM-1
Synchronous Transfer Mode 1

109

BSC6900 Configuration Principle (Global) (V900R015C00 - 09) (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

BSC6900 Configuration Principle (Global) (V900R015C00 - 09) (PDF) - en

Uploaded by

Copyright:

Available Formats

SRAN8.0&GBSS15.0&RAN15.

Configuration Principles (Global)

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

4.4.1 BSC6900 GSM Examples of Typical Configurations...............................................................................................56

5 Expansion and Upgrade Configurations.................................................................................67

7 Acronyms and Abbreviations.................................................................................................109

Huawei Proprietary and Confidential

This chapter provides information about the changes in different versions of

4.1.5 General Principles

Changed the resource allocation algorithm for service processing

Huawei Proprietary and Confidential

4.1.3 Interface Boards

Differentiated interface board specifications in Abis over TDM

Added basic configuration principles.

4.2.3 Service Processing

Added the description that only one SAU is delivered in GU or

4.1.6 Subracks Configurations

Optimized the method of calculating the number of

Huawei Proprietary and Confidential

4.2.2 Hardware Capacity License

Modified some descriptions.

4.2.7 Subracks Configurations

4.2.1 Impact of the Traffic Model

Updated the method of estimating the number of

4.2.3 Service Processing Units

Optimized the procedure of typical configuration.

4.2.10 Description of Restrictions

Modified some descriptions.

6.6 UMTS Hardware

Updated board specifications.

4.2.6 Principles for Board

Changed the default number of SAUs to be configured

Huawei Proprietary and Confidential

4.1.2 Service Processing Units

Updated XPUb specifications for eGBTSs and

4.2.4 Interface Boards

l Changed the value of "IuPS session setup/release

6.2.2 UMTS Traffic Model

Updated "smartphone traffic model" and the

Added the notes for BHCA, PS throughput, and traffic

4.2.1 Impact of the Traffic Model

Corrected board names for UMTS.

4.2.7 Subracks Configurations

Updated the configuration principles for SAU boards

4.2.4 Interface Boards

l Added the rules for calculating the number of Iur

6.6 UMTS Hardware

l Added specifications of ports on Iur interface

Huawei Proprietary and Confidential

4.1.2 Service Processing Units

Updated the configuration principles for XPUb boards

4.2.4 Interface Boards

Modified the configuration principles for Iur-P

GCUb, GCGb, and TNUb boards

UMTS NASP boards

Huawei Proprietary and Confidential

About This Chapter