USU3900-based Multi-BBU Interconnection (SRAN10.1 - 03)

SingleRAN
USU3900-based Multi-BBU
Interconnection Feature Parameter
Description
Issue 03
Date 2017-05-29
HUAWEI TECHNOLOGIES CO., LTD.

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

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

Copyright © Huawei Technologies Co., Ltd.
SingleRAN
USU3900-based Multi-BBU Interconnection Feature
Parameter Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 2
1.4 Differences Between eNodeB Types.............................................................................................................................. 3
2 Overview......................................................................................................................................... 4
2.1 Introduction.................................................................................................................................................................... 4
2.2 Benefits........................................................................................................................................................................... 4
3 Multi-BBU Interconnection Modes............................................................................................5

3.1 Introduction.................................................................................................................................................................... 5
3.2 Interconnection Between BBUs and a USU...................................................................................................................7
3.3 Interconnection Between BBUs and Two Levels of USUs.......................................................................................... 12
4 Clock Synchronization Solutions.............................................................................................16

4.1 Solution 1......................................................................................................................................................................17
4.2 Solution 2......................................................................................................................................................................17
5 Related Features...........................................................................................................................19
6 Network Impact........................................................................................................................... 20
6.1 System Capacity........................................................................................................................................................... 20
6.2 Network Performance...................................................................................................................................................20
7 Engineering Guidelines............................................................................................................. 21
7.1 When to Use Multi-BBU Interconnection....................................................................................................................21
7.2 Required Information................................................................................................................................................... 21
7.3 Planning........................................................................................................................................................................ 21
7.3.1 BBU and USU Installation Position and USU Hardware Planning.......................................................................... 21
7.3.2 Transmission Mode Planning.................................................................................................................................... 21
7.4 Deployment.................................................................................................................................................................. 22
7.4.1 Process....................................................................................................................................................................... 22
7.4.2 Requirements............................................................................................................................................................. 22
7.4.3 Data Preparation........................................................................................................................................................ 24
7.4.4 Initial Configuration.................................................................................................................................................. 26
7.4.5 Activation Observation..............................................................................................................................................29
Issue 03 (2017-05-29) Huawei Proprietary and Confidential ii

SingleRAN
Parameter Description Contents
7.4.6 Reconfiguration......................................................................................................................................................... 30
7.4.7 MML Command Examples....................................................................................................................................... 35
7.5 Parameter Optimization................................................................................................................................................ 36
7.6 Troubleshooting............................................................................................................................................................ 36
8 Parameters..................................................................................................................................... 38
9 Counters........................................................................................................................................ 46
10 Glossary....................................................................................................................................... 47
11 Reference Documents............................................................................................................... 48
Issue 03 (2017-05-29) Huawei Proprietary and Confidential iii

SingleRAN
Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes the USU3900-based multi-BBU interconnection feature, including
its technical principles, related features, network impact, and engineering guidelines.
In addition to the USU3900-based multi-BBU interconnection feature, this document covers
the following features:
l TDLOFD-081213 Inter-BBU Clock Sharing
l LOFD-081220 Inter-BBU Clock Sharing
This document applies to the following types of eNodeBs.
eNodeB Type Model
Macro 3900 series eNodeB
LampSite l LTE FDD: DBS3900

l LTE TDD: DBS3900 LampSite TDD
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein
l Work with Huawei products
Issue 03 (2017-05-29) Huawei Proprietary and Confidential 1

SingleRAN
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
SRAN10.1 03 (2017-05-29)
This issue includes the following changes.
Change Change Description Paramete Affected

Type r Change Entity
Feature None None Macro and

change LampSite
eNodeBs
Editorial Added feature name abbreviations. For details, None N/A

change see 3.1 Introduction.
SRAN10.1 02 (2015-08-31)
Chang Change Description Paramete Affected

e Type r Change Entity
Feature Added configurations of two eNodeBs that function None Macro and
change as source clock providers. For details, see 7.4.4 LampSite
Initial Configuration and 7.4.7 MML Command eNodeBs
Examples.
Editoria None None N/A

l
change
SRAN10.1 01 (2015-03-20)

SingleRAN
Chang Change Description Paramete Affected

e Type r Change Entity
Feature Added hardware licenses required for multi-BBU None Macro and
change interconnection. For details, see To use the multi- LampSite
BBU inter.... eNodeBs
Editoria None None N/A

l
change
SRAN10.1 Draft A (2015-01-15)

Compared with Issue 05 (2014-09-05) of SRAN9.0, Draft A (2015-01-15) of SRAN10.1
includes the following changes.
Change Change Description Para Affected

Type mete Entity
r
Cha
nge
Feature Added the requirement that the licenses for clock None Macro and
change source sharing between eNodeBs be purchased and LampSite
activated on these eNodeBs. For details, see 7.4.2 eNodeBs
Requirements.
Added service features supported by multi-BBU None Macro and

interconnection. For details, see 3.1 Introduction. LampSite
eNodeBs
Modified the specifications for interconnection between None Macro and

BBUs and two levels of USUs in the LTE TDD system. LampSite
For details, see 3.1 Introduction. eNodeBs
Editorial Revised descriptions in this document. None Macro and

change LampSite
eNodeBs
1.4 Differences Between eNodeB Types

The features described in this document apply only to macro and LampSite eNodeBs and are
implemented in the same way on these eNodeBs.

SingleRAN
Parameter Description 2 Overview
2 Overview
2.1 Introduction
USU3900-based multi-BBU interconnection (multi-BBU interconnection for short) allows
two or more baseband units (BBUs) to communicate with each other and process services by
connecting the BBUs and universal switching units (USUs).
BBUs and USUs are connected using the following types of cables:
l Infrastructure interconnection cable
This type of cable connects the cascading interface (CI) port on the main control board in
a BBU and an M port (M0 to M4) on the universal inter-connection infrastructure unit
(UCIU) in a USU or connects the CI port on the switch main processing & transmission
unit (SMPT) in a first-level USU and an M port (M0 to M4) on the UCIU in the second-
level USU. The cable transmits control information about the topology, clock, heartbeat,
and inter-cell link setup and release.
l Baseband interconnection cable
This type of cable connects the high speed extension interface (HEI) port on a baseband
processing unit (BBP) in a BBU and an M port (M0 to M4/S1) on a universal inter-
connection extension unit (UCXU) in a USU or connects the M5/S0 port on a UCXU in
a first-level USU and an M port (M0 to M4/S1) on a UCXU in the second-level USU.
The cable transmits cell coordination information.
2.2 Benefits
Multi-BBU interconnection provides the following benefits:
l Helps achieve service coordination between inter-BBU cells.
l Reduces the number of required Global Positioning System (GPS) antennas because
interconnected BBUs can share GPS clock sources.
NOTE
The GPS clock source includes the Remote Global Positioning System (RGPS) clock source.

SingleRAN
Parameter Description 3 Multi-BBU Interconnection Modes
3 Multi-BBU Interconnection Modes
3.1 Introduction
Multi-BBU Interconnection Modes
Table 3-1 describes multi-BBU interconnection modes.
NOTE
l In this document, USU refers to USU3900.

