USU3910 Based Multi BBU Interconnection(SRAN10.1_02)

SingleRAN

USU3910-based Multi-BBU Interconnection Feature Parameter Description Issue

02

Date

2015-08-31

HUAWEI TECHNOLOGIES CO., LTD.

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 the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

Issue 02 (2015-08-31)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

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

2 Overview......................................................................................................................................... 5 2.1 Introduction.................................................................................................................................................................... 5 2.2 Benefits........................................................................................................................................................................... 5

3 Technical Description...................................................................................................................7 3.1 Introduction.................................................................................................................................................................... 7 3.2 Multi-BBU Interconnection Modes................................................................................................................................8 3.2.1 Interconnection Between BBUs and a USU................................................................................................................8 3.2.2 Interconnection Between BBUs and Two Levels of USUs....................................................................................... 11 3.3 Key Configurations.......................................................................................................................................................15 3.3.1 Basic Data Configurations.........................................................................................................................................15 3.3.2 Clock Data Configurations........................................................................................................................................ 26 3.3.2.1 Clock Synchronization Solution 1.......................................................................................................................... 27 3.3.2.2 Clock Synchronization Solution 2.......................................................................................................................... 28 3.3.2.3 Clock Source Backup............................................................................................................................................. 36

4 Related Features...........................................................................................................................39 5 Network Impact........................................................................................................................... 40 6 Engineering Guidelines............................................................................................................. 41 6.1 When to Use Multi-BBU Interconnection....................................................................................................................41 6.2 Required Information................................................................................................................................................... 41 6.3 Planning........................................................................................................................................................................ 41 6.4 Deployment.................................................................................................................................................................. 42 6.4.1 Process....................................................................................................................................................................... 42 6.4.2 Requirements............................................................................................................................................................. 43 6.4.3 Data Preparation and Feature Activation...................................................................................................................46 6.4.3.1 Data Preparation..................................................................................................................................................... 46 6.4.3.2 Activation............................................................................................................................................................... 55 Issue 02 (2015-08-31)


ii


Contents

6.4.4 MML Command Examples....................................................................................................................................... 59 6.4.5 Activation Observation..............................................................................................................................................60 6.4.6 Reconfiguration......................................................................................................................................................... 62 6.4.6.1 Reconfiguration for the Centralized Cloud BB Mode............................................................................................62 6.4.6.1.1 Adding BBUs...................................................................................................................................................... 62 6.4.6.1.2 Removing BBUs..................................................................................................................................................65 6.4.6.1.3 Adding BBUs and USUs..................................................................................................................................... 65 6.4.6.2 Reconfiguration for Distributed Cloud BB Mode.................................................................................................. 67 6.4.6.2.1 Adding BBUs...................................................................................................................................................... 67 6.4.6.2.2 Removing BBUs..................................................................................................................................................69 6.4.6.2.3 Adding BBUs and USUs..................................................................................................................................... 70 6.5 Performance Monitoring...............................................................................................................................................71 6.6 Parameter Optimization................................................................................................................................................ 72 6.7 Troubleshooting............................................................................................................................................................ 72

7 Parameters..................................................................................................................................... 74 8 Counters........................................................................................................................................ 83 9 Glossary......................................................................................................................................... 84 10 Reference Documents............................................................................................................... 85

Issue 02 (2015-08-31)


iii


1 About This Document

1

About This Document

1.1 Scope This document describes the USU3910-based multi-BBU interconnection feature, including its technical principles, related features, network impact, and engineering guidelines. 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 02 (2015-08-31)


1



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

Affected Entity

Feature change

Added support of the GTMUc. For details, see 6.4.2 Requirements.

None

Macro and LampSite eNodeBs

Added scenarios where base stations with BBU interconnection are applicable in centralized Cloud BB mode. For details, see 6.4.2 Requirements.

None


Revised descriptions in this document.

None


Editorial change

SRAN10.1 01 (2015-03-20) This issue includes the following changes.

Issue 02 (2015-08-31)

Chang e Type

Change Description

Paramete r Change

Affected Entity

Feature change

Added descriptions about hardware requirements and licenses to be purchased for multi-BBU interconnection. For details, see 6.4.2 Requirements.

None


Editoria l change


None



2



SRAN10.1 Draft C (2015-03-10) This issue includes the following changes. Chang e Type

Change Description

Paramete r Change

Affected Entity

Feature change

Added descriptions about hardware requirements for inter-BBU interconnection. For details, see 6.4.2 Requirements.

None


Editoria l change


None


SRAN10.1 Draft B (2015-02-10) This issue includes the following changes. Chang e Type

Change Description

Paramete r Change

Affected Entity

Feature change

None

None

N/A

Editoria l change


None


SRAN10.1 Draft A (2015-01-20) Compared with Issue 01 (2014-12-30) of SRAN10.0, Draft A (2015-01-20) of SRAN10.1 includes the following changes.

Issue 02 (2015-08-31)

Chang e Type

Change Description

Paramete r Change

Affected Entity

Feature change

Added descriptions related to the distributed Cloud BB mode.

None


Added the requirement that the license for clock source sharing in a Cloud BB network be purchased and activated on the eNodeBs that receive signals from the clock source. For details, see 6.4.2 Requirements.

None



3


Chang e Type

Editoria l change


Change Description

Paramete r Change

Affected Entity

Added the method of performing link connectivity tests and link performance monitoring based on the ITU-T Y.1731 protocol to locate the connectivity and performance faults in Ethernet links. For details, see 6.7 Troubleshooting.

None


Added the service features supported in a Cloud BB network. For details, see Service Features Supported.

None


None

None

N/A

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.

Issue 02 (2015-08-31)


4


2 Overview

2

Overview

2.1 Introduction USU3910-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 USU3910s. NOTE

l This feature requires USU3910s and BBU3900s or BBU3910s. l In this document, universal switching unit (USU) refers to USU3910 and BBU refers to BBU3900 and BBU3910.

After BBUs are interconnected, each USU and the eNodeB where each BBU is installed function as independent network elements (NEs) on the U2000. A cluster of these NEs form a Cloud BB network. BBUs and USU are connected in either of the following modes: l

Centralized Cloud BB (Ideal Backhaul) (centralized Cloud BB for short)

l

Distributed Cloud BB (Ideal Backhaul) (distributed Cloud BB for short)

In a Cloud BB network, if some BBUs connect to a USU in centralized Cloud BB mode and other BBUs connect to this USU in distributed Cloud BB mode, this networking mode is called the centralized Cloud BB+distributed Cloud BB mode.

2.2 Benefits Multi-BBU interconnection provides the following benefits: l

Helps achieve inter-BBU cell coordination when features, such as Uplink Coordinated Multiple Points Transmission (UL CoMP) based on coordinated BBU, carrier aggregation for 2CC based on coordinated BBU, and coordinated scheduling based power control (Cloud BB), are enabled.

l

Reduces the number of required Global Positioning System (GPS) antennas because interconnected BBUs can share GPS clock sources.

Issue 02 (2015-08-31)


5


2 Overview

NOTE

GPS clock sources include RGPS clock sources.

Issue 02 (2015-08-31)


6


3 Technical Description

3

Technical Description

3.1 Introduction Multi-BBU Interconnection Modes l

Interconnection between BBUs and a USU: Only one USU connects to BBUs, as shown in Figure 3-1. Figure 3-1 Interconnection between BBUs and a USU

l

Interconnection between BBUs and two levels of USUs: Multiple first-level USUs connect to BBUs and one or two second-level USUs connect to the first-level USUs. Three types of connections are involved: connection between first-level USUs and BBUs, connection between first- and second-level USUs, and connection between second-level USUs in centralized Cloud BB mode, as shown in Figure 3-2. Figure 3-2 Interconnection between BBUs and two levels of USUs

Issue 02 (2015-08-31)


7



Service Features Supported l

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)

–

LOFD-081208 Inter-eNodeB SFN Based on Coordinated BBU

–

LOFD-081209 Inter-eNodeB Adaptive SFN/SDMA Based on Coordinated BBU

LTE TDD: –

TDLOFD-001080 Inter-BBU SFN

–

TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA

–

TDLOFD-081207 UL CoMP based on Coordinated BBU

–

TDLOFD-080203 Coordinated Scheduling based Power Control (Cloud BB)

3.2 Multi-BBU Interconnection Modes 3.2.1 Interconnection Between BBUs and a USU The requirements on BBUs and the USU are as follows: l

BBU3900s and BBU3910s can be connected to the same first-level USU.

l

In the USU, a universal enhanced switch fabric unit (UEFU) and a universal line process unit (ULPU) must be available and are always installed in slots 0 and 1, respectively.

l

eNodeBs connecting to the USU are classified into two types: –

An eNodeB configured with one BBU: The BBU is directly connected to the USU.

–

An eNodeB configured with two interconnected BBUs: The BBU configured with the UMPT and UCIU connects to the USU. NOTE

For restrictions on multi-BBU interconnection, see Multi-BBU Interconnection Feature Parameter Description.

Centralized Cloud BB l

Cable connections BBUs and USUs are connected using the following types of cables: –

Cascading interface (CI) interconnection cable: This type of cable connects the CI port on the UMPT in a BBU and a CI-DL port (S0 to S11) on the UEFU in the USU. The cable transmits control information about the topology, clock, heartbeat, and inter-cell link setup and release.

–

High speed extension interface (HEI) interconnection cable for short-distance connection: This type of cable connects the HEI port on a baseband processing unit (BBP) in a BBU and an HEI port (P0 to P29) on the ULPU in the USU. The cable transmits cell coordination information.

l Issue 02 (2015-08-31)

Configuration principles Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

8


l


–

A BBU and the USU can be connected using only one CI interconnection cable and a maximum of six HEI interconnection cables. The number of HEI interconnection cables depends on the number of BBPs in this BBU.

–

The HEI ports on the ULPU work in SCPRI/SRIO mode. The HEI port on a BBP can connect to any HEI port on the ULPU. To facilitate cable routing, you are advised to connect cables according to Figure 3-3.

–

Each USU can connect to a maximum of 5 BBUs. In a Cloud BB network, a maximum of 12 first-level USUs can be configured.

–

UMPT backup is not supported.

–

The maximum distance between a BBU and a first-level USU is 100 m.

Example Figure 3-3 shows the interconnection between BBUs and a USU in centralized Cloud BB mode. Figure 3-3 Centralized Cloud BB

Distributed Cloud BB l

Cable connections HEI interconnection cable for long-distance connection: This type of optical cable connects the M5/S0 port on the universal inter-connection combo unit (UCCU) in a BBU and an HEI port on the ULPU in the USU.

l

Issue 02 (2015-08-31)

Configuration principles –

On a ULPU, the HEI ports connecting to BBUs must work in 4*10GE mode.

–

Each USU can connect to a maximum of 50 BBUs. In a Cloud BB network, a maximum of 6 first-level USUs can be configured.

–

Each UCCU connects to the USU by using a maximum of two optical cables, each of which is used for both transmission and receiving.

–

The maximum length of the optical cable connecting the BBU and a first-level USU is 10 km and that of the optical cable connecting two BBUs that transmit signals through first- and second-level USUs for service coordination is 20 km. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

9


–


Each eNodeB must be configured with only one UCCU. Slots 3, 2, 4, 5, 1, and 0 for the UCCU are prioritized in descending order. NOTE

If the UCCU is installed in slot 0, 1, 4, or 5 instead of slot 2 or 3, it must connect to BBPs using baseband interconnection cables, as shown in Figure 3-4.

Figure 3-4 Connection between the UCCU and BBPs

l

Example –

Figure 3-5 shows the interconnection between BBUs and a USU in distributed Cloud BB mode when each BBU and the USU are connected using two optical cables. Figure 3-5 Interconnection between BBUs and a USU in distributed Cloud BB mode (1)

–

Issue 02 (2015-08-31)

Figure 3-6 shows the interconnection between BBUs and a USU in distributed Cloud BB mode when each BBU and the USU are connected using one optical cable.


10



Figure 3-6 Interconnection between BBUs and a USU in distributed Cloud BB mode (2)

