MLB (eRAN6.0 02)

eRAN
eRAN6.0
MLB Feature Parameter Description
Issue 02
Date 2013-05-31
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 02 (2013-05-31) 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................................................................................................7

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

4.1 Load Measurement and Evaluation..............................................................................................................................13
4.2 Load Information Exchange.........................................................................................................................................13
4.3 Load Sharing Decision.................................................................................................................................................13
4.4 Load Sharing Execution...............................................................................................................................................14
4.4.1 Transferring UEs in Connected Mode.......................................................................................................................14
4.4.2 Transferring UEs in Idle Mode..................................................................................................................................15
5 Related Features...........................................................................................................................16
5.1 Features Related to LOFD-001032 Intra-LTE Load Balancing...................................................................................16
5.2 Features Related to LOFD-001044 Inter-RAT Load Sharing to UTRAN...................................................................16
5.3 Features Related to LOFD-001045 Inter-RAT Load Sharing to GERAN...................................................................17
6 Network Impact...........................................................................................................................18
Issue 02 (2013-05-31) Huawei Proprietary and Confidential ii

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

6.2 LOFD-001044 Inter-RAT Load Sharing to UTRAN...................................................................................................18
6.3 LOFD-001045 Inter-RAT Load Sharing to GERAN...................................................................................................18
7 Engineering Guidelines.............................................................................................................20
7.1 When to Use MLB........................................................................................................................................................20
7.2 Required Information...................................................................................................................................................20
7.3 Planning........................................................................................................................................................................20
7.3.1 RF Planning...............................................................................................................................................................20
7.3.2 Network Planning......................................................................................................................................................21
7.3.3 Hardware Planning....................................................................................................................................................21
7.4 Deployment..................................................................................................................................................................21
7.4.1 Requirements.............................................................................................................................................................21
7.4.2 Data Preparation........................................................................................................................................................21
7.4.3 Precautions.................................................................................................................................................................33
7.4.4 Activation..................................................................................................................................................................34
7.4.5 Activation Observation..............................................................................................................................................39
7.4.6 Deactivation...............................................................................................................................................................48
7.6 Parameter Optimization................................................................................................................................................51
7.7 Troubleshooting............................................................................................................................................................51
8 Parameters.....................................................................................................................................54
9 Counters........................................................................................................................................98
10 Glossary.....................................................................................................................................102
11 Reference Documents.............................................................................................................103
Issue 02 (2013-05-31) Huawei Proprietary and Confidential iii

eRAN
MLB Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document explains the principles and procedures for mobility load balancing (MLB)
between cells, including air interface load monitoring, inter-cell load information exchange, and
load transfer. In addition, this document describes the parameters and implementation for MLB.
Any managed objects (MOs), parameters, alarms, or counters described below correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with the latest software release.
This document applies only to LTE FDD. Any "L" or "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 MLB
l Work with Huawei LTE 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: refers to a change in the MLB feature of a specific product version.
l Editorial change: refers to a change in wording or the addition of information that was not
described in the earlier version.
Document Versions
The document versions are as follows:
l 02 (2013-05-31)
Issue 02 (2013-05-31) Huawei Proprietary and Confidential 1

eRAN
l 01 (2013-04-28)
l Draft A (2013-01-30)
02 (2012-05-31)
Compared with Issue 01 (2013-04-28) of eRAN6.0, Issue 02 (2013-05-31) of eRAN6.0 includes
the following changes.
Change Type Change Description Parameter Change
Feature change None None
Editorial change Optimized some descriptions in 7.4.2 Data None

Preparation and 7.4.4 Activation.
01 (2013-04-28)
This is the first commercial release of eRAN6.0.
Compared with Draft A (2013-01-30) of eRAN6.0, Issue 01 (2013-04-28) of eRAN6.0 includes
Change Type Change Description Parameter Change
Feature change None None
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
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 RAN Information
Management (RIM)
procedures.

eRAN
Change Change Description Parameter Change

Type
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.4.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 intra- or inter-RAT cells
to maximize network resource usage, reduce the system congestion rate, increase the access
success rate, and improve user experience with services. To achieve these goals, MLB checks
the load status of cells, exchanges cell load information, and transfers load from busy cells to
cells with more available resources.
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
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 MLB, 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 For inter-RAT MLB, the eNodeB determines the target RAT based on user equipment
(UE) capabilities, service information, and subscriber profile IDs (SPIDs). Then, the
eNodeB selects a target cell based on the information about the inter-RAT 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
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
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)
check box is selected under the CellAlgoSwitch.MlbAlgoSwitch parameter.
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 results with the
specified MLB threshold.
Load information exchange is triggered for inter-frequency load balancing if the air interface
load of a cell is continuously equal to or greater than the sum of CellMLB.InterFreqMlbThd
(the threshold for starting inter-frequency load balancing) and CellMLB.LoadOffset. Load
balancing is preferentially triggered by GBR services over total services. If the PRB usage of
GBR services is greater than CellMLB.InterFreqMlbThd, load balancing is triggered by GBR
services. If the PRB usage of GBR services is smaller than CellMLB.InterFreqMlbThd but the
PRB usage of total services is greater than CellMLB.InterFreqMlbThd, load balancing is
triggered by total services. Services that triggering load balancing are distinguished in the uplink
and downlink. A load offset, CellMLB.LoadOffset, is added to prevent fluctuations from
frequently triggering and stopping MLB.
During load information exchange, if the air interface load of the cell is continuously less than
CellMLB.InterFreqMlbThd, the load information exchange is stopped.
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 with which there is no X2 interface
l Cells with a historical handover success rate less than 98%
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 a cell can exchange load information, the
eNodeB sends a RESOURCE STATUS REQUEST message to all the eNodeBs to which the

