Cpri Mux (Sran12.1 04)

SingleRAN
CPRI MUX Feature Parameter

Description
Issue 04
Date 2017-10-17
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: [email protected]
Issue 04 (2017-10-17) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
SingleRAN
CPRI MUX Feature Parameter Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 2
1.4 Differences Between Base Station Types....................................................................................................................... 3
2 Overview......................................................................................................................................... 4
2.1 Introduction.................................................................................................................................................................... 4
2.2 Benefits........................................................................................................................................................................... 5
3 BBUs and Boards That Support CPRI MUX............................................................................ 6

3.1 BBU3900 Boards That Support CPRI MUX................................................................................................................. 6
3.2 BBU3910 Boards That Support CPRI MUX................................................................................................................. 9
3.3 BBU3910As That Support CPRI MUX....................................................................................................................... 10
3.4 BBU3910C That Supports CPRI MUX........................................................................................................................10
3.5 BBU5900 Boards That Support CPRI MUX................................................................................................................11
4 CPRI Topology Principles for Multimode Base Stations.................................................... 12

5 Star Topology with CPRI MUX (BBU3900)............................................................................ 13
5.1 Co-MPT Scenarios....................................................................................................................................................... 13
5.1.1 Constraints................................................................................................................................................................. 13
5.1.2 UL CPRI MUX in Star Topology..............................................................................................................................13
5.1.3 GU/GL CPRI MUX in Star Topology....................................................................................................................... 15
5.1.4 GUL CPRI MUX in Star Topology........................................................................................................................... 21
5.2 Separate-MPT Scenarios.............................................................................................................................................. 25
5.2.1 Constraints................................................................................................................................................................. 25
5.2.2 UL CPRI MUX in Star Topology..............................................................................................................................25
5.2.3 GU/GL CPRI MUX in Star Topology....................................................................................................................... 26

6.1 Co-MPT Scenarios....................................................................................................................................................... 28
7 Star Topology with CPRI MUX (BBU3910A)......................................................................... 34

8 Star Topology with CPRI MUX (BBU3910C)......................................................................... 35
Issue 04 (2017-10-17) Huawei Proprietary and Confidential ii

SingleRAN

9.1 Co-MPT Scenarios....................................................................................................................................................... 36
10 Chain Topology with CPRI MUX.......................................................................................... 40

11 CPRI MUX with Multimode Load Sharing Topology....................................................... 44
12 Triple-Mode Dual-Star Topology.......................................................................................... 46
12.1 GU+L Dual-Star Topology......................................................................................................................................... 46
12.2 GL+U Dual-Star Topology......................................................................................................................................... 47
12.3 G[U*L] Dual-Star Topology.......................................................................................................................................47
13 Specifications of the CPRI MUX Feature..............................................................................48

13.1 CPRI MUX Converging Capabilities......................................................................................................................... 48
13.2 Cascading Level of the Chain Topology with CPRI MUX........................................................................................ 53
14 Related Features.........................................................................................................................54
14.1 Prerequisite Features...................................................................................................................................................54
14.2 Mutually Exclusive Features...................................................................................................................................... 54
14.3 Impacted Features.......................................................................................................................................................55
15 Network Impact......................................................................................................................... 56
15.1 System Capacity......................................................................................................................................................... 56
15.2 Network Performance.................................................................................................................................................56
15.3 Reliability................................................................................................................................................................... 56
16 Engineering Guidelines........................................................................................................... 58
16.1 When to Use............................................................................................................................................................... 58
16.2 Required Information................................................................................................................................................. 58
16.3 Network Planning....................................................................................................................................................... 58
16.4 Deployment................................................................................................................................................................ 59
16.4.1 Requirements........................................................................................................................................................... 59
16.4.2 Data Preparation...................................................................................................................................................... 59
16.4.3 Activation................................................................................................................................................................ 62
16.4.4 Activation Observation............................................................................................................................................66
16.4.5 Deactivation.............................................................................................................................................................67
16.4.6 Reconfiguration....................................................................................................................................................... 67
16.5 Performance Monitoring.............................................................................................................................................68
16.6 Parameter Optimization.............................................................................................................................................. 68
16.7 Possible Issues............................................................................................................................................................ 68
16.7.1 Related Alarms........................................................................................................................................................ 68
16.7.2 MML Commands for Maintenance......................................................................................................................... 71
17 Parameters................................................................................................................................... 73
18 Counters...................................................................................................................................... 81
Issue 04 (2017-10-17) Huawei Proprietary and Confidential iii

SingleRAN
19 Glossary....................................................................................................................................... 82
20 Reference Documents............................................................................................................... 83
Issue 04 (2017-10-17) Huawei Proprietary and Confidential iv

SingleRAN
CPRI MUX Feature Parameter Description 1 About This Document
1 About This Document
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:
l BTS3900
l BTS3900L
l BTS3900A
l BTS3900AL
l BTS3900C
l DBS3900
l BTS5900
l BTS5900L
l DBS5900
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.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein

l Work with Huawei products
Issue 04 (2017-10-17) Huawei Proprietary and Confidential 1

SingleRAN
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
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 04 (2017-10-17)
Issue 04 (2017-10-17) of SRAN12.1 introduces the following changes to Issue 03
(2017-09-15) of SRAN12.1.
Change Change Description Parameter

Type Change
Feature Added support for the BBU5900. None

change
Added support for the BBU3910C. For details, see 3.4
BBU3910C That Supports CPRI MUX, 8 Star Topology
with CPRI MUX (BBU3910C), and Converging
Capability of the Converging Party.
Editorial None None

change
SRAN12.1 03 (2017-09-15)
(2017-08-30) of SRAN12.1.

Type Change
Feature None None

change
Editorial Added the description that all RF modules on a chain must None
change work at the same rate. For details, see 10 Chain Topology
with CPRI MUX.
SRAN12.1 02 (2017-08-30)
(2017-03-10) of SRAN12.1.

SingleRAN

Type Change
Feature None None

change
Editorial Added figures showing topology examples in MML None

change Command Examples.
SRAN12.1 01 (2017-03-10)
This issue does not include any changes.
SRAN12.1 Draft A (2016-12-31)

Draft A (2016-12-31) of SRAN12.1 introduces the following changes to Issue 02
(2016-04-20) of SRAN11.1.

Type Change
Feature Supported the following relationships between the None

change converged boards and converging boards in UL separate-
MPT scenarios:
l One-to-one relationship
A converged board corresponds to a converging board.
A maximum of three pairs of one-to-one relationships
are supported.
l One-to-two relationship
A converged board corresponds to two converging
boards.
A maximum of two pairs of one-to-two relationships are
supported.
For details, see 6.2 Separate-MPT Scenarios.
Editorial Deleted the description "In separate-MPT scenarios, CPRI None

change MUX is used as a special solution." from 4 CPRI Topology
Principles for Multimode Base Stations.
Added an example to 14.2 Mutually Exclusive Features. None
1.4 Differences Between Base Station Types

This document applies only to 3900 series base stations, excluding DBS3900 LampSite base
stations. For application of the CPRI MUX feature in the DBS3900 LampSite base stations,
see CPRI MUX (LampSite) Feature Parameter Description.

SingleRAN
CPRI MUX Feature Parameter Description 2 Overview
2 Overview
2.1 Introduction
In the CPRI MUX feature, multiple modes use a common public radio interface (CPRI) link
to transmit data.
Multimode RF modules are connected to a single-mode or multimode(1) baseband processing

board/interface board through CPRI links. Another single-mode or multimode(1) baseband
processing board/interface board is connected to the previous baseband processing board/
interface board through the BBU backplane and indirectly communicates with the multimode
RF modules. The baseband processing board or interface board that is directly connected to
multimode RF modules is called the converging board, and the corresponding mode is called
the converging party. The baseband processing board or interface board that is indirectly
connected to multimode RF modules is called the converged board, and the corresponding
mode is called the converged party. In Figure 2-1, mode A is the converged party and mode B
is the converging party. Note that mode A and mode B can be a single mode or co-BBP
multiple modes.(1)
Figure 2-1 Working principle of CPRI MUX

SingleRAN
CPRI MUX Feature Parameter Description 2 Overview
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.

SingleRAN
CPRI MUX Feature Parameter Description 3 BBUs and Boards That Support CPRI MUX
3 BBUs and Boards That Support CPRI MUX
BBUs that support CPRI MUX include the BBU5900, BBU3910C, BBU3910A, BBU3910,
and BBU3900.
l Section 3.1 BBU3900 Boards That Support CPRI MUX describes the BBU3900
boards that support CPRI MUX.
l Section 3.3 BBU3910As That Support CPRI MUX describes the BBU3910A modules
that support CPRI MUX.
l Section 3.4 BBU3910C That Supports CPRI MUX describes the BBU3910C module
that supports CPRI MUX.
NOTE
3.1 BBU3900 Boards That Support CPRI MUX

In separate-MPT scenarios, only UMTS and LTE can serve as the converging party. If GSM is
involved in the scenarios, GSM baseband signals are processed by RF modules. Table 3-1
lists BBU3900 boards that support the CPRI MUX feature and slot assignment.
Table 3-1 BBU3900 boards that support the CPRI MUX feature and slot assignment in
separate-MPT scenarios
Mode on Converging Slot of the Converged Slot of the
the CPRI Board Converging Board Converged Board
Port Board
UL WBBPf/ Slot 2 or 3 LBBPd/ One LBBPd or

