Eden Net GSM Fo Guide

EdenNet 21 FP 2106
GSM Frequency Optimization Guide

DN09257997
Issue: 1-1
GSM Frequency Optimization Guide DN09257997 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 Frequency Optimization Guide DN09257997 1-1 Table of Contents
Contents
1 Summary of changes...................................................................................................................................... 5
2 Overview of GFO........................................................................................................................................... 10
2.1 GFO dependencies and interactions...................................................................................................... 10
2.1.1 Dependencies................................................................................................................................. 11
2.1.1.1 Dependencies for Nokia.........................................................................................................11
2.1.1.2 Dependencies for Huawei...................................................................................................... 12
2.1.1.3 Open IM format support......................................................................................................... 13
2.1.2 Interactions......................................................................................................................................14
3 GFO functional description and guidelines................................................................................................15

3.1 Operational modes of GFO.................................................................................................................... 17
3.1.1 Open loop mode............................................................................................................................. 17
3.1.2 Closed loop mode...........................................................................................................................18
4 GFO algorithm................................................................................................................................................20
5 Configuring and executing GFO module....................................................................................................22

5.1 GFO prerequisites................................................................................................................................... 22
5.1.1 License............................................................................................................................................ 22
5.1.2 PM data and CM data for GFO module.........................................................................................23
5.2 Accessing GFO....................................................................................................................................... 23
5.3 Configuring targets for GFO................................................................................................................... 24
5.4 Configuring parameters for GFO............................................................................................................ 24
5.5 Selecting the configuration file for GFO................................................................................................. 25
5.6 Selecting execution type for GFO.......................................................................................................... 26
5.7 Confirming execution for GFO................................................................................................................ 26
6 GFO configuration parameters.................................................................................................................... 28

6.1 GFO GUI parameters..............................................................................................................................28
6.2 GFO interference matrix configuration INI file........................................................................................ 40
6.2.1 DB offset value lookup table.......................................................................................................... 46
6.2.2 Example of GFO interference matrix configuration file.................................................................. 47
6.3 GFO module configuration file................................................................................................................ 48
6.4 User defined frequency groups Excel file...............................................................................................54
6.5 Configuring INI parameters.....................................................................................................................58
7 Viewing GFO reports.....................................................................................................................................60

7.1 GFO reports............................................................................................................................................ 60
8 Viewing GFO events......................................................................................................................................76

8.1 GFO events............................................................................................................................................. 77
EdenNet 21 FP 2106 © 2021 Nokia 3

GSM Frequency Optimization Guide DN09257997 1-1 Table of Contents
9 Monitoring GFO............................................................................................................................................. 78
10 Automatic verification and rollback.......................................................................................................... 79

GSM Frequency Optimization Guide DN09257997 1-1 Summary of changes
1 Summary of changes
Release Change description
EdenNet 21 FP 2106 No change.
EdenNet 21 FP 2103 Updated section:
• Dependencies for Huawei is updated by removing Ericsson references.
EdenNet 21 Updated section:
• Overview of GFO - A note is added about the deprecation of direct CM

integration.
• Closed loop mode is updated with a Note.
EdenNet 20 Added sections:
• Closed loop mode

• Automatic verification and rollback
Updated sections:
• GFO functional description and guidelines

• GFO module configuration file is updated with Verification and Rollback
sheet
• GFO GUI parameters is updated with the following parameters:
– KPI Verification Window

– Start hour of maintenance window
– End hour of maintenance window
– Medium Traffic Level
– High Traffic level
– Delta Increase Medium Traffic Level
– Delta Increase High Traffic Level
– Fix Violations Aggressively

– Violations Cost Margin

• GFO reports section is updated with a Note for Existing interfered
hopping mode and Existing interfering hopping mode.
EdenNet 19A FP 2004 No change.
EdenNet 19A FP 2001 Updated sections:
• GFO module configuration file - The New TRX Assignment sheet is

added.
• GFO functional description and guidelines
• GFO reports
• Example of GFO interference matrix configuration file
EdenNet 19A No change.
• Instance of NOLS is replaced with Support portal in Dependencies for

Huawei section.
EdenNet 19 FP 1904 Updated sections:
• Instances of Custom modules are changed to Adapted modules in

the following sections:
– Accessing GFO
– Configuring INI parameters
• GFO GUI parameters section is updated with modified descriptions for

BSIC: Limit by cells and BSIC: Limit by distance.
EdenNet 19 Updated section:
• GFO GUI parameters is updated with enhanced description for the fol-
lowing parameters:
– BSIC: Limit by Distance

– BSIC: Maximum Distance

– BSIC: Limit by Cells

– BSIC: Maximum number of Cells
– HSN: Limit by Distance
– HSN: Maximum Distance
– HSN: Limit by Cells
– HSN: Maximum number of Cells
– Mobile Allocation List (MAL) length adjustment
EdenNet 18 SP1 1901 No change.
EdenNet 18SP1 1812 Updated section:
• Updated the description of the Network Statistics tab in GFO reports

section.
EdenNet 18 SP1 Added section:
• The User defined frequency groups Excel file section is added.
Updated sections:
• A new parameter User defined frequency groups is added to

GFO GUI parameters.
• The Open loop mode section is modified.
• Information about CSV files is updated in the Dependencies for Huawei
section.
EdenNet 18 Added content:
• Added Huawei content to Dependencies for Huawei.

• Added Huawei content to GFO functional description and guidelines.
• Added MAIO and HSN optimization as a bullet point in GFO functional
description and guidelines.
• Added a note for violation report to GFO reports.
• The below GUI parameters are added to the GFO GUI parameters sec-
tion:
– Consider PGSM and EGSM separately in the BCCH fre-

quency group
– Consider PGSM and EGSM separately in the TCH fre-
quency group
– Use exclusive frequency channels for PGSM and EGSM
• The Open IM format support section is added.
• The Table 29: Interference matrix tab table is added to the GFO reports
section.

Updated content:
• Updated the description of the GUI parameter FC: Average inter-

ference in GFO GUI parameters.
• Added BSIC: Forbidden BSIC parameters in GFO GUI parameters.
• The GFO reports section is updated.
EdenNet 17 SP1 FP1 No change.
EdenNet 17 SP1 Added sections:
• Dependencies for Huawei

• GFO interference matrix configuration INI file
Updated sections:
• Renamed module name from GSM TCH Frequency Optimization

Guide to GSM Frequency Optimization Guide.
• Added baseband hopping details in section GFO functional description
and guidelines.
• Enhanced GFO functional description and guidelines with additional in-
formation.
• Added Plan Name Tag and BSIC:Allowed BCC parameters in GFO
GUI parameters.
• Added Forbidden Assignments sheet.
• Added Average CS traffic (Erlangs),TCH Blocking (%), Original HSN1,
Original HSN2, New HSN1, New HSN2, Forbidden BCCs , and Forbid-
den NCCs details in Table 27: Proposed Plan Report tab.
• Removed resolve_to_a_single_cell parameter in GFO interference
matrix configuration INI file
EdenNet 17 FP1 Added sections:
The Configuring and executing GFO module section is enhanced by adding

Selecting the configuration file for GFO section.
Updated sections:
• Configuring INI parameters section is updated with Save As and Set

As Default options in GSM_Frequency_Optimization Configuration
Manager dialog box.
• SON Operation mode parameter description is updated in GFO GUI
parameters.
EdenNet 17 This is a new document that provides information on GSM Frequency Opti-
mization module.

Table 1: Summary of changes

GSM Frequency Optimization Guide DN09257997 1-1 Overview of GFO
2 Overview of GFO
The EdenNet GSM Frequency Optimization (GFO) module creates a frequency plan based on the in-
terference information. This information is collected from the measurements carried out by the mobile
stations in the GSM network.
Since frequency spectrum is a scarce resource, GSM networks must perform frequency optimization
to maintain acceptable levels of performance while using the available resource. Both signaling and
traffic channels must be allocated in the optimal frequency to reduce interference in the network.
In general, frequency optimization is required in the following situations:
• Planning frequencies for the entire set of target cells in the network.
• Re-farming frequencies across different GSM frequency bands
• Optimizing frequency plans in the target set of cells where new cells are deployed in the nearby
area
The GFO module supports the creation of a frequency plan for a given set of target cells by automati-
cally considering the impacted area of frequency changes.
Note:
• For new 2G sites, it is recommended to create BTS objects corresponding to new

2G sites in the OSS and lock these BTSs. Use the GSM ANR (Automatic Neighbor
Relations) module to create and provision the neighbor relations to these new 2G sites.
Then use the GFO module to obtain optimal frequencies for these new 2G sites.
• Once the BCCH frequencies in the 2G BTSs are updated, it is recommended to run the
LTE Frequency Rules module. This ensures the objects on the LTE side are updated
(which are referring to the BCCH frequencies on the 2G side if LTE-GSM handover
supported).
Note: Nokia only supports the use of AC based integration for Nokia, Ericsson, and Huawei
vendors as direct CM integration is deprecated from EdenNet 21 release onwards for these
vendors.
Vendor Technology
Nokia GSM
Ericsson
Huawei
Table 2: Supported vendor and technology

2.1 GFO dependencies and interactions

This section describes how the GFO module interacts with other EdenNet modules. It also describes
the dependencies of the GFO module:
• Dependencies
• Interactions
2.1.1 Dependencies
The dependencies vary for each supported vendor. For more information, see
• Dependencies for Nokia

• Dependencies for Huawei
2.1.1.1 Dependencies for Nokia
• The Measurement BCCH Allocation List (MBAL) of a given Base Station Controller (BSC) must
contain the Broadcast Control Channel (BCCH) frequencies of:
– The neighbors of the cell in the target BSCs.

– All the cells present in the neighbor BSCs.
Note: Create MBAL manually outside the GFO module.
Based on the operator strategy and the network, you can use the BCCHs used in the entire net-
work to create an MBAL. However, before provisioning the MBAL in the network, you must enable
its usage in all the BTSs of the relevant BSCs by setting the Measurement BCCH Allocation List
parameter of corresponding BTS managed objects.
Additionally, you can reduce the number of neighbor cell BCCHs in the MBAL by ranking the
neighbor cells based on their handover performance (HO). Before enabling the usage of MBAL in
the network, you must provision a plan in the network that contains all the ranked neighbor cells.
Note: A backup plan must be created during MBAL plan provisioning so that once the
measurement cycle is completed original network configuration can be restored by re-
moving the MBALs.
• MBAL usage comes with limitations defined by European Telecommunications Standards Institute
(ETSI) or American National Standards Institute (ANSI).
– It is safe to use MBAL, if operator has:
• Only one GSM band

• Only channels from PGSM and GSM 1800 band and in GSM 1800 Absolute Radio
frequency Channel Numbers (ARFCNs) are within 112 consecutive channel numbers
• Only channels from EGSM and GSM 1800 band and in GSM 1800 ARFCNs are within
112 consecutive channel numbers and channel number 0 is not used in EGSM

– It is not safe to use MBAL, if:
• Operator has three GSM bands in use (PGSM, EGSM and GSM 1800)
• Operator has channel number 0 in use with some other channels from EGSM band
• If the ARFCNs of a band does in 112 consecutive channel numbers
• Before enabling the Frame Erasure Probability (FEP) measurement, Total FEP usage should be
enabled in the required BSCs.
The syntax of MML command is:
WOA:<parameter class>,<parameter number>,<activation status>;
MML command to:
– enable TOTAL_FEP_USAGE in BSC is:
ZWOA:2,820,A;
– check TOTAL_FEP_USAGE in BSC is to verify FEP usage:
ZWOS:2,820;
– disable CF measurements is:
ZWOC:10,65,0;
– disable DAC measurements is:
ZWOA:2,626,D;
• You should use the NetAct Administration of Measurements application to measure the total FEP
for the target BSCs and the impacted BSCs. Measurement interval must be set to 15 minutes as
the BSC changes its frequency once in every is minutes.
• Once the FEP measurement is completed, you must restore the original network configuration
manually by provisioning the backup plan. The backup plan is created during the provisioning of
MBAL in the network.
2.1.1.2 Dependencies for Huawei

For Huawei vendors, it is mandatory to provide the Channel Finder and Defined Adjacent Cell
(CF&DAC) data in the vendor agnostic Interference Matrix (IM) format as mentioned in this section.
The vendor agnostic IM data is required to in the .csv format and it must contain the following fields:
Note: The fields need not necessarily follow the order as listed below.
• Date and time (DD/MM/YYYY HH:MM)

• CellName (String)
• Interferer Absolute Radio Frequency Channel Number (ARFCN) (Integer)
• Interferer BSIC (2 DIGITS – NCC, BCC)

• Number of samples per victim (Integer) (*)

