Cpri Mux (Sran11.1 - 03)

SingleRAN
CPRI MUX Feature Parameter

Description
Issue 03
Date 2016-08-31
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 03 (2016-08-31) Huawei Proprietary and Confidential i

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

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

3.1 BBU3900 Boards That Support CPRI MUX................................................................................................................. 7
3.2 BBU3910 Boards That Support CPRI MUX................................................................................................................. 9
3.3 BBU3910As That Support CPRI MUX....................................................................................................................... 10
4 CPRI Topology Principles for a Multimode Base Station...................................................12

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

6.1 Co-MPT Scenarios....................................................................................................................................................... 28
6.2 Separate-MPT Scenarios.............................................................................................................................................. 30
7 Star Topology with CPRI MUX (BBU3910A)......................................................................... 33

8 Chain Topology with CPRI MUX............................................................................................ 34
9 CPRI MUX with Multimode Load Sharing Topology......................................................... 37
10 Triple-Mode Dual-Star Topology.......................................................................................... 39
10.1 GU+L Dual-Star Topology......................................................................................................................................... 40
Issue 03 (2016-08-31) Huawei Proprietary and Confidential ii

SingleRAN
CPRI MUX Feature Parameter Description Contents
10.2 GL+U Dual-Star Topology......................................................................................................................................... 40

10.3 G[U*L] Dual-Star Topology.......................................................................................................................................41
11 Specifications of the CPRI MUX Feature..............................................................................42

11.1 Converging Capabilities............................................................................................................................................. 42
11.2 Cascading Level of the Chain Topology Using the CPRI MUX Feature................................................................... 46
12 Related Features.........................................................................................................................48
12.1 Prerequisite Features...................................................................................................................................................48
12.2 Mutually Exclusive Features...................................................................................................................................... 48
12.3 Impacted Features.......................................................................................................................................................48
13 Network Impact......................................................................................................................... 49
13.1 System Capacity......................................................................................................................................................... 49
13.2 Network Performance.................................................................................................................................................49
13.3 Reliability................................................................................................................................................................... 49
14 Engineering Guidelines........................................................................................................... 51
14.1 When to Use CPRI MUX........................................................................................................................................... 52
14.2 Required Information................................................................................................................................................. 52
14.3 Network Planning....................................................................................................................................................... 52
14.4 Deployment................................................................................................................................................................ 53
14.4.1 Requirements........................................................................................................................................................... 53
14.4.2 Data Preparation...................................................................................................................................................... 53
14.4.3 Activation................................................................................................................................................................ 56
14.4.4 Activation Observation............................................................................................................................................59
14.4.5 Deactivation.............................................................................................................................................................59
14.4.6 Reconfiguration....................................................................................................................................................... 59
14.5 Performance Monitoring.............................................................................................................................................61
14.6 Parameter Optimization.............................................................................................................................................. 61
14.7 Troubleshooting.......................................................................................................................................................... 61
14.7.1 Related Alarms........................................................................................................................................................ 61
14.7.2 MML Commands for Maintenance......................................................................................................................... 63
15 Parameters................................................................................................................................... 66
16 Counters...................................................................................................................................... 71
17 Glossary....................................................................................................................................... 72
18 Reference Documents............................................................................................................... 73
Issue 03 (2016-08-31) Huawei Proprietary and Confidential iii

SingleRAN
CPRI MUX Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes the working principles and engineering guidelines of the CPRI
MUX feature.
This document applies only to 3900 series base stations, excluding the DBS3900 in the
LampSite solution. For application of the CPRI MUX feature in the DBS3900, see CPRI
MUX (LampSite) Feature Parameter Description.
MOs, parameters, alarms, and performance counters in this document are consistent with
those of the latest software version at the time of document release. To obtain information
about MOs, parameters, alarms, and performance counters of the current software version, see
the product documentation of this document.
Any "LTE" in this document refers to LTE FDD, and "eNodeB" refers to LTE FDD eNodeB.
In addition, "G", "U", and "L" in RAT acronyms refer to GSM, UMTS, and LTE FDD,
respectively.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein
l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier
version
Issue 03 (2016-08-31) Huawei Proprietary and Confidential 1

SingleRAN
SRAN11.1 03 (2016-08-31)
This issue includes the following changes.
Change Change Description Parameter

Type Change
Feature Added the limitations on the implementation of CPRI MUX None

change on the UBRIb board. For details, see 3.1 BBU3900 Boards
That Support CPRI MUX and 3.2 BBU3910 Boards
That Support CPRI MUX.
Editorial Added CPRI MUX with inter-mode cascading. For details, None
change see 8 Chain Topology with CPRI MUX.
Modified the definition of CPRI MUX with intra-mode None

cascading. For details, see 8 Chain Topology with CPRI
MUX.
SRAN11.1 02 (2016-04-20)
This issue includes the following changes.

Type Change
Feature Modified the converging capability of CPRI links in None

change GL/UL/GUL CPRI MUX when the CPRI line rate is 4.9
Gbit/s or 9.8 Gbit/s. For details, see 11.1 Converging
Capabilities.
Editorial Added a mutually exclusive feature GBFD-113703 Antenna None

change Frequency Hopping. For details, see 12.2 Mutually
Exclusive Features.
SRAN11.1 01 (2016-03-07)
This is the first commercial release of SRAN11.1. This issue does not include any changes.
SRAN11.1 Draft A (2015-12-30)

Compared with Issue 03 (2015-10-30) of SRAN10.1, Draft A (2015-12-30) of SRAN11.1
includes the following changes.

Type Change
Feature The CPRI MUX feature is mutually exclusive with the None
change Multi-Site Cell feature. For details, see 12.2 Mutually
Exclusive Features.

SingleRAN

Type Change
In a CPRI MUX scenario with clock mutual lock, if the None

major standard becomes abnormal, an alarm is reported by
other standards. For details, see 14.7.1 Related Alarms.
Deleted the MML command STR RRULNKTST. For None

details, see 14.7.2 MML Commands for Maintenance.
Editorial None None

change

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

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

SingleRAN
CPRI MUX Feature Parameter Description 2 Overview
NOTE
l (1)
UBBP boards are added in SRAN9.0, which support multimode co-BBP. Therefore, a UBBP
board can serve as both the converging board and converged board.
l Only multimode RF modules support CPRI MUX. Single-mode RF modules do not support CPRI
MUX.
l The modes of RF modules in the figures at chapters 4, 5, and 6 refer to the working modes of RF
modules, not the supporting modes of RF modules.
2.2 Benefits
This feature provides the following benefits:
l Reduced cable purchase, installation, and maintenance costs for newly deployed
multimode base stations: Multiple modes can use a CPRI link to transmit data, and
therefore the number of required optical modules and fiber optic cables decreases
considerably.
l Lower engineering costs and shorter service interruption duration in refarming scenarios:
If a multimode RF module uses a single CPRI cable, newly deployed modes can share
the module and the cable after refarming.
l Guaranteed coverage for cascaded multimode RF modules: CPRI MUX allows
multimode RF modules to be cascaded to ensure coverage along highways and railways.

SingleRAN
CPRI MUX Feature Parameter Description 3 BBUs and Boards That Support CPRI MUX
3 BBUs and Boards That Support CPRI MUX
From SRAN10.0 onwards, BBUs that support CPRI MUX include the BBU3900, BBU3910,
and BBU3910A.
l Section 3.1 BBU3900 Boards That Support CPRI MUX describes the BBU3900
boards that support CPRI MUX.
l Section 3.2 BBU3910 Boards That Support CPRI MUX describes the BBU3910
boards that support CPRI MUX.
l Section 3.3 BBU3910As That Support CPRI MUX describes the BBU3910A that
supports CPRI MUX.

