Eden Net Wcdma MLB Guide

EdenNet 21
WCDMA Mobility Load Balancing Guide

DN09234275
Issue: 1-0
WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 Disclaimer
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein.
This document is intended for use by Nokia' customers (“You”) only, and it may not be used except for the purposes defined in the agreement
between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced,
modified or transmitted in any form or means without the prior written permission of Nokia. If you have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You
are obliged to return it to Nokia and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using
it. Nokia welcome Your comments as part of the process of continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity,
fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia reserves
the right to change any such information and statements without notice. Nokia has made all reasonable efforts to ensure that the content of
this document is adequate and free of material errors and omissions, and Nokia will correct errors that You identify in this document. But,
Nokia' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia does not warrant that the use of
the software in the Product will be uninterrupted or error-free.
N O WA RRA NT Y O F AN Y KI ND , EI T HER EXPR ES S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D TO A N Y

WARR ANT Y OF AVA IL ABI LI T Y, AC CU RAC Y, R EL I A B I L IT Y, T I T L E , N O N - I N F R I N G E M E N T, M E R C H A N TA B I L I TY
OR F IT NE SS FO R A PA RT ICU LAR PU RPO SE, I S M A D E IN R E L AT I O N TO T H E C O N T E N T O F T H I S D O C U M E N T.
IN NO EVEN T WI L L NOK IA B E LI ABLE F OR AN Y DA M A G E S , I N C L U D I N G B U T N O T L I M I T E D TO S P E C I A L ,
D IRE CT, IN D IRECT, I NCI DE NTAL OR C ON SEQ UE N T IA L OR A N Y L O S S E S , S U C H A S B U T N O T L I M I T E D TO LO SS
OF PRO F IT, REVE NU E, B US IN ESS IN T ER RU PT I ON , B U S I NE S S O P P O RT U N I T Y O R D ATA T H AT M AY A R I S E
FRO M T HE USE O F TH IS DO CU M EN T O R T HE IN F OR M AT IO N I N I T, E V E N I N T H E C A S E O F E R R O R S I N O R
OM IS SI O NS FRO M T HI S DOC UM EN T O R IT S CO NT E N T.
This document is Nokia’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the
prior written consent of Nokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their
respective owners, and they are mentioned for identification purposes only.
Copyright © 2021 Nokia. All rights reserved.
Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the
safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this
document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you
as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the
recommendations for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia for
any additional information.
WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 Table of Contents
Contents
1 Summary of changes...................................................................................................................................... 4
2 Overview of WCDMA MLB..............................................................................................................................7

2.1 WCDMA MLB dependencies and interactions......................................................................................... 7
2.1.1 Dependencies................................................................................................................................... 7
2.1.2 Interactions........................................................................................................................................7
3 WCDMA MLB functional description and guidelines.................................................................................. 9

3.1 Operational modes of WCDMA MLB........................................................................................................9
3.1.1 Open loop......................................................................................................................................... 9
3.1.2 Closed loop..................................................................................................................................... 10
4 WCDMA MLB algorithm................................................................................................................................ 11
5 Configuring and executing WCDMA MLB module.....................................................................................13

5.1 WCDMA MLB prerequisites.................................................................................................................... 13
5.1.1 License details................................................................................................................................ 13
5.1.2 CM data and PM data....................................................................................................................14
5.2 Accessing WCDMA MLB........................................................................................................................ 14
5.3 Configuring targets for WCDMA MLB.....................................................................................................15
5.4 Configuring parameters for WCDMA MLB............................................................................................. 15
5.5 Selecting the configuration file for WCDMA MLB...................................................................................16
5.6 Selecting the execution type for WCDMA MLB......................................................................................16
5.7 Confirming execution for WCDMA MLB................................................................................................. 17
6 WCDMA MLB configuration parameters..................................................................................................... 18

6.1 WCDMA MLB GUI parameters...............................................................................................................18
6.2 WCDMA MLB INI parameters.................................................................................................................21
6.3 Configuring INI parameters.....................................................................................................................41
7 Viewing WCDMA MLB reports..................................................................................................................... 43

7.1 WCDMA MLB reports............................................................................................................................. 44
7.1.1 15 minutes report............................................................................................................................44
7.1.2 Daily report......................................................................................................................................46
7.1.3 Specific events report..................................................................................................................... 47
8 Viewing WCDMA MLB events...................................................................................................................... 48

8.1 WCDMA MLB events.............................................................................................................................. 49
9 Monitoring WCDMA MLB..............................................................................................................................51
10 Rollback........................................................................................................................................................ 52
EdenNet 21 © 2021 Nokia 3

WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 Summary of changes
1 Summary of changes
Release Change description
EdenNet 21 No change.
EdenNet 20 FP No change.
2011
2010
2009
2008
2007
EdenNet 19A FP No change.

2004

2003

2002

2001

1912

1911
EdenNet 19A No change.
1907
1906
1905

EdenNet 19 FP Updated sections:

1904
• Instances of Custom modules are changed to Adapted modules in the
following sections:
– Accessing WCDMA MLB

– Configuring INI parameters
EdenNet 18 SP1 No change.

1901

1812

1811
EdenNet 18 Updated section:
• Parameter descriptions in the WCDMA MLB INI parameters section.
EdenNet 17 SP1 Updated sections:

FP1
• WCDMA MLB functional description and guidelines
• WCDMA MLB algorithm
• WCDMA MLB INI parameters
EdenNet 17 SP1 Updated section:
• Added Plan Name Tag parameter in WCDMA MLB GUI parameters.
EdenNet 17 FP1 Added section:
• The Configuring and executing WCDMA MLB module section is enhanced

by adding Selecting the configuration file for WCDMA MLB section.
Updated sections:
• SON Operation mode parameter description is updated in WCDMA

MLB GUI parameters.
• The Configuring INI parameters section is updated with Save As and Set
As Default options. Also, added notes for Delete, Activate, and Deacti-
vate options.
• Modified Viewing WCDMA MLB events.
EdenNet 17 Restructured the document.

Added sections:
• WCDMA MLB dependencies and interactions

• WCDMA MLB algorithm
• WCDMA MLB reports
• WCDMA MLB events
Updated sections:
• Refactored WCDMA MLB functional description and guidelines.

• Added license details and reference to EdenNet module specific data for
supported vendors in WCDMA MLB prerequisites.
• Added WCDMA MLB RAN KPIs and WCDMA MLB impact on the network
details in Monitoring WCDMA MLB.
• ZTE RAN table > [limit.primaryCpichPower] row is updated.
• A note is added in the WCDMA MLB INI parameters section.
EdenNet 16 SP2 Updated sections:
• In the PM data for WCDMA MLB section, the following tables are updated:
– Nokia PM data
– Ericsson PM data
– Huawei PM data
• In the PM data for WCDMA MLB section, ZTE PM data table is newly
added.
• CM data for WCDMA MLB section is updated.
• WCDMA MLB algorithm section is updated.
• Configuring INI parameters section is newly added.
• WCDMA MLB INI parameters section is newly added.
EdenNet 16 This is a new document that provides information on how to plan, configure,
and execute the WCDMA Mobility Load Balancing (MLB) module.
Table 1: Summary of changes

WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 Overview of WCDMA MLB
2 Overview of WCDMA MLB

The primary mechanism of this module is to reduce congestion by temporarily reducing the Common
Pilot Channel (CPICH) power. For the Huawei network, in case of a traffic imbalance, a change in Cell
Individual Offset (CIO) relational handover parameter between co-sector cells is also done.
You can enable or disable the inter frequency congestion reduction and balancing load features sepa-
rately. Through the WCDMA MLB module, you can demonstrate measurable congestion improvement.
The primary objective of WCDMA Mobility Load Balancing (MLB) module is to:
• reduce the congestion related triggers on WCDMA related to downlink power and code congestion
• balance the load between inter-frequency co-sector neighbors
• release the downlink transmission power resources from common channels to traffic channels
Vendor Technology
Nokia WCDMA
Huawei WCDMA
Alcatel-Lucent WCDMA
Ericsson WCDMA
ZTE WCDMA
Table 2: Supported vendor and technology
2.1 WCDMA MLB dependencies and interactions

WCDMA MLB module is dependent on few criteria. It is also recommended to run the module after
running certain modules in EdenNet. For more information, see:
• Dependencies
• Interactions
2.1.1 Dependencies
The WCDMA MLB module adjusts the CPICH power based on congestion and traffic KPIs configured
in the module INI file. It also looks at the intra-frequency neighbors of the module target cells. Hence,
it is necessary to ensure that the correct KPIs are available for the module target cells along with the
right set of neighbors. Else, the module may not mitigate the congestion.

WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 Overview of WCDMA MLB
2.1.2 Interactions
It is recommended to run the Automatic Neighbor Relations (ANR) and Coverage and Capacity Opti-
mization (CCO) modules before running the WCDMA MLB module to ensure that the cells selected to
run are free from missing neighbor and overshooting issues.

WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 WCDMA MLB functional description and
guidelines
3 WCDMA MLB functional description and guidelines

The WCDMA MLB module monitors congestion on the target cells against which the module is exe-
cuted. If localized cell congestion is detected, the module moves the traffic from overloaded cells to
the surrounding cells by modifying the handover offset and CPICH power in increasing steps. If a de-
crease in traffic is detected on a congested cell following mitigation, the mitigation is reduced.
The EdenNet WCDMA MLB module aims to solve:
• Downlink power related congestion, code congestion, or hardware congestion through temporary
reduction of CPICH of the source cell and the co-sector cells.
• Large traffic imbalances between the co-sector cells.
The downlink CPICH power changes are done in a series of up to 7 small (user definable) step sizes.
The amount of mitigation depends on whether the congestion trigger used as the input is reduced to
the acceptable levels. If the cell continues to be congested beyond step 7, there is an overall timer
(defaulted to 8 hours = 28,800 seconds) as defined by the GUI parameter Max Hold Time is started
and upon expiry of this timer, the cells CPICH is reset back to its original value.
When large traffic imbalances are detected, the CIO offset values between the co-sectors are only ap-
plied once in a timer interval (defaulted to 8 hours = 28,800 seconds). Upon expiry of the timer the CIO
step change from a->b and the opposite CIO step change from b->a will be returned to the original val-
ues.
All KPI data (for target cell) must be recorded at every 15 minute interval. Neighbor cell data (traffic da-
ta) must also be collected at every 15 minute interval.
The module will only commit to changes when run in closed loop. When run in closed loop mode, the
module reports are created after the module has validated whether or not the changes pushed to the
network were successful.
The module can be stopped at any time and any parameter modifications (CPICH power) made are
returned to the original settings.
3.1 Operational modes of WCDMA MLB

WCDMA MLB module supports the following mode of operations:
• Open loop
• Closed loop
3.1.1 Open loop

In open-loop mode, no changes are applied to the network. The module output consists of two reports:
• The daily event log file - This file lists the cells for which congestion is detected at any point during
the day.

WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 WCDMA MLB functional description and
guidelines
• The 15 minute log file - This file lists the cells for specified 15 minute interval for which congestion
was detected.
3.1.2 Closed loop

After running the same algorithm as in open-loop mode, the recommended changes are pushed to the
live network.
Note: It is recommended to run this module in closed loop.
The module output consists of two reports:
• The daily event log file - This file lists all congestion, mitigation, pruning and data pause events.
• The 15 minute log file - This file lists the same information as in daily event log file in addition to
the original CPICH and current CPICH settings.

WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 WCDMA MLB algorithm
4 WCDMA MLB algorithm

Upon triggering the WCDMA MLB module, the following steps are executed in each iteration:
1. For a scope of cells, the module verifies if the cells are congested based on the KPI defined in the
congestion_triggers INI parameter. If multiple congestion_triggers are defined in the
INI file, the algorithm considers the cell as congested if any of the congestion_triggers KPIs
are above the threshold.
2. Congested cells detected from the above step are considered for mitigation. The number of
congested cells considered for mitigation are limited. That is, it must be less than or equal to the
Congestion Pen Size GUI parameter value.
Note: The algorithm stores the original CPICH value of the cell when the cell is mitigated
for the first time. The algorithm uses the original CPICH as reference to mitigate the cell’s
power in the case of congestion.
3. The algorithm attempts to mitigate the CPICH power for each cell in the congestion pen. As part of
this:
a. The congested cells CPICH is reduced by one step from the cell’s original CPICH value in each
iteration starting from step 0 up to step 7 as defined by the mitigation_states.x.custom
INI parameter (x denotes step value between 0-7).
b. Based on the Change_cpich_type GUI parameter, only source, or source and its co-sector/
co-band cells CPICH is reduced accordingly.
c. If the mitigation_states.x.cell INI parameter (x denotes step value between 0-7)
is defined, the algorithm reduces the value of the specified cell level parameter by a value
specified in the corresponding step.
d. The algorithm also starts a timer for each cell when the cell is first mitigated, as defined by the
Max Hold Time GUI parameter. This timer is used to guard against cells which continue to be
congested even after mitigation beyond step 7. Upon expiry of this timer, the algorithm reverts
the CPICH value of the cell to its original value.
4. The algorithm evaluates for traffic degradation for the cells mitigated in the previous iteration based
on the KPI defined in the traffic_triggers INI parameter. The evaluation for traffic triggers
can include source and/or neighbor. The type of neighbors evaluated for traffic degradation is
defined by the target INI parameter (under the traffic_triggers.neighbor section). The
algorithm evaluates if all the configured traffic_triggers are degraded when compared with
the previous iteration. If traffic degradation is identified, the CPICH value for the cell is reverted
to its previous step. Similarly, if the mitigation_states.x.cell INI parameter is defined,
the algorithm reverts the value of the specified cell level parameter also to the previous step. If
the traffic continues to be degraded in subsequent iterations, the algorithm pauses the mitigation
(mitigation frozen) for the cell until the timer defined by the Max Hold Time GUI parameter
expires.

WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 WCDMA MLB algorithm
5. The algorithm validates such that the CPICH power of the cell in any iteration never goes
below the value defined in the min_limit INI parameter or exceeds the value defined in the
max_limit INI parameter.
Note: In case of Huawei, the minimum limit and maximum limit is validated against the
parameters MINPCPICHPOWER and MAXPCPICHPOWER of the UPCPICH managed object
class respectively.
6. In each iteration, the algorithm also detects if there is an outage scenario. The outage scenario is
defined as below:
a. For each target cell, fetch all the first tier intra frequency neighbors. If all these neighbors are
congested, respective target cell is not mitigated.
b. If there are at least one or more cells in the first tier intra frequency neighbors that is not
congested, the algorithm fetches all the intra frequency neighbors in first x tiers as defined
by the threshold_tier INI parameter, sorted according to the descending value of the
KPI defined by the ho_attempts_kpi INI parameter. If first N number of these neighbors
are congested, respective target cell is mitigated. The parameter N is defined in the
congested_neighbors_threshold_count INI parameter.
Note: The above check for evaluating outage detection is executed by the algorithm
irrespective of whether the [congestion_related_outage_params] INI parameters
are defined or not.
7. If at any instance, the module is stopped from the GUI, the algorithm reverts the CPICH value for
all the cells in the scope which are currently under mitigation to its original CPICH value.
8. For each cell that is mitigated, the algorithm logs the details such as cell’s congestion, mitigation,
CPICH values, status, trigger reason, and so on. The report can be extracted from the GUI. For
more information, see Viewing WCDMA MLB reports.

WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 Configuring and executing WCDMA MLB
module
5 Configuring and executing WCDMA MLB module

To configure and execute a module, you must access WCDMA Mobility Load Balancing from EdenNet and configure required
parameters.
Configure and execute the WCDMA Mobility Load Balancing module in the following order:
1. Accessing WCDMA MLB
2. Configuring targets for WCDMA MLB
3. Configuring parameters for WCDMA MLB
4. Selecting the execution type for WCDMA MLB
5. Confirming execution for WCDMA MLB
Expected outcome
WCDMA Mobility Load Balancing is executed based on the configuration parameters and as per
the defined schedule.
5.1 WCDMA MLB prerequisites

Before running the WCDMA MLB module, ensure the following:
• Import, activate, and integrate the WCDMA MLB module with the respective EMS/NMS. For exam-
ple, NetAct, in case of vendor Nokia.
• For license details, see License details.
• CM data and PM data is available.
• Up-to-date cell location information is available through antenna objects for each WCDMA cells in
EdenNet database (Upload a cell plan file, if needed).
• Choose a scope on which WCDMA MLB module can operate.
• Select WCDMA cells in scope, which are having degradation in one or more KPIs.
• Import the module configuration file (ini file). For more information, see Configuring INI parame-
ters.
• Google Chrome or Mozilla Firefox are the recommended browsers to access EdenNet.
5.1.1 License details

Table 3: License details for WCDMA MLB lists the license required to access the WCDMA MLB mod-
ule in EdenNet.

module
Licensed feature com- Licensed feature com-

LK item code LK item object name
ponent code ponent name
ENSW6124CLK WCDMA MLBO CLK 0000025961 3G MLBO
Table 3: License details for WCDMA MLB
5.1.2 CM data and PM data

• CM and PM data used by the module for each vendor are listed in the following documents:
– EdenNet Module Specific Data For Nokia

– EdenNet Module Specific Data For Ericsson
– EdenNet Module Specific Data For Huawei
– EdenNet Module Specific Data For Alcatel-Lucent
– EdenNet Module Specific Data For ZTE
5.2 Accessing WCDMA MLB

Log in to the EdenNet application and access the WCDMA MLB module to perform any action on the module.
Prerequisites
All the prerequisites mentioned in the WCDMA MLB prerequisites section must be met.
1. Log in to the EdenNet application:

a) In the address field of your Internet browser, type the following URL (for 2VM, 5VM, and Cross-
OSS):
https://<EdenNet GUI_SERVERS IP>
where <EdenNet GUI_SERVERS IP> is the IP address of the GUI server provided during the
installation of EdenNet.
The EdenNet login page appears.

b) In the Username field, type the user name.
c) In the Password field, type the password.
d) Click Log In.
The SON Activity page appears.
2. Click the Configure tab.
The following module categories appear in the left pane:
• EdenNet modules - The modules that Nokia provides are available in this category.
• Adapted modules - The modules that users develop are available in this category.

module
• Helper modules - These modules are mainly used for troubleshooting by Nokia support
teams. These modules are not categorized as Generally Available. General Availability implies
that the release is available to all customers.
3. Click the LoadBalancing module.
Expected outcome
The Configure Targets page appears.
4. Proceed with Configuring targets for WCDMA MLB.
5.3 Configuring targets for WCDMA MLB

In EdenNet, a module can only be configured and executed on a scope of cells. In the Configure Targets page, you can select
cells on the map.
Prerequisites
• Successful completion of Accessing WCDMA MLB.
1. Select the cells for configuration by using:
• map-based or cell ID search selection tools from the map toolbar

• existing clusters
For more information about selecting cells, see the Selecting cells section in the EdenNet User and
Administration guide.
2. Click Next.
Expected outcome
The Configure Parameters page appears.
3. Proceed with Configuring parameters for WCDMA MLB.
5.4 Configuring parameters for WCDMA MLB

To execute a module, you must configure a set of parameters. In the Configuration Parameter page, a list of parameters,
along with the descriptions and default values are displayed.
Prerequisites
• Successful completion of Configuring targets for WCDMA MLB.

module
You can retain the default values or else select the values from the drop-down list.
1. Define the configuration parameter values. For the list of parameters, see WCDMA MLB GUI
parameters values.
2. Click Next.
Expected outcome
The Select Configuration File page appears.
3. Proceed with Selecting the configuration file for WCDMA MLB.
5.5 Selecting the configuration file for WCDMA MLB

You can select configuration files from the list of available active configurations.
Prerequisites
• Successful completion of Configuring parameters for WCDMA MLB.

• Ensure that the required configuration files are activated. For more details, see Configuring INI pa-
rameters.
1. Select the required configuration file from the available categories. If configuration files are not
available, proceed to the next step.
Note: You can select only one configuration file from each category.
2. Click Next.
Expected outcome
The Execution Type page appears.
3. Continue with Selecting the execution type for WCDMA MLB.
5.6 Selecting the execution type for WCDMA MLB

To verify the targets and parameter inputs in the Execution Type page, you can schedule when the module must be executed.
Depending on the type of execution, such as, immediately, later or during a specific date and time, the module is scheduled and
executed.
Prerequisites

module
• Successful completion of Selecting the configuration file for WCDMA MLB.
1. To schedule the module execution, select one of the following options:
• Activate Now - to activate the module immediately.

