Middle - 02. 190227 - MBF LTE Middle P2.2 - EdenNet Acceptance Test - Rev1.0

EDENNET Customer Acceptance Test Manual
Revision History
Rev. Date Person in Charge Summary of Change
1.0 27Feb19 LamDT Initial version
Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

Contents
1 General...................................................................................................4
1.1 Purpose...................................................................................................4
1.2 Scope......................................................................................................4
1.2.1 Supported NE versions...........................................................................4
1.3 Recommendations..................................................................................4
2 Overview................................................................................................6
2.1 Test cases...............................................................................................6
2.2 Customer acceptance testing procedures...............................................9
2.2.1 Test execution and evaluation.................................................................9
3 Administration.....................................................................................10
3.1 Administration: Importing a SON Module..............................................10
3.2 Administration: Deleting a SON Module................................................11
3.3 Administration: Module Configuration....................................................12
3.3.1 Configuration of Module Default Values................................................12
3.3.2 Module Priority......................................................................................12
3.3.3 Module Exclusion List............................................................................13
3.3.4 Module User Permissions.....................................................................14
3.4 Administration: Roll back.......................................................................15
3.5 Administration: OSS Access Status......................................................16
3.6 Administration: Accounts.......................................................................17
3.6.1 Adding a User.......................................................................................17
3.6.2 Deleting a User.....................................................................................18
4 SON Modules.......................................................................................19
4.1 Automatic Neighbor Relation (ANR)......................................................19
4.1.1 Automatic Neighbor Relation (ANR_4G_IRAT).....................................19
4.1.2 LTE Automatic Neighbor Relation (ANR) Cleanup................................22
4.2 Reuse Code Optimization.....................................................................23
4.3 Coverage & Capacity Optimization (CCO) – LTE..................................24
4.4 Mobility Robustness Optimization (MRO)..............................................25
4.4.1 MRO - Verify CIO optimization for partial freeze strategy......................25
4.5 PRACH Optimization.............................................................................26
4.5.1 PRACH Fresh allocation with Fixed Reuse distance.............................26
4.5.2 PRACH Conflict Resolution with Relative reuse distance......................27

1 General
1.1 Purpose
The purpose of this document is to describe the system acceptance test
cases for Nokia EdenNet.
The test cases are chosen to give as complete picture as possible about
the EdenNet functionality.
1.2 Scope
This document should be used for verification of functionality.
The customer documentation mentioned in the manual can be found in
Nokia Networks Electronic Documentation (NED).
1.2.1 Supported NE versions
For supported NE versions see compatibility matrix from NOLS.
1.3 Recommendations
Always consult the customer and agree which operations can be executed
in the customer environment.

Several test cases affect the customer network and/or EdenNet
environment. Agree with the customer which test cases can be executed in
the customer environment.

2 Overview
The scope of Customer Acceptance Testing is to ensure that the EdenNet

is systematically functioning properly.
2.1 Test cases

The test cases are designed to prove that the EdenNet system has been
installed correctly.
The system acceptance test cases cover the main functional test which can
be tested under field conditions. Not all test cases may be appropriate for a
particular configuration, for example in cases where not all product or
optional hardware module was supplied.
Below table shows the summary of test cases for EdenNet Acceptance
Test
Execution Commen
Test Case ID Description Result
date t
3 Administration
3.1 Administration: Importing a SON Module
3.2 Administration: Deleting a SON Module
3.3 Administration: Module Configuration
3.3.1 Configuration of Module Default Values
3.3.2 Module Priority
3.3.3 Module Exclusion List
3.3.4 Module User Permissions
3.4 Administration: Roll back
3.5 Administration: OSS Access Status
3.6 Administration: Accounts
3.6.1 Adding a User
3.6.2 Deleting a User

4 SON Modules
4.1 Automatic Neighbor Relation (ANR)
4.1.1 Automatic Neighbor Relation (ANR_4G_IRAT)
4.1.2 LTE Automatic Neighbor Relation (ANR) Cleanup
4.2 Reuse Code Optimization
4.3 Coverage & Capacity Optimization (CCO) – LTE
4.4 Mobility Robustness Optimization (MRO)
MRO - Verify CIO optimization for partial freeze
4.4.1 strategy
4.5 PRACH Optimization
4.5.1 PRACH Fresh allocation with Fixed Reuse distance
PRACH Conflict Resolution with Relative reuse
4.5.2 distance
2.2 Customer acceptance testing procedures

