USU3900 Based Multi BBU Interconnection(SRAN10.1_02)

7/25/2019 USU3900 Based Multi BBU Interconnection(SRAN10.1_02)

1/52

SingleRAN

USU3900-based Multi-BBU

Interconnection Feature Parameter

Description

Issue 02

Date 2015-08-31

HUAWEI TECHNOLOGIES CO., LTD.


2/52

Copyright Huawei Technologies Co., Ltd. 2015. 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 thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,

and recommendations in this document are provided "AS IS" without warranties, guarantees or

representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 02 (2015-08-31) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

i
http://www.huawei.com/


3/52

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.............................................................................................164.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....................................................................................................................217.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

SingleRAN

USU3900-based Multi-BBU Interconnection Feature

Parameter Description Contents



ii


4/52

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

SingleRAN


Parameter Description Contents



iii


5/52


6/52

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 02 (2015-08-31)

This issue includes the following changes.

Change Type

Change Description Parameter Change

AffectedEntity

Feature

change

Added configurations of two eNodeBs that function

as source clock providers. For details, see 7.4.4

Initial Configurationand 7.4.7 MML Command

Examples.

None Macro and

LampSite

eNodeBs

Editoria

l

change

None None N/A

SRAN10.1 01 (2015-03-20)

This issue includes the following changes.

Change Type

Change Description Parameter Change

AffectedEntity

Feature

change

Added the description about hardware licenses

required for multi-BBU interconnection. For details,

see To use the multi-BBU inter....

None Macro and

LampSite

eNodeBs

Editoria

l

change

None None N/A

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

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

SingleRAN


Parameter Description 1 About This Document



2


7/52

ChangeType

Change Description ParameterCha

nge

AffectedEntity

Feature

change

Added the requirement that the licenses for clock

source sharing between eNodeBs be purchased and

activated on these eNodeBs. For details, see 7.4.2

Requirements.

None Macro and

LampSite

eNodeBs

Added service features supported by multi-BBU

interconnection. For details, see 3.1 Introduction.

None Macro and

LampSite

eNodeBs

Modified the specifications for interconnection between

two levels of USUs to achieve inter-BBU cell

coordination in the LTE TDD system. For details, see3.1 Introduction.

None Macro and

LampSite

eNodeBs

Editorial

change

Revised descriptions in this document. None Macro and

LampSite

eNodeBs

1.4 Differences Between eNodeB Types

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

SingleRAN


Parameter Description 1 About This Document



3


8/52

2Overview

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 coordination between inter-BBU cells when features, such as

LAOFD-001003 Carrier Aggregation for 2CC based on Coordinated BBU), are enabled.

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 RGPS clock source.

SingleRAN


Parameter Description 2 Overview



4


9/52

3Multi-BBU Interconnection Modes

3.1 Introduction

Multi-BBU Interconnection Modes

Table 3-1describes multi-BBU interconnection modes.

NOTE

l In the current version, USU3900s are used. 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-1Multi-BBU interconnection modes

Mode Purpose Numberof USUs

Numberof BBUs

Intercon

nection

between

BBUs

and a

USU

l To support the use of the following features for cell

coordination:

UL CoMP based on coordinated BBU, carrier

aggregation for 2CC based on coordinated BBU,

or coordinated scheduling based power control

(Cloud BB) in the LTE FDD system

Inter-BBU SFN or 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,

such as RRU3252 (DC type) and RRU3256 (DC type), in

the LTE TDD system have RGPS antenna ports.

1 A

maximu

m of 5

SingleRAN


Parameter Description 3 Multi-BBU Interconnection Modes



5


10/52

Mode Purpose Numberof USUs

Numberof BBUs

Intercon

nection

between

BBUs

and two

levels of

USUs

To support the use of inter-BBU SFN, inter-BBU

adaptive SFN/SDMA, coordinated scheduling based

power control (Cloud BB), or UL CoMP based on

coordinated BBU in the LTE TDD system for cell

coordination

3 to 6 A

maximu

m of 25

To support the use of carrier aggregation based on

multi-BBU interconnection or coordinated scheduling

