Eden Net Remedy Module Orchestrator Guide

EdenNet 21 FP 2106
Remedy Module Orchestrator Guide

DN1000032733
Issue: 1-1
Remedy Module Orchestrator Guide DN1000032733 1-1 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.
Remedy Module Orchestrator Guide DN1000032733 1-1 Table of Contents
Contents
1 Summary of changes...................................................................................................................................... 4
2 Overview of RMO module.............................................................................................................................. 5

2.1 Supported vendor and technology............................................................................................................5
2.2 RMO dependencies, interactions, and limitations.....................................................................................5
2.2.1 Dependencies................................................................................................................................... 5
2.2.2 Interactions........................................................................................................................................6
2.2.3 Limitations......................................................................................................................................... 6
3 RMO functional description and guidelines................................................................................................. 7

3.1 Operational modes.................................................................................................................................... 7
3.1.1 Open loop mode............................................................................................................................... 7
3.1.2 Closed loop mode.............................................................................................................................7
4 RMO algorithm................................................................................................................................................. 8
5 RMO execution...............................................................................................................................................11
5.1 Prerequisites............................................................................................................................................11
5.1.1 License details................................................................................................................................ 11
5.1.2 PM and CM data............................................................................................................................ 11
5.2 Configuring and executing RMO module................................................................................................11
6 RMO configuration parameters....................................................................................................................15

6.1 RMO GUI parameters............................................................................................................................. 15
6.2 RMO INI parameters...............................................................................................................................16
6.2.1 Example of RMO INI file................................................................................................................ 19
6.3 Importing INI parameters........................................................................................................................ 21
7 Viewing RMO reports.................................................................................................................................... 24

7.1 RMO reports............................................................................................................................................24
7.1.1 Parameters......................................................................................................................................25
7.1.2 Problem Configuration.................................................................................................................... 25
7.1.3 Cell Problem Inferences................................................................................................................. 26
7.1.4 Problem Configuration.................................................................................................................... 26
7.1.5 Recommendation Summary........................................................................................................... 27
7.1.6 Recommendation Details................................................................................................................27
7.1.7 KPI Changes...................................................................................................................................27
7.1.8 Cells Excluded................................................................................................................................ 28
7.1.9 Logs.................................................................................................................................................28
8 Monitor RMO module.................................................................................................................................... 29
EdenNet 21 FP 2106 © 2021 Nokia 3

Remedy Module Orchestrator Guide DN1000032733 1-1 Summary of changes
1 Summary of changes
Release Change description
EdenNet 21 FP 2106 No change.
EdenNet 21 FP 2103 Updated sections:
• Dependencies
• Example of RMO INI file
• Supported vendor and technology - Huawei vendor support is added.
EdenNet 21 This document provides information about the Remedy Module Orches-
trator (RMO) module.
Table 1: Summary of changes

Remedy Module Orchestrator Guide DN1000032733 1-1 Overview of RMO module
2 Overview of RMO module

The Remedy Module Orchestrator (RMO) module identifies problems in an LTE network and executes
the remedy module to resolve them based on Machine Learning (ML). The KPIs from the network indi-
cate a variety of problem levels and consumption characteristics of a cell. This provides an opportunity
to learn and take the appropriate actions to keep the network performance at an optimal level.
The user can specify thresholds that are used by the internal rules. These rules are used for identify-
ing problems and remedy modules in the INI file. User can select the required internal rules from the
available settings in the INI file. The remedy modules are triggered based on their priority.
The RMO module is executed in the following phases:
• Training phase: studies the network based on KPIs and gains intelligence on the state of network.
• Deployment phase: uses the intelligence gained (based on the learning from the training phase)
and predicts the problem definitions and remedy module for each cell.
2.1 Supported vendor and technology

This section provides information about the supported vendors and technology of the Remedy Module
Orchestrator (RMO) module.
Table 2: Supported vendor and technology lists the supported vendors and technology.
Vendor Technology
Nokia LTE
Ericsson LTE
Huawei LTE
Table 2: Supported vendor and technology
2.2 RMO dependencies, interactions, and limitations

For information about dependencies and interactions of the RMO module, see:
• Dependencies
• Interactions
• Limitations
2.2.1 Dependencies
The RMO module has dependency on all the modules listed as a remedy module in the INI file.