Recommended management procedures for facilitating organising and
executing the testing process are listed below:
 Test execution and evaluation in accordance with agreed plans and
procedures
 Completion of incident reports
2.2.1 Test execution and evaluation
Test execution and evaluation is the process of performing all the system
acceptance test cases and observing the results. This includes setting up
the test environment, executing test cases, and recording the outcome of
the test cases.
The outcome of the test cases will be one of the following:
 Pass – There are no observed critical or major incidents.
 Not Applicable – The test conditions do not match or customer does
not use the functions
 Fail – One or more of the observed incidents are Critical.

3 Administration
3.1 Administration: Importing a SON Module

TEST PURPOSE:
To verify if a SON Module can be imported from the Eden-NET UI.
PREREQUISITES:
User should be successfully logged into the Eden-NET UI.
Module that will be imported is available in the local computer.
TEST EXECUTION:
1. Navigate to the Administration tab in the UI.
2. Select the Modules tab.
3. Click on the File -> Import Module
4. Browse to the location where the SON Module file is available
5. Select the module to be imported.
6. Select “Upload” button to import module.
EXPECTED RESULTS:
Module is successfully imported without any errors.
Status
PASSED □ FAILED □ NOT APPLICABLE □
Comment
Date
Name

Signature __________________________ __________________________
MOBIFONE Nokia Networks
3.2 Administration: Deleting a SON Module

TEST PURPOSE:
To delete a SON Module.
Note: This test case deletes the SON Module, so this test case should be
executed at user discretion.
PREREQUISITES:
Eden-NET is installed and the SON Module is available in the UI.
TEST EXECUTION:
1. Login to Eden-NET UI
2. Navigate through Administration-> Modules-> Select Module to be deleted
-> File-> Delete Module
EXPECTED RESULTS:
1. Login should be successful.
2. The module should warn the user if he is sure to perform the operation.
Module is successfully deleted from Eden-NET
Status
Comment
Date
Name
Signature __________________________ __________________________


3.3 Administration: Module Configuration
3.3.1 Configuration of Module Default Values
TEST PURPOSE:
To view the default values of a module and change them as needed.
PREREQUISITES:
TEST EXECUTION:
2. Navigate through Administration-> Modules-> Select any Module->
Configure->Default Values
3. If needed, select any other value than the listed ones and click Save
EXPECTED RESULTS:
1. Login to Eden-NET UI is successful.
2. The default values are visible to the user.
3. The user is able to make the changes and the changes are visible while
executing the Module.
Status
Comment
Date
Name
Signature __________________________ __________________________

3.3.2 Module Priority
TEST PURPOSE:

To view/alter the priority for SON Modules.
PREREQUISITES:
TEST EXECUTION:
1. Login to Eden-NET UI.
2. Navigate through Administration-> Modules-> Configure-> Module Priority
3. Select any module and change “Priority”. (Select a value between 0 and 7,
where 7 is the highest priority.)
4. Click on “Save” button
EXPECTED RESULTS:
1. Login to Eden-NET is successful.
2. SON Module Priority window opens.
3. Any SON Module is selected and priority of the SON Module is changed
4. New priority value for selected SON Module is saved
Status
Comment
Date
Name
Signature __________________________ __________________________

3.3.3 Module Exclusion List
TEST PURPOSE:
To choose the cells that should not be excluded by the Module.
PREREQUISITES:
Eden NET is installed and the SON Module is available in the UI.
TEST EXECUTION:

2. Navigate through Administration-> Modules -> Select the Module->
Configure-> Module Exclusion List.
5. Select the Cells that need to be excluded by the Module and click Close.
EXPECTED RESULTS:
1. Login to Eden-NET is successful.
2. Module Exclusion List window opens.
3. User selected cells are added to the Exclusion list successfully.
Status
Comment
Date
Name
Signature __________________________ __________________________

3.3.4 Module User Permissions
TEST PURPOSE:
To view/modify the Module User Permissions
PREREQUISITES:
TEST EXECUTION:
2. Navigate through Administration-> Modules-> Select any Module-> Configure
-> Module User Permissions.
3. If needed, edit the permissions of the user and click Save.
EXPECTED RESULTS:
2. User Permissions window opens and different permissions for the user are
displayed.
3. The user can successfully change the permission and save it successfully.

Status
Comment
Date
Name
Signature __________________________ __________________________

3.4 Administration: Roll back