Centralized Cloud BB+Distributed Cloud BB In centralized Cloud BB+distributed Cloud BB mode, BBUs connected in centralized mode and those connected in distributed mode co-exist. However, a BBU can be connected either in centralized or distributed mode, as shown in Figure 3-7. Figure 3-7 Interconnection between BBUs and a USU in centralized Cloud BB+distributed Cloud BB mode

3.2.2 Interconnection Between BBUs and Two Levels of USUs Interconnection between BBUs and two levels of USUs involves the following types of cable connections: Issue 02 (2015-08-31)


11


l

Between first- and second-level USUs

l

Between second-level USUs in centralized Cloud BB mode


First- and second-level USUs are connected in either centralized or distributed Cloud BB mode. NOTE

l In each USU, a UEFU is always installed in slot 0 regardless of centralized or distributed Cloud BB mode. l First- and second-level USUs cannot be connected in centralized Cloud BB+distributed Cloud BB mode. l Within a Cloud BB network, the interconnection between first- and second-level USUs and that between first-level USUs and BBUs are independent.

Centralized Cloud BB l

Cable connections First- and second-level USUs are connected using the following types of cables: –

CI interconnection cable: This type of cable connects the CI-UL port on a first-level USU and a CI-DL port on the second-level USU that functions as a server and whose NodeID is set to 0. It is used to transmit control and synchronization information.

–

FABRIC interconnection cable: This type of cable connects the FABRIC ports on a first-level USU and a second-level USU. It is used to transmit BBU-related data.

When two second-level USUs are configured, they are connected only using a CI interconnection cable. This cable connects the CI-UL port on a second-level USU (that does not function as a server and whose NodeID is not set to 0) and the CI-DL port on the other second-level USU (that functions as a server and whose NodeID is set to 0). l


Each first-level USU must connect to four FABRIC interconnection cables. These cables connect to two FABRIC ports on each UEFU in the second-level USU if only one second-level USU is configured, or connect to a FABRIC port on each UEFU in two second-level USUs if two second-level USUs are configured. Connections of FABRIC interconnection cables have no requirements for FABRIC port numbers. NOTE

(Optional) If the number of first-level USUs connected to a second-level USU does not exceed three, the second-level USU can use only one UEFU. The first-level USUs are connected to the second-level USE through four FABRIC interconnection cables and connections of FABRIC interconnection cables have no requirements for FABRIC port numbers. This configuration reduces transmission reliability but cuts deployment costs.

l

–

Two UEFUs must be installed in slots 0 and 1 in a second-level USU.

–

A maximum of two second-level USUs can be deployed in a Cloud BB network.

–

When 2 to 6 first-level USUs are configured, 1 second-level USU is required. When 7 to 12 first-level USUs are configured, 2 second-level USUs are required.

–

A second-level USU can connect to a maximum of 12 first-level USUs.

–

The longest distance between first- and second-level USUs is 90 m.

Example Figure 3-8 shows the cable connections between USUs in centralized Cloud BB mode when only one second-level USU is configured (with two UEFUs). Figure 3-9 shows the

Issue 02 (2015-08-31)


12



cable connections between USUs in centralized Cloud BB mode when only one secondlevel USU is configured (with one UEFU). Figure 3-10 shows the cable connections between USUs in centralized Cloud BB mode when two second-level USUs are configured. Figure 3-8 Cable connections between USUs in centralized Cloud BB mode when only one second-level USU is configured (with two UEFUs)

Figure 3-9 Cable connections between USUs in centralized Cloud BB mode when only one second-level USU is configured (with only one UEFU)

Issue 02 (2015-08-31)


13



Figure 3-10 Cable connections between USUs in centralized Cloud BB mode when two second-level USUs are configured

Distributed Cloud BB l

Cable connections HEI interconnection cable for long-distance connection: This type of cable connects the HEI ports (which work in 1*40GE mode) on the ULPUs in first- and second-level USUs.

l


The second-level USU provides a maximum of 30 HEI ports. When each first-level USU connects to 5 HEI ports on the second-level USU, a maximum of 6 first-level USUs can connect to the second-level USU.

–

The longest distance between first- and second-level USUs is 10 km.

–

HEI ports 25 to 29 on a first-level USU connect to the HEI ports on the secondlevel USU by using five optical cables without the requirements of mapping between the port numbers.

–

A ULPU must be installed in slot 1 in the second-level USU.

–

Only one second-level USU can be deployed in a Cloud BB network. NOTE

When 2 to 6 first-level USUs are configured, 1 second-level USU is required.

l

Example Figure 3-11 shows the cable connections between USUs in distributed Cloud BB mode. Figure 3-11 Cable connections between USUs in distributed Cloud BB mode

Issue 02 (2015-08-31)


14



3.3 Key Configurations 3.3.1 Basic Data Configurations This section describes the basic configurations required for eNodeBs, first-level USUs, and second-level USUs in centralized and distributed Cloud BB modes. The configuration principles are as follows: NOTE

The MML commands listed in the section are used as examples and only key parameter settings are provided. Other parameters, such as Cabinet No., Subrack No., and Slot No., must be set based on the actual configuration.

l

l

Principles for setting the CLOUDBBID and NODEID parameters –

The CLOUDBBID parameter must be set to the same value for all the eNodeBs and USUs in a Cloud BB network.

–

The NODEID parameter must be set to a unique value for each of the USUs at the same level in a Cloud BB network.

–

In a Cloud BB network, if only one second-level USU is configured, the NODEID parameter must be set to 0 for this USU; if two second-level USUs are configured, the NODEID parameter must be set to 0 for the USU functioning as a server and set to a non-zero value for the other USU.

Principles for setting the IP addresses In a Cloud BB network, the following IP addresses are involved in basic data configurations: –

In centralized Cloud BB: IP address of the HEI port on the ULPU in the USU

–

In centralized Cloud BB: IP address of the CI port on the UMPT in the BBU

–

In distributed Cloud BB: M5/S0 port on the UCCU in the BBU

The preceding IP addresses must be set based on the following principles: –

The IP addresses must belong to the same network segment.

–

The IP addresses must be unique in the Cloud BB network.

–

The IP addresses cannot belong to the same network segment as the O&M IP addresses or interface (such as S1 and X2) IP addresses.

Data Configuration on an eNodeB l

Table 3-1 describes the data configuration on an eNodeB in centralized Cloud BB mode. Table 3-1 Data configuration on an eNodeB in centralized Cloud BB mode

Issue 02 (2015-08-31)

Configuration Operation

MML Command Example

Specify a Cloud BB ID for an eNodeB.

SET NE: CLOUDBBID=666;


15




MML Command Example

Turn on the alarm detection switch for interconnection ports.

l Turn on the alarm detection switch for the CI port on a UMPT connecting to a USU. SET CASCADEPORT: CN=0, SRN=0, SN=7, PN=8, SW=ON; In this command, set the PN parameter to 8. l Turn on the alarm detection switch for the HEI port on a BBP connecting to a USU. SET CASCADEPORT: CN=0, SRN=0, SN=3, PN=6, SW=ON; In this command, set the PN parameter to 6.

Configure a CI port and the IP address.

l Configure an Ethernet CI port. ADD ETHCIPORT:SN=7,SBT=BASE_BO ARD; In this command, set the SN parameter to the number of the slot in which the main control board is installed. l Set the IP address for an Ethernet CI port. ADD DEVIP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETHCI, PN=0, IP="192.168.2.24", MASK="255.255.255.0"; In this command, always set the SBT parameter to BASE_BOARD, the PN parameter to 0, and the PT parameter to ETHCI.

l

Table 3-2 describes the data configuration on an eNodeB in distributed Cloud BB mode. Table 3-2 Data configuration on an eNodeB in distributed Cloud BB mode Configuration Operation

MML Command Example

Specify a Cloud BB ID for an eNodeB.


Add a UCCU.

ADD BRD: CN=0, SRN=0, SN=3, BT=UCCU; In this command, set the SN parameter according to the slot where the UCCU is installed.

Issue 02 (2015-08-31)


16




MML Command Example

Configure one Ethernet port. (Connect a BBU to a USU using an optical cable that is used for both transmission and reception.)

ADD ETHPORT: CN=0, SRN=0, SN=3, SBT= ETH_COVERBOARD, PN=2, PA=FIBER, MTU=1500, SPEED=10G, DUPLEX=FULL, FC=OPEN; In this command: l Set the SBT parameter to ETH_COVERBOARD. l Set the PN parameter as follows: – When the optical module is inserted in port A on the UCCU, set this parameter to 2. – When the optical module is inserted in port B on the UCCU, set this parameter to 3. l Always set the SPEED parameter to 10G(10G).

Configure two Ethernet ports. (Connect a BBU to a USU using two optical cables that are used for both transmission and reception.)

l Configure two Ethernet ports. – ADD ETHPORT: CN=0, SRN=0, SN=3, SBT= ETH_COVERBOARD, PN=2, PA=FIBER, MTU=1500, SPEED=10G, DUPLEX=FULL, FC=OPEN; – ADD ETHPORT: CN=0, SRN=0, SN=3, SBT= ETH_COVERBOARD, PN=3, PA=FIBER, MTU=1500, SPEED=10G, DUPLEX=FULL, FC=OPEN; l Configure an Ethernet trunk. ADD ETHTRK: CN=0, SRN=0, SN=3, SBT= ETH_COVERBOARD, TN=0; l Add member ports to the Ethernet trunk. – ADD ETHTRKLNK: CN=0, SRN=0, SN=3, SBT= ETH_COVERBOARD, TN=0, PN=2, PRI=255, FLAG=YES; – ADD ETHTRKLNK: CN=0, SRN=0, SN=3, SBT= ETH_COVERBOARD, TN=0, PN=3, PRI=255, FLAG=NO; NOTE In an Ethernet trunk, the port whose FLAG is set to YES functions as the primary port. Each Ethernet trunk is configured with only one primary port.

Issue 02 (2015-08-31)


17




MML Command Example

If the UCCU is neither installed in slot 2 nor installed in slot 3, connect the UCCU and the BBP in slot 2 or 3 using a baseband interconnection cable through the panel, and turn on the alarm detection switch for the ports for connecting the UCCU and BBP.

l Turn on the alarm detection switch for the ports on the UCCU. SET CASCADEPORT: CN=0, SRN=0, SN=4, PN=0, SW=ON;

NOTE This operation is required only for BBU3900s.

In this command, set the PN parameter to a value ranging from 0 to 4. l Turn on the alarm detection switch for the ports on the BBP. SET CASCADEPORT: CN=0, SRN=0, SN=3, PN=6, SW=ON; In this command, set the PN parameter to 6.

Configure the IP address for an Ethernet port on the UCCU.

ADD DEVIP: CN=0, SRN=0, SN=3, SBT= ETH_COVERBOARD, PT=ETH, PN=2, IP="192.168.2.26", MASK="255.255.255.0"; In this command, set the SBT parameter to ETH_COVERBOARD(Ethernet Cover Board). If the ETHTRK MO is configured, the value of the PN parameter must be the same as the primary port number of the Ethernet trunk.

Data Configuration on a First-Level USU l

Table 3-3 describes the data configuration on a first-level USU in centralized Cloud BB mode. Table 3-3 Data configuration on a first-level USU in centralized Cloud BB mode Configuration Operation

MML Command Example

Specify a Cloud BB ID for a USU.


Specify the USU working mode.

SET GTRANSPARA: Level=LEVEL1, NETMODE=CENTRALIZED, NodeID=0; In this command, set the NodeID parameter to a value ranging from 0 to 11.

Specify the name of an eNodeB connecting to a USU.

Issue 02 (2015-08-31)

ADD INTERCONNE: NENAME="JINQIAO_eNODE1";


18




MML Command Example

Set the working mode of HEI ports on the ULPU to SCPRI/SRIO. (Skip this step if the HEI ports already work in SCPRI/ SRIO mode.)