• Activate Later - to activate the module at a later time.
• Schedule Execution - to schedule the module for execution during a certain date and time.
2. Click Next.
Proceed with Confirming execution for WCDMA MLB.
For more information about scheduling the execution, see the Configuring execution type section in
the EdenNet User and Administration Guide.
5.7 Confirming execution for WCDMA MLB

In the Confirm Execution page, you can view the summary of the operation setup and start the operation. The operation is
executed as per the defined schedule.
Prerequisites
• Successful completion of Selecting the execution type for WCDMA MLB.
Procedure
• After verifying the configuration summary, click Finish.
Expected outcome
The WCDMA MLB module starts execution as per the defined schedule.
You can monitor the operation. For more information, see Monitoring WCDMA MLB.

WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 WCDMA MLB configuration parameters
6 WCDMA MLB configuration parameters

A set of parameters are required to run a module. Module parameters are configured through:
• WCDMA MLB GUI parameters

• WCDMA MLB INI parameters
6.1 WCDMA MLB GUI parameters

Default val-
Parameter name Parameter description Range Step
ue
Congestion Pen Maximum number of cells to 20-200 NA 75

Size load balance at once
Max Hold Time Maximum length of time to hold NA NA 28800 sec-

the cells in the load balance onds
state (in seconds).
The time begins when a cell en-

ters mitigation for the first time
and enters the congestion time.
At the end of the timer expiry pe-
riod, the cell CPICH is returned
to the original set value.
Note: The inter-fre-

quency load balancing
timer is separate and
is available in the con-
figuration file.
Prevent Load Bal- Ensures that the module does • True NA True
ancing mitigation if not push CPICH or CIO changes • False
neighbor list is un- for an interval, if the neighbor list
known CM information is temporary un-
available.
For the traffic loss safeguard to

function properly, the neighbor
lists (all intra-frequency neigh-
bors + co-sited inter-frequency
neighbors) must be available.

Default val-
ue
Ensure there is no unacceptable

traffic loss on neighboring cells.
Note: This parameter

must always be set to
True.
Change_cpich_ It lists the CPICH change condi- • Change only NA Change co-
type tion options. source: Only con- sector co-
gested cell re- band step
duces CPCIH
power, checks
source and co-
sector CPICH
values during mit-
igation.
• Change co-sec-
tor and co-band
step: Congest-
ed cell, co-sector,
and co-band cells
reduce CPICH
value with the
same step.
• Change co-sec-
tor and co-band
value: Congest-
ed cell, co-sector,
and co-band cells
reduce CPICH
value to the same
value.
• Change co-sector
step: Congested
cell and co-sec-
tor cells reduce
CPICH value with
the same step.
• Change co-sector
value: Congested
cell and co-sec-

Default val-
ue
tor cells reduce

CPICH value to
the same value.
SON_Operation_ Set to Open Loop to run the • Open Loop NA Open Loop
Mode module in open loop mode. In • Closed Loop
open loop mode, the module
does not automatically push
parameter changes to the net-
work. The user has to man-
ually provision plans to push
changes to the network. Set to
Closed Loop to run the module
in closed loop mode. In closed
loop mode, changes are auto-
matically pushed to the network
without user intervention.
Plan Name Tag Text that will be added to the Sequence which con- NA NA
names of all plans that will be tains any combina-
generated by this module. tions of:
If the target of the module is a • Uppercase and

whole specific cluster (and name lowercase letters:
of this cluster also matches re- [A-Za-z]
quirements specified in Range • Numbers: [0-9]
column), then the cluster name • Underscore: _
will also be added to the plan
Maximum length: 20
name.
characters
Note: The default plan
name tag generated is
LoadBalancing.
The module generates

a single plan file even
if multiple instances
of the module are ex-
ecuted at the same
time. In such scenario,
the plan name tag de-
fined in the GUI will be

Default val-
ue
added to the plan file

in the following cases:
• all the instances

have the same
plan name tag de-
fined in the GUI.
• only one of the
instance has the
plan name tag de-
fined in the GUI.
Table 4: Configurable GUI parameters of WCDMA MLB module
Note: WCDMA MLB module skips a congested cell if the cell is included in the SON/Mod-
ule exclusion list. However, it is not applicable if only the co-sector and co-band cell or a co-
sector cell of the congested cell is recorded in the SON/module exclusion list but not the con-
gested cell itself.
6.2 WCDMA MLB INI parameters

The .ini file is created using the configuration parameters. The configuration file for WCDMA MLB must
be set properly as it is the input for triggering the mechanism. To configure INI parameters, see Config-
uring INI parameters.
The configuration parameters are classified by RAN vendor as follows:
• Ericsson RAN
• Huawei RAN
• Alcatel-Lucent RAN
• ZTE RAN
• Nokia RAN
Range (min, Default val-

Parameter Parameter Description Step
max) ue
[Global]
write_enabled This parameter determines • True False NA

whether the module should miti- • False
gate and provision the changes in
the closed-loop operation. If the


max) ue
module is running in the closed

loop, then set the value of the pa-
rameter as True.
If the value of the parameter is set

to True, the module mitigates and
provisions the changes. If the value
of the parameter is set to false, the
module mitigates, but does not pro-
vision the changes.
This parameter is only applicable if

the module is running in the closed
loop, but not in the open loop.
Interval This parameter controls how of- NA 900 NA

ten the 3G MLB algorithm should
check for congestion detection,
mitigation, provision, and so on.
resolution KPI aggregation level. • 1 = 15 1 NA
For example, if this parameter val- minutes

ue is set to 1, the module consid- • 2=1
ers the KPIs that are aggregated hour
every 15 minutes. That is, the val- • 3 = daily
ues received from the OSS are
considered as is.
interval_min The PM counter generation interval • 15 min- 15 NA

at EMS. utes
This parameter is used to align the • 30 min-
module with the PM counter gen- utes
eration interval at the EMS so that • 60 min-
it can treat KPIs accordingly and utes
seamlessly work with them. For ex- • 120 min-
ample, if this parameter is set to utes
60 minutes (the PM counter is gen-
erated at the EMS only once per
hour), the module would expect
fresh KPIs to arrive only once in an
hour and adjust itself accordingly
rather than expecting KPIs every


max) ue
15 minutes and reporting that the

KPIs are missing.
operation_name Type of KPI aggregation to be con- • Newest Newest NA

sidered. • Sum
• Average
kpi_delay_periods This parameter indicates the num- 1-8 8 NA

ber of KPI periods to be factored
while fetching KPI data.
For example, consider values:
• resolution =1
• interval_min =15 minutes
• kpi_delay_periods = 8
The module considers the past 8

samples of KPI data (starting from
the latest available set and going
back in time). That is, the past two
hours KPI data (15 minutes x 8
samples) would be considered.
Consider:
• resolution =1
• interval_min =15 minutes
• kpi_delay_periods = 1
If the module is triggered at 15:00,

the KPI of 14:45 is considered. If
the module is triggered at 15:10,
the KPI of 15:00 is considered.
enable_inter_freq_ This field enables inter-frequency • True False NA

load_balancing load balancing. • False