SingleRAN
3.1 BBU3900 Boards That Support CPRI MUX

In separate-MPT scenarios, only UMTS and LTE can serve as the converging party. Table 3-1
lists BBU3900 boards that support the CPRI MUX feature in a separate-MPT multimode base
station and constraints on the slots of the converging and converged boards.
Table 3-1 BBU3900 boards that support the CPRI MUX feature in a separate-MPT
multimode base station and constraints on the slots of the converging and converged boards
Mode on Converging Slot of the Converged Slot of the
the CPRI Board Converging Board Converged Board
Port Board
UL WBBPf/ Slot 2 or 3 LBBPd/ One LBBPd or

UBBP_U UBBP_L UBBP_L must be
installed in slot 3 or 2.
LBBPd/ Slot 2 or 3 WBBPa/ One WBBPf or

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

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

UBBP_L GTMUc
In co-MPT scenarios, any one or multiple modes of GSM, UMTS, and LTE can serve as the
converging party or converged party. Table 3-2 lists BBU3900 boards that support the CPRI
MUX feature in a co-MPT multimode base station and constraints on the slots of the
converging and converged boards.
Table 3-2 BBU3900 boards that support the CPRI MUX feature in a co-MPT multimode base
station and constraints on networking
Mode Converging Board Slot of the Constraints on Networking
on Convergin
the g Board
CPRI
Port
UL WBBPf, LBBPd, or Slot 2 or 3 l When LTE serves as the converged

UBBP_U/L/GU/GL/ party, the LBBPc cannot serve as the
UL/GUL(1)(2) converged board.
l One WBBPf or UBBP_Ux(3) needs to
be installed in slot 2 or 3.

SingleRAN

on Convergin
the g Board
CPRI
Port
GU UBRIb(4) Slot 0 or 1 l When LTE serves as the converged

party, the LBBPc cannot serve as the
UBBP_G/U/GU/GL/ Slot 2 or 3 converged board.
UL/GUL
l When the converging party or
converged party contains UMTS, one
WBBPf or UBBP_Ux needs to be
installed in slot 2 or 3.
l When a UBRIb serves as the
converging board, GSM baseband
signals are processed by RF modules.
(5)
l When a UBRIb serves as the

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

SingleRAN

on Convergin
the g Board
CPRI
Port
UBBP_GU/GL/UL/G Slot 2 or 3
UL
GUL UBRIb Slot 1 Same as those for GU
UBBP_G/U/L/GU/G Slot 2 or 3
L/UL/GUL
NOTE
l (1)If a baseband processing board is named UBBP_A/B/C, "A", "B", "C" indicates the mode whose
baseband resources are configured on this board, baseband resources of different modes are isolated by
"/". For example, UBBP_G/U/GU indicates a UBBP configured with GSM baseband resources, UMTS
baseband resources, or GSM and UMTS baseband resources (GU co-BBP).
l (2)When multiple modes are deployed on a UBBP, the mode of data transmitted through CPRI ports on
this board can be one of or all of the deployed modes. For example, the mode of data transmitted through
the CPRI ports on a UBBP_GUL can be UMTS or UL.
l (3) A
UBBP_Ux indicates that this UBBP serves UMTS and other modes; a UBBP_Gx indicates that this
UBBP serves GSM and other modes.
l (4)If the CPRI port rate of the UBRIb board is greater than 4.9 Gbit/s, the CPRI port supports only
services of a single mode in versions earlier than SRAN11.1 and supports services of two modes in
SRAN11.1 and later versions.
l (5)
If GSM baseband signals are processed by RRUs, the signals do not need to be processed on the
baseband processing board (UBBP_Gx) in the BBU.
l (6) Whena UBRIb serves as the converging board in GUL CPRI MUX, cells served by the converged UO
and LO modes must be configured on the specified baseband equipment group, and such a baseband
equipment group must be configured with single-mode baseband processing boards.
l (7)If GSM baseband signals are not processed by RF modules, the signals are processed on the UBBP_Gx
in the BBU. Therefore, a UBBP_Gx must be configured.
3.2 BBU3910 Boards That Support CPRI MUX

In separate-MPT scenarios, only UMTS and LTE can serve as the converging party. Table 3-3
lists the BBU3910 boards that support the CPRI MUX feature and the slot assignment.
Table 3-3 BBU3910 boards that support the CPRI MUX feature and the slot assignment for
separate-MPT multimode base stations

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

4, or 5

SingleRAN

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

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

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

GTMUc
In co-MPT scenarios, any one or multiple modes of GSM, UMTS, and LTE can serve as the
converging party or converged party. Table 3-4 lists the BBU3910 boards that support the
CPRI MUX feature and the slot assignment.
Table 3-4 BBU3910 boards that support the CPRI MUX feature and the slot assignment for
co-MPT multimode base stations
Mode on the Converging Board Slot of the Converging Board
CPRI Port
GU UBRIb or Slot 0, 1, 2, 3, 4, or 5
UBBP_G/U/L/GU/GL/UL/GU
GL L
U
GUL
NOTE
If the data rate of a CPRI port on a UBRIb board is greater than 4.9 Gbit/s, the port can carry services of only
one RAT in versions earlier than SRAN11.1; the port can carry services of two RATs in SRAN11.1 and later
versions.
3.3 BBU3910As That Support CPRI MUX

The BBU3910A only applies to co-MPT scenarios. A BBU3910A provides six CPRI ports,
and all BBU3910As support CPRI MUX. Table 3-5 lists the modes supported by different
models of BBU3910As.
Table 3-5 Modes supported by BBU3910As

BBU Model Mode
BBU3910A1 GU, GL, UL
BBU3910A2 GU, GL, UL

SingleRAN
BBU Model Mode
BBU3910A3 GU, GL, UL, GUL

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

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

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

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

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

SingleRAN
Figure 5-1 UL CPRI MUX in co-MPT scenarios when UMTS serves as the converging
party
l Scenario 2: A co-BBP board serves as the converging board. The following conditions
must be met:
A UBBP_GU/GL/UL/GUL serves as the converging board and is configured in slot
2 or 3.
When a UBBP_GU serves as the converging board in UL CPRI MUX, UMTS is
the converging party, and LTE is the converged party, the LBBPc cannot serve as
the converged board.
When a UBBP_GL serves as the converging board in UL CPRI MUX, LTE is the
converging party and UMTS is the converged party. A WBBPf or UBBP_Ux is
configured in slot 2 or 3.
When a UBBP_UL serves as the converging board in UL CPRI MUX, the
UBBP_UL can provide CPRI ports for transmitting UL data.
Figure 5-2 shows UL CPRI MUX where the UBBP_UL is configured in slot 3.

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

GU CPRI MUX in Star Topology
A UBRIb or UBBP_G/U serves as the converging board. The UBRIb is configured
in slot 0 or 1, and the UBBP_G/U is configured in slot 2 or 3.
When a UBRIb serves as the converging board, GSM baseband signals are
processed by RF modules.
When GSM baseband signals are processed by RF modules and GSM serves as the
converged party, GSM signals can be converged by the UBBP_U. Therefore, a
GSM baseband processing board or interface board is not required.
If GSM baseband signals are not processed by RF modules, a UBBP_Gx is
configured in slot 1, 2, or 3.
Figure 5-3 shows GU CPRI MUX where GSM serves as the converging party, a UBRIb
serves as the converging board, and GSM baseband signals are processed by RF
modules.

