Ilsa2 Aircom

Copyright 2003 AIRCOM International Ltd
All rights reserved. No part of this work, which is protected by copyright,

may be reproduced in any form or by any means - graphic, electronic or
mechanical, including photocopying, recording, taping or storage in an
information retrieval system without the written permission of the
copyright owner.

ILSA2 - Application Note
V1.0

Product Support Group
P-TN-010-001-002

CONTENTS
1 INTRODUCTION......................................................................................................... 3
2 FREQUENCY PLANNING.......................................................................................... 3
3 ILSA2 - PROCESS AND DATA FLOW...................................................................... 3
3.1 HIGH-LEVEL ILSA2 PROCESS ......................................................................................... 3
3.2 DATA INPUTS TO ILSA2 ................................................................................................. 5
4 STEPPING THROUGH THE ILSA2 PROCESS ........................................................ 5
4.1 ANALYSIS OF THE EXISTING FREQUENCY PLAN.............................................................. 5
4.2 PREREQUISITES ............................................................................................................... 6
4.2.1 Propagation Model, Predictions and Best Server Array ....................................... 7
4.2.2 Available Frequencies and Frequency Allocation Strategy................................. 10
4.2.3 Current Frequency Allocations............................................................................ 11
4.2.4 Neighbour Lists and Exceptions........................................................................... 12
4.2.5 Traffic Information / Required Number of Carriers ............................................ 13
4.2.6 Interference Table ................................................................................................ 15
4.3 SETTING UP THE PLAN................................................................................................... 18
4.3.1 ILSA2 Initialisation .............................................................................................. 18
4.3.2 ILSA2 Import Filters ............................................................................................ 20
4.3.3 ILSA2 Plan List Dialog ........................................................................................ 23
4.3.4 ILSA2 Cost Matrix................................................................................................ 24
4.3.5 ILSA2 Options Dialog.......................................................................................... 36
4.4 STARTING PLANNING AND VIEWING PROGRESS............................................................ 41
4.4.1 Commencing Planning......................................................................................... 42
4.4.2 Viewing Planning Progress.................................................................................. 43
4.5 ANALYSING RESULTS.................................................................................................... 46
4.5.1 Carrier Statistics .................................................................................................. 47
4.5.2 Cell Statistics........................................................................................................ 47
4.6 FURTHER OPTIONS........................................................................................................ 48
5 ALGORITHM DESCRIPTION................................................................................... 49
5.1 PROBLEM DEFINITION................................................................................................... 49
5.2 SEARCH ALGORITHMS................................................................................................... 50
5.3 ILSA2 SEARCH STRATEGY ........................................................................................... 51
5.4 COST FUNCTION DESCRIPTION...................................................................................... 51
APPENDIX A - FREQUENCY PLAN EXAMPLE.......................................................... 53
A.1 SCENARIO DESCRIPTION ............................................................................................... 53
A.2 INITIAL NETWORK CONFIGURATION ............................................................................. 53
A.2.1 Network before Site Reconfiguration ................................................................... 53
A.2.2 Worst Interferer Array Statistics .......................................................................... 56
A.2.3 Average Connection Array Statistics ................................................................... 57
A.3 NETWORK RETUNE ....................................................................................................... 58
A.3.1 Network after Site Reconfiguration...................................................................... 58
A.3.2 Frequency Planning Process ............................................................................... 59
A.3.3 Retune Results ...................................................................................................... 62
A.3.4 Worst Interferer Array Statistics .......................................................................... 63
A.3.5 Average Connection Array Statistics ................................................................... 64
P-TN-010-001-002 i
Commercial-in-Confidence

A.4 PLANNING SUMMARY....................................................................................................65
APPENDIX B - TABLE OF FIGURES........................................................................... 67
APPENDIX C - TABLE OF FAQS................................................................................. 69
APPENDIX D - GLOSSARY OF TERMS...................................................................... 71

ii P-TN-010-001-002

1 INTRODUCTION
This application note describes in detail the ILSA2 automatic frequency planning tool,
its use within the ENTERPRISE planning system and example planning scenarios.
2 FREQUENCY PLANNING
In essence, a frequency plan can be defined as carrier assignments to TRX.
There are too many possible carrier permutations to ever manually determine the best
frequency plan when you consider the capacity requirements and consequent number of
TRX found in networks today. Consequently, a method must be chosen that provides
an acceptable solution within the constraints of time whilst intelligently observing the
defined quality objectives.
Older, more traditional frequency planning techniques have relied on the ability of
engineers to manually allocate from carrier groups. But with the conflicting pressures
of larger networks, greater traffic capacity while minimising infrastructure costs,
manual planning can no longer be seriously considered.
Automated tools, in general, are not without their own problems. If an automated
method is unable to take into consideration the current plan, the results will most likely
require a complete reconfiguration of the network something that loses operator
revenue when inevitable mistakes occur.
Fortunately ILSA2, the second generation of ASSETs frequency planning tool, uses an
algorithm that constantly searches for improvements. Changes are therefore
incremental, steered by penalties associated with the changes the algorithm can make.
By choosing the penalties carefully, the desired goals can be achieved.
3 ILSA2 - PROCESS AND DATA FLOW
The secrets of generating a good frequency plan with ILSA2 can be summarised as:
understanding how to perform the procedural steps involved
understanding what inputs are required and whether they are mandatory or optional
understanding what outputs you can expect and how to interpret them
3.1 HIGH-LEVEL ILSA2 PROCESS
The list and diagram below describes the high level procedural steps. The sections later
in this document provide more details of the sub tasks involved.
P-TN-010-001-002 Page 3

Steps:
i. analyse the existing frequency plan
ii. create the prerequisites
iii. set-up the cost matrix
iv. run ILSA2
v. analyse the results
vi. decide whether the plan is acceptable

Start
Create
Prerequisites
Setup ILSA2/Cost
Matrix
Run ILSA2
Analyse Results
Finish
Analyse Existing
Plan
Acceptable
Improvement?
Yes
No
y Worst Interferer Statistics
y Average Connection Statistics
y Frequency Plan Report
y Carriers Required
y Interference Table
y Neighbours and Exceptions
y ILSA2 Setup
y Cost Matrix Setup
y Worst Interferer Statistics
y Average Connection Statistics
y Frequency Plan Report

Figure 1 - Highlevel Flow Chart of ILSA2 Planning Process
Page 4 P-TN-010-001-002

3.2 DATA INPUTS TO ILSA2
The many inputs to ILSA2 are shown in the picture below. Some of the inputs are
mandatory and others are optional (shown with an asterisk).
Site
Database
Cost Matrix
ILSA2
Neighbours *
Exceptions *
Forbidden
Carriers *
Fixed Carriers *
Carrier Costs
Interference
Table
Wizard
Interference
Costs *
Coverage
Predictor
RF Parameters
Predictions
Array
Creation
Best Server
Array
Frequency
Plan
Traffic
Raster
Wizard
Traffic Raster *
Propagation
Model Editor
Terminal
Types
Propagation
Model
Traffic Spread
Separation
Costs
Required
Carriers
FH Settings *
DTX Settings *
Current Freq
Plan *
Carrier Layers
Cell List
Cell
Equipment *
Exception
Costs
Carrier
Layer Costs
Filter
Priorities
Handover
Costs
Cell Equipment
Costs
Cell
Equipment *
Filters
Handover
Counts *

Figure 2 - Flow of Data within the ILSA2 Planning Process (Neglecting
Neighbour Generation)
4 STEPPING THROUGH THE ILSA2 PROCESS
4.1 ANALYSIS OF THE EXISTING FREQUENCY PLAN
An important part of the frequency planning process is the verification of improvement.
It may be that the current frequency allocation is close to optimal, and that other
optimisation techniques need to be employed before a significant improvement can be
made. Alternatively, the level of improvement may not be sufficient to justify a retune,
and other frequency planning strategies may need to be employed.
The current frequency allocations should be loaded into the site database and
interference arrays generated and analysed statistically. Additionally, it can prove
useful to create an interference table and use it to create a frequency plan report.
A number of different interference arrays can be used to analyse the plan, both visually
and statistically, and the Frequency Plan Reporter can be used to detail the separation
constraints that are broken within the current plan.
P-TN-010-001-002 Page 5

Array Description
Worst Connection The Worst Connection array gives the total level of interference
on the worst connection within the pixel - detailing the
connection (the connection can be regarded as either a carrier or
frequency hopping group, as appropriate), and the C/I level in
dB.
Average Connection The Average Connection array averages the total level of
interference across all serving connections at the pixel - detailing
the C/I level in dB.
Worst Interferer The Worst Interferer array gives the individual worst interferer
at the pixel - detailing the C/I level in dB, the interfering cell and
the carrier.
Total Interference The Total interference array gives the ratio of the total signal
strength within the pixel to the total interfering strength in dB.

Note: The arrays calculate the average values of C/I within the pixel, derived from
the predictions for the serving cell and for the interferer. As the predictions are
subject to a statistical distribution, so are the C/I values derived. If we assume
that the predictions follow a Gaussian distribution with standard deviation
(dB) then the standard deviation of the C/I should be 2 (dB). Using this
information, appropriate C/I thresholds can be calculated, according to the
probability of meeting a given real C/I within a pixel.
The arrays can be analysed both visually, by making plots of the area to be planned,
and statistically, using the Coverage Statistics dialog box. It is possible to create arrays
statistics over polygons, for example enclosing an urban area. The reports generated
detail the proportion of interference worse than an interference threshold over the area
analysed as a whole, as well as a breakdown by clutter type and by cell.
The Frequency Plan Reporter generates a report detailing all of the separation
constraints broken over the filter of sites analysed. If an interference table is in memory
then the levels of interference caused by each allocation are also detailed.
4.2 PREREQUISITES
The following sections describe the prerequisites for the frequency planning process. It
is vital that the prerequisites are correctly set up and checked before starting to plan
since if the inputs are poor quality then it cannot be expected that the outputs will offer
an improvement in the performance of the network!
It is expected that users follow sensible procedures while editing the site database to
ensure the integrity of the information it contains. If this is carried out correctly it
removes the requirement for laborious checking every time the tool is used.
The following sections also provide a description of how to generate the prerequisite (if
applicable), a number of FAQs (Frequently Asked Questions) and a section detailing
the site database parameters that will affect the validity of that prerequisite.
Page 6 P-TN-010-001-002

4.2.1 Propagation Model, Predictions and Best Server Array
An important prerequisite is to have a propagation model of known accuracy, and to
have calculated predictions of all the sites that will be planned. The predictions should
be at an appropriate map pixel resolution and range for the problem considered.
The propagation model is used to predict the coverage of cells, in conjunction with the
RF parameters that are stored within the site database and the mapping data used. The
predictions in turn can be used to create arrays, including the best server array, which is
an important input into the generation of a number of the other prerequisites for ILSA2.
It is a good idea to create and display coverage arrays (or to display service areas) to
check that none of the predictions are clearly incorrect, i.e. all sites give some coverage
and none are dominating areas that they clearly should not.
Common errors found in the coverage array are typically simple to resolve, although a
combination of factors may be the root cause. Individual factors may include:
Assigning an invalid model (e.g. a microcell model to a macrocell)
Not assigning a slot to a sub-cell
Incorrectly specifying the PA output power (e.g. 300.0 instead of 30.00)
The best server array itself is a possible input into the generation of many of the
prerequisites to ILSA2. A best server array is required to generate:
Neighbours, if using the Neighbour Wizard
Traffic raster, if using the Spread Live Traffic option
Carriers required, if using the Traffic Analysis Tool
Interference tables using the Interference Table Wizard
The best server array should be generated to the resolution of the predictions created,
over an area that covers all of the service areas of the cells being planned. It is
important that the Filter used to create the array includes all the sites to be planned.

FAQ 1 - Which propagation model should I use?
There are two propagation model styles provided with the basic version of ASSET. These can be
used to calibrate accurate propagation models for different situations, which can be used to create
predictions for use with ILSA2. Each propagation model style has a number of different
characteristics:
Characteristic Standard Macrocell Microcell
Map Data Required Clutter and Height of same
resolution(s) no minimum
resolution.
Clutter and Height of same
resolution(s) minimum
resolution 5m.
Building Vector Data.
Below roof h
Yes, typica Yes, typical
Application Above roof height macrocells.
Cell radius 500m or greater.
eight urban
microcells.
Calibration lly to 8dB standard
deviation.
ly to 8dB standard
deviation.

P-TN-010-001-002 Page 7

FAQ 2 - H ll if the wrong model has d to a site?
I th corre ysis
based upon the predictions to be incorrect. The f likely symptoms:
ow can you te been adde
f the wrong model is allocated to a site then e prediction will be in
ollowing are
ct, causing any anal
Symptom Cause Condition
The cell the model is allocated to may have
far better coverage than it should,
odel on
macrocell
vectors
dominating over correct cells.
Microcell m no building
The prediction may show a distinction in
coverage between areas enclosed by
building vectors and those not.
odel on
macrocell
building vectors
available
Microcell m
The prediction may be very small a
not show a distinction in coverage between
rocell model on
microcell
- nd should Mac
areas enclosed by building vectors and
those not.