based power control (Cloud BB)

3 or 4 A

maximu

m of 15

To share the GPS clock source between BBUs in the

LTE FDD or TDD system

3 to 6 A

maximu

m of 25

To share the RGPS clock source between BBUs in theLTE TDD system

NOTE

RGPS clock source sharing requires that RRUs have RGPS

antenna ports. Currently, only certain RRU models, such as

RRU3252 (DC type) and RRU3256 (DC type), in the LTE

TDD system have RGPS antenna ports.

3 to 6 Amaximu

m of 25

After BBUs are interconnected, each of the eNodeBs and USUs functions as an independent

network element (NE) in the network 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)

TDLOFD-081207 UL CoMP based on Coordinated BBU

l LTE FDD

LOFD-070223 UL CoMP based on Coordinated BBU

LAOFD-070202 Carrier Aggregation for 2CC based on Coordinated BBU

LOFD-070208 Coordinated Scheduling based Power Control (Cloud BB)

SingleRAN





6


11/52

3.2 Interconnection Between BBUs and a USU

Cable ConnectionsNOTE

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-1shows the interconnection between BBUs and a USU for cell coordination.

Figure 3-1Method 1

SingleRAN





7


12/52

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

Two types of clock sources are available in multi-BBU interconnection: GPS clock source

connected to a BBU, and RGPS clock source connected to an RRU. Figure 3-2and Figure

3-3show multi-BBU interconnection for GPS and RGPS clock source sharing, respectively.

Clock source sharing requires only infrastructure interconnection cables between the BBUs

and USU.

Figure 3-2Method 2

SingleRAN





8


13/52

Figure 3-3Method 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





9


14/52

Figure 3-4Method 4

