Uplink Coordinated Scheduling (ERAN18.1 - 01)
Uplink Coordinated Scheduling (ERAN18.1 - 01)
Issue 01
Date 2022-03-08
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: https://www.huawei.com
Email: support@huawei.com
Contents
1 Change History.........................................................................................................................1
1.1 eRAN18.1 01 (2022-03-08)..................................................................................................................................................1
1.2 eRAN18.1 Draft B (2022-02-08)........................................................................................................................................ 1
1.3 eRAN18.1 Draft A (2021-12-30)........................................................................................................................................ 1
3 Overview....................................................................................................................................5
4 UL CRA (FDD)........................................................................................................................... 6
4.1 Principles.................................................................................................................................................................................... 6
4.2 Network Analysis..................................................................................................................................................................... 8
4.2.1 Benefits.................................................................................................................................................................................... 8
4.2.2 Impacts.................................................................................................................................................................................... 9
4.3 Requirements......................................................................................................................................................................... 11
4.3.1 Licenses................................................................................................................................................................................. 11
4.3.2 Software................................................................................................................................................................................11
4.3.3 Hardware.............................................................................................................................................................................. 13
4.3.4 Cells........................................................................................................................................................................................ 14
4.3.5 Others.................................................................................................................................................................................... 14
4.4 Operation and Maintenance............................................................................................................................................. 14
4.4.1 Data Configuration........................................................................................................................................................... 15
4.4.1.1 Data Preparation............................................................................................................................................................ 15
4.4.1.2 Using MML Commands............................................................................................................................................... 16
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 16
4.4.2 Activation Verification..................................................................................................................................................... 17
4.4.3 Network Monitoring......................................................................................................................................................... 17
5 UL CPC (FDD)......................................................................................................................... 18
5.1 Principles.................................................................................................................................................................................. 18
5.2 Network Analysis.................................................................................................................................................................. 21
5.2.1 Benefits................................................................................................................................................................................. 21
5.2.2 Impacts.................................................................................................................................................................................. 22
5.3 Requirements......................................................................................................................................................................... 24
5.3.1 Licenses................................................................................................................................................................................. 24
5.3.2 Software................................................................................................................................................................................25
5.3.3 Hardware.............................................................................................................................................................................. 26
5.3.4 Cells........................................................................................................................................................................................ 27
5.3.5 Others.................................................................................................................................................................................... 27
5.4 Operation and Maintenance............................................................................................................................................. 27
5.4.1 Data Configuration........................................................................................................................................................... 27
5.4.1.1 Data Preparation............................................................................................................................................................ 27
5.4.1.2 Using MML Commands............................................................................................................................................... 28
5.4.1.3 Using the MAE-Deployment...................................................................................................................................... 29
5.4.2 Activation Verification..................................................................................................................................................... 29
5.4.3 Network Monitoring......................................................................................................................................................... 29
6 Parameters.............................................................................................................................. 31
7 Counters.................................................................................................................................. 32
8 Glossary................................................................................................................................... 33
9 Reference Documents...........................................................................................................34
1 Change History
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
Changed the function name "uplink coverage boost" to "uplink full-antenna
reception". For details, see 4.3.2 Software.
Technical Changes
Change Description Parameter Change RAT Base Station
Model
Editorial Changes
Revised descriptions in this document.
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve optimal gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this
document apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
3 Overview
4 UL CRA (FDD)
4.1 Principles
To use UL CRA for it to yield expected gains, the operator must first turn on the
UL CRA switch for all intra-frequency same-bandwidth cells in a planned area. This
minimizes the number of border cells. There are two terms of special relevance to
UL CRA as follows:
● Border cell
A border cell is a cell with an excessively high proportion of neighboring cells
where UL CRA is not in effect in a UL CRA cluster.
● UL CRA cluster
A UL CRA cluster of a cell is the set of all the neighboring cells cooperating
for UL CRA.
When the UL_COORD_RES_ALLOC_SWITCH option of the UlCsAlgoPara.UlCsSw
parameter is selected, UL CRA is enabled, and the UL CRA procedure is performed,
as shown in Figure 4-1.
1. The eNodeB determines which cells will be in the UL CRA cluster of the local
cell.
The eNodeB selects cells that meet all of the following conditions:
– The UL CRA switch is on.
– The cells operate on the same frequency and have the same bandwidth
as the local cell.
– The cells are not high-speed cells (cells configured for UEs moving at
high speed).
– The cells are deployed on non-LBBPc baseband processing units (BBPs).
– The cells are served by the same type of base stations as the local cell.
For example, if both the local cell and neighboring cells are served by
macro base stations, they are of the same type.
– The cells are included in event A3 reports generated for UL CRA by UEs of
the local cell.
Except for the UlCsAlgoPara.UlCsA3Offset parameter, event A3 for UL
CRA uses the same A3 parameters as those of event A3 for UL CoMP.
The eNodeB arranges the cells in descending order based on the differences
between their RSRP values and that of the local cell and selects cells to
generate the UL CRA cluster.
2. The eNodeB determines whether the CPU usage of its main control board has
reached the flow control threshold.
– If it has, the eNodeB disables UL CRA and uses the basic scheduling
policy to allocate resources. For details about resource allocation
principles, see Scheduling.
4.2.1 Benefits
UL CRA decreases the interference of high-interference UEs to neighboring cells. It
increases the average uplink user throughput and edge-user throughput by up to
5% and 30% respectively when the following conditions are met:
● The average uplink interference and noise (IN) is more than –110 dBm.
● The PUSCH resource block (RB) usage is more than 10%.
● There are fewer than 200 uplink-synchronized UEs.
● Inter-site distance
A larger distance results in less interference and lower gains. In general, the
average inter-site distance tends to be less than 500 m.
● Amount of uncontrollable interference
If there is strong uncontrollable interference, better resource allocation will be
unable to eliminate interference, so UL CRA will not yield gains in such
scenarios. Generally, the uncontrollable interference should be less than –115
dBm. Uncontrollable interference includes:
– Inter-RAT interference
– Interference generated by repeaters
– Interference from cells where UL CRA is not in effect
– Intermodulation interference
– Intra-RAT adjacent-channel interference such as that caused by a Double
Deck cell group described in Flexible Bandwidth based on Overlap
Carriers Feature Parameter Description
● Physical cell identifier (PCI)
When the UlCsAlgoPara.UlCoResAllocBandMode parameter is set to
INVALID, the eNodeB adaptively selects a service-protecting band mode to
determine the positions of service-protecting bands. When this setting is used,
UL CRA is less likely to be effective and UL CRA gains will be lower if the PCI
modulo 3 results of the local cell and its neighboring cells are more likely to
conflict.
4.2.2 Impacts
Network Impacts
● The gains in the throughput calculated using (L.Thrp.bits.UL –
L.Thrp.bits.UE.UL.LastTTI)/L.Thrp.Time.UE.UL.RmvLastTTI may be negative
when the average uplink IN is greater than –110 dBm, the average uplink
MCS index is greater than 15, and the uplink residual block error rate (RBLER)
is high.
● UL CRA relies on A3 reporting, and therefore there are the following
additional impacts:
– New A3 reports increase the signaling processing overhead. The value of
L.Signal.Num.Uu will go up and the CPU usage of the main control
board will increase by less than 5%.
– User-plane resources will be preempted for A3 reporting. If the uplink and
downlink RBs and control channel elements (CCEs) are insufficient, the
Cell Downlink Average Throughput value will drop by less than 5% and
the downlink packet delay will increase by less than 5%.
Therefore, UL CRA is not recommended under any of the following conditions:
– The downlink PRB usage is over 90%.
– The uplink PRB usage is over 90%.
– The CCE usage is more than 80%.
– The CPU usage is more than 80%.
● In relaxed backhaul scenarios, when UL CRA and other features involving the
coordination of multiple eNodeBs (such as UL CoMP and CA) are enabled
Function Impacts
Function Function Switch Reference Description
Name
4.3 Requirements
4.3.1 Licenses
Feature ID Feature Name Model Sales Unit
4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
None
4.3.3 Hardware
Boards
Non-LBBPc BBPs
RF Modules
No requirements
4.3.4 Cells
● The cell bandwidth is greater than or equal to 5 MHz.
● The RX mode of the antenna is 1R, 2R, or 4R.
● eNodeBs providing the cells in a cluster are all macro eNodeBs, micro
eNodeBs, or LampSite eNodeBs.
● An X2 interface that supports coordination-based services in non-ideal
backhaul scenarios, or an eX2 interface, is available.
The one-way delay for the interface must be less than 50 ms. For details
about X2 interface support for coordination-based services in non-ideal
backhaul scenarios, see S1 and X2 Self-Management.
In addition, IP Performance Monitor (PM) sessions of forward activation type
are recommended for delay detection.
Configuring an IP PM session of bidirectional activation at either end of an
eX2 interface needs to be avoided. This is because eNodeBs automatically
create IP PM sessions to detect eX2 link status. An IP PM session of
bidirectional activation type may conflict with an automatically created
session. If this is the case, the eX2 interface will fail to work properly.
● There are no PCI conflicts.
PCI conflicts can occur when two involved cells have the same PCI. If there is
a PCI conflict, the eNodeB may incorrectly select a cell in the UL CRA cluster
because it cannot differentiate between the two cells based on the
measurement reports from the UE. You are advised to set the
ENodeBAlgoSwitch.PciConflictAlmSwitch parameter to ON so that PCI
conflicts can be reported.
● There is no intermodulation interference.
If there is intermodulation interference, the eNodeB cannot eliminate the
interference or prevent its impact by using resource coordination.
4.3.5 Others
No requirements
The eNodeB obtains the average load information of the local cell and
cooperating neighboring cells according to the information exchanged in the
coordinated set and then determines the interference control resource allocation
policy.
//Setting UlCoResAllocBandMode and UlCoResAllocRbLoadThld
MOD ULCSALGOPARA: LocalCellId=0, UlCoResAllocBandMode=INVALID, UlCoResAllocRbLoadThld=40;
5 UL CPC (FDD)
5.1 Principles
To use UL CPC for it to yield expected gains, the operator must first turn on the UL
CPC switch for all intra-frequency same-bandwidth cells in a planned area. This
minimizes the number of border cells. There are two terms of special relevance to
UL CPC as follows:
● Border cell
A border cell is a cell with an excessively high proportion of neighboring cells
where UL CPC is not in effect in a UL CPC cluster.
● UL CPC cluster
A UL CPC cluster of a cell is the set of all the neighboring cells cooperating for
UL CPC.
When the UL_COORD_PC_SWITCH option of the UlCsAlgoPara.UlCsSw
parameter is selected, UL CPC is enabled, and the UL CPC procedure is performed,
as shown in Figure 5-1.
1. The eNodeB determines which cells will be in the UL CPC cluster of the local
cell.
The eNodeB removes all cells from the UL CPC cluster if the local cell meets
either of the following conditions:
– The cell is deployed on an LBBPc.
– The cell is a single frequency network (SFN) or adaptive SFN cell.
The eNodeB obtains a list of candidate neighboring cells from event A3
reports and arranges the cells in descending order based on the number of
event A3 reports that contain each cell. From these cells, the eNodeB selects
up to 14 cells that meet all of the following conditions and adds them to the
UL CPC cluster:
– The cells are served by the same type of eNodeB (for example macro
eNodeBs) as the local cell.
– The cells operate on the same frequency and have the same bandwidth
as the local cell.
– The UL CPC switch is on.
▪ UEs running guaranteed bit rate (GBR), Voice over Internet Protocol
(VoIP), or push to talk (PTT) services
– The eNodeB uses UL CPC to adjust the power of other UEs.
eNodeBs exchange scheduling and measurement information for
cooperating cells through the X2 or eX2 interfaces. The serving eNodeB
determines whether to increase or decrease the power of UEs in the local
cell based on the exchanged information and then delivers the relevant
commands to the UEs. This optimizes the overall scheduling performance
of the cells in the cluster.
4. The eNodeB checks whether the PuschRsrpHighThdSwitch option of the
CellAlgoSwitch.UlPcAlgoSwitch parameter is selected.
If UL CPC is used, the eNodeB performs the following operations:
– Option not selected
The procedure ends.
– Option selected
The eNodeB uses the CellPcAlgo.PuschRsrpHighThd parameter value as
the RSRP upper limit. This corresponds to upper limit c in Figure 5-1.
If UL CPC does not take effect in the local cell or the UEs in the local cell do
not meet UL CPC conditions, the eNodeB uses PUSCH closed-loop power
control and performs the following operations:
– Option not selected
▪ If there are hotspot cells in the cluster, the eNodeB uses the
UlCsAlgoPara.UlCoPcRbkRsrpThd parameter value as the RSRP
upper limit. This corresponds to upper limit b in Figure 5-1.
– Option selected
▪ If there are no hotspot cells in the cluster, the eNodeB uses the
CellPcAlgo.PuschRsrpHighThd parameter value as the RSRP upper
limit. This corresponds to upper limit c in Figure 5-1.
▪ If there are hotspot cells in the cluster, the eNodeB uses the smaller
value between the CellPcAlgo.PuschRsrpHighThd and
UlCsAlgoPara.UlCoPcRbkRsrpThd parameter values as the RSRP
upper limit. This corresponds to upper limit a in Figure 5-1.
For details about the RSRP upper limit function, see Power Control.
5.2.1 Benefits
UL CPC controls interference and increases the average uplink user-perceived
throughput by up to 20% when the average uplink IN is greater than –105 dBm
and there is a medium-to-heavy load. In hotspot cells where UL CPC has taken
effect, gains vary with the average uplink RB usage:
● RB usage of approximately 40%
UL CPC increases the average uplink user-perceived throughput by
approximately 5%.
● RB usage of approximately 80%
UL CPC increases the average uplink user-perceived throughput by
approximately 20%.
● RB usage of greater than 90% and MCS index of 20 or higher selected for
more than 20% UEs
UL CPC increases the average uplink user-perceived throughput by up to 5%.
5.2.2 Impacts
Network Impacts
● The throughput decreases significantly because cell center user (CCU) power
drops in cells that meet all of the following conditions:
– The cell causes interference on hotspot cells.
– The sum of the values of the counters L.UL.RSRP.PUSCH.Index20 to
L.UL.RSRP.PUSCH.Index23 exceeds 80% of the values of all similar
counters.
– The uplink PRB usage exceeds 90%.
In this situation, UL CPC does not necessarily increase the overall average
uplink user-perceived throughput of the UL CPC deployment area even if
average uplink user-perceived throughput increases significantly in hotspot
cells.
● UL CPC relies on A3 reporting, and therefore there are the following
additional impacts:
– New A3 reports increase the signaling processing overhead. The value of
L.Signal.Num.Uu will go up and the CPU usage of the main control
board will increase by less than 5%.
Function Impacts
Function Function Switch Reference Description
Name
5.3 Requirements
5.3.1 Licenses
Feature ID Feature Name Model Sales Unit
5.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
Function Function Switch Reference
Name
5.3.3 Hardware
Boards
Non-LBBPc BBPs
RF Modules
No requirements
5.3.4 Cells
● The RX mode of the antenna is 1R, 2R, or 4R.
● eNodeBs providing the cells in a cluster are all macro eNodeBs, micro
eNodeBs, or LampSite eNodeBs.
● An X2 interface that supports coordination-based services in non-ideal
backhaul scenarios, or an eX2 interface, is available.
The one-way delay for the interface must be less than 8 ms. For details about
X2 interface support for coordination-based services in non-ideal backhaul
scenarios, see S1 and X2 Self-Management.
In addition, IP PM sessions of forward activation type are recommended for
delay detection.
Configuring an IP PM session of bidirectional activation at either end of an
eX2 interface needs to be avoided. This is because eNodeBs automatically
create IP PM sessions to detect eX2 link status. An IP PM session of
bidirectional activation type may conflict with an automatically created
session. If this is the case, the eX2 interface will fail to work properly.
● There are no PCI conflicts.
PCI conflicts can occur when two involved cells have the same PCI. If there is
a PCI conflict, the eNodeB may incorrectly select a cell in the UL CPC cluster
because it cannot differentiate between the two cells based on the
measurement reports from the UE. You are advised to set the
ENodeBAlgoSwitch.PciConflictAlmSwitch parameter to ON so that PCI
conflicts can be reported.
● There is no intermodulation interference.
If there is intermodulation interference, the eNodeB cannot eliminate the
interference or prevent its impact by using resource coordination.
5.3.5 Others
No requirements
//Turning on the UL CPC switch only when the configured cell radius is less than 15 km
MOD ULCSALGOPARA: LocalCellId=0, UlCoPcInThd=-105, UlCoPcRbkRsrpThd=-96,
UlCoPcUserNumThd=150, UlCsA3Offset=-20, UlCsSw=UL_COORD_PC_SWITCH-1;
6 Parameters
You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.
----End
7 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● eNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
----End
8 Glossary
9 Reference Documents