Set the working mode of the port connecting a first-level USU and a BBU. (Assume that HEI ports 0 to 24 on the ULPU can be used for multi-BBU interconnection.) SET PORTMODE:CN=0,SRN=0,SN=1,STPN =0,ETPN=24,PM=SCPRI/SRIO; If first- and second-level USUs are connected in distributed mode, set the working mode of the port connecting the first-and second-level USUs. SET PORTMODE:CN=0,SRN=0,SN=1,STPN =25,ETPN=29,PM=40GE; NOTE If first- and second-level USUs are connected in centralized mode, the interconnection cable does not occupy ULPU ports. In this case, you are not required to set the working mode for the port connecting the first- and second-level USUs.

Issue 02 (2015-08-31)


19




MML Command Example


l Turn on the alarm detection switch for the CI-DL port on the UEFU. SET CASCADEPORT: CN=0, SRN=0, SN=0, PT=CI-DL, PN=0, SW=ON; In this command, set the SN parameter to 0 and the PN parameter to a value ranging from 0 to 11. l Turn on the alarm detection switch for the CI-UL port on the UEFU. SET CASCADEPORT: CN=0, SRN=0, SN=0, PT=CI-UL, PN=0, SW=ON; In this command, set the SN parameter to 0 and the PN parameter to 0 or 1. l Turn on the alarm detection switch for a FABRIC port on the UEFU. SET CASCADEPORT: CN=0, SRN=0, SN=0, PT=FABRIC, PN=0, SW=ON; In this command, set the SN parameter to 0 and the PN parameter to a value ranging from 0 to 11. l Turn on the alarm detection switch for an HEI port on the ULPU. SET CASCADEPORT: CN=0, SRN=0, SN=1, PT=HEI, PN=0, SW=ON; In this command, set the PN parameter to a value ranging from 0 to 29.

Issue 02 (2015-08-31)


20




MML Command Example

Configure the IP addresses for HEI ports on the ULPU.

l Configure the IP addresses for HEI ports working in SCPRI/SRIO mode on the ULPU in batches. ADD PORTIPPOOL: PORTIPPOOLNO=0, PORTIPBEGIN=192.100.100.1, PORTIPEND=192.100.100.30, PORTIPMASK=255.255.255.0; NOTE These IP addresses are allocated only to HEI ports working in SCPRI/SRIO mode on the ULPU by order. PORTIPBEGIN and PORTIPEND must be configured in the same network segment. The difference between PORTIPEND and PORTIPBEGIN must be less than the total number of HEI ports working in SCPRI/SRIO mode.

l Configure the IP address for a single HEI port working in SCPRI/SRIO mode on the ULPU. 1. Configure the IP address for an HEI port. ADD PORTIP: CN=0, SRN=0, SN=1, PN=0, VRFID=0, IP= 10.192.1.0, MASK=255.255.255.0; In this command, set the PN parameter to a value ranging from 0 to 29. 2. Configure a source route. ADD SRCIPRT: SRCRTIDX=1, CN=0, SRN=0, SN=1, SBT=ETH_COVERBOARD, SRCIP="1.2.3.4", RTTYPE=IF, IFT=IPPORT, IFNO=2; In this command, set the SN parameter to 1, the SBT parameter to ETH_COVERBOARD (Ethernet Cover Board), the RTTYPE parameter to IF (Exit Interface), the IFT parameter to IPPORT, and the IFNO parameter to a value ranging from 0 to 29. l

Issue 02 (2015-08-31)

Table 3-4 describes the data configuration on a first-level USU in distributed Cloud BB mode.


21



Table 3-4 Data configuration on a first-level USU in distributed Cloud BB mode Configuration Operation

MML Command Example




SET GTRANSPARA:Level=LEVEL1, NETMODE=DISTRIBUTED, NodeID=0; In this command, set the NodeID parameter to a value ranging from 0 to 11.

Specify the name of an eNodeB connecting to a USU.

ADD INTERCONNE: NENAME="JINQIAO_eNODE1";

Set the working mode of HEI ports on the ULPU.

l Set the working mode of the ports connecting first-level USUs and BBUs that are connected in distributed mode. SET PORTMODE: CN=0, SRN=0, SN=1, STPN=0, ETPN=24, PM=10GE; In this command, always set the PM parameter to 10GE(10GE). l Set the working mode of the ports connecting first- and second-level USUs that are connected in distributed mode. SET PORTMODE: CN=0, SRN=0, SN=1, STPN=25, ETPN=29, PM=40GE; In this command, set the PM parameter to 40GE. NOTE If first- and second-level USUs are connected in centralized mode, the interconnection cable does not occupy ULPU ports. In this case, you are not required to set the working mode for the port connecting the first- and second-level USUs.

Issue 02 (2015-08-31)


22




MML Command Example

Configure an Ethernet port on the ULPU.

ADD ETHPORT: CN=0, SRN=0, SN=1, SBT= ETH_COVERBOARD, PN=0, PA= FIBER, MTU=1500, SPEED=10G, DUPLEX=FULL, FC=OPEN; In this command: l Set the PN parameter to a value ranging from 0 to 119. l When the ULPU in a first-level USU connects to the BBU, set the SPEED parameter to 10G(10GE) and the PN parameter to the value calculated using the following formula: Value = Number of the HEI port x 4 + 2 or 3 NOTE Whether 2 or 3 is added to the value of PN depends on the following conditions: l If the optical module is installed in the M5/S0 port that is marked as port A on the UCCU, 2 is added to the PN value. l If the optical module is installed in the M5/S0 port that is marked as port B on the UCCU, 3 is added to the PN value.

l When the ULPU in a first-level USU connects to the ULPU in the second-level USU, set the SPEED parameter to 40G(40GE) and the PN parameter to the value calculated using the following formula: Value = Number of the HEI port x 4 Disable Ethernet ports not in use.

SET PORTSECURITY: SN=1, SBT=ETH_COVERBOARD, PT=ETH, PN=0, SWITCH=DISABLE; SN is the slot number of the ULPU, which is permanently set to 1. PN is set to HEI port number x 4 + 0/1/2/3. NOTE l HEI ports 0 and 1 must be disabled. l HEI ports 2 and 3 that do not provide cables must also be disabled.

If the Nth HEI port must be disabled, set PN to HEI port No. x 4 + N.

Issue 02 (2015-08-31)


23




MML Command Example

Set up an Ethernet trunk for five ports working in 1x40GE mode (HEI port numbers: 25 to 29; the corresponding Ethernet port numbers: 100, 104, 108, 112, and 116).

l ADD ETHTRK: CN=0, SRN=0, SN=1, SBT=ETH_COVERBOARD, TN=0; l ADD ETHTRKLNK: CN=0, SRN=0, SN=1, SBT= ETH_COVERBOARD, TN=0, PN=100, PRI=255, FLAG=YES; l ADD ETHTRKLNK: CN=0, SRN=0, SN=1, SBT= ETH_COVERBOARD, TN=0, PN=104, PRI=255, FLAG=NO; l ADD ETHTRKLNK: CN=0, SRN=0, SN=1, SBT= ETH_COVERBOARD, TN=0, PN=108, PRI=255, FLAG=NO; l ADD ETHTRKLNK: CN=0, SRN=0, SN=1, SBT= ETH_COVERBOARD, TN=0, PN=112, PRI=255, FLAG=NO; l ADD ETHTRKLNK: CN=0, SRN=0, SN=1, SBT= ETH_COVERBOARD, TN=0, PN=116, PRI=255, FLAG=NO;

Data Configuration on a Second-Level USU l

Table 3-5 describes the data configuration on a second-level USU in centralized Cloud BB mode. Table 3-5 Data configuration on a second-level USU in centralized Cloud BB mode Configuration Operation

MML Command Example




SET GTRANSPARA: Level=LEVEL2, NETMODE =CENTRALIZED, NodeID=0; In this command, set the NodeID parameter to a value ranging from 0 to 5.

Issue 02 (2015-08-31)


24




MML Command Example


l Turn on the alarm detection switch for the CI-DL port on the UEFU in the second-level USU whose NodeID is set to 0. SET CASCADEPORT: CN=0, SRN=0, SN=0, PT=CI-DL, PN=0, SW=ON; In this command, set the PN parameter to a value ranging from 0 to 11. l Turn on the alarm detection switch for the CI-UL port on the UEFU in the second-level USU whose NodeID is not set to 0 when two second-level USUs are configured. SET CASCADEPORT: CN=0, SRN=0, SN=1, PT=CI-UL, PN=0, SW=ON; In this command, set the PN parameter to 0 or 1. l Turn on the alarm detection switch for a FABRIC port on the UEFU. SET CASCADEPORT: CN=0, SRN=0, SN=1, PT=FABRIC, PN=0, SW=ON; In this command, set the PN parameter to a value ranging from 0 to 11.

Table 3-6 describes the data configuration on a first-level USU in distributed Cloud BB mode. Table 3-6 Data configuration on a second-level USU in distributed Cloud BB mode

Issue 02 (2015-08-31)


MML Command Example




SET GTRANSPARA: Level=LEVEL2, NETMODE=DISTRIBUTED, NodeID=0; In this command, set the NodeID parameter to a value ranging from 0 to 5.

Set the working mode of HEI ports on the ULPU.

SET PORTMODE: CN=0, SRN=0, SN=1, STPN=27, ETPN=28, PM=40GE;


25




MML Command Example

Configure an Ethernet port.

ADD ETHPORT: CN=0, SRN=0, SN=1, SBT= ETH_COVERBOARD, PN=0, PA= FIBER, MTU=1500, SPEED=40G, DUPLEX=FULL, FC=OPEN; In this command: l Set the PN parameter to a value that ranges from 0 to 119 and that equals to the HEI port number multiplied by 4. l Always set the SPEED parameter to 40GE(40GE).

Set up Ethernet trunks between two levels of USUs.

l Configure Ethernet trunk 1. – ADD ETHTRK: CN=0, SRN=0, SN=1, SBT= ETH_COVERBOARD, TN=0; – ADD ETHTRKLNK: CN=0, SRN=0, SN=1, SBT= ETH_COVERBOARD, TN=0, PN=0, PRI=255, FLAG=YES; – ADD ETHTRKLNK: CN=0, SRN=0, SN=1, SBT= ETH_COVERBOARD, TN=0, PN=4, PRI=255, FLAG=NO; – ADD ETHTRKLNK: CN=0, SRN=0, SN=1, SBT= ETH_COVERBOARD, TN=0, PN=8, PRI=255, FLAG=NO; – ADD ETHTRKLNK: CN=0, SRN=0, SN=1, SBT= ETH_COVERBOARD, TN=0, PN=12, PRI=255, FLAG=NO; – ADD ETHTRKLNK: CN=0, SRN=0, SN=1, SBT= ETH_COVERBOARD, TN=0, PN=16, PRI=255, FLAG=NO; In these commands, set the PN parameter to a value that equals to the HEI port number multiplied by 4. l Configure other Ethernet trunks.

3.3.2 Clock Data Configurations This section describes the optional features TDLOFD-081213 Inter-BBU Clock Sharing and LOFD-081220 Inter-BBU Clock Sharing. To meet the clock synchronization requirements of cell coordination between interconnected BBUs, one of the following clock synchronization solutions can be used:

Issue 02 (2015-08-31)


26



l

Solution 1: Each BBU is configured with a clock source for time synchronization, and the USU clock works in free-run mode.

l

Solution 2: One BBU or USU is configured with a clock source for time synchronization and shares the clock source with other interconnected BBUs or connected USUs.

For details about how to configure these features, see 6.4.3.2 Activation.

3.3.2.1 Clock Synchronization Solution 1 Solution Description This solution applies when a clock source is available for each BBU. Figure 3-12 shows clock synchronization solution 1. Figure 3-12 Clock synchronization solution 1

Clock Data Configuration Table 3-7 describes the clock data configuration on a USU and an eNodeB. Table 3-7 Clock data configuration on a USU and an eNodeB NE Type

MML Command for Clock Synchronization Configuration

Description

USU

Setting the working mode of the reference clock

The USU works in free-run mode.

SET CLKMODE: MODE=FREE; In this command, set the MODE parameter to FREE(Free).

Issue 02 (2015-08-31)


27



NE Type

MML Command for Clock Synchronization Configuration

Description

eNodeB

1. Adding a GPS or an IP clock link