When one of interconnected BBUs is configured with a clock source (such as BBU4 in

Figure 3-2or 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 toone of ports M0 to M4 on the UCIU in the USU.

NOTE

The M0, M1, M2, M3, and M4 ports are prioritized in descending 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.

NOTE

The M0, M1, M2, M3, and M4/S1 ports are prioritized in descending order.

l An infrastructure interconnection cable functions as a logical control link. On the control

link between a BBU and the USU, the USU port is the upstream port of the BBU port bydefault.

SingleRAN





10


15/52

Application Scenarios

Table 3-2shows the application scenarios for the interconnection between BBUs and a USU.

Table 3-2Application scenarios for the interconnection between BBUs and a USU

Number of BBPs in aBBU Connected to theUSU

Position of a BBP in aBBU

Position of a UCXU inthe 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. The upper limit is 5 for LTE.

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 ports with the same number on the UCIU and UCXUs

in a USU using an infrastructure interconnection cable and baseband interconnection

cables, respectively.

For example, if a BBU is connected to the M0 port on the UCIU in a USU, the BBU

must be connected to the M0 ports on the UCXUs in the USU.

l

In a BBU that is connected to the USU, the main control board must be a UMPT(UMPTa or UMPTb), and the BBPs must be UBBPd or LBBPd boards.

SingleRAN





11


16/52

l UBBPd and LBBPd boards apply to the LTE FDD and LTE TDD systems.

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-5shows the interconnection between BBUs and two levels of USUs for cell

coordination.

Figure 3-5Method 1

Two types of clock sources are available in multi-BBU interconnection: GPS clock source

connected to a BBU, and RGPS clock source connected to an RRU. Figure 3-6and Figure

3-7show multi-BBU interconnection for GPS and RGPS clock source sharing, respectively.

Clock source sharing requires only infrastructure interconnection cables between the BBUs

and USUs.

SingleRAN





12


17/52

Figure 3-6Method 2

Figure 3-7Method 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-8shows the

interconnection method between BBUs and two levels of USUs.

SingleRAN





13


18/52

Figure 3-8Method 4

When one of interconnected BBUs is configured with a clock source (such as BBU0 in

Figure 3-6or 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 and the other connected BBUs.

3. The second-level USU 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 of a first-level

USU to one of ports M0 to M4 on the UCIU of the second-level USU.

NOTE

The M0, M1, M2, M3, and M4 ports are prioritized in descending order.

l A baseband interconnection cable connects the M5/S0 port on a UCXU of the first-level

USU to one of ports M0 to M4/S1 on the UCXU of the second-level USU.

NOTE

The M0, M1, M2, M3, and M4/S1 ports are prioritized in descending order.

For details about cable connections between BBUs and a USU, see 3.2 Interconnection

Between BBUs and a USU.

Application Scenarios

Table 3-3lists the application scenarios for the interconnection between BBUs and two levels

of USUs.

SingleRAN





14


19/52

Table 3-3Application scenarios for the interconnection between BBUs and two levels of

USUs

Number of BBPs ina BBU Connected

to a First-LevelUSU

Position of anLBBPd/UBBPd in

a BBU

Position of aUCXU in a First-

Level USU

Position of aUCXU in the

Second-LevelUSU

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 carrier aggregation for 2CC based on

coordinated 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, only 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 alwaysinstalled 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 ports with the same number on the UCIU and

UCXUs in the second-level USU using an infrastructure interconnection cable and

baseband interconnection cables, respectively.

For example, if a first-level USU is connected to the M0 port on the UCIU in the second-

level USU, this first-level USU must be connected to the M0 ports on the UCXUs in the

second-level USU.

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





15


20/52

4Clock Synchronization SolutionsThis 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


Parameter Description 4 Clock Synchronization Solutions



16


21/52

4.1 Solution 1

This solution applies to inter-BBU cell coordination only in the LTE FDD or TDD system.

Figure 4-1shows clock synchronization solution 1.

Figure 4-1Clock 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 for backup to ensure that clock signals are available

for time synchronization when the clock source on one of the eNodeBs is faulty.

SingleRAN





17


22/52

Figure 4-2Clock synchronization solution 2

SingleRAN





18


23/52

5Related FeaturesPrerequisite Features

None

Mutually Exclusive Features

None

Impacted Features

None

SingleRAN


Parameter Description 5 Related Features



19


24/52

6Network 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 6 Network Impact



20


25/52

7Engineering Guidelines

7.1 When to Use Multi-BBU Interconnection

This feature applies to the following scenarios:

l Multiple service cooperation between different base stations, for example, 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 Guideand

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 HardwarePlanning

For details about BBU and USU installation positions, seeBase 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 basestation transmission mode.

SingleRAN


Parameter Description 7 Engineering Guidelines



21


26/52

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-1shows the process for deploying the multi-BBU interconnection feature.

Figure 7-1Process

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 maincontrol board in multi-BBU interconnection.

SingleRAN





22


27/52

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.

Licensel 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 infrastructureinterconnection 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 BOMCode

Model License ControlItem

NE SalesUnit

BBU

Pool

Intercon

nection

Port

License

88032BU

L

LT1S0BBUIP0

0

BBU Pool

Interconnection Port

License (per BBU/

USU)

US

U

Per NE

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.

FeatureID

FeatureName

Model LicenseControlItem

NE SalesUnit

LOFD-0

81220

Inter-

BBUClock

Sharing

LT1S0ICLKS00 Inter-BBU

ClockSharing(FD

D)

eNodeB per

eNodeB

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





23


28/52

Feature ID Feature Name Model LicenseControl Item

NE SalesUnit

TDLOFD-08121

3

Inter-BBU

Clock Sharing

LT1STI

BCS00

0

Inter-BBU

Clock

Sharing(TDD)

eNode

B

per

eNode

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-1MO EQUIPMENT

Parameter Name

Parameter ID

Setting Notes DataSource

Open DU

Interface

ID

EQUIPM

ENT.OD

IID

In multi-BBU interconnection scenarios, the

parameter for each BBU and USU must be set to a

unique value ranging from 1 to 254.

Network

plan

(negotiati

on not

required)

Table 7-2MO CASCADEPORT

Parameter Name

Parameter ID


Switch CASCA

DEPOR

T.SW

It is recommended that this switch be set to ON. Network

plan

(negotiati

on not

required)

Operators must plan IP addresses for each USU. For details about USU configuration, seeUSU3900 Initial Configuration Guide.

SingleRAN





24


29/52

Scenario-specific Data

Clock synchronization configurations vary with RATs and service requirements.

l Clock synchronization solution 1

Table 7-3MO TASM

ParameterName

Parameter ID


Clock

Working

Mode

TASM.M

ODE

Set this parameter to FREE(Free)for each

USU and MANUAL(Manual)for each

BBU.

Network

plan

(negotiatio

n not

required)

Selected

Clock

Source

TASM.CL

KSRC

Set this parameter to GPS(GPS Clock)or

IPCLK(IP Clock)for each BBU.

Network

plan

(negotiatio

n not

required)

Clock

Synchroniza

tion Mode

TASM.CL

KSYNCM

ODE

Set this parameter to TIME(TIME)for

each BBU.

Network

plan

(negotiatio

n not

required)


Table 7-4MO TASM

ParameterName

ParameterID


Cloud BB

Clock

Reference

Source Flag

TASM.CLO

UDSRC

Set this parameter to

ENABLE(ENABLE)for the eNodeB

configured with the GPS clock source.


DISABLE(DISABLE)for each

eNodeBs receiving GPS clock signals.

Network

plan

(negotiatio

n not

required)

Selected Clock

Source

TASM.CLK

SRC

Set this parameter to GPS(GPS Clock)

for the eNodeB configured with the

GPS clock source.


INTERCLK(Inter Clock)for each

eNodeBs receiving GPS clock signals.

Network

plan

(negotiatio

n not

required)

SingleRAN





25


30/52

ParameterName

ParameterID


Clock

Synchronizatio

n Mode

TASM.CLK

SYNCMOD

E

Set this parameter to TIME(TIME)

for each BBU.

Network

plan

(negotiatio

n not

required)

Table 7-5MO INTERCLK

ParameterName

ParameterID


Interconnectio

n Clock No.

InterClk.L

N

The default value is 0. Network

plan(negotiatio

n not

required)

Priority InterClk.P

RI

Set this parameter to the priority of the

GPS or RGPS clock source on an

eNodeB receiving GPS or RGPS clock

signals. The value ranges from 1 to 4.

The default value is 4, which indicates

the lowest priority.

If the system clock working mode of

this eNodeB is set to AUTO(Auto), theeNodeB selects the clock source with

the highest priority.

Network

plan

(negotiatio

n not

required)

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 Guideand 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-6and Table 7-7in 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

Guideand USU3900 Initial Configuration Guide.

The summary data file may be a scenario-specific file provided by the CME or a customizedfile, depending on the following conditions:

SingleRAN





26


31/52

l The managed objects (MOs) in Table 7-6and Table 7-7are 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-6and Table 7-7are not contained in a scenario-specific summary

data file. In this situation, customize a summary data file to include the MOs before youcan set the parameters.

Table 7-6Multi-BBU interconnection parameters on eNodeBs

MO Sheet in the SummaryData File

Parameter Group Remarks

EQUIPMENT Equipment Open DU Interface ID This

parameter has

been set in

the default

template.

CASCADEPO

RT

Cascade Port Switch This

parameter

must be

customized in

the template.

INTERCLK InterClk Interconnection Clock No.

Priority

These

parameters

must be

customized in

the template.

TASM TASM Clock Working Mode

Selected Clock Source

Cloud BB Clock

Reference Source Flag

Clock Synchronization

Mode

This

parameter

must be

customized in

the template.

Table 7-7Multi-BBU interconnection parameters on USUs



EQUIPMENT Equipment Open DU Interface ID This

parameter has

been set in

the default

template.

SingleRAN





27


32/52



CASCADEPO

RT

Cascade Port Switch This

parameter

must be

customized in

the template.

TASM TASM Clock Working Mode

Selected Clock Source

Cloud BB Clock

Reference Source Flag

Clock Synchronization

Mode

These

parameters

must be

customized in

the template.

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 according to the "Configuration for a Single USU" section in USU3900Initial Configuration Guide.

Step 3 Run the SET EQUIPMENTcommand 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 CASCADEPORTcommands on each BBU and USU to enable the portsrequired 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 CASCADEPORTcommand. 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. 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 CLKMODEcommand with Clock Working Modeset

to FREE(Free).

b. On each eNodeB, run the ADD GPSor ADD IPCLKLINKcommand to add aGPS clock link or IP clock link.

SingleRAN





28


33/52

c. On each eNodeB, run the SET CLKMODEcommand with Selected Clock Source

set to GPS(GPS Clock)or IPCLK(IP Clock).

d. On each eNodeB, run the SET CLKSYNCMODEcommand with Clock

Synchronization Modeset 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 GPScommand to add a GPS clock link.

2) Run the SET CLKMODEcommand with Selected Clock Sourceset to

GPS(GPS Clock).

3) Run the SET CLOUDSRCcommand with Cloud BB Clock Reference