l In the current version, the BBU3900 and BBU3910 are supported.
l BBU3900s and BBU3910s can be connected to the same USU.
l The longest distance between a BBU and an RRU is 20 km.
Table 3-1 Multi-BBU interconnection modes

Mode Purpose Number Number
of USUs of BBUs
Intercon l To support cell coordination for the following 1 A

nection features: maximu
between – UL CoMP based on coordinated BBU, inter- m of 5
BBUs eNodeB CA based on coordinated BBU, and
and a coordinated scheduling based power control
USU (Cloud BB) in the LTE FDD system
– Inter-BBU SFN and inter-BBU adaptive SFN/
SDMA in the LTE TDD system
l To share the GPS clock source between BBUs in the
LTE FDD or TDD system
l To share the RGPS clock source between BBUs in
the LTE TDD system
NOTE
RGPS clock source sharing requires that RRUs have
RGPS antenna ports. Currently, only certain RRU models
in the LTE TDD system, such as RRU3252 DC and
RRU3256 DC, have RGPS antenna ports.

SingleRAN
Mode Purpose Number Number

of USUs of BBUs
Intercon To support cell coordination for inter-BBU SFN, inter- 3 to 6 A

nection BBU adaptive SFN/SDMA, coordinated scheduling maximu
between based power control (Cloud BB), and UL CoMP based m of 25
BBUs on coordinated BBU in the LTE TDD system
and two
levels of To support cell coordination for inter-eNodeB CA 3 or 4 A
USUs based on coordinated BBU and coordinated scheduling maximu
based power control (Cloud BB) in the LTE FDD m of 15
system
To share the GPS clock source between BBUs in the 3 to 6 A

LTE FDD or TDD system maximu
m of 25
To share the RGPS clock source between BBUs in the 3 to 6 A

LTE TDD system maximu
NOTE m of 25
RGPS clock source sharing requires that RRUs have RGPS
antenna ports. Currently, only certain RRU models in the LTE
TDD system, such as RRU3252 DC and RRU3256 DC, have
RGPS antenna ports.
After BBUs are interconnected, each eNodeB and USU functions as an independent network
element (NE) in the element management system.
In multi-BBU interconnection scenarios, each eNodeB must meet both of the following
requirements:
l The eNodeB works in LTE-only mode. Multimode base stations cannot be connected to
a USU3900.
l The eNodeB is equipped with only one BBU. An eNodeB equipped with two or more
BBUs cannot be connected to a USU3900.
Service Features Supported

Multi-BBU interconnection applies to the following service features:
l LTE TDD
– TDLOFD-001080 Inter-BBU SFN
– TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA
– TDLOFD-080203 Coordinated Scheduling based Power Control (Cloud BB)
(referred to as CSPC)
– TDLOFD-081207 UL CoMP based on Coordinated BBU (UL CoMP is short for
uplink coordinated multipoint reception.)
l LTE FDD
– LOFD-070208 Coordinated Scheduling based Power Control (Cloud BB) (referred
to as CSPC)

SingleRAN
– LOFD-070223 UL CoMP based on Coordinated BBU (UL CoMP is short for

uplink coordinated multipoint reception.)
– LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU
3.2 Interconnection Between BBUs and a USU

Cable Connections
NOTE
The number of BBPs to be installed depends on service requirements. BBPs refer to LBBPd or UBBPd
boards. LBBP is short for LTE baseband process unit, and UBBP is short for universal baseband process
unit. The number of BBPs shown in the following figures is used as an example.
Figure 3-1 shows the interconnection between BBUs and a USU for cell coordination.
Figure 3-1 Method 1

SingleRAN
NOTE
SMPT: switch main processing & transmission unit

UCIU: universal inter-connection infrastructure unit
UCXU: universal inter-connection extension unit
UMPT: universal main processing and transmission unit
UPEU: universal power and environment interface unit
The following clock sources are supported in multi-BBU interconnection: GPS clock source
connected to the main control board in a BBU, and RGPS clock source connected to an RRU.
Figure 3-2 and Figure 3-3 show multi-BBU interconnection for GPS and RGPS clock source
sharing, respectively. Clock source sharing requires only infrastructure interconnection cables
between the BBUs and USU and does not require baseband interconnection cables.
Figure 3-2 Method 2

SingleRAN
Figure 3-3 Method 3
BBUs can share a maximum of two clock sources, which can be any of the following
combinations: GPS+GPS, RGPS+RGPS, and GPS+RGPS. When the BBUs share one GPS
clock source and one RGPS clock source, the BBUs and USU are interconnected in the way
shown in Figure 3-4.

SingleRAN
Figure 3-4 Method 4
When one of the interconnected BBUs is configured with a clock source (such as BBU4 in
Figure 3-2 or Figure 3-3), these BBUs can share the clock source as follows:
1. BBU4 transmits clock signals to the USU.
2. The USU transmits the signals to other connected BBUs.
Cable Connection Principles

The cable connections are as follows:
l An infrastructure interconnection cable connects the CI port on the UMPT in a BBU to
one of ports M0 to M4 on the UCIU in the USU. The M0, M1, M2, M3, and M4 ports
are prioritized in ascending order.
l A baseband interconnection cable connects the HEI port on the BBP in a BBU to one of
ports M0 to M4/S1 on a UCXU in the USU. The M0, M1, M2, M3, and M4/S1 ports are
prioritized in ascending order.
l The infrastructure interconnection cable is configured in the CTRLLNK MO. On the
control link between a BBU and the USU, the connected USU is at the upper level of the
BBU by default.
Application Scenarios
Table 3-2 shows the application scenarios for the interconnection between BBUs and a USU.

SingleRAN
Table 3-2 Application scenarios for the interconnection between BBUs and a USU
Number of BBPs in a Position of a BBP in a Position of a UCXU in

BBU Connected to the BBU the USU
USU
1 Slot 3 Slot 3
2 Slots 2 and 3 Slots 2 and 3
3 Slots 1 to 3 Slots 1 to 3
In the LTE system, slots 4, 0, 1, 2, and 3 for BBPs are prioritized in ascending order. A BBP
can be installed in slot 5 but this BBP cannot be connected to the USU.
Through the backplane, BBPs that are not connected to the USU transfer cell coordination
information to the BBPs that are connected to the USU by using baseband interconnection
cables. Then, BBUs exchange the cell coordination information through the USU to
implement inter-BBU cell coordination.
Restrictions
Restrictions on the interconnection between BBUs and a USU are as follows:
l Two to five BBUs can be connected to the USU.