eRAN
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 subsequently receive regular 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 the following condition:
l The historical success rate of handovers from the serving cell to the neighboring cell is less
than 98%.
l The transport network layer load or hardware load of the neighboring cell is in the HighLoad
or Overload state.
l Services in the neighboring cell and the serving cell in the uplink or downlink by which
load balancing is triggered have a PRB usage difference that is less than
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.
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

eRAN
selects the UEs that perform GBR services. If the load balancing is triggered by total services,
the eNodeB selects UEs that perform 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 condition. This prevents ping-pong load balancing in
the transmission direction opposite to the MLB-triggering direction after the UE is transferred
to the neighboring cell.
In inter-frequency load balancing, there are two methods to transfer UEs that support inter-
frequency measurement and handover: blind handover and measurement-based handover. The
default method is measurement-based handover. If the InterFreqMlbBlindHo
(InterFreqMlbBlindHo) option of the CellAlgoSwitch.MlbHoMode parameter is selected, the
eNodeB transfers UEs to the target cells by blind handover.
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).
Based on the measurement results reported by the UEs, the eNodeB performs inter-frequency
handovers of 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).
If a UE is to be transferred and the eNodeB has learned the UE's SPID from the EPC, the UE will be
transferred only to the RATs or frequencies specified in the SPID configuration.
3.5 Performance Monitoring

Self-organizing network (SON) logs record the following information during a load balancing
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 failure during handovers
l Total PRB usage
Operators can query the SON logs to check the statistics on load balancing within each period.

eRAN
The eNodeB monitors the handover success rate of the source cells after UE handovers. 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
The decision on inter-RAT load sharing is based on the load of the 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 results with the
specified MLB threshold.
Inter-RAT load sharing is triggered if the cell load is continuously greater than or equal to the
sum of CellMLB.InterRatMlbThd and CellMLB.LoadOffset and if 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 cell load is continuously less than
CellMLB.InterRatMlbThd or the number of uplink synchronized UEs in the cell falls below
CellMLB.InterRatMlbUeNumThd.
4.2 Load Information Exchange

If the MlbLoadInfoSwitch(MlbLoadInfoSwitch) option of the
CellAlgoSwitch.MlbAlgoSwitch parameter is selected, the serving cell exchanges load
information with UTRAN cells through the RAN Information Management (RIM) procedures.
(If the MlbLoadInfoSwitch(MlbLoadInfoSwitch) option of the
CellAlgoSwitch.MlbAlgoSwitch parameter is not selected, the load status of the neighboring
UTRAN cells is not considered in target cell selection.) Based on the load information, the
eNodeB generates a target cell list by removing congested or overloaded UTRAN cells. If the
target cell list is empty, the eNodeB stops load sharing for the serving cell.
Selecting target cells based on the load status of the neighboring UTRAN cells applies to load
sharing for UEs in connected mode, but not to load sharing for UEs in idle mode.
NOTE
For details about the RIM procedures for load information exchange, see section 8c.2 in 3GPP TS 48.018
V10.6.0 (2012-05) and sections 8.13 and 8.14 in 3GPP TS 36.413 V10.6.0 (2012-06).
It is required that the EPC support Release 9-stipulated RIM procedures and the UTRAN support Release
10-stipulated RIM procedure for load information exchange.
4.3 Load Sharing Decision

If the neighboring cells of more than one RAT meet the requirements for load sharing, the
eNodeB selects the target RAT based on the UE capabilities and the following switch settings:
l If the UtranMlbSwitch(UtranMlbSwitch) option of the

CellAlgoSwitch.MlbAlgoSwitch parameter and the UtranPsHoSwitch
(UtranPsHoSwitch) option of the EnodebAlgoSwitch.HoModeSwitch parameter are
selected, UEs in connected mode are handed over to UTRAN cells.
l If the UtranIdleMlbSwitch(UtranIdleMlbSwitch) option of the
CellAlgoSwitch.MlbAlgoSwitch parameter is selected, UEs in idle mode are transferred
to UTRAN cells.
l If the GeranMlbSwitch(GeranMlbSwitch) option of the
CellAlgoSwitch.MlbAlgoSwitch parameter and the GeranPsHoSwitch

eRAN
(GeranPsHoSwitch) option of the EnodebAlgoSwitch.HoModeSwitch parameter are

selected, UEs are handed over to GERAN cells.
4.4 Load Sharing Execution

