Cpri Mux (Sran16.1 - 01)

SingleRAN
CPRI MUX Feature Parameter

Description
Issue 01
Date 2020-03-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. 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: https://www.huawei.com
Email: support@huawei.com
Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. i

SingleRAN
CPRI MUX Feature Parameter Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 SRAN16.1 01 (2020-03-30)..................................................................................................................................................1
1.2 SRAN16.1 Draft A (2020-01-20)........................................................................................................................................ 1
2 About This Document.............................................................................................................3

2.1 General Statements................................................................................................................................................................ 3
2.2 Applicable RAT......................................................................................................................................................................... 4
2.3 Features in This Document.................................................................................................................................................. 4
3 Overview....................................................................................................................................5
3.1 Introduction............................................................................................................................................................................... 5
3.2 Application Scenarios............................................................................................................................................................. 6
4 Boards That Support CPRI MUX and Constraints.............................................................8

4.1 BBU3900 Boards Supporting CPRI MUX and Constraints......................................................................................... 8
4.1.1 Co-MPT Scenarios................................................................................................................................................................ 8
4.1.2 Separate-MPT Scenarios................................................................................................................................................. 10
4.2 BBU3910 Boards Supporting CPRI MUX and Constraints....................................................................................... 11
4.2.1 Co-MPT Scenarios............................................................................................................................................................. 12
4.3 BBU5900 Boards Supporting CPRI MUX and Constraints....................................................................................... 14
4.3.1 Co-MPT Scenarios............................................................................................................................................................. 15
4.4 BBU3910A Boards Supporting CPRI MUX and Constraints.................................................................................... 17
4.5 BBU3910C Boards Supporting CPRI MUX and Constraints.................................................................................... 18
4.6 BBU5900A Supporting CPRI MUX and Constraints................................................................................................... 18
5 CPRI MUX Networking Example........................................................................................ 20

5.1 Star Topology with CPRI MUX.......................................................................................................................................... 20
5.1.1 Star Topology with CPRI MUX (BBU3900)............................................................................................................... 20
5.1.1.1 Co-MPT Scenarios.......................................................................................................................................................... 20
5.1.1.2 Separate-MPT Scenarios.............................................................................................................................................. 28
5.1.2.1 Co-MPT Scenarios.......................................................................................................................................................... 31
Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. ii

SingleRAN
5.1.3.1 Co-MPT Scenarios.......................................................................................................................................................... 36

5.1.4 Star Topology with CPRI MUX (BBU3910A).............................................................................................................40
5.1.5 Star Topology with CPRI MUX (BBU3910C)............................................................................................................. 40
5.1.6 Star Topology with CPRI MUX (BBU5900A).............................................................................................................41
5.2 Chain Topology with CPRI MUX.......................................................................................................................................42
5.2.1 Intra-Mode Cascading......................................................................................................................................................43
5.2.2 Inter-Mode Cascading...................................................................................................................................................... 44
5.2.2.1 Co-MPT Scenarios.......................................................................................................................................................... 44
5.3 Load Sharing Topology with CPRI MUX........................................................................................................................ 47
5.4 Dual-Star Topology with CPRI MUX............................................................................................................................... 48
6 Specifications of CPRI MUX Access Capabilities............................................................ 51

6.1 CPRI MUX Access Capabilities.......................................................................................................................................... 51
6.2 Capacity Specifications........................................................................................................................................................55
6.3 Examples.................................................................................................................................................................................. 56
7 Network Analysis.................................................................................................................. 58
7.1 Benefits..................................................................................................................................................................................... 58
7.2 Impacts..................................................................................................................................................................................... 58
7.2.1 Services..................................................................................................................................................................................58
7.2.2 Features................................................................................................................................................................................ 59
7.2.3 System Capacity................................................................................................................................................................. 60
7.2.4 Network Performance...................................................................................................................................................... 60
8 Requirements......................................................................................................................... 61
8.1 Licenses.................................................................................................................................................................................... 61
8.2 Software................................................................................................................................................................................... 61
8.3 Hardware................................................................................................................................................................................. 62
8.4 Networking............................................................................................................................................................................. 62
8.5 Others....................................................................................................................................................................................... 62
9 Operation and Maintenance.............................................................................................. 63

9.1 When to Use........................................................................................................................................................................... 63
9.2 Precautions.............................................................................................................................................................................. 63
9.3 Data Configuration...............................................................................................................................................................64
9.3.1 Data Preparation............................................................................................................................................................... 64
9.3.2 Using MML Commands................................................................................................................................................... 67
9.3.3 Using the MAE-Deployment.......................................................................................................................................... 69
9.4 Activation Verification......................................................................................................................................................... 69
9.5 Network Monitoring............................................................................................................................................................ 69
9.6 Reconfiguration..................................................................................................................................................................... 71
10 Parameters............................................................................................................................73
Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. iii

SingleRAN
11 Counters................................................................................................................................ 74
12 Terminology..........................................................................................................................75
13 Reference Documents........................................................................................................ 76
Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. iv

SingleRAN
CPRI MUX Feature Parameter Description 1 Change History
1 Change History
This chapter describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation
1.1 SRAN16.1 01 (2020-03-30)

This issue includes the following changes.
Technical Changes
None
Editorial Changes
None
1.2 SRAN16.1 Draft A (2020-01-20)

This issue introduces the following changes to SRAN15.1 05 (2019-10-25).
Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. 1

SingleRAN
CPRI MUX Feature Parameter Description 1 Change History
Technical Changes
Change Description Parameter Change
Added support for the ULN CPRI MUX None

topology in co-MPT scenarios. For
details, see 4.2 BBU3910 Boards
Supporting CPRI MUX and
Constraints, 4.3 BBU5900 Boards
Constraints, and 4.6 BBU5900A
Constraints.
Added support for GULN quadruple- None

mode inter-BBU dual-star topology in
separate-MPT scenarios. For details,
see 3.2 Application Scenarios and 5.4
Dual-Star Topology with CPRI MUX.
Changed the name of CME to MAE- None

Deployment.
Editorial Changes
None

SingleRAN
CPRI MUX Feature Parameter Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
Feature Parameter Description documents are intended to acquaint readers with:
● The technical principles of features and their related parameters

● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.
Trial Features
Trial features are features that are not yet ready for full commercial release for
certain reasons. For example, the industry chain (terminals/CN) may not be
sufficiently compatible. However, these features can still be used for testing
purposes or commercial network trials. Anyone who desires to use the trial
features shall contact Huawei and enter into a memorandum of understanding
(MoU) with Huawei prior to an official application of such trial features. Trial

SingleRAN
CPRI MUX Feature Parameter Description 2 About This Document
features are not for sale in the current version but customers may try them for
free.
Customers acknowledge and undertake that trial features may have a certain
degree of risk due to absence of commercial testing. Before using them, customers
shall fully understand not only the expected benefits of such trial features but also
the possible impact they may exert on the network. In addition, customers
acknowledge and undertake that since trial features are free, Huawei is not liable
for any trial feature malfunctions or any losses incurred by using the trial features.
Huawei does not promise that problems with trial features will be resolved in the
current version. Huawei reserves the rights to convert trial features into
commercial features in later R/C versions. If trial features are converted into
commercial features in a later version, customers shall pay a licensing fee to
obtain the relevant licenses prior to using the said commercial features. If a
customer fails to purchase such a license, the trial feature(s) will be invalidated
automatically when the product is upgraded.
2.2 Applicable RAT

This document applies to GSM, UMTS, LTE FDD, LTE TDD, NB-IoT, and NR.
Unless otherwise specified, in this document, LTE and eNodeB always include FDD,
TDD, and NB-IoT. In scenarios where they need to be distinguished, LTE FDD, LTE
TDD, and LTE NB-IoT are used. The same rules apply to eNodeB.
Unless otherwise specified, in this document, NR and gNodeB always include FDD
and TDD. In scenarios where they need to be distinguished, NR FDD and NR TDD
are used. The same rules apply to gNodeB.
The "G", "C", "U", "L", "T", "M", "N", "N (FDD)", and "N (TDD)" in RAT acronyms
refer to GSM, CDMA, UMTS, LTE FDD, LTE TDD, LTE NB-IoT, NR, NR FDD, and NR
TDD, respectively.
2.3 Features in This Document

This document describes the following features.
Feature ID Feature Name Chapter/Section
- CPRI MUX 9 Operation and Maintenance

SingleRAN
CPRI MUX Feature Parameter Description 3 Overview
3 Overview
This document applies to 3900 and 5900 series base stations, excluding DBS3900
and DBS5900 LampSite base stations. For CPRI MUX in DBS3900 and DBS5900
LampSite base stations, see CPRI MUX (LampSite).
This document does not involve any basic CPRI topologies, such as chain, star, ring,
dual-star, and load-sharing topologies. For details, see RF Unit and Topology
Management.
This document does not involve the CPRI trunk chain and description of the trunk
chain topology with CPRI MUX. For details, see RMU.
If LTE and NR uplink spectrum sharing is enabled, data convergence is supported
between LTE and NR. For details, see LTE FDD and NR Uplink Spectrum Sharing.
This document applies only to CPRIs, and does not apply to enhanced common
public radio interfaces (eCPRIs). For details about eCPRI MUX, see eCPRI.
3.1 Introduction
CPRI MUX enables multiple network modes to use a common public radio
interface (CPRI) link for data transmission.
Figure 3-1 shows CPRI MUX principles when data of multiple network modes is
converged. The board of network mode B is connected to the board of network
mode A through the backplane. This way, data of network mode B is converged
on the board of network mode A. Then, the CPRI optical fiber connecting the
board of network mode A and a multimode RF module can carry data of both
network modes A and B.
The board of network mode A serves as the converging board and network mode
A is the converging party. The board of network mode B serves as the converged
board and network mode B is the converged party.

SingleRAN
Figure 3-1 CPRI MUX principles when data of multiple network modes is
converged
3.2 Application Scenarios