l The USU can house a maximum of five UCXUs and one UCIU. The UCIU is always
installed in slot 5.
l The number of UCXUs to be configured depends on the number of BBPs in a BBU to be
connected to the UCXUs. A maximum of five UCXUs can be configured in a USU in
the LTE system.
For example, when three LBBPd boards in a BBU need to be connected to UCXUs,
three UCXUs are required.
l The slot numbers of the two boards connected by an infrastructure interconnection cable
must be the same.
For example, if a BBP is installed in slot 3 of a BBU, the UCXU connected to the BBP
must also be installed in slot 3 of the USU.
l A BBU must be connected to the UCIU and UCXU ports with the same number in a
USU.
For example, if a BBU is connected to the M0 port on the UCIU in a USU using an
infrastructure interconnection cable, the BBU must be connected to the M0 ports on the
UCXUs in the USU using a baseband interconnection cable.
l In a BBU that is connected to a USU, the main control board must be a UMPT (UMPTa
or UMPTb), and the BBPs must be UBBPd or LBBPd boards.
l UBBPd and LBBPd boards apply to the LTE FDD and LTE TDD systems.

SingleRAN
3.3 Interconnection Between BBUs and Two Levels of

USUs
Cable Connections
NOTE
The number of BBPs to be installed depends on service requirements. The number of BBPs shown in the
following figures is used as an example.
Figure 3-5 shows the interconnection between BBUs and two levels of USUs for cell
coordination.
Figure 3-5 Method 1
The following clock sources are supported in multi-BBU interconnection: GPS clock source
connected to the main control board in a BBU, and RGPS clock source connected to an RRU.
Figure 3-6 and Figure 3-7 show multi-BBU interconnection for GPS and RGPS clock source
sharing, respectively. Clock source sharing requires only infrastructure interconnection cables
between the BBUs and USUs and does not require baseband interconnection cables.

SingleRAN
Figure 3-6 Method 2
Figure 3-7 Method 3
BBUs can share a maximum of two clock sources, which can be any of the following
combinations: GPS+GPS, RGPS+RGPS, and GPS+RGPS. Figure 3-8 shows the
interconnection method between BBUs and two levels of USUs.

SingleRAN
Figure 3-8 Method 4
When one of the interconnected BBUs is configured with a clock source (such as BBU0 in
Figure 3-6 or Figure 3-7), these BBUs can share the clock source as follows:
1. BBU0 transmits clock signals to the first-level USU (USU0) connected to BBU0.
2. USU0 transmits the signals to the second-level USU (USU5) and the other connected
BBUs.
3. USU5 transmits the signals to the other first-level USUs.
4. The other first-level USUs transmit the signals to their connected BBUs.
Cable Connection Principles

The cable connections between two levels of USUs are as follows:
l An infrastructure interconnection cable connects the CI port on the SMPT in a first-level
USU to one of ports M0 to M4 on the UCIU in the second-level USU. The M0, M1, M2,
M3, and M4 ports are prioritized in ascending order.
l A baseband interconnection cable connects the M5/S0 port on a UCXU in a first-level
USU to one of ports M0 to M4/S1 on the UCXU of the second-level USU. The M0, M1,
M2, M3, and M4/S1 ports are prioritized in ascending order.
For details about cable connections between BBUs and a USU, see 3.2 Interconnection
Between BBUs and a USU.
Application Scenarios
Table 3-3 lists the application scenarios for the interconnection between BBUs and two levels
of USUs.

SingleRAN
Table 3-3 Application scenarios for the interconnection between BBUs and two levels of
USUs
Number of BBPs in Position of an Position of a Position of a
a BBU Connected LBBPd/UBBPd in UCXU in a First- UCXU in the
to a First-Level a BBU Level USU Second-Level
USU USU
1 Slot 3 Slot 3 Slot 3
2 Slots 2 and 3 Slots 2 and 3 Slots 2 and 3
3 Slots 1 to 3 Slots 1 to 3 Slots 1 to 3
Restrictions
Restrictions on the interconnection between BBUs and two levels of USUs are as follows:
l When BBUs share GPS or RGPS clock sources, a maximum of five first-level USUs can
be connected to the second-level USU. When inter-eNodeB CA based on coordinatied
BBU is enabled in the LTE FDD system, a maximum of three first-level USUs can be
connected to the second-level USU. When inter-BBU adaptive SFN/SDMA is enabled in
the LTE TDD system, a maximum of two first-level USUs can be connected to the
second-level USU.
l The USU can house a maximum of five UCXUs and one UCIU. The UCIU is always
installed in slot 5.
l The slot number of the two boards connected by a baseband interconnection cable must
be the same.
For example, the UCXU connected to the UCXU in slot 3 of a first-level USU must also
be installed in slot 3 of the second-level USU.
l A first-level USU must be connected to the UCIU and UCXU ports with the same
number in the second-level USU.
For example, if a first-level USU is connected to the M0 port on the UCIU in the second-
level USU using an infrastructure interconnection cable, the first-level USU must be
connected to the M0 ports on the UCXUs in the second-level USU using a baseband
interconnection cable.
l In a BBU that is connected to a USU, the main control board must be a UMPT (UMPTa
or UMPTb), and the BBPs must be UBBPd or LBBPd boards.

SingleRAN
Parameter Description 4 Clock Synchronization Solutions
4 Clock Synchronization Solutions
This chapter describes the optional features TDLOFD-081213 Inter-BBU Clock Sharing and
LOFD-081220 Inter-BBU Clock Sharing.
After BBUs are interconnected, links on the user and control planes are automatically set up
without manual configuration. To meet the time synchronization requirements of cell
coordination between interconnected BBUs, one of the following clock synchronization
solutions can be used:
l Solution 1: Each BBU is configured with a clock source for time synchronization, and
the USU clock can work in free-run mode.
l Solution 2: One BBU is configured with the GPS clock source (including the RGPS
clock source) for time synchronization and shares the clock source with its
interconnected BBUs.
Both of the preceding solutions apply to inter-BBU cell coordination in LTE FDD and LTE
TDD systems.

SingleRAN
4.1 Solution 1
This solution applies when each BBU is configured with a clock source and the USU clock
work in free-run mode. Figure 4-1 shows clock synchronization solution 1.
Figure 4-1 Clock synchronization solution 1
4.2 Solution 2
This solution applies when a GPS clock source is shared among multiple eNodeBs. In this
solution, when BBUs are interconnected and one eNodeB obtains a GPS clock source, other
eNodeBs can share the GPS clock source, as shown in Figure 4-2.
Two eNodeBs can provide clock sources in backup mode to ensure that clock signals are
available for time synchronization when the clock source on one of the eNodeBs is abnormal.

SingleRAN
Figure 4-2 Clock synchronization solution 2

SingleRAN
Parameter Description 5 Related Features
5 Related Features
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None

SingleRAN
Parameter Description 6 Network Impact
6 Network Impact
6.1 System Capacity

The multi-BBU interconnection feature has no impact on system capacity. However, other
features can increase system capacity after the multi-BBU interconnection feature is enabled.
This is because the multi-BBU interconnection feature facilitates inter-BBU cell coordination.
For details about these features, see Service Features Supported.
6.2 Network Performance

The multi-BBU interconnection feature has no impact on network performance. However,
other features can enhance network performance after the multi-BBU interconnection feature
is enabled. This is because the multi-BBU interconnection feature facilitates inter-BBU cell
coordination. For details about these features, see Service Features Supported.

