Professional Documents
Culture Documents
Configuration
Principle(Global)
(BSC/RNC by kandasami)
1
Revisions
Date Subject Revision Created By
12/01/2016 SRAN10.1&GBSS17.1&RAN Draft V1.0 Kandasami
17.1 BSC6910
2
Contents
1.Introduction.
2.Application Overview.
3.Product Configurations.
4. Interface boards
5. Hardware Expansion and Upgrade Configurations
6 Spare parts and Configuration
7. Appendix
8.Acronyms and Abbreviations
3
01-Introduction of BSC6910 for VHA
1.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 (GO) mode and functions as a GSM BSC.
l A BSC6910 UMTS works in UMTS Only (UO) 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 describes the version differences between HW6910 R15 and later versions.
Table 2-1 Version differences between HW6910 R15 and later versions
5
Hardware Version
QM1D00EOM EOMU Evolved Operation and Provides the GSM & UMTS
U00 a Maintenance Unit evolved operation
and maintenance
function.
7
Model Name Description Function Application
Scenario
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.
Notes:
A BSC6900 cannot be upgraded to the BSC6910 by upgrading the software.
New software versions are compatible with old hardware versions. For
example, RAN17 software versions can work with HW6910 R15, HW6910
R16 and HW6910 R17 hardware version.
9
2.Application Overview
1
0
Figure 2-2 BSC6910 configurations (front view and rear view)
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 that can be
GSM (1 EPS): configured across cabinets: 2 EPSs):
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
Item Value
Power input -48 V DC power supply (Each subrack requires four 100 A
inputs.)
Power range 57 V to 40 V
Power consumption of The power consumption should be equal to or less than 7100 W
a single cabinet to reduce the impact of cabinet heat dissipation on the equipment
room. The practical power consumption of a cabinet can reach
12000 W.
NOTE
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:
3.1.3 Subracks
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
boards (logical function: RMP), which are not housed in the EPS.
The following table lists fixed boards in the BSC6910.
Table 3-3 Fixed board configurations
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
Cabinet power consumption calculation
The maximum power supply of a subrack is 4000 W. The maximum power consumption of a
cabinet is 7100 W.
For the calculation formula, see the following attachment.
BSC_Power_Consumption_Tool.xls
NOTE
l Average power consumption (Pavg) is the estimated value in a typical operating environment. The
maximum power consumption mentioned in hardware description is obtained when all devices on
boards are full-loaded. This maximum power consumption will not be obtained under the actual
system running conditions. Therefore, Pavg is provided for power consumptioncalculation.
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 adjustmentupon
future capacity expansion.
l Maximum cabinet power consumption is 7100 W which is the upper limit of the heat dissipation
capability in the equipment room and obtained based on survey and research. Therefore, the
maximum cabinet power consumption is not 12,000W.
3.1.4 License
Table 4-5 Hardware capacity licenses for BSC6910 V100R017C10
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.
Service Processing Modules
The BSC6900 calculates the numbers of CP boards (XPUa and XPUb) based on either the number
of planned TRXs or the BHCA. The numbers of PS UP boards (DPUd and DPUg) are calculated
based on the number of planned PDCHs. The numbers of CS UP boards (DPUc and DPUf) are
calculated based on the predicted traffic.
For the BSC6910, the CP board and UP board are integrated on the GCUP board. To calculate the
number of GCUP boards, divide the site specifications and the predicted specifications separately
by the number of TRXs, number of PDCHs, BHCA, or traffic. The maximum number among the
obtained four numbers is the number of GCUP boards. The number of standby GCUP boards can
be manually configured (recommended redundancy mode: N+1). By default, no standby GCUP
board is configured. A minimum of two GCPU boards are configured.
Item Value Description
TRX 1000 NA
(TRXNoPerEGPU)
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.
2. 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.
3. Calculating the number of required EGPU based on the number of PS user-plane PDCHs:
Maximum number of activated PDCHs (TotalPDCH): calculated based on number of users and traffic model
5. Calculating the number of required EGPU boards based on the number of cells:
7. 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.
The BSC6910 supports FE electrical ports, GE optical ports, and 10GE optical ports
in IP networking, and supports channelized STM-1 ports in TDM networking.
By default, the following boards are delivered: FG2c, GOUe, EXOUa, and POUc.
Table 4-1 Interface board specifications
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. GBSS17.1
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.
1. Select the types of interface boards based on the network plan. The number of required
Abis interface boards is calculated based on either the service capability (number of
supported TRXs) or number of required ports. Use the larger of the two values to
determine the number of required Abis interface boards.
To determine the number of Abis interface boards, you can use the following formula:
number of Abis interface boards = 2 x Roundup (Max (Number of TRXs in a
transmission mode/Number of TRXs supported by the interface board, Number of ports
in a transmission mode/Number of ports supported by the interface boards), 0)
Abis interface configuration precautions:
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.
The POUc must meet the following requirements:
Number of TRXs supported by the POUc x (Average number of Erlangs per TRX + Average number of
PDCHs per TRX x Number of timeslots required for PS transmission) 16,384
The following table lists the number of timeslots required for PS transmission.
For example:
a. 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.
b. 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.
c. 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.
d. If the BSC provides IP over E1 links, the POUc board must be configured in the
BSC6910.
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.
To calculate the total interface boards when multiple interfaces share one interface board use the
following formulas:
Number of Interface boards = 2 x Roundup (Number of Abis Interface boards + Number of A Interface
boards + Number of Gb Interface boards, 0)
Number of Abis Interface boards = Max (Number of TRXs in a transmission mode/Number of TRXs
supported by the interface board, Number of ports in a transmission mode/Number of ports supported by
the interface boards)
Number of Gb Interface boards = GbThroughput/BSC data flow over Gb interface supported by the
interface board
In the BSC6910, EGPUa/EXPUa boards work in intra-BSC resource pool mode. Services of TRXs
connected to interface boards in a subrack are preferentially processed by service processing units in the
same subrack. If the resources required by a subrack exceed the specified threshold, load sharing is
implemented between subracks of the BSC. The purpose is to reduce resources used for inter-subrack
switching. Boards are configured according to the following principles:
1. Ensure that interface boards and processing boards are distributed evenly among subracks. This
reduces the consumption of processor resources and switching resources by inter-subrack switching.
Interface boards can be configured only in rear slots, and service processing units can be configured
in non-fixed slots. It is recommended that service processing units be configured in front slots.
Under a BSC, A interface boards, Abis interface boards, and service processing units must be
distributed as evenly as possible among subracks. Configuring the same type of board in the same
subrack lowers system reliability.
2. You do not have to specify the subrack and slot number for configuring M3UA links. The number
of M3UA links are greater than or equal to (recommended) the number of EGPUa/EXPUa boards
(logical function: GCUP).
3. General principles for board configuration: The basic principles during network plan and design do
not change by devices. The basic principles include but are not limited to the following:
Each LAC can receive more than 120 paging requests per second over the Um interface when a
single CCCH is configured. Therefore, it is recommended that 512 TRXs for each LAC be
configured in the case of a single CCCH. The TRX number can be adjusted by traffic.
Consecutive PDCHs are configured so that uses can use multiple consecutive slots.
Other basic principles during GSM network plan.
4. General principles for slot restrictions: The GCUb/GCGb, EOMUa, SCUb/SCUc,
EGPUa/EXPUa (logical function type: RMP) boards are inserted in fixed slots. The interface
boards and service boards can be inserted in slots within a specific range. For details, see the
descriptions about subrack configurations.
Auxiliary Material Configurations
Operator provides the network requirements which must include the information contained in the
following figure. Here is an example.
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
Item Name Specifications
7 PDCH QTY A7
4.3.1 Cabinets
The following table describes cabinet
configurations.
A BSC6910 can be configured with a maximum of two cabinets. A maximum of three subracks can be
configured in each cabinet. The number of cabinets required is calculated as follows:
New deployment
Number of cabinets = MAX (Number of cabinets_1, Number of cabinets_2) Number of
1.
The power consumption of a single subrack on the BSC6910 is 4000 W. The maximum power consumption
of a single cabinet on the BSC6910 is 7100 W.
For the calculation formula, see the following attachment:
BSC_Power_Consumption_Tool.xls
Configuration Principles for Interface Boards and Service
Boards
Service boards and interface boards must be distributed evenly among subracks to reduce the
CPU and swapping resources consumed during inter-subrack swaps and avoid traffic volume
restrictions caused by limited inter-subrack bandwidths. For example, if there are 12 EGPU
boards (for the control plane), 9 EGPU boards (for the user plane), 3 EXOUa boards, and 3
subracks, then is recommended that 4 EGPU boards (for control plane), 3 EGPU boards (for
the user plane), and 1 EXOUa board be configured in each subrack.
Iu interface boards in each subrack form a resource pool. A route to the core network is
configured on each Iu interface board.
Iub interface boards in each subrack form a transmission resource pool. Routes to all the
NodeBs are configured on each Iub interface board.
EGPUa Evolved General Processing Unit N+1 backup in resource pool mode Any universal slots
(logical function:
GCUP/UCUP/ UMSP)
EXOUa Evolved 10GE Optical interface Active/standby mode Any universal slots
Unit
ENIUa Evolved Network Intelligence Unit REV:a N+1 backup in resource pool mode Any universal slots
SCUb GE Switching network and Control Unit REV:b Active/standby mode Fixed slots
SCUc GE Switching Network and Control Unit REV:c Active/standby mode Fixed slots
FG2c IP Interface Unit (12 FE/4 GE, Electric) Active/standby mode Any universal slots
AOUc ATM Interface Unit (4 STM-1, Active/standby mode Of the two boards in each pair,
Channelized) one must be installed in an odd-
numbered slot and the other in
an adjacent even- numbered
slot.
UOIc ATM Interface Unit (8 STM-1, Active/standby mode Of the two boards in each pair,
Unchannelized) one must be installed in an odd-
numbered slot and the other in
an adjacent even- numbered
slot.
GCUb General Clock Unit Active/standby mode Fixed slots
DEUa Data Enhancement Processing Unit N+1 backup in resource pool mode Any universal slots
Restrictions on Inter-Subrack Switching
A pair of active and standby SCUb boards can process data at 40 Gbit/s on the
physical layer. The SCUb boards in various subracks are connected in chain
mode. If either of the active and standby board becomes faulty, the processing
capability is halved.
A pair of active and standby SCUc boards can process data at 320 Gbit/s on
the physical layer. The SCUc boards in various subracks are connected in
chain mode. If either of the active and standby board becomes faulty, the
processing capability is halved.
If the service boards are not evenly configured among the subracks or services are
not evenly deployed among the subracks, the volume of inter-subrack data flows
may sharply increase. Once the volume exceeds the capacity, services are
interrupted. Therefore, all types of service processing boards (including EGPUa
and ENIUa) and interface boards must be evenly configured among subracks.
The user-plane capacity of each subrack should be similar.
For example, if there are 15 EGPUa boards, 3 ENIUa boards,2 ESAUa boards, 8
pairs of Iub GOUe boards, 6 Iu GOUe boards, and 6 subracks, Complying with
the even-configuration principle, configure data as follows: Configure 2 or 3
EGPUa boards, 0 or 1 ENIUa board for each subrack.Configure 1 or 2 pairs of
Iub GOUe boards and 1 pair of Iu GOUe boards.
Configure more Iub GOUe boards and ENIUa boards in the subrack with more
EGPU boards. ESAUa boards are configured in reserved slots in MPS. The
following table lists a recommended configuration.
The operator provides the network capacity requirement which should include the
information listed in Table 4-24.
Totalsubscribers 800,000
TotalNodeBs 600
Totalcells 3000
Voice traffic per CS voice subscriber in BH (Erlang) 0.02
CS voice call duration(sec.) 75
Handover times per CS call 8
CS voice call per subscriber per BH 0.96
PS call per subscriber per BH 2
Proportion of SHO for CS call 0.3
Handover times per PS call 5
Mean holding time (MHT) in DCH/H/FACH state per PS 52
call(sec)
5.1 BSC6910 G S M
You can use either of or both of the two methods based on the network traffic model and traffic volume
requirements.
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/EXPUa, DPUf, FG2c, GOUc, GOUe, EXOUa, and POUc. The
BSC6910 does not support other BSC6900 boards.
In A over IP networking, the EGPUa/EXPUa 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/EXPUa 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 interfacessupport only IP transmission mode.
Before hardware capacity expansion, sufficient hardware capacity licenses for "BSC HW TRX Capacity (per
TRX)" and "BSC HW PDCH Capacity (per PDCH)" must be obtained. The number of licenses to be increased
depends on the difference in TRX or PDCH capacity before and after capacityexpansion.
Total Replacement
An operator may want to increase equipment integration and achieve a larger capacity with existing cabinets and
subracks. In this case, a total replacement is recommended. In a total replacement, the capacity is considered first.
The Unistar quotation template is used to work out a BSC equipment list based on the specifications of the new
hardware version. The boards required for the capacity expansion are determined through a comparison with
existing boards that can be reused. Boards that cannot be reused must be removed.
The components required in the capacity expansion are the components after the capacity expansion minus those
before the capacity expansion.
Hardwa Boards
re
Version
HW6910 SCUb, GCGa, GCUa, AOUc, UOIc, FG2c, GOUc, EGPUa, EXOUa, EOMUa, ESAUa, ENIUa,
R15 GCGb, GCUb, GOUe, GCUb, GCGb
HW6910 SCUb, AOUc, UOIc, FG2c, EGPUa, EXOUa, EOMUa, ESAUa, ENIUa, GCGb, GCUb,
R16 GOUe, SCUc
HW6910 SCUb, SCUc, AOUc, UOIc, FG2c, EGPUa, EXOUa, EOMUa, ESAUa, ENIUa, GCGb,
R17 GCUb, GOUe, DEUa
The following table lists the number of components to be added to the BSC6900 UMTS that adopts HW6910 R17
hardware for capacity expansion.
NOTE
According to the Poisson algorithm, the number of backup boards (BOM: 02319428) is 4.
2. Percentage Algorithm
If the operator specifies the percentage algorithm, use the percentage algorithm to calculate
the number of spare parts.
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
Parameter Value
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
2. 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
Maximum number of TRXs 3000
Maximum number of equivalent BHCA 6500
(k)
Maximum traffic volume (Erlang) 18750
Maximum number of activated PDCHs 12000
(MCS-9)
3. Table 7-4 provides the capacity of a BSC6910 GSM in all-IP transmission mode.
Number of subracks 1
4. 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
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.
BH busy hour
CN core network
CP Control Plane
UP User Plane