0% found this document useful (1 vote)

264 views63 pages

Feature Parameter Description: MLB eRAN3.0

Uploaded by

Sergio Buonomo

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (1 vote)

264 views63 pages

Feature Parameter Description: MLB eRAN3.0

Uploaded by

Sergio Buonomo

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 63

MLB

eRAN3.0
Feature Parameter Description

Issue 07

Date 2013-05-20

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 the 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
eRAN
MLB Contents

Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience ........................................................................................................................ 1-1
1.3 Change History.............................................................................................................................. 1-1

2 MLB Overview ............................................................................................................................2-1

2.1 Basic Concepts ............................................................................................................................. 2-1
2.1.1 Cell Load .............................................................................................................................. 2-1
2.1.2 Source Cell and Target Cell .................................................................................................. 2-2
2.1.3 Cell Individual Offset............................................................................................................. 2-2
2.2 MLB Procedure ............................................................................................................................. 2-2

3 Intra-Frequency Load Balancing ..........................................................................................3-1

3.1 Load Measurement and Evaluation .............................................................................................. 3-1
3.2 Load Information Exchange .......................................................................................................... 3-1
3.2.1 Neighboring Cell Selection ................................................................................................... 3-2
3.2.2 Inter-eNodeB Cell Load Information Exchange .................................................................... 3-2
3.3 Load Balancing Decision ............................................................................................................... 3-2
3.4 Load Balancing Execution............................................................................................................. 3-3
3.4.1 Execution for UEs in Connected Mode ................................................................................ 3-3
3.4.2 Execution for UEs in Idle Mode ............................................................................................ 3-4
3.5 Performance Monitoring and Adjustment ...................................................................................... 3-4

4 Inter-Frequency Load Balancing ..........................................................................................4-1

4.1 Load Measurement and Evaluation .............................................................................................. 4-1
4.2 Load Information Exchange .......................................................................................................... 4-1
4.2.1 Neighboring Cell Selection ................................................................................................... 4-1
4.2.2 Inter-eNodeB Cell Load Information Exchange .................................................................... 4-2
4.3 Load Balancing Decision ............................................................................................................... 4-2
4.4 Load Balancing Execution............................................................................................................. 4-2
4.5 Performance Monitoring ................................................................................................................ 4-3

5 Inter-RAT Load Sharing ...........................................................................................................5-1

5.1 Load Measurement and Evaluation .............................................................................................. 5-1
5.2 Load Sharing Decision .................................................................................................................. 5-1
5.3 Load Sharing Execution ................................................................................................................ 5-1
5.3.1 Transferring UEs in Connected Mode .................................................................................. 5-1
5.3.2 Transferring UEs in Idle Mode .............................................................................................. 5-2
5.4 Performance Monitoring ................................................................................................................ 5-2

6 Related Features .......................................................................................................................6-1

6.1 Required Features ........................................................................................................................ 6-1
6.2 Mutually Exclusive Features ......................................................................................................... 6-1

Issue 07 (2013-05-20) Huawei Proprietary and Confidential i

6.3 Affected Features .......................................................................................................................... 6-1

7 Impact on the Network ............................................................................................................7-1

7.1 Impact on System Capacity........................................................................................................... 7-1
7.2 Impact on Network Performance ................................................................................................... 7-1

8 Engineering Guidelines...........................................................................................................8-1
8.1 When to Use MLB ......................................................................................................................... 8-1
8.2 Information to Be Collected ........................................................................................................... 8-1
8.3 Network Planning .......................................................................................................................... 8-1
8.3.1 RF Planning .......................................................................................................................... 8-1
8.3.2 Network Topology ................................................................................................................. 8-1
8.3.3 Hardware Planning ............................................................................................................... 8-1
8.4 Deploying MLB .............................................................................................................................. 8-1
8.4.1 Deployment Requirements ................................................................................................... 8-1
8.4.2 Data Preparation .................................................................................................................. 8-2
8.4.3 Precautions ........................................................................................................................... 8-8
8.4.4 Feature Activation ................................................................................................................. 8-9
8.4.5 Activation Observation .........................................................................................................8-11
8.4.6 Deactivation ........................................................................................................................ 8-21
8.5 Performance Optimization ........................................................................................................... 8-21
8.5.1 Monitoring ........................................................................................................................... 8-21
8.5.2 Parameter Optimization ...................................................................................................... 8-21
8.6 Troubleshooting ........................................................................................................................... 8-21
8.6.1 Serving Cell Not Initiating Load Information Exchange for Inter-Frequency Load Balancing
..................................................................................................................................................... 8-22
8.6.2 Failing to InitiateInter-RAT Load Sharing with UTRAN for UEs in Connected Mode ......... 8-23
8.6.3 Failing to Initiate Inter-RAT Load Sharing with UTRAN for UEs in Idle Mode .................... 8-23

9 Parameters .................................................................................................................................9-1
10 Counters .................................................................................................................................10-1
11 Glossary ..................................................................................................................................11-1
12 Reference Documents .........................................................................................................12-1

Issue 07 (2013-05-20) Huawei Proprietary and Confidential ii

1 Introduction
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 engineering guidelines for MLB.
Any managed objects (MOs), parameters, alarms, or counters described in this document correspond to
the software release delivered with this document. In the event of updates, the updates will be described
in the product documentation delivered with the latest software release.

1.2 Intended Audience

