EdenNet 21 FP 2106

GSM Automatic Neighbor Relations Guide

DN09241774
Issue: 1-1
GSM Automatic Neighbor Relations Guide DN09241774 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.
GSM Automatic Neighbor Relations DN09241774 1-1 Table of Contents
Guide

Contents
1 Summary of changes...................................................................................................................................... 6

2 Overview of GSM ANR..................................................................................................................................12

2.1 GSM ANR interactions............................................................................................................................13

3 GSM ANR functional description and guidelines...................................................................................... 14

3.1 Operational modes.................................................................................................................................. 14
3.1.1 Open loop....................................................................................................................................... 14
3.1.2 Closed loop..................................................................................................................................... 14
3.2 Bidirectional support................................................................................................................................15
3.2.1 Handling GSM-INTRA ENM neighbors.......................................................................................... 15
3.3 Removal of poorly performing neighbor relations...................................................................................17
3.4 Neighbor trimming for GSM to UMTS relations......................................................................................17
3.5 Measurement based additions for GSM to GSM relations..................................................................... 17
3.6 Cross OSS.............................................................................................................................................. 18
3.6.1 Cross OSS support for ANR 2G (with NAdC)................................................................................18
3.6.2 Cross OSS support for ANR 2G (without NAdC)...........................................................................18

4 GSM ANR algorithm...................................................................................................................................... 20

4.1 Optimization of GSM to GSM relations.................................................................................................. 20
4.1.1 Removal of poorly performing distant neighbors for high TCH drop rate cells...............................20
4.1.2 Addition of missing neighbors........................................................................................................ 20
4.1.2.1 Add missing whitelisted neighbors......................................................................................... 20
4.1.2.2 Add missing first tier neighbors and high TCH drop rate cell................................................ 21
4.1.2.3 Add missing first tier neighbors and low TCH drop rate cell..................................................21
4.1.2.4 Add neighbor cell for high TCH drop rate cell with no missing first tier neighbors................. 21
4.1.3 Replacement of existing neighbors................................................................................................ 22
4.1.3.1 Initial replacement list.............................................................................................................22
4.1.3.2 Additional filtering................................................................................................................... 23
4.1.3.3 Ranking method for existing relations....................................................................................23
4.1.3.4 Outperformance of candidate versus existing relations......................................................... 23
4.2 Optimization of GSM to WCDMA relations.............................................................................................24
4.2.1 Removal of poorly performing distant GSM IRAT relations............................................................24
4.2.2 Trimming of GSM IRAT neighbors................................................................................................. 25
4.2.3 Addition of missing GSM IRAT neighbors...................................................................................... 25
4.2.3.1 Add missing whitelisted GSM IRAT neighbors...................................................................... 25
4.2.3.2 Add missing first tier GSM IRAT neighbors........................................................................... 25
4.2.3.3 Add missing GSM IRAT neighbors based on HO Success counts........................................ 25
4.2.3.4 Additional detected missing GSM IRAT neighbors based on network topology.....................26
4.2.4 Replacement of existing GSM IRAT neighbors..............................................................................28
4.2.4.1 Initial replacement list.............................................................................................................28
4.2.4.2 Existing GSM IRAT usage threshold......................................................................................28
4.2.4.3 Existing HO Success Score threshold................................................................................... 28

EdenNet 21 FP 2106 © 2021 Nokia 3

GSM Automatic Neighbor Relations DN09241774 1-1 Table of Contents
Guide

4.2.4.4 Ranking method..................................................................................................................... 28

4.2.4.5 Out-performance criteria when neighbor candidate and existing neighbor have HO
success score............................................................................................................................... 29
4.2.4.6 Out-performance criteria when neighbor candidate or existing neighbor do not have HO
success score............................................................................................................................... 29
4.3 Configuring relation DN ID for Ericsson (2G)......................................................................................... 30

5 Configuring and executing GSM ANR........................................................................................................ 33

5.1 GSM ANR prerequisites..........................................................................................................................33
5.1.1 License............................................................................................................................................ 33
5.1.2 CM data and PM data....................................................................................................................33
5.1.3 Cell plan and OSS data................................................................................................................. 34
5.1.3.1 Identify issues in cell plan and OSS data..............................................................................35
5.1.4 Tier counting and geo-scoring........................................................................................................ 36
5.1.5 LMS and neighbor list sizes........................................................................................................... 37
5.1.5.1 LMS Configuration..................................................................................................................37
5.1.5.2 Module configuration.............................................................................................................. 38
5.1.6 Check CF and DAC measurements (for Nokia vendor).................................................................39
5.1.6.1 Activating Double BCCH Allocation list..................................................................................39
5.1.7 Activate BA list recordings (for Ericsson vendor)...........................................................................40
5.2 Accessing GSM ANR..............................................................................................................................41
5.3 Configuring targets for GSM ANR.......................................................................................................... 42
5.4 Configuring parameters for GSM ANR................................................................................................... 43
5.5 Selecting the configuration file for GSM ANR........................................................................................ 44
5.6 Selecting the execution type for GSM ANR........................................................................................... 44
5.7 Confirming execution for GSM ANR.......................................................................................................45
5.8 ENM GSM BA list and UMFI list updates.............................................................................................. 45
5.8.1 BA list updates................................................................................................................................45
5.8.2 UMFI list updates............................................................................................................................46

6 GSM ANR configuration parameters...........................................................................................................47

6.1 GSM ANR GUI parameters.................................................................................................................... 47
6.2 GSM ANR INI parameters...................................................................................................................... 50
6.2.1 Common configuration file parameters...........................................................................................51
6.2.2 Baseline configuration file parameters........................................................................................... 61
6.2.3 GSM to GSM measurement based detection parameters............................................................. 64
6.2.4 GSM to UMTS configuration file parameters................................................................................. 66
6.2.5 Example of GSM ANR configuration file........................................................................................ 71
6.3 Configuring INI parameters.....................................................................................................................72

7 Viewing GSM ANR targets............................................................................................................................75

8 Viewing GSM ANR reports........................................................................................................................... 76

8.1 GSM ANR reports................................................................................................................................... 77

9 Plan provisioning in case of failure............................................................................................................ 93

9.1 Re-provision a plan................................................................................................................................. 93

EdenNet 21 FP 2106 © 2021 Nokia 4

GSM Automatic Neighbor Relations DN09241774 1-1 Table of Contents
Guide

9.2 Filtering provisioning of failed cells based on feedback logs received from NAdC.................................93

10 Viewing GSM ANR events.......................................................................................................................... 95

10.1 GSM ANR events..................................................................................................................................96

11 Viewing SON change reports..................................................................................................................... 98

11.1 Cell level records...................................................................................................................................98

12 Monitoring GSM ANR................................................................................................................................100

12.1 Module Monitor Service...................................................................................................................... 100

13 Troubleshooting ANR................................................................................................................................101
13.1 ANR tries to create relations that already exist..................................................................................101

EdenNet 21 FP 2106 © 2021 Nokia 5

GSM Automatic Neighbor Relations DN09241774 1-1 Summary of changes
Guide

1 Summary of changes

Release Change description

EdenNet 21 FP 2106 No change.

EdenNet 21 FP 2105 Updated section:

• Tier counting and geo-scoring

EdenNet 21 FP 2104 No change.

EdenNet 21 FP 2103 No change.

EdenNet 21 Updated sections:

• GSM to UMTS configuration file parameters: The following parameters

are added:

– Limit_no_of_detected_neighbors
– Buffer_for_Detected_Neighbors
• Additional detected missing GSM IRAT neighbors based on network
topology: The note is updated.
• Common configuration file parameters: A note is added to the parameter
description of the validation_workflow_enabled parameter.

EdenNet 20 FP 2011 Added sections:

• Handling GSM-INTRA ENM neighbors

• ENM GSM BA list and UMFI list updates
• BA list updates
• UMFI list updates
• Plan provisioning in case of failure

Updated sections:

• Common configuration file parameters:

– The PPS_Exclude_criteria parameter description is modified.

– The PPS_Time_between_retries parameter name is changed to
PPS_Time_between_retries_in_minutes.
• GSM to UMTS configuration file parameters

– The UMFI_diversity parameter is added.

• Configuring relation DN ID for Ericsson (2G)

EdenNet 20 FP 2010 No change.

EdenNet 20 FP 2009 No change.

EdenNet 21 FP 2106 © 2021 Nokia 6

GSM Automatic Neighbor Relations DN09241774 1-1 Summary of changes
Guide

Release Change description

EdenNet 20 FP 2008 Updated section:

• Common configuration file parameters: The following INI parameters are

added:

– PPS_Retry
– PPS_Number_of_retries_of_provision
– PPS_Time_between_retries
– PPS_Exclude_criteria
– validation_workflow_enabled

EdenNet 20 FP 2007 No change.

EdenNet 20 Updated sections:

• Overview of GSM ANR

• GSM ANR reports
• Example of GSM ANR configuration file

EdenNet 19A FP Updated section:

2004
• Common configuration file parameters: A new parameter (Config-
urable_relation_Id) is added.

Added section:

• Configuring relation DN ID for Ericsson (2G)

EdenNet 19A FP Updated sections:

2003
• Add neighbor cell for high TCH drop rate cell with no missing first tier
neighbors: Information related to archipelago deployment is added.
• Common configuration file parameters: Is_ocean_mode parameter is
added.
• Example of GSM ANR configuration file

EdenNet 19A FP No change.

2002

EdenNet 19A FP Updated section:

2001
• The following parameters are added to the Common configuration file pa-
rameters section:

– global_white_list
– global_white_list_plugins

EdenNet 19A FP Updated sections:

1912

EdenNet 21 FP 2106 © 2021 Nokia 7

GSM Automatic Neighbor Relations DN09241774 1-1 Summary of changes
Guide

Release Change description

• Common configuration file parameters: The description of the TimeBe-

tweenPushes_15Mins parameter is modified.
• Example of GSM ANR configuration file

EdenNet 19A FP Updated sections:

1911
• A note is added to the Overview of GSM ANR section.
• A note is added to the Closed loop section.
• A new parameter (TimeBetweenPushes_15Mins) is added to the
Common configuration file parameters section.
• The Add neighbor cell for high TCH drop rate cell with no missing first tier
neighbors section is modified.

EdenNet 19A The restriction for measurement based addition is removed from the Mea-
surement based additions for GSM to GSM relations section.

EdenNet 19 FP 1906 No change.

EdenNet 19 FP 1905 The Measurement based additions for GSM to GSM relations section is up-
dated.

EdenNet 19 FP 1904 Added sections:

• Cross OSS support for ANR 2G (with NAdC)

• Cross OSS support for ANR 2G (without NAdC)

Updated sections:

• Instances of Custom modules are changed to Adapted modules in the fol-

lowing sections:

– Accessing GSM ANR

– Configuring INI parameters
• A new parameter (Enable_first_tier_adds) is added to the Com-
mon configuration file parameters section.
• The GSM_IRAT_enforce_first_tier parameter is removed from the
GSM to UMTS configuration file parameters section.
• A note is added in the Common configuration file parameters section.

EdenNet 19 The following INI parameters are added to the Common configuration file pa-
rameters section:

• Optimize_Final_Neighbors
• Exclude_outdoor_cells

The Optimize_Detected_Neighbors INI parameter is added to the

Baseline configuration file parameters section.

EdenNet 21 FP 2106 © 2021 Nokia 8

GSM Automatic Neighbor Relations DN09241774 1-1 Summary of changes
Guide

Release Change description

The default value is modified for the GSM_IRAT_excluded_HO_based_

addition_method parameter.

EdenNet 18 SP1 The descriptions of the following parameters have been modified in the Com-
1901 mon configuration file parameters section:

• Label_type_for_Ericsson_cells
• Use_userSpecificInfo_for_ALU_cells

EdenNet 18 SP1 No updates.

1812

EdenNet 18 SP1 A note is removed from Viewing SON change reports.

1811

EdenNet 18 SP1 The description of the Module_log_level parameter is modified.

EdenNet 18 FP1 The Exclude_indoor_cells parameter is added to the Common configu-

ration file parameters section.

EdenNet 18 Updated content:

• The parameter name is changed from GSM_Min_Tier_Count_For_

Cell_Removal to GSM_minimum_tier_count_for_intra_cell_
removal in the section GSM to UMTS configuration file parameters.
• IRAT Reuse Conflicts tab (for GSM-UMTS candidates only) and IRAT
Neighbor Performance tab (for GSM-UMTS neighbors only) tables are re-
moved and the content of these tables is now merged with Reuse Con-
flicts and Neighbor Performance tables in GSM ANR reports. In addition,
Neighbor type row is added to both the tables.
• Information has been updated for Measurements Low Threshold, Exceed-
ing Low Threshold Counts, Percent Exceeding the Low Threshold, and
Measurements Low Threshold Percent in the GSM ANR reports section.
• Information has been updated for GSM to GSM cell relation
neighbor optimization, GSM to GSM Neighbor Deletion,
and GSM to UMTS cell relation neighbor optimization
parameters in the GSM ANR GUI parameters section.
• The below parameters in the GSM ANR GUI parameters section are mod-
ified:

– GSM to GSM cell relations remove distant poor

performers
– GSM to GSM cell relation neighbor optimization
• A note is added to the GSM_IRAT_Neighbor_List_Size_3G_per_
layer parameter description in the GSM to UMTS configuration file para-
meters section.

EdenNet 21 FP 2106 © 2021 Nokia 9

GSM Automatic Neighbor Relations DN09241774 1-1 Summary of changes
Guide

Release Change description

Added content:

• A note about the Tier column is added to the GSM ANR reports section.
• A new parameter is added to the section Baseline configuration file para-
meters: GSM_minimum_tier_count_for_IRAT_cell_removal
• Cell Level Summary and Cell level records tables are added to the GSM
ANR reports section.
• Additional rows are added to the following tables in the GSM ANR reports
section.

– Changes tab
– Detected neighbors tab
– Final neighbors tab
– DCR report tab
– HO report tab
• The following sections are added:

– Nokia vendor dependencies

– Ericsson vendor dependencies
• The below parameters are added to the Common configuration file para-
meters section:

– Label_type_for_Ericsson_cells
– Use_userSpecificInfo_for_ALU_cells
– Module_log_level
• The GSM_Meas_BCCH_BSIC_Disambiguate_All parameter is added
to the section GSM to GSM measurement based detection parameters.
• The Troubleshooting ANR section is added.

EdenNet 17 SP1 • Addition of missing GSM IRAT neighbors section is updated with a note
FP1 added under Additional detected missing GSM IRAT neighbors based on
network topology.
• Common configuration file parameters section is updated.
• Baseline configuration file parameters section is updated.
• GSM to UMTS configuration file parameters section is updated.
• New tabs are added to the GSM ANR reports section:

– BA <vendor_name> List Measurements

– Disambiguation

EdenNet 17 SP1 • Plan name tag parameter is added to the section GSM ANR GUI para-
meters.
• GSM ANR reports section is updated.

EdenNet 21 FP 2106 © 2021 Nokia 10

GSM Automatic Neighbor Relations DN09241774 1-1 Summary of changes
Guide

Release Change description

• Module Monitor Service information has been updated under the section
Monitoring GSM ANR.
• The Tabs parameter is added to the Common configuration file parame-
ters section.

EdenNet 17 FP1 • The Configuring and executing GSM ANR section is enhanced by adding
Selecting the configuration file for GSM ANR section.
• The Configuring INI parameters section is updated with Save As and Set
As Default options.
• The GSM ANR reports section is updated.

EdenNet 17 The document is restructured. The newly added sections are:

• GSM ANR functional description and guidelines

• Viewing GSM ANR events
• Viewing GSM ANR targets

The updated sections are:

• Configuring and executing GSM ANR

• GSM ANR configuration parameters
• Viewing GSM ANR reports

EdenNet 16 SP4 The newly added section is:

Cross OSS

The updated section is:

Cell plan and OSS data

EdenNet 16 SP3 The updated sections are:

• Addition of missing neighbors

• Replacement of existing neighbors
• GSM ANR GUI parameters
• Common configuration file parameters
• GSM to GSM measurement based detection parameters
• GSM to UMTS configuration file parameters

EdenNet 16 SP2 This is a new document that provides information on how to optimize network
performance by automating the task of managing neighbor relations.

Table 1: Summary of changes

EdenNet 21 FP 2106 © 2021 Nokia 11

GSM Automatic Neighbor Relations DN09241774 1-1 Overview of GSM ANR
Guide

2 Overview of GSM ANR

The GSM ANR (Automatic Neighbor Relations) module optimizes the neighbor lists of GSM cells. In
the GSM network, there are several types of handovers:

• Intra-cell handovers for changing TCH (Traffic Channels) within the same cell
• Inter-cell handovers for mobility between different cells in the same system (either intra-BSC or in-
ter-BSC)
• Inter-system handovers for mobility to systems of higher generations (WCDMA-UMTS, LTE)

Currently, the GSM ANR module optimizes:

• GSM to GSM neighbor relations for inter-cell handovers

• GSM to WCDMA (UMTS) relations for inter-system handovers

In addition to defining relations, active and idle measurement lists are updated with:

• the appropriate BCCH (Broadcast Control Channel) for GSM neighbor relations
• UMFI (UTRAN FDD measurement frequency information) for UMTS neighbor relations

The GSM ANR module:

• detects and adds missing neighbor relations.

• evaluates existing relations for potential replacement by detected missing relations (for full neigh-
bor lists).
• automatically removes misconfigured and distant relations with poor handover success rate, to in-
crease the overall performance.
• trims GSM to UMTS relations to configured size limits per frequency layer.
• enforces operator policies for neighbor additions through LMS (Layer Management Strategy) con-
figuration.

ANR creates different push files for external cell creation (if any) and neighbor relation creation. Exter-
nal cells are a prerequisite for relation creation. Hence, in case the external cell creation fails, the push
file for neighbor creation is not provisioned.

Note:

• If relations are created manually, they will be reflected in EdenNet after a few hours. The
time taken for the relation MO update per vendor is as follows:

– Huawei: 12 hours
– Ericsson: 4 hours
– Nokia: 4 hours
– ZTE: 6 to 12 hours
• If ANR is triggered before synchronization, the module may propose the same relations
which are added manually and implementation may fail.

Supported vendors and technologies

EdenNet 21 FP 2106 © 2021 Nokia 12

GSM Automatic Neighbor Relations DN09241774 1-1 Overview of GSM ANR
Guide

Table 2: ANR 2G supported vendors and technologies lists the supported vendors and technologies.
For new cells, Nokia recommends that complete BSCs or dynamic clusters must be selected for ANR
2G target lists.

Vendor Technology

Nokia GSM

Ericsson GSM

Huawei GSM

Alcatel Lucent GSM

ZTE GSM

Table 2: ANR 2G supported vendors and technologies

Note: 2G to 3G functionality is currently not available for ALU and ZTE based networks.

2.1 GSM ANR interactions

Each cell in the network should be included in not more than one ANR closed loop instance since up-
dates of the cache for the cell in one module instance can occur in the middle of the decision making
process for the other module instance. Manual neighbor relation additions, removals, or changes from
tools outside of EdenNet should not be permitted. If manual operations are permitted, they should be
carefully planned when the ANR modules are running in closed loop in a network area. These neigh-
bor changes will not be immediately visible in the EdenNet cache. This may result in non-optimal deci-
sions in the ANR modules.

The ANR modules are the only EdenNet modules that add neighbor relations. Therefore, interactions
are not expected with other modules (in terms of neighbor additions).

EdenNet 21 FP 2106 © 2021 Nokia 13

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR functional description and
Guide guidelines