FAQ 3 - W r e affected by the accuracy of the
p
The accuracy of the model affects th
Accuracy of the Model Affects
hat in the ILSA2 Planning p ocess will b
ropagation model?
e accuracy of the following:
In This Way
This has implications for the spreading of traffic within cells.
Typically
calculation of service area. For a less densely planned
network, where cell service areas are limited by minimum
signal thresholds, inaccuracies in the model will have a greater
effect.
Typically for a densely planned area of the
accuracy of the model will have minimal impact on this
calculation of nearest neighbours. For a less densely p
network, where cell service areas are limited by minimum
signal thresholds, inaccuracies in the model will have a greater
effect upon the calculation of neighbours.
The greatest effect of accuracy of the model is in the
interference table generation process. If, for example, the
Service area calculation
for a densely planned area of the network the
accuracy of the model will have minimal impact on this

Neighbour analysis network the

lanned
Interference table generation
propagation model is accurate to 8dB standard deviation, then
l C/I calculated the standard deviation will be
11.3dB. If the model is accurate to 10dB standard deviation,

for each individua
the standard deviation of the C/I will be 14.1dB. The accuracy
of an uncalibrated model may be significantly less than this.

FAQ 4 -
model?
ple if the
This
2. Manually entering the neighbour lists (by importing or directly into the site database)
3. Disabling the interference table allowing ILSA2 to work solely on separation
constraints that you have entered into the cost matrix
What action can be taken if you have no confidence in your current propagation
Even if you have little or no confidence in the propagation model that you have, for exam
model tuning process is still being carried out, ILSA2 can still be used to develop a frequency plan.
can be achieved by:
1. Manually entering the carriers required
(see below) and
While this is possible it is not necessarily desirable.

Page 8 P-TN-010-001-002

FAQ 5 -
y to use the highest resolution mapping data available, with which it takes a
sensible amount of time to create the predictions to the required radius. The radius used should be
the minim
are included in the predictions. To work out the area of coverage it is advisable to create low
resolution predictions over a very large radius, before creating higher resolution predictions over a
more restricted range.
a much
What resolution and radius of predictions should be used with ILSA2?
The resolution and radius of the predictions that you should use are dependent upon a number of
issues. There is a compromise that must be made between the accuracy of the prediction and the
amount of information that must be manipulated and stored.
As a rule, you should tr
such that the predictions hold the information about the entire area of coverage which is 20dB below
um service threshold. This should ensure that all pixels that might contribute as interferers
Note: It may be the case that you have a number of sites in your network, which pollute
larger area than others. If this is the case it is perfectly sensible to create much larger
predictions for these sites.

FAQ 6 - w
Whe
impo
2.
ool and Interference Table Wizard.
3. Candidate and nominal sites th frequency planned should not be included in
the filter used to create the best server array. Including these sites will adversely affect the
Tool and
4. The best server array should cover the entire service area of all the sites to be frequency

FAQ 7 - W meters in th e predictions from a site?
The following is a list of parameters in the site database that affect the predictions from a site.
Site Object
Property Description
Ho should I set up my best server array for the ILSA2 planning process?
n creating your best server array for the ILSA2 planning process, there are a number of
rtant considerations:
1. All of the sites to be included in the ILSA2 frequency planning process must be included in the
array, by using a filter including all of them.
Live sites / sites on the fringes of the region to be planned should be included in the filter used
to create the best server array. These sites will affect the service areas of cells in a realistic
manner. This will increase the accuracy of the Neighbour Wizard, Traffic Raster Wizard, Traffic
Analysis t
at are not being
accuracy of the Neighbour Wizard, Traffic Raster Wizard, Traffic Analysis
Interference Table Wizard.
planned.
hat para e site database affect th
Location Physical location of site.
Actual Ground Height nd height at site. If the default value of 0 is entered Surveyed grou
ASSET assumes the DTM height. (Units: metres)
Prediction Radius ault radius for predictions from this site. (Units: kilometres) The def
Prediction Model
Allocated
Prediction model to use on cell, as defined in the Propagation Model
Editor.
Slot One cell configu
configuration on
ration per slot, all antenna, feeder and cell equipment
a slot by slot basis.
Antenna Type The antenna for use on slot as defined in the equipment database.
Antenna Azimuth (Units: degrees)
Antenna Downtilt Downtilt positive, Uptilt negative. (Units: degrees)
(Units: metr
Cell Object
Antenna Height es)
P-TN-010-001-002 Page 9

Antenna Correction in/loss for fine tuning. A negative value implies a loss, a
Factor
An additional ga
positive value implies a gain. (Units: dB)
The absolu
Feeder Type The feeder type for use on the slot, as defined in the equipment
database.
Antenna Location te antenna location, or that relative to the site.
Feeder Length (Units: metres)
Cell Equipment Type The cell equipment type for use on the slot, as defined in the equipment
database.
Cell Equipment e implies a loss, a
Correction Factor
An additional gain/loss for fine-tuning. A negative valu
positive value implies a gain. (Units: dB)
Description
Signal Offset The Signal Offset of the sub-cell within its cell layer.
The Signal Threshold of the sub-cell. Below the threshold lower priority
sub-cells will serve the traffic, if they are available. If no lower priority
sub-cells are available then the sub-cell will serve traffic down to the
minimum signal threshold held within the Array Creation dialog box.
The Tim
Timing Advance lower p
priority sub-cells exist th
Maximum Timing Advance set within the Array Creation dialog box.
Override to enable multiple model types within a cell. Default disabled
uses model defined in cell. Model
Sub-cell Object
Property
Signal Threshold

TA Threshold ing Advance threshold for the sub-cell. Further out than this
riority sub-cells will serve the traffic. If no lower
en the sub-cell will serve the traffic down to the
Enable Model
as defined in the propagation model
editor.
Slot Allocation Slot for use on sub-cell
PA Output Power The PA Power output for use on sub-cell. The EiRP is derived from this
value, taking into account losses and gains from the antenna, feeder,
and cell equipment. (Units: dBm)

4.2.2
frequency allocation
to be
c in the tool, the frequency
o

(using additional carrier layers with appropriate carriers removed). These might be
Available Frequencies and Frequency Allocation Strategy
Before beginning the planning process you must decide upon your
strategy and create the appropriate carrier layers and cell layers. All frequencies
used should be entered into the system carriers list in the tool.
On e the available frequencies have been identified with
all cation strategy must be decided. Typically this would include:
Deciding if, and how, to use HCS, dual band frequency allocation and MRP
Allocating carriers to BCCH, TCH, and other, carrier layers
Deciding if and how FH and DTX are going to be used
Identifying frequencies that should not be allocated in areas of the network, on an
individual site (using forbidden carriers in the site database) or regional basis
caused by cross border separation agreements or geographical considerations.
These carriers can then be split into subsets (carrier layers), to help define the frequency
plan. These carrier layers can then be allocated to cell layers in the cell layers dialog
box. Cell layers then can be instantiated as sub-cells to cells.
Within the sub-cell object in the site database it is possible to allocate the individual
carrier layers for use. This is necessary as it is possible to allocate more carrier layers to
Page 10 P-TN-010-001-002

a cell layer than are used. For example it is possible to allocate two carrier layers to
supply the BCCH carriers perhaps BCCH and BCCH_border.
If DTX is to be considered by ILSA2, then the cells at which it is enabled need to be
indicated in the site database, and the appropriate Voice Activity Factor (VAF)
assigned. VAFs are typically considered to be in the range 0.2 to 0.4.
If frequency hopping is to be considered by ILSA2, then the sub-cells at which it is
enabled need to be indicated in se. A choice needs to be made between
synthesiser, site and baseband hopping. If synthesiser or site hopping is enabled then it
for
opping where the number of carriers and TRXs must be identical. Finally
FH must be enabled on a carrier layer basis, on the carriers page of the sub-cell. It is not
possible to allocate FH to a control carrier layer.

FAQ 8 - What Parameters in the site database affect the frequency allocation strategy?
Cell Object
the site databa
is possible to indicate that more carriers are required than TRXs. This is not the case
baseband h
Enable DTX ell. Choose to enable DTX on the c
Voice Activity Factor VAF for the cell which indicates the factor by which the interference is
reduced.
Enable Frequency
Hopping
This allows the user to enable frequency hopping on the individual
carriers on the carriers page.
Enables the choice between Baseband, Synthesi
Sub-cell Object
Baseband /
Synthesiser / Site
Hopping
ser and Site hopping on
the sub-cell. With Baseband Hopping the number of frequencies required
is equal to the number of TRX required. With Synthesiser or Site
encies than TRX can be allocated. Hopping more frequ
Carrier Layers Used Only those carrier layers allocated Used will be considered by ILSA2.
Carrier Layer Hopping The hopping column indicates whether an individual carrier layer uses
frequency hopping. Even if Frequency Hopping is enabled on the
General page of the sub-cell then if this column is not allocated, then no
frequency hopping will be considered by ILSA2.

4.2.3 C ncy
The current frequency ed
a st m
urrent Freque Allocations
allocation, including Fixed and Forbidden carriers, may be us
s inputs into the co atrix and ILSA2 itself.
P-TN-010-001-002 Page 11

Sub-cell Object
Allocated Carriers The currently allocated carriers. If improving a current plan, ILSA2
will take these allocations as the initial state of the frequency plan.
Forbidden Carriers The carriers that are forbidden from this site. If improving a current
plan, ILSA2 treats these carriers as subject to the forbidden carriers
cost, as generated within the cost matrix.
Fixed Carriers The carriers that should be fixed to the site. If improving a current
plan, and the retuning of these carriers is allowed, ILSA2 makes a
t different carrier subject to the retune cost, as generated within the cos
matrix
Neighbour Lists and Exceptions
To allow ILSA2 to make fast initial progress with the frequency allocation problem, th
neighbours and exceptions present in the network should be known. Either th
optimised neighbours from the real network can be entered into the site database,
Neighbour lists can be generated using the Neighbour Analysis Tool. Exceptions can be
tered manually within the tool.
The neighbours are used to generate separation costs within the cost matrix and can
generated in a number of ways as shown below:
Start Start
Input Known
Neighbour
Relationships into
Site Database
Start
Input Known
Neighbour
Relationships into
Site Database

4.2.4
e
e
or
en
be
Generate Best
Server Array
Generate Best
Complete
Neighbour
Nei
Analyse Neighbour
Relationahips using
Neighbour Wizard
Update Database
Analyse Neighbour
Relationahips using
Neighbour Wizard
Update Differences
to Database
Finish
Server Array
Finish Finish
Generation
ghbour
Update
our generation is to create a best server array and generate

Figure 3 - Flow Charts Showing Possible Routes for the Generation of
Neighbours
The first method of neighb
neighbour relationships using the Neighbour Wizard. These are then applied to the site
database using the Neighbour Analysis Tool. The advantage of using this method is that
it allows a quick first approximation of the neighbour relationships within the network.
Page 12 P-TN-010-001-002

The disadvantages are that this may not align with the current neighbours set up within
your network, and that it will not produce neighbours with the same accuracy as a well
optimised network. The neighbour wizard creates neighbours when the number of
using the import
functionality within ASSET. The advantage of this method is that it can directly reflect
n the optimised network. The disadvantage of this method is that it
will not account for new sites or cell-splitting, unless these are added manually which is
a ming proce
The third method is a od,
known neighbour relat into the database by hand or by
i est serv n.
However during the ne ediate
icinity of new sites or modified sites should be updated.
A2. For each site an
se, either manually or
l carrier assignments, but which are not neighbours.
Pr
pixels at the equal power boundary of the two cells exceeds a specified threshold.
The second method of neighbour generation relies upon direct input of neighbours into
the site database. This could either be manually, site by site, or by
the settings withi
time consu ss.
combination of the previous two. As in the second meth
ionships are added directly
mporting. A b er array is then generated and the Neighbour Wizard is ru
ighbour analysis, only the relationships within the imm
v
Exceptions can also be used to generate separations within ILS
Exception list can be entered into the cell page of the site databa
by importing. Exceptions represent a list of other cells which should not be allocated
co-channe
Sub-cell Object
operty Description
Neighbour List The neighbour list for a cell a
cost matrix. Neighbours can
ffects the separations created in ILSA2s
either be entered manually or created
using the Neighbour Wizard.
ception List The exception list for a cell indicates the cells for which co-channel
allocations should not be made but which are not neighbours.
Ex

4.2.5 Traffic Information / Required Number of Carriers
Either of these two inputs can be generated first:
spread traffic from sites option in the Traffic Raster Wizard.
2. The traffic raster can be generated first, using the approximated traffic spreading
set within the Terminal Types dialog box, using the Traffic Raster Wizard, and
then using the Traffic Analysis Tool to calculate the required carriers per carrier
layer.
If the required carriers are to be generated from a traffic raster, it is important that the
correct channel to carrier map is allocated to the cell layer. The map defines the
relationship between the number of TCHs available for a specific number of installed
TRX. Only a single channel to carrier map can be allocated per cell layer although five
Two forms of information about traffic are required in the ILSA2 frequency planning
process:
A traffic raster for generation of the interference table
The required carriers for every carrier layer of every sub-cell, to allow ILSA2 to
allocate the correct number of carriers
1. The required carriers can be entered directly into the site database from
known/predicted network statistics, and these can then be used to generate a traffic
raster using the
P-TN-010-001-002 Page 13