This document is intended for:
 Personnel who need to understand MLB
 Personnel who work with Huawei Long Term Evolution (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:
 Feature change: refers to a change in the MLB feature of a specific product version.
 Editorial change: refers to a change in wording or the addition of information that was not described in
the earlier version.

Document Issues
The document issues are as follows:
 07 (2013-05-20)
 06 (2013-02-27)
 05 (2012-12-29)
 04 (2012-09-20)
 03 (2012-06-30)
 02 (2012-05-11)
 01 (2012-03-30)
 Draft A (2012-01-10)

07 (2013-05-20)
Compared with issue 06 (2012-02-27) of eRAN3.0, issue 07 (2013-05-20) of eRAN3.0 includes the
following changes.

Change Type Change Description Parameter Change

Feature change None None

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 1-1

Change Type Change Description Parameter Change

Editorial change Optimized the descriptions of types None
of services that trigger
inter-frequency load balancing and
inter-RAT load sharing. For details,
see chapter 4 "Inter-Frequency Load
Balancing" and chapter 5 "Inter-RAT
Load Sharing."

06 (2013-02-27)
Compared with issue 05 (2012-12-29) of eRAN3.0, issue 06 (2013-02-27) of eRAN3.0 includes the
following changes.

Change Type Change Description Parameter Change

Feature change Added the handover switches for Added the
inter-RAT MLB. For details, see EnodebAlgoSwitch.HoModeSwi
chapter 5 "Inter-RAT Load Sharing." tch parameter.
Editorial change Revised the description of inter-RAT None
load sharing.

05 (2012-12-29)
Compared with issue 04 (2012-09-20) of eRAN3.0, issue 05 (2012-12-29) of eRAN3.0 includes the
following changes.

Change Type Change Description Parameter Change

Feature change None None
Editorial change Added the application scenarios of None
inter-RAT load sharing and relevant
engineering guidelines. For details,
see chapter 5 "Inter-RAT Load
Sharing" and chapter 8 "Engineering
Guidelines."

04 (2012-09-20)
Compared with issue 03 (2012-06-30) of eRAN3.0, issue 04 (2012-09-20) of eRAN3.0 includes the
following changes.

Change Type Change Description Parameter Change

Feature change Modified the implementation of Added the following parameters:
inter-RAT load sharing. For  CellMLB.InterRATMlbUeNumThd
details, see chapter 5
 CellMLB.InitValidPeriod

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 1-2

"Inter-RAT Load Sharing." Added the option

UtranIdleMlbSwitch(UtranIdleMLBSwitch)
to the CellAlgoSwitch.MlbAlgoSwitch
parameter.
Editorial change None None

03 (2012-06-30)
Compared with issue 02 (2012-05-11) of eRAN3.0, issue 03 (2012-06-30) of eRAN3.0 includes the
following changes.

Change Type Change Description Parameter Change

Feature change None None
Editorial change Revised the technical descriptions of intra-frequency None
load balancing and inter-frequency load balancing.

02 (2012-05-11)
Compared with issue 01 (2012-03-30) of eRAN3.0, issue 02 (2012-05-11) of eRAN3.0 includes the
following changes.

Change Type Change Description Parameter Change

Feature change None None
Editorial change Revised the technical descriptions of inter-frequency None
load balancing and inter-RAT load sharing.

01 (2012-03-30)
This is the first official release.
Compared with draft A (2012-01-10) of eRAN3.0, issue 01 (2012-03-30) of eRAN3.0 includes the
following changes.

Change Type Change Description Parameter Change

Feature change Removed one criterion, allocation/retention priority (ARP) of None
services, from the evaluation to determine which UEs are to
be transferred to the target inter-frequency or inter-RAT cell
for load balancing purposes.
Editorial change Revised chapter 8 "Engineering Guidelines." None

Draft A (2012-01-10)
This is a draft.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 1-3

Compared with issue 02 (2011-12-24) of eRAN2.2, draft A (2012-01-10) of eRAN3.0 includes the
following changes.

Change Type Change Description Parameter Change

Feature change None None
Editorial change Prepared this document by splitting the Load Control None
Feature Parameter Description into Admission and
Congestion Control Feature Parameter Description and
MLB Feature Parameter Description.
 Added chapters 6 "Related Features" and 7 "Impact on None
the Network."
 Optimized the technical description.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 1-4

2 MLB 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.

Based on network deployment, cell frequencies, and RATs, MLB can be classified into intra-frequency
load balancing, inter-frequency load balancing, and inter-RAT load sharing.
MLB involves the following optional features:
 LOFD-001032 Intra-LTE Load Balancing
 LOFD-001044 Inter-RAT Load Sharing to UTRAN
 LOFD-001045 Inter-RAT Load Sharing to GERAN

2.1 Basic Concepts

2.1.1 Cell Load
MLB considers the following types of load: air interface load, hardware load, and transport network layer
load, as shown in Figure 2-1.
Figure 2-1 Different types of load and their positions

 The air interface load is represented by the uplink (UL) and DL physical resource block (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).
 The transport network layer load is represented by the S1 bandwidth usage. For details, see Transport
Resource Management Feature Parameter Description.
 The hardware load is represented by the hardware resource usage, such as the central processing
unit (CPU) and digital signal processing (DSP) hardware usage.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 2-1

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 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.1.4 Cell Individual Offset

For intra-frequency load balancing, a cell individual offset (CIO) value can be set for each serving cell
and its neighboring cells. Ocn described in the subsequent sections denotes the CIO for a neighboring
cell.
The CIO value is used to adjust the boundary of the associated cell for handovers. A larger Ocn value
entails a higher probability of a handover from the serving cell to the neighboring cell. For details about
the CIO, see 3GPP TS 36.331.

2.2 MLB Procedure

MLB can be performed between intra-frequency, inter-frequency, and inter-RAT cells. A cell can be
configured with more than one of the three types of neighboring cells. When the three types are all
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 all of them are turned on, the
three 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, chapter 8 "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 guaranteed bit
rate (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 UL and DL 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

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 2-2

− For intra- and 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.
− 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 handovers or it may be cell reselection. If UEs do not support inter-RAT handover, the
UEs are redirected to another cell.
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.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 2-3

3 Intra-Frequency Load Balancing

Intra-frequency load balancing is classified into two types: load balancing for UEs in connected mode
and load balancing for UEs in idle mode. The two types are described as follows:
 Among UEs in connected mode, the eNodeB selects appropriate cell edge users (CEUs) and hands
over these CEUs to intra-frequency neighboring cells. In addition, the source and target cells are
coordinated in changing Ocn values to prevent ping-pong handovers.
 Load balancing for UEs in idle mode is a type of preliminary balancing. It controls camping of the UEs
on cells before services start for them. This method prevents potential load imbalance that may be
caused by service activation on these UEs.
This type of load balancing is dependent on load balancing for UEs in connected mode.
To increase the probability of handovers or cell reselection for UEs at the cell edge, intra-frequency load
balancing modifies certain parameters related to handovers or cell reselection. These parameters are
determined in compliance with 3GPP TS 36.902. Because the load status of one pair of cells is different
from that of another pair, intra-frequency load balancing adjusts only the parameters that are specific to
each pair of serving and neighboring cells:

 In the intra-frequency handover entering condition Mn  Ofn  Ocn  Hys  Ms  Ofs  Ocs  Off , the
value of Ocn is adjusted.

 In the intra-frequency cell reselection condition Qmeas, n  Qoffset  Qmeas, s  Qhyst , the value of
Qoffset is adjusted.
Ocn is the cell-specific offset for the neighboring cell and applies to UEs in connected mode. Qoffset is
the offset between two cells and applies to UEs in idle mode.

NOTE
For details about the preceding formulas and parameters, see 3GPP TS 36.902.

Intra-frequency load balancing is enabled if the IntraFreqMlbSwitch(IntraFreqMlbSwitch) check box

or the IntraFreqMlbSwitch(IntraFreqMlbSwitch) and
IntraFreqIdleMlbSwitch(IntraFreqIdleMlbSwitch) check boxes are selected under the
CellAlgoSwitch.MlbAlgoSwitch parameter.
The following sections describe the procedure for intra-frequency load balancing.

3.1 Load Measurement and Evaluation

The eNodeB periodically measures cell resources in use and compares the results with the specified
MLB threshold. If the air interface load of a cell is continuously equal to or greater than the sum of
CellMLB.IntraFreqMlbThd (the threshold for starting intra-frequency load balancing) and
CellMLB.LoadOffset, load information exchange is triggered for intra-frequency load balancing. A load
offset, CellMLB.LoadOffset, is added to prevent fluctuations from frequently triggering and stopping
MLB. Considering that GBR services have higher priorities than non-GBR services, load evaluation and
exchange triggering for GBR services take precedence over those for non-GBR services. During load
information exchange, if the air interface load of the cell is continuously less than
CellMLB.IntraFreqMlbThd, the load information exchange is stopped.

3.2 Load Information Exchange

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.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 3-1

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 intra-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:
 Cells with which there is no X2 interface
 Cells with a historical handover success rate less than 99%
The way the cells exchange load information varies depending on the cell type:
 If all the neighboring cells are intra-eNodeB cells, the eNodeB can acquire the load status of the cells
directly before making a load balancing decision.
 If the neighboring cells include inter-eNodeB cells, the eNodeB can acquire the load status of the
inter-eNodeB neighboring cells only through the X2 interface.

3.2.2 Inter-eNodeB Cell Load Information Exchange

After determining the inter-eNodeB cells with which a cell exchanges load information, the eNodeB
sends a RESOURCE STATUS REQUEST message to all the eNodeBs that the inter-eNodeB cells
belong to. 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.
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 RESOURCE STATUS UPDATE messages at intervals from that neighboring cell. If the serving
cell receives a RESOURCE STATUS FAILURE message from a neighboring cell, the neighboring cell is
not considered as 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.

For more details about the procedure for load information exchange, see 3GPP TS 36.423.

3.3 Load Balancing Decision

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 non-GBR
services. Then, the eNodeB generates a formal candidate cell list by removing the cells that meet any of
the following conditions:
 The previous CIO adjustment for the candidate cell failed, or the CIO value for the candidate cell was
restored due to performance deterioration after the previous adjustment.
 The serving cell meets the triggering condition for load balancing in the uplink or downlink, and the
load difference between the candidate cell and the serving cell in the uplink or downlink is less than
CellMLB.LoadDiffThd.
 The candidate cell does not have any CEUs within the overlapping coverage area with the serving cell.
 The success rate of handovers from the serving cell to the candidate cell is lower than 99%.
 The S1 bandwidth usage or hardware resource usage of the target cell is HighLoad or Overload.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 3-2

If the formal candidate cell list is empty, the eNodeB stops the evaluation on load balancing.
If the formal candidate cell list contains more than one cell, the eNodeB categorizes them as classes A,
B, and C, which are described as follows:
 Class A: cells whose uplink load and downlink load are both less than CellMLB.IntraFreqMlbThd
 Class B: cells whose uplink or downlink load exceeds CellMLB.IntraFreqMlbThd
 Class C: cells whose uplink load and downlink load both exceed CellMLB.IntraFreqMlbThd
Classes A, B, and C are laid out in descending order of priority. If there are multiple cells in one class, the
eNodeB selects the cell with the largest load difference from the serving cell as the target cell.
In summary, the eNodeB selects a target cell by taking the cell class as the first priority and the load
difference as the second priority.

NOTE
It is recommended that the CellMLB.IntraFreqMlbThd parameter be set to the same value throughout the network.

3.4 Load Balancing Execution

Intra-frequency load balancing involves UEs in connected mode and those in idle mode:
 eNodeBs change CIO values to increase the probability that CEUs in connected mode are handed
over from the source cell. The CIO values changed in the source and target cells are coordinated to
prevent ping-pong handovers. Based on the measurement configuration containing the updated CIO
values, the UEs perform intra-frequency measurements. If the measurement results meet handover
conditions, the eNodeB performs intra-frequency handovers.
 Based on each updated CIO value, the eNodeB changes the Qoffset value of each cell and delivers
the updated Qoffset value to UEs in idle mode. The UEs perform measurements, and the eNodeB
performs cell reselection according to the intra-frequency cell reselection criteria.

3.4.1 Execution for UEs in Connected Mode

Intra-frequency load balancing for UEs in connected mode is enabled if the
IntraFreqMlbSwitch(IntraFreqMlbSwitch) option of the CellAlgoSwitch.MlbAlgoSwitch parameter is
selected.
To execute load balancing, the source and target cells need to be coordinated in changing the CIO
values. During the CIO adjustment procedure, the source cell sends a CIO adjustment request to the
target cell, and both cells adjust the CIO values. For details about the CIO adjustment procedure, see
3GPP TS 36.423.
The Ocn value needs to be increased to raise the probability of handovers to the target cell. The value
must be within its adjustment range. If the Ocn value is beyond the range, the target cell rejects the
request and notifies the source cell.
If the target cell sends the source cell a positive response, the CIO values are adjusted in the source and
target cells. The source cell determines the time to perform handovers based on the adjusted CIO value
of the source cell. The target cell sends the adjusted CIO value to the UEs that newly access or are
newly handed over in the target cell. The UEs determine the time to perform handovers based on the
adjusted CIO value. Load balancing is performed by transferring UEs with the corresponding type of
services (for example, uplink or downlink services, GBR or non-GBR services) from one cell to another
to reduce the load difference of that service type between the cells.
For details about intra-frequency handovers, see Mobility Management in Connected Mode Feature
Parameter Description.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 3-3

3.4.2 Execution for UEs in Idle Mode

Intra-frequency load balancing for UEs in idle mode is enabled if the
IntraFreqIdleMlbSwitch(IntraFreqIdleMlbSwitch) and IntraFreqMlbSwitch(IntraFreqMlbSwitch)
check boxes are both selected under the CellAlgoSwitch.MlbAlgoSwitch parameter.
IntraFreqIdleMlbSwitch(IntraFreqIdleMlbSwitch) must be on or off for all eNodeBs throughout a
network. Otherwise, some UEs will encounter frequent cell reselections.
The cell coverage is the same for UEs in idle mode and UEs in connected mode. Therefore, the
handover boundary for UEs in connected mode is generally the same as the reselection boundary for
UEs in idle mode. To ensure consistent coverage after the adjustments, the Qoffset adjustment should
be contrary to CIO adjustment. That is, if the CIO value for the neighboring cell is increased, the Qoffset
value should be decreased. After the CIO and then Qoffset are successfully adjusted, the source and
target cells broadcast the new Qoffset value to control cell reselection for UEs in idle mode. For details
about cell reselection, see Idle Mode Management Feature Parameter Description.

3.5 Performance Monitoring and Adjustment

After CIO adjustment, cell performance monitoring is started in the source and target cells. 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 the target cell in intra-frequency load balancing. If the performance (for example, in terms of the
call drop rate and handover success rate) of the target cell meets the requirements during the monitoring
period, the CIO values are successfully adjusted. If its performance deteriorates and fails to meet the
requirements, the target cell instructs the source cell to restore the CIO values together with the target
cell.
The cell load distribution and the load difference between the two cells change after CIO adjustment.
The load of the cell with a lighter load gradually increases, and the load of the cell with a heavier load
gradually decreases. If measurement control is performed based on the adjusted CIO values, a new load
imbalance may occur. In addition, the adjusted CIO values are not the optimal values for handovers.
Therefore, if the load difference between the two cells is almost zero or if the load of both cells is less
than CellMLB.IntraFreqMlbThd, load balancing between the two cells is stopped. Then, the adjusted
CIO values are no longer sent to newly admitted UEs, and the UEs using the adjusted CIO values for
measurement control retain the adjusted CIO values.
For details about the performance variations (premature or delayed handovers), see MRO Feature
Parameter Description.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 3-4

4 Inter-Frequency Load Balancing

Inter-frequency load balancing transfers some UEs in connected mode to inter-frequency neighboring
cells 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.

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

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

4.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:
 Cells with which there is no X2 interface
 Cells with a historical handover success rate less than 98%

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 4-1

 Cells for which the EutranInterFreqNCell.NoHoFlag parameter is set to FORBID_HO_ENUM(Forbid

Ho)

4.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 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 as 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.

4.3 Load Balancing Decision

The eNodeB generates a target cell list for in inter-frequency scenarios based on the load differences
between 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 formal candidate cell list by removing the cells that meet any of
the following conditions:
 Cells with a historical handover success rate less than 98%
 The S1 bandwidth usage or hardware resource usage of the target cell is HighLoad or Overload.
 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 the 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 by adjusting the CIO as long as the target cell meets the load balancing condition.

4.4 Load Balancing Execution

Inter-frequency load balancing involves only UEs in connected mode. The eNodeB selects some UEs
based on the frequency information about the target cells, frequency capabilities of UEs, PRB usage in
the target cells, and type of services that trigger load balancing in the serving cell. Then, the eNodeB
instructs the UEs to transfer to the target cells. If load balancing is triggered by GBR services, the
eNodeB selects the UEs that perform GBR services. If the load balancing is triggered by total services,
the eNodeB selects UEs that perform non-GBR services.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 4-2

Based on the measurement results reported by the UEs, the eNodeB performs inter-frequency
handovers on UEs that meet the handover conditions. For details about inter-frequency handovers, see
Mobility Management in Connected Mode Feature Parameter Description.

NOTE
An SPID is sent by the evolved packet core (EPC) 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. Subscriber profiles
are determined by the operators' network plans. 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.5 Performance Monitoring

SON logs record the following information during a load sharing period:
 Number of UEs that are handed over to target cells
 Number of UEs whose RRC connections are reestablished with the target cells because of radio link
failure during handovers
 Total PRB usage
Operators can query the SON logs to check the statistics on load balancing within each period.
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 the target cell in inter-frequency load balancing.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 4-3

5 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:
 Transfers some UEs in connected mode to the target cell.
 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.

5.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 section 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.

5.2 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:
 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.
 If the UtranIdleMlbSwitch(UtranIdleMlbSwitch) option of the CellAlgoSwitch.MlbAlgoSwitch
parameter is selected, UEs in idle mode are transferred to UTRAN cells.
 If the GeranMlbSwitch(GeranMlbSwitch) option of the CellAlgoSwitch.MlbAlgoSwitch parameter
and the GeranPsHoSwitch(GeranPsHoSwitch) option of the EnodebAlgoSwitch.HoModeSwitch
parameter are selected, UEs are handed over to GERAN cells.

5.3 Load Sharing Execution

Inter-RAT load sharing execution is performed on UEs in connected mode or idle mode.

5.3.1 Transferring UEs in Connected Mode

The eNodeB instructs a number of UEs to perform inter-RAT measurements based on the information
about the target cells, frequencies and RAT capabilities of UEs, PRB usage in the target cells, and the
type of services that trigger load sharing, when either of the following option combinations is selected:
 The UtranMlbSwitch(UtranMlbSwitch) option of the CellAlgoSwitch.MlbAlgoSwitch parameter
and the UtranPsHoSwitch(UtranPsHoSwitch) option of the EnodebAlgoSwitch.HoModeSwitch
parameter

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 5-1

 The GeranMlbSwitch(GeranMlbSwitch) option of the CellAlgoSwitch.MlbAlgoSwitch parameter

and the GeranPsHoSwitch(GeranPsHoSwitch) option 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. 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.
Handover is the preferred method for the eNodeB to perform load balancing, because the use of
redirection interrupts services. The eNodeB performs load balancing 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 balancing.

NOTE
An SPID is sent by the EPC 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. Subscriber profiles are determined by the
operators' network plans. 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.

In RAN sharing scenarios, load sharing execution is similar to inter-frequency load balancing execution.
For details, see section 4.4 "Load Balancing Execution."

5.3.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, using the dedicated priority information contained in the RRCConnectionRelease message 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.
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.

5.4 Performance Monitoring

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 5-2

 Total PRB usage

Operators can query the SON logs to check the statistics on load balancing within each period.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 5-3

6 Related Features
Two features are related to MLB: admission control (LBFD-002023 Admission Control) and congestion
control (LBFD-002024 Congestion Control).
For details about admission control and congestion control, see Admission and Congestion Control
Feature Parameter Description.

6.1 Required Features

None

6.2 Mutually Exclusive Features

None

6.3 Affected Features

MLB increases the access success rate and reduces the probability of triggering congestion control
because MLB transfers a partial load of an E-UTRAN cell to an intra- or inter-RAT neighboring cell before
the E-UTRAN cell becomes congested.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 6-1

7 Impact on the Network

This chapter describes the impact of MLB on system capacity and network performance.

7.1 Impact on System Capacity

MLB affects GBR service satisfaction rates, the number of users, and throughput in cells. The impact on
GBR and non-GBR services is described as follows:
 If the PRB usage of GBR services in a cell is high, the satisfaction rates of GBR services decrease. In
this situation, admission control may reject new GBR service requests, or congestion control may
release GBR services. However, MLB can transfer GBR services to other cells, and therefore, reduce
the probability that the eNodeB takes admission or congestion control actions.
 If the PRB usage of non-GBR services in a cell is high, the non-GBR services experience rate is
reduced and the non-GBR service capacity is restricted. MLB can transfer certain non-GBR services
to other cells, and therefore, increase resource usage and system capacity.

7.2 Impact on Network Performance

Modifications in mobility-related parameters may cause decreases in the handover performance or
increases in the proportion of ping-pong handovers. These decreases are especially noticeable in
high-speed mobility scenarios in which the sensitivity to mobility-related parameters is high. Therefore,
MLB is not recommended for high-speed mobility scenarios. Intra-frequency load balancing is not as
effective as inter-frequency load balancing. Intra-frequency load balancing also negatively impacts the
intra-frequency handover success rate and increases the call drop rate. Therefore, intra-frequency load
balancing is not recommended in multi-carrier scenarios.
The Inter-RAT Load Sharing to UTRAN and Inter-RAT Load Sharing to GERAN features are only
applicable to the load sharing from an E-UTRAN cell with high load to a GERAN or UTRAN cell with low
load. In the scenarios where a GERAN or UTRAN cell is heavily loaded, inter-RAT load sharing
negatively impacts the network performance of GERAN or UTRAN.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 7-1

8 Engineering Guidelines
8.1 When to Use MLB
Use MLB in the following situations:
 Use intra-frequency load balancing if intra-frequency cells are continuously deployed on the network.
 Use inter-frequency load balancing if inter-frequency cells provide the same coverage, inter-frequency
cells have a large proportion of overlapping coverage, or 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 continuous coverage.

8.2 Information to Be Collected

Collect the following information:
 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 flag is set to True for the neighboring cell
 Status of the X2 interfaces with neighboring eNodeBs
 UE capabilities
The proportion of UEs that support inter-frequency or inter-RAT measurements

8.3 Network Planning

8.3.1 RF Planning
MLB is implemented by handover and reselection. Therefore, the current network coverage must meet
the following UE mobility requirements:
 There is no hole in the coverage.
 There is as little cross-cell coverage as possible.
 There is as little preamble pollution as possible. Preamble pollution occurs if the preambles used by
different cells under one eNodeB conflict.
 There are as few uplink and downlink imbalances as possible.

8.3.2 Network Topology

N/A

8.3.3 Hardware Planning

N/A

8.4 Deploying MLB

8.4.1 Deployment Requirements
There are no requirements for the operating system and transmission networking. Before deploying MLB,
operators must purchase and activate the following licenses.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-1

Feature License Control Item Name

LOFD-001032 Intra-LTE Load Balancing
LOFD-001044 Inter-RAT Load Sharing to UTRAN
LOFD-001045 Inter-RAT Load Sharing to GERAN

8.4.2 Data Preparation

This section describes generic data and scenario-specific data to be collected. Generic data is
necessary for all scenarios and must always be collected. Scenario-specific data is collected only when
necessary for a specific scenario.
There are three types of data sources:
 Network plan (negotiation required): Parameters are planned by operators and negotiated with the
EPC or peer transmission equipment.
 Network plan (negotiation not required): Parameters are planned and set by operators.
 User-defined: Parameters are set as required by users.

Generic Data
The following table describes the parameters that must be set in CellMLB managed objects (MOs) to
configure MLB algorithms.

Parameter Parameter ID Source Setting Description

Name
Load Offset CellMLB.Load Network plan This parameter specifies an offset applied to the
Offset (negotiation not threshold value for triggering MLB. MLB is triggered
required) 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.
Load CellMLB.Load Network plan This parameter specifies the minimum load
Difference DiffThd (negotiation not difference between two cells that triggers MLB.
Threshold required) 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.

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

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-2

the uplink or downlink PRB usage and offset for cell intelligent shutdown. The following table describes
the parameters contained in the CellShutDown MO.

Parameter Parameter ID Source Setting Description

Name
Local cell ID CellShutdown. Network plan This parameter specifies the local ID of a cell. It
LocalCellId (negotiation not uniquely identifies the cell within an eNodeB.
required) The actual value range is 0 to 17.
Cell intelligent CellShutdown. Network plan This parameter specifies whether to enable cell
shutdown CellShutdown (negotiation not intelligent shutdown. Cell intelligent shutdown can be
switch Switch required) performed only when this parameter is set to ON(On)
and specific conditions are met.
The recommended value is OFF(Off).
StartTime CellShutdown. Network plan This parameter specifies the time to start cell
StartTime (negotiation not intelligent shutdown.
required) The recommended value is 00:00:00.
Stop time CellShutdown. Network plan This parameter specifies the time to stop cell
StopTime (negotiation not intelligent shutdown. If the stop time for cell
required) 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 CellShutdown. Network plan This parameter specifies the downlink PRB usage
PRB DlPrbThd (negotiation not threshold for starting cell intelligent shutdown. When
threshold required) the average downlink PRB usage of the cell and its
inter-frequency neighboring cells is lower than this
threshold, intelligent shutdown is started in the
current cell.
The recommended value is 20.
Downlink CellShutdown. Network plan Cell intelligent shutdown is stopped when the
PRB offset DlPrbOffset (negotiation not average downlink PRB usage of the cell's
required) inter-frequency neighboring cells reaches the sum of
CellShutdown.DlPrbThd and the value of this
parameter.
The recommended value is 20.
Uplink PRB CellShutdown. Network plan This parameter specifies the uplink PRB usage
threshold UlPrbThd (negotiation not threshold for starting cell intelligent shutdown. When
required) the average uplink PRB usage of the cell and its
inter-frequency neighboring cells is lower than this
threshold, intelligent shutdown is started in the
current cell.
The recommended value is 20.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-3

Parameter Parameter ID Source Setting Description

Name
Uplink PRB CellShutdown. Network plan Cell intelligent shutdown is stopped when the
offset UlPrbOffset (negotiation not average uplink PRB usage of the cell's
required) 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: Intra-Frequency Load Balancing
The following table describes the parameters that must be set in CellAlgoSwitch MOs to enable the
intra-frequency load balancing algorithm.

Parameter Parameter ID Source Setting Description

Name
Local cell ID CellAlgoSwitch. Network plan This parameter specifies the local ID of a cell. It
LocalCellId (negotiation not uniquely identifies the cell within an eNodeB.
required) The actual value range is 0 to 17.
Load CellAlgoSwitch. Network plan  If IntraFreqMlbSwitch(IntraFreqMlbSwitch)
balancing MlbAlgoSwitch (negotiation not under this parameter is on, intra-frequency load
algorithm required) balancing is enabled and
switch IntraFreqIdleMlbSwitch(IntraFreqIdleMlbSwit
ch) is valid.
 If IntraFreqMlbSwitch(IntraFreqMlbSwitch)
under this parameter is off, intra-frequency load
balancing is disabled and
IntraFreqIdleMlbSwitch(IntraFreqIdleMlbSwit
ch) is invalid.

The following table describes the parameters that must be set in CellMLB MOs to configure the
intra-frequency load balancing algorithm.

Parameter Parameter ID Source Setting Description

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-4

Parameter Parameter ID Source Setting Description

Name
Intra-Frequency CellMLB.IntraF Network plan This parameter specifies the threshold for
Mobility Load reqMlbThd (negotiation not intra-frequency load balancing. Intra-frequency
Balancing required) load balancing is started when the load exceeds
Threshold the sum of the threshold and load offset values. It
is stopped when the load drops below this
threshold.
The recommended value is 60.
It is recommended that this parameter be set to
the same value throughout the network.

Scenario 2: Inter-Frequency Load Balancing

The following table describes the parameters that must be set in CellAlgoSwitch MOs to enable the
inter-frequency load balancing algorithm.

Parameter Parameter ID Source Setting Description

Name
Local cell ID CellAlgoSwitc Network plan This parameter specifies the local ID of a cell. It
h.LocalCellId (negotiation not uniquely identifies the cell within an eNodeB.
required) The actual value range is 0 to 17.
Load CellAlgoSwitc Network plan InterFreqMlbSwitch(InterFreqMlbSwitch) under
balancing h.MlbAlgoSwi (negotiation not this parameter specifies whether to enable the
algorithm tch required) inter-frequency load balancing algorithm.
switch  If InterFreqMlbSwitch(InterFreqMlbSwitch) is
on, the algorithm is enabled.
 If InterFreqMlbSwitch(InterFreqMlbSwitch) is
off, the algorithm is disabled.

The following table describes the parameters that must be set in CellMLB MOs to configure the
inter-frequency load balancing algorithm.

Parameter Parameter ID Source Setting Description

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

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-5

Parameter Parameter ID Source Setting Description

Name
Inter-Frequency CellMLB.Inte Network plan This parameter specifies the threshold for
Mobility Load rFreqMlbThd (negotiation not inter-frequency load balancing. Inter-frequency load
Balancing required) balancing is started when the load exceeds the sum
Threshold of this threshold and the load offset. It is stopped
when the load drops below this threshold.
The recommended value is 60.
It is recommended that this parameter be set to the
same value throughout the network.

The following table describes the parameters that must be set in SpidCfg MOs to configure SPIDs.

Parameter Parameter ID Source Setting Description

Name
Spid SpidCfg.Spi Network plan This parameter specifies an SPID.
d (negotiation not The actual value range is 1 to 256.
required)
RAT frequency SpidCfg.Rat Network plan This parameter specifies whether to configure
priority FreqPriorityI (negotiation not priorities for RATs and frequencies.
indication nd required)
RAT frequency SpidCfg.Rat Network plan This parameter uniquely identifies a priority
priority group ID FreqPriority (negotiation not configuration group for RATs and frequencies.
GroupId required) The actual value range is 0 to 255.
InterFreq Mlb SpidCfg.Inte Network plan This parameter specifies whether to allow
Switch rFreqMlbSwi (negotiation not inter-frequency load balancing for UEs.
tch required)  TRUE(TRUE) = Inter-frequency load balancing is

allowed for UEs.

 FALSE(FALSE) = Inter-frequency load balancing
is not allowed for UEs.

Scenario 3: Inter-RAT Load Sharing

The following table describes the parameters that must be set in CellAlgoSwitch MOs to enable the
inter-RAT load sharing algorithm.

Parameter Parameter ID Source Setting Description

Name
Local cell CellAlgoSwitch.L Network plan This parameter specifies the local ID of a cell. It
ID ocalCellId (negotiation not uniquely identifies the cell within an eNodeB.
required) The actual value range is 0 to 17.
Load CellAlgoSwitch. Network plan UtranMlbSwitch(UtranMlbSwitch) under this
balancing MlbAlgoSwitch (negotiation not parameter specifies whether to enable load sharing
algorithm required) with UTRAN for UEs in connected mode.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-6

Parameter Parameter ID Source Setting Description

Name
switch  If UtranMlbSwitch(UtranMlbSwitch) is on, the
algorithm is enabled.
 If UtranMlbSwitch(UtranMlbSwitch) is off, the
algorithm is disabled.
UtranIdleMlbSwitch(UtranIdleMLBSwitch) under
this parameter specifies whether to enable load
sharing with UTRAN for UEs in idle mode.
 If UtranIdleMlbSwitch(UtranIdleMLBSwitch) is
on, the algorithm is enabled.
 If UtranIdleMlbSwitch(UtranIdleMLBSwitch) is
off, the algorithm is disabled.
GeranMlbSwitch(GeranMlbSwitch) under this
parameter specifies whether to enable load sharing
with GERAN.
 If GeranMlbSwitch(GeranMlbSwitch) is on, the
algorithm is enabled.
 If GeranMlbSwitch(GeranMlbSwitch) is off, the
algorithm is disabled.


The following table describes the parameters that must be set in CellMLB MOs to configure the
inter-RAT load sharing algorithm.

Parameter Parameter ID Source Setting Description

Name
Local cell ID CellMLB.Local Network plan This parameter specifies the local ID of a cell. It
CellId (negotiation not uniquely identifies the cell within an eNodeB.
required) The actual value range is 0 to 17.
Inter-RAT CellMLB.Inter Network plan This parameter specifies the threshold for inter-RAT
Mobility Load RatMlbThd (negotiation not load sharing. Inter-RAT load sharing is triggered if
Balancing required) the cell load is continuously greater than or equal to
Threshold 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. 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.
The recommended value is 75.
Initial valid CellMLB.InitVa Network plan This parameter specifies the initial duration for load
period lidPeriod (negotiation not sharing with UTRAN for UEs in idle mode. The
required) actual duration increases with the cell load.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-7

Parameter Parameter ID Source Setting Description

Name
Inter-RAT CellMLB.Inter Network plan This parameter specifies the threshold for the
Mobility Load RatMlbUeNum (negotiation not number of uplink synchronized UEs used to trigger
Balancing Thd required) inter-RAT load sharing. Inter-RAT load sharing is
Threshold of triggered if the cell load is continuously greater than
UE number 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.
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.
The actual number of uplink synchronized UEs is
equal to this threshold multiplied by 1000.

The following table describes the parameters that must be set in SpidCfg MOs to configure SPIDs.

Parameter Parameter ID Source Setting Description

Name
Spid SpidCfg.Spid Network plan This parameter specifies an SPID.
(negotiation not The actual value range is 1 to 256.
required)
RAT SpidCfg.RatFr Network plan This parameter specifies whether to configure
frequency eqPriorityInd (negotiation not priorities for RATs and frequencies.
priority required)
indication
RAT SpidCfg.RatFr Network plan This parameter uniquely identifies a priority
frequency eqPriorityGrou (negotiation not configuration group for RATs and frequencies.
priority group pId required) The actual value range is 0 to 255.
ID
InterRat Mlb SpidCfg.InterR Network plan This parameter specifies whether to allow inter-RAT
Switch atMlbSwitch (negotiation not load sharing for UEs.
required)  TRUE(TRUE) = Inter-RAT load sharing is allowed

for UEs.
 FALSE(FALSE) = Inter-RAT load sharing is not
allowed for UEs.

8.4.3 Precautions
Pay attention to the following when deploying MLB in a live network:
 The entire network must have the same setting of the switch for intra-frequency load balancing for UEs
in idle mode.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-8

If cells with different settings for this switch are configured as neighboring cells, severe ping-pong
reselection will occur.
 When you turn on the switch for inter-frequency load balancing by running the MOD
CELLALGOSWITCH command, turn off the switch for frequency-priority-based inter-frequency
handovers. If both switches are turned on, severe ping-pong handovers may occur between cells. For
example, after a UE is transferred from cell A to cell B by means of a frequency-priority-based
inter-frequency handover, the UE may soon be transferred back to cell A due to inter-frequency load
balancing.
 If the switches for intra-frequency load balancing, inter-frequency load balancing, and inter-RAT load
sharing are all turned on for a cell and the cell load meets the conditions for starting all three types of
MLB, the target MLB cell is uncertain because no priorities have been specified for the different types
of MLB.
 Among the three types of MLB, inter-frequency load balancing is recommended. Intra-frequency load
balancing brings fewer benefits than inter-frequency load balancing does. Intra-frequency load
balancing also negatively impacts the intra-frequency handover success rate and increases the call
drop rate. Therefore, intra-frequency load balancing is not recommended in multi-carrier scenarios.
 The Inter-RAT Load Sharing to UTRAN and Inter-RAT Load Sharing to GERAN features are only
applicable to the load sharing from an E-UTRAN cell with high load to a GERAN or UTRAN cell with
low load.
 If the IntraFreqMlbSwitch check box under the CellAlgoSwitch.MlbAlgoSwitch parameter is
selected, the IntraFreqIdleMlbSwitch check box must be cleared. If the IntraFreqIdleMlbSwitch
check box under the CellAlgoSwitch.MlbAlgoSwitch parameter is selected, the
IntraFreqMlbSwitch check box must be cleared.

8.4.4 Feature Activation

Configuring a Single eNodeB Using the GUI
Configure a single eNodeB using the Configuration Management Express (CME) graphical user
interface (GUI) based on the collected data described in section 8.4.2 "Data Preparation." For details,
see the procedure for configuring a single eNodeB using the CME GUI described in eNodeB Initial
Configuration Guide.

Configuring eNodeBs in Batches

To configure eNodeBs in batches, perform the following steps:
Step 1 On the GUI, set the parameters listed in the table for a specific scenario in this section, and save
the parameter settings as a user-defined template.
The parameters are the same as those described in section 8.4.2 "Data Preparation."
Step 2 Fill in the summary data file with the name of the user-defined template.
The parameter settings in the user-defined template will be applied to the eNodeBs after you
import the summary data file into the CME.
----End

For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
Scenario 1: Intra-Frequency Load Balancing
A user-defined template is recommended. The following table lists the distribution of parameters in the
template.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-9

MO Parameter Group Name Parameter

CellAlgoSwitch CellAlgoSwitch Local cell ID, Load balancing algorithm switch
CellMLB CellMLB Local cell ID, Intra-Frequency Mobility Load Balancing
Threshold(%), Load Information Exchange Period(s),
Load Offset(%), Load Difference Threshold(%),
InitValidPeriod(s), InterRatMlbUeNumThd

Scenario 2: Inter-Frequency Load Balancing

A user-defined template is recommended. The following table lists the distribution of parameters in the
template.

MO Parameter Group Parameter

CellAlgoSwitch CellAlgoSwitch Local cell ID, Load balancing algorithm switch
CellMLB CellMLB Local cell ID, Inter-Frequency Mobility Load Balancing
Threshold(%), Load Information Exchange Period(s), Load
Offset(%), Load Difference Threshold(%)
CellShutdown CellShutdown Local cell ID, Cell intelligent shutdown switch, Start time,
Stop time, Downlink PRB threshold(%), Downlink PRB
offset(%), Uplink PRB threshold(%), Uplink PRB offset(%)
SpidCfg SpidCfg Spid, RAT frequency priority indication, RAT frequency
priority group ID, InterFreq Mlb Switch

Scenario 3: Inter-RAT Load Sharing

A user-defined template is recommended. The following table lists the distribution of parameters in the
template.

MO Parameter Group Parameter

CellAlgoSwitch CellAlgoSwitch Local cell ID, Load balancing algorithm switch
CellMLB CellMLB Local cell ID, Inter-RAT Mobility Load Balancing
Threshold(%), Load Information Exchange Period(s),
Load Offset(%), Load Difference Threshold(%)
SpidCfg SpidCfg Spid, RAT frequency priority indication, RAT frequency
priority group ID, InterRat Mlb Switch
ENodeBAlgoSwitch ENodeBAlgoSwitch Handover Mode switch

Configuring a Single eNodeB Using MML Commands

Scenario 1: Intra-Frequency Load Balancing
You can activate intra-frequency load balancing on a single eNodeB using MML commands as follows:

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-10

Step 1 Run the MOD CELLALGOSWITCH command to enable the intra-frequency load balancing
algorithm.
Step 2 Run the MOD CELLMLB command to set thresholds for intra-frequency load balancing.
----End

Scenario 2: Inter-Frequency Load Balancing

You can activate inter-frequency load balancing on a single eNodeB using MML commands as follows:
Step 1 Run the MOD CELLALGOSWITCH command to enable the inter-frequency load balancing
algorithm and disable frequency-priority-based inter-frequency handover.
Step 2 Run the MOD CELLMLB command to set thresholds for inter-frequency load balancing.
Step 3 Run the ADD SPIDCFG command to enable SPID-based inter-frequency load balancing. If the
SPID configuration already exists, run the MOD SPIDCFG command to modify the configuration
as required.
Step 4 Run the MOD CELLSHUTDOWN command to configure parameters for cell intelligent
shutdown.
----End

Scenario 3: Inter-RAT Load Sharing

You can activate inter-RAT load sharing on a single eNodeB using MML commands as follows:
Step 1 Run the MOD CELLALGOSWITCH command to enable the algorithms of load sharing with
UTRAN (for UEs in connected mode and idle mode) and GERAN.
Step 2 Run the MOD CELLMLB command to set thresholds for inter-RAT load sharing, the threshold
for the number of uplink synchronized UEs, and the initial duration for load sharing with UTRAN
for UEs in idle mode.
Step 3 Run the ADD SPIDCFG command to enable SPID-based inter-RAT load sharing and set
parameters. If the SPID configuration already exists, run the MOD SPIDCFG command to modify
the configuration.
Step 4 Run the MOD ENODEBALGOSWITCH command with the
UtranPsHoSwitch(UtranPsHoSwitch) or GeranPsHoSwitch(GeranPsHoSwitch) check box
under the Handover Mode switch parameter selected.
----End

8.4.5 Activation Observation

Intra-Frequency Load Balancing
Scenario 1: Intra-Frequency Load Balancing for UEs in Connected Mode
To verify whether intra-frequency load balancing for UEs in connected mode works correctly, perform the
following steps:
Step 1 On the M2000 client, choose Monitor > Signaling Trace > Signaling Trace Management.
The Signaling Trace Management window is displayed, as shown in Figure 8-1.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-11

Figure 8-1 Signaling Trace Management window

Step 2 In the left navigation tree, double-click Usage of RB Monitoring under Cell Performance
Monitoring.
The Create Trace Task dialog box is displayed, as shown in Figure 8-2.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-12

Figure 8-2 Create Trace Task window

Step 3 In the Create Trace Task window, set the task name, select the eNodeB site, and click Next.
The Usage of RB Monitoring dialog box is displayed, as shown in Figure 8-3.
Figure 8-3 Usage of RB Monitoring dialog box

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-13

Step 4 In the Usage of RB Monitoring dialog box, 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
8-4.
Figure 8-4 RB usage tracing result

Step 5 In the left navigation tree in the Signaling Trace Management window (shown in Figure 8-1),
double-click Uu Interface Trace under Application Layer. In the displayed Create Trace Task
window (shown in Figure 8-2), set the task name, select the eNodeB site, and click Next.
The Uu Interface Trace dialog box is displayed, as shown in Figure 8-5.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-14

Figure 8-5 Uu Interface Trace dialog box

Step 6 Click Finish.

The Uu interface tracing task starts for the cell, and the tracing result is displayed as shown in
Figure 8-6.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-15

Figure 8-6 Uu interface tracing result

Step 7 In the Uu interface tracing result, check messages to observe that UE1 and UE2 access the cell
at the cell center and cell edge, respectively. Ensure that UE2 is a CEU in the cell.
For details about how to identify a CEU, see the descriptions related to CEU identification in ICIC
Feature Parameter Description.
Step 8 (This step simulates downlink overload in a 10 MHz cell as an example.) Inject downlink UDP
packets for UE1 continuously until the RB usage observed on the M2000 client exceeds the sum
of CellMLB.IntraFreqMlbThd and CellMLB.LoadOffset. Inject downlink UDP packets for UE2
at a rate of 2 Mbit/s.
Step 9 Follow Step 5 and Step 6 to start X2 interface tracing, and check the messages traced over the
X2 interface.
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,
intra-frequency load balancing has been activated. Figure 8-7 shows an example of the
RESOURCE STATUS REQUEST message.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-16

Figure 8-7 RESOURCE STATUS REQUEST message

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 10 Check for the Mobility Change Request message in the X2 interface tracing result. This message
contains the source cell ID and target cell ID, as shown in Figure 8-8.
If the Mobility Change Request message appears in the X2 interface tracing result, one round of
CIO adjustment has been performed on the source and target cells.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-17

Figure 8-8 Mobility Change Request message

Step 11 Observe the progress of CIO adjustments.

If the UE is transferred to the target cell through a load-based handover after several rounds of
CIO adjustments, intra-frequency load balancing for UEs in connected mode is working correctly.
----End

Scenario 2: Intra-Frequency Load Balancing for UEs in Idle Mode

To verify whether intra-frequency load balancing for UEs in idle mode works correctly, perform the
following steps:
Step 1 Run the MOD RRCCONNSTATETIMER command to set the UE inactivity timer to 20s.
Step 2 On the M2000 client, start Uu interface tracing and RB usage monitoring.
For details about how to start the two tasks, see Scenario 1 for "Intra-Frequency Load Balancing"
earlier in this section.
Step 3 Access a cell with UE1 in the cell center, access the cell with UE2 at the cell edge, and then wait
20s.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-18

Step 4 (This step simulates downlink overload as an example.) Inject downlink UDP packets for UE1
until the M2000 client shows that the RB usage exceeds the sum of CellMLB.IntraFreqMlbThd
and CellMLB.LoadOffset. Do not run any services on UE2.
Step 5 Proceed as in Step 9 through Step 11 of Scenario 1 to check whether intra-frequency load
balancing for UEs in idle mode has been activated.

NOTE
Qoffset is used to control the reselection procedures for UEs in idle mode. After the CIO is successfully adjusted, the
serving cell and target neighboring cell broadcast a new Qoffset value. The Qoffset adjustment has a negative correlation
to the CIO adjustment.

----End

Inter-Frequency Load Balancing

To verify whether inter-frequency load balancing works correctly, perform the following steps:
Step 1 On the M2000 client, start Uu interface tracing, X2 interface tracing, and RB usage monitoring.
For details about how to start the three tasks, see Scenario 1 for "Intra-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.
Step 3 (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
CellMLB.InterFreqMlbThd and CellMLB.LoadOffset. Inject downlink UDP packets for UE2 at a
rate of 2 Mbit/s.
Step 4 Check for an RRC_CONN_RECFG message in the Uu interface tracing result and an
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:

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-19

Step 1 On the M2000 client, start Uu interface tracing, X2 interface tracing, and RB usage monitoring.
For details about how to start the three tasks, see Scenario 1 for "Intra-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.
The number of uplink synchronized UEs in the cell is greater than or equal to the
CellMLB.InterRATMlbUeNumThd value.
Step 3 (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
CellMLB.InterRatMlbThd and CellMLB.LoadOffset. Inject downlink UDP packets for UE2 at a
rate of 2 Mbit/s.
Step 4 Check for an S1AP_HANDOVER_REQUIRED message in the S1 interface tracing result.
If the S1AP_HANDOVER_REQUIRED message containing the cause value 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 1 On the M2000 client, choose SON > SON log.
Step 2 On the Query SON Log tab page, choose MLB Log from the Log Category drop down list in
the upper left corner, and click Inter-RAT Handover Statistics under Event Name. Then, click
Query to query SON logs.
From the logs, check whether the feature is working correctly. You can view only the SON logs
that were generated at least one day ago.
----End

Inter-RAT Load Sharing 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 Scenario 1 for "Intra-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.
The number of uplink synchronized UEs in the cell is greater than or equal to the
CellMLB.InterRATMlbUeNumThd value.
Step 3 (This step simulates downlink overload in a 10 MHz cell as an example.) Inject downlink UDP
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 CellMLB.InterRatMlbThd and
CellMLB.LoadOffset. Stop injecting downlink UDP packets for UE2. Wait until its inactivity timer
expires, UE2 enters idle mode. Check whether the RB usage exceeds the sum of
CellMLB.InterRatMlbThd and CellMLB.LoadOffset.
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 successfully redirects to an UTRAN cell, inter-RAT load sharing is working correctly. For
details about the reselection priority, see section 5.3.2 "Transferring UEs in Idle Mode."

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-20

----End

8.4.6 Deactivation
Scenario 1: Intra-Frequency Load Balancing (for UEs in Idle or Connected
Mode)
Run the MOD CELLALGOSWITCH command to disable the intra-frequency load balancing algorithm.

Scenario 2: Inter-Frequency Load Balancing

Run the MOD CELLALGOSWITCH command to disable the inter-frequency load balancing algorithm.

Scenario 3: Inter-RAT Load Sharing

Run the MOD CELLALGOSWITCH command to disable the algorithms of load sharing with UTRAN (for
UEs in connected mode and idle mode) and GERANCDMA2000.

8.5 Performance Optimization

8.5.1 Monitoring
MLB does not have any related counter for performance monitoring.
To monitor MLB performance, calculate the average uplink and downlink throughput of a cell using the
following formulas:
 Average uplink throughput = Total amount of uplink data received by the PDCP layer
(L.Thrp.bits.UL)/Total duration of uplink data reception at the PDCP layer (L.Thrp.Time.UL)
 Average downlink throughput = Total amount of downlink data received by the PDCP layer
(L.Thrp.bits.DL)/Total duration of downlink data reception at the PDCP layer (L.Thrp.Time.DL)

8.5.2 Parameter Optimization

The following parameters may need to be adjusted for better performance:
 Thresholds for starting intra-frequency load balancing, inter-frequency load balancing, and inter-RAT
load sharing
The thresholds directly determine the probabilities and effectiveness of the three types of MLB.
 Load offset (specified by the CellMLB.LoadOffset parameter)
If the load offset is set to an appropriate value, the probability of ping-pong load transfer will drop.
 Handover-related parameters
They determine the handover performance for load transfer.

8.6 Troubleshooting
This section provides steps to troubleshoot a possible fault that might occur after MLB is enabled.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-21

8.6.1 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 the procedure of starting Uu
interface tracing task for Scenario 1 for "Intra-Frequency Load Balancing" in section 8.4.5
"Activation Observation."
Step 2 Check whether the serving eNodeB has sent a RESOURCE STATUS REQUEST message,
which contains information about the neighboring cells involved in load information exchange
with the serving cell. If the eNodeB has not sent this message, then this fault did occur. Go to
Step 3.
Step 3 Run the LST EUTRANINTERFREQNCELL command to check the inter-frequency neighboring
cells of the serving cell.
1. If at least one neighboring cell is displayed, go to substep 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 not 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 substep 3. Otherwise, handle
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.
 If all these neighboring cells are blacklisted, this fault occurred because the eNodeB does not perform
MLB on those blacklisted cells. No further action is required.
 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.
 If this alarm has been reported, handle the alarm by following handling suggestions in eNodeB Alarm
Reference.
 If this alarm has not been reported, contact Huawei technical support.
----End

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-22

8.6.2 Failing to InitiateInter-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 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
Perform the following steps for troubleshooting:
Step 1 On the M2000 client, start RB usage monitoring by referring to the procedure of starting Uu
interface tracing task for Scenario 1 for "Intra-Frequency Load Balancing" in section 8.4.5
"Activation Observation."
Step 2 Check whether the RB usage of the serving cell exceeds the sum of CellMLB.InterRatMlbThd
and CellMLB.LoadOffset.
 If yes, go to Step 3.
 If no, increase the traffic volume of UEs.
Step 3 Check whether the number of uplink synchronized UEs exceeds
CellMLB.InterRATMlbUeNumThd.
 If yes, go to Step 4.
 If no, 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.
 If yes, contact Huawei technical support.
 If no, configure the inter-RAT neighbor relationship on the serving cell.
----End

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

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-23

Step 3 Check whether the number of uplink synchronized UEs exceeds

CellMLB.InterRATMlbUeNumThd.
 If yes, go to Step 4.
 If no, this is not a problem. No further action is required.
Step 4 Check whether or not the priorities of E-UTRAN frequencies and those of neighboring UTRAN
frequencies belong to non-overlapping ranges.
 Otherwise, go to Step 5.
 If no, 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.
 If yes, contact Huawei technical support.
 If no, configure the inter-RAT neighbor relationship on the serving cell.
----End

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 8-24

9 Parameters
Table 9-1 Parameter description
MO Parameter MML Command Feature ID Feature Description
ID Name

CellShutdo CellShutdow MOD LOFD-001 Intellige Meaning:Indicates whether to enable or

wn nSwitch CELLSHUTDO 042 / nt disable cell intelligent shutdown. Cell
WN TDLOFD-0 Power- intelligent shutdown can be performed
01042 Off of only when this parameter is set to ON
LST Carriers and specific conditions are met. For cell
CELLSHUTDO in the intelligent shutdown, each basic cell
WN Same must have its cell intelligent shutdown
Coverag enabled and the UL or DL PRB usage
e threshold set to 0.
GUI Value Range:OFF(Off), ON(On)
Unit:None
Actual Value Range:OFF, ON
Default Value:OFF(Off)

CellShutdo DlPrbOffset MOD LOFD-001 Intellige Meaning:Indicates the DL PRB usage

wn CELLSHUTDO 042 / nt offset for cell intelligent shutdown. For
WN TDLOFD-0 Power- cell intelligent shutdown, each basic cell
01042 Off of must have its cell intelligent shutdown
LST Carriers enabled and the UL or DL PRB usage
CELLSHUTDO in the threshold set to 0. The local cell enters
WN Same cell intelligent shutdown mode if its UL
Coverag and DL loads are lower than the UL and
e DL PRB usage thresholds, respectively,
and the total load of the local and basic
cells is lower than the sum of the UL
PRB usage threshold and offset as well
as the sum of the DL PRB usage
threshold and offset. The local cell exits
cell intelligent shutdown mode if the load
of any basic cell is higher than or equal
to the sum of the UL PRB usage
threshold and offset, or the sum of the
DL PRB usage threshold and offset.
GUI Value Range:0~100
Unit:%
Actual Value Range:0~100
Default Value:20

CellShutdo DlPrbThd MOD LOFD-001 Intellige Meaning:Indicates the DL PRB usage

wn CELLSHUTDO 042 / nt threshold for cell intelligent shutdown.
WN TDLOFD-0 Power- For cell intelligent shutdown, each basic
Off of cell must have its cell intelligent

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 9-1

MO Parameter MML Command Feature ID Feature Description

ID Name
LST 01042 Carriers shutdown enabled and the UL or DL
CELLSHUTDO in the PRB usage threshold set to 0. The local
WN Same cell enters cell intelligent shutdown mode
Coverag if its UL and DL loads are lower than the
e UL and DL PRB usage thresholds,
respectively, and the total load of the
local and basic cells is lower than the
sum of the UL PRB usage threshold and
offset as well as the sum of the DL PRB
usage threshold and offset. The local cell
exits cell intelligent shutdown mode if the
load of any basic cell is higher than or
equal to the sum of the UL PRB usage
threshold and offset, or the sum of the
DL PRB usage threshold and offset.
GUI Value Range:0~100
Unit:%
Actual Value Range:0~100
Default Value:20

ENodeBAlg HoModeSwit MOD LOFD-001 PS Meaning:Indicates the switches

oSwitch ch ENODEBALGO 019 / Inter-RA corresponding to the inputs based on
SWITCH TDLOFD-0 T which the eNodeB determines handover
01019 Mobility policies.
LST between
ENODEBALGO LOFD-001 E-UTRA Note that EutranVoipCapSwitch will be
SWITCH 020 / N and removed in the later versions. In this
TDLOFD-0 UTRAN version, the setting of this switch is still
01020 synchronized between the M2000 and
PS the eNodeB, but it is no longer used
LOFD-001 Inter-RA internally. Therefore, avoid using this
021 / T switch.
TDLOFD-0 Mobility
01021 between GUI Value
Range:EutranVoipCapSwitch(EutranVoi
LOFD-001 E-UTRA pCapSwitch),
022 / N and
UtranVoipCapSwitch(UtranVoipCapSwit
TDLOFD-0 GERAN ch),
01022 PS GeranVoipCapSwitch(GeranVoipCapSwi
LOFD-001 Inter-RA tch),
023 / T Cdma1xRttVoipCapSwitch(Cdma1xRttV
TDLOFD-0 Mobility oipCapSwitch),
01023 between UtranPsHoSwitch(UtranPsHoSwitch),
E-UTRA GeranPsHoSwitch(GeranPsHoSwitch),
N and CdmaHrpdNonOtpimisedHoSwitch(Cdm
CDMA2 aHrpdNonOtpimisedHoSwitch),
000 CdmaHrpdOptimisedHoSwitch(CdmaHr
pdOptimisedHoSwitch),
SRVCC GeranNaccSwitch(GeranNaccSwitch),
to GeranCcoSwitch(GeranCcoSwitch),

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 9-2

MO Parameter MML Command Feature ID Feature Description

ID Name
UTRAN UtranSrvccSwitch(UtranSrvccSwitch),
GeranSrvccSwitch(GeranSrvccSwitch),
SRVCC Cdma1xRttSrvccSwitch(Cdma1xRttSrvc
to cSwitch),
GERAN UtranRedirectSwitch(UtranRedirectSwitc
h),
GeranRedirectSwitch(GeranRedirectSwi
tch),
CdmaHrpdRedirectSwitch(CdmaHrpdRe
directSwitch),
Cdma1xRttRedirectSwitch(Cdma1xRttR
edirectSwitch),
BlindHoSwitch(BlindHoSwitch)
Unit:None
Actual Value
Range:EutranVoipCapSwitch,
UtranVoipCapSwitch,
GeranVoipCapSwitch,
Cdma1xRttVoipCapSwitch,
UtranPsHoSwitch, GeranPsHoSwitch,
CdmaHrpdNonOtpimisedHoSwitch,
CdmaHrpdOptimisedHoSwitch,
GeranNaccSwitch, GeranCcoSwitch,
UtranSrvccSwitch, GeranSrvccSwitch,
Cdma1xRttSrvccSwitch,
UtranRedirectSwitch,
GeranRedirectSwitch,
CdmaHrpdRedirectSwitch,
Cdma1xRttRedirectSwitch,
BlindHoSwitch
Default Value:EutranVoipCapSwitch:On,
UtranVoipCapSwitch:Off,
GeranVoipCapSwitch:Off,
Cdma1xRttVoipCapSwitch:Off,
UtranPsHoSwitch:Off,
GeranPsHoSwitch:Off,
CdmaHrpdNonOtpimisedHoSwitch:Off,
CdmaHrpdOptimisedHoSwitch:Off,
GeranNaccSwitch:Off,
GeranCcoSwitch:Off,
UtranSrvccSwitch:Off,
GeranSrvccSwitch:Off,
Cdma1xRttSrvccSwitch:Off,
UtranRedirectSwitch:Off,
GeranRedirectSwitch:Off,
CdmaHrpdRedirectSwitch:Off,
Cdma1xRttRedirectSwitch:Off,
BlindHoSwitch:Off

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 9-3

MO Parameter MML Command Feature ID Feature Description

ID Name

CellMLB InitValidPerio MOD CELLMLB LBFD-001 3GPP Meaning:Indicates the standard duration
d 001 / R8 of the UTRAN load balancing in idle
LST CELLMLB TDLBFD-0 Specific mode. The actual duration has a positive
01001 ations correlation with the number of UEs in the
uplink synchronization state.
LOFD-001 Inter-RA
044 / T Load GUI Value Range:1~30
TDLOFD-0 Sharing
01044 to Unit:s
UTRAN Actual Value Range:1~30
LOFD-001
045 / Inter-RA Default Value:10
TDLOFD-0 T Load
01045 Sharing
to
GERAN

SpidCfg InterFreqMlb ADD SPIDCFG LOFD-001 Intra-LT Meaning:Indicates whether to enable or

Switch 032 / E Load disable inter-frequency load balancing
MOD SPIDCFG TDLOFD-0 Balanci for the SPID. The values TRUE and
LST SPIDCFG 01032 ng FALSE indicate that inter-frequency load
balancing is allowed and prohibited for
LOFD-001 Flexible UEs with the SPID, respectively.
054 / User
TDLOFD-0 Steering GUI Value Range:FALSE(FALSE),
01054 TRUE(TRUE)
Unit:None
Actual Value Range:FALSE, TRUE
Default Value:TRUE(TRUE)

CellMLB InterFreqMlb MOD CELLMLB LBFD-001 3GPP Meaning:Indicates the threshold for
Thd 001 / R8 triggering inter-frequency load
LST CELLMLB TDLBFD-0 Specific balancing. Load balancing between the
01001 ations cell and its inter-frequency neighboring
cell is triggered if the cell load exceeds
LOFD-001 Intra-LT the sum of this threshold and the offset,
032 / E Load and is stopped if the cell load falls below
TDLOFD-0 Balanci this threshold.The sum of this threshold
01032 ng and the load offset must be greater than
the sum of the UL/DL PRB usage
threshold and UL/DL PRB offset for cell
intelligent shutdown.
GUI Value Range:1~100
Unit:%
Actual Value Range:1~100
Default Value:60

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 9-4

MO Parameter MML Command Feature ID Feature Description

ID Name

SpidCfg InterRatMlbS ADD SPIDCFG LOFD-001 Inter-RA Meaning:Indicates whether to enable or

witch 044 / T Load disable inter-RAT load balancing for the
MOD SPIDCFG TDLOFD-0 Sharing SPID. The values TRUE and FALSE
LST SPIDCFG 01044 to indicate that inter-RAT load balancing is
UTRAN allowed and prohibited for UEs with the
LOFD-001 SPID, respectively.
045 / Inter-RA
TDLOFD-0 T Load GUI Value Range:FALSE(FALSE),
01045 Sharing TRUE(TRUE)
to
LOFD-001 GERAN Unit:None
054 /
TDLOFD-0 Flexible Actual Value Range:FALSE, TRUE
01054 User Default Value:TRUE(TRUE)
Steering

CellMLB InterRatMlbT MOD CELLMLB LBFD-001 3GPP Meaning:Indicates the threshold for
hd 001 / R8 triggering inter-RAT load balancing. Load
LST CELLMLB TDLBFD-0 Specific balancing between the cell and its
01001 ations inter-RAT neighboring cell is triggered if
the cell load exceeds the sum of this
LOFD-001 Inter-RA threshold and the offset, and is stopped
044 / T Load if the cell load falls below this
TDLOFD-0 Sharing threshold.The sum of this threshold and
01044 to the load offset must be greater than the
UTRAN sum of the UL/DL PRB usage threshold
LOFD-001
045 / Inter-RA and UL/DL PRB offset for cell intelligent
TDLOFD-0 T Load shutdown.
01045 Sharing GUI Value Range:1~100
to
GERAN Unit:%
Actual Value Range:1~100
Default Value:75

CellMLB InterRatMlb MOD CELLMLB LBFD-001 3GPP Meaning:Indicates a percentage value

UeNumThd 001 / R8 used in the evaluation of inter-RAT load
LST CELLMLB TDLBFD-0 Specific balancing. This parameter value
01001 ations multiplied by 1000 is the threshold for
the number of UL-synchronized users.
LOFD-001 Inter-RA Load balancing between the cell and its
044 / T Load inter-RAT neighboring cell is triggered if
TDLOFD-0 Sharing the number of UL-synchronized users in
01044 to the cell exceeds this threshold, and is
UTRAN stopped if the number of
LOFD-001
045 / Inter-RA UL-synchronized users falls below this
TDLOFD-0 T Load threshold. For example, GUI value 1 is
01045 Sharing mapped to actual value 10(1000*1%),
to GUI value 2 is mapped to actual value
GERAN 20, GUI value 10 is mapped to actual
value 100. Note: there is special

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 9-5

MO Parameter MML Command Feature ID Feature Description

ID Name
mapping of two GUI values, GUI value
100 is mapped to actual value 1 and GUI
value 99 is mapped to actual value 2.
GUI Value Range:1~100
Unit:%
Actual Value Range:1~100
Default Value:15

CellMLB IntraFreqMlb MOD CELLMLB LBFD-001 3GPP Meaning:Indicates the threshold for
Thd 001 / R8 triggering intra-frequency load
LST CELLMLB TDLBFD-0 Specific balancing. Intra-frequency load
01001 ations balancing is started if the cell load
exceeds the sum of the threshold and
LOFD-001 Intra-LT the offset, and is stopped if the cell load
032 / E Load falls below the threshold.The sum of this
TDLOFD-0 Balanci threshold and the load offset must be
01032 ng greater than the sum of the UL/DL PRB
usage threshold and UL/DL PRB offset
for cell intelligent shutdown.
GUI Value Range:1~100
Unit:%
Actual Value Range:1~100
Default Value:60

CellMLB LoadDiffThd MOD CELLMLB LBFD-001 3GPP Meaning:Indicates the threshold of load
001 / R8 difference between two cells for load
LST CELLMLB TDLBFD-0 Specific balancing. If the load difference between
01001 ations cells exceeds this threshold, the eNodeB
determines that load imbalance occurs
LOFD-001 Intra-LT and therefore initiates load balancing
032 / E Load between the cells. If the load difference
TDLOFD-0 Balanci between cells falls below this threshold,
01032 ng the eNodeB determines that load
LOFD-001 Inter-RA imbalance is resolved and therefore
044 / T Load stops load balancing between the
TDLOFD-0 Sharing cells.For Blind MLB, if MlbTriggerMode
01044 to is PrbMode, PRB usage of the UE
UTRAN selected for handover must be lower
LOFD-001 than LoadDiffThd and higher than
045 / Inter-RA MlbUeSelectPrbThd. If LoadDiffThd is
TDLOFD-0 T Load lower than MlbUeSelectPrbThd, no UE
01045 Sharing will be selected.
to
GERAN GUI Value Range:1~50
Unit:%

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 9-6

MO Parameter MML Command Feature ID Feature Description

ID Name
Actual Value Range:1~50
Default Value:15

CellMLB LoadOffset MOD CELLMLB LBFD-001 3GPP Meaning:Indicates the offset used in the
001 / R8 evaluation of whether to trigger load
LST CELLMLB TDLBFD-0 Specific balancing. To prevent load fluctuations
01001 ations from frequently triggering or stopping
load balancing, an offset needs to be set.
LOFD-001 Intra-LT That is, a specific load balancing action
032 / E Load is taken only if the cell load exceeds the
TDLOFD-0 Balanci sum of the corresponding load balancing
01032 ng threshold and this offset.
LOFD-001 Inter-RA GUI Value Range:0~50
044 / T Load
TDLOFD-0 Sharing Unit:%
01044 to
UTRAN Actual Value Range:0~50
LOFD-001
045 / Inter-RA Default Value:8
TDLOFD-0 T Load
01045 Sharing
to
GERAN

CellAlgoSwi LocalCellId LST None None Meaning:Indicates the local ID of the

tch CELLALGOSWI cell. It uniquely identifies a cell within a
TCH BS.
MOD GUI Value Range:0~17
CELLALGOSWI
TCH Unit:None
Actual Value Range:0~17
Default Value:None

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

CellShutdo LocalCellId LST LOFD-001 Intellige Meaning:Indicates the local ID of the

wn CELLSHUTDO 042 / nt cell. It uniquely identifies a cell within a
WN TDLOFD-0 Power- BS.
01042 Off of
MOD Carriers

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 9-7

MO Parameter MML Command Feature ID Feature Description

ID Name
CELLSHUTDO in the GUI Value Range:0~17
WN Same
Coverag Unit:None
e Actual Value Range:0~17
Default Value:None

CellAlgoSwi MlbAlgoSwit MOD LBFD-001 3GPP Meaning:Indicates the switches used to

tch ch CELLALGOSWI 001 / R8 enable or disable load balancing
TCH TDLBFD-0 Specific algorithms. There are seven load
01001 ations balancing switches, which are used to
LST control the intra-frequency,
CELLALGOSWI LOFD-001 Intra-LT intra-frequency idle, inter-frequency,
TCH 032 / E UTRAN, UTRAN idle, GERAN, and
TDLOFD-0 Load CDMA2000 load balancing algorithms,
01032 Balanci respectively. If one switch is set to ON,
ng the corresponding algorithm is enabled
LOFD-001
044 / Inter-RA to balance the loads between
TDLOFD-0 T Load neighboring cells of the specified
01044 Sharing category. If IntraFreqMlbSwitch is set
to to ON, the intra-frequency load
LOFD-001 UTRAN balancing is enabled. If
045 / IntraFreqMlbSwitch is set to OFF, the
TDLOFD-0 Inter-RA intra-frequency load balancing is
01045 T Load disabled. If InterFreqMlbSwitch is set to
Sharing ON, the inter-frequency load balancing
to is enabled. If InterFreqMlbSwitch is set
GERAN to OFF, the inter-frequency load
balancing is disabled. If
UtranMlbSwitch is set to ON, the UTRAN
load balancing is enabled. If
UtranMlbSwitch is set to OFF, the
UTRAN load balancing is disabled. If
GeranMlbSwitch is set to ON, the
GERAN load balancing is enabled. If
GeranMlbSwitch is set to OFF, the
GERAN load balancing is disabled. If
CdmaMlbSwitch is set to ON, the
CDMA2000 load balancing is enabled.
If CdmaMlbSwitch is set to OFF, the
CDMA2000 load balancing is disabled. If
IntraFreqIdleMlbSwitch and
IntraFreqMlbSwitch are both set to ON,
the intra-frequency idle load balancing is
enabled. Otherwise, the intra-frequency
idle load balancing is disabled. If
UtranIdleMlbSwitch is set to ON, the
UTRAN load balancing in idle mode is
enabled. If UtranIdleMlbSwitch is set to
OFF, the UTRAN load balancing in idle
mode is disabled. When
InterFreqBlindMlbSwitch is set to On, the

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 9-8

MO Parameter MML Command Feature ID Feature Description

ID Name
blind inter-frequency MLB is enabled.
When InterFreqBlindMlbSwitch is set to
Off, the blind inter-frequency MLB is
disabled.InterFreqBlindMlbSwitch and
InterFreqMlbSwitch cannot be set to On
simultaneously.
GUI Value
Range:IntraFreqMlbSwitch(IntraFreqMlb
Switch),
InterFreqMlbSwitch(InterFreqMlbSwitch)
, UtranMlbSwitch(UtranMlbSwitch),
GeranMlbSwitch(GeranMlbSwitch),
CdmaMlbSwitch(CdmaMlbSwitch),
IntraFreqIdleMlbSwitch(IntraFreqIdleMlb
Switch),
UtranIdleMlbSwitch(UtranIdleMLBSwitch
),
InterFreqBlindMlbSwitch(InterFreqBlind
MlbSwitch)
Unit:None
Actual Value Range:IntraFreqMlbSwitch,
InterFreqMlbSwitch, UtranMlbSwitch,
GeranMlbSwitch, CdmaMlbSwitch,
IntraFreqIdleMlbSwitch,
UtranIdleMlbSwitch,
InterFreqBlindMlbSwitch
Default Value:IntraFreqMlbSwitch:Off,
InterFreqMlbSwitch:Off,
UtranMlbSwitch:Off,
GeranMlbSwitch:Off,
CdmaMlbSwitch:Off,
IntraFreqIdleMlbSwitch:Off,
UtranIdleMLBSwitch:Off,
InterFreqBlindMlbSwitch:Off

EutranInter NoHoFlag ADD LBFD-002 Coverag Meaning:Indicates whether handovers of

FreqNCell EUTRANINTER 01802 / e Based UEs to the neighboring cell are
FREQNCELL TDLBFD-0 Inter-fre prohibited.
0201802 quency
MOD Handov GUI Value
EUTRANINTER LOFD-002 er Range:PERMIT_HO_ENUM(Permit Ho),
FREQNCELL 001 / FORBID_HO_ENUM(Forbid Ho)
TDLOFD-0 Automat
LST 02001 ic Unit:None
EUTRANINTER Neighbo Actual Value
FREQNCELL ur Range:PERMIT_HO_ENUM,
Relation FORBID_HO_ENUM
(ANR)
Default

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 9-9

MO Parameter MML Command Feature ID Feature Description

ID Name
Value:PERMIT_HO_ENUM(Permit Ho)

SpidCfg RatFreqPrior ADD SPIDCFG LOFD-001 Intra-LT Meaning:Indicates the ID of a

ityGroupId 032 / E Load RAT/frequency priority group.
MOD SPIDCFG TDLOFD-0 Balanci
GUI Value Range:0~255
LST SPIDCFG 01032 ng
LOFD-001 Inter-RA Unit:None
044 / T Load Actual Value Range:0~255
TDLOFD-0 Sharing
01044 to Default Value:0
UTRAN
LOFD-001
045 / Inter-RA
TDLOFD-0 T Load
01045 Sharing
to
LOFD-001 GERAN
054 /
TDLOFD-0 Flexible
01054 User
Steering
LOFD-001
05401 / Camp &
TDLOFD-0 Handov
0105401 er
Based
LOFD-001 on SPID
059 /
TDLOFD-0 UL
01059 Pre-allo
cation
Based
on SPID

SpidCfg RatFreqPrior ADD SPIDCFG LOFD-001 Intra-LT Meaning:Indicates whether to specify a

ityInd 032 / E Load RAT/frequency priority group. If this
MOD SPIDCFG TDLOFD-0 Balanci parameter is set to CFG, UEs
LST SPIDCFG 01032 ng preferentially camp on the specified
RAT/frequency. If this parameter is set to
LOFD-001 Inter-RA NOT_CFG, UEs randomly camp on an
044 / T Load RAT/frequency.
TDLOFD-0 Sharing
01044 to GUI Value
UTRAN Range:NOT_CFG(NOT_CFG),
LOFD-001 CFG(CFG)
045 / Inter-RA
TDLOFD-0 T Load Unit:None
01045 Sharing
to Actual Value Range:NOT_CFG, CFG
LOFD-001 GERAN
054 / Default Value:NOT_CFG(NOT_CFG)
TDLOFD-0 Flexible
01054 User

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 9-10

MO Parameter MML Command Feature ID Feature Description

ID Name
Steering

SpidCfg Spid ADD SPIDCFG LOFD-001 Intra-LT Meaning:Indicates the subscriber profile
032 / E Load ID (SPID).
LST SPIDCFG TDLOFD-0 Balanci
GUI Value Range:1~256
MOD SPIDCFG 01032 ng
Unit:None
RMV SPIDCFG LOFD-001 Inter-RA
044 / T Load Actual Value Range:1~256
TDLOFD-0 Sharing
01044 to Default Value:None
UTRAN
LOFD-001
045 / Inter-RA
TDLOFD-0 T Load
01045 Sharing
to
LOFD-001 GERAN
054 /
TDLOFD-0 Flexible
01054 User
Steering
LOFD-001
05401 / Camp &
TDLOFD-0 Handov
0105401 er
Based
LOFD-001 on SPID
059 /
TDLOFD-0 UL
01059 Pre-allo
cation
Based
on SPID

CellShutdo StartTime MOD LOFD-001 Intellige Meaning:Indicates the start time of cell
wn CELLSHUTDO 042 / nt intelligent shutdown. If the stop time is
WN TDLOFD-0 Power- earlier than or the same as the start time,
01042 Off of the stop time is assumed to be a time of
LST Carriers the next day.
CELLSHUTDO in the
WN Same GUI Value Range:00:00:00~23:59:59
Coverag Unit:None
e
Actual Value Range:00:00:00~23:59:59
Default Value:00:00:00

CellShutdo StopTime MOD LOFD-001 Intellige Meaning:Indicates the stop time of cell
wn CELLSHUTDO 042 / nt intelligent shutdown. If the stop time is
WN TDLOFD-0 Power- earlier than or the same as the start time,
01042 Off of the stop time is assumed to be a time of
LST Carriers the next day.
CELLSHUTDO

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 9-11

MO Parameter MML Command Feature ID Feature Description

ID Name
WN in the GUI Value Range:00:00:00~23:59:59
Same
Coverag Unit:None
e Actual Value Range:00:00:00~23:59:59
Default Value:06:00:00

CellShutdo UlPrbOffset MOD LOFD-001 Intellige Meaning:Indicates the UL PRB usage

CellShutdo UlPrbThd MOD LOFD-001 Intellige Meaning:Indicates the UL PRB usage

wn CELLSHUTDO 042 / nt threshold for cell intelligent shutdown.
WN TDLOFD-0 Power- For cell intelligent shutdown, each basic
01042 Off of cell must have its cell intelligent
LST Carriers shutdown enabled and the UL or DL
CELLSHUTDO in the PRB usage threshold set to 0. The local
WN Same cell enters cell intelligent shutdown mode
Coverag if its UL and DL loads are lower than the
e UL and DL PRB usage thresholds,
respectively, and the total load of the
local and basic cells is lower than the
sum of the UL PRB usage threshold and
offset as well as the sum of the DL PRB
usage threshold and offset. The local cell
exits cell intelligent shutdown mode if the
load of any basic cell is higher than or
equal to the sum of the UL PRB usage
threshold and offset, or the sum of the

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 9-12

MO Parameter MML Command Feature ID Feature Description

ID Name
DL PRB usage threshold and offset.
GUI Value Range:0~100
Unit:%
Actual Value Range:0~100
Default Value:20

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 9-13

10 Counters
Table 10-1 Counter description
Counter ID Counter Name Counter Feature ID Feature Name
Description

1526728526 L.HHO.InterFreq.Load.PrepAttOut Number of LOFD-001032 Intra-LTE Load

Inter-Frequency Balancing
Handover TDLOFD-001032
Preparation Intra-LTE Load
Attempts Balancing
Triggered
Because of High
Load

1526728527 L.HHO.InterFreq.Load.ExecAttOut Number of LOFD-001032 Intra-LTE Load

Inter-Frequency Balancing
Handover TDLOFD-001032
Execution Intra-LTE Load
Attempts Balancing
Triggered
Because of High
Load

1526728528 L.HHO.InterFreq.Load.ExecSuccOut Number of LOFD-001032 Intra-LTE Load

Successful Balancing
Inter-Frequency TDLOFD-001032
Handover Intra-LTE Load
Executions Balancing
Triggered
Because of High
Load

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 10-1

11 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 11-1

12 Reference Documents
This chapter lists the reference documents related to MLB:
[1] 3GPP TS 36.300, "E-UTRAN Overall description"
[2] 3GPP TS 36.413, "S1 Application Protocol (S1AP)"
[3] 3GPP TS 36.423, "X2 application protocol (X2AP)"
[4] 3GPP TS 36.902, "Self-configuring and self-optimizing network use cases and solutions"
[5] 3GPP TS 36.331, "Radio Resource Control (RRC)"
[6] Transport Resource Management Feature Parameter Description
[7] Idle Mode Management Feature Parameter Description
[8] Admission and Congestion Control Feature Parameter Description
[9] Mobility Management in Connected Mode Feature Parameter Description
[10] RAN Sharing Feature Parameter Description
[11] MRO Feature Parameter Description
[12] eNodeB Initial Configuration Guide

Issue 07 (2013-05-20) Huawei Proprietary and Confidential 12-1

Huawei 3D Beamforming (FDD) (eRAN15.1 - Draft A)
No ratings yet
Huawei 3D Beamforming (FDD) (eRAN15.1 - Draft A)
42 pages
Mobility Management in Connected Mode (ERAN3.0 - 07)
No ratings yet
Mobility Management in Connected Mode (ERAN3.0 - 07)
359 pages
TSEL LTE OMC Guideline - V9
No ratings yet
TSEL LTE OMC Guideline - V9
131 pages
00-Guide To Features (eRAN15.1 - 05)
No ratings yet
00-Guide To Features (eRAN15.1 - 05)
102 pages
Cellmlb: MO MO Parameter Default Optime Value
No ratings yet
Cellmlb: MO MO Parameter Default Optime Value
1 page
07 - LTE Mobility Management
No ratings yet
07 - LTE Mobility Management
59 pages
Load Balancing FDD-TDD
No ratings yet
Load Balancing FDD-TDD
4 pages
UMTS Multi Carrier Strategy and Configuration 20100622 1
No ratings yet
UMTS Multi Carrier Strategy and Configuration 20100622 1
44 pages
LTE Basic Optim v2
No ratings yet
LTE Basic Optim v2
13 pages
Huawei NodeB CE Utilization Guide
100% (1)
Huawei NodeB CE Utilization Guide
4 pages
Interoperability Between UMTS and LTE (RAN16.0 - Draft A)
No ratings yet
Interoperability Between UMTS and LTE (RAN16.0 - Draft A)
1,534 pages
Inter-RAT Configuration Guide
No ratings yet
Inter-RAT Configuration Guide
4 pages
Telecom Network Audit Checklist
No ratings yet
Telecom Network Audit Checklist
8 pages
GENEX Assistant V5 User Guider
No ratings yet
GENEX Assistant V5 User Guider
32 pages
ERAN Capacity Monitoring Guide
No ratings yet
ERAN Capacity Monitoring Guide
37 pages
LTE Rollout Performance Analysis
No ratings yet
LTE Rollout Performance Analysis
19 pages
Layered Paging in Idle Mode
100% (1)
Layered Paging in Idle Mode
2 pages
Neighbor Audit With OMStar
No ratings yet
Neighbor Audit With OMStar
8 pages
4G RF CLUSTER OPTIMIZATION JBK016 - Rivised
No ratings yet
4G RF CLUSTER OPTIMIZATION JBK016 - Rivised
31 pages
XL NPS RF Design & Tuning Guideline Final
No ratings yet
XL NPS RF Design & Tuning Guideline Final
20 pages
LTE L900 Hygiene Report
No ratings yet
LTE L900 Hygiene Report
44 pages
Geran/Ran/Eran Optimization and Troubleshooting Tools Set: Egor Martiniuc
No ratings yet
Geran/Ran/Eran Optimization and Troubleshooting Tools Set: Egor Martiniuc
57 pages
HUAWEI 2nd Carrier Service Strategy
100% (1)
HUAWEI 2nd Carrier Service Strategy
15 pages
Toaz - Info Lte Pci Self Optimization Feature v100r015c10 01pdf en PR
No ratings yet
Toaz - Info Lte Pci Self Optimization Feature v100r015c10 01pdf en PR
74 pages
GSM GUL Interoperability Performance Assessment and Optimization V1.0
No ratings yet
GSM GUL Interoperability Performance Assessment and Optimization V1.0
34 pages
Introduction To LTE: Security Level
No ratings yet
Introduction To LTE: Security Level
40 pages
TRX DG-UG Guideline - v2
No ratings yet
TRX DG-UG Guideline - v2
5 pages
GSM Handover: Algorithm Principles and KPI Analysis
No ratings yet
GSM Handover: Algorithm Principles and KPI Analysis
44 pages
UMTS UL&DL Capacity Improvement Solution - V1R2.0
No ratings yet
UMTS UL&DL Capacity Improvement Solution - V1R2.0
66 pages
B - 04 - TDD LTE Network Access Optimization Guide
No ratings yet
B - 04 - TDD LTE Network Access Optimization Guide
30 pages
Mop NPM XL Project North 2G HUAWEI Add TRX: Prepared By: Reviewed By: Approved by
No ratings yet
Mop NPM XL Project North 2G HUAWEI Add TRX: Prepared By: Reviewed By: Approved by
10 pages
Cluster Acceptance Certificate (CAC) Lte Project
No ratings yet
Cluster Acceptance Certificate (CAC) Lte Project
52 pages
Common Parameters For Cluster Opti v6
0% (1)
Common Parameters For Cluster Opti v6
19 pages
UMTS HSDPA Throughput Optimization Modified
No ratings yet
UMTS HSDPA Throughput Optimization Modified
30 pages
LTE Optimization Analyze 89P
No ratings yet
LTE Optimization Analyze 89P
88 pages
Telkomsel Lte FDD Interworking Strategy For l1800 Amp U900 U2100
No ratings yet
Telkomsel Lte FDD Interworking Strategy For l1800 Amp U900 U2100
10 pages
SJ-20131203170829-006-ZXSDR UniRAN FDD-LTE Base Station (V3.20.30) Radio Parameters Reference - 558739
100% (1)
SJ-20131203170829-006-ZXSDR UniRAN FDD-LTE Base Station (V3.20.30) Radio Parameters Reference - 558739
341 pages
ZTE - UMTS Idle Mode & Common Channel Behavior Feature Guide PDF
No ratings yet
ZTE - UMTS Idle Mode & Common Channel Behavior Feature Guide PDF
147 pages
Step 1: Login U2000 and Link To Maintenance Client: Huawei Technologies Co., Ltd. Huawei Confidential
No ratings yet
Step 1: Login U2000 and Link To Maintenance Client: Huawei Technologies Co., Ltd. Huawei Confidential
5 pages
3 LTE Interoperability in Connection Mode (LTE-GU)
67% (3)
3 LTE Interoperability in Connection Mode (LTE-GU)
152 pages
Formulas 160516
No ratings yet
Formulas 160516
97 pages
UMTS UL DL Capacity Improvement Solution 007
100% (1)
UMTS UL DL Capacity Improvement Solution 007
65 pages
SR@N12.0 GUL - Interoperability - Guide
No ratings yet
SR@N12.0 GUL - Interoperability - Guide
598 pages
Huawei Team Organization Chart
No ratings yet
Huawei Team Organization Chart
2 pages
Handover (GBSS19.1 01)
No ratings yet
Handover (GBSS19.1 01)
646 pages
Oeo208010 Lte Eran7.0 Kpi Introduction Issue 1.00
No ratings yet
Oeo208010 Lte Eran7.0 Kpi Introduction Issue 1.00
67 pages
New Site Kpi Optimization
No ratings yet
New Site Kpi Optimization
7 pages
Uplink Data Compression (ERAN18.1 - 01)
No ratings yet
Uplink Data Compression (ERAN18.1 - 01)
21 pages
DL CoMP (FDD) (eRAN13.1 - 05)
No ratings yet
DL CoMP (FDD) (eRAN13.1 - 05)
100 pages
Telecom Network Layering Guide
No ratings yet
Telecom Network Layering Guide
7 pages
3G RAN 12 Huawei - Recommended KPIs - v1.0
No ratings yet
3G RAN 12 Huawei - Recommended KPIs - v1.0
13 pages
UMTS Signaling Trace and Analysis
No ratings yet
UMTS Signaling Trace and Analysis
38 pages
MLB (eRAN6.0 02)
No ratings yet
MLB (eRAN6.0 02)
107 pages
Intra-RAT Mobility Load Balancing (eRAN20.0 - 02)
No ratings yet
Intra-RAT Mobility Load Balancing (eRAN20.0 - 02)
237 pages
Huawei eRAN6.0 MLB Feature Intro Duction: Huawei Technologies Co., LTD
No ratings yet
Huawei eRAN6.0 MLB Feature Intro Duction: Huawei Technologies Co., LTD
15 pages
SPD - Huawei ERAN6.0 MLB Feature Introduction
No ratings yet
SPD - Huawei ERAN6.0 MLB Feature Introduction
21 pages
Mobility Load Balancing (5G RAN6.1 - Draft A)
100% (1)
Mobility Load Balancing (5G RAN6.1 - Draft A)
132 pages
3D Beamforming (ERAN12.1 05)
No ratings yet
3D Beamforming (ERAN12.1 05)
50 pages
14-BSC6900 BSC6910 WCDMA RAN15 Routine Operation Maintenance ISSUE 1.00 (Don't Print PPT, Use It With Student Book)
No ratings yet
14-BSC6900 BSC6910 WCDMA RAN15 Routine Operation Maintenance ISSUE 1.00 (Don't Print PPT, Use It With Student Book)
202 pages
09-BSC6900 BSC6910 WCDMA V900R015 Initial Data Configuration Based On CME ISSUE 1.00
100% (1)
09-BSC6900 BSC6910 WCDMA V900R015 Initial Data Configuration Based On CME ISSUE 1.00
116 pages
11-BTS3900 WCDMA V200R015 Local Commissioning
No ratings yet
11-BTS3900 WCDMA V200R015 Local Commissioning
43 pages
02-Bsc6900 v900r015 Wcdma Product Description Issue 1.00
No ratings yet
02-Bsc6900 v900r015 Wcdma Product Description Issue 1.00
96 pages
22-OnW310630 IManager M2000 V200R013 Performance Management ISSUE 1.00
No ratings yet
22-OnW310630 IManager M2000 V200R013 Performance Management ISSUE 1.00
55 pages
10-NodeB WCDMA V200R015 Initial Data Configuration Based On CME
No ratings yet
10-NodeB WCDMA V200R015 Initial Data Configuration Based On CME
78 pages
03-SRAN8.0 - BSC6900BSC6910 Hardware and Capacity Expansion
No ratings yet
03-SRAN8.0 - BSC6900BSC6910 Hardware and Capacity Expansion
31 pages
GSM Network CS Paging Coordination
No ratings yet
GSM Network CS Paging Coordination
122 pages
Seminar5 Synch Netw
No ratings yet
Seminar5 Synch Netw
37 pages
Repeated ACCH: B11 MR1 Ed1.x / Ed2.x Seminar of GSM Network Engineering
No ratings yet
Repeated ACCH: B11 MR1 Ed1.x / Ed2.x Seminar of GSM Network Engineering
129 pages
BSS Dimensionning B10
No ratings yet
BSS Dimensionning B10
154 pages
Traffic Capacity ALU
No ratings yet
Traffic Capacity ALU
10 pages
LAC Dimensioning & MCCCH
No ratings yet
LAC Dimensioning & MCCCH
69 pages
Indor Covarge Solution
No ratings yet
Indor Covarge Solution
38 pages
GSM Network Location Planning Guide
No ratings yet
GSM Network Location Planning Guide
26 pages
Telecom Training Overview
No ratings yet
Telecom Training Overview
44 pages
GSM Training & Traffic Concepts
No ratings yet
GSM Training & Traffic Concepts
81 pages
Delta Counters B10MR2Ed7 B11MR1Ed1 RL
No ratings yet
Delta Counters B10MR2Ed7 B11MR1Ed1 RL
132 pages
Gprs Pcu Mfs
No ratings yet
Gprs Pcu Mfs
67 pages
Hopping Concepts V1: JE DEC URT N
No ratings yet
Hopping Concepts V1: JE DEC URT N
19 pages
BSS Dimensioning Methods B10
No ratings yet
BSS Dimensioning Methods B10
133 pages
This Delta Is Between: B10 Catalogue Edition 19 Corresponding To B10 MR2 Ed7 QD2 B11 Catalogue Edition 14 Corresponding To B11 MR1 Ed1.2
No ratings yet
This Delta Is Between: B10 Catalogue Edition 19 Corresponding To B10 MR2 Ed7 QD2 B11 Catalogue Edition 14 Corresponding To B11 MR1 Ed1.2
197 pages
B10 Features VIP Ed3
No ratings yet
B10 Features VIP Ed3
68 pages
Commercial Vehicle Insurance Policy
No ratings yet
Commercial Vehicle Insurance Policy
14 pages
IvJ08AfXQfCzfNy4Ax77 - PSA - Double Close
No ratings yet
IvJ08AfXQfCzfNy4Ax77 - PSA - Double Close
3 pages
Skull Shaver v. Freedom Grooming - Complaint
No ratings yet
Skull Shaver v. Freedom Grooming - Complaint
19 pages
Class VII Social Science Assessment
No ratings yet
Class VII Social Science Assessment
2 pages
P4-3ATutorial Question Chapter 4
No ratings yet
P4-3ATutorial Question Chapter 4
1 page
Income Taxation Quiz Guide
No ratings yet
Income Taxation Quiz Guide
3 pages
Student Contact Information List
No ratings yet
Student Contact Information List
18 pages
Accounting For Employee Benefits
No ratings yet
Accounting For Employee Benefits
35 pages
Evolution of Philippine Taxation
No ratings yet
Evolution of Philippine Taxation
15 pages
North and South Devide
No ratings yet
North and South Devide
15 pages
Analysis Sums-1
No ratings yet
Analysis Sums-1
10 pages
Maguire - Barden - FINAL AFFIDAVIT PDF (Nuance) W-Highlights
No ratings yet
Maguire - Barden - FINAL AFFIDAVIT PDF (Nuance) W-Highlights
34 pages
Justice Leonen's Dissent on Martial Law
No ratings yet
Justice Leonen's Dissent on Martial Law
2 pages
NAPSA - Penailty Waiver - Guidelines - V03
No ratings yet
NAPSA - Penailty Waiver - Guidelines - V03
8 pages
Levis RSL (SCA)
No ratings yet
Levis RSL (SCA)
2 pages
Transfer Admission Request Letter
No ratings yet
Transfer Admission Request Letter
2 pages
Admission Form 63rd Batch 2024
No ratings yet
Admission Form 63rd Batch 2024
4 pages
Marriage Under Private International Law
No ratings yet
Marriage Under Private International Law
4 pages
Rape Complaint
No ratings yet
Rape Complaint
5 pages
White Certificate of Appreciation Simple Modern Certificate
No ratings yet
White Certificate of Appreciation Simple Modern Certificate
10 pages
Sohail Jawaid - Trade Union Movement in India
No ratings yet
Sohail Jawaid - Trade Union Movement in India
121 pages
36 TH BCS
No ratings yet
36 TH BCS
2 pages
GFA 712S - 2019 Test 1 Memo
No ratings yet
GFA 712S - 2019 Test 1 Memo
8 pages
Technical Traffic Crash Investigators Handbook (Level 3) A Tec
No ratings yet
Technical Traffic Crash Investigators Handbook (Level 3) A Tec
500 pages
U260cdji321050 - 2024-02-13 12:37:43
No ratings yet
U260cdji321050 - 2024-02-13 12:37:43
3 pages
(Month, Day, Year) (Place Where This Agreement Was Executed)
100% (1)
(Month, Day, Year) (Place Where This Agreement Was Executed)
2 pages
ASME AG 1 Code On Nuclear Gas and Air Treatment
50% (2)
ASME AG 1 Code On Nuclear Gas and Air Treatment
12 pages
B'laan Tribal Association
No ratings yet
B'laan Tribal Association
331 pages
Keep Your Focus On Jesus
100% (1)
Keep Your Focus On Jesus
5 pages
Insurance Certificate for Therapists
No ratings yet
Insurance Certificate for Therapists
1 page