TEST PURPOSE:
To verify if the network can be rolled back as per the selected changes.
PREREQUISITES:
Eden-NET is installed and some SON module has been executed prior to
the rollback so that the network can be rolled back to its previous state.
TEST EXECUTION:
2. Navigate through Administration-> Rollback
3. Select the date and time to which the network needs to be rolled back and
click ‘Get changes’.
4. Chose the changes that need to be rolled back and click Rollback Selected
Changes
EXPECTED RESULTS:
1. Login should be successful.
2. User should be able to select the date and time to which roll back should
happen. Once Get changes is clicked, Eden-NET will fetch the list of changes
that were done in the network.
3. Once Rollback selected changes is clicked, Eden-NET should calculate the
changes that will be made and the network work should be rolled back as
opted.
Status

Comment
Date
Name
Signature __________________________ __________________________

3.5 Administration: OSS Access Status

TEST PURPOSE:
To disable or enable the OSS Access
PREREQUISITES:
Eden-NET is installed and integrated to a Region.
TEST EXECUTION:
2. Navigate through Administration->OSS Access
3. Select the OSS listed
4. In order to:
a. immediately OSS Access enable/disable click Enable or Disable
b. OSS Access enable/disable at later point of time click on Schedule
and configure.
EXPECTED RESULTS
1. Login is successful.
2. The access to OSS from Eden-NET is successfully disabled or enabled.
Status
Comment
Date
Name

Signature __________________________ __________________________
3.6 Administration: Accounts
3.6.1 Adding a User
TEST PURPOSE:
To add a User to access Eden-NET.
PREREQUISITES:
Eden-NET is installed.
TEST EXECUTION:
1. Login to Eden-NET UI with admin privileges.
2. Navigate through Administration-> Accounts.
3. Click on Add User and provide the mandatory information, choose the User
group accordingly and click Save Changes.
EXPECTED RESULTS
1. User is able to login successfully.
2. User should be successfully created and should be able to login with the new
credentials.
Status
Comment
Date
Name
Signature __________________________ __________________________


3.6.2 Deleting a User
TEST PURPOSE:
To delete a User.
PREREQUISITES:
Eden-NET is installed.
TEST EXECUTION:
1. Login to Eden-NET UI with admin privileges.
2. Navigate through Administration-> Accounts.
3. Click on the User that needs to be deleted and click on the Red Cross mark
indicating to delete the user and click Save.
EXPECTED RESULTS
2. Once the save is clicked, the user is deleted from Eden-NET and can no
longer log in to the UI.
Status
Comment
Date
Name
Signature __________________________ __________________________


4 SON Modules
4.1 Automatic Neighbor Relation (ANR)
4.1.1 Automatic Neighbor Relation (ANR_4G_IRAT)
TEST PURPOSE:
The purpose of this test case is to verify the ANR-4G IRAT module
functionality.
PREREQUISITES:
1. CM Data. Ensure that CM data is available for the area being tested including
managed objects for existing GSM->WCDMA neighbour relations.
2. Cell Plan Data. Ensure that Cell Plan data is available for all cells in the area
being tested including site location (lat, lon) and antenna details (orientation,
beam-width).
3. PM Data. Ensure that at least 24hrs of KPI data is available for cells in test
area. PM counts for LTE->WCDMA and LTE->GSM handovers per relation
are required to evaluate existing relations for replacement. Per relation counts
for WCDMA->WCDMA handovers and GSM->GSM handovers are also be
utilized by the module to find missing neighbors.
4. Module Configuration. Ensure that a module configuration is loaded with
module parameter values in line with the recommendations provided in the
Feature Description.
5. LMS Configuration. Including:
a. Definition of the allowed LTE->WCDMA and LTE->GSM relations
within each node configuration. This is done in the "rules" section of
the LMS. An example is given below which can be inserted into one or
more node configurations in the LMS. From the layer which matches
the “optional_LTE” definition the “optional_LTE_row_rule1” is used:
"optional_LTE": "optional_LTE_row_rule1",

b. The “row rules" section of the LMS is normally used to create rule
sets. An example rule set is given below. So in this example when the
“optional_GSM_row_rule1” is specified in a node configuration it
permits relations to a layer named “GSM” and WCDMA layers named
“U1” and “P1”:
"optional_LTE_row_rule1": {
"GSM": { "condition" : "always", "hop": { "template":
"lte_gsm" } },
"U1": { "condition" : "majority", "hop": { "template": "lte_wcdma" } },
"P1": { "condition" : "majority", "hop": { "template": "lte_wcdma" } }
},
c. LTE->WCDMA and LTE->GSM attribute values in the "templates"