3 GSM ANR functional description and guidelines

This section provides a functional description of the GSM ANR module:

• Operational modes
• Bidirectional support
• Removal of poorly performing neighbor relations
• Neighbor trimming for GSM to UMTS relations
• Measurement based additions for GSM to GSM relations
• Cross OSS

3.1 Operational modes

The supported modes are:

• Open loop
• Closed loop

3.1.1 Open loop

In open loop mode, changes are not applied to the network. The module output consists of a report
listing the recommended neighbor relation changes to improve the network performance. The ANR 2G
module retrieves the configuration information from the EdenNet Configuration Management Cache. It
does not force any reading from the OSS for data in the cache that has been modified, or that has ex-
pired. However, any changes made by EdenNet through previous successful closed loop iterations of
the module are immediately reflected in the EdenNet Configuration Management Cache.

3.1.2 Closed loop

In closed loop mode, changes are applied to the network and the module runs only once. If repeated
executions are required, they should be run manually or scheduled.

The module attempts to process all of the cells from the list of selected cells at each execution. After
running the same algorithm as in open loop mode, the recommended changes are pushed to the live
network. Changes made by EdenNet through previous successful closed loop iterations of the module
are immediately reflected in the EdenNet Configuration Management Cache. Therefore, when Eden-
Net is solely in control of neighbor relation operations, the module always works with the latest config-
uration information. Periodic updates of relevant MOs are also performed according to the configured
schedule.

Typically, the updates are carried out:

• every hour for cell level managed objects

• every four hours for neighbor relation managed objects

EdenNet 21 FP 2106 © 2021 Nokia 14

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR functional description and
Guide guidelines

Contact Nokia technical support for the configuration details.

Note:

The ANR 2G module is iterative in closed loop mode. When the ANR 2G module is execut-
ed, it runs indefinitely (until it is manually stopped or a scheduled end-time is reached). When
the execution is complete, the ANR 2G module enters an idle state until another execution is
automatically triggered at the start of the next 15 minute period.

3.2 Bidirectional support

The ANR 2G module includes the parameter Bi-directional_Neighbors. This parameter
controls how the module handles bi-directional neighbors for GSM to GSM relations. The parameter
can take one of three values:

• True: Strictly enforces two-way neighbor relationships. If the candidate cell lies outside the
selected target list, no neighbor relation is added. This is the recommended value.
• Hybrid: Enforces two-way relations when the source and candidate cells are both within the
selected target list. If the candidate cell lies outside the selected target list, a one-way relation can
be added. Two-way neighbor relations are not enforced.
• False: Two-way relations are not enforced. All neighbor relation additions are uni-directional. If the
candidate cell lies inside or outside the selected target list, a one-way relation is added.

Nokia recommends that you set the Bi-directional_Neighbors parameter to True for the ANR
2G module. In GSM, bi-directional relations are always defined due to the single server nature of the
system. In order to prevent blocking of one way neighbor adds, the number of source cells chosen
must be large enough (at least the size of a BSC) so that reciprocal neighbors can be added.

GSM to UMTS relations are always defined only in one direction, from the GSM source cell to a UMTS
target.

3.2.1 Handling GSM-INTRA ENM neighbors

The Bi-directional_Neighbors parameter controls how the ANR 2G module handles bi-
directional neighbors for GSM to GSM relations. The possible values are:

• True
• False
• Hybrid

Table 3: GSM-INTRA ENM neighbor flow describes various scenarios considering the flow of GSM-
INTRA ENM neighbors for different settings of the Bi-directional_Neighbors parameter.

EdenNet 21 FP 2106 © 2021 Nokia 15

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR functional description and
Guide guidelines

Bi- One-way neighbor is present One-way neighbor is absent

directional_Neighbors between the candidate and between the candidate and
parameter setting source source

False Existing one way neighbor Two-way relations are not en-
relations are deleted if the forced. All neighbor relation ad-
candidate cell lies inside the ditions are uni-directional.
selected target list and two way
If the candidate cell lies inside
relations are added with the
or outside the selected target
relationDirection parameter
list, a one-way relation is added
set to MUTUAL.
with the relationDirection
If the candidate cell lies outside parameter set to SINGLE.
the selected target list, no relation
When there is a potential
is added.
neighbor candidate for a source
or when a candidate is a
potential neighbor for a source,
two way relations are added
with the relationDirection
parameter set to MUTUAL.

Hybrid Existing one way neighbor Two-way relations are not en-
relations are deleted if the forced. All neighbor relation ad-
candidate cell lies inside the ditions are uni-directional.
selected target list and two way
If the candidate cell lies inside
relations are enforced with the
or outside the selected target
relationDirection parameter
list, a one-way relation is added
set to MUTUAL.
with the relationDirection
If the candidate cell lies outside parameter set to SINGLE.
the selected target list, then no re-
When there is a potential
lation is added.
neighbor candidate for a source
or when a candidate is a
potential neighbor for a source,
two way relations are added
with the relationDirection
parameter set to MUTUAL.

True Existing one way neighbor Strictly enforces two-way neigh-

relations are deleted if the bor relationships. If the candi-
candidate cell lies inside the date cell lies outside the select-
selected target list and two way ed target list, no neighbor rela-
relations are strictly enforced tion is added.

EdenNet 21 FP 2106 © 2021 Nokia 16

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR functional description and
Guide guidelines

Bi- One-way neighbor is present One-way neighbor is absent

directional_Neighbors between the candidate and between the candidate and
parameter setting source source

with the relationDirection

parameter set to MUTUAL.

If the candidate cell lies outside

the selected target list, then no re-
lation is added.

Table 3: GSM-INTRA ENM neighbor flow

Note:

• One-way neighbor removals happen irrespective of the value of the GSM to GSM
Neighbor Deletion GUI parameter.
• For all the one-way neighbor removals, ANR 2G pushes the one-way neighbor removals
in the first plan, and the corresponding creations are pushed in the second plan.
• The ANR 2G module deletes uni-directional relations and creates bi-directional relations
as ENM does not support the conversion of uni-directional relations to bi-directional rela-
tions.

3.3 Removal of poorly performing neighbor relations

Before processing any neighbor additions, the module identifies the existing neighbor relations that
may be contributing to poor performance. These are typically distant relations which may have been
configured in error. Relations that meet a number of configured thresholds such as HO Success
Count, HO Success Rate, Tier Count, or Geo-score will be removed by the module. This feature is
available only for GSM to GSM and GSM to UMTS relations.

3.4 Neighbor trimming for GSM to UMTS relations

This optional step can be performed to ensure that GSM IRAT neighbor list sizes conform to the de-
fined limits in the module configuration.

3.5 Measurement based additions for GSM to GSM relations

Interference cannot be directly measured from the network. Instead, it can be computed indirectly from
measured field strengths. Each mobile that is connected to a cell measures the signal strengths of au-
dible cells. A mobile reports the signal strength of the 6 strongest cells. This report is sent to the BTS
and further to the controller that makes decisions on the cell to which a mobile will connect.

EdenNet 21 FP 2106 © 2021 Nokia 17

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR functional description and
Guide guidelines

In the Nokia network, there are two different measurements to collect for computing C/I:

• Channel Finder measurement (CF): measures all other cells except the cells that have been de-
fined to be adjacent to serving cells.
• Defined Adjacent Cell measurement (DAC): collects signal strength counts for the adjacent cells of
each serving cell.

Measurements can be optionally utilized by the ANR 2G module for the detection and addition of miss-
ing GSM to GSM relations. These are based on mechanisms provided by the RAN vendor to include
test BCCH in the BA-lists, and for subsequent monitoring and inclusion in the measurement reports re-
ceived from the mobiles.

Currently, the GSM ANR module supports:

• Channel Finder + Defined Adjacency PM Counters from Nokia

• BA-list recordings from Ericsson

The BA-list recordings are set up through the NCS (Neighboring Cell Support) tool in the OSS-RC.
The resulting recording files are automatically picked up by EdenNet from a common location on
the OSS.

Contact Nokia technical support for assistance with the configuration.

3.6 Cross OSS

This section describes the cross OSS support for ANR 2G.

3.6.1 Cross OSS support for ANR 2G (with NAdC)

The ANR 2G module supports the optimization of neighbor relations across OSS boundaries.

When configuring a cross OSS instance:

• Select GSM cells or BSCs that stretch over the OSS boundary.
• Send the generated plan with neighbor additions, removals, or changes to NAdC. NAdC splits the
plan per OSS and sends them to the respective OSS for provisioning.
• AC creates external cells in the source OSS, if required.

ANR 2G instances which stretch over OSS boundaries between different vendors are also supported.

To support cross OSS:

• The LMS file must contain separate LMS definitions per OSS.
• The OSS name must be specified at the beginning of each LMS configuration in the file.

The module configuration supports separate parameter settings per vendor for a few parameters.

3.6.2 Cross OSS support for ANR 2G (without NAdC)

The ANR 2G module supports the optimization of neighbor relations across OSS boundaries.

EdenNet 21 FP 2106 © 2021 Nokia 18

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR functional description and
Guide guidelines

When configuring a cross OSS instance:

• Select GSM cells or BSCs that stretch over the OSS boundary.
• Generate separate plans with neighbor additions, removals, or changes and send them to each
OSS.
• Create external cells in the source OSS, if required.

ANR 2G instances that stretch across OSS boundaries between different vendors can also be sup-
ported.

To support cross OSS:

• The LMS file must contain separate LMS definitions per OSS.
• The OSS name must be specified at the beginning of each LMS configuration in the file.

The module configuration supports separate parameter settings per vendor for a few parameters.

EdenNet 21 FP 2106 © 2021 Nokia 19

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR algorithm
Guide

4 GSM ANR algorithm

GSM ANR module optimizes neighbor relations in the GSM network.

This section describes:

• Optimization of GSM to GSM relations

• Optimization of GSM to WCDMA relations

4.1 Optimization of GSM to GSM relations

The module optimizes GSM to GSM neighbor relations for inter-cell handovers by:

• Removal of poorly performing distant neighbors for high TCH drop rate cells
• Addition of missing neighbors
• Replacement of existing neighbors

4.1.1 Removal of poorly performing distant neighbors for high TCH drop rate cells

Before processing any neighbor additions, the module identifies existing neighbor relations that may
be contributing to poor performance for high TCH drop rate cells. Neighbor relations are defined as
poor performers and removals are attempted for neighbors with the following criteria:

• Neighbor is not whitelisted.

• Tier count is greater than the threshold (for example, 10 tiers).
• Geo-score is below a threshold from source cell to target cell, and the other way around.
• Handover success rate is below a threshold (for example, 50%) and rate calculation is valid based
on a minimum number of handover attempts.

If reciprocal neighbor relations are enforced, then the module will check all the above conditions and
may also attempt to remove the reciprocal relation. If one relation cannot be removed for any of the
above reasons, then both relations are retained.

4.1.2 Addition of missing neighbors

At each execution, the module iterates over all source cells and attempts to add or replace neighbors
as required:

• Add missing whitelisted neighbors

• Add missing first tier neighbors and low TCH drop rate cell
• Add missing first tier neighbors and high TCH drop rate cell
• Add neighbor cell for high TCH drop rate cell with no missing first tier neighbors

EdenNet 21 FP 2106 © 2021 Nokia 20

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR algorithm
Guide

4.1.2.1 Add missing whitelisted neighbors

The module attempts to add all the missing whitelisted neighbors detected in each execution. If there
is no space in the neighbor list, an attempt is made to remove an existing neighbor from the list to add
the new relation.

4.1.2.2 Add missing first tier neighbors and high TCH drop rate cell

The module attempts to add all missing first tier neighbor cells. In case the source cell has a high TCH
drop rate and if there is no space in the neighbor list, an attempt is made to remove an existing neigh-
bor from the list to add the new missing first tier neighbor.

4.1.2.3 Add missing first tier neighbors and low TCH drop rate cell

The module attempts to add all missing first tier neighbor cells. In case the source cell has a low TCH
drop rate and if there is no space in the neighbor list, the existing neighbor is not removed to add the
new missing first tier neighbor.

4.1.2.4 Add neighbor cell for high TCH drop rate cell with no missing first tier neighbors

In cases where the source cell has a high TCH drop rate, the ANR 2G module attempts to add neigh-
bors that are detected as missing using measurement based methods. If measurement based neigh-
bors and missing first tier neighbors are not added, the ANR 2G module attempts to add a single
neighbor detected as missing using network topology based methods.

• Measurement based: This method is used when:

– measurements are available

– the option to use measurements in the ANR 2G module is enabled in the UI
– the measurements pass a set of data validity checks

An attempt is made to add multiple cells that show up on a significant percentage of measure-
ments (PercentReported) and/or with a percent and number of measurements (PercentExceed
and NumExceed respectively) above a threshold relative to the serving cell. The cells for addition
are sorted based on the PercentReported and then by the Cell Coupling Score. The Cell Coupling
Score is calculated using a combination of distance, tier count, and geo-scores, and the highest
ranked candidates are selected.

The candidates with the highest PercentReported (or Cell Coupling score in case of a tie) that also
meet the conditions below are selected for addition:

– (PercentReported > GSM_Meas_Percent_Reported_Threshold_For_Direct_Add)

OR ((PercentExceed > GSM_Meas_Relative_Exceedlow_Threshold) AND (NumEx-
ceed > GSM_Meas_Relative_Num_Exceedlow_Threshold) AND (PercentReported >
GSM_Meas_Percent_Reported_Threshold_For_Cell_Add))

– AND Tier count < GSM_Meas_Max_Tier_Count_For_Cell_Add

EdenNet 21 FP 2106 © 2021 Nokia 21

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR algorithm
Guide

– AND Distance between the candidate and source cell < Max_Cell_Distance_Threshold

In archipelago deployment, it is possible to have long range, long distance cells. In such
cases, though measurements are present for the adjacent cell, the GSM ANR module does
not add it as a neighbor, as it does not meet either tier criteria or distance criteria or both. The
Is_ocean_mode parameter handles such scenarios.

If Is_ocean_mode is set to True, the GSM ANR module:

• adds such an intra-frequency cell as a neighbor based only on the measurements

(ignoring the tier and distance threshold criteria).
• does not replace a long distance measurement based neighbor with any normal neighbor.

• Additional Cells - Network Topology based

When measurements are not available or do not pass validity checks then potential candidates
are ranked using the Cell Coupling score. The candidate with the highest Cell Coupling score
which also meets the conditions below is selected for addition:

– Tier count < GSM_Max_Tier_Count_For_Cell_Add AND

– Distance between the candidate and source cell < Max_Cell_Distance_Threshold

When there is no space on a neighbor list, the candidate will not be added - no replacement of existing
neighbors is performed.

If bi-directional neighbor relations are enforced then the module will attempt to also add the reciprocal
relations. Replacement of existing neighbors to make space for the reciprocal additions can occur.

For all neighbor additions, a maximum tier limit and maximum distance limit are enforced. A check is
also performed to ensure that BCCH (Broadcast Control Channel) + BSIC (Base Station Identity Code)
conflicts are not introduced.

4.1.3 Replacement of existing neighbors

Existing neighbors can be removed to create space on a neighbor list for a new cell relation. Replace-
ments are permitted for:

• Missing white-list neighbors

• Missing first tier neighbors to cells with high TCH Drop Rate
• Missing neighbors detected using measurements to cells with high TCH Drop Rate

For all other cases, the detected neighbors are only added when there is room on the neighbor list.

When replacements are permitted, a check is made to determine if there is an existing GSM neighbor
which has the same reuse code (BCCH - Broadcast Control Channel +BSIC - Base Station Identity
Code) as the candidate neighbor. If there is, the module will attempt to replace this existing neighbor
as the first choice. If not, the module will examine all existing relations for potential replacement.

EdenNet 21 FP 2106 © 2021 Nokia 22

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR algorithm
Guide

4.1.3.1 Initial replacement list

The replacement list is initialized with existing 2G>2G relations where:

• Neighbor is not whitelisted (including the global whitelist)

• Neighbor is not a first tier or co-site

4.1.3.2 Additional filtering

The neighbor replacement list is created out of existing neighbor cells that satisfy the following criteria:

• PM counter data for Handover Attempts to an existing neighbor is available (for at least
Min_KPI_Hours_Percent of the Connected mode evaluation period as configured in
the UI at module initiation)
• Number of Handover Attempts in this period is less than a defined threshold
GSM_Max_HO_Attempts_For_Neighbor_Removal
• Tier count is greater than threshold GSM_Min_Tier_Count_For_Cell_Removal (for example,
10 tiers)
• For cells where measurement data is available, the PercentReported and PercentExceed for the
existing relation is less than the threshold:

– (PercentExceed < GSM_Meas_Relative_Num_Exceedlow_Threshold) AND (PercentRe-

ported < min[GSM_Meas_Percent_Reported_Threshold_For_Cell_Add, (PercentRe-
ported of candidate cell GSM_Meas_Percent_Reported_Outperform_Multiplier)])

4.1.3.3 Ranking method for existing relations

The following method is used for ranking the remaining existing 2G>2G relations for potential replace-
ment:

• Let HO_min be the smallest number of HO Successes to a neighbor cell of the source cell in the
Connected mode evaluation period.
• Identify all neighbors with HO successes < max (HO_min+0.1*HO_min,
0.01*Total_HO_Successes), where Total_HO_Successes is the total number of
HO_Successes from the source cell.
• From the filtered neighbor list, the lowest ranked relation is:

– If measurements are available, the neighbor with the smallest PercentReported

– If measurements are not available or two or more existing relations have the same PercentRe-
ported:

• the neighbor with the highest tier count

• if two or more relations have the same high tier count then the neighbor with the lowest
Cell Coupling score

EdenNet 21 FP 2106 © 2021 Nokia 23

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR algorithm
Guide

4.1.3.4 Outperformance of candidate versus existing relations

Even if an existing relation can potentially be replaced, the candidate must still, in addition, outperform
the lowest ranked existing relation. The following outperformance criteria must be met:

For measurement based additions:

• (PercentReported for candidate cell /

(GSM_Meas_Percent_Reported_Outperform_Multiplier)) > PercentReported for existing
relations

For network topology based additions:

• (Cell Coupling score for candidate cell / (GSM_CC_Outperform_Multiplier)) > Cell Coupling
score for the existing relation

4.2 Optimization of GSM to WCDMA relations

The module processes GSM to UMTS relations per GSM source cell to each target UMTS frequency
layer.

Note: Currently, this functionality is not supported for ALU and ZTE based networks.

The module optimizes GSM to UMTS neighbor relations by:

• Removal of poorly performing distant GSM IRAT relations

• Trimming of GSM IRAT neighbors
• Addition of missing GSM IRAT neighbors
• Replacement of existing GSM IRAT neighbors

4.2.1 Removal of poorly performing distant GSM IRAT relations

Before processing any neighbor additions, the module identifies existing GSM IRAT neighbor relations
that may be contributing to poor performance. Neighbor relations are defined as poor performers and
removal is attempted for those which meet all the following criteria:

• Neighbor is not whitelisted (including the global whitelist).

• Tier count is greater than a threshold (for example, 10 tiers).
• Distance is greater than a threshold.
• Geo-score is below a certain threshold from source cell to target cell, or the other way around.
• IRAT handover success rate is below a threshold (for example, 50%) and the rate calculation is
valid based on a defined minimum number of handover attempts.

EdenNet 21 FP 2106 © 2021 Nokia 24

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR algorithm
Guide

Note: When the neighbor lists are defined only for the purpose of reselection and/or fast
return functionality, then there will not be any GSM IRAT connected mode handovers.
Therefore, neighbor removal for poor performance will not occur.