• Number of samples while in BAL (Integer) (*)
• Number of samples per interferer (Integer)
• Interferer average rxlev (Integer)
• High interference samples (Integer)
• Moderate interference samples (Integer)
Note:
• Fields marked with (*) are not mandatory. They can be empty.
• ARFCN stands for Absolute Radio Frequency Channel Number.
• NCC stands for Network Color Code.
• BCC stands for Base Station Color Code.
You can generate a vendor agnostic IM file by using the IM converters for Huawei available in the Sup-
port portal. Support portal can be accessed at https://customer.nokia.com/.
A group of CSV files can be packaged in a ZIP file and the ZIP file must be placed in a folder in the
shared path of the task server of EdenNet. If multiple task servers are used, then the files must be
places in all the task servers. The path of the folder must be provided in the Interference Matrix config-
uration (INI) file.
For example: A folder can be created under the below shared path:
/home/vson/eData/userInputFiles
The VSON user must have permission to read the CSV or ZIP files.
2.1.1.3 Open IM format support

The Open IM format facilitates the usage of a previously generated IM along with the IM obtained from
the current measurements (either obtained directly using measurement records or using vendor ag-
nostic IM CSV). The GFO module supports the Open IM format. In Open IM format, the file is expect-
ed to be a CSV file with the following columns:
• Interfered Cell (Cell Global Identifier (CGI) format Mobile Country Code (MCC)-Mobile Network
Code (MNC)-Location Area Code (LAC)-Cell Identifier (CI))
• Interfering Cell (CGI format MCC-MNC-LAC-CI or EXT bcch:bcc:ncc for external cell)
• Co-channel CIP (in %)
• Adjacent Channel CIP (in %)
• Measurement type (Frame Erasure Probability (FEP) or Co-channel Interference Probability Aver-
age Received Power (CIP_ARP))
• Distance (in km)
• Blind Spot (Yes or No)
• Number of Samples (Integer)
The files will be available in:

/home/vson/eData/userInputFiles/openIM which is accessible from GUI and task servers.
Note:
• If you do not want to use the previous IM files, then you must delete them manually from
the above mentioned location.
• The parent directory name of the vendor agnostic IM CSV file(s) should be the manag-
ing OSS name. If the name does not match the region name in EdenNet, then the cell
should be resolved based on the cell name, otherwise cell should be resolved with cell
name within the region corresponding to region name.
For a given interfered cell and interfering cell pair, if there are values in both measurement records and
the Open IM CSV file then the value corresponds to the maximum value of:
(0.5 * Co-channel CIP + 0.2 * Adjacent channel CIP)
Otherwise, whichever value exists either in the measurement records or in the Open IM CSV file is
taken against the given interfered cell and interfering cell pair.
The GFO module supports FEP interference data only. If the CIP_ARP is provided in the Open IM
CSV file, then it will be scaled to FEP using the settings defined in the interference matrix INI file.
If a given interfered cell and interfering cell pair is marked as a blind spot in the Open IM CSV file, then
the value is not considered. Instead, the corresponding value in the measurement record is used.
2.1.2 Interactions
Dynamic Frequency Channel Assignment (DFCA) is an optional feature in the BSCs starting from
S11.5 version. DFCA allocates frequency channels dynamically to the Traffic Channel (TCH) trans-
ceivers (TRXs) based on the interference calculated in the network.
Note:
• Frequency planning must be done by ensuring network freeze. This is needed during the
measurement collection till the results are validated.
• If target BSCs contains BTSs where DFCA is activated, the frequency changes proposed
by the GFO module will be overridden by the DFCA in the respective BTSs.

GSM Frequency Optimization Guide DN09257997 1-1 GFO functional description and
guidelines
3 GFO functional description and guidelines

The GFO module creates a new frequency plan based on the interference information from the inter-
ference matrix. Interference is presented as Frame Erasure Probability (FEP). The GFO module us-
es the total FEP measurement to generate the FEP interference matrix based on the Motoring period
parameter set in the GUI configuration parameters. Interference matrix consists of a set of measured
interferers for a given BTS. This provides a measure of interference by indicating the probability of co-
channel and adjacent-channel interference.
For every GSM band, separate frequency groups can be defined for the Broadcast Control Channel
(BCCH) and the Traffic Channel (TCH) layers. The GFO module supports both frequency channel opti-
mization and Base Station Identity Code (BSIC) optimization.
You can turn ON or OFF:
• Frequency optimization for each band and for each layer within the band.
• BSIC allocation for each band.
• Mobile Allocation Index Offset (MAIO) and Hopping Sequence Number (HSN) optimization for the
given scope of execution.
The GFO module supports the following modes of frequency channel optimization and BSIC optimiza-
tion:
• Fast: The fast mode allocates frequency channel or BSIC changes quickly to the given target
cells. This mode provides a rough idea about the allocation based on the given set of input para-
meters, thereby, enabling modification of the input parameters (frequency group contents, Mobile
Allocation List (MAL) length and so on) to get the desired output.
• Optimize: The optimize mode is suitable for a small number of target cells, where a decent set of
frequency channel or BSIC changes are observed.
• Accurate: In accurate mode, you need to specify the duration of the execution. It provides the best
frequency channel or BSIC changes. Higher the duration, better is the output. Accurate mode is
recommended to obtain a practically feasible frequency plan.
Separation violation criteria for frequency channels can be defined for each layer (BCCH or TCH)
and band combination. As the algorithm used for optimization is cost-based, if a criteria is violated,
the corresponding violation cost is added for the given transceiver (TRX). By modifying the viola-
tion cost, the importance for given criteria can be altered. Higher the cost of violation, higher is the
importance of the corresponding criteria.
Hopping mode can be defined for each TCH layer of each band. The GFO module supports:
• No hopping: The BCCH layer does not support hopping.

• Baseband: The baseband hopping involves assigning frequencies to the TCH TRXs along with
Hopping Sequence Number (HSN). Nokia vendor requires two HSN parameters. One for zero
time slot TRXs (except for BCCH TRX) and the other for non-zero time slots of all TCH TRXs. All
other vendors require only one HSN parameter corresponding to the TCH TRXs.

guidelines
• Synthesized hopping (also known as RF hopping): Synthesized hopping mode are of two types:
– Cell hopping
– Site hopping
Note: When site hopping mode is selected for allocation, it is advisable that all the
cells in a given site must be in the scope. All the cells with the same site_id in the
cell plan data are assumed to be co-site cells.
When synthesized hopping mode is selected for a given TCH layer of each band, the Mobile Allocation
List (MAL) is configured against the layer. MAL contains a list of the frequencies to be used either on
a set of BTS having same segment or cell ID under a given site (cell hopping) or a set of all BTSs un-
der a given site (site hopping). When synthesized hopping is used, the same HSN is allocated to BTSs
such that it is used by all the TCH TRXs using the given MAL. The MAL length will be at least equal
to the number of TRXs in cases where the number of TRXs using the MAL is greater than maximum
MAL length in both simple and complex MAL length calculation strategies.
Note:
• HSN allocation assigns HSN values only from 1 to 63, representing random hopping.
• Existing hopping mode of the cells should be the same as the hopping mode that is de-
fined in the GFO settings for the Ericsson or Huawei cells.
Minimum and maximum MAL length can be defined for each TCH layer of each band. MAL allocation
can be turned ON or OFF for each TCH layer of each band. MAIO step and MAIO offset are allocated
as part of MAIO optimization. The traffic channels with the same HSN hop over the same frequencies
in the same order but are separated in time by a MAIO and next frequencies are chosen based on the
MAIO step.
Note:
• Simple and complex mode of MAL length calculations are supported. Simple mode con-
siders frequency load parameter along with the number of TRXs in a given BTS, cell
(synthesized cell hopping), or in a site (synthesized site hopping). Whereas, complex
mode considers the traffic load situation to evaluate the length of MAL in addition to the
frequency load parameter and number of TRXs.
• In case of both simple and complex MAL length calculation strategies, if the number of
TRXs using the MAL is greater than the maximum MAL length or proposed MAL length,
then the MAL length will be at least equal to the number of TRXs.
• Before performing the frequency optimization, Nokia recommends performing MO up-
load or similar operations supported in the respective OSS. This helps to synchronize the
configuration data of the OSS with the data configured in network elements. It is also ad-
vised to delete empty or unused MAL objects in the BSCs planned to be optimized.
Instantaneous Bandwidth support

guidelines
The GFO module supports configuring maximum Instantaneous Bandwidth (IBW) for the target BTSs.
IBW corresponds to the maximum difference between frequencies allocated to TRXs of a given BTS.
This feature is required to support the hardware limitation of the BTS. If the target BTS list contains
BTS with different maximum IBWs, minimum of the IBW values must be used in the GUI. Else, dif-
ferent scope of target BTSs can be defined and corresponding maximum IBW can be provided in the
GUI.
The GFO module supports planning frequencies for new (additional) transceivers (TRXs) and assigns
new frequencies to it. The feature is supported for Nokia, Ericsson, and Huawei vendors.
Additional TRX Support
A new sheet New TRX Assignment is added to the GFO module configuration file. In the New TRX As-
signment sheet, specify the Cell CGI for the cell where additional TRXs have to be added, the num-
ber of TRXs to be created, and the band. The new TRXs is created under the BTS with the same band
within the cell. If the cell has both primary and secondary BTSs, and they belong to the same band
as the band of the planned TRXs, the new TRXs will be created under the primary BTS. DNs are as-
signed to the new TRXs by incrementing the existing TRX count. The algorithm considers the planned
TRXs along with the actual one for a cell during frequency planning. The Mobile Allocation (MA) lists
created as part of the algorithm also includes the frequencies assigned for the planned TRXs.
The plan generated by the module will only propose the frequencies for the new TRX and update the
MA list or DCHNO list as applicable for the vendors. The maio, maio offset, and maio step values
will be added to the plan based on whether there is any change existing after recalculation.
The Managed Objects (MOs) corresponding to the TRX (TRX for Nokia and GTRXCHANHOP for
Huawei) and other necessary MOs for the new TRX must be created before provisioning the plan
proposed by the module.
The plan generated by the module does not create any new TRXs or the required supporting MOs for
the TRX and maio values.
TSC parameter change
When BCC of the primary BTS is updated for Nokia, all the TRXs under it and the TRXs under
corresponding secondary BTS must have tsc parameter (CM parameter) updated with the same
value as set for the BCC of the primary BTS.
3.1 Operational modes of GFO

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

• Closed loop mode
3.1.1 Open loop mode

In open loop mode, parameters are not pushed to the network automatically.

guidelines
During open loop operation, a plan is generated and can be provisioned to the network. The plan con-
tains changes in frequency channel, Base Station Identity Code (BSIC), Mobile Allocation List (MAL),
and Hopping Sequence Number (HSN). It is valid only for NetAct Advanced Configurator (NAdC)
based EdenNet deployment.
• The GFO module considers the parameters configured in the GUI, Excel configuration file, and
the INI file. The default frequency groups defined in the GFO module configuration file for a given
band and layer are considered for allocation. The hopping mode to be used for the target cells is
also defined in the GFO module configuration file. Additionally, the GFO module avoids allocation
of forbidden frequencies for a given set of cells. User defined frequency groups can be defined in
the User defined frequency groups Excel file.
• An interference matrix is created for the BSCs containing the target cells and the neighboring
BSCs which have either incoming or outgoing neighbor relations with the target cells. Additionally,
BSCs for which the interference matrix should be retrieved can be provided in the INI file.
• Based on the allocation status, frequency channels and BSIC parameters are allocated to the
target cells which are provided in the output report.
Open loop mode with deferred provisioning (only for NAdC (NetAct Advanced Configurator) in-
tegration)
When the GFO module runs in open loop mode, the plan is visible under SON Modules → Status →
Provisioning Logs.
• When the module run is successful, an entry appears in the provisioning logs area. The provision-
ing status is set as waiting till the plan is provisioned or till it expires.
• When a plan is scheduled, the provision status will be changed to Scheduled. For direct OSS inte-
gration, open loop does not generate a plan.
• If the cells in the plan are a part of the SON module exclusion list, or if they are not a part of the
user’s geofence, the plan will not be provisioned. In such cases, the status remains as waiting and
even the scheduled plans are moved to waiting status.
• The validity of the plan is for a period of 24 hours. The plan validity period can be configured. The
plan expires after the validity period and the user is not allowed to provision the plan.
For more details, see the Editing plan lifetime validity for open loop section in the EdenNet User
and Administration Guide.
• The user can reschedule and cancel schedules.
3.1.2 Closed loop mode
In the closed loop mode, changes are applied to the network. The GFO module generates a plan file
for the proposed changes to the parameters, which must be sent to the OSS.
The plan is pushed only during the maintenance window. If it is out of maintenance window, the plan
gets scheduled to be pushed in the next maintenance window. The automatic verification and rollback
(AVR) operation is triggered only after a successful push. For more information on AVR, see Automatic
verification and rollback.

guidelines
Note:
• The closed loop execution is supported only for Nokia and Ericsson vendor.
• Before executing the algorithm in the closed loop mode, execute the GFO module in the
open loop mode and verify the proposed plan.
• If the GFO module has scope cells from both connected OSS (enabled) and discon-
nected OSS (disabled) in the closed loop mode, the module run will be overridden to
open loop mode. If not overridden, the plan will be provisioned only for connected OSS,
which then creates an inconsistency in the network. This scenario is applicable only for
MORAN (Multi Operator Radio Access Network) enabled networks.
For more information on disabling OSS access, see Disabling OSS access for a
disconnected OSS section in the EdenNet User and Administration Guide document.