In multimode base stations, CPRI MUX can work with a variety of CPRI topologies
to suit the requirements of different application scenarios. The following table
provides further details.
Topology Application Scenario Related Section/

Document
Star topology with CPRI Most areas, especially densely 5.1 Star Topology
MUX populated areas (The star with CPRI MUX
topology with CPRI MUX is
recommended for co-MPT base
stations.)
Chain topology with Long and narrow areas, such as 5.2 Chain
CPRI MUX highways and railways Topology with
CPRI MUX
Multimode load sharing ● Insufficient CPRI bandwidth 5.3 Load Sharing

topology with CPRI for co-MPT base stations Topology with
MUX ● Reconstruction from CPRI MUX
separate-MPT base stations
using the dual-star topology
to co-MPT base stations
using the dual-star topology
Dual-star topology with Separate-MPT triple-mode/ 5.4 Dual-Star

CPRI MUX quadruple-mode base stations Topology with
CPRI MUX
Trunk chain topology Insufficient CPRI links for long- RMU Feature
with CPRI MUX distance transmission or Parameter
insufficient CPRI bandwidth Description

SingleRAN
From SRAN12.0 onwards, star, chain, load sharing, and dual-star topologies with CPRI MUX
are supported by GM, UM, GUM, GLM, ULM, and GULM multimode base stations.
● CPRI MUX in GM or GLM base stations is used in the same way in GL base stations.
● CPRI MUX in UM or ULM base stations is used in the same way in UL base stations.
● CPRI MUX in GUM or GULM base stations is used in the same way in GUL base stations.
For details about CPRI MUX in GM/GLM, UM/ULM, and GUM/GULM base stations, see CPRI
MUX in GL, UL, and GUL multimode base stations respectively in 5.1 Star Topology with
CPRI MUX, 5.2 Chain Topology with CPRI MUX, 5.3 Load Sharing Topology with CPRI
MUX, and 5.4 Dual-Star Topology with CPRI MUX. For the BBU models and boards that
support NB-IoT, see BBU3900 and BBU3910 Hardware Description, BBU5900 Hardware
Description, and BBU5900A Hardware Description.

SingleRAN
CPRI MUX Feature Parameter Description 4 Boards That Support CPRI MUX and Constraints
4 Boards That Support CPRI MUX and

Constraints
BBUs that support CPRI MUX include BBU3900/BBU3910/BBU5900/BBU5900A/

BBU3910A/BBU3910C.
● See 4.1 BBU3900 Boards Supporting CPRI MUX and Constraints for details
on CPRI MUX used with a BBU3900.
● See 4.4 BBU3910A Boards Supporting CPRI MUX and Constraints for details
on CPRI MUX used with a BBU3910A.
● See 4.5 BBU3910C Boards Supporting CPRI MUX and Constraints for details
on CPRI MUX used with a BBU3910C.
● See 4.6 BBU5900A Supporting CPRI MUX and Constraints for details on
CPRI MUX used with a BBU5900A.
This chapter describes only BBU boards that support CPRI MUX and constraints. For more
details about BBUs and BBU boards, see BBU3900 and BBU3910 Hardware Description,
BBU5900 Hardware Description, and BBU5900A Hardware Description.
4.1 BBU3900 Boards Supporting CPRI MUX and

Constraints
4.1.1 Co-MPT Scenarios

Topology Constraints
The constraints on CPRI MUX used with a BBU3900 in co-MPT scenarios are listed
as follows:
● Converging and converged parties must be deployed in the same BBU.

SingleRAN
● If the converged party is LTE, the converged board cannot be an LBBPc.

● If the converging or converged party is UMTS, a WBBPf or UBBP_Ux(1) must
be installed in slot 3 or 2.
● In non-baseband extension mode(2), GSM can serve as the converged party,
and GSM RF modules are connected to the converging board. This eliminates
the need for adding a GSM baseband processing unit (BBP) or baseband radio
interface unit (BRI).
In GSM baseband extension mode(3), a UBBP_Gx(1) must be installed in slot 1,
2, or 3.
● If the converging board is a UBRIb, GSM supports the non-baseband
extension mode only.
In UL or GUL CPRI MUX, if the converging board is a UBRIb, and UMTS and
LTE serve as converged parties, then the cells of the converged parties must
be served by the specified baseband equipment group. Such a baseband
equipment group can only include single-mode baseband processing units.
In UL CPRI MUX, if the converging board is a UBRIb(4), a WBBPf or
UBBP_Ux(1) must be installed in slot 2 or 3.
● If a BBU is configured with a co-BBP board, and network modes involved in
CPRI MUX are the same as or included in the network modes that work in co-
BBP mode, connect this co-BBP board to RF modules. For example, if a BBU is
configured with a UBBP_GL, the GL CPRI port connecting to RF modules is
provided by this UBBP_GL instead of a GO or LO BBP/BRI.
● (1)UBBP_Ux indicates that the working mode of this UBBP includes UMTS. UBBP_Gx
indicates that the working mode of this UBBP includes GSM.
● (2)In non-baseband extension mode, GSM baseband signals are processed by RRUs
instead of a UBBP_Gx in the BBU.
● (3) In GSM baseband extension mode, GSM baseband signals are processed by a
UBBP_Gx. In this case, a UBBP_Gx must be configured in the BBU.

● (4) If CPRI ports on a UBRIb work at a data rate higher than 4.9 Gbit/s, each port can
carry services of two network modes. If the CPRI ports work at a data rate less than or
equal to 4.9 Gbit/s, each port can carry GUL services. If GLM/ULM concurrency is
applied, GLM/ULM is equivalent to two network modes when CPRI compression is not
used for LTE FDD and equivalent to three network modes when CPRI compression is
used for LTE FDD.
Boards and Their Slot Assignment

Table 4-1 describes BBU3900 boards that can serve as the converging board of
CPRI MUX in co-MPT scenarios and their slot assignment.
See Topology Constraints for BBU3900 boards that can serve as the converged
board of CPRI MUX in co-MPT scenarios and their slot assignment.

SingleRAN
Table 4-1 BBU3900 boards that can serve as the converging board of CPRI MUX in
co-MPT scenarios and their slot assignment
Network Converging Board Slot of the

Mode Served Converging Board
by the CPRI
Port
UL UBRIb Slot 1
UL WBBPf, LBBPd, or Slot 2 or 3

UBBP_U/L/GU/GL/UL/GUL
GU UBRIb Slot 0 or 1
UBBP_G/U/GU/GL/UL/GUL Slot 2 or 3
GL UBRIb Slot 1
UBBP_G/L Slot 1, 2, or 3
UBBP_GU/GL/UL/GUL Slot 2 or 3
GUL UBRIb Slot 1
UBBP_G/U/L/GU/GL/UL/GUL Slot 2 or 3
In this table, UBBP_G/U/L/GU/GL/UL/GUL indicates that this UBBP works in GO,

UO, LO, GU, GL, UL, or GUL mode. For example, UBBP_UL indicates that this
UBBP works in UL mode, and there is a possibility that it supports GSM, UMTS,
and LTE.
4.1.2 Separate-MPT Scenarios
The constraints on CPRI MUX used with a BBU3900 in separate-MPT scenarios are
listed as follows:
● Converging and converged parties must be deployed in the same BBU. Inter-
BBU CPRI MUX is not supported.
● Converging and converged boards must be configured in the same BBU. The
converging party cannot serve as the converged party. Data of a network
mode can only be converged to one board.
● Only UMTS and LTE can serve as the converging party. If CPRI MUX involves
GSM, GSM supports the non-baseband extension mode only.
● Each BBU provides a maximum of six ports for data convergence. These ports
must be located on the same WBBPf, LBBPd, UBBP_U, or UBBP_L.
● When UMTS serves as the converged party, a WBBPf or UBBP_U must be
installed in slot 2 or 3.
● The CPRI ports on the two RRUs serving a dual-RRU cell must be connected
to the BBPs of the same mode.

SingleRAN

Table 4-2 describes BBU3900 boards that support CPRI MUX in separate-MPT
scenarios and their slot assignment.
Table 4-2 BBU3900 boards that support CPRI MUX in separate-MPT scenarios and
their slot assignment
Network Converging Converging Slot of the Converge Slot of
Mode Party Board Converging d Board the
Served Board Converge
by the d Board
CPRI
Port
UL UMTS WBBPf Slot 2 or 3 LBBPd An LBBPd

UBBP_U UBBP_L or UBBP_L
must be
installed in
slot 3 or 2.
LTE LBBPd Slot 2 or 3 WBBP(1) A WBBPf

UBBP_L UBBP_U or UBBP_U
must be
installed in
slot 3 or 2.
GU UMTS WBBPf Slot 2 or 3 GTMUb Slot 6(2)

UBBP_U GTMUc
GL LTE LBBPd Slot 2 or 3 GTMUb Slot 6(2)

UBBP_L GTMUc
In this table, UBBP_G/U/L/GU/GL/UL/GUL indicates that this UBBP works in GO,

UO, LO, GU, GL, UL, or GUL mode. For example, UBBP_UL indicates that this
UBBP works in UL mode, and there is a possibility that it supports GSM, UMTS,
and LTE.
(1)
WBBP refers to all types of WBBPs that support UMTS, including the WBBPa,
WBBPb, WBBPd, and WBBPf.
(2)In this scenario, data is converged from slot 6 to slot 2 or 3 instead of both of
them.

Constraints

SingleRAN

as follows:
● If the converging board is a UBRIb, GSM supports the non-baseband
extension mode only.
In UL or GUL CPRI MUX, if the converging board is a UBRIb, and UMTS and
LTE serve as converged parties, then the cells of the converged parties must
be served by the specified baseband equipment group. Such a baseband
equipment group can only include single-mode baseband processing units.
● In non-baseband extension mode, GSM can serve as the converged party, and
GSM RF modules are connected to the converging board. This eliminates the
need for adding a GSM BBP/BRI.
● If a BBU is configured with a multimode co-BBP board, and network modes
involved in CPRI MUX are the same as or included in the network modes that
work in co-BBP mode, connect this multimode co-BBP board to RF modules.
For example, if a BBU is configured with a UBBP_GL, the GL CPRI port
connecting to RF modules is provided by this UBBP_GL instead of a GO or LO
BBP/BRI.