UBBP_U UBBP_L UBBP_L must be
installed in slot 3 or 2.

SingleRAN

Port Board
LBBPd/ Slot 2 or 3 WBBPa/ One WBBPf or

UBBP_L WBBPb/ UBBP_U must be
WBBPd/ installed in slot 3 or 2.
WBBPf/
UBBP_U
GU WBBPf/ Slot 2 or 3 GTMUb/ Slot 6

UBBP_U GTMUc
GL LBBPd/ Slot 2 or 3 GTMUb/ Slot 6

UBBP_L GTMUc
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, topology constraints, and slot assignment.
Table 3-2 BBU3900 boards that support the CPRI MUX feature, topology constraints, and
slot assignment in co-MPT scenarios
Mode Converging Board Slot of the Topology Constraint
on Convergin
the g Board
CPRI
Port
UL WBBPf, LBBPd, or Slot 2 or 3 l If LTE serves as the converged party,

UBBP_U/L/GU/GL/ the converged board cannot be an
UL/GUL(1)(2) LBBPc.
l One WBBPf or UBBP_Ux(3) must be
installed in slot 2 or 3.
GU UBRIb(4) Slot 0 or 1 l If LTE serves as the converged party,

the converged board cannot be an
LBBPc.
l If the converging party or converged
party contains UMTS, one WBBPf or
UBBP_Ux must be installed in slot 2
or 3.
l If a UBRIb serves as the converging
board, GSM baseband signals are
processed by RF modules.(5)
l If a UBRIb serves as the converging
board in GUL CPRI MUX, the
converged boards must be UO and LO
baseband processing boards.(6)

SingleRAN
Mode Converging Board Slot of the Topology Constraint

on Convergin
the g Board
CPRI
Port
UBBP_G/U/GU/GL/ Slot 2 or 3 l If a BBU is configured with a

UL/GUL multimode co-BBP board, and modes
used in CPRI MUX are the same as or
are the subset of the modes on the co-
BBP board, RF modules are connected
to CPRI ports on the multimode co-
BBP board. For example, if the BBU
is configured with a UBBP_GL,
implement GL CPRI MUX on this
UBBP_GL instead of a GO or LO
baseband processing board.
l If GSM baseband signals are
processed by RF modules and GSM
serves as the converged party, GSM
signals can be converged by the
UBBP_U/UL. Therefore, a GSM
baseband processing board or interface
board is not required.
l If GSM baseband signals are not
processed by RF modules(7), a
UBBP_Gx(3) must be installed in slot
1, 2, or 3.
GL UBRIb Slot 1 Same as those for GU
UBBP_G/L Slot 1, 2, or
3
UBBP_GU/GL/UL/G Slot 2 or 3
UL
GUL UBRIb Slot 1 Same as those for GU
UBBP_G/U/L/GU/G Slot 2 or 3
L/UL/GUL

SingleRAN
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) If multiple modes are deployed on a UBBP, the mode of data transmitted through CPRI ports on this
board can be all or some 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)In GUL CPRI MUX, if the converging board is a UBRIb, UMTS and LTE cells of the converged party
must be served by the specified baseband equipment group, and such a baseband equipment group must
include only 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. Therefore, a UBBP_Gx must be configured in the BBU.

In separate-MPT scenarios, only UMTS and LTE can serve as the converging party. If GSM is
involved in the scenarios, GSM baseband signals are processed by RF modules. Table 3-3
lists the BBU3910 boards that support the CPRI MUX feature and the slot assignment.
Table 3-3 BBU3910 boards that support the CPRI MUX feature and slot assignment in
separate-MPT scenarios

Port Board
UL UBBP_U Slot 0, 1, 2, 3, UBBP_L Slot 0, 1, 2, 3, 4, or 5

4, or 5
UBBP_L Slot 0, 1, 2, 3, UBBP_U Slot 0, 1, 2, 3, 4, or 5

4, or 5
UL UBBPei_U Slot 0, 1, 2, 3, UBBPd/ Slot 0, 1, 2, 3, 4, or 5

4, or 5 UBBPe_L
UBBPei_L Slot 0, 1, 2, 3, UBBPd/ Slot 0, 1, 2, 3, 4, or 5

4, or 5 UBBPe_U
GU UBBP_U Slot 0, 1, 2, or 3 GTMUb/ Slot 6

GTMUc
GL UBBP_L Slot 0, 1, 2, or 3 GTMUb/ Slot 6

GTMUc

SingleRAN
NOTE
In separate-MPT scenarios, the UBBPei cannot serve as a converged board.
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 slot assignment in co-
MPT scenarios
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.
3.3 BBU3910As That Support CPRI MUX

The BBU3910A only applies to co-MPT scenarios. A BBU3910A provides six CPRI ports,
and all BBU3910As support CPRI MUX. Table 3-5 lists the modes supported by different
models of BBU3910As.
Table 3-5 Modes supported by BBU3910As
BBU Model Mode
BBU3910A1 GU, GL, UL
BBU3910A2 GU, GL, UL
BBU3910A3 GU, GL, UL, GUL
3.4 BBU3910C That Supports CPRI MUX

The BBU3910C applies only to GU co-MPT scenarios. A BBU3910C provides one CPRI
port.

SingleRAN

In separate-MPT scenarios, only UMTS and LTE can serve as the converging party. Table 3-6
lists the BBU5900 boards that support the CPRI MUX feature as well as the slot assignment.
Table 3-6 BBU5900 boards that support the CPRI MUX feature as well as the slot assignment
for separate-MPT multimode base stations
Mode on the Convergi Slot of the Converged Slot of the
CPRI Port ng Board Converging Board Converged Board
Board
UL UBBP_U Slot 0, 1, 2, 3, UBBP_L Slot 0, 1, 2, 3, 4, or 5

4, or 5
UBBP_L Slot 0, 1, 2, 3, UBBP_U Slot 0, 1, 2, 3, 4, or 5

4, or 5
UL UBBPei_U Slot 0, 1, 2, 3, UBBPd/ Slot 0, 1, 2, 3, 4, or 5

4, or 5 UBBPe_L
UBBPei_L Slot 0, 1, 2, 3, UBBPd/ Slot 0, 1, 2, 3, 4, or 5

4, or 5 UBBPe_U
converging party or converged party. Table 3-7 lists the BBU5900 boards that support the
CPRI MUX feature as well as the slot assignment.
Table 3-7 BBU5900 boards that support the CPRI MUX feature as well as the slot assignment
for co-MPT multimode base stations
Mode on the Converging Board Slot of the Converging
CPRI Port Board
GU UBBP_G/U/L/GU/GL/UL/GUL Slot 0, 1, 2, 3, 4, or 5
GL
UL
GUL

SingleRAN
CPRI MUX Feature Parameter Description 4 CPRI Topology Principles for Multimode Base Stations
4 CPRI Topology Principles for Multimode

Base Stations
l The dual-star topology is recommended for a separate-MPT base station.

l The star topology with CPRI MUX is recommended for a co-MPT base station.
l The multimode load sharing topology is recommended when the CPRI bandwidth is
insufficient in a co-MPT base station or a separate-MPT base station using the dual-star
topology is reconstructed to a co-MPT base station.
l The chain topology with CPRI MUX where multimode RF modules are cascaded is
recommended for base stations deployed to provide coverage for stadiums, metros, and
high-speed railways.

SingleRAN
CPRI MUX Feature Parameter Description 5 Star Topology with CPRI MUX (BBU3900)
5 Star Topology with CPRI MUX (BBU3900)
5.1 Co-MPT Scenarios
5.1.1 Constraints
The converging and converged parties in the CPRI MUX feature must share one BBU.
5.1.2 UL CPRI MUX in Star Topology

l Scenario 1: A single-mode baseband processing board serves as the converging board.
The following conditions must be met:
– A WBBPf, LBBPd, or UBBP_U/L that serves as the converging board must be
configured in slot 2 or 3.
– If LTE serves as the converged party, the converged board cannot be an LBBPc.
– When UMTS serves as the converging or converged party, one WBBPf or
UBBP_Ux must be installed in slot 2 or 3.
Figure 5-1 shows CPRI MUX where a WBBPf/UBBP_U serves as the converging board
and an LBBPd/UBBP_L serves as the converged board.

SingleRAN
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
– 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.

SingleRAN
Figure 5-2 UL CPRI MUX in co-MPT scenarios with UL co-BBP
5.1.3 GU/GL CPRI MUX in Star Topology

GU CPRI MUX in Star Topology
– A UBRIb or UBBP_G/U serves as the converging board. The UBRIb is configured
in slot 0 or 1, and the UBBP_G/U is configured in slot 2 or 3.
– When a UBRIb serves as the converging board, GSM baseband signals are
processed by RF modules.
– When GSM baseband signals are processed by RF modules and GSM serves as the
converged party, GSM signals can be converged by the UBBP_U. Therefore, 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.
Figure 5-3 shows GU 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.

SingleRAN
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.

SingleRAN
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
must be met:
2 or 3.
– When a UBBP_GL serves as the converging board in GU CPRI MUX, GSM is the
– 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.