SingleRAN
Parameter Description 7 Engineering Guidelines
7 Engineering Guidelines
7.1 When to Use Multi-BBU Interconnection

This feature applies to the following scenarios:
l Service cooperation between multiple base stations, for example, cooperation for UL
CoMP based on coordinated BBU.
l Multiple BBUs share GPS or RGPS clock sources.
7.2 Required Information

Collect the initial configurations of the BBUs and USUs involved in multi-BBU
interconnection. For details, see 3900 Series Base Station Initial Configuration Guide and
USU3900 Initial Configuration Guide.
7.3 Planning
Before deploying the multi-BBU interconnection feature, plan the following items:
l BBU and USU installation positions and USU hardware

l Transmission modes
7.3.1 BBU and USU Installation Position and USU Hardware

Planning
For details about BBU and USU installation positions, see Base Station Cabinets and
Subracks (Including the BBU Subrack) Configuration Feature Parameter Description. After
the installation positions have been planned, plan USU hardware according to 3 Multi-BBU
Interconnection Modes.
7.3.2 Transmission Mode Planning

l The multi-BBU interconnection feature has no additional requirements for the base
station transmission mode.

SingleRAN
l A USU must set up an operation and maintenance (O&M) channel with the operations
support system (OSS) through the FE/GE0 or FE/GE1 port.
7.4 Deployment
7.4.1 Process
Figure 7-1 shows the process for deploying the multi-BBU interconnection feature.
Figure 7-1 Process
7.4.2 Requirements
Hardware
l In each BBU, the main control board must be a UMPT and connected to the UCIU by
using an infrastructure interconnection cable. The LMPT cannot function as the main
control board in multi-BBU interconnection.

SingleRAN
l In each BBU, LBBPd or UBBPd boards must be installed and connected to UCXUs by
using baseband interconnection cables. Other types of BBPs, such as the LBBPc, cannot
be connected to UCXUs.
License
l To use the multi-BBU interconnection feature, operators must purchase the licenses for
this feature.
– The number of licenses to be purchased depends on the number of NEs to be
connected to USUs.
The number of licenses for a second-level USU depends on the number of first-
level USUs to be connected to the second-level USU.
The number of licenses for a first-level USU depends on the number of BBUs to be
connected to the first-level USU.
NOTE
A license is occupied only when the NE is connected to both the infrastructure

interconnection cable and the baseband interconnection cable. If the NE is connected only to
the infrastructure interconnection cable or baseband interconnection cable, no license is
occupied.
– The license listed in the following table is required.
License BOM Model License Control NE Sales
Code Item Unit
BBU 88032BU LT1S0BBUIP0 BBU Pool US Per NE

Pool L 0 Interconnection Port U
Intercon License (per BBU/
nection USU)
Port
License
l If LTE FDD eNodeBs need to share clock sources, operators must purchase the license
listed in the following table and activate it on these eNodeBs.
Feature Feature Model License NE Sales
ID Name Control Unit
Item
LOFD-0 Inter- LT1S0ICLKS00 Inter-BBU eNodeB per

81220 BBU Clock eNode
Clock Sharing(FD B
Sharing D)
l If LTE TDD eNodeBs need to share clock sources, operators must purchase the license
listed in the following table and activate it on these eNodeBs.

SingleRAN
Feature ID Feature Name Model License NE Sales

Control Item Unit
TDLOFD-08121 Inter-BBU LT1STI Inter-BBU eNode per

3 Clock Sharing BCS00 Clock B eNode
0 Sharing(TDD) B
Other Requirements
l USUs must be installed to interconnect BBUs.
l If two interconnected units are installed in the same cabinet, 2-meter interconnection
cables are used. If two interconnected units are installed in different cabinets, 10-meter
interconnection cables are used. If the two cabinets are located far away from each other,
customized interconnection cables are used and the cable length must be equal to or
shorter than 100 meters.
l Interconnected BBUs must work in the same RAT, such as LTE FDD or LTE TDD.
l The software versions of eNodeBs and USUs must be compatible with those used in the
current version.
7.4.3 Data Preparation

Required Data
Table 7-1 EQUIPMENT MO

Paramete Paramet Setting Notes Data
r Name er ID Source
Open DU EQUIPM In multi-BBU interconnection scenarios, this Network

Interface ENT.OD parameter for each BBU and USU must be set to a plan
ID IID unique value ranging from 1 to 254. (negotiati
on not
required)
Table 7-2 CASCADEPORT MO

Paramete Paramet Setting Notes Data
r Name er ID Source
Switch CASCA It is recommended that this parameter for each port Network
DEPOR used for interconnection be set to ON. plan
T.SW (negotiati
on not
required)
Plan IP addresses for each USU. For details about USU configuration, see USU3900 Initial
Configuration Guide.

SingleRAN
Scenario-specific Data
Clock synchronization configurations vary with RATs and service requirements.
l Clock synchronization solution 1
Table 7-3 TASM MO

Parameter Paramete Setting Notes Data
Name r ID Source
Clock TASM.M Set this parameter to FREE(Free) for each Network

Working ODE USU and MANUAL(Manual) for each plan
Mode BBU. (negotiatio
n not
required)
Selected TASM.CL Set this parameter to GPS(GPS Clock) or Network

Clock KSRC IPCLK(IP Clock) for each BBU. plan
Source (negotiatio
n not
required)
Clock TASM.CL Set this parameter to TIME(TIME) for Network

Synchroniza KSYNCM each BBU. plan
tion Mode ODE (negotiatio
n not
required)
Table 7-4 TASM MO

Parameter Parameter Setting Notes Data
Name ID Source
Cloud BB TASM.CLO Set this parameter to Network

Clock UDSRC ENABLE(ENABLE) for the eNodeB plan
Reference configured with the GPS clock source. (negotiatio
Source Flag Set this parameter to n not
DISABLE(DISABLE) for each required)
eNodeBs receiving GPS clock signals.
Selected Clock TASM.CLK Set this parameter to GPS(GPS Clock) Network

Source SRC for the eNodeB configured with the plan
GPS clock source. (negotiatio
Set this parameter to n not
INTERCLK(Inter Clock) for each required)
eNodeBs receiving GPS clock signals.

SingleRAN

Name ID Source
Clock TASM.CLK Set this parameter to TIME(TIME) Network

Synchronizatio SYNCMOD for each BBU. plan
n Mode E (negotiatio
n not
required)
Table 7-5 INTERCLK MO

Name ID Source
Interconnectio InterClk.L Set this parameter to the default value Network

n Clock No. N 0. plan
(negotiatio
n not
required)
Priority InterClk.P Set this parameter to the priority of the Network