Network Mode Converging Board Slot of the Converging
Served by the Board
CPRI Port
GU UBRIb Slot 0, 1, 2, 3, 4, or 5
GL UBBP_G/U/L/GU/GL/UL/GUL
UL
GUL
LN UBBP_L/UBBP_N/UBBP_LN Slot 0, 1, 2, 3, 4, or 5
ULN UBBP_U/L/N/UL/LN Slot 0, 1, 2, 3, 4, or 5

SingleRAN

Served by the Board
CPRI Port
In this table, UBBP_G/U/L/GU/GL/UL/GUL/N/LN/ULN indicates the working

mode of the UBBP instead of the mode supported by the UBBP. For example,
UBBP_UL indicates that this UBBP works in UL mode, and there is a possibility
that it supports GSM, UMTS, and LTE.
● The network modes served by a CPRI port on a co-BBP UBBP are the same as or included in
those served by this UBBP. For example, a CPRI port on a UBBP_GUL can work in UO, UL, or
GUL mode.
● If CPRI ports on a UBRIb work at a data rate higher than 4.9 Gbit/s, each port can carry
services of only one network mode in versions earlier than SRAN11.1, and can carry services
of two network modes in SRAN11.1 and later versions.

listed as follows:
converging party cannot serve as the converged party. Data of a network
mode can only be converged to one board.
● Only UMTS, LTE, and NR can serve as the converging party. If CPRI MUX
involves GSM, GSM supports the non-baseband extension mode only.
● For GU or GL CPRI MUX in separate-MPT scenarios, each BBU provides a
maximum of six ports for data convergence. These ports must be located on
the same UBBP_U or UBBP_L.
● For UL/LN CPRI MUX in separate-MPT scenarios, each BBU provides a
maximum of 24 ports for data convergence. One converged board
corresponds to one or two converging boards. A maximum of three one-to-
one convergence relationships or two one-to-two convergence relationships
are supported. The two-to-one convergence relationship is not supported.
After the converged party supports one-to-two convergence relationships,
CPRI chains/rings with Access Type set to LOCALPORT cannot be configured
on the converged party.


SingleRAN
Network Converging Slot of the Converged Slot of the

Mode Board Converging Board Board Converged
Served by Board
the CPRI
Port
UL UBBP_U Slot 0, 1, 2, 3, 4, or UBBP_L Slot 0, 1, 2,

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

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

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

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

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

GTMUc
LN UBBP_L Slot 0, 1, 2, 3, 4, or UBBP_N Slot 0, 1, 2,

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

5 3, 4, or 5
In this table, UBBP_G/U/L/N/LN/GU/GL/UL/GUL indicates the working mode of

the UBBP. For example, UBBP_UL indicates that this UBBP works in UL mode,
and there is a possibility that it supports GSM, UMTS, and LTE.
(1)Data is converged from slot 6 to one instead of two or more of slots 0 to 3
(for example, from slot 6 to slot 0 or 1).
(2)A UBBPei cannot serve as the converged board of CPRI MUX in separate-MPT
scenarios.
The UBBPg2/UBBPg2a using DSFP optical modules cannot serve as the converged board. If
they serve as the converging board, only the first LC port of each DSFP optical module
supports CPRI MUX.

Constraints
The BBU5900 supports CPRI MUX in co-MPT scenarios for data convergence
among two or more network modes (including GSM, UMTS, and LTE). In separate-

SingleRAN
MPT scenarios, data convergence between UMTS and LTE and between LTE and
NR is supported.

as follows:
GSM RF modules are connected to the converging board UBBP_U/L/UL. This
eliminates the need for adding a GSM baseband processing unit.
BBP/BRI.
NOTICE
The slot assignment in a BBU5900 is different from that in a BBU3910. For

details about the slot assignment in a BBU5900, see BBU5900 Hardware
Description. The BBU5900 does not support the UBRIb.


Served by the Board
CPRI Port
GU UBBP_G/U/L/GU/GL/UL/GUL Slot 0, 1, 2, 3, 4, or 5
GL
UL
GUL
LN UBBP_L/UBBP_N/UBBP_LN Slot 0, 1, 2, 3, 4, or 5

SingleRAN

Served by the Board
CPRI Port
ULN UBBP_U/L/N/UL/LN Slot 0, 1, 2, 3, 4, or 5
In this table, UBBP_G/U/L/N/GU/GL/UL/GUL/LN/ULN indicates the working

mode of the UBBP. For example, UBBP_UL indicates that this UBBP works in UL
mode, and there is a possibility that it supports GSM, UMTS, and LTE.
The network modes served by a CPRI port on a co-BBP UBBP are the same as or included in
GUL mode.

listed as follows:
converging party cannot serve as the converged party.
● The converging party can be UMTS/LTE/NR.
● For UL/LN CPRI MUX in separate-MPT scenarios, each BBU provides a
maximum of 24 ports for data convergence. One converged board
corresponds to one or two converging boards. A maximum of three one-to-
one convergence relationships or two one-to-two convergence relationships
are supported. The two-to-one convergence relationship is not supported.
After the converged party supports one-to-two convergence relationships,
CPRI chains/rings with Access Type set to LOCALPORT cannot be configured
on the converged party.


SingleRAN
Network Converging Slot of the Converged Slot of the

Mode Served Board Converging Board Converged
by the CPRI Board Board
Port
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 UBBPe_L 4, or 5
UBBPei_L Slot 0, 1, 2, 3, UBBPd/ Slot 0, 1, 2, 3,

4, or 5 UBBPe_U 4, or 5
LN UBBP_L Slot 0, 1, 2, 3, UBBP-W_N(1) Slot 0, 2, or 4

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

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

4, or 5 4, or 5
In this table, UBBP_G/U/L/GU/GL/UL/GUL/LN indicates the working mode of the

UBBP. For example, UBBP_UL indicates that this UBBP works in UL mode, and
there is a possibility that it supports GSM, UMTS, and LTE.
(1) UBBP-W indicates the full-width board.
The UBBPg2/UBBPg2a/UBBPg3 using DSFP optical modules cannot serve as the converged
board. If they serve as the converging board, only the first LC port of each DSFP optical
module supports CPRI MUX.
4.4 BBU3910A Boards Supporting CPRI MUX and

Constraints
The constraints on CPRI MUX used with a BBU3910A are listed as follows:
● A BBU3910A supports CPRI MUX only in co-MPT scenarios and supports only
GU, GL, UL, and GUL CPRI MUX.
● A BBU3910A provides six CPRI ports, all of which support CPRI MUX.

SingleRAN
Network Mode Constraints

The supported network mode varies with the BBU3910A model. Table 4-7 lists the
details.
Table 4-7 Network modes supported by each BBU3910A model
BBU Model Network Mode
BBU3910A1 GU, GL, UL
BBU3910A2 GU, GL, UL
BBU3910A3 GU, GL, UL, GUL
4.5 BBU3910C Boards Supporting CPRI MUX and

Constraints
The constraints on CPRI MUX used with a BBU3910C are listed as follows:

● The BBU3910C only supports GU CPRI MUX in co-MPT scenarios. A BBU3910C
provides one CPRI port.
4.6 BBU5900A Supporting CPRI MUX and Constraints

The constraints on CPRI MUX used with a BBU5900A are listed as follows:

GSM RF modules are connected to the converging board UBBP_U/L/UL. This
eliminates the need for adding a GSM baseband processing unit.
BBP/BRI.

Table 4-8 describes the BBU5900A that can serve as the converging board of CPRI
MUX and the slot assignment.

SingleRAN
Table 4-8 BBU5900A that can serve as the converging board of CPRI MUX and
Served by the Board
CPRI Port
GU UBBP_G/U/L/GU/GL/UL/GUL Slot 0, 2, or 4
GL
UL
GUL
LN UBBP_L/N/LN Slot 0, 2, or 4
ULN UBBP_U/L/N/UL/LN Slot 0, 2, or 4
In this table, UBBP_G/U/L/GU/GL/UL/GUL/LN/ULN indicates the working mode

of the UBBP. For example, UBBP_UL indicates that this UBBP works in UL mode,
and there is a possibility that it supports GSM, UMTS, and LTE.
The network modes served by a CPRI port on a co-BBP UBBP are the same as or included in
GUL mode.

SingleRAN
CPRI MUX Feature Parameter Description 5 CPRI MUX Networking Example
5 CPRI MUX Networking Example
5.1 Star Topology with CPRI MUX

This section provides examples of the star topology with CPRI MUX. For the
restrictions on BBU board slot assignment, see 4 Boards That Support CPRI MUX
and Constraints.
5.1.1 Star Topology with CPRI MUX (BBU3900)
5.1.1.1 Co-MPT Scenarios
Star Topology with UL CPRI MUX

● Scenario 1: The converging board is a single-mode board.
Figure 5-1 shows an example. In this example, UMTS is the converging party
and the converging board is a WBBPf or UBBP_U; LTE FDD is the converged
party and the converged board is an LBBPd or UBBP_L.

SingleRAN
Figure 5-1 UL CPRI MUX in co-MPT scenarios (converging party: UMTS)
● Scenario 2: The converging board is a co-BBP board.

Figure 5-2 shows an example with a UBBP_UL configured in slot 3.
Figure 5-2 UL CPRI MUX with UL co-BBP in co-MPT scenarios

SingleRAN
Star Topology with GU CPRI MUX

Figure 5-3 shows an example where GSM uses the non-baseband extension
mode. In this example, the converging party is GSM and the converging board
is a UBRIb.
Figure 5-3 GU CPRI MUX in co-MPT scenarios (converging board: UBRIb)
mode. In this example, the converging party is UMTS and the converging
board is a UBBP_U.

SingleRAN
Figure 5-4 GU CPRI MUX in co-MPT scenarios (converging board: UBBP_U)

