Eden Net Sleeping Cells Resolution Help
Eden Net Sleeping Cells Resolution Help
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.
Sleeping Cells Resolution Guide DN09237869 1-0 Table of Contents
Contents
1 Summary of changes...................................................................................................................................... 5
2 Overview of SCR............................................................................................................................................. 9
2.1 SCR dependencies and interactions........................................................................................................ 9
2.1.1 Dependencies................................................................................................................................... 9
2.1.2 Interactions........................................................................................................................................9
4 SCR algorithm................................................................................................................................................12
4.1 SCR logic................................................................................................................................................ 12
4.1.1 Configuration of SCR detection logic............................................................................................. 12
4.1.1.1 WCDMA default detection logic............................................................................................. 13
4.1.1.2 LTE default detection logic.....................................................................................................14
4.1.2 SCR resolution logic....................................................................................................................... 14
4.1.2.1 Nokia (cell reset).................................................................................................................... 14
4.1.2.2 Nokia (site reset).................................................................................................................... 15
4.1.2.3 Ericsson (cell reset)................................................................................................................16
4.1.2.4 Ericsson (site reset)............................................................................................................... 16
4.1.2.5 Technology specific site reset................................................................................................ 17
4.2 Cross OSS.............................................................................................................................................. 17
4.2.1 Cross OSS support for sleeping cell detection and resolution (with NAdC)...................................17
4.2.2 Cross OSS support for sleeping cell detection and resolution (without NAdC).............................. 18
9 Monitoring SCR..............................................................................................................................................42
1 Summary of changes
EdenNet 21 No change.
– Reset_interval_mode
– Number_of_hours_between_resets
– Technology_Specific_Site_Reset_even_if_
GSM_is_present
• Example of SCR configuration file
• Reset request MO cleanup report table is added to the
Sleeping cells detection reports section.
Added sections:
• Cross OSS
• Cross OSS support for sleeping cell detection and resolution
(with NAdC)
• Cross OSS support for sleeping cell detection and resolution
(without NAdC)
Updated sections:
• The Time_to_wait_for_MO_feedback_in_seconds
parameter is added to the SCR INI parameters section.
• A note is added to the Details report table in the Sleeping
cells detection reports section.
• Example of SCR configuration file
EdenNet 19 FP 1904 All instances of Custom modules are changed to Adapted mod-
ules in the following sections:
• Accessing SCR
• Configuring INI parameters
EdenNet 18 SP1 1812 The description of the Reset Count Threshold parameter is
modified.
Added content:
EdenNet 18 No changes.
EdenNet 17 SP1 FP1 SCR algorithm section is updated with the description of para-
meters.
SON reporting
Updated sections:
Added new GUI parameter Plan Name Tag in the SCR GUI pa-
rameters section.
Updated sections:
Updated sections:
2 Overview of SCR
Sleeping cells are radio cells which do not accept new connections from mobile devices and do not
carry traffic, due to software defects. Until a software update is applied to address the software de-
fects, the temporary remedy is to reset the sleeping cells. The EdenNet Sleeping Cells Resolution
(SCR) module identifies the sleeping cells in a cellular network and performs cell reset automatically.
Table 2: SCR supported vendors and technologies lists the supported vendors and technologies for
the SCR module.
Vendor Technology
• Dependencies
• Interactions
2.1.1 Dependencies
• The SCR module requires the configuration of the reset cell or site, and toggling of the cell lock.
• The SCR module requires a 15 minute measurement period for the KPIs.
2.1.2 Interactions
The SCR module can impact the traffic at the BTS and influence the KPIs of the other modules, if any
KPIs are executed during the same time frame.
The SCR module supports LTE and UMTS technologies. Regardless of the cell type (macro cells or
small cells), the SCR module can detect the sleeping cells in the network. Once a cell is detected
as sleeping, the SCR module sends an e-mail notification to the RF engineers to automatically reset
the sleeping cell and resolve the issue. If the cell does not recover even after reset, the SCR module
sends an e-mail notification to the RF engineer to investigate the issue.
The SCR module supports a maintenance window during which no cells are reset. Also, it can distin-
guish off-air cells from sleeping cells so that no locked cells, reserved cells, or barred cells are reset.
The SCR module does not repeatedly reset chronic sleeping cells. For example, a cell should not be
reset more than once in a week, even if it is sleeping after several resets.
The SCR module checks if the MORAN feature (RAN sharing) is enabled for cells at a site. If RAN
sharing is enabled, the SCR module skips the site reset for those cells.
In the open loop mode, the SCR module performs the following tasks:
• Monitors the selected cells and evaluates them against the sleeping cell conditions
• Generates a report containing the details of the sleeping cells and sends e-mail notifications
• Executes in a continuous loop every 15 minutes
In the closed loop mode, the SCR module performs the following tasks:
Note: The SCR module does not propose site-reset if unsupported vendors (like Huawei,
ZTE and fALU) are part of the same site. In addition, the SCR module logs the names of the
unsupported vendors.
Table 3: Cell reset and site reset for various vendors describes the cell reset and site reset scenarios
for various vendors.
Ericsson For 3G and 4G cells, it generates two For 3G and 4G cells, it triggers a command
plans to change the administra- to the NE using AMOS.
tiveState parameter for each cell
that was detected as sleeping.
4 SCR algorithm
The main goal of the SCR algorithm is to identify sleeping cells by correlating different KPIs or compar-
ing KPIs with historical statistics.
For every KPI event, the SCR module selects the target cells and obtains the KPI definitions and time
window. If the cells are not in the maintenance window (Maintenance_Window Start_Time and
Maintenance_Window End_Time), it retrieves the KPI data for all the selected cells. Then the SCR
module runs the detection logic (3G Detection Criteria, LTE Detection Criteria, and
Enable Additional Criteria) on the selected cells based on the selected algorithm. If any
potential sleeping cells are found (Number of consecutive detections), it filters out the cells
that are locked or disabled. If no sleeping cells are left after filtering locked and disabled cells, further
execution (resolution logic) of the SCR module stops. If other sleeping cells remain after eliminating
the locked cells, the SCR module runs the resolution logic on them if they meet the following criteria:
Once the reset is performed, the SCR module clears the sleeping condition flag from all the non-
sleeping cells, sets the Number of consecutive detections to 0 for all the non-sleeping cells,
and removes them from the reset and alert lists. If a cell does not recover after reset, the SCR module
sends e-mail notifications to the e-mail addresses stored in the Alert recipients parameter.
You can override the default sleeping cell detection logic of the SCR module by importing module con-
figuration files that contain detection logic. When the SCR module detects custom detection logic, it
uses the custom detection logic instead of the default logic. For more information on the sleeping cell
detection logic, see WCDMA default detection logic and LTE default detection logic. You can import
only one detection logic for each of the supported technologies.
Each element of the detection logic requires one of the following comparators:
The KPIs with the arithmetic operators (+, -, *, /) between them have to be on the left side. The number
has to be on the right side of the comparator:
The AND operator allows combining of the detection logic that must be fulfilled before a cell is
considered to be sleeping. The semicolon ( ; ) serves the purpose of an OR operator, allowing the
combining of detection logic so that when any one detection logic is fulfilled, the cell is considered
to be sleeping. The AND operator takes precedence over the semicolon. The example above can be
interpreted as:
Note:
– curly braces { }
– colon :
– equals =
• Each KPI name in the condition needs to be enclosed within curly braces.
Data:
Additional Criteria:
• {VOICE_RRC_CONN_REQ} = 0
• {VOICE_RRC_CONN_REQ_AVG} >=13
• {VOICE_TRAFFIC_AVG} > 0
OR
• {PS_RRC_CONN_REQ} = 0
• {PS_RRC_CONN_REQ_AVG} >= 20
• {HSDPA_TRAFFIC_VOL_MB_AVG} > 0
LTE detection logic is built on several conditions. A cell is considered to be sleeping when any of the
following conditions is evaluated to be true for a number of consecutive ROPs (Report Output Periods)
of 15 minute intervals. The number of consecutive ROPs is configurable as a user input parameter to
the module.
Note: This is default detection logic which can be overwritten by importing custom detection
logic through Module Configuration.
This section describes the cell reset and site reset scenarios for the following vendors:
This section describes the cell reset process for Single Radio Access Network (SRAN) and non SRAN
cells.
For 4G cells, the SCR module generates a plan to change the cellResetRequest (LNCEL)
parameter with the value of the current timestamp for each cell that was detected as sleeping.
The plan is downloaded with the current timestamp to indicate the reset request. A new request re-
ceives a new timestamp and therefore causes a parameter change. The cell reset is executed auto-
matically because the parameter change requires cell lock or unlock.
For 3G cells, the SCR module triggers a command to the NE. The resetCell.sh tool is used for the
cell reset:
where:
SRAN cells
For SRAN 4G cells, the SCR module generates a plan to change the cellResetRequest (LNCEL)
parameter with the value of the current timestamp for each cell that was detected as sleeping.
The plan is downloaded with the current timestamp to indicate the reset request. A new request re-
ceives a new timestamp and therefore causes a parameter change. Cell reset is executed automati-
cally since parameter change requires cell lock or unlock.
For SRAN 3G cells, the SCR module toggles the AdminCellState parameter by generating two
plans for each cell that was detected as sleeping:
• The first plan changes the value of the AdminCellState parameter to LOCKED.
• The second plan changes the value of the AdminCellState parameter to UNLOCKED.
This section describes the site reset process for SRAN and non SRAN sites.
For 4G cells, the SCR module generates a plan to change the btsResetRequest (LNBTS)
parameter with the value of the current timestamp. Whenever a plan that modifies or sets this
parameter is downloaded, the BTS resets automatically.
For 3G cells, the SCR module triggers a command to the NE. The reset.sh tool is used for site
reset:
where:
SRAN sites
For 4G cells, it generates a plan to change the btsResetRequest with the value of the current
timestamp. Whenever a plan modifying or setting this parameter is downloaded, the BTS resets
automatically.
For SRAN 3G cells, the reset is done by creating a SWRESETERQ managed object with the
swResetLevel option set as wcdmaReset. After the SWRESETREQ is created, the respective BTS
is reset and SWRESETRES is created automatically:
• If the reset request fails, (the BTS does not reset), the object is created immediately with the
SWRESETRES::status attribute set to failure.
• If the reset request succeeds (BTS resets), the object is created after BTS reset under the request
object that triggered the reset. In this case, the SWRESETRES::status attribute is set to success.
Note:
• SWRESETERQ belongs to the CMD managed object. If the CMD managed object does
not exist, a separate plan is generated to create it. The SWRESETREQ managed object
plan is implemented only after the CMD managed object is created.
• If the CMD managed object creation fails, the SCR module considers the corresponding
3G site reset as a failure.
• For non SRAN WCDMA cells, the SCR module uses a script, and feedback logs are not
provided in the Provisioning logs tab.
• For plan based resolution, provisioning logs are available in the Provisioning logs tab.
SWRESETERQ cleanup
A maximum of 255 SWRESETREQs can be created under an MRBTS. The SCR module
cleans up the created SWRESETREQs during the instance maintenance window. The SCR
module generates a plan with SWRESETREQ deletion and the same is provisioned during
the instance maintenance window.
Note: The SCR module does not detect and reset the sleeping cells during the in-
stance maintenance window.
If the module iteration is stopped manually, the SCR module deletes the SWRESETREQ
managed objects.
For WCDMA and LTE cells, the SCR module toggles the administrativeState parameter by
generating two plans for each cell that was detected as sleeping:
• The first plan changes the value of the administrativeState parameter to LOCKED.
• The second plan changes the value of the administrativeState parameter to UNLOCKED.
For WCDMA and LTE cells, site reset is done by entering the following AMOS command:
Site reset is done if the cells are sleeping even after a reset in the previous iteration. During the site re-
set, the SCR module checks the following:
The SCR module does not trigger a site reset if any of the above mentioned checks fails.
The technology specific reset allows the site reset to happen even if the other technology cells are not
sleeping or if GSM cells are present in the site.
The technology specific reset is not enabled by default. To enable it, set the
Technology_Specific_Site_Reset_even_if_GSM_is_present parameter to True.
The SCR module triggers the technology specific site reset, if all the cells belonging to that technology
are detected as sleeping (even if GSM cells are present in the same site).
Note: In case of updates, Nokia recommends that you run the SCR module again for the
Nokia vendor if the technology specific reset needs to be enabled for the scheduled in-
stances.
4.2.1 Cross OSS support for sleeping cell detection and resolution (with NAdC)
• Select LTE or WCDMA cells that stretch over the OSS boundary.
• Send the generated plan with cell reset (plan based) to NAdC. NAdC splits the plan per OSS and
sends them to the respective OSS for provisioning.
• The command based reset (scripts in the case of Nokia and AMOS commands in the case of
Ericsson) is triggered directly (not via NAdC).
4.2.2 Cross OSS support for sleeping cell detection and resolution (without NAdC)
The SCR module supports cross OSS functionality only with NAdC integration.
Note: In the case of cross OSS functionality without NAdC integration, the SCR module de-
tects and resets the sleeping cells if the cells belong to a single region.
To configure and execute the SCR module for WCDMA and LTE cells, do the following procedures in a
sequential order:
1. Accessing SCR.
2. Configuring targets for SCR.
3. Configuring parameters for SCR.
4. Selecting the configuration file for SCR.
5. Selecting execution type for SCR.
6. Confirming execution for SCR.
• The SCR license must be installed. For more information, see License details.
• The CM data and PM data must be available.
• The Average KPIs must be available.
• Default conditions for the module require 15 minute measurements.
• Google Chrome or Mozilla Firefox must be installed in your system.
Table 4: Sleeping Cell Resolution license table lists the licenses required to access the SCR module in
EdenNet.
For information on the PM counters and CM parameters of the Sleeping Cells Resolution module, see
the following documents:
Table 5: Methods of aggregating data lists the special data aggregation methods of the SCR module.
Average_of_ _AVG Average of hourly data from the same hour from the last
previous_14_ 14 days
days
Average_of_ _4wsdhAVG Average of hourly data from the same hour and the same
previous_4_ day of the week from the previous four weeks
weeks
The function loads the last 14 days of data (14*24=336 samples of hourly data) and evaluates the av-
erage for every hour. Since the result is hourly data, it should be divided into four to obtain the quarter-
ly equivalent. The quarterly data can be evaluated against all the other operators and conditions.
KPI value 50 43 46 61 55 56 60 59 58 52 52 55 56 51
Average 53,85
This function loads the data of the last four weeks for the same week day and evaluates the average
for every hour (four samples in total). Since the result is hourly data, it should be divided into four to
obtain the quarterly equivalent. The quarterly data can be evaluated against all the other operators
and conditions.
Day Four weeks ago Three weeks Two weeks ago Last week
ago
KPI value 52 55 56 51
Average 53,5
Note: For the rate KPIs (KPIs which are the result of the division of a counter by some other
counter), modify the formula by applying *4 to the KPI name.
For the grammar rules of detection logic using the EBNF (Extended Backus-Naur Form) notation, see
Appendix B: EBNF notation of detection logic.
Prerequisites
• All the prerequisites mentioned in the SCR prerequisites section must be met.
where <EdenNet GUI_SERVERS IP> is the IP address of the GUI server provided during the
installation of EdenNet.
• 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
Prerequisites
For more information about selecting cells, see the Selecting cells section in the EdenNet User and
Administration Guide.
2. Click Next.
Expected outcome
Prerequisites
1. Define the configuration parameters values. For the list of parameters, see SCR GUI parameters
values.
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.
Prerequisites
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. Verify the configuration in the right pane, and then click Next.
Expected outcome
The configuration file is selected and the Execution Type page appears.
Prerequisites
Note: For more information about the scheduling an execution, see the Configuring
execution type section in the EdenNet User and Administration Guide.
2. Click Next.
Prerequisites
Procedure
You can monitor the operation. For more information, see Monitoring SCR.
Expected outcome
The SCR module is executed based on the configuration parameters and as per the defined
schedule.
Expected outcome
The SCR module execution is confirmed and execution begins as per the defined schedule.
Default
Parameter Description Range Step
value
Alert recipients Comma separated e-mail addresses of the Any valid e- N/A N/A
(Optional) RF engineers who should do further investi- mail address-
gation of why the cells remain sleeping after es separated
they have been reset. by a comma
Default
Parameter Description Range Step
value
• VOICE_RRC_CONN_REQ = 0
• VOICE_RRC_CONN_REQ_AVG >=13
• VOICE_TRAFFIC_AVG > 0
OR
• PS_RRC_CONN_REQ = 0
• PS_RRC_CONN_REQ_AVG >= 20
• HSDPA_TRAFFIC_VOL_MB_AVG > 0
UMTS Condi- It is the optional configuration file contain- Any valid file N/A N/A
tion file (Option- ing a custom sleeping cell detection logic for location
al) UMTS technology.
LTE Condition It is the optional configuration file contain- Any valid file N/A N/A
file (Optional) ing a custom sleeping cell detection logic for location
LTE technology.
SON Operation Indicates the mode of operation for the SON Open Loop/ N/A Open Loop
Mode module. Valid values are: Closed Loop
Default
Parameter Description Range Step
value
Plan Name Tag It is a prefix for all the plans generated by an Sequence N/A Empty
user. which con-
tains any
Text that is added to the names of all the
combinations
plans that are generated by the SCR mod-
of:
ule. If the target of the module is a whole
specific cluster (and name of this clus- • Upper-
ter matches requirements specified in the case and
Range column), then the cluster name will lowercase
also be added to the plan name. letters: [A
to Z, a to
z]
• Numbers:
[0 to 9]
• Under-
score: _
Maximum
length: 20
characters
Email subject Indicates the custom subject for the notifica- N/A N/A N/A
(Optional) tion e-mails generated by the SCR module.
If you do not provide a custom e-mail sub-
ject, the SCR module uses the default e-mail
subject.
<module_instance_name> + <module_
start_time>
Note: module_start_time is
mentioned in UTC time format.
Example:
Default
Parameter Description Range Step
value
Example:
Custom_email_subject = "PS_
RRC_CONN_REQ < 125.00 AND DL_
R99_DATA_TRAFFIC_MB = 0.00 AND
HSDPA_TRAFFIC_VOL_MB = 0.00 AND
PS_RRC_CONN_REQ >= 3.00;"
SleepingCellResolution_Test_
admin_20180622_093109_757
2018-06-27 16:00:12
Note: For further information on how parameters can impact the network, contact Nokia
Technical Support.
Default
Parameter Description Range Step
value
Ignore_Reserved_ Allows to reset cells by disabling the True, False N/A False
Cells protection mechanism. This parameter
is used for pilot or trial cells, for testing
purpose only.
Reset_even_if_ If the parameter is set to True, cells will True, False N/A False
threshold_ex- be reset depending on the reset count
ceeds threshold in the UI. In addition, an e-
mail is sent alerting the user that the re-
maining cells which exceed the thresh-
old count will not be reset.
Time_to_wait_for_ Time interval in seconds for which the Any positive N/A 300
MO_feedback_in_ SCR module waits after provisioning integer
seconds and before fetching the MO level feed-
back.
Note:
Default
Parameter Description Range Step
value
For example:
– In case of Ericsson
cell reset, the SCR
module pushes two
plans, so it adds
two wait times to the
module execution
time.
– In case of Nokia LTE
cell reset, the SCR
module pushes on-
ly one plan so it adds
only one wait time to
the module execution
time.
Reset_interval_ Indicates the mode for the reset interval. Daily, N/A Daily
mode Hourly
If this parameter is set to Daily, the
Number_of_days_between_resets
parameter is used and the interval is in
days.
Default
Parameter Description Range Step
value
[Global]
Number_of_days_between_resets = 7
Alert_Frequency_Hours = 1
Reset_even_if_threshold_exceeds = False
Ignore_Reserved_Cells = False
Time_to_wait_for_MO_feedback_in_seconds = 300
Number_of_hours_between_resets = 168
Reset_interval_mode = Daily
Technology_Specific_Site_Reset_even_if_GSM_is_present = False
Prerequisites
• Admin privilege is available. Only admin users can 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.
Note: Users with Administrator or SON Module Manager permissions can delete
the configuration files. The configuration files can be deleted, only if it is not used by
any other modules.
Note: A file can be deactivated only when it is not used by other modules listed
under the Active SON Modules or the Module History.
Note: For more information, see the Configuring a module section of the EdenNet User
and Administration Guide.
Expected outcome
To view logs for Sleeping Cell Resolution for WCDMA and LTE cells, do the following:
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 Sleeping Cells Resolution 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. 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 list of file with module name appears.
A set of related Excel files are listed in the Directory Listing For dialog box.
Expected outcome
The SCR module is accessed and it generates the SCR report in XLSX format. For information on
the contents of the report, see Sleeping cells detection reports.
The report is in Microsoft Excel format with the summary table in one worksheet and the detailed table
in another excel.
The SCR module also delivers run-time events so that module actions can be correlated with oth-
er module's actions and SON changes can be correlated with advanced outputs like maps and KPI
charts.
Table 11: SCR module report describes the reports generated by the SCR module.
Sheet Description
Parameters Lists the module parameters used in each iteration of the SCR module
For example, name of the instance, region name, number of cells inspected,
cells detected sleeping, rested, number of alters sent, and count of chronic
sleeping cells
Details Displays all cells detected as sleeping with one entry per cell regarding the ac-
tion taken for that cell
Reset request MO Lists all the swResetReq managed objects which are marked for deletion or
cleanup cleanup.
Table 12: Parameters sheet lists the module parameters used in each iteration of the SCR module.
Value Indicates the value of the configuration parameter used for executing the mod-
ule
Table 13: Summary report presents a summary of each execution of the SCR module.
Parameter The parameter names like instance name, region name, number of cells in-
spected, number of cells detected sleeping, number of cells reset, number of
alerts sent, and number of cells still sleeping after reset
Value Displays the values for the parameter for that iteration of the SCR module
Table 14: Details report lists all the sleeping cells and the actions taken to resolve the issue.
Condition The condition and the values that are obtained during execution.
Condition thresh- The logic that is responsible for the detection of sleeping cells.
olds
Resolution The action taken for that cell like reset, alert, and no action.
Time of action The time at which resolutions are applied to the sleeping cell. The Time of ac-
(UTC) tion is specified in UTC time format.
Action result Results about the resolution action like successful, failed, and N/A.
Note: When the MORAN feature (RAN sharing) is enabled for cells
at a site, the reason displayed is Site Reset is skipped due to RAN
sharing.
Table 15: Reset request MO cleanup report describes the Reset request MO cleanup report.
Prerequisites
All the prerequisites mentioned in the SCR prerequisites section must be met.
3. In the left pane, click Modulesselect SleepingCellResolution, and then click Apply.
Expected outcome
The SCR module is accessed and the SON changes made for SleepingCellResolution are displayed
in a tabular format.
3. From the Module/Service filter, select the required SCR instance to view the event logs.
You can use one of the following filters to view the event logs:
Note: The common event levels are information and warning. The warning and error
level filters are selected by default. To view all levels of events, remove the warning and
error level filters.
5. Optional: Under the 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 Filter.
Expected outcome
The SCR module is accessed and the event log of the SCR module appears.
Category: SleepingCellResolution
Sleeping Cell Detected warning The event is generated in case sleeping cell is detect-
ed by the SCR module.
Resetting cells warning The event is generated when the SCR module resets
cells.
Target was reset The event is generated after the SCR module finishes
resetting the cell.
Cell is still sleeping after critical The event is generated in case reset did not improve
reset KPIs and cell is still considered as sleeping.
Resetting sites warning The event is generated when the SCR module resets
sites. It happens in case all cells served by the site are
sleeping and are already reset.
Target was reset The event is generated after the SCR module finishes
resetting the site.
Failed EMS Push The event is generated in case push with reset is un-
successful.
9 Monitoring SCR
• activities
• status
• events
For more information, see the Configure and monitor SON modules section of the EdenNet User and
Administration Guide document.
For each vendor, the list of RAN KPIs is listed in the RAN KPIs section of the following documents:
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:
<file_name>.ini or <file_name>.txt
For the grammar rules of detection logic using Extended Backus-Naur Form notation, see
Appendix B: EBNF notation of detection logic.
For example:
Expected outcome
A condition file with the specified conditions is created for either UMTS or LTE.
Extended Backus-Naur Form notation of detection logic is used while python references use modified
BNF notation. The grammar rules are:
For python float and python identifier grammar limitations required by the module, go to:
https://docs.python.org/3.7/reference/lexical_analysis.html#grammar-token-exponentfloat