RI GPS or RGPS clock source on an plan
eNodeB receiving GPS or RGPS clock (negotiatio
signals. The value ranges from 1 to 4. n not
The default value is 4, which indicates required)
the lowest priority.
If the MODE parameter of this
eNodeB is set to AUTO(Auto), the
eNodeB selects the clock source with
the highest priority.
7.4.4 Initial Configuration

Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
NOTE
Before starting the initial configuration for multi-BBU interconnection, configure the BBUs and USUs
according to 3900 Series Base Station Initial Configuration Guide and USU3900 Initial Configuration
Guide, respectively.
Before performing batch configuration on the Configuration Management Express (CME), familiarize
yourself with the batch configuration procedure in the "Initially Configuring USUs in Batches" section
in USU3900 Initial Configuration Guide.
Enter the values of the parameters listed in Table 7-6 and Table 7-7 in a summary data file,
which also contains other data for the new eNodeBs to be deployed. Then, import the
summary data file into the Configuration Management Express (CME) for batch
configuration. For detailed instructions, see 3900 Series Base Station Initial Configuration
Guide and USU3900 Initial Configuration Guide.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:

SingleRAN
l The managed objects (MOs) in Table 7-6 and Table 7-7 are contained in a scenario-
specific summary data file. In this situation, set the parameters in the MOs, and then
verify and save the file.
l Some MOs in Table 7-6 and Table 7-7 are not contained in a scenario-specific summary
data file. In this situation, customize a summary data file to include the MOs before you
can set the parameters.
Table 7-6 Multi-BBU interconnection parameters on eNodeBs

MO Sheet in the Summary Parameter Group Remarks
Data File
Equipment Equipment Open DU Interface ID This

parameter has
been set in
the default
template.
CASCADEPO Cascade Port Switch This

RT parameter
must be
customized in
the template.
InterClk InterClk Interconnection Clock No. These

Priority parameters
must be
customized in
the template.
TASM TASM Clock Working Mode This

Selected Clock Source parameter
must be
Cloud BB Clock customized in
Reference Source Flag the template.
Clock Synchronization
Mode
Table 7-7 Multi-BBU interconnection parameters on USUs

Data File
Equipment Equipment Open DU Interface ID This

parameter has
been set in
the default
template.

SingleRAN

Data File
CASCADEPO Cascade Port Switch This

RT parameter
must be
customized in
the template.
TASM TASM Clock Working Mode These

Selected Clock Source parameters
must be
Cloud BB Clock customized in
Reference Source Flag the template.
Clock Synchronization
Mode
Using MML Commands

Step 1 Configure each BBU by following the procedure for configuring a single eNodeB using man-
machine language (MML) commands. For details, see 3900 Series Base Station Initial
Configuration Guide.
Step 2 Configure each USU by following the procedures in section "Initially Configuring a Single
USU Using MML Commands" in USU3900 Initial Configuration Guide.
Step 3 Run the SET EQUIPMENT command on each BBU and USU to specify ODI IDs.
NOTE
The ODI IDs for each BBU and USU must be unique.
You need to restart the BBU and USU to make the ODI IDs take effect.
Step 4 Run the SET CASCADEPORT commands on each BBU and USU to enable the ports
required for interconnection.
NOTE
The alarm generated on an interconnection port can be reported only after the port is enabled. If you do
not need to use an interconnection port, do not enable it. To query the number of an interconnection port,
run the LST CASCADEPORT command. The number of the CI port on the UMPT is 8, and the
number of the HEI port on an LBBPd or a UBBPd is 6.
Step 5 Configure the clock source.

NOTE
The clock synchronization requirements of inter-BBU cell coordination vary with the RAT and
therefore, different configurations are applied. In the LTE FDD or TDD system, inter-BBU cell
coordination requires phase synchronization between eNodeBs (that is, each eNodeB can obtain clock
signals).
a. On each USU, run the SET CLKMODE command with Clock Working Mode set
to FREE(Free).
b. On each eNodeB, run the ADD GPS or ADD IPCLKLINK command to add a
GPS clock link or IP clock link.

SingleRAN
c. On each eNodeB, run the SET CLKMODE command with Selected Clock Source
set to GPS(GPS Clock) or IPCLK(IP Clock).
d. On each eNodeB, run the SET CLKSYNCMODE command with Clock
Synchronization Mode set to TIME(TIME).
a. On the eNodeB configured with the GPS clock source:
n If only one BBU provides the clock source:
1) Run the ADD GPS command to add a GPS clock link.
2) Run the SET CLKMODE command with Selected Clock Source set to
GPS(GPS Clock).
3) Run the SET CLOUDSRC command with Cloud BB Clock Reference
Source Flag set to EANBLE(ENABLE).
4) Run the SET CLKSYNCMODE command with Clock
n If two BBUs provide clock sources in backup mode:
1) Run the ADD GPS command to add a GPS clock link.
2) Run the ADD INTERCLK command with Interconnection Clock No.
set to 0.
3) Run the SET CLKMODE command with Clock Working Mode set to
AUTO(Auto).
4) Run the SET CLKSYNCMODE command with Clock
b. On each eNodeB receiving GPS clock signals:
i. Run the ADD INTERCLK command with Interconnection Clock No. set to
0.
ii. Run the SET CLKMODE command with Selected Clock Source set to
INTERCLK(Inter Clock).
iii. Run the SET CLKSYNCMODE command with Clock Synchronization
Mode set to TIME(TIME).
----End
7.4.5 Activation Observation

Local Observation
Perform local observation on the BBUs and USUs as follows:
l On a BBU, view the following indicators to check the status of the infrastructure and
baseband interconnection cables:
– Indicator of the CI port on the UMPT: If the indicator is steady green, the
infrastructure interconnection cable between the BBU and the USU is properly
connected.
– Indicator of the HEI port on the BBP: If the indicator is steady green, the baseband
interconnection cable between the BBU and the USU is properly connected.
l On a USU, view the following indicators to check the status of the infrastructure and
baseband interconnection cables:

SingleRAN
– Indicator of an M port on the UCIU: If the indicator is steady green, the

infrastructure interconnection cable between the BBU and the first-level USU or
between two levels of USUs is properly connected.
– Indicator of an M port on the UCXU: If the indicator is steady green, the baseband
interconnection cable between the BBU and the first-level USU or between two
levels of USUs is properly connected.
– Indicator of the CI port on the SMPT: If the indicator is steady green, the
infrastructure interconnection cable between two levels of USUs is properly
connected. (If the USU is not configured with an upper-level USU, skip this check
item.)
– Indicator of the M5/S0 port on the UCXU: If the indicator is steady green, the
baseband interconnection cable between two levels of USUs is properly connected.
(If the USU is not configured with an upper-level USU, skip this check item.)
Remote Observation
Run the following command to verify whether multi-BBU interconnection has been enabled:
1. Run the DSP INTERCONTOPO command on a USU to check the status of
connections between the USU and BBUs:
– If the query results are consistent with the network plan, the cables between the
USU and BBUs are properly connected.
– If the query results are not consistent with the network plan, reconnect the cables
between the USU and BBUs.
2. Run the DSP CTRLLNKSTAT command on the USU to check the status of links
carried by infrastructure interconnection cables between the USU and BBUs:
a. If both the packet loss rate and packet error rate on these links are lower than
specified thresholds (such as, 10-5), the links are working properly.
b. If the packet loss rate or packet error rate on these links is higher than or equal to
the threshold, locate and rectify the fault.
3. Run the DSP BBPLNKSTAT command on the USU to check the status of links carried
by baseband interconnection cables between the USU and BBUs:
a. If both the packet loss rate and link disconnection rate on these links are lower than
specified thresholds (such as, 10-5), the links are working properly.
b. If the packet loss rate or link disconnection rate on these links is higher than or
equal to the threshold, locate and rectify the fault.
7.4.6 Reconfiguration
Network reconfiguration includes the following procedures:
l Adding BBUs only
l Adding BBUs and USUs
Adding BBUs Only