SingleRAN
Figure 5-3 GU CPRI MUX in co-MPT scenarios when GSM serves as the converging
party, a UBRIb serves as the converging board, and GSM baseband signals are processed
by RF modules
Figure 5-4 shows GU CPRI MUX where UMTS serves as the converging party, a
UBBP_U serves as the converging board, and GSM baseband signals are processed by
RF modules.

SingleRAN
Figure 5-4 GU CPRI MUX in co-MPT scenarios when UMTS serves as the converging
party, a UBBP_U serves as the converging board, and GSM baseband signals are
processed by RF modules
must be met:
2 or 3.
When a UBBP_GL serves as the converging board in GU CPRI MUX, GSM is the
When a UBBP_UL serves as the converging board in GU CPRI MUX, UMTS is
the converging party and GSM is the converged party. If GSM baseband signals are
processed by RF modules, the GSM signals can be converged by a UBBP_UL, so a
GSM baseband processing board or interface board is not required. If GSM
baseband signals are not processed by RF modules, a UBBP_Gx is configured in
slot 1, 2 or 3.
When a UBBP_GU/GUL serves as the converging board in GU CPRI MUX, a
single board can provide CPRI ports for transmitting GU data.
Figure 5-5 shows GU CPRI MUX where the UBBP_GU is configured in slot 3.

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

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

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

SingleRAN
Figure 5-7 GL CPRI MUX in co-MPT scenarios when LTE serves as the converging
party, a UBBP_L serves as the converging board, and GSM baseband signals are
processed by RF modules
must be met:
2 or 3.
When a UBBP_GU serves as the converging board in GL CPRI MUX, GSM is the
converging party and LTE is the converged party. In this case, the LBBPc cannot
serve as the converged board.
When a UBBP_UL serves as the converging board in GL CPRI MUX, LTE is the
converging party and GSM is the converged party. If GSM baseband signals are
slot 1, 2 or 3.
When a UBBP_GL/GUL serves as the converging board in GL CPRI MUX, a
single board can provide CPRI ports for transmitting GL data.
Figure 5-8 shows GL CPRI MUX where the UBBP_GL is configured in slot 3.

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

A UBRIb or UBBP_G/U/L serves as the converging board. The UBRIb is
configured in slot 1, and the UBBP_G/U/L is configured in slot 2 or 3.
board.
When a UBRIb serves as the converging board in GUL CPRI MUX, the converged
boards are UO and LO baseband processing boards(1), that is, WBBP(2)/UBBP_U
and LBBPd/UBBP_L.
converged party, GSM signals can be converged by the UBBP_U/L. Therefore, a
NOTE
l (1)In this scenario, cells served by the converged UO and LO modes must be configured on the
specified baseband equipment group, and such a baseband equipment group must be
configured with single-mode baseband processing boards.
l (2) WBBP refers to WBBPa, WBBPb, WBBPd, or WBBPf.
Figure 5-9 shows GUL CPRI MUX where GSM serves as the converging party, a
UBRIb serves as the converging board, and GSM baseband signals are processed by RF
modules.

SingleRAN
Figure 5-9 GUL CPRI MUX in co-MPT scenarios when GSM serves as the converging
by RF modules
Figure 5-10 shows GUL CPRI MUX where UMTS serves as the converging party and
GSM baseband signals are processed by RF modules.

SingleRAN
Figure 5-10 GUL CPRI MUX in co-MPT scenarios where UMTS serves as the
converging party and GSM baseband signals are processed by RF modules
must be met:
2 or 3.
When a UBBP_GU serves as the converging board in GUL CPRI MUX, GU is the
converging party, and LTE is the converged party. In this case, the LBBPc cannot
serve as the converged board.
When a UBBP_GL serves as the converging board in GUL CPRI MUX, GL is the
When a UBBP_UL serves as the converging board in GUL CPRI MUX, UL is the
converging party and GSM is the converged party. If GSM baseband signals are
slot 1, 2 or 3.
When a UBBP_GUL serves as the converging board in GUL CPRI MUX, a single
board can provide CPRI ports for transmitting GUL data.
Figure 5-11 shows GUL CPRI MUX where UL serves as the converging party and GSM
baseband signals are processed by RF modules.

SingleRAN
Figure 5-11 GUL CPRI MUX in co-MPT scenarios where UL serves as the converging
party and GSM baseband signals are processed by RF modules
Figure 5-12 shows GUL CPRI MUX where the UBBP_GUL is configured in slot 3.
Figure 5-12 GUL CPRI MUX in co-MPT scenarios with GUL co-BBP

SingleRAN
5.2 Separate-MPT Scenarios
5.2.1 Constraints
l The converging and converged parties in the CPRI MUX feature must share one BBU.
l One mode can only converge data or have its data converged. Data can only be
converged to one board at a time.
l A BBU can provide a maximum of six CPRI ports for data convergence, and the CPRI
ports must be provided by a WBBPf, LBBPd, or UBBP_U/L that is installed in slot 2 or
slot 3.
5.2.2 UL CPRI MUX in Star Topology

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

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

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

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

SingleRAN
6 Star Topology with CPRI MUX (BBU3910)
6.1 Co-MPT Scenarios

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

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

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

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

Constraints
l The converging and converged parties in the CPRI MUX feature must share one BBU.
l One mode can only converge data or have its data converged. Data can only be
converged to one board at a time.
l One BBU can provide a maximum of six ports for converging data. The six ports must
be provided by the same UBBP_U or UBBP_L.
GU/GL CPRI MUX

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

SingleRAN
Figure 6-4 Separate-MPT GU CPRI MUX
UL CPRI MUX
BBU3910s support separate-MPT UL CPRI MUX when the following conditions are met:
A UBBP_U or UBBP_L serves as the converging or converged board and is installed in one
of slots 0 to 5.
Figure 6-5 shows separate-MPT UL CPRI MUX where UMTS serves as the converging
party.

SingleRAN
Figure 6-5 Separate-MPT UL CPRI MUX where UMTS serves as the converging party

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

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

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

SingleRAN
CPRI MUX Feature Parameter Description 8 Chain Topology with CPRI MUX
8 Chain Topology with CPRI MUX
In a chain topology with CPRI MUX, configurations of a BBU, including the BBU3900,
BBU3910, and BBU3910A, are the same as the configurations of the BBU in a star topology.
On the RRU side, multimode RF modules working in the same or different modes can be
cascaded on one CPRI link. Intra-mode cascading is recommended and inter-mode cascading
is provided for use in specific scenarios.
NOTE
In a chain topology with CPRI MUX, preferentially activate GSM cells served by the RF modules that
can process GSM signals and are configured at the upper levels on a chain, that is close to a baseband
processing board.
l Intra-mode cascading: All cascaded multimode RF modules must be configured with the
same mode and work in the same mode. Figure 8-1 shows GU CPRI MUX where
UMTS serves as the converging party, the UBBP_U serves as the converging board,
GSM baseband signals are processed by RF modules, and a BBU3900 is used.
l Inter-mode cascading: Cascaded multimode RF modules can work in different modes.
Inter-mode cascading is implemented in the following scenarios:
Scenario 1: GSM is contained in the cascading chain in co-MPT CPRI MUX. The
working modes of a multimode RF module in an inter-mode RF module cascading
chain contain GSM. For example, the working mode may be GO, GU, GL, or GUL.
In this scenario, all RF modules in the cascading chain must be multimode RF
modules that support GSM. That is, all RF modules must support GU, GL, or GUL.
Figure 8-2 shows co-MPT GU CPRI MUX where UMTS serves as the converging
party, the UBBP_U serves as the converging board, GSM baseband signals are
processed by RF modules, and a BBU3900 is used. The "UO Radio Unit" in this
figure is working in UO, but it is a multimode RF module that supports GSM. That
is, it supports GU or GUL.
Scenario 2: GSM is not contained in the cascading chain in co-MPT CPRI MUX.
The working modes of all multimode RF modules in an inter-RAT RRU cascading
chain do not contain GSM. These multimode RF modules work in UO, LO, or UL.
In this scenario, cascaded multimode RF modules can be GU, GL, UL, or GUL RF
modules. Figure 8-3 shows co-MPT UL CPRI MUX where UMTS serves as the
converging party and a BBU3900 is used.
Scenario 3: In separate-MPT CPRI MUX, the multimode RF modules in the inter-
RAT hybrid cascading chain can work in one or two modes, but all multimode RF
modules must support both the converging and converged parties. For example, in