is valid only for Huawei
WCDMA.
min_erlang_inter_ This field requires a minimum com- 1-100 20 NA

abs_trigger bined voice + data erlang traffic of


max) ue
10. For the inter-frequency load

balancing mechanism to start.

WCDMA.
min_erlang_inter_ This field requires the heavily 0-100 25 NA

layer_delta_% loaded sector to be at least 25%
more loaded (in terms of combined
Erlangs) than the next loaded co-
sector for the load balancing mech-
anism to start.

WCDMA.
cio_interfreq This field denotes the magnitude of -24 to 24 -2 NA

the CIO offset change (db).

WCDMA.
interfreq_traffic_ This field enables the inter- • True Yes NA

footprint_enabled freq_traffic_footprint • False
check.
If the field is set to Yes, then this

mechanism will ensure that the
coverage footprint of the heavi-
ly loaded sector is not significant-
ly greater than the sector that the
traffic is steered towards.

WCDMA.
footprint_bin_delta If the interfreq_traffic_ 0-1 0.5 NA

footprint_enabled field is
set to Yes, then this parameter


max) ue
is used to determine the accept-

able amount of footprint imbalance
(as measured by the Cumulative
Distribution Framework (CDF) of
PRACH distance) from the heavi-
ly loaded sector to the less loaded
sector.

WCDMA.
distant_starting_ This is the PRACH bin that the cu- 1-11 6 NA

bin mulative CDF begins from (through
bin 11) to determine the footprint
imbalance.

WCDMA.
maximum_hold_ This is the timer for the conges- Hour 28800 sec- 3600 secs
time_inter_freq_lb tion pen for inter-frequency (in seconds (8
onds). hours)

WCDMA.
[mitigation_states. Contains the values for steps 1-7 NA -0.4 for step -0.4
x.custom] by which the source CPICH power 1 and incre-
is modified. mented by
-0.4 for each
Note: Replace x by num-
step till step
ber.
7.
[mitigation_states. Contains the values for steps 1-7 NA NA NA

x.cell] by which the defined cell parame-
ters are modified.
module = load- This is a hardcoded value and rec- NA NA NA

balance.oss. ommended not to be changed.


max) ue
builder:get_
changes
<CPICH power pa- The CPICH power to be reduced in NA Recommend- • For oth-
rameter name with each step (in dBm). ed is as fol- er ven-
value> lowing: dors: 0.
• Huawei: Use PCPICHPOWER
as key name • For other 5 dBm
• Nokia:Use PtxPrima- vendors: • For

ryCPICH as key name 0 for step Huawei:
• ZTE: Use primaryCpich- 0, 0.5 for 5 dBm
Power as key name step 1
• Alcatel-Lucent: Use pcpich- and in-
Power as key name crement-

ed by 0.5
• Ericsson: Use prima-
for each
ryCpichPower as key name
step till
step
• For
Huawei:
0 for step
0, 5 for
step1
and in-
crement-
ed by 5
till step 7
[congestion_re- Settings for detection of Outage in NA NA NA

lated_outage_ the network.
params]
ho_attempts_kpi Deciding KPI to rank the neigh- Intra_HO_At- NA NA

bors. tempts
threshold_tier Neighbors for the configured tier is NA 3 NA

fetched for outage detection.
congested_neigh- The number of neighbors to select NA 10 NA

bors_threshold_ from the specified tiers.
count
[limit.primaryCpich- The key name change depends on NA NA NA

Power] the vendor.


max) ue
• Nokia: PtxPrimaryCPICH
• ZTE: primaryCpichPower
• Alcatel-Lucent: pcpichPower
• Ericsson: limit.prima-
ryCpichPower
Note: This parame-

ter is not applicable for
Huawei.
min_limit The minimum value of the pri- NA 23.5 NA

maryCpichPower threshold (in
dBm).
Note: This parame-

Huawei.
max_limit The maximum value of the pri- NA 43 NA

maryCpichPower threshold (in
dBm).
Note: This parame-

Huawei.
traffic_triggers. The voice traffic loss in the source NA NA NA

source_ve.Voice cell .
Erlangs
The module uses the KPI specified
for the automatic verification and
the rollback purpose, as described
in WCDMA MLB algorithm section.
decrease_thresh- The threshold to detect the traffic NA 0.2 NA

old loss.
traffic_triggers. The data traffic loss in the source NA NA NA

source_de.HSDPA cell.
Erlangs


max) ue
decrease_thresh- The threshold to detect the traffic NA 0.2 NA

old loss.
traffic_triggers. The voice traffic loss in the neigh- NA NA NA

neighbor_ve.Voice bor cells.
Erlangs
decrease_thresh- The threshold to detect the traffic NA 0 NA

old loss.
target The types of neighbors to look for intra,cosite_ intra,cosite_ NA

traffic loss. inter inter
traffic_triggers. The data traffic loss in the neighbor NA NA NA

neighbor_de.HSD- cells.
PA Erlangs
decrease_thresh- The threshold to detect the traffic NA 0 NA

old loss.
target The types of neighbors to look for intra,cosite_ intra,cosite_ NA

traffic loss. inter inter
congestion_trig- The KPI used to identify the con- NA NA NA

gers gestion. If the KPI crosses the de-
fined threshold limit, then the cell is
assumed to be under congestion.
Note: The KPIs specified

under the congestion_
triggers parameter is
vendor specific.
rollback_retry_at- The number of times the module NA 2 NA

tempts must retry the rollback if rollback to
original CPICH fails for a cell.


max) ue
Note: Currently, the roll-

back failure retry is sup-
ported for only Nokia.
Table 5: ini configuration file parameters
Explanation for .ini file format
Congestion trigger
This configuration specifies the KPI used to identify the congestion. If the KPI crosses the defined
threshold limit, then the cell is assumed to be under congestion.
For example,
[congestion_triggers.RRC_CONNECTION_REJECT Level ]
threshold = 5
Traffic trigger
This configuration is used as safeguard if the CS or the PS traffic is decreased more than the thresh-
old and the cell continues to be congested. In such cases, the CPICH value of the cell is rolled back to
the previous step.
For example,
[traffic_triggers.source_de.HSDPA Erlangs]
decrease_threshold = 0
CPICH power limit
This configuration indicates the minimum and maximum limit of CPICH power.
For example,
[limit.primaryCpichPower]
min_limit = 23.5
max_limit = 43
Mitigation
This configuration is used to mitigate congestion. There are seven levels of mitigations, and at each
level the amount by which the CPICH power has to be reduced is determined by the primaryCpich-
Power parameter.
For example,