SingleRAN
Figure 5-5 GU CPRI MUX in co-MPT scenarios with GU co-BBP
GL CPRI MUX in Star Topology

– A UBRIb or UBBP_G/L serves as the converging board. The UBRIb is configured
in slot 1, and the UBBP_G/L is configured in slot 1, 2, or 3.
– When LTE serves as the converged party, the LBBPc cannot serve as the converged
board.
converged party, GSM signals can be converged by the UBBP_L. Therefore, a
Figure 5-6 shows GL CPRI MUX where GSM serves as the converging party, a UBRIb
modules.

SingleRAN
Figure 5-6 GL CPRI MUX in co-MPT scenarios when GSM serves as the converging
by RF modules
Figure 5-7 shows GL CPRI MUX where LTE serves as the converging party, a UBBP_L
modules.

SingleRAN
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
must be met:
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
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.

SingleRAN
Figure 5-8 GL CPRI MUX in co-MPT scenarios with GL co-BBP
5.1.4 GUL CPRI MUX in Star Topology

– A UBRIb or UBBP_G/U/L serves as the converging board. The UBRIb is
configured in slot 1, and the UBBP_G/U/L is configured in slot 2 or 3.
– When LTE serves as the converged party, the LBBPc cannot serve as the converged
board.
– When a UBRIb serves as the converging board in GUL CPRI MUX, the converged
boards are UO and LO baseband processing boards(1), that is, WBBP(2)/UBBP_U
and LBBPd/UBBP_L.
converged party, GSM signals can be converged by the UBBP_U/L. Therefore, a
NOTE
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.

SingleRAN
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
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.

SingleRAN
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
must be met:
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
– 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
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.

SingleRAN
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

SingleRAN
5.2 Separate-MPT Scenarios
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.
5.2.2 UL CPRI MUX in Star Topology

l If UMTS is the converging party and LTE is the converged party, the converging board
must be a WBBPf/UBBP_U and the WBBPf/UBBP_U must be installed in slot 2 or 3.
The converged board must be an LBBPd/UBBP_L and one LBBPd/UBBP_L must be
installed in slot 3 or 2, as shown in Figure 5-13.
l If LTE is the converging party and UMTS is the converged party, the converging board
must be an LBBPd/UBBP_L and the LBBPd/UBBP_L must be installed in slot 2 or 3.
The converged board can be a WBBPa/WBBPb/WBBPd/WBBPf/UBBP_U, and one
WBBPf/UBBP_U must be installed in slot 3 or 2, as shown in Figure 5-14.
Figure 5-13 UL CPRI MUX in separate-MPT scenarios when UMTS is the converging party

SingleRAN
Figure 5-14 UL CPRI MUX in separate-MPT scenarios when LTE is the converging party
5.2.3 GU/GL CPRI MUX in Star Topology

l In GU CPRI MUX, the converging party must be UMTS, and the converged party must
be GSM. The converging board must be a WBBPf or UBBP_U and must be installed in
slot 2 or 3, and the converged board must be a GTMUb or GTMUc and must be installed
in slot 6, as shown in Figure 5-15.
l In GL CPRI MUX, LTE must serve as the converging party and GSM must serve as the
converged party. The converging board must be an LBBPd or UBBP_L and must be
installed in slot 2 or 3, and the converged board must be a GTMUb or GTMUc and must
be installed in slot 6, as shown in Figure 5-16.
NOTICE
In this scenario, data from slot 6 can be converged to either slot 2 or 3, but cannot be
converged to both slots.

SingleRAN
Figure 5-15 Separate-MPT GU CPRI MUX
Figure 5-16 Separate-MPT GL CPRI MUX

SingleRAN

In co-MPT scenarios, the following conditions must be met if BBU3910s support CPRI
MUX:
l The converging and converged parties in the CPRI MUX feature share one BBU.
l A UBRIb or UBBP_G/U/L/GU/GL/UL/GUL board can serve as the converging board,
and is installed in one of slots 0 to 5.
l When a UBRIb serves as the converging board, GSM baseband signals are processed by
RF modules.
l When GSM baseband signals are processed by RF modules and GSM serves as the
converged party, GSM signals can be converged by the UBBP_U/L/UL. Therefore, a
Use GU CPRI MUX as an example:

l Figure 6-1 shows co-MPT GU CPRI MUX where a UBRIb serves as the converging
board.
l Figure 6-2 shows co-MPT GU CPRI MUX where a UBBP_U serves as the converging
board.
l Figure 6-3 shows co-MPT GU CPRI MUX where a UBBP_GU serves as the converging
board.

SingleRAN
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

SingleRAN
Figure 6-3 Co-MPT GU CPRI MUX where a UBBP_GU serves as the converging board

Constraints
only converge data or have its data converged.
l In separate-MPT UL CPRI MUX, one BBU can provide a maximum of 24 ports for
converging data. 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. The two-to-one relationship is not supported.
GU/GL CPRI MUX

BBU3910s support separate-MPT GU or GL CPRI MUX when the following conditions are
met:
l A UBBP_U or UBBP_L serves as the converging board and is installed in one of slots 0
to 3. A GTMUb or GTMUc serves as the converged board and is installed in slot 6.
l Data from slot 6 is converged to one instead of two of slots 0 to 3.
Figure 6-4 shows GU CPRI MUX as an example.

SingleRAN
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.

SingleRAN
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.

SingleRAN
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.

SingleRAN
CPRI MUX Feature Parameter Description 7 Star Topology with CPRI MUX (BBU3910A)
7 Star Topology with CPRI MUX

(BBU3910A)
l A BBU3910A supports CPRI MUX only in co-MPT scenarios, including the

GU/GL/UL/GUL CPRI MUX.
l CPRI MUX can only be used within one BBU.
Figure 7-1 GU CPRI MUX in co-MPT scenarios where a BBU3910A is used

SingleRAN
CPRI MUX Feature Parameter Description 8 Star Topology with CPRI MUX (BBU3910C)
8 Star Topology with CPRI MUX (BBU3910C)
l A BBU3910C supports CPRI MUX only in GU co-MPT scenarios.

Figure 8-1 GU CPRI MUX in co-MPT scenarios where a BBU3910C is used

SingleRAN

In co-MPT scenarios, the following conditions must be met if BBU5900s support CPRI
MUX:
l The converging and converged parties in the CPRI MUX feature share one BBU.
l A UBBP_G/U/L/GU/GL/UL/GUL board can serve as the converging board, and is
installed in one of slots 0 to 5.
l When GSM baseband signals are processed by RF modules and GSM serves as the
converged party, GSM signals can be converged by the UBBP_U/L/UL. Therefore, a
GSM baseband processing board is not required.
The following uses GU CPRI MUX as an example.
l Figure 9-1 shows co-MPT GU CPRI MUX where a UBBP_U serves as the converging
board.
l Figure 9-2 shows co-MPT GU CPRI MUX where a UBBP_GU serves as the converging
board.

SingleRAN
Figure 9-1 Co-MPT GU CPRI MUX where a UBBP_U serves as the converging board
Figure 9-2 Co-MPT GU CPRI MUX where a UBBP_GU serves as the converging board

Constraints

SingleRAN
only converge data or have its data converged.
l In separate-MPT UL CPRI MUX, one BBU can provide a maximum of 24 ports for
converging data. 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. The two-to-one relationship is not supported.
UL CPRI MUX
BBU5900s support separate-MPT UL CPRI MUX when the following conditions are met:
l A UBBP_U or UBBP_L serves as the converging or converged board and is installed in

one of slots 0 to 5.
l In a BBU5900, 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 9-3 shows an example of three pairs of one-to-one relationships with LTE as the
converging party.
Figure 9-3 Separate-MPT UL CPRI MUX with LTE as the converging party (three pairs of
one-to-one relationships)
NOTE
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 9-4 shows an example of two pairs of one-to-two relationships with LTE as the
converging party.

SingleRAN
Figure 9-4 Separate-MPT UL CPRI MUX with LTE as the converging party (two pairs of
one-to-two relationships)
NOTE
In the preceding figure, the board in slot 0 is a converged board, and boards in slots 1 and 3 are
converging boards. These three boards form a group. Similarly, boards in slots 2, 4, and 5 form a group.

SingleRAN
CPRI MUX Feature Parameter Description 10 Chain Topology with CPRI MUX
10 Chain Topology with CPRI MUX
In a chain topology with CPRI MUX, configurations of the BBU, such as a BBU5900,
BBU3910A, BBU3910, or BBU3900, 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
l In a chain topology with CPRI MUX, preferentially activate GSM cells served by the RF modules
that are configured at the upper levels on a chain, that is, closer to a baseband processing board.
l All RF modules on the chain must work at the same rate.
l Intra-mode cascading: All cascaded multimode RF modules are configured with the
same mode and work in the same mode. Figure 10-1 shows GU CPRI MUX 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.
l Inter-mode cascading: Cascaded multimode RF modules work in different modes. Inter-
mode cascading is implemented in the following scenarios:
– Scenario 1
In the chain topology with co-MPT CPRI MUX, the working mode of an RF
module includes GSM. For example, the working mode may be GO, GU, GL, or
GUL.
In this scenario, all RF modules on the chain must be multimode RF modules that
support GSM. That is, all RF modules must support GU, GL, or GUL.
Figure 10-2 shows co-MPT GU CPRI MUX 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. The "UO Radio Unit" in this
figure is working in UO mode, but it is a multimode RF module that supports GSM.
That is, it supports GU or GUL.
– Scenario 2
In the chain topology with CPRI MUX, GSM is not included in the working mode
of any RF module. RF modules on the chain work in UO, LO, or UL mode.
In this scenario, the RF modules on the chain can be any GU, GL, UL, or GUL RF
modules.
Figure 10-3 shows co-MPT UL CPRI MUX where a BBU3900 is used and UMTS
serves as the converging party.