Each BBU is configured with a clock source for time synchronization.

l ADD GPS: GN=0, CN=0, SRN=0, SN=7, CABLE_LEN=1000, MODE=GPS, PRI=4; l ADD IPCLKLINK: LN=0, ICPT=PTP, SN=7, CNM=L2_MULTICAST, DELAYTYPE=E2E, MACMODE=NO, PROFILETYPE=1588V2; 2. Setting the working mode of the reference clock SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0; In this command, set the CLKSRC parameter to GPS(GPS Clock) or IPCLK(IP Clock). 3. Setting the eNodeB clock synchronization mode SET CLKSYNCMODE: CLKSYNCMODE=TIME, SYSCLKSRC=LOCAL; In this command, set the CLKSYNCMODE parameter to TIME(TIME) and the SYSCLKSRC parameter to LOCAL(Local Standard Clock).

3.3.2.2 Clock Synchronization Solution 2 Solution Description This solution applies when a clock source can be shared between BBUs and USUs in a Cloud BB network. When BBUs are interconnected and one NE obtains a clock synchronization source, other NEs can share the clock synchronization source. l

Figure 3-13 shows the clock synchronization solution when a USU provides a GPS/ IPCLK clock source for time synchronization.

l

Figure 3-14 shows the clock synchronization solution when a BBU provides a GPS clock source for time synchronization.

Issue 02 (2015-08-31)


28



Figure 3-13 Clock synchronization solution when a USU provides a clock source for time synchronization

Figure 3-14 Clock synchronization solution when a BBU provides a clock source for time synchronization

NOTE

In the solution shown in Figure 3-14, after receiving clock signals from BBU0, USU1 forwards the clock signals to the second-level USU (USU0) and the other connected BBU (BBU1).

Clock Data Configuration Clock synchronization scenarios are classified based on the following aspects: l

NE type: BBU or USU

l

NE function in clock synchronization: providing a clock source for time synchronization, receiving clock signals, or forwarding clock signals

Issue 02 (2015-08-31)


29



Clock signal transmission bearer mode: –

Centralized Cloud BB

–

Distributed Cloud BB

–

Transmission from the clock source provider in centralized Cloud BB mode to a clock signal receiver in distributed Cloud BB mode

–

Transmission from the clock source provider in distributed Cloud BB mode to a clock signal receiver in centralized Cloud BB mode

Clock data configuration on an eNodeB and a USU varies with clock synchronization scenarios. NOTE

l In the IPCLKLINK MO, when the DEVTYPE parameter is set to OC_MASTER or BC, set the LN parameter to 2; when the DEVTYPE parameter is set to OC_SLAVE, set the LN parameter to 0 or 1. l Always set the CLKSYNCMODE parameter to TIME(TIME) for both eNodeBs and USUs except when the USUs works in free-run mode. l When a USU provides a clock source for time synchronization, the USU must use the GPS or IEEE 1588v2 clock as the clock source for its own synchronization. When an eNodeB provides a clock source for time synchronization, the eNodeB must use the GPS clock source for its own synchronization. Set the CLKSYNCMODE parameter to TIME(TIME) for the USU and eNodeB that provide clock sources for time synchronization.

l

Issue 02 (2015-08-31)

Table 3-8 describes the clock data configuration on an eNodeB.


30



Table 3-8 Clock data configuration on an eNodeB Sce nar io

NE Func tion

Clock Signal Trans missi on Bearer Mode

MML Command for Synchronization Object Configuration

MML Command for System Clock Mode Setting

MML Command for Clock Sharing Mode Setting

1

Provi ding a clock sourc e for time synch roniz ation

Central ized Cloud BB

1. ADD GPS: GN=0, CN=0, SRN=0, SN=7, CABLE_LEN=20, MODE=GPS, PRI=1;

SET CLKSYNC MODE: CLKSYNC MODE=TI ME, SYSCLKS RC=LOCA L;

SET CLOUDSRC: CLOUDSRC=E NABLE;


ADD IPCLKLINK: LN=2, ICPT=PTP, DEVTYPE=OC _MASTER, CNM=L2_MU LTICAST, PROFILETYPE =1588V2;

2. SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0; If two eNodeBs in a Cloud BB network provides clock sources, run the following commands to enable the eNodeB whose external clock source becomes faulty to obtain clock signals from the other eNodeB: 1. ADD GPS: GN=0, CN=0, SRN=0, SN=7, CABLE_LEN=20, MODE=GPS, PRI=1; 2. ADD INTERCLK: LN=0; In this command, always set the LN parameter to 0. 3. SET CLKMODE: MODE=AUTO;

2

Issue 02 (2015-08-31)


Distrib uted Cloud BB

1. ADD GPS: GN=0, CN=0, SRN=0, SN=7, CABLE_LEN=1000, MODE=GPS, PRI=4; 2. SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0;


31



Sce nar io

NE Func tion





3

Recei ving clock signal s


1. ADD INTERCLK: LN=0; In this command, always set the LN parameter to 0.


N/A


N/A

2. SET CLKMODE: MODE=MANUAL, CLKSRC=INTERCLK , SRCNO=0; 4

Recei ving clock signal s


1. ADD IPCLKLINK: LN=0, ICPT=PTP, SN=2, CNM=L2_MULTICAS T, DELAYTYPE=E2E, MACMODE=NO, PROFILETYPE=1588 V2; SN is set to the slot number of the UCCU. 2. SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, SRCNO=0;

l

Issue 02 (2015-08-31)

Table 3-9 describes the clock data configuration on a USU.


32



Table 3-9 Clock data configuration on a USU Sce nar io

NE Func tion





1



l GPS clock sharing

SET CLKSYNC MODE: CLKSYNC MODE=TI ME;


1. ADD GPS: GN=0, CN=0, SRN=0, SN=0, CABLE_LEN=20, MODE=GPS, PRI=4; 2. SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0; l IP clock sharing 1. ADD IPCLKLINK: LN=0, SN=0, ICPT=PTP, CNM=L2_MULTIC AST, DELAYTYPE=E2E , MACMODE=NO, PROFILETYPE=15 88V2; 2. SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, SRCNO=0;

Issue 02 (2015-08-31)


33



Sce nar io

NE Func tion





2



l GPS clock sharing



N/A

N/A

1. ADD GPS: GN=0, CN=0, SRN=0, SN=0, CABLE_LEN=20, MODE=GPS, PRI=4; 2. SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0; l IP clock sharing 1. ADD IPCLKLINK: LN=0, SN=0, ICPT=PTP, CNM=L2_MULTIC AST, DELAYTYPE=E2E , MACMODE=NO, PROFILETYPE=15 88V2; 2. SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, SRCNO=0;

3

Issue 02 (2015-08-31)

Forw ardin g clock signal s


Set the clock mode to freerun to prevent an alarm. SET CLKMODE: MODE=FREE;


34



Sce nar io

NE Func tion





4



1. ADD IPCLKLINK: LN=2, ICPT=PTP, DEVTYPE=BC, CNM=L2_MULTICAS T, PROFILETYPE=1588 V2;


N/A



2. SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, SRCNO=2; 5

Issue 02 (2015-08-31)


Trans missio n from the clock source provid er in central ized Cloud BB mode to a clock signal receive r in distrib uted Cloud BB mode

1. ADD INTERCLK: LN=0; 2. SET CLKMODE: MODE=MANUAL, CLKSRC=INTERCLK , SRCNO=0;


35



Sce nar io

NE Func tion





6


Trans missio n from the clock source provid er in distrib uted Cloud BB mode to a clock signal receive r in central ized Cloud BB mode

1. ADD IPCLKLINK: LN=2, ICPT=PTP, DEVTYPE=BC, CNM=L2_MULTICAS T, PROFILETYPE=1588 V2;



2. SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, SRCNO=2;

3.3.2.3 Clock Source Backup In a Cloud BB network, two NEs can provide clock sources for backup to ensure that clock signals are available for time synchronization when the clock source on one of the NEs is faulty. The two NEs must be of the same type, such as: l

Two eNodeBs

l

Two first-level USUs

l

Two second-level USUs in centralized Cloud BB mode

The restrictions on clock source backup in a Cloud BB network are as follows: l

When two eNodeBs provide GPS clock sources: –

For clock signal receivers: Clock signal receivers can maintain time synchronization when all NEs in the network are connected in either centralized or distributed Cloud BB mode and the clock source on one of the providers works properly.

– Issue 02 (2015-08-31)

For clock source providers: Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

36


–


The two clock source providers can implement clock source backup only when both of them connect to the first-level USUs in centralized Cloud BB mode. If one BBU fails to provide the clock source, NEs can obtain the clock source from the other BBU. As shown in Figure 3-15, BBU0 and BBU2 can serve as backups of each other. Figure 3-15 Example

NOTE

In figures in this section, the arrows indicate the transmission direction of the clock source.

l

When two first-level USUs provide clock sources: –

For clock signal receivers (BBUs connected to USUs that do not provide clock sources): A clock source can be shared by NEs in a Cloud BB network when a clock source provider works properly.

–

For clock source providers: The two clock source providers can implement clock source backup only when all first-level USUs connect to second-level USUs in centralized Cloud BB mode. Figure 3-16 Example

Issue 02 (2015-08-31)


37



That is, if the first-level USUs connect to a second-level USU in distributed Cloud BB mode, as shown in Figure 3-17, BBU2 and BBU3 cannot receive clock signals from USU0 when the clock source on USU1 is faulty. The reasons are as follows: In distributed Cloud BB mode, the clock source is transmitted in a unidirectional manner. That is, the second-level USU can only receive clock resource signals from the first-level USU that functions as a clock source provider, but cannot obtain signals from other clock source providers. Figure 3-17 Example

l

When two second-level USUs implement clock source backup, NEs in the Cloud BB network can receive signals if one clock source provider works properly, If a second-level USU that does not function as a server provides the clock source, the clock signals can be transmitted to other NEs through second-level USUs that function as servers, as shown in Figure 3-18. Figure 3-18 Non-server second-level USU providing the clock source

Issue 02 (2015-08-31)


38


4 Related Features

4

Related Features

Prerequisite Features None

Mutually Exclusive Features None

Impacted Features None

Issue 02 (2015-08-31)


39


5 Network Impact

5

Network Impact

System Capacity The multi-BBU interconnection feature has no impact on system capacity. However, the features impacted by the multi-BBU interconnection feature (as described in Service Features Supported) can increase system capacity after the multi-BBU interconnection feature is enabled. This is because the multi-BBU interconnection feature facilitates interBBU cell coordination. For details about the impact of these features on system capacity, see the relevant feature parameter descriptions.

Network Performance The multi-BBU interconnection feature has no impact on network performance. However, the features impacted by the multi-BBU interconnection feature (as described in Service Features Supported) can enhance network performance after the multi-BBU interconnection feature is enabled. This is because the multi-BBU interconnection feature facilitates interBBU cell coordination. For details about the impact of these features on network performance, see the relevant feature parameter descriptions.

Issue 02 (2015-08-31)


40


6

6 Engineering Guidelines

Engineering Guidelines

6.1 When to Use Multi-BBU Interconnection This feature applies to the following scenarios: l

Inter-BBU cell coordination is required when one of the supported service features is enabled. For details about these service features, see Service Features Supported.

l

Multiple NEs in a Cloud BB network share GPS clock sources.

6.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 USU3910 Initial Configuration Guide.

6.3 Planning Network Planning l

Multi-BBU interconnection has no impact on the existing transmission over the S1 or X2 interface or operation and maintenance (O&M) channel. The transmission plan in multiBBU interconnection scenarios is the same as that when BBUs are not interconnected. A transmission link between a BBU and USU must be added to implement inter-BBU cell coordination.

l

A USU must set up an O&M channel with the U2000 through the FE/GE0 or FE/GE1 port.

Hardware Planning For details about BBU and USU installation positions in cabinets, 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.2.1 Interconnection Between BBUs and a USU and 3.2.2 Interconnection Between BBUs and Two Levels of USUs. Issue 02 (2015-08-31)


41



6.4 Deployment 6.4.1 Process Figure 6-1 shows the process for deploying the multi-BBU interconnection feature. Figure 6-1 Process