SingleRAN
separate-MPT GU CPRI MUX, the multimode RF modules can work in GO, UO,
or GU, but these modules must support GU or GUL, as shown in Figure 8-4.
NOTE
For inter-mode cascading, GU or GO RF modules must be configured at the upper levels on a

chain, that is close to a baseband processing board.
Figure 8-1 GU CPRI MUX using intra-mode cascading where a BBU3900 is used, UMTS
serves as the converging party, the UBBP_U serves as the converging board, and GSM
baseband signals are processed by RF modules
Figure 8-2 GU CPRI MUX using inter-mode cascading where a BBU3900 is used, UMTS
serves as the converging party, the UBBP_U serves as the converging board, and GSM
baseband signals are processed by RF modules

SingleRAN
Figure 8-3 Co-MPT UL CPRI MUX with inter-RAT cascading (the BBU3900 is used and
UMTS serves as the converging party)
Figure 8-4 Separate-MPT GU CPRI MUX with inter-mode cascading (a BBU3900 is used
and UMTS serves as the converging party)

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

Topology
In co-MPT scenarios, if two CPRI links on an RF module carry the data of two or more
modes, this network topology is called the multimode load sharing topology. If each CPRI
link in the multimode load sharing topology can transmit data of only one mode, the CPRI
MUX feature is not required.
l For details about this network topology, see RRU/RFU/AAU Topologies > Load-
Sharing Topology > Multimode Load-Sharing Topology in RF Unit and Topology
Management Feature Parameter Description.
l If a CPRI link in the multimode load sharing topology needs to transmit data of multiple
modes, the CPRI MUX feature is required. In this scenario, only GUL RF modules
support CPRI MUX with multimode load sharing at present. Two CPRI links carry GU
+L data, with one link carrying GU data and the other carrying LTE data, as shown in
Figure 9-1.
NOTICE
l In the multimode load sharing topology, two CPRI links of an RF module must be
connected to two baseband processing boards or two interface boards of different modes.
In other words, only a BBU3900 or a BBU3910 supports multimode load sharing
topology.
l In the multimode load sharing topology, the number of LTE cells cannot exceed the
maximum number of LTE cells supported by one CPRI link, which depends on the CPRI
port rate. For the number of LTE cells supported by different CPRI port rates, see "CPRI
Specifications" in Technical Specifications of the eNodeB FDD > Technical
Specifications of the BBU3900 and BBU3910 > Product Specifications in 3900 Series
Base Station Technical Description.
l If a UBBP is used in the multimode load sharing topology, the UBBP must have been
configured with baseband resources of the mode served by this board. Otherwise, carriers
cannot be successfully allocated to the CPRI ports on this UBBP.
l In multimode load sharing, if a CPRI port is faulty or the board carrying this CPRI port is
faulty, services of certain modes cannot be established. After the fault is cleared, services
of all modes will recover.

SingleRAN
CPRI MUX Feature Parameter Description 9 CPRI MUX with Multimode Load Sharing Topology
Figure 9-1 GU+L load sharing topology

SingleRAN
CPRI MUX Feature Parameter Description 10 Triple-Mode Dual-Star Topology
10 Triple-Mode Dual-Star Topology
In a triple-mode dual-star topology, two modes are deployed in a co-MPT CPRI MUX and
form a separate-MPT dual-star topology with the third mode. This topology applies only to a
BBU3900 and a BBU3910.

SingleRAN
10.1 GU+L Dual-Star Topology

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

In Figure 10-2, BBU 0 uses separate-MPT GL CPRI MUX. The LBBPd/UBBP_L provides a
CPRI link to connect to the multimode RF module. In BBU 1 (UMTS mode), the WBBP/
UBBP_U provides a CPRI link to connect to the multimode RF module. In this way, the
LBBPd/UBBP_L and WBBP/UBBP_U form a GL+U dual-star topology.
Figure 10-2 GL+U dual-star topology

SingleRAN
10.3 G[U*L] Dual-Star Topology

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

SingleRAN
CPRI MUX Feature Parameter Description 11 Specifications of the CPRI MUX Feature
11 Specifications of the CPRI MUX Feature
11.1 Converging Capabilities

In separate-MPT or co-MPT CPRI MUX, the multimode converging capability depends on
the CPRI line rate and the board capabilities of the converging party. Table 11-1 lists the
converging capability of the converging party in multimode scenarios where CPRI MUX is
used with a BBU3900 or a BBU3910. Table 11-2 lists the converging capability in multimode
scenarios where CPRI MUX is used with a BBU3910A.
NOTE
l CPRI link rate, maximum number of carriers supported by a CPRI link, and maximum number of
carriers supported by a board all refer to those of the converging party.
l Converging capabilities in Table 11-1 apply to common cells. For the impact of different features on
cell capacity, see the corresponding feature parameter description.
l When GSM baseband signals are processed by the baseband processing board, Table 11-1 lists the
numbers of GSM TRXs supported when the antenna capability is 1T2R.
l Table 11-1 lists the numbers of supported UMTS cells when the antenna capability is 1T2R.
l Table 11-1 lists the numbers of supported LTE cells when the antenna capability is 2T2R.
l The capabilities of a BBU3910A or a BBU3900/BBU3910 converging board cannot exceed the
maximum carrier/cell specifications of a site. For the maximum carrier/cell specifications of a site,
see Product Specifications > Technical Specifications of the BBU3900/BBU3910 or Technical
Specifications of the BBU3910A > Capacity Specifications in 3900 Series Base Station Technical
Description.
Table 11-1 CPRI line rates and the converging capabilities of the converging party in
multimode scenarios where CPRI MUX is used with a BBU3900 or a BBU3910
CPRI Line 2.5 Gbit/s 4.9 Gbit/s 9.8 Gbit/s
Rate
Converging 16 GSM TRXs+ 32 GSM TRXs(1)+ 32 GSM TRXs(1)+

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

SingleRAN
CPRI Line 2.5 Gbit/s 4.9 Gbit/s 9.8 Gbit/s

Rate
Converging 96 GSM TRXs(2)+ 126 GSM TRXs(2)+ 126 GSM TRXs(2)(3)+

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

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

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

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

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

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

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