Source Flagset to EANBLE(ENABLE).

4) Run the SET CLKSYNCMODEcommand with Clock


n If two BBUs provide clock sources for backup:

1) Run the ADD GPScommand to add a GPS clock link.

2) Run the ADD INTERCLKcommand with Interconnection Clock No.

set to 0.

3) Run the SET CLKMODEcommand with Clock Working Modeset to

AUTO(Auto).

4) Run the SET CLKSYNCMODEcommand with Clock


b. On each eNodeB receiving GPS clock signals:

i. Run the ADD INTERCLKcommand with Interconnection Clock No.set to0.

ii. Run the SET CLKMODEcommand with Selected Clock Sourceset to

INTERCLK(Inter Clock).

iii. Run the SET CLKSYNCMODEcommand with Clock Synchronization

Modeset 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 andbaseband interconnection cables:

SingleRAN





29


34/52

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 twolevels 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 only one USU is configured, 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 only one USU is configured, skip this check item.)

Remote Observation

Run the following command to verify whether multi-BBU interconnection has been enabled:

1. Run the DSP INTERCONTOPOcommand 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 CTRLLNKSTATcommand 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 BBPLNKSTATcommand 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-2shows the hardware configurations before and after two BBUs are added.

SingleRAN





30


35/52

Figure 7-2Hardware 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 2

