Professional Documents
Culture Documents
SRAN12.1
Issue 01
Date 2017-03-10
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
2 Overview......................................................................................................................................... 3
2.1 Introduction.................................................................................................................................................................... 3
2.2 Benefits........................................................................................................................................................................... 4
13 Related Features.........................................................................................................................50
13.1 Prerequisite Features...................................................................................................................................................50
13.2 Mutually Exclusive Features...................................................................................................................................... 50
13.3 Impacted Features.......................................................................................................................................................51
14 Network Impact......................................................................................................................... 52
14.1 System Capacity......................................................................................................................................................... 52
14.2 Network Performance.................................................................................................................................................52
14.3 Reliability................................................................................................................................................................... 52
15 Engineering Guidelines........................................................................................................... 54
15.1 When to Use............................................................................................................................................................... 55
15.2 Required Information................................................................................................................................................. 55
15.3 Network Planning....................................................................................................................................................... 55
15.4 Deployment................................................................................................................................................................ 56
15.4.1 Requirements........................................................................................................................................................... 56
15.4.2 Data Preparation...................................................................................................................................................... 56
15.4.3 Activation................................................................................................................................................................ 59
15.4.4 Activation Observation............................................................................................................................................62
15.4.5 Deactivation.............................................................................................................................................................63
15.4.6 Reconfiguration....................................................................................................................................................... 63
15.5 Performance Monitoring.............................................................................................................................................64
15.6 Parameter Optimization.............................................................................................................................................. 64
15.7 Possible Issues............................................................................................................................................................ 64
15.7.1 Related Alarms........................................................................................................................................................ 64
15.7.2 MML Commands for Maintenance......................................................................................................................... 67
16 Parameters................................................................................................................................... 69
17 Counters...................................................................................................................................... 85
18 Glossary....................................................................................................................................... 86
19 Reference Documents............................................................................................................... 87
1.1 Scope
This document describes the working principles and engineering guidelines of the CPRI
MUX feature.
This document applies to macro base stations, including BTS3900, BTS3900L, BTS3900A,
BTS3900AL, BTS3900C, and DBS3900.
Any parameters, alarms, counters, or managed objects (MOs) described herein apply only to
the corresponding software release. For future software releases, refer to the corresponding
updated product documentation.
Any "LTE" in this document refers to LTE FDD, and "eNodeB" refers to LTE FDD eNodeB.
In addition, "G", "U", and "L" in RAT acronyms refer to GSM, UMTS, and LTE FDD,
respectively.
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
SRAN12.1 01 (2017-03-10)
This issue does not include any changes.
2 Overview
2.1 Introduction
In the CPRI MUX feature, multiple modes use a common public radio interface (CPRI) link
to transmit data.
NOTE
l (1)
UBBP boards are added in SRAN9.0, which support multimode co-BBP. Therefore, a UBBP
board can serve as both the converging board and converged board.
l Only multimode RF modules support CPRI MUX. Single-mode RF modules do not support CPRI
MUX.
l The modes of RF modules in the figures at chapters 4, 5, and 6 refer to the working modes of RF
modules, not the supporting modes of RF modules.
2.2 Benefits
This feature provides the following benefits:
l Reduced cable purchase, installation, and maintenance costs for newly deployed
multimode base stations: Multiple modes can use a CPRI link to transmit data, and
therefore the number of required optical modules and fiber optic cables decreases
considerably.
l Lower engineering costs and shorter service interruption duration in refarming scenarios:
If a multimode RF module uses a single CPRI cable, newly deployed modes can share
the module and the cable after refarming.
l Guaranteed coverage for cascaded multimode RF modules: CPRI MUX allows
multimode RF modules to be cascaded to ensure coverage along highways and railways.
From SRAN10.0 onwards, BBUs that support CPRI MUX include the BBU3900, BBU3910,
and BBU3910A.
l Section 3.1 BBU3900 Boards That Support CPRI MUX describes the BBU3900
boards that support CPRI MUX.
l Section 3.2 BBU3910 Boards That Support CPRI MUX describes the BBU3910
boards that support CPRI MUX.
l Section 3.3 BBU3910As That Support CPRI MUX describes the BBU3910A that
supports CPRI MUX.
Table 3-1 BBU3900 boards that support the CPRI MUX feature in a separate-MPT
multimode base station and constraints on the slots of the converging and converged boards
In co-MPT scenarios, any one or multiple modes of GSM, UMTS, and LTE can serve as the
converging party or converged party. Table 3-2 lists BBU3900 boards that support the CPRI
MUX feature in a co-MPT multimode base station and constraints on the slots of the
converging and converged boards.
Table 3-2 BBU3900 boards that support the CPRI MUX feature in a co-MPT multimode base
station and constraints on networking
UBBP_G/L Slot 1, 2, or
3
UBBP_GU/GL/UL/G Slot 2 or 3
UL
UBBP_G/U/L/GU/G Slot 2 or 3
L/UL/GUL
NOTE
l (1)If a baseband processing board is named UBBP_A/B/C, "A", "B", "C" indicates the mode whose
baseband resources are configured on this board, baseband resources of different modes are isolated by
"/". For example, UBBP_G/U/GU indicates a UBBP configured with GSM baseband resources, UMTS
baseband resources, or GSM and UMTS baseband resources (GU co-BBP).
l (2) When multiple modes are deployed on a UBBP, the mode of data transmitted through CPRI ports on
this board can be one of or all of the deployed modes. For example, the mode of data transmitted through
the CPRI ports on a UBBP_GUL can be UMTS or UL.
l (3) A
UBBP_Ux indicates that this UBBP serves UMTS and other modes; a UBBP_Gx indicates that this
UBBP serves GSM and other modes.
l (4)If the data rate of a CPRI port on a UBRIb board is greater than 4.9 Gbit/s, the port can carry services
of only one RAT in versions earlier than SRAN11.1 and carry services of two RATs in SRAN11.1 and
later versions.
l (5)
If GSM baseband signals are processed by RRUs, the signals do not need to be processed on the
baseband processing board (UBBP_Gx) in the BBU.
l (6) Whena UBRIb serves as the converging board in GUL CPRI MUX, cells served by the converged UO
and LO modes must be configured on the specified baseband equipment group, and such a baseband
equipment group must be configured with single-mode baseband processing boards.
l (7) If GSM baseband signals are not processed by RF modules, the signals are processed on the UBBP_Gx
Table 3-3 BBU3910 boards that support the CPRI MUX feature and the slot assignment for
separate-MPT multimode base stations
Mode on Converging Slot of the Converged Slot of the
the CPRI Board Converging Board Converged Board
Port Board
NOTE
In co-MPT scenarios, any one or multiple modes of GSM, UMTS, and LTE can serve as the
converging party or converged party. Table 3-4 lists the BBU3910 boards that support the
CPRI MUX feature and the slot assignment.
Table 3-4 BBU3910 boards that support the CPRI MUX feature and the slot assignment for
co-MPT multimode base stations
Mode on the Converging Board Slot of the Converging Board
CPRI Port
GU UBRIb or Slot 0, 1, 2, 3, 4, or 5
UBBP_G/U/L/GU/GL/UL/GU
GL L
UL
GUL
NOTE
If the data rate of a CPRI port on a UBRIb board is greater than 4.9 Gbit/s, the port can carry services of only
one RAT in versions earlier than SRAN11.1; the port can carry services of two RATs in SRAN11.1 and later
versions.
5.1.1 Constraints
The converging and converged parties in the CPRI MUX feature must share one BBU.
Figure 5-1 UL CPRI MUX in co-MPT scenarios when UMTS serves as the converging
party
l Scenario 2: A co-BBP board serves as the converging board. The following conditions
must be met:
– A UBBP_GU/GL/UL/GUL serves as the converging board and is configured in slot
2 or 3.
– When a UBBP_GU serves as the converging board in UL CPRI MUX, UMTS is
the converging party, and LTE is the converged party, the LBBPc cannot serve as
the converged board.
– When a UBBP_GL serves as the converging board in UL CPRI MUX, LTE is the
converging party and UMTS is the converged party. A WBBPf or UBBP_Ux is
configured in slot 2 or 3.
– When a UBBP_UL serves as the converging board in UL CPRI MUX, the
UBBP_UL can provide CPRI ports for transmitting UL data.
Figure 5-2 shows UL CPRI MUX where the UBBP_UL is configured in slot 3.
Figure 5-3 GU CPRI MUX in co-MPT scenarios when GSM serves as the converging
party, a UBRIb serves as the converging board, and GSM baseband signals are processed
by RF modules
Figure 5-4 shows GU CPRI MUX where UMTS serves as the converging party, a
UBBP_U serves as the converging board, and GSM baseband signals are processed by
RF modules.
Figure 5-4 GU CPRI MUX in co-MPT scenarios when UMTS serves as the converging
party, a UBBP_U serves as the converging board, and GSM baseband signals are
processed by RF modules
l Scenario 2: A co-BBP board serves as the converging board. The following conditions
must be met:
– A UBBP_GU/GL/UL/GUL serves as the converging board and is configured in slot
2 or 3.
– When a UBBP_GL serves as the converging board in GU CPRI MUX, GSM is the
converging party and UMTS is the converged party. A WBBPf or UBBP_Ux is
configured in slot 2 or 3.
– When a UBBP_UL serves as the converging board in GU CPRI MUX, UMTS is
the converging party and GSM is the converged party. If GSM baseband signals are
processed by RF modules, the GSM signals can be converged by a UBBP_UL, so a
GSM baseband processing board or interface board is not required. If GSM
baseband signals are not processed by RF modules, a UBBP_Gx is configured in
slot 1, 2 or 3.
– When a UBBP_GU/GUL serves as the converging board in GU CPRI MUX, a
single board can provide CPRI ports for transmitting GU data.
Figure 5-5 shows GU CPRI MUX where the UBBP_GU is configured in slot 3.
Figure 5-6 GL CPRI MUX in co-MPT scenarios when GSM serves as the converging
party, a UBRIb serves as the converging board, and GSM baseband signals are processed
by RF modules
Figure 5-7 shows GL CPRI MUX where LTE serves as the converging party, a UBBP_L
serves as the converging board, and GSM baseband signals are processed by RF
modules.
Figure 5-7 GL CPRI MUX in co-MPT scenarios when LTE serves as the converging
party, a UBBP_L serves as the converging board, and GSM baseband signals are
processed by RF modules
l Scenario 2: A co-BBP board serves as the converging board. The following conditions
must be met:
– A UBBP_GU/GL/UL/GUL serves as the converging board and is configured in slot
2 or 3.
– When a UBBP_GU serves as the converging board in GL CPRI MUX, GSM is the
converging party and LTE is the converged party. In this case, the LBBPc cannot
serve as the converged board.
– When a UBBP_UL serves as the converging board in GL CPRI MUX, LTE is the
converging party and GSM is the converged party. If GSM baseband signals are
processed by RF modules, the GSM signals can be converged by a UBBP_UL, so a
GSM baseband processing board or interface board is not required. If GSM
baseband signals are not processed by RF modules, a UBBP_Gx is configured in
slot 1, 2 or 3.
– When a UBBP_GL/GUL serves as the converging board in GL CPRI MUX, a
single board can provide CPRI ports for transmitting GL data.
Figure 5-8 shows GL CPRI MUX where the UBBP_GL is configured in slot 3.
l (1)In this scenario, cells served by the converged UO and LO modes must be configured on the
specified baseband equipment group, and such a baseband equipment group must be
configured with single-mode baseband processing boards.
l (2) WBBP refers to WBBPa, WBBPb, WBBPd, or WBBPf.
Figure 5-9 shows GUL CPRI MUX where GSM serves as the converging party, a
UBRIb serves as the converging board, and GSM baseband signals are processed by RF
modules.
Figure 5-9 GUL CPRI MUX in co-MPT scenarios when GSM serves as the converging
party, a UBRIb serves as the converging board, and GSM baseband signals are processed
by RF modules
Figure 5-10 shows GUL CPRI MUX where UMTS serves as the converging party and
GSM baseband signals are processed by RF modules.
Figure 5-10 GUL CPRI MUX in co-MPT scenarios where UMTS serves as the
converging party and GSM baseband signals are processed by RF modules
l Scenario 2: A co-BBP board serves as the converging board. The following conditions
must be met:
– A UBBP_GU/GL/UL/GUL serves as the converging board and is configured in slot
2 or 3.
– A WBBPf or UBBP_Ux is configured in slot 2 or 3.
– When a UBBP_GU serves as the converging board in GUL CPRI MUX, GU is the
converging party, and LTE is the converged party. In this case, the LBBPc cannot
serve as the converged board.
– When a UBBP_GL serves as the converging board in GUL CPRI MUX, GL is the
converging party and UMTS is the converged party. A WBBPf or UBBP_Ux is
configured in slot 2 or 3.
– When a UBBP_UL serves as the converging board in GUL CPRI MUX, UL is the
converging party and GSM is the converged party. If GSM baseband signals are
processed by RF modules, the GSM signals can be converged by a UBBP_UL, so a
GSM baseband processing board or interface board is not required. If GSM
baseband signals are not processed by RF modules, a UBBP_Gx is configured in
slot 1, 2 or 3.
– When a UBBP_GUL serves as the converging board in GUL CPRI MUX, a single
board can provide CPRI ports for transmitting GUL data.
Figure 5-11 shows GUL CPRI MUX where UL serves as the converging party and GSM
baseband signals are processed by RF modules.
Figure 5-11 GUL CPRI MUX in co-MPT scenarios where UL serves as the converging
party and GSM baseband signals are processed by RF modules
Figure 5-12 shows GUL CPRI MUX where the UBBP_GUL is configured in slot 3.
Figure 5-12 GUL CPRI MUX in co-MPT scenarios with GUL co-BBP
5.2.1 Constraints
l The converging and converged parties in the CPRI MUX feature must share one BBU.
l Data convergence is allowed only between two modes in the same BBU. Each mode can
only converge data or have its data converged. Data can only be converged to one board
at a time.
l A BBU can provide a maximum of six CPRI ports for data convergence, and the CPRI
ports must be provided by a WBBPf, LBBPd, or UBBP_U/L that is installed in slot 2 or
slot 3.
Figure 5-13 UL CPRI MUX in separate-MPT scenarios when UMTS is the converging party
Figure 5-14 UL CPRI MUX in separate-MPT scenarios when LTE is the converging party
NOTICE
In this scenario, data from slot 6 can be converged to either slot 2 or 3, but cannot be
converged to both slots.
Figure 6-1 Co-MPT GU CPRI MUX where a UBRIb serves as the converging board
Figure 6-2 Co-MPT GU CPRI MUX where a UBBP_U serves as the converging board
Figure 6-3 Co-MPT GU CPRI MUX where a UBBP_GU serves as the converging board
UL CPRI MUX
BBU3910s support separate-MPT UL CPRI MUX when the following conditions are met:
A UBBP_U or UBBP_L serves as the converging or converged board and is installed in one
of slots 0 to 5.
In a BBU3910, one converged board can correspond to one or two converging boards. A
maximum of three pairs of one-to-one relationships or two pairs of one-to-two relationships
are supported.
Figure 6-5 shows an example of three pairs of one-to-one relationships with LTE as the
converging party.
Figure 6-5 Separate-MPT UL CPRI MUX with LTE as the converging party (three pairs of
one-to-one relationships)
In the preceding figure, boards in slots 0 and 1 are converged and converging boards,
respectively. These two boards form a group. Similarly, boards in slots 2 and 3 form a group,
and boards in slots 4 and 5 form a group.
Figure 6-6 shows an example of two pairs of one-to-two relationships with LTE as the
converging party.
Figure 6-6 Separate-MPT UL CPRI MUX with LTE as the converging party (two pairs of
one-to-two relationships)
In the preceding figure, the board in slot 0 is a converged board, and boards in slots 4 and 5
are converging boards. These three boards form a group. Similarly, boards in slots 1, 2, and 3
form a group.
In a chain topology with CPRI MUX, configurations of a BBU, including the BBU3900,
BBU3910, and BBU3910A, are the same as the configurations of the BBU in a star topology.
On the RRU side, multimode RF modules working in the same or different modes can be
cascaded on one CPRI link. Intra-mode cascading is recommended and inter-mode cascading
is provided for use in specific scenarios.
NOTE
In a chain topology with CPRI MUX, preferentially activate GSM cells served by the RF modules that
can process GSM signals and are configured at the upper levels on a chain, that is close to a baseband
processing board.
l Intra-mode cascading: All cascaded multimode RF modules must be configured with the
same mode and work in the same mode. Figure 8-1 shows GU CPRI MUX where
UMTS serves as the converging party, the UBBP_U serves as the converging board,
GSM baseband signals are processed by RF modules, and a BBU3900 is used.
l Inter-mode cascading: Cascaded multimode RF modules can work in different modes.
Inter-mode cascading is implemented in the following scenarios:
– Scenario 1: GSM is contained in the cascading chain in co-MPT CPRI MUX. The
working modes of a multimode RF module in an inter-mode RF module cascading
chain contain GSM. For example, the working mode may be GO, GU, GL, or GUL.
In this scenario, all RF modules in the cascading chain must be multimode RF
modules that support GSM. That is, all RF modules must support GU, GL, or GUL.
Figure 8-2 shows co-MPT GU CPRI MUX where UMTS serves as the converging
party, the UBBP_U serves as the converging board, GSM baseband signals are
processed by RF modules, and a BBU3900 is used. The "UO Radio Unit" in this
figure is working in UO, but it is a multimode RF module that supports GSM. That
is, it supports GU or GUL.
– Scenario 2: GSM is not contained in the cascading chain in co-MPT CPRI MUX.
The working modes of all multimode RF modules in an inter-RAT RRU cascading
chain do not contain GSM. These multimode RF modules work in UO, LO, or UL.
In this scenario, cascaded multimode RF modules can be GU, GL, UL, or GUL RF
modules. Figure 8-3 shows co-MPT UL CPRI MUX where UMTS serves as the
converging party and a BBU3900 is used.
– Scenario 3: In separate-MPT CPRI MUX, the multimode RF modules in the inter-
RAT hybrid cascading chain can work in one or two modes, but all multimode RF
modules must support both the converging and converged parties. For example, in
separate-MPT GU CPRI MUX, the multimode RF modules can work in GO, UO,
or GU, but these modules must support GU or GUL, as shown in Figure 8-4.
NOTE
Figure 8-1 Co-MPT GU CPRI MUX using intra-mode cascading where a BBU3900 is used,
UMTS serves as the converging party, the UBBP_U serves as the converging board, and GSM
baseband signals are processed by RF modules
Figure 8-2 Co-MPT GU CPRI MUX using inter-mode cascading where a BBU3900 is used,
UMTS serves as the converging party, the UBBP_U serves as the converging board, and GSM
baseband signals are processed by RF modules
Figure 8-3 Co-MPT UL CPRI MUX using inter-mode cascading where a BBU3900 is used
and UMTS serves as the converging party
Figure 8-4 Separate-MPT GU CPRI MUX using inter-mode cascading where a BBU3900 is
used and UMTS serves as the converging party
Figure 9-1 Co-MPT UL CPRI MUX where a UBBPei_L serves as the converging board
NOTE
l The number of XCI ports (one or two) depends on the service bandwidth carried by RRUs
connecting to the RMU.
l When a UBBPei board is used as a UL dual-mode board, block and unblock the CPRI ports in case
of insufficient bandwidth of CPRI links if the board supports inter-board interference cancellation.
l The converging and converged parties in the CPRI MUX feature must share one BBU.
l One mode can only converge data or have its data converged. Data can only be
converged to one board at a time.
l Only the UBBPei board can serve as the converging board. It can be configured only in
the BBU3910 and in slots 0 to 5.
l In separate-MPT UL scenarios, the converged board must be a UBBPd or UBBPe.
l Each BBU can provide a maximum of eight XCI ports.
Figure 9-2 shows separate-MPT UL CPRI MUX where LTE serves as the converging party.
Figure 9-2 Separate-MPT UL CPRI MUX where LTE serves as the converging party
NOTE
When one XCI port cannot provide sufficient physical bandwidth required by all cells carried by the
connected RRUs, two XCI ports can be used to connect the RMU3900A. The two XCI ports work in a
load sharing mode. When one XCI port becomes faulty, the O&M links automatically switch over to the
other XCI link. If the other XCI link has sufficient physical bandwidth, the service data can also be
switched over to the other XCI link.
In co-MPT scenarios, if two CPRI links on an RF module carry the data of two or more
modes, this network topology is called the multimode load sharing topology. If each CPRI
link in the multimode load sharing topology can transmit data of only one mode, the CPRI
MUX feature is not required.
l For details about this network topology, see RRU/RFU/AAU Topologies > Load-
Sharing Topology > Multimode Load-Sharing Topology in RF Unit and Topology
Management Feature Parameter Description.
l If a CPRI link in the multimode load sharing topology needs to transmit data of multiple
modes, the CPRI MUX feature is required. In this scenario, only GUL RF modules
support CPRI MUX with multimode load sharing at present. Two CPRI links carry GU
+L data, with one link carrying GU data and the other carrying LTE data, as shown in
Figure 10-1.
NOTICE
l In the multimode load sharing topology, two CPRI links of an RF module must be
connected to two baseband processing boards or two interface boards of different modes.
In other words, only a BBU3900 or a BBU3910 supports multimode load sharing
topology.
l In the multimode load sharing topology, the number of LTE cells cannot exceed the
maximum number of LTE cells supported by one CPRI link, which depends on the CPRI
port rate. For the number of LTE cells supported by different CPRI port rates, see "CPRI
Specifications" in Technical Specifications of the eNodeB FDD > Technical
Specifications of the BBU3900 and BBU3910 > Product Specifications in 3900 Series
Base Station Technical Description.
l If a UBBP is used in the multimode load sharing topology, the UBBP must have been
configured with baseband resources of the mode served by this board. Otherwise, carriers
cannot be successfully allocated to the CPRI ports on this UBBP.
l In multimode load sharing, if a CPRI port is faulty or the board carrying this CPRI port is
faulty, services of certain modes cannot be established. After the fault is cleared, services
of all modes will recover.
In a triple-mode dual-star topology, two modes use CPRI MUX and form a separate-MPT
dual-star topology with the third mode. This topology applies only to a BBU3900 and a
BBU3910. Note that the converging and converged parties in the CPRI MUX feature share
one BBU
NOTE
l CPRI link rate, maximum number of carriers supported by a CPRI link, and maximum number of
carriers supported by a board all refer to those of the converging party.
l Converging capabilities in the tables apply to common cells. For the impact of different features on
cell capacity, see the corresponding feature parameter description.
l When GSM baseband signals are processed by the baseband processing board, the tables list the
numbers of GSM TRXs supported when the antenna capability is 1T2R.
l The tables list the numbers of supported UMTS cells when the antenna capability is 1T2R.
l The tables list LTE-related capacity specifications when the antenna capability is 2T2R.
l The capabilities of a BBU3910A or a BBU3900/BBU3910 converging board cannot exceed the
maximum carrier/cell specifications of a site. For the maximum carrier/cell specifications of a site,
see Product Specifications > Technical Specifications of the BBU3900/BBU3910 or Technical
Specifications of the BBU3910A > Capacity Specifications in 3900 Series Base Station Technical
Description.
Table 12-1 CPRI line rates and the converging capabilities of the converging party in
multimode scenarios where CPRI MUX is used with a BBU3900 or a BBU3910
NOTE
l (1)
In separate-MPT GU or GL CPRI MUX where a BBU3910 is used, if the number of converging
ports is less than or equal to five, a single CPRI link can carry 32 GSM TRXs; if the number of
converging ports is six, a single CPRI link can only carry 24 GSM TRXs.
l When GSM baseband signals are processed by RF modules, the GSM capacity listed in the
preceding table is the number of GSM carriers in the time division multiplexing (TDM) transmission
mode when the maximum distance between the BBU and the RF module is 20 km.
In the IP over E1 and IP over FE transmission schemes, use capacity specifications in Table 12-1 if
these specifications do not exceed the maximum carrier specifications of a site; use the maximum
capacity specifications of a site if capacity specifications in Table 12-1 exceed the maximum
capacity specifications of a site.
l (2)
The specifications apply to scenarios where GSM baseband signals are processed by RF modules.
When GSM baseband signals are processed by baseband processing boards, a maximum of 72 GSM
TRXs can be supported by the boards.
l (3) In separate-MPT GU or GL CPRI MUX where a BBU3900 is used, when a WBBPf or an LBBPd
NOTICE
l The minimum CPRI line rate of the converging board is 2.5 Gbit/s.
Table 12-2 CPRI line rates and the converging capabilities of the converging party in
multimode scenarios where CPRI MUX is used with a BBU3910A
NOTE
The table lists the numbers of GSM TRXs in the IP over E1 and IP over FE transmission schemes when
the maximum distance between the BBU and the RF module is 20 km and the GSM baseband signals
are processed by RF modules.
Table 12-3 CPRI line rates and the converging capabilities of the converging party in
multimode scenarios where CPRI MUX is used with an RMU3900A
CPRI Line Rate 2.5 Gbit/s 4.9 Gbit/s 9.8 Gbit/s
Table 12-4 CPRI line rates and the converging capabilities of the converging party in
multimode scenarios where CPRI MUX is used on the XCI ports of a UBBPei board
CPRI Line Rate 9.8 Gbit/s 10.1 Gbit/s
NOTE
l On the UBBPei board, the XCI port rate can be either 9.8 Gbit/s or 10.1 Gbit/s.
l The minimum CPRI line rate of the converging board is 2.5 Gbit/s.
Capacity specifications for each mode with different configurations are calculated as follows:
l GSM:
– When GSM baseband signals are processed by RF modules, the numbers of GSM
TRXs are reduced by half if the following condition is met: 20 km < distance
between the BBU and the RF module ≤ 40 km.
l UMTS:
– The number of cells supported when the antenna capability is 1T2R is the same as
that supported when the antenna capability is 2T2R.
– The antenna capability is inversely proportional to the number of cells. For
example, the number of cells supported when the antenna capability is 1T2R is
twice that supported when the antenna capability is 2T4R.
l LTE:
– When LTE cells have the same antenna capability and CPRI line rate, the number of
cells supported by a 3 MHz, 5 MHz, 10 MHz, or 20 MHz cell is inversely
proportional to the bandwidth of LTE cells. For example, the number of cells
supported by a 3 MHz cell is twice that supported by a 5 MHz cell, and the number
of cells supported by a 5 MHz cell is twice that supported by a 10 MHz cell.
– When LTE cells have the same antenna capability and CPRI line rate, 1.4- and 3-
MHz cells support the same number of cells, and 15- and 20-MHz cells support the
same number of cells.
– When LTE cells have the same bandwidth, the antenna capability is inversely
proportional to the number of cells for 1T1R, 2T2R, and 4T4R. For example, when
the cell bandwidth is 20 MHz, the number of cells supported when the antenna
capability is 2T2R is twice that supported when the antenna capability is 4T4R.
– When LTE cells have the same bandwidth, the number of cells supported by 1T2R
and 2T2R antennas is the same, and that supported by 2T4R and 4T4R antennas is
the same.
The capacity requirement of each board is 6 GSM TRXs + LTE 3x10 MHz 4T4R.
Therefore, a 10 MHz 4T4R LTE cell needs to be converted to 2T2R LTE cells based on the
preceding calculation methods. The conversion is as follows: 1x10 MHz 4T4R -> 2x10 MHz
2T2R -> 1x20 MHz 2T2R. According to Table 12-1, the CPRI line rate for a CPRI link that
supports a 20 MHz 2T2R cell is 4.9 Gbit/s. The corresponding carrier capacity of a GL
converging board is 126 GSM TRXs + LTE 4x20 MHz 2T2R. Therefore, the capacity
requirements can be met and this configuration is supported.
The capacity requirement of each CPRI link is 2 GSM TRXs + LTE 1x20 MHz 2T2R.
The capacity requirement of each board is 12 GSM TRXs + LTE 6x20 MHz 2T2R.
According to Table 12-1, the CPRI line rate for a CPRI link that supports a 20 MHz 2T2R
LTE cell is 4.9 Gbit/s. The corresponding carrier capacity of a GL converging board is 126
GSM TRXs + LTE 4x20 MHz 2T2R. Therefore, the capacity requirements of LTE 6x20 MHz
2T2R cannot be met and this configuration is not supported. In this case, contact Huawei
engineers for technical support.
Table 12-5 Cascading Level of the Chain Topology Using the CPRI MUX Feature
GU 6
GL 4
UL 4
GUL 4
For the distance between the RF modules and the BBU, see Product Specifications >
Technical Specifications of RRUs > Specifications of CPRI Ports in 3900 Series Base
Station Technical Description.
NOTE
If the CPRI MUX converging capability of a base station is exceeded, cell status of certain cells under
the base station may be abnormal.
13 Related Features
In Figure 13-1, the UBRI/UBRIb/UBBP_G and the GTMUb/GTMUc directly connect to one
RF module, respectively. The GTMUb/GTMUc also is the converged board and the WBBP/
UBBP_U is the converging board that connects to an RF module working in GU mode,
implementing GU CPRI MUX. RF frequency hopping between RF modules connected to the
WBBP/UBBP_U and the GTMUb/GTMUc is supported. RF frequency hopping between RF
modules connected to the GTMUb/GTMUc and the UBRI/UBRIb/UBBP_G and between RF
modules connected to the WBBP/UBBP_U and UBRI/ UBRIb/UBBP_G is not supported.
NOTE
If a UBRIb in a BBU3900 is the converging board in co-MPT scenarios, CPRI MUX does not
support baseband hopping, RF frequency hopping between two RF modules, or antenna
frequency hopping between a GTMUb/GTMUc (working in the Evolution mode) and a
UBRIb.
14 Network Impact
14.3 Reliability
CPRI MUX in Separate-MPT Scenarios
CPRI MUX in separate-MPT scenarios has the following impacts on system reliability:
l Operations or exceptions on the converging party
Circuit switched (CS) and packet switched (PS) services of the converged party will be
interrupted when a CPRI port of the converging party becomes faulty or when any of the
following operations is performed by the converging party:
– Software reset or power-off reset on the main control board or the converging board
– Removing and then inserting the main control board or the converging board
Blocking the converging board
– Commissioning CPRI ports on the converging board
In general, this duration lasts less than 3 minutes and the longest duration does not
exceed 3.5 minutes.
l Operations or exceptions on the converged party
– Performing software reset on the main control board
The data rate of PS services of the converging party may be reduced for less than 3s
and the longest duration of rate reduction does not exceed 10s.
– Performing power-off reset, inserting and then removing the main control board
CS and PS services on the converging party will be interrupted for less than 1
minute and the longest duration of service interruption does not exceed 3 minutes.
The service interruption duration does not include the duration of manual operations.
15 Engineering Guidelines
For scenarios where CPRI MUX is used with the RMU solution, see section "Engineering
Guidelines" in RMU Feature Parameter Description.
l Sites in which a single-mode base station is to be evolved into a multimode base station
and the operator requires that the existing topology of fiber optic cables remain
unchanged to reduce engineering costs
l Sites in which a co-MPT dual-mode or multimode base station is to be deployed and the
operator requires that costs of fiber optic cables be reduced
l Sites whose coverage must be ensured through cascaded RF modules, such as stadiums,
subways, and high-speed railways
Network Planning
Perform network planning by referring to instructions in 4 CPRI Topology Principles for a
Multimode Base Station, 5 Star Topology with CPRI MUX (BBU3900), 6 Star Topology
with CPRI MUX (BBU3910), 7 Star Topology with CPRI MUX (BBU3910A), 8 Chain
Topology with CPRI MUX, 9 CPRI MUX Trunk Chain Topology (RMU3900A), 10
CPRI MUX with Multimode Load Sharing Topology, and 11 Triple-Mode Dual-Star
Topology.
Hardware Planning
When selecting BBU boards that are to be used in CPRI MUX, you must consider the
application scenarios and constraints provided in 3 BBUs and Boards That Support CPRI
MUX, 5 Star Topology with CPRI MUX (BBU3900), 6 Star Topology with CPRI MUX
(BBU3910), 7 Star Topology with CPRI MUX (BBU3910A), 8 Chain Topology with
CPRI MUX, 9 CPRI MUX Trunk Chain Topology (RMU3900A), 10 CPRI MUX with
Multimode Load Sharing Topology, and 11 Triple-Mode Dual-Star Topology.
NOTICE
The CPRI link rates of baseband processing boards/interface boards, optical modules, and RF
modules must match each other and must meet the specifications in 12.1 Converging
Capabilities.
15.4 Deployment
15.4.1 Requirements
Hardware
RF modules have been installed. Cables between RF modules and BBUs have been connected
as required by the CPRI MUX feature. For detailed installation procedures, see the
corresponding Base station Installation Guide and Site Maintenance Guide of the base
stations.
NOTE
If CPRI MUX is to be deployed in a site where a single-mode base station is to be evolved into a
multimode base station, the hardware must meet the requirements of CPRI MUX. If it does not, replace
the hardware.
License
None
The RRU configuration of the converged party takes effect only after RRUs of the converging
party have been configured.
Data configurations on the converging party remain unchanged compared with those for the
trunk chain, chain, or star topology. For detailed data configurations, see RF Unit and
Topology Management Feature Parameter Description > Engineering Guidelines >
Deployment > Data Preparation.
l If GSM (GBTS) is the converged party, configure the BTSRXUCHAIN MO. For key
parameters, see Table 15-2.
l If GSM (eGBTS)/UMTS/LTE is the converged party, configure the RRUCHAIN MO.
For key parameters, see Table 15-2.
l Data configurations for the CPRI MUX-based load-sharing topology in a co-MPT base
station are the same data as those in an eNodeB. For detailed data configurations for the
load-sharing topology, see RF Unit and Topology Management Feature Parameter
Description > Engineering Guidelines (eNodeB) > Deployment > Data Preparation.
l For how to configure UBBP baseband resources, see sections "Baseband equipment" and
"Baseband resources" in 3900 Series Base Station Initial Configuration Guide > 3900
Series Base Station Initial Configuration (CME-based) > Creating Base Stations >
Creating Co-MPT Base Station > Creating Co-MPT Base Stations in Batches >
Preparing Co-MPT Base Station Data > Radio Data for a Co-MPT Base Station.
15.4.3 Activation
In co-MPT scenarios, CPRI MUX is supported by default when the requirements described in
5.1 Co-MPT Scenarios/6.1 Co-MPT Scenarios/7 Star Topology with CPRI MUX
(BBU3910A)/9.1 Co-MPT Scenarios are met. Software configuration is not required for
activating CPRI MUX. For data configurations for a co-MPT base station, see 3900 Series
Base Station Initial Configuration Guide.
This section describes the procedure for activating CPRI MUX in separate-MPT scenarios.
Step 2 On the converging party side, run the MML command ADD RRU to add an RRU/RFU to the
RRU/RFU chain.
On the converged party, run the MML command to add an RRU/RFU chain: Run ADD
RRUCHAIN for GSM (eGBTS)/UMTS/LTE, and run ADD BTSRXUCHAIN for GSM
(GBTS). For key parameter settings, see Table 15-2.
Step 3 On the converged party, run the MML command to add an RRU/RFU to the RRU/RFU chain.
Run ADD RRU for GSM (eGBTS)/UMTS/LTE, and run ADD BTSRXUBRD for GSM
(GBTS).
----End
NOTE
Data configurations must be the same for RRUs on the converging party and converged party. For detailed
parameter settings, see Table 15-1.
BBU3910:
RRU Type RT
RF Unit Working RS
Mode
NOTE
Data configurations must be the same for RRUs on the converging party and converged party. For detailed
parameter settings, see Table 15-1.
On the LMT or the U2000 for the 3900 series base station, run the DSP BRD
command to check whether RF modules on the GSM (eGBTS) side function
properly.
On the LMT or the U2000 for the 3900 series base station, run the DSP BRD
command to check whether RF modules on the UMTS side function properly.
On the LMT or the U2000 for the 3900 series base station, run the DSP BRD
command to check whether RF modules on the LTE side function properly.
– Co-MPT Scenarios
On the LMT or U2000 of converging party of a 3900 series base station, run the
MML command DSP BRD to check whether RF modules on the LTE side function
properly.
2. Check whether the line rate of the converging port is the same as planned.
– Separate-MPT scenarios: On the LMT or U2000 for the 3900 series base station,
run the MML command DSP CPRIPORT on the converging party side, and check
whether the line rate of the converging port is the same as planned.
– Co-MPT scenarios: Run the MML command DSP CPRIPORT to check whether
the line rate of the converging port is the same as planned.
15.4.5 Deactivation
This feature does not need to be deactivated.
15.4.6 Reconfiguration
You can add an RRU to or remove an RRU from a cascaded RRU chain in the star or chain
CPRI MUX topology.
For how to add or remove RF modules to or from a chain or ring on the CME, see eRAN
(FDD) Reconfiguration Guide > Device Data Reconfiguration > Adding or Deleting an RF
Module in a Chain.
Separate-MPT Scenarios
l Adding an RRU to a cascaded RRU chain
To add an RRU to a cascaded RRU chain without changing the original topology, you
need to add the RRU information on both the converging and converged parties.
a. Run the MOD RRUCHAIN command on the converging party to set a breaking
point.
b. Run MML commands on both the converging and converged parties to add an
RRU. Run ADD RRU for GSM (eGBTS)/UMTS/LTE, and run ADD
BTSRXUBRD for GSM (GBTS).
c. Adjust the original cable connections and add an RRU to the specified position.
d. Run the MOD RRUCHAIN command on the converged party to remove the
breaking point.
l Deleting an RRU from a cascaded RRU chain
To remove an RRU from a cascaded RRU chain without changing the original topology,
you need to remove the RRU information from both the converging and converged
parties.
a. Run the MOD RRUCHAIN command on the converging party to set a breaking
point.
b. Run MML commands on both the converging and converged parties to remove an
RRU. Run RMV RRU for GSM (eGBTS)/UMTS/LTE, and run RMV
BTSRXUBRD for GSM (GBTS).
c. Adjust the original cable connections and remove an RRU from the specified
position.
d. Run the MOD RRUCHAIN command on the converged party to remove the
breaking point.
Co-MPT Scenarios
l Adding an RRU to a cascaded RRU chain
To add an RRU to a cascaded RRU chain without changing the original topology:
a. Run the MOD RRUCHAIN command to set a breaking point.
b. Run the ADD RRU command to add an RRU.
c. Adjust the original cable connections and add an RRU to the specified position.
d. Run the MOD RRUCHAIN command to remove the breaking point.
l Deleting an RRU from a cascaded RRU chain
To remove an RRU from a cascaded RRU chain without changing the original topology:
a. Run the MOD RRUCHAIN command to set a breaking point.
b. Run the RMV RRU command to remove an RRU.
c. Adjust the original cable connections and remove an RRU from the specified
position.
d. Run the MOD RRUCHAIN command to remove the breaking point.
NOTE
After CPRI MUX is implemented, alarms will be reported if any exceptions occur. Clear the alarms
according to the alarm reference.
16 Parameters
TT BSC691 ADD GBFD-1 O&M of Meaning: RXU topology type, that is, RXU ring
0 BTSRX 11202 BTS topology or RXU chain topology. In the case of the
UCHAI ring topology, the optical ports of the head and tail
N boards must be specified. In the case of the chain
MOD topology, only the optical port of the head board must
BTSRX be specified.
UCHAI GUI Value Range: CHAIN(Chain), RING(Ring)
N Unit: None
Actual Value Range: CHAIN, RING
Default Value: None
TT BSC690 ADD GBFD-1 O&M of Meaning: RXU topology type, that is, RXU ring
0 BTSRX 11202 BTS topology or RXU chain topology. In the case of the
UCHAI ring topology, the optical ports of the head and tail
N boards must be specified. In the case of the chain
MOD topology, only the optical port of the head board must
BTSRX be specified.
UCHAI GUI Value Range: CHAIN(Chain), RING(Ring)
N Unit: None
Actual Value Range: CHAIN, RING
Default Value: None
TT BTS390 ADD None None Meaning: Indicates the type of the topology. In a ring
0, RRUC topology, the service data is transmitted on the fiber
BTS390 HAIN optic cable that carries the HDLC link. In a load
0 MOD sharing topology, the service data is transmitted on
WCDM RRUC two fiber optic cables simultaneously, which enhances
A, HAIN the transmission capability. The physical connection
BTS390 in the ring topology is similar to that in the load
0 LTE DSP sharing topology. The trunk chain enables multiple
RRUC CPRI fiber optic cables to simultaneously transmit
HAINP service data.
HYTOP
O GUI Value Range: CHAIN(CHAIN), RING(RING),
LOADBALANCE(LOADBALANCE),
LST TRUNK_CHAIN(TRUNK_CHAIN)
RRUC
HAIN Unit: None
Actual Value Range: CHAIN, RING,
LOADBALANCE, TRUNK_CHAIN
Default Value: None
CN BSC691 ADD GBFD-1 O&M of Meaning: Number of the cabinet where the BTS board
0 BTSRX 11202 BTS is located.
UBRD GUI Value Range: 0~62
MOD Unit: None
BTSRX
UBRD Actual Value Range: 0~62
CN BSC690 ADD GBFD-1 O&M of Meaning: Number of the cabinet where the BTS board
0 BTSRX 11202 BTS is located.
UBRD GUI Value Range: 0~62
MOD Unit: None
BTSRX
UBRD Actual Value Range: 0~62
CN BTS390 DSP None None Meaning: Indicates the number of the cabinet where
0, RRUCL the RRU is located.
BTS390 KSRC GUI Value Range: 0~15
0 SET
WCDM Unit: None
RRUCL
A, KSRC Actual Value Range: 0~15
BTS390 Default Value: 0
0 LTE TST
LOPRR
U
SRN BSC691 ADD GBFD-1 O&M of Meaning: Number of the subrack where the BTS
0 BTSRX 11202 BTS board is located.
UBRD GUI Value Range: 0~254
MOD Unit: None
BTSRX
UBRD Actual Value Range: 0~254
SRN BSC690 ADD GBFD-1 O&M of Meaning: Number of the subrack where the BTS
0 BTSRX 11202 BTS board is located.
UBRD GUI Value Range: 0~254
MOD Unit: None
BTSRX
UBRD Actual Value Range: 0~254
SRN BTS390 DSP None None Meaning: Indicates the number of the subrack where
0, RRUCL the RRU is located.
BTS390 KSRC GUI Value Range: 60~254
0 SET
WCDM Unit: None
RRUCL
A, KSRC Actual Value Range: 60~254
BTS390 Default Value: None
0 LTE TST
LOPRR
U
SN BSC691 ADD GBFD-1 O&M of Meaning: Number of the slot where the BTS board is
0 BTSRX 11202 BTS located.
UBRD GUI Value Range: 0~23
MOD Unit: None
BTSRX
UBRD Actual Value Range: 0~23
SN BSC690 ADD GBFD-1 O&M of Meaning: Number of the slot where the BTS board is
0 BTSRX 11202 BTS located.
UBRD GUI Value Range: 0~23
MOD Unit: None
BTSRX
UBRD Actual Value Range: 0~23
SN BTS390 DSP None None Meaning: Indicates the number of the slot where the
0, RRUCL RRU is located.
BTS390 KSRC GUI Value Range: 0~3
0 SET
WCDM Unit: None
RRUCL
A, KSRC Actual Value Range: 0~3
BTS390 Default Value: 0
0 LTE TST
LOPRR
U
BT BSC691 ADD GBFD-1 O&M of Meaning: Type of the newly added RXU board
0 BTSRX 11202 BTS GUI Value Range: DRRU(DRRU), DRFU(DRFU),
UBRD MRRU(MRRU), XRRU(XRRU), MRFU(MRFU),
MOD GRFU(GRFU), GRRU(GRRU), XRFU(XRFU),
BTSRX BTS3900E(BTS3900E), AIRU(AIRU)
UBRD Unit: None
QUICK
Actual Value Range: DRRU, DRFU, MRRU, XRRU,
MOD MRFU, GRFU, GRRU, XRFU, BTS3900E, AIRU
BTSRX
UBRDT Default Value: None
YPE
BT BSC690 ADD GBFD-1 O&M of Meaning: Type of the newly added RXU board
0 BTSRX 11202 BTS GUI Value Range: DRRU(DRRU), DRFU(DRFU),
UBRD MRRU(MRRU), XRRU(XRRU), MRFU(MRFU),
MOD GRFU(GRFU), GRRU(GRRU), XRFU(XRFU),
BTSRX BTS3900E(BTS3900E), AIRU(AIRU)
UBRD Unit: None
QUICK
Actual Value Range: DRRU, DRFU, MRRU, XRRU,
MOD MRFU, GRFU, GRRU, XRFU, BTS3900E, AIRU
BTSRX
UBRDT Default Value: None
YPE
RT BTS390 MOD None None Meaning: Indicates the type of the RRU.
0, RRU GUI Value Range: MRRU(MRRU), MRXU(MRXU),
BTS390 LST PRRU(PRRU), MPRU(MPRU), MPMU(MPMU),
0 RRU MPRF(MPRF), AIRU(AIRU), MRIU(MRIU),
WCDM GRRU(GRRU), LRRU(LRRU), ORRU(ORRU)
A,
BTS390 Unit: None
0 LTE Actual Value Range: MRRU, MRXU, PRRU, MPRU,
MPMU, MPRF, AIRU, MRIU, GRRU, LRRU,
ORRU
Default Value: None
WORK BSC690 SET GBFD-1 O&M of Meaning: Working mode of the RXU board.
INGST 0 BTSRX 11202 BTS GUI Value Range: GSM_AND_UMTS(GSM AND
ANDA UBP UMTS), UMTS(UMTS), GSM(GSM),
RD GSM_AND_LTE(GSM AND LTE), LTE(LTE),
UMTS_AND_LTE(UMTS AND LTE),
GSM_AND_UMTS_AND_LTE(GSM, UMTS AND
LTE), LTE_TDD(LTE TDD),
GSM_AND_LTE_TDD(GSM AND LTE TDD),
UMTS_AND_LTE_TDD(UMTS AND LTE TDD),
LTE_AND_LTE_TDD(LTE AND LTE TDD),
GSM_AND_UMTS_AND_LTE_TDD(GSM, UMTS
AND LTE TDD),
GSM_AND_LTE_AND_LTE_TDD(GSM, LTE AND
LTE TDD),
UMTS_AND_LTE_AND_LTE_TDD(UMTS, LTE
AND LTE TDD),
GSM_AND_UMTS_AND_LTE_AND_LTE_TDD(G
SM, UMTS, LTE AND LTE TDD), NBIOT(NB-IoT),
GSM_AND_NBIOT(GSM AND NB-IoT),
UMTS_AND_NBIOT(UMTS AND NB-IoT),
LTE_AND_NBIOT(LTE AND NB-IoT),
GSM_AND_UMTS_AND_NBIOT(GSM, UMTS
AND NB-IoT),
GSM_AND_LTE_AND_NBIOT(GSM, LTE AND
NB-IoT), UMTS_AND_LTE_AND_NBIOT(UMTS,
LTE AND NB-IoT),
GSM_AND_UMTS_AND_LTE_AND_NBIOT(GSM
, UMTS, LTE AND NB-IoT)
Unit: None
Actual Value Range: GSM_AND_UMTS, UMTS,
GSM, GSM_AND_LTE, LTE, UMTS_AND_LTE,
GSM_AND_UMTS_AND_LTE, LTE_TDD,
GSM_AND_LTE_TDD, UMTS_AND_LTE_TDD,
LTE_AND_LTE_TDD,
GSM_AND_UMTS_AND_LTE_TDD,
GSM_AND_LTE_AND_LTE_TDD,
UMTS_AND_LTE_AND_LTE_TDD,
GSM_AND_UMTS_AND_LTE_AND_LTE_TDD,
NBIOT, GSM_AND_NBIOT, UMTS_AND_NBIOT,
LTE_AND_NBIOT,
GSM_AND_UMTS_AND_NBIOT,
GSM_AND_LTE_AND_NBIOT,
UMTS_AND_LTE_AND_NBIOT,
GSM_AND_UMTS_AND_LTE_AND_NBIOT
Default Value: GSM(GSM)
WORK BSC691 SET GBFD-1 O&M of Meaning: Working mode of the RXU board.
INGST 0 BTSRX 11202 BTS GUI Value Range: GSM_AND_UMTS(GSM AND
ANDA UBP UMTS), UMTS(UMTS), GSM(GSM),
RD GSM_AND_LTE(GSM AND LTE), LTE(LTE),
UMTS_AND_LTE(UMTS AND LTE),
GSM_AND_UMTS_AND_LTE(GSM, UMTS AND
LTE), LTE_TDD(LTE TDD),
GSM_AND_LTE_TDD(GSM AND LTE TDD),
UMTS_AND_LTE_TDD(UMTS AND LTE TDD),
LTE_AND_LTE_TDD(LTE AND LTE TDD),
GSM_AND_UMTS_AND_LTE_TDD(GSM, UMTS
AND LTE TDD),
GSM_AND_LTE_AND_LTE_TDD(GSM, LTE AND
LTE TDD),
UMTS_AND_LTE_AND_LTE_TDD(UMTS, LTE
AND LTE TDD),
GSM_AND_UMTS_AND_LTE_AND_LTE_TDD(G
SM, UMTS, LTE AND LTE TDD), NBIOT(NB-IoT),
GSM_AND_NBIOT(GSM AND NB-IoT),
UMTS_AND_NBIOT(UMTS AND NB-IoT),
LTE_AND_NBIOT(LTE AND NB-IoT),
GSM_AND_UMTS_AND_NBIOT(GSM, UMTS
AND NB-IoT),
GSM_AND_LTE_AND_NBIOT(GSM, LTE AND
NB-IoT), UMTS_AND_LTE_AND_NBIOT(UMTS,
LTE AND NB-IoT),
GSM_AND_UMTS_AND_LTE_AND_NBIOT(GSM
, UMTS, LTE AND NB-IoT)
Unit: None
Actual Value Range: GSM_AND_UMTS, UMTS,
GSM, GSM_AND_LTE, LTE, UMTS_AND_LTE,
GSM_AND_UMTS_AND_LTE, LTE_TDD,
GSM_AND_LTE_TDD, UMTS_AND_LTE_TDD,
LTE_AND_LTE_TDD,
GSM_AND_UMTS_AND_LTE_TDD,
GSM_AND_LTE_AND_LTE_TDD,
UMTS_AND_LTE_AND_LTE_TDD,
GSM_AND_UMTS_AND_LTE_AND_LTE_TDD,
NBIOT, GSM_AND_NBIOT, UMTS_AND_NBIOT,
LTE_AND_NBIOT,
GSM_AND_UMTS_AND_NBIOT,
GSM_AND_LTE_AND_NBIOT,
UMTS_AND_LTE_AND_NBIOT,
GSM_AND_UMTS_AND_LTE_AND_NBIOT
Default Value: GSM(GSM)
RS BTS390 ADD None None Meaning: Indicates the working standard of the RRU
0, RRU or RFU.
BTS390 MOD GUI Value Range: TDL(LTE_TDD), TL(TDS_TDL),
0 RRU LO(LTE_FDD), LFTD(LTE_FDD_TDD),
WCDM WL(WiMAX_LTE), CL(CDMA_LTE),
A, LST
RRU GO(GSM_ONLY), GT(GSM_LTE_TDD),
BTS390 GL(GSM_LTE), GLFTD(GSM_LTE_FDD_TDD),
0 LTE UO(UMTS_ONLY), UT(UMTS_LTE_TDD),
UL(UMTS_LTE), ULFTD(UMTS_LTE_FDD_TDD),
CU(CDMA_UMTS), GU(GSM_UMTS),
GUT(GSM_UMTS_LTE_TDD),
GUL(GSM_UMTS_LTE),
GULFTD(GSM_UMTS_LTE_FDD_TDD), MO(NB-
IoT), LM(LTE_FDD_NB-IoT), CM(CDMA_NB-
IoT), CLM(CDMA_LTE_FDD_NB-IoT),
GM(GSM_NB-IoT), GLM(GSM_LTE_FDD_NB-
IoT), UM(UMTS_NB-IoT),
ULM(UMTS_LTE_FDD_NB-IoT),
GUM(GSM_UMTS_NB-IoT),
GULM(GSM_UMTS_LTE_FDD_NB-IoT),
RO(RFA_ONLY), TR(LTE_TDD_RFA),
LR(LTE_FDD_RFA),
LFTDR(LTE_FDD_TDD_RFA), UR(UMTS_RFA),
UTR(UMTS_LTE_TDD_RFA),
ULR(UMTS_LTE_FDD_RFA),
ULFTDR(UMTS_LTE_FDD_TDD_RFA)
Unit: None
Actual Value Range: TDL, TL, LO, LFTD, WL, CL,
GO, GT, GL, GLFTD, UO, UT, UL, ULFTD, CU,
GU, GUT, GUL, GULFTD, MO, LM, CM, CLM,
GM, GLM, UM, ULM, GUM, GULM, RO, TR, LR,
LFTDR, UR, UTR, ULR, ULFTDR
Default Value: None
AT BSC691 ADD GBFD-1 O&M of Meaning: The parameter is access type of RXU. Local
0 BTSRX 11202 BTS port access GTMU/UBRI/UBBP/GBBP/BTS3900E
UCHAI connected to RRU/RFU by CPRI; Peer port means
N GTMU gathered to the other type of base band board
MOD connect to RRU/RFU by IDX2.
BTSRX GUI Value Range: LOCALPORT(local port),
UCHAI PEERPORT(peer port)
N Unit: None
Actual Value Range: LOCALPORT, PEERPORT
Default Value: LOCALPORT(local port)
AT BSC690 ADD GBFD-1 O&M of Meaning: The parameter is access type of RXU. Local
0 BTSRX 11202 BTS port access GTMU/UBRI/UBBP/GBBP/BTS3900E
UCHAI connected to RRU/RFU by CPRI; Peer port means
N GTMU gathered to the other type of base band board
MOD connect to RRU/RFU by IDX2.
BTSRX GUI Value Range: LOCALPORT(local port),
UCHAI PEERPORT(peer port)
N Unit: None
Actual Value Range: LOCALPORT, PEERPORT
Default Value: LOCALPORT(local port)
AT BTS390 ADD None None Meaning: Indicates the access type of the board on an
0, RRUC RRU chain/ring. When Access Type is set to
BTS390 HAIN LOCALPORT(local port), the BBP connects to the
0 MOD board on an RRU chain/ring through the CPRI port.
WCDM RRUC When Access Type is set to PEERPORT(peer port),
A, HAIN the local BBP connects to the peer BBP through the
BTS390 IDX2 port on the backplane and the peer BBP
0 LTE LST connects to a board on an RRU chain/ring.
RRUC
HAIN GUI Value Range: LOCALPORT(local port),
PEERPORT(peer port)
Unit: None
Actual Value Range: LOCALPORT, PEERPORT
Default Value: LOCALPORT(local port)
HCN BSC691 ADD GBFD-1 O&M of Meaning: Number of the cabinet where the board
0 BTSRX 11202 BTS connected to the RXU chain or ring is installed.
UCHAI GUI Value Range: 0~62
N
Unit: None
MOD
BTSRX Actual Value Range: 0~62
UCHAI Default Value: None
N
HCN BSC690 ADD GBFD-1 O&M of Meaning: Number of the cabinet where the board
0 BTSRX 11202 BTS connected to the RXU chain or ring is installed.
UCHAI GUI Value Range: 0~62
N
Unit: None
MOD
BTSRX Actual Value Range: 0~62
UCHAI Default Value: None
N
HCN BTS390 ADD None None Meaning: Indicates the cabinet number of the board
0, RRUC where the head CPRI port is located.
BTS390 HAIN GUI Value Range: 0~15
0 MOD
WCDM Unit: None
RRUC
A, HAIN Actual Value Range: 0~15
BTS390 Default Value: 0
0 LTE DSP
RRUC
HAINP
HYTOP
O
LST
RRUC
HAIN
HSRN BSC691 ADD GBFD-1 O&M of Meaning: Number of the subrack where the board
0 BTSRX 11202 BTS connected to the RXU chain or ring is installed. The
UCHAI subrack No. is unique in a BTS.
N GUI Value Range: 0~254
MOD Unit: None
BTSRX
UCHAI Actual Value Range: 0~254
N Default Value: None
HSRN BSC690 ADD GBFD-1 O&M of Meaning: Number of the subrack where the board
0 BTSRX 11202 BTS connected to the RXU chain or ring is installed. The
UCHAI subrack No. is unique in a BTS.
N GUI Value Range: 0~254
MOD Unit: None
BTSRX
UCHAI Actual Value Range: 0~254
N Default Value: None
HSRN BTS390 ADD None None Meaning: Indicates the subrack number of the board
0, RRUC where the head CPRI port is located.
BTS390 HAIN GUI Value Range: 0~1,60~254
0 MOD
WCDM Unit: None
RRUC
A, HAIN Actual Value Range: 0~1,60~254
BTS390 Default Value: 0
0 LTE DSP
RRUC
HAINP
HYTOP
O
LST
RRUC
HAIN
HSN BSC691 ADD GBFD-1 O&M of Meaning: Number of the slot where the board
0 BTSRX 11202 BTS connected to the RXU chain or ring is installed. The
UCHAI slot No. is unique in a BTS.
N GUI Value Range: 0~23
MOD Unit: None
BTSRX
UCHAI Actual Value Range: 0~23
N Default Value: None
HSN BSC690 ADD GBFD-1 O&M of Meaning: Number of the slot where the board
0 BTSRX 11202 BTS connected to the RXU chain or ring is installed. The
UCHAI slot No. is unique in a BTS.
N GUI Value Range: 0~23
MOD Unit: None
BTSRX
UCHAI Actual Value Range: 0~23
N Default Value: None
HSN BTS390 ADD None None Meaning: Indicates the slot number of the board
0, RRUC where the head CPRI port is located.
BTS390 HAIN GUI Value Range: 0~6
0 MOD
WCDM Unit: None
RRUC
A, HAIN Actual Value Range: 0~6
BTS390 Default Value: None
0 LTE DSP
RRUC
HAINP
HYTOP
O
LST
RRUC
HAIN
HPN BSC691 ADD GBFD-1 O&M of Meaning: Number of the optical port on the board
0 BTSRX 11202 BTS connected to the RXU chain or ring.
UCHAI GUI Value Range: 0~5
N
Unit: None
MOD
BTSRX Actual Value Range: 0~5
UCHAI Default Value: None
N
HPN BSC690 ADD GBFD-1 O&M of Meaning: Number of the optical port on the board
0 BTSRX 11202 BTS connected to the RXU chain or ring.
UCHAI GUI Value Range: 0~5
N
Unit: None
MOD
BTSRX Actual Value Range: 0~5
UCHAI Default Value: None
N
HPN BTS390 ADD None None Meaning: Indicates the number of the head CPRI port.
0, RRUC GUI Value Range: 0~11
BTS390 HAIN
0 Unit: None
MOD
WCDM RRUC Actual Value Range: 0~11
A, HAIN Default Value: None
BTS390
0 LTE DSP
RRUC
HAINP
HYTOP
O
LST
RRUC
HAIN
RCN BTS390 ADD None None Meaning: Indicates the ID of the RRU chain. It
0, RRUC uniquely identifies a chain within a base station.
BTS390 HAIN GUI Value Range: 0~249
0 DSP
WCDM Unit: None
CPRIL
A, BR Actual Value Range: 0~249
BTS390 Default Value: None
0 LTE DSP
RRUC
HAIN
LST
RRUC
HAIN
MOD
RRUC
HAIN
RMV
RRUC
HAIN
STR
CPRIL
BRNEG
LSN BTS390 ADD None None Meaning: Indicates the slot number of the converged
0, RRUC party in CPRI MUX. If this parameter is set to 255,
BTS390 HAIN the slot number of the converged party is not
0 MOD specified. When the converging party is in a
WCDM RRUC BBU3900, this parameter can be left unspecified.
A, HAIN When the converging party is in a BBU3910, this
BTS390 parameter must be specified.
0 LTE LST
RRUC GUI Value Range: 0~6,255
HAIN Unit: None
Actual Value Range: 0~6,255
Default Value: 255
RCN BSC691 ADD GBFD-1 O&M of Meaning: Number of the RXU chain or ring. The
0 BTSRX 11202 BTS value scope is 0~11 for Non-SingleRAN BTS and
UCHAI 0~249 for SingleRAN BTS. The RXU chain No. is
N unique in the same BTS.
MOD GUI Value Range: 0~249
BTSRX Unit: None
UCHAI
N Actual Value Range: 0~249
RCN BSC690 ADD GBFD-1 O&M of Meaning: Number of the RXU chain or ring. The
0 BTSRX 11202 BTS value scope is 0~11 for Non-SingleRAN BTS and
UCHAI 0~249 for SingleRAN BTS. The RXU chain No. is
N unique in the same BTS.
MOD GUI Value Range: 0~249
BTSRX Unit: None
UCHAI
N Actual Value Range: 0~249
RCN BTS390 ADD None None Meaning: Indicates the ID of the RRU or RFU chain/
0, RRU ring.
BTS390 LST GUI Value Range: 0~249
0 RRU
WCDM Unit: None
A, Actual Value Range: 0~249
BTS390 Default Value: None
0 LTE
RXUC BSC691 ADD GBFD-1 O&M of Meaning: Number of the RXU chain where the board
HAINN 0 BTSRX 11202 BTS is located
O UBRD GUI Value Range: 0~249
MOD Unit: None
BTSRX
UBRD Actual Value Range: 0~249
RXUC BSC690 ADD GBFD-1 O&M of Meaning: Number of the RXU chain where the board
HAINN 0 BTSRX 11202 BTS is located
O UBRD GUI Value Range: 0~249
MOD Unit: None
BTSRX
UBRD Actual Value Range: 0~249
17 Counters
18 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
19 Reference Documents