SingleRAN
– Scenario 3
In separate-MPT CPRI MUX, the multimode RF modules 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 mode, but these modules must support GU or GUL, as
shown in Figure 10-4.
NOTE
For inter-mode cascading, if an RF module whose working mode includes GSM is configured with
GSM TRXs, it must be configured at the upper level on a chain, that is, closer to a baseband
processing board.
Figure 10-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

SingleRAN
Figure 10-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 10-3 Co-MPT UL CPRI MUX using inter-mode cascading where a BBU3900 is used
and UMTS serves as the converging party

SingleRAN
Figure 10-4 Separate-MPT GU CPRI MUX using inter-mode cascading where a BBU3900 is
used and UMTS serves as the converging party

SingleRAN
CPRI MUX Feature Parameter Description 11 CPRI MUX with Multimode Load Sharing Topology
11 CPRI MUX with Multimode Load

Sharing Topology
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.
l If each CPRI link in the multimode load sharing topology can transmit data of only one
mode, the CPRI MUX feature is not required. For details on 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. Currently, only GUL RF modules support
CPRI MUX with multimode load sharing. Two CPRI links carry GU+L data, with one
link carrying GU data and the other carrying LTE data, as shown in Figure 11-1.

SingleRAN
CPRI MUX Feature Parameter Description 11 CPRI MUX with Multimode Load Sharing Topology
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 BBU5900, BBU3910, or BBU3900 supports the multimode load
sharing topology.
l In the multimode load sharing topology, the number of LTE cells cannot exceed the
maximum supported by each CPRI link, which depends on the CPRI port rate. For the
maximum number of LTE cells supported by different CPRI port rates, see the following
documents:
"Specifications of CPRI Ports" in Product Specifications > Technical Specifications of
the BBU3900s and BBU3910s > Technical Specifications of the eNodeB > Technical
Specifications of the eNodeB FDD of 3900 Series Base Station Technical Description for
the BBU3900 and BBU3910
"Specifications of CPRI Ports" in Product Specifications > Technical Specifications of
the BBU5900 > Technical Specifications of the eNodeB > Technical Specifications of
the eNodeB FDD of 5900 Series Base Station Technical Description for the BBU5900
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.
Figure 11-1 GU+L load sharing topology

SingleRAN
CPRI MUX Feature Parameter Description 12 Triple-Mode Dual-Star Topology
12 Triple-Mode Dual-Star Topology
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
The converging and converged parties in the CPRI MUX feature must share one BBU.
12.1 GU+L Dual-Star Topology

In Figure 12-1, BBU 0 uses separate-MPT GU CPRI MUX. The WBBPf/UBBP_U provides
a CPRI link to connect to the multimode RF module. In BBU 1 (LTE mode), the LBBP/
UBBP_L provides a CPRI link to connect to the multimode RF module. In this way, the
WBBPf/UBBP_U and LBBP/UBBP_L form a GU+L dual-star topology.
Figure 12-1 GU+L dual-star topology

SingleRAN
CPRI MUX Feature Parameter Description 12 Triple-Mode Dual-Star Topology
12.2 GL+U Dual-Star Topology

In Figure 12-2, BBU 0 uses separate-MPT GL CPRI MUX. The LBBPd/UBBP_L provides a
CPRI link to connect to the multimode RF module. In BBU 1 (UMTS mode), the WBBP/
UBBP_U provides a CPRI link to connect to the multimode RF module. In this way, the
LBBPd/UBBP_L and WBBP/UBBP_U form a GL+U dual-star topology.
Figure 12-2 GL+U dual-star topology
12.3 G[U*L] Dual-Star Topology

UMTS and LTE share one main control board, and the WBBPf/UBBP_U, LBBPd/UBBP_L,
or UBBP_UL uses a UL port to connect to a multimode RF module. GSM uses an
independent main control board GTMU, and the GTMU uses a CPRI port to connect to the
multimode RF module. In this way, the WBBPf/UBBP_U, LBBPd/UBBP_L, or UBBP_UL
and GTMU form a G[U*L] dual-star topology. Figure 12-3 shows the G[U*L] dual-star
topology in which a WBBPf/UBBP_U provides UL CPRI ports.
Figure 12-3 G[U*L] dual-star topology

SingleRAN
CPRI MUX Feature Parameter Description 13 Specifications of the CPRI MUX Feature
13 Specifications of the CPRI MUX Feature
13.1 CPRI MUX Converging Capabilities

In separate-MPT or co-MPT CPRI MUX, the multimode converging capability depends on
the CPRI line rate and the board capabilities of the converging party.
Converging Capability of the Converging Party

Table 13-1 lists the converging capability of the converging party in multimode scenarios
where CPRI MUX is used with a BBU5900, BBU3900, or BBU3910. Table 13-2 lists the
converging capability in multimode scenarios where CPRI MUX is used with a BBU3910A.
Table 13-3 lists the converging capability in multimode scenarios where CPRI MUX is used
with a BBU3910C.
NOTE
l The 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 If 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 number of UMTS cells supported when the antenna capability is 1T2R.
l The tables list the number of LTE cells supported when the antenna capability is 2T2R.
l The capabilities of a BBU3910A or a converging board in a BBU3900/BBU3910/BBU5900 cannot
exceed the maximum TRX/cell/carrier specifications of a site. For the maximum TRX/cell/carrier
specifications, see the following sections:
"Capacity Specifications" in Product Specifications > Technical Specifications of the BBU3900s
and BBU3910s or Technical Specifications of the BBU3910A of 3900 Series Base Station
Technical Description for the BBU3900, BBU3910, and BBU3910A
"Capacity Specifications" in Product Specifications > Technical Specifications of the BBU5900
of 5900 Series Base Station Technical Description for the BBU5900

SingleRAN
Table 13-1 Converging capabilities of the converging party in multimode scenarios where
CPRI MUX is used with a BBU3900/BBU3910/BBU5900
CPRI Line 2.5 Gbit/s 4.9 Gbit/s 9.8 Gbit/s
Rate
Converging 16 GSM TRXs + 32 GSM TRXs(1) + 32 GSM TRXs(1) +

Capabilities of 4 UMTS cells 8 UMTS cells 16 UMTS cells
a CPRI Link
(GU)
Converging 96 GSM TRXs(2) + 126 GSM TRXs(2) + 126 GSM TRXs(2)(3) +

Capabilities of
24 UMTS cells 24 UMTS cells 24 UMTS cells
a Board (GU)
Converging 16 GSM TRXs + 32 GSM TRXs(1) + 32 GSM TRXs(1) +

Capabilities of LTE 1x10 MHz LTE 1x20 MHz LTE 2x20 MHz
a CPRI Link
(GL)
Converging 96 GSM TRXs(2) + 126 GSM TRXs(2) + 126 GSM TRXs(2)(3) +

Capabilities of
LTE 6x10 MHz LTE 6x20 MHz(4) LTE 8x20 MHz(4)
a Board (GL)
Converging 4 UMTS cells + 8 UMTS cells + 8 UMTS cells +

Capabilities of LTE 1x10 MHz LTE 1x20 MHz LTE 2x20 MHz
a CPRI Link
(UL) or 3 UMTS cells +
LTE 3x20 MHz
Converging 24 UMTS cells + 24 UMTS cells + 24 UMTS cells +

Capabilities of LTE 6x10 MHz LTE 6x20 MHz(4) LTE 8x20 MHz(4)
a Board (UL)
Converging 6 GSM TRXs + 12 GSM TRXs + 24 GSM TRXs +

Capabilities of 2 UMTS cells + 4 UMTS cells + 8 UMTS cells +
a CPRI Link
(GUL) LTE 1x10 MHz LTE 1x20 MHz LTE 2x20 MHz(5)
Converging 36 GSM TRXs + 72 GSM TRXs + 126 GSM TRXs(2) +

Capabilities of 12 UMTS cells + 24 UMTS cells + 24 UMTS cells +
a Board (GUL)
LTE 6x10 MHz LTE 6x20 MHz(4) LTE 8x20 MHz(4)

SingleRAN
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 TRXs 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, capacity specifications in Table 13-1 apply
if these specifications do not exceed the maximum carrier specifications of a site; the maximum
capacity specifications of a site apply if capacity specifications in Table 13-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 are supported by the boards.
l (3) In separate-MPT GU or GL CPRI MUX where a BBU3900 is used, if a WBBPf or an LBBPd
serves as the converging board:

