MLB in LTE
MLB in LTE
MLB in LTE
System Engineering
LTE MLB - Design
Document
TABLE OF CONTENTS
1 References .........................................8
4.3 Huawei............................................................................................................................ 14
7.3 Huawei............................................................................................................................ 27
18 Reporting .........................................51
References
LTE Load balancing Algorithm Overview
LTE Load balancing Flow Chart
LTE Loading Algorithm Metrics (1.1)
o Nokia Networks
o Ericsson
o Huawei
o Alcatel Lucent
Uplink Noise Measurements (2.1)
o Nokia Networks
o Ericsson Networks
o Huawei Networks
o Alcatel Lucent Networks
Performance Metrics (2.9, 2.10)
o Nokia Networks
o Ericsson Networks
o Huawei Networks
o Alcatel Lucent
Neighbor Cells Measurements (1.5, 1.6)
o Nokia Networks
o Ericsson
o Huawei
o Alcatel Lucent
Default Eden-Net Criteria for Cell Overload (1.2)
o Source
Nokia Networks
Ericsson Networks
Huawei Networks
o Target
Nokia Networks
Ericsson Networks
Huawei Networks
o Ericsson Networks
o Nokia Networks
Target
o Nokia Networks
User Defined Thresholds
1 REFERENCES
Eden-NET 4G Metrics - ALU - Initial Formulas
The LTE load balancing module detects cells within the LTE network that exceed the loading
threshold triggers for accessibility failures and cell loading. When congested cells are detected, the
module attempts to reduce congestion by moving idle mode users on the congested cell and
dedicated users in the congested cell to neighbor cells within the same frequency layer.
The LTE load balancing module does this through:
- Making adjustments to neighbor cell offset parameters used in both dedicated and idle mode.
- Making adjustments to handover thresholds.
- TBD: Decreasing total power used in the cell. (This part of the algorithm will not be
implemented yet. Currently for all RAN vendors object locking is required before the cell power can
be adjusted. This causes a temporary outage)
The module examines the loading on neighbor cells and attempts to distribute load among target
neighbor cells. Based on handover metrics the module will continually measure the load on the top
filtered neighbors and will adjust individual offsets per neighbor pair to allow priority selection in UE
offload to these neighbor cells.
The module will monitor the handover success rate for each handover pair to ensure that the most
suitable neighbors are selected as target cells for sharing the excess load on the source cell. The
module will ensure that corrective actions do not cause the neighbors cells themselves to become
congested.
The module continually monitors the load of the neighbor cells to ensure that the UE offloading
(particularly for dedicated mode UEs) does not cause the target neighbor cells to become
congested. If this occurs, other neighbor cells will be made more attractive (through offset
adjustments), so that offloading decreases to the loaded target cell.
Once loading consistently decreases over a set number of periods, the module returns all
parameters to the original operator defined settings.
Metric Calculation
Average avg(PDCP_RET_DL_DEL_MEAN_QCI_1)
Latency
Downlink for
QCI1 DRBs
(msec)
[Avg_Lat_Q
C1]
Average ( LNCEL.PDCP_RET_DL_DEL_MEAN_NON_GBR)
Latency
Downlink for
non GBR
DRBs
(msec)
[Avg_lat_All
_QCI ]
Metric Calculation
% DL PRB ( LNCEL.DL_PRB_UTIL_TTI_MEAN)/10
Utilization
[%_DL_PR
B_Util]
RRC 100*(SIGN_CONN_ESTAB_FAIL_RRMRAC
Connection /(SIGN_CONN_ESTAB_ATT_MO_S+SIGN_CONN_ESTAB_ATT_MT+SIGN_CON
Setup N_ESTAB_ATT_MO_D+SIGN_CONN_ESTAB_ATT_OTHERS+SIGN_CONN_EST
Failure Rate AB_ATT_EMG))
- Radio
Access
Control
[RRC_Conn
_Stp_Fail_R
AC]
E-RAB 100*(EPS_BEARER_SETUP_FAIL_RESOUR)
Failure Rate /(EPS_BEARER_SETUP_ATTEMPTS)
- Resource
Failure
[ERAB_Fail
_Resource]
DL Traffic (PDCP_SDU_VOL_DL)
Volume
(byte)
Average ( LNCEL.DL_UE_DATA_BUFF_AVG)/100
Active UEs
with data in
the DL
buffer
[Avg_Act_U
ser]
"lncel.rrc_conn_ue_avg": "LTE_Cell_Load.M8001C199"
Average
RRC
Not to be used now.It is valid for upcoming features
Connected
Users
[RRC_Conn
ected_UE]
4.2 Ericsson
Metric Calculation
4.3 Huawei
5 UPLINK NOISE
MEASUREMENTS (2.1)
Changing cell individual offsets will artificially shrink the source cell footprint and cause the UEs that
should be connected to the source cell to be connected to the neighbor cell although being closer
(in terms of RF) to the source cell. This
will result in a rise in UL interference. The algorithm will require that the uplink is monitored. If the
rise in uplink interference rises above a user defined threshold then the offsets shown in table for
dedicated and idle mode will be reduced by 1dB.
The counter used are as follows:
Metric Calculation
Metric Calculation
6 PERFORMANCE METRICS
(2.9, 2.10)
The performance metrics are used to assess performance degradation on the target cells only. This
will allow the algorithm to reduce the offsets to mitigate any negative impacts if needed.
Metric Calculation
RRC 100*(SIGN_CONN_ESTAB_FAIL_RRMRAC
Connection /(SIGN_CONN_ESTAB_ATT_MO_S+SIGN_CONN_ESTAB_ATT_MT+SIGN_CON
Setup N_ESTAB_ATT_MO_D+SIGN_CONN_ESTAB_ATT_OTHERS+SIGN_CONN_EST
Failure Rate AB_ATT_EMG))
- Radio
Access
Control
[RRC_Conn
_Stp_Fail_R
AC]
($eRAB_Voice_Drops$) / ($eRAB_Voice_Call_Initiated$)
[eRAB_Voic
Metric Calculation
e_Drop_Rat
e]
Average $Avg_Lat_QC1$
Latency
Downlink for
QCI1 DRBs
(msec)
[Avg_Lat_Q
C1]
Average $Avg_Lat_Non_GBR$
Latency
Downlink for
non GBR
DRBs
(msec)
[Avg_Lat_N
on_GBR]
Metric Calculation
eRAB_Drop_Rate = ($eRAB_Drops$) /
ERAB Drop Rate - All QCI (%)
($eRAB_Disconnections$)
[ERAB_DROPRATE]
Metric Calculation
QCI 1 (msec)
[Avg_Lat_QCI1]
7 NEIGHBOR CELLS
MEASUREMENTS (1.5, 1 .6)
The following counters are used to determine the number of handover attempts per neighbor cell
pair, at least one weeks worth of data will need to be collected:
7.2 Ericsson
7.3 Huawei
8 DEFAULT EDEN-NET
CRITERIA FOR CELL
OVERLOAD (1.2)
8.1 Source
A Source cell is considered overloaded if the following criteria is fulfilled:
8.2 Target
A Target cell is considered overloaded if the following criteria is fulfilled:
9.1 Source
{ Cell_Underload = true; }
{ Cell_Overload = true; }
{ Cell_Overload = true; }
BufferDelay_QCI1 - This parameter defines the maximum amount of time data scheduled for a user
is allowed to be delayed within the eNB. As the eNB loads per cell the delays for transmission of
data will increase and eventual exceed the this threshold indicating overload.
Range: 10 to 100 ms
Step size : 5ms
Default : 20 ms
BufferDelay_NonGBR - This parameter defines the maximum amount of time data scheduled for a
user is allowed to be delayed within the eNB. As the eNB loads per cell the delays for transmission
of data will increase and eventual exceed the this threshold indicating overload.
Range: 100 to 1000 ms
Step size : 50ms
Default : 200 ms
Userdefined_L_RAC - This parameter allows the user to define a threshold for the percentage of
blocking due to Load and Admission Control before load balancing is activated
Range: 0 to 100%
Step size : 1%
Default : 5%
Userdefined_Erab - This parameter allows the user to set a threshold for ERAB failures due eNB
resource blocking before load balancing is activated
Range: 0 to 100%
Step size : 1%
Default : 5%
Userdefined_Time_No_Res - This parameter allows the users to set a percentage of time threshold
for blocking due to lack of eNodeB resources over the measurement period, before load balancing
is activated.
Range: 0 to 100%
Step size : 1%
Default : 5%
PRB_exit_threshold - This parameter allows the users to set a threshold for beginning to reduce
offsets over a measurement period
Range: 0% to (less than or equal to PRB_threshold)
Step size: 1%
Default 75 (or 5% below entry criteria)
Buffer_Delay_QC1_exit - This parameter defines the maximum amount of time data can be
buffered before the offset are allowed to be reduced on the source call
Range: 0% to (less than or equal to BufferDelay_QCI1)
Step size : 1 ms
Default: 20
Buffer_Delay_nonGBR_exit - This parameter defines the maximum amount of time non-GBR data
can be buffered before the offset are allowed to be reduced on the source call
Range: 0% to (less than or equal to BufferDelay_nonGBR)
Step size : 5 ms
Default : 175 (or 25 ms below entry criteria)
10 T-MOBILE CRITERIA FO R
CELL OVERLOAD (1.3)
Add a new optional section to the config called, "Operator Criteria". If this module config file section
contains: "Triggers = TMUS", then this sections trigger criteria applies. If module config file
contains: "Triggers = edennet" or contains no "Triggers" entry, then use the default criteria in
section 1.2
There is a longer term need to make operator in use be visible to the module through the
framework, in order to make a Default vs Operator selection available in GUI Parameters list.
Currently an operator flag is available and used at "install" time, and this is not retained or stored in
redis or otherwise. If this was retained for the framework to access, then the GUI parameters could
become variable and change as a function of the operator(s) in use. We do not recommend
hardcoding a default/operator selection into the GUI parameters as is, as this may deliver one
operators custom capability to all other customers, which is not desired.
Source
A Source cell is considered overloaded if the following criteria is fulfilled:
10.3 Target
A Target cell is considered overloaded if the following criteria is fulfilled:
Ericsson Networks
If (DL_PRB_Util > TMO_PRB_threshold OR (RRC_Connected_UE / (dlChannelBandwidth / 5)) >
TMO_RRC_Users_threshold)
Then { Cell_Overload = true; }
TMO_RRC_Users_threshold - This parameter allows the user to define a trigger threshold for
setting of RRC Connected UEs over a measurement period.
Range : 0 to 100
Steps size : 1
Default: 65
TMO_RRC_Users_eq5_threshold - This parameter allows the user to define a trigger threshold for
setting of RRC Connected UEs over a measurement period, when inactivityTimer=5 for Nokia
Range : 0 to 100
Steps size : 1
Default: 50
By categorizing the top N neighbor cells according to load through the use of a weighting value, will
ensure that a cell does not offload too much of it's traffic to a cell that is close to overload itself.
The weighting mechanism will allow individual cell offsets to be implemented to make one cell more
attractive than the other, the loaded cell should offload more traffic to the low traffic cells than the
higher traffic cells. This concept is shown in the figure below:
It should be noted that in the diagram the individual cell offset from the neighbor cells to loaded cell
is set so that only a minimum amount of handovers take place back to to loaded cells. Also, a
target candidate that is already under mitigation with always be excluded from a source cell
selection list.
To determine the top 5 suitable cells to offload load to; arrange the cells with greater than 1% of the
total handover attempts, in a list from highest to lowest based on handover attempts where the
success rate is greater 95% and apply the following pseudo code:
11.1.1 Nokia
Buffer_Slope = 2
Buffer_Weight = 30
CellWeight = %_DL_PRB_Util + (Avg_Lat_Non_GBR -
Buffer_Slope*%_DL_PRB_Util)/Buffer_Weight
11.1.2 Ericsson
Buffer_Slope = 5
Buffer_Weight = 20
CellWeight = %_DL_PRB_UTIL + (Avg_Lat_All_QCI - (Buffer_Slope)) / Buffer_Weight
11.1.3 Huawei
Buffer_Slope = 2
Buffer_Weight = 60
CellWeight = %_DL_PRB_Util + (Avg_Lat_Non_GBR -
Buffer_Slope*%_DL_PRB_Util)/Buffer_Weight
11.1.4 ALU
Buffer_Slope = 2
Buffer_Weight = 60
12 DEDICATED MODE
PARAMETER SETTINGS F OR
OFFLOADING (1.8)
The cell weighting that has been calculated in step 1.7 for the top 5 neighbor cells which are not
overloaded and the following initial offset applied, relative to the defaults network setting, from the
source cell to the target neighbor cell and from the target cell to the source cell:
Number of Targets Offset Applied (source to targets) Offset Applied (targets to source)
Min 5, Max 15 3 dB -3 dB
LNREL cellIndOffNeigh
EUtranCellRelation cellIndividualOffsetEUtran
EutranIntraFreqNCell CellIndividualOffset
LteNeighboringCellRelation cellIndividualOffset
LNCEL threshold1
threshold1(new) = threshold1(old) + 6
12.2.2 Ericsson
Managed Object Parameter
UeMeasControlsMeasure sMeasure
HoMeasComm SMeasureInd
HoMeasComm SMeasure
RrcMeasurementConf sMeasure
12.2.5
sMeasure(new) = sMeasure(old) + 6
Number of Targets Offset Applied (source to targets) Offset Applied (targets to source)
Min 5, Max 15 3 dB -3 dB
IAFIM physCellIdNcl
IAFIM qOffsetCell
Nokia requires that under the IAFIM managed object a "list name="intrFrNCList" is created if one is
not present and then the above parameters are to be added .
The physCellIdNcl is the neighbor cell physical cell identity (PCI) that will be used by the UE to
apply the offset to the power measurements.
qOffsetCell is the parameter that the offset in the above table is applied to.
An extract for the xml that illustrates the structure is shown as follows:
EUtranCellRelation qOffsetCellEUtran
EutranIntraFreqNCell CellQOffset
LteNeighboringCellRelation qOffsetCell
LNCEL sIntrasearch
EUTRANCELLFDD/SIB3 sIntraSearch
EUTRANCELLFDD/SIB3 sIntraSearchP
CellResel SIntraSearch
CellSelectionReselectionConf sIntraSearch
If the uplink noise threshold has been triggered or the loaded cell is no longer overloaded then the
algorithm will reduce the offsets for both dedicated and idle mode.
Do not reduce any of the offsets below that of the network operator values.
For source to target neighbor cell, the offsets should be adjusted as follows:
new Offset = Offset - RedOffset
For target to source cell the offsets are adjusted as follows:
new Offset = Offset + RedOffset
RedOffset - Value that sets the amount by which the CIO offsets can be increased or decreased
Range: 0,1,2
Step Size : 1
Default : 1
If the cell is still overloaded then the offsets can be increased to offload more traffic as follows:
For source to target neighbor cell, the offsets should be adjusted as follows for dedicated and idle
parameters:
new Offset = Offset +IncOffset
For target to source cell, the offsets should be adjusted as follows for dedicated and idle
parameters:
new Offset = Offset -IncOffset
The maximum absolute offset that can be applied per cell should be configurable by a configuration
file threshold and should be relative to the cells starting offset values. The default max absolute
offset is 6 dB over the current offset value
For example, if CIO in the cells is set to 0, then the max allowable offset is 0 + 6 = 6. If CIO, in the
cell is set to 2, then the max allowable offset is 2 + 6 = 8 dB
IncOffset - Value that sets the amount by which the CIO and qOffset parameters can be increased
or decreased
Range: 0,1,2
Step Size : 1
Default : 1
17 PERFORMANCE TRIGGERS
(2.10)
ERABHysteresis - This parameter sets the threshold for the increase in drop rate for the target cell
before the algorithm attempts to reduce the offsets applied.
Range : 0 .. 100%
Step: 1%
Default: 10%
RACHysteresis - This parameter sets the threshold for the increase in eNB resource failure on the
target cell before the algorithm attempts to reduce the offsets applied.
Range : 0 .. 100%
Step: 1%
Default: 10%
LACHysteresis - This parameter sets the threshold for the increase in eNB resource failure on the
target cell before the algorithm attempts to reduce the offsets applied.
Range : 0 .. 100%
Step: 1%
Default: 10%
18 REPORTING
20 PM COUNTER REQUIREMENTS
VS.NbSimultane
ousTransmittin
gUEInDL.GBR.N
bEvt,
VS.NbSimultane
ousTransmittin
gUEInDL.NonG
BR.NbEvt
22 PM SCANNERS ENABLED IN
T MOBILE'S ERICSSON
Currently, T Mobile LTE Ericsson RAN is L14B
verifiable via AMOS in any eNb with command
LBX03130A> invh
150521-19:55:02 11.162.122.84 11.0b ERBS_NODE_MODEL_E_1_236 stopfile=/tmp/9813
Node: RBS6131L CXP102051/22_R45DM L14B (C15.0-EP2-5)
===========================================================================
==========================================================
SMN APN BOARD SWALLOCATION S FAULT OPER MAINT c/p d PRODUCTNUMBER REV
SERIAL DATE MO
===========================================================================
==========================================================
0 1 DUL2001 main 1 OFF ON OFF 27% 33% KDU137533/4 R1F D160962507 20120619 1,Slot=1
------------------------------------------------------------------------------------------------------------------------------------
-
===========================================================================
==========================================================
XPBOARD ST FAULT OPER MAINT PRODUCTNUMBER REV SERIAL/NAME DATE MO
===========================================================================
==========================================================
S-RET 1 16910526 V_A02 KA035871201843_A1 AntennaUnitGroup=1,AntennaNearUnit=1
S-RET 1 16910526 V_A02 KA035871101083_A1 AntennaUnitGroup=2,AntennaNearUnit=1
S-RET 1 16910526 V_A02 KA035987201056_A1 AntennaUnitGroup=3,AntennaNearUnit=1
RRUS0ZB4 1 OFF ON OFF KRC118034/1 R1C D162180635 20120826 AuxPlugInUnit=RRU-1-1
RRUS0ZB4 1 OFF ON OFF KRC118034/1 R1C D162180634 20120826 AuxPlugInUnit=RRU-1-2
RRUS0ZB4 1 OFF ON OFF KRC118034/1 R1C D162225032 20120828 AuxPlugInUnit=RRU-2-1
RRUS0ZB4 1 OFF ON OFF KRC118034/1 R1C D162225031 20120828 AuxPlugInUnit=RRU-2-2
RRUS0ZB4 1 OFF ON OFF KRC118034/1 R1C D162225026 20120828 AuxPlugInUnit=RRU-3-1
RRUS0ZB4 1 OFF ON OFF KRC118034/1 R1C D162225025 20120828 AuxPlugInUnit=RRU-3-2
AIR21B4AB2P KRC118046/1 R2A CQ30031500 20120906 000100/BXP_1 000100/BXP_1_1
AIR21B4AB2P KRC118046/1 R2A CQ30031502 20120906 000100/BXP_2 000100/BXP_2_1
AIR21B4AB2P KRC118046/1 R2A CQ30030708 20120906 000100/BXP_0 000100/BXP_0_1
------------------------------------------------------------------------------------------------------------------------------------
-
===========================================================================
==========================================================
MO SMN PRODUCT PRODUCTNUMBER REV SERIAL/NAME DATE transmissionType maxPwr
fanConfiguration position
===========================================================================
==========================================================
Subrack=1 0 Subrack ROJ999999 * ETHERNET_CABLE 2000W NO_CPP_FAN
the attached pm.txt has the contents of scanners 40 (predefined) & 69 (T Mobile's default)
the enclosed lic.txt has the license status of LTE features (via AMOS invr
Ideally, this information needs to be provided by any operator, for each provider, and updated prior
to any RAN release.
23 TEST PLANS
FOA for LTE LBO_v0.2.docx
TP-Lab for LTE LBO v0.1.docx