GSM Frequency Optimization Guide DN09257997 1-1 GFO algorithm
4 GFO algorithm
The GFO module uses a constructive stochastic greedy algorithm to organize the transceivers (TRXs)
according to the required separation constraints. The GFO module uses Simulated Annealing which is
a deep learning algorithm based on energy models.
1. In the initialization phase, the algorithm tries to find an allocation fulfilling all the separation con-
straints. If this is not possible, the algorithm retains the most important separation constraints and
violates only the less important separation constraints. Initialization phase uses the lowest avail-
able channels for the frequency allocation. Therefore, they are used more often than the highest
channels. This skewness may cause bias to the interference minimization. In an optimal allocation,
the spectrum is used evenly.
2. In the second phase, the algorithm removes the bias caused by the initialization phase so that the
spectrum is used evenly. This scrambling of frequencies is an iterative process changing each
TRX channel to a random available channel within the constraints. This process is repeated sever-
al times.
3. In the final phase, the algorithm modifies the frequency plan so that the interference is minimized
while maintaining all the constraints.
GFO algorithms calculate and decide frequency allocation based on the cost. Cost is nothing but the
penalty incurred due to a violation of the rules.
For example, if two neighboring cells use the same frequency, let the cost incurred be equal to 1000.
Suppose, if there are three such frequencies which are the same across the two neighboring cells, the
total cost is 3000. To minimize the cost, GFO algorithm tries to allocate three different frequencies to
the cells so that overall cost is minimum, which in this case the cost will be zero.
There are three algorithms for optimization:
• Fast: The fast algorithm is a stochastic greedy algorithm which allocates frequencies quickly. The
fast algorithm stops execution as soon as it finds the first solution with minimum network cost.
However, it can be used to get a rough idea of the quality of the allocation. The fast algorithm is
very useful when only a few missing frequencies need to be allocated without disturbing the rest of
the allocation. In this way, possible parameters and other errors can be found and corrected in the
early phase. This algorithm also provides a good optimization reference point for the accurate al-
gorithm.
• Optimize: The optimize algorithm is a stochastic greedy algorithm that starts from the current allo-
cation. It can only make changes, if the allocation gets better.
• Accurate: The accurate algorithm consumes more time and should be used for the actual alloca-
tion that will be implemented in the network. The accurate algorithm provides allocations close to
the most optimal one within a reasonable amount of time.
The accurate algorithm is a simulated annealing based algorithm. You can allocate the time for
this algorithm. The accurate algorithm generates better results when more time is allocated for its
execution.

GSM Frequency Optimization Guide DN09257997 1-1 GFO algorithm
Because both the algorithms are stochastic, they can provide slightly different allocations each time,
even when the allocation problem remains the same. For fast algorithm, the standard deviation of the
results is large. However, for the accurate algorithm, the standard deviation of the results is small and
it is smaller if the available time is increased.
The optimization algorithms are executed in the following order:
1. Frequency optimization: Allocates Broadcast Control Channel (BCCH), Traffic Channel (TCH), and
Mobile Allocation List (MAL) frequencies using the measured interference in the network, based
on the settings and user defined constraints. This allows reduction in interference in the network
which in turn improves the channel quality in the network.
2. Base Station Identity Code (BSIC) optimization: Allocates BSIC (Network Color Code (NCC) and
Base Station Color Code (BCC)) codes to the cells to minimize the BCCH-BSIC collision in the net-
work. The codes are allocated based on the reuse distance configured in the EdenNet GUI and the
BCCH frequency proposed by the frequency optimization. This allows unambiguous detection of
cells in the network.
3. Hopping Sequence Number (HSN) optimization: Allocates 1 to 63 Hopping Sequence Number
(HSN) (corresponds to pseudo random sequence used in random hopping) to the cells or BTS
based on the reuse distance configured in the EdenNet GUI and the output of the frequency opti-
mization. This is applicable only when the baseband or synthesized hopping mode is used. This
reduces the probability of interference of the same frequency channels at a given point in time.
4. Mobile Allocation Index Offset (MAIO) optimization: Allocates MAIO step and offset for the mo-
bile allocation list associated with the cells in the network. The MAIO step and offset are allocat-
ed based on the output of frequency optimization and HSN optimization. MAIO optimization allows
separation of frequency channels in time domain when same HSN is used between cells having
the same frequency channels.

GSM Frequency Optimization Guide DN09257997 1-1 Configuring and executing GFO module
5 Configuring and executing GFO module

To configure and execute the GFO module, you must access the GFO module from EdenNet and configure few parameters.
Configure and execute the GFO module in the following order:
1. Accessing GFO
2. Configuring targets for GFO
3. Configuring parameters for GFO
4. Selecting the configuration file for GFO
5. Selecting execution type for GFO
6. Confirming execution for GFO
Note:
Known Restrictions
GFO module execution results are known to be dependent on FC: 'Accurate' algorithm
execution time and hence execution results have to be carefully validated by looking
at the improvement in the violation and interference cost at each layer for each band. It
is recommended to execute multiple runs with different FC: 'Accurate' algorithm exe-
cution time settings of 4 hrs, 8 hrs, 12 hrs, 24 hrs and so on, so that one can compare
improvement in violation and interference cost across multiple runs before choosing the
best plan to provision.
5.1 GFO prerequisites

Before running the GFO module, ensure the following:
• GFO module is imported, activated and integrated with the respective Element Management Sys-
tem (EMS) or Network Management System (NMS). For example, NetAct, in case of Nokia. For li-
cense details, see License.
• PM data and CM data for GFO module must be available.
• Select the GSM cells in scope.
• Import module configuration file (INI file). For more information, see Configuring INI parameters.
• Google Chrome or Mozilla Firefox are the recommended browsers to access EdenNet.
5.1.1 License
The following license must be installed to activate GFO module.

Licensed feature Licensed feature component

LK item code LK item object name
component code name
ENSW6117CLK GSM Frequency Optimiza- 0000027101 2G Frequency Optimization

tion CLK
Table 3: GFO License
5.1.2 PM data and CM data for GFO module

PM and CM data used by the module for each vendor are listed in the following documents:
• EdenNet module specific Data for Nokia

• EdenNet module specific Data for Huawei
• EdenNet module specific Data for Ericsson
5.2 Accessing GFO

Log in to the EdenNet application and access the GFO module to perform any action on the module.
Prerequisites
All the prerequisites mentioned in the GFO 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 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. Click EdenNet modules → GSM_Frequency_Optimization.
Expected outcome
The GSM_Frequency_Optimization module is accessed and the Configure Targets page

appears.
4. Continue with Configuring targets for GFO.
5.3 Configuring targets for GFO

In EdenNet, the GFO 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 GFO.
1. Select the GSM cells for configuration by:
• filtering specific cells on map based on Topology Filter or Center Frequency Filter and then
select target cells from the map
Or
• filtering specific cells on map based on Topology Filter or Center Frequency Filter and then
select all filtered items by clicking
Or
• cell ID search selection tools from the map toolbar

Or
• selecting existing clusters
The selected cells appear in the Selections pane. For more information about selecting cells, see
the Selecting cellsSelecting cells section in the EdenNet User and Administration guide.
2. Click Next.
Expected outcome
The target cells are selected and the Configure Parameters page appears.
3. Continue with Configuring parameters for GFO.

5.4 Configuring parameters for GFO

To execute the GFO module, you must configure a set of parameters. In the Configure Parameters page, a list of parameters,
along with the descriptions and default values are displayed.
Prerequisites
• Successful completion of Configuring targets for GFO.
1. Define the configuration parameter values. For the list of parameters, see GFO GUI parameters.
Note:
• You can retain the default values or else select the values from the drop-down list.
• To revert to the default parameter value, click the Default Value icon.
2. Click Next.
Expected outcome
The parameters are configured and the Select Configuration File page appears.
3. Continue with Selecting the configuration file for GFO.
5.5 Selecting the configuration file for GFO

You can select configuration files from the list of available configurations.
Prerequisites
• Successful completion of Configuring parameters for GFO.

• Ensure that the required configuration files are activated. For more details, see Configuring INI pa-
rameters.
1. Select the required configuration files from the GFO Preferences and the Interference Matrix
Configuration categories.
Note: You can select only one configuration file from each category.
2. Verify the configuration in the right pane and click Next.

Expected outcome
The configuration file is selected and the Execution Type page appears.
3. Continue with Selecting execution type for GFO.
5.6 Selecting execution type for GFO

In the Execution type page, you can schedule when the GFO 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 Configuring parameters for GFO.
1. To schedule the module execution, select one of the following options:
• Activate Now - to activate the module immediately.

• Activate Later - to activate the module at a later time.
• Schedule Execution - to schedule the module for execution during a certain date and time.
For more information about Activate Later and Schedule Execution, see Configuring execution
typeConfiguring 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 GFO.
5.7 Confirming execution for GFO

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 execution type for GFO.
Procedure
• Verify the configuration summary, click Finish.

Note: You can monitor the operation. For more information, see Monitoring GFO .
Expected outcome
GFO module is executed based on the configuration parameters and as per the defined schedule.

GSM Frequency Optimization Guide DN09257997 1-1 GFO configuration parameters
6 GFO configuration parameters

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

• GFO interference matrix configuration INI file
6.1 GFO GUI parameters

Table 4: Graphical user interface parameters lists the parameters that can be configured in the Eden-
Net GUI.
Default val-
Parameter name Description Range (min, max) Step
ue
Monitoring period FEP co-channel and adja- 1-14 days 1 1

cent channel interference
values are aggregated over
the defined monitoring peri-
od. Also, Average CS traffic
and TCH blocking KPIs are
fetched based on the value
of the monitoring period.
Start hour of main- This parameter indicates the 0 - 23 hours N/A 0

tenance window start time for pushing the
parameter changes to the
network when the module is
run in closed loop. Changes
will be provisioned after this
time.
End hour of main- This parameter indicates the 0 - 23 hours N/A 3

tenance window end time for pushing the pa-
rameter changes to network
when the module is run in
closed loop. Changes will
not be provisioned after this
time.
Consider external Indicates if the interference Yes, No N/A No

cells from external cells is consid-
ered to create the interfer-
ence matrix.

Default val-
ue
Mobile Allocation Indicates if the MAL length User Defined, De- N/A User Defined
List (MAL) length is adjusted based on the fault
adjustment cell's hopping mode. It is
useful when the hopping
mode of the cell is set to ei-
ther Synthesized cell hop-
ping or Synthesized site
hopping.
If the parameter is set to
User Defined, then MAL
length is computed based
on user defined MAL
Length Calculation Mode
(Simple or Complex) for a
given layer in the settings
XLSX file.
If the parameter is set to
Default, then MAL length is
computed as the maximum
value of number of TRXs
and the user defined
minimum MAL length.
Frequency Chan- Indicates if the frequency Yes, No N/A Yes

nel (FC) Optimiza- planning is performed on
tion the selected target cells.
Base Station Iden- Indicates if BSIC planning is Yes, No N/A Yes

tity Code (BSIC) performed on the selected
Optimization target cells.
Hopping Se- Indicates if HSN planning is Yes, No N/A Yes

quence Number performed on the selected
(HSN) Optimiza- target cells.
tion
Mobile Alloca- Indicates if MAIO planning Yes, No N/A Yes

tion Index Offset is performed on the select-
(MAIO) Optimiza- ed target cells. It is also ap-
tion plicable when the hopping
mode of the cell is set to ei-
ther Synthesized cell hop-

Default val-
ue
ping or Synthesized site

hopping.
Fix Violations Ag- If the Fix Violations True, False N/A False
gressively Aggressively parameter
is set to True, the GFO al-
gorithm tries to balance in-
terference and separation
violations thereby produces
plan with least possible vi-
olations in a heavy inter-
ference network limited by
number of channels.
If the Fix Violations
Aggressively parameter
is set to False then
interference are treated
higher in priority with
respect to violations.
Violation Cost Indicates the threshold val- 1 to 10000 N/A 10000

Margin ue of total violation cost. Be-
yond this value violations
are fixed aggressively.
FC: Optimization Indicates the type of plan- Fast, Optimization, N/A Fast
algorithm ning algorithm to be used. Accurate
If set to Fast, then stochas-
tic greedy algorithm is used,
which helps to plan the fre-
quencies in a short time.
Fast algorithm provides the
first set of optimal frequen-
cies. If set to Optimization,
then stochastic greedy algo-
rithm is used, which consid-
ers the existing frequencies
to optimize the frequency
planning. If set to Accurate,
then simulated annealing al-
gorithm is used to plan the

Default val-
ue
frequencies which provides