If the CPRI line rate of ports on a converging board is 9.8 Gbit/s, the converging board can provide a
maximum of three converging ports, which must be ports 0, 1, and 2.
If the CPRI line rates of ports on a converging board include 9.8 Gbit/s and 4.9 Gbit/s
simultaneously, the converging board can provide the following combination of converging ports:
Three 9.8 Gbit/s ports and one 4.9 Gbit/s port
Two 9.8 Gbit/s ports and two 4.9 Gbit/s ports
One 9.8 Gbit/s port and four 4.9 Gbit/s ports
A 9.8 Gbit/s converging port must be port 0, 1, or 2.
l (4)When the baseband signals of an LTE cell are processed on the baseband processing board in slot
0, 1, 4, or 5 of a BBU3900, the board supports LTE 4x20 MHz 2T2R.
l (5) Only the UBBP supports GUL CPRI MUX with a CPRI line rate of 9.8 Gbit/s.
NOTICE
l The minimum CPRI line rate of the converging board is 2.5 Gbit/s.
CPRI MUX is used with a BBU3910A
CPRI Line Rate 2.5 Gbit/s 4.9 Gbit/s 9.8 Gbit/s
Converging Capabilities 16 GSM TRXs + 32 GSM TRXs + 32 GSM TRXs +

of a CPRI Link (GU) 4 UMTS cells 8 UMTS cells 12 UMTS cells

of a BBU (GU) 12 UMTS cells 12 UMTS cells 12 UMTS cells

of a CPRI Link (GL) LTE 1x10 MHz LTE 1x20 MHz LTE 2x20 MHz

of a BBU (GL) LTE 6x10 MHz LTE 6x20 MHz LTE 6x20 MHz

SingleRAN
CPRI Line Rate 2.5 Gbit/s 4.9 Gbit/s 9.8 Gbit/s
Converging Capabilities 4 UMTS cells + 6 UMTS cells + 6 UMTS cells +

of a CPRI Link (UL) LTE 1x10 MHz LTE 1x20 MHz LTE 2x20 MHz
or 3 UMTS cells +
LTE 3x20 MHz
Converging Capabilities 6 UMTS cells + 6 UMTS cells + 6 UMTS cells +

of a BBU (UL) LTE 3x10 MHz LTE 3x20 MHz LTE 3x20 MHz

of a CPRI Link (GUL) 2 UMTS cells + 4 UMTS cells + 6 UMTS cells +
LTE 1x10 MHz LTE 1x20 MHz LTE 2x20 MHz

of a BBU (GUL) 6 UMTS cells + 6 UMTS cells + 6 UMTS cells +
LTE 3x10 MHz LTE 3x20 MHz LTE 3x20 MHz
NOTE
The table lists the numbers of GSM TRXs when the following conditions are met:
l The IP over E1 or IP over FE transmission scheme is used.
l The distance between the BBU and the RF module does not exceed 20 km.
l GSM baseband signals are processed by the RF module.
CPRI MUX is used with a BBU3910C
CPRI Line Rate 2.5 Gbit/s 4.9 Gbit/s
Converging Capabilities of a 24 GSM TRXs + 24 GSM TRXs +

CPRI Link (GU) 6 UMTS cells 6 UMTS cells
Converging Capabilities of a 24 GSM TRXs + 24 GSM TRXs +

BBU (GU) 6 UMTS cells 6 UMTS cells
NOTE
The table lists the numbers of GSM TRXs when the following conditions are met:
l The IP over FE transmission scheme is used.
l The distance between the BBU3910C and the RF module reaches the maximum.
l GSM baseband signals are processed by the RF module.
Capacity Specifications
Capacity specifications for each mode with different configurations are calculated as follows:

SingleRAN
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.
Examples of Application Scenarios

Scenario 1: BBU3900, GL 1800 MHz, GSM S2/2/2, LTE 3x20 MHz 2T2R
The capacity requirement of each CPRI link is 2 GSM TRXs + LTE 1x20 MHz 2T2R.
The capacity requirement of each board is 6 GSM TRXs + LTE 3x20 MHz 2T2R.
According to Table 13-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 can be met and
this scenario is supported.
Scenario 2: BBU3900, GL 1800 MHz, GSM S2/2/2, 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 13-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 can be met and this scenario is supported.

SingleRAN
Scenario 3: BBU3900, GL 1800 MHz, GSM S2/2/2/2/2/2, LTE 6x20 MHz 2T2R
According to Table 13-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 scenario is not supported. In this case, contact Huawei engineers
for technical support.
13.2 Cascading Level of the Chain Topology with CPRI

MUX
Table 13-4 lists the maximum cascading level of the chain topology with CPRI MUX. The
maximum cascading level is determined by the cell capacity of each mode and the carrier
capabilities of the converging party. For details on the capabilities of the converging party, see
13.1 CPRI MUX Converging Capabilities.
Table 13-4 Cascading level of the chain topology with CPRI MUX
Mode Maximum Cascading Level
GU 6
GL 4
UL 4
GUL 4
For the distance between the RF modules and the BBU, see "Specifications of CPRI Ports" in
Product Specifications > Technical Specifications of RRUs in 3900 Series Base Station
Technical Description or 5900 Series Base Station Technical Description.
NOTE
If the CPRI MUX converging capability of a base station is exceeded, the status of certain cells served
by the base station may be abnormal.

SingleRAN
CPRI MUX Feature Parameter Description 14 Related Features
14 Related Features
14.1 Prerequisite Features

None
14.2 Mutually Exclusive Features

CPRI MUX is mutually exclusive with the following features:
l GBFD-113701 Frequency Hopping (RF hopping, baseband hopping)
l GBFD-113703 Antenna Frequency Hopping
In separate-MPT scenarios, GU/GL CPRI MUX does not support baseband hopping, RF
frequency hopping between two RF modules, or antenna frequency hopping between the RF
modules:
l Between two RF modules connecting to a GTMUb/GTMUc and a UBRI/UBRIb/
UBBP_G, respectively
l Between two RF modules connecting to a converging board and a UBRI/UBRIb/
UBBP_G, respectively
The GU separate-MPT scenario is used as an example.

SingleRAN
CPRI MUX Feature Parameter Description 14 Related Features
In Figure 14-1, the UBRI/UBRIb/UBBP_G and the GTMUb/GTMUc directly connect to one
RF module, respectively. The GTMUb/GTMUc is the converged board and the WBBPf/
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
WBBPf/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 WBBPf/UBBP_U and UBRI/UBRIb/UBBP_G is not supported.
NOTE
The UBBP_G is a UBBP working in GSM mode.
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.3 Impacted Features

l GBFD-510104 Multi-site Cell
For hardware capability and cell capacity specifications when both CPRI MUX and
Multi-site Cell are used, see Multi-site Cell Feature Parameter Description.

SingleRAN
CPRI MUX Feature Parameter Description 15 Network Impact
15 Network Impact
15.1 System Capacity

No impact.
15.2 Network Performance

No impact.
15.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.

SingleRAN
CPRI MUX Feature Parameter Description 15 Network Impact
CPRI MUX in Co-MPT Scenarios

CPRI MUX in co-MPT scenarios has the following impacts on system reliability:
l CS and PS services of the converged party will be interrupted when a CPRI port of the
converging party becomes faulty or when either of the following operations is performed
by the converging party:
– Software reset or power-off reset on the converging board blocking
– Removing and then inserting the converging board
– Commissioning CPRI ports on the converging board
In general, the interruption lasts shorter than 3 minutes and the longest interruption lasts
no longer than 3.5 minutes.
l If the WBBPf converges data and a UMTS application is deleted or reset, cells on the
converged party will become unavailable for less than 5 minutes.
l If the LBBPd converges data and an LTE application is deleted or reset, cells on the
converged party will become unavailable for less than 5 minutes.
l If the UBRIb converges data and a GSM application is deleted or reset, there is no
impact on the converged party.
l When a UBBP serves as the converging board, deleting or resetting the applications of
the modes configured on this board does not affect the converged party.
l Adding baseband resources to one mode configured on a UBBP interrupts services of
other modes configured on this board, but does not affect services of the converged party
that communicates with this board through the BBU backplane.
NOTE
The service interruption duration does not include the duration of manual operations.

SingleRAN
CPRI MUX Feature Parameter Description 16 Engineering Guidelines
16 Engineering Guidelines
For scenarios where CPRI MUX is used with the RMU solution, see section "Engineering
Guidelines" in RMU Feature Parameter Description.
16.1 When to Use

You can enable the CPRI MUX feature in the following scenarios:
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
16.2 Required Information

The following information must be collected before feature deployment:
l Names of baseband processing boards that are to be used in CPRI MUX
l Names of RF modules that are to be used in CPRI MUX
l Information about optical modules
l Planned site capacity
16.3 Network Planning

RF Planning
N/A
Network Planning
Perform network planning according to chapters 4 CPRI Topology Principles for
Multimode Base Stations, 5 Star Topology with CPRI MUX (BBU3900), 6 Star Topology

SingleRAN
with CPRI MUX (BBU3910), 7 Star Topology with CPRI MUX (BBU3910A), 10 Chain
Topology with CPRI MUX, 11 CPRI MUX with Multimode Load Sharing Topology, and
12 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 chapters 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), 10 Chain Topology
with CPRI MUX, 11 CPRI MUX with Multimode Load Sharing Topology, and 12 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 meet the specifications in 13.1 CPRI MUX Converging
Capabilities.
16.4 Deployment
16.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
16.4.2 Data Preparation
CPRI MUX in Separate-MPT Scenarios

