Intra-RAT Mobility Load Balancing (ERAN8 1 - 01)

eRAN
Intra-RAT Mobility Load Balancing

Feature Parameter Description
Issue 01
Date 2015-03-23
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
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.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2015-03-23) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
eRAN
Intra-RAT Mobility Load Balancing Feature Parameter
Description Contents
Contents
1 About This Document..................................................................................................................1

1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................2
1.3 Change History...............................................................................................................................................................2
1.4 Differences Between eNodeB Types..............................................................................................................................5
2 Overview.........................................................................................................................................6
2.1 Introduction....................................................................................................................................................................6
2.2 Benefits...........................................................................................................................................................................6
2.3 Architecture....................................................................................................................................................................6
3 Related Concepts...........................................................................................................................9
3.1 Cell Load........................................................................................................................................................................9
3.2 Cell Types.......................................................................................................................................................................9
3.3 Overlapping Neighboring Cell.....................................................................................................................................10
3.4 Type of UEs to Be Transferred.....................................................................................................................................10
3.5 Exchange and Non-Exchange Modes...........................................................................................................................10
4 MLB Procedure.............................................................................................................................12
5 User-Number-based Inter-Frequency MLB............................................................................14
5.1 MLB by Transferring RRC_REL UEs.........................................................................................................................15
5.1.1 MLB Triggering and Termination.............................................................................................................................15
5.1.2 Candidate Cell Selection...........................................................................................................................................15
5.1.2.1 Preliminary Candidate Cell Selection.....................................................................................................................16
5.1.2.2 Load Information Exchange...................................................................................................................................18
5.1.2.3 Final Candidate Cell Selection...............................................................................................................................19
5.1.3 Target Frequency Selection.......................................................................................................................................19
5.1.4 UE Selection..............................................................................................................................................................20
5.1.5 Load Transfer............................................................................................................................................................20
5.2 MLB by Transferring UL-Sync UEs............................................................................................................................22
5.2.2.1 Preliminary Candidate Cell Selection.....................................................................................................................25
5.2.2.2 Load Information Exchange...................................................................................................................................27
Issue 01 (2015-03-23) Huawei Proprietary and Confidential ii

eRAN
5.2.2.3 Final Candidate Cell Selection...............................................................................................................................27

5.2.4 UE Selection..............................................................................................................................................................28
5.2.5 Load Transfer............................................................................................................................................................29
6 PRB-Usage-based Inter-Frequency MLB................................................................................33

6.1 MLB Triggering and Termination................................................................................................................................34
6.2 Candidate Cell Selection..............................................................................................................................................34
6.3 Target Frequency Selection..........................................................................................................................................36
6.4 UE Selection.................................................................................................................................................................36
6.5 Load Transfer...............................................................................................................................................................37
7 Operator-Level Inter-Frequency MLB.....................................................................................39

7.1 Operator-Level User-Number-based Inter-Frequency MLB........................................................................................40
7.1.1 MLB by Transferring RRC_REL UEs......................................................................................................................40
7.1.1.1 MLB Triggering and Termination..........................................................................................................................40
7.1.1.2 Candidate Cell Selection........................................................................................................................................41
7.1.1.3 Target Frequency Selection....................................................................................................................................41
7.1.1.4 UE Selection...........................................................................................................................................................41
7.1.1.5 Load Transfer.........................................................................................................................................................41
7.1.2 MLB by Transferring UL-Sync UEs.........................................................................................................................41
7.1.2.1 MLB Triggering and Termination..........................................................................................................................42
7.1.2.2 Candidate Cell Selection........................................................................................................................................42
7.1.2.3 Target Frequency Selection....................................................................................................................................42
7.1.2.4 UE Selection and Load Transfer............................................................................................................................42
7.2 Operator-Level PRB-Usage-based Inter-Frequency MLB...........................................................................................43
7.2.4 UE Selection..............................................................................................................................................................45
7.2.5 Load Transfer............................................................................................................................................................45
8 Inter-Frequency MLB for Non-Cosited Cells.........................................................................46

9 Load Pre-Balancing.....................................................................................................................47
9.1 Load Pre-Balancing Methods.......................................................................................................................................48
9.2 Execution and Termination of Load Pre-Balancing.....................................................................................................49
9.3 UE Transfer Proportions...............................................................................................................................................49
9.4 Selection of Dedicated Priorities..................................................................................................................................51
10 Transport-QoS-based Inter-Frequency MLB.......................................................................53

10.1 MLB Triggering and Termination..............................................................................................................................54
10.2 Candidate Cell Selection............................................................................................................................................54
10.3 Target Frequency Selection........................................................................................................................................54
Issue 01 (2015-03-23) Huawei Proprietary and Confidential iii

eRAN
10.4 UE Selection...............................................................................................................................................................55
10.5 Load Transfer.............................................................................................................................................................55
11 Related Features.........................................................................................................................56
11.1 Features Related to LOFD-070215 Intra-LTE User Number Load Balancing..........................................................56
11.2 Features Related to LOFD-001032 Intra-LTE Load Balancing.................................................................................57
11.3 Features Related to LOFD-070204 Operator Load Based Intra-LTE MLB...............................................................57
11.4 Features Related to LOFD-081227 Intra-LTE Load Balancing for Non-cosited Cells..............................................58
11.5 Features Related to LOFD-001057 Load Balancing based on Transport QoS..........................................................59
12 Network Impact.........................................................................................................................60
12.1 LOFD-070215 Intra-LTE User Number Load Balancing..........................................................................................60
12.2 LOFD-001032 Intra-LTE Load Balancing.................................................................................................................61
12.3 LOFD-070204 Operator Load Based Intra-LTE MLB..............................................................................................61
12.4 LOFD-081227 Intra-LTE Load Balancing for Non-cosited Cells.............................................................................61
12.5 LOFD-001057 Load Balancing based on Transport QoS..........................................................................................62
12.6 Load Pre-Balancing....................................................................................................................................................62
13 Engineering Guidelines...........................................................................................................63
13.1 LOFD-070215 Intra-LTE User Number Load Balancing..........................................................................................63
13.1.1 When to Use LOFD-070215 Intra-LTE User Number Load Balancing.................................................................63
13.1.2 Required Information..............................................................................................................................................64
13.1.3 Planning...................................................................................................................................................................64
13.1.3.1 RF Planning..........................................................................................................................................................64
13.1.3.2 Network Planning.................................................................................................................................................65
13.1.3.3 Hardware Planning...............................................................................................................................................65
13.1.4 Requirements...........................................................................................................................................................65
13.1.5 Data Preparation......................................................................................................................................................66
13.1.6 Activation................................................................................................................................................................74
13.1.7 Activation Observation............................................................................................................................................78
13.1.8 Deactivation.............................................................................................................................................................79
13.1.9 Reconfiguration.......................................................................................................................................................80
13.1.10 Performance Monitoring........................................................................................................................................81
13.1.11 Parameter Optimization.........................................................................................................................................82
13.1.12 Troubleshooting.....................................................................................................................................................87
13.2 LOFD-001032 Intra-LTE Load Balancing.................................................................................................................88
13.2.1 When to Use LOFD-001032 Intra-LTE Load Balancing........................................................................................88
13.2.2 Required Information..............................................................................................................................................88
13.2.3 Planning...................................................................................................................................................................88
13.2.4 Requirements...........................................................................................................................................................88
13.2.5 Data Preparation......................................................................................................................................................89
13.2.6 Activation................................................................................................................................................................92
13.2.7 Activation Observation............................................................................................................................................96
Issue 01 (2015-03-23) Huawei Proprietary and Confidential iv

eRAN
13.2.8 Deactivation.............................................................................................................................................................96
13.2.9 Reconfiguration.......................................................................................................................................................97
13.2.11 Parameter Optimization.........................................................................................................................................99
13.2.12 Troubleshooting...................................................................................................................................................102
13.3 LOFD-070204 Operator Load Based Intra-LTE MLB............................................................................................102
13.3.1 When to Use LOFD-070204 Operator Load Based Intra-LTE MLB....................................................................102
13.3.2 Required Information............................................................................................................................................102
13.3.3 Planning.................................................................................................................................................................102
13.3.4 Requirements.........................................................................................................................................................103
13.3.5 Data Preparation....................................................................................................................................................104
13.3.6 Activation..............................................................................................................................................................108
13.3.7 Activation Observation..........................................................................................................................................113
13.3.8 Deactivation...........................................................................................................................................................114
13.3.10 Parameter Optimization.......................................................................................................................................116
13.4 LOFD-081227 Intra-LTE Load Balancing for Non-cosited Cells...........................................................................118
13.4.1 When to Use LOFD-081227 Intra-LTE Load Balancing for Non-cosited Cell....................................................118
13.4.3 Planning.................................................................................................................................................................118
13.4.4 Requirements.........................................................................................................................................................118
13.4.6 Activation..............................................................................................................................................................121
13.4.8 Deactivation...........................................................................................................................................................124
13.5 Load Pre-Balancing..................................................................................................................................................126
13.5.1 When to Use Load Pre-Balancing.........................................................................................................................126
13.5.3 Planning.................................................................................................................................................................126
13.5.4 Requirements.........................................................................................................................................................127
13.5.6 Activation..............................................................................................................................................................131
13.5.8 Deactivation...........................................................................................................................................................136
13.5.9 Reconfiguration.....................................................................................................................................................137
13.5.10 Performance Monitoring......................................................................................................................................137
Issue 01 (2015-03-23) Huawei Proprietary and Confidential v

eRAN
13.6 LOFD-001057 Load Balancing based on Transport QoS........................................................................................139
13.6.1 When to Use LOFD-001057 Load Balancing based on Transport QoS...............................................................139
13.6.3 Planning.................................................................................................................................................................139
13.6.4 Requirements.........................................................................................................................................................139
13.6.6 Activation..............................................................................................................................................................141
13.6.8 Deactivation...........................................................................................................................................................145
14 Parameters.................................................................................................................................147
15 Counters....................................................................................................................................189
16 Glossary.....................................................................................................................................196
17 Reference Documents.............................................................................................................197
Issue 01 (2015-03-23) Huawei Proprietary and Confidential vi

eRAN
Description 1 About This Document
1 About This Document
1.1 Scope
This document describes intra-radio access technology (intra-RAT) inter-frequency mobility
load balancing (MLB), including its technical principles, related features, network impact, and
engineering guidelines.
This document covers the following features:
l LOFD-001032 Intra-LTE Load Balancing

l LOFD-070215 Intra-LTE User Number Load Balancing
l LOFD-070204 Operator Load Based Intra-LTE MLB
l LOFD-081227 Intra-LTE Load Balancing for Non-cosited Cells
l LOFD-001057 Load Balancing based on Transport QoS
This document applies to the following types of eNodeBs.
eNodeB Type Model
Macro 3900 series eNodeB
Micro BTS3202E
LampSite DBS3900
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD, and
"eNodeB" refers to LTE FDD eNodeB.
Issue 01 (2015-03-23) Huawei Proprietary and Confidential 1

eRAN
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein

l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
eRAN8.1 01 (2015-03-23)
This issue includes the following changes.
Chan Change Description Parameter Change Affected

ge Entity
Type
Featur None None None

e
change
Editori Optimized some descriptions None N/A

al of the document.
change
eRAN8.1 Draft A (2015-01-15)

Compared with Issue 07 (2014-12-30) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1 includes
the following changes.

eRAN

ge Entity
Type
Featur Modified the candidate cell Added the parameter Macro, micro,
e selection procedure of "user- CellMLB.CellCapacityScale- and LampSite
change number-based inter-frequency Factor. eNodeBs
MLB by transferring
RRC_REL UEs" and UE
selection procedure of "user-
number-based inter-frequency
MLB by transferring UL-sync
UEs". For details, see 5.1.2.3
Final Candidate Cell
Selection and 5.2.4 UE
Selection.
Modified the load transfer Added the following parameters:

procedures of "user-number- l CellMlbHo.
based inter-frequency MLB by MlbHoInProtectMode
transferring UL-sync UEs" and
PRB-usage-based inter- l CellMlbHo.
frequency MLB. For details, MlbHoInProtectTimer
see 5.2.5 Load Transfer.
Modified the candidate cell Added the following parameters:

selection procedures of user- l CellMLB.
number-based inter-frequency InterFrqUeNumOffloa-
MLB by transferring UL-sync dOffset
UEs and PRB-usage-based
inter-frequency MLB. For l CellMLB.InterFreqOffloa-
details, see 5.2.2.3 Final dOffset
Candidate Cell Selection and
6.2 Candidate Cell Selection.
Added LOFD-081227 Intra- Added the following parameters:

LTE Load Balancing for Non- l EutranInterNFreq.
cosited Cells. For details, see 8 MlbInterFreqHoEventType
Inter-Frequency MLB for
Non-Cosited Cells and 13.4 l InterFreqHoGroup.
LOFD-081227 Intra-LTE MlbInterFreqHoA5Thd1Rs
Load Balancing for Non- rp
cosited Cells. l InterFreqHoGroup.
MlbInterFreqHoA5Thd1Rs
rQ
Added the A2BasedFreqPri-
HoSwitch(A2BasedFreqPri-
HoSwitch) option to the
CellAlgoSwitch.FreqPriorityH
oSwitch parameter.

eRAN

ge Entity
Type
Revised the descriptions of the Added the following parameters:

penalty on target frequencies, l CellMLB.PunishJudgePrd-
target cells, and UEs. For Num
details, see 5.2.3 Target
Frequency Selection and l CellMLB.
5.2.5 Load Transfer. FreqPunishPrdNum
l CellMLB.MlbUeSelectPu-
nishTimer
l CellMLB.
CellPunishPrdNum
Editori Revised the quality None N/A

al requirements on target cells in
change the load transfer procedures of
"user-number-based inter-
frequency MLB by
transferring UL-sync UEs" and
PRB-usage-based inter-
frequency MLB. For details,
see 5.2.5 Load Transfer.
Revised the descriptions in the None N/A

following sections:
l 2.3 Architecture
l 5.1.2.1 Preliminary
Candidate Cell Selection
l 5.2.2.1 Preliminary
Candidate Cell Selection
l 6.1 MLB Triggering and
Termination
l 9.3 UE Transfer
Proportions
l 13.5.6 Activation

eRAN
1.4 Differences Between eNodeB Types

Feature Support by Macro, Micro, and LampSite eNodeBs
Feature ID Feature Name Supported Supporte Supported by
by Macro d by LampSite
eNodeBs Micro eNodeBs
eNodeBs
LOFD-001032 Intra-LTE Load Yes Yes Yes

Balancing
LOFD-070215 Intra-LTE User Yes Yes Yes

Number Load
Balancing
LOFD-070204 Operator Load Based Yes Yes Yes

Intra-LTE MLB
LOFD-081227 Intra-LTE Load Yes Yes Yes

Balancing for Non-
cosited Cells
LOFD-001057 Load Balancing based No Yes No

on Transport QoS
Function Implementation in Macro, Micro, and LampSite eNodeBs

Function Difference
Load pre-balancing Macro, micro, and LampSite eNodeBs support load pre-balancing in
in fixed proportions fixed proportions.
Load pre-balancing Micro eNodeBs do not support load pre-balancing in adaptive

in adaptive proportions.
proportions

eRAN
Description 2 Overview
2 Overview
2.1 Introduction
Intra-RAT MLB coordinates load distribution among inter-frequency cells. For this purpose,
MLB checks the load status of cells and transfers UEs from their serving cell to lightly loaded
inter-frequency neighboring cells.
In this document, lightly loaded inter-frequency neighboring cells can be LTE FDD or LTE
TDD cells.
For details about inter-RAT MLB, see Inter-RAT Mobility Load Balancing Feature Parameter
Description.
2.2 Benefits
MLB offers the following benefits:
l Relieves load imbalances among inter-frequency cells by transferring appropriate UEs to

lightly loaded inter-frequency neighboring FDD or TDD cells.
l Increases the access success rate, improves user experience with telecommunication
services, and achieves better resource utilization.
2.3 Architecture
Inter-frequency MLB can be categorized by triggering variables and the types of UEs to be
transferred, as shown in Figure 2-1. (PRB is short for physical resource block.)

eRAN
Figure 2-1 Triggering variables and types of UEs to be transferred for inter-frequency MLB
Table 2-1 lists the usage scenario of each MLB function.
Table 2-1 Usage scenarios of MLB functions
Function UEs to Applicab Intra- or Inter- Applicabl Support

Transfer le Entity eNodeB Load e Between RAN
Transfer? eNodeBs Sharing
Without with
X2? Common
Carriers or
Hybrid
RAN
Sharing?
User-number- RRC_REL Macro, Intra- and inter- No Yes

based MLB UEs micro, and eNodeB
LampSite
eNodeBs
UL-sync Macro, Intra- and inter- Yes Yes

UEs micro, and eNodeB
LampSite
eNodeBs
PRB-usage- UL-sync Macro, Intra- and inter- Yes Yes

based MLB UEs micro, and eNodeB
LampSite
eNodeBs
Load pre- RRC_REL Macro, Intra- and inter- Yes No

balancing in UEs micro, and eNodeB
fixed LampSite
proportions eNodeBs

eRAN
Function UEs to Applicab Intra- or Inter- Applicabl Support

Transfer le Entity eNodeB Load e Between RAN
Transfer? eNodeBs Sharing
Without with
X2? Common
Carriers or
Hybrid
RAN
Sharing?
Load pre- RRC_REL Macro and Intra-eNodeB N/A No

balancing in UEs LampSite
adaptive eNodeBs
proportions
Transport- UL-sync Micro Intra- and inter- No No

QoS-based UEs eNodeBs eNodeB
MLB
NOTE
For the definitions of UL-sync UEs and RRC_REL UEs, see 3.4 Type of UEs to Be Transferred.
Transport-QoS-based MLB requires PRB-usage-based MLB to be activated.

eRAN
Description 3 Related Concepts
3 Related Concepts
3.1 Cell Load

Inter-frequency MLB considers the following types of loads:
l Air interface load
The air interface load is represented by the PRB usage and the number of UL-sync UEs in
a cell.
NOTE
For details about how to calculate the PRB usage, see section 4.1.1 "PRB usage" in 3GPP TS 36.314
V10.2.0.
l Hardware load
The hardware load is represented by the central processing unit (CPU) and digital signal
processing (DSP) usage of the baseband processing unit.
l Transport network layer (TNL) load
The TNL load is represented by the S1 bandwidth usage. For details, see Transport
Resource Management Feature Parameter Description.
NOTE
According to section 9.2.36 "Load Indicator" in 3GPP TS 36.423 V10.5.0, the hardware and TNL loads
can be in one of the following states: LowLoad, MediumLoad, HighLoad, and OverLoad.
Currently, macro and LampSite eNodeBs support only air-interface-load-triggered MLB. Micro
eNodeBs support TNL-load-triggered MLB, as well as air-interface-load-triggered MLB.
eNodeBs consider the hardware load and TNL load when selecting candidate cells.
3.2 Cell Types

A source cell is the cell from which MLB transfers the load. Therefore, a source cell is the serving
cell of the UEs to be transferred.
A candidate cell is a neighboring cell that meets certain cell selection conditions for load transfer.
eNodeBs select target cells for MLB from candidate cells.
A target cell is a neighboring cell to which MLB attends to transfer the load.

eRAN
3.3 Overlapping Neighboring Cell

An overlapping neighboring cell is an inter-frequency neighboring cell for which the
EutranInterFreqNCell.OverlapInd parameter is set to YES(YES). You are advised to set this
parameter to YES(YES) for inter-frequency neighboring cells whose coverage area is the same
as, or overlaps a large portion of, the serving cell's coverage area.
3.4 Type of UEs to Be Transferred

eNodeBs transfer the following types of UEs:
l RRC_REL UE: An RRC_REL UE is a UE for which the UE inactivity timer specified by

the RrcConnStateTimer.UeInactiveTimer parameter expires and that the eNodeB is
about to release.
l UL-sync UE: If a UE in RRC_CONNECTED mode maintains uplink synchronization with
the eNodeB and the eNodeB allocates physical uplink control channel (PUCCH) and
sounding reference signal (SRS) resources for the UE, this UE is a UL-sync UE.
RRC_REL UE transfer reduces the potential source-cell load in terms of the number of UEs
without affecting user experience. eNodeBs can transfer both types of UEs simultaneously.
3.5 Exchange and Non-Exchange Modes

For inter-frequency MLB, eNodeBs select candidate cells in either of the following modes:
l Exchange mode
This mode is enabled when the InterFreqMlbSwitch(InterFreqMlbSwitch) option of the
CellAlgoSwitch.MlbAlgoSwitch parameter is selected. In this mode, eNodeBs select
candidate cells based on exchanged load information. The eNodeB has the load information
of neighboring cells and coordinates load distribution among inter-frequency cells based
on load differences among these cells, as shown in Figure 3-1.
Figure 3-1 MLB in exchange mode and non-exchange mode
l Non-exchange mode
This mode is enabled when the InterFreqBlindMlbSwitch
(InterFreqBlindMlbSwitch) option of the CellAlgoSwitch.MlbAlgoSwitch parameter is
selected. In this mode, eNodeBs do not exchange load information during candidate cell
selection. The eNodeB does not have the load information of neighboring cells and directly
transfers UEs to neighboring cells. Inter-frequency MLB without load information

eRAN
exchange aims to achieve that the local cell load is lower than an absolute threshold, as
shown in Figure 3-1.
The switches that control these two modes can be set on simultaneously.

eRAN
Description 4 MLB Procedure
4 MLB Procedure
The overall procedure for inter-frequency MLB can be divided into the following phases: MLB
triggering, candidate cell selection, target frequency selection, UE selection, load transfer, and
MLB termination. Figure 4-1 illustrates the overall procedure.
Figure 4-1 Overall procedure
NOTE
Load information exchange in the blue circle is present only in exchange mode.
After the MLB algorithm is enabled, the eNodeB starts load measurement and evaluation every
second. After MLB is triggered, the MLB algorithm repeats the procedure shown in Figure
4-1 within each period specified by the CellMLB.InterFreqLoadEvalPrd parameter. When the
MLB termination conditions are met, the MLB algorithm immediately stops the ongoing MLB
operations.

eRAN
Description 4 MLB Procedure
For UL-sync UEs, after MLB is triggered in a cell, the eNodeB performs MLB procedures at an
interval specified by the CellMLB.InterFreqLoadEvalPrd parameter and transfers UEs to
neighboring cells by handovers, as shown in Figure 4-2.
Figure 4-2 Example of handover intervals in MLB by transferring UL-sync UEs
For RRC_REL UEs, after MLB is triggered in a cell and the first MLB period specified by the
CellMLB.InterFreqLoadEvalPrd parameter elapses, the eNodeB performs cell reselections for
all released UEs within the succeeding MLB periods, as shown in Figure 4-3.
Figure 4-3 Example of cell reselection duration in MLB by transferring RRC_REL UEs

eRAN
Description 5 User-Number-based Inter-Frequency MLB
5 User-Number-based Inter-Frequency MLB
This chapter describes how the LOFD-070215 Intra-LTE User Number Load Balancing feature
works.
During user-number-based inter-frequency MLB, an eNodeB transfers some UL-sync UEs and
RRC_REL UEs to the selected neighboring cells to balance inter-frequency cell load.
User-number-based inter-frequency MLB is enabled if the following options are selected:
l The InterFreqMlbSwitch(InterFreqMlbSwitch), InterFreqBlindMlbSwitch

(InterFreqBlindMlbSwitch), or both options of the CellAlgoSwitch.MlbAlgoSwitch
parameter
l The UE_NUMBER_ONLY(UeNumMode) or PRB_OR_UE_NUMBER
(PrbOrUeNumMode) option of the CellMLB.MlbTriggerMode parameter
For details about how to deploy this type of MLB, see 13.1 LOFD-070215 Intra-LTE User
Number Load Balancing.

eRAN
5.1 MLB by Transferring RRC_REL UEs

If user-number-based inter-frequency MLB with load information exchange is enabled and the
IdleUE(IdleUE) option of the CellMLB.InterFreqUeTrsfType parameter is selected, the
eNodeB can transfer RRC_REL UEs for MLB.
5.1.1 MLB Triggering and Termination

Each second, an eNodeB measures the number of UL-sync UEs in a cell and compares the result
with the specified MLB threshold.
l The eNodeB starts MLB if the following condition is met continuously for 5s:
Number of UL-sync UEs in the cell CellMLB.InterFreqIdleMlbUeNumThd +
CellMLB.MlbUeNumOffset
l The eNodeB stops MLB if the following condition is met continuously for 5s:
Number of UL-sync UEs in the cell < CellMLB.InterFreqIdleMlbUeNumThd
The CellMLB.MlbUeNumOffset parameter is used to prevent user number fluctuations from

frequently triggering MLB.
5.1.2 Candidate Cell Selection

After triggering MLB, an eNodeB selects candidate cells from the inter-frequency neighboring
relation table (NRT) within each period specified by the CellMLB.InterFreqLoadEvalPrd
parameter. If the candidate cell list is empty, the eNodeB does not execute MLB during the
current MLB period.
In MLB by transferring RRC_REL UEs, the eNodeB must evaluate the load status of inter-
frequency neighboring cells based on load information exchange.
During candidate cell selection, the eNodeB first derives a preliminary list of candidate cells
from all inter-frequency neighboring cells. It then exchanges load information with the cells, as
described in 5.1.2.2 Load Information Exchange. Finally, the eNodeB filters the cells based
on load evaluation and generates a final list of candidate cells, as described in 5.1.2.3 Final
Candidate Cell Selection. Figure 5-1 illustrates the selection process.

eRAN
Figure 5-1 Process of candidate cell selection in exchange mode
When both exchange mode and non-exchange mode are enabled, the eNodeB selects candidate
cells only after load information exchange.
5.1.2.1 Preliminary Candidate Cell Selection

After triggering MLB, the eNodeB filters out the following cells from the inter-frequency NRT:
l Cells to which the success rate of handovers is less than 98% (This condition applies only
to MLB with load information exchange.)
l Cells for which the EutranInterFreqNCell.NoHoFlag parameter is set to
FORBID_HO_ENUM(Forbid Ho)
l Blacklisted inter-frequency cells configured in InterFreqBlkCell MOs
l Cells with the same physical cell identifier (PCI) on the same frequency in the NRT
l Cells on the frequencies for which the EutranInterNFreq.MlbTargetInd parameter is set
to NOT_ALLOWED(NOT_ALLOWED)
NOTE
The handover success rate considered involves all types of inter-frequency handovers. The handover
success rate is collected and updated once per minute.
Then, the eNodeB selects cells from the remaining inter-frequency neighboring cells to generate
the preliminary list of candidate cells. The selection adheres to the following criteria:
l If there are overlapping neighboring cells, for which the

EutranInterFreqNCell.OverlapInd parameter is set to YES(YES), the eNodeB selects
the following cells:
Intra-eNodeB overlapping neighboring cells
Inter-eNodeB overlapping neighboring cells served by eNodeBs that are connected to
the source eNodeB through X2 interfaces
l If no inter-frequency overlapping neighboring cell exists, the eNodeB selects cells as
described in Table 5-1.

eRAN
Table 5-1 Preliminary candidate cell selection (for the purpose of load information exchange)
CellMLB.LoadBalanceNCellScope Preliminary Candidate Cells

Parameter Value
ADAPTIVE(Adaptive) Preferentially intra-eNodeB neighboring cells

only; (if no intra-eNodeB neighboring cell exists
or is normal) inter-eNodeB neighboring cells
served by eNodeBs that are connected to the
source eNodeB through X2 interfaces
ALL(All) l Intra-eNodeB neighboring cells

l Inter-eNodeB neighboring cells served by
eNodeBs that are connected to the source
eNodeB through X2 interfaces
Example 1
As shown in Figure 5-2, MLB is triggered in cell 1 on frequency F1. Cell 1 detects that the
EutranInterNFreq.MlbTargetInd parameter values for its neighboring frequencies F2 and F3
are ALLOWED(ALLOWED) and NOT_ALLOWED(NOT_ALLOWED), respectively. In
this case, cells 2 and 3 on F2 are included in the preliminary list of candidate cells, but cells 4
and 5 on F3 are not.
Figure 5-2 Preliminary candidate cell selection among cells with different settings of the
EutranInterNFreq.MlbTargetInd parameter
Example 2
As shown in Figure 5-3, MLB is triggered in cell 1 on frequency F1. Cell 1 detects that the
EutranInterFreqNCell.OverlapInd parameter is set to YES(YES) only for its neighboring
cells 2 and 4. In this case, cells 2 and 4 are included in the preliminary list of candidate cells,
but cells 3 and 5 are not.

eRAN
Figure 5-3 Preliminary candidate cell selection among cells with different settings of the
EutranInterFreqNCell.OverlapInd parameter
5.1.2.2 Load Information Exchange

The serving cell performs load information exchange with the preliminary candidate cells in
different ways:
l For intra-eNodeB inter-frequency neighboring cells, the serving cell can acquire the load
status of the candidate cells directly (not through the X2 interface).
l For inter-eNodeB inter-frequency neighboring cells, the serving cell initiates a load status
request towards the candidate cells to exchange load information through the X2 interface.
The procedure for load information exchange with inter-eNodeB neighboring cells is as follows:
After determining the preliminary candidate cell list, the serving eNodeB sends a load status
request to all neighboring eNodeBs that serve the candidate cells. This message is used to request
the number of UL-sync UEs as well as hardware, capability, and TNL resource information of
these cells. In addition, this message contains the interval at which the cell load information
should be reported.
When these neighboring eNodeBs receive load information request messages, they send load
information response messages to the serving eNodeB if the candidate cells are active. After
that, the neighboring eNodeBs send the load status of the candidate cells to the serving cell at
the specified interval for load status update till the neighboring eNodeBs receive an update stop
message from the serving cell. If a candidate cell is inactive, X2 messages for load information
exchange with the cell are unnecessary.
If the serving cell receives a failure message from a neighboring cell, the neighboring cell is not
considered a qualified candidate cell for the current MLB period.
NOTE
According to 3GPP TS 36.423 V10.4.0, load information exchange messages do not contain the number
of UL-sync UEs. Therefore, load information is exchanged using private messages. For details about load
information exchange, see section 8.3.6 "Resource Status Reporting Initiation" in 3GPP TS 36.423 V10.4.0.
If a neighboring cell fails to send private messages to the serving cell for six consecutive times, the
neighboring cell will not be treated as a candidate cell in the next 10 minutes.

eRAN
5.1.2.3 Final Candidate Cell Selection

After load information exchange, the eNodeB generates a final list of candidate cells by removing
the neighboring cells that meet any of the following conditions:
l The success rate of handovers from the serving cell to the neighboring cell is less than 98%.
The handover success rate considered involves all types of inter-frequency handovers. The
handover success rate is collected and updated once per minute.
l The TNL load or hardware load of the neighboring cell is in the HighLoad or OverLoad
state.
l The ratio of the difference in the number of UL-sync UEs between the serving and
neighboring cells to the number of UL-sync UEs in the serving cell is less than or equal to
the CellMLB.UeNumDiffThd parameter value. The difference is calculated after the
bandwidths of the cells are converted to the same value.
This ratio is calculated as follows:

where:
A denotes the number of available PRBs of the serving cell.
SFs denotes the CellMLB.CellCapacityScaleFactor parameter value of the serving cell.
M indicates the number of UL-sync UEs in the serving cell.
B denotes the number of available PRBs of the neighboring cell.
SFt denotes the CellMLB.CellCapacityScaleFactor parameter value of the neighboring
cell.
N denotes the number of UL-sync UEs in the neighboring cell.
l The maximum number of UEs that the neighboring cell can accept from the serving cell
for MLB is less than 1. This number is calculated as follows:
. The definitions of the variables are the same as those in the

previous bullet.
If the candidate cell list is empty, the eNodeB does not execute MLB during the current MLB
period.
5.1.3 Target Frequency Selection

The eNodeB collects the operating frequencies of all the candidate cells and generates a
candidate frequency list. If the candidate cell uses multiple frequency band indicator (MFBI),
the central frequencies of the secondary frequency bands are also regarded as the target
frequencies.
For details about LBFD-070103 Multi-Band Compatibility Enhancement, see Multiple
Frequency Band Indicator Feature Parameter Description.
Then, the eNodeB selects target frequencies from the candidate frequency list. For MLB by
transferring RRC_REL UEs, the eNodeB may select one or several target frequencies. For details
about the priorities of the target frequencies, see 5.1.5 Load Transfer.

eRAN
When generating a target frequency list, the eNodeB selects intra-RAT neighboring frequencies
for which the EutranInterNFreq.CellReselPriorityCfgInd parameter is set to CFG
(Configure) and that meet one of the following conditions:
l The serving cell is configured with overlapping neighboring cells, and all overlapping
neighboring cells on the frequency are included in the candidate cell list.
l The serving cell is not configured with overlapping neighboring cells, and one of its
neighboring cells on the frequency is included in the candidate cell list.
5.1.4 UE Selection
The eNodeB selects RRC_REL UEs, which are about to be released because of
RrcConnStateTimer.UeInactiveTimer expiration, for MLB.
5.1.5 Load Transfer

The eNodeB sends each selected UE an RRCConnectionRelease message that carries the
IdleModeMobilityControlInfo IE to control cell reselection for the UE after the RRC connection
release. This IE contains the following information:
l Target frequencies and their dedicated priorities

l Length of the T320 timer, which is specified by the
RrcConnStateTimer.T320ForLoadBalance parameter
In the IdleModeMobilityControlInfo IE, the dedicated cell-reselection priorities of the