NOTE

The data preparation in this document only involves adjusting the configurations associated with interconnection between the BBU and USU in the preceding figure. As for other steps: l For details about eNodeB and USU3910 installation, see 3900 Series Base Station Installation Guide and USU3910 Installation Guide, respectively. l For details about initial configuration of NEs, see 3900 Series Base Station Initial Configuration Guide and USU3910 Initial Configuration Guide. l For details about feature-related configurations on the BBU, see eX2 Self-Management Feature Parameter Description and the relevant feature parameter descriptions.

Issue 02 (2015-08-31)


42



6.4.2 Requirements Hardware Table 6-1 describes the configuration restrictions of boards in the BBU. Table 6-1 Board configuration restrictions Networ king

Type of the Base Station Connecting to the USU

Main Control Board/BBP

UCCU

Centrali zed Cloud BB

With one BBU

l The main control board that directly connects to the USU must be a UMPT, including UMPTa1/UMPTa2/UMPTa6 and UMPTb1/ UMPTb2.

Not require d

l The BBP that directly connects to the USU must be any of the following: – LBBPd, including LBBPd1 to LBBPd4 – UBBPd, including UBBPd1 to UBBPd6 and UBBPd9 l UMPT backup is not supported. With interconnected BBUs

l The BBUs must be connected in UCIU+UMPT mode. The UCIU can be installed only in the BBU in LTE mode.

NOTE BBU interconnection applies only to the following scenario:

l In LTE mode, one UMPT or two UMPTs working in load sharing mode can be used.

Not require d

l Root BBU (LTE) + leaf BBU (UMTS) l Root BBU (GL)+ leaf BBU (UMTS)

Issue 02 (2015-08-31)


43


Networ king


Type of the Base Station Connecting to the USU

Main Control Board/BBP

UCCU

Either of the preceding types

When the base station is connected with a USU,

Not require d

l If the base station has GL SDR RF modules, the GSM main control board cannot be the GTMU, but can be the GTMUb or GTMUc. l If the base station has UL SDR RF modules, the UMTS main control board cannot be a WMPT. l In LTE mode, one UMPT or two UMPTs working in load sharing mode can be used. l UMPT backup is not supported.

Distribu ted Cloud BB

All scenarios

When the base station is connected with a USU, l If the base station has GL SDR RF modules, the GSM main control board cannot be the GTMU, but can be the GTMUb or GTMUc.

Not require d

l If the base station has UL SDR RF modules, the UMTS main control board cannot be a WMPT. l In LTE mode, one UMPT or two UMPTs working in load sharing mode can be used. l UMPT backup is not supported.

NOTE

The GTMU is classified into the sub-type GTMU, GTMUb, and GTMUc.

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 firstlevel 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. The principles that whether a USU occupies a license are as follows: n

In centralized Cloud BB mode: A license is occupied by a first-level USU only when both the CI interconnection cable and the HEI interconnection cable are used. If only the CI interconnection cable or HEI interconnection cable is used, no license is occupied.

Issue 02 (2015-08-31)


44



For a second-level USU, a license is occupied only when both the CI interconnection cable and the FABRIC interconnection cable are used and the NodeID parameter is set to 0. Otherwise, no license is occupied. n

In distributed Cloud BB mode: For a first-level USU, a license is occupied if the HEI interconnection cable is used to connect it and a BBU. For a second-level USU, a license is occupied if the HEI interconnection cable is used to connect it and a first-level USU.

–

The license listed in the following table is required. License

BOM Code

Model

License Control Item

NE

Sales Unit

BBU Pool Intercon nection Port License

88032BU L

LT1S0BBUIP0 0

BBU Pool Interconnection Port License (per BBU/ USU)

US U

per NE

l

To enable inter-BBU cell coordination, operators need to purchase the licenses required for relevant features. For details about these features, see Service Features Supported.

l

If clock sharing is required in a CloudBB network, operators must purchase the licenses listed in the following tables and activate them on the eNodeBs that need to receive signals from the clock source. –

–

–

Issue 02 (2015-08-31)

LTE FDD eNodeBs in centralized Cloud BB mode Featur e ID

Feature Name

Model


NE

Sales Unit

LOFD081220

InterBBU Clock Sharing

LT1S0ICLKS0 0

Inter-BBU Clock Sharing(FD D)

eNodeB

per eNode B

LTE TDD eNodeBs in centralized Cloud BB mode Featur e ID

Feature Name

License Control Item ID


NE

Sales Unit

TDLO FD-081 213

InterBBU Clock Sharing

LT1STIBCS00 0

Inter-BBU Clock Sharing(TD D)

eNodeB

per eNode B

LTE FDD eNodeBs in distributed Cloud BB mode


45


–


Featur e ID

Feature Name



NE

Sales Unit

LOFD003013 02

IEEE158 8 V2 Clock Synchro nization

LT1S00ENSY0 0

Enhanced Synchronizati on (FDD)

eNodeB

per eNode B

LTE TDD eNodeBs in distributed Cloud BB mode Featur e ID

Feature Name



NE

Sales Unit

TDLO FD-003 01302

IEEE158 8 V2 clock synchron ization

LT1ST0ESYN 00

Enhanced Synchronizati on (TDD)

eNodeB

per eNode B

Other Requirements l

USUs must be installed to interconnect BBUs.

l

The eNodeB and USU software versions must be compatible with those used in the current version.

6.4.3 Data Preparation and Feature Activation 6.4.3.1 Data Preparation Data to be prepared is classified into two types: l

Common configuration data for eNodeBs and USUs –

–

Issue 02 (2015-08-31)

The following table describes the parameter that must be set in the NE MO to specify a Cloud BB ID. Parameter Name

Parameter ID

Setting Notes

Data Source

Cloud BB Identifier

NE.CloudBBID

Set this parameter as planned.

Network plan (negotiation not required)

The following table describes the parameters that must be set in the ETHCIPORT MO to configure CI ports.


46


–


Parameter Name

Parameter ID

Setting Notes

Data Source

Subboard Type

ETHCIPORT.S BT

Set this parameter to BASE_BOARD( Base Board).


Port No.

ETHCIPORT.P N

Set this parameter to 0.


The following table describes the parameters that must be set in the ETHPORT MO to configure Ethernet ports. Parameter Name

Parameter ID

Setting Notes

Data Source

Subboard Type

ETHPORT.SBT

Set this parameter to ETH_COVERB OARD(Ethernet Cover Board).


Port No.

ETHPORT.PN

l For a BBU, set this parameter to 2 or 3 as required.


l For a USU, set this parameter to a value ranging from 0 to 119.

–

Issue 02 (2015-08-31)

The following table describes the parameters that must be set in the ETHTRK MO to configure Ethernet trunks. Parameter Name

Parameter ID

Setting Notes

Data Source

Subboard Type

ETHTRK.SBT

Set this parameter to ETH_COVERB OARD(Ethernet Cover Board).


Trunk No.

ETHTRK.TN

Set this parameter to a unique value for an Ethernet trunk in a Cloud BB network.



47


–


The following table describes the parameters that must be set in the ETHTRKLNK MO to configure the ports in Ethernet trunks. Parameter Name

Parameter ID

Setting Notes

Data Source

Port No.

ETHTRKLNK.P N

l For a BBU, set this parameter to 2 or 3 as required.


l For a USU, set this parameter to a value ranging from 0 to 119. Master Flag

–

ETHTRKLNK.F LAG

Set this parameter to YES(Yes) for the primary port and NO(No) for other ports.


The following table describes the parameters that must be set in the DEVIP MO to configure device IP addresses. Parameter Name

Parameter ID

Setting Notes

Data Source

Subboard Type

DEVIP.SBT

l For the UMPT in a BBU or a UEFU in a USU, set this parameter to BASE_BOAR D(Base Board).


l For other boards, set this parameter to ETH_COVE RBOARD(Et hernet Cover Board).

Issue 02 (2015-08-31)


48



Parameter Name

Parameter ID

Setting Notes

Data Source

Port Type

DEVIP.PT

l For the UMPT in a BBU, set this parameter to ETHCI(Ether net CI Port).


l For the UCCU in a BBU, set this parameter to ETH(Etherne t Port) or ETHTRK(Et hernet Trunk). Port No.

DEVIP.PN

l For the UMPT in a BBU, set this parameter to 0.


l For the UCCU in a BBU, set this parameter to 2 or 3. IP Address

–

DEVIP.IP

Set this parameter as required.


The following table describes the parameters that must be set in the CASCADEPORT MO to configure interconnection ports. Parameter Name

Parameter ID

Setting Notes

Data Source

Port No.

CASCADEPOR T.PN

l For the UMPT in a BBU, set this parameter to 8.


l For the LBBPd or UBBPd, set this parameter to 6. l For a USU, set this parameter as required.

Issue 02 (2015-08-31)


49


–


Parameter Name

Parameter ID

Setting Notes

Data Source

Switch

CASCADEPOR T.SW

Set this parameter to ON(On).


The following table describes the parameters that must be set in the IPCLKLINK MO to configure IP clock links. Paramet er Name

Parameter ID

Setting Notes

Data Source

Link No.

IPCLKLNK.L N(N/A,LTE FDD eNodeB)

l For an eNodeB:


– When the DEVTYPE parameter is set to OC_SLAVE, set the LN parameter to 0 or 1. – When the DEVTYPE parameter is set to OC_MASTER, set the LN parameter to 2. l For a USU: – When the DEVTYPE parameter is set to OC_MASTER or BC, set the LN parameter to 2. – When the DEVTYPE parameter is set to OC_SLAVE, set the LN parameter to 0 or 1.

Issue 02 (2015-08-31)


50



Paramet er Name

Parameter ID

Setting Notes

Data Source

Device Type

IPCLKLNK.DE VTYPE(N/ A,LTE FDD eNodeB)

l For an eNodeB:


– When the eNodeB provides a clock source for time synchronization, set this parameter to OC_MASTER. – When the eNodeB receives clock signals, set this parameter to OC_SLAVE. l For a USU: – When the USU provides a clock source for time synchronization, set this parameter to OC_MASTER. – When the USU forwards clock signals, set this parameter to BC.

–

Issue 02 (2015-08-31)

Clock Net Mode

IPCLKLNK.CN M(N/A,LTE FDD eNodeB)

Set this parameter to L2_MULTICAST.


Profile Type

IPCLKLNK.PR OFILETYPE(N/ A,LTE FDD eNodeB)

Set this parameter to 1588V2.


The following table describes the parameters that must be set in the TASM MO to configure the system clock. Parameter Name

Parameter ID

Setting Notes

Data Source

Clock Working Mode

TASM.MO DE

Set this parameter to MANUAL.

Network plan (negotiati on not required)


51



Parameter Name

Parameter ID

Setting Notes

Data Source

Cloud BB Clock Reference Source Flag

TASM.CL OUDSRC

l For an eNodeB:


– When the eNodeB provides a clock source for time synchronization, set this parameter to ENABLE(ENABLE). – When the eNodeB receives clock signals, set this parameter to DISABLE(DISABLE). l For a USU: – When the USU provides a clock source for time synchronization, set this parameter to ENABLE(ENABLE). – When the USU forwards clock signals, set this parameter to DISABLE(DISABLE).

Selected Clock Source

TASM.CL KSRC

l For an eNodeB: – When the eNodeB provides a clock source for time synchronization, set this parameter to GPS(GPS Clock) or IPCLK(IP Clock).


– When the eNodeB receives clock signals, set this parameter to INTERCLK(Inter Clock). l For a USU: – When the USU provides a clock source for time synchronization, set this parameter to GPS(GPS Clock) or IPCLK(IP Clock). – When the USU forwards clock signals, this parameter is not required.

Issue 02 (2015-08-31)


52



Parameter Name

Parameter ID

Setting Notes

Data Source

Clock Synchronizati on Mode

TASM.CL KSYNCM ODE

l For an eNodeB, set this parameter to TIME(TIME).


l For a USU: – When the USU forwards clock signals, this parameter is not required. – When the USU provides a clock source for time synchronization, set this parameter to TIME(TIME).

–

