MLB Lte Load Control Mechanismm

eRAN
MLB Feature Parameter Description
Issue 04
Date 2013-10-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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 04 (2013-10-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
MLB Feature Parameter Description Contents
Contents
1 About This Document..................................................................................................................1

1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................1
1.3 Change History...............................................................................................................................................................1
2 Overview.........................................................................................................................................4
2.1 Basic Concepts...............................................................................................................................................................5
2.1.1 Cell Load.....................................................................................................................................................................5
2.1.2 Service Type................................................................................................................................................................5
2.1.3 Source Cell and Target Cell.........................................................................................................................................6
2.2 MLB Procedure..............................................................................................................................................................6
3 Inter-Frequency Load Balancing................................................................................................8

3.1 Load Measurement and Evaluation................................................................................................................................9
3.2 Load Information Exchange...........................................................................................................................................9
3.2.1 Neighboring Cell Selection.........................................................................................................................................9
3.2.2 Inter-eNodeB Cell Load Information Exchange........................................................................................................10
3.3 Load Balancing Decision..............................................................................................................................................10
3.4 Load Balancing Execution............................................................................................................................................11
3.5 Performance Monitoring...............................................................................................................................................12
4 Inter-RAT Load Sharing.............................................................................................................13

4.1 Load Measurement and Evaluation..............................................................................................................................14
4.2 Load Sharing Decision.................................................................................................................................................14
4.3 Load Sharing Execution...............................................................................................................................................14
4.3.1 Transferring UEs in Connected Mode.......................................................................................................................15
4.3.2 Transferring UEs in Idle Mode..................................................................................................................................16
5 Related Features...........................................................................................................................17
5.1 Features Related to LOFD-001032 Intra-LTE Load Balancing...................................................................................17
5.2 Features Related to LOFD-001044 Inter-RAT Load Sharing to UTRAN...................................................................17
5.3 Features Related to LOFD-001045 Inter-RAT Load Sharing to GERAN...................................................................18
6 Network Impact...........................................................................................................................19
Issue 04 (2013-10-30) Huawei Proprietary and Confidential ii

eRAN
MLB Feature Parameter Description Contents
6.1 LOFD-001032 Intra-LTE Load Balancing...................................................................................................................19

6.2 LOFD-001044 Inter-RAT Load Sharing to UTRAN...................................................................................................19
6.3 LOFD-001045 Inter-RAT Load Sharing to GERAN...................................................................................................20
7 Engineering Guidelines.............................................................................................................21
7.1 When to Use MLB........................................................................................................................................................21
7.2 Required Information...................................................................................................................................................21
7.3 Planning........................................................................................................................................................................21
7.3.1 RF Planning...............................................................................................................................................................21
7.3.2 Network Planning......................................................................................................................................................22
7.3.3 Hardware Planning....................................................................................................................................................22
7.4 Deployment..................................................................................................................................................................22
7.4.1 Requirements.............................................................................................................................................................22
7.4.2 Data Preparation........................................................................................................................................................22
7.4.3 Precautions.................................................................................................................................................................32
7.4.4 Activation..................................................................................................................................................................32
7.4.5 Activation Observation..............................................................................................................................................36
7.4.6 Deactivation...............................................................................................................................................................44
7.6 Parameter Optimization................................................................................................................................................47
7.7 Troubleshooting............................................................................................................................................................47
8 Parameters.....................................................................................................................................50
9 Counters......................................................................................................................................105
10 Glossary.....................................................................................................................................108
11 Reference Documents.............................................................................................................109
Issue 04 (2013-10-30) Huawei Proprietary and Confidential iii

eRAN
MLB Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes 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-001044 Inter-RAT Load Sharing to UTRAN
l LOFD-001045 Inter-RAT Load Sharing to GERAN
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.
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, which are defined as follows:
l Feature change
Changes in features of a specific product version
l Editorial change
Issue 04 (2013-10-30) Huawei Proprietary and Confidential 1

eRAN
Changes in wording or addition of information that was not described in the earlier version
04 (2013-10-30)
This issue includes the following changes.
Change Type Change Description Parameter Change
Feature change None None
Editorial change Revised 3.4 Load Balancing Execution and None

4.3.1 Transferring UEs in Connected
Mode.
03 (2013-08-30)
Feature change In inter-RAT load sharing to UTRAN, deleted None

the exchange of load information about
neighboring UTRAN cells through RAN
Information Management (RIM) procedures.
Editorial change None None
02 (2012-05-31)
Editorial change Optimized some descriptions in 7.4.2 Data None

Preparation and 7.4.4 Activation.
01 (2013-04-28)

eRAN
Editorial change Optimized the descriptions of None

types of services that trigger
inter-frequency load
balancing and inter-RAT
load sharing. For details, see
3 Inter-Frequency Load
Balancing and 4 Inter-RAT
Load Sharing.
Draft A (2013-01-30)
Compared with Issue 05 (2012-12-29) of eRAN3.0, Draft A (2013-01-30) of eRAN6.0 includes
the following changes.
Change Change Description Parameter Change

Type
Feature In inter-RAT load sharing to Added the MlbLoadInfoSwitch

change UTRAN, added the exchange of (MlbLoadInfoSwitch) option to the
load information about CellAlgoSwitch.MlbAlgoSwitch
neighboring UTRAN cells parameter.
through RIM procedures.
Removed intra-frequency load Removed the parameters for intra-

balancing. frequency load balancing.
Added the switches of blind Added the CellAlgoSwitch.MlbHoMode

handover for inter-frequency parameter.
and inter-RAT MLB. For
details, see 3.4 Load Balancing
Execution and 4.3.1
Transferring UEs in
Connected Mode.
Added the configuration of the Added the CellMLB.LoadTransferFac-

number of UEs that can be tor parameter.
transferred in an MLB period.
For details, see 3.4 Load
Balancing Execution.
Editorial Revised the description of inter- None

change RAT load sharing.

eRAN
MLB Feature Parameter Description 2 Overview
2 Overview
Mobility load balancing (MLB) coordinates load distribution among inter-frequency cells to
maximize network resource usage. To achieve these goals, MLB checks the load status of cells,
exchanges cell load information, and transfers load from heavily loaded cells to lightly loaded
cells. In addition, MLB can transfer load to inter-RAT cells to reduce the E-UTRAN congestion
rate, increase the access success rate, and improve user experience with services.
NOTE
RAT is short for radio access technology.
MLB can be classified into inter-frequency load balancing and inter-RAT load sharing.
MLB involves the following optional features:
l LOFD-001032 Intra-LTE Load Balancing

l LOFD-001044 Inter-RAT Load Sharing to UTRAN
l LOFD-001045 Inter-RAT Load Sharing to GERAN

eRAN
2.1 Basic Concepts
2.1.1 Cell Load

MLB considers the following types of loads: air interface load, hardware load, and transport
network layer load, as shown in Figure 2-1.
Figure 2-1 Different types of loads and their positions
l The air interface load is represented by the uplink (UL) and DL PRB usages in each cell.
For details about how to calculate the PRB usage, see section 4.1.1 in 3GPP TS 36.314
V10.2.0 (2011-09).
l The hardware load is represented by the hardware resource usage, such as the central
processing unit (CPU) and digital signal processing (DSP) hardware usage.
l The transport network layer load is represented by the S1 bandwidth usage. For details, see
Transport Resource Management Feature Parameter Description.
According to section 9.2.36 in 3GPP TS 36.423 V10.5.0 (2012-03), the hardware and transport
network layer loads can be in one of the following states: LowLoad, MediumLoad, HighLoad,
and Overload.
3900 series eNodeBs currently support only MLB triggered by the air interface load.
In RAN sharing scenarios, cell load is measured on a per cell basis, not on a per operator basis.
NOTE
For concepts related to RAN sharing, see RAN Sharing Feature Parameter Description.
2.1.2 Service Type

Services are categorized into guaranteed bit rate (GBR) services and non-GBR services in the
uplink and downlink. The GBR services and non-GBR services combined are referred to as total

eRAN
services. In MLB, the eNodeB determines the load balancing type based on the percentage of
resources occupied by each type of service.
2.1.3 Source Cell and Target Cell

A source cell is the cell from which MLB transfers the load. In this document, a source cell is
also referred to as a serving cell.
A target cell is a neighboring cell to which MLB transfers the load.
2.2 MLB Procedure

MLB can be performed between inter-frequency and inter-RAT cells. A cell can be configured
with one or both of the two types of neighboring cells. When both types are configured, the type
of neighboring cells to which the load should be transferred is determined by the settings of the
associated switches and MLB thresholds. If the switches for both of them are turned on, the two
types of MLB can coexist. It is recommended that the threshold for inter-frequency load
balancing be set to a smaller value than the threshold for inter-RAT load sharing so that inter-
frequency load balancing takes precedence over inter-RAT load sharing. Load balancing may
be triggered by an overload in the uplink or downlink. For details about how to configure MLB,
see 7 Engineering Guidelines.
The MLB procedure consists of the following steps:
1. Load measurement and evaluation

The eNodeB periodically measures the resources occupied by the uplink and downlink
GBR services and non-GBR services. Based on these measurement results, the eNodeB
evaluates the cell load.
2. Load information exchange (only applicable to inter-frequency load balancing)
If an MLB switch is turned on for a cell, the cell initiates a resource status request towards
its neighboring cells when the uplink and downlink loads of the cell meet the MLB
triggering condition. In this scenario, the cell exchanges the load information with its
neighboring cells.
3. MLB decision
l For inter-frequency load balancing, the eNodeB selects the best candidate cell as the
target cell. The selection is based on the load difference between the serving cell and
the candidate cells and the historical statistics on the performance of handovers from
the serving cell to the candidate cells.
l The eNodeB determines whether to perform load sharing with UTRAN or GERAN
based on the MLB switch settings on the eNodeB. If the switches for load sharing with
UTRAN and GERAN are turned on, the eNodeB may select UEs for load sharing to
UTRAN or GERAN neighboring cells.
4. MLB execution
After the target cell for MLB is determined, the serving cell selects several UEs to transfer.
The transfer method may be handover or cell reselection. If UEs do not support inter-RAT
handover, the serving cell transfers UEs using redirections.
5. Performance monitoring and adjustment

eRAN
After executing MLB, the eNodeB monitors the performance of the source and target cells.
The performance serves as a basis for the next selection of a target cell for MLB.

eRAN
MLB Feature Parameter Description 3 Inter-Frequency Load Balancing
3 Inter-Frequency Load Balancing
This chapter describes the optional feature LOFD-001032 Intra-LTE Load Balancing.
Inter-frequency load balancing transfers some UEs in connected mode to balance load between
inter-frequency neighboring cells. This feature applies to inter-frequency cells with the same
coverage or with a large proportion of overlapping coverage. Therefore, inter-frequency load
balancing takes into consideration all the UEs in connected mode in a cell.
Inter-frequency load balancing is enabled if the InterFreqMlbSwitch(InterFreqMlbSwitch)

option of the CellAlgoSwitch.MlbAlgoSwitch parameter is selected.
The following sections describe the procedure for inter-frequency load balancing.

eRAN
3.1 Load Measurement and Evaluation

The eNodeB periodically measures cell resources in use and compares the result with the
specified MLB threshold.
Load information exchange is triggered for inter-frequency load balancing if the air interface
load of a cell is consistently equal to or greater than the sum of CellMLB.InterFreqMlbThd
(the threshold above which inter-frequency load balancing is started) and
CellMLB.LoadOffset.
Load balancing is preferentially triggered by GBR services, then by total services. If the PRB
usage of GBR services is greater than the specified threshold, load balancing is triggered by
GBR services. If the PRB usage of GBR services is less than the specified threshold but the PRB
usage of total services is greater than the specified threshold, load balancing is triggered by total
services. Services that trigger load balancing are treated separately in the uplink and downlink.
Load offset is used to prevent load fluctuations from frequently triggering and stopping load
balancing.
Load information exchange is stopped if the PRB usage of the serving cell is consistently less
than the value of CellMLB.InterFreqMlbThd .
3.2 Load Information Exchange

If the cell has at least one inter-frequency neighboring cell under the same eNodeB, the eNodeB
will perform inter-frequency load balancing only to these intra-eNodeB inter-frequency
neighboring cells. The serving cell can acquire the load status of these cells directly (not through
the X2 interface) before making a load balancing decision.
If the cell does not have any inter-frequency neighboring cells under the same eNodeB, the
serving cell initiates a resource status request towards the neighboring cells on a specified list
to exchange load information. The load information consists of the air interface, hardware, and
transport network layer loads. The air interface load is represented by the total PRB usage, PRB
usage of GBR services, and PRB usage of non-GBR services in the uplink or downlink in each
cell.
NOTE
Inter-eNodeB cells exchange load information through the X2 interface. If the X2 interface is not
configured, load information cannot be exchanged between the cells, and therefore the subsequent activities
are not performed.
3.2.1 Neighboring Cell Selection

All inter-frequency neighboring cells can be candidate cells. After filtering out certain cells, the
eNodeB generates a list of neighboring cells for load information exchange. The following are
examples of cells that the eNodeB filters out:
l Cells under a neighboring eNodeB to which the local eNodeB is not connected through an
X2 interface
l Cells with a handover success rate less than 98%

eRAN
l Cells for which the EutranInterFreqNCell.NoHoFlag parameter is set to

FORBID_HO_ENUM(Forbid Ho)
3.2.2 Inter-eNodeB Cell Load Information Exchange

After determining the inter-eNodeB cells with which the serving cell can exchange load
information, the eNodeB sends a RESOURCE STATUS REQUEST message to all the eNodeBs
to which the inter-eNodeB cells belong. The message contains the IDs of the inter-eNodeB cells
whose load information is requested and the interval at which the cell load information should
be reported. For details, see section 8.3.6 in 3GPP TS 36.423 V10.5.0 (2012-03).
The serving cell requests all candidate cells to report their load information. If the serving cell
receives a RESOURCE STATUS RESPONSE message from a neighboring cell, the serving cell
will periodically receive subsequent RESOURCE STATUS UPDATE messages from that
neighboring cell. If the serving cell receives a RESOURCE STATUS FAILURE message from
a neighboring cell, the neighboring cell is not considered a qualified candidate for load balancing
at present.
NOTE
If a neighboring cell stops reporting RESOURCE STATUS UPDATE messages after several reports, the
cell is not considered as a candidate cell at present.
3.3 Load Balancing Decision

The eNodeB generates a target cell list for inter-frequency load balancing based on the load
differences between the cells, handover performance, and the load information exchange results.
After load information exchange, the eNodeB derives a preliminary candidate cell list based on
factors such as cell bandwidth differences and the uplink or downlink resources occupied by
GBR and total services. Then, the eNodeB generates a target cell list 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%.
l The TNL load or hardware load of the neighboring cell is in the HighLoad or Overload
state.
l Between the neighboring and serving cells, services in the uplink or downlink that trigger
load balancing is less than the value of CellMLB.LoadDiffThd.
If the target cell list is empty, the eNodeB stops load balancing for the serving cell.
NOTE
In RAN sharing scenarios, a neighboring cell can be the target cell regardless of whether the cell operates
in RAN sharing with common carriers mode or in RAN sharing with dedicated carriers mode.
It is recommended that the CellMLB.InterFreqMlbThd parameter be set to the same value throughout the
network.
The target cell may be so heavily loaded that load balancing from the target cell to other cells is also
triggered in the same direction (uplink or downlink) as load balancing from the source cell. In this situation,
load balancing from the source cell to the target cell is still performed as long as the target cell meets the
load balancing condition.

eRAN
3.4 Load Balancing Execution

Inter-frequency load balancing involves only UEs in connected mode. The eNodeB selects some
UEs that do not support carrier aggregation (called non-CA UEs) based on the frequency
information about the target cells, frequency capabilities of UEs, PRB usage in the target cells,
and type of services that trigger load balancing in the serving cell. Then, the eNodeB instructs
the UEs to transfer to the target cells. If load balancing is triggered by GBR services, the eNodeB
selects the UEs that are performing GBR services. If the load balancing is triggered by total
services, the eNodeB selects UEs that are performing non-GBR services.
In addition, the eNodeB considers both the uplink and downlink PRB usages of UEs during UE
selection for load balancing. That is, the uplink and downlink PRB usages of the UEs that are
selected by the eNodeB must meet certain conditions. This prevents ping-pong load balancing
in the transmission direction opposite to the MLB-triggering direction after the UEs are
transferred to the neighboring cell. If uplink or downlink PRB usage of the selected UEs is too
large, load balancing is likely to be triggered in the uplink or downlink of the target cell. If the
uplink or downlink PRB usage of the selected UEs is too small, the load of the source cell may
not be reduced in time.
For example, if load balancing is triggered by GBR services in the downlink, the eNodeB selects
the UEs that meet the following conditions for load balancing:
l The PRB usage of downlink GBR services is greater than 2% and less than or equal to half
of the value of the CellMLB.LoadDiffThd parameter.
l The PRB usage of uplink GBR services is less than or equal to 2%.
This prevents load balancing triggered by GBR services in the uplink after the UEs are transferred
to the neighboring cell.
In inter-frequency load balancing, there are two methods to transfer UEs that support inter-
frequency handover: blind handover and measurement-based handover. Measurement-based
handovers work by default, and in this case it is required that the RSRP of target inter-frequency
cells must be greater than the value of the
InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrp parameter. Blind handovers work
only if the InterFreqMlbBlindHo(InterFreqMlbBlindHo) option of the
CellAlgoSwitch.MlbHoMode parameter is selected.
NOTE
The total number of RBs in a cell used by the UEs to be transferred within an inter-frequency load balancing
process cannot exceed the maximum number, which is calculated based on the PRB usage difference
between the source and target cells and the CellMLB.LoadTransferFactor parameter. A greater PRB
usage difference or a larger value of the CellMLB.LoadTransferFactor parameter produces a larger total
number of RBs in a cell used by the UEs to be transferred within an inter-frequency load balancing process.
A UE is considered as a CA UE regardless of whether the UE is in its secondary serving cell (SCell) or
primary serving cell (PCell).
During inter-frequency load balancing, the serving cell rejects incoming handover requests with
the cause value "Resource optimisation handover".
NOTE
For definitions of the cause values for handover requests, see section 9.2.1.3 in 3GPP TS 36.413 V10.6.0
(2012-06) and section 9.2.6 in 3GPP TS 36.423 V11.1.0 (2012-06).

eRAN
Based on the measurement results reported by the UEs, the eNodeB performs inter-frequency
handovers for UEs that meet the handover conditions. For details about inter-frequency
handovers, see Mobility Management in Connected Mode Feature Parameter Description.
NOTE
The EPC sends an SPID to the eNodeB when a UE accesses the network. The subscriber profile identified
by the SPID includes the mobility and service usage information to which the UE subscribes. The operators'
network plan determines subscriber profiles. For details about SPIDs, see section 8.6.2.2 in 3GPP TS 36.413
V10.6.0 (2012-06) and section 16.1.8 and Annex I in 3GPP TS 36.300 V11.2.0 (2012-06).
The UE will be transferred only to the RATs or frequencies specified in the SPID configuration if the
following conditions are met:
l The UE is to be transferred and the eNodeB has learned the UE's SPID from the EPC.
l The SpidCfg MO corresponding to this SPID has been configured on the eNodeB with the
SpidCfg.InterFreqMlbSwitch parameter set to TRUE(TRUE).
3.5 Performance Monitoring

Self-organizing network (SON) logs record the following information during a load balancing
period:
l Total number of UEs that are handed over to target cells and UEs whose RRC connections
are reestablished with the target cells because of radio link failures during handovers
l Total PRB usage
Operators can query the SON logs for the statistics on load balancing within each period.
The eNodeB monitors the success rate of handovers from the source cell. In the next round of
load measurement and evaluation, the handover success rate is considered as an evaluation
standard for selecting target cells for inter-frequency load balancing.

eRAN
MLB Feature Parameter Description 4 Inter-RAT Load Sharing
4 Inter-RAT Load Sharing
This chapter describes the optional features LOFD-001044 Inter-RAT Load Sharing to
UTRAN and LOFD-001045 Inter-RAT Load Sharing to GERAN.
The decision on inter-RAT load sharing is based on the load of an E-UTRAN cell. If an E-
UTRAN cell becomes heavily loaded, the eNodeB can trigger inter-RAT load sharing based on
UE capabilities, load statistics of the target inter-RAT network, and system performance. After
triggering inter-RAT load sharing, the eNodeB takes one or both of the following actions:
l Transfers some UEs in connected mode to the target cell.

l Instructs some UEs to camp on the target cell after their Radio Resource Control (RRC)
connections are released (when the UEs enter idle mode).
The following sections describe the inter-RAT load sharing procedure.

eRAN
4.1 Load Measurement and Evaluation

The eNodeB periodically measures cell resources in use and compares the result with the
specified MLB threshold.
Inter-RAT load sharing is triggered if both the following conditions are met:
l The cell load is consistently greater than or equal to the sum of
CellMLB.InterRatMlbThd and CellMLB.LoadOffset.
l The number of uplink synchronized UEs in the cell is greater than or equal to
CellMLB.InterRatMlbUeNumThd.
The same rules that determine the service type for triggering inter-frequency load balancing
(described in 3.1 Load Measurement and Evaluation) apply to inter-RAT load sharing.
Inter-RAT load sharing is stopped if the load of the serving cell is consistently less than the value
of CellMLB.InterRatMlbThd or the number of uplink synchronized UEs in the serving cell is
consistently less than the value of CellMLB.InterRatMlbUeNumThd.
4.2 Load Sharing Decision

In inter-RAT load sharing, the eNodeB selects the target RAT based on the MLB switch settings
in the CellAlgoSwitch.MlbAlgoSwitch parameter.
l If the UtranMlbSwitch(UtranMlbSwitch) option of the
CellAlgoSwitch.MlbAlgoSwitch parameter and the UtranPsHoSwitch
(UtranPsHoSwitch) option of the EnodebAlgoSwitch.HoModeSwitch parameter are
selected, the eNodeB will select UEs in connected mode for load sharing to UTRAN cells.
l If the UtranIdleMlbSwitch(UtranIdleMlbSwitch) option of the
CellAlgoSwitch.MlbAlgoSwitch parameter is selected, the eNodeB will select UEs in idle
mode for load sharing to UTRAN cells.
l If the GeranMlbSwitch(GeranMlbSwitch) option of the
CellAlgoSwitch.MlbAlgoSwitch parameter and the GeranPsHoSwitch
(GeranPsHoSwitch) option of the EnodebAlgoSwitch.HoModeSwitch parameter are
selected, the eNodeB will select UEs for load sharing to GERAN cells.
If the switches for load sharing with UTRAN and GERAN are turned on, the eNodeB may select
UEs for load sharing to UTRAN or GERAN neighboring cells.
4.3 Load Sharing Execution

During inter-RAT load sharing, the serving cell rejects incoming handover requests with the
cause value "Resource optimisation handover".
NOTE
For definitions of the cause values for handover requests, see section 9.2.1.3 in 3GPP TS 36.413 V10.6.0
(2012-06) and section 9.2.6 in 3GPP TS 36.423 V11.1.0 (2012-06).
The following sections describe the principles of transferring UEs in connected mode and idle
mode.

eRAN
4.3.1 Transferring UEs in Connected Mode

The eNodeB instructs a number of UEs to perform inter-RAT measurements based on the
information about the target cells, frequencies and RAT capabilities of UEs, PRB usage in the
source cell, and the type of services that trigger load sharing, when either of the following option
combination is selected:
l UtranMlbSwitch(UtranMlbSwitch) of the CellAlgoSwitch.MlbAlgoSwitch parameter
and UtranPsHoSwitch(UtranPsHoSwitch) of the EnodebAlgoSwitch.HoModeSwitch
parameter
l GeranMlbSwitch(GeranMlbSwitch) of the CellAlgoSwitch.MlbAlgoSwitch parameter
and GeranPsHoSwitch(GeranPsHoSwitch) of the EnodebAlgoSwitch.HoModeSwitch
parameter
If load sharing is triggered by GBR services, the eNodeB selects UEs that are performing GBR
services and sends Measurement Configuration messages to these UEs. Alternatively, if load
sharing is triggered by total services, the eNodeB selects UEs that are performing non-GBR
services and sends Measurement Configuration messages to those UEs.
In addition, the eNodeB considers both the uplink and downlink PRB usages of UEs during UE
selection for load sharing. That is, the uplink and downlink PRB usages of the UEs that are
selected by the eNodeB must meet certain conditions. This prevents ping-pong load sharing in
the transmission direction opposite to the MLB-triggering direction after the UEs are transferred
to the neighboring cell. If uplink or downlink PRB usage of the selected UEs is too large, load
sharing is likely to be triggered in the uplink or downlink of the target cell. If the uplink or
downlink PRB usage of the selected UEs is too small, the load of the source cell may not be
reduced in time.
For example, if load sharing is triggered by GBR services in the downlink, the eNodeB selects
the UEs that meet the following conditions for load sharing:
l The PRB usage of downlink GBR services is greater than 2% and less than or equal to half
of the value of the CellMLB.LoadDiffThd parameter.
l The PRB usage of uplink GBR services is less than or equal to 2%.
This prevents load sharing triggered by GBR services in the uplink after the UEs are transferred
to the neighboring cell.
Based on the measurement results reported by the UEs, the eNodeB determines the target UEs
for load sharing. The E-UTRAN cell transfers the selected UEs to the target cell for inter-RAT
load sharing based on inter-RAT handover policies.
In inter-RAT load sharing, there are two methods to transfer UEs that support inter-RAT
handover: blind handover and measurement-based handover. Measurement-based handovers
work by default, and in this case it is required that the received signal code power (RSCP) of
target UTRAN cells for load sharing must be greater than the value of the
InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdEcn0 parameter or the received signal
strength indicator (RSSI) of target GERAN cells for load sharing must be greater than the value
of the InterRatHoGeranGroup.LdSvBasedHoGeranB1Thd parameter. Blind handovers work
only if the InterRatMlbBlindHo(InterRatMlbBlindHo) option of the
CellAlgoSwitch.MlbHoMode parameter is selected. If UEs do not support inter-RAT handover,
the eNodeB transfers UEs by blind redirections.
Handover is the preferred method for the eNodeB to perform load sharing, because the use of
redirection interrupts services. The eNodeB performs load sharing only if handover is enabled.

eRAN
If handover is enabled but the UEs do not support handover, the eNodeB performs redirections
for load sharing.
For details about the description of inter-RAT handover, see Mobility Management in Connected
Mode Feature Parameter Description.
NOTE
The EPC sends an SPID to the eNodeB when a UE accesses the network. The subscriber profile identified
by the SPID includes the mobility and service usage information to which the UE subscribes. The operators'
network plan determines subscriber profiles. For details about SPIDs, see section 8.6.2.2 in 3GPP TS 36.413
V10.6.0 (2012-06) and section 16.1.8 and Annex I in 3GPP TS 36.300 V11.2.0 (2012-06).
The UE will be transferred only to the RATs or frequencies specified in the SPID configuration if the
following conditions are met:
l The UE is to be transferred and the eNodeB has learned the UE's SPID from the EPC.
l The SpidCfg MO corresponding to this SPID has been configured on the eNodeB with the
SpidCfg.InterRatMlbSwitch parameter set to TRUE(TRUE).
4.3.2 Transferring UEs in Idle Mode

If the UtranIdleMlbSwitch(UtranIdleMlbSwitch) option of the
CellAlgoSwitch.MlbAlgoSwitch parameter is selected for an E-UTRAN cell and the E-UTRAN
cell meets the conditions for triggering inter-RAT load sharing, the eNodeB instructs several
UEs that are undergoing RRC connection release procedures to camp on the target UTRAN cell
after their RRC connections are released. The eNodeB delivers the instructions by including the
CellReselectionPriority IE in the RRCConnectionRelease messages to the UEs.
The actual duration of load sharing with UTRAN is calculated based on the value of the
CellMLB.InitValidPeriod parameter and the number of uplink synchronized UEs. The
CellMLB.InitValidPeriod parameter specifies the initial duration of load sharing with UTRAN
for UEs in idle mode, and the actual duration increases with the number of uplink synchronized
UEs. Therefore, the larger the value of the CellMLB.InitValidPeriod parameter or the number
of uplink synchronized UEs, the larger the actual duration of load sharing with UTRAN. Within
the time of actual duration, UEs preferentially camp on neighboring UTRAN cells if the UEs
are to be released after the inactive timer expires.
Load sharing with UTRAN for UEs in idle mode takes effect only if the priorities of the serving
frequency and the neighboring E-UTRAN frequencies of the serving cell are all higher than or
all lower than those of the neighboring UTRAN frequencies of the serving cell.

SON logs record the following information during a load sharing period:
l Number of UEs that are handed over to target cells

l Number of UEs whose RRC connections are reestablished with the target cells because of
radio link failures during handovers
l Total PRB usage
Operators can query the SON logs for the statistics on load sharing within each period.

eRAN
MLB Feature Parameter Description 5 Related Features
5 Related Features
5.1 Features Related to LOFD-001032 Intra-LTE Load

Balancing
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None
5.2 Features Related to LOFD-001044 Inter-RAT Load

Sharing to UTRAN
The Inter-RAT Load Sharing to UTRAN feature depends on LOFD-001019 PS Inter-RAT
Mobility between E-UTRAN and UTRAN.

None
Impacted Features
None

eRAN
MLB Feature Parameter Description 5 Related Features
5.3 Features Related to LOFD-001045 Inter-RAT Load

Sharing to GERAN
The Inter-RAT Load Sharing to GERAN feature depends on LOFD-001020 PS Inter-RAT
Mobility between E-UTRAN and GERAN.

None
Impacted Features
None

eRAN
MLB Feature Parameter Description 6 Network Impact
6 Network Impact
6.1 LOFD-001032 Intra-LTE Load Balancing

System Capacity
The Intra-LTE Load Sharing feature transfers some load from an E-UTRAN cell to intra-RAT
neighboring cells before the source E-UTRAN cell becomes congested, and, therefore, increases
resource usage and system capacity.
Network Performance
The Intra-LTE Load Balancing feature increases the number of intra-LTE handovers.
6.2 LOFD-001044 Inter-RAT Load Sharing to UTRAN

System Capacity
The Inter-RAT Load Sharing to UTRAN feature transfers some load from an E-UTRAN cell to
neighboring UTRAN cells before the source E-UTRAN cell becomes congested, and, therefore,
decreases the E-UTRAN load and improves the user experience of UEs in E-UTRAN. However,
this feature increases the UTRAN load and negatively affects the user experience of UEs in
UTRAN.
Network Performance
The Inter-RAT Load Sharing to UTRAN feature increases the number of inter-RAT handovers
from E-UTRAN to UTRAN and the value of the L.RRC.ConnReq.Att.MoSig counter in the
source cell.

eRAN
MLB Feature Parameter Description 6 Network Impact
6.3 LOFD-001045 Inter-RAT Load Sharing to GERAN

System Capacity
The Inter-RAT Load Sharing to GERAN feature transfers some load from an E-UTRAN cell to
neighboring GERAN cells before the source E-UTRAN cell becomes congested, and, therefore,
decreases the E-UTRAN load and improves the user experience of UEs in E-UTRAN. However,
this feature increases the GERAN load and negatively affects the user experience of UEs in
GERAN.
Network Performance
The Inter-RAT Load Sharing to GERAN feature increases the number of inter-RAT handovers
from E-UTRAN to GERAN and the value of the L.RRC.ConnReq.Att.MoSig counter in the
source cell.

eRAN
MLB Feature Parameter Description 7 Engineering Guidelines
7 Engineering Guidelines
7.1 When to Use MLB

Use inter-frequency load balancing when one of the following conditions is met:
l Inter-frequency cells provide the same coverage.

l Inter-frequency cells have a large proportion of overlapping coverage.
l The coverage of a cell contains that of another inter-frequency cell.
Use inter-RAT load sharing if multi-mode base stations are used or base stations of different
RATs provide contiguous coverage.
7.2 Required Information

Collect the following information:
l Information about each neighboring cell of the cells under the local eNodeB
– Whether information about the neighboring cell is complete
– Whether the neighboring cell has been blacklisted
– Whether the No Handover attribute is set to prohibit handovers to the neighboring cell
l Status of the X2 interfaces with neighboring eNodeBs
l UE capabilities
The proportion of UEs that support inter-frequency or inter-RAT measurements
7.3 Planning
7.3.1 RF Planning
MLB is implemented by handover and reselection. Therefore, the current 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. Pilot pollution occurs if the preambles used by different cells
under one eNodeB conflict.
l Uplink and downlink imbalances are minimized.
7.3.2 Network Planning

N/A
7.3.3 Hardware Planning

N/A
7.4 Deployment
7.4.1 Requirements
There are no requirements for the operating system and transmission networking. Before
deploying MLB, the operator must purchase and activate the licenses for the features listed in
Table 7-1.
Table 7-1 License information for MLB
Feature ID Feature Name License NE Sales Unit

Control Item
Name
LOFD-001032 Intra-LTE Load Intra-LTE Load eNodeB per RRC

Balancing Balancing Connected User
LOFD-001044 Inter-RAT Load Inter-RAT Load eNodeB per RRC

Sharing to Sharing to Connected User
UTRAN UTRAN
LOFD-001045 Inter-RAT Load Inter-RAT Load eNodeB per RRC

Sharing to Sharing to Connected User
GERAN GERAN
7.4.2 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.
There are three types of data sources:

eRAN
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l Network plan (negotiation not required): parameter values planned and set by the operator
l User-defined: parameter values set by users
Required Data
The following table describes the parameters that must be set in the CellMLB managed object
(MO) to configure MLB algorithms.
Parameter Parameter ID Data Source Setting Notes

Name
Load Offset CellMLB. Network plan This parameter specifies an

LoadOffset (negotiation not offset applied to the threshold
required) value for triggering MLB. MLB
is triggered only when the load
is consistently equal to or
greater than the sum of the
threshold and offset values.
This mechanism helps prevent
load fluctuations from
frequently triggering and
stopping MLB.
The recommended value is 8.
Load CellMLB. Network plan This parameter specifies the

Difference LoadDiffThd (negotiation not minimum load difference
Threshold required) between two cells that triggers
MLB. When the load difference
between two cells exceeds the
value of this parameter, the
eNodeB regards the load as
imbalanced and triggers MLB
between the two cells. When the
load difference between these
cells drops below this threshold,
the eNodeB no longer regards
the load as imbalanced and
stops MLB between the cells.
This parameter also specifies
the maximum PRB usage of
UEs selected for inter-RAT load
sharing. The recommended
value is 15.
The following table describes the parameter that must be set in the InterFreqHoGroup MO to
configure inter-frequency handover.

eRAN

Name
Load Based InterFreqHoG Network plan This parameter specifies the

Interfreq RSRP roup. (negotiation not RSRP threshold for event A4
threshold InterFreqLoad required) related to load-based inter-
BasedHoA4Th frequency handover. When the
dRsrp measured RSRP value exceeds
this threshold, event A4 is
reported.
The default value is -103.
The following table describes the parameter that must be set in the InterRatHoUtranGroup
MO to configure inter-RAT handover to UTRAN.

Name
Load Service InterRatHoU- Network plan This parameter specifies the

Based UTRAN tranGroup. (negotiation not RSCP threshold for event B1
EventB1 RSCP LdSvBasedHo required) related to load- or service-based
trigger UtranB1ThdR inter-RAT handover to
threshold scp UTRAN.
d In inter-RAT handover to
UTRAN, this parameter
specifies the requirement for
RSCP of the target UTRAN
cell.
When the measured RSCP
exceeds this threshold, a
measurement report will be
sent.
The recommended value is
-101.
The following table describes the parameters that must be set in the InterRatHoGeranGroup
MO to configure inter-RAT handover to GERAN.

eRAN

Name
Load Service InterRatHoGe Network plan This parameter specifies the

Based Geran ranGroup. (negotiation not RSSI threshold for event B1
EventB1 LdSvBasedHo required) related to load- or service-based
trigger GeranB1Thd inter-RAT handover to
threshold GERAN.
When the measured RSSI
exceeds this threshold, event
B1 will be reported.
The recommended value is
-98.
Scenario-specific Data
Scenario 1: Inter-Frequency Load Balancing
The following table describes the parameters that must be set in the CellAlgoSwitch MO to
enable the inter-frequency load balancing algorithm.
Parameter Name Parameter ID Data Source Setting Notes
Local cell ID CellAlgoSwitch. Network plan This parameter

LocalCellId (negotiation not specifies the local ID
required) of a cell. It uniquely
identifies the cell
within an eNodeB.
The actual value
range is 0 to 17.

eRAN
Load balancing CellAlgoSwitch. Network plan The

algorithm switch MlbAlgoSwitch (negotiation not InterFreqMlbS-
required) witch
(InterFreqMlbS-
witch) check box
under this parameter
specifies whether to
enable the inter-
frequency load
balancing algorithm.
l If
InterFreqMlbS-
witch
(InterFreqMlbS
witch) is
selected, the
algorithm is
enabled.
l If
InterFreqMlbS-
witch
(InterFreqMlbS
witch) is not
selected, the
algorithm is
disabled.
The following table describes the parameters that must be set in the CellMLB MO to configure
the inter-frequency load balancing algorithm.
Parameter Parameter Data Source Setting Notes

Name ID
Local cell ID CellMLB. Network plan This parameter specifies the local
LocalCellId (negotiation not ID of a cell. It uniquely identifies
required) the cell within an eNodeB.
The actual value range is 0 to 17.

eRAN
Parameter Parameter Data Source Setting Notes

Name ID
Inter-Frequency CellMLB. Network plan This parameter specifies the

Mobility Load InterFreqMlb (negotiation not threshold for inter-frequency load
Balancing Thd required) balancing. Inter-frequency load
Threshold balancing is started when the load
exceeds the sum of this threshold
and the load offset. Inter-
frequency load balancing is
stopped when the load drops
below this threshold.
The default value is 60.
It is recommended that this
parameter be set to the same value
throughout the network.
Load Transfer CellMLB. Network plan This parameter specifies the factor
Factor LoadTransfer (negotiation not used to control the amount of load
Factor required) transferred during a single MLB
procedure. The value of this
parameter has an impact on the
efficiency of the MLB algorithm
and the algorithm to prevent ping-
pong load transfer.
A larger value of this parameter
leads to the situation where a
larger amount of load can be
transferred, and a smaller value
leads to the situation where a
smaller amount of load can be
transferred. The recommended
value is 0.
(Optional) The following table describes the parameters that must be set in SpidCfg MOs to
configure SPIDs.
Spid SpidCfg.Spid Network plan This parameter

(negotiation not specifies an SPID.
required) The actual value
range is 1 to 256.

eRAN
RAT frequency SpidCfg. Network plan This parameter

priority indication RatFreqPriorityInd (negotiation not specifies whether to
required) configure a
frequency priority
group.

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

Switch InterFreqMlbS- (negotiation not specifies whether to
witch required) allow inter-
frequency load
balancing for UEs
with the SPID.
l If the parameter is
set to TRUE
(TRUE), inter-
frequency load
balancing is
allowed for UEs
with the SPID.
set to FALSE
(FALSE), inter-
frequency load
balancing is not
allowed for UEs
with the SPID.
This parameter
takes effect only
for UEs that
newly access the
network.
Scenario 2: Inter-RAT Load Sharing
The following table describes the parameters that must be set in the CellAlgoSwitch MO to
enable the inter-RAT load sharing algorithm.

eRAN
Parameter Name Paramete Data Setting Notes

r ID Source
Local cell ID CellAlgoS Network This parameter specifies the local ID of a

witch. plan cell. It uniquely identifies the cell within an
LocalCellI (negotiati eNodeB.
d on not The actual value range is 0 to 17.
required)
Load balancing CellAlgoS Network The UtranMlbSwitch(UtranMlbSwitch)

algorithm switch witch. plan check box under this parameter specifies
MlbAlgoS (negotiati whether to enable load sharing with
witch on not UTRAN for UEs in connected mode.
required) l If UtranMlbSwitch
(UtranMlbSwitch) is selected, the
algorithm is enabled.
l If UtranMlbSwitch
(UtranMlbSwitch) is not selected, the
algorithm is disabled.
The UtranIdleMlbSwitch
(UtranIdleMLBSwitch) check box under
this parameter specifies whether to enable
load sharing with UTRAN for UEs in idle
mode.
l If UtranIdleMlbSwitch
(UtranIdleMLBSwitch) is selected,
the algorithm is enabled.
l If UtranIdleMlbSwitch
(UtranIdleMLBSwitch) is not
selected, the algorithm is disabled.
The GeranMlbSwitch
(GeranMlbSwitch) check box under this
parameter specifies whether to enable load
sharing with GERAN.
l If GeranMlbSwitch
(GeranMlbSwitch) is selected, the
algorithm is enabled.
l If GeranMlbSwitch
(GeranMlbSwitch) is not selected, the
algorithm is disabled.
The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO
to configure the inter-RAT load sharing policy.

eRAN
Parame Parameter ID Data Setting Notes

ter Source
Name
Handov ENodeBAlgoSwi Network If the UtranPsHoSwitch

er Mode tch. plan (UtranPsHoSwitch) or GeranPsHoSwitch
switch HoModeSwitch (negotiation (GeranPsHoSwitch) check box is selected,
not the eNodeB performs inter-RAT load sharing
required) using handovers. If neither of them is not
selected, the eNodeB cannot perform inter-
RAT load sharing using handovers and MLB
is not allowed.
The following table describes the parameters that must be set in the CellMLB MO to configure
the inter-RAT load sharing algorithm.
Param Parameter ID Data Setting Notes

eter Source
Name
Local CellMLB.LocalCellId Network This parameter specifies the local ID of a

cell ID plan cell. It uniquely identifies the cell within an
(negotiat eNodeB.
ion not The actual value range is 0 to 17.
required
)
Inter- CellMLB. Network This parameter specifies the threshold for

RAT InterRatMlbThd plan inter-RAT load sharing. Inter-RAT load
Mobilit (negotiat sharing is triggered if the cell load is
y Load ion not consistently greater than or equal to the
Balanci required sum of CellMLB.InterRatMlbThd and
ng ) CellMLB.LoadOffset and if the number of
Thresh uplink synchronized UEs in the cell is
old greater than or equal to
CellMLB.InterRatMlbUeNumThd. Inter-
RAT load sharing is stopped if the cell load
is consistently less than
CellMLB.InterRatMlbThd or the number
of uplink synchronized UEs in the cell falls
below CellMLB.InterRatMlbUe-
NumThd.
The default value is 75.

eRAN
Param Parameter ID Data Setting Notes

eter Source
Name
UTRA CellMLB. Network This parameter specifies the initial duration

N Idle InitValidPeriod plan for load sharing with UTRAN for UEs in
Mode (negotiat idle mode.
Mobilit ion not A larger value of this parameter leads to the
y Load required situation where more UEs in idle mode are
Balanci ) transferred to UTRAN after the E-UTRAN
ng cell is over loaded. The recommended
Initial value is 10.
Valid
Period
Inter- CellMLB. Network This parameter specifies the threshold for

RAT InterRatMlbUe- plan the number of uplink synchronized UEs
Mobilit NumThd (negotiat used to trigger or stop inter-RAT load
y Load ion not sharing.
Balanci required The actual number of uplink synchronized
ng ) UEs is equal to this threshold multiplied by
Thresh 1000.
old of
UE
number
The following table describes the parameters that must be set in SpidCfg MOs to configure
SPIDs.
Spid SpidCfg.Spid Network plan This parameter

(negotiation not specifies an SPID.
required) The actual value
range is 1 to 256.

priority indication RatFreqPriorityInd (negotiation not specifies whether to
required) configure a
frequency priority
group.

priority group ID RatFreqPriority- (negotiation not uniquely identifies a
GroupId required) frequency priority
group.
The actual value
range is 0 to 255.

eRAN
InterRat Mlb Switch SpidCfg. Network plan This parameter

InterRatMlbSwitch (negotiation not specifies whether to
required) allow inter-RAT load
sharing for UEs with
the SPID.
set to TRUE
(TRUE), inter-
RAT load sharing
is allowed for
UEs with the
SPID.
set to FALSE
(FALSE), inter-
RAT load sharing
is not allowed for
UEs with the
SPID.
This parameter
takes effect only
for UEs that
newly access the
network.
7.4.3 Precautions
Pay attention to the following when deploying MLB in a live network:
l If the switches for inter-frequency load balancing and inter-RAT load sharing are turned
on for a cell and the cell load meets the conditions for starting both types of MLB, the
probabilities of both types are the same because no priorities have been specified for the
different types of MLB.
l Inter-frequency load balancing is recommended in live networks.
7.4.4 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 7-2 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 section "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:

eRAN
l The MOs in Table 7-2 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 7-2 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.
Table 7-2 Parameters for MLB

MO Sheet in the Parameter Group Remarks
Summary Data
File
CellAlgoSw CELLALGOSWIT MlbAlgoSwitch This MO must be

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

InterFreqMlbThd, customized in a list-type
InterRatMlbThd, sheet of the template.
LoadExchangePeriod,
LoadOffset,
LoadDiffThd,
InterRatMlbUe-
NumThd,
InitValidPeriod,
LoadTransferFactor
ENodeBAlg ENODEBALGOS HoModeSwitch This MO must be

oSwitch WITCH customized in a list-type
sheet of the template.
SpidCfg SPIDCFG Spid, InterFreqMlbS- This MO must be

(Optional) witch, InterRatMlbS- customized in a list-type
witch sheet of the template.
CellShutDo CELLSHUTDOW LocalCellId, This MO must be

wn N CellShutdownSwitch, customized in a list-type
(Optional) StartTime, StopTime, sheet of the template.
DlPrbThd,
DlPrbOffset,
UlPrbThd,
UlPrbOffset
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 Choose CME > Advanced > Customize Summary Data File (M2000 client mode), or choose
Advanced > Customize Summary Data File (M2000 client mode), to customize a summary
data file for batch reconfiguration.

eRAN
NOTE
For context-sensitive help on a current task in the client, press F1.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration
Data (M2000 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 listed in Table 7-2 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data (M2000 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.
Step 5 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.
----End
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 7-1, select the eNodeB to which the MOs belong.
Figure 7-1 MO search and configuration window
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.

eRAN
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 (M2000 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

Step 1 Run the MOD CELLMLB command to set the threshold for inter-frequency load balancing.
Step 2 Run the MOD CELLALGOSWITCH command to enable the inter-frequency load balancing
algorithm.
Step 3 (Optional) Run the ADD SPIDCFG command to set an SPID and enable SPID-specific inter-
frequency load balancing. If the SPID already exists, run the MOD SPIDCFG command to
modify the configuration as required.
----End
Scenario 2: Inter-RAT Load Sharing for UEs in Connected Mode
Step 1 Run the MOD ENODEBALGOSWITCH command with the UtranPsHoSwitch

(UtranPsHoSwitch) or GeranPsHoSwitch(GeranPsHoSwitch) check box under the
Handover Mode switch parameter selected.
Step 2 Run the MOD CELLMLB command to set the threshold for inter-RAT load sharing and the
threshold for the number of uplink synchronized UEs.
Step 3 Run the MOD CELLALGOSWITCH command to enable inter-RAT load sharing with
UTRAN for UEs in connected mode or inter-RAT load sharing with GERAN.
Step 4 (Optional) Run the ADD SPIDCFG command to set an SPID and enable SPID-specific inter-
RAT load sharing. If the SPID already exists, run the MOD SPIDCFG command to modify the
configuration as required.
----End
Scenario 3: Inter-RAT Load Sharing for UEs in Idle Mode
Step 1 Run the MOD CELLMLB command to modify the threshold for inter-RAT load sharing, the
threshold for the number of uplink synchronized UEs, and the initial duration for load sharing
with UTRAN for UEs in idle mode.
Step 2 Run the MOD CELLALGOSWITCH command to enable inter-RAT load sharing with
UTRAN for UEs in idle mode.
----End
MML Command Examples


eRAN
MOD CELLMLB: LocalCellId=0, InterFreqMlbThd=60;

MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=InterFreqMlbSwitch-1;
ADD SPIDCFG: Spid=1, RatFreqPriorityInd=NOT_CFG, InterFreqMlbSwitch=TRUE;
Scenario 2: Inter-RAT Load Sharing for UEs in Connected Mode

MOD ENODEBALGOSWITCH: HoModeSwitch=UtranPsHoSwitch-1;
MOD ENODEBALGOSWITCH: HoModeSwitch=GeranPsHoSwitch-1;
MOD CELLMLB: LocalCellId=0, InterRatMlbThd=70, InterRatMlbUeNumThd=15;
MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=UtranMlbSwitch-1;
MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=GeranMlbSwitch-1;
ADD SPIDCFG: Spid=1, RatFreqPriorityInd=NOT_CFG, InterRatMlbSwitch=TRUE;
Scenario 3: Inter-RAT Load Sharing for UEs in Idle Mode

MOD CELLMLB: LocalCellId=0, InterRatMlbThd=70, InterRatMlbUeNumThd=15,
InitValidPeriod=10;
MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=UtranIdleMlbSwitch-1;
7.4.5 Activation Observation
Inter-Frequency Load Balancing

To verify whether inter-frequency load balancing works correctly, perform the following steps:
Step 1 On the M2000 client, choose Monitor > Signaling Trace > Signaling Trace Management.
The Signaling Trace Management window is displayed, as shown in Figure 7-2.
Figure 7-2 Signaling Trace Management window
Step 2 Start RB usage monitoring.

1. In the navigation tree on the left of the Signaling Trace Management window, double-
click Usage of RB Monitoring under LTE > Cell Performance Monitoring.
The Usage of RB Monitoring dialog box is displayed, as shown in Figure 7-3.

eRAN
Figure 7-3 Usage of RB Monitoring dialog box
2. Set the task name, select the eNodeB site, and click Next.
The Usage of RB Monitoring dialog box as shown in Figure 7-4 is displayed.
Figure 7-4 Usage of RB Monitoring dialog box

eRAN
3. Enter the local cell ID and then click Finish.

The RB monitoring task starts for the cell, and the tracing result is displayed as shown in
Figure 7-5.
Figure 7-5 RB usage tracing result
Step 3 Start MLB performance monitoring.

click MLB Monitoring under LTE > Cell Performance Monitoring.
The MLB Monitoring dialog box is displayed, as shown in Figure 7-6.
Figure 7-6 MLB Monitoring dialog box
2. Set the task name, select the eNodeB site, and click Next.
3. Enter the information about a neighboring cell of the local cell to be traced, as shown in
Figure 7-7.

eRAN
Figure 7-7 Entering information about a neighboring cell
4. Click Finish.
The MLB performance monitoring task starts for the local cell, and the monitoring result
is displayed as shown in Figure 7-8. The monitoring result includes the PRB usage of the
cell, the PRB usage of the neighboring cell, and the type of load that triggers MLB in the
local cell.
Figure 7-8 MLB performance monitoring result

eRAN
NOTE
For details about the types of load that trigger MLB, see the related performance monitoring reference.
Step 4 On the M2000 client, start Uu interface tracing.

click Uu Interface Trace under LTE > Application Layer. The Uu Interface Trace
dialog box is displayed as shown in Figure 7-9.
2. Set the task name, select the eNodeB site, and click Next. The Uu Interface Trace dialog
box as shown in Figure 7-10 is displayed.
Figure 7-9 Uu Interface Trace dialog box

eRAN
Figure 7-10 Entering information about a Uu interface tracing task
3. Click Finish.
The Uu interface tracing task starts for the cell, and the tracing result is displayed as shown in
Figure 7-11.

eRAN
Figure 7-11 Uu interface tracing result
Step 5 Start X2 interface tracing in a similar way as Step 4, and check the messages traced over the X2
interface.
NOTE
Load information can be traced on the X2 interface only in inter-eNodeB inter-frequency load balancing.
No load information is exchanged over the X2 interface in intra-eNodeB inter-frequency load balancing.
If the serving cell receives a RESOURCE STATUS RESPONSE message from a neighboring
cell after sending a RESOURCE STATUS REQUEST message to the neighboring cell, and later
periodically receives RESOURCE STATUS UPDATE messages from the neighboring cell,
inter-frequency load balancing has been activated. Figure 7-12 shows an example of the
RESOURCE STATUS REQUEST message.
Figure 7-12 RESOURCE STATUS REQUEST message

eRAN
NOTE
The RESOURCE STATUS REQUEST message contains the IDs (eUTRANcellIdentifier IE) of the cells
whose load information is requested and the interval (reportingPeriodicity IE) at which the cell load
information needs to be reported.
Step 6 Use UE1 to access the local cell in the cell center, and use UE2 to access the cell at a place where
UE2 can receive signals from an inter-frequency neighboring cell with RSRP greater than
InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrp.
Step 7 (This step simulates downlink overload in a 10 MHz cell as an example.) Inject downlink UDP
packets for UE1 until the M2000 client shows that the RB usage exceeds the sum of Inter-
Frequency Mobility Load Balancing Threshold and Load Offset. Inject downlink UDP
packets at a rate of 2 Mbit/s for at least 1 minute.
Step 8 Check for an RRC_CONN_RECFG message in the Uu interface tracing result and a
HANDOVER_REQUEST message in the X2 interface tracing result.
If the HANDOVER_REQUEST message containing the handover cause of "reduce-load-in-

serving-cell" exists, inter-frequency load sharing is working correctly. For details about the
signaling procedure, see the description of a successful inter-frequency handover in Mobility
Management in Connected Mode Feature Parameter Description.
----End
To use SON logs to verify whether MLB takes effect, perform the following steps:
Step 1 On the M2000 client, choose SON > SON Log.
Step 2 On the Query SON Log tab page, choose MLB Log from the Log Category drop down list in
the upper left corner, and click Inter-Frequency Handover Statistics under Event Name.
Then, click Query to query SON logs. From the logs, check whether the feature is working
correctly.
You can view only the SON logs that were generated at least one day ago.
----End
Inter-RAT Load Sharing for UEs in Connected Mode

To verify whether inter-RAT load sharing for UEs in connected mode works correctly, perform
the following steps:
Step 1 On the M2000 client, start Uu interface tracing, S1 interface tracing, and RB usage monitoring.
For details about how to start these three tasks, see Inter-Frequency Load Balancing earlier
in this section.
Step 2 Use UE1 to access a cell in the cell center, and use UE2 to access the cell at a place where UE2
can receive signals from an inter-RAT neighboring cell with the radio signal greater than the
trigger thresholds for load- and service-based event B1. In addition, ensure that the number of
uplink synchronized UEs in the cell is greater than or equal to the Inter-RAT Mobility Load
Balancing UE Number Threshold value.
packets for UE1 until the M2000 client shows that the RB usage exceeds the sum of Inter-RAT

eRAN
Mobility Load Balancing Threshold and Load Offset. Inject downlink UDP packets for UE2
at a rate of 2 Mbit/s.
Step 4 Check for an S1AP_HANDOVER_REQUIRED message in the S1 interface tracing result.
If the S1AP_HANDOVER_REQUIRED message containing the cause value "reduce-load-in-
serving-cell" exists, inter-RAT load sharing for UEs in connected mode is working correctly.
----End
To use SON logs to verify whether MLB takes effect, perform the following steps:
Step 1 On the M2000 client, choose SON > SON Log.
Step 2 On the Query SON Log tab page, choose MLB Log from the Log Category drop down list in
the upper left corner, and click Inter-RAT Handover Statistics under Event Name. Then, click
Query to query SON logs. From the logs, check whether the feature is working correctly.
----End
Inter-RAT Load Sharing with UTRAN for UEs in Idle Mode

To verify whether inter-RAT load sharing for UEs in idle mode works correctly, perform the
following steps:
Step 1 On the M2000 client, start Uu interface tracing, S1 interface tracing, and RB usage monitoring.
For details about how to start these three tasks, see Inter-Frequency Load Balancing earlier
in this section.
Step 2 Use UE1 to access a cell in the cell center, and use UE2 to access the cell at a place where UE2
can receive signals from an inter-RAT neighboring cell with a signal level higher than the cell-
reselection threshold. In addition, ensure that the number of uplink synchronized UEs in the cell
is greater than or equal to the Inter-RAT Mobility Load Balancing UE Number Threshold
value.
packets for UE2 at a rate of 2 Mbit/s. Inject downlink UDP packets for UE1 until the M2000
client shows that the RB usage exceeds the sum of Inter-RAT Mobility Load Balancing
Threshold and Load Offset. Stop injecting downlink UDP packets for UE2. Wait until its
inactivity timer expires, so that UE2 enters idle mode. Check whether the RB usage exceeds the
sum of Inter-RAT Mobility Load Balancing Threshold and Load Offset.
If UE2 enters idle mode within the configured initial duration, the reselection priority contained
in the RRC_CONN_REL message in the Uu interface tracing result meets the requirements, and
UE2 is successfully transferred to the UTRAN cell, inter-RAT load sharing is working correctly.
For details about the reselection priority, see 4.3.2 Transferring UEs in Idle Mode.
----End
7.4.6 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

eRAN
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 7-3.
Table 7-3 Parameters for MLB
MO Sheet in the Parameter Setting Notes

Summary Data Group
File
CELLALG CELLALGOSWI MlbAlgoSwitc Turn off the related load balancing

OSWITCH TCH h switch.
Using the CME to Perform Single Configuration

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

Run the MOD CELLALGOSWITCH command to disable the inter-frequency load balancing
algorithm.
Run the MOD CELLALGOSWITCH command to disable inter-RAT load sharing with
UTRAN for UEs in connected or idle mode or inter-RAT load sharing with GERAN.
MML Command Examples

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

MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=UtranMlbSwitch-0;
MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=UtranIdleMlbSwitch-0;
MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=GeranMlbSwitch-0;

Table 7-4 lists the counters used to monitor inter-frequency MLB performance. They can be
used to calculate the proportion of load-based inter-frequency handovers to total inter-frequency
handovers in a cell.

eRAN
Table 7-4 Performance counters related to inter-frequency MLB
Counter Name Description
L.HHO.InterFreq.Load.PrepAttOut Number of inter-frequency handover preparation

attempts triggered because of high load
L.HHO.InterFreq.Load.ExecAtt- Number of inter-frequency handover execution

Out attempts triggered because of high load
L.HHO.InterFreq.Load.ExecSucc- Number of successful inter-frequency handovers

Out triggered because of high load
Table 7-5 lists the counters used to monitor inter-RAT load sharing performance.
Table 7-5 Performance counters related to inter-RAT MLB
Description Counter Name
L.IRATHO.E2W.Load.PrepAtt- Number of EUTRAN-to-WCDMA handover preparation

L.IRATHO.E2W.Load.ExecAtt- Number of EUTRAN-to-WCDMA handover execution

L.IRATHO.E2W.Load.Exe- Number of successful EUTRAN-to-WCDMA handover

cSuccOut executions triggered because of high load
L.IRATHO.E2G.Load.PrepAtt- Number of EUTRAN-to-GERAN handover preparation

L.IRATHO.E2G.Load.ExecAtt- Number of EUTRAN-to-GERAN handover execution

L.IRATHO.E2G.Load.Exe- Number of successful EUTRAN-to-GERAN handover

cSuccOut executions triggered because of high load
L.RRCRedirection.E2W.Load Number of EUTRAN-to-WCDMA RRC redirections

triggered because of high load
L.RRCRedirection.E2G.Load Number of EUTRAN-to-GERAN RRC redirections

triggered because of high load
L.RRCRel.DedicatedPri.WCD Number of times WCDMA frequencies are assigned the

MA.High highest dedicated cell-reselection priority
NOTE
LOFD-00105401 Camp & Handover Based on SPID and LOFD-001112 MOCN Flexible Priority Based
Camping also affect the L.RRCRel.DedicatedPri.WCDMA.High counter.

eRAN
7.6 Parameter Optimization

The following parameters may need to be adjusted for better performance:
l Thresholds inter-frequency load balancing or inter-RAT load sharing

The thresholds directly determine the probabilities and effectiveness of the two types of
MLB.
l Load offset (specified by the CellMLB.LoadOffset parameter)
If the load offset is set to an appropriate value, the probability of ping-pong load transfer
will decrease.
l Handover-related parameters
These parameters determine the handover performance for load transfer.
7.7 Troubleshooting
This section provides steps to troubleshoot a possible fault that might occur after MLB is enabled.
Serving Cell Not Initiating Load Information Exchange for Inter-Frequency Load
Balancing
Fault Description
When inter-frequency load balancing is enabled and packet injection is performed for a UE, the
serving cell fails to initiate load information exchange with the neighboring E-UTRAN cells.
Fault Handling
Perform the following steps for troubleshooting:
Step 1 On the M2000 client, start X2 interface tracing task by referring to Inter-Frequency Load
Balancing in 7.4.5 Activation Observation.
Step 2 Check whether the serving eNodeB has sent a RESOURCE STATUS REQUEST message,
which contains information about the neighboring cells involved in load information exchange
with the serving cell. If the eNodeB has not sent this message, then this fault did occur. Go to
Step 3.
Step 3 Run the LST EUTRANINTERFREQNCELL command to check the inter-frequency

neighboring cells of the serving cell.
1. If at least one neighboring cell is displayed, go to 3.2. Otherwise, configure inter-frequency
neighboring cells and end the troubleshooting procedure.
2. If all the inter-frequency neighboring cells displayed are intra-eNodeB neighboring cells,
this is a normal condition and no fault handling is required. If all the inter-frequency
neighboring cells displayed are inter-eNodeB neighboring cells, run the DSP
X2INTERFACE command to check the connectivity of the X2 interface. If the X2
interface is functional, go to 3.3. Otherwise, handle the ALM-29204 X2 Interface Fault by
following handling suggestions in the alarm reference.

eRAN
3. If No handover indicator for the neighboring cell is Permit Ho, go to Step 4. Otherwise,
run the MOD EUTRANINTERFREQNCELL command to change it to Permit Ho.
Step 4 Run the LST INTERFREQBLKCELL command to check whether the displayed inter-
frequency neighboring cells have been blacklisted.
l If all these neighboring cells are blacklisted, this fault occurred because the eNodeB does
not perform MLB on blacklisted cells. No further action is required.
l Otherwise, go to Step 5.
Step 5 On the M2000 client, check whether ALM-29247 Cell PCI Conflict has been reported for the
serving cell.
l If this alarm has been reported, handle the alarm by following handling suggestions in the
alarm reference.
l If this alarm has not been reported, contact Huawei technical support.
----End
Failing to Initiate Inter-RAT Load Sharing with UTRAN for UEs in Connected
Mode
Fault Description
When inter-RAT load sharing with UTRAN for UEs in connected mode is enabled, the
UtranPsHoSwitch(UtranPsHoSwitch) check box under the Handover Mode switch
parameter is selected, and packet injection is performed for UEs, the servicing cell cannot initiate
inter-RAT load sharing to a UTRAN cell for any UE.
Fault Handling
Step 1 On the M2000 client, start RB usage monitoring by referring to Inter-Frequency Load
Step 2 Check whether the RB usage of the serving cell exceeds the sum of Inter-RAT Mobility Load
Balancing Threshold and Load Offset.
l If so, go to Step 3.
l If not, increase the traffic volume of UEs.
Step 3 Check whether the number of uplink synchronized UEs exceeds Inter-RAT Mobility Load
Balancing UE Number Threshold.
l If not, this is not a problem. No further action is required.
Step 4 Run the LST UTRANNCELL command to check whether the inter-RAT neighbor relationship
has been configured on the serving cell.
l If so, contact Huawei technical support.
l If not, configure the inter-RAT neighbor relationship on the serving cell.
----End

eRAN
Failing to Initiate Inter-RAT Load Sharing with UTRAN for UEs in Idle Mode
Fault Description
When inter-RAT load sharing with UTRAN for UEs in idle mode is enabled, no UE in the serving
cell can be transferred to a UTRAN cell by cell reselection.
Fault Handling
Step 1 On the M2000 client, start RB usage monitoring by referring to Inter-Frequency Load
Step 2 Check whether the RB usage of the serving cell exceeds the sum of Inter-RAT Mobility Load
Balancing Threshold and Load Offset.
l If not, increase the traffic volume of UEs.
Step 3 Check whether the number of uplink synchronized UEs exceeds Inter-RAT Mobility Load
Balancing UE Number Threshold.
l If not, this is not a problem. No further action is required.
Step 4 Check whether the priorities of E-UTRAN frequencies and those of neighboring UTRAN
frequencies belong to non-overlapping ranges.
l If not, modify the frequency priority configurations.
Step 5 Run the LST UTRANNCELL command to check whether the inter-RAT neighbor relationship
has been configured on the serving cell.
l If so, contact Huawei technical support.
l If not, configure the inter-RAT neighbor relationship on the serving cell.
----End

eRAN
MLB Feature Parameter Description 8 Parameters
8 Parameters
Table 8-1 Parameter description
MO Parameter ID MML Feature ID Feature Name Description

Command
CellAlgoSwitch MlbAlgoSwitch MOD LOFD-001032 / Intra-LTE Load Meaning:Indi-

CELLALGOS TDLOFD-0010 Balancing cates the
WITCH 32 Inter-RAT Load switches used to
LST LOFD-001044 / Sharing to enable or disable
CELLALGOS TDLOFD-0010 UTRAN load balancing
WITCH 44 algorithms,
Inter-RAT Load including the
LOFD-001045 / Sharing to switches which
TDLOFD-0010 GERAN are used to
45 Load Balancing control the intra-
LOFD-001057 based on frequency, intra-
Transport QoS frequency idle,
and inter-
frequency load
balancing
algorithms,
blind inter-
frequency load
balancing
algorithms, and
UTRAN,
UTRAN idle,
GERAN,
CDMA2000 and
LoadInfo load
sharing
algorithms. If
one switch is
turned on, the
corresponding
algorithm is

eRAN

Command
enabled to
balance or share
the loads
between
neighboring
cells of the
specified
category. If
IntraFreqMlbS-
witch is set to
On, intra-
frequency load
balancing is
enabled and
therefore
IntraFreqI-
dleMlbSwitch
becomes valid.
If
IntraFreqMlbS-
witch is set to
Off, intra-
frequency load
balancing is
disabled and
therefore
IntraFreqI-
dleMlbSwitch
does not take
effect. This
parameter will
be removed in
later versions. In
this version, the
setting of this
parameter is still
synchronized
between the
M2000 and the
eNodeB, but it is
no longer used
internally.
Therefore, avoid
using this
parameter. If
InterFreqMlbS-
witch is set to
On, inter-

eRAN

Command
frequency load
balancing is
enabled. If
InterFreqMlbS-
witch is set to
Off, inter-
frequency load
balancing is
disabled. If
UtranMlbSwitc
h is set to On,
load sharing
with UTRAN is
enabled. If
UtranMlbSwitc
h is set to Off,
load sharing
with UTRAN is
disabled. If
GeranMlbSwitc
h is set to On,
load sharing
with GERAN is
enabled. If
GeranMlbSwitc
h is set to Off,
load sharing
with GERAN is
disabled. If
CdmaMlbSwitc
h is set to On,
load sharing
with
CDMA2000 is
enabled. If
CdmaMlbSwitc
h is set to Off,
load sharing
with
CDMA2000 is
disabled. This
parameter will
be removed in
later versions. In
this version, the
setting of this
parameter is still
synchronized

eRAN

Command
between the
M2000 and the
eNodeB, but it is
no longer used
internally.
Therefore, avoid
using this
parameter. If
both IntraFreqI-
dleMlbSwitch
and
IntraFreqMlbS-
witch are set to
On, intra-
frequency load
balancing for
UEs in idle
mode is enabled.
Otherwise,
intra-frequency
idle load
balancing for
UEs in idle
mode is
disabled. This
parameter will
be removed in
later versions. In
this version, the
setting of this
parameter is still
synchronized
between the
M2000 and the
eNodeB, but it is
no longer used
internally.
Therefore, avoid
using this
parameter. If
UtranIdleMlbS-
witch is set to
On, load sharing
with UTRAN
for UEs in idle
mode is enabled.
If
UtranIdleMlbS-

eRAN

Command
witch is set to
Off, load sharing
with UTRAN
for UEs in idle
mode is
disabled. If
MlbLoadInfoS-
witch is set to
On, whether the
load sharing
between an E-
UTRAN cell
and an inter-
RAT cell is
performed based
on load of the
inter-RAT cell.
If
MlbLoadInfoS-
witch is set to
Off, load of an
inter-RAT cell is
not considered
when the load
sharing between
an E-UTRAN
cell and the
inter-RAT cell is
performed. In
load sharing
between an E-
UTRAN cell
and an inter-
RAT cell based
on load of the
inter-RAT cell,
the inter-RAT
cell must be a
UTRAN cell. If
MlbLoadInfoS-
witch and
UtranMlbSwitc
h are both set to
On, the UTRAN
cells with the
UMTS cell load
status parameter
set to Normal

eRAN

Command
among all the

UTRAN cells
whose load
status is
obtained are
considered as
target cells in
load sharing
between an E-
UTRAN cell
and a UTRAN
cell. When
InterFreq-
BlindMlbSwitc
h is set to On, the
blind inter-
frequency MLB
is enabled.
When InterFreq-
BlindMlbSwitc
h is set to Off,
the blind inter-
frequency MLB
is disabled.Inter-
FreqBlindMlbS-
witch and
InterFreqMlbS-
witch cannot be
set to On
simultaneously.
GUI Value
Range:Intra-
FreqMlbSwitch
(IntraFreqMlbS-
witch),
InterFreqMlbS-
witch
(InterFreqMlbS-
witch),
UtranMlbSwitc
h
(UtranMlbSwitc
h),
GeranMlbSwitc
h
(GeranMlbSwit
ch),

eRAN

Command
CdmaMlbSwitc
h
(CdmaMlbSwit
ch), IntraFreqI-
dleMlbSwitch
(IntraFreqI-
dleMlbSwitch),
UtranIdleMlbS-
witch
(UtranIdleMlbS
witch),
MlbLoadInfoS-
witch
(MlbLoadInfoS-
witch),
InterFreq-
BlindMlbSwitc
h(InterFreq-
BlindMlbSwitc
h)
Unit:None
Actual Value
Range:Intra-
FreqMlbSwitch,
InterFreqMlbS-
witch,
UtranMlbSwitc
h,
GeranMlbSwitc
h,
CdmaMlbSwitc
h, IntraFreqI-
dleMlbSwitch,
UtranIdleMlbS-
witch,
MlbLoadInfoS-
witch,
InterFreq-
BlindMlbSwitc
h
Default
Value:IntraFreq
MlbSwitch:Off,
InterFreqMlbS
witch:Off,
UtranMlbSwitc
h:Off,

eRAN

Command
GeranMlbSwitc
h:Off,
CdmaMlbSwitc
h:Off,
IntraFreqIdleMl
bSwitch:Off,
UtranIdleMlbS
witch:Off,
MlbLoadInfoS
witch:Off,
InterFreqBlind
MlbSwitch:Off

eRAN

Command
CellAlgoSwitch MlbHoMode MOD LOFD-001032 / Intra-LTE Load Meaning:Indi-

CELLALGOS TDLOFD-0010 Balancing cates whether to
WITCH 32 Inter-RAT Load enable or disable
LST LOFD-001044 / Sharing to handovers
CELLALGOS TD UTRAN triggered by the
WITCH LOFD-001044 load balancing
Inter-RAT Load algorithm, based
LOFD-001045 / Sharing to on which the
TDLOFD-0010 GERAN eNodeB
45 determines
handover
policies. When a
load-based
handover to an
inter-frequency
neighboring cell
in E-UTRAN is
to be performed,
the inter-
frequency blind
handover is
preferentially
performed if
InterFreqMlb-
BlindHo is set to
ON, and the
inter-frequency
blind handover
is not performed
if InterFreqMlb-
BlindHo is set to
OFF. When a
load-based
handover from
an E-UTRAN
cell to a UTRAN
or GERAN cell
is to be
performed, the
inter-RAT blind
handover is
preferentially
performed if
InterRatMlb-
BlindHo is set to
ON, and the
inter-RAT blind
handover is not

eRAN

Command
performed if
InterRatMlb-
BlindHo is set to
OFF.
GUI Value
Range:Inter-
FreqMlbBlindH
o(InterFreqMlb-
BlindHo),
InterRatMlb-
BlindHo
(InterRatMlb-
BlindHo)
Unit:None
Actual Value
Range:Inter-
FreqMlbBlindH
o, InterRatMlb-
BlindHo
Default
Value:InterFreq
MlbBlindHo:Of
f,
InterRatMlbBli
ndHo:Off

eRAN

Command
CellMLB LoadTransferFa MOD LOFD-001032 / Intra-LTE Load Meaning:Indi-

ctor CELLMLB TDLOFD-0010 Balancing cates the control
LST CELLMLB 32 factor for the
amount of a
single load
transfer. The
value of this
parameter has an
impact on the
efficiency of
MLB algorithm
and the
algorithm to
prevent ping-
pong load
transfer.
GUI Value
Range:0~100
Unit:%
Actual Value
Range:0~100
Default Value:0

eRAN

Command
CellMLB InterRatMlbThd MOD LOFD-001044 / Inter-RAT Load Meaning:Indi-

CELLMLB TDLOFD-0010 Sharing to cates the
LST CELLMLB 44 UTRAN threshold for
LOFD-001045 / Inter-RAT Load triggering inter-
TDLOFD-0010 Sharing to RAT load
45 GERAN balancing. Load
balancing
between the cell
and its inter-
RAT
neighboring cell
is triggered if the
cell load
exceeds the sum
of this threshold
and the offset,
and is stopped if
the cell load falls
below this
threshold.
GUI Value
Range:1~100
Unit:%
Actual Value
Range:1~100
Default Value:
75

eRAN

Command
CellMLB InterRatMlbUe- MOD LOFD-001044 / Inter-RAT Load Meaning:Indi-

NumThd CELLMLB TDLOFD-0010 Sharing to cates the
LST CELLMLB 44 UTRAN threshold of the
number of
uplink-
synchronized
UEs for
triggering inter-
RAT load
sharing. Load
balancing
between the cell
and its
neighboring
inter-RAT cell is
triggered if the
number of
uplink-
synchronized
UEs in the cell
exceeds this
threshold, and is
stopped if the
number of
uplink
synchronized
UEs falls below
this threshold.
The threshold
for the number
of uplink-
synchronized
UEs equals the
GUI value
multiplied by
1000 and 1%.
For example, a
GUI value of 1
means that the
threshold for the
number of
uplink-
synchronized
UEs is 10 (that
is, 1000 x 1%), a
GUI value of 2
means that the
threshold for the

eRAN

Command
number of
uplink-
synchronized
UEs is 20, and a
GUI value of 10
means that the
number of
uplink-
synchronized
UEs is 100.
However, if the
GUI values are
100 and 99, the
thresholds for
the numbers of
uplink-
synchronized
UEs are 1 and 2,
respectively.
GUI Value
Range:1~100
Unit:%
Actual Value
Range:1~100
Default Value:
15

eRAN

Command
CellMLB InitValidPeriod MOD LOFD-001044 / Inter-RAT Load Meaning:Indi-

CELLMLB TDLOFD-0010 Sharing to cates the
LST CELLMLB 44 UTRAN standard valid
duration for load
sharing with
universal
terrestrial radio
access network
(UTRAN) for
UEs in idle
mode. The
actual duration
increases on the
basis of a
standard valid
duration with
the increase of
the number of
uplink-
synchronized
UEs.
GUI Value
Range:1~30
Unit:s
Actual Value
Range:1~30
Default Value:
10

eRAN

Command
ENodeBAlgoS HoModeSwitch MOD LOFD-001022 / SRVCC to Meaning:Indi-

witch ENODEBALG TDLOFD-0010 UTRAN cates the
OSWITCH 22 SRVCC to switches
LST LOFD-001023 / GERAN corresponding
ENODEBALG TDLOFD-0010 to the inputs
CS Fallback to based on which
OSWITCH 23
UTRAN the eNodeB
LOFD-001033 / determines
CS Fallback to
TDLOFD-0010 handover
GERAN
33 policies.
LOFD-001034 / PS Inter-RAT
EutranVoipCap
TDLOFD-0010 Mobility
Switch: This
34 between E-
switch will be
UTRAN and
LOFD-001019 / removed in later
UTRAN
TDLOFD-0010 versions. In this
19 PS Inter-RAT version, the
Mobility setting of this
LOFD-001020 / between E- switch is still
TDLOFD-0010 UTRAN and synchronized
20 GERAN between the
LOFD-001021 / M2000 and the
PS Inter-RAT
TDLOFD-0010 eNodeB, but it is
Mobility
21 no longer used
between E-
TDLOFD-0010 UTRAN and internally.
52 CDMA2000 Therefore, avoid
using this
TDLOFD-0010 Flash CS switch.
88 Fallback to UtranVoipCapS
TDLOFD-0010 UTRAN witch: If this
43 CS Fallback switch is turned
TDLOFD-0010 Steering to on, UTRAN
72 UTRAN supports VoIP.
TDLOFD-0010 If this switch is
Service based
46 turned off,
Inter-RAT
UTRAN does
TDLOFD-0010 handover to
not support
73 UTRAN
VoIP.
Distance based GeranVoipCapS
Inter-RAT witch: If this
handover to switch is turned
UTRAN on, GERAN
Service based supports VoIP.
Inter-RAT If this switch is
handover to turned off,
GERAN GERAN does
not support
Distance based VoIP.
Inter-RAT Cdma1xRttVoip

eRAN

Command
handover to CapSwitch: If
GERAN this switch is
turned on,
CDMA2000
1xRTT supports
VoIP. If this
switch is turned
off, CDMA2000
1xRTT does not
support VoIP.
UtranPsHoSwit
ch: If this switch
is turned on,
UTRAN
supports PS
handovers. If
this switch is
turned off,
UTRAN does
not support PS
handovers.
GeranPsHoSwit
ch: If this switch
is turned on,
GERAN
supports PS
handovers. If
this switch is
turned off,
GERAN does
not support PS
handovers.
CdmaHrpdNon
OtpimisedHoS-
witch: If this
switch is turned
on, non-
optimized
handovers to
CDMA2000
HRPD are
enabled. If this
switch is turned
off, non-
optimized
handovers to
CDMA2000
HRPD are

eRAN

Command
disabled.
CdmaHrpdOpti
misedHoSwitch
: If this switch is
turned on,
optimized
handovers to
CDMA2000
HRPD are
enabled. If this
switch is turned
off, optimized
handovers to
CDMA2000
HRPD are
disabled.
GeranNaccSwit
ch: This switch
does not take
effect if
GeranCcoSwitc
h is disabled. If
this switch is
turned on,
GERAN
supports
network assisted
cell change
(NACC). If this
switch is turned
off, GERAN
does not support
NACC.
GeranCcoSwitc
h: If this switch
is turned on,
GERAN
supports cell
change order
(CCO). If this
switch is turned
off, GERAN
does not support
CCO.
UtranSrvccSwit
ch: If this switch
is turned on,
UTRAN

eRAN

Command
supports single
radio voice call
continuity
(SRVCC). If this
switch is turned
off, UTRAN
does not support
SRVCC.
GeranSrvccSwit
ch: If this switch
is turned on,
GERAN
supports
SRVCC. If this
switch is turned
off, GERAN
does not support
SRVCC.
Cdma1xRttSrvc
cSwitch: If this
switch is turned
on, CDMA2000
1xRTT supports
SRVCC. If this
switch is turned
off, CDMA2000
1xRTT does not
support
SRVCC.
UtranRedirectS-
witch: If this
switch is turned
on, redirection
to UTRAN is
enabled. If this
switch is turned
off, redirection
to UTRAN is
disabled.
GeranRedirectS
witch: If this
switch is turned
on, redirection
to GERAN is
enabled. If this
switch is turned
off, redirection
to GERAN is

eRAN

Command
disabled.
CdmaHrpdRedi
rectSwitch: If
this switch is
turned on,
redirection to
CDMA2000
HRPD is
enabled. If this
switch is turned
off, redirection
to CDMA2000
HRPD is
disabled.
Cdma1xRttRedi
rectSwitch: If
this switch is
turned on,
redirection to
CDMA2000
1xRTT is
enabled. If this
switch is turned
off, redirection
to CDMA2000
1xRTT is
disabled.
BlindHoSwitch:
If this switch is
turned on, blind
handovers for
CSFB are
enabled. If this
switch is turned
off, blind
handovers for
CSFB are
disabled.
LcsSrvccSwitch
: If this switch is
turned on, an
SRVCC
procedure is
triggered when a
UE receives a
CSFB
instruction
during a VoIP

eRAN

Command
service. If this
switch is turned
off, an SRVCC
procedure is not
triggered when a
UE receives a
CSFB
instruction
during a VoIP
service.
AutoGapSwitch
: If this switch is
turned on and
UEs support
automatic
measurement
gap
configurations
on the target
frequency, the
eNodeB does
not deliver gap
configurations
to UEs. If this
switch is turned
off, the eNodeB
delivers gap
configurations
to UEs during all
inter-frequency
and inter-RAT
measurements.
GUI Value
Range:Eutran-
VoipCapSwitch
(EutranVoipCap
Switch),
UtranVoipCapS
witch
(UtranVoipCap
Switch),
GeranVoipCapS
witch
(GeranVoipCap
Switch),
Cdma1xRttVoip
CapSwitch

eRAN

Command
(Cdma1xRttVoi
pCapSwitch),
UtranPsHoSwit
ch
(UtranPsHoSwit
ch),
GeranPsHoSwit
ch
(GeranPsHoSwi
tch),
CdmaHrpdNon
OtpimisedHoS-
witch
(CdmaHrpdNon
OtpimisedHoS-
witch),
CdmaHrpdOpti
misedHoSwitch
(CdmaHrpdOpti
misedHoSwitch
),
GeranNaccSwit
ch
(GeranNaccSwi
tch),
GeranCcoSwitc
h
(GeranCcoSwit
ch),
UtranSrvccSwit
ch
(UtranSrvccS-
witch),
GeranSrvccSwit
ch
(GeranSrvccS-
witch),
Cdma1xRttSrvc
cSwitch
(Cdma1xRttSrv
ccSwitch),
UtranRedirectS-
witch
(UtranRedirectS
witch),
GeranRedirectS
witch
(GeranRedirect

eRAN

Command
Switch),
CdmaHrpdRedi
rectSwitch
(CdmaHrpdRed
irectSwitch),
Cdma1xRttRedi
rectSwitch
(Cdma1xRttRed
irectSwitch),
BlindHoSwitch
(BlindHoSwitch
),
LcsSrvccSwitch
(LcsSrvccSwitc
h),
AutoGapSwitch
(AutoGapSwitc
h)
Unit:None
Actual Value
Range:Eutran-
VoipCapSwitch
,
UtranVoipCapS
witch,
GeranVoipCapS
witch,
Cdma1xRttVoip
CapSwitch,
UtranPsHoSwit
ch,
GeranPsHoSwit
ch,
CdmaHrpdNon
OtpimisedHoS-
witch,
CdmaHrpdOpti
misedHoSwitch
,
GeranNaccSwit
ch,
GeranCcoSwitc
h,
UtranSrvccSwit
ch,
GeranSrvccSwit
ch,

eRAN

Command
Cdma1xRttSrvc
cSwitch,
UtranRedirectS-
witch,
GeranRedirectS
witch,
CdmaHrpdRedi
rectSwitch,
Cdma1xRttRedi
rectSwitch,
BlindHoSwitch,
LcsSrvccSwitch
,
AutoGapSwitch
Default
Value:EutranVo
ipCapSwitch:O
n,
UtranVoipCapS
witch:Off,
GeranVoipCapS
witch:Off,
Cdma1xRttVoip
CapSwitch:Off,
UtranPsHoSwit
ch:Off,
GeranPsHoSwit
ch:Off,
CdmaHrpdNon
OtpimisedHoS
witch:Off,
CdmaHrpdOpti
misedHoSwitch
:Off,
GeranNaccSwit
ch:Off,
GeranCcoSwitc
h:Off,
UtranSrvccSwit
ch:Off,
GeranSrvccSwit
ch:Off,
Cdma1xRttSrvc
cSwitch:Off,
UtranRedirectS
witch:Off,
GeranRedirectS

eRAN

Command
witch:Off,
CdmaHrpdRedi
rectSwitch:Off,
Cdma1xRttRedi
rectSwitch:Off,
BlindHoSwitch:
Off,
LcsSrvccSwitch
:Off,
AutoGapSwitch
:Off

eRAN

Command
CellMLB MlbUeSe- MOD LOFD-001032 / Intra-LTE Load Meaning:Indi-

lectPrbThd CELLMLB TDLOFD-0010 Balancing cates the PRB
LST CELLMLB 32 usage threshold
of a UE in the
inter-frequency
MLB. When the
MlbTriggerMod
e parameter is
set to
PRB_ONLY,
the UE whose
the PRB usage
with the load
balancing in
downlink or
uplink is larger
than the
MlbUeSe-
lectPrbThd
parameter value
and the PRB
usage with the
load balancing
in the reserve
direction (uplink
or downlink) is
less than the
MlbUeSe-
lectPrbThd
parameter value
is selected.
When the
MlbTriggerMod
e parameter is
set to
UE_NUMBER_
ONLY, the UE
whose PRB
usage is less than
the MlbUeSe-
lectPrbThd
parameter value
is selected.
When
MlbTriggerMod
e parameter is
set to
PRB_OR_UE_

eRAN

Command
NUMBER, a
related UE is
selected based
on the scenario
where the inter-
frequency MLB
is triggered the
number of UEs
in the serving
cell. The
parameter only
applies to blind
inter-frequency
MLB in this
version.
GUI Value
Range:0~50
Unit:%
Actual Value
Range:0~50
Default Value:2

eRAN

Command
CellMLB MlbTriggerMod MOD LOFD-001032 / Intra-LTE Load Meaning:Indi-

e CELLMLB TDLOFD-0010 Balancing cates the mode
LST CELLMLB 32 to trigger MLB.
PRB_ONLY:
Indicates that
the inter-
frequency MLB
is triggered by
PRB usage.
UE_NUMBER_
ONLY:
Indicates that
the inter-
frequency MLB
is triggered by
the number of
UEs in the
serving cell.
PRB_OR_UE_
NUMBER:
Indicates that
blind inter-
frequency MLB
is triggered by
either the PRB
usage or the
number of UEs
in the serving
cell. The
MlbTriggerMod
e parameter only
applies to blind
inter-frequency
MLB in this
version.
GUI Value
Range:PRB_O
NLY
(PrbMode),
UE_NUMBER_
ONLY
(UeNumMode),
PRB_OR_UE_
NUMBER
(PrbOrUeNum
Mode)
Unit:None

eRAN

Command
Actual Value
Range:PRB_O
NLY,
UE_NUMBER_
ONLY,
PRB_OR_UE_
NUMBER
Default
Value:PRB_ON
LY(PrbMode)

eRAN

Command
CellMLB InterFreqMlbUe MOD LOFD-001032 / Intra-LTE Load Meaning:Indi-

NumThd CELLMLB TDLOFD-0010 Balancing cates the
LST CELLMLB 32 threshold of
maximum
number of UL-
synchronized
users when the
MLB is
triggered by the
number of UEs
in the serving
cell. When the
number of UL-
synchronized
users in the
serving cell
exceeds the sum
of the
InterFreqMlbUe
NumThd
parameter value
and the
MlbUeNumOffs
et parameter
value, inter-
frequency MLB
is
triggered.When
the number of
UL-
synchronized
users in the
serving cell is
less than the
InterFreqMlbUe
NumThd
parameter value,
the inter-
frequency MLB
stops. The
InterFreqMlbUe
NumThd
parameter only
applies to blind
inter-frequency
MLB in this
version.

eRAN

Command
GUI Value
Range:1~10000
Unit:None
Actual Value
Range:1~10000
Default Value:
100
CellMLB MlbUeNumOffs MOD LOFD-001032 / Intra-LTE Load Meaning:Indi-

et CELLMLB TDLOFD-0010 Balancing cates the offset
LST CELLMLB 32 of the number of
UL-
synchronized
users for
triggering the
inter-frequency
MLB. The inter-
frequency MLB
is triggered
when the
number of UL-
synchronized
users exceeds
the sum of the
InterFreqMlbUe
NumThd
parameter value
and the
MlbUeNumOffs
et parameter
value. The
MlbUeNumOffs
et parameter
only applies to
blind inter-
frequency MLB
in this version.
GUI Value
Range:0~10000
Unit:None
Actual Value
Range:0~10000
Default Value:
20

eRAN

Command
CellMLB MlbMaxUeNu MOD LOFD-001032 / Intra-LTE Load Meaning:Indi-

m CELLMLB TDLOFD-0010 Balancing cates the
LST CELLMLB 32 maximum
number of UEs
that can be
handed over to
the inter-
frequency cell in
the inter-
frequency MLB.
This parameter
aims to avoid too
many UEs being
handed over to
the inter-
frequency cell at
a time, and
therefore the
impact on the
inter-frequency
cell is reduced.
The
MlbMaxUeNu
m parameter
only applies to
blind inter-
frequency MLB
in this version.
GUI Value
Range:1~20
Unit:None
Actual Value
Range:1~20
Default Value:5

eRAN

Command
EutranInterNFre MlbTargetInd ADD LBFD-0020180 Coverage Based Meaning:Indi-

q EUTRANINTE 2/ Inter-frequency cates whether an
RNFREQ TDLBFD-0020 Handover inter-frequency
MOD 1802 is allowed to
EUTRANINTE function as the
RNFREQ target frequency
in the inter-
LST frequency MLB.
EUTRANINTE When this
RNFREQ parameter is set
to ALLOWED,
an inter-
frequency can
function as the
target frequency
in the inter-
frequency MLB.
When this
parameter is set
to
NOT_ALLOW
ED, an inter-
frequency
cannot function
as the target
frequency in the
inter-frequency
MLB. This
parameter
applies only to
inter-frequency
blind MLB in
the current
version.
GUI Value
Range:NOT_A
LLOWED
(NOT_ALLOW
ED),
ALLOWED
(ALLOWED)
Unit:None
Actual Value
Range:NOT_A
LLOWED,
ALLOWED

eRAN

Command
Default
Value:ALLOW
ED
(ALLOWED)
CellMLB InterFreqMlbTh MOD LOFD-001032 / Intra-LTE Load Meaning:Indi-

d CELLMLB TDLOFD-0010 Balancing cates the
LST CELLMLB 32 threshold for
triggering inter-
frequency load
balancing. Load
balancing
between the cell
and its inter-
frequency
neighboring cell
is triggered if the
cell load
exceeds the sum
of this threshold
and the offset,
and is stopped if
the cell load falls
below this
threshold.
GUI Value
Range:1~100
Unit:%
Actual Value
Range:1~100
Default Value:
60

eRAN

Command
CellMLB LoadOffset MOD LOFD-001032 / Intra-LTE Load Meaning:Indi-

CELLMLB TDLOFD-0010 Balancing cates the offset
LST CELLMLB 32 Inter-RAT Load used in the
LOFD-001044 / Sharing to evaluation of
TDLOFD-0010 UTRAN whether to
44 trigger load
Inter-RAT Load balancing. To
LOFD-001045 / Sharing to prevent load
TDLOFD-0010 GERAN fluctuations
45 from frequently
triggering or
stopping load
balancing, an
offset needs to
be set. That is, a
specific load
balancing action
is taken only if
the cell load
exceeds the sum
of the
corresponding
load balancing
threshold and
this offset.
GUI Value
Range:0~50
Unit:%
Actual Value
Range:0~50
Default Value:8

eRAN

Command
EutranInter- NoHoFlag ADD LBFD-0020180 Coverage Based Meaning:Indi-

FreqNCell EUTRANINTE 2/ Inter-frequency cates whether
RFREQNCELL TDLBFD-0020 Handover handovers of
MOD 1802 Distance Based UEs to the
EUTRANINTE LBFD-0020180 Inter-frequency neighboring cell
RFREQNCELL 4/ Handover are prohibited.
LST TDLBFD-0020 Service Based GUI Value

EUTRANINTE 1804 Inter-frequency Range:PERMIT
RFREQNCELL LBFD-0020180 Handover _HO_ENUM
5/ (Permit Ho),
Cell Outage FORBID_HO_
TDLBFD-0020 Detection and
1805 ENUM(Forbid
Compensation Ho)
LOFD-002012 /
TDLOFD-0020 Unit:None
12 Actual Value
Range:PERMIT
_HO_ENUM,
FORBID_HO_
ENUM
Default
Value:PERMIT
_HO_ENUM
(Permit Ho)

eRAN

Command
CellMLB LoadDiffThd MOD LOFD-001032 / Intra-LTE Load Meaning:Indi-

CELLMLB TDLOFD-0010 Balancing cates the
LST CELLMLB 32 Inter-RAT Load threshold of load
LOFD-001044 / Sharing to difference
TDLOFD-0010 UTRAN between two
44 cells for load
Inter-RAT Load balancing. If the
LOFD-001045 / Sharing to load difference
TDLOFD-0010 GERAN between two
45 cells exceeds
this threshold,
the eNodeB
determines that
load imbalance
occurs and
therefore
initiates load
balancing
between the
cells. If the load
difference
between cells
falls below this
threshold, the
eNodeB
determines that
load imbalance
is resolved and
therefore stops
load balancing
between the
cells.
GUI Value
Range:1~50
Unit:%
Actual Value
Range:1~50
Default Value:
15

eRAN

Command
InterFreqHoGro InterFreqLoadB ADD LBFD-0020180 Service Based Meaning:Indi-

up asedHoA4ThdR INTERFREQH 5/ Inter-frequency cates the RSRP
srp OGROUP TDLBFD-0020 Handover threshold for
MOD 1805 event A4 related
INTERFREQH to load-based
OGROUP inter-frequency
handover. When
LST the measured
INTERFREQH RSRP value
OGROUP exceeds this
threshold, an
inter-frequency
measurement
report will be
sent. The value
-141 does not
take effect and is
reserved for
forward
compatibility. If
this parameter is
set to -141, the
value -140 is
used as the
threshold in
implementation.
The value of this
parameter is also
used as the
RSRP threshold
for event A4
related to
frequency-
priority-based or
service-based
inter-frequency
handover.
GUI Value
Range:-141~-43
Unit:dBm
Actual Value
Range:-141~-43
Default
Value:-103

eRAN

Command
SpidCfg InterFreqMlbS- ADD SPIDCFG LOFD-0010540 Camp & Meaning:Indi-

witch MOD SPIDCFG 1/ Handover Based cates whether to
TDLOFD-0010 on SPID enable or disable
LST SPIDCFG 5401 inter-frequency
Intra-LTE Load
LOFD-001032 / Balancing load balancing
TDLOFD-0010 for the SPID.
32 The values
TRUE or
FALSE indicate
that inter-
frequency load
balancing is
allowed or
prohibited for
UEs with the
SPID,
respectively.
GUI Value
Range:FALSE
(FALSE),
TRUE(TRUE)
Unit:None
Actual Value
Range:FALSE,
TRUE
Default
Value:TRUE
(TRUE)

eRAN

Command
InterRatHoU- LdSvBasedHoU ADD LOFD-001043 Service based Meaning:Indi-

tranGroup tranB1ThdEcn0 INTERRATHO TDLOFD-0010 inter-RAT cates the Ec/N0
UTRANGROU 22 handover to threshold for
P UTRAN event B1 related
MOD SRVCC to to load- or
INTERRATHO UTRAN service-based
UTRANGROU inter-RAT
P handover to
UTRAN. This
LST parameter
INTERRATHO specifies the
UTRANGROU requirement for
P Ec/N0 of the
target UTRAN
cell. When the
measurement
value exceeds
this threshold, a
measurement
report may be
sent. For a cell
with large signal
fading variance,
set this
parameter to a
large value to
prevent
unnecessary
handovers. For a
cell with small
signal fading
variance, set this
parameter to a
small value to
ensure timely
handovers.
GUI Value
Range:-48~0
Unit:0.5dB
Actual Value
Range:-24~0,
step:0.5
Default
Value:-18

eRAN

Command
InterRatHoGer- LdSvBasedHoG ADD LOFD-001046 / Service based Meaning:Indi-

anGroup eranB1Thd INTERRATHO TDLOFD-0010 inter-RAT cates the RSSI
GERANGROU 46 handover to threshold for
P GERAN event B1 related
MOD to load- or
INTERRATHO service-based
GERANGROU inter-RAT
P handover to
GERAN. When
LST the measured
INTERRATHO RSSI value
GERANGROU exceeds this
P threshold, a
measurement
report will be
sent.
GUI Value
Range:-110~-48
Unit:dBm
Actual Value
Range:-110~-48
Default
Value:-98

eRAN

Command
SpidCfg InterRatMlbS- ADD SPIDCFG LOFD-0010540 Camp & Meaning:Indi-

witch MOD SPIDCFG 1/ Handover Based cates whether to
TDLOFD-0010 on SPID enable or disable
LST SPIDCFG 5401 inter-RAT load
Inter-RAT Load
LOFD-001044 / Sharing to sharing for the
TDLOFD-0010 UTRAN SPID. The
44 values TRUE or
Inter-RAT Load FALSE indicate
LOFD-001045 / Sharing to that inter-RAT
TDLOFD-0010 GERAN load sharing is
45 allowed or
prohibited for
UEs with the
SPID,
respectively.
GUI Value
Range:FALSE
(FALSE),
TRUE(TRUE)
Unit:None
Actual Value
Range:FALSE,
TRUE
Default
Value:TRUE
(TRUE)

eRAN

Command
RrcConnStateTi T320ForLoadB MOD None None Meaning:Indi-

mer alance RRCCONNST cates the length
ATETIMER of timer T320
LST for load
RRCCONNST balancing. T320
ATETIMER specifies the
time period
during which the
dedicated
priorities (used
for cell
reselection)
retain valid. The
time period is
contained in the
RRCConnection
Release
message that is
received by the
UE. After T320
expires, the
dedicated
priorities
become invalid.
This timer is
started when the
UE receives an
RRCConnection
Release
message
containing the
t320 IE. This
timer is stopped
when the UE
enters the
RRC_CONNEC
TED mode.
GUI Value
Range:min5(5),
min10(10),
min20(20),
min30(30),
min60(60),
min120(120),
min180(180)
Unit:min

eRAN

Command
Actual Value
Range:min5,
min10, min20,
min30, min60,
min120, min180
Default
Value:min10
(10)
InterRatHoU- LdSvBasedHoU ADD LOFD-001043 Service based Meaning:Indi-

tranGroup tranB1ThdRscp INTERRATHO TDLOFD-0010 inter-RAT cates the RSCP
UTRANGROU 22 handover to threshold for
P UTRAN event B1 related
MOD SRVCC to to load- or
INTERRATHO UTRAN service-based
UTRANGROU inter-RAT
P handover to
UTRAN. This
LST parameter
INTERRATHO specifies the
UTRANGROU requirement for
P RSCP of the
target UTRAN
cell. When the
measurement
value exceeds
this threshold, a
measurement
report will be
sent.
GUI Value
Range:-120~-25
Unit:dBm
Actual Value
Range:-120~-25
Default
Value:-101

eRAN

Command
CellAlgoSwitch LocalCellId LST None None Meaning:Indi-

CELLALGOS cates the local
WITCH ID of the cell. It
MOD uniquely
CELLALGOS identifies a cell
WITCH within a BS.
GUI Value
Range:0~17
Unit:None
Actual Value
Range:0~17
Default
Value:None
CellMLB LocalCellId LST CELLMLB None None Meaning:Indi-

MOD cates the local
CELLMLB ID of the cell. It
uniquely
identifies a cell
within a BS.
GUI Value
Range:0~17
Unit:None
Actual Value
Range:0~17
Default
Value:None
SpidCfg Spid ADD SPIDCFG LOFD-0010540 Camp & Meaning:Indi-

LST SPIDCFG 1/ Handover Based cates the
TDLOFD-0010 on SPID subscriber
MOD SPIDCFG 5401 profile ID
UL Pre-
RMV SPIDCFG LOFD-001059 / allocation Based (SPID).
TDLOFD-0010 on SPID GUI Value
59 Range:1~256
Unit:None
Actual Value
Range:1~256
Default
Value:None

eRAN

Command
SpidCfg RatFreqPriori- ADD SPIDCFG LOFD-0010540 Camp & Meaning:Indi-

tyInd MOD SPIDCFG 1/ Handover Based cates whether to
TDLOFD-0010 on SPID set the priority
LST SPIDCFG 5401 for the intra-
RAT frequency
group. If this
parameter is set
to CFG(CFG),
UEs select the
target frequency
based on the
priority setting.
If this parameter
is set to
NOT_CFG
(NOT_CFG),
UEs do not
select the target
frequency based
on the priority
setting.
GUI Value
Range:NOT_CF
G(NOT_CFG),
CFG(CFG)
Unit:None
Actual Value
Range:NOT_CF
G, CFG
Default
Value:NOT_CF
G(NOT_CFG)
SpidCfg RatFreqPriority- ADD SPIDCFG LOFD-0010540 Camp & Meaning:Indi-

GroupId MOD SPIDCFG 1/ Handover Based cates the ID of
TDLOFD-0010 on SPID the intra-RAT
LST SPIDCFG 5401 frequency
priority group.
GUI Value
Range:0~255
Unit:None
Actual Value
Range:0~255
Default Value:0

eRAN

Command
TLDRALG TRMULLDRT SET TLDRALG LOFD-001032 / Intra-LTE Load Meaning:Indi-

RGTH LST TLDRALG TDLOFD-0010 Balancing cates the
32 threshold for
triggering the
UL high load. If
the ratio of the
UL transport
load to the UL
transport
bandwidth of the
BS keeps above
this threshold
for a period of
hysteresis, the
UL transport
load of the BS
enters the high-
load state. In UL
high-load state,
the BS sends a
UL S1 TNL
Load Indicator,
which is set to
HighLoad, to
each
neighboring BS
through the X2
interface.
GUI Value
Range:0~100
Unit:%
Actual Value
Range:0~100
Default Value:
70

eRAN

Command
TLDRALG TRMDLLDRT SET TLDRALG LOFD-001032 / Intra-LTE Load Meaning:Indi-

32 threshold for
triggering the
DL high load. If
the ratio of the
DL transport
load to the DL
transport
bandwidth of the
BS keeps above
this threshold
for a period of
hysteresis, the
DL transport
load of the BS
enters the high-
load state. In DL
high-load state,
the BS sends a
DL S1 TNL
Load Indicator,
which is set to
HighLoad, to
each
neighboring BS
through the X2
interface.
GUI Value
Range:0~100
Unit:%
Actual Value
Range:0~100
Default Value:
70

eRAN

Command
TLDRALG TRMULLDRC SET TLDRALG LOFD-001032 / Intra-LTE Load Meaning:Indi-

LRTH LST TLDRALG TDLOFD-0010 Balancing cates the
32 threshold for
clearing the UL
high load. If the
ratio of the UL
transport load to
the UL transport
bandwidth of the
BS keeps below
this threshold
for a period of
hysteresis, the
UL transport
load of the BS
enters the
medium-load
state. In UL
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.
GUI Value
Range:0~100
Unit:%
Actual Value
Range:0~100
Default Value:
65

eRAN

Command
TLDRALG TRMDLLDRC SET TLDRALG LOFD-001032 / Intra-LTE Load Meaning:Indi-

32 threshold for
clearing the DL
high load. If the
ratio of the
transport load to
the transmission
bandwidth in
DL of the BS
keeps below this
threshold for a
period of time,
the DL transport
load of the BS
enters the
medium-load
state. In DL
medium-load
state, the BS
sends a DL S1
TNL Load
Indicator, which
is set to
MediumLoad, to
each
neighboring BS
through the X2
interface.
GUI Value
Range:0~100
Unit:%
Actual Value
Range:0~100
Default Value:
65

eRAN

Command
TLDRALG TRMULMLDT SET TLDRALG LOFD-001032 / Intra-LTE Load Meaning:Indi-

32 threshold for
triggering the
UL medium
load. If the ratio
of the UL
transport load to
the UL transport
bandwidth of the
BS is above this
threshold, the
UL transport
load of the BS
enters the
medium-load
state. In UL
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.
GUI Value
Range:0~100
Unit:%
Actual Value
Range:0~100
Default Value:
50

eRAN

Command
TLDRALG TRMDLMLDT SET TLDRALG LOFD-001032 / Intra-LTE Load Meaning:Indi-

32 threshold for
triggering the
DL medium
load. If the ratio
of the DL
transport load to
the DL transport
bandwidth of the
BS is above this
threshold, the
DL transport
load of the BS
enters the
medium-load
state. In DL
medium-load
state, the BS
sends a DL S1
TNL Load
Indicator, which
is set to
MediumLoad, to
each
neighboring BS
through the X2
interface.
GUI Value
Range:0~100
Unit:%
Actual Value
Range:0~100
Default Value:
50

eRAN

Command
TLDRALG TRMULMLDC SET TLDRALG LOFD-001032 / Intra-LTE Load Meaning:Indi-

32 threshold for
clearing the UL
medium load. If
the ratio of the
UL transport
load to the UL
transport
bandwidth of the
BS is below this
threshold, the
UL transport
load of the BS
enters the low-
load state. In UL
low-load state,
the BS sends a
UL S1 TNL
Load Indicator,
which is set to
LowLoad, to
each
neighboring BS
through the X2
interface.
GUI Value
Range:0~100
Unit:%
Actual Value
Range:0~100
Default Value:
45

Command
TLDRALG TRMDLMLDC SET TLDRALG LOFD-001032 / Intra-LTE Load Meaning:Indi-

32 threshold for
clearing the DL
medium load. If
the ratio of the
DL transport
load to the DL
transport
bandwidth of the
BS is below this
threshold, the
DL transport
load of the BS
enters the low-
load state. In DL
low-load state,
the BS sends a
DL S1 TNL
Load Indicator,
w p
Load Indi low- RA "
tht " M di
eRAN

Command
EutranInterNFre LocalCellId ADD None None Meaning:Indi-

q EUTRANINTE cates the cell ID
RNFREQ of the local cell.
LST It uniquely
EUTRANINTE identifies a cell
RNFREQ within an
eNodeB.
MOD
EUTRANINTE GUI Value
RNFREQ Range:0~17
RMV Unit:None
EUTRANINTE Actual Value
RNFREQ Range:0~17
Default
Value:None

eRAN
MLB Feature Parameter Description 9 Counters
9 Counters
Table 9-1 Counter description
Counter ID Counter Name Counter Feature ID Feature Name

Description
1526728443 L.RRCRel.Dedicate Number of times Multi-mode: None Camp & Handover

dPri.WCDMA.High that the WCDMA GSM: None Based on SPID
network is Camp & Handover
configured as the UMTS: None
Based on SPID
highest frequency LTE:
priority in an LOFD-00105401 Inter-RAT Load
IMMCI IE Sharing to UTRAN
TDLOFD-0010540
1 Inter-RAT Load
Sharing to UTRAN
LOFD-001044
MOCN Flexible
TDLOFD-001044 Priority Based
LOFD-001112 Camping
1526728526 L.HHO.InterFreq.L Number of inter- Multi-mode: None Intra-LTE Load

oad.PrepAttOut frequency handover GSM: None Balancing
preparation attempts Intra-LTE Load
triggered because of UMTS: None
Balancing
high load LTE:
LOFD-001032
TDLOFD-001032
1526728527 L.HHO.InterFreq.L Number of inter- Multi-mode: None Intra-LTE Load

oad.ExecAttOut frequency handover GSM: None Balancing
execution attempts Intra-LTE Load
Balancing
high load LTE:
LOFD-001032
TDLOFD-001032

eRAN

Description
1526728528 L.HHO.InterFreq.L Number of Multi-mode: None Intra-LTE Load

oad.ExecSuccOut successful inter- GSM: None Balancing
frequency handover Intra-LTE Load
executions triggered UMTS: None
Balancing
because of high load LTE:
LOFD-001032
TDLOFD-001032
1526728529 L.IRATHO.E2W.L Number of inter- Multi-mode: None Inter-RAT Load

oad.PrepAttOut RAT handover GSM: None Sharing to UTRAN
preparation attempts Inter-RAT Load
from E-UTRAN to UMTS: None
Sharing to UTRAN
WCDMA network LTE:
triggered because of LOFD-001044
high load TDLOFD-001044
1526728530 L.IRATHO.E2W.L Number of inter- Multi-mode: None Inter-RAT Load

oad.ExecAttOut RAT handover GSM: None Sharing to UTRAN
execution attempts Inter-RAT Load
Sharing to UTRAN
WCDMA network LTE:
1526728531 L.IRATHO.E2W.L Number of Multi-mode: None Inter-RAT Load

oad.ExecSuccOut successful inter- GSM: None Sharing to UTRAN
RAT handover Inter-RAT Load
executions from E- UMTS: None
Sharing to UTRAN
UTRAN to LTE:
WCDMA network LOFD-001044
triggered because of TDLOFD-001044
high load
1526728532 L.IRATHO.E2G.Lo Number of inter- Multi-mode: None Inter-RAT Load

ad.PrepAttOut RAT handover GSM: None Sharing to GERAN
preparation attempts Inter-RAT Load
Sharing to GERAN
GERAN triggered LTE:
because of high load LOFD-001045
TDLOFD-001045
1526728533 L.IRATHO.E2G.Lo Number of inter- Multi-mode: None Inter-RAT Load

ad.ExecAttOut RAT handover GSM: None Sharing to GERAN
execution attempts Inter-RAT Load
Sharing to GERAN
GERAN triggered LTE:
because of high load LOFD-001045
TDLOFD-001045

eRAN

Description
1526728534 L.IRATHO.E2G.Lo Number of Multi-mode: None Inter-RAT Load

ad.ExecSuccOut successful inter- GSM: None Sharing to GERAN
RAT handover Inter-RAT Load
executions from E- UMTS: None
Sharing to GERAN
UTRAN to GERAN LTE:
1526728535 L.RRCRedirection. Number of Multi-mode: None Inter-RAT Load

E2W.Load redirections from E- GSM: None Sharing to UTRAN
UTRAN to Inter-RAT Load
WCDMA network UMTS: None
Sharing to UTRAN
triggered because of LTE:
high load LOFD-001044
TDLOFD-001044
1526728536 L.RRCRedirection. Number of Multi-mode: None Inter-RAT Load

E2G.Load redirections from E- GSM: None Sharing to GERAN
UTRAN to GERAN Inter-RAT Load
Sharing to GERAN
high load LTE:
LOFD-001045
TDLOFD-001045
1526728949 L.RIM.Load.E2W. Number of load Multi-mode: None Inter-RAT Load

Req requests from GSM: None Sharing to UTRAN
eNodeB to Inter-RAT Load
Sharing to UTRAN
LTE:
LOFD-001044
TDLOFD-001044

Resp responses from GSM: None Sharing to UTRAN
WCDMA network Inter-RAT Load
to eNodeB UMTS: None
Sharing to UTRAN
LTE:
LOFD-001044
TDLOFD-001044

Update updates from GSM: None Sharing to UTRAN
eNodeB to Inter-RAT Load
Sharing to UTRAN
LTE:
LOFD-001044
TDLOFD-001044

eRAN
MLB Feature Parameter Description 10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
MLB Feature Parameter Description 11 Reference Documents
11 Reference Documents
1. 3GPP TS 36.300, "E-UTRAN Overall description"

2. 3GPP TS 36.331, "Radio Resource Control (RRC)"
3. 3GPP TS 36.413, "S1 Application Protocol (S1AP)"
4. 3GPP TS 36.423, "X2 application protocol (X2AP)"
5. 3GPP TS 36.902, "Self-configuring and self-optimizing network use cases and solutions"
6. Mobility Management in Connected Mode Feature Parameter Description
7. RAN Sharing Feature Parameter Description
8. Transport Resource Management Feature Parameter Description


MLB Lte Load Control Mechanismm

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

MLB Lte Load Control Mechanismm

Hochgeladen von

Copyright:

Verfügbare Formate

eRAN

MLB Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2013-10-30) Huawei Proprietary and Confidential i

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

3 Inter-Frequency Load Balancing................................................................................................8

4 Inter-RAT Load Sharing.............................................................................................................13

Issue 04 (2013-10-30) Huawei Proprietary and Confidential ii

6.1 LOFD-001032 Intra-LTE Load Balancing...................................................................................................................19

Issue 04 (2013-10-30) Huawei Proprietary and Confidential iii

1 About This Document

This document covers the following features:

l LOFD-001032 Intra-LTE Load Balancing

1.2 Intended Audience

l Need to understand the features described herein

1.3 Change History

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 1

Change Type Change Description Parameter Change

Feature change None None

Editorial change Revised 3.4 Load Balancing Execution and None

Change Type Change Description Parameter Change

Feature change In inter-RAT load sharing to UTRAN, deleted None

Editorial change None None

Change Type Change Description Parameter Change

Feature change None None

Editorial change Optimized some descriptions in 7.4.2 Data None

Change Type Change Description Parameter Change

Feature change None None

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 2

Change Type Change Description Parameter Change

Editorial change Optimized the descriptions of None

Change Change Description Parameter Change

Feature In inter-RAT load sharing to Added the MlbLoadInfoSwitch

Removed intra-frequency load Removed the parameters for intra-

Added the switches of blind Added the CellAlgoSwitch.MlbHoMode

Added the configuration of the Added the CellMLB.LoadTransferFac-

Editorial Revised the description of inter- None

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 3

RAT is short for radio access technology.

MLB involves the following optional features:

l LOFD-001032 Intra-LTE Load Balancing

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 4

2.1 Basic Concepts

2.1.1 Cell Load

Figure 2-1 Different types of loads and their positions

2.1.2 Service Type

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 5

2.1.3 Source Cell and Target Cell

A target cell is a neighboring cell to which MLB transfers the load.

2.2 MLB Procedure

The MLB procedure consists of the following steps:

1. Load measurement and evaluation

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 6

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 7

3 Inter-Frequency Load Balancing

Inter-frequency load balancing is enabled if the InterFreqMlbSwitch(InterFreqMlbSwitch)

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 8

3.1 Load Measurement and Evaluation

3.2 Load Information Exchange

3.2.1 Neighboring Cell Selection

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 9