Mobility Load Balancing

Security Level:
Huawei eRAN8.1 Intra-LTE Load

Balance Feature Discription
2014 June.
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD.

Content
 Huawei MLB Overview

 MLB Feature Description
 Detail of the function
 Activation and Verification
HUAWEI TECHNOLOGIES CO., LTD. Page 2

Road Map
•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.
• Intra-LTE Load Balance(base on PRB usage)

•Minimum UE number Trigger condition
eRAN6.0 eRAN7.0 eRAN8.X

Solution at each load stage
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

MLB in distributed Architecture
Other RAT LTE Other Vendor
Load balance
Load information is
Make the load
not same dimension Without X2, no Load exchanged
diff under a
Offload Offload
certain
threshold
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

Content


Connect-Mode Load Balance(base on PRB usage)
Overview Uplink Balance & Downlink Balance
DL PRB% of UL PRB% of the
the UE UE
Target:
PRB
Handover Load exchanged Remain is When downlink load is high,
same UE with high PRB usage of
DL is choose without
consideration of UL
SCENE: When uplink load is high, UE

 Inter-frequency with high PRB usage of UL and
 X2 interface low PRB usage of DL is choose
to avoid Ping Pang
 the Most user equipment is data card. Because
the feature need the statistic of PRB is stable. But for
smart phone user, non-GBR is usually short but Support:
frequent data transactions, the PRB usage is rapidly 1. Downlink PRB balance
changed. It is not suitable for the function 2. Uplink PRB balance
3. GBR downlink PRB balance
4. GBR uplink PRB balance

Connect-Mode Offload(base on PRB usage)
Overview
Source Cell Target Cell
Target: High load

Handover PRB is low
than a
Handover Request
threshold. (with Cause: Reduce Load in Serving Cell)
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

Connect-Mode Load Balance(base on UE Number)
M operator DL PRB/UL PRB Usage vs User
Overview Number
100.00%
Target:
90.00%
UE Number of F1:UE Number
F1 80.00%
of F2 = Bandwidth of F1:
70.00%
bandwidth of F2
Handover Load exchanged 60% 60% 60.00%
50.00% 50.63%
40.00% 43.22%
F2
30.00%
20.00%
10.00%
0.00%
0 100 200 300 400 500 600 700 800 900
SCENE: Support: Average User Number
DL PRB Usage UL PRB Usage CCE Usage
 Inter-frequency 1. CA users not selected The control resource(CCE)’s cost/RB cost increases as
 X2 interface is need 2. VoLTE users not selected connected user number growth
Sum of RB number
45000
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)
PRB usage Rapid changed in each second In one cell

Idle-Mode Load Balance(base on UE Number)
In 3GPP 36.304:
Overview
Target: Absolute priorities of different E-
UE Number of F1:UE Number
F1 of F2 = Bandwidth of F1:
UTRAN frequencies or inter-RAT
RRCRel(with Load exchanged 60% 60%
bandwidth of F2 frequencies may be provided to the UE
IMMCI)
in the system information, in the
F2 RRCConnectionRelease message, or by
inheriting from another RAT at inter-
IMMCI:Idle mode mobility RAT cell (re)selection. In the case of
control info system information, an E-UTRAN
frequency or inter-RAT frequency may
be listed without providing a priority
SCENE: (i.e. the field cellReselectionPriority is
 Inter-frequency absent for that frequency). If priorities
are provided in dedicated signalling,
 X2 interface is need
the UE shall ignore all the priorities
 only one target cell on the same inter-frequency, usually the provided in system information.
cells are co-coverage. Need configure the co-coverage cell as a
“overlapind”.

Connect-Mode Offload(base on UE Number)
Overview
Source Cell Target Cell
Target: High load

Handover UE Number
is low than
Handover Request
a threshold. (with Cause: Reduce Load in Serving Cell)
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
Published the target cell

Pre-Load Balance in fixed mode
Overview
Support:
IMMCI with F1 higher 1. The target ratio can be set
priority for 60%
by operator
IMMCI 60%*N camp IMMCI
on F1
with F1
RRCRel(wit RRCRel(wit with F2
higher h IMMCI) h IMMCI) higher
priority 40%*N camp on F2 priority
for 60% for 40%
IMMCI with F2 higher
priority for 40%
SCENE:
 Inter-frequency
 Each cell has the same coverage capacity. That means there are almost no