The following table describes the parameters that must be set in the INTERCLK MO to configure the shared clock source. Parameter Name

Paramete r ID

Setting Notes

Data Source

Interconnectio n Clock No.

InterClk. LN

Set this parameter to 0.


Priority

InterClk. PRI

l Set this parameter to the priority of the clock source on an eNodeB receiving clock signals. The value ranges from 1 to 4. The default value is 4, which indicates the lowest priority.


l If the TASM.MODE parameter is set to AUTO(Auto), the eNodeB selects the clock source with the highest priority.

l

Configuration data dedicated to USUs –

Issue 02 (2015-08-31)

The following table describes the parameter that must be set in the INTERCONNE MO to specify NE names. Parameter Name

Parameter ID

Setting Notes

Data Source

Network Element Name

INTERCONNE. NENAME

Set this parameter to the name of an eNodeB connecting to a USU.

Network plan (negotiatio n not required)


53


–


The following table describes the parameters that must be set in the GTRANSPARA MO to configure global transmission parameters. Parameter Name

Parameter ID

Setting Notes

Data Source

Level

GTRANSPARA. LEVEL

Set this parameter to LEVEL1(LEVEL1) or LEVEL2(LEVEL2) as required.


Network Mode

GTRANSPARA. NETMODE

Set this parameter to CENTRALIZED(CEN TRALIZED), DISTRIBUTED(DIST RIBUTED), or HYBRID(HYBRID) as required.


Node ID

GTRANSPARA. NODEID

Set this parameter only when the first- and second-level USUs are connected in centralized Cloud BB mode. Otherwise, do not set this parameter.


For a first-level USU, set this parameter to a value ranging from 0 to 11. For a second-level USU, set this parameter to a value ranging from 0 to 5.

–

Issue 02 (2015-08-31)

The following table describes the parameters that must be set in the PORTIP MO to configure port IP addresses. Parameter Name

Parameter ID

Setting Notes

Data Source

IP Address

PORTIP.IP

Set this parameter for an HEI port working in SCPRI/SRIO mode on the ULPU in a USU as required.


Mask

PORTIP.MASK

Set this parameter as required.



54


–


The following table describes the parameter that must be set in the PORTMODE MO to specify the working mode for ports. Parameter Name

Parameter ID

Setting Notes

Data Source

Port Mode

PORTMODE.P M

l In centralized Cloud BB mode, set this parameter to SCPRI/ SRIO(SCPRI/ SRIO).


l In distributed Cloud BB mode: – For an HEI port connecting to an eNodeB, set this parameter to 4*10GE(4*10GE ). – For an HEI port connecting to the second-level USU, set this parameter to 1*40GE(1*40GE ).

6.4.3.2 Activation Using the CME to Perform Batch Configuration Enter the values of the parameters listed in Table 6-2 and Table 6-3 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 USU3910 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: l

The MOs in Table 6-2 and Table 6-3 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 6-2 and Table 6-3 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.

Issue 02 (2015-08-31)


55



Table 6-2 Multi-BBU interconnection parameters on eNodeBs

Issue 02 (2015-08-31)

MO

Sheet in the Summary Data File

Parameter Group

Remarks

NE

User-defined sheet

Cloud BB Identifier

This parameter must be customized in the template.

CASCADEPO RT

User-defined sheet

Port No., Switch

These parameters must be customized in the template.

DEVIP

User-defined sheet

Subboard Type, Port Type, Port No., IP Address


ETHCIPORT

User-defined sheet

Port No., Subboard Type


IPCLKLINK

User-defined sheet

Link No., Device Type, Clock Net Mode, Profile Type


INTERCLK

User-defined sheet

Interconnection Clock No., Priority


TASM

User-defined sheet

Clock Working Mode, Selected Clock Source, Cloud BB Clock Reference Source Flag, Clock Synchronization Mode



56



Table 6-3 Multi-BBU interconnection parameters on USUs

Issue 02 (2015-08-31)

MO


Parameter Group

Remarks

NE

User-defined sheet

Cloud BB Identifier


CASCADEPO RT

User-defined sheet

Port No., Switch


DEVIP

User-defined sheet

Subboard Type, Port Type, Port No., IP Address


ETHCIPORT

User-defined sheet

Port No., Subboard Type


IPCLKLINK

User-defined sheet

Link No., Device Type, Clock Net Mode, Profile Type


INTERCLK

User-defined sheet

Interconnection Clock No., Priority


TASM

User-defined sheet

Clock Working Mode, Selected Clock Source, Cloud BB Clock Reference Source Flag, Clock Synchronization Mode



57



MO


Parameter Group

Remarks

GTRANSPARA

User-defined sheet

Level, Network Mode, Node ID


PORTIP

User-defined sheet

IP Address, Mask


PORTMODE

User-defined sheet

Port Mode


INTERCONNE

User-defined sheet

Network Element Name


Using MML Commands Step 1 Configure the Could BB ID, NE working mode, and port working mode. For details, see 3.3.1 Basic Data Configurations. Step 2 Run the SET CASCADEPORT command on each BBU and USU to configure the ports required for interconnection. NOTE

Alarms generated on an interconnection port can be reported only after the alarm detection switch is turned on. Turn on the switch for an interconnection port only when you need to use this interconnection port. 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 3 Configure the clock source. NOTE

In the LTE system, inter-BBU cell coordination requires phase synchronization between eNodeBs (that is, each eNodeB can obtain clock signals).

l

Clock synchronization solution 1 a.

Issue 02 (2015-08-31)

On each USU, run the SET CLKMODE command with Clock Working Mode set to FREE(Free). Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

58


l


b.

On each eNodeB, run the ADD GPS or ADD IPCLKLINK command to add a GPS clock link or IP clock link.

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

Clock synchronization solution 2 a.

Determine the USU configuration scenario according to 3.3.2.2 Clock Synchronization Solution 2 and configure the USUs based on the key configuration data.

b.

Determine the BBU configuration scenario according to 3.3.2.2 Clock Synchronization Solution 2 and configure the BBUs based on the key configuration data.

----End

6.4.4 MML Command Examples This section provides the examples of MML commands related to transmission and clock synchronization between USU0, USU1, and BBU0 circled by dashed lines in Figure 6-2. Figure 6-2 Clock synchronization solution when a USU provides a clock source for time synchronization

Issue 02 (2015-08-31)


59



NOTE

l The parameter settings in the following commands are used for reference only. Set the parameters based on network requirements. l In these examples, the BBU and USUs are connected in centralized Cloud BB mode. l For the MML command examples related to USU initial configuration, see the following section in USU3910 Initial Configuration Guide: Initially Configuring a USU (Using the MML Commands) > Typical Configuration Example

1.

To configure USU0 basic data, run the related MML commands listed in Table 3-5.

2.

To configure USU1 basic data, run the related MML commands listed in Table 3-3.

3.

To configure BBU0 basic data, run the related MML commands listed in Table 3-1.

4.

To configure USU0 clock synchronization data, run the related MML commands for scenario 1 listed in Table 3-9.

5.

To configure USU1 clock synchronization data, run the related MML commands for scenario 3 listed in Table 3-9.

6.

To configure BBU0 clock synchronization data, run the related MML commands for scenario 3 listed in Table 3-8.

6.4.5 Activation Observation Local Observation Table 6-4 describes the method for local observation. Table 6-4 Local observation NE

Board

Port

Expected Result

USU

UEFU

CI-DL port

Steady green, indicating that the connection between a USU and a lowerlevel NE is normal.

FABRIC port

Steady green, indicating that the userplane connection between a first-level USU and a second-level USU is normal.

CI-UL port

Steady green, indicating that the controlplane connection between a first-level USU and a second-level USU is normal.

ULPU

HEI port

Steady green, indicating that the connection between a USU and a peer NE is normal.

UMPT

CI port

Steady green, indicating that the controlplane (over the CI-DL port) connection between a BBU and USU is normal.

BBP

HEI port

Steady green, indicating that the userplane (through the QSFP cable on the ULPU) connection between a BBU and USU is normal.

eNodeB

Issue 02 (2015-08-31)


60


NE


Board

Port

Expected Result

UCCU

M5/S0 port

Steady green, indicating that the Ethernet link between a BBU and an HEI port on a USU is normal.

Remote Observation l

Run the following MML commands to check whether the USU and eNodeBs are working properly. NE

MML Command

Expected Result

USU

DSP INTERCONTOPO

The command output is the same as planned.

DSP CLKSTAT

l When the USU provides a clock source or forwards clock signals for time synchronization, the values of PLL Status and Clock Synchronization Mode in the command output are Locked and TIME, respectively. l When the USU forwards clock signals or the USU clock works in free-run mode, the value of PLL Status in the command output is Free running.

eNodeB

Issue 02 (2015-08-31)

DSP CTRLLNKSTAT

Both the packet loss rate and packet error rate on the link are lower than the specified thresholds (10-3).

DSP BBPLNKSTAT

Both the packet loss rate and link interruption rate are lower than the specified thresholds (10-3).

DSP CXP

The value of Port Receive Status in the command output is Up.

DSP PORTIP

The value of IP Address in the command output is not null.

DSP ETHPORT

In the command output, if the values of both Port Status and Physical Layer Status are Up and the value of Local Speed is 10G or 40G.

DSP INTERCONTOPO

The topology between the BBU and USU is the same as planned.

DSP CLKSTAT

In the command output, the value of PLL Status is Locked and the value of Clock Synchronization Mode is TIME.


61


NE


MML Command

Expected Result

DSP ETHCIPORT

The value of Port Status in the command output is Up.

DSP BBPLNK

The value of SRIO Line Bit Rate(Gbit/s) in the command output is 6.25.

DSP CTRLLNKSTAT

The values of 1 Hour LOS Rate (per mill) and 1 Hour Packet Error Rate (per mill) in the command output are 0 or 1.

NOTE In this command, set the CTRLLNK.PT parameter to 8.

DSP ETHPORT

In the command output, if the values of both Port Status and Physical Layer Status are Up and the value of Local Speed is 10G or 40G.

6.4.6 Reconfiguration Network reconfiguration includes the following procedures: l

Adding BBUs

l

Removing BBUs

l

Adjusting BBUs NOTE

BBUs are adjusted in the following scenarios: l

BBUs are disconnected from a first-level USU and connect to another first-level USU in the same Cloud BB network.

l

BBUs are disconnected from a first-level USU in a Cloud BB network and connect to a firstlevel USU in another Cloud BB network.

BBU adjustment can be implemented by adding and removing BBUs and therefore is not described in this section.

l

Adding BBUs and USUs

6.4.6.1 Reconfiguration for the Centralized Cloud BB Mode 6.4.6.1.1 Adding BBUs This section describes the reconfiguration procedure when the number of BBUs increases from 2 to 4 and only one USU is configured. Figure 6-3 shows the hardware configurations after two BBUs are added. For details about the original hardware configurations, see Figure 3-3.

Issue 02 (2015-08-31)


62



Figure 6-3 Hardware configurations after two BBUs are added

The reconfiguration procedure is as follows: Step 1 Prepare devices and cables. Before adjusting configuration data, obtain the devices and cables listed in the following table.

Issue 02 (2015-08-31)

Device or Cable

Quantity

BBU subrack

2

UMPT

2

BBP (LBBPd or UBBPd)

12

CI interconnection cable

2 small form-factor pluggable (SFP) cables (each 3 m long)

HEI interconnection cable for short-distance connection

12 quad small form-factor pluggable (QSFP) active cables (each 2.5 m long)


63



Device or Cable

Quantity

Other cables, including common public radio interface (CPRI) cables, transmission cables, clock cables, power cables, and monitoring cables

Based on the site plan

Step 2 Install the devices and cables. 1.

Install UMPTs and BBPs in BBU2 and BBU3, and connect cables, including CPRI cables, transmission cables, clock cables, power cables, and monitoring cables.

2.

Use CI interconnection cables to connect the CI ports on the UMPTs to the CI-DL ports on the UEFU.

3.

Use HEI interconnection cables to connect the HEI ports on the BBPs to the HEI ports on the ULPU.

Step 3 Adjust configuration data. 1.