BBP (LBBPd/UBBPd) 4

Infrastructure interconnection cable 2

Baseband interconnection cable 4

Small form-factor pluggable (SFP)

optical module

4

QSFP optical module 8

Cables, such as the common public radio

interface (CPRI) cable, transmission

cable, clock cable, power cable, and

monitoring cable

Based on the site plan

NOTE

An infrastructure interconnection cable connects the CI port on a UMPT to an M port on the UCIU.

A baseband interconnection cable connects port HEI on a BBP to an M port on a UCXU.

An SFP optical module is inserted in the CI port on a UMPT or an M port on the UCIU.

A QSFP optical module is inserted in the HEI port on a BBP or an M port on a UCXU.

l Installing Hardware

SingleRAN





31


36/52

Step 1 Install UMPTs and BBPs 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 UMPTs to the M portson the UCIU. For details about the restrictions on the preceding cable connections, see

Restrictions.

Step 3 Use baseband interconnection cables to connect the HEI ports on the BBPs to the M ports onUCXUs. For details about 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 ConfigurationGuide.

Step 2 Run the SET EQUIPMENTcommands on BBU2 and BBU3 to specify ODI IDs.NOTE

The setting of the EQUIPMENT.ODIIDparameter 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 CASCADEPORTcommands on BBU2, BBU3, and the USU to enable theports required for interconnection: On BBU2 and BBU3, enable the CI ports on the UMPTs

and the HEI ports on the BBPs. On the USU, enable the M2 and M3 ports on the UCXUs and

UCIU.

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.

For the hardware configurations before BBU and USU addition, see Figure 3-1. Figure 7-3

shows the hardware configurations after three BBUs and two USUs are added

SingleRAN





32


37/52

Figure 7-3Hardware configurations after three BBUs and two USUs are added

lPreparing HardwareBefore reconfiguring data, obtain the devices listed in the following table.

Device Quantity

BBU subrack 3

USU subrack 2

UMPT 3

BBP (LBBPd, UBBPd, or WBBPf4) 6

SMPT 2