coverage-based inter frequency handover happened.

Pre-Load Balance in adaptive mode
Get the frequency load by
Accumulating the cells in Overview
same frequency. And calculate
Support:
the release ratio due to load 1. The target ratio can be set
diff in different frequencies.
Target:60%*N
IMMCI with by operator
camp on F1 F1 higher
RRCRel(with priority for
IMMCI) the Ratio
Target:40%*N
camp on F2 calculate by
the load diff.
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)

Content


Huawei MLB Function description
Act period:
CellMLB.InterFreq Preliminary Load
LoadEvalPrd Candidate Informatio
Cell n
Continue 5S Enter
Selection Exchange
condition is satisfied
MLB Trigger Candidate Cell
Selection Final
Candidat
e Cell
Target Frequency Selection
Selection
UE Selection
Continue 5S Leave
condition is satisfied
MLB Stop Load Transfer

Main change in eRAN8.1
Position Change information Parameter
Candidate Target：the target of balance for ”Load balance based on UE number”can be adjust by operator。 CellMLB.Ce
Cell Scene：frequency efficiency is different for different cells llCapacityS
Selection Implementation：The cell level parameter CellMLB.CellCapacityScaleFactor“cell capacity scale factor”is added in the caleFactor，
function，the target for load balance for cellA&cellB is ：UE num of CellA/UE num of CellB=(RB number of
CellA*CellMLB.CellCapacityScaleFactor of cellA)/ (RB number of CellB*CellMLB.CellCapacityScaleFactor of cellB)
Impact on device：new item is added in the message of X2.
Impact on operation and maintenance：new parameter is added for the function.
Impact on capacity and performance：
capacity ：the efficiency of radio resource usage can be improved, so the capacity can increase.
Performance：Average throughput per UE can increase。
Impact on other features：enhance the function of Connect-Mode Load Balance/Idle-Mode Load Balance in the
feature“LOFD-070215 Intra-LTE User Number Load Balancing”.
Candidate Target：the enter condition of Load Balance/Offload is independent. CellMLB.Int
Cell Scene：Multi-frequencies of HW+ frequency of other vendor erFrqUeNu
Selection Implementation： mOffloadOff
In the “Intra-LTE User Number Load Balancing”：when the load of serving cell lower than set
CellMLB.InterFreqMlbUeNumThd + CellMLB.MlbUeNumOffset + CellMLB.InterFrqUeNumOffloadOffset) ，the neighbor cell CellMLB.Int
without load exchanged cannot be selected as a candidate erFreqOfflo
In the “Intra-LTE Load Balancing”：when the load of serving cell lower than (CellMLB.InterFreqMlbThd + adOffset
CellMLB.LoadOffset + CellMLB.InterFreqOffloadOffset)，the neighbor cell without load exchanged cannot be selected as a
candidate
Impact on device：
Impact on operation and maintenance：new parameter is added for the function.
Impact on capacity and performance：before eRAN8.1，Load Balance&Offload cannot work together。In eRAN8.1,
they can work together
HUAWEI TECHNOLOGIES
Impact CO., LTD.
on other features：enhance the feature”LOFD-070215 Intra-LTE User Number Load Page 16
Balancing/LOFD-001032
Load Target：in non co-located scene，UE close to the site cannot be select to steer to other cell。 EutranInterNFr
Transfer Scene：non co-located scene。 eq.MlbInterFre
Implementation：When configure the parameter EutranInterNFreq.MlbInterFreqHoEventType as “EventA5”， qHoEventType
measurement control with EventA5 is sent to UE. InterFreqHoGr
Impact on device：N/A oup.MlbInterFr
Impact on operation and maintenance：new parameter is added for the function；New LICENSE：”LOFD-081227 eqHoA5Thd1R
Intra-LTE Load Balancing for Non-cosited Cell “ is added for the function srp
Impact on capacity and performance： InterFreqHoGr
capacity ：the efficiency of radio resource usage can be improved, so the capacity can increase. oup.MlbInterFr
Performance：Average throughput per UE can increase。 eqHoA5Thd1R
Impact on other features：enhance the function of Connect-Mode Load Balance和Connect-Mode Offload in the srQ
feature LOFD-070215 Intra-LTE User Number Load Balancing/LOFD-001032 Intra-LTE Load Balancing
Load Target：Handover Published for UE handover in due to MLB. CellMlbHo.Mlb
Transfer Scene：All scene. HoInProtectMo
Implementation： de
Set CellMlbHo.MlbHoInProtectMode to “PROTECTTIMERMODE”,When UE in the period CellMlbHo.Mlb
CellMlbHo.MlbHoInProtectTimer，UE cannot be transferred to other cell caused by MLB。 HoInProtectTi
Impact on device：N/A mer
Impact on operation and maintenance：new parameter is added for the function
Impact on capacity and performance：set a suitable value of CellMlbHo.MlbHoInProtectTimer, the capacity is not
affected，set a much large value of CellMlbHo.MlbHoInProtectTimer，It may cause the load cannot be balance, the
capacity may decrease。
Impact on other features：enhance the function of Connect-Mode Load Balance and Connect-Mode offload in the
feature LOFD-070215 Intra-LTE User Number Load Balancing/LOFD-001032 Intra-LTE Load Balancing