[mitigation_states.7.custom]
primaryCpichPower = -2.5
module = loadbalance.oss.builder:get_changes
Parameter
[congestion_triggers.RRC_CONNECTION_REJECT Level ]
threshold = 5
[congestion_triggers.high_dl_power.Congestion control triggered--High DL Power]
threshold = 1
[congestion_triggers.hs_downswitch.HS downswitches due to congestion]
threshold = 1
[congestion_triggers.eul_downswitch.EUL downswitches due to congestion]
threshold = 1
[congestion_triggers.dl_codes.Congestion due to Lack of DL Codes]
threshold = 1
[congestion_triggers.dl_power.Congestion due to Lack of DL Power]
threshold = 1
[congestion_triggers.dl_hw.Congestion due to Lack of DL HW]
threshold = 1
[congestion_triggers.ul_hw.Congestion due to Lack of UL HW]
threshold = 1
[traffic_triggers.source_ve.Voice Erlangs]
[traffic_triggers.neighbor_ve.Voice Erlangs]
target = intra,cosite_inter
[traffic_triggers.neighbor_de.HSDPA Erlangs]

Parameter
min_limit = 23.5
max_limit = 43
[congestion_related_outage_params]
ho_attempts_kpi=Intra_HO_Attempts
threshold_tier=3
congested_neighbors_threshold_count=10
primaryCpichPower = 0

Parameter
[global]
write_enabled=True
interval=900
enable_inter_freq_load_balancing=No
Table 6: Ericsson RAN
Parameter
[congestion_triggers.rtwp.UL RTWP Level]
threshold = -5
[congestion_triggers.congestion3.RRC Connection Rejects for Congestion Reasons]
threshold = 10
decrease_threshold = 0.02
threshold_tier=3

Parameter
PCPICHPOWER = 0
PCPICHPOWER = -5
PCPICHPOWER = -10
PCPICHPOWER = -15
PCPICHPOWER = -20
PCPICHPOWER = -25
PCPICHPOWER = -30
PCPICHPOWER = -35
[global]
write_enabled=True
interval=900

Parameter
enable_inter_freq_load_balancing=Yes
min_erlang_inter_abs_trigger=20
min_erlang_inter_layer_delta_%=25
cio_interfreq=-2
interfreq_traffic_footprint_enabled=Yes
footprint_bin_delta=.05
distant_starting_bin=6
maximum_hold_time_inter_freq_lb=28800
enable_intra_freq_load_balancing=Yes
Table 7: Huawei RAN
Parameter
[congestion_triggers.congestion1.Average RTWP]
threshold=-35
[congestion_triggers.congestion2.RAB_FailEstab_CS_DLPwr]
threshold=1
[congestion_triggers.congestion3.RAB_FailEstab_CS_RLFailNodeBResource]
threshold=1
decrease_threshold =0.02

Parameter
[limit.pcpichPower]
min_limit = 25
max_limit = 43
threshold_tier=3
pcpichPower = 0
pcpichPower = -0.5
pcpichPower = -1.0
pcpichPower = -1.5
pcpichPower = -2.0
pcpichPower = -2.0
pcpichPower = -2.0

Parameter
pcpichPower = -2.5
[global]
write_enabled=True
interval=900
Table 8: Alcatel-Lucent RAN
Parameter
[congestion_triggers.congestion1.RRC_Connection_Rej_Cong]
threshold=1
[congestion_triggers.congestion2.RRC_Connection_Rel_DCCH_Cong]
threshold=1
[congestion_triggers.congestion3.RRC_Connection_Rel_CCCH_Cong]
threshold=1
[congestion_triggers.congestion4.RRC_Connection_Failure_Adm]
threshold=1
[congestion_triggers.congestion5.RRC_Connection_Failure_Code]
threshold=1
[congestion_triggers.congestion6.RRC_Connection_DL_PWR]
threshold=1
[congestion_triggers.congestion7.RAB_CS_Setup_Failure_No_Rscs]
threshold=1
[congestion_triggers.congestion8.RAB_CS_Setup_Failure_No_Code]
threshold=1

Parameter
[congestion_triggers.congestion9.RAB_CS_Setup_Failure_DL_Pwr]
threshold=1
[congestion_triggers.congestion10.RAB_PS_Setup_Failure_No_Rscs]
threshold=1
[congestion_triggers.congestion11.RAB_PS_Setup_Failure_No_Code]
threshold=1
[congestion_triggers.congestion12.RAB_PS_Setup_Failure_DL_Pwr]
threshold=1
min_limit = 23.3
max_limit = 43
threshold_tier=3
primaryCpichPower = 0

Parameter
[global]
write_enabled=True
interval=900

Table 9: ZTE RAN
Parameter
[congestion_triggers.rtwp.Average RTWP]
threshold=-35
[congestion_triggers.congestion1.RB Downgrade by Dyn Link Opt due to RL Power Congestion]
threshold=1
[congestion_triggers.congestion2.RB Downgrade by PBS due to Spreading Code Congestion]
threshold=1
[limit.PtxPrimaryCPICH]
min_limit = 27
max_limit = 43
threshold_tier=3
PtxPrimaryCPICH = 0

Parameter
PtxPrimaryCPICH = -0.5
[global]
write_enabled=True
interval=100
rollback_retry_attempts = 2

Table 10: Nokia RAN
Note:
• The modifications done to configuration parameters are not reflected in the immediate
WCDMA MLB trigger. It will be considered from next subsequent iterations.
• The value of the target field for traffic loss KPIs must be configured appropriately as fol-
lowing:
– intra: To check the traffic loss of all intra frequency neighbors

– cosite_inter: To check the traffic loss of all co-site inter frequency neighbors
Operator can view whether the selected cells in scope have inter frequency neighbors. If
it does not have, then it is recommended only to mention intra in the target field.
The configuration file is uploaded to the EdenNet application. For more information on how to upload
the file, see the Configuring a SON Module section in the EdenNet User and Administration Guide.
Note: For further information on how parameters can impact the network, contact Nokia
Technical Support.
6.3 Configuring INI parameters

INI parameters must be available to run a module. You can modify, import, export, delete, activate, or deactivate configuration
files.
Only users with administrator privileges have permission to modify the parameters.

OSS):

d) Click Log In.
2. Click Administration tab.
The following module categories appear in the left pane:

• EdenNet modules - The modules that Nokia provides are available in this category.
• Adapted modules - The modules that users develop are available in this category.
• Helper modules - These modules are mainly used for troubleshooting by Nokia support
teams. These modules are not categorized as Generally Available. General Availability implies
that the release is available to all customers.
3. Select the LoadBalancing module.
4. Click Configure → Module Configuration.
The LoadBalancing Configuration Manager dialog box appears.
5. Select the required configuration category.
You can click:
• Import And Activate: to import a file and activate it immediately.

• Import: to import a file.
• Export: to export the selected file to your system.
• Delete: to delete the selected file from the list.
Note: Users with Administrator or SON Module Manager permissions can delete
the configuration files. The configuration files can be deleted only if they are not used
by other modules.
• Activate: to activate the selected file from the list.
Note: Multiple configurations can be activated.
• Deactivate: to deactivate the activated file.
Note: A file can be deactivated only when it is not used by other modules listed
under Active SON Modules or Module History.
• Set As Default: to set the selected file as the default configuration.

• Reset: to reset the edited parameter values in the selected INI file.
• Save: to save the new version of the configuration after editing the parameter values in the
selected INI file.
• Save As: to save the configuration with a different name.
Note: For more information on how to upload the file, see the Configuring a module
section in the EdenNet User and Administration Guide.
For the INI file parameters, see WCDMA MLB INI parameters .

WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 Viewing WCDMA MLB reports
7 Viewing WCDMA MLB reports

For every execution, WCDMA MLB module generates multiple reports in XLSX format. Each report is displayed in each
worksheet of the Microsoft Excel file.

OSS):

d) Click Log In.
2. Type the user name and password.
3. Click Log In.
The SON Activity page appears displaying active SON modules and SON module activities.
4. Click SON Modules → Status.
Active SON Modules and Module History appears in the left pane, and Execution Status
appears in the right pane.
5. In the left pane, click a module either from Active SON Modules or Module History.
The module execution status appears in the right pane.
6. In the right pane, click Logs.
7. Click the user name next to User Outputs.
The Directory Listing For dialog box appears displaying a list of files with module names.
8. Select the module file name.
A set of related Excel files are listed in the Directory Listing For dialog box.
9. Select a file and open or save it.

Expected outcome
The logs are generated in an Excel.
7.1 WCDMA MLB reports

WCDMA MLB generates the following types of log files:
• Module log status

• Daily log events
– In the open loop mode, the report lists the cells for which congestion is detected at any point
during the day.
– In the closed loop mode, the report lists all congestion, mitigation, pruning, and data pause
events.
• 15 minutes log files
– In the open loop mode, the report lists the cells of the specific 15 minute period for which the
congestion is detected.
– In the closed loop mode, the report lists the daily event log report along with the original
CPICH and current CPICH settings.
7.1.1 15 minutes report

The 15 minutes report generates multiple sheets in the output XLSX such as:
• Mitigation
• Congestion
• Neighbor Congestion
• Config
Inter-Frequency Mitigation and Inter-Frequency KPI (in case of Huawei only if the
enable_inter_freq_load_balancing parameter in INI=Yes/True).
Column name Column description
Cell Target cell
Current State Current Mitigation state as configured in the INI
Original State Previous Mitigation state
Status In mitigation, congestion_pen_full,not_writable_target etc
Trigger Congestion1, Congestion2 and so on (based on the Congestion KPI con-

figured in ini).

Time of State Change Time when congestion was last mitigated
Time Left Time difference between max_hold_time (UI property) - Time when con-
gestion was last mitigated
Trigger Value Name Trigger name corresponding to the KPI which detected the congestion.
Trigger Value Trigger name corresponding to the KPI with the Current and threshold val-
ues.
Current CPICH Value of the current CPICH in dBM (modified in this iteration)
Previous CPICH Value of the previous CPICH in dBM (value prior to the CPICH modifica-
tion)
Original CPICH Value of the Original CPICH in dBM
Neighbor Summed Voice Aggregated traffic KPI for Voice Erlangs for all Intra-Freq neighbors of the
Erlangs target cell.
Neighbor Summed HSD- Aggregated traffic KPI for Data Erlangs for all Intra-Freq neighbors of the
PA Erlangs target cell.
Source Cell Voice Er- KPI for Voice Erlangs of the target cell.
langs
Source Cell HSDPA Er- KPI for Data Erlangs of the target cell.
langs
Region Name of managing OSS
Vendor Name of the vendor OSS
Table 11: Mitigation sheet report
Tabs Details
Cell Target cell
Time of Event Time when the congestion was detected
Event Congestion1, Congestion2, and so on (based on the Congestion KPI con-

figured in ini).
Data Trigger name corresponding to the KPI with the Current and threshold val-
ues.
Region Name of managing OSS

Table 12: Congestion sheet report
Tabs Details
Cell Target cell
Time Time when the congestion was detected
Remarks Indicates the reason if all neighbors of Target cell (configured number of
Tiers as in ini) are congested.
Region Name of the managing OSS
Table 13: Neighbor Congestion sheet report
Tabs Details
Category Indicates the categories of the configuration. For example, Module, Glob-
al, Traffic_Triggers, Mitigation_States, Limits,congestion_triggers, conges-
tion_related_outage_params, and so on.
Parameter Parameter name corresponding to the category. For example, conges-

tion_pen_size, write_enabled, Voice Erlangs, state #, max_limit,RRC_
Connection_Rejects, ho_attempts_kpi, and so on.
Value Value corresponding to each parameter. For example, 200, True, de-
crease_threshold = 0, 5, 43,threshold = 15, Intra_HO_Attempts, and so on
Table 14: Config sheet report
7.1.2 Daily report
The module generates a daily report with the following columns. The daily report is also updated at
every iteration.
Timestamp Date and time when the Event occurred
Write Time The time when the report was updated for that row.
Cell Target cell.
Event Congestion, In mitigation, not_writable_target, and so on.
Event Data Description of the corresponding Event indicating the congestion and mit-
igation details. For example, RB Downgrade by Dyn Link Opt due to RL
Power Congestion: (Threshold: 1.0, Current value: 2.0)RRC_Connec-

tion_Rejects: (Threshold: 1.0, Current value: 2.0)State: 1, Original State:

0, Time Left: 0:16:48, CPICH (Current / Original): (32.6 / 33.1), Neigh-
bor Summed Erlangs (Voice / HSDPA): ( / ), Source Cell Erlangs (Voice /
HSDPA): (2.47903333333 / 8.89333333333)
Table 15: Daily report
7.1.3 Specific events report

In addition to the generic events generated by EdenNet's framework (For example, module started,
module idling, module finished, and so on.), the WCDMA MLB module may generate specific events
such as congestion_detected, increase_mitigation, attempt_to_enter_pen, mitigation_paused_traffic,
prune_cell, exit_pen, and so on. This report is also a daily report (updated once at every iteration of
the module).
Timestamp Date and time when the Event occurred
Write Time The time when the report was updated for that row.
Cell Target cell.
Event For example, congestion_detected, increase_mitigation, attempt_to_en-

ter_pen, mitigation_paused_traffic, prune_cell, exit_pen
Event Data Description of the corresponding Event indicating the congestion and miti-
gation details.
Table 16: Events report

WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 Viewing WCDMA MLB events
8 Viewing WCDMA MLB events

You can view events which are specific to the module.

OSS):

d) Click Log In.
2. Click the Events tab.
A list of filters appears in the left pane.
3. From the Module/Service filter, select the required WCDMA MLB instance to view the event logs.
The event logs can also be viewed using the following filters:
• Name: indicates the name of the event.

• Category: indicates the category of the event.
• Level: indicates the level of the event.
• Source Type: indicates from where the event originates.
• Target Type: indicates to where the event is targeted.
• Target: indicates the target of the event (cell name can be selected).
Note: The common event levels are information and warning. By default, the warning
and error level filters are selected. To view all levels of events, remove the warning and
error level filter.
4. In the Time Range area, set the required time range.
5. Under Saved Filters, enter a name for the event filter or for the combination of filters, and save it
using the Save As New Filter option.
6. Click to apply the filter.
The event log appears.

8.1 WCDMA MLB events