4.2.2 Trimming of GSM IRAT neighbors

This optional step can be performed to ensure that GSM IRAT neighbor list sizes conform to the de-
fined limits in the module configuration. If this option is not selected, GSM IRAT neighbor list limits will
still be optimized but they will be kept at the existing size.

The potential trim list is constructed from current IRAT neighbor cells that satisfy the following criteria:

• Neighbor is not whitelisted (including the global whitelist).

• Neighbor is not a first tier or co-site.
• Valid handover success count must be available for Min_KPI_Hours_Percent of the
Connected mode evaluation period as specified in the GUI at run-time.

This GSM IRAT neighbor list for each frequency layer (UARFCN - UTRA absolute
radio frequency channel number) is then ranked by GSM to UMTS handover success
counts (low to high), then tier count (high to low), then cell coupling score (low to high). If
GSM_IRAT_UMTS_connected_mode_ho_counts_available = FALSE, then ranking is based only
on tier count and cell coupling score.

4.2.3 Addition of missing GSM IRAT neighbors

GSM IRAT relations are only added in one direction from the source 2G cell to the target cell. At each
execution, the module iterates all the GSM source cells and attempts to add or replace neighbor rela-
tions as needed.

4.2.3.1 Add missing whitelisted GSM IRAT neighbors

The module attempts to add whitelisted GSM IRAT neighbor relations detected in each execution. If
there is no space in the neighbor list, an attempt is made to remove an existing neighbor from the list
to add the new relation.

4.2.3.2 Add missing first tier GSM IRAT neighbors

The module can enforce addition of UMTS cell relations which have been identified as missing first
tier neighbors. If there is no space in the neighbor list, an attempt is made to remove an existing GSM
IRAT neighbor from the list to add the new relation.

Note: The configured maximum number of first tiers (Absolute_1st_Tier_Maximum) ap-

plies to the total number of first tiers across all frequency layers.

EdenNet 21 FP 2106 © 2021 Nokia 25

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR algorithm
Guide

4.2.3.3 Add missing GSM IRAT neighbors based on HO Success counts

The module attempts to add all missing first tier neighbor cells. In case the source cell has a low TCH
drop rate and if there is no space in the neighbor list, the existing neighbor is not removed to add the
new missing first tier neighbor.

Additional detected neighbors are identified through handover success count based methods. Only
one method is used per source cell and target frequency layer. All candidates must meet the defined
tier count limit and distance limit thresholds for additions. When neighbor list limits are reached, an at-
tempt is made to remove an existing GSM IRAT neighbor to make way for the new relation. The meth-
ods are listed in order of preference below:

1. UMTS to GSM incoming - Used when incoming handover success counts are available in the GSM
source cell. Candidates are ranked by the incoming UMTS to GSM handover success counts. This
is the HO success score. These PM counters are normally only available for Nokia networks. Can-
didates must exceed the defined GSM_IRAT_min_2GIncoming_ho_success_for_cell_add
and gsm_irat_min_2gincoming_ho_contribution_percent_for_cell_add thresh-
olds.
2. UMTS to UMTS (co-sector 2G is source): Used when the GSM source cell has a co-sector
3G cell for the frequency layer being optimized and handover success counts for the UMTS to
UMTS intra-frequency relations are available (generally UMTS cells are available in the same
EdenNet region as the GSM source cell or else as a connected region). Candidates are ranked
based on the UMTS to UMTS handover success counts. This is the HO success score. Candi-
dates must exceed the defined gsm_irat_min_3gto3g_ho_success_for_cell_add and
gsm_irat_min_3gto3g_ho_contribution_percent_for_cell_add thresholds.
3. GSM to GSM (co-sector 3G on target): The module searches for candidates based on exist-
ing 2G neighbor relations and co-sector 3G cells to those neighbors. Candidates are ranked
based on the GSM to GSM handover success counts. This is the HO success score. Can-
didates are ranked based on the UMTS to UMTS handover success counts. Candidates
must exceed the defined gsm_irat_min_2gto2g_ho_success_for_cell_add and
gsm_irat_min_2gto2g_ho_contribution_percent_for_cell_add thresholds.

4.2.3.4 Additional detected missing GSM IRAT neighbors based on network topology

Additional candidates can then be identified based on network topology (distance, tier count, and rela-
tive antenna orientations). GSM IRAT relations are only added in one direction from the source 2G cell
to the target cell.

Note:

• Extended first tier neighbors are added when there are additional first tier neighbors out-
side the absolute first tier max count. This is a reporting categorization. In case of neigh-
bor removal between the first tier and the extended first tier, extended first tier neighbors
take precedence.

EdenNet 21 FP 2106 © 2021 Nokia 26

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR algorithm
Guide

• If the Limit_no_of_detected_neighbors parameter is set to True,

the number of topology based detected neighbors is limited based on the
Buffer_for_Detected_Neighbors parameter.

Consider the following scenario:

For cell A, there are 2 slots left. The GSM ANR module tries to fetch all the possible
candidates, evaluate them, and propose suitable relations. In this process, for a few
slots, a high number of relations are detected. This causes performance issues (when
the GSM to UMTS cell relation neighbor optimization parameter is set
to True). If the Limit_no_of_detected_neighbors parameter is set to True and
the GSM to UMTS cell relation neighbor optimization parameter is set to
True, then the GSM ANR module will detect neighbors based on the following example,
thus avoiding performance issues:

For GSM to WCDMA addition, the count of the Maximum GSM - WCDMA neighbor size
is derived from the GSM_IRAT_Neighbor_List_Size_3G_per_layer parameter
that can be added for a cell per target frequency and the count of the existing GSM -
WCDMA neighbors for a cell. The remaining neighbors are calculated by subtracting the
Max GSM - WCDMA neighbor size per target frequency and Existing neighbor per target
frequency for a cell. After the remaining neighbors are identified for GSM -WCDMA (per
frequency), the buffer is added based on the Buffer_for_Detected_Neighbors
parameter, to limit topology based detection.

For example, if the source cell has 20 GSM -WCDMA (F1) IRAT relations, the
GSM_IRAT_Neighbor_List_Size_3G_per_layer parameter is set to 32, and the
Buffer_for_Detected_Neighbors parameter is set to 20, the detected neighbors
for topology based addition are limited to:

Max GSM -WCDMA list size per target frequency - Total number of existing relations per
target frequency + Buffer for detected neighbors

32 – 20 + 20 = 32

The slot is reduced if first tier, whitelisted, or HO based detected neighbors are present.
If topology based (tier 2+) relations already exist, the slot is further reduced.

For example, consider that 5 first tier, 2 white listed, and 1 HO based detected neighbor
are present. For the same scope cell, there are 2 topology based relations which are al-
so detected. In this case, detected neighbors are:

Max GSM -WCDMA list size per target frequency – (Total number of existing relations
per target frequency + Detected 1st tier + detected whitelisted + detected HO based) +
Buffer for detected neighbors

32 – (20+5+2+1)+ 20 = 22

EdenNet 21 FP 2106 © 2021 Nokia 27

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR algorithm
Guide

It fetches 22 tier 2+ neighbors (for target frequency F1) for the scope cell. It will skip the
2 existing topology based relations. It will populate 20 topology based neighbors for the
scope cell (for target frequency F1) in the detected sheet.

4.2.4 Replacement of existing GSM IRAT neighbors

If a GSM IRAT neighbor list is already at or above the limits configured in the module, removal of an
existing neighbor can occur for any candidate missing a neighbor. A check is made to determine if
there is an existing GSM IRAT neighbor which has the same reuse code (UARFCN - UTRA absolute
radio frequency channel number + SC - Scrambling Code) as the candidate neighbor. If there is, then
the module will attempt to replace this existing neighbor first. In all cases, the candidate must outper-
form the existing relation being replaced.

4.2.4.1 Initial replacement list

The replacement list is initialized with those existing GSM IRAT relations in the frequency layer that
satisfy all of the following criteria:

• Neighbor is not whitelisted (including the global whitelist)

• Neighbor is not a first tier or co-site

4.2.4.2 Existing GSM IRAT usage threshold

The neighbor replacement list is filtered further to exclude existing GSM to

UMTS relations which are currently utilized. When the configuration parameter
GSM_IRAT_UMTS_connected_mode_ho_counts_available is true, then GSM to UMTS
neighbors which have a valid handover success count greater than the configuration parameter
GSM_IRAT_max _ho_success_for_nbr_replacement threshold are not replaced and
removed from the replacement list. Valid handover success count must be available for
Min_KPI_Hours_Percent of the specified Connected mode evaluation period.

4.2.4.3 Existing HO Success Score threshold

If the existing GSM IRAT relation is above the HO success count thresholds (in terms of both the ab-
solute count and percentage contribution) for addition as a candidate, then these are not replaced and
are removed from the list. This prevents possible oscillating additions or removals.

4.2.4.4 Ranking method

The replacement list is ranked from low to high by the number of GSM to UMTS handover success
counts. If there are multiple GSM IRAT neighbors with zero handover successes in the previous
period (for example, existing IRAT neighbor is completely unused or connected mode IRAT
handovers are not enabled), these existing GSM IRAT relations are ranked by highest tier count

EdenNet 21 FP 2106 © 2021 Nokia 28

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR algorithm
Guide

and then by lowest cell coupling score within the same tier. When the configuration parameter
GSM_IRAT_UMTS_connected_mode_ho_counts_available is false, all existing relations are
ranked by highest tier count and then by lowest cell coupling score within the same tier.

4.2.4.5 Out-performance criteria when neighbor candidate and existing neighbor have HO success
score

For GSM IRAT neighbor replacement based on the 2G <- 3G incoming method, these additional crite-
ria must be met:

• PM counter data for handover successes for the defined incoming UMTS to GSM neighbor cell
relations to the GSM cell must be available (for at least 16 of the previous 24 hours).
• Number of incoming handover successes from the IRAT candidate must
outperform the incoming handover successes from the existing IRAT neighbor by
GSM_IRAT_outperform_multiplier_HO_success.

For GSM IRAT neighbor replacement based on the 3G -> 3G (co-sector 2G is source) method, these
additional criteria must be met:

• PM counter data for the co-sited UMTS cell for intra-frequency handover successes must be
available (for at least 16 of the previous 24 hours).
• The number of intra-frequency handover successes to the candidate 3G cell must outperform the
existing IRAT neighbor by GSM_IRAT_outperform_multiplier_HO_success.

For GSM IRAT neighbor replacement based on the 2G -> 2G (co-sector 3G on target) method, these
additional criteria must be met:

• PM counter data for the GSM cell for GSM to GSM handover successes must be available (for at
least 16 of the previous 24 hours).
• Number of GSM to GSM handover successes to the candidate IRAT neighbor's co-
sector 2G cell must outperform the existing IRAT neighbor's co-sector GSM cell by
GSM_IRAT_outperform_multiplier_HO_success.

4.2.4.6 Out-performance criteria when neighbor candidate or existing neighbor do not have HO
success score

For GSM IRAT neighbor replacement based on network topology (tier count, distance and Geo-
scores) and when an existing relation does not have a HO success score, this additional criteria must
be met:

• Cell coupling score (calculated from tier count and geo-scores) for proposed neighbor addition
must exceed the cell coupling score calculated for the existing neighbor being replaced by
GSM_IRAT_outperform_multiplier_topology.

If the out-performance criteria are met then the existing GSM IRAT relation is replaced with the can-
didate. If the out-performance criteria cannot be met, the next existing GSM IRAT neighbor on the re-
placement list is tried.

EdenNet 21 FP 2106 © 2021 Nokia 29

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR algorithm
Guide

4.3 Configuring relation DN ID for Ericsson (2G)

An optional INI parameter (Configurable_relation_Id) is added. This parameter can be
configured with any combination of CM parameters to be used as the relation DN ID. At present,
this parameter is only valid for Ericsson in an AC based scenario. As this feature only deals with
configuring relation DNs (RDNs), external cells and internal cells are handled the same way. The GSM
ANR module only deals with proposing relations to external cells and not with the creation of such
cells (creation is handled by NAdC).

This parameter will be a dictionary with the following structure:

Configurable_relation_Id= {

"GSM": {

"GSM_to_GSM_relation_Id": "value",

"GSM_to_WCDMA_relation_Id": "value"

Note: The entire dictionary must be written in a single line.

The following parameters must be configured

• GSM_to_GSM_relation_Id
• GSM_to_WCDMA_relation_Id

The value of these parameters is verified when the INI file is imported into the GUI. The following are
checked in GUI validation:

• If the file is empty, an error message is displayed.

• The value of the Configurable_relation_Id parameter must be a proper dictionary. If the
structure is incorrect, an error message is displayed.
• The parameter must contain either of the following valid keys (or an error message is displayed):

– GSM_to_GSM_relation_Id
– GSM_to_WCDMA_relation_Id
• After the above conditions are verified, the parameter values are verified syntactically. An error
message is displayed if they are syntactically wrong.

The value is verified syntactically based on the following rules:

• Each CM parameter must be enclosed within angle brackets (< and >)

For example: <mcc>, <mnc>

EdenNet 21 FP 2106 © 2021 Nokia 30

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR algorithm
Guide

– The name specified within angle brackets must be a correct CM parameter name. (validated
during the GSM ANR module run)
– Any number of CM parameters can be specified in the INI parameters which may or may not
be separated by delimiters.

For example: <mcc><mnc><rncId> or <mcc>_<mnc>_<rncId>

• For 2G (OSSRC and ENM), there is a character limit of 8 characters for the RDN ID.
• Only the following delimiters can be used to separate the CM parameters placed within angle
brackets:

[ "-", "_", "+"], for example, <mcc>_<mnc>

– It is not necessary to use the same delimiter in the entire parameter value. Any combination of
delimiters can be used.

For example: <mcc>_<mnc>-<rncId>+<cellId> or <mcc>+<mnc>+<rncId>+<cellId>

– Spaces are not allowed in the configurable RDN ID.
• Other alphanumeric characters can also be mentioned in the INI parameter. The GSM ANR mod-
ule uses these characters while building the value part of the RDN:

– The alphanumeric part can be specified anywhere in the INI parameter value except in be-
tween the angle brackets.
For example: "abc<mcc>_<mnc>" or "ABC<mcc>+Qwe1<mnc>zxc"

The characters "ABC", "Qwe1", "zxc" are placed as is in their respective positions in the final
parsed value for the RDN ID.

– If the parameter contains any keys other than the specified ones (at any level), GUI validation
fails and an error message is displayed.

• The value can also be set to the instance ID of the source cell or the neighbor cell:

– For the instance id of the source cell, use <Source_Instance_Id>

– For the instance id of the neighbor cell, use <Target_Instance_Id>

If the INI file is verified and imported, the GSM ANR module searches for the configured CM parame-
ters during execution, firstly in the neighbor cell object or else in the CM cache.

If the configured CM parameters are still not found, or if the CM parameter names are incorrect, the
default values are used. The default values are different for different technologies and relation types,
as described in Table 4: Default values for relation DN IDs:

Module name Parameter name Default value Description

ANR 2G GSM_to_GSM_re- OSS RC ENM Relation ID of the

lation_Id GSM to GSM rela-
<label> <label>
tion MO.

GSM_to_WCD- <label> <label> Relation ID of the

MA_relation_Id external cell MO.

EdenNet 21 FP 2106 © 2021 Nokia 31

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR algorithm
Guide

Table 4: Default values for relation DN IDs

The following assumptions are made for this feature:

• The user must populate the config parameter in the Global section of the INI file.

• The user must configure the INI parameter with a combination of CM parameters which will
resolve to a unique value for each RDN ID as the feature does not check for uniqueness.
For example:

If the user configures the INI parameter as <mcc>_<mnc>_<rncId>, this combination is not unique
for different relations of a source cell (as all three parameters can be the same for different rela-
tions). The user needs to configure it as <mcc>_<mnc>_<rncId>_<cell_id>, as in this combination
the cell_id is unique for each neighbor of a source cell and hence it is also unique for the relation
to that neighbor.

EdenNet 21 FP 2106 © 2021 Nokia 32

GSM Automatic Neighbor Relations DN09241774 1-1 Configuring and executing GSM ANR
Guide

5 Configuring and executing GSM ANR

To configure and execute the GSM ANR module, do the following procedures in the following sequen-
tial order:

1. Accessing GSM ANR

2. Configuring targets for GSM ANR
3. Configuring parameters for GSM ANR
4. Selecting the configuration file for GSM ANR
5. Selecting the execution type for GSM ANR
6. Confirming execution for GSM ANR

5.1 GSM ANR prerequisites

To execute the GSM ANR module, the following prerequisites must be met:

• The license must be installed.

• PM counters and CM data must be available.
• Cell plan and OSS data must be available.
• The tier counting and geo-scoring options must be available.
• The LMS (Layer Management Strategy) must be defined.
• Google Chrome or Mozilla Firefox must be installed in your system.
• Cells with issues must be identified, as listed in Identify issues in cell plan and OSS data.
• CF (Channel Finder) and DAC (Defined Adjacent Cell) measurements must be checked.
• BA (Broadcast Control Channel Allocation) list recordings must be activated.

5.1.1 License
Table 5: EdenNet License lists the license required for executing the GSM ANR module.

Licensed feature com- Licensed feature compo-

LK item code LK item object name
ponent code nent name

ENSW6111CLK 2G ANR LK 0000025954 2G ANR

Table 5: EdenNet License

5.1.2 CM data and PM data

For details about the CM data and PM data of the ANR 2G module, see the below documents:

• EdenNet module specific Data for Nokia

• EdenNet module specific Data for Huawei

EdenNet 21 FP 2106 © 2021 Nokia 33

GSM Automatic Neighbor Relations DN09241774 1-1 Configuring and executing GSM ANR
Guide

• EdenNet module specific Data for Ericsson

• EdenNet module specific Data for ALU
• EdenNet module specific Data for ZTE

5.1.3 Cell plan and OSS data

The GSM ANR module requires the cell plan as well as CM and PM data for all the cells under opti-
mization (source and potential target cells):

• From the cell plan:

– Cell location, in terms of latitude and longitude (in decimal degrees)

– Neighbor cell locations, in terms of latitude and longitude (in decimal degrees)
– Cell azimuth, angle of the antenna main beam relative to a defined geo-grid reference (the
magnetic north)
– Neighbor cell azimuths, angle of the antenna main beam relative to a defined geo-grid refer-
ence
• Configuration information from the Operation Support System (OSS):

– CM data exports, including currently defined neighbors lists

Note:

For Ericsson, where GSM to UMTS relations are to be optimized, a review of the ex-
isting procedure for the creation of these relations is essential:

• Utran External Cell audit: The ANR 2G module detects missing GSM to UMTS
relations through UTRAN_EXTERNAL_CELL objects under each BSC. Ensure
that UTRAN_EXTERNAL_CELL objects for all potential UMTS relations are
present and accurate in the CNAI export from the Ericsson GSM OSS.
• RNC objects: When defining a new UTRAN_NREL for GSM to UMTS relations,
the CNAI commands generated by the ANR 2G module refer to a UTRAN_CELL
object for the target cell. These managed objects provide a higher level abstrac-
tion of the UMTS cell representations within the GSM OSS and enable automat-
ed handling of the UTRAN_EXTERNAL_CELL objects under each BSC. The
module can create new UTRAN_CELL objects, however, the parent RNC man-
aged objects must already exist in the GSM OSS for the module to operate.
• Utran External Cell names: Ensure that the CELL_NAME field in the exist-
ing UTRAN_EXTERNAL_CELL objects are unique within the OSS. When
the UTRAN_CELL objects are created, the Ericsson OSS audits the existing
UTRAN_EXTERNAL_CELL objects based purely on the matching CELL_NAME.
If multiple instances of UTRAN_EXTERNAL_CELL with the same name exist
in the OSS, then the attributes for all matching cells are updated to match the
UTRAN_CELL attributes (including the FDDARFCN, LAC and SCRCODE).

• Performance information from the OSS:

EdenNet 21 FP 2106 © 2021 Nokia 34

GSM Automatic Neighbor Relations DN09241774 1-1 Configuring and executing GSM ANR
Guide

– PM counts for handover attempts and successes per relationship

– PM counts for TCH dropped calls and TCH calls completed per cell
– PM counts for determining missing GSM to UMTS relations including:

• Incoming GSM to UMTS handover counts (if available)

• UMTS to UMTS handover counts
• GSM to GSM handover attempts and success counts
– Optional measurement data for GSM to GSM relations:

• Nokia: Channel Finder + Defined Adjacency PM Counters are supported

• Ericsson: BA-list Recordings from Ericsson are supported

Note:

• For ALU networks, PM counter data for GSM to GSM handover attempts and successes
per relationship (of type PMRES26) can typically be activated in a maximum of 40 cells
per BSC.
• Removal of existing neighbors for replacement by missing neighbors will be blocked in
cells where the PM data is not available. To ensure full functionality, including existing
neighbor replacements, the GSM ANR module can be run repeatedly on an area of one
or more BSCs but the counters must be activated in rotation to ensure coverage of all
cells.

Measurements may also be optionally utilized by the ANR 2G module. These are based on mech-
anisms provided by the RAN vendor to include test BCCH (Broadcast Control Channel) in the BA
(BCCH Allocation) lists and subsequent monitoring and inclusion in measurement reports received
from the mobiles.

For Ericsson, the Channel Finder + Defined Adjacency PM Counters from Nokia and BA-list Record-
ings are supported. The BA-list recordings are setup through the NCS (Neighboring Cell Support)
tool in the OSS-RC (Radio Configuration). The resulting recording files are picked up automatically by
EdenNet from a common location on the OSS.

For ALU, PM counter data for GSM to GSM handover attempts and successes per relationship (of
type PMRES26) can be activated in a maximum of 40 cells per BSC. Removal of existing neighbors
for replacement by missing neighbors is blocked in cells where the PM data is not available. To ensure
the complete functionality, including existing neighbor replacements, the ANR 2G module can be run
repeatedly on an area of one or more BSCs but the counters must be activated in rotation to ensure
coverage of all cells.

5.1.3.1 Identify issues in cell plan and OSS data

Table 6: Problems in cell plan and OSS data lists issues that may occur in the cell plan and OSS data
(CM export). Checks should be performed to identify cells with these issues before running the GSM
ANR module.

EdenNet 21 FP 2106 © 2021 Nokia 35

GSM Automatic Neighbor Relations DN09241774 1-1 Configuring and executing GSM ANR
Guide

Problem Description Action

Parent and child belong to Parent MO version is different Delete all plans containing the parent
different versions from the child MO version. MO from OSS or NAdC. Perform MO
upload.

SYS ID parameter is missing SYS ID or System ID repre- Perform MO upload.

in external cell sents the operating band of
external cells.

Target cell DN is missing in Target cell DN is missing from Find the target cell DN based on tar-
relation objects relation objects like ADCE, get cell parameters, for example,
ADJS, ADJI, ADJG, ADJW, MNC, MCC, eNB ID, Target RNC ID,
LNRELW, LNRELG, and so Target cell ID and so on. If target cell
on. parameters are missing, suggest or
perform MO upload.

Target cell parameters are Target cell parameters are Find the target cell parameters from
missing in relation objects missing from relation ob- the target cell DN. If the target cell
jects like ADCE, ADJS, AD- DN is missing, suggest or perform
JI, ADJG, ADJW, LNRELW, MO upload.
LNRELG, and so on.

Cells do not have cell plan If cells do not have cell plan List all the cells (with cell DN and cell
data data, those cells are incorrect- name) which do not have cell plan
ly ignored by modules. data.

External cells do not have Mandatory parameters are List all the cells which do not have
mandatory parameters missing in the external cell (for mandatory parameters.
example, RAC)

Invalid external cells in the There may be cases where Delete such external cells from the
network there is an external cell in the OSS.
network, but the actual cell for
which this external cell was
created is not available in the
network.

Table 6: Problems in cell plan and OSS data

5.1.4 Tier counting and geo-scoring

The GSM ANR module employs advanced tier counting and geo-scoring. These methods provide fun-
damental components for:

• Ensuring first tier neighbors are always defined

• Limiting neighbor additions to a specified tier threshold

EdenNet 21 FP 2106 © 2021 Nokia 36

GSM Automatic Neighbor Relations DN09241774 1-1 Configuring and executing GSM ANR
Guide

• Enabling deletion of distant or erroneous neighbors

Tier counting and geo-scoring use the cell locations and antenna information from the cell plan data.
This information is mandatory for every cell in the areas under optimization.

Tier counting identifies the number of tiers between every source cell and all neighbors or potential
neighbors (within a reasonable range). Tier counts enable a more adaptive approach for evaluating
neighbor relations when compared to pure distance thresholds, especially in transition areas of the
network, for example between cities and rural areas.

Geo-scoring is a method for quantifying the degree of radio frequency coupling or isolation between
two or more cells based on the antenna relationships between the cells of interest.

The tier count, distance, and geo-score are calculated individually, but they are also combined into a
metric called the cell coupling score.

Note:

• Distance indicates the distance between the source cell and target cell. If the source cell
and target cell have multiple antenna locations, the distance from all the antenna loca-
tions will be calculated and the minimum value will be returned.
• Tier Count indicates the tier count between the source cell and target cell. If the cell cov-
erage type is indoor, then the tier count can be +1.
• Co-site cells: all the cells that share the same site_id from cell_plan data. Tier count for
co-site cells is 1.
• Co-sector cells: Among co-site cells, all the cells that face the same azimuth direction
(+/- 20 degree) are considered as co-sector cells. For co-sector cells, the tier count is 0.
• If the source and target cells are in the same location (for example, co-site, or two sites
in the same location with different site IDs) then distance is shown as 0 in the report.

5.1.5 LMS and neighbor list sizes

When a GSM cell is processed by the GSM ANR module, its frequency layer and allowed intra tech-
nology and IRAT relations are determined based on the combination of an LMS (Layer Management
Strategy) and a module configuration file.

It is possible to define the Max Neighbor Size conditions in the LMS configuration. The permissible
relations must be defined in the LMS configuration to ensure that the LMS enforcement module does
not remove existing relations.

5.1.5.1 LMS Configuration

The LMS configuration details the frequency layers in each technology (LTE, UMTS, GSM) and the
rules for allowed neighbor definitions from each GSM frequency layer to the intra-technology and IRAT
frequency layers. The frequency layers for UMTS are defined either by pattern matching on the cell
name or else from the UARFCN (UTRA Absolute Radio Frequency Channel Number).

EdenNet 21 FP 2106 © 2021 Nokia 37

GSM Automatic Neighbor Relations DN09241774 1-1 Configuring and executing GSM ANR
Guide

It is possible to define Max Neighbor Size conditions in the LMS configuration which can be used,
for example, to:

• limit the number of GSM to GSM relations allowed between GSM bands or to limit the number of
GSM to UMTS relations allowed to a specific UARFCN.
• limit the number of GSM to UMTS relations, or limit the number of GSM to GSM relations allowed.

Note:

• While running the LMS Enforcement module on GSM cells:

– The permissible GSM to WCDMA relations must be defined in the LMS configuration
to ensure that the LMS enforcement module does not remove existing relations.
– If relations are omitted from the LMS configuration, it indicates that they are non
permissible and will be removed during closed loop operation.
• In case both LMS based trimming and GSM to UMTS cell relation trimming are True,
LMS based trimming occurs only if Max Neighbor Size exists.
• If LMS based trimming is true and Max Neighbor Size exists in the LMS, even the
first tier and co-site or co-sector relations can be removed.
• During IRAT neighbor addition, if Max Neighbor Size exists in the LMS, the module
adds relations till Max Neighbor Size reaches the target cell, irrespective of the
module configuration.

5.1.5.2 Module configuration

For GSM to GSM relations, the neighbor list size parameter defines the total number of neighbor rela-
tions allowed.

For example, GSM_Neighbor_List_Size_2g = 18. In this example, the total GSM to GSM neighbor
list size is set to 18. The number of BCCH (Broadcast Control Channel) frequencies in the BA (BCCH
Allocation) list is an important performance consideration for GSM. However, this does not equate
directly to the number of allowed neighbor relations since BCCH may be reused on this neighbor list
as long as the BCCH+BSIC (Base Station Identity Code) combinations are unique.

If there is more than one GSM band in operation, the range of BCCH values allowed is limited by the
available space in the SI2ter and SI5ter messages.

The smallest number of allowed relations to secondary band cells is 16. This occurs when the
range of BCCH values assigned (called N in the standard) is between 512 < N <= 1023 for
secondary band GSM1800 and EGSM900. To ensure that these limits are never exceeded, set
Neighbor_List_Size_2G_Secondary_Band = 16.

For GSM IRAT, the neighbor list size parameter defines the number of neighbor relations allowed with-
in each frequency layer..

For example, GSM_IRAT_Neighbor_List_Size_3G_per_layer = 15. In this example, if there are

two UMTS frequency layers, 15 relations are allowed to be defined for each of these frequency layers.

EdenNet 21 FP 2106 © 2021 Nokia 38

GSM Automatic Neighbor Relations DN09241774 1-1 Configuring and executing GSM ANR
Guide

At neighbor addition, any Max Neighbor Size conditions defined in the LMS are evaluated first and
then the module configuration limits are evaluated.

5.1.6 Check CF and DAC measurements (for Nokia vendor)

Before enabling CF (Channel Finder) and DAC (Defined Adjacent Cell) measurements, CF and DAC
usage must be enabled in the required BSCs.

The syntax of the MML command is:

WOA:<parameter class>,<parameter number>,<activation status>;

The MML command to:

• enable DAC usage in BSC is:

ZWOA:2,626,A;

• enable CF usage in BSC is:

ZWOI:10,65,FF;

• disable TOTAL_FEP measurements is:

ZWOA:2,820,D;

5.1.6.1 Activating Double BCCH Allocation list

With the Double BA (Broadcast Control Channel Allocation) list, you can define a list of BCCH (Broadcast Control Channel)
carriers to be used in cell selection and reselection by the MS (Mobile Station) while in idle state. You can also configure
measurements if the network has less than 32 BCCH frequencies.

1. Obtain information about the current IDLE list used by the BTS.

ZEQO:BTS=<source_bts_id>:BCCH

This returns a BCCH frequency list ID for the BA list used in IDLE mode.

2. Define a cell list which includes the BCCH frequencies of serving, adjacent, and dummy (non-
existing) cells using the EBC command.

ZEBC:<identification of BCCH frequency list>,<type of BCCH frequency

list>,<frequency>;

Example:

ZEBC:1,900:112&118&120; (contains parameter values)

where:

• 1 is an example of the identification of a BCCH frequency list.

• 900 indicates the type of BCCH frequency list.
• 112 is an example of the BCCH frequency of the dummy cell.
• 118 is an example of the BCCH frequency of the serving cell.

EdenNet 21 FP 2106 © 2021 Nokia 39

GSM Automatic Neighbor Relations DN09241774 1-1 Configuring and executing GSM ANR
Guide

• 120 is an example of the BCCH frequency of the adjacent cell.

3. Modify the BSC to use the created BA list in the IDLE mode.

ZEQB:BTS=<source_bts_id>:IDLE=<identification of BCCH frequency list>;

For example, if the ID of the BCCH list created above is 2:

ZEQB:BTS=<source_bts_id>:IDLE=2;

4. Modify the BTS so that active state UEs use the IDLE mode BA list for the neighbor list.

ZEQB:BTS=<source_bts_id>:ACT=IDLE;

5. Allow measurements to be collected for a period of time (2-3 days).

6. Modify the BTS so that UEs use the neighbor list again.

ZEQB:BTS=<source_bts_id>:ACT=ADJ;

7. Ensure that the BTS uses the original BA list for IDLE mode (from step 2).

ZEQB:BTS=<source_bts_id>:IDLE=identification of BCCH frequency list from

step 2>;

8. Delete the BCCH frequency list that was created.

ZEBD:<identification of BCCH frequency list>;

Expected outcome

The CF and DAC measurements are available.

5.1.7 Activate BA list recordings (for Ericsson vendor)

BA (Broadcast Control Channel Allocation) list recordings are used to collect 2G measurement data on
missing neighbors for Ericsson. There is no PM counter data available. A binary file is generated from
the recordings with an Ericsson specific format.

The BA list recordings are activated through the NCS (Neighbor Cell Support) feature in the OSS-RC
(Regional Cluster) - although MML commands on the BSC can also be used. NCS is an optional fea-
ture.

Data can be collected on a set of defined BCCH (Broadcast Control Channel) test frequencies (for 2G
> 2G definitions) or a set of defined test UMFI (UARFCN - UTRA Absolute Radio Frequency Channel
Number + SC - Scrambling Code) (for 2G > 3G definitions). The NCS feature includes a BA-list rota-
tion functionality to ensure that the mobiles are instructed to measure on all available BCCH (Broad-
cast Control Channel) or all available UMFI at some point in the rotation cycle. The user specifies
the range of BCCH or UMFI in the NCS recording function along with other parameters such as the
recording duration.

General recording parameters are:

EdenNet 21 FP 2106 © 2021 Nokia 40

GSM Automatic Neighbor Relations DN09241774 1-1 Configuring and executing GSM ANR
Guide

• A set of GSM cells on which the recording will be executed. A cell set may contain cells from more
than one BSC.
• A time schedule that defines when recordings should be made.
• The length of recording segments which indicate how often the test frequency numbers in the
Active BA list should be changed. This value applies both to the GSM Active BA-list and the 3G
Active BA-list.
• Automatic export of all results might be executed.

GSM specific recording parameters are:

• The GSM test frequencies that will be recorded

• Relative signal strength thresholds (at a minimum of 0 dB thresholds)
• An absolute signal strength threshold
• The maximum number of GSM test frequencies that may be added to the active mode BA lists at
one time
• Multi Band Cell Offset (this field is only present if the Multi Band Cell feature is used)

WCDMA recording parameters are:

• Number of WCDMA cells in each measurement report

• An absolute Ec/No threshold
• The maximum number of test UMFIs that may be added to the 3G active mode BA lists at one
time
• A set of test UMFIs that will be used in the recording

The resulting binary files are called BARFIL. The files are retrieved by the OSS from each BSC and
stored at:

/var/opt/ ericsson/brf/data/db/ tmpfileStore/ "bscName"

Then, the binary files are picked up by the OSS for processing and presentation. Actions are taken, if
required.

5.2 Accessing GSM ANR

To perform any action on a module, you must log in to the EdenNet application and access the module.

Prerequisites

• All the prerequisites mentioned in the GSM ANR prerequisites section must be met.

1. Log in to the EdenNet application:

a) In the address field of your Internet browser, type the following URL (for 2VM, 5VM, and cross-
OSS):

https://<EdenNet GUI_SERVERS IP>

where <EdenNet GUI_SERVERS IP> is the IP address of the GUI server.

EdenNet 21 FP 2106 © 2021 Nokia 41

GSM Automatic Neighbor Relations DN09241774 1-1 Configuring and executing GSM ANR
Guide

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 SON Activity page appears.

2. Click the Configure tab.

The following module categories appear in the left pane:

• 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.

3. From the EdenNet modules category, select ANR_2G.

Expected outcome

The ANR_2G module is accessed and the Configure Targets page appears.

4. Continue with Configuring targets for GSM ANR.

5.3 Configuring targets for GSM ANR

In EdenNet, a module can only be configured and executed on a cluster of cells. In the Configure Targets page, you can select
cells on the map.

Prerequisites

• Successful completion of Accessing GSM ANR.

EdenNet restricts the module to making changes only to those cells selected by the user. Entire RNCs
and dynamic clusters can also be selected. When running the module with strict enforcement of
bidirectional neighbor relations, changes will not be made to cells unless the reciprocal neighbor cell is
also in the list of cells to be optimized.

Note: When running multiple instances of the ANR_2G module, users should ensure that the
selected cells will only be part of one module instance execution.

1. Select the cells for configuration by:

• filtering specific cells on the map based on Topology Filter or Center Frequency Filter and
then selecting target cells from the map.
Or

EdenNet 21 FP 2106 © 2021 Nokia 42

GSM Automatic Neighbor Relations DN09241774 1-1 Configuring and executing GSM ANR
Guide

• filtering specific cells on the map based on Topology Filter or Center Frequency Filter and
then selecting all filtered items by clicking .
Or

• using the cell ID search selection tools from the map toolbar.
Or

• selecting existing clusters.

Target cells are selected and shown in the Selection pane. For more information about selecting
cells, see the Selecting cells section in the EdenNet User and Administration Guide.

Note: A module may retrieve configuration and performance information for other cells
in the network that are not on the target list. For many modules, this information may
be required by the modules core algorithms. Multiple instances of the module, each
with its own target cell list are permitted and are necessary for large OMCs or OSS
configurations.

2. Click Next.

Expected outcome

The target cells are selected and the Configure Parameters page appears.

3. Continue with Configuring parameters for GSM ANR.

5.4 Configuring parameters for GSM ANR

To execute a module, you must configure a set of parameters. In the Configuration Parameter page, a list of parameters,
along with the descriptions and default values are displayed.

Prerequisites

• Successful completion of Configuring targets for GSM ANR.

1. Define the configuration parameter values. For the list of parameters, see GSM ANR GUI
parameters.

You can retain the default values or select the values from the drop-down list.

To revert to the default parameter value, click the Default Value icon.

2. Click Next.

EdenNet 21 FP 2106 © 2021 Nokia 43

GSM Automatic Neighbor Relations DN09241774 1-1 Configuring and executing GSM ANR
Guide

Expected outcome

The parameters are configured and the Select Configuration File page appears.

3. Continue with Selecting the configuration file for GSM ANR.

5.5 Selecting the configuration file for GSM ANR

You can select configuration files from the list of available configurations.

Prerequisites

• Successful completion of Configuring parameters for GSM ANR.

• Ensure that the required configuration files are activated. For more details, see Configuring INI pa-
rameters.

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. Click Next.

Expected outcome

The configuration file is selected and the Execution Type page appears.

3. Continue with Selecting the execution type for GSM ANR.

5.6 Selecting the execution type for GSM ANR

In the Execution Type page, you can schedule when the module must be executed. Depending on the type of execution, such
as immediately, later, or during a specific date and time, the module is scheduled and executed.

Prerequisites

• Successful completion of Selecting the configuration file for GSM ANR.

1. To schedule the module execution, select one of the following options:

• Execute Now - to execute the module immediately.

• Execute Later - to execute the module at a later time.
• Schedule Execution - to schedule the module for execution during a certain date and time.

EdenNet 21 FP 2106 © 2021 Nokia 44

GSM Automatic Neighbor Relations DN09241774 1-1 Configuring and executing GSM ANR
Guide

For more information about scheduling the execution, see the Configuring execution type section
in the EdenNet User and Administration Guide.

2. Click Next.

Expected outcome

The module is scheduled for execution and the Confirm Execution page appears.

3. Continue with Confirming execution for GSM ANR.

5.7 Confirming execution for GSM ANR

In the Confirm Execution page, you can view the summary of the operation setup and start the operation. The operation is
executed as per the defined schedule.

Prerequisites

• Successful completion of Selecting the execution type for GSM ANR.

Procedure

• Verify the configuration summary and click Finish.

You can monitor the activities, status, and events of the ANR_2G module. For more information,
see Monitoring GSM ANR.

Expected outcome

The ANR_2G module is executed based on the configured parameters and as per the defined
schedule.

5.8 ENM GSM BA list and UMFI list updates

In Ericsson ENM GSM, the Broadcast Control Channel Allocation (BA) lists and UTRAN FDD Mea-
surement Frequency Information (UMFI) lists are updated after every relation optimization.

Note:

• In case of plan provisioning failure of the BA lists or the UMFI lists, a roll-back attempt is
made by the ANR 2G module.
• The BA lists and UMFI lists are updated only for those cells that are optimized by ANR
2G. The lists are not updated if the relations are added manually without using the ANR
2G module.

EdenNet 21 FP 2106 © 2021 Nokia 45

GSM Automatic Neighbor Relations DN09241774 1-1 Configuring and executing GSM ANR
Guide

5.8.1 BA list updates

In Ericsson ENM, for every GSM INTRA relation optimization within the selected scope, ANR 2G up-
dates the corresponding BA active and idle lists.

5.8.2 UMFI list updates

In Ericsson ENM, for every GSM IRAT relation optimization within the selected scope, the ANR 2G
module updates the corresponding UMFI active and idle lists. UTRAN FDD neighboring cells are
identified by the combination of frequency, scrambling code, and diversity. The UMFI_diversity
parameter is used to define whether or not diversity is applied to a UTRAN cell.

Note: The UMFI lists are updated only when the Perform GSM to UMTS cell
relation optimization parameter is set to Enabled.

EdenNet 21 FP 2106 © 2021 Nokia 46

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

6 GSM ANR configuration parameters

A set of parameters are required to run a module. Module parameters are configured through:

• Graphical user interface (GUI)

• INI file

6.1 GSM ANR GUI parameters

The GUI parameters of the GSM ANR module are described in Table 7: GSM ANR GUI configuration
parameters.

Range (Min, Default val-

Parameter Description Step
Max) ue

Connected mode The number of GSM to GSM and 1 to 14 1 7

evaluation period GSM to UMTS connected mode
handover success counts over this
evaluation period that are used in
the evaluation of existing neigh-
bors for all removal scenarios such
as poorly performing, trimming of
GSM>UMTS, unused, and so on.
Unit is days.

Perform GSM to Enables or disables all GSM to Enabled, Dis- N/A Enabled
GSM cell relation GSM cell relation operations. abled
operations

GSM to GSM cell re- Set to True to perform removal of True, False N/A True
lations remove dis- distant poorly performing GSM >
tant poor performers GSM relations according to config-
ured thresholds.

GSM to GSM cell re- Set to True to perform optimization True, False N/A True
lation neighbor opti- (addition/replacement) of GSM >
mization GSM relations according to config-
ured settings.

GSM to GSM cell Depending on availability, the use True, False N/A False
relations use mea- of BA-list recording type measure-
surements ments for detecting missing GSM
to GSM relations may or may not
be active in the operator's network.

EdenNet 21 FP 2106 © 2021 Nokia 47

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range (Min, Default val-

Parameter Description Step
Max) ue

If this parameter is set to True,

such measurements, when avail-
able, are used to augment GSM to
GSM relation optimization. If the
measurements are missing, or da-
ta validity criteria are not met for a
source cell, the module falls back
to using network topology meth-
ods.

If this parameter is set to False,

the module never attempts to use
such measurements.

The supported vendors are Nokia

and Ericsson.

GSM to GSM Neigh- Applicable only for GSM targets. Disabled, Al- N/A Disabled
bor Deletion Setting this parameter to Disabled lowed
prevents the deletion of neighbors
including distant poor performers.
Neighbor relations blacklisted from
the UI can be removed indepen-
dently and are not dependent on
this parameter.

Perform GSM to Enables or disables all GSM to Enabled, Dis- N/A Disabled
UMTS cell relation UMTS cell relation operations. abled
operations

GSM to UMTS cell Set to True to perform removal True, False N/A True
relations remove of distant poorly performing
distant poor per- GSM>UMTS relations according to
formers configured thresholds.

GSM to UMTS cell Set to True to perform trimming of True, False N/A True
relations trimming GSM>UMTS relations according
to the module configured neighbor
list size limits per UMTS frequency
layer.

GSM to UMTS cell Set to True to perform optimiza- True, False N/A True
relation neighbor op- tion (addition or replacement) of
timization

EdenNet 21 FP 2106 © 2021 Nokia 48

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range (Min, Default val-

Parameter Description Step
Max) ue

GSM>UMTS relations according to

the configured settings.

Addition of neighbor relations

which are whitelisted from the UI is
independent of this parameter.

If GSM>UMTS connected mode

handover counts are not avail-
able, the removal of existing
GSM>UMTS neighbors to be re-
placed by detected neighbors are
based on outperformance crite-
ria only. If GSM>UMTS connected
mode handover counts are avail-
able, the removal of existing neigh-
bors is additionally restricted by the
configured GSM>UMTS success
count threshold.

Enforce_LMS_Size_ With this function enabled, neigh- True, False N/A False
For_Existing_Neigh- bor lists are trimmed according to
bors the maximum neighbor size de-
fined in the LMS configuration for
specific layer to layer transitions.
The number of relations in sub-
set conditions are checked and re-
movals are performed before high-
er level set conditions are checked.
This function is used in the roll-out
phase for a new LMS.

SON Operation Set to Open Loop to run the mod- Open Loop, N/A Open Loop
Mode ule in open loop mode. Set to Closed Loop
Closed Loop to run the module in
closed loop mode. In Closed Loop
mode, changes are automatically
pushed to the network without user
intervention. In Open Loop mode,
the module does not automatical-
ly push parameter changes to the
network. The user has to manually

EdenNet 21 FP 2106 © 2021 Nokia 49

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range (Min, Default val-

Parameter Description Step
Max) ue

provision plans to push changes to

the network.

Plan Name Tag Text that will be added to the Sequence which N/A Empty
names of all the plans that will be contains any
generated by this module. If the combinations of:
target of the module is a whole
• Uppercase
specific cluster (and the name
and lower-
of this cluster also matches the
case letters:
Range), then the cluster name will
[A-Za-z]
also be added to the plan name.
• Numbers:
[0-9]
• Underscore:
_

The maximum
length is 20
characters.

Table 7: GSM ANR GUI configuration parameters

6.2 GSM ANR INI parameters

This section describes:

• Common configuration file parameters

• Baseline configuration file parameters
• GSM to GSM measurement based detection parameters
• GSM to UMTS configuration file parameters
• Example of GSM ANR configuration file

Note:

The ANR 2G module supports providing different values for the same module INI parameters
(for different vendors) by defining a vendor section in the module configuration INI file. If the
parameter value is not specified within the respective vendor section, the corresponding val-
ue mentioned in the global section will be returned. If the parameter is not mentioned in the
global section and in the vendor section, or if it is not defined in the configuration file, the de-
fault value will be used.

The parameters that support this feature are listed below:

• GSM_Neighbor_List_Size_2G

EdenNet 21 FP 2106 © 2021 Nokia 50

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

• GSM_IRAT_Neighbor_List_Size_3G_per_layer
• GSM_IRAT_Max_3G_Frequencies

There are no changes to their respective functionalities.

6.2.1 Common configuration file parameters

Table 8: Common configuration file parameters lists the common configuration file parameters.

Range Default val-

Parameter name Parameter description Step
(Min, Max) ue

Min_KPI_Hours_Per- Used together with the GUI 0 to 100 1 75

cent parameter Connected mode
evaluation period for GSM
to GSM relations and GSM to
UMTS relations.

Defines the minimum percentage

of data required over the
configured evaluation period
to permit deletion of relations.
For example, if Connected
mode evaluation period = 7 and
Min_KPI_Hours_Percent =
75%, then at least 126 hours of
handover success count data
must be available over a 7 day
period for removals of existing
GSM to UMTS relations to be
permitted.

Absolute_1st_Tier_ Defines the maximum number 0 to 20 1 8

Maximum of relations classified as first tier
for the algorithm. Additional first
tier relations are classified as ex-
tended first tier. For IRAT, the lim-
it applies to the sum of relations
across all frequency layers (UAR-
FCN).

Extended_1st_Tier_ Defines the maximum allowed dis- 1 to 100 1 40

Distance_Threshold tance for relations to be classified
as first tier for the algorithm. Addi-
tional first tier relations are classi-

EdenNet 21 FP 2106 © 2021 Nokia 51

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range Default val-

Parameter name Parameter description Step
(Min, Max) ue

fied as extended first tier. Unit is

kilometers.

Maximum_Cell_Dis- Proposed neighbor addition must 1 to 100 1 25

tance_Threshold be within this distance. Keep-
ing this parameter to a high val-
ue allows neighbors with low tier
counts but high distance in rural
areas to be added. Unit is kilome-
ters.

Bi-directional_Neigh- When set to True, bi-directional True, False Hybrid True

bors neighbor relations are enforced.
Whenever the module adds or
deletes a relation, it will enforce
the addition or deletion of the reci-
procal relation. True is the recom-
mended setting for GSM.

With a setting of Hybrid, relations

can be added or removed to cells
outside the target list, creating one
directional neighbors. With a set-
ting of False, each single direc-
tion addition or deletion is evaluat-
ed independently. Hybrid or False
settings are not recommended for
GSM.

Max_Num_Changes_ Maximum number of neighbors to 1 to unlimited 1 500

To_Push push to the network at each exe-
cution of the module.

Additional_Logging Additional information is logged if True, False N/A False

this parameter is set to True. Addi-
tional logs are mainly used for de-
bugging purposes. They include
internal parameters which cannot
be modified and are displayed in
the parameter sheet of the report.

EdenNet 21 FP 2106 © 2021 Nokia 52

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range Default val-

Parameter name Parameter description Step
(Min, Max) ue

tabs The ANR_2G module generates • Parameters N/A Default tabs

the following sheets in the output • Final Neighbors are:
report: • Detected Neigh- • Para-
• Parameters bors meters

• Final Neighbors • Changes • Changes

• Detected Neighbors • DCR Report • Logs

• Changes • HO Report • De-

• DCR Report • Reuse Conflicts tected

• Neighbor Perfor- Neigh-
• HO Report
mance bors
• Reuse Conflicts
• Logs • Reuse
• Neighbor Performance
• Disambiguation Con-
• Logs
flicts
• Disambiguation • BA <vendor_
name> List Mea-
• BA <vendor_name> List Mea-
surements
surements
• Cell Level Sum-
• Cell Level Summary
mary
• BA-List
• BA List Updates
• UMFI
• UMFI List Up-
dates

Label_type_for_Erics- Indicates the type of label used to CELL_NAME N/A CELL_

son_cells display the cell nomenclature in NAME
USERDATA
the XLS reports. The allowed val-
ues are CELL_NAME, USERDA- USERLABEL
TA, and USERLABEL.

Changes are reflected in the fol-

lowing columns:

• Source Cell and Target Cell in

the Changes sheet
• Source Cell Name, Target Cell
Name, and UserLabel in the
HO Report sheet

Use_userSpecificInfo_ If set to True, the userSpecificIn- True, False N/A False

for_ALU_cells fo value is used to display the cell
nomenclature in the XLS report. If

EdenNet 21 FP 2106 © 2021 Nokia 53

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range Default val-

Parameter name Parameter description Step
(Min, Max) ue

set to False, the default cell label

is used.

Changes are reflected in the fol-

lowing columns:

• Source Cell and Target Cell in

the Changes sheet
• Source Cell Name, Target Cell
Name, and UserLabel in the
HO Report sheet

Module_log_level This parameter controls the log- INFO N/A INFO

ging level at which you can view
DEBUG
the log statements.

Optimize_Final_ This parameter indicates whether True, False N/A False

Neighbors or not to optimize the final
neighbors. If it is set to True, the
final neighbor is only populated
with the optimized cells. If it is
set to False, the final neighbor
is populated with all the cells
in the scope. This parameter
is considered only when Final
Neighbors is added to the tabs
INI parameter.

Exclude_outdoor_ When this parameter is set to True, False N/A False

cells True, outdoor cells are excluded
from tier based intra, inter, and
IRAT neighbor relation addition
for an indoor source cell, but they
will be included in measurement
based neighbor relation addition.

Exclude_indoor_ cells When this parameter is set to True, False N/A False
True, indoor cells are excluded
from tier based intra, inter, and
IRAT neighbor relation addition
but they are still included in mea-
surement based neighbor relation
addition.

EdenNet 21 FP 2106 © 2021 Nokia 54

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range Default val-

Parameter name Parameter description Step
(Min, Max) ue

Enable_first_tier_adds Enables or disables enforcement True, False N/A True

of first tier neighbors for both Intra
and IRAT relations.

Note: As this parameter

is applicable to both In-
tra and IRAT relations,
there will be no case
where first tier adds are
enabled/disabled only
for IRAT or only for In-
tra.

If this parameter is
disabled, measurement
based addition must be
enabled by setting the
GSM to GSM cell
relations use
measurements GUI
parameter to True.

TimeBetweenPushes_ This parameter extends the time 0 to 96 1 1

15Mins between pushes by preventing
new module executions based on
the time that has expired since the
last push (rounded down to the
last 15 minute period).

For example: A setting of 4 in-

dicates four 15 minute periods.
Therefore, the module execution
is allowed to proceed only if more
than 1 hour has elapsed from the
time of the last push.

For a setting of 4, consider that

the module begins execution at
3:00 and ends at 3:10. The mod-
ule is then idle until 3:15, which is
taken as the first 15 minute peri-
od. The next three 15 minute pe-

EdenNet 21 FP 2106 © 2021 Nokia 55

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range Default val-

Parameter name Parameter description Step
(Min, Max) ue

riods are at 3:30, 3:45 and 4:00.

Hence, the module begins its next
iteration at 4:00.

Setting the value of this parameter

to 0 triggers the module only one
time.

global_white_list Enables a list of cells to be en- N/A N/A N/A

tered. These cells are never re-
moved from a source cell. The
syntax is:

List of cells format:

[MCC, MNC, LAC, CI]

For example:

global_white_list =
[[300, 221, 63999,
64000],[300, 221, 63999,
64000]]

Contact Nokia technical support

for assistance in configuring glob-
al white lists.

global_white_list_plu- Enables you to filter the cells N/A N/A N/A

gins which should not contain global
whitelisted cells. The plug-in op-
tions are:

• band_filter: It takes JSON as

a value. For example:

{<source_band>:
[<target_allowed_
band>, ...]}

It is a plug-in that filters out

any cells that are not specified
as allowed bands in the con-
figuration file.

• neighbor_type_filter: The val-

ue can be intra, inter, or IRAT.

EdenNet 21 FP 2106 © 2021 Nokia 56

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range Default val-

Parameter name Parameter description Step
(Min, Max) ue

It is a plug-in that filters out

any cells that are not specific
neighbor types.

For example: global_white_

list_plugins = ["neighbor_
type_filter", ["intra"]]

• label_ref_match: It takes a
regular expression as a val-
ue. It is a plug-in that trims all
the cells that do not match a
source cell name.

Note: The regular

expression must be
a string based regu-
lar expression.

For example: Consider

three source cells from OSS
- AAA123, BBB123, and
RAA123. If the plug-in is
defined as "label_ref_
match:"^R.*3$",

it creates a whitelist for

RAA123 but filters out
AAA123 and BAA123.

Example usage:

global_white_list_
plugins = [["label_
ref_match", ".*"]]

Note:

If multiple plugins
are used in the con-
figuration file, then
the plugin that is ini-
tialized last is con-

EdenNet 21 FP 2106 © 2021 Nokia 57

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range Default val-

Parameter name Parameter description Step
(Min, Max) ue

sidered as the glob-

al_whitelist_plugin.

Contact Nokia technical

support for further assistance
in configuring the global_
white_list_plugins.

Note: The list of valid

bands accepted by
band_filter are:

• GSM900
• GSM High Band
• GSM1800
• DCS1800
• GSM850
• GSM1900
• PCS1900
• EGSM900

Is_ocean_mode This parameter indicates whether True, False N/A False

or not the current deployment is
an ocean mode deployment. In
ocean mode, the GSM ANR mod-
ule considers long distance neigh-
bor addition and ignores the dis-
tance and tier count between the
source and target cells.

Note: If this parame-

ter is enabled, distant
neighbors are preferred.

Configurable_rela- Indicates the relation ID (RDN val- N/A N/A The default
tion_Id ue) of a relation MO. value is dif-
ferent for
For details on how to configure
different re-
the parameter, see Configuring re-
lation types
lation DN ID for Ericsson (2G).
and tech-
nologies.

EdenNet 21 FP 2106 © 2021 Nokia 58

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range Default val-

Parameter name Parameter description Step
(Min, Max) ue

For more in-

formation,
see the De-
fault values
for relation
DN IDs for
GSM ANR
table in the
Configuring
relation DN
ID for Eric-
sson (3G)
section.

PPS_Retry This parameter controls whether True, False N/A False

the plan can be split and re-provi-
sioned.

Set this parameter to True to

trigger the plan split and re-
provision.

Note: CM split plan fea-

ture supports both acti-
vation and validation for
the following vendors:

• Nokia
• Ericsson (ENM on-
ly)

PPS_Number_of_re- This parameter controls the num- 3 to 10 1 3

tries_of_provision ber of times that a plan can be re-
tried and provisioned.

PPS_Time_between_ This parameter specifies the Positive integer N/A 5

retries_in_minutes amount of time to wait after a retry
plan is created and the previous
provision has been completed. It
is specified in minutes.

EdenNet 21 FP 2106 © 2021 Nokia 59

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range Default val-

Parameter name Parameter description Step
(Min, Max) ue

PPS_Exclude_criteria This parameter specifies the con- • exclude_ mo_ N/A exclude_
dition based on which the retry from_ plan cell_from_
plan is created: • exclude_cell_ plan

• exclude_MO_from_plan: from_plan

Removes MO instances • exclude_con-

(based on the DN) that were troller_from_plan
reported with failures during • STOP
plan validation.
• exclude_cell_from_plan:
Applicable for changes being
performed at the cell level or
for the sub-tree under the Cell
object in the object model.

In case of failures of any MO

instance, remove from the
plan all the MO instances un-
der the parent cell object.
• exclude_controller_
from_plan: For each failure
in the validation phase,
remove all changes under
the corresponding network
element (node). A network
element corresponds to BSC
for 2G, RNC for WCDMA,
eNB for LTE and gNB for 5G.
• STOP: Stops CM plan split
if there is validation failure.
Retries all failed MOs if there
are activation failures.

validation_workflow_ This parameter enables or dis- True, False N/A False

enabled ables the validation workflow.

If this parameter is set to True,

the validation workflow is enabled.
If this parameter is set to
False, the validation workflow is
disabled.

EdenNet 21 FP 2106 © 2021 Nokia 60

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range Default val-

Parameter name Parameter description Step
(Min, Max) ue

Note: : Nokia
recommends that this
parameter must be
set to True if plan
provisioning is failing
due to validation errors
such as:

• wrong parameter
values
• creation of existing
managed objects
• deletion of non-
existing managed
objects

Table 8: Common configuration file parameters

Note: Table 9: Module behavior for Exclude indoor cells and Exclude outdoor cells parame-
ters lists the behavior of Exclude indoor cells and Exclude Outdoor cells para-
meters when they are set to True.

Scope cell Target cell Addition

Outdoor Cell Outdoor Cell No restriction

Outdoor Cell Indoor Cell Measurement based addition

only

Indoor Cell Indoor Cell Measurement based addition

only

Indoor Cell Outdoor Cell Measurement based addition

only

Table 9: Module behavior for Exclude indoor cells and Exclude outdoor cells parameters

6.2.2 Baseline configuration file parameters

Table 10: Baseline configuration parameters lists the baseline configuration file parameters.

EdenNet 21 FP 2106 © 2021 Nokia 61

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range (Min, Default

Parameter name Parameter description Step
Max) value

GSM_DCR_Thresh- Determines if the cell is classified as a 0.1 to 10 0.1 4.0

old high TCH drop call rate cell along with the
dropped call rate threshold.

GSM_Min_TCH_ Determines if the cell is classified as a 0 to 50 1 5

Drops_For_High_ high TCH drop call rate cell along with the
Drop_Rate_Calcula- absolute number of TCH drops.
tion

GSM_HO_Success_ Used as one of the conditions to identify 0 to 100 10 50

Rate_Threshold_For_ poorly performing neighbor relations for
Poorly_Performing_ high TCH drop call rate cells. The han-
Cell_Removal dover success rate must be below this
threshold for removal.

GSM_Min_HO_At- Used when identifying poorly perform- 1 to any posi- 1 50

tempts_For_Poorly_ ing neighbor relations for high TCH drop tive integer
Performing_Cell_Re- rate cells. It checks whether the calculated
moval handover success rate is based on a rea-
sonable number of handovers.

GSM_GeoScore_ Used as one of the conditions to identify -1 to 1 0.1 -0.5

Threshold_For_Poor- poorly performing neighbor relations for
ly_Performing_Cell_ high TCH drop rate cells. Both source to
Removal target and target to source geo-score must
be below this threshold for neighbor re-
moval.

GSM_Min_Tier_ The tier count for the poorly performing re- 2 to 10 1 10

Count_For_Poorly_ lation must be at or above this threshold
Performing_Cell_Re- for removal to be allowed.
moval

GSM_minimum_tier_ Intra neighbor relations with tier count 2 to 10 1 10

count_for_intra_cell_ equal to or greater than the defined value
removal are considered for removal.

GSM_Neighbor_List_ The maximum allowed neighbor list size. 5 to 32 1 18

Size_2G The neighbor list is considered full when
this limit is reached.

Neighbor_List_Size_ The maximum allowed neighbor list size 5 to 32 1 16

2G_Secondary_Band for secondary band relations. The smallest
number of allowed relations to secondary

EdenNet 21 FP 2106 © 2021 Nokia 62

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range (Min, Default

Parameter name Parameter description Step
Max) value

band cells is 16 when the following condi-

tions are satisfied:

• the range of BCCH values assigned

(called N in the standard) for the sec-
ondary band is GSM 1800 and EGSM
900
• the range is between 512 < N <= 1023

GSM_Max_HO_At- Used for removal of neighbors for replace- 0 to any posi- 1 0

tempts_For_Neigh- ment by a candidate neighbor. The neigh- tive integer
bor_Removal bor cannot be removed if the number of
handovers is above this threshold.

GSM_Max_Tier_ Cells can only be added as neighbors at 1 to 10 1 2

Count_For_Cell_Add this tier count or below.

GSM_ CC_Outper- Cell-coupling score of the candidate cell 1 to 5 0.1 1.0

form_Multiplier must exceed the cell-coupling score for the
neighbor cell score by this factor to allow
replacement.

GSM_C1 Used in calculating the cell coupling score 0 to 4 0.5 2.0

for neighbor ranking.

Note: The GSM_C1, GSM_C2,

GSM_C3, and GSM_C4 para-
meters should only be modified
under the guidance of the Nokia
technical support team.

GSM_C2 Used in calculating the cell coupling score 0 to 1 0.2 0.0

for neighbor ranking. Higher values of this
parameter increase the weight of neigh-
bors with lower tier counts.

GSM_C3 Used in calculating the cell coupling score 1 to 2 0.2 1.0

for neighbor ranking. Higher values of this
parameter reduce the weight of neighbors
with lower tier counts.

GSM_C4 Used in calculating the cell coupling score 0 to 2 0.2 1.0

for neighbor ranking. Higher values of this
parameter increase the weight of neigh-

EdenNet 21 FP 2106 © 2021 Nokia 63

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range (Min, Default

Parameter name Parameter description Step
Max) value

bors with lower tier counts. Setting the val-

ue to zero means the tier count is ignored.

Optimize_Detected_ This parameter indicates whether or not to True, False N/A False
Neighbors optimize a detected neighbor:

• If this parameter is set to True, all the

detected neighbors are reported for
topology or measurement based addi-
tion.
• If this parameter is set to False, only
the detected neighbors which are pro-
posed for addition are reported.

This parameter is considered only when

Detected Neighbors is added to the tabs
INI parameter.

Table 10: Baseline configuration parameters

6.2.3 GSM to GSM measurement based detection parameters

Table 11: GSM to GSM measurement based detection parameters lists the GSM to GSM measure-
ment based detection parameters.

Range (Min, Default

Parameter name Parameter description Step
Max) value

GSM_Meas_Max_ Number of tiers below which a cell 1 to 20 1 5

Tier_Count_For_ can be considered a valid neigh-
Cell_Add bor candidate.

GSM_Meas_Rel- Cells with PercentExceed- 0 to 100 0.1 1

ative_Exceedlow_ LowThresh above this threshold
Threshold can be considered as candidate
cells for neighbor addition.

GSM_Meas_Rela- Cells with NumExceed- 0 to 10,000 10 100

tive_Num_Exceed- LowThresh above this threshold
low_Threshold can be considered as candidate
cells for neighbor addition.

GSM_Meas_Per- Cells with PercentReport- 0 to 100 0.1 50

cent_Reported_ ed above this threshold can be

EdenNet 21 FP 2106 © 2021 Nokia 64

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range (Min, Default

Parameter name Parameter description Step
Max) value

Threshold_For_Di- considered as candidate cells for

rect_Add neighbor addition.

GSM_Meas_Per- Cells with PercentReport- 0 to 100 0.1 10

cent_Reported_ ed above this threshold cab be
Threshold_For_ considered as candidate cells for
Cell_Add neighbor addition in combination
with other conditions.

GSM_Meas_Per- Multiplication factor by which the 0.1 to 20 0.1 5

cent_Reported_ candidate cell's PercentRe-
Outperform_Multi- ported value should exceed
plier an existing neighbor cell Per-
centReportedNbr value for the
neighbor to be considered for re-
moval.

GSM_Disambig_ For a specific BSIC-BCCH com- 1 to 10 1 3.0

Coupling_Score_ bination, multiplication factor by
Outperform_Multi- which a candidate cell's coupling
plier score should exceed the cou-
pling score of a second candidate
cell to be disambiguated as the
source of the BSIC-BCCH value.

GSM_Meas_BAL_ The number of BAL rotation cy- 1 to 50 1 1

Rotation_Cycles cles. It is used to normalize mea-
surements if measurement fre-
quencies need to be configured in
multiple BA lists which are rotated
in the network. Currently, this pa-
rameter is only used for Nokia.

GSM_Meas_Peri- Number of hours for which mea- 1 to 1000 1 24

od_In_Hours surements should be retrieved.

GSM_Meas_Low_ Ericsson counter to be used for TIMERELSS, TIMER TIMER

Thresh_Counter_ calculating the number of mea-
TIMERELSS2 ELSS ELSS5
Ericsson surements that exceed the low
threshold.

GSM_Meas_ If it is set to True, all the measure- True, False NA False

BCCH_BSIC_Dis- ments which are reported are dis-
ambiguate_All ambiguated. If it is set to False,

EdenNet 21 FP 2106 © 2021 Nokia 65

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

Range (Min, Default

Parameter name Parameter description Step
Max) value

cell pairs which cross the thresh-

old are disambiguated.

Table 11: GSM to GSM measurement based detection parameters

6.2.4 GSM to UMTS configuration file parameters

Table 12: GSM to UMTS configuration file parameters lists the GSM to UMTS configuration file para-
meters.

De-
Range (Min,
Parameter name Parameter description Step fault
Max)
value

GSM_IRAT_UMTS_ Set to True if connected mode handover True, False N/A True
connected_mode_ from GSM to UMTS is enabled in the net-
ho_counts_available work and GSM to UMTS connected mode
handover attempt and success counts are
available.

GSM_IRAT_ho_suc- Used as one of the conditions to identi- 0 to 100 10 50

cess_rate_thresh- fy poorly performing IRAT neighbor rela-
old_for_ poorly_ tions. Confirms that the calculated han-
performing_cell_re- dover success rate is based on a reason-
moval able number of handovers. The IRAT han-
dover success rate must be below this
threshold for removal.

GSM_IRAT_min_ Used when identifying poorly performing 10 to 100 1 50

ho_attempts_for_ IRAT neighbor relations. Confirms that
poorly_performing_ the calculated handover success rate is
cell_removal based on a reasonable number of han-
dovers.

GSM_IRAT_ Used as one of the conditions for neighbor -1 to 1 0 0.5

geoscore_threshold_ removal for unused or poorly performing
for_poorly_perform- IRAT relations. Both source to target and
ing_cell_removal target to source geoscore must be below
this threshold for neighbor removal. Set to
1 to switch off this restriction.

GSM_IRAT_min_ Used as one of the conditions for neighbor 6 to 12 1 8

tier_count_for_poor- removal for unused or poorly performing

EdenNet 21 FP 2106 © 2021 Nokia 66

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

De-
Range (Min,
Parameter name Parameter description Step fault
Max)
value

ly_performing_cell_ IRAT relations. Relations must be at this

removal tier count or higher to be considered for
removal.

GSM_IRAT_min_dis- Used as one of the conditions for neighbor 1 to 200 1 40

tance_for_poorly_ removal for unused or poorly performing
performing_cell_re- IRAT relations. Relations must be at this
moval distance or higher to be considered for re-
moval.

GSM_minimum_tier_ IRAT neighbor relations with tier count 4 to 12 1 10

count_for_IRAT_ equal to or greater than the defined value
cell_removal are considered for removal.

GSM_IRAT_max _ Used for removal of an existing IRAT 0 to any positive 1 0

ho_success_for_ neighbor for replacement by a candidate integer
nbr_replacement IRAT neighbor. The existing IRAT neigh-
bor cannot be removed if the number of
handovers is above this threshold.

GSM_IRAT_max_ Cells or frequencies can only be added as 1 to 3 1 2

tier_count_for_add_ IRAT neighbors at this tier count or below.
topology

GSM_IRAT_max_ Cells or frequencies can only be added as 1 to 5 1 4

tier_count_for_add_ IRAT neighbors at this tier count or below.
hobased

GSM_IRAT_enable_ Permits or disables missing neighbor ad- True, False N/A False
topology_adds ditions based on network topology.

GSM_IRAT_outper- Out-performance multiplier required for re- 1.0 to 5.0 0.1 2.0
form_multiplier_HO_ placement of existing IRAT neighbors with
success a candidate when HO success scores are
compared.

GSM_IRAT_out- Out-performance multiplier required for re- 1.0 to 5.0 0.1 1.5
perform_multiplier_ placement of existing IRAT neighbor with
topology a candidate where cell coupling scores
are compared.

GSM_IRAT_min_ Specifies the minimum number of hours of 0 to 168 1 16

ho_kpi_hours_re- PM counter data required for HO success
quired counts on proxy relations using methods
which must be available for missing neigh-

EdenNet 21 FP 2106 © 2021 Nokia 67

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

De-
Range (Min,
Parameter name Parameter description Step fault
Max)
value

bor candidates to be evaluated. The meth-

ods used are: 2G<-3G, 3G->3G (co-sec-
tor 2G is source), 2G->2G (co-sector 3G
on target).

GSM_IRAT_min_ Threshold for intra-frequency handover 1 to 200 1 50

3Gto3G_ho_suc- success counts from the co-sector UMTS
cess_for_cell_add cell to an intra-frequency neighbor for this
cell to be considered for addition as an
IRAT neighbor to the GSM source cell.
The proxy relation method is 3G->3G (co-
sector 2G is source).

GSM_IRAT_min_ Threshold for intra-frequency handover 1 to 100 1 2

3Gto3G_ho_contri- successes on a UMTS to UMTS relation
bution_percent_for_ as a percentage of all outgoing intra-fre-
cell_add quency handovers from the co-sector
UMTS cell. The relation must be above
this contribution threshold for the neighbor
UMTS cell to be considered for addition
as an IRAT neighbor to the GSM source
cell. The proxy relation method is 3G->3G
(co-sector 2G is source).

GSM_IRAT_min_ Threshold for incoming IRAT handover 1 to 200 1 50

2G_Incoming_ho_ successes to the GSM cell for it to be con-
success_for_cell_ sidered for addition as an outgoing rela-
add tion. Proxy relation method 2G<-3G.

GSM_IRAT_min_ Threshold for incoming IRAT handover 1 to 100 1 1

2G_Incoming_ho_ successes to the GSM cell as a percent-
contribution_per- age of all incoming handovers from this
cent_for_cell_add IRAT frequency layer for it to be consid-
ered for addition as an outgoing relation.
Proxy relation method 2G<-3G.

GSM_IRAT_min_ Threshold for GSM intra-technology 1 to 200 1 50

2Gto2G_ho_suc- neighbor successes to GSM neighbor
cess_for_cell_add cells such that co-sector UMTS cells on
the neighbors are considered for addition.
The proxy relation method is 2G->2G (co-
sector 3G on target).

EdenNet 21 FP 2106 © 2021 Nokia 68

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

De-
Range (Min,
Parameter name Parameter description Step fault
Max)
value

GSM_IRAT_min_ Threshold for GSM intra-technology 1 to 100 1 2

2Gto2G_ho_contri- neighbor success on a GSM to GSM rela-
bution_percent_for_ tion as a percentage of all outgoing rela-
cell_add tions to GSM neighbor cells. The relation
must be above this contribution threshold
for co-sector UMTS cells on the neighbors
to be considered for addition. The proxy
relation method is 2G->2G (co-sector 3G
on target).

GSM_IRAT_Neigh- Number of defined neighbor relations al- 7 to 31 1 15

bor_List_Size_3G_ lowed to UMTS cells per UARFCN. Neigh-
per_layer bors will be added up to this limit before
any replacement of existing neighbors
takes place.

Note: The maximum neighbor

list size for 2G > 3G relations
for certain vendors is mentioned
below:

• Nokia - 32
• Ericsson - 64
• Huawei - 64

These limits are considered for

new additions as well as re-
placements.

GSM_IRAT_ Max_ A missing 2G->3G relation will not be 3 to 6 1 3

3G_Frequencies added if it would result in the number of
unique target UARFCN for all relations ex-
ceeding this limit.

GSM_IRAT_c1 Used in calculating the cell coupling score 0 to 4 0.5 0.8

for neighbor ranking. Higher values of this
parameter increase the weight of closer
neighbors by distance.

Note: The GSM_IRAT_c1, c2,

c3, c4 parameters should only
be modified under the guidance

EdenNet 21 FP 2106 © 2021 Nokia 69

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

De-
Range (Min,
Parameter name Parameter description Step fault
Max)
value

of the Nokia technical support

team.

GSM_IRAT_c2 Used in calculating the cell coupling score 0 to 1 0.2 0

for neighbor ranking. Higher values of this
parameter increase the weight of neigh-
bors with lower tier counts.

GSM_IRAT_c3 Used in calculating the cell coupling score 1 to 2 0.2 1

for neighbor ranking. Higher values of this
parameter reduce the weight of neighbors
with lower tier counts.

GSM_IRAT_c4 Used in calculating the cell coupling score 0 to 2 0.2 0.8

for neighbor ranking. Higher values of this
parameter increase the weight of neigh-
bors with lower tier counts. Setting the val-
ue to zero means the tier count is ignored.

GSM_IRAT_exclud- Used to exclude a specific detection Comma sepa- N/A None

ed_HO_based_addi- method based on HO success counts. A rated list of one
tion_method typical setting may be GSM_IRAT_ex- or more values
cluded_HO_based_addition_method from:
= 2G<-3G which will prevent the use of
• 2G<-3G
the 2G<-3G Incoming HO success count
• 3G->3G (co-
based method. The algorithm will then at-
sector 2G is
tempt to use the 3G->3G (co-sector 2G is
source)
source) method which is next in the priori-
• 2G->2G (co-
ty order.
sector 3G
on target)

UMFI_diversity Indicates if diversity is applied to the DIV, NODIV N/A NODIV

UTRAN cell. For a specific combination
of ARFCN and scrambling code, only one
value of information unit diversity can be
defined in the UTRAN measurement fre-
quency list. DIV or NODIV, as indicated by
the value of this configuration parameter,
are the diversity values applied for all the
UTRAN neighbors within ENM optimized
GSM cells.

EdenNet 21 FP 2106 © 2021 Nokia 70

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

De-
Range (Min,
Parameter name Parameter description Step fault
Max)
value

Buffer_for_Detect- This parameter is used to limit the detect- 1 to any positive 1 20

ed_Neighbors ed neighbor size for topology based addi- integer
tion.

Note: If a negative value or any

other unsupported value is set,
this parameter defaults to 20.

Limit_no_of_detect- This parameter is used to limit the number True, False N/A False
ed_neighbors of detected neighbors.

If this parameter is set to Yes, the ANR

2G module limits the detected neighbors
based on the value of the Buffer_for_
Detected_Neighbors parameter.

If this parameter is set to No, the ANR

2G module does not limit the detected
neighbors.

Table 12: GSM to UMTS configuration file parameters

6.2.5 Example of GSM ANR configuration file

This section provides an example of a GSM to GSM configuration file for aggressive replacement of
existing neighbors.

If existing neighbors are not replaced, the configuration below provides an example of more aggres-
sive configuration settings to force more replacements.

Note:

• The implications of parameter changes must be carefully considered and tests must be
performed in open loop mode before running the module with such a configuration in
closed loop mode:

– All source cells are considered to have a high TCH drop rate.
– The relationship of source to target and target to source antenna orientation
(geoscore) will not block the removal of existing relations.
– The tier count threshold for the removal of existing neighbors is reduced.

• The setting of Max_HO_Attempts_For_Neighbor_Removal = 0 is retained. This

means that only existing neighbors with zero handover counts in the past Connected

EdenNet 21 FP 2106 © 2021 Nokia 71

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

mode evaluation period will be candidates for replacement. Nokia recommends

that you do not increase this threshold due to the hard handover nature of GSM.

• During neighbor replacement, there could be additional changes based on the last
processed cell and the Max_Num_Changes_To_Push parameter limit could be changed
by a maximum of 5.

For example: During neighbor replacement for a cell, if the

Max_Num_Changes_To_Push parameter is set to 500, then 505 changes can be seen
in the generated report and its corresponding change set.

[Global]
#------------------------#
# Common parameters #
#------------------------#
Maximum_Cell_Distance_Threshold = 25.0
Bi-directional_Neighbors = True
Max_Num_Changes_To_Push = 5000
TimeBetweenPushes_15Mins = 1
Is_ocean_mode = False
#------------------------#
# 2G Specific parameters #
#------------------------#
GSM_DCR_Threshold = 0
GSM_Min_TCH_Drops_For_High_Drop_Rate_Calculation = 0
GSM_Max_Tier_Count_For_Cell_Add = 2
GSM_Min_Tier_Count_For_Cell_Removal = 5
GSM_GeoScore_Threshold_For_Poorly_Performing_Cell_Removal = 0.999
GSM_HO_Success_Rate_Threshold_For_Poorly_Performing_Cell_Removal = 50
GSM_Min_HO_Attempts_For_Poorly_Performing_Cell_Removal= 50
GSM_Max_HO_Attempts_For_Neighbor_Removal = 0
GSM_Neighbor_List_Size_2G = 18
GSM_C1 = 0.8
GSM_C2 = 0.0
GSM_C3 = 1.0
GSM_C4 = 0.8

6.3 Configuring INI parameters

INI parameters can be modified to change the default settings of a module. You can also import, export, delete, activate, and
deactivate configuration files.

Prerequisites

Only users with admin privileges have permissions to modify the parameters.

1. Log in to the EdenNet application:

EdenNet 21 FP 2106 © 2021 Nokia 72

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

a) In the address field of your Internet browser, type the following URL (for 2VM, 5VM, 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 SON Activity page appears.

2. Click Administration → Modules.

The following module categories appear in the left pane:

• 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.

3. Select ANR_2G.

4. Click Configure → Module Configuration.

The ANR_2G Configuration Manager dialog box appears.

5. Select the required configuration category.

You can click:

• Import And Activate: to import a file and activate it immediately.

• Import: to import a file.
• Export: to export the selected file to your system.
• Delete: to delete the selected file from the list.

The user should have admin or SON manager access permissions to perform the Delete oper-
ation. INI files can be deleted only if they are not used by other modules.
• Activate: to activate the selected file from the list.

Multiple configurations can be activated in the list.

• Deactivate: to deactivate the activated file.

A file can be deactivated only when it is not used by other module instances listed under Ac-
tive SON Modules and Module History.
• Set As Default: to set the selected file as the default configuration.
• Reset: to reset the edited parameter values in the selected INI file.

EdenNet 21 FP 2106 © 2021 Nokia 73

GSM Automatic Neighbor Relations DN09241774 1-1 GSM ANR configuration parameters
Guide

• Save: to save the new version of the configuration after editing the parameter values in the
selected INI file.
• Save As: to save the configuration with a different name.

For more information, see the Configuring a module section in the EdenNet User and Administra-
tion Guide.

For the INI parameters, see:

• Common configuration file parameters

• Baseline configuration file parameters
• Example of GSM ANR configuration file
• GSM to GSM measurement based detection parameters
• GSM to UMTS configuration file parameters

Expected outcome

The INI parameters are configured.

EdenNet 21 FP 2106 © 2021 Nokia 74

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR targets
Guide

7 Viewing GSM ANR targets

You can view the targets which are configured for the GSM ANR module.

1. Log in to the EdenNet application:

a) In the address field of your Internet browser, type the following URL (for 2VM, 5VM, 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 SON Activity page appears.

2. Click the SON Modules > Status tab.

The list of active SON modules appears in the left pane.

3. Select the ANR_2G module.

The Configure Targets page appears.

4. Click the Target tab.

Expected outcome

The target cells which were configured for the selected module instance are displayed on the map.

• The cells selected for module execution are displayed in blue.

• The cells with errors are displayed in red. The GSM ANR module does not optimize these cells.

The cells with errors also generate error events which can be analyzed in order to perform the re-
quired troubleshooting.

EdenNet 21 FP 2106 © 2021 Nokia 75

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

8 Viewing GSM ANR reports

For every execution, the module generates multiple reports in an Excel format. Each report is displayed in a separate worksheet
of the Excel file.

1. Log in to the EdenNet application:

a) In the address field of your Internet browser, type the following URL (for 2VM, 5VM, 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 SON Activity page appears.

2. Click SON Modules → Status.

Active SON Modules and Module History appear in the left pane, and Execution Status
appears in the right pane.

3. In the left pane, select ANR_2G either from Active SON Modules or Module History.

Module Status appears in the right pane.

4. Click Logs.

The log contains messages which provide information on the progress of the module run as well
as any warnings and errors that were encountered. The log also contains entries from the Module
Monitor service. For more information, see Monitoring GSM ANR.

5. Click the user name next to User Outputs.

The Directory Listing For dialog box with a list of files and module names appears.

6. Select the module file name.

A set of Excel files are listed in the Directory Listing For dialog box.

7. Select a file and open or save it.

Expected outcome

The module generates an Excel spreadsheet as defined in GSM ANR reports.

EdenNet 21 FP 2106 © 2021 Nokia 76

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

8.1 GSM ANR reports

Table 13: GSM ANR module report describes the tabs available in the output report.

Tab Description

Parameters Lists the module parameters used for iteration of

the ANR 2G module.

Final Neighbors Presents details on the final neighbors which ex-

ist after ANR execution, the relative rank of each
neighbor within each neighbor type, source LMS
layer, target (neighbor) LMS layer, LMS condi-
tion for the relation, LMS neighbor maximum size
constraints.

Detected Neighbors Displays all detected GSM and IRAT missing

neighbors. It also displays whether the neighbor
was actually added in the ANR run or provides
the reason why the detected neighbor was not
added.

Changes Details the neighbor additions and deletions ac-

tually proposed (open loop) or sent for implemen-
tation (closed loop). This list excludes changes
which could not be implemented due to errors or
other conditions such as full neighbor list or reuse
code conflict. These exclusions are listed in the
Logs tab for GSM and IRAT relations.

DCR Report Provides statistics from PM counters on dropped

call counts and rate. It is used as a condition for
processing cells for neighbor optimization.

HO Report Provides statistics from PM counters on han-

dover counts and success rate. It is used as a
condition for identifying poorly performing existing
neighbors. For GSM relations and IRAT relations.

Reuse Conflicts Provides additional details on the proposed Intra

and IRAT neighbors that could not be added be-
cause:

• they have the same BCCH as the source cell

or the same BCCH+BSIC combination as an
existing neighbor.

EdenNet 21 FP 2106 © 2021 Nokia 77

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Tab Description
• they have the same UARFCN+SC as an ex-
isting IRAT relation.

Neighbor Performance Provides details on the tier counts and geo-score

calculations for existing Intra and IRAT neighbors
and details relations classified as poor perform-
ers.

Logs Details any errors or conditions resulting in

changes which could not be sent for implemen-
tation. It is applicable to GSM relations and IRAT
relations.

Disambiguation List of measurements reported per source cell,

and 2G cell reuse parameters (BCCH, NCC,
BCC). It also provides a disambiguated cell.

BA <vendor_name> List Measurements Lists all the measurements reported per source
cell.

Cell Level Summary Presents a summary with one entry per cell re-
garding the action taken for that cell and the total
neighbor list sizes before and after ANR execu-
tion.

The Status column provides information on

whether the cell is:

• Evaluated - can result in neighbor additions,

removals, or no actions if the cell is already
optimized.
• Excluded - excluded through the SON exclu-
sion list or module exclusion list. It does not
have the required data for analysis and can-
not be trimmed.

Table 13: GSM ANR module report

Note: For all the reports mentioned in Table 13: GSM ANR module report, the Tier column
will have values greater than or equal to 10001 for all invalid or missing data related cells, as
defined in Table 14: Tier count.

Type/Code Name Description

10001 UNREACHABLE Tier count is greater than the maximum con-

figured value (10), or there is no path from

EdenNet 21 FP 2106 © 2021 Nokia 78

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Type/Code Name Description

the source cell to the target cell beyond 10

tiers.

There is no path from the source cell to the

target cell (the distance exceeds the thresh-
old).

10002 INVALID_SOURCE_CELL The source cell or one or more of its anten-

nas are missing attributes.

10003 INVALID_TARGET_CELL The target cell or one or more of its anten-

nas are missing attributes.

10004 CELL_HAS_NO_ANTENNA The source or target cell does not have an

antenna.

10005 UNKNOWN_TARGET_CELL The unique identifier of the target cell does

not match any cell in the tier service data-
base.

10006 UNKNOWN_SOURCE_CELL The unique identifier of the source cell does

not match any cell in the tier service data-
base.

10007 UNKNOWN_ERROR There is an unexpected error indicating an

internal exception.

10008 NO_SURROGATE The source cell or all its antennas have no

surrogates on the target layer.

Table 14: Tier count

Table 15: Parameters tab describes the columns in the Parameters tab.

Column name Description

Parameter The configuration parameter name

Value The parameter value used for the module execution

Table 15: Parameters tab

Table 16: Changes tab describes the columns in the Changes tab.

Column name Description

Neighbor Type Intra, IRAT.

Source Parent The parent entity of the source cell.

EdenNet 21 FP 2106 © 2021 Nokia 79

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Column name Description

• For WCDMA cells - the RNC-ID

• For GSM cells - the LAC

Source Cell The source cell name.

Neighbor Parent The parent entity of the target cell.

• For WCDMA cells - the RNC-ID

• For GSM cells - the LAC

Neighbor Cell The neighboring cell name.

Neighbor Frequency The frequency layer the neighbor cell belongs to.
Layer
• For WCDMA cells - the UARFCN
• For GSM cells - the Band

Source Frequency The frequency layer the source cell belongs to.
Layer

Reuse code • For WCDMA cells - the UARFCN + Primary Scrambling Code
• For GSM cells - the BCCH + BSIC

Distance Distance in kilometers to the neighboring cell.

Tier Tier count to the neighboring cell. The Effective Tier count after Tier Count Ad-
justment has been applied. A tier of 10,000 means it is unreachable through
the tier map.

Modification Neighbor relations are added or removed.

Reason Descriptive reason for neighbor addition or removal.

HO Attempts Number of HO attempts to the neighbor cell.

Source Cell DN The DN of the source cell.

Source Region The OSS that manages the source cell.

Source Vendor The source cell vendor.

Neighbor Cell DN The DN of the neighbor cell.

Neighbor Region The OSS that manages the neighbor cell.

Neighbor Vendor The neighbor cell vendor.

EdenNet 21 FP 2106 © 2021 Nokia 80

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Table 16: Changes tab

Table 17: Reasons for neighbor addition describes the reasons for neighbor addition in the Reason
column of the Changes tab.

Reason Description

White List Neighbor A neighbor relation was added which was white-listed through EdenNet.

First Tier Neighbor A missing neighbor relation was added which is a first tier according to the
tier map and is ranked within the number of Absolute_1st_Tier_Maxi-
mum.

HO Based Detected A neighbor relation that was detected as missing through handover success
Neighbor counts on proxy relations was added.

Measurement Based A neighbor relation that was detected as missing through the Mobile Mea-
Neighbor surement Report was added.

Topology Based A neighbor relation was added based on the network topology.
Neighbor

Tier 2+ Neighbor A neighbor relation that was tier two or greater according to the tier map and
detected as missing through the network topology was added.

Neighbor is a cosite A neighbor relation was added based on 3G cells for intra-frequency han-
(Same site ID) dover successes or 2G>2G handover successes for IRAT.

Missing Reciprocal A neighbor relation that was reciprocal (in the opposite direction) to an al-
ready added relation to maintain bi-directionality was added.

Missing Reciprocal A neighbor relation that was reciprocal (in the opposite direction) to an al-
(Extended First Tier ready added extended first tier relation to maintain bi-directionality was
Neighbor) added.

Table 17: Reasons for neighbor addition

Table 18: Reasons for neighbor removal describes the reasons for neighbor removal provided in the
Reason column of the Changes tab.

Reason Description

Trimmed Neighbor A neighbor relation was removed from the source cell to meet the configured
neighbor list size limits.

SON Excluded A neighbor relation which was excluded through EdenNet was removed.

Poorly Performing A neighbor relation was removed as it met all the configured thresholds that
Neighbor define a poorly performing relation.

Black List Neighbor A neighbor relation that was blacklisted through EdenNet was removed.

EdenNet 21 FP 2106 © 2021 Nokia 81

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Reason Description

Conflict with Source A neighbor relation that had a conflict in the BCCH frequency was removed.
BCCH frequency

Conflict with Neigh- A neighbor relation which had the same BCCH and BSIC was removed.
bor BSIC and BCCH
frequency - {}.
format(nbr)

Bidirectional Removal A neighbor relation which was reciprocal (in the opposite direction) to an al-
ready removed relation in order to maintain bi-directionality was removed.

Neighbor List Full. An existing lower ranked neighbor was removed and replaced by a higher
Removed {} with ranked missing neighbor. The reciprocal relation was removed to maintain bi-
same reuse code.for- directionality.
mat (change.catego-
ry)

Table 18: Reasons for neighbor removal

Table 19: Detected neighbors tab describes the columns in the Detected neighbors tab.

Column name Description

Source Parent The parent entity to the Source Cell.

• For WCDMA cells - the RNC-ID

• For GSM cells - the LAC

Source Cell The source cell name.

Neighbor Parent The parent entity of the Target Cell.

• For WCDMA cells - the RNC-ID

• For GSM cells - the LAC

Neighbor cell The target cell name.

Neighbor Type The neighbor types are Intra, Inter, and IRAT.

Neighbor Frequency The frequency layer the neighbor cell belongs to.
Layer
• For WCDMA cells - the UARFCN
• For GSM cells - the Band

Neighbor Reuse • For WCDMA cells - the UARFCN + Primary Scrambling Code
Code • For GSM cells - the BCCH + BSIC

Distance Distance in kilometers to the neighboring cell.

EdenNet 21 FP 2106 © 2021 Nokia 82

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Column name Description

Reason Descriptive reason why the cell is considered for addition. For example:

• First Tier (through first tier addition phase)

• HO Based (through proxy relations) or Topology/Tier2+

Other additions are done through the tier map.

Tier Count Tier count to the neighboring cell. The Effective Tier count after Tier Count
Adjustment has been applied. A tier of 10,000 indicates that it is unreachable
through the tier map.

Cell Coupling Score It is calculated from the Tier Count, Distance and relative antenna orienta-
tions. It is also called the Coupling Score.

Detection Method Describes the proxy relations used to detect missing neighbors. For example,
3G->3G (co-sector 2G is source).

HO Success Score The number of Handover Success counts on the proxy relations over the last
24 hour period.

Neighbor List Modifi- Neighbors are either added to the neighbor list or they are not added.
cation

Neighbor List Modifi- Descriptive reason for Not Added (for example, the candidate does not out-
cation Reason perform the current lowest ranked neighbor).

Source Cell DN The DN of the source cell.

Source Region The OSS that manages the source cell.

Source Vendor The source cell vendor.

Neighbor Cell DN The DN of the neighbor cell.

Neighbor Region The OSS that manages the neighbor cell.

Neighbor Vendor The neighbor cell vendor.

Table 19: Detected neighbors tab

Table 20: Final neighbors tab (includes GSM-GSM neighbors and GSM-UMTS neighbors) describes
the columns in the Final neighbors tab.

Column name Description

Source cell The source cell name.

Neighbor cell The neighboring cell name.

Neighbor Category The neighbor categories are Intra and IRAT.

EdenNet 21 FP 2106 © 2021 Nokia 83

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Column name Description

Neighbor Frequency The frequency layer the neighbor cell belongs to.
Layer
• For WCDMA cells - the UARFCN
• For GSM cells - the Band

New Neighbor It is True if the neighbor that is added is in the current iteration of the mod-
ule. It is False if it is an existing neighbor.

Tier Count Tier count to the neighboring cell. It is the Effective Tier count after Tier
Count Adjustment has been applied. A tier of 10,000 indicates that it is un-
reachable through the tier map.

Basic Tier Count The basic tier count before Tier Count Adjustment.

HO Successes The handover success count on this relation.

Neighbor Type The neighbor types are existing, added, and removed.

Reason Descriptive reason for neighbor additions (for example, First Tier, HO
Based, Topology or Tier2+, Missing Reciprocal).

Cell Coupling Score It is calculated from the Tier Count, Distance and relative antenna orienta-
tions. It is also called the Coupling Score.

Neighbor Rank The neighbor ranking along with the neighbor type (Intra, Inter, IRAT)

Source LMS Layer The layer from the LMS which the source cell belongs to.

Neighbor LMS Layer The layer from the LMS which the neighbor cell belongs to.

Neighbor LMS Condi- The condition from the LMS which permits the neighbor relation. The site
tion Name type (also called node configuration) is considered.

LMS Max Nbr Size The maximum neighbor size defined in the LMS.

Cannot Remove Rea- Descriptive reason why any existing neighbors are unsuitable for removal.
son

Source Cell DN The DN of the source cell.

Source Region The OSS that manages the source cell.

Source Vendor The source cell vendor.

Neighbor Cell DN The DN of the neighbor cell.

Neighbor Region The OSS that manages the neighbor cell.

Neighbor Vendor The neighbor cell vendor.

Table 20: Final neighbors tab (includes GSM-GSM neighbors and GSM-UMTS neighbors)

Table 21: DCR report tab describes the columns in the DCR report tab.

EdenNet 21 FP 2106 © 2021 Nokia 84

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Column name Description

Source Cell The source cell name.

SDCCH Drop Call Rate The SDCCH Drop Rate (%) on the cell.

TCH Drops Number of TCH Drops on the cell.

TCH Calls Complete Number of TCH Calls completed on the cells.

TCH Drop Call Rate The TCH Drop Call Rate is defined as: 100 * (TCH Drops / TCH Calls
Complete) (%)

High Drop Rate Cell True only if both GSM_DCR_Threshold and GSM_Min_TCH_Drops_
For_High_Drop_Rate_Calculation configuration thresholds are
met.

Source Cell DN The DN of the source cell.

Source Region The OSS managing the source cell.

Source Vendor The source cell vendor.

Table 21: DCR report tab

Table 22: HO report tab describes the columns in the HO report tab.

Column name Description

Source Cell The source cell name.

Neighbor Cell The neighboring cell name.

UserLabel The userLabel of the cell name (from the CM data).

Neighbor Type The neighbor types are Intra, Inter, and IRAT.

Neighbor Frequency The frequency layer the neighbor cell belongs to.
Layer
• For WCDMA cells - the UARFCN
• For GSM cells - the Band

Reuse Code • For WCDMA cells - the UARFCN + Primary Scrambling Code
• For GSM cells - the BCCH + BSIC

Neighbor relation exis- Indicates if the relation exists.

tence
• actual if run in closed loop
• hypothetical if run in open loop

Cross OSS neighbor re- Indicates if the relation is across an OSS boundary.
lation existence

Category The categories are first tier and extended first tier.

EdenNet 21 FP 2106 © 2021 Nokia 85

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Column name Description

Change Reason Descriptive reason for neighbor addition or removal (for example, first tier
addition, detected neighbor addition, reciprocal addition, replacement)

HO Successes The Handover Success count on the neighbor relation.

HO Attempts The Handover Attempt count on the neighbor relation.

Percentage of HO at- Percentage of handover attempts on this relation compared to all outgoing
tempts (%) neighbor relations for this frequency (for WCDMA targets - the UARFCN,
for GSM targets - the Band)

Success rate The Handover Success rate in percent.

Failure count The Handover Failure count.

Distance Distance in kilometers to the neighboring cell.

Tier Count Tier count to the neighboring cell. The Effective Tier count after Tier Count
Adjustment has been applied. A tier of 10,000 indicates that it is unreach-
able through the tier map.

Source Cell DN The DN of the source cell.

Source Region The OSS managing the source cell.

Source Vendor The source cell vendor.

Neighbor Cell DN The DN of the neighbor cell.

Neighbor Region The OSS managing the neighbor cell.

Neighbor Vendor The neighbor cell vendor.

Table 22: HO report tab

Table 23: Neighbor Performance tab describes the columns in the Neighbor Performance tab.

Column name Description

Neighbor Type The type of neighbor.

Source Cell DN The DN of the source cell.

Source Cell The source cell name.

Source Region The OSS managing the source cell.

Source Vendor The source cell vendor.

Neighbor Cell DN The DN of the neighbor cell.

Neighbor Cell The neighbor cell name.

Neighbor Region The OSS managing the neighbor cell.

EdenNet 21 FP 2106 © 2021 Nokia 86

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Column name Description

Neighbor Vendor The neighbor cell vendor.

Neighbor Frequency The frequency layer the neighbor cell belongs to. For WCDMA cells - the
Layer UARFCN.

Basic Tier Count The basic tier count before Tier Count Adjustment.

Tier Count Tier count to the neighboring cell. It is the Effective Tier count after Tier
Count Adjustment has been applied. A tier of 10,000 means it is unreach-
able through the tier map.

Distance Distance in kilometers to the neighboring cell.

S->T GeoScore GeoScore of the angle between the source cell azimuth and the neighbor
cell.

T->S GeoScore GeoScore of the angle between the target cell azimuth and the source
cell.

HO Attempts Number of Handover Attempts.

HO Success Rate (%) Handover Success Rate in %.

Poor Performing Neigh- True if the relation meets all the configured criteria for poorly perform-
bor ing neighbor removal (for example, Tier, Distance, S->T GeoScore, T->S
GeoScore, HO Attempt Number, HO Success Rate).

HO Data Hours Avail- Number of hours of valid handover data available in the PM counters.
able
Note: This value is zero if Connected Mode Handover is en-
abled for GSM to UMTS. When it is zero, the configuration pa-
rameter GSM_IRAT_UMTS_connected_mode_ho_counts_
available should be set to False.

Cell Coupling Score It is calculated from the Tier Count, Distance and relative antenna orienta-
tions. It is also called Coupling Score.

Detection Method Describes the proxy relations used to detect missing neighbors. For ex-
ample, 3G->3G (co-sector 2G is the source) for this cell.

HO Success Score The number of Handover Success counts on the proxy relations over the
last 24 hour period.

Table 23: Neighbor Performance tab

Table 24: Reuse Conflicts tab describes the columns in the Reuse Conflicts tab.

Column name Description

Neighbor type The type of neighbor.

EdenNet 21 FP 2106 © 2021 Nokia 87

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Column name Description

Source Cell DN The source cell DN.

Source Cell The source cell name.

Source Region The OSS managing the source cell.

Source Vendor The source cell vendor.

Candidate Cell DN The DN of the candidate cell.

Candidate Cell The candidate cell name.

Candidate Region The candidate cell managing OSS.

Candidate Vendor The candidate cell vendor.

Distance Distance in kilometers to the neighboring cell.

Basic Tier Count Tier Count to the neighboring cell.

Source-Candidate GeoScore of the angle between the source cell azimuth and the neighbor
GeoScore cell.

Candidate-Source GeoScore of the angle between the target cell azimuth and the source
GeoScore cell.

Reason for conflict Reason for the conflict. Usually, it is due to the clash of the UARFCN+SC
with the existing neighbor.

Candidate-bcch BCCH frequency of the candidate neighbor.

Candidate-ncc network color code (ncc_bcc = BSIC) of the candidate neighbor.

Candidate-bcc base station color code (ncc_bcc = BSIC) of the candidate neighbor.

Candidate-uarfcn UARFCN of the candidate neighbor.

Candidate-sc Primary Scrambling Code of the candidate neighbor.

Table 24: Reuse Conflicts tab

Table 25: Logs tab describes the columns in the Logs tab.

Column name Description

Time Timestamp for the log message during module execution.

Type The event types are error and warning.

Message Description of the error or warning.

Table 25: Logs tab

Table 26: Disambiguation tab describes the columns in the Disambiguation tab.

EdenNet 21 FP 2106 © 2021 Nokia 88

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Column name Description

Source Cell DN The source cell DN.

Source Cell The source cell name.

Source Region The source cell managing OSS.

Source Vendor The source cell vendor.

NCC Indicates the Network Color Code of the target cell.

BCC Indicates the Base station Color Code of the target cell.

BCCH Indicates the BCCH frequency of the target cell.

Disambiguated Cell (if Indicates a disambiguated cell.

any)

Measurements Total Re- Total number of reports received from a serving cell.
ports

Measurements Percent The percentage of the reports received from a serving cell.
Reported

Measurements Low Indicates the number of measurements that exceed the low threshold
Threshold from the carrier to interferer.

Note:

• For Nokia, low threshold is the sum of NBR_OF_SAMPLES_

IN_CLASS_2 and NBR_OF_SAMPLES_IN_CLASS_3 col-
lected from CF and DAC measurements.
• For Ericsson, low threshold is defined using the parameter
GSM_Meas_Low_Thresh_Counter_Ericsson.

Measurements Low Indicates the percentage of measurements that exceed the low threshold
Threshold Percent from the carrier to interferer.

1st Close Cell Indicates the first closest disambiguated cell.

1st Close Cell Coupling Indicates the cell coupling score from the source cell of the first closest
Score disambiguated cell.

1st Close Cell Distance Indicates the distance between the source cell and the first closest disam-
biguated cell.

1st Close Cell Tier Indicates the tier count between the source cell and the first closest dis-
ambiguated cell.

1st Close Cell Geoscore Indicates the geoscore for the first closest disambiguated cell.

2nd Close Cell Indicates the second closest disambiguated cell.

EdenNet 21 FP 2106 © 2021 Nokia 89

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Column name Description

2nd Close Cell Coupling Indicates the cell coupling score from the source cell of the second closest
Score disambiguated cell.

2nd Close Cell Distance Indicates the distance between the source cell and the second closest dis-
ambiguated cell.

2nd Close Cell Tier Indicates the tier count between the source cell and the second closest
disambiguated cell.

2nd Close Cell Indicates the geoscore for the second closest disambiguated cell.
Geoscore

Error (if any) Reports errors during disambiguation.

Table 26: Disambiguation tab

Table 27: BA <vendor_name> List Measurements tab describes the columns in the BA
<vendor_name> List Measurements tab.

Column name Description

Source Cell DN The source cell DN.

Source Cell The source cell name.

Source Region The source cell managing OSS.

Source Vendor The source cell vendor.

BSIC Indicates the BSIC target cell.

BCCh Indicates the BCCH frequency of the target cell.

Is Neighboring Indicates whether the neighboring relation exists with the target cell.

Is Valid Measurement Indicates whether the recorded measurement is valid for optimization.

Number of Measurement Total number of reports received from a serving cell.

Reports

Counter Total Indicates the sum of Low, Min and High measurements.

Percent Reported Indicates the percentage of Counter Total.

Exceeding Low Thresh- Indicates the number of measurements that exceed the low threshold
old Counts from the carrier to interferer.

Note:

• For Nokia, low threshold is the sum of NBR_OF_SAMPLES_

IN_CLASS_2 and NBR_OF_SAMPLES_IN_CLASS_3 col-
lected from CF and DAC measurements.

EdenNet 21 FP 2106 © 2021 Nokia 90

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Column name Description

• For Ericsson, low threshold is defined using the parameter
GSM_Meas_Low_Thresh_Counter_Ericsson.

Percent Exceeding the Indicates the percentage of measurements that exceed the low threshold
Low Threshold from the carrier to interferer.

Disambiguated Cell Indicates a disambiguated cell.

Table 27: BA <vendor_name> List Measurements tab

Table 28: Cell Level Summary tab describes the columns in the Cell Level Summary tab.

Column name Description

Source Parent The parent entity to the Source Cell. For GSM cells, it is the LAC.

Source Cell The Distinguished Name for the source cell managed object.

Source Cell DN The source cell DN.

Source Region The EdenNet region to which the source cell belongs.

Source Vendor The vendor for the source cell.

Status The status can be:

• Evaluated - can result in neighbor additions or removals, or no action

if the cell is already optimized.
• Excluded - cell is excluded (for example, excluded through the SON
exclusion list or Module exclusion list, missing required data for analy-
sis, or cannot be trimmed).

Reason Descriptive reason for the status.

Total Neighbors Before Total number of neighbors before this execution of the module.

Total Neighbors After Total number of neighbors after this execution of the module (actual if run
in closed loop, hypothetical if run in open loop).

Intra Neighbors Before Total number of Intra neighbors before this execution of the module.

Intra Neighbors After Total number of Intra neighbors after this execution of the module (actual
if run in closed loop, hypothetical if run in open loop).

Intra Neighbors Added Total number of Intra neighbors added during the execution of the module.

Intra Neighbors Re- Total number of Intra neighbors removed during the execution of the mod-
moved ule.

IRAT Neighbors Before Total number of IRAT (GSM-WCDMA) neighbors before this execution of
the module.

EdenNet 21 FP 2106 © 2021 Nokia 91

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR reports
Guide

Column name Description

IRAT Neighbors After Total number of IRAT (GSM-WCDMA) neighbors after this execution of
the module (actual if run in closed loop, hypothetical if run in open loop).

IRAT Neighbors Added Total number of IRAT neighbors added during the execution of the mod-
ule.

IRAT Neighbors Re- Total number of IRAT neighbors removed during the execution of the mod-
moved ule.

Table 28: Cell Level Summary tab

EdenNet 21 FP 2106 © 2021 Nokia 92

GSM Automatic Neighbor Relations DN09241774 1-1 Plan provisioning in case of failure
Guide

9 Plan provisioning in case of failure

This section describes:

• Re-provision a plan
• Filtering provisioning of failed cells based on feedback logs received from NAdC

9.1 Re-provision a plan

A plan provisioning failure is a failure resulting from at least one or more NEs which have their provi-
sioning status as FAILED. However, this operation status does not necessarily reflect the actual net-
work state. A FAILED status in provisioning does not mean the provisioning has failed for all the para-
meters and network elements in the plan.

The user has the option to re-provision the plan. In this situation, failing elements are removed from
the plan based on the rules specified in the XML file. The result is a delta plan with all the cells which
have a chance of successful provisioning. Such a plan is then provisioned to the network. The plan
provisioning and splitting can be retried in case a new delta plan returns failures again.

9.2 Filtering provisioning of failed cells based on feedback logs

received from NAdC
When plan provisioning fails due to failures on specific cells, the user has the option to exclude these cells from plan and retry
provisioning along with the rest of the changes in the plan.

To filter cells based on the feedback logs received from NAdC, update the rules.xml file which is
available at /var/tmp/enet/ on the central VM:

Note:

If the rules.xml file is not available in the central VM at the /var/tmp/enet location,
then create a file called rules.xml as a vson user.

1. Log in to the central VM.

2. Go to:

/var/tmp/enet/
3. Locate the rules.xml file.
4. Create a new rule.
For example:

<rule name="new_rule" enabled="true" vendor ="nsn">

<expression>

<contains>CONSISTENCY CHECK FAILED</contains>

EdenNet 21 FP 2106 © 2021 Nokia 93

GSM Automatic Neighbor Relations DN09241774 1-1 Plan provisioning in case of failure
Guide

<matcher>.*PRIMARY SCRAMBLING CODE.*</matcher>

</expression>

<reason>CONSISTENCY CHECK FAILED:PRIMARY SCRAMBLING CODE</reason>

</rule>
5. Add the new rule and save the rules.xml file.

For details about the rule tags, see Table 29: Rule tags.

Expected outcome

Based on the rule, the relevant cells are excluded from plan and retry provisioning.

Additional information

Table 29: Rule tags describes the function of tags mentioned in the rule.

Tag name Description

rule name identifies the rule.

enabled enables or disables the rule.

The values are true or false.

vendor applies rules to the MO belonging to the mentioned vendor.

Default values are:

"nsn","alu","zte","huawei","ericsson","default"

Note: If vendor = default, this rule is applied to any MO

identified in feedback.

contains used for matching the expected feedback error.

matcher used for matching the expected feedback error.

reason tags are logged in:

/home/vson/log/enet/error_classifier_app.log when an MO is
excluded from retry.

Table 29: Rule tags

The logs related to plan_provisioning_app and error_classifier_app are available at the

below mentioned paths:

• plan_provisioning_app: /home/vson/log/enet/plan_provisioning_app.log
• error_classifier_app: /home/vson/log/enet/error_classifier_app.log

EdenNet 21 FP 2106 © 2021 Nokia 94

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR events
Guide

10 Viewing GSM ANR events

You can view events which are specific to the module.

1. Log in to the EdenNet application:

a) In the address field of your Internet browser, type the following URL (for 2VM, 5VM, 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 SON Activity page appears.

2. Click the Events tab.

A list of filters appears in the left pane.

3. From the Module/Service filter, click the ANR_2G instance to view the event logs.

The event logs can also be viewed using the following filters:

• Name: indicates the name of the event.

• Category: indicates the category of the event.
• Level: indicates the level of the event.
• Source Type: indicates from where the event originates.
• Target Type: indicates to where the event is targeted.
• Target: indicates the target of the event (cell name can be selected).

Note: The common event levels are information and warning. By default, the warning
and error level filters are selected. To view all levels of events, remove the warning and
error level filters.

4. In the Time Range area, set the required time range.

5. Under 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 to apply the filter.

EdenNet 21 FP 2106 © 2021 Nokia 95

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR events
Guide

Expected outcome

The event log appears.

10.1 GSM ANR events

The ANR 2G events are described in Table 30: ANR 2G events.

Category: ANR_2G

Name Level Description

neighbor_relation_unre- info When the target cell of the relation is an unknown cell,
solved that is, the internal cell representation is not present in
any OSS.

Could not evaluate cell info If the cell does not satisfy all the initial ANR validations
or if it has a relation pointing to an invalid target cell
then the cell is skipped from optimization.

Could not trim neighbor list info When the module is not able to trim targets to the con-
figured value.

Neighbor change event info Generates a cell event to indicate neighbor addition, re-
moval, or updation. The event type is added, removed,
or updated.

Could not add particular info When the target cell is not added because of LMS or
neighbor module configuration constraints.

Could not remove poorly info When we are not able to remove the neighbor because
performing neighbor of pre-validation failure for removal.

could_not_build_mos info Whenever there is an exception while building MOs.

Optimizer Exception info Any other Optimizer exception during building of MOs.

Failed to push changes! info When the provision fails during closed loop.

Attempted changes did not info When the EMS validation before the actual provision
pass EMS validation. See fails.
log for details.

Target has a high DCR info When the source 2G cell has a high DCR as per the
module configuration.

Could not add detected info When the detected neighbor is not added because of
neighbor (HO-based) {} the pre-validation for addition.
could not be added as

EdenNet 21 FP 2106 © 2021 Nokia 96

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing GSM ANR events
Guide

Name Level Description

neighbor of {} via HO-
based addition

No first tiers info When there are no first tiers for the source cell.

No n tiers info When the n tier for the cell cannot be fetched and has
validation errors.

Table 30: ANR 2G events

EdenNet 21 FP 2106 © 2021 Nokia 97

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing SON change reports
Guide

11 Viewing SON change reports

You can view the changes made by the ANR_2G module to the managed objects.

Prerequisites

All the prerequisites mentioned in the GSM ANR prerequisites section must be met.

1. Log in to the EdenNet application:

a) In the address field of your Internet browser, type the following URL (for 2VM, 5VM, 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 SON Activity page appears.

2. Click SON Modules → Reports.

The Network Analysis page is displayed.

3. In the left pane, click Modules, select ANR_2G, and click Apply.

Expected outcome

The SON changes for ANR_2G are displayed in a tabular format.

11.1 Cell level records

The ANR 2G module reports the records at cell level as defined in Table 31: Cell level records. The
cell level records can be viewed from the Reports tab of the EdenNet GUI. For more information, see
the View reports section in the EdenNet User and Administration Guide.

Scenario Description

Cell neighbor list evalu- <cell1> is evaluated and neighbor list changes are made and/or missing
ated neighbors are detected.

Detected <W> neighbors. Added <X> neighbors and removed <Y> neigh-
bors.

EdenNet 21 FP 2106 © 2021 Nokia 98

GSM Automatic Neighbor Relations DN09241774 1-1 Viewing SON change reports
Guide

Scenario Description

Example :PCH99221A22 is evaluated and neighbor list changes are

made and/or missing neighbors are detected.

Detected 4 neighbors, added 4 neighbors and removed 0 neighbors.

Note:

• The module generates the record in the Report tab only for
the cell which is evaluated under the following conditions:

– when there are changes to the cell

– when missing neighbors are detected and cannot be
added

The Network Analysis tab shows the record, although

there is no change pushed to the network.

Cell excluded <cell1> was excluded from evaluation due to: <reason for exclusion>

Example: PCH19704A21 was excluded from evaluation due to: Could not
trim (PCH19704A21) because sufficient neighbors could not be removed
to meet the max total size limit.

Note: The cell can be excluded for several reasons including:

• on SON Exclusion List

• on Module Exclusion List
• cannot be trimmed
• missing required data

Table 31: Cell level records

EdenNet 21 FP 2106 © 2021 Nokia 99

GSM Automatic Neighbor Relations DN09241774 1-1 Monitoring GSM ANR
Guide

12 Monitoring GSM ANR

You can monitor the GSM ANR module's activities, status, and events.

For more information, see the Configure and monitor SON modules section in the EdenNet User and
Administration Guide document.

To view the Network Analysis table, which displays information about the reasons behind the changes
pushed by the EdenNet modules, see the Viewing network analysis details section in the EdenNet
User and Administration Guide.

To view the execution status, which provides the Instance Name and State of a selected module, as
well as the SON module's script log detailing the actions taken on individual target cells, see the View-
ing the execution status section in the EdenNet User and Administration Guide.

12.1 Module Monitor Service

This service performs pre-defined checks on the CM data and cell plan data either periodically or up-
on reception of new CM data. When the module runs, the service is queried, and messages indicating
problems or potential problems are inserted at the beginning of the module log.

The problems are categorized into two levels:

• Error: causes the module to stop working and log the incident that caused the module to stop.
• Warning: logs a detailed warning in the instance log.

Currently, only per cell warnings are defined for Module Monitor Service for ANR. These are:

• Triggered at the reception of new CM data:

– Cell has no location (lat, lon) (indicates that the location in the Cell Plan should be checked).
• Triggered once every 24 hours:

– Cell has no first tier information (indicates that the location in the Cell Plan or Tier Count ser-
vice should be checked).
– Cell does not have any intra-frequency neighbors.
– Cell does not have any inter-frequency neighbors.
– Cell does not have any IRAT type neighbors.
– Cell does not have neighbors of any type.
– Cell has large tier counts for close surrounding cells (indicates that Tier Count service should
be checked).

EdenNet 21 FP 2106 © 2021 Nokia 100

GSM Automatic Neighbor Relations DN09241774 1-1 Troubleshooting ANR
Guide

13 Troubleshooting ANR
This section describes how to troubleshoot the ANR modules.

13.1 ANR tries to create relations that already exist

Problem

When ANR is run iteratively, it tries to create the same relations in every iteration. This results in provi-
sioning failure from the second iteration onwards. However, if ANR is triggered again after a few hours,
it proposes the correct relations and provisioning succeeds.

Possible scenarios:

The neighbors table is not updated properly because relation creation notifications are getting
dropped.

Solution

1. Log in to the central App Server.

2. Switch to vson user by entering:

su - vson
3. Restart the mo_event_distributor_app by entering:

enet restart {region_name}.cm.mo_event_distribution_app

The provisioning is successful.

EdenNet 21 FP 2106 © 2021 Nokia 101