Remedy Module Orchestrator Guide DN1000032733 1-1 Overview of RMO module
RMO module has dependency on cell building for fetching the cell type.
2.2.2 Interactions
The RMO module can have interactions if other users on the same EdenNet instance are running the
remedy modules that are run by RMO. In such cases, users might see unexpected outcomes.
2.2.3 Limitations
• The user cannot specify the priority of the remedy modules.
• The user cannot add new problem definitions for finding a problem in the network.
• The remedy modules with iteration frequency less than 12 hours are not supported.
• The RMO module is not suitable for high frequency modules that execute in every 15 minutes.
• The RMO module is compatible only with non-iterative modules and long term iterative modules.
• The RMO module is allocated with 4GB of memory by default. Nokia recommends to increase the
RMO module memory to 6GB for a larger scope of cells, such as 50K cells.

Remedy Module Orchestrator Guide DN1000032733 1-1 RMO functional description and
guidelines
3 RMO functional description and guidelines

The RMO module enables operators to run optimization algorithms on a selected scope of 4G cells.
Optimization algorithms are selected from the INI file.
RMO supports the following types of execution:
• Single execution: The RMO module runs in the recommendation mode, where none of the
remedy modules are triggered, rather it will report the problematic cells, associated problems, and
the suggested remedy modules.
• Iterative execution: The RMO module is designed to be executed in an iterative mode
every 12 or 24 hours by default. The module continues triggering the remedy modules if the
recommendation flag is not enabled.
For the list of remedy modules, see Table 4: Problem remedies.
3.1 Operational modes

The RMO module supports the following operational modes:
• Open loop mode

• Closed loop mode
3.1.1 Open loop mode

In the open loop mode, the RMO module triggers the remedy modules.
If the Recommendation Mode parameter is enabled, it will not trigger any of the remedy modules.
The RMO module simply infers the problems and maps them to the remedy modules that are available
in the report.
3.1.2 Closed loop mode

In the closed loop mode, the RMO module triggers the remedy modules.

Remedy Module Orchestrator Guide DN1000032733 1-1 RMO algorithm
4 RMO algorithm
This chapter describes the RMO module algorithm.
The RMO module execution occurs in the following phases:
1. Multilabel generation and ML model training phase: Based on the set of rules (KPI names and
thresholds) defined in the INI file for each cell type (macro, micro, pico, and femto), the cells are
analyzed and a set of unique labels are assigned to each problematic cell in the network. The ML
model is trained based on the KPI values and labels generated. The trained model is saved to be
used later in the problem detection phase.
2. Problem detection phase: The problems in the given set of cells are detected using the trained
ML model. The input data is fed to the deployed model and the problem labels for the given set of
cells are inferred.
3. Remedy module selection phase: Problems identified in the previous phases are used for rem-
edy module selection in this phase. Remedy module selection is done based on the mapping be-
tween the problems identified and the remedy module defined in the configuration file (INI).
This phase follows a heuristic approach for finding the remedy modules. The problem solving lev-
el of each remedy module is pre-defined as HIGH, MID, or LOW. Among the remedy modules pro-
vided from the configuration, the module with the highest priority is executed on the cell upon iden-
tification of the problem. If modules have multiple remedies of the same priority, the RMO algorithm
considers the least executed module.
4. Remedy module execution phase: The system determines the problem definitions and triggers
the remedy modules. The RMO module is executed at an interval specified by the Module Exe-
cution Interval. The retraining of the ML model is done by default on a weekly basis at an in-
terval specified by the ML Model Re-training Interval.
Table 3: Problem identification lists the rules used to identify a problem.
Problem Identification KPI KPI thresholds
Poor VoLTE-SRVCC handover LTE_WCDMA_VoLTE_Handover_Success_ < 95%

Ratio
Weak LTE-WCDMA VoLTE- LTE_WCDMA_Problematic_VoLTE_Han- > 5%

SRVCC Mobility Parameters dover_Ratio
Poor Intra-LTE Handover LTE_Handover_Success_Ratio < 95%
Weak LTE Mobility Parameters LTE_Problematic_Handover_Ratio > 5%
Poor LTE-WCDMA PSHO LTE_WCDMA_PSHO_Success_Ratio < 95%
Weak LTE-WCDMA PSHO Mobil- LTE_WCDMA_Problematic_PSHO_Ratio > 5%

ity Parameters
Poor LTE IRAT Handover LTE_IRAT_Handover_Success_Ratio < 95%

