6.4 Deployment
6.4.1 Process
Figure 6-1 shows the process for deploying the multi-BBU interconnection feature.
Figure 6-1 Process
NOTE
The data preparation in this document only involves adjusting the configurations associated with interconnection between the BBU and USU in the preceding figure. As for other steps:
l For details about eNodeB and USU3910 installation, see 3900 Series Base Station Installation Guide
Hardware
Table 6-1 describes the configuration restrictions of boards in the BBU.
Table 6-1 Board configuration restrictions Networ
king Type of the Base Station Connecting to the USU
Main Control Board/BBP UCCU
Centrali zed Cloud BB
With one BBU l The main control board that directly connects to the USU must be a UMPT, including UMPTa1/UMPTa2/UMPTa6 and UMPTb1/
UMPTb2.
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 applies only to the following
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 the Base Station Connecting to the USU
Main Control Board/BBP UCCU
Either of the preceding types
When the base station is connected with a USU, 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
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.
The principles that whether a USU occupies a license are as follows:
NodeID parameter is set to 0. Otherwise, no license is occupied.
n In distributed Cloud BB mode:
For a first-level USU, a license is occupied if the HEI interconnection cable is used to connect it and a BBU.
For a second-level USU, a license is occupied if the HEI interconnection cable is used to connect it and a first-level USU.
– The license listed in the following table is required.
License BOM
Code Model License Control
Item NE Sales
Unit 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 Feature
Name Model License
Control
– LTE TDD eNodeBs in centralized Cloud BB mode Featur
e ID Feature
Name License
Featur
e ID Feature
Name License
– LTE TDD eNodeBs in distributed Cloud BB mode Featur
e ID Feature
Name License
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
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
Port No. ETHPORT.PN l For a BBU, set this parameter 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
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 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
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
Port No. DEVIP.PN l For the UMPT
in a BBU, set
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
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 Data Source Link No. IPCLKLNK.L
N(N/A,LTE FDD eNodeB)
l For an eNodeB:
–When the DEVTYPE parameter is set to OC_SLAVE, set the LN parameter to 0 or 1.
–When the DEVTYPE parameter is set to OC_MASTER, set the LN parameter to 2.
l For a USU:
–When the DEVTYPE parameter is set to
OC_MASTER or BC, set the LN parameter to 2.
–When the DEVTYPE parameter is set to OC_SLAVE, set the LN parameter to 0 or 1.
Network plan (negotiation not
required)
er Name Source
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
Set this parameter to L2_MULTICAST.
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 Parameter
ID Setting Notes Data
Source
Set this parameter to MANUAL. Network plan (negotiati on not required)
Parameter
Name Parameter
ID Setting Notes Data
Source
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
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
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 Paramete
r ID Setting Notes Data
Source Interconnectio
n Clock No.
InterClk.
LN
Set this parameter to 0. Network plan
l Set this parameter to the priority of the clock source on an eNodeB receiving clock signals. The value ranges from 1 to 4. The default value is 4, which indicates the lowest priority.
l If the TASM.MODE parameter is set to AUTO(Auto), the eNodeB selects the clock source with the highest priority.
l Configuration data dedicated to USUs
– The following table describes the parameter that must be set in the INTERCONNE MO to specify NE names.
Parameter
Name Parameter ID Setting Notes Data
Source Network Element
Name
INTERCONNE.
NENAME
Set this parameter to the name of an eNodeB connecting to a USU.
Network plan (negotiatio
– The following table describes the parameters that must be set in the GTRANSPARA MO to configure global transmission parameters.
Parameter
Name Parameter ID Setting Notes Data
Source
Level GTRANSPARA.
LEVEL
Set this parameter to LEVEL1(LEVEL1) or Network Mode GTRANSPARA.
NETMODE
Set this parameter to CENTRALIZED(CEN
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 Data
Source IP Address PORTIP.IP Set this parameter for an
HEI port working in SCPRI/SRIO mode on the ULPU in a USU as Mask PORTIP.MASK Set this parameter as
required.
Network plan (negotiatio
Parameter
Name Parameter ID Setting Notes Data
Source
Port Mode PORTMODE.P
M
l In centralized Cloud BB mode, set this parameter to SCPRI/
SRIO(SCPRI/
SRIO).
l In distributed Cloud BB mode:
– For an HEI port connecting to an eNodeB, set this parameter to 4*10GE(4*10GE ).
– For an HEI port connecting to the second-level USU, set this parameter to 1*40GE(1*40GE ).
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.
Table 6-2 Multi-BBU interconnection parameters on eNodeBs MO Sheet in the Summary
Data File Parameter Group Remarks
NE User-defined sheet Cloud BB Identifier This
parameter
User-defined sheet Port No., Switch These parameters must be customized in the template.
DEVIP User-defined sheet Subboard Type, Port Type, Port No., IP Address
ETHCIPORT User-defined sheet Port No., Subboard Type These parameters must be customized in the template.
IPCLKLINK User-defined sheet Link No., Device Type, Clock Net Mode, Profile Type
INTERCLK User-defined sheet Interconnection Clock No., Priority
TASM User-defined sheet Clock Working Mode, Selected Clock Source, Cloud BB Clock
These parameters must be
MO Sheet in the Summary
Data File Parameter Group Remarks
NE User-defined sheet Cloud BB Identifier This
parameter
User-defined sheet Port No., Switch These parameters must be customized in the template.
DEVIP User-defined sheet Subboard Type, Port Type, Port No., IP Address
These
ETHCIPORT User-defined sheet Port No., Subboard Type These parameters must be customized in the template.
IPCLKLINK User-defined sheet Link No., Device Type, Clock Net Mode, Profile Type
INTERCLK User-defined sheet Interconnection Clock No., Priority
TASM User-defined sheet Clock Working Mode, Selected Clock Source, Cloud BB Clock Reference Source Flag, Clock Synchronization
MO Sheet in the Summary
Data File Parameter Group Remarks
GTRANSPARA User-defined sheet Level, Network Mode, Node ID
These parameters must be customized in the template.
PORTIP User-defined sheet IP Address, Mask These
parameters must be customized in the template.
PORTMODE User-defined sheet Port Mode This
parameter must be customized in the template.
INTERCONNE User-defined sheet Network Element Name This parameter must be customized in the template.
Using MML Commands
Step 1 Configure the Could BB ID, NE working mode, and port working mode. For details, see 3.3.1 Basic Data Configurations.
Step 2 Run the SET CASCADEPORT command on each BBU and USU to configure the ports required for interconnection.
NOTE
Alarms generated on an interconnection port can be reported only after the alarm detection switch is turned on. Turn on the switch for an interconnection port only when you need to use this interconnection port. To query the number of an interconnection port, run the LST CASCADEPORT command. The number of the CI port on the UMPT is 8, and the number of the HEI port on an LBBPd or a UBBPd is 6.
Step 3 Configure the clock source.
NOTE
c. On each eNodeB, run the SET CLKMODE command with Selected Clock Source set to GPS(GPS Clock) or IPCLK(IP Clock).
d. On each eNodeB, run the SET CLKSYNCMODE command with Clock Synchronization Mode set to TIME(TIME).
l Clock synchronization solution 2
a. Determine the USU configuration scenario according to 3.3.2.2 Clock Synchronization Solution 2 and configure the USUs based on the key configuration data.
b. Determine the BBU configuration scenario according to 3.3.2.2 Clock Synchronization Solution 2 and configure the BBUs based on the key configuration data.
----End
6.4.4 MML Command Examples
This section provides the examples of MML commands related to transmission and clock synchronization between USU0, USU1, and BBU0 circled by dashed lines in Figure 6-2.
Figure 6-2 Clock synchronization solution when a USU provides a clock source for time synchronization
NOTE
l The parameter settings in the following commands are used for reference only. Set the parameters based on network requirements.
l In these examples, the BBU and USUs are connected in centralized Cloud BB mode.
l For the MML command examples related to USU initial configuration, see the following section in USU3910 Initial Configuration Guide: Initially Configuring a USU (Using the MML Commands) >
Typical Configuration Example
1. To configure USU0 basic data, run the related MML commands listed in Table 3-5.
2. To configure USU1 basic data, run the related MML commands listed in Table 3-3.
3. To configure BBU0 basic data, run the related MML commands listed in Table 3-1.
4. To configure USU0 clock synchronization data, run the related MML commands for scenario 1 listed in Table 3-9.
5. To configure USU1 clock synchronization data, run the related MML commands for scenario 3 listed in Table 3-9.
6. To configure BBU0 clock synchronization data, run the related MML commands for scenario 3 listed in Table 3-8.
6.4.5 Activation Observation
Local Observation
Table 6-4 describes the method for local observation.
Table 6-4 Local observation
NE Board Port Expected Result
USU UEFU CI-DL port Steady green, indicating that the
connection between a USU and a lower-level NE is normal.
FABRIC port Steady green, indicating that the user-plane connection between a first-level USU and a second-level USU is normal.
CI-UL port Steady green, indicating that the control-plane connection between a first-level USU and a second-level USU is normal.
ULPU HEI port Steady green, indicating that the
connection between a USU and a peer NE is normal.
eNodeB UMPT CI port Steady green, indicating that the control-plane (over the CI-DL port) connection between a BBU and USU is normal.
UCCU M5/S0 port Steady green, indicating that the Ethernet link between a BBU and an HEI port on a USU is normal.
Remote Observation
l Run the following MML commands to check whether the USU and eNodeBs are working properly.
NE MML Command Expected Result
USU DSP
INTERCONTOPO
The command output is the same as planned.
DSP CLKSTAT l When the USU provides a clock source or forwards clock signals for time synchronization, the values of PLL Status and Clock Synchronization Mode in the command output are Locked and TIME, respectively.
l When the USU forwards clock signals or the USU clock works in free-run mode, the value of PLL Status in the command output is Free running.
DSP CTRLLNKSTAT Both the packet loss rate and packet error rate on the link are lower than the specified thresholds (10-3).
DSP BBPLNKSTAT Both the packet loss rate and link
interruption rate are lower than the specified thresholds (10-3).
DSP CXP The value of Port Receive Status in the command output is Up.
DSP PORTIP The value of IP Address in the command output is not null.
DSP ETHPORT In the command output, if the values of both Port Status and Physical Layer Status are Up and the value of Local Speed is 10G or 40G.
eNodeB DSP
INTERCONTOPO
The topology between the BBU and USU is the same as planned.
DSP CLKSTAT In the command output, the value of PLL
NE MML Command Expected Result
DSP ETHCIPORT The value of Port Status in the command output is Up.
DSP BBPLNK The value of SRIO Line Bit Rate(Gbit/s) in
DSP BBPLNK The value of SRIO Line Bit Rate(Gbit/s) in