During inter-RAT load sharing, the serving cell rejects 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.
4.4.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
target cells, 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 condition. This prevents ping-pong load sharing in the transmission direction
opposite to the MLB-triggering direction after the UE is transferred to the neighboring cell.
Based on the measurement results, 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
measurement and handover: blind handover and measurement-based handover. The default
method is measurement-based handover. If the InterRatMlbBlindHo
(InterRatMlbBlindHo) option of the CellAlgoSwitch.MlbHoMode parameter is selected, the
eNodeB transfers UEs to the target cells by blind handover. If UEs do not support inter-RAT
handover, the eNodeB transfers UEs by blind handover.
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 the UtranPsHoSwitch
(UtranPsHoSwitch) or GeranPsHoSwitch(GeranPsHoSwitch) of the
EnodebAlgoSwitch.HoModeSwitch parameter is selected to enable handover. If handover is
enabled but the UEs do not support handover, the eNodeB performs redirections for load sharing.

eRAN
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).
If a UE is to be transferred and the eNodeB has learned the UE's SPID from the EPC, the UE will be
transferred only to the RATs or frequencies specified in the SPID configuration.
4.4.2 Transferring UEs in Idle Mode

If UtranIdleMlbSwitch(UtranIdleMlbSwitch) is selected under the
CellAlgoSwitch.MlbAlgoSwitch parameter 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 (which are regarded as UEs in idle mode) to
camp on the target UTRAN cell after their RRC connections are released. The eNodeB delivers
the instructions by including the dedicated-priority information in the RRCConnectionRelease
messages to the UEs.
This proportion is indirectly determined 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 actual
duration has a positive correlation with the initial duration and the number of uplink
synchronized UEs. Considering that a longer duration indicates a larger proportion of UEs in
idle mode to be transferred, the proportion of UEs in idle mode to be transferred also has a
positive correlation with the initial duration and the number of uplink synchronized UEs.
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 failure during handovers
l Total PRB usage
Operators can query the SON logs to check 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
The Intra-LTE Load Balancing feature increases the access success rate and reduces the
probability of triggering congestion control, because the Intra-LTE Load Balancing feature
transfers some load of an E-UTRAN cell to intra-RAT neighboring cells before the source E-
UTRAN cell becomes congested.
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
The Inter-RAT Load Sharing to UTRAN feature increases the access success rate and reduces
the probability of triggering congestion control, because the Inter-RAT Load Sharing to UTRAN

eRAN
MLB Feature Parameter Description 5 Related Features
feature transfers some load of an E-UTRAN cell to neighboring UTRAN cells before the source
E-UTRAN cell becomes congested.
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
The Inter-RAT Load Sharing to GERAN feature increases the admission success rate and
reduces the probability of triggering congestion control, because the Inter-RAT Load Sharing
to GERAN feature transfers some load of an E-UTRAN cell to neighboring GERAN cells before
the source E-UTRAN cell becomes congested.

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 of 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 of 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.
6.3 LOFD-001045 Inter-RAT Load Sharing to GERAN

System Capacity
The Inter-RAT Load Sharing to GERAN feature transfers some load of an E-UTRAN cell to
neighboring GERAN cells before the source E-UTRAN cell becomes congested, and, therefore,

eRAN
MLB Feature Parameter Description 6 Network Impact
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.

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:
l No holes exist in the coverage.

eRAN
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:
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

eRAN
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 Name Parameter ID Data Source Setting Notes
Load Offset CellMLB. Network plan This parameter

LoadOffset (negotiation not specifies an offset
required) applied to the
threshold value for
triggering MLB.
MLB is triggered
only when the load is
continuously 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.

eRAN
Load Difference CellMLB. Network plan This parameter

Threshold LoadDiffThd (negotiation not specifies the
required) minimum load
difference 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.
The recommended
value is 15. This
parameter is valid
only for intra-RAT
load balancing.
The values of the parameters in the CellShutdown and CellMLB MOs must meet the following
condition: The sum of the inter-frequency MLB threshold and the load offset is greater than the
sum of the uplink or downlink PRB usage threshold and offset for cell intelligent shutdown. The
following table describes the parameters contained in the CellShutdown MO.
Local cell ID CellShutdown. 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
Cell intelligent CellShutdown. Network plan This parameter

shutdown switch CellShutdownS- (negotiation not specifies whether to
witch required) enable cell intelligent
shutdown. Cell
intelligent shutdown
can be performed
only when this
parameter is set to
ON(On) and specific
conditions are met.
The recommended
value is OFF(Off).
Start time CellShutdown. Network plan This parameter

StartTime (negotiation not specifies the time to
required) start cell intelligent
shutdown.
The recommended
value is 00:00:00.
Stop time CellShutdown. Network plan This parameter

StopTime (negotiation not specifies the time to
required) stop cell intelligent
shutdown. If the stop
time for cell
intelligent shutdown
is not later than the
start time, the stop
time is regarded as
that time the next
day.
The recommended
value is 06:00:00.
Downlink PRB CellShutdown. Network plan This parameter