frequencies are sorted in the following order:
1. Target E-UTRA frequency set > non-target E-UTRA frequency set (including the serving
cell's operating frequency) > UTRA frequency set > GERAN frequency set
2. In each type of frequency set, the cell-reselection priorities are sorted as follows: SPID-
specific cell-reselection priorities > operator-specific dedicated cell-reselection priorities
> absolute cell-reselection priorities. SPID is short for subscriber profile ID.
According to the preceding prioritization rules, the eNodeB includes frequencies preferentially
with priorities from 7 to 0 in sequence in the IdleModeMobilityControlInfo IE. If a UE is
configured with SPID-specific cell-reselection priorities, the IdleModeMobilityControlInfo IE
contains only frequencies configured with SPID-specific cell-reselection priorities.
The target frequency selection is described as in 5.1.3 Target Frequency Selection.
For details about SPID-specific cell-reselection priorities, operator-specific cell-reselection

dedicated priorities, and absolute cell-reselection priorities, see Flexible User Steering Feature
Parameter Description, RAN Sharing Feature Parameter Description, and Idle Mode
Management Feature Parameter Description, respectively.
Example 1: If the target frequency set are the following listed in Table 5-2,
Table 5-2 Target frequency set
Target E-UTRA Frequency F1, F2, F3, F4

Set

eRAN
Non-Target E-UTRA F5, F6, F7

Frequency Set
Frequencies Configured with F5 > F1 > F2

SPID-specific Cell-
Reselection Priorities
Then, the frequencies contained in the IdleModeMobilityControlInfo IE are prioritized as listed

in Table 5-3.
Table 5-3 Frequency priority
Frequency F1 F2 F5
Priority 7 6 5
Example 2: If the target frequency set are the following listed in Table 5-4,
Table 5-4 Target frequency set
Target E-UTRA Frequency F1, F2, F3, F4

Set
Non-Target E-UTRA F5, F6, F7

Frequency Set
Frequencies Configured with F6 > F3 > F1

Operator-specific Cell-
Reselection Dedicated
Priorities
Frequencies Configured with F6 > F5 > F1 > F2 > F3 > F4 > F7

Absolute Cell-Reselection
Priorities
Then, the frequencies contained in the IdleModeMobilityControlInfo IE are prioritized as listed

in Table 5-5.
Table 5-5 Frequency priority
Freque F3 F1 F2 F4 F6 F5 F7
ncy
Priority 7 6 5 4 3 2 1

eRAN
NOTE
For details about frequency priorities, see section 6.2.2 "Message definitions" in 3GPP TS 36.331 V10.3.0.
After a UE receives the RRCConnectionRelease message, within the T320 timer length, the UE
performs cell reselection based on the dedicated priorities. For details about priority handling,
see section 5.2.4.1 "Reselection priorities handling" in 3GPP TS 36.304 V10.3.0.
5.2 MLB by Transferring UL-Sync UEs

If user-number-based inter-frequency MLB is enabled and the SynchronizedUE
(SynchronizedUE) option of the CellMLB.InterFreqUeTrsfType parameter is selected, the
eNodeB can transfer UL-sync UEs for MLB.

An eNodeB periodically measures the number of UL-sync UEs in a cell and compares the result
with the specified MLB threshold.
Number of UL-sync UEs in the cell CellMLB.InterFreqMlbUeNumThd +
Number of UL-sync UEs in the cell < CellMLB.InterFreqMlbUeNumThd


During candidate cell selection, the eNodeB obtains a preliminary list of candidate cells from
all inter-frequency neighboring cells, filters them, and then generates a final list of candidate
cells.
For MLB by transferring UL-sync UEs, candidate cell selection may or may not involve load
information exchange.
l If exchange mode is enabled, the eNodeB performs load information exchange (as
described in 5.1.2.2 Load Information Exchange) and then generates a final list of
candidate cells by removing certain neighboring cells (as described in 5.1.2.3 Final
Candidate Cell Selection). Figure 5-4 illustrates the selection process.

eRAN
Figure 5-4 Process of candidate cell selection in exchange mode
l If non-exchange mode is enabled, the eNodeB does not perform load information exchange.
The eNodeB compares the number of UL-sync UEs in the serving cell to the offload
threshold (which is equal to the sum of the CellMLB.InterFreqMlbUeNumThd and
CellMLB.InterFrqUeNumOffloadOffset parameter values) and then generates the final
candidate cell list, as illustrated in Figure 5-5.
If the cell load is greater than or equal to the offload threshold, the eNodeB removes
cells in penalty to generate the final candidate cell list.
If the cell load is smaller than the offload threshold, the final candidate cell list is empty.

eRAN
Figure 5-5 Process of candidate cell selection in non-exchange mode
The eNodeB imposes a penalty on a neighboring cell if the neighboring cell rejects a load-
based incoming handover request sent from the source cell. The penalty starts from the
current MLB period, whose length is defined by CellMLB.InterFreqLoadEvalPrd, and
lasts for CellMLB.CellPunishPrdNum MLB periods.
l If both exchange mode and non-exchange mode are enabled, the final list of candidate cells
includes all the candidate cells selected in the two modes, as illustrated in Figure 5-6.

eRAN
Figure 5-6 Process of candidate cell selection when both exchange and non-exchange
modes are enabled
5.2.2.1 Preliminary Candidate Cell Selection

The mechanism for preliminary filtering for candidate cell selection in MLB by transferring UL-
sync UEs is the same as that in MLB by transferring RRC_REL UEs. For details, see 5.1.2.1
Preliminary Candidate Cell Selection.
Then, the eNodeB evaluates the remaining inter-frequency neighboring cells to generate a
preliminary list of candidate cells. The evaluation varies with the
CellAlgoSwitch.MlbAlgoSwitch parameter setting.
Scenario 1
If the InterFreqMlbSwitch(InterFreqMlbSwitch) option of the
CellAlgoSwitch.MlbAlgoSwitch parameter is selected and the InterFreqBlindMlbSwitch
(InterFreqBlindMlbSwitch) option of the same parameter is not, the selection adheres to the
following criteria:

the following cells:
Intra-eNodeB overlapping neighboring cells
Inter-eNodeB overlapping neighboring cells served by eNodeBs that are connected to
the source eNodeB through X2 interfaces

eRAN
Table 5-6 Preliminary candidate cell selection (for the purpose of load information
exchange)
CellMLB.LoadBalanceN- Preliminary Candidate Cells

CellScope Parameter Value
ADAPTIVE(Adaptive) Preferentially intra-eNodeB neighboring cells only;

(if no intra-eNodeB neighboring cell exists or is
normal) inter-eNodeB neighboring cells served by
eNodeBs that are connected to the source eNodeB
through X2 interfaces
ALL(All) l Intra-eNodeB neighboring cells

l Inter-eNodeB neighboring cells served by
eNodeBs that are connected to the source eNodeB
through X2 interfaces
Scenario 2
If the InterFreqBlindMlbSwitch(InterFreqBlindMlbSwitch) option of the
CellAlgoSwitch.MlbAlgoSwitch parameter is selected and the InterFreqMlbSwitch
(InterFreqMlbSwitch) option of the same parameter is not, the selection adheres to the
following criteria:

the overlapping neighboring cells.
Table 5-7 Preliminary candidate cell selection (not for the purpose of load information
exchange)
CellMLB.LoadBalanceNCellScope Parameter Preliminary Candidate

Value Cells
ADAPTIVE(Adaptive) Inter-eNodeB neighboring cells
ALL(All) All neighboring cells (including

intra- and inter-eNodeB
neighboring cells)
Scenario 3
If both the InterFreqBlindMlbSwitch(InterFreqBlindMlbSwitch) and
InterFreqMlbSwitch(InterFreqMlbSwitch) options of the CellAlgoSwitch.MlbAlgoSwitch
parameter are selected, the selection adheres to the following criteria:

eRAN

the overlapping neighboring cells.
Table 5-8 Preliminary candidate cell selection (some cells selected for the purpose of load
information exchange and others not)
CellMLB.LoadBalanceNCellScope Preliminary Candidate Cells

Parameter Value
ADAPTIVE(Adaptive) Preferentially intra-eNodeB neighboring

cells only; (if no intra-eNodeB
neighboring cell exists or is normal) inter-
eNodeB neighboring cells
ALL(All) All neighboring cells (including intra-

and inter-eNodeB neighboring cells)
5.2.2.2 Load Information Exchange

For details, see 5.1.2.2 Load Information Exchange.
5.2.2.3 Final Candidate Cell Selection

For details, see 5.1.2.3 Final Candidate Cell Selection.

The eNodeB collects the operating frequencies of all the candidate cells and generates a
candidate frequency list.
The eNodeB selects the target frequencies for measurements by using one of the following
methods, depending on the CellMLB.FreqSelectStrategy parameter setting:
l If the parameter is set to FAIRSTRATEGY(FairStrategy):

The eNodeB randomly selects a frequency from the candidate frequencies.
l If the parameter is set to PRIORITYBASED(PriorityBased):
The eNodeB selects target frequencies based on the frequency priorities specified by the
EutranInterNFreq.MlbFreqPriority parameter. If several frequencies have the same
priority, the eNodeB selects all these frequencies for measurements.
If intra-RAT inter-frequency MLB and inter-RAT MLB to UTRAN are triggered
simultaneously, the eNodeB considers all frequency priorities defined by the
EutranInterNFreq.MlbFreqPriority and UtranNFreq.MlbFreqPriority parameters and
selects the highest-priority frequencies as target frequencies.

eRAN
NOTE
An eNodeB imposes a penalty on a frequency selected based on MLB priorities if no UE is transferred to

the frequency within CellMLB.PunishJudgePrdNum MLB periods. The length of each MLB period is
defined by CellMLB.InterFreqLoadEvalPrd. During the penalty, the eNodeB no longer selects the
frequency as a target frequency. The penalty starts from the next MLB period and lasts for
CellMLB.FreqPunishPrdNum MLB periods.
5.2.4 UE Selection
The eNodeB selects UEs that meet all the following conditions:
l The uplink and downlink PRB usage values of a single UE are less than or equal to the
value of the CellMLB.MlbUeSelectPRBThd parameter. The PRB usage of a single UE is
calculated as follows:
, where UeRbNumber denotes the number of PRBs used by the

UE and CellResource denotes the total number of PRBs in the source cell.
l The UE is not performing a service with QCI 1.
l The UE is in the UL-sync state.
l The UE is served by the PLMN to which a cell in the final candidate list belongs. (This
condition takes effect only when inter-PLMN handover is disabled.)
l The UE is not in the carrier aggregation (CA) state.
l The SPIDCFG.InterFreqMlbSwitch parameter is set to TRUE(TRUE) for the UE.
NOTE
After an eNodeB configures a secondary serving cell (SCell) for a CA UE, the UE is in the CA state. Micro
eNodeBs do not support CA. Therefore, for micro eNodeBs, the MLB algorithm does not check the CA
status of UEs.
Total Number of UEs Selected for MLB in Exchange Mode

l When only exchange mode is enabled or both exchange and non-exchange modes are
enabled and there are neighboring cells selected in exchange mode, the eNodeB calculates
the maximum number of UEs to be transferred within an MLB period by using the following
formula:
Maximum number of UEs that can be transferred to a certain candidate cell = Min{(B
SFt M A SFs N)/(A SFs + B SFt), M CellMLB.InterFreqMlbUeNumThd +
1, CellMLB.MlbMaxUeNum}
A denotes the total number of PRBs in the source cell.
SFs denotes the CellMLB.CellCapacityScaleFactor parameter value of the serving cell.
B indicates the total number of PRBs in a certain candidate cell.
SFt denotes the CellMLB.CellCapacityScaleFactor parameter value of the candidate
cell.
M indicates the number of UL-sync UEs in the source cell.
N indicates the number of UL-sync UEs in the candidate cell.
The CellMLB.MlbMaxUeNum parameter specifies the user-configured maximum
number of UEs that can be transferred from the source cell in a single MLB period.

eRAN
The result of "(B SFt M A SFs N)/(A SFs + B SFt)" indicates the number
of UEs to be transferred so that the number of UEs per unit of bandwidth in the source
cell will equal that in the candidate cell.
The result of "M CellMLB.InterFreqMlbUeNumThd + 1" indicates the minimum
number of UEs to be transferred so that the source cell can exist MLB.
If there are multiple candidate cells, the maximum total number of UL-sync UEs to be
transferred is the smallest value among the maximum numbers of UL-sync UEs that can
be transferred to each candidate cell.
Total Number of UEs Selected for MLB in Non-Exchange Mode

When only non-exchange mode is enabled, the eNodeB calculates the maximum number of UEs
to be transferred within an MLB period by using the following formula: Maximum number of
UEs that can be transferred = Min{M CellMLB.InterFreqMlbUeNumThd + 1,
CellMLB.MlbMaxUeNum}
M denotes the number of UL-sync UEs in the source cell.
5.2.5 Load Transfer

There are two methods of transferring UL-sync UEs that support inter-frequency handover:
measurement-based handover and blind handover. If the CellMlbHo.MlbHoInProtectMode
parameter is set to PROTECTTIMERMODE(PROTECTTIMER MODE), the eNodeB does
not re-transfer UEs that were handed over to the local cell for MLB within a period specified by
the CellMlbHo.MlbHoInProtectTimer parameter. In inter-frequency handovers for MLB, the
handover request message contains the cause value of "Reduce Load in Serving Cell".
Measurement-based Handover
In a measurement-based handover, the UE performs measurements on one or more frequencies
specified in the measurement configuration delivered from the eNodeB. If the eNodeB has not
received the measurement report from the UE within three seconds, the eNodeB instructs the
UE to terminate the measurements. If the eNodeB has received the measurement report from
the UE, the eNodeB selects the handover policies based on the measure report, exchange or non-
exchange mode, and target cell selection policy for load-based handovers.
During MLB with load information exchange, the eNodeB selects the target cell for a handover
based on the setting of the CellMLB.MlbHoCellSelectStrategy parameter.
l If this parameter is set to ONLY_STRONGEST_CELL(Only Try Strongest Cell), the

eNodeB selects the strongest cell in a measurement report. The eNodeB checks whether
this cell meets the following conditions. If this cell meets the following conditions, the
eNodeB sends a handover request to this cell. Otherwise, the eNodeB does not send a
handover request or try any other cells in the measurement report.
This cell is included in the final list of candidate cells for MLB.
This cell is not in the areas indicated by the Handover Restriction List IE in the INITIAL
CONTEXT SETUP REQUEST message sent from the MME.
l If this parameter is set to PERMIT_NON_STRONGEST_CELL(Permit Trying Non-
Strongest Cell), the eNodeB can try non-strongest neighboring cells in the measurement
report when the strongest cell does not exist in the final list of candidate cells.

eRAN
When non-exchange mode is enabled or both exchange mode and non-exchange mode are
enabled, the eNodeB selects the strongest cell in a measurement report. The target cell selection
method is the same as that with the CellMLB.MlbHoCellSelectStrategy parameter set to
ONLY_STRONGEST_CELL(Only Try Strongest Cell) for MLB in exchange mode.
The EutranInterNFreq.MlbInterFreqHoEventType parameter specifies whether load-based
inter-frequency handovers to cells on a neighboring E-UTRA frequency can be triggered by
event A4 or A5. The value EventA5(EventA5) takes effect only if the LOFD-081227 Intra-LTE
Load Balancing for Non-cosited Cells feature is activated. For details, see 8 Inter-Frequency
MLB for Non-Cosited Cells.
The principle of triggering load-based inter-frequency handovers by event A4 or A5 is the similar
to that of triggering coverage-based inter-frequency handovers by event A4. For details, see
Intra-RAT Mobility Management in Connected Mode.
The differences the triggering thresholds. Table 5-9 lists the thresholds for event A4 or A5 that
triggers load-based inter-frequency handovers.
Table 5-9 Thresholds for event A4 or A5 that triggers load-based inter-frequency handovers
Parameter Parameter ID Description

Name
Load Based InterFreqHoGroup. These parameters are set for each QCI.
Interfreq RSRP InterFreqLoadBasedH The threshold offset parameter is set for each
threshold oA4ThdRSRP inter-frequency neighboring frequency.
Load Based InterFreqHoGroup. l The sum of the
Interfreq RSRQ InterFreqLoadBasedH InterFreqHoGroup.InterFreqLoadBas
threshold oA4ThdRSRQ edHoA4ThdRSRP and
EutranInterNFreq.IfMlbThdRsrpOff-
Inter-Freq Mlb EutranInterNFreq. set parameter values specifies the
Threshold RSRP IfMlbThdRsrpOffset reference signal received power (RSRP)
Offset threshold for event A4 and the RSRP
threshold 2 for event A5 that trigger load-
MLB Inter-Freq InterFreqHoGroup.
based inter-frequency handovers.
Handover A5 MlbInterFreqHoA5Th
Threshold1 d1Rsrp l The
RSRP InterFreqHoGroup.InterFreqLoadBas
edHoA4ThdRSRQ parameter specifies
MLB Inter-Freq InterFreqHoGroup. the reference signal received quality
Handover A5 MlbInterFreqHoA5Th (RSRQ) threshold for event A4 and the
Threshold1 d1RsrQ RSRQ threshold 2 for event A5 that trigger
RSRQ load-based inter-frequency handovers.
The IntraRatHoComm.InterFreqHoA4TrigQuan parameter specifies the triggering quantity

for event A4 or A5 that triggers load-based inter-frequency handovers. Other parameters related
to event A4 or A5 that triggers load-based inter-frequency handovers are the same as the
parameters related to event A4 that triggers coverage-based inter-frequency handovers.
l If the IntraRatHoComm.InterFreqHoA4TrigQuan parameter is set to BOTH, the
eNodeB delivers two sets of measurement configurations related to event A4 or A5, with
one being RSRP-based and the other RSRQ-based. When either the RSRP-based or RSRQ-

eRAN
based entering condition of event A4 or A5 is met, the UE reports event A4 or A5. An inter-
frequency handover is triggered only when both measurement quantities meet the entering
condition for event A4 or A5.
l When IntraRatHoComm.InterFreqHoA4TrigQuan parameter is set to RSRP or
RSRQ, the eNodeB delivers a measurement configuration related to event A4 or A5 for
which the triggering quantity is RSRP or RSRQ, respectively.
The IntraRatHoComm.InterFreqHoA4RprtQuan parameter specifies the reporting quantity

to be included in the measurement reports after event A4 or A5 is triggered.
l When the IntraRatHoComm.InterFreqHoA4RprtQuan parameter is set to BOTH, both

RSRP-based and RSRQ based events are reported.
l When IntraRatHoComm.InterFreqHoA4RprtQuan is set to SAME_AS_TRIG_QUAN
(Same as Trig Quan), the reporting quantity is the same as the triggering quantity of event
A4 or A5 that triggers load-based inter-frequency handovers.
Based on measurement reports, the eNodeB performs inter-frequency handovers on UEs that
meet handover conditions. If a selected UE fails to be transferred to the target frequency within
a period specified by CellMLB.InterFreqLoadEvalPrd, the eNodeB will not select the UE for
MLB until the timer specified by CellMLB.MlbUeSelectPunishTimer expires.
For details about inter-frequency handovers, see Intra-RAT Mobility Management in Connected
Mode Feature Parameter Description.
Blind Handover
Blind handovers work only if the InterFreqMlbBlindHo(InterFreqMlbBlindHo) option of
the CellAlgoSwitch.MlbHoMode parameter is selected. The eNodeB selects the target cell with
the highest EutranInterFreqNCell.BlindHoPriority from neighboring cells that meet the
following conditions:
l This cell is included in the final list of candidate cells for MLB.
l This cell is not in the areas indicated by the Handover Restriction List IE in the INITIAL
CONTEXT SETUP REQUEST message sent from the MME.
l The EutranInterFreqNCell.BlindHoPriority parameter value is 1 to 16.
If there are target cells that meet the preceding conditions, user-number-based inter-frequency
MLB transfers UL-sync UEs to the target cells through blind handovers.
Handover Request Admission

If non-exchange mode is enabled and the target cell is in the high load state, then:
l If the target cell is an intra-eNodeB cell of the source cell, the source cell does not send a
handover request to the target cell.
l If the target cell is an inter-eNodeB cell of the source cell, the target cell rejects incoming
handover requests withe the cause value of "Reduce Load in Serving Cell".
In user-number-based MLB, the high load state is defined as follows:
l A cell enters the high load state if the following condition is met continuously for 5s:
Number of UL-sync UEs in the cell CellMLB.InterFreqMlbUeNumThd +
CellMLB.InterFrqUeNumOffloadOffset

eRAN
l The cell exits the high load state if the following condition is met continuously for 5s:
Number of UL-sync UEs in the cell < CellMLB.InterFreqMlbUeNumThd +
CellMLB.InterFrqUeNumOffloadOffset CellMLB.MlbUeNumOffset
If a target cell rejects a handover request from the source cell, the source eNodeB will not select
this target cell as a candidate cell. The penalty starts from the current MLB period, whose length
is defined by CellMLB.InterFreqLoadEvalPrd, and lasts for CellMLB.CellPunishPrdNum
MLB periods.
If a procedure of user-number-based MLB by transferring UL-sync UEs is triggered in the target

cell, handovers to this cell are handled as follows:
l If the target cell is an intra-eNodeB cell of the source cell, the source cell does not send a
handover request to the target cell.
l If the target cell is an inter-eNodeB cell of the source cell, the target cell rejects incoming
handover requests with the cause value of "Resource optimization handover" or "Handover
Optimization".
NOTE
For details about handover request causes, see section 9.2.1.3 "Cause" in 3GPP TS 36.413 V10.6.0 and
section 9.2.6 "Cause" in 3GPP TS 36.423 V11.1.0.

eRAN
Description 6 PRB-Usage-based Inter-Frequency MLB
6 PRB-Usage-based Inter-Frequency MLB
This chapter describes how the LOFD-001032 Intra-LTE Load Balancing feature (referred to
as PRB-usage-based inter-frequency MLB in this chapter) works.
During PRB-usage-based inter-frequency MLB, an eNodeB transfers some UL-sync UEs to the
selected neighboring cells to balance inter-frequency cell load.
PRB-usage-based inter-frequency MLB is enabled if the following options are selected:
l The InterFreqMlbSwitch(InterFreqMlbSwitch), InterFreqBlindMlbSwitch

(InterFreqBlindMlbSwitch), or both options of the CellAlgoSwitch.MlbAlgoSwitch
parameter
l The PRB_ONLY(PrbMode) or PRB_OR_UE_NUMBER(PrbOrUeNumMode) option
of the CellMLB.MlbTriggerMode parameter
For details about how to deploy this type of MLB, see 13.2 LOFD-001032 Intra-LTE Load
Balancing.

eRAN
6.1 MLB Triggering and Termination

After PRB-usage-based inter-frequency MLB is enabled for a cell, an eNodeB measures the
PRB usage and number of UL-sync UEs in the cell each second. When counting the number of
UL-sync UEs, the eNodeB counts both UL-sync UEs in the non-CA state and equivalent UEs
in the CA state. If a CA UE is served by N aggregated component carriers, including PCCs and
SCCs, this CA UE is counted as N equivalent UEs.
PRB Usage Type

The following types of PRB usage may trigger or stop MLB:
l Uplink GBR PRB usage

l Downlink GBR PRB usage
l Uplink total PRB usage (uplink GBR + non-GBR)
l Downlink total PRB usage (downlink GBR + non-GBR)
GBR PRB usage takes priority over total PRB usage in triggering and stopping MLB. If the
GBR PRB usage is greater than the specified MLB threshold, MLB is triggered by GBR PRB
usage. The eNodeB will transfer UEs with GBR bearers. If the GBR PRB usage is less than but
the total PRB usage is greater than the specified MLB threshold, MLB is triggered by total PRB
usage. The eNodeB will transfer UEs without GBR bearers.
MLB Triggering
The eNodeB starts PRB-usage-based inter-frequency MLB if the following conditions are met
continuously for 5s:
l One type of PRB usage of the cell CellMLB.InterFreqMlbThd + CellMLB.LoadOffset

l Number of UL-sync UEs in the cell CellMLB.MlbMinUeNumThd +
CellMLB.MlbMinUeNumOffset
MLB Termination
The eNodeB stops MLB if one of the following conditions is met continuously for 5s:
l Each type of PRB usage of the cell < CellMLB.InterFreqMlbThd

l Number of UL-sync UEs in the cell < CellMLB.MlbMinUeNumThd
6.2 Candidate Cell Selection

The process of candidate cell selection for PRB-usage-based inter-frequency MLB is similar to
that for user-number-based inter-frequency MLB, except for the load information exchange
procedure and final candidate cell selection.
Preliminary Candidate Cell Selection

For details, see 5.2.2.1 Preliminary Candidate Cell Selection.

eRAN
Load Information Exchange

l If the CellMLB.MlbTriggerMode parameter is set to PRB_ONLY(PrbMode), the load
information is exchanged using protocol-defined messages. For details, see 3GPP TS
36.423.
The process of load information exchange for PRB-usage-based inter-frequency MLB is
similar to that for user-number-based inter-frequency MLB. The difference is that the
eNodeB obtains the information about the hardware load, TNL load, and PRB usage of the
neighboring cells for PRB-usage-based inter-frequency MLB.
The PRB usage information includes:
Downlink: GBR PRB usage, non-GBR PRB usage, and total PRB usage
Uplink: GBR PRB usage, non-GBR PRB usage, and total PRB usage
l If the CellMLB.MlbTriggerMode parameter is set to PRB_OR_UE_NUMBER
(PrbOrUeNumMode), the load information is exchanged using Huawei private messages
and includes the number of UEs that an individual neighboring cell can accept. For a
neighboring cell, the number of UEs that it can accept equals its
CellMLB.InterFreqMlbUeNumThd parameter value minus the number of UL-sync UEs
in it.
For details about load information exchange for user-number-based inter-frequency MLB, see
5.1.2.2 Load Information Exchange.
Final Candidate Cell Selection

l If the CellMLB.MlbTriggerMode parameter is set to PRB_ONLY(PrbMode), then:
In exchange mode, after load information exchange, the eNodeB generates a final candidate
cell list by removing the neighboring cells that meet any of the following conditions:
The success rate of handovers from the serving cell to the neighboring cell is less than
98%. The handover success rate considered involves all types of inter-frequency
handovers. The handover success rate is collected and updated once per minute.
The TNL load or hardware load of the neighboring cell is in the HighLoad or OverLoad
state.
The difference in the MLB-triggering PRB usage between the serving and neighboring
cells is less than the CellMLB.LoadDiffThd parameter value. The difference is
calculated based on the converted bandwidths of the cells.
The neighboring cell is in penalty. (The eNodeB imposes a penalty on a neighboring
cell if the cell rejects an incoming handover request with the cause value of "Reduce
Load in Serving Cell".)
When the PRB usage of the serving cell is less than the sum of the
CellMLB.InterFreqMlbThd + CellMLB.InterFreqOffloadOffset parameter values,
the serving cell does not exchange load information with the neighboring cell or the
serving cell fails to obtain the load information of the neighboring cell.

eRAN
NOTE
The MLB-triggering PRB usage of the serving cell and that of the neighboring cell are calculated
as follows:
X and M denote the numbers of available and used PRBs of the cell with a larger bandwidth,
respectively. Y and N denote the numbers of available and used PRBs of the other cell with a
smaller bandwidth, respectively.
PRB usage of the cell with a larger bandwidth =
PRB usage of the other cell with a smaller bandwidth =

In final candidate cell selection for MLB in non-exchange mode, the eNodeB filters out
neighboring cells in penalty to generate the final candidate cell list. The in-penalty
neighboring cell is a cell that rejects an incoming handover request with the cause value of
"Reduce Load in Serving Cell".
(PrbOrUeNumMode), the eNodeB additionally removes the candidate cells that cannot
accept more UEs for MLB in exchange mode. This prevents ping-pong MLB caused by
the triggering of user-number-based inter-frequency MLB after load transfer.
6.3 Target Frequency Selection

For details, see 5.2.3 Target Frequency Selection.
6.4 UE Selection
PRB-usage-based inter-frequency MLB transfers UL-sync UEs. The
CellMLB.MlbMaxUeNum parameter specifies the maximum number of UEs that can be
transferred to target cells in an MLB period.
When selecting UEs, the eNodeB considers the following factors:
l PRB usage of individual UEs
l Type of PRB usage that triggers MLB
l UEs in the CA state are not selected.
l UEs for which the SPIDCFG.InterFreqMlbSwitch parameter is set to FALSE(FALSE)
are not selected.
NOTE
After an eNodeB configures an SCell for a CA UE, the UE is in the CA state.

Micro eNodeBs do not support CA. Therefore, for micro eNodeBs, the MLB algorithm does not check the
CA status of UEs.
PRB Usage of a UE
The PRB usage of a UE is calculated by using the following formula:
PRB usage of a UE =

eRAN
where UeRbNumber indicates the number of PRBs used by the UE and CellResource indicates
the total number of PRBs in the cell.
Selection Criteria
The eNodeB evaluates both uplink and downlink PRB usage of individual UEs to prevent further
MLB in the other direction (uplink or downlink; opposite to the direction that has triggered the
current MLB procedure) from the target cell.
For example, if MLB is triggered by downlink GBR PRB usage, the eNodeB selects UEs that
meet the following conditions:
l CellMLB.MlbUeSelectPRBThd < Downlink GBR PRB usage of a single UE Maximum
total PRB usage of UEs to be transferred
The lower limit helps ensure that the UE transfer efficiently decreases the source cell
load.
The upper limit is used to prevent the UE transfer from causing overload in the target
cell while decreasing the source cell load.
The upper limit of the total PRB usage of all UEs to be transferred during the current MLB
period can be calculated by using the following formula:
Upper limit to the total PRB usage of all UEs to be transferred to a certain candidate cell
= Min{PRB usage of the source cell (CellMLB.InterFreqMlbThd
CellMLB.LoadOffset 1%), correction factor x [0.5 x (PRB usage of the source cell
PRB usage of the candidate cell) + CellMLB.LoadDiffThd x
CellMLB.LoadTransferFactor]}
The result of "PRB usage of the source cell (CellMLB.InterFreqMlbThd
CellMLB.LoadOffset 1%)" indicates the extent that the PRB usage of the source cell
exceeds the MLB triggering threshold.
The result of "PRB usage of the source cell PRB usage of a certain candidate cell"
indicates the PRB usage difference between the source and candidate cells.
The CellMLB.LoadDiffThd parameter specifies the load difference threshold.
The CellMLB.LoadTransferFactor parameter specifies the factor used to control the
total load to be transferred within the current MLB period. The default value is 0%. A
larger value of this parameter indicates that more load can be transferred.
Correction factor: Consider that the numbers of available RBs in the source cell and and
target cell are A and B, respectively. If A is greater than B, the value of the correction
factor is equal to B/A. Otherwise, the value is 1.
In MLB without load information exchange, the source and candidate cell load cannot be
compared. Therefore, the upper limit to the total PRB usage is determined by the result of
"PRB usage of the source cell (CellMLB.InterFreqMlbThd CellMLB.LoadOffset) +
1%}
l Uplink GBR PRB usage of the UE CellMLB.MlbUeSelectPRBThd
This restriction helps prevent uplink GBR PRB usage in the target cell from triggering
MLB after the UE is transferred to the target cell.
6.5 Load Transfer

Like UL-sync UE transfer in user-number-based inter-frequency MLB, there are two methods
of transferring UEs in PRB-usage-based inter-frequency MLB: blind handover and

eRAN
measurement-based handover. Only when UEs performing services with a QCI of 1 are selected,
the eNodeB filters out cells that prohibit handovers of UEs running VoIP services. For details,
see Intra-RAT Mobility Management in Connected Mode Feature Parameter Description.
Compared with user-number-based inter-frequency MLB, load transfer in PRB-usage-based

inter-frequency MLB uses a different definition of high load state in handover admission and
MLB triggering conditions.
In PRB-usage-based MLB, the high load state is defined as follows:
l A cell enters the high load state if the following condition is met continuously for 5s: PRB
usage of the cell CellMLB.InterFreqMlbThd + CellMLB.InterFreqOffloadOffset
l The cell exits the high load state if the following condition is met continuously for 5s: PRB
usage of the cell CellMLB.InterFreqMlbThd + CellMLB.InterFreqOffloadOffset
CellMLB.LoadOffset
For details about MLB triggering conditions, see 6.1 MLB Triggering and Termination.
When both PRB-usage-based inter-frequency MLB and user-number-based inter-frequency

MLB by transferring UL-sync UEs are enabled, a cell enters or exits the high load state and an
MLB procedure is triggered if the related conditions in any of the two algorithms are met.
For details about load transfer in user-number-based inter-frequency MLB, see 5.2.5 Load
Transfer.

eRAN
Description 7 Operator-Level Inter-Frequency MLB
7 Operator-Level Inter-Frequency MLB
This chapter describes how the LOFD-070204 Operator Load Based Intra-LTE MLB feature
works.
Like cell-level inter-frequency MLB (described in 5 User-Number-based Inter-Frequency

MLB and 6 PRB-Usage-based Inter-Frequency MLB), operator-level inter-frequency MLB
is classified into user-number-based MLB and PRB-usage-based MLB.
For details about how to deploy this type of MLB, see 13.3 LOFD-070204 Operator Load
Based Intra-LTE MLB.

eRAN
7.1 Operator-Level User-Number-based Inter-Frequency

MLB
In operator-level user-number-based MLB, the eNodeB evaluates the number of UL-sync UEs
served by each operator in a cell. If the user number for an operator is large, the eNodeB selects
the inter-frequency neighboring cells with a small number of UL-sync UEs served by the
operator.
In addition, the eNodeB selects certain UL-sync and RRC_REL UEs and transfers them to the
selected cells to achieve load balancing between inter-frequency neighboring cells for the
operator.
Operator-level user-number-based MLB is enabled if the parameter settings are as follows:
l The UE_NUMBER_ONLY(UeNumMode) or PRB_OR_UE_NUMBER

(PrbOrUeNumMode) option of the CellMLB.MlbTriggerMode parameter is selected.
l The InterFreqMlbSwitch(InterFreqMlbSwitch) or InterFreqBlindMlbSwitch
selected.
l The SHARING(SHARING) option of the CellMLB.InterFreqMLBRanShareMode
parameter is selected.
l The CellAlgoSwitch.RanShareModeSwitch parameter is set to ON(On).
7.1.1 MLB by Transferring RRC_REL UEs

If operator-level user-number-based inter-frequency MLB is enabled and the IdleUE(IdleUE)
option of the CellMLB.InterFreqUeTrsfType parameter is selected, the eNodeB can transfer
RRC_REL UEs for MLB.
7.1.1.1 MLB Triggering and Termination

An eNodeB periodically measures the number of UL-sync UEs served by each operator in a cell
and compares the result with the operator-specific user-number-based MLB threshold.
Number of operator-specific UL-sync UEs < CellMLB.InterFreqIdleMlbUeNumThd x
P + CellMLB.MlbUeNumOffset
Number of operator-specific UL-sync UEs < CellMLB.InterFreqIdleMlbUeNumThd x
P
P indicates the operator-specific percentage of CellOp.OpUeNumRatio settings. For example,

the serving cell is shared by N operators. Then, the percentage for operator A1 is calculated as
follows:

eRAN
OpA1UeNumRatio is the CellOp.OpUeNumRatio parameter value defined for operator A1. This
parameter specifies the percentage of the user number capacity allocated to the operator.

7.1.1.2 Candidate Cell Selection

The candidate cell selection procedure is similar to that described in 5.1.2 Candidate Cell
Selection.

In addition to the activities described in 5.1.2.1 Preliminary Candidate Cell Selection, the
eNodeB filters out inter-operator neighboring cells.

In the exchange procedure described in 5.1.2.2 Load Information Exchange, the load
information exchange messages convey the operator-specific number of UL-sync UEs as well
as hardware and TNL resource information of neighboring cells. The messages also specify the
interval at which the cell load information should be reported. The neighboring cells periodically
send the operator-specific load information to the serving cell at the specified load update
interval. If a candidate cell is not activated, messages transmitted over the X2 interface for load
information exchange with it are unnecessary.

The selection mechanism is similar to that described in 5.1.2.3 Final Candidate Cell
Selection. The difference is that the eNodeB considers bandwidth resources reserved for the
operator, that is, P x number of available PRBs of the cell.
7.1.1.3 Target Frequency Selection

Target frequency selection is the same as that described in 5.1.3 Target Frequency Selection.
7.1.1.4 UE Selection
The eNodeB selects RRC_REL UEs served by the operator for MLB. RRC_REL UEs are about
to be released because the timer specified by RrcConnStateTimer.UeInactiveTimer expired.
7.1.1.5 Load Transfer

Load transfer is the same as that described in 5.1.5 Load Transfer.
7.1.2 MLB by Transferring UL-Sync UEs

If operator-level user-number-based inter-frequency MLB is enabled and the SynchronizedUE
(SynchronizedUE) option of the CellMLB.InterFreqUeTrsfType parameter is selected, the
eNodeB can transfer UL-sync UEs for MLB.

eRAN
7.1.2.1 MLB Triggering and Termination

An eNodeB periodically measures the number of UL-sync UEs served by each operator in a cell
and compares the result with the operator-specific user-number-based MLB threshold.
Number of operator-specific UL-sync UEs CellMLB.InterFreqMlbUeNumThd x P +
Number of operator-specific UL-sync UEs < CellMLB.InterFreqMlbUeNumThd x P
For details about P, see 7.1.1.1 MLB Triggering and Termination.

7.1.2.2 Candidate Cell Selection

The candidate cell selection procedure is similar to that described in 5.2.2 Candidate Cell
Selection.

In addition to the activities described in 5.2.2.1 Preliminary Candidate Cell Selection, the
eNodeB filters out inter-operator neighboring cells.

In the exchange procedure described in 5.1.2.2 Load Information Exchange, the load
information exchange messages convey the operator-specific number of UL-sync UEs as well
as hardware and TNL resource information of neighboring cells. The messages also specify the
interval at which the cell load information should be reported. The neighboring cells periodically
send the operator-specific load information to the serving cell at the specified load update
interval. If a candidate cell is not activated, messages transmitted over the X2 interface for load
information exchange with it are unnecessary.