Load Target：work together with eMBMS ，When UE is receiving MBMS, it will not be transferred to other frequency by N/A
Transfer MLB
Scene：When the frequency active eMBMS and connect-Mode load balance/connect-Mode offload
Implementation：When UE report“MBMSInterestIndication ”，When the frequency of serving cell is in the
mbms-FreqList ，the measurement control will not be sent to the UE, and when the measurement control has been
sent to the UE, after the UE report the measurement report, handover will not trigger。
Impact on device：N/A
Impact on operation and maintenance：N/A
Impact on capacity and performance：N/A
Impact on other features：enhance the function of Connect-Mode Load Balance/Connect-Mode Offload in the
feature “LOFD-070215 Intra-LTE User Number Load Balancing/LOFD-001032 Intra-LTE Load Balancing; LOFD-
070220 eMBMS Phase 1 based on Centralized MCE Architecture
Load Target：When the ratio of UE not support handover is high, support use redirect to transfer load. CELLALGOS
Transfer Scene：the ratio of UE not support handover is high WITCH.MlbHo
Implementation： Mode中子开关
When the sub-switch InterFreqMlbRedirect of the paratermterCELLALGOSWITCH.MlbHoMode set to 1，When InterFreqMlbR
the UE selected not support handover to the target frequency, it will redirect to the target frequency。 edirect
Impact on device：N/A
Impact on operation and maintenance：new parameter is added for the function； (Note:For
Impact on capacity and performance： OneTrack，do
capacity ：the efficiency of radio resource usage can be improved, so the capacity can increase. the same
Performance：the UE be transferred by redirect will be down, so it will cause the performance of the UE be bad. funtion as
Impact on other features：enhance the function of Connect-Mode Load Balance/Connect-Mode Offload in the TDD)
feature “LOFD-070215 Intra-LTE User Number Load Balancing/LOFD-001032 Intra-LTE Load Balancing;

Load Target：All the frequency priority for MLB used as the IMMCI of “Idle-Mode Load Balance” 。 CELLMLBHO.
Transfer Scene：N/A。 IdleUeSelFreq
Implementation：the parameter CELLMLBHO. IdleUeSelFreqStrategy set to “MLBPRIOBASED”， When fill Strategy
the IMMCI of Idle-Mode Load Balance，the target frequency for load transfer will be set to 7，other frequency will
be ordered as EUTRANINTERNFREQ.MlbFreqPriority。 (Note:For
Impact on device：N/A OneTrack，do
Impact on operation and maintenance：new parameter is added for the function the same
Impact on capacity and performance：N/A funtion as
Impact on other features：enhance the function “Idle-Mode Load Balance” in the feature LOFD-070215 Intra-LTE TDD)
User Number Load Balancing

L2L MLB
1. Trigger Mechanism
PRB% to trigger, UE number to trigger（Connect-Mode) UE number to trigger（Idle-Mode)
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