threshold DlPrbThd (negotiation not specifies the
required) downlink PRB usage
threshold for starting
or stopping cell
intelligent shutdown.
The recommended
value is 20.

eRAN
Downlink PRB CellShutdown. Network plan Cell intelligent

offset DlPrbOffset (negotiation not shutdown is stopped
required) when the average
downlink PRB usage
of the cell's inter-
frequency
neighboring cells
reaches the sum of
CellShutdown.DlPr
bThd and the value
of this parameter.
The recommended
value is 20.
Uplink PRB CellShutdown. Network plan This parameter

threshold UlPrbThd (negotiation not specifies the uplink
required) PRB usage threshold
for starting or
stopping cell
The recommended
value is 20.
Uplink PRB offset CellShutdown. Network plan Cell intelligent

UlPrbOffset (negotiation not shutdown is stopped
required) when the average
uplink PRB usage of
the cell's inter-
frequency
neighboring cells
reaches the sum of
CellShutdown.
UlPrbThd and the
value of this
parameter.
The recommended
value is 20.
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.

eRAN
Local cell ID CellAlgoSwitch. Network plan This parameter

identifies the cell
within an eNodeB.
The actual value
range is 0 to 17.
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.
RAT frequency SpidCfg. Network plan This parameter

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

eRAN

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.
Local cell ID CellAlgoSwitch. Network plan This parameter

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 UtranMlbSwitch
required) (UtranMlbSwitch)
check box under this
parameter specifies
whether to enable
load sharing with
UTRAN for UEs in
connected mode.
l If
UtranMlbSwitc
h
(UtranMlbSwitc
h) is selected, the
algorithm is
enabled.
l If
UtranMlbSwitc
h
(UtranMlbSwitc
h) is not selected,
the algorithm is
disabled.

eRAN
The
UtranIdleMlbS-
witch
(UtranIdleMLBS-
witch) check box
under this parameter
specifies whether to
enable load sharing
with UTRAN for
UEs in idle mode.
l If
UtranIdleMlbS-
witch
(UtranIdleMLB
Switch) is
selected, the
algorithm is
enabled.
l If
UtranIdleMlbS-
witch
(UtranIdleMLB
Switch) is not
selected, the
algorithm is
disabled.
If the
MlbLoadInfoS-
witch
(MlbLoadInfoS-
witch) check box is
selected, the eNodeB
considers UTRAN
cell load during load
sharing with
UTRAN.
If the
MlbLoadInfoS-
witch
(MlbLoadInfoS-
witch) check box is
not selected, the
eNodeB does not
consider UTRAN
cell load during load
sharing with
UTRAN.

eRAN
The
GeranMlbSwitch
(GeranMlbSwitch)
check box under this
parameter specifies
whether to enable
load sharing with
GERAN.
l If
GeranMlbSwitc
h
(GeranMlbSwit
ch) is selected,
the algorithm is
enabled.
l If
GeranMlbSwitc
h
(GeranMlbSwit
ch) 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.
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 selected,
the eNodeB cannot perform inter-RAT load
sharing using handovers. 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.

eRAN
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 continuously 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 continuously less than
CellMLB.InterRatMlbThd or the number
of uplink synchronized UEs in the cell falls
below CellMLB.InterRATMlbUe-
NumThd.
The default value is 75.
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 UE 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.

eRAN
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.
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

eRAN
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:
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.

eRAN
Table 7-2 Parameters for MLB

M Sheet in the Parameter Remarks
O Summary Group
Data File
Cell CELLALGOS MlbAlgoSwitc

Alg WITCH h
oS
wit
ch
Cell CELLMLB LocalCellId,

ML InterFreqMlbT
B hd,
InterRatMlbTh
d,
LoadExchange
Period,
LoadOffset,
LoadDiffThd,
InterRatMlbUe
NumThd,
InitValidPerio
d,
LoadTransferF
actor

eRAN
M Sheet in the Parameter Remarks

O Summary Group
Data File
EN ENODEBAL HoModeSwitc
ode GOSWITCH h
BAl
goS
wit
ch
Spi SPIDCFG Spid,

dCf InterFreqMlbS
g witch,
(Op InterRatMlbS-
tion witch
al)
Cell CELLSHUTD LocalCellId,