When removing cells as described in 5.1.2.3 Final Candidate Cell Selection, the eNodeB
considers bandwidth resources reserved for the operator.
7.1.2.3 Target Frequency Selection

7.1.2.4 UE Selection and Load Transfer

The UE selection and load transfer procedures are similar to those described in 5.2.4 UE
Selection and 5.2.5 Load Transfer. One difference is that the eNodeB selects UEs served by
the operator. Another difference is the method of calculating the PRB usage of a single UE. The
formula is as follows:

eRAN
PRB usage = , where UeRbNumber indicates the

number of PRBs used by the UE and OperatorReserveResource indicates the number of PRBs
reserved for the operator in the serving cell.
7.2 Operator-Level PRB-Usage-based Inter-Frequency MLB

The eNodeB evaluates the PRB usage of each operator in the serving cell. When the PRB usage
of an operator is high, the eNodeB selects intra-operator inter-frequency neighboring cells with
low PRB usage.
In addition, the eNodeB selects certain UL-sync UEs and transfers them to the selected cells to
achieve load balancing between inter-frequency neighboring cells for the operator.
Operator-level PRB-usage-based MLB is enabled if the parameter settings are as follows:
l The PRB_ONLY(PrbMode) or PRB_OR_UE_NUMBER(PrbOrUeNumMode) option

of the CellMLB.MlbTriggerMode parameter is selected.
l The InterFreqMlbSwitch(InterFreqMlbSwitch) or InterFreqBlindMlbSwitch
selected.
l The SHARING(SHARING) option of the CellMLB.InterFreqMLBRanShareMode
parameter is selected.
l The CellAlgoSwitch.RanShareModeSwitch parameter is set to ON(On).

MLB triggering and termination are similar to those described in 6.1 MLB Triggering and
Termination. The difference is that the eNodeB evaluates the operator-specific PRB usage and
user number threshold. The PRB usage is the percentage of PRBs used by an operator among
PRBs reserved for the operator in the serving cell.
The number of PRBs reserved for an operator is a prerequisite for calculating the operator-
specific PRB usage. For example, the downlink PRB usage of operator A1 is calculated as
follows:
l Number of downlink PRBs reserved for operator A1 =
where:
OpDlRbUsedRatio_A1 indicates the CellOp.OpDlRbUsedRatio parameter value
defined for operator A1. This parameter specifies the percentage of the downlink PRB
capacity allocated to the operator. (The CellOp.OpUlRbUsedRatio specifies the
percentage of the uplink PRB capacity allocated to the operator.)
N is the number of operators that share the cell.
TotalRBNum is the total number of PRBs corresponding to the cell bandwidth.

eRAN
l PRB usage of operator A1 =
where RbNumberForOperatorA1 indicates the number of downlink PRBs used by operator

A1. If RbNumberForOperatorA1 is greater than the number of PRBs reserved for operator
A1, the PRB usage of operator A1 is greater than 100%.
The operator-specific user number threshold is calculated based on the following rules:
l If the CellMLB.MlbMinUeNumThd parameter (cell-level threshold) is set to 0, the

threshold for each operator is 0.
l If the CellMLB.MlbMinUeNumThd parameter is set to a non-zero value, the operator-
specific threshold is equal to round(P x CellMLB.MlbMinUeNumThd) plus
CellMLB.MlbMinUeNumOffset. round() is the rounding function.
For details about P, see 7.1.1.1 MLB Triggering and Termination.

The candidate cell selection procedure is similar to that described in 6.2 Candidate Cell
Selection.

The eNodeB filters out inter-operator neighboring cells.

Load information exchange messages contain operator-related load information and therefore
are Huawei private messages over X2 interfaces.
The operator-related information includes the PRB usage for the operator, the number of PRBs
reserved for the operator, and information about hardware and transport resources. The messages
also contain the interval at which the load information should be reported.

After load information exchange, the eNodeB derives a candidate cell list based on factors such
as differences in cell bandwidths reserved for the operator, in PRB usage of the operator, and in
the handover success rate. Then, the eNodeB generates a final candidate cell list by removing
state.
l The difference in the MLB-triggering PRB usage of the operator between the serving and
neighboring cells is less than the CellMLB.LoadDiffThd parameter value, or the operator-
specific PRB usage in the MLB-triggering direction in the neighboring cell is not less than
the result of 100% (0.5 x CellMLB.LoadDiffThd). The values are calculated based on
the converted bandwidths of the cells.

eRAN

7.2.4 UE Selection
The selection mechanism is similar to that described in 6.4 UE Selection. The difference is that
the eNodeB considers the information about the operator for which MLB is triggered.
The PRB usage of a single UE in operator-level MLB is calculated as follows:
PRB usage =
UeRbNumber indicates the number of PRBs used by the UE, and OperatorReserveResource
indicates the number of PRBs corresponding to the bandwidth reserved for the operator. For
details, see 7.2.1 MLB Triggering and Termination.
When selecting UEs, the eNodeB considers the following factors:
l Difference in the operator-specific PRB usage between the source and candidate cells
l Load difference threshold (specified by the CellMLB.LoadDiffThd parameter)
l Load transfer factor (specified by the CellMLB.LoadTransferFactor parameter)
l Extent that the operator-specific PRB usage of the source cell exceeds the MLB triggering
threshold
In MLB without load information exchange, the source and candidate cell load cannot be
compared. Therefore, the upper limit to the total PRB usage of all UEs to be transferred in the
current MLB period is determined by the extent that the operator-specific PRB usage of the
source cell exceeds the MLB triggering threshold.
7.2.5 Load Transfer

Load transfer is similar to that described in 6.5 Load Transfer.
If a high-load target cell rejects a handover request, the source cell imposes a penalty on the
target cell.
For example:
Cell 1 sends a handover request to cell 2 for a UE of operator A. If cell 2 determines that the
load of operator A in the cell is high, cell 2 rejects the handover request. In this situation, cell 1
imposes a penalty on operator A's part of cell 2. During the penalty, cell 2 is not considered as
a candidate cell for operator A's load balancing from cell 1. The penalty starts from the current
MLB period, whose length is defined by CellMLB.InterFreqLoadEvalPrd, and lasts for
CellMLB.CellPunishPrdNum MLB periods.

eRAN
Description 8 Inter-Frequency MLB for Non-Cosited Cells
8 Inter-Frequency MLB for Non-Cosited Cells
This chapter describes the LOFD-081227 Intra-LTE Load Balancing for Non-cosited Cells
feature. This feature supports the following two functions to improve the network capacity
management capability for non-cosited cells:
l Event-A5-triggered load-based inter-frequency handovers

In PRB-usage-based inter-frequency MLB and user-number-based inter-frequency MLB,
the EutranInterNFreq.MlbInterFreqHoEventType parameter specifies whether A4- or
A5-related measurement configuration for a neighboring E-UTRAN frequency is delivered
to UEs. In scenarios where inter-frequency neighboring cells are not located in the same
site, if the eNodeB initiates handovers based on event A5, UEs that are not located in the
site center are selected for MLB, improving the Uu interface performance of UEs after
MLB and the spectral efficiency.
For details about the function implementation and engineering guidelines of this function,
see 5.2.5 Load Transfer and 13.4 LOFD-081227 Intra-LTE Load Balancing for Non-
cosited Cells, respectively.
l Event-A2-triggered frequency-priority-based inter-frequency handovers
This function is enabled if the A2BasedFreqPriHoSwitch(A2BasedFreqPriHoSwitch)
option of the CellAlgoSwitch.FreqPriorityHoSwitch parameter is selected.
When a UE initially accesses a cell, a UE is handed over to the cell, or the RRC connection
of a UE is reestablished to the cell, the eNodeB delivers A2-related measurement
configuration to the UE. When the UE reports event A2 and PRB-usage-based inter-
frequency MLB or user-number-based inter-frequency MLB is not triggered in the target
cell of a frequency-priority-based handover, the eNodeB performs a handover and transfers
this UE to this cell.
In scenarios where inter-frequency neighboring cells that are configured with different
bandwidths are located in different sites, cells with smaller bandwidths can choose cells
with larger bandwidths as target cells for frequency-priority-based handovers. When the
cell load is light, UEs that are not located in the site center of small-bandwidth cells can be
handed over to large-bandwidth cells, improving the peak throughput of UEs.
For details about the function implementation and engineering guidelines of this function,
see Intra-RAT Mobility Management in Connected Mode.

eRAN
Description 9 Load Pre-Balancing
9 Load Pre-Balancing
To reduce potential cell load in a multi-carrier network, eNodeBs instruct RRC_REL UEs to
proportionally camp on cells on different frequencies before the load in the serving cells of the
UEs increases. This achieves better utilization of network resources.
Load pre-balancing works when the user number load in the serving cell is light (that is, before
user-number-based inter-frequency MLB is triggered). Therefore, load pre-balancing does not
directly affect system capacity. However, it prevents the situation that a carrier is continuously
in the high load state while other carriers are in the low load state. If the bandwidths of the
carriers are different, the UE transfer proportions must be set based on the ratios of the carrier
bandwidths.
Load pre-balancing is not compatible with the following functions:
l Operator-level MLB
l Inter-RAT MLB to UTRAN by transferring RRC_REL UEs
For details about how to deploy load pre-balancing, see 13.5 Load Pre-Balancing.

eRAN
9.1 Load Pre-Balancing Methods

Load pre-balancing can be implemented in two ways, as listed in Table 9-1. Micro eNodeBs
support only load pre-balancing in fixed proportions.
Table 9-1 Load pre-balancing method
Method Usage Scenario Implementation
Load pre-balancing Intra-eNodeB or inter- The eNodeB instructs RRC_REL UEs to

in fixed proportions eNodeB multi-carrier proportionally camp on different
scenario frequencies. The proportions are
determined by the
EutranInterNFreq.IdleMlbUERelea-
seRatio parameter.
Load pre-balancing Intra-eNodeB multi- When either this function is enabled or the
in adaptive carrier scenario eNodeBMlb.InterFreqIdleMlbInterval
proportions parameter value is changed, the eNodeB
periodically measures the average number
of UL-sync UEs served by the eNodeB.
The measurement period is specified by the
eNodeBMlb.InterFreqIdleMlbInterval
parameter. If the average number of UL-
sync UEs per frequency is greater than the
eNodeBMlb.InterFreqIdleMlbStaThd
parameter value at the end of a
measurement period, the eNodeB
adaptively adjusts the proportions for the
frequencies. As a result, the distribution of
UEs on the operating frequencies of the
eNodeB will approximate to the
seRatio parameter settings for these
frequencies.
If user-number-based MLB is triggered to transfer RRC_REL UEs from the serving cell, the
algorithm of load pre-balancing in fixed proportions automatically stops.
Inter-eNodeB load pre-balancing requires configurations of external cells but not neighbor
relationships. Intra-eNodeB load pre-balancing does not require configurations of external cells.
Load pre-balancing does not work with LBFD-070103 Multi-Band Compatibility Enhancement.
If a UE (for example, a roaming UE) does not support the primary-band-specific EARFCN but
a secondary-band-specific EARFCN of a target cell, then the eNodeB does not select any
EARFCN of the frequency on which the target cell operates. Instead, the eNodeB selects other
frequencies supported by the UE for load pre-balancing. For details about LBFD-070103 Multi-
Band Compatibility Enhancement, see Multiple Frequency Band Indicator Feature Parameter
Description.

eRAN
9.2 Execution and Termination of Load Pre-Balancing

The following table describes how to enable or disable each load pre-balancing algorithm. If
both algorithms are enabled, the eNodeB performs load pre-balancing only in adaptive
proportions.
Load Pre- How to Enable the How to Disable the Algorithm

Balancing Algorithm
Method
Load pre-balancing Select both of the following Deselect one of the following
in fixed proportions options: options:
l The InterFreqIdleMlbS- l The InterFreqIdleMlbSwitch
witch(InterFreqI- (InterFreqIdleMlbSwitch)
dleMlbSwitch) option of option of the
the CellAlgoSwitch.MlbAlgoSwit
CellAlgoSwitch.MlbAlgoS ch parameter
witch parameter l The Proportion(Proportion)
l The Proportion option of the
(Proportion) option of the CellMLB.InterFreqIdleMlb-
CellMLB.InterFreqI- Mode parameter
dleMlbMode parameter
Load pre-balancing Select both of the following Deselect one of the following
in adaptive options: options:
proportions l The l The
INTER_FREQ_IDLE_M INTER_FREQ_IDLE_MLB
LB_SWITCH _SWITCH
(INTER_FREQ_IDLE_ (INTER_FREQ_IDLE_MLB
MLB_SWITCH) option of _SWITCH) option of the
the ENodeBAlgoSwitch.MlbAlgo
ENodeBAlgoSwitch.MlbA Switch parameter
lgoSwitch parameter l The ADAPTIVE_PROPOR-
l The TION(ADAPTIVE_PRO-
ADAPTIVE_PROPOR- PORTION) option of the
TION(ADAPTIVE_PRO- eNodeBMlb.InterFreqI-
PORTION) option of the dleMlbMode parameter
eNodeBMlb.InterFreqI-
dleMlbMode parameter
9.3 UE Transfer Proportions

The proportions of UEs that the eNodeB releases to frequencies are dependent on the
EutranInterNFreq.IdleMlbUEReleaseRatio parameter settings for the frequencies.
If a frequency is included in multiple bands and its information is configured in more than one
EutranInterNFreq MO of the serving cell, the EutranInterNFreq.IdleMlbUEReleaseRatio

eRAN
parameter must be set to 0% in the MOs that contain secondary-band-specific information. If

the parameter is not set to 0%, the UE transfer proportion will be incorrectly calculated.
Load Pre-Balancing in Fixed Proportions

The EutranInterNFreq.IdleMlbUEReleaseRatio and
EutranInterNFreq.CellReselPriorityCfgInd parameter settings for frequencies determine the
proportions of UEs that the eNodeB releases to the frequencies.
For example, a cell operates on frequency F1 and is configured with two neighboring frequencies
F2 and F3. The EutranInterNFreq.IdleMlbUEReleaseRatio parameter is set to 30% and 50%
for F2 and F3, respectively. The EutranInterNFreq.CellReselPriorityCfgInd parameter is set
to CFG(Configure) for F2 and F3. Then, the percentage of UEs to be released to F1 is equal to
20% (that is, 100% 30% 50%). Figure 9-1 shows the example.
In this example, the serving cell preferentially releases 20%, 30%, and 50% of UEs to F1, F2,
and F3, respectively.
Figure 9-1 Example of load pre-balancing in fixed proportions
If the EutranInterNFreq.CellReselPriorityCfgInd parameter is set to NOT_CFG(Not

configure) for F3, the serving cell does not release UEs to F3. Then, the percentage of UEs to
be released to F1 is equal to 70% (that is, 100% 30%).
Load Pre-Balancing in Adaptive Proportions

The eNodeB calculates the average of the proportions of UEs that the eNodeB releases to a
frequency from the cells served by the eNodeB in the same way as load pre-balancing in fixed
proportions. The average proportion is taken as the expected proportion of UEs that are
distributed on the frequency. The eNodeB periodically measures the number of UEs served by
each operating frequency and adaptively adjusts the proportions for the frequencies.
For example, the cells served by the eNodeB operate on frequencies F1 and F2. It is expected
that the UEs are equally distributed on F1 and F2 at a ratio of 1:1. However, UL-sync UEs served
by the eNodeB are now distributed on F1 and F2 at a ratio of 4:1. Then, the eNodeB adjusts the
policy for releasing UEs as shown in Figure 9-2.

eRAN
l 3/8 of the UEs served by cells on F1 are released to F2, and 5/8 of them are released to F1.
l All UEs served by cells on F2 are released to F2.
Figure 9-2 Example of load pre-balancing in adaptive proportions
If the EutranInterNFreq.CellReselPriorityCfgInd parameter is set to NOT_CFG(Not

configure) for a neighboring frequency, the serving cell does not release UEs to this frequency.
9.4 Selection of Dedicated Priorities

If load pre-balancing is enabled, the eNodeB sends an RRCConnectionRelease message to a UE
when the UE inactivity timer (specified by the RrcConnStateTimer.UeInactiveTimer
parameter) expires or the MME initiates an RRC connection release with the cause value of
"Normal Release". The RRCConnectionRelease message carries the
IdleModeMobilityControlInfo IE. This IE contains the following information:
l Target frequencies, which may include the serving frequency, and their dedicated priorities
l Non-target frequencies and their dedicated priorities
The non-target frequencies are configured with SPID-specific dedicated cell-reselection
priorities, operator-specific dedicated cell-reselection priorities, or absolute cell-reselection
priorities.
For details about SPID-specific cell-reselection priorities and operator-specific cell-
reselection priorities, see Flexible User Steering Feature Parameter Description and RAN
Sharing Feature Parameter Description.
l Length of the T320 timer, which is specified by the
RrcConnStateTimer.T320ForLoadBalance parameter
In the IdleModeMobilityControlInfo IE, the frequencies are sorted by frequency category in the
following order:
1. Target E-UTRA frequency

2. Non-target E-UTRA frequency
3. UTRA frequency
4. GERAN frequency

eRAN
If there is more than one frequency in a category, the priorities of non-target E-UTRA, UTRA,
and GERAN frequencies are dependent on the SPID-specific dedicated cell-reselection
priorities, operator-specific dedicated cell-reselection priorities, or absolute cell-reselection
priorities.
If the MME initiates a release with the cause of "Normal Release" for an RRC connection that
was set up during a tracking area update (TAU), the eNodeB determines whether to include the
dedicated priorities in the RRCConnectionRelease message based on the
CellAlgoSwitch.ReselecPriAdaptSwitch parameter setting. The eNodeB includes the dedicated
priorities in the message only if this parameter is set to ON(On).

eRAN
Description 10 Transport-QoS-based Inter-Frequency MLB
10 Transport-QoS-based Inter-Frequency
MLB
This chapter describes how the LOFD-001057 Load Balancing based on Transport QoS feature
works. This feature is under license control and applies only to micro eNodeBs.

eRAN
10.1 MLB Triggering and Termination

The transport resource management (TRM) module of an eNodeB calculates the TNL load based
on the total load of the transport resource groups and the admission bandwidths of these transport
resource groups. The eNodeB compares the TNL load with load thresholds to determine load
status.
NOTE
The TRM module calculates only the load of transport resource groups in which IP paths are configured.
If the TNL load is in the HighLoad or OverLoad state, the eNodeB triggers transport-QoS-based
inter-frequency MLB. If the TNL load falls to the LowLoad or MediumLoad state, the eNodeB
stops transport-QoS-based inter-frequency MLB. For details about the TNL load measurement
and status evaluation, see Transport Resource Management Feature Parameter Description.
10.2 Candidate Cell Selection

The mechanism of preliminary candidate cell selection in transport-QoS-based inter-frequency
MLB is the same as that in user-number-based inter-frequency MLB with load information
exchange. For details, see 5.2.2.1 Preliminary Candidate Cell Selection.

The mechanism of load information exchange in transport-QoS-based inter-frequency MLB is
the same as that in PRB-usage-based inter-frequency MLB with load information exchange. For
details, see Load Information Exchange.

After load information exchange, the eNodeB generates a final list of candidate cells by removing
l The success rate of handovers from the serving cell to the neighboring cell is less than 98%.
state.
NOTE
If a cell is in the HighLoad or OverLoad state, the cell is heavily loaded.
If the candidate cell list is empty, the eNodeB does not execute MLB during the current MLB
period.
10.3 Target Frequency Selection

Target frequency selection is the same as that described in 6.3 Target Frequency Selection.

eRAN
10.4 UE Selection
Transport-QoS-based inter-frequency MLB is implemented by transferring UL-sync UEs. The
maximum number of UEs that can be transferred to target cells within an MLB period is specified
by the CellMLB.MlbMaxUeNum parameter.
When selecting UEs, the eNodeB first identifies whether the uplink or downlink TNL load
triggered MLB and selects the UEs that are running services in the same direction as the MLB
triggering direction. Then, the eNodeB compares the PRB usage of these UEs running GBR
services and non-GBR services and selects UEs that use more PRBs.
The conditions for UE selection in transport-QoS-based inter-frequency MLB are the same as
those in PRB-usage-based inter-frequency MLB with load information exchange. For details,
see 6.4 UE Selection.
10.5 Load Transfer

The mechanism of load transfer in transport-QoS-based inter-frequency MLB is the same as that
in PRB-usage-based inter-frequency MLB with load information exchange. For details, see 6.5
Load Transfer.

eRAN
Description 11 Related Features
11 Related Features
11.1 Features Related to LOFD-070215 Intra-LTE User

Number Load Balancing
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
l LBFD-070103 Multi-Band Compatibility Enhancement
LOFD-070215 Intra-LTE User Number Load Balancing can work with LBFD-070103
Multi-Band Compatibility Enhancement. If a UE (for example, a roaming UE) does not
support the primary-band-specific EARFCN but a secondary-band-specific EARFCN of a
target cell, the eNodeB includes the supported EARFCN in the measurement configuration
for an inter-frequency handover or in an RRC connection release message to be sent to the
UE.
l LOFD-003029 SFN or LOFD-070205 Adaptive SFN/SDMA
MLB performance is negatively affected because the source cell does not acquire the
number of RRUs in the target inter-eNodeB cell and encounters errors in evaluating the
number of UL-sync UEs in the target cell. Therefore, MLB is currently not recommended
when target cells are SFN cells.
l LBFD-00201805 Service Based Inter-Frequency Handover
If a target cell is in the MLB state, service-based inter-frequency handovers and other
unnecessary handovers, for example, frequency-priority-based inter-frequency handovers
to the cell are not allowed.

eRAN
11.2 Features Related to LOFD-001032 Intra-LTE Load

Balancing
None

None
Impacted Features
When evaluating a single frequency network (SFN) cell for MLB, the eNodeB considers
the PRB usage in the entire SFN cell. The congestion status of each RRU in the SFN cell
is unknown to the source cell. Therefore, RRU-level load balancing is currently not
supported. MLB performance is negatively affected because the source cell does not acquire
the number of RRUs in the target inter-eNodeB cell and encounters errors in evaluating the
PRB usage of the target cell. Therefore, MLB is currently not recommended when target
cells are SFN cells.
LOFD-001032 Intra-LTE Load Balancing can work with LBFD-070103 Multi-Band
Compatibility Enhancement. If a UE (for example, a roaming UE) does not support the
primary-band-specific EARFCN but a secondary-band-specific EARFCN of a target cell,
the eNodeB includes the supported EARFCN in the measurement configuration for an inter-
frequency handover or in an RRC connection release message to be sent to the UE. For
details about LBFD-070103 Multi-Band Compatibility Enhancement, see Multiple
11.3 Features Related to LOFD-070204 Operator Load Based

Intra-LTE MLB
LOFD-070204 Operator Load Based Intra-LTE MLB requires LOFD-001032 Intra-LTE Load
Balancing or LOFD-070215 Intra-LTE User Number Load Balancing.
If neither LOFD-001036 RAN Sharing with Common Carrier nor LOFD-070206 Hybrid RAN
Sharing is enabled in the network, cell-level inter-frequency MLB, instead of operator-level
inter-frequency MLB, takes effect.

eRAN
In addition, operator-level inter-frequency MLB requires that RanShareModeSwitch be set on.

If the switch is off, cell-level inter-frequency MLB instead of operator-level inter-frequency
MLB takes effect.

None
Impacted Features
When evaluating an SFN cell for MLB, the eNodeB considers the operator-specific PRB
usage in the entire SFN cell. The congestion status of each RRU in the SFN cell is unknown
to the source cell. Therefore, RRU-level load balancing is currently not supported. MLB
performance is negatively affected because the source cell does not acquire the number of
RRUs in the target inter-eNodeB cell and encounters errors in evaluating the PRB usage
or number of UL-sync UEs in the target cell. Therefore, MLB is currently not recommended
when target cells are SFN cells.
LOFD-070204 Operator Load Based Intra-LTE MLB can work with LBFD-070103 Multi-
Band Compatibility Enhancement. If a UE (for example, a roaming UE) does not support
the primary-band-specific EARFCN but a secondary-band-specific EARFCN of a target
cell, the eNodeB includes the supported EARFCN in the measurement configuration for
an inter-frequency handover or in an RRC connection release message to be sent to the UE.
For details about LBFD-070103 Multi-Band Compatibility Enhancement, see Multiple
11.4 Features Related to LOFD-081227 Intra-LTE Load

Balancing for Non-cosited Cells
LOFD-081227 Intra-LTE Load Balancing for Non-cosited Cells requires the following features:
l Features Related to LOFD-001032 Intra-LTE Load Balancing

l LOFD-070215 Intra-LTE User Number Load Balancing

None
Impacted Features
None

eRAN
11.5 Features Related to LOFD-001057 Load Balancing based

on Transport QoS
LOFD-001057 Load Balancing based on Transport QoS requires LOFD-001032 Intra-LTE Load
Balancing.

None
Impacted Features
LOFD-001057 Load Balancing based on Transport QoS can work with LBFD-070103 Multi-
Band Compatibility Enhancement. If a UE (for example, a roaming UE) does not support the
primary-band-specific EARFCN but a secondary-band-specific EARFCN of a target cell, the
eNodeB includes the supported EARFCN in the measurement configuration for an inter-
frequency handover or in an RRC connection release message to be sent to the UE. For details
about LBFD-070103 Multi-Band Compatibility Enhancement, see Multiple Frequency Band
Indicator Feature Parameter Description.

eRAN
Description 12 Network Impact
12 Network Impact
12.1 LOFD-070215 Intra-LTE User Number Load Balancing

System Capacity
In a multi-carrier LTE network, if the number of UL-sync UEs per unit of bandwidth differs
greatly between carriers, this feature helps decrease the differences and balance the user number
load among cells. Note that the user number load is relatively balanced, due to factors such as
coverage capabilities of frequency bands and band capabilities of UEs on networks.
After this feature is enabled, the source cells of load transfer may receive capacity gains, mainly
in terms of the average single-UE throughput and cell throughput. Especially when a source cell
with a large number of UL-sync UEs encountered an obvious drop in the average single-UE
throughput before load transfer, MLB brings high capacity gains to the source cell and also
benefits the capacity of the MLB system. The MLB system consists of the source cell and its
inter-frequency cells between which load can be transferred.
Network Performance
In MLB by transferring RRC_REL UEs, if the source and target cells differ noticeably in their
coverage, the UE locations relative to the cell center change after MLB. The following are
example scenarios:
l The cells operate on different frequencies in the same band and do not share the same
antenna. The downtilt or azimuth difference causes the coverage difference.
l One cell operates in the 2.6 GHz band, and the other cell operates in the 700 MHz band.
The difference in the measured RSRP value at the same location between the two cells is
greater than 5 dB.
The change in UE locations affects the performance counters highly related to coverage, for
example, the access success rate and service drop rate.
The "user-number-based inter-frequency MLB by transferring UL-sync UEs" algorithm

increases the number of inter-frequency handovers.

eRAN
12.2 LOFD-001032 Intra-LTE Load Balancing

System Capacity
In a multi-carrier LTE network, if PRB usage differs greatly between carriers, this feature helps
decrease the differences and balance the PRB usage among cells. Note that, on live networks,
the user number load is relatively balanced.
After this feature is enabled, the source cells of load transfer may receive capacity gains, mainly
in terms of the average single-UE throughput and cell throughput. Especially when a source cell
with PRB usage as high as 100% encounters an obvious drop in the average single-UE
throughput before load transfer, MLB brings high capacity gains to the source cell and also
benefits the capacity of the MLB system. The MLB system consists of the source cell and its
inter-frequency cells between which load can be transferred.
Network Performance
This feature increases the number of inter-frequency handovers.
12.3 LOFD-070204 Operator Load Based Intra-LTE MLB

System Capacity
Operator-level inter-frequency MLB coordinates load distribution on the resources reserved for
an operator and increases the usage of reserved resources among different frequencies for the
operator.
For details, see "System Capacity" in 12.1 LOFD-070215 Intra-LTE User Number Load
Balancing and 12.2 LOFD-001032 Intra-LTE Load Balancing.
Network Performance
For details, see "Network Performance" in 12.1 LOFD-070215 Intra-LTE User Number Load
Balancing and 12.2 LOFD-001032 Intra-LTE Load Balancing.
12.4 LOFD-081227 Intra-LTE Load Balancing for Non-

cosited Cells
System Capacity
This feature improves the radio resource utilization and increases system capacity in non-cosited
scenarios.
Network Performance
This feature increases the peak throughput of UEs.

eRAN
12.5 LOFD-001057 Load Balancing based on Transport QoS

System Capacity
This feature transfers partial load from a cell with a heavy TNL load to neighboring E-UTRAN
cells, and, therefore, reduces the probability of transmission congestion in the source cell.
Network Performance
This feature increases the number of inter-frequency handovers.
12.6 Load Pre-Balancing

System Capacity
For details, see 12.1 LOFD-070215 Intra-LTE User Number Load Balancing. This function
pre-balances load only at the frequency level. The benefits of load pre-balancing are less
significant compared with user-number-based inter-frequency MLB.
Network Performance
Load pre-balancing in fixed proportions continues to instruct RRC_REL UEs to proportionally
camp on neighboring cells after the specified proportions are reached. Compared with the
network impact of user-number-based inter-frequency MLB described in 12.1 LOFD-070215
Intra-LTE User Number Load Balancing, load pre-balancing in fixed proportions increases
the number of inter-frequency measurements, the number of reselections, and UE power
consumption and extends paging latency if the cell-reselection priorities are the same.

eRAN
Description 13 Engineering Guidelines
13 Engineering Guidelines
13.1 LOFD-070215 Intra-LTE User Number Load Balancing
13.1.1 When to Use LOFD-070215 Intra-LTE User Number Load

Balancing
Use LOFD-070215 Intra-LTE User Number Load Balancing in a multi-carrier network where
most UEs are smartphones.
User-Number-based Inter-Frequency MLB by Transferring RRC_REL UEs

This type of MLB applies to a multi-carrier network, regardless of whether the cell-reselection
priorities of different frequencies are the same or not.
To prevent the impact on network performance described in 12.1 LOFD-070215 Intra-LTE

User Number Load Balancing, use this MLB algorithm in a multi-carrier network where the
coverage areas of the carriers are the same. (The coverage areas are considered the same if the
difference in measured RSRP values between the carriers at the same location is less than or
equal to 3 dB). Alternatively, use this algorithm in concentric cells where the cell with the smaller
coverage area (for example, in the 700 MHz band) transfers RRC_REL UEs to the cell with the
larger coverage area (for example, in the 2.6 GHz band). The
EutranInterNFreq.MlbTargetInd parameter specifies whether a neighboring frequency can
be the target frequency.
User-Number-based Inter-Frequency MLB by Transferring UL-Sync UEs

This type of MLB applies to multi-carrier networks where the cell-reselection priorities of
different frequencies are the same.
If the cell-reselection priorities are different, according to the terminal behavior characteristics,
smartphones may change from RRC_CONNECTED mode to RRC_IDLE mode in the target
cell of inter-frequency handovers for MLB and return to the source cell by cell reselection soon
after the handovers. Therefore, MLB has little effect.

eRAN
Load Information Exchange Evaluation

Exchange mode applies to the following scenarios where load information exchange is required:
l Intra-eNodeB inter-frequency neighboring cells can be target cells of MLB.

l Inter-eNodeB inter-frequency neighboring cells served by eNodeBs that are connected to
the source eNodeB through X2 interfaces can be target cells of MLB.
Non-exchange mode applies to scenarios where the source cell cannot exchange load information
with inter-eNodeB inter-frequency neighboring cells. The neighboring cells are served by
eNodeBs that are provided by other vendors or are not connected to the source eNodeB through
X2 interfaces.
If the preceding scenarios coexist, you can enable both exchange and non-exchange modes.
Example
It is recommended that all cells involved in MLB have the same parameter settings on load
information exchange. If they have different settings, after MLB is triggered, there is a possibility
that neither the source cell nor the target cell will evaluate the load status of each other and the
cell in the low load state will continually transfer load to the high-load cell.
For example, non-exchange mode is enabled in cell A and exchange mode is enabled in cell B.
After MLB is triggered in cell A, cell A does not exchange load information with cell B or
evaluate cell B's load status during candidate cell selection. As a result, cell A may select cell B
as a target cell even if cell B is in the high load state. Cell B considers that cell A has evaluated
cell B's load status. When receiving a handover request from cell A, cell B accepts the request
without checking its own load status.
13.1.2 Required Information

Collect the following information:
l Information about each neighboring cell of the cells served by the local eNodeB
Whether information about the neighboring cell is complete
Whether the neighboring cell has been blacklisted
Whether the No handover indicator parameter is set to PERMIT_HO_ENUM
(Permit Ho)
l Status of the X2 interfaces with neighboring eNodeBs
l UE capabilities
Proportion of UEs that support inter-frequency measurements and handovers and
proportion of the other UEs
l Whether the operator has purchased the required licenses
13.1.3 Planning
13.1.3.1 RF Planning
The network coverage must meet the following UE mobility requirements:

eRAN
l No holes exist in the coverage.

l Overshoot coverage is minimized.
l Pilot pollution is minimized.
l Uplink and downlink imbalances are minimized.
13.1.3.2 Network Planning

N/A
13.1.3.3 Hardware Planning

N/A
13.1.4 Requirements
There are no requirements for the operating system and transmission networking. Before
deploying LOFD-070215 Intra-LTE User Number Load Balancing, the operator must purchase
and activate the licenses for the feature based on the setting of the
CellMLB.MlbTriggerMode parameter.
l If the CellMLB.MlbTriggerMode parameter is set to UE_NUMBER_ONLY

(UeNumMode), the license listed in the following table must be activated.
Feature Feature Name Model License Control NE Sales Unit

ID Item
LOFD- Intra-LTE User LT1SI Intra-LTE User eNodeB per RRC

070215 Number Load LUNL Number Load Connected
Balancing B00 Balancing (FDD) User

(PrbOrUeNumMode), the licenses listed in the following table must be activated.
Featur Feature Name Model License NE Sales Unit

e ID Control
Item
LOFD- Intra-LTE Load LT1S00I Intra-LTE eNodeB per RRC

001032 Balancing LLB00 Load Connected
Balancing User
(FDD)
LOFD- Intra-LTE User LT1SILU Intra-LTE eNodeB per RRC

070215 Number Load NLB00 User Number Connected
Balancing Load User
Balancing
(FDD)

eRAN
13.1.5 Data Preparation

This section describes the data that you need to collect for setting parameters. Required data is
data that you must collect for all scenarios. Collect scenario-specific data when necessary for a
specific feature deployment scenario.
specific feature deployment scenario. There are three types of data sources:
l Network plan (negotiation not required): parameter values planned and set by the operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users
Required Data
The following table describes the parameter that must be set in a CellMLB managed object
(MO) to configure the MLB algorithm.
Parameter Name Parameter ID Data Source Setting Notes
Mobility Load CellMLB. User-defined The recommended

Balancing Trigger MlbTriggerMode value is
Mode UE_NUMBER_ON
LY(UeNumMode).
The following table describes the parameter that must be set in an EutranInterFreqNCell MO
to configure an inter-frequency neighbor relationship.
Overlap Indicator EutranInterFreqN- Network plan This parameter

Cell.OverlapInd (negotiation not specifies whether the
required) E-UTRAN
neighboring cell is
manually identified
as an overlapping
neighboring cell. The
default value is NO
(NO). You are
advised to identify
overlapping
neighboring cells and
set this parameter to
YES(YES) for these
cells.

eRAN
The following table describes the parameter that must be set in the CellAlgoSwitch MO to
configure the handover policy for MLB.
Load Balancing CellAlgoSwitch. Network plan If the