SingleRAN
NOTE
l (1)
In separate-MPT GU or GL CPRI MUX where a BBU3910 is used, if the number of converging
ports is less than or equal to five, a single CPRI link can carry 32 GSM TRXs; if the number of
converging ports is six, a single CPRI link can only carry 24 GSM TRXs.
l When GSM baseband signals are processed by RF modules, the GSM capacity listed in the
preceding table is the number of GSM carriers in the time division multiplexing (TDM) transmission
mode when the maximum distance between the BBU and the RF module is 20 km.
In the IP over E1 and IP over FE transmission schemes, use capacity specifications in Table 11-1 if
these specifications do not exceed the maximum carrier specifications of a site; use the maximum
capacity specifications of a site if capacity specifications in Table 11-1 exceed the maximum
capacity specifications of a site.
l (2)
The specifications apply to scenarios where GSM baseband signals are processed by RF modules.
When GSM baseband signals are processed by baseband processing boards, a maximum of 72 GSM
TRXs can be supported by the boards.
l (3) In separate-MPT GU or GL CPRI MUX where a BBU3900 is used, when a WBBPf or an LBBPd
serves as the converging board:

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

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

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

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

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

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

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

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

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

of a BBU (GUL) 6 UMTS cells+ 6 UMTS cells+ 6 UMTS cells+
LTE 3x10 MHz LTE 3x20 MHz LTE 3x20 MHz
NOTE
Table 11-1 lists the numbers of GSM TRXs in the IP over E1 and IP over FE transmission schemes
when the maximum distance between the BBU and the RF module is 20 km and the GSM baseband
signals are processed by RF modules.
Capacity specifications for each mode with different configurations are calculated as follows:
l GSM:
When GSM baseband signals are processed by RF modules, the numbers of GSM
TRXs are reduced by half if the following condition is met: 20 km < distance
between the BBU and the RF module 40 km.
l UMTS:
The number of cells supported when the antenna capability is 1T2R is the same as
that supported when the antenna capability is 2T2R.
The antenna capability is inversely proportional to the number of cells. For
example, the number of cells supported when the antenna capability is 1T2R is
twice that supported when the antenna capability is 2T4R.
l LTE:
When LTE cells have the same antenna capability and CPRI line rate, the number of
cells supported is inversely proportional to the bandwidth of LTE cells. For
example, the number of cells supported by a 3 MHz cell is twice that supported by a
5 MHz cell, and the number of cells supported by a 5 MHz cell is twice that
supported by a 10 MHz cell.
When LTE cells have the same antenna capability and CPRI line rate, 1.4- and 3-
MHz cells support the same number of cells, and 15- and 20-MHz cells support the
same number of cells.
When LTE cells have the same bandwidth, the antenna capability is inversely
proportional to the number of cells for 1T1R, 2T2R, and 4T4R. For example, when

SingleRAN
the cell bandwidth is 20 MHz, the number of cells supported when the antenna
capability is 2T2R is twice that supported when the antenna capability is 4T4R.
When LTE cells have the same bandwidth, the number of cells supported by 1T2R
and 2T2R antennas is the same, and that supported by 2T4R and 4T4R antennas is
the same.
Examples of Application Scenarios

Scenario 1: BBU3900 GL 1800 MHz GSM configuration requirements: S2/2/2 LTE
configuration requirements: 3x20 MHz 2T2R
The capacity requirement of each CPRI link is 2 GSM TRXs + LTE 1x20 MHz 2T2R.
The capacity requirement of each board is 6 GSM TRXs + LTE 3x20 MHz 2T2R.
According to Table 11-1, the CPRI line rate for a CPRI link that supports a 20 MHz 2T2R
LTE cell is 4.9 Gbit/s. The corresponding carrier capacity of a GL converging board is 126
GSM TRXs + LTE 4x20 MHz 2T2R. Therefore, the capacity requirements can be met and
this configuration is supported.
Scenario 2: BBU3900 GL 1800 MHz GSM configuration requirements: S2/2/2 LTE

Therefore, a 10 MHz 4T4R LTE cell needs to be converted to 2T2R LTE cells based on the
preceding calculation methods. The conversion is as follows: 1x10 MHz 4T4R -> 2x10 MHz
2T2R -> 1x20 MHz 2T2R. According to Table 11-1, the CPRI line rate for a CPRI link that
supports a 20 MHz 2T2R cell is 4.9 Gbit/s. The corresponding carrier capacity of a GL
converging board is 126 GSM TRXs + LTE 4x20 MHz 2T2R. Therefore, the capacity
requirements can be met and this configuration is supported.
Scenario 3: BBU3900 GL 1800 MHz GSM configuration requirements: S2/2/2/2/2/2 LTE

According to Table 11-1, the CPRI line rate for a CPRI link that supports a 20 MHz 2T2R
LTE cell is 4.9 Gbit/s. The corresponding carrier capacity of a GL converging board is 126
GSM TRXs + LTE 4x20 MHz 2T2R. Therefore, the capacity requirements of LTE 6x20 MHz
2T2R cannot be met and this configuration is not supported. In this case, contact Huawei
engineers for technical support.
11.2 Cascading Level of the Chain Topology Using the

CPRI MUX Feature
Table 11-3 lists the maximum cascading level of the chain topology using the CPRI MUX
feature. The maximum number of cascading levels is determined by the cell capacity of each
mode and the carrier capabilities of the converging party. For details about the capabilities of
the converging party, see section 11.1 Converging Capabilities.

SingleRAN
Table 11-3 Cascading Level of the Chain Topology Using the CPRI MUX Feature
Mode Maximum Cascading Level
GU 6
GL 4
UL 4
GUL 4
For the distance between the RF modules and the BBU, see Product Specifications >
Technical Specifications of RRUs > Specifications of CPRI Ports in 3900 Series Base
Station Technical Description.

SingleRAN
CPRI MUX Feature Parameter Description 12 Related Features
12 Related Features
12.1 Prerequisite Features

None
12.2 Mutually Exclusive Features

l GBFD-113701 Frequency Hopping (RF hopping, baseband hopping)
l GBFD-113703 Antenna Frequency Hopping
In separate-MPT scenarios, GU/GL CPRI MUX does not support baseband hopping, RF
frequency hopping between two RF modules, or antenna frequency hopping between the
RF modules:
Between two RF modules connecting to a GTMUb/GTMUc and a UBRI/UBRIb/
UBBP_G, respectively
Between two RF modules connecting to a converging board and a UBRI/UBRIb/
UBBP_G, respectively
If a UBRIb is the converging board in co-MPT scenarios, CPRI MUX does not support
baseband hopping, RF frequency hopping between two RF modules, or antenna
frequency hopping between a GTMUb/GTMUc and a UBRIb.
12.3 Impacted Features

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

SingleRAN
CPRI MUX Feature Parameter Description 13 Network Impact
13 Network Impact
13.1 System Capacity

No impact.
13.2 Network Performance

No impact.
13.3 Reliability
CPRI MUX in Separate-MPT Scenarios
CPRI MUX in separate-MPT scenarios has the following impacts on system reliability:
l Operations or exceptions on the converging party
Circuit switched (CS) and packet switched (PS) services of the converged party will be
interrupted when a CPRI port of the converging party becomes faulty or when any of the
following operations is performed by the converging party:
Software reset or power-off reset on the main control board or the converging board
Removing and then inserting the main control board or the converging board
Blocking the converging board
Commissioning CPRI ports on the converging board
In general, this duration lasts less than 3 minutes and the longest duration does not
exceed 3.5 minutes.
l Operations or exceptions on the converged party
Performing software reset on the main control board
The data rate of PS services of the converging party may be reduced for less than 3s
and the longest duration of rate reduction does not exceed 10s.
Performing power-off reset, inserting and then removing the main control board
CS and PS services on the converging party will be interrupted for less than 1
minute and the longest duration of service interruption does not exceed 3 minutes.

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

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

