Interconnection Feature Parameter
Description
Issue 02
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
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.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
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
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 ParameterChange AffectedEntity
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 Macro and
LampSite eNodeBs Editorial
change
Revised descriptions in this document. None Macro and
LampSite eNodeBs
SRAN10.1 01 (2015-03-20)
This issue includes the following changes. Chang
e Type Change Description Parameter Change AffectedEntity
Feature change
Added descriptions about hardware requirements and licenses to be purchased for multi-BBU
interconnection. For details, see 6.4.2 Requirements.
None Macro and
LampSite eNodeBs
This issue includes the following changes. Chang
e Type Change Description Parameter Change AffectedEntity
Feature change
Added descriptions about hardware requirements for inter-BBU interconnection. For details, see 6.4.2 Requirements.
None Macro and
LampSite eNodeBs Editoria
l change
Revised descriptions in this document. None Macro and
LampSite eNodeBs
SRAN10.1 Draft B (2015-02-10)
This issue includes the following changes. Chang
e Type Change Description Parameter Change AffectedEntity
Feature change
None None N/A
Editoria l change
Revised descriptions in this document. None Macro and
LampSite eNodeBs
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.
Chang
e Type Change Description Parameter Change AffectedEntity
Feature change
Added descriptions related to the distributed Cloud BB mode.
None Macro and
LampSite eNodeBs 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 Macro and
LampSite eNodeBs
Chang
e Type Change Description Parameter Change AffectedEntity
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 Macro and
LampSite eNodeBs
Added the service features supported in a Cloud BB network. For details, see Service Features
Supported.
None Macro and
LampSite eNodeBs Editoria
l change
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.
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
NOTE
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.
Service Features Supported
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
l 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.
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.
l 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 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
– 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)
– 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.
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
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 Configuration principles
– 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.
– 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.
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)
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 Configuration principles
– 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
second-level 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.
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 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.
l 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
Configuration Operation 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.
SET NE: CLOUDBBID=666;
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.
Configuration Operation 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.
NOTE
This operation is required only for BBU3900s.
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;
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. SET NE: CLOUDBBID=666;
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.
ADD INTERCONNE:
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.
Configuration Operation MML Command Example Turn on the alarm detection switch for
interconnection ports.
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.
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 Table 3-4 describes the data configuration on a first-level USU in distributed Cloud BB
Table 3-4 Data configuration on a first-level USU in distributed Cloud BB mode
Configuration Operation MML Command Example
Specify a Cloud BB ID for a USU.
SET NE: CLOUDBBID=666;
Specify the USU working mode. 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.
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.
Configuration Operation 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
Specify a Cloud BB ID for a USU. SET NE: CLOUDBBID=666;
Specify the USU working mode. SET GTRANSPARA: Level=LEVEL2,
NETMODE =CENTRALIZED, NodeID=0;
In this command, set the NodeID parameter to a value ranging from 0 to 5.
Turn on the alarm detection switch for interconnection ports.
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
Configuration Operation MML Command Example
Specify a Cloud BB ID for a USU. SET NE: CLOUDBBID=666;
Specify the USU working mode. 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;
Configuration Operation 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.
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
SET CLKMODE: MODE=FREE;
In this command, set the MODE parameter to FREE(Free).
The USU works in free-run mode.
NE Type MML Command for Clock
Synchronization Configuration Description
eNodeB 1. Adding a GPS or an IP clock link
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).
Each BBU is configured with a clock source for time synchronization.
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.
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 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.
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; 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; SET CLKSYNC MODE: CLKSYNC MODE=TI ME, SYSCLKS RC=LOCA L; SET CLOUDSRC: CLOUDSRC=E NABLE; 2 Provi ding a clock sourc e for time synch roniz ation 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; SET CLKSYNC MODE: CLKSYNC MODE=TI ME, SYSCLKS RC=LOCA L; ADD IPCLKLINK: LN=2, ICPT=PTP, DEVTYPE=OC _MASTER, CNM=L2_MU LTICAST, PROFILETYPE =1588V2;
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 3 Recei ving clock signal s Central ized Cloud BB 1. ADD INTERCLK: LN=0; In this command, always set the LN parameter to 0. 2. SET CLKMODE: MODE=MANUAL, CLKSRC=INTERCLK , SRCNO=0; SET CLKSYNC MODE: CLKSYNC MODE=TI ME, SYSCLKS RC=LOCA L; N/A 4 Recei ving clock signal s Distrib uted Cloud BB 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; SET CLKSYNC MODE: CLKSYNC MODE=TI ME, SYSCLKS RC=LOCA L; N/A
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 l GPS clock sharing 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; SET CLKSYNC MODE: CLKSYNC MODE=TI ME; SET CLOUDSRC: CLOUDSRC=E NABLE;
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 2 Provi ding a clock sourc e for time synch roniz ation Distrib uted Cloud BB l GPS clock sharing 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; SET CLKSYNC MODE: CLKSYNC MODE=TI ME; ADD IPCLKLINK: LN=2, ICPT=PTP, DEVTYPE=OC _MASTER, CNM=L2_MU LTICAST, PROFILETYPE =1588V2; 3 Forw ardin g clock signal s Central ized Cloud BB
Set the clock mode to free-run to prevent an alarm. SET CLKMODE: MODE=FREE;
nar
io Function SignalTrans missi on Bearer Mode
Synchronization Object
Configuration Commandfor System Clock Mode Setting Command for Clock Sharing Mode Setting 4 Forw ardin g clock signal s Distrib uted Cloud BB 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; SET CLKSYNC MODE: CLKSYNC MODE=TI ME; N/A 5 Forw ardin g clock signal s 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; SET CLKSYNC MODE: CLKSYNC MODE=TI ME; ADD IPCLKLINK: LN=2, ICPT=PTP, DEVTYPE=OC _MASTER, CNM=L2_MU LTICAST, PROFILETYPE =1588V2;
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 6 Forw ardin g clock signal s 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; SET CLKSYNC MODE: CLKSYNC MODE=TI ME; SET CLOUDSRC: CLOUDSRC=E NABLE;
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:
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
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.
4
Related Features
Prerequisite Features
None
Mutually Exclusive Features
None
Impacted Features
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 inter-BBU 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 inter-BBU cell coordination.
For details about the impact of these features on network performance, see the relevant feature parameter descriptions.
6
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 multi-BBU interconnection scenarios is the same as that when multi-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
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:
Hardware
Table 6-1 describes the configuration restrictions of boards in the BBU.
Table 6-1 Board configuration restrictions Networ
king Type of theBase 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.
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.
Not require d With interconnected BBUs NOTE BBU interconnection applies only to the following scenario: l Root BBU (LTE) + leaf BBU (UMTS) l Root BBU (GL)+ leaf BBU (UMTS)
l The BBUs must be connected in UCIU+UMPT mode. The UCIU can be installed only in the BBU in LTE mode.
l In LTE mode, one UMPT or two UMPTs working in load sharing mode can be used.
Not require d
Networ
king Type of theBase Station Connecting to the USU
Main Control Board/BBP UCCU
Either of the preceding types
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. 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.
Not require d 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. 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.
Not require d
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 first-level USUs to be connected to the second-first-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.
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 ControlItem NE SalesUnit
BBU Pool Intercon nection Port License 88032BU L LT1S0BBUIP0 0 BBU Pool Interconnection Port License (per BBU/ USU)
US U
per NE
l 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.
– LTE FDD eNodeBs in centralized Cloud BB mode
Featur
e ID FeatureName Model LicenseControl Item NE Sales Unit LOFD-081220 Inter-BBU 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 FeatureName LicenseControl Item ID License Control Item NE Sales Unit TDLO FD-081 213 Inter-BBU Clock Sharing LT1STIBCS00 0 Inter-BBU Clock Sharing(TD D) eNodeB per eNode B
Featur
e ID FeatureName LicenseControl Item ID License Control Item NE Sales Unit LOFD-003013 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 FeatureName LicenseControl Item ID License Control Item 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
– 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)
Name
Subboard Type ETHCIPORT.S
BT
Set this parameter to BASE_BOARD( Base Board). Network plan (negotiation not required)
Port No. ETHCIPORT.P
N
Set this parameter to 0.
Network plan (negotiation not required)
– 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). Network plan (negotiation not required)
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. Network plan (negotiation not required)
– 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). Network plan (negotiation not required)
Trunk No. ETHTRK.TN Set this parameter
to a unique value for an Ethernet
Network plan (negotiation not required)
– 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. Network plan (negotiation not required)
Master Flag ETHTRKLNK.F
LAG
Set this parameter to YES(Yes) for the primary port and NO(No) for other ports.
Network plan (negotiation not required)
– 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). Network plan (negotiation not required)
Name
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). Network plan (negotiation not required)
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. Network plan (negotiation not required)
IP Address DEVIP.IP Set this parameter
as required.
Network plan (negotiation not 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
Network plan (negotiation not required)
Parameter
Name Parameter ID Setting Notes Data Source
Switch CASCADEPOR
T.SW
Set this parameter to ON(On).
Network plan (negotiation not required)
– 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 DataSource
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. Network plan (negotiation not required)
er Name 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. Network plan (negotiation not required) Clock Net Mode IPCLKLNK.CN M(N/A,LTE FDD eNodeB)
Set this parameter to L2_MULTICAST. Network plan (negotiation not required) Profile Type IPCLKLNK.PR OFILETYPE(N/ A,LTE FDD eNodeB)
Set this parameter to 1588V2. Network
plan (negotiation not
required)
– The following table describes the parameters that must be set in the TASM MO to
configure the system clock. Parameter
Name ParameterID Setting Notes DataSource
Clock Working Mode
TASM.MO DE
Set this parameter to MANUAL. Network
plan (negotiati on not required)
Parameter
Name ParameterID Setting Notes DataSource
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). Network plan (negotiati on not required) 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. Network plan (negotiati on not required)
Name ID 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). Network plan (negotiati on not required)
– The following table describes the parameters that must be set in the INTERCLK
MO to configure the shared clock source. Parameter
Name Parameter ID Setting Notes DataSource
Interconnectio n Clock No.
InterClk. LN
Set this parameter to 0. Network
plan (negotiati on not required) 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. Network plan (negotiati on not required)
l Configuration data dedicated to USUs
– The following table describes the parameter that must be set in the INTERCONNE
MO to specify NE names. Parameter
Name Parameter ID Setting Notes DataSource
Network Element Name
INTERCONNE. NENAME
Set this parameter to the name of an eNodeB connecting to a USU.
Network plan (negotiatio
– 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 DataSource
Level GTRANSPARA.
LEVEL
Set this parameter to LEVEL1(LEVEL1) or LEVEL2(LEVEL2) as required. Network plan (negotiatio n not required)
Network Mode GTRANSPARA.
NETMODE
Set this parameter to CENTRALIZED(CEN TRALIZED), DISTRIBUTED(DIST RIBUTED), or HYBRID(HYBRID) as required. Network plan (negotiatio n not 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. Network plan (negotiatio n not required)
– 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 DataSource
IP Address PORTIP.IP Set this parameter for an
HEI port working in SCPRI/SRIO mode on the ULPU in a USU as required. Network plan (negotiatio n not required)
Mask PORTIP.MASK Set this parameter as
required.
Network plan (negotiatio
Parameter
Name Parameter ID Setting Notes DataSource
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 ). Network plan (negotiatio n not required)
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.