UCXU 4

UCIU 2

Infrastructure interconnection cable 5

Baseband interconnection cable 10

Small form-factor pluggable (SFP)

optical module

10

QSFP optical module 20

SingleRAN





33


38/52

Device Quantity

Cables, such as the common public radio

interface (CPRI) cable, transmission

cable, clock cable, power cable, and

monitoring cable

Based on the site plan

NOTE

An infrastructure interconnection cable connects the CI port on a UMPT to an M port on the UCIU of a

first-level USU or connects the CI port on the SMPT of a first-level USU to an M port on the UCIU of

the second-level USU.

A baseband interconnection cable connects the HEI port on a BBP to an M port on a UCXU or connects

the S0 port on a UCXU of a first-level USU to an M port on a UCXU of the second-level USU.

An SFP optical module is inserted in the CI port on a UMPT or SMPT or an M port on a UCIU.

A QSFP optical module is inserted in the HEI port on a BBP or an M port or the S0 port on a UCXU.

l Installing Hardware

Step 1 Install UMPTs and BBPs in BBU5 to BBU7, and connect cables, such as CPRI cables,transmission cables, clock cables, power cables, and monitoring cables.

Step 2 Install SMPTs, UCXUs, and UCIUs in USU1 and USU2, and connect cables, such astransmission cables, power cables, and monitoring cables.

Step 3 Use infrastructure interconnection cables to connect the CIports on the UMPTs to the M portson the UCIU in USU1. For details about the restrictions on the preceding cable connections,

see Restrictions.

Step 4 Use basebandinterconnection cables to connect the HEI ports on the BBPs to the M ports onUCXUs in USU1. For details about the restrictions on the preceding cable connections, see

Restrictions.

Step 5 Use infrastructure interconnection cables to connect the CI ports on the SMPTs in USU0 andUSU1 to the M ports on the UCIU in USU2. For details about the restrictions on the

preceding cable connections, see Restrictions.

Step 6 Use baseband interconnection cables to connect the S0 ports on the UCXUs in USU0 andUSU1 to the M ports on the UCXUs in USU2. For details about the restrictions on the

preceding cable connections, see Restrictions.

----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 the "Configuration for a Single USU" section inUSU3900 Initial Configuration Guide.

Step 3 Run the SET EQUIPMENTcommands on BBU5, BBU6, BBU7, USU0, and USU1 tospecify ODI IDs.

NOTE

The setting of the EQUIPMENT.ODIIDparameter 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





34


39/52

Step 4 Run the SET CASCADEPORTcommands on BBU5, BBU6, BBU7, USU0, USU1, andUSU2 to enable the ports required for interconnection: On BBU5 to BBU7, enable the CI

ports on the UMPTs and the HEI ports on the BBPs. On USU0, enable the CI port on the

SMPT and the S ports on the UCXUs. On USU1, enable the CI port on the SMPT, the M0,

M1, M2, and S0 ports on the UCXUs, and the M0, M1, and M2 ports on the UCIU. On

USU2, enable the M0 and M1 ports on the UCXUs and UCIU.

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 of USU initial configuration, see the following section in USU3900

Initial Configuration Guide: Configuration for a Single USU > Typical Configuration Script

On the eNodeB:

l Basic configuration

//Specifying the ODI ID for a BBU

SET EQUIPMENT: ODIID=175;

//Resetting the eNodeB

RST BTSNODE:;//Enabling the HEI port on the BBP in slot 3

SET CASCADEPORT: CN=0, SRN=0, SN=3, PN=6, SW=ON;

//Enabling the CI port on the UMPT in slot 6


l Configuration for clock synchronization solution 2

On the eNodeB configured with the GPS clock source:

n If only one BBU provides 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 for backup:

//Adding a GPS clock link

SingleRAN





35


40/52

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 the 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

RST BTSNODE:;

//Enabling the M0 port on the UCXU in slot 3


//Enabling the M0 port on the UCIU in slot 5


//Enabling the S0 port on the UCXU in slot 3


7.5 Parameter OptimizationNone

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 or receiving fails on the optical port where the optical module is installed,or the optical port where the optical module is installed is faulty.

