USU3910 Based Multi BBU Interconnection (SRAN12.1 - 08)
USU3910 Based Multi BBU Interconnection (SRAN12.1 - 08)
USU3910-based Multi-BBU
Interconnection Feature Parameter
Description
Issue 08
Date 2018-05-15
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.
Website: http://www.huawei.com
Email: [email protected]
Contents
2 Overview......................................................................................................................................... 6
2.1 Introduction.................................................................................................................................................................... 6
2.2 Benefits........................................................................................................................................................................... 6
3 Technical Description...................................................................................................................8
3.1 Introduction.................................................................................................................................................................... 8
3.2 Multi-BBU Interconnection Modes................................................................................................................................9
3.2.1 Interconnection Between BBUs and One First-Level USU........................................................................................ 9
3.2.2 Interconnection Between BBUs and Two Levels of USUs....................................................................................... 15
3.3 Key Configurations.......................................................................................................................................................19
3.3.1 Basic Data Configurations.........................................................................................................................................19
3.3.1.1 General Principles...................................................................................................................................................19
3.3.1.2 Data Configurations on an eNodeB........................................................................................................................20
3.3.1.3 Data Configurations on a First-Level USU............................................................................................................ 27
3.3.1.4 Data Configurations on a Second-Level USU........................................................................................................33
3.3.2 Clock Data Configurations........................................................................................................................................ 35
3.3.2.1 Each BBU Configured with an External Clock Source..........................................................................................36
3.3.2.2 Clock Signal Sharing.............................................................................................................................................. 37
3.3.2.3 Clock Source Backup............................................................................................................................................. 50
4 Related Features...........................................................................................................................53
5 Network Impact........................................................................................................................... 54
6 Engineering Guidelines............................................................................................................. 55
6.1 When to Use................................................................................................................................................................. 55
6.2 Required Information................................................................................................................................................... 55
6.3 Planning........................................................................................................................................................................ 55
6.4 Deployment.................................................................................................................................................................. 56
6.4.1 Process....................................................................................................................................................................... 56
6.4.2 Requirements............................................................................................................................................................. 57
6.4.3 Data Preparation and Feature Activation...................................................................................................................60
6.4.3.1 Data Preparation..................................................................................................................................................... 60
6.4.3.2 Using the CME....................................................................................................................................................... 67
6.4.3.3 Using MML Commands......................................................................................................................................... 67
6.4.3.4 MML Command Examples.................................................................................................................................... 68
6.4.4 Activation Observation..............................................................................................................................................70
6.4.5 Reconfiguration......................................................................................................................................................... 74
6.4.5.1 Reconfiguration for the Centralized Cloud BB Mode............................................................................................74
6.4.5.1.1 Adding BBUs...................................................................................................................................................... 75
6.4.5.1.2 Removing BBUs..................................................................................................................................................77
6.4.5.1.3 Changing One-Level USU Interconnection to Two-Level USU Interconnection...............................................77
6.4.5.1.4 Adding a First-level USU.................................................................................................................................... 79
6.4.5.1.5 Changing from One Second-Level USU to Two Second-Level USUs............................................................... 81
6.4.5.1.6 Backup of Second-Level USUs........................................................................................................................... 84
6.4.5.1.7 Backup of First-Level USUs............................................................................................................................... 85
6.4.5.2 Reconfiguration for Distributed Cloud BB Mode.................................................................................................. 86
6.4.5.2.1 Adding BBUs...................................................................................................................................................... 86
6.4.5.2.2 Removing BBUs..................................................................................................................................................89
6.4.5.2.3 Changing One-Level USU Interconnection to Two-Level USU Interconnection...............................................89
6.5 Performance Monitoring...............................................................................................................................................92
6.6 Parameter Optimization................................................................................................................................................ 92
6.7 Possible Issues.............................................................................................................................................................. 92
7 Parameters..................................................................................................................................... 94
8 Counters...................................................................................................................................... 104
9 Glossary....................................................................................................................................... 106
10 Reference Documents............................................................................................................. 107
1.1 Scope
This document describes the USU3910-based multi-BBU interconnection feature, including
its technical principles, related features, network impact, and engineering guidelines.
Feature compatibility with specific terminal models is not presented in this document. For
compatibility information, contact Huawei engineers.
Any parameters, alarms, counters, or managed objects (MOs) described herein apply only to
the corresponding software release. For future software releases, refer to the corresponding
updated product documentation.
SRAN12.1 08 (2018-05-15)
This issue includes the following changes.
SRAN12.1 07 (2018-01-22)
This issue includes the following changes.
SRAN12.1 06 (2017-10-23)
This issue includes the following changes.
SRAN12.1 05 (2017-09-20)
This issue includes the following changes.
Feature l Added the support for 5900 series None Macro and
change eNodeBs and DBS5900 LampSite LampSite eNodeBs
eNodeBs.
l Added the BBU5900.
SRAN12.1 04 (2017-08-30)
This issue includes the following changes.
SRAN12.1 03 (2017-06-29)
This issue includes the following changes.
SRAN12.1 02 (2017-05-25)
This issue includes the following changes.
SRAN12.1 01 (2017-03-08)
This issue does not include any changes.
Feature l Added support for this feature by the None Macro and
change UBBPei. LampSite
l Added support for backup mode between eNodeBs
two second-level USUs in centralized
Cloud BB mode and connection
descriptions when two second-level
USUs work in backup mode. For details,
see 6.4.5.1.6 Backup of Second-Level
USUs.
l Added support for a maximum of 10
BBUs connecting to a first-level USU in
the LTE TDD system. For details, see
Centralized Cloud BB Mode.
l Added support for first-level USU
backup. For details, see 3.3.1 Basic Data
Configurations and 6.4.5.1.7 Backup of
First-Level USUs.
l Renamed coordination-based features.
For details, see 3.1 Introduction.
l Added the description that the baseband
processing board connecting to a USU
must work in LTE only mode. For
details, see 6.4.2 Requirements.
2 Overview
2.1 Introduction
USU3910-based multi-BBU interconnection (multi-BBU interconnection for short) allows
two or more BBUs to communicate with each other and process services by connecting the
BBUs and USU3910s.
NOTE
l The universal switching unit (USU) in this document refers to the USU3910.
l BBUs in this document include the BBU3900, BBU3910, and BBU5900 but exclude the
BBU3910A.
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.
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 hybrid Cloud BB mode.
2.2 Benefits
Multi-BBU interconnection provides the following benefits:
l Helps achieve inter-BBU cell coordination when a coordinated-based feature is enabled.
l Reduces the number of required Global Positioning System (GPS) or BieDou antennas
because interconnected BBUs can share GPS or BieDou clock signals.
l Improves the reliability of the clock on Cloud BB networks by supporting clock source
backup.
NOTE
In this document, GPS clock sources include GPS and RGPS clock sources.
3 Technical Description
3.1 Introduction
Multi-BBU Interconnection Modes
l Interconnection between BBUs and a USU: involves one USU, multiple BBUs, and the
connection between the USU and BBUs, as shown in Figure 3-1.
l Interconnection between BBUs and two levels of USUs: involves multiple first-level
USUs, multiple BBUs, one or two second-level USUs, 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.
NOTE
In USU3910-based multi-BBU interconnection, the longest distance between a BBU and an RRU is 20
km.
l BBU3900, BBU3910, and BBU5900 modules can connect to the same first-level USU.
l In the first-level USU, a universal enhanced switch fabric unit (UEFU) and a universal
line processing unit (ULPU) must be installed in slots 0 and 1, respectively.
l eNodeBs connecting to the first-level USU are classified into two types:
– If one BBU is used, the BBU directly connects to the USU.
– If two BBUs are used, the root BBU directly connects to the USU.
NOTE
NOTE
The first-level USU can work in backup mode only in centralized Cloud BB mode.
Figure 3-3 Cable connections between BBUs and USUs in centralized Cloud BB mode when
first-level USUs do not work in backup mode
Figure 3-4 Cable connections between BBUs and USUs in centralized Cloud BB mode when
first-level USUs work in backup mode
For a BBU:
l When first-level USUs do not work in backup mode, one main control board is required
in a BBU and this board connects to a first-level USU through a CI interconnection
cable.
l When first-level USUs work in backup mode, two main control boards are required in a
BBU. Each main control board connects to a CI interconnection cable, and the two
cables connect to different first-level USUs.
l A maximum of six HEI interconnection cables can be configured for a BBU. The
number of HEI interconnection cables connecting to a BBU equals to the number of
BBPs in the BBU.
For a first-level USU:
l If the CASCADEPORT.PM parameter of an HEI port on the ULPU is set to AUTO
(recommended) or SCPRI/SRIO, there are no strict rules for the mappings between the
ports on the ULPU and BBP.
NOTE
If the parameter is set to SCPRI/SRIO, the ports of the ULPU and connected BBP work in the
SRIO mode. If this parameter is set to AUTO, the ports of the ULPU and connected BBP work in
the 40GE mode to obtain larger channel bandwidth.
l In the LTE FDD network, a maximum of five BBUs can be configured for each first-
level USU.
l In the LTE TDD network, a maximum of 10 BBUs can be configured for each first-level
USU. The number of connected BBPs in the BBUs cannot exceed the number of HEI
ports on the ULPU.
For a Cloud BB network:
l A maximum of 12 first-level USUs and 60 BBUs can be deployed in a Cloud BB
network.
l The cable connecting a BBU and a first-level USU must be shorter than or equal to 100
m.
HEI ports, cable connections, and configurations are the same for the UBBPe, UBBPem, or
UBBPei. The following takes the UBBPe as an example.
The optical module of an HEI port on a ULPU or UBBPe or the M5/S0 port on a UCCU provides
two optical ports. Each optical port provides single-fiber bidirectional transmission at a rate of 10
Gbit/s. You can connect one or two cables to an optical module.
l If an HEI port on a ULPU connects to two optical fibers, the fibers can connect to either the
same BBU (shown in Figure 3-6) or different BBUs (shown in Figure 3-7).
l If a BBU connects to two optical fibers, the fibers must connect to the same ULPU.
For a BBU:
l A UBBPem or UBBPei can be installed only in a BBU3910 or BBU5900.
l If a UBBPe is installed in a BBU3900, ensure that at least a UBBPe is installed in slot 2
or 3 and connects to a USU. This restraint does not apply to the BBU3910 and
BBU5900.
l In a BBU3900, the UCCU is installed in slot 3, 2, 4, 5, 1, or 0 in descending order of
priority. If a UCCU is not installed in slot 2 or 3, baseband interconnection cables are
required to connect the UCCU and BBP, as shown in Figure 3-5. This restraint does not
apply to the BBU3910.
Figure 3-5 Connections of baseband interconnection cables between a UCCU and BBP
Figure 3-6 Cable connections between BBUs and a USU in distributed Cloud BB mode
when a BBU and USU are connected using two optical fibers
l An HEI port on a ULPU can connect to two BBUs, and to each BBU using one optical
fiber, as shown in Figure 3-7.
Figure 3-7 Cable connections between BBUs and a USU in distributed Cloud BB mode
when a BBU and USU are connected using one optical fiber
Figure 3-8 Cable connections between BBUs and a USU in hybrid Cloud BB mode
NOTE
l In each USU, a UEFU is always installed in slot 0 regardless of whether in centralized or distributed
Cloud BB mode.
l First- and second-level USUs cannot be connected in hybrid Cloud BB mode.
l On a Cloud BB network, connections between first- and second-level USUs and those between first-
level USUs and BBUs are independent.
one second-level USU which does not function as a server and a CI-DL port in the other
second-level USU that functions as a server.
When two second-level USUs are configured and they work in backup mode:
– CI interconnection cables between two second-level USUs: The UEFU in slot 0 in a
second-level USU connects to the other second-level USU using two CI
interconnection cables. One cable connects to the CI-DL port on the UEFU and the
other cable connects to the CI-UL port on the UEFU at the peer end. The two CI
interconnection cables form a trunk. The cables transmit the control and clock
information between two second-level USUs.
– CI interconnection cable between first- and second-level USUs: One end of the
cable connects to the CI-DL port in the second-level USU. The other end connects
to the CI-UL port in the first-level USU. Only one CI-UL port can be activated in
the first-level USU to prevent loopback between two second-level USUs.
– FABRIC interconnection cables between a first-level USU and two second-level
USUs in backup mode: Each first-level USU connects to the UEFU in a second-
level USU using two FABRIC interconnection cables.
l Configuration principles
– Each first-level USU must connect to four FABRIC interconnection cables. These
cables connect to two or four UEFU boards in second-level USUs. Connections of
FABRIC interconnection cables have no requirements for the FABRIC port
numbers.
NOTE
If the number of first-level USUs connected to a second-level USU is less than or equal to
three, the second-level USU can use only one UEFU. The first-level USUs connect to the
second-level USU through four FABRIC interconnection cables and port numbers are not
strictly matched. This configuration reduces transmission reliability.
– Slots 0 and 1 in a second-level USU can house UEFU boards only.
– A maximum of two second-level USUs can be deployed in a Cloud BB network. A
maximum of 12 first-level USUs can be configured for a second-level USU.
– When two to six first-level USUs are configured, one second-level USU is required.
When seven to 12 first-level USUs are configured, two second-level USUs are
required.
– The optical fiber connecting a first-level USU and a second-level USU must be
shorter than or equal to 90 m. The optical fiber connecting two second-level USUs
must be shorter than or equal to 100 m.
l Example
Figure 3-9, Figure 3-10, Figure 3-11, and Figure 3-12 show the cable connections
between USUs in centralized Cloud BB mode.
Figure 3-9 Cable connections between USUs in centralized Cloud BB mode when only
one second-level USU is configured (with two UEFU boards)
Figure 3-10 Cable connections between USUs in centralized Cloud BB mode when only
one second-level USU is configured (with only one UEFU)
Figure 3-11 Cable connections between USUs in centralized Cloud BB mode when two
second-level USUs do not work in backup mode
Figure 3-12 Cable connections between USUs in centralized Cloud BB mode when two
second-level USUs work in backup mode
– The second-level USU provides a maximum of 30 HEI ports. When each first-level
USU connects to five HEI ports in the second-level USU, the second-level USU can
connect to a maximum of six first-level USUs.
– The total length of optical fibers between first-level and second-level USUs must
not exceed 10 km.
– The total length of optical fibers between two coordinated BBUs that transmit
signals through first- and second-level USUs must not exceed 20 km.
– HEI ports 25 to 29 in a first-level USU connect to HEI ports in the second-level
USU by using ten optical fibers without any requirement for 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 two to six first-level USUs are configured, one second-level USU is required.
l Example
l The NODEID parameter cannot be set to the same value for each USU at the same level
on a Cloud BB network.
l In centralized Cloud BB mode, the NODEID parameter must be set to 0 or 1 for the
second-level USU that functions as the server.
l Node IDs need be planned and used starting from small values preferably. If larger node
IDs are used when smaller ones are available, the network is temporarily interrupted.
IP addresses must be configured in the same network segment and be unique on a Cloud BB
network. The following IP addresses must be configured:
l Centralized Cloud BB mode:
– IP address of an HEI port which is on the ULPU in a USU and connects to an HEI
interconnection cable
– IP address of a CI port which is on the UMPT in a BBU and connects to a CI
interconnection cable
l Distributed Cloud BB mode:
– IP address of the M5/S0 port which is on the UCCU in a BBU and connects to an
HEI interconnection cable
– IP address of the HEI port which is on the UBBPe, UBBPem, or UBBPei in a BBU
and connects to an HEI interconnection cable
NOTE
In a Cloud BB network, these IP addresses must be in a different network segment from the O&M IP
addresses and other interface IP addresses (such as IP addresses of the S1 and X2 interfaces).
The MML commands listed in this section are used as examples and only key parameter settings are
provided. Other parameters, such as Cabinet No., Subrack No., Slot No., and Port No. must be set
based on site conditions.
Table 3-1 Data configurations on an eNodeB in centralized Cloud BB mode when first-level
USUs do not work in backup mode
Configuration Operation MML Command Example
Add the SRIOPORT MO for the ADD SRIOPORT: CN=0, SRN=0, SN=3,
measurement of the bandwidth pre-allocated PN=0;
to the SRIO port. Set the PN parameter to 0.
(Optional) Set the working mode of the SET PORTMODE: CN=0, SRN=0, SN=3,
ports on the UBBPe, UBBPem, or UBBPei PN=6, PM=AUTO;
to AUTO if the eNodeB uses any of the Set the PN parameter to 6.
ports to connect to a first-level USU.
Turn on the alarm detection switch for l Turn on the alarm detection switch for
interconnection ports. the CI port on a UMPT connecting to a
USU.
SET CASCADEPORT: CN=0, SRN=0,
SN=7, PN=8, SW=ON;
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;
Set the PN parameter to 6.
Table 3-2 Data configurations on an eNodeB in centralized Cloud BB mode when first-level
USUs work in backup mode and main control boards work in the high availability (HA)
group mode
Configuration Operation MML Command Example
Add the SRIOPORT MO for the ADD SRIOPORT: CN=0, SRN=0, SN=3,
measurement of the bandwidth pre-allocated PN=0;
to the SRIO port. Set the PN parameter to 0.
(Optional) Set the working mode of the SET PORTMODE: CN=0, SRN=0, SN=3,
ports on the UBBPe, UBBPem, or UBBPei PN=6, PM=AUTO;
to AUTO if the eNodeB uses any of the Set the PN parameter to 6.
ports to connect to a first-level USU.
Turn on the alarm detection switch for l Turn on the alarm detection switch for
interconnection ports. the CI port on a UMPT connecting to a
USU.
SET CASCADEPORT: CN=0, SRN=0,
SN=7, PN=8, SW=ON;
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;
Set the PN parameter to 6.
Table 3-3 Data configurations on an eNodeB in centralized Cloud BB mode when first-level
USUs work in backup mode and main control boards work in "main control"+"main control
and transmission" mode
Configuration Operation MML Command Example
Add the SRIOPORT MO for the ADD SRIOPORT: CN=0, SRN=0, SN=3,
measurement of the bandwidth pre-allocated PN=0;
to the SRIO port. Set the PN parameter to 0.
(Optional) Set the working mode of the SET PORTMODE: CN=0, SRN=0, SN=3,
ports on the UBBPe, UBBPem, or UBBPei PN=6, PM=AUTO;
to AUTO if the eNodeB uses any of the Set the PN parameter to 6.
ports to connect to a first-level USU.
Turn on the alarm detection switch for l Turn on the alarm detection switch for
interconnection ports. the CI port on a UMPT connecting to a
USU.
SET CASCADEPORT: CN=0, SRN=0,
SN=7, PN=8, SW=ON;
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;
Set the PN parameter to 6.
(Optional) Set the working mode of the HEI SET PORTMODE: CN=0, SRN=0, SN=3,
port on a UBBPe, UBBPem, or UBBPei to PN=6, PM=10GE;
10GE if these BBP boards connect to a Set the PN parameter to 6.
USU.
(Optional) Add two ETHPORT MOs if a l Add two ETHPORT MOs on the
BBU connects to a USU using two optical eNodeB side.
fibers, each of which is used for both – ADD ETHPORT: CN=0, SRN=0,
transmission and reception. 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.
(Optional) Turn on the alarm detection l Turn on the alarm detection switch for
switch for the ports connecting to baseband the ports on the UCCU.
interconnection cables on the UCCU and SET CASCADEPORT: CN=0, SRN=0,
LBBP or UBBPd if the UCCU is not SN=4, PN=0, SW=ON;
installed in slot 2 or 3 in a BBU3900. Set the PN parameter to a value ranging
NOTE from 0 to 4.
This operation is required only for the BBU3900.
l Turn on the alarm detection switch for
the ports on the LBBP/UBBPd.
SET CASCADEPORT: CN=0, SRN=0,
SN=3, PN=6, SW=ON;
Set the PN parameter to 6.
l The MML commands listed in this section are used as examples and only key parameter settings are
provided. Other parameters, such as Cabinet No., Subrack No., Slot No., and Port No. must be set
based on site conditions.
l The distributed or centralized Cloud BB mode in this section describes the networking mode
between the first-level USU and BBUs.
(Optional) Set the working mode of HEI l Set the working mode of HEI ports on
ports on the ULPU. the ULPU to AUTO if the ports between
a first-level USU and a BBU do not
work in the automatic mode.
SET
PORTMODE:CN=0,SRN=0,SN=1,STP
N=0,ETPN=24,PM=AUTO;
l If first- and second-level USUs are
connected in distributed Cloud BB
mode, configure the working mode of
the ports between the first-and second-
level USUs.
SET
PORTMODE:CN=0,SRN=0,SN=1,STP
N=25,ETPN=29,PM=40GE;
l If first- and second-level USUs are
connected in centralized Cloud BB
mode, the interconnection cable between
these USUs is not installed in any port
on the ULPU. In this case, you do not
need to set the working mode for the
ports between the first- and second-level
USUs.
Turn on the alarm detection switch for l Centralized Cloud BB mode between
interconnection ports. first-level USUs and BBUs
– 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;
Set the SN parameter to 0 and the PN
parameter to a value ranging from 0
to 11.
– Turn on the alarm detection switch
for an HEI port on a ULPU which
connects to a BBU.
SET CASCADEPORT: CN=0,
SRN=0, SN=1, PT=HEI, PN=0,
SW=ON;
Set the PN parameter to a value
ranging from 0 to 24.
l Centralized Cloud BB mode between
first- and second-level USUs
– 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;
Set the SN parameter to 0 and the PN
parameter to 0 or 1.
– 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;
Set the SN parameter to 0 and the PN
parameter to a value ranging from 0
to 11.
l Distributed Cloud BB mode between
first- and second-level USUs
Turn on the alarm detection switch for
an HEI port on a ULPU which connects
to a second-level USU.
SET CASCADEPORT: CN=0, SRN=0,
SN=1, PT=HEI, PN=25, SW=ON;
Set the PN parameter to a value ranging
from 25 to 29.
(Optional) Add an Ethernet port on the ADD ETHPORT: CN=0, SRN=0, SN=1,
ULPU if first-level and second-level USUs SBT= ETH_COVERBOARD, PN=100,
are interconnected in distributed Cloud BB PA= FIBER, SPEED=40G,
mode. DUPLEX=FULL, FC=OPEN;
Set the SPEED parameter to 40G and PN
parameter to a value equal to the HEI port
number multiplied by 4.
Configure the IP addresses for HEI ports on l Configure the IP addresses for HEI ports
the ULPU. 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
l In centralized Cloud BB mode, these IP
addresses are allocated to ULPU HEI
ports connecting to eNodeBs
sequentially.
l PORTIPBEGIN and PORTIPEND
must be configured in the same network
segment. The difference between the last
digit of PORTIPEND and
PORTIPBEGIN must be less than the
total number of HEI ports connecting to
eNodeBs.
l Source routes will be automatically
generated after batch IP address
configurations.
l Configure the IP addresses for a single
HEI port on the ULPU.
1. Configure the IP address for an HEI
port.
ADD PORTIP: CN=0, SRN=0,
SN=1, PN=0, IP="10.192.1.1",
MASK="255.255.255.0";
Set PN 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="10.192.1.1", RTTYPE=IF,
IFT=IPPORT, IFNO=0;
Set SN to 1, SBT to
ETH_COVERBOARD, RTTYPE
to IF, IFT to IPPORT, and IFNO to
a value ranging from 0 to 29.
Set the working mode of HEI ports on the l Set the working mode of the ports
ULPU. connecting first-level USUs and BBUs
in distributed Cloud BB mode.
SET PORTMODE: CN=0, SRN=0,
SN=1, STPN=0, ETPN=24, PM=10GE;
Set the PM parameter to 10GE.
l Set the working mode of the ports
connecting first- and second-level USUs
in distributed Cloud BB mode.
SET PORTMODE: CN=0, SRN=0,
SN=1, STPN=25, ETPN=29,
PM=40GE;
Set the PM parameter to 40GE.
NOTE
If first- and second-level USUs are connected
in distributed Cloud BB mode, the
interconnection cable between these USUs is
not installed in any port on the ULPU. You
do not need to set the working mode of ports
between two levels of USUs.
Configure an Ethernet port on the ULPU. ADD ETHPORT: CN=0, SRN=0, SN=1,
SBT= ETH_COVERBOARD, PN=0, PA=
FIBER, SPEED=10G, DUPLEX=FULL,
FC=OPEN;
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.
l Set PN parameter to the value calculated
using the following formula:
Value of PN = 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
HEI port that is marked as port A on the
interface board of the eNodeB side, 2 is
added to the PN value.
l If the optical module is installed in the
HEI port that is marked as port B on the
interface board of the eNodeB side, 3 is
added to the PN value.
l When a port on the ULPU in a first-level
USU connects to the second-level USU,
set the SPEED parameter to 40G, and
the PN parameter to the value equal to
the number of the HEI port multiplied by
4.
Add an Ethernet port aggregation group on l ADD ETHTRK: CN=0, SRN=0, SN=1,
the ULPU and add member ports to the SBT=ETH_COVERBOARD, TN=0;
group when the ULPU is connected to the l ADD ETHTRKLNK: CN=0, SRN=0,
UCCU, UBBPe, UBBPem, or UBBPei SN=1, SBT= ETH_COVERBOARD,
using two optical fibers. TN=0, PN=2, PRI=255, FLAG=YES;
l ADD ETHTRKLNK: CN=0, SRN=0,
SN=1, SBT= ETH_COVERBOARD,
TN=0, PN=3, PRI=255, FLAG=NO;
Set up an Ethernet trunk for five ports l ADD ETHTRK: CN=0, SRN=0, SN=1,
working in 40GE mode (HEI port numbers: SBT=ETH_COVERBOARD, TN=0;
25 to 29; Ethernet port numbers: 100, 104, l ADD ETHTRKLNK: CN=0, SRN=0,
108, 112, and 116) when the ULPU in a SN=1, SBT= ETH_COVERBOARD,
first-level USU connects to the second-level TN=0, PN=100, PRI=255, FLAG=YES;
USU.
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;
The MML commands listed in this section are used as examples and only key parameter settings are
provided. Other parameters, such as Cabinet No., Subrack No., Slot No., and Port No. must be set
based on site conditions.
Turn on the alarm detection switch for Turn on the switch for an interconnection
interconnection ports. port in use.
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;
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.
SET CASCADEPORT: CN=0, SRN=0,
SN=0, PT=CI-UL, PN=0, SW=ON;
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;
Set the PN parameter to a value ranging
from 0 to 11.
Set the working mode of HEI ports on the SET PORTMODE: CN=0, SRN=0, SN=1,
ULPU. STPN=0, ETPN=4, PM=40GE;
Solution Description
This solution applies when each BBU independently obtains its clock source and the USU
clock works in free-running mode, as shown in Figure 3-14.
USU Set the working mode of the reference clock source. The USU works
SET CLKMODE: MODE=FREE; in free-running
mode.
Set the MODE parameter to FREE.
Solution Description
This solution applies when clock signals are shared between BBUs and USUs on a Cloud BB
network. When BBUs are interconnected and one NE is configured with a clock source, other
NEs can share the clock signals from the clock source.
A clock source can be configured in the following ways:
l A USU is configured with a GPS, BeiDou, or IP clock source, as shown in Figure 3-15.
l A BBU is configured with a GPS or BeiDou clock source, as shown in Figure 3-16.
Figure 3-15 Clock synchronization solution when a USU is configured with a clock source
Figure 3-16 Clock synchronization solution when a BBU is configured with a GPS clock
source
NOTE
In the solution shown in the preceding figure, after receiving clock signals from BBU 0, USU 1
forwards the clock signals to the second-level USU (USU 0) and the other connected BBU (BBU 1).
Among main control boards, only the UMPT can connect to a USU.
l Some main control boards can be configured with GPS satellite cards, which can receive GPS clock
signals.
l Some main control boards do not support GPS satellite cards, on which USCU boards can be
configured to receive GPS clock signals.
For details about whether a main control board supports a GPS satellite card, see BBU Hardware
Description.
Clock data configurations on an eNodeB and a USU vary with the clock synchronization
scenario.
l Each NE can perform only one function in clock configurations and takes effect based on
this function. Each BBU can either be configured with a clock source or receive clock
signals from another NE. Each USU can either be configured with a clock source or
forward clock signals.
l IPCLKLINK: If DEVTYPE is set to OC_MASTER or BC, LN is 2. If DEVTYPE is
set to OC_SLAVE, LN is 0 or 1.
l Set the CLKSYNCMODE parameter to TIME for both eNodeBs and USUs except
when the USUs work in free-running mode.
l When a USU is configured with a clock source, the USU must use the GPS or IEEE
1588v2 clock as the clock source for its own synchronization. When an eNodeB is
configured with a clock source, the eNodeB must use the GPS clock source for its own
synchronization. Set the CLKSYNCMODE parameter to TIME for the USU or
eNodeB that is configured with a clock source.
NOTE
Table 3-10 uses a GPS clock as an example. The configuration of a BeiDou clock is similar to that
of a GPS clock. The only difference is that the MODE parameter in the ADD GPS command is set
to BDS for the BeiDou clock.
l Table 3-11 describes the clock data configurations on a USU.
NOTE
l Table 3-11 uses a GPS clock as an example. The configuration of a BeiDou clock is similar to
that of a GPS clock. The only difference is that the MODE parameter in the ADD GPS
command is set to BDS for the BeiDou clock.
l If a first-level USU supports multiple bearer modes for clock signal transmission, the
configuration for each mode is needed and the same parameters need to be configured only
once based on Table 3-11. Specifically, if a first-level USU supports both centralized and
centralized -> distributed clock signal transmission bearer modes, configure the MODE MO
of the USU as a USU supporting centralized -> distributed clock signal transmission bearer
mode. Figure 3-18 and Figure 3-19 show examples.
Abnormal Scenarios
If a clock source is faulty, the NE configured with the clock source continues providing clock
signals for BBUs within 30 minutes.
If a clock source is lost, the difference of the clock on the UMPT of each BBU and the clock
source is less than 1.5 μs within 2 hours. In this scenario, inter-eNodeB coordination-based
services can be performed properly. If the difference is greater than 1.5 μs, the clock accuracy
requirement of service coordination cannot be met and therefore inter-eNodeB coordination-
based services are interrupted.
In hybrid or distributed Cloud BB mode, the two NEs configured with the clock source must
be of the same type, such as:
l Two BBUs
l Two first-level USUs
In addition, the centralized Cloud BB mode also supports the following scenarios:
NOTE
In the figures in this section, the arrows indicate the transmission directions of clock signals.
l When two first-level USUs provide clock source backup:
These USUs can provide clock source backup only when these USUs connect to second-
level USUs in centralized mode. As shown in Figure 3-21, USU 1 and USU 2 can serve
as backups of each other.
In distributed Cloud BB mode, clock signals are transmitted unidirectionally. The first-
level USU configured with a clock source can only provide clock signals to the second-
level USU, but cannot receive signals from the second-level USU. If the clock source of
the first-level USU is faulty, this USU cannot receive clock signals from other first-level
USUs. Therefore, if first-level USUs connect to second-level USUs in distributed Cloud
BB mode, first-level USUs cannot serve as backups for themselves. As shown in Figure
3-22, if the clock source of USU 1 is faulty, BBUs 2 and 3 cannot receive clock signals
from USU 2.
Figure 3-23 Clock synchronization solution where a second-level USU which does not
function as a server is configured with the clock source
4 Related Features
Prerequisite Features
None
Impacted Features
None
5 Network Impact
System Capacity
Multi-BBU interconnection has no impact on system capacity. However, the services
supported by multi-BBU interconnection (as described in 3.1 Introduction) can increase
system capacity after multi-BBU interconnection is enabled. This is because multi-BBU
interconnection facilitates inter-BBU cell coordination.
For details about the impact of related features on system capacity, see relevant feature
parameter description documentations, such as UL CoMP and SFN.
Network Performance
Multi-BBU interconnection has no impact on network performance. However, the services
supported by multi-BBU interconnection (as described in 3.1 Introduction) can enhance
network performance after multi-BBU interconnection is enabled. This is because multi-BBU
interconnection facilitates inter-BBU cell coordination.
For details about the impact of related features on network performance, see relevant feature
parameter description documentations, such as UL CoMP and SFN.
6 Engineering Guidelines
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 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 on BBU and USU installation positions in cabinets, see Base Station Cabinets and
Subracks (Including the BBU Subrack) Configuration. After the installation positions have
been planned, plan USU hardware according to 3.2.1 Interconnection Between BBUs and
One First-Level USU and 3.2.2 Interconnection Between BBUs and Two Levels of USUs.
6.4 Deployment
6.4.1 Process
Figure 6-1 shows the process for deploying the multi-BBU interconnection feature.
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, 5900 Series Base Station Installation Guide, and USU3910 Installation Guide.
l For details about initial configuration of NEs, see 3900 & 5900 Series Base Station Initial
Configuration Guide and USU3910 Initial Configuration Guide.
l For details about NE commissioning, site deployment, and license loading, see 3900 & 5900 Series
Base Station Commissioning Guide and License Management.
l For details about feature-related configurations on the BBU, see eX2 Self-Management and the
relevant feature parameter descriptions (such as UL CoMP and CA).
6.4.2 Requirements
Hardware
Centralized With one BBU l Among main control boards, the UMPT
Cloud BB board including the UMPTa, UMPTb, or
mode UMPTe board can directly connect to a
USU.
l The BBP that directly connects to the USU
must work in LTE only mode.
l The BBP board that connects to the USU
must be any of the following:
– LBBPd
– UBBPd
– UBBPe
– UBBPem
– UBBPei
NOTE
GTMU boards are classified into GTMU, GTMUb, and GTMUc boards.
License
l To use the multi-BBU interconnection feature, operators must purchase the licenses for
this feature.
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.
l The following table describes the parameters that must be set in the ETHCIPORT MO.
Parameter Name Parameter ID Setting Notes
l The following table describes the parameters that must be set in the ETHPORT MO.
Parameter Name Parameter ID Setting Notes
l The following table describes the parameters that must be set in the ETHTRK MO.
Parameter Name Parameter ID Setting Notes
l The following table describes the parameters that must be set in the ETHTRKLNK
MO.
l The following table describes the parameters that must be set in the DEVIP MO.
l The following table describes the parameters that must be set in the CascadePort MO.
l The following table describes the parameters that must be set in the IPCLKLNK MO.
Parameter Name Parameter ID Setting Notes
l 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
l The following table describes the parameters that must be set in the InterClk MO.
Parameter Name Parameter ID Setting Notes
l The following table describes the parameters that must be set in the GTRANSPARA
MO to configure global transmission parameters.
l The following table describes the parameters that must be set in the PORTIP MO.
Parameter Name Parameter ID Setting Notes
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 a UMPT port connecting to a first-level USU is 8, and the number of a BBP port connecting
to a first-level USU is 6.
Step 3 (Optional) Run the ADD SRIOPORT command to add an SRIOPORT MO.
In the LTE network, inter-BBU cell coordination requires phase synchronization between eNodeBs.
Each eNodeB must be configured with a clock source.
l Each BBU configured with an external clock source
a. On each USU, run the SET CLKMODE command with Clock Working Mode set
to FREE.
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 or IPCLK.
d. On each eNodeB, run the SET CLKSYNCMODE command with Clock
Synchronization Mode set to TIME.
l Clock signal sharing
----End
Figure 6-2 Clock synchronization solution when USUs share a clock source
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 BBUs and USUs are connected in centralized Cloud BB mode.
l The following uses a GPS clock as an example. The configuration of a BeiDou clock is similar to
that of a GPS clock. The only difference is that the MODE parameter in the ADD GPS command is
set to BDS for the BeiDou clock.
l For the MML command examples related to USU initial configuration, see "Typical Configuration
Example" in "Initially Configuring a USU (Using the MML Commands)" of USU3910 Initial
Configuration Guide.
1. To configure basic data for USU 0, run the MML commands listed in 3.3.1.4 Data
Configurations on a Second-Level USU. A command example is as follows:
//Setting an NE attribute
SET NE: CLOUDBBID=666;
//Setting USU transport parameters
SET GTRANSPARA: Level=LEVEL2, NETMODE =CENTRALIZED, NodeID=0;
//Turning on the alarm detection switch for interconnection ports
SET CASCADEPORT: CN=0, SRN=0, SN=0, PT=CI-DL, PN=0, SW=ON;
SET CASCADEPORT: CN=0, SRN=0, SN=0, PT=FABRIC, PN=0, SW=ON;
2. To configure basic data for USU 1, run the MML commands listed in 3.3.1.3 Data
Configurations on a First-Level USU. A command example is as follows:
//Setting an NE attribute
SET NE: CLOUDBBID=666;
//Setting USU transport parameters
SET GTRANSPARA: Level=LEVEL1, NETMODE=CENTRALIZED, NodeID=0;
//Adding information about an interconnected NE
ADD INTERCONNE: NENAME="JINQIAO_eNODE1";
//Configuring the working mode of the ports between a first-level USU and a
BBU
SET PORTMODE:CN=0,SRN=0,SN=1,STPN=0,ETPN=24,PM=AUTO;
//Turning on the alarm detection switch for interconnection ports
SET CASCADEPORT: CN=0, SRN=0, SN=0, PT=CI-DL, PN=0, SW=ON;
SET CASCADEPORT: CN=0, SRN=0, SN=0, PT=CI-UL, PN=0, SW=ON;
SET CASCADEPORT: CN=0, SRN=0, SN=0, PT=FABRIC, PN=0, SW=ON;
SET CASCADEPORT: CN=0, SRN=0, SN=0, PT=FABRIC, PN=1, SW=ON;
SET CASCADEPORT: CN=0, SRN=0, SN=0, PT=FABRIC, PN=2, SW=ON;
SET CASCADEPORT: CN=0, SRN=0, SN=0, PT=FABRIC, PN=3, SW=ON;
SET CASCADEPORT: CN=0, SRN=0, SN=1, PT=HEI, PN=0, SW=ON;
//Configuring the IP address for HEI ports on the ULPU
ADD PORTIPPOOL: PORTIPPOOLNO=0, PORTIPBEGIN="192.100.100.1",
PORTIPEND="192.100.100.25", PORTIPMASK="255.255.255.0";
3. To configure basic data for BBU 0, run the MML commands listed in 3.3.1.2 Data
Configurations on an eNodeB. A command example is as follows:
//Specifying a Cloud BB identifier in an eNodeB
SET NE: CLOUDBBID=666;
//Adding an SRIO port
ADD SRIOPORT: CN=0, SRN=0, SN=3, PN=0;
//Configuring the working mode of the ports between a first-level USU and a
BBU
SET PORTMODE:CN=0,SRN=0,SN=3,PN=6,PM=AUTO;
//Turning on the alarm detection switch for interconnection ports
SET CASCADEPORT: CN=0, SRN=0, SN=7, PN=8, SW=ON;
SET CASCADEPORT: CN=0, SRN=0, SN=3, PN=6, SW=ON;
//Adding an Ethernet CI port and allocating an IP address to it
ADD ETHCIPORT:SN=7,SBT=BASE_BOARD;
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";
4. To configure clock synchronization data for USU 0, run the MML commands for
scenario 1 listed in Table 3-11. A command example is as follows:
//Setting the system clock mode
SET CLKSYNCMODE: CLKSYNCMODE=TIME;
//Setting the sharing mode
SET CLOUDSRC: CLOUDSRC=ENABLE;
//Configuring objects to be synchronized when the second-level USU is
configured with the GPS clock source
ADD GPS: GN=0, CN=0, SRN=0, SN=0, CABLE_LEN=0, MODE=GPS, PRI=4;
SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0;
//Configuring objects to be synchronized when the second-level USU provides
the Clock over IP source
ADD IPCLKLINK: LN=0, SN=0, ICPT=PTP, CNM=L2_MULTICAST, DELAYTYPE=E2E,
MACMODE=NO;
SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, SRCNO=0;
5. To configure clock synchronization data for USU 1, run the MML commands for
scenario 3 listed in Table 3-11. A command example is as follows:
//Configuring objects to be synchronized
SET CLKMODE: MODE=FREE;
6. To configure clock synchronization data for BBU 0, run the MML commands for
scenario 3 listed in Table 3-10. A command example is as follows:
//Setting the system clock mode
SET CLKSYNCMODE: CLKSYNCMODE=TIME,SYSCLKSRC=LOCAL;
Remote Observation
Perform remote observation using either of the following methods:
l Run the following MML commands to check whether the USU and eNodeBs work
properly.
Centralize DSP BBPLNKSTAT Both the packet loss rate and link
d Cloud interruption rate are lower than the
BB mode specified thresholds (10-3).
in
interconne
ction
between
BBUs and
a first-
level USU
(SCPRI/
SRIO
ports)
l Measure counters related to SRIO ports (centralized) and resource groups (distributed).
NOTE
l After SRIO ports are configured, performance counters related to these ports for all BBPs
connecting to the USU3910 can be measured.
l If multiple BBPs are configured with SRIO ports, performance counters of each port are
independent.
l When SRIO ports and eX2 interfaces are configured but no eX2 services are ongoing, the
values of the performance counters related to these ports are 0.
6.4.5 Reconfiguration
BBUs can be adjusted by removing and adding BBUs.
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
first-level USU in another Cloud BB network.
BBU 2
UMPT 2
BBP 12
CI interconnection cable 2
Skip this step if Port Mode is set to AUTO. To query the working mode of an HEI port, run the
LST PORTMODE command.
6. Configure the IP addresses for HEI ports on the ULPU in batches or one by one
according to Table 3-5.
7. Run the SET CASCADEPORT command on BBU 2, BBU 3, and the USU to configure
the ports required for interconnection:
a. On BBUs 2 and 3, turn on the alarm detection switch for the CI ports on the UMPT
boards and the HEI ports on the BBP boards. 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-5.
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 BBUs 2 and 3.
----End
l Retain the parameter settings in the ETHPORT MOs for the CI ports. Based on the network plan,
determine whether to modify the device IP addresses (DEVIP MOs) for the CI ports.
l Modify the clock configuration of the BBU accordingly if the BBU performs a different NE function
from that before the adjustment. Otherwise, retain the clock configuration.
Before adjusting configuration data, obtain the devices and cables listed in the following
table.
BBU 3 N/A
USU 2 N/A
UMPT 3 N/A
UEFU 3 N/A
ULPU 1 N/A
When USUs are newly added, Level, Network Mode, and Node ID in the GTRANSPARA MO
must be set to the planned values, and Node ID must be set to a unique value for each USU at the
same level.
2. Configure device- and transmission-related data of new BBUs and USUs by referring to
3.3.1 Basic Data Configurations.
3. Configure clock synchronization-related data of new BBUs and USUs by referring to
3.3.2 Clock Data Configurations.
----End
Before adjusting configuration data, obtain the devices and cables listed in the following
table.
BBU 3 N/A
USU 1 N/A
UMPT 3 N/A
UEFU 1 N/A
ULPU 1 N/A
NOTE
When USUs are newly added, Level, Network Mode, and Node ID in the GTRANSPARA MO
must be set to the planned values, and Node ID must be set to a unique value for each USU at the
same level.
2. Configure device- and transmission-related data of new BBUs and USUs by referring to
3.3.1 Basic Data Configurations.
3. Configure clock synchronization-related data of new BBUs and USUs by referring to
3.3.2 Clock Data Configurations.
----End
Before adjusting configuration data, obtain the devices and cables listed in the following
table.
USU 4 N/A
UEFU 5 N/A
ULPU 3 N/A
NOTE
The two FABRIC interconnection cables which connect the original first-level USU and the UEFU of
the second-level USU which function as a server are changed to connect the original first-level USU and
the UEFU of the second-level USU which does not function as a server, respectively. Four new FABRIC
interconnection cables connect the new first-level USUs and four UEFU boards of the second-level
USUs, respectively. (You are advised to use two FABRIC interconnection cables to connect the new
first-level USUs and the same ports of the second-level USU which functions as a server as those
connect the second-level USU and the original first-level USU before reconfiguration.)
The configuration of the original first-level USU does not need modifying. Ensure that the alarm
detection switch for interconnection ports is turned on and the alarm detection switch for unused
ports is turned off.
----End
Figure 6-7 Cable connection when two second-level USUs work in backup mode
To ensure that the CI interconnection cables between two second-level USUs can form a trunk, a UEFU
connecting to the cable must be installed in slot 0 at each end. If a UEFU board is not in slot 0, adjust
cable connections and the corresponding configuration data.
Turn on the alarm detection switch for the ports connecting to the new and adjusted cables.
Ensure that the alarm detection switch for ports in use is turned on and the alarm detection
switch for unused ports is turned off.
----End
NOTE
For details about how to configure data for newly deployed eNodeBs when second-level USUs work in
backup mode, see USU3910 Initial Configuration Guide.
Before adjusting configuration data, obtain the devices and cables listed in the following
table.
USU 1 N/A
UEFU 1 N/A
ULPU 1 N/A
NOTE
configurations after two BBUs are added. For details about the original hardware
configurations, see Figure 3-6.
BBU 2 N/A
UMPT 2 N/A
4. Run the ADD DEVIP command to configure the IP addresses for the M5/S0 ports on the
UCCU boards or the HEI ports on the UBBPe, UBBPem, or UBBPei boards in BBUs 2
and 3.
5. Run the SET PORTMODE command to set the working mode of the HEI ports on the
ULPU.
Step 4 On the USU, run the ADD INTERCONNE command with the INTERCONNE.NENAME
parameter specified to add names for BBUs 2 and 3.
----End
l Retain the parameter settings for the added UCCU and in the ETHPORT MOs for the added
Ethernet ports. Based on the network plan, determine whether to modify the device IP addresses
(DEVIP MOs) for the Ethernet ports.
l Modify the clock configuration of the BBU accordingly if the BBU performs a different NE function
from that before the adjustment. Otherwise, retain the clock configuration.
BBU 3 N/A
USU 2 N/A
UMPT 3 N/A
UEFU 2 N/A
ULPU 2 N/A
If the UBBPe, UBBPem, or UBBPei is used, connect the HEI port on the UBBPe, UBBPem, or
UBBPei to the HEI port on the ULPU using an HEI interconnection cable for long-distance
connection.
– Use 10GE HEI interconnection cables for long-distance transmission to connect the
M5/S0 ports on the UCCU boards or HEI ports on the UBBPe, UBBPem, or
UBBPei boards in new BBUs to the HEI ports on the ULPU in the new first-level
USU.
– Use HEI interconnection cables (40GE) for long-distance transmission to connect
the HEI ports on the ULPU boards in the new first-level and second-level USUs.
----End
7 Parameters
CASCA PM SET None None Meaning: Indicates the application mode of the port.
DEPOR PORTM The application mode is set based on the actual
T ODE physical networking. Value NULL indicates that a
DSP negotiation is being performed over the port or the
PORTM negotiation is failed.
ODE GUI Value Range: SCPRI/SRIO(SCPRI/SRIO),
LST 1*40GE(1*40GE), 4*10GE(4*10GE), AUTO(AUTO)
PORTM Unit: None
ODE Actual Value Range: SCPRI/SRIO, 1*40GE, 4*10GE,
AUTO
Default Value: AUTO(AUTO)
NE CLOUD SET NE None None Meaning: Indicates the Cloud BB identifier that
BBID LST NE 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.
GUI Value Range: 0~65535
Unit: None
Actual Value Range: 0~65535
Default Value: 0
ETHCIP SBT ADD None None Meaning: Indicates the subboard type of the board
ORT ETHCIP where the Ethernet CI port is located.
ORT GUI Value Range: BASE_BOARD(Base Board)
MOD Unit: None
ETHCIP
ORT Actual Value Range: BASE_BOARD
ETHCIP PN ADD None None Meaning: Indicates the number of the Ethernet CI
ORT ETHCIP port.
ORT GUI Value Range: 0
MOD Unit: None
ETHCIP
ORT Actual Value Range: 0
ETHPO SBT ADD None None Meaning: Indicates the type of sub-board on the board
RT ETHPO where the Ethernet port is located.
RT GUI Value Range: BASE_BOARD(Base Board),
DSP ETH_COVERBOARD(Ethernet Cover Board)
ETHPO Unit: None
RT
Actual Value Range: BASE_BOARD,
RMV ETH_COVERBOARD
ETHPO
RT Default Value: None
RST
ETHPO
RT
SET
ETHPO
RT
LST
ETHPO
RT
ETHPO PN ADD None None Meaning: Indicates the number of the Ethernet port.
RT ETHPO GUI Value Range: 0~5
RT
Unit: None
DSP
ETHPO Actual Value Range: 0~5
RT Default Value: None
RMV
ETHPO
RT
RST
ETHPO
RT
SET
ETHPO
RT
LST
ETHPO
RT
ETHTR SBT ADD None None Meaning: Indicates the type of subboard on the board
K ETHTR where the Ethernet trunk is established.
K GUI Value Range: BASE_BOARD(Base Board),
DSP ETH_COVERBOARD(Ethernet Cover Board)
ETHTR Unit: None
K
Actual Value Range: BASE_BOARD,
MOD ETH_COVERBOARD
ETHTR
K Default Value: None
RMV
ETHTR
K
RST
ETHTR
K
LST
ETHTR
K
ETHTR TN ADD MRFD- Link Meaning: Indicates the number of the Ethernet trunk.
K ETHTR 210103 aggregat When the board is a UTRPc board, the value of this
K ion parameter ranges from 0 to 2. When the board is a
DSP board other than the UTRPc board, the value of this
ETHTR parameter ranges from 0 to 1.
K GUI Value Range: 0~2
MOD Unit: None
ETHTR Actual Value Range: 0~2
K
Default Value: 0
RMV
ETHTR
K
RST
ETHTR
K
LST
ETHTR
K
ETHTR PN ADD MRFD- Link Meaning: Indicates the number of the member port in
KLNK ETHTR 210103 aggregat an Ethernet trunk.
KLNK ion GUI Value Range: 0~5
DSP Unit: None
ETHTR
KLNK Actual Value Range: 0~5
ETHTR FLAG ADD MRFD- Link Meaning: Indicates whether the member port is the
KLNK ETHTR 210103 aggregat primary port of an Ethernet trunk. Each Ethernet trunk
KLNK ion has only one primary port. The primary port must be
LST the first port added to an Ethernet trunk and the last
ETHTR port removed from the Ethernet trunk.
KLNK GUI Value Range: NO(No), YES(Yes)
Unit: None
Actual Value Range: NO, YES
Default Value: None
DEVIP SBT ADD None None Meaning: Indicates the type of sub-board on the board
DEVIP where a port is located.
MOD GUI Value Range: BASE_BOARD(Base Board),
DEVIP E1_COVERBOARD(E1 Cover Board),
RMV BACK_BOARD(Back Board),
DEVIP ETH_COVERBOARD(Ethernet Cover Board)
DSP Unit: None
DEVIP Actual Value Range: BASE_BOARD,
LST E1_COVERBOARD, BACK_BOARD,
DEVIP ETH_COVERBOARD
Default Value: None
DEVIP PT ADD None None Meaning: Indicates the type of the port. The UMTS
DEVIP currently does not support SUBIF.
MOD GUI Value Range: PPP(PPP Link), MPGRP(Multi-
DEVIP link PPP Group), ETH(Ethernet Port),
RMV ETHTRK(Ethernet Trunk), LOOPINT(Loopback
DEVIP Interface), SUBIF(Sub-interface), ETHCI(Ethernet CI
Port)
DSP
DEVIP Unit: None
LST Actual Value Range: PPP, MPGRP, ETH, ETHTRK,
DEVIP LOOPINT, SUBIF, ETHCI
Default Value: None
DSP
DEVIP
LST
DEVIP
DEVIP IP ADD WRFD- IP Meaning: Indicates the IP address configured for the
DEVIP 050402 Transmi port.
MOD WRFD- ssion GUI Value Range: Valid IP address
DEVIP 050411 Introduc
tion on Unit: None
RMV Iub Actual Value Range: Valid IP address
DEVIP Interface Default Value: None
DSP Fraction
DEVIP al IP
DSP Function
MULTI on Iub
CASTIP Interface
LST
DEVIP
CASCA PN DSP None None Meaning: Indicates the number of the port that carries
DEPOR BBPLN the interconnection link.
T KSTAT GUI Value Range: 0~6,8
DSP Unit: None
PORTM
ODE Actual Value Range: 0~6,8
CASCA SW SET None None Meaning: Indicates the enabled/disabled state of the
DEPOR CASCA port. Alarms can be detected and reported through the
T DEPOR port only when the state of the port is ON.
T GUI Value Range: OFF(Off), ON(On)
LST Unit: None
CASCA
DEPOR Actual Value Range: OFF, ON
T Default Value: OFF(Off)
IPCLKL LN ADD WRFD- Clock Meaning: Indicates the number of the IP clock link.
NK IPCLKL 050501 Sync on GUI Value Range: 0~2
INK Ethernet
in Unit: None
DSP
IPCLKL NodeB Actual Value Range: 0~2
INK Default Value: 0
DSP
PRICLA
SS
RMV
IPCLKL
INK
SET
CLASSI
DENTIF
Y
SET
PRICLA
SS
LST
IPCLKL
INK
LST
PRICLA
SS
IPCLKL DEVTY ADD None None Meaning: Indicates the device type of the IP clock.
NK PE IPCLKL The value of this parameter can be OC_SLAVE or
INK OC_MASTER. In OC_SLAVE mode, the NE serves
LST as the clock equipment that is synchronized with the
IPCLKL upstream clock. In OC_MASTER mode, the NE
INK 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.
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 CNM ADD WRFD- Clock Meaning: Indicates the networking type for the IP
NK IPCLKL 050501 Sync on clock. The LTE currently does not support L3
INK Ethernet Multicast function.
LST in GUI Value Range: UNICAST(Unicast),
IPCLKL NodeB L3_MULTICAST(L3 Multicast),
INK L2_MULTICAST(L2 Multicast)
Unit: None
Actual Value Range: UNICAST, L3_MULTICAST,
L2_MULTICAST
Default Value: UNICAST(Unicast)
IPCLKL PROFIL ADD WRFD- Clock Meaning: Indicates the type of protocol supported by
NK ETYPE IPCLKL 050501 Sync on the IEEE 1588 V2-compliant IP clock link, which can
INK Ethernet be ITU-T G.8265.1, IEEE 1588 V2,
LST in IEEE1588V2_16.1, ITU-T G.8275.1 or ITU-T G.
IPCLKL NodeB 8275.2. ITU-T G.8265.1 is defined by the
INK 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.ITU-T G.8275.2 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 L3 unicast. An IP clock link in compliant with
ITU-T G.8275.2 supports interconnection with clock
service devices from other vendors.
GUI Value Range: 1588V2(1588V2), G.8265.1(G.
8265.1), 1588V2_16.1(1588V2_16.1), G.8275.1(G.
8275.1), G.8275.2(G.8275.2)
Unit: None
Actual Value Range: 1588V2, G.8265.1,
1588V2_16.1, G.8275.1, G.8275.2
Default Value: 1588V2(1588V2)
SRIOPO CN ADD None None Meaning: Indicates the cabinet number of the board
RT SRIOPO where the SRIO port is located.
RT GUI Value Range: 0~7
RMV Unit: None
SRIOPO
RT Actual Value Range: 0~7
SRIOPO SRN ADD None None Meaning: Indicates the subrack number of the board
RT SRIOPO where the SRIO port is located.
RT GUI Value Range: 0~1
RMV Unit: None
SRIOPO
RT Actual Value Range: 0~1
SRIOPO SN ADD None None Meaning: Indicates the slot number of the board
RT SRIOPO where the SRIO port is located.
RT GUI Value Range: 0~5
RMV Unit: None
SRIOPO
RT Actual Value Range: 0~5
SRIOPO PN ADD None None Meaning: Indicates the number of the SRIO port.
RT SRIOPO GUI Value Range: 0
RT
Unit: None
RMV
SRIOPO Actual Value Range: 0
RT Default Value: 0
LST
SRIOPO
RT
8 Counters
9 Glossary
10 Reference Documents