Atoll 3.1.0 User Manual UMTS

User Manual
UMTS
v e r s i o n 3.1.0
AT310_UMU_E0
AT310_UMU_E0
experts in radio network planning

& optimisation software
Forsk USA Office
Forsk Head Office
Forsk China Office
200 South Wacker Drive
7 rue des Briquetiers
Suite 302, 3/F, West Tower,
Suite 3100
31700 Blagnac
Jiadu Commercial Building,
Chicago, IL 60606
France
No.66 Jianzhong Road,
USA
Tianhe Hi-Tech Industrial Zone,

Guangzhou, 510665,
Peoples Republic of China
sales_us@forsk.com
sales@forsk.com
enquiries@forsk.com.cn
+1 312 674 4846
+33 (0) 562 747 210
+86 20 8553 8938
+1 312 674 4847
+33 (0) 562 747 211
+86 20 8553 8285
support_us@forsk.com
helpdesk@forsk.com
atollsupport@forsk.com.cn
+1 888 GoAtoll (+1 888 462 8655)
+33 (0) 562 747 225
+86 20 8557 0016
8.00 am to 8.00 pm (EST)
9.00 am to 6.00 pm (CET)
9.00 am to 5.30 pm (GMT+8)
Monday - Friday
Monday - Friday
Monday - Friday
www.forsk.com
Atoll 3.1.0
User Manual
Forsk
Atoll 3.1.0 User Manual Release AT310_UMU_E0
Copyright 1997 - 2011 by Forsk

The software described in this document is provided under a licence agreement. The software may only be used or copied under the terms and
conditions of the licence agreement. No part of this document may be copied, reproduced or distributed 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 registering parties.
The Atoll user documentation is a guide and reference for users working with Atoll. Atoll is easy to use and offers a clear, self-explanatory user
interface. The user documentation helps the user make effective and efficient use of all the features that Atoll offers. The user documentation
aims to familiarise the user with the working environment of Atoll and enable him to use all of Atolls features and functions.
The Atoll user documentation is technology-specific. For each Atoll radio technology, the Atoll user manual contains instructions and information
specific to that technology as well as chapters describing the Atoll working environment and the tools available.
Atoll 3.1.0 User Manual

Table of Contents
AT310_UMU_E0
Table of Contents
Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
The Working Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.1
1.1.1
1.1.2
The Atoll Work Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Working with Document Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Docking or Floating an Atoll Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2
1.2.1
1.2.2
1.2.3
The Explorer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Working with the Explorer Window Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Displaying or Hiding Objects on the Map Using the Explorer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Working with Layers Using the Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3
1.3.1
1.3.1.1
1.3.1.2
1.3.1.3
1.3.2
1.3.2.1
1.3.2.2
1.3.2.3
1.3.2.4
1.3.2.5
1.3.3
1.3.3.1
1.3.3.2
Working with Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Using the Object Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Renaming an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Deleting an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Displaying the Properties of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Modifying Sites and Transmitters Directly on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Selecting One of Several Transmitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Moving a Site Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Moving a Site to a Higher Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Changing the Azimuth of the Antenna Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Changing the Antenna Position Relative to the Site Using the Mouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Display Properties of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Defining the Display Properties of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Examples of Using the Display Properties of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.4
1.4.1
1.4.1.1
1.4.1.2
1.4.1.3
1.4.1.4
1.4.2
1.4.3
1.4.4
1.4.5
1.4.6
1.4.7
1.4.8
1.4.9
1.4.10
1.4.10.1
1.4.10.2
1.4.10.3
1.4.10.4
1.4.10.5
1.4.10.6
1.4.11
1.4.11.1
1.4.11.2
1.4.11.3
1.4.11.4
1.4.11.5
1.4.11.6
1.4.12
1.4.12.1
1.4.12.2
Working with Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Changing the Map Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Zooming In and Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Zooming In on a Specific Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Choosing a Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Changing Between Previous Zoom Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Moving the Map in the Document Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Using the Panoramic Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Centring the Map Window on an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Centring the Map Window on a Table Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Adjusting the Map Window to a Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Measuring Distances on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Displaying Rulers Around the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Displaying the Map Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Using Zones in the Map Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Using a Filtering Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Using a Computation Zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Using a Focus Zone or Hot Spots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Using Polygon Zone Editing Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Using a Printing Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Using a Geographic Export Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Editing Polygons, Lines, and Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Adding a Vector Layer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Creating Polygons, Lines, and Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Editing the Shape of Polygons and Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Combining or Cropping Polygons Using the Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Editing a Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Editing Contours, Lines, and Points Using the Context Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Exporting Coverage Prediction Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Exporting an Individual Coverage Prediction in Vector Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Exporting an Individual Coverage Prediction in Raster Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Table of Contents
1.4.12.3
1.4.13
1.4.14
1.4.15
Forsk 2011
Exporting Multiple Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Saving a Map as a Graphic Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Copying a Map to Another Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Map Window Pointers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
1.5
1.5.1
1.5.2
1.5.2.1
1.5.2.2
1.5.2.3
1.5.3
1.5.4
1.5.5
1.5.6
1.5.6.1
1.5.6.2
1.5.7
1.5.8
1.5.9
1.5.10
1.5.11
Working with Data Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Opening a Data Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Adding, Deleting, and Editing Data Table Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Accessing an Object Types Table Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Adding a Field to an Object Types Data Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Deleting a Field from an Object Types Data Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Editing the Contents of a Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Opening an Objects Record Properties Dialogue from a Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Defining the Table Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Copying and Pasting in Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Copying and Pasting a Table Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Pasting the Same Data into Several Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Viewing a Statistical Analysis of Table Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Exporting Tables to Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Importing Tables from Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Exporting Tables to XML Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Importing Tables from XML Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
1.6
1.6.1
1.6.2
1.6.2.1
1.6.2.2
1.6.2.3
1.6.3
1.6.4
1.6.5
Printing in Atoll. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Printing Data Tables and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Printing a Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Printing Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Defining the Printing Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Defining the Print Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Previewing Your Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Printing a Docking Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Printing Antenna Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
1.7
1.7.1
1.7.1.1
1.7.1.2
1.7.1.3
1.7.1.4
1.7.2
1.7.2.1
1.7.2.2
1.7.3
1.7.3.1
1.7.3.2
1.7.3.3
1.7.3.4
1.7.4
1.7.4.1
1.7.4.2
1.7.5
1.7.5.1
1.7.5.2
1.7.5.3
1.7.5.4
1.7.5.5
1.7.5.6
1.7.6
1.7.6.1
1.7.6.2
1.7.6.3
1.7.6.4
1.7.6.5
1.7.6.6
1.7.7
1.7.8
Grouping, Sorting, and Filtering Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Grouping Data Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Grouping Data Objects by a Selected Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Configuring the Group By Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Advanced Grouping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Examples of Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Sorting Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Sorting Data in Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Advanced Sorting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Filtering Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Filtering in Data Tables by Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Advanced Data Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Restoring All Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Advanced Filtering: Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
User Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Saving a User Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Loading a User Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Site and Transmitter Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Creating a Site or Transmitter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Adding a Site or Transmitter to a List from the Explorer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Adding a Site or Transmitter to a List from the Map Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Adding Sites or Transmitters to a List Using a Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Editing a Site or Transmitter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Filtering on a Site or Transmitter List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Folder Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Creating a Folder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Applying a Saved Folder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Reapplying the Current Folder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Saving a Folder Configuration in an External File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Loading a Folder Configuration from an External File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Deleting a Folder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Creating and Comparing Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Filtering Data Using a Filtering Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
AT310_UMU_E0
1.8
1.8.1
1.8.2
1.8.3
1.8.3.1
1.8.3.2
1.8.3.3
1.8.4
1.8.5
1.8.6
1.8.7

Table of Contents
Tips and Tricks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Undoing and Redoing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Refreshing Maps and Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Searching for Objects on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Searching for a Map Object by Its Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Searching for a Map Object using Any Text Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Searching for a Point on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Using the Status Bar to Get Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Saving Information Displayed in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Using Icons from the Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Using Shortcuts in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Starting an Atoll Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
2.1
Before Starting a Radio-Planning Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
2.2
2.2.1
2.2.1.1
2.2.1.2
2.2.1.3
2.2.2
2.2.2.1
2.2.2.2
2.2.2.3
2.2.2.4
2.2.2.5
Creating an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Creating a New Atoll Document from a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Templates Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Creating a New Atoll Document from a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Defining a New Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Working in a Multi-User Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
The Atoll Multi-User Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Creating a New Atoll Document from a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Working With a Document on a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Refreshing an Atoll Document from the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Archiving the Modifications of an Atoll Document in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
2.3
2.3.1
2.3.2
Making a Backup of Your Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Configuring Automatic Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Recovering a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
2.4
Making and Sharing Portable Atoll Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
3.1
Geographic Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
3.2
Supported Geographic Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
3.3
3.3.1
3.3.2
3.3.3
3.3.3.1
3.3.3.2
3.3.4
3.3.5
3.3.6
3.3.7
Importing Geo Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Importing a Raster-format Geo Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Importing a Vector-format Geo Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Importing MSI Planet Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Importing One MSI Planet Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Importing a MSI Planet Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Importing a WMS Raster-format Geo Data File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Grouping Geo Data Files in Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Embedding Geographic Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Repairing a Broken Link to a Geo Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
3.4
Digital Terrain Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
3.5
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Assigning Names to Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Defining Clutter Class Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Adding a Clutter Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Refreshing the List of Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Displaying Total Surface Area per Clutter Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
3.6
Clutter Heights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
3.7
3.7.1
3.7.2
3.7.3
Contours, Lines, and Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Managing the Display of a Vector Layer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Managing the Properties of the Vector Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Moving a Vector Layer to the Network Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
3.8
3.8.1
3.8.2
Scanned Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Importing Several Scanned Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Defining the Display Properties of Scanned Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Table of Contents
3.9
3.9.1
3.9.2
Population Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Managing the Display of Population Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Displaying Population Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
3.10
3.10.1
3.10.2
3.10.3
3.10.4
3.10.5
Custom Geo Data Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a Custom Geo Data Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a File to a Custom Geo Data Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing the Properties of a Custom Geo Data Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Statistics on Custom Geo Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integrable Versus Non Integrable Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
126
126
127
128
128
129
3.11
3.11.1
3.11.2
3.11.2.1
3.11.2.2
3.11.2.3
Setting the Priority of Geo Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Setting the Display Priority of Geo Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the Priority of Geo Data in Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example 1: Two DTM Maps Representing Different Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example 2: Clutter Classes and DTM Maps Representing the Same Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example 3: Two Clutter Class Maps Representing a Common Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
129
129
130
130
131
131
3.12
Displaying Information About Geo Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
3.13
3.13.1
3.13.2
Geographic Data Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Exporting a Geo Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Loading a Geo Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
3.14
3.14.1
3.14.1.1
3.14.1.2
3.14.1.3
3.14.1.4
3.14.2
Editing Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Editing Clutter Class Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Clutter Polygon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing Clutter Polygons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying the Coordinates of Clutter Polygons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting Clutter Polygons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing Population or Custom Data Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
134
134
134
134
135
135
135
3.15
3.15.1
3.15.1.1
3.15.1.2
3.15.2
3.15.3
3.15.4
3.15.5
Saving Geographic Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Saving Modifications to an External File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exporting an Edited Clutter Class Map in a Raster-Format File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exporting an Edited Vector Layer in Vector-Format File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating the Source File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Combining Several Raster Files into One File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exporting an Embedded File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a New File from a Larger File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
136
137
137
138
138
138
139
140
Antennas and Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
Working With Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating an Antenna. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing Planet-Format Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing 3-D Antenna Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Smoothing an Antenna Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing an Antenna Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
143
143
144
145
147
147
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
4.2.7
4.2.8
Working With Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining TMA Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Feeder Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Transmitter Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating the Values for Total Losses and the Transmitter Equipment Noise Figure . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
..................................................................................................
Creating or Modifying a Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
..................................................................................................
Creating or Modifying Waveguides and Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
147
148
148
148
149
150
151
151
152
5
5.1
5.1.1
5.1.2
5.1.2.1
5.1.2.2
5.1.2.3
5.1.2.4
Forsk 2011
Working with Calculations in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Working with Propagation Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Propagation Model Characteristics: Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Standard Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recommendations for Working with the Standard Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calculating Diffraction With the SPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample Values for SPM Formulas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calculating f(clutter) with the Standard Propagation Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
155
155
156
157
158
158
159
AT310_UMU_E0
5.1.2.5
5.1.2.6
5.1.3
5.1.3.1
5.1.3.2
5.1.3.3
5.1.4
5.1.4.1
5.1.4.2
5.1.4.3
5.1.5
5.1.5.1
5.1.5.2
5.1.5.3
5.1.6
5.1.7
5.1.7.1
5.1.7.2
5.1.7.3
5.1.8
5.1.9
5.1.10
5.1.11
5.1.12
5.1.13
5.1.14

Table of Contents
Modelling Fixed Receivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Defining the Parameters of the Standard Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
The Okumura-Hata Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Defining General Settings (Okumura-Hata) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Selecting an Environment Formula (Okumura-Hata). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Creating or Modifying Environment Formulas (Okumura-Hata) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
The Cost-Hata Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Defining General Settings (Cost-Hata) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Selecting an Environment Formula (Cost-Hata) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Creating or Modifying Environment Formulas (Cost-Hata). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
The ITU 529-3 Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Defining General Settings (ITU 529-3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Selecting an Environment Formula (ITU 529-3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Creating or Modifying Environment Formulas (ITU 529-3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
The Erceg-Greenstein Propagation Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Defining General Settings (Erceg-Greenstein (SUI)). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Selecting an Environment Formula (Erceg-Greenstein (SUI)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Creating or Modifying Environment Formulas (Erceg-Greenstein (SUI)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
The WLL Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
The Longley-Rice Propagation Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
The ITU 1546 Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
The Sakagami Extended Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
CrossWave Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Managing Propagation Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.2
5.2.1
5.2.2
5.2.3
5.2.4
5.2.5
Defining Calculation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Defining Calculation Parameters for One Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Defining the Same Calculation Parameters for a Group of Transmitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Defining the Same Calculation Parameters for All Transmitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Defining a Default Propagation Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Defining a Default Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5.3
5.3.1
5.3.2
5.3.3
5.3.4
5.3.5
5.3.6
5.3.7
5.3.7.1
5.3.7.2
5.3.7.3
5.3.7.4
5.3.7.5
5.3.8
Managing Path Loss Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Calculating Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Stopping Path Loss Matrix Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Setting the Storage Location of Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Using Centralised Path Loss Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Checking the Validity of Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Optimising Path Loss Matrix Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Tuning Path Loss Matrices Using Measurement Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Defining the Area to be Tuned. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Defining Maximum Corrections and Thresholds on Path Loss Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Tuning Path Loss Matrices Using CW Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Tuning Path Loss Matrices Using Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Managing the Path Loss Tuning Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Exporting Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
5.4
5.4.1
5.4.1.1
5.4.1.2
5.4.1.3
5.4.1.4
5.4.1.5
5.4.2
5.4.2.1
5.4.2.2
5.4.2.3
5.4.2.4
5.4.2.5
5.4.2.6
Predictions Available in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Making Point Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Starting a Point Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
The Views of the Point Analysis Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Moving the Receiver on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Taking Indoor Losses into Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Taking Shadowing into Account in Point Analyses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Making Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Creating Coverage Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Defining the Storage Location of Coverage Prediction Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Calculating Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Saving Defined Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Calculating Indoor Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Taking Shadowing into Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Table of Contents
Forsk 2011
UMTS HSPA Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
6.1
Designing a UMTS Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
6.2
6.2.1
6.2.1.1
6.2.1.2
6.2.1.3
6.2.1.4
6.2.1.5
6.2.2
6.2.3
6.2.4
6.2.5
6.2.6
6.2.6.1
6.2.6.2
6.2.6.3
6.2.6.4
6.2.6.5
6.2.6.6
6.2.7
6.2.7.1
6.2.7.2
6.2.7.3
6.2.7.4
6.2.7.5
6.2.8
6.2.9
6.2.9.1
6.2.9.2
6.2.10
6.2.10.1
6.2.10.2
6.2.10.3
6.2.10.4
6.2.10.5
6.2.10.6
6.2.10.7
6.2.10.8
6.2.10.9
6.2.10.10
6.2.10.11
6.2.10.12
6.2.11
6.2.11.1
6.2.11.2
6.2.11.3
6.2.11.4
6.2.11.5
6.2.11.6
6.2.11.7
6.2.11.8
6.2.11.9
6.2.12
6.2.12.1
6.2.12.2
6.2.12.3
6.2.12.4
6.2.12.5
6.2.12.6
Planning and Optimising UMTS Base Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a UMTS Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Definition of a Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating or Modifying a Base Station Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Placing a New Station Using a Station Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Station Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Duplicating an Existing Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Group of Base Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Sites and Transmitters Directly on the Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display Tips for Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Dual-Band UMTS Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening the Repeaters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating and Modifying Repeater Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Placing a Repeater on the Map Using the Mouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Several Repeaters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining the Properties of a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tips for Updating Repeater Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Remote Antenna. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening the Remote Antennas Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Placing a Remote Antenna on the Map Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Several Remote Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining the Properties of a Remote Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tips for Updating Remote Antenna Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the Working Area of an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Studying a Single Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Making a Point Analysis to Study the Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Studying Signal Level Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Studying Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Path Loss Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning a Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Calculation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Computation Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Transmitters or Cells as Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signal Level Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Analysing a Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UMTS-Specific Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HSDPA Quality and Throughput Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HSUPA Quality and Throughput Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing and Exporting Coverage Prediction Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Making a Multi-point Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning Neighbours. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Exceptional Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Importance Factors for Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Allocating Neighbours Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking Automatic Allocation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Allocating and Deleting Neighbours per Cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calculating the Importance of Existing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the Consistency of the Neighbour Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exporting Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning Scrambling Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining the Scrambling Code Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Scrambling Code Domains and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Exceptional Pairs for Scrambling Code Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Allocating Scrambling Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the Consistency of the Scrambling Code Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying the Allocation of Scrambling Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
200
201
201
208
210
211
218
218
219
219
220
220
220
220
221
221
222
223
224
224
224
225
225
226
226
227
227
229
231
232
233
235
236
236
237
241
251
267
269
270
271
274
275
275
276
276
280
283
285
287
288
288
289
289
290
290
293
294
6.3
6.3.1
6.3.2
6.3.2.1
Studying Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining Multi-service Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Sector Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
297
298
298
298
10
AT310_UMU_E0

Table of Contents
6.3.2.2
6.3.2.3
6.3.2.4
6.3.2.5
6.3.3
6.3.4
6.3.4.1
6.3.4.2
6.3.4.3
6.3.4.4
6.3.4.5
6.3.4.6
6.3.4.7
6.3.4.8
6.3.4.9
6.3.5
6.3.5.1
6.3.5.2
Creating a User Profile Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Creating User Density Traffic Maps (No. Users/km2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Converting 2G Network Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Exporting Cumulated Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Exporting a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Calculating and Displaying Traffic Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
The Power Control Simulation Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Creating Simulations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Displaying the Traffic Distribution on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Displaying the User Active Set on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Displaying the Results of a Single Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Displaying the Average Results of a Group of Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Updating Cell Values With Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Adding New Simulations to an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Estimating a Traffic Increase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Analysing the Results of a Simulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Making an AS Analysis of Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Making Coverage Predictions Using Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
6.4
6.4.1
6.4.1.1
6.4.1.2
6.4.1.3
6.4.1.4
6.4.1.5
6.4.2
6.4.2.1
6.4.2.2
6.4.2.3
6.4.2.4
6.4.3
6.4.3.1
6.4.3.2
6.4.3.3
6.4.4
6.4.5
6.4.6
6.4.6.1
6.4.6.2
6.4.6.3
Optimising Network Parameters Using the ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

The ACP Module and Atoll. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Using Zones with ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Using Traffic Maps with ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Shadowing Margin and Indoor Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
ACP and Antenna Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
EMF Exposure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Configuring the ACP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Defining the Storage Location of ACP Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Defining the Antenna Masking Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Configuring the Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Configuring Setup-specific Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Optimising Cell Planning with the ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Creating an Optimisation Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Defining Optimisation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Defining Site Selection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Running an Optimisation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Working with Optimisations in the Explorer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Viewing Optimisation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Viewing Optimisation Results in the Properties Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Viewing Optimisation Results in the Map Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Viewing Optimisation Results Using the Histogram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
6.5
6.5.1
6.5.2
6.5.3
6.5.4
6.5.4.1
6.5.4.2
6.5.4.3
6.5.4.4
6.5.4.5
6.5.5
6.5.6
6.5.7
Verifying Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Importing a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Displaying Drive Test Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Defining the Display of a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Network Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Filtering Incompatible Points Along Drive Test Data Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Creating Coverage Predictions from Drive Test Data Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Displaying Statistics Over a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Extracting a Field From a Drive Test Data Path for a Transmitter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Analysing Data Variations Along the Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Exporting a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Extracting CW Measurements from Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Printing and Exporting the Drive Test Data Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
6.6
6.6.1
6.6.2
6.6.2.1
6.6.2.2
6.6.3
6.6.3.1
6.6.3.2
6.6.3.3
6.6.3.4
6.6.3.5
6.6.3.6
Co-planning UMTS Networks with Other Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Switching to Co-planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Working with Coverage Predictions in a Co-Planning Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Updating Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Analysing Coverage Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Performing Inter-Technology Neighbour Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Setting Inter-Technology Exceptional Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Displaying Inter-Technology Exceptional Pairs on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Adding and Removing Inter-Technology Exceptional Pairs on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Configuring Importance Factors for Inter-Technology Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Allocating Inter-Technology Neighbours Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Displaying Inter-Technology Neighbours on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
11

Table of Contents
6.6.3.7
6.6.3.8
6.6.3.9
6.6.4
6.6.5
6.6.5.1
6.6.5.2
6.6.6
6.7
6.7.1
6.7.2
6.7.3
6.7.3.1
6.7.3.2
6.7.4
6.7.4.1
6.7.4.2
6.7.4.3
6.7.5
6.7.5.1
6.7.5.2
6.7.5.3
6.7.6
6.7.6.1
6.7.6.2
6.7.6.3
6.7.7
6.7.8
6.7.9
6.7.9.1
6.7.10
6.7.10.1
Forsk 2011
Allocating and Deleting Inter-Technology Neighbours per Cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Calculating the Importance of Existing Inter-technology Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the Consistency of the Inter-technology Neighbour Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a UMTS Sector From a Sector in the Other Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using ACP in a Co-planning Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a New Co-planning Optimisation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing the Other Network into the Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ending Co-planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
401
404
406
407
407
408
408
408
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modelling Inter-Carrier Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Frequency Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Options of the Network Settings Properties Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining R99 Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining HSDPA Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining HSUPA Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Site Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Resource Consumption per UMTS Site Equipment and R99 Radio Bearer . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Resource Consumption per UMTS Site Equipment and HSUPA Radio Bearer . . . . . . . . . . . . . . . . . . . . . . . . .
Receiver Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating or Modifying Reception Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HSDPA UE Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HSUPA UE Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple Input Multiple Output Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conditions for Entering the Active Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modelling Shadowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying the Shadowing Margins and Macro-diversity Gain per Clutter Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modelling Inter-Technology Interference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Inter-Technology IRFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
409
409
409
410
410
411
411
412
412
413
413
413
414
415
415
415
417
417
417
418
419
419
420
421
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
12
Chapter 1
The Working
Environment
This chapter presents the Atoll working environment and
explains the tools and shortcuts available.
In this chapter, the following are explained:
"The Atoll Work Area" on page 15
"The Explorer Window" on page 17
"Working with Objects" on page 19
"Working with Maps" on page 29
"Working with Data Tables" on page 47
"Printing in Atoll" on page 60
"Grouping, Sorting, and Filtering Data" on page 65
"Tips and Tricks" on page 82

Chapter 1: The Working Environment
14
Forsk 2011

AT310_UMU_E0
1 The Working Environment

The Atoll working environment is both powerful and flexible. It provides a comprehensive and integrated set of tools and
features that allow you to create and define your radio-planning project in a single application. Atoll includes advanced multitechnology network planning features (e.g., CDMA/LTE), and a combined single-RAN, multi-RAT GSM/UMTS/LTE Monte Carlo
simulator and traffic model. You can save the entire project as a single file, or you can link your project to external files.
The Atoll working environment uses familiar Windows interface elements, with the ability to have several document windows
open at the same time, support for drag-and-drop, context menus, and support for standard Windows shortcuts, for example,
for cutting and pasting. Atoll not only enables you to create and work on your planning project, but also offers you a wide
range of options for creating and exporting results based on your project. The working environment provides a wide selection
of tools to facilitate radio-planning, such as a search tool to locate either a site, a point on the map, or a vector.
The Explorer window plays a central role in Atoll. The Explorer window contains most of the objects in a document arranged
in folders.
Using the Explorer window, you can manage all objects in the Atoll document: sites, transmitters, calculations, etc., as well
as geographic data such as the Digital Terrain Model (DTM), traffic maps, and clutter classes. You can, for example, define various coverage predictions or configure the parameters or display of data objects.
The content of the folders in the Explorer window can be displayed in tables, allowing you to manage large amounts of data.
You can sort and filter the data in a table, or change how the data is displayed. You can also use the table feature to enter
large amounts of information by importing data or by cutting and pasting the information from any Windows spreadsheet into
the table.
The map is the working area for your document and Atoll provides many tools for working with the map. You can change the
view by moving or zooming in or out and you can choose which objects are displayed and how they are displayed. You can
also export the current display definition, or configuration, to use it in other documents.
This chapter provides an overview of the Atoll working environment.
This chapter explains the following topics:
"The Atoll Work Area" on page 15

"The Explorer Window" on page 17
"Working with Objects" on page 19
"Printing in Atoll" on page 60
"Working with Maps" on page 29
"Working with Data Tables" on page 47
"Grouping, Sorting, and Filtering Data" on page 65
"Tips and Tricks" on page 82.
1.1 The Atoll Work Area

The Atoll work area, shown in Figure 1.1 on page 16, consists of the main window where the map window and data tables and
reports are displayed and the Explorer window. The Explorer window contains the data and objects of a document, arranged
in folders. It is presented in detail in "The Explorer Window" on page 17.
Atoll offers a variety of tools to help you plan a network. The tools open in separate windows, some of which can be docked
into the work area or floated over the work area (see Figure 1.1 on page 16).
15

Forsk 2011
Toolbar
Document window
(map)
Workspace
Explorer window
(docked)
Panoramic window
(floating)
Find on Map window

(docked)
Figure 1.1: Atoll user interface
1.1.1 Working with Document Windows

When you have one Atoll document open, you can have several document windows open at the same time. You can resize,
maximise, and minimise document windows as you can in any Windows-based application.
As well, you can tile document windows, in order to display all of them at the same time, or cascade them, in order to display
the title bar of each document window.
To tile document windows:
Select Window > Tile.
To cascade document windows:
Select Window > Cascade.
1.1.2 Docking or Floating an Atoll Window

Only document windows are part of an individual Atoll document. Other windows and tools, such as the Explorer window,
display the content of the active document. They are not part of the individual Atoll document, but part of the working environment and, when you switch to a different document, they will display the content of the active document.
You can change how these windows and tools are displayed. You can also remove them from their position and float them
over the Atoll working environment.
To display a window:
On the View menu, select the name of the window.
To display a tool window:
On the Tool menu, select the name of the window.
To close a window or tool:
Click the Close button ( ) in the corner of the window. Depending on the position of the docking window, this button
can be in the upper-left or upper-right corner.
You can change how much room a window takes if it shares a docking area with other windows by maximising or minimising
the window.
16

AT310_UMU_E0
To maximise a window in its docking area:
Click the Maximise button ( ) near the corner of the window. Depending on the position of the window, this button
To minimise a window in its docking area:
Click the Minimise button ( ) near the corner of the window. Depending on the position of the window, this button
You can leave a window in its docking area, or you can have it float over the working environment, allowing you to maximise
the amount of area for document windows or other windows.
To float a window:
Double-click the docking window title bar. The docking window leaves the docking area and floats over the working
environment.
You can move the docking window by clicking the title bar and dragging it. To prevent the
window from docking as you move it, press CTRL as you drag the docking window.
To dock a window:
To return the window to its previous docked location, double-click the docking window title bar.
Or
Click the title bar of the docking window and drag the window to a different docking area.
The window positions for docking windows are not associated with the current document;
they remain the same no matter which document you open.
1.2 The Explorer Window

The Explorer window plays a central role in Atoll. The Explorer window contains the data and objects of a document, arranged
in folders. Each object and folder has a context-specific menu that you can access by right-clicking. You can modify items at
the folder level, with changes affecting all items in the folder, or you can access and edit items individually. As well, most folder
contents can also be accessed in a table, allowing you to easily manage large amounts of information. For information on
working with tables, see "Working with Data Tables" on page 47.
In this section, the following are described:
"Working with the Explorer Window Tabs" on page 17

"Displaying or Hiding Objects on the Map Using the Explorer" on page 18
"Working with Layers Using the Explorer" on page 19.
1.2.1 Working with the Explorer Window Tabs

The Explorer window has three tabs; each tab has objects and folders containing objects.
To move from one tab to another:
Click the tab at the bottom of the Explorer window.
You can open a folder on a tab to view its contents. Each folder containing at least one object has an Expand ( ) or Contract
button ( ) to the left of its name.
To expand a folder to display its contents:
Click the Expand button (
) to the left of its name.
The tabs in the Explorer window are:
The Network tab: The Network tab allows you to manage radio data and calculations. Depending on the modules
installed with Atoll, the Network tab has the following folders:
-
Sites
Transmitters
Predictions
UMTS Simulations, CDMA2000 Simulations , WiMAX 802.16e simulations, or LTE Simulations
Traffic analysis (GSM/GPRS/EDGE projects only)
17

Interference matrices (GSM/GPRS/EDGE, LTE, and WiMAX projects only)

Subscriber lists (LTE and WiMAX projects only)
Multi-point analyses (
Automatic cell planning results (GSM/GPRS/EDGE, UMTS, LTE, and WiMAX only)
Hexagonal design
Microwave links
CW Measurements and drive test data
The Geo Tab: The Geo tab allows you to manage geographic data. The number of folders depends on the number
and types of geographical data types (vector data, scanned images, etc.) you import or create:
-
Forsk 2011
Clutter classes
Clutter heights
Digital terrain model
Population data
Geoclimatic parameters
Any other geo data map
Traffic maps (GSM/GPRS/EDGE/TDMA, UMTS HSPA, CDMA2000, LTE, and WiMAX)
The Parameters tab: The Parameters tab allows you to manage the propagation models and additional modules.
It contains:
-
Propagation Models: The Parameters tab has a Propagation Models folder with the following propagation
models:
- Cost-Hata
- Erceg-Greenstein (SUI)
- ITU 1546
- ITU 370-7 (Vienna 93)
- ITU 526-5
- ITU 529
- Longley-Rice
- Microwave ITU-R P.452 Model
- Microwave Propagation Model
- Okumura-Hata
- Standard Propagation Model
- WLL
Radio Network Equipment: The Radio Network Equipment folder contains antenna models, transmitter models,
repeater and smart antenna equipment, and waveguides, cables, and feeders.
Traffic Parameters: The Traffic Parameters folder contains services, mobility types, terminals, user profiles, and
environments.
Network Settings: The Network Settings folder contains station templates, frequencies and frequency bands,
bearers, reception equipment, quality indicators, etc.
Microwave link network settings and equipment
The AFP models available in your Atoll installation.
Any additional module created using the API.
1.2.2 Displaying or Hiding Objects on the Map Using the Explorer

You can use the Explorer to display or hide objects on the map. This allows you to hide one type of object so that another type
of object is more plainly visible. For example, you could hide all predictions but one, so that the results of one prediction are
more clearly displayed.
Hiding an object affects only its visibility in the map window; it will still be taken into
consideration during calculations.
To hide an object on the map:

1. Select the tab of the Explorer window that contains that object.
2. Clear the check box ( ) immediately to the left of the object name. The check box appears cleared (
is no longer visible on the map.
) and the object
You can hide the contents of an entire folder by clearing the check box to the left of the
folder name. When the check box of a folder appears greyed ( ), it indicates that the
folder contains both visible and hidden objects.
18

AT310_UMU_E0
1.2.3 Working with Layers Using the Explorer

In Atoll, the map is made of objects arranged in layers. The layers on the top (as arranged on the Network and Geo tabs) are
the most visible on the screen and in print. The visibility of the lower layers depends on which layers are above and visible (see
"Displaying or Hiding Objects on the Map Using the Explorer" on page 18) and on the transparency of these layers (see "Defining the Transparency of Objects and Object Types" on page 25).
To move a layer up or down:
1. Select the tab of the Explorer window that contains that object.
2. Click and drag the object to its new position. As you drag the object, a horizontal black line indicates where the object
will remain when you release the mouse button (see Figure 1.2).
Figure 1.2: Moving a layer

Before you print a map, you should pay attention to the arrangement of the layers. For
more information, see "Printing Recommendations" on page 61.
1.3 Working with Objects

In Atoll, the items found in the Explorer window and displayed on the map are referred to as objects. Most objects in Atoll
belong to an object type. For example, a transmitter is an object of the type transmitter.
Atoll enables you to carry out many operations on objects by clicking the object directly or by right-clicking the object and
selecting the operation from the context menu.
In this section, the following are explained:
"Using the Object Context Menu" on page 19

"Modifying Sites and Transmitters Directly on the Map" on page 21
"Display Properties of Objects" on page 23.
1.3.1 Using the Object Context Menu

In Atoll, an objects context menu gives you access to commands specific to that object as well as to commands that are
common to most objects. In this section, the following context menu commands common to all objects types are explained:
Rename: "Renaming an Object" on page 19.

Delete: "Deleting an Object" on page 20.
Properties: "Displaying the Properties of an Object" on page 20.
1.3.1.1 Renaming an Object

You can change the name of an object in Atoll.
To rename an object:
1. Right-click the object either in the Explorer window or on the map. The context menu appears.
2. Select Rename from the context menu.
3. Enter the new name and press ENTER to change the name.
19

Forsk 2011
In Atoll, objects such as sites or transmitters are named with default prefixes. Individual
objects are distinguished from each other by the number added automatically to the
default prefix. You can change the default prefix for sites, transmitters, and cells by editing
the atoll.ini file. For more information, see the Administrator Manual.
1.3.1.2 Deleting an Object

You can delete objects from either the Explorer window or from the map.
To delete an object:
2. Select Delete from the context menu. The selected object is deleted.
1.3.1.3 Displaying the Properties of an Object

You can modify the properties of an object in the Properties dialogue.
To open the Properties dialogue of a data object:
When you are selecting data objects on the map, it can be difficult to ensure that the
correct object has been selected. When a site is selected, the site (and its name) is
surrounded by a black frame (
). When a transmitter is selected, both ends of its
icon have a green point (
). When there is more than one transmitter with with the
same azimuth, clicking the transmitters in the map window opens a context menu
allowing you to select the transmitter you want (see "Selecting One of Several
Transmitters" on page 21).
2. Select Properties from the context menu. The Properties dialogue appears.
Switching Between Property Dialogues
You can switch between the Properties dialogues of items (transmitters, antennas, sites, services, user profiles, etc.) in the
same folder or defined view in the Explorer window by using the browse buttons (
of each Properties dialogue:
: jump to the first item in the list
: jump to the previous item in the list
: jump to the next item in the list
: jump to the last item in the list
) in the lower-left corner
If you have made any changes to the properties of an item, Atoll prompts you to confirm these changes before switching to
the next Properties dialogue.
You can use this feature, for example, to access the properties of co-site transmitters without closing and reopening the Properties dialogue. Switching is performed within the folder or, if you have created a view, within the view. For example:
If transmitters are grouped by site, you can switch only within one site (co-site transmitters).
If transmitters are grouped by a flag, you can switch only within this group.
If transmitters are grouped by activity and by a flag, you can switch only within transmitters having the same activity
and the same flag.
The browse buttons are not available:
When creating a new item.

When opening an items Properties dialogue by double-clicking its record in a table.
For repeater properties.
For propagation model properties.
The Display tab of the Properties dialogue is explained in "Display Properties of Objects" on page 23.
20

AT310_UMU_E0
1.3.2 Modifying Sites and Transmitters Directly on the Map

In a complex radio-planning project, it can be difficult to find the data object on the Network tab, although it might be visible
in the map window. Atoll lets you access the Properties dialogue of sitesand transmitters directly from the map. You can also
change the position of a site by dragging it, or by letting Atoll find a higher location for it.
"Selecting One of Several Transmitters" on page 21

"Moving a Site Using the Mouse" on page 21
"Moving a Site to a Higher Location" on page 21
"Changing the Azimuth of the Antenna Using the Mouse" on page 22
"Changing the Antenna Position Relative to the Site Using the Mouse" on page 22.
1.3.2.1 Selecting One of Several Transmitters

If there is more than one transmitter with the same azimuth, Atoll enables you to select a specific transmitter.
To select one of several transmitter with the same azimuth:
1. In the map window, click the transmitters. A context menu appears with a list of the transmitterswith the same
azimuth (see Figure 1.3).
Figure 1.3: Selecting one transmitter

2. Select the transmitter from the context menu.
-
When you select a transmitter, it appears with a green point at both ends of the icon (
).
1.3.2.2 Moving a Site Using the Mouse

You can move a site by editing the coordinates on the General tab of the Site Properties dialogue, or by using the mouse.
To move a site using the mouse:
1. Click and drag the site to the desired position. As you drag the site, the exact coordinates of the pointers current location are visible in the Status bar.
2. Release the site where you would like to place it. By default, Atoll locks the position of a site. When the position of a
site is locked, Atoll asks you to confirm that you want to move the site.
3. Click Yes to confirm.
While this method allows you to place a site quickly, you can adjust the location more
precisely by editing the coordinates on the General tab of the Site Properties dialogue.
1.3.2.3 Moving a Site to a Higher Location

If you want to improve the location of a site, in terms of reception and transmission, Atoll can find a higher location within a
specified radius from the current location of the site.
To have Atoll move a site to a higher location:
1. Right-click the site in the map window. The context menu appears.
2. Select Move to a Higher Location.
21

Forsk 2011
3. In the Move to a Higher Location dialogue, enter the radius of the area in which Atoll should search and click OK. Atoll
moves the site to the highest point within the specified radius.
1.3.2.4 Changing the Azimuth of the Antenna Using the Mouse

In Atoll, you can set the azimuth of a transmitters antenna by modifying it on the Transmitter tab of the Transmitter Properties dialogue, or you can modify it on the map, using the mouse. The azimuth is defined in degrees, with 0 indicating north.
The precision of the change to the azimuth depends on the distance of the pointer from the transmitter symbol. Moving the
pointer changes the azimuth by:
1 degree when the pointer is within a distance of 10 times the size of the transmitter symbol.
0.1 degree when the pointer is moved outside this area.
To modify the azimuth of the antenna using the mouse:

1. On the map, click the antenna whose azimuth you want to modify.
2. Move the pointer to the end of the antenna with a green circle ( ). An arc with an arrow
appears under the pointer.
3. Click the green circle and drag it to change the antennas azimuth.
The current azimuth of the antenna is displayed in the far left of the status bar.
4. Release the mouse when you have set the azimuth to the desired angle.
The antennas azimuth is modified on the Transmitter tab of the Transmitter Properties
dialogue.
You can also modify the azimuth on the map for all the antennas on a base station using the mouse.
To modify the azimuth of all the antennas on a base station using the mouse:
1. On the map, click one of the antennas whose azimuth you want to modify.
2. Move the pointer to the end of the antenna with a green circle ( ). An arc with an arrow
appears under the pointer.
3. Hold CTRL and, on the map, click the green circle and drag it to change the antennas azimuth.
The current azimuth of the antenna is displayed in the far left of the status bar.
4. Release the mouse when you have set the azimuth of the selected antenna to the desired
angle.
The azimuth of the selected antenna is modified on the Transmitter tab of the Transmitter
Properties dialogue. The azimuth of the other antennas on the base station is offset by the
same amount as the azimuth of the selected antenna.
If you make a mistake when changing the azimuth, you can undo your changes by using
Undo (by selecting Edit > Undo, by pressing CTRL+Z, or by clicking
undo the changes made.
in the toolbar) to
1.3.2.5 Changing the Antenna Position Relative to the Site Using the Mouse
By default, antennas are placed on the site. However, antennas are occasionally not located directly on the site, but a short
distance away. In Atoll, you can change the position of the antenna relative to the site either by adjusting the Dx and Dy
parameters or by entering the coordinates of the antenna position on the General Tab of the Transmitter Property dialogue.
Dx and Dy are the distance in metres of the antenna from the site position. You can also modify the position of the antenna
on the map, using the mouse.
To move a transmitter using the mouse:
1. On the map, click the transmitter you want to move.
2. Move the pointer to the end of the antenna with a green rectangle ( ). A cross appears under
the pointer.
3. Click the green rectangle and drag it to change the antennas position relative to the site.
The current coordinates (x and y) of the antenna are displayed in the far right of the status
bar.
4. Release the mouse when you have moved the selected transmitter to the desired position.
The position of the selected transmitter is modified on the General tab of the Transmitter
Properties dialogue.
22

AT310_UMU_E0
If you make a mistake when changing the position of the transmitter, you can undo your
changes by using Undo (by selecting Edit > Undo, by pressing CTRL+Z, or by clicking
in the toolbar) to undo the changes made.
1.3.3 Display Properties of Objects

In Atoll, most objects, such as sites or transmitters, belong to an object type. How an individual object appears on the map
depends on the settings on the Display tab of the object types Properties dialogue. The Display tab is similar for all object
types whose appearance can be configured. Options that are inapplicable for a particular object type are unavailable on the
Display tab of its Properties dialogue (see Figure 1.4).
In this section, the display options are explained, followed by a few examples of how you can use them while working on your
Atoll document (see "Examples of Using the Display Properties of Objects" on page 28).
"Defining the Display Properties of Objects" on page 23

"Examples of Using the Display Properties of Objects" on page 28.
1.3.3.1 Defining the Display Properties of Objects

When you access the Properties dialogue of a group of objects, for example, when you access the Properties dialogue of the
Sites folder, the Display tab will show options applicable to all objects in that group (see Figure 1.4).
Figure 1.4: The Display tab for Sites

When you access the Properties dialogue of an individual object, the Display tab will only show the options applicable to an
individual object (see Figure 1.5).
23

Forsk 2011
Figure 1.5: The Display tab for an individual site

To define the display properties of an object type:
1. Right-click the object type folder in the Explorer window. The context menu appears.
3. Select the Display tab. Depending on the object type, the following options are available:
-
"Defining the Display Type" on page 24

"Defining the Transparency of Objects and Object Types" on page 25
"Defining the Visibility Scale" on page 25
"Defining the Object Type Label" on page 26
"Defining the Object Type Tip Text" on page 26
"Adding an Object Type to the Legend" on page 27
4. Set the display parameters.

5. Click OK.
Defining the Display Type
Depending on the object selected, you can choose from the following display types: unique, discrete values, value intervals,
or automatic.
To change the display type:
1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 23.
2. Select the display type from the Display Type list:
-
Unique: defines the same symbol for all objects of this type. By defining a unique symbol for an object type,
objects of different types, for example, sites or transmitters, are immediately identifiable.
i.
To modify the appearance of the symbol, click the symbol in the table below. The Symbol Style dialogue appears.
ii. Modify the symbol as desired.

iii. Click OK to close the Symbol Style dialogue.
-
Discrete values: defines the display of each object according to the value of a selected field. This display type can
be used to distinguish objects of the same type by one characteristic. For example, you could use this display type
to distinguish transmitter by antenna type, or to distinguish inactive from active sites.
i.
Select the name of the Field by which you want to display the objects.
ii. You can click the Actions button to access the Actions menu. For information on the commands available, see
"Using the Actions Button" on page 25.
iii. To modify the appearance of a symbol, click the symbol in the table below. The Display Parameters dialogue
appears.
iv. Modify the symbol as desired.
v. Click OK to close the Display Parameters dialogue.
-
Value intervals: defines the display of each object according to set ranges of the value of a selected field. This display type can be used, for example, to distinguish population density, signal strength, or the altitude of sites.
i.
24
Select the name of the Field by which you want to display the objects.

AT310_UMU_E0
ii. Define the ranges directly in the table below. For an example, see Figure 1.7 on page 27.
iii. You can click the Actions button to access the Actions menu. For information on the commands available, see
"Using the Actions Button" on page 25.
iv. To modify the appearance of a symbol, click the symbol in the table. The Display Parameters dialogue appears.
v. Modify the symbol as desired.
vi. Click OK to close the Display Parameters dialogue.
-
Automatic: only available for transmitters; Atoll automatically assigns a colour to each transmitter, ensuring that
each transmitter has a different colour than the transmitters surrounding it.
i.
Click the symbol in the table below. The Display Parameters dialogue appears.
ii. Modify the symbol as desired.

iii. Click OK to close the Display Parameters dialogue.
When you create a new map object, for example, a new site or a new transmitter,
you must click the Refresh button (
) for Atoll to assign a colour to newly created object according to the set display type.
You can define the default symbol used for sites and how it is displayed by editing
an option in the atoll.ini file. For more information, see the Administrator Manual.
Using the Actions Button

The Actions button on the Display tab of the Properties dialogue allows you to modify the display type as defined in "Defining
the Display Type" on page 24.
To access the Actions menu:
2. Click the Actions button. The Actions menu gives you access to the following commands:
-
Properties: Atoll displays the Display Parameters dialogue, enabling you to define the appearance of the selected
symbol in the table.
Select all: Atoll selects all the values in the table.
Delete: Atoll removes the selected value from the table.
Insert before: When the selected display type is value intervals, Atoll inserts a new threshold in the table before
the threshold selected in the table.
Insert after: When the selected display type is value intervals, Atoll inserts a new threshold in the table after the
threshold selected in the table.
Shading: Atoll opens the Shading dialogue. When "Value Intervals" is the selected display type, you select Shading
to define the number of value intervals and configure their colour. Enter the upper and lower limits of the value
in the First Break and Last Break boxes respectively, and enter a value in the Interval box. Define the colour
shading by choosing a Start Colour and an End Colour. The value intervals will be determined by the set values
and coloured by a shade going from the set start colour to the set end colour.
When "Discrete Values" is the selected display type, you select Shading to choose a Start Colour and an End Colour.
Display Configuration: Select Load if you want to import an existing display configuration. Select Save if you want
to save the display settings of the current object in a display configuration file, so that you can share them with
other users or use them in other documents.
Defining the Transparency of Objects and Object Types

You can change the transparency of some objects, such as predictions, and some object types, such as clutter classes, to allow
objects on lower layers to be visible on the map.
To change the transparency:
2. Move the Transparency slider to the right to make the object or object type more transparent or to the left to make
it less transparent.
Defining the Visibility Scale
You can define a visibility range for object types. An object is visible only if the scale, as displayed on the Map toolbar, is within
this range. This can be used to, for example, prevent the map from being cluttered with symbols when you are at a certain
scale.
25

Forsk 2011
Visibility ranges are taken into account for screen display, and for printing and previewing printing. They do not affect which
objects are considered during calculations.
To define an object visibility range:
2. Enter a Visibility Scale minimum in the between 1: text box.
3. Enter a Visibility Scale maximum in the and 1: text box.
Defining the Object Type Label
For most object types, such as sites and transmitters, you can display information about each object in the form of a label that
is displayed with the object. You can display information from every field in that object types data table, including from fields
that you add.
To define a label for an object type:
2. Click the Browse button (
) beside the Label box. The Field Selection dialogue appears (see Figure 1.6).
Figure 1.6: Defining a label

3. Select the fields which you want to display in the label:
a. To select a field to be displayed in the label for the object type, select the field in the Available Fields list and click
to move it to the Selected Fields list.
b. To remove a field from the Selected Fields list, select the field in the Selected Fields list and click
it.
to remove
c. To change the order of the fields, select a field and click or to move it up or down in the list. The objects will
be grouped in the order of the fields in the Selected Fields list, from top to bottom.
4. Click OK to close the Field Selection dialogue and click OK to close the Properties dialogue.
For most object types, you can also display object information in the form of tip text that
is only visible when you move the pointer over the object. This option has the advantage
of not filling the map window with text. For more information on tip text, see "Defining the
Object Type Tip Text" on page 26.
Defining the Object Type Tip Text
For most object types, such as sites and transmitters, you can display information about each object in the form of tip text
that is only visible when you move the pointer over the object. You can display information from every field in that object
types data table, including from fields that you add.
In the Explorer window, the tip text displays the total numbers of elements present in the Sites and Transmitters folders, and
the view.
26

AT310_UMU_E0
To define tip text for an object type:

) beside the Tip Text box. The Field Selection dialogue appears (see Figure 1.6).
3. Select the fields which you want to display in the tip text:
a. To select a field to be displayed in the tip text for the object type, select the field in the Available Fields list and
click
to move it to the Selected Fields list.
b. To remove a field from the the Selected Fields list, select the field in the Selected Fields list and click
remove it.
to
For most object types, you can also display object information in the form of a label that is
displayed with the object. This option has the advantage of keep object-related information permanently visible. For more information on tip text, see "Defining the Object Type
Label" on page 26.
Once you have defined the tip text, you must activate the tip text function before it appears.
To display tip text:
Click the Display Tips button (
) on the toolbar. Tip text will now appear when the pointer is over the object.
If you have more than one coverage prediction displayed on the map, the tip text displays the tip text for all the coverage
predictions available on a pixel up to a maximum of 30 lines. You can change this default maximum using an option in the
atoll.ini file. For more information, see the Administrator Manual.
Adding an Object Type to the Legend
You can display the information defined by the display type (see "Defining the Display Type" on page 24) in your Atoll documents legend. Only visible objects appear in the Legend window. For information on displaying or hiding objects, see
"Displaying or Hiding Objects on the Map Using the Explorer" on page 18.
In Figure 1.7, on the Display tab of a signal level prediction, the intervals defined are:
Signal level >= -65

red
-65 > Signal level >= -105 shading from red to blue (9 intervals)
Signal level < -105
not shown in the coverage.
The entries in the Legend column will appear in the Legend window.
Figure 1.7: Defined thresholds as they will appear in the Legend

With value intervals, you can enter information in the Legend column to be displayed on the legend. If there is no information
entered in this column, the maximum and minimum values are displayed instead.
2. Select the Add to legend check box. The defined display will appear on the legend.
To display the Legend window:
Select View > Legend Window. The Legend window appears.
You can also display the comments defined in the properties of a coverage prediction in the Legend window by setting an
option in the atoll.ini file. For more information about setting options in the atoll.ini file, see the Administrator Manual.
27

Forsk 2011
1.3.3.2 Examples of Using the Display Properties of Objects

In this section are the following examples of how display properties of objects can be used:
"Automatic Display Type - Server Coverage Predictions" on page 28

"Shading - Signal Level Coverage Prediction" on page 28.
Automatic Display Type - Server Coverage Predictions

When making a best server prediction, Atoll calculates, for each pixel on the map, which server is received the best. If the
selected display type for transmitters is "Automatic," Atoll colours each pixel on the map according to the colour of the transmitter that is best received on that pixel. This way, you can identify immediately which transmitter is best received on each
pixel. The following two figures show the results of the same best server area and handover margin coverage prediction.
In Figure 1.8, the transmitter display type is "Discrete Values," with the site name as the chosen value. The difference in colour
is insufficient to make clear which transmitter is best received on each pixel. In Figure 1.9, the transmitter display type is
"Automatic." Because Atoll ensures that each transmitter has a different colour than the transmitters surrounding it, the
prediction results are also immediately visible.
Figure 1.8: Value interval display type
Figure 1.9: Automatic display type
To display the results of a server coverage prediction with the transmitters set to the automatic display type:
1. Right-click the Transmitters folder in the Explorer window. The context menu appears.
3. Select the Display tab.
4. Select "Automatic" as the Display Type.
5. Click OK.
6. Click the Refresh button (
) to update the display of the prediction results.
Shading - Signal Level Coverage Prediction

Atoll displays the results of a signal level prediction as value intervals. On the map, these value intervals appear as differences
of shading. You can use the Shading command to define the appearance of these value intervals to make the results easier to
read or more relevant to your needs. For example, you can change the range of data displayed, the interval between each
break, or you can change the colours to make the intervals more visible.
In this example, Figure 1.10 shows the results of the best signal level plot from -60 dBm to -105 dBm. However, if you are more
interested in reception from -80 dBm to -105 dBm, you can change the shading to display only those values. The result is visible in Figure 1.11.
28

AT310_UMU_E0
Figure 1.10: Shading from -60 dBm to -105 dBm
Figure 1.11: Shading from -80 dBm to -105 dBm
To change how the results of a signal level coverage prediction are displayed:
1. Expand the Predictions folder in the Explorer window and right-click the signal level prediction. The context menu
appears.
4. Click Actions to display the menu and select Shading. The Shading dialogue appears.
5. Change the value of the First Break to "-80". Leave the value of the Last Break at "-105."
6. Click OK to close the Shading dialogue.
7. Click OK to close the Properties dialogue and apply your changes.
1.4 Working with Maps

Atoll has the following functions to help you work with maps:
"Changing the Map Scale" on page 29

"Moving the Map in the Document Window" on page 30
"Using the Panoramic Window" on page 30
"Centring the Map Window on an Object" on page 31
"Centring the Map Window on a Table Record" on page 31
"Adjusting the Map Window to a Selection" on page 31
"Measuring Distances on the Map" on page 32
"Displaying Rulers Around the Map" on page 32
"Displaying the Map Legend" on page 32
"Using Zones in the Map Window" on page 33
"Editing Polygons, Lines, and Points" on page 39
"Saving a Map as a Graphic Image" on page 45
"Copying a Map to Another Application" on page 45.
"Map Window Pointers" on page 46.
1.4.1 Changing the Map Scale

You can change the scale of the map by zooming in or out, by zooming in on a specific area of the map, or by choosing a scale.
Atoll also allows you to define a zoom range outside of which certain objects are not displayed (see "Defining the Visibility
Scale" on page 25).
1.4.1.1 Zooming In and Out

Atoll offers several tools for zooming in and out on the map. When you zoom in or out on the map, you do so based on the
position of the cursor on the map.
To zoom in on the map:
1. Click the Zoom icon (
) on the Map toolbar (or press CTRL+Q).
2. Click the map where you want to zoom in.
29

Forsk 2011
You can also zoom in by pressing CTRL++, by selecting Zoom > Zoom In from the View
menu, or by holding down the CTRL key and rotating the mouse wheel button forward.
To zoom out on the map:

1. Click the Zoom icon (
) on the Map toolbar (or press CTRL+Q).
2. Right-click the map where you want to zoom out.

You can also zoom out by pressing CTRL+, by selecting Zoom > Zoom Out from the View
menu, or holding down the CTRL key and rotating the mouse wheel button backward.
1.4.1.2 Zooming In on a Specific Area

To zoom in on a specific area of the map:
1. Click the Zoom Area icon (
) on the Map toolbar (or press CTRL+W).
2. Click in the map on one of the four corners of the area you want to select.
3. Drag to the opposite corner. When you release the mouse button, Atoll zooms in on the selected area.
1.4.1.3 Choosing a Scale

To choose a scale:
1. Click the arrow next to the scale box (
) on the Map toolbar.
2. Select the scale from the list.

If the scale value you want is not in the list:
1. Click in the scale box (
) on the Map toolbar.
2. Enter the desired scale.

3. Press ENTER. Atoll zooms the map to the entered scale.
1.4.1.4 Changing Between Previous Zoom Levels

Atoll saves the last five zoom levels, allowing you to move quickly between previous zoom levels and zoomed areas.
To move between zoom levels:
Click the Previous Zoom button (
) to return to a zoom level you have already used (or press ALT + ).
Once you have returned to a previous zoom level, click the Next Zoom button (
) to return to the latest zoom level
(or press ALT + ).
1.4.2 Moving the Map in the Document Window

You can move the map in the document window using the mouse.
To move the map in the document window:
1. Click the Move Map Window button (
) on the Map toolbar (or press CTRL + D).
2. Move the pointer over the map and drag the map in the desired direction.
1.4.3 Using the Panoramic Window

The Panoramic window displays the entire map with all of the imported geographic data. A dark rectangle indicates what part
of the geographic data is presently displayed in a document window, helping you situate the displayed area in relation to the
entire map.
You can use the Panoramic window to:
30
Zoom in on a specific area of the map

Resize the displayed map area

AT310_UMU_E0
Move around the map.
To zoom in on a specific area of the map:

1. Click in the Panoramic window on one of the four corners of the area you want to zoom in on.
2. Drag to the opposite corner. When you release the mouse button, Atoll zooms in on the selected area.
To resize the displayed map area:
1. Click in the Panoramic window on a corner or border of the zoom area (i.e., the dark rectangle).
2. Drag the border to its new position.
To move around the map:
1. Click in the zoom area (i.e., the dark rectangle) in the Panoramic window.
2. Drag the rectangle to its new position.
1.4.4 Centring the Map Window on an Object

You can centre the map on any selected object, for example, a transmitter, a site, or on any zone in the Zones folder on the
Geo tab of the Explorer window. When centring the Map window on an object the current scale is kept.
You can select the object in the map window or in the Explorer window.
To centre the map window on a selected object:
1. Right-click the object in the map window or in the Explorer window.
2. Select Centre in Map Window from the context menu.
If you want to quickly find an object, such as a site, on the map, you can select it in the
Explorer window and then select the Centre in Map Window command.
1.4.5 Centring the Map Window on a Table Record

You can centre the map on any record in the following tables:
Sites table
Transmitters table
Any vector table.
When centring the Map window on an object the current scale is kept.
To centre the map window on a table record:
1. Open the table.
2. Right-click the record. The context menu appears.
3. Select Centre in Map Window from the context menu.
1.4.6 Adjusting the Map Window to a Selection

You can adjust the Map window to display the contents of the Sites folder (or of a view), or a set of measurement data points
or any object or zone on the Geo tab of the Explorer window. When you adjust the Map window to display a selection, Atoll
optimises the display by changing the scale and position so that the selection (for example, the sites) is completely displayed
in the Map window.
To adjust the map window to a folder an object on the Geo tab of the Explorer window:
1. Right-click the folder or object in the Explorer window. The context menu appears.
2. Select Adjust Map Window from the context menu.
You can also adjust the Map window to a record (polygon or line) in a vector table. The
Map window is then adjusted so that the polygon (or line) entirely occupies the displayed
map.
31

Forsk 2011
1.4.7 Measuring Distances on the Map

You can measure distances on the map by using the Distance Measurement tool. The Distance Measurement tool also gives
you the azimuth of a straight line between two points. You can also use the Distance Measurement tool to measure distance
along a line with several points. Atoll will then give you the distance between each point (as you measure), the azimuth of
each segment between two points, and the total distance.
To measure a distance on the map between two points:
1. Click the Distance Measurement button (
) on the toolbar.
2. Click the first point on the map once.

As you move the pointer away from the first point, Atoll marks the initial position and connects it to the pointer with
a line.
3. Place the pointer over the second point on the map. The status bar displays the following (see Figure 1.12):
-
The distance between the two points

The azimuth between the two points.
To measure the total distance on the map on a line over a series of points:
1. Click the Distance Measurement button (
) on the toolbar.
2. Click the first point on the map once.

As you move the pointer away from the first point, Atoll marks the initial position and connects it to the pointer with
a line.
3. Click once on the map at each point on the line between the first point and the final point, where you will have to
change direction on the line.
4. When you reach the last point on the line, the status bar displays the following (see Figure 1.12):
-
The total distance between the first point and the last point
The distance between the second-last point and the last point
The azimuth between the last two points.
Total distance between

Azimuth between secondfirst and last point
last and last point
Distance
between
second-last and last point
Figure 1.12: Measurement data in the status bar
1.4.8 Displaying Rulers Around the Map

You can display rulers around the map in the document window.
To display rulers:
1. Select Document > Preferences. The Preferences dialogue appears.
2. In the Preferences dialogue, click the Coordinates tab.
3. Under Display rulers, select where you want the rulers to be displayed in the map window.
4. Click OK.
1.4.9 Displaying the Map Legend

You can display a map legend. The legend will contain the information on the object types that you have added to it. For information on adding object types to the legend, see "Adding an Object Type to the Legend" on page 27.
To display the legend:
32
Select View > Legend Window.

AT310_UMU_E0
1.4.10 Using Zones in the Map Window

On the Geo tab of the Explorer window, Atoll provides you with a set of tools known as zones. The zones are a type of polygon,
which can be created and modified in the same way as contours, lines, or points. Zones can be used to define areas of the map
for the following purposes:
Filtering Zone: The filtering zone is a graphical filter that restricts the objects displayed on the map and on the
Network tab of the Explorer window to the objects inside the filtering zone. It also restricts which objects are used in
calculations such as coverage predictions, etc.
Computation Zone: The computation zone is used to define which base stations are to be taken into consideration in calculations and the area where Atoll calculates path loss matrices, coverage predictions, etc.
Focus Zone and Hot Spots: With the focus zone and hot spots, you can select the areas of coverage predictions
or other calculations on which you want to generate reports and results.
Printing Zone: The printing zone allows you to define the area to be printed.
Geographic Export Zone: The geographic export zone is used to define part of the map to be exported as a bitmap.
Zones are taken into account whether or not they are visible. In other words, if you have
drawn a zone, it will be taken into account whether or not its visibility check box in the
Zones folder of the Geo tab in the Explorer window is selected. For example, if you have
filtered the sites using a filtering zone, the sites outside the filtering zone will not be
taken into consideration in coverage predictions, even if you have cleared the filtering
zones visibility check box. You will have to delete the zone if you no longer want to select
sites using a filtering zone.
"Using a Filtering Zone" on page 33

"Using a Computation Zone" on page 34
"Using a Focus Zone or Hot Spots" on page 35
"Using Polygon Zone Editing Tools" on page 36
"Using a Printing Zone" on page 38
"Using a Geographic Export Zone" on page 38.
1.4.10.1 Using a Filtering Zone

The filtering zone is a graphical filter that restricts the objects displayed on the map and on the Network tab of the Explorer
window to the objects inside the filtering zone. It also restricts which objects are used in calculations such as coverage predictions, etc. By limiting the number of sites, you can reduce the time and cost of calculations and make visualisation of data
objects on the map clearer.
The filtering zone is taken into account whether or not it is visible. In other words, if you have drawn a zone, it will be taken
into account whether or not its visibility check box in the Zones folder of the Geo tab in the Explorer window is selected. You
will have to delete the zone if you no longer want to select sites using a filtering zone.
1.4.10.1.1
Creating a Filtering Zone

To create a filtering zone:
1. Click the Geo tab of the Explorer window.
2. Click the Expand button (
) to the left of Zones folder to expand the folder.
3. Right-click the Filtering Zone folder.

4. Select Draw from the context menu.
5. Draw the filtering zone:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
The filtering zone is delimited by a blue line. The data objects outside of the selected zone are filtered out. On the
Network tab of the Explorer window, any folder whose content is affected by the filtering zone appears with a special
icon (
), to indicate that the folder contents have been filtered.
33

Forsk 2011
You can also create a filtering zone as follows:
Vector Editor toolbar: You can use the New Polygon (

) and New Rectangle (
) buttons available in the Vector
Editor toolbar to draw the filtering zone.
Existing polygon: You can use any existing polygon as a filtering zone by right-clicking it on the map or in the Explorer
window and Use As > Filtering Zone from the context menu. You can also combine an existing filtering zone with any
existing polygon by right-clicking it on the map or in the Explorer window and selecting Add To > Filtering Zone from
the context menu.
Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative
area, you can import it and use it as a filtering zone. You can import it by right-clicking the Filtering Zone folder on the
Geo tab and selecting Import from the context menu.
Fit to Map Window: You can create a filtering zone the size of the map window by right-clicking the Filtering Zone
folder on the Geo tab and selecting Fit to Map Window from the context menu.
Once you have created a filtering zone, you can use Atolls polygon editing tools to edit it. For more information on the polygon editing tools, see "Using Polygon Zone Editing Tools" on page 36.
You can save the filtering zone, so that you can use it in a different Atoll document, in the
following ways:
Saving the filtering zone in the user configuration: For information on saving the
fiiltering zone in a user configuration, see "Saving a User Configuration" on
page 76.
Exporting the filtering zone: You can export the filtering zone by right-clicking the
Filtering Zone on the Geo tab of the Explorer window and selecting Export from
the context menu.
1.4.10.2 Using a Computation Zone

The computation zone is used to define the area where Atoll carries out calculations. When you create a computation zone,
Atoll carries out the calculation for all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Therefore, it takes into consideration base stations inside and base stations outside the computation zone if they have an influence on the computation
zone. In addition, the computation zone defines the area within which the coverage prediction results will be displayed.
When working with a large network, the computation zone allows you to restrict your coverage predictions to the part of the
network you are currently working on. By allowing you to reduce the number of base stations studied, Atoll reduces both the
time and computer resources necessary for calculations. As well, by taking into consideration base stations within the computation zone and base stations outside the computation zone but which have an influence on the computation zone, Atoll gives
you realistic results for base stations that are close to the border of the computation zone.
If there is no computation zone defined, Atoll makes its calculations on all base stations that are active and filtered and for
the entire extent of the geographical data available.
The computation zone is taken into account whether or not it is visible. In other words, if you have drawn a computation zone,
it will be taken into account whether or not its visibility check box in the Zones folder of the Geo tab in the Explorer window
is selected. You will have to delete the computation zone if you no longer want to define an area for calculations.
1.4.10.2.1
Creating a Computation Zone

To create a computation zone:
1. Click the Geo tab in the Explorer window.
) to expand the Zones folder.
3. Right-click the Computation Zone. The context menu appears.

5. Draw the computation zone:
The computation zone is delimited by a red line.
You can also create a computation zone as follows:
34

Editor toolbar to draw the computation zone.

AT310_UMU_E0
Existing polygon: You can use any existing polygon as a computation zone by right-clicking it on the map or in the
Explorer window and selecting Use As > Computation Zone from the context menu. You can also combine an existing
computation zone with any existing polygon by right-clicking it on the map or in the Explorer window and selecting
Add To > Computation Zone from the context menu.
area, you can import it and use it as a computation zone. You can import it by right-clicking the Computation Zone on
the Geo tab and selecting Import from the context menu.
Fit to Map Window: You can create a computation zone the size of the map window by right-clicking the Computation
Zone on the Geo tab and selecting Fit to Map Window from the context menu.
Once you have created a computation zone, you can use Atolls polygon editing tools to edit it. For more information on the
polygon editing tools, see"Using Polygon Zone Editing Tools" on page 36.
You can save the computation zone, so that you can use it in a different Atoll document,
in the following ways:
Saving the computation zone in the user configuration: For information on saving
the computation zone in a user configuration, see "Saving a User Configuration" on
page 76.
Exporting the computation zone: You can export the computation zone by rightclicking the Computation Zone on the Network tab of the Explorer window and
selecting Export from the context menu.
1.4.10.3 Using a Focus Zone or Hot Spots

Using the focus zone and hot spots, you can define an area on which statistics can be drawn and on which reports are made.
While you can only have one focus zone, you can define several hot spots in addition to the focus zone.
It is important not to confuse the computation zone and the focus and hot spots. The computation zone defines the area
where Atoll calculates path loss matrices, coverage predictions, etc., while the focus and hot spots are the areas taken into
consideration when generating reports and results.
Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation
zone. However, by using a focus zone for the report, you can display the statistics for a specific number of sites, instead of
displaying statistics for every site that has been calculated.
Atoll takes the focus zone and hot spots into account whether or not they are visible. In other words, if you have drawn a focus
zone or hot spot, it will be taken into account whether or not its visibility check box in the Zones folder of the Geo tab in the
Explorer window is selected. You will have to delete the zone if you no longer want to define an area for reports.
A focus zone can consist of more than one polygon. The polygons of a focus zone must not
intersect or overlap each other.
1.4.10.3.1
Drawing a Focus Zone or a Hot Spot

To define a focus zone or a hot spot:
3. Right-click the Focus Zone or Hot Spots folder, depending on whether you want to create a focus zone or a hot spot.
The context menu appears.
5. Draw the focus zone or hot spot:
A focus zone is delimited by a green line; a hot spot is delimited by a heavy black line. If you clear the zones visibility
check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken
into account.
You can also create a focus zone or hot spot in one of the following ways:

Editor toolbar to draw the focus zone or hot spot.
35

Forsk 2011
Existing polygon: You can use any existing polygon as a focus zone or hot spot by right-clicking it on the map or in the
Explorer window and selecting Use As > Focus Zone or Use As > Hot Spot from the context menu. You can also combine an existing focus zone or hot spot with any existing polygon by right-clicking it on the map or in the Explorer
window and selecting Add To > Hot Spot or Add To > Hot Spot from the context menu.
area, you can import it and use it as a focus zone or hot spot. You can import it by right-clicking the Focus Zone or Hot
Spots folder on the Geo tab and selecting Import from the context menu. When you import hot spots, you can import
the name (in text format) given to each zone as well. Additionally, because you can have several hot spots, you can
import more than one polygon into the Hot Spot folder, with each as a separate hot spot.
Fit to Map Window: You can create a focus zone or hot spot the size of the map window by right-clicking the Focus
Zone or Hot Spots folder on the Geo tab and selecting Fit to Map Window from the context menu.
You can save the focus zone or hot spot, so that you can use it in a different Atoll document, in the following ways:
Saving the focus zone in the user configuration: For information on saving the
focus zone in a user configuration, see "Saving a User Configuration" on page 76.
Exporting the focus zone or hot spots: You can export the focus zone or hot spots
by right-clicking the Focus Zone or the Hot Spots folder on the Geo tab of the
Explorer window and selecting Export from the context menu.
1.4.10.4 Using Polygon Zone Editing Tools

Atoll provides you with several different ways of editing the computation zone, focus zone, hot spots, and filtering zones. You
can edit these zones by editing the points that define them, by combining several polygons, or by deleting parts of the polygons that make up these zones. When you no longer need the zone, you can delete it from the map.
The computation, focus and hot spot polygons can contain holes. The holes within polygonal areas are differentiated from
overlaying polygons by the order of the coordinates of their vertices. The coordinates of the vertices of polygonal areas are in
clockwise order, whereas the coordinates of the vertices of holes within polygonal areas are in counter-clockwise order.
1.4.10.4.1
"Editing Polygon Zones" on page 36

"Removing a Polygon Zone" on page 38.
Editing Polygon Zones

Atoll enables you to edit a polygon zone in several different ways. The first step in editing a polygon zone is selecting it, either
by:
Selecting the polygon zone in the Zones folder of the Geo tab of the Explorer window
Selecting the polygon zone by clicking it on the map, or
Selecting the polygon zone from the list in the Vector Editor toolbar.
Once you have selected the polygon zone, you can edit it as explained in the following sections:
"Editing the Points of a Polygon Zone" on page 36

"Editing Polygon Zones Using the Toolbar" on page 37
"Editing Polygon Zones Using the Context Menu" on page 37.
Editing the Points of a Polygon Zone

To edit a point of a polygon zone:
1. Put the polygon zone in editing mode as explained in "Editing Polygon Zones" on page 36.
2. Select the polygon zone. You can now edit it by:
-
Moving a point:
i.
Position the pointer over the point you want to move. The pointer changes (
).
ii. Drag the point to its new position.

-
Adding a point to the polygon zone:

i.
Position the pointer over the polygon zone border where you want to add a point. The pointer changes (
).
ii. Right-click and select Insert Point from the context menu. A point is added to the polygon zone border at the
position of the pointer.
-
36
Deleting a point from a polygon zone:

AT310_UMU_E0
i.
Position the pointer over the point you want to delete. The pointer changes (
).
ii. Right-click and select Delete Point from the context menu. The point is deleted.
Editing Polygon Zones Using the Toolbar
In Atoll, you can create complex polygon zones by using the tools on the Vector Editor toolbar. The filtering, computation,
and focus zone polygons can contain holes. The holes within polygonal areas are differentiated from overlaying polygons by
the order of the coordinates of their vertices. The coordinates of the vertices of polygonal areas are in clockwise order,
whereas the coordinates of the vertices of holes within polygonal areas are in counter-clockwise order.
To edit a polygon zone using the icons on the Vector Editor toolbar:
1. Put the polygon zone in editing mode as explained in "Editing Polygon Zones" on page 36.
2. Click the contour to edit. The Vector Editor toolbar has the following buttons:
-
: To combine several polygon zones:

i.
In the Vector Editor toolbar, click the Combine button (
).
ii. Click once on the map where you want to begin drawing the new polygon zone.
iii. Click each time you change angles on the border defining the outside of the polygon zone.
iv. Double-click to close the polygon zone.
v. Draw more polygon zones if desired. Atoll creates a group of polygons of the selected and new contours. If
polygon zones overlap, Atoll merges them.
-
: To delete part of the selected polygon zone:

i.
In the Vector Editor toolbar, click the Delete button (
).
ii. Draw the area you want to delete from the selected polygon zone by clicking once on the map where you want
to begin drawing the area to delete.
iii. Click each time you change angles on the border defining the outside of the area.
iv. Double-click to close the area. Atoll deletes the area from the selected contour.
-
: To create a polygon out of the overlapping area of two polygons:

i.
In the Vector Editor toolbar, click the Intersection button (
).
ii. Click once on the map where you want to begin drawing the polygon that will overlap the selected one.
iii. Click each time you change angles on the border defining the outside of the polygon.
iv. Double-click to close the polygon. Atoll creates a new polygon of the overlapping area of the two polygons
and deletes the parts of the polygons that do not overlap.
-
: To split the selected polygon into several polygons:

i.
In the Vector Editor toolbar, click the Split button (
).
ii. Click once on the map where you want to begin drawing the polygon that will split the selected one.
iii. Click each time you change angles on the border defining the outside of the polygon.
iv. Double-click to close the polygon. Atoll separates the area covered by the polygon from the selected polygon
and creates a new polygon.
Editing Polygon Zones Using the Context Menu
When you are editing polygon zones, you can access certain commands using the context menu.
To edit a polygon zone using the context menu:
1. Click the polygon zone you want to edit.
2. Right-click the polygon zone to display the context menu and select one of the following:
-
Properties: Select Properties to open the Properties dialogue of the selected polygon zone. The Properties dialogue gives the coordinates of each point that defines the position and shape of the polygon zone.
Insert Point: Select Insert Point to add a point to the border of the contour at the position of the pointer.
Move:
i.
Select Move from the context menu to move the contour, line, or point on the map.
37

Forsk 2011
ii. Move the contour, line, or point.

iii. Click to place the contour, line, or point.
1.4.10.4.2
Quit edition: Select Quit Edition to exit editing mode.
Delete: Select Delete to remove the selected contour, line, or point from the map.
Removing a Polygon Zone

When you no longer need a polygon zone, you can remove the zone and redisplay all data objects.
To remove a polygon zone:
) to the left of Zones folder to expand the folder.
3. Right-click the folder containing the zone you want to remove.

4. From the context menu, select Delete Zone. The polygon zone is removed and all document data are now displayed.
You can also delete it by right-clicking its border on the map and selecting Delete from
the context menu.
1.4.10.5 Using a Printing Zone

The printing zone allows you to define the area to be printed. For information on using the printing zone, see "Defining the
Printing Zone" on page 61.
1.4.10.6 Using a Geographic Export Zone

If you want to export part of the map as a bitmap, you can define a geographic export zone. After you have defined a
geographic export zone, Atoll offers you the option of exporting only the area covered by the zone if you export the map as
a raster image.
To define a geographic export zone:
3. Right-click the Geographic Export Zone folder. The context menu appears.
5. Draw the geographic export zone:
a. Click the point on the map that will be one corner of the rectangle that will define the geographic export zone.
b. Drag to the opposite corner of the rectangle that will define the geographic export zone. When you release the
mouse, the geographic export zone will be created from the rectangle defined by the two corners.
The geographic export zone is delimited by a light purple line . If you clear the geographic export zones visibility check
box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into
account.
You can also create a geographic export zone as follows:

Editor toolbar to draw the geogaphic export zone.
Existing polygon: You can use any existing polygon as a geographic export zone by right-clicking it on the map or in
the Explorer window and selecting Use As > Geographic Export Zone from the context menu. You can also combine
an existing geographic export zone with any existing polygon by right-clicking it on the map or in the Explorer window
and selecting Add To > Geographic Export Zone from the context menu. The "effective" geographic export zone will
be the rectangle encompassing the several polygons composing the geographic export zone.
Importing a polygon: If you have a file with an existing polygon, you can import it and use it as a geographic export
zone. You can import it by right-clicking the Geographic Export Zone folder on the Geo tab and selecting Import from
the context menu.
Fit to Map Window: You can create a geographic export zone the size of the map window by right-clicking it on the
map or in the Explorer window and selecting Fit to Map Window from the context menu.
Once you have created a geographic export zone, you can use Atolls polygon editing tools to edit it. For more information on
the polygon editing tools, see "Using Polygon Zone Editing Tools" on page 36.
38

AT310_UMU_E0
You can save the geographic export zone, so that you can use it in a different Atoll document, in the following ways:
Saving the geographic export zone in the user configuration: For information on
saving the geographic export zone in a user configuration, see "Saving a User Configuration" on page 76.
Exporting the geographic export zone: You can export the geographic export zone
by right-clicking the Geographic Export Zone on the Geo tab of the Explorer
window and selecting Export from the context menu.
The geographic export zone can only export in raster format. You can not export in raster
format if the coverage prediction was made per transmitter (for example, coverage
predictions with the display type set by transmitter, by a transmitter attribute, by signal
level, by path loss, or by total losses). Only the coverage area of a single transmitter can
be exported in raster format.
1.4.11 Editing Polygons, Lines, and Points

Atoll uses different types of polygons, lines, and points in the map window. For example, the zones such as the computation,
focus zone and hot spot, described in "Using Zones in the Map Window" on page 33, are specific types of polygons. Another
type of polygon, called contours, can along with lines and points, be used to add additional information to geographic data.
Atoll provides you with several different ways of editing the polygons, lines, and points. You can move or delete the points
that define polygons, lines, and points. You can edit polygons by editing the points that define them, by combining several
polygons, or by deleting parts of the polygons.
Polygons, including the computation, focus zone and hot spot polygons can contain holes. The holes within polygonal areas
are differentiated from overlaying polygons by the order of the coordinates of their vertices. The coordinates of the vertices
of polygonal areas are in clockwise order, whereas the coordinates of the vertices of holes within polygonal areas are in counter-clockwise order.
When you no longer need the polygon, line, or point, you can delete it from the map.
In this section, the different ways of editing polygons, lines, and points are explained:
"Adding a Vector Layer" on page 39

"Creating Polygons, Lines, and Points" on page 39
"Editing the Shape of Polygons and Lines" on page 40
"Combining or Cropping Polygons Using the Toolbar" on page 41
"Editing a Point" on page 41
"Editing Contours, Lines, and Points Using the Context Menu" on page 42.
1.4.11.1 Adding a Vector Layer

You can add vector objects such as polygons, lines or points to geographical map information in a project by first creating a
vector layer. You can also modify certain geographic data maps, for example, population maps, and custom data, by adding a
vector layer to them and afterwards adding polygons, lines and points. For information on modifying certain geographic data
maps by adding a vector layer, see "Editing Population or Custom Data Maps" on page 135.
To add a vector layer to the Geo tab:
Click the New Vector Layer button (
) ) on the Vector Editor toolbar.
Atoll creates a folder called "Vectors" on the Geo tab of the Explorer window.
For information on adding vector objects such as contours, lines, and points to the vector layer, see "Creating Polygons, Lines,
and Points" on page 39.
1.4.11.2 Creating Polygons, Lines, and Points

Once you have created a vector layer, as explained in "Adding a Vector Layer" on page 39, you can add polygons, lines, and
points to it.
To add a polygon, line, or point to a vector layer:
1. Right-click the vector layer on the Geo tab. The context menu appears.
2. Select Edit from the context menu. The tools on the Vector Editor toolbar are available.
39

Forsk 2011
You can also make the vector tools available by selecting the vector layer to edit from
the Vector Editor toolbar list. Because Atoll names all new vector layers "Vectors" by
default, it might be difficult to know which Vectors folder you are selecting. By renaming
each vectors folder, you can ensure that you select the correct folder. For information on
renaming objects, see "Renaming an Object" on page 19.
If the Vector Editor toolbar is not visible, select View > Toolbars > Vector Editor.
3. Click one of the following buttons on the Vector Editor toolbar:
New Polygon:
a. Click once on the map where you want to begin drawing the contour.
b. Click each time you change angles on the border defining the outside of the contour.
c. Double-click to close the contour.
New Rectangle:
a. Click the point on the map that will be one corner of the rectangle.
b. Drag to the opposite corner of the rectangle.
c. Release the mouse to create the rectangle defined by the two corners.
If the polygon or rectangle is on the vector layer of a population map, or custom data, you
must define the value the polygon or rectangle represents and map the vector layer. For
more information, see "Editing Population or Custom Data Maps" on page 135.
New Line:
a. Click once on the map where you want to begin the line.
b. Click each time you change angles on the line.
c. Double-click to end the line.
New Point: Click once on the map where you want to place the point.
4. Press ESC to deselect the currently selected button on the Vector Editor toolbar.
1.4.11.3 Editing the Shape of Polygons and Lines

You can edit the shape of polygons and lines on the vector layer.
To edit the shape of polygons and lines:
1. On the Explorer window tab containing the vector layer, right-click the vector layer folder. The context menu appears.
2. Select Edit from the context menu. The vector tools on the Vector Editor toolbar are activated.
You can also activate the vector tools by selecting the vector layer to edit from the
Vector Editor toolbar list.
3. Select the contour or line. You can now edit by:

-
Moving a point:
i.
).
ii. Drag the point to its new position. If you are editing a rectangle, the adjacent points on the rectangle change
position as well, in order for the rectangle to retain its shape.
-
Adding a point to a contour or a line:

i.
Position the pointer over the contour border or line where you want to add a point. The pointer changes (
).
ii. Right-click and select Insert Point from the context menu. A point is added to the contour border or line at the
position of the pointer.
40

AT310_UMU_E0
Deleting a point from a contour or a line:

i.
).
1.4.11.4 Combining or Cropping Polygons Using the Toolbar

In Atoll, you can create complex contours by using the tools on the Vector Editor toolbar.
To edit a vector object using the icons on the Vector Editor toolbar:
3. Click the contour to edit. The Vector Editor toolbar has the following buttons:
-
: To combine several contours:

i.
In the Vector Editor toolbar, click the Combine button (
).
ii. Click once on the map where you want to begin drawing the new contour.
iii. Click each time you change angles on the border defining the outside of the contour.
iv. Double-click to close the contour.
v. Draw more contours if desired. Atoll creates a group of polygons of the selected and new contours. If contours
overlap, Atoll merges them.
-
: To delete part of the selected contour:

i.
In the Vector Editor toolbar, click the Delete button (
).
ii. Draw the area you want to delete from the selected contour by clicking once on the map where you want to
begin drawing the area to delete.
iii. Click each time you change angles on the border defining the outside of the area.
iv. Double-click to close the area. Atoll deletes the area from the selected contour.
-
: To create a contour out of the overlapping area of two contours:

i.
In the Vector Editor toolbar, click the Intersection button (
).
ii. Click once on the map where you want to begin drawing the contour that will overlap the selected one.
iv. Double-click to close the contour. Atoll creates a new contour of the overlapping area of the two contours and
deletes the parts of the contours that do not overlap.
-
: To split the selected contour into several contours:

i.
In the Vector Editor toolbar, click the Split button (
).
ii. Click once on the map where you want to begin drawing the contour that will split the selected one.
iv. Double-click to close the contour. Atoll separates the area covered by the contour from the selected contour
and creates a new contour.
1.4.11.5 Editing a Point

To edit a point:
41

Forsk 2011
3. Select the point. You can now edit by:

-
Moving:
i.
Click the point you want to move. The pointer changes (
).

-
Deleting a point:
i.
Click the point you want to delete. The pointer changes (
).
ii. Right-click and select Delete from the context menu. The point is deleted.
1.4.11.6 Editing Contours, Lines, and Points Using the Context Menu
When you are editing contours, lines, and points, you can access certain commands using the context menu.
To edit a vector object using the context menu:
1. Click the vector object you want to edit.
2. Right-click the vector object to display the context menu and select one of the following:
-
Delete: Select Delete to remove the selected contour, line, or point from the map.
Convert to Line: Select Convert to Line to convert the selected contour to a line.
Convert to Polygon: Select Convert to Polygon to convert the selected line to a contour.
Open Line: Select Open Line to remove the segment between the last and the first point.
Close Line: Select Close Line to add a segment between the last and the first point of the line.
Insert Point: Select Insert Point to add a point to the border of the contour at the position of the pointer.
Move:
i.
Select Move from the context menu to move the contour, line, or point on the map.
ii. Move the contour, line, or point.

iii. Click to place the contour, line, or point.
-
Quit edition: Select Quit Edition to exit editing mode.

Properties: Select Properties to open the Properties dialogue of the selected contour, line, or point. The Properties dialogue has two tabs:
-
General: The General tab gives the name of the vector Layer, the Surface of the object, and any Properties of
the contour, line, or point.
Geometry: This tab gives the coordinates of each point that defines the position and shape of the contour,
line, or point.
Only the commands relevant to the selected contour, line, or point are displayed in the
context menu.
1.4.12 Exporting Coverage Prediction Results

In Atoll, you can export the coverage areas of a coverage prediction in raster or vector formats. In raster formats, you can
export in BMP, TIF, JPEG 2000, ArcView grid, or Vertical Mapper (GRD and GRC) formats. When exporting in GRD or GRC
formats, Atoll allows you to export files larger than 2 GB. In vector formats, you can export in ArcView, MapInfo, or AGD
formats. The file exported can then be imported as a vector or raster object in Atoll or in another application.
When you export a coverage prediction in vector format, the exported zone is delimited by the rectangle encompassing the
coverage. When you export a coverage prediction in vector format, you can export the entire coverage prediction, or you can
export a defined area of the coverage prediction.
All coverage types can be exported, however, you can not export a coverage prediction in raster format if the coverage prediction was made per transmitter (for example, coverage predictions with the display type set by transmitter, by a transmitter
attribute, by signal level, by path loss, or by total losses). In this case, only the coverage area of a single transmitter can be
exported in raster format.
42

AT310_UMU_E0
You can export coverage predictions separately or you can export several coverage predictions at the same time. When you
export more than one coverage prediction, Atoll suggests the formats that can be used for all the coverage predictions to be
exported.
"Exporting an Individual Coverage Prediction in Vector Format" on page 43

"Exporting an Individual Coverage Prediction in Raster Format" on page 43
"Exporting Multiple Coverage Predictions" on page 44.
1.4.12.1 Exporting an Individual Coverage Prediction in Vector Format

To export a coverage prediction in vector format:
1. Select the Network tab in the Explorer window.
) to expand the Predictions folder.
The coverage prediction must be displayed in the map window before it can be exported.
For information on displaying objects in the map window, see "Displaying or Hiding Objects
on the Map Using the Explorer" on page 18.
3. Select Export the Coverage from the context menu. The Save As dialogue appears.
4. In the Save As dialogue, enter the File name and select the vector format from the Save as type list.
If you have chosen to export the prediction coverage in a vector format other than in AGD format, you can modify the
coverage prediction export:
a. Coordinate Systems: You can change the reference coordinate system for the file being exported.
b. Resolution: You can change the Resolution of the exported coverage. The default resolution is the resolution of
the coverage prediction results (as set in the coverage prediction Properties dialogue).
c. Filtering: You can apply a filter to the coverage prediction export to fill empty pixels with a value averaged from
surrounding pixels. Define the level of filtering by moving the Filtering slider, or entering the percentage in the
text box.
d. Smoothing: You can smooth the vectors exported by a set percentage by moving the Smoothing slider, or entering
the percentage in the text box.
5. Click Save to export the coverage prediction results.
1.4.12.2 Exporting an Individual Coverage Prediction in Raster Format

To export a coverage prediction in raster format:
The coverage prediction must be displayed in the map window before it can be exported.
For information on displaying objects in the map window, see "Displaying or Hiding Objects
on the Map Using the Explorer" on page 18.
3. You can export the entire coverage prediction, the geographic export zone, or part of the coverage prediction:
To export the entire coverage prediction:
-
Right-click the coverage prediction you want to export.
To export the geographic export zone, define the geographic export zone:
a. Click the Geo tab in the Explorer window.
b. Click the Expand button (
c. Right-click the Geographic Export Zone folder. The context menu appears.
d. Select Draw from the context menu.
e. Draw the geographic export zone by clicking the point on the map that will be one corner of the rectangle that will
define the geographic export zone and dragging to the opposite corner of the rectangle that will define the geographic export zone. When you release the mouse, the geographic export zone will be created from the rectangle
defined by the two corners.
43

Forsk 2011
The geographic export zone is delimited by a light purple line. If you clear the geographic export zones visibility
check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be
taken into account.
f. Right-click the coverage prediction you want to export.
To export part of the coverage prediction:
a. Click the Expand button (
) to expand the coverage prediction.
b. Right-click the part of the coverage prediction you want to export.

5. In the Save As dialogue, enter the File name and select the raster format from the Save as type list.
6. Enter the file name and select the type and the path of the file to be exported.
7. Click Save to export the coverage prediction results. The Raster Export dialogue appears.
a. Under Region, select the area to export:
-
Entire covered area: to export a rectangle containing only the area covered by the study,
Computation zone: to export a rectangle containing the entire computation zone, or
Geographic export zone: to export the rectangle defined by the geographic export zone.
b. If desired, you can apply a filter to the coverage prediction export to fill empty pixels with a value averaged from
surrounding pixels. Define the level of filtering by moving the Filtering slider, or entering the percentage in the
text box.
c. Filtering:
d. Click OK to finish exporting the coverage prediction results.
You can not export in raster format if the coverage prediction was made per transmitter
(for example, coverage predictions with the display type set by transmitter, by a transmitter attribute, by signal level, by path loss, or by total losses). Only the coverage area of a
single transmitter can be exported in raster format.
1.4.12.3 Exporting Multiple Coverage Predictions

If you have several coverage predictions that you want to export, you can export them at the same time.
To export several coverage predictions at the same time:
2. Right-click the the Predictions folder. The context menu appears.
3. Select Export Coverages from the context menu. The Coverage Export dialogue appears.
4. In the Coverage Export dialogue, select the check boxes corresponding to the coverage predictions you want to
export. By default, Atoll selects the check boxes of all coverage predictions whose visibility check box is selected on
the Network tab of the Explorer window.
5. Under Options, you can define the following parameters:
-
Folder: Enter the folder you want to store the exported coverage predictions in or click the Browse button (
)
to navigate to it.
Format: Select the vector file format you want Atoll to export the coverage predictions in.
Time stamp: If you select the Time stamp check box, Atoll will add the date and time to the file name of each
exported coverage prediction.
Resolution in metres: You can define a resolution for the exported coverage predictions.
6. Click Export to export the selected coverage predictions. The selected coverage predictions are saved in the selected
folder.
When you export several coverage predictions at the same time, Atoll does not take the
geographic export zone into consideration. The geographic export zone is only taken into
consideration for raster file formats.
44

AT310_UMU_E0
1.4.13 Saving a Map as a Graphic Image

You can save a map as a graphic image.
To save a map as a graphic image:
1. Select Edit > Select Area.
a. Click in the map on one of the four corners of the area you want to select.
b. Drag to the opposite corner.
2. Select File > Save Image As. The Map Export dialogue appears.
3. In the Map Export dialogue, select the zone that you want to save as an image. You can select:
-
Selection: The area on the map selected in step 1.

Geographic export zone
Printing zone
4. Click Export. The Save As dialogue appears.

5. In the Save as dialogue, select a destination folder, enter a File name, and select a file type from the Save as type list.
The following file formats are supported: TIF, BIL, BMP, and ArcView Grid (TXT). If you want to use the saved file as a
digital terrain model, you should select the TIF, BIL, or TXT format. When saving in BIL format, Atoll allows you to save
files larger than 2 Gb.
6. Click Save. The Exported Image Size dialogue appears.
7. You can define the size of the exported image in one of two ways:
-
Scale: If you want to define the size by scale, select Scale, enter a scale in the text box and a resolution. If you want
to export the image with rulers, select Include Rulers.
Pixel size: If you want to define the size by pixel size, select Pixel size, and enter a pixel size in the text box.
If you want to use the exported file as a digital terrain model, you must define the size of
the exported image by pixel size. Atoll then creates a geo-reference file for the exported
image.
8. Click OK.
1.4.14 Copying a Map to Another Application

You can copy a selected area of the map into a document created using another application.
To copy a selected area of the map into a document created using another application:
1. Select Edit > Select Area
2. Define the area to copy:
a. Click in the map on one of the four corners of the area you want to select.
b. Drag to the opposite corner.
3. Select Edit > Copy Image. The Copy Image dialogue appears.
4. Define the resolution of the image in one of the following ways:
-
Select Use screen resolution

Select Use custom resolution and enter a resolution in metres.
5. Click OK.
6. Open the application into which you want to paste the image.
7. In the new application, select Edit > Paste Special.
8. In the Paste Special dialogue, select Picture (Enhanced Metafile).
You can also select Bitmap to paste the selection without rulers, or Text to paste the upper
left and lower right coordinates of the selection.
9. Click OK. The area of the map, including the rulers, is pasted as an image into the new document.
45

Forsk 2011
1.4.15 Map Window Pointers

In Atoll, the pointer appears in different forms according to its function. Each pointer is described below:
Appearance
Description
Meaning
Selection arrow
The zone selection pointer indicates that, on the map, you can define a zone to print
or copy and, in the Panoramic window, you can define the zone to be displayed on
the map. To define a zone, click and drag diagonally.
Polygon drawing
pointer
The polygon drawing pointer indicates you can draw a zone to filter either sites or
transmitters, draw computation/focus/hot spot/filtering/printing/ geographic
export zones, or draw vector or raster polygons on the map. To draw a polygon, click
once to start, and each time you change angles on the border defining the outside of
the polygon. Close the polygon by clicking twice.
The rectangle drawing pointer indicates you can draw computation/focus/hot spot/
Rectangle drawing
filtering/printing/geographic export zones, or draw vector or raster rectangles on
pointer
the map. To define a zone, click and drag diagonally.
Hand
The hand pointer indicates you can move the visible part of the displayed map.
Zoom tool
The zoom pointer indicates you can click to zoom in and right-click to zoom out at
the location of the mouse pointer
Zoom area
The zoom area pointer indicates you can zoom in on an area of the by clicking and
dragging to define the area.
New transmitter
The transmitter pointer indicates you can place a transmitter on the map where you
click. You can place more than one station by pressing CTRL as you click on the map.
Point analysis
The point analysis pointer indicates that you have selected the Point Analysis tool
and have not yet chosen the first point.
Point placed
(Receiver)
The point placed pointer indicates the position of the receiver on the map that is
used for the point-to-point analysis. The results are displayed in the CW
Measurements or Point Analysis window.
Pencil
The pencil pointer indicates you can create a polygonal clutter zone, by clicking once
to start the polygon, once to create each corner, and by double-clicking to close the
polygon.
Deletion
The deletion pointer indicates that you can delete a newly created polygonal clutter
zone by clicking its border.
Position indicator
The position indicator pointer indicates you can select the border of a polygon.
Right-clicking the polygon border opens a context menu allowing you to add a point,
delete the polygon, or centre the map on the polygon.
Select/create
points
The select/create points pointer indicates you can modify the polygon in the map
window. You can add a new point and modify the polygon contour by clicking on one
of the edges and dragging. You can move an existing point by clicking and dragging
an existing point. You can right-click to open a context menu to delete a point,
delete the polygon, or centre the map on the polygon.
Placing a CW
measurement
point
The first CW measurement point pointer indicates you can click a point on the map
to create the first point of a CW measurement path.
Placing points in a The next CW measurement point pointer indicates the first CW measurement point
CW measurement has been set and you can now click other points on the map. Double-click to end the
path
CW measurement path.
The measurement pointer indicates you can click on the map to set the start point of
Measurements on
your measurement. As you move the pointer, the distance between the first point
the map
and the pointer is displayed in the status bar.
46

AT310_UMU_E0
Appearance
Description
Meaning
Terrain section
The terrain section pointer indicates that you can create a terrain section by clicking
once on the map to create the first point and once more to create the second point.
The terrain profile between the two points is displayed in the Point Analysis window
and stored under Terrain Sections in the Geo tab.
1.5 Working with Data Tables

Atoll stores object data (sites, transmitters, repeaters, antennas, UMTS or CDMA2000 cells, UMTS or CDMA2000 parameters,
etc.) in the form of tables, containing all their parameters and characteristics. The data contained in prediction reports are
also stored in the form of tables.
You can add columns to the data table and you can delete certain columns. When you create a new column, you can create a
default value for a field you create. You can also create a list of options (for text fields) from which the user can choose when
filling in the field.
You can filter, sort, and group the data contained in these tables, and view a statistical analysis of the data. You can also export
the data or import data into the Atoll data tables. The options for working with data tables are available from the context
menu or from the Table toolbar displayed above the table.
"Opening a Data Table" on page 47

"Adding, Deleting, and Editing Data Table Fields" on page 47
"Editing the Contents of a Table" on page 49
"Opening an Objects Record Properties Dialogue from a Table" on page 50
"Defining the Table Format" on page 50
"Copying and Pasting in Tables" on page 54
"Viewing a Statistical Analysis of Table Contents" on page 56
"Exporting Tables to Text Files" on page 57
"Importing Tables from Text Files" on page 58
"Exporting Tables to XML Files" on page 59
"Importing Tables from XML Files" on page 59.
1.5.1 Opening a Data Table

To open a data table:
1. Click the Network or Parameters tab in the Explorer window.
2. Right-click the data folder of which you want to display the data table.
3. Select Open Table from the context menu.
1.5.2 Adding, Deleting, and Editing Data Table Fields

The data for each object type is stored in the form of a data table. Every data table in Atoll is created with a default set of
columns, each corresponding to a field. In this section, the following functions are explained:
"Accessing an Object Types Table Fields" on page 47

"Adding a Field to an Object Types Data Table" on page 48
"Deleting a Field from an Object Types Data Table" on page 49
1.5.2.1 Accessing an Object Types Table Fields

The fields contained in an object types table are defined in a dialogue.
To access an object types table fields:
1. In the Explorer window, open the data table as described in "Opening a Data Table" on page 47.
2. Right-click the table in the map window. The context menu appears.
3. Select Table Fields from the context menu. A dialogue appears where you can view the existing fields and add or
delete new ones.
The dialogue displays the following information for each type of data (see Figure 1.13):
-
The name of the field in the database (Name).

The name of the field as it appears in the ATL file (Legend).
The Type of the field.
47

Forsk 2011
The maximum Size of the field.

The Default value of the field.
The Group to which the field belongs. When opening an Atoll document from a database, you can select a group
of custom fields to be loaded from the database, instead of loading all custom fields.
Figure 1.13: The Table tab
1.5.2.2 Adding a Field to an Object Types Data Table

You can add a custom field to any object types data table.
To add a custom field to an object types data table:
1. Access the object types table fields as explained in "Accessing an Object Types Table Fields" on page 47.
2. Click Add. The Field Definition dialogue appears (see Figure 1.14).
3. The Field Definition dialogue has the following text boxes:
-
Name: Enter the Name for the field that will appear in the database
Group: If desired, you can define a Group that this custom field will belong to. When you open an Atoll document
from a database, you can then select a specific group of custom fields to be loaded from the database, instead of
loading all custom fields.
Legend: Enter the name for the field that will appear in the Atoll document.
Type: Select a type for the field (text, short integer, long integer, single, double, true/false, date/time, or currency)
Size: The Size field is only available if you have selected "text" as the Type. Enter a size in characters.
Default value: If you want, enter a default value that will appear each time you create a new record of this object
type.
Choice list: The Choice list field is only available if you have selected "text" as the Type. You can create a choice
list by entering the list items in the Choice list text box, and pressing ENTER after each list item, if you want,
keeping each on a separate line.
Select the Restricted check box, if you want the custom field to only accept values listed in the Choise list text box.
Clear the Restricted check box, if you want to allow users to enter values other than those in the choice list.
4. Click OK to return to the object type table.

User or custom fields are for information only and are not taken into account in any calculation. You can find these fields on the Other Properties tab of an object types Properties
dialogue.
48

AT310_UMU_E0
Figure 1.14: The Field Definition dialogue
1.5.2.3 Deleting a Field from an Object Types Data Table

You can delete custom fields from an object types data table. Custom fields are the fields that the user adds to an object
types data table, as explained in "Adding a Field to an Object Types Data Table" on page 48.
To delete a custom field from an object types data table:
All data stored in the field will be lost when you delete the field itself. Make sure that you
are not deleting important information.
1. Access the object types table fields as explained in "Accessing an Object Types Table Fields" on page 47.
2. Select the custom field that you want to delete.
Some fields can not be deleted. If you select a field and the Delete button remains
unavailable, the selected field is not a custom field and can not be deleted.
3. Click Delete. The field is deleted from the object types data table.
1.5.3 Editing the Contents of a Table

To edit the contents of a table:
1. Click the Network or Parameters tab in the Explorer window.
2. Right-click the data folder of which you want to display the data table.
4. Edit the content of the table by entering the value directly in the field (see Figure 1.15).
5. Click elsewhere in the table when you have finished updating the table. Your changes are automatically saved.
If a list of options has been defined for a field, you can select a value from the list (see
Figure 1.16) or enter a new value.
49

Forsk 2011
Figure 1.15: Editing data in the transmitters data tables
Figure 1.16: Choosing data in the transmitters data tables
1.5.4 Opening an Objects Record Properties Dialogue from a Table

You can open the Record Properties dialogue of an object, for example, a site, antenna, transmitter, or cell, from its data table.
To open the Record Properties dialogue of an object:
1. Open the data table as explained in "Opening a Data Table" on page 47.
2. Right-click the record whose properties you want to see.
3. Select Record Properties from the context menu.
You can also open the Record Properties dialogue by double-clicking the record. To avoid
editing the record when you double-click, double-click the left margin of the record instead
of the record itself. You can also select the record and click the Record Properties button
(
) in the Table toolbar.
1.5.5 Defining the Table Format

Atoll lets you format the data tables so that the data presented is more legible or better presented. You can change the format
of the data table by:
50
"Formatting the Column Headers" on page 51

AT310_UMU_E0
"Formatting Table Cells" on page 51

"Changing Column Width or Row Height" on page 51
"Displaying or Hiding a Column" on page 52
"Freezing or Unfreezing a Column" on page 53
"Moving Columns" on page 53
Formatting the Column Headers

To define the format of the column headers:
2. Right-click the table. The context menu appears.
3. Select Format > Header Format from the context menu. The Format dialogue appears.
4. The Format dialogue has the following tabs:
-
Font: You can select the Font, Outline (the font style), font Size, Effects, and Text colour.
Colour: You can select the colour of the column headers by selecting a Foreground colour, a Background colour,
and a pattern from the list box. You can also select a 3D Effect for the header.
Borders: You can select the Border, the Type, and the Colour for each column header.
Alignment: You can select both the Horizontal and Vertical alignment of the column header text. The Alignment
tab has additional options as well, allowing you to enable Wrap text, Auto-size, and Allow enter.
5. Click OK.
Formatting Table Cells
To define the format of the table cells:
3. Select Format > Cell Format from the context menu. The Format dialogue appears.
4. The Format dialogue has the following tabs:
-
Font: You can select the Font, Outline (the font style), font Size, Effects, and Text Colour.
Colour: You can select the background colour (Interior) of the column headers, by selecting a Foreground colour,
a Background colour, and a pattern from the list box. You can also select a 3D Effect for the header.
Borders: You can select the Border, the Type, and the Colour for each column header.
Alignment: You can select both the Horizontal and Vertical alignment of the column header text. The Alignment
tab has additional options as well, allowing you to enable Wrap text, Auto-size, and Allow enter.
5. Click OK.
Changing Column Width or Row Height
You can change the column width and row height in a data table. When you change the column width, you change the width
only for the selected column. When you change the row height, however, you change the row height for every row in the
table.
To change the column width:
2. Click the border separating two column headers and drag to change the column width (see Figure 1.17).
To change the row height:
2. Click the border separating two rows and drag to change the row height (see Figure 1.18).
The width or height of the columns or rows change once you release the mouse.
51

Forsk 2011
Figure 1.17: Changing column width
Figure 1.18: Changing row height

Displaying or Hiding a Column
You can choose which columns in data tables to display or hide.
To display or hide a column:
3. Select Display Columns from the context menu or click the Display Columns button (
Columns to Be Displayed dialogue appears (see Figure 1.19).
) in the Table toolbar. The
4. To display a column, select its check box.

5. To hide a column, clear its check box.
You can also hide a column by right-clicking on its header and selecting Hide Columns
from the context menu or by clicking the Hide Columns button (
) in the Table
toolbar. You can hide more than one column by pressing CTRL while selecting the
columns and then clicking the Hide Columns button (
6. Click Close.
52
).

AT310_UMU_E0
Figure 1.19: The Columns to Be Displayed dialogue

Freezing or Unfreezing a Column
In Atoll, you can freeze one or more columns of a data table so that they always remain visible as you scroll horizontally
through the table. For example, while scrolling through the Sites table, you might want to have the Name column always visible. You can keep this column, or any other column visible, by freezing it.
To freeze a column:
2. Select the header of the column you want to freeze. Click and drag over several headers to select more than one
column to freeze.
You can only freeze adjacent columns.
3. Right-click the selected header or headers and select Freeze Columns from the context menu or click the Freeze Columns button (

You can not freeze a column in a report table.
To unfreeze columns:
Right-click the table and select Unfreeze All Columns from the context menu or click the Unfreeze All Columns button
(
Moving Columns
In Atoll, you can change the column order so that you can group similar columns or present data in a determined order.
To move a column:
2. Select the header of the column you want to move. Click and drag over several headers to select more than one
column to move.
You can only move several columns at the same time when they are adjacent.
3. Click again on the selected column and drag to the desired area. As you drag the column, the position the column will
occupy is indicated by a red line (see Figure 1.20).
53

Forsk 2011
Figure 1.20: Moving columns

4. Release the mouse column to place the column.
It may be necessary to click Refresh
in the Map toolbar for your changes to appear.
1.5.6 Copying and Pasting in Tables

In Atoll, you can copy and paste data in tables using the Copy (CTRL+C), Cut (CTRL+X), and Paste (CTRL+V) commands on the
Edit menu. You can copy and paste data to create new elements or you can copy and paste the same data into several cells.
In this section, the following is explained:
"Copying and Pasting a Table Element" on page 54

"Pasting the Same Data into Several Cells" on page 54.
1.5.6.1 Copying and Pasting a Table Element

You can create a new element in tables by copying an existing element, pasting it into a new row and editing the details that
are different.
Each element in a table must have a unique Name.
To create a new element by copying and pasting:

2. Click in the left margin of the table row containing the element to select the entire row.
3. Select Edit > Copy to copy the table row.
4. Click in the left margin of the table row marked with the New Row icon (
) to select the entire row.
5. Select Edit > Paste to paste the copied data into the new row. Atoll, creates a new element from the copied data. The
name of the new element is the same as that of the copied element, preceded by "Copy of." You can edit this name.
1.5.6.2 Pasting the Same Data into Several Cells

You can paste the same data into several cells, using Fill Up or Fill Down.
To paste the same data into several cells:
2. Click on the cell with the data you want to copy and drag to select the cells into which you want to copy the data (see
Figure 1.21).
54

AT310_UMU_E0
Figure 1.21: Selecting the cells

3. Copy into the selected cells:
-
To copy the contents of the top cell of the selection into the other cells, right-click the selection and select Edit >
Fill Down from the context menu or click the Fill Down button (
) in the Table toolbar (see Figure 1.22).
Figure 1.22: Copying the contents of the top cell

-
To copy the contents of the bottom cell of the selection into the other cells, right-click the selection and select
Edit > Fill Up from the context menu or click the Fill Up button (
) in the Table toolbar (see Figure 1.23).
55

Forsk 2011
Figure 1.23: Copying the contents of the bottom cell
1.5.7 Viewing a Statistical Analysis of Table Contents

You can view a statistical analysis of the contents of an entire column in a table or of the contents of a selection of cells.
To view a statistical analysis of table contents:
2. Select the column data you want to analyse:
To view a statistical analysis of an entire column:
-
Click the column title. The entire column is selected.
To view a statistical analysis of a selection of cells in one column:

-
Select the cells you want to analyse. You can select contiguous cells by clicking the first cell and dragging to the
last cell of the selection you want to analyse, or by clicking the first cell, pressing SHIFT and clicking the last cell.
You can select non-contiguous cells by pressing CTRL and clicking each cell in the column separately.
In Atoll you can organise data in several different ways, allowing you to select only
certain data. For more information, see "Grouping, Sorting, and Filtering Data" on
page 65.
3. Right-click the selection of cells. The context menu appears.

4. Select Statistics from the context menu. The Statistics dialogue appears (see Figure 1.24).
Figure 1.24: The Statistics dialogue

The statistics displayed depend on the type of numerical data selected. If you leave the Statistics dialogue open, you
can view the statistical analysis of other cells by selecting them in the table. The contents of the Statistics dialogue are
updated automatically.
56

AT310_UMU_E0
1.5.8 Exporting Tables to Text Files

You can export entire Atoll data tables, or selected columns, to ASCII text files (in text and comma-separated value formats)
and to MS Excel files.
To export a table:
3. Select Export from the context menu. The Export dialogue appears. You can see how the exported table will appear
in the Preview pane (see Figure 1.25).
Figure 1.25: Exporting a data table

4. Select the Header check box if you want to export the names of the columns with the data.
5. Select a Decimal Symbol from the list.
6. Select a Field Separator from the list.
7. Select the fields (displayed as columns in the table) you want to export. You can display all the fields belonging to a
table by clicking the Expand button ( ) to the left of the table name. You can select contiguous fields by clicking the
first field, pressing SHIFT and clicking the last field. You can select non-contiguous fields by pressing CTRL and clicking
each fields separately.
a. To select a field to be exported, select the field in the Available Fields box and click
ported Fields list. All fields in the Exported Fields list will be exported.
to move it to the Ex-
b. To remove a field from the list of Exported Fields, select the field in the Exported Fields list and click
move it.
to re-
c. To change the order of the fields, select a field and click or to move it up or down in the list. The fields at the
top of the Exported Fields appear at the left of the exported table.
57

Forsk 2011
You can save the choices you have made in the Export dialogue as a configuration file by
clicking the Save button at the top of the dialogue and entering a name for the file in the
Save As dialogue that appears. The next time you export a data table, you can click Load
in the Export dialogue to open your configuration file with the same settings you used this
time.
8. Click Export. The Save As dialogue appears.
9. In the Save As dialogue, enter the File name and select the format from the Save as type list.
10. Click Save to export the table.
You can export the Sites and Transmitters tables to text files by selecting the folder or view in the Explorer window and pressing CTRL+E.
For information on importing data into a data table, see "Importing Tables from Text Files" on page 58.
1.5.9 Importing Tables from Text Files

You can import data in the form of ASCII text files (in TXT and CSV formats) into Atoll data tables.
To import a table:
3. Select Import from the context menu. The Open dialogue appears.
4. Select the ASCII text file you want to open and click Open. The Import dialogue appears (see Figure 1.26).
Figure 1.26: Importing information into a data table

5. If the file you was creating using a different Coordinate system, click the Browse button (
) to select the coordinate
system the file was created with. Atoll will covert the coordinates in the imported file to correspond to the coordinate
system used in the Atoll document.
6. Enter the number of the first line of data in the 1st Data Line box.
7. Select a Decimal Symbol from the list.
8. Select a Field Separator from the list.
9. Select the Update Records check box if you want to replace the data of records already existing in the table.
58

AT310_UMU_E0
Atoll compares the values in the left-most column of the data to be imported with the
values in the same column of the data table to see if records already exist. The values of
these records are replaced when the Update Records check box is selected. If the Update
Records check box is not selected, these records are not imported.
10. Under Field Mapping, there are two header rows:
-
Source: The column headers from the text file you are importing.
Destination: The column headers from the Atoll data table.
Align the content of the source file with the content of the destination file by clicking the column header in the Destination row and selecting the corresponding column from the Atoll data file (see Figure 1.26). Select <Ignore> for
source file columns that you do not want to import.
You can change the width of the columns to make the contents easier to work with. See
"Changing Column Width or Row Height" on page 51.
You can save the choices you have made in the Import dialogue as a configuration file by
clicking the Save button at the top of the dialogue and entering a name for the file in the
Save As dialogue that appears. The next time you export a data table, you can click Load
in the Import dialogue to open your configuration file with the same settings you used this
time.
11. Click Import. The contents are imported in the current Atoll data table.
You can import data from text files into the Sites and Transmitters tables by selecting the folder or view in the Explorer
window and pressing CTRL+I.
For information on exporting the information in a data table into a text file, see "Exporting Tables to Text Files" on page 57.
1.5.10 Exporting Tables to XML Files

You can export the data tables in your Atoll document to XML files. You can use XML to exchange information between Atoll
and the OMC.
Atoll creates one XML file for each exported data table, and an index.xml file that contains the mapping between the tables
that were exported and the XML files corresponding to each data table. The index.xml file also stores the information on the
system (GSM, UMTS, etc.), the technology (TDMA, CDMA, TD-SCDMA, etc.), and the version of Atoll with which the XML files
were created. For more information about the formats of the XML files, see the Technical Reference Guide.
To export all the data tables in your document to XML files:
1. Select Document > Data Exchange > XML File Export. The Browse for Folder dialogue appears.
2. Select the folder where the XML files are to be stored. Click the Make New Folder button if you want to create a new
folder to store the XML files.
3. Click OK. All the data tables in the document are exported to XML files.
For information on importing the data tables from XML files into your document, see "Importing Tables from XML Files" on
page 59.
1.5.11 Importing Tables from XML Files

You can import data tables into your Atoll document from XML files. You can use XML to exchange information between Atoll
and the OMC.
In order for Atoll to be able to correctly import the data tables from XML files, the XML files and the current Atoll document
must use the same system (GSM, UMTS, etc.), the technology (TDMA, CDMA, TD-SCDMA, etc.), and the Atoll version used to
create the XML files must be the same as the version used to import the data. For more information about the formats of the
XML files, see the Technical Reference Guide.
To import data tables into your document from XML files:
1. Select Document > Data Exchange > XML File Import. The Browse for Folder dialogue appears.
2. Select the folder where the index.xml file is located.
3. Click OK. The data tables from the XML files listed in the index.xml file are imported in the document .
59

Forsk 2011
Tables are imported in the same order they appear in the index.xml file. Do not modify the
order of tables in the index.xml file because the order in which the data is imported is very
important; some data must be imported before other data. For example, antennas used by
transmitters must be imported before the transmitters themselves.
During the import procedure, existing data in the tables are overwritten by the data from the XML files. Once the import is
complete, Atoll performs a database integrity check, and a duplicate records check to ensure that the import did not create
database problems.
For information on exporting the data tables in your document to XML files, see "Exporting Tables to XML Files" on page 59.
1.6 Printing in Atoll

In Atoll, you can print any part of your document, including maps, data tables, document reports, and antenna patterns. This
section explains the following:
"Printing Data Tables and Reports" on page 60

"Printing a Map" on page 60
"Printing a Docking Window" on page 64
"Printing Antenna Patterns" on page 64.
1.6.1 Printing Data Tables and Reports

Data tables and reports are both presented in tabular format in Atoll and can, therefore, both be printed in the same way.
If you want to see how the table will appear once printed, see "Previewing Your Printing" on page 64.
To print a table:
2. If you want to print an area of the table, select it by clicking in one corner of the area and dragging diagonally to the
opposite corner.
3. Select File > Print.
4. If you want to print only a selected area, choose Selected in the Print dialogue.
5. Click OK to print.
1.6.2 Printing a Map

You can print a map in Atoll and create a paper copy of coverage predictions, etc. Atoll offers several options allowing you to
customise and optimise the printed map. Atoll supports printing to a variety of paper sizes, including A4 and A0.
Before you print a map, you have the following options:
You can print the entire map, or you can define an area of the map to be printed in one of the following ways:
-
Selecting the print area (see "Defining the Printing Zone" on page 61).
Creating a focus zone (see "Drawing a Focus Zone or a Hot Spot" on page 35).
You can accept the default layout or you can modify the print layout (see "Defining the Print Layout" on page 62).
You can see how the map will appear once printed (see "Previewing Your Printing" on page 64).
Printing graphics is a memory-intensive operation and can make heavy demands on your
printer. Before printing for the first time, you should review the "Printing
Recommendations" on page 61 to avoid any memory-related problems.
To print a map:
1. Select the document window containing the map.
2. You now have the following options before printing the map:
-
You can select a print area ("Defining the Printing Zone" on page 61) or create a focus zone ("Drawing a Focus Zone
or a Hot Spot" on page 35).
You can modify the print layout ("Defining the Print Layout" on page 62).
You can see how the map will appear once printed (see "Previewing Your Printing" on page 64).
3. Select File > Print.
60

AT310_UMU_E0
4. Click OK.
1.6.2.1 Printing Recommendations

The appearance of the map is determined by the arrangement and properties of the objects the map contains. Objects in Atoll
are arranged in layers. The layers on the top (as arranged on the Network and Geo tabs) are the most visible on the screen
and in print. The visibility of the lower layers depends on which layers are above it and on the transparency of these layers
(for information on transparency, see "Defining the Transparency of Objects and Object Types" on page 25).
Before printing a map, it is recommended to organise the layers from top to bottom as follows, when a document contains
surface layers (raster maps or polygonal vector maps), lines (vectors such as roads, or airport), and points (measurements,
etc.):
Points (vectors)
Roads and Lines (vectors)
Surface polygons (vectors)
Multi-format maps - population, geoclimatic, traffic maps (vector or raster), and others
Clutter class maps (transparent raster maps)
Images, DTM, or clutter height maps (non-transparent maps).
Sites and transmitters must be above all the other layers. For this reason, visible objects on the Network tab, for example,
sites, transmitters, and predictions, are displayed above objects on the Geo tab. For performance reasons, however, it is
strongly recommended to put vector layers, such as roads, over predictions. This will ensure that these vector layers are visible
when you print the map.
To put vector layers from the Geo tab over predictions:
1. In the Explorer window, click the Geo tab.
2. Right-click the vector layer you want to move to the Network tab. The context menu appears.
3. Select Move to Network Tab from the context menu.
4. Click the Network tab.
5. Drag the vector layer to a position above Predictions but below Sites, Antennas, and Transmitters.
1.6.2.2 Defining the Printing Zone

You can define an area to be printed.
To create a printing zone:
3. Right-click the Printing Zone folder. The context menu appears.

5. Draw the printing zone:
a. Click the point on the map that will be one corner of the rectangle that will define the printing zone.
b. Drag to the opposite corner of the rectangle that will define the printing zone. When you release the mouse, the
printing zone will be created from the rectangle defined by the two corners.
The printing zone is delimited by a light green line (see Figure 1.27). If you clear the printing zones visibility check box
in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into
account.
61

Forsk 2011
Figure 1.27: Printing zone

You can also create a printing zone as follows:

Editor toolbar to draw the printing zone.
Existing polygon: You can use any existing polygon as a printing zone by right-clicking it on the map or in the Explorer
window and selecting Use As > Printing Zone from the context menu. You can also combine an existing printing zone
with any existing polygon by right-clicking it on the map or in the Explorer window and selecting Add To > Printing
Zone from the context menu. The "effective" resulting printing zone will be the rectangle encompassing the several
polygons composing the printing zone.
Importing a polygon: If you have a file with an existing polygon, you can import it and use it as a printing zone. You
can import it by right-clicking the Printing Zone folder on the Geo tab and selecting Import from the context menu.
Fit to Map Window: You can create a printing zone the size of the map window right-clicking the Printing Zone folder
and selecting Fit to Map Window from the context menu.
Once you have created a printing zone, you can change its size by dragging the edges of the zone displayed on the rulers of
the map window. You can also use Atolls polygon editing tools to edit the printing zone. For more information on the polygon
editing tools, see "Using Polygon Zone Editing Tools" on page 36.
You can save the printing zone, so that you can use it in a different Atoll document, in the
following ways:
Saving the printing zone in the user configuration: For information on saving the
printing zone in a user configuration, see "Saving a User Configuration" on page 76.
Exporting the printing zone: You can export the geographic export zone by rightclicking the Printing Zone on the Geo tab of the Explorer window and selecting
Export from the context menu.
1.6.2.3 Defining the Print Layout

You can use the Print Setup dialogue to define how your map will appear when you print it. On the Print Setup dialogue, you
can:
Set the scale of the map.

Choose to print the rulers with the map.
Choose to print the area outside the focus zone.
Choose to print the legend.
Add a title, comment, logo, header, or footer.
Select paper size and source, as well as the page orientation and the margins.
These settings can be saved as a configuration, allowing you to define a standard appearance which you can then load and
use the next time you print a similar document.
62

AT310_UMU_E0
To define the appearance of the map when it is printed:

1. Select File > Print Setup. The Print Setup dialogue appears. You define the print setup on the Page tab, the Components tab, and the Header/Footer tab. You can see any changes you make in the schematic preview on the right side
of the Print Setup dialogue.
If you have previously defined a configuration file containing all the necessary settings, you
can click the Load button under Configuration to import those settings.
2. Click the Page tab. On the Page tab, you can define the page size, margins, and orientation and the scale of the printed
map:
a. Under Orientation, select whether the page should be printed in Portrait or Landscape.
b. Under Paper, select the Size of the paper and, optionally, the Source of the paper.
c. Under Scaling, define the scale of the printed image either by selecting Fit to page, or by selecting Scale and defining the scale.
d. Under Margins, set the margins of the page in millimetres.
3. Click the Components tab.
a. Under Map, you can define the appearance of the printed map:
-
Select the Rulers check box if you want to print the map with a scale around it.
Select the Area inside focus zone only check box if you only want to print the part of the map inside the focus
zone.
b. Under Legend, you can define the placement of the legend.

-
Select the Legend check box if you want to print a legend with the map.
Click a button to set the Position of the legend. The buttons

inside the square will place the legend on top of the map. The
buttons outside of the square will place the legend outside of the
map.
Click the Font button to open the Font dialogue to define the font of the legend.
c. Select the Comments check box if you want to print a comment with the map and set its Position. Clicking the
Properties button opens a dialogue where you can enter text and set variables such as the current time and date.
If you want the comment to appear on the map (and not outside of it), select the On the map check box.
4. Click the Header/Footer tab. On the Header/Footer tab, you can set the position of graphic elements.
a. Select the Map Title check box if you want to define a title for the map and set its Position. Clicking the Properties
button opens a dialogue where you can enter text and set variables such as the current time and date. If you want
the title to appear on the map (and not outside of it), select the On the map check box.
b. Under Logo 1 and Logo 2, you can define graphics that appear for the map. The graphics can be a company logo
or other information, such as copyright information, in the form of a BMP graphic.
i.
For the selected logo check box, click the Properties button. The Logo dialogue appears.
By default, Atoll searches for the logo files in the Atolls installation folder. If a file named logo.bmp is present
in this folder, it is considered as the default header logo. However, you can select a different file.
ii. Click File. The Open dialogue appears.

iii. Select the your graphic in BMP format and click Open.
Only BMP graphics can be used as logos. If your logo is in a different format, you must first
convert it using a graphics programme to the BMP format.
iv. Select the correct Width and Height (in pixels).

v. Click OK.
63

Forsk 2011
c. Select the Header/Footer Note check box if you want to define a header or footer for the map and set its Position.
Clicking the Properties button opens a dialogue where you can enter text and set variables such as the current
time and date. If you want the header or footer to appear on the map (and not outside of it), select the On the
map check box.
5. Once you have made your settings, click OK to close the Print Setup dialogue, or click Print to print the document.
You can save the current settings as a configuration file by clicking the Save button under
Configuration. This enables you to re-use the same settings the next time by loading them.
1.6.3 Previewing Your Printing

When you want to print maps, data tables, or reports, you can preview your printing.
To preview your printing:
1. Select the map or table you want to print.
2. Select File > Print Preview. The Print Preview window appears.
At the top of the Print Preview window, you can click one of the following buttons:
-
Click the Print button (
) to open the Print dialogue.
Click the Next Page button (
Click the Previous Page button (
Click the Zoom In button (
Click the Zoom Out button (
Click the Toggle One/Two Pages Display button (

Click Close to close the print preview.
) to display the following page

) to display the previous page.
) to zoom in on the print preview.

) to zoom out on the print preview.
) to switch display from one to two pages side by side
1.6.4 Printing a Docking Window

You can print the content of many docking windows using the context menu; selecting File > Print only prints the contents of
a document window, as explained in "Printing a Map" on page 60. The docking windows whose contents you can print are:
Legend Window (for more information on this tool, see "Adding an Object Type to the Legend" on page 27)
Point Analysis Tool
CW Measurement Analysis Tool (for more information on this tool, see the Measurements and Model Calibration
Guide.
Drive Test Data Analysis Tool
Microwave Link Analysis (for more information on this tool, see "Studying Reflection" on page 88)
To print the content of a docking window:

1. Open the docking window you want to print.
-
If you want to print a Point Analysis window, click the tab you want to print.
2. Right-click the window you want to print.

3. Select Print from the context menu. The Print dialogue appears.
4. Click OK to print.
1.6.5 Printing Antenna Patterns

You can print the horizontal or vertical pattern of an antenna.
To print an antenna pattern:
1. Click the Parameters tab of the Explorer window.
2. Open the Antennas table:
To open the RF Antennas table:
) to the left of the Radio Network Equipment folder.
b. Right-click the Antennas folder.
64

AT310_UMU_E0
c. Select Open Table from the context menu.

3. Right-click the antenna whose pattern you want to print.
4. Select Record Properties from the context menu. The Properties dialogue appears.
5. Select the Horizontal Pattern tab or the Vertical Pattern tab.
6. Right-click the antenna pattern and select Linear or Logarithmic from the context menu.
7. Right-click the antenna pattern and select Print from the context menu.
1.7 Grouping, Sorting, and Filtering Data

In Atoll you can organise data in several different ways, allowing you to select only certain data and then, for example, modify
only selected data or run calculations on the selected data. Atoll allows you to group, sort, or filter data quickly by one criterion, or by several.
After you have defined how you will group, sort, or filter data, you can save this information as a folder configuration.
In this section the following will be explained:
"Grouping Data Objects" on page 65

"Sorting Data" on page 69
"Filtering Data" on page 71
"Folder Configurations" on page 80
"Creating and Comparing Views" on page 81
1.7.1 Grouping Data Objects

You can group objects according to a selected property on the Network tab of the Explorer window. The objects to be grouped
can be in a data folder or in a view (see "Creating and Comparing Views" on page 81). You can also define the properties by
which you can group objects. Grouping objects in the Explorer window is similar to sorting data in the data table because it
puts all records with the selected property together.
Once you have grouped data objects, you can access their Properties dialogue from the context menu to edit properties on
all grouped objects. You can save the grouping parameters as a folder configuration. For information, see "Folder Configurations" on page 80.
This section explains:
"Grouping Data Objects by a Selected Property" on page 65

"Configuring the Group By Submenu" on page 66
"Advanced Grouping" on page 66.
For examples of grouping data objects, see "Examples of Grouping" on page 67.
1.7.1.1 Grouping Data Objects by a Selected Property

You can group data objects by a selected property using the Group By command on the context menu.
To group data objects by a selected property:
1. Click the Network tab in the Explorer window.
2. Right-click the folder or view whose objects you want to group. The context menu appears.
3. From the Group By submenu, select the property by which you want to group the objects. The objects in the folder
are grouped by that property.
If the range of properties available in the Group By submenu has been configured as
explained in "Configuring the Group By Submenu" on page 66, you can select additional
properties by selecting More Fields from the Group By submenu. For information on using
the dialogue that appears, see "Configuring the Group By Submenu" on page 66.
To undo the grouping:
2. Right-click the folder or view whose objects you have grouped.
3. From the context menu, select from the Group By > None.
See "Examples of Grouping" on page 67.
65

Forsk 2011
1.7.1.2 Configuring the Group By Submenu

Some data objects, such as transmitters, have a large number of properties that will appear by default in the Group By
submenu. You can make it easier to group data objects by configuring the Group By submenu to display only the properties
that are relevant for grouping.
To configure the Group By submenu:
2. Right-click the folder whose Group By submenu you want to configure. The context menu appears.
3. Select Properties from the context menu.
4. Select the General tab of the Properties dialogue.
5. Click the Configure Menu button next to the Group By field that shows how the data objects are presently grouped.
The Menu Configuration dialogue appears (see Figure 1.28).
Figure 1.28: The Menu Configuration dialogue

6. Select the fields you want to appear in the Group By submenu. You can display all the fields belonging to a table by
clicking the Expand button ( ) to the left of the table name. You can select contiguous fields by clicking the first field,
pressing SHIFT and clicking the last field. You can select non-contiguous fields by pressing CTRL and clicking each fields
separately.
-
To select a field to appear in the Group By submenu, select the field in the Available fields list and click
move it to the Grouping Fields list.
to
To remove a field from the list of Grouping Fields, select the field in the Grouping fields list and click
remove it.
to
To change the order of the fields, select a field and click or to move it up or down in the list. The objects will
be grouped in the order of the fields in the Grouping fields list, from top to bottom.
7. Click OK to close the Menu Configuration dialogue and click OK to close the Properties dialogue. The Group By submenu will now contain only the fields you selected.
1.7.1.3 Advanced Grouping

You can group data objects by one or more properties, using the Group By button on the Properties dialogue.
To group data objects by one or more properties:
4. Select the General tab of the Properties dialogue.
5. Click the Group By button. The Group dialogue appears (see Figure 1.29).
66

AT310_UMU_E0
Figure 1.29: The Group dialogue

6. Select the fields by which you want to group the objects. You can select contiguous fields by clicking the first field,
pressing SHIFT and clicking the last field. You can select non-contiguous fields by pressing CTRL and clicking each fields
separately.
-
To select a field to be used to group the objects, select the field in the Available Fields list and click
it to the Grouping Fields list.
to move
To remove a field from the list of Grouping Fields, select the field in the Grouping Fields list and click
remove it.
To change the order of the fields, select a field and click or to move it up or down in the list. The objects will
be grouped in the order of the fields in the Grouping Fields list, from top to bottom.
to
7. Click OK to close the Group dialogue and click OK to close the Properties dialogue and group the objects.
To undo the grouping:
3. From the context menu, select from the Group By > None.
1.7.1.4 Examples of Grouping

In this example, there is an Atoll document with a large number of sites and, therefore, transmitters. While it is easy to see
on the map which transmitters are part of which site, in the Explorer window, you can only see a very long list of transmitters
under the Transmitter folder.
By right-clicking the Transmitter folder and selecting Group By > Site (Figure 1.30), you can group the transmitters by the site
they are located on.
67

Forsk 2011
Figure 1.30: Grouping transmitters by site

The result of grouping can be seen in Figure 1.31.
Figure 1.31: Transmitters grouped by site

You can also group objects by the computation or focus zone. You normally create a computation or focus zone when you
want to concentrate on a given subset of transmitters, for example, when you are working on a certain area of the network.
By grouping them by computation or focus zone, the transmitters you are working on are immediately visible under the Transmitter folder.
By right-clicking the Transmitter folder and selecting Group By > Polygon > Focus Zone (Figure 1.30), you can group the transmitters in the focus zone together.
68

AT310_UMU_E0
Figure 1.32: Grouping transmitters by zone

The result of grouping can be seen in Figure 1.31. The transmitters are now in two groups: those inside the focus zone and
those outside the focus zone.
Figure 1.33: Transmitters grouped by site
1.7.2 Sorting Data

In Atoll, you can sort the document data either in the data tables or using the Sort function of Properties dialogue. You can
sort the data in ascending (A to Z, 1 to 10) or descending (Z to A, 10 to 1) order.
You can sort the data by either one or by several columns. When you sort data by several columns, Atoll sorts the records by
the first column and then, within each group of identical values in the first column, Atoll then sorts the records by the second
column, and so on.
Once you have sorted data objects, you can save the settings as a folder configuration. For information, see "Folder Configurations" on page 80.
This section explains the following:
"Sorting Data in Tables" on page 69

"Advanced Sorting" on page 70
1.7.2.1 Sorting Data in Tables

When sorting data in tables, you can sort by one column or by several columns:
"Sorting by One Column" on page 70

"Sorting by Several Columns" on page 70.
69

Forsk 2011
Sorting by One Column

To sort data in a table by one column:
2. Select the header of the column that you want to sort on. The entire column is selected.
3. Right-click the column header. The context menu appears.
4. From the context menu, select how you want to sort:
-
Sort Ascending: sort the data table records from the lowest value in the reference column to the highest value.
Sort Descending: sort the data table records from the highest value in the reference column to the lowest value.
You can also sort data in a table by selecting the column as described and then clicking
either the Sort Ascending (
) or Sort Descending (
) buttons in the Table toolbar.
Sorting by Several Columns

You can only sort in a table by adjacent columns. If you want to sort by columns that are not adjacent, you can move the
columns first as explained in "Moving Columns" on page 53.
If you want to sort data by several columns without moving the columns, you can use the
Sort function on the Properties dialogue. For information, see "Advanced Sorting" on
page 70.
To sort data in a table by several columns:
2. Click the header of the first column and drag over the adjacent columns that will be your sort references. The entire
column is selected.
3. Right-click the column headers. The context menu appears.
4. From the context menu, select how you want to sort:
-
Sort Ascending: sort the data table records from the lowest value in the first reference column to the highest
value.
Sort Descending: sort the data table records from the highest value in the first reference column to the lowest
value.
You can also sort data in a table by selecting the column as described and then clicking
either the Sort Ascending (
) or Sort Descending (
) buttons in the Table toolbar.
1.7.2.2 Advanced Sorting

You can sort data by several criteria using the Sort function of the Properties dialogue.
To sort data using the Sort function of the Properties dialogue:
1. Click the Network tab of the Explorer window.
2. Right-click the folder whose data you want to sort. The context menu appears
4. Select the General tab in the Properties dialogue.
5. Click the Sort button. The Sort dialogue appears (see Figure 1.34).
6. For the first column you want to sort on:
a. Select the column name from the Sort by list.
b. Choose whether you want to sort in ascending or descending order.
7. For each other column you want to sort on:
a. Select the column name from the And by list.
b. Choose whether you want to sort in ascending or descending order.
70

AT310_UMU_E0
8. Click OK.
Figure 1.34: The Sort dialogue
1.7.3 Filtering Data

In Atoll, you can filter data according to one or several criteria. You can filter data to be able to work with a subset of data, or
to facilitate working with large documents by reducing the amount of records displayed.
The filtered data objects are the data objects that remain after you have applied your filter criteria.
You can save the filtering parameters as a folder configuration. For information, see "Folder Configurations" on page 80.
"Filtering in Data Tables by Selection" on page 71

"Advanced Data Filtering" on page 72
"Restoring All Records" on page 73
"Advanced Filtering: Examples" on page 73.
1.7.3.1 Filtering in Data Tables by Selection

You can filter a data table by selecting one or more values. Once you have selected one or more values, you can choose to
view only records that have the same value or only records that do not have that value.
To filter a data table on one or more fields:
2. Select the value to filter on. To select more than one value, press CTRL as you click the other values.
3. Right-click the selected value or values and select one of the following from the tables context menu:
-
Filter by Selection: All records with the selected value or values are displayed. You can now modify these records
or make calculations on them as you would normally do with the entire data table (see Figure 1.35 on page 72).
Filter Excluding Selection: All records without the selected value or values are displayed. You can now modify
these records or make calculations on them as you would normally do with the entire data table (see Figure 1.36
on page 72).
71

Forsk 2011
Figure 1.35: Filtering by selection (Antenna AO9209)
Figure 1.36: Filtering excluding selection (Antenna AO9209)

You can also filter data in a table by selecting the values as described and then clicking
either the Filter by Selection (
toolbar.
) or Filter Excluding Selection (
) buttons in the Table
1.7.3.2 Advanced Data Filtering

You can use advanced data filtering to combine several criteria in different fields to create complex filters.
To create an advanced filter:
2. Click the Advanced Filter button (
) in the Table toolbar. The Filter dialogue appears.
You can also access the Filter dialogue by clicking the Filter button of the tables
Properties dialogue.
3. Click the Filter tab:

a. Select a Field from the list.
b. Under Values to Include, you will find all the values represented in the selected field. Select the check boxes next
to the values you want to include in the filter. Click Clear All to clear all check boxes.
72

AT310_UMU_E0
Making selections on the Filter tab of the Filter dialogue is the equivalent of filtering by
selection as explained in "Filtering in Data Tables by Selection" on page 71.
4. Click the Advanced tab:

a. In the Column row, select the name of the column to be filtered on from the list. Select as many columns as you
want (see Figure 1.37).
Figure 1.37: The Filter dialogue - Advanced tab

b. Underneath each column name, enter the criteria on which the column will be filtered as explained in the following table:
Formula
Data are kept in the table only if
=X
value equal to X (X may be a number or characters)
<> X
value not equal to X (X may be a number or characters)
<X
numerical value is less than X
>X
numerical value is greater than X
<=X
numerical value is less than or equal to X
>=X
numerical value is greater than or equal to X
*X*
text objects which contain X
X*
text objects which start with X
5. Click OK to filter the data according to the criteria you have defined.
Filters are combined first horizontally, then vertically.
See "Advanced Filtering: Examples" on page 73.
1.7.3.3 Restoring All Records

After you have applied filter criteria to records, you may want to cancel the filter criteria and display all the records again.
To restore all records:
Click the Remove Filter button (
1.7.3.4 Advanced Filtering: Examples

In this section, you will find a few examples of advanced filtering:
"Advanced Filtering: Example 1" on page 74

"Advanced Filtering: Example 2" on page 74
"Advanced Filtering: Example 3" on page 75.
73

1.7.3.4.1
Forsk 2011
Advanced Filtering: Example 1

In this example, there is an Atoll document with antennas from two manufacturers and with different characteristics.
Figure 1.38: Initial table

The objective of this example is to use filter criteria to find antennas manufactured by Kathrein with a beamwidth between
50 and 100. To do this, the following filter syntax is entered on the Advanced tab of the Filter dialogue (for information on
the Advanced tab, see "Advanced Data Filtering" on page 72):
The first criterion, as shown in Figure 1.39, is all antennas made by a manufacturer with a name beginning with a "K"
("=K*"). While you could write in the entire name ("=Kathrein"), it is not necessary because there is only one manufacturer with a "K."
The second criterion is all antennas with a beamwidth under 100.
The third criterion is all antennas with a beamwidth over 50.
The combination of these criteria is all antennas from manufacturers with a name beginning with "K" and with a beamwidth
under 100 but over 50.
The result of this advanced filter can be seen in the second pane of Figure 1.39.
Figure 1.39: Advanced filtering
1.7.3.4.2

In this example, the document is the same as in "Advanced Filtering: Example 1" on page 74. The objective of this example is
the same as well: to use filter criteria to find antennas manufactured by Kathrein with a beamwidth between 50 and 100. The
filter syntax is entered on the Advanced tab of the Filter dialogue (for information on the Advanced tab, see "Advanced Data
Filtering" on page 72), in this case, however, the entered filter syntax contains errors:
74
As shown in Figure 1.40, the first criterion is all antennas made by a manufacturer with a name beginning with a "K"
("=K*").

AT310_UMU_E0
The second criterion is all antennas with a beamwidth under 100 and over 50.
Figure 1.40: Errors in filtering

As previously stated, the objective of this example was to use filter criteria to find antennas manufactured by Kathrein with a
beamwidth between 50 and 100. However, because the second criterion (beamwidth under 100 and over 50) is malformed,
with "> 50" placed under "< 100", it functioned as an OR condition and not as an AND condition. The resulting filter searched
for all antennas manufactured by Kathrein with a beamwidth under 100, or all antennas over 50; all antennas are displayed.
1.7.3.4.3

In this example, the document is the same as in "Advanced Filtering: Example 1" on page 74. The objective of this example is
the same as well: to use filter criteria to find antennas manufactured by Kathrein with a beamwidth between 50 and 100. The
filter syntax is entered on the Advanced tab of the Filter dialogue (for information on the Advanced tab, see "Advanced Data
Filtering" on page 72), in this case, however, the entered filter syntax contains errors:
As shown in Figure 1.41, the first criterion is all antennas made by a manufacturer with a name beginning with a "K"
("=K*").
The second criterion is all antennas with a beamwidth under 100 and over 50.
Figure 1.41: Errors in filtering

As previously stated, the objective of this example was to use filter criteria to find antennas manufactured by Kathrein with a
beamwidth between 50 and 100. However, because the second criterion is malformed, the filter only generates an error
message and no antennas are filtered out.
75

Forsk 2011
1.7.4 User Configurations

In Atoll, you can save many parameters and settings in user configurations and then load them in other documents. User
configurations are used to store parameters and settings that are not stored in databases. User configuration files enable you
to ensure that all users in a multi-user environment use the same settings.
The file extension of user configuration files is CFG. The file extension GEO is, however, used if only the geographic data set
or zones are being saved in a user configuration file. User configuration files are XML files and may be opened in text and XML
editors.
You can save the following information in user configuration files:
Geographic data set: Full paths of imported geographic maps, map display settings (such as, the visibility scale, transparency, tip text, etc.), clutter description (code, name, height, standard deviations, etc.), and raster or user profile
traffic map description.
When you save the geographic data set in a user configuration file, the coordinate
system of all vector geographic data must be the same as that of the raster geographic
data.
Zones: Filtering, focus, computation, printing, and geographic export zones in the current document.
Folder configurations: Sort, group, and filter settings (the current folder configuration, even if not saved, and other
defined configurations for the folders), the filtering zone, and the display settings of network data folders (including
measurement display settings).
Automatic Neighbour Allocation Parameters: The input parameters of the automatic neighbour allocation.
Automatic Scrambling Code Allocation Parameters: The parameters of the automatic scrambling code allocation.
Automatic PN Offset Allocation Parameters: The parameters of the automatic PN offset allocation.
Prediction List: The list of predictions in the Predictions folder and their settings (general, coverage conditions, and
display).
GSM Automatic Frequency Planning Parameters: Calculation options selected when starting a GSM AFP session as
well as calculation parameters used for interference histograms.
Macros: Full paths of any macros. Macros are loaded for entire Atoll sessions and not for a specific Atoll document.
You can export the macros to a user configuration even if you do not have an Atoll document open.
For a detailed description of the user configuration file, see the Administrator Manual.
"Saving a User Configuration" on page 76

"Loading a User Configuration" on page 77.
1.7.4.1 Saving a User Configuration

You create a user configuration by saving the selected settings to an external file.
To save a user configuration:
1. Select Tools > User Configuration > Save. The User Configuration dialogue appears (see Figure 1.42).
Figure 1.42: Saving a user configuration

2. Select the check boxes of the information you want to export as part of the user configuration.
76

AT310_UMU_E0
3. Click OK. The Save As dialogue appears.

4. Enter a File name for the user configuration file and click Save. The folder configuration has been saved.
1.7.4.2 Loading a User Configuration

You can load a user configuration that you or another user has created, as explained in "Saving a User Configuration" on
page 76, into your current Atoll document. If the user configuration you load contains macro information, it will only be
loaded if no document is currently open. When there is no Atoll document open, only macro information is loaded from the
user configuration.
To load a user configuration:
1. Select Tools > User Configuration > Load. The Open dialogue appears.
2. Select the user configuration file with the data you want to use in your current document.
3. Click Open. The User Configuration dialogue appears (see Figure 1.43).
Figure 1.43: Loading a user configuration

4. Select the check boxes of the information you want to load.
5. Click OK. The user configuration is loaded into your current document.
1.7.5 Site and Transmitter Lists

In Atoll, you can create lists of sites and transmitters. Once you have created a site or transmitter list, you can modify the list
and use it to filter data to be able to work with a subset of data, or to facilitate working with large documents by reducing the
amount of records displayed.
In a multi-user environment, site lists can be stored in the database. When you open a document from a database, you can
select the sites to load according to any defined site lists. In a large radio-planning project, this allows you to more effectively
manage your resources by reducing the unnecessary data you retrieve from the database.
"Creating a Site or Transmitter List" on page 77

"Adding a Site or Transmitter to a List from the Explorer Window" on page 78
"Adding a Site or Transmitter to a List from the Map Window" on page 78
"Adding Sites or Transmitters to a List Using a Zone" on page 79
"Editing a Site or Transmitter List" on page 79
"Filtering on a Site or Transmitter List" on page 79.
1.7.5.1 Creating a Site or Transmitter List

You can create lists of sites or transmitters that you can then use to filter the data displayed.
To create a site or transmitter list:
2. Right-click the folder where you want to create the list:
77

Forsk 2011
Site list: if you want to create a site list:

a. Right-click the Sites folder. The context menu appears.
b. Select Site Lists > Open Table from the context menu. The Site Lists table appears.
Transmitter list: if you want to create a transmitter list:
a. Right-click the Transmitters folder. The context menu appears.
b. Select Transmitter Lists > Open Table from the context menu. The Transmitter Lists table appears.
3. Enter the name of the new list in the row marked with the New Row icon (
).
1.7.5.2 Adding a Site or Transmitter to a List from the Explorer Window

You can add a site or transmitter to a list by selecting it from the Explorer window.
To add a site or transmitter to a list:
) to the left of Sites or Transmitters folder to expand the folder.
3. Right-click the site or transmitter you want to add to the list. The context menu appears.
Site list: if you want to add a site to a list:
-
Select Add Site to a List from the context menu. A dialogue appears.
Transmitter list: if you want to add a transmitter to a list.

-
Select Add Transmitter to a List from the context menu. A dialogue appears.
4. Select the name of the list from the dialogue.

You can create a new list by entering a name in the list instead of selecting the name
from the list. The selected site or transmitter will be added to the new list.
5. Click OK. The site or transmitter is added to the selected list.

You can quickly create a complete list by first filtering the contents of the Sites or
Transmitters folder as explained in "Filtering Data" on page 71. Then, by right-clicking
the Sites or Transmitters folder and selecting Site Lists > Add Sites to a List or
Transmitter Lists > Add Transmitters to a List from the context menu, you can add the
filtered contents of folder to the list you select.
1.7.5.3 Adding a Site or Transmitter to a List from the Map Window

You can add a site or transmitter to a list by selecting it from the map window.
To add a site or transmitter to a list:
1. In the map window, right-click the site or transmitter you want to add to a list.
Site list: if you want to add a site to a list:
-
Select Add Site to a List from the context menu. A dialogue appears.
Transmitter list: if you want to add a transmitter to a list.

-
Select Add Transmitter to a List from the context menu. A dialogue appears.

3. Click OK. The site or transmitter is added to the selected list.
78

AT310_UMU_E0
1.7.5.4 Adding Sites or Transmitters to a List Using a Zone

You can add the sites or transmitters contained in a zone to a site or transmitter list.
To add the sites or transmitters contained in a zone to a list:
1. Create a zone as explained in "Using Zones in the Map Window" on page 33 that contains the sites or transmitters you
want to add to a list. You can use a filtering, computation, focus, hot spot, printing, or geographic export zone.
2. On the Geo tab of the Explorer window, right-click the zone and select one of the following from the context menu:
-
Add Sites to a List: Select Add Sites to a List to add the sites in the zone to a site list. A dialogue appears.
Add Transmitters to a List: Select Add Transmitters to a List to add the sites in the zone to a site list. A dialogue
appears.

4. Click OK. The sites or transmitters contained in the zone are added to the selected list.
1.7.5.5 Editing a Site or Transmitter List

You can edit a site or transmitter list using the Site List or Transmitter List table.
To edit a site or transmitter list:
2. Right-click the folder where you want to edit the list:
Site list: if you want to edit a site list:
a. Right-click the Sites folder. The context menu appears.
b. Select Site Lists > Open Table from the context menu. The Site Lists table appears.
Transmitter list: if you want to edit a transmitter list:
a. Right-click the Transmitters folder. The context menu appears.
b. Select Transmitter Lists > Open Table from the context menu. The Transmitter Lists table appears.
3. Select the name of the list you want to edit and click Properties. The Properties dialogue appears.
4. You can now edit the list:
To add a site or transmitter to the list:
-
Select the name of the site or transmitter in the row marked with the New Row icon (
).
To delete a site or transmitter from the list:

a. Click in the left margin of the row containing the site or transmitter to select it.
b. Press DEL to delete the site or transmitter from the list.
5. Click OK when you have finished editing the site or transmitter list.
1.7.5.6 Filtering on a Site or Transmitter List

You can use site or transmitter lists to filter the contents of the Sites and Transmitters folders.
To filter folder contents using a site or transmitter list:
2. Right-click the folder whose contents you want to filter. The context menu appears.
4. On the General tab of the Properties dialogue, click the Filter button. The Filter dialogue appears.
5. If you have created a list, there will be an additional tab:
-
Sites: Click the Site Lists tab.

Transmitters: Click the Transmitter Lists tab.
6. Select the check box of the list or lists that you want to display.
79

Forsk 2011
7. Click OK to close the Filter dialogue.

8. Click OK to close the Properties dialogue. Only sites or transmitters that belong to the selected list are now displayed
on the Network tab of the Explorer window and in the map window.
1.7.6 Folder Configurations

In Atoll, the parameters defining how data contained in a folder are grouped, sorted, or filtered are referred to as a folder
configuration. You can define folder configurations and save them, allowing you to consistently apply the same grouping,
filtering, or sorting criteria.
"Creating a Folder Configuration" on page 80

"Applying a Saved Folder Configuration" on page 80
"Reapplying the Current Folder Configuration" on page 80
"Saving a Folder Configuration in an External File" on page 81
"Loading a Folder Configuration from an External File" on page 81
"Deleting a Folder Configuration" on page 81.
For transmitters, there is a default folder configuration called Same as Sites Folder. You
can apply this configuration to arrange the transmitters in the Transmitters folder with the
same parameters as those defined for sites.
1.7.6.1 Creating a Folder Configuration

In Atoll, you can save the parameters defining how data contained in a folder are grouped, filtered, or sorted as a folder configuration.
To create a configuration:
2. Right-click the folder whose settings you want to save.
5. If you have not yet done so, set the following parameters as desired:
-
Group By (see "Grouping Data Objects" on page 65)

Sort (see "Sorting Data" on page 69)
Filter (see "Filtering Data" on page 71).
6. Under Folder configuration, click Save.

7. Enter the name of the configuration in the Save Configuration dialogue.
8. Click OK to save the configuration and click OK to close the Properties dialogue.
The saved folder configuration is only available for the current folder and can be reapplied to the folder by selecting it from
the Folder Configuration submenu on the folders context menu.
1.7.6.2 Applying a Saved Folder Configuration

You can apply a folder configuration that has been created and saved for the present folder.
To apply a saved folder configuration:
2. Right-click the folder to which you want to apply a folder configuration. The context menu appears.
3. On the Folder Configuration submenu, select the name of the folder configuration you want to apply. The folder configuration is applied to the current folder.
1.7.6.3 Reapplying the Current Folder Configuration

If you have grouped, filtered, or sorted a data folder, you have created and applied a folder configuration. If you then add or
modify data, the properties of these may not match the folder configuration you previously made on the data folder. In this
case, you can reapply the same filter or sort settings to the new or modified data.
80

AT310_UMU_E0
To reapply the folder configuration:

2. Right-click the folder whose folder configuration you want to reapply.
3. Select Update Folder Configuration from the context menu. The previously configured folder configuration is reapplied to the data.
1.7.6.4 Saving a Folder Configuration in an External File

When you create a folder configuration, you save it in the current ATL document. However, you can save it as part of a user
configuration in an external file, so that it can be used in other documents.
To save a folder configuration in an external file:
1. Select Tools > User Configuration > Save. The User Configuration dialogue appears (see Figure 1.42 on page 76).
2. Select the Folder Configuration check box.
If you want to export other configurations at the same time, select those check boxes as well.
4. Enter a File name for the CFG file and click Save. The folder configuration has been saved.
1.7.6.5 Loading a Folder Configuration from an External File

Once you have saved a folder configuration as explained in "Saving a Folder Configuration in an External File" on page 81, you
can load it into your current document.
To load a folder configuration:
2. Select the CFG file with the folder configuration you want to import.
3. Click Open. The User Configuration dialogue appears (see Figure 1.43 on page 77).
4. Select the Folder Configuration check box.
If you want to import other configurations at the same time, select those check boxes as well.
5. Click OK. The folder configuration is imported.
1.7.6.6 Deleting a Folder Configuration

You can delete a folder configuration from the Atoll document when you no longer need it.
To delete a folder configuration:
2. Right-click the folder with the folder configuration you want to delete.
5. Under Folder configuration, select the name of the configuration from the list.
6. Click Delete. The folder configuration is deleted.
When you delete a folder configuration, Atoll will not ask for confirmation; it is deleted
immediately.
1.7.7 Creating and Comparing Views

You can compare the effects of different grouping, sorting, or filtering settings by creating views of object folders on the
Network tab and applying different settings to each view. Each view contains a copy of the data in the object folder in which
it was created.
To create a view of a folder:
1. On the Network tab of the Explorer window, right-click the folder you want to create a view of.
2. Select Create View from the context menu. A view is created containing a copy of the original folder content.
81

Forsk 2011
You can now perform the following actions on the view:
Grouping (see "Grouping Data Objects" on page 65)

Sorting (see "Sorting Data" on page 69)
Filtering (see "Filtering Data" on page 71).
If you have created several views, you can rename each one to give it a more descriptive
name. For information on renaming an object, see "Renaming an Object" on page 19.
Once you have performed the actions on each view, you can compare the differences, by displaying in turn each view, with
its grouping, sorting, or filtering settings, on the map. For more information on display properties, see "Display Properties of
Objects" on page 23.
To compare views:
1. On the Network tab of the Explorer window, clear the check boxes to the left of each view. The data objects are not
displayed on the map.
2. Select the check box of one of the views, leaving the check boxes of the other views cleared. The data objects of the
selected view, with its associated grouping, sorting, or filtering settings, are displayed on the map.
3. Clear this check box and select the check box of a different view. How the objects are displayed on the map will
change, depending on the different grouping, sorting, or filtering settings of the selected view.
You can remove views by deleting them. When you delete a view, the data contained are not deleted. When you delete the
last view, the data reappear under the initial folder.
To delete a view:
Select the view to be deleted and press DEL.

If, after deleting the last view, the data do not reappear under the initial folder, you can
refresh the display by right-clicking the folder and selecting Group By > None from the
context menu.
1.7.8 Filtering Data Using a Filtering Zone

In Atoll, you can simplify your calculations by using a polygon on the map to limit the amount of data considered in calculations. By limiting the number of sites, you can reduce the time and cost of calculations and make the display of data objects
on the map clearer. You can select a pre-existing computation or focus zone as a filter zone or you can draw a new filtering
zone.
The data objects filtered by the polygon are reflected on the map and in the data tables. On the Network tab of the Explorer
window, any folder whose content is affected by the filtering zone appears with a special icon (
contents have been filtered.
), to indicate that the folder
When you have applied a polygon filter, you can perform the following actions on the filtered data:
Grouping (see "Grouping Data Objects" on page 65)

Sorting (see "Sorting Data" on page 69)
Filtering (see "Filtering Data" on page 71).
For more information on creating and editing a filtering zone, see "Using a Filtering Zone" on page 33.
1.8 Tips and Tricks

In this section, you will learn a few shortcuts and tricks to help you work more efficiently with Atoll:
82
"Undoing and Redoing" on page 83

"Refreshing Maps and Folders" on page 83
"Searching for Objects on the Map" on page 83
"Using the Status Bar to Get Information" on page 84
"Saving Information Displayed in the Event Viewer" on page 85
"Using Icons from the Toolbar" on page 85
"Using Shortcuts in Atoll" on page 88.

AT310_UMU_E0
1.8.1 Undoing and Redoing

You can undo or redo most actions in Atoll, up to a maximum of 10 actions. If you perform an action that can not be undone,
for example, a simulation, the Undo and Redo histories are erased.
For example, you can undo or redo:
Most modifications in the workspace: such as creating, deleting, and moving a site, a station or a group of stations,
modifying the antenna azimuth, moving a transmitter, or deleting a transmitter,
Tasks performed in the Explorer: such as creating and deleting objects (sites, transmitters, antennas, repeaters or
remote antennas, links, groups of hexagons, measurement paths, coverage predictions, maps, propagation models,
etc.).
Tasks performed in tables: such as adding or deleting records, pasting in tables.
To undo an action:
Select Edit > Undo.
To redo an action that you have undone:
Select Edit > Redo.
1.8.2 Refreshing Maps and Folders

Under certain circumstances, for example, when you add data that is inconsistent with an applied filter, the data displayed on
the map or in the Explorer window may not be actual. You can refresh the display to get Atoll to reload the data and reapply
the current folder configurations.
To refresh the display of the Explorer window and the map:
Click the Refresh button (
) on the toolbar or press F5.
1.8.3 Searching for Objects on the Map

Atoll provides the Find on Map tool for finding data objects on the map. You can search for some objects (sites, vectors, transmitters, repeaters) by their name or by any text field, using Find on Map. You can also use Find on Map to search for a point
on the map by its x and y coordinates. Additionally, the Find on Map tool enables you to find technology-specific attributes
such as a BSIC-BCCH pair in GSM. Using the Find on Map tool to find technology-specific attributes is covered in the chapter
for that technology.
This section explains:
"Searching for a Map Object by Its Name" on page 83

"Searching for a Map Object using Any Text Property" on page 84
"Searching for a Point on the Map" on page 84.
1.8.3.1 Searching for a Map Object by Its Name

You can use the Find on Map tool to search for the following map objects by name:
sites
transmitters
repeaters
remote antennas
vectors
To search for a map object by name using the Find on Map tool:
1. Select Tools > Find on Map. The Find on Map window appears.
2. From the Find list, choose the map object you are searching for:
-
Vector
Site
Transmitter
Repeater/Rem. Antenna
The map object you select appears in the Field box.

3. Enter the name of the object in the text box marked with an equal sign ("="). You can use an asterisk ("*") as a wild
card by entering it as the first character. For example, entering "*X*" will find all names which contain "X".
Atoll automatically begins searching and displays the results in the Find on Map window.
4. Select the object from the list. Atoll centres it in the map window.
83

Forsk 2011
1.8.3.2 Searching for a Map Object using Any Text Property

You can use the Find on Map tool to search for the following map object using any text (i.e., non-numeric) property:
sites
transmitters
repeaters
remote antennas
vectors.
To search for a map object by a text property using the Find on Map tool:
2. From the Find list, choose the map object you are searching for:
-
Site
Transmitter
Repeater/Rem. Antenna
Vector
3. From the Field list, select the text property on which you want to search, for example, "Antenna," or "Main Propagation Model."
4. Enter the name of the object in the text box marked with an equal sign ("="). You can use an asterisk ("*") as a wild
card by entering it as the first character. For example, entering "*X*" will find all names which contain "X".
Atoll automatically begins searching and displays the results in the Find on Map window.
5. Select the object from the list. Atoll centres it in the map window.
1.8.3.3 Searching for a Point on the Map

You can can use the Find on Map tool to search for a point by its x and y coordinate.
To search on the map for a point using the Find on Map tool:
2. From the Find list, choose Position.
3. Enter the X and Y coordinates of the point, using the same units as defined under Display on the Coordinates tab of
the Preferences dialogue (see "Projection and Display Coordinate Systems" on page 94).
4. Click Find. Atoll centres the point in the map window.
1.8.4 Using the Status Bar to Get Information

Atoll displays the following information, if available, about the current position of the mouse pointer in right side of the status
bar (see Figure 1.44):
the current X-Y coordinates (according to the defined display coordinate system)
the altitude (as defined in the DTM)
the clutter class (as defined in the clutter classes properties)
the clutter height (as defined in the clutter height file, or in the clutter classes).
X-Y coordinates
Altitude
Clutter class
Figure 1.44: Information displayed in the status bar
84

AT310_UMU_E0
1.8.5 Saving Information Displayed in the Event Viewer

Atoll displays information about the current document in the Event Viewer. The Event Viewer displays information ( ),
warning ( ), and error ( ) messages, as well as the progress of calculations. You can save the information displayed in the
Event Viewer in a log file.
To save events in the Event Viewer in a log file:
1. If the Event Viewer is not displayed, select View > Event Viewer to display it.
2. Click the event in the Event Viewer to select it. Click and drag to select several events.
3. Right-click the select event(s). The context menu appears.
4. Select Save As. The Save As dialogue appears.
5. In the Save As dialogue, select a destination folder, enter a File name, and select a file type from the Save as type list.
6. Click OK. The selected events are saved in the text file.
You can also automatically generate log files for each Atoll session and select the level of information displayed in the Event
viewer. For more information about these settings, see the Administrator Manual.
1.8.6 Using Icons from the Toolbar

You can access many commands in Atoll by clicking its icon on the toolbar. Some of them are also linked to shortcut keys (see
"Using Shortcuts in Atoll" on page 88).
The different icons located in the toolbar are listed below:
In the Standard toolbar

Open the Project Templates dialogue (CTRL+N)
Open the Open dialogue (CTRL+O)
Save the current document (CTRL+S)
New from an existing database
Refresh from database
Save pending changes in database
Import a file
Load a user configuration
Save a user configuration
Cut the selected data (CTRL+X)
Copy the selected data (CTRL+C)
Paste the content of the clipboard (CTRL+V)
Undo the last modification (CTRL+Z)
Redo the previous undone modification (CTRL+Y)
Print the current window (table or map) (CTRL+P)
Preview the current window before printing (table or map)
Open the Atoll Help
In the Radio Planning toolbar

Station template currently selected
Create a new transmitter or station based on the currently selected model
85

Forsk 2011
Create a new group of hexagons based on the currently selected station template
A new hexagon group is created in the Hexagonal Design folder if the check box to the left
of this folder is selected when you create a new station or a group of stations. If the check
box is not selected, you can create a new station without creating a corresponding hexagon group.
Create a new repeater or remote antenna for the currently selected transmitter
Graphically manage neighbours for the selected transmitter
Open the Point Analysis window
Calculate only invalid matrices, unlocked coverages, and pending simulations (F7)
Force the calculation of all matrices, unlocked coverages, and pending simulations (CTRL+F7)
Stop the calculation of all matrices, unlocked coverages, and pending simulations (ESC)
In the Map toolbar

Refresh display of map and folders (F5)
Select an object and disable zooming and panning tools.
Move the map (CTRL+D)
Map scale currently used
Previous view (zoom and location) (Alt+left arrow)
Next view (zoom and location) (Alt+right arrow)
Zoom in or out on the map and centre on the cursor location (CTRL+Q)
Define a zoom area on the map (CTRL+W)
Display a height profile
Measure distances on the map
Turn on tip text
Find on the map
In the Vector Editor toolbar

Create a new vector layer (in either the Geo or the Network tab)
Select the vector layer to edit
Draw a new polygon
Draw a new rectangle
Draw a new line
Draw points
Combine several vector polygons
Cut out areas in polygons
Create new polygon from overlapping areas
Split one polygon along the drawn lines.
86

AT310_UMU_E0
In the Windows toolbar

Display the Network tab of the Explorer window
Display the Geo tab of the Explorer window
Display the Parameters tab of the Explorer window
Display the Event Viewer
Display the Legend Window
Display the Panoramic Window
In the Table toolbar

Import data from a file into the table
Export data from the table to a file
Display the properties of the current record
Centre the current record on the map
Define which columns should be displayed
Hide the selected columns
Freeze the selected columns
Unfreeze all frozen columns
Filter by the selected fields
Filter excluding all records with the selected values
Define an advanced filter
Remove the filter
Sort the selected columns in ascending order
Sort the selected columns in descending order
Display statistics
Copy the contents of the top selected row into the rows below
Copy the contents of the bottom selected row into the rows above
Select the entire table
Align the contents of the selected columns to the left
Centre the contents of the selected columns
Align the contents of the selected columns to the right
Display the selected columns in bold
Display the selected columns in italics
When you place the cursor over an icon, tip text appears, giving a short description.
87

Forsk 2011
1.8.7 Using Shortcuts in Atoll

Atoll provides many shortcuts that enable you to access commonly used tools and commands more quickly.
The shortcuts available are listed below (some of the same commands can be accessed using a toolbar icon; see "Using Icons
from the Toolbar" on page 85):
Using the CTRL key:

-
CTRL++: Zoom in on the map (in the toolbar, click
CTRL+: Zoom out on the map (in the toolbar, click
CTRL+A: Select all records in a table
CTRL+C: Copy the selected data (in the toolbar, click
CTRL+D:
and click the map)

and right-click the map)
In tables: Copy the first cell of a selection down into all selected cells
In the map window: Move the map in the map window (in the toolbar, click
CTRL+E: Export the table of the selected Sites or Transmitters folder or view to a text file. For more information,
see "Exporting Tables to Text Files" on page 57.
CTRL+F: Open the Find on Map tool
CTRL+I: Import the table of the selected Sites or Transmitters folder or view from a text file. For more information,
see "Importing Tables from Text Files" on page 58.
CTRL+N: Open the Project Templates dialogue (in the toolbar, click
CTRL+SHIFT+N: Create a new document from an existing database
CTRL+O: Open the Open dialogue (in the toolbar, click
CTRL+P: Print the current window (in the toolbar, click
CTRL+Q: Select Zoom In/Out tool (in the toolbar, click
CTRL+S: Save the current active document (in the toolbar, click
CTRL+U: Copy the last cell of a selection up into all selected cells
CTRL+V: Paste the content of the clipboard (in the toolbar, click
CTRL+W: Define a zoom area on the map (in the toolbar, click
CTRL+X: Cut the selected data (in the toolbar, click
CTRL+Y: Redo the previous undone modification (in the toolbar, click
CTRL+Z: Undo the last modification (in the toolbar, click
)
)
)
)
Using the ALT key:

-
ALT+: Previous zoom and location on the map (in the toolbar, click
ALT+: Next zoom and location on the map (in the toolbar, click
ALT+F8: Open the Add-ins and Macros dialogue
)
)
Using the Function Keys

-
F5: Refresh display of map and folders (toolbar: select
F7: Calculate only invalid matrices, unlocked coverages, and pending simulations (in the toolbar, click
CTRL+F7: Force the calculation of all matrices, unlocked coverages, and pending simulations (in the toolbar, click
)
You can also access menus and commands by pressing the ALT key and typing the
underlined letter in the menu or command name.
88
Chapter 2
Starting a Project
This chapter explains how to start a new Atoll project.
"Before Starting a Radio-Planning Project" on page 91
"Creating an Atoll Document" on page 91
"Making a Backup of Your Document" on page 103
"Making and Sharing Portable Atoll Projects" on

page 105

Chapter 2: Starting a Project
90
Forsk 2011

Chapter 2: Starting an Atoll Project
AT310_UMU_E0
2 Starting an Atoll Project

When you want to start a new project, you base it on a template that has the data and folder structure necessary for the technology you are using. Once you have started your new Atoll project, you can modify the network parameters to meet your
particular needs. Several templates are supplied with Atoll: GSM GPRS EDGE, CDMA200 1xRTT 1xEV-DO, microwave radio
links, UMTS HSPA, WiMAX, and LTE. The actual templates supplied depend on the modules included with your Atoll installation. You can also create your own templates by opening an existing template, making the changes necessary to meet your
own needs and then saving it as a new template.
When you open an existing project, you can select it from the File menu if it is one of the last projects you have worked on,
or you can open it from the Open dialogue. Because Atoll can work with linked geographic data files, it may happen that one
of the linked files was moved or renamed since the last time you worked on that project. Atoll enables you to find the file and
repair the link.
"Before Starting a Radio-Planning Project" on page 91

"Creating an Atoll Document" on page 91.
2.1 Before Starting a Radio-Planning Project

For every radio-planning project you must assemble the information necessary:
Radio equipment: sites, transmitters, antennas, repeaters, and other equipment. For more information on radio
equipment, see the technology-specific chapters.
Radio data: frequency bands, technology-specific parameters, coordinate systems, etc. For more information on radio
data, see the technology-specific chapters.
Geographic data: clutter classes, clutter heights, DTM, population maps, etc. For more information on geographic
data, see Chapter 2: Starting an Atoll Project.
Once the necessary data have been assembled, you can create the Atoll document.
2.2 Creating an Atoll Document

Whatever the radio technology you will be modelling, you create an Atoll document in one of two ways:
From a document template: You can create a new Atoll document, including a multi-RAT document, from a template.
Atoll is delivered with a template for each technology you will be planning for. For information on creating a document
from a template, see "Creating a New Atoll Document from a Template" on page 91.
You can also create your own template by basing it on an existing document that you have already customised with,
for example, certain geo data or antennas.
From an existing database: When you create a new Atoll document from a database, the database you connect to
has been created with the technology or technologies, in the case of a multi-RAT document, and data you need.
Working with a database allows several users to share the same data while at the same time managing data consistency. The exact procedure for creating a new Atoll document from a database differs, depending on the database containing the data. Atoll can work with several common databases. For information on starting a document from a
database, see "Creating a New Atoll Document from a Database" on page 97.
2.2.1 Creating a New Atoll Document from a Template

You can create a new Atoll document from a template. Atoll has a template for each technology you will be planning for. Each
template provides data and a data structure suitable for the technology. For example, the tables and fields for transmitters
as well as the radio parameters available differ according to the project. As well, the objects that are available are appropriate
for the technology. For example, UMTS cells are only available in UMTS documents and TRX are only available in GSM-TDMA
documents.
If you create a multi-RAT document, Atoll enables you to select the multiple radio technologies you will be planning for. In a
multi-RAT document, the data and data structures for each radio technology planned for are made available in the new Atoll
document.
Once you have selected the appropriate template for your radio-planning project, you configure the basic parameters of the
Atoll document (see "Defining a New Atoll Document" on page 94).
"Templates Available" on page 92

"Creating a New Atoll Document from a Template" on page 92
91

Forsk 2011
"Defining a New Atoll Document" on page 94
2.2.1.1 Templates Available

Depending on your configuration of Atoll, the following templates are available:
GSM GPRS EDGE: This template can be used to model second generation (2G) mobile telecommunications using
TDMA (Time Division Multiple Access) technology. This template can be used to model the following technologies:
-
GSM (Global System for Mobile Communication): GSM is a 2G technology based on TDMA.
GPRS (General Packet Radio Service): GPRS is a packet-switched technology that enables data applications on
GSM networks. It is considered a 2.5G technology.
EDGE (Enhanced Data for Global Evolution): EDGE is an advancement for GSM/GPRS networks that triples data
rates. Because it is based on existing GSM technology, it allows for a smooth upgrade for GSM operators, giving
them capabilities approaching those of a 3G network, while remaining with the existing 2G system. Two types of
EDGE are considered: standard EDGE (also called EGPRS) and EDGE Evolution (EGPRS2).
CDMA2000 1xRTT 1xEV-DO: This template can be used to model third generation (3G) mobile telecommunications
based on CDMA2000 technology. CDMA2000 is an evolution of CDMA, or code division multiple access. This template
can be used to model the following technologies:
-
1xRTT (1 Radio Transmission Technology): 1xRTT is sometimes considered not as 3G but as 2.5G in terms of
mobile telecommunications. It offers increased voice capacity as compared to 2G technologies, but not as much
as pure 3G solutions.
1xEV-DO (1x Evolution - Data Only): 1xEV-DO is an evolution of CDMA2000 that provides data transfer rates of
over 10 times those of 1xRTT. It is considered a 3G solution and addresses, as its name suggests, data only.
UMTS HSPA: UMTS (Universal Mobile Telecommunications System) and HSDPA (High Speed Downlink Packet Access)
and HSUPA (High Speed Uplink Packet Access), collectively referred to as HSPA, are third generation (3G) mobile telecommunication systems based on WCDMA (Wideband Code Division Multiple Access) technology. Although WCDMA
is similar in implementation to CDMA, the two technologies are incompatible. UMTS and HSPA are usually implemented in place and over GSM networks.
TD-SCDMA: TD-SCDMA (Time Division Synchronous CDMA) is a 3G mobile telecommunication system based on Time
Division Duplex (TDD) mode. TD-SCDMA transmits uplink and downlink traffic in the same frame in different time
slots.
WiMAX: Atoll WiMAX is a state-of-the-art WiMAX and Broadband Wireless Access (BWA) network planning tool
developed in cooperation with world-leading WiMAX equipment suppliers. Atoll WiMAX supports IEEE 802.16e.
LTE: This template can be used to model the new fourth generation (4G) networks based on the UTRAN LTE (UMTS
Terrestrial Radio Access Networks Long Term Evolution) specifications proposed by the 3GPP. Atoll LTE is strictly follows the latest 3GPP LTE specifications, and has been developed in collaboration with the market-leading equipment
manufacturers. Atoll LTE is the first and most comprehensive LTE network planning tool available on the market.
3GPP Multi-RAT: This template can be used to model the most common multi-technology multiple technology
projects. When starting a new 3GPP multi-RAT project, Atoll allows you to select which radio technologies will be modelled in the same project: GSM, UMTS, and LTE.
The multi-RAT template can also be used to create a GSM, UMTS, or LTE single-RAT
document. By using the multi-RAT template to create a single-RAT document, you will
have the flexibility of being able to add additional technologies to the document in the
future.
2.2.1.2 Creating a New Atoll Document from a Template

To create a new document from a template:
1. Select File > New > From a Document Template. The Project Templates dialogue appears.
2. Select the template on which you want to base your document and click OK. Atoll creates a new document based on
the template selected.
-
If the template you selected was "Multi-RAT," Atoll displays a dialogue enabling you to select the radio technologies you want to model in the new document: GSM, UMTS, or LTE.
Figure 2.1 shows a new Atoll document based on the UMTS HSPA template. The Network tab of the Explorer window now
has a folder structure suitable for a UMTS HSPA radio-planning project, with, among other UMTS-specific elements, UMTS
HSPA HSPA simulations. Figure 2.2 shows the contents of the Geo tab of the new document. Figure 2.3 shows the contents of
the Parameters tab, with other UMTS HSPA parameters. The Antennas folder is expanded to show the UMTS-compatible
antennas suggested by Atoll. These can be modified or replaced.
92

AT310_UMU_E0
Figure 2.1: New Atoll document based on a template
Figure 2.2: New Atoll document Geo Tab
Figure 2.3: New Atoll document Parameters tab
When you create an Atoll document from a template, the document is not connected to a database.
To verify whether the document is connected to a database:
Select Document > Database > Connection Properties. The dialogue in Figure 2.4 appears.
Figure 2.4: An Atoll document based on a template is not connected to a database
93

Forsk 2011
2.2.1.3 Defining a New Atoll Document

Once you have created a new Atoll document as explained in "Creating a New Atoll Document from a Template" on page 92,
you configure the basic parameters of the Atoll document. You can accept the default values for some parameters, such as
basic measurement units, but you must set projection and display coordinate systems.
2.2.1.3.1
"Projection and Display Coordinate Systems" on page 94

"Setting a Coordinate System" on page 95
"Selecting the Degree Display Format" on page 95
"Setting Measurement Units" on page 96
Projection and Display Coordinate Systems

In Atoll, you define the two coordinate systems for each Atoll document: the projection coordinate system and the display
coordinate system. By default, the same coordinate system is used for both.
A projection is a method for producing all or part of a round body on a flat sheet. This projection cannot be done without
distortion, thus the cartographer must choose the characteristic (distance, direction, scale, area or shape) which is to be
shown appropriately at the expense of the other characteristics, or he must compromise on several characteristics1. The
projected zones are referenced using cartographic coordinates (meter, yard, etc.).
Two projection systems are widely used:
The Lambert Conformal-Conic projection: a portion of the earth is mathematically projected on a cone conceptually
secant at one or two standard parallels. This projection type is useful for representing countries or regions that lay
primarily east to west.
The Universal Transverse Mercator projection (UTM): a portion of the earth is mathematically projected on a cylinder
tangent to a meridian (which is transverse or crosswise to the equator). This projection type is useful for mapping large
areas that are oriented north-south.
A geographic system is not a projection, but a representation of a location on the earth's surface from geographic coordinates
(degree-minute-second or grade) giving the latitude and longitude in relation to the origin meridian (Paris for the NTF system
and Greenwich for the ED50 system). The locations in the geographic system can be converted into other projections.
Atoll has databases including more than 980 international coordinate system references, a database based on the European
Petroleum Survey Group and another one regrouping only France's coordinate systems. Atoll uses the cartographic coordinate systems for projection and either cartographic or geographic coordinate systems for display.
The maps displayed in the workspace are referenced with the same projection system as the imported geographic data files;
thus, the projection system depends on the imported geographic file. By choosing a specific display system, you can see (using
the rulers or status bars) the location of sites on the map in a coordinate system different from the projection coordinate
system. You can also position on the map sites referenced in the display system: the coordinates are automatically converted
from the projection system to the display system and the site is displayed on the map.
In Figure 2.5, the Brussels geographic data file has been imported. The map shows Brussels projected using the cartographic
UTM system (coordinates in metres). On the other hand, site coordinates are stated in the geographic WGS 84 system (coordinates in degrees-minutes-seconds).
1.
Snyder, John. P., Map Projections Used by the US Geological Survey, 2nd Edition, United States Government Printing
Office, Washington, D.C., 313 pages, 1982.
94

AT310_UMU_E0
Figure 2.5: UTM system used with WGS 84 system

All imported raster geographic files must be use the same cartographic system. If not, you
must convert them to a single cartographic system.
2.2.1.3.2
Setting a Coordinate System

Because you are working with maps, you must set a coordinate system for your Atoll document. By default, projection and
display coordinate systems are the same, but you can choose a different display coordinate system if you want.
To define the coordinate system:
1. Select Document > Properties. The Properties dialogue appears.
2. On the Coordinates tab, click the Browse button (
dialogue appears.
) to the right of the Projection field. The Coordinate Systems
3. In the Coordinate Systems dialogue, select a catalogue from the Find in list. For the projection system, only cartographic systems (
) are available.
4. Select a coordinate system from the list.
If you frequently use a particular coordinate system you can add it to a catalogue of
favourites by clicking Add to Favourites.
5. Click OK. The selected coordinate system appears in the Projection field and, by default, in the Display field as well.
6. If you wish to set a different coordinate system for the display, click the Browse button (
) to the right of the
Display field and repeat step 3. to step 5. For the display system, both cartographic systems (identified by the
symbol) and geographic systems (
2.2.1.3.3
) are available.
Selecting the Degree Display Format

Atoll can display longitude and latitude in four different formats. For example:
265629.9N
26d56m29.9sN
26.93914N
+26.93914
To change the degree display format:

2. On the Coordinates tab, select the format from the Degree Format list.
3. Click OK.
95

Forsk 2011
The degree format options apply only to the geographic coordinate systems.
2.2.1.3.4
Setting Measurement Units

When you create a new Atoll document, Atoll sets certain measurement units for reception, transmission, antenna gain,
distance, height and offset to internal defaults. You can accept these default measurement units, or you can change them
using the Properties dialogue.
To set the measurement units:
2. On the Units tab, select the desired unit for the following measurements:
-
Antenna Gain
Transmission
Reception
Distance
Height and Offset
Temperature
3. Click OK.
2.2.2 Working in a Multi-User Environment

A multi-user environment is one where a number of users, or groups of users, work simultaneously on given parts of a single,
large (perhaps nation-wide) network. Different user groups may be working on regional or smaller sections of the network.
This section describes the different components of multi-user environments and outlines their purpose.
When you create a new Atoll document from a database, Atoll loads the data to which you have rights from database into
your new document and then disconnects it from the database. The connection to the reference database is reactivated only
when necessary, thus ensuring access to the database by other users.
When you work on a document created from a database, you are working on data that you are sharing with other users.
Consequently, there are issues related to sharing data that do not arise when you are working on a stand-alone document.
For example, when you archive your changes to the database, the changes you have made may occasionally interfere with
changes other users have made and you will need to resolve this conflict.
"The Atoll Multi-User Environment" on page 96

"Creating a New Atoll Document from a Database" on page 97
"Working With a Document on a Database" on page 98
"Refreshing an Atoll Document from the Database" on page 100
"Archiving the Modifications of an Atoll Document in the Database" on page 100.
2.2.2.1 The Atoll Multi-User Environment

An Atoll multi-user environment consists of the following elements, connected over a network:
96
A central Atoll project: The central Atoll project can only be accessed, modified, and updated by the Atoll administrator. Through this central Atoll project, the Atoll administrator can manage all the data shared by all the individual
Atoll users or groups of users.
Shared data: Shared data are initially set up by the administrator using the central Atoll project and are then accessed,
modified, worked on, and updated by the Atoll users and the administrator. The shared data are mainly of the following three types:
-
The central database: The central database stores all the radio data of all the Atoll user documents. It is initiated
through the central Atoll project by the administrator, and is then subdivided into sections on which users or
groups of users can work simultaneously. Once the database is in place, users can modify their projects, refresh
their projects from the data stored in the database, and archive their modifications in the database. The use of a
database means that potential data conflicts due to modifications from other users, modified or deleted records,
for example, can be detected and resolved.
Shared geographic data: Shared geographic data files are usually stored on a common file server with a fast access
connection. Since geographic data files are usually large, they are usually linked to an Atoll file, i.e., they are stored
externally, so as to minimise the size of the Atoll file. Users who modify geographic data locally, for example,
editing edit clutter or traffic in their respective projects, usually store these modifications locally, since these modifications rarely have an impact on other users.

AT310_UMU_E0
Path loss matrices: The path loss matrices are calculated through the central Atoll project by the administrator
and can be updated only by the administrator. Each user can read these path loss data but cannot modify them.
If users modify their Atoll documents in such a way that the path loss data becomes invalid for their document,
any path loss matrices calculated by these users are stored locally, either embedded in the ATL file or linked to an
external file. The shared path loss data are not modified.
Shared path loss matrices are updated when the calculation administrator performs an update, taking into account the modifications made by other users which have been stored and updated in the central database. Shared
path loss matrices enable a number of users to work with a centralised path loss matrices folder, containing path
loss matrices corresponding to the central Atoll project.
User Documents: Individual user documents are initialised by the administrator but are later worked upon and managed by each user. User documents are Atoll files which are connected to the central database, load only the required
part of the geographic data (as defined by the CFG file, for example), and have access to the shared path loss matrices
folder.
Figure 2.6: Components of Multi-user Environments

For information on creating and maintaining the database, see the Administrator Manual.
2.2.2.2 Creating a New Atoll Document from a Database

When you create a new document from a database, you must connect to the database. Once connected, Atoll loads the database into a new Atoll document. Then the connected is interrupted. A new connection with the database will be created only
when necessary, in order to allow other users access to the database.
The exact procedure of connecting with the database differs from one database to another. Atoll can work with the following
databases:
Microsoft Access
Microsoft SQL Server
Oracle
Sybase
Microsoft Data Link files
The following sections give examples of connecting to two different databases and loading data:
"Connecting to a Database" on page 98.

"Selecting the Data to Load From the Database" on page 98.
97

Forsk 2011
An example of a new Atoll document created from a database is shown in:
2.2.2.2.1
"Working With a Document on a Database" on page 98
Connecting to a Database
To create a new document from a database:
1. Select File > New > From an Existing Database. The Open from a Database dialogue appears.
2. In the Files of type list, select the option corresponding to the type of your database. Depending on the type of the
database, a dialogue may appear where you can enter your User Name, Password, and Server.
Additional dialogues may open asking you to choose which project in the database to load
or which site list to load.
3. Click OK. The Data to Load dialogue appears, allowing you to select the data to load into Atoll as a new document (see
"Selecting the Data to Load From the Database" on page 98).
2.2.2.2.2
Selecting the Data to Load From the Database

When you create a new document from a database, you can select the data to be loaded from the database to create the
document in the Data to load dialogue. You can select which Project, Site List, Custom Fields Groups, and Neighbours to load.
If you load the intra-technology or the inter-technology neighbour list, Atoll will also load the associated exceptional pairs
table.
Figure 2.7: Selecting the data to load
2.2.2.3 Working With a Document on a Database

Figure 2.8 shows a new Atoll document based created from a database. The Network tab of the Explorer window now has a
folder structure suitable for a UMTS radio-planning project. The Sites folder is expanded to show that a document created
from a database can have additional data, such as sites, unlike a document created from a template. These can be modified
or replaced. Figure 2.9 and Figure 2.10 show the contents of the Geo and Parameters tabs of the new document, respectively.
98

AT310_UMU_E0
Figure 2.8: New Atoll document opened from a database

The new document might open with no site displayed in the map window. This is because
the north-west point of the project is by default the axis origin. You can re-centre the document on the data displayed in the Network tab by expanding the Sites folder, right-clicking
any site, and selecting Centre in Map Window from the context menu.
Figure 2.9: New Atoll document Geo Tab
Figure 2.10: New Atoll document Parameters tab
When you create an Atoll document from a database, you can view the characteristics of the database connection.
To view the characteristics of the database connection:
1. Select Document > Database > Connection Properties. The Database Connection dialogue appears (see Figure 2.11).
2. You can now:
-
Disconnect your document from the database.

If you disconnect your document from the database, it will be become a stand-alone
document and you will not be able to reconnect it to the database.
Modify your connection to the database.
99

Forsk 2011
Figure 2.11: The Database Connection dialogue
2.2.2.4 Refreshing an Atoll Document from the Database

As you are working on your document, other users who have access to the database may have modified some of the data. You
can ensure that you have the most recent data in your document by refreshing the information from the database. How
frequently you refresh the document depends on how frequently the database is updated. If the database is updated
frequently, you should refresh your document frequently as well, in order to continue working with the most up-to-date data.
To refresh an Atoll document from the database:
1. Select Document > Database > Refresh From the Database. The Refresh dialogue appears.
2. In the dialogue, you can do one of the following if you have modified your document but have not yet saved those
changes in the database:
-
Archive your changes in the database: This option allows you to archive your changes to the server instead of
refreshing your document from the server.
Refresh unmodified data only: This option allows you to refresh from the database only those items that you have
not modified in your document.
Cancel your changes and reload database: This option allows you to cancel any changes you have made and start
over from the point of the last archive to the database.
If you chose Refresh unmodified data only or Cancel your changes and reload
database, Atoll proceeds without asking for confirmation.
If you chose Archive your changes in the database, the Archive dialogue appears.
For information on using the Archive dialogue, see "Archiving the Modifications of
an Atoll Document in the Database" on page 100.
3. Under Take into account, you can select the neighbour lists, Intra-technology Neighbours and Inter-technology
Neighbours, to refresh.
4. Under Modifications Since the Last Refresh, you can select the Generate Report check box to create a report for the
refresh process.
5. Click OK. The document is refreshed according to the selected options.
If you selected to generate a report, Atoll creates a text file in CSV (Comma Separated Values) format in the temporary files
system folder, and opens it. You can then rename the file and save it where you want. The report lists all the modifications
(deletions, additions, and updates) that were stored in the database since the last time you refreshed or opened your document.
2.2.2.5 Archiving the Modifications of an Atoll Document in the Database

When you are working on an Atoll document that is attached to a database, you should from time to time archive the modifications you have made to the data on the database. How frequently you should archive your document depends on several
factors: the amount and size of changes you make, the number of other users using the database who might benefit from your
modifications, etc. What you can archive depends on the user rights the database administrator has given to you. For example,
you can have read access to the antennas table, allowing you to create a new Atoll document with the given antennas.
However, because only the administrator can modify the properties of the antennas, you will not be able to archive any
changes you make to the antennas without write access to the table.
The Atoll archiving process is flexible. You can archive all your modifications or only the site-related modifications. As well,
when you are archiving, Atoll shows you all modifications that will be archived and, if you want, you can archive only some of
them or even undo modifications you have made locally. Occasionally, other users might have modified some of the same
data and, when you archive your changes, Atoll will inform you of the possible conflicts and help you resolve them.
100
"Archiving All Modifications in the Database" on page 101

"Archiving Only Site-Related Data in the Database" on page 101

AT310_UMU_E0
2.2.2.5.1
"Resolving Data Conflicts" on page 101.
Archiving All Modifications in the Database

To archive all your modifications in the database:
1. Select Document > Database > Archive. The Archive dialogue appears (see Figure 2.12).
2. In the Archive dialogue, you can do the following:
-
Click Run All to archive all your changes to the database.

Select one item under Pending changes and click Run to archive the selected modification to the database
Select one item under Pending changes and click Differences to view the differences between the local item and
the item on the database.
Select one item under Pending changes and click Undo to refresh the modification with the original data from the
database.
Figure 2.12: The Archive dialogue

3. If some of the data has been modified on the database since you last refreshed, Atoll stops the archiving process and
asks you to resolve the conflict. For information on managing conflicts, see "Resolving Data Conflicts" on page 101.
4. When you are finished archiving, click Close.
2.2.2.5.2
Archiving Only Site-Related Data in the Database

Atoll allows you to archive only site-related data if you want. Which data is archived depends on the radio technology you are
working with. For example, in a UMTS HSPA radio planning project, the site-related data are: sites, transmitters, cells, and
neighbours.
To archive only the site-related data in the database:
1. Click the Data tab of the Explorer window.
2. Right-click the Sites folder. The context menu appears.
3. Select Archive. The Archive dialogue appears with only site-related data displayed.
4. In the Archive dialogue, you can do the following:
-
Click Run All to archive all your changes to the database.

Select one item under Pending Changes and click Run to archive the selected modification to the database
Select one item under Pending Changes and click Differences to view the differences between the local item and
the item on the database.
Select one item under Pending Changes and click Undo to refresh the modification with the original data from the
database.
5. If some of the data has been modified on the database since you last refreshed, Atoll stops the archiving process and
asks you to resolve the conflict. For information on managing conflicts, see "Resolving Data Conflicts" on page 101.
6. When you are finished archiving, click Close.
2.2.2.5.3
Resolving Data Conflicts

Atoll enables several users to use the same database by allowing user to load the data and then freeing the database for other
users. However, this also creates the possibility of two users modifying the same data. When the second user attempts to
archive his changes, Atoll warns him that the data have been changed since he last refreshed the data and that there is a
conflict.
101

Forsk 2011
Atoll allows you to resolve data conflicts. When Atoll finds a conflict, it displays the warning shown in Figure 2.13.
Figure 2.13: Conflict warning

You have three options:
Ignore: If you click Ignore, Atoll ignores items causing conflicts in the table being archived, archives all other modifications in the table, and continues with the next table. You can resolve the conflicts after the archiving process has
ended. However, if conflicts are found in other tables, Atoll will warn you with the Database Transfer Error dialogue
again.
Ignore All: If you click Ignore All, Atoll ignores all items causing conflicts in all tables being archived, and archives all
other modifications. You can resolve the conflicts after the archiving process has ended.
Abort: If you click Abort, the archiving process stops. You can attempt to resolve conflicts before restarting the
archiving process.
Whether you abort the archive process to resolve the conflict immediately, or wait until the end of the archive process, the
procedure to resolve the conflict is the same.
To resolve data conflicts one by one:
1. In the Pending Changes pane of the Archive dialogue, select the conflict you want to resolve and click Resolve. There
are two different types of data conflicts:
-
On a modified record: You are in the process of archiving your modifications on the database and another user
has modified the same data since you last archived or refreshed your data. A conflict is caused only by differences
in the same field of the same record between the database and the current Atoll document.
The Conflict in Changes dialogue appears, with the fields in conflict highlighted (see Figure 2.14). In the Conflict
in Changes dialogue, you can see the value of the field in the database in the Database values column, as well as
the value of the same field in your document in the Current values column.
Figure 2.14: The Conflict in Changes dialogue
If you want to overwrite the database value with the value of the same field in your document, select the check
box next to the highlighted change and click Okay. Your modification will be written to the database, overwriting the value there.
If you want to accept the value of the field in the database, clear the check box next to the highlighted change
and click Okay. Your modification will be lost and the value in the database will remain unchanged.
On a deleted record: You are in the process of archiving your modifications on the database and another user has
deleted a record since you last archived or refreshed your data. For information, see "Resolving Data Conflicts" on
page 101.
Atoll displays a message explaining that the record you are trying to update has been deleted from the database
(see Figure 2.15). Select one of the following:
102

AT310_UMU_E0
Figure 2.15: Conflict on a deleted record

-
Yes: Select Yes to store your modifications in the database, thereby recreating the deleted record.
No: Select No to abandon your modifications to this record and delete this record from your document.
Cancel: Select Cancel to cancel.
2. Click Close to close the Archive dialogue.

To resolve all the data conflicts:
1. In the Pending Changes pane of the Archive dialogue, select any conflict and click Resolve All. Atoll displays a message
explaining how Resolve All works (see Figure 2.16). Select one of the following:
Figure 2.16: Resolving all the data conflicts simultaneously

-
Yes: Select Yes to accept all the modifications made by other users in the database and update your document
with values from the database.
No: Select No to overwrite the modifications made by other users in the database with the values from your document.
Cancel: Select Cancel to cancel.
2. Click Close to close the Archive dialogue.

You should only resolve all the data conflicts when you are certain about the
modifications.
2.3 Making a Backup of Your Document

Atoll can create and automatically update backups of documents you are working on. Once you have saved the document,
Atoll creates a backup of the original document and updates it at a defined interval. For example, for a document named
"filename.atl," Atoll will create a backup file called "filename.atl.bak" in the same folder as the original document. You can
define the update interval each time you start Atoll.
You can also configure Atoll to create automatic backups of external path loss matrices (LOS files) by setting an option in the
atoll.ini file. For more information, see the Administrator Manual.
When you have activated automatic backup, Atoll automatically creates a backup for every document open. Consequently, if
you have a lot of documents open, this operation can take a long time. However, you can optimise the process by opening
large documents in separate Atoll sessions, instead of in the same Atoll session. This also improves memory management
because each instance of Atoll has its own 2 GB (under 32-bit operating systems; 4 GB under 64-bit operating systems)
memory allocation. If you open two large documents in the same Atoll session, these documents will use the same 2 GB
memory pool. If you open them in two different Atoll sessions, each document will have its own 2 GB allocated memory.
103

Forsk 2011
"Configuring Automatic Backup" on page 104

"Recovering a Backup" on page 104.
2.3.1 Configuring Automatic Backup

You can set up automatic backup for each Atoll session.
To configure automatic backup:
1. Select Tools > Configure Auto Backup. The Auto Backup Configuration dialogue appears (see Figure 2.17).
Figure 2.17: Auto Backup Configuration dialogue

2. Select the Activate Auto Backup check box.
3. Select the Prompt before starting Auto Backup check box if you want Atoll to ask you before saving the backup of
your file every time (see Figure 2.18).
4. Enter a time interval, in minutes, between consecutive backups in the Automatically save backups every text box.
It can take a long time to back up large documents. Therefore, you should set a correspondingly longer interval between backups when working with large documents in order
to optimise the process.
5. Click OK.
If you selected the Prompt before starting automatic backup check box, Atoll prompts you each time before backing up the
document. If you click OK, Atoll proceeds to back up all open documents. If you click Cancel, Atoll skips the backup once.
Figure 2.18: Automatic backup prompt

The automatic backup timer is stopped while the prompt is displayed. Atoll displays a message in the Event Viewer every time
a backup file is updated. If you are performing calculations, i.e., coverage predictions or simulations, the automatic backup is
delayed until the calculations have ended. The timer starts again once the calculations are over. If you save the original document manually, the timer is reset to 0.
2.3.2 Recovering a Backup

You can easily recover your backup document and open it in Atoll just like any other Atoll document.
To recover your backup document:
1. Using Windows Explorer, navigate to the folder containing your original Atoll document and its backup.
2. If the original document was named "filename.atl," the backup document will be in the same folder and will be called
"filename.atl.bak". Rename the document and remove the BAK extension. For example, you could change the name
to "filename-backup.atl."
104

AT310_UMU_E0
If you just remove the BAK extension, your backup file will have the same file name as
the original file and Windows will not allow you to rename the file. Therefore, it is safer
to give a new name to the backup file and keep the original file until you are sure which
version is most recent.
3. Open the renamed backup document in Atoll. You will be able to recover all the work up to the last time the backup
was saved.
2.4 Making and Sharing Portable Atoll Projects

You can create portable Atoll documents in two ways:
by embedding all the geographic data in the ATL file, or

by creating a compressed archive (ZIP file) containing the ATL file and all geographic data linked to the Atoll document.
In most working environments, geographic data files are stored on a common file server and are linked to the ATL documents
of different users over a network. Often these geographic data files are quite large, and it is not feasible to embed these files
in an ATL file for reasons related to file size, memory consumption, and performance. It is, therefore, more useful to make a
project portable by creating an archive that contains the ATL and all geographic data files.
Atoll lets you make an archive containing the ATL file and all geographic data directly from the File menu.
To make an archive containing the ATL file and all linked geographic data files:
1. Select File > Save to Zip. The Save As dialogue appears.
2. Select the folder where the created archive is to be stored, enter a File name for the archive to be created, and select
"Zip Files (*.zip)" from the Save as type list.
Atoll creates a ZIP file containing:
-
A copy of the ATL file with the same name as the name of the archive (ZIP file).
The ATL file added to the archive contains all the data that might be embedded in it (path loss matrices, geographic
data, coverage predictions, simulation results, measurement data, etc.).
A ".losses" folder containing a pathloss.dbf file and a LowRes subfolder which contains the pathloss.dbf file corresponding to the extended path loss matrices.
Externally stored path loss matrices are not added to the archive because they are not necessary for making a
portable document; they can be recalculated based on the network and geographic data in the ATL file. The pathloss.dbf files are stored in the archive because they are needed when reopening the archive in Atoll.
A "Geo" folder with all the linked geographic data available on the Geo tab of the Explorer window for the Atoll
document.
This folder contains subfolders with the same names as the folders on the Geo tab. Geographic data that are found
outside folders on the Geo tab are stored in files under the Geo folder, and data present within folders on the Geo
tab are stored inside their respective folders. If the geographic data files linked to the document are located on a
remote computer, such as a file server over a network, they are first copied to the local computer in the Windows
temporary files folder and then added to the archive.
Once the portable archive is created, you can open it directly from Atoll without first having to extract it using another tool.
To open an archive containing an ATL file and all linked geographic data files:
1. Select File > Open from Zip. The Open dialogue appears.
2. Select the ZIP file that contains the ATL file and linked geographic data files.
3. Click Open. The Browse For Folder dialogue appears.
4. Select the folder where you want to extract the contents of the ZIP file.
5. Click OK. Atoll extracts all the files from the archive to the selected folder. If necessary, it creates the subfolders
required for extracting the contents of the Geo folder. Once Atoll has finished extracting files from the archive, it
opens the extracted ATL file. Geographic data extracted from the archive are linked to the ATL file.
You do not need to have a compression utility, such as WinZip or WinRAR, installed
on the computer for this feature.
The highest compression level is used when creating the archive.
105

106
Forsk 2011
Chapter 3
Geographic Data
This chapter provides information on working with
geographic data in an Atoll project.
"Geographic Data Types" on page 109
"Supported Geographic Data Formats" on page 111
"Importing Geo Data Files" on page 111
"Digital Terrain Models" on page 118
"Clutter Classes" on page 118
"Clutter Heights" on page 122
"Contours, Lines, and Points" on page 122
"Scanned Images" on page 124
"Population Maps" on page 125
"Custom Geo Data Maps" on page 126
"Setting the Priority of Geo Data" on page 129
"Displaying Information About Geo Data" on page 132
"Geographic Data Sets" on page 132
"Editing Geographic Data" on page 134
"Saving Geographic Data" on page 136

Chapter 3: Geographic Data
108
Forsk 2011

AT310_UMU_E0
3 Geographic Data
Several different geographic data types are used in an Atoll document. For example: the digital terrain model (DTM), clutter
classes, clutter heights, scanned images, population maps, and traffic data maps are types of the geographic data that you can
import or create. Some data types, such as clutter classes, can be used to give more realistic calculations. Other types such as
scanned images, are used to create a more realistic display of the region under study.
You can import a wide variety of both vector and raster-format geo data files. When you import a geo data file into Atoll, you
can decide in which folder it goes. The Geo tab of the Atoll Explorer window has folders for the commonly used data types.
Therefore, choosing a folder is choosing what the file will be used for. You can also create your own data type by importing a
file and defining what data is to be used.
Once you have imported a file into the Atoll document, you can edit the data, define how the geo data will be displayed. Atoll
also allows you to manage multiple files for a single data type, deciding the priority of data files with different information or
different resolutions. You can also display geo data over items on the Network tab, either by transferring them to the Network
tab, or by importing them directly to the Network tab.
You can also create and edit geographic data. You can add a vector layer to certain data types to which you can add contours,
lines, or points, create new geographic data, or modify existing data. You can also create raster-based geographic data such
as traffic maps or clutter classes.
You can export most geo data objects (for example, DTM, clutter classes, clutter heights, raster polygons, or vector layers) for
use in other Atoll documents or in other applications. Atoll also allows you to save changes you make to geo data objects back
to the original files. This enables you to update the original files and, through the process of saving them, recompact the file.
This chapter explains the following topics:
"Geographic Data Types" on page 109

"Supported Geographic Data Formats" on page 111
"Importing Geo Data Files" on page 111
"Digital Terrain Models" on page 118
"Custom Geo Data Maps" on page 126
"Setting the Priority of Geo Data" on page 129
"Editing Geographic Data" on page 134
"Saving Geographic Data" on page 136.
3.1 Geographic Data Types

An Atoll document can contain several different geographic data types. Atoll supports a wide range of file formats for
geographic data files. The different geographic data types play different roles in the Atoll document:
Geographic data used in propagation calculation:

-
Geographic data used in dimensioning:

-
Traffic maps
Geographic data used in statistics:

-

Clutter classes
Clutter heights
Population maps
Custom maps
Geographic data used for display purposes:

-
Scanned maps
Images from web map services (WMS)
Contours, lines, and points representing, for example, roads, railways, or regions.
In this section, the following data types are described:
"Digital Terrain Model" on page 110

109

Forsk 2011

"Traffic Data Maps" on page 110
"Custom Data Maps" on page 110.
Digital Terrain Model

The DTM describes the elevation of the ground over sea level. You can display the DTM in different ways: by single value,
discrete values, or by value intervals (see "Display Properties of Objects" on page 23).
The DTM is automatically taken into account by the propagation model during computations.
Clutter Classes
The clutter class geo data file describes land cover or land use. Clutter classes are taken into account by the propagation model
during computations.
Each pixel in a clutter class file contains a code (from a maximum of 256 possible classes) which corresponds to a clutter class,
or in other words to a certain type of ground use or cover. The height per class can be defined as part of the clutter class,
however, the height will be defined as an average height for each clutter class. For information on defining the height per clutter class, see "Defining Clutter Class Properties" on page 119. Clutter heights can also be defined by a separate clutter heights
file (see "Clutter Heights" on page 110). A clutter height map can represent height much more accurately because it allows a
different height to be assigned for each pixel of the map.
Clutter Heights
Clutter height maps describe the altitude of clutter over the DTM with one altitude defined per pixel. Clutter height maps can
offer more precise information than defining an altitude per clutter class because, in a clutter height file, it is possible to have
different heights within a single clutter class.
When clutter altitude is defined both in clutter classes and in a clutter height map, clutter altitude is taken from the clutter
height map.
You can display the clutter height map in different ways: by single value, discrete values, or by value intervals (see "Display
Properties of Objects" on page 23).
The only propagation models that can take clutter heights into account in calculations are
the Standard Propagation Model and WLL model.
Contours, Lines, and Points

Atoll supports contours, lines, and points to represent polygons such as regions, or lines such as roads or coastlines, or points.
They are used for display only and have no effect on computations. Contours can also be used to create filtering polygons or
computation or focus zones.
Scanned Images
Scanned images are geographic data files which represent the actual physical surroundings, for example, road maps or satellite images. They are used to provide a precise background for other objects or for less precise maps and are used only for
display; they have no effect on calculations.
Population Maps
Population maps contain information on population density or on the total number of inhabitants. Population maps can be
used in prediction reports in order to display, for example, the absolute and relative numbers of the population covered.
Population maps have no effect on prediction and simulation results.
Traffic Data Maps
Traffic data maps contain information on capacity and service use per geographic area. Traffic data maps are used for network
capacity analyses.
Custom Data Maps
You can import many different types of files for, for example, revenue, rainfall, or socio-demographic data. You could use the
imported data in prediction reports. For example, you could display the predicted revenue for defined coverage.
These imported data have no effect on prediction and simulation results.
110

AT310_UMU_E0
3.2 Supported Geographic Data Formats

Atoll supports the following geographic data formats:
DTM files in the following formats: TIF (8 or 16-bit integer), BIL (8, 16 or 32-bit integer, 32-bit float), Planet (16-bit
integer), BMP (8-bit integer), GRD Vertical Mapper (16-bit integer), and Erdas Imagine (8, 16 or 32-bit integer, 32-bit
float)
Clutter height files in the following formats: TIF (8 or 16-bit integer), BIL (8, 16 or 32-bit integer, 32-bit float), Planet
(16-bit integer), BMP (8-bit integer), GRD Vertical Mapper (16-bit integer), and Erdas Imagine (8, 16 or 32-bit integer,
32-bit float)
Clutter class and traffic files in the following formats: TIF (8-bit), BIL (8-bit), IST (8-bit), BMP (8-bit), Planet, GRC Vertical
Mapper (8-bit), and Erdas Imagine (8-bit)
Vector data files in the following formats: AGD, DFX, Planet, SHP, MIF, and TAB.
Vector traffic files in the following formats: AGD, DFX, Planet, SHP, MIF, and TAB.
Scanned image files in the following formats: TIF (1 to 24-bit), JPEG 2000 (1 to 24-bit), BIL (1 to 24-bit), IST (1 to 24-bit),
BMP (1 to 24-bit), Planet, Erdas Imagine (1 to 24-bit), GRC Vertical Mapper (1 to 24-bit), and ECW (8 or 24-bit)
Population files in the following formats: TIF (16-bit), BIL (16-bit), IST (16-bit), Planet, BMP (16-bit), Erdas Imagine
(16-bit), GRD/GRC Vertical Mapper (16-bit), AGD, DXF, SHP, MIF, and TAB.
Other data in the following formats: TIF (16-bit), BIL (16-bit), IST (16-bit), Planet, BMP (16-bit), Erdas Imagine (16-bit),
GRD/GRC Vertical Mapper (16-bit), AGD, DXF, SHP, MIF, and TAB.
All raster maps imported must have the same projection coordinate system.
3.3 Importing Geo Data Files

You can import the geographic data you need into the current Atoll document. As explained in "Supported Geographic Data
Formats" on page 111, Atoll supports a variety of both raster and vector file formats. When you import a new geo data file,
Atoll recognises the file format and suggests the appropriate folder on the Geo tab of the Explorer window. You can embed
geo data files in the Atoll document while you are importing them or afterwards (see "Embedding Geographic Data" on
page 117).
You can share the paths of imported maps and display settings with other users by using Atolls user configuration files. For
information on exporting the paths of your documents files or to import the path from another document using user configuration files, see "Geographic Data Sets" on page 132.
The instructions in this section do not apply to custom geo data maps. For information on
importing or creating an custom geo data map, see "Custom Geo Data Maps" on page 126.
"Importing a Raster-format Geo Data File" on page 111

"Importing a Vector-format Geo Data File" on page 113
"Importing MSI Planet Data" on page 114
"Importing a WMS Raster-format Geo Data File" on page 115
"Grouping Geo Data Files in Folders" on page 117
"Embedding Geographic Data" on page 117.
You can use the drag-and-drop feature to import geo data files into a document. The
format is automatically recognized and Atoll presents you with the appropriate
dialogue.
3.3.1 Importing a Raster-format Geo Data File

All raster geo data files must be represented in the same projection coordinate system as the Atoll document itself.
To import a geographic data file in a raster format:
1. Select File > Import. The Open dialogue appears.
2. Select the geo data file you want to import.
111

Forsk 2011
You can import more than one geo data file at the same time, providing that the geo data files are of the same type.
You can select contiguous files by clicking the first file, pressing SHIFT and clicking the last file you want to import. You
can select non-contiguous files by pressing CTRL and clicking each file.
3. Click Open. The File Import dialogue appears (see Figure 3.1).
If the Vector Import dialogue appears, go to "Importing a Vector-format Geo Data File" on
page 113.
Depending on the type of geo data file you are importing, choose one of the following options:
-
DTM: Select Altitudes (DTM) from the Data Type list.

Clutter Classes: Select Clutter Classes from the Data Type list.
Clutter Heights: Select Clutter Heights from the Data Type list.
Scanned Images: Select Image or Scan from the Data Type list.
Population:
i.
Select Population from the Data Type list. The Use as list becomes available.
ii. Select from the Use as list whether the imported data are to be interpreted as a Density (number of inhabitants per square kilometre) or as a Value (number of inhabitants).
-
Custom Geo Data: See "Custom Geo Data Maps" on page 126.
Traffic Data Maps: Select Traffic Density from the Data Type list.
4. By default, the imported file is linked to the Atoll document. To embed the data file in the Atoll document, select the
Embed in Document check box. For information on embedding files, see "Embedding Geographic Data" on page 117.
5. Click Import. The geo data file is imported and listed in the Geo tab of the Explorer window.
When you import a traffic data map, the traffic maps Properties dialogue appears:
a. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must
equal 100.
b. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must
equal 100.
c. Under Services (%), enter the percentage of each service type used in the map. The total percentages must equal
100.
d. Under Clutter Distribution, enter for each clutter class the percentage of indoor users.
An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define
a clutter weighting for traffic density maps because the traffic is provided in terms of user density per pixel.
e. For UMTS and CDMA, select whether the users are active in the Uplink/Downlink, only in the Downlink, or only
in the Uplink.
f. Click OK.
Figure 3.1: Importing a clutter class file
112

AT310_UMU_E0
3.3.2 Importing a Vector-format Geo Data File

When you import geo data files in vector format, their geographic system can be converted to the system used by the Atoll
document. When you import extremely large vector geo data files, for example, vector files that cover an entire country, you
must ensure that at least the centre of the bounding box defining the vector file is within the projection coordinate system
defined for the Atoll document.
To import a vector-format geographic data file:
2. Select the geo data file you want to import.
You can import more than one geo data file at the same time, providing that the geo data files are of the same type.
You can select contiguous files by clicking the first file, pressing SHIFT and clicking the last file you want to import. You
can select non-contiguous files by pressing CTRL and clicking each file.
3. Click Open. The Vector Import dialogue appears (see Figure 3.4).
If the File Import dialogue appears, go to "Importing a Raster-format Geo Data File" on
page 111.
Depending on the type of geo data file you are importing, choose one of the following options:
-
Vector Data:
-
Select Geo from the Import to list.
Population:
i.
Select Population from the Import to list.
ii. Under Fields to be imported, the first list contains the attributes of the population vector data file that you
are importing, and the second list lets you select whether the attribute corresponds to population density or
to a number of inhabitants.
iii. Select from the first list which field is to be imported and from the second list whether the imported field is a
Density (number of inhabitants per square kilometre for polygons, number of inhabitants per kilometre for
lines, or number of inhabitants for points) or a Value (number of inhabitants) (see Figure 3.2 and Figure 3.3).
Figure 3.2: Population density (number of inhabitants/km)
Figure 3.3: Population values (number of inhabitants per item polygon/road/point)

-
Custom Geo Data:

-
See "Custom Geo Data Maps" on page 126.
Traffic Data Maps: Select Traffic from the Import to list.
4. By default, the imported file is linked to the Atoll document. To embed the data file in the Atoll document, select the
Embed in Document check box. For information on embedding files, see "Embedding Geographic Data" on page 117.
5. Click Import. The geo data file is imported and listed in the Geo tab of the Explorer window.
113

Forsk 2011
Figure 3.4: Vector Import dialogue
You can import ellipses and arcs from MapInfo files (MIF and TAB). Rectangles are
interpreted as polygons.
You can define mappings between the coordinate system used for the MapInfo/
ESRI vector files, defined in the corresponding MIF/PRJ files, and Atoll. This way,
when you import a vector file, Atoll can detect the correct coordinate system automatically. For more information about defining the mapping between coordinate
systems, please refer to the Administrator Manual.
3.3.3 Importing MSI Planet Data

MSI Planet data are contained in a series of files described in index files. The index file is in ASCII text format and contains
the information necessary to identify and properly interpret each data file. When you import MSI Planet data, you can import
each type of data separately, by importing the corresponding index file, or you can import several MSI Planet data files at
the same time, by importing several index files.
"Importing One MSI Planet Data Type" on page 114

"Importing a MSI Planet Database" on page 115.
3.3.3.1 Importing One MSI Planet Data Type

When you want to import a certain type of MSI Planet data, such as a DTM or clutter heights, you import the index file
containing the information necessary to import the set of files containing the data.
To import one type of MSI Planet data:
2. Select the index file you want to import and click Open. The Data Type dialogue appears (see Figure 3.5).
Figure 3.5: Importing an MSI Planet index file
114

AT310_UMU_E0
3. Select the type of data you are importing and select the Embed check box if you want to embed the data in the current
Atoll document.
4. Click OK to import the data into the current Atoll document.
3.3.3.2 Importing a MSI Planet Database

You can import all available MSI Planet data at the same time by importing all index files.
To import the MSI Planet database:
2. Select "Planet database" from the Files of Type list. The Planet Data Import dialogue appears (see Figure 3.6).
Figure 3.6: Importing an MSI Planet database

3. For each type of data that you want to import:
a. Select the corresponding check box.
b. If you want to embed the data, select the Embed check box.
c. To locate the MSI Planet index file, click
. The Open dialogue appears.
d. Select the MSI Planet index file and click Open. The path and name of the file appears in the corresponding field
of the Planet Data to Be Imported dialogue.
4. If you are also importing network data, select the network Technology.
5. When you have selected all the types of data you want to import, click OK. The data is imported into the current Atoll
document.
3.3.4 Importing a WMS Raster-format Geo Data File

You can import raster images from a Web Map Service (WMS) server into your Atoll document. The image must be in TIF
format. All images imported at the same time are imported as a single image. Before you import them, you can arrange them
by placing on top the image that is the most important, such as roads. Or, you can place the least transparent image towards
the bottom so that the other images imported at the same time remain visible.
The image will be referenced in the document; it can not be embedded. Only WMS data mapped with a projection system (for
example, the Lambert Conformal-Conic or the Universal Transverse Mercator projection) can be imported. Before importing
an image from a WMS server, you must ensure that the coordinate system used in your document is the same projection
system supported by the server. All raster geo data files must be represented in the same projection coordinate system as
that used by the Atoll document itself.
115

Forsk 2011
To import a geographic data file from a web map service:

2. From the Files of Type list, select Connection to a Web Map Services server. The Web Map Services Data Import dialogue appears.
3. Select the URL of the WMS server from the Server URL list or enter it directly.
The list of WMS servers that appears in the Server URL list are defined by entries in the
atoll.ini file. For information on defining these entries, see the Administrator Manual.
4. Click the Connect button. Atoll connects to the URL of the WMS server and displays the information available along
with a description of the service (Figure 3.7 on page 116).
Figure 3.7: The Web Map Services Data Import dialogue

5. In the left pane of the Web Map Services Data Import dialogue, navigate to the item you want to import by clicking
the Expand button ( ) to open each level.
6. Select either the image you want to import, or the image group, i.e., a group preceded by an Expand button ( ).
7. Click
for each image you want to import. The files you want to import appear in the right pane of the Web Map
Services Data Import dialogue.
You can remove an image or group of images from the images to be imported by selecting
it in the right pane and clicking
8. Arrange the order in which you want the images to appear by selecting each image in the right pane and clicking
to move it towards the top or
to move it toward the bottom. The images will be imported as a single object and
their appearance will depend on the order you define here.
9. The Web Map Import dialogue appears. The following information is given about the imported WMS data:
-
Data Types: "Image or Scan" is selected.

Geographic Coordinates: The geographic coordinates are the WMS data are given.
10. The Name suggested is the name of the lowest layer to be imported. If desired, you can modify this name.
11. Click Import. The image is imported by reference into the Atoll document. You can not embed a WMS image in your
document.
If you had selected more than one image or an image group, Atoll imports the group as a single object. You can not
modify this object. If you want to remove one of the images or add another one you will go through the import process
again.
116

AT310_UMU_E0
3.3.5 Grouping Geo Data Files in Folders

By default, when you import scanned images and contours, lines, and points, they appear directly on the Geo tab. Other data
files, such as clutter classes, are listed together in a single Clutter Classes folder. You can, however, group scanned images and
contours, lines, and points into folders as well.
Once grouped, these geo data files can be displayed or hidden and moved more easily. They retain, however, their own individual display settings; the display settings cannot be managed at the folder level.
You create the folder when you import the first geo data file that will be imported into it. When you import the next geo data
file, either raster or vector, you can import it directly into the new folder.
To create a new geo data folder when importing:
2. Select the geo data file and click Open. If the file to be imported is a raster file, the File Import dialogue appears (see
Figure 3.1). If the file to be imported is a vector file, the Vector Import dialogue appears (see Figure 3.4).
3. From the Data Type list (on the File Import dialogue) or the Import To list (on the Vector Import dialogue), select New
folder in Geo. The New Folder dialogue appears.
If you want to import your file to the Network tab, you can select New folder in Network.
4. Enter a name for the folder in Folder Name box and click OK.
5. Click Import. Your file is imported into the newly created folder.
You can now import other geo data files into this folder by selecting it from the Data Type list (on the File Import dialogue) or
the Import To list (on the Vector Import dialogue) when you import.
You can transfer geo data that has been imported from the Geo tab to the Network tab,
or vice versa. Right-click the data in the Explorer window and select Move to Network Tab
or Move to Geo Tab.
3.3.6 Embedding Geographic Data

By default, when you import a geo data file, Atoll creates a link to the file. You can, however, choose to embed the geo data
file in your Atoll document, either when you import it or later. When Atoll is linked to a geo data file, the geo data file remains
separate and modifying or saving the Atoll document has no effect on the geo data file. When the geo data file is embedded
in the Atoll document, it is saved as part of the document.
Both linking and embedding present advantages and disadvantages. For more information, see the Administrator Manual.
If you are using distributed calculations, you must link your geo data files. Distributed
calculations will not work with embedded geo data files. For information, see the
Administrator Manual.
To embed a geo data file in the current Atoll document while you are importing:
Select the Embed in Document check box on the File Import or Vector Import dialogue box.
To embed a geo data file that is already linked to the current Atoll document:
2. Right-click the file you want to embed in the current document.
4. Click the General tab of the Properties dialogue.
5. Click Embed.
6. Click OK. The geo data file is now embedded in the current Atoll document.
117

Forsk 2011
3.3.7 Repairing a Broken Link to a Geo Data File

By default, when you import a geo data file, Atoll creates a link to the file; the geo data file remains separate and modifying
or saving the Atoll document has no effect on the geo data file. If, however, the geo data file is moved, the link will be broken.
an AtollAtollAtollAtollTo repair a broken link from within the Atoll document:
-
If the geo data file is in a folder, such as the Clutter Classes, Traffic Maps, or DTM folder, click
folder.
to expand the
2. Right-click on the geo data file whose link you want to repair. The context menu appears.
4. On the General tab of the Properties dialogue, click the Find button.
5. Browse to the geo data file, select it and click OK.
3.4 Digital Terrain Models

The Digital Terrain Model (DTM) is a geographic data file representing the elevation of the ground over sea level.
To manage the properties of the DTM:
2. Right-click the Digital Terrain Model folder.
4. Click the Display tab to define the display properties for the DTM.
-
For information on Display tab settings, see "Display Properties of Objects" on page 23.
5. Move the Relief slider towards Flat, if you want to display very few little relief or towards x6 if you want to emphasise
the differences in altitude.
6. Click OK to close the Properties dialogue.
3.5 Clutter Classes

The clutter class geo data file describes land cover or land use.
Each pixel of a clutter class file contains a code (from a maximum of 256 possible classes) which corresponds to a clutter class,
or in other words to a certain type of ground use or cover. The height per class can be defined as part of the clutter class,
however this height is only an average per class. A clutter height map can represent height much more accurately because it
allows a different height to be assigned for each bin of the map. For information on clutter height maps, see "Clutter Heights"
on page 122.
"Assigning Names to Clutter Classes" on page 118

"Defining Clutter Class Properties" on page 119
"Adding a Clutter Class" on page 121
"Refreshing the List of Clutter Classes" on page 121
"Displaying Total Surface Area per Clutter Class" on page 122.
3.5.1 Assigning Names to Clutter Classes

The clutter class file identifies each clutter class with a code. To make it easier to work with clutter classes, you can assign a
descriptive name to each clutter class name. When a clutter class has a descriptive name, it is the name that appears in tool
tips and reports.
When you import a clutter class file in BIL, TIF, JPEG 2000, or IMP format, Atoll can automatically assign names to clutter
classes if the clutter class file has a corresponding MNU file. The MNU file contains a list with the clutter class codes and their
corresponding names. For more information on the MNU file format and on creating an MNU file, see the Technical Reference
Guide.
To assign names to clutter classes:
2. Right-click the Clutter Classes folder.
118

AT310_UMU_E0

4. Click the Description tab of the Properties dialogue.
5. In the Name column, enter descriptive text for each class identified in the Code column.
3.5.2 Defining Clutter Class Properties

The parameters are applied in relation to the location of the receiver being studied and the clutter class of the receiver location. These parameters can be set on the Properties dialogue:
To define clutter class properties:
4. Click the Description tab of the Properties dialogue.
5. Enter a Name and average Height (m) for each code.
If the Height field is left blank, propagation models which use the height information of
clutter classes will assume a clutter height of "0" if there is no clutter height map.
6. Enter default values in the first row of the table on the Description tab. or information about each field, see the
descriptions in the following step.
The default values are used if no clutter map is available. Even if there is a clutter classes map, you can select the Use
default values only check box on the at the bottom of the Description tab to make Atoll use the values specified in
this row instead of the values defined per clutter class.
7. If desired, you can enter a value for each of the following fields applicable to the current document:
-
For all Atoll documents:

-
Model Standard Deviation (dB): to calculate shadowing losses on the path loss, as related to a user-defined
cell edge coverage probability.
Indoor Loss (dB): to be applied to the path loss and used in coverage predictions, point analysis, and Monte
Carlo simulations.
Indoor penetration losses depend on the clutter types as well as the operating frequency.
You can define an additional indoor loss per frequency band used in the Frequency bands
table in GSM GPRS EDGE, UMTS HSPA, CDMA2000 1xRTT 1xEV-DO, and TD-SCDMA documents. This is an optional feature that must first be activated. For more information,
contact support.
For GSM GPRS EDGE documents:

-
C/I Standard Deviation (DL) (dB): to calculate shadowing losses on the C/I values, as related to a user-defined
Additional Diversity Gain (DL) (dB): to add to the 3 dB gain in case diversity is set at the subcell level.
For UMTS HSPA, and CDMA2000 1xRTT 1xEV-DO documents:

-
Ec/Io Standard Deviation (dB): to calculate shadowing losses on the Ec/Io values, as related to a user-defined
DL Eb/Nt Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt values, as related to a userdefined cell edge coverage probability.
UL Eb/Nt Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt values, as related to a userdefined cell edge coverage probability.
% Pilot Finger: to be used in the Ec/Io calculations. This factor represents the percentage of energy received
by the mobile pilot finger. Mobile user equipment has one searcher finger for pilot. The searcher finger selects
one path and only energy from this path is considered as signal; energy from other multipaths is considered
as interference. For example, if 70% of the total energy is in one path and 30% of the energy is in other multipaths, then the signal energy is reduced to 70% of total energy).
Orthogonality Factor: to be used to evaluate DL Eb/Nt. This parameter indicates the remaining orthogonality
at the receiver; it can be modelled by a value from 0, indicating no remaining orthogonality because of multipath, to 1, indicating perfect orthogonality.
Spatial Multiplexing Gain Factor: to apply to the spatial multiplexing gain read from the Max Spatial Multiplexing Gain graphs in the MIMO tab of reception equipment.
119

Forsk 2011
For TD-SCDMA documents:

-
C/I Standard Deviation (DL) (dB): to calculate shadowing losses on the C/(I+N) values, as related to a user-defined cell edge coverage probability.
SU-MIMO Gain Factor: to apply to the spatial multiplexing gain read from the Max SU-MIMO Gain graphs in
the MIMO tab of reception equipment.
Additional Diversity Gain (DL) (dB): to add to the users downlink C/(I+N), if the user and its reference cell
supports transmit diversity.
Additional Diversity Gain (UL) (dB): to add to the users uplink C/(I+N), if the user and its reference cell
supports receive diversity.
For multi-RAT documents:

-
120
C/I Standard Deviation (DL) (dB): to calculate shadowing losses on the C/(I+N) values, as related to a user-defined cell edge coverage probability.
SU-MIMO Gain Factor: to apply to the spatial multiplexing gain read from the Max SU-MIMO Gain graphs in
the MIMO tab of reception equipment.
Additional STTD/MRC Gain (DL) (dB): to add to the users downlink C/(I+N), if the user and its reference cell
supports STTD/MRC.
Additional STTD/MRC Gain (UL) (dB): to add to the users uplink C/(I+N), if the user and its reference cell
supports STTD/MRC.
For LTE documents:

-
P-CCPCH Eb/Nt or C/I Standard Deviation (dB): to calculate shadowing losses on the P-CCPCH Eb/Nt or C/I
values, as related to a user-defined cell edge coverage probability.
DL Eb/Nt or C/I Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt or C/I values, as related
to a user-defined cell edge coverage probability.
UL Eb/Nt or C/I Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt or C/I values, as related
to a user-defined cell edge coverage probability.
DL Orthogonality Factor: to be used to evaluate DL Eb/Nt or C/I. This parameter indicates the remaining
orthogonality at the receiver; it can be modelled by a value from 0, indicating no remaining orthogonality
because of multi-path, to 1, indicating perfect orthogonality.
UL Orthogonality Factor: to be used to evaluate UL Eb/Nt or C/I. This parameter indicates the remaining
orthogonality at the receiver; it can be modelled by a value from 0, indicating no remaining orthogonality
because of multi-path, to 1, indicating perfect orthogonality.
Spreading Angle (): to be used in determining the cumulative distribution of C/I gains for statistical smart
antenna modelling.
For WiMAX 802.16e documents:

-
Additional Diversity Gain (DL) (dB): to add to the users downlink HS-PDSCH Ec/Nt, if the user and its reference
cell supports transmit diversity.
GSM Model Standard Deviation (dB): to calculate shadowing losses on the path loss (from GSM transmitters
only), in relation to a user-defined cell edge coverage probability.
GSM Indoor Loss (dB): to be applied to the path loss (from GSM transmitters only) and used in coverage
predictions, point analysis, and Monte Carlo simulations.
GSM C/I Standard Deviation (DL) (dB): to calculate shadowing losses on the C/I values (from GSM transmitters
GSM Additional Diversity Gain (DL) (dB): to add to the 3 dB gain if diversity is set at the subcell level (GSM
transmitters only).
UMTS Model Standard Deviation (dB): to calculate shadowing losses on the path loss (from UMTS cells only),
in relation to a user-defined cell edge coverage probability.
UMTS Indoor Loss (dB): to be applied to the path loss (from UMTS cells only) and used in coverage predictions,
point analysis, and Monte Carlo simulations.
UMTS Ec/Io Standard Deviation (dB): to calculate shadowing losses on the Ec/Io values (from UMTS cells
UMTS DL Eb/Nt Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt values (from UMTS cells
UMTS UL Eb/Nt Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt values (from UMTS cells
UMTS % Pilot Finger: to be used in the Ec/Io calculations (from UMTS cells only). This factor represents the
percentage of energy received by the mobile pilot finger. (Mobile user equipment has one searcher finger for
the pilot. The searcher finger selects one path and only energy from this path is considered as signal; energy
from other multipaths is considered as interference. For example, if 70% of the total energy is in one path and
30% of the energy is in other multipaths, then the signal energy is reduced to 70% of total energy).
UMTS Orthogonality Factor: to be used to evaluate DL Eb/Nt (from UMTS cells only). This parameter indicates
the remaining orthogonality at the receiver; it can be modelled by a value from 0, indicating no remaining
orthogonality because of multi-path, to 1, indicating perfect orthogonality.

AT310_UMU_E0
UMTS Spatial Multiplexing Gain Factor: to apply to the spatial multiplexing gain read from the Max Spatial
Multiplexing Gain graphs on the MIMO tab of UMTS reception equipment.
UMTS Additional Diversity Gain (DL) (dB): to add to the users downlink HS-PDSCH Ec/Nt, if the users mobile
and his reference UMTS cell support transmit diversity.
LTE Model Standard Deviation (dB): to calculate shadowing losses on the path loss (from LTE cells only), in
relation to a user-defined cell edge coverage probability.
LTE Indoor Loss (dB): to be applied to the path loss (from LTE cells only) and used in coverage predictions,
point analysis, and Monte Carlo simulations.
LTE C/I Standard Deviation (DL) (dB): to calculate shadowing losses on the C/(I+N) values (from LTE cells only),
in relation to a user-defined cell edge coverage probability.
LTE SU-MIMO Gain Factor: to apply to the spatial multiplexing gain read from the Max SU-MIMO Gain graphs
in the MIMO tab of LTE reception equipment.
LTE Additional Diversity Gain (DL) (dB): to add to the users downlink C/(I+N), if the users mobile and his
reference LTE cell support transmit diversity.
LTE Additional Diversity Gain (UL) (dB): to add to the users uplink C/(I+N), if the users mobile and his reference LTE cell support receive diversity.
8. If you want to use default values for all clutter classes, select the Use only default values check box at the bottom of
the Description tab.
9. Click the Display tab to define the display properties for clutter classes. In addition to the Display tab options described
in "Display Properties of Objects" on page 23, each clutter class display type has a visibility check box. By selecting or
clearing the visibility check box, you can display or hide clutter class display types individually.
Selecting white as the colour for a clutter class value or value interval will cause that clutter
class value or value interval to be displayed as transparent.
10. Click OK.

You can copy the description table into a new Atoll document after importing the clutter
classes file. To copy the description table, select the entire table by clicking the cell in the
upper-left corner of the table and press CTRL+C. On the Description tab of the clutter
classes Properties dialogue in the new Atoll document, press CTRL+V to paste the values
in the table.
3.5.3 Adding a Clutter Class

You can add a new clutter class to your document.
To add a new clutter class to the your document:
4. Select the Description tab from the Properties dialogue.
5. In the blank row marked with
column.
at the bottom of the table, enter an unused number from 1 to 255 in the Code
6. Fill in the remainder of the fields as described in step 5. and step 7. of "Defining Clutter Class Properties" on page 119.
7. Click OK.
You can now use the new clutter class when modifying the clutter class map. For information on modifying the clutter class
map, see "Creating a Clutter Polygon" on page 134.
3.5.4 Refreshing the List of Clutter Classes

Under certain circumstances, it can happen that the list of clutter classes on the Description tab of the clutter classes Properties dialogue contains unused clutter classes. For example, if you have imported two clutter class files and then deleted one
of them, the list of clutter classes will still contain the clutter classes of the deleted file, even if they are not used in the remaining file. Whenever you want to ensure that the list of clutter classes is accurate and current, you can refresh the list.
121

Forsk 2011
To refresh the list of the clutter classes:

4. Select the Description tab from the Properties dialogue.
5. Click Refresh. Atoll removes the unused clutter classes from the list.
6. Click OK.
3.5.5 Displaying Total Surface Area per Clutter Class

You can display the total surface area covered by each clutter class in the document. Atoll displays the surface area covered
by each clutter class in the focus zone if there is one, in the computation zone if there is no focus zone and, if there is no focus
or computation zone, Atoll displays the total surface area covered by each clutter class in the entire document. This information is also available in prediction reports.
To display the surface area covered by each clutter class:
3. Select Statistics from the context menu.
The Statistics dialogue appears, displaying the surface area (Si in km) of each clutter class (i) and its percentage (% of
i) in the computation zone or focus zone, if one exists.
Si
% of I = -------------- 100
Sk
3.6 Clutter Heights

Clutter height maps describe the altitude of clutter over the DTM. Clutter height files allow for a higher degree of accuracy
because they allow more than one height per clutter class. In a clutter height file, a height is given for each point on the map.
If you define clutter height as a property of clutter classes, the height is given as an average per clutter class.
When a clutter height file is available, Atoll uses its clutter height information for calculations using certain propagation
models (the Standard Propagation Model and WLL model), for display (in tool tips and in the status line), and for CW measurements and test mobile data paths. If no clutter height file exists, Atoll uses the average clutter height per clutter class as
defined in the clutter classes properties (see "Defining Clutter Class Properties" on page 119).
To manage the properties of clutter heights:
2. Right-click the Clutter Heights folder.
4. Click the Display tab to define the display properties for clutter heights.
-
For information on Display tab settings, see "Display Properties of Objects" on page 23.
5. Click OK to close the Properties dialogue.

The clutter height of the current pointer position as given in the clutter height file or in the clutter classes is displayed in the
status bar.
3.7 Contours, Lines, and Points

In Atoll, you can import or create vector objects such as contours, lines, and points. The imported or created vectors are used
primarily for display purposes, but polygons can be used as filters, or computation or focus zones. Vector files can also be used
for traffic maps or for population maps. They can also be used as part of an custom geo data map (see "Custom Geo Data
Maps" on page 126).
In an Atoll document, vector objects such as contours, lines, and points are arranged in vector layers. When you import a
vector file, with, for example, roads, Atoll adds the file as a new vector layer containing all the vector objects in the file. The
vector object data can be managed in the vector layer table. For information on working with data tables, see "Working with
Data Tables" on page 47.
122

AT310_UMU_E0
"Managing the Display of a Vector Layer" on page 123

"Managing the Properties of the Vector Layer" on page 123
"Moving a Vector Layer to the Network Tab" on page 124.
3.7.1 Managing the Display of a Vector Layer

Imported geographic vector files can have different attributes depending on their file formats. Atoll can use additional information related to vectors as display parameters. In addition, Atoll can read three-dimensional vector data.
To manage the display of a vector layer:
1. Click the Network or Geo tab in the Explorer window on which the vector layer is located.
2. Right-click the vector layer. The context menu appears.
4. Select the Display tab of the Properties dialogue. For information on using the display tab, see "Display Properties of
You can manage the display of an individual vector object by right-clicking the vector
object in the vector layer folder and selecting Properties from the context menu.
3.7.2 Managing the Properties of the Vector Layer

The properties of the objects on the vector layer can be managed in two ways: either from a table containing all vectors and
their attributes or from the Properties dialogue.
Vector Layer Table
All the vector objects of a vector layer and their attributes are listed in the vector table.
To open the vector layer table:
2. Select Open Table from the context menu. The vector table appears.
You can edit the contents of this table using the commands from the context menu or from the Edit, Format, and Records
menus. For more information on editing tables in Atoll, see "Working with Data Tables" on page 47.
Vector Layer Properties Dialogue
The vector layer Properties dialogue has three tabs: a General tab, a Table tab, and a Display tab.
To open the Properties dialogue of a vector layer:
3. Click the General tab. The following options are available:
-
Name: The name of the vector layer. You can rename the vector layer using this field.
Source File: The complete path of the vector layer file if the file is linked to the Atoll document; otherwise the file
is described as embedded.
-
Find: Click the Find button to redefine the path when the files location has changed.
Embed: Click the Embed button to embed a linked vector layer file in the Atoll document.
Coordinate System: When a vector layer is linked, the coordinate system used is the files, as specified when the
file was imported. When the a vector layer is embedded, the coordinate system used is documents, as specified
when the file was embedded.
-
Change: Click the Change button to change the coordinate system of the vector layer.
Sort: Click the Sort button to sort the data contained in the vector layer. For information on sorting, see "Advanced
Sorting" on page 70.
Filter: Click the Filter button to filter the data contained in the vector layer. For information on filtering, see
"Advanced Data Filtering" on page 72.
4. Click the Table tab. You can use the Table tab to manage the vector layer table content. For information on the Table
tab, see "Adding, Deleting, and Editing Data Table Fields" on page 47.
123

Forsk 2011
5. Click the Display tab. You can use the Display tab to manage the vector layer display. For information on the Table tab,
see "Display Properties of Objects" on page 23.
3.7.3 Moving a Vector Layer to the Network Tab

In Atoll, all objects on the Network tab, such as transmitters, antennas, and predictions, are displayed over all objects on the
Geo tab. You may wish, however, to ensure that certain geo data, for example, major geographical features, roads, etc.,
remain visible in the map window. You can do this by transferring the geo data from the Geo tab to the Network tab and placing it above data such as predictions.
To transfer a vector layer to the Network tab of the Explorer window:
2. Right-click the vector layer you want to transfer. The context menu appears.
3. Select Move to Network Tab from the context menu. The vector layer is transferred to the Network tab.
You can transfer the vector layer back to the Geo tab by right-clicking it in the Network tab and selecting Move to Geo Tab
from the context menu. For more information about display priority in Atoll, see "Setting the Priority of Geo Data" on
page 129.
3.8 Scanned Images

Scanned images are geographic data files which represent the actual physical surroundings, for example, road maps or satellite images. They are used to provide a precise background for other objects or for less precise maps.They have no effect on
calculations.
"Importing Several Scanned Images" on page 124

"Defining the Display Properties of Scanned Images" on page 124.
3.8.1 Importing Several Scanned Images

You can import scanned images into the current Atoll document one at a time, as explained in "Importing Geo Data Files" on
page 111, or you can import a group of images by importing an index file listing the individual image files. The index file is a
text file with the information for each image file on a separate line.
Each line contains the following information, with the information separated by a space:
File name: The name of the file, with its path relative to the current location of the index file.
XMIN: The beginning X coordinate of the file.
XMAX: The end X coordinate, calculated as XMIN + (number of horizontal bins x bin width).
YMIN: The beginning Y coordinate of the file.
YMAX: The end Y coordinate, calculated as YMIN + (number of horizontal bins x bin width).
0: The zero character ends the sequence.
nice1.tif 984660 995380 1860900 1872280 0

nice2.tif 996240 1004900 1860980 1870700 0
File name
XMIN
XMAX
YMIN
YMAX
To import an index
1. Select File > Import.
2. Select the index file and click Open. The File Import dialogue appears (see Figure 3.1).
3. Select Image or Scan from the Data Type list.
4. Click Import. The image files imported and listed in the Geo tab of the Explorer window.
3.8.2 Defining the Display Properties of Scanned Images

Because imported images cannot be modified, they have fewer display parameters than other object types.
To define the display properties of a scanned image:
1. Click the Geo tab in the Explorer window
2. Right-click the scanned image. The context menu appears.
124

AT310_UMU_E0
3. Select Properties from the context menu. The Properties dialogue appears (see Figure 3.8).
4. Select the Display tab and set the following options:
-
Colour: Select either Automatic, Shades of gray, or Watermark from the list.
Transparent Colour: Select White from the list if you wish parts of the scanned image that are coloured white to
be transparent, allowing objects in lower layers to be visible.
Lightness: Move the slider to lighten or darken the scanned image.
Contrast: Move the slider to adjust the contrast.
Visibility Scale: Enter a visibility scale minimum in the between 1: text box and maximum in the and 1: text box.
When the displayed or printed scale is outside this range, the scanned image is not displayed.
5. Click OK.
Figure 3.8: Scanned image Properties dialogue
3.9 Population Maps

Population maps contain information on population density or on the total number of inhabitants.
Population maps can be used in prediction reports in order to display, for example, the absolute and relative numbers of the
population covered.
"Managing the Display of Population Data" on page 125

"Displaying Population Statistics" on page 125.
3.9.1 Managing the Display of Population Data

You can manage the display of population data.
To manage the display of population data:
2. Right-click the Population folder. The context menu appears.
4. Select the Display tab of the Properties dialogue. For information on using the display tab, see "Display Properties of
Vector points added to a vector population map are not displayed if the map is displayed
by population density.
3.9.2 Displaying Population Statistics

You can display the relative and absolute distribution of population, according to the defined value intervals in the display
properties (for information on defining value intervals, see "Defining the Display Type" on page 24), as well as the total popu-
125

Forsk 2011
lation. Atoll displays the statistics for the focus zone if there is one, for the computation zone if there is no focus zone and, if
there is no focus or computation zone, Atoll displays the statistics for the entire document.
To display the population distribution statistics:
2. Right-click the Population folder.
3. Select Statistics from the context menu. The Statistics window appears with the distributions of each value interval
defined in the display properties.
Statistics are displayed only for visible data. See "Displaying or Hiding Objects on the Map
Using the Explorer" on page 18.
3.10 Custom Geo Data Maps

You can import maps other than the default maps that Atoll uses. For example, you can import files for the revenue, rainfall,
or socio-demographic data. Depending on the type of information displayed, you could use it in prediction reports. For example, you could display the predicted revenue for defined coverage.
These maps can be raster files of 8, 16, or 32 bits per pixel or vector-format files that you have either imported or created
using the Vector Editor toolbar "Editing Polygons, Lines, and Points" on page 39.
You create an custom data map by:
1. Importing an custom geo data file and creating the custom data map folder.
2. Importing other custom geo data files into the newly created custom data map folder, if more than one file will be
used for this custom geo data map.
"Creating a Custom Geo Data Map" on page 126

"Adding a File to a Custom Geo Data Map" on page 127
"Managing the Properties of a Custom Geo Data Map" on page 128
"Displaying Statistics on Custom Geo Data" on page 128
"Integrable Versus Non Integrable Data" on page 129.
3.10.1 Creating a Custom Geo Data Map

The first step in creating a custom geo data map is importing the first file and creating the custom data map folder.
To create an custom geo data map:
2. Select the first geo data file that will be a part of the custom data map and click Open.
-
If the selected file is a raster file, the File Import dialogue appears (see Figure 3.1).
If the selected file is a vector file, the Vector Import dialogue appears (see Figure 3.4).
3. Click the Advanced button. The New Type dialogue appears (see Figure 3.4).
4. Enter a Name for the custom geo data map. Atoll creates a folder with this name on the Geo tab and all other files of
the new custom geo data map will go in here.
5. Under Supported Input Formats, select the check boxes corresponding to the formats of both the present file and all
other files that will constitute the new custom geo data map:
-
8-bit Raster
16-bit Raster
32-bit Raster
Vector.
If you do not select all the formats you need now, you will not be able to add a format
later.
6. Under Supported Input Formats, select the check box corresponding to the type of value of the present file and all
other files that will constitute the new custom geo data map:
126

AT310_UMU_E0
Classes (8 bits): to create a map of value classes (such as clutter classes) with classes from 0 to 255.
Short Integer (16 bits): to create a map with whole values.
Long Integer (32 bits): to create a map with whole values.
Float (32 bits): to create a map with decimal values.
Double (64 bits): to create a map with decimal values.
7. Select the Integrable check box if you want to be able to use imported data as a surface density value and show cumulative custom geo data in prediction reports.
To use imported data as a surface density value, you must select the Integrable
check box.
You can not change the integrable setting once you have created your custom geo
data map.
8. Click OK.
9. If the imported file is a raster file, the File Import dialogue appears (see Figure 3.1 on page 112); if the imported file
is a vector file, the Vector Import dialogue appears (see Figure 3.4 on page 114):
-
File Import dialogue: From the Use as list, select whether the new data is to be used a Density or as a Value.
Vector Import dialogue: Under Fields to be imported, select from the first list which field is to be imported and
from the second list whether the imported field is a Density or a Value (see Figure 3.2 on page 113 and Figure 3.3
on page 113).
If the file you first import when you create your custom geo data map is an 8-bit raster
map, the Use as and Fields to be imported boxes will not be available for any file that is
imported into your new custom geo data map. The values in 8-bit maps are codes and
not values such as densities.
10. .Click Import. A new folder is created on the Geo tab of the Explorer window containing the geo data file you
imported.
Figure 3.9: The New Type dialogue
3.10.2 Adding a File to a Custom Geo Data Map

Once you have created the custom geo data map by importing the first file, you can add more files that will be part of the
custom map.
To add a file to an custom geo data map:
2. Select the geo data file that you want to add to the custom data map and click Open.
-
If the selected file is a raster file, the File Import dialogue appears (see Figure 3.1).
i.
From the File Type list, select the name of the custom geo data map.
ii. From the Use as list, select whether the new data is to be used a Density or as a Value.
127

Forsk 2011
If the selected file is a vector file, the Vector Import dialogue appears (see Figure 3.4).
i.
From the Import To list, select the name of the custom geo data map.
ii. Under Fields to be imported, select from the first list which field is to be imported and from the second list
whether the imported field is a Density or a Value (see Figure 3.2 on page 113 and Figure 3.3 on page 113).
If the file you first imported when you created your custom geo data map was an
8-bit raster map, the Use as and Fields to be imported boxes will not be available
for any file that is imported into your new custom geo data map.
To use imported data as a surface density value, you must select the Integrable
check box.
3. Click Import. The file is added to the custom geo data file on the Geo tab of the Explorer window containing the geo
data file you imported.
3.10.3 Managing the Properties of a Custom Geo Data Map

To manage the properties of an custom geo data map:
1. Right-click the custom geo data map on the Geo tab of the Explorer window.
2. Select Properties from the context menu:
3. Depending on the imported file types, the following tabs are available:
-
Description: The Description table lists the classes of all 8-bit raster files contained in the custom geo data map.
You must enter a different value for each class.
Table: The Table tab enables you to manage the contents of the class table presented on the Description tab. For
information on working with the Table tab, see "Adding, Deleting, and Editing Data Table Fields" on page 47.
Data Mapping: The Data Mapping tab enables you to select which value from each imported vector file is part of
the custom geo data map. The imported vector files are listed in the Name column, with the relevant data selected
in the Field column. You can change this value by selecting another value from the Field list. If the custom geo data
map is marked as integrable (see "Integrable Versus Non Integrable Data" on page 129), there is also a Density
check box. If the value in the Field column is to be considered as a density, select the Density check box.
Display: The Display tab enables you to define how the custom geo data map appears in the map window. Discrete
value and value interval are the available display types.
In the Field list, display by value is not permitted if the custom geo data map has:
-
different raster maps with different resolutions

both line and polygon vectors
both raster and vector maps.
In the Field list, display by density is not permitted if the custom geo data map consists of vector points or lines.
For information on using the display tab, see "Display Properties of Objects" on page 23.
3.10.4 Displaying Statistics on Custom Geo Data

You can display the relative and absolute distribution of each value interval (for information on defining value intervals, see
"Defining the Display Type" on page 24) of an custom geo data map. Atoll displays the statistics for the focus zone if there is
one, for the computation zone if there is no focus zone and, if there is no focus or computation zone, Atoll displays the statistics for the entire document.
To display the statistics of an custom geo data map:
2. Right-click the custom geo data map.
3. Select Statistics from the context menu. The Statistics window appears with the distributions of each value interval.
Statistics are displayed only for visible data. See "Displaying or Hiding Objects on the Map
128

AT310_UMU_E0
3.10.5 Integrable Versus Non Integrable Data

Integrable data can be summed over the coverage area defined by the item in a prediction report (for example, by transmitter
or threshold). The data can be value data (revenue, number of customers, etc.) or density data (revenue/km, number of
customer/km, etc.). For example, if the integrable data comes from a revenue map, a prediction report would indicate:
The percentage of coverage for each revenue class for the entire focus zone, and for each single coverage area (transmitter, threshold, etc.),
The revenue of the focus zone and of each single coverage area,
The percentage of the revenue map covered for the entire focus zone and for each single coverage area.
Data is considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example,
socio-demographic classes, etc.
In the example of a socio-demographic classes map, a prediction report would indicate:
The coverage of each socio-demographic class for the entire focus zone and for each single coverage area (transmitter,
threshold, etc.)
3.11 Setting the Priority of Geo Data

Atoll lists the imported DTM, clutter class or traffic objects in their respective folders and creates a separate folder for each
imported vector data file and scanned image. Each object is placed on a separate layer. Thus, there are as many layers as
imported objects. The layers are arranged from top to bottom in the map window as they appear on the Geo tab of the
Explorer window.
It is important to remember that all objects on the Network tab, such as transmitters, antennas, and predictions, are displayed
over all objects on the Geo tab.
3.11.1 Setting the Display Priority of Geo Data

There are several factors that influence the visibility of geo data:
The display check box: The check box immediately to the left of the object name in the Geo tab controls whether or
not the object is displayed on the map. If the check box is selected ( ), the object is displayed; if the check box is
cleared ( ), the object is not displayed. If the check box, is selected but shaded ( ), not all objects in the folder are
displayed. For more information, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 18.
The order of the layers: The layer at the top of the Geo tab is on top of all other layers in the map window. Data on
layers below is only visible where there is no data on the top layer or if you adjust the transparency of the objects on
the top layer. You can use drag and drop to change the order of layers by dragging a layer on the Geo tab of the
Explorer window towards the top or the bottom of the tab.
All objects on the Network tab, such as transmitters, antennas, and predictions, are
displayed over all objects on the Geo tab. Vector geo data, however, can be transferred to
the Network tab, where they can be placed over data such as predictions. In this way, you
can ensure that certain vector geo data, for example, major geographical features, roads,
etc., remain visible in the map window For more information, see "Moving a Vector Layer
to the Network Tab" on page 124.
The transparency of objects: You can change the transparency of some objects, such as predictions, and some object
types, such as clutter classes, to allow objects on lower layers to be visible on the map. For more information, see
"Defining the Transparency of Objects and Object Types" on page 25.
The visibility range of objects: You can define a visibility range for object types. An object is visible only in the map
window if the scale, as displayed on the zoom toolbar, is within this range. For more information, see "Defining the
Visibility Scale" on page 25.
In Figure 3.10, vector data (including the linear vectors HIGHWAYS, COASTLINE, RIVERLAKE, MAJORROADS, MAJORSTREETS,
RAILWAYS and AIRPORT), clutter classes, DTM and scanned image have been imported and a UMTS environment traffic map
has been edited inside the computation zone. In the map window, the linear objects (ROADS, RIVERLAKE, etc.) are visible both
inside and outside the computation zone. The clutter class layer is visible in the area where there is no traffic data (outside
the computation zone). On the other hand, the DTM layer which is beneath the clutter class layer and the scanned map which
is beneath the DTM layer, are not visible.
129

Forsk 2011
Figure 3.10: Displaying Geo data layers
3.11.2 Setting the Priority of Geo Data in Calculations

The priority of geo data in calculations is determined in much the same way as it is for display.
When you make calculations in Atoll, the data taken into account in each folder (Clutter Classes, DTM, etc.) is the data from
the top down. In other words, Atoll takes the object on top and objects below only where there is no data in higher levels;
what is used is what is seen.
The visibility in the context of calculations must not be confused with the display check box
( ). Even if the display check box of an object is cleared ( ), so that the object is not
displayed on the map, it will still be taken into consideration for calculations. The only
cases where clearing the display check box means that the data will not be used are for
population data in reports, and for custom geo data maps.
Object folders, for example, the DTM, clutter classes, clutter heights, and traffic density folders, can contain more than one
data object. These objects can represent different areas of the map or the same parts of the map with the same or different
resolutions. Therefore for each folder, you should place the objects with the best data at the top. These are normally the
objects which cover the least area but have the highest resolution. For example, when calculating coverage in an urban area,
you might have two clutter class files: one with a higher resolution for the downtown core, where the density of users is
higher, and one with a lower resolution but covering the entire area. In this case, by placing the clutter class file for the downtown core over the file with the lower resolution, Atoll can base its calculations for the downtown core on the clutter class
file with the higher resolution, using the second file for all other calculations.
Population maps and custom geo data maps, both of which can be used in prediction reports follow the same rules of calculation priority.
The following sections give several examples to better illustrate how data are used in Atoll:
"Example 1: Two DTM Maps Representing Different Areas" on page 130

"Example 2: Clutter Classes and DTM Maps Representing the Same Area" on page 131
"Example 3: Two Clutter Class Maps Representing a Common Area" on page 131.
3.11.2.1 Example 1: Two DTM Maps Representing Different Areas

In this example, there are two imported DTM files:
"DTM 1 represents a given area and has a resolution of 50 m.

DTM 2 represents a different area and has a resolution of 20 m.
In this example, the file order of the DTM files in the Explorer window does not matter because they do not overlap; in both
Case 1 and Case 2, Atoll will take all the data from both "DTM 1 and "DTM 2 into account.
130

AT310_UMU_E0
Explorer window
Work space
Case 1
DTM
DTM 2 (20m)
DTM 1 (50m)
Case 2
DTM
DTM 1 (50m)
DTM 2 (20m)
Figure 3.11: Multi-layer management in calculations two DTM maps representing different areas
3.11.2.2 Example 2: Clutter Classes and DTM Maps Representing the Same Area
In this example, there are two imported maps:
A clutter class map called Clutter.

A DTM map called DTM.
Independently of the order of the two maps in the Explorer window, Atoll uses both the clutter and DTM data in calculations.
In Case 1, the clutter class map is on top of the DTM map. In Case 2, the DTM map is on top of the clutter class map. In both
Case 1 and Case 2, Atoll will use both the clutter and DTM data in calculations.
Explorer window
Work space
Case 1
Clutter classes
Clutter
DTM
DTM
Case 2
DTM
DTM
Clutter classes
Clutter
Figure 3.12: Multi-layer management in calculations Clutter and DTM maps representing the same area
3.11.2.3 Example 3: Two Clutter Class Maps Representing a Common Area

In this example, there are two imported clutter classes maps:
"Clutter 1" represents a large area with a resolution of 50 m.

"Clutter 2" represents a smaller area with a resolution of 20 m. This area is also covered by "Clutter 1"
In the case of two clutter class maps, Atoll uses the order of the maps in the Clutter Classes folder on the Geo tab of the
Explorer window to decide which data to use. In Case 1, "Clutter 2" is on top of "Clutter 1". Atoll will therefore use the data
in "Clutter 2" where it is available, and the data from "Clutter 1" everywhere that is covered by "Clutter 1" but not by
"Clutter 2." In Case 2, "Clutter 1" is on top and completely covers "Clutter 2." Therefore, Atoll will only use the data from
"Clutter 1."
131

Forsk 2011
Explorer window
Work space
Case 1
Clutter classes
Clutter 2 (20m)
Clutter 1 (50m)
Case 2
Clutter classes
Clutter 2 (50m)
Clutter 1 (20m)
Figure 3.13: Multi-layer management in calculations two clutter maps representing the same area
3.12 Displaying Information About Geo Data

You can display information about a geo data map by using tooltips. For information on how to display information in tooltips,
see "Defining the Object Type Tip Text" on page 26.
To display information about the geo data in a tool tip:
Hold the pointer over the geo data until the tool tip appears. The surface area is only given for closed polygons.
Tool tips only appear when the Display Tips button (
) on the toolbar has been selected.
3.13 Geographic Data Sets

In Atoll, once you have imported geographic data and defined their parameters, you can save much of this information in a
user configuration file. Then, another user, working on a similar Atoll document, can import the user configuration file
containing the paths to the imported geographic data and many of the defined parameters.
When you save the geographic data set in a user configuration, you save:
the paths of imported geographic maps

map display settings (visibility scale, transparency, tips text, etc.)
clutter description (code, name, height, standard deviations, etc.)
raster or user profile traffic map description.
"Exporting a Geo Data Set" on page 133

"Loading a Geo Data Set" on page 133.
You can save and load other types of information with user configuration files as well. For
information, see the Administrator Manual.
132

AT310_UMU_E0
3.13.1 Exporting a Geo Data Set

When you save a geo data set in a user configuration file, the information listed in "Geographic Data Sets" on page 132 is saved
into a file.
Vectors must be in the same coordinate system as the raster maps.
To save a geo data set in a user configuration file:

1. Select Tools > User Configuration > Save. The User Configuration dialogue appears (see Figure 3.14).
2. In the User Configuration dialogue, select the Geographic Data Set check box.
Figure 3.14: The User Configuration dialogue

3. Click OK, The Save As dialogue appears.
4. In the Save As dialogue, browse to the folder where you want to save the file and enter a File name.
5. Click OK.
3.13.2 Loading a Geo Data Set

When you load a user configuration file containing a geo data set, the information listed in "Geographic Data Sets" on
page 132 is loaded into your current Atoll document.
To load a user configuration file containing a geo data set into your current Atoll document:
2. Browse to the user configuration file, select it and click Open.
3. The User Configuration dialogue appears.
When you load a user configuration file including a geographic data set, Atoll checks if there are already geographic
data in the current Atoll document. If so, the option Delete existing geo data appears with other options in the User
Configuration dialogue.
4. In the User Configuration dialogue, select the check boxes of the items you want to load into your current Atoll document.
5. If you already have geographic data in your current Atoll document and would like to replace it with any data in the
user configuration file you are loading, select the Delete existing geo data check box.
If you do not want to replace existing geo data with imported data, clear the Delete existing geo data check box.
6. Click OK.
You can automatically start Atoll with a user configuration file by naming the file "atoll.cfg"
and placing it in the same folder as the Atoll executable. You can also edit the Windows
shortcut to Atoll and add "-cfg <.cfg_file>" where "<.cfg_file>" is the full path to the user
configuration file.
133

Forsk 2011
3.14 Editing Geographic Data

In Atoll, you can edit geo data that you have imported or you can create geo data by, for example, adding a vector layer to
the Population folder and then adding polygons.
The following types of geographic data can be edited:
Clutter classes (for more information, "Editing Clutter Class Maps" on page 134)
Contours, lines, and points (for more information, "Editing Polygons, Lines, and Points" on page 39)
Population maps (if they are in vector format, i.e., Erdas Imagine (16-bit), AGD, DXF, SHP, MIF, or TAB format) (for
more information, "Editing Population or Custom Data Maps" on page 135)
Geoclimatic maps (for more information, "Editing Population or Custom Data Maps" on page 135)
Traffic data maps
Custom data maps (for more information, "Editing Population or Custom Data Maps" on page 135).
3.14.1 Editing Clutter Class Maps

Clutter class maps and certain traffic maps are raster maps. You can edit these maps by creating or modifying polygons.
"Creating a Clutter Polygon" on page 134

"Editing Clutter Polygons" on page 134
"Displaying the Coordinates of Clutter Polygons" on page 135.
"Deleting Clutter Polygons" on page 135
3.14.1.1 Creating a Clutter Polygon

In Atoll, you can modify imported clutter class maps or create your own maps by adding data in the form of polygons. You can
later edit and export the polygons you have created. All modifications you make to clutter class maps are taken into account
by propagation model calculations.
To create a polygon:
2. Right-click the Clutter Classes folder. The context menu appears.
3. Select Edit from the context menu. The Editor toolbar appears with a clutter or traffic list, a polygon drawing tool
a polygon deletion tool
, and a Close button (see Figure 3.15).
Figure 3.15: Editor toolbar

4. From the list, select the clutter class for the polygon you want to create.
Clutter classes are defined on the Descriptions tab of the clutter classes Properties
dialogue.
5. Click the polygon drawing button (
). The pointer changes to a pencil (
).
6. Click once on the map where you want to begin drawing the polygon.
7. Click each time you change angles on the border defining the outside of the polygon.
8. Double-click to close the polygon.
You can copy the exact coordinates of a closed polygon by right-clicking it on the map and
selecting Properties from the context menu.
3.14.1.2 Editing Clutter Polygons

You can edit clutter polygons by moving existing points of the polygon or by adding or deleting points.
134

AT310_UMU_E0
To edit clutter polygons:

3. Select Edit from the context menu. The Editor toolbar appears (see Figure 3.15).
4. Select the polygon. You can now edit the clutter polygon by:
-
Moving a point:
i.
).

-
Adding a point:
i.
Position the pointer over the polygon border where you want to add a point. The pointer changes (
).
ii. Right-click and select Insert Point from the context menu. A point is added to the border at the position of the
pointer.
-
Deleting a point:
i.
).
3.14.1.3 Displaying the Coordinates of Clutter Polygons

To display the coordinates of the points defining the polygon area:
4. Right-click the polygon and select Properties from the context menu. The Properties dialogue appears with the coordinates of the points defining the polygon and the total area.
You can select and copy the coordinates displayed in the Properties dialogue of the
polygon.
3.14.1.4 Deleting Clutter Polygons

You can delete clutter polygons.
To delete a clutter polygon:
4. Click the polygon deletion tool (
). The pointer changes (
).
5. Click the polygon you want to delete. The polygon is deleted.
3.14.2 Editing Population or Custom Data Maps

Some geographic data maps, for example, population maps, and custom data, are made up of individual vector objects. You
can modify and create these geo data maps by adding a vector layer and then adding vector objects (contours, lines, and
points) to this layer.
To create a vector layer and vector objects on a geo data map:
2. Right-click the geo data object, the Population, or the Custom Data folder, to which you want to add a vector layer.
3. Select Add Vector Layer from the context menu. A new data object called "Vectors" is created in the selected geo data
object folder.
135

Forsk 2011
4. Right-click the new vector layer. The context menu appears.

Vector Editor toolbar list. Because Atoll names all new vector layers "Vectors" by
default, it might be difficult to know which Vectors folder you are selecting. By renaming
each vectors folder, you can ensure that you select the correct folder. For information on
renaming objects, see "Renaming an Object" on page 19.
6. To draw a polygon, click the New Polygon button (
) on the Vector Editor toolbar:
a. Click once on the map where you want to begin drawing the contour.
b. Click each time you change angles on the border defining the outside of the contour.
c. Double-click to close the contour.
7. To draw a rectangle, click the New Rectangle button (
) on the Vector Editor toolbar:
a. Click the point on the map that will be one corner of the rectangle.
b. Drag to the opposite corner of the rectangle.
c. Release the mouse to create the rectangle defined by the two corners.
8. Right-click the new polygon or rectangle and select Properties from the context menu.
9. Enter a value:
-
Population: Enter a value in the Population field to indicate the number of inhabitants or the population density.
Custom Data Map: The value you enter will depend on the type of custom data map you created.
10. Press ESC to deselect the New Polygon (
) or the New Rectangle (
) button on the Vector Editor toolbar.
11. For Atoll to consider the new vector layer as part of the data map, you must map the vector layer. Right-click the the
Population, or the Custom Data folder. The context menu appears.
13. Click the Data Mapping tab. For the following geo data:
-
Population Map:
i.
In the Field column, "Population" is selected by default.
ii. If the vector layer contains a population density, select the check box in the Density column. If the vector layer
indicates the number of inhabitants, and not the population density, clear the check box in the Density column.
-
Custom Data Map: The data you map will depend on the type of custom data map you created.
You can edit the vector objects as explained in "Editing Polygons, Lines, and Points" on page 39.
3.15 Saving Geographic Data

Atoll allows you to save your geographic data files separately from saving the Atoll document. Atoll supports a variety of both
raster and vector file formats (for more information, see "Supported Geographic Data Formats" on page 111). Saving a
geographic file separately from saving the Atoll document enables you to:
Save modifications you have made to an external file: If you have made modifications to geo data, you can export
them to a new external file.
Update the source file with modifications you have made: If you have made modifications to a geo data type in Atoll,
you can save these changes to the source file.
Combine several raster files into one file: If you have several small raster files in one folder of the Geo tab, you can
save them as one file.
Export an embedded file to be used in another Atoll document or in another application: You can save a file to an
external file, in the same format or in another one.
Create a new file from part of a larger one: You can select part of certain geo data types and then save the selected
part as a new file.
136
"Saving Modifications to an External File" on page 137

"Updating the Source File" on page 138

AT310_UMU_E0
"Combining Several Raster Files into One File" on page 138

"Exporting an Embedded File" on page 139
"Creating a New File from a Larger File" on page 140
3.15.1 Saving Modifications to an External File

In Atoll, you can save your modifications to an external file.
"Exporting an Edited Clutter Class Map in a Raster-Format File" on page 137

"Exporting an Edited Vector Layer in Vector-Format File" on page 138.
3.15.1.1 Exporting an Edited Clutter Class Map in a Raster-Format File

You can export clutter class modifications in a raster-format file, either in the same format as used in the current Atoll document, or in a different raster format. You can also choose to export the entire clutter class geo data, the part containing the
computation zone, or just your modifications to the geo data.
When you have made modifications to a raster-format geo data file, exporting either the entire geo data or just your modifications allows you to save those modifications to an external file.
To export clutter class modifications in a raster-format file:
3. Select Save As from the context menu. The Save As dialogue appears.
4. In the Save As dialogue, browse to the folder where you want to save the file, enter a name for the file, and select the
file format from the Save as type list. You can select from one of the following file formats:
-
BMP: When you select bitmap format, Atoll automatically creates the corresponding BPW file containing the
georeference information.
TXT: The ArcView text format is intended only for export; no corresponding geo-reference file is created.
TIF: When you select tagged image file format, Atoll automatically creates the corresponding TFW file containing
the georeference information.
BIL: When you select the BIL format, Atoll automatically creates the corresponding HDR file containing the georeference information. When exporting in BIL format, Atoll allows you to export files larger than 2 Gb.
JPEG 2000: When you select the JPEG 2000 format, no corresponding geo-reference file is created.
GRC or GRD: Files with the extension GRC or GRD are Vertical Mapper files. When exporting in GRD or GRC formats, Atoll allows you to export files larger than 2 Gb.
5. Click Save. The Export dialogue appears (see Figure 3.16).
Figure 3.16: Export dialogue

6. Under Region, select one of the following:
-
The Entire Project Area: This option allows you to export the entire clutter class geo data file, including any modifications you have made to the geo data. The exported geo data file will replace the geo data file in the current
Atoll document.
Only Pending Changes: This option allows you to export a rectangle containing any modifications you have made
to the clutter classes. The exported geo data file will be added as a new object to the Clutter Classes geo data
folder.
137

Forsk 2011
The Computation Zone: This option allows you to export the clutter class geo data contained by a rectangle
encompassing the computation zone, whether or not the computation zone is visible. The exported geo data file
will be added as a new object to the selected geo data folder.
7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1. The suggested resolution value is defined by the following criteria:
-
If one object has been modified, the suggested resolution is the resolution of the modified object.
If several objects have been modified, the suggested resolution is the highest resolution of the modified objects.
If there is no initial clutter class object, the resolution will equal the highest resolution of the DTM maps.
If the Atoll document in which you created the clutter class file has no DTM, no other clutter class geo data file,
or traffic objects, the suggested resolution is 100 m.
8. Click OK. The selected data is saved in an external file.
3.15.1.2 Exporting an Edited Vector Layer in Vector-Format File

You can export an edited vector layer as a vector format file. A vector layer can contain contours, lines, and points. Along with
vector layers you have added to the Geo tab, the following maps can be exported as vector format files:
Vector-format population maps

Vector-format geoclimatic maps
Vector-format custom maps.
Once you save a vector layer, the exported file replaces the vector layer as a linked file. You can embed the file afterwards
(see "Embedding Geographic Data" on page 117).
To export a vector layer:
3. In the Save As dialogue, browse to the folder where you want to save the file, enter a name for the file, and select the
file format from the Save as type list. You can select from one of the following file formats:
-
AGD: The Atoll Geographic Data format is an Atoll-specific format. As a format created for Atoll, Atoll can read
AGD files faster than the other supported vector formats.
SHP: The ArcView vector format should be used for vector layers containing only polygons; it cannot save vectors
made of lines or points. If you have a vector layer with vector lines or points, use either the AGD, the MIF or the
TAB format.
MIF and TAB: MapInfo formats.
4. Click Save in the Save As dialogue. The Vector Export dialogue appears, displaying the current coordinate system and
allowing you to change the coordinate system by clicking Change.
5. Click Export. The vector layer is saved in the format and with the name you specified and the exported file replaces
the vector layer in the current document as a linked file.
3.15.2 Updating the Source File

While working on an Atoll document, you may make changes to geo data. If the geo data file is embedded in the Atoll document, Atoll saves the changes automatically when you save the document. If the geo data file is linked, Atoll prompts you to
save the changes when you close the document.
To update the source file of a linked geo data file:
2. Right-click the folder containing geo data file whose source file you want to update. The context menu appears.
3. Select Save from the context menu. The linked file is updated.
You will not be warned that you are replacing the current file. Therefore, ensure that you
want to replace the current file before proceeding to the following step. If you do not
want to replace the current file, you can save your changes to an external file ("Exporting
an Edited Vector Layer in Vector-Format File" on page 138).
3.15.3 Combining Several Raster Files into One File

In certain circumstances, for example, after importing an MSI Planet index file, you may have several geo data files of the
same type. You can combine these separate files to create one single file. The files will be combined according to their order
138

AT310_UMU_E0
from the top down in the folder on the Geo tab of the Explorer window. If the files overlap on the map, the combined file will
show the file on the top.
You can create a one file from a section of the following geo data types:

Clutter classes
Clutter heights
Scanned maps
To combine individual files into a new file:

2. Right-click the folder of the geo data files you want to combine into one file. The context menu appears.
4. Enter a File name and select a file type from the Save as type list.
5. Click OK. The Export dialogue appears (see Figure 3.17).
6. Under Region, select The Entire Project Area. This option allows you to save the entire area covered by the geo data
files, including any modifications you have made to the geo data.
7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1. The suggested resolution value is the highest resolution of all objects.
8. Click OK. The selected data is saved as a new file.
3.15.4 Exporting an Embedded File

You can export an embedded geo data file to be used in a different Atoll document, or in a different application. When you
export an embedded file, Atoll replaces the embedded file in the current Atoll document with the newly exported file.
To export an embedded geo data file:
2. Right-click the folder of the embedded geo data file you want to export. The context menu appears.
5. Click OK.
If the geo data file is a vector file, the Vector Export dialogue appears (see Figure 3.17).
Figure 3.17: The Vector Export dialogue

a. The Vector Export dialogue displays the coordinate system of the file. To change the coordinate system used for
the exported file, click Change. The Coordinate Systems dialogue appears. For information on the Coordinate Systems dialogue, see "Setting a Coordinate System" on page 95.
b. Click Export. The geo data file is exported with the selected coordinate system.
If the geo data file is a raster file, the Export dialogue appears (see Figure 3.18).
139

Forsk 2011
Figure 3.18: Export dialogue

a. Under Region, select one of the following:
-
The Entire Project Area: This option allows you to export the entire raster-format geo data file, including any
modifications you have made to the geo data. The exported file will replace the embedded file in the Geo tab.
Only Pending Changes: This option allows you to export a rectangle containing any modifications you have
made to the geo data. The exported file will be added as an object in the geo data folder.
The Computation Zone: This option allows you to export the geo data contained by a rectangle encompassing
the computation zone, whether or not the computation zone is visible. The exported file will be added as an
object in the geo data folder.
b. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1.
c. Click OK. The selected data is saved in an external file.
3.15.5 Creating a New File from a Larger File

You can create a new file from a section of a larger file. You can use this new file in the same Atoll document, or in a new Atoll
document. To create a new file, you must first define the area by creating a computation zone.
You can create a new file from a section of the following geo data types:

Clutter classes
Clutter heights
Scanned maps
Population
Geoclimatic maps
To create a new file from a section of a larger file:

2. Right-click the folder of the embedded geo data file you want to export. The context menu appears.
5. Click OK. The Export dialogue appears (see Figure 3.17).
6. Under Region, select The Computation Zone. This option allows you to export the geo data contained by a rectangle
encompassing the computation zone, whether or not the computation zone is visible. The exported geo data file will
be added as a new object to the selected geo data folder.
7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1.
8. Click OK. The selected data is saved as a new file.
140
Chapter 4
Antennas and
Equipment
This chapter provides the information to work with
antennas and equipment in Atoll.
"Working With Antennas" on page 143
"Working With Equipment" on page 147

Chapter 4: Antennas and Equipment
142
Forsk 2011

AT310_UMU_E0
4 Antennas and Equipment

In Atoll, the equipment used to create a network is modelled, along with the characteristics which have a bearing on network
performance.
This chapter explains working with antennas as well as equipment such as tower-mounted amplifiers, feeder cables, base
transceiver station equipment:
"Working With Antennas" on page 143

"Working With Equipment" on page 147
4.1 Working With Antennas

Atoll enables you to work with antennas in many ways. To create a new antenna, you can import the data necessary from
external sources, such as from a spreadsheet or from a Planet-format file. Once you have created an antenna, you can improve
signal level prediction by smoothing the high-attenuation points of the vertical pattern.
"Creating an Antenna" on page 143

"Importing Planet-Format Antennas" on page 144
"Importing 3-D Antenna Patterns" on page 145
"Smoothing an Antenna Pattern" on page 147.
4.1.1 Creating an Antenna

Each Atoll project template has antennas specific to the technology supported by the template. As well, Atoll allows you to
create antennas and set the parameters such as manufacturer, gain, horizontal pattern, and vertical pattern.
When you create a new antenna, you can copy the horizontal and vertical antenna
patterns from a spreadsheet or word processor.
To create an antenna:
1. Click the Parameters tab in the Explorer window.
2. Click the Expand button ( ) to expand the Radio Network Equipment folder.
3. Right-click on the Antennas folder. The context menu opens.
4. Select New from the context menu. The Antennas New Element Properties dialogue appears.
5. Click the General tab. You can enter information in the following fields:
-
Name: Atoll automatically enters a default name for each new antenna. You can modify the name Atoll enters if
you want.
Manufacturer: The name of the antenna manufacturer.
Gain: The antennas isotropic gain.
Pattern Electrical Tilt: The antennas electrical tilt. This field is for information only; for an antennas electrical tilt
to be taken into consideration in calculations, it must be integrated into the horizontal and vertical patterns. Atoll
automatically calculates the pattern electrical tilt if the Pattern Electrical Tilt field is left blank or has a value of
"0." This field has to be correctly filled (i.e., consistent with the defined vertical pattern) if you want the antenna
to be available when selecting an antenna for a transmitter.
Physical antenna: The name of the physical antenna to which the antenna model belongs. A physical antenna may
have one or more antenna models (patterns), corresponding to different electrical downtilts. If you want to flag a
physical antenna as obsolete, add the word "obsolete" (not case sensitive) to the name of the physical antenna.
Physical antennas flagged as obsolete are not listed among available antennas in the Antenna Selector dialogue
It is strongly recommended to enter a name in the Physical antenna field. Atoll uses this
entry to group antenna models into physical antennas.
Comments: Any additional information on the antenna.
6. Click the Horizontal Pattern tab. The Horizontal Pattern tab has a table describing the horizontal antenna pattern in
terms of the attenuation in dB (Att.) per Angle and a graphical representation of the pattern. Atoll allows you to enter
143

Forsk 2011
antenna pattern attenuations for as many as 720 angles. Therefore, attenuation values can also be defined for angles
other than integer values from 0 to 359. If you have the horizontal pattern in a spreadsheet or text document, you
can copy the data directly into the table:
a. Switch to the document containing the horizontal pattern.
b. Select the columns containing the angles and attenuation values of the horizontal pattern.
c. Copy the selected data.
Figure 4.1: Copying horizontal pattern values

d. Switch to Atoll.
e. Click the upper-left cell of the Co-polar Section table describing the horizontal pattern.
f. Press CTRL+V to paste the data in the table.
-
If there are some blank rows in your data sheet, Atoll will interpolate the values in order to obtain a complete
and realistic pattern.
When performing a calculation along an angle for which no data is available, Atoll calculates a linear interpolation from the existing pattern values.
g. Click Apply to display the pattern of the values you have pasted in.
7. Click the Vertical Pattern tab. The Vertical Pattern tab has a table describing the vertical antenna pattern in terms of
the attenuation in dB (Att.) per Angle and a graphical representation of the pattern. Atoll allows you to enter antenna
pattern attenuations for as many as 720 angles. Therefore, attenuation values can also be defined for angles other
than integer values from 0 to 359. If you have the vertical pattern in a spreadsheet or text document, you can copy
the data directly into the table as described in step 6.
8. Click the Other Properties tab. You can define the following fields (not used in any calculation):
-
Beamwidth: In a plane containing the direction of the maximum lobe of the antenna pattern, the angle between
the two directions in which the radiated power is one-half the maximum value of the lobe. In terms of dB, half
power corresponds to -3 dB. In this window, you can enter this angle in degrees. This field must be filled in correctly if you want to display transmitters using a symbol that indicates the beamwidth.
FMin: The minimum frequency that the antenna is capable of emitting.
FMax: The maximum frequency that the antenna is capable of emitting.
9. Click OK.
Atoll checks whether the vertical and horizontal patterns are correctly aligned at the extremities. The antenna patterns are
correctly aligned when:
the horizontal pattern attenuation at 0 is the same as the vertical pattern attenuation at the pattern electrical tilt
angle, and
the horizontal pattern attenuation at 180 is the same as the vertical pattern attenuation at the 180 less the pattern
electrical tilt angle.
4.1.2 Importing Planet-Format Antennas

In Atoll, you can import Planet-format antennas by importing an index file listing the individual antenna files to be imported.
Standard Atoll fields are directly imported. Other fields are imported for information only and are accessible on the Other
Properties tab of the Antenna Properties dialogue.
If you are working with a database, you will have to create the required fields before you import the Planet-format antennas.
For more details, see the relevant technical note.
144

AT310_UMU_E0
To import Planet-format antennas:

1. Select the Parameters tab in the Explorer window.
3. Right-click the Antennas folder. The context menu appears.
5. Select "Planet 2D Antenna Files (index)" from the Files of type list.
6. Select the index file you want to import and click Open. The antennas are imported.
Atoll checks whether the vertical and horizontal patterns are correctly aligned at the extremities. The antenna patterns are
correctly aligned when:
the horizontal pattern attenuation at 0 is the same as the vertical pattern attenuation at the pattern electrical tilt
angle, and
the horizontal pattern attenuation at 180 is the same as the vertical pattern attenuation at the 180 less the pattern
electrical tilt angle.
4.1.3 Importing 3-D Antenna Patterns

You can import three-dimensional antenna patterns in the form of text files. The three-dimensional antenna patterns you
import are saved in the Antennas table.
During calculations, Atoll interpolates the data of antennas for which only horizontal and vertical cross-sections are available
to create a three-dimensional pattern. When you import a three-dimensional antenna pattern, even though only horizontal
and vertical sections of the antenna pattern are displayed, Atoll conserves all the information and can use it directly; Atoll
does not therefore need to interpolate to recreate the three-dimensional antenna pattern.
The text file must have the following format:
Antenna description: Three separate values are necessary to describe the three-dimensional antenna pattern. The
columns containing the values can be in any order:
-
Azimuth: The range of values allowable is from 0 to 360, with the smallest allowable increment being 1.
Tilt angle: The range of values allowable is from -90 to 90, or from 0 to 180, with the smallest allowable increment being 1.
Attenuation: The attenuation (in dB).
The text file describing the the antenna can also contain a header with additional information. When you import the antenna
pattern you indicate where the header ends and where the antenna pattern itself begins.
To import three-dimensional antenna pattern files:
5. Select the file to import.
6. Click Open. The Setup dialogue appears (see Figure 4.2).
145

Forsk 2011
Figure 4.2: Importing a 3-D antenna pattern

7. If you already have an import configuration defining the data structure of the imported file, you can select it from the
Configuration list. If you do not have an import configuration, continue with step 8.
a. Under Configuration, select an import configuration from the Configuration list.
b. Continue with step 11.
8. Under Name, you can define a name for the imported antenna pattern. This name will appear in the Antennas folder
on the Network tab. If no name is defined, Atoll will use the file name as the name of the antenna:
-
If the name of the antenna is in the file, check the Value read in the file check box and enter a Keyword identifying
the name value in the file.
If you want to enter a name for the antenna, clear the Value read in the file check box and enter a name.
9. Under Gain, you can define the antenna gain. If no gain is defined, Atoll will assume that the gain is "0."
-
If the gain of the antenna is in the file, check the Value read in the file check box and enter a Keyword identifying
the gain value in the file.
If you want to enter a gain for the antenna, clear the Value read in the file check box and enter a gain value.
10. Under Diagram, you define the structure of the antenna pattern file. As you modify the parameters, the results are
displayed in the table.
-
1st Pattern: Select the first row of the file containing data on the antenna pattern.
File Tilt Range: Select the tilt range in the file. The tilt range can be measured from top to bottom or from bottom
to top and from 0 to 180 or from -90 to 90.
Field Separator: Select the character that is used in the file to separate fields (" ", "<tab>", ";")
Decimal Symbol: Select the decimal symbol.
11. In the table under Diagram, click the title in each column in the table and select the data type: Azimuth, Tilt, Attenuation, or <Ignore>. As you modify the parameters, the results are displayed in the table.
You can save the choices you have made in the Setup dialogue as a configuration file by
clicking the Save button at the top of the dialogue and entering a name for the configuration. The next time you import a three-dimensional antenna pattern file, you can select the
same settings from the Configuration file list.
12. Click Import. The antenna patterns are imported into the current Atoll document.
146

AT310_UMU_E0
4.1.4 Smoothing an Antenna Pattern

Empirical propagation models, such as the Standard Propagation Model (SPM), require antenna pattern smoothing in the
vertical plane to better simulate the effects of reflection and diffraction, which, therefore, improves signal level prediction. In
Atoll, you can smooth antennas vertical as well as horizontal patterns.
You should make a copy of the antenna before smoothing its vertical pattern. You can
make a copy of the antenna by opening the Antennas table and copying and pasting the
antenna data into a new row. For information on data tables, see "Working with Data
Tables" on page 47.
To smooth the vertical or horizontal pattern of an antenna:
3. Click the Expand button ( ) to expand the Antennas folder.
4. Right-click the antenna whose pattern you want to smooth. The context menu appears.
6. Select the Vertical Pattern or the Horizontal Pattern tab.
7. Right-click the graphical representation of the pattern. The context menu appears.
8. Select Smooth from the context menu. The Smoothing Parameters dialogue appears.
9. Enter the following parameters and click OK to smooth the vertical pattern:
-
Max Angle: Enter the maximum angle. Smoothing will be applied to the section of the vertical pattern between 0
and the maximum angle (clock-wise).
Peak-to-Peak Deviation: Enter the attenuation values to which smoothing will be applied. Atoll will smooth all
attenuation values greater than or equal to the peak-to-peak deviation with the defined correction factor.
Correction: Enter the correction factor by which the attenuation values will be smoothed.
10. Click OK.
4.1.5 Printing an Antenna Pattern

You can print the horizontal or vertical pattern of an antenna.
To print an antenna pattern:
4. Select Open Table from the context menu. The Antennas table appears.
5. In the Antennas table, right-click the antenna whose pattern you want to print.
6. Select Record Properties from the context menu. The Properties dialogue appears.
7. Select the Horizontal Pattern tab or the Vertical Pattern tab to display the antenna pattern you want to print.
8. Right-click the antenna pattern and select Linear or Logarithmic from the context menu.
9. Right-click the antenna pattern again and select Print from the context menu.
4.2 Working With Equipment

Atoll can model the components of base station. You can define these components and modify their properties in their
respective tables. Atoll uses these properties to calculate the downlink and uplink losses and transmitter noise figure in UMTS,
CDMA2000, WiMAX, or LTE. In GSM, Atoll calculates the downlink losses only. These parameters can be automatically calculated by Atoll from the properties of the components or they can defined by the user.
Base station subsystems consist of the following components:
Tower-mounted amplifier: Tower-mounted amplifiers (TMAs, also referred to as masthead amplifiers) are used to
reduce the composite noise figure of the base station. TMAs are connected between the antenna and the feeder
cable. To define a TMA, see "Defining TMA Equipment" on page 148.
147

Forsk 2011
Feeder cables: Feeder cables connect the TMA to the antenna. To define feeder cables, see "Defining Feeder Cables"
on page 148.
Transmitter equipment: To define transmitter equipment, see "Defining Transmitter Equipment" on page 148.
4.2.1 Defining TMA Equipment

The tower-mounted amplifier (TMA) is used to reduce the composite noise figure of the base station. Once you have defined
a TMA, you can assign it to individual transmitters.
To create a tower-mounted amplifier:
3. Right-click the TMA folder. The context menu appears.
4. Select Open Table from the context menu. The TMA table appears.
5. In the table, create one TMA per row. For information on using data tables, see "Working with Data Tables" on
page 47. For each TMA, enter:
-
Name: Enter a name for the TMA. This name will appear in other dialogues when you select a TMA.
Noise Figure (dB): Enter a noise figure for the TMA.
Reception Gain (dB): Enter a reception (uplink) gain for the TMA. This must be a positive value.
Transmission Losses (dB): Enter transmission (downlink) losses for the TMA. This must be a positive value.
4.2.2 Defining Feeder Cables

Feeder cables connect the TMA to the antenna. Once you have defined feeder cables, you can assign them to individual transmitters.
To create feeder cables:
3. Right-click the Feeders folder. The context menu appears.
4. Select Open Table from the context menu. The Feeder table appears.
5. In the table, create one feeder per row. For information on data tables, see "Working with Data Tables" on page 47.
For each feeder, enter:
-
Name: Enter a name for the feeder cable. This name will appear in other dialogues when you select a feeder cable.
Loss per Length: Enter the loss per meter of cable. This must be a positive value.
Connector Reception Loss: Enter the connector reception loss. This must be a positive value.
Connector Transmission Loss: Enter the connector transmission loss. This must be a positive value.
4.2.3 Defining Transmitter Equipment

Transmitter equipment is modelled for UMTS, CDMA2000, TD-SCDMA, WiMAX, and LTE. In GSM, only the downlink losses are
modelled.
Once you have defined transmitter equipment, it can be assigned to individual transmitters.
To create transmitter equipment:
3. Right-click the Transmitter Equipment folder. The context menu appears.
4. Select Open Table from the context menu. The Transmitter Equipment table appears.
5. In the table, create one entry per row. For information on data tables, see "Working with Data Tables" on page 47. For
each transmitter equipment entry, enter:
-
148
Name: Enter a name for the transmitter equipment. This name will appear in other dialogues when you select
transmitter equipment.
Noise Figure (dB): Enter the noise figure for the transmitter equipment. This value is not used in GSM GPRS EDGE
documents.
Downlink Losses Due to the Configuration (dB): Enter the losses on downlink due to the transmitter equipment
configuration.

AT310_UMU_E0
Uplink Losses Due to the Configuration (dB): Enter the losses on uplink due to the transmitter equipment configuration. This value is not used in GSM GPRS EDGE documents.
CDMA Rho Factor (%): Enter the CDMA Rho factor, as a percentage. The CDMA Rho factor enables Atoll to take
into account self-interference produced by the transmitter equipment. Because equipment is not perfect, an input
signal will experience some distortion, consequently the output signal will be not be identical. This factor defines
how much distortion the system generates. Entering 100% means the system is perfect (there is no distortion) and
the output signal will be 100% identical to the input signal. On the other hand, if you specify a value different from
100%, Atoll will consider that the transmitted signal is not 100% signal and that it contains a small percentage of
interference generated by the equipment ("self-interference"). Atoll uses this parameter to evaluate the signalto-noise ratio in the downlink.
This value is only used in CDMA-based technologies (CDMA2000, UMTS, and TD-SCDMA). It is not used in GSM,
WiMAX, and LTE documents.
4.2.4 Updating the Values for Total Losses and the Transmitter
Equipment Noise Figure
Once equipment is defined and assigned to a transmitter, Atoll can evaluate downlink and uplink total losses and the total
noise figure.
Atoll uses the entry of the transmitter equipment as the reference point when evaluating total losses and the total noise
figure. The transmitter equipment noise figure used by Atoll is the one specified in the transmitter equipment properties.
Transmitter reception losses include feeder reception losses, connector reception losses, miscellaneous reception losses,
antenna diversity gain, TMA benefit gain (as calculated using the Friis equation), and an additional loss modelling the noise
rise generated from repeaters (if any). Transmitter transmission losses include feeder transmission losses, connector transmission losses, miscellaneous transmission losses, and TMA transmission losses. For more information on the total noise
figure and on transmitter reception and transmission losses, see the Technical Reference Guide.
You can assign equipment to a transmitter:
Using the Equipment Specifications dialogue, available by clicking the Equipment button on the Transmitter tab of
the transmitters Properties dialogue, or
Using the Transmitters table, available by right-clicking the Transmitters folder on the Network tab of the Explorer
window and selecting Open Table from the context menu.
When you assign equipment to a transmitter using the Equipment Specifications dialogue, Atoll updates the real values when
you click OK and close the dialogue. When you assign equipment to a transmitter using the Transmitters table, Atoll does not
update the real values automatically.
To update the real values (total losses and transmitter equipment noise figure) with the calculated values of all transmitters:
2. Right-click the Transmitters folder. The context menu appears.
3. Select Calculations > Update Losses and Noise Figures from the context menu.
To update the real values (total losses and transmitter equipment noise figure) with the calculated values of a group of transmitters:
3. Click Group by in the context menu and select the property by which you want to group the transmitters from the
Group by submenu. The objects in the folder are grouped by that property.
4. Click the Expand button ( ) to expand the Transmitters folder.
5. Right-click the group of transmitters whose real values you want to update. The context menu appears.
6. Select Open Table from the context menu. The Transmitters table appears with the transmitters from the selected
group.
7. In the Transmitters table, select the values you want to update in the following columns and press DEL:
-
Transmission Loss (dB)

Reception Loss (dB)
Noise Figure (dB)
Atoll automatically recalculates and updates these values.
149

1.
a.
b.
c.
d.
2.
a.
b.
c.
d.
e.
3.
4.
5.
6.
7.
8.
9.
10.
4.2.5
11.
12. ()
-
150
Forsk 2011

AT310_UMU_E0
4.2.6 Creating or Modifying a Radio

1.
a.
b.
c.
d.
e.
f.
g.
h.
-
2.
a.
b.
c.
3.
4.
5.
4.2.7
6.
7.
a.
151

4.2.8 Creating or Modifying Waveguides and Cables

1.
a.
b.
c.
d.
2.
a.
b.
c.
3.
152
Forsk 2011
Chapter 5
Working with
Calculations in Atoll
This chapter provides the information to work with
calculations in Atoll.
"Working with Propagation Models" on page 155
"Defining Calculation Parameters" on page 173
"Managing Path Loss Matrices" on page 175
"Predictions Available in Atoll" on page 186

Chapter 5: Working with Calculations in Atoll
154
Forsk 2011

AT310_UMU_E0
5 Working with Calculations in Atoll

Once you have created a network, you can make predictions. There are two types of predictions:
Point predictions using the Point Analysis tool: The Point Analysis tool allows you to predict, at any point on the map,
the profile between a reference transmitter and a receiver, the value of the signal levels of the surrounding transmitters, an active set analysis for UMTS, CDMA2000, and TD-SCDMA projects and an interference analysis for GSM/GPRS/
EDGE projects.
Coverage predictions: You can calculate standard coverage predictions, coverage by transmitter, coverage by signal
level and overlapping zones, and specific coverage predictions such as interference predictions for GSM/GPRS/EDGE
projects or handover, service availability, etc. for UMTS, CDMA2000 and TD-SCDMA projects. Many customisation features on coverage predictions are available in order to make their analysis easier.
Atoll facilitates the calculation of coverage predictions with support for multithreading and distributed calculating. The
progress of the calculations can be displayed in the Event Viewer window or in a log file.
Atoll also allows you to use polygonal zones to limit the amount of resources and time used for calculations. The polygonal
zones, such as the filtering zone and the computation zone, help you to restrict calculations to a defined set of transmitters,
and to limit calculations and coverage predictions.
Depending on the type of project you are working on, you can choose between the propagation models available in Atoll.
5.1 Working with Propagation Models

In the section, the following are explained:
"Propagation Model Characteristics: Overview" on page 155

"The Standard Propagation Model" on page 156
"The Okumura-Hata Propagation Model" on page 163
"The Cost-Hata Propagation Model" on page 164
"The ITU 529-3 Propagation Model" on page 166
"The Erceg-Greenstein Propagation Model" on page 167
"The WLL Propagation Model" on page 169
"The Longley-Rice Propagation Model" on page 170
"The ITU 1546 Propagation Model" on page 170
"The Sakagami Extended Propagation Model" on page 171
"CrossWave Model" on page 171
"Managing Propagation Models" on page 172.
5.1.1 Propagation Model Characteristics: Overview

Each propagation model available in Atoll is suited for certain conditions, frequencies and radio technologies. The following
table summarises the frequency band, necessary geo data, recommended use of each propagation model.
Model
Frequency Range
Geo Data Taken into Account
Recommended Use
ITU 370-7 Vienna 93
100 400 MHz
Terrain profile
d > 10 km
Low frequencies
Broadcast
ITU 1546
30 3000 MHz
Terrain profile
1 < d < 1000 km

Land and maritime mobile,
broadcast
ITU 526-5 (theoretical)
30 10000 MHz
Terrain profile
Fixed receivers
WLL
WLL
30 10000 MHz
Terrain profile
Deterministic clutter
Fixed receivers
WLL, Microwave links, WiMAX
150 1000 MHz
Terrain profile
Statistical clutter (at the receiver)
1 < d < 20 km
GSM 900, CDMA2000, LTE
Okumura-Hata
(Automatic calibration
available)
155

Model
Forsk 2011
Frequency Range
Geo Data Taken into Account
Recommended Use
1500 2000 MHz
Terrain profile
1 < d < 20 km
GSM 1800, UMTS, CDMA2000,
LTE
300 1500 MHz
Terrain profile
1 < d < 100 km

GSM 900, CDMA2000, LTE
150 3500 MHz
Terrain profile
Statistical clutter
1 < d < 20 km
GSM, UMTS, CDMA2000,
WiMAX, LTE
Terrain profile
Urban and suburban areas

100 m < d < 8 km
Fixed WiMAX
3000 8000 MHz
Terrain profile
Statistical clutter
1 < d < 20 km
WiMAX
200 5000 MHz
Terrain profile
Statistical or deterministic clutter
3D building and line vectors
(optionnal)
Specific morphology, facets and
graphs data files (optionnal)
Any engineering (micro, mini,

small and macro cells)
GSM, UMTS, CDMA2000,
WiMAX, LTE
Cost-Hata
available)
ITU 529-3
Standard Propagation
Model
available)
Erceg-Greenstein (SUI) 1900 6000 MHz
Sakagami Extended
available)
CrossWave Model
5.1.2 The Standard Propagation Model

The Standard Propagation Model is a propagation model based on the Hata formulas and is suited for predictions in the 150
to 3500 MHz band over long distances (from one to 20 km). It is best suited to GSM 900/1800, UMTS, and CDMA2000 radio
technologies.
The Standard Propagation Model is based on the following formula:
K 1 + K 2 Log ( d ) + K 3 Log ( H Txeff ) + K 4 DiffractionLoss + K 5 Log ( d ) Log ( H Txeff ) +
P R = P Tx
K 6 H Rx eff + K 7 Log ( H Rx eff ) + K clutter f ( clutter ) + K hill, LOS
where:
PR
received power (dBm)
PTx
transmitted power (EIRP) (dBm)
K1
constant offset (dB)
K2
multiplying factor for Log(d)
distance between the receiver and the transmitter (m)
K3
multiplying factor for Log(HTxeff)
H Tx
effective height of the transmitter antenna (m)
K4
multiplying factor for diffraction calculation. K4 must be a positive number

DiffractionLoss losses due to diffraction over an obstructed path (dB)
K5
multiplying factor for Log(HTxeff) x Log(d)
K6
multiplying factor for HRxeff
K7
multiplying factor for Log(HRxeff)
H Rx
Kclutter
multiplying factor for f(clutter)
f(clutter)
average of weighted losses due to clutter
Khill, LOS
corrective factor for hilly regions (=0 in case of NLOS)
156
eff
eff
mobile antenna height (m)

AT310_UMU_E0
These parameters can be defined on the tabs (Parameters, and Clutter) of the Standard Propagation Model Properties
dialogue. You can also calibrate the Standard Propagation Model using a wizard. For information on the Automatic Calibration
Wizard, see the Measurements and Model Calibration Guide.
"Recommendations for Working with the Standard Propagation Model" on page 157
"Calculating Diffraction With the SPM" on page 158
"Sample Values for SPM Formulas" on page 158
"Calculating f(clutter) with the Standard Propagation Model" on page 159
"Modelling Fixed Receivers" on page 160
"Defining the Parameters of the Standard Propagation Model" on page 160.
5.1.2.1 Recommendations for Working with the Standard Propagation Model

It is important to remember that clutter information can be taken into consideration in both diffraction loss and f(clutter). To
avoid taking clutter information into account twice, you should choose one of the following approaches:
Approach #1: If you specify losses per clutter class, do not consider clutter altitudes in diffraction loss over the transmitter-receiver profile. This approach is recommended if the clutter height information is statistical (i.e., where the
clutter is roughly defined and without a defined altitude).
Because the Standard Propagation Model is a statistical propagation model, using this
approach is recommended.
Approach #2: If you consider clutter altitudes, do not define any loss per clutter class. In this case, f(clutter) will be
"0;" losses due to clutter will only be taken into account in the calculated diffraction. This approach is recommended
if the clutter altitude information is semi-deterministic (i.e., where the clutter is roughly defined with an average altitude per clutter class) or deterministic (i.e., where the clutter is sharply defined with an average altitude per clutter
class or where there is a clutter height file).
If the clutter height information is an average height defined for each clutter class, you must specify a receiver clearance per clutter class. Both ground and clutter altitude are considered along the whole transmitter-receiver profile
except over a specific distance around the receiver (clearance), in which Atoll bases its calculations only on the DTM.
The clearance information is used to model streets because it is assumed that the receiver is in the street.
It is not necessary to define receiver clearance if the height information is from a clutter height file. In this case, the
clutter height information is accurate enough to be used without additional information such as clearance; Atoll calculates the path loss if the receiver is in the street (if the receiver height is higher than the clutter height). If the receiver
height is lower than the clutter height, the receiver is assumed to be inside a building. In this case, Atoll does not
consider any diffraction for the building (or any clearance) but takes into account the clutter class indoor loss as an
additional penetration loss. Nevertheless, Atoll does consider diffraction caused by surrounding buildings. In
Figure 5.1 on page 158 this diffraction is displayed with a green line.
In order to consider indoor losses inside a building when only using a deterministic
clutter map (i.e., a clutter height map), you must clear the Indoor Coverage check box
when creating a prediction or indoor losses will be added twice (once for the entire
reception clutter class and once as indoor losses).
157

Forsk 2011
Figure 5.1: Diffraction caused by surrounding buildings when the receiver is indoors
5.1.2.2 Calculating Diffraction With the SPM

You can set the parameters used to calculate diffraction losses on the Parameters and Clutter tabs of the Standard Propagation Model Properties dialogue.
On the Parameters tab, you can define the calculation method used for diffraction and the K4 factor. The methods available
are:
Deygout
Epstein-Peterson
Deygout with correction
Millington
For detailed information on each method, see the Technical Reference Guide. The methods for calculating diffraction are
based on the general method for one or more obstacles described in the ITU 526-5 recommendations. The calculations take
the curvature of the earth into account. Along the transmitter-receiver profile, you can choose to take either the ground altitude only or both the ground altitude and the clutter height into account. If you choose to take clutter height into account,
Atoll uses the clutter height information in the clutter heights file. Otherwise, it uses average clutter height specified for each
clutter class in the clutter classes. When the clutter height information is statistical, Atoll also uses clearance values per clutter
class to model streets.
To take heights into account when calculating diffraction:
2. Click the Expand button ( ) to expand the Propagation Models folder.
3. Right-click Standard Propagation Model. The context menu appears.
5. Click the Clutter tab.
6. Under Heights, select one of the following for Clutter taken into account in diffraction:
-
1 - Yes: Select "1 - Yes" if you want heights from the clutter heights to be taken into account on top of the DTM
when calculating diffraction.
0 - No: Select "0 - No" if you want diffraction to be calculated using only the DTM.
7. Click OK.
5.1.2.3 Sample Values for SPM Formulas

The following table gives some possible values for the constants used in the Standard Propagation Model formulas.
K1
158
Minimum
Typical
Maximum
Variable
Variable
Variable

AT310_UMU_E0
Minimum
Typical
Maximum
K2
20
44.9
70
K3
-20
5.83
20
K4
0.5
0.8
K5
-10
-6.55
K6
-1
K7
-10
It is recommended to set K6 to 0, and use K7 instead of K6. K6 is a multiplicative coefficient to a value in dB, which means that
slight variations in K6 have considerable impact on the path loss.
K1 is a constant; its value depends on the radio frequency and on the radio technology. The following table gives some possible values for K1.
Project Type
Frequency (MHz)
K1
GSM 900
935
12.5
GSM 1800
1805
22
GSM 1900
1930
23
UMTS
2110
23.8
1xRTT
1900
23
2300
24.7
2500
25.4
2700
26.1
3300
27.8
3500
28.3
WiMAX
Its value is heavily influenced by the values given to losses per clutter class.
5.1.2.4 Calculating f(clutter) with the Standard Propagation Model

The average of weighted losses due to clutter, f(clutter), is defined as follows:
n
f ( clutter ) =
Li wi
i=1
where
L: loss due to clutter.
w: weight.
n: number of points taken into account over the profile.
The losses due to clutter are calculated for the maximum distance from the receiver, defined as Maximum Distance on the
Clutter tab of the Standard Propagation Model Properties dialogue. When the Maximum Distance is defined as "0", Atoll
only considers the losses on the pixel where the receiver is located. On the Clutter tab, each clutter class is assigned losses
and a weighting function, enabling Atoll to give a weight to each point. For more information, see the Technical Reference
Guide.
The losses per clutter class can be calculated using the Automatic Calibration Wizard. For
information on the Automatic Calibration Wizard, see the Measurements and Model Calibration Guide.
159

Forsk 2011
The following table gives typical values for losses (in dB) per clutter class:
Clutter Class
Losses (dB)
Dense urban
from 4 to 5
Woodland
from 2 to 3
Urban
Suburban
from -5 to -3
Industrial
from -5 to -3
Open in urban
from -6 to -4
Open
from -12 to -10
Water
from -14 to -12
The Standard Propagation Model is based on Hata formulas, which are valid for an urban
environment. The values above are consistent with an urban environment because losses
of 0 dB are indicated for an urban clutter class, with positive values for more dense clutter
classes and negative values for less dense clutter classes.
5.1.2.5 Modelling Fixed Receivers

The following are suggestions for defining the height of fixed receivers:
You can model the receiver as always being above the clutter, by selecting "1 - Yes" for the Receiver on Top of Clutter
option on the Clutter tab of the Standard Propagation Model Properties dialogue. The receiver height will then be
sum of the clutter height and the receiver height. This option can be used to model receivers on top of buildings, for
example.
You can define a specific receiver height for each clutter class in the Rx Height column on the Clutter tab of the
Standard Propagation Model Properties dialogue. Or, you can select "(default)" for the receiver height. When creating a coverage prediction, Atoll will then read the receiver height on the Receiver tab of the Properties dialogue for
the Predictions folder.
5.1.2.6 Defining the Parameters of the Standard Propagation Model

You can define the parameters of the Standard Propagation Model using the Standard Propagation Model Properties
dialogue.
Default values have been assigned to the multiplying factors. The default values correspond to the rural (quasi-open) Okumura-Hata formula valid for a frequency of 935 MHz.
The values for K values can be calculated using an automatic or assisted calibration
method. For more information, see the Measurements and Model Calibration Guide.
To define the calculations parameters of the Standard Propagation Model:
3. Right-click Standard Propagation Model. The context menu appears.
5. Click the Parameters tab (see Figure 5.2).
160

AT310_UMU_E0
Figure 5.2: Standard Propagation Model - Parameters tab

Under Near Transmitter, you can set the following parameters:
-
Maximum Distance: Set the maximum distance for a receiver to be considered near the transmitter. If the distance between the receiver and the transmitter is greater than the set distance, the receiver is considered far from
the transmitter.
K1 - los and K2 - los: Enter the K1 and K2 values that will be used for calculations when the receiver is in the transmitter line of sight.
K1 - nlos and K2 - nlos: Enter the K1 and K2 values that will be used for calculations when the receiver is not in the
transmitter line of sight.
Under Far from Transmitter, the values you set will be used for all receivers whose distance from the transmitter is
greater than the distance specified in Maximum Distance under Near Transmitter. You can set the following parameters:
-
K1 - los and K2 - los: Enter the K1 and K2 values that will be used for calculations when the receiver is in the transmitter line of sight.
K1 - nlos and K2 - nlos: Enter the K1 and K2 values that will be used for calculations when the receiver is not in the
transmitter line of sight.
The LOS is defined by no obstruction along the direct ray between the transmitter and the
receiver.
Under Effective Antenna Height, you can set the following parameters:
-
Method: Select the method that will be used to calculate HTxeff, the effective antenna height.
You can use the Automatic Calibration Wizard to select the best method for calculating
the effective Tx antenna height. For information on the Automatic Calibration Wizard, see
the Measurements and Model Calibration Guide.
Distance min. and Distance max.: The Distance min. and Distance max. are set to 3,000 m and 15,000 m
(according to ITU recommendations) for frequencies under 500 MHz and to 0 m and 15,000 m (according to ITU
recommendations) for high frequency mobile communications. These values are only used for the "Abs Spot Ht"
and the "Enhanced Slope at Receiver" methods. For more information on how these values are used, see the Technical Reference Guide.
161

Forsk 2011
K3: Enter the K3 value.
Under Diffraction, you can set the following parameters:

-
Method: Select the method that will be used to calculate diffraction.

Under Other Parameters, you can set the following parameters:

-

It is recommended to set K6 to 0, and use K7 instead of K6. K6 is a multiplicative coefficient to a value in dB, which
means that slight variations in K6 have considerable impact on the path loss.

Kclutter: Enter the Kclutter value.
Hilly Terrain Correction Factor: Select "1 - Yes" to take the Hilly Terrain Correction Factor into account. Otherwise, select "0 - No". The Hilly Terrain Correction Factor corrects path loss for hilly regions when transmitter and
receiver are in LOS. For more information on the Hilly Terrain Correction Factor, see the Technical Reference
Guide.
Limitation to Free Space Loss: When using a Hata-based propagation model, it is possible to calculate a theoretical
path loss that ends up being lower than the free space loss. In Atoll, you can define any Hata-based propagation
model to never calculate a path loss that is lower than the calculated free space loss per pixel. Select "1 - Yes" if
you want the propagation model to limit the path loss calculated per pixel to the calculated free space loss.
Profiles: Select the method to be used to extract the profile. If you select "1 - Radial," Atoll establishes a profile
between each transmitter and each point located on its calculation perimeter (as defined by the calculation
radius) and then uses the nearest profile to make a prediction on a point inside the calculation perimeter. This
process is called radial optimisation. If you select "2 - Systematic," Atoll systematically determines a profile
between each transmitter and each point in its calculation area. This method requires a significantly longer calculation time, therefore, you should choose "1 - Radial" if you want a shorter calculation time.
Grid Calculation: Select "0 - Centred" if you want Atoll to perform the calculations at the centre of each pixel or
select "1 - Bottom left" if you want Atoll to perform the calculations at the lower left of each pixel.
6. Click the Clutter tab (see Figure 5.3).
Figure 5.3: Standard Propagation Model - Clutter tab

Under Clutter Taken into Account, you can set the following parameters under Heights:
-
162
Clutter taken into account in diffraction: Select "1 - Yes" if you want the clutter heights to be taken into account
when calculating diffraction.

AT310_UMU_E0
Receiver on top of clutter: Select "1 - Yes" if you want the receiver to be considered to be located on top of clutter.
This option can be used where fixed receivers are located on top of buildings.
Under Clutter Taken into Account, you can set the following parameters under Range:
-
Max. distance: Set the maximum distance from a receiver to be considered when calculating f(clutter).
Weighting function: Select a weighting function to be used when calculating f(clutter). It enables you to weight
losses for each pixel between a receiver and a maximum distance. For more information on weighting functions,
see the Technical Reference Guide.
Under Parameters per clutter class, you can set the following parameters for each clutter class:
-
Losses: Enter, if desired, losses for each clutter class to be considered when calculating f(clutter).
Clearance: Enter, if desired, a clearance around each receiver for each clutter class. The clearance information is
used to model streets because it is assumed that the receiver is in the street. The clearance is used when calculating diffraction when statistical clutter is taken into account.
Rx Height: Enter, if desired, a specific receiver height for each clutter class. Or, you can select "(default)" for the
receiver height. When creating a coverage prediction, Atoll will then read the receiver height on the Receiver tab
of the Properties dialogue for the Predictions folder.
7. Click OK.
5.1.3 The Okumura-Hata Propagation Model

The Okumura-Hata model is suited for predictions in the 150 to 1000 MHz band over long distances (from one to 20 km). It is
best suited to GSM 900 and CDMA 1xRTT radio technologies.
Hata models in general are well adapted to the urban environment. You can define several corrective formulas and associate
a formula with each clutter class to adapt the Hata model to a wide variety of environments. You can also define a default
formula to be used when no land use data is available. Additionally, you can consider diffraction losses based on the DTM.
"Defining General Settings (Okumura-Hata)" on page 163

"Selecting an Environment Formula (Okumura-Hata)" on page 163
"Creating or Modifying Environment Formulas (Okumura-Hata)" on page 164.
5.1.3.1 Defining General Settings (Okumura-Hata)

To set general parameters on the Okumura-Hata propagation model:
3. Right-click Okumura-Hata. The context menu appears.
5. Click the Parameters tab. You can modify the following settings:
-
Add diffraction loss: The Okumura-Hata propagation model can take into account losses due to diffraction, using
a 1-knife-edge Deygout method, and using the ground altitude given in the DTM. For detailed information on the
Deygout method, see the Technical Reference Guide. The calculations take the curvature of the earth into account.
Select "1 - Yes" if you want the propagation model to add losses due to diffraction. You can weight this diffraction
for each Hata environment formula (See "Creating or Modifying Environment Formulas (Okumura-Hata)" on
page 164)
Limitation to free space loss: When using a Hata-based propagation model, it is possible to calculate a theoretical
6. Click OK.
5.1.3.2 Selecting an Environment Formula (Okumura-Hata)

The Okumura-Hata propagation model can use an environment formula appropriate to each clutter class when calculating.
You can assign a default formula that Atoll can use for all clutter classes for which you have not assigned an environment
formula or if you do not have clutter classes in your Atoll document.
To select environment formulas:
163

Forsk 2011
5. Click the Configuration tab.
6. Under Formulas assigned to clutter classes, select the Default formula row. Under this grid, choose the appropriate
formula in the formula scrolling list.
Atoll uses the default environment formula for calculations on any clutter class to which you have not assigned an
environment formula or if you do not have clutter classes in your Atoll document.
7. For each clutter class under Formulas assigned to clutter classes, select a formula from the list.
8. For each clutter class under Additional Losses per Clutter Class, enter an optional correction (in dB). This correction
acts as an additional loss on the loss calculated by the chosen formula.
For information on modifying the selected formula, see "Creating or Modifying Environment Formulas (OkumuraHata)" on page 164.
9. Click OK.
Correction terms can be evaluated using the Automatic Calibration Wizard. For information on the Automatic Calibration Wizard, see the Measurements and Model Calibration
Guide.
5.1.3.3 Creating or Modifying Environment Formulas (Okumura-Hata)

Several environment formulas are available with the Okumura-Hata propagation model to model different environments. You
can modify existing environment formulas used by the Okumura-Hata propagation model or create new environmental
formulas.
To create or modify an environment formula:
6. Click the Formulas button. The Formulas dialogue appears. You can do the following:
-
Add: To create a new formula, click the Add button and modify the parameters of the formula.
Delete: To delete a formula, select the formula and click the Delete button.
Modify: To modify an existing formula, select the formula and modify the parameters.
7. Click OK to save your changes and close the Formulas dialogue.

8. Click OK.
You can weight the diffraction loss by setting the diffraction multiplying factor
within the range [0;1].
Constant values and diffraction multiplying factor can be evaluated using the Automatic Calibration Wizard for each environment formula. For information on the
Automatic Calibration Wizard, see the Measurements and Model Calibration
Guide.
5.1.4 The Cost-Hata Propagation Model

The Cost-Hata model is suited for coverage predictions in the 1500 to 2000 MHz band over long distances (from one to 20 km).
It is best suited to DCS 1800 and UMTS radio technologies.
formula to be used when no land use data is available.
164
"Defining General Settings (Cost-Hata)" on page 165

"Selecting an Environment Formula (Cost-Hata)" on page 165
"Creating or Modifying Environment Formulas (Cost-Hata)" on page 165.

AT310_UMU_E0
5.1.4.1 Defining General Settings (Cost-Hata)

To set general parameters on the Cost-Hata propagation model:
3. Right-click Cost-Hata. The context menu appears.
-
Add diffraction loss: The Cost-Hata propagation model can take into account losses due to diffraction, using a 1knife-edge Deygout method, and using the ground altitude given in the DTM. For detailed information on the
Select "1 - Yes" if you want the propagation model to add losses due to diffraction. You can weight this diffraction
for each Hata environment formula (See "Creating or Modifying Environment Formulas (Cost-Hata)" on page 165)
6. Click OK.
5.1.4.2 Selecting an Environment Formula (Cost-Hata)

The Cost-Hata propagation model can use an environment formula appropriate to each clutter class when calculating. You can
assign a default formula that Atoll can use for all clutter classes for which you have not assigned an environment formula or
if you do not have clutter classes in your Atoll document.
6. Under Formulas assigned to clutter classes, select the Default formula row. Under this grid, choose the appropriate
formula in the formula scrolling list.
8. For each clutter class under Additional Losses per Clutter Class, enter an optional correction (in dB). This correction
acts as an additional loss on the loss calculated by the chosen formula.
9. Click OK.
5.1.4.3 Creating or Modifying Environment Formulas (Cost-Hata)

Several environment formulas are available with the Cost-Hata propagation model to model different environments. You can
modify existing environment formulas used by the Cost-Hata propagation model or create new environmental formulas.
-
165

Forsk 2011
8. Click OK.
You can weight the diffraction loss by setting the diffraction multiplying factor
within the range [0;1].
Constant values and diffraction multiplying factor can be evaluated using the Automatic Calibration Wizard for each environment formula. For information on the
Automatic Calibration Wizard, see the Measurements and Model Calibration
Guide.
5.1.5 The ITU 529-3 Propagation Model

The ITU 529-3 model is suited for predictions in the 300 to 1500 MHz band over long distances (from one to 100 km). It is best
suited to the GSM 900 radio technology.
formula to be used when no land use data is available. In addition, for long distances 20km<d<100 km), the model uses automatically a corrective formula as defined in the recommendation.
"Defining General Settings (ITU 529-3)" on page 166

"Selecting an Environment Formula (ITU 529-3)" on page 166
"Creating or Modifying Environment Formulas (ITU 529-3)" on page 167.
5.1.5.1 Defining General Settings (ITU 529-3)

To set general parameters on the ITU 529-3 propagation model:
3. Right-click ITU529. The context menu appears.
-
Add diffraction loss: The ITU 529-3 propagation model can take into account losses due to diffraction, using a 1knife-edge Deygout method, and using the ground altitude given in the DTM. For detailed information on the
Select "1 - Yes" if you want the propagation model to add losses due to diffraction.
6. Click OK.
5.1.5.2 Selecting an Environment Formula (ITU 529-3)

The ITU 529-3 propagation model can use an environment formula appropriate to each clutter class when calculating. You can
assign a default formula that Atoll can use for all clutter classes for which you have not assigned an environment formula or
if you do not have clutter classes in your Atoll document.
6. Under Formulas assigned to clutter classes, select a Default formula.
166

AT310_UMU_E0
For information on modifying the selected formula, see "Creating or Modifying Environment Formulas (ITU 529-3)" on
page 167.
8. Click OK.
5.1.5.3 Creating or Modifying Environment Formulas (ITU 529-3)

Several environment formulas are available with the ITU 529-3 propagation model to model different environments. You can
modify existing environment formulas used by the ITU 529-3 propagation model or create new environmental formulas.
-

8. Click OK.

The ITU 370-7 model is based on the recommendations of the Vienna 1993 international conference on telecommunications
network coordination. This model is suited for predictions in the 100 to 400 MHz band over long distances (over 10 km), such
as in broadcast predictions. It uses the terrain profile to calculate propagation.
The only parameter you can define with the ITU 370-7 (Vienna 93) model is the percentage of time during which the real field
is higher than the signal level calculated by the model (1%, 10%, or 50% of the time). The value 50% is usually used for coverage predictions, whereas 1% is usually used for interference predictions.
To set the percentage of time during which the real field is higher than the signal level:
5. Click the Parameters tab.
6. Under Calculate exceeded signal during, select one of the following:
-
50% of the time

10% of the time
1% of the time
7. Click OK.
When using the ITU 370-7 model, do not define the cell edge coverage probability in the
coverage prediction properties with a value other than 50%, or cell edge coverage probability will be considered twice.
5.1.7 The Erceg-Greenstein Propagation Model

The Erceg-Greenstein (SUI) propagation model is suited for predictions in the 1900 and 6000 MHz range over distances
between 100 m and 8 km. The Erceg-Greenstein (SUI) propagation model is suited for WiMAX (IEEE 802.16e).
The Erceg-Greenstein (SUI) propagation model is well adapted for suburban environment. You can define several corrective
formulas and associate a formula with each clutter class to adapt the model to a wide range of environments. You can also
define a default formula to be used when no land use data is available. You can also set a default formula which is used when
no clutter data is available.
167

Forsk 2011
"Defining General Settings (Erceg-Greenstein (SUI))" on page 168

"Selecting an Environment Formula (Erceg-Greenstein (SUI))" on page 168
"Creating or Modifying Environment Formulas (Erceg-Greenstein (SUI))" on page 168.
5.1.7.1 Defining General Settings (Erceg-Greenstein (SUI))

To set general parameters on the Erceg-Greenstein (SUI) propagation model:
3. Right-click Erceg-Greenstein (SUI). The context menu appears.
-
Add diffraction loss: The Erceg-Greenstein (SUI) propagation model can take into account losses due to diffraction, using a 1-knife-edge Deygout method, and using the ground altitude given in the DTM. For detailed information on the Deygout method, see the Technical Reference Guide. The calculations take the curvature of the earth
into account. Select "1 - Yes" if you want the propagation model to add losses due to diffraction.
Limitation to free space loss: When using the Erceg-Greenstein (SUI) propagation model, it is possible to calculate
a theoretical path loss that ends up being lower than the free space loss. In Atoll, you can define the Erceg-Greenstein (SUI) propagation model to never calculate a path loss that is lower than the calculated free space loss per
pixel. Select "1 - Yes" if you want the propagation model to limit the path loss calculated per pixel to the calculated
free space loss.
7. Click OK.
5.1.7.2 Selecting an Environment Formula (Erceg-Greenstein (SUI))

The Erceg-Greenstein (SUI) propagation model can use an environment formula appropriate to each clutter class when calculating. You can assign a default formula that Atoll can use for all clutter classes for which you have not assigned an environment formula or if you do not have clutter classes in your Atoll document.
6. Under Formulas assigned to clutter classes, select a Default formula.
For information on modifying the selected formula, see "Creating or Modifying Environment Formulas (Erceg-Greenstein (SUI))" on page 168.
8. Click OK.
5.1.7.3 Creating or Modifying Environment Formulas (Erceg-Greenstein (SUI))

Several environment formulas are available with the Erceg-Greenstein (SUI) propagation model to model different environments. You can modify existing environment formulas used by the Erceg-Greenstein (SUI) propagation model or create new
environmental formulas.
168

AT310_UMU_E0
-

8. Click OK.

The ITU 526-5 model is suitable for predictions in the 30 to 10,000 MHz band with fixed receivers.
According to the ITU 526-5 recommendations:
If there are no obstacles, propagation takes place in free space

If there is an obstacle, attenuation due to diffraction will be taken into account. The model uses the terrain profile and
a diffraction mechanism (3-knife-edge Deygout method), optionally with correction, to calculate path loss.
To set the parameters on the ITU 526-5 propagation model:

6. If desired, select the Apply to empirical correction check box and enter a formula that will be used as a correction with
the Deygout method. Otherwise, the Deygout method will be used without correction.
7. Click OK.
5.1.9 The WLL Propagation Model

The WLL propagation model is designed for radio local loop applications in the 30-10,000 MHz band. The model is derived
from the ITU 526-5 model.
Along the Tx-Rx profile, both ground altitude and clutter height are considered to calculate diffraction losses. Atoll takes clutter height information in clutter heights file if available in the ATL document. Otherwise, it considers average clutter height
specified for each clutter class in the clutter classes file description. If the ATL document does not contain any clutter height
file and no average height per clutter class is specified, Atoll will consider ground altitude only.
To set the parameters on the WLL propagation model:
3. Right-click WLL. The context menu appears.
5. Click the Parameters tab. You can set the following parameters:
-
Free space loss: You can modify the parameters of the formula used to calculate path loss in free space.
Line of sight only: If the Line of sight only option is selected, Atoll checks for each pixel if the receiver is in the
transmitter line of sight. The receiver is considered to be in the transmitter line of sight if 100% of the Fresnel halfellipsoid is clear, in other words, if no obstacle is on the transmitter-receiver profile. If the receiver is not in the
transmitter line of sight, no results at all will be displayed. If the Line of sight only option is not selected, Atoll calculates the path loss for each pixel, using the formula defined in the dialogue.
If you select the Line of sight only option and the receiver is not in the transmitter line of
sight, no results at all will be displayed because Atoll will only show results for the line of
sight.
Transmitter clearance: You can set the clearance around the transmitter. This clearance can be used, for example,
to model streets in areas where the clutter class file does not show enough detail. It will be taken into consideration when calculating diffraction. The default value is 20 m.
Receiver default clearance: You can set the default clearance around the receiver. This default clearance will be
used for each clutter class where the receiver clearance is not specified. This clearance will be taken into consideration when calculating diffraction. The default value is 20 m.
169

Forsk 2011
Diffraction multiplying factor: You can set the multiplying factor for the diffraction losses. The final diffraction
losses are determined by multiplying the diffraction losses calculated using the 3-obstacle Deygout method by the
Diffraction multiplying factor.
Receiver height per clutter class: You can set a height for the receiver for each clutter class. Because the WLL propagation model is designed for networks with immobile receivers, the receivers are often on top of buildings. This
option allows you to specify a height which will be added to the clutter class.
Receiver clearance per clutter class: You can set a clearance around the receiver for each clutter class. This clearance will be taken into consideration when calculating diffraction.
6. Click OK.
5.1.10 The Longley-Rice Propagation Model

Longley-Rice is a theoretical model suited for predictions in the 40-MHz band in flat areas. The Longley-Rice propagation
model uses the terrain profile to calculate propagation. However, the parameters of the Longley-Rice propagation model can
be set using distance and an additional loss value.
To set the parameters on the Longley-Rice propagation model:
3. Right-click Longley-Rice. The context menu appears.
6. Under Add to propagation loss, enter the formula that will be used to calculate additional losses (in flat terrain, a
value of "0" means a signal decreasing in a linear fashion as a function of distance). "dkm" in the formula is the distance
in kilometres from the transmitter.
7. Click OK.
5.1.11 The ITU 1546 Propagation Model

The ITU 1546 propagation model is based on the ITU-R P-1546-2 recommendations. This model is suited for predictions in the
30 to 3000 MHz band over distances from 1 to 1000 km. It is appropriate for point-to-area predictions such as broadcast and
land and maritime mobile services, and fixed services employing point-to-multipoint systems. It uses the terrain profile to
calculate propagation.
Because this propagation model is based on graphs giving the field strength as a function of distance provided in the ITU
recommendations for different operating frequencies, the only parameters you have to define for this model are:
the percentage of time during which the real field strength is higher than the signal level calculated by the model (1%,
10%, or 50% of the time), and
the type of path over which the signal level is to be predicted (land in urban or suburban zones, land other zones, or
sea).
To set the propagation model parameters:

6. Under Calculate Signal Level Exceeded During, select one of the following:
-
50% of the time

10% of the time
1% of the time
7. Under Type of Path, select one of the following:

-
Land (Urban or Suburban Zones)

Land (Other Zones)
Sea
8. Select Use clutter altitude if you want to take the height of the clutter into account in diffraction. The height of the
clutter will be taken from the Clutter Height folder, if clutter heights are available. Otherwise the average height of
each clutter class will be used when evaluating diffraction. If this box is unselected, the diffraction is evaluated using
only the DTM.
170

AT310_UMU_E0
9. Click OK.
For more information, see the Technical Reference Guide and the ITU-R P.1546 recommendation.
5.1.12 The Sakagami Extended Propagation Model

The Sakagami extended propagation model is based on a simplified version of the extended Sakagami-Kuboi propagation
model. The Sakagami extended propagation model is valid for frequencies above 3 GHz. Therefore, it is only available in
WiMAX 802.16e documents by default.
The Sakagami-Kuboi propagation model requires detailed information about the environment, such as the widths of the
streets where the receiver is located, the angles formed by the street axes and the directions of the incident waves, the
heights of the buildings close to the receiver, etc. The Sakagami-Kuboi propagation model is valid for frequencies below
2.2 GHz. Studies have shown that the Sakagami-Kuboi propagation model can be extended to frequencies higher than 3 GHz,
which also allows the input required by the model to be simplified. The same studies show that the path loss predicted by the
extended model is almost independent of the input parameters such as street widths and angles.
The path loss calculation formula of the Sakagami extended propagation model is similar to the formula of the Standard Propagation Model. In Atoll, this model is in fact a copy of the Standard Propagation Model with the following values assigned to
the K coefficients:
K Coefficient
Value Assigned
K1
65.4 (calculated for 3.5 GHz)
K2
40
K3
-30
K4
K5
K6
K7
-5
For more information on working with the Standard Propagation Model, see "The Standard Propagation Model" on page 156.
5.1.13 CrossWave Model

CrossWave is the Atoll version of the Orange Labs propagation model. This model is developed by Orange Labs and is distributed and supported by Forsk as an option to Atoll. This high performance universal propagation model is dedicated to any
wireless technologies, any propagation situations and environments. In addition, the model uses an automatic tuning using
CW measurements. Aven if automatic calibration can be run on it, the originally provided model has been statistically precalibrated using measurements from different countries and environment types where the Orange Group is present. As a
consequence, CrossWave benefits from Orange Labs experience in term of propagation modeling of basic components
(antenna and profile modelling) and automatic tuning process (multi-linear regression, neuronal networks, ...). Even with such
a complexity, several years of research focused not only on accurateness, but also on rapidity, versatility and robustness of
CrossWave model.
CrossWave models the three propagation phenomena which are:
Vertical diffraction
Horizontal guided propagation
Reflection on mountains
171

Forsk 2011
Figure 5.4: Propagation phenomena in CrossWave

CrossWave supports and technology (GSM, UMTS, WiMAX, LTE) and any frequency range (from 200 MHz to 5GHz). It also
applies on any type of cells (micro, mini and macro cells). Its domains of appliance is various since it can be used over any
type of environment (dense urban, urban, suburban, rural.) without any restriction.
Crosswave supports the same type of geo data files than the other propgation models available in Atoll (DTM, clutter classes,
clutter heights), but any additional raster file might be used with it and optionnally, it may be even more accurate by the use
of specific geo data maps such as:
3D building vectors (TAB)

Line vectors (TAB) for railway track predictions
For more information on CrossWave propagation model, please refer to its specific user manual.
5.1.14 Managing Propagation Models

The propagation models available for the current Atoll document can be found in the Propagation Models folder on the
Parameters tab of the Explorer window. You can manage the propagation models with the commands available on the
context menu.
To manage the propagation models of the current Atoll document:
3. Right-click the propagation model you want to manage. The context menu appears.
4. Select one of the following commands from the context menu:
-
Properties: The Properties dialogue appears. You can view the general information about the propagation model
on the General tab:
-
Name: The name of the propagation model, as displayed in the Propagation Models folder
Signature: The signature is assigned to the propagation model by Atoll. Each time you modify the parameters
of the selected propagation model, Atoll changes the signature. The signature of the propagation model used
to calculate a set of path loss matrices is stored with the matrices. This enables Atoll to verify the validity of
the path loss matrices.
When path loss matrices are not embedded in the Atoll document but are stored externally, the signature is
found in the MODEL_SIG field of the Pathloss.dbf file. The name of the propagation model used is found in the
MODEL_NAME field of the Pathloss.dbf file.
Description: You can enter a description or comments in this field.
Duplicate: The selected propagation model is duplicated. It appears in the Propagation Models folder with the
same name, preceded by "Copy of."
Copy: The selected propagation model is copied. You can paste it, with its current settings into a new Atoll document by opening the document, clicking the Parameters tab of the Explorer window and pressing CTRL+V.
If there is already a propagation model in the Atoll document with the same name as the
one you are trying to paste, Atoll will display a warning and will not allow you to overwrite
the existing propagation model.
172
Delete: The selected propagation model is deleted.

AT310_UMU_E0
Rename: You can enter a new name for the selected propagation model.
5.2 Defining Calculation Parameters

Atoll uses the propagation model defined for each transmitter to calculate losses along the transmitter-receiver path.
Depending on the type of prediction you make, Atoll either calculates the path loss at any point of the map in real time, or it
calculates a path loss matrix for each transmitter that will be considered in predictions. The path loss matrix contains a set of
path loss values calculated on each pixel over a specific area. It is calculated based on a set of three parameters defined for
the transmitter:
The propagation model

The calculation radius
The resolution.
By using a calculation radius, Atoll limits the scope of calculations to a defined area.
Atoll enables you to calculate two path loss matrices: a main and an extended one. By using two sets of calculation parameters, Atoll allows you to calculate high resolution path loss matrices closer to the transmitter with one propagation model,
while reducing calculation time and storage size by using an extended matrix with a lower resolution and another propagation
model. Atoll will calculate the extended matrix only if you define all three parameters: propagation model, calculation radius,
and resolution.
If you do not define a calculation radius for the main propagation model and if you do not assign an extended propagation
model, Atoll uses the prediction minimum threshold to define the calculation radius for each transmitter. However, this can
lead to lengthy calculation times. In that case, Atoll does not assign a calculation radius to transmitters.
This can be done if you let Atoll calculate the optimised main or extended calculation radii based on user-defined minimum
received signal levels. As an consequence, the storage of path loss matrices can drastically be reduced. See "Optimising Path
Loss Matrix Storage" on page 178 for more information.
When creating coverage predictions, you can define a coverage resolution that is different
from the resolution defined for the path loss matrices.
"Defining Calculation Parameters for One Transmitter" on page 173

"Defining the Same Calculation Parameters for a Group of Transmitters" on page 174
"Defining the Same Calculation Parameters for All Transmitters" on page 174
"Defining a Default Propagation Model" on page 175
"Defining a Default Resolution" on page 175.
5.2.1 Defining Calculation Parameters for One Transmitter

In Atoll, you can define calculation parameters, in other words, the propagation model, resolution, and calculation radius, for
each transmitter.
To define main and extended calculation parameters for one transmitter:
3. Right-click the transmitter to which you want to assign main and extended calculation parameters. The context menu
appears.
5. Click the Propagation tab.
6. Under Main Matrix:
-
Select a Propagation Model

Enter a Radius and Resolution.
7. If desired, under Extended Matrix:

-

8. Click OK. The selected calculation parameters will be used for the selected transmitter.
173

Forsk 2011
5.2.2 Defining the Same Calculation Parameters for a Group of

Transmitters
Transmitters that share the same parameters and environment will usually use the same propagation model and settings. In
Atoll, you can defining the same calculation parameters for several transmitters by first grouping them by their common
parameters and then defining the calculation parameters.
To define main and extended calculation parameters for a defined group of transmitters:
3. Select from the Group by submenu of the context menu the property by which you want to group the transmitters.
The objects in the folder are grouped by that property.
You can group transmitters by several properties by using the Group By button on the
Properties dialogue. For more information, see "Advanced Grouping" on page 66.

5. Right-click the group of transmitters for which you want to define main and extended calculation parameters. The context menu appears.
group.
For each transmitter, you can set the calculation parameters in the following columns:
-
Main Propagation Model

Main Calculation Radius
Main Resolution
Extended Propagation Model
Extended Calculation Radius
Extended Resolution
To enter the same values in one column for all transmitters in the table:
1. Enter the value in the first row in the column.
2. Select the entire column.
3. Right-click the selection and select Edit > Fill Down from the context menu or click the Fill Down button (
Table toolbar to copy the contents of the top cell of the selection into the other cells.
If you want to copy the contents of the last cell in the selection into all other cells, you can
right-click the selection and select Edit > Fill Up from the context menu or click the Fill Up
button (
) in the Table toolbar. For more information on working with tables in Atoll,
see "Working with Data Tables" on page 47.
5.2.3 Defining the Same Calculation Parameters for All

Transmitters
In Atoll, you can choose one set of calculation parameters and assign them to all transmitters.
To define the same calculation parameters for all transmitters:
-
174

) in the

AT310_UMU_E0

-

7. Click OK. The selected calculation parameters will be used for all transmitters.
Setting a different main or extended matrix on an individual transmitter as explained in
"Defining Calculation Parameters for One Transmitter" on page 173 will override this
entry. You can also optimise the path loss matrix radii as explained in "Optimising Path Loss
Matrix Storage" on page 178.
5.2.4 Defining a Default Propagation Model

When you assign a propagation model to a transmitter, you can choose "(Default Model)" from the list of the propagation
models available. Atoll will then calculate path loss using the default propagation model set for the project.
To define the default propagation model for the Atoll document:
2. Right-click the Predictions folder. The context menu appears.
4. Click the Predictions tab.
5. Select a Default Propagation Model from the list.
6. Click OK. The selected propagation model will be used for predictions for all transmitters whose main propagation
model is "(Default model)."
5.2.5 Defining a Default Resolution

When the resolution of the path loss matrix is not defined in the transmitter properties, Atoll uses the default resolution set
for the Atoll document. Additionally, this resolution is used as the default coverage resolution when you create a new coverage prediction.
To define the default resolution of the Atoll document:
4. Click the Predictions tab.
5. Enter a Default Resolution.
By setting an option in the atoll.ini file, you can set Atoll to use the currently defined
default resolution if you clear the value entered in the Resolution text box when you
create a coverage prediction. That way, if you have many coverage predictions, you can
change their resolution by changing the default resolution and recalculating the
coverage predictions. Atoll will then calculate them using the updated resolution. For
information on changing entries in the atoll.ini file, see the Administrator Manual.
6. Click OK.
5.3 Managing Path Loss Matrices

"Calculating Path Loss Matrices" on page 176

"Stopping Path Loss Matrix Calculation" on page 176
"Setting the Storage Location of Path Loss Matrices" on page 176
"Using Centralised Path Loss Matrices" on page 177
"Checking the Validity of Path Loss Matrices" on page 177
"Optimising Path Loss Matrix Storage" on page 178
"Tuning Path Loss Matrices Using Measurement Data" on page 179
"Exporting Path Loss Matrices" on page 185.
175

Forsk 2011
5.3.1 Calculating Path Loss Matrices

When you calculate a coverage prediction, Atoll automatically calculates non-existent and invalid path loss matrices before
calculating the prediction. This can take a lot of time if there are many path loss matrices that must be calculated. Consequently, you can calculate path loss matrices separately, when you have more time and computer resources available. In
multi-user environments, the administrator is responsible for shared path loss matrices and can calculate them separately.
Users can then base calculations on the updated shared path loss matrices.
When you calculate a coverage prediction, Atoll calculates only the non-existent and invalid path loss matrices that intersect
the rectangle containing the computation zone, whether or not the computation zone is visible. When you manually calculate
the path loss matrices as described in this section, Atoll does not take the computation zone into consideration; it calculates
all non-existent and invalid path loss matrices of active and filtered transmitters.
To calculate path loss matrices:
3. Select Calculations > Calculate Path Loss Matrices from the context menu. Atoll calculates all non-existent and invalid
path loss matrices of active and filtered transmitters.
You can calculate the non-existent and invalid path loss matrices for all transmitters, for a single transmitter, or for a defined
group of transmitters, by expanding the Transmitters folder right-clicking either the single transmitter or the defined group
of transmitters and selecting Calculations > Calculate Path Loss Matrices from the context menu.
You can prevent Atoll from calculating one or more path loss matrices by locking them. You
can lock path loss matrices using the Propagation tab of the Transmitters dialogue. You can
lock a single path loss matrix by selecting the check box in the Locked column, or more than
one by selecting several path loss matrices and then selecting Lock from the context menu.
5.3.2 Stopping Path Loss Matrix Calculation

Depending on the size of the path loss matrices, it can take a long time and a lot of computer resources to calculate them. If
necessary, you can stop calculation at any point.
To stop calculations:
Click the Stop Calculations button (

) in the toolbar. Atoll immediately stops all ongoing calculations. The results of
calculations that have already been completed, however, will be saved.
5.3.3 Setting the Storage Location of Path Loss Matrices

Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices
in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning projects,
embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case of large radioplanning projects, saving your path loss matrices externally will help reduce the size of the file and the use of computer
resources.
When you save the path loss matrices to an external directory, Atoll creates:
One file per transmitter with the extension LOS for its main path loss matrix
A DBF file with validity information for all the main matrices.
A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
To set the storage location of the path loss matrices:

4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss matrices:
-
Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are loading
path loss matrices from a shared location, where you store your changes to shared path loss matrices.
Click the button beside Private Directory (
) and select Embedded to save the path loss matrices in the Atoll
document, or Browse to select a directory where Atoll can save the path loss matrices externally.
176

AT310_UMU_E0
When you save the path loss files externally, the external files are updated as soon as
calculations are performed and not only when you save the Atoll document. In order to
keep consistency between the Atoll document and the stored calculations, you should
save the Atoll document before closing it, if you have updated the path loss matrices.
5. Click OK.
5.3.4 Using Centralised Path Loss Matrices

Using centralised path loss matrices is recommended in a multi-user environment when several users are working on the same
radio-planning document. In this case, the radio data is stored in a database. An administrator responsible for calculations
calculates the path loss matrices of the entire project and saves them in an external folder accessible to all users. This folder
is shared by all users and read only. When the user changes his radio data and recalculates the path loss matrices, the changes
to the path loss matrices are stored locally; the common path loss matrices are not modified. In other words, the user can
read the information from the shared path loss matrices but any changes he makes will be stored locally, either in the ATL file
or in a private external folder. Centralised path loss matrices will be recalculated by the administrator and will take into consideration the changes made by all users to the radio data.
For information on calculating path loss matrices, see "Calculating Path Loss Matrices" on page 176.
For information on setting the storage location for local path loss matrices, see "Setting the Storage Location of Path
Loss Matrices" on page 176.
For information on working in a multi-user environment, see the Administrator Manual.
To use pre-calculated path loss matrices:

4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for the shared path loss matrices:
-
Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a database and the common path loss matrices are stored in a directory that is accessible to all users. Any changes you
make will not be saved to this directory; they will be saved in the location indicated in Private Directory. The path
loss matrices in the shared directory are updated by a user with administrator rights based on the updated information in the database. For more information on shared directories, see The Administrator Manual.
The shared path loss matrices must be unlocked in order for users to be able to work
with them. The administrator can check whether shared path loss matrices are unlocked
or not in the Propagation tab of the Transmitters folders Properties dialogue.
5. Click OK.
5.3.5 Checking the Validity of Path Loss Matrices

Atoll automatically checks the validity of the path loss matrices when calculating any coverage prediction. If you want, you
can check whether the path loss matrices are valid before calculating a coverage prediction.
To check whether the path loss matrices are valid:
4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table.
5. Select one of the following display options:
-
Display all the matrices: All path loss matrices are displayed.
Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available Results table lists the following information for each displayed path loss matrix:
-
Transmitter: The name of the transmitter.

Locked: If the Locked check box is selected, the path loss matrix will not be updated even if the path loss matrices
are recalculated.
Valid: This is a boolean field indicating whether or not the path loss matrix is valid.
177

Forsk 2011
Reason for Invalidity: If the path loss matrix is indicated as being invalid, the reason is given here.
Size: The size of the path loss matrix for the transmitter.
File: If the path loss matrix is not embedded, the location of the file is listed.
Tuned: If the Tuned check box has been selected, the initial path loss matrix obtained by the propagation model
has been tuned by the use of real measurement points. See "Tuning Path Loss Matrices Using Measurement Data"
on page 179 for more information.
6. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue
appears (see Figure 5.5) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a
summary of the reasons for invalidity.
Figure 5.5: Path loss matrix statistics
5.3.6 Optimising Path Loss Matrix Storage

As explained in "Defining Calculation Parameters" on page 173, you can assign calculation radii for main and extended matrices, either for each specific transmitter, for a group of transmitters or for all the transmitters contained in a project. The path
loss matrices are then evaluted from the transmitter up to these calculation radii. In some cases, considering the minimum
signal required from a receiver point of view, the calculation of large path losses is useless and definitely has bad consequences in term of computation time and storage.
In Atoll, you can re-evaluate the calculation radii of existing path loss matrices by truncating values which would drive to
unnecessary received signal levels.
To optimise the calculation radius of the main and/or extended path loss matrices:
3. Select Calculations > Optimise Path Loss Matrices from the context menu.
4. Select for which matrices (main and/or extended) you want to re-evaluate their calculation radius
5. For each selected matrix, enter the minimum signal level which must result from the matrix reduction. After calculation, Atoll will filter out the path losses driving to signal levels lower than these thresholds.
6. Click Calculate. Atoll begins the process of calculation radius evaluations. Atoll first checks to see whether the path
loss matrices are valid before optimising their radius. If the path loss matrices are not valid, Atoll do not optimise their
radius.
7. Information relative to the path loss matrix radius calculation are listed in the Available Results table.
-
Display all results: All path loss matrices, including the ones which do not need optimisation, are displayed.
Display modified raddi only: Only path loss matrices for which the radius have to be optimised are displayed.
The Available Results table lists the following information for each displayed transmiitter:
-

Main Radius: radius of the main path loss matrix before optimisation.
Optimised Main Radius: radius of the main path loss matrix after optimisation.
Extended Radius: radius of the extended path loss matrix before optimisation.
Optimised Extended Radius: radius of the extended path loss matrix after optimisation.
9. Select the Commit check box for each transmitter you want to commit the opitmised radius (or radii). You can select
one, several or all the results and right click in order to select or unselect them for committing the results.
178

AT310_UMU_E0
10. Click Commit. All the transmitters whose Commit check box is selected have their calculation radius (or radii) modified. For extended matrices, if the calculation radii are changed, these are deleted and need to be recalculated with
the new radius values.
Invalid matrices cannot be optimised and have to be calculated prior to the optimisation process (see "Calculating Path Loss Matrices" on page 176 for more information). Invalid (or inexistent) matrices are displayed in red in the available results
list.
Even if the radius can be evaluated (and committed to the transmitter properties),
path losses are not optimised for locked matrices or matrices in a shared directory
(see "Using Centralised Path Loss Matrices" on page 177 for more information). In
those cases, matrices are displayed in grey in the available results list.
You can also optimise path loss matrices using the context menu of a transmitter
or group of transmitters. Only the matrices belonging to that selection will be optimised.
5.3.7 Tuning Path Loss Matrices Using Measurement Data

In Atoll, the path loss matrices are calculated using the propagation model and parameters defined as explained in "Defining
Calculation Parameters" on page 173. However, the results calculated by a propagation model can vary from actual measurements. Atoll allows you to use available drive test data paths and CW measurements to increase the accuracy of calculated
path loss matrices. When Atoll applies measurement data to path loss matrices, it first strips the effect of the antenna pattern
from the data. Therefore, if the antenna parameters change, the same measurement data can be used to tune the path loss
matrices because the effect of the antenna pattern is not present in the data.
Atoll uses the selected measurement data to tune a user-defined elliptical area around each measurement point. The main
axis of the ellipse is oriented in the direction of the transmitter or repeater.
Atoll smoothes the differences between tuned path loss matrix points and uncorrected path loss matrix points using an average error calculated between each measured value and the corresponding value in the path loss matrices.
When you use measurement data to tune path loss matrices, the results are stored
locally. If you are using shared path loss matrices, these results will be automatically
deleted when you make a calculation if the FullResyncPrivShared option is set in the
atoll.ini file. If you are using shared path loss matrices, you should disable this option
before tuning path loss matrices using measurement data. For more information, see the
When using measurement data to tune path loss matrices, you need to have valid path loss matrices (for more information
on path loss matrix validity, see "Managing Path Loss Matrices" on page 175):
1. Define the elliptical area around the measurement point as explained in "Defining the Area to be Tuned" on page 179.
2. Select the measurement data to be used to tune the path loss matrices:
-
CW Measurements: You select the CW measurements from the CW Measurements folder as explained in "Tuning
Path Loss Matrices Using CW Measurements" on page 181. The selected CW measurements will be used to tune
the path loss matrices calculated for the site on which the CW measurements were made.
Drive Test Data: You select the drive test data path from the Drive Test Data folder as explained in "Tuning Path
Loss Matrices Using Drive Test Data" on page 182. The selected measurements from drive test data path will be
used to tune the path loss matrices calculated for the selected transmitter.
Atoll replaces existing path loss matrices with the tuned matrices which remain valid as long as the radio configuration of the
network does not change. Atoll creates an external folder containing the catalogue of all the tuning paths as explained in
"Managing the Path Loss Tuning Points" on page 183. By activating or deactivating the tuning paths, you can select the tuning
path to be applied to the existing path loss matrices. Therefore, even if the path loss is recalculated, the path loss is automatically retuned using the active tuning paths.
5.3.7.1 Defining the Area to be Tuned

Atoll tunes the path loss matrices over an elliptical area around each measurement point. The main axis of the ellipse is
oriented in the direction of the transmitter.
To define the elliptical area around each measurement point:
2. Right-click the measurement type that you will use to tune the path loss matrices:
179

Forsk 2011
CW Measurements: If you are going to use CW measurements to tune the path loss matrices, right-click the CW
Measurements folder. The context menu appears.
Drive Test Data: If you are going to use drive test data to tune the path loss matrices, right-click the Drive Test
Data folder. The context menu appears.
4. Select the Path Loss Tuning Parameters tab (see Figure 5.6).
Figure 5.6: Defining the ellipse for tuning path loss matrices
5. Under Path Loss Tuning Ellipse, set the following parameters:
-
Radius of the Axis Parallel to the Profile: Enter the radius of the ellipse axis oriented in the same direction as the
transmitter (or repeater).
Radius of the Axis Perpendicular to the Profile: Enter the radius of the ellipse axis perpendicular to the transmitter (or repeater).
6. Click OK.
5.3.7.2 Defining Maximum Corrections and Thresholds on Path Loss Tuning

Path loss tuning is done in two steps, as described in the Technical Reference Guide:
1. Correction of the entire path loss matrix:
A mean error is calculated between each measured value and the corresponding pixel in the path loss matrix. Mean
error is calculated for each path loss matrix (main and extended) of each transmitter. This mean error is then applied
to all the pixels in the matrix. This tuning is done to smooth local corrections (step 2) of measured values and not the
tuned pixels themselves.
2. Local correction for each measured value.
In Atoll, you can set a tuning range in order to limit the tuning in the case the difference between the measurements and the
predicted measurements is too great. In addition, you can define a level under which the measured signal strength is not used
forpath loss tuning.
To define the tuning range and the measurement threshold for path loss tuning:
2. Right-click the measurement type that you will use to tune the path loss matrices:
-
CW Measurements: If you are going to use CW measurements to tune the path loss matrices, right-click the CW
Measurements folder. The context menu appears.
Drive Test Data: If you are going to use drive test data to tune the path loss matrices, right-click the Drive Test
Data folder. The context menu appears.
4. Select the Path Loss Tuning Parameters tab (see Figure 5.6).
5. Under Tuning Range, set the following parameters:
-
180
Maximum total correction (dB): Enter the maximum admissible mean error in step 1 of the path loss tuning
process.
Maximum local correction (dB): Enter the maximum admissible local error in step 2 of the path loss tuning
process.

AT310_UMU_E0
Minimum measurement threshold (dBm): Enter the measured signal level under which measurements are not
taken into account for the path loss tuning.
6. Click OK.
5.3.7.3 Tuning Path Loss Matrices Using CW Measurements

Atoll allows you to use available CW measurements to increase the accuracy of calculated path loss matrices.
To use CW measurements to tune path loss matrices:
2. Select how you want to tune the path loss matrices:
To tune the path loss matrix for a single transmitter:
a. Click the Expand button ( ) to expand the CW Measurement folder.
b. In the CW Measurement folder, click the Expand button ( ) to expand the site folder containing the CW measurement path you want to use to tune the path loss matrices.
c. Right-click the CW measurement path in the site folder. The context menu appears.
d. Select Tune Path Loss Matrices from the context menu. Atoll immediately begins optimising the path loss matrices for the transmitter on which the CW measurement was made. The progress is displayed in the Event Viewer
window.
To tune the path loss matrices for all transmitters:
a. Right-click the CW Measurement folder. The context menu appears.
b. Select Tune Path Loss Matrices from the context menu. The Measurement Path Selection dialogue appears (see
Figure 5.7).
Figure 5.7: Selecting all CW measurement paths

c. Under Measurement Paths, select All.
d. Click OK. Atoll begins optimising the path loss matrices for all transmitters on which CW measurements are available. The progress is displayed in the Event Viewer window.
To tune the path loss matrices for selected transmitters using selected CW measurement paths:
a. Right-click the CW Measurement folder. The context menu appears.
Figure 5.7).
c. Under Measurement Paths, select the option beside the list of CW measurements.
d. Select the check box corresponding to each transmitter for which you want to tune the path loss matrices.
For some transmitters, more than one CW measurement may exist. In this case, selecting the check box for the
transmitter will select all the CW measurements. If you do not want to use all CW measurements, click the Expand
button ( ) to expand the transmitter list and then select the single CW measurements you want to use.
e. Click OK. Atoll begins optimising the path loss matrices for all transmitters on which CW measurements are available. The progress is displayed in the Event Viewer window.
181

Forsk 2011
For repeaters, Atoll also tunes the path loss matrix of both the donor transmitter and the
repeater. The contribution of the repeater and donor to the measured value is calculated
based on the ratio of calculated values between the repeater signal and the donor signal.
Each evaluated contribution is then used as input to tune the path loss matrix of each
element. For more information, please refer to the Technical Reference Guide.
5.3.7.4 Tuning Path Loss Matrices Using Drive Test Data

Atoll allows you to use available drive test data paths to increase the accuracy of calculated path loss matrices.
To use drive test data to tune path loss matrices:
2. Select how you want to tune the path loss matrices:
To tune the path loss matrix using a single drive test data path:
a. Click the Expand button ( ) to expand the Drive Test Data folder.
b. Right-click the drive test data path you want to use to tune the path loss matrices. The context menu appears.
c. Select Tune Path Loss Matrices from the context menu. The Path Loss Tuning dialogue appears (see Figure 5.8).
Figure 5.8: Path Loss Tuning dialogue

d. Click the For the following transmitters list. The list opens.
e. Select the check box for each transmitter whose path loss matrix you want to tune.
f. Click the Select the measured signal levels list. The list opens.
g. For each transmitter selected fromthe For the following transmitters list, select the check box for each measured
signal strength that will be used to tune the path loss matrices.
h. Click OK. Atoll begins optimising the path loss matrices for the transmitter on which the CW measurement was
made. The progress is displayed in the Event Viewer window.
To tune the path loss matrices using all drive test data paths:
a. Right-click the Drive Test Data folder. The context menu appears.
Figure 5.9).
182

AT310_UMU_E0
Figure 5.9: Selecting all CW measurement paths

c. Under Measurement Paths, select All.
d. Click the For the following transmitters list. The list opens.
e. Select the check box for each transmitter whose path loss matrix you want to tune.
f.
Click the Select the measured signal levels list. The list opens.
g. For each transmitter selected fromthe For the following transmitters list, select the check box for each measured
h. Click OK. Atoll begins optimising the path loss matrices for the transmitter on which the CW measurement was
To tune the path loss matrices for selected transmitters using selected drive test data paths:
a. Right-click the Drive Test Data folder. The context menu appears.
Figure 5.9).
c. Under Measurement Paths, select the option beside the list of drive test data paths.
d. Select the check box corresponding to the drive test data you want to use to tune the path loss matrices.
e. Click the For the following transmitters list. The list opens.
f.
Select the check box for each transmitter whose path loss matrix you want to tune.
g. Click the Select the measured signal levels list. The list opens.
h. For each transmitter selected fromthe For the following transmitters list, select the check box for each measured
i.
Click OK. Atoll begins optimising the path loss matrices for the transmitter on which the CW measurement was
For repeaters, Atoll also tunes the path loss matrix of both the donor transmitter and the
repeater. The contribution of the repeater and donor to the measured value is calculated
based on the ratio of calculated values between the repeater signal and the donor signal.
Each evaluated contribution is then used as input to tune the path loss matrix of each
element. For more information, please refer to the Technical Reference Guide.
5.3.7.5 Managing the Path Loss Tuning Points

After tuning the path loss matrices is complete, Atoll creates a tuning measurement file for each transmitter and stores it in
a folder with the extension ".tuning". The .pts tuning file contains a header and a list of points defining the measurement data
path excluding the antenna losses which means that the measurement data remains valid even if the antenna parameters
change. A tuning file can contain several measurement paths, so that several calibrations can be applied successively on a path
183

Forsk 2011
loss matrix and stored in a single tuning file. All the tuning files are stored as a catalogue in the current project. Each single
tuning path can be activated or deactivated in order to be automatically applied to path loss matrices, even after recalculation.
Tuning files are stored in the same way as path loss matrices, as explained in "Setting the Storage Location of Path Loss Matrices" on page 176. They can be saved on a network and shared between users.
To manage the catalogue of the tuning path loss data:
-
-
Transmitter: The name of the transmitter or repeater.

Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices are
recalculated.
Tuned: If the check box is selected, the initial path loss matrix obtained by the propagation model has been tuned
by the use of real measurement data.
6. Select the tuning path loss matrices you want to manage using the available catalogue by holding CTRL and click the
corresponding line in the Available Results table and then right-clicking. The context menu appears.
7. Select Path Loss Tuning Points from the context menu. The Path Loss Tuning Points dialogue appears.
Figure 5.10: Path Loss Tuning Catalogue

-
All: All the tuning paths are displayed.

Active Only: Only the active tuning paths are displayed.
The Available Results table lists the following information for each displayed tuning path, assuming each transmitter
(or repeater) can have several ones coming from either the same or different measurement paths:
-
184
Transmitter: The name of the transmitter or repeater.

File: The location of the tuning file.
Name: The name of the tuning entry. Each entry is automatically named by Atoll based on the source of the tuning
data. You can edit the name by right-clicking the line and selecting Properties from the context menu.
Active: You can set each tuning path as active by selecting the check box. Only active entries are used to tune the
path loss matrices. When several entries are active and therefore applied to the same transmitter (or repeater),
the applicable tunings on the path loss matrix are realised in turn from the top to the bottom of the catalogue.
No. points: Displays the number of measurement points on the tuning path.
X Radius (m): Displays the radius of the ellipse axis oriented in the same direction as the transmitter (or repeater)
during the tuning session.
Y Radius (m): Displays the radius of the ellipse axis perpendicular to the transmitter (or repeater) during the tuning
session.
Gain (dB): Displays the gain of the measurement receiver.
Max. total correction (dB): Displays the user-defined maximum admissible total correction.
Max. local correction (dB): Displays the user-defined maximum admissible local correction.
Min. Threshold (dBm): Displays the user-defined level under which measurement values are not taken into
account for path loss tuning

AT310_UMU_E0
Total correction (dB): Displays the mean error between each measured value and its corresponding pixel in the
path loss matrix. This is the correction which is applied globally to all the matrices during the first step of path loss
tuning (For more information, please refer to the Technical Reference Guide).
Valid: This is a boolean field indicating whether or not the measurement path data (excluding the antenna information) are valid.
Reason for Invalidity: If the measurement path data is indicated as being invalid, the reason is given here.
Comments: Additional comments referring to the measurement entry are given in this field. You can edit the comment by right-clicking the line and selecting Properties from the context menu.
When path loss tuning entries are changed (e.g., activated or deleted) Atoll suggests deleting the corresponding path loss matrices.
You can import tuning files to replace an existing tuning or to benefit from a path loss tuning done by another user. The PTS
files are imported using a DBF file containing all the information relative to matrices and their tuning.
To import a path loss tuning catalogue:
5. Select the tuning path loss matrices for which you want to import tuning files by holding CTRL and click the corresponding line in the Available Results table and then right-clicking. The context menu appears.
6. Select Import Path Loss Tuning Catalogue from the context menu. The Open dialogue appears.
7. Select the DBF path loss tuning catalogue file you want to import.
8. Click Open. The existing PTS files are replaced by the ones referenced in the catalogue file. Any additional files in the
DBF catalogue file are added. You can work with the imported PTS files with the same options as files from a tuning
carried out in the current project.
5.3.8 Exporting Path Loss Matrices

You can export path loss matrices if you want to use the data in another application.
To export an Atoll documents path loss matrices:
5. Right-click the Available Results table and select Select All from the context menu.
6. Right-click the Available Results table and select Export from the context menu. The Calculation Results Export dialogue appears (see Figure 5.11).
7. Set the following export parameters:
-
Directory: Enter the directory you want to store the exported path loss matrices in or click the Browse button
(
) to navigate to it. The directory must already exist.
Exported Values: Select the values that are to be exported: Path Loss (dB), Signal Level (dBm), Signal Level (dBV),
or Signal Level (dBV/m).
Format: Select the format of the exported data: BIL Files (*.bil), TXT Files (*.txt) (Separator: tab), or CSV Files
(*.csv) (Separator: ";").
185

Forsk 2011
Figure 5.11: Exporting path loss matrices

8. Click OK to export the path loss matrices.
5.4 Predictions Available in Atoll

There are two types of predictions available in Atoll:
Point predictions using the Point Analysis tool: It allows you to predict, at any point on the map, the profile between
a reference transmitter and a receiver, the value of the signal levels of the surrounding transmitters, quality and interference analysis for any technology, scrambling code (resp. PN Offset) collision analysis in UMTS/HSPA (resp.
CDMA2000) projects.
Coverage predictions: You can calculate standard coverage predictions, coverage by transmitter, coverage by signal
level and overlapping zones, and specific coverage predictions such as interference predictions for GSM/GPRS/EDGE
projects or handover, service availability, etc. for UMTS, CDMA2000 and TD-SCDMA projects. Many customisation features on coverage predictions are available in order to make their analysis easier.
"Making Point Predictions" on page 186

"Making Coverage Predictions" on page 189.
5.4.1 Making Point Predictions

"Starting a Point Analysis" on page 186

"The Views of the Point Analysis Tool" on page 186
"Moving the Receiver on the Map" on page 188
"Taking Indoor Losses into Account" on page 188
"Taking Shadowing into Account in Point Analyses" on page 188.
5.4.1.1 Starting a Point Analysis

When you start a point analysis, Atoll automatically opens the Point Analysis window.
To make a point analysis:
1. Select Tools > Point Analysis. The Point Analysis window appears and the pointer changes (
receiver. This receiver is placed at the centre of the active map.
) to represent the
If a transmitter was already selected on the map, a line appears connecting the selected transmitter and the receiver.
2. Select the view of the Point Analysis window corresponding to the type of point prediction you want to make. For
information on the views available in the Point Analysis window, see "The Views of the Point Analysis Tool" on
page 186.
5.4.1.2 The Views of the Point Analysis Tool

You can access several views from the Point Analysis tool. These views enable you to make several different point predictions
and depend on the radio technology of the current document. When opening the Point Analysis Tool, you can select the
appropriate window from the list located at the top left part of a window:
The Profile View:

The Profile view (
and LTE projects.
186
) is available in the Point Analysis tool for GSM/GPRS/EDGE, CDMA, UMTS, TD-SCDMA, WiMAX,

AT310_UMU_E0
The Profile view of the Point Analysis tool displays the profile between a reference transmitter and the receiver. As
well, Atoll displays the signal level of the received signal from the selected transmitter. You can also display the path
loss or total losses from the selected transmitter. In this view, the results are calculated in real time.
The Reception View:

The Reception view (
) is available in the Point Analysis tool for GSM/GPRS/EDGE, CDMA, UMTS, TD-SCDMA,
WiMAX, and LTE projects. In Multi-RAT projects, there are as many Reception views as there are technologies.
The Reception view of the Point Analysis tool displays the predicted signal level from different transmitters in the
form of a bar chart, from the highest predicted signal level on the top to the lowest one on the bottom. The calculations are based on the path loss matrices. Each bar is displayed in the colour of the transmitter it represents.
In the map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they
represent. The best server for the pointer is the transmitter from which the pointer receives the highest signal level.
If you let the pointer rest on an arrow, the signal level received from the corresponding transmitter at the pointer location is displayed in the tip text.
The AS Analysis View:

The AS Analysis view (
) is available in the Point Analysis tool for CDMA and UMTS projects.
The AS Analysis view displays informa on on the pilot quality (Ec I0), which is the main parameter used to define the
mobile active set, the connection status, and the active set of the probe mobile.
The Interference View:

The Interference view (
) is available in the Point Analysis window for GSM/GPRS/EDGE projects, WiMAX, and LTE
projects. In a multi-RAT projects where GSM and LTE are present, there are one reception window for each of these
technologies.
The Interference view displays, in the form of a bar graph, the signal level of the selected transmitter, a black bar indicating the total interference experienced by the receiver, and bars representing the interference received from each
interferer.
In the map window, arrows from the receiver towards each transmitter are also displayed in the colour of the transmitters they represent. If you let the pointer rest on an arrow, the interference level received from the corresponding
transmitter at the receiver location will be displayed in the tip text along with information on the channel being interfered and the type of interference, i.e., co- or adjacent channel.
The PN Offset Collision View:

The PN Offset Collision view (
) is available in the Point Analysis tool for CDMA projects.
The PN Offset Collision view of the Point Analysis tool gives you information on the reception for any point on the
map where there is PN Offset collision.
The SC Collision View:

The SC Collision view (
) is available in the Point Analysis tool for UMTS projects.
The SC Collision view of the Point Analysis tool gives you information on reception for any point on the map where
there is scrambling code collision.
The Details View:

The Details view (
) is available in the Point Analysis tool for GSM/GPRS/EDGE, CDMA, UMTS, TD-SCDMA, WIMAX,
and LTE projects. In Multi-RAT projects, there are as many Results views as there are technologies.
The Details view displays the current position and height of the receiver, the clutter class it is situated on. In addition,
it also displays:
-
in GSM/GPRS/EDGE projects, you can select to display the results on a specific HCS layer (or all). You can also evaluate either C/I or C/I+N values where the interferences are due to any combination between adjacent channels,
co-channels or external sources. Atoll displays for each transmitter its BCCH signal level, the BCCH C/I, the most
interfered mobile station allocation (TRX, MAL or MAL-MAIO depending on the hopping mode) and its corresponding C/I.
in CDMA projects, you can select to display the results for a specific terminal, service, mobility, carrier, DL rate,
and UL rate. Atoll displays for each transmitter its signal level (or RSCP), its path loss, Ec/Io, C/I, DL and UL Eb/Nt
values, PN offsets.
in UMTS/HSPA projects, you can select to display the results for a specific terminal, service, mobility, carrier. Atoll
displays for each transmitter its signal level, Ec/Io, DL and UL Eb/Nt values, scrambling codes.
in TD-SCDMA projects, Atoll displays for each transmitter its signal level.
187

Forsk 2011
in WiMAX projects, you can select to display the results for a specific terminal, service, mobility. Atoll displays for
each transmitter its preamble index, its preamble signal C, C/N and I.
in LTE projects, you can select to display the results for a specific terminal, service, mobility. Atoll displays for each
transmitter its physical cell ID, its reference signal Level, its RSRP and its RS I.
5.4.1.3 Moving the Receiver on the Map

When you make a point analysis, the pointer (
of the receiver in several ways:
) represents the receiver in the map window. You can change the position
You can move the receiver manually

You can enter the coordinates of the new position
You can place the receiver on a selected site.
To change the position of the receiver manually:
Move the receiver to change the current position.

Click to place the receiver at the current position. You can move the receiver again by clicking it a second time.
To enter the coordinates of a position:

1. Right-click the receiver (
) in the map window. The context menu appears.
2. Select Coordinates from the context menu. The Receiver Position dialogue appears.
3. Enter or paste the X and Y coordinates of the position and click OK. The receiver moves to the specified position.
To place the receiver on a selected site:
1. Right-click the receiver (
) in the map window. The context menu appears.
2. Select Target Site from the context menu. The Target Site dialogue appears.
3. Select the site on which you want to place the receiver from the Name list and click OK. The receiver moves to the
specified position.
5.4.1.4 Taking Indoor Losses into Account

In Atoll you can calculate indoor predictions by taking indoor losses into consideration. You can define default indoor losses
for all clutter classes, or you can define different indoor losses for each clutter class so that the characteristics of each clutter
class are taken into consideration during calculations.
To take indoor losses into account when making a point analysis:
1. Click the option button (
dialogue appears.
) n the window you are using from the Point Analysis tool. The Calculation Options
2. Select the Indoor Coverage check box to add indoor losses to the total path loss.
5.4.1.5 Taking Shadowing into Account in Point Analyses

Shadowing, or slow fading, is signal loss along a path caused by obstructions not taken into consideration by the propagation
model. Even when a receiver remains in the same location or in the same clutter class, there are variations in reception due
to the surrounding environment.
Normally, the signal received at any given point is spread on a gaussian curve around an average value and a specific standard
deviation. If the propagation model is correctly calibrated, the average of the results it gives should be correct. In other words,
in 50% of the measured cases, the result will be greater and in 50% of the measured cases, the result will be worse.
Atoll uses a model standard deviation with the defined cell edge coverage probability to model the effect of shadowing and
thereby provide predictions that are reliable more than fifty percent of the time. The additional losses or gains caused by shadowing are known as the shadowing margin. The shadowing margin is added to the path losses calculated by the propagation
model.
For example, a properly calibrated propagation model calculates a loss leading to a signal level of -70 dBm. You have set a cell
edge coverage probability of 85%. If the calculated shadowing margin is 7 dB for a specific point, the target signal will be equal
to or greater than -77 dBm 85% of the time.
For informa on on se ng the model standard devia on and the C I standard devia ons for each clu er class or for all clutter
classes, see "Defining Clutter Class Properties" on page 119.
You can take shadowing into account when you are making a point analysis.
188

AT310_UMU_E0
To take shadowing into account when making a point analysis:

1. Click the option button (
dialogue appears.
) n the window you are using from the Point Analysis tool. The Calculation Options
2. Select the Shadowing Taken into Account check box and enter a Cell Edge Coverage Probability. Atoll calculates the
shadowing using the appropriate standard deviation defined per clutter class.
5.4.2 Making Coverage Predictions

A coverage prediction displays the results of defined coverage conditions. It is calculated using the path loss matrices and is
based on coverage conditions and coverage resolutions. After calculation, Atoll displays the results as a graphical representation of the pixels for which the defined coverage conditions are satisfied.
Atoll offers the following general coverage predictions, available for all technologies:
Coverage by transmitter
Coverage by signal level
Coverage by overlapping zones.
Atoll also offers technology-specific coverage predictions, described in the technology-specific chapters, for example:
Interference predictions in GSM/GPRS/EDGE projects

Coding scheme and throughput predictions for GPRS/EDGE
UMTS or CDMA2000 coverage predictions.
Atoll gives you a large flexibility over how the results of your coverage prediction are displayed. You can select which
attributes should be displayed on the map and how they are displayed. As well, you can define information to be displayed in
the legend, in the label, or in tooltips. Furthermore, Atoll also allows you to filter, sort, or group results before displaying them.
Atoll offers several options and ways enabling you to create and work with coverage predictions. In this section, the following
are explained:
"Creating Coverage Predictions" on page 189

"Defining the Storage Location of Coverage Prediction Results" on page 190
"Calculating Coverage Predictions" on page 191
"Saving Defined Coverage Predictions" on page 193.
5.4.2.1 Creating Coverage Predictions

In Atoll, you can create a coverage prediction using several different methods. Each method has its own advantages. For
example, you can create a new coverage prediction and set all of the parameters. Or you can base a new coverage prediction
on an existing one.
In this section, the following ways of creating a coverage prediction are explained:
5.4.2.1.1
"Creating a New Coverage Prediction" on page 189

"Duplicating a Coverage Prediction" on page 190
"Cloning a Coverage Prediction" on page 190.
Creating a New Coverage Prediction

When you create a new coverage prediction, you can select the type of coverage prediction and set all the parameters that
define it. The newly created coverage prediction is not automatically calculated.
To create a coverage prediction:
3. Select New from the context menu. The Prediction Types dialogue appears.
4. Select a coverage prediction from the Prediction Types dialogue and click OK. The coverage prediction Properties dialogue appears.
The Properties dialogue for a coverage prediction common to all technologies has three tabs:
-
General tab: You can rename the coverage prediction, define the coverage resolution, add comments, and define
where the coverage prediction results are stored. For information on defining the storage location of the coverage
prediction results, see "Defining the Storage Location of Coverage Prediction Results" on page 190.
You can also define group, sort, and filter criteria; these criteria will apply to the coverage display, not the results.
Condition tab: You can define the parameters of the coverage prediction.
Display tab: You can define how coverage prediction results will be displayed.
189

Forsk 2011
5. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it
later:
-
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately
OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the
Calculate button (
) on the Radio Planning toolbar.
For more information on calculating coverage predictions, see "Calculating Coverage Predictions" on page 191.
5.4.2.1.2
Duplicating a Coverage Prediction

You can create a new coverage prediction by duplicating an existing coverage prediction. When you duplicate an existing
coverage prediction, the coverage prediction you create will have the same coverage and display settings as the original one.
Duplicating a coverage prediction is a way to quickly create a new coverage prediction with the same settings as an original
one. The newly created coverage prediction is not automatically calculated.
To duplicate an existing coverage prediction:
2. Click the Expand button ( ) to expand the Predictions folder.
3. Right-click the coverage prediction you want to duplicate. The context menu appears.
4. Select Duplicate from the context menu. A new coverage prediction appears in the Predictions folder with the same
name as the original coverage prediction, preceded by "Copy of." The duplicated coverage prediction has the same
coverage and display settings as the original one.
For information on calculating coverage predictions, see "Calculating Coverage Predictions" on page 191.
5.4.2.1.3
Cloning a Coverage Prediction

You can create a new coverage prediction by cloning an existing coverage prediction. When you clone an existing coverage
prediction, Atoll creates a copy of the coverage prediction with the calculated coverage. You can then change the display,
providing that the selected parameter does not invalidate the calculated coverage prediction. Cloning is useful if the existing
coverage prediction has a display by discrete values (e.g., coverage by transmitter with a display by transmitter) and if you
want a new coverage prediction with another display by discrete values (e.g., display by RNC or BSC). In this case, Atoll maps
the results to the selected field and you do not need to recalculate the coverage prediction. On the other hand, cloning is not
relevant if you change the display from a discrete field to value intervals, in which case, you must recalculate the coverage
prediction.
To clone an existing coverage prediction:
3. Right-click the coverage prediction you want to clone. The context menu appears.
4. Select Clone from the context menu. A new coverage prediction appears in the Predictions folder with the same name
as the original coverage prediction, preceded by "Clone of." The cloned coverage prediction not only has the same
coverage and display settings as the original one, but keeps the same results as well.
5. Right-click the cloned coverage prediction. The context menu appears.
8. On the Display tab, keep the Display Type "Discrete Values" selected.
9. Select another value from the Field list to change the value displayed.
10. Click OK to apply the new display parameter.
5.4.2.2 Defining the Storage Location of Coverage Prediction Results

When you define and calculate a coverage prediction, Atoll stores the results in the Atoll document by default. You can,
however, choose to save the coverage prediction results externally. When you are working on extremely large projects, saving
results externally can help reduce the size of the Atoll document and the use of computer resources. These results can also
have been calculated on a server. You can also include in your document the results of coverage predictions that were calculated on a server. When the original coverage prediction is updated, the results displayed in the current document will also
be updated.
You can define the storage location of the results either before you calculate the coverage prediction or afterwards.
190

AT310_UMU_E0
You can not store externally the results of coverage predictions that are calculated by
transmitter instead of by level.
To define the storage location of coverage prediction results:

3. Right-click the coverage prediction for which you want to define the storage location of the results. The context menu
appears.
4. Select Properties from the context menu. The coverage predictions Properties dialogue appears.
5. On the General tab, click the button beside Folder (
-
) and select the storage location of the results:
Saving in the Atoll document: To store the results in the document, select Embedded.
Saving externally: To store the results externally, select the external storage location. Atoll creates a folder for the
results in the same folder with the Atoll document and gives it the name of the document, with the extension
"studies."
Sharing the results of another coverage prediction: To display the results of a coverage prediction that was calculated in a different document, select Connect to Results to navigate to the XML file describing the coverage prediction results.
Externally stored coverage prediction results can be imported as customised coverage predictions. For more information on
importing customised coverage predictions, see "Saving Defined Coverage Predictions" on page 193. For a detailed description of the XML file, see Studies.XML in the Administrator Manual.
5.4.2.3 Calculating Coverage Predictions

After you have defined a coverage prediction, you can calculate it. Atoll allows you to define and calculate coverage predictions in two separate steps. This enables you to create one or several coverage predictions at one time, and then calculate
them later, when you do not need the computer resources.
Before calculating one or more coverage predictions, you can create a computation zone. The computation zone is used to
define the area where Atoll carries out calculations. When you create a computation zone, Atoll carries out the calculation
for all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation
zone intersects a rectangle containing the computation zone. Therefore, it takes into consideration base stations inside and
base stations outside the computation zone if they have an influence on the computation zone. In addition, the computation
zone defines the area within which the coverage prediction results will be displayed.
The computation zone is taken into account whether or not it is visible. In other words, if you have drawn a computation zone,
it will be taken into account whether or not its visibility check box in the Zones folder of the Geo tab in the Explorer window
is selected. You will have to delete the computation zone if you no longer want to define an area for calculations.
When working with a large network, the computation zone allows you to restrict your coverage predictions to the part of the
network you are currently working on. By allowing you to reduce the number of base stations studied, Atoll reduces both the
time and computer resources necessary for calculations. As well, by taking into consideration base stations within the computation zone and base stations outside the computation zone but which have an influence on the computation zone, Atoll gives
you realistic results for base stations that are close to the border of the computation zone.
If there is no computation zone defined, Atoll makes its calculations on all base stations that are active and filtered and for
the entire extent of the geographical data available.
For information on creating a computation zone, see "Creating a Computation Zone" on page 34.
5.4.2.3.1
"Calculating Several Coverage Predictions" on page 191

"Calculating a Single Coverage Prediction" on page 192
"Forcing Calculations" on page 192
"Stopping Calculations" on page 192
"Locking Coverage Predictions" on page 192.
Calculating Several Coverage Predictions

When you have several defined coverage predictions, you can start calculation when you want and Atoll will calculate them
one after the other.
When you calculate coverage predictions, only unlocked coverage predictions are calculated. Unlocked coverage predictions
are displayed in the Predictions folder with the unlocked icon (
predictions, see "Locking Coverage Predictions" on page 192.
). For information on locking and unlocking coverage
191

Forsk 2011
To calculate created coverage predictions:
Click the Calculate button (

) in the toolbar. When you click the Calculate button, Atoll first calculates non-existent
and invalid path loss matrices and then, unlocked coverage predictions in the Predictions folder.
The progress of the calculations is displayed in the Event Viewer window.
After calculation, the results are displayed in the map window, if the coverage predictions visibility check box has
been selected.
5.4.2.3.2
Calculating a Single Coverage Prediction

To calculate a single coverage prediction:
3. Right-click the coverage prediction you want to calculate. The context menu appears.
4. Select Calculate from the context menu.
Atoll first calculates non-existent and invalid path loss matrices and then, the coverage prediction even if this one has
been previously locked.
been selected.
5.4.2.3.3
Forcing Calculations
When you have several defined coverage predictions, you can start calculation when you want and Atoll will calculate them
one after the other. Normally, Atoll only recalculates non-existent and invalid path loss matrices before calculating coverage
predictions. If you want, you can make Atoll recalculate all path loss matrices, including valid ones.
When you calculate coverage predictions, only unlocked coverage predictions are calculated. Unlocked coverage predictions
are displayed in the Predictions folder with the unlocked icon (
predictions, see "Locking Coverage Predictions" on page 192.
). For information on locking and unlocking coverage
To force Atoll to recalculate all path loss matrices before calculating coverage predictions:
Click the Force Calculate button (

) in the toolbar. When you click the Force Calculate button, Atoll first removes
existing path loss matrices, recalculates them and then calculates unlocked coverages predictions.
been selected.
5.4.2.3.4
Stopping Calculations
When Atoll has begun to calculate coverage predictions, you can stop the calculation at any given point. This can be useful if,
for example, you want to change one of the coverage predictions or if you dont want to calculate the coverage predictions
at that time.
To stop calculations:
5.4.2.3.5
Click the Stop Calculations button (

) in the toolbar. Atoll immediately stops all ongoing calculations. The results of
calculations that have already been completed, however, will be saved.
Locking Coverage Predictions

Coverage predictions are locked by default as soon as they have been calculated. Then, when you calculate new coverage
predictions, only unlocked coverage predictions are calculated. Locking a coverage prediction retains the information as calculated under given conditions (e.g., before a new base station is created or before optimising the network). It also saves time
by limiting unnecessary recalculation.
To prevent Atoll from automatically locking coverage predictions after calculating them,
you can set an option in the atoll.ini file. For information on setting options in the atoll.ini
file, see the Administrator Manual.
To lock a coverage prediction:
3. Right-click the coverage prediction you want to lock. The context menu appears.
192

AT310_UMU_E0
Unlocked coverage predictions are displayed in the Predictions folder with the unlocked icon (
4. Select Prediction Locked from the context menu.

The icon changes to the locked icon (
) and the Prediction Locked item in the context menu now appears checked.
The coverage prediction is now locked and will not be calculated when the Calculate button in the toolbar is clicked.
However, if you select Calculate from the coverage predictions context menu, Atoll will first unlock the coverage
prediction and then calculate it.
You can lock all unlocked coverage predictions using the Predictions folders context menu.
5.4.2.3.6
Unlocking Coverage Predictions

Coverage predictions are locked by default as soon as they have been calculated. You can unlock a single coverage prediction.
To unlock a coverage prediction:
3. Right-click the coverage prediction you want to unlock. The context menu appears.
Locked coverage predictions are displayed in the Predictions folder with the locked icon (
).
4. Select Prediction Locked from the context menu.

The icon changes to the unlocked icon (
) and the Prediction Locked item in the context menu is no longer selected.
You can unlock all locked coverage predictions using the Predictions folders context menu.
5.4.2.4 Saving Defined Coverage Predictions

Once you have defined a coverage prediction, you can use it again in other Atoll documents, either by using the coverage
prediction to create a customised coverage prediction or by saving its coverage and display parameters in a user configuration.
5.4.2.4.1
"Saving a Coverage Prediction as a Customised Coverage Prediction" on page 193

"Saving a Defined List of Predictions in a User Configuration File" on page 194.
Saving a Coverage Prediction as a Customised Coverage Prediction

Once you have defined a coverage prediction, you can use it as a customised coverage prediction. This coverage prediction
will be available to you in the Prediction Types dialogue the next time you want to create a new coverage prediction. The
initial parameters of the coverage prediction will be the same as the coverage prediction it is based on but, when you select
it in the Prediction Types dialogue, Atoll allows you to modify them.
To save a coverage prediction as a customised coverage prediction:
3. Right-click the coverage prediction you want to save as a customised coverage prediction. The context menu appears.
4. Select Save as Customised Prediction from the context menu. The Save As dialogue appears.
In the Save As dialogue, Atoll proposes a name and location for the XML file that will contain the customised coverage
prediction. You can accept the default values or you can change the name and save the XML file in any folder you have
write access to.
5. Click Save. Atoll saves the coverage prediction in the selected XML file.
The next time you create a new coverage prediction, the customised coverage prediction will be available at the bottom of
the list, under the full path and file name of the XML file (see Figure 5.12). If you have other XML template files, you can click
the Customised Predictions button and select it in the Open dialogue.
193

Forsk 2011
Figure 5.12: Prediction Types dialogue

Coverage predictions stored in the XML template files are also directly available in the Calculations menu of the context
menus of the Transmitters folder, of a group of transmitters, and of a single transmitter.
In a multi-user environment, the administrator can make customised predictions available for all the users by saving the XML
file in the Atoll installation directory. For more information, see the Administrator Manual.
5.4.2.4.2
Saving a Defined List of Predictions in a User Configuration File

You can save the defined coverage predictions in the Predictions folder in a user configuration file. You can then import this
user configuration file into another Atoll document. All the coverage predictions in the user configuration will then be available in the Predictions folder of the new Atoll document and can be calculated.
To export a user configuration with the coverage predictions in the Predictions folder:
1. Select Tools > User Configuration > Save. The User Configuration dialogue appears.
2. Select the Prediction List check box, as well as the check box of any other information you want to save as part of the
user configuration.
4. Enter a File name for the user configuration file and click Save. The folder configuration is saved.
For information on loading the user configuration into another Atoll document, see "Loading a User Configuration" on
page 77.
5.4.2.5 Calculating Indoor Coverage

In Atoll you can calculate indoor coverage by taking the indoor losses into consideration. Indoor losses are defined per clutter
class. You can define a default indoor losses value for all clutter classes. Or, you can define a different indoor losses value for
each clutter classes, to take the characteristics of each clutter class into consideration.
To calculate indoor coverage when making a coverage prediction:
When creating the coverage prediction, select the Indoor Coverage check box on the Condition tab of the coverage
predictions Properties dialogue. The indoor losses defined for the clutter classes will be added to the total path loss
for each pixel.
5.4.2.6 Taking Shadowing into Account

Shadowing, or slow fading, is signal loss along a path that is caused by obstructions not taken into consideration by the propagation model. Even when a receiver remains in the same location or in the same clutter class, there are variations in reception due to the surrounding environment.
thereby create coverage predictions that are reliable more than fifty percent of the time. The additional losses or gains caused
by shadowing are known as the shadowing margin. The shadowing margin is added to the path losses calculated by the propagation model.
194

AT310_UMU_E0
For informa on on se ng the model standard devia on and the C I standard devia ons for each clu er class or for all clutter
classes, see "Defining Clutter Class Properties" on page 119.
-
When creating the coverage prediction, select the Shadowing Taken into Account check box. Then, you can define
the Cell Edge Coverage Probability.
5.
195

196
Forsk 2011
Chapter 6
UMTS HSPA Networks
This chapter provides the information to use Atoll to
design, analyse, and optimise a UMTS HSPA network.
"Designing a UMTS Network" on page 199
"Planning and Optimising UMTS Base Stations" on

page 200
"Studying Network Capacity" on page 297
"Optimising Network Parameters Using the ACP" on

page 330
"Verifying Network Capacity" on page 379
"Co-planning UMTS Networks with Other Networks"

on page 390
"Advanced Configuration" on page 409

Chapter 6: UMTS HSPA Networks
198
Forsk 2011

AT310_UMU_E0
6 UMTS HSPA Networks

Atoll enables you to create and modify all aspects of a UMTS HSPA (HSDPA and HSUPA) network. Once you have created the
network, Atoll offers many tools to let you verify the network. Based on the results of your tests, you can modify any of the
parameters defining the network.
The process of planning and creating a UMTS HSPA network is outlined in "Designing a UMTS Network" on page 199. Creating
the network of base stations is explained in "Planning and Optimising UMTS Base Stations" on page 200. Allocating neighbours
and scrambling codes is also explained. In this section, you will also find information on how you can display information on
base stations on the map and how you can use the tools in Atoll to study base stations.
In "Studying Network Capacity" on page 297, using traffic maps to study network capacity is explained. Creating simulations
using the traffic map information and analysing the results of simulations is also explained.
Using drive test data paths to verify the network is explained in "Verifying Network Capacity" on page 379. Filtering imported
drive test data paths, and using the data in coverage predictions is also explained.Filtering imported drive test data paths, and
using the data in coverage predictions is also explained.
6.1 Designing a UMTS Network

Figure 6.1 depicts the process of planning and creating a UMTS HSPA network.
1
Open an Existing Project
or Create a New One
2
Network Configuration
- Add Network Elements
- Change Parameters
3
Basic Predictions
(Best Server, Signal Level)
4
Neighbour Allocation
5a
Traffic Maps
5c
5b
Monte-Carlo
Simulations
User-defined values
5
Cell Load
Conditions
6a
6
UMTS/HSPA Predictions
Prediction Study Reports

7
Scrambling Code Plan
Figure 6.1: Planning a UMTS network - workflow

The steps involved in planning a UMTS HSPA network are described below. The numbers refer to Figure 6.1.
1. Open an existing radio-planning document or create a new one (
-
).
You can open an existing Atoll document by selecting File > Open.
Creating a new a new Atoll document is explained in Chapter 2: Starting an Atoll Project.
2. Configure the network by adding network elements and changing parameters (
).
You can add and modify the following elements of base stations:
-
"Creating or Modifying a Site" on page 209

"Creating or Modifying a Transmitter" on page 209
"Creating or Modifying a Cell" on page 210.
199

Forsk 2011
You can also add base stations using a base station template (see "Placing a New Station Using a Station Template" on
page 210).
3. Carry out basic coverage predictions (
-
"Making a Point Analysis to Study the Profile" on page 227

"Studying Signal Level Coverage" on page 229 and "Signal Level Coverage Predictions" on page 237
4. Allocate neighbours, automatically or individually (

-
).
"Planning Neighbours" on page 274.
5. Before making more advanced coverage predictions, you need to define cell load conditions (
).
You can define cell load conditions in the following ways:

-
You can generate realistic cell load conditions by creating a simulation based on a traffic map ( 5a and 5b ) (see
"Studying Network Capacity" on page 297).
You can define them manually either on the Cells tab of each transmitters Properties dialogue or in the Cells table
(see "Creating or Modifying a Cell" on page 210) (
5c
).
6. Make UMTS-specific coverage predictions using the defined cell load conditions (
-
).
"UMTS-Specific Predictions" on page 251

"HSDPA Quality and Throughput Analysis" on page 267
"HSUPA Quality and Throughput Analysis" on page 269.
7. Allocate scrambling codes (

-
).
"Planning Scrambling Codes" on page 288.
6.2 Planning and Optimising UMTS Base Stations

As described in Chapter 2: Starting an Atoll Project, you can start an Atoll document from a template, with no sites, or from a
database with a set of sites. As you work on your Atoll document, you will still need to create sites and modify existing ones.
In Atoll, a site is defined as a geographical point where one or more transmitters are located. Once you have created a site,
you can add transmitters. In Atoll, a transmitter is defined as the antenna and any other additional equipment, such as the
TMA, feeder cables, etc. In a UMTS project, you must also add cells to each transmitter. A cell refers to the characteristics of
a carrier on a transmitter.
Antenna
- Azimuth
- Mechanical tilt
TMA
Antenna
- Height
Feeder Cable
Transmitter
- Noise figure
- Power
Site
- X, Y coordinates
Figure 6.2: A transmitter

Atoll lets you create one site, transmitter, or cell at a time, or create several at once by creating a station template. Using a
station template, you can create one or more base stations at the same time. In Atoll, a base station refers to a site with its
transmitters, antennas, equipment, and cells.
Atoll allows you to make a variety of coverage predictions, such as signal level or transmitter coverage predictions. The results
of calculated coverage predictions can be displayed on the map, compared, or studied.
200

AT310_UMU_E0
Atoll enables you to model network traffic by allowing you to create services, users, user profiles, environments, and terminals. This data can be then used to make quality predictions, such as effective service area, noise, or handover status predictions, on the network.
"Creating a UMTS Base Station" on page 201

"Creating a Group of Base Stations" on page 218
"Modifying Sites and Transmitters Directly on the Map" on page 219
"Display Tips for Base Stations" on page 219
"Creating a Dual-Band UMTS Network" on page 220
"Creating a Repeater" on page 220
"Creating a Remote Antenna" on page 224
"Setting the Working Area of an Atoll Document" on page 226
"Studying a Single Base Station" on page 227
"Studying Base Stations" on page 231
"Planning Neighbours" on page 274
"Planning Scrambling Codes" on page 288.
6.2.1 Creating a UMTS Base Station

When you create a UMTS site, you create only the geographical point; you must add the transmitters and cells afterwards.
The site, with the transmitters, antennas, equipment, and cells is called a base station.
In this section, each element of a base station is described. If you want to add a new base station, see "Placing a New Station
Using a Station Template" on page 210. If you want to create or modify one of the elements of a base station, see "Creating
or Modifying a Base Station Element" on page 208. If you need to create a large number of base stations, Atoll allows you to
import them from another Atoll document or from an external source. For information, see "Creating a Group of Base
Stations" on page 218.
This section explains the various parts of the base station process:
"Definition of a Base Station" on page 201

"Creating or Modifying a Base Station Element" on page 208
"Placing a New Station Using a Station Template" on page 210
"Managing Station Templates" on page 211
"Duplicating an Existing Base Station" on page 218.
6.2.1.1 Definition of a Base Station

A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. You will usually create a new base station using a station template, as described in "Placing a New Station Using a
Station Template" on page 210. This section describes the following elements of a base station and their parameters:
"Site Description" on page 202

"Transmitter Description" on page 202
"Cell Definition" on page 205.
201

6.2.1.1.1
Forsk 2011
Site Description
The parameters of a site can be found in the sites Properties dialogue. The Properties dialogue has two tabs:
The General tab (see Figure 6.3):
Figure 6.3: New Site dialogue

-
Name: Atoll automatically enters a default name for each new site. You can modify the default name here. If you
want to change the default name that Atoll gives to new sites, see the Administrator Manual.
Position: By default, Atoll places the new site at the centre of the map window. You can modify the location of
the site here.
While this method allows you to place a site with precision, you can also place sites using
the mouse and then position them precisely with this dialogue afterwards. For
information on placing sites using the mouse, see "Moving a Site Using the Mouse" on
page 21.
Altitude: The altitude, as defined by the DTM for the location specified under Position, is given here. You can
specify the actual altitude under Real, if you want. If an altitude is specified here, Atoll will use this value for calculations.
Comments: You can enter comments in this field if you want.
The Equipment tab:

-
Max Number of Uplink Channel Elements: The maximum number of physical radio resources for the current site
in the uplink. By default Atoll enters the maximum possible (256).
Max Number of Downlink Channel Elements: The maximum number of physical radio resources for the current
site in the downlink. By default Atoll enters the maximum possible (256).
Max Iub Uplink Backhaul Throughput: The maximum Iub backhaul throughput for the current site in the uplink.
Max Iub Downlink Backhaul Throughput: The maximum Iub backhaul throughput for the current site in the downlink.
Equipment: You can select equipment from the list. To create new site equipment, see "Creating Site Equipment"
on page 413.
If no equipment is assigned to the site, Atoll considers the following default values:
-
6.2.1.1.2
Rake efficiency factor = 1

MUD factor = 0
Carrier selection = UL minimum noise
Downlink and uplink overhead resources for common channels = 0
The option AS Restricted to Neighbours is not selected, and Atoll uses one channel element on the uplink or
downlink for any service during power control simulation.
Transmitter Description
The parameters of a transmitter can be found in the transmitters Properties dialogue. When you create a transmitter, the
Properties dialogue has two tabs: the General tab and the Transmitter tab. Once you have created a transmitter, its Properties dialogue has three additional tabs: the Cells tab (see "Cell Definition" on page 205), the Propagation tab (see Chapter 5:
Working with Calculations in Atoll), and the Display tab (see "Display Properties of Objects" on page 23).
202

AT310_UMU_E0
The General tab:

-
Name: By default, Atoll names the transmitter after the site it is on, adding an underscore and a number. You can
enter a name for the transmitter, but for the sake of consistency, it is better to let Atoll assign a name. If you want
to change the way Atoll names transmitters, see the Administrator Manual.
Site: You can select the Site on which the transmitter will be located. Once you have selected the site, you can
click the Browse button (
) to access the properties of the site on which the transmitter will be located. For
information on the site Properties dialogue, see "Site Description" on page 202. You can click the New button to
create a new site on which the transmitter will be located.
Frequency Band: You can select a Frequency Band for the transmitter. Once you have selected the frequency
band, you can click the Browse button (
) to access the properties of the band. For information on the frequency band Properties dialogue, see "Defining Frequency Bands" on page 409.
Shared Antenna: This flag is used to identify the transmitters of different technologies, located at the same site,
that share antennas. These transmitters may be other technology transmitters in a 3GPP Multi-RAT document or
in a linked co-planning document. The flag must be the same for all such transmitters. Shared antennas have the
same position relative to the site (Dx, Dy), height, azimuth, and mechanical tilt, for all the transmitters that use
them. Atoll automatically synchronises changes made to these parameters for one transmitter to all other transmitters that share the antenna. For more information on co-planning, see "Co-planning UMTS Networks with
Other Networks" on page 390.
Under Antenna Position, you can modify the position of the antennas (main and secondary):
-
Relative to Site: Select this option if you want to enter the antenna positions as offsets with respect to the site
location, and then enter the x-axis and y-axis offsets, Dx and Dy, respectively.
Coordinates: Select this option if you want to enter the coordinates of the antenna, and then enter the x-axis
and y-axis coordinates of the antenna, X and Y, respectively.
The Transmitter tab (see Figure 6.4):
Figure 6.4: Transmitter dialogue - Transmitter tab

-
Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are displayed
in red in the Transmitters folder of the Network tab.
203

Forsk 2011
Only active transmitters are taken into consideration during calculations.
Transmission/Reception: Under Transmission/Reception, you can see the total losses and the noise figure of the
transmitter. Atoll calculates losses and noise according to the characteristics of the equipment assigned to the
transmitter. Equipment can be assigned by using the Equipment Specifications dialogue which appears when you
click the Equipment button.
On the Equipment Specifications dialogue (see Figure 6.5), the equipment you select and the gains and losses you
define are used to initialise total transmitter UL and DL losses:
-
TMA: You can select a tower-mounted amplifier (TMA) from the list. You can click the Browse button (
) to
access the properties of the TMA. For information on creating a TMA, see "Defining TMA Equipment" on
page 148.
Feeder: You can select a feeder cable from the list. You can click the Browse button (
) to access the properties of the feeder. For information on creating a feeder cable, see "Defining Feeder Cables" on page 148.
Transmitter: You can select transmitter equipment from the Transmitter list. You can click the Browse button
(
) to access the properties of the transmitter equipment. For information on creating transmitter equipment, see "Defining Transmitter Equipment" on page 148.
Feeder Length: You can enter the feeder length at transmission and reception.
Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value you enter
must be positive.
Receiver Antenna Diversity Gain: You can enter a receiver antenna diversity gain. The value you enter must
be positive.
Figure 6.5: The Equipment Specifications dialogue

Any loss related to the noise due to a transmitters repeater is included in the calculated
losses. Atoll always takes the values in the Real boxes into consideration in prediction even
if they are different from the values in the Computed boxes. The information in the real
Noise Figure reception box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real Total Losses at transmission and
reception and the real Noise Figure at reception if you want. Any value you enter must be
positive.
-
Antennas:
-
Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added to
the altitude of the site as given by the DTM. If the transmitter is situated on a building, the height entered must
include the height of building.
Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the Browse
button (
) to access the properties of the antenna. Clicking the Select button opens a dialogue displaying
all the possible antennas based on the same physical antenna as the currently selected one. Selecting the Electrical tilt of the antenna model displays the appropriate antennas under Available Antennas. Selecting the
antenna under Available Antennas and clicking OK assigns the antenna to the transmitter. The other fields,
Azimuth, Mechanical Downtilt, and Additional Electrical Downtilt, display additional antenna parameters.
204

AT310_UMU_E0
The Additional Electrical Downtilt may be made accessible through an option in

For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
The mechanical and additional electrical downtilts defined for the main antenna
are also used for the calculations of smart antennas.
Under Diversity, you can select the number of transmission and reception antenna ports used for MIMO (No.
of ports). MIMO systems are supported by some HSDPA bearers (following improvements introduced by
release 7 of the 3GPP UTRA specifications, referred to as HSPA+). For more information on how the number
of antenna ports are used, see "Multiple Input Multiple Output Systems" on page 417.
R99 bearers only support transmit and receive diversities. You can define the transmit diversity method from
the Transmission list when more than one transmission antenna port is available. The receive diversity method depends on the number of reception antenna ports selected (2RX for two reception antenna ports and 4RX
for four reception antenna ports).
Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column and enter
their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power, which is the percentage of
power reserved for this particular antenna. For example, for a transmitter with one secondary antenna, if you
reserve 40% of the total power for the secondary antenna, 60% is available for the main antenna.
6.2.1.1.3

For information on working with data tables, see "Working with Data Tables" on
page 47.
Cell Definition
In Atoll, a cell is defined as a carrier, with all its characteristics, on a transmitter; the cell is the mechanism by which you can
configure a UMTS multi-carrier network. In other words, a transmitter has one cell for every carrier.
When you create a transmitter, Atoll automatically creates one cell for the transmitter. The following explains the parameters
of a UMTS cell, including the parameters for HSDPA and HSUPA functionality. As you create a cell, Atoll calculates appropriate
values for some fields based on the information you have entered. You can, if you want, modify these values.
The properties of a UMTS cell are found on Cells tab of the Properties dialogue of the transmitter to which it is assigned.
The following HSDPA options apply to all the cells of the transmitter:
Inter-Carrier Power Sharing: You can enable power sharing between cells by selecting the Inter-Carrier Power Sharing
check box under HSDPA and entering a value in the Maximum Shared Power box. In order for Inter-Carrier Power
Sharing to be available, you must have at least one HSDPA carrier with dynamic power allocation.
Inter-Carrier Power Sharing enables the network to dynamically allocate available power from R99-only and HSDPA
carriers among HSDPA carriers.
When you select Inter-Carrier Power Sharing and you define a maximum shared power, the Max Power of each cell
is used to determine the percentage of the transmitter power that the cell cannot exceed.
The most common scenario is where you have R99-only cells that are not using 100% of their power and can share it
with an HSDPA carrier. To use power sharing efficiently, you should set the Max Power of the HSDPA cells to the same
value as the Maximum Shared Power. For example, if the Maximum Shared Power is defined as 43 dBm, the Max
Power of all HSDPA cells should be set to 43 dBm in order to be able to use 100% of the available power. In this case,
all of an R99 cells unused power can be allocated to the HSDPA cell.
Under Multi-cell, the following dual-cell HSDPA options are available:

-
Mode: The multi-cell HSDPA mode. You can activate dual-cell HSDPA support for the transmitter. When dual-cell
HSDPA is active, HSDPA users can simultaneously connect to two HSDPA cells of the transmitter for data transfer,
i.e., users of dual-cell HSDPA receive the HS-DSCH on two separate carriers. The R99 A-DPCH bearer is still transmitted on one of the two cells, which is called the anchor cell.
A dual-cell HSDPA user can be assigned two different HSDPA bearers in the two cells, depending on separate CQI
values.
Scheduler Algorithm: The scheduling technique that will be used to rank the HSDPA users to be served.
The sheduler manages a single queue of users at the Node B. All users belonging to the transmitter, i.e., dual-cell
HSDPA and single-carrier HSDPA users, are ranked together in a unique list. Dual-cell HSDPA users are considered
twice in the list as they may be assigned two different HSDPA bearers in the two cells.
205

Forsk 2011
Atoll supports the following algorithms:

-
Max C/I: "n" HSDPA users (where "n" corresponds to the sum of the maximum numbers of HSDPA users defined for all HSDPA cells) are scheduled in the same order as in the simulation (i.e., in random order). Then,
they are sorted in descending order by the channel quality indicator (CQI).
Round Robin: HSDPA users are scheduled in the same order as in the simulation (i.e., in random order).
Proportional Fair: "n" HSDPA users (where "n" corresponds to the sum of the maximum numbers of HSDPA
users defined for all HSDPA cells) are scheduled in the same order as in the simulation (i.e., in random order).
Then, they are sorted in descending order according to a random parameter which corresponds to a combination of the user rank in the simulation and the channel quality indicator (CQI).
MUG=f(No. Users): The multi-user diversity gain graph as a function of the number of users. The average cell
throughput is higher with multiple users than with a single user. It is used to calculate the peak gross throughput
per cell when the scheduling algorithm is "Proportional Fair".
The MUG graph is only available if you have set the peak HSDPA throughput option in the atoll.ini file. For more
In transmitters that support multi-cell HSDPA, the multi-cell HSDPA scheduler algorithm and MUG graph are used in
calculations instead of the HSDPA scheduler algorithms and MUG graphs set per cell.
The following parameters can be set for each individual cell of the transmitter:
Name: By default, Atoll names the cell after its transmitter, adding the carrier number in parentheses. If you change
transmitter name or carrier, Atoll does not update the cell name. You can enter a name for the cell, but for the sake
of consistency, it is better to let Atoll assign a name. If you want to change the way Atoll names cells, see the Administrators Manual.
ID: You can enter an ID for the cell. This is a user-definable network-level parameter for cell identification.
Carrier: The number of the carrier.
Active: If this cell is to be active, you must select the Active check box.
Max Power (dBm): The maximum available downlink power for the cell.
Pilot Power (dBm): The pilot power.
SCH power (dBm): The average power of both the synchronisation channels (P-SCH and S-SCH).
The SCH power is only transmi ed 1 10 of the me. Consequently, the value entered for
the SCH power should only be 1 10 of its value when transmi ed, in order to respect its
actual interference on other channels.
Other CCH power (dBm): The power of other common channels (P-CCPCH, S-CCPCH, AICH).
AS Threshold (dB): The ac ve set threshold. It is the Ec I0 margin in comparison with the Ec I0 of the best server. It is
used to determine which cells, apart from the best server, will be part of the active set.
DL Peak Rate per User (kbps): The downlink peak rate per user in kbps. The DL peak rate per user is the maximum
connection rate in the downlink for a user. The DL and UL peak rates are taken into account during power control simulation.
UL Peak Rate per User (kbps): The uplink peak rate per user in kbps. The UL peak rate per user is the maximum connection rate in the uplink for a user. The DL and UL peak rates are taken into account during power control simulation.
Max DL Load (% Pmax): The percentage of the maximum downlink power (set in Max Power) not to be exceeded. This
limit will be taken into account during the simulation if the option DL Load is selected. If the DL load option is not
selected during a simulation, this value is not taken into consideration.
Max UL Load Factor (%): The maximum uplink load factor not to be exceeded. This limit can be taken into account
during the simulation.
Total Power (dBm or %): The total transmitted power on downlink is the total power necessary to serve R99 and
HSDPA users. This value can be a simulation result or can be entered by the user.
By default, the total power is set as an absolute value. You can set this value as a percentage of the maximum power of the cell by right-clicking the UMTS Network Settings folder
on the Parameters tab of the Explorer window and selecting Properties from the context
menu. Then, on the Global Parameters tab of the Properties dialogue, under DL Load, you
can select % Pmax. The total power value is automatically converted and set as a percentage of the maximum power.
206
UL Load Factor (%): The uplink cell load factor. This factor corresponds to the ratio between the uplink total interference and the uplink total noise. The uplink cell load factor is a global value and includes the inter-technology uplink
interference. This value can be a simulation result or can be entered by the user.
UL Reuse Factor: The uplink reuse factor is determined from uplink intra and extra-cell interference (signals received
by the transmitter respectively from intra and extra-cell terminals). This is the ratio between the total uplink interference and the intra-cell interference. This value can be a simulation result or can be entered by the user.

AT310_UMU_E0
Scrambling Code Domain: The scrambling code domain to which the allocated scrambling code belongs. This and the
scrambling code reuse distance are used by the scrambling code planning algorithm.
SC Reuse Distance: The scrambling code reuse distance. This and the scrambling code domain are used by the scrambling code planning algorithm.
Primary Scrambling Code: The primary scrambling code.
Comments: If desired, you can enter any comments in this field.
Max Number of Intra-carrier Neighbours: The maximum number of intra-carrier neighbours for this cell. This value is
used by the intra-carrier neighbour allocation algorithm.
Max Number of Inter-carrier Neighbours: The maximum number of inter-carrier neighbours for this cell. This value is
used by the inter-carrier neighbour allocation algorithm.
Max Number of Inter-technology Neighbours: The maximum number of inter-technology neighbours for this cell.
This value is used by the inter-technology neighbour allocation algorithm.
Inter-technology UL Noise Rise: This noise rise represents the interference on this cell on the uplink created by the
mobiles and base stations of an external network. This noise rise will be taken into account in uplink interferencebased calculations involving this cell in the simulation. It is not used in predictions (AS Analysis and coverage predictions). In predictions, Atoll calculates the uplink total interference from the UL load factor which includes inter-technology uplink interference. For more information on inter-technology interference, see "Modelling Inter-Technology
Interference" on page 420.
Inter-technology DL Noise Rise: This noise rise represents the interference created by mobiles of an external network
on the mobiles served by this cell on the downlink. This noise rise will be taken into account in all downlink interference-based calculations involving this cell. For more information on inter-technology interference, see "Modelling
Inter-Technology Interference" on page 420.
Neighbours: You can access a dialogue in which you can set both intra-technology (intra-carrier and inter-carrier) and
inter-technology neighbours by clicking the Browse button (
ning Neighbours" on page 274.
). For information on defining neighbours, see "Plan-
The Browse button ( ) might not be visible in the Neighbours box if this is a new cell.
You can make the Browse button appear by clicking Apply.
HSPA Support: The HSPA functionality supported by the cell. You can choose between None (i.e., R99 only), HSDPA,
HSPA (i.e., HSDPA and HSUPA), HSPA+ with transmit diversity or HSPA+ with spatial multiplexing.
When HSDPA is supported, the following fields are available:
-
HSDPA Dynamic Power Allocation: If you are modelling dynamic power allocation, the HSDPA Dynamic Power
Allocation should be checked. During a simulation, Atoll first allocates power to R99 users and then dynamically
allocates the remaining power of the cell to the HS-PDSCH and HS-SCCH of HSDPA users. At the end of the simulation, you can commit the calculated available HSDPA power and total power values to each cell.
In the context of dynamic power allocation, the total power cannot exceed the maximum
power minus the power headroom.
Available HSDPA Power (dBm): When you are modelling static power allocation, the HSDPA Dynamic Power Allocation check box is cleared and the available HSDPA power is entered in this box. This is the power available for
the HS-PDSCH and HS-SCCH of HSDPA users.
Power Headroom (dB): The power headroom is a reserve of power that Atoll keeps for Dedicated Physical Channels (DPCH) in case of fast fading. During simulation, HSDPA users will not be connected if the cell power remaining
after serving R99 users is less than the power headroom value.
HS-SCCH Dynamic Power Allocation: If you are modelling dynamic power allocation the HS-SCCH Dynamic Power
Allocation check box should be checked and a value should be entered in HS-SCCH Power (dBm). During power
control, Atoll will control HS-SCCH power in order to meet the minimum quality threshold (as defined for each
mobility type). The value entered in HS-SCCH Power (dBm) is the maximum power available for each HS-SCCH
channel. The calculated power for each HSDPA user during the simulation cannot exceed this maximum value.
HS-SCCH Power (dBm): The value for each HS-SCCH channel will be used if you are modelling dynamic power allocation. If you have selected the HS-SCCH Dynamic Power Allocation check box and modelling dynamic power allocation, the value entered here represents a maximum for each HSDPA user. If you have not selected the HS-SCCH
Dynamic Power Allocation check box and are modelling static power allocation, the value entered here represents the actual HS-SCCH power per HS-SCCH channel.
Number of HS-SCCH Channels: The maximum number of HS-SCCH channels for this cell. Each Packet (HSDPA) and
Packet (HSPA) user consumes one HS-SCCH channel. Therefore, at any given time (over a time transmission
interval), the number of HSDPA bearer users cannot exceed the number of HS-SCCH channels per cell.
207

Forsk 2011
HS-DSCH transmissions without an accompanying HS-SCCH are performed for Packet

(HSPA - Constant Bit Rate) users. Therefore, the number of HS-SCCH channels is not taken
into account when managing the number of Packet (HSPA - Constant Bit Rate) users
connected at a given time.
-
Min. Number of HS-PDSCH Codes: The minimum number of OVSF codes available for HS-PDSCH channels. This
value will be taken into account during simulations in order to find a suitable bearer.
Max Number of HS-PDSCH codes: The maximum number of OVSF codes available for HS-PDSCH channels. This
value will be taken into account during simulations and coverage predictions in order to find a suitable bearer.
Max Number of HSDPA Users: The maximum number of HSDPA bearer users (i.e., Packet (HSDPA) users, Packet
(HSPA) users and Packet (HSPA - Constant Bit Rate) users) that this cell can support at any given time.
Number of HSDPA Users: The number of HSDPA bearer users is an average and can be used for certain coverage
predictions. You can enter this value yourself, or have the value calculated by Atoll using a simulation. Dual-cell
HSDPA users are counted once in each cell they are connected to.
HSDPA Scheduler Algorithm: The scheduling technique that will be used to rank the HSDPA users to be served:
- Max C/I: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined) are
scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending
order by the channel quality indicator (CQI).
- Round Robin: HSDPA users are scheduled in the same order as in the simulation (i.e., in random order).
- Proportional Fair: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined)
are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order according to a random parameter which corresponds to a combination of the user rank in the simulation and the channel quality indicator (CQI).
The random parameter is calculated by giving both the user simulation rank and the CQI a
weight of 50%. You can change the default weights by setting the appropriate options in
MUG Table = f(No. Users): You can access the MUG (Multi-User Gain) table by clicking the Browse button ( ).
The MUG table is a graph of throughput gain as a function of the number of users. The average cell throughput is
higher with multiple users than with a single user.
The MUG graph is only available if you have set the peak HSDPA throughput option in the atoll.ini file. For more
In transmitters that support multi-cell HSDPA, the multi-cell HSDPA scheduler algorithm and MUG graph are used in
calculations instead of the HSDPA scheduler algorithms and MUG graphs set per cell.
When HSUPA is supported, the following fields are also available:
-
DL HSUPA Power: The power (in dBm) allocated to HSUPA DL channels (E-AGCH, E-RGCH, and E-HICH). This value
must be entered by the user.
Max Number of HSUPA Users: The maximum number of HSUPA bearer users (i.e., Packet (HSPA) users and Packet
(HSPA - Constant Bit Rate) users) that this cell can support at any given time.
UL Load Factor Due to HSUPA (%): The uplink cell load contribution due to HSUPA. This value can be a simulation
result or can be entered by the user.
Number of HSUPA Users: The number of HSUPA bearer users is an average and can be used for certain coverage
predictions. This value can be a simulation result or can be entered by the user.
By default, the SCH power, the CCH power, the HS-SCCH power and the HSUPA power are
set as absolute values. You can set these values as relative to the pilot power by right-clicking the UMTS Network Settings folder on the Parameters tab of the Explorer window and
selecting Properties from the context menu. Then, on the Global Parameters tab of the
Properties dialogue, under DL Powers, you can select Relative to Pilot. The SCH power, the
CCH power, the HS-SCCH power, and the HSUPA power values are automatically converted
and set as relative to the pilot power.
6.2.1.2 Creating or Modifying a Base Station Element

A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells.
This section describes how to create or modify the following elements of a base station:
208
"Creating or Modifying a Site" on page 209

"Creating or Modifying a Transmitter" on page 209
"Creating or Modifying a Cell" on page 210.

AT310_UMU_E0
6.2.1.2.1
Creating or Modifying a Site

You can modify an existing site or you can create a new site. You can access the properties of a site, described in "Site Description" on page 202, through the sites Properties dialogue. How you access the Properties dialogue depends on whether you
are creating a new site or modifying an existing site.
To create a new site:
3. Select New from the context menu. The Sites New Element Properties dialogue appears (see Figure 6.3 on page 202).
4. Modify the parameters described in "Site Description" on page 202.
5. Click OK.
To modify the properties of an existing site:
) to expand the Sites folder.
3. Right-click the site you want to modify. The context menu appears.
4. Select Properties from the context menu. The sites Properties dialogue appears.
5. Modify the parameters described in "Site Description" on page 202.
6. Click OK.
If you are creating several sites at the same time, or modifying several existing sites, you
can do it quickly by editing or pasting the data directly in the Sites table. You can open
the Sites table by right-clicking the Sites folder on the Network tab of the Explorer
window and selecting Open Table from the context menu. For information on copying
and pasting data, see "Copying and Pasting in Tables" on page 54.
6.2.1.2.2
Creating or Modifying a Transmitter

You can modify an existing transmitter or you can create a new transmitter. When you create a new transmitter, its initial
settings are based on the default station template displayed in the Radio Planning toolbar. You can access the properties of
a transmitter, described in "Transmitter Description" on page 202, through the transmitters Properties dialogue. How you
access the Properties dialogue depends on whether you are creating a new transmitter or modifying an existing transmitter.
To create a new transmitter:
3. Select New from the context menu. The Transmitters New Element Properties dialogue appears (see Figure 6.4).
4. Modify the parameters described in "Transmitter Description" on page 202.
5. Click OK. When you create a new transmitter, Atoll automatically creates a cell based on the default station template.
For information on creating a cell, see "Creating or Modifying a Cell" on page 210.
To modify the properties of an existing transmitter:
) to expand the Transmitters folder.
3. Right-click the transmitter you want to modify. The context menu appears.
4. Select Properties from the context menu. The transmitters Properties dialogue appears.
5. Modify the parameters described in "Transmitter Description" on page 202.
6. Click OK.
209

Forsk 2011
6.2.1.2.3
If you are creating several transmitters at the same time, or modifying several
existing transmitters, you can do it more quickly by editing or pasting the data
directly in the Transmitters table. You can open the Transmitters table by rightclicking the Transmitters folder on the Network tab of the Explorer window and
selecting Open Table from the context menu. For information on copying and
pasting data, see "Copying and Pasting in Tables" on page 54.
If you want to add a transmitter to an existing site on the map, you can add the
transmitter by right-clicking the site and selecting New Transmitter from the context menu.
Creating or Modifying a Cell

You can modify an existing cell or you can create a new cell. You can access the properties of a cell, described in "Cell Definition" on page 205, through the Properties dialogue of the transmitter where the cell is located.
To create or modify a cell:
3. Right-click the transmitter on which you want to create a cell or whose cell you want to modify. The context menu
appears.
5. Select the Cells tab.
6. Modify the parameters described in "Cell Definition" on page 205.
7. Click OK.
If you are creating or modifying several cells at the same time, you can do it more
quickly by editing the data directly in the Cells table. You can open the Cells table
by right-clicking the Transmitters folder on the Network tab of the Explorer
window and selecting Cells > Open Table from the context menu. You can either
edit the data in the table, paste data into the table (see "Copying and Pasting in
Tables" on page 54), or import data into the table (see "Importing Tables from Text
Files" on page 58).
If you want to add a cell to an existing transmitter on the map, you can add the cell
by right-clicking the transmitter and selecting New Cell from the context menu.
6.2.1.3 Placing a New Station Using a Station Template

In Atoll, a station is defined as a site with one or more transmitters sharing the same properties. With Atoll, you can create a
network by placing stations based on station templates. This allows you to build your network quickly with consistent parameters, instead of building the network by first creating the site, then the transmitters, and finally by adding the cells.
To place a new station using a station template:
1. In the Radio Planning toolbar, select a template from the list.
2. Click the New Transmitter or Station button (
210
) in the Radio Planning toolbar.

AT310_UMU_E0
3. In the map window, move the pointer over the map to where you would like to
place the new station. The exact coordinates of the pointers current location are
visible in the Status bar.
4. Click to place the station.
To place the station more accurately, you can zoom in on the map before you click
the New Station button. For information on using the zooming tools, see "Changing
the Map Scale" on page 29.
If you let the pointer rest over the station you have placed, Atoll displays its tip text
with its exact coordinates, allowing you to verify that the location is correct.
You can also place a series of stations using a Atoll template. You do this by defining an area on the map where you want to
place the stations. Atoll calculates the placement of each station according to the defined hexagonal cell radius in the station
template. For information on defining the cell radius, see "Creating a Station Template" on page 212.
To place a series of stations within a defined area:
2. Click the Hexagonal Design button (
), to the left of the template list. A hexagonal design is a group of stations created from the same station template.
3. Draw a zone delimiting the area where you want to place the series of stations:
Atoll fills the delimited zone with new stations and their hexagonal shapes. Station objects such as sites and transmitters are also created and placed into their respective folders.
You can work with the sites and transmitters in these stations as you work with any station object, adding, for example,
another antenna to a transmitter.
Placing a Station on an Existing Site
When you place a new station using a station template as explained in "Placing a New Station Using a Station Template" on
page 210, the site is created at the same time as the station. However, you can also place a new station on an existing site.
To place a station on an existing site:
1. On the Network tab, clear the display check box beside the Hexagonal Design folder.
3. Click the New Station button (
4. Move the pointer to the site on the map. When the frame appears around the site, indicating it is selected, click to
place the station.
6.2.1.4 Managing Station Templates

Atoll comes with UMTS station templates, but you can also create and modify station templates. The tools for working with
station templates can be found on the Radio Planning toolbar (see Figure 6.6).
Figure 6.6: The Radio Planning toolbar

"Creating a Station Template" on page 212

"Modifying a Station Template" on page 212
"Copying Properties from One Station Template to Another" on page 217
211

6.2.1.4.1
Forsk 2011
"Modifying a Field in a Station Template" on page 217

"Deleting a Station Template" on page 217.
Creating a Station Template

When you create a station template, Atoll bases it on the station template selected in the Station Template Properties
dialogue. The new station template has the same parameters as the one it is based on. Therefore, by selecting the existing
station template that most closely resembles the station template you want to create, you can create a new template by only
modifying the parameters that differ.
To create a station template:
) to expand the UMTS Network Settings folder.
3. Right-click the Station Templates folder. The context menu appears.

4. Select Open Table from the context menu. The Station Templates table appears.
5. In the Station Templates table, right-click the station template that most closely resembles the station template you
want to create. The context menu appears.
6. Select Copy from the context menu.
7. Right-click the row marked with the New Row icon (
). The context menu appears.
8. Select Paste from the context menu. The station template you copied in step 5. is pasted in the new row, with the
Name of the new station template given as the same as the template copied but preceded by "Copy of".
9. Edit the parameters of the new station template in the table or as explained in "Modifying a Station Template" on
page 212.
6.2.1.4.2
Modifying a Station Template

You can modify a station template directly in the Station Templates table, or you can open the Properties dialogue for that
station template and modify the parameters in the dialogue.
To modify a station template:

5. Right-click the station template you want to modify. The context menu appears.
6. Select Record Properties from the context menu. The station templates Properties dialogue appears.
7. Click the General tab of the Properties dialogue. On this tab (see Figure 6.7), you can modify the following: the Name
of the station template, the number of Sectors, each with a transmitter, and the Hexagon Radius, i.e., the theoretical
radius of the hexagonal area covered by each sector.
212

AT310_UMU_E0
Figure 6.7: Station Template Properties dialogue General tab

-
Under Main Antenna, you can modify the following: the Height/Ground of the antennas from the ground (i.e., the
height over the DTM; if the transmitter is situated on a building, the height entered must include the height of
building), the main antenna Model, 1st Sector Azimuth, from which the azimuth of the other sectors are offset to
offer complete coverage of the area, the Mechanical Downtilt, and the Additional Electrical Downtilt for the
antenna.

Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both the
Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Working with Calculations in Atoll.
Under Comments, you can add additional information. The information you enter will be the default information
in the Comments field of any transmitter created using this station template.
8. Click the Transmitter tab. On this tab (see Figure 6.8), if the Active check box is selected, you can modify the following:
-
Under Transmission/Reception, you can click the Equipment button to open the Equipment Specifications dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or transmitter equipment. For information
on the Equipment Specifications dialogue, see "Transmitter Description" on page 202.
The information in the real Total Losses in transmission and reception boxes is calculated from the information
you entered in the Equipment Specifications dialogue (see Figure 6.5 on page 204). Any loss related to the noise
due to a transmitters repeater is included in the calculated losses. Atoll always considers the values in the Real
boxes in predictions even if they are different from the values in the Computed boxes. You can modify the real
Total Losses at transmission and reception if you want. Any value you enter must be positive.
The information in the real Noise Figure reception box is calculated from the information you entered in the
Equipment Specifications dialogue. You can modify the real Noise Figure at reception if you want. Any value you
enter must be positive.
Under Diversity, you can select the number of transmission and reception antenna ports used for MIMO (No. of
ports). MIMO systems are supported by some HSDPA bearers (following improvements introduced by release 7
of the 3GPP UTRA specifications, referred to as HSPA+). For more information on how the number of antenna
ports are used, see "Multiple Input Multiple Output Systems" on page 417.
R99 bearers only support transmit and receive diversities. You can define the transmit diversity method from the
Transmission list when more than one transmission antenna port is available. The receive diversity method de-
213

Forsk 2011
pends on the number of reception antenna ports selected (2RX for two reception antenna ports and 4RX for four
reception antenna ports).
Figure 6.8: Station Template Properties dialogue Transmitter tab

9. Click the W-CDMA/UMTS tab. On this tab (see Figure 6.9), you modify the Carriers (each corresponding to a cell) that
this station supports. For information on carriers and cells, see "Cell Definition" on page 205.
-
You can select the Carrier numbers for each sector of the station template. To select the carriers to be added to
the sectors of a base station created using this station template:
i.
Click the Browse button (
). The Carriers per Sector dialogue appears.
ii. In the Carriers per Sector dialogue, select the carriers to be created for each sector of the station.
iii. Click OK.
214

AT310_UMU_E0
Figure 6.9: Station Template Properties dialogue W-CDMA/UMTS tab

-
Under Primary Scrambling Code, you can modify the Reuse Distance and the scrambling code Domain.
Under Power, you can select the Power Shared Between Cells check box. As well, you can modify the Pilot, the
SCH, the Other CCH powers, and the AS Threshold.
Under Simulation Constraints, you can modify the Max Power, the Max DL Load (defined as a percentage of the
maximum power), the DL Peak Rate/User, the Max UL Load Factor, and the UL Peak Rate/User.
Under Load Conditions, you can modify the Total Transmitted Power, the UL Load Factor, and the UL Reuse
Factor.
Under Inter-technology Interferences, you can modify the UL and DL noise rise which respectively model the
effect of terminals and stations of an external network on the network cells and the effect of terminals of an
external network interfering the mobiles served by the network cells. For more information on inter-technology
interferences, See "Modelling Inter-Technology Interference" on page 420.
You can also modify the Number of Uplink and Downlink Channel Elements, the Max Iub Uplink and Downlink
Backhaul Throughputs and select the Equipment.
10. Click the HSPA/HSPA+ tab.

On this tab (see Figure 6.10), you can define the HSPA functionality supported by the cells. You can choose between
None (i.e., R99 only), HSDPA, HSPA (i.e, HSDPA and HSUPA), HSPA+ (transmit diversity) or HSPA+ (spatial multiplexing). When HSDPA functionality is supported, you can modify the following under HSDPA (for more information on
the fields, see "Cell Definition" on page 205):
-
You can select the Allocation Strategy (Static or Dynamic). If you select Static as the Allocation Strategy, you can
enter the available HSDPA Power. If you select Dynamic as the Allocation Strategy, Atoll allocates the HSDPA
power to cells during the simulation. Atoll first allocates power to R99 users and then dynamically allocates the
remaining power of the cell to the HS-PDSCH and HS-SCCH of HSDPA users. At the end of the simulation, you can
commit the calculated available HSDPA power and total power values to each cell.
Under Multi-cell, you can modify the multi-cell HSDPA Mode, select a multi-cell HSDPA scheduler Algorithm, and
enter a MUG=f(No. Users) graph.
Multi-cell HSDPA options are available if the dual-cell HSDPA optional feature has been activated. The MUG graph
is only available if you have set the peak HSDPA throughput option in the atoll.ini file. For more information, see
the Administrator Manual.
215

Forsk 2011
Under HS-PDSCH, you can modify the Min. and Max Number of Codes and the Power Headroom.
Under HS-SCCH, you can select the Allocation Strategy (Static or Dynamic) and the Number of Channels. If you
select Static as the Allocation Strategy, you can enter the HS-SCCH Power.
Under Scheduler, you can modify the Algorithm, the Max Number of Users, the Number of Users, and you can
enter a MUG=f(No. Users) graph. The MUG graph is only available if you have set the peak HSDPA throughput
option in the atoll.ini file. For more information, see the Administrator Manual.
Under HSUPA, if HSUPA functionality is supported, you can modify the following (for more information on the fields,
see "Cell Definition" on page 205):
-
You can modify the DL Power, the UL Load, the Max Number of Users, and the Number of Users.
Figure 6.10: Station Template Properties dialogue HSDPA tab

11. Click the Neighbours tab. In this tab (see Figure 6.11), you can modify the Max Number of Intra- and Inter-Carrier
Neighbours and the Max Number of Inter-Technology Neighbours. For information on defining neighbours, see
"Planning Neighbours" on page 274.
Figure 6.11: Station Template Properties dialogue Neighbours tab

12. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the
Sites table, or if you have defined an additional field in the Station Template Properties dialogue.
13. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your
changes.
216

AT310_UMU_E0
6.2.1.4.3
Copying Properties from One Station Template to Another

You can copy properties from one template to another template by using the Station Templates table.
To copy properties from one template to another template:

5. In the Stations Templates table, copy the settings in the row corresponding to the station template you want to copy
from and paste them into the row corresponding to the station template you want to modify.
6.2.1.4.4
Modifying a Field in a Station Template

To modify a field in a station template:

4. Select Properties from the context menu. The Station Template Properties dialogue appears.
5. Select the Table tab.
6. On the Table tab, you have the following options:
-
Add: If you want to add a user-defined field to the station templates, you must have already added it to the Sites
table (for information on adding a user-defined field to a table, see "Adding a Field to an Object Types Data Table"
on page 48) for it to appear as an option in the station template properties. To add a new field:
i.
Click the Add button. The Field Definition dialogue appears.
ii. Enter a Name for the new field. This is the name that will be used in database.
iii. If desired, you can define a Group that this custom field will belong to. When you open an Atoll document
from a database, you can then select a specific group of custom fields to be loaded from the database, instead
of loading all custom fields.
iv. In Legend, enter the name for the field that will appear in the Atoll document.
v. For Type, you can select from Text, Short integer, Long integer, Single, Double, True/False, Date/Time, and
Currency. If you choose text, you can also set the field Size (in characters), and create a Choice list, by entering
the possible selections directly in the Choice list window and pressing ENTER after each one.
vi. Enter, if desired, a Default value for the new field.
vii. Click OK to close the Field Definition dialogue and save your changes.
-
Delete: To delete a user-defined field:

i.
Select the user-defined field you want to delete.
ii. Click the Delete button. The user-defined field appears in strikeout. It will be definitively deleted when you
close the dialogue.
-
Properties: To modify the properties of a user-defined field:

i.
Select the user-defined field you want to modify.
ii. Click the Properties button. The Field Definition dialogue appears.
iii. Modify any of the properties as desired.
iv. Click OK to close the Field Definition dialogue and save your changes.
7. Click OK.
6.2.1.4.5
Deleting a Station Template

To delete a station template:
) to expand the Station Templates folder.
4. In the Station Templates folder, right-click the station template you want to delete. The context menu appears.
5. Select Delete from the context menu. The template is deleted.
217

Forsk 2011
6.2.1.5 Duplicating an Existing Base Station

You can create new base stations by duplicating an existing base station. When you duplicate an existing base station, the base
station you create will have the same site, transmitter, and cell parameter values as the original one. Duplicating a base station
allows you to:
Quickly create a new base station with the same settings as the original base station in order to study the effect of a
new base station on the coverage and capacity of the network, and
Quickly create a homogeneous network with stations that have the same characteristics.
To duplicate an existing base station:

) to expand the Sites folder.
3. Right-click the site you want to duplicate. The context menu appears.
4. From the context menu, select one of the following:
-
Select Duplicate > Without Neighbours from the context menu, if you want to duplicate the base station without
the intra- and inter-technology neighbours of its transmitters.
Select Duplicate > With Outward Neighbours from the context menu, if you want to duplicate the base station
along with the lists of intra- and inter-technology neighbours of its transmitters.
You can now place the new base station on the map using the mouse.
5. In the map window, move the pointer over the map to where you would like to place the new base station. The exact
coordinates of the pointers current location are visible in the Status bar.
Figure 6.12: Placing a new base station
To place the station more accurately, you can zoom in on the map before you select
Duplicate from the context menu. For information on using the zooming tools, see
"Changing the Map Scale" on page 29.
If you let the pointer rest over the station you have placed, Atoll displays tip text
with its exact coordinates, allowing you to verify that the location is correct.
6. Click to place the duplicate base station.

A new base station is placed on the map. The site, transmitters, and cells of the new base station have the same names
as the site, transmitters, and cells of the original base station with each name marked as "Copy of." The site, transmitters, and cells of the duplicate base station have the same settings as those of the original base station. All the remote
antennas and repeaters of any transmitter on the original site are also duplicated.
You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to place each
duplicate station.
For more information on the site, transmitter, subcell, and TRX properties, see "Definition of a Base Station" on page 201.
6.2.2 Creating a Group of Base Stations

You can create base stations individually as explained in "Creating a UMTS Base Station" on page 201, or you can create one
or several base stations by using station templates as explained in "Placing a New Station Using a Station Template" on
page 210. However, if you have a large data-planning project and you already have existing data, you can import this data into
your current Atoll document and create a group of base stations.
When you import data into your current Atoll document, the coordinate system of the
imported data must be the same as the display coordinate system used in the document.
If you cannot change the coordinate system of your source data, you can temporarily
change the display coordinate system of the Atoll document to match the source data. For
information on changing the coordinate system, see "Setting a Coordinate System" on
page 95.
218

AT310_UMU_E0
You can import base station data in the following ways:
Copying and pasting data: If you have data in table form, either in another Atoll document or in a spreadsheet, you
can copy this data and paste it into the tables in your current Atoll document. When you create a group of base
stations by copying and pasting data, you must copy and paste site data in the Sites table, transmitter data in the
Transmitters table, and cell data in the Cells table, in that order.
Important: The table you copy data from must have the same column layout as the table you are
pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 54.
Importing data: If you have data in text or comma-separated value (CSV) format, you can import it into the tables in
the current document. If the data is in another Atoll document, you can first export it in text or CSV format and then
import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select what
values you import into which columns of the table.
When you create a group of base stations by importing data, you must import site data in the Sites table, transmitter
data in the Transmitters table, and cell data in the Cells table, in that order.
For information on exporting table data, see "Exporting Tables to Text Files" on page 57. For information on importing
table data, see "Importing Tables from Text Files" on page 58.
You can quickly create a series of base stations for study purposes using the Hexagonal
Design tool on the Radio Planning toolbar. For information, see "Placing a New Station
Using a Station Template" on page 210.
6.2.3 Modifying Sites and Transmitters Directly on the Map

In Atoll, you can access the Properties dialogue of a site or transmitter using the context menu on the Network tab of the
Explorer window. However, in a complex radio-planning project, it can be difficult to find the data object in the Network tab,
although it might be visible in the map window. Atoll lets you access the Properties dialogue of sites and transmitters directly
from the map. If there is more than one transmitter with the same azimuth, clicking the transmitters in the map window opens
a context menu allowing you to select the transmitter. You can also change the position of the station by dragging it, or by
letting Atoll find a higher location for it.
Modifying sites and transmitters directly on the map is explained in detail in Chapter 1: The Working Environment:
"Selecting One of Several Transmitters" on page 21

"Moving a Site Using the Mouse" on page 21
"Moving a Site to a Higher Location" on page 21
"Changing the Azimuth of the Antenna Using the Mouse" on page 22
"Changing the Antenna Position Relative to the Site Using the Mouse" on page 22.
6.2.4 Display Tips for Base Stations

Atoll allows to you to display information about base stations in a number of different ways. This enables you not only to
display selected information, but also to distinguish base stations at a glance.
The following tools can be used to display information about base stations:
Label: You can display information about each object, such as each site or transmitter, in the form of a label that is
displayed with the object. You can display information from every field in that object types data table, including from
fields that you add. The label is always displayed, so you should choose information that you would want to always be
visible; too much information will lead to a cluttered display. For information on defining the label, see "Defining the
Object Type Label" on page 26.
Tip text: You can display information about each object, such as each site or transmitter, in the form of tip text that is
only visible when you move the pointer over the object. You can choose to display more information than in the label,
because the information is only displayed when you move the pointer over the object. You can display information
from any field in that object types data table, including from fields that you add. For information on defining the tip
text, see "Defining the Object Type Tip Text" on page 26.
Transmitter colour: You can set the transmitter colour to display information about the transmitter. For example, you
can select "Discrete Values" to distinguish transmitters by antenna type, or to distinguish inactive from active sites.
219

Forsk 2011
You can also define the display type for transmitters as "Automatic." Atoll then automatically assigns a colour to each
transmitter, ensuring that each transmitter has a different colour than the transmitters surrounding it. For information on defining the transmitter colour, see "Defining the Display Type" on page 24.
Transmitter symbol: You can select one of several symbols to represent transmitters. For example, you can select a
symbol that graphically represents the antenna half-power beamwidth (
). If you have two transmitters on the
same site with the same azimuth, you can differentiate them by selecting different symbols for each (
For information on defining the transmitter symbol, see "Defining the Display Type" on page 24.
and
).
6.2.5 Creating a Dual-Band UMTS Network

In Atoll, you can model a dual-band UMTS network, i.e., a network consisting of 2100 MHz and 900 MHz transmitters, in one
document. Creating a dual-band UMTS network consists of the following steps:
1. Defining the two frequency bands in the document (see "Defining Frequency Bands" on page 409).
2. Selecting and calibrating a propagation model for each frequency band (see Chapter 5: Working with Calculations in
Atoll).
3. Assigning a frequency band, with its propagation model, to each transmitter (see "Transmitter Description" on
page 202).
4. Defining the frequency bands with which terminals are compatible (see "Modelling UMTS HSPA Terminals" on
page 255).
6.2.6 Creating a Repeater

A repeater receives, amplifies, and re-transmits the radiated or conducted RF carrier both in downlink and uplink. It has a
donor side and a server side. The donor side receives the signal from a donor transmitter, repeater, or remote antenna. This
signal may be carried by different types of links such as a radio link or a microwave link. The server side re-transmits the
received signal.
Atoll models RF repeaters and microwave repeaters. The modelling focuses on:
The additional coverage these systems provide to transmitters in the downlink.

The UL total gain value in service areas predictions (effective service area and UL Eb/Nt service area) and the noise
rise generated at the donor transmitter by the repeater.
"Opening the Repeaters Table" on page 220

"Creating and Modifying Repeater Equipment" on page 220
"Placing a Repeater on the Map Using the Mouse" on page 221
"Creating Several Repeaters" on page 221
"Defining the Properties of a Repeater" on page 222
"Tips for Updating Repeater Parameters" on page 223.
Broad-band repeaters are not modelled. Atoll assumes that all carriers from the 3G donor
transmitter are amplified.
6.2.6.1 Opening the Repeaters Table

Repeaters and their defining parameters are stored in the Repeaters table.
To open the Repeaters table:
3. Select Repeaters > Open Table from the context menu. The Repeaters table appears.
6.2.6.2 Creating and Modifying Repeater Equipment

You can define repeater equipment to be assigned to each repeater in the network.
To create repeater equipment:
) to expand the Radio Network Equipment folder.
3. In the Radio Network Equipment folder, right-click Repeater Equipment. The context menu appears.
220

AT310_UMU_E0
4. Select Open Table from the context menu. The Repeater Equipment table appears.
5. Enter the following in the row marked with the New Row icon (
):
a. Enter a Name and Manufacturer for the new equipment.

b. Enter a Noise Figure (dB). The repeater causes a rise in noise at the donor transmitter, so the noise figure is used
to calculate the UL loss to be added to the donor transmitter UL losses. The noise figure must be a positive value.
c. Enter minimum and maximum repeater amplification gains in the Min. Gain and Max Gain columns. These parameters enable Atoll to ensure that the user-defined amplifier gain is consistent with the limits of the equipment if
there are any.
d. Enter a Gain Increment. Atoll uses the increment value when you increase or decrease the repeater amplifier gain
using the buttons to the right of the Amplification gain box (
dialogue.
) on the General tab of the repeater Properties
e. Enter the maximum power that the equipment can transmit on the downlink in the Max Downlink Power column.
This parameter enables Atoll to ensure that the downlink power after amplification does not exceed the limit of
the equipment.
f.
If desired, enter a Max Uplink Power, an Internal Delay and Comments. These fields are for information only and
are not used in calculations.
To modify repeater equipment:

3. In the Radio Network Equipment folder, right-click Repeater Equipment. The context menu appears.
4. Select Open Table from the context menu. The Repeater Equipment table appears.
5. Change the parameters in the row containing the repeater equipment you want to modify.
6.2.6.3 Placing a Repeater on the Map Using the Mouse

In Atoll, you can create a repeater and place it using the mouse. When you create a repeater, you can add it to an existing site,
or have Atoll automatically create a new site. Atoll supports cascading repeaters, in other words, repeaters that extend the
coverage of another repeater or of a remote antenna.
To create a repeater and place it using the mouse:
1. Select the donor transmitter, repeater, or remote antenna. You can select it from the Transmitters folder of the
Explorer windows Network tab, or directly on the map.
2. Click the arrow next to New Repeater or Remote Antenna button (
3. Select Repeater from the menu.

4. Click the map to place the repeater. The repeater is placed on the map, represented by a symbol (
) in the same
colour as the donor transmitter, repeater, or remote antenna. If the repeater is inactive, it is displayed by an empty
icon. By default, the repeater has the same azimuth as the donor. Its tip text and label display the same information
as displayed for the donor. As well, its tip text identifies the repeater and the donor. In the Explorer window, the
repeater is found in the Transmitters folder of the Network tab under its donor transmitter, repeater, or remote
antenna.
For information on defining the properties of the new repeater, see "Defining the Properties of a Repeater" on
page 222.
You can see to which base station the repeater is connected by clicking it; Atoll displays a
link to the donor transmitter, repeater, or remote antenna.
6.2.6.4 Creating Several Repeaters

In Atoll, the characteristics of each repeater are stored in the Repeaters table. If you have data in table form, either in another
Atoll document or in a spreadsheet, you can copy this data and paste it into the Repeaters table in your current Atoll document.
To paste the information into the Repeaters table:
1. Open the Repeaters table as explained in "Opening the Repeaters Table" on page 220.
2. Copy the data from the source document and paste it into the Repeaters table.
221

Forsk 2011
The table you copy data from must have the same column layout as the table you are
pasting data into.
6.2.6.5 Defining the Properties of a Repeater

To define the properties of a repeater:
1. Right-click the repeater either directly on the map, or in the Repeaters table (for information on opening the Repeaters table, see "Opening the Repeaters Table" on page 220). The context menu appears.
3. Click the General tab. You can modify the following parameters:
-
You can change the Name of the repeater. By default, repeaters are named "RepeaterN" where "N" is a number
assigned as the repeater is created.
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, another repeater,
or a remote antenna. Clicking the Browse button (
You can change the Site on which the repeater is located. Clicking the Browse button (
) opens the Properties
dialogue of the site.
You can enter the Shared Antenna (coverage side) flag for the repeater. This flag is used to identify the repeaters
of different technologies, located at the same site, that share antennas. These repeaters may be other technology
repeaters in a 3GPP Multi-RAT document or in a linked co-planning document. The flag must be the same for all
such repeaters. Shared antennas have the same position relative to the site (Dx, Dy), height, azimuth, and mechanical tilt, for all the repeaters that use them. Atoll automatically synchronises changes made to these parameters
for one repeater to all other repeaters that share the antenna. For more information on co-planning, see "Co-planning UMTS Networks with Other Networks" on page 390.
Under Antenna Position, you can define the position of the repeater, if it is not located on the site itself:
-
) opens the Properties dialogue of the donor.
Relative to Site: Select Relative to Site, if you want to define the position of the repeater relative to the site
itself and then enter the XY offsets.
Coordinates: Select Coordinates, if you want to define the position of the repeater by its XY coordinates.
You can select equipment from the Equipment list. Clicking the Browse button (
) opens the Properties dialogue of the equipment.
You can change the Amplification Gain. The amplification gain is used in the link budget to evaluate the repeater
total gain.
4. Click the Donor Side tab. You can modify the following parameters:
-
Under Donor-Repeater Link, select a Link Type.

-
If you select Microwave Link, enter the Propagation Losses and continue with step 5.
If you select Air, select a Propagation Model and enter the Propagation Losses or click Calculate to determine
the actual propagation losses between the donor and the repeater. If you do not select a propagation model,
the propagation losses between the donor transmitter and the repeater are calculated using the ITU 526-5
propagation model.
When you create an off-air repeater, it is assumed that the link between the donor transmitter and the repeater has the same frequency as the network.
If you want to create a remote antenna, you must select Optical Fibre Link.
If you selected Air under Donor-Repeater Link, enter the following information under Antenna:
-
222
Model: The type of antenna is visible in the Model list. You can click the Browse button (
) to access the
properties of the antenna. Clicking the Select button opens a dialogue displaying all the possible antennas
based on the same physical antenna as the currently selected one. Selecting the Electrical tilt of the antenna
model displays the appropriate antennas under Available Antennas. Selecting the antenna under Available
Antennas and clicking OK assigns the antenna to the transmitter. The other fields, Azimuth, Mechanical
Downtilt, and Additional Electrical Downtilt, display additional antenna parameters.
the altitude of the site as given by the DTM. If the repeater is situated on a building, the height entered must
Enter the Azimuth and the Mechanical Downtilt.

AT310_UMU_E0
You can click the Calculate button to update azimuth and downtilt values after changing
the repeater donor side antenna height or the repeater location. If you choose another site
or change site coordinates in the General tab, click Apply before clicking the Calculate
button.
-
If you selected Air under Donor-Repeater Link, enter the following information under Feeders:
i.
Select a Type of feeder from the list. You can click the Browse button (
feeder.
) to access the properties of the
ii. Enter the Length of the feeder cable at Transmission and at Reception.
5. Click the Coverage Side tab. You can modify the following parameters:
-
Select the Active check box. Only active repeaters (displayed in red in the Transmitters folder in the Network tab
of the Explorer window) are calculated.
Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual gains. If
you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply before clicking
the Calculate button. Atoll uses the DL total gain values to calculate the signal level received from the repeater.
The UL total gain value is considered in UL Eb/Nt service area predictions.
The DL total gain is applied to each power (pilot power, SCH power, etc.). The UL total gain is applied to each terminal power. The total gains take into account losses between the donor transmitter and the repeater, donor
characteristics (donor antenna gain, reception feeder losses), amplification gain, and coverage characteristics
(coverage antenna gain and transmission feeder losses).
Under Antennas, you can modify the following parameters:

-
the altitude of the site as given by the DTM. If the repeater is situated on a building, the height entered must
button (
their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power.

page 47.
Under Feeders, you can modify the following information:

i.
feeder.
-
Under Losses, Atoll displays the Loss Related to Repeater Noise Rise.
6. Click the Propagation tab. Since repeaters are taken into account during calculations, you must set the propagation
parameters. On the Propagation tab, you can modify the following: the Propagation Model, Radius, and Resolution
for both the Main Matrix and the Extended Matrix. By default, the propagation characteristics of the repeater (model,
calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation
models, see Chapter 5: Working with Calculations in Atoll.
6.2.6.6 Tips for Updating Repeater Parameters

Atoll provides you with a few shortcuts that you can use to change certain repeater parameters:
You can update the calculated azimuth and downtilt of the donor-side antennas of all repeaters by selecting
Repeaters > Calculate Donor Side Azimuths and Tilts from the Transmitters context menu.
You can update the UL and DL total gains of all repeaters by selecting Repeaters > Calculate Gains from the Transmitters context menu.
223

Forsk 2011
You can prevent Atoll from updating the UL and DL total gains of selected repeaters by
creating a custom Boolean field named "FreezeTotalGain" in the Repeaters table and
setting the value of the field to "True." Afterwards, when you select Repeaters > Calculate
Gains from the Transmitters context menu, Atoll will only update the UL and DL total gains
for repeaters with the custom field "FreezeTotalGain" set to "False."
You can update the propagation losses of all off-air repeaters by selecting Repeaters > Calculate Donor Side Propagation Losses from the Transmitters context menu.
You can select a repeater on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using the
Mouse" on page 22) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using
the Mouse" on page 22).
6.2.7 Creating a Remote Antenna

Atoll allows you to create remote antennas to position antennas at locations that would normally require long runs of feeder
cable. A remote antenna is connected to the base station with an optic fibre. Remote antennas allow you to ensure radio
coverage in an area without a new base station.
In Atoll, the remote antenna should be connected to a base station that does not have any antennas. It is assumed that a
remote antenna, as opposed to a repeater, does not have any equipment and generates no amplification gain nor noise. In
certain cases, you may want to model a remote antenna with equipment or a remote antenna connected to a base station
that has antennas. This can be done by modelling a repeater. For information on creating a repeater, see "Creating a
Repeater" on page 220.
"Opening the Remote Antennas Table" on page 224

"Placing a Remote Antenna on the Map Using the Mouse" on page 224
"Creating Several Remote Antennas" on page 225
"Defining the Properties of a Remote Antenna" on page 225
"Tips for Updating Remote Antenna Parameters" on page 226.
6.2.7.1 Opening the Remote Antennas Table

The remote antennas and their defining parameters are stored in the Remote Antennas table.
To open the Remote Antennas table:
3. Select Remote Antennas > Open Table from the context menu. The Remote Antennas table appears.
6.2.7.2 Placing a Remote Antenna on the Map Using the Mouse

In Atoll, you can create a remote antenna and place it using the mouse. When you create a remote antenna, you can add it
to an existing base station without antennas, or have Atoll automatically create a new site.
To create a remote antenna and place it using the mouse:
1. Select the donor transmitter. You can select it from the Transmitters folder of the Explorer windows Network tab, or
directly on the map.
Ensure that the remote antennas donor transmitter does not have any antennas.
2. Click the arrow next to New Repeater or Remote Antenna button (
3. Select Remote Antenna from the menu.

4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol (
)
in the same colour as the donor transmitter. If the remote antenna is inactive, it is displayed by an empty icon. By
default, the remote antenna has the same azimuth as the donor transmitter. Its tip text and label display the same
information as displayed for the donor transmitter. As well, its tip text identifies the remote antenna and the donor
transmitter.
For information on defining the properties of the new remote antenna, see "Defining the Properties of a Remote
Antenna" on page 225.
224

AT310_UMU_E0
You can see to which base station the remote antenna is connected by clicking it; Atoll
displays a link to the donor transmitter.
6.2.7.3 Creating Several Remote Antennas

In Atoll, the characteristics of each remote antenna are stored in the Remote Antennas table. If you have data in table form,
either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Remote Antennas table in
your current Atoll document.
To paste the information into the Remote Antennas table:
1. Open the Remote Antennas table as explained in "Opening the Remote Antennas Table" on page 224.
2. Copy the data from the source document and paste it into the Remote Antennas table.
The table you copy data from must have the same column layout as the table you are
pasting data into.
6.2.7.4 Defining the Properties of a Remote Antenna

To define the properties of a remote antenna:
1. Right-click the remote antenna either directly on the map, or in the Remote Antennas table (for information on opening the Remote Antennas table, see "Opening the Remote Antennas Table" on page 224). The context menu appears.
3. Click the General tab. You can modify the following parameters:
-
You can change the Name of the remote antenna. By default, remote antennas are named "RemoteAntennaN"
where "N" is a number assigned as the remote antenna is created.
You can change the Donor transmitter by selecting it from the Donor list. Clicking the Browse button (
the Properties dialogue of the donor transmitter.
You can change the Site on which the remote antenna is located. Clicking the Browse button (
) opens the
Properties dialogue of the site.
You can enter the Shared Antenna (coverage side) flag for the remote antenna. This flag is used to identify the
remote antennas of different technologies, located at the same site, that share antennas. These remote antennas
may be other technology remote antennas in a 3GPP Multi-RAT document or in a linked co-planning document.
The flag must be the same for all such remote antennas. Shared antennas have the same position relative to the
site (Dx, Dy), height, azimuth, and mechanical tilt, for all the remote antennas that use them. Atoll automatically
synchronises changes made to these parameters for one remote antenna to all other remote antennas that share
the antenna. For more information on co-planning, see "Co-planning UMTS Networks with Other Networks" on
page 390.
Under Antenna Position, you can define the position of the remote antenna, if it is not located on the site itself:
) opens
Relative to Site: Select Relative to Site, if you want to define the position of the remote antenna relative to
the site itself and then enter the XY offsets.
Coordinates: Select Coordinates, if you want to define the position of the remote antenna by its XY coordinates.
A remote antenna does not have equipment.
4. Click the Donor Side tab. You can modify the following parameters:
-
Under Donor-Repeater Link, select Optical Fibre Link and enter the Fibre Losses.
5. Click the Coverage Side tab. You can modify the following parameters:
-
Select the Active check box. Only active remote antennas (displayed in red in the Transmitters folder in the Network tab of the Explorer window) are calculated.
Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual gains. If
you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply before clicking
225

Forsk 2011
the Calculate button. Atoll uses the DL total gain values to calculate the signal level received from the remote
antenna. The UL total gain value is considered in UL Eb Nt service area predic ons.
The DL total gain is applied to each power (pilot power, SCH power, etc.). The UL total gain is applied to each terminal power. The total gains take into account losses between the donor transmitter and the remote antenna.
-
Under Antennas, you can modify the following parameters:

-
the altitude of the site as given by the DTM. If the remote antenna is situated on a building, the height entered
must include the height of building.
button (
their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power.

page 47.
Under Feeders, you can modify the following information:

i.
feeder.
6. Click the Propagation tab. Since remote antennas are taken into account during calculations, you must set propagation parameters, as with transmitters. On the Propagation tab, you can modify the following: the Propagation Model,
Radius, and Resolution for both the Main Matrix and the Extended Matrix. By default, the propagation characteristics
of the remote antenna (model, calculation radius, and grid resolution) are the same as those of the donor transmitter.
For information on propagation models, see Chapter 5: Working with Calculations in Atoll.
6.2.7.5 Tips for Updating Remote Antenna Parameters

Atoll provides you with a few shortcuts that you can use to change certain remote antenna parameters:
You can update the UL and DL total gains of all remote antennas by selecting Remote Antennas > Calculate Gains from
the Transmitters context menu.
You can prevent Atoll from updating the UL and DL total gains of selected remote antennas
by creating a custom Boolean field named "FreezeTotalGain" in the Remote Antennas
table and setting the value of the field to "True." Afterwards, when you select Remote
Antennas > Calculate Gains from the Transmitters context menu, Atoll will only update
the UL and DL total gains for remote antennas with the custom field "FreezeTotalGain" set
to "False."
You can select a remote antenna on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using
the Mouse" on page 22) or its position relative to the site (see "Changing the Antenna Position Relative to the Site
Using the Mouse" on page 22).
6.2.8 Setting the Working Area of an Atoll Document

When you load project data from a database, you will probably only modify the data in the region for which you are responsible. For example, a complex radio-planning project may cover an entire region or even an entire country. You, however,
might be responsible for the radio planning for only one city. In such a situation, doing a coverage prediction that calculates
the entire network would not only take a lot of time, it is not necessary. Consequently, you can restrict a coverage prediction
to the sites that you are interested in and generate only the results you need.
In Atoll, there are two ways of restricting the number of sites covered by a coverage prediction, each with its own advantages:
226

AT310_UMU_E0
Filtering the desired sites

You can simplify the selection of sites to be studied by using a filter. You can filter sites according to one or more fields,
or you can create an advanced filter by combining several criteria in several fields. You can create a graphic filter by
either using an existing vector polygon or creating a new vector polygon. For information on graphic filters, see "Filtering Data Using a Filtering Zone" on page 82. This enables you to keep only the base stations with the characteristics
you want to study. The filtering zone is taken into account whether or not it is visible.
For information on filtering, see "Filtering Data" on page 71.
Setting a computation zone

Drawing a computation zone to encompass the sites to be studied limits the number of sites to be calculated, which
in turn reduces the time necessary for calculations. In a smaller project, the time savings may not be significant. In a
larger project, especially when you are making repeated predictions in order to see the effects of small changes in site
configuration, the savings in time is considerable. Limiting the number of sites by drawing a computation zone also
limits the resulting calculated coverage. The computation zone is taken into account whether or not it is visible.
It is important not to confuse the computation zone and the focus zone or hot spot. The computation zone defines
the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo, power control simulations, etc.,
while the focus zone or hot spot is the area taken into consideration when generating reports and results.
For information on the computation zone, see "Creating a Computation Zone" on page 236.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be studied.
6.2.9 Studying a Single Base Station

As you create a site, you can study it to test the effectiveness of the set parameters. Coverage predictions on groups of sites
can take a large amount of time and consume a lot of computer resources. Restricting your coverage prediction to the site
you are currently working on allows you get the results quickly. You can expand your coverage prediction to a number of sites
once you have optimised the settings for each individual site.
Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data into
account and calculates losses along the transmitter-receiver path. This allows you to predict the received signal level at any
given point. Atoll enables you to assign both a main propagation model, with a shorter radius and a higher resolution, and an
extended propagation model, with a longer radius and a lower resolution. By using a calculation radius, Atoll limits the scope
of calculations to a defined area. By using two matrices, Atoll allows you to calculate high resolution path loss matrices closer
to the transmitter, while reducing calculation time by using an extended matrix with a lower resolution.
You can assign a propagation model to all transmitters at once, to a group of transmitters, or to a single transmitter. Assigning
a propagation model is explained in "Assigning a Propagation Model" on page 233.
"Making a Point Analysis to Study the Profile" on page 227

"Studying Signal Level Coverage" on page 229.
6.2.9.1 Making a Point Analysis to Study the Profile

In Atoll, you can make a point analysis to study reception along a profile between a reference transmitter and a UMTS user.
Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data into
account and calculates losses along the transmitter-receiver path. The profile is calculated in real time, using the propagation
model, allowing you to study the profile and get a prediction on each selected point.
For information on assigning a propagation model, see "Assigning a Propagation Model" on page 233.
To make a point analysis:
1. In the map window, select the transmitter from which you want to make a point analysis.
2. Click the Point Analysis button (
pointer changes (
) in the Radio Planning toolbar. The Point Analysis window appears and the
) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following:
-
Move the receiver to change the current position.

Click to place the receiver at the current position. You can move the receiver again by clicking it a second time.
Right-click the receiver to choose one of the following commands from the context menu:
-
Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates.
Target Site: Select a site from the list to place the receiver directly on a site.
4. Select Profile from the list at the top of the Point Analysis window.
227

Forsk 2011
The profile analysis appears in the Profile tab of the Point Analysis window. The altitude (in metres) is reported on
the vertical axis and the receiver-transmitter distance on the horizontal axis. A blue ellipsoid indicates the Fresnel zone
between the transmitter and the receiver, with a green line indicating the line of sight (LOS). Atoll displays the angle
of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an obstacle, this causes attenuation with diffraction displayed by a red vertical line (if the propagation model used takes diffraction mechanisms
into account). The main peak is the one that intersects the most with the Fresnel ellipsoid. With some propagation
models using a 3 knife-edge Deygout diffraction method, the results might display two additional attenuations peaks.
The total attenuation is displayed above the main peak.
The results of the analysis are displayed at the top of the Profile tab:
-
The received signal strength of the selected transmitter

The propagation model used
The shadowing margin and the indoor loss (if selected)
The distance between the transmitter and the receiver.
You can change the following options at the top of the Profile tab:
-
Transmitter: Select the transmitter from the list.

Carriers: Select the carrier to be analysed.
5. At the top of the Profile tab, you can click one of the following buttons:
-
: Click the Properties button (
: Click the Options button (
) to display the Properties dialogue of the selected transmitter.

) to display the Calculation Options dialogue. You can change the following:
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability.
- Select Signal Level, Path loss, or Total losses from the Result Type list.
- You can select the Indoor Coverage check box to add indoor losses.
Geographic: Click the Geographic button if you want to view the geographic profile between the transmitter and
the receiver. Atoll displays the profile between the transmitter and the receiver with clutter heights. An ellipsoid
indicating the Fresnel zone is also displayed. Atoll does not calculate or display signal levels and losses.
: Click the Link Budget button (
) to display a dialogue with the link budget.
: Click the Detailed Report button (

) to display a text document with details on the displayed profile
analysis. Detailed reports are only available for the standard propagation model.
: Click the Copy button (

) to copy the Profile tab. You can then paste the contents of the Profile tab as a
graphic into a graphic editing or word-processing programme.
: Click the Print button (
) to print the Profile tab.
Figure 6.13: Point Analysis - Profile tab
228

AT310_UMU_E0
6.2.9.2 Studying Signal Level Coverage

As you are building your radio-planning project, you might want to check the coverage of a new base station without having
to calculate the entire project. You can do this by selecting the site with its transmitters and then creating a new coverage
prediction.
This section explains how to calculate the signal level coverage of a single site. A signal level coverage prediction displays the
signal of the best server for each pixel of the area studied.
You can use the same procedure to study the signal level coverage of several sites by
grouping the transmitters. For information on grouping transmitters, see "Grouping Data
Objects by a Selected Property" on page 65.
To study the signal level coverage of a single base station:
2. Right-click the Transmitters folder and select Group by > Site from the context menu. The transmitters are now displayed in the Transmitters folder by the site on which they are situated.
If you want to study only sites by their status, at this step you could group them by
status.
3. Select the propagation parameters to be used in the coverage prediction:

b. Right-click the group of transmitters you want to study. The context menu appears.
c. Select Open Table from the context menu. A table appears with the properties of the selected group of transmitters.
d. In the table, you can configure two propagation models: one for the main matrix, with a shorter radius and a higher resolution, and another for the extended matrix, with a longer radius and a lower resolution. By calculating two
matrices you can reduce the time of calculation by using a lower resolution for the extended matrix and you can
obtain more accurate results by using for the main and extended matrices propagation models best suited for
each distance.
e. For the main propagation model:
f.
Select a Main Propagation Model

Enter a Main Calculation Radius and Main Resolution.
If desired, for the extended propagation model:

-
Select an Extended Propagation Model

Enter an Extended Calculation Radius and Extended Resolution.
g. Close the table.

4. In the Transmitters folder, right-click the group of transmitters you want to study and select Calculations > Create a
New Prediction from the context menu. The Prediction Types dialogue appears.
The Prediction Types dialogue lists the predictions available. They are divided into Standard Predictions, supplied
with Atoll, and Customised Predictions. Unless you have already created some customised coverage predictions, the
Customised Predictions list will be empty.
5. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears.
6. You can configure the following parameters in the Properties dialogue:
-
General tab: You can change the assigned Name of the coverage prediction, the Resolution, and you can add a
Comment. The resolution you set is the display resolution, not the calculation resolution.
To improve memory consumption and optimise the calculation times, you should set the display resolutions of
coverage predictions according to the precision required. The following table lists the levels of precision that are
usually sufficient:
Size of the Coverage Prediction
Display Resolution
City Centre
5m
City
20 m
229

Forsk 2011
Size of the Coverage Prediction
Display Resolution
County
50 m
State
100 m
Country
According to the size of the

country
Conditions tab: The coverage prediction parameters on the Conditions tab allow you to define the signals that will
be considered for each pixel (see Figure 6.14).
-
At the top of the Conditions tab, you can set the signal level range to be considered. In Figure 6.14, a signal
level less than or equal to -120 dBm will be considered.
Under Server, select "All" to consider signal levels from all servers.
If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability.
You can select the Indoor Coverage check box to add indoor losses.
You can select the Carrier to be studied, or select "Best (All Bands)" to have the carrier selected according to
the carrier selection method defined for the site equipment. The coverage prediction displays the strength of
the received pilot signal.
Figure 6.14: Condition settings for a signal level coverage prediction

-
Display tab: You can modify how the results of the coverage prediction will be displayed.
-
Under Display Type, select "Value Intervals."

Under Field, select "Best Signal Level." Selecting "All" or "Best Signal Level" on the Conditions tab will give you
the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal
Level" necessitates, however, the longest time for calculation.
You can change the value intervals and their displayed colour. For information on changing display properties,
see "Display Properties of Objects" on page 23.
You can create tip text with information about the coverage prediction by clicking the Browse button (
next to the Tip Text box and selecting the fields you want to display in the tip text.
You can select the Add to Legend check box to add the displayed value intervals to the legend.
If you change the display properties of a coverage prediction after you have calculated it,
you may make the coverage prediction invalid. You will then have to recalculate the coverage prediction to obtain valid results.
later:
-
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately.
Calculate button (
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
230

AT310_UMU_E0
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The signal level
coverage prediction can be found in the Predictions folder on the Network tab. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon (
folder. When you click the Calculate button (
) beside the coverage prediction in the Predictions
), Atoll only calculates unlocked coverage predictions (
).
6.2.10 Studying Base Stations

When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the
current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone.
Figure 6.15 gives an example of a computation zone. In Figure 6.15, the computation zone is displayed in red, as it is in the
Atoll map window. The propagation zone of each active site is indicated by a blue square. Each propagation zone that intersects the rectangle (indicated by the green dashed line) containing the computation zone will be taken into consideration
when Atoll calculates the coverage prediction. Sites 78 and 95, for example, are not in the computation zone. However, their
propagation zones intersect the rectangle containing the computation zone and, therefore, they will be taken into consideration in the coverage prediction. On the other hand, the coverage zones of three other sites do not intersect the green rectangle. Therefore, they will not be taken into account in the coverage prediction.
Figure 6.15: An example of a computation zone

Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices using
the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main propagation
model with a shorter radius (displayed with a blue square in Figure 6.15) and a higher resolution and an extended propagation
model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate higher resolution
path loss matrices close to the transmitter and the extended propagation model to calculate lower resolution path loss matrices outside the area covered by the main propagation model.
"Path Loss Matrices" on page 232

"Assigning a Propagation Model" on page 233
"The Calculation Process" on page 235
"Creating a Computation Zone" on page 236
"Setting Transmitters or Cells as Active" on page 236
"Signal Level Coverage Predictions" on page 237
"Analysing a Coverage Prediction" on page 241
"UMTS-Specific Predictions" on page 251
231

Forsk 2011
"HSDPA Quality and Throughput Analysis" on page 267

"HSUPA Quality and Throughput Analysis" on page 269
"Printing and Exporting Coverage Prediction Results" on page 270.
6.2.10.1 Path Loss Matrices

Path loss is caused by objects in the transmitter-receiver path and is calculated by the propagation model. In Atoll, the path
loss matrices are needed for all base stations that are active, filtered and whose propagation zone intersects a rectangle
containing the computation zone (for an explanation of the computation zone, see "Studying Signal Level Coverage" on
page 229) and must be calculated before predictions and simulations can be made.
Storing Path Loss Matrices
Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices
in the Atoll document results in a more portable but significantly larger document. in the case of large radio-planning projects,
embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case of large radioplanning projects, saving your path loss matrices externally will help reduce the size of the file and the use of computer
resources.
The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same
radio-planning document and share the path loss matrices. In this case, the radio data is stored in a database and the path
loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to radio data made
by all users. For more information on working in a multi-user environment, see the Administrator Manual.
When you save the path loss matrices to an external directory, Atoll creates:
One file per transmitter with the extension LOS for its main path loss matrix
A DBF file with validity information for all the main matrices.
A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
To set the storage location of the path loss matrices:

4. On the Predictions tab, under Path loss matrix storage, you can set the location for your private path loss matrices
and the location for the shared path loss matrices:
-
Private directory: The Private directory is where you store path loss matrices you generate or, if you are loading
path loss matrices from a shared location, where you store your changes to shared path loss matrices.
Click the button beside Private directory (
) and select Embedded to save the path loss matrices in the Atoll
document, or Browse to select a directory where Atoll can save the path loss matrices externally.
Path loss matrices you calculate locally are not stored in the same directory as shared path
loss matrices. Shared path loss matrices are stored in a read-only directory. In other words,
you can read the information from the shared path loss matrices but any changes you
make will be stored locally, either embedded in the ATL file or in a private external folder,
depending on what you have selected in Private directory.
When you save the path loss files externally, the external files are updated as soon as
calculations are performed and not only when you save the Atoll document. In order to
keep consistency between the Atoll document and the stored calculations, you should
save the Atoll document before closing it, if you have updated the path loss matrices.
-
Shared directory: When you are working in a multi-user Atoll environment, the project data is stored in a database
and the common path loss matrices are stored in a directory that is accessible to all users. Any changes you make
will not be saved to this directory; they will be saved in the location indicated in Private directory. The path loss
matrices in the shared directory are updated by a user with administrator rights based on the updated information
in the database. For more information on shared directories, see The Administrator Manual.
5. Click OK.
232

AT310_UMU_E0
Checking the Validity of Path Loss Matrices

Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want, you
can check whether the path loss matrices are valid without creating a coverage prediction.
To check whether the path loss matrices are valid:
-
-

Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices are
recalculated.
6. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue
appears (see Figure 6.16) with the total number of invalid path loss matrices and the reasons for invalidity, as well as
a summary of the reasons for invalidity.
Figure 6.16: Path loss matrix statistics
6.2.10.2 Assigning a Propagation Model

In Atoll, you can assign a propagation model globally to all transmitters, to a defined group of transmitters, or a single transmitter. As well, you can assign a default propagation model for coverage predictions. This propagation model is used for all
transmitters where the main propagation model selected is "(Default model)."
Because you can assign a propagation model in several different ways, it is important to understand which propagation model
Atoll will use:
1. If you have assigned a propagation model to a single transmitter, as explained in "Assigning a Propagation Model to
One Transmitter" on page 235, or to a group of transmitters, as explained in "Assigning a Propagation Model to a
Group of Transmitters" on page 234, this is the propagation model that will be used.
The propagation model assigned to an individual transmitter or to a group of transmitters will always have precedence
over any other assigned propagation model.
2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation Model
to All Transmitters" on page 234, this is the propagation model that will be used for all transmitters, except for those
to which you will later assign a propagation model either individually or as part of a group.
233

Forsk 2011
When you assign a propagation model globally, you override any selection you might
have already made to an individual transmitter or to a group of transmitters.
3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default Propagation Model" on page 175, this is the propagation model that will be used for all transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main propagation
model, that is the propagation model that will be used.
"Assigning a Propagation Model to All Transmitters" on page 234

"Assigning a Propagation Model to a Group of Transmitters" on page 234
"Assigning a Propagation Model to One Transmitter" on page 235.
Assigning a Propagation Model to All Transmitters

In Atoll, you can choose a propagation model per transmitter or globally.
To define a main and extended propagation model for all transmitters:
-


-

7. Click OK. The selected propagation models will be used for all transmitters.
Setting a different main or extended matrix on an individual transmitter as explained in
"Assigning a Propagation Model to One Transmitter" on page 235 will override this entry.
Assigning a Propagation Model to a Group of Transmitters

Transmitters that share the same parameters and environment will usually use the same propagation model and settings. In
Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common parameters
and then assigning the propagation model.
To define a main and extended propagation model for a defined group of transmitters:
3. Select from the Group by submenu of the context menu the property by which you want to group the transmitters.
The objects in the folder are grouped by that property.
You can group transmitters by several properties by using the Group By button on the
Properties dialogue. For more information, see "Advanced Grouping" on page 66.
5. Right-click the group of transmitters to which you want to assign a main and extended propagation model. The context
menu appears.
group.
For each transmitter, you can set the propagation model parameters in the following columns:
-
234
Main Propagation Model

Main Calculation Radius (m)

AT310_UMU_E0
Main Resolution (m)

Extended Propagation Model
Extended Calculation Radius (m)
Extended Resolution (m)
To enter the same values in one column for all transmitters in the table:
) in the
button (
Assigning a Propagation Model to One Transmitter
If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model to a
single transmitter after you have assigned a main and extended propagation model globally or to a group of transmitters.
When you assign a main and extended propagation model to a single transmitter, it overrides any changes made globally.
To define a main and extended propagation model for all transmitters:
3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu
appears.
-


-

8. Click OK. The selected propagation models will be used for the selected transmitter.
6.2.10.3 The Calculation Process

When you create a coverage prediction and click the Calculate button (
), Atoll follows the following process:
1. Atoll first checks to see whether the path loss matrices exist and, if so, whether they are valid. There must be valid
path loss matrices for each active and filtered transmitter whose propagation radius intersects the rectangle containing the computation zone.
2. If the path loss matrices do not exist or are not valid, Atoll calculates them. There has to be at least one unlocked coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click the Calculate button (
).
3. Atoll calculates all unlocked coverage predictions in the Predictions folder. Atoll automatically locks the results of a
coverage prediction as soon as it is calculated, as indicated by the icon (
dictions folder.
You can stop any calculations in progress by clicking the Stop Calculations button
(
) beside the coverage prediction in the Pre-
) in the toolbar.
When you click the Force Calculation button (

) instead of the Calculate button,
Atoll calculates all path loss matrices, unlocked coverages, and pending simulations.
235

Forsk 2011
6.2.10.4 Creating a Computation Zone

To create a computation zone:
3. Right-click the Computation Zone. The context menu appears.

5. Draw the computation zone:
The computation zone is delimited by a red line. If you clear the computation zones visibility check box in the Zones
folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account.
You can also create a computation zone as follows:

Existing polygon: You can use any existing polygon on the map as a computation zone by right-clicking it and selecting
Use As > Computation Zone from the context menu. You can also combine an existing computation zone with any
existing polygon by right-clicking it on the map or in the Explorer window and selecting Add To > Computation Zone
from the context menu.
area, you can import it and use it as a computation zone. You can import it by right-clicking the Computation Zone on
the Geo tab and selecting Import from the context menu.
Fit to Map Window: You can create a computation zone the size of the map window by selecting Fit to Map Window
You can save the computation zone, so that you can use it in a different Atoll document,
in the following ways:
Saving the computation zone in the user configuration: For information on saving
the computation zone in the user configuration, see "Saving a User Configuration"
on page 76.
Exporting the computation zone: You can export the computation zone by rightclicking the Computation Zone on the Geo tab of the Explorer window and
selecting Export from the context menu.
6.2.10.5 Setting Transmitters or Cells as Active

When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the
current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Before you
define a coverage prediction, you must ensure that all the transmitters on the sites you want to study have been activated. In
the Explorer window, active transmitters are indicated with a red icon ( ) in the Transmitters folder and with the defined
colour on the map and inactive transmitters are indicated with an empty icon ( )in the Transmitters folder and on the map.
In Atoll, you can also set individual cells on a transmitter as active or inactive.
You can set an individual transmitter as active from its context menu or you can set more than one transmitter as active by
activating them from the Transmitters context menu, by activating the transmitters cells from the Cells table, or by selecting
the transmitters with a zone and activating them from the zones context menu.
To set an individual transmitter as active:
3. Right-click the transmitter you want to activate. The context menu appears.
4. Select Active Transmitter from the context menu. The transmitter is now active.
To set more than one transmitter as active using the Transmitters context menu:
2. Select the transmitters you want to set as active:
236

AT310_UMU_E0
To set all transmitters as active, right-click the Transmitters folder. The context menu appears.
To set a group of transmitters as active, click the Expand button ( ) to expand the Transmitters folder and rightclick the group of transmitters you want to set as active. The context menu appears.
3. Select Activate Transmitters from the context menu. The selected transmitters are set as active.
To set more than one transmitter as active using the Transmitters table:
3. Select Open Table. The Transmitters table appears with each transmitters parameters in a second row.
4. For each transmitter that you want to set as active, select the check box in the Active column.
To set more than one cell as active using the Cells table:
3. Select Cells > Open Table. The Cells table appears with each cells parameters in a row.
4. For each cell that you want to set as active, select the check box in the Active column.
To set transmitters as active using a zone:
2. Click the Expand button ( ) to the left of Zones folder to expand the folder.
3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears.
If you do not yet have a zone containing the transmitters you want to set as active, you can
draw a zone as explained in "Using Zones in the Map Window" on page 33.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active.
Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on
choosing and configuring a propagation model, see Chapter 5: Working with Calculations in Atoll.
Calculating path loss matrices can be extremely time and resource intensive when you are working on larger projects. Consequently, Atoll offers you the possibility of distributing path loss calculations on several computers. You can install the Atoll
computing server application on other workstations or on servers. Once the computing server application is installed on a
workstation or server, the computer is available for distributed path loss calculation to other computers on the network. For
information on distributed calculations, see the Administrator Manual.
6.2.10.6 Signal Level Coverage Predictions

Atoll offers a series of standard coverage predictions that are common to all radio technologies. Coverage predictions specific
to UMTS are covered in "UMTS-Specific Predictions" on page 251, "HSDPA Quality and Throughput Analysis" on page 267, and
"HSUPA Quality and Throughput Analysis" on page 269.
Once you have created and calculated a coverage prediction, you can use the coverage predictions context menu to make
the coverage prediction into a customised prediction which will appear in the Prediction Types dialogue. You can also select
Duplicate from the coverage predictions context menu to create a copy. By duplicating an existing prediction that has the
parameters you want to study, you can create a new coverage prediction more quickly than by creating a new coverage
prediction. If you clone a coverage prediction, by selecting Clone from the context menu, you can create a copy of the coverage prediction with the calculated coverage. You can then change the display, providing that the selected parameter does not
invalidate the calculated coverage prediction.
You can also save the list of all defined coverage predictions in a user configuration, allowing you or other users to load it into
a new Atoll document. When you save the list in a user configuration, the parameters of all existing coverage predictions are
saved; not just the parameters of calculated or displayed ones. For information on exporting user configurations, see "Saving
a User Configuration" on page 76.
The following standard coverage predictions are explained in this section:
6.2.10.6.1
"Making a Coverage Prediction by Signal Level" on page 237

"Making a Coverage Prediction by Transmitter" on page 239
"Making a Coverage Prediction on Overlapping Zones" on page 240.
Making a Coverage Prediction by Signal Level

A coverage prediction by signal level allows you to predict the best signal strength at each pixel. You can base the coverage
on the signal level, path loss, or total losses within a defined range.
237

Forsk 2011
To make a coverage prediction by signal level:

4. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction,
and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage
Location of Coverage Prediction Results" on page 190. Under Display configuration, you can create a Filter to select
which sites to display in the results. For information on filtering, see "Filtering Data" on page 71. The Group By and
Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction).
6. Click the Conditions tab (see Figure 6.17). On the Conditions tab, you can define the signals that will be considered
for each pixel.
-
At the top of the Conditions tab, you can set the range of signal level to be considered. In Figure 6.17, a signal level
less than or equal to -120 dBm will be considered.
Under Server, select "All" to consider all servers.
You can select the Carrier to be studied, or select "Best (All Bands)" to have the carrier selected according to the
carrier selection method defined for the site equipment. The coverage prediction displays the strength of the
received pilot signal.
Figure 6.17: Condition settings for a coverage prediction by signal level

7. Click the Display tab.
8. Choose to display the results by best signal level. The coverage prediction results will be in the form of thresholds. For
information on adjusting the display, see "Display Properties of Objects" on page 23.
Selecting "All" or "Best Signal Level" on the Conditions tab will give you the same results because Atoll displays the
results of the best server in either case. Selecting "Best Signal Level" necessitates, however, the longest time for calculation.
9. Once you have created the coverage prediction, you can calculate immediately or you can save it and calculate it later:
-
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately..
Calculate button (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 6.18).
238

AT310_UMU_E0
Figure 6.18: Coverage prediction by signal level
6.2.10.6.2
Making a Coverage Prediction by Transmitter

A coverage prediction by transmitter allows the user to predict which server is the best at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range.
To make a coverage prediction by transmitter:
4. Select Coverage by Transmitter and click OK. The Coverage by Transmitter Properties dialogue appears.
Location of Coverage Prediction Results" on page 190. Under Configuration, you can create a Filter to select which
sites to display in the results. You can also display the results grouped on the Network tab by one or more characteristics by clicking the Group By button, or you can display the results sorted by clicking the Sort button. For information
on filtering, see "Filtering Data" on page 71; for information on grouping, see "Advanced Grouping" on page 66; for
information on sorting, see "Advanced Sorting" on page 70.
for each pixel.
-
less than or equal to -120 dBm or greater then -85 dBm will be considered.
Under Server, select "Best signal level."

You can also define a Margin. Atoll will then consider the best signal level on each pixel and any other signal level
within the defined margin of the best one.
You can select the Carrier to be studied, or select "Best (All bands)" to have the carrier selected according to the
carrier selection method defined for the site equipment.
239

Forsk 2011
Figure 6.19: Condition settings for a coverage prediction by transmitter

For a coverage prediction by transmitter, the Display Type "Discrete Values" based on the Field "Transmitter" is
selected by default. Each coverage zone will then be displayed with the same colour as that defined for each transmitter. For information on defining transmitter colours, see "Display Properties of Objects" on page 23.
later:
-
Calculate button (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
You can also predict which server is the second best server on each pixel by selecting
"Second best signal level" on the Conditions tab setting "Discrete Values" as the Display
Type and "Transmitter" as the Field on the Display tab.
6.2.10.6.3
Making a Coverage Prediction on Overlapping Zones

Overlapping zones are composed of pixels that are, for a defined condition, covered by the signal of at least two transmitters.
You can base a coverage prediction of overlapping zones on the signal level, path loss, or total losses within a defined range.
To make a coverage prediction on overlapping zones:
4. Select Overlapping Zones and click OK. The Overlapping Zones Properties dialogue appears.
for each pixel.
-
240
less than or equal to -120 dBm will be considered.

AT310_UMU_E0
Under Server, select "Best signal level" and define a Margin. Atoll will then consider the best signal level on each
pixel and any other signal level within the defined margin of the best one.
You can select the Carrier to be studied, or select "Best (All bands)" to have the carrier selected according to the
carrier selection method defined for the site equipment. The coverage prediction displays the strength of the
received pilot signal.
Figure 6.20: Condition settings for a coverage prediction on overlapping zones

For a coverage prediction on overlapping zones, the Display Type "Value Intervals" based on the Field "Number of
Servers" is selected by default. Each overlapping zone will then be displayed in a colour corresponding to the number
of servers received per pixel. For information on defining display properties, see "Display Properties of Objects" on
page 23.
later:
-
Calculate button (
By changing the parameters selected on the Conditions tab and by selecting different
results to be displayed on the Display tab, you can calculate and display information other
than that which has been explained in the preceding sections.
6.2.10.7 Analysing a Coverage Prediction

Once you have completed a prediction, you can analyse the results with the tools that Atoll provides.
The results are displayed graphically in the map window according to the settings you made on the Display tab when you
created the coverage prediction (step 6. of "Studying Signal Level Coverage" on page 229). If several coverage predictions are
visible on the map, it might be difficult to clearly see the results of the coverage prediction you want to analyse. You can select
which predictions to display or to hide by selecting or clearing the display check box. For information on managing the display,
see "Displaying or Hiding Objects on the Map Using the Explorer" on page 18.
In this section, the following tools are explained:
"Displaying the Legend Window" on page 242

"Displaying Coverage Prediction Results Using Tip Text" on page 242
"Using the Point Analysis Reception View" on page 242
"Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 243
241

6.2.10.7.1
Forsk 2011
"Viewing Coverage Prediction Statistics" on page 245

"Comparing Coverage Predictions: Examples" on page 246.
Displaying the Legend Window

When you create a coverage prediction, you can add the displayed values of the coverage prediction to a legend by selecting
the Add to Legend check box on the Display tab.
6.2.10.7.2
Select View > Legend Window. The Legend window is displayed, with the values for each displayed coverage prediction identified by the name of the coverage prediction.
Displaying Coverage Prediction Results Using Tip Text

You can get information by placing the pointer over an area of the coverage prediction to read the information displayed in
the tip text. The information displayed is defined by the settings you made on the Display tab when you created the coverage
prediction (step 6. of "Studying Signal Level Coverage" on page 229).
To get coverage prediction results in the form of tip text:
In the map window, place the pointer over the area of the coverage prediction that you want more information on.
After a brief pause, the tip text appears with the information defined in the Display tab of the coverage prediction
properties (see Figure 6.21).
Figure 6.21: Displaying coverage prediction results using the tip text
6.2.10.7.3
Using the Point Analysis Reception View

Once you have calculated the coverage prediction, you can use the Point Analysis tool.
pointer changes (
) in the Radio Planning toolbar. The Point Analysis window appears and the
) to represent the receiver.
2. At the top of the Point Analysis window, select the Reception view (see Figure 6.22).
The predicted signal level from different transmitters is reported in the Reception view in the form of a bar chart, from
the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the colour of
the transmitter it represents. In the map window, arrows from the pointer to each transmitter are displayed in the
colour of the transmitters they represent. A thick black line from the pointer to its best server is also displayed in the
map window. The best server of the pointer is the transmitter from which the pointer receives the highest signal level.
If you let the pointer rest, the signal level received from the corresponding transmitter at the pointer location is
displayed in the tip text.
3. At the top of the Reception view, select the carrier to be analysed.
Figure 6.22: Point Analysis - Reception tab
242

AT310_UMU_E0
4. At the top of the Reception view, you can click one of the following buttons:
-
: Click the Options button (

-
Change the X and Y coordinates to change the present position of the receiver.
Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability.
: Click the Copy button (

) to copy the Reception view. You can then paste the contents of the Reception
view as a graphic into a graphic editing or word-processing programme.
: Click the Print button (
) to print the Reception view.
You can also select the Details view from the top of the Point Analysis window to get more information. The Details view
displays the profile of the receiver (the combination of terminal, service, mobility, and carrier) and, for each transmitter, its
distance from the receiver, its signal level (or RSCP), its path loss, Ec/Io, DL and UL Eb/Nt values, and scrambling code.
6.2.10.7.4
Creating a Focus Zone or Hot Spot for a Coverage Prediction Report

The focus zone and hot spots define an area on which statistics can be drawn and on which reports are made. While you can
only have one focus zone, you can define several hot spots in addition to the focus zone.
It is important not to confuse the computation zone and the focus zone and hot spots. The computation zone defines the area
where Atoll calculates path loss matrices, coverage predictions, Monte Carlo, power control simulations, etc., while the focus
zone and hot spots are the areas taken into consideration when generating reports and results. When you create a coverage
prediction report, it gives the results for the focus zone and for each of the defined hot spots.
To define a focus zone or hot spot:
3. Right-click the Focus Zone or Hot Spots, depending on whether you want to create a focus zone or a hot spot. The
context menu appears.
5. Draw the focus zone or hot spot:
A focus zone is delimited by a green line; a hot spot is delimited by a heavy black line. If you clear the zones visibility
check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken
into account.
You can also create a focus zone or hot spot as follows:

Existing polygon: You can use any existing polygon on the map as a focus zone or hot spot by right-clicking it and
selecting Use As > Focus Zone or Use As > Hot Spot from the context menu. You can also combine an existing focus
zone or hot spot with any existing polygon by right-clicking it on the map or in the Explorer window and selecting Add
To > Hot Spot or Add To > Hot Spot from the context menu.
area, you can import it and use it as a focus zone or hot spot. You can import it by right-clicking the Focus Zone folder
or Hot Spots on the Geo tab and selecting Import from the context menu. When you import hot spots, you can import
the name given to each zone as well.
Fit to Map Window: You can create a focus zone or hot spot the size of the map window by selecting Fit to Map
Window from the context menu.
243

Forsk 2011
You can save the focus zone or hot spots in the following ways, so that you can use it in a
different Atoll document:
Saving the focus zone in the user configuration: For information on saving the
focus zone in the user configuration, see "Saving a User Configuration" on page 76.
Exporting the focus zone or hot spots: You can export the focus zone or hot spots
by right-clicking the Focus Zone or the Hot Spots folder on the Geo tab of the
Explorer window and selecting Export from the context menu.
You can include population statistics in the focus zone or hot spot by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data
File" on page 111.
6.2.10.7.5
Displaying a Coverage Prediction Report

Atoll can generate a report for any coverage prediction whose display check box is selected ( ). The report displays the
covered surface and percentage for each threshold value defined in the Display tab of the coverage predictions Properties
dialogue.
The coverage prediction report is displayed in a table. By default, the report table only displays the name and coverage area
columns. You can edit the table to select which columns to display or to hide. For information on displaying and hiding
columns, see "Displaying or Hiding a Column" on page 52.
Atoll bases the report on the area covered by the focus zone and hot spots; if no focus zone is defined, Atoll will use the
computation zone. However, by using a focus zone for the report, you can create a report for a specific number of sites,
instead of creating a report for every site that has been calculated.
The focus zone or hot spot must be defined before you display a report; it is not necessary to define it before calculating coverage. The focus zone or hot spot does not, however, need to be visible; even if it is not displayed, Atoll will take it into account
when generating the report. For information on defining a focus zone or hot spot, see "Creating a Focus Zone or Hot Spot for
a Coverage Prediction Report" on page 243.
Atoll can generate a report for a single prediction, or for all displayed predictions.
To display a report on a single coverage prediction:
3. Right-click the coverage prediction for which you want to generate a report. The context menu appears.
4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears.
5. Define the format and content of the report:
You can select the columns that will be displayed in the report and define the order they are in:
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking
to move it down.
to move it up or
You can load a configuration that you have saved previously and apply it to the current report:
a. Under Configuration, click the Load button. The Open dialogue appears.
b. Select the configuration you want to load and click Open. The loaded report configuration is applied.
You can save the current report format in a configuration:
a. Under Configuration, click the Save button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report is based on the hot spots and on the focus zone if
available or on the hot spots and computation zone if there is no focus zone.
To display a report on all coverage predictions:
3. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears.
4. Define the format and content of the report:
244

AT310_UMU_E0
You can select the columns that will be displayed in the report and define the order they are in:
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking
to move it down.
to move it up or
You can save the current report format in a configuration:

a. Under Configuration, click the Save button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can load a configuration that you have saved previously and apply it to the current report:
a. Under Configuration, click the Load button. The Open dialogue appears.
b. Select the configuration you want to load and click Open. The loaded report configuration is applied.
5. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in the same
order as in the Predictions folder. The report is based on the focus zone if available or on the calculation zone if there
is no focus zone.
You can include population statistics in the focus zone or hot spots by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 111. Normally, Atoll takes all geo data into consideration,
whether it is displayed or not. However, for the population statistics to be used in a report, the population map has to be
displayed.
To include population statistics in the focus zone or hot spots:
1. Ensure that the population geo data is visible. For information on displaying geo data, see "Displaying or Hiding
Objects on the Map Using the Explorer" on page 18.
2. Display the report as explained above.
3. Select Format > Display Columns. The Columns to Be Displayed dialogue appears.
4. Select the following columns, where "Population" is the name of the folder on the Geo tab containing the population
map:
-
"Population" (Population): The number of inhabitants covered.

"Population" (% Population): The percentage of inhabitants covered.
"Population" (Population [total]: The total number of inhabitants inside the zone.
Atoll saves the names of the columns you select and will automatically select them the next time you create a coverage prediction report.
5. Click OK.
If you have created a custom data map with integrable data, the data can be used in prediction reports. The data will be
summed over the coverage area for each item in the report (for example, by transmitter or threshold). The data can be value
data (revenue, number of customers, etc.) or density data (revenue/km, number of customer/km, etc.). Data is considered
as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example, socio-demographic
classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable Versus Non Integrable Data"
on page 129.
6.2.10.7.6
Viewing Coverage Prediction Statistics

Atoll can display statistics for any coverage prediction whose display check box is selected ( ). By default, Atoll displays a
histogram using the coverage prediction colours, interval steps, and shading as defined on the Display tab of the coverage
predictions Properties dialogue. You can also display a cumulative distribution function (CDF) or an inverse CDF (1 - CDF). For
a CDF or an inverse CDF, the resulting values are combined and shown along a curve. You can also display the histogram or
the CDFs as percentages of the covered area.
Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation
zone. However, by using a focus zone for the report, you can display the statistics for a specific number of sites, instead of
displaying statistics for every site that has been calculated. Hot spots are not taken into consideration when displaying statistics.
The focus zone must be defined before you display statistics; it is not necessary to define it before calculating coverage. For
information on defining a focus zone, see "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 243.
To display the statistics on a coverage prediction:
3. Right-click the coverage prediction whose statistics you want to display. The context menu appears.
245

Forsk 2011
4. Select Histogram from the context menu. The Statistics dialogue appears with a histogram of the area defined by the
focus zone (see Figure 6.23).
-
Under Histogram Based on Covered Areas, you can select to view a histogram, CDF, or inverse CDF based on area
or percentage.
The Detailed Results section displays the covered area values, or the percentage of the covered area, along the yaxis against the coverage criterion along the x-axis.
You can copy the graph by clicking the Copy button.
You can print the graph by clicking the Print button.
Under Statistics Based on Prediction Conditions, you can view the mean and standard deviation of the coverage
criterion calculated during the coverage calculations, if available.
Figure 6.23: Histogram of a coverage prediction by signal level
6.2.10.7.7
Comparing Coverage Predictions: Examples

Atoll allows you to compare two similar predictions to see the differences between them. This enables you to quickly see how
changes you make affect the network.
In this section, there are two examples to explain how you can compare two similar predictions. You can display the results
of the comparison in one of the following ways:
Intersection: This display shows the area where both prediction coverages overlap (for example, pixels covered by
both predictions are displayed in red).
Union: This display shows all pixels covered by both coverage predictions in one colour and pixels covered by only one
coverage prediction in a different colour (for example, pixels covered by both predictions are red and pixels covered
by only one prediction are blue).
Difference: This display shows all pixels covered by both coverage predictions in one colour, pixels covered by only
the first prediction with another colour and pixels covered only by the second prediction with a third colour (for
example, pixels covered by both predictions are red, pixels covered only by the first prediction are green, and pixels
covered only by the second prediction are blue).
To compare two similar coverage predictions:

1. Create and calculate a coverage prediction of the existing network.
2. Examine the coverage prediction to see where coverage can be improved.
3. Make the changes to the network to improve coverage.
4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged).
5. Calculate the duplicated coverage prediction.
246

AT310_UMU_E0
6. Compare the original coverage prediction with the new coverage prediction. Atoll displays differences in coverage
between them.
In this section, the following examples are explained:
"Example 1: Studying the Effect of a New Base Station" on page 247

"Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 249.
Example 1: Studying the Effect of a New Base Station

If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, you can verify if a newly added base station improves coverage.
A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal
Level" on page 237. The results are displayed in Figure 6.24. An area with poor coverage is visible on the right side of the
figure.
Figure 6.24: Signal level coverage prediction of existing network

A new base station is added, either by creating the site and adding the transmitters, as explained in "Creating a UMTS Base
Station" on page 201, or by placing a station template, as explained in "Placing a New Station Using a Station Template" on
page 210. Once the new site base station been added, the original coverage prediction can be recalculated, but then it would
be impossible to compare the results. Instead, the original signal level coverage prediction can be copied by selecting Duplicate from its context menu. The copy is then calculated to show the effect of the new site (see Figure 6.25).
247

Forsk 2011
Figure 6.25: Signal level coverage prediction of network with new base station
Now you can compare the two predictions.
To compare two predictions:
1. Right-click one of the two predictions. The context menu appears.
2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you want
to compare with the first. The Comparison Properties dialogue appears.
3. Click the General tab. You can change the Name of the comparison and add Comments.
The General tab contains information about the coverage predictions being compared, including their name and resolution.
4. Click the Display tab. On the Display tab, you can choose how you want the results of the comparison to be displayed.
You can choose among:
-
Intersection
Union
Difference
In order to see what changes adding a new base station made, you should choose Difference.
5. Click OK to create the comparison. The comparison in Figure 6.26, shows clearly the area covered only by the new
base station.
248

AT310_UMU_E0
Figure 6.26: Comparison of both signal level coverage predictions

Example 2: Studying the Effect of a Change in Transmitter Tilt
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, you can see how modifying transmitter tilt can improve coverage.
A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by Transmitter" on page 239. The results are displayed in Figure 6.27. The coverage prediction shows that one transmitter is covering
its area poorly. The area is indicated by a red oval in Figure 6.27.
Figure 6.27: Coverage prediction by transmitter of existing network

You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed
by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue.
Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it would be
impossible to compare the results. Instead, the original coverage prediction by can be copied by selecting Duplicate from its
context menu. The copy is then calculated, to show how modifying the antenna tilt has affected coverage (see Figure 6.28).
249

Forsk 2011
Figure 6.28: Coverage prediction by transmitter of network after modifications

As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change in
coverage, you can compare the two predictions.
To compare two predictions:
1. Right-click one of the two predictions. The context menu appears.
2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you want
to compare with the first. The Comparison Properties dialogue appears.
3. Click the General tab. You can change the Name of the comparison and add Comments.
The General tab contains information about the coverage predictions being compared, including their name and resolution.
4. Click the Display tab. On the Display tab, you can choose how you want the results of the comparison to be displayed.
You can choose among:
-
Intersection
Union
Difference
In order to see what changes modifying the antenna tilt made, you can choose Union. This will display all pixels
covered by both predictions in one colour and all pixels covered by only one prediction in another colour. The increase
in coverage, seen in only the second coverage prediction, will be immediately clear.
5. Click OK to create the comparison. The comparison in Figure 6.29, shows clearly the increase in coverage due to the
change in antenna tilt.
Figure 6.29: Comparison of both transmitter coverage predictions
250

AT310_UMU_E0
6.2.10.8 UMTS-Specific Predictions

In UMTS, the quality of the signal and the size of the area that can be covered are influenced by the network load. As the
network load increases, the area a cell can effectively cover decreases. For this reason, the network load must be defined in
order to calculate UMTS-specific predictions.
If you have traffic maps, you can do a Monte-Carlo simulation to model power control and evaluate the network load for a
generated user distribution. If you do not have traffic maps, Atoll can calculate the network load using the UL load factor and
DL total power defined for each cell.
In this section, the UMTS-specific coverage predictions will be calculated using UL load factor and DL total power parameters
defined at the cell level. For the purposes of these predictions, each pixel is considered a non-interfering user with a defined
service, mobility type, and terminal.
Before making a coverage prediction, you will have to set the UL load factor and DL total power and the parameters that
define the services and users. These are explained in the following sections:
"Setting the UL Load Factor and the DL Total Power" on page 251.
"Service and User Modelling" on page 252.
Several different types of UMTS-specific coverage predictions are explained in this section:
"Making a Pilot Signal Quality Prediction" on page 256

"Studying Service Area (Eb Nt) Downlink or Uplink" on page 258
"Studying the Effective Service Area" on page 259.
The following noise predictions, also coverage predictions, are explained:
"Studying the Total Noise Level on the Downlink" on page 261

"Calculating Pilot Pollution" on page 262
"Studying Inter-Technology Downlink Interference" on page 263.
Another type of coverage prediction, the handover prediction, is also explained:
"Making a Handoff Status Coverage Prediction" on page 264.
You can also make a point analysis using the Point Analysis window. The analysis is calculated using UL load factor and DL total
power parameters defined at the cell level and provided for a user-definable probe receiver which has a terminal, a mobility
and a service:
"Making an AS Analysis" on page 265.
Interference from an external project can also be modelled. For an explanation of modelling external interference, see
"Modelling Inter-Technology Interference" on page 420.
6.2.10.8.1
Setting the UL Load Factor and the DL Total Power

If you are setting the UL load factor and the DL total power for a single transmitter, you can set these parameters on the Cells
tab of the transmitters Properties dialogue. However, you can set the UL load factor and the DL total power for all cells using
the Cells table.
To set the UL load factor and the DL total power using the Cells table:
3. Select Cells > Open Table from the context menu. The Cells table appears.
4. Enter a value in the following columns:
-
Total Power (dBm)

UL Load Factor (%)
For a definition of the values, see "Cell Definition" on page 205.
To enter the same values in one column for all cells in the table:
) in the
251

Forsk 2011
button (
6.2.10.8.2
Service and User Modelling

Before you can model services, you must already have R99 radio bearers defined in your Atoll document. Only the following
R99 radio bearer parameters are used in predictions:
Max TCH Power (dBm)

The type of bearer.
For information on defining R99 radio bearers, "Defining R99 Radio Bearers" on page 412.
"Modelling UMTS HSPA Services" on page 252

"Creating a UMTS HSPA Mobility Type" on page 254
"Modelling UMTS HSPA Terminals" on page 255.
Modelling UMTS HSPA Services

Services are the various services available to subscribers. These services can be either circuit-switched or packet-switched
services. This section explains how to create a service. However, only the following parameters are used in predictions:
R99 bearer parameters

Downgrading capabilities
Handover capabilities
HSPA capabilities
Body loss
HSPA application throughput parameters
Before you can model services, you must have defined R99 bearers. For information on defining R99 radio bearers, see "Defining R99 Radio Bearers" on page 412.
To create or modify a service:
) to expand the Traffic Parameters folder.
3. Right-click the Services folder. The context menu appears.

4. Select New from the context menu. The Services New Element Properties dialogue appears.
You can modify the properties of an existing service by right-clicking the service in the Services folder and selecting Properties from the context menu.
5. Edit the fields on the General tab to define the new service:
-
Name: Atoll proposes a name for the new service, but you can change the name to something more descriptive.
Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity for each
user during Monte-Carlo simulations. For packet-switched services, this parameter is used when working with
sector traffic maps and user density traffic maps. For circuit-switched services, the parameter is taken into consideration with any traffic map.
Average Requested Rate: You can enter the average requested rate for uplink and downlink. This rate is the
average rate obtained by a user of the service. How the average requested rate is used in Atoll depends on the
type of service:
-
Circuit (R99): This rate is the average rate obtained by a user of the service. It is used in simulations during
user distribution generation to calculate the number of users attempting a connection and to determine their
activity status.
Packet (R99): This rate is the average rate obtained by a user of the service. It is used in simulations during
user distribution generation to calculate the number of users attempting a connection and to determine their
activity status.
Packet (HSPA): This rate is the requested average rate which guarantees a minimum average rate during an
HSUPA call. It is used twice in a simulation: once during user distribution generation in order to calculate the
number of HSUPA users attempting a connection and then during power control as a quality target to be
compared to the real obtained average throughput.
6. Click the UMTS tab to define the new service.
252

AT310_UMU_E0
7. Select an R99 Radio Bearer from the list. If you want to edit the settings of the selected R99 radio bearer, click the
Browse button (
) to open the bearers Properties dialogue.
8. Select a service Type:

-
Circuit (R99): For circuit services, select Circuit (R99).

Packet (R99): For packet services that can only use R99 channels, select Packet (R99).
Packet (HSDPA Best Effort): For packet services that can use HSDPA channels, select Packet (HSDPA Best Effort).
The HSDPA service is linked to a R99 bearer in order to manage the connection to the R99dedicated channel A-DPCH.
Packet (HSPA Best Effort): For packet services that can use HSDPA and HSUPA channels, select Packet (HSPA Best
Effort).
Packet (HSPA-Constant Bit Rate): For packet services requiring a minimum bit rate and using HSPA channels (e.g.,
voice over IP), select Packet (HSPA - Constant Bit Rate).
9. For all types of services, define the following parameters:

-
Preferred/Allowed Carrier: You can select one of the available carriers or all carriers. The specified carrier is considered in simulation when admitting a transmitter to the mobile active set. If you select "Preferred Carrier" and
the transmitter uses the specified carrier, Atoll selects it. Otherwise, it will choose another one, using the carrier
selection mode defined in the site equipment properties. The carrier specified for the service is not used in predictions (i.e., AS analysis and coverage predictions). In predictions, Atoll considers the carrier selection mode
defined in the site equipment properties. If no preferred carrier is specified in the service properties, it will consider the carrier selection mode defined in the site equipment properties.
If you select "Allowed Carrier," Atoll will only use the defined carriers. If they are not available, service will be rejected.
Bearer Downgrading: Select the Bearer downgrading check box if the service supports bearer downgrading on
uplink and downkink.
Soft Handoff Allowed: Select the Soft Handoff Allowed check box if you want the network to be able to use soft
handoff with this service.
HSDPA channels do not use soft handover even if the Soft Handoff Allowed check box is
selected. If you want the HSUPA service to be operated using soft handover, select the Soft
Handoff Allowed check box. Soft handover will be applied to R99 and HSUPA channels
only.
Priority: Enter a priority for this service. "0" is the lowest priority.
Body Loss: Enter a body loss for the service. The body loss is the loss due to the body of the user. For example, in
a voice connection the body loss, due to the proximity of the users head, is estimated to be 3dB.
10. If you selected Circuit (R99) as the Type in step 8., continue to step 13. If you selected Packet (R99), Packet (HSDPA
Best Effort), Packet (HSPA Best Effort), or Packet (HSPA - Constant Bit Rate) as the Type in step 8., click the Packet
button to define the parameters used to determine the probability of activity for each user during Monte-Carlo simulations. These parameters are used when working with user profile traffic maps only. Click the Packet tab.
In the Packet dialogue, you can set the following parameters for packet-switched services:
-
Under BLER, you can define the following:

-
Under Session, you can set:

-
Efficiency Factor: The uplink and downlink efficiency factors are used to determine duration of usage by the
user during Monte-Carlo simulations.
Average Number of Packet Calls: Enter the average number of packet calls in the uplink and downlink during
one session.
Average Time Between Two Packet Calls: Enter the average time between two packet calls (in milliseconds)
in the uplink and downlink.
Under Packet Calls, you can set:

-
Min. Size (Kbytes): Enter the minimum size of a packet call in kilobytes in the uplink and downlink.
Max Size (Kbytes): Enter the maximum size of a packet call in kilobytes in the uplink and downlink.
Average Time Between Two Packets (ms): Enter the average time between two packets in milliseconds in the
uplink and downlink.
253

Forsk 2011
Under Packet, you can set:

-
Size (Bytes): Enter the packet size in bytes in the uplink and downlink.
11. Click Commit to save your changes and close the Packet dialogue when you have finished setting the parameters.
12. If you selected a packet service (i.e., Packet (HSDPA Best Effort), Packet (HSPA Best Effort), or Packet (HSPA - Constant Bit Rate) as the Type in step 8., set the following parameters:
Under Application Throughput:
-
Set a Scaling Factor between the application throughput and the RLC (Radio Link Control) throughput and a
throughput Offset. These parameters model the header information and other supplementary data that does not
appear at the application level.
For Packet (HSDPA Best Effort) services, set the following parameters under HSPA Parameters:
-
E-DPCCH/A-DPCH Activity Factor: The downlink E-DPCCH/A-DPCH activity factor is used to estimate the average
power on A-DPCH channels.
For Packet (HSPA Best Effort) services, set the following parameters under HSPA Parameters:
-
E-DPCCH/A-DPCH Activity Factor: The uplink and downlink E-DPCCH/A-DPCH activity factors are used to estimate
the average power on E-DPCCH and A-DPCH channels.
For Packet (HSPA Constant Bit Rate) service, set the following parameters under HSPA Parameters:
-
E-DPCCH/A-DPCH Activity Factor: The E-DPCCH/A-DPCH activity factor is used to estimate the average power on
A-DPCH channels.
Guaranteed Bit Rate: Enter the minimum required bit rate that the service should have in order to be available in
the uplink and downlink.
13. Click OK.

Creating a UMTS HSPA Mobility Type
In UMTS, information about receiver mobility is important to efficiently manage the active set: a mobile used by someone
travelling a certain speed and a mobile used by a pedestrian will not necessarily be connected to the same transmi ers. Ec I0
requirements and Eb/Nt targets per radio bearer and per link (up and down) are largely dependent on mobile speed.
The following parameters are used in predictions:
Ec I0 threshold
HS-SCCH Ec Nt Threshold
To create or modify a mobility type:

3. Right-click the Mobility Types folder. The context menu appears.

4. Select New from the context menu. The Mobility Types New Element Properties dialogue appears.
You can modify the properties of an existing mobility type by right-clicking the mobility
type in the Mobility Types folder and selecting Properties from the context menu.
5. On the General tab, you can enter or modify the following parameters in the Mobility Types New Element Properties
dialogue:
-
Name: Enter or modify the descriptive name for the mobility type.
Speed: Enter or modify an average speed for the mobility type. This field is for information only; the average speed
is not used by any calculation.
6. On the Parameters tab, you can enter or modify the following parameters in the Mobility Types New Element Properties dialogue:
-
EcI0 Threshold: Under Active Set Management, enter or modify the minimum Ec I0 required from a transmi er
to enter the active set. This value must be verified for the best server.
HS-SCCH EcNt Threshold: Under HSDPA, enter or modify the minimum quality required in order for the HSDPA
link to be available. This parameter is used by Atoll to determine the HS-SCCH power when the user has selected
dynamic allocation in the cell properties. For static allocation, Atoll calculates the HS-SCCH Ec Nt from the
HS-SCCH power set in the cell properties and compares it to this threshold. This field is only used with HSDPA.
7. Click OK.
254

AT310_UMU_E0
Modelling UMTS HSPA Terminals

In UMTS, a terminal is the user equipment that is used in the network, for example, a mobile phone, a PDA, or a cars on-board
navigation device.
The following parameters are used in predictions:
Receiver equipment
Main and secondary bands
Maximum terminal power
Gain and losses
Noise figures
Active set size
DL rake factor
CDMA Rho factor
Compressed mode capability
HSPA capability and HSPA-specific categories:
-
UE category
Number of reception antenna ports
MUD factor (for HSDPA only).
To create or modify a terminal:

3. Right-click the Terminals folder. The context menu appears.

4. Select New from the context menu. The Terminals New Element Properties dialogue appears.
You can modify the properties of an existing terminal by right-clicking the terminal in the
Terminal folder and selecting Properties from the context menu.
5. Click the General tab. You can modify the following parameter:
-
Name: You can change the name of the terminal.
6. Click the Parameters tab. You can modify the following parameters:
Under Transmission/Reception:
-
UMTS Equipment: Select a type of reception equipment from the list.

You can create a new type of reception equipment by using the Reception Equipment
table. You can open open the Reception Equipment table by clicking the Expand button
( ) to expand the UMTS Network Settings folder, and then right-clicking the Reception
Equipment folder and selecting Open Table from the context menu.
Min. Power: Set the minimum transmission power. The minimum and maximum transmission power make up the
dynamic range for uplink power control.
Max Power: Set the maximum transmission power.
Gain: Set the antenna gain.
Losses: Set the reception losses.
Active Set Size: Set the active set size. The active set size is the maximum number of transmitters to which a terminal can be connected at one time.
DL Rake Factor: Set the DL rake factor. This enables Atoll to model the rake receiver on DL.
The rake efficiency factor, used for calculating recombination in uplink has to be set in the
site equipment properties. For information on setting site equipment properties, see
"Creating Site Equipment" on page 413.
CDMA Rho factor (%): This parameter enables Atoll to take into account the self-interference produced by the
terminal. Because hardware equipment is not perfect, the input signal experiences some distortion which affects,
in turn, the output signal. This factor defines how much distortion the system generates. Entering 100% means
the system is perfect (there is no distortion) and the output signal will be 100% equal to the input signal. On the
other hand, if you specify a value different than 100%, Atoll considers that the transmitted energy is not 100%
signal and contains a small percentage of interference generated by the equipment, i.e., self-interference. Atoll
considers this parameter to calculate the signal to noise ratio in the uplink.
255

Forsk 2011
Compressed Mode Supported: Check the Compressed Mode Supported check box if the terminal uses compressed mode. Compressed mode is generally used to prepare hard-handover of users with single receiver terminals.
Under Frequency Bands:

-
Main Band: Select the frequency band with which the terminal is compatible and enter the terminal Noise Figure
for the main frequency.
Secondary Band: Select a second frequency band with which the terminal is compatible and enter the terminal
Noise Figure for the second frequency. Leave the Secondary Band field empty if the terminal works only on one
frequency band.
There are two different ways of defining dual-band terminals. Depending on the configuration, Atoll processes dual-band terminal users differently in the Monte-Carlo simulation.
The first one consists of defining main and secondary frequency bands. This enables you to give a higher priority to one frequency band in the Monte-Carlo simulation (the main frequency band will have the higher priority). A user with such a
dual-band terminal will be connected to transmitters using the main frequency
band if carriers on this frequency band are not overloaded. In case of overloading,
he will be connected to transmitters using the secondary frequency band.
The second consists of selecting "All" as main frequency band. This means that the
terminal works on any frequency band without any priority. In this case, the user
can be connected to transmitters using any frequency band.
In coverage predictions, both configurations give the same results. The priority of
frequency bands is not taken into account.
Select the type of HSPA Support the terminal has: None (i.e., R99 support only), HSDPA or HSPA (i.e., HSDPA and
HSUPA).
If the terminal supports HSDPA, you can define the HSDPA parameters under HSDPA:
-
UE Category: Select the HSDPA user equipment category of the terminal.

MUD Factor: Enter a multi-user detection factor (MUD). MUD is based on an algorithm used to improve mobile
receiver capacity. It reduces intra-cell interference and allows for higher Ec Nt. MUD is modelled by a coecient
from 0 to 1; this factor is considered in calculating DL interference. If MUD is not supported, enter "0."
Number of Reception Antenna Ports: Select the number of reception antenna ports available on the terminal for
MIMO.
If the terminal supports HSUPA, you can define the HSUPA parameters under HSUPA:
-
UE Category: Select the HSUPA user equipment category of the terminal.
7. Click OK.
6.2.10.8.3
Making Quality Predictions

In Atoll, you can make several predictions to study the quality. In this section, the following quality predictions are explained:
"Making a Pilot Signal Quality Prediction" on page 256

"Studying Service Area (Eb Nt) Downlink or Uplink" on page 258
"Studying the Effective Service Area" on page 259
"Creating a Quality Coverage Prediction Using Quality Indicators" on page 260.
A table listing quality indicators (BER, BLER, etc.) to be analysed is available. Quality predictions proposed by Atoll depend on quality indicators specified in this table.
Making a Pilot Signal Quality Prediction

A pilot signal quality prediction enables you to identify areas where there is at least one transmitter whose pilot quality is
received sufficiently well to be added to the probe mobile active set.
Atoll calculates the best pilot quality received on each pixel. Then, depending on the coverage prediction definition, it
compares this value either to the Ec I0 threshold defined for the selected mobility type, or to user-defined Ec I0 thresholds.
256

AT310_UMU_E0
The pixel is coloured if the condi on is fulfilled (in other words, if the best Ec I0 is higher than the Ec I0 mobility threshold or
specified Ec I0 thresholds).
To make a pilot signal quality prediction:
4. Select Pilot Quality Analysis (Ec/I0) and click OK. The Pilot Quality Analysis (Ec/I0) Properties dialogue appears.
6. Click the Conditions tab (see Figure 6.30).
Select "(Cells Table)" from Load conditions. In this case, the coverage prediction is not going to be based on load
conditions taken from a simulation. Atoll will calculate the coverage prediction using the UL load factor and the DL
total power defined in the cell properties.
When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 252. You must
also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the
"Best (Main band)" carrier selected according to the carrier selection method defined for the site equipment.
If you want the pilot signal quality prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell edge coverage probability text box.
You can also select the Indoor coverage check box to add indoor losses.
Figure 6.30: Load condition settings for a coverage prediction on pilot quality
For a pilot signal quality prediction, the Display Type "Value Intervals" based on the Field "Ec I0 (dB)" is selected by
default. Each pixel is displayed in a colour corresponding to the pilot signal quality. For information on defining display
properties, see "Display Properties of Objects" on page 23.
You can also set parameters to display the following results:
-
Where at least one transmitter is in the active set: Select "Unique" as the Display Type.
257

Forsk 2011
Where at least one transmitter is in the active set, with information on the best server: Select "Discrete Value"
as the Display Type and "Transmitter" as the Field.
The pilot quality rela ve to the EcI0 threshold: Select "Value Intervals" as the Display Type and "Ec I0 margin
(dB)" as the Field.
later:
-
Calculate button (
Studying Service Area (EbNt) Downlink or Uplink
Atoll calculates the trac channel quality (as defined by Eb Nt) when using the maximum power allowed, i.e., the maximum
traffic channel power allowed per cell for downlink and the maximum terminal power for uplink. In the coverage prediction,
the downlink or uplink service area is limited by the maximum power allowed and by the pilot quality. If the received pilot
quality is insufficient, Atoll will not display the traffic channel quality. The mobile handover status is taken in consideration to
evaluate the downlink and uplink trac channel quality (Eb Nt). Atoll combines the signal from each transmitter in the probe
mobile active set.
To make a coverage prediction on service area (Eb/Nt) downlink or uplink:
4. Select one of the following predictions and click OK:
-
Service Area Analysis (Eb/Nt) (DL)

Service Area Analysis (Eb/Nt) (UL)
The coverage prediction Properties dialogue appears.

6. Click the Conditions tab.
If you want the service area (Eb Nt) coverage predic on to consider shadowing, you can select the Shadowing taken
into account check box and enter a percentage in the Cell edge coverage probability text box.
You can select the Bearer downgrading check box if you want the service area (Eb Nt) predic on to take into consideration circumstances when the R99 bearer is downgraded. When downgrading is enabled and if the selected service
supports bearer downgrading, Atoll will consider only the lowest radio bearer.
For a service area (Eb/Nt) coverage prediction, the Display Type "Value Intervals" based on the Field "Max Eb Nt (dB)"
is selected by default. The Field you choose determines which informa on the service area (Eb Nt) downlink or uplink
258

AT310_UMU_E0
prediction makes available. Each pixel is displayed in a colour corresponding to the traffic channel quality. For information on defining display properties, see "Display Properties of Objects" on page 23.
-
The trac channel quality rela ve to the EbNt threshold: Select "Value Intervals" as the Display Type and
"Eb Nt Margin (dB)" as the Field.
The power required to reach the EbNt threshold: Select "Value Intervals" as the Display Type and "Required
Power (dB)" as the Field.
Where trac channel quality exceeds the EbNt threshold for each mobility type: On the Conditions tab, select
"All" as the Mobility Type. The parameters on the Display tab are automatically set.
For a service area (Eb Nt) (UL) coverage predic on, you can also display the following result:
-
The gain due to soft handover: Select "Value Intervals" as the Display Type and "Soft Handover Gain" as the Field.
later:
-
Calculate button (
Studying the Effective Service Area
The effective service area is the intersection zone between the pilot reception area, and the uplink and downlink service areas.
In other words, the effective service area prediction calculates where a service actually is available for the probe mobile.
To make an effective service area prediction:
4. Select Effective Service Area Analysis (EbNt) (DL+UL) and click OK. The Effective Service Area Analysis (EbNt)
(DL+UL) Properties dialogue appears.
"Best" carrier selected according to the carrier selection method defined for the site equipment.
If you want the effective service area prediction to consider shadowing, you can select the Shadowing taken into
account check box and enter a percentage in the Cell edge coverage probability text box.
You can also select the Indoor Coverage check box to add indoor losses.
You can select the Bearer downgrading check box if you want the effective service area prediction to take into consideration circumstances when the R99 bearer is downgraded. When downgrading is enabled and if the selected service
supports bearer downgrading, Atoll will consider only the lowest radio bearer.
259

Forsk 2011
For an effective service area prediction, the Display Type "Unique" is selected by default. The coverage prediction will
display where a service actually is available for the probe mobile. For information on defining display properties, see
"Display Properties of Objects" on page 23.
later:
-
Calculate button (
Creating a Quality Coverage Prediction Using Quality Indicators
You can create a quality prediction based on a given quality indicators (BER, BLER, or FER). The coverage prediction will show
for each pixel the measurement of the selected quality indicator.
This type of coverage prediction is not available in the list of standard predictions; you can, however, use quality indicators in
a prediction by first ensuring that the parameters of the quality indicators have been correctly set and then creating a coverage prediction, selecting display parameters that use these quality indicators.
Before you define the quality prediction, you must ensure that the parameters of the quality indicators have been correctly
set.
To check the parameters of the quality indicators:
3. Right-click Quality Indicators. The context menu appears.

4. Select Open Table from the context menu. The Quality Indicators table appears.
For each quality indicator in the Name column, you can set the following parameters:
-
Used for Packet Services: Select the Used for Packet Services check box if the quality indicator is to be used for
packet services.
Used for Circuit Services: Select the Used for Circuit Services check box if the quality indicator is to be used for
circuit services.
Measured Parameter for Quality Indicator: From the list, select the parameter that will be measured to indicate
quality.
Interpolated Quality Indicator: Select the Interpolated Quality Indicator check box if you want Atoll to interpolate between two existing QI values. Clear the Interpolated Quality Indicator check box if you want Atoll to take
the closest QI value.
5. Close the Quality Indicators table.

6. In the UMTS Network Settings folder, right-click the Reception Equipment folder. The context menu appears.
7. Select Open Table from the context menu. The Reception Equipment table appears.
"Standard" is the default reception equipment type for all terminals.
8. Double-click the reception equipment type for which you want to verify the correspondence between the measured
quality and the quality indicator. The reception equipment types Properties dialogue appears.
9. Click the Quality Graphs tab.
10. Ensure that a Quality Indicator has been chosen for each R99 Bearer. You can edit the values in the DL and UL Quality
Indicator Tables by clicking directly on the table entry, or by selecting the Quality Indicator and clicking the Downlink
Quality Graphs or the Uplink Quality Graphs buttons.
11. Click OK to close the reception equipment types Properties dialogue.
Once you have ensured that the parameters of the quality indicators have been correctly set, you can use the measured quality to create a quality prediction. How you define a coverage prediction according to the measured quality indicator depends
several parameters:
The settings made in the Quality Indicators table

The service you want to study
The quality indicator you want to use (BER, BLER, or FER)
The coverage prediction you want to use (Pilot Quality Analysis, the Service Area Analysis Downlink, or Service Area
Analysis Uplink).
In the following example, you will create a quality prediction showing BLER, for a user on foot, and with mobile internet access.
260

AT310_UMU_E0
To create a quality prediction showing BLER for a user on foot, and with mobile internet access:
4. Select Service Area Analysis (EbNt) (DL) and click OK. The Service Area Analysis (EbNt) (DL) Properties dialogue
appears.
5. Click the General tab. On the General tab, you can change the default Name and Resolution of the service area (Eb Nt)
downlink prediction, and add some Comments. Under Display configuration, you can create a Filter to select which
sites to display in the results. For information on filtering, see "Filtering Data" on page 71.
Terminal: Select the appropriate terminal for mobile Internet access from the Terminal list.
Service: Select "Mobile Internet Access" from the Service list.
Mobility: Select "Pedestrian" from the Mobility list.
Carrier: Select a specific carrier or "Best (Main band)" to have the carrier selected according to the carrier selection method defined for the site equipment.
If you want the service area (Eb Nt) (DL) prediction to consider shadowing, you can select the Shadowing taken into
You can select the Bearer downgrading check box if you want the service area (Eb Nt) downlink predic on to take into
consideration circumstances when the R99 bearer is downgraded. When downgrading is enabled and if the selected
service supports bearer downgrading, Atoll will consider only the lowest radio bearer.
Select "Value intervals" as the Display Type and "BLER" as the Field. The exact field value will depend on the name
given in the Quality Indicators table. For information on defining display properties, see "Display Properties of
later:
-
Calculate button (
Atoll calculates for each pixel the DL trac channel quality (Eb Nt) (provided when using the maximum trac channel power
allowed). Then, it calculates the corresponding BLER value from the quality graph (BLER=f(DL Eb Nt)). The pixel is coloured if
the condition is fulfilled (i.e., if BLER is evaluated as being higher than the specified threshold).
6.2.10.8.4
Studying Noise
Atoll has several coverage predictions that enable you to study the downlink total noise, downlink noise rise or pilot pollution.
In this section, the following noise predictions are explained:
"Studying the Total Noise Level on the Downlink" on page 261

"Calculating Pilot Pollution" on page 262
"Studying Inter-Technology Downlink Interference" on page 263.
Studying the Total Noise Level on the Downlink

In the coverage by total noise level (DL) prediction, Atoll calculates and displays the areas where the downlink total noise or
the downlink noise rise exceeds a set threshold.
261

Forsk 2011
To make a downlink total noise or downlink noise rise prediction:

4. Select Total Noise Level Analysis (DL) and click OK. The Total Noise Level Analysis (DL) dialogue appears.
You must select a Terminal, and Service, as defined in "Service and User Modelling" on page 252. You must also select
which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the "Best" carrier
selected according to the carrier selection method defined for the site equipment
For a downlink total noise or downlink noise rise prediction, the Display Type "Value Intervals" is selected by default.
The Field you choose determines which information the downlink total noise or downlink noise rise prediction makes
available.
-
Coverage by total noise on the downlink: When making a prediction on the total noise level on the downlink,
select one of the following in the Field list:
-
Min. Noise Level

Average Noise Level
Max Noise Level
Coverage by noise rise on the downlink: When making a prediction on the noise rise on the downlink, select one
of the following in the Field list:
-
Min. Noise Rise

Average Noise Rise
Max Noise Rise
For information on defining display properties, see "Display Properties of Objects" on page 23.
later:
-
Calculate button (
Calculating Pilot Pollution
A transmitter which fulfils all the criteria to enter a mobiles active set but which is not admitted because the active set limit
has already been reached is considered a polluter.
In the Pilot Pollution Analysis prediction, Atoll calculates and displays the areas where the probe mobile is interfered by the
pilot signal from polluter transmitters.
262

AT310_UMU_E0
To make a pilot pollution prediction:

4. Select Pilot Pollution Analysis and click OK. The Pilot Pollution Analysis Properties dialogue appears.
"Best" carrier selected according to the carrier selection method defined for the site equipment.
If you want the pilot pollution prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell edge coverage probability text box.
For a Pilot Pollution Analysis prediction, the Display Type "Value Intervals" and the Field "Number of Polluters" are
selected by default. For information on defining display properties, see "Display Properties of Objects" on page 23.
later:
-
Calculate button (
Studying Inter-Technology Downlink Interference
In the inter-technology downlink noise prediction, Atoll calculates and displays the areas where the downlink noise or noise
rise from external base stations and mobiles exceeds a set threshold. For more information on the modelling of inter-technology interference, see "Modelling Inter-Technology Interference" on page 420.
To make an inter-technology downlink noise or noise rise prediction:
4. Select Inter-technology Interference Level Analysis (DL) and click OK. The coverage prediction Properties dialogue
appears.
263

Forsk 2011
conditions taken from a simulation.
You must select a Terminal and a Service, as defined in "Service and User Modelling" on page 252. You must also select
which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the "Best" carrier
selected according to the carrier selection method defined for the site equipment.
If you want the prediction to consider shadowing, you can select the Shadowing taken into account check box and
enter a percentage in the Cell edge coverage probability text box.
The Display Type "Value Intervals" is selected by default. The Field you choose determines which information the
prediction makes available, Noise Level or Noise Rise. For information on defining display properties, see "Display
Properties of Objects" on page 23.
later:
-
Calculate button (
6.2.10.8.5
Making a Handoff Status Coverage Prediction

In the handoff status coverage prediction, Atoll calculates and displays the zones where a handoff can be made. For a handover to be possible, there must be a potential active transmitter, i.e., a transmitter that fulfils all the criteria to enter the mobile
active set, and the service chosen by the user must be available.
You can also use the handoff status coverage prediction to display the number of potential active transmitters.
To make a handoff status coverage prediction:
4. Select Handoff Zones and click OK. The Handoff Zones Properties dialogue appears.
264

AT310_UMU_E0
If you want the handoff status coverage prediction to consider shadowing, you can select the Shadowing taken into
7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage prediction will display.
To display the handoff status:
a. Select "Discrete Values" from the Display Type list.
b. Select "Status" from the Field list. Depending on the active set size of the terminal and the service capabilities in
terms of soft handover, the coverage prediction can display the following values:
-
No handoff: one cell in the mobile active set.

Softer: two cells in the mobile active set belonging to the same site.
Soft: two cells in the mobile active set, one from Site A and the other from Site B.
Softer-Softer: three cells in the mobile active set, belonging to the same site.
Softer-Soft: three cells in the mobile active set, two from Site A and the third one from Site B.
Soft-Soft: three cells in the mobile active set, one from Site A, one from Site B and one from Site C.
Not connected: no cell in the mobile active set.
To display the number of potential active transmitters:

a. Select "Value Intervals" from the Display Type list.
b. Select "Potential Active Transmitters" from the Field list. The coverage prediction will display the number of potential active transmitters.
For information on defining display properties, see "Display Properties of Objects" on page 23.
later:
-
Calculate button (
6.2.10.8.6
Making an AS Analysis
The Point Analysis window gives you information on reception for any point on the map. The AS Analysis view gives you informa on on the pilot quality (Ec I0) (which is the main parameter used to define the mobile ac ve set), the connec on status,
and the active set of the probe mobile. The analysis is provided for a user-definable probe receiver which has a terminal, a
mobility and a service.
Analysis is based on:
The UL load percentage and the DL total power of cells for R99 bearer connection
The available HSDPA power of cells for HSDPA bearer users
The uplink reuse factor, the uplink load factor due to HSUPA, the maximum uplink load factor of cells and the number
of HSUPA users in the cells in case of HSUPA bearer users.
You can make an AS analysis to verify a coverage prediction. Before you make the AS analysis, ensure the coverage prediction
you want to use in the AS analysis is displayed on the map.
For information on the criteria for belonging to the active set, see "Conditions for Entering the Active Set" on page 418.
To make an AS analysis:
) on the toolbar. The Point Analysis window appears (see Figure 6.32).
2. Select the AS Analysis view at the top of the Point Analysis window.
3. At the top of the AS Analysis view, select "Cells Table" from Load conditions.
265

Forsk 2011
4. If you are making an AS analysis to verify a coverage prediction, you can recreate the conditions of the coverage prediction:
a. Select the same Terminal, Service, and Mobility studied in the coverage prediction.
b. Select the Carrier to be considered. You can make the AS analysis for a specific carrier or for the "Best" carrier selected according to the carrier selection method defined for the site equipment.
c. Select the Bearer downgrading check box if bearer downgrading was selected in the coverage prediction. When
downgrading is enabled and if the selected service supports bearer downgrading, Atoll will consider only the lowest radio bearer.
d. Click the Options button (
-
) to display the Calculation Options dialogue.
Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability.
Select the Indoor Coverage check box to add indoor losses.
e. Click OK to close the Calculation Options dialogue.

5. Move the pointer over the map to make an active set analysis for the current location of the pointer.
As you move the pointer, Atoll indicates on the map which is the best server for the current position (see Figure 6.31).
Information on the current position is given on the AS Analysis view of the Point Analysis window. See Figure 6.32 on
page 266 for an explanation of the displayed information.
Figure 6.31: Point analysis on the map

6. Click the map to leave the point analysis pointer at its current position.
To move the pointer again, click the point analysis pointer on the map and drag it to a new position.
) on the toolbar again to end the point analysis.
Figure 6.32: Point Analysis Tool - AS Analysis tab
266

AT310_UMU_E0
The bar graph displays the following information:
The pilot quality (Ec I0) of all transmi ers using the selected carrier (the colour of the bar colour corresponds to the
colour of the transmitter on the map).
The thresholds of the ac ve set (Ec I0 threshold, best server ac ve set threshold). The por on of the graph with the
grey background indicates the transmitters in the active set.
The pilot and the availability of service on UL and DL.
If there is at least one successful connection (for pilot, downlink, or uplink), double-clicking the icons in the right-hand frame
will open a dialogue with additional information.
6.2.10.9 HSDPA Quality and Throughput Analysis

The HSDPA predictions allow you to study many HSDPA-related parameters, depending on the parameters defined. Each
HSDPA bearer user is associated to an R99-dedicated channel A-DPCH in the uplink and downlink, and must first initiate a ADPCH connection in order to be able to use HSDPA channels. In the coverage prediction, the HSDPA service area is limited by
the pilot quality and the A-DPCH quality. The parameters used as input for the HSDPA coverage predictions are the available
HSDPA power, and the total transmitted power for each cell. If the coverage prediction is not based on a simulation, these
values are taken from the cell properties. For information about the cell parameters, see "Creating or Modifying a Cell" on
page 210. For information on the formulas used to calculate different throughputs, see the Technical Reference Guide.
To make an HSDPA coverage prediction:
4. Select HSDPA Quality and Throughput Analysis and click OK. The HSDPA Quality and Throughput Analysis Properties
dialogue appears.
You must select a Mobility, as defined in "Service and User Modelling" on page 252. For an HSDPA coverage prediction, under Terminal, you must chose an HSDPA-capable terminal and, under Service, you must chose a service with
HSDPA.
You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or
for the "Best (Main band)" carrier selected according to the carrier selection method defined for the site equipment.
Under HSDPA radio bearer, select either "All" to consider all possible HSDPA radio bearers in the prediction or an
HSDPA radio bearer index to calculate a prediction for a certain bearer. Display options available in the Display tab
depend on what you have selected here.
If you want to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell edge coverage probability text box.
7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage prediction will display.
If you have selected "All" as the HSDPA radio bearer in the Conditions tab, you can set the following parameters:
-
To analyse the uplink and downlink A-DPCH qualities on the map:
267

Forsk 2011
To analyse the HS-SCCH quality or power:

-
The maximum DL A-DPCH quality rela ve to the EbNt threshold: Select "Max DL A-DPCH Eb Nt (dB)" as the
Field. Atoll determines downlink A-DPCH quality at the receiver for the maximum traffic channel power allowed for the best server.
The maximum UL A-DPCH quality rela ve to the EbNt threshold: Select "Max UL A-DPCH Eb Nt (dB)" as the
Field. Atoll determines uplink A-DPCH quality at the receiver for the maximum terminal power allowed.
The HS-SCCH power per HS-SCCH channel relative to the power threshold: Select "HS-SCCH Power (dBm)" as
the Field. This display option is relevant only if HS-SCCH power is allocated dynamically.
The HS-SCCH EcNt per HS-SCCH channel rela ve to the EcNt threshold: Select "HS-SCCH Ec Nt (dBm)" as the
Field. This display option is relevant only if HS-SCCH power is allocated statically.
To model fast link adaptation for a single HSDPA bearer user or for a defined number of HSDPA users:
For a single HSDPA bearer user, Atoll considers one HSDPA bearer user on each pixel and determines the best HSDPA bearer that the user can obtain by considering the entire available HSDPA power of the cell.
-
The HS-PDSCH Ec/Nt rela ve to the EcNt threshold: Select "HS-PDSCH Ec/Nt" as the Field. Atoll calculates
the best HS-PDSCH Ec Nt on each pixel.
The channel quality indicator (CQI) rela ve to the EcNt threshold: Select "CQI" as the Field. Atoll displays
either the CPICH CQI or the HS-PDSCH CQI, depending on the option selected under HSDPA on the Global
Parameters tab of the UMTS Network Settings Properties dialogue (see "The Options of the Network Settings
Properties Dialogue" on page 410).
For transmitters that support dual-cell HSDPA, rates and throughputs are calculated for two carriers: the best carrier, either selected in prediction properties or determined according to the carrier selection criterion defined in
the site equipment, and a second carrier that has the highest HSDPA power available.
-
The MAC rate relative to the threshold: Select "MAC Rate (kbps)" as the Field. Atoll calculates the MAC rate
from the transport block size of the selected HSDPA bearer.
The MAC throughput relative to the threshold: Select "MAC Throughput (kbps)" as the Field. The MAC
throughput is calculated from the MAC rate.
The RLC peak rate relative to the threshold: Select "RLC Peak Rate (kbps)" as the Field. Atoll displays the RLC
peak rate that the selected HSDPA bearer can be supplied with. The RLC peak rate is a characteristic of the
HSDPA bearer.
The RLC peak throughput relative to the threshold: Select "RLC Peak Throughput (kbps)" as the Field. Atoll
calculates the RLC peak throughput from the RLC peak rate.
The average RLC throughput relative to the threshold: Select "Average RLC Throughput (kbps)" as the Field.
The application throughput relative to the threshold: Select "Application Throughput (kbps)" as the Field.
Using the RLC peak rate, the BLER, the HSDPA service scaling factor, and the throughput offset, Atoll calculates
the application throughput. The application throughput represents the net throughput without coding (redundancy, overhead, addressing, etc.).
Atoll can consider several HSDPA bearer users per pixel. When the coverage prediction is not based on a simulation, this value is taken from the cell properties. Atoll considers the defined number of HSDPA bearer users on
each pixel and determines the best HSDPA bearer that each user can obtain. The coverage prediction results displayed are the average results for one user. The available HSDPA power of the cell is shared between the HSDPA
bearer users. For transmitters that support dual-cell HSDPA, the following rates and throughputs are calculated
for the two best carriers depending on the carrier selection criterion defined in the site equipment.
You can display the following results:
-
The average MAC throughput per mobile relative to the threshold: Select "MAC Throughput per Mobile
(kbps)" as the Field. Atoll calculates the average MAC throughput per mobile from the from the MAC throughput of each user.
The average RLC throughput per mobile relative to the threshold: Select "RLC Throughput per Mobile (kbps)"
as the Field. Atoll calculates the average RLC throughput per mobile from the RLC throughput of each user.
The average application throughput per mobile relative to the threshold: Select "Application Throughput per
Mobile (kbps)" as the Field. Using the RLC peak rate, the BLER, the HSDPA service scaling factor, and the
throughput offset, Atoll calculates the average application throughput per mobile from the application
throughput of each user.
If you have selected an HSDPA radio bearer index as the HSDPA Radio Bearer on the Conditions tab, you can display
the following results:
-
Where a certain RLC peak rate is available with different cell edge coverage probabilities: On the Conditions tab,
do not take shadowing into consideration and select a specific HSDPA radio bearer index. On the Display tab, the
Display Type "Value Intervals" based on the Field "Cell Edge Coverage Probability (%)" is selected by default.
When no value is defined in the Cells table for the total transmitted power and the number of HSDPA bearer users,
Atoll uses the following default values:
-
268
Total transmitted power = 50% of the maximum power (i.e, 40 dBm if the maximum power is set to 43 dBm)

AT310_UMU_E0
Number of HSDPA bearer users = 1
On the other hand, no default value is used for the available HSDPA power; this parameter must be defined by the
user.
For information on selecting the best bearer, see the Technical Reference Guide. For information on defining display
later:
-
Calculate button (
6.2.10.10 HSUPA Quality and Throughput Analysis

The HSUPA coverage prediction allows you to study several HSUPA-related parameters. Each HSUPA bearer user is associated
with an R99-dedicated traffic channel in the downlink and uplink (i.e., the ADPCH-EDPCCH R99 bearer), and must first initiate
this connection in order to be able to use HSUPA channels. In the coverage prediction, the HSUPA service area is limited by
the pilot quality and ADPCH-EDPCCH quality. The parameters used as input for the HSUPA predictions are the uplink load
factor the uplink reuse factor, the uplink load factor due to HSUPA and the maximum uplink load factor for each cell. If the
coverage prediction is not based on a simulation, these values are taken from the cell properties. For information about the
cell parameters, see "Creating or Modifying a Cell" on page 210. For information on the formulas used to calculate required
E-DPDCH Ec/Nt, required terminal power, and different throughputs, see the Technical Reference Guide.
To make an HSUPA coverage prediction:
4. Select HSUPA Quality and Throughput Analysis and click OK. The HSUPA Quality and Throughput Analysis Properties
dialogue appears.
You must select a Mobility, as defined in "Service and User Modelling" on page 252. For an HSUPA coverage prediction, under Terminal, you must chose an HSUPA-capable terminal and, under Service, you must chose a service with
HSUPA.
You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or
for the "Best (Main band)" carrier selected according to the carrier selection method defined for the site equipment.
HSUPA Resources: Atoll can calculate the HSUPA coverage prediction in one of two ways:
-
For a single user: After allocating capacity to all R99 users, the entire remaining load will be allocated to a single
HSUPA bearer user.
Shared by HSUPA users defined or calculated per cell: After allocating capacity to all R99 users, the remaining
load of the cell will be shared equally between all the HSUPA bearer users. When the coverage prediction is not
based on a simulation, the number of HSUPA bearer users is taken from the cell properties. The displayed results
of the coverage prediction will be for one user.
269

Forsk 2011
When no value is defined in the Cells table, Atoll uses the following default values:
-
Uplink load factor = 50%

Uplink reuse factor = 1
Uplink load factor due to HSUPA = 0%
Maximum uplink load factor = 75%
Number of HSUPA users = 1
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account check
box and enter a percentage in the Cell edge coverage probability text box.
7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage prediction will display. You can set parameters to display the following results:
-
The required E-DPDCH EcNt rela ve to the threshold: Select "Required E-DPDCH Ec Nt (dB)" as the Field. Atoll
selects the best HSUPA bearer whose required E-DPDCH Ec Nt does not exceed the maximum E-DPDCH Ec Nt
allowed. The required E-DPDCH Ec Nt is a property of the selected HSUPA bearer.
The power required for the selected terminal relative to the threshold: Select "Required Terminal Power (dBm)"
as the Field. Atoll calculates the required terminal power from the required E-DPDCH Ec Nt.
The MAC Rate relative to the threshold: Select "MAC Rate (kbps)" as the Field. Atoll calculates the MAC rate from
the transport block size of the selected HSUPA bearer.
The RLC peak rate relative to the threshold: Select "RLC Peak Rate (kbps)" as the Field. Atoll displays the RLC peak
rate that the selected HSUPA bearer can supply. The RLC peak rate is a property of the HSUPA bearer.
The guaranteed RLC throughput relative to the threshold: Select "Min RLC Throughput (kbps)" as the Field.
The average RLC throughput relative to the threshold: Select "Average RLC Throughput (kbps)" as the Field. Atoll
calculates the average RLC throughput on the uplink using the early termination probabilities, defined in the terminals reception equipment, to model HARQ (Hybrid Automatic Repeat Request).
The application throughput relative to the threshold: Select "Application Throughput (kbps)" as the Field. Using
the RLC peak rate, the BLER, the HSUPA service scaling factor, and the throughput offset, Atoll calculates the application throughput. The application throughput represents the net throughput without coding (redundancy, overhead, addressing, etc.).
The average application throughput relative to the threshold: Select "Average Application Throughput (kbps)" as
the Field. Atoll calculates the average application throughput on the uplink using the early termination probabilities, defined in the terminals reception equipment, to model HARQ (Hybrid Automatic Repeat Request).
For information on selecting the best bearer, see the Technical Reference Guide. For information on defining display
later:
-
Calculate button (
6.2.10.11 Printing and Exporting Coverage Prediction Results

Once you have made a coverage prediction, you can print the results displayed on the map or save them in an external format.
You can also export a selected area of the coverage as a bitmap.
270
Printing coverage prediction results: Atoll offers several options allowing you to customise and optimise the printed
coverage prediction results. Atoll supports printing to a variety of paper sizes, including A4 and A0. For more information on printing coverage prediction results, see "Printing a Map" on page 60.
Defining a geographic export zone: If you want to export part of the coverage prediction as a bitmap, you can define
a geographic export zone. After you have defined a geographic export zone, when you export a coverage prediction
as a raster image, Atoll offers you the option of exporting only the area covered by the zone. For more information on
defining a geographic export zone, see "Using a Geographic Export Zone" on page 38.
Exporting coverage prediction results: In Atoll, you can export the coverage areas of a coverage prediction in raster
or vector formats. In raster formats, you can export in BMP, TIF, JPEG 2000, ArcView grid, or Vertical Mapper (GRD
and GRC) formats. When exporting in GRD or GRC formats, Atoll allows you to export files larger than 2 GB. In vector
formats, you can export in ArcView, MapInfo, or AGD formats. For more information on exporting coverage prediction results, see "Exporting Coverage Prediction Results" on page 42.

AT310_UMU_E0
6.2.10.12 Making a Multi-point Analysis

In Atoll, you can carry out calculations on lists of points representing subscribers and analyse them. These analyses may be
useful for verifying network QoS at subscriber locations in case of incidents (call drops, low data rates, etc.) reported by users.
Moreover, some user equipment may feed back a number of network measurements at their locations. This may help verify
network quality without the need for measurement campaigns at the expense of the operator.
Two types of analyses are available:
Active Set Analysis: A number of parameters are calculated for each point. These parameters include the best server,
the ac ve set, Ec Io values for the ac ve set, the connec on status, and the obtained rates. The load condi ons are
fixed by the user, either read from the Cells table or from a traffic simulation.
Shadowing margins are not used in these calculations, i.e., fixed at 0 dB.
Potential Server Analysis: A number of parameters are calculated for each point, not just for the best server but for
all poten al servers. These parameters include the path loss, RSCP, Ec Io, DL Eb Nt, and UL Eb Nt. The load condi ons
are fixed by the user, either read from the Cells table or from a traffic simulation. The results provided by this analysis
are the same as available for one point in the Details view of the Point Analysis tool.
Shadowing margins are calculated for the cell edge coverage probability defined in the Properties dialogue of the
Point Analysis tool. The Indoor Coverage check box in this dialogue is also taken into account.
You may choose to carry out either or both types of analyses as needed. For both analysis types, all the points are considered
to have the same height, which is the receiver height defined in the Properties dialogue of the UMTS Network Settings folder,
i.e., the receiver height at which path loss matrices are calculated.
6.2.10.12.1
"Creating a Multi-point Analysis Group" on page 271.

"Adding New Analyses to Existing Multi-point Analysis Groups" on page 272.
"Accessing Multi-point Analysis Results" on page 273.
"Defining the Display Properties of Multi-point Analysis Results" on page 274.
Creating a Multi-point Analysis Group

Atoll lets you create a multi-point analysis group for each list of points. An analysis group may contain one or more analyses
carried out on one list of points. Analyses may be added to existing groups as required.
To create a new multi-point analysis group:
2. Right-click the Multi-point Analysis folder. The context menu appears.
3. Select New from the context menu. The Analysis Group N Properties dialogue appears.
4. Click the General tab. The following options are available:
-
Name: The name of the analysis group. You can change the name of the analysis group if desired.
Comments
5. Click the Conditions tab. The following options are available:

-
Load Conditions: Select the load conditions to be used in the analysis. If you select "(Cells Table)," the calculations
are not going to be based on load conditions taken from a simulation; Atoll will use the UL load factor and the DL
When you base an analysis on simulations, you would select the simulations from the Load
Conditions list.
Results: Select the results that you wish to be calculated:

-
All: Both types of the analyses below will be performed.

Active Set Analysis: Only the active set analysis will be carried out.
Potential Server Analysis: Only the potential server analysis will be carried out.
For more information on the two types of analyses, see "Making a Multi-point Analysis" on page 271.
-
Bearer Downgrading: Select the Bearer downgrading check box if you want to permit bearer downgrading.
Carrier: Under Potential Server Analysis Options, select the carrier for which you want the analysis to be carried
out. You can either select "Best" or one or more carrier numbers from the list. This option is only available when
either All or Potential Server Analysis is selected in the Results list above. The "Best" carrier will depend on the
271

Forsk 2011
6. Click the Points tab. Here you can create the list of points on which the analyses will be carried out. Each point in the
list is defined by its X and Y coordinates, a Service, a Terminal, and a Mobility. You can:
-
Import a list of points.

To import a list of points:
i.
Click the Actions button. The context menu appears.
ii. Select Import Table from the menu. For more information on importing table data, see "Importing Tables from
Text Files" on page 58.
-
Copy and paste an existing list of points.
Create points in the list by editing the table.

In the row marked with the New Row icon (
), you can create one point per row by entering its X and Y coordinates and assigning it a service, a terminal, and a mobility.
The coordinates must be in the format used by the display coordinate system of the document. For information on changing the coordinate system, see "Setting a Coordinate
System" on page 95.
7. You can either run the analyses selected in the General tab immediately or you can create the analysis group and run
the analyses later:
-
6.2.10.12.2
Calculate: Click Calculate to run the selected analyses immediately. Once the calculations for the selected analyses are complete, an analysis (Analysis 0) will appear under the Analysis Group N in the Multi-point Analysis
folder. For information on how to access the analysis results, see "Accessing Multi-point Analysis Results" on
page 273.
OK: Click OK to create the analysis group without running any analysis. Analysis Group N will appear under the
Multi-point Analysis folder. For information on how to run analyses on an existing analysis group, see "Adding
New Analyses to Existing Multi-point Analysis Groups" on page 272.
Adding New Analyses to Existing Multi-point Analysis Groups

When you have created a multi-point analysis group corresponding to a list of points, you can re-examine this list of points
with different calculation options by adding new analyses to the group.
To add a new analysis to an existing multi-point analysis group:
) to expand the Multi-point Analysis folder.
3. Right-click the multi-point analysis group. The context menu appears.

4. Select New from the context menu. The Analysis Group N Properties dialogue appears.
5. On the Conditions tab, the following options are available:
-
Load Conditions: Select the load conditions to be used in the analysis. If you select "(Cells Table)," the calculations
are not going to be based on load conditions taken from a simulation. Atoll will use the UL load factor and the DL
When you base an analysis on simulations, you would select the simulations from the Load
Conditions list.
Results: Select the results that you wish to be calculated:

-
All: Both types of the analyses below will be performed.

Active Set Analysis: Only the active set analysis will be carried out.
Potential Server Analysis: Only the potential server analysis will be carried out.
For more information on the two types of analyses, see "Making a Multi-point Analysis" on page 271.
-
Bearer Downgrading: Select the Bearer downgrading check box if you want to permit bearer downgrading.
Carrier: Under Potential Server Analysis Options, select the carrier for which you want the analysis to be carried
out. You can either select "Best" or one or more carrier numbers from the list. This option is only available when
either All or Potential Server Analysis is selected in the Results list above. The "Best" carrier will depend on the
6. Click Calculate. Once the calculations for the new analysis are complete, an analysis will appear under the Analysis
Group N in the Multi-point Analysis folder. For information on how to access the analysis results, see "Accessing
Multi-point Analysis Results" on page 273
272

AT310_UMU_E0
6.2.10.12.3
Accessing Multi-point Analysis Results

To access the active set analysis results:
) to expand the analysis group containing the analysis whose results you want to access.
4. Right-click the analysis. The context menu appears.

5. Select Active Set Analysis Results from the context menu. The Active Set Analysis Results dialogue appears. The
results include the following information:
-
Load Conditions: The load conditions that were used when creating the analysis.
Bearer Downgrading: Whether bearer downgrading was allowed for the calculations or not.
X and Y: The coordinates of users who attempt to connect.
Service: The services assigned to the users.
Terminal: The terminals assigned to the users.
Mobility: The mobility types assigned to the users.
Carrier: The carrier used for the mobile-transmitter connection. Dual-cell HSDPA users are connected to two carriers.
Frequency Band: The frequency band used for the mobile-transmitter connection.
DL and UL Total Requested Rate (kbps): For circuit and packet (R99) service users, the DL and UL total requested
rates correspond to the DL and UL nominal rates of the R99 bearer associated to the service.
For packet (HSDPA) service users, the uplink total requested rate corresponds to the nominal rate of ADPCH-UL64
R99 bearer and the downlink total requested rate is the sum of the ADPCH-UL64 radio bearer nominal rate and
the RLC peak rate that the selected HSDPA radio bearers can provide. Here, the HSDPA user is treated as if he is
the only user in the cell and then, Atoll determines the HSDPA bearer the user would obtain by considering the
entire HSDPA power available of the cell.
For HSUPA bearer users (i.e., packet (HSPA) and packet (HSPA - Constant Bit Rate) service users), the uplink total
requested rate is equal to the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate of the
requested HSUPA radio bearer. The requested HSUPA radio bearer is selected from the HSUPA bearers compatible
with the user equipment. Here, the HSUPA user is treated as if he is the only user in the cell and then, Atoll determines the HSUPA bearer the user would obtain by considering the entire remaining load of the cell. The downlink
total requested rate is the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate that the
requested HSDPA radio bearers can provide. The requested HSDPA bearer is determined as explained in the previous paragraph.
DL and UL Total Obtained Rate (kbps): For circuit and packet (R99) service users, the DL or UL total obtained rate
is the same as the DL or UL total requested rate if he is connected without being downgraded. Otherwise, the total
obtained rate is lower (it corresponds to the nominal rate of the selected R99 bearer). If the user was rejected, the
total obtained rate is zero.
For a packet (HSDPA) service user connected to an HSDPA bearer, the uplink total obtained rate equals the requested one and the downlink total obtained rate corresponds to the instantaneous rate; this is the sum of the
ADPCH-UL64 radio bearer nominal rate and the RLC peak rate provided by the selected HSDPA radio bearers after
scheduling and radio resource control. If the user is delayed (he is only connected to an R99 radio bearer), uplink
and downlink total obtained rates correspond to the uplink and downlink nominal rates of ADPCH-UL64 radio
bearer. Finally, if the user is rejected either in the R99 part or in the HSDPA part (i.e., because the HSDPA scheduler
is saturated), the uplink and downlink total obtained rates are zero.
For a connected packet (HSPA) service user, on uplink, if the user is connected to an HSUPA bearer, the uplink total
obtained rate is the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate provided by the
selected HSUPA radio bearer after noise rise scheduling. On downlink, if the user is connected to an HSDPA bearer,
the downlink total obtained rate corresponds to the instantaneous rate. The instantaneous rate is the sum of the
ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate provided by the selected HSDPA radio bearers
after scheduling and radio resource control. If the user is delayed, the downlink total obtained rate corresponds
to the downlink nominal rate of ADPCH-EDPCCH radio bearer. If the user is rejected, the uplink and downlink total
obtained rates are "0".
For a connected packet (HSPA - Constant Bit Rate) service user, the uplink and downlink total obtained rates are
the sum of the ADPCH-EDPCCH radio bearer nominal rate and the guaranteed bit rate defined for the service. If
the user is rejected, the uplink and downlink total obtained rates are "0".
Mobile Total Power (dBm): The mobile total power corresponds to the total power transmitted by the terminal.
Connection Status: The connection status indicates whether the user is connected or rejected. If connected, the
connection status corresponds to the activity status. If rejected, the rejection cause is given.
Best Server: The best server among the transmitters in the mobile active set.
HO Status (Sites/No. Transmitters Act. Set): The HO status is the number of sites compared to the number of
transmitters in the active set.
273

Forsk 2011
AS1, AS2, AS3, AS4: The name of the cell that is the best server, the second-best server, and so on is given in a
separate column for each cell in the active set.
Ec/I0 AS1, AS2, AS3, AS4, (dB): Ec I0 is given in a separate column for each cell in the ac ve set. The Ec/I0 AS 1
column lists the Ec/I0 from the best server for the rejected mobiles as well.
Active Compressed Mode: This field indicates whether active compressed mode is supported by the mobile or
not.
6. Click Close.
To access the potential server analysis results:
) to expand the analysis group containing the analysis whose results you want to access.
4. Right-click the analysis. The context menu appears.

5. Select Potential Server Analysis Results from the context menu. The Potential Server Analysis Results dialogue
appears. The results include the following information:
-
Load Conditions: The load conditions that were used when creating the analysis.
Shadowing taken into account: Whether shadowing was taken into account for the calculations or not.
Cell Edge Coverage Probability: Used to calculate the shadowing margin if shadowing was taken into account.
Indoor Coverage: Whether the points were considered to be indoor for the calculations. In this case, indoor losses
were used in the calculations.
Bearer Downgrading: Whether bearer downgrading was allowed for the calculations or not.
Carrier: The carrier(s) for which the calculations were made.
X and Y: The coordinates of users who attempt to connect.
Service: The services assigned to the users.
Terminal: The terminals assigned to the users.
Mobility: The mobility types assigned to the users.
Transmitter: Potential servers of the users for which the remaining parameters were calculated.
Distance (m): Distances from the potential servers.
Path Loss (dB): Path losses corresponding to the potential servers.
RSCP (dBm): Received Signal Code Powers corresponding to the potential servers.
Ec/Io (dB): Ec/Io corresponding to the potential servers.
Eb/Nt DL (dB): Downlink Eb/Nt corresponding to the potential servers.
Eb/Nt UL (dB): Uplink Eb/Nt corresponding to the potential servers.
Scrambling code: Scrambling codes corresponding to the potential servers.
6. Click Close.
6.2.10.12.4
Defining the Display Properties of Multi-point Analysis Results

You can display the multi-point analysis results on the map according to different parameters.
To define the display properties of multi-point analysis results:
2. Right-click the Multi-point Analysis folder. The context menu appears.
3. Select Properties from the context menu. The Multi-point Analysis Properties dialogue appears.
4. On the Display tab of the dialogue, define the display properties of multi-point analysis results. For information on
changing display characteristics, see "Defining the Display Properties of Objects" on page 23.
5. Click OK.
6.2.11 Planning Neighbours

You can set neighbours for each cell manually, or you can let Atoll automatically allocate neighbours, based on the parameters
that you define. When allocating neighbours, the cell to which you are allocating neighbours is referred to as the reference
cell. The cells that fulfil the requirements to be neighbours are referred to as possible neighbours. When allocating neighbours
to all active and filtered transmitters, Atoll allocates neighbours only to the cells within the focus zone and considers as possible neighbours all the active and filtered cells whose propagation zone intersects a rectangle containing the computation
zone. If there is no focus zone, Atoll allocates neighbours only to the cells within the computation zone.
The focus and computation zones are taken into account whether or not they are visible. In other words, the focus and computation zones will be taken into account whether or not their visibility check box in the Zones folder of the Geo tab in the
Explorer window is selected.
Usually, you will allocate neighbours globally during the beginning of a radio planning project. Afterwards, you will allocate
neighbours to base stations or transmitters as you add them. You can use automatic allocation on all cells in the document,
274

AT310_UMU_E0
or you can define a group of cells either by using a focus zone or by grouping transmitters in the Explorer window. For information on creating a focus zone, see "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 243. For
information on grouping transmitters in the Explorer window, see "Grouping Data Objects" on page 65.
Atoll supports the following neighbour types in a UMTS network:
Intra-technology Neighbours: Intra-technology neighbours are cells defined as neighbours that also use UMTS. Intratechnology neighbours can be divided into:
-
Intra-carrier Neighbours: Cells defined as neighbours which perform handover using the same carrier.
Inter-carrier Neighbours: Cells defined as neighbours which perform handover using a different carrier.
Inter-technology Neighbours: Inter-technology neighbours are cells defined as neighbours that use a technology
other than UMTS.
"Importing Neighbours" on page 275

"Defining Exceptional Pairs" on page 275
"Configuring Importance Factors for Neighbours" on page 276
"Allocating Neighbours Automatically" on page 276
"Checking Automatic Allocation Results" on page 280
"Allocating and Deleting Neighbours per Cell" on page 283
"Calculating the Importance of Existing Neighbours" on page 285
"Checking the Consistency of the Neighbour Plan" on page 287
"Exporting Neighbours" on page 288.
6.2.11.1 Importing Neighbours

You can import neighbour data in the form of ASCII text files (in TXT and CSV formats) into the current Atoll document using
the Neighbours table.
To import neighbours using the Neighbours table:
1. Open the Neighbours table:
a. Select the Network tab of the Explorer window.
b. Right-click the Transmitters folder. The context menu appears.
c. Select Neighbours > Intra-technology > Open Table from the context menu. The Neighbours table appears.
2. Import the ASCII text file as explained in "Importing Tables from Text Files" on page 58.
6.2.11.2 Defining Exceptional Pairs

In Atoll, you can define neighbour constraints that will be taken into consideration during the automatic allocation of neighbours. Exceptional pairs can be taken into consideration when you manually allocate neighbours.
To define exceptional pairs of neighbours:
4. Right-click the cell for which you want to define neighbour constraints. The context menu appears.
5. Select Record Properties from the context menu. The cells Properties dialogue appears.
6. Click the Intra-technology Neighbours tab.
7. Under Exceptional Pairs, create a new exceptional pair in the row marked with the New Row icon (
):
a. Select the cell from the list in the Neighbours column.

b. In the Status column, select one of the following:
-
Forced: The selected cell will always be a neighbour of the reference cell.
Forbidden: The selected cell will never be a neighbour of the reference cell.
8. Click elsewhere in the table when you have finished creating the new exceptional pair.
9. Click OK.
You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology
Neighbours table. You can open this table by right-clicking the Transmitters folder and
selecting Neighbours > Intra-Technology > Exceptional Pairs.
275

Forsk 2011
6.2.11.3 Configuring Importance Factors for Neighbours

You can define the relative importance of the factors that Atoll uses to evaluate possible intra-technology neighbours (intraand inter-carrier) and inter-technology neighbours (for information on how Atoll calculates importance, see the Technical
Reference Guide).
To configure the importance factors for intra-technology neighbours:
3. Select Neighbours > Intra-technology > Configure Importance from the context menu. The Neighbour Importance
Weighting dialogue appears.
4. Select the Intra-carrier Neighbours tab. On the Intra-carrier Neighbours tab, you can set the following importance
factors:
-
Distance Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located
within the maximum distance from the reference transmitter.
Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons.
Adjacency Factor: Set the minimum and maximum importance of a possible neighbour transmitter being adjacent
to the reference transmitter. The Adjacency Factor will be used if you select the Force adjacent transmitters as
neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 276.
Co-site Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located on
the same site as reference transmitter. The Co-site Factor will be used if you select the Force co-site transmitters
as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 276.
5. Select the Inter-carrier Neighbours tab. On the Inter-carrier Neighbours tab, you can set the following importance
factors:
-
as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 276.
6. Click OK.
You can configure the same importance factors for inter-technology neighbours by
selecting Neighbours > Inter-technology > Configure Importance from the Transmitters folder context menu.
By adding an option to the atoll.ini file, the importance calculation can be based on
the distance criterion only. For more information, see the Technical Reference
Guide.
6.2.11.4 Allocating Neighbours Automatically

Atoll can automatically allocate both intra- and inter-carrier neighbours in a UMTS network. Atoll allocates neighbours based
on the parameters you set in the Automatic Neighbour Allocation dialogue.
By setting an option in the atoll.ini file, you can prevent Atoll from allocating inter-carrier neighbours to cells located on sites
whose equipment does not support the compressed mode. For more information, see the Administrator Manual.
To automatically allocate intra-carrier UMTS neighbours:
3. Select Neighbours > Intra-technology > Automatic Allocation from the context menu. The Automatic Neighbour
Allocation dialogue appears.
4. Click the Intra-Carrier Neighbours tab. You can set the following parameters:
-
276
Max. Inter-site Distance: Set the maximum distance between the reference cell and a possible neighbour.
Max. No. of Neighbours: Set the maximum number of intra-carrier neighbours that can be allocated to a cell. This
value can be either set here for all transmitters, or specified for each transmitter in the Cells table.

AT310_UMU_E0
Coverage Conditions: The coverage conditions must be respected for a cell to be considered as a neighbour. Click
Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the following
parameters:
-
Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation.
Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by reference cell A and
possible neighbour cell B.
Min. EcI0: Enter the minimum Ec I0 which must be provided by reference cell A in an overlapping area. Reference cell A must also be the best server in terms of pilot quality in the overlapping area.
EcI0 Margin: Enter the maximum dierence of Ec I0 between reference cell A and possible neighbour cell B
in the overlapping area.
DL Load Contributing to I0: You can let Atoll base the interference ratio on the total power used as defined in
the properties for each cell (Defined per Cell) or on a percentage of the maximum power (Global Value).
Shadowing taken into account: If desired, select the Shadowing taken into account check box and enter a Cell
Edge Coverage Probability.
Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses in the calculations.
% Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cells coverage area must
overlap the reference cells coverage area.
5. Select the desired calculation parameters:

-
Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers (Atoll
will allocate neighbours to cells using the selected carriers).
Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want cells located
on the same site as the reference cell to be automatically considered as neighbours.
Force adjacent cells as neighbours: Select the Force adjacent cells as neighbours check box if you want cells that
are adjacent to the reference cell to be automatically considered as neighbours. A cell is considered adjacent if
there is at least one pixel in the reference cells coverage area where the possible neighbour cell is the best server,
or where the possible neighbour cell is the second best server in the reference cells active set (respecting the
handover margin).
Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In other
words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neighbour list
of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from the list of
neighbours of the reference cell.
Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or forbid
neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see "Defining
Exceptional Pairs" on page 275.
Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete all current
neighbours when allocating neighbours. If you do not select the Delete existing neighbours check box, Atoll will
not delete any existing neighbours when automatically allocating neighbours; it will only add new neighbours to
the list.
6. Click Calculate. Atoll begins the process of allocating intra-carrier neighbours. Atoll first checks to see whether the
path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates
them.
Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays new
neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is cleared, the
Results table will be empty.
The Results table contains the following information.
-
Cell: The name of the reference cell.

Number: The total number of neighbours allocated to the reference cell.
Maximum Number: The maximum number of neighbours that the reference cell can have.
Neighbour: The cell that will be allocated as a neighbour to the reference cell.
Importance (%): The importance. For information on defining neighbour importance, see "Configuring Importance Factors for Neighbours" on page 276.
Cause: The reason Atoll has allocated the possible neighbour cell, as identified in the Neighbour column, to the
reference cell, as identified in the Cell column.
-
Co-site
Adjacency
Symmetry
Coverage
Existing
Coverage: The amount of reference cells coverage area that the neighbour overlaps, in percentage and in square
kilometres.
277

Forsk 2011
Adjacency: The area of the reference cell, in percentage and in square kilometres, where the neighbour cell is best
server or second best server.
7. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on
page 47.
At this point you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document:
-
Click Compare. The list of automatically allocated neighbours (those whose Commit check box is selected) is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists:
-
The document name and the neighbour allocation type

The number of created neighbour relations (new neighbour relations proposed in the automatic allocation
results compared to the existing neighbour relations) and the list of these relations
The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation
The number of existing neighbour relations (existing neighbour relations that are also proposed in the automatic allocation results) and the list of these relations.
8. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neighbours
are listed in the Intra-technology Neighbours tab of each cells Properties dialogue.
To automatically allocate inter-carrier UMTS neighbours:
3. Select Neighbours > Intra-technology > Automatic Allocation from the context menu. The Automatic Neighbour
4. Click the Inter-Carrier Neighbours tab. You can set the following parameters:
-
Max. Inter-site Distance: Set the maximum distance between the reference cell and a possible neighbour.
Max. Number of Neighbours: Set the maximum number of inter-carrier neighbours that can be allocated to a cell.
This value can be either set here for all transmitters, or specified for each transmitter in the Cells table.
Coverage Conditions: The coverage conditions must be respected for a cell to be considered as a neighbour. Click
Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the following
parameters:
-
Min. EcI0: Enter the minimum Ec I0 which must be provided by reference cell A and possible neighbour B in
an overlapping area. Possible neighbour B must also be the best server in terms of pilot quality in the overlapping area.
EcI0 Margin: Enter the Ec I0 margin rela ve to the Ec I0 of the reference cell A. See the Technical Reference
Guide for an explana on of how the Ec I0 margin is used in dierent inter-carrier handover scenarios.
% Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cells coverage area must
overlap the reference cells coverage area.
5. Select the desired calculation parameters:

-
278
Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers (Atoll
will allocate neighbours to cells using the selected carriers).
Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want cells located
on the same site as the reference cell to be automatically considered as neighbours.
Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In other
words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neighbour list
of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from the list of
neighbours of the reference cell.
Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or forbid
neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see "Defining
Exceptional Pairs" on page 275.
Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete all current
neighbours when allocating neighbours. If you do not select the Delete existing neighbours check box, Atoll will

AT310_UMU_E0
not delete any existing neighbours when automatically allocating neighbours; it will only add new neighbours to
the list.
6. Click Calculate. Atoll begins the process of allocating inter-carrier neighbours. Atoll first checks to see whether the
path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates
them.
Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays new
neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is cleared, the
Results table will be empty.
-

Number: The total number of neighbours allocated to the reference cell.
Maximum Number: The maximum number of neighbours that the reference cell can have.
Neighbour: The cell that will be allocated as a neighbour to the reference cell.
Importance (%): The importance. For information on defining neighbour importance, see "Configuring Importance Factors for Neighbours" on page 276.
Cause: The reason Atoll has allocated the possible neighbour cell, as identified in the Neighbour column, to the
reference cell, as identified in the Cell column.
-
Co-site
Symmetry
Coverage
Existing
Coverage: The amount of reference cells coverage area that the neighbour overlaps, in percentage and in square
kilometres.
7. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on
page 47.
At this point you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document:
-
Click Compare. The list of automically allocated neighbours (those whose Commit check box is selected) is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists:
-
The document name and the neighbour allocation type

8. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neighbours
are listed in the Intra-technology Neighbours tab of each cells Properties dialogue.
A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already exists and the Delete existing neighbours check box is cleared when
you start the new allocation. In this case, Atoll displays a warning in the Event
Viewer indicating that the constraint on the forbidden neighbour will be ignored
by the algorithm because the neighbour already exists.
When the options Force exceptional pairs and Force symmetry are selected, Atoll
considers the constraints between exceptional pairs in both directions in order to
respect symmetry. On the other hand, if the neighbour relation is forced in one
direction and forbidden in the other one, symmetry cannot be respected. In this
case, Atoll displays a warning in the Event Viewer.
By adding an option to the atoll.ini file, the importance calculation can be based on
the distance criterion only. When the option is active, neighbours are allocated for
distance reasons. For more information, see the Technical Reference Guide.
You can save automatic neighbour allocation parameters in a user configuration.
For information on saving automatic neighbour allocation parameters in a user
configuration, see "Saving a User Configuration" on page 76.
Atoll also enables you to automatically allocate neighbours to a single base station or transmitter:
"Allocating Neighbours to a New Base Station" on page 280
279

6.2.11.4.1
Forsk 2011
"Allocating Neighbours to a New Transmitter" on page 280.
Allocating Neighbours to a New Base Station

When you create a new base station, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the
new base station and other cells whose coverage area intersects with the coverage area of the cells of the new base station.
To allocate neighbours to a new base station:
1. On the Network tab of the Explorer window, group the transmitters by site, as explained in "Grouping Data Objects"
on page 65.
2. In the Transmitters folder, right-click the new base station. The context menu appears.
3. Select Neighbours > Intra-technology Neighbours > Automatic Allocation from the context menu. The Automatic
Neighbour Allocation dialogue appears.
4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on
page 276.
6.2.11.4.2
Allocating Neighbours to a New Transmitter

When you add a new transmitter, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new
transmitters and other cells whose coverage area intersects the coverage area of the cells of the new transmitter.
To allocate neighbours to a new transmitter:
2. In the Transmitters folder, right-click the new transmitter. The context menu appears.
3. Select Allocate Neighbours from the context menu. The Automatic Neighbour Allocation dialogue appears.
4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on
page 276.
6.2.11.5 Checking Automatic Allocation Results

You can verify the results of automatic neighbour allocation in the following ways:
6.2.11.5.1
"Displaying Neighbour Relations on the Map" on page 280

"Displaying the Coverage of Each Neighbour of a Cell" on page 282.
Displaying Neighbour Relations on the Map

You can view neighbour relations directly on the map. Atoll can display them and indicate the direction of the neighbour relation (in other words, Atoll indicates which is the reference cell and which is the neighbour) and whether the neighbour relation is symmetric.
To display the neighbour relations of a cell on the map:
3. Select Neighbours > Intra-technology > Display Options from the context menu. The Neighbour Display dialogue
appears.
4. Under Intra-technology Neighbours, select the Display links check box.
) beside the Display links check box.
6. The Intra-technology Neighbour Display dialogue appears.

7. From the Display Type list, choose one of the following:
-
280
Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a cell with a unique
colour.
Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you want Atoll
to colour the cells neighbour links according to a value from the Intra-technology Neighbours table, or according
to the neighbour carrier. In this case, you can view intra-carrier and inter-carrier neighbour relations on the map.
Value Intervals: Select "Value Intervals" to colour the cells neighbour links according the value interval of the
value selected from the Field list. For example, you can choose to display a cells neighbours according to their
rank, in terms of automatic allocation, or according to the importance, as determined by the weighting factors.

AT310_UMU_E0
You can display the number of handoff attempts for each cell-neighbour pair by first
creating a new field of the Type "Integer" in the Intra-Technology Neighbour table for
the number of handoff attempts. Once you have imported or entered the values in the
new column, you can select this field from the Field list along with "Value Intervals" as
the Display Type. For information on adding a new field to a table, see "Adding a Field to
an Object Types Data Table" on page 48.
Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you can
display or hide neighbour link display types individually.
For information on changing display properties, see "Display Properties of Objects" on page 23.
8. Select the Add to legend check box to add the displayed neighbour links to the legend.
) next to Tip text and select the neighbour characteristics to be displayed in the tip text.
This information will be displayed on each neighbour link.
10. Click OK to save your settings.
11. Under Advanced, select which neighbour links to display:
-
Outwards non-symmetrical: Select the Outwards non-symmetrical check box to display neighbour relations
where the selected cell is the reference cell and where the neighbour relation is not symmetric.
Inwards non-symmetrical: Select the Inwards non-symmetrical check box to display neighbour relations where
the selected cell is neighbour and where the neighbour relation is not symmetric.
Symmetric links: Select the Symmetric links check box to display neighbour relations that are symmetric between
the selected cell and the neighbour.

13. Click the arrow ( ) next to the Edit Relations on the Map button (
appears.
) in the Radio Planning toolbar. The menu
14. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
15. Click the Edit Relations on the Map button (
16. Click a transmitter on the map to display the neighbour relations. When there is more than one cell on the transmitter,
clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see
"Selecting One of Several Transmitters" on page 21).
Atoll displays the following information (see Figure 6.33) for the selected cell:
-
The symmetrical neighbour relations of the selected (reference) cell are indicated by a line.
The outward neighbour relations are indicated with a line ending in an arrow pointing at the neighbour (e.g., see
Site1_2(0)) in Figure 6.33.).
The inward neighbour relations are indicated with a line ending in an arrow pointing at the selected cell (e.g., see
Site9_3(0)) in Figure 6.33.).
In Figure 6.33, neighbour links are displayed according to the neighbour. Therefore, the symmetrical and outward
neighbour links are coloured the same as the corresponding neighbour transmitters and the inward neighbour link is
coloured the same as the reference transmitter because it is neighbour of Site9_3(0) here.
Figure 6.33: Intra-carrier Neighbours of Site 22_3(0) - Display According to the Neighbour
281

Forsk 2011
In Figure 6.34, neighbour links are displayed according to the neighbour carrier. You can view intra-carrier and intercarrier neighbour links. In Figure 6.34, all neighbour relations are symmetrical.
Figure 6.34: Intra-carrier and Inter-Carrier Neighbours of Site 14_3(0)

You can display either forced neighbours or forbidden neighbours by clicking the arrow
( ) next to the Edit Relations on the Map button (
) in the Radio Planning toolbar and
selecting either Forced Neighbours or Forbidden Neighbours.
6.2.11.5.2
Displaying the Coverage of Each Neighbour of a Cell

By combining the display characteristics of a coverage prediction with neighbour display options, Atoll can display the coverage area of a cells neighbours and colour them according to any neighbour characteristic in the Neighbours table.
To display the coverage of each neighbour of a cell:
1. Create, calculate, and display a "Coverage by transmitter" prediction, with the Display Type set to "Discrete Values"
and the Field set to "Transmitter" (for information on creating a coverage by transmitter prediction, see "Making a
Coverage Prediction by Transmitter" on page 239).
3. Select Neighbours > Intra-technology > Display Options from the context menu. The Neighbour Display dialogue
appears.
4. Under Intra-technology Neighbours, select the Display Coverage Areas check box.
) beside the Display Coverage Areas check box.
6. The Intra-technology Neighbour Display dialogue appears.

7. From the Display Type list, choose one of the following:
-
Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage area of a cells neighbours
with a unique colour.
Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you want Atoll
to colour the coverage area of a cells neighbours according to a value from the Intra-technology Neighbours
table.
Value Intervals: Select "Value Intervals" to colour the coverage area of a cells neighbours according the value
interval of the value selected from the Field list. For example, you can choose to display a cells neighbours
according to their rank, in terms of automatic allocation, or according to the importance, as determined by the
weighting factors.

) next to Tip Text and select the neighbour characteristics to be displayed in the tip text.
This information will be displayed on each coverage area.
appears.
10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
282

AT310_UMU_E0
12. Click a transmitter on the map to display the coverage of each neighbour. When there is more than one cell on the
transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want
(see "Selecting One of Several Transmitters" on page 21).
Only intra-carrier neighbour coverage areas are displayed.
13. In order to restore colours and cancel the neighbour display, click the Edit Relations on the Map button (
Radio Planning toolbar.
) in the
6.2.11.6 Allocating and Deleting Neighbours per Cell

Although you can let Atoll allocate neighbours automatically, you can adjust the overall allocation of neighbours by allocating
or deleting neighbours per cell. You can allocate or delete neighbours directly on the map or using the Cells tab of the Transmitter Properties dialogue.
"Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 283
"Allocating or Deleting Neighbours Using the Neighbours Table" on page 284
"Allocating or Deleting Neighbours on the Map" on page 285.
Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete UMTS neighbours using the Cells tab of the transmitters Properties dialogue:
1. On the map, right-click the transmitter whose neighbours you want to change. The context menu appears.
3. Click the Cells tab.
4. On the Cells tab, there is a column for each cell. Click the Browse button ( ) beside Neighbours in the cell for which
you want to allocate or delete neighbours. The cells Properties dialogue appears.
5. Click the Intra-technology Neighbours tab.
6. If desired, you can enter the maximum number of neighbours in the following boxes:
-
Max number inter-carrier

Max number intra-carrier
To allocate a new neighbour:

1. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon (
).
2. Click elsewhere in the table to complete creating the new neighbour.

When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the
neighbour and displays it in the Distance column, sets the Source to "manual," and sets the Importance to "1."
To create a symmetric neighbour relation:
1. Click in the left margin of the table row containing the neighbour to select the entire row.
2. Right-click the neighbour in the Neighbour column. The context menu appears.
3. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column.
To delete a symmetric neighbour relation:
3. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the
cell in the Neighbour column and the cell in the Cell column is deleted.
To delete a neighbour:
2. Press DEL to delete the neighbour.
283

Forsk 2011
Allocating or Deleting Neighbours Using the Neighbours Table

To allocate or delete UMTS neighbours using the Neighbours table:
1. Select the Network tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appear.
3. Select Neighbours > Intra-technology > Open Table from the context menu. The Neighbours table appears.
For information on working with data tables, see "Working with Data Tables" on page 47.
To allocate a neighbour:
1. In the row marked with the New Row icon (
), select a reference cell in the Cell column.
2. Select the neighbour in the Neighbour column.

3. Click elsewhere in the table to create the new neighbour and add a new blank row to the table.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the
neighbour and displays it in the Distance column, sets the Source to "manual," and sets the Importance to "1."
To create a symmetrical neighbour relation:
3. Select Make Symmetrical from the context menu. A symmetrical neighbour relation is created between the cell in the
Neighbour column and the cell in the Cell column.
To make several neighbour relations symmetrical:
1. Click in the left margin of the table rows containing the neighbours to select the entire rows. You can select contiguous
rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing
CTRL and clicking each rows separately.
2. Right-click the Neighbours table. The context menu appears.
3. Select Make Symmetrical from the context menu.
To take all exceptionnal pairs into consideration:
2. Select Force Exceptional Pairs from the context menu.
You can add or delete some forced neighbours or some forbidden neighbours using the
Exceptional Pairs of Intra-Technology Neighbours table. You can open this table, select
the exceptional pairs, right-click the table and select Force Exceptional Pairs in the context
menu.
To delete a symmetrical neighbour relation:
3. Select Delete Link and Symmetric Relation from the context menu. The symmetrical neighbour relation between the
To delete several symmetric neighbour relations:
1. Click in the left margin of the table rows containing the neighbours to select the entire rows. You can select contiguous
3. Select Delete Link and Symmetric Relation from the context menu.
To delete a neighbour relation:
284

AT310_UMU_E0
Allocating or Deleting Neighbours on the Map

You can allocate or delete intra-technology neighbours directly on the map using the mouse.
To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neighbours
on the map as explained in "Displaying Neighbour Relations on the Map" on page 280.
To add a symmetrical neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters to
the intra-technology neighbours list.
To remove a symmetrical neighbour relation:
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitters
from the intra-technology neighbours.
To add an outward neighbour relation:
2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the intra-technology neighbour list of the reference transmitter.
To remove an outward neighbour relation:
2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference
transmitter from the intra-technology neighbours list of the reference transmitter.
To add an inward neighbour relation:
Click the reference transmitter on the map. Atoll displays its neighbour relations.
-
If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter.
Atoll converts the symmetric relation to an inward non-symmetric inter-technology neighbour relation.
If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation
by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then press
CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric intertechnology neighbour relation.
To remove an inwards neighbour relation:

2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the transmitter
from the intra-technology neighbours list of the reference transmitter.
When there is more than one cell on the transmitter, clicking the transmitter in the
map window opens a context menu allowing you to select the cell you want (see
You can add or delete either forced neighbours or forbidden neighbours by clicking
the arrow ( ) next to the Edit Relations on the Map button (
) in the Radio
Planning toolbar and selecting either Forced Neighbours or Forbidden Neighbours.
6.2.11.7 Calculating the Importance of Existing Neighbours

After you have imported neighbours into the current Atoll document or manually defined neighbours, Atoll can calculate the
importance of each neighbour, i.e., the weight of each neighbour. This value is used to define a rank for different neighbours
in the AFP process.
Atoll calculates the importance for neighbours of active and filtered transmitters within the focus zone.
To calculate the importance of existing neighbours:
3. Select Neighbours > Intra-technology > Calculate Importance from the context menu. The Neighbour Importance
Evaluation dialogue appears.
4. Select the Intra-carrier Neighbours tab.
285

Forsk 2011
5. Under Importance, enter the Max inter-site distance. Sites outside the defined maximum inter-site distance will not
be considered as possible neighbours.
6. Under Importance, select the factors to be taken into consideration when calculating the importance (for information
on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 276):
-
Take into account the adjacency factor: Select the Take into account the adjacency factor check box to verify that
neighbours are adjacent to their reference transmitters when calculating importance.
Take into account the co-site factor: Select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance.
7. Under Coverage Conditions, you can set the coverage conditions between neighbours and their reference cells.
Clicking Define opens the Coverage Conditions dialogue. In the Coverage Conditions dialogue, you can change the
following parameters:
-
Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour
allocation.
Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell and the
neighbour.
Min. Ec/Io: Enter the minimum Ec Io which must be provided by reference cell in an area with overlapping coverage. The reference cell must also be the best server in terms of pilot quality in the area with overlapping coverage.
Ec/Io Margin: Enter the Ec/Io margin to define the area of coverage overlapping between UMTS cells.
DL Load Contributing to Io: Under DL Load Contributing to Io, select whether you want Atoll to base the interference ratio on the total power used as defined in the properties for each cell (Defined per Cell) or on a percentage
of the maximum power (Global Value).
Shadowing Taken into Account: If desired, select the Shadowing Taken into Account check box and enter a Cell
Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for
indoor coverage.
8. Click OK to save your modifications and close the Coverage Conditions dialogue.
9. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on
the same site as their reference cell when calculating importance (for information on defining importance factors, see
"Configuring Importance Factors for Neighbours" on page 276):
10. Under Coverage Conditions, you can set the coverage conditions between neighbours and their reference cells.
Clicking Define opens the Coverage Conditions dialogue. In the Coverage Conditions dialogue, you can change the
following parameters:
-
Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour
allocation.
Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell and the
neighbour.
Min. Ec/Io: Enter the minimum Ec Io which must be provided by reference cell in an area with overlapping coverage. The reference cell must also be the best server in terms of pilot quality in the area with overlapping coverage.
Ec/Io Margin: Enter the Ec/Io margin to define the area of coverage overlapping between UMTS cells.
DL Load Contributing to Io: Under DL Load Contributing to Io, select whether you want Atoll to base the interference ratio on the total power used as defined in the properties for each cell (Defined per Cell) or on a percentage
of the maximum power (Global Value).
Shadowing Taken into Account: If desired, select the Shadowing Taken into Account check box and enter a Cell
Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for
indoor coverage.
11. Click OK to save your modifications and close the Coverage Conditions dialogue.
Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes
(importance and reason) in a table.
You can use many of Atolls table shortcuts, such as filtering and sorting. For information
on working with data tables, see "Working with Data Tables" on page 47. In addition, by
clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be
calculated.
12. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll
first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices
are not valid, Atoll recalculates them.
Once Atoll has finished calculating importance, the results are displayed in the table on each tab.
286

AT310_UMU_E0
The table contains the following information:

-

Neighbour: The neighbour of the reference transmitter.
Importance (%): The importance as calculated with the options selected in step 5.
Cause: The reason Atoll has calculated the value in the Importance column.
-
Co-site
Adjacency
Symmetry
Coverage
Coverage: The amount of reference transmitters coverage area that the neighbour overlaps, in percentage and
in square kilometres.
Adjacency: The area of the reference transmitter, in percentage and in square kilometres, where the neighbour
transmitter is best server or second best server. This information is not relevant for inter-carrier neighbours and
is therefore not present on the Inter-carrier Neighbours tab.
Distance: The distance in kilometres between the reference cell and the neighbour.
13. Click Commit to commit the importance values and the reasons for allocation to the Neighbours table.
6.2.11.8 Checking the Consistency of the Neighbour Plan

You can perform an audit of the current neighbour allocation plan. When you perform an audit of the current neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit.
To perform an audit of the intra-technology neighbour allocation plan:
3. Select Neighbours > Intra-technology > Audit from the context menu. The Neighbour Audit dialogue appears.
4. Define the parameters of the audit:
-
Neighbourhood Type: Select whether you want to perform an audit on Intra-Carrier or Inter-Carrier neighbour
relations.
Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average
number of neighbours per cell.
Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words,
which cells have an empty neighbour list).
Full Lists: Which cells having the maximum number of neighbours allowed (in other words, which cells have a full
neighbour list). The maximum number of neighbours can be either set here for all transmitters, or specified for
each transmitter in the Cells table.
Lists > Max Number: Which cells having more than the maximum number of neighbours allowed. The maximum
number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Cells
table.
Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site neighbours.
Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have non-symmetric neighbour relations.
Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours
or forbidden neighbours.
Distance Between Neighbours: Select the Distance Between Neighbours check box and enter the distance
between neighbours that must not be exceeded.
5. Click OK to perform the audit. Atoll displays the results of the audit in a new text file:
-
Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan
audited.
Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list)
Syntax:
Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed
in their respective neighbours lists.
Syntax:
|CELL|
|CELL| |NUMBER| |MAX NUMBER|
Lists > Max Number (default max number = Y): x/X; x number of cells out of a total of X having more than Y
number of neighbours listed in their respective neighbours lists.
Syntax:
287

Forsk 2011
If the field Maximum number of intra-technology neighbours in the Cells table is empty,
the Full Lists check and the Lists > Max Number check use the Default Max Number value
defined in the audit dialogue.
-
Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan.
Syntax:
Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan.
Syntax:
|CELL| |NEIGHBOUR|
Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan.
Syntax:
|CELL| |NEIGHBOUR| |TYPE| |REASON|
Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan.
Syntax:
|CELL| |NEIGHBOUR|
Distance Between Neighbours > Y: X; total number of neighbours existing in the audited neighbour plan that are
located at a distance greater than Y.
Syntax:
|CELL| |NEIGHBOUR| |DISTANCE|

You can perform an audit of the inter-technology neighbour allocation plan by selecting
Neighbours > Inter-technology > Audit from the Transmitters folder context menu.
6.2.11.9 Exporting Neighbours

The neighbour data of an Atoll document is stored in a series of tables. You can export the neighbour data to use it in another
application or in another Atoll document.
To export neighbour data:
3. Select Neighbours > and then select the neighbour table containing the data you want to export from the context
menu:
-
Intra-technology > Open Table: This table contains the data for the intra-technology (intra-carrier and inter-carrier) neighbours in the current Atoll document.
Inter-technology > Open Table: This table contains the data for the inter-technology neighbours in the current
Atoll document.
Intra-technology > Exceptional Pairs: This table contains the data for the intra-technology exceptional pairs
(forced and forbidden) in the current Atoll document.
Inter-technology > Exceptional Pairs: This table contains the data for the inter-technology exceptional pairs
(forced and forbidden) in the current Atoll document.
4. When the selected neighbours table opens, you can export the content as described in "Exporting Tables to Text Files"
on page 57.
6.2.12 Planning Scrambling Codes

In UMTS, 512 scrambling codes are available, numbered from 0 to 511. Although UMTS scrambling codes are displayed in decimal format by default, they can also be displayed and calculated in hexadecimal format, in other words using the numbers 0
to 9 and the letters A to F.
Atoll facilitates the management of scrambling codes by letting you create groups of scrambling codes and domains, where
each domain is a defined set of groups.
You can also assign scrambling codes manually or automatically to any cell in the network.
Once allocation is completed, you can audit the scrambling codes, view scrambling code reuse on the map, and make an analysis of scrambling code distribution.
The procedure for planning scrambling codes for a UMTS project is:
Preparing for scrambling code allocation

-
288
"Defining the Scrambling Code Format" on page 289

"Creating Scrambling Code Domains and Groups" on page 289

AT310_UMU_E0
"Defining Exceptional Pairs for Scrambling Code Allocation" on page 290.
Allocating scrambling codes

-
"Automatically Allocating Scrambling Codes to UMTS Cells" on page 291

"Allocating Scrambling Codes to UMTS Cells Manually" on page 293.
"Checking the Consistency of the Scrambling Code Plan" on page 293.
Displaying the allocation of scrambling codes

-
"Using Find on Map to Display Scrambling Code Allocation" on page 294

"Displaying Scrambling Code Allocation Using Transmitter Display Settings" on page 295
"Grouping Transmitters by Scrambling Code" on page 295
"Displaying the Scrambling Code Allocation Histogram" on page 296
"Making a Scrambling Code Collision Zone Prediction" on page 296.
"Making a Scrambling Code Collision Analysis" on page 297
Within the context of primary scrambling code allocation, "neighbours" refer to

intra-carrier neighbours.
According to 3GPP specifications, the 512 possible scrambling codes can be broken
down into groups, each containing 8 codes. Because the term "group" in Atoll
refers to user-defined sets of scrambling codes, these groups of 8 codes each are
referred to as "clusters" in Atoll. As well, Atoll allows you to change the number of
codes in a cluster.
6.2.12.1 Defining the Scrambling Code Format

Scrambling codes can be displayed in decimal or hexadecimal format. The selected format is used to display scrambling codes
in dialogues and tables such as in the Domains and Groups tables, the Cells table, and the Scrambling Code Allocation
dialogue.
The decimal format is the default format in Atoll. The accepted decimal values are from 0 to 511. The decimal format is also
used, even if you have chosen the hexadecimal format, to store scrambling codes in the database and to display scrambling
code distribution or the results of a scrambling code audit.
The hexadecimal format uses the numbers 0 to 9 and the letters A to F for its base characters. In Atoll, hexadecimal values
are indicated by a lower-case "h" following the value. For example, the hexadecimal value "3Fh" is "63" as a decimal value.
You can convert a hexadecimal value to a decimal value with the following equation, where A, B, and C are decimal values
within the hexadecimal index ranges:
2
A 16 + B 16 + C
For example, the hexadecimal value "3Fh" would be calculated as shown below:
2
0 16 + 3 16 + 15 = 63
To define the scrambling code format for an Atoll document:

3. Right-click the Scrambling Codes folder. The context menu appears.

4. Select Format from the context menu and select either Decimal or Hexadecimal.
6.2.12.2 Creating Scrambling Code Domains and Groups

Atoll facilitates the management of scrambling codes by letting you create domains, each containing groups of scrambling
codes.
The procedure for managing scrambling codes in a UMTS document consists of the following steps:
1. Creating a scrambling code domain, as explained in this section.
2. Creating groups, each containing a range of scrambling codes, and assigning them to a domain, as explained in this
section.
3. Assigning a scrambling code domain to a cell or cells. If there is no scrambling code domain, Atoll will consider all 512
possible scrambling codes when assigning codes.
To create a scrambling code domain:
289

Forsk 2011
) to expand the Scrambling Codes folder.
4. Right-click Domains in the Scrambling Codes folder. The context menu appears.
5. Select Open Table from the context menu. The Domains table appears.
), enter a Name for the new domain.
7. Click in another cell of the table to create the new domain and add a new blank row to the table.
8. Double-click the domain to which you want to add a group. The domains Properties dialogue appears.
9. Under Groups, enter the following information for each group you want to create.
-
Name: Enter a name for the new scrambling code group.

Min.: Enter the lowest available primary scrambling code in this groups range. The minimum and maximum
scrambling codes must be entered in the format, decimal or hexadecimal, set for the Atoll document (for information on setting the scrambling code format, see "Defining the Scrambling Code Format" on page 289).
Max: Enter the highest available primary scrambling code in this groups range.
Step: Enter the separation interval between each primary scrambling code.
Excluded: Enter the scrambling codes in this range that you do not want to use.
Extra: Enter any additional scrambling codes (i.e., outside the range defined by the Min. and Max fields) you want
to add to this group. You can enter a list of codes separated by either a comma, semi-colon, or a space. You can
also enter a range of scrambling codes separated by a hyphen. For example, entering, "1, 2, 3-5" means that the
extra scrambling codes are "1, 2, 3, 4, 5."
10. Click in another cell of the table to create the new group and add a new blank row to the table.
6.2.12.3 Defining Exceptional Pairs for Scrambling Code Allocation

You can also define pairs of cells which cannot have the same primary scrambling code. These pairs are referred to as exceptional pairs. Exceptional pairs are used along with other constraints, such as neighbours, reuse distance, and domains, in allocating scrambling codes.
To create a pair of cells that cannot have the same scrambling code:
3. Select Primary Scrambling Codes > Exceptional Pairs. The Exceptional Separation Constraints table appears. For
information on working with data tables, see "Working with Data Tables" on page 47.
), select one cell of the new exceptional pair in the Cell column and
the second cell of the new exceptional pair from the Cell_2 column.
5. Click in another cell of the table to create the new exceptional pair and add a new blank row to the table.
6.2.12.4 Allocating Scrambling Codes

Atoll can automatically assign scrambling codes to the cells of a UMTS network according to set parameters. For example, it
takes into account the definition of groups and domains of scrambling codes, the selected scrambling code allocation strategy
(clustered, distributed per cell, distributed per site and one cluster per site), minimum code reuse distance, and any
constraints imposed by neighbours.
You can also allocate scrambling codes manually to the cells of a UMTS network.
In this section, the following methods of allocating scrambling codes are described:
"Defining Automatic Allocation Constraint Violation Costs" on page 290

"Automatically Allocating Scrambling Codes to UMTS Cells" on page 291
"Allocating Scrambling Codes to UMTS Cells Manually" on page 293.
Defining Automatic Allocation Constraint Violation Costs

You can define the costs of the different types of constraints used in the automatic scrambling code allocation algorithm.
To define the different constraint violation costs:
3. Select Primary Scrambling Codes > Constraint Costs. The Constraint Violation Costs dialogue appears. In this dialogue
you can define the following costs of constraint violations for the automatic allocation process (the cost is a value from
0 to 1):
-
290
Under Intra-technology Neighbours, you can set the constraint violation cost for 1st Order, 2nd Order, and 3rd
Order neighbours.

AT310_UMU_E0
Under Distributed per Site Strategy, you can set the constraint violation cost for intra-technology neighbours that
are 1st or 2nd Order Using the Same Cluster.
Reuse Distance: Enter the maximum cost for reuse distance constraint violations.
Exceptional Pair: Enter the cost for exceptional pair constraint violations.
Common Inter-technology Neighbour: Enter the cost for inter-technology neighbour constraint violations.
4. Click OK. The constraint violation costs are stored and will be used in the automatic allocation.
Automatically Allocating Scrambling Codes to UMTS Cells
The allocation algorithm enables you to automatically allocate primary scrambling codes to cells in the current network. You
can choose among several automatic allocation strategies. The actual automatic allocation strategies available will depend on
your network and options selected in the atoll.ini file. For more information on the atoll.ini file, see the Administrator Manual.
For more information on automatic allocation strategies, see the Technical Reference Guide.
Clustered: The purpose of this strategy is to choose for a group of mutually constrained cells, scrambling codes among
a minimum number of clusters. In this case, Atoll will preferentially allocate all the codes from the same cluster.
Distributed per Cell Allocation: This strategy consists in using as many clusters as possible. Atoll will preferentially
allocate codes from different clusters.
One Cluster per Site: This strategy allocates one cluster to each base station, then, one code of the cluster to each cell
of each base station. When all the clusters have been allocated and there are still base stations remaining to be allocated, Atoll reuses the clusters at another base station.
Distributed per Site: This strategy allocates a group of adjacent clusters to each base station in the network, then, one
cluster to each transmitter of the base station according to its azimuth and finally one code of the cluster to each cell
of each transmitter. The number of adjacent clusters per group depends on the number of transmitters per base station you have in your network; this information is required to start allocation based on this strategy. When all the
groups of adjacent clusters have been allocated and there are still base stations remaining to be allocated, Atoll reuses
the groups of adjacent clusters at another base station.
To automatically allocate primary scrambling codes:

3. Select Primary Scrambling Codes > Automatic Allocation. The Primary Scrambling Codes dialogue appears.
-
Under Constraints, you can set the constraints on automatic scrambling code allocation.
-
Existing Neighbours: Select the Existing Neighbours check box if you want to consider intra-carrier neighbour
relations and then choose the neighbourhood level to take into account:
Neighbours of a cell are referred to as the first order neighbours, neighbours neighbours are referred to as
the second order neighbours and neighbours neighbours neighbours as the third order neighbours.
First Order: No cell will be allocated the same scrambling code as its neighbours.
Second Order: No cell will be allocated the same scrambling code as its neighbours or its second order neighbours.
Third Order: No cell will be allocated the same scrambling code as its neighbours or its second order neighbours or its third order neighbours.
Atoll can only consider neighbour relations if neighbours have already been allocated. For information on allocating neighbours, see "Planning Neighbours" on page 274.
Atoll can take into account inter-technology neighbour relations as constraints when allocating scrambling codes to the UMTS neighbours of a GSM transmitter. In order to
consider inter-technology neighbour relations in scrambling code allocation, you must
make the Transmitters folder of the GSM Atoll document accessible in the UMTS Atoll
document. For information on making links between GSM and UMTS Atoll documents, see
"Creating a UMTS Sector From a Sector in the Other Network" on page 407
Additional Overlapping Conditions: Select the Additional Overlapping Conditions check box, if you want to
set overlapping coverage criteria. If cells meet the overlapping conditions to enter the reference cells active
set, they will be not allocated the same scrambling code as the reference cell. Click Define to change the overlapping conditions. In the Coverage Conditions dialogue, you can change the following parameters:
Min. EcI0: Enter the minimum Ec I0 which must be provided by reference cell A in an area with overlapping
coverage. Reference cell A must also be the best server in terms of pilot quality in the area with overlapping
coverage.
291

Forsk 2011
EcI0 Margin: Enter the maximum dierence of Ec I0 between reference cell A and possible neighbour cell B
in the area with overlapping coverage.
Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses in the calculations.
-
Reuse Distance: Select the Reuse Distance check box, if you want to the automatic allocation process to consider the reuse distance constraint. Enter the Default reuse distance within which two cells on the same carrier
cannot have the same primary scrambling code.
A reuse distance can be defined at the cell level (in the cell Properties dialogue or in the
Cells table). If defined, a cell-specific reuse distance will be used instead of the value
entered here.
From the Strategy list, you can select an automatic allocation strategy:
-
Exceptional Pairs: Select the Exceptional Pairs check box, if you want to the automatic allocation process to
consider the exceptional pair constraints.
Clustered
Distributed per Cell
One Cluster per Site
Distributed per Site
Carrier: Select the Carrier on which you want to run the allocation. You may choose one carrier (Atoll will assign
primary scrambling codes to transmitters using the selected carrier) or all of them.
No. of Codes per Cluster: According to 3GPP specifications, the number of codes per cluster is 8. If you want, you
can change the number of codes per cluster.
When the allocation is based on a distributed strategy (Distributed per Cell or Distributed per Site), this parameter can also be used to define the interval between the primary scrambling codes assigned to cells on a same site.
The defined interval is applied by setting an option in the atoll.ini file. For more information about setting options
in the atoll.ini file, see the Administrator Manual.
Use a Max of Codes: Select the Use a Max of Codes check box to make Atoll use the maximum number of codes.
For example, if there are two cells using the same domain with two scrambling codes, Atoll will assign the
remaining code to the second cell even if there are no constraints between these two cells (for example, neighbour relations, reuse distance, etc.). If you do not select this option, Atoll only checks the constraints, and allocates
the first ranked code in the list.
Delete Existing Codes: Select the Delete Existing Codes check box if you want Atoll to delete currently allocated
scrambling codes and recalculate all scrambling codes. If you do not select this option, Atoll will keep currently
allocated scrambling codes and will only allocate scrambling codes to cells that do not yet have codes allocated.
Allocate Carriers Identically: Select the Allocate Carriers Identically check box if you want Atoll to allocate the
same primary scrambling code to each carrier of a transmitter. If you do not select this option, Atoll allocates
scrambling codes independently for each carrier.
4. Click Calculate. Atoll begins the process of allocating scrambling codes.

Once Atoll has finished allocating scrambling codes, the codes are visible under Results. Atoll only displays newly allocated scrambling codes.
-
Site: The name of the base station.

Cell: The name of the cell.
Code: The primary scrambling code allocated to the cell.
Cluster: The cluster the scrambling code belongs to.
5. Click Commit. The primary scrambling codes are committed to the cells.
You can save automatic scrambling code allocation parameters in a user configuration. For
information on saving automatic scrambling code allocation parameters in a user configuration, see "Saving a User Configuration" on page 76.
292

AT310_UMU_E0
If you need to allocate scrambling codes to the cells on a single transmitter, you can
allocate them automatically by selecting Allocate Scrambling Codes from the
transmitters context menu.
If you need to allocate scrambling codes to all the cells on group of transmitters,
you can allocate them automatically by selecting Primary Scrambling Codes >
Automatic Allocation from the transmitter groups context menu.
Allocating Scrambling Codes to UMTS Cells Manually

When you allocate scrambling codes to a large number of cells, it is easiest to let Atoll allocate scrambling codes automatically,
as described in "Automatically Allocating Scrambling Codes to UMTS Cells" on page 291. However, if you want to add a
primary scrambling code to one cell or to modify the primary scrambling code of a cell, you can do it by accessing the properties of the cell.
To allocate a scrambling code to a UMTS cell manually:
1. On the map, right-click the transmitter to whose cell you want to allocate a scrambling code. The context menu
appears.
3. Select the Cells tab.
4. Enter a Primary Scrambling Code in the cells column.
5. Click OK.
6.2.12.5 Checking the Consistency of the Scrambling Code Plan

Once you have completed allocating scrambling codes, you can verify whether the allocated scrambling codes respect the
specified constraints by performing an audit of the plan. The scrambling code audit also enables you to check for inconsistencies if you have made some manual changes to the allocation plan.
To perform an audit of the allocation plan:
3. Select Primary Scrambling Codes > Audit. The Code and Cluster Audit dialogue appears.
4. In the Code and Cluster Audit dialogue, select the allocation criteria that you want to check:
-
No. of Codes per Cluster: Enter the number of scrambling codes per cluster.
Neighbours: Select Neighbours to check scrambling code constraints between cells and their neighbours and then
choose the neighbourhood level to take into account:
-
First Order: Atoll will check that no cell has the same scrambling code as any of its neighbours.
Second Order Neighbours: Atoll will check that no cell has the same scrambling code as any of its neighbours
or any of the neighbours of its neighbours.
Third Order Neighbours: Atoll will check that no cell has the same scrambling code as any of its neighbours or
any of the neighbours of its neighbours or any of the neighbours of its second order neighbours.
The report will list the cells and the neighbours that do not meet any of these constraints. In addition, it will indicate the allocated primary scrambling code and the neighbourhood level.
-
Neighbours in Different Clusters: If you select the Neighbours in different clusters check box, Atoll will check that
neighbour cells have scrambling codes from different clusters. The report will list any neighbour cells that do have
scrambling codes from the same cluster.
Domain Compliance: If you select the Domain Compliance check box, Atoll will check if allocated scrambling
codes belong to domains assigned to cells. The report will list any cells with scrambling codes that do not belong
to domains assigned to the cell.
Site Domains Not Empty: If you select the Site Domains Not Empty check box, Atoll will check for and list base
stations for which the allocation domain (i.e., the list of possible scrambling codes) is not consistent with the "One
cluster per site" strategy. If there is a base station with N cells, Atoll will check that the domains assigned to the
cells contain at least one cluster consisting of N codes. If you plan to automatically allocate scrambling codes using
the "One Cluster per Site" strategy, you can perform this test beforehand to check the consistency of domains
assigned to cells of each base station.
One Cluster per Site: If you select the One Cluster per Site check box, Atoll will check for and list base stations
whose cells have scrambling codes coming from more than one cluster.
Distance: If you select the Distance check box and set a reuse distance, Atoll will check for and list the cell pairs
that do not respect the reuse distance condition. For any cell pair, Atoll uses the lowest of the reuse distance
values defined in the properties of the two cells and the value that you set in the Code and Cluster Audit dialogue.
293

Forsk 2011
Cell pairs that do not respect the reuse distance condition are listed in increasing order of the distance between
them. The primary scrambling code and the reuse distance are also listed for each cell pair.
Exceptional Pairs: If you select the Exceptional Pairs check box, Atoll will check for and display pairs of cells that
are listed as exceptional pairs but still use the same scrambling code.
5. Click OK. Atoll displays the results of the audit in a text file called CodeCheck.txt, which it opens at the end of the audit.
For each selected criterion, Atoll gives the number of detected inconsistencies and details each of them.
6.2.12.6 Displaying the Allocation of Scrambling Codes

Once you have completed allocating scrambling codes, you can verify several aspects of scrambling code allocation. You have
several options for displaying scrambling codes:
"Using Find on Map to Display Scrambling Code Allocation" on page 294

"Displaying Scrambling Code Allocation Using Transmitter Display Settings" on page 295
"Grouping Transmitters by Scrambling Code" on page 295
"Displaying the Scrambling Code Allocation Histogram" on page 296
"Making a Scrambling Code Collision Zone Prediction" on page 296.
"Making a Scrambling Code Collision Analysis" on page 297
Using Find on Map to Display Scrambling Code Allocation

In Atoll, you can search for scrambling codes and scrambling code groups using the Find on Map tool. Results are displayed
in the map window in red.
If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results
displayed by transmitter, the search results will be displayed by transmitter coverage. Scrambling codes and scrambling code
groups and any potential problems will then be clearly visible. For information on coverage predictions by transmitter, see
"Making a Coverage Prediction by Transmitter" on page 239.
To find scrambling codes or scrambling code groups using the Find on Map tool:
1. Click Tools > Find on Map. The Find on Map window appears.
2. From the Find list, select "Scrambling Code."
3. Select what you what you want to search for:
-
Scrambling code: If you want to find a scrambling code, select Scrambling code and select it from the list.
SC Group: If you want to find a scrambling code group, select SC group and select it from the list.
4. Select the carrier you want to search on from the For carrier list, or select "(All)" to search in all carriers.
5. Click Search. Transmitters with cells matching the search criteria are displayed in red. Transmitters that do not match
the search criteria are displayed as grey lines.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
1. Create, calculate, and display a coverage prediction by transmitter. For information on coverage predictions by transmitter, see "Making a Coverage Prediction by Transmitter" on page 239.
2. Click View > Search Tool. The Search Tool window appears.
The Search Tool window is a docking window. For information on docking windows, see "Docking or Floating an Atoll
Window" on page 16.
3. You can search either for a specific scrambling code or scrambling code group:
To search for a scrambling code:
a. Select Scrambling Code.
b. Enter a scrambling code in the text box.
To search for a scrambling code group:
a. Select SC Group.
b. Select a scrambling code group from the list.
4. Select the carrier you want to search on from the For the Carrier list, or select "(All)" to search for the scrambling code
or scrambling code group in all carriers.
5. Click Search. Transmitters with cells matching the search criteria are displayed in red. Transmitters that do not match
the search criteria are displayed as grey lines.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
294

AT310_UMU_E0
Displaying Scrambling Code Allocation Using Transmitter Display Settings

You can use the display characteristics of transmitters to display scrambling code-related information.
To display scrambling code-related information on the map:
You can display the following information per transmitter:
-
Primary scrambling code: To display the primary scrambling code of a transmitters cell, select "Discrete values"
as the Display Type and "Cells: Primary Scrambling Code" as the Field.
Ranges of primary scrambling codes: To display ranges of primary scrambling codes, select "Value intervals" as
the Display Type and "Cells: Primary Scrambling Code" as the Field.
Scrambling code domain: To display the scrambling code domain of a transmitters cell, select "Discrete values"
as the Display Type and "Cells: Scrambling Code Domain" as the Field.
You can display the following information in the transmitter label or tip text by clicking the Label or Tip Text Browse
button (
-
):
Primary scrambling code: To display the primary scrambling code of a transmitters cell in the transmitter label or
tip text, "Cells: Primary Scrambling Code" from the Label or Tip Text Field Definition dialogue.
Scrambling code domain: To display the primary scrambling code domain of a transmitters cell in the transmitter
label or tip text, "Cells: Scrambling Code Domain" from the Label or Tip Text Field Selection dialogue.
Scrambling code reuse distance: To display the scrambling code reuse distance of a transmitters cell in the transmitter label or tip text, "Cells: SC Reuse Distance" from the Label or Tip Text Field Selection dialogue.
5. Click OK.
For information on display options, see "Display Properties of Objects" on page 23.
Grouping Transmitters by Scrambling Code
You can group transmitters on the Network tab of the Explorer window by their primary scrambling code, their scrambling
code domain, or by their scrambling code reuse distance.
To group transmitters by scrambling code:
4. On the General tab, click Group by. The Group dialogue appears.
5. Under Available Fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
-
Scrambling Code Domain

Primary Scrambling Code
SC Reuse Distance
7. Click
to add the parameter to the Grouping Fields list. The selected parameter is added to the list of parameters
on which the transmitters will be grouped.
8. If you do not want the transmitters to be sorted by a certain parameter, select it in the Grouping Fields list and click
. The selected parameter is removed from the list of parameters on which the transmitters will be grouped.
9. Arrange the parameters in the Grouping Fields list in the order in which you want the transmitters to be grouped:
a. Select a parameter and click
to move it up to the desired position.
b. Select a parameter and click
to move it down to the desired position.
10. Click OK to save your changes and close the Group dialogue.
If a transmitter has more than one cell, Atoll cannot arrange the transmitter by cell. Transmitters that cannot be grouped by cell are arranged in a separate folder under the Transmitters folder.
295

Forsk 2011
Displaying the Scrambling Code Allocation Histogram

You can use a histogram to analyse the use of allocated scrambling codes in a network. The histogram represents the scrambling codes or scrambling code clusters as a function of the frequency of their use.
To display the scrambling code histogram:
3. Select Primary Scrambling Codes > Code Distribution. The Distribution Histograms dialogue appears.
Each bar represents a scrambling code or a cluster, its height depending on the frequency of its use.
4. Select Scrambling Codes to display scrambling code use and Clusters to display scrambling code cluster use.
5. Move the pointer over the histogram to display the frequency of use of each scrambling code or cluster. The results
are highlighted simultaneously in the Detailed Results list.
Making a Scrambling Code Collision Zone Prediction
You can make a scrambling code collision zone prediction to view areas covered by cells using the same scrambling code. Atoll
checks on each pixel whether the best server and other servers satisfying the conditions to enter the user active set have the
same scrambling code. If so, Atoll considers that there is scrambling code collision.
To make a scrambling code collision zone prediction:
4. Select Scrambling Zone Collision Zones and click OK.
which sites to display in the results. For information on filtering, see "Filtering Data" on page 71. Under Configuration,
you can create a Filter to select which sites to display in the results. You can also display the results grouped on the
Network tab by one or more characteristics by clicking the Group By button, or you can display the results sorted by
clicking the Sort button. For information on filtering, see "Filtering Data" on page 71; for information on grouping, see
"Advanced Grouping" on page 66; for information on sorting, see "Advanced Sorting" on page 70.
also select which Carrier is to be considered.
If you want the scrambling code collision zone prediction to consider shadowing, you can select the Shadowing taken
into account check box and enter a percentage in the Cell edge coverage probability text box.
For a scrambling code collision zone prediction, the Display Type "Discrete Values" based on the Field "Transmitter"
is selected by default. Each pixel where there is scrambling code collision is displayed with the same colour as that
defined for the interfered transmitter. In the Explorer window, the coverage prediction results are first arranged by
interfered transmitter and then by interferer. For information on defining display properties, see "Display Properties
of Objects" on page 23.
-
296
The number of interferers for each transmitter: Select "Value Intervals" as the Display Type and "No. of Interferers per Transmitter" as the Field. In the Explorer window, the coverage prediction results are arranged by interfered transmitter.

AT310_UMU_E0
The total number of interferers on one pixel: Select "Value Intervals" as the Display Type and "No. of Interferers"
as the Field. In the Explorer window, the coverage prediction results are arranged according to the number of
interferers.
8. Click the Calculate button (

) in the Radio Planning toolbar to calculate the scrambling code collision zone prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Making a Scrambling Code Collision Analysis
The SC Collisions tab of the Point Analysis window gives you information on reception for any point on the map where there
is scrambling code collision. Scrambling code collision occurs when the best server and other servers satisfying the conditions
to enter the user active set have the same scrambling code. When there is scrambling code collision, Atoll displays the pilot
quality (Ec I0) received from interfered and interferer transmi ers.
The analysis is based on the UL load percentage and the DL total power of each cell. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility, and a service.
You can make a scrambling code collision analysis to verify a scrambling code collision zone prediction. In this case, before you
make the scrambling code collision analysis, ensure the coverage prediction you want to use in the scrambling code collision
analysis is displayed on the map.
To make a scrambling code collision analysis:
) on the toolbar. The Point Analysis window appears.
2. At the top of the Point Analysis window, select the SC Collisions view.
3. At the top of the SC Collisions view, select "Cells Table" from Load conditions.
4. If you are making a scrambling code collision analysis to verify a coverage prediction, you can recreate the conditions
of the coverage prediction:
a. Select the same Terminal, Service, and Mobility studied in the coverage prediction.
b. Select the Carrier studied in the coverage prediction.
c. Click the Options button (
-
Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and, select
"Ec I0" from the Shadowing Margin list.
Select the Indoor Coverage check box to add indoor losses.
d. Click OK to close the Properties dialogue.

If you are making a scrambling code collision analysis to make a prediction on a defined
point, you can use the instructions in this step to define a user.
5. Move the pointer over the map to make a scrambling code collision analysis for the current location of the pointer.
6.3 Studying Network Capacity

A UMTS network automatically regulates power on both uplink and downlink with the objective of minimising interference
and maximising network capacity. In the case of HSDPA, the network uses A-DCH power control in the uplink and downlink
and a fast link adaptation (in other words, the selection of an HSDPA bearer) in the downlink. Atoll can simulate these network
regulation mechanisms, thereby enabling you to study the capacity of the UMTS network.
In Atoll, a simulation is based on a realistic distribution of R99 and HSDPA users at a given point in time. The distribution of
users at a given moment is referred to as a snapshot. Based on this snapshot, Atoll calculates various network parameters
such as the active set for each mobile, the required power of the mobile, the total DL power and DL throughput per cell, and
the UL load per cell. Simulations are calculated in an iterative fashion.
When several simulations are performed at the same time using the same traffic information, the distribution of users will be
different, according to a Poisson distribution. Consequently you can have variations in user distribution from one snapshot to
another.
297

Forsk 2011
To create snapshots, services and users must be modelled. As well, certain traffic information in the form of traffic maps must
be provided. Once services and users have been modelled and traffic maps have been created, you can make simulations of
the network traffic.
"Defining Multi-service Traffic Data" on page 298

"Creating a Traffic Map" on page 298
"Calculating and Displaying Traffic Simulations" on page 308
"Analysing the Results of a Simulation" on page 328.
6.3.1 Defining Multi-service Traffic Data

The first step in making a simulation is defining how the network is used. In Atoll, this is accomplished by creating all of the
parameters of network use, in terms of services, users, and equipment used.
The following services and users are modelled in Atoll in order to create simulations:
R99 radio bearers: Bearer services are used by the network for carrying information. The R99 Radio Bearer table lists
all the available radio bearers. You can create new R99 radio bearers and modify existing ones by using the R99 Radio
Bearer table. For information on defining R99 radio bearers, see "Defining R99 Radio Bearers" on page 412.
Services: Services are the various services, such as voice, mobile internet access, etc., available to subscribers. These
services can be either circuit-switched or packet-switched. For information on modelling end-user services, see "Modelling UMTS HSPA Services" on page 252.
Mobility type: In UMTS, information about receiver mobility is important to efficiently manage the active set: a mobile
used by a driver moving quickly or a pedestrian will not necessarily be connected to the same transmi ers. Ec I0
requirements and Eb Nt targets per radio bearer and per link (uplink or downlink) are largely dependent on mobile
speed. For information on creating a mobility type, see "Creating a UMTS HSPA Mobility Type" on page 254.
Terminals: In UMTS, a terminal is the user equipment that is used in the network, for example, a mobile phone, a PDA,
or a cars on-board navigation device. For information on creating a terminal, see "Modelling UMTS HSPA Terminals"
on page 255.
6.3.2 Creating a Traffic Map

The following sections describe the different types of traffic maps available in Atoll and how to create, import, and use them.
Atoll provides three types of traffic maps for UMTS projects.
Sector traffic map

User profile traffic map
User density traffic map (number of users per km2)
These maps can be created using different types of traffic data sources as follows:
Sector traffic maps can be used if you have live traffic data from the OMC (Operation and Maintenance Centre).
The OMC (Operations and Maintenance Centre) collects data from all cells in a network. This includes, for example,
the number of users or the throughput in each cell and the traffic characteristics related to different services. Traffic
is spread over the best server coverage area of each transmitter and each coverage area is assigned either the
throughputs in the uplink and in the downlink or the number of users per activity status or the total number of users
(including all activity statuses). For more information, see "Creating a Sector Traffic Map" on page 298.
User profile traffic maps can be used if you have marketing-based traffic data.
User profile traffic maps, where each vector (polygon, line, or point) describes subscriber densities (or numbers of
subscribers for points) with user profiles and mobility types, and user profile environment based traffic maps, where
each pixel has an assigned environment class. For more information, see "Importing a User Profile Traffic Map" on
page 302, "Importing a User Profile Environment Based Traffic Map" on page 304, and "Creating a User Profile Environment Based Traffic Map" on page 304.
User density traffic maps (number of users per km2) can be used if you have population-based traffic data, or 2G network statistics.
Each pixel has a user density assigned. The value either includes all activity statuses, or it corresponds to a particular
activity status. For more information, see "Importing a User Density Traffic Map" on page 305, "Creating a User
Density Traffic Map" on page 306, "Converting 2G Network Traffic" on page 307 and "Exporting Cumulated Traffic" on
page 307.
6.3.2.1 Creating a Sector Traffic Map

This section explains how to create a sector traffic map in Atoll to model traffic.
298

AT310_UMU_E0
You can input either the throughput demands in the uplink and in the downlink, the number of users per activity status, or
the total number of users including all activity statuses. A coverage prediction by transmitter is required to create this traffic
map. If you do not already have a coverage prediction by transmitter in your document, you must create and calculate it. For
more information, see "Making a Coverage Prediction by Transmitter" on page 239.
To create a sector traffic map:
2. Right-click the Traffic Maps folder. The context menu appears.
3. Select New Map from the context menu. The New Traffic Map dialogue appears.
4. Select Sector Traffic Map.
5. Select the type of traffic information you want to input. You can choose between Uplink and Downlink Throughputs,
Total Number of Users (All Activity Statuses) or Number of Users per Activity Status.
6. Click the Create button. The Sector Traffic Map dialogue appears.
You can also import a traffic map from a file by clicking the Import button. You can import
AGD (Atoll Geographic Data) format files that you have exported from an other Atoll document.
7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter.
8. Enter the data required in the Sector Traffic Map dialogue:
-
If you have selected Uplink and Downlink Throughputs, enter the throughput demands in the uplink and downlink
for each sector and for each listed service.
If you have selected Total Number of Users (All Activity Statuses), enter the number of connected users for each
sector and for each listed service.
If you have selected Number of Users per Activity Status, enter the number of inactive users, the number of users
active in the uplink, in the downlink and in the uplink and downlink, for each sector and for each service.
You can also import a text file containing the data by clicking the Actions button and selecting Import Table from the menu. For more information on importing table data, see
"Importing Tables from Text Files" on page 58.
9. Click OK. The Sector Traffic Map Properties dialogue appears.

10. Select the Traffic tab.
11. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal
100.
12. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal
100.
13. Under Clutter Distribution, for each clutter class, enter:
-
A weight to spread the traffic over the vector.

The percentage of indoor users. An additional loss will be counted for indoor users during Monte-Carlo simulations.
14. Click OK. Atoll creates the traffic map in the Traffic Maps folder.
You can modify the sector traffic map after it has been created.
To modify the sector traffic map:
) to expand the Traffic Maps folder.
3. Right-click the traffic map based on live data that you want to update. The context menu appears.
4. Select Properties from the context menu. The Sector Traffic Map dialogue appears.
100.
100.
8. Under Clutter Distribution, for each clutter class, enter a weight to spread the traffic over the clutter classes and the
percentage of indoor users.
299

Forsk 2011
9. Click OK. Atoll saves the traffic map with its modifed values.
You can update the information, throughput demands and the number of users, on the map afterwards. You can update
sector traffic maps if you add or remove a base station. You must first recalculate the coverage prediction by transmitter. For
more information, see "Making a Coverage Prediction by Transmitter" on page 239. Once you have recalculated the coverage
prediction, you can update the traffic map.
To update the traffic map:
3. Right-click the sector traffic map that you want to update. The context menu appears.
4. Select Update from the context menu. The Sector Traffic Map dialogue appears.
5. Select the updated coverage prediction by transmitter and define traffic values for the new transmitter(s) listed at the
bottom of the table. Deleted or deactivated transmitters are automatically removed from the table.
6. Click OK. The Sector Traffic Map Properties dialogue appears.
If desired you can update the values under Terminals (%), Mobilities (%), and Clutter Distribution.
7. Click OK. The traffic map is updated on the basis of the selected coverage prediction by transmitter.
If you want to extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account
any clutter weighting defined for the sector traffic map, you can create user density traffic maps from sector traffic maps. For
more information, see "Creating User Density Traffic Maps from Sector Traffic Maps" on page 307.
6.3.2.2 Creating a User Profile Traffic Map

The marketing department can provide information which can be used to create traffic maps. This information describes the
behaviour of different types of users. In other words, it describes which type of user accesses which services and for how long.
There might also be information about the type of terminal devices they use to access different services.
In Atoll, this type of data can be used to create user profile traffic maps.
A user profile models the behaviour of different subscriber categories. Each user profile is defined by a list of services which
are in turn defined by the terminal used, the calls per hour, and duration (for circuit-switched calls) or uplink and downlink
volume (for packet-switched calls).
Environment classes are used to describe the distribution of subscribers on a map. An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of subscribers
with the same profile per km).
The sections "Importing a User Profile Traffic Map" on page 302, "Importing a User Profile Environment Based Traffic Map"
on page 304 and "Creating a User Profile Environment Based Traffic Map" on page 304 describe how to use traffic data from
the marketing department in Atoll to model traffic.
"Modelling User Profiles" on page 300

"Modelling Environments" on page 301.
Modelling User Profiles

You can model variations in user behaviour by creating different profiles for different times of the day or for different circumstances. For example, a user may be considered a business user during the day, with video conferencing and voice, but no web
browsing. In the evening the same user might not use video conferencing, but might use multi-media services and web browsing.
To create or modify a user profile:
3. Right-click the User Profiles folder. The context menu appears.

4. Select New from the context menu. The User Profiles New Element Properties dialogue appears.
You can modify the properties of an existing user profile by right-clicking the user profile
in the User Profiles folder and selecting Properties from the context menu.
300

AT310_UMU_E0
5. You can modify the following parameters:

-
Service: Select a service from the list. For information on services, see "Modelling UMTS HSPA Services" on
page 252.
Terminal: Select a terminal from the list. For information on terminals, see "Modelling UMTS HSPA Terminals" on
page 255.
Calls/Hour: For circuit-switched services, enter the average number of calls per hour for the service. The number
of calls per hour is used to calculate the activity probability. For circuit-switched services, one call lasting 1000 seconds presents the same activity probability as two calls lasting 500 seconds each.
For packet-switched services, the Calls/Hour value is defined as the number of sessions per hour. A session is like
a call in that it is defined as the period of time between when a user starts using a service and when he stops using
a service. In packet-switched services, however, he may not use the service continually. For example, with a webbrowsing service, a session starts when the user opens his browsing application and ends when he quits the
browsing application. Between these two events, the user may be downloading web pages and other times he
may not be using the application, or he may be browsing local files, but the session is still considered as open. A
session, therefore, is defined by the volume transferred in the uplink and downlink and not by the time.
In order for all the services defined for a user profile to be taken into account during traffic
scenario elaboration, the sum of activity probabilities must be lower than 1.
Duration: For circuit-switched services, enter the average duration of a call in seconds. For packet-switched services, this field is left blank.
UL Volume: For packet-switched services, enter the average uplink volume per session in kilobytes.
DL Volume: For packet-switched services, enter the average downlink volume per session in kilobytes.
Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given
density (i.e., the number of subscribers with the same profile per km). To get an appropriate user distribution, you can assign
a weight to each clutter class for each environment class. You can also specify the percentage of indoor subscribers for each
clutter class. In a Monte-Carlo simulation, an additional loss will be added to the indoor users path loss.
To create or modify a UMTS environment:
3. Right-click the Environments folder. The context menu appears.

4. Select New from the context menu. The Environments New Element Properties dialogue appears.
You can modify the properties of an existing environment by right-clicking the environment in the Environments folder and selecting Properties from the context menu.

6. Enter a Name for the new UMTS environment.
), set the following parameters for each user profile/mobility combination that this UMTS environment will describe:
-
User: Select a user profile.

Mobility: Select a mobility type.
Density (Subscribers/km2): Enter a density in terms of subscribers per square kilometre for the combination of
user profile and mobility type.
8. Click the Clutter Weighting tab.

9. For each clutter class, enter a weight that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk Sk
N k = N Area -------------------------Wi Si
301

Forsk 2011
where:
Nk
N Area =
Number of users in the clutter k

Number of users in the zone Area
Wk
Weight of clutter k
Sk
Surface area of clutter k (in square km)
For example: An area of 10 km with a subscriber density of 100/km. Therefore, in this area, there are 1000 subscribers. The area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1" and for Building is "4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter class and 800 in
the Building clutter class.
10. If you want you can specify a percentage of indoor subscribers for each clutter class. During a Monte-Carlo simulation,
an additional loss will be added to the indoor users path loss.
6.3.2.2.1
Importing a User Profile Traffic Map

User profile traffic maps are composed of vectors (either points with a number of subscribers, lines with a number of subscribers km, or polygons with a number of subscribers km) with a user profile, mobility type, and trac density assigned to each
vector.
To import a user profile traffic map:
4. Select User profile traffic map.
5. Select User profile densities from the list.
6. Click the Import button. The Open dialogue appears.
You can also create a traffic map manually in Atoll by clicking the Create button in the New
Traffic Map dialogue. For information, see "Creating a User Density Traffic Map" on
page 306.
7. Select the file to import.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears.
11. Select the Traffic tab (see Figure 6.35). Under Traffic fields, you can specify the user profiles to be considered, their
mobility type (km h), and their density. If the file you are impor ng has this data, you can define the trac characteristics by identifying the corresponding fields in the file. If the file you are importing does not have data describing the
user profile, mobility, or density, you can assign values. When you assign values, they apply to the entire map.
302

AT310_UMU_E0
Figure 6.35: Traffic map properties dialogue - Traffic tab

Define each of the following:
-
User profile: If you want to import user profile information from the file, under Defined, select "By field" and
select the source field from the Choice column. If you want to assign a user profile from the Traffic Parameters
folder of the Parameters tab, under Defined, select "By value" and select the user profile in the Choice column.
Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select the
source field from the Choice column. If you want to assign a mobility type from the Traffic Parameters folder of
the Parameters tab, under Defined, select "By value" and select the mobility type in the Choice column.
Density: If you want to import density information from the file, under Defined, select "By field" and select the
source field from the Choice column. If you want to assign a density, under Defined, select "By value" and enter a
density in the Choice column for the combination of user profile and mobility type. In this context, the term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kilometre for
polygons, the number of subscribers per kilometre in case of lines and the number of subscribers when the map
consists of points.
When you import user profile or mobility information from the file, the values in the file
must be exactly the same as the corresponding names in the Traffic Parameters folder
of the Parameters tab. If the imported user profile or mobility does not match, Atoll will
display a warning.
12. Under Clutter distribution, enter a weight for each class that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk Sk
N k = N Area -------------------------Wi Si
where:
Nk
N Area =
Number of users in the clutter k

Number of users in the zone Area
Wk
Weight of clutter k
Sk
Surface area of clutter k (in square km)
13. If you want you can specify a percentage of indoor subscribers for each clutter class. During a Monte-Carlo simulation,
an additional loss will be added to the indoor users path loss.
14. Click OK to finish importing the traffic map.
303

6.3.2.2.2
Forsk 2011
Importing a User Profile Environment Based Traffic Map

Environment classes describe the distribution of user profiles.
To create a user profile environment based traffic map:
5. Select User profile environments from the list.
Traffic Map dialogue. For information, see "Creating a User Profile Environment Based
Traffic Map" on page 304.
7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, JPEG 2000, BIL,
IST, BMP, PlaNET, GRC Vertical Mapper, and Erdas Imagine.
11. Select the Description tab.
In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the Code
column.
12. For each Code, select the environment it corresponds to from the Name column.
The environments available are those available in the Environments folder, under Traffic Parameters on the Parameters tab of the Explorer window. For more information, see "Modelling Environments" on page 301.
13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects" on
page 23.
6.3.2.2.3
Creating a User Profile Environment Based Traffic Map

Atoll enables you to create a user profile environment traffic map based on by drawing it in the map window.
To draw a traffic map:
5. Select User profile environments from the list.
6. Click Create. The Environment Map Editor toolbar appears (see Figure 6.36).
Draw Map
Delete
Figure 6.36: Environment Map Editor toolbar

7. Select the environment class from the list of available environment classes.
8. Click the Draw Polygon button (
9. Click the Delete Polygon button (
) to draw the polygon on the map for the selected environment class.
) and click the polygon to delete the environment class polygon on the map.
10. Click the Close button to close the Environment Map Editor toolbar and end editing.
304

AT310_UMU_E0
6.3.2.2.4
Displaying Statistics on a User Profile Environment Traffic Map

You can display the statistics of a user profile environment traffic map. Atoll provides absolute (surface) and relative (percentage of the surface) statistics on the focus zone for each environment class. If you do not have a focus zone defined, statistics
are determined for the computation zone.
To display traffic statistics of a user profile environment traffic map:
3. Right-click the user profile environment traffic map whose statistics you want to display. The context menu appears.
4. Select Statistics from the context menu. The Statistics window appears.
The Statistics window lists the surface (Si in km) and the percentage of surface (% of i) for each environment class "i"
S
i
- 100
within the focus zone. The percentage of surface is given by: % of i = -------------
Sk
k
You can print the statistics by clicking the Print button.

5. Click Close.
If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per clutter
class.
6.3.2.3 Creating User Density Traffic Maps (No. Users/km2)

User density traffic maps can be based on population statistics (user densities can be calculated from the density of inhabitants) or on 2G traffic statistics. User density traffic maps provide the number of connected users per unit of surface, i.e., the
density of users, as input. This can be either the density of users per activity status or the density of users including all activity
statuses.
In this section, the following ways of creating a user density traffic map are explained:
"Importing a User Density Traffic Map" on page 305

"Creating a User Density Traffic Map" on page 306.
User density traffic maps can be created from sector traffic maps in order to extract and display the exact number of users
per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. for
more information, see "Creating User Density Traffic Maps from Sector Traffic Maps" on page 307.
6.3.2.3.1
Importing a User Density Traffic Map

The user density traffic map defines the density of users per pixel. For a traffic density of X users per km, Atoll will distribute
x users per pixel during the simulations, where x depends on the size of the pixels. These x users will have a terminal, a mobility
type, a service, and percentage of indoor users as defined on the Traffic tab of the traffic maps properties dialogue.
You can create a number of user density traffic maps for different combinations of terminals, mobility types, and services. You
can add vector layers to the map and draw regions with different traffic densities.
To create a user density traffic map:
4. Select User density traffic map (no. users/km2).
5. Select the type of traffic information you input:
-
All activity statuses: Select All activity statuses if the map you are importing provides a density of users with any
activity status.
Active in uplink: Select Active in uplink if the map you are importing provides a density of users active in the uplink
only.
Active in downlink: Select Active in downlink if the map you are importing provides a density of users active in
the downlink only.
Active in uplink and downlink: Select Active in uplink and downlink if the map you are importing provides a density of users with both uplink and downlink activity.
Inactive: Select Inactive if the map you are importing provides a density of inactive users.
305

Forsk 2011
Traffic Map dialogue. For information, see "Creating a User Density Traffic Map" on
page 306.
7. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP,
PlaNET, TIF, JPEG 2000, ISTAR, and Erdas Imagine.
100.
100.
14. Under Services (%), enter the percentage of each service type used in the map. The total percentages must equal 100.
15. Under Clutter distribution, enter the percentage of indoor users for each clutter class.
An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define a
clutter weighting for user density traffic maps because the traffic is provided in terms of user density per pixel.
6.3.2.3.2
Creating a User Density Traffic Map

Atollenables you to create a user density traffic map by drawing it in the map window.
To draw a user density traffic map:
4. Select User Density Traffic Map (Number of users per km2).
5. Select the type of traffic information you input:
-
All Activity Statuses: Select All Activity Statuses if the map you are drawing provides a density of users with any
activity status.
Active in Uplink: Select Active in Uplink if the map you are drawing provides a density of users active in the uplink
only.
Active in Downlink: Select Active in Downlink if the map you are drawing provides a density of users active in the
downlink only.
Active in Uplink and Downlink: Select Active in Uplink and Downlink if the map you are drawing provides a density of users with both uplink and downlink activity.
Inactive: Select Inactive if the map you are drawing provides a density of inactive users.
6. Click the Create button. The traffic maps properties dialogue appears.
100.
100.
10. Under Services (%), enter the percentage of each service type used in the map. The total percentages must equal 100.
11. Under Clutter distribution, enter the percentage of indoor users for each clutter class.
An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define a
clutter weighting for user density traffic maps because the traffic is provided in terms of user density per pixel.
13. Right-click the traffic map. The context menu appears.
14. Select Edit from the context menu.
15. Use the tools available in the Vector Editor toolbar to draw contours. For more information on editing contours, see
"Editing Polygons, Lines, and Points" on page 39.
306

AT310_UMU_E0
Atoll creates an item called Density values in the User Density Map folder.
16. Right-click the Density values item in the User Density Map folder. The context menu appears.
18. In the table, enter a traffic density value (i.e., the number of users per km2) for each contour you have drawn.
19. Right-click the item. The context menu appears.
20. Select Edit from the context menu to end editing.
6.3.2.3.3
Creating User Density Traffic Maps from Sector Traffic Maps

You can create user density traffic maps from sector traffic maps. User density traffic maps created from sector traffic maps
display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting
defined for the sector traffic maps.
To create user density traffic maps from a sector traffic map:
3. Right-click the sector traffic map from which you want to create user density traffic maps. The context menu appears.
4. Select Create density maps from the context menu.
Atoll creates as many user density traffic maps as the number of services present in the sector traffic map. The user
density map files use the resolution of the coverage prediction used for the sector traffic map and are embedded in
the document.
6.3.2.4 Converting 2G Network Traffic

Atollcan cumulate the traffic of the traffic maps that you select and export it to a file. The information exported is the number
of users per km for a particular service of a particular type, i.e., data or voice. This allows you to export your 2G network
packet and circuit service traffic, and then import these maps as user density traffic maps into your UMTS document. These
maps can then be used in traffic simulations like any other type of map.
For more information on how to export cumulated traffic, see "Exporting Cumulated Traffic" on page 307, and for information
on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 305.
To import a 2G traffic map into a UMTS document:
1. Create a sector traffic map in your 2G document for each type of service, i.e., one map for packet-switched and one
for circuit-switched services. For more information on creating sector traffic maps, see "Creating a Sector Traffic Map"
on page 369.
2. Export the cumulated traffic of the maps created in step 1. For information on exporting cumulated traffic, see
"Exporting Cumulated Traffic" on page 307.
3. Import the traffic exported in step 2 in your UMTS document as a user density traffic map. For more information on
importing user density traffic maps, see "Importing a User Density Traffic Map" on page 305.
6.3.2.5 Exporting Cumulated Traffic

Atollallows you to export the cumulated traffic of selected traffic maps in the form of user density traffic maps. During export,
Atoll converts any traffic map to user densities. The cumulated traffic is exported in 32-bit BIL, ArcView Grid, or Vertical
Mapper format. When exporting in BIL format, Atoll allows you to export files larger than 2 GB. The exported traffic map can
then be imported as a user density traffic map.
To export the cumulated traffic:
3. Select Export Cumulated Traffic from the context menu. The Save As dialogue appears.
4. Enter a file name and select the file format.
5. Click Save. The Export dialogue appears.
6. Under Region, select the area to export:
-
The Entire Project Area: This option allows you to export the cumulated traffic over the entire project.
The Computation Zone: This option allows you to export the cumulated traffic contained by a rectangle encompassing the computation zone, whether or not the computation zone is visible.
7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1.
307

Forsk 2011
You must enter a resolution before exporting. If you do not enter a resolution, it remains
at "0" and no data will be exported.
8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic
data to be exported.
-
Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal.
Service: Select the service that will be exported, select "All circuit services" to export traffic using any circuit
service, "All packet services" to export traffic using any packet service, or select the specific type of service: HSDPA,
HSUPA, mobile internet access, multimedia messaging service, video conferencing, or voice.
Mobility: Select the mobility type that will be exported or select "All" to export all mobility types.
Activity: Select one of the following:
-
All Activity Statuses: Select All Activity Statuses to export all users without any filter by activity status.
Uplink: Select Uplink to export mobiles active in the uplink only.
Downlink: Select Downlink to export mobiles active in the downlink only.
Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity.
Inactive: Select Inactive to export only inactive mobiles.
9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the cumulated
traffic.
10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.
6.3.3 Exporting a Traffic Map

To export a traffic map:
3. Right-click the traffic map you want to export. The context menu appears.
5. Enter a file name and select a file format for the traffic map.
6. Click Save.
If you are exporting a raster traffic map, you have to define:
-
The Export Region:

-
Entire Project Area: Saves the entire traffic map.

Only Pending Changes: Saves only the modifications made to the map.
Computation Zone: Saves only the part of the traffic map inside the computation zone.
An export Resolution.
6.3.4 Calculating and Displaying Traffic Simulations

Once you have modelled the network services and users and have created traffic maps, you can create simulations. The simulation process consists of two steps:
1. Obtaining a realistic user distribution: Atoll generates a user distribution using a Monte-Carlo algorithm; this user
distribution is based on the traffic database and traffic maps and is weighted by a Poisson distribution between simulations of the same group.
Each user is assigned a service, a mobility type, and an activity status by random trial, according to a probability law
that uses the traffic database.
The user activity status is an important output of the random trial and has direct consequences on the next step of
the simulation and on the network interferences. A user may be either active or inactive. Both active and inactive
users consume radio resources and create interference.
Then, Atoll randomly assigns a shadowing error to each user using the probability distribution that describes the shadowing effect.
Finally, another random trial determines user positions in their respective traffic zone (possibly according to the clutter weighting and the indoor ratio per clutter class).
2. Modelling network power control: Atoll uses a power control algorithm for R99 users, and an algorithm mixing
A-DPCH power control and fast link adaptation for HSDPA users and an additional loop modelling noise rise scheduling
308

AT310_UMU_E0
for HSUPA users. The power control simulation algorithm is described in "The Power Control Simulation Algorithm"
on page 309.
6.3.4.1 The Power Control Simulation Algorithm

The power control algorithm (see Figure 6.37) simulates the way a UMTS network regulates itself by using uplink and downlink
power controls in order to minimize interference and maximize capacity. HSDPA users (i.e., Packet (HSDPA), Packet (HSPA),
and Packet (HSPA - Constant Bit Rate) service users) are linked to the A-DPCH radio bearer (an R99 radio bearer). Therefore,
the network uses an A-DPCH power control on UL and DL and then performs fast link adaptation on DL in order to select an
HSDPA radio bearer. For HSUPA users (i.e., Packet (HSPA) and Packet (HSPA - Constant Bit Rate) service users), the network
first uses an E-DPCCH/A-DPCH power control on UL and DL, checks that there is an HSDPA connection on downlink and then
carries out noise rise scheduling in order to select an HSUPA radio bearer on uplink. Atoll simulates these network regulation
mechanisms for each user distribution. During each iteration of the algorithm, all the mobiles (i.e., Circuit (R99), Packet (R99),
Packet (HSDPA), Packet (HSPA), and Packet (HSPA - Constant Bit Rate) service users) selected during the user distribution
generation attempt to connect one by one to network transmitters. The process is repeated until the network is balanced,
i.e., until the convergence criteria (on UL and DL) are satisfied.
Initialisation
R99 part
Mi Best Server Determination
Mi Active Set Determination
For HSDPA users, this part of

the algorithm is performed for
the A-DPCH bearer (R99 bearer)
For HSUPA users, this part is
performed for the E-DPCCH/ADPCH bearer (R99 bearer)
For each R99, HSDPA

and HSUPA mobile, Mi
UL Power Control
DL Power Control
UL and DL Interference Update
Congestion and Radio Resource Control
HSDPA part
For each HSDPA and
HSUPA mobile, Mi
Fast Link Adaptation
Mobile Scheduling
Radio Resource Control
HSUPA part
Admission Control
For each HSUPA
mobile, Mi
Noise Rise Scheduling
Radio Resource Control
Convergence Study
Figure 6.37: Schematic view of simulation algorithm

As shown in Figure 6.37, the simulation algorithm is divided in three parts. All users are evaluated by the R99 part of the algorithm. HSDPA and HSUPA bearer users, unless they have been rejected during the R99 part of the algorithm, are then evaluated by the HSDPA part of the algorithm. Finally, HSUPA bearer users, unless they have been rejected during the R99 or HSDPA
parts of the algorithm, are then evaluated by the HSUPA part of the algorithm.
Description of the R99 Portion of the Simulation
The R99 part of the algorithm simulates power control, congestion and radio resource control performed for R99 bearers for
all users. Atoll considers each user in the order established during the generation of the user distribution and determines his
best server and his active set. Atoll first calculates the required terminal power in order to reach the Eb Nt threshold
requested by the R99 bearer on UL, followed by the required trac channel power in order to reach the Eb Nt threshold
requested by the R99 bearer on DL. After calculating power control, Atoll updates the cell load parameters. Atoll then carries
out congestion and radio resource control, verifying the cell UL load, the total power transmitted by the cell, the number of
channel elements, the Iub throughput and OVSF codes consumed by the cell.
In dual-cell HSDPA, A-DPCH is only transmitted on one of the two carriers (called the anchor carrier). Therefore, dual-cell
HSDPA users consume the same amount of R99 resources as single-cell HSDPA users. The R99 bearer is allocated to dual-cell
HSDPA users on their best serving cell.
At this point, users can be either connected or rejected. They are rejected if:
The signal quality is not sufficient:
309

Forsk 2011
On the downlink, the pilot quality is not high enough (no cell in the user ac ve set): the status is "Ec I0 <
(Ec I0)min"
On the downlink, the power required to reach the user is greater than the maximum allowed: the status is "Ptch >
PtchMax"
On the uplink, there is not enough power to transmit: the status is "Pmob > PmobMax"
Even if constraints above are respected, the network may be saturated:

-
The maximum uplink load factor is exceeded (at admission or congestion): the status is either "Admission Rejection" or "UL Load Saturation"
There are not enough channel elements on site: the status is "Ch. Elts Saturation"
The maximum Iub backhaul throughput on site is exceeded: the status is "Iub Throughput Saturation"
There is not enough power for cells: the status is "DL Load Saturation"
There are no more OVSF codes available: the status is "OVSF Code Saturation"
Description of the HSDPA Portion of the Simulation

In the HSDPA part, Atoll processes all HSDPA bearer users, i.e., Packet (HSDPA), Packet (HSPA), and Packet (HSPA - Constant
Bit Rate) service users. The HSDPA part of the algorithm simulates fast link adaptation, the scheduling of HSDPA bearer users,
and radio resource control on downlink.
For dual-cell HSDPA users, fast link adaptation is done once for each carrier. For a dual-cell HSDPA user, the first carrier is the
one selected in the R99 part according to the carrier selection method chosen in the site equipment, and the second carrier
is the one that provides the best CQI. Therefore, dual-cell HSDPA users have two HSDPA bearers (possibly different ones
depending on the available HSDPA power in each cell), and consume HSDPA resources in both cells. Their throughputs are the
sum of the throughputs provided by the two HSDPA bearers.
HSDPA bearer selection is based on look-up tables, available by double-clicking the corresponding entry in the Reception
Equipment table, found in the Terminals context menu. HSDPA bearer selection depends on reported CQI, UE and cell capabilities as detailed in the following diagramme.
[
Figure 6.38: HSDPA bearer selection
The HSDPA and HS-SCCH powers of a cell are evaluated before calcula ng HS-PDSCH Ec Nt. The available HSDPA power (the
power dedicated to HS-SCCH and HS-PDSCH of HSDPA bearer users) of a cell can be either fixed (statically allocated) or dynamically allocated. If it is dynamically allocated, the power allocated to HSDPA depends on how much power is required to serve
R99 traffic. In other words, the power available after all common channels (including the power for downlink HSUPA channels)
and all R99 traffic have been served is allocated to HS-PDSCH and HS-SCCH of HSDPA bearer users. Similarly, the power per
HS-SCCH can be either fixed or dynamically allocated in order to a ain the HS-SCCH Ec Nt threshold. Using the HS-SCCH and
HSDPA powers, Atoll evaluates the HS-PDSCH power (the difference between the available HSDPA power and the HS-SCCH
power), calculates the HS-PDSCH Ec Nt and, from that, the corresponding CQI (from the graph CQI=f(HS-PDSCH Ec Nt) defined
for the terminal reception equipment and the user mobility). Then, Atoll reads the best HSDPA bearer associated to this CQI
(i.e., it reads the Best Bearer=f(HS-PDSCH CQI) from the table defined for the terminal reception equipment and the user
mobility) and checks if it is compatible with the user equipment and cell capabilities. If compatible, Atoll selects the HSDPA
bearer. Otherwise, it downgrades the HSDPA bearer to a lower one until the selected HSDPA bearer is compatible with the
user equipment and cell capabilities. The selected HSDPA bearer is the best HSDPA bearer that the user can obtain. Two CQI
values are calculated for dual-cell HSDPA users, one for each carrier, and two HSDPA bearers are determined.
For Packet (HSPA - Constant Bit Rate) service users, HS-SCCH-less operation (i.e., HS-DSCH transmissions without any accompanying HS-SCCH) is performed. In this case, the UE is not informed about the transmission format and has to revert to blind
decoding of the transport format used on the HS-DSCH. Complexity of blind detections in the UE is decreased by limiting the
transmission formats that can be used (i.e., the HSDPA bearers available). Therefore, only HSDPA bearers using QPSK modulation and a maximum of two HS-PDSCH channels can be selected and allocated to the user. Additionally, the selected HSDPA
bearer must provide a RLC peak rate higher than the guaranteed bit rate defined for the service.
Packet (HSPA - Constant Bit Rate) service users have the highest priority and are processed first, in the order established
during the generation of the user distribution. The schedulermanages the maximum number of users within each cell and
shares the cells available HSDPA power between the users. Atoll determines the HSDPA bearer for each user. The selected
HSDPA bearer must provide a RLC peak rate higher than the guaranteed bit rate defined for the service. To achieve the highest
cell capacity, the scheduler can hold several packets over a TTI (Transmission Time Interval). Atollmodels this "intelligent
scheduling" by allowing several Packet (HSPA - Constant Bit Rate) service users to share the same HSDPA bearer. Then, Atoll
calculates the HSDPA bearer consumption for each user and takes into account this parameter when it determines the
resources consumed by the user (i.e., the HSDPA power used, the number of OVSF codes, and the Iub backhaul throughput).
Atoll checks if enough codes and Iub backhaul throughput are available for the user (taking into account the maximum
number of OVSF codes defined for the cell and the maximum Iub backhaul throughput allowed on the site in the downlink).
If not, Atoll allocates a lower HSDPA bearer ("downgrading") which needs fewer OVSF codes and consumes lower Iub backhaul
310

AT310_UMU_E0
throughput. If no OVSF codes are available, the user is rejected. At the same time, if the maximum Iub backhaul throughput
allowed on the site in the downlink is still exceeded, the user is rejected.
At this point, Packet (HSPA - Constant Bit Rate) service users can be connected or rejected. They are rejected if:
The maximum number of HSDPA users per cell is exceeded: the status is "HSDPA Scheduler Saturation"
The lowest HSDPA bearer they can obtain does not provide a RLC peak rate higher than the guaranteed bit rate: the
status is "HSDPA Resource Saturation"
The HS-SCCH signal quality is not sufficient: the status is "HSDPA Resource Saturation"
There are no more OVSF codes available: the status is "HSDPA Resource Saturation"
The maximum Iub backhaul throughput allowed on the site in the downlink is exceeded: the status is "HSDPA Resource
Saturation"
After processing the Packet (HSPA - Constant Bit Rate) service users, Atoll processes the remaining HSDPA bearer users (i.e.,
Packet (HSDPA) and Packet (HSPA) service users) without exceeding the maximum number of users within each cell.
The scheduler ranks the users according to the selected scheduling technique:
Max C/I: "n" users (where "n" corresponds to the maximum number of HSDPA users defined for the cell minus the
number of Packet (HSPA - Constant Bit Rate) service users in the cell) are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order by the channel quality indicator (CQI).
Round Robin: Users are scheduled in the same order as in the simulation (i.e., in random order).
Proportional Fair: "n" users (where "n" corresponds to the maximum number of HSDPA users defined for the cell
minus the number of Packet (HSPA - Constant Bit Rate) service users in the cell) are scheduled in the same order as
in the simulation (i.e., in random order). Then, they are sorted in descending order according to a random parameter
which corresponds to a combination of the user rank in the simulation and the channel quality indicator (CQI).
Then, users are processed in the order defined by the scheduler and the remaining cells HSDPA power (i.e., the HSDPA power
available after all Packet (HSPA - Constant Bit Rate) service users have been served) is shared between them. Atoll checks to
see if enough codes and Iub backhaul throughput are available for the HSDPA bearer assigned to the user (taking into account
the maximum number of OVSF codes defined for the cell and the maximum Iub backhaul throughput allowed on the site in
the downlink). If not, Atoll allocates a lower HSDPA bearer ("downgrading") which needs fewer OVSF codes and consumes
lower Iub backhaul throughput. If no OVSF codes are available, the user is delayed. At the same time, if the maximum Iub backhaul throughput allowed on the site in the downlink is still exceeded even by using the lowest HSDPA bearer, the user is
delayed.
At this point, packet (HSDPA) and packet (HSPA) service users can be connected, rejected, or delayed. They are rejected if the
maximum number of HSDPA users per cell is exceeded (status is "HSDPA Scheduler Saturation") and delayed if:
They cannot obtain the lower HSDPA bearer: the status is "No Compatible Bearer"
The HS-SCCH signal quality is not sufficient: the status is "HSDPA Power Saturation"
There are no more HS-SCCH channels available: the status is "HS-SCCH Channels Saturation"
There are no more OVSF codes available: the status is "OVSF Code Saturation"
The maximum Iub backhaul throughput allowed on the site in the downlink is exceeded: the status is "Iub Throughput
Saturation"
Description of the HSUPA Portion of the Simulation

In the HSUPA part, Atoll processes Packet (HSPA) service users and Packet (HSPA - Constant Bit Rate) service users who are
connected to an HSDPA bearer or were delayed in the previous step. It manages the maximum number of users within each
cell. Packet (HSPA - Constant Bit Rate) service users have the highest priority and are processed first, in the order established
during the generation of the user distribution. Then, Atoll considers Packet (HSPA) service users in the order established
during the generation of the user distribution. The HSUPA part of the algorithm simulates an admission control on the HSUPA
bearer users followed by noise rise scheduling and radio resource control.
Atoll first selects a list of HSUPA bearers that are compatible with the user equipment capabilities for each HSUPA bearer user.
For Packet (HSPA - Constant Bit Rate) service users, the list is restricted to HSUPA bearers that provide a RLC peak rate higher
than the guaranteed bit rate. Then, during admission control, Atoll checks that the lowest compatible bearer in terms of the
required E-DPDCH Ec Nt does not require a terminal power higher than the maximum terminal power allowed.
Then, Atoll performs the noise rise scheduling on Packet (HSPA - Constant Bit Rate) service users, followed by a radio resource
control. The noise rise scheduling algorithm attempts to evenly share the remaining cell load between the users admitted in
admission control; in terms of HSUPA, each user is allocated a right to produce interference. The remaining cell load factor on
uplink depends on the maximum load factor allowed on uplink and how much uplink load is produced by the served R99 traffic. From this value, Atoll calculates the maximum E-DPDCH Ec Nt allowed and can select an HSUPA bearer. The HSUPA bearer
is selected based on the values in a look-up table, and depends on the maximum E-DPDCH Ec Nt allowed and on UE capabilities.
311

Forsk 2011
You can open the HSUPA Bearer Selection table by clicking the Expand button ( ) to
expand the UMTS Network Settings folder on the Parameters tab of the Explorer window,
and then right-clicking the Reception Equipment folder and selecting Open Table from the
context menu.
Atoll selects the best HSUPA bearer from the HSUPA compatible bearers, in other words, the HSUPA bearer with the highest
poten al throughput where the required E-DPDCH Ec/Nt is lower than the maximum E-DPDCH Ec Nt allowed and the required
terminal power is lower than the maximum terminal power. In this section, the potential throughput refers to the ratio
between the RLC peak rate and the number of retransmissions. When several HSUPA bearers are available, Atoll selects the
one with the lowest required E-DPDCH Ec Nt.
Several Packet (HSPA - Constant Bit Rate) service users can share the same HSUPA bearer. Atoll calculates the HSUPA bearer
consumption for each user and takes into account this parameter when it determines the resources consumed by each user
(i.e., the terminal power used, the number of channel elements and the Iub backhaul throughput).
Finally, Atoll carries out radio resource control on Packet (HSPA - Constant Bit Rate) service users. Atoll checks to see if
enough channel elements and Iub backhaul throughput are available for the HSUPA bearer assigned to the user (taking into
account the maximum number of channel elements defined for the site and the maximum Iub backhaul throughput allowed
on the site in the uplink). If not, Atoll allocates a lower HSUPA bearer ("downgrading") which needs fewer channel elements
and consumes lower Iub backhaul throughput. If no channel elements are available, the user is rejected. On the same hand,
if the maximum Iub backhaul throughput allowed on the site in the uplink is still exceeded even by using the lowest HSUPA
bearer, the user is rejected.
At this point, Packet (HSPA - Constant Bit Rate) service users can be either connected, or rejected. They are rejected if:
The maximum number of HSUPA users per cell is exceeded: the status is "HSUPA Scheduler Saturation".
The terminal power required to obtain the lowest compatible HSUPA bearer exceeds the maximum terminal power
in the admission control: the status is "Pmob > PmobMax".
The lowest compatible HSUPA bearer they can obtain does not provide a RLC peak rate higher than the guaranted bit
rate: the status is "HSUPA Admission Rejection".
There are no more channel elements available: the status is "Ch. Elts Saturation"
The maximum Iub backhaul throughput allowed on the site in the uplink is exceeded: the status is "Iub Throughput
Saturation".
Then, Atoll processes Packet (HSPA) service users. It performs a new noise rise scheduling and distributes the remaining cell
load factor available after all Packet (HSPA - Constant Bit Rate) service users have been served. From this value, Atoll selects
an HSUPA bearer for each Packet (HSPA) service user. Then, Atoll checks that each Packet (HSPA) service user has obtained
the average requested rate (defined in the properties of the service).
Finally, Atoll carries out radio resource control, verifying whether enough channel elements and Iub backhaul throughput are
available for the HSUPA bearer assigned to the user (taking into account the maximum number of channel elements defined
for the site and the maximum Iub backhaul throughput allowed on the site in the uplink). If not, Atoll allocates a lower HSUPA
bearer ("downgrading") which needs fewer channel elements and consumes lower Iub backhaul throughput. If no channel
elements are available, the user is rejected. On the same hand, if the maximum Iub backhaul throughput allowed on the site
in the uplink is still exceeded even by using the lowest HSDPA bearer, the user is rejected.
At this point, Packet (HSPA) service users can be either connected, or rejected. They are rejected if:
The maximum number of HSUPA users per cell is exceeded: the status is "HSUPA Scheduler Saturation".
The terminal power required to obtain the lowest compatible HSUPA bearer exceeds the maximum terminal power
in the admission control: the status is "Pmob > PmobMax".
There are no more channel elements available: the status is "Ch. Elts Saturation"
The maximum Iub backhaul throughput allowed on the site in the uplink is exceeded: the status is "Iub Throughput
Saturation".
Bearer Downgrading
If you select the option "Bearer Downgrading," when creating a simulation, R99, HSDPA and HSUPA service users can be downgraded under certain circumstances. When the downgrading is allowed, Atoll does not reject R99, HSDPA and HSUPA users
directly; it downgrades them first.
The R99 to R99 bearer downgrading occurs when:
The cell resources are insufficient when the user is admitted

-
The cell resources are insufficient during congestion control

-
312
The maximum uplink load factor is exceeded

The maximum uplink load factor is exceeded
There is not enough power for cells
There are not enough channel elements on the site
The maximum Iub backhaul throughput on the site is exceeded

AT310_UMU_E0
There are no more OVSF codes available
The user maximum connection power is exceeded during power control:

-
On the downlink, the maximum traffic channel power is exceeded

On the uplink, the maximum terminal power is exceeded
For all these reasons, the users R99 bearer will be downgraded to another R99 bearer of the same type (same traffic class).
Upon admission and during power control, downgrading is only performed on the user who causes the problem. During
congestion control, the problem is at the cell level and therefore, downgrading is performed on several users according to
their service priority. Users with the lowest priority services will be the first to be downgraded.
If R99 bearer downgrading does not fix the problem, the user will be rejected.
For an HSDPA bearer user, downgrading is triggered upon admission (into the R99 portion) when the best serving cell does
not support HSDPA traffic. When this happens, the HSDPA bearer user will not be able to get an HSDPA bearer and will be
downgraded to an R99 bearer of the same type as the A-DPCH bearer and the user will be processed as an R99 user.
For an HSUPA bearer user, downgrading is triggered upon admission (into the R99 portion) when the best serving cell does
not support HSUPA traffic. When this happens, the HSUPA bearer user will not be able to get an HSUPA bearer and will be
downgraded to an R99 bearer of the same type as the E-DPCCH/A-DPCH bearer and the user will be processed as an R99 user.
6.3.4.2 Creating Simulations

In Atoll, simulations enable you to model UMTS HSPA network regulation mechanisms in order to minimise interference and
maximise capacity.
You can create one simulation or a group of simulations that will be performed in sequence.
To create a simulation or a group of simulations:
2. Right-click the Simulations folder. The context menu appears.
3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears.
4. On the General tab of the dialogue, enter a Name and Comments for this simulation or group of simulations.
5. Under Execution on the General tab, you can set the following parameters:
-
Number of simulations: Enter the number of simulations to be carried out. All simulations created at the same
time are grouped together in a folder on the Network tab of the Explorer window.
Information to retain: You can select the level of detail that will be available in the output:
-
Only the Average Simulation and Statistics: None of the individual simulations are displayed or available in
the group. Only an average of all simulations and statistics is available.
Some calculation and display options available for coverage predictions are not available
when the option "Only the Average Simulation and Statistics" is selected.
No Information About Mobiles: All the simulations are listed and can be displayed. For each of them, a properties window containing simulation output, divided among four tabs Statistics, Sites, Cells, and Initial
Conditions is available.
Standard Information About Mobiles: All the simulations are listed and can be displayed. The properties
window for each simulation contains an additional tab with output related to mobiles.
Detailed Information About Mobiles: All the simulations are listed and can be displayed. The properties
window for each simulation contains additional mobile-related output on the Mobiles and Mobiles (Shadowing Values) tabs.
When you are working on very large radio-planning projects, you can reduce memory
consumption by selecting Only the Average Simulation and Statistics under Information
to retain.
6. Under Load constraints on the General tab, you can set the constraints that Atoll must respect during the simulation:
-
Number of CEs: Select the Number of CEs check box if you want Atoll to respect the number of channel elements
defined for each site.
Iub throughputs: Select the Iub throughputs check box if you want Atoll to respect the maximum Iub backhaul
throughputs defined for each site.
Number of codes: Select the Number of codes check box if you want Atoll to respect the number of OVSF codes
available each cell.
313

Forsk 2011
UL load factor: If you want the UL load factor to be considered in the simulation, select the UL load factor check
box.
Max UL load factor: If you want to enter a global value for the maximum uplink cell load factor, click the button
(
) beside the box and select Global value. Then, enter a maximum uplink cell load factor. If you want to use the
maximum uplink cell load factor as defined in the properties for each cell, click the button ( ) beside the box and
select Defined per cell.
DL load (% Pmax): If you want the DL load to be considered in the simulation, select the DL load (% Pmax) check
box and enter a maximum downlink cell load in the Max DL load box.
Max DL load (% Pmax): If you want to enter a global value for the maximum downlink cell load, as a percentage
of the maximum power, click the button ( ) beside the box and select Global value. Then, enter a maximum
downlink cell load, as a percentage of the maximum power. If you want to use the maximum downlink cell load
factor as defined in the properties for each cell, click the button (
) beside the box and select Defined per cell.
7. Under Bearer negotiation on the General tab, check the Bearer downgrading check box if you want to permit bearer
downgrading during the simulation. When a constraint is not respected, user radio bearers with services supporting
bearer downgrading are downgraded. If the constraint is still not satisfied after downgrading, users are rejected. If
downgrading is not selected, users will be rejected immediately, starting with users with the lowest service priority, if
a constraint can not be respected.
8. On the Traffic tab, enter the following:
-
Global scaling factor: If desired, enter a scaling factor to increase user density.
The global scaling factor enables you to increase user density without changing traffic parameters or traffic maps.
For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for
environment and user profile traffic maps) or the rates/users (for sector traffic maps).
Select traffic maps to be used: Select the traffic maps you want to use for the simulation.
You can select traffic maps of any type. However, if you have several different types of traffic maps and want to
make a simulation on a specific type of traffic map, you must ensure that you select only traffic maps of the same
type. For information on the types of traffic maps, see "Creating a Traffic Map" on page 298.
9. Click the Advanced tab.

10. Under Generator initialisation, enter an integer as the generator initialisation value. If you enter "0", the default, the
user and shadowing error distribution will be random. If you enter any other integer, the same user and shadowing
error distribution will be used for any simulation using the same generator initialisation value.
Using the same generated user and shadowing error distribution for several simulations
can be useful when you want to compare the results of several simulations where only
one parameter changes.
11. Under Convergence, enter the following parameters:
-
Max number of iterations: Enter the maximum number of iterations that Atoll should run to make convergence.
UL convergence threshold: Enter the relative difference in terms of interference and connected users on the
uplink that must be reached between two iterations.
DL convergence threshold: Enter the relative difference in terms of interference and connected users on the
downlink that must be reached between two iterations.
12. Once you have defined the simulation, you can calculate it immediately or you can save it to calculate it later:
-
Calculate: Click Calculate to save the defined simulation and calculate it immediately.
OK: Click OK to save the defined simulation without calculating it. You can calculate it later clicking the Calculate
button (
All simulations created at the same time are grouped together in a folder on the Network tab of the Explorer window. You
can now use the completed simulations for specific UMTS and HSDPA coverage predictions (see "Making Coverage Predictions
Using Simulation Results" on page 329) or for an AS analysis using the Point Analysis window (see "Making an AS Analysis of
Simulation Results" on page 329).
6.3.4.3 Displaying the Traffic Distribution on the Map

Atoll enables you to display on the map the distribution of the traffic generated by all simulations according to different
parameters. You can, for example, display the traffic according to service, activity status, pilot signal strength, or soft handover
gain.
You can set the display of the traffic distribution according to discrete values and the select the value to be displayed. Or, you
can select the display of the traffic distribution according to value intervals, and then select the parameter and the value intervals that are to be displayed. You can also define the colours of the icon and the icon itself.
314

AT310_UMU_E0
For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 23.
In this section are the following examples of traffic distribution:
"Displaying the Traffic Distribution by Handover Status" on page 315

"Displaying the Traffic Distribution by Connection Status" on page 315
"Displaying the Traffic Distribution by Service" on page 316.
You can make the traffic distribution easier to see by hiding geo data and predictions.
For information, see "Displaying or Hiding Objects on the Map Using the Explorer" on
page 18.
6.3.4.3.1
Displaying the Traffic Distribution by Handover Status

In this example, the traffic distribution is displayed by the handover status.
To display the traffic distribution by the handover status:
3. Select Properties from the context menu. The Simulations Properties dialogue appears.
4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "HO Status (Sites/No. Transmitters
Act. Set)" as the Field.
5. Click OK. The traffic distribution is now displayed by handover status (see Figure 6.39).
Figure 6.39: Displaying the traffic distribution by handover status
6.3.4.3.2
Displaying the Traffic Distribution by Connection Status

In this example, the traffic distribution is displayed by the connection status.
To display the traffic distribution by the connection status:
4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "Connection Status" as the Field.
5. Click OK. The traffic distribution is now displayed by connection status (see Figure 6.40).
315

Forsk 2011
Figure 6.40: Displaying the traffic distribution by connection status
6.3.4.3.3
Displaying the Traffic Distribution by Service

In this example, the traffic distribution is displayed by service.
To display the traffic distribution by service:
4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "Service" as the Field.
5. Click OK. The traffic distribution is now displayed by service (see Figure 6.41).
Figure 6.41: Displaying the traffic distribution by service
6.3.4.4 Displaying the User Active Set on the Map

Atoll enables you to display on the map the active set for each user generated by a simulation.
To display the active set for a user:
On the map, click and hold the icon of the user whose best and second-best servers you want to display.
The servers in the users active set are connected to the user with lines the same colour as the serving transmitter.
The best server is indicated with the number "1", the second-best with number "2" and so on. Figure 6.42 shows a
user with three servers in his active set.
316

AT310_UMU_E0
Figure 6.42: The active set of a user
6.3.4.5 Displaying the Results of a Single Simulation

After you have created a simulation, as explained in "Creating Simulations" on page 313, you can display the results.
To access the results of a single simulation:
) to expand the Simulations folder.

want to access.
) to expand the folder of the simulation group containing the simulation whose results you
4. Right-click the simulation. The context menu appears.

5. Select Properties from the context menu. The simulation properties dialogue appears.
One tab gives statistics of the results of the simulation. Other tabs in the simulation properties dialogue contain simulation results as identified by the tab title. A final tab lists the initial conditions of the simulation. The amount of detail
available when you display the results depends on the level of detail you selected from the Information to retain list
on the General tab of the properties dialogue for the group of simulations. For more information on the different
options, see step 5. of "Creating Simulations" on page 313.
The Statistics tab: The Statistics tab contains the following two sections:
-
Demand: Under Demand, you will find data on the connection requests:
-
Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; power control has not yet finished. The result depends on the traffic description and traffic input.
During the first random trial, each user is assigned a service and an activity status. The number of users per
activity status and the UL and DL rates that all active users could theoretically generate are provided.
The breakdown per service (total number of users, number of users per activity status, and UL and DL rates)
is given.
Results: Under Results, you will find data on connection results:

-
The number of iterations that were run in order to converge.

The number and the percentage of rejected users is given along with the reason for rejection. These figures
include rejected users only. These figures are determined at the end of the simulation and depend on the
network design.
The number and the percentage of delayed users is given along with the reason for delay.
The number and percentage of R99 bearer users connected to a cell, the number of users per frequency band
for a dual-band network, the number of users per activity status, and the UL and DL total rates they generate.
These figures include R99 users as well as HSDPA and HSUPA bearer users (since all of them request an R99
bearer); they are determined in the R99 part of the algorithm. These data are also given per service.
The total number and the percentage of connected users with an HSDPA bearer, the number of users per
frequency band for a dual-band network, the number of users per activity status, and the DL total rate that
they generate. Packet (HSDPA), Packet (HSPA), and Packet (HSPA - Constant Bit Rate) service users are
considered because they all request an HSDPA bearer.
The total number of connected HSUPA bearer users and the percentage of users with an HSUPA bearer, the
number of users per frequency band for a dual-band network, the number of users per activity status, and the
UL total rate they generate. Only Packet (HSPA) and Packet (HSPA - Constant Bit Rate) service users are
considered.
The Sites tab: The Sites tab contains the following information per site:
-
Max No. of DL and UL CEs: The maximum number of channel elements available on uplink and downlink for R99
bearers requested by the users.
317

Forsk 2011
No. of DL and UL CEs Used: The number of channel elements required on uplink and downlink for R99 bearers to
handle the traffic of current simulation.
No. of DL and UL CEs Due to SHO Overhead: The number of extra channel elements due to soft handover, on
Carrier Selection: The carrier selection method defined on the site equipment.
Downlink and Uplink Overhead CEs/Cell: The overhead channel elements per cell on the downlink and on the
uplink, defined on the site equipment.
AS Restricted to Neighbours: Whether the active set is restricted to neighbours of the reference cell. This option
is selected on the site equipment.
Rake Factor: The rake factor, defined on the site equipment, enables Atoll to model a rake receiver on downlink.
MUD Factor: The multi-user detection factor, defined on the site equipment, is used to decrease intra-cell interference on uplink.
Compressed Mode: Whether compressed mode is supported. This option is defined on the site equipment.
Max Iub Downlink and Uplink Backhaul Throughput (kbps): The maximum Iub backhaul throughput in the downlink and uplink .
Iub Downlink and Uplink Backhaul Throughput (kbps): The Iub backhaul throughput required on downlink and
uplink to handle the traffic of current simulation.
Overhead Iub Throughput (kbps): the Iub throughput required by the site for common channels in the downlink.
It corresponds to the overhead Iub throughput per cell (defined on the site equipment) multiplied by the number
of cells on the site.
HSDPA Iub Backhaul Overhead (%): This parameter is defined on the site equipment. It corresponds to the percentage of the HSDPA bearer RLC peak rate to be added to the RLC peak rate. The total value corresponds to the
Iub backhaul throughput required by the HSDPA bearer user for HS Channels in the downlink.
Nb of Recommended E1/T1/Ethernet Link: The number of E1/T1/Ethernet links required to provide the total Iub
backhaul throughput.
Instantaneous HSDPA Rate (kbps): The Instantaneous HSDPA Rate (kbps).
Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps).
DL and UL Throughput for Each Service: The throughput in kbits s for each service. The result is detailed on the
downlink and uplink only when relevant.
The Cells tab: The Cells tab contains the following information, per site, transmitter, and carrier:
-
Max Power (dBm): The maximum power as defined in the cell properties.
Pilot Power (dBm): The pilot power as defined in the cell properties.
SCH power (dBm): The SCH power as defined in the cell properties.
Other CCH power (dBm): The power of other common channels. It includes the other CCH power and the DL
HSUPA power as defined in the cell properties.
Available HSDPA Power (dBm): The available HSDPA power as defined in the cell properties. This is the power
available for the HS-PDSCH and HS-SCCH. The value is either fixed by the user when the HSDPA power is allocated
statically, or by a simulation when the option HSDPA Power Dynamic Allocation is selected.
AS Threshold (dB): The active set threshold as defined in cell properties
Gain (dBi): The gain as defined in the antenna properties for that transmitter.
Reception Loss (dB): The reception loss as defined in the transmitter properties.
Transmission Loss (dB): The transmission loss as defined in the transmitter properties.
Noise Figure (dB): The noise figure as defined in the transmitter properties
Total Transmitted R99 Power (dBm): The total transmitted R99 power is the power transmitted by the cell on
common channels (Pilot, SCH, other CCH), HSUPA channels (E-AGCH, E-RGCH, and E-HICH) and R99 traffic-dedicated channels.
Transmitted HSDPA Power (dBm): The HSDPA power transmitted by the cell on HSDPA channels. It corresponds
to the HSDPA power used to serve HSDPA bearer users.
Total Transmitted Power (dBm): The total transmitted power of the cell is the sum of the total transmitted R99
power and the transmitted HSDPA power. If HSDPA power is allocated dynamically, the total transmitted power
cannot exceed the maximum power minus the power headroom.
When the constraint "DL load" is set and HSDPA power is statically allocated, the total
transmitted power cannot exceed the maximum DL load (defined either in the cell properties, or in the simulation). On the other hand, if HSDPA power is allocated dynamically, the
control is carried out on the R99 transmitted power, which cannot exceed the maximum
DL load.
318
UL Total Noise (dBm): The uplink total noise takes into account the total signal received at the transmitter on a
carrier from intra and extra-cell terminals using the same carrier and adjacent carriers (uplink total interference)
and the thermal noise.
Max UL Load Factor (%): The maximum uplink load factor that the cell can support. It is defined either in the cell
properties, or in the simulation creation dialogue.
Max DL Load (% Pmax): The maximum percentage of power that the cell can use. It is defined either in the cell

AT310_UMU_E0
UL load factor (%): The uplink cell load factor corresponds to the ratio between the uplink total interference and
the uplink total noise. If the constraint "UL load factor" has been selected, UL cell load factor is not allowed to
exceed the user-defined maximum UL load factor (either in the cell properties, or in the simulation creation dialogue).
DL Load Factor (%): The DL load factor of the cell i corresponds to the ratio (DL average interference [due to transmi er signals on the same and adjacent carriers] for terminals in the transmi er i area) (DL average total noise
[due to transmitter signals and to thermal noise of terminals] for terminals in the transmitter i area).
UL and DL Noise Rise (dB): The uplink and downlink noise rises are calculated from uplink and downlink load factors. These data indicate signal degradation due to cell load (interference margin in the link budget).
DL R99 Load (% Pmax): The percentage of power used for R99 channels is determined by the total transmitted
R99 power-maximum power ratio (power stated in W). When the constraint "DL load" is set and HSDPA power is
allocated dynamically, the DL R99 Load can not exceed the user-defined Max DL Load (defined either in the cell
properties, or in the simulation).
Reuse Factor (UL): The uplink reuse factor is the ratio between the uplink total interference and the intra-cell
interference.
Reuse Efficiency Factor (UL): The uplink reuse efficiency factor is the reciprocal of the uplink reuse factor.
Number of UL and DL Radio Links: The number of radio links corresponds to the number of user-transmitter links
on the same carrier. This data is calculated on uplink and on downlink and indicates the number of users connected to the cell on uplink and downlink. Because of handover, a single user can use several radio links.
Connection Success Rate (%): The connection success rate gives the ratio of connected users over the total
number of users in the cell.
HSDPA Application Throughput (kbps): This is the net HSDPA throughput without coding (redundancy, overhead,
addressing, etc.). The HSDPA application throughput of dual-cell HSDPA users is the sum of their HSDPA application throughputs on both cells.
Min. HSDPA RLC Peak Rate (kbps): The minimum HSDPA RLC peak rate corresponds to the lowest of RLC peak
rates obtained by HSDPA bearer users connected to the cell. For dual-cell HSDPA users, this is the lower of the two
minimum HSDPA RLC peak rates.
Max HSDPA RLC Peak Rate (kbps): The maximum HSDPA RLC peak rate corresponds to the highest of RLC peak
rates obtained by HSDPA bearer users connected to the cell. For dual-cell HSDPA users, this is the higher of the
two maximum HSDPA RLC peak rates.
Avg. Instantaneous HSDPA Throughput (kbps): The average instantaneous HSDPA rate (kbps) is the average
number of kbits per second that the cell supports on downlink to provide one connected user with an HSDPA
bearer. The HSDPA throughput of dual-cell HSDPA users is the sum of their HSDPA throughputs on both cells.
Instantaneous HSDPA Rate (kbps): The instantaneous HSDPA rate (kbps) is the number of kbits per second that
the cell supports on downlink to provide simultaneous connected users with an HSDPA bearer. The HSDPA rate of
dual-cell HSDPA users is the sum of their HSDPA rates on both cells.
Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps) that the cell
carries. The HSDPA throughput of dual-cell HSDPA users is the sum of their HSDPA throughputs on both cells.
No. of Simultaneous HSDPA Users: The number of simultaneous HSDPA users corresponds to the number of
HSDPA bearer users that the cell supports at one time, i.e. within one time transmission interval. All these users
are connected to the cell at the end of the HSDPA part of the simulation; they have a connection with the R99
bearer and an HSDPA bearer. Dual-cell HSDPA users are be accounted for once in each cell they are connected to.
No. of HSDPA Users: The number of HSDPA users including the connected and delayed HSDPA bearer users. Dualcell HSDPA users are be accounted for once in each cell they are connected to.
No. of HSUPA Users: The number of HSUPA bearer users connected to the cell.
HSUPA Application Throughput (kbps): This is the net HSUPA throughput without coding (redundancy, overhead,
addressing, etc.).
HSUPA UL Load Factor (%): The uplink cell load contribution due to HSUPA traffic.
No. of Codes (512 Bits): The number of 512-bit OVSF codes used per cell.
The types of handover as a percentage: Atoll estimates the percentages of handover types for each transmitter.
Atoll only lists the results for the following handover status, no handover (1 1), so er (1 2), so (2 2), so er-so
(2 3) and so -so (3 3) handovers; the other handover status (other HO) are grouped.
R99 UL and DL Throughput (kbps): The uplink and downlink R99 throughputs represent the numbers of kbits per
second delivered by the cell respectively on uplink and on downlink to supply users with a R99 bearer. All the radio
links in the cell, i.e., links due to handover, are taken into account in the throughput calculation.
R99 UL and DL Throughput Without HO (kbps): The uplink and downlink R99 throughputs represent the numbers
of kbits per second delivered by the cell respectively on uplink and on downlink to supply users with a R99 bearer.
Only the links with the best server are taken into account in the calculation of throughput.
Min TCH Pwr (dBm): The minimum power allocated to a traffic channel to supply services.
Max TCH Pwr (dBm): The maximum power allocated to a traffic channel to supply services.
Avg TCH Pwr (dBm): The average power allocated to a traffic channel to supply services.
Non-connected users: The number of rejected and delayed users per cell. Rejected users are sorted by the following values: Pmob > PmobMax, Ptch > PtchMax, EcIo < (EcIo)min., UL Load Saturation, Ch. Elts Saturation,
DL Load Saturation, Code Saturation, Admission Rejection, HSDPA Scheduler Saturation, HSDPA Resource Saturation, HSUPA Admission Rejection, HSUPA Scheduler Saturation and Iub Throughput Saturation. Delayed
users are regrouped under HSDPA Delayed.
319

Forsk 2011
Connection Success Rate (%) For Each Service: For each service, the connection success rate gives the ratio of connected users over the total number of users of that service in the cell.
The Mobiles tab: The Mobiles tab contains the following information:
The Mobiles tab only appears if, when creating the simulation as explained in "Creating
Simulations" on page 313, you select either "Standard information about mobiles" or
"Detailed information about mobiles" under Information to Retain.
-
X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the second
random trial).
Service: The service assigned during the first random trial during the generation of the user distribution.
Terminal: The assigned terminal. Atoll uses the assigned service and activity status to determine the terminal and
the user profile.
User Profile: The assigned user profile. Atoll uses the assigned service and activity status to determine the terminal and the user profile.
Mobility: The mobility type assigned during the first random trial during the generation of the user distribution.
Activity Status: The activity status assigned during the first random trial during the generation of the user distribution.
Carrier: The carrier used for the mobile-transmitter connection. Dual-cell HSDPA users are connected to two carriers. Details can be displayed per carrier by selecting Actions > Detailed Display.
Frequency Band: the frequency band used for the mobile-transmitter connection.
DL and UL Total Requested Rate (kbps): For circuit and packet (R99) service users, the DL and UL total requested
rates correspond to the DL and UL nominal rates of the R99 bearer associated to the service.
For packet (HSDPA) service users, the uplink total requested rate corresponds to the nominal rate of ADPCH-UL64
R99 bearer and the downlink total requested rate is the sum of the ADPCH-UL64 radio bearer nominal rate and
the RLC peak rate that the selected HSDPA radio bearers can provide. Here, the HSDPA user is treated as if he is
the only user in the cell and then, Atoll determines the HSDPA bearer the user would obtain by considering the
entire HSDPA power available of the cell.
For HSUPA bearer users (i.e., packet (HSPA) and packet (HSPA - Constant Bit Rate) service users), the uplink total
requested rate is equal to the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate of the
requested HSUPA radio bearer. The requested HSUPA radio bearer is selected from the HSUPA bearers compatible
with the user equipment. Here, the HSUPA user is treated as if he is the only user in the cell and then, Atoll determines the HSUPA bearer the user would obtain by considering the entire remaining load of the cell. The downlink
total requested rate is the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate that the
requested HSDPA radio bearer can provide. The requested HSDPA bearer is determined as explained in the previous paragraph.
DL and UL Total Obtained Rate (kbps): For circuit and packet (R99) service users, the DL or UL total obtained rate
is the same as the DL or UL total requested rate if he is connected without being downgraded. Otherwise, the total
obtained rate is lower (it corresponds to the nominal rate of the selected R99 bearer). If the user was rejected, the
total obtained rate is zero.
For a packet (HSDPA) service user connected to an HSDPA bearer, the uplink total obtained rate equals the requested one and the downlink total obtained rate corresponds to the instantaneous rate; this is the sum of the
ADPCH-UL64 radio bearer nominal rate and the RLC peak rate provided by the selected HSDPA radio bearers after
scheduling and radio resource control. If the user is delayed (he is only connected to an R99 radio bearer), uplink
and downlink total obtained rates correspond to the uplink and downlink nominal rates of ADPCH-UL64 radio
bearer. Finally, if the user is rejected either in the R99 part or in the HSDPA part (i.e., because the HSDPA scheduler
is saturated), the uplink and downlink total obtained rates are zero.
For a connected packet (HSPA) service user, on uplink, if the user is connected to an HSUPA bearer, the uplink total
obtained rate is the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate provided by the
selected HSUPA radio bearer after noise rise scheduling. On downlink, if the user is connected to an HSDPA bearer,
the downlink total obtained rate corresponds to the instantaneous rate. The instantaneous rate is the sum of the
ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate provided by the selected HSDPA radio bearers
after scheduling and radio resource control. If the user is delayed, the downlink total obtained rate corresponds
to the downlink nominal rate of ADPCH-EDPCCH radio bearer. If the user is rejected, the uplink and downlink total
obtained rates are "0".
For a connected packet (HSPA - Constant Bit Rate) service user, the uplink and downlink total obtained rates are
the sum of the ADPCH-EDPCCH radio bearer nominal rate and the guaranteed bit rate defined for the service. If
the user is rejected, the uplink and downlink total obtained rates are "0".
320
Mobile Total Power (dBm): The mobile total power corresponds to the total power transmitted by the terminal.
Connection Status: The connection status indicates whether the user is connected, delayed or rejected at the end
of the simulation. If connected, the connection status corresponds to the activity status. If rejected, the rejection
cause is given. If delayed (for packet (HSDPA) and packet (HSPA) service users only), the status is "HSDPA delayed."

AT310_UMU_E0
Best Server: The best server among the transmitters in the mobile active set.
HO Status (Sites/No. Transmitters Act. Set): The HO status is the number of sites compared to the number of
transmitters in the active set.
AS1, AS2, AS3, AS4: The name of the cell that is the best server, the second-best server, and so on is given in a
separate column for each cell in the active set.
Ec/I0 AS1, AS2, AS3, AS4, (dB): Ec I0 is given in a separate column for each cell in the ac ve set. The Ec/I0 AS 1
column lists the Ec/I0 from the best server for the rejected mobiles as well.
Indoor: This field indicates whether indoor losses have been added or not.
Active Compressed Mode: This field indicates whether active compressed mode is supported by the mobile or
not.
The following columns only appear if, when creating the simulation as explained in "Creating Simulations" on
page 313, you select "Detailed information about mobiles" under Information to Retain:
-
DL and UL Requested RLC Peak Rates (kbps): For HSUPA bearer users (i.e., packet (HSPA) and packet (HSPA - Constant Bit Rate) service users), the requested uplink RLC peak rate is the rate of the requested HSUPA radio bearer.
If the user is connected to an HSDPA bearer in the downlink, the downlink requested RLC peak rate is the rate that
the requested HSDPA radio bearer can provide.
Downlink and uplink requested RLC peak rates are not calculated for circuit and packet (R99) service users. For
packet (HSDPA) service users, the uplink RLC peak rate is not calculated and the downlink requested RLC peak rate
is the rate that the selected HSDPA radio bearer can provide.
DL and UL Obtained RLC Peak Rate (kbps): For a connected packet (HSPA) service user, on uplink, if the user is
connected to an HSUPA bearer, the obtained uplink RLC peak rate is the rate provided by the selected HSUPA radio
bearer after noise rise scheduling. On downlink, if the user is connected to an HSDPA bearer, the downlink
obtained RLC peak rate is the rate provided by the selected HSDPA radio bearer after scheduling and radio
resource control. For a connected packet (HSPA - Constant Bit Rate) service user, the uplink and downlink obtained
RLC peak rates are the uplink and downlink guaranteed bit rates defined for the service.
Downlink and uplink obtained RLC peak rates are not calculated for circuit and packet (R99) service users.
For a packet (HSDPA) service user connected to an HSDPA bearer, the downlink obtained RLC peak rate is the rate
provided by the selected HSDPA radio bearer after scheduling and radio resource control. The uplink obtained RLC
peak rate is not calculated.
HSDPA Application Throughput (kbps): The HSDPA application throughput is the net HSDPA throughput without
coding (redundancy, overhead, addressing, etc.). It is calculated from the instantaneous HSDPA rate (i.e., the DL
obtained rate), the BLER, the HSDPA service scaling factor and the throughput offset.
Served HSDPA Power (dBm): This is the HSDPA power required to provide the HSDPA bearer user with the downlink obtained rate.
Required HSDPA Power (dBm): The required HSDPA power is the HSDPA power required to provide the HSDPA
bearer user with the downlink requested rate. If the HSDPA bearer allocated to the user is the best one, the
required HSDPA power corresponds to the available HSDPA power of the cell. On the other hand, if the HSDPA has
been downgraded in order to be compliant with cell and UE capabilities, the required HSDPA power will be lower
than the available HSDPA power of the cell.
No. of HSUPA Retransmissions (Required): The maximum number of retransmissions in order to have the
requested HSUPA radio bearer with a given BLER.
No. of HSUPA Retransmissions (Obtained): The maximum number of retransmissions in order to have the
obtained HSUPA radio bearer with a given BLER.
HSUPA Application Throughput (kbps): The HSUPA application throughput is the net HSUPA throughput without
coding (redundancy, overhead, addressing, etc.). It is calculated from the UL obtained rate, the BLER, the HSUPA
service scaling factor and the throughput offset.
Cell TCH Power AS1, AS2, AS3, AS4 (DL) (dBm): The cell power transmitted on the downlink is given for each link
between the mobile and a transmitter in the active set.
DL Ntot AS1, AS2, AS3, AS4 (dBm): The total noise on the downlink for each link between the mobile and a transmitter in the \active set.
Load Factor AS1, AS2, AS3, AS4 (DL) (%): The load factor on the downlink for each link between the mobile and a
transmitter in the active set. It corresponds to the ratio between the total interference on the downlink and total
noise at the terminal.
Noise Rise AS1, AS2, AS3, AS4 (DL) (dB): The noise rise on the downlink for each link between the mobile and a
transmitter in the active set.
Reuse Factor AS1, AS2, AS3, AS4 (DL): The DL reuse factor for each link between the mobile and a transmitter in
the active set. It is calculated from the interference received at the terminal from the intra cell area and the total
interference received at the terminal from all the transmitters (intra and extra-cell and inter-carrier).
Iintra AS1, AS2, AS3, AS4 (DL) (dBm): The intra-cell interference for each cell (I) of the active set.
DL
(ic ) Fortho P DL
(ic ) PSCH
I int ra = P DL
tot
tot
LT
i
i
321

Forsk 2011
Iextra AS1, AS2, AS3, AS4 (DL) (dBm): The extra-cell interference for each cell (I) of the active set.
I extra =
DL
(ic ) Fortho P DL
(ic ) PSCH
P DL
tot
tot
LT
Tx ,iTx
Total Loss AS1, AS2, AS3, AS4 (dB): The total attenuation for each link between the mobile and a transmitter in
the active set.
Iub UL Backhaul Throughput (kbps): The Iub backhaul throughput consumed on the uplink by the mobile.
Iub DL Backhaul Throughput (kbps): The Iub backhaul throughput consumed on the downlink by the mobile.
No. of UL CEs: The number of channel elements consumed on the uplink by the mobile.
No. of DL CEs: The number of channel elements consumed on the downlink by the mobile.
Name: The name of the mobile, as assigned during the random user generation.
Clutter: The clutter class on which the mobile is located.
Orthogonality Factor: The orthogonality factor used in the simulation. The orthogonality factor is the remaining
orthogonality of the OVSF codes at reception. The value used is the orthogonality factor set in the clutter classes.
% Pilot Finger: The percentage pilot finger used in the simulation, defined per clutter class or globally for all clutter
classes.
UL SHO Gain (dB): The uplink soft handover gain is calculated if mobile receivers are connected either on DL or on
UL and DL.
DL SHO Gain (dB): The downlink soft handover gain is calculated if mobile receivers are connected either on DL or
on UL and DL.
No. of Codes (512 Bits): The number of OVSF codes used per mobile.
The Mobiles (Shadowing Values) tab: The Mobiles (Shadowing Values) tab contains information on the shadowing
margin for each link between the receiver and up to ten closest potential transmitters:
The Mobiles (Shadowing Values) tab only appears if, when creating the simulation as
explained in "Creating Simulations" on page 313, you select "Detailed information about
mobiles" under Information to Retain.
-
Name: The name assigned to the mobile.

Value at Receiver (dB): The value of the shadowing margin at the receiver.
Clutter: The clutter class on which the mobile is located.
Path To: The name of the potential transmitter.
Value (dB): The shadowing value for the potential link in the corresponding Path To column. These values depend
on the model standard deviation per clutter type on which the receiver is located and are randomly distributed on
a gaussian curve.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
-
The global transmitter parameters:

-
The input parameters specified when creating the simulation:

-
The spreading width

Whether the power values on the downlink are absolute or relative to the pilot
The default uplink soft handover gain
Whether the MRC in softer/soft is defined or not
The methods used to calculate I0 and Nt
Parameters for compressed mode
The methods used to calculate Nt and CQI for HSDPA.
The maximum number of iterations
The global scaling factor
The generator initialisation value
The uplink and downlink convergence thresholds
The simulation constraints such as maximum power, the maximum number of channel elements, the maximum Iub throughputs, the uplink load factor and the maximum load
The name of the traffic maps used.
The parameters related to the clutter classes, including the default values.
6.3.4.6 Displaying the Average Results of a Group of Simulations

After you have created a group of simulations, as explained in "Creating Simulations" on page 313, you can display the average
results of the group. If you want to display the results of a single simulation of a group, see "Displaying the Results of a Single
Simulation" on page 317.
322

AT310_UMU_E0
To access the averaged results of a group of simulations:

3. Right-click the group of simulations whose results you want to access.

4. Select Average Simulation from the context menu. A properties dialogue appears.
One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialogue contain simulation results for all simulations, both averaged and as a standard deviation.
The Statistics tab: The Statistics tab contains the following two sections:
-
Request: Under Request, you will find data on the connection requests:
-
Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; power control has not yet finished. The result depends on the traffic description and traffic input.
During the first random trial, each user is assigned a service. The UL and DL rates that all users could theoretically generate are provided.
The breakdown per service (total number of users, number of users per activity status, and UL and DL rates)
is given.
Results: Under Results, you will find data on the connection results:
-
The number of iterations that were run in order to converge.

The number and the percentage of rejected users is given along with the reason for rejection. These figures
include rejected users only. These figures are determined at the end of the simulation and depend on the
network design.
The number and the percentage of delayed users is given along with the reason for delay.
The number and percentage of R99 bearer users connected to a cell, the number of users per frequency band
for dual-band networks, the number of users per activity status, and the total UL and DL rates they generate.
These figures include R99 users as well as HSDPA and HSUPA bearer users (since all of them request an R99
bearer); they are determined in the R99 part of the algorithm. These data are also given per service.
The total number and the percentage of connected users with an HSDPA bearer, the number of users per
frequency band for dual-band networks, the number of users per activity status, and DL total rate that they
generate. Packet (HSDPA), packet (HSPA) and packet (HSPA - Constant Bit Rate) service users are considered
since they all request an HSDPA bearer.
The total number of connected HSUPA bearer users and the percentage of users with an HSUPA bearer, the
number of users per frequency band for dual-band networks, the number of users per activity status, and UL
and DL total rates they generate. Only packet (HSPA) and packet (HSPA - Constant Bit Rate) service users are
considered.
The Sites (Average) and Sites (Standard Deviation) tabs: The Sites (Average) and Sites (Standard Deviation) tabs
contains the following average and standard deviation information, respectively, per site:
-
Max No. of DL and UL CEs: The maximum number of channel elements available on uplink and downlink for R99
bearers requested by the users.
No. of DL and UL CEs Used: The number of channel elements required on uplink and downlink for R99 bearers to
handle the traffic of current simulation.
No. of DL and UL CEs Due to SHO Overhead: The number of extra channel elements due to soft handover, on
Carrier Selection: The carrier selection method defined on the site equipment.
Downlink and Uplink Overhead CEs/Cell: The overhead channel elements per cell on the downlink and on the
uplink, defined on the site equipment.
AS Restricted to Neighbours: Whether the active set is restricted to neighbours of the reference cell. This option
is selected on the site equipment.
Rake Factor: The rake factor, defined on the site equipment, enables Atoll to model a rake receiver on downlink.
MUD Factor: The multi-user detection factor, defined on the site equipment, is used to decrease intra-cell interference on uplink.
Compressed Mode: Whether compressed mode is supported. This option is defined on the site equipment.
Max Iub Downlink and Uplink Backhaul Throughput (kbps): The maximum Iub backhaul throughput in the downlink and uplink.
Iub Downlink and Uplink Backhaul Throughput (kbps): The Iub backhaul throughput required on downlink and
uplink to handle the traffic of current simulation.
Overhead Iub Throughput/Cell (kbps): The Iub throughput required by the cell for common channels in the downlink, defined on the site equipment.
HSDPA Iub Backhaul Overhead (%): This parameter is defined on the site equipment. It corresponds to the percentage of the HSDPA bearer RLC peak rate to be added to the RLC peak rate. The total value corresponds to the
Iub backhaul throughput required by the HSDPA bearer user for HS Channels in the downlink.
Nb of Recommended E1/T1/Ethernet Link: The number of E1/T1/Ethernet links required to provide the total Iub
backhaul throughput.
323

Forsk 2011
Instantaneous HSDPA Rate (kbps): The Instantaneous HSDPA Rate (kbps).

Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps).
DL and UL Throughput for Each Service: The throughput in kbits s for each service.
The Cells (Average) and Cells (Standard Deviation) tabs: The Cells (Average) and Cells (Standard Deviation) tabs
contains the following average and standard deviation information, respectively, per site, transmitter, and carrier:
-
Max Power (dBm): The maximum power as defined in the cell properties.
Pilot Power (dBm): The pilot power as defined in the cell properties.
SCH power (dBm): The SCH power as defined in the cell properties.
Other CCH power (dBm): The power of other common channels. It includes the other CCH power and the DL
HSUPA power as defined in the cell properties.
Available HSDPA Power (dBm): The available HSDPA power as defined in the cell properties. This is the power
available for the HS-PDSCH and HS-SCCH. The value is either fixed by the user when the HSDPA power is allocated
statically, or by a simulation when the option HSDPA Power Dynamic Allocation is selected.
AS Threshold (dB): The active set threshold as defined in cell properties
Gain (dBi): The gain as defined in the antenna properties for that transmitter.
Reception Loss (dB): The reception loss as defined in the transmitter properties.
Transmission Loss (dB): The transmission loss as defined in the transmitter properties.
Noise Figure (dB): The noise figure as defined in the transmitter properties
Total Transmitted R99 Power (dBm): The total transmitted R99 power is the power transmitted by the cell on
common channels (Pilot, SCH, other CCH), HSUPA channels (E-AGCH, E-RGCH, and E-HICH) and R99 traffic-dedicated channels.
Transmitted HSDPA Power (dBm): The HSDPA power transmitted by the cell on HSDPA channels. It corresponds
to the HSDPA power used to serve HSDPA bearer users.
Total Transmitted Power (dBm): The total transmitted power of the cell is the sum of the total transmitted R99
power and the transmitted HSDPA power. If HSDPA power is allocated dynamically, the total transmitted power
cannot exceed the maximum power minus the power headroom.
When the constraint "DL load" is set and HSDPA power is statically allocated, the total
transmitted power cannot exceed the maximum DL load (defined either in the cell properties, or in the simulation). On the other hand, if HSDPA power is allocated dynamically, the
control is carried out on the R99 transmitted power, which cannot exceed the maximum
DL load.
324
UL Total Noise (dBm): The uplink total noise takes into account the total signal received at the transmitter on a
carrier from intra and extra-cell terminals using the same carrier and adjacent carriers (uplink total interference)
and the thermal noise.
Max UL Load Factor (%): The maximum uplink load factor that the cell can support. It is defined either in the cell
Max DL Load (% Pmax): The maximum percentage of power that the cell can use. It is defined either in the cell
UL Load Factor (%): The uplink cell load factor corresponds to the ratio between the uplink total interference and
the uplink total noise. If the constraint "UL load factor" has been selected, UL cell load factor is not allowed to
exceed the user-defined maximum UL load factor (either in the cell properties, or in the simulation creation dialogue).
UL Load Factor due to HSUPA (%): The uplink cell load caused by HSUPA traffic.
DL Load Factor (%): The DL load factor of the cell i corresponds to the ratio (DL average interference [due to transmi er signals on the same carrier] for terminals in the transmi er i area) (DL average total noise [due to transmitter signals and to thermal noise of terminals] for terminals in the transmitter i area).
UL and DL Noise Rise (dB): The uplink and downlink noise rises are calculated from uplink and downlink load factors. These data indicate signal degradation due to cell load (interference margin in the link budget).
DL R99 Load (% Pmax): The percentage of power used for R99 channels is determined by the total transmitted
R99 power-maximum power ratio (power stated in W). When the constraint "DL load" is set and HSDPA power is
allocated dynamically, the DL R99 Load can not exceed the user-defined Max DL Load (defined either in the cell
properties, or in the simulation).
Reuse Factor (UL): The uplink reuse factor is the ratio between the uplink total interference and the intra-cell
interference.
Reuse Efficiency Factor (UL): The uplink reuse efficiency factor is the reciprocal of the uplink reuse factor.
Number of UL and DL Radio Links: The number of radio links corresponds to the number of user-transmitter links
on the same carrier. This data is calculated on uplink and on downlink and indicates the number of users connected to the cell on uplink and downlink. Because of handover, a single user can use several radio links.
Connection Success Rate (%): The connection success rate gives the ratio of connected users over the total
number of users in the cell.
HSDPA Application Throughput (kbps): The HSDPA application throughput is the net HSDPA throughput without
coding (redundancy, overhead, addressing, etc.). It is calculated from the instantaneous HSDPA rate (i.e., the DL

AT310_UMU_E0
obtained rate), the BLER, the HSDPA service scaling factor and the throughput offset. The HSDPA application
throughput of dual-cell HSDPA users is the sum of their HSDPA application throughputs on both cells.
Min. HSDPA RLC Peak Rate (kbps): The minimum HSDPA RLC peak rate corresponds to the lowest of RLC peak
rates obtained by HSDPA bearer users connected to the cell. For dual-cell HSDPA users, this is the lower of the two
minimum HSDPA RLC peak rates.
Max HSDPA RLC Peak Rate (kbps): The maximum HSDPA RLC peak rate: It corresponds to the highest of RLC peak
rates obtained by HSDPA bearer users connected to the cell. For dual-cell HSDPA users, this is the higher of the
two maximum HSDPA RLC peak rates.
Avg. Instantaneous HSDPA Throughput (kbps): The average instantaneous HSDPA rate (kbps) is the average
number of kbits per second that the cell supports on downlink to provide one connected user with an HSDPA
bearer. The HSDPA throughput of dual-cell HSDPA users is the sum of their HSDPA throughputs on both cells.
Instantaneous HSDPA Rate (kbps): The instantaneous HSDPA rate (kbps) is the number of kbits per second that
the cell supports on downlink to provide simultaneous connected users with an HSDPA bearer. The HSDPA rate of
dual-cell HSDPA users is the sum of their HSDPA rates on both cells.
Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps) that the cell
carries. The HSDPA throughput of dual-cell HSDPA users is the sum of their HSDPA throughputs on both cells.
No. of Simultaneous HSDPA Users: The number of simultaneous HSDPA users corresponds to the number of
HSDPA bearer users that the cell supports at a time, i.e. within one time transmission interval. All these users are
connected to the cell at the end of the simulation HSDPA part; they have a connection with the R99 bearer and an
HSDPA bearer. Dual-cell HSDPA users are be accounted for once in each cell they are connected to.
No. of HSDPA Users: The number of HSDPA users include the connected and delayed HSDPA bearer users. Dualcell HSDPA users are be accounted for once in each cell they are connected to.
No. of HSUPA Users: The number of HSUPA bearer users connected to the cell.
HSUPA Application Throughput (kbps): This is the net HSUPA throughput without coding (redundancy, overhead,
addressing, etc.).
HSUPA UL Load Factor (%): The uplink cell load caused by HSUPA traffic.
No. of Codes (512 Bits): The number of OVSF codes used per cell.
The types of handover as a percentage: Atoll estimates the percentages of handover types for each transmitter.
Atoll only lists the results for the following handover status, no handover (1 1), so er (1 2), so (2 2), so er-so
(2 3) and so -so (3 3) handovers; the other handover status (other HO) are grouped.
R99 UL and DL Throughput (kbps): The uplink and downlink R99 throughputs represent the numbers of kbits per
second delivered by the cell respectively on uplink and on downlink to supply users with a R99 bearer. All the radio
links in the cell, i.e., links due to handover, are taken into account in the throughput calculation.
R99 UL and DL Throughput Without HO (kbps): The uplink and downlink R99 throughputs represent the numbers
of kbits per second delivered by the cell respectively on uplink and on downlink to supply users with a R99 bearer.
Only the links with the best server are taken into account in the calculation of throughput.
Min TCH Pwr (dBm): The minimum power allocated to a traffic channel to supply services.
Max TCH Pwr (dBm): The maximum power allocated to a traffic channel to supply services.
Avg TCH Pwr: The average power allocated to a traffic channel to supply services.
Non-connected users: The number of rejected and delayed users per cell. Rejected users are sorted by the following reasons: Pmob > PmobMax, Ptch > PtchMax, EcIo < (EcIo)min., UL Load Saturation, Ch. Elts Saturation,
DL Load Saturation, Code Saturation, Admission Rejection, HSDPA Delayed, HSDPA Scheduler Saturation,
HSDPA Resource Saturation, HSUPA Admission Rejection, HSUPA Scheduler Saturation and Iub Throughput Saturation. Delayed users are regrouped under HSDPA Delayed.
Connection Success Rate (%) For Each Service: For each service, the connection success rate gives the ratio of connected users over the total number of users of that service in the cell.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
-
The global transmitter parameters:

-
The input parameters specified when creating the group of simulations:

-
The spreading width

Whether the power values on the downlink are absolute or relative to the pilot
The default uplink soft handover gain
Whether the MRC in softer/soft is defined or not
The methods used to calculate I0 and Nt
Parameters for compressed mode
The methods used to calculate Nt and CQI for HSDPA.
The maximum number of iterations
The global scaling factor
The generator initialisation value
The uplink and downlink convergence thresholds
The simulation constraints such as maximum power, the maximum number of channel elements, the uplink
load factor and the maximum load
The name of the traffic maps used.
The parameters related to the clutter classes, including the default values.
325

Forsk 2011
6.3.4.7 Updating Cell Values With Simulation Results

After you have created a simulation or a group of simulations, as explained in "Creating Simulations" on page 313, you can
update values for each cell with the results calculated during the simulation. The following values are updated:
Total Transmitted Power

UL Load Factor
UL Reuse Factor
Available HSDPA Power
Number of HSDPA Users
UL Load Factor due to HSUPA
Number of HSUPA Users.
To update cell values with simulation results:

1. Display the simulation results:
To display the results for a group of simulations:
a. Click the Network tab in the Explorer window.
c. Right-click the group of simulations whose results you want to access.

d. Select Average Simulation from the context menu. A properties dialogue appears.
One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialogue contain simulation results for all simulations, both averaged and as a standard deviation.
To display the results for a single simulation:
a. Click the Network tab in the Explorer window.
c. Click the Expand button (

you want to access.
) to expand the folder of the simulation group containing the simulation whose results
d. Select Properties from the context menu. The simulation properties dialogue appears.
3. On the Cells tab, click Commit Results. The following values are updated for each cell:
-
Total Transmitted Power

UL Load Factor
UL Reuse Factor
Available HSDPA Power
Number of HSDPA Users
UL Load Factor due to HSUPA
Number of HSUPA Users.
6.3.4.8 Adding New Simulations to an Atoll Document

When you have created a simulation or group of simulations, you can re-examine the same conditions by adding new simulations to the Atoll document. In Atoll, there are the following ways of adding new simulations:
Adding to a group: When you add one or more simulations to an existing group of simulations, Atoll reuses the same
input (radio, traffic, and simulation parameters) as those used to generate the group of simulations. It then generates
a new user distribution and performs the power control simulation.
To add a simulation to a group of simulations, see "Adding a Simulation to a Group of Simulations" on page 327.
Replaying a group: When you replay an existing group of simulations, Atoll reuses the same user distribution (users
with a service, a mobility and an activity status) as the one used to calculate the initial simulation. The shadowing error
distribution between simulations is different. Traffic parameter changes (such as, maximum and minimum traffic
channel powers allowed, Eb/Nt thresholds, etc.) might or might not be taken into account. Finally, radio data modifications (new transmitters, changes to the antenna azimuth, etc.) are always taken into account during the power control (or rate/power control) simulation.
To replay a group of simulations, see "Replaying a Simulation or Group of Simulations" on page 327.
326
Using the Generator Initialisation Number: When you create groups of simulations using the same generator initialisation number (which must be an integer other than 0) Atoll generates the same user and shadowing error distributions (user with a service, a mobility, an activity status and a shadowing error) in all groups using the same number.
However, any modifications to traffic parameters (such as, maximum and minimum traffic channel powers allowed,

AT310_UMU_E0
Eb Nt thresholds, etc.) and radio data (new transmi er, azimuth, etc.) are taken into account during the power control
simulation.
By creating and calculating one group of simulations, making a change to the network and then creating and calculating a new group of simulations using the same generator initialisation number, you can see the difference your parameter changes make.
To create a new simulation to a group of simulations using the generator initialisation number, see "Creating a New
Simulation or Group of Simulations Using the Generator Initialisation Number" on page 328.
Duplicating a Group: When you duplicate a group, Atoll creates a group of simulations with the same simulation
parameters as those used to generate the group of simulations. You can then modify the simulation parameters
before calculating the group.
To duplicate a group of simulations, see "Duplicating a Simulation or Group of Simulations" on page 328.
Adding a Simulation to a Group of Simulations

To add a simulation to an existing group of simulations:
3. Right-click the group of simulations to which you want to add a simulation. The context menu appears.
4. Select New from the context menu. The properties dialogue of the group of simulations appears.
When adding a simulation to an existing group of simulations, the parameters originally
used to calculate the group of simulations are used for the new simulations. Consequently,
few parameters can be changed for the added simulation.
5. On the General tab of the dialogue, if desired, change the Name and Comments for this group of simulations.
6. Under Execution on the General tab, you can set the following parameter:
-
Number of Simulations: Enter the number of simulations to added to this group of simulations.
7. Once you have added the simulation, you can calculate it immediately or you can save it to calculate it later:
-
Calculate: Click Calculate to save the defined simulation and calculate it immediately.
OK: Click OK to save the defined simulation without calculating it. You can calculate it later clicking the Calculate
button (
Replaying a Simulation or Group of Simulations

To replay an existing simulation or group of simulations:
3. Right-click the group of simulations you want to replay. The context menu appears.
4. Select Replay from the context menu. The properties dialogue of the group of simulations appears.
When replaying an existing group of simulations, some parameters originally used to calculate the group of simulations are reused for the replayed group. Consequently, few parameters can be changed for the replayed group.
5. On the General tab of the dialogue, you can set the following parameters:
-
Select the level of detail as explained in "Creating Simulations" on page 313 that will be available in the output
from the Information to retain list.
Under Cell Load Constraints, you can set the constraints as explained in "Creating Simulations" on page 313 that
Atoll must respect during the simulation.
Under Bearer Negotiation, check the Bearer downgrading check box if you want to permit bearer downgrading
during the simulation.
6. On the Source Traffic tab of the dialogue, select the Refresh Traffic Parameters check box if you want to take into
account traffic parameter changes (such as maximum and minimum traffic channel powers allowed, Eb/Nt thresholds,
etc.) in the replayed simulation.
7. On the Advanced tab, you can set the following parameters:
-
Max Number of Iterations: Enter the maximum number of iterations that Atoll should run to make convergence.
327

Forsk 2011
UL Convergence Threshold: Enter the relative difference in terms of interference and connected users on the
uplink that must be reached between two iterations.
DL Convergence Threshold: Enter the relative difference in terms of interference and connected users on the
downlink that must be reached between two iterations.
8. Click Calculate. Atoll immediately begins the simulation.

Creating a New Simulation or Group of Simulations Using the Generator Initialisation Number
To create a new simulation or group of simulations using the generator initialisation number:
3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears.
4. Click the Advanced tab.
5. Under Generator Initialisation, enter an integer as the generator initialisation value. The integer must be the same
generator initialisation number as used in the group of simulations with the user and shadowing error distributions
you want to use in this simulation or group of simulations. If you enter "0", the default, the user and shadowing error
distribution will be random. If you enter any other integer, the same user and shadowing error distribution will be
used for any simulation using the same generator initialisation value.
6. For information on setting other parameters, see "Creating Simulations" on page 313.
You can create a new group of simulations with the same parameters as the original
group of simulations by duplicating an existing one as explained in "Duplicating a
Simulation or Group of Simulations" on page 328.
Duplicating a Simulation or Group of Simulations
To duplicate an existing simulation or group of simulations:
3. Right-click the simulation or group of simulations you want to duplicate. The context menu appears.
4. Select Duplicate from the context menu. The properties dialogue for the duplicated group of simulations appears.
You can change the parameters for the duplicated simulation or group of simulations as explained in "Creating Simulations" on page 313.
6.3.4.9 Estimating a Traffic Increase

When you create a simulation or a group of simulations, you are basing it on a set of traffic conditions that represent the situation you are creating the network for. However, traffic can, and in fact most likely will, increase. You can test the performance
of the network against an increased traffic load without changing traffic parameters or maps by using the global scaling factor.
For example, setting the global scaling factor to "2" is the same as doubling the initial number of subscribers (for environment
and user profile traffic maps) or the rates/users (for sector traffic maps).
To change the global scaling factor:
1. Create a simulation or group of simulations by:
-
Creating a new simulation or group of simulations as described in "Creating Simulations" on page 313.
Duplicating an existing simulation or group of simulations as described in "Adding New Simulations to an Atoll Document" on page 326.
2. Click the Source Traffic tab of the properties dialogue.

3. Enter a Global Scaling Factor. For example, setting the global scaling factor to "2" is the same as doubling the initial
number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps).
6.3.5 Analysing the Results of a Simulation

In Atoll, you have several methods available to help you analyse simulation results. You can make an active set analysis of a
real-time probe user or you can make a prediction where each pixel is considered as a probe user with a defined terminal,
mobility, and service. The analyses are based on a single simulation or on an averaged group of simulations.
You can find information on the analysis methods in the following sections:
328
"Making an AS Analysis of Simulation Results" on page 329

AT310_UMU_E0
"Making Coverage Predictions Using Simulation Results" on page 329.
6.3.5.1 Making an AS Analysis of Simulation Results

The Point Analysis window gives you information on reception for any point on the map. The AS Analysis tab gives you informa on on the pilot quality (Ec I0) (which is the main parameter used to define the mobile ac ve set), the connec on status,
and the active set of the probe mobile. Analysis is based on the UL load percentage and the DL total power of cells. In this
case, these parameters can be either outputs of a given simulation, or average values calculated from a group of simulations.
The analysis is provided for a user-definable probe receiver which has a terminal, a mobility and a service.
For information on the criteria for belonging to the active set, see "Conditions for Entering the Active Set" on page 418.
Before you make an AS analysis:
Ensure the simulation or group of simulations you want to use in the AS analysis is displayed on the map.
Replay the simulation or group of simulations you want to use if you have modified radio parameters since you made
the simulation.
The AS analysis does not take possible network saturation into account. Therefore, there
is no guarantee that a simulated mobile with the same receiver characteristics can verify
the point analysis, simply because the simulated network may be saturated.
To make an AS analysis of simulation results:

) on the toolbar. The Point Analysis window appears. (see Figure 6.13).
2. Select the AS Analysis view at the top of the Point Analysis window.
3. At the top of the AS Analysis view, select the simulation or group of simulations you want to base the AS analysis on
from the Load Conditions list.
4. Select the Terminal, Service, and Mobility.
5. Click the Options button (
) to display the Calculation Options dialogue.
6. Select or clear the following options:

-
Whether shadowing is to be taken into account (and, if so, the cell edge coverage probability).
Whether indoor coverage is to be taken into account.
Whether downgrading is allowed.
7. Click OK to close the Calculation Options dialogue.

8. Move the pointer over the map to make an active set analysis for the current location of the pointer.
As you move the pointer, Atoll indicates on the map which is the best server for the current position (see Figure 6.31
on page 266).
Information on the current position is given on the AS Analysis tab of the Point Analysis window. See Figure 6.32 on
page 266 for an explanation of the displayed information.
6.3.5.2 Making Coverage Predictions Using Simulation Results

When no simulations are available, Atoll uses the UL load factor, the DL total power, the UL reuse factor, the available HSDPA
power, the number of HSDPA users, the number of HSUPA users, and the UL load factor due to HSUPA defined for each cell
to make coverage predictions. For information on cell properties, see "Creating or Modifying a Cell" on page 210; for information on modifying cell properties, see "Cell Definition" on page 205.
Once you have made simulations, Atoll can use this information instead of the defined parameters in the cell properties to
make coverage predictions where each pixel is considered as a probe user with a terminal, mobility, profile, and service. For
each coverage prediction based on simulation results, you can base the coverage prediction on a selected simulation or on a
group of simulations, choosing either an average analysis of all simulations in the group or a statistical analysis based on a
defined probability. To be able to base a coverage prediction on a simulation or group of simulations, the simulation must
have converged.
The coverage predictions that can use simulation results are:
Coverage predictions on the pilot or on a service:
329

Handoff Zones: For information on making a Handoff Zones, see "Making a Handoff Status Coverage Prediction"
on page 264.
An HSDPA prediction to analyse A-DPCH qualities, HS-SCCH power or quality per HS-SCCH channel and to model fast
link adaptation.
-
Coverage by Total Noise Level (DL): For information on making a coverage by total noise level, see "Studying the
Total Noise Level on the Downlink" on page 261.
Pilot Pollution Analysis: For information on making a coverage by pilot polluter, see "Calculating Pilot Pollution"
on page 262.
A handover status coverage prediction to analyse macro-diversity performance:

-
Pilot Quality Analysis: For information on making a pilot quality analysis, see "Making a Pilot Signal Quality Prediction" on page 256.
Service Area Analysis Downlink: For information on making a coverage prediction on the downlink service area,
see "Studying Service Area (Eb Nt) Downlink or Uplink" on page 258.
Service Area Analysis Uplink: For information on making a coverage prediction on the uplink service area, see
"Studying Service Area (Eb Nt) Downlink or Uplink" on page 258.
Effective Service Area Analysis (Eb/Nt) (DL+UL): For information on making a effective service area analysis, see
"Studying the Effective Service Area" on page 259.
Coverage predictions on noise and interference:

-
Forsk 2011
HSDPA Quality and Throughput Analysis: For information on making an HSDPA coverage prediction, see "HSDPA
Quality and Throughput Analysis" on page 267.
An HSUPA predictions prediction to analyse the required E-DPDCH Ec/Nt, the required terminal power, and the
obtained HSUPA bearer.
-
HSUPA Quality and Throughput Analysis: For information on making an HSUPA coverage prediction, see "HSUPA
Quality and Throughput Analysis" on page 269.
The procedures for the coverage predictions assume that simulation results are not available. When no simulations are available, you select "(Cells Table)" from the Load Conditions list, on the Conditions tab. However, when simulations are available
you can base the coverage prediction on one simulation or a group of simulations.
To base a coverage prediction on a simulation or group of simulations, when setting the parameters:
2. From the Load Conditions list, select the simulation or group of simulations on which you want to base the coverage
prediction.
3. If you select a group of simulations from the Load Conditions list, select one of the following:
-
All: If you select All to make a statistical analysis of all simulations based on the defined Probability (the probability
must be from 0 to 1). This will make a global analysis of all simulations in a group and with an evaluation of the
network stability in terms of fluctuations in traffic.
Average: Select Average make the coverage prediction on the average of the simulations in the group.
6.4 Optimising Network Parameters Using the ACP

Atoll Automatic Cell Planning (ACP) enables radio engineers designing UMTS networks to automatically calculate the optimal
network settings in terms of network coverage and capacity. Atoll ACP can also be used in co-planning projects where UMTS
networks must both be taken into consideration when calculating the optimal network settings. Coverage maps are used for
the optimisation process, however, traffic maps can be used for weighting network load distribution.
Atoll ACP is primarily intended to improve existing network deployment by reconfiguring the main parameters that can be
remotely controlled by operators: antenna electrical tilt and cell pilot power. ACP can also be used during the initial planning
stage of a UMTS network by enabling the selection of the antenna, and its azimuth, height, and mechanical tilt. ACP not only
takes transmitters into account in optimisations but also any repeaters and remote antennas. ACP also enables you to select
to select which sites can be added or removed to improve existing or new networks.
Atoll ACP can also be used to measure and optimise the EMF exposure created by the network. This permits the optimisation
of power and antenna settings to reduce excessive EMF exposure in existing networks and optimal site selection for new
transmitters.
330
"The ACP Module and Atoll" on page 331

"Configuring the ACP Module" on page 335
"Optimising Cell Planning with the ACP" on page 338
"Running an Optimisation Setup" on page 362

AT310_UMU_E0
"Working with Optimisations in the Explorer Window" on page 364

"Viewing Optimisation Results" on page 365.
6.4.1 The ACP Module and Atoll

Atoll ACP can be used either with existing networks or with networks in the initial planning phases. With existing networks, it
is most efficient to focus on tuning the parameters that can be easily changed remotely, for example:
Antenna electrical tilt: ACP adjusts the electrical tilt by selecting the best antenna from the antenna group assigned
to this transmitter.
Pilot power for each cell: The pilot power is set within a defined minimum and maximum value for each cell.
When optimising a network that is still in the planning phase, Atoll ACP can calculate how the network can be improved by:
Selecting the antenna type for each transmitter: ACP selects the best antenna from the antenna group assigned to
this transmitter.
Changing the antenna azimuth: ACP sets the antenna azimuth using a defined range on either side of the currently
defined azimuth.
Changing the mechanical tilt of the antenna: ACP sets the mechanical tilt using a defined range on either side of the
currently defined mechanical tilt.
Changing the height of the antenna: ACP sets the optimal antenna height using a defined range on either side of the
currently defined antenna height.
Selecting sites: ACP adds or removes sites that you have indicated as candidates for addition or removal in order to
improve existing or new networks.
"Using Zones with ACP" on page 331

"Using Traffic Maps with ACP" on page 332
"Shadowing Margin and Indoor Coverage" on page 332
"ACP and Antenna Masking" on page 333
"EMF Exposure" on page 334.
6.4.1.1 Using Zones with ACP

ACP uses different zones during the optimisation process for different purposes.
ACP uses the computation zone to define the area where the quality objectives are evaluated. It also uses the computation
and focus zones to quickly select the sites which are optimized, although you can also optimise transmitters and sites that are
outside the computation or focus zone. All sites and transmitters in the network, including those outside the computation and
focus zones are taken into consideration when calculating signal, interference, and best server status.
ACP enables you to define different targets and different weights for each zone: for the computation zone, for the focus zone,
for the hot spots, and for each clutter classes.
6.4.1.1.1
"Using the Computation Zone and the Focus Zone" on page 331
"Using Custom Zones" on page 332
"Using the Filtering Zone" on page 332.
Using the Computation Zone and the Focus Zone

Atoll ACP measures the quality objectives within the computation zone. If there is no computation zone, the ACP measures
the quality objectives using a rectangle that includes all cells in the network. You can also use the computation or focus zone
to quickly select which cells are to be optimised, although you can also optimise either cells outside of the zones or a subset
of cells within a zone.
Atoll ACP allows you to define different targets for the computation zone and the focus zone, as well as for any custom zones.
You can also define different weights for each zone.
It is recommended to define a computation zone. ACP uses the computation zone as the
area in which the quality figures are calculated and improved during optimisation. Additionally, the zone defined by ACP might take into account areas outside of actual traffic
boundaries.
331

6.4.1.1.2
Forsk 2011
Using Custom Zones

Atoll ACP also allows you to use custom zones, enabling you to specify different quality targets for each custom zone and
display final results per zone. You can also define different weights for each zone. You can use the hot spots defined in the
Atoll document, import ArcView SHP files to create hot spots, or you can create custom zones based on clutter classes.
6.4.1.1.3
Using the Filtering Zone

If there is a filtering zone defined, Atoll ACP will optimise all currently defined and active cells selected by the filtering zone.
Cells that are locked will not be optimised. However, all cells will be used to model coverage and interference.
ACP automatically considers all the cells that have an effect on the computation or focus
zone, and ignores the rest (for example, cells that are too far away to have an impact on
the selected cells). It is nonetheless recommended to use a filtering zone to speed up initial
data extraction from the Atoll document.
6.4.1.2 Using Traffic Maps with ACP

Atoll ACP can use traffic maps to determine the traffic density on each pixel. The traffic density is used to weight each of the
quality figures according to traffic and to put more emphasis on high traffic areas. You can set traffic weighting separately for
each quality indicator. For example, you can use a uniform map for RSCP and a trac-weighted map for Ec Io. The calcula on
for network quality always uses traffic maps if they are present.
Figure 6.43: ACP traffic parameters

When you use selected traffic maps, ACP allows you to define a resolution to extract the data from traffic maps. The resolution
should usually be the same as the resolution of the traffic maps. To increase the accuracy of the data-extraction process, you
can increase the resolution defined in the Resolution (m) text box.
In the ACP, each traffic map is converted into one or more traffic profiles. A traffic profile is a combination of:
a service, terminal, and mobility

a traffic distribution
a relative load (expressed in Erlangs).
For the moment, traffic profiles are only used to evaluate the traffic weighting to apply to
each pixel (by adding the load-scaled traffic distribution on each traffic profile). This information will also be used in the future to better manage cell load (and the evaluation of
network quality).
6.4.1.3 Shadowing Margin and Indoor Coverage

Atoll ACP enables you to take indoor coverage and a shadowing margin into consideration. When indoor coverage is taken
into consideration, all pixels marked as indoors have an additional indoor loss added to total losses. The indoor loss is defined
per clutter class.
When the shadowing margin is taken into consideration, the defined shadowing margin is taken into consideration in the
calculation of the received useful signal power and interfering signal power.
For more information on how shadowing and macro-diversity gains are calculated, see the Technical Reference Guide.
332

AT310_UMU_E0
You can set ACP to not take macro-diversity gains into consideration by setting the appropriate option in the acp.ini file. You will need to update the corresponding parameters in
the atoll.ini file as well. For information on modifying the atoll.ini file, see the Administrator Manual.
6.4.1.4 ACP and Antenna Masking

When ACP performs any type of antenna reconfiguration, it must determine how attenuation to the path loss changes when
the antenna is modified. ACP determines changes to path loss attenuation using antenna masking. Depending on the propagation model used to calculate the path loss matrices, ACP supports the following antenna masking methods:
Natively supported propagation models: ACP calculates the change in attenuation by unmasking the current antenna
pattern and then remasking it with the new antenna pattern. Because ACP is using the same propagation model as
was used to calculate the original path loss matrices, the results are consistent and accurate. For this reason, using
natively supported propagation models is the preferred method.
For more information, see "Natively Supported Propagation Models" on page 333.
ACPs default antenna masking method: If the propagation model used to calculate the original path loss matrices is
not supported by ACP, ACP can use its own default antenna masking method. Because the ACP default masking
method is not the same as the one used to calculate the original path loss matrices, accuracy cannot be guaranteed.
ACPs default masking method gives results similar to Atolls Standard Propagation Model and should deliver acceptable results for any macro-type propagation model.
For more information, see "ACPs Default Antenna Masking Model" on page 333.
Precalculated path loss matrices: ACP can precalculate either the full path loss matrices for a selected propagation
model or the angles of incidence for any propagation model that supports it.
For more information, see "Precalculated Path Loss Matrices" on page 334.
Pilot power optimisation and site selection (without reconfiguration) are made independently of the method used to determine changes to path loss attenuation.
6.4.1.4.1
Natively Supported Propagation Models

During antenna optimisation, ACP must calculate how the attenuation to the path loss changes when the antenna is modified,
i.e., when the antenna type, tile, or azimuth is modified.
When ACP uses natively supported propagation models, it calculates the change in attenuation by unmasking the current
antenna pattern and then remasking it with the new antenna pattern. The unmasking and remasking operations are strongly
dependent on the propagation model that was used to calculate the path losses, especially to:
Find the horizontal and vertical emission angles between a transmitter and the receiving pixel. The angles depend
strongly on the radial method used to account for the height profile between the transmitter and receiver.
Find the correct antenna gain for a given set of horizontal and vertical emission angles. The gain is usually based on a
3-D interpolation of the 2-D patterns and can be model-dependent.
How ACP calculates attenuation depends on the propagation model used by Atoll to generate the path loss. The propagation
model parameters which affect processing are automatically extracted by ACP. ACP supports the propagation models
commonly used in Atoll.
The raster data needed by ACP depends on the propagation model that Atoll used to generate the path loss.
6.4.1.4.2
Propagation Model
Raster Data Required
All Atoll Hata-based propagation models (Cost-Hata,

Okumura-Hata, ITU, etc.)
DEM file
Atoll Standard Propagation Model
DEM file
Clutter Height file (optional)
Clutter file (optional)
All other models.
DEM file
ACPs Default Antenna Masking Model

ACP has an internal default antenna masking model that can be used if the propagation model used to calculate the original
path loss matrices is not supported by ACP. Because the ACP default antenna masking model can deliver different results than
333

Forsk 2011
those given by the original propagation model, accuracy can not be guaranteed, although it should deliver acceptable results
for any macro-type propagation model.
ACP offers a few parameters that enable you to improve the accuracy of the default antenna masking model:
Use Clutter Height: By selecting Use Clutter Height, ACP will take into consideration clutter height information from
the clutter heights file, if available, or from the clutter classes file.
Receiver on Top of Clutter: If the receiver is on top of the clutter, for example, if receivers are located on top of buildings, you can select Receiver on Top of Clutter. The receiver height will then be sum of the clutter height and the
receiver height.
Use Radial Method: You can select the Use Radial Method check box if you want ACP to use the radial method to
extract the profile between the transmitter and the receiver.
Direct View: You can select the Direct View check box if you want ACP to trace a direct line between the transmitter
and the receiver when calculating the vertical incidence angle, without taking any obstacle into account.
Antenna Masking Method: You can select either the native 3D interpolation method or the linear interpolation
method as the type of Antenna Masking Method ACP uses.
These parameters can be set individually for each propagation model for which ACP will use the default propagation method.
6.4.1.4.3
Precalculated Path Loss Matrices

After the ACP setup has been created, ACP calculates the path loss matrices necessary (i.e., for sites that are being optimised
and do not use natively supported propagation models or the ACP's internal model) while the optimisation is loading.
ACP does not calculate all path loss matrices for all possible combinations, for example, five possible changes in electrical tilt
and five possible changes in azimuth, i.e., 25 path loss matrices to be calculated. ACP only calculates the path loss matrices
for the changes which need to be evaluated by the optimisation algorithm. By pre-calculating only the changes to be evaluated, ACP reduces the number of path loss changes to be calculated and reduces the calculation time.
While the optimisation is running, ACP uses the pre-calculated path loss matrices. If a change is made to a transmitter that
was not taken into the consideration when the path loss matrices were calculated, ACP recalculates the path loss matrix for
that change only.
The end result are considerable savings in both time and computer resources.
For information on natively supported propagation models, see "Natively Supported Propagation Models" on page 333.
Although ACP minimises the number of calculations necessary when using precalculated path loss matrices, it is recommended to:
Use precalculated path loss matrices only when necessary. When a propagation model is natively supported, you
should use it. Even if a propagation model is not officially natively supported, using the default antenna masking
method is often sufficient.
Try to limit the number of parameters covered, when using precalculated path loss matrices. For example, only use a
2- or 3-azimuth span. Carefully designing the antenna groups will also reduce the number of unnecessary calculations.
Use a temporary path loss storage directory dedicated to your document region when using precalculated path loss
matrices. This ensures that future optimisations on this region will be able to use these path losses that have already
been calculated.
6.4.1.5 EMF Exposure

EMF exposure is defined as the total electromagnetic field measured at a given location. Although the exact limit on the
acceptable level of EMF exposure varies by jurisidic on, it is typically a few V m. Using an internal propaga on model specific
to EMF exposure, ACP calculates the EMF exposure in two dimensions (for open areas such as parks or roads) or in three
dimensions (for buildings). Additionally, with buildings, you can choose to measure the exposure only at the front faade,
where the EMF exposure will be the greatest.
The internal propagation model calculates EMF exposure using propagation classes which are retrieved from input files. Each
propagation class is either opaque, meaning that the signal experiences diffraction losses at the edge of the object but does
not go completely through, or transparent, meaning that the signal passes through it (with perhaps some losses) and does not
experience diffraction loss. The propagation classes have the following parameters:
334
Penetration loss (dB): The loss occuring when the signal enters the object.
Linear loss (dB/m): A linear loss applied for each meter within an object. The loss is applied only after a given number
of meters, specified by the "Linear loss start distance (m)" parameter.
Distribution of measurement points: Field strength measurements are made on a set of points within an object. The
measurement points can be distributed in either a 3D pattern or in a 2D pattern. For a two-dimensional distribution,
the points can be placed either at the bottom (for example, in a park) or at the top (for example, for a bridge) to better
reflect where people will be.

AT310_UMU_E0
The following default propagation classes are provided:
Open: The Open propagation class is for areas without obstacles, such as an open area or water. An open area can
also be an elevated area such as a bridge. Such areas are transparent, with no diffraction loss.
Vegetation: The Vegetation propagation class is used for areas covered with vegetation, such as parks. They can be
considered as transparent but with a certain degree of diffraction loss.
Building: The Building propagation class is used for opaque objects such as buildings. The signal experiences some loss
when going through and also suffer from diffraction loss.
6.4.2 Configuring the ACP Module

You can change the default settings of the Atoll ACP module so that selected options are the default settings each time you
run ACP. Additionally, you can base the default ACP settings on some or all of the settings of a given Atolloptimisation.
"Defining the Storage Location of ACP Settings" on page 335

"Defining the Antenna Masking Method" on page 335
"Configuring the Default Settings" on page 337
"Configuring Setup-specific Settings" on page 337.
6.4.2.1 Defining the Storage Location of ACP Settings

You can define where Atoll stores the default settings of the ACP module.
To configure the default settings of the ACP module:
2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears.
3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears.
4. Click the Setup Template tab. The location of the settings are either embedded in the Atoll document or stored in an
acp.ini file.
5. Click the arrow to the right of the current location of the ACP settings (
). The menu appears:
6. Select where you want the ACP to store the template options:
-
Embedded: Atoll will store the ACP settings in the current Atoll document.
Default User Location: Atoll will store the ACP settings in the default location for user configuration files.
Browse: Clicking Browse enables you to select a location to store the acp.ini file.
6.4.2.2 Defining the Antenna Masking Method

You can define how Atoll ACP calculates path loss matrices, using either Atolls propagation models, ACPs internal propagation model, or precalculated path loss matrices. These parameters will be applied to all new and duplicated setups.
To define how ACP calculates path loss matrices:
4. Click the Setup Template tab.
5. Click Antenna Masking Method in the left-hand pane. Under Antenna Masking Method, you can define how ACP calculates path loss matrices (see Figure 6.44).
335

Forsk 2011
Figure 6.44: The Antenna Masking Model tab

6. Under Propagation Models, select the check boxes in each column to define how ACP will model each propagation
model.
By default, all available propagation models are displayed. By selecting the Show only
used propagation models check box, ACP will only display the propagation models that
are actually used in that document.
-
Antenna masking method: The antenna masking method column indicates whether ACP can use this propagation
model natively ("Native"), or whether ACP uses its own default antenna masking method ("Default"). If you want,
you can set ACP to use a precalculated mode for each propagation model from the list:
-
Incidence: Select Incidence if you want ACP to only calculate the angles of incidence for this propagation model.
Full path loss: Select Full path loss if you want ACP to calculate full path loss matrices for this propagation
model.
Use clutter height: Select the check box in the Use clutter height column if you want ACP to take clutter height
information from the clutter heights file, if available, or from the clutter classes file. This option is only available if
ACP is using its default antenna masking method
Receiver on top of clutter: Select the check box in the Receiver on top of clutter column if you want the receiver
height to be sum of the clutter height and the receiver height. This option can be used, for example, to model
receivers on top of buildings.
Use radial method: Select the check box in the Use radial method column if you want ACP to use the radial
method to extract the profile between the transmitter and the receiver. Using the radial method improves efficiency.
Additional Parameters: In the Additional Parameters column, a Browse button (
) appears for each propagation model not supported natively for ACP. Click the Browse button to open the Default Propagation Model
Parameters dialogue. In the Default Propagation Model Parameters dialogue, define the following parameters
for each propagation model for which ACP uses its default method:
-
Direct View: Select the Direct View check box if you want ACP to trace a direct line between the transmitter
and the receiver when calculating the vertical incidence angle, without taking any obstacle into account.
Antenna Masking Method: Select either the native 3D interpolation method or the linear interpolation
method as the type of Antenna Masking Method ACP uses. When you select the linear interpolation method,
you can also define the degree of smoothing applied.
7. Click OK.
336

AT310_UMU_E0
6.4.2.3 Configuring the Default Settings

You can configure default settings for Atoll ACP that are used for each ACP setup.
1. Click the Data tab in the Explorer window.
4. Select the Setup Template tab. On the Setup Template tab, you can set options that are normally set in the ACP.ini
file for the following categories:
-
EMF Exposure
Optimisation
Objective
Reconfiguration.
For information on the various options and their possible values, see the Administrator Manual.
6.4.2.4 Configuring Setup-specific Settings

You can configure default settings for Atoll ACP that are used for each ACP setup.
1. Click the Data tab in the Explorer window.
4. Select the Setup Template tab. On the Setup Template tab, you can set options that are normally set in the ACP.ini
file for the following categories:
-
EMF Exposure
Optimisation
Objective
Reconfiguration.
For information on the various options and their possible values, see the Administrator Manual.
5. Click the User Preferences tab (see Figure 6.45).
Figure 6.45: Setting ACP user preferences

Under Setup Preferences: You can define the following settings:
-
Enable EMF exposure module: Select the Enable EMF exposure module check box if you want the ACP to display
the options related to EMF exposure. When you have selected the Enable EMF exposure module check box, you
will still have to select the option on the Optimisation tab of the Setup dialogue and define the EMF exposure
options if you want to optimise the EMF exposure.
Calculation setting: Adjust the slider to define whether you want ACP to provide its results more quickly, at the
expense of precision, or whether you want ACP to provide more accurate results, at the expense of speed. By
selecting a higher speed, you will cause ACP to reduce the number of cells monitored for each pixel, some of which
337

Forsk 2011
might only create a bit of interference at first, but which could possibly create significantly more interference after
antenna parameters are changed during the optimisation process. Selecting a higher precision avoids this problem
at the expense of more time and computer resources.
Under Result Preferences: You can define the following setting for report maps:
-
Default map transparency: Define the default map transparency with the slider.
6. Click the Private Directory tab. On the Private Directory tab (see Figure 6.46), you can define the directory to be used
by the ACP to store precalculated path loss matrices as well as the path loss matrices for antenna height optimisation.
Figure 6.46: Defining the directory for path loss matrices

7. Enter the name of the directory or click the arrow to the right of the current directory (
directory.
) to navigate to the new
8. Click OK to save your changes.

When the propagation model used is not one natively supported by ACP, for example, complex ray-tracing propagation
models, ACP can use precalculated path loss matrices to calculate attenuation.
For more information, see "Defining the Antenna Masking Method" on page 335.
6.4.3 Optimising Cell Planning with the ACP

Optimising cell planning with the Atoll ACP consists of defining the parameters that will be used during the optimisation process and then running the process. Each optimisation, with its parameters and results, is stored in a Setup folder in the ACP Automatic Cell Planning folder on the Network tab of the Explorer window.
"Creating an Optimisation Setup" on page 338

"Defining Optimisation Parameters" on page 339.
6.4.3.1 Creating an Optimisation Setup

In ACP, you can create an optimisation setup either by creating and running a new one, or by duplicating or opening an existing
optimisation, editing the parameters, and then running it.
"Creating a New Optimisation Setup" on page 338

"Running an Existing Optimisation Setup" on page 339
"Duplicating an Existing Optimisation Setup" on page 339.
Creating a New Optimisation Setup

To create a new optimisation setup:
3. Select New from the context menu. A dialogue appears in which you can set the parameters for the optimisation
setup.
338

AT310_UMU_E0
For information on the parameters available, see "Defining Optimisation Parameters" on page 339.
4. After defining the optimisation setup:
-
Click the Run button to run the optimisation immediately. For information on the optimisation results, see
"Viewing Optimisation Results" on page 365.
Click the Create Setup button to save the defined optimisation. For information on running the optimisation, see
"Running an Existing Optimisation Setup" on page 339.
Running an Existing Optimisation Setup

To run an existing optimisation setup:
2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder.
3. Right-click the optimisation you want to run. The context menu appears.
-
Select Run from the context menu to run the optimisation immediately. For information on the optimisation
results, see "Viewing Optimisation Results" on page 365.
Select Properties from the context menu to view or modify the parameters of the optimisation setup. For information on the parameters available, see "Defining Optimisation Parameters" on page 339.
Duplicating an Existing Optimisation Setup

To duplicate an existing optimisation setup:
3. Right-click the setup you want to duplicate. The context menu appears.
4. Select Duplicate from the context menu. The ACP Duplicate Options dialogue appears.
5. Under Data Synchronisation Option, select one of the following:
-
Partial update: The duplicated ACP setup will have only the data that was changed by the ACP during optimisation.
Duplicating the ACP-generated data permits you to create a new setup with up-to-date data even though the data
of the original setup is no longer valid.
Full update: The duplicated ACP setup will have all the data resynchronised from the database.
6. Run the existing optimisation setup as described in "Running an Existing Optimisation Setup" on page 339.
6.4.3.2 Defining Optimisation Parameters

In Atoll ACP, when you create a new optimisation setup, you must first define all the parameters. You can also modify the
parameters of an existing optimisation setup before running it. Creating a new optimisation setup is explained in "Creating a
New Optimisation Setup" on page 338. Running an existing optimisation is explained in "Running an Existing Optimisation
Setup" on page 339.
The optimisation parameters are grouped onto specific tabs of the dialogue. The parameters are the same whether you create
a new optimisation setup or whether you modify the parameters of an existing one.
In this section, the following parameters are explained:
6.4.3.2.1
"Setting Optimisation Parameters" on page 339

"Setting Objective Parameters" on page 345
"Setting Network Reconfiguration Parameters" on page 349
"Defining Site Selection Parameters" on page 354
"Defining Antenna Groups" on page 358
"Adding Comments to the Optimisation Setup" on page 362.
Setting Optimisation Parameters

The Optimisation tab allows you to define the various parameters related to the optimisation algorithm.
To set the optimisation parameters:
1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 338.
2. Click the Optimisation tab (see Figure 6.47).
339

Forsk 2011
Figure 6.47: The Optimisation tab

3. Define the following:
-
Number of Iterations: Set the number of iterations for the optimisation algorithm. ACP calculates a suggested
number of iterations by multiplying the total number of parameters to optimise (i.e., cell pilot power, antennas,
azimuth, mechanical tilt, antenna height, sites subject to selection) by two. You can accept the number of iterations, or set your own value. Often one-half or one-quarter of the suggested number is sufficient for ACP to find
the optimal configuration.
Resolution (m): Specify the resolution for the optimisation. Each criterion will be evaluated on each of these
pixels. The total number of pixels and the average number per site is indicated. This parameter has a large influence on the accuracy and speed of the optimisation process. You should either set a resolution that is consistent
with the path loss and raster data in the Atoll document, or you should set a resolution that will result in between
300 and 3000 positions per site.
4. Under Setup, you can set the following optimisation-related objectives and parameters:
-
"Defining Layer-related Objectives and Parameters" on page 340

"Defining Zone-related Objectives and Parameters" on page 341
"Defining Cost Control-related Objectives and Parameters" on page 342
"Defining Site Classes for Cost Control" on page 343
"Defining EMF Exposure-related Objectives and Parameters" on page 343.
Defining Layer-related Objectives and Parameters

On the Optimisation tab of the ACP Setup dialogue, you can define objectives and parameters related to radio layers of the
current project.
To define layer-related objectives and parameters:
2. Click the Optimisation tab (see Figure 6.47 on page 340).
3. In the pane on the left-hand side, click Layers.
Under Layers (see Figure 6.47 on page 340), you can define the following for each layer to be optimised:
-
Use: You can select which layers are to be considered in the optimisation process by selecting their check box in
the Use column. The signals and interference of the transmitters and sites in the selected layers will be taken into
consideration during the optimisation process. If the transmitters and sites in the selected layers are within the
area to be optimised (the computation zone or the focus zone, as selected under Zones on the Optimisation tab),
these transmitters and cells will be optimised.
Selecting layers to be taken into consideration is most useful when you want to take the signal and interference
of several layers into consideration, but only want to optimise one of the layers. Selecting the layers here ensures
that ACP will take them into consideration. Transmitters and sites in layers which are not selected are treated by
340

AT310_UMU_E0
ACP as if they do not exist: they will not be optimised and their signal and interference will not be taking into consideration during the optimisation of the selected transmitters and sites.
If a transmitter on one selected layer that is optimised is linked with a transmitter on
another selected layer that is not optimised, the second transmitter will still appear on the
Reconfiguration tab and any changes to the first transmitter will be applied to the linked
transmitter as well.
-
Name: You can change the name of the layer by clicking it and entering a new name.
Reconfiguration: If you want the layer to be taken into consideration for reconfiguration, you can select the check
box in the Reconfiguration column.
Site Selection: If you want the layer to be taken into consideration for site selection, you can select the check box
in the Site Selection column.
The following columns give information about the layer; they can not be edited:
-
Technology: The technology (UMTS in this case) used by the layer.

Freq. Band/Carrier: The frequency band and carrier (if applicable) used by the layer.
Nb Tx/Cell: The number of sectors in the layer.
Defining Zone-related Objectives and Parameters

On the Optimisation tab of the ACP Setup dialogue, you can define objectives and parameters related to the computation and
focus zones as well as the hot spot zones of the current project.
To define zone-related objectives and parameters:
3. In the pane on the left-hand side, click Zones.
Under Zones (see Figure 6.48), you can define how the zones will be used during optimisation. The zones are used to
define geographical objectives and weighting. The zones are taken into consideration in the following order: the hot
spots zones in their defined order, the focus zone, and finally the computation zone.
-
Filtering Zones: Select the Computation Zone check box to preselect the sectors in the computation zone and the
Focus Zone check box to preselect the sectors in the focus zone. If there is no focus zone in the project to be optimised, the computation zone is automatically selected. You can always manually reconfigure sectors outside the
selected zone on the Reconfiguration tab.
Hot Spots: For each new hot spot, enter a Name in the row marked with the New Row icon (
) and click the
Browse button (
) to open the Zone Definition dialogue. You can import an ArcView SHP file by selecting From
file and clicking the the Browse button (

). Or, you can use an existing hot spot zone in the Atoll document by
selecting From hot spot and selecting the hot spot zone from the list. Or, you can create a hot spot zone composed
of all areas in the reconfiguration zones that are included in one or more clutter class by selecing From clutter
classes and selecting the check box corresponding to the clutter class or classes you want to study.
Figure 6.48: The Zone Definition dialogue

You can change the order in which the hot spots will be taken into consideration, by clicking the layers number in
the Order column and then clicking the Up button (
) or the Down button (
).
341

Forsk 2011
Figure 6.49: Configuring zones on the Optimisation tab

Defining Cost Control-related Objectives and Parameters
On the Optimisation tab of the ACP Setup dialogue, you can define objectives and parameters related to cost control.
To define zone-related objectives and parameters:
3. In the pane on the left-hand side, click Cost Control.
Under Cost Control (see Figure 6.50), you can define how the costs will be calculated for each optimisation option.
ACP will use the defined costs to calculate the optimisations that are the most cost-effective. You can select three
types of cost control:
-
No cost control: If you select No cost control, ACP will not take cost into consideration when optimising the network.
Maximum cost: If you select Maximum cost, you can enter a maximum cost not to be exceeded and define the
costs under Cost Setting.
Quality/Cost trade-off: If you select Quality/Cost trade-off, ACP will find a compromise between cost and quality.
You can use the slider to define whether ACP should put more emphasis on quality (Low) or cost (High).
Figure 6.50: Configuring costs on the Optimisation tab

-
342
In the Reconfiguration Cost section, under Cost Setting, define the individual costs for each reconfiguration
option. If reconfiguring an option can only be done at the physical location of the transmitter, select the check box
in the Site Visit column. The cost will be increased by the defined Site Visit value. The site visit cost is incurred only
once per site, independently of the number of reconfigurations that might be made to the same site, including
sites supporting more than one technology.
In the Site Selection Cost section, under Cost Setting, define the individual costs for each site selection option.

AT310_UMU_E0
Defining Site Classes for Cost Control

On the Optimisation tab of the ACP Setup dialogue, you can create and define site classes. By setting different costs for each
site class and assigning each site to a class, ACP can calculate costs that reflect more realistically the actual costs of each site.
To create and define site classes:
3. In the pane on the left-hand side, click Cost Control.
Under Cost Control (see Figure 6.50), you can create site classes and define how the costs will be calculated for each
optimisation option and each class. ACP will use the defined costs to calculate the optimisations that are the most
cost-effective.
To define the costs for a site class:
a. Click the arrow beside the Site Classes list and select a site class.
b. Define the individual costs for each reconfiguration option as explained in "Defining Cost Control-related Objectives and Parameters" on page 342.
To create a site class:
a. Click the New Site Class button (
). The New Site Class dialogue appears.
b. Enter the name for the site class and click OK. The new site class now appears in the list of site classes.
c. Define the individual costs for each reconfiguration option of the new site class as explained in "Defining Cost Control-related Objectives and Parameters" on page 342.
To delete a site class:
a. Click the arrow beside the Site Classes list and select the site class you want to delete.
b. Click the Delete Site Class button (
fault" site class.
). The selected site class is immediately deleted. You can not delete the "De-
ACP will not ask you to confirm your decision, so ensure that you have selected the
correct site class before clicking the Delete Site Class button.
Defining EMF Exposure-related Objectives and Parameters

On the Optimisation tab of the ACP Setup dialogue, you can set the parameters necessary to measure and optimise the EMF
exposure caused to the network.
The EMF Exposure section of the Optimisation tab is only available if you have selected the Enable EMF exposure module
check box on the User Preferences tab of the ACP Properties dialogue. For more information on setting the properties of the
ACP module, see "Configuring Setup-specific Settings" on page 337.
To define EMF exposure parameters:
3. In the pane on the left-hand side, click EMF Exposure.
Under EMF Exposure, you can define the parameters used to optimise EMF exposure.
343

Forsk 2011
Figure 6.51: Setting EMF exposure parameters

4. Under EMF Exposure, select the Enable EMF exposure calculation check box if you want the ACP to optimise EMF
exposure.
5. Use the EMF Exposure importance slider to define the importance of EMF exposure in comparison with the other optimisation objectives:
-
Low: EMF exposure is improved when doing so not have a strong adverse effect on coverage quality.
Medium: There is a trade-off between coverage quality and EMF exposure.
Critical: EMF exposure is improved at all costs, even if doing so has a strong adverse effect on coverage quality.
6. Under Distribution of Measurement Points, define how the measurement points will be distributed:
-
Resolution XY (m): Define in meters the horizontal resolution of the measurement points.
Resolution Z (m): Define in meters the vertical resolution of the measurement points (only for three-dimensional
EMF exposure analysis).
Building front only: Select the Building front only check box if you only want measurement points to be distributed on the building faade.
Indoor distance analysis (m): If you want measurement points to be distributed within the building (i.e., if the
Building front only check box is not selected), define the maximum distance up to which measurement points are
distributed inside the building.
Measurement on zone: Select the zone (computation, focus, or individual hot spot zone) on which measurement
points will be distributed and on which the EMF exposure will be optimised.
7. Under Raster and Vector Inputs, set the data that will be used to define the profile of the terrain:
-
File: Under File, click the Browse button (

) to select a file describing the terrain. The files must be ArcView
vector files (SHP). By default, the first entry in the File column is "Native clutter classes and clutter heights." If you
want to remove them completely from the table, select the Ignore clutter check box at the bottom of the dialogue.
Definition: Under Definition, click the Browse button (

) corresponding to the file in the File column to map
the files data to ACP propagation classes.
Used in Measurements: Select the Used in Measurements check box for each entry in the File column that you
want to use for EMF exposure optimisation.
Once you have defined the EMF exposure parameters, you can back up the configuration
by clicking the Back Up Configuration button. In future ACP sessions, the same parameters
will be applied automatically
8. In the pane on the left-hand side, click Propagation under EMF Exposure.
Under Propagation, you can define the propagation classes used to optimise the EMF exposure , as well as additional
EMF exposure parameters.
344

AT310_UMU_E0
Figure 6.52: Defining propagation classes

9. Under Propagation Class Definition, set the following parameters for each propagation class. If you want to create a
new propagation class, enter the parameters in the row marked with the New Row icon (
).
-
Name: The name of the propagation class.

Distribution of Measurement Points: The pattern in which measurement points will be distributed in that propagation class. The measurement points can be distributed in either a 3D pattern (for a building, in which measurement points must be made vertically as well) or in a 2D pattern. For a two-dimensional distribution, the points can
be placed either at the bottom (for example, in a park) or at the top (for example, for a bridge) to better reflect
where people will be.
Penetration Loss (dB): Define the loss occuring when the signal enters the object.
Linear Loss (dBm): Define a linear loss applied for each meter within an object. The loss is applied only after a
given number of meters, specified by the Linear Loss Start Distance (m) parameter.
Linear Loss Start Distance (m): Define the distance after which the Linear Loss (dBm) is applied.
10. Under Parameters, define the following:

-
6.4.3.2.2
Use diffraction: This option is currently disabled. In other words, measurement points that are not in the line of
sight do not experience any diffraction loss.
Free space model (worst case): Select the Free space model (worst case) check box if you want the ACP to calculate the worst possible EMF exposure levels under the current conditions. When you select the Free space model
(worst case) check box, the ACP treats all objects (i.e., buildings, etc.) as fully transparent and no indoor loss is
applied.
Calculation radius (m): Define the maximum distance from a transmitter for which its EMF exposure contribution
is calculated.
Setting Objective Parameters

The Objectives tab allows you to define the various parameters related to the objectives of the optimisation. ACP allows you
to set different objectives for each layer selected in the Use column under Layers on the Optimisation tab. You can combine
the objectives per layer with boolean operators (AND, OR, or XOR). This enables you to build complex objectives combining
several conditions.
To set the objective parameters:
2. Click the Objectives tab (see Figure 6.53).
345

Forsk 2011
Figure 6.53: The Optimisation tab

3. Under Criteria, in the left-hand pane, under Objectives, click UMTS RSCP or UMTS EcIo to define the RSCP coverage
or EcIo coverage parameters, respectively.
-
Target Zone: Select the zone on which RSCP coverage or EcIo coverage is to evaluated.
Traffic Weighting: If you want define non-uniform traffic, click the Browse button (
) to open the Traffic Definition dialogue. In the Traffic Definition dialogue, you can select either Traffic generated from maps and select
the traffic maps or you can select Traffic generated from file and then click the Browse button (
) to select a
traffic map.
Weight: You can set the importance of the RSCP coverage or EcIo coverage objective by defining a weight. Giving
the RSCP coverage or EcIo coverage objective a weight of "0" means that ACP will not consider RSCP coverage or
EcIo coverage in determining the success of the optimisation.
4. Under Criteria, in the left-hand pane, under Objectives, click Condition under UMTS RSCP or UMTS EcIo to define how
ACP will calculate RSCP coverage or EcIo coverage.
-

-
), set the following parameters:
In the first column, select the boolean operator (AND, OR, or XOR) that will be used to combine the conditions.
Layer: In the Layer column, select the layer that the objective will be evaluated on.
Quality: In the Quality column, select the objective.
In the next column, select the operator (">" or "<") that will be used to evaluate the objective in relation to
the Threshold.
Threshold: In the Threshold column, enter the threshold to be used to evaluate the objective. Clicking the
Browse button (
) opens a dialogue where you can define in which zone the objective will be evaluated and
a threshold for each zone.
Each pixel can belong to more than one zone, however for each pixel the quality is only
measured according to the zone with the highest priority (i.e., first the hot spot, then the
focus zone, and finally the computation zone).
Once you have defined more than one condition under either UMTS RSCP or UMTS EcIo, you can combine them or
change the order in which ACP takes them into consideration.
-
You can combine conditions by selecting them and clicking the Group button. You can then select a boolean operator (AND, OR, or XOR) that will be used to combine the conditions with other defined conditions.
You can change the order in which ACP takes them into consideration by selecting the condition and clicking conditions by selecting them and and then clicking the Up button (
346
) or the Down button (
).

AT310_UMU_E0
5. Under Criteria, in the left-hand pane, under Objectives, click Target under UMTS RSCP or UMTS EcIo to define the
coverage target.
a. Enter a value for one of the following:
-
Improve Current Coverage (+- %): If you want to use an improvement of current coverage as the optimisation
target, enter the percentage by which the current coverage should be improved.
Target Coverage (%): If you want to use a target coverage (defined as a percentage of the target zone), enter
the percentage in Target Coverage (%).
If you want to use a coverage prediction, the coverage prediction must have already
been calculated.
6. If you want to filter the points on which the objective will be measured, click Advanced at the bottom of the dialogue.
-

-
), set the following parameters:
In the first column, select the boolean operator (AND, OR, or XOR) that will be used to combine the filter conditions.
Layer: In the Layer column, select the layer that the measurement points will be evaluated on.
Quality: In the Quality column, select the objective.
In the next column, select the operator (">" or "<") that will be used to evaluate the objective in relation to
the Threshold.
Threshold: In the Threshold column, enter the threshold to be used to evaluate the objective. Clicking the
Browse button (
) opens a dialogue where you can define in which zone the objective will be evaluated and
a threshold for each zone.
Once you have defined more than one filter condition, you can combine them or change the order in which ACP
takes them into consideration.
-
You can combine filter conditions by selecting them and clicking the Group button. You can then select a
boolean operator (AND, OR, or XOR) that will be used to combine the filter conditions with other defined conditions.
You can change the order in which ACP takes them into consideration by selecting the filter condition and
clicking filter conditions by selecting them and and then clicking the Up button (
(
) or the Down button
).
7. If you are optimising EMF exposure, under Criteria, in the left-hand pane, click EMF Exposure to set the importance
of the objectives.
Figure 6.54: Setting EMF exposure parameters

-
Select the check box in the Use column for each zone in the project that you want to be taken into consideration
in the EMF exposure optimisation.
Enter a Maximum Threshold (Vm) for each selected zone.
Define a Weight for each zone. Measurement points will be weighted according to the weight assigned to the zone
they are in. For example, if a zone has a weight of "2," then improving the EMF exposure by one measurement
point within this zone is of the same importance as improving the EMF exposure by two measurement points in a
zone with a weighting of "1."
It is important to remember that, if every zone is assigned the same weight, the
optimisation is made as if no weight is assigned to any zone. Defining a weight of "0" for
a zone means that that zone will not be taken into consideration when trying to reach
the set objectives.
347

Forsk 2011
8. Under Criteria, click Zone Weighting to set the importance of the objectives (see Figure 6.55).
Figure 6.55: Setting weighting options

9. Define the weight given to the computation zone, the focus zone, and any hot spot zone. With zone weighting, ACP
adds an extra weight to all the pixels of a zone. Because one pixel can belong to several zones (for example, a pixel can
be inside both the focus zone and the computation zone and in a hot spot zone, if there is one), the weight applied to
that pixel is the weight of the zone with the highest priority: the hot spot zone, if it exists, then the focus zone, finally
the computation zone.
It is important to remember that, if every zone is assigned the same weight, the
optimisation is made as if no weight is assigned to any zone. Defining a weight of "0" for
a zone means that that zone will not be taken into consideration when trying to reach
the set objectives.
Zone weighting is used to focus optimisation on the appropriate areas. The assigned weights are used to weight the
traffic parameters, unless the optimisation is based on uniform traffic. However, if no traffic maps are available or if
the optimisation is based on uniform traffic, zone weighting can be used to ensure that ACP prioritises the optimisation of areas of high traffic.
With multiple layers, you might have a layer that is restricted geographically (for example, the UMTS 900 layer might
only be available in rural areas). Because ACP always measures the quality target over the entire computation zone,
such a situation would lead to a measurement of poor quality in the urban areas, where there are no UMTS 900
sectors. By defining a weight of "0" outside of the rural area for this layer, you can restrict the measurement of coverage only to the part of the layer with UMTS 900 sectors. This way, the global target (90% of coverage for instance) is
measured in a meaningful way.
10. Under Criteria, in the left-hand pane under Parameters, click UMTS.
You can define the quality parameters for UMTS.
a. Under UMTS, select the Enable indoor coverage check box if you want all pixels to be considered as indoors when
the Enable indoor coverage check box is selected. The indoor loss per clutter class will be applied or, if no clutter
classes are available, a default value will be applied.
You can base the evaluation of the objectives on a calculated coverage prediction or on manual configuration. If you
base the coverage prediction settings on a calculated coverage prediction, ACP will use the ranges and colours defined
in the selected coverage prediction as the default for its own maps. However, if you have saved the display options of
an ACP map as default, or if you are using a configuration file for ACP, these defined ranges and colours will be used
as the default, overriding the settings in the selected coverage prediction. For information on setting ACP map display
options as the default, see "Changing the Display Properties of ACP Maps" on page 377. For information on saving a
configuration file, see "Configuring the Default Settings" on page 337.
If you want to use a coverage prediction, the coverage prediction must have already
been calculated.
b. Under UMTS in the left-hand pane under Parameters, select Overlap.

If you select Manual Configuration from the Base prediction settings on list, define an Overlap threshold margin.
It will be used for traffic maps.
c. Under UMTS in the left-hand pane under Parameters, select RSCP.
If you select Manual Configuration from the Base prediction settings on list, define the following options:
-
348
Select the Enable Shadowing Margin check box if you want to enable a shadowing margin and define a Cell
edge coverage probability.

AT310_UMU_E0
When selected, the shadowing margin will be taken into account using the defined Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is available,
default values are used. Macro diversity is also taken into account during RSCP calculation.
d. Under UMTS in the left-hand pane under Parameters, select EcIo.
If you select Manual Configuration from the Base prediction settings on list, define the following options:
-
Select the Enable Shadowing Margin check box if you want to enable a shadowing margin and define a Cell
When selected, the shadowing margin will be taken into account using the defined Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is available,
default values are used. Macro diversity is also taken into account during Ec Io calcula on.
6.4.3.2.3
Select a Service and a Terminal. The service and terminal specified are used during the calcula on of Ec Io
through gain and losses (i.e., the service body loss, the gain and loss of the terminal antenna, and terminal
noise factor).
Setting Network Reconfiguration Parameters

The Reconfiguration tab allows you to select the UMTS cells for which the pilot power will be reconfigured and the transmitters for which the antenna, azimuth, height, or tilt will be reconfigured. The Reconfiguration tab also allows you to select
which sites can be added or removed to improve existing or new networks. You can also use the Reconfiguration tab to quickly
select sites for reconfiguration. For information on site selection, see "Defining Site Selection Parameters" on page 354.
Atoll allows you to export the reconfiguration parameters, modify them in an external application and then reimport them
into the Reconfiguration tab.
"Setting UMTS Cell Reconfiguration Parameters" on page 349

"Setting Transmitter Reconfiguration Parameters" on page 351
"Linking Transmitters in Multi-layer Networks" on page 352
"Importing Network Reconfiguration Parameters" on page 353.
Setting UMTS Cell Reconfiguration Parameters

To set the UMTS cell reconfiguration parameters:
2. Click the Reconfiguration tab and, on the left-hand side of the Reconfiguration tab, click the UMTS Cells tab (see
Figure 6.57).
Figure 6.56: UMTS cell reconfiguration options
349

Forsk 2011
You can limit the cells displayed on the Reconfiguration tab by selecting the zone they are
located in from the Display on list. The Display on list only affects the cells displayed and
not the cells optimised. The Display on list is available at the top of the Sites, Transmitters,
and UMTS Cells tabs. Any selection you make from the Display on list on one tab affects
what will be displayed on all other tabs.
3. Select the Pilot power check box for the pilot power of each selected cell to be set within a defined minimum and
maximum value and in the defined number of steps.
4. If you are optimising exposimetry, select the Max Power check box to ensure a maximum power level is respected.
The option of optimising maximum power is only available when you are optimising
exposimetry.
5. Select the Synchronise cell power on co-sector cells check box to ensure that all cells on the same sector are assigned
the same cell power. If you are optimising exposimetry, the cell power of co-sector cells is automatically synchronised.
In other words, if, in order to meet the exposimetry objectives, the cell power of one cell must be set to a given level,
then the cell power of all co-sector cells will be set accordingly.
If one of the cells of a sector is not being optimised (if the check box in the Use column is
cleared), when cell power is synchronised, its assigned cell power forced to that of the
optimised cells.
6. Define the pilot power settings for each cell.
-
Use: Select the Use check box corresponding to the cell to include it in the optimisation of the pilot power.
Current: The current pilot power for the cell.
Min. and Max.: Set a minimum and maximum pilot power to be respected during the optimisation process.
If you selected the Power max/min as offset check box, you will set the Min. Offset and
Max. Offset for each cell.
Step (dB): Set a Step in dB that ACP should use with attempting to find the optimal pilot power.
For pilot power optimisation, the pilot range is defined with minimum, maximum, and step
values. Independently of the maximum defined on the UMTS Cells tab, there is an absolute
maximum possible pilot power which depends on the other powers used in the cell (for
control, traffic, and maximum cell power).
You can make the same changes to several cells by making the change for one item, selecting the others starting from
the changed item and using the Fill Up (CTRL+U) or Fill Down (CTRL+D) commands. For more information on the Fill
Up or Fill Down commands, see "Pasting the Same Data into Several Cells" on page 54.
You can select the cells to which the reconfiguration options are going to be applied using the Advanced section of
the Reconfiguration tab. For more information, see "Selecting Sites for Reconfiguration" on page 357.
You can sort the contents of any column by right-clicking the column and selecting Sort Ascending or Sort Descending
Cells that have been filtered out, either by zone or by clearing their check box in the
table, will not be optimised but are still present in the network and, therefore, continue
to generate interference.
Atoll enables you to export the current network reconfiguration options, edit them in a different application and then reimport them into the Reconfiguration tab. For information on importing network reconfiguration options, see "Importing
Network Reconfiguration Parameters" on page 353.
350

AT310_UMU_E0
Setting Transmitter Reconfiguration Parameters

To set the transmitter reconfiguration parameters:
2. Click the Reconfiguration tab (see Figure 6.57).
Figure 6.57: Transmitter reconfiguration options

3. Select the parameters that will be optimised:
-
Antenna type: Select the Antenna type check box for ACP to adjust the antenna type by selecting the best antenna
from the antenna group assigned to each selected transmitter.
Electrical tilt: Select the Electrical tilt check box for ACP to select the best electrical tilt from the antenna group
assigned to each selected transmitter within the defined range.
When ACP selects the best antenna type, it will also choose the best electrical tilt from the
antenna group even if it is not optimising the electrical tilt. However, because no range is
defined, ACP will select the best electrical tilt from all available.
Azimuth: Select the Azimuth check box for ACP to set the antenna azimuth using a defined range on either side
of the currently defined azimuth.
By default, ACP optimises the antenna azimuth of each sector of a site individually.
However, you might want to retain the same inter-sector angle separation. If this is the
case, you can select the Azimuth check box corresponding to that site under Lock Site on
the Sites tab of the Reconfiguration tab.
Mechanical tilt: Select the Mechanical tilt check box for ACP to set the mechanical tilt within the defined range
and in the defined number of steps.
Antenna Height: Select the Antenna Height check box for ACP to set the antenna height within the defined range
and in the defined number of steps. If you are optimising EMF exposure, you can not optimise the antenna height.
By default, if the Antenna Height check box corresponding to a site under Lock Site on the
Sites tab of the Reconfiguration tab is cleared, ACP checks whether a sites antennas are
co-located (i.e., have the same coordinates). If so, the height of the antennas is locked. If
the antennas are not co-located, the height of the antennas is not automatically locked,
permitting ACP to optimise the height of each antenna individually.
The table displays, for each parameter selected, both the current settings for each cell in the selected zone and the
currently defined optimisation parameters.
351

Forsk 2011
If you want ACP to display more information on each transmitter, you can select the Show
Advanced Grid check box. ACP will then display, for each transmitter, the antenna masking
method, the propagation model used, the name, and status of the site the transmitter is
located on. The propagation model displayed is extracted from the Atoll document but can
be changed if the propagation model is not recognised by ACP (for more information, see
"ACP and Antenna Masking" on page 333).
4. Define the settings to be optimised for each cell.
If are optimising the antenna azimuth, you can enter a single value in the Variation column, to define a range on either
side of the current azimuth, or you can enter a minimum and maximum value separated by a semi-colon in the format
"-min;max", (for example, "-20;40") in the Variation column for an asymmetric antenna.
You can make the same changes to several cells by making the change for one item, selecting the others starting from
the changed item and using the Fill Up (CTRL+U) or Fill Down (CTRL+D) commands.
For more information on the Fill Up or Fill Down commands, see "Pasting the Same Data into Several Cells" on
page 54.
Linking Transmitters in Multi-layer Networks
When you are optimising transmitters in multi-layer environments, ACP automatically links transmitters in the same location
but in different layers to ensure that it applies the same reconfiguration to them. ACP links them not only by location, but also
by azimuth, mechanical tilt, and antenna height. If ACP does not automatically link two transmitters which should be linked,
it is normally because there is too large a difference in one of the parameters of the two transmitters, for example, a few
degrees in azimuth, one degree in mechanical tilt, or one meter difference in antenna height.
If two transmitters should be linked but were not, you can manually link them.
If the site of one of the linked transmitters has either its antenna heights or azimuths
locked, i.e., if changes made to one sector of the site are made to all sectors on that site,
then corresponding changes will be made to the other linked transmitter. For more information on locking antenna heights or azimuths, see "Setting Transmitter Reconfiguration
Parameters" on page 351.
To link transmitters:
2. Click the Reconfiguration tab and, on the left-hand side of the Reconfiguration tab, click the Transmitters tab.
3. Click Advanced at the bottom of the Reconfiguration tab. The Advanced options appear.
4. Under Advanced, click the Multi-layer Management tab. On the Multi-layer Management tab, you can link transmitters (see Figure 6.58).
352

AT310_UMU_E0
Figure 6.58: Multi-layer management

To link transmitters in the same location but on different layers:
a. Hold CTRL and click the first transmitter in the table above and then the second transmitter. The Link button on
the Multi-layer Management tab is now available.
b. Click the Link button. The two transmitters are now linked and ACP will apply the same reconfiguration to them
both.
To unlink linked transmitters:
a. Select the transmitters in the table The Unlink button on the Multi-layer Management tab is now available.
b. Click the Unlink button. The transmitters are no longer linked.
To unlink all linked transmitters:
-
Click the Unlink All button. ACP resets all linked transmitters.
To automatically all transmitters in the same location but on different layers:

-
Click the Auto Link button. ACP links all transmitters that have the same position, azimuth and mechanical tilt.
Importing Network Reconfiguration Parameters

Atoll enables you to export the current network reconfiguration options, edit them in a different application and then reimport them into the Reconfiguration tab.
To import reconfiguration parameters:
2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the desired tab.
3. Right-click the table and select Export as Text from the context menu. The Save As dialogue appears.
4. Enter a name in the File name box and click Save. The file will be saved as a tab-delimited text file.
5. Open the text file in another application, for example, in a spreadsheet application, and make the modifications
desired.
6. Save the file as a text file and return to Atoll.
7. Click Advanced at the bottom of the Reconfiguration tab. The Advanced options appear.
8. Under Advanced, click the Import Facility tab.
9. Click the Import from File button. The Open dialogue appears.
10. Browse to the file and click Open. The Import Data dialogue appears (see Figure 6.59).
353

Forsk 2011
Figure 6.59: Importing site data into the Reconfiguration tab

11. Under Format Parameters, enter the number of the first row with data in the First Imported Row box, select the data
Separator, and select the Decimal Symbol used in the file.
12. If you want only the transmitters in the imported list to be used on the Reconfiguration tab, select the Use Only Tx(s)
in List check box. The Use check box will be cleared for all transmitters that are not in the imported file and they will
not be affected by reconfiguration options.
13. In the table, ensure that the column names from the imported file (the Source file) match the column names on the
Reconfiguration tab (Destination). You can change the Destination column by clicking the column name and selecting
the name from the list.
Any values in the imported file for current values can not be imported.
14. Click the Import button to import the file and replace the settings in the Reconfiguration tab.
6.4.3.3 Defining Site Selection Parameters

The Reconfiguration tab allows you to select which sites can be added or removed to improve existing or new networks. You
can also use the Reconfiguration tab to quickly select sites for reconfiguration.
"Selecting Sites for Addition or Removal" on page 354

"Creating Candidate Sites" on page 356
"Selecting Sites for Reconfiguration" on page 357.
Selecting Sites for Addition or Removal

You can use the Reconfiguration tab to select the sites that will be added or removed to improve existing or new networks.
To set site selection parameters:
2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab (see Figure 6.60).
354

AT310_UMU_E0
Figure 6.60: Site selection

3. Select the Current Site Selection check box to enable site selection. You can then define how sites will be added or
removed.
4. In the table, define how each site will be treated during site selection:
a. Select the Locked check box for each site that is not to be affected by site selection.
If you have many sites that you do not want to be affected by site selection, you can
select and lock them with the Advanced section. For more information on the options in
the Advanced section, see "Selecting Sites for Reconfiguration" on page 357.
b. Select the Status for each site that is not locked:
Only active sites are loaded by ACP. If you want inactive sites to be taken into account
during site selection, you must set them as active first in Atoll. When you commit the
results of the ACP run, all sites and sectors disabled by the ACP will be set to inactive in
Atoll.
-
Existing: An "Existing" site is considered as being active in the initial network. ACP will remove an existing site
if the Site Removable check box has been checked and if removing the site will improve network quality. If the
Sectors Removable check box has been checked, one or more sectors might be removed if removing them will
improve network quality.
Candidate: A "Candidate" site is considered as being inactive in the initial network. ACP will add the site during
the optimisation process if adding the site will improve network quality. If the Sectors Removable check box
has been checked, only one or more sectors might be added if adding them will improve network quality.
You can define candidate sites by clicking the New Candidate Setup button. For more information on defining
candidate sites, see "Creating Candidate Sites" on page 356.
c. Select the Sectors Removable check box for each site that can have sectors removed to improve network quality.
d. Select the Site Removable check box for each site that can be removed to improve network quality.
e. If desired, assign sites marked as "Candidate" in the Status column to a Group by selecting it from the list. If a candidate site does not belong to a group, no further constraints are imposed on ACP during optimisation. If a candidate site belongs to a group, ACP must respect the constraints of the group.
If a site group has no sites belonging to it, it is automatically deleted.
355

Forsk 2011
i.
Under Group, click the field and select New from the list. The New Site Group dialogue appears (see
Figure 6.61).
ii. Enter a Group Name and define the minimum and maximum number of sites from this group (from 0 to 1000)
that must be respected by ACP during optimisation (Minimum Site Occurrence and Maximum Site Occurrence, respectively). If there is no minimum or maximum that ACP must respect, leave the field blank.
iii. Click OK to create the group and return to the Site Selection tab.
Figure 6.61: Creating a new site group

f. Under UMTS Lock Sector, select the Azimuth or Height check box for any site for which you want to prevent the
ACP from making changes (to either the antenna azimuth or the height).
Creating Candidate Sites
The ACP enables you to create a list of candidate sites that can be added to the network to improve quality. For each candidate, you can specify both the location and the station template the candidate site would be based on if the ACP adds it to
the network. As well, the ACP can optimise candidate sites when they are added to the network.
During optimisation, the ACP will choose either from the sites defined as candidates on the Sites tab or from the list of candidate sites.
To create or edit candidate sites:
2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab.
3. On the Sites tab, click the New Candidate Sites button. The New Candidate Sites dialogue appears (see Figure 6.62).
Figure 6.62: New Candidate Setup dialogue

4. Under Zone Configuration, define, if desired, how candidate sites will be treated for each zone:
-
Zone: Select the zone (computation, focus, or hot spot zone defined on the Optimisation tab) from the list. The
ACP will add the candidate site according to the quality objectives defined on the Optimisation tab.
Default Station Template: Select the station template that any candidate site the ACP adds in the selected zone
will be based on.
The ACP can optimise each candidate site based on a template. You can set the optimisation parameters for each template by clicking the Template Reconfiguration button. For
information on the options, see "Setting Transmitter Reconfiguration Parameters" on
page 351.
356

AT310_UMU_E0
Default Group: Select the group that the candidate site will belong to by default.
Radio Layer: If there is more than one radio layer, select the radio layer the candidate site will be added to.
5. Under New Candidate List, define the individual candidate sites. For each candidate site set the following:
-
Name: Enter a name for the candidate site.
Location: Click the Browse button (

) to define the location of the candidate site. You can define the location
either as a set of co-ordinates or you can select an existing site from a list.
Station Template: Select the station template the candidate site will be based on. This selection overrides the
selection made under Zone Configuration.
Group: Select the group the candidate site will belong to. This selection overrides the selection made under Zone
Configuration.
Antenna Height: The antenna height of the candidate site is updated automatically from the defined default site
template or read from the data when you import a CSV file with a list of defined candidate sites.
You force the antenna height of all candidate sites to a defined value for each clutter class by clicking the Action
button and selecting Update candidate height from clutter height from the menu.
-
Site Class: Select the site class this candidate site will belong to. The site class will be used to determine the cost
of implementing this site.
The Site Class column does not appear if you have not defined a site class under Cost
Control on the Optimisation tab. All candidate sites will belong to the "Default" class site.
Radio Layer: Select the radio layer the candidate site will be added to. This selection overrides the selection made
under Zone Configuration.
6. If desired, select the Try to use multi-band antenna when possible check box. The ACP will attempt to use linked
transmitters on candidate sites if possible.
7. Click the Action button to update the list of new candidates by selecting one of the following options:
-
Clear List: Select Clear List to delete all current entries in the New Candidate List.
Import from File: Select Import from File to import a list of candidate sites, defined as XY coordinates.
Import from Current Sites Defined as Location Only: Select Import from Current Sites Defined as Location Only
to import as candidate sites sites in the current document that have no transmitters. The sites imported are those
in the reconfiguration zone(s) selected on the Optimisation tab. The defined reconfiguration zone(s) is displayed
at the top of the Reconfiguration tab as well.
Update Candidate Height from Clutter Height: Select Update Candidate Height from Clutter Height to define the
height of all candidate sites for each clutter class.
If you are using the ACP on a co-planning project, you have an additional option. This option enables you to, for example, upgrade an existing network from one technology to another.
-
Import from Existing [Technology] Sites: Select Import from Existing [Technology] Sites to import all the sites in
the other document as candidate sites in the current document.
Selecting Sites for Reconfiguration

You can use the Advanced area of the Reconfiguration tab to select sites. For more information on the Reconfiguration tab,
see "Setting Network Reconfiguration Parameters" on page 349.
To select sites:
2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab.
3. Select the Current Site Selection check box.
4. Click Advanced to display the Advanced area (see Figure 6.63).
357

Forsk 2011
Figure 6.63: The Advanced section

5. Select the Global Change tab.
6. Select the sites:
-
For entire table: Select For entire table if you want to select all sites in the table.
For selected rows: If you want to select a series of rows in the table, select the entries in the Site Name column
and then select For selected rows under Advanced. You can select contiguous rows by clicking the first entry,
pressing SHIFT and clicking the last entry. You can select non-contiguous rows by pressing CTRL and clicking each
entry separately.
With technology: If you have a co-planning project with more than one technology, select the With technology
check box and then select the technology from the list if you want to select all sites using that technology.
With status: Select the With status check box and then select the status from the list if you want to select all sites
with that status.
With site class: If you have defined site classes, select the With site class check box and then select the site class
from the list if you want to select all sites from that site class.
If you want to lock the selected sites, you can select the Set "Locked" check box and click
Apply. The locked sites will not be affected by the site addition or removal options.
6.4.3.3.1
Defining Antenna Groups

You can use the Antenna tab to define antenna groups according to their physical characteristics, as well as grouping patterns
according to their antenna pattern and defining multi-band antennas.
The antenna groups are necessary to apply the antenna type or electrical tilt reconfiguration options defined on the Reconfiguration tab. For more information on the Reconfiguration tab, see "Setting Network Reconfiguration Parameters" on
page 349.
By grouping similar antennas in the same group, ACP can select the best antenna for a transmitter from the group to which
the transmitter was assigned on the Reconfiguration tab. As well, electrical tilt is modelled in Atoll using the same antenna,
each with a different electrical tilt. By grouping all instances of the same antenna with different electrical tilts, ACP can reconfigure the electrical tilt of a transmitter by selecting the antenna with the optimal electrical tilt from the group to which the
transmitter was assigned.
358
"Creating and Grouping Antennas by Pattern" on page 359

"Grouping Antennas Automatically" on page 360
"Defining Multi-band Antennas" on page 360
"Creating Antenna Elements and Physical Antennas Automatically" on page 361
"Creating Antenna Groups" on page 361.

AT310_UMU_E0
Creating and Grouping Antennas by Pattern

Atoll enables you to create physical antennas by grouping several instances of antennas by their pattern.
By setting an option in the ACP.ini file, you can also optimise the additional electrical downtilt (AEDT) of antennas. When you
have set this option, you can select which antennas for which you will optimise the AEDT and the range of values that Atoll
can chose from during the optimisation process.
For information on setting options in the ACP.ini file, see the Administrator Manual.
To group antennas by their pattern:
2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Patterns tab (see Figure 6.64). The Antenna
tab displays all antennas in the Antenna Pattern Table and the groups under Antenna Element.
Figure 6.64: Antenna tab

3. Click the New button to create a new group under Antenna Element. You can change the name of the new group or
of any group by right-clicking the group name twice under Antenna Element, selecting Rename from the context
menu, and entering the new name.
You can delete one group by selecting it under Antenna Element and clicking the Delete button. You can delete all
groups by clicking the Delete All button.
4. Assign antennas to a group to create physical antenna elements or to associate antenna patterns to define a radiation
diagramme of a group of antennas with several variations of electrical tilt:
a. Select the group under Antenna Element.
b. Select the antenna under Antenna Pattern Table and click the right arrow between the columns (
) to assign
it to the selected group. Antennas under Antenna Pattern Table that have been assigned to a group are indicated
with an icon (
).
You can assign the same antenna to more than one group.
You can remove an antenna from a group by selecting it in the group under Antenna Element and clicking the left
arrow between the columns (
).
When you have grouped the antennas, you can back up the configuration by clicking the
Back Up Configuration button. In future ACP sessions, the antennas will then be grouped
automatically according to this definition.
5. If you are also optimising additional electrical downtilt, select the check box in the Use AEDT column corresponding
to each antenna for which you want to optimise the additional electrical downtilt and define the limits Atoll must
respect by entering values in the Min. AEDT and Max. AEDT for each antenna to be optimised.
359

Forsk 2011
Figure 6.65: The Antenna Pattern Table with AEDT enabled

Grouping Antennas Automatically
You can group antennas automatically using a regular expression, or "regex." The regular expression is retained from one Atoll
session to the next. Therefore, once you have set the regular expression for the given antenna naming convention, you will
not have to set again for the next Atoll session. The default regex pattern is overwritten when you change it. You can return
to the default regular expression by clearing the text box and clicking OK. You can change the default regular expression by
editing the appropriate entry in the ACP.ini file. For more information on the options available in the ACP.ini file, see the
It is recommended to identify both the antenna type and the electrical tilt in the
antenna name in Atoll and to separate the antenna type and electrical tilt with a special
character, for example, "_". This will make it easier to group antenna groups
automatically using a regular expression.
To group antennas automatically:
2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Patterns tab (see Figure 6.64 on page 359).
3. Under Automatic Creation, enter a regular expression, or "regex," in the text box.
Clicking the tip text button (

expressions.
) displays tip text with an explanation of common regular
4. Click the Build from Expression button to create antenna groups according to the defined regular expression.
When you have created the antenna groups, you can back up the configuration by clicking
the Back Up Configuration button. In future ACP sessions, the antenna groups are then
automatically created according to this definition.
Defining Multi-band Antennas
When you have grouped antennas according to their physical characteristics as explained in "Creating and Grouping Antennas
by Pattern" on page 359 and "Grouping Antennas Automatically" on page 360, they are displayed on the Radome tab of the
Antenna tab, grouped according to their frequency band.
You can merge these groups to create groups of antennas that are multi-band antennas.
To define multi-band antennas:
2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Physical Antenna tab (see Figure 6.64 on
page 359).
360

AT310_UMU_E0
Figure 6.66: Creating multi-band antennas

3. Create multi-band antennas by merging two or more antenna groups:
a. Select two or more antenna groups by holding CTRL and clicking the antenna groups in the Physical Antenna Table.
b. Click the Merge button. The antenna groups are now merged and will appear on the Antenna Groups tab.
You can break the merged antenna groups up by selecting them in the Physical Antenna Table and clicking the
Unmerge button, or by clicking Unmerge All. If you click Unmerge All, all merged antenna groups will be broken up.
4. Under Automatic Creation, enter a regular expression, or "regex," in the text box.
Creating Antenna Elements and Physical Antennas Automatically
ACP can automatically create representations of antenna elements and physical antennas using a custom field in the Atoll
document database.
To enable the ACP to automatically create antenna elements and physical antennas:
1. Create a custom column in the Antennas table of the Atoll document database.
2. For each antenna identified in the Antennas table, enter the name of the physical antenna to which the antenna pattern belongs in the custom column.
3. Define the name of the custom column in the ACP.ini file using the "antenna.model" option. For more information on
defining options in the ACP.ini file, see the Administrator Manual.
When you restart Atoll, and run the ACP on this document, ACP will now automatically create antenna elements and physical
antennas based on the entry in the custom field of the Antennas table of the Atoll document database.
Creating Antenna Groups
ACP creates antenna groups based on their frequency band, but you can create antenna groups based on other common characteristics. The antenna groups are used especially to choose between a directive antenna (of 35 degrees) and a less directive
one (of 65 degrees). However, in most circumstances, one antenna group corresponds to one physical antenna.
To group antennas:
2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Antenna Groups tab (see Figure 6.67 on
page 362).
On the Antenna Groups tab, there is already one group called "Default" in the Antenna Groups pane of the tab. The
"Default" group is created automatically by ACP and contains all the antenna patterns available for a given frequency.
361

Forsk 2011
Figure 6.67: Creating antenna groups

3. Click the New button to create a new group under Antenna Groups. You can change the name of the new group or of
any group by right-clicking the group name twice under Antenna Groups, selecting Rename from the context menu,
and entering the new name.
You can delete one group by selecting it under Antenna Groups and clicking the Delete button. You can delete all
groups by clicking the Delete All button.
4. Assign antennas to groups according to their physical characteristics:
a. Select the group under Antenna Groups.
b. Select the antenna under Physical Antenna Table and click the right arrow between the columns (
) to assign
it to the selected group. Antennas under Physical Antenna Table that have been assigned to a group are indicated
with an icon (
).
You can assign the same antenna to more than one group.
You can remove an antenna from a group by selecting it in the group under Antenna Groups and clicking the left
arrow between the columns (
).
When you have created the antenna groups, you can back up the configuration by clicking
the Back Up Configuration button. In future ACP sessions, the antenna groups are then
automatically created according to this definition.
6.4.3.3.2
Adding Comments to the Optimisation Setup

You can enter comments about the current optimisation setup on the Comments tab.
To add comments:
2. Click the Comments tab and add your comments.
6.4.4 Running an Optimisation Setup

When you have finished defining the optimisation parameters as described in "Defining Optimisation Parameters" on
page 339, you can run the optimisation setup, either immediately by clicking the Run button.
You can also save the defined optimisation setup by clicking the Create Setup button and then running the optimisation at a
later point.
362

AT310_UMU_E0
To run a saved optimisation setup:

3. Right-click the setup folder that you want to run in the ACP - Automatic Cell Planning folder. The context menu
appears.
4. Select Run from the context menu. The optimisation setup runs.
As the optimisation setup runs, ACP displays the current status of the process (see Figure 6.68) allowing you to observe the
progress. You can pause the optimisation if you desire or stop the optimisation early,
The Optimisation dialogue has four tabs:
Graphs: The Graphs tab displays a graph with the itera ons on the X axis and the op misa on objec ves (RSCP, Ec Io,
network quality, and global cost, if you have selected to take cost into consideration) on the Y axis (see Figure 6.68).
The values displayed are indicated with a legend.
Changes: The Changes tab displays in a graph indicating the quantity of changes made for each reconfiguration parameter selected during setup. The values displayed are indicated with a legend.
Quality: The Quality tab displays coverage quality maps for RSCP (Ec) and Ec Io improvement. If more than one layer
is being optimised, you can select the layer displayed at the top of the tab. The maps display the computation zone
with the network improvement performed to that point. If you based this optimisation on a coverage prediction (see
"Setting Objective Parameters" on page 345), the ranges and colours defined in the selected coverage prediction will
be used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP maps
settings as the default (see "Changing the Display Properties of ACP Maps" on page 377) or by using a configuration
file (see "Configuring the Default Settings" on page 337).
Objectives: The Objectives tab displays the progress in meeting the defined objectives, with the success or failure of
meeting the objectives indicated. You can select the objective displayed at the top of the tab.
EMF Exposure Maps: The EMF Exposure Maps tab displays maps indicating EMF exposure improvement performed
to that point.
Figure 6.68: The network coverage improvement graphs and maps
363

Forsk 2011
Figure 6.68: The network coverage improvement graphs and maps

When the optimisation has finished, the results are stored in the optimisation folder on the Network tab of the Explorer
window. By default, Atoll calls the optimisation folder a "Setup" folder. Each setup folder contains one or more optimisation
processes. Each optimisation process folder contains the results of that optimisation. For information on viewing optimisation
results, see "Viewing Optimisation Results" on page 365.
Figure 6.69: An optimisation run in the Explorer window

You can perform an optimisation on a network that has already been optimised. After
running the first optimisation and committing the results, you can create and run a second
optimisation, with different parameters on the optimised network. The setup on which the
optimisation is based is locked after you commit the changes. If you want to use the same
setup, you will have to duplicate it and select Partial update from the Setup Duplication
Options dialogue.
6.4.5 Working with Optimisations in the Explorer Window

Atoll offers you several options for working with the optimisation that you can access using the context menu on the Network
tab of the Explorer window.
To work with the optimisation:
4. Right-click the setup folder of the optimisation you want to work with. The context menu appears (see Figure 6.70).
Figure 6.70: Options available in the context menu
364

AT310_UMU_E0
5. Select one of the following from the context menu:

-
Properties: Selecting Properties from the context menu opens the optimisations Properties dialogue. You can
modify all of the optimisation parameters except for the selection of traffic maps (for information on the optimisation parameters, see "Defining Optimisation Parameters" on page 339). If you want to base an optimisation on
different traffic maps, you must create a new optimisation (for information on creating a new optimisation, see
"Creating an Optimisation Setup" on page 338).
Run: Selecting Run runs the optimisation setup. The results will be contained in a new optimisation folder in the
setup folder.
If you have changed some data in Atoll, for example, if you added transmitters or
change some of the transmitter settings, the data that optimisation results are based on
may differ from the current Atoll data. If you run a optimisation based on settings made
before the changes, it will not take the changed data into consideration.
ACP normally detects changes in the Atoll document data and can lock a group if it is
impossible to run an optimisation that is coherent with existing data. ACP can lock a
group if, for example, when you commit optimisation results after the path losses have
been recalculated and are no longer consistent with the data used to run the
optimisation.
When this happens you will either have to:
Create a new optimisation as explained in "Creating a New Optimisation Setup"

on page 338.
Duplicate an existing optimisation which will create a new optimisation with the
same configuration but with updated parameters.
Roll back the previously committed parameters as explained in "The Commit Tab"
on page 373.
Delete: Selecting Delete deletes the defined optimisation setup and any results.
Storing optimisation results and the group configuration increase the size of the Atoll file. Deleting unused setups
in the ACP - Automatic Cell Planning folder will decrease the size of the Atoll file.
Load Configuration: Selecting Load Configuration displays the Open dialogue. You can then select a PRJ file based
on the settings of a different optimisation. When you load a configuration based on a different Atoll document,
only the settings that are not specific to that document are loaded.
Save Configuration: Selecting Save Configuration displays the Save As dialogue. You can then save the optimisation settings in a PRJ file. You can then use this PRJ file to quickly configure an optimisation.
Saving a configuration is a quick way to save the settings you have made in an external
file. You can then easily create new configurations using these same settings as a basis
without having to recreate them.
Duplicate: Selecting Duplicate displays the ACP Duplicate Options dialogue. You can then duplicate the either the
ACP-generated data of selected optimisation setup or all of the data of the setup. Duplicating the ACP-generated
data permits you to create a new setup with up-to-date data even though the data of the original setup is no
longer valid.
6.4.6 Viewing Optimisation Results

Once you have run the calibrated optimisation as explained in "Running an Optimisation Setup" on page 362, the results are
stored in the optimisation folder on the Network tab of the Explorer window. You can view the results in the optimisations
Properties dialogue or in the map window.
"Viewing Optimisation Results in the Properties Dialogue" on page 366

"Viewing Optimisation Results in the Map Window" on page 373
"Viewing Optimisation Results Using the Histogram" on page 379.
365

Forsk 2011
6.4.6.1 Viewing Optimisation Results in the Properties Dialogue

You can view the results of the optimisation run in its Properties dialogue in the ACP - Automatic Cell Planning folder.
To view the results of the optimisation in its Properties dialogue:
3. Click the Expand button ( ) to expand the folder of the setup containing the optimisation results you want to view.
4. Right-click the optimisation. The context menu appears.
5. Select Properties from the context menu. The optimisations Properties dialogue appears.
The optimisation results are on individual tabs of the Properties dialogue (with an extra tab, the General tab, that
allows you to change the name of the optimisation results):
-
6.4.6.1.1
Statistics: The Statistics tab displays a synthesised view of the optimisation results of the quality figures (RSCP
quality, Ec Io quality, and network quality), and of the EMF exposure op misa on, if one was made. For more
information on the Statistics tab, see "The Statistics Tab" on page 366.
Sectors: The Sectors tab displays a table with the reconfigured cells in green, sites and sectors which have been
added or removed, and the RSCP and Ec Io coverage quality per cell before and a er op misa on. For more information on the Statistics tab, see "The Sectors Tab" on page 368.
Graph: The Graph tab displays a graph with the iterations on the X axis and the optimisation objectives (RSCP
quality, Ec Io quality, network quality, and global cost, if you have selected to take cost into considera on, and the
EMF exposure optimisation, if one was made) on the Y axis. The values displayed are indicated with a legend. For
more information on the Graph tab, see "The Graph Tab" on page 370.
Quality: The Quality tab displays the computa on zone with coverage quality maps for RSCP (Ec) and Ec Io before
and after optimisation, and for the EMF exposure optimisation, if one was made. For more information on the
Quality tab, see "The Quality Tab" on page 371.
Change Details: The Change Details tab enables you to analyse the improvement caused by each reconfiguration
option. For more information on the Change Details tab, see "The Change Details Tab" on page 372.
Commit: The Commit tab enables you to commit the set of selected changes. For more information on the
Commit tab, see "The Commit Tab" on page 373.
The Statistics Tab

The Statistics tab displays a synthesized view of the op misa on results of the quality figures (RSCP quality, Ec Io quality, and
network quality) and of the EMF exposure optimisation, if one was made.
366

AT310_UMU_E0
Figure 6.71: The Statistics tab

For the RSCP and Ec Io coverage quality, both the ini al and final figures are given, as well as the absolute improvement. These
figures are given both for the computation zone and the focus zone. If you defined weights for each zone on the Objectives
tab of the dialogue used to define the optimisation (see "Setting Objective Parameters" on page 345), ACP indicates that the
results are weighted.
For the network quality, the relative improvement is given. This improvement measures the overall decrease of interference
in the network, which can be loosely equated to the overall capacity increase in the network.
You can see more detailed information by clicking the links (see Figure 6.72):
Show Change Statistics: The change statistics showing the reconfiguration and site selection statistics.
Show Detailed Hot Spot/Clutter Results: The detailed quality figures on each hot spot and by each clutter class.
Show Input: The input settings of this optimisation.
367

Forsk 2011
Figure 6.72: The Statistics tab - detailed information

You can export the results by clicking the Export button. The Save As dialogue that appears allows you to select the format in
which you want to save the results: XLS, TXT, HTML, or XML.
6.4.6.1.2
The Sectors Tab

The Sectors tab displays a table with all the cells in the network with the following information:
368
Cells which have been reconfigured are displayed in green (i.e., if they have had their antenna type, azimuth, mechanical tilt, or pilot power reconfigured).
Sites and sectors which have been added or removed.
The RSCP and Ec Io coverage quality per cell before and a er op misa on. The quality figures are measured on the
best server area of each cell.
Antenna type, height, azimuth, mechanical tilt, and pilot power initial and final values for each cell.

AT310_UMU_E0
Figure 6.73: The Sectors tab

The results are displayed in a table. You can access options such as sorting, exporting data using the context menu (see
Figure 6.74) sort, column hiding, export, etc.
Figure 6.74: Options available for data in the Sectors tab

If you are optimising EMF exposure, on the left-hand side of the Sectors tab, a second tab, the EMF Exposure tab, appears.
The EMF Exposure tab displays the initial and final Vm contribution for each transmitter in the optimisation.
369

6.4.6.1.3
Forsk 2011
The Graph Tab

The Graph tab displays a graph with the itera ons on the X axis and the op misa on objec ves (RSCP quality, Ec Io quality,
and total cost, if you have selected to take cost into consideration, and the EMF exposure optimisation, if one was made) on
the Y axis (see Figure 6.75). The values displayed are indicated with a legend.
Figure 6.75: The Graph tab

The tool bar allows you to:
Zoom and span the graph

Export to a BMP image file or simple text file
Print the graph
Show the values along the curves.
Figure 6.76: The Graph tab with the values displayed on the selected point
370

AT310_UMU_E0
6.4.6.1.4
The Quality Tab

The Quality tab displays the computa on zone with coverage quality maps for RSCP (Ec), Ec Io, and overlapping coverage
before and after optimisation, the objective maps, and the EMF exposure optimisation, if one was made. You can define the
area displayed in the coverage quality maps by selecting the zone (computation, focus, or hot spot) from the list above the
maps.
Figure 6.77: Coverage maps on the Quality tab

The maps are displayed with a range of values displayed on the right. If you based this optimisation on a coverage prediction
(see "Setting Objective Parameters" on page 345), the ranges and colours defined in the selected coverage prediction will be
used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as
the default (see "Changing the Display Properties of ACP Maps" on page 377) or by using a configuration file (see "Configuring
the Default Settings" on page 337).
This range can be modified using the Map Properties dialogue accessed through the tool bar (see Figure 6.78).
Figure 6.78: Defining the display properties of the coverage maps

In addition to the map, a histogram is provided for quick evaluation of the improvement seen across the entire range of values.
This histogram displays the statistics within the focus zone if selected. It should be also noted that the statistics are given using
traffic weighting when traffic maps are used. They can therefore be different from similar statistics obtained through the
Generate Report tool in Atoll which only uses uniform weighting.
371

Forsk 2011
The default colour range used for display can be changed by setting options in the acp.ini
file. For information on the acp.ini file options, see the Administrator Manual.
6.4.6.1.5
The Change Details Tab

In addition of the map, a histogram is provided for quick evaluation of improvement seen across the entire range of values.
This histogram displays the statistics within the focus zone if selected. It should be also noted that the statistics are given using
traffic weighting when traffic maps are used. They can therefore be different from similar statistics obtained through the
Generate Report tool in Atoll which only uses uniform weighting.
The default colour range used for display can be changed by setting options in the acp.ini
file. For information on the acp.ini file options, see the Administrator Manual.
Figure 6.79: The Change Details tab

You can select a subset of all changes using a slider and view the corresponding performance improvement on the graph. This
can enable you to achieve two goals:
To select a subset of changes to be implemented. For example, you might find that implementing only one-third of
the recommended changes will provide 80% of the benefit. You could then chose to commit only those changes to the
Atoll document.
To find the optimal order in which to apply these changes in the field, while at the same time avoiding less than
optimal performance, or even degrading the performance, during the implementation phase.
Before selecting a subset of recommended changes, it is important to understand that ACP calculates the set of recommendations globally and that these changes are interdependent. During the finalisation step, ACP calculates the ordered list of
changes displayed on the Change Details tab by starting from the initial network configuration and iteratively selecting the
change that will have the most effect on the network. If you arbitrarily select a subset of the recommended changes, it is highly
likely that the improvement of the network quality will not be as great as projected. It is therefore highly recommended to
follow the ordered list of changes as proposed.
The data displayed on the other tabs takes all the proposed changes into consideration.
If you select only a subset of the proposed changes on the Change Details tab, the
statistics displayed on other tabs do not change.
When you commit the optimisation changes, ACP will only commit the proposed changes selected on the Change Details tab.
For information on committing the optimisation changes, see "The Commit Tab" on page 373.
372

AT310_UMU_E0
6.4.6.1.6
The Commit Tab

This dialogue enables you to commit the set of selected changes (antenna, azimuth, tilt, sector selection, or pilot power) to
the Atoll document or to roll the network back to its initial state.
The Commit tab automatically takes into account the changes selected on the Change Details tab; the Use check box is cleared
for any change that was deselected on the Change Details tab.
Figure 6.80: The Commit tab

You can select one of the following:
Commit: Clicking the Commit button will update the Atoll document with the changes displayed on the Commit tab.
Once you have committed the changes, you can recalculate the path losses and use any of the functions available in
Atoll, including coverage predictions and simulations. After you perform any such calculations, remember to click the
Roll Back to Initial State button to return to the original network settings.
Roll Back to Initial State: Clicking the Roll Back to Initial State button will revert the Atoll network to its state before
the optimisation was run.
When you click either the Commit button or the Roll Back to Initial State button, information about the commit or rollback
process is displayed in the Atoll Event Viewer.
The Effects of Committing or Rolling Back Changes on Existing Setups
When you commit the optimisation results, all existing configuration setups are locked because the network state on which
the configuration setup was based is not coherent with the current path losses. ACP automatically detects any incoherence
and prevents you from running an optimisation on incoherent data. ACP will unlock the optimisation setups when it becomes
possible, for example, when you roll back the data to restore the Atoll state to be coherent with the network state on which
the configuration setup was based.
It is important to remember that you can commit or roll back other optimisation results even when the setup is locked.
6.4.6.2 Viewing Optimisation Results in the Map Window

ACP can display optimisation results in the form of maps in the map window. This allows you to view the results and facilitates
analysis. If you based this optimisation on a coverage prediction, the ranges and colours defined in the selected coverage
prediction will be used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP
maps settings as the default or by using a configuration file.
To view the results of the optimisation in the map window:
373

Forsk 2011
4. Right-click the optimisation. The context menu appears.

5. Select New Map from the context menu. The ACP Map Types dialogue appears (see Figure 6.82).
Figure 6.81: Displaying a new map based on ACP results

The maps available in the ACP Map Types dialogue are organised by category.
6. Select the category of maps or click the Expand button (
or map.
) to expand the category and then select the sub-category
7. Click OK to create the maps. The maps are created and inserted into the folder of the setup containing the optimisation results (see Figure 6.82).
Figure 6.82: The map types correspond to the available results

You can display a map by selecting its check box in the folder of the setup containing the optimisation results. The display
properties can be changed for a single map or for all maps.
For information on the display properties for ACP maps, see "Changing the Display Properties of ACP Maps" on page 377.
The following sections provide more information on the maps:
6.4.6.2.1
"The Objective Analysis Maps" on page 374

"The UMTS Layer Maps" on page 375
"The EMF Exposure Maps" on page 376
"Comparing Maps" on page 376
"Changing the Display Properties of ACP Maps" on page 377
"Exporting ACP Coverage Maps" on page 378.
The Objective Analysis Maps

The objective analysis maps enable you to display the whether or not the defined objectives (RSCP and EcIo) were met in the
intial coverage or in the final coverage. An additional objective analysis map displays the variation between the initial coverage and the final coverage, i.e., whether the objective was met in the initial coverage, in the final coverage, in both, or in
neither.
You can view whether or not the objective was met on any pixel by letting the pointer rest over the pixel. Whether or not the
objective was met is then displayed in tip text. When the variation between the initial and final coverage is displayed, the tip
text also indicates whether the objective was met on that pixel in the initial coverage, final coverage, both, or neither.
374

AT310_UMU_E0
6.4.6.2.2
The UMTS Layer Maps

The UMTS layer maps provide a series of technology-specific maps to analyse the results of the optimisation:
"The Quality Analysis Maps" on page 375

"The Change Analysis Maps" on page 375
"Best Server Analysis" on page 376
"Objective Coverage Analysis" on page 376.
The Quality Analysis Maps

The quality analysis maps enable you to display the RSCP and Ec Io quality maps in the Atoll map window. These maps are the
same as those displayed on the Quality tab of the optimisations Properties dialogue.
The quality analysis maps are the equivalent of maps created by different Atoll coverage predictions:
The RSCP maps correspond to the Atoll coverage by signal level in UMTS. For information on the coverage by signal
level, see "Studying Signal Level Coverage" on page 229.
The overlapping zones maps correspond to the Atoll overlapping zones coverage prediction. For more information,
see "Making a Coverage Prediction on Overlapping Zones" on page 240.
Making these maps available within ACP enables you to quickly validate the optimisation results without having to commit
the results and then calculate a coverage prediction in Atoll. The ACP maps display results very similar to those that Atoll
would display if you committed the optimisation results and calculated Atoll coverage predictions, however, before basing
any decision to commit the optimisation results on the maps produced by ACP, you should keep the following recommendations in mind:
You should verify the results with a different Atoll coverage prediction, such as the pilot pollution prediction.
ACP generated maps are generated using the entire set of proposed changes. They do not take into account the
change subset defined on the Change Details tab.
Multiple carriers are not supported by ACP; the maps are only provided for the requested carrier.
Even after committing the optimisation results, differences can remain between the ACP maps and the maps resulting
from Atoll coverage predictions.
You can view the exact RSCP and Ec Io values on any pixel by le ng the pointer rest over the pixel. The RSCP or Ec Io value is
then displayed in tip text.
For the overlapping zones map, you can set the best server threshold on the User Preferences tab of the ACP Properties
dialogue (see "Configuring the Default Settings" on page 337) or by setting the CellOverlap parameter in the acp.ini file.
For each network quality coverage prediction, ACP offers a map showing the initial network state, the final network state, and
a map showing the changes between the initial and final state.
The Change Analysis Maps
The change analysis maps allow you to analyse the changes recommended by the ACP. The change attributes are displayed
on the map using a best server map, because the types of changes that ACP recommends are all related to individual cells.
The best server map used is usually the initial best server map but you can use the final best server map for new sites (i.e.,
sites that have been added during optimisation).
The following maps are available:
Reconfiguration Types: In the Reconfiguration Types folder, there is a separate map for each reconfiguration option
displaying the changes to the network: azimuth, mechanical tilt, antenna, and pilot power. The changes are displayed
for the best server zone. The maps can be displayed individually to display each reconfiguration option separately or
together to display all reconfiguration options.
Sector Selection Types: In the Sector Selection Types folder, there are maps to display which sectors or sites have
been added or removed. These maps are only available if the site selection was activated during optimisation.
Change Order: The Change Order map displays the order of changes (as displayed on the Change Details tab of the
optimisations Properties dialogue). You can define the colours used to display the order of changes by right-clicking
the Change Order map in the Change Analysis folder, selecting Properties from the context menu and then changing
the colours on the Display tab. By displaying the Change Order map, you can see where the most important changes
to be made to the network are located.
Change of Electrical Tilt, Mechanical Tilt, Azimuth, Height, Pilot Power, and Change Cost: These maps show the variation of the given parameter. They can be used to see where in the network this reconfiguration option was changed.
The electrical tilt values are calculated using the vertical antenna pattern. The Change of
Electrical Tilt map is made available even when the change was to the antenna type.
375

Forsk 2011
Best Server Analysis

The best server analysis maps contain maps enabling you to analyse cell-related parameters as related to the best server. The
following maps are available:
Initial and Final Electrical and Mechanical Tilt Values: These maps show the tilt values on the initial and final network.
They can be used, for example, to identify areas with strong tilt values.
Initial and Final Antenna Height: These maps show the initial and final antenna heights.
Ini al and Final Cell RSCP and EcIo Coverage: These maps show the percentage of the best server area which is covered according to the defined threshold. The values displayed are the same as those on the Cells tab of the optimisations Properties dialogue. You can use these maps to quickly identify the cells which potentially have poor quality.
Initial and Final Overlapping Ratio: These maps show the percentage of the best server area with overlapping coverage greater than "1," i.e., with several received signals over the defined threshold.
Objective Coverage Analysis

The objective coverage analysis maps enable you to display the initial and final coverage of the objectives (RSCP and EcIo) relative to the defined thresholds. You can view the RSCP and EcIo values relative to the defined thresholds on any pixel by letting
the pointer rest over the pixel. The RSCP or EcIo value is then displayed in tip text. The tip text also provides the best server,
whose signal is used to calculate the RSCP and EcIo.
6.4.6.2.3
The EMF Exposure Maps

The EMF exposure maps contain maps enabling you to analyse EMF exposure. The following maps are available:
6.4.6.2.4
Quality Analysis: These maps show the EMF exposure values on the initial and final network, as well as the EMF exposure gain.
EMF Exposure Coverage Improvement: This map shows the improvement in EMF exposure.
Sector Analysis: These maps show the initial and final Vm contribution of the optimisation area.
Comparing Maps
You can compare the results displayed on one map with the results of another map from the same optimisation or from a
different optimisation.
To compare a map with a map from the same optimisation:
1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results
as explained in "Viewing Optimisation Results in the Map Window" on page 373, right-click the map you want to
compare. The context menu appears.
2. From the context menu, select Compare With and then select one of the maps in the submenu. A new map is created
in the optimisation folder and the results of the comparison are displayed in the map window.
3. ACP creates a new map in the optimisation folder and displays it in the map window with the pixels that are displayed
on both maps or only on a single map.
Figure 6.83: Comparing two optimisation maps
376

AT310_UMU_E0
To compare a map with a map from a different map type or with a map from a different optimisation:
as explained in "Viewing Optimisation Results in the Map Window" on page 373, right-click the map you want to
compare. The context menu appears.
2. From the context menu, select Compare With > Others. The ACP Compare Map dialogue appears (see Figure 6.84).
By default, the ACP Compare Map dialogue displays only maps from the same optimisation as the map you want to
compare.
Figure 6.84: The ACP Compare Map dialogue

3. Define the maps you choose from:
-
Show predictions from Predictions folder: Select the Show predictions from Predictions folder check box if you
want to be able to compare with a map from a coverage prediction you have already created and calculated.
Show maps from all ACP setups: Select the Show maps from all ACP setups check box if you want to be able to
compare with a map from a different optimisation.
Show only maps of same type: Select the Show only maps of same type check box if you want to restrict the maps
displayed to maps displaying comparable information.
4. Select the map with which you want to compare the first one and click OK. ACP creates a new map in the optimisation
folder and displays it in the map window with the pixels that are displayed on both maps or only on a single map.
By first defining a display interval of "1" in both maps and then comparing them, the
resulting comparison map will have more meaningful results. For information on
defining "Changing the Display Properties of ACP Maps" on page 377.
6.4.6.2.5
Changing the Display Properties of ACP Maps

You can define how ACP maps are displayed in the Atoll map window. You can define the colours used as well as the ranges
of values on the Display tab of each maps Properties dialogue. As well, ACP allows you to display the value on each pixel in
the form of tip text.
To define the display of an ACP map:
as explained in "Viewing Optimisation Results in the Map Window" on page 373, right-click the map whose display you
want to define. The context menu appears.
2. Select Properties from the context menu. The Properties dialogue appears (see Figure 6.85).
377

Forsk 2011
Figure 6.85: Setting the display properties for a map

4. On the Display tab, you can define the following settings:
-
Colours: For each range of values, you can click the colour button and select the colour that will be used to represent that range.
Min. and Max.: You can define the minimum and maximum values that will define that range.
Transparency: You can define the transparency of the map using the slider.
Add to legend: You can display the range of values of the optimisation map by selecting the Add to legend. check
box.
Actions: You can modify the ranges of values by clicking the Actions button and selecting one of the following:
-
Select All: Select Select All to select all the ranges on the Display tab. Anything you select after that from the
Actions menu (for example, Delete) will be applied to the selected ranges.
Delete: Select Delete to delete the selected range or ranges.
Insert Before: Select Insert Before to insert a new range before the selected range.
Insert After: Select Insert After to insert a new range after the selected range
Shading: Select Shading to open the Shading dialogue where you can define all the ranges by setting the first
value, the last value, and the step between values, as well as the colour used for the first value and the colour
used for the last value. ACP will shade the ranges in between the first and last value with a range of colours
going from the first colour to the last.
Save as Default: Select Save as Default to set the current settings on the Display tab to the default settings.
These settings can then be used for all maps of the same kind.
Load from Default: Select Load from Default to change the current settings to those set as the default using
Save as Default.
Reset to Default: Select Reset to Default to change the current settings back to the ACP defaults. You can also
use Reset to Default to return to the ACP defaults when you have created user-defined defaults using Save as
Default.
You can display the value on a pixel by resting the pointer on the pixel in the map window. The value on that pixel will be
displayed in tip text.
6.4.6.2.6
Exporting ACP Coverage Maps

ACP enables you to export the optimisation coverage maps as BMP files. Before you can export an optimisation coverage map,
you must first select the map and define its appearance as explained in "Viewing Optimisation Results in the Map Window"
on page 373.
To export an optimisation coverage map:
3. Click the Expand button ( ) to expand the folder of the setup containing the optimisation map you want to export.
378

AT310_UMU_E0
4. Click the Expand button ( ) to expand the optimisation.

5. Right-click the map. The context menu appears.
7. Enter a File name for the exported coverage map and select the format from the Save as type list.
8. Click Save. The exported coverage map is saved in the selected format. Depending on the file format selected from
the Save as type list, Atoll creates an additional file in the same location containing geo-referencing information:
-
BMP file: Atoll creates a BPW file.

ArcView grid (TXT) file: Atoll creates a BPW file.
BIL file: Atoll creates a HDR file.
GRD or GRC file: Atoll creates a TAB file.
PNG file: Atoll creates a PGW file.
TIF file: Atoll creates a TFW file.
9. Atoll also creates a BPW file in the same location containing geo-referencing information.
6.4.6.3 Viewing Optimisation Results Using the Histogram

ACP can display optimisation results in the form of a histogram. The histogram is provided for quick evaluation of improvement seen across the entire range of values. This histogram displays the statistics within the focus zone if selected. If you
based this optimisation on a coverage prediction, the ranges and colours defined in the selected coverage prediction will be
used for the histogram, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as
the default or by using a configuration file.
To view the results of the optimisation using a histogram:
4. Click the Expand button ( ) to expand the folder of the optimisation.
Depending on the type of optimisation results you want to view, you might need to expand
additional folders.
5. Right-click the optimisation results. The context menu appears.

6. Select Histogram from the context menu. The histogram appears in a separate window with a legend on the right side.
6.5 Verifying Network Capacity

An important step in the process of creating a UMTS HSPA network is verifying the capacity of the network. This is done using
measurements of the strength of the pilot signal in different locations within the area covered by the network. This collection
of measurements is called a drive test data path.
The data contained in a drive test data path is used to verify the accuracy of current network parameters and to optimise the
network.
"Importing a Drive Test Data Path" on page 379

"Displaying Drive Test Data" on page 382
"Defining the Display of a Drive Test Data Path" on page 382
"Network Verification" on page 383
"Exporting a Drive Test Data Path" on page 389
"Extracting CW Measurements from Drive Test Data" on page 389
"Printing and Exporting the Drive Test Data Window" on page 389.
6.5.1 Importing a Drive Test Data Path

In Atoll, you can analyse drive tests by importing drive test data in the form of ASCII text files (with tabs, semi-colons, or spaces
as separator), TEMS FICS-Planet export files (with the extension PLN), or TEMS text export files (with the extension FMT).
379

Forsk 2011
For Atoll to be able to use the data in imported files, the imported files must contain the following information:
The position of drive test data points. When you import the data, you must indicate which columns give the abscissa
and ordinate (XY coordinates) of each point.
Information identifying scanned cells (for example, serving cells, neighbour cells, or any other cells). In UMTS networks, a cell is identified by its scrambling code. Therefore, you must indicate during the import process which columns contain the scrambling code of cells and the scrambling code format (decimal or hexadecimal) used in the file.
Because a scrambling code can belong to several groups, you can also indicate from which group the scrambling code
has been selected.
You can import a single drive test data file or several drive test data files at the same time. If you regularly import drive test
data files of the same format, you can create an import configuration. The import configuration contains information that
defines the structure of the data in the drive test data file. By using the import configuration, you will not need to define the
data structure each time you import a new drive test data file.
To import one or several drive test data files:
2. Right-click the Drive Test Data folder. The context menu appears.
4. You can import one or several files. Select the file or files you want to open.
If you are importing more than one file, you can select contiguous files by clicking the first
file you want to import, pressing SHIFT and clicking the last file you want to import. You
can select non-contiguous files by pressing CTRL and clicking each file you want to import.
5. Click Open. The Import of Measurement Files dialogue appears.
Files with the extension PLN, as well as some FMT files (created with previous versions of
TEMS) are imported directly into Atoll; you will not be asked to define the data structure
using the Import of Measurement Files dialogue.
6. If you already have an import configuration defining the data structure of the imported file or files, you can select it
from the Import configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have
an import configuration, continue with step 7.
a. Under Import configuration, select an import configuration from the Import configuration list.
b. Continue with step 10.
When importing a drive test data path file, existing configurations are available in
the Files of type list of the Open dialogue, sorted according to their date of creation. After you have selected a file and clicked Open, Atoll automatically proposes
a configuration, if it recognises the extension. If several configurations are associated with an extension, Atoll chooses the first configuration in the list.
The defined configurations are stored, by default, in the file "NumMeasINIFile.ini",
located in the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters:
-
Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if
desired.
Under Receiver, set the Height of the receiver antenna and the Gain and Losses.
Under Measurement Conditions,
-
Units: Select the measurement units used.

Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document. If the
coordinates used in the file you are importing are different than the coordinates used in the Atoll document,
you must click the Browse button (
) and select the coordinate system used in the drive test data file. Atoll
will then convert the data imported to the coordinate system used in the Atoll document.
8. Click the Setup tab (see Figure 6.86).
380

AT310_UMU_E0
Figure 6.86: The Setup tab of the Import of Measurement Files dialogue
a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Decimal
Symbol used in the file.
b. Click the Setup button to link file columns and internal Atoll fields. The Drive Test Data Setup dialogue appears.
c. Under Measurement point position, select the columns in the imported file that give the X-Coordinates and the
Y-Coordinates of each point in the drive test data file.
You can also identify the columns containing the XY coordinates of each point in the drive
test data file by selecting them from the Field row of the table on the Setup tab.
d. If you are importing data using Scrambling Codes as cell identifiers:

i.
Select By Scrambling Code under Transmitter Identification.
i.
In the Scrambling Code Identifier box, enter a string that is found in the column names identifying the scrambling code of scanned cells. For example, if the string "SC" is found in the column names identifying the scrambling code of scanned cells, enter it here. Atoll will then search for columns with this string in the column
name.
ii. From the SC Format list, select the scrambling code format, either "Decimal" or "Hexadecimal."
iii. In the Scrambling Code Group Identifier box, enter a string that must be found in the column names identifying the scrambling code group of scanned cells. For example, if the string "SC_Group" is found in the column
names identifying the scrambling code group of scanned cells, enter it here. Atoll will then search for columns
with this string in the column name.
If there is no scrambling code group information contained in the drive test data file, leave the Scrambling
Code Group Identifier box empty.
e. If you are importing data using Cell ID as cell identifiers:
i.
Select By Cell ID under Transmitter Identification.
ii. In the Cell ID Identifier box, enter a string found in the column name identifying the cell Ids of scanned cells.
For example, if the string "Cell_ID" is found in the column names identifying the Cell_ID of scanned cells, enter
it here. Atoll will then search for the column with this string in the column name.
f.
Click OK to close the Drive Test Data Setup dialogue.
381

Forsk 2011
If you have correctly entered the information under File on the Setup tab, and the
necessary values in the Drive Test Data Setup dialogue, Atoll should recognize all
columns in the imported file. If not, you can click the name of the column in the
table in the Field row and select the column name. For each field, you must ensure
that each column has the correct data type in order for the data to be correctly
interpreted. The default value under Type is "<Ignore>". If a column is marked with
"<Ignore>", it will not be imported.
The data in the file must be structured so that the columns identifying the scrambling code group and the scrambling code are placed before the data columns for
each cell. Otherwise Atoll will not be able to properly import the file.
9. If you want to save the definition of the data structure so that you can use it again, you can save it as an import configuration:
a. On the Setup tab, under Import configuration, click Save. The Configuration dialogue appears.
b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atolls installation folder. If
you cannot write into that folder, you can click the Browse button to choose a different location.
c. Enter a Configuration Name and an Extension of the files that this import configuration will describe (for example,
"*.csv").
d. Click OK.
Atoll will now select this import configuration automatically every time you import a drive test data path file with
the selected extension. If you import a file with the same structure but a different extension, you will be able to
select this import configuration from the Configuration list.
You do not have to complete the import procedure to save the import configuration and have it available for future use.
When importing a CW measurement file, you can expand the NumMeasINIfile.ini
file by clicking the Expand button ( ) in front of the file under Import configuration to display all the available import configurations. When selecting the appropriate configuration, the associations are automatically made in the table at the
bottom of the dialogue.
You can delete an existing import configuration by selecting the import configuration under Import configuration and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The mobile
data are imported into the current Atoll document.
6.5.2 Displaying Drive Test Data

When you have imported the drive test data into the current Atoll document, you can display it in the map window. Then,
you can select individual drive test data points to see information about the active set at that location.
To display information about a single drive test data point:
) to expand the Drive Test Data folder.
3. Select the display check box beside the drive test data you want to display in the map window. The drive test data is
displayed.
4. Click and hold the drive test data point on which you want active set information. Atoll displays an arrow pointing
towards the serving cells (see Figure 6.88 on page 387), with a number identifying the server as numbered in the drive
test data. If the transmitter display type is "Automatic," both the number and the arrow are displayed in the same
colour as the transmitter. For information on changing the display type to "Automatic," see "Defining the Display
Type" on page 24.
6.5.3 Defining the Display of a Drive Test Data Path

You can manage the display of drive test data paths using the Display dialogue. The points on a drive test data path can be
displayed according to any available attribute. You can also use the Display dialogue to manage permanent labels on the map,
tip text and the legend. In other words, the display of measurement paths can be defined in the same way as for sites, transmitters, etc.
382

AT310_UMU_E0
To display the Display tab of a drive test data paths Properties dialogue:
3. Right-click the drive test data path whose display you want to manage. The context menu appears.
4. Select Properties from the context menu,
Each point can be displayed by a unique attribute or according to:
a text or integer attribute (discrete value)

a numerical value (value interval).
In addition, you can display points by more than one criterion at a time using the Advanced option in the Display Type list.
When you select Advanced from the Display Type list, a dialogue opens in which you can define the following display for each
single point of the measurement path:
a symbol according to any attribute

a symbol colour according to any attribute
a symbol size according to any attribute
You can, for example, display a signal level in a certain colour, choose a symbol type for Transmitter 1 (a circle, triangle, cross,
etc.) and a symbol size according to the altitude.
Fast Display forces Atoll to use the lightest symbol to display the points. This is particularly useful when you have a very large number of points.
You can not use Advanced Display if the Fast Display check box has been selected.
You can sort drive test data paths in alphabetical order on the Network tab of the
Explorer window by right-clicking the Drive Test Data Path folder and selecting
Sort Alphabetically from the context menu.
You can save the display settings (such as colours and symbols) of a drive test data
path in a user configuration file to make them available for use on another drive
test data path. To save or load the user configuration file, click the Actions button
on the Display tab of the path properties dialogue and select Save or Load from
the Display Configuration submenu.
6.5.4 Network Verification

The imported drive test data is used to verify the UMTS HSPA network. To improve the relevance of the data, Atoll allows you
to filter out incompatible or inaccurate points. You can then use the data for coverage predictions, either by comparing the
imported measurements with previously calculated coverage predictions, or by creating new coverage predictions using the
imported drive test data.
"Filtering Incompatible Points Along Drive Test Data Paths" on page 383
"Creating Coverage Predictions from Drive Test Data Paths" on page 385
"Displaying Statistics Over a Drive Test Data Path" on page 386
"Extracting a Field From a Drive Test Data Path for a Transmitter" on page 387
"Analysing Data Variations Along the Path" on page 387.
6.5.4.1 Filtering Incompatible Points Along Drive Test Data Paths

When using a drive test data path, some measured points may present values that are too far outside of the median values
to be useful in calibration. As well, test paths may include test points in areas that are not representative of the drive test data
path as a whole. For example, a test path that includes two heavily populated areas might also include test points from the
more lightly populated region between the two.
In Atoll, you can filter out points that are incompatible with the points you are studying, either by filtering out the clutter
classes where the incompatible points are located, or by filtering out points according to their properties.
To filter out incompatible points by clutter class:
2. On the Network tab of the Explorer window, right-click the Drive Test Data on which you want to filter out incompatible points:
-
All drive test data measurements: Right-click the Drive Test Data folder.
383

Forsk 2011
Only one drive test data path: Click the Expand button ( ) to expand the Drive Test Data folder and right-click
the drive-test data path on which you want to filter out incompatible points.

3. Select Filter from the context menu. The Drive Test Data Filter dialogue appears.
4. In the Clutter classes window, under Filter, clear the check boxes of the clutter classes you want to filter out. Only the
clutter classes whose check box is selected will be taken into account.
5. If you want to keep the measurement points inside the focus zone, select the Use focus zone to filter check box.
6. If you want to permanently remove the measurement points outside the filter, select the Delete points outside filter
check box.
If you permanently delete measurement points and later want to use them, you will have to re-import the original
measurement data.
To filter out incompatible points using a filter:
2. On the Network tab of the Explorer window, right-click the Drive Test Data on which you want to filter out incompatible points:
-
All drive test data measurements: Right-click the Drive Test Data folder.
Only one drive test data path: Click the Expand button ( ) to expand the Drive Test Data folder and right-click
the drive-test data path on which you want to filter out incompatible points.

3. Select Filter from the context menu. The Drive Test Data Filter dialogue appears.
4. Click More. The Filter dialogue appears.
5. Click the Filter tab:
a. Select a Field from the list.
b. Under Values to include, you will find all the values represented in the selected field. Select the check boxes next
to the values you want to include in the filter. Click Clear All to clear all check boxes.
6. Click the Advanced tab:
a. In the Column row, select the name of the column to be filtered on from the list. Select as many columns as you
want (see Figure 6.87).
Figure 6.87: The Filter dialogue - Advanced tab

b. Underneath each column name, enter the criteria on which the column will be filtered as explained in the following table:
384
Formula
=X
value equal to X (X may be a number or characters)
<> X
value not equal to X (X may be a number or characters)
<X
numerical value is less than X

AT310_UMU_E0
Formula
>X
numerical value is greater than X
<=X
numerical value is less than or equal to X
>=X
numerical value is greater than or equal to X
*X*
text objects which contain X
*X
text objects which end with X
X*
text objects which start with X
7. Click OK to filter the data according to the criteria you have defined.
Filters are combined first horizontally, then vertically. For more information on filters, see "Advanced Data Filtering"
on page 72.
8. Click OK to apply the filter and close the dialogue.
You can update heights (of the DTM, and clutter heights) and the clutter class of drive test
data points after adding new geographic maps or modifying existing ones by selecting
Refresh Geo Data from the context menu of the Drive Test Data Paths folder.
6.5.4.2 Creating Coverage Predictions from Drive Test Data Paths

You can create the following coverage predictions for all transmitters on each point of a drive test data path:
Pilot signal level and coverage by signal level

Pilot Quality Analysis (Ec I0), service area (Eb Nt) downlink, and service area (Eb Nt) uplink.
To create a coverage prediction along a drive test data path:

3. Right-click the drive test data to which you want to add a coverage prediction. The context menu appears.
4. Select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears.
5. Under Save the selected prediction as a customised prediction, select one of the following coverage predictions and
click OK:
-
Coverage by Signal Level: Click the Conditions tab.

-
Pilot Quality Analysis (EcI0): Click the Conditions tab.

-
At the top of the Conditions tab, you can set the range of signal level to be calculated. Under Server, you can
select whether to calculate the signal level from all transmitters, or only the best or second-best signal. If you
choose to calculate the best or second-best signal, you can enter a Margin. If you select the Shadowing taken
into account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. Finally, you can select the Carrier to be studied.
On the Conditions tab, you can select which simulation to study in the Load Conditions list. Or you can select
a group of simulations and either select All to perform an average analysis of all simulations in the group based
on a Probability (from 0 to 1) or select Average to perform statistical analysis of all simulations.
If you want to perform the coverage prediction without a simulation, you can select "(Cells Table)" from Load
conditions. In this case, Atoll calculates the coverage prediction using the UL load factor and the DL total
power defined in the cell properties.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 252.
You must also select which Carrier is to be considered.
If you want the pilot signal quality prediction to consider shadowing, you can select the Shadowing taken into
Service Area Analysis (EbNt) (DL): Click the Conditions tab.

-
385

Forsk 2011
If you want the service area (Eb/Nt) coverage prediction to consider shadowing, you can select the Shadowing
taken into account check box and enter a percentage in the Cell edge coverage probability text box.
Service Area Analysis (EbNt) (UL): Click the Conditions tab.

-
If you want the service area (Eb/Nt) coverage prediction to consider shadowing, you can select the Shadowing
taken into account check box and enter a percentage in the Cell edge coverage probability text box.
6. When you have finished setting the parameters for the coverage prediction, click OK.
You can create a new coverage prediction by repeating the procedure from step 1. to step 6. for each new coverage
prediction.
7. When you have finished creating new coverage predictions for these drive test data, right-click the drive test data. The
8. Select Calculations > Calculate All the Predictions from the context menu.
A new column for each coverage prediction is added in the table for the drive test data. The column contains the
predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned to
the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Working with Calculations in Atoll).
You can display the information in these new columns in the Drive Test Data window. For more information on the
Drive Test Data window, see "Analysing Data Variations Along the Path" on page 387.
6.5.4.3 Displaying Statistics Over a Drive Test Data Path

Assuming some predictions have been calculated along a drive test data path, you can display the statistics between the measured and the predicted values on a specific measurement path.
To display the statistics for a specific drive test data path:
3. Right-click the drive test data from which you want to display comparative statistics. The context menu appears.
4. Select Display Statistics from the context menu. The Measurement and Prediction Fields Selection dialogue appears.
5. Select one or more transmitters from the For the following transmitters list.
6. Select the fields that you want to use for predictions from the Select the predicted values list. Only one type of value
can be compared at a time (signal level or quality).
7. Select the fields that you want to use for predictions the Select the measured values list. Only one type of value can
be compared at a time (signal level or quality). The measured and the selected values have to match up.
8. Enter the minimum and maximum Measured Values. Statistics are done with drive test data points where the measured values are within this specified range.
9. Click OK.
Atoll opens a dialogue in which the global statistics between measurements and predictions are given over all the filtered (or
not) points of the current drive test data path through the mean error, its standard deviation, the root mean square and the
error correlation factor. The statistics are also given per clutter class.
386

AT310_UMU_E0
6.5.4.4 Extracting a Field From a Drive Test Data Path for a Transmitter
You can extract a specific field for a specific transmitter on each point of an existing drive test data path. The extracted information will be added to a new column in the table for the drive test data.
To extract a field from a drive test data path:
3. Right-click the drive test data from which you want to extract a field. The context menu appears.
4. Select Focus on a Transmitter from the context menu. The Field Select for a Given Transmitter dialogue appears.
5. Select a transmitter from the On the Transmitter list.
6. Click the For the Fields list. The list opens.
7. Select the check box beside the field you want to extract for the selected transmitter.
Atoll can display the best server and up to six other servers in the active set. If you want to
display for example, the point signal level, remember to select the check box for the point
signal level for all servers in the For the Fields list. The new column will then display the
point signal level for the selected transmitter for all servers if a value exists.
8. Click OK. Atoll creates a new column in the drive test data path table for the selected transmitters and with the
selected values.
6.5.4.5 Analysing Data Variations Along the Path

In Atoll, you can analyse variations in data along any drive test data path using the Drive Test Data window. You can also use
the Drive Test Data window to see which cell is the serving cell for a given test point.
To analyse data variations using the Drive Test Data window.
3. Right-click the drive test data you want to analyse. The context menu appears.
4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 6.88).
Figure 6.88: The Drive Test Data window

5. Click Display at the top of the Drive Test Data window. The Display Parameters dialogue appears (see Figure 6.89).
387

Forsk 2011
Figure 6.89: The Drive Test Data window

6. In the Display Parameters dialogue:
-
Select the check box next to any field you want to display in the Drive Test Data window.
If you want, you can change the display colour by clicking the colour in the Colour column and selecting a new
colour from the palette that appears.
Click OK to close the Display Parameters dialogue.
You can change the display status or the colour of more than one field at a time. You can
select contiguous fields by clicking the first field, pressing SHIFT and clicking the last field
you want to import. You can select non-contiguous fields by pressing CTRL and clicking
each field. You can then change the display status or the colour by right-clicking on the
selected fields and selecting the choice from the context menu.
The selected fields are displayed in the Drive Test Data window.
7. You can display the data in the drive test data path in two ways:
-
Click the values in the Drive Test Data window.

Click the points on the drive test data path in the map window.
The drive test data path appears in the map window as an arrow pointing towards the serving cell, with a number identifying the best server (see Figure 6.88 on page 387). If the transmitter display type is "Automatic," both the number
and the arrow are displayed in the same colour as the transmitter. For information on changing the display type to
"Automatic," see "Defining the Display Type" on page 24.
8. You can display a second Y-axis on the right side of the window in order to display the values of a variable with different orders of magnitude than the ones selected in the Display Parameters dialogue. You can select the secondary
Y-axis from the right-hand list on the top of the Drive Test Data window. The selected values are displayed in the colours defined for this variable in the Display Parameters dialogue.
9. You can change the zoom level of the Drive Test Data window display in the Drive Test Data window in the following
ways:
-
Zoom in or out:
i.
Right-click the Drive Test Data window.
ii. Select Zoom In or Zoom Out from the context menu.

-
Select the data to zoom in on:

i.
Right-click the Drive Test Data window on one end of the range of data you want to zoom in on.
ii. Select First Zoom Point from the context menu.

iii. Right-click the Drive Test Data window on the other end of the range of data you want to zoom in on.
iv. Select Last Zoom Point from the context menu. The Drive Test Data window zooms in on the data between
the first zoom point and the last zoom point.
10. Click the data in the Drive Test Data window to display the selected point in the map window. Atoll will recentre the
map window on the selected point if it is not presently visible.
388

AT310_UMU_E0
If you open the table for the drive test data you are displaying in the Drive Test Data
window, Atoll will automatically display in the table the data for the point that is
displayed in the map and in the Drive Test Data window (see Figure 6.88 on page 387).
6.5.5 Exporting a Drive Test Data Path

You can export drive test data paths to vector files.
To export a drive test data path to a vector file:
3. Right-click the drive test data path you want to export. The context menu appears.
4. Select Export from the context menu. The Save As dialogue appears.
5. Enter a File name for the drive test data path and select a format from the Save as type list.
6. Click Save. The drive test data path is exported and saved in the file.
6.5.6 Extracting CW Measurements from Drive Test Data

You can generate CW measurements from drive test data paths and extract the results to the CW Measurements folder.
To generate CW measurement from a drive test data path:
3. Right-click the drive test data path you want to export. The context menu appears.
4. Select Extract CW Measurements from the context menu. The CW Measurement Extraction dialogue appears.
5. Under Extract CW Measurements:
a. Select one or more transmitters from the For the following transmitters list.
b. Select the field that contains the information that you want to export to CW measurements from the Select the
measured signal levels list.
6. Under Extraction Parameters of CW Measurement Paths:
a. Enter the Min. number of points to extract per measurement path. CW measurements are not created for transmitters that have fewer points than this number.
b. Enter the minimum and maximum Measured Signal Levels. CW measurements are created with drive test data
points where the signal levels are within this specified range.
7. Click OK. Atoll creates new CW measurements for transmitters satisfying the parameters set in the CW Measurement
Extraction dialogue.
For more information about CW measurements, see the Model Calibration Guide.
6.5.7 Printing and Exporting the Drive Test Data Window

You can print or export the contents of the Drive Test Data window, using the context menu in the Drive Test Data window.
To print or export the contents of the Drive Test Data window:
3. Right-click the drive test data you want to analyse. The context menu appears.
4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 6.88 on
page 387).
5. Define the display parameters and zoom level as explained in "Analysing Data Variations Along the Path" on page 387.
6. Right-click the Drive Test Data window. The context menu appears.
To export the Drive Test Data window:
a. Select Copy from the context menu.
b. Open the document into which you want to paste the contents of the Drive Test Data window.
389

Forsk 2011
c. Paste the contents of the Drive Test Data window into the new document.
To print the Drive Test Data window:
a. Select Print from the context menu. The Print dialogue appears.
b. Click OK to print the contents of the Drive Test Data window.
6.6 Co-planning UMTS Networks with Other Networks

Atoll is a multi-technology radio network planning tool. You can work on several technologies at the same time, and several
network scenarios can be designed for any given area: a country, a region, a city, etc. For example, you can design a UMTS
and a GSM network for the same area in Atoll, and then work with Atolls co-planning features to study the mutual impacts
of the two networks.
Before starting a co-planning project in Atoll, the Atoll administrator must perform the
pre-requisite tasks that are relevant for your project as described in the Administrator
Manual.
Sectors of both networks can share the same sites database. You can display base stations (sites and sectors), geographic data,
and coverage predictions, etc., of one network in the other networks Atoll document. You can also study inter-technology
handovers by performing inter-technology neighbour allocations, manually or automatically. Inter-technology neighbours are
allocated on criteria such as the distance between sectors or overlapping coverage. In addition, you can optimise the settings
of the two networks using Atolls Automatic Cell Planning (ACP) module.
"Switching to Co-planning Mode" on page 390

"Working with Coverage Predictions in a Co-Planning Project" on page 392
"Performing Inter-Technology Neighbour Allocation" on page 396
"Creating a UMTS Sector From a Sector in the Other Network" on page 407
"Using ACP in a Co-planning Project" on page 407
"Ending Co-planning Mode" on page 408.
6.6.1 Switching to Co-planning Mode

Before starting a co-planning project, you must have two networks designed for a given area, i.e., you must have a UMTS Atoll
document and an Atoll document for the other network. Atoll switches to co-planning mode as soon as the two documents
are linked together. In the following sections, the UMTS document will be referred to as the main document, and the other
document as the linked document. Atoll does not establish any restriction on which is the main document and which is the
linked document.
Before starting a co-planning project, make sure that your main and linked documents
have the same geographic coordinate systems.
To switch to co-planning mode:

1. Open the main document.
-
Select File > Open or File > New > From an Existing Database.
2. Link the other document with the open main document.

a. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document.
b. Select Document > Link > Link With. The Link With dialogue appears.
c. Select the document to be linked.
d. Click Open.
The selected document is opened in the same Atoll session as the main document and the two documents are linked.
The Explorer window of the main document now contains a folder named Transmitters in [linked document], where
[linked document] is the name of the linked document and another folder named Predictions in [linked document].
390

AT310_UMU_E0
By default, only the Transmitters and Predictions folders of the linked document appear
in the main document. If you want the Sites folder of the linked document to appear in the
main document as well, you can set an option in the atoll.ini file. For information on setting
options in the atoll.ini file, see the Administrator Manual.
As soon as a link is created between the two documents, Atoll switches to co-planning mode and Atolls co-planning features
are now available.
When you are working on a co-planning document, Atoll facilitates working on two different but linked documents by
synchronising the display in the map window between both documents. Atoll syncronises the display for the following:
Geographic data: Atoll synchronises the display of geographic data such as clutter classes and the DTM. If you select
or deselect one type of geographic data, Atoll makes the corresponding change in the linked document.
Zones: Atoll synchronises the display of filtering, focus, computation, hot spot, printing, and geographic export zones.
If you select or deselect one type of zone, Atoll makes the corresponding change in the linked document.
Map display: Atoll co-ordinates the display of the map in the map window. When you move the map, or change the
zoom level in one document, Atoll makes the corresponding changes in the linked document.
Point analysis: When you use the Point Analysis tool, Atoll co-ordinates the display on both the working document
and the linked document. You can select a point and view the profile in the main document and then switch to the
linked document to make an analysis on the same profile but in the linked document.
Displaying Both Networks in the Same Atoll Document

After you have switched to co-planning mode as explained in "Switching to Co-planning Mode" on page 390, transmitters and
predictions from the linked document are displayed in the main document. If you want, you can display other items or folders
from the Explorer window of the linked document to the Explorer window of the main document (e.g., you can display GSM
sites and measurement paths in a UMTS document).
To display sites from the linked document in the main document:
1. Click the linked documents map window. The linked documents map window becomes active and the Explorer
window shows the contents of the linked document.
4. Select Make Accessible In from the context menu, and select the name of the main document from the submenu that
opens.
The Sites folder of the linked document is now available in the main document. The Explorer window of the main document
now contains a folder named Sites in [linked document], where [linked document] is the name of the linked document. If you
want the Sites folder of the linked document to appear in the main document automatically, you can set an option in the
atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual.
The same process can be used to link other folders in one document, folders such as CW Measurements, Drive Test Data,
Clutter classes, Traffic Maps, and DTM, etc., in the other document.
Once the folders are linked, you can access their properties and the properties of the items in the folders from either of the
two documents. Any changes you make in the linked document are taken into account in the both the linked and main documents. However, the only changes in the working document that are taken into account in the linked document are changes
made to the linked folders (e.g., the Transmitters and Predictions folders).
If you close the linked document, Atoll displays a warning icon ( ) in the main documents Explorer window, and the linked
items are no longer accessible from the main document. You can load the linked document in Atoll again by right-clicking the
linked item in the Explorer window of the main document, and selecting Open Linked Document.
The administrator can create and set a configuration file for the display parameters of linked and main document transmitters
in order to enable you to distinguish them on the map and to be able to select them on the map using the mouse. If such a
configuration file has not been set up, you can choose different symbols, sizes and colours for the linked and the main document transmitters. For more information on folder configurations, see "Folder Configurations" on page 80. You can also set
the tip text to enable you to distinguish the objects and data displayed on the map. For more information on tip text, see
"Defining the Object Type Tip Text" on page 26.
In order to more easily view differences between the networks, you can also change the order of the folders or items in the
Explorer window. For more information on changing the order of items in the Explorer window, see "Working with Layers
Figure 6.90 shows an example of UMTS transmitters with labels, and GSM transmitter data displayed in tip text.
391

Forsk 2011
Figure 6.90: GSM and UMTS Transmitters displayed on the map
6.6.2 Working with Coverage Predictions in a Co-Planning Project

Atoll provides you with features that enable you to work with coverage predictions in your co-planning project. You can
modify the properties of coverage predictions in the linked document from within the main document, and calculate coverage
predictions in both documents at the same time. You can also study and compare the coverage predictions of the two
networks.
"Updating Coverage Predictions" on page 392

"Analysing Coverage Predictions" on page 393.
6.6.2.1 Updating Coverage Predictions

You can access the properties of the coverage predictions in the linked Predictions folder in the main documents Explorer
window. After modifying the linked coverage prediction properties, you can update them from the main document.
To update a linked coverage prediction:
1. Click the main documents map window. The main documents map window becomes active and the Explorer window
shows the contents of the main document and the linked folders from the linked document.
3. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the
name of the linked document.
4. Right-click the linked coverage prediction whose properties you want to modify. The context menu appears.
5. Select Properties from the context menu. The coverage prediction Properties dialogue appears.
6. Modify the calculation and display parameters of the coverage prediction.
8. Click the Calculate button (
) in the toolbar.
When you click the Calculate button, Atollfirst calculates uncalculated and invalid path loss matrices and then
unlocked coverage predictions in the main and linked Predictions folders.
When you have several unlocked coverage predictions defined in the main and linked Predictions folders, Atoll calculates
them one after the other. For information on locking and unlocking coverage predictions, see "Locking Coverage Predictions"
on page 192.
If you want, you can make Atoll recalculate all path loss matrices, including valid ones, before calculating unlocked coverage
predictions in the main and linked Predictions folders.
To force Atoll to recalculate all path loss matrices before calculating coverage predictions:
Click the Force Calculate button (
) in the toolbar.
When you click the Force Calculate button, Atoll first removes existing path loss matrices, recalculates them and then
calculates unlocked coverages predictions defined in the main and linked Predictions folders.
392

AT310_UMU_E0
To prevent Atoll from calculating coverage predictions in the linked Predictions folder, you
can set an option in the atoll.ini file. For information on setting options in the atoll.ini file,
see the Administrator Manual.
6.6.2.2 Analysing Coverage Predictions

In Atoll, you can analyse coverage predictions of the two networks together. You can display information about coverage
predictions in the main and the linked documents in the Legend window, use tip text to get information on displayed coverage
predictions, compare coverage areas by overlaying the coverage predictions in the map window, and study the differences
between the coverage areas by creating coverage comparisons.
If several coverage predictions are visible on the map, it might be difficult to clearly see the results of the coverage prediction
you want to analyse. You can select which predictions to display or to hide by selecting or clearing the display check box. For
information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 18.
6.6.2.2.1
"Co-Planning Coverage Analysis Process" on page 393

"Displaying the Legend Window" on page 393
"Comparing Coverage Prediction Results Using Tip Text" on page 393
"Comparing Coverage Areas by Overlaying Coverage Predictions" on page 394
"Studying Differences Between Coverage Areas" on page 395.
Co-Planning Coverage Analysis Process

The aim of coverage analysis in a co-planning project is to compare the coverage areas of the two networks and to analyse
the impact of changes made in one network on the other. Changes made to the sectors of one network might also have an
impact on sectors in the other network if the sectors in the two networks share some antenna parameters. You can carry out
a coverage analysis with Atoll to find the impact of these changes.
The recommended process for analysing coverage areas, and the effect of parameter modifications in one network on the
other, is as follows:
1. Create and calculate a Coverage by Transmitter (best server with 0 dB margin) coverage prediction and a Coverage
by Signal Level coverage prediction in the main document. For more information, see "Making a Coverage Prediction
by Transmitter" on page 239 and "Studying Signal Level Coverage" on page 229.
2. Create and calculate a Coverage by Transmitter (best server with 0 dB margin) coverage prediction and a Coverage
by Signal Level coverage prediction in the linked document.
3. Choose display settings for the coverage predictions and tip text contents that will allow you to easily interpret the
predictions displayed in the map window. This can help you to quickly assess information graphically and using the
mouse. You can change the display settings of the coverage predictions on the Display tab of each coverage predictions Properties dialogue.
4. Make the two new coverage predictions in the linked document accessible in the main document as described in "Displaying Both Networks in the Same Atoll Document" on page 391.
5. Optimise the main network by changing parameters such as antenna azimuth and tilt or the pilot power. You can use
a tool such as the Atoll ACP to optimise the network.
Changes made to the shared antenna parameters will be automatically propagated to the linked document.
6. Calculate the coverage predictions in the main document again to compare the effects of the changes you made with
the linked coverage predictions.
For information on comparing coverage predictions, see "Comparing Coverage Areas by Overlaying Coverage Predictions" on page 394 and "Studying Differences Between Coverage Areas" on page 395.
7. Calculate the linked coverage predictions again to study the effects of the changes on the linked coverage predictions.
6.6.2.2.2
Displaying the Legend Window

When you create a coverage prediction, you can add the displayed values of the coverage prediction to the legend by selecting
the Add to Legend check box on the Display tab.
6.6.2.2.3
Select View > Legend Window. The Legend window is displayed, with the values for each displayed coverage prediction in the main and linked Predictions folders, identified by the name of the coverage prediction.
Comparing Coverage Prediction Results Using Tip Text

You can compare coverage predictions by placing the pointer over an area of the coverage prediction to read the information
displayed in the tip text. Atoll displays information for all displayed coverage predictions in both the working and the linked
393

Forsk 2011
documents. The information displayed is defined by the settings you made on the Display tab when you created the coverage
prediction (step 3. of "Analysing Coverage Predictions" on page 393).
To get coverage prediction results in the form of tip text:
In the map window, place the pointer over the area of the coverage prediction that you want more information on.
After a brief pause, the tip text appears with the information defined on all displayed coverage predictions in both the
working and the linked documents (see Figure 6.21). The tip text for the working document is on top and the tip text
for the linked document, with the linked document identified by name is on the bottom.
Figure 6.91: Comparing coverage prediction results using tip text
6.6.2.2.4
Comparing Coverage Areas by Overlaying Coverage Predictions

You can compare the coverage areas of the main and linked documents by overlaying coverage predictions in the map
window.
To compare coverage areas by overlaying coverage predictions in the map window:
4. Select the visibility check box to the left of the coverage prediction of the main document you want to display in the
map window. The coverage prediction is dislayed on the map.
5. Right-click the coverage prediction. The context menu appears.
8. Modify the display parameters of the coverage prediction. For information on defining display properties, see "Display
Properties of Objects" on page 23.
9. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the
name of the linked document.
10. Select the visibility check box to the left of the linked coverage prediction you want to display in the map window. The
coverage prediction is dislayed on the map.
11. Right-click the coverage prediction. The context menu appears.
13. Modify the display parameters of the coverage prediction.
14. Calculate the two coverage predictions again, if needed.
Figure 6.92 and Figure 6.93 show an example of overlayed UMTS and GSM coverage predictions.
To more easily view differences between the coverage areas, you can also change the order of the Predictions folders in the
Explorer window. For more information on changing the order of items in the Explorer window, see "Working with Layers
394

AT310_UMU_E0
Figure 6.92: UMTS coverage by transmitter pink contours with no interior
Figure 6.93: GSM coverage by transmitter high transparency with full interior coloured by BCCH, with BCCH/BSIC
information available in tip text
6.6.2.2.5
Studying Differences Between Coverage Areas

You can compare coverage predictions to find differences in coverage areas.
To compare coverage predictions:
4. Right-click the coverage prediction of the main document you want to compare. The context menu appears.
5. Select Compare With > [linked coverage prediction] from the context menu, where [linked coverage prediction] is
the coverage prediction in the linked document you want to compare with the coverage prediction of the main document. The Comparison Properties dialogue opens.
6. Select the display parameters of the comparison and add a comment if you want.
7. Click OK.
395

Forsk 2011
The two coverage predictions are compared and a comparison coverage prediction is added to the main documents Predictions folder.
For more information on coverage prediction comparison, see "Comparing Coverage Predictions: Examples" on page 246.
6.6.3 Performing Inter-Technology Neighbour Allocation

Atoll enables you to carry out inter-technology neighbour planning. For example, you can study handovers between a UMTS
and a GSM network in Atoll by allocating neighbour GSM sectors to UMTS cells.
"Setting Inter-Technology Exceptional Pairs" on page 396

"Displaying Inter-Technology Exceptional Pairs on the Map" on page 397
"Adding and Removing Inter-Technology Exceptional Pairs on the Map" on page 397
"Configuring Importance Factors for Inter-Technology Neighbours" on page 398
"Allocating Inter-Technology Neighbours Automatically" on page 398
"Displaying Inter-Technology Neighbours on the Map" on page 400
"Allocating and Deleting Inter-Technology Neighbours per Cell" on page 401
"Calculating the Importance of Existing Inter-technology Neighbours" on page 404
"Checking the Consistency of the Inter-technology Neighbour Plan" on page 406.
In the sections listed above, it is assumed that Atoll is already in co-planning mode, and the Atoll documents corresponding
to the two networks have already been linked. For more information on switching to co-planning mode, see "Switching to Coplanning Mode" on page 390.
6.6.3.1 Setting Inter-Technology Exceptional Pairs

You can set inter-technology neighbour constraints by defining exceptional pairs in Atoll. These constraints can be taken into
account when inter-technology neighbours are automatically or manually allocated.
To define inter-technology exceptional pairs between the main document and the linked document:
1. Click the main documents map window.
4. Select Neighbours > Inter-technology > Exceptional Pairs from the context menu. The Inter-technology Neighbours
Exceptional Pairs table appears.
5. Enter one exceptional pair per row of the table. A cell can have more than one exceptional pair.
6. For each exceptional pair, select:
a. Cell: The name of the cell in the main document as the first part of the exceptional pair. The names of all the cells
in the main document are available in the list.
b. Neighbour: The name of the neighbour in the linked document as the second part of the exceptional pair. The
names of all the transmitters/cells in the linked document are available in the list.
c. Status: The status indicates whether the neighbour should always (forced) or never (forbidden) be considered as
a neighbour of the cell.
d. Atoll fills the Number and Distance (m) fields automatically.
In GSM, neighbours and exceptional pairs are allocated by transmitter (i.e., by sector).
You can access a cells inter-technology neighbours and exceptional pairs by using its Properties dialogue.
To open a cells Properties dialogue:
4. Double-click the row corresponding to the cell whose properties you want to access. The cells Properties dialogue
appears.
5. Click the Inter-Technology Neighbours tab.
In GSM, the Inter-technology Neighbours tab is found on the transmitters Properties dialogue.
396

AT310_UMU_E0
6.6.3.2 Displaying Inter-Technology Exceptional Pairs on the Map

You can display inter-technology exceptional pairs on the map in order to study the forced and forbidden neighbour relations
defined in the Inter-technology Exceptional Pairs table.
To display exceptional pairs defined between the main and the linked documents:
4. Select Neighbours > Inter-technology > Display Options from the context menu. The Neighbour Display dialogue
appears.
5. Under Inter-technology Neighbours, select the Display Links check box.
6. Under Advanced, select which exceptional pair links to display:
-
Outwards Non-Symmetric: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document.
Inwards Non-Symmetric: Selecting this option displays an exceptional pair link for each transmitter/cell in the
linked document that has an exceptional pair defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document.
Symmetric Links: Selecting this option displays an exceptional pair link for each cell in the main document that has
an exceptional pair defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked
document also has the cell of the main document in its exceptional pair list. These links are represented with
straight black lines.
appears.
8. Select Forced Neighbours or Forbidden Neighbours from the menu. The exceptional pair of a cell will be displayed
when you select a transmitter.
) in the Radio Planning toolbar. Exceptional pairs are now displayed
on the map. Exceptional pairs will remain displayed until you click the Visual Management button again.
10. Click a transmitter on the map to show its exceptional pair links. When there is more than one cell on the transmitter,
The exceptional pair links can be displayed even if you do not have neighbours allocated. If you select the Display Links check
box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology exceptional pairs on the
map.
6.6.3.3 Adding and Removing Inter-Technology Exceptional Pairs on the Map

You can set inter-technology exceptional pairs using the mouse. Atoll adds or removes forced or forbidden exceptional pairs
depending on the display option set, i.e., Forced Neighbours or Forbidden Neighbours.
Before you can add or remove exceptional pairs using the mouse, you must activate the display of exceptional pairs on the
map as explained in "Displaying Inter-Technology Exceptional Pairs on the Map" on page 397.
To add a symmetric forced or forbidden exceptional pair:
2. Press SHIFT and click the transmitter with which you want to set an exceptional pair. Atoll adds both transmitters to
the list of inter-technology exceptional pairs of the other transmitter.
To remove a symmetric forced or forbidden exceptional pair:
2. Press SHIFT and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes both
transmitters from the list of inter-technology exceptional pairs of the other transmitter.
397

Forsk 2011
To add an outwards forced or forbidden exceptional pair:

2. Press CTRL and click the transmitter with which you want to set an exceptional pair. Atoll adds the reference transmitter to the list of inter-technology exceptional pairs of the other transmitter.
To remove an outwards forced or forbidden exceptional pair:
2. Press CTRL and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes the reference transmitter from the list of inter-technology exceptional pairs of the other transmitter.
To add an inwards forced or forbidden exceptional pair:
Click the reference transmitter on the map. Atoll displays its neighbour relations.
-
If the two transmitters already have a symmetric exceptional pair relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric exceptional pair relation.
If there is no existing exceptional pair relation between the two transmitters, first create a symmetric exceptional
pair relation between the two transmitters, and then press CTRL and click the other transmitter. Atoll converts
the symmetric relation to an inwards non-symmetric exceptional pair relation.
To remove an inwards forced or forbidden exceptional pair:

2. Press SHIFT and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes the
transmitter from the inter-technology exceptional pairs list of the other transmitter.
When there is more than one cell on the transmitter, clicking the transmitter in the map
window opens a context menu allowing you to select the cell you want (see "Selecting One
of Several Transmitters" on page 21).
6.6.3.4 Configuring Importance Factors for Inter-Technology Neighbours

You can define the relative importance of the factors that Atoll uses to evaluate possible inter-technology neighbours (for
information on how Atoll calculates importance, see the Technical Reference Guide).
To configure the importance factors for inter-technology neighbours:
3. Select Neighbours > Inter-technology > Configure Importance from the context menu. The Neighbour Importance
Weighting dialogue appears.
4. Select the Inter-technology Neighbours tab. On the Inter-technology Neighbours tab, you can set the following
importance factors: start here
-
The Adjacency factor is not used when calculating the importance of inter-technology
neighbours.
as neighbours check box when performing automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Inter-Technology Neighbours Automatically" on page 398.
5. Click OK.
6.6.3.5 Allocating Inter-Technology Neighbours Automatically

Atoll can automatically determine handover relations between networks of different technologies, for example, UMTS and
GSM. In this case, inter-technology handovers from UMTS to GSM may occur when the UMTS coverage is not continuous. The
networks overall coverage is extended by a UMTS-to-GSM handover. Atoll can automatically determine neighbours in the
linked document for cells in the main document and vice versa. Inter-technology neighbours are stored in the database.
398

AT310_UMU_E0
By setting an option in the atoll.ini file, you can prevent Atoll from allocating inter-technology neighbours to cells located on sites whose equipment does not support the
compressed mode. For more information, see the Administrator Manual.
To automatically allocate neighbours in the linked document for cells in the main document:
4. Select Neighbours > Inter-technology > Automatic Allocation from the context menu. The Automatic Neighbour
5. Click the Inter-technology Neighbours tab.
6. Define the maximum distance between the reference cell and a possible neighbour in the Max Inter-site Distance box.
7. Define the maximum number of inter-technology neighbours that can be allocated to a cell in the Max Number of
Neighbours box. This value can be either set here for all the cells, or specified for each cell in the Cells table.
8. Clear the Use Overlapping Coverage check box in order to base the neighbour allocation on a distance criterion and
continue with step 9. Otherwise, select the Use Overlapping Coverage check box if you want to base the neighbour
allocation on coverage conditions.
a. Click the Define button to change the coverage conditions for the cells in the main document. The UMTS Coverage
Conditions dialogue appears.
In the UMTS Coverage Conditions dialogue, you can change the following parameters:
-
Min. pilot signal level: Enter the minimum pilot signal level which must be provided by the reference cell.
Min. Ec/Io: Enter the minimum Ec/Io which must be provided by the reference cell.
Ec/Io margin: Enter the Ec/Io margin relative to the Ec/Io of the best server. The reference cell is either the
best server in terms of pilot quality or a cell of the active set.
Max. Ec/Io: Select the Max. Ec/Io option and enter the maximum Ec/Io which must not be exceeded by the
reference cell.
DL load contributing to Io: You can select whether Atoll should use a Global Value (% Pmax) of the downlink
load for all the cells, or the downlink loads Defined per Cell.
Indoor coverage: If desired, select the Indoor coverage check box. Atoll will then calculate additional losses
for indoor coverage.
b. Click OK to save your modifications and close the Coverage Conditions dialogue.
c. Click the Define button to change the coverage conditions for the transmitters/cells in the linked document.
If the linked document is a GSM document, the GSM Coverage Conditions dialogue appears. In the GSM Coverage
Conditions dialogue, you can change the following parameters:
-
Min. BCCH Signal Level: Enter the minimum BCCH signal level which must be provided by the GSM transmitter.
Margin: Enter the margin relative to the BCCH signal level of the best server. The BCCH signal level of the
neighbour transmitter is either the highest one or within a margin of the highest one.
Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a
Cell Edge Coverage Probability.
Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses
If the linked document is an LTE document, the LTE Coverage Conditions dialogue appears. In the LTE Coverage
-
Margin: Enter the margin relative to the reference signal level of the best server. The reference signal level of
the neighbour transmitter is either the highest one or within a margin of the highest one.
399

Forsk 2011
d. Click OK to save your modifications and close the Coverage Conditions dialogue.
e. In the % Min. Covered Area box, enter the minimum percentage of the cells coverage area that the neighbours
coverage area should also cover to be considered as a neighbour.
9. Under Calculation Options, define the following:
-
CDMA Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers;
Atoll will allocate neighbours to cells using the selected carriers.
Force co-site as neighbours: Selecting the Force co-site as neighbours check box will include the co-site transmitters/cells in the neighbour list of the UMTS cell. The check box is automatically selected when the neighbour allocation is based on distance.
Force exceptional pairs: Selecting the Force exceptional pairs check box will apply the inter-technology exceptional pair criteria on the neighbours list of the UMTS cell.
Delete existing neighbours: Selecting the Delete existing neighbours check box will delete all existing neighbours
in the neighbours list and perform a clean neighbour allocation. If the Delete existing neighbours check box is not
selected, Atoll keeps the existing neighbours in the list.
10. Click the Calculate button to start calculations.

11. Once the calculations finish, Atoll displays the list of neighbours in the Results section. The results include the names
of the neighbours, the number of neighbours of each cell, and the reason they are included in the neighbours list. The
reasons include:
Reason
Description
When
Exceptional Pair
Neighbour relation is defined as an exceptional pair.
Force exceptional pairs is

selected
Co-site
The neighbour is located at the same site as the reference

cell.
Force co-site as neighbours is

selected
Distance
The neighbour is within the maximum distance from the

reference cell.
Use coverage overlapping is

not selected
% of covered area
and overlapping area
Neighbour relation that fulfils coverage conditions.
Use coverage overlapping is

selected
Existing
The neighbour relation existed before running the automatic

allocation.
Reset is not selected
12. Select the check box in the Commit column of the Results section to choose the inter-technology neighbours you want
to assign to cells.
At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document.
To compare the proposed and existing neighbour lists:
-
Click Compare. The list of automatically allocated neighbours, whose Commit check box is selected, is compared
with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt which appears at the end of the comparison. This file lists:
-
The document name and the neighbour allocation type,

results compared to the existing neighbour relations) and the list of these relations,
results compared to the existing neighbour relations) and the list of these relations,
13. Click the Commit button. The allocated neighbours are saved in the Intra-technology Neighbours tab of each cell.
14. Click Close.
6.6.3.6 Displaying Inter-Technology Neighbours on the Map

You can display inter-technology neighbours on the map in order to study the inter-technology handover scenarios.
To display neighbours in the linked document for cells in the main document:
400

AT310_UMU_E0
3. Select Neighbours > Inter-technology > Display Options from the context menu. The Neighbour Display dialogue
appears.
4. Under Inter-technology Neighbours, select the Display Links check box.
5. Under Advanced, select the neighbour links to display:
-
Outwards Non-Symmetric: Shows a neighbour link for each cell in the main document that has a neighbour
defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of
the same colour as the transmitter in the main document.
Inwards Non-Symmetric: Shows a neighbour link for each transmitter/cell in the linked document that has a
neighbour defined with a cell in the main document. These links are represented with straight dashed lines of the
same colour as the transmitter in the linked document.
Symmetric Links: Shows a neighbour link for each cell in the main document that has a neighbour defined with a
transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the
main document in its neighbours list. These links are represented with straight black lines.
appears.
7. Select Neighbours as the type of neighbour links to display.

) in the Radio Planning toolbar. Neighbours are now displayed on the
map. Neighbours and displayed until you click the Edit Relations on the Map button again.
9. Click a transmitter on the map to show its neighbour links. When there is more than one cell on the transmitter,
If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intratechnology neighbours on the map. The figure below shows the intra- and inter-technology neighbours of the transmitter
Site22_2.
6.6.3.7 Allocating and Deleting Inter-Technology Neighbours per Cell

Although you can let Atoll allocate inter-technology neighbours automatically, you can adjust the overall allocation of intertechnology neighbours by allocating or deleting inter-technology neighbours per cell. You can allocate or delete inter-technology neighbours directly on the map, or using the Cells tab of the Transmitter Properties dialogue, or using the Inter-technology Neighbours table.
"Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on
page 402.
"Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table" on page 402.
"Allocating and Removing Inter-Technology Neighbours on the Map" on page 403.
401

Forsk 2011
Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main
document using the Cells tab of the transmitters Properties dialogue:
1. On the main documents map window, right-click the transmitter whose neighbours you want to change. The context
menu appears.
4. On the Cells tab, there is a column for each cell. Click the Browse button ( ) beside Neighbours in the cell for which
you want to allocate or delete neighbours. The cells Properties dialogue appears.
5. Click the Inter-Technology Neighbours tab.
6. If desired, you can enter the Maximum Number of Neighbours.
To allocate a new neighbour:
1. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon (
).
2. Click elsewhere in the table to complete creating the new neighbour.

3. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the
neighbour and displays it in the Distance column, and sets the Source to "manual."
In GSM, the Inter-technology Neighbours tab is available in each transmitters Properties dialogue.
Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table
To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main
document using the Inter-technology Neighbours table:
4. Select Neighbours > Inter-technology > Open Table from the context menu. The Inter-technology Neighbours table
appears.
5. Enter one inter-technology neighbour per row of the table. Each cell can have more than one inter-technology neighbour.
To allocate an inter-technology neighbour:
), select a reference cell in the Cell column.
2. Select the neighbour in the Neighbour column.

3. Click elsewhere in the table to create the new neighbour and add a new blank row to the table.
4. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the
neighbour and displays it in the Distance column and sets the Source to "manual."
402

AT310_UMU_E0

To make several neighbour relations symmetric:
1. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by
pressing CTRL and clicking each rows separately.
3. Select Make Symmetrical from the context menu.
To take all exceptionnal pairs into consideration:
2. Select Force Exceptional Pairs from the context menu.
You can add or delete either forced neighbours or forbidden neighbours using the Exceptional Pairs of Inter-Technology Neighbours table. You can open this table, select the
exceptional pairs to be considered, right-click the table and select Force Exceptional Pairs
in the context menu.
To delete several symmetric neighbour relations:
1. Click in the left margin of the table rows containing the neighbours to select entire rows. You can select contiguous
3. Select Delete Link and Symmetric Relation from the context menu.
In GSM, neighbours are allocated by transmitter (i.e., by sector).
Allocating and Removing Inter-Technology Neighbours on the Map
You can allocate inter-technology neighbours directly on the map using the mouse. Atoll adds or removes neighbours to transmitters if the display option is set to Neighbours.
Before you can add or remove inter-technology neighbours using the mouse, you must activate the display of inter-technology
neighbours on the map as explained in "Displaying Inter-Technology Neighbours on the Map" on page 400.
To add a symmetric neighbour relation:
2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitter to
the list of inter-technology neighbours of the other transmitter.
To remove a symmetric neighbour relation:
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitter
from the list of inter-technology neighbours of the other transmitter.
403

Forsk 2011
To add an outwards neighbour relation:

2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the list of inter-technology neighbour of the other transmitter.
T remove an outwards neighbour relation:
2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference
transmitter from the list of inter-technology neighbours of the other transmitter.
To add an inwards neighbour relation:
2. There can be two cases:
-
If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter.
Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation.
If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation
by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then press
CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric intertechnology neighbour relation.
To remove an inwards neighbour relation:

2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the transmitter
from the inter-technology neighbours list of the other transmitter.
When there is more than one cell on the transmitter, clicking the transmitter in the map
window opens a context menu allowing you to select the cell you want (see "Selecting One
of Several Transmitters" on page 21).
6.6.3.8 Calculating the Importance of Existing Inter-technology Neighbours

After you have imported inter-technology neighbours into the current Atoll document or manually defined inter-technology
neighbours, Atoll can calculate the importance of each inter-technology neighbour, i.e., the weight of each neighbour.
Atoll calculates the importance for inter-technology neighbours of active and filtered transmitters within the focus zone.
To calculate the importance of existing inter-technology neighbours:
4. Select Neighbours > Inter-technology > Calculate Importance from the context menu. The Neighbour Importance
Evaluation dialogue appears.
5. Select the Inter-technology Neighbours tab.
6. Under Importance, enter the Max inter-site distance. Sites outside the defined maximum inter-site distance will not
be considered as possible neighbours.
7. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on
the same site as their reference cell when calculating importance.
8. Clear the Use Overlapping Coverage check box in order to base the neighbour importance calculation only on the distance criterion and continue with step 10. Otherwise, select the Use Overlapping Coverage check box if you want to
base the neighbour importance calculation on coverage conditions.
9. Under Coverage Conditions, you can set the coverage conditions between inter-technology neighbours and their reference cells for both of the projects.
a. Click the Define button to change the coverage conditions for cells in the main document. The UMTS Coverage
Conditions dialogue appears.
In the UMTS Coverage Conditions dialogue, you can change the following parameters:
-
404
Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell.
Min. Ec/Io: Enter the minimum Ec/Io which must be provided by the reference cell.

AT310_UMU_E0
Ec/Io Margin: Enter the Ec/Io margin relative to the Ec/Io of the best server. The reference cell is either the
best server in terms of pilot quality or a cell of the active set.
Max. Ec/Io: Select the Max. Ec/Io option and enter the maximum Ec/Io which must not be exceeded by the
reference cell.
DL Load Contributing to Io: You can select whether Atoll should use a Global Value (% Pmax) of the downlink
load for all the cells, or the downlink loads Defined per Cell.
b. Click OK to save your modifications and close the Coverage Conditions dialogue.
c. Click the Define button to change the coverage conditions for the transmitters/cells in the linked document.
If the linked document is a GSM document, the GSM Coverage Conditions dialogue appears. In the GSM Coverage
-
Min. BCCH Signal Level: Enter the minimum BCCH signal level which must be provided by the GSM transmitter.
Margin: Enter the margin relative to the BCCH signal level of the best server. The BCCH signal level of the
neighbour transmitter is either the highest one or within a margin of the highest one.
If the linked document is an LTE document, the LTE Coverage Conditions dialogue appears. In the LTE Coverage
-
Margin: Enter the margin relative to the reference signal level of the best server. The reference signal level of
the neighbour transmitter is either the highest one or within a margin of the highest one.
d. Click OK to save your modifications and close the Coverage Conditions dialogue.
10. If you cleared the Use Overlapping Coverage check box, enter the maximum distance between the reference cell and
a possible neighbour in the Max Inter-site Distance box.
Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes
(importance and reason) in a table.
You can use many of Atolls table shortcuts, such as filtering and sorting. For information
on working with data tables, see "Working with Data Tables" on page 47. In addition, by
clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be
calculated.
11. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll
first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices
are not valid, Atoll recalculates them.
Once Atoll has finished calculating importance, the results are displayed in the table.
The table contains the following information.
-

Neighbour: The neighbour of the reference transmitter.
Importance (%): The importance as calculated with the options selected in step 5.
Cause: The reason Atoll has calculated the value in the Importance column.
-
Co-site
Symmetry
Coverage
Distance: If you calculated neighbour importance using inter-site distance, Atoll gives the distance in kilometres
between the reference cell and the neighbour.
405

Forsk 2011
Coverage: If you calculated neighbour importance using coverage overlapping, Atoll gives the amount of reference transmitters coverage area that the neighbour overlaps, in percentage and in square kilometres.
12. Click Commit to commit the importance values and the reasons for allocation to the Neighbours table.
6.6.3.9 Checking the Consistency of the Inter-technology Neighbour Plan

You can perform an audit of the current inter-technology neighbour allocation plan. When you perform an audit of the current
inter-technology neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides
in the audit.
To perform an audit of the inter-technology neighbour plan:
3. Select Neighbours > Inter-technology > Audit from the context menu. The Neighbour Audit dialogue appears.
4. Click the Inter-technology Neighbours tab.
5. Define the parameters of the audit:
-
Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average
number of neighbours per cell.
Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words,
which cells have an empty neighbour list).
Full Lists: Which cells having the maximum number of neighbours allowed (in other words, which cells have a full
neighbour list). The maximum number of neighbours can be either set here for all transmitters, or specified for
each transmitter in the Cells table.
Lists > Max Number: Which cells having more than the maximum number of neighbours allowed. The maximum
number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Cells
table.
Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site neighbours.
Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have non-symmetric neighbour relations.
Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours
or forbidden neighbours.
Distance Between Neighbours: Select the Distance Between Neighbours check box and enter the distance
between neighbours that should not be exceeded.
6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file:
-
Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan
audited.
Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list)
Syntax:
Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed
in their respective neighbours lists.
Syntax:
|CELL|
Lists > Max Number (default max number = Y): x/X; x number of cells out of a total of X having more than Y
number of neighbours listed in their respective neighbours lists.
Syntax:

If the field Maximum number of inter-technology neighbours in the Cells table is empty,
the Full Lists check and the Lists > Max Number check use the Default Max Number value
defined in the audit dialogue.
Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan.
Syntax:
Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan.
Syntax:
406
Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan.
Syntax:
|CELL| |NEIGHBOUR|
|CELL| |NEIGHBOUR|
Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan.

AT310_UMU_E0
Syntax:
-
Distance Between Neighbours > Y: X; total number of neighbours in the audited neighbour plan that are located
at a distance greater than Y.
Syntax:
|CELL| |NEIGHBOUR| |DISTANCE|
6.6.4 Creating a UMTS Sector From a Sector in the Other Network

You can create a new sector in the main document based on an existing sector in the linked document. To create a new sector
in the main document based on an existing sector in the linked document:
2. In the map window, right-click the linked transmitter based on which you want to create a new UMTS transmitter. The
3. Select Copy in [main document] from the context menu.
The following parameters of the new sector in the main document will be the same as the sector in the linked document it
was based on: antenna position relative to the site (Dx and Dy), antenna height, azimuth, and mechanical tilt. The new sector
will be initialised with the radio parameters from the default station template in the main document.
If the sector in the linked document is located at a site that does not exist in the main document, the site is created in the main
document as well.
If the sector in the linked document is located at a site that also exists in the main document, and the coordinates of the site
in the linked and main documents are the same, the sector is created in the main document at the existing site. The site coordinates in the linked and main documents will always be the same if the Atoll administrator has set up site sharing in the database. For more information about site sharing in databases, see the Administrator Manual.
If the sector in the linked document is located at a site that exists in the main document, but at a different location (geographic
coordinates), the sector is not created in the main document.
To update the display settings of the new sector:
3. Right-click the Transmitters folder of the main document. The context menu appears.
4. Select Update Folder Configuration from the context menu.
Figure 6.94: New sector Before and after applying the configuration
The azimuths and mechanical tilts of secondary antennas or remote antennas are not
included when you select Update Folder Configuration and have to be set up manually.
6.6.5 Using ACP in a Co-planning Project

Atoll ACP enables you to automatically calculate the optimal network settings in terms of network coverage and capacity in
co-planning projects where networks using different technologies, for example, UMTS and GSM, must both be taken into
consideration.
When you run an optimisation setup in a co-planning environment, you can display the sites and transmitters of both
networks in the document in which you will run the optimisation process, as explained in "Switching to Co-planning Mode"
on page 390. While this step is not necessary in order to create a co-planning optimisation setup, it will enable you to visually
analyse the changes to both networks in the same document.
Afterwards you can create the new optimisation setup, but when creating an optimisation setup in a co-planning environment, you can not run it immediately; you must first import the other network into the ACP setup.
This section explains how to use ACP to optimise network settings in a co-planning project:
407

Forsk 2011
"Creating a New Co-planning Optimisation Setup" on page 408

"Importing the Other Network into the Setup" on page 408.
6.6.5.1 Creating a New Co-planning Optimisation Setup

Once you have displayed both networks in the main document as explained in "Switching to Co-planning Mode" on page 390,
you can create the new co-planning optimisation setup.
To create a new co-planning optimisation setup:
4. Select New from the context menu. A dialogue appears in which you can set the parameters for the optimisation
process.
For information on the parameters available, see "Defining Optimisation Parameters" on page 339.
5. After defining the optimisation setup, click the Create Setup button to save the defined optimisation.
The optimisation setup has now been created. The next step is to add the GSM network to the ACP optimisation setup you
have just created.
6.6.5.2 Importing the Other Network into the Setup

Once you have created the co-planning optimisation setup, you must import the linked network.
To import the linked network:
) to expand the ACP - Automatic Cell Planning folder.
4. Right-click the setup you created in "Creating a New Co-planning Optimisation Setup" on page 408. The context menu
appears.
5. Select Import Project from the context menu and select the name of the linked document you want to import into the
newly created setup.
The setup has been modified to include the linked network.

You can modify the parameters for the optimisation setup by right-clicking it on the Network tab of the Explorer window and
selecting Properties from the context menu. For information on the parameters available, see "Defining Optimisation Parameters" on page 339.
After defining the co-planning optimisation setup:
Right-click the setup in the ACP - Automatic Cell Planning folder and select Run from the context menu to run the
optimisation. For information on running the optimisation, see "Running an Optimisation Setup" on page 362. For
information on the optimisation results, see "Viewing Optimisation Results" on page 365.
6.6.6 Ending Co-planning Mode

once you have linked two Atoll documents for the purposes of co-planning, Atoll will maintain the link between them.
However, you might want to unlink the two documents at some point, either because you want to use a different document
in co-planning or because you want to restore the documents to separate, technology-specific documents.
408

AT310_UMU_E0
To unlink the documents and end co-planning mode:

1. Select File > Open to open the main document.
Atoll informs you that this document is part of a multi-technology environment and asks whether you want to open
the other document.
2. Click Yes to open the linked document as well.
3. Select Document > Unlink to unlink the documents and end co-planning mode.
The documents are no longer linked and co-planning mode is ended.
6.7 Advanced Configuration

In this section, the following advanced configuration options are explained:
"Modelling Inter-Carrier Interference" on page 409

"Defining Frequency Bands" on page 409
"The Global Network Settings" on page 410
"Radio Bearers" on page 411
"Site Equipment" on page 413
"Receiver Equipment" on page 415
"Multiple Input Multiple Output Systems" on page 417
"Conditions for Entering the Active Set" on page 418
"Modelling Shadowing" on page 419
"Modelling Inter-Technology Interference" on page 420.
6.7.1 Modelling Inter-Carrier Interference

If you want Atoll to take into account the interference between two carriers, you must create a carrier pair with an interference reduction factor. Atoll will take the interference reduction factor into account on both the uplink and the downlink.
To create a pair of carriers with an interference reduction factor:
) to expand the Frequencies folder.
4. Right-click the Intra-technology Interference Reduction Factors folder. The context menu appears.
5. Select Open Table from the context menu. The Inter-Carrier Interference Reduction Factor table appears.
6. For each carrier pair for which you want define inter-carrier interference:
a. Enter the first carrier of the pair in the 1st Carrier column.
b. Enter the second carrier of the pair in the 2nd Carrier column.
c. Enter an interference reduction factor in the Reduction Factor (dB) column. When Atoll is calculating interference, it subtracts the interference reduction factor from the calculated interference. If the interference reduction
factor is set to "0," Atoll assumes that the carriers in the defined pair generate as much interference as cells with
the same carrier interference.
The interference reduction factor must be a positive value.
For every pair of carriers that is not defined, Atoll assumes that there is no inter-carrier interference.
d. Press ENTER to create the carrier pair and to create a new row in the table.
6.7.2 Defining Frequency Bands

To define frequency bands:
) to expand the Frequencies folder.
4. In the Frequencies folder, right-click Bands. The context menu appears.
409

Forsk 2011
5. Select Open Table from the context menu. The Frequency Bands table appears.
6. In the Frequency Bands table, enter one frequency band per row. For information on working with data tables, see
"Working with Data Tables" on page 47. For each frequency band, enter:
-
Name: Enter a name for the frequency, for example, "Band 2100." This name will appear in other dialogues when
you select a frequency band.
Average Frequency (MHz): Enter the average frequency.
First Carrier: Enter the number of the first carrier in this frequency band.
Last Carrier: Enter the number of the last carrier in this frequency band. If this frequency band has only one carrier,
enter the same number as entered in the First Carrier field.
When you have more than one frequency band, the carriers must be numbered
sequentially, contiguously (i.e., you cannot skip numbers in a range of carriers, and the
range of carriers in one band cannot overlap the range of carriers in another), and
uniquely (i.e., you can only use each number once).
For example: Band 2100: First carrier: 0; Last carrier 1 and Band 900: First carrier: 2 and
Last carrier: 2
7. When you have finished adding frequency bands, click the Close button (
).
6.7.3 The Global Network Settings

In the Network Settings Properties dialogue, you can define many calculation parameters that are used in predictions and in
Monte Carlo simulations.
This section explains the options available in the Network Settings Properties dialogue, and explains how to access the
dialogue:
"The Options of the Network Settings Properties Dialogue" on page 410

"Modifying Global Network Settings" on page 411.
6.7.3.1 The Options of the Network Settings Properties Dialogue

The Network Settings Properties dialogue has two tabs: the Global Parameters Tab and the Calculation Parameters tab.
6.7.3.1.1
"The Global Parameters Tab" on page 410

"The Calculation Parameters Tab" on page 411
The Global Parameters Tab

The Global Parameters tab has the following options:
DL Powers: Under DL Powers, you can define whether the power values on the downlink are Absolute or offset from
the pilot (Pilot Offset). The power values affected are the synchronisation channel, other common channel, HS-SCCH,
and HSUPA powers defined in the cell properties, as well as the minimum and maximum traffic channel powers per
R99 radio bearer. Atollautomatically converts the power values defined in the cell properties (i.e., synchronisation
channel, other common channel, HS-SCCH, and HSUPA powers) when you change the option. On the other hand, the
values for the minimum and maximum traffic channel powers have to be modified manually.
DL Load: Under DL Load, you can define whether the total power values on the downlink are Absolute or a percentage
of the maximum power (% Pmax). Atollautomatically converts the total power values when you change the option.
Interferences: Under Interferences, you can define the method used to calculate interference on the downlink (I0 and
Nt):
- I0: You can select "Total noise" and Atoll will calculate I0 using the noise generated by all transmitters plus thermal
noise or you can select "Without pilot" and Atoll will calculate I0 using the total noise less the pilot signal and
orthogonal part of traffic channels and other common channels.
- Nt: You can select "Total noise" and Atoll will calculate Nt as the noise generated by all transmitters plus thermal
noise or you can select "Without useful signal" and Atoll will calculate Nt as the total noise less the signal of the
studied cell.
Handoff: Under Handoff, you can define the parameters used to model soft handoff on the uplink.
-
410
Default UL Macro-Diversity Gain: You can set a default value for the uplink gain due to macro-diversity on soft
and soft-soft handovers. If you clear the Shadowing taken into account check box on the Conditions tab when
defining a coverage prediction or during a point analysis, Atoll uses this value. If you select the Shadowing taken
into account check box on the Conditions tab, Atoll calculates the UL macro-diversity gain, based on the standard
devia on value of Eb Nt on the uplink defined per clu er class.
+MRC (maximal ratio combining) in Softer/Soft: If you select the +MRC in Softer/Soft check box, Atoll selects the
serving cell during a softer/soft handover by recombining the signal of co-site transmitters and multiplying the

AT310_UMU_E0
resulting signal by the rake efficiency factor and then comparing this value to the signal received at transmitters
located on the other sites of the active set. Atoll chooses the greatest value and multiplies it by the macro-diversity gain.
Compressed Mode: Under Compressed Mode, you can define the parameters related to compressed mode. Compressed mode is used when a mobile supporting compressed mode is connected to a cell located on a site with a compressed-mode-capable equipment and either the pilot RSCP, or the received Ec I0, or both of them are lower than the
defined activation thresholds.
-
Pilot RSCP Activation Threshold: You can select the RSCP Active check box and enter a Pilot RSCP Activation
Threshold.
EcI0 Ac va on Threshold: You can select the EcI0 Ac ve check box and enter a EcI0 Ac va on Threshold.
You must select either the RSCP Active check box or the EcI0 Ac ve check box or both.
HSDPA: Under HSDPA, you can define how total noise is calculated and how the CQI (Channel Quality Indicator) is
evaluated for HSDPA.
-
6.7.3.1.2
EbNt UL and DL Target Increase: When compressed mode is ac vated, Eb Nt requirements in UL and DL are
increased. In order to take this into account, Atoll adds UL and DL Eb Nt target increase values to the UL and DL
Eb Nt requirements set for each radio bearer.
Nt: You can select "Total noise" and Atoll will calculate Nt as the noise generated by all transmitters plus thermal
noise or you can select "Without useful signal" and Atoll will calculate Nt as the total noise less the signal of the
studied cell.
CQI: You can select Based on CPICH quality and Atoll will measure the CQI based on the pilot Ec Nt or you can
select Based on HS-PDSCH quality and Atoll will measure the CQI based on the HS-PDSCH Ec Nt. Depending on
the option selected, you will have to define either a CQI=f(CPICH Ec/Nt) graph, or a CQI=f(HS-PDSCH Ec/Nt) graph
in the Properties dialogue of the terminal equipment. The calculated CQI will be used to determine the best
bearer.
The Calculation Parameters Tab

The Calculation Parameters tab has the following options:
Calculation limitation: Under Calculation limitation, you can define the following data:
-
Min. interferer reception threshold: This value is used by Atoll to limit the influence of interferers in calculations.
The performance of UMTS-specific coverage predictions and Monte Carlo simulations can be improved by setting
a high minimum interferer reception threshold. This value is used as a filter criterion on the signal level received
from interferers. Atoll will discard all interferers with a signal level lower than this value.
- Min. pilot RSCP threshold: The minimum pilot RSCP threshold. The value is used as a filter criterion on the
received pilot signal level when calculating UMTS-specific predictions. Atoll does not display any result on the pixel
if the pilot signal level received from the best server is lower than the defined min. pilot RSCP threshold.
Receiver: Under Receiver, you can enter the Height of the receiver.
6.7.3.2 Modifying Global Network Settings

You can change global network settings in the Network Settings Properties dialogue.
To change global network settings:
2. Right-click the Network Settings folder. The context menu appears.
3. Select Properties from the context menu. The Network Settings Properties dialogue appears.
4. Modify the parameters described in "The Options of the Network Settings Properties Dialogue" on page 410.
5. Click OK.
6.7.4 Radio Bearers

Bearer services are used by the network for carrying information. In this section, the following are explained:
"Defining R99 Radio Bearers" on page 412

"Defining HSDPA Radio Bearers" on page 412
"Defining HSUPA Radio Bearers" on page 413.
411

Forsk 2011
6.7.4.1 Defining R99 Radio Bearers

Bearer services are used by the network for carrying information. The R99 Radio Bearer table lists all the available radio bearers. You can create new R99 radio bearers and modify existing ones by using the R99 Radio Bearer table.
Only the following R99 radio bearer parameters are used in predictions:
Max TCH Power (dBm)

The type of bearer.
To create or modify an R99 radio bearer:

) to expand the Radio Bearers folder.
4. Right-click the R99 Radio Bearers folder. The context menu appears.
5. Select Open Table from the context menu. The R99 Radio Bearers table appears.
6. In the R99 Radio Bearers table, you can enter or modify the following fields:
-
Name: You can modify the name of the bearer. If you are creating a new R99 radio bearer, enter a name in the
row marked with the New Row icon (
).
Nominal Uplink Rate (Kbps): Enter or modify the nominal uplink rate in kilobytes per second.
Nominal Downlink Rate (Kbps): Enter or modify the nominal downlink rate in kilobytes per second.
Type: Select or modify the service type. There are four classes: Conversational, Streaming, Interactive, and Background. This field corresponds to the QoS (quality of service) class or traffic class that the bearer will belong to.
UL DPCCH/DPCH Power Ratio: Enter or modify the uplink DPCCH (Dedicated Physical Control Channel)/DPCH
(Dedicated Physical Channel) power ratio. The DPCH power is the combination of the DPCCH and the DPDCH (Dedicated Physical Data Channel) power.
DL DPCCH/DPCH Power Ratio: Enter or modify the downlink DPCCH (Dedicated Physical Control Channel)/DPCH
(Dedicated Physical Channel) power ratio.
Min. TCH Power (dBm): Enter or modify the minimum traffic channel power. The minimum and maximum traffic
channel power make up the dynamic range for downlink power control.
Max TCH Power (dBm): Enter or modify the maximum traffic channel power.
The maximum and minimum traffic channel powers can be either absolute values or values
relative to the pilot power; this depends on the option defined on the Global Parameters
tab of the UMTS Network Settings Properties dialogue. These values have to be manually
modified when the option is changed.
DL Spreading Factor (Active Users): Enter or modify the downlink spreading factor for active users. This parameter
is used to estimate the number of OVSF codes required by an active user using the R99 radio bearer.
DL Spreading Factor (Inactive Users): Enter or modify the downlink spreading factor for inactive users. This
parameter is used to estimate the number of OVSF codes required by an inactive user with the R99 radio bearer.
6.7.4.2 Defining HSDPA Radio Bearers

In each cell, the scheduler selects the HSDPA resource per UE and per TTI. This HSDPA resource is called a TFRC (Transport
Format Resource Combination) and is the set of parameters such as the transport format, the modulation scheme, and the
number of used HS-PDSCH channels. In Atoll, the TFRC are referred to as HSDPA radio bearers.
During a simulation, and for the HSDPA coverage prediction, Atoll selects a suitable HSDPA radio bearer and uses its RLC peak
rate. The HSDPA radio bearer selection is based on UE capabilities (maximum number of HS-PDSCH channels, transport block
size, modulation supported), cell capabilities (HSPA or HSPA+, MIMO system used, maximum number of HS-PDSCH channels),
and reported CQI.
The HSDPA Radio Bearers table lists the available HSDPA radio bearers. They can be classified into two categories:
HSDPA bearers using QPSK and 16QAM modulations. They can be selected for users connected to HSPA and HSPA+
capable cells.
HSDPA bearers using 64QAM modulation (following improvements introduced by release 7 of the 3GPP UTRA specifications, referred to as HSPA+). These HSDPA bearers can be allocated to users connected to cells with HSPA+ capabilities only.
You can create new HSDPA radio bearers and modify existing ones by using the HSDPA Radio Bearers table.
To open the HSDPA Radio Bearers table:
412

AT310_UMU_E0
4. Right-click the HSDPA Radio Bearers folder. The context menu appears.
5. Select Open Table from the context menu. The HSDPA Radio Bearers table appears with the following information:
-
Radio Bearer Index: The bearer index number.

Transport Block Size (Bits): The transport block size in bits.
Number of Used HS-PDSCH Channels: The number of HS-PDSCH channels used.
RLC Peak Rate (bps): The RLC peak rate represents the peak rate without coding (redundancy, overhead,
addressing, etc.).
Modulation: The modulation used. You can choose between QPSK, 16QAM or 64QAM.
6.7.4.3 Defining HSUPA Radio Bearers

In each cell, the scheduler selects the HSUPA resource per UE, per Node B, and per user service. This HSUPA resource is called
a TFC (Transport Format Combination) and requires a defined ratio of E-DPDCH power over DPCCH power. This ratio is
modelled as the required E-DPDCH Ec Nt. The combina on of the TFC and the power oset is modelled in Atoll as HSUPA radio
bearers.
During a simulation, and for the HSUPA coverage prediction, Atoll selects a suitable HSUPA radio bearer. The HSUPA radio
bearer selection is based on UE capabilities (maximum number of E-DPDCH codes, smallest spreading factor, TTI length, and
modula on supported), cell capabili es (HSPA or HSPA+), and the required E-DPDCH Ec Nt.
The HSUPA Radio Bearers table lists the available HSUPA radio bearers. They can be classified into two categories:
HSUPA bearers using QPSK modulation. They can be selected for users connected to HSPA and HSPA+ capable cells.
HSUPA bearers using 16QAM modulation (following improvements introduced by release 7 of the 3GPP UTRA specifications, referred to as HSPA+). These HSUPA bearers can be allocated to users connected to cells with HSPA+ capabilities only.
To open the HSUPA Radio Bearers table:

4. Right-click the HSUPA Radio Bearers folder. The context menu appears.
5. Select Open Table from the context menu. The HSUPA Radio Bearers table appears with the following information:
-
Radio Bearer Index: The bearer index number.

TTI Duration (ms): The TTI duration in ms. The TTI can be 2 or 10 ms.
Transport Block Size (Bits): The transport block size in bits.
Number of E-DPDCH Codes: The number of E-DPDCH channels used.
Min. Spreading Factor: The minimum spreading factor used.
RLC Peak Rate (bps): The RLC peak rate represents the peak rate without coding (redundancy, overhead,
addressing, etc.).
Modulation: The modulation used. You can choose between QPSK or 16QAM.
6.7.5 Site Equipment

"Creating Site Equipment" on page 413

"Defining Resource Consumption per UMTS Site Equipment and R99 Radio Bearer" on page 414
"Defining Resource Consumption per UMTS Site Equipment and HSUPA Radio Bearer" on page 415.
6.7.5.1 Creating Site Equipment

To create a new piece of UMTS site equipment:
) to expand the Radio Resource Management folder.
4. Right-click Site Equipment. The context menu appears.

5. Select Open Table from the context menu. The Site Equipment table appears.
6. In the Equipment table, each row describes a piece of equipment. For information on working with data tables, see
"Working with Data Tables" on page 47. For the new piece of UMTS equipment you are creating, enter the following:
-
Name: The name you enter will be the one used to identify this piece of equipment.
413

Forsk 2011
Manufacturer: The name of the manufacturer of this piece of equipment.

MUD factor: Multi-User Detection (MUD) is a technology used to decrease intra-cell interference in the uplink.
MUD is modelled by a coefficient from 0 to 1; this factor is considered in the UL interference calculation. In case
MUD is not supported by equipment, enter 0 as value.
Rake factor: The rake receiver efficiency factor enables Atoll to model the rake receiver on UL. Atoll uses this
factor to calculate the uplink SHO gain and uplink signal quality in simulations, point-to-point handover analysis
and coverage predictions. This parameter is considered in the uplink for softer and softer-softer handovers; it is
applied to the sum of signals received on the same site. The factor value can be from 0 to 1. It models losses due
to the imperfection of signal recombination.
The rake receiver efficiency factor used to model the recombination in downlink can be set
in terminal properties.
Carrier selection: Carrier selection refers to the carrier selection method used during the transmitter admission
control in the mobile active set. The selected strategy is used in simulations when no carrier is specified in the
properties of the service (all the carriers can be used for the service) or when the carrier specified for the service
is not used by the transmitter. On the other hand, the specified carrier selection mode is always taken into account
in predictions (AS analysis and coverage predictions). Choose one of the following:
-
Min. UL Load Factor: The carrier with the minimum UL noise (carrier with the lowest UL load factor) is selected.
Min. DL Total Power: The carrier with the minimum DL total power is selected.
Random: The carrier is randomly chosen.
Sequential: Carriers are sequentially loaded. The first carrier is selected as long as it is not overloaded. Then,
when the maximum uplink load factor is reached, the second carrier is chosen and so on.
Downlink and Uplink Overhead Resources for Common Channels/Cell: The uplink and downlink overhead
resources for common channels/cell correspond to the numbers of channel elements that a cell uses for common
channels in the uplink and downlink. This setting is also used for OVSF code allocation; it indicates the number of
OVSF codes to be allocated to control channels per cell.
AS restricted to neighbours: Select this option if you want the other transmitters in the active set to belong to the
neighbour list of the best server.
Compressed Mode: If you select this option, cells located on sites with this equipment are able to manage compressed mode when radio conditions require it. Compressed mode is generally used to prepare the hard handover
of users with single receiver terminals.
By setting an option in the atoll.ini file, you can prevent Atoll from allocating inter-carrier
and inter-technology neighbours to cells located on sites whose equipment does not
support the compressed mode. For more information, see the Administrator Manual.
Overhead Iub Throughput/Cell (kbps): The overhead Iub throughput per cell corresponds to the Iub throughput
required by the cell for common channels in the downlink.
HSDPA Iub Backhaul Overhead (%): The HSDPA Iub backhaul overhead corresponds to the percentage of the
HSDPA bearer RLC peak rate to be added to the RLC peak rate. The total value corresponds to the Iub backhaul
throughput required by the HSDPA user for HS Channels in the downlink.
Throughput Supported per E1/T1/Ethernet Link (kbps): The throughput supported per E1/T1/Ethernet link corresponds to the throughput carried by an E1/T1/Ethernet link. This parameter is used to calculate the required Iub
capacity, i.e. the number of E1/T1/Ethernet links required to provide the total throughput.
7. Click the Close button (
) to close the table.
6.7.5.2 Defining Resource Consumption per UMTS Site Equipment and R99 Radio
Bearer
The number of channel elements and the Iub backhaul throughput consumed by an R99 bearer user depend on the site equipment, on the R99 radio bearer, and on the link direction (up or down). The number of channel elements and the Iub backhaul
throughput consumed can be defined for UMTS simulations.
To define channel element and Iub backhaul throughput consumption during UMTS simulations:
4. Right-click R99 Resource Consumption. The context menu appears.
414

AT310_UMU_E0
5. Select Open Table from the context menu. The R99 Resource Consumption table appears.
6. For each equipment-R99 radio bearer pair, enter in the R99 Resource Consumption table the number of UL and DL
channel elements and the UL and DL Iub backhaul throughputs that Atoll will consume during the power control simulation.
6.7.5.3 Defining Resource Consumption per UMTS Site Equipment and HSUPA Radio Bearer
The number of channel elements and the Iub backhaul throughput consumed by a HSUPA bearer user in the uplink depend
on the site equipment and on the HSUPA radio bearer. The number of channel elements and the Iub backhaul throughput
consumed can be defined for UMTS simulations.
To define channel element and Iub backhaul throughput consumption during UMTS simulations:
4. Right-click HSUPA Resource Consumption. The context menu appears.

5. Select Open Table from the context menu. The HSUPA Resource Consumption table appears.
6. For each equipment-HSUPA radio bearer pair, enter in the HSUPA Resource Consumption table the number of UL
channel elements and the UL Iub backhaul throughput that Atoll will consume during the power control simulation.
6.7.6 Receiver Equipment

"Creating or Modifying Reception Equipment" on page 415

"HSDPA UE Categories" on page 417
"HSUPA UE Categories" on page 417.
6.7.6.1 Creating or Modifying Reception Equipment

In Atoll, reception equipment models the reception characteristics of user terminals and is used when you create a terminal.
The graphs defined for each reception equipment entry are used for quality predictions and for selecting HSDPA and HSUPA
bearers.
To create or modify reception equipment:
) to expand the Reception Equipment folder.
"Standard" is the default reception equipment type for all terminals.

4. Double-click the reception equipment type you want to modify. The reception equipment types Properties dialogue
appears.
You can create a new reception equipment type by right-clicking the Reception Equipment
folder and selecting New from the context menu.
5. Click the R99 Bearer Selection tab. On the R99 Bearer Selection tab, you can define downlink and uplink Eb Nt
requirements. These are the thresholds (in dB) that must be reached to provide users with the service. These parameters depend on the mobility type.
Using transmit (Tx) and receive (Rx) diversity results in a quality gain on received downlink and uplink Eb Nt. You can
specify gains on received downlink and uplink Eb Nt for each diversity configura on. Atoll will consider them when Tx
or Rx diversity configurations are assigned to transmitters.
-
R99 Bearer: Select an R99 bearer from the list.

Mobility: Select a mobility type from the list.
UL Target (dB): Enter or modify the uplink (Eb Nt) threshold.
Uplink 2RX Diversity Gain (dB): Enter or modify the two-receiver uplink diversity gain in dB.
Uplink 4RX Diversity Gain (dB): Enter or modify the four-receiver uplink diversity gain in dB.
DL Target (dB): Enter or modify the downlink (Eb Nt) threshold.
Downlink Open Loop Diversity Gain (dB): Enter or modify the downlink open loop diversity gain in dB.
415

Forsk 2011
Downlink Closed Loop Diversity Gain (dB): Enter or modify the downlink closed loop diversity gain in dB.
6. Click the Quality Graphs tab.

7. Ensure that a Quality Indicator has been chosen for each R99 Bearer. You can edit the values in the DL and UL Quality
Indicator Tables by clicking directly on the table entry, or by selecting the Quality Indicator and clicking the Downlink
Quality Graphs or the Uplink Quality Graphs buttons.
The DL and UL Quality Indicator tables describe the variation of the quality indicator as a function of the measured
parameter (as defined in the Quality Indicators table). The Uplink and Downlink Quality Graphs are used for quality
predictions.
8. Click the HSDPA Bearer Selection tab.
9. Ensure that the values for each Mobility in the CQI Table and the Best HSDPA Bearer Table have been entered. You
can edit the values in the CQI Table and the Best HSDPA Bearer Table by clicking directly on the table entry, or by
selecting the Mobility and clicking the CQI Graph or the Best Bearer Graph buttons.
The CQI table describes the variation of the CPICH CQI as a function of the CPICH Ec/Nt (or the variation of HS-PDSCH
CQI as a function of the HS-PDSCH Ec/Nt); the values displayed depend on the calculation parameter you have selected
in the Global Parameters tab of the UMTS Network Settings Properties dialogue (for more information, see "The
Options of the Network Settings Properties Dialogue" on page 410).
The HS-PDSCH CQI table describes the index of the best HSDPA bearer as a function of the HS-PDSCH CQI.
The CQI graphs and best bearer graphs are used in the simulation and in the HSDPA prediction to model fast link adaptation (selection of the HSDPA bearer).
The supplier RRM (radio resource management) strategy can be taken into account using the HS-PDSCH CQI table, for
example:
-
You can define several pieces of reception equipment with a separate table for each. You can reserve low bearer
indexes for poor-performance reception equipment and higher bearer indexes for high-performance equipment.
You can specify a graph for each mobility. Here, you can reserve low bearer indexes for high speeds and higher
bearer indexes for low speeds.
You can also give priority to either one user by assigning him a high bearer index or to all users by assigning them
low bearer indexes.
10. Click the HSDPA Quality Graphs tab.

11. Ensure that a Quality Indicator has been chosen for each Radio Bearer Index. You can edit the values in the DL Quality
Indicator Table by clicking directly on the table entry, or by selecting the Quality Indicator and clicking the Downlink
Quality Graph button.
The HSDPA BLER table describes the varia on of the BLER as a func on of the HS-PDSCH Ec Nt. It is used to calculate
the application throughput for the HSDPA coverage prediction.
12. Click the HSUPA Bearer Selection tab.
13. Ensure that, for each Radio Bearer Index and Mobility pair, you have entered a value for the Number of Retransmissions and for the Requested EcNt Threshold. You can edit the values in the Early Termination Probabilities table by
clicking directly on the table entry, or by selecting the Radio Bearer Index and clicking the Early Termination Probability Graph button.
The Number of Retransmissions and the Requested EcNt Threshold values are used in the simulation and in the
HSUPA prediction to model noise rise scheduling and in the selection of the HSUPA radio bearer.
The Early Termination Probabilities table describes the variation of the early termination probability as a function of
the number of retransmissions. It is used in the HSUPA prediction to calculate the average RLC throughput and the
average application throughput when HARQ (Hybrid Automatic Repeat Request) is used.
14. Click the HSUPA Quality Graphs tab.
15. Ensure that a Quality Indicator has been chosen for each Radio Bearer Index and that there is a value defined for the
Number of Retransmissions. You can edit the values in the UL Quality Indicator Table by clicking directly on the table
entry, or by selecting the Quality Indicator and clicking the Uplink Quality Graph button.
The HSUPA BLER table describes the varia on of the BLER as a func on of the E-DPDCH Ec Nt. It is used to calculate
the application throughput for the HSUPA coverage prediction.
16. Click the MIMO tab.
17. Ensure that, for each HSDPA Radio Bearer Index and Mobility pair, you have entered a value for the Number of Transmission Antennas Ports, for the Number of Reception Antennas Ports and for the Transmit Diversity Gain. You can
edit the values in the Max Spatial Multiplexing Gains table by clicking directly on the table entry, or by selecting the
Mobility and clicking the Max Spatial Multiplexing Gain Graph button.
416

AT310_UMU_E0
The Max Spatial Multiplexing Gains table describes the variation of the maximum spatial multiplexing gain as a function of the HS-PDSCH Ec/Nt (dB).
For more information on the different MIMO systems, see "Multiple Input Multiple Output Systems" on page 417.
RX
No MIMO gain (diversity, spatial multiplexing) is applied if N TX
Ant = N Ant = 1 .
18. Click OK to close the reception equipment types Properties dialogue.
6.7.6.2 HSDPA UE Categories

HSDPA user equipment capabilities are standardised into 22 different categories according to 3GPP specifications.
To edit a UE category:
) to expand the UE Categories folder.
4. Right-click HSDPA UE Categories. The context menu appears.

5. Select Open Table from the context menu. The HSDPA User Equipment Categories table appears.
6. The HSDPA User Equipment Categories table has the following columns:
-
Index: Each HSDPA UE category is a separate record in the table and has a unique index.
Category Name: Name of the HSDPA UE category.
Max. Number of HS-PDSCH Channels: The maximum number of HS-PDSCH channels allowed for the category.
Min. Number of TTI Between Two Used TTI: The minimum number of TTI (Transmission Time Interval) between
two TTI used.
Max. Transport Block Size (bits): The maximum transport block size allowed for the category.
Highest Modulation: Select the highest modulation supported by the category. You can choose between QPSK,
16QAM (if you select 16QAM, 16QAM and QPSK modulations can be used) or 64QAM (if you select 64QAM,
64QAM, 16QAM and QPSK modulations can be used).
MIMO Support: Select whether the category supports MIMO systems or not.
Multi-cell Mode: Select whether the category supports dual-cell HSDPA or not.
6.7.6.3 HSUPA UE Categories

HSUPA user equipment capabilities are standardised into 7 different categories according to 3GPP specifications.
To edit a UE category:
) to expand the UE Categories folder.
4. Right-click HSUPA UE Categories. The context menu appears.

5. Select Open Table from the context menu. The HSUPA User Equipment Categories table appears.
6. The HSUPA User Equipment Categories table has the following columns:
-
Index: Each HSUPA UE category is a separate record in the table and has a unique index.
Category Name: Name of the HSUPA UE category.
Max Number of E-DPDCH Codes: The maximum number of E-DPDCH codes allowed for the category.
TTI 2 ms: Select the check box if a TTI of 2 ms is supported. If a 2 ms TTI is not selected, a 10 ms TTI is used.
Min Spreading Factor: Enter the minimum spreading factor supported.
Max Block Size for a 2 ms TTI (bits): The maximum transport block size allowed for a 2 ms TTI.
Max Block Size for a 10 ms TTI (bits): The maximum transport block size allowed for a 10 ms TTI.
Highest Modulation: Select the highest modulation supported by the category. You can choose between QPSK
or16QAM. If 16QAM modulation is selected, 16QAM and QPSK modulations can be used.
6.7.7 Multiple Input Multiple Output Systems

Multiple Input Multiple Output (MIMO) systems which are supported by some HSDPA bearers (following improvements introduced by release 7 of the 3GPP UTRA specifications, referred to as HSPA+) use different transmission and reception diversity
techniques. MIMO diversity systems can be roughly divided into the types described in the following sections, all of which are
modelled in Atoll.
417

Forsk 2011
Transmit and Receive Diversity

Transmit or receive diversity uses more than one transmission or reception antenna to send or receive more than one copy
of the same signal. The signals are constructively combined (using optimum selection or maximum ratio combining) at the
receiver to extract the useful signal. As the receiver gets more than one copy of the useful signal, the signal level at the receiver
after combination of all the copies is more resistant to interference than a single signal would be. Therefore, diversity
improves the quality at the receiver. It is often used for the regions of a cell that have bad quality conditions.
In Atoll, you can define whether a cell supports transmit diversity by selecting HSPA+ (Transmit Diversity) in cell properties
(see "Cell Definition" on page 205). Diversity gains on downlink can be defined in the reception equipment for different
numbers of transmission and reception antenna ports, mobility types and HSDPA bearers. For more information on downlink
diversity gains, see "Creating or Modifying Reception Equipment" on page 415. Additional gain values can be defined per clutter class. For information on setting the additional downlink diversity gain for each clutter class or for all clutter classes, see
"Defining Clutter Class Properties" on page 119.
During calculations in Atoll, a user (mobile, pixel, or point receiver) using a MIMO-capable terminal, and connected to a cell
that supports HSPA+ with transmit diversity, will benefit from the downlink diversity HS-PDSCH Ec/Nt gain.
Spatial Multiplexing
Spatial multiplexing uses more than one transmission antenna to send different signals (data streams) on each antenna. The
receiver can also have more than one antenna for receiving different signals. When spatial multiplexing is used with M transmission and N reception antenna ports, the throughput over the transmitter-receiver link can be theoretically increased M or
N times, depending on which is smaller, M or N. Spatial multiplexing improves the throughput (i.e., the channel capacity) for
a given HS-PDSCH Ec/Nt, and is used for the regions of a cell that have sucient HS-PDSCH Ec Nt condi ons.
In Atoll, you can define whether a cell supports spatial multiplexing by selecting HSPA+ (Spatial Multiplexing) in the cell properties (see "Cell Definition" on page 205). Spatial multiplexing capacity gains can be defined in the reception equipment for
different numbers of transmission and reception antenna ports, mobility types, and HSDPA bearers. For more information on
spatial multiplexing gains, see "Creating or Modifying Reception Equipment" on page 415.
During calculations in Atoll, a user (mobile, pixel, or point receiver) using a MIMO-capable terminal, and connected to a cell
that supports HSPA+ with spatial multiplexing, will benefit from the spatial multiplexing gain in its throughput depending on
its HS-PDSCH Ec Nt.
Because spa al mul plexing improves the channel capacity or throughputs, the HS-PDSCH Ec Nt of a user is determined first.
Once the HS-PDSCH Ec Nt is known, Atoll determines the corresponding CQI and calculates the user throughput based on the
bearer available at the user location. The obtained user throughput is then increased according to the spatial multiplexing
capacity gain and the Spatial Multiplexing Gain Factor of the users clutter class. The capacity gains defined in Max Spatial
Multiplexing Gain graphs are the maximum theoretical capacity gains using spatial multiplexing. Spatial multiplexing requires
a rich multipath environment, without which the gain is reduced. In the worst case, there is no gain. Therefore, you can define
a Spatial Multiplexing Gain Factor per clutter class whose value can vary from 0 to 1 (0 = no gain, 1 = 100% gain). For information on setting the Spatial multiplexing Gain Factor for each clutter class or for all clutter classes, see "Defining Clutter
Class Properties" on page 119.
The spatial multiplexing capacity gain vs. HS-PDSCH Ec/Nt graphs available in Atoll by default have been generated based on
the maximum theoretical spatial multiplexing capacity gains obtained using the following equations:
CC MIMO
G MIMO = ---------------------CC SISO
Where CC MIMO =
TX
Min ( N Ant,
RX
N Ant )
Ec
-------
Nt HS PDSCH
Log 2 1 + ----------------------------------------- is the channel capacity at a given HS-PDSCH Ec/Nt for a

TX
RX
Min ( N Ant, N Ant )
TX
RX
is the chanMIMO system using N Ant transmission and N Ant reception antenna ports. CCSISO = Log 2 1 + -------
Nt HS PDSCH
Ec
nel capacity for a single antenna system at a given HS-PDSCH Ec Nt. HS-PDSCH Ec Nt is used as a ra o (and not dB) in these
formulas. You can replace the default spatial multiplexing capacity gain graphs with graphs extracted from simulated or measured values.
6.7.8 Conditions for Entering the Active Set

The mobile active set is the list of the transmitters to which the mobile is connected. The active set may consist of one or more
transmitters; depending on whether the service supports soft handover and on the terminal active set size. Transmitters in
the mobile active set must use a frequency band with which the terminal is compatible.
It is, however, the quality of the pilot (Ec I0) that finally determines whether or not a transmi er can belong to the ac ve set.
In order for a given transmitter to enter the mobile active set as best server, the pilot quality from this transmitter must
exceed an upper threshold defined in the properties of the mobility type. In addition, the pilot quality must be the highest one.
418

AT310_UMU_E0
In order for a transmitter to enter the active set:
It must use the same carrier as the best server transmitter. In Atoll, carriers are modelled using cells. For information
on accessing cell properties, see "Creating or Modifying a Cell" on page 210. For a description of the properties of a
cell, see "Cell Definition" on page 205.
The pilot quality difference between the cell and the best server must not exceed the AS-threshold set per cell. For
information on accessing the AS threshold defined for a given cell, see "Creating or Modifying a Cell" on page 210.
If you have selected to restrict the active set to neighbours, the transmitter must be a neighbour of the best server.
You can restrict the active set to neighbours by selecting the AS Restricted to Neighbours option in the Site Equipment table. For an explanation of how to set the AS Restricted to Neighbours option, see "Creating Site Equipment"
on page 413.
The active set for HSDPA users is different in the following way: HSDPA physical channels do not support soft handover, therefore the user is never connected to more than one transmitter at a time.
6.7.9 Modelling Shadowing

Shadowing, or slow fading, is signal loss along a path that is caused by obstructions not taken into consideration by the propagation model. Even when a receiver remains in the same location or in the same clutter class, there are variations in reception due to the surrounding environment.
thereby create coverage predictions that are reliable more than fifty percent of the time. The additional losses or gains caused
by shadowing are known as the shadowing margin. The shadowing margin is added to the path losses calculated by the propagation model.
In UMTS projects, the standard deviation of the propagation model is used to calculate shadowing margins on signal levels.
You can also calculate shadowing margins on Ec I0 and Eb Nt values and the macro-diversity gain. For informa on on se ng
the model standard devia on and the Ec I0 and Eb Nt standard devia ons for each clu er class or for all clu er classes, see
"Defining Clutter Class Properties" on page 119.
Shadowing can be taken into consideration when Atoll calculates the signal level, Ec I0, and Eb Nt for:
A point analysis (see "Making a Point Analysis to Study the Profile" on page 227)
A coverage prediction (see "Studying Signal Level Coverage" on page 229).
Atoll always takes shadowing into consideration when calculating a Monte-Carlo-based UMTS simulation.
You can display the shadowing margins and the macro-diversity gain per clutter class. For information, see "Displaying the
Shadowing Margins and Macro-diversity Gain per Clutter Class" on page 419.
6.7.9.1 Displaying the Shadowing Margins and Macro-diversity Gain per Clutter
Class
To display the shadowing margins and macro-diversity gain per clutter class:
3. Select Shadowing Margins from the context menu. The Shadowing Margins and Gains dialogue appears (see
Figure 6.95).
4. You can set the following parameters:
-
Cell Edge Coverage Probability: Enter the probability of coverage at the edge of the cell. The value you enter in
this dialogue is for information only.
Standard Deviation: Select the type of standard deviation to be used to calculate the shadowing margin or macrodiversity gains:
-
Model: The model standard deviation. Atoll will display the shadowing margin of the signal level.
EcI0: The Ec I0 standard devia on. Atoll will display the Ec I0 shadowing margin and the resul ng DL pilot
macro-diversity gains. The macro-diversity gains will be calculated using the values you enter in 1st - 2nd Best
Signal Difference and 2nd - 3rd Best Signal Difference.
419

Forsk 2011
UL EbNt: The Eb Nt UL standard devia on. Atoll will display the Eb Nt UL shadowing margin and the resul ng
UL macro-diversity gains. The macro-diversity gains will be calculated using the values you enter in 1st - 2nd
Best Signal Difference and 2nd - 3rd Best Signal Difference.
DL EbNt: The Eb Nt DL standard devia on. Atoll will display the Eb Nt DL shadowing margin.
5. If you select "Ec I0" or "Eb Nt UL" as the standard devia on under Standard Deviation, you can enter the differences
that will be used to calculate the macro-diversity gain under Macro-Diversity Parameters:
-
1st - 2nd Best Signal Difference: If you selected "Ec I0" as the standard devia on under Standard Deviation, enter
the allowed Ec I0 dierence between the best server and the second one. This value is used to calculate DL macrodiversity gains. If you selected "Eb Nt UL" as the standard devia on under Standard Deviation, enter the allowed
Eb/Nt difference between the best server and the second one. This value is used to calculate UL macro-diversity
gains.
2nd - 3rd Best Signal Difference: If you selected "Ec I0" as the standard devia on under Standard Deviation, enter
the allowed Ec I0 dierence between the second-best server and the third one. This value is used to calculate DL
macro-diversity gains. If you selected "Eb Nt UL" as the standard devia on under Standard Deviation, enter the
allowed Eb/Nt difference between the second-best server and the third one. This value is used to calculate UL
macro-diversity gains.
6. Click Calculate. The calculated shadowing margin is displayed. If you selected "Ec I0" or "Eb Nt UL" as the standard
deviation under Standard Deviation, Atoll also displays the macro-diversity gains for two links and for three links.
7. Click Close to close the dialogue.
Figure 6.95: The Shadowing Margins and Gains dialogue
6.7.10 Modelling Inter-Technology Interference

Analyses of UMTS networks co-existing with other technology networks can be carried out in Atoll. Inter-technology interference may create considerable capacity reduction in a UMTS network. Atoll can take into account interference from co-existing
networks in Monte Carlo simulations and coverage predictions.
The following inter-technology interference scenarios are modeled in Atoll:
Interference received by mobiles on the downlink: Interference can be received by mobiles in a UMTS network on
the downlink from external base stations and mobiles in the vicinity.
Interference from external base stations (also called downlink-to-downlink interference) may be created by the use
of same or adjacent carriers, wideband noise (thermal noise, phase noise, modulation products, and spurious emissions), and intermodulation. In Atoll, you can define interference reduction factor (IRF) graphs for different technologies (CDMA, TDMA, OFDM). These graphs are then used for calculating the interference from the external base
stations on mobiles. This interference is taken into account in all downlink interference-based calculations. For more
information, see "Defining Inter-Technology IRFs" on page 421.
Interference from external mobiles (also called uplink-to-downlink interference) may be created by insufficient separation between the uplink frequency used by the external network and the downlink frequency used by your UMTS
network. Such interference may also come from co-existing TDD networks. The effect of this interference is modelled
in Atoll using the Inter-technology DL Noise Rise definable for each cell in the UMTS network. This noise rise is taken
into account in all downlink interference-based calculations. However, this noise rise does not impact the calculation
of the mobile reuse factor. For more information on the Inter-technology DL Noise Rise, see "Cell Definition" on
page 205.
420

AT310_UMU_E0
You can study the downlink inter-technology interference by carrying out an Inter-technology Downlink Interference
coverage prediction as explained in "Studying Inter-Technology Downlink Interference" on page 263.
Figure 6.96: Interference received by mobiles on the downlink
Interference received by cells on the uplink: Interference can be received by cells of a UMTS network on the uplink
from external base stations and mobiles in the vicinity.
Interference from external base stations (also called downlink-to-uplink interference) may be created by insufficient
separation between the downlink frequency used by the external network and the uplink frequency used by your
UMTS network. Such interference may also come from co-existing TDD networks.
Interference from external mobiles (also called uplink-to-uplink interference) may be created by the use of same or
nearby frequencies for uplink in both networks. Unless the exact locations of external mobiles is known, it is not possible to separate interference received from external base stations and mobiles on the uplink. The effect of this interference is modelled in Atoll using the Inter-technology UL Noise Rise definable for each cell in the UMTS network.
This noise rise is taken into account in uplink interference-based calculations in the simulation. However, this noise
rise is not taken into consideration in predictions (AS Analysis and coverage predictions) and does not have an impact
on the calculation of the cell reuse factor. For more information on the Inter-technology UL Noise Rise, see "Cell Definition" on page 205.
Figure 6.97: Interference received by cells on the uplink
6.7.10.1 Defining Inter-Technology IRFs

Interference received from external base stations on mobiles of your UMTS network can be calculated by Atoll. Atoll uses
inter-technology interference reduction factor (IRF) graphs for calculating the interference levels. An IRF graph represents the
variation of the Adjacent Channel Interference Ratio (ACIR) as a function of frequency separation. ACIR is determined from
the Adjacent Channel Suppression (ACS) and the Adjacent Channel Leakage Ratio (ACLR) parameters as follows:
1
ACIR = ------------------------------------1
1
------------- + ----------------ACS ACLR
An IRF depends on:
The interfering technology (TDMA, CDMA, or OFDM)

The interfering carrier bandwidth (kHz)
The interfered carrier bandwidth (kHz)
The frequency offset between both carriers (MHz).
IRFs are used by Atoll to calculate the interference from external base stations only if the Atoll document containing the external base stations is linked to your UMTS document, i.e., when Atoll is in co-planning mode. For more information on how to
switch to co-planning mode, see "Switching to Co-planning Mode" on page 390.
421

Forsk 2011
To define the inter-technology IRFs in the victim network:

3. Right-click Inter-technology Interference Reduction Factors. The context menu appears.

4. Select Open Table from the context menu. The Inter-technology Interference Reduction Factors table appears.
5. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter:
-
Technology: Select the technology used by the interfering network.

Interferer Bandwidth (kHz): Enter the width in kHz of the channels (carriers) used by the interfering network. This
channel width must be consistent with that used in the linked document.
Victim Bandwidth (kHz): Enter the width in kHz of the channels (carriers) used by the interfered network. This
channel width must be consistent with that used in the main document.
Reduction Factors (dB): Click the cell corresponding to the Reduction Factors (dB) column and the current row in
the table. The Reduction Factors (dB) dialogue appears.
-
Enter the interference reduction factors in the Reduction (dB) column for different frequency separation,
Freq. Delta (MHz), values relative to the centre frequency of the channel (carrier) used in the main document.
Reduction values must be positive.

If you leave reduction factors undefined, Atoll assumes there is no interference.
Click OK. The interference reduction factors are stored.
You can, if you want, link more than one Atoll document with your main document following the procedure described in
"Switching to Co-planning Mode" on page 390. If the linked documents model networks using different technologies, you can
define the interference reduction factors in your main document for all these technologies, and Atollwill calculate interference from all the external base stations in all the linked documents.
422

Index
AT310_UMU_E0
Index
Symbols
+MRC in Softer/Soft (UMTS) 410
Numerics
2G network traffic, converting (UMTS) 307
3-D antenna pattern
defining attenuation 145
defining azimuth 145
defining tilt angle 145
importing 145
3GPP multi-RAT
template 92
A
ACP
antenna azimuth, reconfiguration 331, 351
antenna height, reconfiguration 331, 351
antenna masking 333
antenna type, reconfiguration 331, 351
antennas, AEDT 359
antennas, creating by pattern 359
antennas, grouping automatically 360, 361
best server analysis maps 376
candidates, creating 356
change analysis maps 375
comments, adding to optimisation 362
computation zone, using 331
configuration, loading 365
configuration, saving 365
configuring 335
co-planning optimisation process, second technology, importing
408
co-planning optimisation setup, creating 408

default settings, configuring 337
default settings, storage 335
definition 330
electrical tilt, reconfiguration 331, 351
EMF exposure 334
EMF exposure maps 376
filtering zone, using 332
hot spot, using 332
hot spots, importing 341
indoor coverage 332
iterations, defining number of 340
iterations, defining resolution 340
maps, comparing 376
maps, display properties 377
mechanical tilt, reconfiguration 331
multi-band antennas, defining 360
multi-layer networks, linking transmitters 352
optimisation parameters, defining (UMTS) 339

optimisation process, cost control 342
optimisation process, creating 338
optimisation process, creating in co-planning 407
optimisation process, EMF exposure 343
optimisation process, layers 340
optimisation process, running 339
optimisation process, site classes 343
optimisation process, zones 341
optimisation properties, changing 365
optimisation setup, running 365
optimisation, deleting 365
optimisation, running saved 363
pilot power, reconfiguration 331, 350
propagation model, default 333
propagation models 333
propagation models, defining 335
propagation models, natively supported 333
propagation models, precalculated path loss matrices 335
propagation models, precalculated pathloss matrices 334
quality analysis maps 375
reconfiguration options 331
reconfiguration options (UMTS) 349
reconfiguration, importing parameters 350, 353
results, viewing in histogram 379
results, viewing in map window 373
results, viewing in Properties dialogue 366
shadowing margin 332
site selection 331
site selection, defining 354
traffic maps, using (UMTS) 332
weighting 348
zones, using 331
ACP coverage maps
exporting (UMTS) 378
active set
conditions for entering (UMTS) 418
defining size in terminals (UMTS) 255
displaying per simulation user (UMTS) 316
size, used in predictions (UMTS) 255
threshold, defining in cells (UMTS) 206
active set analysis (UMTS) 265
adaptive modulation and coding, see "fast link adaptation"
antenna
azimuth, reconfiguring with ACP 331, 351
beamwidth, defining 144
changing azimuth on the map 22
changing relative position on the map 22
creating 143
electrical tilt, reconfiguring with ACP 331, 351
423

Index
gain 143
height, reconfiguring with ACP 331, 351
importing 3-D patterns 145
importing Planet-format 144
mechanical tilt, reconfiguring with ACP 331
model, reconfiguring with ACP 331, 351
pasting antenna pattern 143
pattern electrical tilt 143
smoothing vertical pattern 147
antenna patterns
printing 64, 147
archiving
all modifications to the database 101
only site data to the database 101
attenuation
3-D antenna pattern 145
audit of inter-technology neighbour plan (UMTS) 406
audit of neighbour allocation plan (UMTS) 287
audit of scrambling code plan (UMTS) 293
automatic backup 103
configuring 104
recovering a backup 104
Automatic Cell Planning, see "ACP"
azimuth
antenna, changing on the map 22
B
backup 103
configuring 104
recovering a backup 104
base station
assigning equipment (UMTS) 204
components of subsystem 147
copying into document (UMTS) 218
creating with template (UMTS) 210
definition (UMTS) 200, 201
displaying information (UMTS) 219
duplicating (UMTS) 218
importing (UMTS) 218
beamwidth
defining antenna 144
bearer selection, HSDPA, explanation (UMTS) 310
bearer, downgrading (UMTS) 312
bearer, R99, see "R99 radio bearer"
BER coverage prediction (UMTS) 260
BLER coverage prediction (UMTS) 260
C
calculation
min. interferer reception threshold, defining (UMTS) 411
min. pilot RSCP threshold, defining (UMTS) 411
calculation process, explanation (UMTS) 235
calculations 155
CDMA Rho factor, transmitter equipment 149
CDMA2000 1xRTT 1xEV-DO
template 92
424
Forsk 2011
cell
creating (UMTS) 210
modifying (UMTS) 210
parameters (UMTS) 205
setting as active (UMTS) 236
updating values with simulation (UMTS) 326
channel element
calculation of consumption (UMTS) 309
consumption per site equipment-HSUPA radio bearer, defining
(UMTS) 415
consumption per site equipment-R99 radio bearer, defining
(UMTS) 414
downlink, defining (UMTS) 202
simulations (UMTS) 313
uplink and downlink consumption (UMTS) 414
uplink, defining (UMTS) 202
column headers
formatting 51
columns
changing width 51
displaying 52
freezing 53
hiding 52
moving 53
unfreezing 53
compressed mode (UMTS) 255, 256, 318, 411
computation zone
ACP 331
drawing 34
drawing (UMTS) 236
editing 39
explanation (UMTS) 231
Fit to Map Window 35
Fit to Map Window (UMTS) 236
importing 35
polygon, creating from 35
polygon, creating from (UMTS) 236
configuration
loading ACP 365
saving ACP 365
Connection Properties 98
connection status
traffic distribution, displaying by (UMTS) 315
constraint costs, defining scrambling code(UMTS) 290
context menu 19
renaming objects 19
coordinate system 94
setting 95
coordinates, searching by 84
co-planning
co-planning mode, ending (UMTS) 408
co-planning mode, switching to (UMTS) 390
inter-technology exceptional pairs, displaying (UMTS) 397
inter-technology exceptional pairs, setting (UMTS) 396
inter-technology exceptional pairs, setting on the map (UMTS)
397

Index
AT310_UMU_E0
inter-technology neighbour allocation (UMTS) 396

inter-technology neighbours, allocating automatically (UMTS)
398
inter-technology neighbours, allocating per cell (UMTS) 401

inter-technology neighbours, allocating using Neighbours table
(UMTS) 402
inter-technology neighbours, displaying (UMTS) 400
inter-technology neighbours, setting on the map (UMTS) 403
legend window, displaying (UMTS) 393
neighbours, configuring importance of (UMTS) 398
networks, coverage areas, comparing (UMTS) 394
networks, coverage areas, studying differences (UMTS) 395
networks, coverage predictions, analysing (UMTS) 393
networks, coverage predictions, updating (UMTS) 392
networks, displaying both in same document (UMTS) 391
UMTS 390
unlinking documents (UMTS) 408
Cost-Hata propagation model 164
creating environment formula 165
defining default environment formula 165
modifying environment formula 165
taking diffraction into account 165
coverage of neighbours, displaying (UMTS) 282
coverage prediction
assigning a default propagation model 175
by transmitter (UMTS) 239
calculating 191, 192
calculating several 191
cloning 190
comparing (UMTS) 246
creating 189
creating from existing 190
downlink total noise (UMTS) 261
duplicating 190
effective service area (UMTS) 259
exporting in user configuration 194
exporting results 42
filtering base stations studied by computation zone (UMTS) 227
filtering base stations studied by filter (UMTS) 227
forcing calculation 192
geographic export zone, defining (UMTS) 270
geogrphic export zone, defining 38
handover status (UMTS) 264
histogram, viewing (UMTS) 245
HSDPA (UMTS) 267
HSUPA (UMTS) 269
legend, adding values to (UMTS) 242
locking coverage predictions 192, 193
new 189
overlapping zones (UMTS) 240
pilot pollution (UMTS) 262
pilot reception analysis (Ec/I0) based on test mobile data path
(UMTS) 385
pilot signal quality (UMTS) 256
printing results (UMTS) 270
quality indicator (UMTS) 260
report, displaying (UMTS) 244
report, displaying using focus zone 35

report, displaying using focus zone (UMTS) 243
report, displaying using hot spot (UMTS) 243
report, displaying using hot spot zone 35
results, analysing (UMTS) 241
results, displaying with tip text (UMTS) 242
results, exporting (UMTS) 270
scrambling code interference zone (UMTS) 296
service area (Eb/Nt) downlink based on test mobile data path
(UMTS) 385
service area (Eb/Nt) downlink or uplink (UMTS) 258
service area (Eb/Nt) uplink based on test mobile data path
(UMTS) 386
signal level - single station (UMTS) 229
signal level (UMTS) 237
simulation results, based on (UMTS) 329
statistics, viewing (UMTS) 245
stopping calculation 192
template, saving as 193
test mobile data path, based on (UMTS) 385
tip text, comparing coverage predictions with (UMTS) 393
coverage predictions 189
cursors 46
CW Measurement Analysis Tool
printing data 64
CW measurements
test mobile data path, generating from (UMTS) 389
D
Data tab 17
data tables
adding a field 48
changing column width 51
changing row height 51
copying data 54
deleting a field 49
displaying columns 52
editing 49
exporting data 57
filtering 69
filtering by selection 71
filtering by several criteria 72
filtering, examples 73
formatting column headers 51
formatting table columns 51
freezing columns 53
hiding columns 52
importing data 58
moving columns 53
opening 47
opening record properties from table 50
pasting data 54
printing 60
restoring after filtering 73
sorting 69
sorting by one column 70
sorting by several columns 70
425

Index
unfreezing columns 53
viewing properties 47
XML files, exporting to 59
XML files, importing from 59
database
archiving all modifications 101
archiving only site data 101
connecting to 98
Connection Properties 98
creating a document from 97
refreshing document 100
resolving data conflicts 101
working with 96
defining 188, 194
defraction
smoothing vertical antenna pattern 147
display
changing properties 23
defining display type 24
display type, automatic 25
display type, discrete values 24
display type, unique 24
display type, value intervals 24
display coordinate system 94
display resolution (UMTS) 229
Distance Measurement tool 32
diversity
reception (UMTS) 213, 415
transmission (UMTS) 213, 415
document
creating from database 91, 97
creating from template 91, 92
geographic data 91
information needed to create 91
radio data 91
radio equipment 91
refreshing from the database 100
setting basic parameters 94
document templates, see "templates"
domains, creating scrambling code(UMTS) 289
downgrading bearer (UMTS) 312
downlink total noise coverage prediction (UMTS) 261
downlink total power, setting (UMTS) 251
DTM maps representing different areas 130
dual-band network, creating (UMTS) 220
E
Ec/I0 threshold (UMTS) 254
effective service area coverage prediction (UMTS) 259
EMF exposure
ACP, studying with 334
environment
creating (UMTS) 301
Equipment Specifications dialogue (UMTS) 204
equipment, repeater, see "repeater equipment"
Erceg-Greenstein (SUI) propagation model 167
426
Forsk 2011
assigning environment formulas 168

exceptional pairs
inter-technology, displaying (UMTS) 397
inter-technology, setting (UMTS) 396
inter-technology, setting on the map (UMTS) 397
exceptional pairs, defining neighbour (UMTS) 275
exceptional pairs, defining scrambling code (UMTS) 290
Explorer window 17
Data tab 17
Geo tab 18
layers 19
Modules tab 18
using tabs 17
F
fast link adaptation (UMTS) 310
feeder
assigning (UMTS) 204
defining cables 148
length, defining (UMTS) 204
FER coverage prediction (UMTS) 260
field
adding to a table 48
deleting from a table 49
filter
site list, using for 79
transmitter list, using for 79
filtering
data tables by selection 71
data tables by several criteria 72
examples 73
restoring after filtering 73
using a polygon 33, 82
with views 81
filtering zone
deleting 38
drawing 33
importing 34
Find on Map 83
scrambling codes, displaying with (UMTS) 294
searching by coordinates 84
searching by text property 84
focus zone
coverage prediction report, using to display (UMTS) 243
creating 35
creating (UMTS) 243
editing 39
explanation 35
explanation (UMTS) 243

Index
AT310_UMU_E0
importing 36
polygon, creating from (UMTS) 243
population statistics (UMTS) 245
using to display coverage prediction report 35
folder configuration 80
applying a saved configuration 80
creating 80
deleting 81
exporting 81
importing 81
reapplying current configuration 80
frequency bands
defining (UMTS) 203, 409
G
gain
defining antenna 143
Geo tab 18
geographic export zone
creating 38
creating (UMTS) 270
importing 38
global network settings (UMTS) 410
global scaling factor (UMTS) 328
global transmitter parameters
grouping 65
by a property 65, 66
by several properties 66
examples 67
with views 81
groups, creating scrambling code (UMTS) 289
GSM/GPRS/EGPRS template 92
H
handover status
coverage prediction (UMTS) 264
traffic distribution, displaying by (UMTS) 315
hexagonal design
definition (UMTS) 211
histogram
coverage prediction, viewing (UMTS) 245
results, viewing ACP 379
scrambling code (UMTS) 296
hot spot
coverage prediction report, using to display (UMTS) 243
creating (UMTS) 243
population statistics (UMTS) 245
hot spot zone
creating 35
editing 39
explanation 35
importing 36
using to display coverage prediction report 35
HSDPA
activating (UMTS) 207
bearer selection, explanation (UMTS) 310
configuring (UMTS) 207
scheduler algorithm 208
service, enabling (UMTS) 252
template 92
terminal, enabling (UMTS) 255
user equipment category 256
user equipment category, editing (UMTS) 417
HSDPA radio bearer
defining (UMTS) 412
HSPA+
activating (UMTS) 207, 215
HSUPA
activating (UMTS) 207, 215
configuring (UMTS) 208
service, enabling (UMTS) 252
template 92
terminal, enabling (UMTS) 255
user equipment category, editing (UMTS) 417
HSUPA radio bearer
defining (UMTS) 413
I
indoor coverage
ACP 332
activating in simulation (UMTS) 261
AS analysis, activating in (UMTS) 266
AS analysis, activating in(UMTS) 297
calculating 188, 194
coverage prediction, activating in (UMTS) 230
modelling environment, defining when (UMTS) 302
modelling user profile traffic map, defining when (UMTS) 303
point analysis, activating in (UMTS) 228, 243
simulation results (UMTS) 321
simulation, activating in (UMTS) 259
traffic map (UMTS) 299
indoor losses 188, 194
inter-carrier interference, defining (UMTS) 409
interference
inter-carrier, defining (UMTS) 409
interference reduction factor
using assistant (MW) 152
interference zone coverage prediction, scrambling code (UMTS) 296
inter-technology DL noise rise (UMTS) 207
inter-technology UL noise rise (UMTS) 207
ITU 1546 propagation model 170
ITU 370-7 propagation model (Vienna 93) 166, 167
ITU 526-5 propagation model 169
ITU 529-3 propagation model
427

Index

Iub backhaul throughput
consumption per site equipment-HSUPA radio bearer, defining
(UMTS) 415
consumption per site equipment-R99 radio bearer, defining
(UMTS) 414
L
label 26
Lambert Conformal-Conic projection 94
layers 19
legend
adding object type 27
co-planning, displaying window in (UMTS) 393
displaying 27
displaying (UMTS) 242
displaying Legend window 32
printing Legend window 64
lines
editing 39
Longley-Rice propagation model 170
LTE
template 92
M
macro-diversity gain
clutter class, displaying per (UMTS) 419
map
centring on a selected object 31
exporting as image 45
measuring distances 32
moving 30
printing 60
refreshing display 83
saving as image 45
Map toolbar 86
masthead amplifier, see "TMA"
matrix, see "path loss matrix"
measurement units, setting 96
measuring distances on the map 32
Microwave Link Analysis
printing 64
MIMO
receive diversity (UMTS) 418
spatial multiplexing (UMTS) 418
transmit diversity (UMTS) 418
mobility type
creating (UMTS) 254
parameters used in predictions (UMTS) 254
Modules tab 18
Monte-Carlo-based user distribution (UMTS) 308
428
Forsk 2011
MUD, see "multi-user detection"

multi-carrier network (UMTS) 205
multi-point analysis
active set analysis (UMTS) 271
adding to a group (UMTS) 272
changing display (UMTS) 274
creating (UMTS) 271
potential server analysis (UMTS) 271
results, accessing (UMTS) 273
multi-point analysis (UMTS) 271
multi-RAT
template 92
multi-user detection factor
site equipment, defining in (UMTS) 414
terminals, defining in (UMTS) 256
multi-user environment 96
N
neighbours
allocating automatically (UMTS) 276
allocating on the map (UMTS) 285
allocating per cell (UMTS) 283
allocating using Cells tab of Transmitter Properties (UMTS) 283
allocating using Neighbours table (UMTS) 284
audit of allocation (UMTS) 287
audit of inter-technology (UMTS) 406
comparing existing and allocated (UMTS) 278, 279
deleting on the map (UMTS) 285
deleting per cell (UMTS) 283
deleting using Cells tab of Transmitter Properties (UMTS) 283
deleting using Neighbours table (UMTS) 284
displaying (UMTS) 280
displaying coverage (UMTS) 282
exceptional pairs, defining (UMTS) 275
importance in co-planning, configuring (UMTS) 398
importance, configuring (UMTS) 276
inter-technology, allocating (UMTS) 396
inter-technology, allocating automatically (UMTS) 398
inter-technology, allocating per cell (UMTS) 401
inter-technology, allocating using Neighbours table (UMTS) 402
inter-technology, comparing existing and allocated (UMTS) 400
inter-technology, displaying (UMTS) 400
inter-technology, setting on the map (UMTS) 403
possible (UMTS) 274
network
global parameters (UMTS) 410
network, creating dual-band (UMTS) 220
noise figure 149
noise figure (UMTS) 204
non-symmetric neighbours, displaying (UMTS) 280
O
objects
changing transparency 25
deleting 20
AT310_UMU_E0
displaying 18
displaying properties 20
grouping 65
grouping by a property 65, 66
grouping by several properties 66
grouping, examples 67
hiding 18
label 26
tip text 26
visibility scale 25
Okumura-Hata model 163, 164
Okumura-Hata propagation model 163, 164
optimisation
ACP optimisation parameters, defining (UMTS) 339
co-planning ACP setup, creating 408
creating and defining site classes 343
creating new ACP process 338
defining cost control 342
defining layers 340
defining zones 341
deleting 365
EMF exposure parameters, defining 343
properties, changing 365
running ACP process 339
running ACP setup 365
running saved ACP 363
second technology, importing 408
overlapping zones coverage prediction (UMTS) 240
OVSF codes
consumption, calculating (UMTS) 309
maximum number of codes available for HS-PDSCH (UMTS) 208
minimum number of codes available for HS-PDSCH (UMTS) 208
orthogonality factor, default (UMTS) 410
simulations (UMTS) 313
P
Page Setup, see "printing"
Panoramic window 16, 30
Path loss calculation 161, 162
Systematic 161, 162
path loss calculation
radial 161, 162
path loss matrices
adjusting using CW measurements 180, 181
defining area to be adjusted with measurement data 179
tuning using measurement data 178, 179
path loss matrix
calculation process (UMTS) 235
exporting 185
resolution (UMTS) 213
storing 176
storing (UMTS) 232

Index
validity, checking 177

validity, checking (UMTS) 233
pattern electrical tilt 143
pilot pollution coverage prediction (UMTS) 262
pilot power
reconfiguration with ACP 331, 350
pilot reception analysis (Ec/I0) based on test mobile data path
(UMTS) 385
pilot signal quality coverage prediction (UMTS) 256
Planet
importing antennas 144
point analysis
opening Point Analysis Tool window 186
shadowing, calculating 188
starting 186
Point Analysis window
active set analysis of simulation (UMTS) 329
AS Analysis view (UMTS) 265
printing 64
Profile view (UMTS) 227
Reception view (UMTS) 242
points
editing 39
polygon
computation zone, using as (UMTS) 236
deleting polygon filter 38
drawing a polygon filter 33
editing 39
focus zone, using as 36
focus zone, using as (UMTS) 243
geographic export zone, using as 38
printing zone, using as 62
using as computation zone 35
using as filter 33, 82
using as filtering zone 34
population statistics
integrable data (UMTS) 245
report, including in (UMTS) 245
possible neighbours, definition (UMTS) 274
power
maximum power in cells, defining (UMTS) 206
other CCH power in cells, defining (UMTS) 206
pilot power in cells, defining (UMTS) 206
SCH power in cells, defining (UMTS) 206
power control simulation algorithm (UMTS) 309
predictions
overview 189
printing
antenna patterns 64, 147
coverage prediction results (UMTS) 270
CW Measurement Analysis Tool 64
data tables and reports 60
defining print layout 62
docking windows 64
Legend window 64
map 60
Microwave Link Analysis 64
429

Index
Point Analysis window 64

print preview 64
recommendations 61
Test Mobile Data Analysis Tool 64
printing zone
drawing 61
importing 62
Profile 161, 162
Systematic extraction 161, 162
profile
radial extraction 161, 162
projection coordinate system 94
Lambert Conformal-Conic projection 94
Universal Transverse Mercator projection 94
propagation model
ACP, default 333
ACP, natively supported 333
ACP, using precalculated path loss matrices with 335
ACP, using precalculated pathloss matrices with 334
ACP, using with 333
assigning a default model for predictions 175
assigning to a transmitter (UMTS) 235
assigning to all transmitters 174
assigning to all transmitters (UMTS) 234
assigning to group of transmitters 174
assigning to group of transmitters (UMTS) 234
Cost-Hata 164
Cost-Hata, diffraction 165
Erceg-Greenstein (SUI) 167
Erceg-Greenstein (SUI), diffraction 168
ITU 1546 170
ITU 370-7 (Vienna 93) 166, 167
ITU 526-5 169
ITU 529-3, diffraction 166
Longley-Rice 170
Okumura-Hata 163, 164
Okumura-Hata, diffraction 163
Sakagami extended 171
signature 172
Standard Propagation Model 156
Standard Propagation Model, correction factor for hilly regions
162
Standard Propagation Model, defining parameters 160

Standard Propagation Model, diffraction 158
Standard Propagation Model, recommendations 157
WLL 169
properties
changing display 23
grouping objects by 65, 66
switching between property dialogues 20
Q
quality indicator coverage prediction (UMTS) 260
430
Forsk 2011
R
R99 radio bearer
creating (UMTS) 412
radial 161, 162
radio resource management
calculation of channel element consumption (UMTS) 309
channel element consumption per site equipment-R99 radio
bearer, defining (UMTS) 414, 415
channel elements on downlink, defining (UMTS) 202
channel elements on uplink, defining (UMTS) 202
channel elements, simulations (UMTS) 313
maximum number of OVSF codes available for HS-PDSCH (UMTS)
208
minimum number of OVSF codes available for HS-PDSCH (UMTS)

208
orthogonality factor, default (UMTS) 410

OVSF code consumption, calculating (UMTS) 309
OVSF codes, simulations (UMTS) 313
uplink and downlink channel element consumption (UMTS) 414
Radio toolbar 85
receiver
height, defining (UMTS) 411
receiver antenna diversity gain, defining (UMTS) 204
reception equipment
creating (UMTS) 415
reconfiguration
ACP parameters, importing 350
importing ACP parameters 353
redo 83
reflection
smoothing vertical antenna pattern 147
refresh 83
from the database 100
Refresh Geo data (UMTS) 385
remote antenna
placing on the map (UMTS) 224
properties, defining (UMTS) 225
remote antenna table, opening (UMTS) 224
renaming 19
repeater
cascading (UMTS) 221
placing on the map (UMTS) 221
properties, defining (UMTS) 222
repeater table, opening (UMTS) 220
repeater equipment
creating (UMTS) 220, 224
modifying (UMTS) 220, 224
report, displaying a coverage prediction (UMTS) 244
reports
printing 60
AT310_UMU_E0
resolution
display (UMTS) 229
path loss matrix (UMTS) 213
row height
changing 51
rulers
displaying 32
S
Sakagami extended propagation model 171
scale level, choosing 30
scheduler
explanation of scheduling technique (UMTS) 311
HSDPA scheduler algorithm, selecting 208
scrambling codes
allocating, automatically (UMTS) 291
allocating, manually (UMTS) 293
audit of plan (UMTS) 293
constraint costs, defining (UMTS) 290
defining available (UMTS) 289
displaying allocation (UMTS) 294
displaying on transmitter (UMTS) 295
domains and groups, creating (UMTS) 289
exceptional pairs, defining (UMTS) 290
Find on Map, finding with (UMTS) 294
format, defining (UMTS) 289
grouping transmitters by (UMTS) 295
histogram (UMTS) 296
interference zone coverage prediction (UMTS) 296
scrambling codes (UMTS) 288
searching for map objects 83, 84
secondary antenna, assigning (UMTS) 205
service
creating (UMTS) 252
displaying traffic distribution by (UMTS) 316
HSDPA, enabling (UMTS) 252
HSUPA, enabling (UMTS) 252
priority, defining (UMTS) 253
soft handover, activating (UMTS) 253
service area (Eb/Nt) downlink based on test mobile data path
(UMTS) 385
service area (Eb/Nt) downlink or uplink coverage prediction (UMTS)
258
service area (Eb/Nt) uplink based on test mobile data path (UMTS)
386
shadowing 188, 194

point analysis, calculating in 188
shadowing (UMTS) 410, 419
shadowing margin
ACP 332
clutter class, displaying per (UMTS) 419
signal level coverage
single station (UMTS) 229
signal level coverage prediction (UMTS) 237

Index
simulation
adding to a group (UMTS) 326, 327
average results of group (UMTS) 322
coverage predictions, using results for (UMTS) 329
creating (UMTS) 313
displaying active set per user (UMTS) 316
duplicating (UMTS) 327, 328
generator initialisation number (UMTS) 326, 328
global scaling factor (UMTS) 328
power control algorithm (UMTS) 309
replaying (UMTS) 326, 327
results of single (UMTS) 317
traffic increase, estimating (UMTS) 328
updating cell values with results (UMTS) 326
site
creating (UMTS) 209
moving on the map 21
moving to a higher location 21
parameters (UMTS) 202
properties, accessing from the Explorer window 20
properties, accessing from the map 20
site equipment
channel element consumption per R99 radio bearer, defining
(UMTS) 414, 415
creating (UMTS) 413
Iub backhaul throughput, defining (UMTS) 414, 415
site list 77
adding 78, 79
adding site 78
creating 77
editing 79
filter, using as 79
slow fading, see "shadowing"
snapshot, definition (UMTS) 297
soft handover
activating per service (UMTS) 253
modelling on the downlink (UMTS) 323
modelling on the uplink (UMTS) 253, 323, 410
sorting
sorting tables by one column 70
sorting tables by several columns 70
with views 81
SPM Parameters tab window 161, 162
Standard Propagation Model 156, 161, 162
calculating diffraction 158
correction factor for hilly regions 162
defining parameters 160
recommendations 157
sample values for constants 158
typical values for losses per clutter class 160
Standard toolbar 85
station template
copying properties from another template (UMTS) 217
creating (UMTS) 212
creating base station (UMTS) 210
431

Index
deleting (TD-SCDMA) 217

field, modifying (UMTS) 217
statistics, viewing coverage prediction (UMTS) 245
study, see "coverage prediction"
symmetric neighbours, displaying (UMTS) 280
T
table columns
formatting 51
Table toolbar 87
tables, see "data tables"
TD-SCDMA
template 92
template
coverage prediction, using as 193
templates 92
3GPP multi-RAT 92
CDMA2000 1xRTT 1xEV-DO 92
GSM/GPRS/EGPRS 92
LTE 92
TD-SCDMA 92
UMTS HSDPA HSUPA 92
WiMAX 92
terminal
creating (UMTS) 255
HSDPA, enabling (UMTS) 255
HSUPA, terminal (UMTS) 255
Test Mobile Data Analysis Tool
printing 64
test mobile data path
coverage prediction, using in (UMTS) 385
exporting to CW measurements (UMTS) 389
extracting a field for a transmitter (UMTS) 387
filtering out points (UMTS) 383
pilot reception analysis (Ec/I0), using for (UMTS) 385
Refresh Geo Data (UMTS) 385
service area (Eb/Nt) downlink, using for (UMTS) 385
service area (Eb/Nt) uplink, using for (UMTS) 386
variations, analysing (UMTS) 387
Test Mobile Data window
printing (UMTS) 389
tilt angle
tip text 26
comparing coverage predictions, co-planning (UMTS) 393
displaying coverage prediction results with (UMTS) 242
TMA
defining 148
TMS, assigning (UMTS) 204
tool tips, see "tip text"
432
Forsk 2011
toolbar
icons 85
Map 86
Radio 85
Standard 85
Table 87
Vector Editor 86
Windows 87
total losses, updating 149
total noise on downlink, see "downlink total noise"
traffic distribution
connection status, displaying by (UMTS) 315
creating, see "simulation"
displaying by service (UMTS) 316
handover status, displaying by (UMTS) 315
traffic increase, estimating (UMTS) 328
traffic map
data sources (UMTS) 298
exporting cumulated traffic (UMTS) 307
importing traffic map based on user profile densities (UMTS) 302
live data, creating from (UMTS) 299
sector (UMTS) 298
statistics on user profile environment based traffic map (UMTS)
305
user density (UMTS) 305

user density traffic map, importing (UMTS) 305
user density, creating (UMTS) 306
user density, creating from sector traffic maps (UMTS) 307
user profile (UMTS) 300
user profile environment based, creating (UMTS) 304
user profile environment based, importing (UMTS) 304
traffic maps
ACP, using with (UMTS) 332
converting 2G (UMTS) 307
traffic quality studies, see "quality studies"
transmitter
coverage prediction by transmitter (UMTS) 239
creating (UMTS) 209
definition (UMTS) 200, 202
extracting a field from a test mobile data path (UMTS) 387
grouping by scrambling codes (UMTS) 295
modifying global properties (UMTS) 411
scrambling codes, displaying (UMTS) 295
setting as active (UMTS) 236
transmitter equipment
assigning (UMTS) 204
CDMA Rho factor 149
defining 148
noise figure, updating 149
transmitter list 77
adding 78, 79
adding transmitter 78
creating 77
editing 79
editing filter 79

Index
AT310_UMU_E0
transmitters
automatic display type 25
transparency, changing 25
U
UMTS HSDPA HSUPA
template 92
undo 83
Universal Transverse Mercator projection 94
uplink load factor, setting (UMTS) 251
user configuration 76
coverage prediction, exporting 194
creating 76
exporting 76
importing 77
user density traffic map
creating (UMTS) 306
creating from sector traffic maps (UMTS) 307
user distribution, Monte-Carlo-based (UMTS) 308
user equipment category, HSDPA 256
user equipment category, HSDPA, editing (UMTS) 417
user equipment category, HSUPA, editing (UMTS) 417
user profile
creating (UMTS) 300
user profile densities
importing traffic map based on (UMTS) 302
user profile environment based traffic map
creating (UMTS) 304

statistics on (UMTS) 305
V
Vector Editor toolbar 86
Vienna 93 model 166, 167
views
creating 81
visibility scale 25
W
WiMAX
template 92
windows
cascading 16
docking 16
floating 16
Windows toolbar 87
wireless local loop propagation model 169
WLL (Wireless Local Loop) propagation model 169
X
XML
exporting data tables to 59
importing data tables from 59
Z
zooming
choosing a scale 30
in on a specific area 30
433

Index
434
Forsk 2011

AT310_UMU_E0
435
User Manual
UMTS
version 3.1.0
AT310_UMU_E0
February 2011
Head Office
7, rue des Briquetiers
31700 Blagnac - France
Tel: +33 562 747 210
Fax: +33 562 747 211
US Office
200 South Wacker Drive - Suite 3100
Chicago, IL 60606 - USA
Tel: +1 312 674 4846
Fax: +1 312 674 4847
China Office
Suite 302, 3/F, West Tower,
Jiadu Commercial Building,
No. 66 Jianzhong Road,
Tianhe Hi-Tech Industrial Zone,
Guangzhou, 510665, P. R. of China
Tel: +86 20 8553 8938
Fax: +86 20 8553 8285
www.forsk.com

Atoll 3.1.0 User Manual UMTS

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Atoll 3.1.0 User Manual UMTS

Uploaded by

Copyright:

Available Formats

User Manual

experts in radio network planning

Forsk USA Office

Forsk Head Office

Forsk China Office

200 South Wacker Drive

7 rue des Briquetiers

Suite 302, 3/F, West Tower,

Jiadu Commercial Building,

No.66 Jianzhong Road,

Tianhe Hi-Tech Industrial Zone,

+1 312 674 4846

+33 (0) 562 747 210

+86 20 8553 8938

+1 312 674 4847

+33 (0) 562 747 211

+86 20 8553 8285

+1 888 GoAtoll (+1 888 462 8655)

+33 (0) 562 747 225

+86 20 8557 0016

8.00 am to 8.00 pm (EST)

9.00 am to 6.00 pm (CET)

9.00 am to 5.30 pm (GMT+8)

Atoll 3.1.0 User Manual Release AT310_UMU_E0

Copyright 1997 - 2011 by Forsk

Atoll 3.1.0 User Manual

The Working Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

The Atoll Work Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

The Explorer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Working with Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Working with Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Atoll 3.1.0 User Manual

Exporting Multiple Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Working with Data Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Printing in Atoll. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Grouping, Sorting, and Filtering Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Atoll 3.1.0 User Manual

Tips and Tricks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Starting an Atoll Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Before Starting a Radio-Planning Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Creating an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Making a Backup of Your Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Making and Sharing Portable Atoll Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Geographic Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Supported Geographic Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Importing Geo Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Digital Terrain Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Clutter Heights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Contours, Lines, and Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Scanned Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Atoll 3.1.0 User Manual

Population Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Custom Geo Data Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Setting the Priority of Geo Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Displaying Information About Geo Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Geographic Data Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Editing Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Saving Geographic Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Antennas and Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Working With Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Working With Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Working with Calculations in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155