Figure 5-5 shows an example with a UBBP_GU configured in slot 3.
Figure 5-5 GU CPRI MUX with GU co-BBP in co-MPT scenarios
Star Topology with GL CPRI MUX


SingleRAN
is a UBRIb.
Figure 5-6 GL CPRI MUX in co-MPT scenarios (converging board: UBRIb)
mode. In this example, the converging party is LTE and the converging board
is a UBBP_L.

SingleRAN
Figure 5-7 GL CPRI MUX in co-MPT scenarios (converging board: UBBP_L)

Figure 5-8 shows an example with a UBBP_GL configured in slot 3.
Figure 5-8 GL CPRI MUX with GL co-BBP in co-MPT scenarios
Star Topology with GUL CPRI MUX


SingleRAN
● (1) In this scenario, UMTS and LTE cells must be configured on the specified
baseband equipment group, and such a baseband equipment group must include
only single-mode BBPs.
● (2)
WBBP refers to all types of WBBPs that support UMTS, including the WBBPa,
WBBPb, WBBPd, and WBBPf.
is a UBRIb.
Figure 5-9 GUL CPRI MUX in co-MPT scenarios (converging board: UBRIb)
mode. In this example, the converging party is UMTS.

SingleRAN
Figure 5-10 GUL CPRI MUX in co-MPT scenarios (converging party: UMTS)

mode. In this example, the converging party is UL.
Figure 5-11 GUL CPRI MUX in co-MPT scenarios (converging party: UL)
Figure 5-12 shows an example with a UBBP_GUL configured in slot 3.

SingleRAN
Figure 5-12 GUL CPRI MUX with GUL co-BBP in co-MPT scenarios
5.1.1.2 Separate-MPT Scenarios
Star Topology with UL CPRI MUX

● Figure 5-13 shows an example. In this example, the converging party is UMTS
and the converged party is LTE.

SingleRAN
Figure 5-13 UL CPRI MUX in separate-MPT scenarios (converging party:

UMTS)
● Figure 5-14 shows an example. In this example, the converging party is LTE
and the converged party is UMTS.
Figure 5-14 UL CPRI MUX in separate-MPT scenarios (converging party: LTE)

SingleRAN

In GU CPRI MUX, the converging party must be UMTS and the converged party
must be GSM. Figure 5-15 shows an example.
NOTICE
In this scenario, data can be converged from slot 6 to either slot 2 or 3, but cannot
to both slots.
Figure 5-15 GU CPRI MUX in separate-MPT scenarios (converged party: GSM)
Star Topology with GL CPRI MUX

In GL CPRI MUX, the converging party must be LTE and the converged party must
be GSM. Figure 5-16 shows an example.

SingleRAN
Figure 5-16 GL CPRI MUX in separate-MPT scenarios (converged party: GSM)

This section describes the star topology with CPRI MUX where the converging
board is a UBRIb, a single-mode BBP, or a multimode BBP. In this section, the star
topology with GU CPRI MUX is taken as an example.
● Figure 5-17 shows an example when the converging board is a UBRIb.

SingleRAN
Figure 5-17 GU CPRI MUX in co-MPT scenarios (converging board: UBRIb)
● Figure 5-18 shows an example when the converging board is a UBBP_U.
● Figure 5-19 shows an example when the converging board is a UBBP_GU.

SingleRAN
Figure 5-19 GU CPRI MUX in co-MPT scenarios (converging board: UBBP_GU)
Star Topology with GU or GL CPRI MUX

Figure 5-20 shows an example of GU CPRI MUX. In this example, the converging
board is a UBBP_U.
Figure 5-20 GU CPRI MUX in separate-MPT scenarios

SingleRAN
Star Topology with UL or LN CPRI MUX

● One convergence relationship
Figure 5-21 shows an example. In this example, the converging board is a
UBBP_U.
Figure 5-21 UL CPRI MUX in separate-MPT scenarios (converging party:

UMTS)
● Multiple convergence relationships

In a BBU3910, one converged board corresponds to one or two converging
boards. A maximum of three one-to-one convergence relationships or two
one-to-two convergence relationships are supported.
Figure 5-22 shows an example of three one-to-one convergence relationships.
In this example, the converging party is LTE. In this 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.

SingleRAN
Figure 5-22 UL CPRI MUX in separate-MPT scenarios with three one-to-one

convergence relationships
Figure 5-23 shows an example of two one-to-two convergence relationships.

In this example, the converging party is LTE. In this figure, the board in slot 0
is a converged board, and boards in slots 4 and 5 are converging boards.
These boards form a group. Similarly, boards in slot 1, 2, and 3 form a group.
Figure 5-23 UL CPRI MUX in separate-MPT scenarios with two one-to-two


SingleRAN

● Figure 5-24 shows an example. In this example, the converging board is a
UBBP_U.
● Figure 5-25 shows an example. In this example, the converging board is a

UBBP_GU.

SingleRAN
Star Topology with UL or LN CPRI MUX

● One convergence relationship
Figure 5-26 shows an example. In this example, the converging board is
UBBP_L and the networking is LN CPRI MUX.

SingleRAN
Figure 5-26 LN CPRI MUX in separate-MPT scenarios (converging board:

UBBP_L)
● Multiple convergence relationships

In a BBU5900, one converged board can correspond to one or two converging
boards. A maximum of three one-to-one convergence relationships or two
one-to-two convergence relationships are supported.
Scenario 1: Figure 5-27 shows an example of three one-to-one convergence
relationships. In this 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.

SingleRAN
Figure 5-27 UL CPRI MUX in separate-MPT scenarios with three one-to-one

Scenario 2: Figure 5-28 shows an example of two one-to-two convergence

relationships. In this 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
Figure 5-28 UL CPRI MUX in separate-MPT scenarios with two one-to-two

5.1.4 Star Topology with CPRI MUX (BBU3910A)

Figure 5-29 shows an example of GU CPRI MUX.
Figure 5-29 GU CPRI MUX used with a BBU3910A in co-MPT scenarios
5.1.5 Star Topology with CPRI MUX (BBU3910C)

Figure 5-30 uses GU CPRI MUX as an example.

SingleRAN
Figure 5-30 GU CPRI MUX used with a BBU3910C in co-MPT scenarios
5.1.6 Star Topology with CPRI MUX (BBU5900A)

● The following figure shows an example. In this example, the converging board
is a UBBP_U.
● The following figure shows an example. In this example, the converging board
is a UBBP_GU.

SingleRAN
5.2 Chain Topology with CPRI MUX

The chain topology with CPRI MUX adopts the same BBU configurations as the
star topology. The difference is that in a chain topology, multimode RF modules
operating in the same or different network modes can be cascaded.
● This section describes RF module cascading solutions and constraints. For BBU
configurations, see 4 Boards That Support CPRI MUX and Constraints and 5.1 Star
Topology with CPRI MUX.
● If a chain contains RF modules whose working mode includes GSM, first activate cells
served by such RF modules that are configured at the upper levels, that is, closer to the
BBP.
● All RF modules on a chain must work at the same rate.
Cascading Specifications
Table 5-1 lists the maximum number of cascading levels in a chain topology with
CPRI MUX.
Table 5-1 Maximum number of cascading levels in a chain topology with CPRI
MUX
Network Mode Maximum Number of Cascading Levels
GU 6
GL 4

SingleRAN
Network Mode Maximum Number of Cascading Levels
UL 4
GUL 4
LN 4
ULN 4
● In specific scenarios, the maximum number of cascading levels also depends on factors
such as the cell specifications of each network mode and the CPRI MUX access
capabilities of the converging party. For details on the CPRI MUX access capabilities, see
6 Specifications of CPRI MUX Access Capabilities.
● If configurations of a base station exceed CPRI MUX access capabilities, the status of
certain cells served by this base station may be abnormal.
● For the maximum level of cascading and the maximum distance between an RF module
and a BBU, see the description of CPRI port specifications in RRU Technical
Specifications or AAU Technical Specifications for the RF module.
5.2.1 Intra-Mode Cascading

Definition and Constraints
On an intra-mode cascading chain, all multimode RF modules are configured with
an identical working mode. The configured working mode is the same as the
working mode of the live network.
The intra-mode cascading solution applies to both co-MPT scenarios and
separate-MPT scenarios. This recommended solution features few limitations in
terms of application and is implemented in a broad range of scenarios.
Example
Figure 5-33 shows an example of GU CPRI MUX where a BBU3900 is used and
GSM uses the non-baseband extension mode. In this example, the converging
party is UMTS and the converging board is a UBBP_U. Multimode RF modules on
the chains are all configured to work in GU mode which is the case on the live
network.

SingleRAN
Figure 5-33 Intra-mode cascading chain with GU CPRI MUX in co-MPT scenarios
where a BBU3900 is used and GSM uses the non-baseband extension mode
(converging party: UMTS; converging board: UBBP_U)
5.2.2 Inter-Mode Cascading
Introduction
On an inter-mode cascading chain, multimode RF modules are configured with
different working modes. The configured working modes are the same as or
included in the working modes of the live network. The inter-mode cascading
solution is provided for use in specific scenarios.
On an inter-mode cascading chain, if an RF module whose working mode includes GSM is

configured with GSM TRXs, it must be configured at the upper level, that is, closer to a BBP.
Constraints
1. If GSM is included in the working mode of any multimode RF module on an
inter-mode cascading chain, all multimode RF modules on this chain must
support GSM. In other words, if any multimode RF module on such a chain
works in GO, GU, GL, or GUL mode, then this chain can only contain GU, GL,
and GUL RF modules. Figure 5-34 shows an example.
2. If GSM is excluded from the working modes of all multimode RF modules on
an inter-mode cascading chain, this chain can contain any type of multimode
RF modules. In other words, if all multimode RF modules on such a chain