SingleRAN
CPRI MUX Feature Parameter Description 14 Engineering Guidelines
14 Engineering Guidelines
For scenarios where CPRI MUX is used with the RMU solution, see section "Engineering
Guidelines" in RMU Feature Parameter Description.

SingleRAN
14.1 When to Use CPRI MUX

You can enable the CPRI MUX feature in the following scenarios:
l Sites in which a single-mode base station is to be evolved into a multimode base station
and the operator requires that the existing topology of fiber optic cables remain
unchanged to reduce engineering costs
l Sites in which a co-MPT dual-mode or multimode base station is to be deployed and the
operator requires that costs of fiber optic cables be reduced
l Sites whose coverage must be ensured through cascaded RF modules, such as stadiums,
subways, and high-speed railways
14.2 Required Information

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

RF Planning
N/A
Network Planning
Perform network planning by referring to instructions in 4 CPRI Topology Principles for a
Multimode Base Station, 5 Star Topology with CPRI MUX (BBU3900), 6 Star Topology
with CPRI MUX (BBU3910), 7 Star Topology with CPRI MUX (BBU3910A), 8 Chain
Topology with CPRI MUX, 9 CPRI MUX with Multimode Load Sharing Topology, and
10 Triple-Mode Dual-Star Topology.
Hardware Planning
When selecting BBU boards that are to be used in CPRI MUX, you must consider the
application scenarios and constraints provided in 3 BBUs and Boards That Support CPRI
MUX, 5 Star Topology with CPRI MUX (BBU3900), 6 Star Topology with CPRI MUX
(BBU3910), 7 Star Topology with CPRI MUX (BBU3910A), 8 Chain Topology with
CPRI MUX, 9 CPRI MUX with Multimode Load Sharing Topology, and 10 Triple-Mode
Dual-Star Topology.

SingleRAN
NOTICE
The CPRI link rates of baseband processing boards/interface boards, optical modules, and RF
modules must match each other and must meet the specifications in 11.1 Converging
Capabilities.
14.4 Deployment
14.4.1 Requirements
Hardware
RF modules have been installed. Cables between RF modules and BBUs have been connected
as required by the CPRI MUX feature. For detailed installation procedures, see the
corresponding Base station Installation Guide and Site Maintenance Guide of the base
stations.
NOTE
If CPRI MUX is to be deployed in a site where a single-mode base station is to be evolved into a
multimode base station, the hardware must meet the requirements of CPRI MUX. If it does not, replace
the hardware.
License
None
14.4.2 Data Preparation

CPRI MUX in Separate-MPT Scenarios
Multimode RF modules that work in multiple modes must follow the following configuration
rules:
l RF modules are configured and monitored by each mode.
l RF modules working in the same mode must have the same configuration. Otherwise,
the ALM-26274 Inter-System Board Object Configuration Conflict alarm will be
reported.
l Table 14-1 lists parameters that must have the same configuration when CPRI MUX is
deployed in separate-MPT scenarios.

SingleRAN
Table 14-1 Common parameters
Parameter Parameter ID on Parameter Parameter ID on

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

Mode D Standard
The RRU configuration of the converged party takes effect only after RRUs of the converging
party have been configured.
Data configurations on the converging party remain unchanged compared with those for the
chain or star topology. For detailed data configurations, see RF Unit and Topology
Management Feature Parameter Description > Engineering Guidelines > Deployment >
Data Preparation.
Enable the CPRI MUX feature only on the converged party:
l If GSM (GBTS) is the converged party, configure the BTSRXUCHAIN MO. For key
parameters, see Table 14-2.
l If GSM (eGBTS)/UMTS/LTE is the converged party, configure the RRUCHAIN MO.
For key parameters, see Table 14-2.
Table 14-2 Key parameters in the BTSRXUCHAIN/RRUCHAIN MO
Parameter Parameter ID Remarks (Configuration Data

Name Principle for Different Source
Scenarios)
Access Type AT Set this parameter to Engineering

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

No. cabinet number, subrack Design
number, slot number, and
Head Subrack HSRN optical port number of the Engineering
No. CPRI port on the baseband Design
Head Slot No. HSN board of the peer end, Engineering

respectively. Design

SingleRAN
Parameter Parameter ID Remarks (Configuration Data

Name Principle for Different Source
Scenarios)
Head Port No. HPN Engineering

Design
Local Slot No. LSN l BBU3900: Set this Equipment

parameter to 255, and do Planning
not set the slot No. for the
converged party.
l BBU3910:
In separate-MPT
GU/GL CPRI MUX
(GBTS on the GSM
side), set this
parameter to 255, and
do not set the slot No.
for the converged
party.
In separate-MPT
GU/GL CPRI MUX
(eGBTS on the GSM
side) or UL CPRI
MUX, set the slot No.
for the converged party
based on the actual slot
where the converged
board is configured.
CPRI MUX in Co-MPT Scenarios

In co-MPT scenarios, if the networking meets the requirements described in 5.1 Co-MPT
Scenarios/6.1 Co-MPT Scenarios, CPRI MUX is supported by default.
l Data configurations for the CPRI MUX-based chain or star topology in a co-MPT base
station are the same as those in a single-mode base station. For detailed data
configurations for the chain and star topologies, see RF Unit and Topology Management
Feature Parameter Description > Engineering Guidelines > Deployment > Data
Preparation.
l Data configurations for the CPRI MUX-based load-sharing topology in a co-MPT base
station are the same data as those in an eNodeB. For detailed data configurations for the
load-sharing topology, see RF Unit and Topology Management Feature Parameter
Description > Engineering Guidelines (eNodeB) > Deployment > Data Preparation.
l For how to configure UBBP baseband resources, see sections "Baseband equipment" and
"Baseband resources" in 3900 Series Base Station Initial Configuration Guide > 3900
Series Base Station Initial Configuration (CME-based) > Creating Base Stations >
Creating Co-MPT Base Station > Creating Co-MPT Base Stations in Batches >
Preparing Co-MPT Base Station Data > Radio Data for a Co-MPT Base Station.

SingleRAN
GU+L or GL+U Triple-Mode Dual-Star Topology

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

For details about this network topology, see 10.3 G[U*L] Dual-Star Topology. For details
about data preparation, see CPRI MUX in Co-MPT Scenarios and data preparation in the
dual-star networking scenario in RF Unit and Topology Management > Engineering
Guidelines (Multimode Base Station) > Deployment > Data Preparation.
14.4.3 Activation
In co-MPT scenarios, CPRI MUX is supported by default when the requirements described in
5.1 Co-MPT Scenarios/6.1 Co-MPT Scenarios/7 Star Topology with CPRI MUX
(BBU3910A) are met. Software configuration is not required for activating CPRI MUX. For
data configurations for a co-MPT base station, see 3900 Series Base Station Initial
Configuration Guide.
This section describes the procedure for activating CPRI MUX in separate-MPT scenarios.
Using MML Commands

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

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

SingleRAN
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 chain on the converged party side

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

TXNUM=2;
BBU3910:
//Adding an RRU chain on the converging party side

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

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

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