Problem Identification KPI KPI thresholds
High VoLTE Drop Rate VoLTE Drop Rate Market (GCR) > 2%
Poor Downlink Throughput LTE_DL_User_Throughput < 3gbps
Poor Uplink Throughput LTE_UL_User_Throughput < 3gbps
High Service Drop Rate E_UTRAN_E_RAB_Drop_Ratio > 2%
Poor E2E Call Setup Success LTE_E_RAB_Accessibility < 97%

Rate
Poor RRC Setup Complete Rate LTE_RRC_Setup_Success_Rate < 98%
Poor RACH Setup Success Rate LTE_RACH_Setup_Completes_Rate < 95%
Poor Cell Availability LTE_Cell_Availability < 99%
Table 3: Problem identification
Table 4: Problem remedies lists the problem solving level of each remedy module used by the RMO
module.
Problem solving
Problem Remedy modules
level
Poor VoLTE-SRVCC handover VoLTE_SRVCC_Optimization MID
Weak LTE-WCDMA VoLTE- VoLTE_SRVCC_Optimization HIGH

SRVCC Mobility Parameters
Poor Intra-LTE Handover ANR_Blacklisting_and_Cleanup_LTE MID
PCIReuse HIGH
PRACH_Optimization_LTE MID
Weak LTE Mobility Parameters MRO_Intra_InterFreq_LTE HIGH
Poor LTE-WCDMA PSHO Inter-RAT_MRO MID
Weak LTE-WCDMA PSHO Mobili- Inter-RAT_MRO HIGH

ty Parameters
Poor LTE IRAT Handover ANR_4G_IRAT HIGH
High VoLTE Drop Rate VoLTE_SRVCC_Optimization HIGH
Poor Downlink Throughput PCIReuse HIGH
Poor Uplink Throughput PCIReuse HIGH
High Service Drop Rate PCIReuse HIGH

Problem solving
Problem Remedy modules
level
Poor E2E Call Setup Success PCIReuse HIGH

Rate
Poor RRC Setup Complete Rate SleepingCellResolution HIGH
Poor RACH Setup Success Rate PRACH_Optimization_LTE HIGH
Poor Cell Availability CellOutageCompensation HIGH
Table 4: Problem remedies

Remedy Module Orchestrator Guide DN1000032733 1-1 RMO execution
5 RMO execution
This chapter describes how to access the RMO module, select the scope, configure GUI and INI para-
meters, and schedule the module execution.
5.1 Prerequisites
To execute the RMO module, the following prerequisites must be met:
• Google Chrome or Mozilla Firefox Web browser must be installed on your computer.
• The RMO module license must be activated. For more information, see License details.
• Configuration files must be activated. For more information, see the Configuring a module section
in the EdenNet User and Administration Guide.
• PM and CM data must be available.
5.1.1 License details

Table 5: License details lists the license that must be installed to access the RMO module.
Licensed feature Licensed feature component

LK item code LK item object name
component code name
ENSW6292CLK Remedy Modules Orches- 0000058415 Remedy Modules Orchestrator

trator CLK
Table 5: License details
5.1.2 PM and CM data

The RMO module uses the Performance Management (PM) counters as input and modifies the Con-
figuration Management (CM) parameters. For more information, see the following documents:
• EdenNet module specific Data for Nokia

• EdenNet module specific Data for Ericsson
• EdenNet module specific Data for Huawei
5.2 Configuring and executing RMO module

This section describes how to configure and execute the RMO module.

Prerequisites
• All the prerequisites mentioned in the Prerequisites section must be met.
1. Log in to the EdenNet application by doing the following:

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

b) In the Username field, type the username.
c) In the Password field, type the password.
d) Click Log In.
The EdenNet application opens displaying the SON Activity page.
2. Click the Configure tab.
The following module categories appear in the left pane:
• EdenNet modules: Lists the modules provided by Nokia.

• Adapted modules: Lists the modules developed by users.
• Helper modules: Lists the modules used for troubleshooting by Nokia support teams.
3. Click EdenNet modules → Remedy_Modules_Orchestrator.
The Configure Targets page appears.
4. To select the LTE target cells for configuration, do one of the following:
• Based on the Topology Filter or Center Frequency Filter, select the target cells on the map.
Or
• Based on the Topology Filter or Center Frequency Filter, click the Select all Filtered Items
icon to select all the filtered items.
Or
• Based on the following options, select the existing clusters or create a new cluster:
• From selected cells

• Based on rules
For more information about creating a new cluster, see the Cell Clusters section in the
EdenNet User and Administration Guide.
Or
• Based on the cell ID search or selection tools from the map toolbar.