the best frequency planning.
FC: 'Accurate' al- Indicates the duration of Ac- 1-2200 minutes 1 minute 720 minutes
gorithm execution curate algorithm execution.
time
FC: Average inter- If the FC: Average Yes, No N/A No

ference interference parameter
is set to Yes, then
interference cost is more
than separation violation
cost. Therefore, more
emphasis is given to
interference reduction.
If the FC: Average

interference parameter
is set to No, then separation
violation cost is more
emphasized than
interference cost.
BSIC: Forbidden List of globally forbidden 0-7 N/A N/A

NCC Network Color Codes
(NCC). Enter NCC as com-
ma separated values. A
range of values is also al-
lowed, for example: 0, 1-3,
7.
BSIC: Forbidden List of globally forbidden 0-77 N/A N/A

BSIC BSIC (Combination of NCC
and BCC). Enter BSIC as
comma separated values.
For example: 00, 34, 75.
BSIC: Limit by dis- The BSIC: Limit by Yes, No N/A Yes

tance distance parameter is
used to achieve collision
free BSIC allocation when
BCCH frequency reuse is
high. When the parameter

Default val-
ue
is disabled, all the cells hav-

ing same BCCH frequency
are considered to allocate
collision free BSIC for a giv-
en cell. When the parameter
is enabled, BSIC algorithm
considers only closest cells
having same BCCH fre-
quency, whose distance is
less than or equal to BSIC:
Maximum distance.
BSIC: Maximum The BSIC: Maximum 1-200 km 1 km 60 km

distance distance parameter is
used to further reduce the
number of distance based
cells in the buffer area
having the same BCCH
frequency as the given cell
to achieve collision free
BSIC allocation. Cells which
are neither adjacent or
second adjacent but within
this maximum distance is
considered in the buffer
area to allocate collision
free BSIC for a given cell.
The BSIC: Maximum
distance parameter is
used when BSIC: Limit
by distance parameter is
enabled.
BSIC: Limit by The BSIC: Limit by Yes, No N/A Yes

cells cells parameter is used to
achieve collision free BSIC
allocation when BCCH fre-
quency reuse is high. When
this parameter is disabled,
all the cells having same
BCCH frequency are con-

Default val-
ue
sidered to allocate colli-

sion free BSIC for a giv-
en cell. When this parame-
ter is enabled, BSIC algo-
rithm considers only closest
cells having same BCCH
frequency, number equal to
BSIC: Maximum number
of cells – (Number of
adjacency and second ad-
jacency cells having same
BCCH frequency as given
cell).
BSIC: Maximum The BSIC: Maximum 1-2000 1 500

number of cells number of cells
parameter is used to further
reduce the number of
distance based cells in
the buffer area having the
same BCCH frequency
as the given cell to
achieve collision free
BSIC allocation. Adjacent
and second adjacent
cells having the same
BCCH frequency are
always considered in the
buffer. If their sum is less
than maximum number
of cell values, then the
other closest cells are
considered such that the
amount of closest cells
is the difference between
maximum number of cells
and sum of adjacent and
second same BCCH cells.
The BSIC: Maximum
number of cells
parameter is used when

Default val-
ue
BSIC: Limit by cells

is enabled.
BSIC: Optimiza- Indicates the type of plan- Fast, Fix Collisions, N/A Fast
tion algorithm ning algorithm to be used. Accurate
If set to Fast, then stochas-
tic greedy algorithm is used,
which helps to plan the
BSIC in a short time. Fast
algorithm provides the first
set of optimal BSIC values.
If set to Fix collisions, then
stochastic greedy algorithm
is used, which considers the
existing BSIC values to de-
tect collisions and resolve
the same. If set to Accurate,
then simulated annealing al-
gorithm is used to plan the
BSIC values which provide
the best BSIC planning.
Note: Effective-
ness of the Ac-
curate algorithm
depends on the
duration of exe-
cution. When the
Accurate algo-
rithm is allowed
to run for a longer
duration, it pro-
duces a better
BSIC plan.
BSIC: 'Accurate' Indicates the duration of the 1-2200 minutes 1 minute 60 minutes
algorithm execu- Accurate algorithm execu-
tion time tion.
BSIC: Allocate Indicates if the same BSIC Yes, No N/A No

same BSIC for co- is allocated for co-site cells.
site cells

Default val-
ue
HSN: Limit by dis- The HSN: Limit by Yes, No N/A Yes

tance distance parameter en-
ables the usage of reuse
distance defined in HSN:
Maximum distance para-
meter for HSN allocation.
If HSN: Limit by
distance parameter is
set to No, then the reuse
distance is considered as
an integer maximum value -
2147483647.
HSN: Maximum The HSN: Maximum 1-200 km 1 km 60 km

distance distance parameter
serves as a threshold for
including distance based
colliding cell pairs for
resolution, where distance
between colliding cell pairs
is less than or equal to the
threshold.
HSN: Limit by Indicates if the number of Yes, No N/A Yes

cells cells to be considered for in-
terference analysis per tar-
get cell is limited to the de-
fined threshold.
If HSN: Limit by cells

parameter is set to Yes, it
limits the number of cells
defined as HSN: Maximum
number of Cells
parameter within the reuse
distance, which is either
HSN: Maximum Distance
or an integer maximum
value - 2147483647 (all the
cells in target and buffer).

Default val-
ue
HSN: Maximum The HSN: Maximum 1-2000 1 500

number of cells number of cells
parameter serves as a
threshold for including other
cells in the target and buffer
area, for a given cell, for
considering unique HSN
allocation.
User defined fre- Assign custom frequen- N/A N/A N/A

quency groups cy group to the cells in the
form of an XLSX file input.
The XLSX file should con-
tain the Frequency Groups
sheet, the Separation Vio-
lations Penalties sheet cor-
responding to the frequen-
cy group, and the Frequen-
cy Group Assignment sheet.
If an user defined frequen-
cy group is assigned to a
cell, then the channels, vio-
lations, and penalties corre-
sponding to the user defined
frequency group is used.
Other cells will use the de-
fault settings. If multiple fre-
quency groups are assigned
to a cell, the respective fre-
quency groups are used de-
pending on the bands sup-
ported by the cell. If multiple
frequency groups belong-
ing to the same band and
the same layer of the cell
are assigned, then the last
frequency group is used for
that cell.

Default val-
ue
Maximum Instan- Maximum Instantaneous 0-10000 MHz 1 0

taneous Band- Bandwidth (IBW) represents
width the maximum continuous
bandwidth supported by
BTS. Frequency allocation
will consider the IBW such
that the difference between
the highest and the low-
est frequency assigned to
a BTS is within the defined
bandwidth. If set to 0, then
this parameter is ignored.
Consider PGSM Indicates whether the fre- Yes, No N/A No

and EGSM sepa- quency stored in the BCCH
rately in the BCCH frequency group should
frequency group be treated as PGSM and
EGSM separately. The
BCCH frequency are allo-
cated either from PGSM or
EGSM sub group. The fre-
quency allocation depends
original BCCH frequency
used in the given cell. If
set to No, both PGSM and
EGSM frequency channels
are considered for allocation
of BCCH frequency regard-
less of the original BCCH
frequency used in the given
cell.
Consider PGSM Indicates whether the fre- Yes, No N/A No

and EGSM sepa- quency stored in the TCH
rately in the TCH frequency group should
frequency group be treated as PGSM and
EGSM separately. The TCH
frequency are allocated ei-
ther from PGSM or EGSM
sub group. The frequen-
cy allocation depends on

Default val-
ue
the original TCH frequency

used in the given cell.
If set to No, both PGSM and

EGSM frequency channels
are considered for allocation
of TCH frequencies through-
out the cell.
Use exclusive fre- The Use exclusive Yes, No N/A Yes

quency channels frequency channels
for PGSM and for PGSM and EGSM
EGSM parameter setting is used
when PGSM and EGSM fre-
quency channel separation
is enabled for either BCCH
or TCH frequency group.
If set to Yes, GSM 900

BCCH or TCH frequency
groups will have a unique
set of PGSM and EGSM fre-
quency channels.
If set to No, then EGSM

sub-group will have PGSM
frequencies.
Medium Traffic This parameter is used for 0 to 10000 N/A 500 Erlangs
Level complex MAL allocation and
indicates the threshold lev-
el of average CS traffic of
a cell, above which the cell
traffic is considered to be at
a medium traffic level, un-
less the average CS traffic
is below the high traffic lev-
el.
High Traffic Level This parameter is used for 0 to 20000 N/A 1000 Erlangs
complex MAL allocation and
indicates the threshold lev-
el of average CS traffic of a
cell, above which cell traffic

Default val-
ue
is considered to be at a high
level.
Delta Increase This parameter is used for 0 to 63 N/A 2

Medium Level complex MAL allocation, for
Traffic cells having medium level
traffic. It indicates the delta
increase in MAL length for
medium traffic cells.
Delta Increase Indicates the delta increase 0 to 63 N/A 3

High Level Traffic in MAL length for high traf-
fic cells. This parameter is
used for complex MAL allo-
cation, for cells having high
level traffic. This
KPI Verification Indicates the period of eval- 0 to 24 hrs N/A 6 hrs

Window uation of KPIs after plan
provisioning is completed.
SON Operation To run the GFO module • Open Loop N/A Open Loop
Mode in open loop mode, set • Closed Loop
the SON Operation
Mode parameter to
Open Loop. In open loop
mode, the module does
not automatically push
parameter changes to the
network. The user has to
manually provision plans
to push changes to the
network.
To run the GFO module in

closed loop mode, set the
SON Operation Mode
parameter to Closed Loop.
In closed loop mode,

changes are automatically
pushed to the network with-
out user intervention.

Default val-
ue
Plan Name Tag Text that is added to the Sequence which N/A N/A
names of all the plans that contains any combi-
are generated by the GFO nations of:
module.
• Uppercase and
If the target of the module lowercase let-
is a whole cluster and the ters: [A-Za-z]
name of this cluster satis- • Numbers: [0-9]
fies the requirements spec- • Underscore: _
ified in the Range column,
Maximum length:
the cluster name will also be
20 characters
added to the plan name.
Table 4: Graphical user interface parameters
6.2 GFO interference matrix configuration INI file

To import the interference matrix configuration INI file, see Configuring INI parameters.
Note: You must import the interference matrix INI file under the Interference Matrix Config-
uration category.
Parameter Description Range Step Default value
blind_spot_co_ch Indicates the co- 0 to 100% 1% 3%

channel interfer-
ence probability
percentage value
to be used for all
the identified blind
spot cells
blind_spot_adj_ch Indicates the adja- 0 to 100% 1% 1%

cent channel inter-
ference probability
percentage value
to be used for all
the identified blind
spot cells.
search_distance Distance in km 0 to 1000 km 1 km 70 km

within which in-

terferers having
the same BSIC
and BCCH value
should be consid-
ered.
blind_spot_count Indicates num- 0 to 100 1 3

ber of cells with
the same BCCH
frequency as the
source cell to be
added as interfer-
ers
Buffer_BSCs List of BSCs which Semicolon sepa- N/A N/A

should be consid- rated BSC DNs
ered while retriev-
ing interference
matrix in addition
to the adjacent
BSCs and set of
target cells given
as input. This can
be defined per re-
gion.
co_channel_re- Indicates the co- 0 to 100 0.001 0.001

trieval_threshold channel threshold
percentage below
which an interferer
is neglected.
path_to_measure- Resource path Path in the GUI N/A Empty

ment_files from where raw server of EdenNet
interference CSV where the CSV
files need to be file/ Raw measure-
imported. ment folders is
placed.
In case multiple
OSSs are
connected to
EdenNet, then
the measurement
files of each OSS
must be placed

in the respective
managing_oss
named folders.
If no inputs are
provided, the de-
fault value will be
used.
date_and_time_ Indicates whether Combined, N/A Combined

columns date and time Separate
columns are
present togeth-
er or in separate
columns in the
mentioned in the
vendor agnos-
tic IM CSV file.
It is set to Com-
bined if in the raw
measurement
CSV files, the date
and time stamp is
combined. Else, it
is set to Separate.
date_format Indicates the date ( %d/%m/%Y, %d- N/A %d/%m/%Y

format used in the %m-%Y, %d:%m:
raw measurement %Y)
files. The accept-
ed formats are:
• %d-%m-%Y
(for example,
12-03-2017)
• %d/%m/%Y
(for example:
01/12/2016)
• %d:%m:%Y
(for example:
23:09:2016)
time_format Indicates the time ( %H:%M:%S) N/A %H:%M:%S

format used in the

raw measurement
files. The accept-
ed format is: %H:
%M:%S (for ex-
ample: 12:12:23)
db1_co Indicates the DB1 0 to 1 0.0001 0.9656 (corre-

threshold used in sponds to -12 dB
FEP conversion threshold from the
formula. Value lookup table)
should be provid-
ed from the lookup
table (DB offset
value lookup ta-
ble) given below,
corresponding to
the CIR used for
scheduling mea-
surements in the
network. The CIR
corresponds to
the moderate in-
terference sample
threshold used in
generating mea-
surement CSV file.
For more informa-
tion on the DB off-
set value lookup
table, see DB off-
set value lookup
table.
db2_co Indicates the DB2 0 to 1 0.0001 0.9303 (corre-

threshold used in sponds to -9 dB
FEP conversion threshold from the
formula. A FEP lookup table)
value that corre-
sponds to the CIR
used for sched-
uling measure-
ments in the net-
work should be