L2L MLB
2. Target Selection
UL_Sync_User to trigger PRB% to trigger

(for trigger1 and trigger2)
Target Frequency Selection Target Frequency Selection
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 Selection
 Target Frequency Selection

 Neighbor cell list  Candidate cell List  Candidate Frequency List  Target Frequency
Target
Frequency
(for dedicated
priority in RRC_Rel)
Neighbor Cell Candidate Cell Candidate
List List Frequency List
Target
Frequency
(for IFHO)
Different scope for 1. MLBTargetInd=allowed;  (M-A/B*N)/M >

different X2 scenarios. 2. NoHoFlag = UeNumDiffThd Two options for frequency policy
See next pages. PERMIT_HO_ENUM;  Random
3. Not in blacklist;  ServCell_PRB% >  Priority
4. No PCI confliction; Target_PRB% +
5. Cell is activated LoadDiffThd

Load-exchange Mode
 Two load-exchange modes
 Non-Blind mode
 Load info is a must for target frequency selection (via. Co-BBU signaling or X2)
 L2L: MlbAlgoSwitch = InterFreqMlbSwitch-1 & InterFreqBlindMlbSwitch-0
 Blind MLB mode (for IFHO action only)

 X2 is not available. MLB functions without load info.
 L2L: MlbAlgoSwitch = InterFreqMlbSwitch-0 & InterFreqBlindMlbSwitch-1
Load-exchange Mode eRAN6.0 eRAN7.0
Non-Blind or Blind or
L2L MLB Non-Blind or Blind
Both

Candidate Cell Scope
 Candidate Cell Scope
Mode Non-Blind Blind Both

InterFreqMlbSwitch=ON InterFreqMlbSwitch=OFF InterFreqMlbSwitch=ON
Switch
InterFreqBlindMLBSwitch=OFF InterFreqBlindMLBSwitch=ON InterFreqBlindMLBSwitch=ON
No OverlapInd is configured OverlapI No OverlapInd is configured OverlapI No OverlapInd is configured
OverlapInd is nd is LoadBalanceNce nd is
NCell Configuration LoadBalanceNcellS LoadBalanceNce LoadBalanceNcell LoadBalanceNcell LoadBalanceNce
configured configur llScope=Adaptiv configur
cope=Adaptive llScope=All Scope=All Scope=Adaptive llScope=All
ed e ed
OverlapInd
Co-BBU Ncell. If Co-BBU Ncell. If
Ncell in the
none co-BBU ncell Co-BBU Ncell none co-BBU
same BBU and OverlapI Ncell from other OverlapI
Selection Result available, then and X2 Ncell All Ncell ncell available, All Ncell
OverlapInd nd Ncell BBU nd Ncell
select Ncell with X2 from other BBU then select Ncell
Ncell with X2
from other BBU from other BBU
from other BBU
 OverlapInd and LoadBalanceNcell are new parameters in eRAN7.0

 Rules of OverlapInd for MLB – RRC_Rel with dedicated priority
 If more than one Ncell are configured with OverlapInd on the same frequency, then the frequency can be a MLB
candidate only if all of Ncell with OverlapInd are in Candidate Cell List.
 If no Ncell is configured with OverlapInd, a frequency can be MLB candidate if there is at least one Ncell is in
Candidate Cell List.

OverlapInd
Background
In a real multi-carrier network, the coverage between carriers are not exactly the same. The
overlapping area could be large or small due to site planning, band propagation characteristic, etc.
Introduction
OverlapInd is introduced as an attribute in EUTRANINTERFREQNCELL, to facilitate MLB to select a
better candidate cell.
In the example below, only Cell2 is possible to become a MLB Candidate Cell for Cell1.
Cell1: F1
MLB
MLB
Cell3: F2
Cell2: F2 OverlapInd=NO
OverlapInd=YES

Target Frequency for IFHO
Two Policies for IFHO MLB action

 Random
 Randomly a frequency is selected from Candidate Frequency List and sent to all UE.
 Priority policy (newly introduced in eRAN7.0)
 Frequency priority of MLB is configurable for neighbor frequencies. The frequency with highest