The target cells are selected on the map and are listed in the Selections pane.
Note: For more information about selecting cells, see the Selecting cells section in the
EdenNet User and Administration guide.
5. Click Next.
The Configure Parameters page appears.
6. In the Parameter Value column, define the values of the GUI configuration parameters. For the list
of GUI parameters, see RMO GUI parameters.
Note: Click the Default Value icon to revert to the default GUI parameter value.
7. Click Next.
The Select Configuration File page appears.
8. In the Module Global Configuration category, select the required configuration file.
Note: In each category, you can select only one configuration file.
9. Verify the configuration and click Next.
The Execution Type page appears.
10. To schedule the module execution, do one of the following:
• Activate Now : Select to execute or activate the module immediately.

• Activate Later : Select to execute or activate the module at a later time.
• Schedule Execution : Select to schedule the module for execution during a certain date and
time.
For more information, see the Configuring execution type section in theEdenNet User and Admin-
istration Guide.
11. Click Next.
The Confirm Execution page appears.
12. Verify the configuration summary and click Finish.
Expected outcome
The RMO module is configured and executed as per the defined schedule.

Note: You can monitor the RMO module activities, status, and so on. For more information,
see Monitor RMO module .

Remedy Module Orchestrator Guide DN1000032733 1-1 RMO configuration parameters
6 RMO configuration parameters

The configuration parameters required to execute the RMO module are as follows:
• RMO GUI parameters

• RMO INI parameters
6.1 RMO GUI parameters

Table 6: GUI parameters describes the RMO module GUI parameters.
Range (min, Default

Parameter name Description Step
max) value
Module Execution In- Indicates the time interval (in 12 or 24 hours N/A 24
terval hours) at which the RMO mod-
ule must be re-triggered.
ML Model Re-Training Indicates the time interval (in 1...4 weeks N/A 1
Interval weeks) at which the ML model
for RCA must be re-trained.
ML Model Training KPI Indicates the KPI duration in 3, 5, or 7 N/A 5

Duration days, required to train ML mod-
el for RCA classification.
KPI Thresholds Selec- Indicates the KPI thresholds to User Configured N/A User Con-
tion be used by ML model for RCA or System Com- figured
classification. System comput- puted
ed thresholds are derived from
the KPI data. User configured
thresholds are derived from the
module configuration file.
Recommendation When the module is executed • True N/A False

Mode in Open loop and Recommen- • False
dation Mode is set to True,
the RMO module generates
a recommendation report but
does not execute any remedy
modules.
SON_Operation_Mode Indicates that the parameter • Open Loop N/A Open Loop
must be set to Open loop to • Closed Loop
run the module in open loop

Range (min, Default

Parameter name Description Step
max) value
mode. In Open Loop mode,

the module will not automatical-
ly push parameter changes to
network. The user has to manu-
ally provision the plans to push
changes to the network.
It must be set to Closed loop

to run the module in closed
loop mode.
In closed loop mode, the

changes are automatically
pushed to the network with-
out user intervention. For more
information, see Operational
modes.
Plan Name Tag Text that will be added to the Sequence which N/A N/A
names of all the plans that will contains any
be generated by this module. combinations of:
If the target of the module is • Uppercase

a whole specific cluster (and and lower-
name of this cluster also match- case letters:
es requirements specified in [A-Z, a-z]
Range column), then the clus- • Numbers:
ter name is also added to the [0-9]
plan name. • Underscore:
_
Maximum length
is 20 characters.
Table 6: GUI parameters
6.2 RMO INI parameters

Table 7: INI parameters describes the RMO module INI parameters.

Range (min, Default val-

Parameter Description Step
max) ue
Debug_mode This parameter must be (True, False) N/A False

enabled to get debug
logs.
Degradation_ Indicates the KPI degra- N/A N/A 5

tolerance dation tolerance, when
combined with the indica-
tor type, we can measure
whether a cell has under-
gone degradation or not.
If its a good indicator then

reduction of KPI (used
for problem detection)
beyond degradation_tol-
erance is considered as
degradation.
If its a bad indicator then

increase of KPI (used for
problem detection) be-
yond degradation_toler-
ance is considered as
degradation.
Upper_limit_for_ Indicates how many more N/A N/A 3

remedy_ executions are allowed for
module_ cells which repeatedly oc-
executions cur as problematic cells
and show KPI degrada-
tion in the previous runs.
For iterative modules, this

parameter is used to elim-
inate cells from the scope
of the module instances
created by the RMO mod-
ule.
For non-iterative modules,