TXNUM=2;
Using the CME to Perform Single Configuration

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

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

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

RRU/RFU to
Subrack No. SRN the RRU/RFU
Slot No. SN chain on the
converging
RRU Chain No. RCN party side.

SingleRAN
RRU Type RT
RF Unit Working RS
Mode
3 RRUCHAIN Chain No. RCN Add an

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

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

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

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

SingleRAN
BTSRXUBP Working Mode WORKINGSTA

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

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

After the configured data is activated, check whether RF module-related alarms are reported
on the Alarm/Event tab page of the LMT or U2000 for GSM, UMTS, or LTE. For details
about RF module-related alarms, see section 14.7.1 Related Alarms.
1. Check whether the status of RF modules is normal.
Separate-MPT Scenarios
On the BSC LMT or the U2000, run the DSP BTSBRD command to check whether
RF modules on the GSM (GBTS) side function properly.
On the LMT or the U2000 for the 3900 series base station, run the DSP BRD
command to check whether RF modules on the GSM (eGBTS) side function
properly.
command to check whether RF modules on the UMTS side function properly.
command to check whether RF modules on the LTE side function properly.
Co-MPT Scenarios
On the LMT or U2000 of converging party of a 3900 series base station, run the
MML command DSP BRD to check whether RF modules on the LTE side function
properly.
2. Check whether the line rate of the converging port is the same as planned.
Separate-MPT scenarios: On the LMT or U2000 for the 3900 series base station,
run the MML command DSP CPRIPORT on the converging party side, and check
whether the line rate of the converging port is the same as planned.
Co-MPT scenarios: Run the MML command DSP CPRIPORT to check whether
the line rate of the converging port is the same as planned.
14.4.5 Deactivation
This feature does not need to be deactivated.
14.4.6 Reconfiguration
You can add an RRU to or remove an RRU from a cascaded RRU chain in the star or chain
CPRI MUX topology.

SingleRAN
For how to add or remove RF modules to or from a chain or ring on the CME, see eRAN
(FDD) Reconfiguration Guide > Device Data Reconfiguration > Adding or Deleting an RF
Module in a Chain.
Separate-MPT Scenarios
l Adding an RRU to a cascaded RRU chain
To add an RRU to a cascaded RRU chain without changing the original topology, you
need to add the RRU information on both the converging and converged parties.
a. Run the MOD RRUCHAIN command on the converging party to set a breaking
point.
b. Run MML commands on both the converging and converged parties to add an
RRU. Run ADD RRU for GSM (eGBTS)/UMTS/LTE, and run ADD
BTSRXUBRD for GSM (GBTS).
c. Adjust the original cable connections and add an RRU to the specified position.
d. Run the MOD RRUCHAIN command on the converged party to remove the
breaking point.
l Deleting an RRU from a cascaded RRU chain
To remove an RRU from a cascaded RRU chain without changing the original topology,
you need to remove the RRU information from both the converging and converged
parties.
a. Run the MOD RRUCHAIN command on the converging party to set a breaking
point.
b. Run MML commands on both the converging and converged parties to remove an
RRU. Run RMV RRU for GSM (eGBTS)/UMTS/LTE, and run RMV
BTSRXUBRD for GSM (GBTS).
c. Adjust the original cable connections and remove an RRU from the specified
position.
d. Run the MOD RRUCHAIN command on the converged party to remove the
breaking point.
Co-MPT Scenarios
l Adding an RRU to a cascaded RRU chain
To add an RRU to a cascaded RRU chain without changing the original topology:
a. Run the MOD RRUCHAIN command to set a breaking point.
b. Run the ADD RRU command to add an RRU.
c. Adjust the original cable connections and add an RRU to the specified position.
d. Run the MOD RRUCHAIN command to remove the breaking point.
l Deleting an RRU from a cascaded RRU chain
To remove an RRU from a cascaded RRU chain without changing the original topology:
a. Run the MOD RRUCHAIN command to set a breaking point.
b. Run the RMV RRU command to remove an RRU.
c. Adjust the original cable connections and remove an RRU from the specified
position.
d. Run the MOD RRUCHAIN command to remove the breaking point.

SingleRAN
14.5 Performance Monitoring

N/A
14.6 Parameter Optimization

N/A
14.7 Troubleshooting
14.7.1 Related Alarms

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

Failure communication fails in the BBU.
Services of the converged party are
affected.
ALM-26235 RF Unit Maintenance Link This alarm is reported if the

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

SingleRAN
ALM-26270 Inter-System In multi-mode configuration, this

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

Parameter Settings Conflict alarm is reported if the parameter
settings of an RF unit in a mode are
inconsistent with those of the same
RF unit in the other mode, such as
the working mode or other RF
parameters.
ALM-26274 Inter-System Board Object In multi-mode configuration, this

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

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

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

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

SingleRAN
ALM-28203 Local Cell Unusable When CPRI MUX is implemented,

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

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

alarms mutual lock, if the major standard
becomes abnormal, this alarm is
reported by other standards.
14.7.2 MML Commands for Maintenance

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

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

to query the number
of RRUs carried on
an RRU chain or
ring over an optical
port on the
converging party
and the number of
cascading levels.

SingleRAN

(Only in Separate-
MPT Scenarios)
DSP Use this command Fully supported Fully supported

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

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

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

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

SingleRAN

(Only in Separate-
MPT Scenarios)
MOD RRUCHAIN Use this command Supported Not supported

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

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

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

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
RRUCH TT ADD None None Meaning: Indicates the type of the topology. In a ring
AIN RRUCH topology, the service data is transmitted on the fiber
AIN optic cable that carries the HDLC link. In a load
MOD sharing topology, the service data is transmitted on
RRUCH two fiber optic cables simultaneously, which enhances
AIN the transmission capability. The physical connection
in the ring topology is similar to that in the load
DSP sharing topology.
RRUCH
AINPH GUI Value Range: CHAIN(CHAIN), RING(RING),
YTOPO LOADBALANCE(LOADBALANCE)
LST Unit: None
RRUCH Actual Value Range: CHAIN, RING,
AIN LOADBALANCE
Default Value: None
RRU CN DSP None None Meaning: Indicates the number of the cabinet where
RRUCL the RRU is located.
KSRC GUI Value Range: 0
SET Unit: None
RRUCL
KSRC Actual Value Range: 0
TST Default Value: 0

LOPRR
U

SingleRAN

nd
RRU SRN DSP None None Meaning: Indicates the number of the subrack where
RRUCL the RRU is located.
KSRC GUI Value Range: 60~254
SET Unit: None
RRUCL
KSRC Actual Value Range: 60~254
TST Default Value: None

LOPRR
U
RRU SN DSP None None Meaning: Indicates the number of the slot where the
RRUCL RRU is located.
KSRC GUI Value Range: 0~3
SET Unit: None
RRUCL
KSRC Actual Value Range: 0~3
TST Default Value: 0

LOPRR
U
RRU RT MOD None None Meaning: Indicates the type of the RRU.
RRU GUI Value Range: MRRU(MRRU), MRXU(MRXU),
LST PRRU(PRRU), MPRU(MPRU), MPMU(MPMU),
RRU MPRF(MPRF), AIRU(AIRU), GRRU(GRRU),
LRRU(LRRU), ORRU(ORRU)
Unit: None
Actual Value Range: MRRU, MRXU, PRRU, MPRU,
MPMU, MPRF, AIRU, GRRU, LRRU, ORRU
Default Value: None

SingleRAN