provided from the

DB offset value
lookup table. The
CIR corresponds
to the high inter-
ference sample
threshold used in
generating mea-
surement CSV file.
db1_adj Indicates the (DB1 0 to 1 0.0001 0.2438 (corre-

+ 18dB) threshold sponds to 6 dB
used in FEP con- threshold from the
version formula. lookup table)
A FEP value that
corresponds to
the CIR used for
scheduling mea-
surements in the
network should be
provided from the
DB offset value
lookup table. The
CIR corresponds
to the moderate
interference sam-
ple threshold +
18dB used in gen-
erating measure-
ment CSV file.
db2_adj Indicates the (DB2 0 to 1 0.0001 0.1328 (corre-

threshold + 18dB) sponds to 9 dB
used in FEP con- threshold from the
version formula. lookup table)
A FEP value that
corresponds to
the CIR used for
scheduling mea-
surements in the
network should be
provided from the
DB offset value

lookup table. The

CIR corresponds
to the High Inter-
ference sample
threshold + 18 dB
used in generat-
ing measurement
CSV file.
fep_co This is user mod- (dB1_Co * Mod-

ifiable formula for erate interference
FEP channel val- samples + dB2_
ue to be used in Co * High interfer-
the interference ence samples) /
matrix. (Number of sam-
ples while in BAL)
fep_adj This is user mod- (dB1_Adj * Mod-

ifiable formula for erate interference
FEP adjacent val- samples + dB2_
ue to be used in Adj * High interfer-
the interference ence samples) /
matrix. (Number of Sam-
ples While in BAL)
scaling_factor This is a scaling 0.03*X**2+0.41*X

factor to match the
cumulative dis-
tributive function
regarding Nokia
FEP. If no scaling
is intended then
use X as the val-
ue. Only Polyno-
mial equation in-
volving X is al-
lowed.
Note:
** indi-
cates
power.

Table 5: Interference matrix file
6.2.1 DB offset value lookup table
CIR FEP CIR FEP CIR FEP CIR FEP
-63 1.0000 -31 0.9997 1 0.5272 33 0.0004
-62 1.0000 -30 0.9996 2 0.4652 34 0.0003
-61 1.0000 -29 0.9995 3 0.4043 35 0.0002
-60 1.0000 -28 0.9993 4 0.3462 36 0.0002
-59 1.0000 -27 0.9991 5 0.2924 37 0.0001
-58 1.0000 -26 0.9989 6 0.2438 38 0.0001
-57 1.0000 -25 0.9986 7 0.2009 39 0.0001
-56 1.0000 -24 0.9982 8 0.1640 40 0.0001
-55 1.0000 -23 0.9977 9 0.1328 41 0.0001
-54 1.0000 -22 0.9970 10 0.1067 42 0.0000
-53 1.0000 -21 0.9962 11 0.0852 43 0.0000
-52 1.0000 -20 0.9951 12 0.0678 44 0.0000
-51 1.0000 -19 0.9938 13 0.0537 45 0.0000
-50 1.0000 -18 0.9920 14 0.0424 46 0.0000
-49 1.0000 -17 0.9898 15 0.0334 47 0.0000
-48 1.0000 -16 0.9870 16 0.0262 48 0.0000
-47 1.0000 -15 0.9834 17 0.0206 49 0.0000
-46 1.0000 -14 0.9788 18 0.0161 50 0.0000
-45 1.0000 -13 0.9730 19 0.0126 51 0.0000
-44 1.0000 -12 0.9656 20 0.0099 52 0.0000
-43 1.0000 -11 0.9564 21 0.0077 53 0.0000
-42 1.0000 -10 0.9448 22 0.0060 54 0.0000
-41 1.0000 -9 0.9303 23 0.0047 55 0.0000
-40 1.0000 -8 0.9124 24 0.0037 56 0.0000
-39 1.0000 -7 0.8904 25 0.0029 57 0.0000
-38 0.9999 -6 0.8637 26 0.0022 58 0.0000

CIR FEP CIR FEP CIR FEP CIR FEP
-37 0.9999 -5 0.8318 27 0.0018 59 0.0000
-36 0.9999 -4 0.7941 28 0.0014 60 0.0000
-35 0.9999 -3 0.7506 29 0.0011 61 0.0000
-34 0.9998 -2 0.7013 30 0.0008 62 0.0000
-33 0.9998 -1 0.6469 31 0.0007 63 0.0000
-32 0.9998 0 0.5883 32 0.0005
Table 6: DB offset value lookup table
6.2.2 Example of GFO interference matrix configuration file
The INI file is created using the configuration parameters. For more information, see GFO interference
matrix configuration INI file. The following is an example of the GFO module configuration file with de-
fault values:
[Global]
# Path to the directory where the measurement zip files or csv files are
uploaded. Specify the path only if there are any csv files uploaded.
Path_to_measurement_files =
# Specify whether the date and time columns in the csv are 'Combined' or
'Separate'. Default Combined
Date_and_Time_columns : Combined
# Mention the date format to be used when Date_and_Time_columns value is
'Separated'. Valid date formats: %d-%m-%Y, %d/%m/%Y and %d:%m:%Y.
Date_format : %d/%m/%Y
# Mention the time format to be used when Date_and_Time_columns value
is 'Separated'. Valid time format: %d/%m/%Y.
Time_format : %H:%M:%S
# Distance in km within which interferers having the same BSIC and BCCH
value should be considered. Ranges from 0 to 1000 km. Default 70km
Search_distance : 70
# Indicates number of cells with same BCCH frequency as the source cell
to be added as interferers. Ranges from 0 to 100, default 3.
blind_spot_count : 3
# Indicates the co-channel interference probability percentage value to
be used for all the identified blind spot cells. Ranges from 0 to 100%,
default 3.
blind_spot_co_ch : 3
# Indicates the adjacent channel interference probability percentage
value to be used for all the identified blind spot cells. Ranges from 0
to 100%, default 1.
blind_spot_adj_ch : 1

# The DB offset values for co-channel and adjacent channel found from
the lookup table.
DB1_Co : 0.9656
DB2_Co : 0.9303
DB1_Adj : 0.2438
DB2_Adj : 0.1328
# The CIP to FEP conversion equations; Valid variables: 'Moderate
interference samples', 'High interference samples', 'Number of Samples
While in BAL' and 'Number of samples per Victim'.
# Allowed operators: (), +,-,*,/, %, **. NOTE: '**' indicates power.
FEP_Co : (DB1_Co * Moderate interference samples + DB2_Co * High
interference samples) / (Number of Samples While in BAL)
FEP_Adj : (DB1_Adj * Moderate interference samples + DB2_Adj * High
interference samples) / (Number of Samples While in BAL)
# The polynomial scaling equation to form FEP equation; allowed variable
is 'X'.
# Allowed operators: (),+,-,*,/, %, **. NOTE: '**' indicates power.
Scaling_factor : 0.03*X**2+0.41*X
# The tuning parameters used for resolving only one interfering cell
among the list of interfering cells for the victim cell.
C1 : 2
C2 : 0
C3 : 1
C4 : 1
[Region.oss1]
# List of BSCs which should be considered while retrieving interference
matrix for given target cells. Enter BSC DNs as semi-colon (;) separated
values.
# Replace oss1 with managing oss name accordingly. Additional sections
with different managing oss can also be added.
Buffer_BSCs :
[Region.oss2]
# List of BSCs which should be considered while retrieving interference
matrix for given target cells. Enter BSC DNs as semi-colon (;) separated
values.
# Replace oss1 with managing oss name accordingly. Additional sections
with different managing oss can also be added.
Buffer_BSCs :
6.3 GFO module configuration file

The GFO module requires an Excel file containing the preferences and options for setting layers, fre-
quency groups, and separation violation penalties. The Excel file contains the following sheets:
• Frequency Bands
• Frequency Groups
• Layers

• Separation Violations Penalties

• Forbidden Assignments
• New TRX Assignment
• Verification and Rollback
Examples of the various sheets are given below:
Frequency Bands: Provides the option to enable or disable the frequency optimization and the Base
Station Identity Code (BSIC) optimization for each band. Table 7: Frequency Bands sheet displays a
sample of the Frequency Bands sheet.
Name Allocation BSIC
GSM 850 Yes/No Yes/No
Table 7: Frequency Bands sheet
Frequency Groups: Contains the channels to be used for the allocation of both Broadcast Control
Channel (BCCH) and Traffic Channel (TCH) at each band. Also, You can mention a frequency change
penalty to restrict the number of changes and preserve the existing allocation, if there are no violations
detected.
Table 8: Frequency Groups sheet displays a sample of the Frequency Groups sheet.
Frequency
Name Frequency Band Layer Channels
Change Penalty
BCCH 850 GSM 850 BCCH 0
TCH 850 GSM 850 TCH 0
TCH 900 GSM 900 TCH 0
TCH 1800 GSM 1800 TCH 0
TCH 1900 GSM 1900 TCH 0
Table 8: Frequency Groups sheet
Layers: Contains the allocation settings at BCCH/TCH level and Mobile Allocation List (MAL) related
settings for creating or updating the existing MAL object. In simple MAL length calculation mode, the

frequency load is used as a denominator in MAL length calculation to scale up the number of frequen-
cies required against the number of TRXs. In addition to the parameters used by the simple mode, the
complex mode uses traffic information to determine the number of frequencies required in the MAL.
The MAL allocation can either be turned ON or OFF for the TCH layer of each band.
The hopping mode can be set to
• No hopping
• Synthesized Cell Hopping
• Synthesized Site Hopping
• Baseband Hopping
Note:
For vendors other than Nokia, Nokia recommends that you retain the same hopping mode
that is currently used in the network.
Table 9: Layers displays a sample of the Layers sheet.
MAL
Fre- Min Max MAL Al-
TRX Alloca- Length Frequen- Hopping
Band quency MAL MAL location
Layer tion Calcula- cy Group Mode
Load Length Length Mode
tion Mode
GSM 850 BCCH Yes BCCH

850
GSM 850 TCH Yes 0.5 Simple 4 8 TCH 850 Synthesized Allocate
Cell Hopping
GSM 900 BCCH Yes BCCH

900
GSM 900 TCH Yes 0.5 Simple 4 8 TCH 900 Synthesized Allocate
Cell Hopping
GSM BCCH Yes BCCH

1800 1800
GSM TCH Yes 0.5 Simple 4 8 TCH 1800 Baseband Allocate

1800 Hopping
GSM BCCH Yes BCCH

1900 1900
GSM TCH Yes 0.5 Simple 4 8 TCH 1900 No Hopping Allocate

1900

Table 9: Layers
Separation violation penalties: Provides the ability to configure separation and its corresponding vio-
lation penalties across the BCCH and the TCH layers. The violation penalties are configured for each
band of the user defined frequency group. If the separation in frequency channel allocation could not
be achieved, penalty is added to the layer. Also, co-channel and adjacent channel interference values
can either be scaled up or scaled down. This allows the GFO module to give more importance to any
one of the two interference. The scaling factor can be set for each combination of the BCCH and the
TCH layers and across each band. Co-cell separation is about the channel separation within the cell.
Co-site separation is about the channel separation within the site (all the cells associated to a site).
Adjacent cell separation is about the channel separation among the adjacent cells. Common adjacent
cell separation is about the channel separation among adjacent cell’s adjacent cell. Similar to interfer-
ence scale, separation and its corresponding violation can be given for each combination of the BCCH
and the TCH layers and across each band.
Table 10: Separation Violation Penalties and Table 11: Separation Violation Penalties display a sample
of the Separation Violation Penalties sheet.
From
Freq To TRX CoCh Interfer- AdjCh Inter- Co-Cell Co-Cell
Band TRX
Group Layer ence Scale ference Scale Separation Violation
Layer
GSM BCCH BCCH BCCH 1.5 1.5

850 850
GSM BCCH BCCH TCH 1 1 3 10000

850 850
GSM TCH TCH TCH 0.5 0.5 3 1000

850 850
GSM TCH TCH BCCH 1 1 3 2500

850 850

900 900

900 900

900 900

900 900

1800 1800

From
Freq To TRX CoCh Interfer- AdjCh Inter- Co-Cell Co-Cell
Band TRX
Group Layer ence Scale ference Scale Separation Violation
Layer

1800 1800

1800 1800

1800 1800

1900 1900

1900 1900

1900 1900

1900 1900
Table 10: Separation Violation Penalties
Common Ad- Common Ad-