Multimode RF modules that work in multiple modes must follow the following configuration
rules:
l RF modules are configured and monitored by each mode.

SingleRAN
l RF modules must have the same configuration among different modes. Otherwise,
ALM-26274 Inter-System Board Object Configuration Conflict will be reported.
l Table 16-1 lists parameters that must have the same configuration when CPRI MUX is
deployed in separate-MPT scenarios.
Table 16-1 Common parameters

Parameter Parameter ID on Parameter Parameter ID on
Name on GSM (GBTS) Side Name on GSM (eGBTS)/
GSM GSM UMTS/LTE Side
(GBTS) Side (eGBTS)/
UMTS/LTE
Side
Topo Type TT Topo Type TT
Cabinet No. CN Cabinet No. CN
Subrack No. SRN Subrack No. SRN
Slot No. SN Slot No. SN
Board Type BT RRU Type RT
Working WORKINGSTANDAR RRU Work RS

Mode D Standard
The RRU configuration of the converged party takes effect only after RRUs of the converging
party have been configured.
The configuration of the converging party remains unchanged. For details, see the parameter
configuration in the star and chain topologies of the corresponding mode in RF Unit and
Topology Management > Engineering Guidelines > Deployment > Data Preparation.
To enable the CPRI MUX feature, set AT to PEERPORT on the converged party. Table 16-2
provides key parameter settings.
l If GSM (GBTS) is the converged party, specify the parameters in the BTSRXUCHAIN
MO.
l If GSM (eGBTS)/UMTS/LTE is the converged party, specify the parameters in the
RRUCHAIN MO.
Table 16-2 Key parameters in the BTSRXUCHAIN/RRUCHAIN MO

Parameter Parameter ID Setting Notes Data
Name Source
Access Type AT Set this parameter to Engineering

PEERPORT. Design
Head Cabinet HCN Set these parameters to the Engineering

No. cabinet number, subrack Design
number, slot number, and
optical port number of the

SingleRAN

Name Source
Head Subrack HSRN CPRI port on the baseband Engineering

No. board of the peer end, Design
respectively.
Head Slot No. HSN Engineering
Design
Head Port No. HPN Engineering

Design
Local Slot No. LSN l BBU3900: This parameter Equipment

is set to 255 by default and Planning
the slot number does not
need to be configured for
the converged party. If
GSM (GBTS) is the
converged party, this
parameter cannot be
specified.
l BBU3910:
– In separate-MPT
GU/GL CPRI MUX
(GBTS on the GSM
side), set this
parameter to 255, and
do not specify the slot
number for the
converged party.
– In separate-MPT
GU/GL CPRI MUX
(eGBTS on the GSM
side) or UL CPRI
MUX, set the slot
number for the
converged party based
on site conditions.
User-Defined USERDEFRATEN Turn on the user-defined rate User-

Rate EGOSW negotiation switch. defined
Negotiation If this switch is turned on,
Switch users can specify a bit rate set
and a rate change period for
automatic rate negotiation.
Bit Rate Set BITRATESET This parameter specifies the User-

bit rate set for rate defined
negotiation. This parameter
takes effect only when the
user-defined rate negotiation
switch is turned on.

SingleRAN

Name Source
Rate Change RATECHGPERIO This parameter specifies the User-

Period D duration of a port working in defined
each negotiated rate. This
parameter takes effect only
when the user-defined rate
negotiation switch is turned
on.
CPRI MUX in Co-MPT Scenarios

In co-MPT scenarios, if the topology meets the requirements in 5.1 Co-MPT Scenarios or
6.1 Co-MPT Scenarios, CPRI MUX is supported by default.
l Data configurations for the chain or star topology with co-MPT CPRI MUX are the same
as those for the chain or star topology in a single-mode base station.
For detailed data configurations for the chain and star topologies, see RF Unit and
Topology Management Feature Parameter Description > Engineering Guidelines >
Deployment > Data Preparation.
l Data configurations for the multimode load sharing topology with co-MPT CPRI MUX
are the same as those for the load sharing topology 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.
GU+L or GL+U Triple-Mode Dual-Star Topology

For details on this network topology, see 12.1 GU+L Dual-Star Topology and 12.2 GL+U
Dual-Star Topology.
For details on data preparation, see CPRI MUX in Separate-MPT Scenarios and data
preparation for the dual-star topology in RF Unit and Topology Management > Engineering
Guidelines (Multimode Base Station) > Deployment > Data Preparation.
G[U*L] Dual-Star Topology

For details on this network topology, see 12.3 G[U*L] Dual-Star Topology.
For details on data preparation, see CPRI MUX in Co-MPT Scenarios and data preparation
for the dual-star topology in RF Unit and Topology Management > Engineering Guidelines
(Multimode Base Station) > Deployment > Data Preparation.
16.4.3 Activation
In co-MPT scenarios, CPRI MUX is supported by default when the requirements in 5.1 Co-
MPT Scenarios, 6.1 Co-MPT Scenarios, or 7 Star Topology with CPRI MUX

SingleRAN
(BBU3910A) 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.
Using MML Commands

Step 1 On the converging party side, run the ADD RRUCHAIN command to add an RRU/RFU
chain.
Step 2 On the converging party side, run the ADD RRU command to add an RRU to the RRU/RFU
chain.
Step 3 On the converged party side, run the ADD RRUCHAIN command for GSM (eGBTS)/
UMTS/LTE or ADD BTSRXUCHAIN command for GSM (GBTS) to add an RRU/RFU
chain. For key parameter settings, see Table 16-2.
Step 4 On the converged party, run the ADD RRU command for GSM (eGBTS)/UMTS/LTE or
ADD BTSRXUBRD command for GSM (GBTS) to add an RRU/RFU to the RRU/RFU
chain.
----End
NOTE
Data configurations must be the same for RRUs on the converging party and converged party. For detailed
parameter settings, see Table 16-1.
MML Command Examples

l BBU3900:
Figure 16-1 shows the CPRI MUX topology used in the following command example.
Figure 16-1 Separate-MPT UL CPRI MUX with UMTS as the converging party in a
BBU3900
//Adding an RRU/RFU chain on the converging party side

ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HCN=0, HSRN=0, HSN=3,
HPN=0;

SingleRAN
//Adding an RRU to the RRU/RFU chain on the converging party side

ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=UL, RXNUM=2,
TXNUM=2;
//Adding an RRU/RFU chain on the converged party side

ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=PEERPORT, HCN=0, HSRN=0, HSN=3,
HPN=0;
//Adding an RRU to the RRU/RFU chain on the converged party side

TXNUM=2;
l BBU3910:
Figure 16-2 shows the CPRI MUX topology used in the following command example.
Figure 16-2 Separate-MPT UL CPRI MUX with UMTS as the converging party in a
BBU3910
//Adding an RRU/RFU chain on the converging party side

ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HCN=0, HSRN=0, HSN=3,
HPN=0;
//Adding an RRU to the RRU/RFU chain on the converging party side

TXNUM=2;
//Adding an RRU/RFU chain on the converged party side

ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=PEERPORT, HCN=0, HSRN=0, HSN=3,
HPN=0, LSN=2;
//Adding an RRU to the RRU/RFU chain on the converged party side

TXNUM=2;
Using the CME to Perform Single Configuration

Set parameters on the CME according to the operation sequence in Table 16-3. For
instructions on how to perform the CME single configuration, see CME Single Configuration
Operation Guide.

SingleRAN
Table 16-3 Configuring parameters on the CME

SN MO Parameter Name Parameter ID Notes
1 RRUCHAIN Chain No. RCN Add an

RRU/RFU
Topo Type TT chain on the
Access Type AT converging
party side.
Head Cabinet No. HCN
Head Subrack No. HSRN
Head Slot No. HSN
Head Port No. HPN
2 RRU Cabinet No. CN Add an

RRU/RFU to
Subrack No. SRN the RRU/RFU
Slot No. SN chain on the
converging
RRU Chain No. RCN party side.
RRU Type RT
RF Unit Working RS
Mode
3 RRUCHAIN Chain No. RCN Add an

RRU/RFU
Access Type AT converged party
side for GSM
Head Cabinet No. HCN (eGBTS)/
UMTS/LTE.
Head Slot No. HSN
Head Port No. HPN
Local Slot No. LSN
BTSRXUCH Chain No. RCN Add an

AIN RRU/RFU
Access Type AT converged party
side for GSM
Head Cabinet No. HCN (GBTS).
Head Slot No. HSN
Head Port No. HPN

SingleRAN
SN MO Parameter Name Parameter ID Notes
4 RRU Cabinet No. CN Add an

RRU/RFU to
Subrack No. SRN the RRU/RFU
Slot No. SN chain on the
converged party
RRU Chain No. RCN side for GSM
(eGBTS)/
RRU Type RT UMTS/LTE.
RF Unit Working RS
Mode
BTSRXUBR Board Type BT Add an

D RRU/RFU to
Cabinet No. CN the RRU/RFU
Subrack No. SRN chain on the
converged party
Slot No. SN side for GSM
(GBTS).
RXU Chain No. RXUCHAINNO
BTSRXUBP Working Mode WORKINGSTA