nd
RRU RS ADD None None Meaning: Indicates the working standard of the RRU
RRU or RFU.
MOD GUI Value Range: TDL(LTE_TDD), TL(TDS_TDL),
RRU LO(LTE_FDD), LFTD(LTE_FDD_TDD),
LST WL(WiMAX_LTE), CL(CDMA_LTE),
RRU GO(GSM_ONLY), GT(GSM_LTE_TDD),
GL(GSM_LTE), GLFTD(GSM_LTE_FDD_TDD),
UO(UMTS_ONLY), UT(UMTS_LTE_TDD),
UL(UMTS_LTE), ULFTD(UMTS_LTE_FDD_TDD),
CU(CDMA_UMTS), GU(GSM_UMTS),
GUT(GSM_UMTS_LTE_TDD),
GUL(GSM_UMTS_LTE),
GULFTD(GSM_UMTS_LTE_FDD_TDD)
Unit: None
Actual Value Range: TDL, TL, LO, LFTD, WL, CL,
GO, GT, GL, GLFTD, UO, UT, UL, ULFTD, CU,
GU, GUT, GUL, GULFTD
Default Value: None
RRUCH AT ADD None None Meaning: Indicates the access type of the board on an
AIN RRUCH RRU chain/ring. When Access Type is set to
AIN LOCALPORT(local port), the BBP connects to the
MOD board on an RRU chain/ring through the CPRI port.
RRUCH When Access Type is set to PEERPORT(peer port),
AIN the local BBP connects to the peer BBP through the
IDX2 port on the backplane and the peer BBP
LST connects to a board on an RRU chain/ring.
RRUCH
AIN GUI Value Range: LOCALPORT(local port),
PEERPORT(peer port)
Unit: None
Actual Value Range: LOCALPORT, PEERPORT
Default Value: LOCALPORT(local port)
RRUCH HCN ADD None None Meaning: Indicates the cabinet number of the board
AIN RRUCH where the head CPRI port is located.
AIN GUI Value Range: 0~7
MOD Unit: None
RRUCH
AIN Actual Value Range: 0~7
DSP Default Value: 0

RRUCH
AINPH
YTOPO
LST
RRUCH
AIN

SingleRAN

nd
RRUCH HSRN ADD None None Meaning: Indicates the subrack number of the board
AIN GUI Value Range: 0~1,60~254
MOD Unit: None
RRUCH
AIN Actual Value Range: 0~1,60~254
DSP Default Value: 0

RRUCH
AINPH
YTOPO
LST
RRUCH
AIN
RRUCH HSN ADD None None Meaning: Indicates the slot number of the board
MOD Unit: None
RRUCH
AIN Actual Value Range: 0~6
DSP Default Value: None

RRUCH
AINPH
YTOPO
LST
RRUCH
AIN
RRUCH HPN ADD None None Meaning: Indicates the number of the head CPRI port.
AIN RRUCH GUI Value Range: 0~7
AIN
Unit: None
MOD
RRUCH Actual Value Range: 0~7
AIN Default Value: None
DSP
RRUCH
AINPH
YTOPO
LST
RRUCH
AIN

SingleRAN

nd
RRUCH LSN ADD None None Meaning: Indicates the slot number of the converged
AIN RRUCH party in CPRI MUX. If this parameter is set to 255,
AIN the slot number of the converged party is not
MOD specified. When the converging party is in a
RRUCH BBU3900, this parameter can be left unspecified.
AIN When the converging party is in a BBU3910, this
parameter must be specified.
LST
RRUCH GUI Value Range: 0~6,255
AIN Unit: None
Actual Value Range: 0~6,255
Default Value: 255
RRUCH RCN ADD None None Meaning: Indicates the ID of the RRU chain. It
AIN RRUCH uniquely identifies a chain within a base station.
DSP Unit: None
CPRILB
R Actual Value Range: 0~249
DSP Default Value: None

RRUCH
AIN
LST
RRUCH
AIN
MOD
RRUCH
AIN
RMV
RRUCH
AIN
STR
CPRILB
RNEG
RRU RCN ADD None None Meaning: Indicates the ID of the RRU or RFU chain/
RRU ring.
LST GUI Value Range: 0~249
RRU Unit: None
Actual Value Range: 0~249
Default Value: None

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

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

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

2. Installation Guide of relevant base stations
3. Site Maintenance Guide of relevant base stations
4. RF Unit and Topology Management Feature Parameter Description
5. BSC6900 GSM MML Command Reference
6. 3900 Series Base Station MML Command Reference
7. 3900 Series Base Station Alarm Reference


Cpri Mux (Sran11.1 - 03)

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 (Sran11.1 - 03)

Uploaded by

Copyright:

Available Formats

SingleRAN

CPRI MUX Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2016-08-31) Huawei Proprietary and Confidential i

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

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

4 CPRI Topology Principles for a Multimode Base Station...................................................12

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

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

Issue 03 (2016-08-31) Huawei Proprietary and Confidential ii

10.2 GL+U Dual-Star Topology......................................................................................................................................... 40

11 Specifications of the CPRI MUX Feature..............................................................................42

Issue 03 (2016-08-31) Huawei Proprietary and Confidential iii

1 About This Document

1.2 Intended Audience

1.3 Change History

Issue 03 (2016-08-31) Huawei Proprietary and Confidential 1

Change Change Description Parameter

Feature Added the limitations on the implementation of CPRI MUX None

Modified the definition of CPRI MUX with intra-mode None

Change Change Description Parameter

Feature Modified the converging capability of CPRI links in None

Editorial Added a mutually exclusive feature GBFD-113703 Antenna None

SRAN11.1 Draft A (2015-12-30)

Change Change Description Parameter

Issue 03 (2016-08-31) Huawei Proprietary and Confidential 2

Change Change Description Parameter

In a CPRI MUX scenario with clock mutual lock, if the None

Deleted the MML command STR RRULNKTST. For None

Editorial None None

Issue 03 (2016-08-31) Huawei Proprietary and Confidential 3

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

Figure 2-1 Working principle of CPRI MUX

Issue 03 (2016-08-31) Huawei Proprietary and Confidential 4

Issue 03 (2016-08-31) Huawei Proprietary and Confidential 5

3 BBUs and Boards That Support CPRI MUX

Issue 03 (2016-08-31) Huawei Proprietary and Confidential 6

3.1 BBU3900 Boards That Support CPRI MUX

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

LBBPd/ Slot 2 or 3 WBBPa/ One WBBPf or

GU WBBPf/ Slot 2 or 3 GTMUb/ Slot 6

GL LBBPd/ Slot 2 or 3 GTMUb/ Slot 6

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

Issue 03 (2016-08-31) Huawei Proprietary and Confidential 7

Mode Converging Board Slot of the Constraints on Networking

GU UBRIb(4) Slot 0 or 1 l When LTE serves as the converged

l When a UBRIb serves as the

GL UBRIb Slot 1 Same as those for GU

Issue 03 (2016-08-31) Huawei Proprietary and Confidential 8

Mode Converging Board Slot of the Constraints on Networking

GUL UBRIb Slot 1 Same as those for GU

3.2 BBU3910 Boards That Support CPRI MUX

Mode on Converging Slot of the Converged Slot of the

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

Issue 03 (2016-08-31) Huawei Proprietary and Confidential 9

Mode on Converging Slot of the Converged Slot of the

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

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

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

3.3 BBU3910As That Support CPRI MUX

Table 3-5 Modes supported by BBU3910As