This section describes the reconfiguration procedure when the number of BBUs increases
from 2 to 4 and only one USU is configured.
Figure 7-2 shows the hardware configurations before and after two BBUs are added.

SingleRAN
Figure 7-2 Hardware configurations before and after two BBUs are added
l Preparing Hardware
Before reconfiguring data, obtain the devices listed in the following table.
Device Quantity
BBU subrack 2
UMPT board 2
BBP (LBBPd or UBBPd) board 4
Infrastructure interconnection cable 2
Baseband interconnection cable 4
Small form-factor pluggable (SFP) 4

optical module
Quad small form-factor pluggable 8

(QSFP) optical module
Cables, such as the common public radio Based on the site plan
interface (CPRI) cable, transmission
cable, clock cable, power cable, and
monitoring cable
NOTE
An infrastructure interconnection cable connects the CI port on a UMPT board and an M port on the
UCIU board.
A baseband interconnection cable connects port HEI on a BBP board and an M port on a UCXU board.
An SFP optical module is inserted in the CI port on a UMPT board or an M port on the UCIU board.
A QSFP optical module is inserted in the HEI port on a BBP board or an M port on a UCXU board.

SingleRAN
l Installing Hardware
Step 1 Install UMPT and BBP boards in BBU2 and BBU3, and connect cables, such as CPRI cables,
transmission cables, clock cables, power cables, and monitoring cables.
Step 2 Use infrastructure interconnection cables to connect the CI ports on the UMPT boards and the
M ports on the UCIU board. For the restrictions on the preceding cable connections, see
Restrictions.
Step 3 Use baseband interconnection cables to connect the HEI ports on the BBP boards and the M
ports on UCXU boards. For the restrictions on the preceding cable connections, see
Restrictions.
----End
l Reconfiguring Data
Step 1 Configure BBU2 and BBU3 according to 3900 Series Base Station Initial Configuration
Guide.
Step 2 Run the SET EQUIPMENT commands on BBU2 and BBU3 to specify ODI IDs.
NOTE
The setting of the EQUIPMENT.ODIID parameter takes effect only after the SMPT or UMPT resets.
Therefore, a base station must be reset after the initial configuration of the base station is complete.
Step 3 Run the SET CASCADEPORT commands on BBU2, BBU3, and the USU to enable the
ports required for interconnection: On BBU2 and BBU3, enable the CI ports on the UMPT
boards and the HEI ports on the BBP boards. On the USU, enable the M2 and M3 ports on the
UCXU boards and UCIU board.
NOTE
not need to use an interconnection port, do not enable it.
----End
Adding BBUs and USUs

When 6 to 10 BBUs are interconnected, two levels of USUs are required. This section
describes the reconfiguration procedure when the number of BBUs increases from 5 to 8 and
the number of USUs increases from 1 to 3.
Figure 7-3 shows the hardware configurations after three BBUs and two USUs are added. For
the hardware configurations before BBU and USU addition, see Figure 3-1.

SingleRAN
Figure 7-3 Hardware configurations after three BBUs and two USUs are added
l Preparing Hardware
Before reconfiguring data, obtain the devices listed in the following table.
Device Quantity
BBU subrack 3
USU subrack 2
UMPT board 3
BBP (LBBPd or UBBPd) board 6
SMPT board 2
UCXU board 4
UCIU board 2
Infrastructure interconnection cable 5
Baseband interconnection cable 10
SFP optical module 10
QSFP optical module 20

SingleRAN
Device Quantity
Cables, such as the CPRI cable, Based on the site plan

transmission cable, clock cable, power
cable, and monitoring cable
NOTE
An infrastructure interconnection cable connects the CI port on a UMPT or SMPT board and an M port
on the UCIU board.
A baseband interconnection cable connects the HEI port on a BBP board and an M port on a UCXU
board or connects the S0 port on a UCXU board in a first-level USU and an M port on a UCXU board in
the second-level USU.
An SFP optical module is inserted in the CI port on a UMPT or SMPT board or an M port on a UCIU
board.
A QSFP optical module is inserted in the HEI port on a BBP board or an M port or the M/S0 port on a
UCXU board.
l Installing Hardware
Step 1 Install UMPT and BBP boards in BBU5 to BBU7, and connect cables, such as CPRI cables,
transmission cables, clock cables, power cables, and monitoring cables.
Step 2 Install SMPT, UCXU, and UCIU boards in USU1 and USU2, and connect cables, such as
transmission cables, power cables, and monitoring cables.
Step 3 Use infrastructure interconnection cables to connect the CI ports on the UMPT boards in
BBU5 to BBU7 and the M ports on the UCIU board in USU1. For the restrictions on the
preceding cable connections, see Restrictions.
Step 4 Use baseband interconnection cables to connect the HEI ports on the BBP boards in BBU5 to
BBU7 and the M ports on UCXU boards in USU1. For the restrictions on the preceding cable
connections, see Restrictions.
Step 5 Use infrastructure interconnection cables to connect the CI ports on the SMPT boards in
USU0 and USU1 and the M ports on the UCIU board in USU2. For the restrictions on the
Step 6 Use baseband interconnection cables to connect the S0 ports on the UCXU boards in USU0
and USU1 and the M ports on the UCXU boards in USU2. For the restrictions on the
----End
l Reconfiguring Data
Step 1 Configure BBU5 to BBU7 according to 3900 Series Base Station Initial Configuration Guide.
Step 2 Configure USU1 and USU2 according to instructions in section "Initially Configuring a
Single USU Using MML Commands" in USU3900 Initial Configuration Guide.
Step 3 Run the SET EQUIPMENT command to specify the ODI IDs for USU1, USU2, and BBU5
to BBU7.
NOTE
The setting of the EQUIPMENT.ODIID parameter takes effect only after the SMPT or UMPT resets.
Therefore, a base station must be reset after the initial configuration of the base station is complete.

SingleRAN
Step 4 Run the SET CASCADEPORT commands on BBU5 to BBU7 and USU0 to USU2 to enable
the ports required for interconnection: On BBU5 to BBU7, enable the CI ports on the UMPT
boards and the HEI ports on the BBP boards. On USU0, enable the CI port on the SMPT
board and the S ports on the UCXU boards. On USU1, enable the CI port on the SMPT board,
the M0, M1, M2, and S ports on the UCXU boards, and the M0, M1, and M2 ports on the
UCIU board. On USU2, enable the M0 and M1 ports on the UCXU boards and UCIU board.
NOTE
not need to use an interconnection port, do not enable it.
----End
7.4.7 MML Command Examples