section. An example with values for required Nokia attributes for LTE-
>WCDMA and LTE->GSM relations is given below:
"templates": {
"lte_gsm": {
"nrControl": "automatic",
"redirWithSysInfoAllowed": "allowed",
"eNACCAllowed": "allowed",
"srvccAllowed": "allowed"
},
"lte_wcdma": {
"nrControl": "automatic",
"csfbPsHoAllowed": "forbidden",
"psHoAllowed": "forbidden",
"srvccAllowed": "allowed",
"redirWithSysInfoAllowed": "allowed",
"removeAllowed": "true",
"utranLbAllowed": "true"
},
"enodeB_UMTS": {
"srvccHoInd": "CSonly"
},
"enodeB_GSM": {
"dtm": "FALSE",
"networkControlOrder": "NC0",
"systemInfoType": "none"
}
},
TEST EXECUTION:
1. Navigate to the SON Modules / Configure page to create a new module
execution
2. Select the ANR_4G_IRAT module

3. Select a cluster of at least 200 target LTE cells for execution.
4. In the "Configure Parameters":
a. Set the "SON Operation Mode" appropriately (Open Loop for first
runs, Closed Loop after successful Open Loop)
5. Using the defaults for the rest of the configuration flow, execute the module
6. Verify that the module is running
7. When the module execution is complete, verify the results
EXPECTED RESULTS:
1. There are no errors/exceptions during the execution which caused the
module to stop before neighbor additions and removals were proposed.
Examples would be Out of Memory, ems timeouts, ems validation errors, etc.
2. Towards the end of the log Neighbor Additions (with the correct attribute
values as defined in the LMS) AND Neighbor Removals for LTE->WCDMA
and LTE->GSM are specified.
3. The log ends with message: "Commit Successful" (for Closed Loop run only).
4. Check the "Output Report".
a. “Changes” tab:
i. Includes additions and removals of LTE->WCDMA and LTE-
>GSM relations as indicated in the module log.
ii. LTE IRAT neighbour additions are limited to those as specified
in the LMS.
b. "HO Report" tab:
i. Has values for HO attempt and success counts for existing
LTE IRAT relations
ii. All percentage values are less than 100%
iii. Correctly reflects the LTE IRAT neighbor additions and LTE
IRAT neighbor removals included in the “Changes” tab.
c. " Neighbor Performance " tab:
i. "Potential Replacement" column indicates that some existing
LTE IRAT relations could potentially be replaced
Status
Comment
Date
Name
Signature __________________________ __________________________


4.1.2 LTE Automatic Neighbor Relation (ANR) Cleanup
TEST PURPOSE:
To verify that LTE ANR Cleanup Module successfully identifies all the
distant neighbors and removes them from neighbor lists.
PREREQUISITES:
1. All the required CM and PM data are available in EMS.
2. Eden-NET is integrated successfully with EMS.
TEST EXECUTION:
1. Launch Eden-NET GUI
2. Go to SON Modules->Configure->LTE_ANR_Cleanup
3. Select any number of target cells - LTE cells
4. Run module with default GUI/.ini setting in “Close Loop” or “Open Loop”
EXPECTED RESULTS:
In case of Open Loop selection:
1. Module run finishes without exception
2. Module caches Cell Data
3. Module caches neighbor data and handover data
4. Module detects intra-frequency neighbors to cleanup
5. Module detects inter-frequency neighbors to cleanup
6. Module generates excel report file
In case of Close Loop selection:
2. Module caches Cell Data
3. Module caches neighbor data and handover data
4. Module detects intra-frequency neighbors to cleanup
5. Module detects inter-frequency neighbors to cleanup
6. Module generates excel report file
8. Verify that module generates xml plan file for neighbor removal
Status
Comment
Date
Name

Signature __________________________ __________________________
4.2 Reuse Code Optimization

TEST PURPOSE:
To report PCI Code reuse in LTE
PREREQUISITES:
1. LTE – PCIReuse module is installed,
2. KPI data is available to execute the module.
TEST EXECUTION:
1. Launch Eden-NET GUI.
2. Go to SON Modules->Configure.
3. Select PCIReuse
4. Select the target cells.
5. Click next and run the module with the default user input parameters.
EXPECTED RESULTS:
1. The module run should be finished successfully, creating an output report file
at the end.
2. The module should successfully detect the PCI confusion cases and list in the
output file - PCI Confusions tab.
3. All PCI confusion cases should be resolved by PCI Retunes.
Status
Comment
Date
Name
Signature
__________________________ __________________________