SingleRAN





36


41/52

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

If an alarm listed in Table 7-8and Table 7-9is generated, clear the alarm by referring to the

alarm handling suggestions in the alarm reference.

Table 7-8Alarms 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-9Alarms related to USUs

Alarm ID Alarm Name

26116 Inter-NE Address Conflict

27105 Interconnected Optical Module Fault27106 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





37


42/52

8ParametersTable 8-1Parameters

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

EQUIP

MENT

ODIID SET

EQUIP

MENT

LST

EQUIP

MENT

None None Meaning: Indicates the ID of the open DU interface

(ODI). If this parameter is set to 0, no ID is configured

for the ODI and this base station cannot communicate

with other base stations. This parameter applies only

to Cloud BB scenarios.

GUI Value Range: 0~254

Unit: None

Actual Value Range: 0~254

Default Value: 0

CASCA

DEPOR

T

SW SET

CASCA

DEPOR

T

LST

CASCA

DEPOR

T

None None Meaning: Indicates the enabled/disabled state of the

port. Alarms can be detected and reported through the

port only when the state of the port is ON.

GUI Value Range: OFF(Off), ON(On)

Unit: None

Actual Value Range: OFF, ON

Default Value: OFF(Off)

SingleRAN


Parameter Description 8 Parameters



38


43/52

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TASM MODE SET

CLKM

ODE

DSP

CLKST

AT

LST

CLKM

ODE

MRFD-

210501

LBFD-0

03005

LBFD-0

0300501

LBFD-0

0300502

LBFD-0

0300503

LBFD-00300504

LBFD-0

0300505

LBFD-0

0300506

LOFD-0

03013

LOFD-0

0301301

LOFD-0

0301302

LOFD-0

0301303

LOFD-0

03023

BTS

Clock

Synchro

nization

Clock

Source

Switchin

g

Manuall

y or

Automat

icallyFree-

running

Mode

Synchro

nization

with

GPS

Synchro

nization

with

BITS

Synchro

nization

with

1PPS

Synchro

nization

with

E1/T1

Enhance

dSynchro

nization

Synchro

nization

with

Ethernet

(ITU-T

G.8261)

IEEE15

88 V2

Clock

Meaning: Indicates the working mode of the system

clock. Manual indicates that a clock source must be

specified by the user. Auto indicates that the system

automatically selects a clock source based on the

priority and availability of the clock source. Free

indicates that the system clock works in free-running

mode, that is, the system clock does not trace any

reference clock source.

GUI Value Range: AUTO(Auto), MANUAL(Manual),

FREE(Free)

Unit: None

Actual Value Range: AUTO, MANUAL, FREEDefault Value: FREE(Free)

SingleRAN





39


44/52

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

Synchro

nization

Clock

over IP

(Huawei

propriet

ary)

IEEE

1588v2

over

IPv6

SingleRAN





40


45/52

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TASM CLKSR

C

SET

CLKM

ODE

LST

CLKM

ODE

MRFD-

210501

LBFD-0

03005

LBFD-0

0300501

LBFD-0

0300503

LBFD-0

0300504

LBFD-00300505

LBFD-0

0300506

LOFD-0

03013

LOFD-0

0301301

LOFD-0

0301302

LOFD-0

0301303

LOFD-0

03023

BTS

Clock

Synchro

nization

Clock

Source

Switchin

g

Manuall

y or

Automat

icallySynchro

nization

with

GPS

Synchro

nization

with

BITS

Synchro

nization

with1PPS

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

Meaning: Indicates the type of the user-selected clock

source. The UMTS currently does not support

"SyncEth Clock+IP Clock" or "GPS Clock+SyncEth

Clock" function.

GUI Value Range: GPS(GPS Clock), BITS(BITS

Clock), IPCLK(IP Clock), SYNCETH(SyncEth

Clock), LINECLK(Line Clock), TOD(TOD Clock),

PEERCLK(Peer Clock), SYNCETH+IPCLK(SyncEth

Clock+IP Clock), GPS+SYNCETH(GPS Clock

+SyncEth Clock), INTERCLK(Inter Clock)