NOTE
The parameter settings in the following commands are used for reference only. Set the parameters based
on network conditions.
For the MML command examples related to USU initial configuration, see the following section in
USU3900 Initial Configuration Guide > Initially Configuring a Single USU Using MML Commands
> Typical Configuration Example.
On the eNodeB:
l Basic configuration
//Specifying the ODI ID for a BBU
SET EQUIPMENT: ODIID=175;
//Resetting the eNodeB to make the ODI ID take effect
RST BTSNODE:;
//Enabling the HEI port on the BBP board in slot 3
SET CASCADEPORT: CN=0, SRN=0, SN=3, PN=6, SW=ON;
//Enabling the CI port on the UMPT board in slot 6
l Configuration for clock synchronization solution 2
– On the eNodeB configured with the GPS clock source:
n If only one BBU is configured with the clock source:
//Adding a GPS clock link
ADD GPS: GN=0, CN=0, SRN=0, SN=7, CABLE_LEN=20, MODE=GPS,
PRI=1;
//Specifying the working mode of the reference clock source
SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0;
//Enabling the GPS clock source for time synchronization in the Cloud BB
network
SET CLOUDSRC: CLOUDSRC=ENABLE;
//Specifying the clock synchronization mode of the eNodeB
SET CLKSYNCMODE: CLKSYNCMODE=TIME;
n If two BBUs provide clock sources in backup mode:
//Adding a GPS clock link

SingleRAN
ADD GPS: GN=0, CN=0, SRN=0, SN=7, CABLE_LEN=20, MODE=GPS,

PRI=1;
//Adding a clock link
ADD INTERCLK: LN=0;
SET CLKMODE: MODE=AUTO;
– On each eNodeB receiving GPS clock signals:
//Adding a clock link
ADD INTERCLK: LN=0;
SET CLKMODE: MODE=MANUAL, CLKSRC= INTERCLK, SRCNO=0;
On the USU:
//Specifying the ODI ID for a USU
SET EQUIPMENT: ODIID=125;
//Resetting the USU to make the ODI ID take effect
RST BTSNODE:;
//Enabling the M0 port on the UCXU board in slot 3
//Enabling the M0 port on the UCIU board in slot 5
//Enabling the S0 port on the UCXU board in slot 3
7.5 Parameter Optimization

None
7.6 Troubleshooting
Alarms related to multi-BBU interconnection are reported due to the following reasons:
l Two or more NEs involved in multi-BBU interconnection are configured with the same
ODI ID.
l An optical module for connecting a BBU and a USU is faulty or cannot be detected, data
transmission fails on the optical port where the optical module is installed, or the optical
port where the optical module is installed is faulty.

SingleRAN
l Cables are incorrectly connected between a BBU and a USU.

If an alarm listed in Table 7-8 and Table 7-9 is generated, clear the alarm by referring to the
alarm handling suggestions in the alarm reference.
Table 7-8 Alarms related to BBUs

Alarm ID Alarm Name
26116 Inter-NE Address Conflict
26310 Inter-BBU Optical Module Fault
26311 Inter-BBU Optical Module Not in Position
26312 Inter-BBU Optical Module Receive Failure
26313 Inter-BBU Optical Module Transmit Failure
26314 Inter-BBU Port Failure
26315 Inter-BBU Port Connection Error
Table 7-9 Alarms related to USUs

Alarm ID Alarm Name
26116 Inter-NE Address Conflict
27105 Interconnected Optical Module Fault
27106 Interconnected Optical Module Not Installed
27107 Interconnected Optical Module Receive Failure
27108 Interconnected Optical Module Transmit Failure
27109 Inter-Port Failure
27110 Inter-Port Connection Error

SingleRAN
Parameter Description 8 Parameters
8 Parameters
Table 8-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
EQUIP ODIID SET None None Meaning: Indicates the ID of the open DU interface
MENT EQUIP (ODI). If this parameter is set to 0, no ID is configured
MENT for the ODI and this base station cannot communicate
LST with other base stations. This parameter applies only
EQUIP to Cloud BB scenarios.
MENT GUI Value Range: 0~254
Unit: None
Actual Value Range: 0~254
Default Value: 0
CASCA SW SET None None Meaning: Indicates the enabled/disabled state of the
DEPOR CASCA port. Alarms can be detected and reported through the
T DEPOR port only when the state of the port is ON.
T GUI Value Range: OFF(Off), ON(On)
LST Unit: None
CASCA
DEPOR Actual Value Range: OFF, ON
T Default Value: OFF(Off)

SingleRAN

nd
TASM MODE SET MRFD- BTS Meaning: Indicates the working mode of the system
CLKM 210501 Clock clock. Manual indicates that a clock source must be
ODE specified by the user. Auto indicates that the system
LBFD-0 Synchro automatically selects a clock source based on the
DSP 03005 nization priority and availability of the clock source. Free
CLKST
AT LBFD-0 Clock indicates that the system clock works in free-running
0300501 Source mode, that is, the system clock does not trace any
LST reference clock source.
LBFD-0 Switchin
CLKM
0300502 g GUI Value Range: AUTO(Auto), MANUAL(Manual),
ODE
LBFD-0 Manuall FREE(Free)
0300503 y or
Unit: None
Automat
LBFD-0 ically Actual Value Range: AUTO, MANUAL, FREE
0300504 Default Value: FREE(Free)
Free-
LBFD-0 running
0300505 Mode
LBFD-0
Synchro
0300506
nization
LOFD-0 with
03013 GPS
LOFD-0 Synchro
0301301 nization
LOFD-0 with
0301302 BITS
LOFD-0 Synchro
0301303 nization
LOFD-0 with
03023 1PPS
Synchro
nization
with
E1/T1
Enhance
d
Synchro
nization
Synchro
nization
with
Ethernet
(ITU-T
G.8261)
IEEE15
88 V2
Clock

SingleRAN

nd
Synchro
nization
Clock
over IP
(Huawei
propriet
ary)
IEEE
1588v2
over
IPv6

SingleRAN

nd
TASM CLKSR SET MRFD- BTS Meaning: Indicates the type of the user-selected clock
C CLKM 210501 Clock source. The UMTS currently does not support
ODE "SyncEth Clock+IP Clock" or "GPS Clock+SyncEth
LBFD-0 Synchro Clock" function.
LST 03005 nization
CLKM GUI Value Range: GPS(GPS Clock), BITS(BITS
ODE LBFD-0 Clock Clock), IPCLK(IP Clock), SYNCETH(SyncEth
0300501 Source Clock), LINECLK(Line Clock), TOD(TOD Clock),
LBFD-0 Switchin PEERCLK(Peer Clock), SYNCETH+IPCLK(SyncEth
0300503 g Clock+IP Clock), GPS+SYNCETH(GPS Clock
Manuall +SyncEth Clock), INTERCLK(Inter Clock)
LBFD-0
y or
0300504 Unit: None
Automat
LBFD-0 ically Actual Value Range: GPS, BITS, IPCLK, SYNCETH,
0300505 LINECLK, TOD, PEERCLK, SYNCETH+IPCLK,
Synchro
LBFD-0 GPS+SYNCETH, INTERCLK
nization
0300506 with Default Value: GPS(GPS Clock)
LOFD-0 GPS
03013 Synchro
LOFD-0 nization
0301301 with
LOFD-0 BITS
0301302 Synchro
LOFD-0 nization
0301303 with
1PPS
LOFD-0
03023 Synchro
nization
with
E1/T1
Enhance
d
Synchro
nization
Synchro
nization
with
Ethernet
(ITU-T
G.8261)
IEEE15
88 V2
Clock
Synchro
nization
Clock
over IP