maps are supplied with ASSET. If the maps supplied do not match the configuration of
your carriers it is possible to add your own.
These t
ILSA2 requires that the site database contains the required number of carriers in each
carrier layer for the frequency plan. Also, to generate the interference table a traffic
raster is required.
wo inputs can be generated as shown in the flow chart below:
Start
Set Up Terminal
Types
Spread Traffic
Raster
Create Best Server
Array
Capture Traffic
Input Required
Carriers to Sites
Database
Create Best Server
Array
Spread Traffic
Raster
Start
Set Up Terminal
Types
Set Up Channel to
Carrier Map
Generated Required
Number of Carriers
Directly Input
Required Number of
Carriers
Calculate Required
Carriers
Finish Finish

The first ply described as generating a traffic raster,
and then from the traffic raster to calculate the required number of carriers.
Figure 4 - Flow Charts Showing Traffic Raster and Required Carriers
Generation
method (left flow chart) can be sim
Note: If you have a small number of cells that have a very high control overhead it is
possible to manually edit the required number of carriers at these sites in the
site database, after the new required carriers values have been applied by the
Traffic Analysis tool. This may be preferable to creating a new cell layer with
a different Channel to Carrier map.
Page 14 P-TN-010-001-002

When setting up Terminal Types you are defining how the traffic is spread within your
network. Each Terminal Type can be associated with one or more cell layers. This
makes it possible to separate GSM900 and GSM1800 traffic. Also held within the
ted with it is spread.
d (right flowchart) may simply be described as entering the required
number of carriers and then using them to generate a traffic raster.
T details
S
Terminal Type are the details of how the traffic associa
The second metho
he table below the database objects involved:
ub-cell Object
The traffic carried by a cell affects the creation of Carried Traffic the interference table
and can affect the generation of the required carriers
Carriers Required The required number of carriers can be entered manually or allocated
by the Traffic Analysis Tool
TRX Required The required number of TRX may be different from the carriers
required in a synthesiser or site hopping network

Interference Table
An interference table allows ILSA2 to attempt to minimise the interference generated
by the frequency plan. The interference table in ASSET details the effect of
interference for every pair of sub-cell/carrier layer combinations in the network w
4.2.6
hose
predictions overlap. It gives the effect of interference in terms of both area and traffic
be that
area wh The
inte
affected by interference. The area/traffic affected by interference is calculated to
ich is defined within an interference weights table for a mean C/I.
rference table is defined on a cell layer basis. The specific interference weights table
to be used is selected during the creation of an interference table using the wizard.
Start
Generate Best
Server Array
Generate Traffic
Raster
Generate
Interference Table
Using Interference
Table Wizard
Finish

Figure 5 - Flow Chart Showing Interference Table Generation Process

P-TN-010-001-002 Page 15

FAQ 9 - verage C/I and the percentage traffic/area
affected stored?
How is the mapping between the a
The mapping is stored in the Interference Weights tables. When generating an interference table,
you must specify which interference weights table is to be used. The default interference weights
table within ASSET appears as follows:
Default Interference Weights
0%
25%
50%
75%
100%
P
r
o
p
o
r
t
i
o
n

o
f

I
n
t
e
r
f
e
r
e
n
c
e

(
%
)
Co-Channel Adjacent Channel
-20 -10 0 10 20 30 40
Average C/I (dB)

Figure 6 - Default Interference Weights
This default interference weights table has been generated assuming that a co-channel C/I of 9dB
C/I follows a
.8dB.

FAQ 10 - enerate the adjacent channel
interference weights?
The adjacent channel curve used by the Interference Table Wizard is implied directly from the
e Interference page of the Array
FAQ 11 - eights table have?
any the network.
10% of the traffic to be operating in unacceptable
interference.
aking
assignments where a C/I of 9dB is possible.
is where the quality of a connection begins to be adversely affected, and that the
Gaussian distribution about the calculated mean, which has a standard distribution of 7
How does the Interference Table Wizard g
specified co-channel curve by applying an offset specified on th
Creation dialog box. The default offset is -18dB.

What values can the Interference W
It is not necessary to stick to a Gaussian distribution, or a maximum of 1: the table can be assigned
values to reflect the distribution/severity of interference in
For example, consider a network where
The propagation model was known to be accurate to a standard deviation of 8dB, and the C/I
assumed to be accurate to 11.3dB standard deviation.
The required C/I for acceptable operation were 9dB.
The network target was for less than
A C/I curve could be generated to measure the probability of the C/I being worse than 9dB, using
simple Gaussian statistics. However this does not bias the ILSA2 significantly against m
Page 16 P-TN-010-001-002

Alternatively you could create a curve to measure the probability of the C/I of being worse than a
e that, if it w valu ere the average in the network, result in only 10% of the real C/Is being 9dB or
rs carried out.
If an allocation would result in more than 10% C/Is being worse than 9dB the cost would be
wo e. This target value of C/I would actually be approximately 23dB if this were
A third option could be to alter the curve centred targeting 9dB in such a way that:
increased
If less than 10% C/Is being worse than 9dB the cost would be decreased.
For example, you could square the probability according to the first option and multiply by 10. This
would result in the graphs shown below:
Interference Weights - 9dB Rejection
200%
400%
600%
800%
1000%
P
r
o
p
o
r
t
i
o
n

o
f

I
n
t
e
r
f
e
r
e
n
c
e

(
%
)
11.3dB Standard Deviation >10% Interference Rejection
0%
10 20 30 40
Average C/I (dB)
-20 -10 0

Figure 7 - Interference Weights 9dB Rejection
Interference Weights - 9dB Rejection (Close Up)
25%
50%
75%
100%
P
r
o
p
o
r
t
i
o
n

o
f

I
n
t
e
r
f
e
r
e
n
c
e

(
%
)
11.3dB Standard Deviation >10% Interference Rejection
0%
20 30 40
Average C/I (dB)
-20 -10 0 10

Figure 8 - Interference Weights 9dB Rejection (Close Up)
These are only suggestions of how the problem might be approached. Other solutions may present
better results.

P-TN-010-001-002 Page 17

4.3
en the plan needs to be set up within the
ILSA2 tool itself. There are two distinct stages to setting up ILSA2, which combine to
to suit your needs. The first stage consists of initialising
Planning tool dialog.
4.3.1 ILSA2 Initialisation
The ILSA2 Initialise d certain prerequisites are
imported into ILSA2.
SETTING UP THE PLAN
Once the prerequisites have been generated th
allow you to create a plan
ILSA2, where the Network, Interference and Network Counters prerequisites can be
imported. Further options are available in the second stage, and are accessed from the
main ILSA2 Frequency
ialog allows the user to specify how

Figure 9 - ILSA2 Initialise Dialog
The ILSA2 Initialise Dialog
Property Action
allows the setting of:
Description
This option allows current network configurations from the site
database to be imported into ILSA2. Use the Import Filters button
to select the exact configuration to be planned (see 4.3.2).
If this option is selected and no filters have yet been imported, if
the user attempts to initialise a warning wil
be available for ILSA2 to plan. It is possible to initialise ILSA2
without importing filters, although planning will not be possible.
Checking this option allows a network configuration stored in
XML export files to be imported into ILSA2 for planning. Use the
Data from
memory
l appear as no cells will
Network
File
browse button to locate the required files.
To use this method, complete network data must be selected for
import. The files required are those exported using the XML export
functionality in ASSET, with all Project and Configuration options
selected, or using the Save Network option in ILSA2 (section 4.6).
Page 18 P-TN-010-001-002

Data from
memory
If this option is selected, ILSA2 will use the interference
relationships in the current interference table as inputs to the Cost
function.
If there is no interference table currently loaded, no interference
will be taken into account by ILSA2, and the only inputs to the
cost function will be the carrier and separation costs specified
within the cost matrix.
Interference
File If this option is selected, ILSA2 will use the interference
relationships stored in an interference table file (AIT) that has been
created and saved previously. Use the browse button to locate the
required file.
Selecting this option allows ILSA2 to use interference without the
need to generate an interference table each time ASSET is started.
This is of particular use when planning large networks.
If this option is used whilst an interference table is currently
loaded, the AIT file specified here will take precedence, and the
interference table in memory will be ignored.
None This option prevents ILSA2 from using handover counts as inputs
to the cost function.
Handover
Counts
File Checking this option allows handover counts stored in a handover
counts file (TXT) to be imported into ILSA2 for planning. Use the
browse button to locate the required file.
Initialise Initialise When all three prerequisites have been set as required, the final
step is to initialise ILSA2. If initialisation is successful, the main
ILSA2 Frequency Planning dialog will be displayed.

FAQ 12 - When would you not use interference?
It is generally advisable to use interference, in the form of an interference table, with ILSA2.
However it may be the case that you have little confidence in the propagation model that you are
using. In this case the interference table may be unreliable and you may wish to use ILSA2 with
separation and carrier constraints alone.
If an interference table is currently loaded in ASSET, and the Data from Memory option is selected,
ILSA2 will automatically load the interference relationships that are in the table and use them as
inputs to the cost function. In this case, should you specifically wish to plan without interference, the
current interference table should be saved to file (in case it is needed at a later date), and the
current ASSET project that is running should be closed and reopened. This will have the effect of
clearing the interference table from memory, allowing ILSA2 to plan without interference.

P-TN-010-001-002 Page 19

4.3.2 ILSA2 Import Filters
The ILSA2 Import Filters wizard allows the exact network configuration to be selected
for planning over four steps.
4.3.2.1 Import Filters Wizard Step 1

Figure 10 - ILSA2 Filter Import Wizard Step 1
On the first step of the wizard, filters and filter folders are presented as in the filter
database. Any of the filter folders, or the individual filters, in the project can be selected
to be included in planning. In a project that contains a large number of filters in various
folders, this page allows groups of filters to be selected or deselected quickly.
Page 20 P-TN-010-001-002

4.3.2.2 ILSA2 Import Filters Wizard Step 2

In the second step of the wizard, the filters chosen in the first step are presented without
the associated folder hierarchies. This page allows the user to further select any of the
filters that are required for planning. Sites that are to be considered, even if not
modified, must be included in the filters selected.
Filter priorities are also editable at this stage of the wizard. The properties of sites
which belong to multiple filters within the list are determined by the order of the filters
within the list. The properties of the top filter in the list have precedence.

FAQ 13 - What happens if a site is identified by multiple filters?
Only one set of allocations can be made to a site, even if that site is present in the results of more
than one filter that ILSA2 is planning. Consequently, the order of the filters in the list is important
and can be modified by using the up and down buttons.

P-TN-010-001-002 Page 21


The third step of the wizard allows users to select which cell layers in the project are
required to be planned. In a project that contains a large number of cell layers, this page
allows groups of filters to be selected or deselected quickly. A typical use for this
would be when only planning GSM1800 cell layers in a dual band project environment.

Page 22 P-TN-010-001-002

The last step in the wizard allows the user to make detailed selections of the
combinations of filters and cell layers that are required for planning. This step is used to
prevent unnecessary filter / cell layer combinations from being imported into ILSA2:
minimising the amount of data that the algorithm must consider will improve the rate at
which ILSA2 arrives at an optimal solution. As was the case with filters, cell layers that
are to be considered, even if not modified, must be included in the cell layers selected
here.

FAQ 14 - When to include/ignore filter/cell layer combinations?
When planning, the complexity of the filter/cell layer combinations can severely impact the speed at
which a solution is reached. If due to the nature of the frequency banding technique chosen, you
can disregard a particular cell layer since it is no possible impact on the others, it is advisable to
ignore the layer completely. This would happen when considering a dual-band network and only
planning the 900MHz layer. In this case the 900MHz layer and 1800MHz layer can be considered
independent of one another.

4.3.3 ILSA2 Plan List Dialog
After ILSA2 has been initialised, a plan list can be displayed and edited. For each
Filter/Cell Layer/Carrier Layer combination that was imported using the Import Filters
wizard you can choose to either plan, read only or to ignore the sub-cells included in
the list. The Plan List dialog is accessed from the View menu on the main ILSA2
Frequency Planning dialog.

Figure 14 - ILSA2 Plan List Dialog
The Plan List dialog displays the filter/cell layer/carrier layer combinations that were
imported into ILSA2. The dialog is used to define which combinations are to be
considered by the plan. The items that are available on the Plan List page include:
P-TN-010-001-002 Page 23

Option Description
Plan List The Plan List is a list of all the filter/cell layer/carrier layer combinations that
the cost matrix includes. There are three options for each item.
Plan The plan option enables ILSA2 to plan the carriers required within sites
satisfying the filter/cell layer/carrier layer criteria. The carrier allocations can
be modified and are considered by other carrier allocations as interferers.
Read Only The Read Only option disables ILSA2 from planning the carrier allocations
required within sites satisfying the filter/cell layer/carrier layer criteria. The
current carrier allocations can still be considered as interferers by ILSA2
when planning other carrier allocations.
Ignore This option ignores sites satisfying the filter/cell layer/carrier layer criteria.

FAQ 15 - When would you use the plan/read only/ignore options?
If you wish to plan sites then it may be important to take into account frequency allocations in
neighbouring regions. In this case the filter/cell layer/carrier layer combinations describing the
neighbouring regions should be assigned the read only option. It may also be that there are
combinations within the plan list that you neither wish to plan nor take account of. These
combinations should be set to ignore.

