Professional Documents
Culture Documents
Eden Net Lte Nokia Dynamic Le Guide
Eden Net Lte Nokia Dynamic Le Guide
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.
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.
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.
LTE Nokia Dynamic Load Equalization DN1000020270 1-1 Table of Contents
Guide
Contents
1 Summary of changes...................................................................................................................................... 5
1 Summary of changes
EdenNet 21 No change.
EdenNet 20 No change.
EdenNet 19 FP 1907 This document describes how the Dynamic Load Equalization module per-
forms load equalization between different co-sector layers and automates
the manual portion of layer management strategy.
The DLE module performs load equalization between layers, by dynamically configuring load profile
parameters that affect the load balancing and traffic steering behavior for each individual cell, while
maintaining level-1 KPIs.
• If all traffic layers are congested, offload traffic to a low band when it is possible.
• Determines load imbalance between co-located cells.
• Distributes load for imbalanced sectors according to a strategy that the user can supply.
• Enables load equalization alignment between active mode and idle mode.
• Reduce blocking and allow traffic absorption in areas where multiple carrier frequency is present.
• Improve the end user experience especially for Non-Guaranteed Bit Rate (Non-GBR) services.
• Dependencies
• Interactions
2.1.1 Dependencies
The LTE DLE module has the following dependencies:
• It relies on the RAN feature, LTE1841: AMLE Inter-frequency Load Equalization. The LTE1841
RAN feature must be activated. If not activated, the DLE module excludes those cells.
• It does not create nor delete AMLEPR, LNHOIF, and IFRIM managed objects. However, the LTE
DLE module provides option to use adapted module for LTE1841 feature activation along with the
creation of these managed objects.
2.1.2 Interactions
The LTE Nokia Dynamic Load Equalization module does not interact with any other EdenNet module.
The module enables the efficient use of network resources on multiple carrier frequencies and
achieves similar user experience independent of the carrier frequency in use. It works in an iterative
mode on consecutive days, taking optimization steps based on the previous day's results.
The LTE DLE module balances the traffic between bands. User can select and configure 3GPP bands
as follows:
• In traffic layers, the minimum number of bands that can be configured is two and the maximum
number is up to the user.
• In coverage layers, the number of bands that can be configured is one.
For more information about the LTE bands used in deployments, see Appendix B: LTE frequency
bands
After the parameter pushes are complete, the module waits for the configured measurement period to
assess the impacts on monitoring metrics, and rollback changes if critical performance degradations is
detected in the network.
1. Check feature activation (optional step): This functionality is applicable when feature activation
is required. By default, this functionality is disabled.
The parameterEnforcement is used to enable or disable the usage of adapted audit modules.
If parameterEnforcement is set to True and the adapted audit module fails to run, then the
LTE Nokia Dynamic Load Equalization module will be stopped.
2. Conduct congestion check: In this step, the LTE Nokia Dynamic Load Equalization module
checks if the traffic layers (for example, B2 and B4) are congested. All cells on trafficLayers
from the same sector must satisfy the congestion criteria. The congestion criteria are present in the
INI configuration file and are therefore configurable. The default criteria are as follows:
If traffic layer cells are congested, the traffic is offloaded to the coverage layer (for example, co-
sector B12) cells. Congested sectors are excluded from load equalization steps for current itera-
tion. They will be evaluated again during next iteration.
3. Check KPI data validity: When module requires KPIs for load evaluation, it checks the entire cells
if all the required data points are present. After outliers are removed, if a cell or sector has less
than dataValidityThreshold, the cell and sector is excluded.
4. Evaluate load: In this step, the module evaluates the load to determine if a sector is load imbal-
anced. There are three options for the loadMetrics parameter:
• Normalize RRC/5Mhz:
The following example illustrates how the load evaluation using normalized RRC/5Mhz triggers
equalization between two traffic layers.
• DL Ue Throughput:
The following example describes how the load evaluation using DL UE Throughout triggers
equalization between two traffic layers.
If loadMetrics is set to ALL, both KPIs must meet conditions mentioned above for the
sector to be an imbalanced sector. If one of the KPIs does not meet the condition, then module
falls back using the KPI which meets the condition criteria. If both KPIs meet the criteria, then
the module applies weight (cost function) on each KPI as a number between 0 and 1, defined
as per rrc5MhzWeight and throughputWeight GUI parameters. The total weight must be
equal to 1. The formula to calculate the load for each cell is:
more information on how the parameter changes are determined, see the Appendix A: Sample pa-
rameter changes template section.
6. Push parameters to network: This step is only applicable for closed loop mode. For every im-
balanced sector, the module pushes new parameter values to cells. After a time period, module
will check for KPI degradation. If any KPI is found degraded, the changes for that sector are rolled
back and the sector is put on the blacklist. Module will not process the sector until its blacklist ex-
pires. Module allows user to specify KPIs via configuration that need to be checked for degrada-
tion.
7. Compare composite available capacity before and after the push: This step collects available
capacity (CAC) data from cells comparing CAC before and after each iteration.
8. Reporting: In this step, the module generates an XLSX report, that lists the following:
• Cell azimuth, angle of the antenna main beam relative to a defined geo-grid reference
• Site ID, the unique ID of the site
Prerequisites
• Prerequisites mentioned in the LTE Nokia Dynamic Load Equalization prerequisites section must
be met.
• 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.
They are not categorized as Generally Available. General Availability implies that the release is
available to all customers.
Expected outcome
The selected module is accessed and the Configure Targets page appears.
4. Continue with Configuring targets for LTE Nokia Dynamic Load Equalization .
Prerequisites
1. To select the target LTE cells for configuration, do one of the following:
• Filter specific cells on map based on Topology Filter or Center Frequency Filter and then
select target cells from the map
Or
• Filter specific cells on map based on Topology Filter or Center Frequency Filter and then
select all filtered items by clicking
Or
Target cells are selected and shown in the Selections pane. For more information about selecting
cells, see the Selecting cells section in the EdenNet User and Administration guide.
2. Click Next.
Expected outcome
The target cells are selected and the Configure Parameters page appears.
3. Continue with Configuring parameters for LTE Nokia Dynamic Load Equalization .
Prerequisites
• Successful completion of Configuring targets for LTE Nokia Dynamic Load Equalization .
1. Define the configuration parameter values. For the list of parameters, see LTE Nokia Dynamic
Load Equalization GUI parameters.
Note:
• You can retain the default values or else select the values from the drop-down list.
• To revert to the default parameter value, click the Default Value icon.
2. Click Next.
Expected outcome
The parameters are configured and the Select Configuration File page appears.
3. Continue with Selecting the configuration file for LTE Nokia Dynamic Load Equalization .
5.5 Selecting the configuration file for LTE Nokia Dynamic Load
Equalization
You can select the configuration files from the list of available configurations.
Prerequisites
• Only files that are activated through module configuration manager are visible. Ensure that the re-
quired module files are active.
• Successful completion of Configuring parameters for LTE Nokia Dynamic Load Equalization .
1. Select the required module configuration file from the Module Global Configuration area.
Note: The Module Global Configuration header displays the number of available active
configurations.
Expected outcome
The configuration file is selected and the Execution Type page appears.
3. Continue with Selecting execution type for LTE Nokia Dynamic Load Equalization .
5.6 Selecting execution type for LTE Nokia Dynamic Load Equalization
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
• Successful completion of Selecting the configuration file for LTE Nokia Dynamic Load Equalization
.
Note: For more information about scheduling the execution, see Configuring execution
type section in the EdenNet User and Administration Guide.
2. Click Next.
Expected outcome
The module is scheduled for execution and the Confirm Execution page appears.
3. Continue with Confirming execution for LTE Nokia Dynamic Load Equalization .
Prerequisites
• Successful completion of Selecting execution type for LTE Nokia Dynamic Load Equalization .
Procedure
Note: You can monitor the activities, status, and events of the LTE Nokia Dynamic Load
Equalization module. For more information, see Monitoring LTE Nokia Dynamic Load
Equalization
Expected outcome
The LTE Nokia Dynamic Load Equalization module is executed based on the configured
parameters and as per the defined schedule.
Range Default
Parameter name Description Step
(min, max) value
loadMetrics The KPI used to indicate load. The options N/A Normalize
are: RRC/5
Mhz
• Normalize
RRC/5 Mhz
• DL Ue
Throughput
• All (AND
condition)
Range Default
Parameter name Description Step
(min, max) value
For example, if
windowsInputTime value is 24,
then for every 24 hours, the module
makes changes for the sector to be
equalized.
Range Default
Parameter name Description Step
(min, max) value
For example:
If degradationCheckTime is set
to 2 hours, and dataStabiliza-
tionTime is set to 45 minutes, the
KPI degradation check procedure
must be executed 2 hours and 45
minutes after parameter changes.
exclusionDays Days that must be excluded from Sun to Sat N/A Sat, Sun
module operations, such as KPI cal-
culations, parameter push, and so
on. The default is Sat and Sun, but
the GUI allows the user to modify.
If blacklistDays is expired
and the module is still running, at
whichever iteration the module is,
the sector will be included into the
algorithm.
Range Default
Parameter name Description Step
(min, max) value
SON Operation Set to Open Loop to run the mod- • Open loop N/A Open
Mode ule in open loop mode. In open loop • Closed loop loop
mode, the module does not automat-
ically push parameter changes to the
network. The user has to manually
provision plans to push changes to
the network.
Plan Name Tag Text that will be added to the names Sequence N/A Empty
of all the plans that will be generated which contains
by this module. any combina-
tions of:
If the target of the module is a whole
specific cluster (and name of this • Uppercase
cluster also matches requirements and low-
Range Default
Parameter name Description Step
(min, max) value
Maximum
length is 20
characters.
Note: The Adapted audit module parameters require user settings only when the para-
meterEnforcement is set to TRUE, otherwise it can be ignored.
Range Default
Parameter name Description Step
(min, max) value
For information
about traffic lay-
ers, see Appendix
B: LTE frequency
bands
coverageLayers List of band used as coverage LTE band accord- N/A B12
layer. ing to 3GPP.
Range Default
Parameter name Description Step
(min, max) value
• Band selected as
traffic layer must
not be used as a
coverage layer.
Note:
• dataValidi-
tyThreshold is
applicable only to
windowsInput-
Time parameter.
• For example, if
windowsInput-
Time is 24 and
dataValidi-
tyThreshold is
90%, the module
requires 22 hours
of data points
to run the algo-
rithm. Otherwise,
the sectors are
skipped.
CM_ATTR_1 = inactivityTimer
Range Default
Parameter name Description Step
(min, max) value
parameter User can decide if Adapted audit (True, False) N/A False
Enforcement modules are required (True) or
not required (False), before run-
ning the Dynamic Load Equal-
ization algorithm.
If parameterEnforcement is
set to True, it enables the calling
of Adapted audit modules.
If parameterEnforcement
is set to False, it disables the
calling of Adapted audit modules
(bypassing module chaining).
[global]
# bands for equalization
trafficLayers = B2,B4
# bands for coverage coverageLayers = B12
dataStabilizationTime = 45
dataValidityThreshold =10
parameterEnforcement = false
[congestion]
kpi_1 = DL PRB Utilization %
kpi_2 = RRC Connected User_5Mhz_numerator cm_attr_1 = inactivityTimer
expression = (kpi_1 >= 70) and (kpi_2 >= (50 if cm_attr_1 == 5 else 65))
Prerequisites
Only users with admin privileges have permissions to modify the INI parameters.
• 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.
They are not categorized as Generally Available. General Availability implies that the release is
available to all customers.
For more details, see the Configuring a module section in the EdenNet User and Administration
Guide.
For the INI file parameters, see section LTE Nokia Dynamic Load Equalization INI parameters.
Active SON Modules and Module History appears in the left pane, and Execution Status
appears in the right pane.
3. In the left pane, click a module either from Active SON Modules or Module History.
Note: The Active SON Modules area displays all active SON module instances which
are in a state other than stopped, completed, or failed. LTE Nokia Dynamic Load
Equalization which is an iterative module, will be visible in the Active SON Modules
section till the module is stopped.
The Module History area of the Status tab displays SON modules in various states of
inactivity like recently stopped, completed, or failed.
Directory Listing For dialog box with a list of files and module names appears.
Set of related Excel files are listed in the Directory Listing For dialog box.
Expected outcome
The module generates reports as Excel files. For more information, see LTE Nokia Dynamic Load
Equalization report.
Table 7: LTE Nokia Dynamic Load Equalization report describes the tabs listed in the LTE Nokia Dy-
namic Load Equalization module report.
Tabs Description
Configuration Configuration tab lists all the GUI and INI parameters with default or user
selected values.
KPI KPI tab lists values of KPIs used by the module to evaluate load and calcu-
late imbalance.
Changes Changes tab lists the parameter changes in all iterations in the closed loop.
MO Attributes MO Attributes tab lists current load configuration parameters used by the
module to fine tune changes to re-balance load.
CacComparison CacComparison tab lists the histogram data derived from M8011C82 -
M8011C86 counters. This data is used to do a comparison before and after
the module run.
Table 8: Configuration
Table 9: Validation
Date Date when the new parameter value has been successfully pushed.
Cell Name Cell name that indicates the band and sector.
For example, BCT11000A11.
Parameter Name Parameter that has the new value for the specific iteration.
Step # Parameter changes can be executed in steps. This column shows the step
with the associated parameter changes.
Table 11: KPI describes the columns in the KPI tab. This tab is common to the KPI data reports gener-
ated in open loop and closed loop operations.
Band Indicates the name of the band to which the cell belongs.
Normalize RRC/5 Mhz Indicates the number of RRC connection per 5 MHz bandwidth. This KPI
used to determine the cell load.
DL Ue Throughput Indicates the Downlink Ue Throughput. This KPI is used to determine the
cell load.
Remark Provides information whether the sector has been equalized or not.
DL PRB Utilization (%) Downlink PRB Utilization is a KPI used to determine the cell congestion.
LTE Access Failure LTE cell accessibility failure rate is a level-1 KPI used to determine the cell
Rate % degradation.
VoLTE Access Failure VoLTE cell accessibility failure rate is a level-1 KPI used to determine the
Rate % cell degradation.
Band Indicates the name of the band to which the cell belongs.
Name and Value Pairs Indicates the list of CM parameters related to load equalization
and balance functions. For example, targetLoadNonGbrDl, cac-
Headroom, deltaCac, maxCacThreshold, sNonIntraSearch, qOff-
Frq, and so on.
Table 13: CacComparison describes the columns in the CacComparison tab. This tab is available in
reports generated in closed loop operations.
CAC_Zero_Initial[%] The initial value (before running module) of Downlink CAC equal to zero,
where counter ID = M8011C81.
CAC_0_20_Initial[%] The initial value (before running module) of Downlink CAC above zero and
below 20, where counter ID = M8011C82.
CAC_20_40_Initial[%] The initial value (before running module) of Downlink CAC above 20 and
below 40, where counter ID = M8011C83.
CAC_40_60_Initial[%] The initial value (before running module) of Downlink CAC above 40 and
below 60, where counter ID = M8011C84.
CAC_60_80_Initial[%] The initial value (before running module) of Downlink CAC above 60 and
below 80, where counter ID = M8011C85.
CAC_80_100_Initial[%] The initial value (before running module) of Downlink CAC above 80 and
below 100, where counter ID = M8011C86.
CAC_Zero_after[%]. The after value (after running module) of Downlink CAC equal to zero,
where counter ID = M8011C81.
CAC_0_20_after[%] The after value (after running module) of Downlink CAC above zero and
below 20, where counter ID = M8011C82.
CAC_20_40_after[%] The after value (after running module) of Downlink CAC above 20 and be-
low 40, where counter ID = M8011C83.
CAC_40_60_after[%] The after value (after running module) of Downlink CAC above 40 and be-
low 60, where counter ID = M8011C84.
CAC_60_80_after[%] The after value (after running module) of Downlink CAC above 60 and be-
low 80, where counter ID = M8011C85.
CAC_80_100_after[%] The after value (after running module) of Downlink CAC above 80 and be-
low 100, where counter ID = M8011C86.
3. From the Module/Service filter, select the required dynamicLoadEqualization instance to view the
event logs.
The event logs can also be viewed using the following filters:
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.
5. Optional: Under Saved Filters, enter a name for the event filter, and save it using the Save As
New Filter option.
Expected outcome
Category: dynamicLoadEqualization
Module Chain Failure warning This event is generated when the dynamic
load equalization module calls the Adapted au-
dit module and the module chaining process
fails.
Sector load Information info This event is generated when the sector (list of
cells) load is already balanced. In such cases,
no action is taken.
• SON activities
• Status
• Events
• Reports
For more information, see the Configure and monitor SON modules section in the EdenNet User and
Administration Guide.
For each vendor, the list of RAN KPIs is listed in the RAN KPIs section of the EdenNet Module Specif-
ic Data For Nokia document.
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 EdenNet Module Specific Data For
Nokia document.
A sample template is provided in this section that shows how the operator must develop their
parameter changes template. As per this sample there are two traffic bands (for example, B2 and B4)
that the operator wants to equalize load.Table 15: Example for parameter changes template describes
the tabs in parameterChangestemplate.xlsx file.
Tabs Description
<B4> Offload <B4>offload tab, when a sector is imbalanced and B4 layer has more load
compared to B2 layer. Parameter changes for the iteration follow the steps in
this template.
<B2> Offload <B2>offload tab is the opposite of <B4> offload, where B2 layer has more load
compared to the B4 layer. Parameter changes for the iteration follow the steps
in this template.
Congestion Congestion tab contains the parameter list to be pushed when all the traffic
layer cells are congested.
level1Deg level1Degtab contains level-1 KPIs to be checked for degradation. If any KPI
is found degraded, the DLE module rollback the changes.
Note: The <B2> offload tab and <B4> offload tab names can change depending on the
bands selected by the user.
• Table 16: <B4> Offload lists the columns in the <B4> Offload tab with example values. The step
value is used to make parameter changes in steps. The LTE Nokia Dynamic Load Equalization
module supports up to five steps.
B4 LNCEL targetLoadGbrDl 50 60 50
B4 LNCEL targetLoadNonGbrDl 75 60 50
B4 LNCEL targetLoadPdcch 80 85 90
B4 LNCEL highLoadGbrDl 80 80 80
B4 LNCEL highLoadNonGbrDl 80 80 80
B4 LNCEL highLoadPdcch 95 95 95
B4 AMLEPR deltaCac 20 10 0
B2 LNCEL targetLoadGbrDl 50 75 75
B2 LNCEL targetLoadNonGbrDl 75 75 75
B2 LNCEL targetLoadPdcch 80 90 90
B2 LNCEL highLoadGbrDl 80 80 80
B2 LNCEL highLoadNonGbrDl 80 80 80
B2 LNCEL highLoadPdcch 95 95 95
B2 AMLEPR deltaCac 15 20 25
B2 LNCEL sNonIntrsearch 28 20 12
B2 IRFIM qOffFrq 0 3 3
• Table 17: <B2> Offload lists the columns in the <B2> Offload tab with example values. The step
value is used to make parameter changes in every iteration. The LTE Nokia Dynamic Load Equal-
ization module supports up to five iterations.
B2 LNCEL targetLoadGbrDl 50 50 50
B2 LNCEL targetLoadNonGbrDl 75 60 50
B2 LNCEL targetLoadPdcch 80 85 90
B2 LNCEL highLoadGbrDl 80 80 80
B2 LNCEL highLoadNonGbrDl 80 80 80
B2 LNCEL highLoadPdcch 95 95 95
B2 AMLEPR deltaCac 15 10 0
B4 LNCEL targetLoadGbrDl 50 75 75
B4 LNCEL targetLoadNonGbrDl 75 75 75
B4 LNCEL targetLoadPdcch 80 85 90
B4 LNCEL highLoadGbrDl 80 80 80
B4 LNCEL highLoadNonGbrDl 80 80 80
B4 LNCEL highLoadPdcch 95 95 95
B4 AMLEPR deltaCac 20 25 30
B2 LNCEL sNonIntrsearch 28 36 40
B2 IRFIM qOffFrq 0 3 3
• Table 18: Congestion lists the columns in the Congestion tab with example values. The step val-
ue is used to make parameter changes in every iteration.
B4 LNCEL tReselEutr 2 0
• Table 19: level1Deg lists the columns in the level1Deg tab with example values.