Handover Policy MlbHoMode (negotiation not InterFreqMlb-
required) BlindHo
(InterFreqMlb-
BlindHo) option of
this parameter is
selected, the eNodeB
adopts blind
handovers for MLB.
The following table describes the parameters that must be set in an EutranInterNFreq MO to
configure a neighboring E-UTRA frequency.
Parameter Parameter ID Data Setting Notes

Name Source
Mobility Load EutranInterNFreq. Network This parameter specifies

Balancing MlbTargetInd plan whether the neighboring E-
Target (negotiation UTRA frequency can be a
Indicator not required) target frequency for inter-
frequency MLB.
Inter-Freq Mlb EutranInterNFreq. Network This parameter specifies the

Threshold IfMlbThdRsrpOffset plan offset to the RSRP threshold
RSRP Offset (negotiation for load-based inter-
not required) frequency handovers. The
default value is
recommended.
The following table describes the parameters that must be set in an InterFreqHoGroup MO to
configure a group of parameters for inter-frequency handovers.
Parameter Parameter ID Data Source Setting Notes

Name
Load Based InterFreqHoGroup. Network plan This parameter specifies

Interfreq RSRP InterFreqLoadBasedHo (negotiation not the RSRP threshold for
threshold A4ThdRSRP required) event A4 that triggers
load-based inter-
frequency handovers. The
default value is
recommended.

eRAN

Name
Load Based InterFreqHoGroup. Network plan This parameter specifies

Interfreq RSRQ InterFreqLoadBasedHo (negotiation not the RSRQ threshold for
threshold A4ThdRSRQ required) event A4 that triggers
load-based inter-
frequency handovers. The
default value is
recommended.
The following table describes the parameter that must be set in a CellMlbHo MO to configure
the handover for the MLB algorithm.

Name
Mlb CellMlbHo. Network plan This parameter specifies the

Handover-in MlbHoInProtect- (negotiation not protection mode for UEs that
Protect Mode Mode required) are handed over to a cell for
MLB.
The
PROTECTTIMERMOD
E(PROTECTTIMER
MODE) value is
recommended if operators
do not want that an eNodeB
always instructs the same
UE to perform gap-assisted
measurements and performs
handovers for the UE.
Mlb CellMlbHo. Network plan This parameter specifies the

Handover-in MlbHoInProtectTim- (negotiation not length of duration in which
Protect Timer er required) UEs that are handed over to
a cell for MLB are not
allowed to be handed over
for MLB again.
The default value is
recommended.
Scenario-specific Data
The following table describes the parameter that must be set in a CellAlgoSwitch MO to control
load information exchange for a cell.

eRAN

Name Source
Load balancing CellAlgoSwitch. User- Set this parameter to control

algorithm switch MlbAlgoSwitch defined load information exchange.
To enable exchange mode,
select the InterFreqMlbS-
witch(InterFreqMlbSwitch)
option of this parameter. To
enable non-exchange mode,
select the InterFreq-
BlindMlbSwitch(InterFreq-
BlindMlbSwitch) option.
The two options can be
selected at the same time.
The following table describes the parameters that must be set in a CellMLB MO to configure
the inter-frequency MLB algorithm for the cell.
Parameter Name Parameter ID Data Setting Notes

Source
InterFreq MLB CellMLB. User-defined When only one target cell

Transfer Type InterFreqUeTrsf- operates on a single target
Type frequency and cell-
reselection priorities of
different frequencies are
different in a multi-
frequency network, it is
recommended that the
IdleUE(IdleUE) option be
selected and the
SynchronizedUE
(SynchronizedUE) option
be deselected. When
multiple target cells operate
on a single target frequency,
it is recommended that the
IdleUE(IdleUE) option be
deselected and the
SynchronizedUE
(SynchronizedUE) option
be selected and cell-
reselection priorities of
different frequencies be the
same.

eRAN

Source
Inter-Frequency CellMLB. User-defined The recommended value is

MLB RAN Sharing InterFreqMLBRan- NON_SHARING
Mode ShareMode (NON_SHARING).
Load Balancing CellMLB. Network plan If this parameter is set to

Frequency Select FreqSelectStrategy (negotiation FAIRSTRATEGY
Strategy not required) (FairStrategy), the eNodeB
randomly selects one
neighboring frequency as the
target frequency. If this
parameter is set to
PRIORITYBASED
(PriorityBased), the
eNodeB selects the target
frequencies based frequency
priorities for MLB. The
recommended value is
FAIRSTRATEGY
(FairStrategy).
Inter-frequency Load CellMLB. Network plan This parameter specifies the

Evaluate Period InterFreqLoadE- (negotiation length of an inter-frequency
valPrd not required) MLB period. If the
CellMLB.FreqSelectStrat-
egy parameter is set to
PRIORITYBASED
(PriorityBased) and both a
neighboring E-UTRA
frequency and a neighboring
UTRA frequency are
selected as the target
frequencies, it is required
that the
CellMLB.InterFreqLoadE-
valPrd and
CellMLB.InterRatLoadE-
valPrd parameters be set to
the same value. If the IdleUE
(IdleUE) option of the
CellMLB.InterFreqUeTrsf
Type parameter is selected, it
is recommended that this
parameter be set to a small
value, for example, 10. This
prevents ping-pong MLB
caused by too many UEs are
released in a single MLB
period.

eRAN

Source
Inter-Rat Load CellMLB. Network plan This parameter specifies the

Evaluate Period InterRatLoadE- (negotiation length of an inter-RAT MLB
valPrd not required) period. If the
CellMLB.FreqSelectStrat-
egy parameter is set to
PRIORITYBASED
(PriorityBased) and both a
neighboring E-UTRA
frequency and a neighboring
UTRA frequency are
selected as the target
frequencies, it is required
that the
CellMLB.InterFreqLoadE-
valPrd and
CellMLB.InterRatLoadE-
valPrd parameters be set to
the same value.
Mlb Ho Cell select CellMLB. Network plan This parameter specifies

Strategy MlbHoCellSelect- (negotiation whether the eNodeB can try
Strategy not required) a second-strongest
neighboring cell for MLB
when the eNodeB fails to
initiate handovers to the
strongest cell during inter-
frequency MLB with load
information exchange.
You are advised to set this
parameter to
ONLY_STRONGEST_CE
LL(Only Try Strongest
Cell). Otherwise, after UEs
are handed over to the non-
strongest neighboring cells,
these UEs are transferred to
the strongest neighboring
cell by coverage-based intra-
frequency handovers. This
causes that the the load
balancing effects are not
achieved and increases the
number of ineffective
handovers.

eRAN

Source
Cell Capacity Scale CellMLB. Network plan This parameter specifies the
Factor CellCapacityScale- (negotiation scale factor used to
Factor not required) determine the MLB
capability of a cell. This
factor helps adjust the MLB
target in user-number-based
inter-frequency MLB. The
default value is
recommended.
Inter-Freq UE CellMLB. Network plan This parameter specifies the

Number Offload InterFrqUeNumOf- (negotiation UL-synchronized UE
Offset floadOffset not required) number threshold for
transferring loads to
neighboring cells with which
the source cell does not
exchange load information
during inter-frequency
MLB.
This parameter controls the
user number threshold for
offloading loads to
the source cell does not
exchange load information.
Meanwhile, setting this
parameter does not affect the
triggering of MLB to
the source cell exchanges
load information. If both
exchange and non-exchange
modes are activated, set this
parameter based on the
minimum tolerable average
UE throughput and the
relationship between the
average UE throughput and
the number of UEs in live
networks.
The following table describes the parameter that must be set in an EutranInterNFreq MO to
configure the frequency priority for inter-frequency MLB.

eRAN
MLB Frequency EutranInterNFreq. Network plan This parameter

Priority MlbFreqPriority (negotiation not specifies the MLB
required) priority of an intra-
RAT neighboring
frequency. The value
0 indicates the lowest
priority. The eNodeB
selects a high-
priority frequency as
the target frequency
for MLB.
The following table describes the parameter that must be set in a UtranNFreq MO to configure
the frequency priority for inter-RAT MLB.
MLB Frequency UtranNFreq. Network plan This parameter

Priority MlbFreqPriority (negotiation not specifies the MLB
required) priority of a UTRA
frequency. The value
0 indicates the lowest
priority. The eNodeB
selects a high-
priority frequency as
the target frequency
for MLB.
configure the neighboring E-UTRA frequency if the IdleUE(IdleUE) option of the
CellMLB.InterFreqUeTrsfType parameter is selected.
Inter frequency cell EutranInterNFreq. Network plan Set this parameter to

resel priority CellReselPriorityCf- (negotiation not CFG(Configure)
configure indicator gInd required) for frequencies
involved in load pre-
balancing.
Inter frequency cell EutranInterNFreq. Network plan Set this parameter

resel priority CellReselPriority (negotiation not based on the network
required) plan.

eRAN
Inter frequency high EutranInterNFreq. Network plan The parameter value

priority threshold ThreshXhigh (negotiation not must be greater than
required) the
InterFreqHoGroup
.InterFreqHoA2Thd
Rsrp parameter value
of neighboring cells
on the neighboring
frequency.
The parameter value
must also be greater
than the smaller
value of the
CellResel.ThrshSer
vLow and
CellResel.SNonIntr
aSearch parameter
values of
neighboring cells on
the neighboring
frequency.
For details about inter-RAT MLB, see Inter-RAT Mobility Load Balancing Feature Parameter
Description.
13.1.6 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 13-1 in a summary data file, which also contains
other data for the new eNodeBs to be deployed.
Then, import the summary data file into the Configuration Management Express (CME) for
batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial
configuration guide for the eNodeB, which is available in the eNodeB product documentation.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
l The MOs in Table 13-1 are contained in a scenario-specific summary data file. In this
situation, set the parameters in the MOs, and then verify and save the file.
l Some MOs in Table 13-1 are not contained in a scenario-specific summary data file. In
this situation, customize a summary data file to include the MOs before you can set the
parameters.

eRAN
Table 13-1 Parameters for user-number-based inter-frequency MLB
MO Sheet in the Parameter Group Remarks

Summary
Data File
CellAlgoSwitch CellAlgoSwitc MlbAlgoSwitch This MO must be

h customized in a list-
type sheet of the
template.
CellMLB CellMLB LocalCellId, This MO must be

MlbTriggerMode, customized in a list-
InterFreqMlbUeNumThd, type sheet of the
MlbUeNumOffset, template.
UeNumDiffThd,
MlbMaxUeNum,
MlbUeSelectPrbThd,
InterFreqUeTrsfType,
InterFreqMLBRanShare-
Mode, InterFreqIdleMlb-
Mode, MlbHoCellSelect-
Strategy, PunishJudgePrd-
Num, FreqPunishPrdNum,
MlbUeSelectPunishTimer,
CellPunishPrdNum,
CellCapacityScaleFactor,
InterFrqUeNumOffloa-
dOffset
ENodeBAlgoSwitch ENodeBAlgoS HoModeSwitch, This MO must be

witch MlbAlgoSwitch customized in a list-
type sheet of the
template.
CellOp CellOp OpUeNumRatio This MO must be

customized in a list-
type sheet of the
template.
eNodeBMlb eNodeBMLB InterFreqIdleMlbMode, This MO must be

InterFreqIdleMlbInterval, customized in a list-
InterFreqIdleMlbStaThd type sheet of the
template.
EutranInterNFreq EutranInterNF LocalCellId, DlEarfcn, This MO must be

req CellReselPriorityCfgInd, customized in a list-
CellReselPriority, type sheet of the
IfMlbThdRsrpOffset template.

eRAN

Summary
Data File
CellMlbHo CellMlbHo MlbHoInProtectMode, This MO must be

MlbHoInProtectTimer customized in a list-
type sheet of the
template.
InterFreqHoGroup InterFreqHoGr InterFreqLoadBasedHoA4 This MO must be

oup ThdRSRP, customized in a list-
InterFreqLoadBasedHoA4 type sheet of the
ThdRSRQ template.
SpidCfg (Optional) SpidCfg Spid, InterFreqMlbSwitch, This MO must be

InterRatMlbSwitch customized in a list-
type sheet of the
template.
Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure is as follows:
Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the CME
to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press F1 when
a CME window is active, and select Managing the CME > CME Guidelines > LTE
Application Management > eNodeB Related Operations > Customizing a Summary Data
File for Batch eNodeB Configuration.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station
Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME
into the customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs according to the setting notes provided
in section "Data Preparation" and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station
Bulk Configuration Data (CME client mode), to import the summary data file into the CME,
and then start the data verification.
Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental
Scripts (U2000 client mode), or choose Area Management > Planned Area > Export
Incremental Scripts (CME client mode), to export and activate the incremental scripts. For
detailed operations, see Managing the CME > CME Guidelines > Script File Management
> Exporting Incremental Scripts from a Planned Data Area in the CME online help.
----End

eRAN
Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.
Step 2 In area 1 shown in Figure 13-1, select the eNodeB to which the MOs belong.
Figure 13-1 MO search and configuration window
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export
and activate the incremental scripts.
----End
Using MML Commands

MLB by Transferring RRC_REL UEs
Step 1 Run the MOD CELLMLB command with the Mobility Load Balancing Trigger Mode
parameter set to UE_NUMBER_ONLY(UeNumMode), with the IdleUE(IdleUE) option of
the InterFreq MLB Transfer Type parameter selected, and with the Inter-Freq Idle MLB
UE Number Threshold parameter specified.

eRAN
Step 2 Run the MOD EUTRANINTERNFREQ command with the Cell reselection priority
configure indicator parameter set to CFG(Configure) and with the Cell reselection priority
parameter specified based on the network plan.
Step 3 Run the MOD CELLALGOSWITCH command with the InterFreqMlbSwitch

(InterFreqMlbSwitch) option of the Load balancing algorithm switch parameter selected.
----End
MLB by Transferring UL-Sync UEs
parameter set to UE_NUMBER_ONLY(UeNumMode), with the SynchronizedUE
(SynchronizedUE) option of the InterFreq MLB Transfer Type parameter selected, and with
Inter-frequency Mobility Load Balancing UE Number Threshold parameter specified.

(InterFreqMlbSwitch) or InterFreqBlindMlbSwitch(InterFreqBlindMlbSwitch) option of
the Load balancing algorithm switch parameter selected. If both options are selected, proceed
to the next step.
Step 3 Run the MOD CELLMLB command with the Inter-Freq UE Number Offload Offset
parameter specified.
----End
MML Command Examples

MOD CELLMLB: LocalCellId=0, InterFreqIdleMlbUeNumThd=80,
MlbTriggerMode=UE_NUMBER_ONLY, InterFreqUeTrsfType=IdleUE-1;
MOD EutranInterNFreq: LocalCellId=0, DlEarfcn=6000, CellReselPriorityCfgInd=CFG,
CellReselPriority=6;
MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=InterFreqMlbSwitch-1;
MLB by Transferring UL-Sync UEs With Exchange Mode Enabled

MOD CELLMLB: LocalCellId=0, InterFreqMlbUeNumThd=100,
MlbTriggerMode=UE_NUMBER_ONLY, InterFreqUeTrsfType=SynchronizedUE-1;
MOD CELLALGOSWITCH: LocalCellId=0,
MlbAlgoSwitch=InterFreqMLBSwitch-1&InterFreqBlindMlbSwitch-0;
MLB by Transferring UL-Sync UEs With Both Exchange and Non-Exchange Modes
Enabled
MOD CELLMLB: LocalCellId=0, InterFreqMlbUeNumThd=100,
MlbTriggerMode=UE_NUMBER_ONLY, InterFreqUeTrsfType=SynchronizedUE-1;
13.1.7 Activation Observation
MLB by Transferring UL-Sync UEs

To use SON logs to verify whether user-number-based inter-frequency MLB by transferring
UL-sync UEs has been activated, perform the following steps:
Step 1 On the U2000 client, choose SON > SON Log.

eRAN
Step 2 On the Query SON Log tab page, click LTE MLB Log in the Log Category drop-down list
in the upper left corner, and click Inter-Frequency Handover Statistics in the Custom list
under Event Name. Then click Query to query SON logs. User-number-based inter-frequency
MLB has been activated if the following information is displayed in the event description:
l Load status of the serving cell: threshold for user-number-based inter-frequency MLB and
the number of UL-sync UEs
l Information about inter-frequency neighboring cells: mobile country code (MCC), mobile
network code (MNC), eNodeB ID, cell ID, downlink EARFCN, and the number of UL-sync
UEs
l Handover information: number of UEs that have been successfully handed over from the
serving cell (excluding UEs for which the RRC connection is reestablished to the source cell)
----End
Performance counters can also be used for activation observation. For details, see 13.1.10
Performance Monitoring.

Performance counters can be used for activation observation. For details, see 13.1.10
13.1.8 Deactivation
Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for Existing
eNodeBs. In the procedure, modify parameters according to Table 13-2.

eRAN
MO Sheet in the Parameter Group Setting Notes

Summary Data
File
CellAlgoSwitch CellAlgoSwitch MlbAlgoSwitch l To disable inter-

frequency MLB
with load
information
exchange,
deselect the
InterFreqMlbS-
witch
(InterFreqMlbS
witch) option.
l To disable inter-
frequency MLB
without load
information
exchange,
deselect the
InterFreq-
BlindMlbSwitch
(InterFreq-
BlindMlbSwitch
) option.

On the CME, set parameters according to Table 13-2. For detailed instructions, see Using the
CME to Perform Single Configuration described for feature activation.
Using MML Commands

Run the MOD CELLALGOSWITCH command with the InterFreqMlbSwitch
(InterFreqMlbSwitch) option of the Load balancing algorithm switch parameter deselected
to disable user-number-based inter-frequency MLB.
Run the MOD CELLALGOSWITCH command with the InterFreqBlindMlbSwitch
(InterFreqBlindMlbSwitch) option of the Load balancing algorithm switch parameter
deselected.

MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=InterFreqMLBSwitch-0;
MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch= InterFreqBlindMlbSwitch-0;
13.1.9 Reconfiguration
For measurement-based handovers, the eNodeB selects target frequencies randomly or based
on the frequency priorities for MLB, depending on the setting of the

eRAN
CellMLB.FreqSelectStrategy parameter. If the eNodeB selects target frequencies based on the

frequency priorities, the E-UTRAN and UTRAN frequency priorities specified by the
EutranInterNFreq.MlbFreqPriority and UtranNFreq.MlbFreqPriority parameters take
effect. In addition, if both a neighboring E-UTRA frequency and a neighboring UTRA frequency
are selected as target frequencies, it is required that the CellMLB.InterFreqLoadEvalPrd and
CellMLB.InterRatLoadEvalPrd parameters be set to the same value.
13.1.10 Performance Monitoring

Table 13-3 lists the counters used to monitor the performance of user-number-based inter-
frequency MLB.
After user-number-based inter-frequency MLB is enabled, the difference in the

L.Traffic.User.Ulsync.Avg counter value between frequencies drops. In addition, the average
downlink bit rate (equal to L.Thrp.bits.DL/L.Thrp.Time.DL) of UEs in the MLB system may
increase. The MLB system consists of the source cell and its inter-frequency cells between which
load can be transferred.
Table 13-3 Performance counters related to user-number-based inter-frequency MLB
Counter ID Counter Name Counter Description
1526729559 L.HHO.InterFreq.UeNum Number of user-number-

Load.PrepAttOut based inter-frequency
handover preparation
attempts
1526729560 L.HHO.InterFreq.UeNum Number of user-number-

Load.ExecAttOut based inter-frequency
handover execution attempts
1526729561 L.HHO.InterFreq.UeNum Number of successful user-

Load.ExecSuccOut number-based inter-
frequency handover
executions
1526728333 L.Traffic.User.Ulsync.Avg Average number of UL-sync

UEs in a cell
1526728261 L.Thrp.bits.DL Total downlink traffic

volume of PDCP SDUs in a
cell
1526728262 L.Thrp.Time.DL Total transmission duration

of downlink PDCP SDUs in
a cell
1526730528 L.InterFreq.HighLoad.Du Duration in which a cell with

r.Cell inter-frequency MLB
enabled is in the high load
state

eRAN
1526730529 L.InterFreq.HighLoad.Nu Number of times a cell with

m.Cell inter-frequency MLB
enabled entered from the low
load state to the high load
state
1526730526 L.InterFreq.Load.Meas.N Number of times the eNodeB

um.Cell delivered the load-triggered
inter-frequency
measurement configuration
to UEs in a cell
1526730527 L.InterFreq.Load.MeasSu Number of times the load-

cc.Num.Cell triggered inter-frequency
measurement succeeded
1526729593 L.HHO.InterFddTdd.UeN Number of user-number-

umLoad.PrepAttOut based inter-duplex-mode
outgoing handover
preparation attempts
1526729594 L.HHO.InterFddTdd.UeN Number of user-number-

umLoad.ExecAttOut based inter-duplex-mode
outgoing handover execution
attempts
1526729595 L.HHO.InterFddTdd.UeN Number of successful user-

umLoad.ExecSuccOut number-based inter-duplex-
mode outgoing handover
executions
1526729877 L.RRCRel.load.Dedicated Number of times the highest

Pri.LTE.High dedicated priority was
assigned to E-UTRA
frequencies as indicated in an
IMMCI IE sent from a high-
load cell
13.1.11 Parameter Optimization
MLB Algorithm
the MLB algorithm.

eRAN

Name
Inter-frequency CellMLB. Network plan This parameter specifies the UL-

Mobility Load InterFreqMlbUe- (negotiation not sync UE number threshold for
Balancing UE NumThd required) triggering the "user-number-
Number based inter-frequency MLB by
Threshold transferring UL-sync UEs"
algorithm. If this parameter is set
to a large value, this MLB
algorithm is triggered when the
number of UL-sync UEs in the
cell is large. If this parameter is
set to a small value, this MLB
cell is small.
Inter-Freq Idle CellMLB. Network plan This parameter specifies the UL-
MLB UE InterFreqIdleMl- (negotiation not sync UE number threshold for
Number bUeNumThd required) triggering the "user-number-
Threshold based inter-frequency MLB by
transferring RRC_REL UEs"
algorithm. If this parameter is set
to a large value, this MLB
cell is large. If this parameter is
set to a small value, this MLB
cell is small.
Mobility Load CellMLB. Network plan This parameter specifies the

Balancing UE MlbUeNumOffse (negotiation not offset to the threshold for user-
Number Offset t required) number-based inter-frequency
MLB. This offset is used to
prevent user number fluctuations
from frequently triggering and
stopping MLB.
The recommended value is 20.

eRAN

Name
Ue Number CellMLB. Network plan This parameter specifies a

Difference UeNumDiffThd (negotiation not threshold used in candidate cell
Threshold required) selection. This threshold is
expressed as a percentage of the
UL-sync UE number difference
between serving and neighboring
cells. A larger value of this
parameter results in a higher
requirement for the difference. A
smaller value of this parameter
results in a lower requirement.

Balancing Max MlbMaxUeNum (negotiation not maximum number of UEs that
UE Number required) can be transferred within an MLB
period. If this parameter is set to
a large value, the load on the
source cell can decrease quickly,
but the load on target cells also
rises rapidly.

Balancing UE MlbUeSe- (negotiation not threshold for the PRB usage of a
Selection PRB lectPrbThd required) single UE used in UE selection
Usage Threshold for MLB. A larger value of this
parameter results in more UEs
that meet the selection
conditions.
If the
CellMLB.MlbTriggerMode
parameter is set to
UE_NUMBER_ONLY
(UeNumMode), the
recommended value of the
CellMLB. parameter is 50.
Number of CellMLB. Network plan The parameter specifies the

Periods for PunishJudgePrd- (negotiation not number of consecutive MLB
Punishment Num required) periods within which the eNodeB
Judgement evaluates a penalty on a
frequency.

eRAN

Name
Number of CellMLB. Network plan This parameter specifies the

Periods for FreqPunishPrdN (negotiation not number of consecutive MLB
Punishment on um required) periods that a penalty on a
Frequency neighboring frequency lasts.
During the penalty, the eNodeB
no longer selects the frequency as
a target.
Number of CellMLB. Network plan This parameter specifies the

Periods for CellPunishPrdN (negotiation not number of consecutive MLB
Punishment on um required) periods that a penalty on a
Cell neighboring cell lasts. During the
penalty, the eNodeB no longer
selects the cell as a target.
MLB UE CellMLB. Network plan This parameter specifies the UE

Selection Punish MlbUeSelectPu- (negotiation not penalty timer. Before the timer
Timer nishTimer required) expires, the eNodeB no longer
selects the UE for MLB.

eRAN

Name
Cell Capacity CellMLB. Network plan This parameter specifies the scale
Scale Factor CellCapacitySca- (negotiation not factor used to determine the MLB
leFactor required) capability of a cell. This factor
helps adjust the MLB target in
user-number-based inter-
frequency MLB.
When setting this parameter, take
the deployment purpose and the
spectral efficiency of the
operating frequency of the cell
into consideration. Ensure that
this parameter is set to a value
less than 10 for cells whose
operating frequencies are used to
provide in-depth coverage or
have low spectral efficiency.
Otherwise, ensure that this
parameter is set to a value greater
than 10 for cells whose operating
frequencies have high spectral
efficiency. Adjust this parameter
gradually based on the purpose to
achieve the highest average UE
throughput.
In addition, when setting this
parameter, operators also need to
take into consideration the
maximum number of UEs that a
cell can serve. In heavy-traffic
scenarios, if the maximum
number of UEs that a cell can
serve is small, the number of UEs
that the cell serves is easily to
reach the maximum number and
the cell rejects new UE access
requests. Therefore, a small value
of this parameter for such a cell
helps increase the RRC setup
success rate.
Inter-Frequency Handover Parameter Group

The following table describes the parameter that must be set in an InterFreqHoGroup MO to

eRAN
Load Based Interfreq InterFreqHo Network plan This parameter specifies the
RSRP threshold Group. (negotiation not RSRP threshold for event A4
InterFreqLoa required) that triggers load-based inter-
dBasedHoA4T frequency handovers. When
hdRsrp the measured RSRP value is
greater than the sum of the
InterFreqHoGroup.InterFr
eqLoadBasedHoA4ThdRsrp
and
EutranInterNFreq.IfMlbTh
dRsrpOffset parameter
values, the UE sends an inter-
frequency measurement
report to the eNodeB. The
default value is -103.
Inter-Frequency MLB Offset

The following table describes the parameter that must be set in an EutranInterNFreq MO to
set the offset to the inter-frequency MLB threshold.
Inter-Freq Mlb EutranInterNFreq. Network plan This parameter

Threshold RSRP IfMlbThdRsrpOff- (negotiation not specifies the offset to
Offset set required) the RSRP threshold
for load-based inter-
frequency
handovers. When the
measured RSRP
value is greater than
the sum of the
InterFreqHoGroup
.InterFreqLoadBase
dHoA4ThdRsrp and
EutranInterNFreq.
IfMlbThdRsrpOff-
set parameter values,
the UE sends an
inter-frequency
measurement report
to the eNodeB.
13.1.12 Troubleshooting
None

eRAN
13.2 LOFD-001032 Intra-LTE Load Balancing
13.2.1 When to Use LOFD-001032 Intra-LTE Load Balancing

Use PRB-usage-based inter-frequency MLB in a multi-carrier network where both the following
conditions are met:
l Some UEs are data cards. Alternatively, due to the fee policy (for example, unlimited data
plan), some smartphones are used as data cards.
l PRB usage is unbalanced between carriers due to user distribution and characteristics of
data card user behavior. The UEs are in the data transmission state for a long time and the
PRB usage of a single UE is high. These characteristics can be determined by the fee policy
and network tracing.
For details about when to use exchange mode and non-exchange mode, see 13.1.1 When to Use
LOFD-070215 Intra-LTE User Number Load Balancing.

For details, see 13.1.2 Required Information.
13.2.3 Planning
For details, see 13.1.3 Planning.
13.2.4 Requirements
deploying LOFD-001032 Intra-LTE Load Balancing, the operator must purchase and activate
the licenses for the feature based on the setting of the CellMLB.MlbTriggerMode parameter.
l If the CellMLB.MlbTriggerMode parameter is set to PRB_ONLY(PrbMode), the license

listed in the following table must be activated.
Feature ID Feature Model License NE Sales Unit

Name Control
Item
LOFD-00103 Intra- LT1S00 Intra-LTE eNodeB per RRC

2 LTE ILLB00 Load Connected
Load Balancing User
Balancin (FDD)
g


eRAN

Name Control
Item
LOFD-00103 Intra-LTE LT1S00ILL Intra- eNodeB per RRC

2 Load B00 LTE Connected
Balancing Load User
Balancin
g (FDD)
LOFD-07021 Intra-LTE LT1SILUN Intra- eNodeB per RRC

5 User Number LB00 LTE User Connected
Load Number User
Balancing Load
Balancin
g (FDD)

Required Data
The following table describes the parameter that must be set in a CellMLB MO to configure the
MLB algorithm.
Mobility Load CellMLB. User-defined The recommended

Balancing Trigger MlbTriggerMode value is
Mode PRB_ONLY
(PrbMode).
The preparation of other required data is the same as that for user-number-based inter-frequency
MLB. For details, see Required Data.

eRAN
The following table describes the parameter that must be set in a CellAlgoSwitch MO to enable
the inter-frequency MLB algorithm.
Load balancing CellAlgoSwitch. Network plan Set this parameter to

algorithm switch MlbAlgoSwitch (negotiation not control load
required) information
exchange. To enable
exchange mode,
select the
InterFreqMlbS-
witch
(InterFreqMlbS-
witch) option of this
parameter. To enable
non-exchange mode,
BlindMlbSwitch
(InterFreq-
BlindMlbSwitch)
option. The two
options can be
selected at the same
time.

eRAN

Name
Mlb Ho Cell CellMLB. Network plan This parameter specifies whether

select MlbHoCellSelect (negotiation not the eNodeB can try a second-
Strategy Strategy required) strongest neighboring cell for MLB
when the eNodeB fails to initiate
handovers to the strongest cell
during inter-frequency MLB with
load information exchange.
You are advised to set this
parameter to
ONLY_STRONGEST_CELL
(Only Try Strongest Cell).
Otherwise, after UEs are handed
over to the non-strongest
neighboring cells, these UEs are
transferred to the strongest
neighboring cell by coverage-
based intra-frequency handovers.
This causes that the the load
balancing effects are not achieved
and increases the number of
ineffective handovers.
Inter-Freq CellMLB. Network plan This parameter specifies the PRB

Offload InterFreqOffloa- (negotiation not usage threshold for transferring
Offset dOffset required) loads to neighboring cells with
which the source cell does not
exchange load information during
inter-frequency MLB.
This parameter controls the PRB
usage threshold for offloading
loads to neighboring cells with
which the source cell does not
exchange load information.
Meanwhile, setting this parameter
does not affect the triggering of
MLB to neighboring cells with
which the source cell exchanges
load information. If both exchange
and non-exchange modes are
activated, set this parameter based
on the minimum tolerable average
UE throughput and the relationship
between the average UE
throughput and the PRB usage in
live networks.

eRAN
(Optional) The following table describes the parameters that must be set in SpidCfg MOs to
configure SPIDs. An SpidCfg MO consists of parameters related to the inter-frequency handover
priority for UL-sync UEs and the SPID-based inter-frequency MLB switch.
Spid SpidCfg.Spid Network plan This parameter

(negotiation not specifies an SPID.
required) The value range is 1
to 256.
RAT frequency SpidCfg. Network plan This parameter

priority indication RatFreqPriorityInd (negotiation not specifies whether to
required) configure a
frequency priority
group.
RAT frequency SpidCfg. Network plan This parameter

priority group ID RatFreqPriority- (negotiation not uniquely identifies a
GroupId required) frequency priority
group. The value
range is 0 to 255.
InterFreq Mlb SpidCfg. Network plan If the parameter is set

Switch InterFreqMlbS- (negotiation not to TRUE(TRUE),
witch required) inter-frequency load
balancing is allowed
for UEs with the
SPID. If the
parameter is set to
FALSE(FALSE),
inter-frequency load
balancing is not
allowed for UEs with
the SPID. This
parameter takes
effect only for UEs
that will access the
network after the
parameter setting.
13.2.6 Activation
Enter the values of the parameters listed in Table 13-4 in a summary data file, which also contains
other data for the new eNodeBs to be deployed.

eRAN
parameters.
Table 13-4 Parameters for PRB-usage-based inter-frequency MLB

Summary Data
File
CellAlgoSwit CellAlgoSwitch MlbAlgoSwitch This MO must be

ch customized in a list-
type sheet of the
template.

InterFreqMlbThd, customized in a list-
LoadExchangePeriod, type sheet of the
LoadOffset, LoadDiffThd, template.
LoadTransferFactor,
MlbTriggerMode,
MlbMaxUeNum, MlbUeSe-
lectPrbThd,
Mode, MlbMinUeNumThd,
MlbMinUeNumOffset,
MlbHoCellSelectStrategy,
PunishJudgePrdNum,
FreqPunishPrdNum,
CellPunishPrdNum,
InterFreqOffloadOffset

type sheet of the
template.
EutranInterN EutranInterNFreq LocalCellId, DlEarfcn, This MO must be

Freq IfMlbThdRsrpOffset customized in a list-
type sheet of the
template.
InterFreqHo InterFreqHoGroup InterFreqLoadBasedHoA4T This MO must be

Group hdRSRP, customized in a list-
InterFreqLoadBasedHoA4T type sheet of the
hdRSRQ template.

eRAN

Summary Data
File
ENodeBAlgo ENodeBAlgoSwitc HoModeSwitch This MO must be

Switch h customized in a list-
type sheet of the
template.
CellOp CellOp OpUlRbUsedRatio, This MO must be

OpDlRbUsedRatio customized in a list-
type sheet of the
template.
SpidCfg SpidCfg Spid, InterFreqMlbSwitch, This MO must be

(Optional) InterRatMlbSwitch customized in a list-
type sheet of the
template.

----End

eRAN

----End
Using MML Commands

parameter set to PRB_ONLY(PrbMode) and with the Inter-Frequency Mobility Load
Balancing Threshold parameter specified.

the Load balancing algorithm switch parameter selected to enable inter-frequency MLB. If
both options are selected, proceed to the next step.

eRAN
Step 3 Run the MOD CELLMLB command with the Inter-Freq Offload Offset parameter specified.
Step 4 (Optional) Run the ADD SPIDCFG command to set an SPID and enable SPID-specific inter-
frequency MLB. If the SPID exists, run the MOD SPIDCFG command to modify the
configuration as required.
----End

MLB with Exchange Mode Enabled
MOD CELLMLB: LocalCellId=0, InterFreqMlbThd=60, MlbTriggerMode=PRB_ONLY;
MlbAlgoSwitch=InterFreqMlbSwitch-1&InterFreqBlindMlbSwitch-0;
ADD SPIDCFG: Spid=1, RatFreqPriorityInd=NOT_CFG, InterFreqMlbSwitch=TRUE;
MLB with Both Exchange and Non-Exchange Modes Enabled

MOD CELLMLB: LocalCellId=0, InterFreqMlbThd=60, LoadOffset=8,
InterFreqOffloadOffset=12, MlbTriggerMode=PRB_ONLY;

To use SON logs to verify whether PRB-usage-based inter-frequency MLB has been activated,
perform the following steps:
Step 2 On the Query SON Log tab page, click LTE MLB Log in the Log Category drop-down list
in the upper left corner, and click Inter-Frequency Handover Statistics in the Custom list
under Event Name. Then click Query to query SON logs. PRB-usage-based inter-frequency
MLB has been activated if the following information is displayed in the event description:
l Load status of the serving cell: inter-frequency MLB threshold, uplink PRB usage, and
downlink PRB usage
l Information about inter-frequency neighboring cells: MCC, MNC, eNodeB ID, cell ID,
downlink EARFCN, uplink PRB usage, and downlink PRB usage
l Handover information: number of UEs that have been successfully handed over from the
serving cell and the number of PRBs occupied by these UEs
----End
Performance counters can also be used for activation observation. For details, see 13.2.10
13.2.8 Deactivation