SingleRAN
work in UO, LO, and UL modes, then this chain can contain GU, GL, UL, and
GUL RF modules. Figure 5-35 shows an example.
Example
● The following figure takes GU CPRI MUX in co-MPT scenarios as an example
of constraint 1. In this example, a BBU3900 is used, GSM uses the non-
baseband extension mode, the converging party is UMTS, and the converging
board is a UBBP_U.
Figure 5-34 Inter-mode cascading chain with GU CPRI MUX in co-MPT

scenarios where a BBU3900 is used and GSM uses the non-baseband
extension mode (converging party: UMTS; converging board: UBBP_U)
In this figure, UO RF modules are multimode RF modules that work in UO mode and
also support GSM. In other words, they are GU or GUL RF modules.
● The following figure takes UL CPRI MUX in co-MPT scenarios as an example

of constraint 2. In this example, a BBU3900 is used and the converging party
is UMTS.

SingleRAN
Figure 5-35 Inter-mode cascading chain with UL CPRI MUX in co-MPT

scenarios where a BBU3900 is used (converging party: UMTS)
Constraints
In separate-MPT scenarios, an inter-mode cascading chain can contain multimode
RF modules that work in a single network mode or dual network modes. These RF
modules must support both converging and converged parties.
Example
Figure 5-36 takes GU CPRI MUX in separate-MPT scenarios as an example. In this
example, multimode RF modules on the inter-mode cascading chains must be GU
or GUL RF modules that work in GO, UO, or GU mode.

SingleRAN
Figure 5-36 Inter-mode cascading chain with GU CPRI MUX in separate-MPT

scenarios where a BBU3900 is used (converging party: UMTS)
5.3 Load Sharing Topology with CPRI MUX

This topology is one of multimode load sharing topologies. In the load sharing
topology with CPRI MUX, a multimode RF module has two CPRI links. These CPRI
links together carry services of two or more network modes, and one of them
carry services of multiple network modes on its own.
Currently, the CPRI MUX load sharing topology applies only to co-MPT scenarios.
Only GUL RF modules support this topology. Figure 5-37 shows two examples. In
each example, the two CPRI links carry GU+L services. Specifically, one carries GU
services and the other carries LTE services.
Figure 5-37 GU+L load sharing topology

SingleRAN
NOTICE
● In the multimode load sharing topology, the two CPRI links of an RF module
must be connected to two BBPs/BRIs that work in different network modes.
Only the BBU3900/BBU3910/BBU5900 supports the multimode load sharing
topology.
● In the multimode load sharing topology, the number of LTE cells cannot exceed
the limit supported by each CPRI link. The maximum number of LTE cells varies
depending on the CPRI port rate and the number of cells supported by the BBU.
For details about the number of LTE cells supported by CPRI ports with
different data rates, see the following:
For 3900 series BBUs, see section "UBBP" or "LBBP" in 3900 & 5900 Series Base
Station Product Documentation > BBU3900 and BBU3910 Hardware
Description > BBU3900 and BBU3910 Boards.
For the BBU5900, see section "UBBP" in 3900 & 5900 Series Base Station
Product Documentation > BBU5900 Hardware Description > BBU5900 Boards.
● If a UBBP is used in the multimode load sharing topology, the UBBP must have
been configured with baseband resources of its working mode. Otherwise,
carriers cannot be successfully allocated to the CPRI ports on this UBBP.
● In the multimode load sharing topology, if the CPRI port or the board hosting
the CPRI port is faulty, services of certain network modes may fail to be
established. After the fault is rectified, services of all network modes will
automatically recover.
5.4 Dual-Star Topology with CPRI MUX

The dual-star topology with CPRI MUX applies to triple-mode base stations and
quadruple-mode base stations. In a triple-mode dual-star topology, two network
modes use CPRI MUX and form a dual-star topology with the third one in
separate-MPT scenarios. In a quadruple-mode dual-star topology, four network
modes are divided into two groups, and two modes in each group use CPRI MUX
and form a dual-star topology between groups in separate-MPT scenarios. Only
the BBU3900, BBU3910, and BBU5900 support this topology.
The converging party and the converged party must share one BBU and cannot be deployed
in different BBUs.
GU+L Dual-Star Topology

As shown in Figure 5-38, BBU 0 uses GU CPRI MUX in separate-MPT scenarios. In
BBU 0, a WBBPf/UBBP_U is connected to a multimode RF module through a CPRI
link which carries GU data. BBU 1 is deployed only with LTE. In BBU 1, an LBBP/
UBBP_L is connected to the multimode RF module through another CPRI link. This
way, a GU+L dual-star topology is formed.

SingleRAN
Figure 5-38 GU+L triple-mode dual-star topology
GL+U Dual-Star Topology

As shown in Figure 5-39, BBU 0 uses GL CPRI MUX in separate-MPT scenarios. In
BBU 0, an LBBPd/UBBP_L is connected to a multimode RF module through a CPRI
link which carries GL data. BBU 1 is deployed only with UMTS. In BBU 1, a WBBP/
UBBP_U is connected to the multimode RF module through another CPRI link. This
way, a GL+U dual-star topology is formed.
Figure 5-39 GL+U triple-mode dual-star topology
G[U*L] Dual-Star Topology

UMTS and LTE share one main control board, and a WBBPf/UBBP_U, LBBPd/
UBBP_L, or UBBP_UL is connected to a multimode RF module through a CPRI link
which carries UL data. GSM uses another main control board GTMU, and the
GTMU is connected to the multimode RF module through another CPRI link. This
way, a G[U*L] dual-star topology is formed. Figure 5-40 shows an example of the
G[U*L] dual-star topology where a WBBPf/UBBP_U provides the UL CPRI port.

SingleRAN
Figure 5-40 G[U*L] triple-mode dual-star topology
GU+LN Dual-Star Topology

In Figure 5-41, BBU 0 uses separate-MPT GU CPRI MUX. The UBBP_U provides a
CPRI link to connect to the multimode RF module. BBU 1 adopts LN separate-MPT,
and the UBBP_N provides a CPRI link to connect to the multimode RF module. In
this way, a quadruple-mode inter-BBU dual-star topology is formed.
Figure 5-41 GU+LN dual-star topology
BBU 0 supports the BBU3900 and BBU3910, and BBU 1 supports the BBU5900.

SingleRAN
CPRI MUX Feature Parameter Description 6 Specifications of CPRI MUX Access Capabilities
6 Specifications of CPRI MUX Access

Capabilities
In a topology with CPRI MUX, the CPRI MUX access capability depends on the
CPRI line rate and board capabilities of the converging party.
6.1 CPRI MUX Access Capabilities

Table 6-1 lists the access capabilities of the converging party in multimode
scenarios where CPRI MUX is used with a BBU3900/BBU3910/BBU5900/
BBU5900A. Table 6-3 lists the access capability in multimode scenarios where
CPRI MUX is used with BBU3910A. Table 6-4 lists the access capability in
multimode scenarios where CPRI MUX is used with BBU3910C.
● The CPRI line rate, access capabilities of a CPRI link, and access capabilities of a board
all refer to those of the converging party.
● Access capabilities mentioned in the tables apply to common cells. For the impact of
this feature working in different RATs on cell capacity, see the corresponding feature
parameter description.
● If GSM uses the baseband extension mode, GSM-related data in the tables refers to
capacity specifications when the antenna TX/RX mode is 1T2R.
● UMTS-related data in the tables refers to capacity specifications when the antenna
TX/RX mode is 1T2R.
● LTE-related data in the tables refers to capacity specifications when the antenna TX/RX
mode is 2T2R.
● The capabilities of a BBU3910A or a converging board in a BBU3900/BBU3910/
BBU5900/BBU5900A cannot exceed the TRX, cell, or carrier specifications of a site. For
the TRX, cell, and carrier specifications, see BBU Technical Specifications.

SingleRAN
Access Capabilities When CPRI MUX Is Used with a BBU3900/BBU3910/

BBU5900/BBU5900A
Table 6-1 Access capabilities in multimode scenarios where CPRI MUX is used with
a BBU3900/BBU3910/BBU5900/BBU5900A
CPRI Line 2.5 Gbit/s 4.9 Gbit/s 9.8 Gbit/s
Rate
Access 16 GSM TRXs + 32 GSM TRXs(1) + 32 GSM TRXs(1) +

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

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

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

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

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

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

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

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

Capabilities LTE 1x10 MHz + LTE 1x20 MHz +
of a CPRI
Link (ULN) NR 1x20 MHz NR 2x20 MHz

SingleRAN

Rate
Access Not supported 12 UMTS cells + 12 UMTS cells +

Capabilities LTE 6x10 MHz + LTE 6x20 MHz +
of a Board
(ULN) NR 6x20 MHz NR 8x20 MHz
● (1) For GU or GL CPRI MUX used with a BBU3910 in separate-MPT scenarios, if the
number of ports converging data is less than or equal to five, a single CPRI link can
carry 32 GSM TRXs. However, if the number of ports converging data is six, a single CPRI
link can only carry 24 GSM TRXs.
● If GSM uses the non-baseband extension mode, GSM-related data in this table refers to
capacity specifications when the maximum distance between the BBU and RF modules
is 20 km in time division multiplexing (TDM) transmission mode.
In IP over E1 or IP over FE transmission mode, specifications in this table take
precedence if these specifications do not exceed the site capacity specifications.
Otherwise, site capacity specifications take precedence.
● (2) The capacity specifications refer to those when GSM uses the non-baseband
extension mode. If GSM uses the baseband extension mode, a board serves a maximum
of 72 GSM TRXs.
● (3)For GU or GL CPRI MUX used with a BBU3900 in separate-MPT scenarios, if the
converging board is a WBBPf or an LBBPd:
The converging board can provide a maximum of three ports for data convergence if the
CPRI line rate of the ports is 9.8 Gbit/s. The ports must be ports 0, 1, and 2.
The converging board can provide the following port combinations for data convergence
if the CPRI line rates of the ports include both 9.8 Gbit/s and 4.9 Gbit/s:
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 port converging data must be port 0, 1, or 2.
● For LTE access capabilities in this table:
An LTE FDD cell with a bandwidth of 10 MHz is equivalent to four LTE NB-IoT cells, each
with a bandwidth of 200 kHz.
An LTE FDD cell with a bandwidth of 20 MHz is equivalent to eight LTE NB-IoT cells,
each with a bandwidth of 200 kHz.
● (4) If LTE cells are served by a board in slot 0, 1, 4, or 5 of a BBU3900, the board serves a
maximum of four 20 MHz 2T2R cells.

