Load Balancing
Load Balancing
Inter-Frequency
Intra-Frequency
• Load Balancing Features Overview Intra-LTE Inter-RAT
Connected Mode Load Balancing Features
LTE1387 – Intra-eNB Inter-Frequency Load Balancing (RL40)
LTE1140 – Intra-Frequency Load LTE1357 LTE-UTRAN load
Balancing (RL70/RL55TD) LTE1170 – Inter-eNB Inter-frequency Load Balancing (RL50) balancing (FL15A)
LTE1531 – Inter-frequency Load Balancing Extensions (RL60/RL45TD)
LTE1841 – Inter Frequency Load Equalization (RL70/RL55TD)
Key functionality
• A UE is selected for IMMLB if the condition below is true:
• Where:
• NrOfRrcReleaseForIMMC: Internal counter RRC connection release with IMMLB information
• NrOfRrcRelease: Total number of RRC connection release
• idleLBPercentageOfUes: Percentage of UE’s set via parameter for IMMLB offloading. This is based on object level (LNCEL, MOPR,
MODPR)
• Additionally it is also checked the UE capabilities support at least one of the configured target
Interfrequency/RAT layers
• eNB has at least one frequency valid for load balancing , taking into account UE Capabilities with supported bands and
configured frequencies in SIB related instances for intra-LTE and inter-RAT target frequencies or Mobility Profiles
• UE was not selected for any kind of redirection
Example: Value 0.76 was randomly generated Generated value 0.76 means that f4 will get priority 7 in IMMCI
• Idle Mode Mobility Load Balancing (IMMLB) refers to the inclusion of Dedicated Priorities within the RRC
Connection Release message
• Load balancing is achieved by allowing:
• some UE’s use the Priorities broadcast within the SIB
• some UE’s use Dedicated Priorities included within their RRC Connection Release
• IMMLB has evolved with each software release
• RL70 introduces the capability to trigger IMMLB only when the serving load becomes high
• rather than always triggering the feature
Technolo Abbreviated Name MO Class Paramet Parent Full Name Data Range and step Default Value PROPOSED Required
gy er Structure Type on
Category Creation
4G idleLBPercentageOfUes MRBTS/LNBTS/LNCEL Basic Percentage of UE for idle mode load balancing Number 0...100, step 10 0 50 Mandator
parameter y
s
4G t320 MRBTS/LNBTS/LNCEL Advanced Timer T320 Enumerati 5:5min; 180 10 Mandator
parameter on 10:10min; y
s 20:20min;
30:30min;
60:60min;
120:120min;
180:180min
4G actIdleLB MRBTS/LNBTS Basic Activation of idle mode load balancing (IdleLB) Boolean 0 1 Mandator
parameter y
s
4G idleLBCellReSelPrio MRBTS/LNBTS/LNCEL Basic Serving cell carrier freq prio for idle mode load balancing Number 0...6.8, step 0.2 7 Optional
parameter
s
4G idleLBCelResWeight MRBTS/LNBTS/LNCEL Basic Cell reselection weight factor idle mode load balancing Number 1...100, step 1 50 Optional
parameter
s
4G eutCelResPrio MRBTS/LNBTS/LNCEL/ Basic EUTRA carrier frequency absolute priority Number 0...7, step 1 7 Optional
IRFIM parameter
s
4G idleLBEutCelResPrio MRBTS/LNBTS/LNCEL/ Basic EUTRAN carrier freq prio for idle mode load balancing Number 0...6.8, step 0.2 6 Optional
IRFIM parameter
s
4G idleLBEutCelResWeight MRBTS/LNBTS/LNCEL/ Basic EUTRA carrier weight factor idle mode load balancing Number 1...100, step 1 50 Optional
IRFIM parameter
s
• UEs entering Connected state can be offloaded if target cell is measured to be at good radio
condition
• Offloading of UEs can be done towards intra-eNB or inter-eNB neighbor cells
850 MHz
DL
• Target cell for offloading must have available capacity to serve offloaded UEs
UL
• Load information is exchanged only between cells of the same eNB
• Load information from cells belonging to other eNBs are implicitly determined from HO
2100 MHz
preparation decision in Load blind HO DL
- Relative Load defines measured load in relation to configured Target Load Threshold (TL)
- Target Load Threshold is configured via parameters: LNCEL:LoadSettings:targetLoadGbrDl, targetLoadNonGbrDl,
targetLoadPdcch
- Relative load is a subcomponent in calculation of DL Available Capacity (AC)
Available Capacity = [100% - RL]
100%
DL GBR Measured DL GBR Relative DL GBR Available
Load Load Capacity
N
Cell in Y
Active iF-
LB state
N ANY Cell ALL Cell Load Y Leave Active iF-LB
Load
Y > N< State
TargetLoadxxx
HighLoadxxx
iFLBHighLoadGBRDL/
iFLBHighLoadNonGBR TargetLoadGBRDL/
Y N TargetLoadNonGBRDL/
DL/
iFLBHighLoadPDCCH TargetLoadPDCCH
Enter Active iF-LB
State Note : Filtered load measurements are evaluated
UE Selection for periodically each time measurements arrive from
Measurement L2 (period= 500ms).
Solicitation
14 RA41220-V-22R3 © Nokia 2021
Inter-frequency Load Balancing
Step 4 iF-LB Execution
Upon receiving A4 reports, the target cell list (TCL) is processed to choose the best target cell for offloading
Reordering of Target Cell List • eNodeB shall reorder Target Cell List according to
descending Composite Available Capacity (CAC)
• CAC= min (AC_GBR, AC_nGBR, AC_PDCCH)
Choosing the target cell for HO
• Topmost cell of re-ordered TCL is chosen as the target cell
for HO
Handover preparation
• Intra-eNB X2, or S1 HO is prepared towards the chosen
target cell
• HO Cause “Reduce load in serving cell”
Handover Execution • Admission Control shall be applied as for “HO due to radio
reasons”
When feature is activated (LNCEL:actAmle = true) its behaviour can be Source Cell
reflected as 5 functional blocks
1) Load supervision and exchange: Load supervision and
CAC exchange
• Measurements of CACS and exchange with neighbours
Check of active AMLE
2) Check of active AMLE state conditions state conditions
• AMLE state of source cell is determined
Candidate UE selection AMLE feature
3) Candidate UE selection
• When Inter Frequency Load Balancing QCI1 Bearer Check Timer or Inter Frequency Load Measurement
Balancing Retry Timer is expired UE is checked if it can be Candidate for offloading solicitation
4) Measurement solicitation Load Equalization
• A4 measurements of partner neighbour frequencies are triggered execution
• Each measured DL Load (ML) is reflected as Relative DL GBR Measured DL GBR Relative DL GBR Available
Load (RL) Load Load Capacity
˗ Relative Load defines measured load in relation to PDCCH Measured PDCCH Relative PDCCH Available
Load Load Capacity
configured Target Load Threshold (TL)
DL non-GBR DL non-GBR DL non-GBR
˗ Target Load Threshold is configured via parameters: Measured Load Relative Load Available Capacity
LNCEL:LoadSettings:targetLoadGbrDl,
targetLoadNonGbrDl, targetLoadPdcch
˗ Relative load is a subcomponent in calculation of DL Cell LoadX [%]
Available Capacity (AC) 100%
Cell1 Cell1
Resource Status Update (RSU) message
…
…
X2AP: RSU
• Resource Status Update message contains LM
CellX CellY
information coming from different eNB
• The first RSU is sent by responding eNB as soon as
first Load Measurements are available
X2AP:RSU (Cell1)
• Subsequent reporting is handled according to A B C C C C
Requested Periodicity Responding eNB Requested Periodicity time
Note:
When LTE1841 is activated (LNBTS:actAmle = true), at least
default AMLEPR-0 has to be configured
MRBTS.LNBTS.LNCEL.AMLEPR.deltaCac
Difference in CAC of source and target cells
The difference between S
0..100%;
and T is enough to make
Default :20% offload
Example:
AMLE State verification:
• 3 partner cells
• 2 partner frequency layers Partner Cell (PC) of Source Cell (S)
PC1 PC2 PC3
f1 f2 f2
CACPC1 CACPC2 CACPC3
4) Measurement Solicitation
AMLE feature
Measurement
For UE that is a candidate for offloading A4 measurements Solicitation
are started, provided that maximum number of concurrent
Partner Cell
• Cells from different RAT (including cells of Home eNB when LNBTS:actHeNBMobility is activated)
• Cells with unknown CAC and with too low CAC
• When AMLEPR:cacHeadroom > 0 then cells with CACT < AMLEPR:cacHeadroom are removed, otherwise cells with CACT=0% are
removed [no available capacity]
• Cells for which CAC of Source cell is too high [CACS > AMLEPR:maxCacThreshold] *
• Cells that do not fulfill: CACT - CACS > AMLEPR:deltaCac *
• Number of AMLE HOs towards given cell, between two CAC updates from this cell,
is higher than LNCEL:amleMaxNumHo
• Cells that are blacklisted for Load Based HO (LB HO) All unsuitable cells are
STEP 2: TCL sorting removed from TCL
• If there is at least one cell on TCL after STEP1, list is sorted according to descending ∆CAC
• First candidate that is at the top of TCL is a partner target cell with the biggest CAC deviation with source cell
HO preparation phase
• First cell from the top of TCL is considered to be the first Handover Request
Target Cell Cause: Reduce Load in Serving Cell
HO preparation phase
Handover Request
˗ Case 2) Unsuccessful HO preparation
Cause: Reduce Load in Serving Cell
phase
Admission Other
• If RAC of target cell rejects the HO Request, Control Target Cell
HO Preparation failure with proper cause is HO Preparation Failure
sent Cause: No Radio Resources Available in
prohibitLBHoTimer
Target Cell/Transport Resources
- If RAC admits only some of UE`s bearers, Unavailable
LBHO is cancelled by source cell (cause: Handover Request Handover Request
Partial HO) Cause: Reduce Load in Serving Cell Cause: Reduce Load in
Serving Cell
• Target cell in which RAC rejects (or partially
Handover Request
admits) LBHO is blocked by source cell to
Cause: Reduce Load in Serving Cell
avoid next LBHOs during time defined by
LNBTS:prohibitLBHOTimer
• In such case, HO towards the second cell in NOTE: For simplicity, only X2 Load Based Handover is
TCL (if any) will be triggered described. In case of different types of HO (intra-eNB, S1
based HO) proper HO messages are used
4G amlePrId MRBTS/LNBTS/LNCEL/AMLEPR Active mode load equalization profile identifier 0...15, step 1 0 0 Not modifiable Mandatory