priority is sent firstly to UE for measurement.
 LTE: EUTRANINTERNFREQ.MlbFreqPriority
 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.
 eRAN6.0, there is only one random frequency in MC to UE if MLB triggered.
 Frequency Priority doesn’t apply to the action of RRC_Rel with dedicated priority.

Target Frequency for Dedicated Priority in RRC_Rel
All frequencies in Candidate Frequency List will be used as Target Frequency.

Target Frequency, dedicated priority value and T320 will be contained in the IE
IdleModeMobilityControlInfo of RRCConnectionRelease, in the sequence as below:
1. Target Frequency of MLB
2. LTE other frequencies
3. UMTS (if exists)
4. GSM (if exists)
For 1. 2. 3. 4. above, if there are more than one frequency in each department, the relative order will be
in accord with the order of their common reselection priority (in SIB).
 If SPID-based reselection priority (or Operator-based reselection priority) exists, the relative order will be in
accord with the order in SPID-based reselection priority.

L2L MLB
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
User Selection Criteria

User Selection Criteria UE PRB% on trigger direction >
UE PRB% <= MlbUeSelectPrbThd (for MlbUeSelectPrbThd (UE PRB% on other
both UL and DL) direction <= MlbUeSelectPrbThd)
Up to MlbMaxUeNum UE to select Up to MlbMaxUeNum UE to select within
(within period InterFreqLoadEvalPrd) period InterFreqLoadEvalPrd
 QCI≠1 Total_UE_PRB% to transfer, next page for
details
IFHO Target Criteria IFHO Target Criteria
RSRP > InterFreqLoadBasedHoA4ThdRsrp + RSRP > InterFreqLoadBasedHoA4ThdRsrp +
IfMlbThdRsrpOffset, only allowed when IfMlbThdRsrpOffset, only allowed when coverage
coverage is good is good

UE Selection
1. Total_UE_PRB% is calculated and a ‘minimum amount’ to transfer is determined

For each cell in Candidate Cell List, calculation is based on formula below:
 Total_UE_PRB% = Min{ServCell_PRB%-( InterFreqMlbTh-LoadOffset-1%), 0.5*(ServCell_PRB%–
Target_PRB%) + LoadDiffThd*LoadTransferFactor}
From all of the calculation results, get the smallest one as minimum Total_UE_PRB% to transfer, so as
to guarantee there is no risk of Ping-Pong no matter what cell the UEs finally go to.
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%
3. Total number of UE to transfer is calculated on each cell in Candidate Cell List

TotalTransfUENum = min{ (B*M-A*N)/(B+A), ServCell_Ul_Sync_User_Num – CellMLB.InterFreqMlbUeNumThd+1,
MlbMaxUeNum }
A is ServCell’s total RB, B is Ncell’s total RB, M is ServCell’s user number, N is Ncell’s user number.

HO Execution
 Execution Results depends on different target frequency policies
 Random:UE may go to different cells but on the same frequency
 Priority (new in eRAN7.0):UE may go to different cells of different frequencies
 In eRAN7.0 if the best cell in Measurement Report does not exist in Candidate Cell List, HO will
not carry out.
 This policy is controlled by CellMLB.MlbHoCellSelectStrategy:
 ONLY_STRONGEST_CELL/PERMIT_NON_STRONGEST_CELL can be selected
 The RSRP/RSRQ condition for target cell is need fulfill:

 eRAN6.0/eRAN7.0, A4 is support, InterFreqLoadBasedHoA4ThdRsrp
A: F1
/InterFreqLoadBasedHoA4ThdRsrq can be set by operator
 eRAN8.1: for different target frequency, A4/A5 can be choose by
B: F2 C: F2
MlbInterFreqHoEventType, and MlbInterFreqHoA5Thd1Rsrp
/ MlbInterFreqHoA5Thd1Rsrp can be set by operator.
 MLB HO can be BlindHO (supported since eRAN6.0)
An example for MLB HO execution under ‘Random’ policy
 Configurable. CellAlgoSwitch.MlbHoMode
 InterFreqMlbBlindHo