Shu OWN CellShutdown
tDo Switch,
wn StartTime,
(Op StopTime,
tion DlPrbThd,
al) 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 (CME 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 Advanced > Base Station Bulk Configuration > Export
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

eRAN
NOTE
l To view descriptions of the parameters in the MO, click in area 4 and press F1.
l Area 5 displays the details of a selected area-4 entry in vertical format. Click the Details icon to show
or hide this area.
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (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.
Command:
MOD CELLMLB: LocalCellId=xx, InterFreqMlbThd=XX;
Step 2 Run the MOD CELLALGOSWITCH command to enable the inter-frequency load balancing
algorithm.
Command:
MOD CELLALGOSWITCH: LocalCellId=xx, MlbAlgoSwitch=InterFreqMlbSwitch-1;
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.
Commands:
ADD SPIDCFG: Spid=xx, RatFreqPriorityInd=NOT_CFG, InterFreqMlbSwitch=TRUE;
MOD SPIDCFG: Spid=xx, InterFreqMlbSwitch=TRUE;
Step 4 (Optional) Run the MOD CELLSHUTDOWN command to set the parameters for cell
Command:
MOD CELLSHUTDOWN: LocalCellId=xx, CellShutdownSwitch=ON, StartTime=xx,
StopTime=xx, DlPrbThd=xx, DlPrbOffset=xx, UlPrbThd=xx, UlPrbOffset=xx;
----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.
Commands:

eRAN
MOD ENODEBALGOSWITCH: HoModeSwitch=UtranPsHoSwitch-1;

MOD ENODEBALGOSWITCH: HoModeSwitch=GeranPsHoSwitch-1;
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.
Command:
MOD CELLMLB: LocalCellId=0, InterRatMlbThd=xx, InterRatMlbUeNumThd=xx;
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.
Commands:
MOD CELLALGOSWITCH: LocalCellId=xx, MlbAlgoSwitch=UtranMlbSwitch-1;
MOD CELLALGOSWITCH: LocalCellId=xx, MlbAlgoSwitch=GeranMlbSwitch-1;
NOTE
When inter-RAT load sharing with UTRAN for UEs in connected mode is enabled, if the load status of
neighboring UTRAN cells needs to be considered in MLB, the MLB algorithm based on UTRAN
neighboring cell load status must be enabled. Run the DSP UTRANRIMLOADINFO command to query
the load status of neighboring UTRAN cells, which are obtained through the RIM procedures.
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.
Commands:
ADD SPIDCFG: Spid=xx, RatFreqPriorityInd=NOT_CFG, InterRatMlbSwitch=TRUE;
MOD SPIDCFG: Spid=xx, InterRatMlbSwitch=TRUE;
----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.
Command:
MOD CELLMLB: LocalCellId=xx, InterRatMlbThd=xx, InterRatMlbUeNumThd=xx,
InitValidPeriod=xx;
Step 2 Run the MOD CELLALGOSWITCH command to enable inter-RAT load sharing with
UTRAN for UEs in idle mode.
Command:
MOD CELLALGOSWITCH: LocalCellId=xx, MlbAlgoSwitch=UtranIdleMlbSwitch-1;
----End
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.

eRAN
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.
Figure 7-3 Usage of RB Monitoring dialog box

eRAN
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
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.

eRAN
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.
Figure 7-7 Entering information about a neighboring cell

eRAN
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
NOTE
For details about the types of load that trigger MLB, see eNodeB Performance Monitoring
Reference.
Step 4 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.

eRAN
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 Load
Based Interfreq RSRP threshold.
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 the 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
Mobility Load Balancing Threshold and Load Offset. Inject downlink UDP packets for UE2
at a rate of 2 Mbit/s.

eRAN
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 of "reduce-load-

in-serving-cell" exists, inter-RAT load sharing for UEs in connected mode is working correctly.
To use SON logs to verify whether MLB takes effect, perform the following steps:
Step 5 On the M2000 client, choose SON > SON log.
Step 6 Then in the Query SON log window, choose MLB Log under Log Category and Inter-RAT
Handover Statistics under Event Name. And then click Query to 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 the 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.4.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
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.

eRAN
Table 7-3 Parameters for MLB

MO Sheet in the Parameter Remarks
Summary Data Group
File
CELLALG CELLALGOSWI MlbAlgoSwitc

OSWITCH TCH h
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.
Command:
MOD CELLALGOSWITCH: LocalCellId=xx, MlbAlgoSwitch=InterFreqMlbSwitch-0;
Scenario 2: Inter-RAT Load Sharing

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.
Commands:

eRAN
MOD CELLALGOSWITCH: LocalCellId=xx, MlbAlgoSwitch=UtranMlbSwitch-0;

MOD CELLALGOSWITCH: LocalCellId=xx, MlbAlgoSwitch=UtranIdleMlbSwitch-0;
MOD CELLALGOSWITCH: LocalCellId=xx, 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.
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. As RIM
procedures are introduced in inter-RAT load sharing, the counters can be used to monitor whether
the transportation between E-UTRAN and UTRAN and the status of the EPC are normal. The
counters can also be used to evaluate the impact of RIM procedures on network elements (NEs)
and transmission based on the frequency of cell load change.
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

eRAN
Description Counter Name
L.RRCRedirection.E2G.Load Number of EUTRAN-to-GERAN RRC redirections

triggered because of high load
L.RIM.Load.E2W.Req Number of times the eNodeB sends load information

requests to WCDMA network
L.RIM.Load.E2W.Resp Number of times the eNodeB receives load information

responses from WCDMA network
L.RIM.Load.E2W.Update Number of times the eNodeB receives load information

updates from WCDMA network
7.6 Parameter Optimization

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

The thresholds directly determine the probabilities and effectiveness of the two types of
MLB.
l Load offset (specified by the Load Offset 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.

eRAN
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 eNodeB Alarm Reference.
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
eNodeB 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.

eRAN
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
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, and
UTRAN,
UTRAN idle,
GERAN,
CDMA2000 and
LoadInfo load
sharing
algorithms. If
one switch is
turned on, the
corresponding
algorithm is
enabled to
balance or share
the loads
between
neighboring

eRAN

Command
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-
frequency load
balancing is
enabled. If
InterFreqMlbS-
witch is set to
Off, inter-

eRAN

Command
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
between the
M2000 and the
eNodeB, but it is
no longer used
internally.
Therefore, avoid
using this

eRAN

Command
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-
witch is set to
Off, load sharing
with UTRAN
for UEs in idle
mode is
disabled. If
MlbLoadInfoS-
witch is set to

eRAN

Command
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
among all the
UTRAN cells
whose load
status is
obtained are
considered as
target cells in
load sharing
between an E-

eRAN

Command
UTRAN cell
and a UTRAN
cell.
GUI Value
Range:Intra-
FreqMlbSwitch
(IntraFreqMlbS-
witch),
InterFreqMlbS-
witch
(InterFreqMlbS-
witch),
UtranMlbSwitc
h
(UtranMlbSwitc
h),
GeranMlbSwitc
h
(GeranMlbSwit
ch),
CdmaMlbSwitc
h
(CdmaMlbSwit
ch), IntraFreqI-
dleMlbSwitch
(IntraFreqI-
dleMlbSwitch),
UtranIdleMlbS-
witch
(UtranIdleMlbS
witch),
MlbLoadInfoS-
witch
(MlbLoadInfoS-
witch)
Unit:None
Actual Value
Range:Intra-
FreqMlbSwitch,
InterFreqMlbS-
witch,
UtranMlbSwitc
h,
GeranMlbSwitc
h,
CdmaMlbSwitc
h, IntraFreqI-
dleMlbSwitch,
UtranIdleMlbS-

eRAN

Command
witch,
MlbLoadInfoS-
witch
Default
Value:IntraFreq
MlbSwitch:Off,
InterFreqMlbS
witch:Off,
UtranMlbSwitc
h:Off,
GeranMlbSwitc
h:Off,
CdmaMlbSwitc
h:Off,
IntraFreqIdleMl
bSwitch:Off,
UtranIdleMlbS
witch:Off,
MlbLoadInfoS
witch: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
performed if

eRAN

Command
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
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 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 cells
45 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
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
number of

eRAN

Command
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
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 removed in later
LOFD-001019 / 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.
If this switch is
TDLOFD-0010 Service based
turned off,
46 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
handover to CapSwitch: If
GERAN

eRAN

Command
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
disabled.
CdmaHrpdOpti

eRAN

Command
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
supports single
radio voice call
continuity

eRAN

Command
(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
disabled.
CdmaHrpdRedi
rectSwitch: If
this switch is

eRAN

Command
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
service. If this
switch is turned
off, an SRVCC
procedure is not
triggered when a

eRAN

Command
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
(Cdma1xRttVoi
pCapSwitch),
UtranPsHoSwit
ch
(UtranPsHoSwit
ch),
GeranPsHoSwit

eRAN

Command
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
Switch),
CdmaHrpdRedi
rectSwitch
(CdmaHrpdRed
irectSwitch),
Cdma1xRttRedi
rectSwitch
(Cdma1xRttRed

eRAN

Command
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,
Cdma1xRttSrvc
cSwitch,
UtranRedirectS-
witch,
GeranRedirectS
witch,
CdmaHrpdRedi
rectSwitch,
Cdma1xRttRedi
rectSwitch,

eRAN

Command
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
witch:Off,
CdmaHrpdRedi
rectSwitch:Off,
Cdma1xRttRedi
rectSwitch:Off,
BlindHoSwitch:
Off,
LcsSrvccSwitch
:Off,
AutoGapSwitch
:Off

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
CellShutdown LocalCellId LST None None Meaning:Indi-

CELLSHUTDO cates the local
WN ID of the cell. It
MOD uniquely
CELLSHUTDO identifies a cell
WN within a BS.
GUI Value
Range:0~17
Unit:None
Actual Value
Range:0~17
Default
Value:None

eRAN

Command
CellShutdown CellShutdownS- MOD LOFD-001042 / Intelligent Meaning:Indi-

witch CELLSHUTDO TDLOFD-0010 Power-Off of cates whether to
WN 42 Carriers in the enable or disable
LST Same Coverage intelligent
CELLSHUTDO power-off of
WN carriers in the
same coverage.
Intelligent
power-off of
carriers in the
same coverage
can be
performed only
when this
parameter is set
to ON and
specific
conditions are
met. For
intelligent
power-off of
carriers in the
same coverage,
each basic cell
must have its
intelligent
power-off of
carriers switch
enabled and the
UL or DL PRB
usage threshold
set to 0.
GUI Value
Range:OFF
(Off), ON(On)
Unit:None
Actual Value
Range:OFF, ON
Default
Value:OFF(Off)

eRAN

Command
CellShutdown StartTime MOD LOFD-001042 / Intelligent Meaning:Indi-

CELLSHUTDO TDLOFD-0010 Power-Off of cates the start
WN 42 Carriers in the time of
WN carriers in the
same coverage.
GUI Value
Range:
00:00:00~23:59
:59
Unit:None
Actual Value
Range:
00:00:00~23:59
:59
Default Value:0
CellShutdown StopTime MOD LOFD-001042 / Intelligent Meaning:Indi-

CELLSHUTDO TDLOFD-0010 Power-Off of cates the stop
WN 42 Carriers in the time of
WN carriers in the
same coverage.
If the stop time is
earlier than or
the same as the
start time, the
stop time is
assumed to be a
time of the next
day.
GUI Value
Range:
00:00:00~23:59
:59
Unit:None
Actual Value
Range:
00:00:00~23:59
:59
Default Value:
0.25

eRAN

Command
CellShutdown DlPrbThd MOD LOFD-001042 / Intelligent Meaning:Indi-

CELLSHUTDO TDLOFD-0010 Power-Off of cates the
WN 42 Carriers in the downlink PRB
LST Same Coverage threshold for
CELLSHUTDO starting
WN intelligent
power-off of
carriers in the
same coverage
for the cell.
GUI Value
Range:0~100
Unit:%
Actual Value
Range:0~100
Default Value:
20

eRAN

Command
CellShutdown DlPrbOffset MOD LOFD-001042 / Intelligent Meaning:Indi-

CELLSHUTDO TDLOFD-0010 Power-Off of cates the
WN 42 Carriers in the downlink PRB
LST Same Coverage offset for
CELLSHUTDO stopping
WN intelligent
power-off of
carriers in the
same coverage
for the cell. The
downlink PRB
threshold for
stopping
intelligent
power-off of
carriers in the
same coverage
for the cell is
equal to the sum
of the downlink
PRB threshold
for starting
intelligent
power-off of
carriers in the
same coverage
and the value of
this parameter.
GUI Value
Range:0~100
Unit:%
Actual Value
Range:0~100
Default Value:
20

eRAN

Command
CellShutdown UlPrbThd MOD LOFD-001042 / Intelligent Meaning:Indi-

CELLSHUTDO TDLOFD-0010 Power-Off of cates the uplink
WN 42 Carriers in the PRB threshold
LST Same Coverage for starting
CELLSHUTDO intelligent
WN power-off of
carriers in the
same coverage
for the cell.
GUI Value
Range:0~100
Unit:%
Actual Value
Range:0~100
Default Value:
20

eRAN

Command
CellShutdown UlPrbOffset MOD LOFD-001042 / Intelligent Meaning:Indi-

CELLSHUTDO TDLOFD-0010 Power-Off of cates the uplink
WN 42 Carriers in the PRB offset for
LST Same Coverage stopping
CELLSHUTDO intelligent
WN power-off of
carriers in the
same coverage
for the cell. The
uplink PRB
threshold for
stopping
intelligent
power-off of
carriers in the
same coverage
for the cell is
equal to the sum
of the uplink
PRB threshold
for starting
intelligent
power-off of
carriers in the
same coverage
and the value of
this parameter.
GUI Value
Range:0~100
Unit:%
Actual Value
Range:0~100
Default Value:
20

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 a RAT/
LST SPIDCFG 5401 frequency
priority. If this
parameter is set
to CFG, UEs
preferentially
camp on the
RAT or
frequency. If
this parameter is
set to
NOT_CFG, UEs
do not
preferentially
camp on the
RAT or
frequency.
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 a
TDLOFD-0010 on SPID RAT/frequency
LST SPIDCFG 5401 priority group.
GUI Value
Range:0~255
Unit:None
Actual Value
Range:0~255
Default Value:0

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 and
FALSE indicate
that inter-
frequency load
balancing is
allowed and
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
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
Inter-RAT Load and FALSE
LOFD-001045 / Sharing to indicate that
TDLOFD-0010 GERAN inter-RAT load
45 sharing is
allowed and
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
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

eRAN

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,
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

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 LOFD-00105401 Camp & Handover

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

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

oad.ExecAttOut frequency handover TDLOFD-001032 Balancing
execution attempts Intra-LTE Load
triggered because of Balancing
high load
1526728528 L.HHO.InterFreq.L Number of LOFD-001032 Intra-LTE Load

oad.ExecSuccOut successful inter- TDLOFD-001032 Balancing
frequency handover Intra-LTE Load
executions triggered Balancing
because of high load

eRAN

Description
1526728529 L.IRATHO.E2W.L Number of inter- LOFD-001044 Inter-RAT Load

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

oad.ExecAttOut RAT handover TDLOFD-001044 Sharing to UTRAN
execution attempts Inter-RAT Load
from E-UTRAN to Sharing to UTRAN
WCDMA network
high load
1526728531 L.IRATHO.E2W.L Number of LOFD-001044 Inter-RAT Load

oad.ExecSuccOut successful inter- TDLOFD-001044 Sharing to UTRAN
RAT handover Inter-RAT Load
executions from E- Sharing to UTRAN
UTRAN to
WCDMA network
high load
1526728532 L.IRATHO.E2G.Lo Number of inter- LOFD-001045 Inter-RAT Load

ad.PrepAttOut RAT handover TDLOFD-001045 Sharing to GERAN
preparation attempts Inter-RAT Load
from E-UTRAN to Sharing to GERAN
GERAN triggered
1526728533 L.IRATHO.E2G.Lo Number of inter- LOFD-001045 Inter-RAT Load

ad.ExecAttOut RAT handover TDLOFD-001045 Sharing to GERAN
execution attempts Inter-RAT Load
from E-UTRAN to Sharing to GERAN
GERAN triggered
1526728534 L.IRATHO.E2G.Lo Number of LOFD-001045 Inter-RAT Load

ad.ExecSuccOut successful inter- TDLOFD-001045 Sharing to GERAN
RAT handover Inter-RAT Load
executions from E- Sharing to GERAN
UTRAN to GERAN
high load

eRAN

Description
1526728535 L.RRCRedirection. Number of LOFD-001044 Inter-RAT Load

E2W.Load redirections from E- TDLOFD-001044 Sharing to UTRAN
UTRAN to Inter-RAT Load
WCDMA network Sharing to UTRAN
high load
1526728536 L.RRCRedirection. Number of LOFD-001045 Inter-RAT Load

E2G.Load redirections from E- TDLOFD-001045 Sharing to GERAN
UTRAN to GERAN Inter-RAT Load
triggered because of Sharing to GERAN
high load

dPri.GERAN.High that GERAN is TDLOFD-0010540 Based on SPID
configured as the 1 Camp & Handover
highest frequency Based on SPID
priority in an LOFD-001044
IMMCI IE TDLOFD-001044 Inter-RAT Load
Sharing to UTRAN
LOFD-001112
Inter-RAT Load
Sharing to UTRAN
MOCN Flexible
Priority Based
Camping

dPri.LTE.High that E-UTRAN is TDLOFD-0010540 Based on SPID
configured as the 1 Camp & Handover
highest frequency Based on SPID
priority in an LOFD-001044
IMMCI IE TDLOFD-001044 Inter-RAT Load
Sharing to UTRAN
LOFD-001112
Inter-RAT Load
Sharing to UTRAN
MOCN Flexible
Priority Based
Camping
1526728949 L.RIM.Load.E2W. Number of load LOFD-001044 Inter-RAT Load

Req requests from TDLOFD-001044 Sharing to UTRAN
eNodeB to Inter-RAT Load

Resp responses from TDLOFD-001044 Sharing to UTRAN
WCDMA network Inter-RAT Load
to eNodeB Sharing to UTRAN

eRAN

Description

Update updates from TDLOFD-001044 Sharing to UTRAN
eNodeB to Inter-RAT Load

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. Admission and Congestion Control Feature Parameter Description
7. Mobility Management in Connected Mode Feature Parameter Description
8. RAN Sharing Feature Parameter Description
9. Transport Resource Management Feature Parameter Description
10. eNodeB Initial Configuration Guide


MLB (eRAN6.0 02)

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 (eRAN6.0 02)

Hochgeladen von

Copyright:

Verfügbare Formate

eRAN

MLB Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2013-05-31) Huawei Proprietary and Confidential i

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

3 Inter-Frequency Load Balancing................................................................................................7

4 Inter-RAT Load Sharing.............................................................................................................12

Issue 02 (2013-05-31) Huawei Proprietary and Confidential ii

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

Issue 02 (2013-05-31) Huawei Proprietary and Confidential iii

1 About This Document

1.2 Intended Audience

1.3 Change History

Issue 02 (2013-05-31) Huawei Proprietary and Confidential 1

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

Editorial change Optimized the descriptions of None

Change Change Description Parameter Change

Feature In inter-RAT load sharing to Added the MlbLoadInfoSwitch

Issue 02 (2013-05-31) Huawei Proprietary and Confidential 2

Change Change Description Parameter Change

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 02 (2013-05-31) Huawei Proprietary and Confidential 3

RAT is short for radio access technology.

Issue 02 (2013-05-31) 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 02 (2013-05-31) 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 02 (2013-05-31) Huawei Proprietary and Confidential 6

3 Inter-Frequency Load Balancing

Issue 02 (2013-05-31) Huawei Proprietary and Confidential 7

3.1 Load Measurement and Evaluation

3.2 Load Information Exchange

3.2.1 Neighboring Cell Selection

3.2.2 Inter-eNodeB Cell Load Information Exchange

Issue 02 (2013-05-31) Huawei Proprietary and Confidential 8

3.3 Load Balancing Decision

3.4 Load Balancing Execution

Issue 02 (2013-05-31) Huawei Proprietary and Confidential 9

3.5 Performance Monitoring

l Number of UEs that are handed over to target cells

Issue 02 (2013-05-31) Huawei Proprietary and Confidential 10

Issue 02 (2013-05-31) Huawei Proprietary and Confidential 11

4 Inter-RAT Load Sharing

Issue 02 (2013-05-31) Huawei Proprietary and Confidential 12

4.1 Load Measurement and Evaluation

4.2 Load Information Exchange

4.3 Load Sharing Decision