eRAN

Summary Data
File
CellAlgoSwi CellAlgoSwitch MlbAlgoSwitch l To disable inter-

tch frequency MLB with
load information
exchange, deselect the
InterFreqMlbSwitch
(InterFreqMlbSwitch)
option.
l To disable inter-
frequency MLB without
load information
exchange, deselect the
InterFreqBlindMlbS-
witch(InterFreq-
BlindMlbSwitch)
option.

Using MML Commands

(InterFreqMlbSwitch) option of the Load balancing algorithm switch parameter deselected.
Run the MOD CELLALGOSWITCH command with the InterFreqBlindMlbSwitch
(InterFreqBlindMlbSwitch) option of the Load balancing algorithm switch parameter
deselected.

MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=InterFreqBlindMlbSwitch-0;
For measurement-based handovers, the eNodeB selects target frequencies randomly or based
on the frequency priorities for MLB, depending on the setting of the
CellMLB.FreqSelectStrategy parameter. If the eNodeB selects target frequencies based on the
frequency priorities, the E-UTRAN and UTRAN frequency priorities specified by the
EutranInterNFreq.MlbFreqPriority and UtranNFreq.MlbFreqPriority parameters take

eRAN
effect. In addition, if both a neighboring E-UTRA frequency and a neighboring UTRA frequency
are selected as target frequencies, it is required that the CellMLB.InterFreqLoadEvalPrd and
CellMLB.InterRatLoadEvalPrd parameters be set to the same value.

Table 13-6 lists the counters used to monitor inter-frequency MLB performance.
After PRB-usage-based inter-frequency MLB is enabled, the difference in the

L.ChMeas.PRB.DL.Used.Avg or L.ChMeas.PRB.UL.Used.Avg counter value between
frequencies drops. In addition, the average downlink (or uplink) bit rate of UEs in the MLB
system may increase. The downlink bit rate is equal to L.Thrp.bits.DL/L.Thrp.Time.DL, and
the uplink bit rate is equal to L.Thrp.bits.UL/L.Thrp.Time.UL.
Table 13-6 Performance counters related to intra-RAT MLB
1526728526 L.HHO.InterFreq.Load.Pre Number of load-based inter-frequency

pAttOut handover preparation attempts
1526728527 L.HHO.InterFreq.Load.Ex- Number of load-based inter-frequency

ecAttOut handover execution attempts
1526728528 L.HHO.InterFreq.Load.Ex- Number of successful load-based inter-

ecSuccOut frequency handover executions
1526726740 L.ChMeas.PRB.DL.Used.A Average number of PRBs used on the

vg PDSCH
1526726737 L.ChMeas.PRB.UL.Used.A Average number of used uplink PRBs

vg
1526728262 L.Thrp.Time.DL Total transmission duration of

downlink PDCP SDUs in a cell
1526728261 L.Thrp.bits.DL Total downlink traffic volume of PDCP

SDUs in a cell
1526728260 L.Thrp.Time.UL Total reception duration of uplink

PDCP PDUs in a cell
1526728259 L.Thrp.bits.UL Total uplink traffic volume of PDCP

PDUs in a cell
1526729590 L.HHO.InterFddTdd.Load. Number of load-based inter-duplex-

PrepAttOut mode outgoing handover preparation
attempts
1526729591 L.HHO.InterFddTdd.Load. Number of load-based inter-duplex-

ExecAttOut mode outgoing handover execution
attempts

eRAN
1526729592 L.HHO.InterFddTdd.Load. Number of successful load-based inter-

ExecSuccOut duplex-mode outgoing handover
executions
1526730528 L.InterFreq.HighLoad.Dur. Duration in which a cell with inter-

Cell frequency MLB enabled is in the high
load state
1526730529 L.InterFreq.HighLoad.Nu Number of times a cell with inter-

m.Cell frequency MLB enabled entered from
the low load state to the high load state
1526730526 L.InterFreq.Load.Meas.Nu Number of times the eNodeB delivered

m.Cell the load-triggered inter-frequency
measurement configuration to UEs in a
cell
1526730527 L.InterFreq.Load.MeasSuc Number of times the load-triggered

c.Num.Cell inter-frequency measurement
succeeded
If both PRB-usage-based inter-frequency MLB and user-number-based inter-frequency MLB

are enabled, the counters listed below indicate the total statistics of the two algorithms. The
values of the following counters minus the values of counters for user-number-based inter-
frequency MLB listed in Table 13-3 are the measurement results for PRB-usage-based inter-
frequency MLB:
l L.HHO.InterFreq.Load.PrepAttOut
l L.HHO.InterFreq.Load.ExecAttOut
l L.HHO.InterFreq.Load.ExecSuccOut
l L.HHO.InterFddTdd.Load.PrepAttOut
l L.HHO.InterFddTdd.Load.ExecAttOut
l L.HHO.InterFddTdd.Load.ExecSuccOut
NOTE
If PRB-usage-based and transport-QoS-based MLB are both enabled, the measurement results for PRB-
usage-based inter-frequency MLB are the total statistics of the two types of MLB.
MLB Algorithm
The following table describes the parameters that must be set in the CellMLB MO to configure
the MLB algorithm.

eRAN

Name
Load Offset CellMLB.LoadOffset Network plan This parameter specifies

(negotiation not the offset applied to the
required) threshold for triggering
MLB. This mechanism
helps prevent load
fluctuations from
frequently triggering and
stopping MLB. An
excessively small value of
this parameter does not help
reduce the probability of
ping-pong effect. The
recommended value is 8.
Load CellMLB. Network plan This parameter specifies

Difference LoadDiffThd (negotiation not the threshold of PRB usage
Threshold required) difference between the
serving cell and a
neighboring cell for
triggering MLB. The
recommended value is 15.
Inter- CellMLB. Network plan This parameter specifies

Frequency InterFreqMlbThd (negotiation not the PRB usage threshold for
Mobility required) triggering inter-frequency
Load MLB. The default value is
Balancing 60.
Threshold

eRAN

Name
Load CellMLB. Network plan This parameter specifies

Transfer LoadTransferFactor (negotiation not the factor used to control
Factor required) the amount of load
transferred during a single
MLB period. A larger value
results in a larger total
amount of load to be
transferred. (After load
transfer, the target cell's
load can be higher than that
of the source cell.) A
smaller value results in the
opposite effect. If this
parameter is set to the
minimum value 0, after
load transfer, the load of the
target cell will not exceed
that of the source cell. In
MLB without load
information exchange, this
parameter does not need to
be set. The recommended
value is 0.
MLB CellMLB. Network plan This parameter specifies

Minimum UE MlbMinUeNumThd (negotiation not the UL-sync UE number
Number required) threshold for PRB-usage-
Threshold based inter-frequency
MLB. The recommended
value is 10.
MLB CellMLB. Network plan This parameter specifies

Minimum UE MlbMinUeNumOffset (negotiation not the offset to the UL-sync
Number required) UE number threshold for
Offset PRB-usage-based inter-
frequency MLB. This
offset is used to prevent the
fluctuations in the number
of UEs from frequently
triggering and stopping
MLB. The recommended
value is 5.

eRAN

Name
Mobility CellMLB.MlbUeSe- Network plan This parameter specifies

Load lectPrbThd (negotiation not the PRB usage threshold for
Balancing UE required) selecting UEs in PRB-
Selection usage-based inter-
PRB Usage frequency MLB.
Threshold The recommended value is
2.
Other Parameters
Adjust the settings of the following parameters as described in 13.1.11 Parameter
Optimization:
l CellMLB.MlbMaxUeNum
l Penalty-related parameters: CellMLB.PunishJudgePrdNum,
CellMLB.FreqPunishPrdNum, CellMLB.CellPunishPrdNum, and
CellMLB.MlbUeSelectPunishTimer
l InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrp
l EutranInterNFreq.IfMlbThdRsrpOffset
None
13.3 LOFD-070204 Operator Load Based Intra-LTE MLB
13.3.1 When to Use LOFD-070204 Operator Load Based Intra-LTE

MLB
In RAN sharing scenarios, to operate independently, use operator-level MLB.
For details about when to use exchange mode and non-exchange mode, see 13.1.1 When to Use
LOFD-070215 Intra-LTE User Number Load Balancing.
Set the CellMLB.InterFreqMLBRanShareMode parameter to the same value for all cells.
Otherwise, this feature will not work as expected.

13.3.3 Planning

eRAN
13.3.4 Requirements
deploying LOFD-070204 Operator Load Based Intra-LTE MLB, the operator must purchase
and activate the licenses for the feature based on the setting of the
l If the CellMLB.MlbTriggerMode parameter is set to PRB_ONLY(PrbMode), the

licenses listed in the following table must be activated.
Feature ID Feature Mode License Control NE Sales Unit

Name l Item
LOFD-00103 Intra-LTE LT1S Intra-LTE Load eNodeB per RRC

2 Load 00ILL Balancing (FDD) Connected
Balancing B00 User
LOFD-07020 Operator LT1S Operator Load eNodeB per cell

4 Load OLB Based Intra-LTE
Based MLB0 MLB (FDD)
Intra-LTE 0
MLB

(UeNumMode), the licenses listed in the following table must be activated.
Feature ID Feature Mode License Control NE Sales Unit

Name l Item
LOFD-07021 Intra-LTE LT1SI Intra-LTE User eNode per RRC

5 User LUNL Number Load B Connected
Number B00 Balancing (FDD) User
Load
Balancing
LOFD-07020 Operator LT1S Operator Load eNode per cell

4 Load OLB Based Intra-LTE B
Based MLB0 MLB (FDD)
Intra-LTE 0
MLB


Name Control Item
LOFD-00103 Intra-LTE LT1S0 Intra-LTE eNodeB per RRC

2 Load 0ILLB Load Connected
Balancing 00 Balancing User
(FDD)

eRAN

Name Control Item
LOFD-07021 Intra-LTE LT1SI Intra-LTE eNodeB per RRC

5 User Number LUNL User Number Connected
Load B00 Load User
Balancing Balancing
(FDD)
LOFD-07020 Operator LT1SO Operator Load eNodeB per cell

4 Load Based LBML Based Intra-
Intra-LTE B00 LTE MLB
MLB (FDD)

Required Data
For details, see the following sections:
l Required Data for the LOFD-070215 Intra-LTE User Number Load Balancing feature
l Required Data for the LOFD-001032 Intra-LTE Load Balancing feature
For details about scenario-specific data except the following parameters, see Scenario-specific
Data for the LOFD-070215 Intra-LTE User Number Load Balancing feature and Scenario-
specific Data for the LOFD-001032 Intra-LTE Load Balancing feature.
Scenario 1: Operator-level User-Number-based Inter-Frequency MLB
The following table describes the parameter that must be set in a CellAlgoSwitch MO to enable
the inter-frequency MLB algorithm.

eRAN
Load balancing CellAlgoSwitch. User-defined Set this parameter to

algorithm switch MlbAlgoSwitch control load
information
exchange. To enable
exchange mode,
select the
InterFreqMlbS-
witch
(InterFreqMlbS-
witch) option of this
parameter. To enable
non-exchange mode,
BlindMlbSwitch
(InterFreq-
BlindMlbSwitch)
option. The two
options can be
selected at the same
time.

eRAN
Mobility Load CellMLB. Network plan This parameter

Balancing Trigger MlbTriggerMode (negotiation not specifies the MLB
Mode required) triggering variable.
PRB_ONLY
(PrbMode) indicates
that the triggering
variable is only the
PRB usage of the
serving cell.
UE_NUMBER_ON
LY(UeNumMode)
indicates that the
triggering variable is
the number of UL-
sync UEs in the
serving cell.
PRB_OR_UE_NU
MBER
(PrbOrUeNumMo
de) indicates that the
triggering variable is
either the PRB usage
or the number of UL-
sync UEs in the
serving cell. It is
recommended that
this parameter be set
to
UE_NUMBER_ON
LY(UeNumMode)
in networks that
serve a large number
of smartphones.
Inter-Frequency CellMLB. User-defined The recommended

MLB RAN Sharing InterFreqMLBRan- value is SHARING
Mode ShareMode (SHARING).

eRAN
Mlb Ho Cell select CellMLB. Network plan This parameter

Strategy MlbHoCellSelect- (negotiation not specifies whether the
Strategy required) eNodeB can try a
second-strongest
neighboring cell for
MLB when the
eNodeB fails to
initiate handovers to
the strongest cell
during inter-
frequency MLB with
load information
exchange.
You are advised to
set this parameter to
ONLY_STRONGE
ST_CELL(Only
Try Strongest Cell).
Otherwise, after UEs
are handed over to
the non-strongest
neighboring cells,
these UEs are
transferred to the
strongest
neighboring cell by
coverage-based
intra-frequency
handovers. This
causes that the the
load balancing
effects are not
achieved and
increases the number
of ineffective
handovers.
Scenario 2: Operator-level PRB-Usage-based Inter-Frequency MLB
The parameter configurations in this scenario are the same as those in scenario 1, except that the
recommended value for the CellMLB.MlbTriggerMode parameter is PRB_ONLY
(PrbMode).

eRAN
13.3.6 Activation
Enter the values of the parameters listed in Table 13-7 and Table 13-8 in a summary data file,
which also contains other data for the new eNodeBs to be deployed.
batch configuration. For detailed instructions, see section "Creating eNodeBs in Batches" in the
initial configuration guide for the eNodeB.
l The MOs in Table 13-7 and Table 13-8 are contained in a scenario-specific summary data
file. In this situation, set the parameters in the MOs, and then verify and save the file.
l Some MOs in Table 13-7 and Table 13-8 are not contained in a scenario-specific summary
data file. In this situation, customize a summary data file to include the MOs before you
can set the parameters.

Summary
Data File
CellAlgoSwitc CellAlgoSwitch MlbAlgoSwitch, This MO must be

h RanShareModeSwitch customized in a list-
type sheet of the
template.
CellMLB CellMLB LocalCellId, MlbTriggerMode, This MO must be

InterFreqMlbUeNumThd, customized in a list-
MlbUeNumOffset, type sheet of the
UeNumDiffThd, template.
MlbMaxUeNum, MlbUeSe-
lectPrbThd, InterFreqUeTrsf-
Type, InterFreqMLBRanShare-
Mode, OpUeNumRatio,
InterFreqIdleMlbMode,
IdleMlbUEReleaseRatio,
MlbHoCellSelectStrategy,
PunishJudgePrdNum,
FreqPunishPrdNum,
CellPunishPrdNum,
CellCapacityScaleFactor,
InterFrqUeNumOffloadOffset

eRAN

Summary
Data File
EutranInterNF EutranInterNFr LocalCellId, DlEarfcn, This MO must be

req eq CellReselPriorityCfgInd, customized in a list-
CellReselPriority, type sheet of the
MlbInterFreqHoEventType, template.
IfMlbThdRsrpOffset

type sheet of the
template.
InterFreqHoGr InterFreqHoGro MlbInterFreqHoA5Thd1Rsrp, This MO must be

oup up MlbInterFreqHoA5Thd1RsrQ, customized in a list-
InterFreqLoadBasedHoA4Thd type sheet of the
RSRP, template.
InterFreqLoadBasedHoA4Thd
RSRQ
ENodeBAlgoS ENodeBAlgoS HoModeSwitch This MO must be

witch witch customized in a list-
type sheet of the
template.
CellOp CellOp OpUeNumRatio This MO must be

type sheet of the
template.

type sheet of the
template.

Summary Data
File
CellAlgoSwitch CellAlgoSwitch MlbAlgoSwitch, This MO must be

RanShareModeSwitch customized in a list-
type sheet of the
template.

eRAN

Summary Data
File

InterFreqMlbThd, customized in a list-
LoadExchangePeriod, type sheet of the
LoadOffset, LoadDiffThd, template.
LoadTransferFactor,
MlbTriggerMode,
MlbMaxUeNum,
MlbUeSelectPrbThd,
Mode, MlbMinUeNumThd,
MlbMinUeNumOffset,
MlbHoCellSelectStrategy
ENodeBAlgoS ENodeBAlgoSwit HoModeSwitch This MO must be

witch ch customized in a list-
type sheet of the
template.

type sheet of the
template.
EutranInterNFre EutranInterNFreq LocalCellId, DlEarfcn, This MO must be

q MlbInterFreqHoEvent- customized in a list-
Type, IfMlbThdRsrpOffset type sheet of the
template.
InterFreqHoGro InterFreqHoGrou MlbInterFreqHoA5Thd1Rs This MO must be

up p rp, customized in a list-
MlbInterFreqHoA5Thd1Rs type sheet of the
rQ, template.
InterFreqLoadBasedHoA4
ThdRSRP,
InterFreqLoadBasedHoA4
ThdRSRQ
CellOp CellOp OpUlRbUsedRatio, This MO must be

OpDlRbUsedRatio customized in a list-
type sheet of the
template.

type sheet of the
template.

eRAN

----End


eRAN
----End
Using MML Commands

parameter set to UE_NUMBER_ONLY(UeNumMode) and the Inter-Frequency MLB RAN
Sharing Mode parameter set to SHARING(SHARING). In addition, set the following
parameters:
l Inter-frequency Mobility Load Balancing UE Number Threshold
l Inter-Freq Idle MLB UE Number Threshold
the Load balancing algorithm switch parameter selected.
Step 3 Run the MOD CELLOP command to set the Operator Ue Number Ratio parameter.
----End

eRAN
Step 1 Run the MOD CELLMLB command with the Inter-Frequency MLB RAN Sharing Mode
parameter set to SHARING(SHARING), with the Mobility Load Balancing Trigger Mode
parameter set to PRB_ONLY(PrbMode), and with the Inter-Frequency Mobility Load
Balancing Threshold parameter specified.
the Load balancing algorithm switch parameter selected.
Step 3 Run the MOD CELLOP command to set the Operator uplink RB used ratio and Operator
downlink RB used ratio parameters.
----End

MOD CELLOP: LocalCellId=0, OpUeNumRatio=16;
MOD CELLMLB: LocalCellId=0, MlbTriggerMode=UE_NUMBER_ONLY,
InterFreqMlbUeNumThd=100, InterFreqIdleMlbUeNumThd=80,
InterFreqMLBRanShareMode=Sharing;

MOD CELLMLB: LocalCellId=0, InterFreqMlbThd=60, InterFreqMLBRanShareMode=SHARING,
MlbTriggerMode=PRB_ONLY;
MOD CELLOP: LocalCellId=0, OpDlRbUsedRatio=16, OpUlRbUsedRatio=16;

Operator-Level User-Number-based Inter-Frequency MLB
To use an MLB monitoring task to verify whether operator-level user-number-based MLB has
been activated, perform the following steps on the U2000 client:
Step 1 Log in to the U2000 client, and choose Monitor > Signaling Trace > Signaling Trace
Management.
Step 2 In the navigation tree on the left of the Signaling Trace Management tab page, double-click
MLB Monitoring under Cell Performance Monitoring. In the displayed MLB Monitoring
dialog box, set the task name, select the eNodeB, and click Next. Set Local cell ID, PLMN ID
of Local Cell, and monitor period (ms) on the Basic tab page, and enter information about
neighboring cells on the Neighbor Cell tab page. Start the task.
Step 3 On the U2000 client, check the value of Inter-Frequency MLB type, which indicates the type
of inter-frequency MLB. If the Inter-Frequency MLB type attribute value is 64, operator-level
user-number-based MLB was triggered.
----End

eRAN
Operator-Level PRB-Usage-based Inter-Frequency MLB

To use an MLB monitoring task to verify whether operator-level PRB-usage-based MLB has
been activated, perform the following steps on the U2000 client:
Management.
MLB Monitoring under Cell Performance Monitoring. In the displayed MLB Monitoring
dialog box, set the task name, select the eNodeB, and click Next. Set Local cell ID, PLMN ID
of Local Cell, and monitor period (ms) on the Basic tab page, and enter information about
neighboring cells on the Neighbor Cell tab page. Start the task.
Step 3 On the U2000 client, check the uplink and downlink PRB usage of the serving cell. If one of
them meets the triggering conditions for inter-frequency MLB, the Inter-Frequency MLB
type attribute is displayed. For example, if the downlink total PRB usage meets the triggering
condition, the Inter-Frequency MLB type attribute value is 32.
----End
The following table lists the mapping between Inter-Frequency MLB type values and different
MLB triggering variables.
Triggering Variable Inter-Frequency MLB type
None 0
Uplink GBR PRB usage 1
Downlink GBR PRB usage 2
Uplink total PRB usage 16
Downlink total PRB usage 32
Number of UL-sync UEs 64
13.3.8 Deactivation


eRAN
Table 13-9 Parameters for operator-level MLB

Summary Data
File
CellMLB CellMLB InterFreqMLBRan- To disable operator-

ShareMode level MLB, set this
parameter to
NON_SHARING
(NON_SHARING).

Using MML Commands

To deactivate operator-level inter-frequency MLB (either user-number-based or PRB-usage-
based), do as follows:
Run the MOD CELLMLB command with the Inter-Frequency MLB RAN Sharing Mode
parameter set to NON_SHARING(NON_SHARING).

//Deactivating operator-level inter-frequency MLB (either user-number-based or PRB-usage-
based)
MOD CELLMLB: LocalCellId=0, InterFreqMLBRanShareMode=NON_Sharing;

Table 13-10 lists the counters used to monitor operator-level inter-frequency MLB performance.
Table 13-11 lists the counters used to monitor operator-level user-number-based inter-frequency
MLB performance.
If both operator-level PRB-usage-based MLB and operator-level user-number-based MLB are

enabled, the counters listed in Table 13-10 indicate the total statistics of the two algorithms. The
values of counters listed in Table 13-10 minus the values of counters listed in Table 13-11 are
the measurement results of operator-level PRB-usage-based MLB.
If the operator-specific difference in the L.Traffic.User.Ulsync.Avg.PLMN counter value

between frequencies drops, operator-level MLB takes effect.

eRAN
Table 13-10 Performance counters related to operator-level inter-frequency MLB
1526730583 L.HHO.InterFreq.Load.Pr Number of load-based inter-frequency

epAttOut.PLMN handover preparation attempts for a
specific operator
1526730584 L.HHO.InterFreq.Load.Ex Number of load-based inter-frequency

ecAttOut.PLMN handover executions for a specific operator
1526730585 L.HHO.InterFreq.Load.Ex Number of successful load-based inter-

ecSuccOut.PLMN frequency handovers for a specific operator
Table 13-11 Performance counters related to operator-level user-number-based inter-frequency

MLB
1526730589 L.Traffic.User.Ulsync.Avg. Average number of UL-sync UEs for a

PLMN specific operator in a cell
1526730586 L.HHO.InterFreq.UeNum Number of user-number-based inter-

Load.PrepAttOut.PLMN frequency handover preparation attempts
for a specific operator
1526730587 L.HHO.InterFreq.UeNum Number of user-number-based inter-

Load.ExecAttOut.PLMN frequency handover executions for a
specific operator
1526730588 L.HHO.InterFreq.UeNum Number of successful user-number-based

Load.ExecSuccOut.PLMN inter-frequency handovers for a specific
operator
Operator-Level User-Number-based Inter-Frequency MLB

Operator-specific UE Percentage Adjustment
The following table describes the parameter that must be set in a CellOp MO for the adjustment.

eRAN
Operator Ue Number CellOp. User-defined This parameter

Ratio OpUeNumRatio specifies the
percentage of UL-
sync UEs served by
the operator in a cell
when operator-level
inter-frequency
MLB and RAN
sharing are enabled.
For details about optimization of other parameters, see 13.1.11 Parameter Optimization.
Operator-Level PRB-Usage-based Inter-Frequency MLB

Operator-specific PRB Percentage Adjustment
The following table describes the parameters that must be set in a CellOp MO for the adjustment.
Operator uplink RB CellOp. Network plan This parameter

used ratio OpUlRbUsedRatio (negotiation not specifies the
required) percentage of uplink
resources reserved
for each operator that
shares a cell. This
parameter takes
effect only in RAN
sharing with
common carriers
mode.
Operator downlink CellOp. Network plan This parameter

RB used ratio OpDlRbUsedRatio (negotiation not specifies the
required) percentage of
downlink resources
reserved for each
operator that shares
the cell. This
parameter takes
effect only in RAN
sharing with
common carriers
mode.
For details about optimization of other parameters, see 13.2.11 Parameter Optimization.

eRAN
Fault description: After operator-level PRB-usage-based MLB is enabled as described in 13.3.6
Activation, the traced X2 messages indicate that the eNodeB does not perform operator-level
PRB-usage-based MLB.
Fault handling:
Step 1 Check whether the license control items for RAN sharing with common carriers or hybrid RAN
sharing have been purchased.
l If they have been purchased, go to Step 2.
l If they have not been purchased, contact Huawei technical support.
Step 2 Check whether the RAN Sharing Mode Switch parameter is set to ON(On).
l If this switch is off, run the MOD CELLALGOSWITCH command with the RAN Sharing
Mode Switch parameter set to ON(On).
l If this switch is on, contact Huawei technical support.
----End
13.4 LOFD-081227 Intra-LTE Load Balancing for Non-

cosited Cells
This section describes how to configure event-A5-triggered load-based inter-frequency
handovers. For details about how to configure event-A2-triggered load-based inter-frequency
handovers, see Intra-RAT Mobility Management in Connected Mode.
13.4.1 When to Use LOFD-081227 Intra-LTE Load Balancing for

Non-cosited Cell
Use LOFD-081227 Intra-LTE Load Balancing for Non-cosited Cells in a multi-frequency
network where cells are not cosited.

13.4.3 Planning
13.4.4 Requirements
deploying LOFD-081227 Intra-LTE Load Balancing for Non-cosited Cells, the operator must
purchase and activate the licenses for the feature based on the setting of the
l If the CellMLB.MlbTriggerMode parameter is set to PRB_ONLY(PrbMode), the

licenses listed in the following table must be activated.

eRAN
Featur Feature Model License NE Sales Unit

e ID Name Control Item
LOFD- Intra-LTE LT1S00ILLB Intra-LTE eNodeB per RRC

001032 Load 00 Load Connected
Balancing Balancing User
(FDD)
LOFD- Intra-LTE LT1SILBNC Intra-LTE eNodeB per cell

081227 Load C00 Load
Balancing for Balancing for
Non-cosited Non-cosited
Cells Cells (FDD)

(UeNumMode), the licenses listed in the following table must be activated.
Featu Feature Name Model License Control NE Sales Unit

re ID Item
LOFD Intra-LTE User LT1SIL Intra-LTE User eNode per RRC

-0702 Number Load UNLB00 Number Load B Connected
15 Balancing Balancing (FDD) User
LOFD Intra-LTE Load LT1SIL Intra-LTE Load eNode per cell

-0812 Balancing for BNCC00 Balancing for Non- B
27 Non-cosited cosited Cells (FDD)
Cells

Featur Feature Model License Control NE Sales Unit

e ID Name Item
LOFD- Intra-LTE LT1S00IL Intra-LTE Load eNodeB per RRC

001032 Load LB00 Balancing (FDD) Connected
Balancing User
LOFD- Intra-LTE LT1SILU Intra-LTE User eNodeB per RRC

070215 User NLB00 Number Load Connected
Number Balancing (FDD) User
Load
Balancing
LOFD- Intra-LTE LT1SILB Intra-LTE Load eNodeB per cell

081227 Load NCC00 Balancing for
Balancing Non-cosited Cells
for Non- (FDD)
cosited Cells

eRAN

There are three types of data sources:
Required Data
For details, see the following sections:
l Required Data for the LOFD-070215 Intra-LTE User Number Load Balancing feature
l Required Data for the LOFD-001032 Intra-LTE Load Balancing feature
For details about scenario-specific data except the following parameters, see Scenario-specific
Data for the LOFD-070215 Intra-LTE User Number Load Balancing feature and Scenario-
specific Data for the LOFD-001032 Intra-LTE Load Balancing feature.
configure a neighboring E-UTRA frequency.

Name Source
MLB Inter-Freq EutranInterNFreq. Network This parameter specifies the

Handover MlbInterFreqHoEvent- plan frequency-specific event that
Event Type Type (negotiation triggers load-based inter-
not required) frequency handovers. If cells
on a neighboring E-UTRA
frequency and the serving cell
are cosited, the value
EventA4(EventA4) is
recommended; otherwise, the
value EventA5(EventA5) is
recommended.
The following table describes the parameters that must be set in an InterFreqHoGroup MO to

eRAN

Name
MLB Inter- InterFreqHoGroup. Network plan This parameter specifies

Freq Handover MlbInterFreqHoA5Thd1 (negotiation not the serving cell's RSRP
A5 Threshold1 Rsrp required) threshold 1 for event A5
RSRP that triggers load-based
inter-frequency
handovers.
MLB Inter- InterFreqHoGroup. Network plan This parameter specifies

Freq Handover MlbInterFreqHoA5Thd1 (negotiation not the serving cell's RSRQ
A5 Threshold1 Rsrq required) threshold 1 for event A5
RSRQ that triggers load-based
inter-frequency
handovers.
13.4.6 Activation
Before activating LOFD-081227 Intra-LTE Load Balancing for Non-cosited Cells, operators
need to activate user-number-based inter-frequency MLB and "PRB-usage-based inter-
frequency MLB by transferring UL-sync UEs" as described in 13.1.6 Activation and 13.2.6
Activation, respectively.
Enter the values of the parameters listed in Table 13-12 in a summary data file, which also
contains other data for the new eNodeBs to be deployed.
parameters.

eRAN
Table 13-12 Parameters for event-A5-triggered load-based inter-frequency handovers

Summary
Data File
EutranInterNF EutranInterNFr LocalCellId, DlEarfcnMlbIn- This MO must be

req eq terFreqHoEventType customized in a list-
type sheet of the
template.
InterFreqHoGr InterFreqHoGro MlbInterFreqHoA5Thd1Rsrp, This MO must be

oup up MlbInterFreqHoA5Thd1Rsrq customized in a list-
type sheet of the
template.

----End


eRAN
----End
Using MML Commands

Run the MOD EUTRANINTERNFREQ command with the MLB Inter-Freq Handover Event
Type parameter set to EventA5(EventA5) to enable event-A5-triggered load-based inter-
frequency handovers.

MOD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=2600,
MlbInterFreqHoEventType=EventA5;

Ensure that user-number-based or PRB-usage-based inter-frequency MLB has been activated,
the eNodeB has successfully transferred UL-sync UEs, and no other types of handovers are

eRAN
performed. Then, to use signaling tracing to verify whether LOFD-081227 Intra-LTE Load
Balancing for Non-cosited Cells has been activated, perform the following steps:
Management.
Uu Interface Trace under Trace Type > LTE > Application Layer.
Step 3 In the displayed Uu Interface Trace window, create a Uu interface tracing task, and click
Finish to start the task on the local cell.
Step 4 Double-click the new task in the task list on the right of the Signaling Trace Management tab
page. The query result tab page is displayed.
l This feature has been activated is there is an RRC Connection Reconfiguration message that
contains the IE measConfig and meets the following conditions:
The message also contains the IE eventA5.
The values of the IEs CarrierFreq, a5-Threshold1, a5-Threshold2 that are associated with
IE eventA5 are consistent with the parameter values configured on the eNodeB.
l If such a message does not exist, this feature has not been activated.
----End
13.4.8 Deactivation

eNodeBs for feature activation. In the procedure, modify parameters according to Table
13-13.
Table 13-13 Parameters for events that trigger load-based inter-frequency handovers

Summary Data
File
EutranInterNFreq EutranInterNFreq MlbInterFreqHoE- Set this parameter to

ventType EventA4(EventA4).

CME to Perform Single Configuration.

eRAN
Using MML Commands

Run the MOD EUTRANINTERNFREQ command with the MLB Inter-Freq Handover Event
Type parameter set to EventA4(EventA4).

MOD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=2600,
MlbInterFreqHoEventType=EventA4;

For details, see 13.1.10 Performance Monitoring and 13.2.10 Performance Monitoring.

The following table describes the parameter that must be set in an InterFreqHoGroup MO to
MLB Inter-Freq InterFreqHo Network plan This parameter specifies the

Handover A5 Group. (negotiation serving cell's RSRP threshold 1 for
Threshold1 RSRP MlbInterFreq not required) event A5 that triggers load-based
HoA5Thd1Rsr inter-frequency handovers.
p This parameter is valid only if the
EutranInterNFreq.MlbInterFre
qHoEventType parameter is set to
EventA5(EventA5). If event A5 is
used to trigger load-based inter-
frequency handovers, UEs can be
transferred to neighboring cells
with better signal quality for MLB.
This improves spectral efficiency,
as well as relieves load imbalances
among inter-frequency cells.
Adjust this parameter value from
large to small in order to use a
smaller parameter value to achieve
load balances among neighboring
cells.

eRAN
MLB Inter-Freq InterFreqHo Network plan This parameter specifies the

Handover A5 Group. (negotiation serving cell's RSRQ threshold 1 for
Threshold1 RSRQ MlbInterFreq not required) event A5 that triggers load-based
HoA5Thd1Rsr inter-frequency handovers.
Q This parameter is valid only if the
EutranInterNFreq.MlbInterFre
qHoEventType parameter is set to
EventA5(EventA5). If event A5 is
used to trigger load-based inter-
frequency handovers, UEs can be
transferred to neighboring cells
with better signal quality for MLB.
This improves spectral efficiency,
as well as relieves load imbalances
among inter-frequency cells.
Adjust this parameter value from
large to small in order to use a
smaller parameter value to achieve
load balances among neighboring
cells.
For details about optimization of other parameters, see 13.1.11 Parameter Optimization and
13.2.11 Parameter Optimization.
None
13.5 Load Pre-Balancing
13.5.1 When to Use Load Pre-Balancing

Use load pre-balancing in a multi-carrier network where different carriers provide almost the
same coverage areas (that is, the difference in measured RSRP values between carriers at the
same location is less than or equal to 5 dB).

13.5.3 Planning

eRAN
13.5.4 Requirements
Load pre-balancing has no requirement for the operating environment, transmission networking,
or licenses.

Required Data
configure a neighboring E-UTRAN frequency.
Inter frequency cell EutranInterNFreq. Network plan Set this parameter to

resel priority CellReselPriorityCf- (negotiation not CFG(Configure)
configure indicator gInd required) for frequencies
involved in load pre-
balancing.
Inter frequency cell EutranInterNFreq. Network plan Set this parameter

resel priority CellReselPriority (negotiation not based on the network
required) plan.
Scenario 1: Load Pre-Balancing in Fixed Proportions
The following table describes the parameter that must be set in the CellAlgoSwitch MO to enable
load pre-balancing.

eRAN
Load balancing CellAlgoSwitch. User-defined Select the

algorithm switch MlbAlgoSwitch InterFreqI-
dleMlbSwitch
(InterFreqI-
dleMlbSwitch)
option of this
parameter.
The following table describes the parameter that must be set in the CellMLB MO to specify the
load pre-balancing mode.
Inter-Frequency Idle CellMLB. User-defined Select the

Load Balancing InterFreqIdleMlb- Proportion
Mode Mode (Proportion) option
of this parameter.
The following table describes the parameter that must be set in the EutranInterNFreq MOs to
configure the percentages of RRC_REL UEs to be transferred to specific neighboring
frequencies.

eRAN
Idle MLB UE EutranInterNFreq. User-defined Set this parameter

Release Ratio IdleMlbUERelea- based on the
seRatio coverage and
bandwidths of
neighboring
frequencies and the
capabilities of UEs in
the network. For
example, a network
uses two frequencies,
F1 and F2. The
coverage and
bandwidth of both
frequencies are the
same. All UEs in the
network support the
two frequencies.
Then, the
recommended value
for both frequencies
is 50, indicating
50%.
Scenario 2: Load Pre-Balancing in Adaptive Proportions
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to
enable the eNodeB-level load pre-balancing.
Load balancing ENodeBAlgoSwitc User-defined Select the