L2L MLB
4.2 RRC_Rel
Execution eRAN7.0, UL_Sync_User to trigger
RRC_Rel User Selection
RRC_Rel with
Dedicated Priority
User Selection Criteria

 When UE releases RRC, it’ll become
a MLB user
Dedicated Priority in RRC_Rel

 T320ForLoadBalance for dedicated
priority

Pre-load Balancing
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

Content


Activation Guide
Scene1: multi target cells in same frequency , such as
Idle-Mode common Low load (Target：Camp on Middle/High load(Target：Load

Priority wide bandwidth) Balance)
same Connect Mode：frequency- Connect Mode：Connect-Mode Load

priority-based inter-frequency Balance
handover
Same Idle-Mode common priority is suggest to prevent the UE back to overload cell after MLB handover it to
the low load cell.

Activation Guide2
Scene2: only one target cells in same frequency , such as
Mothod1:
Idle-Mode common Priority Low load (Target：Camp on wide Middle/High load(Target：Load Balance)
bandwidth)
same Connect Mode：frequency-priority- Connect Mode：Connect-Mode Load

based inter-frequency handover Balance(optional)
Idle-Mode dedicated Priority：N/A Idle-Mode dedicated Priority：Idle-Mode Load

Balance

Activation Guide3
Scene2: only one target cells in same frequency , such as
Mothod2:
Frequency with Wider Connect Mode：frequency-priority- Connect Mode：N/A

bandwidth has higher based inter-frequency
priority handover(optional)
Idle-Mode dedicated Priority：N/A Idle-Mode dedicated Priority：Idle-Mode
Load Balance

Activation Guide4
Scene3: Hetnet

Frequency of Micrio has N/A Connect Mode：N/A

higher priority Idle-Mode dedicated Priority：N/A Idle-Mode dedicated Priority：Micro-
>Macro: Idle-Mode Load Balance
Macro->Micro:N/A

Activation Guide5
Scene

Activation Guide5
 L2L MLB
 PRB% based:
MOD CELLMLB: LocalCellId=0, MlbTriggerMode=PRB_ONLY;
MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=InterFreqMlbSwitch-1;
 UL_Sync_User based:
MOD CELLMLB: LocalCellId=0, MlbTriggerMode=UE_NUMBER_ONLY , InterFreqUeTrsfType=SynchronizedUE-
1&IdleUE-1;
MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=InterFreqMlbSwitch-1;

Verification
 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

Counter
TYPE Counter Name Description
L.Traffic.User.Ulsync.Avg Number of Average UL Synchronized UEs in a Cell
User Number L.Traffic.User.Avg Average Number of Users in a Cell
L.Traffic.User.Max Maximum Number of Users in a Cell
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.Thrp.bits.DL Total downlink traffic volume for PDCP SDUs in a cell
L.Thrp.bits.UL Total uplink traffic volume for PDCP SDUs in a cell

Throughput
L.Thrp.Time.Cell.DL Total duration of downlink data transmission in a cell
L.Thrp.Time.Cell.UL Total duration of uplink data transmission in a cell

Number of successfully transmitted downlink traffic PDCP SDUs for DRB services with the QCI of 1~9 in a
Package Delay L.Traffic.DL.PktDelay.Num.QCI.1~9
cell
Time
L.Traffic.DL.PktDelay.Time.QCI.1~9 Processing delay of downlink PDCP SDUs for DRB services with the QCI of 1~9 in a cell
L.HHO.InterFreq.UeNumLoad.PrepAttOut Number of user-number-load-based inter-frequency handover preparation attempts
L.HHO.InterFreq.UeNumLoad.ExecAttOut Number of user-number-load-based inter-frequency handover execution attempts
L.HHO.InterFreq.UeNumLoad.ExecSuccOut Number of successful user-number-load-based inter-frequency handover executions
Handover L.HHO.InterFreq.Load.PrepAttOut Number of load-based inter-frequency handover preparation attempts