4.3.4 ILSA2 Cost Matrix
The cost matrix within ILSA2 allows you to define the rules within which ILSA2
operates. It allows you to choose the separation constraints, and the desirability of the
constraints being met. The ILSA2 Cost Matrix is accessed from the Cost Matrix menu,
which contains the following functionality:
Option Description
Load This option allows you to load a previously saved cost matrix (CMF file).
When loaded, the user is given the option of immediately reviewing the cost
matrix.
Save This option allows you to save the current cost matrix (CMF file).
Edit This option opens the Cost Matrix Editor where the current cost matrix can be
edited (see subsequent sections 4.3.4.1 to 4.3.4.8).
Note: When ILSA2 is closed, or when it is re-initialised, the current cost matrix is
lost. For this reason, it is suggested that large cost matrices are always saved
before ILSA2 is closed or re-initialised, and then re-loaded.
Page 24 P-TN-010-001-002

4.3.4.1 ILSA2 Cost Matrix Carrier Costs
The first folder in the ILSA2 Cost Matrix Editor is used to specify the constraints and
costs for individual carriers.

Figure 15 - ILSA2 Cost Matrix Carrier Costs
The ILSA2 Carrier Costs folder allows the user to view and edit the carrier costs (i.e.
costs associated with a single carrier on a single carrier layer of a single subcell). The
following options are available:
Cell ID The cell ID of the subcell for which a carrier cost is defined.
Cell Layer The cell layer of the subcell for which a carrier cost is defined.
Carrier Layer The carrier layer for which a carrier cost is defined.
Carrier The individual carrier for which a carrier cost is defined.
The actual cost associ
following situations:
If the cost type is forbidden, the cost will be
assigned to this carrier layer of this subcell.
If the cost type is fixed, the cost will b
Cost Type Whether the individual carrier is a Forbidden carrier or a Fixed carrier.
Cost ated with the individual carrier, applied in the
applied if this carrier is
e applied if this carrier is removed
from this carrier layer of this subcell.

FAQ 16 - How should Forbidden Carrier Costs be used?
In this way,
the cost matrix is used to fine tune how ILSA2 deals with the allocations at these sites.

It is useful to be able to edit forbidden carrier costs on an individual carrier basis if the undesirability
of making carrier allocations varies significantly between sites. It may be that, for some sites,
making a certain allocation is undesirable, while for other sites it is absolutely imperative that the
allocation is not made. Within the site database both of these situations can be considered as
forbidden carriers. When each forbidden carrier is considered by ILSA2, different costs should be
incurred depending on how important it is that the allocation is not made to this carrier.
P-TN-010-001-002 Page 25

FAQ 17 - How should Fixed Carrier Costs be used?
As with forbidden carriers, the costs assigned to fixed carriers should reflect how important it is that
ILSA2 does not de-allocate the carrier. It will be highly likely that this level of importance will vary on
a site to site basis. The cost associated with a fixed carrier would normally be set high enough such
that ILSA2 is strongly discouraged from de-allocating that carrier. If the carrier is then de-allocated,
in all probability there is something amiss in the network design that means that the inclusion of this
cost makes an improvement to the overall plan.

FAQ 18 - Why cant I assign individual carrier costs to all possible carriers?
Only forbidden and fixed carriers are considered in the carrier costs folder.

4.3.4.2 ILSA2 Cost Matrix Carrier Layer Costs
The second folder in the ILSA2 Cost Matrix Editor is used to specify the constraints
and costs for carrier layers that are to be planned.

Figure 16 - ILSA2 Cost Matrix Carrier Layer Costs
The ILSA2 Carrier Layer Costs folder allows the user to view and edit the carrier layer
costs (i.e. costs associated with actions that apply to an entire carrier layer). The
following options are available:
Filter The filter name that contains the carrier layer for which costs are
defined.
Cell Layer The cell layer that contains the carrier layer for which costs are defined.
Carrier Layer The carrier layer for which costs are defined.
Weight The weight option is used to define the importance of Filter/Cell
Layer/Carrier Layer combinations relative to each other.
Typically you would use low weightings between 1 and 10.
Allow Retune If this option is selected for a carrier layer, ILSA2 is allowed to retune
it. The option would generally be used when considering the Use
Current Plan option (section 4.4), although it has identical functionality
Page 26 P-TN-010-001-002

when creating a new plan.
With the option selected, ILSA2 is able to retune any allocated carrier
on the carrier layer. If it does so, the associated retune cost will be
incurred for each carrier that is retuned.
With the option deselected, ILSA2 is not able to retune any allocated
carriers on the carrier layer.
Note: this option is solely concerned with allocated carriers, NOT fixed
carriers.
Retune Cost The actual cost associated with retuning any carrier on the carrier layer.
The value should be set such that retuning a carrier on the carrier layer
is only of benefit to the overall cost of the plan because it will allow
considerable improvements in other areas of the network.
Note: Only filter/cell layer/carrier layer combinations that have been assigned a
planning status of Plan in the Plan List dialog will be displayed in the Carrier
Layer Costs folder.

FAQ 19 - When to use weightings?
Weightings can be used on a carrier layer by carrier layer basis to increase the importance of any
interference or separation breaking on those carrier layers. For example, interference on the BCCH
carrier is regarded as more important than interference on the TCH carriers, and so the weighting
on the BCCH carrier layers would be higher than the weighting on the TCH carrier layers.

FAQ 20 - How should the retune option be used?
The retune option for carrier layers can be used in two ways:
1. Deselecting the Allow Retune option for carrier layers that truly cannot be retuned. For
example, if adding a new cell, it may be that carriers can be found to meet acceptable
interference criteria without changing any of the current allocations on the same carrier layer.
This option would typically be tried before option 2.
2. Allowing the carrier layer to be retuned, but only at a cost. This option can be used to try to
maintain a majority of the current frequency plan. For example, when adding a few new cells to
the network, instead of retuning every cell within the region, it is best to change just enough to
meet acceptable interference criteria. This can be used to give ILSA2 slightly more flexibility
than preventing all retuning from occurring.

FAQ 21 - How would you re-plan in a localised area?
For example, take the case when adding a new site to an existing design. In this case, you would
expect to have to re-plan the immediate cells surrounding the new site
be reluctant to re-plan cells more than a neighbour relationship away, but if the plan was
significantly better then you would accept minor changes
want the majority of the existing design to be read-only
To achieve this create three dynamic filters based on polygons named Area for new site, Border
around new site and Rest of plan.
In the Import Filters Wizard, import the three filters and, in Step 2, order the priority of the filters
such that Area for new site is at the top and Rest of plan is at the bottom.
In the Plan List dialog, the cell layer/carrier layer combinations for the Rest of plan filter should be
set to Read Only, and those of the Area for new site and Border around new site filters should be
set to Plan.
P-TN-010-001-002 Page 27

In the Carrier Layer costs folder, set the Allow Retune checkbox for all the filter/cell layer/carrier
layer combinations (note that the cell layer/carrier layer combinations for the Rest of plan filter are
not present). For the cell layer/carrier layer combinations of the Border around new site filter
choose an associated cost of performing the retune. The cost should be high enough to ensure that
carriers are re-planned in the border region only if a significant improvement is made: the value
really depends on how critical it is to you that the number of changes should be minimised the
more important, the higher the cost. It may take a couple of iterations (without applying the changes
to the database) before the optimal retune cost is found.

4.3.4.3 ILSA2 Cost Matrix Equipment Costs
The third folder in the ILSA2 Cost Matrix Editor is used to specify the Site and Cell
separation constraints that ILSA2 should aim towards. A separation of 0 corresponds to
a co-channel allocation, 1 to an adjacent channel allocation, and so on. The costs
incurred if these separation constraints are not met are also defined here. The
separations and costs are defined at two levels, these being absolute minimum and
preferred values.

Figure 17 - ILSA2 Cost Matrix Equipment Costs
The ILSA2 Equipment Costs folder allows the user to view and edit the required
separations, and associated costs, for each of the equipment types. The following
options are available:
Equipment The equipment type for which a separation, and associated cost, is
defined. There are two mandatory equipment types that ILSA2
considers, Site and Cell, but any other equipment that is defined to cells
will be listed here, so that separations and costs can be specified at an
extra level of detail.
Cell separations apply to carrier assignments made on the same cell, i.e.
intra-cell separations.
Site separations apply to carrier assignments made on the same site, i.e.
inter-cell separations.
If an assignment on a cell breaks both Site and Cell separations, costs
for both equipment types will be incurred.
If any cell equipment is defined for cells, the separations and associated
costs for the equipment will take precedence over, and is therefore used
Page 28 P-TN-010-001-002

in place of, cell separations and costs.
Cell Layer The cell layer that the equipment separations apply to.
Carrier Layer The carrier layer that the equipment separations apply to.
Min Separation The absolute minimum separation required.
Min Cost The cost incurred if the minimum separation is not met.
Pref Separation The separation preferred.
Pref Cost The cost incurred if the preferred separation is not met.
and a
preferred separation of 4, with the cost of breaking it of 100, the following costs would apply:
Separation Cost (ignoring all other costs and interference)

FAQ 22 - How is the cost calculated when separation constraints are broken?
If a constraint is set to a minimum separation of 2, with the cost of breaking it of 1000,
4 or greater 0
3 100
2 200
1 1000
0 2000
As can be seen above, cost values are summed for each reduction in separation. If only the
preferred separation is broken, only the preferred cost is summed. If the minimum and preferred
separations are broken, only the minimum cost is summed.

costs are defined at two levels, these
being absolute minimum and preferred values.
4.3.4.4 ILSA2 Cost Matrix Neighbour Costs
The fourth folder in the ILSA2 Cost Matrix Editor is used to specify the First and
Second Order neighbour separation constraints that ILSA2 should aim towards. As
above, a separation of 0 corresponds to a co-channel allocation, 1 to an adjacent
channel allocation, and so on. The costs incurred if these separation constraints are not
met are also defined here. The separations and

Figure 18 - ILSA2 Cost Matrix Neighbour Costs
P-TN-010-001-002 Page 29

The ILSA2 Neighbour Costs folder allows the user to view and edit the required
separations, and associated costs, for neighbour relationships. The following options
are available:
Neighbour The neighbour relationship type for which a separation, and associated
cost, is defined. There two options considered are First Order
(Neighbour) and Second Order (2nd Order Nbr).
If both first and second order relationships exist between a pair of cells,
costs can be incurred for both separation constraints if they are broken.
Cell Layer The cell layer that the neighbour separations apply to.
Carrier Layer The carrier layer that the neighbour separations apply to.
Min Separation The absolute minimum separation required.

