AFP Reference Guide PDF

AFP
Reference
Guide
2.5.0
AT250_ARG_E2
AFP Reference Guide
Contact Information
Forsk (Head Office) 7 rue des Briquetiers www.forsk.com Web

31700 Blagnac L forsk@forsk.com General information
France sales@forsk.com Sales and pricing information
{ support@forsk.com Technical support
« +33 (0) 562 74 72 10 General
+33 (0) 562 74 72 25 Technical support
¬ +33 (0) 562 74 72 11 Fax
Forsk (USA Office) 200 South Wacker Drive L sales_us@forsk.com Sales and pricing information
Suite 3100 { support_us@forsk.com Technical support
Chicago, IL 60606 « +1 312 674 4846 General
USA +1 888 GoAtoll (+1 888 462 8655) Technical support
¬ +1 312 674 4847 Fax
Forsk (China Office) Suite 302, 3/F, West Tower, www.forsk.com.cn Web
Jiadu Commercial Building, L enquiries@forsk.com.cn Information and enquiries
No.66 Jianzhong Road, « +86 20 8553 8938 Telephone
Tianhe Hi-Tech Industrial Zone, ¬ +86 20 8553 8285 Fax (Guangzhou)
Guangzhou, 510665, +86 10 6513 4559 Fax (Beijing)
People’s Republic of China
Atoll 2.5.0 AFP Reference Guide Release AT250_ARG_E2
© Copyright 1997 - 2006 by Forsk

The software described in this document is provided under a license agreement. The software may only be used/copied
under the terms and conditions of the license agreement. No part of this document may be copied, reproduced or distrib-
uted in any form without prior authorisation from Forsk.
The product or brand names mentioned in this document are trademarks or registered trademarks of their respective reg-
istering parties.
About AFP Reference Guide

This document is aimed at frequency planning engineers using Atoll AFP module to perform automatic frequency planning
of their networks. This document introduces the AFP with a high level description of the frequency planning process in Atoll.
Then descending lower to the practical level, this document describes in detail every aspect of frequency planning in Atoll.
Main topics covered in this document include AFP pre-requisites, AFP usage, AFP minimization target and some possible
problems that may come up during training.
This document begins with a basic user guide containing a short operational introduction to the AFP process in Atoll. Then
it goes on to summarize most aspects of the practical planning process and provides detailed discussions on certain topics.
It also explains the means to evaluate a frequency plan. Furthermore, a chapter is dedicated to advanced topics and trou-
bleshooting in the end.
The appendices deeply detail the technical aspects of the cost function, the BSIC allocation algorithm, the IM calculation,
and the dimensioning process.
© Forsk 2006 AT250_ARG_E2 a

AFP Reference Guide
b AT250_ARG_E2 © Forsk 2006

Table of Contents
Table of Contents
1 Overview ........................................................................................... 3
1.1 Introduction to AFP ..........................................................................................3
1.1.1 Frequency Assignment as a Cost Minimization Problem....................................... 3
1.1.2 Abbreviations ......................................................................................................... 3
1.2 Architecture......................................................................................................5
2 Basic AFP Tutorial ............................................................................ 9

2.1 AFP Process in Atoll ........................................................................................9
2.2 Loading and Validating the Network ..............................................................10
2.3 Definition of the AFP Scope...........................................................................12
2.4 Preparing to Launch the AFP.........................................................................13
2.5 Launching the AFP and Monitoring its Progress............................................14
2.6 AFP Outputs ..................................................................................................16
2.6.1 Partial Commit Functionality ................................................................................ 18
2.6.2 Automatic Constraint Violation Resolution........................................................... 19
2.7 Visualising and Manipulating Results ............................................................20
2.8 Manual Frequency Allocation ........................................................................20
2.8.1 Manual Frequency Allocation for NH Case.......................................................... 20
2.8.2 Manual Frequency Allocation for SFH Case........................................................ 21
3 Frequency Planning Prerequisites .................................................. 25

3.1 Atoll Data Model ............................................................................................25
3.1.1 Reliability and Propagation .................................................................................. 25
3.1.2 HCS Layers ......................................................................................................... 25
3.1.3 Subcells ............................................................................................................... 26
3.1.3.1 Key Roles of Subcells ..................................................................................................26
3.1.3.2 Concentric Cells and Dual-band Cells .........................................................................26
3.1.3.3 Minimum C/I .................................................................................................................26
3.1.3.3.1 Quality Targets...................................................................................................................... 26
3.1.3.4 Traffic Loads ................................................................................................................26
3.1.3.5 Local Domain Restrictions ...........................................................................................27
3.1.4 TRXs.................................................................................................................... 27
3.1.5 Freezing Flags ..................................................................................................... 27
3.1.6 AFP Weights ........................................................................................................ 27
3.1.7 Spectrum Administration...................................................................................... 27
3.1.8 Redundancy and Subcell Audit............................................................................ 27
3.1.9 Neighbour Importance ......................................................................................... 28
3.1.10 SeparationConstraints Table ............................................................................... 28
3.1.11 SeparationRules Table and Rule Priority............................................................. 28
3.1.12 Adjacency Suppression ....................................................................................... 28
3.2 AFP Performance Indicators..........................................................................28
3.2.1 AFP TRX Rank .................................................................................................... 28
3.2.1.1 TRX Rank Usage .........................................................................................................29
3.2.2 Total Cost and Separation Violation Cost Component ........................................ 29
4 Frequency Plan Optimisation .......................................................... 33

4.1 Step 1 (Optional): Traffic Model Usage .........................................................33
4.1.1 Creating a Traffic Map Based only on Clutter Weighting ..................................... 33
4.1.2 Performing a Traffic Capture................................................................................ 33
4.1.3 Creating IMs Based on Traffic ............................................................................. 34
© Forsk 2006 AT250_ARG_E2 i

AFP Reference Guide
4.2 Step 2 (Optional): Neighbour Relations and Relative Weighting .................. 34

4.2.1 Automatic Neighbour Allocation .......................................................................... 34
4.2.2 Importing Neighbour Importance ......................................................................... 35
4.2.3 Extending Existing Neighbour Relations ............................................................. 35
4.2.4 Importing Partial Sources of Neighbour Importance............................................ 36
4.3 Step 3 (Optional): Using Dimensioning......................................................... 37
4.3.1 Optimal Dimensioning of an Existing Network..................................................... 37
4.4 Step 4: Optimal Usage of the Atoll AFP ........................................................ 38
4.4.1 Introduction to the AFP Cost Function................................................................. 38
4.4.1.1 Combination of Separation Violation and Interference Probabilities ........................... 38
4.4.1.2 Counting TRXs (Nodes) Instead of Relations (Edges) ................................................ 38
4.4.1.3 Each TRX Cost............................................................................................................ 39
4.4.1.4 Separation Violation Cost............................................................................................ 39
4.4.1.5 Interference Cost......................................................................................................... 40
4.4.1.6 Probabilistic Cost combination .................................................................................... 40
4.4.1.7 Missing TRX Cost........................................................................................................ 40
4.4.1.8 Corrupted TRX Cost.................................................................................................... 41
4.4.1.9 Out-of-domain Frequency Assignment Cost ............................................................... 41
4.4.1.10 Quality Target.............................................................................................................. 41
4.4.1.11 Modifiable and Non-modifiable Costs.......................................................................... 41
4.4.2 Most Important Cost Function Parameters and Tuning ....................................... 42
4.4.2.1 Interference Weight vs. Separation Weight................................................................. 42
4.4.2.2 Cost of Changing a TRX ............................................................................................. 42
4.4.2.3 Quality Target and C/I Weighting ................................................................................ 43
4.4.2.3.1 Quality Target ........................................................................................................................43
4.4.2.3.2 C/I Weighting .........................................................................................................................43
4.4.2.4 Separation Weights Settings ....................................................................................... 43
5 Means to Evaluate Frequency Plans ...............................................47

5.1 Estimating Frequency Plan Quality............................................................... 47
5.1.1 Using Interference Studies .................................................................................. 47
5.1.1.1 Various Interference Studies ....................................................................................... 47
5.1.1.1.1 TRX Based Interference Study ..............................................................................................47
5.1.1.1.2 Worst Case Interference Study..............................................................................................48
5.1.1.2 Visualising TRX Ranks with a TRX Based Interference Study.................................... 48
5.1.1.3 Visualising C/I Distributions with a TRX Based Interference Study............................. 48
5.1.2 Using Audit .......................................................................................................... 49
5.1.2.1 Global Separation Fitness Expression ........................................................................ 49
5.1.2.1.1 Forsk Independent Separation Fitness Expression (FISFE)..................................................49
5.1.2.1.2 Main Separation Violation Item Summary .............................................................................50
5.2 Using Point Analysis ..................................................................................... 51
5.2.1 Example 1: Combination of Interference Effects ................................................. 51
5.2.2 Example 2: Counting Strong Interference Only Once ......................................... 51
5.3 Uniform Frequency Usage Distribution ......................................................... 52
5.3.1 When Uniform Distribution and Quality do not Coincide ..................................... 52
5.3.1.1 Domain Range Effect and Adjacent Constraints ......................................................... 52
6 Advanced Topics and Troubleshooting ...........................................55

6.1 Various AFP Related Features ..................................................................... 55
6.1.1 SFH (HSN, MAL, MAIO)...................................................................................... 55
6.1.2 Definition of Atom ................................................................................................ 55
6.1.3 Synchronous Networks........................................................................................ 55
6.1.4 Optimising Hopping Gains................................................................................... 55
6.1.5 Fractional Load.................................................................................................... 55
6.1.6 Domain Use Ratio ............................................................................................... 56
6.1.7 User Defined MAL Length ................................................................................... 56
6.1.8 HSN Allocation .................................................................................................... 56
6.1.9 MAIO Allocation................................................................................................... 56
6.1.9.1 Staggered MAIO Allocation ......................................................................................... 56
ii AT250_ARG_E2 © Forsk 2006

Table of Contents
6.1.10 BSIC Allocation.................................................................................................... 57

6.1.11 Robustness of Atoll AFP ...................................................................................... 57
6.1.11.1 Value Ranges and Limitations at Validation.................................................................57
6.2 Managing Consistency in Atoll and the AFP..................................................58
6.2.1 Service Zone of a Subcell .................................................................................... 58
6.2.1.1 Specifying Correct Interference Study Coverage Criteria ............................................58
6.2.1.2 Selecting “All servers” or “Best Server” Service Zone..................................................59
6.3 Event Viewer..................................................................................................59
6.4 Interference Study Quality Criteria.................................................................59
6.5 Calculation Zone Border Effect......................................................................59
6.6 Frequency Planning Techniques ...................................................................60
6.6.1 Basics .................................................................................................................. 60
6.6.2 Post-processing of Hot Spots .............................................................................. 60
6.6.3 Learning the Network and Solving for Hot Spots ................................................. 60
7 Appendices ..................................................................................... 63
7.1 Appendix 1: Description of the AFP Cost Function........................................63
7.1.1 Notations.............................................................................................................. 63
7.1.2 Cost Function....................................................................................................... 64
7.1.3 Cost Components ................................................................................................ 65
7.1.3.1 Separation Violation Cost Component .........................................................................65
7.1.3.2 Interference Cost Component ......................................................................................67
7.1.4 I_DIV, F_DIV and Other Advanced Cost Parameters .......................................... 68
7.2 Appendix 2: Interferences..............................................................................70
7.2.1 Using Interferences.............................................................................................. 70
7.2.2 Cumulative Density Function of C/I Levels .......................................................... 70
7.2.3 Precise Definition................................................................................................. 70
7.2.4 Precise Interference Distributions Strategy ......................................................... 71
7.2.4.1 Direct Availability of Precise Interference Distributions to the AFP ..............................71
7.2.4.2 Efficient Calculation and Storage of Interference Distributions ....................................71
7.2.4.3 Robustness of the IM ...................................................................................................71
7.2.5 Traffic Load and Interference Information Discrimination .................................... 71
7.3 Appendix 3: BSIC Allocation..........................................................................73
7.3.1 Definitions ............................................................................................................ 73
7.3.2 Hard Criterion ...................................................................................................... 73
7.3.3 Soft Criterion........................................................................................................ 73
7.3.4 Behaviour............................................................................................................. 73
7.4 Appendix 4: Traffic Capture and Dimensioning .............................................74
7.4.1 Introduction .......................................................................................................... 74
7.4.2 Traffic Map Generation ........................................................................................ 74
7.4.3 Traffic Capture Process ....................................................................................... 74
7.4.3.1 Inputs ...........................................................................................................................74
7.4.3.2 The Engine...................................................................................................................75
7.4.3.2.1 Traffic Distribution ................................................................................................................. 75
7.4.3.2.2 Average Timeslot Capacity ................................................................................................... 76
7.4.3.2.3 Integration ............................................................................................................................. 77
7.4.3.3 Outputs.........................................................................................................................77
7.4.4 Network Dimensioning Process ........................................................................... 78
7.4.4.1 Inputs ...........................................................................................................................78
7.4.4.2 Dimensioning ...............................................................................................................78
7.4.4.3 Outputs.........................................................................................................................78
© Forsk 2006 AT250_ARG_E2 iii

AFP Reference Guide
iv AT250_ARG_E2 © Forsk 2006

List of Figures
List of Figures
Figure 2.1: AFP Process in Atoll .................................................................................................................................... 9

Figure 2.2: Interaction of the AFP with Other Elements................................................................................................. 9
Figure 2.3: AFP Outputs .............................................................................................................................................. 10
Figure 2.4: AFP Launch Wizard - AFP Session Tab .................................................................................................... 10
Figure 2.5: AFP Launch Wizard - Separations Tab ..................................................................................................... 10
Figure 2.6: AFP Launch Wizard - Global Parameters Tab........................................................................................... 11
Figure 2.7: Event Viewer - Sample Messages ............................................................................................................. 11
Figure 2.8: Message 1 ................................................................................................................................................. 12
Figure 2.9: Message 2 ................................................................................................................................................. 12
Figure 2.10: AFP Launch Dialog - Example 1................................................................................................................ 13
Figure 2.11: AFP Launch Dialog - Example 2................................................................................................................ 13
Figure 2.12: AFP Progress Window............................................................................................................................... 14
Figure 2.13: Event Viewer Message - Solution Kept...................................................................................................... 15
Figure 2.14: AFP Progress Window............................................................................................................................... 15
Figure 2.15: Cost Distributions on Frequencies ............................................................................................................. 16
Figure 2.16: Frequency Usage Distributions.................................................................................................................. 16
Figure 2.17: AFP Results Window ................................................................................................................................. 17
Figure 2.18: Separation Constraint Violation Details Message...................................................................................... 17
Figure 2.19: AFP Results Window - Partial Commit Feature ......................................................................................... 18
Figure 2.20: AFP Results Window - Partial Commit Feature ......................................................................................... 19
Figure 2.21: Constraint Violation Resolution Tool.......................................................................................................... 19
Figure 2.22: Scanning for Frequencies .......................................................................................................................... 20
Figure 2.23: Scanning for Frequencies .......................................................................................................................... 21
Figure 3.1: Model Standard Deviation - Default Value................................................................................................. 25
Figure 4.1: Automatic Neighbour Allocation................................................................................................................. 35
Figure 4.2: Automatic Neighbour Allocation Results.................................................................................................... 36
Figure 4.3: Neighbours Table ...................................................................................................................................... 36
Figure 4.4: Dimensioning Process ............................................................................................................................... 37
Figure 4.5: Atoll AFP Module Properties - Separation Weights Tab ............................................................................ 39
Figure 4.6: Atoll AFP Module Properties - Cost Tab .................................................................................................... 42
Figure 4.7: C/I Weighting ............................................................................................................................................. 43
Figure 4.8: Atoll AFP Module Properties - Separation Weights Tab ............................................................................ 44
Figure 5.1: Interference Study Report.......................................................................................................................... 47
Figure 5.2: TRX Based Interference Studies ............................................................................................................... 48
Figure 5.3: TRX Based Interference Study - C/I Distributions...................................................................................... 49
Figure 5.4: Event Viewer Messages ............................................................................................................................ 50
Figure 5.5: Event Viewer Message 1 ........................................................................................................................... 50
Figure 5.6: Event Viewer Message 2 ........................................................................................................................... 50
Figure 5.7: Combinatin of Interference Effects............................................................................................................. 51
Figure 5.8: Counting Strong Interference Only Once................................................................................................... 51
Figure 6.1: Hopping Sequence Numbers..................................................................................................................... 56
Figure 7.1: Atoll AFP Module Properties - Advanced Tab ........................................................................................... 69
Figure 7.2: The cumulative density of C/I levels between [TX1, BCCH] and [TX2, BCCH] ......................................... 70
Figure 7.3: Traffic Maps Overlay.................................................................................................................................. 75
Figure 7.4: Traffiic Overflow......................................................................................................................................... 76
Figure 7.5: Intra-Layer Distribution .............................................................................................................................. 76
Figure 7.6: Traffic Distribution in Atoll .......................................................................................................................... 77
Figure 7.7: Network Dimensioning Process................................................................................................................. 78
© Forsk 2006 AT250_ARG_E2 v

AFP Reference Guide
vi AT250_ARG_E2 © Forsk 2006

Chapter 1
Overview
AFP Reference Guide
2 AT250_ARG_E2 © Forsk 2006

Chapter 1: Overview
1 Overview
This document describes every aspect of frequency planning in Atoll, from high level description of the frequency planning
process to the practical level detail. Main topics covered in this document include AFP prerequisites, AFP usage, AFP min-
imisation target and some possible problems that may come up during training.
This document begins with a basic user guide, a short operational introduction to the AFP process in Atoll, and goes on to
summarize most aspects of the practical planning process with detailed discussions on certain topics. It also explains the
means to evaluate a frequency plan available in Atoll. A chapter is dedicated to advanced topics and troubleshooting in
the end.
Four appendices contain in-depth information on technical aspects of the cost function, the BSIC allocation algorithm, the
IM calculation and the dimensioning process respectively. All in all, this document is almost self sufficient with respect to
the use of Atoll AFP.
1.1 Introduction to AFP

The main role of an Automatic Frequency Planner (AFP) is to assign frequencies (channels) to the network such that the
overall network quality is optimised. With the evolution of GSM over the years to integrate many improvements, additional
requirements have emerged in the process of radio network planning. The implementation of baseband and synthesised
frequency hopping, discontinous transmission and network synchronisation, for example, has led to higher sophistication
in the process of frequency planning. These enhancements require that an AFP also be intelligent and advanced enough
to help the frequency planner through out his tedious task.
The Atoll AFP considers a large number of constraints and directives; for example, ARFCN separation requirements be-
tween transmitters, interference relations, HSN assignment methods, frequency domain constraints, a certain fractional
load to maintain etc. Hence, the AFP depends on a variety of input data, such as the interference matrix, neighbourhood
relations, traffic information and so on.
This document not only explains how to use the Atoll AFP, by describing the AFP GUI, but also includes detailed descrip-
tions of the various constraints, directives, and data sources. The primary target of this document is to explain the technical
background of the AFP.
1.1.1 Frequency Assignment as a Cost Minimization Problem

From the technical point of view, the Frequency Assignment Problem (FAP) is considered as a minimization problem. This
means that the AFP will generate a set of Frequency Plans (FPs), and propose the one that has the lowest cost as the
“Best Solution”. Therefore, the AFP cost is the equivalent of AFP quality estimation: the lower the cost, the better should
be the quality from the AFP point of view.
The approach of cost minimization is not only the most common approach to the FAP but probably also the easiest to un-
derstand and control. It provides the user with means of guiding the AFP in its task. For example, by setting the cost of
interference violation low, the AFP will concentrate its efforts on resolving the separation violations.
There are AFP tools in which certain types of objectives are presented as “hard constraints”. If a hard constraint is not sat-
isfied, the AFP does not offer any solution or offers a partial solution (with fewer frequencies and satisfying hard con-
straints). The philosophy of hard constraints vs. soft constraints has nothing to do with the quality of an AFP engine, it is
merely a behaviour convention. In Atoll, we prefer always offering a solution to offering partial assignments or violating
domain limitations. This ensures that you will always get a result when you launch the Atoll AFP. This result will very well
depict the difficulty of the FAP. The cost of this solution will clearly indicate if unacceptable violations have occurred or if
this plan has improved the current frequency plan.
The cost function definition permits you to place as much emphasis as required on certain elements of the cost function.
This manipulation will make the AFP behave as if it were guided by hard constraints, from the optimisation viewpoint, while
retaining its property of being a quality monitor and a hardness-of-assignment monitor both.
1.1.2 Abbreviations
Some abbreviations and terminologies used in the document are listed below:
GSM Global System for Mobile Communications (Groupe Speciale Mobile)

GPRS General Packet Radio Service
EDGE Enhanced Data rates for GSM (or Global) Evolution
EGPRS EDGE based GPRS
TSL Timeslot
TX Transmitter or sector
© Forsk 2006 AT250_ARG_E2 3

AFP Reference Guide
TRX Transceiver
Broadcast Control CHannel. A term usually employed in Atoll to refer to the TRX carrying this
BCCH
channel.
Traffic CHannel. A term usually employed in Atoll to refer to a TRX carrying traffic with usually the
TCH
same coverage area as the BCCH.
Inner Traffic CHannel. A term usually employed in Atoll to refer to a TRX carrying traffic but usually
TCH_INNER
having a coverage area less than that of a TCH.
HR/FR Half Rate/Full Rate
CS Circuit-switched
PS Packet-switched
HCS Hierarchical Cell Structure
Subcell An entity defined by the pair [TX, TRX Type]
HO Handover
Kbps Kilobits per second
GoS Grade of Service
QoS Quality of Service
KPI Key Performance Indicators
TL Traffic Load
P Probability
C Carrier power (Signal strength)
C/I Carrier to Interference ratio
AFP Automatic Frequency Planner/Planning
DTX Discontinuous transmission
GUI Graphical User Interface
FP Frequency Plan
BBH Baseband Hopping
SFH Synthesized Hopping
NH No Hopping
Mobile Allocation List. In the context of SFH, MAL is the group of frequencies used by the
MAL
frequency hopping TRX.
HCS Hierarchical Cell Structure
AMR Adaptive Multi-Rate
HR / FR Half-rate / Full-rate
CC Concentric Cells
Transmitter Atoll synonym for cell or sector in conventional GSM jargon
FER Frame Erasure Rate
FH Frequency Hopping
DL_PC Down Link Power Control
RRM Radio Resource Management
Synchronised
Transmitters that are synchronised and can, therefore, share the same HSN.
transmitters
A project can be saved in a filename.ATL file or as a database. In both cases, most of the project’s
Data Model
information is saved in database tables. We refer to these tables as the data model.
IM, IMco, IMadj Interference Matrix, Co-channel / Adjacent-channel Interference Matrix
HO Handover or Handoff
FN Frame Number
CDF Cumulative Density Function
TSC Training Sequence Code
FAP Frequency Assignment Problem
# Number of

Chapter 1: Overview
1.2 Architecture
The Atoll Automatic Frequency Planning (AFP) module is an optional module that enables you to generate frequency plans
for GSM and TDMA networks automatically. The Atoll AFP module can allocate the following parameters:
• Frequencies
• Frequency hopping groups (MAL)
• HSN, MAIO
• BSIC (TSC planning)
• TRX rank (can be used to prioritise the use of good frequencies)
• Performance Indicators at Site/Cell/TRX levels
Atoll works with an open AFP interface. Any AFP built using this interface can be able to allocate the following additional
parameters. Future versions of the Atoll AFP module are planned to assign the following parameters as well:
• Group ID (better administration of the frequency resources)

• TN offsets
• FN offsets
Atoll AFP implements simulated annealing, taboo search, graph heuristics and machine learning. It manages its time re-
sources to match the users time directive. If allowed enough time, the AFP will employ a major part of this time in “learning”
the network. During the learning phase, the AFP tunes up its internal parameters. Towards the end of the user-defined
time, the AFP switches to a randomised combinatorial search phase.
Remark:
The role of this learning phase is extremely important in order to get good results. You should often let the AFP run over
a night or a weekend by specifying corresponding target time. If you never run the AFP specifying a long time period, it
will never be able to calibrate itself and will always perform from 10 to 70 solutions and stop.
Network learning is performed by executing numerous fast and deterministic instances of the AFP. The one that obtains
the best performance is memorized in the document and is, therefore, the most suitable for the specific network. The next
time an AFP is executed it will start where the learning process ended and it will use the parameter profile of the best so-
lution stored in the document.
Note: The following scenario will demonstrate the usefulness of AFP learning capabilities:
- Create a GSM GPRS EGPRS project and import its network elements and maps.
- Create a copy of “Atoll AFP module” and name it “Atoll AFP module 2”.
- If the network has X transmitters, run “Atoll AFP module 2” for X / 10 minutes to obtain a cost Y. (Short exe-
cution)
- Now run “Atoll AFP module 2” for a longer time (for example, X / 5 hours).
- Another cost, Z, is obtained, which is better than Y (i.e. Z < Y). The network dependent information is mem-
orized in the “Atoll AFP module 2” instance whereas the “Atoll AFP module” instance remains unchanged.
- Now if you perform a short execution with “Atoll AFP module 2”, you can get the improved result (Z) right
away. While a short execution of the “Atoll AFP module” instance will give the initial cost (Y).
- If X / 5 hours is too long, you can perform the “learning” on a small (representative) part of the network.
The Atoll AFP is built based on a specified COM interface designed as a part of Atoll’s open platform strategy. The interface
is designed in such a way that puts aside elements that are not inherent to the AFP process. At the same time, through the
modelling capabilities of the planning tool, the AFP can support complete list of features expected from an AFP.

AFP Reference Guide

Chapter 2
Basic AFP Tutorial
AFP Reference Guide

Chapter 2: Basic AFP Tutorial
2 Basic AFP Tutorial

Atoll AFP framework complies with its global open architecture Strategy. Any AFP module, Atoll AFP or 3rd party AFP, can
be interfaced and made available to RF planning engineers through Atoll. Furthermore, different AFP modules are activat-
ed, accept their main inputs and generate their main outputs in the same manner. This section teaches the basics of acti-
vating an AFP in Atoll.
2.1 AFP Process in Atoll

The AFP process is a cycle in which the AFP is only one of its many steps:
Figure 2.1: AFP Process in Atoll
The figure below gives a better view of interaction of the AFP with other elements in Atoll:
Figure 2.2: Interaction of the AFP with Other Elements
The following figure depicts the outputs of the AFP:

AFP Reference Guide
Figure 2.3: AFP Outputs
2.2 Loading and Validating the Network

To launch the AFP, choose the Automatic Allocation… command from the Frequency Plan menu of the Transmitters folder
context menu. This initiates a series of dialogs called the AFP wizard.
Figure 2.4: AFP Launch Wizard - AFP Session Tab
Figure 2.5: AFP Launch Wizard - Separations Tab
10 AT250_ARG_E2 © Forsk 2006

Here you can,
• Specify the AFP module you would like to use and set its parameters,
• Choose the network parameters and AFP performance indicators you want the AFP to allocate,
• Specify the network’s default separation requirements,
• Consult the network’s “Exceptional Pairs” and define other separation constraints for them, and
• Indicate whether interferences are to be included in calculations or not.
For explanations of AFP performance indicators, refer to section 3.2.
The last of the wizard dialogs contains some global parameters that often vary from one AFP instance to another:
Figure 2.6: AFP Launch Wizard - Global Parameters Tab
The most important option here is the one proposing the two sources of the traffic load information. Traffic load can be read
directly from the subcells table, which could have been filled manually, by the dimensioning process or by a KPI calculation.
You can also specify that the traffic load should be read from the default traffic capture (explained later).
Notes:
1. In case the traffic load is taken from the Subcells table, committed after a KPI calculation, you must be
aware of a certain difference: in the KPI calculation, Atoll divides the captured traffic by the timeslot capac-
ity of the existing number of TRXs, while the AFP requires it to be divided by the timeslot capacity of the
required number of TRXs.
2. The traffic load is artificially increased to 0.1, if it is too low (less than 0.1), in order to maintain the AFP
robust against partial data conditions. Hence, the AFP cannot completely ignore the existence of a fre-
quency in a TRX.
Clicking Validate will start the data verification and storage optimisation aimed at providing fast access to data needed by
the AFP. This stage may generate many warnings for real-life networks (for example, values out of range). These are dis-
played in the Event viewer. It is recommended to revise the network data according to these messages and continue once
all the data are clean and coherent. If a certain message is not clear or self evident, you can always contact Forsk’s tech-
nical support. The figure below depicts the Event viewer with some sample messages:
Figure 2.7: Event Viewer - Sample Messages
© Forsk 2006 AT250_ARG_E2 11

AFP Reference Guide
Let us look at two of these messages:
Figure 2.8: Message 1
This means that the value entered in the AFP weight column of the Transmitters table for the transmitter 19941 is invalid.
In the database, this field’s name is “COST_FACTOR”. A value of –2 for the cost factor implies that the AFP should gener-
ate the worst assignment possible for the transmitter. It would be interesting to investigate the origin of this erroneous value
as it may avoid possible errors in the future. Atoll automatically resets this value to 1 in order to avoid such calculation
errors.
Figure 2.9: Message 2
This message informs that 3678 subcells were loaded successfully. The next section explains the significance of the term
‘effectively selected’ and why 3678 subcells were loaded and only 6 selected for the AFP process.
2.3 Definition of the AFP Scope

In the example above, the 6 subcells effectively selected for the AFP process had many potential interferers, neighbours,
neighbours of neighbours, and/or transmitters with exceptional separation constraints with them. No AFP can perform a
good allocation for these 6 subcells without “dragging in” a large part of the network. The AFP considers the part that is
“dragged in” to be “frozen”. On the other hand, there are many other ways to freeze network elements in Atoll. Some pre-
cise definitions are provided in order to avoid misconceptions.
Let us define 4 groups of transmitters (ALL, NET, SEL, RING):
• ALL = All the transmitters in the project.

• NET = Active transmitters that pass the filters on the main Transmitters folder and on the main Sites folder.
• SEL = Transmitters belonging to the (sub)folder for which the AFP was launched and that are in the intersection
of the calculation zone and focus zone.
• RING = Transmitters belonging to NET, not belonging to SEL and having some relationship with the transmitters
in SEL:
- If interferences are to be taken into account (see the dialog above), all transmitters whose calculation radii in-
tersect the calculation radius of any transmitter in SEL will be included in RING. For large calculation radii (20
km for example), a single site can have a very large RING loaded.
- Neighbours are always included in RING.
- If one transmitter of an Exceptional Pair is included in SEL and the other is not, then the other will be included
in RING as well.
- If BSIC assignment is required, then all the second order neighbours (neighbours of a neighbour) will be in-
cluded in RING as well.
Both the RING and the SEL parts of the network are loaded. It is important to know which subcells are loaded as the cost
is calculated for all loaded subcells. The RING part is frozen for all assignments (BSIC, HSN, MAL, MAIO and channels).
The SEL part may be assigned some parameters but only the ones specified in the dialog above. For example, if the user
did not select BSIC, it will not be assigned.
In addition to the generic freezing options above, there are some finer freezing options available in the data structure:
1. Individual transmitters can be frozen for channel (and MAL), HSN and/or BSIC assignment.
2. Individual TRX’s can be frozen for channel (and MAL) assignment.
In an Atoll project, it is strongly recommended to avoid TRX’s without channels. For this reason, never create transmitters
automatically if there are no channels to assign to them. Therefore, if the user does not ask for MAL/MAIO assignment, all
SFH subcells are considered frozen and no TRX will be created for them. The same occurs when only a MAL/MAIO as-
signment is requested. In this case, all NH and BBH subcells will be considered frozen and no TRXs will be created.
Note: See Developer Reference Guide for details on the TO_ASSIGN and FROZEN assignment states available
in the AFP API.
12 AT250_ARG_E2 © Forsk 2006

2.4 Preparing to Launch the AFP

Once the network is loaded and all warnings resolved, the AFP launch dialog will appear. This dialog contains a short sum-
mary of the state of the loaded network, SEL + RING. In addition, this dialog contains an optional section from which IMs
can be manipulated. In Atoll, IMs are normally manipulated outside the AFP and are compressed and saved in the docu-
ment. It is no longer necessary to load IMs or look for them each time AFP is launched. For this reason, a small report
indicates the current state of the IMs.
Example 1: When partial IM info exists, we can see that 9 transmitters out of 12 do not have any
interferers.
Figure 2.10: AFP Launch Dialog - Example 1
Example 2: When complete IM info exists, observe that the IM topology is more or less normal.
Figure 2.11: AFP Launch Dialog - Example 2
This dialog also lets you define a generator initilialisation number. This number serves as a directive of randomness for
the AFP process being launched. If the generator initialisation is set to 0, the AFP will be fully random. An integer other
than 0 will define a given deterministic sequence for the AFP process. Each generator initialisation number (other than 0)
corresponds to a deterministic sequence. Therefore, each AFP instance launched with the same generator initialisation
number will yeild the same results.
However, you must keep in mind that all the AFP computations are deterministic in the start, independent of the generator
initialisation. The AFP must be allowed to compute during the target time to observe the effects of randomness.
© Forsk 2006 AT250_ARG_E2 13

AFP Reference Guide
Notes:
1. Since the method chosen by the AFP depends on the target time provided, you might not get the same
results using the same generator initialisation number if the defined target times are different. Therefore, to
actually get the exact same results from the AFP process, you must define a certain target time and a cer-
tain generator initialisation.
2. The AFP may be perfectly deterministic during a portion of the target computation time (5 - 15%). During
this period, the randomness seed will have no effect on the solutions. If you want to see the effect of ran-
domness, let the AFP calculate until the end of the target time, or set a shorter target time.
2.5 Launching the AFP and Monitoring its Progress

Provide a time quota and a generator initialisation number in the above dialog and launch the AFP by clicking Run. It is
important to set a long time quota from time to time to allow the AFP to calibrate itself. If not stopped, the AFP will usually
continue for a while before stopping by itself.
Important: If only a short time is specified, the full optimisation potential of the AFP will not be utilised.
The window below opens when the AFP is started, and displays information about the AFP process:
Figure 2.12: AFP Progress Window
The Progress section of this window in the top left displays the target time allocated to the AFP, the time elapsed and the
number of AFP solutions that have been evaluated so far.
The calculation status window in the top right gives some general information about the current solution in real time. This
display depends on the selected AFP module. This section lists the status of the current solution, the initial cost, the cost
of the current best solution, the cost of the previous solution and whether the previous solution was kept or rejected.
The Event viewer has been made accessible through the AFP progress dialog in order to help the user keep track of all
the important warnings and messages generated before and during the AFP process. This also enables you to export
these messages as an AFP log file.
If a solution is kept, a corresponding message appears in the Event viewer. Double-clicking the message in the Event view-
er will open a dialog with the full details of this message, which will look something like the following figure.
14 AT250_ARG_E2 © Forsk 2006

Figure 2.13: Event Viewer Message - Solution Kept
The Best Frequency Plan Costs section displays the current values of modifiable and total costs, and their respective sep-
aration components. This section also displays the total weighted Erlangs of the network concerned in the AFP process,
i.e. the total cost of a 100% interfered frequency plan). It gives a general idea of how good the cost of a certain frequency
plan is. The cost of any solution remains between 0 and the Network Weighted Erlangs. The cost is as better as it is closer
to 0.
Apart from this information, this section also contains a table listing the initial frequency plan and all the AFP solutions kept
so far sorted in ascending order of cost. This table can display:
• Modifiable costs
• Total costs
• Frozen costs
• Summed components
• Main components (separation violation cost component, interference component and modified TRX component)
• Additional taxes (corrupted, missing or out of domain TRXs)
For detailed description of modifiable and non-modifiable parts of the total cost, please refer to section 4.4.1.11.
After the AFP is allowed to compute solutions and try to optimise the network for a while, the AFP progress dialog would
look somewhat like this:
Figure 2.14: AFP Progress Window
Using the buttons available in the Plan comparison section in the bottom right, it is possible to visually compare the initial
frequency plan and the current best solution (with the Best Plan column in the AFP cost details table checked). Clicking
these buttons opens dialogs containing graphs corresponding to ’Cost Distribution on Frequencies’ and ’Usage Distribution
on Frequencies’.
The cost of a frequency f is given as:
© Forsk 2006 AT250_ARG_E2 15

AFP Reference Guide
Cost ( f ) = ∑ FL ( i ) × Cost ( i )
i ∈ TRXs using f
Where, FL(i) is the fractional load of frequency f in the MAL of i, and cost(i) is the AFP cost of TRX i in Erlangs.
Figure 2.15: Cost Distributions on Frequencies
Figure 2.16: Frequency Usage Distributions
You can pause or stop the AFP process any time to check the current best solution, and resume optimising the network
after you have checked it. Pausing the AFP process opens the AFP results window with the current best solution results
listed.
2.6 AFP Outputs

When calculations stop (completed or paused to view the current situation), Atoll displays the frequency plan proposed by
the AFP. All results/violations are listed in a dialog window.
This window contains a table listing all the assigned resources.These resources and related items (transmitters, subcells)
are coloured differently to indicate different reasons, such as:
• Arctic blue: frozen resource

• Red: resource modified compared to the previous allocation but with separation violation
• Green: resource modified compared to the previous allocation respecting the separation constraints
• Black: resource not modified
• Blue: resource assigned with no separation violation
• Purple: resource assigned but with separation violation
• Grey: items and resources involved in computation but not available for allocation
Positioning the cursor over a resource in the table displays the reason for its colour in a tool tip.
The results window displays all the results of the AFP session. It is possible to only display some of the results by checking/
un-checking the relevant choices in the Display options menu. You can choose to display the results related to:
• Cells (BSICs)
• Subcells (HSNs)
• TRXs (Channels/MAL, MAIO) and related separation violations
Selected AFP performance indicators (AFP TRX ranks, and total and separation costs at TRX, subcell, transmitter and site
levels) will also be available in the results window. These AFP performance indicators are also available to export. You
can choose whether to display the AFP indicators in the results as separate columns. The Show AFP Indicators command
in the Display options menu controls the display of AFP TRX ranks, and total costs and separation cost components at
TRX, subcell, transmitter, and site levels.
16 AT250_ARG_E2 © Forsk 2006

Figure 2.17: AFP Results Window
As the network had been loaded according to both the items to assign and the ones they relate to, it is possible to display
the frequency plan of either:
• Items belonging to the selected transmitters (see the definition of SEL), or

• Items belonging to the loaded transmitters (see the definition of SEL + RING). In the preceding example, there
were no transmitters in the RING set, so the option is not available.
It is also possible to display detailed information about separation constraint violations, i.e. the co-channel and adjacent
channel collision probabilities for relevant TRXs. You can choose to display these separation constraint violations through
the Display options menu.
The Separation violations column lists each each type of separation constraint violation realted to a given TRX, i.e. excep-
tional pair, co-transmitter, co-site, or neighbour. Another column titled ’With the TRX’ contains a button for each type of
separation constraint violation. This caption of this button shows the TRX with which the separation constraint violation
occurs. Clicking this button takes you to the corresponding TRX row in the table. Right-clicking a row with a separation
constraint violation opens a Separation Constraint Violations context menu, which opens a dialog mentioning the reason
of violation when clicked. For example:
Figure 2.18: Separation Constraint Violation Details Message
Use the Commit button to assign the allocated resources and AFP performance indicators. The resume button permits re-
suming the AFP optimisation from where it stopped the last time.
Note: At the bottom of the AFP results window, messages related to the last solution are displayed. These may
list problems as well.
© Forsk 2006 AT250_ARG_E2 17

AFP Reference Guide
The AFP result dialog is a non-blocking dialog. It enables the user to access other Atoll windows while the AFP is still pend-
ing. Thus, it is possible to view other data or warning/error messages in the Event viewer (for example, the history of AFP
solutions). From this stage, it is possible to commit, to resume or to quit the AFP. It is good practice to keep a report through
the export option before resuming the AFP. The user can also partially commit some of the results as explined next.
2.6.1 Partial Commit Functionality

It is often required to commit only a part of the automatically generated frequency plan rather than committing it entirely.
The purpose is to avoid committing TRXs that violate separation constraints (sometimes referred to as “not closing the
frequency plan”). Future Atoll versions will incorporate advanced automatic filters for partial commit.
The dialog examples below depict a case where removing a TRX eliminates a separation constraint violation on neigh-
bours. Once a TRX is manually removed from the resulting plan, separation violations are recalculated (may take a few
seconds). If the TCH TRX of transmitter Site36_3, causing neighbour separation constraint violations, is removed from the
sample frequency plan below, the resulting frequency plan has no neighbour separation constraint violations on the TCH
TRX of transmitter Site36_1.
It is possible to specify the action to be taken with each TRX individually, or globally delete all TRXs with separation viola-
tions. It is also possible to mix the old plan and the new plan. Though this is not recommended, since it can cause interfer-
ences of which the user might be unaware.
The dialog examples below depict how this operation can be carried out.
Figure 2.19: AFP Results Window - Partial Commit Feature
The Delete the TRX option implies that the resulting frequency plan will not respect the number of required TRXs. In the
above example, note than the neighbour separation constraint violations at transmitter Site36_1 vanished once the TCH
TRX at Site36_31 was deleted.
18 AT250_ARG_E2 © Forsk 2006

Figure 2.20: AFP Results Window - Partial Commit Feature
2.6.2 Automatic Constraint Violation Resolution

Different types of constraint violations, i.e. co-transmitter, co-site, neighbour, and exceptional pair, can automatically be
eliminated from the propsed frequency plan using the Automatic Constraint Violation Resolution tool. This tool is accessi-
ble from the Actions button menu.
Figure 2.21: Constraint Violation Resolution Tool
© Forsk 2006 AT250_ARG_E2 19

AFP Reference Guide
The aim of this tool is to find the TRXs in the currently proposed frequency plan that cause constraint violations of any of
the four following types:
1. Co-transmitter
2. Co-site
3. Neighbour
4. Exceptional Pair
Once it finds the TRXs that satisfy the criteria, it sets their corresponding values to Delete the TRX in the Channel Assign-
ment column of the AFP results window.
This tool lets you resolve any type of constraint violations for different types of TRXs, control or traffic. You can also define
a threshold of co-channel and adjacent channel collision probabilities. This restriction will only set those TRXs to Delete
the TRX, which have a co-channel or adjacent channel collision probability higher than the threshold you defined.
2.7 Visualising and Manipulating Results

The Commit button copies the frequency plan to the data structure. It is not necessary to save the document or commit the
changes to the database right away as the AFP cycle has not yet ended. At this stage, various generic and specific tools
are available in Atoll, and can be used to inspect the candidate frequency plan. Interference and C/I prediction studies and
various consistency checks are described in the following chapters of document. In addition to these, a useful tool is also
available in Atoll, called the Search tool. Its function is to facilitate visualising co-channel and adjacent-channel transmit-
ters. This tool is explained in detail in the User Manual. Other means of inspection include the common grouping, filtering,
advanced filtering, display and tool tip management features.
2.8 Manual Frequency Allocation

This section describes quick and useful techniques for performing manual frequency allocations in Atoll.
2.8.1 Manual Frequency Allocation for NH Case

To carry out manual frequency assignment:
1. Create a Best Server map and display it,

2. Display neighbours of the transmitter for which you want to find a frequency manually,
3. Open the Search tool,
4. By scanning the spectrum a good frequency can easily be found and can be allocated to the transmitter.
Figure 2.22: Scanning for Frequencies
20 AT250_ARG_E2 © Forsk 2006

In this example, frequency 11 is not a good choice since it is used as a neighbour co channel. Frequencies 10 and 12
present similar characteristics.
Figure 2.23: Scanning for Frequencies
On the other hand, frequency 14 is a good one and can be possibly allocated. None of the frequencies {13, 14, 15} are
allocated at the selected transmitter of at its neighbours.
2.8.2 Manual Frequency Allocation for SFH Case

It is possible to perform frequency allocations for irrgular pattern networks, i.e. patten allocation of type 1/N. The following
set of operations will results in a frequency allocation even if the network is not a 100% regular pattern network.
1. Run the AFP so that it creates the required number of TRXs.

2. Group the transmitters by azimuth and manually assign the MALs to the most important azimuth groups.
3. Filter out these azimuth groups and delete the TRXs of all transmitters that were not assigned a MAL manually.
4. Run the AFP again selecting MAIO assignment only. This will assign proper MAIOs to the TRXs to which MAL was
manually assigned.
5. Remove the filter and freeze the existing TRXs. Now use the AFP to complete the assignment (assigning all re-
sources).
© Forsk 2006 AT250_ARG_E2 21

AFP Reference Guide
22 AT250_ARG_E2 © Forsk 2006

Chapter 3
Frequency Planning Prerequisites
AFP Reference Guide
24 AT250_ARG_E2 © Forsk 2006

Chapter 3: Frequency Planning Prerequisites
3 Frequency Planning Prerequisites

The principal difference between AFP and other planning activities is that the impacts of poor frequency planning are more
widespread in a network. For example, poor planning of a site or a cell will have somewhat local influences, while imple-
menting a poor frequency plan will affect a much larger part of the network. Moreover, creating a poor frequency plan is
rather relatively easy, the presence of a single faulty parameter in the process can be sufficient for the damage the entire
plan.
Therefore, it is mandatory that the AFP user acquires a minimum level of knowledge regarding Atoll data model. This chap-
ter familiarises the user with the essentials of the data model and depicts their relations with the AFP.
3.1 Atoll Data Model

3.1.1 Reliability and Propagation
Often the user senses that the AFP does not have enough constraints:
• The unfrozen part of the AFP cost is 0 and the AFP stops due to this fact.
• There appear to be close frequency reuses in the resulting frequency plan.
This means that the problem is too “easy” for the AFP and the user would like to create a more difficult IM in order for the
AFP to have a more difficult problem to solve.
The best method to accomplish this is to increase the cell edge reliability and recalculate the IMs. When the reliability re-
quirement is elevated, a larger part of the standard deviation is reduced from “C” when calculating the C/I for each IM entry.
The user should also verify that the standard deviation is properly defined in all clutter classes and its default value. This
verification is more important in the case of Atoll documents converted from older versions or connected to a database.
Figure 3.1: Model Standard Deviation - Default Value
3.1.2 HCS Layers

HCS layers have several roles in Atoll. Their most important role is related to the way Atoll manages traffic maps. Different
layers have different priorities and mobility limitations. There is also the possibility to manage traffic overflow from one layer
to another. The objective of all these options is to model the behaviour of a real network, where two potential servers that
do not belong to the same layer usually do not compete for best server.
When calculating an IM, or when generating an interference study, HCS layers are used in generating service zone maps,
the basis of these calculations. If two transmitters belong to different layers, they can both serve the same pixel even if
received signal from one is much stronger than the other’s. For equal HO margins, more HSC layers mean higher overlap-
ping levels in the network. As the overlapping level increases, the constraint level in the IM and the amount of interference
in an interference study also increase.
Note: Be sure to study the priority mechanism in your network, both in the re-selection process and in the han-
dover process. Define the corresponding HCS layers once you know its working. When using a traffic
model, make sure that there are a few levels of mobility in order to model high speed / low speed mobility
behaviours.
© Forsk 2006 AT250_ARG_E2 25

AFP Reference Guide
3.1.3 Subcells
Subcells are defined as a group of TRXs in the same transmitter. Two subcells of the same transmitter can request fre-
quencies from different domains, require different C/I qualities, have different downlink power offsets and even have dif-
ferent Radio Resource Managements (RRM). Different RRMs can lead to different service zones under the same cell.
Subcells are crucial for modelling concentric and dual band transmitters. In these cases, the TRXs belonging to the “inner”
subcell serve traffic within a limited zone.
Note: All TRXs in a subcell share the same TRX type.
3.1.3.1 Key Roles of Subcells

• Associating TRX groups with required quality definitions
• Associating TRX groups with weak / strong constraints (interference , separation)
• Associating TRX groups with different domain limitations
• Visualising and filtering by TRX Type
• The following additional parameters are also defined in the Subcells table:
- HSN (since the inner zone HSN may be different from the outer zone HSN)
- Power offset
- Reception threshold (can limit the zone of the inner subcell)
- Hopping mode
- Assignment mode (in SFH, “group constrained mode” limits the choice of MAL to one of the groups in the do-
main)
- Support of DTX
- Traffic load and supplementary AFP weight
- Some other parameters influencing the AFP indirectly (for example, the overflow rate)
3.1.3.2 Concentric Cells and Dual-band Cells

Concentric cells were created in order to exploit downlink power control (DL PC) and radio resource management (RRM)
in frequency planning. This is accomplished by associating channels with subcells. Subcells may have different service
zones with respect to the transmitter’s geographic coverage. For example, a subcell TCH_INNER covers a zone requiring
minimum reception level of –75 dBm and TCH_OUTER covers a zone with minimum reception level of –94 dBm. In this
case, the inner zone has a higher resistance to increasing interference. The AFP has the possibility ot assign a relatively
interfered frequency to the TCH_INNER zone to give more choice to the outer zone.
The other important property of concentric cells is the fact that a downlink power offset is associated with each subcell.
The inner subcells can have higher DL PC implying that the frequencies assigned to the inner zones will interfere less with
other transmitters. Concentric cells permit a higher reuse pattern between inner zones, providing up to 40% increase in
capacity.
Atoll can fully exploit this increase in capacity since it calculates interferences between subcells. It uses the power offset
and the C/I threshold that defines the subcell boundaries. Furthermore, it is also possible to define separation constraints
at subcell level.
3.1.3.3 Minimum C/I

The required quality thresholds for BCCH and TCH are usually 12 and 9 dB respectively. But the GSM standard tests this
behaviour under the comfortable reception conditions of 20 dB above thermal noise. Therefore, it does not specify the be-
haviour for, for example, signals received being only 15 dB above thermal noise.
Atoll provides the possibility to define these thresholds at subcell level resulting in maximum flexibility and option to support
a mixture of old and new equipment. Moreover, the safety margins corresponding to these values can be defined in the
AFP cost definition (see C/I weighting in the next chapter).
3.1.3.3.1 Quality Targets

Atoll considers various quality requirements given by a C/I threshold value, “min C/I” with a probability threshold and “%
max interference”. These two values indicate that the probability of having C/I lower than the “min C/I” value must not be
greater then “% max interference”.
The benefit of this method is to facilitate Atoll in exploiting the fact that a larger number of TCH channels can be assigned
with quality requirements lower than the BCCH quality. This results in less constraining interferences and an easier and
faster assignment.
3.1.3.4 Traffic Loads

Traffic loads of all the subcells are used as input to the AFP. These traffic loads can be calculated by Atoll or read from the
Subcells table. Traffic loads are discussed in detail afterwards.
26 AT250_ARG_E2 © Forsk 2006

3.1.3.5 Local Domain Restrictions

Low level domain restrictions can be introduced at subcell level through the excluded channels column in the Subcells ta-
ble.
3.1.4 TRXs
Atoll’s TRX table enables the following:
• Support of an external ID space of the TRXs of a transmitter (important for import and export utilities).
• MAL / channel at TRX level.
• MAIO at TRX level.
• Fine freezing: The user can freeze specific TRXs in an unfrozen transmitter.
The TRX table does not contain an “active” field. Therefore, all TRXs in it should contain a valid frequency or MAL and are
all considered to be on air. It is better to remove an entire TRX record than removing only the frequency or MAL from its
channels list.
3.1.5 Freezing Flags

A multilevel freezing mechanism enables freezing resources at TRX level as well as at transmitter level. This, in turn, en-
ables the user to use an existing plan while assigning only newly added demand for channels. These options are in addition
to the working zone limitations.
Note: When freezing channels, keep in mind that the MAIOs are not frozen.
3.1.6 AFP Weights

The AFP weight field in the Transmitters table enables the user to assign high or low weightings to certain transmitters. It
can be used to improve quality at a problematic location or to boost quality in a particular covered region of the network.
An additional AFP weight field exists at the subcell level. It enables the user to assign weighting to subcells. A conventional
idea could be to assign a higher weight to the BCCH. The AFP uses the multiplicative product of transmitter level AFP
weight and subcell level AFP weight.
3.1.7 Spectrum Administration

Many levels of administration exist relative to frequency planning. In order to avoid confusion, here is a comprehensive list:
• ARFCNs
ARFCN is the method employed by the GSM/DCS standards to enumerate 200 kHz frequency carriers.
• Frequency Bands
Frequency Bands are subgroups of ARFCNs. Different equipment may be limited to different frequency bands (BTS, MS,
…). In addition, propagation models use the central frequency of the band for calculating propagation.
• Frequency Domains
Domains are used for managing the usage of the Frequency Bands. For example, an operator may use frequencies 1 to
50 while the other uses 52 to 100. Splitting the band on channel usage basis is of great importance as well (BCCH frequen-
cies, TCH frequencies, Hopping layer).
• Domain Groups
Domain groups are used for further managing the use of the frequencies in a domain. For example, f1 and f2 can be as-
signed at the same transmitter if and only if they belong to the same group. Another frequent use for groups is in the MAL
assignment.
In Atoll, a domain is defined as a union of groups. It points to a frequency band and must be included therein. The AFP
respects domain limitations at subcell level.
3.1.8 Redundancy and Subcell Audit

Atoll incorporates some deliberate redundancies between the subcells and TRX levels, and the Transmitters table:
• The channel list in the Transmitters table is the intersection of all channels appearing in the TRXs of a transmitter.
© Forsk 2006 AT250_ARG_E2 27

AFP Reference Guide
• The hopping mode of a transmitter is the hopping mode of it’s default traffic carrier (the TCH TRX Type)
• The frequency band of the transmitter (the one used by the propagation model to deduce the central frequency),
is read from the domain of the BCCH subcell of the transmitter.
Atoll considers the low level to be the accurate source of information. For example:
• Atoll will automatically update the TRX table if the channel list of a transmitter in the transmitter table is changed.
• The frequency band of a transmitter cannot be edited.
These redundancies provide some additional features (for example, grouping transmitters according to the frequency
bands).
On the other hand, there is a chance of mistakes and bugs which may damage a redundancy in the ATL file. Therefore, it
is recommended that the audit tool be used from time to time in order to fix these problems (right click on the Transmitters
folder, choose Audit from the Subcells menu).
3.1.9 Neighbour Importance

Neighbour importance field exists in the neighbour relation tables. It is also available in the AFP and can assist in resolving
congestion situations. This is discussed in detail in subsequent chapters.
3.1.10 SeparationConstraints Table

It is a separation exceptional-pair table containing pairs of subcells with associated separation requirements. Special sep-
arations have a higher priority with respect to all other separations and can be used to relax separation constraints as well.
3.1.11 SeparationRules Table and Rule Priority

The SeparationRules table is simple to understand once the order of priority that exists between various separation rules
is kept in mind:
1. Highest priority: exceptional pairs

2. Second higher: co-transmitter
3. Third priority: co-site
4. Last priority: Neighbour.
For example, if two subcells are neighbours and at the same site, their associated separation requirement will be according
to the co-site separation rules. And, if this separation requirement is not fulfilled, their separation violation costs will be
weighted by the co-site weight.
3.1.12 Adjacency Suppression

Adjacency suppression is defined as the difference between the required C/I and the required C/A (C/A being the “Carrier
to Adjacent Intensity ratio”). By default this is set to 18 dB following the standard. It is available in the Predictions folder
properties dialog window under the name “Adjacent channel protection level”.
The GSM standard requires this desired behaviour but does not specify any amplification level. It is recommended to be
sure that the physical equipment in the network support this value. The value of this parameter is used in the AFP when
extracting the interference caused by an adjacent channel, and in Atoll in interference and C/I studies.
It might be a good idea to use a safety margin for this parameter and set it to 16 dB, for example.
3.2 AFP Performance Indicators

The AFP can be used to generate different AFP performance indicators and listing them in the AFP results window. These
performance indicators describe the states of different network entities, such as TRXs, subcells, transmitters and sites.
3.2.1 AFP TRX Rank

AFP TRX Rank provides a ranking of the TRXs in a subcell. If a TRX rank is high, it implies that the frequency (channel)
corresponding to this TRX has bad usage conditions. TRX ranks indicate the best and worst quality TRXs in each subcell,
which maybe candidate GPRS TRXs or potentially removable TRXs to improve overall network quality. The OMC might
use rank (or preference) information for better RRM.
28 AT250_ARG_E2 © Forsk 2006

Notes:
1. Rank = 1 is the best rank.
2. TRX Rank is the corresponding field in the TRX table.
As it is during an AFP process that frequencies and MALs/MAIOs for different TRXs of a subcell are chosen, the AFP tool
stores and manipulates the information about TRXs in good and in bad conditions.
If you choose AFP Rank indicator to be allocated when starting an AFP session, each cost improving solution will go
through a TRX rank assignment. If no improving plan is found, TRX rank will be assigned for the initial plan (like BSIC).
TRX ranking within a subcell is performed on the basis of TRX costs.
In many cases of MAL/MAIO assignment, only one or two of a TRX’s MAIOs violate separation constraints. Therefore, a
higher ranking will be assigned to the MAIO violating the separation constraints.
3.2.1.1 TRX Rank Usage

This information can help increase performance in certain cases where a cell and its neighbour are not loaded with traffic
at the same time (for example, a stadium and its parking lot). In such cases, it is possible to decrease call blocking by add-
ing the TRXs in bad conditions to the concerned cells. If the BTSs do not recognize TRXs in bad conditions, the overall
network behaviour will either be very poor or difficult to predict even if the BTS knows how to track ranking in real time.
TRX ranks may be required by the OMC in order to optimise the spectral efficiency. In some networks, a part of the deci-
sion-making process at the OMC may be transferred to the BTSs when this information is available. Even if such a “smart”
system exists, it might be better to know the TRX ranks in advance to improve predictability and consistent behaviour.
Apart from these uses, AFP TRX ranks can be used in post-AFP optimisation. For example, once you perform AFP, you
can freeze all TRXs with ranks less than or equal to X. So that a new AFP instance will concentrate on a smaller subset of
the most interfered TRXs in the most loaded subcells.
A TRX will not be considered frozen for TRX Rank assignment if and only if it is selected for AFP allocation and has not
been frozen at Transmitter level or by the AFP launch Wizard.
3.2.2 Total Cost and Separation Violation Cost Component

Total cost and separation violation cost component at the TRX, subcell, transmitter and site levels can be computed and
displayed as AFP performance indicators. These are the cumulated total costs and the cumulated separation violation
costs of each TRX, subcell, transmitter and site.
In order to be able to compute and display these results, you must add AFP_COST and AFP_SEP_COST fields (of type
SINGLE) to the TRX, Subcells, Transmitters and Sites tables. AFP_COST field and AFP_SEP_COST field correspond to
the total cost and separation cost component respectively. These AFP performance indicators are available in the list of
AFP performance indicators to be computed available when launching the AFP tool.
The AFP cost assignment to the TRXs, subcells, transmitters and sites is carried out at the same time as the TRX rank
assignment. Once a frequency plan is committed, the next instance of the AFP can concentrate more on the problematic
TRX/subcell/transmitter/site to improve results. Another use of this feature can be to automatically limit the modification
scope to the problematic cells/sites. This feature can deliver a significant quality gain.
© Forsk 2006 AT250_ARG_E2 29

AFP Reference Guide
30 AT250_ARG_E2 © Forsk 2006

Chapter 4
Frequency Plan Optimisation
AFP Reference Guide
32 AT250_ARG_E2 © Forsk 2006

Chapter 4: Frequency Plan Optimisation
4 Frequency Plan Optimisation

4.1 Step 1 (Optional): Traffic Model Usage
It is not possible to solve a difficult optimisation problem without having a traffic model. Following are the 4 principal roles
of a traffic model:
1. To reduce the required number of TRXs where they are least needed and spectrum not available.
2. To indicate the least loaded TRXs, since they are less important and interfere less with others TRXs.
3. To reduce the constraint level of the IM (for example where interferences are limited to low density surface).
4. To provide an accurate quality estimation of the resulting frequency plan.
The first point is currently implemented through a dimensioning model, which is explained in this chapter. Moreover, it will
be available as an AFP option in one of the future versions (i.e. the AFP will optimise the decisions so as not to respect the
required number of TRXs. In other words, it will perform a spectrum oriented dimensioning). The second role is carried out
by the traffic loads. In order to understand traffic loads better, traffic capture is also described subsequently. The third point
is explained alongwith the description of the IM and the last point is detailed in chapter 5.
The Atoll traffic model is quite advanced. To gain familiarity with the concepts of user profiles, environments, services, mo-
bile types, terminal types etc. a new user should refer to the Atoll User Manual. These traffic model entities can be used to
benefit from all possible capacity gaps in a network. The simplest application here, would be to use a clutter weight oriented
model. The more advanced models and techniques of creating traffic maps, based on traffic-by-transmitter etc., are also
explained in detail in the Atoll User Manual. This chapter provides with the basic know-how on creating the simplest model
using clutter information and clutter weights.
4.1.1 Creating a Traffic Map Based only on Clutter Weighting

There are two simple methods:
• Using a raster map

- Define a simple user profile for an active user with voice service, speaking 3600s per hour (i.e. consuming 1
Erlang).
- Create a traffic environment of this kind of user profile with a density of 1 and pedestrian mobility. Any mobility
can be used (e.g. 1), as it will be used for calculating IM where only the relative weight matters.
- Assign appropriate clutter weighting to this traffic environment.
- In the Geo tab, create a new traffic map based on environments through the GSM GPRS EGPRS Traffic folder
context menu. On the drawing toolbar, select the traffic environment created earlier, click on the polygon but-
ton and draw a polygon surrounding the computation zone. This raster map will appear in the Traffic folder.
• Using a vector map

- Define a simple user profile for an active user with voice service, speaking 3600s per hour (i.e. consuming 1
Erlang).
- In the Geo tab, create a new traffic map based on user profiles through the GSM GPRS EGPRS Traffic folder
context menu. Select the user profile just created with pedestrian mobility and assign density to the Density
field.
- Assign appropriate clutter weighting.
- Click on the polygon button on the drawing toolbar and draw a polygon surrounding the computation zone.
Double-click on it and assign a density of 1. This vector map will appear in the Traffic folder.
Both traffic maps are stored in the document and can be exported. An exported vector map is smaller than a raster one.
4.1.2 Performing a Traffic Capture

Traffic capture is a means to cumulate one or more traffic maps, for voice and/or data services, for different terminals and
provide a spreading of traffic per sector respecting layer priorities, frequency bands and other rules that can be defined by
the user. The details of this process are described in Appendix 4 (Traffic Capture and Dimensioning). Once traffic analysis
is performed, a traffic capture object is available in the Explorer window Data tab. This traffic capture object contains traffic
demand per [service, subcell] pair in terms of Erlangs for CS traffic and kbps for PS traffic. This traffic demand provides
Atoll with an estimate of average demand in terms of # TSL used.
The AFP combines this traffic capture with the number of required TRXs and their timeslot configurations to generate traffic
loads (assuming the AFP will create the required number of TRXs indicated in the subcell table).
The dimensioning process reads the basic information contained in the traffic capture to find out the number of TRXs need-
ed to support a user defined blocking rate, HR ratio etc. (See Appendix 4 for details).
The KPI calculations combine traffic capture with the current number of TRXs in the network and their timeslot configura-
tions to generate current traffic loads.
© Forsk 2006 AT250_ARG_E2 33

AFP Reference Guide
Important: Keep in mind that the required number of TRXs is the number of TRXs required to carry a given traffic. This
is the number of TRXs (usually) calculated through the dimensioning process. The number of existing
TRXs is the current actual number to TRXs at a transmitter.
4.1.3 Creating IMs Based on Traffic

IM calculation is either based on uniform distribution or on the maps used to perform the default traffic capture. In order to
calculate IMs based on a traffic clutter weighting,
• Create the traffic map as described earlier,

• Perform a traffic capture using only this traffic map,
• make this traffic capture the default one, and
• Select the option "Traffic spreading based on the maps used in the default traffic capture" in the IM calculation di-
alog.
This option has the following advantages:
• Interference over “hot spots” will have more weight

- Example: Sites covering an important highway will interfere over the highway but the interfered surface will be
less compared to the coverage. Therefore, not significant if no traffic is used.
• Interference over dead spots will not create overhead constraints
- Example: A large hilly park in the middle of a city is often not covered by a dedicated site since it has low traffic.
The slopes of this hill are covered by many overlapping cells and tend to create many undesirable IM entries.
If the weight of these slopes is reduced due to very little traffic, this can simplify an over-constrained problem.
See Appendix 3 to understand further why traffic loads and interference information are not combined together in Atoll.
4.2 Step 2 (Optional): Neighbour Relations and Relative

Weighting
In many cases, neighbour relations are the most constraining elements for the AFP. Neighbour importance field of the
neighbours table permits the AFP to partially ignore weak / far-away neighbours and concentrate more on the more impor-
tant neighbours.
This section details the use of this new feature in various scenarios.
Tip:
Check neighbour allocation before running the AFP. Often a bad neighbour relation definition causes poor frequency
plan performance.
4.2.1 Automatic Neighbour Allocation

Neighbour importance has two major roles in Atoll:
1. Weighting the neighbour relation in the AFP.

2. Ranking the neighbours so that Atoll can select the n most important neighbours.
The configuration presented below is recommended in order to use the resulting neighbour importance in the AFP.
• Coverage Factor: 1% to 81%

• Adjacency Factor: 20% to 90%
• Co-site Factor: 70% to 100%
Note: The default values for computing importance values are:

Coverage Factor: 1% to 30%
Adjacency Factor: 30% to 60%
Co-site Factor: 60% to 100%
The neighbour allocation algorithm works as in earlier versions with these default values. Changing these
values changes the priority definitions of the neighbour allocation algorithm. Refer to the Technical Refer-
ence Guide for more details.
34 AT250_ARG_E2 © Forsk 2006

Figure 4.1: Automatic Neighbour Allocation
AFP can be launched once the results of the neighbour allocation have been generated and committed.
4.2.2 Importing Neighbour Importance

Various sources of neighbour importance exist:
• OMC HO statistics
• Test mobile data measurements (which ignore interferences between non-neighbours)
• Other
As with any other source of information, it is the user’s task to prepare and import this external data. The units of the neigh-
bour importance are probabilities and are expected to reamin between 0 and 1.
4.2.3 Extending Existing Neighbour Relations

Extending an existing neighbour relation should be performed often either to solve some HO problems or because of ad-
dition of new sites. Such operations usually imply that a fresh frequency allocation be carried out. The AFP would be re-
quired to use the original neighbour relations as well as the new additional neighbours, yet in a different way (with a
different weight). In addition, the AFP would require access to the former (complete or partial) source of neighbour impor-
tance as well as to the new values of neighbour importance calculated for the recently added relations.
The neighbour importance of the original neighbour assignment is probably more reliable than the one calculated using
path loss calculations.
This section explains how this can be done:
1. Export the current neighbour relation into a file called AllCurrentNei.txt using the generic export feature available
through the context menu of the table,
2. Export all the relations for which there are reliable neighbour importance into a file named
AllCurrentNei_Importance.txt,
3. Import the file AllCurrentNei.txt into the neighbour exceptional pairs so that the existing neighbour allocation is
forced (usual operation for extending an existing allocation),
4. Run automatic neighbour allocation in order to extend your neighbour relations and/or assign importance where it
was not already assigned. To keep important values lower than X%, all Max% values in the importance part of the
dialog should be kept less than X. For example, if X is 50%, the configuration shown below can be used,
© Forsk 2006 AT250_ARG_E2 35

AFP Reference Guide
Figure 4.2: Automatic Neighbour Allocation Results
As can be observed in the figure above, all new neighbour relations have weak importance values.
5. Commit the allocation,

6. Import the file, and answer “no” if asked to remove neighbours of modified transmitters.
The screenshot below shows that the neighbour relations now comprise old neighbours with a higher importance and new
neighbours with a lower importance automatically calculated by Atoll.
Figure 4.3: Neighbours Table
4.2.4 Importing Partial Sources of Neighbour Importance

Atoll’s generic import feature can be used to import the data easily. In order to import, the user should know the location
to place this imported data (Importance column of the Neighbours table) and the data units (probabilities between 0 and 1).
36 AT250_ARG_E2 © Forsk 2006

4.3 Step 3 (Optional): Using Dimensioning

The Atoll dimensioning model, combined with the traffic capture, is a strong tool for frequency plan optimisation. In most
cases, where a spectrum problem exists and the problem does not originate from the neighbour relation, the second most
important task is to reduce the number of required TRXs in a selective and careful way.
This optimisation can currently be carried out with the help of the dimensioning model. In future versions, it may be avail-
able directly through the AFP.
4.3.1 Optimal Dimensioning of an Existing Network

1. Run the AFP and commit the resulting frequency plan. Proceed to the next step if this frequency plan is not satis-
factory and the TRX demands have to be reduced.
2. Increase the service blocking rates (from 2% to 4% for example). The screenshot below shows:
- Where this can be done (Services table).
- That the dimensioning model is based on blocking.
- The effect this change has on the required number of TRXs (the number of existing TRXs being the previous
number of required TRXs for 2% blocking rate committed in Step 1).
3. Recalculate the traffic capture since service definitions have changed and then launch dimensioning. Some trans-
mitters will have less required TRXs while others, which were more loaded, have the same number of required
TRXs as before.
Figure 4.4: Dimensioning Process
Running the AFP once more can return an improved frequency plan, as the following example shows:
AFP cost for the empty Sum of

Separation
network, indicating the Number of Interference Missing TRX
Action performed Violation
number of weighted Required Cost Erlangs
Cost
Erlangs TRXs
Original network 603.6 100 106 9.7 0
After increasing the
Blocking Probability to 601.4 95 96.6 9.4 0
4% and dimensioning
© Forsk 2006 AT250_ARG_E2 37

AFP Reference Guide
The above experiment proves that the capacity difference between the two networks is very low (first column, around 2
Erlangs). This means that the reduction of 5 TRXs leads to a very minor decrease in capacity. This is due to the fact that
this was done by dimensioning considerations rather than other possible considerations.
The AFP generates a better plan after this decrease in the number of TRXs. The AFP cost units are Erlangs, therefore, we
can compare the 2 Erlangs lost because of capacity to the 10 Erlangs gained because of better AFP cost.
Note: It is possible to set a “Maximum number of TRXs” in the Transmitters table. You can copy and paste the
current demand to this column, thus forcing the dimensioning process to respect the current state of the
network as an upper bound. This possibility is a handy in all possible cases of difficult frequency allocation.
4.4 Step 4: Optimal Usage of the Atoll AFP

4.4.1 Introduction to the AFP Cost Function
4.4.1.1 Combination of Separation Violation and Interference Probabilities
The cost function of Atoll AFP has two main components. The first component is the cost for violations of separation con-
straints and the second component is the cost for creating interference.
Atoll AFP gives each separation violation a cost equivalent to a certain amount of interference, making it possible to sum
both costs and minimize their sum. For example, the user can define that a separation violation of 1 “costs” the same as
x% of interfered traffic. This is weighted by the type of violation (co-transmitter separation violations have higher impact
than neighbour separation violations). Through this equivalence, It is possible to sum separation violation and interference
costs that share a common unit, i.e. percentage of interfered traffic.
Following this principle, all other cost elements are also calculated in the same manner, the cost of Missing TRXs, the cost
of corrupted TRXs, the cost of a TRX assigned out-of-domain frequencies and the cost of changing a TRX’s assignment.
4.4.1.2 Counting TRXs (Nodes) Instead of Relations (Edges)

In the following example, each separation violation represents an edge and each TRX a node. All the 3 frequency plans
proposed in this example do not respect all separation requirements for all TRXs, meaning that they all have bad nodes
and bad edges. Now the question is that whether the AFP minimization target should try to minimize the number of bad
edges or the number of bad nodes.
Example:
• Imagine a network with 6 TRXs, all having a separation constraint of 1 with each other (i.e. 6 nodes, 15 Edges).
• The following 3 cases demonstrate the way the AFP calculates the cost of an allocation.
Case 1 Case 2 Case 3

F1 is used 4 times, F2 and F3 are F1 is used 3 times, F2 twice, and F3 is F1, F2, and F3 are used two times
used one time each. only used one time. each.
Number of separation violations is 6 Number of separation violation is 4 Number of separation violations is 3

(6 bad edges) (4 bad edges) (3 bad edges)
Two TRXs have good assignments Only one TRX has a good assignment No TRX has a good assignment
The spectrum is not equally used The spectrum is equally used
• Atoll AFP prefers Case 1 by default. Nevertheless, it can be configured to opt for Case 3.
The parameters that control the capability of Atoll AFP to be more Edge-oriented than Node-oriented are explained next.
But, before this explanation, following are the three main advantages of the Node-oriented approach:
1. The cost function has meaningful units, i.e. Interfered Erlangs.

2. The ability to focus problems on a TRX that is already 100% interfered and to improve the others instead of spread-
ing interference on several TRXs.
3. The capability to respect a TRX based quality target, i.e. dismissing interference at a TRX that does not sum up to
a certain considerable value (explained below).
The Node-oriented approach is an important feature of the Atoll AFP and provides a tighter correspondence between the
AFP cost and the network quality.
38 AT250_ARG_E2 © Forsk 2006

4.4.1.3 Each TRX Cost

The AFP cost function is summed up for each TRX according to the following logic:
• If TRX α is corrupted, the tax of being corrupted is added to the cost, and multiplied by T(α).
• If TRX α is missing (the required number of TRXs and the actual number of TRXs being different), the tax of miss-
ing TRX is added to the cost, and multiplied by T(α).
• If TRX α has out-of-domain frequencies assigned to it, the tax of out-of-domain frequency assignment is added to
the cost, and multiplied by T(α).
• Otherwise, the separation cost, the interference cost and the changing load of this TRX are summed up (probabi-
listically) and added to the cost, and multiplied by T(α).
• If this sum is very small, it is discarded (see the Quality Target section)
Here, T(α) is an estimation of the traffic Erlangs using TRX α weighted by the AFP weight for this TRX.
The user can fully control the AFP cost target by determining the value of the cost function parameters. Some of these
parameters belong to the data model, e.g. “Maximum MAL Length” and “Minimum C/I”, while others are present in the
specifc AFP GUI. Appendix 2 explains how to find each of these parameters.
Note: The AFP cost is the cost of the entire loaded network, not only the cost of the selected or non-frozen TRXs.
In many cases, the AFP is authorized to change only a part of the network. Therefore, the part of the cost
corresponding to the non-frozen part of the network and the part of the cost corresponding to the frozen
part of the network are indicated.
4.4.1.4 Separation Violation Cost

In this section, interference cost is ignored in order to understand the separation violation cost. A TRX having only one
separation violation is considered.
Let Sij denote the required separation between two transmitters in a network. If f1 is assigned at i and f2 at j such that
( f 1 – f 2 ) < S ij , this means that the separation constraint is not satisfied. A separation constraint can be violated strongly or
weakly:
For example, the pair of frequencies (1, 2) violates a separation requirement of 3. The pair of frequencies 1 and 3 violate
this requirement as well but is still a better solution than (1, 2) and, therefore, should have a lower cost.
Frequencies that are part of a MAL with a low fractional load and that disobey a separation constraint, should not be weight-
ed the same as in non-hopping separation violation. In fact, the separation component is weighted by the burst collision
probability, which is the multiplication of the victim’s fractional load and the interferer’s fractional load.
Example: Let us consider the following simple case of a network comprising two TRXs in the same cell. The first, TRXi,
has a MAL denoted as MALi. It is interfered by TRXk having MALk. TRXi and TRXk have a separation requirement of 2.
Their MAL lengths are respectively 5 and 4. Unfortunately, one of their frequencies is the same (i.e. separation = 0), while
all other frequencies are correct. For the case of a co-channel violation when the required separation is 2, the cost of the
separation violation is 90%, as shown in the dialog bellow:
Figure 4.5: Atoll AFP Module Properties - Separation Weights Tab
© Forsk 2006 AT250_ARG_E2 39

AFP Reference Guide
Since only one channel of each TRX causes interference, with length(MALi)=5 and length(MALk)=4, the collision probabil-
ity is 1/20. Hence, the cost to consider is divided by 20, i.e. 90/20 = 4.5% for each TRX.
In addition, since the two TRXs have different MAL lengths, they have different interferer diversity gains: a gain of 1.4 for
MAL length of 5 and a gain of 1.2 for MAL length of 4 (see Appendix 2 for details).
( 1.4 ⁄ 10 )
Applying interference diversity gain of 1.4 dB means that the cost will be divided by the value: 10 ≈ 1.38 . For TRXi,
this will give 4.5% / 1.38 = 3.25%.
1 90
For TRXk, the cost to consider will be ------ ------------------------ = 3.41% .
20 10 ( 1.2 ⁄ 10 )
Now, in order to get the exact contribution to the separation cost component, these values are multipilies by the traffic load
(Erlangs / timeslot) and by the number of traffic carrier timeslots in each TRX. Assuming the traffic load to be 1 and that
each TRX has 8 traffic carrier timeslots, we will get (8 x 3.25 + 8 x 3.41), i.e. about 0.5 Erlangs for the two TRXs together.
Note: In this example, the AFP weight was assumed to be 1, the traffic loads were assumed to be 1, no DTX was
involved, no other interference or violation was combined with the above, the global separation cost was
set to be 1, and the co-transmitter separation weight was set to 1 as well.
4.4.1.5 Interference Cost

Traffic on a TRX will be interfered if and only if co/adjacent-channel reuse exists within interfering transmitters. Each such
reuse will reduce the amount of good traffic and increase the interference cost. It will be weighted by the global interference
weighting factor, and will take into account the burst collision probability in the same way as in the example above.
4.4.1.6 Probabilistic Cost combination

Assume that TRX α is subject to a separation violation causing a cost of 30% of T(α) (T(α) = Traffic of TRX α) and in ad-
dition, a co/adjacent-channel reuse causing this TRX to be 40% interfered. This section explains how these two events are
summed together.
The solution to this problem is provided by a probabilistic approach: all different costs are considered as bad events and
are combined as if these events were independent.
The probabilities of events in this example are p(Violation) = 0.3 and p(Interference) = 0.4. The cost of the two together is
given by:
1 – ( 1 – p ( Violation ) ) × ( 1 – p ( Interference ) ) = 0.58 or 58%
Let P1, P2, ….Pn be the violation probability costs of the given TRX (one for each of its n violations).
Let Pn+1, Pn+2, ….Pm be the interference probability costs of the given TRX (one for each of its (m-n) interferences).
Let Pm+1 be the “changing TRX cost” described below.
n
⎛ ⎞
The separation cost of this TRX will therefore be: ⎜ 1 – ( 1 – P i )⎟
∏
⎜ ⎟
⎝ i=1 ⎠
m+1 n
⎛ ⎞ ⎛ ⎞
⎜ ( 1 – P i )⎟ – ⎜1 – ( 1 – P i )⎟
The additional cost of this TRX will be ⎜ 1 – ∏ ⎟ ⎜ ∏ ⎟
⎝ i=1 ⎠ ⎝ i=1 ⎠
The interference cost uses the “min C/I” value, defined at subcell level, for which it may have precise pair-wise interference
information. It may apply various gains to this C/I quality target due to frequency hopping and/or DTX.
4.4.1.7 Missing TRX Cost

It is easy to have a 0-cost solution if the required number of TRXs criterion is not fulfilled (by removing all TRXs, for exam-
ple). This is the main purpose of missing TRX cost. By default, the exact traffic that a missing TRX was supposed to carry
will be counted by the cost function. However, the user can increase this tax (to 200% for example) if needed.
In certain cases, creating more TRXs will not only generate interferences for the newly assigned TRXs but also for other
TRXs that, otherwise, would have correct assignments. This parameter enables the user to tune the AFP in its tradeoffs
between respecting the number of required TRXs and optimising quality.
40 AT250_ARG_E2 © Forsk 2006

Note: The Atoll AFP always assigns as many TRXs as the “Required TRXs” field indicates. The user can only
decide regarding the better plan, i.e. the previous plan having a better quality but some missing TRXs or
the new plan having lower quality but having all required TRXs assigned. In future versions, the AFP will be
capable of optimising these decisions as well.
4.4.1.8 Corrupted TRX Cost

It is easy to generate a 0-cost solution if frequency domain constraints are not satisfied (by putting an arbitrary channel,
for example). This cost component exists in order to avoid this behaviour. By default, 1000% of the traffic that a corrupted
TRX is supposed to carry will be considered impaired.
In some cases, fixing the assignment on a group of corrupted TRXs will not only result in an interfered assignment for these
TRXs but also for many other TRXs that, otherwise, would have correct assignments. It is for this reason that this tax is
higher than 100%.
Note: A TRX is corrupted not only if it contains frequencies that are out of domain but also when:
- An NH TRX has a MAL with more than one frequency
- A TRX has no channel at all
- A group constrained SFH TRX is assigned a MAL that is not strictly a group of its domain
- An SFH TRX has no MAIO, or no HSN, or has an out of domain HSN / MAIO value.
In future versions, different corruption reasons will have different tax levels and the assignment of a corrupted TRX will not
always be ignored.
4.4.1.9 Out-of-domain Frequency Assignment Cost

TRXs may have proper ARFCN assigned yet may not comply with the frequency domain definition. In many cases, the
frequency domain limitations are not fully respected in the surroundings of the zone considered for frequency planning.
This cost component can not be ignored or be modelled by the corrupted TRX cost because such a corrupted TRX can
interfere and be interfered, which will be ignored in both the cases.
If a TRX is assigned out-of-domain frequencies (channels) but has correct ARFCNs, it will have dual influence on the cost:
1. The normal cost of interference, separation and/or modification.

2. An additional cost of having out-of-domain channels, multiplied by the number of frequencies out of domain and
divided by the MAL length.
Note: If SFH and group constrained subcells have out-of-domain channels, and are frozen, the frozen TRX will be
ignored altogether.
4.4.1.10 Quality Target

It is often required to handle small and large interferences differently. For example, it would be preferable to have 10 trans-
mitters with 2% interfered traffic than to have two transmitters with 10% interfered traffic. The last section in the Atoll AFP
properties dialog window is an option to dismiss interference and separation costs that do not sum up to the value of the
parameter “% Max Interference" in the Subcells table. TRXs that comply with their ‘% Max Interference’ are excluded from
the cost.
4.4.1.11 Modifiable and Non-modifiable Costs

Interfered Erlangs or separation constraint violations between frozen TRXs can not be resolved by the AFP. The AFP can
only reduce the non-frozen cost, which is the modifiable cost.
Modifiable and non-modifiable parts of the total netwok cost are linked in concept with the definition of the AFP scope, sec-
tion 2.3. Four groups of transmitters can be defined with respect to AFP:
• ALL = All the transmitters in the project.

• NET = Active transmitters that pass the filters on the main Transmitters folder and on the main Sites folder.
• SEL = Transmitters belonging to the (sub)folder for which the AFP was launched and that are in the intersection
of the calculation zone and focus zone.
• RING = Transmitters belonging to NET, not belonging to SEL and having some relationship with the transmitters
in SEL:
- If interferences are to be taken into account, all transmitters whose calculation radii intersect the calculation
radius of any transmitter in SEL will be included in RING. For large calculation radii (20 km for example), a
single site can have a very large RING loaded.
- Neighbours are always included in RING.
- If one transmitter of an Exceptional Pair is included in SEL and the other is not, then the other will be included
in RING.
© Forsk 2006 AT250_ARG_E2 41

AFP Reference Guide
- If BSIC assignment is required, then all the second order neighbours (neighbours of neighbours) will be includ-
ed in RING.
The total cost of the network corresponds to SEL+RING. It contains the modifiable as well as the non-modifiable parts of
the network costs.
The modifiable part of the total cost of the network corresponds to SEL. However, this cost does not include costs corre-
sponding to frozen entities of transmitters in SEL.
The non-modifiable part of the total cost of the network corresponds to RING. It includes the costs corresponding to frozen
entities of transmitters in SEL.
In each instance of an AFP process, there might be entities frozen by the user. In addition to the generic freezing options,
there are finer freezing options available in the data structure:
1. Individual transmitters can be frozen for channel (and MAL), HSN and/or BSIC assignment.
2. Individual TRX’s can be frozen for channel (and MAL) assignment.
4.4.2 Most Important Cost Function Parameters and Tuning

It is strongly advised that the user should fully understand the different cost function parameters before manipulating them.
In order to understand the parameters that are not explained in this section, please refer to Appendices 1 and 3.
The figure below depicts the Cost tab of the AFP properties dialog:
Figure 4.6: Atoll AFP Module Properties - Cost Tab
4.4.2.1 Interference Weight vs. Separation Weight

The most important parameters are the ones outlined by rectangles in the figure above. Interference and separation
weights are used as multiplicative factors before each interference or violation event. Therefore, these parameters have
the ability to reduce one type of event cost compared to the other. If these two parameters are set to low values (for exam-
ple, 0.1 and 0.035 respectively), AFP will be forced to work according to the edge-oriented strategy, which is probably not
the recommended approach. By default, interference events are less important than separation violation events.
4.4.2.2 Cost of Changing a TRX

The second most important parameter (also outlined with a rectangle in the figure above), is the cost of modifying a TRX.
This is recommended to be used if the non-frozen part of the network should be changed as little as possible. The following
experiment shows the effects using this parameter can have:
42 AT250_ARG_E2 © Forsk 2006

Test case:
A network with 90 transmitters in total, 15 frozen transmitters and sum of required TRXs = 257.
Only 193 good TRXs were already allocated.
64 TRXs should be created / newly allocated with as little influence as possible on the other 193 TRXs.
For a cost of changing a TRX = 1 AFP changed only 98 TRXS
For a cost of changing a TRX = 0.3 AFP changed only 129 TRXS
For a cost of changing a TRX = 0.1 AFP changed only 139 TRXS
For a cost of changing a TRX = 0 AFP changed 162 TRXS
4.4.2.3 Quality Target and C/I Weighting

4.4.2.3.1 Quality Target
The quality target (Global Cost, outlined with a rectangle as well in the figure above) corresponds to dismissing the cost of
a TRX when its cost probability is less than a corresponding threshold in the Subcells table.
4.4.2.3.2 C/I Weighting

The last option (related to the quality threshold, also outlined with a rectangle), referred to as C/I weighting, is more com-
plicated. When this option is used, the AFP takes into account that the traffic having close-to-threshold C/I conditions is
neither 100% satisfactory nor 100% corrupted. In this way, safety margins on the threshold C/I conditions can be avoided.
Therefore, the user must specify a margin around which a “slope” is created, as illustrated in the figure below. This figure
corresponds to an interference relation between two TRXs. It describes the distribution of traffic according to C/I conditions.
It depicts the effect of 3 different quality requirements on the interference cost of a co-channel frequency reuse.
It can be observed that, when a low quality (C/I > 8 dB) is required, less traffic is considered as interfered than for a high
quality (C/I > 11 dB).
Figure 4.7: C/I Weighting
The option ‘C/I >10 dB + 2dB margin’ has the advantage of not being too strict on one hand, and yet trying to achieve high
quality if possible. It is visible from the above figure how it integrates the different traffic classes into the interference cost.
4.4.2.4 Separation Weights Settings

The Separation Weights tab enables the user to define relative weights of different separation types with respect to each
other and of one co-channel violation with respect to an adjacent channel violation and so on.
The figure below shows the Separation Weights tab of the AFP properties dialog.
© Forsk 2006 AT250_ARG_E2 43

AFP Reference Guide
Figure 4.8: Atoll AFP Module Properties - Separation Weights Tab
Other tabs of the AFP module properties dialog are more advanced. Please refer to the Atoll User Manual for more infor-
mation on AFP module properties tabs.
44 AT250_ARG_E2 © Forsk 2006

Chapter 5
Means to Evaluate Frequency Plans
AFP Reference Guide
46 AT250_ARG_E2 © Forsk 2006

Chapter 5: Means to Evaluate Frequency Plans
5 Means to Evaluate Frequency Plans

5.1 Estimating Frequency Plan Quality
5.1.1 Using Interference Studies
The full description of the interference study features is outside the scope of this document. Nonetheless, it is important to
understand that a geographically based interference study has an important advantage over any simulation based on pair-
wise interference matrices (or histograms).
Atoll interference studies are geographic studies that analyse each point on the map. For each point, an interference study
estimates the carrier power and then sums up the interference powers taking burst collision probabilities, DTX, and traffic
load into account.
As the AFP works with interference matrices, it is limited to coarse estimations of interference combination and loses
knowledge of the geographical location of interference events. It is due to this reason that the interference study output is
much more accurate than the AFP cost.
Figure 5.1: Interference Study Report
The column “Erlangs (based on traffic load)” is available in the interference study report as seen above. This column uses
a traffic model similar to the one used by the AFP:
• It spreads the traffic of each subcell (#TRX x traffic load x # timeslots) on the service zone of the subcell.
• Then, it sums up the interfered traffic (in Erlangs) of each interfered TRX.
This means that it is a TRX based estimation of interference and is much more accurate than any other tool available in
Atoll. In order to be able to use this option, you must check the “Detailed results” option when specifying conditions for an
interference study.
5.1.1.1 Various Interference Studies

Following are the main differences between a TRX based interference study and a transmitter level worst case interference
study.
5.1.1.1.1 TRX Based Interference Study

If there are more than one TRXs per cell, a “TRX based” frequency plan analysis is usually required. This can be performed
in Atoll using the “Detailed results” option of an “Interfered zones” study. The following figures depict this function:
© Forsk 2006 AT250_ARG_E2 47

AFP Reference Guide
Figure 5.2: TRX Based Interference Studies
For each TRX, Atoll retains a map of all the pixels that do not comply with the quality threshold (one map for each TRX).
The threshold can be global or dedicated to each subcell (from the Subcells table). The maps can be visualised by the user
and contribute to the overall statistics. The column mentioned earlier weighs the “bad” surface of each TRX map by the
traffic carried by the TRX as seen by the AFP. Therefore, it is the most appropriate tool for frequency plan interference
evaluation.
5.1.1.1.2 Worst Case Interference Study

A Worst Case Interference study allows generating the Worst C/I (I being the worst interferer) per pixel or per serving trans-
mitter at pixel. Statistics on these maps are available with or without traffic weighting. The principal drawback is that pixels
are coloured in both cases: when 1 out of n TRXs is interfered and when n out of n TRXs are interfered. Moreover, there
is no information about TRXs (channels or frequency) responsible of these worst C/I values.
5.1.1.2 Visualising TRX Ranks with a TRX Based Interference Study

You can also visualise and compare the AFP TRX ranks with the results of a detailed interference study. In the interference
study report table, as shown in the earlier figure, the “Erlangs (based on traffic load)” column should rank the TRXs in the
same order as the AFP TRX ranks. Make sure that the AFP cost is based on interferences and not separation constraints.
In case of large networks, where it might be easier to compare these results using MS-Excel, you might not get a 100%
match between these reuslts and small variations in the order may exist.
5.1.1.3 Visualising C/I Distributions with a TRX Based Interference Study

The figure above and the example below show how to get very detailed information about the various C/I conditions at TRX
level:
The different information seen in this screen shot is part of the report obtained by creating several instances of an interfered
zone study. The interfered zone study whose properties dialog is shown, is the closest to the default configuration. Its in-
terference definition references the subcell quality threshold.
In the two other interfered zones studies, the global threshold for the minimum and maximum TRX C/I to be included in
each TRX’s map were fixed at the reference values. These studies show that there are more “weak interferences” (11.3
Erlangs) than “strong interferences” (6.3 Erlangs). The “weak interferences” being 8 < C/I <= 12 and the strong interference
being C/I <= 7.
48 AT250_ARG_E2 © Forsk 2006

Figure 5.3: TRX Based Interference Study - C/I Distributions
5.1.2 Using Audit

The consistency checking tool gives precise information about separation constraint violations:
• Number of constraints violated

• Types of constraints violated (co-transmitter, co-site, neighbour, special)
• Transmitters and TRXs affected
• Synchronisation, HSN, MAL and MAIO are taken in to account.
The consistency check tool is described in detail in the Atoll User Manual. A quantified summary of separation constraint
violations is available. It makes the evaluation of a frequency plan much easier than before. The section below demon-
strates how this evaluation can be carried out.
5.1.2.1 Global Separation Fitness Expression

It is often interesting to quantify the “amount” of separation violation in a frequency plan. The difficulty in this is that many
different cases and subcases exist. It is not possible to simply count the violating pairs since the SFH violation with low
fractional reuse will affect the count. Another complexity is the difference between co-channel and adjacent-channel vio-
lations. Therefore, a Separation Fitness Expression that tries to assign relative weights to different types of separation vi-
olations is defined. It is composed of 7 separate summations (N1 through N7), each assigned its respective weight. It is
called Forsk Independent Separation Fitness Expression (FISFE) and it is described below.
The FISFE expression is part of our open architecture AFP strategy. There are more than one AFP integrated with the Atoll
platform and, therefore, it is interesting to know the frequency plan FISFE values. The answer must be independent of the
AFP used to generate the plan.
5.1.2.1.1 Forsk Independent Separation Fitness Expression (FISFE)

FISFE ( FP ) = 7.5 × { 0.8 ×N1 + 0.3 × N2 + 0.2 × N3 + 0.1 × N4 + 0.07 × ( N5 – N1 – N2 – N3 – N4 ) + 0.3 × N6 + 0.15 × N7 }
The value “7.5” is arbitrary. It is used to upscale the FISFE(FP) value to “close to Erlang” units. On the other hand, the
weights specified for each component reflect the idea of their relative importance.
N1 through N7 are now available in the summary of the consistency checking tool.
© Forsk 2006 AT250_ARG_E2 49

AFP Reference Guide
5.1.2.1.2 Main Separation Violation Item Summary
• N1 is the number of TRXs subject to a co-channel reuse violation where the separation violation concerns two non
SFH TRXs.
• N2 is the additional number of TRXs subject to an adjacent-channel reuse violation where the separation violation
concerns two non SFH TRXs.
Note: If a TRX is counted in N1 it will not be counted in N2.
• N3 is the additional number of TRXs subject to a co-channel reuse violation where the separation violation con-
cerns two TRX where at least one is SFH.
Note: If a TRX is counted in N1 or N2 it will not be counted in N3.
• N4 is the additional number of TRXs subject to an adjacent-channel reuse violation where the separation violation
concerns two TRX where at least one is SFH.
Note: If a TRX is counted in N1, N2 or N3 it will not be counted in N4.
• N5 is the number of TRXs subject to whatever separation violation that exists.

• N6 and N7 correspond to a different counting system, the pair-wise counting system. N6 and N7 are only used in
cases where the fractional load is less than 1, which means that at least one of the TRXs in the pair is SFH.
The pair-wise violation counting is less important than TRX counting and therefore has a low weight coefficient. On the
other hand, it cannot be ignored, since in 1/1 SFH plans, all TCH TRXs will have violations with neighbours and yet it would
be required to minimize the volume of these violations. N6 and N7 are defined as following:
• N6 is summed over all pairs subject to a co-channel reuse violation, where at least one TRX in the pair is SFH and
where the probability of a burst having a co-channel violation is summed.
• N7 is summed over all pairs subject to an adjacent-channel reuse violation, where at least one TRX in the pair is
SFH and where the probability of a burst having an adjacent-channel violation is summed.
In the following example, the values of N1 through N7 are {0, 23, 62, 35, 123, 7.695, 2}
Figure 5.4: Event Viewer Messages
Figure 5.5: Event Viewer Message 1
Figure 5.6: Event Viewer Message 2
50 AT250_ARG_E2 © Forsk 2006

5.2 Using Point Analysis

It is often useful to know what exactly causes interference conditions at a point. This is one of the important roles of the
point analysis tool. Yet because of it’s complexity, some users are afraid to use it, which is a pity. The point analysis is
complicated only because it is a very rich tool. It provides the user with the information of how are the interferers of a TRX
at a point, what are the different gains (power offsets, burst collision probability, DTX, adjacency suppression), and how
do the different components combine to a “total interference”.
5.2.1 Example 1: Combination of Interference Effects

This figure depicts the case where two adjacent interferences are combined to create total interference (the gain value (the
empty part – 18 dB) shows that they are adjacent). For each of the two adjacent interferers, C/I > 11 dB, while for their
combination, the total interference, C/I < 11 dB. This example demonstrates the fact that geographic interference combi-
nation is more accurate than the interference cost of the AFP. Assuming the required quality to be 11 dB, this specific point
would not contribute to the AFP cost, while it would be considered as interfered in the interference study.
Figure 5.7: Combinatin of Interference Effects
5.2.2 Example 2: Counting Strong Interference Only Once

In this case, two strong interferences are combined to create an extra strong total interference. C/I is very weak for both of
the two interferers. Therefore, the point under analysis contributes to both IM entries, which are considered in the AFP cost.
This example demonstrates the fact that geographic interference combination is more accurate than the interference cost
of the AFP because of counting this point only once as an interfered point (and not twice as in the AFP).
Figure 5.8: Counting Strong Interference Only Once
© Forsk 2006 AT250_ARG_E2 51

AFP Reference Guide
5.3 Uniform Frequency Usage Distribution

A frequency distribution analysis tool is available. This feature is accessible through the Frequency Distribution command
from the Frequency Plan menu in the Transmitters folder context menu. The output of this tool consists of a 3 column table
listing,
• The ARFCN frequency,

• The number of TRXs in which the ARFCN appears
• Its relative load.
The relative load is the same as the number of TRXs if no synthesised hopping is involved. When synthesised hopping
exists, the frequency load is the sum of 1/(MAL size) of all the TRXs using this frequency.
The scope of this tool is the same as the AFP scope.
5.3.1 When Uniform Distribution and Quality do not Coincide

While it is clear that in some cases the frequency usage distribution can be a quality indicator, it is not always the case.
The following two examples prove the same. Therefore, a cost has not been dedicated to non-uniformity of spectral use in
Atoll and thus marking it an “objective” of the AFP. As a result Atoll AFP will create non-uniform frequency distributions in
the following cases:
1. When the FAP is easy, the AFP reaches a 0-cost solution and stops immediately. If it was instructed to use the
minimum possible spectrum, the AFP will use the smaller ARFCNs more than the larger ones (and will leave the
largest ARFCNs untouched, for future use). Otherwise, the AFP will try to spread the spectrum usage. By default
this directive is free for AFP tuning. Therefore, the AFP will not create a uniform frequency usage distribution when
the FAP is easy.
2. If the FAP is somewhat difficult, the frequency usage distribution will be somewhat non-uniform. In order for it to
be uniform, the corresponding directive must be set in the Spectrum tab of the AFP properties dialog.
3. If the FAP is difficult, all frequencies will be used and the allocation heuristics will result in a balanced allocation.
Lastly, when the FAP is extremely difficult (many separation violations, for example), an unbalanced allocation
may result because of the reason explained in chapter VII.1, concerning the fact the AFP cost is a TRX (node)
based cost.
4. AFP can also create non-uniform frequency distributions due to the domain range effects described below.
Advice:
Do not expect a balanced distribution of frequencies in every case. Sometimes the best solution requires an unbal-
anced assignment.
5.3.1.1 Domain Range Effect and Adjacent Constraints

Other sources of unbalanced frequency distribution are the domain range limits. The first and the last frequencies in a do-
main have lesser separation constraints related to them. Consequently, they are used more than other frequencies. The
second and the second last are used less since frequencies adjacent to them are used more and so on. This effect is
stronger for more regular networks. If the domain is small, if ((first – last) / 2) is an integer and if the network is regular, the
AFP may hardly use a part of the spectrum. This will happen if and only if there are many adjacent constraints.
The following example can be interesting:
In a domain of 1 to 7 in a typical hexagon network with 6 neighbours for each transmitter, one solution can be a 1/4 pattern
using only the frequencies 1, 3, 5 and 7, while 2, 4 and 6 will not be used at all. Another solution for the same can be a 1/
7 pattern. Although, if the separation constraints between neighbours are 2, the 1/4 pattern (based on odd number frequen-
cies only) will give a better result.
52 AT250_ARG_E2 © Forsk 2006

Chapter 6
Advanced Topics and Troubleshooting
AFP Reference Guide
54 AT250_ARG_E2 © Forsk 2006

Chapter 6: Advanced Topics and Troubleshooting
6 Advanced Topics and Troubleshooting

6.1 Various AFP Related Features
6.1.1 SFH (HSN, MAL, MAIO)
Atoll AFP is capable of performing free MAL assignment and predefined MAL assignment both. The instruction indicating
the assignment mode to be used is at subcell level. In free assignment mode, the AFP is free to assign any MAL that sat-
isfies the requirements of the TRXs. The length of MAL, the HSNs and the MAIOs are assigned in compliance with the
user’s directives. If the assignment mode is group constrained, the AFP can assign one of the predefined groups in the
domain.
The success of the assignment depends on the definition of groups in the domain. Each MAL length, represented by one
or more groups in the domain, is supposed to fulfil the conditions:
• that there must be a number of other groups having the same length, and
• that on the whole they cover the domain as much as possible.
For example, a domain containing groups of lengths 3, 5 and 8 will be a badly planned domain if there are many groups of
length 3, many of length 8 and only one of length 5.
If restricted to such a domain, the AFP will not produce an optimum plan. On the other hand, by adding a few more groups
of length 5, the quality can be much improved. Another solution could be to simply remove the single group of length 5.
When many groups are defined, the quality is almost as good as with free assignment.
Notes:
1. Currently, the AFP always assigns the same MAL to all TRXs within a subcell.
2. The “group constrained” assignment mode is applicable for SFH only. In NH and BBH, the assignment
mode is always free.
6.1.2 Definition of Atom

An atom is a set of synchronised subcells that share the same HSN, the same frequency domain and have the same length
MAL. The MAIO assignment of an atom manages the frequency collisions between the MALs of the atom. If an atom con-
tains more than one subcell, the AFP may assign to it partially different MALs (depending on a user-definable option) but
it will always consider the fact that the subcells are synchronised. Atoms can be determined by the user or by the AFP via
the HSN allocation. Some restrictions on this definition exist due to some extreme cases:
1. If two subcells have different domains, they cannot belong to the same atom.
2. If two subcells have different limitations on “Max MAL Length”, they cannot belong to the same atom.
A warning is generated when HSN assignment directives contradict with these restrictions.
An important feature is the possibility to force the AFP to always assign the same MAL among subcells of an atom. Fur-
thermore, improved results can be obtained by post-relaxation of this constraint, performed on a carefully selected and
small subset of transmitters.
6.1.3 Synchronous Networks

Through working at atom level, and consulting a user defined synchronisation reference given in the subcell table, the AFP
can fully exploit the benefits of synchronisation in a GSM network. It is capable of extending Atoms beyond the limit of a
site and, by doing so, using the MAIO assignment to further resolve violations or interference.
6.1.4 Optimising Hopping Gains

If the AFP has a certain degree of freedom when choosing MAL lengths, it may opt for longer MAL lengths. In this way, it
can profit more from the hopping gains. On the other hand, it may be increasingly hard to find frequencies for these MALs.
6.1.5 Fractional Load

Both HSN assignment and MAL length determination processes are tuned to obtain a user defined fractional load. A frac-
tional load of δ is obtained if the number of TRXs using a certain MAL is only δ times the size of the MAL. Atoll’s notion of
fractional load does not require the traffic load to be taken into account.
© Forsk 2006 AT250_ARG_E2 55

AFP Reference Guide
Since fractional load cannot always be obtained, this parameter is considered as a guide rather than a constraint. When it
can be obtained, AFP chooses either a MAL length 1/δ times longer than the number of TRXs in the biggest subcell of the
atom or a MAL length 1/δ times longer than the sum of all TRXs in the atom. These are called “the short MAL strategy” and
“the long MAL strategy” respectively. The user can choose between the two in the MAL tab of the properties dialog. The
value of the fractional load parameter can also be edited and, furthermore, it can even be automatically calibrated by the
AFP.
Note: Fractional load is 1 for Baseband hopping.
6.1.6 Domain Use Ratio

Both HSN assignment and MAL length determination processes are tuned to avoid exceeding a user defined Domain Use
Ratio. Domain Use Ratio is the MAL length divided by the total number of frequencies in the domain. For example, a 1/1
reuse pattern has a frequency reuse ratio of 1. A 4/12 reuse pattern can have a reuse ratio between 1/4 and 1/12, depend-
ing on whether all TRXs in a site have the same MAL (and HSN) or not.
6.1.7 User Defined MAL Length

The MAL length has an upper limit defined in the “Max MAL length” parameter of the subcell table. The user can instruct
the AFP to strictly use this value.
6.1.8 HSN Allocation

The AFP assigns HSNs at subcell level. It chooses different HSNs for interfering and non-synchronous subcells. For syn-
chronous subcells (usually within a site), the AFP can opt to assign the same HSN and different MAIOs within the set of
same-HSN subcells.
According to the adapted convention on HSNs for BBH TRXs, the AFP allocates different HSNs to the BCCH TRX and
TCH TRXs. The 1st HSN corresponds to timeslots 1 through 7 of the BCCH and TCH TRXs, and the second HSN corre-
sponds to the timeslot 0 of the TCH TRXs only. The second HSN is used in studies.
Figure 6.1: Hopping Sequence Numbers
The user can control the HSN allocation so that it performs one of the following:
• Assigns the same HSN to all subcells of a site

• Assigns the same HSN to all subcells of a transmitter
• Assigns pair-wise different HSNs if a pair of subcells has mutual interference.
• Optimise HSN assignment so that the frequency assignment is better (free HSN).
6.1.9 MAIO Allocation

The AFP assigns MAIOs to TRXs so that the same MAL can be reused within a subcell, within a transmitter or even within
a site. The separation requirements must be satisfied for frequencies that are on air, at all frame numbers. The cost func-
tion averages the cost upon all frame numbers in the synchronised case and upon all collision probabilities in the non-syn-
chronised case. See Appendix 1 for details.
6.1.9.1 Staggered MAIO Allocation

Checking this option restricts the AFP to allocate a MAIO set represented by 3 numbers: {First, step, total Number}. For
example:
• {17, 85} OK, Step is 68

• {2, 3, 4, 5} OK. Step is 1
• {2, 3, 5} Not OK, 4 is missing
• {2, 4, 6} OK. Step is 2
56 AT250_ARG_E2 © Forsk 2006

6.1.10 BSIC Allocation

Atoll AFP allocates BSICs according to two criteria, a soft criterion and a hard criterion. Not respecting the hard criterion
is considered an error, while not respecting the soft criterion provokes a warning. The soft constraints are logically stronger,
meaning these have a higher probability of not being satisfied. The hard criterion is easier to satisfy but must not be broken
as it will cause handover failures. The hard criterion is based on the second order neighbour relation and BCCH co-channel
reuse. The soft criterion uses interference information as well and tries to induce a larger [BSIC, BCCH] reuse distance.
Appendix 4 details the new algorithm and both criteria.
The BSIC allocation is compliant with the BSIC domains of transmitters and the strategy indicated in the BSIC tab of the
AFP module property dialog. Either the algorithm selects a minimum number of BSICs in the related BSIC domain (Minimal
option), or it chooses as many BSICs as possible while keeping them evenly distributed in the related BSIC domain (Max-
imal and homogeneous option).
Notes:
1. In the Atoll AFP, the directions of neighbour relations are all considered equivalent, so that the BSIC alloca-
tion is subject to harder constraints. Let us consider the following two examples:
A A
N N N N
B C B C
1st case: B and C neighbours of A 2nd case: A neighbour of B and C
From the operational point of view, the first case is much more critical in terms of (BSIC, BCCH) collision.
However, both cases are considered as violations of hard constraints by the AFP and error messages are
generated (if the domain limitation provokes violations).
2. The soft criteria add additional constraints due to interference and adjacent reuse between BCCH chan-
nels. Warning messages are generated when soft criteria are not fulfilled.
3. Atoll AFP also considers Training Sequence Code collisions for synchronous networks. The AFP tries to
avoid having the same TSC when interference exists (i.e. TCH interference, not only BCCH reuse).
6.1.11 Robustness of Atoll AFP

There are three main checks to avoid corrupt data entries and illegal data manipulations in Atoll:
• The first is available in the GUI and protects Atoll’s tables from NULL and out of range values, non-existing refer-
ences and other inconsistencies. The deficiency of these checks is that these can be partially bypassed by auto-
mated import procedures and external database manipulations.
• The second comprises Network Validation processes as described in the User Manual. The setback of this check
is that the user can ignore it altogether.
• The third check is available when launching the AFP. As the AFP puts together information collected from many
different sources, it is quite possible that some elements be conflicting and/or missing. Before launching the AFP,
a validation process is launched that controls the possibility to launch the AFP.
If possible, missing / incorrect data are changed and default values are used (with warnings for each in the Event viewer).
If any serious problem is detected, an error message appears and access to the AFP is denied. The table below lists the
most common data limitations enforced in order to protect the frequency planner.
6.1.11.1 Value Ranges and Limitations at Validation

Limitation Value Comments
Maximum number of subcells in the loaded part of
1,000,000
the network
Highest possible HSN 63
Lowest possible HSN 0
Limitation on the number of different frequency Each exclusion of frequencies at a transmitter may create a new
10,000
domains domain
Highest possible BSIC 77
Lowest possible BSIC 0
So that with the BCCH frequency there are not more than 63
Longest possible MAL length 62 frequencies in a list to avoid exceeding the 255 character limit in
Access.
Shortest possible MAL length 0
© Forsk 2006 AT250_ARG_E2 57

AFP Reference Guide
Default Max MAL length 62 Used if the parameter is out of range.

Interference calculations are performed for co-
If separation <= 1 Performance
channel and adjacent interference only.
Highest frequency ARFCN 1024
Maximum required channels at a subcell 62
Highest value of AFP weight 100
Lowest value of AFP weight 0
Default value of AFP weight 1 Used if the parameter is out of range.
Highest value of Traffic Load 10
Lowest value of Traffic Load 0.1
Default value of Traffic Load 0.1 / or 1 if the field is NULL. Used if the parameter is out of range.
Highest value of “% max interference” 100 Appears in subcell and cell type configuration tables.
Lowest value of “% max interference” 1 Appears in subcell and cell type configuration tables.
Used if the parameter is out of range. (The parameter appears
Default value of “% max interference” 2
in subcell and cell type configuration tables).
Highest value of “min C/I” 25
Lowest value of “min C/I” 2
Default value of “min C/I” 12 Used if the parameter is out of range.
Maximum power offset 25
Highest value of “Reception threshold” -50
Lowest value of “Reception threshold” -116
Default value of “Reception threshold” -94 Used if the parameter is out of range.
Limitation on separation requirements Must be <= 7 Will be eliminated in the future.
Limitation on the actual number of TRXs in a
50
transmitter
Limitation on the number of interfering and
1000
neighbour subcells
6.2 Managing Consistency in Atoll and the AFP

Atoll can generate many prediction studies, some of which can be used to analyse the AFP results. In each case, it is the
task of the user to ensure consistency between the prediction study settings and the AFP settings.
6.2.1 Service Zone of a Subcell

To render flexibility, optimised storage, validity checking and backward compatibility, each of the following Atoll processes
has its own definition of service zone:
1. Neighbour allocation
2. Network dimensioning
3. Prediction studies
4. Interference calculation
To avoid confusion, it is recommended that the user be aware of service zone model being used. In fact, the user should
decide a unique service zone definition to use throughout a project.
Advice:
Before running the AFP, select the definition of the service zone to use for the AFP and all Atoll prediction studies
intended for AFP results analysis.
6.2.1.1 Specifying Correct Interference Study Coverage Criteria

The AFP reads required interference information from either calculated or imported interference histograms. For interfer-
ences calculated by the AFP, the service zone is determined by the minimum reception level found in the Subcells table,
and by the option, “all servers” / “best server”. Atoll interference study has a wider range of options to determine the service
zone. A small service zone in the AFP interference calculation and a large one in the Atoll interference study will imply
great amount of interferences in the interference study, even if the AFP had declared the cost to be 0.
Moreover, for imported interference matrices, there is no means to check whether the imported files are a complete source
of information. The user could very well calculate interference matrices for a part of the network, export it, and later import
it as interference data for the entire network. This would result in an interfered frequency plan.
58 AT250_ARG_E2 © Forsk 2006

Advice:
1. Check that the options in the Atoll interference study are consistent with the AFP interference calculation
settings.
2. Verify that the small IM report does not indicate the existance of many non-interfered transmitters.
3. If AFP interferences have been imported, check that they are consistent with the service zone of Atoll inter-
ference study.
6.2.1.2 Selecting “All servers” or “Best Server” Service Zone

Except neighbour allocation, all other calculations and processes allow choosing their service zone models through the
options “All” or “Best server” with a margin. It is important to understand the difference between these options and why
these options exist in Atoll.
The “All servers” option implies that a transmitter is assumed to serve the region where its signal is stronger than a mini-
mum reception threshold. This means that more than one transmitter can be serving a given point. The service zone is
based on the minimum reception level “C”.
The “Best server” option implies that a transmitter is assumed to serve the region where its signal is the strongest among
all signals stronger than a minimum reception threshold. In other words, where C/N > 0 (C being reception level and N
being the strongest neighbour reception level). If a margin M is defined, then the condition translates to C/N > – M. There
may be more than one serving transmitters at a point but only one best server.
By tuning the minimum reception level and the margin value, any desired server overlapping can be achieved. Large over-
laps will result in a denser interference relation, more neighbours and a rather pessimistic analysis of C/I levels or interfer-
ences. It might be interesting to manipulate the overlapping zones study and the coverage by transmitter study to
determine the correct service zone model.
Coming back to the question of choosing between the two models, since both “C” and “N” values contain errors, the better
model would be the one with the least error. The choice depends on the correlation between the errors in “C” and in “N”. If
these errors are geographically correlated, the “C/N > – M” model should be preferred. Moreover, the error in “C” and the
one in “N” are not evenly distributed: the further you are from the site, the bigger the error is. Therefore, when “N” is much
stronger than “C” it is probably more reliable as well. For these reasons, it is recommended to use the “C/N > – M” model.
As a final argument, it should be kept in mind that the C/N > – M model is bound by the C model.
Advice:
Use a "Best server with margin" coverage study as service zone for both AFP and Atoll studies dedicated to analyse
AFP results.
The fact that “C/N > – M” is bounded by the “C” model might incur misunderstandings. For example, increasing the margin
will not essentially increase the service zone, but change nothing because service zones are limited by coverage and not
by other best servers.
Note: For simplicity, hierarchical layers have been ignored in this discussion.
6.3 Event Viewer

The AFP outputs various messages in the Event viewer. For example, when it finds a zero cost solution, when it stops
because of a data problem or when it finishes without improving. The events, warnings and errors may be helpful in un-
derstanding the AFP behaviour, especially when a problem occurs.
6.4 Interference Study Quality Criteria

The AFP uses the quality specified in the data model (min C/I field in the subcell table). In Atoll interference study, there is
a wider range of quality criteria determination. To assess a frequency plan quality in accordance with AFP calculations,
ensure that the interference study quality threshold has been specified accordingly (use subcell C/I threshold as study set-
ting).
Advice:
Select "Subcell min C/I threshold" instead of "Specified min threshold" in the Atoll interference study Condition tab.
6.5 Calculation Zone Border Effect

If a calculation zone is used to geographically select a set of transmitters for assignment. The following problem will occur
without the user being aware of it:
© Forsk 2006 AT250_ARG_E2 59

AFP Reference Guide
Since the calculation zone limits the influence area in the interference studies (and IM calculation), all subcell service zones
are, therefore, limited to the calculation zone. Hence, the transmitters at the borders will have very small service zones. All
of the traffic corresponding to these transmitters will be considered as if concentrated in these few pixels and their interfer-
ence matrix entries will be calculated so.
Advice:
Use a focus zone inside the calculation zone in order to focus the study on properly modelled transmitters. Preferably,
use calculation zones that are geographically isolated. See the example below:
6.6 Frequency Planning Techniques

6.6.1 Basics
For any network and any amount of available time, fill in the target computation time field to instruct the AFP to behave
according to its default and basic allocation strategy.
6.6.2 Post-processing of Hot Spots

Assuming X hours of available computation time, the strategy is as following:
• Launch the AFP during X * 30 minutes (half of the time), then stop it and commit the results (if good).
• Freeze all TRXs in the network.
• Find the areas that generate problems. For example, some sites with separation violations.
• Unfreeze the worst 10 sites.
• For each such site, unfreeze 2 – 4 neighbouring transmitters.
• Run the AFP for an additional X * 30 minutes (the remaining half of the time).
AFP is also capable of committing cell level and TRX level quality indicators into the data structure. This makes the selec-
tion of hot spots a much easier task.
6.6.3 Learning the Network and Solving for Hot Spots

• Apply this technique to networks having 4000 to 40000 Erlangs (500 to 5000 TRXs).
• Run the AFP for at least 10 solutions, specifying a short time period.
• Find the areas that generate problems. For example, some sites with separation violations.
• Create a calculation zone around these areas (referred to as the network core).
• Make sure that this network core is not too big or too small. For example: 100 to 150 transmitters, in one chunk, if
possible. The network core should not be too small because it is representative of the entire network.
• Specify a long execution time (1000 to 5000 minutes) and let the AFP work on the core over a weekend.
• Commit the plan and run the AFP on entire network. Specify a short time (between 5 and 40 minutes) but let the
AFP run for a long time (a night if possible, to get at least 50 solutions).
• Optional: You can freeze the network core before this last AFP execution.
60 AT250_ARG_E2 © Forsk 2006

Chapter 7
Appendices
AFP Reference Guide
62 AT250_ARG_E2 © Forsk 2006

Chapter 7: Appendices
7 Appendices
7.1 Appendix 1: Description of the AFP Cost Function
7.1.1 Notations
The notations listed hereafter are used to describe the cost function:
• TRG denotes a group of TRXs.

• # is used instead of “number of”. For example, # TRXi is the number of TRXs in TRGi.
• “⇔” denotes the relation “if and only if”.
• g denotes the size of any group g.
ARFCN
• ARFCN denotes the set of all the frequencies, and 2 the set of all the subsets of frequencies.
• “TRGs” denote the set of all the TRGs.
• x denotes the largest integer ≤ x (x can be a real number).
ARFCN
• A i, g denotes the number of times a group g ∈ 2 is assigned to TRGi in the assignment A.
For example:
- When i is NH, A i, g = 1 ⇔ g is a single member group containing one of the frequencies assigned at TRGi.
If |g| is not 1 or if g does not contain a frequency assigned at i, then A i, g = 0 .
- When i is BBH, A i, g can be either 0 or #TRXi.
A i, g = #TRX i ⇔ g is the set of frequencies assigned to TRXs of TRGi. (|g| = # TRXi).
When we talk about “TRXs of i using g”, and in the case of BBH, then there are |g| such virtual TRXs, each using the entire
group g and having a virtual MAIO [0, |g| - 1].
- When i is SFH, A i, g must be ≤ #TRX i . A i, g = n ⇔ g is the set of frequencies assigned to n TRXs of TRGi.
We assume all the groups assigned to TRGi to have the same length.
• TSi denotes the number of timeslots available for each TRX in TRGi.
• TLi is the traffic load of TRGi. This parameter may either be calculated during dimensioning or be user specified.
TL i = #Erlangs of a single TRX in TRGi divided by TSi
• TSUi refers to the downlink timeslot use ratio (due to DTX) at TRGi.
• CFi is the cost factor of TRGi (AFP Weight field).
• QMINi is the minimum required quality (in C/I) at TRGi.
• PMAXi is the percentage permitted to have quality lower than QMINi at TRGi.
• REQi corresponds to the required number of TRXs at TRGi.
A communication uses the group g in TRGi if its mobile allocation is g. The probability to be interfered is denoted by
P i, i', g ( A ) (i’ is the TRX index). Different TRX indexes may have different MAIOs. P i, i', g ( A ) is a function of the whole fre-
quency assignment. The precise definition of the term “to be interfered” is provided afterwards. The probability penalty due
to violating a separation constraint is P i, i', g ( A ) . It is a function of the whole frequency assignment as well.
The term “Atom” will be used in the following context:
For two TRGs, i and k,
ATOM ( i ) ≡ ATOM ( k ) i and k are synchronised, have the same HSN, the same MAL length and the same hopping mode.
NH TRGs or BBH TRGs are always in separate atoms. If two TRGs interfere but are not in the same atom, these can be
taken as unsynchronised. The quality of unsynchronised TRGs is a function of all possible frequency combinations. For
synchronised TRGs, pairs of frequencies emitted at the same time are known.
© Forsk 2006 AT250_ARG_E2 63

AFP Reference Guide
7.1.2 Cost Function

The Atoll AFP cost function is a TRX based cost and not an interference matrix entry based cost. It counts the impaired
traffic of the network TRXs in weighted Erlangs.
The cost function Ψ is reported to the user during the AFP progress with the help of its 5 components: Ψ mis , Ψ sep ,
Ψ comp , Ψ corr and Ψ dom .
Ψ = Ψ mis + Ψ sep + Ψ comp + Ψ corr + Ψ dom
where,
Ψ mis represents the missing TRX cost component
Ψ sep represents the separation component
Ψ comp represents the additional cost component (interference, cost of changing a TRX)
Ψ corr represents the corrupted TRX cost component
Ψ dom represents the out-of-domain frequency assignment cost component
Note: Do not let this form of representation mask the fact that the cost function is a TRX based cost function.
Ψ mis = ∑ ( MIS_TRX i × λ ) × TL i × CF i × TS i
i ∈ TRGs
Ψ corr = ∑ ( CORR_TRX i × Ω ) × TL i × CF i × TS i
i ∈ TRGs
Ψ dom = ∑ ( DOM_TRX i × ω ) × TL i × CF i × TS i
i ∈ TRGs
⎛ ⎞
⎜ ⎟
⎜ ⎟
⎜ δ' i, i', g ( A )⎟ × TL i × CF i × TS i
Ψ sep = ∑ ⎜ ∑ ⎟
i ∈ TRGs ⎜ ⎟
⎜ g∈2
ARFCN
⎟
⎝ i' ∈ TRXs of i using g ⎠
⎛ ⎞
⎜ ⎟
⎜ ⎟
⎜ δ'' i, i', g ( A )⎟ × TL i × CF i × TS i
Ψ comp = ∑ ⎜ ∑ ⎟
i ∈ TRGs ⎜ ⎟
⎜ g∈2
ARFCN
⎟
⎝ i' ∈ TRXs of i using g ⎠
In the above equations,
• i’ is the TRX index belonging to { 0, 1, ..., A i, g – 1 } .

• MIS_TRX i is the number of missing TRXs for the subcell i.
MIS_TRX i = MAX 0, REQ i – ∑ A i, g

ARFCN
g∈2
• λ is the cost value for a missing TRX. This value can vary between 0 and 10. The default cost value is set to 1 and
can be modified in the AFP module properties dialog.
• CORR_TRX i is the number of corrupted TRXs for the subcell i.
• Ω is the cost value of a corrupted TRX. This value can vary between 0 and 10. The default cost value is set to 10
and can be modified in the AFP module properties dialog.
• DOM_TRX i is the number of TRXs, for the subcell i, having out-of-domain frequencies assigned.
• ω is the cost value of a TRX with out-of-domain frequencies assigned. This value can vary between 0 and 1. The
default cost value is set to 0.5 and can be modified in the AFP module properties dialog.
64 AT250_ARG_E2 © Forsk 2006

And, as mentioned earlier, a virtual TRX is considered in case of BBH.
If i’ is valid, the algorithm evaluates the cost of a valid TRX. This cost has two components, δ' i, i', g ( A ) and δ'' i, i', g ( A ) .
• δ' i, i', g ( A ) is the separation violation probability penalty.

• δ'' i, i', g ( A ) is complementary probability penalty due to interference and the cost of modifying a TRX.
If the option “Take into account the cost of all the TRXs” available in the AFP module properties dialog is selected, then,
δ' i, i', g ( A ) = P' i, i', g ( A ) and δ'' i, i', g ( A ) = P'' i, i', g ( A )
Or if the option “Do not include the cost of TRXs having reached their quality target” available in the AFP module properties
dialog is selected, the algorithm compares P' i, i', g ( A ) + P'' i, i', g ( A ) with the quality target specified for i, P MAX :
If P' i, i', g ( A ) + P'' i, i', g ( A ) > P MAX ,
Then δ' i, i', g ( A ) = P' i, i', g ( A ) and δ'' i, i', g ( A ) = P'' i, i', g ( A ) .
Otherwise,
Both δ' i, i', g ( A ) and δ'' i, i', g ( A ) will be equal 0.
P' i, i', g ( A ) is the same as δ' i, i', g ( A ) (separation violation probability penalty) and P'' i, i', g ( A ) the same as δ'' i, i', g ( A ) (com-
plementary probability penalty due to interference and the cost of modifying a TRX) in most cases. These are explained in
detail in the next sections.
7.1.3 Cost Components

Separation violation and interference cost components are described hereafter. Parameters considered in the cost func-
tion components can be fully controlled by the user. Some of these parameters are part of the general data model (quality
requirements, percentage of interference allowed per subcell), while others (such as separation costs and diversity gains)
can be managed through the properties dialog of the Atoll AFP module.
7.1.3.1 Separation Violation Cost Component

The separation violation cost component is evaluated for each TRX. Estimation is based on costs specified for the required
separations.
Let SEP_CONSTRi, k denote the required separation constraint between TRGi and TRGk. Let Cost s, z denote the user
defined separation penalty for a required separation “s” and actual separation “z”. SEP i, k, v is used instead of
Cost SEP_CONSTR as abbreviation.
i, k, z
Note: The AFP module properties dialog takes probability percentages as inputs while this document deals in
probability values.
ξ ii'kgg'k' is considered to be the effect of a separation violation on the i' th TRX of TRGi assigned the group g, caused by
the k' th TRX of TRGk assigned the group g' .
γ denotes the overall weight of the separation violation cost component. This value can be between 0 and 1, set to 1 by
default. It can be modified in the AFP module properties dialog.
γik represents the weight of the specific separation constraint between i and k. This specific weight depends on the type
of separation violation and follows the following priority rule:
• Exceptional pairs
• Co-transmitters
• Co-site
• Neighbours
For example, if a pair of subcells are co-site and neighbours at the same time, they will be considered as co-site because
higher priority. Hence, γik of these subcells will be the weight of co-site relations. If only a neighbour relation exists be-
tween two subcells, then γik will be further weighted by the neighbour relation importance. The value of γik remains be-
tween 0 and 1. The default weights of each type of separation are available in the Separation cost tab.
© Forsk 2006 AT250_ARG_E2 65

AFP Reference Guide
If ATOM ( i ) ≠ ATOM ( k )
∑ SEP i, k, f – f'
f∈g
f' ∈ g'
Then ξ ii'kgg'k' = γ × γik × --------------------------------------------- , which is same for all values of k.
g × g'
If ATOM ( i ) = ATOM ( k )
∑ SEP i, k, g υ – g' τ
f_n ∈ { 0, 1, ..., F_N – 1 }
Then ξ ii'kgg'k' = γ × γik × -----------------------------------------------------------------------------------
-
F_N
In the above equations, F_N ( g ) is the number of frames in the MAL g. F_N ( g ) = g .
Note: Since F_N ( g ) = F_N ( g' ) , we shortly denote the two as F_N .
Let f_n denote the instantaneous frame number from 0 to F_N .
th
While υ = ( f_n + MAIO A ) modulo F_N and g υ is the υ frequency in g,
i, g, i'
th
And τ = ( f_n + MAIO A ) modulo F_N and g' τ is the τ frequency in g’.
k, g', k'
In addition, frequencies belonging to a MAL with a low fractional load, and breaking a separation constraint, should not be
weighted equally as in a non-hopping separation breaking case. Therefore, the cost is weighted by an interferer diversity
gain.
ˆ 1
G i, k, g, g' = -------------------------------------------------------------------
( 0.1 × SEP_GAIN ( i, k, g , g' ) )
-
10
The separation gain, denoted by SEP_GAIN ( i, k, g , g' ) is basically a function of the MAL length (and, of course, of the
hopping mode). With frequency hopping, the effects of DTX and traffic load become more significant (due to the consider-
ation of the average case instead of the worst case). For this reason, it is possible to consider these effects in
SEP_GAIN ( i, k, g , g' ) through the relevant option available in the Advanced tab of the AFP module properties dialog.
Without this option, the SEP_GAIN ( i, k, g , g' ) is:
SEP_GAIN ( i, k, g , g' ) = I_DIV ( g )
I_DIV ( g ) is the user defined interferer diversity gain (dB) for a given MAL length. It is used in P i, i', g ( A ) definition as well.
On the other hand, if this option is selected, the SEP_GAIN ( i, k, g , g' ) becomes,
( 2 + ASYN_GAIN ( i, k, g' ) )
SEP_GAIN ( i, k, g , g' ) = I_DIV ( g ) +⎛0.5 × TSU_GAIN ( k ) × min ⎛ 10, 4 + ⎛ ( 2 + I_DIV ( g ) ) × ------------------------------------------------------------------------⎞ ⎞ ⎞
⎝ ⎝ ⎝ 4 ⎠⎠⎠
1
Where TSU_GAIN ( k ) = log 10 ⎛ -------------------------------⎞ ,
⎝ TL k × TSU k⎠
And ASYN_GAIN ( i, k, g' ) = 0 if ATOM(i) = ATOM(k)

I_DIV( g' ) Otherwise
ˆ
More than one separation violations may exist for a TRX. Many “small” G i, k, g, g' and ξ' ii'kgg' have to be combined to form
one cost element, the P' i, i', g ( A ) . This is done through iterating over all violating assignments and by summing up an equiv-
alent to the probability of not being violated while considering each separation violation as an independent probability
event. This sum is naturally limited to 100% of the TRX traffic, and is given by,
66 AT250_ARG_E2 © Forsk 2006

⎛ ⎞
⎜ ˆ ⎟
⎜1 –
⎜
∏ ( 1 – ξ ii'kgg'k' × G i, k, g, g' ) ⎟
⎟
P' i, i', g ( A ) = ⎜ ⎟
k ∈ TRGs
⎜ ⎟
⎜ g' ∈ 2
ARFCN
⎟
⎜ k' ∈ TRXs of k using g' ⎟
⎝ ⎠
In the above formula, if ( k = i ) , then ( k' ≠ i' ) , so that interference with itself is not taken into account.
7.1.3.2 Interference Cost Component

The interference cost component is evaluated for each TRX. Its estimation is based on interference histograms calculated
for pairs of subcells. In addition, it takes into account frequency and interferer diversity gains and models frequency hop-
ping and gain due to DTX.
Note: Interference histograms are described in User Manual (GSM GPRS EGPRS project management, GSM
GPRS EGPRS network optimisation, GSM GPRS EGPRS generic AFP management). Interference histo-
grams can also be exported to files. For further description, refer to chapter Appendix 2: Interferences of
this document.
When estimating P'' i, i', g ( A ) , the following problems are encountered:
• The QMINi C/I quality indicator corresponds to the accumulated interference level of all interferers while the C/I
interference histograms correspond to pair-wise interferences.
• Both QMINi and the histograms correspond to a single frequency. In case of a MAL containing more than one fre-
quencies, interferences on several different frequencies of a MAL must be combined.
This estimation, presented below, is the simplest possible as it solves the first problem by linear summation and truncation
at the value of 1 and it solves the second problem by averaging and adding the two diversity gains:
• F_DIV ( g ) , the frequency diversity gain, and

• I_DIV ( g ) , the interferer diversity gain.
Hereafter, α denotes the global weight of interference cost component. This value can vary between 0 and 1 and is set to
0.35 by default, which can be modified in the AFP module properties dialog.
Let F_N ( g ) be the number of frames in the MAL g. F_N ( g ) = g .
Let f_n denote the instantaneous frame number from 0 to F_N .
Let MAIO A be the j’th MAIO of A k, g' , where j is one of the { 0, 1, ..., A k, g' – 1 } TRXs.
k, g', j
The value of MAIO A is one of { 0, 1, ..., g' }

k, g', j
If TRGk is NH, then MAIO A = 0.

k, g', j
If TRGk is BBH, then MAIO A = j.

k, g', j
As said earlier, in case of BBH, we consider g' virtual TRXs, the jth TRX has the MAIO j.
Let g i be the ith frequency in the group g.
Similar to the definition of ξ ii'kgg'k' , ξ' ii'kgg'k' is defined as an interference event. ξ' ii'kgg'k' is the effect interference on the
i' th TRX of TRGi assigned the group g, caused by the k' th TRX of TRGk assigned the group g' .
If ATOM ( i ) ≠ ATOM ( k )
C
Probability ⎛ ----- < Q_UB i, k, f, f'⎞
⎝ I ik ⎠
Then ξ' ii'kgg'k' = ∑ --------------------------------------------------------------------------------
g × g'
f ∈ g, f' ∈ g'
Where Q_UB i, k, f, f' = QMIN i – f – f' × ADJ_SUP + INTERF_GAIN ( i, k, g , g' )
© Forsk 2006 AT250_ARG_E2 67

AFP Reference Guide
If ATOM ( i ) = ATOM ( k )
Then,
Since F_N ( g ) = F_N ( g' ) , these are both represented by F_N .
C
⎧ Probability ⎛ ----- < Q_UB i, k, f, f'⎞ ⎫
⎪ ⎝ I ik ⎠⎪
ξ ii'kgg'k' = ∑ ⎨ -------------------------------------------------------------------------------
⎪ F_N
-⎬
⎪
f_n ∈ { 0, 1, ..., F_N – 1 } ⎩ ⎭
Where,
f = gυ ,
f' = g' τ ,
υ = ( f_n + MAIO A ) modulo F_N ,

i, g, i'
τ = ( f_n + MAIO A ) modulo F_N ,

k, g', k'
Q_UB i, k, f, f' = QMIN i – f – f' × ADJ_SUP + INTERF_GAIN ( i, k, g , g' )
⎧ ⎫
⎪ ⎪
⎪ ⎪
⎪ ⎪
Therefore, we have, P'' i, i', g ( A ) = 1 – ⎨ ( 1 – P' i, i', g ( A ) ) ×
⎪
∏ ( 1 – ξ ii'kgg'k' ) ⎬ – P' i, i', g ( A )
⎪
⎪ ⎪
⎪ k ∈ TRGs ⎪
⎩ g' ∈ 2
ARFCN ⎭
k' ∈ TRXs of k using g'
In the above formula, if ( i = k ) , then ( k' ≠ i' ) , so that interference with itself is not taken into account.
The sum is limited to 100% of the TRX traffic. INTERF_GAIN ( i, k, g , g' ) is quite similar to SEP_GAIN ( i, k, g , g' ) . The
only difference is the frequency diversity gain, F_DIV ( g ) , added to SEP_GAIN ( i, k, g , g' ) .
7.1.4 I_DIV, F_DIV and Other Advanced Cost Parameters

When combining interference effects (or separation violation effects) on different frequencies belonging to a MAL, the fol-
lowing considerations should be taken into account:
1. Non-linearity of Frame Error Rate (FER) with respect to average C/I conditions and MAL length.
2. Interference Diversity Gain. This factor represents that the effect of average negative effects over user geographic
location are directly proportional to the MAL length.
3. Frequency Diversity Gain. This factor models the gain due to diversity of multi-path effects and should be applied
to the interference cost component only.
4. The fact that long MALs with synthesized hopping permit discarding the worst case estimation and include a gain
due to DTX and low traffic load at the interferer end.
The Advanced properties tab shown in the figure below facilitates modelling these effects.
The Interference Diversity Gain table lists the values of I_DIV provided as a functions of MAL length. This gain is applied
to the interference cost component and to the separation constraint violation cost component. Therefore, it provides a
means to model the non-linear FER effects and interference diversity both. The default values in this table correspond to
the curve y = 2 × log 10 ( x ) . This equation generates values somewhat lower than empirical best-found values (this is be-
cause we prefer a slightly pessimistic cost function to be on the safe side).
The other table contains the F_DIV values, which are the same as the I_DIV values by default.
68 AT250_ARG_E2 © Forsk 2006

Figure 7.1: Atoll AFP Module Properties - Advanced Tab
© Forsk 2006 AT250_ARG_E2 69

AFP Reference Guide
7.2 Appendix 2: Interferences

In the Technical Reference Guide, Chapter 7.8 (File Formats: Interference Histogram Formats), there is a detailed descrip-
tion of the Atoll’s interference representation. The User Manual contains additional descriptions of interference usage: im-
porting, calculating, keeping up-to-date etc. This appendix explains what is carried out at high level.
7.2.1 Using Interferences

If interferences are to be taken into account by the AFP, they must be calculated or imported beforehand (Step 2 in the
AFP dialog, see Chapter II.4). In order to do this, the user should previously decide to take interferences into account (en-
abling the loading of all the potential interferers). Otherwise, Atoll does not allow performing their computation by disabling
the histogram part in the corresponding dialog.
7.2.2 Cumulative Density Function of C/I Levels

For each [interfered subcell, interfering subcell] pair, Atoll calculates a C/I value on each bin of the interfered subcell serv-
ice area (as if the two subcells share the same channel). Then, Atoll integrates these C/I values to determine a C/I distri-
bution and transforms this distribution function into a cumulative density function in the normal way.
In Atoll, both the IMco and IMadj are represented by this Cumulative Density function This implies that each query for the
probability to have C/I conditions worse than X dB requires a single memory access: the co-channel interference probabil-
ity at X dB. In order to deduce the adjacent interference probability value, Atoll looks up the cumulative density function at
the value corresponding to X - Y dB, Y dB being the adjacency suppression value. The following example may be helpful
in further clarifying this concept:
Example: Let [TX1, BCCH] and [TX2, BCCH] be the interfered and interfering subcells respectively. The service areas for
both have been defined by Best Server with 0 dB margin. The interference probability is stated in percentage of interfered
area.
Figure 7.2: The cumulative density of C/I levels between [TX1, BCCH] and [TX2, BCCH]
In this case, we observe that the probability for C/I (BCCH of TX2 effecting the BCCH of TX1) being greater than 0 is 100%
(which is normal because TX1 is the Best Server). The probability of having a C/I value at least equal to 31 dB is 31.1%.
For a required C/I level of 12 dB on the BCCH of TX1, the interference probability is 6.5% (as this requirement is fulfilled
with a probability of 93.5%).
Note: The subcell power offset does not enter the calculation results in the .clc file. It is added later by the AFP
interface. On the other hand, its influence on the subcell service zone is taken into account in the .clc file.
7.2.3 Precise Definition

Pci ( v, n, C_I ) is defined to be the probability of a communication (call) occupying a timeslot in subcell v (victim) to have
C/I conditions of C_I with respect to a co-channel interference from the BCCH TRX of cell n (neighbour). We assume C_I
values to be discrete and in dB. CDF(Pci) is the cumulative density function of Pci:
CDF ( Pci ( v, n, C_I ) ) = ∑ Pci ( v, n, x )

x ≥ C_I
70 AT250_ARG_E2 © Forsk 2006

7.2.4 Precise Interference Distributions Strategy

Why does Atoll calculate and maintain precise interference distributions, while the most common solution (used by most
other tools) is rather to compress the information into two values: the co-channel and adjacent-channel interference prob-
abilities?
The reason is simply that it,
• improves the AFP result,

• introduces very little (or no) overhead, and
• creates more generic interference information.
7.2.4.1 Direct Availability of Precise Interference Distributions to the AFP

In the presence of frequency hopping, and when one or more frequencies are common (or adjacent) in two interfering MAL
sequences, the hopping gain depends on following factors:
• the MAL length,

• the traffic load on the interferer TRX,
• DTX level, and
• the number of common (and adjacent) frequencies in the two MALs.
All these factors cannot be pre-calculated since it is the AFP that determines the MAL length and the MAL frequencies.
7.2.4.2 Efficient Calculation and Storage of Interference Distributions

In the innermost loop of the calculation process Atoll increments a counter each time a C/I level has a certain value. In the
case of a two-entry IM, there are only two counters for each [interfered, interferer] pair. In the case of precise distribution
information, there are about 40 counters per pair. In both cases, the number of operations is the same: one increment of
an integer value. Once Atoll finishes the counting for an [interfered, interferer] pair, it compresses the information from the
counters to a Cumulative Density Function (CDF) representation. In this way, access to interference probability at a certain
level is instantaneous. Thus, the only overheads are the read / write times to the files and the memory occupation at run-
ning time. These two overheads are negligible and do not affect the calculations, the heaviest part of the task.
7.2.4.3 Robustness of the IM

By having precise C/I distributions calculated and exported, the user is free to change the following settings without the
need for recalculating their interference distributions:
1. Quality requirements of network elements (required C/I, % Probability Max, …),

2. C/I weighting (the interference levels above and below the C/I target),
3. Separation requirements and/or neighbour relations,
4. Hopping gain values, DTX activities, traffic load levels, HSNs, synchronisation information,
5. Any frequency assignment setting (MAL length directives, frequency domains, assignment strategies, number of
required TRXs, cost function parameters, …), or
6. Remove equipment
By not mixing any of the elements above, the interference information keeps its original probability units and is easier to
check and validate. Therefore, the user spends less time on interference recalculations than in the case of a two-entry ma-
trix (where “everything” is included).
7.2.5 Traffic Load and Interference Information Discrimination

Atoll maintains the traffic load separate from the interference information. The reasons for implementing this strategy are
explained here.
Let us look at the possible alternatives to this strategy:
1. The mixed option: The interference information contains the traffic information as well. In this way, each IM entry
will contain the quantity of traffic interfered if a co-channel / adjacent channel reuse exists.
2. The separated option: The AFP has separate access to traffic load information and to interference probabilities
(As in Atoll).
Knowing the difference between the two alternative solutions explains why the second strategy has been opted for for Atoll.
However, in detail, this has been done because:
• Option 2 is a superset that contains option 1. But option 1, being a subset, does not contain option 2 (i.e. once the
information are mixed they cannot be separated).
• It does not create any overhead (the size of the additional information is negligible compared to the size of the IM).
• It helps keeping the unit definitions simpler.
© Forsk 2006 AT250_ARG_E2 71

AFP Reference Guide
• It is facilitates merging IMs with different traffic units.

• The traffic information can be used for weighting the separation violation component.
• The traffic load can be used in deciding whether a TRX can be left uncreated.
- For example, if there are too many TRXs at a site and the user wishes that the AFP remove one of them, in
order to be able to not violate site constraints, the AFP must know the traffic loads in order to choose a low
load TRX to be removed.
• The gain introduced by the traffic load of the interferer depends on the hopping mode and the MAL size. Incorpo-
rating this gain in the IM (as a result of the mixed option) means that the IMs become hopping-mode and MAL-size
dependent. This is a bad idea since the AFP should be able to change the MAL. And the user should be able to
change the hopping mode without recalculating the IM. In addition, an IM calculated externally to Atoll, with a non-
hopping BCCH can be used for the hopping TCH.
A third option also exists. Though, this option is so practically useless due to its inefficiency. It consists in mixing IM and
traffic but still keeping the traffic in its isolated form. This is again a bad idea because of the unit definition and the variety
of IM sources. It involves less benefits than the option chosen in Atoll.
72 AT250_ARG_E2 © Forsk 2006

7.3 Appendix 3: BSIC Allocation

The soft and hard criteria of BSIC Allocation are described here. As explained earlier, not respecting the hard criterion is
considered an error while not respecting the soft criterion just provokes a warning.
The hard criterion is easier to satisfy but must not be violated since it causes handover failures. It is based on the second
order neighbour relation and BCCH co-channel reuse.
The soft criterion uses interference information as well and expands the BSIC reuse prohibition over adjacent-channel
BCCH use. It aims at inducing a larger (BSIC, BCCH) reuse distance. When unable to satisfy this criterion, Atoll BSIC al-
location algorithm will use the interference and separation relations to choose the “least interfering” BSIC to assign.
7.3.1 Definitions
Here,
• “iff” is used instead of “if and only if”.

• “Pred” is used instead of predict.
• Let Pred_Nei(X, Y) be True iff X is a neighbour of Y or Y is a neighbour of X.
Note: For all X, Y in the network, if Pred_Nei(X, Y) then Pred_Nei(Y, X).
• Let Pred_Nei_Of_Nei(X, Y) be true iff there exist Z such that Pred_Nei(X, Z) and Pred_Nei(Y, Z).
• Let Pred_Co_BCCH(X, Y) be true iff X and Y both have the same BCCH.
• Let Pred_Adj_BCCH(X, Y) be true iff X and Y both have adjacent BCCH frequencies.
• Let Pred_Int(X, Y) be true iff X interferes with Y or Y interferes with X.
7.3.2 Hard Criterion

Prohibit using the same BSIC in both X and Y iff,
(Pred_Nei_Of_Nei(X, Y) OR Pred_Nei(X, Y)) AND Pred_Co_BCCH(X, Y)
7.3.3 Soft Criterion

Prohibit using the same BSIC in both X and Y iff,
(Pred_Nei_Of_Nei(X, Y) OR Pred_Int(X, Y) OR Pred_Nei(X, Y)) AND (Pred_Co_BCCH(X, Y) OR Pred_Adj_BCCH(X, Y))
7.3.4 Behaviour
As obvious, the soft constraint is much stronger and has a higher probability of not being respected.
For any criterion not respected, the AFP issues a warning message counting the number of times the AFP was blocked
due to each of the two criteria. The Consistency checking tool considers the cases where the hard criterion is not respected
as errors. The previous algorithm (version 2.2.1) had a weaker soft criterion and had a tendency of using fewer BSICs.
For a realistic test-bench network (using only one NCC), following BSIC usage results were obtained:
Old algorithm Old algorithm New algorithm New algorithm

(equal use of BSIC (equal use of BSIC (equal use of BSIC (equal use of BSIC
disabled) enabled) disabled) enabled)
BSIC 20 204 36 74 49
BSIC 21 112 50 79 47
BSIC 22 52 45 76 39
BSIC 23 10 52 64 47
BSIC 24 1 52 39 44
BSIC 25 0 50 28 49
BSIC 26 0 48 16 52
BSIC 27 0 46 3 52
© Forsk 2006 AT250_ARG_E2 73

AFP Reference Guide
7.4 Appendix 4: Traffic Capture and Dimensioning

7.4.1 Introduction
This appendix describes key GSM (and other TDMA based) network design processes in Atoll, namely Traffic Capture
process and Network Dimensioning process. The purpose of this appendix is not to detail the algorithms and formulas on
which these processes are based, but rather to describe their concepts and processing steps. A glossary of terms used
throughout this document is provided in the beginning to familiarize the reader with terminology employed in Atoll and in
this document as well. It should be noted that the sequence in which these processes are explained is also, usually, the
sequence of designing a GSM network. Though modifications (optimisation or otherwise) in a mature GSM network may
not necessarily follow this rule. The features described in this appendix are:
• Traffic Capture
• Network Dimensioning (and Key Performance Indicator calculation)
Traffic Capture in Atoll is defined as the process of reading raw traffic data from the traffic maps and integrating them to
generate traffic demand for each subcell. In order to perform a Traffic Capture, Atoll collects traffic information (in the form
of Services, Mobility types, Terminal types) from traffic maps and network parameters/criteria (HCS priorities, service zone
model, HR/FR activity percentages, other compatibility criteria, etc.) from the traffic model. Then, it distributes this traffic
according to the criteria over the network’s subcells, and generates and assigns the calculated traffic demand to each
subcell. Traffic Demand is defined as the number of Circuit Switched/Packet Switched traffic Erlangs/kbps in a subcell.
The results from this process are ready to be utilized in the next step.
Network Dimensioning is the process that determines the number of TRXs per subcell required to carry the traffic assigned
to it while respecting the QoS/GoS criteria defined. The traffic captured by the network’s subcells in the previous step is
the main input to this process along with the Quality of Service (or Grade of Service for Circuit Switched traffic) criteria
defined by the user. Assigning a large number of TRXs to a subcell may guarantee the QoS required but will make the
generation of a good frequency plan more difficult. This will also increase the infrastructure cost that depends directly upon
the quantity of equipment required. Therefore, network dimensioning is a more sophisticated process than a mere estima-
tion. Additional outputs of this process are the Traffic Load values (used by the Automatic Frequency Planners) and the
Key Performance Indicators (KPIs).
7.4.2 Traffic Map Generation

Traffic map generation is the process of creating a geographic distribution of offered traffic demand based on user defined
traffic inputs. Atoll is capable of creating, editing, importing and exporting various types of traffic maps. Atoll is capable of
working with raster and vector maps, and incorporates the function of spreading live traffic data (from the network) in the
form of a traffic map.
7.4.3 Traffic Capture Process

Traffic capture is the process of determining and accumulating served traffic onto specific network elements and bearers.
To facilitate comprehension, we will divide the description of the entire process into three parts, the inputs, the calculation
engine and the outputs.
7.4.3.1 Inputs
The following inputs are required for performing a traffic capture:
• Defined traffic model data (Services, Mobility types, Terminal types)

• Traffic map(s) (either internally generated, imported or edited)
• Network elements (Transmitters, Subcells, HCS layers, Frequency domains, equipment, …)
The traffic model data contain the requirements for a certain class of traffic. Numerous classes of traffic can be created
through combinations of [Services, Mobility types, Terminal types]. For example, a Packet Switched service requiring a
certain kbps data throughput, allowing a certain maximum number of simultaneous timeslots to be used, with a minimum
blocking probability, together define a minimum Quality of Service criterion. When this service is accessed by a user with
certain mobility through a certain type of terminal device, this constitutes a particular class of traffic.
Traffic maps can comprise many such traffic classes with user densities for each geographically distributed over the entire
network or a part of it. Different traffic maps, raster, vector and live data, can be overlaid as shown in the figure below.
During the traffic distribution, Atoll combines or integrates the traffic data read from these multiple layers of traffic maps to
generate the traffic per bin.
74 AT250_ARG_E2 © Forsk 2006

Live Traffic Data
Traffic Vector Map
Traffic Raster Map
Figure 7.3: Traffic Maps Overlay
The next section describes how these data, traffic information, compatibility criteria, and requirement criteria, are utilized
in distributing and assigning this traffic to the network’s sectors (subcells, to be precise).
7.4.3.2 The Engine

The Traffic Capture performs three principal tasks. First of all, it computes a Best Server per HCS layer prediction study
(with the possibility to define an handover margin and a coverage reliability level at the boundaries) to define boundaries
and overlaps between sectors corresponding to different layers and to generate an estimate timeslot capacity in kbps/
timeslot per sector. You can choose whether the later be based on C or C/I and C/(I+N). Secondly, it divides the traffic input
from the maps between different HCS layers of the network and between sectors of the same layer complying with the
criteria defined in the data model. In the end, it integrates the traffic distributed to each subcell to generate the end result:
traffic demand per [service, subcell] pair in terms of Erlangs for CS traffic and in terms of kbps for PS traffic. This traffic
demand provides Atoll with an estimate of average demand in terms of # TSL used.
These three steps are described one by one hereafter.
7.4.3.2.1 Traffic Distribution

The distribution of traffic can itself be divided into two parts, one that is performed between different HCS layers and one
that is performed between the sectors of the same layer. Here we will describe both respectively.
7.4.3.2.1.1 Inter-Layer Distribution
Once the Best Server per HCS layer prediction study has been performed in the background, Atoll proceeds to distributing
the traffic over the different HCS layers and between the subcells of each layer.
In Atoll, a user can define any number of HCS layers as required and assign priorities to them. A possible, rather probable,
priority structure could be:
• Micro layer: assigned priority 3

• Macro layer: assigned priority 2
• Umbrella layer: assigned priority 1
Note: In Atoll, the priority levels increase directly as the integer assigned. This means that priority 3 is higher than
priority 2, which is higher than priority 1, and so on.
Atoll starts by assigning traffic to the HCS layer with the highest priority and then moves down the priority scale. There are
two levels of control for filtering the traffic for each layer:
• Global control
• Local control
• Global Control
A user can define each HCS layer to have a certain priority in order to control its importance at the time of traffic distribution.
The priority parameter can hence be termed as one of the global control parameters that guide Atoll to start with a certain
HCS layer. Each HCS layer is assigned a maximum speed limit. Any user with mobility higher than the maximum allowed
on a certain layer cannot be allocated to it. Therefore, all traffic with speeds higher than that permissible on an HCS layer
will not be assigned to it. Next, each layer can have a certain operating frequency. Although this parameter is managed at
© Forsk 2006 AT250_ARG_E2 75

AFP Reference Guide
the TX level, a network can very well have, for example, a GSM 900 layer and an 1800 layer. Only the traffic compatible
with the operating frequency band of a layer will be distributed over that layer. A network can also have, for example, a CS
GSM layer and a PS EDGE layer. This technology compatibility criterion is also taken into account when distributing traffic
over layers. This parameter is also at the level of transmitters in Atoll.
• Local Control
The local control parameters enable much finer tuning at the level of subcells. Each subcell in a network can be assigned
a ‘Target Traffic Overflow’. This is the percentage of traffic that is allowed to overflow from this subcell to the lower priority
layer beneath it. The figure below gives an idea of the effect of this parameter over traffic distribution.
Figure 7.4: Traffiic Overflow
In the example above, when the Target Traffic Overflow for the microcell layer is defined to be 0, the entire traffic (compat-
ible to the micro layer, of course) covered by this cell will be carried by it. On the other hand, if there is a percentage of
traffic allowed to overflow from the micro layer to the layer underneath (10% in this example), Atoll will be permitted in this
case to assign this overflowing traffic to the macro layer. This parameter enables fine tuning of the network’s traffic distri-
bution policy. This may be useful in order to avoid over-dimensioning the micro layer, or to avoid reaching the upper limit
on the maximum number of TRXs that a sector can accommodate.
To be a bit more precise on the two compatibility criteria, i.e. the frequency band and technology, this compatibility com-
parison is in fact performed at the sector level. Atoll compares whether the traffic to be assigned is technologically com-
patible with the higher priority sector before handing it over to the lower priority one. For example, a user with a GSM
terminal using the 900MHz band cannot be assigned to a sector that operates on the 1800Mhz band. Similarly, a terminal
accessing a PS service using the EDGE technology cannot be allocated to a sector that can only perform CS functions.
7.4.3.2.1.2 Intra-Layer Distribution
This function enables the distribution of traffic between sectors of the same layer when there are more than one servers
providing coverage to that traffic. As, for example, in the figure below, there is an overlap between the coverage of A and
B that corresponds to a certain HO margin (fixed by the user). The traffic under this overlapping region is covered by both
servers. Therefore, if the traffic complies with the compatibility criteria for both sectors, it will be equally distributed between
the two. Similarly, when there are more than two servers for traffic in a bin, it will be equally distributed among all the po-
tential servers of that bin.
Figure 7.5: Intra-Layer Distribution
7.4.3.2.2 Average Timeslot Capacity

Atoll computes average TSL capacity for all sectors in terms of kbps for estimating the average TSL consumption relative
to the PS traffic. This capacity can either be based on the C level or interpolation between C/I and C/(I+N) for bins in the
sector’s coverage area. Knowing the average kbps per TSL through this computation, and the kbps demand from the traffic
assigned to a sector, Atoll is able to generate an estimate demand in terms of # TSL for PS traffic.
76 AT250_ARG_E2 © Forsk 2006

7.4.3.2.3 Integration
Atoll integrates the demand in terms of # TSL from the above results to generate the resulting total demand per sector for
each service. This means that the CS traffic demand in Erlangs and PS traffic demand in kbps are converted into a total
demand for each sector. This traffic demand per sector is later utilized when performing the network dimensioning process.
7.4.3.3 Outputs
The outputs of this entire process are CS and PS traffic demands in Erlangs and kbps respectively, the average CS and
PS traffic demand in terms of # TSL, and the average traffic demand in terms of # TSL. The Traffic Capture process gen-
erates an item called ‘Traffic Capture X’, that is required as input to the dimensioning process.
Figure 7.6: Traffic Distribution in Atoll
© Forsk 2006 AT250_ARG_E2 77

AFP Reference Guide
7.4.4 Network Dimensioning Process

The Network Dimensioning process is based on the output of a preceding traffic distribution. Once the traffic from the maps
has been distributed over the network following and respecting the criteria described earlier, it is possible to perform the
dimensioning process for the network. Again, we will break the description into three parts to facilitate explanation and un-
derstanding.
7.4.4.1 Inputs
The input to the dimensioning process is the output of the traffic distribution process described earlier. Once the traffic has
been distributed over the network’s layers and sectors, the dimensioning process can be launched. Apart from the traffic
demand, the dimensioning process also takes into account the minimum required QoS and GoS criteria defined for each
type of service, the upper and lower limits on the # TSL for each service, and the upper limits on the number of TRX sup-
ported by each sector.
7.4.4.2 Dimensioning
The dimensioning engine in Atoll converts the traffic demand into the required # TSL, and eventually the required # TRX,
following the QoS and GoS criteria. For example, for a CS service, let’s say voice, allowing a minimum GoS of 2%, the
traffic demand in Erlangs can easily be converted into # of TSL required to carry that traffic demand while respecting the
required GoS through the Erlang B and Erlang C formulas. The type of model, either Erlang B or Erlang C, can be selected
by the user.
The computation of # TSL required to carry a certain PS traffic demand is more complicated than the simple conversion
process described above. PS traffic implies a more complex definition of Quality of Service than the simple Grade of Serv-
ice of CS traffic. It implies, apart from a certain blocking probability, a certain data throughput (kbps) to be maintained with
a maximum allowable delay. These parameters that indicate the PS traffic quality requirements are known as Key Perform-
ance Indicators or KPIs.
Figure 7.7: Network Dimensioning Process
7.4.4.3 Outputs
To abridge the numerous results generated at the end of a dimensioning process, we can say that the principal result is
always the # TRX required for each subcell, and eventually each sector. Another chief output of the dimensioning process
is the Traffic Load. More specifically, the Atoll Network Dimensioning process provides the # TSL required for CS traffic,
for PS traffic, and the KPIs and the Traffic Load for each subcell. The Traffic Load is defined as the ratio of traffic demand
to the # TSL carrying that traffic. It is perhaps one of the most important outputs of the process as it is further utilized in the
Automatic Frequency Planning process. The consumption for a subcell can be extracted through multiplying the # TRX
required by the Traffic Load and by the TSL multiplexing factor (8 for the GSM standard).
Atoll also incorporates an intelligent allocation methodology for assigning the CS and PS TSL inside a TRX. The user has
the possibility to define the TSL allocation schemes for each type of TRX. This is known as timeslot Configuration.
78 AT250_ARG_E2 © Forsk 2006

AFP Reference Guide
© Forsk 2006 AT250_ARG_E2 79

AFP Reference Guide
Release 2.5.0
AT250_ARG_E2
7 rue des briquetiers – 31700 – Blagnac – France
April 2006
Tel: +33 (0)5 62 74 72 10 – Fax: +33 (0)5 62 74 72 11
http://www.forsk.com – email: forsk@forsk.com

AFP Reference Guide PDF

Hochgeladen von

Dokumentinformationen

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

AFP Reference Guide PDF

Hochgeladen von

Copyright:

Verfügbare Formate

AFP

Forsk (Head Office) 7 rue des Briquetiers  www.forsk.com Web

Atoll 2.5.0 AFP Reference Guide Release AT250_ARG_E2

© Copyright 1997 - 2006 by Forsk

About AFP Reference Guide

© Forsk 2006 AT250_ARG_E2 a

b AT250_ARG_E2 © Forsk 2006

2 Basic AFP Tutorial ............................................................................ 9

3 Frequency Planning Prerequisites .................................................. 25

4 Frequency Plan Optimisation .......................................................... 33

© Forsk 2006 AT250_ARG_E2 i

4.2 Step 2 (Optional): Neighbour Relations and Relative Weighting .................. 34

5 Means to Evaluate Frequency Plans ...............................................47

6 Advanced Topics and Troubleshooting ...........................................55

ii AT250_ARG_E2 © Forsk 2006

6.1.10 BSIC Allocation.................................................................................................... 57

© Forsk 2006 AT250_ARG_E2 iii

iv AT250_ARG_E2 © Forsk 2006

Figure 2.1: AFP Process in Atoll .................................................................................................................................... 9

© Forsk 2006 AT250_ARG_E2 v

vi AT250_ARG_E2 © Forsk 2006

2 AT250_ARG_E2 © Forsk 2006

1.1 Introduction to AFP

1.1.1 Frequency Assignment as a Cost Minimization Problem

GSM Global System for Mobile Communications (Groupe Speciale Mobile)

© Forsk 2006 AT250_ARG_E2 3

4 AT250_ARG_E2 © Forsk 2006

• Group ID (better administration of the frequency resources)

© Forsk 2006 AT250_ARG_E2 5

6 AT250_ARG_E2 © Forsk 2006

8 AT250_ARG_E2 © Forsk 2006

2 Basic AFP Tutorial

2.1 AFP Process in Atoll

Figure 2.1: AFP Process in Atoll

Figure 2.2: Interaction of the AFP with Other Elements

The following figure depicts the outputs of the AFP:

© Forsk 2006 AT250_ARG_E2 9

Figure 2.3: AFP Outputs

2.2 Loading and Validating the Network

Figure 2.4: AFP Launch Wizard - AFP Session Tab

Figure 2.5: AFP Launch Wizard - Separations Tab

10 AT250_ARG_E2 © Forsk 2006

Here you can,

For explanations of AFP performance indicators, refer to section 3.2.

Figure 2.6: AFP Launch Wizard - Global Parameters Tab

Figure 2.7: Event Viewer - Sample Messages

© Forsk 2006 AT250_ARG_E2 11

Let us look at two of these messages:

Figure 2.8: Message 1

Figure 2.9: Message 2

2.3 Definition of the AFP Scope

Let us define 4 groups of transmitters (ALL, NET, SEL, RING):

• ALL = All the transmitters in the project.

12 AT250_ARG_E2 © Forsk 2006

2.4 Preparing to Launch the AFP

Figure 2.10: AFP Launch Dialog - Example 1

Figure 2.11: AFP Launch Dialog - Example 2

© Forsk 2006 AT250_ARG_E2 13

2.5 Launching the AFP and Monitoring its Progress

Figure 2.12: AFP Progress Window

14 AT250_ARG_E2 © Forsk 2006

Figure 2.13: Event Viewer Message - Solution Kept

Figure 2.14: AFP Progress Window

Forsk (Head Office) 7 rue des Briquetiers www.forsk.com Web