Co-Site Sepa- Co-Site Viola- Adjacent Cell Adjacent Cell
jacent Cell jacent Cell Vi-
ration tion Separation Violation
Separation olation
2 10000 1 10 0 1
2 1000 1 1 0 0
2 100 0 0 0 0
2 250 0 0 0 0
2 10000 1 10 0 1
2 1000 1 1 0 0
2 100 0 0 0 0
2 250 0 0 0 0
2 10000 1 10 0 1
2 1000 1 1 0 0
2 100 0 0 0 0


Separation olation
2 250 0 0 0 0
2 10000 1 10 0 1
2 1000 1 1 0 0
2 100 0 0 0 0
2 250 0 0 0 0
Table 11: Separation Violation Penalties
Forbidden Assignments: Indicates the forbidden channel, forbidden Base Station Color Code (BCC),
and forbidden Network Color Code (NCC) which should not be used for allocation of a given cell.
Table 12: Forbidden Assignments displays a sample of the Forbidden Assignments sheet.
Cell CGI Forbidden channels Forbidden BSIC Forbidden NCC
32-100-001-101 100,120, 125-130 00 1,4-7
Table 12: Forbidden Assignments
New TRX Assignment: The New TRX Assignment sheet contains the settings for cell CGI, addition-
al number of TCH TRXs, and band. You can specify the additional number of TCH TRXs to be consid-
ered for frequency planning along with the actual TRXs present in the network. The frequency band
that must be used for the additional TRXs must be specified for a given cell.
Table 13: New TRX Assignment displays a sample of the New TRX Assignment sheet.
Additional Number of TCH

Cell CGI Band
TRXs
222-10-11044-59991 2 GSM 900
Table 13: New TRX Assignment
Verification and Rollback: The Verification and Rollback sheet contains the KPI names, tolerance
percentage, and before KPI reference details.
• KPI Name: Indicates the name of the KPIs. The KPIs are configurable. You can configure any KPI
that is used to evaluate the cell performance post frequency allocation.
For determining the degradation in a cell, a percentage change between the old and new aggre-
gated values of the KPI is calculated. The formula used for this operation is ((new – old)/old) * 100.

For example, if the vertically aggregated KPI value in the pre-interval is 2003.8462 and in the post-
interval is 2050.0 then the percentage change is 2.3%.
• Tolerance %: Indicates the value beyond which the cell is considered as degraded.
• Before KPI Reference: Indicates the period to be selected for KPI evaluation. You can select one
of the following values:
– SAME_DAY_PREV_WEEK: Indicates that the Before KPI value is taken from the same day as
the evaluation day, but for the previous week.
– WINDOW_BEFORE_PROVISION: Indicates that the Before KPI value is taken from the time
window before successful provisioning with size equal to KPI verification window setting.
– PREV_DAY: Indicates that the Before KPI value is taken from the time window before suc-
cessful provisioning with the size equal to 24 hours. When PREV_DAY is selected as Before
KPI reference, use a higher value of KPI verification window to reduce the uncertainty.
Table 14: Verification and Rollback shows a sample of the Verification and Rollback sheet.
KPI Name Tolerance % Before KPI Reference
GSM Accessibility Sdcch Rate -0.1 SAME_DAY_PREV_WEEK
GSM Accessibility Tch Rate -0.1 SAME_DAY_PREV_WEEK
GSM Retainability Sdcch +0.1 SAME_DAY_PREV_WEEK
GSM Retainability Tch +0.1 SAME_DAY_PREV_WEEK
SDCCH Drop Rate [%] +0.1 SAME_DAY_PREV_WEEK
TCH_DropToCallEnd_Rate +0.1 SAME_DAY_PREV_WEEK
Table 14: Verification and Rollback
6.4 User defined frequency groups Excel file

If there are user defined frequency groups then definition of the frequency group and their associated
separation violation penalties for the required GSM cells in the network must be provided in the User
defined frequency groups Excel file. The Excel file contains the following sheets:
• Frequency Groups
• Separation Violations Penalties
• Frequency Group Assignment
Examples of various sheets:
Frequency Groups: Contains the user defined frequency groups and corresponding channels to be
used for allocation of both Broadcast Control Channel (BCCH) and Traffic Channel (TCH) at each
band. Also, the frequency change penalty can be given to restrict the number of changes such that

the existing allocation is preserved, if no violation is detected. The Frequency Groups sheet must con-
tain the columns as mentioned in Table 15: Frequency Groups. These column headers are also listed
in the module configuration file. The correct Frequency Band (GSM 850, GSM 900, GSM 1800, GSM
1900) and correct Layer (BCCH, TCH) need to be entered in the respective columns. Incorrect fre-
quency groups will result in an error.
Note: The name of the user defined frequency group should not be the same as the default
frequency group name.
Table 15: Frequency Groups describes the frequency groups.
Frequency
Name Frequency Band Layer Channels
Change Penalty
User BCCH 850 GSM 850 BCCH 0
User TCH 850 GSM 850 TCH 0
Table 15: Frequency Groups
Separation Violations Penalties: Provides the ability to configure separation and its corresponding
violation penalties across the BCCH and the TCH layers. The violation penalties are configured for
each band of the user defined frequency group. The Separation Violations Penalties sheet contains
the columns as mentioned in Table 16: Separation Violations Penalties and Table 17: Separation Vi-
olations Penalties. To avoid any errors in the module, you must provide all the separation violations
for a given user defined frequency group. If the separation in frequency channel allocation cannot be
achieved, a penalty is added to the layer. Also, co-channel and adjacent channel interference values
can either be scaled up or scaled down. This allows the GFO module to give more importance to the
either co-channel and adjacent channel interference. The scaling factor can be set for each combina-
tion of BCCH and TCH layers and across each band. Co-cell separation is about channel separation
within the cell. Co-site separation is about channel separation within the site (all the cells associated
with the site). Adjacent cell separation is about channel separation among the adjacent cells. Common
adjacent cell separation is about channel separation among the adjacent cell’s adjacent cell. Like inter-
ference scale, separation and its corresponding violation can be given for each combination of BCCH
and TCH layers and across each band.

Note: As, two BCCH layers cannot exist inside the same cell, do not enter any value inside
the Co-cell Separation and Co-cell Violation columns of the BCCH-BCCH combination.
Table 16: Separation Violations Penalties and Table 17: Separation Violations Penalties describe the
separation violation penalties.
CoCh In- AdjCh In-

Frequency To TRX Lay- From TRX Co-Cell Co-Cell Vi-
terference terference
Group er Layer Separation olation
Scale Scale
User BCCH BCCH BCCH 1.5 1.5

850
User BCCH BCCH TCH 1 1 3 10000

850
User TCH TCH TCH 0.5 0.5 3 1000

850
User TCH TCH BCCH 1 1 3 2500

850

1800

1800

1800

1800

1900

1900

1900

1900

900

900

CoCh In- AdjCh In-

Frequency To TRX Lay- From TRX Co-Cell Co-Cell Vi-
terference terference
Group er Layer Separation olation
Scale Scale

900

900
Table 16: Separation Violations Penalties

Separation olation
2 10000 1 10 0 1
2 1000 1 1 0 0
2 100 0 0 0 0
2 250 0 0 0 0
2 10000 1 10 0 1
2 1000 1 1 0 0
2 100 0 0 0 0
2 250 0 0 0 0
2 10000 1 10 0 1
2 1000 1 1 0 0
2 100 0 0 0 0
2 250 0 0 0 0
2 10000 1 10 0 1
2 1000 1 1 0 0
2 100 0 0 0 0
2 250 0 0 0 0
Table 17: Separation Violations Penalties
Frequency Group Assignment: Indicates the user defined frequency groups to be used for a given
cell. The Frequency Group Assignment sheet contains the columns as mentioned in Table 18: Fre-
quency Group Assignment. If multiple frequency groups are associated with a given cell, then you

can enter them as comma separated values. Cells which are not assigned to user defined frequency
groups continue to use default frequency groups defined in the module configuration file. If the user
defined frequency group is completely missing for a cell or it is missing for a layer or a band within the
cell, then the corresponding default frequency group of the layer or band of the cell will be used.
Table 18: Frequency Group Assignment describes the frequency group assignments.
Cell CGI Frequency groups
404-92-1118-14401 New BCCH 1800, New TCH 1800
404-92-1118-14402 New BCCH 1800, New TCH 1800
404-92-1118-14403 New BCCH 1800, New TCH 1800
Table 18: Frequency Group Assignment
6.5 Configuring INI parameters

INI parameters can be modified to change the default settings of the GFO module. You can also import, export, delete, activate,
and deactivate the configuration files.
Prerequisites
• Only users with admin privileges have permission to modify the parameters.
1. Log in to the EdenNet application by doing the following:

OSS):
where <EdenNet GUI_SERVERS IP> is the IP address of the GUI server provided during the
installation of EdenNet.

d) Click Log In.
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 GSM_Frequency_Optimization.
4. Click Configure → Module Configuration.
The GSM_Frequency_Optimization Configuration Manager dialog box appears.
5. Select the required configuration categories. For example, in case of the GFO module, you must
import the Excel file under the GFO Preferences category and the INI file under the Interference
Matrix 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.
Note: Users with Administrator or SON Module Manager permissions can delete
the configuration files. The configuration files can be deleted only if it is not used by
other modules.
• Activate: to activate the selected file from the list.
Note: Multiple configurations can be activated.
• Deactivate: to deactivate the activated file.
Note: A file can be deactivated only when it is not used by other modules listed
under Active SON Modules or Module History.
• Set As Default: to set the selected file as the default configuration.

• 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.
• Reset: to reset the edited parameter values in the selected INI file.
Note: For more details, see the Configuring a moduleConfiguring a module section in
EdenNet User and Administration Guide.
For the Excel file parameters, see GFO module configuration file.
For the INI file parameters, see GFO interference matrix configuration INI file.

GSM Frequency Optimization Guide DN09257997 1-1 Viewing GFO reports
7 Viewing GFO reports

For every execution of a module instance, the GFO module generates multiple reports in .xlsx format. Each report is displayed
in a separate worksheet of the Microsoft Excel file. To see the interference and violations in existing network, execute the GFO
module with all the algorithms disabled.
1. Log in to the EdenNet application by doing the following:

OSS):

d) Click Log In.
2. Click SON Modules → Status.
Active SON Modules and Module History appears in the left pane, and Execution Status
appears in the right pane.
3. In the left pane, click a module either from Active SON Modules or Module History.
The Module Status appears in the right pane.
4. In the right pane, click Logs.
5. Click the user name next to User Outputs.
Directory Listing For dialog box with list of file with module name appears.
6. Select the module file name.
Set of related Excel files are listed in the Directory Listing For dialog box.
7. Select a file and open or save it.
Expected outcome
The GFO report is generated. The reports are generated in XLSX (Excel) format.

7.1 GFO reports

Table 19: GFO module report describes the tabs listed in the report.
Tabs Description
Parameter Settings Contains all the input parameters used by the module from GUI, Excel, and
INI files.
Network Statistics Contains information about the target and buffer cells considered by the
module. It contains the number of BTS, TRX, sites, cells, number of neigh-
bors, interfering cells at scope (network) level, band level, and layer level
within the band.
Buffer cells are identified with the following criteria:
• Cells which are the first and second level defined neighbors of the
scope cells
• Cells having incoming and outgoing interferences to and from the
scope cells
Validation Summary Contains the summary of the validation rules executed on the target and
buffer cells. Report also displays the target and buffer elements that have
failed in the validation rule. Algorithm behavior is also provided for better
understanding.
Validation Details Contains the details of the conflicts detected in the target and buffer cells.
BSIC Collisions Contains the BSIC collisions detected before executing the BSIC algorithm.
GFO module reports a BSIC collision when the target and buffer cells have
same BCCH frequency and use the same BSIC value.
BSIC Algorithm Results Contains the proposed BSIC for the target cells along with the collisions re-
maining after executing the BSIC algorithm.
Interference Report Lists all possible interference combinations that a BTS can have with its
primary/BCCH BTS or with a neighbor BTS. The presence of interference
can be inferred from the percentage interference values displayed and also
from the cost due to the interference.
Violation Report Contains the details of the violations remaining after running the module.
Network Cost Compari- Provides an overview of the quality of the proposed plan. It includes inter-
son ference cost and provides pre-allocation/post allocation and delta cost val-
ues.
Proposed Plan Report Contains the list of all selected BTS and its TRXs along with their existing
and proposed parameter values.
Proposed MAL Report Contains the list of MALs proposed after running the module when synthe-
sized hopping mode is selected.

Tabs Description
Interference Matrix Contains the interference matrix used in the current execution.
Table 19: GFO module report
Table 20: Validation Summary tab described the data displayed in the Validation Summary report.
Algorithm behav-
Problem Impact Target Buffer
ior
Site assignment FREQUENCY (Inter- X Y Skip element from

is missing for ference Matrix), BSIC, the scope
the cell HSN OPTIMIZATION
Site coordinates FREQUENCY OP- X Y Skip element from

are invalid for TIMIZATION (Interfer- the scope
the cell ence Matrix), BSIC,
HSN OPTIMIZATION
Primary BTS is BSIC OPTIMIZATION X Y Skip element from