the scope or cluster of
cells do not contain those
cells, which have experi-
enced a KPI degradation

Range (min, Default val-

Parameter Description Step
max) ue
in the previous runs equal

to value of this parameter.
kpi_feature Indicates the name of N/A N/A N/A

the KPI. It must be under
the [problem_ definitions]
section.
remedy_modules Indicates the name of the N/A N/A N/A

remedy modules to be
triggered if a particular
problem is encountered. It
must be under the [prob-
lem_definitions] section.
Table 7: INI parameters
Note:
• The KPI thresholds are predefined in the rf_solution_type section for each
cell type (macro, micro, pico, and femto). The remedy modules are listed in the
[Remedy_Module_List] section of the RMO module INI file.
• To add configuration file for a remedy module, do the following:
[Remedy_Module_List]
[[<Remedy_module_1>]]
ConfigurationFile.Module Global Configuration=<Remedy_module_
1> INI file
ConfigurationFile.lms=<LMS configuration file>
For example,
[[ANR_4G_IRAT]]
ConfigurationFile.Module Global Configuration = EN19_ANR_4G_
IRAT_v1.ini
ConfigurationFile.lms = 2G_4G_lms_allpass.json
• If user does not configure the ConfigurationFile.Module Global Configura-

tion setting, the default INI configuration file will be picked for a remedy module.
• To add GUI parameters for a remedy module, do the following:
[[<Remedy_module_1>]]
ConfigurationFile.Module Global Configuration=<Remedy_module_
1> INI file
GUI_param_name1 = value
GUI_param_name2 = value

For example,
[[ANR_4G_IRAT]]
Extended_Scope_For_New_Cell = True
Optimize 4G to 3G neighbor relations = No
LTE_IRAT_Outperform_Multiplier = 1.50
For more information, see Example of RMO INI file.
6.2.1 Example of RMO INI file

The following is an example of the RMO module INI file:
[global]
debug_mode=False
Degradation_tolerance = 5%
Upper_limit_for_remedy_module_executions = 3
[problem_definitions]
[[Poor VoLTE-SRVCC handover]]
kpi_feature=LTE_WCDMA_VoLTE_Handover_Success_Ratio
remedy_modules=VoLTE_SRVCC_Optimization
[[Weak LTE-WCDMA VoLTE-SRVCC Mobility Parameters]]
kpi_feature=LTE_WCDMA_Problematic_VoLTE_Handover_Ratio
[[Poor Intra-LTE Handover]]
kpi_feature=LTE_Handover_Success_Ratio
remedy_modules=PCIReuse,ANR_Blacklisting_and_Cleanup_LTE,PRACH_
Optimization_LTE
[[Weak LTE Mobility Parameters]]
kpi_feature=LTE_Problematic_Handover_Ratio
remedy_modules=MRO_Intra_InterFreq_LTE
[[Poor LTE-WCDMA PSHO]]
kpi_feature=LTE_WCDMA_PSHO_Success_Ratio
remedy_modules=Inter-RAT_MRO
[[Weak LTE-WCDMA PSHO Mobility Parameters]]
kpi_feature=LTE_WCDMA_Problematic_PSHO_Ratio
remedy_modules=Inter-RAT_MRO
[[Poor LTE IRAT Handover]]
kpi_feature=LTE_IRAT_Handover_Success_Ratio
remedy_modules=ANR_4G_IRAT
[[High VoLTE Drop Rate]]
kpi_feature=VoLTE Drop Rate Market (GCR)
[[Poor Downlink Throughput]]
kpi_feature=LTE_DL_User_Throughput
remedy_modules=PCIReuse
[[Poor Uplink Throughput]]
kpi_feature=LTE_UL_User_Throughput
[[High Service Drop Rate]]