NDARD
NOTE
Data configurations must be the same for RRUs on the converging party and converged party. For detailed
parameter settings, see Table 16-1.
Using the CME to Perform Batch Modification

This feature does not support batch modification using the CME.
16.4.4 Activation Observation

After the configured data is activated, check whether RF module-related alarms are reported
on the Alarm/Event tab page of the LMT or U2000 for GSM, UMTS, or LTE. For details on
RF module-related alarms, see 16.7.1 Related Alarms.
1. Check whether the status of RF modules is normal.

– Separate-MPT Scenarios
On the BSC LMT or U2000, run the DSP BTSBRD command to check whether RF
modules on the GSM (GBTS) side function properly.
On the LMT or U2000 for the 3900 series base station, run the DSP BRD command
to check whether RF modules on the GSM (eGBTS) side function properly.
to check whether RF modules on the UMTS side function properly.
to check whether RF modules on the LTE side function properly.

SingleRAN
– Co-MPT Scenarios
to check whether RF modules function properly.
2. Check whether the CPRI line rate of the converging port is as planned.
– Separate-MPT scenarios
On the LMT or U2000 for the 3900 series base station, run the DSP CPRIPORT
command on the converging party side and check whether the CPRI line rate of the
converging port is as planned.
– Co-MPT scenarios
Run the DSP CPRIPORT command to check whether the CPRI line rate of the
converging port is as planned.
16.4.5 Deactivation
This feature does not need to be deactivated.
16.4.6 Reconfiguration
You can add an RRU to or remove an RRU from a cascading chain in the star or chain
topology with CPRI MUX.
For how to add RF modules to or remove them 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 cascading chain
To add an RRU to a cascading 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 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 cascading chain
To remove an RRU from a cascading 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 RMV BTSRXUBRD
for GSM (GBTS).
c. Adjust the original cable connections and remove an RRU from the specified
position.

SingleRAN
d. Run the MOD RRUCHAIN command on the converged party to remove the
breaking point.
Co-MPT Scenarios
l Adding an RRU to a cascading chain
To add an RRU to a cascading 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 cascading chain
To remove an RRU from a cascading 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.
16.5 Performance Monitoring

N/A
16.6 Parameter Optimization

N/A
16.7 Possible Issues
16.7.1 Related Alarms

Table 16-4 lists alarms related to the CPRI MUX feature. For detailed troubleshooting
operations, see 3900 & 5900 Series Base Station Alarm Reference, BSC6900 GSM Alarm
Reference, and BSC6910 GSM Alarm Reference.
Table 16-4 CPRI MUX-related alarms
Alarm ID Alarm Name Description
ALM-26215 Inter-Board Service Link This alarm is reported if inter-board

Failure communication fails in the BBU.
Services of the converged party are
affected.

SingleRAN
ALM-26235 RF Unit Maintenance Link This alarm is reported if the

Failure maintenance link between the BBU
and the RF unit malfunctions. The
alarm is triggered by any of the
following faults and is reported by
the converged party in separate-MPT
scenarios: Optical modules on the
baseband board of the converging
party become faulty. Links used to
forward data from the converged
party to the converging party through
the BBU backplane become faulty or
resources are insufficient. The
baseband board of the converging
party is not installed, powered on,
configured or the baseband board
experiences hardware failures. The
hardware capability of the baseband
boards of the two parties is
insufficient to support data
converging through the BBU
backplane. Aggregation relationships
are incorrectly configured.
ALM-26270 Inter-System In multi-mode configuration, this

Communication Failure alarm is reported if the main control
board in the current mode cannot
communicate with the main control
board in the other mode. If the two
main control boards cannot
communicate with each other for
about 45s, this alarm is reported. If
the two main control boards can
communicate with each other for
about 30s consecutively, this alarm is
cleared.
ALM-26272 Inter-System RF Unit In multi-mode configuration, this

Parameter Settings Conflict alarm is reported if the parameter
settings of an RF unit in a mode are
inconsistent with those of the same
RF unit in the other mode, such as
the working mode or other RF
parameters.

SingleRAN
ALM-26274 Inter-System Board Object In multi-mode configuration, this

Configuration Conflict alarm is reported if the cabinet/
subrack/slot configuration of a board
is inconsistent in different modes, the
cabinet/subrack/slot configuration of
different boards is the same in
different modes, or a board that
supports only one mode is used by
multiple modes at the same time.
ALM-26277 Inter-System Control Rights In multi-mode configuration, this

Conflict alarm is reported if the loading
control rights are not configured or
are inconsistent between different
modes in the base station.
ALM-26278 RF Unit Working Mode and In multi-mode configuration, this

Board Capability Mismatch alarm is reported if the configured
working mode of an RF unit does not
match the actual capability of the RF
unit.
ALM-28016 GSM Local Cell Unusable In a CPRI MUX-based topology with

the GSM mode, multiple modes use
ALM-28017 GSM Local Cell Capability one CPRI link to transmit data. As a
Decline result, bandwidth on the GSM side
ALM-28006 Radio Signaling Link may be insufficient and this alarm is
Disconnected reported. This alarm is also reported
when an RF module on a hybrid
ALM-21801 GSM Cell out of Service cascaded CPRI link does not support
the GSM mode.
ALM-28203 Local Cell Unusable When CPRI MUX is implemented,

multiple modes use one CPRI link to
ALM-28206 Local Cell Capability transmit data. As a result, bandwidth
Decline on the UMTS side may be
insufficient and this alarm is
reported.
ALM-29240 Cell Unavailable When CPRI MUX is implemented,

multiple modes use one CPRI link to
ALM-29243 Cell Capability Degraded transmit data. As a result, bandwidth
on the LTE side may be insufficient
and this alarm is reported.
ALM-26262 Clock source exception In a CPRI MUX scenario with clock

alarms mutual lock, if the major standard
becomes abnormal, this alarm is
reported by other standards.

SingleRAN
16.7.2 MML Commands for Maintenance

In separate-MPT scenarios, the converging and converged parties have their own O&M
platforms. In co-MPT scenarios, the converging and converged parties share the same O&M
platform.
NOTE
After CPRI MUX is implemented, alarms will be reported if any exceptions occur. Clear the alarms
according to the alarm reference.
Table 16-5 MML commands for maintenance

MML Command Application Support by the Support by the
Scenario Converging Party Converged Party
(Only in Separate-
MPT Scenarios)
DSP RRUCHAIN Use this command Fully supported Fully supported

to query the number
of RRUs carried on
an RRU chain or
ring over an optical
port on the
converging party
and the number of
cascading levels.
DSP Use this command Fully supported Fully supported

RRUCHAINPHYT to query information
OPO about the RRUs
connected to the
CPRI port.
DSP CPRIPORT Use this command Fully supported Partially supported:

to query real-time Use this command
data rates and other to query data rates
information about on the CPRI port
the optical port on and the status of the
the panel of the aggregation port.
converging party.
Use this command
to query whether the
optical port is in the
aggregation state.

SingleRAN
MML Command Application Support by the Support by the

Scenario Converging Party Converged Party
(Only in Separate-
MPT Scenarios)
DSP CPRILBR Use this command Fully supported Partially supported:

to query the current Use this command
CPRI line rate of the to query the current
specified chain or CPRI line rate of the
ring, the maximum specified chain/ring
CPRI line rate of the and the maximum
baseband processing CPRI line rate of
board, the maximum each RRU or RFU
CPRI line rate of on a chain or ring.
each RRU or RFU
on a chain or ring.
STR Use this command Supported Not supported

CPRILBRNEG to start negotiation
of the line rate on
the optical port on
the panel. Run this
command if the
RRU chain cannot
be set up or the
chain cannot operate
at the maximum line
rate due to changes
in parameter settings
of the RRU chain.
Executing this
command causes
link disconnection,
interrupting
services.
MOD RRUCHAIN Use this command Supported Not supported

to set breakpoints on
an RRU chain.
L: DSP CELL Use this command Supported Supported

U: DSP ULOCELL to query the cell
status. Cell setup
G(GBTS): DSP fails and cell
GTRXSTAT capability degrades
G(eGBTS): DSP when CPRI
GTRX bandwidth is
insufficient.

SingleRAN
CPRI MUX Feature Parameter Description 17 Parameters
17 Parameters
Table 17-1 Parameters

Parame NE MML Feature Feature Description
ter ID Comma ID Name
nd
TT BTS390 ADD None None Meaning: Indicates the type of the topology. In a ring
0, RRUCH topology, the service data is transmitted on the fiber
BTS390 AIN optic cable that carries the HDLC link. In a load
0 MOD sharing topology, the service data is transmitted on
WCDM RRUCH two fiber optic cables simultaneously, which enhances
A, AIN 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
BTS590 RRUCH CPRI fiber optic cables to simultaneously transmit
0, AINPH service data.
BTS590 YTOPO
GUI Value Range: CHAIN(CHAIN), RING(RING),
0 LST LOADBALANCE(LOADBALANCE),
WCDM RRUCH TRUNK_CHAIN(TRUNK_CHAIN)
A, AIN
BTS590 Unit: None
0 LTE Actual Value Range: CHAIN, RING,
LOADBALANCE, TRUNK_CHAIN
Default Value: None

SingleRAN