missing from the the scope
cell
BCCH is miss- BSIC OPTIMIZATION X Y Skip element from

ing for the cell the scope
BSIC is invalid BSIC OPTIMIZATION X Y Cell will be allocat-

for the Cell ed new BSIC
Cell layer is not Analysis X Y Module execution

defined for the stops
cell
TRXs are miss- Not taken into account X Y Skip element from
ing for the BTS the scope
FEP Interfer- FREQUENCY OP- X Y Skip element from

ence data is TIMIZATION, Analysis the scope
missing for the
BTS
FEP measure- FREQUENCY OP- X Y Skip element from

ment data is TIMIZATION, Analysis the scope
missing for the
BTS
Frequency FREQUENCY OP- X Y Error and module

Group assign- TIMIZATION execution stops
ment is missing

Algorithm behav-
Problem Impact Target Buffer
ior
for the layer of

BTS
Invalid channel MAL, MAIO, AFP X Y Error and module

value given to execution stops
the layer
Not enough FREQUENCY OP- X Y Algorithm contin-

frequencies in TIMIZATION ues to execute
the frequency with the available
group to support frequency chan-
EGSM/PGSM nels. As the re-
frequency sep- sults are believed
aration for the to impact the net-
layer of the BTS work performance,
provide sufficient
GSM/PGSM chan-
nels or turn OFF
EGSM/PGSM sep-
aration.
Note: X
and Y
can vary.
Table 20: Validation Summary tab
where, X and Y are the value which can change for each run.
Table 21: Validation Details describes the details of the conflicts detected in the target and buffer cells.
Column name Column description
Log status Indicates whether the conflict reported is an error or warning. If it is an error,
then execution terminates otherwise execution skips the elements and pro-
ceeds.
Problem Indicates the problem found in the corresponding conflicting BTS.
BSC DN Indicates the BSC distinguished name associated with the corresponding
conflicting BTS.
Site name Indicates the name of the site to which BTS is connected.
Cell name Indicates the name of the conflicting BTS.

BTS DN Indicates the distinguished name of the conflicting BTS.
Band Indicates the band configured in the conflicting BTS.
TRX Layer Indicates the TRX Layer (BCCH or TCH) for the problem related to TRX. If
the validation error is related to the BTS, then the TRX layer value is set to
Not applicable.
Target BTS Indicates whether the conflicting BTS is in scope or not. If no, it indicates
that the BTS is in the buffer area.
Primary BTS Indicates whether BCCH TRX is configured in the conflicting BTS. Primary
BTS contains BCCH TRX.
Impacts Indicates the impact of the validation error.
Table 21: Validation Details
Table 22: BSIC Collisions tab describes the data displayed in the BSIC Collisions tab.
Target cell name Indicates target cell name having collision before BSIC optimization
Target cell DN Indicates target cell distinguished name having collision before BSIC opti-
mization
Target site name Indicates site associated with target cell having collision before BSIC opti-
mization
Target BCCH channel Indicates BCCH frequency of the target cell having collision before BSIC
optimization
Target BCC Indicates BCC of the target cell having collision before BSIC optimization
Target NCC Indicates NCC of the target cell having collision before BSIC optimization
Neighbor cell name Indicates name of the neighbor cell having collision before BSIC optimiza-
tion. Neighbor cell can be adjacent cell, second adjacent cell, or distance
based neighbor.
Neighbor cell DN Indicates distinguished name of neighbor cell having collision before BSIC
optimization. Neighbor cell can be adjacent cell, second adjacent cell, or
distance based neighbor.
Neighbor site name Indicates the site associated with neighbor cell having collision before BSIC
optimization. Neighbor cell can be adjacent cell, second adjacent cell, or

Neighbor BCCH chan- Indicates BCCH frequency of the neighbor cell having collision before BSIC
nel optimization. Neighbor cell can be adjacent cell, second adjacent cell, or
Neighbor BCC Indicates BCC of the neighbor cell having collision before BSIC optimiza-
based neighbor.
Neighbor NCC Indicates NCC of the neighbor cell having collision before BSIC optimiza-
based neighbor.
Distance (Km) Indicates the distance between target and neighboring cell having collision
before BSIC optimization
Collision type Indicates the type of collision before BSIC optimization. Collision types can
be collisions due to usage of the same BCCH-BSIC or BCCH-BCC among
neighbors, second level neighbors, or cells within the given maximum dis-
tance. Additionally, usage of forbidden BSIC and NCC is identified as colli-
sion.
Table 22: BSIC Collisions tab
Table 23: BSIC Algorithm Results tab describes the data displayed in the BSIC Algorithm Results tab.
Target cell name Indicates target cell name having collision after BSIC optimization
Target cell DN Indicates target cell distinguished name having collision after BSIC opti-
mization
Target site name Indicates the site associated with target cell having collision after BSIC op-
timization
Target BCCH channel Indicates BCCH frequency of the target cell having collision after BSIC op-
timization
Target BCC Indicates BCC of the target cell having collision after BSIC optimization
Target NCC Indicates NCC the target cell having collision after BSIC optimization
BCCH-BSIC reused by Indicates the number of times BCCH-BSIC of the target cell is reused with-
target in the target cells after BSIC optimization
BCCH-BSIC reused by Indicates the number of times BCCH-BSIC of the target cell is reused with-
buffer in the buffer cells after BSIC optimization