kpi_feature=E_UTRAN_E_RAB_Drop_Ratio
[[Poor E2E Call Setup Success Rate]]
kpi_feature=LTE_E_RAB_Accessibility
[[Poor RRC Setup Complete Rate]]
kpi_feature=LTE_RRC_Setup_Success_Rate
remedy_modules=SleepingCellResolution
[[Poor RACH Setup Success Rate]]
kpi_feature=LTE_RACH_Setup_Completes_Rate
remedy_modules=PRACH_Optimization_LTE
[[Poor Cell Availability]]
kpi_feature=LTE_Cell_Availability
remedy_modules=CellOutageCompensation
[rf_solution_type]
[[macro]]
LTE_WCDMA_VoLTE_handover_Success_Ratio_Threshold=95
LTE_WCDMA_Problematic_VoLTE_Handover_Ratio_Threshold=5
LTE_Handover_Success_Ratio_Threshold=95
LTE_Problematic_Handover_Ratio_Threshold=5
LTE_WCDMA_PSHO_Success_Ratio_Threshold=95
LTE_WCDMA_Problematic_PSHO_Ratio_Threshold=5
LTE_IRAT_Handover_Success_Ratio_Threshold=95
VoLTE_Drop_Rate_Threshold=2
LTE_DL_User_Throughput_Threshold=3
LTE_UL_User_Throughput_Threshold=3
E_UTRAN_E_RAB_Drop_Ratio_Threshold=2
LTE_E_RAB_Accessibility_Threshold=97
LTE_RRC_Setup_Success_Rate_Threshold=98
LTE_RACH_Setup_Completes_Rate_Threshold=95
LTE_Cell_Availability_Threshold=99
[[micro]]
[[pico]]

[[femto]]
[[VoLTE_SRVCC_Optimization]]
ConfigurationFile.Module Global Configuration=VoLTE_SRVCC_Optimization_1.
ini
[[ANR_Blacklisting_and_Cleanup_LTE]]
[[MRO_Intra_InterFreq_LTE]]
[[Inter-RAT_MRO]]
[[ANR_4G_IRAT]]
Optimize 4G to 3G neighbor relations = No
LTE_IRAT_Outperform_Multiplier = 1.50
ConfigurationFile.Module Global Configuration = EN19_ANR_4G_IRAT_v1.ini
ConfigurationFile.lms = 2G_4G_lms_allpass.json
[[PCIReuse]]
[[PRACH_Optimization_LTE]]
[[CellOutageCompensation]]
[[SleepingCellResolution]]

6.3 Importing INI parameters

In EdenNet, you can import and activate the configuration files. You can also edit, export, delete, activate, and deactivate the
configuration files.
Prerequisites
• Only users with Administrator privileges can modify the INI parameters.
• The INI file must be available. For the list of INI file parameters, see RMO INI parameters.

Cross-OSS:

d) Click Log In.
2. Click Administration → Modules.
The following module categories appear in the left pane:
• EdenNet modules: Lists the modules provided by Nokia.

• Adapted modules: Lists the modules developed by users.
• Helper modules: Lists the modules used for troubleshooting by Nokia support teams.
3. Click EdenNet modules → Remedy_Modules_Orchestrator.
4. Click Configure → Module Configuration.
The RMO Configuration Manager dialog box appears.
5. Click the Module Global Configuration category and do one of the following:
• Import And Activate: Click to import a file and activate it immediately.

• Import: Click to import a configuration file.
• Activate: Click to activate the selected file.
Note: Multiple configuration files can be activated.

Expected outcome
The RMO configuration file is imported and activated.
Note: In the RMO Configuration Manager dialog box, you can do one of the following:
• Export: Click to export the selected file to your system.

• Delete: Click to delete the selected file from the list.
Note: Users with Administrator or SON Module Manager permission can

delete the configuration files. The configuration files are deleted if they are not
used by other modules.
• Deactivate - Click to deactivate an activated file.
Note: If a configuration file is not used by other modules listed in the Active
SON Modules or Module History area, you can deactivate the configuration
file.
• Set As Default - Click to set the selected file as the default configuration.
• Reset - Click to reset the edited parameter values in the selected INI file.
• Save - Click to save the new version of the configuration file after editing the parameter
values in the selected INI file.
• Save As - Click to save the configuration file with a different name.
For more information, see the Configuring a module section in the EdenNet User and Admin-
istration Guide.

Remedy Module Orchestrator Guide DN1000032733 1-1 Viewing RMO reports
7 Viewing RMO reports

For every module instance, the RMO module generates reports as an Excel/CSV file. You can view the reports and take
appropriate actions, if required.

Cross-OSS:

d) Click Log In.
2. Click the Status tab.
The Status page appears.
3. In the Active SON Modules or Module History area, select the Remedy_Modules_Orchestrator
module.
The Remedy_Modules_Orchestrator module status appears in the Execution Status tab.
4. Click the Logs tab.
5. In the User Outputs option, click the username. For example, admin.
The Directory Listing For dialog box appears listing the module filename.
6. Click the Remedy_Modules_Orchestrator filename.
A list of Excel/CSV files appears.
7. Click the required Excel/CSV files.
Expected outcome
The Excel/CSV files are saved to your local system. You can open and view the report.
7.1 RMO reports