Unit: None

Actual Value Range: GPS, BITS, IPCLK, SYNCETH,LINECLK, TOD, PEERCLK, SYNCETH+IPCLK,

GPS+SYNCETH, INTERCLK

Default Value: GPS(GPS Clock)

SingleRAN





41


46/52

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

(Huawei

propriet

ary)

IEEE

1588v2

over

IPv6

SingleRAN





42


47/52

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TASM CLKSY

NCMO

DE

SET

CLKSY

NCMO

DE

DSP

CLKST

AT

LST

CLKSY

NCMO

DE

MRFD-

210501

MRFD-

211601

LBFD-0

03005

LBFD-0

0300501

LBFD-0

0300503

LBFD-00300504

LBFD-0

0300505

LBFD-0

0300506

LOFD-0

03013

LOFD-0

0301301

LOFD-00301302

LOFD-0

0301303

LOFD-0

03023

BTS

Clock

Multi-

mode

BS

Commo

n

Referen

ce

Clock(G

BTS)

Synchronization

Clock

Source

Switchin

g

Manuall

y or

Automat

ically

Synchro

nizationwith

GPS

Synchro

nization

with

BITS

Synchro

nization

with

1PPS

Synchro

nization

with

E1/T1

Enhance

d

Synchro

nization

Synchro

nization

with

Ethernet

Meaning: Indicates the clock synchronization mode of

a BS, which can be frequency synchronization or time

synchronization.

GUI Value Range: FREQ(FREQ), TIME(TIME)

Unit: None

Actual Value Range: FREQ, TIME

Default Value: FREQ(FREQ)

SingleRAN





43


48/52

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

(ITU-T

G.8261)

IEEE15

88 V2

Clock

Synchro

nization

Clock

over IP

(Huawei

propriet

ary)

IEEE

1588v2

over

IPv6

TASM CLOUD

SRC

SET

CLOUD

SRC

DSP

CLOUD

SRC

LSTCLOUD

SRC

TDLOF

D-00301

304

Inter-

BBU

Clock

Synchro

nization

Meaning: Indicates whether the local BBU serves as

the clock reference source in the Cloud BB.

GUI Value Range: DISABLE(DISABLE),

ENABLE(ENABLE)

Unit: None

Actual Value Range: DISABLE, ENABLE

Default Value: DISABLE(DISABLE)

INTER

CLK

LN ADD

INTER

CLK

DSP

INTER

CLK

RMV

INTERCLK

LST

INTER

CLK

TDLOF

D-00301

304

Inter-

BBU

Clock

Synchro

nization

Meaning: Indicates the number of the interconnection

refrence clock link.

GUI Value Range: 0

Unit: None

Actual Value Range: 0

Default Value: 0

SingleRAN





44


49/52

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

INTER

CLK

PRI ADD

INTER

CLK

MOD

INTER

CLK

LST

INTER

CLK

TDLOF

D-00301

304

Inter-

BBU

Clock

Synchro

nization

Meaning: Indicates the priority of the clock source.

The value 1 indicates that the current clock source has

the highest priority, and the value 4 indicates that the

current clock source has the lowest priority.

GUI Value Range: 1~4

Unit: None

Actual Value Range: 1~4

Default Value: 4

SingleRAN





45


50/52

9CountersThere are no specific counters associated with this feature.

SingleRAN


Parameter Description 9 Counters



46


51/52

10GlossaryFor the acronyms, abbreviations, terms, and definitions, see Glossary.

SingleRAN


Parameter Description 10 Glossary



47


52/52

11Reference Documents1. Base Station Cabinets and Subracks (Including the BBU Subrack) Configuration Feature

Parameter Description

2. Carrier Aggregation Feature Parameter Descriptionin the LTE FDD documentation

3. CSPC Feature Parameter Descriptionin the LTE FDD documentation

4. SFN Feature Parameter Descriptionin the LTE TDD documentation

5. UL CoMP Feature Parameter Descriptionin the LTE FDD documentation

6. USU3900 Hardware Description

SingleRAN


Parameter Description 11 Reference Documents