FAQ 23 - What is the cost if more than one constraint applies to a separation?
minimum and preferred neighbour separation constraints and (bracketed) costs are 1 (50) and 2 (5).
Separation Site Cost bour
st
all other costs and
rference)
If more than one constraint applies, the costs of breaking the constraints are cumulative. For
example, site and first order neighbour constraints might co-exist. In this case, the minimum and
preferred site separation constraints and (bracketed) costs are 2 (250) and 4 (25) respectively. The
Neigh
Co
Cost (ignoring
inte
4 or greater 0 0 0
3 25 0 25
2 50 0 50
1 250 5 255
0 500 550 50

Page 30 P-TN-010-001-002

4.3.4.5 ILSA2 Cost Matrix Exception Costs
The fifth folder in the ILSA2 Cost Matrix Editor is used to specify the exception
separation constraints that ILSA2 should aim towards. As above, a separation of 0
corresponds to a co-channel allocation, 1 to an adjacent channel allocation, and so on.
The costs incurred if these separation constraints are not met are also defined here. The
separations and costs are defined at two levels, these being absolute minimum and
preferred values.

Figure 19 - ILSA2 Cost Matrix Exception Costs
The ILSA2 Exception Costs folder allows the user to view and edit the required
separations, and associated costs, for exception relationships. The following options are
available:
MSC The MSC of the cell from which an exception has been defined.
BSC The BSC of the cell from which an exception has been defined.
Site The Site of the cell from which an exception has been defined.
Cell The cell from which an exception has been defined.
The cell to which an exce
The absolute minimum separation required. The default value is taken
from that s
Exception ption has been defined (under the Exceptions
tab in the site database).
Min Separation
et in the site database, though this can be modified here if
required.

FAQ 24 - What are the separation constraints between exceptions?
folder of the Cost Matrix. The default value of the minimum separation for each exception is taken
The separation constraints between exceptions can be manually edited in the Exception Costs
P-TN-010-001-002 Page 31

from the exception definition in the site database. The preferred separation is set to be two greater
than the minimum separation.
The site database sets a default separation of 2. In this case the following costs would apply in
ILSA2:
Separation Cost (ignoring all other costs and interference)
4 or greater 0
3 100
2 200
1 1000
0 2000

4.3.4.6 ILSA2 Cost Matrix Filter Priorities
The sixth folder in the ILSA2 Cost Matrix Editor is used to specify the priorities of the
filters that have been imported into ILSA2. The default values shown here reflect the
priorities that the filters were assigned in Step 2 of the Import Filters Wizard.

Figure 20 - ILSA2 Cost Matrix Filter Priorities
The ILSA2 Filter Priorities folder allows the user to view and edit the priorities that
each of the filters imported into ILSA2 is assigned. The properties of sites which
belong to multiple filters within the list are determined by the associated value of the
filter priority. The following options are available:
Filter The name of the filter imported into ILSA2.
Priority The priority of the filter expressed as a value. Filters with a higher value
have precedence over filters with a lower value.
Page 32 P-TN-010-001-002

4.3.4.7 ILSA2 Cost Matrix Handover Counts and Intermodulation Interference
The seventh folder in the ILSA2 Cost Matrix Editor is used to specify the costs
associated with Handover Counts and Intermodulation Interference. These costs are
considered by ILSA2 if the relevant planning options are also selected.

Figure 21 - ILSA2 Cost Matrix Handover Counts and Intermodulation
Interference
The ILSA2 Handover Counts and Intermodulation Interference costs folder allows the
user to view and edit the costs that will be incurred if these two planning options are
included in the planning process. Handover counts describe the number of handovers
that occur between two cells. Intermodulation Interference costs are only incurred if
ILSA2 knows the actual frequencies that the carriers pertain to. To enable this,
Frequency Bands must first be setup. A further option to consider intermodulation
interference is included in the ILSA2 Planning Features options (section 4.3.5.2). The
following options are available in the cost matrix:
Use Handover
Count
When this option is selected, ILSA2 imports any handover counts that
were loaded from a handover counts file during the first stage of
initialisation. The counts are then used as an input to the cost function in
a similar manner to a neighbour relationship. The cost that is added is
the number of handovers that occur between a pair of cells.
The Auto Scale and Scale options become inactive when this option is
deselected.
Auto Scale With this option selected, ILSA2 applies an automatic scaling factor
when adding the handover count costs into the cost function. The scaling
factor is calculated such that large numbers of handovers will not swamp
the other costs involved.
The Scale option is inactive when this option is selected.
Scale When Auto Scale is not selected, this option allows the user to input the
required scaling factor for the handover count costs. This method would
be used to increase or decrease the relevance of handover counts relative
to the auto scale factor.
2nd Order This option sets the cost incurred by a carrier assignment that would
cause second order intermodulation interference.
3rd Order This option sets the cost incurred by a carrier assignment that would
P-TN-010-001-002 Page 33

cause third order intermodulation interference.
Uplink Weighting This option is used to apply a weighting to the uplink frequencies. Since
these frequencies cause less interference, a typical value would be less
than 1.
4.3.4.8 ILSA2 Cost Matrix Separation Costs
The last folder in the ILSA2 Cost Matrix Editor is used to specify the costs associated
with making close carrier allocations between any two individual carrier layers within a
subcell or between subcells.

Figure 22 - ILSA2 Cost Matrix Separation Costs
The ILSA2 Separation Costs folder allows the user to view and edit the costs that will
be incurred if close carrier assignments are made between any two cell/cell layer/carrier
layer combinations that exist in the network to be planned. Costs can be specified for
separations of 0 (co-channel), 1 (adjacent channel) or 2. The folder presents a grid
formation of all possible cell/cell layer/carrier layer combinations and therefore allows
the user to put a higher emphasis on specific network relationships. The following
options are available in the cost matrix:
Page 34 P-TN-010-001-002

Property Action Description
Separation The three close separations for which costs can be defined.
Value The default cost that will be applied to all possible cell/cell
layer/carrier layer combinations in the network (as presented in the
grid) for carrier allocations at that separation.
Costs for co-channel (0) separations would generally be higher
than for adjacent channel (1) separations, which would in turn be
higher than for separations of 2.
Default
Separation
Costs
Reset to
Default
This option resets all cost entries in the grid to the default values
specified. Confirmation is required before the defaults are applied.
Search This option allows the user to move the grid quickly to a certain cell/cell
layer/carrier layer combination. The option presents a dialog allowing the user to
enter the cell ID of the x-axis (horizontal) and y-axis (vertical) cells to be located.
Either the x- or y-axis cell ID may be ignored if necessary.
Grid The grid presents all possible cell/cell layer/carrier layer
combinations that exist in the network to be planned. These are
displayed by network hierarchy MSC/BSC/Site/Cell/Cell
Layer/Carrier Layer on both the x- and y-axis.
Grid
Tabs The tabs allow the user to view the costs for the three levels of
separation.

FAQ 25 - Why edit Separations?
The ability to set individual costs for the three closest levels of separation, for any single network
relationship, allows the user to account for known trouble spots in the network. For example, the
effect of some close separations may be more serious than others, in which case it is desirable for
the cost matrix to include a high cost for making these allocations.

FAQ 26 - How were the default costs in the cost matrix set?
The default costs, seen when a new cost matrix is considered, are set such that they are of a similar
magnitude to typical interference costs. Since typical interference costs are of the order of 10
3

without considering separation constraints, the costs were given values of a similar order to 10
3
.
Constraints that were considered to be more important that others were given larger cost values.

FAQ 27 - Should I modify the default costs for different circumstances?
The costs that you use should always be adapted to the individual planning case that you are
considering. The values you apply should change according to the different levels of importance
that you assign to the different separations in the network, and to the level of constraint that you
decide to use. Of most importance is that the cost of a cell co-channel separation is greater than the
cost of a site co-channel separation, which in turn is greater than the cost of a neighbour co-channel
separation, and so on. Likewise, the cost of a co-channel separation should always be greater than
that of an adjacent channel, which is in turn greater than a separation of 2, and so on.
A typical approach to setting the cost values would be to start with an initial investigation into the
costs incurred from interference alone. This will form the basis of the values applied to all other
separation constraints in the network. An iterative approach is then suggested, where plans are
applied (but NOT committed) to the database, analysed against the same criteria used for the initial
analysis, and, if not satisfactory, re-planned after fine tuning the costs in the cost matrix. It may take
several revisions to arrive at an optimal set of costs.

P-TN-010-001-002 Page 35

4.3.5 ILSA2 Options Dialog
The ILSA2 Options dialog, accessed from the Tools menu on the main ILSA2
Frequency Planning dialog, allows the user to set a number of display and planning
options for use with ILSA2.
4.3.5.1 ILSA2 General Options
The ILSA2 General Options page allows the user to set the display and save options for
use with ILSA2.

Figure 23 - ILSA2 General Options
The ILSA2 General Options page allows the setting of:
Property Action Description
X-Axis:
Iteration
This option draws a new section of graph when an improvement
has been made to the cost of the frequency plan.
Graph
X-Axis:
Increment
This option draws a new section of graph at steady intervals in the
number of iterations.
Page 36 P-TN-010-001-002

Refresh Rate This parameter indicates how quickly the main ILSA2 Frequency
Planning dialog refreshes itself. The actual refresh rate is
calculated by multiplying the value entered in the field by 500ms,
e.g. if 10 were entered, the dialog will be refreshed every 5s.
Setting a slow refresh rate means that several improvements to the
plan may be made before the dialog is updated, and will therefore
not be seen by the user. Setting a faster refresh rate increases the
chance of seeing a cost improvement as soon as one is found.
Display
Log Results in
Message Log
Checking this option writes the current cost to the message log
every minute.
Saving Auto-Save
Assignments
Setting this option enables the current best plan that ILSA2 has
found to be periodically saved automatically. With the option
checked, the user can specify how often, and to which location the
plan can be saved. The file that is saved is an XML file of all data
that is applicable to the frequency plan.
4.3.5.2 ILSA2 Planning Features
The ILSA2 Planning Features page allows the user to set a number of extra options that
ILSA2 will use in the planning algorithm.

Figure 24 - ILSA2 Planning Features Options
The ILSA2 Planning Features page allows the setting of:
Use Frequency
Hopping Diversity
Gain
When this option is selected, ILSA2 will apply a gain to the interference
costs that assignments incur on any frequency hopping subcells. The
gain that is applied is dependent on the number of frequency hopping
carriers that will be allocated to subcells.
Aggregate Carriers
Required under Site
Hopping
This option applies to subcells that have Frequency Hopping enabled,
and Site Hopping selected as the hopping type.
If selected, ILSA2 takes the carrier requirement of each sub-cell to be
the sum of all carriers required for all subcells with which it is
synchronised in frequency hopping (that is, co-site, co-cell layer site
hopping subcells). This is typically used in nominal planning when
P-TN-010-001-002 Page 37

traffic analysis has been used to set the required carriers.
If unselected, ILSA2 presumes that site hopping synchronised sub
on a site have already had their carrier requirements set, with all
synchronised subcells on that site sharing the same carriers. This is
-cells
typically used in when planning using data from an existing network.
Use Antenna
Hopping Gain
assumes that a fixed number of antennas (2) are
When this option is selected, ILSA2 will apply a gain to the interference
costs that assignments incur on subcells with Antenna Hopping enabled.
The gain that is applied
available to hop over.
Use DTX load
factors as set in the
se
which DTX is enabled is multiplied by
site databa
Selecting this will reduce the interference caused by sub-cells with DTX
set. The weighting of the cells on
the VAF set in the site database.
Consider
Intermodulation
Interference
rmodulation
dictate how close an intermodulation frequency would need to be to a
Setting this option means that ILSA2 will take inte
interference into account in the planning process.
When selected, tolerance values for both 2nd and 3rd order
intermodulation interference can be which specified. These values
given carrier before it is considered to interfere.
Selecting this option will cause ILSA2 to allocate frequencies according
to the group planning pattern allocated to the cell layer.
Note: ILSA2 only maintains group planning patterns on a cell basis, not
on a site basis. E.g. within every cell all the carriers will be a member of
a single group, such as A1 or B1. Groups allocated to a si
will not necessarily maintain the group pattern, i.e. a grou
may be allocated to more than one cell on the same site.
interference as an input to the cost function.
If the option to minimise interference by t
function will take as an input the value of
an allocation from the interference table.
If the interfe
selecting thi
by ILSA2.
If the option to minimise interference by area is selected, the cost
from the interference table.
If this option is sele
input a combination
interference table.
The ratio of traffic vs. area can be specified. 0 indicates that only
area will be used and 100 indicates that only traffic will be used.
If the interference table has been generated without a Traffic r
selecting this option means that only the proportion of interfer
ILSA2.
The cost due to interference of ma
allocation is given by the following formula:
|
|
|
| +
=
w A w T
C
)) 1 ( ( 100 .
200
. \ subcell
n
hannel allocation
where:
C = cost added to cost function by the co- or adjacent c
Use Group Planning
te, however,
p, such as A1,
Minimise
Interference by:
These options provide ILSA2 with three different methods of using
1 - raffic is selected, the cost
the traffic affected due to
rence table has been generated without a Traffic raster,
s option means that no interference will be considered
2 -
function will take as an input the area affected due to an allocation
3 - cted then the Cost Function will take as an
of the traffic and area affected from the
aster,
ence
that is contributed by the area affected will be considered by
king a co-channel or adjacent channel
Page 38 P-TN-010-001-002

T = affected traffic value (mE) from interference table
w)
affic and area) to the
same level as the other costs in the cost function.
A = affected area value (km
2
) from interference table
w = % contribution of traffic hence A is multiplied by (1
n
carriers
= total number of carriers required on the subcell
Note: the multiplying factor of 100 is used to scale the affected area
values to the same level as the traffic values; the multiplying factor of
200 is used to scale the interference (made up of tr

FAQ 28 -
d if the site database indicates that frequency
ou wish to create a plan that considers the
reduction of interference that this strategy provides.
u ty gain if
using frequency hopping but without
modifying every sub-cells frequ tings

FAQ 29 -
at is the difference in gain between base-band, synthesised and site
rnal lookup table to determine what gain is provided for a particular
number of hopping carriers.
Hopping Carriers Hop ity
Gain (dB)
When should Frequency Hopping Diversity Gain be used?
Frequency hopping diversity gain should be enable
hopping is enabled on particular sub-cells and y
Yo would disable the frequency hopping diversi
your plan does not use frequency hopping
you want to determine what could be achieved not
ency hopping set
How is the frequency hopping diversity gain calculated and considered with
ILSA2? Wh
hopping?
ILSA2 currently uses an inte
Number of Frequency
ping Divers
2 3.0
4 5.0
5 5.5
6 6.0
7 6.3
8 6.5
9 6.8
<=1 0.0
3 4.0
10 6.9
>=11 7.0
The gain value in dB is converted by
in the following method in order to give the reduction:
ILSA2 into a linear gain, and is then applied to the original cost
FH no FHDG
C
_
where:
G
linear
= FHDG expressed as a linear value
linear DG
G C / =
C
FHDG
= cost, including the gain achieved by adding FHDG, added to the cost function
C
no_FHDG
= cost excluding the gain achieved by adding FHDG
P-TN-010-001-002 Page 39

ILSA2 does not distinguish between the hopping strategy used other than the gain provided by the
potentially greater number of frequencies that synthesised or site hopping uses.
FAQ 30 - uld you choose to aggregate the carriers required under site hopping?
You would generally choose to aggregate the carriers required when considering a new nominal
assume that the carriers assigned are already shared between the synchronous
subcells.
ent, determined using traffic analysis, of 4, 2 and 3 had been set on the three subcells
respectively.
each subcell, with the same 9 carriers being allocated to each
subcell.
If ILSA2 were to plan this site without aggregating the carriers, the common carrier requirement will
each subcell, with the same 4 carriers
being allocated to each subcell.
FAQ 31 -
Antenna hopping gain should be enabled if you wish to create a plan that considers the reduction of
interference that this strategy provides. The gain is applied to carriers on all cells that have antenna
FAQ 32 - hopping gain calculated and considered with ILSA2? Is the
quency hopping gain?
SA2 currently uses the frequency hopping diversity gain lookup table to determine what gain is
for a particular number of hopping carriers and antennas. The gain that is applied is
ted s follow
where:
hopping diversity gain lookup table
number of antennas used by subcell
value (G
AH
) in dB is converted by ILSA2 into a linear gain, and is then applied to the
linear AH no AH _
C
no_AH
= cost excluding the gain achieved by using AH
G
linear
= G
AH
expressed a
The gain that the antenna hopping technique provides is completely independent of the frequency
gain that frequency hopping diversity allows. It
uses the frequency hopping diversity gain lookup table only as the source of the gain values to use.

When wo
plan, with the carrier requirement set on each subcell using traffic analysis. Conversely, if the site
hopping subcells under consideration were part of an existing plan, it would be more likely that you
wish ILSA2 to
For example, consider a single tri-sector site with site hopping FH subcells assigned. A carrier
requirem
When ILSA2 plans this site using the aggregate carriers method, it will set a common carrier
requirement of 9 (4 + 2 + 3) on
be 4 (the highest requirement on any of the subcells) on

When should Antenna Hopping Gain be used?
hopping enabled in the site database.
You would disable the antenna hopping gain if your network does not use antenna hopping.

How is the antenna
technique linked with fre
IL
provided
calcula a s:
) (nAntenna G G
FH AH
=

G
FH
= frequency
nAntenna =
The gain
original cost in the following method in order to give the reduction:
G C C / =
where:
C
AH
= cost, including the gain achieved by using AH, added to the cost function
s a linear value
hopping technique applied to the subcells, or the

Page 40 P-TN-010-001-002

FAQ 33 -
enabled. Note: DTX cannot be enabled on the BCCH carrier.
This means that some carrier alloca twork will have DTX enabled, and others will
not. The carrier allocations without DTX enabled need to be planned more carefully than allocations
ILSA2 allows you to discriminate between the two

FAQ 34 -
that only carriers are allocated from frequency groups then tick the group
planning button.
However, it is recommended that for better frequency plans that ILSA2 is given free reign to
id
FAQ 35 - hen a combination of
the two?
ill make ILSA2 pay more
attention to high traffic areas in the plan when reducing interference.
erence table then you should/must select to
minimise interference by area.
you have only partial confidence in the traffic statistics, or if you wish to bias the plan towards the
rban areas while trying to maintain a reasonable quality across the network, then you may wish to
sider using a bination of both traffic and area.
4.4 S P V P
planning features, there is one last parameter to set before planning can commence.
A setting on the main ILSA2 Frequency Planning dialog allows the user to choose to
either create a new plan or to load the initial carrier assignments from the site database.
When should DTX load factors be used?
DTX load factors should be enabled in ILSA2 to plan for networks where some or all of the BTSs
have DTX
tions within the ne
with DTX and so setting up DTX for use within
settings.
When should Group Planning be used?
If you want to ensure
minimise the interference by assigning carriers in any fashion rather than restricting it to rig
groups.

When should you use traffic to plan with, when area and w
You should plan using traffic if you have a reasonable to high level of confidence in the traffic
statistics that you have used to generate the interference table. This w
If you have no confidence in the traffic statistics that you used to generate the interference table, or
if you did not use a Traffic raster to create the interf
If
u
con com

TARTING LANNING AND IEWING ROGRESS
Once ILSA2 has been set up with an appropriate plan list, cost matrix and required
P-TN-010-001-002 Page 41

Figure 25 - Main ILSA2 Frequency Planning dialog
The Plan section of the main ILSA2 Frequency Planning dialog allows the user to
choose to:
Action Description
Use Current Plan Selecting this option will start ILSA2 with the current plan applied in the
database. This may retain a larger number of the original channel
allocations.
Create New Plan Selecting this option will start ILSA2 planning with an entirely random
frequency plan.

FAQ 36 - When should you create a new plan and when should you use the current plan
from the database?
If you are creating a frequency plan for a new network, carrying out a complete regional retune or
implementing a new technique, such as FH, then you will probably wish to create a new plan. This
randomises the initial assignments and so will take slightly longer to reach an acceptable result,
however it does ensure that any minimisation dead-ends reached after prolonged optimisation
followed by a change in planning strategy are avoided.
If you are adding a small number of new sites to an existing network, then it is highly desirable to
minimise the number of changes that the frequency planner makes. Consequently, you would
choose to use the current plan from the database as the starting point.
The default is to use the current plan.

4.4.1 Commencing Planning
With the plan type selected, it is possible to commence planning. The first phase of
planning is known as Cost Caching, and is displayed as a series of progress dialog
boxes that occur after Start has been pressed. The purpose of cost caching is to load all
the costs that the algorithm cost function will process at once, thus preventing repeated
calls to memory that would be detrimental to the overall performance.
With Cost Caching complete, the main planning stage will commence, where ILSA2
attempts to meet all the rules that have been created in the cost matrix, and
simultaneously reduce the average level of interference per carrier.
Page 42 P-TN-010-001-002

4.4.2 Viewing Planning Progress
When ILSA2 is running, the progress that the algorithm is making can be viewed in a
number of different methods.
4.4.2.1 Textual Information
During planning, a number of new items of information become available on the main
ILSA2 Frequency Planning dialog.

Figure 26 - Main ILSA2 Freuqnecy Planning dialog during planning
The following information is displayed during the planning process:
Action / Property Description
Start This button starts a new plan. If you press the button while there is still a
frequency plan in memory then ILSA2 asks you whether you wish to
discard the current plan.
Stop/Continue This button has three states. If there is no current plan in memory then
the button is greyed out. If a frequency plan is in progress then the
button becomes enabled as a Stop button, pausing ILSA2. If a plan has
been stopped and is still in memory then the button becomes a Continue
button allowing you to restart ILSA2 on the current plan.
Status The Status field gives the status of the current plan. This may be:
Planning this indicates that ILSA2 is in the process of reducing
network interference and trying to meet separation constraints.
Paused this indicates that a plan has been stopped and is still in
memory.
Finished this indicates that ILSA2 has achieved a cost of 0 with the
current plan.
Start Time The Start Time Field gives the date and time at which planning started,
to the nearest second.
Carriers to Plan The number of carrier allocations that ILSA2 must make to satisfy the
current plan.
Initial Cost The cost of the initial allocations that ILSA2 makes when planning
commences. If a new plan is being created then this will be the cost of
an effectively random allocation. If a current plan from the database is
being used, this is the cost of the current plans allocations.
P-TN-010-001-002 Page 43

Current Plan Cost The cost of the current best plan that ILSA2 has discovered.
Iteration The number of iterations that have been carried out. Note that the value
displayed relates to the number of iterations that the algorithm has
performed, not the number of times that the screen has been refreshed.
(Interference)
Show
Checking this box enables the worst interference for an allocation and
the average interference in the network to be displayed, both textually in
the ILSA2 dialog box and in the ILSA2 graph.
(Interference)
Average
The average interference in the network.
(Interference)
Worst
The worst interference for any single carrier allocation.

FAQ 37 - Why would ILSA2 stop of its own accord?
design. An
example might be planning a small network of 10 sites with a full GSM band of carriers!

FAQ 38 - Why does the Worst Interference sometimes increase with time?
t of the plan, then it is
possible for the worst case interference to increase occasionally with time.
nt the worst interference increasing since it is the average interference that
ILSA2 tries to minimise.

FAQ 39 - How long should ILSA2 be left running?
s available. The stability of the
improvement is best judged by using the ILSA2 Graph function.
eriod and only modest (but potentially beneficial) improvements can be
made over many hours.
n whether you wish the plan
to satisfy a quality threshold, or whether it must be as good a possible.

ILSA2 only stops when the cost of the plan reaches zero. This is really only possible when the
planning constraints were really very easy to satisfy which is unlikely in a real network
It is possible for an average improvement in the level of interference within the plan to be coexistent
with a worsening of the interference between one or more carrier allocations. Since an average
improvement in the level of interference results in a lowering of the cos
It is not possible to preve
ILSA2 should be left running until there has been a considerable period of time with no
improvement. The time that ILSA2 takes to find the optimum plan will depend upon the number of
allocations that are required, and the number of frequencie
If the cost matrix is large, ILSA2 may have to be left running for several hours at a time. However,
remember that the rate of improvement decreases with time so vast improvements are made
within a relatively short p
The decision of how long to leave ILSA2 running ultimately depends o
Page 44 P-TN-010-001-002

4.4.2.2 Graphical Information
In addition to the information displayed on the main dialog, it is also possible to view
the progress of the algorithm graphically.

Figure 27 - ILSA2 Cost/Interference Run Time Graph
The graph plots three sets of data: using the left-hand axis, the cost of the current best
plan is plotted (red); using the right-hand axis, the worst interference (blue) and average
interference (green) are plotted. Two other options are available to the user regarding
the graph:
Print This option allows the user to print the current ILSA2 graph. The user is
first presented with a page setup dialog, where the positions, margins,
chart size and units can be set. Printing is then started from the standard
operating system print dialog.
Note: planning must be paused to use this option.
Snapshot This option allows the user to save a snapshot of the current ILSA2
graph as a bitmap file (.bmp).
Note: planning must be paused to use this option.

P-TN-010-001-002 Page 45

4.5 ANALYSING RESULTS
Once ILSA2 has been stopped it is possible to view the allocations that have been made
in the current best plan, by selecting Assignments from the View menu on the main
ILSA2 dialog.

Figure 28 - ILSA2 Carrier Assignments dialog
The Carrier Assignments dialog box allows the user to view two main items:
Carrier Statistics, in terms of the number of allocations per frequency, and the
minimum reuse distance.
Cell Statistics, in terms of the interference on each allocation that is made.
If the statistics are acceptable the user can apply the allocations to the database this is
achieved by selecting the Apply to Database option from the Tools menu on the main
ILSA2 dialog. Once a plan has been applied to the database, the same analysis as
carried out on the original frequency plan (section 4.1) should be carried out to verify
that an improvement has been made.
Alternatively, if the statistics are unacceptable, for example if BCCH carriers are
experiencing worse interference than TCH carriers, then it is possible to continue
planning. Restarting planning after applying the plan to the database is another option
that can improve the quality of the plan, due to a random element within the ILSA2
algorithm.
All of the columns within the carrier assignments dialog box can be ordered by clicking
on the column heading.
Page 46 P-TN-010-001-002

Carrier and Cell statistics can be viewed based on the following categories:
Filter The Filter whose carrier assignments are to be viewed
Cell Layer The Filter/Cell Layer combination whose carrier assignments are
to be viewed
Carrier Layer The Filter/Cell Layer/Carrier Layer combination whose carrier
assignments are to be viewed

4.5.1 Carrier Statistics
The Carrier Statistics section provides an analysis of the individual carriers that have
been allocated to the filter/cell layer/carrier layer selection.
Heading Description
Total Assignments The total number of carrier assignments made for the selection.
Carrier The carrier whose analysis is detailed in the row.
Allocations The number of allocations of the carrier.
Minimum Reuse (km) The minimum distance between cells where allocations of the carrier
have been made.
Note: allocations made to different cells on the same site will give a
minimum reuse distance of 0km.

4.5.2 Cell Statistics
The cell statistics section provides an analysis of the individual carrier allocations that
have been made within the filter/cell layer/carrier layer selection.
Heading Description
Total Sites The total number of sites within the selection.
Total Cells The total number of cells within the selection.
Worst Cell The cell with the highest total cost of all allocations on that cell.
Worst Cost The associated cost on the worst cell.
Average Cost The average cost that each cell contributes.
Cell The cell at which the allocation occurs.
Cell Layer The cell layer within which the allocation occurs.
Car. Layer The carrier layer within which the allocation occurs.
Carrier The carrier allocated.
Cost The cost of the carrier allocation.

FAQ 40 - Why have only alternate carriers been assigned even though I have a contiguous
band of carriers?
This is an indication that the adjacent interference is more dominant than co-channel which is
incorrect. The most common reason for this is that the C/I adjacent offset has the wrong sign. It
should be negative, with the default being 18db.

P-TN-010-001-002 Page 47

FAQ 41 - What carrier allocation distribution should I expect?
ILSA2 attempts to minimise the cost of the plan continuously. There is not a fixed carrier allocation
strategy but typically there is a fairly uniform distribution.

FAQ 42 - How do I interpret the interference values?
The cost value is the summation of all the associated costs of making that assignment. If this
number is less than the minimum separation/retune cost then this is purely an interference cost.
Clicking on the interference column heading allows you to toggle which assignments caused the
most and least cost to the plan. If a large number of assignments have high costs then the
constraints are proving hard e.g. too few carriers or too great separation requirements for the
neighbours or second order neighbours.

FAQ 43 - My plan uses frequency hopping but when I create the interference array, my
results arent as good as Id expected why?
To analyse a plan that uses frequency hopping, you must choose a connection type array since
these are the only ones that consider hopping carriers.

4.6 FURTHER OPTIONS
There are several further options that are available to the user from the main ILSA2
Frequency Planning dialog. These options concern saving, exporting and importing
allocations, and re-initialising ILSA2, as follows:
Save Network This option is available from the File menu of the main ILSA2
Frequency Planning dialog. Selecting this option exports the current
network, including all project and configuration settings, and the
allocations that ILSA2 currently holds, as multiple XML files to the
folder location specified.
Export Assignments This option is available from the File menu of the main ILSA2
Frequency Planning dialog. Selecting this option exports the current
carrier allocations that ILSA2 holds, as a single XML file to the folder
location specified. Only information that is applicable to the frequency
plan is included in the XML file.
This is a useful option, should you wish to analyse the allocations that
ILSA2 has made in other software programs, prior to accepting or
rejecting them.
Import Assignments This option is available from the File menu of the main ILSA2
Frequency Planning dialog. Selecting this option imports the carrier
allocations stored in an XML file.
Initialise This option is available from the Tools menu of the main ILSA2
Frequency Planning dialog. Selecting this option allows the user to re-
initialise ILSA2 from the very start of the process, without the need to
close, then restart, ILSA2. During re-initialisation, the user is prompted
to confirm whether the current assignments can be overwritten.
Help Contents This option provides a link to the ILSA2 specific help contained within
the tool.

Page 48 P-TN-010-001-002

5 ALGORITHM DESCRIPTION
This section of the application note gives detail about the ILSA2 algorithm itself,
briefly describing the nature of the problem, the solution type and the cost function of
the algorithm.
5.1 PROBLEM DEFINITION
Before we describe the ILSA2 algorithm it is sensible to consider the size of the
problem that we are attempting to solve. Consider a small example network. Its
characteristics are as follows:
S = Number of Sites = 10
C = Number of Cells = 30 = 3 cells / site
A = Number of Carrier Allocations Required = 60 = 2 carriers / cell
F = Number of Available Frequencies = 20
Assuming all carriers can be allocated to all carrier allocations, then the number of
possible carrier allocations is given by:
78
60
10 * 15292 . 1
20
=
=
=
A
F s NumberPlan

If we assume that there are no permissible co-channel allocations within a cell then this
value is reduced:
77
30
10 * 47462 . 2
!
30
60
20
! 20
!
!
=
|
|
|
|
|
.
|
\
|
|
|
.
|
\
|
|
.
|
\
|
=
|
|
|
|
|
.
|
\
|
|
|
.
|
\
|
|
.
|
\
|
=
C
C
A
F
F
s NumberPlan

Even if we assume that there are no co-channel allocations within sites, and there is a
larger reduction in the number of possible plans, there are still:
P-TN-010-001-002 Page 49

74
10
10 * 86525 . 2
!
10
60
20
! 20
!
!
=
|
|
|
|
|
.
|
\
|
|
|
.
|
\
|
|
.
|
\
|
=
|
|
|
|
|
.
|
\
|
|
|
.
|
\
|
|
.
|
\
|
=
S
S
A
F
F
s NumberPlan

Clearly checking every possible frequency plan for a reasonable size network would
take a prohibitive period of time, even if the period of time taken to check a plan were
only of the order of 1milli-second. This being the case, algorithms need to be developed
to focus processing power on high probability solutions. These algorithms are generally
known as search algorithms.
5.2 SEARCH ALGORITHMS
Search algorithms specialise in looking for solutions to problems that have too large a
solution space (i.e. too many possible solutions) to allow a simple solution. There is a
vast body of both popular science and technical literature describing search algorithms,
but below is a simple description.
Search algorithms can be visualised as a person moving through a maze. Every time the
person arrives at a junction, they are presented with a number of paths leading to other
junctions. They choose their path depending upon a choice of strategy, for example
keeping their left hand on the wall (always taking the path furthest to the left), or
choosing the path that looks the most promising. If they find themselves at a junction
that they have been to before, then they have a strategy to prevent themselves travelling
in circles, for example back tracking and taking another route. If the person comes to a
dead end they may turn around and continue from a previous junction. Eventually the
person will solve the maze. If it is a large maze, with lots of junctions, then this may
take a very long time. However different strategies may result in the solution being
found more quickly than others.
Similarly a search algorithm moves through a series of states. At each state it is possible
to move to a number of other states. The search algorithm makes a decision as to which
state to move to according to a strategy. If the search algorithm finds itself at a state that
it has been at before, then it has a strategy to prevent it looping. If there are no new
states that the search algorithm can move to, then it has a strategy to move back and
continue the search from a previous state. Eventually the search algorithm will solve the
problem. However if it is a very large problem, with lots of states, this may take a very
long time. Again different strategies may result in the solution being found more
quickly than others.
Some search algorithms have very simple strategies. Examples of these are depth first
and breadth first algorithms. The depth first algorithm is the algorithmic equivalent of
always taking the left most paths in the maze. The breadth first algorithm is the
algorithmic equivalent of checking every junction off your starting position, and then
every junction off these junctions.
Page 50 P-TN-010-001-002

More advanced search algorithms use the algorithmic equivalent of taking the path that
looks like the best one. Search algorithms that take this approach are known as
heuristic search algorithms. These algorithms use a cost function, to determine the
most desirable next state. Typically this will be the state with the lowest cost. The
effectiveness of these algorithms depends largely upon the applicability of the cost
function to the problem, and also to refinements to the search strategy to allow
backtracking from dead ends and loops.
5.3 ILSA2 SEARCH STRATEGY
ILSA2 is an advanced heuristic search algorithm, taking into consideration the latest
techniques in combinatorial mathematics.
ILSA2 initialises with a random frequency plan (if it is chosen not to load the current
plan from the database). This means that for any two runs of ILSA2 the results may not
be the same. Indeed it is true that certain starting frequency plans can allow ILSA2 to
make either more rapid initial improvement or allow a much better plan to be found
within a reasonable period of time.
The Local Search element of ILSA2s name indicates how ILSA2 reduces the
number of options it has for new states derived from a current state. ILSA2 pays special
attention to areas of high cost within the network (analogous to areas of high
interference), temporarily ignoring lower cost areas. This allows ILSA2 to make very
rapid initial progress. For example, if ILSA2 is attempting to plan for a network
requiring 60 carrier allocations, with 20 available carriers, and identifies a subset of 10
high cost carrier allocations, then the maximum number of new states that ILSA2 needs
to consider has been reduced from 3.8*10
25
to 6.1*10
12
.
Random changes can be made by ILSA2 if only low improvement rates are being
achieved, or if a dead end is reached.
5.4 COST FUNCTION DESCRIPTION
The principle behind the algorithm used in the planning tool is that a single number, the
cost, measures the effectiveness of any particular frequency plan. The algorithm then
tries to minimise the cost over the set of all possible frequency plans. ILSA2s cost
function measures how much interference there is in the network, what separations
have been broken and also allows for the different weights that the user may have
imposed to different sub-cells depending upon their importance.
P-TN-010-001-002 Page 51

For a given frequency plan the value of the cost function is given by the formula:

)
+ + +
|
|
|
.
|
\
|
+ + =
|
.
|
\
|
= |
.
|
\
|
=
i
i i i
j
ij
j
ij
j
ij i h d r s a c w
f f f f
Cost
j i j i
1

Where:
a
ij
= The adjacent channel interference caused on allocation i by allocation j
(Units: 200*mE or 20,000*km
2
)
c
ij
= The co-channel interference caused on allocation i by allocation j (Units: 200*mE
or 20,000*km
2
)
f
i
= The frequency allocated at allocation i
i,j = Members of the set of all frequency allocations
r
i
= The retune cost associated with allocation i
d
i
= The fixed or forbidden carrier cost associated with allocation i
s
ij
= The separation costs (from equipment, neighbours, exceptions or close
separations) between allocations i and j
h
i
= The handover count and intermodulation interference costs associated with
allocation i
w
i
= The weighting factor applicable to carrier allocation i

Page 52 P-TN-010-001-002

Appendix A - Frequency Plan Example
A.1 Scenario Description
The exercise explained below details the complete regional frequency retune of a 33
site network. The retune is carried out with the four aims of:
Decreasing the overall level of interference.
Adding an additional site for coverage.
Allowing sectorisation of 6 existing sites.
Allowing for an increase in traffic of 20%.
The individual sites are either omni-directional or tri-sectored, with appropriate
antennas allocated. It is important to note that the sites detailed are an approximation of
a network they are not real sites! Thus no detailed site optimisation has been carried
out. They are all 25m high, have identical Power Amplifier (PA) output settings, and a
maximum Timing Advance (TA) of 63 GSM bit periods.
This example assumes that the network belongs to a GSM900 operator and hence only
GSM900 frequencies are considered. FH and DTX are not in use, and the original
frequencies have been planned using traditional group planning techniques with a 3*9
reuse pattern. The dimensions of the geographical area under consideration are 20.0km
(width) by 15.0km (height). As this is an exercise, 50m resolution predictions are used,
with a radius of 25km.
In this example, 60 frequencies are assumed to be available (1-30, 32-61) and split into
two carrier layers:
1. The BCCH carrier layer contains frequencies 1-18 that are dedicated for use as
control carriers.
2. The TCH carrier layer contains frequencies 19-30 and 32-61, for use as other
carriers.
A single cell layer was used with no MRP, FH or DTX. No forbidden or fixed
frequencies were considered.
A.2 Initial Network Configuration
A.2.1 Network before Site Reconfiguration
The following figure shows the best server array for the initial network configuration,
which consisted of 33 sites and 87 cells:
P-TN-010-001-002 Page 53

Figure 29 - Best Server Coverage of Initial Configuration
The initial frequency allocations for the example were made using a simple 3*9 reuse
pattern roughly applied to the sites in the network.
The statistical reports detailing the performance of this allocation are shown in the
following section. In summary:
Page 54 P-TN-010-001-002

36.15% of the area covered has a mean C/I of less than 12dB due to the worst
individual interferer on the worst carrier.

Figure 30 - Worst Inteferer Array of Initial Configuration
P-TN-010-001-002 Page 55

17.63% of the area covered has a mean C/I of less than 12dB on an average
connection, interference averaged across carriers.

Figure 31 - Average Connection Array of Initial Configuration
Note: For a mean C/I of 12dB with a model of standard deviation 8dB one could
expect 40% of calls to experience a C/I of worse than 9dB. A C/I is of 9dB is
specified level for acceptable quality, as detailed in the ETSI GSM Standards.
A.2.2 Worst Interferer Array Statistics
Statistics shown are for interference levels greater than or equal to: [12dB].
TOTAL INTERFERED AREA (km): 283.79
POOR QUALITY AREA [< 12 dB] (km): 102.58
POOR QUALITY AREA [< 12 dB] (%): 36.15
GOOD QUALITY AREA [>= 12 dB] (km): 181.21
GOOD QUALITY AREA [>= 12 dB] (%): 63.85
Page 56 P-TN-010-001-002

CATEGORY TOTAL
INTERFERED AREA
(km)
POOR QUALITY
AREA (km)
POOR
QUALITY
AREA (%)
Industrial area 2.94 0.58 19.57
Dense urban 0.00 0.00 0.00
Urban 0.31 0.00 0.81
Suburban 0.37 0.07 18.37
Dense Suburban 19.30 3.20 16.57
Rural / Village centre 9.33 3.87 41.52
Agricultural land 187.01 73.15 39.11
Non agricultural land 14.12 4.72 33.46
Semi natural vegetation 8.43 3.99 47.35
Water features 4.78 1.89 39.59
Wetlands 0.00 0.00 0.00
Deciduous wood/forest 11.20 3.99 35.63
Coniferous wood/forest 24.33 6.23 25.59
Mixed wood/forest 1.67 0.90 53.74
Isolated high-rise buildings 0.01 0.00 0.00
Road/motorway junctions 0.00 0.00 0.00
A.2.3 Average Connection Array Statistics
P-TN-010-001-002 Page 57

CATEGORY TOTAL
INTERFERED
AREA (km)
POOR
QUALITY
AREA (km)
POOR
QUALITY
AREA (%)
Industrial area 2.97 0.24 8.24
Dense urban 0 0 0
Urban 0.31 0 0
Suburban 0.37 0 1.36
Dense Suburban 19.41 0.86 4.44
Water features 4.83 0.68 14.03
Wetlands 0 0 0
Deciduous wood/forest 11.32 2.49 22
Mixed wood/forest 1.72 0.59 34.3
Isolated high-rise buildings 0.01 0 0
Road/motorway junctions 0 0 0
A.3 Network Retune
A.3.1
as been added
and sectorisations carried out. No predictions are missing and the coverage from the all
Network after Site Reconfiguration
The figure below shows the coverage for the region after the new site h
the sites is sensible. The new network consists of 34 sites and 102 cells.
Page 58 P-TN-010-001-002

Figure 32 - Best Server Coverage after Addition/Sectorisations
A.3.2
ted.
set-up according
to the multiple carrier layer and frequency banding technique previously described.
e y required since we are creating a
m
The nerated with the Neighbour Analysis tool. They were examined
t
requ he region considered, and
o
betw
Cha
Frequency Planning Process
Creating the Prerequisites
The propagation model had already been tuned, predictions existed for the sites
involved and a best server array crea
The available frequencies and frequency allocation strategy had been
Th current frequency allocations were not actuall
co pletely new plan.
neighbours were ge
and are assumed to be correct. No exceptions were used.
A raffic raster was generated and the Traffic Analysis tool used to calculate the
ired number of carriers. 1200 Erlangs were spread over t
a t tal of 328 carriers were calculated to be required over the 34 sites an average of
een 3 and 4 per cell (between 1 and 8 carriers were required per subcell). The
nnel to Carrier map used was the Standard_GSM mapping, provided with ASSET.
The Interference Table Wizard was then used to generate an interference table. This
table assumed that a real C/I of 9dB corresponds to the point when interference
P-TN-010-001-002 Page 59

becomes significant, and that the C/I is subject to a Gaussian distribution with a
standard deviation of 7.8dB.
the Plan
; no
priorities were necessary in Step 2; the cell layer was added in Step 3; and no
he region, create new plan was
ed for planning.
editor:
carrier layer, as opposed to 1 for the
d TCH carrier layers, with
ghbour constraints were left at the
No exceptions were considered; filter priorities were ignored as only a single filter
ts and intermodulation interference were not
considered; no extra costs were set for making individual close separation
traffic
areas, i.e.
restricted to
inutes
le.
Setting Up
ILSA2 was initialised using the filter import wizard: a filter that included the sites and
cell to be planned (numbering 34 and 102 respectively) was selected in Step 1
modifications were necessary in Step 4.
Since the aim is to create an entirely new retune of t
selected on the main ILSA2 dialog.
In the Plan List dialog, both carrier layers were select
The following settings were made using the Cost Matrix
No fixed or forbidden carriers were considered
A weight of 3 was assigned to the BCCH
TCH carrier layer
The allow retune option was set for both the BCCH an
an associated cost of 0 for each
Separations and costs for equipment and nei
default settings provided in the cost matrix
was considered; handover coun
allocations
On the Planning Features page, it was chosen to minimise the interference by
only. This was to enable the tool to pay additional attention to high traffic
urban areas were given more importance than rural areas. ILSA2 was not
using group planning.
Planning
ILSA2 was allowed to run for approximately 1000 iterations (approximately 10 m
for this configuration), until the cost of the plan had become approximately stab
The planning statistics available when ILSA2 was stopped were as follows:
Page 60 P-TN-010-001-002

re 33 - Plan Textual Statistics Figu

Figure 34 - Plan Graphical Statistics
It is interesting to note from the graph that at some stages during planning, decreases in
the average interference corresponded to increases in th
phenomenon is discussed in FAQ 38).
e worst interference (this
The graph in particular demonstrates how quickly the separation constraints are solved,
illustrated by the steep initial improvement in the cost. Indeed, within the first handful
of iterations, there has been a reduction in cost by approximately 90%.
After examining the allocations in the assignments dialog, the results were deemed
acceptable, and the plan applied to the database.
A statistical analysis of the frequency plan was then performed, with the results
presented in the following section.
P-TN-010-001-002 Page 61

A.3.3 Retune Results
In summary:
1.49% of the area covered has a mean C/I of less than 12dB due to the worst
individual interferer on the worst carrier.

Figure 35 - Worst Interferer Array after ILSA2 Planning
Page 62 P-TN-010-001-002

0.19% of the area covered has a mean C/I of less than 12dB on an average
ed across carriers.
connection, averag

Figure 36 - Average Connection Array after ILSA2 Planning
A.3.4 Worst Interferer Array Statistics
P-TN-010-001-002 Page 63

CATEGORY TOTAL
INTERFERED
AREA (km)
POOR
QUALITY
AREA (km)
POOR
QUALITY
AREA (%)
Industrial area 2.97 0 0
Dense urban 0 0 0
Urban 0.31 0 0
Suburban 0.37 0 0
Dense Suburban 19.41 0. 0. 03 14
Water features 4.83 0. 2. 13 69
Wetlands 0 0 0
Mixed wood/forest 1.73 0. 01 0.87
Isolated high-rise buildings 0.01 0 0
A.3.5 Average Connection Array Statistics
EA (km): 290.52 TOTAL INTERFERED AR
Page 64 P-TN-010-001-002

CATEG
AREA (km) AREA (km)
POOR
QUALITY
AREA (%)
ORY TOTAL
INTERFERED
POOR
QUALITY
Industrial area 2.97 0 0
Dense urban 0 0 0
Urban 0.31 0 0
Suburban 0.37 0 0
ense Suburban 19.41 0 0 D
ater features 4.83 0 0 W
Wetlands 0 0 0
Mixed wood/forest 1.73 0 0.14
I lated high-rise buildings 0.01 0 0 so
A.4 Planning Summary
The following table indicates the frequency plan performance before and after running
th frequency planner. e
Description Before After Improvement
Worst Interferer Good Quality Area 63.85 % 98.51 % 34.66 %
Average Connection Good Quality Area 82.37 % 99.81 % 17.44 %
These results indicate a significant improvement especially considering only 1000
iterations of the AFP were needed.
P-TN-010-001-002 Page 65

A

Figure 1 Highlevel Flow Chart of ILSA2 Planning Process..................................................... 4
............. 12
Figure 4 -
...... 15
Figure 6 -
............. 21
Figure 12 -
................... 22
Figure 14 -
.......... 61
Figure 34 - .. 61
Figure 35 -
ppendix B - Table of Figures
-
Figure 2 - Flow of Data within the ILSA2 Planning Process (Neglecting Neighbour
Generation)................................................................................................................. 5
Figure 3 - Flow Charts Showing Possible Routes for the Generation of Neighbours..
Flow Charts Showing Traffic Raster and Required Carriers Generation................. 14
Figure 5 - Flow Chart Showing Interference Table Generation Process ............................
Default Interference Weights ................................................................................... 16
Figure 7 - Interference Weights 9dB Rejection ..................................................................... 17
Figure 8 - Interference Weights 9dB Rejection (Close Up)...................................................... 17
Figure 9 - ILSA2 Initialise Dialog ............................................................................................ 18
Figure 10 - ILSA2 Filter Import Wizard Step 1....................................................................... 20
Figure 11 - ILSA2 Filter Import Wizard Step 2..........................................................
ILSA2 Filter Import Wizard Step 3....................................................................... 22
Figure 13 - ILSA2 Filter Import Wizard Step 4....................................................
ILSA2 Plan List Dialog............................................................................................ 23
Figure 15 - ILSA2 Cost Matrix Carrier Costs.......................................................................... 25
Figure 16 - ILSA2 Cost Matrix Carrier Layer Costs ............................................................... 26
Figure 17 - ILSA2 Cost Matrix Equipment Costs.................................................................... 28
Figure 18 - ILSA2 Cost Matrix Neighbour Costs.................................................................... 29
Figure 19 - ILSA2 Cost Matrix Exception Costs..................................................................... 31
Figure 20 - ILSA2 Cost Matrix Filter Priorities....................................................................... 32
Figure 21 - ILSA2 Cost Matrix Handover Counts and Intermodulation Interference ............. 33
Figure 22 - ILSA2 Cost Matrix Separation Costs .................................................................... 34
Figure 23 - ILSA2 General Options............................................................................................ 36
Figure 24 - ILSA2 Planning Features Options............................................................................ 37
Figure 25 - Main ILSA2 Frequency Planning dialog.................................................................. 42
Figure 26 - Main ILSA2 Freuqnecy Planning dialog during planning ....................................... 43
Figure 27 - ILSA2 Cost/Interference Run Time Graph .............................................................. 45
Figure 28 - ILSA2 Carrier Assignments dialog .......................................................................... 46
Figure 29 - Best Server Coverage of Initial Configuration......................................................... 54
Figure 30 - Worst Inteferer Array of Initial Configuration......................................................... 55
Figure 31 - Average Connection Array of Initial Configuration ................................................ 56
Figure 32 - Best Server Coverage after Addition/Sectorisations ................................................ 59
Figure 33 - Plan Textual Statistics ....................................................................................
Plan Graphical Statistics.........................................................................................
Worst Interferer Array after ILSA2 Planning .......................................................... 62
Figure 36 - Average Connection Array after ILSA2 Planning ................................................... 63

P-TN-010-001-002 Page 67

Appendix C - Table of FAQs

FAQ 1 - W ................................................................ 7
2 - Ho wrong model has been added to a site?...................................... 8
W
model? .................................................................................................... 8
4 - W
..... 8
5 - W predictions should be used with ILSA2?......................... 9
- Ho er array for the ILSA2 planning process?................... 9
- W fect the predictions from a site?......................... 9
8 - W site database affect the frequency allocation strategy?............ 11
Ho e C/I and the percentage traffic/area
............................................................ 16
0 - H rd generate the adjacent channel
......................................................................... 16
1 - W rence Weights table have? ............................................... 16
12 - W t use interference? ....................................................................... 19
3 - W ... 21
4 - W ... 23
5 - W /ignore options?............................................ 24
6 - H ........................................................... 25
FAQ 17 - How should Fixed Carrier Costs be used?................................................................... 26
FAQ 18 - Why cant I assign individual carrier costs to all possible carriers?............................ 26
FAQ 19 - When to use weightings?............................................................................................. 27
FAQ 20 - How should the retune option be used?....................................................................... 27
FAQ 21 - How would you re-plan in a localised area?................................................................ 27
FAQ 22 - How is the cost calculated when separation constraints are broken? .......................... 29
FAQ 23 - What is the cost if more than one constraint applies to a separation? ......................... 30
FAQ 24 - What are the separation constraints between exceptions? ........................................... 31
FAQ 25 - Why edit Separations? ................................................................................................. 35
FAQ 26 - How were the default costs in the cost matrix set?...................................................... 35
FAQ 27 - Should I modify the default costs for different circumstances?................................... 35
FAQ 28 - When should Frequency Hopping Diversity Gain be used?........................................ 39
FAQ 29 - How is the frequency hopping diversity gain calculated and considered with
ILSA2? What is the difference in gain between base-band, synthesised and site
hopping?................................................................................................................... 39
FAQ 30 - When would you choose to aggregate the carriers required under site hopping? ....... 40
FAQ 31 - When should Antenna Hopping Gain be used?........................................................... 40
FAQ 32 - How is the antenna hopping gain calculated and considered with ILSA2? Is the
technique linked with frequency hopping gain?....................................................... 40
FAQ 33 - When should DTX load factors be used? .................................................................... 41
FAQ 34 - When should Group Planning be used?....................................................................... 41
FAQ 35 - When should you use traffic to plan with, when area and when a combination of
the two? .................................................................................................................... 41
FAQ 36 - When should you create a new plan and when should you use the current plan
from the database?.................................................................................................... 42
FAQ 37 - Why would ILSA2 stop of its own accord?................................................................. 44
FAQ 38 - Why does the Worst Interference sometimes increase with time? .............................. 44
FAQ 39 - How long should ILSA2 be left running?.................................................................... 44
hich propagation model should I use? .........
FAQ w can you tell if the
FAQ 3 - hat in the ILSA2 Planning process will be affected by the accuracy of the
propagation
FAQ hat action can be taken if you have no confidence in your current propagation
model? ...................................................................................................................
FAQ hat resolution and radius of
FAQ 6 w should I set up my best serv
FAQ 7 hat parameters in the site database af
FAQ hat Parameters in the
FAQ 9 - w is the mapping between the averag
affected stored? ............................................
FAQ 1 ow does the Interference Table Wiza
................... interference weights?....
Interfe FAQ 1 hat values can the
FAQ hen would you no
FAQ 1
FAQ 1
hat happens if a site is identified by multiple filters?............................................
hen to include/ignore filter/cell layer combinations?............................................
FAQ 1 hen would you use the plan/read only
FAQ 1 ow should Forbidden Carrier Costs be used?
P-TN-010-001-002 Page 69

Page 70 P-TN-010-001-002
FAQ 40 - Why have only alternate carriers been assigned even though I have a contiguous
band of carriers? ....................................................................................................... 47
FAQ 41 - What carrier allocation distribution should I expect? .................................................. 48
FAQ 42 - How do I interpret the interference values? ................................................................. 48
FAQ 43 - My plan uses frequency hopping but when I create the interference array, my
results arent as good as Id expected why? .......................................................... 48

P-TN-010-001-002 Page 71

Appendix D - Glossary of Terms

AFP Automatic/Advanced Frequency Planning
AH Antenna Hopping
BCCH Broadcast Control Channel in this context referring to the entire carrier containing
the BCCH
C/I Carrier to Interferer ratio in this case the interference is considered as either co-
channel or adjacent channel (which has been offset to co-channel equivalence)
CW Carrier/Continuous Wave
DTX Discontinuous Transmission
EiRP Effective isotropic Radiated Power
FH Frequency Hopping
FHDG Frequency Hopping Diversity Gain
GSM Global System for Mobile communications
ILSA Intelligent Local Search Algorithm
MRP Multiple Reuse Patterns
PA Power Amplifier
TA Timing Advance
TCH Traffic Channel in this context referring to carriers not containing the BCCH
TRX Transmitter / Receiver
VAF Voice Activity Factor

Ilsa2 Aircom

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Ilsa2 Aircom

Hochgeladen von

Copyright:

Verfügbare Formate

Copyright 2003 AIRCOM International Ltd

All rights reserved. No part of this work, which is protected by copyright,

Das könnte Ihnen auch gefallen