Professional Documents
Culture Documents
1 BSC6910
Configuration Principle
Issue 07
Date 2016-07-12
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.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
1 Change History.............................................................................................................................. 1
2 Introduction.................................................................................................................................... 5
2.1 Overview........................................................................................................................................................................ 6
2.2 Version Differences and Hardware List..........................................................................................................................6
3 Application Overview................................................................................................................ 10
4 Product Configurations.............................................................................................................. 14
4.1 BSC6910 GSM Product Configurations.......................................................................................................................15
4.1.1 Hardware Specification Redundancy........................................................................................................................ 15
4.1.2 Cabinets..................................................................................................................................................................... 15
4.1.3 Subracks.....................................................................................................................................................................16
4.1.4 License.......................................................................................................................................................................20
4.1.5 Service Processing Modules...................................................................................................................................... 21
4.1.6 Interface Boards.........................................................................................................................................................26
4.1.7 General Principles for Slot Configurations............................................................................................................... 31
4.1.8 Auxiliary Material Configurations............................................................................................................................ 31
4.1.9 Example BSC6910 GSM Configuration................................................................................................................... 32
4.1.10 BSC6910 GSM Recommended Capacity for Delivery........................................................................................... 35
4.2 BSC6910 UMTS Product Configurations.................................................................................................................... 36
4.2.1 Cabinets..................................................................................................................................................................... 37
4.2.2 Subracks.....................................................................................................................................................................38
4.2.3 Hardware Capacity License.......................................................................................................................................42
4.2.4 Service Processing Modules...................................................................................................................................... 43
4.2.5 Interface Boards.........................................................................................................................................................53
4.2.6 Configuration Principles for Interface Boards and Service Boards...........................................................................59
4.2.7 Board Redundancy Modes.........................................................................................................................................59
4.2.8 Auxiliary Materials....................................................................................................................................................61
4.2.9 Restrictions on Inter-Subrack Switching................................................................................................................... 62
4.2.10 Example BSC6910 UMTS Configuration............................................................................................................... 63
4.2.11 BSC6910 UMTS Recommended Capacity for Delivery.........................................................................................70
4.3 BSC6910 GU Product Configurations......................................................................................................................... 71
4.4 Built-in ECO6910 Product Configurations.................................................................................................................. 72
7 Appendix....................................................................................................................................... 88
7.1 GSM Configuration Reference..................................................................................................................................... 89
7.1.1 GSM Traffic Model................................................................................................................................................... 89
7.1.2 GSM Hardware Specifications.................................................................................................................................. 91
7.2 UMTS Configuration Reference.................................................................................................................................. 93
7.2.1 UMTS Traffic Model.................................................................................................................................................93
7.2.2 UMTS Board Specifications......................................................................................................................................99
7.3 List of Board Power Consumption............................................................................................................................. 105
1 Change History
07 (2016-07-12)
Compared with Issue 06 (2016-06-06), this issue includes the following changes.
Modi None
fied
Delet None
ed
Editorial Modified the number of required EXOUa boards, for the EXOUa boards do
change not support N+1 backup mode. For details, see 4.2.10 Example BSC6910
UMTS Configuration.
06 (2016-06-06)
Compared with Issue 05 (2016-03-31), this issue includes the following changes.
Modi None
fied
Delet Deleted the description that SAU boards are delivered by default in
ed GO mode. For details, see 4.1.5 Service Processing Modules.
Editorial Modified power specifications (four 60 A inputs now for each subrack). For
change details, see 3 Application Overview.
Modified the description about NodeB and cell specifications supported by
each EGPU. For details, see 4.2.4 Service Processing Modules.
05 (2016-03-31)
2
Compared with Issue 04 (2015-12-31), this issue includes the following changes.
Change Description
04 (2015-12-31)
Compared with Issue 03 (2015-09-10), this issue includes the following changes.
Change Description
Change Description
Modified Moved the power distribution box out from subracks. For details, see 4.1.3
Subracks and 4.2.2 Subracks.
Modified the method for calculating the number of EGPUs and EXPUs
required by IBCA. For details, see 4.2.4 Service Processing Modules.
Reorganized 4.4 Built-in ECO6910 Product Configurations.
Deleted Deleted descriptions about laws and regulations because this product
complies with the uniform Huawei regulations.
Deleted descriptions about the impacts of traffic models on product
configurations because such impacts are subject to network conditions.
03 (2015-09-10)
Compared with Issue 02 (2015-05-08), this issue includes the following changes.
Change Description
Added None
Modified 1. Added the constraints between the EXOUa board and the
interconnected transmission equipment. For details, see 4.1.6 Interface
Boards and 4.2.5 Interface Boards.
2. Modified information about the boards that can be shared by multiple
interfaces. For details, see 4.1.6 Interface Boards.
3. Modified typical GSM configurations. For details, see 7.1.1 GSM
Traffic Model.
Deleted None
02 (2015-05-08)
Compared with Issue 01 (2015-03-25), this issue includes the following changes.
Change Description
Added None
Modified UMTS interface boards, such as the FG2c, GOUe, and EXOUa boards, no
longer support N+1 backup mode.
1. Removed N+1 backup from 4.2.5 Interface Boards.
2. Removed N+1 backup in resource pool mode from redundancy modes
of FG2c, GOUe, and EXOUa boards in 4.2.7 Board Redundancy
Modes.
Deleted None
01 (2015-03-25)
Compared with Draft A (2015-01-15), this issue includes the following changes.
Change Description
Added None
Modified l Changed the UMTS ENIUa specifications to 4.8 Gbit/s when the
experience oriented network planning and optimization function or the
WRFD-171210 Radio-Aware Video Precedence feature is enabled, and
updated the calculation methods and configuration rules for UMTS
ENIUa boards. For details, see 4.2.4 Service Processing
Modules, 4.2.6 Configuration Principles for Interface Boards and
Service Boards, and 7.2.2 UMTS Board Specifications.
l Changed the DEUa specifications from 208,000 Erlang to 260,000
Erlang when WRFD-171201 Crystal Voice in Deep Coverage is
enabled.
Deleted None
Draft A (2015-01-15)
Compared with Issue 05 (2014-10-29) of V100R016C00, this issue includes the following
changes.
Change Description
Added None
Deleted None
2 Introduction
2.1 Overview
2.2 Version Differences and Hardware List
2.1 Overview
This document describes the product specifications, configuration principles, upgrade, and
capacity expansion regarding the BSC6910 V100R017C10.
The BSC6910 can be configured as a BSC6910 GSM, BSC6910 UMTS, or BSC6910 GSM
+UMTS (GU) to adapt to various application scenarios:
l A BSC6910 GSM works in GSM Only mode and functions as a GSM BSC.
l A BSC6910 UMTS works in UMTS Only mode and functions as a UMTS RNC.
l A BSC6910 GU works in GSM&UMTS (GU) mode and functions as a GSM BSC and
UMTS RNC.
Table 2-1 Version differences between HW6910 R15 and later versions
Hardware Version Difference
Version
HW6910 R15 HW6910 R15 supports GOUe, GCUb, and GCGb boards (in versions
later than R15C00SPC580),
which can coexist with GOUc, GCUa, and GCGa boards. They have the
same specifications but. However, an old board and its corresponding new
board cannot work in active/standby mode.
HW6910 R16 HW6910 R16 has introduced SCUc boards to expand the switching
bandwidth between extension subracks and slot bandwidth.
Using HW6910 R16, an old board and its corresponding new board (for
example, GOUc and GOUe, GCGa and GCGb, and GCUa and GCUb)
can work in active/standby mode.
HW6910 R17 HW6910 R17 has introduced DEUa boards to support WRFD-170201
Seamless Crystal Voice and WRFD-171201 Crystal Voice in Deep
Coverage.
HW6910 R18 has introduced EGPUb and EXPUb boards. EGPUb boards
function as the evolved version of EGPUa boards as they have the same
specifications. The same is true for EXPUb and EXPUa boards.
In the UMTS network, an RNC pool can be configured by using BSC6910s alone or
BSC6910s and BSC6900s if the RNC in Pool feature is activated. RNCs within an RNC pool
work in node redundancy and resource sharing modes.
The following table describes HW6910 R17 hardware.
QM1D00EOM EOMU Evolved Operation and Provides the GSM & UMTS
U00 a Maintenance Unit evolved operation
and maintenance
function.
QM1D00EXO EXOU Evolved 10GE Optical Provides two GSM & UMTS
U00 a interface Unit REV:a channels over
10GE optical
ports.
WP1D000GCU GCUb General Clock Unit Obtains the GSM & UMTS
02 system clock
source, performs
the functions of
phase-lock and
holdover, and
provides clock
signals.
QW1D000GC GCGb GPS & Clock Obtains the GSM & UMTS
G02 Processing Unit system clock
source, performs
the functions of
phase-lock and
holdover, and
provides clock
signals.
NOTE
3 Application Overview
Table 3-1 describes the maximum and minimum BSC6910 configurations in different
working modes.
Table 3-1 Maximum and minimum BSC6910 configurations in different working modes
BSC691 UMTS (2 subracks: 1 MPS and 1 UMTS (one MPS and four EPSs)
0 GU EPS): 10,000 NodeBs, 20,000 cells,
3330 NodeBs, 6660 cells, 53,300,000 BHCA, 99.8 Gbit/s PS
21,300,000 BHCA, 39.3 Gbit/s PS throughput or 208,000 CS traffic (Erl)
throughput or 82,000 CS traffic (Erl) GSM (three subracks: three EPSs that
GSM (1 EPS): can be configured across cabinets):
l In all-IP transmission mode: l In all-IP transmission mode: 8000
8000 BTSs, 8000 cells, 8000 BTSs, 8000 cells, 24,000 TRXs,
TRXs, 50,000 traffic (Erl), 150,000 Erl, 96,000 PDCHs,
32,000 PDCHs, 17,300,000 52,000,000 integrated BHCA, 8
integrated BHCA, 3 Gbit/s PS Gbit/s PS throughput
throughput l In TDM mode: 7000 BTSs, 7000
l In TDM mode: 3000 BTSs, 3000 cells, 7000 TRXs, 43,750 traffic
cells, 3000 TRXs, 18,750 traffic (Erl), 28,000 PDCHs, 15,000,000
(Erl), 12,000 PDCHs, 6,500,000 integrated BHCA, 2.688 Gbit/s PS
integrated BHCA, 1.1 Gbit/s PS throughput
throughput
Power range 57 V to 40 V
Power consumption of The cabinet power consumption equals the sum of power
a single cabinet consumption of all subracks in the cabinet. The maximum of
power consumption per cabinet is 12000 W. The power
consumption of a typically configured cabinet should be equal to
or less than 7100 W to reduce the impact of cabinet heat
dissipation on the equipment room.
NOTE
4 Product Configurations
You must negotiate with customers about hardware redundancy. Generally, 30% redundancy
is recommended.
For example, when calculating the number of DPUf boards for processing CS user-plane data
in A over TDM mode:
4.1.2 Cabinets
To achieve maximum capacity, a BSC6910 GSM can be configured with up to three subracks
in a single cabinet. In GU mode, the three subracks can be distributed across two cabinets.
For details about the power consumption of each board, see 7.3 List of Board Power
Consumption.
4.1.3 Subracks
Table 4-2 Subrack Configurations
Part Number Name Description Function Description
WP1M00EPEM00 Power Power input module Each subrack has its own
Distributio (version: a) power supply, which is
n Box provided by two power
distribution boxes.
1. Provides power supply,
surge protection, and
filtering.
2. Detects the input power
and input voltage of a
subrack.
3. Monitors the status of
air circuits and of surge
protection circuits.
The MPS and EPS of the BSC6910 have the same physical structure. They both use PARCb
subracks. The difference is that the MPS houses the EOMUa, GCUb, GCGb, and EGPUa/
EXPUa/EGPUb/EXPUb boards (logical function: RMP), which are not housed in the EPS.
The following table lists fixed boards in the BSC6910.
Number of EPSs = Max (Number of required EPSs_1, Number of required EPSs_2, Number
of required EPSs_3)
NOTE
Calculate the number of EPSs based on the SCUb configuration, regardless of whether the SCUb or
SCUc is installed.
Capacity expansion
Number of required EPSs = Number of EPSs required after capacity expansion Number of
EPSs configured before capacity expansion
The maximum power supply of a subrack is 4000 W. The maximum power consumption of a
cabinet is 12000 W.
NOTE
l Average power consumption (Pavg) is the estimated value in a typical operating environment. The
maximum power consumption mentioned in hardware description is obtained when all devices on
boards are full-loaded. This maximum power consumption will not be obtained under the actual
system running conditions. Therefore, Pavg is provided for power consumption calculation.
l Maximum subrack power consumption is 4000 W (including the power consumption of fans) which
is obtained when all slots of the subrack are configured with boards. It is recommended that power
distribution be configured as 4000 W per subrack. This can save power distribution adjustment upon
future capacity expansion.
l For details about the power consumption of each board, see 7.3 List of Board Power
Consumption.
4.1.4 License
The ENIUa does not have hardware processing capability. The Resource-BSC6910-
LGW1DPIHC02-Evolved Network Intelligence Processing Throughput(per 50Mbit/s) license
must be loaded for the board. Each license provides a processing capability of 50 Mbit/s. A
maximum number of N licenses can be loaded, where N is equal to the result of NIU
processing capability divided by 50 Mbit/s. The ENIUa can process the services that require
service type awareness on GSM and UMTS sides at one time. The traffic carried on the
ENIUa board is the sum of traffic over GSM Gb interfaces and UMTS Iu interfaces.
If the BSC6900 is replaced by a BSC6910, the BSC license cannot be used and needs to be
quoted again. However the existing BTS license can be directly used by using license
adjusting tools after the BSC6910 is used.
By default, the following boards are delivered: EGPUa, EXPUa, ENIUa, and DPUf.
Cell 600
BTS 600
By default, GCUP can be configured in N+1 redundancy mode. You can manually configure
the number of redundant GCUP boards. A BSC is configured with a minimum of two GCUP
boards.
1. Calculating the number of required EGPU boards based on the number of TRXs:
1. Calculating the number of required EGPU based on the: CS user-plane traffic volume:
NOTE
When the VAMOS feature is enabled, the traffic volume supported by a single TRX increases.
Therefore, the number of EGPUs calculated by using the preceding formula increases.
1. Calculating the number of required EGPU boards based on the number of cells:
1. Calculating the number of required EGPU boards based on the number of BTSs:
1. The number of required EGPU boards to be configured is equal to the maximum value of
all the values.
MaxACICPerBSCTDM indicates the maximum number of CIC circuits required for the A
interface of a BSC. It is calculated based on the traffic model.
2000 3000 2
4000 3000 2
6000 3000 3
By default, the following boards are delivered: FG2c, GOUe, EXOUa, and POUc.
NOTE
In Abis over TDM, a POUc board supports a maximum of 1024 TRXs when both of the following
conditions are met:
The traffic model is 6.25 Erlangs per TRX. Three PDCHs are configured on each TRX on the average
and the MCS-7 is used, or two PDCHs are configured on each TRX on the average and the MCS-9 is
used.
In fixed Abis networking, idle timeslots and monitoring timeslots must be properly configured.
Otherwise, the number of TRXs supported by the POUc cannot reach the maximum specification.
After the VAMOS feature is enabled, extra Abis bandwidth is required, which also affects the TRX
specifications of interface boards.
Configuration principle of interface boards: The total number of required interface boards
equals the sum of interface boards required on each interface. Interface boards work in 1+1
active/standby mode. The BSC6910 does not support the BM/TC separated mode and
therefore does not have the Ater interface. The A, Gb, and Abis interfaces must be configured
on the BM side. You are advised to configure the A, Gb, and Abis interfaces on different
interface boards.
To determine the number of Abis interface boards, you can use the following formula: number
of Abis interface boards = 2 x Roundup (Max (Number of TRXs in a transmission mode/
Number of TRXs supported by the interface board, Number of ports in a transmission mode/
Number of ports supported by the interface boards), 0)
In Abis over TDM networking, the BSC6910 supports only the POUc board. If a TDM over
E1/T1 link is used for the transmission to the BSC over Abis interfaces, the TDM over E1/T1
must be converted to a TDM over STM-1 link using a device that performs optical-to-
electrical conversion, for example, Huawei optical switch node (OSN) products.
Number of TRXs supported by the POUc x (Average number of Erlangs per TRX + Average
number of PDCHs per TRX x Number of timeslots required for PS transmission) 16,384
The following table lists the number of timeslots required for PS transmission.
CS-1 1
CS-2 1
CS-3 2
CS-4 2
MCS-1 1
MCS-2 1
MCS-3 2
MCS-4 2
MCS-5 2
MCS-6 2
MCS-7 3
MCS-8 4
MCS-9 4
For example:
1. Assume that the POUc supports 1024 TRXs, the average number of Erlangs per TRX is
6.25, the average number of PDCHs per TRX is 3, and the number of timeslots required
for PS transmission is 3 when MCS-7 is used. Then, the calculation result is 15,616,
which is less than 16,384.
2. If a POUc supports 1024 TRXs, the average number of Erlangs per TRX is 6.25, the
average number of PDCHs per TRX is 4, and the number of timeslots required for PS
transmission is 4 when MCS-9 is used, then the calculation result is 22,784, which is
greater than 16,384. In this case, the number of TRXs supported by the POUc should be
reduced to 736.
3. If the BTS provides IP over E1 links, the BSC provides IP transmission links, and the
transmission equipment provides Abis interfaces for IP over E1 links, only GE interface
boards FG2c or GOUe, instead of the 10GE interface board EXOUa, can be configured
on the BSC6910.
4. If the BSC provides IP over E1 links, the POUc board must be configured in the
BSC6910.
Configuration precautions:
In A over TDM networking, the BSC6910 must be configured with the POUc board (TDM
over STM-1), which does not support TDM over E1/T1. If the BSC uses TDM over E1/T1 to
connecting the CN, an optical-to-electrical conversion module (for example, Huawei OSN)
must be installed to convert E1/T1 signals to STM-1 signals.
Calculation of total interface boards when multiple interfaces share one interface
board
For GSM, each interface uses its own interface boards by default. Only the EXOUa board can
be shared by multiple interfaces, as listed in the following table.
It is recommended that multiple interfaces not share the same interface board for the
following reasons:
l The relationship between the Abis interface board and the BTS is fixed and load sharing
cannot be performed. Therefore, it is recommended that the Abis interface not use the
same interface board as other interfaces. If the Abis interface share an interface board
with other interfaces, the data configuration is difficult, the maintenance cost is high, and
even the reliability may be affected when the traffic module is complex.
l There is no admission control on the Gb interface. Therefore, it is recommended that the
Gb interface not use the same interface board as other interfaces.
l Multiple interfaces (Abis, A, and Gb) sharing one interface board applies only to small-
capacity BSCs.
To calculate the total interface boards when multiple interfaces share one interface board use
the following formulas:
Operator provides the network requirements which must include the information contained in
the following figure. Here is an example.
Parameter Value
Parameter Value
MR report/sub/BH 144
The following figure shows the dimensions that are used for calculating the configurations.
2 Abis GE QTY A2
3 A CIC QTY A3
4 IWF QTY A4
5 BHCA A5
6 Gb data flow A6
7 PDCH QTY A7
Step 3 Get the network capacity requirements to calculate the hardware requirements.
Item Name Configuration Before
Capacity Expansion
3 Interface board B3
4 Cabinet B4
----End
Figure 4-1 Relationship between capacity of control plane and use plane
4.2.1 Cabinets
The following table describes cabinet configurations.
New deployment
Power consumption per cabinet = Roundup [SUM(Power consumption of all boards within
the cabinet + power consumption of the fan box within the cabinet)]
When the power consumption per cabinet is higher than 7100 W, confirm with customers
whether the heat dissipation capability of the equipment room is sufficient. where Power
consumption of all boards refers to the average power consumption.
The power consumption per subrack on the BSC6910 is 4000 W. The maximum power
consumption per cabinet on the BSC6910 is 12000 W.
NOTE
l Average power consumption (Pavg) is the estimated value in a typical operating environment. The
maximum power consumption mentioned in hardware description is obtained when all devices on
boards are full-loaded. This maximum power consumption will not be obtained under the actual
system running conditions. Therefore, Pavg is provided for power consumption calculation.
l Maximum subrack power consumption is 4000 W (including the power consumption of fans) which
is obtained when all slots of the subrack are configured with boards. It is recommended that power
distribution be configured as 4000 W per subrack. This can save power distribution adjustment upon
future capacity expansion.
l Every subrack contains 2 fan Assemblies, each fan assembly costs 100 W.
l For details about the power consumption of each board, see 7.3 List of Board Power
Consumption.
Capacity expansion
4.2.2 Subracks
Table 4-11 describes subrack configurations.
The MPS and EPS of the BSC6910 have the same physical structure. They both use the
PARCb subrack. The difference is that the MPS houses the EOMUa, GCUb, GCGb, and
EGPUa/EGPUb boards (used for resource management), which are not housed in the EPS.
NOTICE
The ENIUa, EGPUa/EGPUb, and interface boards not working in active/standby mode can be
inserted in a pair of active and standby slots.
New deployment
Number of EPSs = Max (Number of required EPSs_1, Number of required EPSs_2, Number
of required EPSs_3)
NOTE
Number of required EGPU boards does not include the number of the fixed EGPU boards in the MPS
for resource management.
Calculate the number of EPSs based on the SCUb configuration, regardless of whether the SCUb or
SCUc is installed.
Capacity expansion
Number of required EPSs = Number of EPSs required after capacity expansion Number of
EPSs configured before capacity expansion
RNC Active User Hardware Capacity license (per 1000 Active Users)
The control item "Active User" refers to the number of users in the CELL_DCH or
CELL_FACH state. It is attached to EGPU boards. Configuring this license helps increase the
number of active users on the condition that EGPU hardware allows. Each license increases
the number of active users by 1000. This license can be shared among EGPU boards working
in resource pool mode under a single RNC. It is not bound to any specific EGPU board.
If this license is unavailable, EGPU boards cannot work properly.
Evolved Network Intelligence Throughput License(per 50Mbit/s)
This license is intended for ENIUa hardware capacity. Adding this license helps increase the
RNC capability of enhancing network intelligence on the condition that the existing hardware
capability allows. This license can be shared among ENIUa boards working in resource pool
mode under a single RNC. It is not bound to any specific ENIUa board.
If this license is unavailable, ENIUa boards cannot work properly.
EGPUa Evolved Processes Used only for the user The PS throughput
(QM1D General services and plane: 2000 Mbit/s PS specifications are
00EGP allocates throughput or 10,050 given at the 64 kbit/s
U00) Processing services on the CS Erlang, 28,000 uplink rate and 384
Unit GSM UP and active users, and kbit/s downlink rate
REV:a CP. 70,000 online users in high PS traffic
model.
By default, EGPUa, ENIUa, and EGPUb boards are delivered. If enhanced service awareness
units are required, ESAUa boards are delivered by default. If enhanced data processing units
are required, DEUa boards are delivered by default.
NOTE
The EGPU board can process services on both the user plane and control plane. You can
calculate the number of EGPU boards required by the control plane and the number required
by the user plane, and then add the two numbers to obtain the total number of required EGPU
boards.
NOTE
The calculated number of EGPU boards does not include the EGPU boards used for resource
management.
Methods for configuring EGPU boards required by the user plane and hardware
capacity license
Item Descrip Value Format Prerequisites Calculation of
tion the Board
Quantity
NOTE
On-line user represents the number of users in the RRC connected state, including those in the
Cell_DCH, Cell_FACH, Cell_PCH, and URA_PCH states.
The number of required EGPUb UP boards is calculated using the following formula:
N_EGPUb_UP = MAX(EGPUb_ps + EGPUb_cs, EGPUb_au, EGPUb_cell)
The required RNC Throughput Hardware Capacity license is calculated using the following
formula:
N_ EGPU_Iub_License = ROUNDUP[(a + b x 12.2 x 2/1000)/50 Mbit/s]
Methods for configuring EGPU boards required by the control plane and
hardware capacity license
Item Description Value Format Prerequisi Calculation of
tes the Board
Quantity
The number of EGPUb boards required for the control plane is calculated using the following
formula:
N_EGPUb_nodeb_cell = max(nb/700,c/700)
"+1" indicates that one additional EGPUa board is required for redundancy.
The required RNC Active User Hardware Capacity is calculated using the following formula:
The EGPU board can process services on both the control plane and user plane. All the EGPU
boards (for both the user plane and control plane) form a resource pool. The EGPU boards
work in N+1 redundancy mode.
NOTE
EGPU boards for resource management (RMP) work in 1+1 redundancy mode.
The ENIUa provides the service awareness and PS service quality measurement functions.
If the ENIUa board is used for only the service awareness function:
Number of ENIUa boards required: N_ENIUa = Roundup (a/8000) + 1
Network Intelligence Throughput License = Roundup (a/50)
If the ENIUa board is used for both the service awareness and PS service quality
measurement functions:
Number of ENIUa boards required: N_ENIUa = Roundup (a/4800) + 1
Network Intelligence Throughput License = Roundup (a/50)
Table 4-15 Proportions of traffic volume delivered by major bearer types and application
types (assumed conditions)
Bearer Type HTTPS HTTP (Web HTTP HTTP Others
and Browsing) (Video) (File
Application Access)
Type
NOTICE
l The ENIUa board must be configured with the Evolved Network Intelligence Processing
Throughput(per 50 Mbit/s) License to provide hardware processing capabilities. Each
license has a processing capability of 50 Mbit/s.
l When the ENIUa board is used for PS service quality measurement, the board
specifications are determined by the proportions of traffic delivered by different bearer
types and application types. The assumed conditions in this table apply to most
commercial networks.
l It is recommended that ENIUa boards be configured in N+1 redundancy mode.
Iub CS Voice Iub CS traffic Vco_b(Erlang) = IuCS Voice Traffic Number of DEUa
Traffic in in soft x Ratio of SHO user x Iub RL boards = Vco_b
Soft HO state handover number per SHO user (Erlang) x
state This applies only to WRFD-170201 (Proportion of
(excluding Seamless Crystal Voice. WB-AMR)/3600 +
softer Vco_b(Erlang) x (1
handover) Proportion of
(Erlang) WB-AMR)/9000
Note:
1. Proportion of WB-AMR indicates the radio of WB-AMR traffic to total CS traffic. The
default value is 0.05, which can be set based on network conditions.
2. Ratio of SHO user indicates the ratio of users in the soft handover state to total users.
The default value is 0.25. You can set it based on actual network conditions.
3. Iub RL number per SHO user indicates the average number of radio links used by users
in the soft handover state. The default value is 2.8, which can be set based on network
conditions.
The specifications of DEUa boards for WB-AMR and NB-AMR are different, as listed in the
following table.
If the WRFD-170201 Seamless Crystal Voice feature is required, configure the DEUa board.
The calculation method is as follows:
If the voice services in the network are all NB-AMR (12.2 kbit/s), the number of DEUa
boards is calculated as follows: N_DEUa_SeamlessCryV = Roundup (Vco_b/9000) + 1
If voice services use WB-AMR on the live network, the number of DEUa boards is calculated
as follows:
If the WRFD-171201 Crystal Voice in Deep Coverage feature is used, configure the DEUa
board. The calculation method is as follows:
To use both the WRFD-170201 Seamless Crystal Voice and WRFD-171201 Crystal Voice in
Deep Coverage features, configure more DEUa boards. The calculation method is as follows:
NOTE
The Iur-p interface is used when the RNC in Pool feature is enabled.
The following interface boards are delivered by default: GOUe, FG2c, AOUc, UOIc, and
EXOUa.
NOTE
On-line user indicates the number of users in the RRC connected state, including users in the Cell_DCH,
Cell_FACH, Cell _PCH, and Ura_PCH state. Active user indicates the number of users in the Cell
_DCH and Cell _FACH state.
l In this table, the EXOUa specifications regarding UL(Mbit/s), DL(Mbit/s), and UL
+DL(Mbit/s) are based on UL/DL 64 kbit/s/384 kbit/s.
l The specifications of interface boards on the Iur interface are the same as those of
interface boards on the Iub interface.
l The preceding tables list the maximum processing capabilities of boards. For example,
values in the Number of Connected NodeBs indicate the maximum numbers of NodeBs
that can be connected. The actual number of NodeBs is restricted by the throughput.
The following table describes how to configure the Iub interface board (Iur interface is similar
to Iub interface, without configuring NodeBs).
The configuration method of the Iur interface is similar to that of the Iub interface (without
considering the NodeB).
For Iur interface, if there are several Iur interfaces which do not share ports with each other,
the port requirement and port specification of each interface board should be taken into
account.
Alternatively, the
recommended typical Iu
PS throughput of 10 Gbit/s
is used.
If the Iu-CS and Iu-PS interfaces use the same interface board:
BSC6910 interface boards support 1+1 backup mode. The number of interface boards is
calculated using the following formula: Sum(Iub, Iu-CS, Iu-PS, Iur) x 2.
MPS 3 1 2 1 2
EPS1 3 1 2 1 0
EPS2 3 1 1 1 0
EPS3 2 0 1 1 0
EPS4 2 0 1 1 0
EPS5 2 0 1 1 0
Total 15 3 8 6 2
The operator provides the network capacity requirement which should include the information
listed in Table 4-23.
Item Value
Item Value
NAS (Attach, Detach, LAU, RAU) and SMS per subscriber per BH 3.6
Step 2 Calculate the capacity requirements on the control plane, user plane, and transmission plane,
and the board capabilities under the traffic model.
1. Total Iu-PS throughput requirement (based on sample input, the value is 3600 Mbit/s)
= Total Subscribers x PS throughput (Including R99 and HSPA, UL+DL) per PS
subscriber in BH (bit/s) = 800,000 x 4,500 bit/s= 3600 Mbit/s
2. Total Iu-CS Erlang requirement (based on sample input, the value is 16,000 Erl)
Total Iu-CS Erl = Total Subscribers x Voice Traffic per CS voice subscriber in BH
(Erlang) = 800,000 x 0.02 = 16000
3. Total Iu-PS TEID requirement (based on sample input, the value is 23,111)
= Total Subscribers x [Mean holding time (MHT) in DCH/H/FACH state per PS call(sec)
+ Mean holding time (MHT) in PCH per PS call(sec))] x PS call per subscriber per BH/
3600 = 800,000 x (52 + 0) x 2/3,600 = 23,111
4. Iu-PS session setup/release times requirement (based on sample input, the value is 1778
times/s)
IuPS session setup/release times = Total Subscribers x [PS call per subscriber per BH x
(1 + PS channel switch times per PS call x 0.5 + Cell update times per PS call x 0.5)]/
3600 = 800,000 x [2 x (1 + 3 x 0.5 + 3 x 0.5)]/3600 = 1778
See Table 4-19 for the coefficient.
5. Total Iub PS throughput requirement (based on sample input, the value is 4680 Mbit/s)
= Total Subscribers x PS throughput (Including R99 and HSPA, UL+DL) per PS
subscriber in BH (bit/s) x (1 + Proportion of SHO for PS call)= 800,000 x 4,500 x (1
+ 0.3) bit/s = 4680 Mbit/s
6. Total Iub CS Erlang requirement (based on sample input, the value is 20,800 Erl)
Total Iub CS Erlang = Total Subscribers x Voice Traffic per CS voice subscriber in BH
(Erlang) x (1 + Proportion of SHO for CS call) = 800,000 x 0.02 x (1 + 0.3) = 20,800
7. Total BHCA requirement (based on sample input, the value is 2,368,000)
Total BHCA = Total Subscribers x (CS Voice call per subscriber per BH + PS call per
subscriber per BH) = 800,000 x (0.96 + 2) = 2,368,000
8. Total NodeB number requirement (based on sample input, the value is 600) = Total
NodeBs = 600
9. Total Cell number requirement (based on the sample input, the value is 3000)
= Total Cells= 3000
10. Total active users requirement (based on sample input, the value is 39,111)
Total active users = Total Subscribers x [Mean holding time (MHT) in DCH/H/FACH
state per PS call (sec) x PS call per subscriber per BH/3600 + Voice Traffic per CS voice
subscriber in BH(Erlang)] = 800,000 x (52 x 2/3600 + 0.02) = 39,111
11. Total online users requirement (based on sample input, the value is 39,111)
= Total Subscribers x {[Mean holding time (MHT) in DCH/H/FACH state per PS
call(sec) + Mean holding time (MHT) in PCH state per PS call(sec)] x PS call per
subscriber per BH/3600 + Voice Traffic per CS voice subscriber in BH(Erlang)} =
800000 x [(52 + 0) 2/3600 + 0.02] = 39111
12. Total Iub CID/UDP requirement (based on sample input, the value is 124,800)
= Total Subscribers x {Mean holding time (MHT) in DCH/H/FACH state per PS
call(sec) x PS call per subscriber per BH/3600 x [1 + 2 x (1+Proportion of SHO for PS
call)] + Voice Traffic per CS voice subscriber in BH(Erlang) x 2 x (1 + Proportion of
SHO for CS call)} = 800000 x {52 x 2/3600 x [1 + 2 x (1 + 0.3)] + 0.02 x 2 x (1 + 0.3) }
= 124800
13. In this traffic model, the BHCA of each EGPUa/EGPUb CP only board is 592,000.
EGPUa/EGPUb CP only resources per subscriber = [CS Voice call per subscriber per BH
x (W1 + Handover times per CS call x W2) + PS call per subscriber per BH x (w3 + PS
channel switch times per PS call x w7 + Cell update times per PS call x w8 + Handover
times per PS call x w6) + NAS (Attach, Detach, LAU, RAU) and SMS per subscriber
per BH x w9]/3600 = 14.96%/3600 = 0.0042%
Number of subscribers supported by each EGPUa/EGPUb CP only board = (70%
10%) x 14/EGPUa/EGPUb CP only resource consumed per subscriber = (70% 10%)
x 14/0.0042% = 200,000
BHCA supported by per EGPUa/EGPUb CP only board = Number of subscribers
supported by each EGPUa/EGPUb CP only board x (CS Voice call per subscriber per
BH + PS call per subscriber per BH) = 200,000 x (0.96 + 2) = 592,000
14. In this traffic model, the PS throughput of each EGPUa/EGPUb UP only board is 13680
Mbit/s.
PS RAB mean data rate (UL+DL) (kbit/s) = [PS throughput (Including R99 and HSPA,
UL+DL) per PS subscriber in BH (bit/s) x 3600/1000] /[PS call per subscriber per BH x
Mean holding time (MHT) in DCH/H/FACH state per PS call(sec)] = 4,500 x
3600/1000/(2*52) = 155.8
155.8 kbit/s is in the value range of [128, 196]. Therefore, PS Throughput Capacity per
EGPUa/EGPUb (Mbit/s) is calculated as follows: PS Throughput Capacity per EGPUa
(Mbps) = 1250 + (PS RAB Mean data rate - 128) x4.26 = 1250 + (155.8 - 128) x4.26 =
1368 Mbit/s
The number of licenses required for "RNC Throughput HW Capacity License (per 50
Mbit/s)" is calculated as follows:
1. Calculate the number of EGPU boards required for the control plane.
N_EGPU does not include the fixed EGPU boards for resource management.
1. Calculate the number of required ENIUa boards and the corresponding hardware license.
If ENIUa boards work in resource pool mode for load sharing, configure them in N+1
redundancy mode.
N_ENIUa = ROUNDUP(4680/4800) + 1 = 2
NOTE
The number of required N_ENIUa boards is greater than 0 only when the corresponding optional
features are enabled.
NOTICE
This item is effective only when the corresponding optional feature configuration. Other
wise, N_ DEUa =0.
If Iub, Iu-CS (the Iu-CS and Iur interfaces share the same interface board), and Iu-PS interface
boards are configured separately and work in 1+1 backup mode, the number of required
interface boards is as follows:
1) N_IUB_IF = ROUNDUP[Max(ba'+bb', bn', an')] x 2 = ROUNDUP[Max(0.59 + 0.28, 0.4,
0.25)] x 2 = 2
2) N_IUCSIUR_IF = ROUNDUP( [cb'+ 8% x ( ba' + bb')] x 2 = ROUNDUP[0.21 + 0.08 x
(0.84 + 0.28)] x 2 = 2
3) N_IUPS_IF = ROUNDUP[Max(pb', pu', ps')] x 2 = ROUNDUP[Max(0.36, 0.05, 0.04)] x 2
=2
N_EXOUa = N_IUB_IF + N_IUCSIUR_IF + N_IUPS_IF = 6
1. Number of required ESAUa boards
Four slots are required for two ESAUa boards. By default, the RNC is configured with one
ESAUa board for EBC. If the customer has purchased the Nastar service or other OSS
services (such as SON or PRS-based RAN service virtualization), one or two ESAUa boards
must be configured. The number of required ESAUa boards depends on feature
configurations. Assume that one ESAUa board is required in this example.
1. Number of required GCG boards
A pair of GCGb/GCGa boards must be configured if the GPS positioning function is required.
A pair of GCUb/GCUa boards must be configured if the GPS positioning function is not
required.
----End
delivered in a large scale on the live network. Therefore, it is recommended that the BSC6910
capacity be controlled for the initial network deployment.
For per BSC6910 the NodeB number should less than 600. If the RNC in Pool feature is
enabled, the number of NodeBs served by a BSC6910 is increased to be within 900.
Because network planning is a long-term action, the delivery of BSC capacity is on per-phase
basis. To ensure network reliability and security, active/standby configuration must be used
for large-capacity BSCs. Specifically, use the active/standby configuration for to double the
hardware capacity of the BSC6910. In long-term network planning, if a single BSC serves
600 to 1200 NodeBs, the RNC in Pool feature must be enabled to achieve 1+1 backup and
ensure large-capacity network security.
----End
the BSC6910, calculate the number of EGPUa//EGPUb boards and interface boards supported
by the built-in ECO6910. For details, see ECO6910 V100R004C10 Configuration Principle.
The service processing capability is enhanced by expanding hardware capacity. Follow the
minimum hardware configuration principle during capacity expansion.
5.1 BSC6910 GSM
5.2 BSC6910 UMTS
5.1.1 Precautions
The BSC6900 cannot be upgraded to the BSC6910 by upgrading the software, and can be
upgraded only by migrating the hardware. If the BSC6900 is upgraded to the BSC6910, the
BSC license of BSC6900 can be used for the BSC 6910 only after the license is quoted and
applied for again. However, the BTS license of the BSC6900 that has been quoted can be
directly used for the BSC6910 using license adjusting tools.
The BSC6910 supports the following boards: SCUb, SCUc, EOMUa, ESAUa, GCUa, GCGa,
GCUb, GCGb, EGPUa/EGPUb/EXPUa/EXPUb, DPUf, FG2c, GOUc, GOUe, EXOUa, and
POUc. The BSC6910 does not support other BSC6900 boards.
In A over IP networking, the EGPUa/EGPUb/EXPUa/EXPUb boards with the logical
function type GCUP used in the BSC6910 replace the XPUb, DPUf (for A over IP), and
DPUg boards used in the BSC6900. In A over TDM networking, the EGPUa/EGPUb/EXPUa/
EXPUb and DPUf boards must be configured in the BSC6910.
In the BSC6910 V100R016C00, the Ater and Pb interfaces are removed. The Abis and A
interfaces support IP and TDM transmission modes, whereas other external interfaces support
only IP transmission mode.
WP1D000GO GOUe The GOUe board has the same service capacity, GE port
U03 quantity, and configuration calculation formula as the FG2c
board except the interface type.
QM1B0PBCB Cabinet 1
N00
Total Replacement
An operator may want to increase equipment integration and achieve a larger capacity with
existing cabinets and subracks. In this case, a total replacement is recommended. In a total
replacement, the capacity is considered first.
The Unistar quotation template is used to work out a BSC equipment list based on the
specifications of the new hardware version. The boards required for the capacity expansion
are determined through a comparison with existing boards that can be reused. Boards that
cannot be reused must be removed.
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.
4 EGPUa/EGPUb/EXPUa/ A2 B2 B2 A2
EXPUb
5 Interface boards A3 B3 B3 A3
6 Cabinets A4 B4 B4 A4
----End
Incremental Algorithm
If an operator wants to keep the original equipment without large-scale modifications to the
legacy network, new boards are used only for newly added sites and carriers. If the new
quotation template does not support mixed insertion of boards and the frontline personnel
want to simplify operations, use the original quotation template and the incremental
algorithm.
The core idea is to reuse as much legacy equipment as possible. The purpose of mixed
insertion is to use boards of different specifications in the same logical or physical interface.
The procedure for the incremental algorithm is as follows:
Step 1 Fill in the Unistar calculation table with the quotation parameters of the new hardware version
after the capacity expansion. By doing this, you get the configuration required after the
capacity expansion. In the Dimension Calculator window, you can view the capacity after
the capacity expansion.
Step 2 Fill in the Unistar calculation table with the quotation parameters of the original hardware
version before the capacity expansion. By doing this, you can obtain the configurations of
each interface board before the capacity expansion. In the Dimension Calculator window,
you can view the capacity before the capacity expansion.
Step 3 Subtract the hardware support capability before the capacity expansion from the capacity
required after the expansion. By doing this, you can obtain the capacity support capability
required for the expansion.
Generally, the traffic volume over the Gb interface is light. One pair of boards can cope even
during a capacity expansion. Therefore, set the capacity increase on the Gb interface to 0.
2 PDCH QTY A2 B2 B2 - A2
3 A CIC QTY A3 B3 B3 - A3
4 BHCA A5 B5 B5 - A5
5 Gb interface traffic A6 A6 B6 - A6
Hardwa Boards
re
Version
HW6910 SCUb, GCGa, GCUa, AOUc, UOIc, FG2c, GOUc, EGPUa, EXOUa, EOMUa,
R15 ESAUa, ENIUa, GCGb, GCUb, GOUe, GCUb, GCGb
HW6910 SCUb, AOUc, UOIc, FG2c, EGPUa, EXOUa, EOMUa, ESAUa, ENIUa,
R16 GCGb, GCUb, GOUe, SCUc
HW6910 SCUb, SCUc, AOUc, UOIc, FG2c, EGPUa, EGPUb, EXOUa, EOMUa,
R17 ESAUa, ENIUa, GCGb, GCUb, GOUe, and DEUa
The following table lists the number of components to be added to the BSC6900 UMTS that
adopts HW6910 R17 hardware for capacity expansion.
1 Cabinet A1 B1 B1 A1
2 MPS A2 B2 B2 A2
3 EPS A3 B3 B3 A3
4 Clock board A4 B4 B4 A4
5 Evolved General A5 B5 B5 A5
Processing Unit (for
Control Plane)
6 Evolved General A6 B6 B6 A6
Processing Unit for User
Plane
7 Interface boards A7 B7 B7 A7
NOTE
Configuration 1 1 1 2 1 6
(before capacity
expansion)
Configuration 2 1 1 4 2 6
(after capacity
expansion)
Number of 0 0 2 1 0
components to
be added
2. = 2.71828183
3. = Number of boards applied on the network x Annual damage rate of boards x
Replenishment period/365
a. The replenishment period is usually 60 days.
b. Quantity of boards applied on the network is the number of boards inserted in both
the active BSCs.
There are 1000 boards (BOM: 02319428) applied on the network.
c. The annual damage rates of boards are provided by the spare parts center. Each
board has its own annual damage rate.
For example, the annual damage rate of the board (BOM: 02319428) is 0.005000.
The value of the board (BOM: 02319428) is calculated as follows: = 1000 x 0.005000 x
60/365 = 0.8219178
According to the Poisson algorithm, the number of backup boards (BOM: 02319428) is 4.
6.2.3 Notes
The number of spare parts calculated using the Poisson algorithm satisfies only basic
requirements of the live network. If the operator requires the service level agreement (SLA),
persuade the operator to purchase Huawei spare parts management services (SPMSs).
7 Appendix
MR report/sub/BH 144
1. Table 7-2 provides the capacity of a BSC6910 GSM in Abis over TDM, A over TDM,
and Gb over IP modes.
Table 7-2 Capacity of a BSC6910 GSM in Abis over TDM, A over TDM, and Gb over IP
modes
Name Typical Configuration
Number of subracks 1
1. Table 7-3 provides the capacity of a BSC6910 GSM in Abis over TDM, A over IP, and
Gb over IP modes.
Table 7-3 Capacity of a BSC6910 GSM in Abis over TDM, A over IP, and Gb over IP modes
Name Typical Configuration
Number of subracks 1
1. Table 7-4 provides the capacity of a BSC6910 GSM in all-IP transmission mode.
Number of subracks 1
1. Table 7-5 provides the capacity of a BSC6910 GSM in all-IP transmission mode with
BSC Node Redundancy enabled.
Table 7-5 Capacity of a BSC6910 GSM in all-IP transmission mode with BSC Node
Redundancy
Name Typical Configuration
Number of subracks 1
Board usage
Each type of board on the BSC6910 has its specifications, which are calculated by
collectively considering the capacity on various aspects (including BHCA capacity, TRX
capacity, CIC capacity, and bandwidth capacity).
The specifications for a board indicate the capacity for a board running with long-term
stability. When a board is processing services, its bandwidth capacity, service parsing and
forwarding capacity, and signaling parsing and forwarding capacity must be taken into
consideration. Therefore, Huawei uses the board usage to represent the board capacity.
Board usage = Traffic volume on the BSC(BHCA and number of TRXs)/Maximum board
specification
For example:
The specification of the GOUe board over the A interface is 23,040 CICs, and the number of
serving CICs is 10,000. Therefore, the board usage is 43.4% (10,000/23,040 x 100%).
The capacity under UMTS BSC6910 typical configurations in the high-PS traffic model and
smartphone traffic model are described as follows:
1. High-PS traffic model
Handover 8 N/A
times per CS
call (SHO)
(times/call)
Handover 5 N/A
times per PS
call (SHO)
(times/call)
Iur-to-Iub 8% N/A
traffic ratio
The following table lists the typical capacity of the BSC6910 UMTS configured with
HW6910 R17 under high-PS traffic model.
Table 7-8 Typical capacity of the BSC6910 UMTS under high-PS traffic model
(HW6910 R17)
Number CS PS BHCA Number Numbe Number
of Service Service (k) of Active r of of
Subscrib Capacit Capacity Users Online Subrack
ers y (Iub UL Users Combin
Support (Erlang +DL) ation
ed ) (Mbit/s)
NOTE
l The CS voice service capacity, PS service capacity, and BHCA can reach the maximum at the
same time.
l The number of on-net users indicates the number of users who have accessed a UMTS
network within a busy hour.
l The number of active users indicates the total number of users who are in the CELL_DCH and
CELL_FACH states.
l The number of online users indicates the total number of users who are in the CELL_DCH,
CELL_FACH, CELL_PCH, and URA_PCH states.
The following figure shows the BSC6910 typical configuration (1 MPS + 2 EPSs) under
high-PS traffic model.
The following figure shows the BSC6910 typical configuration (1 MPS + 5 EPSs) under
high-PS traffic model.
The following table lists the typical capacity of the BSC6910 UMTS configured with
HW6910 R17 under smartphone traffic model.
Table 7-10 Typical capacity of the BSC6910 UMTS under smartphone traffic model
(HW6910 R17)
Number CS PS BHCA (k) Numbe Numbe Numbe
of Voice Service r of r of r of
Subscribe Service Capacit Active Online Subrac
rs Capacity y (Iub Users Users k
Supporte (Erlang) UL Combi
d +DL) nation
(Mbit/s
)
NOTE
l The CS voice service capacity, PS service capacity, and BHCA can reach the maximum at the
same time.
l The number of on-net users indicates the number of users who have accessed a UMTS
network within a busy hour.
l The number of active users indicates the total number of users who are in the CELL_DCH and
CELL_FACH states.
l The number of online users indicates the total number of users who are in the CELL_DCH,
CELL_FACH, CELL_PCH, and URA_PCH states.
The following figure shows the BSC6910 typical configuration (1 MPS + 2 EPSs) under
smartphone traffic model.
The following figure shows the BSC6910 typical configuration (1 MPS + 5 EPSs) under
smartphone traffic model.
BH busy hour
CN core network
CP Control Plane
UP User Plane