Mobility Load Balancing
Mobility Load Balancing
•Intra-LTE Load Balance(base on • Intra-LTE User Number Load Balance(base on • Support Load balance and offload work
PRB usage) UE number) together
•Connect-mode Load Balance •Connect-mode Load Balance • Intra-LTE Load Balancing for Non-cosited
•Connect-mode Offload •Idle-mode Load Balance Cell
•Connect-mode Offload • Intra-LTE User Number Load
Balance(base on UE number)
• Intra-LTE Pre-Load balance •Target Ratio can be controlled by
Users
•Pre-Load balance in fixed mode
• Handover Published for UE handover in
•Pre-Load balance in adaptive mode
due to MLB.
Congested Admission
Rejection &
MLB: Pre-emption
L2L(inter- Redirection
Middle/ MLB L2L
Vendor) - for RRC, eRAB
IDLE CellReselPriority: -Connect-mode Load
High Allow UEs to camp on cells with offload between - GBR, non-GBR
z Balance(Based on Congestion
large bandwidths by assigning the LTE carriers
PRB usage) Control
frequency with large bandwidths
with a high reselection priority. -Idle-mode Load - For GBR
Freq-Prio-Based IFHO Balance(Based on
Allow UEs to perform services at UE Number)
cells with large bandwidths even -Connect-mode Load MLB: L2U
when the frequencies have the Balance(Based on offload from
Light UE Number)
same reselection priority LTE to UMTS
carrier
MLB L2L
- Pre-Balancing
LTE LTE
Offload
Make the load
X2, Load exchanged under a certain
Load Balance threshold
Load Balance:
support an arbitrary number of frequencies and frequency bands.
support an arbitrary number of target cells on the same inter-frequency.
Support balance between cells that are co-located and not co-located.
Support balance between cells that are Macro and Macro/ Macro and Micro/ Micro and Micro
Offload:
Support offload to the cells without load exchanged, especially for cells between different vendors.
Support offload to UMTS
Low load
SCENE: HANDOVER REQUEST ACKNOWLEDGE
Inter-frequency
No X2 interface, or method of load evaluation is
not same, such as inter-Vendor scene. High load
the Most user equipment is data card. Because HANDOVER PREPARATION FAILURE
the feature need the statistic of PRB is stable. But for
smart phone user, non-GBR is usually short but Published the target cell
frequent data transactions, the PRB usage is rapidly
changed. It is not suitable for the function
40000
35000
30000
25000
20000
15000
10000
5000
101
1
5
9
13
17
21
25
29
33
37
41
45
49
53
57
61
65
69
73
77
81
85
89
93
97
Time(S)
Low load
SCENE: HANDOVER REQUEST ACKNOWLEDGE
Inter-frequency
No X2 interface, or method of load evaluation is
not same, such as inter-Vendor scene. High load
HANDOVER PREPARATION FAILURE
SCENE:
Inter-frequency
Each cell has the same coverage capacity. That means there are almost no
coverage-based inter frequency handover happened.
SCENE:
Inter-frequency
Co-BBU, Each sector have same frequency configuration. For example, the scene
as follows is not suitable: Sector A: cell1(F1)/cell2(F2);
SectorB:Cell1(F1)/Cell2(F2)/Cell3(F3)
Selection
UE Selection
Continue 5S Leave
condition is satisfied
MLB Stop Load Transfer
eRAN6.0, Load balance & offload : eRAN7.0 , Load balance & offload : eRAN7.0 , Load balance :
PRB% >= InterFreqMLBThd + LoadOffset, for 5s, UL_Sync_User > = InterFreqMlbUeNumThd UL_Sync_User > = IFIdleMlbUeNumThd +
then MLB is triggered + MlbUeNumOffset, for 5s, then MLB is MlbUeNumOffset, for 5s, then MLB is
eRAN7.0 , Load balance & offload : triggered triggered
PRB% >= InterFreqMLBThd + LoadOffset & eRAN8.1 , Load balance: eRAN8.1 , Load balance:
UL_Sync_User >= MlbMinUeNumThd + UL_Sync_User > = InterFreqMlbUeNumThd UL_Sync_User > = IFIdleMlbUeNumThd +
MlbMinUeNumOffset, for 5s, then MLB is + MlbUeNumOffset, for 5s, then MLB is MlbUeNumOffset, for 5s, then MLB is triggered
triggered triggered
eRAN8.1, Load balance : eRAN8.1 , Offload:
PRB% >= InterFreqMLBThd + LoadOffset & UL_Sync_User > = InterFreqMlbUeNumThd
UL_Sync_User >= MlbMinUeNumThd + + MlbUeNumOffset
MlbMinUeNumOffset, for 5s, then LB is +InterFrqUeNumOffloadOffset, for 5s, then
triggered MLB is triggered
eRAN8.1, Offload:
PRB% >= InterFreqMLBThd + LoadOffset
+InterFreqOffloadOffset& UL_Sync_User >=
MlbMinUeNumThd + MlbMinUeNumOffset, for
5s, then LB is triggered
Neighbor Cell List Candidate Cell List Neighbor Cell List Candidate Cell List
Candidate Frequency List Target Frequency Candidate Frequency List Target Frequency
Co-BBU: UL_Sync_User exchange via co-BBU Co-BBU: PRB% exchange via co-BBU signalling
signalling Cross-BBU: X2, PRB% via Resource Status Report, by
Cross-BBU: X2, huawei private message 3GPP
*Next page for details * Next page for details
Target load evaluation Target load evaluation
(M-A/B*N)/M>UeNumDiffThd, M is ServCell_PRB% > Target_PRB% + LoadDiffThd
UL_Sync_User in serving cell while N is for
Ncell, A and B are PRB num of serving cell and
Ncell.
Target
Frequency
(for dedicated
priority in RRC_Rel)
Neighbor Cell Candidate Cell Candidate
List List Frequency List
Target
Frequency
(for IFHO)
Non-Blind or Blind or
L2L MLB Non-Blind or Blind
Both
Cell1: F1
MLB
MLB
Cell3: F2
Cell2: F2 OverlapInd=NO
OverlapInd=YES
If multi frequencies have the same priority, then all of them will be in the MC, which means HO
target can be more than one.
Frequency Priority doesn’t apply to the action of RRC_Rel with dedicated priority.
4.1 UE Selection
eRAN7.0, UL_Sync_User to trigger eRAB6.0->eRAN7.0, PRB% to trigger
and HO
IFHO User Selection IFHO User Selection
Execution
IFHO IFHO
2. What is LoadTransferFactor?
A parameter to control the amount of load to transfer. Larger value means more load is allowed to be
transferred to target cell, but Ping-Pong will not happen as the factor is multiplied by LoadDiffThd.
Parameter range: 0%-100%
RRC_Rel with
Dedicated Priority
Example of Load Pre-balancing in Fix Proportions: Works before L2L MLB is triggered
F1 has N users to release their RRC Connection
To allocate UE to different carriers
according to the pre-defined ratio
Dedicated priority of reselection is carried
F3 Ratio=50% in RRC_Rel message with T320
50%*N UE to
camp on F3
F2 Ratio=30%
30%*N UE to
camp on F2
Serving cell
F1 Ratio=20% N UE RRC_Rel from F1
20%*N UE to
stay on F1
Same Idle-Mode common priority is suggest to prevent the UE back to overload cell after MLB handover it to
the low load cell.
Mothod1:
Idle-Mode common Priority Low load (Target:Camp on wide Middle/High load(Target:Load Balance)
bandwidth)
Mothod2:
Idle-Mode common Low load (Target:Camp on Middle/High load(Target:Load
Priority wide bandwidth) Balance)
UL_Sync_User based:
MOD CELLMLB: LocalCellId=0, MlbTriggerMode=UE_NUMBER_ONLY , InterFreqUeTrsfType=SynchronizedUE-
1&IdleUE-1;
MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=InterFreqMlbSwitch-1;
L2L
L.HHO.InterFreq.UeNumLoad.PrepAttOut will be pegged when feature is working.
UL_Syn_User number diffenence (L.Traffic.User.Ulsync.Avg) between carriers can be decreased
Average user throughput = L.Thrp.bits.DL/(L.Thrp.Time.Cell.DL* L.Traffic.User.Avg) could get improved
Package delay time = L.Traffic.DL.PktDelay.Time.QCIX/L.Traffic.DL.PktDelay.Num.QCIX could be shorter
L.InterFreq.HighLoad.Dur.Cell Duration in which a cell with inter-frequency load balancing enabled is in the high-load state
Load
L.InterFreq.HighLoad.Num.Cell Number of times a cell with inter-frequency load balancing enabled enters from the low-load state to the high-load state
L.InterFreq.Load.Meas.Num.Cell Number of times the eNodeB delivers the load-triggered inter-frequency measurement configuration to a UE
RRC_REL MLB L.RRCRel.DedicatedPri.LTE.High Number of RRC Release with EUTRAN is the highest priority in dedicate priority
HUAWEI TECHNOLOGIES CO., LTD. Page 41