Eden Net Usage Summary Guide
Eden Net Usage Summary 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.
EdenNet Usage Summary DN1000000119 1-0 Table of Contents
Contents
1 Summary of changes...................................................................................................................................... 4
1 Summary of changes
Release Changes
EdenNet 21 No change.
EdenNet 20 No change.
EdenNet 19 No change.
Release Changes
EdenNet 18 SP1 This is a new document for the EdenNet Usage Summary module, which
is an internal helper module from Nokia to report summary of EdenNet
product deployment and usage statistics for administrative purpose.
After EdenNet deployment, the administrator will strategize module execution that includes network
target scope, scheduling pattern, parallel instance runs and so on. Multiple rounds of tuning is used to
get the best results from EdenNet. The supporting information to accomplish these tasks is scattered
across applications, databases, and servers.
The EdenNet Usage Summary module is an internal helper module provided by Nokia to report sum-
mary of EdenNet product deployment and usage statistics for administrative purpose.
• Deployment summary: This report consists of deployment details such as EdenNet release, De-
ployment architecture (2VM/5VM/Cross-OSS), Frequency bands, Cell count per technology, and
so on.
• License management: This report consists of a list of licensed modules, license code, expiry
date, and so on.
• Scheduling information: This report lists all scheduled module names, period of schedule, fre-
quency of repetition, and so on.
• Frequency band details: This report contains a list of different frequency bands in the network
and corresponding cell count.
• Module usage statistics:
– Active modules: List of modules that are currently active and running.
– Open loop module run: History of modules run in Open Loop.
– Closed loop module run: History of modules run in Closed Loop.
• Module output can be configured to one or more e-mail IDs or as a group e-mail account for MIS
purpose.
These reports can be used by different stakeholders, NPO engineers, EdenNet Administrators,
and Service and Care teams.
Table 2: Use case descriptions describes a few examples of how this information can benefit different
stakeholders.
EdenNet administration Reports active modules, history, scheduled runs and so on.
Release maintenance Reports current release, upgrade planning, new modules and so
on.
Planning of schedule tasks Distributes, sequences, and schedules module execution optimal-
ly.
Compare across markets Summarizing information across systems with the acquired re-
ports becomes easier.
Management information Regular reports are sent via e-mail message without even logging
into the system.
Performance analysis Reports system load, parallel runs, scope of network, and so on.
Serviceability Provides first level information to care or support team for trou-
bleshooting purpose.
Table 3: Supported vendor and technology lists the supported vendors and technology for the EdenNet
Usage Summary module.
Vendors Technology
Ericsson
Huawei
Alcatel-Lucent
2.1 Dependencies
This EdenNet Usage Summary module executes well on a EdenNet system that is operational. How-
ever, in the present release, this module is mainly dependent on the Configuration Management (CM)
data. There is no dependency on Performance Management (PM) counter or KPI data.
The EdenNet Usage Summary module collects information from multiple sources and consolidates
output into two files in:
Optionally, additional information such as local operations team contact details, region (City or Country
of deployment), type of deployment (POC, Commercial or Production), and so on can be provided via
module configuration (INI) file. See Example of Usage Summary configuration file for a sample INI file
format.
Note: Depending on the use case, module permissions can be restricted to the users role
such as SON Module Manager or Administrator.
To configure and execute the EdenNet Usage Summary module, do the following procedures in a se-
quential order:
4.1 Prerequisites
To execute the EdenNet Usage Summary module, the following prerequisites must be met:
• Ensure that Google Chrome or Mozilla Firefox Web browser is installed on your system.
• You must have module permissions to execute the EdenNet Usage Summary module.
• At least one Operations Support System (OSS) must be integrated to EdenNet and Configuration
Management (CM) data retrieval must be successful.
Note: This module does not require a module specific license key.
Prerequisites
• 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.
Expected outcome
The EdenNetUsageSummary module is accessed and the Configure Targets page appears.
Prerequisites
• filter specific cells on a map based on the Topology Filter or Center Frequency Filter and
then select target cells from the map
Or
• filter specific cells on a map based on the Topology Filter or Center Frequency Filter and
then select all filtered items by clicking
Or
Or
Target cells are selected and they appear in the Selections pane. For more information about
selecting the 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.
Prerequisites
1. Define the configuration parameter values. For the list of parameters, see EdenNet Usage
Summary GUI parameters.
a) From the drop-down list, select the number of days of history data to be collected.
b) Enter the e-mail IDs separated with semi-colon where the output report need to be sent.
2. Click Next.
Expected outcome
The parameters are configured and the Select Configuration File page appears.
3. Continue with Selecting the configuration file for EdenNet Usage Summary.
Prerequisites
Note: You can skip the above optional step if the module configuration file is not import-
ed.
Note: If configuration files are not available, proceed to the next step.
Expected outcome
The configuration file is selected and the Execution Type page appears.
Prerequisites
• Successful completion of Selecting the configuration file for EdenNet Usage Summary
For more information about Activate Later and Schedule 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.
Prerequisites
Procedure
Note: You can monitor the operation. For more information, see Monitor Usage
Summary.
Expected outcome
EdenNet Usage Summary module is executed based on the configuration parameters and as per the
defined schedule.
Range (Min,
Parameter name Parameter description Step Default value
Max)
Range (Min,
Parameter name Parameter description Step Default value
Max)
SON Operation • Set to Open Loop to Open Loop N/A Open Loop
Mode run module in open loop
mode.
Note: Configuration file is optional and module will execute without configuration file also.
Parameter
Parameter description Range (Min, Max) Step Default value
name
Parameter
Parameter description Range (Min, Max) Step Default value
name
ations team or CT team for
the EdenNet deployment.
The INI file is created using configuration parameters. The following is a sample configuration file with
default values:
[Global]
#Country of this EdenNet deployment
country = INDIA
#Geographical region (APJ/NAM/LAT/EUR/INDIA/MEA/CHINA)
geo_region = INDIA
#Primary contact email ids
primary_contacts = <[email protected]>
#Deployment type (Production, POC, Trial, Pilot)
deployment_type = Production
#Deployment status (On going, completed)
deployment_status = On going
Prerequisites
Users with administration privileges are allowed to modify the INI parameters.
a) In the address field of your Internet browser, type the following URL (for 2VM, 5VM, and Cross-
OSS):
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.
Note: Users with Administrator or SON Module Manager permission can delete
the configuration files. The configuration files can be deleted only if it is not used by
other modules.
Note: A file can be deactivated only when it is not used by other modules listed in
Active SON Modules or Module History.
For more details, see the Configuring a module section in EdenNet User and Administration Guide.
For the INI file parameters, see EdenNet Usage Summary INI parameters.
Expected outcome
For every execution, each Usage Summary module generates a log and provides execution status
data in an Excel format.
The Active SON Modules and Module History appears in the left pane and Execution Status
appears in the right pane.
3. In the left pane, select a module either from Active SON Modules or Module History.
Note: The Active SON Modules area displays all the 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 such as recently
stopped, completed, or failed. To view the execution status of the module, see Viewing
the execution status section in the EdenNet User and Administration Guide.
The module generates an Excel spreadsheet. For information on the contents of the re-
port, see EdenNet Usage Summary reports .
The Directory Listing For dialog box appears displaying a list of files with module names.
A set of related Excel files are listed in the Directory Listing For dialog box.
Expected outcome
The reports are generated as an excel file. For information on the contents of the report, see
EdenNet Usage Summary reports .
Table 6: EdenNetUsageSummary Report provides an overview of the tabs available in the Usage
Summary output report.
Tab Description
Active SON Modules tab Provides details on the list of active SON modules running at
the time of report generation.
Module History OL tab Provides details on the list of SON modules run in Open
Loop mode for the period specified in GUI parameters.
Module Schedule tab Provides a list of all the scheduled tasks created for module
execution.
License_Info tab Provides details on all the licensed modules and the license
expiry details.
Target ID The target identifier linked to the license procured for a given cus-
tomer and EdenNet instance.
Customer Name The name of the customer specified while creating a target identi-
fier or EdenNet module licenses.
Country Indicates the name of the country where the EdenNet instance is
deployed.
Deployment Type Indicates the type of deployment of the EdenNet instance. Possi-
ble options are:
• Production
• POC
• Trial
• Pilot
• Ongoing
• Blocked
• Completed
Frequency Bands Specifies the list of frequency bands and cell count separated
with semicolon.
Table 8: Active SON Modules tab describes the columns in the Active SON Modules tab.
Run Mode Specifies if the Run Mode is in Open Loop or Closed loop.
Launch Date Indicates the time stamp of the module run that is initiated.
Table 9: Module History OL tab describes the columns in the Module History OL tab.
Time stamp The time stamp of the module run that is initiated.
Calendar week Indicates the start time of the week when the module is run.
Target clusters Specifies the name of a cluster if used in target cell selection
along with number of cells from that cluster.
Table 10: Module Schedule tab describes the columns in the Module Schedule tab.
Frequency (once in every) Specifies the frequency of scheduled task. It will be once in
every day or week or month as defined in scheduled task.
End Date Specifies the date when the schedule task should end.
Table 11: License_Info tab describes the columns in the License Info tab.
License Start Time The time from when the license is valid.
Expires in (days) Specifies the number of days from the date of report generation
when the license expires.
• activities
• status
For more information, see Configure and monitor SON modules section in the EdenNet User and Ad-
ministration Guide.