● (5) Only the UBBP supports GUL CPRI MUX with a CPRI line rate of 9.8 Gbit/s.
NOTICE
The minimum CPRI line rate of the converging board is 2.5 Gbit/s.

SingleRAN
Table 6-2 Access capabilities in LTE and NR multimode scenarios where CPRI MUX
is used with a BBU3910/BBU5900/BBU5900A
CPRI Line Rate 10.1 Gbit/s 24.3 Gbit/s
Access Capabilities of a NR 100 MHz 2T2R + LTE NR 100 MHz 8T8R + LTE
CPRI Link (LN) 6x20 MHz 2T2R 20 MHz 8T8R
Access Capabilities of a NR 6x100 MHz 2T2R + NR 6x100 MHz 8T8R +

Board (LN) LTE 24x20 MHz 2T2R LTE 6x20 MHz 8T8R
Access Capabilities When CPRI MUX Is Used with a BBU3910A
a BBU3910A
Rate

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

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

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

a BBU (GL)

a CPRI Link
(UL) or 3 UMTS cells +
LTE 3x20 MHz

a BBU (UL)

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

SingleRAN

Rate

Capabilities of 6 UMTS cells + 6 UMTS cells + 6 UMTS cells +
a BBU (GUL)
LTE 3x10 MHz LTE 3x20 MHz LTE 3x20 MHz
GSM-related data in this table refers to capacity specifications when GSM uses the non-
baseband extension mode, the transmission operates in IP over E1 or IP over FE mode, and
the maximum distance between the BBU3910A and RF modules is 20 km.
Access Capabilities When CPRI MUX Is Used with a BBU3910C
a BBU3910C
CPRI Line Rate 2.5 Gbit/s 4.9 Gbit/s
Access Capabilities of a CPRI 24 GSM TRXs + 24 GSM TRXs +

Link (GU) 6 UMTS cells 6 UMTS cells
Access Capabilities of a BBU 24 GSM TRXs + 24 GSM TRXs +

(GU) 6 UMTS cells 6 UMTS cells
The BBU3910C does not support the baseband extension mode. GSM-related data in this
table refers to capacity specifications when GSM uses the non-baseband extension mode,
the transmission operates in IP over FE mode, and the maximum distance between the
BBU3910C and RF modules is reached.
6.2 Capacity Specifications

The following are methods for calculating capacity specifications for each network
mode with different configurations:
● GSM
– In GSM non-baseband extension mode, the number of GSM TRXs are
reduced by half if the following condition is met:
20 km < Distance between the BBU and RF modules ≤ 40 km.
● UMTS
– The number of cells supported when the antenna TX/RX mode is 1T2R is
the same as that supported when the antenna TX/RX mode is 2T2R.
– The antenna TX/RX mode is in inversely proportion to the supported
number of cells. For example, the number of cells supported when the

SingleRAN
antenna TX/RX mode is 1T2R is twice that supported when the antenna
TX/RX mode is 2T4R.
● LTE
– With the antenna TX/RX mode and CPRI line rate fixed, the number of
cells supported by a 3 MHz, 5 MHz, 10 MHz, or 20 MHz cell is in inverse
proportion to the bandwidth of LTE cells. For example, the supported
number of 3 MHz cells is twice that of 5 MHz cells, and the supported
number of 5 MHz cells is twice that of 10 MHz cells.
– With the antenna TX/RX mode and CPRI line rate fixed, the supported
number of 1.4 MHz cells equals that of 3 MHz, and the supported
number of 15 MHz cells equals that of 20 MHz cells.
– With the cell bandwidth fixed, the antenna TX/RX mode of 1T1R, 2T2R,
and 4T4R is in inverse proportion to the number of cells. For example, if
the cell bandwidth is 20 MHz, the number of cells supported when the
TX/RX mode is 4T4R.
– With the cell bandwidth fixed, the number of cells supported when the
antenna TX/RX mode is 1T2R equals that supported when the antenna
TX/RX mode is 2T2R, and the number of cells supported when the
antenna TX/RX mode is 2T4R equals that supported when the antenna
TX/RX mode is 4T4R.
● NR
– When antenna TX/RX capabilities and CPRI line rates are the same, the
number of supported cells is in inverse proportion to the cell bandwidth.
For example, the supported number of 10 MHz cells is twice that of 20
MHz cells, and the supported number of 20 MHz cells is twice that of 40
MHz cells.
– With the cell bandwidth fixed, the antenna TX/RX mode of 1T1R, 2T2R,
and 4T4R is in inverse proportion to the number of cells. For example, if
the cell bandwidth is 20 MHz, the number of cells supported when the
TX/RX mode is 4T4R.
6.3 Examples
Scenario 1: BBU3900, GL 1800 MHz, GSM S2/2/2, LTE 3x20 MHz 2T2R
This scenario requires that:
● Each CPRI link serves two GSM TRXs and one 20 MHz 2T2R LTE cell.
● Each board serves six GSM TRXs and three 20 MHz 2T2R LTE cells.
According to Table 6-1, each CPRI link can serve one 20 MHz 2T2R LTE cell if the
CPRI line rate is 4.9 Gbit/s. In this case, each converging board can serve a
maximum of 126 GSM TRXs and four 20 MHz 2T2R LTE cells.
The capacity requirements are met and this scenario is supported.
Scenario 2: BBU3900, GL 1800 MHz, GSM S2/2/2, LTE 3x10 MHz 4T4R

SingleRAN
● Each board serves six GSM TRXs and three 10 MHz 4T4R LTE cells.
One 10 MHz 4T4R LTE cell is equivalent to two 10 MHz 2T2R LTE cells, and then
equivalent to one 20 MHz 2T2R LTE cell.
Therefore, the capacity requirements can be met and this scenario is supported.
Scenario 3: BBU3900, GL 1800 MHz, GSM S2/2/2/2/2/2, LTE 6x20 MHz 2T2R
● Each board serves twelve GSM TRXs and six 20 MHz 2T2R LTE cells.
Therefore, the capacity requirements cannot be met and this scenario is not
supported. Contact Huawei engineers for technical support.

SingleRAN
CPRI MUX Feature Parameter Description 7 Network Analysis
7 Network Analysis
7.1 Benefits
CPRI MUX provides benefits in the following scenarios:
● New base station deployment

CPRI MUX enables multiple network modes to use one CPRI link for data
transmission, which considerably decreases the number of required optical
modules and optical fibers. This helps reduce cable purchase, installation, and
maintenance costs.
● Refarming
If only one CPRI cable is used in a base station before refarming, new network
modes can share the existing CPRI cable and RF module after refarming
without the need for adjusting or adding CPRI cables. This reduces both
engineering expenses and service interruption duration.
● Multimode coverage for highways or railways
CPRI MUX enables multimode RF modules to be cascaded and provide
multimode coverage along highways or railways.
7.2 Impacts
7.2.1 Services
CPRI MUX in Separate-MPT Scenarios

● Operations or exceptions of the converging party
Circuit switched (CS) and packet switched (PS) services of the converged
party will be interrupted if any of the following occurs on the converging
party. Most interruptions last less than 3 minutes and the longest does not
exceed 3.5 minutes.
– The software of the converging board or the main control board is reset,
the converging board or the main control board is reset through a power

SingleRAN
cycle, or the converging board or the main control board is removed and
then reinserted.
– The converging board is blocked.
– CPRI ports on the converging board are being commissioned.
– A CPRI port of the converging board becomes faulty.
● Operations or exceptions of the converged party
– If the software of the main control board of the converged party is reset,
the data rate of PS services of the converging party may be decreased for
less than 3s in most cases and the longest does not exceed 10s. However,
voice services will not be affected.
– If the main control board of the converged party is reset through a power
cycle or if it is removed and then reinserted, CS and PS services of the
converging party will be interrupted for less than 1 minute in most cases
and the longest does not exceed 3 minutes.
CPRI MUX in Co-MPT Scenarios

● CS and PS services of the converged party will be interrupted if any of the
following occurs on the converging party. Most interruptions last less than 3
minutes and the longest does not exceed 3.5 minutes.
– The software of the converging board is reset, the converging board is
reset through a power cycle, the converging board is blocked, or the
converging board is removed and then reinserted.
– CPRI ports on the converging board are being commissioned.
– A CPRI port of the converging board becomes faulty.
● If a WBBPf serves as the converging board and a UMTS application is deleted
or reset, cells of the converged party will become unavailable for less than 5
minutes.
● If an LBBPd serves as the converging board and an LTE application is deleted
or reset, cells on the converged party will become unavailable for less than 5
minutes.
● If a UBRIb serves as the converging board, deleting or resetting a GSM
application does not affect the converged party.
● If a UBBP serves as the converging board, deleting or resetting the
applications of the network modes configured on this board does not affect
the converged party.
● Adding baseband resources to one network mode configured on a UBBP
interrupts services of other network modes configured on this board.
However, this does not affect services of the converged party that
communicates with this board through the BBU backplane.
Service interruption duration does not include the duration of manual operations, such as
blocking a board or removing and then reinserting a board.
7.2.2 Features
● GBFD-510104 Multi-site Cell

SingleRAN
For hardware capability and cell capacity specifications when both CPRI MUX
and Multi-site Cell are used, see Multi-site Cell Feature Parameter Description.
7.2.3 System Capacity

None
7.2.4 Network Performance

None

SingleRAN
CPRI MUX Feature Parameter Description 8 Requirements
8 Requirements
8.1 Licenses
None
8.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
None
Mutually Exclusive Functions

Feature ID Feature Name Description
GBFD-113701 Frequency In co-MPT scenarios, GU CPRI MUX and GL