SingleRAN

nd
(Huawei
propriet
ary)
IEEE
1588v2
over
IPv6

SingleRAN

nd
TASM CLKSY SET MRFD- BTS Meaning: Indicates the clock synchronization mode of
NCMO CLKSY 210501 Clock a BS, which can be frequency synchronization or time
DE NCMO synchronization.
DE MRFD- Multi-
211601 mode GUI Value Range: FREQ(FREQ), TIME(TIME)
DSP BS Unit: None
CLKST LBFD-0
Commo Actual Value Range: FREQ, TIME
AT 03005
n
LST LBFD-0 Default Value: FREQ(FREQ)
Referen
CLKSY 0300501 ce
NCMO LBFD-0 Clock(G
DE 0300503 BTS)
LBFD-0 Synchro
0300504 nization
LBFD-0 Clock
0300505 Source
LBFD-0 Switchin
0300506 g
LOFD-0 Manuall
03013 y or
Automat
LOFD-0 ically
0301301
Synchro
LOFD-0 nization
0301302 with
LOFD-0 GPS
0301303 Synchro
LOFD-0 nization
03023 with
BITS
Synchro
nization
with
1PPS
Synchro
nization
with
E1/T1
Enhance
d
Synchro
nization
Synchro
nization
with
Ethernet

SingleRAN

nd
(ITU-T
G.8261)
IEEE15
88 V2
Clock
Synchro
nization
Clock
over IP
(Huawei
propriet
ary)
IEEE
1588v2
over
IPv6
TASM CLOUD SET TDLOF Inter- Meaning: Indicates whether the local BBU serves as
SRC CLOUD D-00301 BBU the clock reference source in the Cloud BB.
SRC 304 Clock GUI Value Range: DISABLE(DISABLE),
DSP Synchro ENABLE(ENABLE)
CLOUD nization
Unit: None
SRC
Actual Value Range: DISABLE, ENABLE
LST
CLOUD Default Value: DISABLE(DISABLE)
SRC
INTER LN ADD TDLOF Inter- Meaning: Indicates the number of the interconnection
CLK INTER D-00301 BBU refrence clock link.
CLK 304 Clock GUI Value Range: 0
DSP Synchro
nization Unit: None
INTER
CLK Actual Value Range: 0
RMV Default Value: 0

INTER
CLK
LST
INTER
CLK

SingleRAN

nd
INTER PRI ADD TDLOF Inter- Meaning: Indicates the priority of the clock source.
CLK INTER D-00301 BBU The value 1 indicates that the current clock source has
CLK 304 Clock the highest priority, and the value 4 indicates that the
MOD Synchro current clock source has the lowest priority.
INTER nization GUI Value Range: 1~4
CLK
Unit: None
LST
Actual Value Range: 1~4
INTER
CLK Default Value: 4

SingleRAN
Parameter Description 9 Counters
9 Counters
There are no specific counters associated with this feature.

SingleRAN
Parameter Description 10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

SingleRAN
Parameter Description 11 Reference Documents
11 Reference Documents
1. Base Station Cabinets and Subracks (Including the BBU Subrack) Configuration Feature
Parameter Description
2. Carrier Aggregation Feature Parameter Description in the LTE FDD documentation
3. CSPC Feature Parameter Description in the LTE FDD documentation
4. SFN Feature Parameter Description in the LTE TDD documentation
5. UL CoMP Feature Parameter Description in the LTE FDD documentation
6. USU3900 Hardware Description


USU3900-based Multi-BBU Interconnection (SRAN10.1 - 03)

Uploaded by

Copyright:

Available Formats

You might also like

USU3900-based Multi-BBU Interconnection (SRAN10.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

USU3900-based Multi-BBU Interconnection (SRAN10.1 - 03)

Uploaded by

Copyright:

Available Formats

SingleRAN

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2017-05-29) Huawei Proprietary and Confidential i

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

3 Multi-BBU Interconnection Modes............................................................................................5

4 Clock Synchronization Solutions.............................................................................................16

Issue 03 (2017-05-29) Huawei Proprietary and Confidential ii

Issue 03 (2017-05-29) Huawei Proprietary and Confidential iii

1 About This Document

eNodeB Type Model

Macro 3900 series eNodeB

LampSite l LTE FDD: DBS3900

1.2 Intended Audience

Issue 03 (2017-05-29) Huawei Proprietary and Confidential 1

1.3 Change History

Change Change Description Paramete Affected

Feature None None Macro and

Editorial Added feature name abbreviations. For details, None N/A

Chang Change Description Paramete Affected

Editoria None None N/A

Issue 03 (2017-05-29) Huawei Proprietary and Confidential 2

Chang Change Description Paramete Affected

Editoria None None N/A

SRAN10.1 Draft A (2015-01-15)

Change Change Description Para Affected

Added service features supported by multi-BBU None Macro and

Modified the specifications for interconnection between None Macro and

Editorial Revised descriptions in this document. None Macro and

1.4 Differences Between eNodeB Types

Issue 03 (2017-05-29) Huawei Proprietary and Confidential 3

Issue 03 (2017-05-29) Huawei Proprietary and Confidential 4

3 Multi-BBU Interconnection Modes

l In this document, USU refers to USU3900.

Table 3-1 Multi-BBU interconnection modes

Intercon l To support cell coordination for the following 1 A

Issue 03 (2017-05-29) Huawei Proprietary and Confidential 5

Mode Purpose Number Number

Intercon To support cell coordination for inter-BBU SFN, inter- 3 to 6 A

To share the GPS clock source between BBUs in the 3 to 6 A

To share the RGPS clock source between BBUs in the 3 to 6 A

Service Features Supported

Issue 03 (2017-05-29) Huawei Proprietary and Confidential 6

– LOFD-070223 UL CoMP based on Coordinated BBU (UL CoMP is short for

3.2 Interconnection Between BBUs and a USU

Figure 3-1 Method 1

Issue 03 (2017-05-29) Huawei Proprietary and Confidential 7

SMPT: switch main processing & transmission unit

Figure 3-2 Method 2

Issue 03 (2017-05-29) Huawei Proprietary and Confidential 8

Figure 3-3 Method 3

Issue 03 (2017-05-29) Huawei Proprietary and Confidential 9

Figure 3-4 Method 4

Cable Connection Principles

Issue 03 (2017-05-29) Huawei Proprietary and Confidential 10

Number of BBPs in a Position of a BBP in a Position of a UCXU in

2 Slots 2 and 3 Slots 2 and 3