Configure BBU2 and BBU3 according to 3900 Series Base Station Initial Configuration Guide.

2.

Run the SET NE command with the Cloud BB Identifier parameter specified to configure Cloud BB IDs for BBU2 and BBU3.

3.

Run the ADD ETHCIPORT command to configure the CI ports on the UMPTs in BBU2 and BBU3.

4.

Run the ADD DEVIP command to configure the IP addresses for the CI ports on these UMPTs.

5.

Run the SET PORTMODE command to set the working mode of the HEI ports on the ULPU to SCPRI/SRIO. NOTE

Skip this step if the HEI ports already work in SCPRI/SRIO mode. To query the working mode of an HEI port, run the LST PORTMODE command.

6.

Configure the IP addresses for the HEI ports on the ULPU in batches or one by one according to Table 3-3.

7.

Run the SET CASCADEPORT command on BBU2, BBU3, and the USU to configure the ports required for interconnection: a.

On BBU2 and BBU3, turn on the alarm detection switch for the CI ports on the UMPTs and the HEI ports on the BBPs. For details about parameter settings in the command, see Table 3-1.

b.

On the USU, turn on the alarm detection switch for the CI-DL ports on the UEFU and the HEI ports on the ULPU. For details about parameter settings in the command, see Table 3-3. NOTE

Alarms generated on an interconnection port can be reported only after the alarm detection switch is turned on. Turn on the switch for an interconnection port only when you need to use this interconnection port.

8.

On the USU, run the ADD INTERCONNE command with the INTERCONNE.NENAME parameter specified to add names for BBU2 and BBU3.

----End Issue 02 (2015-08-31)


64



6.4.6.1.2 Removing BBUs In a Cloud BB network, remove a BBU as follows: 1.

On the BBU, run the SET CASCADEPORT command with the Switch parameter set to OFF(Off) to turn off the alarm detection switch for the CI ports on the UMPTs and the HEI ports on the BBPs.

2.

Remove the CI interconnection cable and HEI interconnection cables (for short-distance connection) between the BBU and USU.

3.

On the BBU, run the SET NE command with the Cloud BB Identifier set to 0.

4.

On the USU connecting to this BBU, run the RMV INTERCONNE command to remove the BBU information. NOTE

To adjust the BBU, perform the following additional operations: l Retain the parameter settings in the ETHCIPORT MOs for the CI ports. Based on the network plan, determine whether to modify the device IP addresses for the CI ports (DEVIP MOs). l If the BBU performs the NE function (providing a clock source for time synchronization or receiving clock signals) different from that before the BBU adjustment, modify the clock configuration of the BBU accordingly. Otherwise, retain the clock configuration.

6.4.6.1.3 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 6-4 shows the hardware configurations after three BBUs and two USUs are added. Figure 6-4 Hardware configurations after three BBUs and two USUs are added

Issue 02 (2015-08-31)


65



The reconfiguration procedure is as follows: Step 1 Prepare devices and cables. Before adjusting configuration data, obtain the devices and cables listed in the following table. Device or Cable

Quantity

Remarks

BBU subrack

3

N/A

USU subrack

2

N/A

UMPT

3

N/A


18

Each BBU can house one to six BBPs.

UEFU

3

N/A

ULPU

1

N/A

CI interconnection cable

5 SFP cables (each 3 m long)

Each BBU and first-level USU are configured with an SFP cable.

HEI interconnection cable for short-distance connection

18 QSFP active cables in cabinets (each 2.5 m long)

Each BBP is configured with a QSFP active cable.

FABRIC interconnection cable

8 CXP multimode active optical cables (AOCs) (each 10 m long)

Each first-level USU is configured with four CXP multimode active optical cables.

Other cables, including CPRI cables, transmission cables, clock cables, power cables, and monitoring cables


N/A


Install UMPTs and BBPs in new BBUs, and connect cables, including CPRI cables, transmission cables, clock cables, power cables, and monitoring cables.

2.

Install UEFUs in new USUs and a ULPU in the new first-level USU, and connect cables, including transmission cables, power cables, and monitoring cables.

3.

Use CI interconnection cables to connect the CI ports on the UMPTs in new BBUs and the CI-DL ports on the UEFU in the new first-level USU.

4.

Use HEI interconnection cables to connect the HEI ports on the BBPs in new BBUs to the HEI ports on the ULPU in the new first-level USU.

5.

Connect the new first-level USU and the second-level USU: –

Issue 02 (2015-08-31)

Use CI interconnection cables to connect the CI-UL port on the UEFU in the new first-level USU and the CI-DL port on the UEFU in the second-level USU. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

66


–


Use FABRIC interconnection cables to connect the FABRIC ports on the UEFU in the new first-level USU and the FABRIC ports on the UEFUs in the second-level USU.


Configure new BBUs according to 3900 Series Base Station Initial Configuration Guide. Configure new USUs according to the "Initially Configuring a USU (Using the MML Commands)" section in USU3910 Initial Configuration Guide.

2.

Configure device- and transmission-related data of new BBUs and USUs according to 3.3.1 Basic Data Configurations.

3.

Configure clock synchronization-related data of new BBUs and USUs according to 3.3.2 Clock Data Configurations.

----End

6.4.6.2 Reconfiguration for Distributed Cloud BB Mode 6.4.6.2.1 Adding BBUs This section describes the reconfiguration procedure when the number of BBUs increases from 2 to 4 and only one USU is configured. Figure 6-5 shows the hardware configurations after two BBUs are added. For details about the original hardware configurations, see Figure 3-5.

Issue 02 (2015-08-31)


67



Figure 6-5 Hardware configurations after two BBUs are added


Issue 02 (2015-08-31)

Device or Cable

Quantity

Remarks

BBU subrack

2

N/A

UMPT

2

N/A


10

Each BBU can house one to five BBPs as required.

UCCU

2

Each BBU houses one UCCU.

HEI interconnection cable for longdistance connection

2

Each BBU can be configured with one or two HEI interconnection cables as required.

Optical module

4

N/A


68



Device or Cable

Quantity

Remarks

Other cables, including CPRI cables, transmission cables, clock cables, power cables, and monitoring cables


N/A


Install UMPTs and BBPs in BBU2 and BBU3, and connect cables, including CPRI cables, transmission cables, clock cables, power cables, and monitoring cables.

2.

Install UCCUs in BBU2 and BBU3.

3.

Use HEI interconnection cables to connect the M5/S0 ports on the UCCU to the HEI ports on the ULPU.


Configure BBU2 and BBU3 according to 3900 Series Base Station Initial Configuration Guide.

2.

Run the SET NE command with the Cloud BB Identifier parameter specified to configure Cloud BB IDs for BBU2 and BBU3.

3.

Run the ADD ETHCIPORT command to configure the M5/S0 ports on the UCCUs in BBU2 and BBU3.

4.

Run the ADD DEVIP command to configure the IP addresses for the M5/S0 ports on these UCCUs.

5.

Run the SET PORTMODE command to set the working mode of the HEI ports on the ULPU to SCPRI/SRIO.

Step 4 On the USU, run the ADD INTERCONNE command with the INTERCONNE.NENAME parameter specified to add names for BBU2 and BBU3. ----End

6.4.6.2.2 Removing BBUs In a Cloud BB network, remove a BBU as follows: 1.

Remove the HEI interconnection cables (for long-distance connection) between the BBU and USU.

2.

On the BBU, run the SET NE command with the Cloud BB Identifier set to 0.

3.

On the USU connecting to this BBU, run the RMV INTERCONNE command to remove the BBU information. NOTE

To adjust the BBU, perform the following additional operations: l Retain the parameter settings in the ETHPORT MOs for the Ethernet ports added to the UCCU. Based on the network plan, determine whether to modify the device IP addresses for the Ethernet ports (DEVIP MOs). l If the BBU performs the NE function (providing a clock source for time synchronization or receiving clock signals) different from that before the BBU adjustment, modify the clock configuration of the BBU accordingly. Otherwise, retain the clock configuration.

Issue 02 (2015-08-31)


69



6.4.6.2.3 Adding BBUs and USUs This section describes the reconfiguration procedure when the number of BBUs increases from 25 to 28, the number of USUs increases from 1 to 3, and each BBU are connected to two optical cables. Figure 6-6 shows the hardware configurations after three BBUs and two USUs are added. Figure 6-6 Hardware configurations after two BBUs are added


Issue 02 (2015-08-31)

Device or Cable

Quantity

Remarks

BBU subrack

3

N/A

USU subrack

2

N/A

UMPT

3

N/A


15

Each BBU can house one to five BBPs as required.

UEFU

2

N/A

ULPU

2

N/A


70



Device or Cable

Quantity

Remarks

HEI interconnection cable for longdistance connection (4*10GE) and optical modules

l HEI interconnection cable: 3

Each UCCU can be configured with one or two HEI interconnection cables as required.

l Optical module: 6 HEI interconnection cable for longdistance connection (1*40GE) and optical modules

l HEI interconnection cable: 10

N/A

l Optical module: 20 Other cables, including common public radio interface (CPRI) cables, transmission cables, clock cables, power cables, and monitoring cables


N/A


Install UMPTs and BBPs in new BBUs, and connect cables, including CPRI cables, transmission cables, clock cables, power cables, and monitoring cables.

2.

Install UEFUs and ULPUs in new USUs, and connect cables, including transmission cables, power cables, and monitoring cables.

3.

Install UCCUs in new BBUs.

4.

Install HEI interconnection cables for long-distance connection as follows: –

Use HEI interconnection cables (4*10GE) to connect the M5/S0 ports on the UCCUs in new BBUs to the HEI ports on the ULPU in the new first-level USU.

–

Use HEI interconnection cables (1*40GE) to connect the HEI ports on the ULPUs in the new first-level and second-level USUs.


Configure new BBUs according to 3900 Series Base Station Initial Configuration Guide.

2.

Configure new USUs according to the "Initially Configuring a USU (Using the MML Commands)" section in USU3910 Initial Configuration Guide.

3.

Configure device- and transmission-related data of new BBUs and USUs according to 3.3.1 Basic Data Configurations.

4.

Configure clock synchronization-related data of new BBUs and USUs according to 3.3.2 Clock Data Configurations.

----End

6.5 Performance Monitoring For details, see the performance monitoring chapter in the parameter description documents for features supported by multi-BBU interconnection.

Issue 02 (2015-08-31)


71



6.6 Parameter Optimization N/A

6.7 Troubleshooting Alarms related to multi-BBU interconnection are reported due to the following reasons: 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.

l

Cables are incorrectly connected between a BBU and a USU.

If any of alarms listed in Table 6-5 or Table 6-6 is generated, clear the alarm by referring to 3900 Series Base Station Alarm Reference or USU3910 Alarm Reference, respectively. Table 6-5 BBU alarms related to multi-BBU interconnection Alarm ID

Alarm Name

Alarm Level

Alarm Type

26116

Inter-NE Address Conflict

Major

Fault

26310

Inter-BBU Optical Module Fault

Warning

Fault

26311

Inter-BBU Optical Module Not in Position

Major

Fault

26312

Inter-BBU Optical Module Receive Failure

Major/Minor

Fault

26313

Inter-BBU Optical Module Transmit Failure

Major/Minor

Fault

26314

Inter-BBU Port Failure

Major

Fault

26315

Inter-BBU Port Connection Error

Major

Fault

Table 6-6 USU alarms related to multi-BBU interconnection

Issue 02 (2015-08-31)

Alarm ID

Alarm Name

Alarm Level

Alarm Type

26247

Configuration Failure

Major/Minor

Fault

27105

Interconnected Optical Module Fault

Warning

Fault

27106

Interconnected Optical Module Not Installed

Major

Fault

27107

Interconnected Optical Module Receive Failure

Major/Minor

Fault


72



Alarm ID

Alarm Name

Alarm Level

Alarm Type

27108

Interconnected Optical Module Transmit Failure

Major/Minor

Fault

27109

Inter-Port Failure

Major

Fault

27110

Inter-BBU Port Connection Error

Major

Fault