Related L.HHO.InterFreq.Load.ExecAttOut Number of load-based inter-frequency handover execution attempts
L.HHO.InterFreq.Load.ExecSuccOut Number of successful load-based inter-frequency handover executions
L.InterFreq.Load.Meas.Num.Cell Number of times the eNodeB delivers the load-triggered inter-frequency measurement configuration to a UE
L.InterFreq.Load.MeasSucc.Num.Cell Number of times the load-triggered inter-frequency measurement is successful
RRC_REL MLB L.RRCRel.DedicatedPri.LTE.High Number of RRC Release with EUTRAN is the highest priority in dedicate priority

Mobility Load Balancing

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mobility Load Balancing

Uploaded by

Copyright:

Available Formats

Security Level:

Huawei eRAN8.1 Intra-LTE Load

HUAWEI TECHNOLOGIES CO., LTD.

 Huawei MLB Overview

HUAWEI TECHNOLOGIES CO., LTD. Page 2

• Intra-LTE Load Balance(base on PRB usage)

eRAN6.0 eRAN7.0 eRAN8.X

HUAWEI TECHNOLOGIES CO., LTD. Page 3

HUAWEI TECHNOLOGIES CO., LTD. Page 4

HUAWEI TECHNOLOGIES CO., LTD. Page 5

 Huawei MLB Overview

HUAWEI TECHNOLOGIES CO., LTD. Page 6

SCENE: When uplink load is high, UE

HUAWEI TECHNOLOGIES CO., LTD. Page 7

Target: High load

HUAWEI TECHNOLOGIES CO., LTD. Page 8

PRB usage Rapid changed in each second In one cell

HUAWEI TECHNOLOGIES CO., LTD. Page 9

HUAWEI TECHNOLOGIES CO., LTD. Page 10

Target: High load

Published the target cell

HUAWEI TECHNOLOGIES CO., LTD. Page 11

HUAWEI TECHNOLOGIES CO., LTD. Page 12

HUAWEI TECHNOLOGIES CO., LTD. Page 13

 Huawei MLB Overview

HUAWEI TECHNOLOGIES CO., LTD. Page 14

HUAWEI TECHNOLOGIES CO., LTD. Page 15

HUAWEI TECHNOLOGIES CO., LTD. Page 17

HUAWEI TECHNOLOGIES CO., LTD. Page 18

HUAWEI TECHNOLOGIES CO., LTD. Page 19

PRB% to trigger, UE number to trigger（Connect-Mode) UE number to trigger（Idle-Mode)

HUAWEI TECHNOLOGIES CO., LTD. Page 20

UL_Sync_User to trigger PRB% to trigger

Target Frequency Selection Target Frequency Selection

HUAWEI TECHNOLOGIES CO., LTD. Page 21

 Target Frequency Selection

Different scope for 1. MLBTargetInd=allowed;  (M-A/B*N)/M >

HUAWEI TECHNOLOGIES CO., LTD. Page 22

 Blind MLB mode (for IFHO action only)

Load-exchange Mode eRAN6.0 eRAN7.0

HUAWEI TECHNOLOGIES CO., LTD. Page 23

 Candidate Cell Scope

Mode Non-Blind Blind Both

 OverlapInd and LoadBalanceNcell are new parameters in eRAN7.0

HUAWEI TECHNOLOGIES CO., LTD. Page 24

HUAWEI TECHNOLOGIES CO., LTD. Page 25

Two Policies for IFHO MLB action

 eRAN6.0, there is only one random frequency in MC to UE if MLB triggered.

HUAWEI TECHNOLOGIES CO., LTD. Page 26

All frequencies in Candidate Frequency List will be used as Target Frequency.

HUAWEI TECHNOLOGIES CO., LTD. Page 27

User Selection Criteria

HUAWEI TECHNOLOGIES CO., LTD. Page 28

1. Total_UE_PRB% is calculated and a ‘minimum amount’ to transfer is determined

3. Total number of UE to transfer is calculated on each cell in Candidate Cell List

HUAWEI TECHNOLOGIES CO., LTD. Page 29

 The RSRP/RSRQ condition for target cell is need fulfill:

HUAWEI TECHNOLOGIES CO., LTD. Page 30

RRC_Rel User Selection

User Selection Criteria

Dedicated Priority in RRC_Rel

HUAWEI TECHNOLOGIES CO., LTD. Page 31

HUAWEI TECHNOLOGIES CO., LTD. Page 32