Professional Documents
Culture Documents
LTE MLB Feature Description (V100R017C10 - 03) (PDF) - EN PDF
LTE MLB Feature Description (V100R017C10 - 03) (PDF) - EN PDF
V100R017C10
Issue 03
Date 2017-03-17
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Scope
This document describes the LTE mobility load balancing (MLB) feature, including
implementation principles, related features, network impact, and engineering guides.
Product Versions
The following table lists the product version related to this document.
SONMaster V100R017C10
Intended Audience
This document is intended for:
l System engineers
l Network management engineers
Change History
03 (2017-03-17)
This is the third commercial release for V100R017C10.
Compared with 02 (2017-02-25) for V100R017C10, this issue does not include any changes.
02 (2017-02-25)
This is the second commercial release for V100R017C10.
Compared with 01 (2017-01-03) for V100R017C10, this issue does not include any changes.
01 (2017-01-03)
This is the first commercial release for V100R017C10.
Compared with Draft B (2016-12-01) for V100R017C10, this issue includes the following
changes.
Change Type Document Change Description
Draft B (2016-12-01)
This is a draft for V100R017C10.
Compared with Draft A (2016-07-28) for V100R017C10, this issue does not include any
changes.
Draft A (2016-07-28)
This is a draft for V100R017C10.
Compared with 03 (2016-06-30) for V100R016C10, this issue does not include any changes.
Organization
1 Overview
2 Technical Description
3 Related Features
4 Network Impact
5 Version Mapping
6 Engineering Guidelines
7 Feature Specifications
8 References
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl
+Alt+A means the three keys should be pressed
concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Contents
3 Related Features...........................................................................................................................13
4 Network Impact........................................................................................................................... 14
5 Version Mapping.........................................................................................................................15
6 Engineering Guidelines............................................................................................................. 16
6.1 Activation Advice.........................................................................................................................................................17
6.2 Information Collection Before the Deployment........................................................................................................... 17
6.3 Feature Deployment..................................................................................................................................................... 18
6.3.1 Deployment Requirements........................................................................................................................................ 19
6.3.2 Data Preparation........................................................................................................................................................ 19
6.3.3 Process....................................................................................................................................................................... 30
6.3.4 Activation Observation..............................................................................................................................................33
6.3.5 Feature Deactivation..................................................................................................................................................33
6.4 Monitoring.................................................................................................................................................................... 33
6.5 Parameter Optimization................................................................................................................................................ 34
7 Feature Specifications.................................................................................................................37
8 References..................................................................................................................................... 45
1 Overview
Background
In a network with multiple frequency bands, high frequency bands have poorer coverage than
low frequency bands and some areas are out of the coverage of high frequency bands, as
shown in Figure 1-1. In addition, frequencies of high frequency bands have higher reselection
priorities than those of low frequency bands.
NOTE
The value range of reselection priority is 0 to 7. A larger value indicates higher reselection priority.
In inter-frequency sectors that share the same site, UEs in idle mode at the center of the
sectors preferentially camp on cells of high-priority frequencies and UEs in idle mode at the
edge of the sectors camp on cells of low-priority frequencies because high-priority
frequencies have limited coverage capability. Considering the uneven UE distribution, if most
UEs distribute at the center of the sectors, excessive UEs camp on cells of high frequency
bands, resulting in signaling congestion. At the same time, fewer UEs camp on cells of low
frequency bands, resulting in improper usage of network resources.
NOTE
Co-sector: The concept of co-sector indicates that used in inter-frequency neighboring cell measurement. The
identification criteria of co-sector configuration are as follows: If the difference between two cells' locations
indicated by latitudes and longitudes is less than 50 m, and the difference between their antenna azimuths is
less than 15 degrees, the two cells are regarded as co-sector co-coverage cells.
Mobility Load Balancing - LTE Idle Mode Inter-Frequency adjusts the inter-frequency
reselection parameters periodically so that UEs in idle mode distribute appropriately among
multiple frequencies. This reduces signaling congestion caused by imbalanced inter-frequency
traffics and addresses the problem of imbalanced usage of air interfaces.
Definition
Mobility Load Balancing - LTE Idle Mode Inter-Frequency adjusts inter-frequency reselection
parameters periodically so that network traffics appropriately distribute among multiple
frequencies, which improves network resource usage and user satisfaction.
Mobility Load Balancing - LTE Idle Mode Inter-Frequency provides the following
optimization methods:
l Automatic optimization: The SONMaster automatically generates optimization advice
and performs parameter optimization without manual intervention.
l Scheduled delivery: The SONMaster automatically generates optimization advice and
performs parameter optimization as scheduled.
l Manual optimization: Users confirm the optimization advice generated by the
SONMaster. Then, the SONMaster performs parameter optimization based on the
confirmed optimization advice.
SIG The data is obtained from the eNodeB. It allows you to obtain the
frequency band supportability of UEs to check the UE penetration
rate of each frequency.
Benefits
Mobility Load Balancing - LTE Idle Mode Inter-Frequency appropriately distributes UEs in
idle mode among multiple frequencies, thereby reducing signaling congestion caused by
imbalanced inter-frequency traffics and improving resource usage.
Application Scenarios
Mobility Load Balancing - LTE Idle Mode Inter-Frequency can be enabled if the network
meets the following requirements:
l There are co-site co-coverage inter-frequency macro site on the network.
l Cells of low-frequency frequencies have better continuous coverage than those of high-
priority frequencies.
NOTE
Mobility Load Balancing - LTE Idle Mode Inter-Frequency does not support load balancing of multi-RRU
cells and mini sites.
Table 1-3 describes application scenarios of Mobility Load Balancing - LTE Idle Mode Inter-
Frequency.
NOTE
This feature supports only outdoor macro base stations, but does not support small cells and remote
RRU scenarios.
2 Technical Description
Figure 2-1 Cell reselection from a cell of high-priority frequency to that of low-priority
frequency
a. Starting measurement: When the signal level of the serving cell (with a high
reselection priority) SServingCell is smaller than or equal to Snonintrasearch, the UE start
measurement.
b. Reselecting cells: Cell reselection is triggered if the following conditions are met:
n SServingCell < Threshserving,low for the signal level of the serving cell.
n STargetCell > Threshx,low for the signal level of the adjacent cell.
l Cell reselection from a cell of low-priority frequency to that of high-priority frequency
Figure 2-2 Cell reselection from a cell of low-priority frequency to that of high-priority
frequency
a. Starting measurement: When the signal level of the serving cell SServingCell is larger
than Snonintrasearch, the UE searches high-priority frequencies periodically. When the
signal level of the serving cell SServingCell is smaller than or equal to Snonintrasearch,
the UE directly starts the search for high-priority frequencies.
b. Reselecting cells: Cell reselection is triggered if the condition is met
STargetCell>Threshx,high.
l Cell reselection between equal-priority cells
2.2 Principles
Figure 2-4 shows the optimization process of the Mobility Load Balancing - LTE Idle Mode
Inter-Frequency. For details, see Table 2-1.
Figure 2-4 Process of the Mobility Load Balancing - LTE Idle Mode Inter-Frequency
Table 2-1 Mobility Load Balancing - LTE Idle Mode Inter-Frequency optimization
No. Procedure Description
1 Create a region and start an You need to create a region and start a Mobility
optimization feature Load Balancing - LTE Idle Mode Inter-Frequency
feature.
4 Select an inter-frequency The SONMaster optimizes the cell group after you
co-coverage cell group that select an inter-frequency co-coverage cell group
is not optimized that is not optimized.
7 Adjust the inter-frequency If the load difference between the maximum load
reselection parameters for cell and its inter-frequency neighboring cells is
the co-coverage cell group greater than the threshold configured on the GUI,
the SONMaster adjusts the corresponding inter-
frequency reselection parameters to decrease the
number of UEs in the overloaded cells.
10 Execute the KPI rollback After the KPI rollback is enabled and optimization
algorithm advice is delivered, the SONMaster monitors live
network KPIs, and checks whether the
optimization advice is appropriate. If it is
inappropriate, the SONMaster rolls back the
optimization advice and imposes a penalty on this
cell. During the imposing of the penalty, the
SONMaster does not optimize the cell.
3 Related Features
4 Network Impact
l System Capacity
This feature optimizes the inter-frequency reselection parameters of inter-frequency co-
coverage cells so that UEs camp on cells working on low-priority frequencies that are
relatively free instead of cells working on high-priority frequencies. This avoids traffic
congestion that occurs in a certain cell, improving network resource usage and system
capacity.
l Network Performance
This feature reduces the load of cells that have high traffic volumes, improves the RRC
setup success rate, and decreases the average buffer delay of packets by optimizing the
inter-frequency reselection parameters of inter-frequency co-coverage cells. This feature
also improves the throughput of the lightly-loaded cell because extra UEs camp on these
cells.
5 Version Mapping
For details about how to activate this feature, and mapping between the SONMaster, NE
software, and other software, see iManager SONMaster V100R017***_ReleaseDoc_ENG.
You can obtain iManager SONMaster V100R017***_ReleaseDoc_ENG by performing the
following steps:
1. Contact Huawei technical support engineers to log in to http://support.huawei.com.
2. On the Product Support tab page, enter SONMaster in the Search box and select the
displayed navigation path.
6 Engineering Guidelines
l NE function requirements
None
l Software and hardware requirements
The SONMaster has been deployed.
l License requirements
The following license control items are added:
– Mobility Load Balancing - LTE FDD Idle Mode Inter-Frequency
– Mobility Load Balancing - LTE TDD Idle Mode Inter-Frequency
l Operation permission requirements
You have obtained the operation rights for LTE Inter-Frequency Idle Mode MLB
Browser and LTE Inter-Frequency Idle Mode MLB Management under
Application-Level Operation Rights > MLB. If not, apply for the operation rights from
the administrator.
You must prepare the following data before deploying Mobility Load Balancing - LTE Idle
Mode Inter-Frequency:
l LTE engineering parameters, as listed in Table 6-2.
l Optimization policy parameters, as listed in Table 6-3.
l Operational policy parameters, as listed in Table 6-4.
l Frequency weight setting parameters, as listed in Table 6-5.
l Frequency load difference parameters,as listed in Table 6-6.
6.3.3 Process
Figure 6-1 shows the process of Mobility Load Balancing - LTE Idle Mode Inter-Frequency,
Table 6-7 describes the process.
Figure 6-1 Process of Mobility Load Balancing - LTE Idle Mode Inter-Frequency
Procedure Description
Log in to the For detailed operations, see the following section in SONMaster
SONMaster Operation User Guide: Reference > Logging In to the SONMaster.
Procedure Description
Connect to the For detailed operations, see the following section in SONMaster
OSS Operation User Guide: Maintenance Management > OSS
Management.
Prepare basic For detailed operations, see the following section in SONMaster
data. Operation User Guide: Reference > Basic Data Types.
Create a region For detailed operations, see the following section in SONMaster
and start an Operation User Guide: Optimization Region Management > Region
LTE inter- Management.
frequency idle
mode MLB
optimization
feature.
(Optional) Set For detailed operations, see the following section in SONMaster
parameters for Operation User Guide: Optimization Region Management > Policy
LTE inter- Management (Single Region).
frequency idle
mode MLB
optimization.
(Optional)
Manually
deliver the LTE
inter-frequency
idle mode MLB
optimization
advice.
(Optional)
Check the
information
about
exceptions
during LTE
inter-frequency
idle mode MLB
optimization.
Procedure Description
(Optional)
Evaluate the
optimization
effect of LTE
inter-frequency
idle mode MLB
optimization
Method 2 Check the generated logs after the See the following section in
feature is activated. SONMaster Operation User
Guide: System Management >
Viewing and Collecting Statistics
About SON Logs.
Method 3 Check the MLB optimization advice For detailed operations, see the
on the optimization advice following section in SONMaster
management GUI. You are advised to Operation User Guide:
do so after a feature running period. Optimization Region
Management > Feature
Management.
6.4 Monitoring
Inter This If the value of this parameter is too small, the adjustable
frequency parameter range of inter-frequency high-priority reselection
high priority specifies the threshold is limited. This affects the effect of executing
upper/lower upper limit of MLB.
threshold the inter-
frequency
reselection
threshold for
high priority.
Inter- This If the value of this parameter is too small, the adjustable
frequency parameter range of inter-frequency lower-priority reselection
lower priority specifies the threshold is limited. This affects the effect of executing
upper/lower upper limit of MLB.
threshold the inter-
frequency
reselection
threshold for
lower priority.
Idle Mode This If the value of this parameter is too small, the adjustable
Cell offset parameter range of inter-frequency equal-priority reselection
upper/lower specifies the threshold is limited. This affects the effect of executing
Threshold upper limit of MLB.
the cell offset
in idle mode.
7 Feature Specifications
20000 30 90
NOTE
The historical optimization storage time is restricted by periods and duration.
Client Version
Server Version
SUSE 10
operating system SUSE Linux Enterprise Server 10 SP4 and SUSE Linux Enterprise
used by the ATAE Server 11 SP3
cluster system
System Specifications
Maximum Specification
Region Management
The number of
Number of regions is restricted
10 16 32 32 32
regions by that of
equivalent NEs.
Client capability
Number of clients
Number of
that can be
clients that
concurrently
can be 50 50 50 50 50
connected to the
connected
SONMaster
concurrently
system.
Maximum Specification
Number of cell
Number of group that can be
zone 100 100 100 100 100 created in the
templates SONMaster
system.
Number of holiday
Number of policies that can be
holiday 1000 1000 1000 1000 1000 created in the
policies SONMaster
system.
Antenna management
Number of
antennas that can
Number of
1000 1000 1000 1000 1000 be imported in the
antennas
SONMaster
system.
Engineering
parameters for cells
in the surrounding
areas need to be
Maximum imported.
number of Therefore, the
cells whose number of cells
300,00
engineering 300,000 300,000 450,000 450,000 whose engineering
0
parameters parameters can be
can be imported is greater
imported than the number of
cells that can
access the
SONMaster
system.
Maximum Specification
Maximum
number of
Number of
repeaters
repeaters that can
whose 300,00
300,000 300,000 450,000 450,000 be imported in the
engineering 0
SONMaster
parameters
system.
can be
imported
Map management
Size of a
Specification of the
single
e-map file (in ZIP
compressed
300 300 300 300 300 format) that can be
package of
imported into the
the e-map
client.
(unit: MB)
Specification of the
Size of a e-map file (in GRC
single file of or GRD format)
100 100 100 100 100
the e-map that can be
(unit: MB) imported into the
client.
Number of e-maps
Number of
10 30 50 50 50 that can be added
e-maps
on the SONMaster.
Size of the
Specification of the
offline map
offline map file that
file that can 300 300 300 300 300
can be imported
be imported
into the client.
(unit: MB)
Number of offline
Number of
maps that can be
offline map 50 50 50 50 50
added on the
files
SONMaster.
Maximum Specification
The concept
Total "region" is used to
number of 10 16 20 28 32 replace "task" from
regions SONMaster
V100R017C10.
Total number of
Total
tasks that can be
number of
created and
tasks that
executed
can be 20000 20000 20000 20000 20000
concurrently for a
created for a
single feature in the
single
SONMaster
feature
system.
Number of
cell-level Number of cell-
parameter level parameter
templates 20 20 20 20 20 templates for each
(within a feature in each
single region
region)
Optimization advice
Storage
duration of Maximum storage
long-period duration of
90 90 90 90 90
optimization optimization result
result data data.
(unit: day)
Maximum
number of
optimization Maximum number
periods of optimization
within periods within
which long- 30 30 30 30 30 which the
period SONMaster saves
optimization optimization result
result data is data.
saved (unit:
integer)
Maximum Specification
Maximum storage
Storage duration of short-
duration of period or real-time
short-period optimization result
or real-time 3 3 3 3 3 data, for example,
optimization fast ANR and
result data traffic burst. The
(unit: day) specification is
three days.
Maximum
number of Maximum number
2,000,0 2,000,0 2,000,00 2,000,00 2,000,00
SON logs of SON logs that
00 00 0 0 0
(unit: can be saved.
integer)
Storage duration of
Storage
SON exception
duration of
records. The least
SON
common multiple
exception 2 2 2 2 2
is used if multiple
records
optimization types
(unit:
of tasks have
period)
different periods.
Maximum Specification
The SONMaster
records task
execution
information within
Storage each optimization
duration of period. This item
SON task specifies the
14 14 14 14 14
execution maximum number
information of optimization
(unit: day) periods within
which the
SONMaster saves
task execution
information.
Service resumption
Maximum service
interruption
Resumption duration allows for
duration of task resumption
interrupted 360 360 360 360 360 after the
tasks (unit: SONMaster task is
minute) stopped due to an
upgrade or
exception.
KPI evaluation
Storage
duration of
hour-level Storage duration of
KPIs hour-level KPIs
24 24 24 24 24
between between every two
every two cells.
cells (unit:
hour)
Storage
duration of
day-level Storage duration of
KPIs day-level KPIs
7 7 7 7 7
between between every two
every two cells.
cells (unit:
day)
Maximum Specification
Storage
duration of
hour-level Storage duration of
KPIs of a hour-level KPIs of
cell, base 72 72 72 72 72 a cell, base station,
station, or or base station
base station controller.
controller
(unit: hour)
Storage
duration of
day-level Storage duration of
KPIs of a day-level KPIs of a
cell, base 30 30 30 30 30 cell, base station,
station, or or base station
base station controller.
controller
(unit: day)
Maximum number
Maximum
of KPIs selected
number of
for an object when
KPIs 10 10 10 10 10
you compare
selected for
multiple KPIs of
an object
the same object.
Maximum number
Maximum
of objects selected
number of
for a KPI when you
objects 10 10 10 10 10
compare the same
selected for
KPI of multiple
a KPI
objects.
File import
8 References
Table 8-1 describes evaluation granularities, evaluation counters, and counter generation rules
related to optimization effect evaluation of Mobility Load Balancing - LTE Idle Mode Inter-
Frequency.
Average L.Traffic.User.Ulsync.Avg(15267 No
Number of UL 28333)
Synchronized
Users in a Cell
Downlink L.Thrp.bits.DL(1526728261)/8 No
Traffic Volume
NOTE
For details about raw counters and counter IDs related to counter generation rules, see 3900 Series Base
Station Performance Counter Reference.