nd
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
BTS590 LOPRR
0, U
BTS590
0
WCDM
A,
BTS590
0 LTE
SRN BTS390 DSP None None Meaning: Indicates the number of the subrack where
0, RRUCL the RRU is located.
0 SET
WCDM Unit: None
RRUCL
BTS390 Default Value: None
0 LTE, TST
BTS590 LOPRR
0, U
BTS590
0
WCDM
A,
BTS590
0 LTE

SingleRAN

nd
SN BTS390 DSP None None Meaning: Indicates the number of the slot where the
0, RRUCL RRU is located.
0 SET
WCDM Unit: None
RRUCL
0 LTE, TST
BTS590 LOPRR
0, U
BTS590
0
WCDM
A,
BTS590
0 LTE
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,
BTS590 MPMU, MPRF, AIRU, MRIU, GRRU, LRRU,
0, ORRU
0
WCDM
A,
BTS590
0 LTE

SingleRAN

nd
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),
BTS590 UL(UMTS_LTE), ULFTD(UMTS_LTE_FDD_TDD),
0, CU(CDMA_UMTS), GU(GSM_UMTS),
BTS590 GUT(GSM_UMTS_LTE_TDD),
0 GUL(GSM_UMTS_LTE),
WCDM GULFTD(GSM_UMTS_LTE_FDD_TDD), MO(NB-
A, IoT), LM(LTE_FDD_NB-IoT), CM(CDMA_NB-
BTS590 IoT), CLM(CDMA_LTE_FDD_NB-IoT),
0 LTE 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

SingleRAN

nd
AT BTS390 ADD None None Meaning: Indicates the access type of the board on an
0, RRUCH RRU chain/ring. When Access Type is set to
BTS390 AIN LOCALPORT(local port), the BBP connects to the
0 MOD board on an RRU chain/ring through the CPRI port.
WCDM RRUCH When Access Type is set to PEERPORT(peer port),
A, AIN 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.
BTS590 RRUCH
AIN GUI Value Range: LOCALPORT(local port),
0, PEERPORT(peer port)
BTS590
0 Unit: None
WCDM Actual Value Range: LOCALPORT, PEERPORT
A, Default Value: LOCALPORT(local port)
BTS590
0 LTE
HCN BTS390 ADD None None Meaning: Indicates the cabinet number of the board
0, RRUCH where the head CPRI port is located.
BTS390 AIN GUI Value Range: 0~15
0 MOD
WCDM Unit: None
RRUCH
A, AIN Actual Value Range: 0~15
0 LTE, DSP
BTS590 RRUCH
0, AINPH
BTS590 YTOPO
0 LST
WCDM RRUCH
A, AIN
BTS590
0 LTE

SingleRAN

nd
HSRN BTS390 ADD None None Meaning: Indicates the subrack number of the board
BTS390 AIN GUI Value Range: 0~1,60~254
0 MOD
WCDM Unit: None
RRUCH
A, AIN Actual Value Range: 0~1,60~254
0 LTE, DSP
BTS590 RRUCH
0, AINPH
BTS590 YTOPO
0 LST
WCDM RRUCH
A, AIN
BTS590
0 LTE
HSN BTS390 ADD None None Meaning: Indicates the slot number of the board
0 MOD
WCDM Unit: None
RRUCH
A, AIN Actual Value Range: 0~6
0 LTE, DSP
BTS590 RRUCH
0, AINPH
BTS590 YTOPO
0 LST
WCDM RRUCH
A, AIN
BTS590
0 LTE

SingleRAN

nd
HPN BTS390 ADD None None Meaning: Indicates the number of the head CPRI port.
0, RRUCH GUI Value Range: 0~11
BTS390 AIN
0 Unit: None
MOD
WCDM RRUCH Actual Value Range: 0~11
A, AIN Default Value: None
BTS390
0 LTE, DSP
BTS590 RRUCH
0, AINPH
BTS590 YTOPO
0 LST
WCDM RRUCH
A, AIN
BTS590
0 LTE
LSN BTS390 ADD None None Meaning: Indicates the slot number of the converged
0, RRUCH party in CPRI MUX. If this parameter is set to 255,
BTS390 AIN the slot number of the converged party is not
0 MOD specified. When the converging party is in a
WCDM RRUCH BBU3900, this parameter can be left unspecified.
A, AIN When the converging party is in a BBU3910 or
BTS390 BBU5900, this parameter must be specified.
0 LTE, LST
RRUCH GUI Value Range: 0~6,255
BTS590
0, AIN Unit: None
BTS590 Actual Value Range: 0~6,255
0 Default Value: 255
WCDM
A,
BTS590
0 LTE

SingleRAN

nd
RCN BTS390 ADD None None Meaning: Indicates the ID of the RRU chain. It
0, RRUCH uniquely identifies a chain within a base station.
0 DSP
WCDM Unit: None
CPRILB
A, R Actual Value Range: 0~249
0 LTE, DSP
BTS590 RRUCH
0, AIN
BTS590 LST
0 RRUCH
WCDM AIN
A, MOD
BTS590 RRUCH
0 LTE AIN
RMV
RRUCH
AIN
STR
CPRILB
RNEG
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
0 LTE,
BTS590
0,
BTS590
0
WCDM
A,
BTS590
0 LTE

SingleRAN
CPRI MUX Feature Parameter Description 18 Counters
18 Counters
There are no specific counters associated with this feature.

SingleRAN
CPRI MUX Feature Parameter Description 19 Glossary
19 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.

SingleRAN
CPRI MUX Feature Parameter Description 20 Reference Documents
20 Reference Documents
1. 3900 Series Base Station Technical Description

2. 5900 Series Base Station Technical Description
3. BBU5900 Hardware Description
4. 3900 Series BBU Hardware Description
5. Installation guide of relevant base stations
6. Site maintenance guide of relevant base stations
7. RF Unit and Topology Management Feature Parameter Description
8. RMU Feature Parameter Description
9. BSC6900 GSM MML Command Reference
10. 3900 Series Base Station MML Command Reference
11. 3900 Series Base Station Alarm Reference


Cpri Mux (Sran12.1 04)

Uploaded by

Copyright:

Available Formats

Cpri Mux (Sran12.1 04)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cpri Mux (Sran12.1 04)

Uploaded by

Copyright:

Available Formats

SingleRAN

CPRI MUX Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2017-10-17) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

3 BBUs and Boards That Support CPRI MUX............................................................................ 6

4 CPRI Topology Principles for Multimode Base Stations.................................................... 12

6 Star Topology with CPRI MUX (BBU3910)............................................................................ 28

7 Star Topology with CPRI MUX (BBU3910A)......................................................................... 34

Issue 04 (2017-10-17) Huawei Proprietary and Confidential ii

9 Star Topology with CPRI MUX (BBU5900)............................................................................ 36

10 Chain Topology with CPRI MUX.......................................................................................... 40

13 Specifications of the CPRI MUX Feature..............................................................................48

Issue 04 (2017-10-17) Huawei Proprietary and Confidential iii

Issue 04 (2017-10-17) Huawei Proprietary and Confidential iv

1 About This Document

This document applies to macro base stations including:

1.2 Intended Audience

l Need to understand the features described herein

Issue 04 (2017-10-17) Huawei Proprietary and Confidential 1

1.3 Change History

Change Change Description Parameter

Feature Added support for the BBU5900. None

Editorial None None

Change Change Description Parameter

Feature None None

Issue 04 (2017-10-17) Huawei Proprietary and Confidential 2

Change Change Description Parameter

Feature None None

Editorial Added figures showing topology examples in MML None

SRAN12.1 Draft A (2016-12-31)

Change Change Description Parameter

Feature Supported the following relationships between the None

Editorial Deleted the description "In separate-MPT scenarios, CPRI None

Added an example to 14.2 Mutually Exclusive Features. None

1.4 Differences Between Base Station Types

Issue 04 (2017-10-17) Huawei Proprietary and Confidential 3

Multimode RF modules are connected to a single-mode or multimode(1) baseband processing

Figure 2-1 Working principle of CPRI MUX

Issue 04 (2017-10-17) Huawei Proprietary and Confidential 4

Issue 04 (2017-10-17) Huawei Proprietary and Confidential 5

3 BBUs and Boards That Support CPRI MUX

3.1 BBU3900 Boards That Support CPRI MUX

UL WBBPf/ Slot 2 or 3 LBBPd/ One LBBPd or

Issue 04 (2017-10-17) Huawei Proprietary and Confidential 6

Mode on Converging Slot of the Converged Slot of the

LBBPd/ Slot 2 or 3 WBBPa/ One WBBPf or

GU WBBPf/ Slot 2 or 3 GTMUb/ Slot 6

GL LBBPd/ Slot 2 or 3 GTMUb/ Slot 6

UL WBBPf, LBBPd, or Slot 2 or 3 l If LTE serves as the converged party,

GU UBRIb(4) Slot 0 or 1 l If LTE serves as the converged party,

Issue 04 (2017-10-17) Huawei Proprietary and Confidential 7

Mode Converging Board Slot of the Topology Constraint

UBBP_G/U/GU/GL/ Slot 2 or 3 l If a BBU is configured with a

GL UBRIb Slot 1 Same as those for GU

GUL UBRIb Slot 1 Same as those for GU

Issue 04 (2017-10-17) Huawei Proprietary and Confidential 8