algorithm switch h.MlbAlgoSwitch INTER_FREQ_ID
LE_MLB_SWITC
H
(INTER_FREQ_ID
LE_MLB_SWITC
H) option.
The following table describes the parameter that must be set in the eNodeBMlb MO to configure
the eNodeB-level load pre-balancing algorithm.

eRAN
Inter Frequency Idle eNodeBMlb.InterFreqI- User-defined Select the

MLB Mode dleMlbMode ADAPTIVE_PROP
ORTION
(ADAPTIVE_PRO-
PORTION) option.
The following table describes the parameter that must be set in the EutranInterNFreq MOs to
configure the percentages of RRC_REL UEs to be transferred to specific neighboring
frequencies.

eRAN

Name Source
Idle MLB EutranInterN User- Set this parameter based on the coverage and
UE Release Freq. defined bandwidths of neighboring frequencies and
Ratio IdleMlbUERel the capabilities of UEs in the network. For
easeRatio example, a network uses two frequencies, F1
and F2. The coverage and bandwidth of both
frequencies are the same. All UEs in the
network support the two frequencies. Then,
the recommended value for both frequencies
is 50, indicating 50%.
For each cell served by an eNodeB, the set of
the cell's operating and neighboring
frequencies must include all frequencies used
in the eNodeB. If this condition is not met, load
pre-balancing in adaptive portions does not
take effect and all UEs are released to their
serving frequency.
For load pre-balancing in adaptive
proportions, you are advised to set this
parameter to the same value for different
sectors.
For example, the cells served by an eNodeB
operate on frequencies F1 and F2. The
expected ratio of UE distribution on F1 and F2
is 1:1.
If cells A and B operate on F1 and cells C and
D operate on F2, then:
l F2 must be configured as a neighboring
frequency of cells A and B with the
seRatio parameter set to 50 for F2.
l F1 must be configured as a neighboring
frequency of cells C and D with the
seRatio parameter set to 50 for F1.
13.5.6 Activation

eRAN
parameters.
Table 13-14 Parameters for load pre-balancing

Summary Data
File
CellAlgoSwitch CellAlgoSwitch MlbAlgoSwitch This MO must be

type sheet of the
template.

InterFreqIdleMlb- customized in a list-
Mode type sheet of the
template.
eNodeBMlb eNodeBMLB InterFreqIdleMlb- This MO must be

Mode, customized in a list-
InterFreqIdleMl- type sheet of the
bInterval, template.
InterFreqIdleMlb-
StaThd
EutranInterNFreq EutranInterNFreq LocalCellId, This MO must be

DlEarfcn, customized in a list-
IdleMlbUERelea- type sheet of the
seRatio, template.
CellReselPriori-
tyCfgInd,
CellReselPriority
ENodeBAlgoSwitc ENodeBAlgoSwitc MlbAlgoSwitch This MO must be

h h customized in a list-
type sheet of the
template.


eRAN
----End


eRAN
----End
Using MML Commands

Step 1 Run the MOD EUTRANINTERNFREQ command with the Idle MLB UE Release Ratio and
Downlink EARFCN parameters specified. If the Cell reselection priority configure
indicator parameter is set to CFG(Configure) for a neighboring E-UTRAN frequency, run the
MOD EUTRANINTERNFREQ command with the Cell reselection priority parameter
specified based on the network plan.
Step 2 Run the MOD CELLALGOSWITCH command with the InterFreqIdleMlbSwitch

(InterFreqIdleMlbSwitch) option of the Load balancing algorithm switch parameter
selected.
Step 3 Run the MOD CELLMLB command with the Proportion(Proportion) option of the Inter-
Frequency Idle Load Balancing Mode parameter selected.
----End

eRAN
Step 1 Run the MOD EUTRANINTERNFREQ command with the Idle MLB UE Release Ratio and
Downlink EARFCN parameters specified. If the Cell reselection priority configure
indicator parameter is set to CFG(Configure) for a neighboring E-UTRAN frequency, run the
MOD EUTRANINTERNFREQ command with the Cell reselection priority parameter
specified based on the network plan.
Step 2 Run the MOD ENODEBALGOSWITCH command with the

INTER_FREQ_IDLE_MLB_SWITCH(INTER_FREQ_IDLE_MLB_SWITCH) option
of the MLB Algorithm Switch parameter selected.
Step 3 Run the MOD ENODEBMLB command with the ADAPTIVE_PROPORTION

(ADAPTIVE_PROPORTION) option of the Inter Frequency Idle MLB Mode parameter
selected and with the Inter Frequency Idle MLB Interval and Inter Frequency Idle MLB
Statistic Threshold parameters set as required.
----End

MOD EutranInterNFreq: LocalCellId=0, DlEarfcn=6000, CellReselPriority=6,
IdleMlbUEReleaseRatio=25;
MOD CELLMLB: LocalCellId=0, InterFreqIdleMlbMode=proportion-1;
MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=InterFreqIdleMlbSwitch-1;

MOD EutranInterNFreq: LocalCellId=0, DlEarfcn=6000, CellReselPriority=6,
IdleMlbUEReleaseRatio=25;
MOD ENODEBALGOSWITCH: MlbAlgoSwitch=INTER_FREQ_IDLE_MLB_SWITCH-1;
MOD ENODEBMLB: InterFreqIdleMlbMode=ADAPTIVE_PROPORTION-1,
InterFreqIdleMlbInterval=1440, InterFreqIdleMlbStaThd=3;

To use SON logs to verify whether load pre-balancing in fixed proportions has been activated,
Step 2 On the Query SON Log tab page, click LTE MLB Log in the Log Category drop down list in
the upper left corner, and click Inter-Frequency Idle Mode Release Statistics under Event
Name. Then click Query to query SON logs. Load pre-balancing in fixed proportions has been
activated if the following information is displayed in the event description:
l Local cell ID
l Number of the target frequencies to which RRC_REL UEs were released
l EARFCNs of the target frequencies to which RRC_REL UEs were released
l Number of RRC_REL UEs released to the specific frequency
----End
To use SON logs to verify whether load pre-balancing in adaptive proportions has been activated,

eRAN
Step 2 On the Query SON Log tab page, click LTE MLB Log in the Log Category drop down list in
the upper left corner, and click Inter-Frequency Idle Mode Adaptive Proportion MLB under
Event Name. Then click Query to query SON logs. Load pre-balancing in adaptive proportions
has been activated if the following information is displayed in the event description:
l Intra-eNodeB downlink frequencies
l Target percentages of UEs served by intra-eNodeB downlink frequencies
l Current percentages of UEs served by intra-eNodeB downlink frequencies
l Source frequency
l Target frequency
l Percentage of UEs released from the source frequency to the target frequency
----End
Performance counters can also be used for activation observation. For details, see Performance
Monitoring.
13.5.8 Deactivation

Table 13-15 Parameters for load pre-balancing

Summary Data
File
CellAlgoSwitch CellAlgoSwitch MlbAlgoSwitch To disable load pre-

balancing in fixed
proportions, deselect
the InterFreqI-
dleMlbSwitch
(InterFreqI-
dleMlbSwitch)
option.

eRAN

Summary Data
File
ENodeBAlgoSwitch ENodeBAlgoSwitch MlbAlgoSwitch To disable load pre-

balancing in adaptive
proportions, deselect
the
INTER_FREQ_ID
LE_MLB_SWITC
H
(INTER_FREQ_ID
LE_MLB_SWITC
H) option.

Using MML Commands

Run the MOD CELLALGOSWITCH command with the InterFreqIdleMlbSwitch

(InterFreqIdleMlbSwitch) option of the Load balancing algorithm switch parameter
deselected.
Run the MOD ENODEBALGOSWITCH command with the

INTER_FREQ_IDLE_MLB_SWITCH(INTER_FREQ_IDLE_MLB_SWITCH) option
of the MLB Algorithm Switch parameter deselected.

MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch= InterFreqIdleMlbSwitch-0;

MOD ENODEBALGOSWITCH: MlbAlgoSwitch=INTER_FREQ_IDLE_MLB_SWITCH -0;
None

Table 13-16 lists the counter used to monitor the performance of load pre-balancing.

eRAN
Table 13-16 Performance counter related to load pre-balancing
1526728333 L.Traffic.User.Ulsync.Avg Average number of UL-sync UEs in a cell

Load Pre-Balancing in Adaptive Proportions
The following table describes the parameters in the eNodeBMlb MO for load pre-balancing in
adaptive proportions.
Inter Frequency Idle eNodeBMlb. User-defined If this parameter is set

MLB Interval InterFreqIdleMlbInterv- to a small value, load
al pre-balancing in
adaptive proportions
can adjust the load
pre-balancing policy
promptly based on
network load. If this
parameter is set to a
large value, load pre-
proportions works
based on a stable
traffic model.
Inter Frequency Idle eNodeBMlb.InterFreqI- User-defined If this parameter is set

MLB Statistic dleMlbStaThd to a small value, load
Threshold pre-balancing in
adaptive proportions
can be easily
triggered. If this
parameter is set to a
large value, load pre-
proportions works
based on more
reliable measurement
results.
None

eRAN
13.6 LOFD-001057 Load Balancing based on Transport QoS
13.6.1 When to Use LOFD-001057 Load Balancing based on

Transport QoS
Use this feature when the transport bandwidth is limited. This type of MLB can be deployed
only when inter-frequency MLB has been activated.

Collect the following information:
l Information about each neighboring cell of the cells served by the local eNodeB
Whether information about the neighboring cell is complete
Whether the neighboring cell has been blacklisted
Whether the No handover indicator parameter is set to PERMIT_HO_ENUM
(Permit Ho)
l Status of the X2 interfaces with neighboring eNodeBs
l UE capabilities
Proportion of UEs that support inter-frequency measurements and handovers and
proportion of the other UEs
l Operator-planned transport bandwidth
The bandwidth for transmission between an eNodeB and the EPC affects not only the uplink
or downlink transmission capacity of the eNodeB, but also the load measurements and
evaluations for transport-QoS-based inter-frequency MLB.
13.6.3 Planning
13.6.4 Requirements
deploying LOFD-001057 Load Balancing based on Transport QoS, the operator must purchase
and activate the licenses for the feature listed in the following table.
Feature Feature Model License NE Sales Unit

ID Name Control Item
LOFD-001 Intra-LTE LT1S00ILLB Intra-LTE Load eNo per RRC

032 Load 00 Balancing deB Connected User
Balancing (FDD)

eRAN
Feature Feature Model License NE Sales Unit

ID Name Control Item
LOFD-001 Load LT1S00LBT Load Balancing eNo per cell

057 Balancing Q00 based on deB
based on Transport QoS
Transport QoS (FDD)

Required Data
The preparation of the required data is the same as that for PRB-usage-based inter-frequency
MLB. For details, see Required Data.
The following table describes the parameters that must be set in the TLDRALG MO to configure
TNL load thresholds. This MO can be modified but cannot be added or removed.
Uplink High Load TLDRALG. Network plan Set these

Trigger Threshold TRMULLDRTRGTH (negotiation not parameters based
required) on the network
Downlink High Load TLDRALG. plan. The default
Trigger Threshold TRMDLLDRTRGTH values are
Uplink High Load Clear TLDRALG. recommended.
Threshold TRMULLDRCLRTH
Downlink High Load TLDRALG.

Clear Threshold TRMDLLDRCLRTH
Uplink Medium Load TLDRALG.

Trigger Threshold TRMULMLDTRGTH
Downlink Medium Load TLDRALG.

Trigger Threshold TRMDLMLDTRGTH

eRAN

Clear Threshold TRMULMLDCLRTH

Clear Threshold TRMDLMLDCLRTH
The preparation of other scenario-specific data is the same as that for PRB-usage-based inter-
frequency MLB. For details, see Scenario-specific Data.
13.6.6 Activation
parameters.
Table 13-17 Parameters for transport-QoS-based inter-frequency MLB

Summary
Data File
CellAlgoS CellAlgoSwitc MlbAlgoSwitch These MOs must be customized

witch h in a list-type sheet of the
template.
CellMLB CellMLB LocalCellId,
LoadOffset,
InterRatMlbThd,
InterRatMlbUe-
NumThd
ENodeBAl ENodeBAlgoS HoModeSwitch

goSwitch witch

eRAN

Summary
Data File
SpidCfg SpidCfg Spid,

(Optional) InterFreqMlbS-
witch,
InterRatMlbSwitch
TLDRAL TLDRALG TRMULLDRTRGT

G H,
TRMDLLDRTRGT
H,
TRMULLDRCLRT
H,
TRMDLLDRCLRT
H,
TRMULMLDTRG
TH,
TRMDLMLDTRG
TH,
TRMULMLDCLRT
H,
TRMDLMLDCLRT
H


eRAN
----End

----End
Using MML Commands

Step 1 Run the MOD CELLALGOSWITCH command to enable inter-frequency MLB.

eRAN
Step 3 Run the SET TLDRALG command to set the TNL load thresholds.
----End

SET TLDRALG: TRMULLDRTRGTH=70, TRMDLLDRTRGTH=70, TRMULLDRCLRTH=65,
TRMDLLDRCLRTH=65, TRMULMLDTRGTH=50, TRMDLMLDTRGTH=50, TRMULMLDCLRTH=45,
TRMDLMLDCLRTH=45;

Step 1 Add a 10 Mbit/s transport resource group and IP paths. In actual applications, change the IP
addresses presented in the following examples as required.
l Run the ADD RSCGRP command to add a transport resource group. A command example
is as follows:
ADD RSCGRP: PT=ETH, PN=1, TXBW=10000, RXBW=10000, TXCBS=10000, TXEBS=10000,
TXCIR=10000, RXCIR=10000, TXPIR=10000, RXPIR=10000, TXPBS=10000;
l Run the ADD IPPATH command to add IP paths. A command example is as follows:
ADD IPPATH: PATHID=0, PT=ETH, PN=1, JNRSCGRP=ENABLE, LOCALIP=" 172.31.102.68",
PEERIP="172.21.128.1", ANI=0, APPTYPE=S1, PATHTYPE=ANY;
ADD IPPATH: PATHID=2, PT=ETH, PN=1, JNRSCGRP=ENABLE, LOCALIP="13.13.11.80",
PEERIP="13.13.11.90", ANI=0, APPTYPE=X2, PATHTYPE=ANY;
Step 2 Use UE1 and UE2 to establish an 8 Mbit/s dedicated bearer with a QCI of 2 and a 2 Mbit/s
dedicated bearer with a QCI of 2, respectively. Then, use UE1 and UE2 to access the network
at the center and edge of an E-UTRAN cell, respectively.
Step 3 On the U2000 client, start Uu interface tracing.
Step 4 On the U2000 client, start X2 interface tracing. MLB takes effect if the following messages are
traced: (1) RESOURCE STATUS REQUEST message from the serving cell to the inter-
frequency neighboring cell; (2) RESOURCE STATUS RESPONSE message from the
neighboring cell to the serving cell; (3) periodic RESOURCE STATUS UPDATE messages
from the neighboring cell to the serving cell.
Step 5 Inject downlink packets for UE1 and UE2 at a rate of 8 Mbit/s and 2 Mbit/s, respectively. The
TNL load is now in the HighLoad state.
Step 6 Check for the RRC_CONN_RECFG message traced over the Uu interface. For details about
how to trace the RRC_CONN_RECFG message over the Uu interface, see the signaling
procedure for a successful handover in Intra-RAT Mobility Management in Connected Mode
Feature Parameter Description. If the RRC_CONN_RECFG message is traced over the Uu
interface, transport-QoS-based inter-frequency MLB takes effect.
----End

eRAN
13.6.8 Deactivation

Table 13-18 Parameters for transport-QoS-based inter-frequency MLB
MO Sheet in the Parameter Setting Notes

Summary Data Group
File
CellAlgoSw CellAlgoSwitch MlbAlgoSwitch Disable inter-frequency MLB:

itch Deselect the InterFreqMlbSwitch
(InterFreqMlbSwitch) option.

Using MML Commands

(InterFreqMlbSwitch) option of the Load balancing algorithm switch parameter deselected.


For details, see 13.2.10 Performance Monitoring.

TNL Load Thresholds
The following table describes the parameters that must be set in the TLDRALG MO to configure
TNL load thresholds. This MO can be modified but cannot be added or removed.
Uplink High Load Trigger TLDRALG. Network plan Set these parameters
Threshold TRMULLDRTRGT (negotiation based on the
H not required) network plan.

eRAN
Downlink High Load TLDRALG. Default values are

Trigger Threshold TRMDLLDRTRGT recommended.
H
Uplink High Load Clear TLDRALG.

Threshold TRMULLDRCLRT
H
Downlink High Load Clear TLDRALG.

Threshold TRMDLLDRCLRT
H

Trigger Threshold TRMULMLDTRGT
H

Trigger Threshold TRMDLMLDTRGT
H
Uplink Medium Load Clear TLDRALG.

Threshold TRMULMLDCLRT
H

Clear Threshold TRMDLMLDCLRT
H
None

eRAN
Description 14 Parameters
14 Parameters
Table 14-1 Parameter description
MO Parame MML Feature Feature Description

ter ID Comma ID Name
nd
CellML CellCap MOD LOFD-0 Intra- Meaning: Indicates the scale factor used to determine
B acitySca CELLM 70215 / LTE the load balancing capability of a cell. This factor helps
leFactor LB TDLOF User adjust the load balancing target in UE-number-based
LST D-07021 Number load balancing. The load balancing capability of a cell
CELLM 5 Load equals the value calculated by the cell bandwidth
LB LOFD-0 Balancin (number of RBs) multiplied by the CellCapacityScale-
70204 g Factor parameter value. Load balancing with this
Operator parameter taken effect aims to achieve even loads in
Load each cell with the same bandwidth.
Based GUI Value Range: 1~100
Intra- Unit: None
LTE
MLB Actual Value Range: 0.1~10, step:0.1
Default Value: 10
CellMlb MlbHoI MOD TDLOF Intra- Meaning: Indicates the protection mode for UEs that are
Ho nProtect CELLM D-00103 LTE transferred to a cell for MLB.
Mode LBHO 2 Load GUI Value Range: PROTECTTIMERMODE
LST TDLOF Balancin (PROTECTTIMER MODE),
CELLM D-07021 g SPECEVENTA1A2MODE(SPECEVENTA1A2
LBHO 5 Intra- MODE)
LTE Unit: None
User
Number Actual Value Range: PROTECTTIMERMODE,
Load SPECEVENTA1A2MODE
Balancin Default Value: PROTECTTIMERMODE:Off,
g SPECEVENTA1A2MODE:Off

eRAN

nd
CellMlb MlbHoI MOD TDLOF Intra- Meaning: Indicates the length of duration in which UEs
Ho nProtect CELLM D-00103 LTE that are transferred to a cell for MLB are not allowed to
Timer LBHO 2 Load be transferred for MLB again. If this parameter is set to
LST TDLOF Balancin 0, this protection timer is not used. This parameter takes
CELLM D-07021 g effect only for UEs that will be transferred to this cell
LBHO 5 Intra- for MLB after the parameter is set.
LTE GUI Value Range: 0~3600
User Unit: s
Number
Load Actual Value Range: 0~3600
Balancin Default Value: 0
g
CellML InterFrq MOD LOFD-0 Intra- Meaning: Indicates the UL-synchronized UE number
B UeNum CELLM 70215 / LTE threshold used for transferring loads to neighboring
Offload LB TDLOF User cells with which the source cell does not exchange load
Offset LST D-07021 Number information during inter-frequency load balancing.
CELLM 5 Load Consider that the MlbTriggerMode parameter is set to
LB LOFD-0 Balancin UE_NUMBER_ONLY(UeNumMode) or
70204 g PRB_OR_UE_NUMBER(PrbOrUeNumMode). If the
Operator number of UL-synchronized UEs in the source cell is
Load greater than or equal to the sum of the InterFreqMlbUe-
Based NumThd parameter value and the InterFrqUeNumOf-
Intra- floadOffset parameter value, neighboring cells with
LTE which the source cell does not exchange load
MLB information can be selected as the target cells for load
balancing, and the source cell cannot be selected as a
target cell for load balancing. If the number of UL-
synchronized UEs in the source cell is less than the value
calculated by the InterFreqMlbUeNumThd parameter
value plus the InterFrqUeNumOffloadOffset parameter
value and then minus the LoadOffset parameter value,
the source cell can be selected as a target cell for load
balancing.
GUI Value Range: 0~10000
Unit: None
Actual Value Range: 0~10000
Default Value: 0

eRAN

nd
CellML InterFre MOD LOFD-0 Intra- Meaning: Indicates the PRB usage threshold used for
B qOffloa CELLM 01032 / LTE transferring loads to neighboring cells with which the
dOffset LB TDLOF Load source cell does not exchange load information during
LST D-00103 Balancin inter-frequency load balancing. Consider that the
CELLM 2 g MlbTriggerMode parameter is set to PRB_ONLY
LB LOFD-0 Operator (PrbMode) or PRB_OR_UE_NUMBER
70204 Load (PrbOrUeNumMode). If the PRB usage in the source
Based cell is greater than or equal to the sum of the
Intra- InterFreqMlbThd parameter value and the
LTE InterFreqOffloadOffset parameter value, neighboring
MLB cells with which the source cell does not exchange load
information can be selected as the target cells for load
balancing, and the source cell cannot be selected as a
target cell for load balancing. If the PRB usage in the
source cell is less than the value calculated by the
InterFreqMlbThd parameter value plus the
InterFreqOffloadOffset parameter value and then minus
the LoadOffset parameter value, the source cell can be
selected as a target cell for load balancing.
Unit: %
Default Value: 0
EutranIn MlbInter ADD LOFD-0 Intra- Meaning: Indicates the event type used to trigger MLB-
terNFre FreqHo EUTRA 01032 / LTE based inter-frequency handovers. MLB-based inter-
q EventTy NINTE TDLOF Load frequency handovers can be triggered based on event
pe RNFRE D-00103 Balancin A4 or event A5. If an inter-frequency neighboring cell
Q 2 g and the serving cell are served by the same eNodeB, you
MOD LOFD-0 Intra- are advised to set this parameter to EventA4(EventA4);
EUTRA 70215 / LTE otherwise, you are advised to set this parameter to
NINTE TDLOF User EventA5(EventA5).
RNFRE D-07021 Number GUI Value Range: EventA4(EventA4), EventA5
Q 5 Load (EventA5)
LST LOFD-0 Balancin Unit: None
EUTRA 70204 g
Actual Value Range: EventA4, EventA5
NINTE Operator
RNFRE Load Default Value: EventA4(EventA4)
Q Based
Intra-
LTE
MLB

eRAN

nd
InterFre MlbInter ADD LOFD-0 Intra- Meaning: Indicates the RSRP threshold 1 of the serving
qHoGro FreqHo INTERF 01032 / LTE cell for event A5 related to inter-frequency
up A5Thd1 REQHO TDLOF Load measurements for MLB. If the measured RSRP of the
Rsrp GROUP D-00103 Balancin serving cell is lower than the
MOD 2 g MlbInterFreqHoA5Thd1Rsr parameter value and the
INTERF LOFD-0 Intra- measured RSRP of a neighboring cell is higher than the
REQHO 70215 / LTE InterFreqLoadBasedHoA4ThdRsrp parameter value,
GROUP TDLOF User the UE reports event A5.
LST D-07021 Number GUI Value Range: -140~-43

INTERF 5 Load Unit: dBm
REQHO LOFD-0 Balancin
g Actual Value Range: -140~-43
GROUP 70204
Operator Default Value: -43
Load
Based
Intra-
LTE
MLB
InterFre MlbInter ADD LOFD-0 Intra- Meaning: Indicates the RSRQ threshold 1 of the serving
qHoGro FreqHo INTERF 01032 / LTE cell for event A5 related to inter-frequency
up A5Thd1 REQHO TDLOF Load measurements for MLB. If the measured RSRQ of the
Rsrq GROUP D-00103 Balancin serving cell is lower than the
MOD 2 g MlbInterFreqHoA5Thd1Rsr parameter value and the
INTERF LOFD-0 Intra- measured RSRQ of a neighboring cell is higher than the
REQHO 70215 / LTE InterFreqLoadBasedHoA4ThdRsrq parameter value,
GROUP TDLOF User the UE reports event A5.
LST D-07021 Number GUI Value Range: -40~-6

INTERF 5 Load Unit: 0.5dB
REQHO LOFD-0 Balancin
g Actual Value Range: -20~-3
GROUP 70204
Operator Default Value: -24
Load
Based
Intra-
LTE
MLB

eRAN

nd
CellAlg FreqPrio MOD None None Meaning: Indicates whether to enable frequency-
oSwitch rityHoS CELLA priority-based inter-frequency handover algorithms.
witch LGOSW This parameter includes the following options:
ITCH FreqPriorIFHOSwitch: Frequency-priority-based inter-
LST frequency handover is applicable when the two E-
CELLA UTRAN frequencies provide the same coverage and
LGOSW one frequency is preferred for carrying services. If this
ITCH option is on, the frequency-priority-based inter-
frequency handover will be triggered even when the
serving cell provides a good signal quality. If this option
is off, the frequency-priority-based inter-frequency
handover is disabled. The inter-frequency handover can
be triggered only when other conditions are met.
FreqPriorIFBlindHOSwitch: If this option is on,
frequency-priority-based inter-frequency handovers are
performed in a blind manner. If this option is off,
frequency-priority-based inter-frequency handovers are
performed based on measurements. This option takes
effect only when the FreqPriorIFHOSwitch option is on.
MlbBasedFreqPriHoSwitch: Indicates whether to
enable frequency-priority-based inter-frequency
handovers when load balancing is triggered. If this
option is on, the eNodeB stops performing frequency-
priority-based inter-frequency handovers on UEs that
newly access the cell with load balancing enabled. If this
option is off, the eNodeB continues to perform
frequency-priority-based inter-frequency handovers on
UEs that newly access the cell with load balancing
enabled. This option takes effect only when the
FreqPriorIFHOSwitch option is on. A2BasedFreqPri-
HoSwitch: Indicates whether measurements for
frequency-priority-based handovers are triggered based
on event A2. If this option is on, new UEs (including
UEs newly access the cell, UEs handed over to the cell,
and UEs reestablish RRC connections in the cell) that
meet conditions of triggering event A2 perform
measurements on high-priority frequencies. If this
option is off, new UEs that meet conditions of triggering
event A1 perform measurements on high-priority
frequencies or perform blind handovers.This option
takes effect only when the FreqPriorIFHOSwitch option
is on.
GUI Value Range: FreqPriorIFHOSwitch
(FreqPriorIFHOSwitch), FreqPriorIFBlindHOSwitch
(FreqPriorIFBlindHOSwitch), MlbBasedFreqPriHoS-

eRAN

nd
witch(MlbBasedFreqPriHoSwitch), A2BasedFreqPri-
HoSwitch(A2BasedFreqPriHoSwitch)
Unit: None
Actual Value Range: FreqPriorIFHOSwitch,
FreqPriorIFBlindHOSwitch, MlbBasedFreqPriHoS-
witch, A2BasedFreqPriHoSwitch
Default Value: FreqPriorIFHOSwitch:Off,
FreqPriorIFBlindHOSwitch:On,
MlbBasedFreqPriHoSwitch:Off,
A2BasedFreqPriHoSwitch:Off
CellML PunishJ MOD LOFD-0 Intra- Meaning: Indicates the number of load balancing
B udgePrd CELLM 01032 / LTE periods used to determine whether to punish a frequency
Num LB TDLOF Load during load balancing.
LST D-00103 Balancin GUI Value Range: 1~127
CELLM 2 g
Unit: None
LB LOFD-0 Intra-
70215 / LTE Actual Value Range: 1~127
TDLOF User Default Value: 1
D-07021 Number
5 Load
LOFD-0 Balancin
01044 / g
TDLOF Inter-
D-00104 RAT
4 Load
Sharing
to
UTRAN

eRAN

nd
CellML FreqPun MOD LOFD-0 Intra- Meaning: Indicates the number of MLB punishment
B ishPrdN CELLM 01032 / LTE periods for a frequency during which cells operating on
um LB TDLOF Load this frequency cannot be selected as target cells in load
LST D-00103 Balancin balancing.
CELLM 2 g GUI Value Range: 0~127
LB LOFD-0 Intra- Unit: None
70215 / LTE
TDLOF User Actual Value Range: 0~127
D-07021 Number Default Value: 4
5 Load
LOFD-0 Balancin
01044 / g
TDLOF Inter-
D-00104 RAT
4 Load
Sharing
to
UTRAN
CellML MlbUeS MOD LOFD-0 Intra- Meaning: Indicates the length of the timer for punishing
B electPun CELLM 01032 / LTE UEs that are selected for MLB but fail to be transferred
ishTime LB TDLOF Load to target cells. Before the timer expires, the UEs cannot
r LST D-00103 Balancin be transferred for MLB.
LB Unit: s
Default Value: 120

eRAN

nd
CellML CellPuni MOD LOFD-0 Intra- Meaning: Indicates the number of MLB punishment
B shPrdNu CELLM 01032 / LTE periods for a cell during which the cell cannot be
m LB TDLOF Load selected as the target cell in load balancing.
LST D-00103 Balancin GUI Value Range: 0~127
CELLM 2 g
Unit: None
LB LOFD-0 Intra-
70215 / LTE Actual Value Range: 0~127
TDLOF User Default Value: 4
D-07021 Number
5 Load
LOFD-0 Balancin
01044 / g
TDLOF Inter-
D-00104 RAT
4 Load
Sharing
to
UTRAN
EutranIn OverlapI ADD LBFD-0 Coverag Meaning: Indicates whether the inter-frequency
terFreq nd EUTRA 0201802 e Based neighboring cell is manually identified as a neighboring
NCell NINTE / Inter- cell overlapping the local E-UTRAN cell. The default
RFREQ TDLBF frequenc value is NO. The parameter value YES indicates that the
NCELL D-00201 y inter-frequency neighboring cell is manually identified
MOD 802 Handov as a neighboring cell overlapping the local E-UTRAN
EUTRA LOFD-0 er cell. The parameter value NO indicates that the inter-
NINTE 02001 / Automat frequency neighboring cell is not manually identified as
RFREQ TDLOF ic a neighboring cell overlapping the local E-UTRAN cell.
NCELL D-00200 Neighbo GUI Value Range: NO(NO), YES(YES)
LST 1 ur Unit: None
EUTRA Relation
(ANR) Actual Value Range: NO, YES
NINTE
RFREQ Default Value: NO(NO)
NCELL

eRAN

nd
RrcCon UeInacti MOD LBFD-0 RRC Meaning: Indicates the length of the UE inactivity timer
nStateTi veTimer RRCCO 02007 / Connect for UEs that are running non-QCI1 services. If the
mer NNSTA TDLBF ion eNodeB detects that a UE has neither received nor sent
TETIM D-00200 Manage data for a duration exceeding the value of this parameter,
ER 7 ment the eNodeB releases the RRC connection for the UE. If
LST this parameter is set to 0, the UE inactivity timer is not
RRCCO used. If the parameter setting is changed, the change
NNSTA applies to UEs that newly access the network.
TETIM GUI Value Range: 0~3600
ER Unit: s
Default Value: 20

eRAN

nd
CellAlg MlbAlg MOD LOFD-0 Intra- Meaning: Indicates whether to enable mobility load
oSwitch oSwitch CELLA 01032 / LTE balancing (MLB) algorithms. Switches included in this
LGOSW TDLOF Load parameter control the following algorithms: intra-
ITCH D-00103 Balancin frequency MLB, intra-frequency MLB for UEs in idle
LST 2 g mode, inter-frequency MLB, inter-frequency MLB for
CELLA LOFD-0 UEs in idle mode, blind inter-frequency MLB, MLB to
Inter- UTRAN, MLB to UTRAN for UEs in idle mode, MLB
LGOSW 01044 / RAT
ITCH TDLOF to GERAN, MLB to CDMA2000, MLB based on PRB
Load evaluation, and MLB based on neighboring cell load
D-00104 Sharing
4 status. If one switch is on, the corresponding algorithm
to is enabled to balance the loads between the serving cell
LOFD-0 UTRAN and neighboring cells of the specified category.
01045 / Inter- IntraFreqMlbSwitch: Indicates whether to enable intra-
TDLOF RAT frequency load balancing. If this switch is on, intra-
D-00104 Load frequency load balancing is enabled and IntraFreqI-
5 Sharing dleMlbSwitch takes effect. If this switch is off, intra-
LOFD-0 to frequency load balancing is disabled and IntraFreqI-
01057 GERAN dleMlbSwitch does not take effect. InterFreqMlbS-
witch: Indicates whether to enable inter-frequency load
balancing. UtranMlbSwitch: Indicates whether to
enable load sharing with UTRAN cells.
GeranMlbSwitch: Indicates whether to enable load
sharing with GERAN cells. CdmaMlbSwitch: Indicates
whether to enable load sharing with CDMA2000 cells.
IntraFreqIdleMlbSwitch: If both IntraFreqIdleMlbS-
witch and IntraFreqMlbSwitch are on, intra-frequency
load balancing for UEs in idle mode is enabled.
Otherwise, intra-frequency load balancing for UEs in
idle mode is disabled. UtranIdleMlbSwitch: Indicates
whether to enable load sharing with UTRAN for UEs in
idle mode. MlbLoadInfoSwitch: Indicates whether load
of an inter-RAT cell is considered when the load sharing
between the E-UTRAN cell and the inter-RAT cell is
performed. This inter-RAT cell must be a UTRAN cell
in this version. If both MlbLoadInfoSwitch and
UtranMlbSwitch are on, the UTRAN cell whose load
status is obtained and is normal or medium can be
selected as the candidate cell for load sharing with
UTRAN. If both MlbLoadInfoSwitch and
UtranIdleMlbSwitch are on, the UTRAN cell whose
load status is obtained and is normal can be selected as
the candidate cell for load sharing with UTRAN.
InterFreqBlindMlbSwitch: Indicates whether to enable
the inter-frequency blind load balancing.
PrbValMlbSwitch: Indicates whether to enable PRB-
evaluation-based load balancing among devices of
different vendors. PRB-evaluation-based load

eRAN

nd
balancing among devices of different vendors is enabled

only when this switch is on. This parameter is valid only
for LTE TDD cells. This switch will be removed in later
versions. InterFreqIdleMlbSwitch: Indicates whether to
enable inter-frequency load balancing for UEs in idle
mode. After InterFreqIdleMlbSwitch is on, the load
balancing for UEs in idle mode is valid only when at
least one inter-frequency load balancing mode for UEs
in idle mode is selected.
GUI Value Range: IntraFreqMlbSwitch
(IntraFreqMlbSwitch), InterFreqMlbSwitch
(InterFreqMlbSwitch), UtranMlbSwitch
(UtranMlbSwitch), GeranMlbSwitch
(GeranMlbSwitch), CdmaMlbSwitch
(CdmaMlbSwitch), IntraFreqIdleMlbSwitch
(IntraFreqIdleMlbSwitch), UtranIdleMlbSwitch
(UtranIdleMlbSwitch), MlbLoadInfoSwitch
(MlbLoadInfoSwitch), InterFreqBlindMlbSwitch
(InterFreqBlindMlbSwitch), PrbValMlbSwitch
(PrbValMlbSwitch), InterFreqIdleMlbSwitch
(InterFreqIdleMlbSwitch)
Unit: None
Actual Value Range: IntraFreqMlbSwitch,
InterFreqMlbSwitch, UtranMlbSwitch,
GeranMlbSwitch, CdmaMlbSwitch, IntraFreqI-
dleMlbSwitch, UtranIdleMlbSwitch, MlbLoadInfoS-
witch, InterFreqBlindMlbSwitch, PrbValMlbSwitch,
InterFreqIdleMlbSwitch
Default Value: IntraFreqMlbSwitch:Off,
InterFreqMlbSwitch:Off, UtranMlbSwitch:Off,
GeranMlbSwitch:Off, CdmaMlbSwitch:Off,
IntraFreqIdleMlbSwitch:Off,
UtranIdleMlbSwitch:Off, MlbLoadInfoSwitch:Off,
InterFreqBlindMlbSwitch:Off, PrbValMlbSwitch:Off,
InterFreqIdleMlbSwitch:Off