The RMO module generates the following reports in an Excel/CSV file.

Table 8: RMO module reports describes each report generated after executing the RMO module.
Report name Description
Parameters This report lists the GUI parameters and the parameters in the global
section of the INI file.
Problem Configuration This report lists problem thresholds per cell type and the mapping of
problems to the remedy modules.
Cell Problem Inferences This report shows the problems inferred against the cells.
Recommendation Summary This report shows the list of cells and the remedy to be executed on
it.
Recommendation Details This report lists the remedy modules suggested for each cell.
KPI Changes This report shows the daily aggregated KPI value per cell for the pre-
vious and current iterations.
Cells Excluded This report lists the cells that has crossed the Upper_limit_for_
remedy_module_executions value.
Logs This report lists the time, log type, and log message for different runs
of the RMO module.
Table 8: RMO module reports
7.1.1 Parameters
Parameters describes the columns present in the Parameters sheet.
Column name Description
Parameter Indicates the name of the parameter.
Value Indicates the value of the parameter.
Table 9: Parameters
7.1.2 Problem Configuration

Problem Configuration describes the columns present in the Problem Configuration sheet.
KPI Indicates the KPI name.
Threshold for Macro Indicates the threshold value for macro cells.
Threshold for Micro Indicates the threshold value for micro cells.
Threshold for Pico Indicates the threshold value for pico cells.

Threshold for Femto Indicates the threshold value for femto cells.
<Remedy Module X> Indicates the remedy module.
<Module Configuration for Module Indicates the module configuration for the remedy module.
X>
Table 10: Problem Configuration
7.1.3 Cell Problem Inferences

Table 11: Cell Problem Inferences describes the columns present in the Cell Problem Inferences
sheet.
Cell DN Indicates the Distinguished Name (DN) of the problematic cell.
Managing OSS Indicates the name of the managing OSS.
Vendor Indicates the supported vendor.
Cell CGI Indicates the name of the cell CGI.
<problem name> Indicates the problem name. For each problem, there is one dedicated
column. The cells affected by that problem are marked as Yes and oth-
ers are marked as No.
Table 11: Cell Problem Inferences
7.1.4 Problem Configuration

Problem Configuration describes the columns present in the Problem Configuration sheet.
KPI Indicates the KPI name.
Threshold for Macro Indicates the threshold value for macro cells.
Threshold for Micro Indicates the threshold value for micro cells.
Threshold for Pico Indicates the threshold value for pico cells.
Threshold for Femto Indicates the threshold value for femto cells.
<Remedy Module X> Indicates the remedy module.
<Module Configuration for Module Indicates the module configuration for the remedy module.
X>

Table 12: Problem Configuration
7.1.5 Recommendation Summary

Table 13: Recommendation Summary describes the columns present in the Recommendation Sum-
mary sheet.
Remedy module Indicates the name of the best remedy module to be execut-
ed to solve the problem in the cell.
Impacted cells Indicates the number of cells on which the remedy module is
executed.
Table 13: Recommendation Summary
7.1.6 Recommendation Details

Table 14: Recommendation Details describes the columns present in the Recommendation Details
sheet.
Cell DN Indicates the Distinguished Name (DN) of the problematic cell.
Recommendation Indicates the name of the recommended modules.

modules
Table 14: Recommendation Details
7.1.7 KPI Changes

KPI Changes describes the columns present in the KPI Changes sheet.
Cell DN Indicates the Distinguished Name (DN) of the problematic

cell.

<KPI name>(before execution) Indicates the KPI value considered in the previous module
execution.
<KPI name>(after execution) Indicates the KPI value considered in the current module
execution.
<KPI name>(Percentage change) The percentage of change in the KPI values.
Table 15: KPI Changes
7.1.8 Cells Excluded

Table 16: Cells Excluded describes the columns present in the Cells Excluded sheet.
Cell DN Indicates the Distinguished Name (DN) of the problematic

cell.
Table 16: Cells Excluded
7.1.9 Logs
Logs describes the columns present in the Logs report.
Time Indicates the timestamp.
Type Indicates the type of log message (for example, error, warn-
ing).
Message Indicates the description of the logged event.
Table 17: Logs

Remedy Module Orchestrator Guide DN1000032733 1-1 Monitor RMO module
8 Monitor RMO module