BCCH-BCC reused by Indicates the number of times BCCH-BCC of the target cell is reused within
target the target cells after BSIC optimization
BCCH-BCC reused by Indicates the number of times BCCH-BCC of the target cell is reused within
buffer the buffer cells after BSIC optimization
BTS count with miss- Indicates the number of BTSs without site information after BSIC optimiza-
ing sites (BCCH-BSIC tion, which uses the same BCCH-BSIC combination newly assigned to the
reuse) corresponding target cell.
BTS count with miss- Indicates the number of BTSs without site information after BSIC optimiza-
ing sites (BCCH-BCC tion, which uses the same BCCH-BCC combination newly assigned to the
reuse) corresponding target cell.
Closest BCCH-BSIC Indicates the closest reuse distance of BCCH-BSIC of the target cell after
reuse distance(km) BSIC optimization
Closest BCCH-BCC Indicates the closest reuse distance of BCCH-BCC of the target cell after
reuse distance(km) BSIC optimization
Average BCCH-BSIC Indicates the average reuse distance of BCCH-BSIC of the target cell after
reuse distance(km) BSIC optimization among the target and buffer cells.
Average BCCH-BCC Indicates the average reuse distance of BCCH-BCC of the target cell after
reuse distance(km) BSIC optimization among the target and buffer cells.
Adjacent BCCH-BSIC Indicates the number of times BCCH-BSIC of the target cell is reused with-
collisions in the adjacent cells after BSIC optimization
Second adjacent Indicates the number of times BCCH-BSIC of the target cell is reused with-
BCCH-BSIC collisions in the second adjacent (adjacent's adjacent) cells after BSIC optimization
Adjacent BCCH-BCC Indicates the number of times BCCH-BCC of the target cell is reused within
collisions the adjacent cells after BSIC optimization
Second adjacent Indicates the number of times BCCH-BCC of the target cell is reused within
BCCH-BCC collisions the second adjacent (adjacent's adjacent) cells after BSIC optimization
Table 23: BSIC Algorithm Results tab
Table 24: Interference Report tab describes the data displayed in the Interference Report tab.
Interfered BSC DN Indicates the distinguished name of BSC associated with the interfered
BTS
Interfering BSC DN Indicates the distinguished name of BSC associated with the interfering
BTS

Interfered site name Indicates the name of the site associated with the interfered BTS
Interfering site name Indicates the name of the site associated with the interfering BTS
Interfered BTS name Indicates the name of the interfered BTS
Interfering BTS name Indicates the name of the interfering BTS
Interfered BTS DN Indicates the distinguished name of the interfered BTS
Interfering BTS DN Indicates the distinguished name of the interfering BTS
Interfered vendor Indicates the vendor of the interfered BTS
Interfering vendor Indicates the vendor of the interfering BTS
Interfered band Indicates the frequency band of the interfered BTS
Interfering band Indicates the frequency band of the interfering BTS
Interfered TRX layer Indicates the TRX layer of the interfered BTS. Values can be either BCCH
or TCH.
Interfering TRX layer Indicates the TRX layer of the interfering BTS. Values can be either BCCH
or TCH.
Existing interfered hop- Indicates the original hopping mode of the interfered BTS
ping mode
Note: For Huawei, although the cell is set as RF hopping, some
TCH TRXs can be Non-hopping. So for those TCH TRXs, the
existing hopping mode is visible as Non-hopping.
User defined interfered Indicates the new hopping mode of the interfered BTS as defined by the
hopping mode user
Existing interfering hop- Indicates the original hopping mode of the interfering BTS
ping mode
Note: For Huawei, although the cell is set as RF hopping, some
TCH TRXs can be Non-hopping. So for those TCH TRXs, the
existing hopping mode is visible as Non-hopping.
User defined interfering Indicates the new hopping mode of the interfering BTS as defined by the
hopping mode user
Existing interfered Indicates the original frequency channels of the interfered BTS
channels
Proposed interfered Indicates the new frequency channels of the interfered BTS
channels

Existing interfering Indicates the original frequency channels of the interfering BTS
channels
Proposed interfering Indicates the new frequency channels of the interfering BTS
channels
Existing average inter- Indicates the original average interference value before frequency opti-
ference (%) mization. Using original frequency channels average interference is cal-
culated as [coInterference + adjInterference - coInterference * adjInterfer-
ence]
Proposed average inter- Indicates the new average interference value after frequency optimization.
ference (%) Using newly proposed frequency channels [coInterference + adjInterfer-
ence - coInterference * adjInterference]
Delta average interfer- Indicates the difference between original and new average interference.
ence (%) Negative value indicates improvement in interference.
Existing co-channel in- Indicates the original co-channel interference before frequency optimiza-
terference (%) tion. Using original frequency channels, co-channel interference is calcu-
lated as [ (Number of duplicate co-channels in the frequency channel list *
number of TRXs / (number of frequency channels) )* Co-channel interfer-
ence probability measured against interfering cell]
Proposed co-channel Indicates the new co-channel interference after frequency optimization. Us-
interference (%) ing newly proposed frequency channels, co-channel interference is calcu-
lated as [ (Number of duplicate co-channels in the frequency channel list *
number of TRXs / (number of frequency channels) )* Co-channel interfer-
ence probability measured against interfering cell]
Delta co-channel inter- Indicates the difference between original and new co-channel interference.
ference (%) Negative value indicates improvement in the interference.
Existing adjacent chan- Indicates the original adjacent-channel interference before frequency opti-
nel interference (%) mization. Using original frequency channels, adjacent-channel interference
is calculated as [ (adjChCollisionProb * ((number of frequency channels)/
(number of TRXs)) * Adjacent channel interference probability measured
against interfering cell] where adjChCollisionProb is the number of adja-
cent channels used in the frequency channels
Proposed adjacent Indicates the new adjacent-channel interference after frequency optimiza-
channel interference tion. Using newly proposed frequency channels, adjacent-channel interfer-
(%) ence is calculated as [ (adjChCollisionProb * ((number of frequency chan-
nels)/ (number of TRXs )) * Adjacent channel interference probability mea-
sured against interfering cell] where adjChCollisionProb is the number of
adjacent channels used in the frequency channels

Delta adjacent channel Indicates the difference between adjacent channel interference before and
interference (%) after execution of frequency optimization.
Existing cost Indicates the cost value of the BTS object before the execution of frequen-
cy optimization algorithm. If the same BTS experiences multiple interfer-
ence then subsequent entries in the Interference report against the given
BTS will have cumulative cost value.
Proposed cost Indicates the cost value of the BTS object after the execution of frequency
optimization algorithm.
Delta cost Indicates the difference between the proposed cost and the existing cost
values. Negative cost indicates interference is resolved.
Number of TRXs in in- Indicates number of TRX objects under the given interfered BTS.
terfered BTS layer
Table 24: Interference Report tab
Table 25: Violation Report tab describes the data displayed in the Violation Report tab.
Note: If there is a co-cell, co-site, co-channel, or adjacent channel violation, the second,
third, or fourth adjacent channel violation for the same cells are not shown. Co-channel and
adjacent channel violation is more critical than second, third, or fourth adjacent channel vio-
lation. Hence, once the critical violation is detected, less critical violation between the same
cells are not shown.
Violation type Indicates the type of violation based on the separation violations defined in
the settings. These violations are the ones which remain in the network af-
ter frequency optimization. Possible violation types correspond to the viola-
tion of the following criteria:
• Separation violation criteria

• Frequency change penalties criteria
Frequency Change Penalty is shown as a suggestion violation.
Penalty Indicates the cost associated with the interfered BTS and the interfering
BTS for a given violation type. The cost calculation is based on the cost val-
ues defined in the GFO Excel configuration file.
Interfered BSC DN Indicates the distinguished name of the BSC associated with the interfered
BTS

Interfering BSC DN Indicates the distinguished name of the BSC associated with the interfering
BTS
Interfered site name Indicates the name of the site associated with the interfered BTS
Interfering site name Indicates the name of the site associated with the interfering BTS
Interfered BTS name Indicates the name of the interfered BTS
Interfering BTS name Indicates the name of the interfering BTS
Interfered BTS DN Indicates the distinguished name of the interfered BTS
Interfering BTS DN Indicates the distinguished name of the interfering BTS
Interfered vendor Indicates the vendor of the interfered BTS
Interfering vendor Indicates the vendor of the interfering BTS
Interfered band Indicates the frequency band of the interfered BTS
Interfering band Indicates the frequency band of the interfering BTS
Interfered TRX layer Indicates the TRX layer of the interfered BTS. Values can be either BCCH
or TCH.
Interfering TRX layer Indicates the TRX layer of the interfering BTS. Values can be either BCCH
or TCH.
Interfered hopping Indicates the hopping mode of the interfered BTS

mode
Interfering hopping Indicates the hopping mode of the interfering BTS

mode
Interfered channels Indicates the frequency band of the interfered BTS
Interfering channels Indicates the frequency band of the interfering BTS
Number of TRXs in in- Total number of TRXs in the interfered BTS layer
terfered BTS layer
Table 25: Violation Report tab
Table 26: Network Cost Comparison tab describes the data displayed in the Network Cost Comparison
tab.
Target Band/Layer Indicates the target band or layer name.

Pre-allocation cost Overall cost against the given band or layer before running the GSM fre-
quency optimization operation. Includes cost due to separation violation and
interference.
Post-allocation cost Overall cost against the given band or layer after running the GSM frequen-
cy optimization operation. Includes cost due to separation violation, fre-
quency change penalty and interference.
Delta cost Difference between the overall cost against the band or the layer before and
after running GSM frequency optimization. Negative value indicates better
allocation for the given band or layer.
Table 26: Network Cost Comparison tab
Table 27: Proposed Plan Report tab describes the data displayed in the Proposed Plan Report tab.
BSC DN Distinguished name of the BSC associated with the BTS
Site Name Name of the site associated with the BTS
Cell Name Name of the cell in the network
BTS Name Name of BTS in the network
BTS DN Distinguished name of the BTS in the network
TRX DN Distinguished name of the TRX in the network
Vendor Vendor of the BTS
Band Frequency band of the BTS
TRX Layer Layer of the cell of the given TRX containing the change in value
Cell ID Cell identity in the network
LAC Location area code in the network
Frequency Group Name of the frequency group used for allocation
Existing Hopping Mode Hopping mode of the TRX before frequency optimization.
Represents the hopping mode of the associated BTS.
User defined Hopping Hopping mode of the TRX after frequency optimization.
Mode
Represents the hopping mode of the associated BTS.
Existing Channel Frequency channel of TRX before frequency optimization
Proposed Channel Frequency channel of TRX after frequency optimization

Forbidden Channel Indicates all the channels which are forbidden for a given cell containing the
given TRX.
Note: The Forbidden Channels are shown at the cell level and
are not segregated at band or layer level.
Existing HSN1 Represents the hopping sequence number used in the BTS in case of syn-
thesized hopping mode, before HSN optimization.
In special cases, for Nokia BTS, when the baseband hopping mode is used,
HSN1 represents the hopping sequence number used by TCH TRXs in time
slot zero.
For other vendor cells, HSN1 represents a single HSN value used in the
cell.
Existing HSN2 Represents the hopping sequence number used in the BTS in case of
baseband hopping mode, before HSN optimization.
In special cases, for Nokia BTS, when baseband hopping mode is used,
HSN2 represents the hopping sequence number used by the TCH TRXs in
non-zero time slots.
For other vendor cells, HSN2 contains the same values as HSN1.
Proposed HSN1 Represents the hopping sequence number proposed to the BTS in case of
synthesized hopping mode, after HSN optimization.
HSN1 represents the hopping sequence number used by TCH TRXs in time
slot zero.
For other vendor cells, HSN1 represent a single HSN value used in the cell.
Proposed HSN2 Represents the hopping sequence number proposed to the BTS in case of
baseband hopping mode, after HSN optimization.
HSN2 represents the hopping sequence number used by TCH TRXs in
non-zero time slots.
For other vendor cells, HSN2 contains the same values as HSN1.
Existing MAIO Offset Mobile Allocation Index Offset of the TRX before frequency optimization.
Represents the MAIO offset of the associated BTS.
Proposed MAIO Offset Mobile Allocation Index Offset of the TRX after frequency optimization.

Represents MAIO offset of associated BTS.
Existing MAIO Step Mobile Allocation Index Step of the TRX before frequency optimization.
Represents MAIO step of associated BTS.
Proposed MAIO Step Mobile Allocation Index Step of the TRX after frequency optimization.
Represents MAIO step of associated BTS.
Existing BCC Base station Color Code of the TRX before frequency optimization.
Represents BCC of associated BTS.
Proposed BCC Base station Color Code of the TRX after frequency optimization.
Represents BCC of associated BTS.
Forbidden BSICs Indicates the Base Station Identity Codes (BSICs) defined as forbidden for
the given cell.
Existing NCC Network Color Code (NCC) of the TRX before frequency optimization.
Represents NCC of associated BTS.
Proposed NCC Network Color Code of the TRX after frequency optimization.
Represents NCC of associated BTS.
Forbidden NCCs Indicates the Network Color Codes (NCCs) defined as forbidden for the giv-
en cell.
MAL Allocation Mode Allocation mode selected for MAL assignment. In this release, it is only allo-
cate mode.
Existing MAL DN Distinguished name of the MAL object associated with the BTS of the TRX
before frequency optimization.
Proposed MAL DN Distinguished name of the MAL object associated with the BTS of the TRX
after frequency optimization. The MAL object is visible in the proposed MAL
report sheet.
Existing MAL ID ID of the MAL object associated with the BTS of the TRX before frequency
optimization.
Proposed MAL ID ID of MAL object associated with the BTS of the TRX after frequency opti-
mization. The corresponding MAL object is listed in the Proposed MAL Re-
port.

Average CS traffic (Er- Indicates the value of the average CS traffic KPI of the cell. This value is
langs) same for all the TRXs under a given cell including primary and secondary
BTS.
TCH Blocking (%) Indicates the value of the TCH blocking KPI of the cell. This value is same
for all the TRXs under a given cell including primary and secondary BTS.
Status Indicates the status of the TRXs. The additional TRXs are displayed as
Planned in the status column. The actual TRXs are displayed as Actual
in the status column.
Table 27: Proposed Plan Report tab
Table 28: Proposed MAL Report tab describes the data displayed in the Proposed MAL Report tab.
MAL DN Distinguished name of the MAL object
MAL ID ID of the MAL object
Original Channels List of frequency channels in the MAL object before frequency optimization.
New Channels List of frequency channels in the MAL object after frequency optimization.
Status Indicates whether the MAL is created, updated or actual (the same as in the
actual configuration of the network).
MAL creation or deletion is not supported for the Huawei and Ericsson el-
ements. Therefore, MAL status of the Huawei and Ericsson nodes will al-
ways be set to Updated.
Table 28: Proposed MAL Report tab
Table 29: Interference matrix tab describes the data displayed in the Interference matrix tab.
Interfered Cell CGI of the interfered cell.
Interfering Cell CGI of the interfering cell.
Co-channel CIP Co-channel Carrier over Interference Probability value between the inter-
fered and interfering cell. The value is in percentage.
Adjacent Channel CIP Adjacent channel Carrier over Interference Probability (CIP) value between
the interfered and interfering cell. The value is in percentage.
Type Indicates the type of the Interference MAtrix. It is always set to FEP.

Distance Distance between the interfered and interfering cell in kms.
Blind Spot Indicates whether the interfering cell is a blind spot or not (Supported val-
ues are either Yes or No).
Number of Samples Indicates the number of samples received by the interfered cell for all the in-
terferers.
Table 29: Interference matrix tab

GSM Frequency Optimization Guide DN09257997 1-1 Viewing GFO events
8 Viewing GFO events

You can view events which are specific to the module.
1. Log in to the EdenNet application:

OSS):

d) Click Log In.
2. Click the Events tab.
A list of filters appears in the left pane.
3. From the Module/Service filter, select the required GFO 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 the source 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 filter.
4. In the Time Range area, set the required time range.
5. Optional: In the Saved Filters, enter a name for the event filter, and save it using the Save As
New Filter option.
6. Click Filter to apply the filter.
The event log appears.

GSM Frequency Optimization Guide DN09257997 1-1 Viewing GFO events
8.1 GFO events

Level Name Description Mitigation action
Information INI file missing Configuration file INI file should be associated with the
of type, INI is not module which is described in GFO
associated with the interference matrix configuration INI
module. file.
Information Input XLS missing Indicates that input Excel file should be associated with
in the form of XLS the module which is described in
is not associated GFO module configuration file.
with the module.
Information Duplicate SEGMENT Indicates same Correct the network configuration.

ID segment ID is
present for two
cells which are
having BCCH TRX
Table 30: Events of GFO

GSM Frequency Optimization Guide DN09257997 1-1 Monitoring GFO
9 Monitoring GFO
You can monitor the activity, status, and events of the GFO module.
For more information, see the Configure and monitor SON modulesConfigure and monitor SON mod-
ules section in the EdenNet User and Administration Guide.

GSM Frequency Optimization Guide DN09257997 1-1 Automatic verification and rollback
10 Automatic verification and rollback
The GFO module supports automatic verification and rollback functionality.
After a successful push, the GFO module waits for the KPI verification window to elapse, and then
evaluates the performance of the scope cells based on the KPI rules configured in the Verification and
Rollback sheet. For more information on Verification and Rollback sheet, see GFO module configura-
tion file.
If any cell is found to be degraded, all the changes pushed by the GFO module previously are rolled
back. The rollback changes are immediately pushed to the network , without waiting for maintenance
window.

Eden Net GSM Fo Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Eden Net GSM Fo Guide

Uploaded by

Copyright:

Available Formats

EdenNet 21 FP 2106

GSM Frequency Optimization Guide

N O WA RRA NT Y O F AN Y KI ND , EI T HER EXPR ES S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D TO A N Y

Copyright © 2021 Nokia. All rights reserved.

Important Notice on Product Safety

3 GFO functional description and guidelines................................................................................................15

5 Configuring and executing GFO module....................................................................................................22

6 GFO configuration parameters.................................................................................................................... 28

7 Viewing GFO reports.....................................................................................................................................60

8 Viewing GFO events......................................................................................................................................76

EdenNet 21 FP 2106 © 2021 Nokia 3

10 Automatic verification and rollback.......................................................................................................... 79

EdenNet 21 FP 2106 © 2021 Nokia 4

Release Change description

EdenNet 21 FP 2106 No change.

EdenNet 21 FP 2105 No change.

EdenNet 21 FP 2104 No change.

EdenNet 21 FP 2103 Updated section:

• Dependencies for Huawei is updated by removing Ericsson references.

EdenNet 21 Updated section:

• Overview of GFO - A note is added about the deprecation of direct CM

EdenNet 20 FP 2011 No change.

EdenNet 20 FP 2010 No change.

EdenNet 20 FP 2009 No change.

EdenNet 20 FP 2008 Updated section:

• Closed loop mode is updated with a Note.

EdenNet 20 FP 2007 No change.

EdenNet 20 Added sections:

• Closed loop mode

• GFO functional description and guidelines

– KPI Verification Window

EdenNet 21 FP 2106 © 2021 Nokia 5

Release Change description

– Violations Cost Margin

EdenNet 19A FP 2004 No change.

EdenNet 19A FP 2003 No change.

EdenNet 19A FP 2002 No change.

EdenNet 19A FP 2001 Updated sections:

• GFO module configuration file - The New TRX Assignment sheet is

EdenNet 19A FP 1912 No change.

EdenNet 19A FP 1911 No change.

EdenNet 19A No change.

EdenNet 19 FP 1907 No change.

EdenNet 19 FP 1906 No change.

EdenNet 19 FP 1905 Updated section:

• Instance of NOLS is replaced with Support portal in Dependencies for

EdenNet 19 FP 1904 Updated sections:

• Instances of Custom modules are changed to Adapted modules in

• GFO GUI parameters section is updated with modified descriptions for

EdenNet 19 Updated section:

– BSIC: Limit by Distance

EdenNet 21 FP 2106 © 2021 Nokia 6

Release Change description

– BSIC: Limit by Cells

EdenNet 18 SP1 1901 No change.

EdenNet 18SP1 1812 Updated section:

• Updated the description of the Network Statistics tab in GFO reports

EdenNet 18 SP1 Added section:

• The User defined frequency groups Excel file section is added.

• A new parameter User defined frequency groups is added to

EdenNet 18 Added content:

• Added Huawei content to Dependencies for Huawei.

– Consider PGSM and EGSM separately in the BCCH fre-