When the inter-RRU distance is not greater than 1000 m in urban areas, UL CoMP based on coordinated BBU is recommended because this feature effectively increases the average uplink throughput for inter-BBU cells and CEUs.
l In suburban, rural, and other areas where the inter-RRU distance is large, this feature is not recommended.
l You are advised to optimize parameter settings by referring to the "Parameter Optimization" section to reduce the impact of signaling processing for event A3 measurement reporting in one of the following situations:
– The uplink or downlink PRB usage is greater than 90%.
– The control channel element (CCE) usage is greater than 80%.
– The central processing unit (CPU) usage is greater than 80%.
l If there is intermodulation interference, solve this problem before using this feature.
l If the difference in cell-specific reference signal (CRS) transmit power between macro and micro cells is greater than or equal to 6 dB, it is recommended that macro-micro UL CoMP based on SRS measurement be used.
l When both SFN and UL CoMP are enabled, the start SRS subframe of the SFN cell must be different from those of its neighboring cells (common or SFN cells). The eNodeB can select a neighboring SFN cell to serve as a coordinated cell for a UE only when the UE is allocated SRS resource in the start SRS subframe.
8.2 Required Information
See "Requirements."
NOTE
This feature shares system resources with SFN, CA, and CSPC. Before deploying this feature, contact Huawei engineers for resource audit.
8.3 Planning
RF Planning
N/A
Network Planning
UL CoMP can be performed in cells in the same connection set only when UL CoMP based on coordinated BBU is enabled.
If a BBU3900 is used, an intra-BBU connection set must contain at least one LBBPd or UBBPd installed in slot 2 or 3. If a BBU3910 is used, there is no restriction on an intra-BBU connection set.
If a USU3900 is used, an inter-BBU connection set can contain only cells established on the BBPs with the same slot number. For example, cells established on the BBP in slot 0 of BBU 0 and those established on the BBP in slot 0 of BBU 1 can compose an inter-BBU connection set. If a USU3910 is used, an inter-BBU connection set can contain cells established on the BBPs with different slot numbers.
It is recommended that intra-frequency cells that are served by RRUs installed on the same pole or tower be configured on the same BBP and configured with baseband equipment.
Geographically adjacent intra-frequency cells should be established on the same BBP or the BBPs whose cells compose a connection set and be bound to baseband equipment.
This feature is based on multi-BBU interconnection. For details, see USU3900-based Multi-BBU Interconnection Feature Parameter Description and USU3910-based Multi-Multi-BBU Interconnection Feature Parameter Description.
NOTE
When the BBP is restarted or reset, the cells are reestablished. The deployment information for these cells may change and the coordinated cell lists may also change. These changes will affect the performance of UL CoMP.
Hardware Planning
For details about the requirements for BBP models, see the "Requirements" section.
8.4 Deployment
8.4.1 Requirements
Operating Environment
LOFD-070223 UL CoMP Based on Coordinated BBU requires the following features:
l LOFD-001066 Intra-eNodeB UL CoMP
l LOFD-070222 Intra-eNodeB UL CoMP Phase II.
LOFD-070223 UL CoMP Based on Coordinated BBU takes effect only when this feature and all its prerequisite features are enabled.
The following table describes the requirements for the operating environment.
Table 8-1 Requirements for the operating environment Information
to Be Collected
Requirements
Networking Multi-BBU interconnection eNodeB type Macro eNodeBs
RRU model Macro-micro and micro-micro UL CoMP allows micro cells to be LPNs, for example, RRU3220E.
BBP model LBBPd2, LBBPd3, UBBPd3, UBBPd4, UBBPd5, or UBBPd6
Number of cells UL CoMP requires at least two intra-frequency cells in a connection set.
If UL CoMP is enabled in only one cell, it will not take effect.
Cell
configuration
l UL CoMP can be performed in inter-BBU inter-BBP cells. The serving cell and coordinated cells must be configured in the same connection set. For details, see 8.3 Planning.
l Inter-BBU cells that are geographically adjacent must be configured as intra-frequency neighboring cells with different PCIs.
l The cells involved in UL CoMP must have the same frequency, bandwidth, and CP type. These cells can be all in 1R, 2R, or 4R mode; or some in 1R mode and the others in 2R mode.
l An LBBPd2, LBBPd3, UBBPd4, or UBBPd5 can be used to support three 2R or 4R cells each with a bandwidth of 20, 15, 10, 5, 3, or 1.4 MHz.
l An LBBPd3 can be used to support six 2R or 4R cells each with a bandwidth of 20, 15, 10, 5, 3, or 1.4 MHz.
l A UBBPd3 can be used to support three 2R cells each with a bandwidth of 20, 15, 10, 5, 3, or 1.4 MHz.
l A UBBPd5 or UBBPd6 can be used to support six 2R or 4R cells each with a bandwidth of 20, 15, 10, 5, 3, or 1.4 MHz.
l The cells can be set up on different models of LBBP, UBBP, or both.
l An LBBPd2, LBBPd3, UBBPd3, UBBPd4, UBBPd5, or UBBPd6 can be used to support 1R or 1R+2R UL CoMP.
l To support inter-BBU UL CoMP, the Cell.eNodeBId parameter values of inter-BBU cells cannot be the same.
NOTE
4R UL CoMP can be performed in only two cells. It requires that the UE be a type-1 UE, the modulation scheme be QPSK or 16QAM, and the networking mode be any Cloud BB mode other than distributed Cloud BB.
Information
It is recommended that UL CoMP be used only when the distance between the RRUs of the serving cell and coordinated cells is not greater than 1000 m.
NOTE
The CellAlgoSwitch.UlJRAntNumCombSw parameter settings of the serving cell and coordinated cells must be matched. For example, to enable 1R+2R UL CoMP, turn on the Ul1R2RJRSwitch for both 1R and 2R cells. Note that 2R UL CoMP and 4R UL CoMP are supported by default, without additional parameter settings.
Transmission Networking
Time synchronization with a deviation less than 1.5 μs must be achieved between BBUs. (You can use a a GPS clock to implement time synchronization. For details, see Synchronization Feature Parameter Description.) When clock quality does not meet the requirement,
LOFD-070223 UL CoMP Based on Coordinated BBU is automatically disabled. When clock quality meets the requirement, this feature is automatically enabled.
LOFD-070223 UL CoMP Based on Coordinated BBU requires that inter-BBU routes be planned. If BBUs are to be connected through USU3910, eX2 interfaces must be configured between BBUs. For details, see eX2 Self-Management Feature Parameter Description.
License
The operator has purchased and activated the license for the feature listed in the following table.
Feature
ID Feature Name Model License
Control Item NE Sales Unit LOFD-07
0223
UL CoMP based on Coordinated BBU
LT1SULC BCB00
UL CoMP based on Coordinated BBU(FDD)
eNode B
per eNodeB
The number of eNodeBs that can use LOFD-070223 UL CoMP Based on Coordinated BBU is subject to the licensed number. If the number of eNodeBs is greater than the licensed number, only the licensed number of eNodeBs can use this feature.
To deploy LOFD-070223 UL CoMP Based on Coordinated BBU, the licenses for
LOFD-001066 Intra-eNodeB UL CoMP and LOFD-070222 Intra-eNodeB UL CoMP Phase II must be purchased and activated.
Other Features
For details, see 4.4 Features Related to LOFD-070223 UL CoMP based on Coordinated BBU.
8.4.2 Data Preparation
This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature deployment scenario.
There are three types of data sources:
l Network plan (negotiation not required): parameter values planned and set by the operator
l Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users
Required Data
The following table describes the parameters that must be set in a BaseBandEqm MO to configure baseband equipment information.
It is recommended that intra-frequency cells that are served by RRUs installed on the same pole or tower be configured on the same BBP, and intra-frequency cells that are
geographically adjacent but served by RRUs installed on different poles or towers be configured in the same connection set. For details, see 8.3 Planning.
Table 8-2 Parameters related to baseband equipment
Parameter Name Parameter ID Data Source Setting Notes Baseband
Set this parameter to ULDL.
Set this parameter to NULL.
Cabinet No. of Process Unit n
CNn Network plan
(negotiation not required)
n indicates the cabinet number of the BBP, ranging from 0 to 7.
Subrack No. of Process Unit n
SRNn Network plan
(negotiation not required)
n indicates the subrack number of the BBP, ranging from 0 to 1.
Slot No. of Process Unit n
SNn Network plan
(negotiation not required)
n indicates the slot number of the BBP, ranging from 0 to 5.
The following table describes the parameters that must be set in an eUCellSectorEqm MO to configure a set of sector equipment for a cell.
It is recommended that intra-frequency cells that are served by RRUs installed on the same pole or tower be configured on the same BBP.
Table 8-3 Parameters related to sector equipment for a cell
Parameter Name Parameter ID Data Source Setting Notes Local cell ID eUCellSectorEqm.
LocalCellId
Network plan (negotiation not required)
None
Sector equipment ID eUCellSectorEqm.
SectorEqmId
Network plan (negotiation not required)
None
Reference signal power
eUCellSectorEqm.
ReferenceSignalPw r
Network plan (negotiation not required)
None
Baseband equipment ID
eUCellSectorEqm.
BaseBandEqmId
Network plan (negotiation not required)
None
Scenario-specific Data
In addition to required data, scenario-specific data also needs to be configured.
1. The following table describes the parameters that must be set in the CellAlgoSwitch and ENodeBAlgoSwitch MOs to configure UL CoMP based on coordinated BBU.
Paramete
r Name Parameter
ID Data
Source Setting Notes UplinkCo
This parameter specifies whether to enable UL CoMP for a cell.
Default value: Additional setting notes for macro-micro scenarios:
(when the difference in CRS transmit power between macro and micro cells is greater than or equal to 6 dB and the micro cell is a common cell) OverBBU
This parameter specifies whether to enable UL CoMP based on coordinated BBU.
Inter-BBU UL CoMP is enabled when UlJointReceptionSwitch,
UlJointReceptionPhaseIISwitch, and UlJointReceptionOverBBUsSwitch are all turned on.
Default value: UlJointReceptionO-verBBUsSwitch:Off
Recommended value: UlJointReceptio-nOverBBUsSwitch:On
2. The following table describes the parameter that must be set in the CellAlgoSwitch MO to configure an IRC switch.
Paramete
r Name Parameter
ID Data
Source Setting Notes PUSCH
This parameter specifies a PUSCH IRC algorithm.
The MrcIrcAdptSwitch option specifies whether to enable adaptive switching between MRC and IRC:
l Default value:
MrcIrcAdptSwitch:On l Recommended value:
MrcIrcAdptSwitch:On
3. The following table describes the parameter that must be set in a CellUlCompAlgo MO to configure a UL CoMP A3 offset.
Parameter
Name Parameter
ID Data
Source Setting Notes UlCompA3
This parameter specifies a UL CoMP A3 offset. The value range is from -30 to +30, with a unit of 0.5 dB.
Default value: -20.
Recommended value: -20
4. The following table describes the parameter that must be set in a CellAlgoSwitch MO to configure a combination of cell RX modes.
Parameter
Name Parameter
ID Data
Source Setting Notes UL JR
This parameter specifies a combination of receive modes for UL CoMP.
Default value:
2R UL CoMP and 4R UL CoMP are supported by default after the UL CoMP switch is turned on.
8.4.3 Precautions
It is recommended that intra-frequency cells that are served by RRUs installed on the same pole or tower be configured on the same BBP, and intra-frequency cells that are
geographically adjacent but served by RRUs installed on different poles or towers be configured in the same connection set. For details, see 8.3 Planning.
8.4.4 Hardware Adjustment
It is recommended that UL CoMP be used only when the distance between the RRUs of the serving cell and coordinated cells is not greater than 1000 m.
For details about USU installation, see USU3900 Installation Guide and USU3910 Installation Guide.
8.4.5 Activation
8.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in the following table 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 CME for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB product documentation.
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 the following table 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 the following table 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 8-4 Parameters related to activation of this feature
MO Sheet in the
Summary Data File Parameter Group Remarks CellUlCompAl
go
eNodeB Radio Data LocalCellId, UlCompA3Offset
For parameter setting notes, see 8.4.2 Data Preparation.
CellAlgoSwitc h
eNodeB Radio Data LocalCellId,
UplinkCompSwitch, PuschIrcAlgoSwitch, UlJRAntNumCombSw ENodeBAlgoS
witch
eNodeB Radio Data OverBBUsSwitch
8.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs
Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows:
Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press F1 when a CME window is active, and select Managing the CME > CME Guidelines >
LTE Application Management > eNodeB Related Operations > Customizing a Summary Data File for Batch eNodeB Configuration.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Export Data >
Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Import Data >
Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification.
Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. For detailed operations, see Managing the CME > CME Guidelines > Script File Management
> Exporting Incremental Scripts from a Planned Data Area in the CME online help.
----End
8.4.5.3 Using the CME to Perform Single Configuration
On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.
Step 2 In area 1 shown in Figure 8-1, select the eNodeB to which the MOs belong.
Figure 8-1 MO search and configuration window
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts.
----End
8.4.5.4 Using MML Commands MML Commands
Step 1 Run the MOD CELLULCOMPALGO command to set a UL CoMP A3 offset.
MOD CELLULCOMPALGO: LocalCellId=0, UlCompA3Offset=-20;
NOTE
The default value is recommended.
Step 2 To activate inter-BBU 2-cell UL CoMP for LOFD-070223 UL CoMP Based on Coordinated BBU, run the MOD CELLALGOSWITCH command to turn on the
UIJointReceptionSwitch and UlJointReceptionPhaseIISwitch, and then run the MOD ENODEBALGOSWITCH command to turn on the UlJointReceptionOverBBUsSwitch for each cell involved.
l Macro-macro or micro-micro 2-cell UL CoMP
MOD CELLALGOSWITCH: LocalCellId=0,
UplinkCompSwitch=UlJointReceptionSwitch-1&UlJointReceptionPhaseIISwitch-1;
MOD ENODEBALGOSWITCH: OverBBUsSwitch=UlJointReceptionOverBBUsSwitch-1;
l Macro-micro 2-cell UL CoMP
To activate macro-micro UL CoMP, run the MOD CELLALGOSWITCH command to set the UlHetnetJointReceptionSwitch, UlHetnetCompOnUlRsrpSw, and
UlHetnetCompManualNcellCfgSw for all macro and micro cells involved.
When the difference in CRS transmit power between macro and micro cells is less than 6 dB or the micro cell is an SFN cell, run the following command:
MOD CELLALGOSWITCH: LocalCellId=0,
UplinkCompSwitch=UlJointReceptionSwitch-1&UlJointReceptionPhaseIISwitch-1&UlHetnet JointReceptionSwitch-1&UlHetnetCompManualNcellCfgSw-0;
MOD ENODEBALGOSWITCH: OverBBUsSwitch=UlJointReceptionOverBBUsSwitch-1;
When the difference in CRS transmit power between macro and micro cells is greater than or equal to 6 dB and the micro cell is a common cell, run the following command:
MOD CELLALGOSWITCH: LocalCellId=0,
UplinkCompSwitch=UlJointReceptionSwitch-1&UlJointReceptionPhaseIISwitch-1&UlHetnet JointReceptionSwitch-1&UlHetnetCompManualNcellCfgSw-0&UlHetnetCompOnUlRsrpSw-1;
MOD ENODEBALGOSWITCH: OverBBUsSwitch=UlJointReceptionOverBBUsSwitch-1;
To enable manual configuration of to-be measured neighboring cells in macro-micro scenarios when the UlHetnetCompOnUlRsrpSw switch is on, run the MOD CELLALGOSWITCH command to turn on the corresponding switch and run the MOD
EUTRANINTRAFREQNCELL command to set the relationships between intra-frequency macro and micro cells.
MOD CELLALGOSWITCH: LocalCellId=0,
UplinkCompSwitch=UlHetnetCompManualNcellCfgSw-1;
MOD EUTRANINTRAFREQNCELL: LocalCellId=0, Mcc="510", Mnc="990", eNodeBId=20043, CellId=2, AttachCellSwitch=ON;
Step 3 To activate inter-BBU 3-cell UL CoMP for LOFD-070223 UL CoMP Based on Coordinated BBU, run the MOD CELLALGOSWITCH command to turn on the
UlJointReceptionSwitch, UlJointReceptionPhaseIISwitch, and
UlJointReception3CellSwitch. Then, run the MOD ENODEBALGOSWITCH command to turn on the UlJointReceptionOverBBUsSwitch for each cell involved.
l Macro-macro or micro-micro 3-cell UL CoMP
MOD CELLALGOSWITCH: LocalCellId=0,
UplinkCompSwitch=UlJointReceptionSwitch-1&UlJointReceptionPhaseIISwitch-1&UlJointR eception3CellSwitch-1;
MOD ENODEBALGOSWITCH: OverBBUsSwitch=UlJointReceptionOverBBUsSwitch-1;
l Macro-micro 3-cell UL CoMP
To activate macro-micro UL CoMP, run the MOD CELLALGOSWITCH command to set the UlHetnetJointReceptionSwitch, UlHetnetCompOnUlRsrpSw, and
UlHetnetCompManualNcellCfgSw for all macro and micro cells involved.
When the difference in CRS transmit power between macro and micro cells is less than 6 dB or the micro cell is an SFN cell, run the following command:
MOD CELLALGOSWITCH: LocalCellId=0,
UplinkCompSwitch=UlJointReceptionSwitch-1&UlJointReceptionPhaseIISwitch-1&UlJointR eception3CellSwitch-1&UlHetnetJointReceptionSwitch-1&UlHetnetCompManualNcellCfgSw-0;
MOD ENODEBALGOSWITCH: OverBBUsSwitch=UlJointReceptionOverBBUsSwitch-1;
When the difference in CRS transmit power between macro and micro cells is greater than or equal to 6 dB and the micro cell is a common cell, run the following command:
MOD CELLALGOSWITCH: LocalCellId=0,
UplinkCompSwitch=UlJointReceptionSwitch-1&UlJointReceptionPhaseIISwitch-1&UlJointR eception3CellSwitch-1&UlHetnetJointReceptionSwitch-1&UlHetnetCompManualNcellCfgSw-0&UlHetnetCompOnUlRsrpSw-1;
MOD ENODEBALGOSWITCH: OverBBUsSwitch=UlJointReceptionOverBBUsSwitch-1;
MOD ENODEBALGOSWITCH: OverBBUsSwitch=UlJointReceptionOverBBUsSwitch-1;