You can monitor:
• SON activities: The SON Activity page enables you to view and monitor SON activities. For more
information, see the View and monitor SON activities section in the EdenNet User and Administra-
tion Guide.
• Status: The Status page enables you to view the status of SON modules. For more information,
see the View status of SON modules section in the EdenNet User and Administration Guide.
RMO module impact on the network
For each vendor, the managed objects created, deleted, or modified in a network are listed in the Ac-
tions column of the CM objects or parameters section. For more information see the following docu-
ments:
• EdenNet Module Specific Data for Nokia

• EdenNet Module Specific Data for Ericsson
• EdenNet Module Specific Data for Huawei

Eden Net Remedy Module Orchestrator Guide

Uploaded by

Document Information

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 Remedy Module Orchestrator Guide

Uploaded by

Copyright:

Available Formats

EdenNet 21 FP 2106

Remedy Module Orchestrator 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 RMO module.............................................................................................................................. 5

3 RMO functional description and guidelines................................................................................................. 7

6 RMO configuration parameters....................................................................................................................15

7 Viewing RMO reports.................................................................................................................................... 24

8 Monitor RMO module.................................................................................................................................... 29

EdenNet 21 FP 2106 © 2021 Nokia 3

Release Change description

EdenNet 21 FP 2106 No change.

EdenNet 21 FP 2105 No change.

EdenNet 21 FP 2104 No change.

EdenNet 21 FP 2103 Updated sections:

Table 1: Summary of changes

EdenNet 21 FP 2106 © 2021 Nokia 4

2 Overview of RMO module

The RMO module is executed in the following phases:

2.1 Supported vendor and technology

Table 2: Supported vendor and technology

2.2 RMO dependencies, interactions, and limitations

EdenNet 21 FP 2106 © 2021 Nokia 5

EdenNet 21 FP 2106 © 2021 Nokia 6

3 RMO functional description and guidelines

Optimization algorithms are selected from the INI file.

RMO supports the following types of execution:

For the list of remedy modules, see Table 4: Problem remedies.

3.1 Operational modes

• Open loop mode

3.1.1 Open loop mode

3.1.2 Closed loop mode

EdenNet 21 FP 2106 © 2021 Nokia 7

The RMO module execution occurs in the following phases:

Table 3: Problem identification lists the rules used to identify a problem.

Problem Identification KPI KPI thresholds

Poor VoLTE-SRVCC handover LTE_WCDMA_VoLTE_Handover_Success_ < 95%

Weak LTE-WCDMA VoLTE- LTE_WCDMA_Problematic_VoLTE_Han- > 5%

Poor Intra-LTE Handover LTE_Handover_Success_Ratio < 95%

Weak LTE Mobility Parameters LTE_Problematic_Handover_Ratio > 5%

Poor LTE-WCDMA PSHO LTE_WCDMA_PSHO_Success_Ratio < 95%

Weak LTE-WCDMA PSHO Mobil- LTE_WCDMA_Problematic_PSHO_Ratio > 5%

Poor LTE IRAT Handover LTE_IRAT_Handover_Success_Ratio < 95%

EdenNet 21 FP 2106 © 2021 Nokia 8

Problem Identification KPI KPI thresholds

Poor Downlink Throughput LTE_DL_User_Throughput < 3gbps

Poor Uplink Throughput LTE_UL_User_Throughput < 3gbps

High Service Drop Rate E_UTRAN_E_RAB_Drop_Ratio > 2%

Poor E2E Call Setup Success LTE_E_RAB_Accessibility < 97%

Poor RRC Setup Complete Rate LTE_RRC_Setup_Success_Rate < 98%

Poor RACH Setup Success Rate LTE_RACH_Setup_Completes_Rate < 95%

Poor Cell Availability LTE_Cell_Availability < 99%

Table 3: Problem identification

Poor VoLTE-SRVCC handover VoLTE_SRVCC_Optimization MID

Weak LTE-WCDMA VoLTE- VoLTE_SRVCC_Optimization HIGH

Poor Intra-LTE Handover ANR_Blacklisting_and_Cleanup_LTE MID

Weak LTE Mobility Parameters MRO_Intra_InterFreq_LTE HIGH

Poor LTE-WCDMA PSHO Inter-RAT_MRO MID

Weak LTE-WCDMA PSHO Mobili- Inter-RAT_MRO HIGH

Poor LTE IRAT Handover ANR_4G_IRAT HIGH

High VoLTE Drop Rate VoLTE_SRVCC_Optimization HIGH

Poor Downlink Throughput PCIReuse HIGH

Poor Uplink Throughput PCIReuse HIGH