To locate the connectivity and performance faults in the Ethernet links between BBUs and first-level USUs and between two levels of USUs, perform link connectivity tests and link performance monitoring based on the ITU-T Y.1731 protocol. For details, see Ethernet OAM Feature Parameter Description.

Issue 02 (2015-08-31)


73


7 Parameters

7

Parameters

Table 7-1 Parameters MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

NE

CLOUD BBID

SET NE

None

None

Meaning: Indicates the Cloud BB identifier that specifies the Cloud BB to which the NE belongs. When multiple NEs are deployed under the same Cloud BB, these NEs have the same Cloud BB identifier.

LST NE

GUI Value Range: 0~65535 Unit: None Actual Value Range: 0~65535 Default Value: 0 ETHCIP ORT

SBT

ADD ETHCIP ORT

None

None

Meaning: Indicates the subboard type of the board where the Ethernet CI port is located. GUI Value Range: BASE_BOARD(Base Board)

MOD ETHCIP ORT

Unit: None

RMV ETHCIP ORT

Default Value: None

Actual Value Range: BASE_BOARD

LST ETHCIP ORT

Issue 02 (2015-08-31)


74


7 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

ETHCIP ORT

PN

ADD ETHCIP ORT

None

None

Meaning: Indicates the number of the Ethernet CI port. GUI Value Range: 0

MOD ETHCIP ORT

Unit: None

RMV ETHCIP ORT

Default Value: None

Actual Value Range: 0

LST ETHCIP ORT ETHPO RT

SBT

ADD ETHPO RT DSP ETHPO RT RMV ETHPO RT

None

None

Meaning: Indicates the type of sub-board on the board where the Ethernet port is located. GUI Value Range: BASE_BOARD(Base Board), ETH_COVERBOARD(Ethernet Cover Board) Unit: None Actual Value Range: BASE_BOARD, ETH_COVERBOARD Default Value: None

RST ETHPO RT SET ETHPO RT LST ETHPO RT

Issue 02 (2015-08-31)


75


7 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

ETHPO RT

PN

ADD ETHPO RT

None

None

Meaning: Indicates the number of the Ethernet port. GUI Value Range: 0~5 Unit: None

DSP ETHPO RT

Actual Value Range: 0~5 Default Value: None

RMV ETHPO RT RST ETHPO RT SET ETHPO RT LST ETHPO RT ETHTR K

SBT

ADD ETHTR K DSP ETHTR K MOD ETHTR K

None

None

Meaning: Indicates the type of subboard on the board where the Ethernet trunk is established. GUI Value Range: BASE_BOARD(Base Board), ETH_COVERBOARD(Ethernet Cover Board) Unit: None Actual Value Range: BASE_BOARD, ETH_COVERBOARD Default Value: None

RMV ETHTR K RST ETHTR K LST ETHTR K

Issue 02 (2015-08-31)


76


7 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

ETHTR K

TN

ADD ETHTR K

MRFD210103

Link aggregat ion

Meaning: Indicates the number of the Ethernet trunk.When the board is a UTRPc board, the value of this parameter ranges from 0 to 2. When the board is a board other than the UTRPc board, the value of this parameter ranges from 0 to 1.

DSP ETHTR K MOD ETHTR K

LOFD-0 03008 / TDLOF D-00300 8

Ethernet Link Aggrega tion(IEE E 802.3ad)

RMV ETHTR K

GUI Value Range: 0~2 Unit: None Actual Value Range: 0~2 Default Value: 0

RST ETHTR K LST ETHTR K ETHTR KLNK

PN

ADD ETHTR KLNK DSP ETHTR KLNK RMV ETHTR KLNK

MRFD210103 LOFD-0 03008 / TDLOF D-00300 8

Link aggregat ion

Meaning: Indicates the number of the member port in an Ethernet trunk.


Unit: None

Link aggregat ion

Meaning: Indicates whether the member port is the primary port of an Ethernet trunk. Each Ethernet trunk has one and only one primary port. The primary port must be the first port added to an Ethernet trunk and the last port removed from the Ethernet trunk.

GUI Value Range: 0~5 Actual Value Range: 0~5 Default Value: None

LST ETHTR KLNK ETHTR KLNK

FLAG

ADD ETHTR KLNK LST ETHTR KLNK

Issue 02 (2015-08-31)

MRFD210103 LOFD-0 03008 / TDLOF D-00300 8


GUI Value Range: NO(No), YES(Yes) Unit: None Actual Value Range: NO, YES Default Value: None


77


7 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

DEVIP

SBT

ADD DEVIP

None

None

Meaning: Indicates the type of sub-board on the board where a port is located.

MOD DEVIP

GUI Value Range: BASE_BOARD(Base Board), E1_COVERBOARD(E1 Cover Board), BACK_BOARD(Back Board), ETH_COVERBOARD(Ethernet Cover Board)

RMV DEVIP

Unit: None

DSP DEVIP

Actual Value Range: BASE_BOARD, E1_COVERBOARD, BACK_BOARD, ETH_COVERBOARD

LST DEVIP

Default Value: None DEVIP

PT

ADD DEVIP

None

None

MOD DEVIP

Meaning: Indicates the type of the physical port. The UMTS currently does not support SUBIF. GUI Value Range: PPP(PPP Link), MPGRP(Multilink PPP Group), ETH(Ethernet Port), ETHTRK(Ethernet Trunk), LOOPINT(Loopback Interface), SUBIF(Sub-interface), ETHCI(Ethernet CI Port)

RMV DEVIP DSP DEVIP

Unit: None Actual Value Range: PPP, MPGRP, ETH, ETHTRK, LOOPINT, SUBIF, ETHCI

LST DEVIP

Default Value: None DEVIP

PN

ADD DEVIP

None

None

Meaning: Indicates the number of a port. GUI Value Range: 0~63

MOD DEVIP

Unit: None

RMV DEVIP

Default Value: None

Actual Value Range: 0~63

DSP DEVIP LST DEVIP

Issue 02 (2015-08-31)


78


7 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

DEVIP

IP

ADD DEVIP

WRFD050402

Meaning: Indicates the IP address configured for the port.

MOD DEVIP

WRFD050411

RMV DEVIP

GBFD-1 18601

IP Transmi ssion Introduc tion on Iub Interface

DSP DEVIP

GBFD-1 18611

DSP MULTI CASTIP

Fraction al IP Function on Iub Interface

LST DEVIP

Abis over IP

GUI Value Range: Valid IP address Unit: None Actual Value Range: Valid IP address Default Value: None

Abis IP over E1/T1 CASCA DEPOR T

PN

DSP BBPLN KSTAT

None

None

Meaning: Indicates the number of the port that carries the interconnection link. GUI Value Range: 0~6,8

LST CASCA DEPOR T

Unit: None Actual Value Range: 0~6,8 Default Value: None

SET CASCA DEPOR T CASCA DEPOR T

SW

SET CASCA DEPOR T LST CASCA DEPOR T

Issue 02 (2015-08-31)

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)


79


7 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

IPCLKL NK

LN

ADD IPCLKL INK

WRFD050501

Clock Sync on Ethernet in NodeB

Meaning: Indicates the number of the IP clock link.

Clock over IP

Default Value: 0

DSP IPCLKL INK DSP PRICLA SS RMV IPCLKL INK SET CLASSI DENTIF Y SET PRICLA SS LST IPCLKL INK LST PRICLA SS

GBFD-1 18606 GBFD-1 18620 LOFD-0 0301301 LOFD-0 0301302 LOFD-0 0301303 LOFD-0 03023

GUI Value Range: 0~2 Unit: None Actual Value Range: 0~2

Clock over IP support 1588v2 Synchro nization with Ethernet (ITU-T G.8261) IEEE15 88 V2 Clock Synchro nization Clock over IP (Huawei propriet ary) IEEE 1588v2 over IPv6

Issue 02 (2015-08-31)


80


7 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

IPCLKL NK

DEVTY PE

ADD IPCLKL INK

None

None

Meaning: Indicates the device type of the IP clock. The value of this parameter can be OC_SLAVE or OC_MASTER. In OC_SLAVE mode, the base station serves as the clock equipment that is synchronized with the upstream clock. In OC_MASTER mode, the base station works as a master clock device to provide IP clock signals, and you need to configure an external reference clock source for supplying reference clock signals.

LST IPCLKL INK

GUI Value Range: OC_SLAVE(OC_SLAVE), OC_MASTER(OC_MASTER) Unit: None Actual Value Range: OC_SLAVE, OC_MASTER Default Value: OC_SLAVE(OC_SLAVE) IPCLKL NK

CNM

ADD IPCLKL INK LST IPCLKL INK

WRFD050501 GBFD-1 18620 LOFD-0 0301301 LOFD-0 0301302 LOFD-0 0301303 LOFD-0 03023

Clock Sync on Ethernet in NodeB Clock over IP support 1588v2 Synchro nization with Ethernet (ITU-T G.8261)

Meaning: Indicates the networking type for the IP clock. The LTE currently does not support L3 Multicast function. GUI Value Range: UNICAST(Unicast), L3_MULTICAST(L3 Multicast), L2_MULTICAST(L2 Multicast) Unit: None Actual Value Range: UNICAST, L3_MULTICAST, L2_MULTICAST Default Value: UNICAST(Unicast)

IEEE15 88 V2 Clock Synchro nization Clock over IP (Huawei propriet ary) IEEE 1588v2 over IPv6

Issue 02 (2015-08-31)


81


7 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

IPCLKL NK

PROFIL ETYPE

ADD IPCLKL INK

WRFD050501

Clock Sync on Ethernet in NodeB

Meaning: Indicates the type of protocol supported by the IEEE 1588 V2-compliant IP clock link, which can be ITU-T G.8265.1, IEEE 1588 V2, IEEE1588V2_16.1 or ITU-T G.8275.1. ITU-T G. 8265.1 is defined by the International Telecommunication Union (ITU) for frequency synchronization of an IEEE 1588 V2-compliant IP clock link with the networking type of UNICAST. An IP clock link in compliant with ITU-T G.8265.1 supports interconnection with servers from other vendors. An IP clock link in compliant with IEEE 1588 V2 supports interconnection with clock service devices from other vendors only in L2 or L3 multicast networking. IEEE1588V2_16.1 can also be used for interconnection with clock service devices from other vendors when the other vendors do not support ITU-T G.8265.1.The contentS of IEEE1588V2_16.1 refers to the optional section 16.1 of IEEE1588V2 protocol. ITU-T G.8275.1 is defined by the International Telecommunication Union (ITU) for time synchronization of an IEEE 1588 V2-compliant IP clock link with the networking type of L2 multicast. An IP clock link in compliant with ITU-T G.8275.1 supports interconnection with clock service devices from other vendors.

LST IPCLKL INK

GBFD-1 18620 LOFD-0 0301301 LOFD-0 0301302 LOFD-0 0301303 LOFD-0 03023

Clock over IP support 1588v2 Synchro nization with Ethernet (ITU-T G.8261) IEEE15 88 V2 Clock Synchro nization Clock over IP (Huawei propriet ary) IEEE 1588v2 over IPv6

GUI Value Range: 1588V2(1588V2), G.8265.1(G. 8265.1), 1588V2_16.1(1588V2_16.1), G.8275.1(G. 8275.1) Unit: None Actual Value Range: 1588V2, G.8265.1, 1588V2_16.1, G.8275.1 Default Value: 1588V2(1588V2)

Issue 02 (2015-08-31)


82


8 Counters

8

Counters

There are no specific counters associated with this feature.

Issue 02 (2015-08-31)


83


9 Glossary

9

Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

Issue 02 (2015-08-31)


84


10

10 Reference Documents

Reference Documents

1.

USU3910 Hardware Description

2.

UL CoMP Feature Parameter Description in the LTE FDD documentation

3.

Carrier Aggregation Feature Parameter Description for LTE FDD

4.

CSPC Feature Parameter Description for LTE FDD

5.

Base Station Cabinets and Subracks (Including the BBU Subrack) Configuration Feature Parameter Description

6.

Ethernet OAM Feature Parameter Description

Issue 02 (2015-08-31)


85

USU3910 Based Multi BBU Interconnection(SRAN10.1_02)

Recommend Documents