4.3 Coverage & Capacity Optimization (CCO) – LTE

TEST PURPOSE:
Verify LTE CCO Module
PREREQUISITES:
1. Coverage & Capacity Optimization Module for LTE is installed.
2. There are sufficient PM and CM data available for testing (2G, 3G, 4G).
TEST EXECUTION:
1. Launch Eden-NET
2. Navigate to the SON Modules / Configure for starting the module execution
3. Select the LTECCO module
4. Select all cells from all technologies
5. Use the default values
a. Make sure the SON Operation Mode is configured as Open Loop
6. Active Now and launch the module
7. When the module finished running:
a. check the ratio execution time vs. number of cells
b. check the log for errors
c. check the output results
EXPECTED RESULTS:
1. Execution time per cell should not exceed 300 ms
2. Log should be free of errors (RET exception excluded, would apply only to
Closed Loop mode)
3. Output results should show the following output files with filled-in columns:
a. Handover_Flow_Outputs.csv should list cells with values for each
valid neighbor (name, HO statistics and distance)
b. Result files for over-shooters and under-shooters should have been
produced and include information related to each cells as describe in
the design specifications
c. Monitoring files for over-shooters and under-shooters should have
been produced and include information related to each cells as
described in the design specifications
Status
Comment

Date
Name
Signature __________________________ __________________________

4.4 Mobility Robustness Optimization (MRO)
4.4.1 MRO - Verify CIO optimization for partial freeze strategy
TEST PURPOSE:
To verify LTE MRO Inter Frequency optimization by verifying CIO
Optimization for Partial Freeze Strategy.
PREREQUISITES:
1. Ensure that the CM and PM data needed by the SON Module is available.
2. Ensure that there are few intra and inter frequency relations exist with
handover problems
3. Make sure that the relation A->B is on the top of List created based on Cost
function
TEST EXECUTION:
1. Login to Eden-NET lab select run the MRO module with
Optimize_cell_level_parameters option set to False
2. Verify that the EUtranRel A -> B is optimised
3. Verify that all outgoing rels from A and B (Except A->B) are frozen
4. Verify that the next rel(other than the frozen rels) in the List is picked up for
optimization.
5. Verify the Logs and Report
EXPECTED RESULTS:
1. Login should be successful and the execution should be successful
2. A -> B should go for CIO optimization
3. All outgoing rels from A and B are frozen
4. The next rel in the List is optimized and the corresponding cells outgoing rels
are frozen. And the next rel in list is picked up for optimization.

5. Report and Logs should be informative and updated properly
Status
Comment
Date
Name
Signature __________________________ __________________________

4.5 PRACH Optimization

Ini file to be imported for the module. Administration->
Select PRACH_Optimization_LTE -> configure -> module configuration
4.5.1 PRACH Fresh allocation with Fixed Reuse distance
TEST PURPOSE:
To allocate PRACH parameters for selected scope according to given
settings for Heterogeneous network data.
PREREQUISITES:
1. Eden-NET is integrated to EdenNet.
2. Create a cluster with LNCELs, where some LNCELs in the scope are of FDD
and some LNCELs are of TDD system type for which new allocation of
PRACH parameters is to be done.
3. Antennas (with co-ordinates) associated with all the LNCELs.
TEST EXECUTION:

1. Log in E-Net lab and select PRACH_optimization_LTE module and select the
cluster created for PRACH optimization.
2. Run the PRACH optimization module in open loop, with following option in the
UI.
Select the :
Use case selection- Fresh Allocation
Neighbor Cell Finding Strategy as Fixed Reuse Distance Strategy, and other
dependent (Fixed reuse distance) parameters
Plan PRACH Frequency Offset (PRFO) - yes
Plan PRACH Configuration Index (PRCI) - yes
Plan PRACH Cyclic Shift (PRCS) – yes
SON operation Mode – Closed loop
3. Verify the Report created under instant output section.
4. Verify the PRACH parameters in EdenNet after successful provision
EXPECTED RESULTS:
1. PRACH_optimization_LTE should be available and scope cluster is selected
2. PRACH parameters are allocated by considering the LNCELs present under
the given fixed Reuse distance and LNREL neighbours.
3. PRACH parameters should be updated successfully in EdenNet.
Status
Comment
Date
Name
Signature __________________________ __________________________