Hopping (RF CPRI MUX do not support baseband
frequency frequency hopping. Nor do they support RF
hopping and frequency hopping and antenna frequency
baseband hopping of the following types:
frequency ● Between an RF module connecting to a
hopping) GTMUb/GTMUc and an RF module
connecting to a UBRI/UBRIb/UBBP_G
● Between an RF module connecting to a
converging board and an RF module
connecting to a UBRI/UBRIb/UBBP_G
CPRI MUX used with a BBU3900 in co-MPT
scenarios does not support baseband
frequency hopping, RF frequency hopping, or
antenna frequency hopping between an RF

SingleRAN
CPRI MUX Feature Parameter Description 8 Requirements
Feature ID Feature Name Description
GBFD-113703 Antenna module connecting to a GTMUb/GTMUc that

Frequency works in evolution mode and an RF module
Hopping connecting to a UBRIb.
8.3 Hardware
3900 and 5900 series base stations
8.4 Networking
Perform network planning according to the topologies and principles described in
5.1 Star Topology with CPRI MUX, 5.2 Chain Topology with CPRI MUX, 5.3
Load Sharing Topology with CPRI MUX, and 5.4 Dual-Star Topology with CPRI
MUX.
8.5 Others
Perform hardware planning by referring to 4 Boards That Support CPRI MUX and
Constraints. The CPRI rates of BBPs/BRIs, optical modules, and RF modules must
correspond and meet the minimum requirements outlined in 6 Specifications of
CPRI MUX Access Capabilities.

SingleRAN
CPRI MUX Feature Parameter Description 9 Operation and Maintenance
9 Operation and Maintenance
For scenarios where CPRI MUX is used with the RMU solution, see the
corresponding "Operation and Maintenance" section in RMU.
9.1 When to Use

CPRI MUX for multimode base stations is recommended in the following scenarios:
● A single-mode base station is to be reconstructed into a multimode base

station with the existing CPRI topology unchanged to reduce engineering
costs.
● A co-MPT dual-mode or multimode base station is to be deployed with lower
costs of CPRI cables.
● Multimode RF modules are to be cascaded, for example, to provide coverage
for stadiums, subways, and high-speed railways.
9.2 Precautions
The following information must be collected before feature deployment:
● Names of baseband processing units

● Names of RF modules
● Information of optical modules
● Planned site capacity
RF modules have been installed. Cables between RF modules and BBUs have been
connected as required by the CPRI MUX feature. For details, see Base Station
Installation Guide in 3900 & 5900 Series Base Station Installation Guide or 3900 &
5900 Series Base Station Maintenance Guide.
If CPRI MUX is to be deployed in a site where a single-mode base station is to be

reconstructed into a multimode base station, the hardware must meet requirements for the
CPRI MUX feature. Otherwise, it is necessary to replace the hardware.

SingleRAN
9.3 Data Configuration

9.3.1 Data Preparation
CPRI MUX in Separate-MPT Scenarios
A multimode RF module that operates in multiple network modes must follow the
following configuration rules:
● The RF module is configured and monitored by all network modes.
● The RF module must have identical configurations in all network modes.
Otherwise, ALM-26274 Inter-System Board Object Configuration Conflict will
be reported.
Parameters in Table 9-1 must be configured to the same values for the RF
module in all network modes.
Table 9-1 Common parameters

Parameter Parameter ID on Parameter Name Parameter ID
Name on the GSM (GBTS) on the GSM on the GSM
the GSM Side (eGBTS)/ (eGBTS)/
(GBTS) Side UMTS/LTE Side 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 RF Unit Working RS
Standard D Mode
The RRU configurations of the converged party take effect only after RRUs of the
converging party have been configured.
There are no specific requirements for the configurations of the converging party.
For the configurations, see section "Data Preparation" in "Data Configuration" of
chapter "Topologies" > "Operation and Maintenance" for a specific base station
type (GBTS/eGBTS/NodeB/eNodeB/gNodeB/multimode base station) in RF Unit
and Topology Management.
CPRI MUX requires that Access Type be set to PEERPORT for the RRU chain or
ring of the converged party. Table 9-2 provides key parameter settings.
● If the converged party is GSM (GBTS), set parameters in a BTSRXUCHAIN
MO.
● If the converged party is GSM (eGBTS)/UMTS/LTE, set parameters in an
RRUCHAIN MO.

SingleRAN
Table 9-2 Key parameters in a BTSRXUCHAIN/RRUCHAIN MO

Parameter Parameter ID Setting Notes
Name
Access Type AT Set this parameter to PEERPORT.
Head HCN Set these parameters to the cabinet

Cabinet No. number, subrack number, slot number,
and optical port number of the CPRI
Head HSRN port on the BBP/BRI of the peer end,
Subrack No. respectively.
Head Slot HSN
No.
Head Port HPN

No.
Local Slot LSN ● BBU3900: This parameter is set to

No. 255 by default and 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.
● BBU3910:
– In GU/GL CPRI MUX (GBTS on the
GSM side) in separate-MPT
scenarios, set this parameter to
255, and do not specify the slot
number for the converged party.
– In GU/GL CPRI MUX (eGBTS on
the GSM side) or UL CPRI MUX in
separate-MPT scenarios, set the
slot number for the converged
party based on site conditions.
● BBU5900:
For a BBU5900 used in a separate-
MPT UL or LN base station using
CPRI MUX, set this parameter to the
slot number of the converged board.
User- USERDEFRATENE Turn on the user-defined rate

Defined GOSW negotiation switch.
Rate If this switch is turned on, users can
Negotiation specify a bit rate set and a rate change
Switch period for automatic rate negotiation.
Bit Rate Set BITRATESET This parameter specifies the bit rate set
for rate negotiation. This parameter
takes effect only when the user-defined
rate negotiation switch is turned on.

SingleRAN
Parameter Parameter ID Setting Notes

Name
Rate RATECHGPERIOD This parameter specifies the duration of

Change a port working in each negotiated rate.
Period This parameter takes effect only when
the user-defined rate negotiation switch
is turned on.
When configuring a BTSRXUCHAIN MO, you do not need to set the Local Slot No.,
User-Defined Rate Negotiation Switch, Bit Rate Set, Rate Change Period
parameters.
CPRI MUX in Co-MPT Scenarios

If the topology meets the requirements for co-MPT scenarios specified in 4 Boards
That Support CPRI MUX and Constraints, CPRI MUX is supported by default and
software configuration is not required.
● The data configurations for the star or chain topology with CPRI MUX are
identical to those for the star or chain topology in a single-mode base station.
For details about how to configure a star or chain topology, see section "Data
Configuration" > "Data Preparation" > "Scenario-specific Data" > "Scenario 1:
Star topology" and "Scenario 2: Chain topology" of chapter "Topologies" >
"Operation and Maintenance" for a specific base station type (GBTS/eGBTS/
NodeB/eNodeB/gNodeB/multimode base station) in RF Unit and Topology
Management.
● Data configurations for the load sharing topology with CPRI MUX are
identical to those for the load sharing topology in an LTE single-mode base
stations. For details, see section "Scenario-specific Data" > "Scenario 4: Load
sharing topology" of chapter "Topologies" > "Operation and Maintenance
(eNodeB)" > "Data Configuration" > "Data Preparation" and "Topologies" >
"Operation and Maintenance (gNodeB)" > "Data Configuration" > "Data
Preparation" in RF Unit and Topology Management.
Dual-Star Topology
● GU+L triple-mode dual-star topology
For details, see Figure 5-38.
● GL+U triple-mode dual-star topology
● G[U*L] triple-mode dual-star topology
● GU+LN dual-star topology
For these topologies, see CPRI MUX in Separate-MPT Scenarios for data
preparation of separate-MPT GU/GL/LN CPRI MUX and CPRI MUX in Co-MPT

SingleRAN
Scenarios for data preparation of co-MPT U*L CPRI MUX. For data preparation for
GSM/UMTS/LTE/NR, see section "Scenario-specific Data" > "Scenario 1: Dual-star
topology" of chapter "Topologies" > "Operation and Maintenance (Multimode
Base Station)" > "Data Configuration" > "Data Preparation" in RF Unit and
Topology Management.
9.3.2 Using MML Commands

In co-MPT scenarios, CPRI MUX is supported by default and software configuration
is not required when the requirements outlined in this document are met. For data
configurations of RRUs and corresponding chains or rings, see operation and
maintenance sections in RF Unit and Topology Management. This section
describes the procedure for activating CPRI MUX in separate-MPT scenarios.
Using MML Commands

Step 1 On the converging party, run the ADD RRUCHAIN command to add an RRU/RFU
chain or ring.
Step 2 On the converging party, run the ADD RRU command to add an RRU or RFU to
the RRU/RFU chain or ring.
Step 3 On the converged party, run the following command to add an RRU/RFU chain or
ring:
● ADD BTSRXUCHAIN if the converged party is GSM (GBTS)
● ADD RRUCHAIN if the converged party is GSM (eGBTS), UMTS, or LTE
In this step, set the key parameters by referring to Table 9-2.
Step 4 On the converged party, run the following command to add an RRU or RFU to the
RRU/RFU chain or ring:
● ADD BTSRXUBRD if the converged party is GSM (GBTS).
● ADD RRU if the converged party is GSM (eGBTS), UMTS, or LTE
----End
Data configurations must be identical for RF modules on the converging party and converged
party sides. For the parameters, see Table 9-1.
MML Command Examples

● BBU3900
Figure 9-1 shows the topology used in the following command example.

SingleRAN
Figure 9-1 UL CPRI MUX used with a BBU3900 in separate-MPT scenarios

(converging party: UMTS)
//Adding an RRU/RFU chain or ring 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 or RFU to the RRU/RFU chain or ring 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 or ring 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 or RFU to the RRU/RFU chain or ring on the converged party
● BBU3910
Figure 9-2 shows the topology used in the following command example.
Figure 9-2 UL CPRI MUX used with a BBU3910 in separate-MPT scenarios