eRAN

nd
CellML InterFre MOD LOFD-0 Intra- Meaning: Indicates the evaluation period for
B qLoadE CELLM 70215 / LTE determining whether to trigger inter-frequency load
valPrd LB TDLOF User balancing. If the serving cell remains in the heavy load
LST D-07021 Number state within an evaluation period, inter-frequency load
CELLM 5 Load balancing is triggered and certain UEs are transferred
LB Balancin for load balancing. If the UtranMlbSwitch or
g GeranMlbSwitch option of the MlbAlgoSwitch
parameter is selected, the InterFreqMlbSwitch or
InterFreqBlindMlbSwitch option of the
MlbAlgoSwitch parameter is selected, and the
FreqSelectStrategy parameter is set to
PRIORITYBASED(PriorityBased), the values of the
InterRatLoadEvalPrd and InterFreqLoadEvalPrd
parameters must be the same. If the two parameters are
set to different values, the evaluation period specified
by the InterRatLoadEvalPrd parameter is adapted when
both cell-level inter-frequency load balancing and inter-
RAT load sharing are triggered at the same time.
Unit: s
Default Value: 30

eRAN

nd
CellML MlbTrig MOD LOFD-0 Intra- Meaning: Indicates the variable that triggers a mobility
B gerMod CELLM 70215 / LTE load balancing (MLB) procedure. In MLB with load
e LB TDLOF User information exchange, If this parameter is set to
LST D-07021 Number PRB_ONLY(PrbMode), PRB usage is used as a
CELLM 5 Load triggering variable and the number of UEs is used as a
LB Balancin supplementary triggering variable; PRB usage
g difference between cells is used as a UE transfer
condition; the aim of MLB is to achieve the same
number of remaining PRBs between cells. If this
parameter is set to UE_NUMBER_ONLY
(UeNumMode), the number of UEs is used as a
triggering variable; the difference of the number of UEs
per unit of bandwidth between cells is used as a UE
transfer condition; the aim of MLB is to achieve the
same number of UEs per unit of bandwidth between
cells. If this parameter is set to
PRB_OR_UE_NUMBER(PrbOrUeNumMode), the
combination of the triggering variables, UE transfer
conditions, and MLB aims for the values
UE_NUMBER_ONLY(UeNumMode) and
PRB_ONLY(PrbMode) are used. In MLB without load
information exchange, If this parameter is set to
PRB_ONLY(PrbMode), PRB usage is used as a
triggering variable and a UE transfer condition and the
number of UEs is used as a supplementary triggering
variable and a supplementary UE transfer condition; the
aim of MLB is to achieve that the PRB usage is less than
the InterFreqMlbThd parameter value. If this parameter
is set to UE_NUMBER_ONLY(UeNumMode), the
number of UEs is used as a triggering variable and a UE
transfer condition; the aim of MLB is to achieve that the
number of UEs is less than the InterFreqMlbUe-
NumThd parameter value. If this parameter is set to
PRB_OR_UE_NUMBER(PrbOrUeNumMode), the
combination of the triggering variables, UE transfer
conditions, and MLB aims for the values
UE_NUMBER_ONLY(UeNumMode) and
PRB_ONLY(PrbMode) are used.
GUI Value Range: PRB_ONLY(PrbMode),
UE_NUMBER_ONLY(UeNumMode),
PRB_OR_UE_NUMBER(PrbOrUeNumMode)
Unit: None
Actual Value Range: PRB_ONLY,
UE_NUMBER_ONLY, PRB_OR_UE_NUMBER
Default Value: PRB_ONLY(PrbMode)

eRAN

nd
CellML InterFre MOD LOFD-0 Intra- Meaning: Indicates the type of UEs that are transferred
B qUeTrsf CELLM 70215 / LTE for inter-frequency load balancing (excluding blind load
Type LB TDLOF User balancing).If the SynchronizedUE check box is
LST D-07021 Number selected,synchronized UEs are transferred for inter-
CELLM 5 Load frequency user-number-based load balancing.If the
LB Balancin IdleUE check box is selected, UEs in idle mode are
g transferred for inter-frequency user-number-based load
balancing.If the PrbMlbSynchronizedUE check box is
selected, synchronized UEs are transferred for inter-
frequency PRB-based load balancing.This parameter is
dedicated to LTE TDD cells.If the PrbMlbIdleUE check
box is selected, UEs in idle mode are transferred for
inter-frequency PRB-based load balancing.This
parameter is dedicated to LTE TDD cells.If multiple
check boxes are selected, multiple uplink synchronized
UEs and UEs in idle mode are transferred for load
balancing.If no check box is selected, no UE is
transferred for load balancing.
GUI Value Range: SynchronizedUE
(SynchronizedUE), IdleUE(IdleUE),
PrbMlbSynchronizedUE(PrbMlbSynchronizedUE),
PrbMlbIdleUE(PrbMlbIdleUE)
Unit: None
Actual Value Range: SynchronizedUE, IdleUE,
PrbMlbSynchronizedUE, PrbMlbIdleUE
Default Value: SynchronizedUE:On, IdleUE:Off,
PrbMlbSynchronizedUE:On, PrbMlbIdleUE:Off

eRAN

nd
CellML InterFre MOD LOFD-0 Intra- Meaning: Indicates the threshold of the number of
B qIdleMl CELLM 70215 / LTE synchronized UEs for triggering inter-frequency load
bUeNu LB TDLOF User balancing to transfer to-be-released UEs. When the
mThd LST D-07021 Number MlbTriggerMode parameter is set to
CELLM 5 Load UE_NUMBER_ONLY(UeNumMode) or
LB Balancin PRB_OR_UE_NUMBER(PrbOrUeNumMode), inter-
g frequency load balancing to transfer to-be-released UEs
is triggered if the number of synchronized UEs in the
cell is greater than or equal to the sum of the
InterFreqIdleMlbUeNumThd and MlbUeNumOffset
parameter values. Inter-frequency load balancing to
transfer to-be-released UEs stops if the number of
synchronized UEs in the cell is less than the
InterFreqIdleMlbUeNumThd parameter value.
Unit: None
Default Value: 100
CellML MlbUeN MOD LOFD-0 Intra- Meaning: Indicates the offset of the number of
B umOffse CELLM 70215 / LTE synchronized UEs for triggering inter-frequency load
t LB TDLOF User balancing. User-number-based inter-frequency load
LST D-07021 Number balancing is triggered if the number of synchronized
CELLM 5 Load UEs in the cell is greater than or equal to the sum of the
LB Balancin InterFreqMlbUeNumThd and MlbUeNumOffset
g parameter values. User-number-based inter-frequency
load balancing to transfer to-be-released UEs is
triggered if the number of synchronized UEs in the cell
is greater than or equal to the sum of the
InterFreqIdleMlbUeNumThd and MlbUeNumOffset
parameter values.
Unit: None
Default Value: 20

eRAN

nd
EutranIn NoHoFl ADD LBFD-0 Coverag Meaning: Indicates whether handovers of UEs to the
terFreq ag EUTRA 0201802 e Based neighboring cell are prohibited.
NCell NINTE / Inter- GUI Value Range: PERMIT_HO_ENUM(Permit Ho),
RFREQ TDLBF frequenc FORBID_HO_ENUM(Forbid Ho)
NCELL D-00201 y
802 Handov Unit: None
MOD
EUTRA LBFD-0 er Actual Value Range: PERMIT_HO_ENUM,
NINTE 0201804 Distance FORBID_HO_ENUM
RFREQ / Based Default Value: PERMIT_HO_ENUM(Permit Ho)
NCELL TDLBF Inter-
LST D-00201 frequenc
EUTRA 804 y
NINTE LBFD-0 Handov
RFREQ 0201805 er
NCELL / Service
TDLBF Based
D-00201 Inter-
805 frequenc
LOFD-0 y
02012 / Handov
TDLOF er
D-00201 Cell
2 Outage
Detectio
n and
Compen
sation
EutranIn MlbTarg ADD LOFD-0 Intra- Meaning: Indicates whether the neighboring frequency
terNFre etInd EUTRA 01032 / LTE of the serving frequency can be a target frequency in
q NINTE TDLOF Load load balancing. If this parameter is set to ALLOWED,
RNFRE D-00103 Balancin the neighboring frequency of the serving frequency can
Q 2 g be selected as a target frequency in load balancing. If
MOD this parameter is set to NOT_ALLOWED, the
EUTRA neighboring frequency of the serving frequency cannot
NINTE be selected as a target frequency in load balancing.
RNFRE GUI Value Range: NOT_ALLOWED
Q (NOT_ALLOWED), ALLOWED(ALLOWED)
LST Unit: None
EUTRA Actual Value Range: NOT_ALLOWED, ALLOWED
NINTE
RNFRE Default Value: ALLOWED(ALLOWED)
Q

eRAN

nd
CellML LoadBal MOD LOFD-0 Intra- Meaning: Indicates the policy based on which the
B anceNC CELLM 70215 / LTE serving cell selects certain neighboring cells as
ellScope LB TDLOF User candidate cells for inter-frequency load balancing if no
LST D-07021 Number neighboring cells are manually configured as
CELLM 5 Load overlapping neighboring cells. If this parameter is set to
LB Balancin ADAPTIVE(Adaptive), the InterFreqMlbSwitch
g option of the MlbAlgoSwitch parameter is selected, and
the InterFreqBlindMlbSwitch option of the
MlbAlgoSwitch parameter is not selected, the serving
cell selects certain intra-eNodeB inter-frequency
neighboring cells as candidate cells for load balancing
when the serving cell has at least one intra-eNodeB
inter-frequency neighboring cell or the serving cell
selects certain inter-eNodeB inter-frequency
neighboring cells configured with X2 interfaces as
candidate cells for load balancing when the serving cell
has no intra-eNodeB inter-frequency neighboring cell.
If this parameter is set to ADAPTIVE(Adaptive), the
InterFreqMlbSwitch option of the MlbAlgoSwitch
parameter is not selected, and the InterFreqBlindMlbS-
witch option of the MlbAlgoSwitch parameter is
selected, the serving cell selects certain inter-eNodeB
inter-frequency neighboring cells as candidate cells for
inter-frequency load balancing. If this parameter is set
to ADAPTIVE(Adaptive), the InterFreqMlbSwitch
option of the MlbAlgoSwitch parameter is selected, and
the InterFreqBlindMlbSwitch option of the
MlbAlgoSwitch parameter is selected, the serving cell
selects certain intra-eNodeB inter-frequency
neighboring cells as candidate cells for inter-frequency
load balancing when the serving cell has at least one
intra-eNodeB inter-frequency neighboring cell or the
serving cell selects certain inter-eNodeB inter-
frequency neighboring cells as candidate cells for load
balancing when the serving cell has no intra-eNodeB
inter-frequency neighboring cell. If this parameter is set
to ALL(All), the InterFreqMlbSwitch option of the
MlbAlgoSwitch parameter is selected, and the
InterFreqBlindMlbSwitch option of the
MlbAlgoSwitch parameter is not selected, the serving
cell selects all intra-eNodeB inter-frequency
neighboring cells and inter-eNodeB inter-frequency
neighboring cells configured with X2 interfaces as
candidate cells for inter-frequency load balancing. If
this parameter is set to ALL(All) and the InterFreq-
BlindMlbSwitch option of the MlbAlgoSwitch
parameter is selected regardless the setting of the

eRAN

nd
InterFreqMlbSwitch option of the MlbAlgoSwitch

parameter, the serving cell selects all inter-frequency
neighboring cells as candidate cells for inter-frequency
load balancing.
GUI Value Range: ADAPTIVE(Adaptive), ALL(All)
Unit: None
Actual Value Range: ADAPTIVE, ALL
Default Value: ADAPTIVE(Adaptive)
CellML UeNum MOD LOFD-0 Intra- Meaning: Indicates the proportion threshold for
B DiffThd CELLM 70215 / LTE determining whether a neighboring cell can be a target
LB TDLOF User cell in load balancing. Providing that the number of
LST D-07021 Number synchronized UEs in the serving cell is value "A" and
CELLM 5 Load that in a neighboring cell is value "B", the proportion
LB Balancin threshold is calculated by "A" dividing the value of "A"
g minus "B". If a calculated proportion is greater than this
parameter value, the neighboring cell involved in the
calculation can be a target cell in load balancing.
Unit: %
Default Value: 15
EutranIn CellRes ADD LBFD-0 Cell Meaning: Indicates whether to set the reselection
terNFre elPriorit EUTRA 0201803 Selectio priority of the neighboring E-UTRAN frequency. If the
q yCfgInd NINTE / n and value of this parameter is not specified, the UE does not
RNFRE TDLBF Re- reselect to neighboring cells on the frequency.
Q D-00201 selection GUI Value Range: NOT_CFG(Not configure), CFG
MOD 803 (Configure)
EUTRA Unit: None
NINTE
RNFRE Actual Value Range: NOT_CFG, CFG
Q Default Value: NOT_CFG(Not configure)
LST
EUTRA
NINTE
RNFRE
Q

eRAN

nd
RrcCon T320For MOD None None Meaning: Indicates the length of timer T320 for load
nStateTi LoadBal RRCCO balancing. T320 specifies the time period during which
mer ance NNSTA the dedicated priorities (used for cell reselection) retain
TETIM valid. The time period is contained in the
ER RRCConnectionRelease message that is received by the
LST UE. After T320 expires, the dedicated priorities become
RRCCO invalid. This timer is started when the UE receives an
NNSTA RRCConnectionRelease message containing the t320
TETIM IE. This timer is stopped when the UE enters the
ER RRC_CONNECTED mode.
GUI Value Range: min5(5), min10(10), min20(20),
min30(30), min60(60), min120(120), min180(180)
Unit: min
Actual Value Range: min5, min10, min20, min30,
min60, min120, min180
Default Value: min10(10)
CellML InterFre MOD LOFD-0 Intra- Meaning: Indicates the threshold of the number of
B qMlbUe CELLM 70215 / LTE synchronized UEs for triggering inter-frequency load
NumTh LB TDLOF User balancing. When the MlbTriggerMode parameter is set
d LST D-07021 Number to UE_NUMBER_ONLY(UeNumMode) or
CELLM 5 Load PRB_OR_UE_NUMBER(PrbOrUeNumMode), inter-
LB Balancin frequency load balancing is triggered if the number of
g synchronized UEs in the cell is greater than or equal to
the sum of the InterFreqMlbUeNumThd and
MlbUeNumOffset parameter values. Inter-frequency
load balancing stops if the number of synchronized UEs
in the cell is less than the InterFreqMlbUeNumThd
parameter value.
Unit: None
Default Value: 100

eRAN

nd
CellML FreqSele MOD LOFD-0 Intra- Meaning: Indicates the target frequency selection policy
B ctStrateg CELLM 70215 / LTE applied for inter-frequency load balancing and inter-
y LB TDLOF User RAT load sharing when candidate cells work at different
LST D-07021 Number frequencies. If this parameter is set to
CELLM 5 Load FAIRSTRATEGY(FairStrategy), a frequency among
LB Balancin all neighboring frequencies of candidate cells is
g randomly selected as the target frequency in inter-
frequency load balancing, all inter-RAT neighboring
frequencies of candidate cells are selected as the target
frequencies in inter-RAT load sharing, and a maximum
of three frequencies among all neighboring frequencies
of candidate cells are randomly selected as the target
frequencies in inter-frequency load balancing by
transferring UEs with low spectral efficiency. If this
parameter is set to PRIORITYBASED(PriorityBased),
the frequency with the highest priority among all intra-
RAT neighboring frequencies and the frequency with
the highest priority among all inter-RAT frequencies are
selected as target frequencies separately when inter-
frequency load balancing and inter-RAT load sharing
are triggered separately or both operator-level inter-
frequency load balancing and inter-RAT load sharing
are triggered together; the frequency with the highest
priority among all neighboring frequencies when both
cell-level inter-frequency load balancing and inter-RAT
load sharing are triggered together; a maximum of three
frequencies with the highest priorities among all
different frequencies are selected as target frequencies
when inter-frequency load balancing by transferring
UEs with low spectral efficiency is triggered.
GUI Value Range: FAIRSTRATEGY(FairStrategy),
PRIORITYBASED(PriorityBased)
Unit: None
Actual Value Range: FAIRSTRATEGY,
PRIORITYBASED
Default Value: FAIRSTRATEGY(FairStrategy)

eRAN

nd
EutranIn MlbFreq ADD LOFD-0 Intra- Meaning: Indicates the priority of the neighboring E-
terNFre Priority EUTRA 01032/ LTE UTRAN frequency for load balancing. The value 0
q NINTE TDLOF Load indicates the lowest priority. The neighboring E-
RNFRE D-00103 Balancin UTRAN frequency with the highest priority is selected
Q 2 g as the target frequency for inter-frequency load
MOD balancing.
EUTRA GUI Value Range: 0~7
NINTE Unit: None
RNFRE
Q Actual Value Range: 0~7
LST Default Value: 7

EUTRA
NINTE
RNFRE
Q
UtranNF MlbFreq ADD LOFD-0 Intra- Meaning: Indicates the priority of the neighboring
req Priority UTRAN 01032/ LTE UTRAN frequency for load sharing with UTRAN. The
NFREQ TDLOF Load value 0 indicates the lowest priority. The neighboring
MOD D-00103 Balancin UTRAN frequency with the highest priority is selected
UTRAN 2 g as the target frequency for inter-RAT load sharing.
NFREQ GUI Value Range: 0~7
LST Unit: None
UTRAN Actual Value Range: 0~7
NFREQ
Default Value: 0

eRAN

nd
CellML MlbUeS MOD LOFD-0 Intra- Meaning: Indicates the UE PRB usage threshold for UE
B electPrb CELLM 70215 / LTE selection in mobility load balancing (MLB). (1) If the
Thd LB TDLOF User MlbTriggerMode parameter is set to PRB_ONLY
LST D-07021 Number (PrbMode) and the value of this parameter is set to 100,
CELLM 5 Load no NEs are selected. If the value of this parameter is not
LB Balancin set to 100, the eNodeB selects UEs whose PRB usage
g in the transmission direction (that triggers MLB) is
greater than this parameter value but the PRB usage in
the opposite direction that triggers MLB is less than this
parameter value. (2) If the MlbTriggerMode parameter
is set to UE_NUMBER_ONLY(UeNumMode) and the
value of this parameter is set to 100, the eNodeB selects
UEs without considering the UE PRB usage. If the value
of this parameter is not set to 100, the eNodeB selects
UEs whose PRB usage is less than or equal to this
parameter value. (3) If the MlbTriggerMode parameter
is set to PRB_OR_UE_NUMBER
(PrbOrUeNumMode) and the MLB procedure is
triggered by the PRB usage, the eNodeB selects UEs for
MLB in the same way as that when the
MlbTriggerMode parameter is set to PRB_ONLY
(PrbMode). If the MlbTriggerMode parameter is set to
PRB_OR_UE_NUMBER(PrbOrUeNumMode) and
MLB is triggered by the number of activated UEs in the
serving cell, the eNodeB selects UEs for MLB in the
same way as that when the MlbTriggerMode parameter
is set to UE_NUMBER_ONLY(UeNumMode).
Unit: %
Default Value: 2
SpidCfg InterFre ADD LOFD-0 Camp & Meaning: Indicates whether to enable or disable inter-
qMlbSw SPIDCF 0105401 Handov frequency load balancing for the SPID. The values
itch G / er Based TRUE or FALSE indicate that inter-frequency load
MOD TDLOF on SPID balancing is allowed or prohibited for UEs with the
SPIDCF D-00105 Intra- SPID, respectively.
G 401 LTE GUI Value Range: FALSE(FALSE), TRUE(TRUE)
LST LOFD-0 Load Unit: None
SPIDCF 01032 / Balancin
TDLOF g Actual Value Range: FALSE, TRUE
G
D-00103 Default Value: TRUE(TRUE)
2

eRAN

nd
CellML MlbMax MOD LOFD-0 Intra- Meaning: Indicates the maximum number of UEs that
B UeNum CELLM 70215 / LTE can be transferred to inter-frequency neighboring cells
LB TDLOF User within a load balancing period triggered by different
LST D-07021 Number factors. This parameter is used to prevent too many UEs
CELLM 5 Load from being transferred to inter-frequency neighboring
LB Balancin cells within a load balancing procedure and the load in
g inter-frequency neighboring cells from increasing
significantly.
Unit: None
Default Value: 5
CellML MlbHoC MOD LOFD-0 Intra- Meaning: Indicates whether the eNodeB is allowed to
B ellSelect CELLM 01032 / LTE initiate a handover to one of the secondary strongest
Strategy LB TDLOF Load neighboring cells when the eNodeB cannot initiate a
LST D-00103 Balancin handover to the strongest neighboring cell triggered by
CELLM 2 g load-information-exchange-based inter-frequency load
LB LOFD-0 Intra- balancing. If this parameter is set to
70215 / LTE PERMIT_NON_STRONGEST_CELL(Permit Trying
TDLOF User Non-Strongest Cell), the eNodeB is allowed to initiate
D-07021 Number a handover to one of the secondary strongest
5 Load neighboring cells in the preceding scenario. If this
Balancin parameter is set to ONLY_STRONGEST_CELL(Only
g Try Strongest Cell), the eNodeB can only initiate a
handover to the strongest neighboring cell in the
preceding scenario.
GUI Value Range: ONLY_STRONGEST_CELL(Only
Try Strongest Cell),
PERMIT_NON_STRONGEST_CELL(Permit Trying
Non-Strongest Cell)
Unit: None
Actual Value Range: ONLY_STRONGEST_CELL,
PERMIT_NON_STRONGEST_CELL
Default Value: PERMIT_NON_STRONGEST_CELL
(Permit Trying Non-Strongest Cell)

eRAN

nd
InterFre InterFre ADD LBFD-0 Service Meaning: Indicates the RSRP threshold for event A4
qHoGro qLoadB INTERF 0201805 Based related to load-based inter-frequency handover. When
up asedHo REQHO / Inter- the measured RSRP value exceeds this threshold, event
A4ThdR GROUP TDLBF frequenc A4 is reported. The value of this parameter is also used
srp MOD D-00201 y as the RSRP threshold for event A4 related to
INTERF 805 Handov frequency-priority-based handover, service-based
REQHO er inter-frequency handover, inter-frequency handover of
GROUP low-speed UEs, or redirection of high-speed UEs.
LST GUI Value Range: -140~-43

INTERF Unit: dBm
REQHO Actual Value Range: -140~-43
GROUP
Default Value: -103
EutranIn IfMlbTh ADD LOFD-0 Intra- Meaning: Indicates the offset to the RSRP threshold for
terNFre dRsrpOf EUTRA 01032 / LTE events A4 and A5 that trigger load-based inter-
q fset NINTE TDLOF Load frequency handovers. In load-based inter-frequency
RNFRE D-00103 Balancin handovers, the eNodeB delivers the RSRP threshold for
Q 2 g event A4 or A5 to UEs, which is equal to the sum of the
MOD InterFreqLoadBasedHoA4ThdRsrp and
EUTRA IfMlbThdRsrpOffset parameter values. If the RSRP
NINTE threshold for event A4 or A5 is less than the minimum
RNFRE RSRP value, the minimum value is delivered instead. If
Q the RSRP threshold for event A4 or A5 is greater than
the maximum RSRP value, the maximum value is
LST delivered instead.
EUTRA
NINTE GUI Value Range: -20~20
RNFRE Unit: dBm
Q Actual Value Range: -20~20
Default Value: 0
InterFre InterFre ADD LBFD-0 Service Meaning: Indicates the RSRQ threshold for event A4
qHoGro qLoadB INTERF 0201805 Based related to load-based inter-frequency handover. When
up asedHo REQHO / Inter- the measured RSRQ value exceeds this threshold, event
A4ThdR GROUP TDLBF frequenc A4 is reported. The value of this parameter is also used
srq MOD D-00201 y as the RSRQ threshold for event A4 related to
INTERF 805 Handov frequency-priority-based, service-based inter-
REQHO er frequency handover, inter-frequency handover of low-
GROUP speed UEs, or redirection of high-speed UEs.
LST GUI Value Range: -40~-6

INTERF Unit: 0.5dB
REQHO Actual Value Range: -20~-3
GROUP
Default Value: -18

eRAN

nd
IntraRat InterFre MOD LBFD-0 Coverag Meaning: Indicates the trigger quantity for event A4/A5
HoCom qHoA4T INTRA 0201802 e Based measurement reports of all inter-frequency handovers
m rigQuan RATHO / Inter- except coverage-based inter-frequency handover.
COMM TDLBF frequenc GUI Value Range: RSRP, RSRQ, BOTH
LST D-00201 y
802 Handov Unit: None
INTRA
RATHO LOFD-0 er Actual Value Range: RSRP, RSRQ, BOTH
COMM 0109804 Carrier Default Value: RSRP
/ Manage
TDLAO ment
FD-001
00306
IntraRat InterFre MOD LBFD-0 Coverag Meaning: Indicates the quantity to be included in the
HoCom qHoA4 INTRA 0201802 e Based measurement report for inter-frequency handover
m RprtQua RATHO / Inter- events. The quantity can be RSRP, RSRQ, or both. The
n COMM TDLBF frequenc measured RSRP values are stable, slightly varying with
LST D-00201 y the load, and therefore there is little signal fluctuation.
INTRA 802 Handov The measured RSRQ values vary with the load and are
RATHO LBFD-0 er likely to reflect the signal quality of the cell in real time.
COMM 0201804 Distance This parameter applies to measurements for event A4/
/ Based A5. For details, see 3GPP TS 36.331.
TDLBF Inter- GUI Value Range: SAME_AS_TRIG_QUAN(Same as
D-00201 frequenc Trig Quan), BOTH
804 y Unit: None
LBFD-0 Handov
er Actual Value Range: SAME_AS_TRIG_QUAN,
0201805 BOTH
/ Service
TDLBF Based Default Value: SAME_AS_TRIG_QUAN(Same as
D-00201 Inter- Trig Quan)
805 frequenc
y
Handov
er

eRAN

nd
CellAlg MlbHo MOD LOFD-0 Intra- Meaning: Indicates whether to enable or disable
oSwitch Mode CELLA 01032 / LTE handovers triggered by mobility load balancing (MLB),
LGOSW TDLOF Load based on which the eNodeB determines handover
ITCH D-00103 Balancin policies. If the InterFreqMlbBlindHo check box under
LST 2 g this parameter is selected, the eNodeB performs a blind
CELLA LOFD-0 Inter- handover to an intra-RAT inter-frequency neighboring
LGOSW 01044 / RAT cell for load balancing. Otherwise, the eNodeB does not
ITCH TD Load perform the blind handover. If the InterFreqMlbRedir-
LOFD-0 Sharing ect check box under this parameter is selected, the
01044 to eNodeB performs a load-based redirection to an intra-
UTRAN RAT inter-frequency neighboring cell. Otherwise, the
LOFD-0 eNodeB does not perform the redirection. If the
01045 / Inter- InterRatMlbRedirect check box under this parameter is
TDLOF RAT selected, the eNodeB performs a redirection from an E-
D-00104 Load UTRAN cell to a UTRAN or GERAN cell. Otherwise,
5 Sharing the eNodeB does not perform the redirection. If the
to InterRatMlbBlindHo check box under this parameter is
GERAN selected, the eNodeB performs a blind handover from
an E-UTRAN cell to a UTRAN or GERAN cell for load
balancing. Otherwise, the eNodeB does not perform the
blind handover.
GUI Value Range: InterFreqMlbBlindHo
(InterFreqMlbBlindHo), InterRatMlbBlindHo
(InterRatMlbBlindHo), InterFreqMlbRedirect
(InterFreqMlbRedirect), InterRatMlbRedirect
(InterRatMlbRedirect)
Unit: None
Actual Value Range: InterFreqMlbBlindHo,
InterRatMlbBlindHo, InterFreqMlbRedirect,
InterRatMlbRedirect
Default Value: InterFreqMlbBlindHo:Off,
InterRatMlbBlindHo:Off, InterFreqMlbRedirect:Off,
InterRatMlbRedirect:Off

eRAN

nd
EutranIn BlindHo ADD LBFD-0 Coverag Meaning: Indicates the priority of the neighboring cell
terFreq Priority EUTRA 0201802 e Based during handovers. The parameter values are divided into
NCell NINTE / Inter- three segments, indicating the blind-handover priority,
RFREQ TDLBF frequenc frequency-based-handover priority, and 0. Within the
NCELL D-00201 y same segment, a larger parameter value indicates a
MOD 802 Handov higher priority. Blind handover is a process in which the
EUTRA LBFD-0 er eNodeB instructs a UE to hand over to a specified
NINTE 0201804 Distance neighboring cell without measurements. If this
RFREQ / Based parameter value is set to 0, blind handovers and
NCELL TDLBF Inter- frequency-based handovers cannot be performed. The
D-00201 frequenc parameter values 1 to 16 indicate the blind-handover
LST priorities. The parameter values 17 to 32 indicate the
EUTRA 804 y
Handov frequency-based-handover priorities for frequency-
NINTE TDLOF based blind handovers and measurement-based
RFREQ D-00105 er
handovers.
NCELL 0 Mobility
between GUI Value Range: 0~32
LTE Unit: None
TDD
and LTE
FDD Default Value: 0
CellML InterFre MOD LOFD-0 Intra- Meaning: Indicates the threshold of the PRB usage for
B qMlbTh CELLM 01032 / LTE triggering inter-frequency load balancing. If the
d LB TDLOF Load MlbTriggerMode parameter is set to PRB_ONLY
LST D-00103 Balancin (PrbMode) or PRB_OR_UE_NUMBER
CELLM 2 g (PrbOrUeNumMode), inter-frequency load balancing is
LB triggered when the number of synchronized UEs in the
MlbMinUeNumThd and MlbMinUeNumOffset
parameter values and the PRB usage of the cell is greater
than or equal to the sum of the InterFreqMlbThd and
LoadOffset parameter values. Load balancing stops
when the PRB usage of the cell or the number of
synchronized UEs falls below the value of the
InterFreqMlbThd parameter or the value of the
MlbMinUeNumThd parameter, respectively.
Unit: %
Default Value: 60

eRAN

nd
CellML LoadOff MOD LOFD-0 Intra- Meaning: Indicates the offset of the PRB usage for
B set CELLM 01032 / LTE triggering inter-frequency load balancing. Inter-
LB TDLOF Load frequency load balancing is triggered if the number of
LST D-00103 Balancin synchronized UEs in the cell is greater than or equal to
CELLM 2 g the sum of the MlbMinUeNumThd and
LB LOFD-0 Inter- MlbMinUeNumOffset parameter values and the PRB
01044 / RAT usage of the cell is greater than or equal to the sum the
TDLOF Load InterFreqMlbThd and LoadOffset parameter values.
D-00104 Sharing Inter-frequency load balancing is triggered if the
4 to number of synchronized UEs in the cell is greater than
UTRAN or equal to the sum of the MlbMinUeNumThd and
LOFD-0 MlbMinUeNumOffset parameter values and the PRB
01045 / Inter- valuation in the cell is greater than or equal to the sum
TDLOF RAT of the PrbValMlbTrigThd and LoadOffset parameter
D-00104 Load values. Inter-RAT load sharing is triggered if the
5 Sharing number of synchronized UEs in the cell is greater than
to or equal to the sum of the InterRatMlbUeNumThd and
GERAN InterRatMlbUeNumOffset parameter values and the
PRB usage of the cell is greater than or equal to the
InterRatMlbThd and LoadOffset parameter values.
Inter-RAT load sharing to transfer to-be-released UEs
is triggered if the number of synchronized UEs is greater
than or equal to the sum of the InterRATIdleMlbUe-
NumThd and InterRatMlbUeNumOffset parameter
values and the PRB usage of the cell is greater than or
equal to the sum of the InterRatMlbThd and LoadOffset
parameter values.
Unit: %
Default Value: 8

eRAN

nd
CellML MlbMin MOD LOFD-0 Intra- Meaning: Indicates the threshold of the minimum
B UeNum CELLM 01032 / LTE number of synchronized UEs for triggering inter-
Thd LB TDLOF Load frequency load balancing. When the MlbTriggerMode
LST D-00103 Balancin parameter is set to PRB_ONLY(PrbMode) or
CELLM 2 g PRB_OR_UE_NUMBER(PrbOrUeNumMode), load
LB balancing is triggered if the PRB usage of the cell is
greater than or equal to the sum of InterFreqMlbThd and
LoadOffset parameter values and the number of
synchronized UEs in the cell is greater than or equal to
the sum of the MlbMinUeNumThd and
MlbMinUeNumOffset parameter values. Load
balancing stops when the PRB usage of the cell or the
number of synchronized UEs falls below the value of
the InterFreqMlbThd parameter or the value of the
MlbMinUeNumThd parameter, respectively.
Unit: None
Default Value: 0
CellML MlbMin MOD LOFD-0 Intra- Meaning: Indicates the offset of the minimum number
B UeNum CELLM 01032 / LTE of synchronized UEs for triggering inter-frequency load
Offset LB TDLOF Load balancing. If the MlbTriggerMode parameter is set to
LST D-00103 Balancin PRB_ONLY(PrbMode) or PRB_OR_UE_NUMBER
CELLM 2 g (PrbOrUeNumMode), inter-frequency load balancing is
LB triggered when the number of synchronized UEs in the
MlbMinUeNumThd and MlbMinUeNumOffset
parameter values and the PRB usage of the cell is greater
than or equal to the sum the InterFreqMlbThd and
LoadOffset parameter values.
Unit: None
Default Value: 0

eRAN

nd
CellML LoadDif MOD LOFD-0 Intra- Meaning: Indicates the threshold of PRB usage
B fThd CELLM 01032 / LTE difference between the serving cell and a neighboring
LB TDLOF Load cell. When the result of the PRB usage of the serving
LST D-00103 Balancin cell minus that of a neighboring cell is greater than the
CELLM 2 g parameter value, this neighboring cell can be a target
LB LOFD-0 Inter- cell for mobility load balancing (MLB).
01044 / RAT GUI Value Range: 1~50
TDLOF Load Unit: %
D-00104 Sharing
4 to Actual Value Range: 1~50
LOFD-0 UTRAN Default Value: 15

01045 / Inter-
TDLOF RAT
D-00104 Load
5 Sharing
to
GERAN
CellML LoadTra MOD LOFD-0 Intra- Meaning: Indicates the control factor for the amount of
B nsferFac CELLM 01032 / LTE a single load transfer. The value of this parameter has
tor LB TDLOF Load an impact on the efficiency of MLB algorithm and the
LST D-00103 Balancin algorithm to prevent ping-pong load transfer.
LB Unit: %
Default Value: 0
CellML InterFre MOD LOFD-0 Operator Meaning: Indicates whether to enable operator-level
B qMLBR CELLM 70204 / Load inter-frequency load balancing. If this parameter is set
anShare LB TDLOF Based to SHARING, operator-level inter-frequency load
Mode LST D-07020 Intra- balancing is enabled and inter-frequency load balancing
CELLM 4 LTE is performed based on the reserved resources of each
LB MLB operator. If this parameter is set to NON_SHARING,
the eNodeB performs load balancing without
distinguishing operators and performs cell-level inter-
frequency load balancing.This parameter is dedicated to
LTE FDD cells.
GUI Value Range: NON_SHARING
(NON_SHARING), SHARING(SHARING)
Unit: None
Actual Value Range: NON_SHARING, SHARING
Default Value: NON_SHARING(NON_SHARING)