4.5.2 PRACH Conflict Resolution with Relative reuse distance
TEST PURPOSE:
To allocate PRACH parameters for selected scope according to
given settings for Heterogeneous network data .
PREREQUISITES:
1. Eden-NET is integrated to EdenNet.

2. Create a cluster with LNCELs, where some LNCELs in the scope are of FDD
and some LNCELs are of TDD system type for which conflict of PRACH
parameters exists with neighbors.
3. Antennas (with co-ordinates) associated with all the LNCELs.
TEST EXECUTION:
1. Log in E-Net lab and select PRACH_optimization_LTE module and Select the
cluster created for PRACH optimization.
2. Run the PRACH optimization module in open loop, with following option in the
UI.
Select the
Use case selection- conflict resolution
Neighbor Cell Finding Strategy as Relative Reuse Distance Strategy, and
other dependent (Relative reuse distance) parameters
Plan PRACH Frequency Offset (PRFO) - yes
Plan PRACH Configuration Index (PRCI) - yes
Plan PRACH Cyclic Shift (PRCS) – yes
SON operation Mode – Closed loop
3. Verify the Report created under instant output section.
4. Verify the PRACH parameters in EdenNet after successful provision
EXPECTED RESULTS:
1. PRACH_optimization_LTE should be available and scope cluster is selected
2. PRACH parameters are allocated by considering the LNCELs present under
the given fixed Reuse distance and LNREL neighbours.
3. PRACH parameters should be updated successfully in EdenNet.
Status
Comment
Date
Name
Signature __________________________ __________________________


Customer Acceptance Test Certificate
EdenNet Software release
(Performed on / / )
This certifies that feature acceptance test cases

were performed completely.
Signature: ………………………………… ….……………………………..

Name: ………………………….…….. …………………………………
Title: ………………………….…….. …………………………………
Date: .............................................. …………………………………

Middle - 02. 190227 - MBF LTE Middle P2.2 - EdenNet Acceptance Test - Rev1.0

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Middle - 02. 190227 - MBF LTE Middle P2.2 - EdenNet Acceptance Test - Rev1.0

Uploaded by

Copyright:

Available Formats

EDENNET Customer Acceptance Test Manual

Rev. Date Person in Charge Summary of Change

1.0 27Feb19 LamDT Initial version

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

1.2.1 Supported NE versions

For supported NE versions see compatibility matrix from NOLS.

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

The scope of Customer Acceptance Testing is to ensure that the EdenNet

2.1 Test cases

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

2.2 Customer acceptance testing procedures

2.2.1 Test execution and evaluation

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

3.1 Administration: Importing a SON Module

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

3.2 Administration: Deleting a SON Module

Signature __________________________ __________________________

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

3.3.1 Configuration of Module Default Values

Signature __________________________ __________________________

3.3.2 Module Priority

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

Signature __________________________ __________________________

3.3.3 Module Exclusion List

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

Signature __________________________ __________________________

3.3.4 Module User Permissions

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

Signature __________________________ __________________________

3.4 Administration: Roll back

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

Signature __________________________ __________________________

3.5 Administration: OSS Access Status

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

3.6 Administration: Accounts

3.6.1 Adding a User

Signature __________________________ __________________________

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

Signature __________________________ __________________________

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

4.1 Automatic Neighbor Relation (ANR)

4.1.1 Automatic Neighbor Relation (ANR_4G_IRAT)

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

c. LTE->WCDMA and LTE->GSM attribute values in the "templates"

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

Signature __________________________ __________________________

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

4.2 Reuse Code Optimization

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

4.3 Coverage & Capacity Optimization (CCO) – LTE

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

Signature __________________________ __________________________

4.4 Mobility Robustness Optimization (MRO)

4.4.1 MRO - Verify CIO optimization for partial freeze strategy

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

Signature __________________________ __________________________

4.5 PRACH Optimization

4.5.1 PRACH Fresh allocation with Fixed Reuse distance

Contract No. TECH/TCT-618-18-MOBIFONE/NSN OY-NSN VN-ANSV ()

Signature

Signature

Signature

Signature

Signature

Signature

Signature

Signature

Signature

Signature

Signature

Signature

Signature