(converging party: UMTS)
//Adding an RRU/RFU chain or ring on the converging party

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

party side
//Adding an RRU/RFU chain or ring on the converged party

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

For detailed operations, see Feature Configuration Using the MAE-Deployment.
9.4 Activation Verification

Step 1 Verify that RRUs do not report related alarms.
Step 2 Run the following command to check whether the RRUs operate properly.
● Separate-MPT scenarios
– DSP BTSBRD for GSM (GBTS)
– DSP BRD for GSM (eGBTS), UMTS, or LTE
● Co-MPT scenarios
– DSP BRD
Step 3 Run the following command to check whether the CPRI line rate of the converging
port is consistent with the plan:
● DSP CPRIPORT on the converging party side in separate-MPT scenarios
● DSP CPRIPORT in co-MPT scenarios
----End
9.5 Network Monitoring

Converging and converged parties have separate O&M platforms in separate-MPT
scenarios, and share one O&M platform in co-MPT scenarios. The following table
lists CPRI MUX-related MML commands, which can be executed on the O&M
platform.

SingleRAN
Table 9-3 MML commands for maintenance

MML Command Application Scenario Support by Support by the
the Converged Party
Converging (Only in
Party Separate-MPT
Scenarios)
DSP RRUCHAIN To query the number Fully Fully supported

of RRUs on a chain or supported
ring connecting to the
optical port of the
converging party and
the number of
cascading levels.
DSP To query the Fully Fully supported

RRUCHAINPHYTO connections and supported
PO physical information of
RRUs connecting to
the optical port of the
converging party.
DSP CPRIPORT To query the real-time Fully Partially

information including supported supported: Use
the data rate over the this command to
optical port of the query data rates
converging party. on the CPRI port
To query whether the and the port
optical port converges aggregation
data. status.
DSP CPRILBR To query the current Fully Partially

CPRI line rate of the supported supported: Use
specified chain or ring, this command to
the maximum CPRI query the CPRI
line rate of the BBP to line rate of the
which the chain or ring specified chain/
is configured, and the ring and the
maximum CPRI line maximum CPRI
rate of each RRU or line rate of each
RFU on the chain or RRU or RFU on a
ring. chain or ring.

SingleRAN
MML Command Application Scenario Support by Support by the

the Converged Party
Converging (Only in
Party Separate-MPT
Scenarios)
STR CPRILBRNEG To manually start a Fully Not supported

negotiation on the supported
CPRI line rate of the
optical port. You can
run this command if
the RRU chain or ring
cannot be set up or
cannot operate at the
maximum CPRI line
rate due to changes in
parameter settings of
the RRU chain or ring.
Executing this
command causes link
disconnection,
interrupting services.
MOD RRUCHAIN To set breakpoints on Fully Not supported

an RRU chain or ring. supported
DSP CELL for LTE To query the cell Fully Fully supported
DSP ULOCELL for status. You can run this supported
UMTS command if cell setup
fails or cell capability
DSP GTRXSTAT degrades due to
for GSM (GBTS) insufficient CPRI
DSP GTRX for bandwidth.
GSM (eGBTS)
9.6 Reconfiguration
You can add an RRU/RFU to or remove an RRU/RFU from a cascading chain in the
star or chain topology with CPRI MUX.
For guidance on how to add RF modules to or remove them from a chain or ring
on the MAE-Deployment, see section "Adding or Deleting an RF Module" of
"Device Data Reconfiguration" in eRAN Reconfiguration Guide.
Separate-MPT Scenarios
● Adding an RRU/RFU to a cascading chain
To add an RRU/RFU to a cascading chain without changing the original
topology, you need to add the information of this RRU/RFU on both the
converging and converged parties.
a. On the converging party, run the MOD RRUCHAIN command to set a
breaking point.

SingleRAN
b. On both the converging and converged parties, run the ADD RRU
command for GSM (eGBTS)/UMTS/LTE or ADD BTSRXUBRD for GSM
(GBTS) to add an RRU/RFU.
c. Adjust the cable connections and add an RRU/RFU at the specified
position.
d. On the converging party, run the MOD RRUCHAIN command to remove
the breaking point.
● Removing an RRU/RFU from a cascading chain
To remove an RRU/RFU from a cascading chain without changing the original
topology, you need to remove the information of this RRU/RFU on both the
converging and converged parties.
a. On the converging party, run the MOD RRUCHAIN command to set a
breaking point.
b. On both the converging and converged parties, run the RMV RRU
command for GSM (eGBTS)/UMTS/LTE or RMV BTSRXUBRD for GSM
(GBTS) to remove an RRU/RFU.
c. Adjust the cable connections and remove the RRU/RFU at the specified
position.
d. On the converging party, run the MOD RRUCHAIN command to remove
the breaking point.
Co-MPT Scenarios
● Adding an RRU/RFU to a cascading chain
To add an RRU/RFU to a cascading chain without changing the original
topology, perform the following steps:
a. Run the MOD RRUCHAIN command to set a breaking point.
b. Run the ADD RRU command to add an RRU/RFU.
c. Adjust the cable connections and add an RRU/RFU at the specified
position.
d. Run the MOD RRUCHAIN command to remove the breaking point.
● Removing an RRU/RFU from a cascading chain
To remove an RRU/RFU from a cascading chain without changing the original
topology, perform the following steps:
a. Run the MOD RRUCHAIN command to set a breaking point.
b. Run the RMV RRU command to remove an RRU/RFU.
c. Adjust the cable connections and remove the RRU/RFU at the specified
position.
d. Run the MOD RRUCHAIN command to remove the breaking point.

SingleRAN
CPRI MUX Feature Parameter Description 10 Parameters
10 Parameters
The following hyperlinked EXCEL files of parameter reference match the software
version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.
● gNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
You can find the EXCEL files of parameter reference for the software version used on the
live network from the product documentation delivered with that version.
FAQ: How do I find the parameters related to a certain feature from

parameter reference?
Step 1 Open the EXCEL file of parameter reference.

Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, FBFD-020100.
Step 3 Click OK. All parameters related to the feature are displayed.
----End

SingleRAN
CPRI MUX Feature Parameter Description 11 Counters
11 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● gNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from

performance counter reference?
Step 1 Open the EXCEL file of performance counter reference.

Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, FBFD-020100.
Step 3 Click OK. All counters related to the feature are displayed.
----End

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

SingleRAN
CPRI MUX Feature Parameter Description 13 Reference Documents
13 Reference Documents
1. BBU Technical Specifications

2. RRU Technical Specifications
3. AAU Technical Specifications
4. BBU5900 Hardware Description
5. BBU5900A Hardware Description
6. BBU3900 and BBU3910 Hardware Description
7. 3900 & 5900 Series Base Station Site Maintenance Guide
8. eRAN Reconfiguration Guide
9. RF Unit and Topology Management Feature Parameter Description
10. RMU Feature Parameter Description
11. CPRI MUX (LampSite) Feature Parameter Description
12. LTE FDD and NR Uplink Spectrum Sharing Feature Parameter Description
13. eCPRI Feature Parameter Description
14. Cell Management Feature Parameter Description (LTE FDD)
15. NodeB Carrier Management Feature Parameter Description
16. GSM Carrier Management Feature Parameter Description
17. Multi-site Cell Feature Parameter Description

Cpri Mux (Sran16.1 - 01)

Uploaded by

Copyright:

Available Formats

Cpri Mux (Sran16.1 - 01)

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 (Sran16.1 - 01)

Uploaded by

Copyright:

Available Formats

SingleRAN

CPRI MUX Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.............................................................................................................3

4 Boards That Support CPRI MUX and Constraints.............................................................8

5 CPRI MUX Networking Example........................................................................................ 20

Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. ii

5.1.3.1 Co-MPT Scenarios.......................................................................................................................................................... 36

6 Specifications of CPRI MUX Access Capabilities............................................................ 51

9 Operation and Maintenance.............................................................................................. 63

Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. iii

Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. iv

This chapter describes changes not included in the "Parameters", "Counters",

1.1 SRAN16.1 01 (2020-03-30)

1.2 SRAN16.1 Draft A (2020-01-20)

Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. 1

Added support for the ULN CPRI MUX None

Added support for GULN quadruple- None

Changed the name of CME to MAE- None

Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. 2

2 About This Document

2.1 General Statements

● The technical principles of features and their related parameters

Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. 3

2.2 Applicable RAT

2.3 Features in This Document

Feature ID Feature Name Chapter/Section

- CPRI MUX 9 Operation and Maintenance

Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. 4

Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. 5

3.2 Application Scenarios

Topology Application Scenario Related Section/

Multimode load sharing ● Insufficient CPRI bandwidth 5.3 Load Sharing

Dual-star topology with Separate-MPT triple-mode/ 5.4 Dual-Star

Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. 6

Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. 7

4 Boards That Support CPRI MUX and

BBUs that support CPRI MUX include BBU3900/BBU3910/BBU5900/BBU5900A/

4.1 BBU3900 Boards Supporting CPRI MUX and

4.1.1 Co-MPT Scenarios

Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. 8

● If the converged party is LTE, the converged board cannot be an LBBPc.

UBBP_Gx. In this case, a UBBP_Gx must be configured in the BBU.

Boards and Their Slot Assignment

Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. 9

Network Converging Board Slot of the

UL WBBPf, LBBPd, or Slot 2 or 3

GUL UBRIb Slot 1

In this table, UBBP_G/U/L/GU/GL/UL/GUL indicates that this UBBP works in GO,

4.1.2 Separate-MPT Scenarios

Issue 01 (2020-03-30) Copyright © Huawei Technologies Co., Ltd. 10

Boards and Their Slot Assignment

UL UMTS WBBPf Slot 2 or 3 LBBPd An LBBPd

LTE LBBPd Slot 2 or 3 WBBP(1) A WBBPf

GU UMTS WBBPf Slot 2 or 3 GTMUb Slot 6(2)

GL LTE LBBPd Slot 2 or 3 GTMUb Slot 6(2)