In addition to the generic events generated by EdenNet's framework (for example, module started,
module idling, module finished, and so on), Table 17: Events of WCDMA MLB lists the WCDMA MLB
module specific events.
Category: LoadBalancing
Name Level Description
Congestion detected info This event indicates that the source cell congestion
is detected for the specified cell.
Neighbor congestion de- info This event indicates that all the neighbors (up to
tected the configured tier) of the specified source cell are
congested due to outage scenario.
Traffic decrease detected info This event indicates a decrease in traffic for the
specified cell.
Enter pen attempt info This event indicates that the specified (congested)
cell has entered the congestion pen, that is, the cell
is starting to get mitigated.
Mitigation paused info This event indicates that the mitigation for the spec-
ified (congested) cell is paused due to the unavail-
ability of relevant traffic KPI data.
Increase state attempt info This event indicates that the mitigation for the spec-
ified (congested) cell is increased, that is, the cell’s
CPICH value is getting decreased by the config-
ured amount.
Decrease state attempt info This event indicates that the mitigation for the spec-
ified (congested) cell is decreased, that is, the cell’s
CPICH value is getting increased by the configured
amount.
Cell selected for pruning info This event indicates that the specified (congested)
cell is selected for the pruning because its mitiga-
tion has timed out. This means the cell will exit the
congestion pen and will not be mitigated any fur-
ther.

Name Level Description
Mitigation exceeded info This event indicates that the specified (congested)
cell cannot be mitigated any further and therefore,
will be skipped.
Exit congestion pen info This event indicates that the cell is removed from
the congestion pen.
Maximum rollback at- critical This event indicates that the rollback to the origi-
tempts reached nal CPICH value has failed for the specified cell de-
spite having exhausted the configured maximum
number of rollback re-attempts.
Rollback failed warning This event indicates that the rollback to the origi-
nal CIPCH value has failed in the current attempt
for the specified cell and that the rollback will not be
re-attempted in the next iteration of the module.
Rollback success info This event indicates that the rollback to the original
CPICH value is successful for the specified cell.
Table 17: Events of WCDMA MLB
Note: The following events are logged only for Nokia vendor:
• Rollback success
• Rollback failed
• Maximum rollback attempts reached

WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 Monitoring WCDMA MLB
9 Monitoring WCDMA MLB

You can monitor the WCDMA MLB module's:
• activities
• status
• events
For more information, see the Configure and monitor SON modules section in the EdenNet User and
Administration Guide.
WCDMA MLB RAN KPIs
For each vendor, the list of RAN KPIs is listed in the RAN KPIs section of the following documents:
• EdenNet Module Specific Data For Nokia

• EdenNet Module Specific Data For Ericsson
• EdenNet Module Specific Data For Huawei
• EdenNet Module Specific Data For Alcatel-Lucent
• EdenNet Module Specific Data For ZTE
WCDMA MLB impact on the network
For each vendor, the managed object that is created, deleted, or modified in a network is mentioned in
the Actions column of the CM objects or parameters section in the following documents:
• EdenNet Module Specific Data For Nokia

• EdenNet Module Specific Data For Ericsson
• EdenNet Module Specific Data For Huawei
• EdenNet Module Specific Data For Alcatel-Lucent
• EdenNet Module Specific Data For ZTE

WCDMA Mobility Load Balancing (MLB) DN09234275 1-0 Rollback
10 Rollback
Several modules in EdenNet support automatic verification and rollback. In addition, EdenNet supports
the manual rollback.
If there is a need for manual rollback of the pilot power changes provisioned by 3G MLB, the Rollback
tab provides the capability to revert the network elements to a specific date and time of a previous net-
work state of operation. For more information, see the Applying rollback section in the EdenNet User
Guide and Administration Guide.
Note: In case the vendor is Huawei, the rollback for PCPICHPOWER should be executed on
the UCELL object.
If rollback to original CPICH fails for a Nokia cell, module retries rollback based on the configuration
parameter rollback_retry_attempts. Module does not attempt further rollback if rollback fails
even after the configured number of retry attempts.

Eden Net Wcdma MLB Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Eden Net Wcdma MLB Guide

Uploaded by

Copyright:

Available Formats

EdenNet 21

WCDMA Mobility Load Balancing Guide

N O WA RRA NT Y O F AN Y KI ND , EI T HER EXPR ES S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D TO A N Y

Copyright © 2021 Nokia. All rights reserved.

Important Notice on Product Safety

2 Overview of WCDMA MLB..............................................................................................................................7

3 WCDMA MLB functional description and guidelines.................................................................................. 9

4 WCDMA MLB algorithm................................................................................................................................ 11

5 Configuring and executing WCDMA MLB module.....................................................................................13

6 WCDMA MLB configuration parameters..................................................................................................... 18

7 Viewing WCDMA MLB reports..................................................................................................................... 43

8 Viewing WCDMA MLB events...................................................................................................................... 48

9 Monitoring WCDMA MLB..............................................................................................................................51

EdenNet 21 © 2021 Nokia 3

Release Change description

EdenNet 19A FP No change.

EdenNet 19A FP No change.

EdenNet 19A FP No change.

EdenNet 19A FP No change.

EdenNet 19A FP No change.

EdenNet 19A FP No change.

EdenNet 19A No change.

EdenNet 21 © 2021 Nokia 4

Release Change description

EdenNet 19 FP Updated sections:

– Accessing WCDMA MLB

EdenNet 18 SP1 No change.

EdenNet 18 SP1 No change.

EdenNet 18 SP1 No change.

EdenNet 18 SP1 No change.

EdenNet 18 Updated section:

• Parameter descriptions in the WCDMA MLB INI parameters section.

EdenNet 17 SP1 Updated sections:

EdenNet 17 SP1 Updated section:

• Added Plan Name Tag parameter in WCDMA MLB GUI parameters.

EdenNet 17 FP1 Added section:

• The Configuring and executing WCDMA MLB module section is enhanced

• SON Operation mode parameter description is updated in WCDMA

EdenNet 17 Restructured the document.

EdenNet 21 © 2021 Nokia 5

Release Change description

• WCDMA MLB dependencies and interactions

• Refactored WCDMA MLB functional description and guidelines.

EdenNet 16 SP4 Updated section:

• ZTE RAN table > [limit.primaryCpichPower] row is updated.

EdenNet 16 SP3 Updated section:

• A note is added in the WCDMA MLB INI parameters section.

EdenNet 16 SP2 Updated sections:

EdenNet 16 SP1 No change.

Table 1: Summary of changes

EdenNet 21 © 2021 Nokia 6

2 Overview of WCDMA MLB

Table 2: Supported vendor and technology

2.1 WCDMA MLB dependencies and interactions

EdenNet 21 © 2021 Nokia 7

EdenNet 21 © 2021 Nokia 8

3 WCDMA MLB functional description and guidelines

The EdenNet WCDMA MLB module aims to solve:

3.1 Operational modes of WCDMA MLB

3.1.1 Open loop

EdenNet 21 © 2021 Nokia 9

3.1.2 Closed loop

Note: It is recommended to run this module in closed loop.