eRAN

nd
CellAlg RanShar MOD LOFD-0 RAN Meaning: Indicates whether to enable or disable RAN
oSwitch eModeS CELLA 01036 / Sharing sharing for admission and scheduling. If this switch is
witch LGOSW TDLOF with turned on, operators share data channel resources
ITCH D-00103 Commo according to the specified percentages.
LST 6 n Carrier GUI Value Range: OFF(Off), ON(On)
CELLA TDLOF MOCN Unit: None
LGOSW D-00111 Flexible
ITCH 2 Priority Actual Value Range: OFF, ON
LOFD-0 Based Default Value: OFF(Off)

70206 Campin
g
Hybrid
RAN
Sharing
CellOp OpUeN ADD LOFD-0 Intra- Meaning: Indicates the percentage of activated UEs
umRatio CELLO 01032 / LTE served by the operator in a cell when inter-frequency
P TDLOF Load load balancing and RAN sharing are enabled.
MOD D-00103 Balancin Modifications on this parameter affect the percentage of
CELLO 2 g activated UEs served by operators.
P GUI Value Range: 1~100
LST Unit: %
CELLO Actual Value Range: 1~100
P
Default Value: 16
CellOp OpDlRb ADD LOFD-0 RAN Meaning: Indicates the percentage of resource blocks
UsedRat CELLO 01036 / Sharing (RBs) occupied by the operator on the physical
io P TDLOF with downlink shared channel (PDSCH) when RAN sharing
MOD D-00103 Commo is enabled on the eNodeB and the cell-level RAN
CELLO 6 n Carrier sharing switch is turned on. If the data volume is
P LBFD-0 Broadca sufficient, the percentage of RBs occupied by each
02009 / st of operator will reach the preset value. Modifications on
LST this parameter affect the percentage of RBs occupied by
CELLO TDLBF system
D-00200 informat operators on the PDSCH. This parameter takes effect
P only in RAN sharing with common carriers mode or in
9 ion
hybrid RAN sharing mode with more than one CellOp
LOFD-0 Hybrid MO being configured.
70206 RAN
Sharing GUI Value Range: 1~100
Unit: %
Default Value: 16

eRAN

nd
CellOp OpUlRb ADD LOFD-0 RAN Meaning: Indicates the percentage of resource blocks
UsedRat CELLO 01036 / Sharing (RBs) occupied by the operator on the physical uplink
io P TDLOF with shared channel (PUSCH) when radio access network
MOD D-00103 Commo (RAN) sharing is enabled on the eNodeB and the cell-
CELLO 6 n Carrier level RAN sharing switch is turned on. If the data
P LBFD-0 Broadca volume is sufficient, the percentage of RBs occupied by
02009 / st of each operator will reach the preset value. Modifications
LST on this parameter affect the percentage of RBs occupied
CELLO TDLBF system
D-00200 informat by operators on the PUSCH. This parameter takes effect
P only in RAN sharing with common carriers mode or in
9 ion
hybrid RAN sharing mode with more than one CellOp
LOFD-0 Hybrid MO being configured.
70206 RAN
Sharing GUI Value Range: 1~100
Unit: %
Default Value: 16
EutranIn IdleMlb ADD LOFD-0 Intra- Meaning: Indicates the preset proportion of UEs in idle
terNFre UERele EUTRA 01032 / LTE mode in a frequency. This parameter takes effect when
q aseRatio NINTE TDLOF Load the InterFreqIdleMlbSwitch option of the
RNFRE D-00103 Balancin MlbAlgoSwitch parameter in the CellAlgoSwitch MO
Q 2 g and the Proportion option of the InterFreqIdleMlbMode
MOD parameter in the CellMlb MO are selected. The eNodeB
EUTRA transfers normally released UEs to frequencies based on
NINTE the preset proportions among frequencies, so that load
RNFRE balancing for UEs in idle mode is achieved. The sum of
Q proportions for load balancing among all frequencies
cannot exceed 100%. Proportion for load balancing at
LST the serving frequency = 100% (proportion at
EUTRA frequency 1 + proportion at frequency 2 + +
NINTE proportion at frequency n). If the
RNFRE INTER_FREQ_IDLE_MLB_SWITCH option of the
Q MlbAlgoSwitch parameter in the ENodeBAlgoSwitch
MO and the ADAPTIVE_PROPORTION option of the
InterFreqIdleMlbMode parameter in the eNodeBMlb
MO are selected, the eNodeB adaptively adjusts the
proportions of UEs in idle mode among frequencies
based on UE distribution in the network, ensuring that
the proportions of UEs in idle mode among frequencies
approach to the preset proportions.
Unit: %
Default Value: 0

eRAN

nd
eNodeB InterFre MOD None None Meaning: Indicates the statistic period within which the
Mlb qIdleMl ENODE eNodeB periodically collects the average number of
bInterva BMLB uplink synchronized UEs in a cell during eNodeB-level
l LST inter-frequency load pre-balancing. If both
ENODE INTER_FREQ_IDLE_MLB_SWITCH of the
BMLB MlbAlgoSwitch parameter in the ENodeBAlgoSwitch
MO and ADAPTIVE_PROPORTION of the
MO are on, the eNodeB collects the number of uplink
synchronized UEs at an interval specified by the
InterFreqIdleMlbInterval parameter. At the end of a
measurement period, the eNodeB adaptively adjusts the
proportions in which to-be-released UEs camp on cells
operating at different frequencies. If the
InterFreqIdleMlbInterval parameter is set to off, the
eNodeB does not adjust the proportions in which to-be-
released UEs camp on cells operating at different
frequencies.
Unit: min
Default Value: 1440

eRAN

nd
eNodeB InterFre MOD None None Meaning: Indicates the threshold for the average
Mlb qIdleMl ENODE number of uplink synchronized UEs above which the
bStaThd BMLB eNodeB adjusts the proportions in which to-be-released
LST UEs camp on cells operating in different frequencies
ENODE based on the actual statistic results during eNodeB-level
BMLB inter-frequency load pre-balancing. If both
INTER_FREQ_IDLE_MLB_SWITCH of the
MlbAlgoSwitch parameter in the ENodeBAlgoSwitch
MO and ADAPTIVE_PROPORTION of the
MO are on, the eNodeB performs periodic statistics on
the average number of uplink synchronized UEs in a
cell. If the sum of the average number of uplink
synchronized UEs in all cells is greater than or equal to
this parameter value, the eNodeB updates the proportion
in which to-be-released UEs camp on cells operating in
different frequencies during eNodeB-level inter-
frequency load pre-balancing based on the actual
statistic results within the statistic period.
Unit: None
Default Value: 3
CellML InterFre MOD LOFD-0 Intra- Meaning: Indicates the inter-frequency load balancing
B qIdleMl CELLM 01032/ LTE mode for UEs in idle mode. If the Proportion check box
bMode LB TDLOF Load under this parameter is selected, the eNodeB transfers
LST D-00103 Balancin normally released UEs to frequencies based on the
CELLM 2 g preset proportions for neighboring frequencies of the
LB serving frequency so that load balancing for UEs in idle
mode is achieved. This parameter is valid only when the
Proportion check box is selected.
GUI Value Range: Proportion(Proportion)
Unit: None
Actual Value Range: Proportion
Default Value: Proportion:Off

eRAN

nd
ENodeB MlbAlg MOD LOFD-0 Intra- Meaning: Indicates whether to enable eNodeB-level
AlgoSwi oSwitch ENODE 01032 / LTE mobility load balancing.
tch BALGO TDLOF Load INTER_FREQ_IDLE_MLB_SWITCH: Indicates
SWITC D-00103 Balancin whether to enable eNodeB-level inter-frequency load
H 2 g balancing for UEs in idle mode. If the
LST INTER_FREQ_IDLE_MLB_SWITCH option of this
ENODE parameter and the ADAPTIVE_PROPORTION option
BALGO of the InterFreqIdleMlbMode parameter are selected,
SWITC the eNodeB timely adjusts the proportions of UEs to be
H released among frequencies based on the current
proportions of UEs in connected mode among
frequencies and the preset proportions of UEs in idle
mode among frequencies, ensuring that the actual
proportions of UEs in idle mode among frequencies
approach to the preset proportions.
GUI Value Range:
INTER_FREQ_IDLE_MLB_SWITCH
(INTER_FREQ_IDLE_MLB_SWITCH)
Unit: None
Actual Value Range:
INTER_FREQ_IDLE_MLB_SWITCH
Default Value:
INTER_FREQ_IDLE_MLB_SWITCH:Off
eNodeB InterFre MOD None None Meaning: Indicates the mode for eNodeB-level inter-
Mlb qIdleMl ENODE frequency load balancing for UEs in idle
bMode BMLB mode.ADAPTIVE_PROPORTION: Indicates whether
LST the eNodeB adjusts the proportions of UEs in idle mode
ENODE among frequencies during eNodeB-level inter-
BMLB frequency load balancing for UEs in idle mode.If the
ADAPTIVE_PROPORTION option of this parameter
and the INTER_FREQ_IDLE_MLB_SWITCH option
of the MlbAlgoSwitch parameter are selected, the
eNodeB timely adjusts the proportions of UEs to be
released among frequencies based on the current
proportions of UEs among frequencies and the preset
proportions of UEs among frequencies, ensuring that
the proportions of UEs in idle mode among frequencies
approaches to the preset proportions.
GUI Value Range: ADAPTIVE_PROPORTION
(ADAPTIVE_PROPORTION)
Unit: None
Actual Value Range: ADAPTIVE_PROPORTION
Default Value: ADAPTIVE_PROPORTION:Off

eRAN

nd
CellAlg Reselec MOD LBFD-0 Cell Meaning: Indicates whether to enable or disable
oSwitch PriAdap CELLA 0201803 Selectio adaptive dedicated cell reselection priority. If this
tSwitch LGOSW / n and parameter is set to 1, the eNodeB delivers the dedicated
ITCH TDLBF Re- cell reselection priority to a UE when the following
LST D-00201 selection conditions are met: (1) The UE requests to set up an
CELLA 803 RRC connection with the cause value being mo-
LGOSW Signalling. (2) The MME instructs the eNodeB to
ITCH release the S1 bearer. (3) The eNodeB fails to obtain the
UE capability. If this switch is turned off, the eNodeB
does not deliver dedicated cell reselection priority to a
UE even if the eNodeB fails to obtain the UE capability
information.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CellML InterRat MOD LOFD-0 Inter- Meaning: Indicates the evaluation period for
B LoadEv CELLM 01044 / RAT determining whether to trigger inter-RAT load sharing.
alPrd LB TDLOF Load If the serving cell remains in the heavy load state within
LST D-00104 Sharing an evaluation period, inter-RAT load sharing is
CELLM 4 to triggered and certain UEs are transferred to an inter-
LB LOFD-0 UTRAN RAT neighboring cell. If the UtranMlbSwitch or
01045 / Inter- GeranMlbSwitch option of the MlbAlgoSwitch
TDLOF RAT parameter is selected, the InterFreqMlbSwitch or
D-00104 Load InterFreqBlindMlbSwitch option of the
5 Sharing MlbAlgoSwitch parameter is selected, and the
to FreqSelectStrategy parameter is set to
GERAN PRIORITYBASED(PriorityBased), the values of the
InterRatLoadEvalPrd and InterFreqLoadEvalPrd
parameters must be the same. If the two parameters are
set to different values, the evaluation period specified
by the InterRatLoadEvalPrd parameter is adapted when
both cell-level inter-frequency load balancing and inter-
RAT load sharing are triggered at the same time.
Unit: s
Default Value: 30

eRAN

nd
EutranIn CellRes ADD LBFD-0 Cell Meaning: Indicates the cell reselection priority of the
terNFre elPriorit EUTRA 0201803 Selectio neighboring E-UTRAN frequency. The value 0
q y NINTE / n and indicates the lowest priority. It is contained in system
RNFRE TDLBF Reselect information block type 5 (SIB5). The UE decides
Q D-00201 ion whether to reselect a neighboring cell on the frequency
MOD 803 based on the value of this parameter and the absolute
EUTRA priority of the serving cell. If the value of this parameter
NINTE is larger than the absolute priority of the serving cell,
RNFRE the UE starts measurements on neighboring cells on the
Q frequency; then if the signal quality of some
neighboring cells meets the related conditions, the UE
LST starts cell reselection. If the value of this parameter is
EUTRA less than or equal to the absolute priority of the serving
NINTE cell, the UE starts the measurements only when the
RNFRE signal quality of the serving cell is poor; then if the
Q signal quality of some neighboring cells meets the
related conditions, the UE starts cell reselection.
Frequencies used for different RATs must be assigned
different cell reselection priorities. For details, see
3GPP TS 36.331.
Unit: None
Default Value: 1
EutranIn ThreshX ADD LBFD-0 Cell Meaning: Indicates the RX level required for a
terNFre high EUTRA 0201803 Selectio neighboring cell on the frequency to become a candidate
q NINTE / n and for reselection if the priority of the frequency is higher
RNFRE TDLBF Reselect than that of the serving frequency. After measurements
Q D-00201 ion are started for neighboring cells on the frequency, the
MOD 803 UE reselects to a neighboring cell on the frequency only
EUTRA if the RX level of the cell is better than the value
NINTE specified by this parameter for a time-to-trigger. For
RNFRE details, see 3GPP TS 36.331.
Q GUI Value Range: 0~31
LST Unit: 2dB
EUTRA Actual Value Range: 0~62
NINTE
RNFRE Default Value: 11
Q

eRAN

nd
InterFre InterFre ADD LBFD-0 Coverag Meaning: Indicates the RSRP threshold for event A2
qHoGro qHoA2T INTERF 0201802 e Based related to event-A4/A5-triggered inter-frequency
up hdRsrp REQHO / Inter- handover. When the measured RSRP value is lower than
GROUP TDLBF frequenc this threshold, a measurement report will be sent.
MOD D-00201 y GUI Value Range: -140~-43
INTERF 802 Handov
er Unit: dBm
REQHO
GROUP Actual Value Range: -140~-43
LST Default Value: -109

INTERF
REQHO
GROUP
CellRes ThrshSe MOD LBFD-0 Cell Meaning: Indicates the threshold used in the evaluation
el rvLow CELLR 0201803 Selectio of reselection to a cell on a lower priority E-UTRAN
ESEL / n and frequency or on an inter-RAT frequency. Cell
LST TDLBF Re- reselection to a cell on a lower priority E-UTRAN
CELLR D-00201 selection frequency or on an inter-RAT frequency is performed
ESEL 803 Broadca if no cell on the serving frequency or on a higher priority
LBFD-0 st of E-UTRAN frequency fulfills criteria 1 for inter-
02009 / system frequency and inter-RAT reselections. For details, see
TDLBF informat 3GPP TS 36.304.
D-00200 ion GUI Value Range: 0~31
9 Unit: 2dB
Default Value: 7
CellRes SNonInt MOD LBFD-0 Cell Meaning: Indicates the measurement triggering
el raSearch CELLR 0201803 Selectio threshold for reselection to inter-frequency or inter-
ESEL / n and RAT cells. If the cell reselection priority of a frequency
LST TDLBF Re- or RAT is higher than that of the serving frequency, the
CELLR D-00201 selection UEs always start inter-frequency or inter-RAT
ESEL 803 Broadca measurements. If the cell reselection priority of a
LBFD-0 st of frequency is lower than or equal to that of the serving
02009 / system frequency or if the cell reselection priority of an RAT is
TDLBF informat lower than that of the serving frequency, the UEs start
D-00200 ion inter-frequency or inter-RAT measurements only when
9 the value of Cell selection RX level value (dB) is lower
than or equal to the value of this parameter.
Unit: 2dB
Default Value: 9

eRAN

nd
SpidCfg Spid ADD LOFD-0 Camp & Meaning: Indicates the subscriber profile ID (SPID).
SPIDCF 0105401 Handov GUI Value Range: 1~256
G / er Based
TDLOF on SPID Unit: None
LST
SPIDCF D-00105 UL Pre- Actual Value Range: 1~256
G 401 allocatio Default Value: None
MOD LOFD-0 n Based
SPIDCF 01059 / on SPID
G TDLOF
D-00105
RMV 9
SPIDCF
G
SpidCfg RatFreq ADD LOFD-0 Camp & Meaning: Indicates whether to set the priority for the
PriorityI SPIDCF 0105401 Handov intra-RAT frequency group. If this parameter is set to
nd G / er Based CFG(CFG), UEs select the target frequency based on
MOD TDLOF on SPID the priority setting. If this parameter is set to NOT_CFG
SPIDCF D-00105 (NOT_CFG), UEs do not select the target frequency
G 401 based on the priority setting.
LST GUI Value Range: NOT_CFG(NOT_CFG), CFG

SPIDCF (CFG)
G Unit: None
Actual Value Range: NOT_CFG, CFG
Default Value: NOT_CFG(NOT_CFG)
SpidCfg RatFreq ADD LOFD-0 Camp & Meaning: Indicates the ID of the intra-RAT frequency
Priority SPIDCF 0105401 Handov priority group.
GroupId G / er Based GUI Value Range: 0~255
MOD TDLOF on SPID
D-00105 Unit: None
SPIDCF
G 401 Actual Value Range: 0~255
LST Default Value: 0

SPIDCF
G

eRAN

nd
TLDRA TRMUL SET LOFD-0 Intra- Meaning: Indicates the threshold for triggering the UL
LG LDRTR TLDRA 01032 / LTE high load. If the ratio of the UL transport load to the UL
GTH LG TDLOF Load transport bandwidth of the BS keeps above this
LST D-00103 Balancin threshold for a period of hysteresis, the UL transport
TLDRA 2 g load of the BS enters the high-load state. In UL high-
LG load state, the BS sends a UL S1 TNL Load Indicator,
which is set to HighLoad, to each neighboring BS
through the X2 interface.
Unit: %
Default Value: 70
TLDRA TRMDL SET LOFD-0 Intra- Meaning: Indicates the threshold for triggering the DL
LG LDRTR TLDRA 01032 / LTE high load. If the ratio of the DL transport load to the DL
GTH LG TDLOF Load transport bandwidth of the BS keeps above this
LST D-00103 Balancin threshold for a period of hysteresis, the DL transport
TLDRA 2 g load of the BS enters the high-load state. In DL high-
LG load state, the BS sends a DL S1 TNL Load Indicator,
which is set to HighLoad, to each neighboring BS
Unit: %
Default Value: 70
TLDRA TRMUL SET LOFD-0 Intra- Meaning: Indicates the threshold for clearing the UL
LG LDRCL TLDRA 01032 / LTE high load. If the ratio of the UL transport load to the UL
RTH LG TDLOF Load transport bandwidth of the BS keeps below this
LST D-00103 Balancin threshold for a period of hysteresis, the UL transport
TLDRA 2 g load of the BS enters the medium-load state. In UL
LG medium load state, the BS sends a UL S1 TNL Load
Indicator, which is set to MediumLoad, to each
neighboring BS through the X2 interface.
Unit: %
Default Value: 65

eRAN

nd
TLDRA TRMDL SET LOFD-0 Intra- Meaning: Indicates the threshold for clearing the DL
LG LDRCL TLDRA 01032 / LTE high load. If the ratio of the transport load to the
RTH LG TDLOF Load transmission bandwidth in DL of the BS keeps below
LST D-00103 Balancin this threshold for a period of time, the DL transport load
TLDRA 2 g of the BS enters the medium-load state. In DL medium-
LG load state, the BS sends a DL S1 TNL Load Indicator,
which is set to MediumLoad, to each neighboring BS
Unit: %
Default Value: 65
TLDRA TRMUL SET LOFD-0 Intra- Meaning: Indicates the threshold for triggering the UL
LG MLDTR TLDRA 01032 / LTE medium load. If the ratio of the UL transport load to the
GTH LG TDLOF Load UL transport bandwidth of the BS is above this
LST D-00103 Balancin threshold, the UL transport load of the BS enters the
TLDRA 2 g medium-load state. In UL medium-load state, the BS
LG sends a UL S1 TNL Load Indicator, which is set to
MediumLoad, to each neighboring BS through the X2
interface.
Unit: %
Default Value: 50
TLDRA TRMDL SET LOFD-0 Intra- Meaning: Indicates the threshold for triggering the DL
LG MLDTR TLDRA 01032 / LTE medium load. If the ratio of the DL transport load to the
GTH LG TDLOF Load DL transport bandwidth of the BS is above this
LST D-00103 Balancin threshold, the DL transport load of the BS enters the
TLDRA 2 g medium-load state. In DL medium-load state, the BS
LG sends a DL S1 TNL Load Indicator, which is set to
MediumLoad, to each neighboring BS through the X2
interface.
Unit: %
Default Value: 50

eRAN

nd
TLDRA TRMUL SET LOFD-0 Intra- Meaning: Indicates the threshold for clearing the UL
LG MLDCL TLDRA 01032 / LTE medium load. If the ratio of the UL transport load to the
RTH LG TDLOF Load UL transport bandwidth of the BS is below this
LST D-00103 Balancin threshold, the UL transport load of the BS enters the
TLDRA 2 g low-load state. In UL low-load state, the BS sends a UL
LG S1 TNL Load Indicator, which is set to LowLoad, to
each neighboring BS through the X2 interface.
Unit: %
Default Value: 45
TLDRA TRMDL SET LOFD-0 Intra- Meaning: Indicates the threshold for clearing the DL
LG MLDCL TLDRA 01032 / LTE medium load. If the ratio of the DL transport load to the
RTH LG TDLOF Load DL transport bandwidth of the BS is below this
LST D-00103 Balancin threshold, the DL transport load of the BS enters the
TLDRA 2 g low-load state. In DL low-load state, the BS sends a DL
LG S1 TNL Load Indicator, which is set to LowLoad, to
each neighboring BS through the X2 interface.
Unit: %
Default Value: 45

eRAN
Description 15 Counters
15 Counters
Table 15-1 Counter description
Counter ID Counter Name Counter Feature ID Feature Name

Description
1526726737 L.ChMeas.PRB.UL Average number of Multi-mode: None Basic Scheduling

.Used.Avg used uplink PRBs GSM: None Basic Scheduling
UMTS: None Adaptive SFN/
LTE: LBFD-002025 SDMA
TDLBFD-002025
LOFD-070205
1526726740 L.ChMeas.PRB.DL Average number of Multi-mode: None Basic Scheduling

.Used.Avg used PDSCH PRBs GSM: None Basic Scheduling
UMTS: None Adaptive SFN/
LTE: LBFD-002025 SDMA
TDLBFD-002025
LOFD-070205
1526728259 L.Thrp.bits.UL Total uplink traffic Multi-mode: None Radio Bearer

volume for PDCP GSM: None Management
PDUs in a cell Radio Bearer
UMTS: None
Management
LTE: LBFD-002008
Basic Scheduling
TDLBFD-002008
Basic Scheduling
LBFD-002025
TDLBFD-002025

eRAN

Description
1526728260 L.Thrp.Time.UL Total receive Multi-mode: None Radio Bearer

duration of uplink GSM: None Management
PDCP PDUs in a Radio Bearer
cell UMTS: None
Management
LTE: LBFD-002008
Basic Scheduling
TDLBFD-002008
Basic Scheduling
LBFD-002025
TDLBFD-002025
1526728261 L.Thrp.bits.DL Total downlink Multi-mode: None Radio Bearer

traffic volume for GSM: None Management
PDCP SDUs in a Radio Bearer
cell UMTS: None
Management
LTE: LBFD-002008
Basic Scheduling
TDLBFD-002008
Basic Scheduling
LBFD-002025
TDLBFD-002025
1526728262 L.Thrp.Time.DL Total transmit Multi-mode: None Radio Bearer

duration of GSM: None Management
downlink PDCP Radio Bearer
SDUs in a cell UMTS: None
Management
LTE: LBFD-002008
Basic Scheduling
TDLBFD-002008
Basic Scheduling
LBFD-002025
TDLBFD-002025
1526728333 L.Traffic.User.Ulsy Average number of Multi-mode: None RRC Connection

nc.Avg UL synchronized GSM: None Management
users in a cell RRC Connection
UMTS: None
Management
LTE: LBFD-002007
TDLBFD-002007
1526728526 L.HHO.InterFreq.L Number of load- Multi-mode: None Intra-LTE Load

oad.PrepAttOut based inter- GSM: None Balancing
frequency handover Intra-LTE Load
preparation attempts UMTS: None
Balancing
LTE:
LOFD-001032
TDLOFD-001032

eRAN

Description

oad.ExecAttOut based inter- GSM: None Balancing
frequency handover Intra-LTE Load
execution attempts UMTS: None
Balancing
LTE:
LOFD-001032
TDLOFD-001032
1526728528 L.HHO.InterFreq.L Number of Multi-mode: None Intra-LTE Load

oad.ExecSuccOut successful load- GSM: None Balancing
based inter- Intra-LTE Load
frequency handover UMTS: None
Balancing
executions LTE:
LOFD-001032
TDLOFD-001032
1526729559 L.HHO.InterFreq.U Number of user- Multi-mode: None Intra-LTE Load

eNumLoad.Pre- number-load-based GSM: None Balancing
pAttOut inter-frequency Intra-LTE Load
handover UMTS: None
Balancing
preparation attempts LTE:
LOFD-001032
TDLOFD-001032

eNumLoad.Exe- number-load-based GSM: None Balancing
cAttOut inter-frequency Intra-LTE Load
handover execution UMTS: None
Balancing
attempts LTE:
LOFD-001032
TDLOFD-001032
1526729561 L.HHO.InterFreq.U Number of Multi-mode: None Intra-LTE Load

eNumLoad.Exe- successful user- GSM: None Balancing
cSuccOut number-load-based Intra-LTE Load
inter-frequency UMTS: None
Balancing
handover executions LTE:
LOFD-001032
TDLOFD-001032
1526729590 L.HHO.InterFddTd Number of load- Multi-mode: None Intra-LTE Load

d.Load.PrepAttOut based inter-duplex- GSM: None Balancing
mode handover Intra-LTE Load
Balancing
LTE:
LOFD-001032
TDLOFD-001032

eRAN

Description
1526729591 L.HHO.InterFddTd Number of load- Multi-mode: None Intra-LTE Load

d.Load.ExecAttOut based inter-duplex- GSM: None Balancing
mode handover Intra-LTE Load
execution attempts UMTS: None
Balancing
LTE:
LOFD-001032
TDLOFD-001032
1526729592 L.HHO.InterFddTd Number of Multi-mode: None Intra-LTE Load

d.Load.ExecSucc- successful load- GSM: None Balancing
Out based inter-duplex- Intra-LTE Load
mode handover UMTS: None
Balancing
executions LTE:
LOFD-001032
TDLOFD-001032
1526729593 L.HHO.InterFddTd Number of user- Multi-mode: None Intra-LTE Load

d.UeNumLoad.Pre- number-load-based GSM: None Balancing
pAttOut inter-duplex-mode Intra-LTE Load
handover UMTS: None
Balancing
LOFD-001032
TDLOFD-001032
1526729594 L.HHO.InterFddTd Number of user- Multi-mode: None Intra-LTE Load

d.UeNumLoad.Exe- number-load-based GSM: None Balancing
cAttOut inter-duplex-mode Intra-LTE Load
handover execution UMTS: None
Balancing
attempts LTE:
LOFD-001032
TDLOFD-001032
1526729595 L.HHO.InterFddTd Number of Multi-mode: None Intra-LTE Load

d.UeNumLoad.Exe- successful user- GSM: None Balancing
cSuccOut number-load-based Intra-LTE Load
inter-duplex-mode UMTS: None
Balancing
handover executions LTE:
LOFD-001032
TDLOFD-001032

eRAN

Description
1526729877 L.RRCRel.load.Ded Number of times Multi-mode: None Intra-LTE Load

icatedPri.LTE.High that the E-UTRAN GSM: None Balancing
network is Intra-LTE Load
configured as the UMTS: None
Balancing
highest frequency LTE:
priority in an LOFD-001032
IMMCI IE TDLOFD-001032
Triggered Because
of High Load
1526729900 L.HHO.NCell.Prep Number of load- Multi-mode: None Intra-LTE Load

AttOut.Load based outgoing GSM: None Balancing
handover attempts Intra-LTE Load
between two UMTS: None
Balancing
specific cells LTE:
LOFD-001032
TDLOFD-001032
1526729901 L.HHO.NCell.Exec Number of load- Multi-mode: None Intra-LTE Load

AttOut.Load based outgoing GSM: None Balancing
handover executions Intra-LTE Load
between two UMTS: None
Balancing
specific cells LTE:
LOFD-001032
TDLOFD-001032
1526729902 L.HHO.NCell.Exec Number of load- Multi-mode: None Intra-LTE Load

SuccOut.Load based successful GSM: None Balancing
outgoing handovers Intra-LTE Load
between two cells UMTS: None
Balancing
LTE:
LOFD-001032
TDLOFD-001032
1526730526 L.InterFreq.Load.M Number of times the Multi-mode: None Intra-LTE Load

eas.Num.Cell eNodeB delivers the GSM: None Balancing
load-triggered inter- Intra-LTE Load
frequency UMTS: None
Balancing
measurement LTE:
configuration to a LOFD-001032 Intra-LTE User
UE Number Load
TDLOFD-001032 Balancing
LOFD-070215 Intra-LTE User
TDLOFD-070215 Number Load
Balancing

eRAN

Description
1526730527 L.InterFreq.Load.M Number of times the Multi-mode: None Intra-LTE Load

easSucc.Num.Cell load-triggered inter- GSM: None Balancing
frequency Intra-LTE Load
measurement is UMTS: None
Balancing
successful LTE:
Number Load
Balancing
1526730528 L.InterFreq.HighLo Duration in which a Multi-mode: None Intra-LTE Load

ad.Dur.Cell cell with inter- GSM: None Balancing
frequency load Intra-LTE Load
balancing enabled is UMTS: None
Balancing
in the high-load state LTE:
Number Load
Balancing
1526730529 L.InterFreq.HighLo Number of times a Multi-mode: None Intra-LTE Load

ad.Num.Cell cell with inter- GSM: None Balancing
frequency load Intra-LTE Load
balancing enabled UMTS: None
Balancing
enters from the low- LTE:
load state to the LOFD-001032 Intra-LTE User
high-load state Number Load
Balancing

oad.PrepAttOut.PL based inter- GSM: None Balancing
MN frequency handover Intra-LTE Load
Balancing
for a specific LTE:
operator LOFD-001032
TDLOFD-001032

eRAN

Description

oad.ExecAttOut.PL based inter- GSM: None Balancing
MN frequency handover Intra-LTE Load
executions for a UMTS: None
Balancing
specific operator LTE:
LOFD-001032
TDLOFD-001032
1526730585 L.HHO.InterFreq.L Number of Multi-mode: None Intra-LTE Load

oad.ExecSuccOut.P successful load- GSM: None Balancing
LMN based inter- Intra-LTE Load
frequency UMTS: None
Balancing
handovers for a LTE:
specific operator LOFD-001032
TDLOFD-001032

eNumLoad.PrepAtt number-load-based GSM: None Balancing
Out.PLMN inter-frequency Intra-LTE Load
handover UMTS: None
Balancing
for a specific LOFD-001032
operator TDLOFD-001032

eNumLoad.ExecAtt number-load-based GSM: None Balancing
Out.PLMN inter-frequency Intra-LTE Load
handover executions UMTS: None
Balancing
for a specific LTE:
operator LOFD-001032
TDLOFD-001032
1526730588 L.HHO.InterFreq.U Number of Multi-mode: None Intra-LTE Load

eNumLoad.ExecSu successful user- GSM: None Balancing
ccOut.PLMN number-load-based Intra-LTE Load
inter-frequency UMTS: None
Balancing
handovers for a LTE:
specific operator LOFD-001032
TDLOFD-001032
1526730589 L.Traffic.User.Ulsy Average number of Multi-mode: None Intra-LTE Load

nc.Avg.PLMN UL synchronized GSM: None Balancing
users for a specific Intra-LTE Load
operator in a cell UMTS: None
Balancing
LTE:
LOFD-001032
TDLOFD-001032

eRAN
Description 16 Glossary
16 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
Description 17 Reference Documents
17 Reference Documents
1. 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User

Equipment (UE) procedures in idle mode"
2. 3GPP TS 36.314: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1
Application Protocol (S1AP)"
3. 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
Control (RRC); Protocol specification"
4. 3GPP TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2
Application Protocol (X2AP)"
5. CS Fallback Feature Parameter Description
6. Inter-RAT Mobility Management in Connected Mode Feature Parameter Description
7. Intra-RAT Mobility Management in Connected Mode Feature Parameter Description
8. Multiple Frequency Band Indicator Feature Parameter Description
9. Transport Resource Management Feature Parameter Description


Intra-RAT Mobility Load Balancing (ERAN8 1 - 01)

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

Intra-RAT Mobility Load Balancing (ERAN8 1 - 01)

Uploaded by

Copyright:

Available Formats

eRAN

Intra-RAT Mobility Load Balancing

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2015-03-23) Huawei Proprietary and Confidential i

1 About This Document..................................................................................................................1

Issue 01 (2015-03-23) Huawei Proprietary and Confidential ii

5.2.2.3 Final Candidate Cell Selection...............................................................................................................................27

6 PRB-Usage-based Inter-Frequency MLB................................................................................33

7 Operator-Level Inter-Frequency MLB.....................................................................................39

8 Inter-Frequency MLB for Non-Cosited Cells.........................................................................46

10 Transport-QoS-based Inter-Frequency MLB.......................................................................53

Issue 01 (2015-03-23) Huawei Proprietary and Confidential iii

Issue 01 (2015-03-23) Huawei Proprietary and Confidential iv

Issue 01 (2015-03-23) Huawei Proprietary and Confidential v

Issue 01 (2015-03-23) Huawei Proprietary and Confidential vi

1 About This Document

This document covers the following features:

l LOFD-001032 Intra-LTE Load Balancing

This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 1

1.2 Intended Audience

l Need to understand the features described herein

1.3 Change History

Chan Change Description Parameter Change Affected

Featur None None None

Editori Optimized some descriptions None N/A

eRAN8.1 Draft A (2015-01-15)

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 2

Chan Change Description Parameter Change Affected

Modified the load transfer Added the following parameters:

Modified the candidate cell Added the following parameters:

Added LOFD-081227 Intra- Added the following parameters:

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 3

Chan Change Description Parameter Change Affected

Revised the descriptions of the Added the following parameters:

Editori Revised the quality None N/A

Revised the descriptions in the None N/A

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 4

1.4 Differences Between eNodeB Types

LOFD-001032 Intra-LTE Load Yes Yes Yes

LOFD-070215 Intra-LTE User Yes Yes Yes

LOFD-070204 Operator Load Based Yes Yes Yes

LOFD-081227 Intra-LTE Load Yes Yes Yes

LOFD-001057 Load Balancing based No Yes No

Function Implementation in Macro, Micro, and LampSite eNodeBs

Load pre-balancing Micro eNodeBs do not support load pre-balancing in adaptive

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 5

l Relieves load imbalances among inter-frequency cells by transferring appropriate UEs to

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 6

Table 2-1 lists the usage scenario of each MLB function.

Table 2-1 Usage scenarios of MLB functions

Function UEs to Applicab Intra- or Inter- Applicabl Support

User-number- RRC_REL Macro, Intra- and inter- No Yes

UL-sync Macro, Intra- and inter- Yes Yes

PRB-usage- UL-sync Macro, Intra- and inter- Yes Yes

Load pre- RRC_REL Macro, Intra- and inter- Yes No

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 7

Function UEs to Applicab Intra- or Inter- Applicabl Support

Load pre- RRC_REL Macro and Intra-eNodeB N/A No