Académique Documents
Professionnel Documents
Culture Documents
User Manual
for Radio Networks
AT332_UMR_E0
AT332_UMR_E0
AT332_UMR_E0
Table of Contents
Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Atoll 3.3.2 User Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
About Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
About Forsk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Printing Help Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
About Atoll Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.1
1.1.1
1.1.1.1
1.1.1.2
1.1.2
1.1.2.1
1.1.2.2
1.1.2.3
1.1.2.4
1.1.2.5
1.1.3
1.1.3.1
1.1.3.2
1.1.3.3
1.1.3.4
1.1.3.5
1.1.4
1.1.4.1
1.1.4.2
1.1.4.3
1.1.5
Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Standalone Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Available Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Creating a Standalone Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Documents Connected to a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Atoll Multi-User Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Creating a Document from a Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Checking the Database Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Refreshing a Document from the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Archiving the Modifications in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Configuring Document Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Projection and Display Coordinate Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Setting a Coordinate System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Selecting the Degree Display Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Setting Measurement Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Defining a Project Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Saving Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Saving a Copy of a Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Creating and Sharing Portable Atoll Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Configuring Automatic Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Opening Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
1.2
1.2.1
1.2.2
1.2.3
1.2.4
1.2.4.1
1.2.4.2
1.2.4.3
1.2.4.4
1.2.4.5
1.2.4.6
1.3
1.3.1
1.3.2
1.3.3
1.3.3.1
1.3.3.2
1.3.4
1.3.5
1.3.5.1
1.3.5.2
1.3.5.3
Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Renaming an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Deleting an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Modifying the Visibility of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Displaying or Hiding Objects on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Changing the Order of Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Accessing Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Setting the Display Properties of Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Setting the Display Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Setting the Transparency of Objects and Object Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Setting the Visibility Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
1.3.5.4
1.3.5.5
1.3.5.6
1.3.5.7
1.3.5.8
1.3.6
1.3.6.1
1.3.6.2
1.3.6.3
1.3.6.4
1.3.6.5
1.3.7
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.3.1
1.4.3.2
1.4.3.3
1.4.3.4
1.4.4
1.4.5
1.4.6
1.4.7
1.4.8
1.4.8.1
1.4.8.2
1.4.8.3
1.4.8.4
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.10.7
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.12
Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Configuring the Layout of the Map Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Displaying the Map Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Displaying Rulers Around the Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Displaying the Map Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Using Full Screen Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Moving the Map in the Document Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Changing the Map Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Zooming In and Out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Choosing a Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Changing Between Previous Zoom Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Adjusting the Map Window to a Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Using the Panoramic Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Opening a New Map Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Centring the Map Window on a Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Favourite Map Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Searching for Objects on the Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Searching for a Map Object by Its Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Searching for a Map Object using Any Text Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Searching for a Point on the Map by its Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Searching for a Point on the Map by its Full or Partial Postal Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Measuring Distances on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Using Zones in the Map Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Filtering Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Computation Zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Focus Zone and Hot Spots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Printing Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Geographic Export Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Creating Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Editing Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Vector Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Adding a Vector Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Creating Polygons, Lines, and Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Editing Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Editing Polygon Contours and Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Creating Complex Polygons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Map Window Pointers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
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.4.1
1.5.4.2
1.5.4.3
1.5.4.4
1.5.4.5
1.5.4.6
1.5.5
1.5.5.1
AT332_UMR_E0
1.5.5.2
1.5.5.3
1.5.6
1.5.7
1.5.8
1.5.9
1.5.10
1.6
1.6.1
1.6.2
1.6.2.1
1.6.2.2
1.6.3
1.6.4
1.6.5
Printing in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Printing Data Tables and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Printing a Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Printing Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Defining the Print Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Previewing Your Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Printing a Docking Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Printing Antenna Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
1.7
1.7.1
1.7.1.1
1.7.1.2
1.7.1.3
1.7.1.4
1.7.1.5
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.3.5
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.5.7
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.8
1.9
1.9.1
1.9.2
2.1
2.2
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.4.1
2.3.4.2
2.3.5
2.3.6
2.3.6.1
2.3.6.2
2.3.6.3
2.3.7
2.3.8
2.4
2.5
2.5.1
2.5.2
2.5.3
2.5.4
2.5.5
Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning Names to Clutter Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Clutter Class Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Clutter Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Refreshing the List of Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Total Surface Area per Clutter Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6
2.7
2.7.1
2.7.2
2.7.3
2.8
2.8.1
2.8.2
2.9
2.9.1
2.9.2
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10.5
133
134
135
135
136
136
2.11
2.11.1
2.11.2
2.11.3
2.11.4
136
137
137
138
138
2.12
2.12.1
2.12.2
2.12.2.1
2.12.2.2
138
138
139
140
140
119
120
120
121
122
122
122
122
124
124
124
125
125
126
126
126
127
129
129
130
130
130
131
131
AT332_UMR_E0
2.12.2.3
2.13
2.14
2.14.1
2.14.2
2.15
2.15.1
2.15.1.1
2.15.1.2
2.15.1.3
2.15.1.4
2.15.2
2.16
2.16.1
2.16.1.1
2.16.1.2
2.16.2
2.16.3
2.16.4
2.16.5
3.1
3.1.1
3.1.2
3.1.3
3.1.3.1
3.1.3.2
3.1.4
3.1.4.1
3.1.4.2
3.1.4.3
3.1.4.4
3.1.4.5
3.1.4.6
3.1.5
3.1.6
3.1.7
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
4
4.1
4.1.1
4.1.2
4.1.2.1
4.1.2.2
4.1.2.3
4.1.2.4
4.1.2.5
4.1.2.6
4.1.2.7
4.1.3
4.1.4
4.1.5
4.1.5.1
4.1.5.2
4.1.5.3
4.1.6
4.1.6.1
4.1.6.2
4.1.6.3
4.1.7
4.1.7.1
4.1.7.2
4.1.7.3
4.1.8
4.1.9
4.1.9.1
4.1.9.2
4.1.9.3
4.1.10
4.1.11
4.1.12
4.1.13
4.1.14
4.1.15
179
179
179
180
180
180
181
181
181
181
182
182
182
183
183
183
184
184
185
185
4.2
4.2.1
4.2.2
4.2.2.1
4.2.2.2
4.2.2.3
4.2.2.4
4.2.3
4.2.3.1
4.2.3.2
4.2.3.3
186
186
187
188
188
189
189
189
190
190
190
4.3
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
4.3.6
4.3.7.1
4.3.7.2
4.3.7.3
4.3.7.4
4.3.7.5
4.3.8
190
190
191
192
192
193
194
196
196
197
198
199
201
4.4
4.4.1
4.4.2
4.4.3
4.4.4
4.4.5
4.4.6
Point Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting a Point Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Views of the Point Analysis Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Moving the Receiver on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Centring the Map Window on the Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Taking Indoor Losses into Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Taking Shadowing into Account in Point Analyses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
201
201
202
203
203
203
204
4.5
4.5.1
4.5.2
4.5.3
4.5.4
4.5.4.1
4.5.4.2
4.5.4.3
4.5.4.4
4.5.4.5
4.5.4.6
4.5.5
4.5.5.1
Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Coverage Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Duplicating Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cloning Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calculating Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calculating a Single Coverage Prediction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calculating Multiple Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Forcing Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stopping Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Locking and Unlocking Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
External Storage of Coverage Prediction Numerical Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving Defined Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving a Coverage Prediction as a Customised Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
204
204
205
205
206
207
207
207
207
207
208
209
209
AT332_UMR_E0
4.5.5.2
4.5.6
4.5.6.1
4.5.6.2
4.5.6.3
4.5.7
4.5.7.1
4.5.7.2
4.5.7.3
4.5.8
4.5.9
4.5.9.1
4.5.9.2
4.5.10
5.1
5.1.1
5.1.2
5.2
5.2.1
5.2.2
5.2.3
5.2.4
5.3
5.3.1
5.3.2
5.3.3
5.4
5.4.1
5.4.2
5.4.3
5.5
5.5.1
5.5.2
5.5.3
5.5.4
5.6
5.7
5.7.1
5.7.2
6.1
6.1.1
6.1.1.1
6.1.1.2
6.1.2
6.1.2.1
6.1.2.2
6.1.3
6.1.3.1
6.1.3.2
6.1.3.3
6.1.3.4
6.2
6.2.1
6.2.2
6.2.2.1
6.2.2.2
6.2.2.3
6.2.3
6.2.3.1
6.2.3.2
6.2.3.3
6.2.4
6.2.5
6.2.6
6.3
6.3.1
6.3.2
6.3.3
6.3.5
6.3.6
6.3.7
6.3.8
261
261
261
262
263
263
264
265
Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Simulations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Simulation Results on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Simulations as a Slideshow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating Cell Values With Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replaying Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Duplicating Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
265
266
270
271
272
273
273
274
7.1
7.2
7.2.1
7.2.1.1
7.2.1.2
7.2.1.3
7.2.1.4
7.2.1.5
7.2.1.6
7.2.2
7.2.3
7.2.4
7.2.5
7.2.6
7.2.6.1
7.2.6.2
7.2.6.3
7.2.6.4
7.2.6.5
7.2.6.6
7.2.7
7.2.7.1
7.2.7.2
7.2.7.3
7.2.7.4
7.2.7.5
7.2.8
7.2.8.1
7.2.8.2
7.2.8.3
7.2.8.4
7.2.8.5
7.2.8.6
7.2.9
7.2.9.1
7.2.9.2
7.2.9.3
7.2.10
7.2.10.1
7.2.10.2
7.2.10.3
278
279
279
289
291
292
294
295
297
297
298
298
298
299
299
299
300
300
302
302
303
303
303
304
305
305
306
307
314
315
316
320
322
323
323
323
324
324
324
325
7.3
7.3.1
7.3.2
7.3.3
7.3.3.1
325
326
326
327
327
10
AT332_UMR_E0
7.3.3.2
7.3.3.3
7.3.3.4
7.3.4
7.3.4.1
7.3.4.2
7.3.5
7.3.5.1
7.3.5.2
7.4
7.4.1
7.4.1.1
7.4.1.2
7.4.1.3
7.4.2
7.4.2.1
7.4.2.2
7.4.2.3
7.4.2.4
7.4.3
7.4.3.1
7.4.3.2
7.4.3.3
7.4.3.4
7.4.3.5
7.4.4
7.4.4.1
7.4.4.2
7.4.4.3
7.4.4.4
7.4.4.5
7.4.4.6
7.4.4.7
7.5
7.5.1
7.5.2
7.5.2.1
7.5.2.2
7.5.2.3
7.5.2.4
7.5.2.5
7.5.3
7.5.3.1
7.5.3.2
7.5.3.3
7.5.3.4
7.5.3.5
7.6
7.6.1
7.6.2
7.6.2.1
7.6.2.2
7.6.2.3
7.6.2.4
7.6.2.5
7.6.3
7.6.3.1
7.6.3.2
7.6.3.3
11
7.6.4
7.6.5
7.6.6
7.6.7
7.6.8
7.6.9
7.6.9.1
7.6.9.2
7.6.9.3
7.6.9.4
7.6.10
452
454
457
458
461
462
462
463
464
464
465
7.7
7.7.1
7.7.2
7.7.3
467
468
468
470
7.8
7.8.1
7.8.2
7.8.3
7.8.4
7.8.4.1
7.8.4.2
7.8.4.3
7.8.4.4
7.8.4.5
7.8.4.6
7.8.5
7.8.6
7.8.7
7.8.8
471
471
474
474
475
475
477
478
480
480
480
482
482
483
483
7.9
7.9.1
7.9.2
7.9.3
7.9.3.1
7.9.3.2
7.9.3.3
7.9.4
7.9.5
7.9.5.1
7.9.5.2
7.9.5.3
7.9.5.4
7.9.5.5
7.9.6
7.9.6.1
7.9.6.2
7.9.6.3
7.9.6.4
7.9.6.5
7.9.7
7.9.8
7.9.8.1
7.9.8.2
7.9.9
7.9.9.1
7.9.9.2
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting HCS Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Comparing Service Areas in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TRX Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Cell Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples of Cell Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TRX Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Codec Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening the Codec Mode Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating or Modifying Codec Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Codec Mode Adaptation Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Codec Mode Quality Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Codec Configurations in Transmitters and Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Coding Scheme Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening the Coding Schemes Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating or Modifying a Coding Scheme Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Coding Scheme Configuration in Transmitters and Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adapting Coding Scheme Thresholds for a Maximum BLER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Coding Scheme Throughput Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timeslot Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Advanced Transmitter Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Extended Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Advanced Modelling of Multi-Band Transmitters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Global Network Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Settings Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
483
484
484
488
488
488
490
491
492
492
493
493
494
495
495
495
496
497
498
498
499
499
499
500
504
504
504
12
AT332_UMR_E0
7.9.10
7.9.11
7.9.12
7.9.13
8.1
8.2
8.2.1
8.2.1.1
8.2.1.2
8.2.1.3
8.2.2
8.2.2.1
8.2.2.2
8.2.2.3
8.2.2.4
8.2.2.5
8.2.2.6
8.2.2.7
8.2.2.8
8.2.2.9
8.2.2.10
8.2.3
8.2.4
8.2.5
8.2.6
8.2.7
8.2.8
8.2.8.1
8.2.8.2
8.2.8.3
8.2.8.4
8.2.8.5
8.2.8.6
8.2.9
8.2.9.1
8.2.9.2
8.2.9.3
8.2.9.4
8.2.9.5
8.2.10
8.2.10.1
8.2.10.2
8.2.10.3
8.2.10.4
8.2.10.5
8.2.10.6
8.2.10.7
8.2.10.8
8.2.11
8.2.11.1
8.2.11.2
8.2.11.3
8.2.12
8.2.12.1
8.2.12.2
8.2.12.3
8.2.12.4
8.2.12.5
8.2.12.6
13
8.3
8.3.1
8.3.2
8.3.2.1
8.3.2.2
8.3.3
8.3.3.1
8.3.3.2
571
571
571
572
578
587
587
588
8.4
8.4.1
8.4.2
8.4.3
589
589
590
592
8.5
8.5.1
8.5.2
8.5.3
8.5.4
8.5.4.1
8.5.4.2
8.5.4.3
8.5.4.4
8.5.4.5
8.5.4.6
8.5.5
8.5.6
8.5.7
593
593
596
596
597
597
598
599
600
600
600
602
602
603
8.6
8.6.1
8.6.2
8.6.2.1
8.6.2.2
8.6.3
8.6.4
8.6.4.1
8.6.4.2
8.6.4.3
8.6.5
8.6.5.1
8.6.5.2
8.6.6
603
603
605
605
606
609
609
609
610
610
610
611
611
611
8.7
8.7.1
8.7.2
8.7.3
8.7.3.1
8.7.3.2
8.7.4
8.7.5
8.7.5.1
8.7.5.2
8.7.5.3
8.7.6
8.7.6.1
8.7.6.2
8.7.6.3
8.7.7
8.7.7.1
8.7.7.2
8.7.7.3
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modelling Inter-Carrier Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Frequency Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Settings Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Network Deployment Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining R99 Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining HSDPA Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining HSUPA Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining 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 . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Receiver Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating or Modifying Reception Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HSDPA UE Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HSUPA UE Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
611
612
612
613
613
614
614
615
615
615
616
616
616
617
618
618
618
620
620
14
AT332_UMR_E0
8.7.8
8.7.9
8.7.10
8.7.11
8.7.12
9.1
9.1.1
9.1.1.1
9.1.1.2
9.1.1.3
9.1.1.4
9.1.1.5
9.1.1.6
9.1.2
9.1.3
9.1.4
9.1.5
9.1.6
9.1.6.1
9.1.6.2
9.1.6.3
9.1.6.4
9.1.6.5
9.1.6.6
9.1.7
9.1.7.1
9.1.7.2
9.1.7.3
9.1.7.4
9.1.7.5
9.1.8
9.1.8.1
9.1.8.2
9.1.8.3
9.1.8.4
9.1.8.5
9.1.8.6
9.1.9
9.1.9.1
9.1.9.2
9.1.9.3
9.1.10
9.1.10.1
9.1.10.2
9.1.10.3
9.1.10.4
9.2
9.2.1
9.2.2
9.2.2.1
9.2.2.2
9.2.3
9.2.3.1
9.2.3.2
15
9.3
9.3.1
9.3.2
9.3.3
698
698
699
700
9.4
9.4.1
9.4.2
9.4.3
9.4.4
9.4.4.1
9.4.4.2
9.4.4.3
9.4.4.4
9.4.4.5
9.4.4.6
9.4.4.7
9.4.5
9.4.6
9.4.7
701
702
704
704
705
705
707
708
709
710
710
710
712
712
713
9.5
9.5.1
9.5.2
9.5.2.1
9.5.2.2
9.5.3
9.5.4
9.5.4.1
9.5.4.2
9.5.4.3
9.5.5
9.5.5.1
9.5.5.2
9.5.6
713
714
715
715
716
718
719
719
720
721
721
721
722
722
9.6
9.6.1
9.6.2
9.6.3
9.6.4
9.6.4.1
9.6.4.2
9.6.5
9.6.6
9.6.6.1
9.6.6.2
9.6.7
9.6.7.1
9.6.7.2
9.6.8
9.6.8.1
9.6.8.2
9.6.9
9.6.10
9.6.10.1
9.6.11
9.6.12
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modelling Inter-carrier Interference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Frequency Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Carrier Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Global Network Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CDMA Network Settings Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Throughputs Available for Services in CDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The 1xEV-DO Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining the Forward Link 1xEV-DO Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining the Reverse Link 1xEV-DO Radio Bearers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Site Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Channel Element Consumption per CDMA Site Equipment and Radio Configuration . . . . . . . . . . . . . . . . . . .
Receiver Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Receiver Height. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating or Modifying Reception Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conditions for Entering the Active Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modelling Shadowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying the Shadowing Margins and Macro-diversity Gain per Clutter Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating PN Offset Domains and Groups for PN Offset Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modelling Inter-technology Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
722
723
723
724
724
724
725
725
726
727
727
727
727
728
728
729
729
730
730
731
732
733
10
10.1
10.2
10.2.1
10.2.1.1
10.2.1.2
10.2.1.3
16
738
738
739
745
747
AT332_UMR_E0
10.2.1.4
10.2.1.5
10.2.1.6
10.2.2
10.2.3
10.2.4
10.2.5
10.2.6
10.2.6.1
10.2.6.2
10.2.6.3
10.2.6.4
10.2.6.5
10.2.6.6
10.2.7
10.2.7.1
10.2.7.2
10.2.7.3
10.2.7.4
10.2.7.5
10.2.8
10.2.8.1
10.2.8.2
10.2.8.3
10.2.8.4
10.2.8.5
10.2.8.6
10.2.8.7
10.2.9
10.2.9.1
10.2.9.2
10.2.9.3
10.2.9.4
10.2.9.5
10.2.10
10.2.10.1
10.2.10.2
10.2.10.3
10.2.11
10.2.11.1
10.2.11.2
10.2.11.3
10.2.11.4
10.2.11.5
10.2.11.6
10.2.11.7
10.3
10.3.1
10.3.1.1
10.3.1.2
10.3.1.3
10.3.2
10.3.3
10.3.3.1
10.3.3.2
10.3.4
10.4
10.4.1
10.4.2
10.4.3
10.4.4
10.4.4.1
10.4.4.2
10.4.4.3
10.4.4.4
17
10.4.4.5
10.4.5
10.4.6
10.4.7
817
819
819
820
10.5
10.5.1
10.5.2
10.5.2.1
10.5.2.2
10.5.3
10.5.4
10.5.4.1
10.5.4.2
10.5.4.3
10.5.5
820
820
822
822
823
825
826
826
826
827
827
10.6
10.6.1
10.6.2
10.6.3
10.6.3.1
10.6.3.2
10.6.4
10.6.4.1
10.6.4.2
10.6.4.3
10.6.4.4
10.6.4.5
10.6.4.6
10.6.4.7
10.6.5
10.6.5.1
10.6.5.2
10.6.5.3
10.6.6
10.6.7
10.6.7.1
10.6.7.2
10.6.7.3
10.6.8
10.6.8.1
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modelling Inter-carrier Interference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Frequency Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Global Network Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TD-SCDMA Network Settings Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Smart Antenna Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Grid of Beams (GOB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adaptive Beam Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conventional Beamformer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optimum Beamformer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Statistical Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Third-Party Smart Antenna Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Smart Antenna Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining R99 Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining HSDPA Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining HSUPA Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Site Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Receiver Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating or Modifying Reception Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HSDPA UE Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HSUPA UE Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modelling Shadowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying the Shadowing Margins per Clutter Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
827
827
828
828
829
830
831
831
833
833
833
834
834
834
835
835
836
836
837
837
837
838
838
839
839
11
11.1
11.2
11.2.1
11.2.1.1
11.2.1.2
11.2.1.3
11.2.2
11.2.2.1
11.2.2.2
11.2.2.3
11.2.2.4
11.2.2.5
11.2.2.6
11.2.2.7
11.2.2.8
11.2.2.9
11.2.2.10
18
844
845
845
846
848
853
853
854
854
854
855
855
855
856
858
859
AT332_UMR_E0
11.2.3
11.2.4
11.2.5
11.2.6
11.2.7
11.2.7.1
11.2.7.2
11.2.7.3
11.2.7.4
11.2.7.5
11.2.7.6
11.2.8
11.2.8.1
11.2.8.2
11.2.8.3
11.2.8.4
11.2.8.5
11.2.8.6
11.2.9
11.2.9.1
11.2.9.2
11.2.9.3
11.2.9.4
11.2.9.5
11.2.10
11.2.10.1
11.2.10.2
11.2.11
11.2.11.1
11.2.11.2
11.2.11.3
11.2.11.4
11.2.11.5
11.2.11.6
11.2.12
11.2.12.1
11.2.12.2
11.2.12.3
11.3
11.3.1
11.3.1.1
11.3.1.2
11.3.2
11.3.3
11.3.3.1
11.3.3.2
11.3.4
11.3.5
11.3.5.1
11.3.5.2
11.3.6
11.3.7
11.3.7.1
11.3.7.2
11.3.8
11.3.8.1
11.3.8.2
11.3.8.3
11.3.9
11.3.9.1
11.3.9.2
11.3.9.3
11.3.9.4
11.3.9.5
19
11.4
11.4.1
11.4.2
11.4.2.1
11.4.2.2
11.4.3
924
925
925
926
928
936
11.5
11.5.1
11.5.2
11.5.3
11.5.4
936
937
937
939
941
11.6
11.6.1
11.6.2
11.6.3
11.6.4
11.6.4.1
11.6.4.2
11.6.4.3
11.6.4.4
11.6.4.5
11.6.4.6
11.6.5
11.6.6
11.6.7
942
942
944
945
945
945
946
947
947
948
948
950
950
950
11.7
11.7.1
11.7.1.1
11.7.2
11.7.2.1
11.7.2.2
11.7.3
11.7.4
11.7.4.1
11.7.4.2
11.7.4.3
11.7.5
11.7.5.1
11.7.5.2
11.7.6
950
951
951
952
953
953
955
956
956
956
956
957
957
957
958
11.8
11.8.1
11.8.2
11.8.2.1
11.8.3
11.8.4
11.8.5
11.8.6
11.8.7
11.8.8
11.8.9
11.8.10
11.8.11
11.8.11.1
11.8.11.2
11.8.11.3
11.8.11.4
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Frequency Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Global Network Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Network Deployment Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Frame Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining LTE Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining LTE Quality Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining LTE Reception Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining LTE Schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining LTE UE Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Smart Antenna Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple Input Multiple Output Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transmit and Receive Diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single-User MIMO or Spatial Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adaptive MIMO Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-User MIMO or Collaborative MIMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
958
958
959
962
962
963
964
964
965
968
970
970
972
972
972
973
973
20
AT332_UMR_E0
11.8.12
11.8.13
11.8.14
11.9
11.9.1
11.9.2
11.9.3
11.9.4
11.9.5
11.9.6
11.9.7
11.9.8
11.9.9
11.9.10
11.10
12
12.1
12.2
12.2.1
12.2.2
12.2.3
12.2.4
12.2.5
12.2.6
12.2.7
12.2.7.1
12.2.7.2
12.2.7.3
12.2.7.4
12.2.7.5
12.2.7.6
12.2.8
12.2.8.1
12.2.8.2
12.2.8.3
12.2.9
12.2.9.1
12.2.9.2
12.2.9.3
12.3
12.3.1
12.3.2
12.3.3
12.4
12.5
13
13.1
13.2
13.2.1
13.2.2
13.2.3
13.2.4
13.2.5
13.2.6
13.2.7
13.2.7.1
13.2.7.2
13.2.7.3
21
13.2.7.4
13.2.7.5
13.2.7.6
13.2.8
13.2.8.1
13.2.8.2
13.2.8.3
13.2.9
13.2.9.1
13.2.9.2
1023
1024
1028
1028
1028
1028
1028
1028
1029
1029
13.3
13.3.1
13.3.2
13.3.3
1029
1029
1029
1030
13.4
13.5
14
14.1
14.2
14.2.1
14.2.1.1
14.2.1.2
14.2.1.3
14.2.2
14.2.2.1
14.2.2.2
14.2.2.3
14.2.2.4
14.2.2.5
14.2.2.6
14.2.2.7
14.2.2.8
14.2.2.9
14.2.2.10
14.2.3
14.2.4
14.2.5
14.2.6
14.2.7
14.2.7.1
14.2.7.2
14.2.7.3
14.2.7.4
14.2.7.5
14.2.7.6
14.2.7.7
14.2.8
14.2.8.1
14.2.8.2
14.2.8.3
14.2.8.4
14.2.8.5
14.2.8.6
14.2.9
14.2.9.1
14.2.9.2
14.2.9.3
14.2.9.4
14.2.9.5
14.2.9.6
14.2.9.7
22
1036
1037
1037
1037
1039
1042
1042
1043
1043
1043
1044
1044
1044
1045
1047
1048
1049
1050
1050
1050
1051
1051
1053
1053
1053
1054
1054
1054
1055
1055
1056
1057
1057
1057
1058
1058
1058
1059
1062
1070
1071
1075
1079
AT332_UMR_E0
14.2.10
14.2.10.1
14.2.10.2
14.2.10.3
14.3
14.3.1
14.3.1.1
14.3.1.2
14.3.2
14.3.3
14.3.4
14.3.5
14.3.5.1
14.3.5.2
14.3.6
14.3.7
14.3.8
14.3.8.1
14.3.8.2
14.3.8.3
14.3.9
14.3.9.1
14.3.9.2
14.3.9.3
14.3.9.4
14.3.9.5
14.4
14.4.1
14.4.2
14.4.2.1
14.4.2.2
14.4.3
14.5
14.5.1
14.5.2
14.5.3
14.6
14.6.1
14.6.2
14.6.3
14.6.4
14.6.4.1
14.6.4.2
14.6.4.3
14.6.4.4
14.6.4.5
14.6.4.6
14.6.5
14.6.6
14.6.7
14.7
14.7.1
14.7.2
14.7.2.1
14.7.2.2
14.7.3
14.7.4
14.7.4.1
14.7.4.2
14.7.4.3
14.7.5
14.7.5.1
14.7.5.2
23
14.7.6
14.8
14.8.1
14.8.2
14.8.2.1
14.8.2.2
14.8.3
14.8.4
14.8.5
14.8.6
14.8.7
14.8.8
14.8.9
14.8.9.1
14.8.9.2
14.8.9.3
14.8.10
14.8.10.1
14.8.10.2
14.8.10.3
14.8.10.4
14.8.11
14.8.12
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Frequency Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Settings Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Network Deployment Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Frame Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining WiMAX Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining WiMAX Quality Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining WiMAX Reception Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining WiMAX Schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Smart Antenna Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optimum Beamformer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conventional Beamformer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Smart Antenna Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple Input Multiple Output (MIMO) Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Space-Time Transmit Diversity and Maximum Ratio Combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single-User MIMO or Spatial Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adaptive MIMO Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-User MIMO or Collaborative MIMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modelling Shadowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modelling Inter-technology Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1133
1134
1134
1134
1136
1137
1138
1139
1139
1140
1143
1145
1146
1146
1147
1148
1148
1148
1149
1149
1150
1150
14.9
14.9.1
14.9.2
14.9.3
14.9.4
14.9.5
14.9.6
14.9.7
14.9.8
14.9.9
14.9.10
1152
1152
1153
1153
1153
1153
1154
1154
1158
1159
1160
14.10
15
15.1
15.2
15.2.1
15.2.1.1
15.2.1.2
15.2.1.3
15.2.2
15.2.2.1
15.2.2.2
15.2.2.3
15.2.2.4
15.2.2.5
15.2.2.6
15.2.2.7
15.2.2.8
15.2.2.9
15.2.3
15.2.4
15.2.5
15.2.6
15.2.7
15.2.7.1
15.2.7.2
15.2.7.3
15.2.7.4
15.2.7.5
24
1166
1166
1166
1167
1168
1170
1170
1170
1171
1171
1171
1172
1172
1174
1175
1176
1177
1177
1177
1178
1178
1179
1182
1189
1190
AT332_UMR_E0
15.2.7.6
15.2.7.7
15.2.8
15.2.8.1
15.2.8.2
15.2.8.3
15.3
15.3.1
15.3.1.1
15.3.1.2
15.3.2
15.3.3
15.3.4
15.3.5
15.3.5.1
15.3.5.2
15.3.6
15.3.6.1
15.3.6.2
15.3.6.3
15.3.7
15.3.7.1
15.3.7.2
15.4
15.4.1
15.4.2
15.4.2.1
15.4.2.2
15.4.3
15.5
15.5.1
15.5.2
15.5.3
15.6
15.6.1
15.6.2
15.6.3
15.6.4
15.6.4.1
15.6.4.2
15.6.4.3
15.6.4.4
15.6.4.5
15.6.4.6
15.6.5
15.6.6
15.6.7
15.7
15.7.1
15.7.2
15.7.3
15.7.3.1
15.7.3.2
15.7.4
15.7.4.1
15.7.4.2
15.7.4.3
15.7.5
15.7.5.1
15.7.5.2
25
15.7.6
15.8
15.8.1
15.8.2
15.8.2.1
15.8.2.2
15.8.3
15.8.4
15.8.5
15.8.6
15.8.7
15.8.7.1
15.8.7.2
15.8.7.3
15.8.7.4
15.8.8
15.8.9
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Frequency Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Settings Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Frame Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Wi-Fi Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Wi-Fi Quality Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Wi-Fi Reception Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple Input Multiple Output (MIMO) Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Space-Time Transmit Diversity and Maximum Ratio Combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single-User MIMO or Spatial Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adaptive MIMO Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-User MIMO or Collaborative MIMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modelling Shadowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modelling Inter-technology Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1235
1235
1236
1236
1236
1237
1237
1238
1238
1240
1240
1240
1241
1241
1241
1242
15.9
15.9.1
15.9.2
15.9.3
1243
1244
1244
1244
16
16.1
16.2
16.2.1
16.2.1.1
16.2.1.2
16.2.1.3
16.2.2
16.2.2.1
16.2.2.2
16.2.2.3
16.2.2.4
16.2.2.5
16.2.2.6
16.2.2.7
16.2.2.8
16.2.2.9
16.2.2.10
16.2.3
16.2.4
16.2.5
16.2.6
16.2.6.1
16.2.6.2
16.2.6.3
16.2.6.4
16.2.6.5
16.2.6.6
16.2.7
16.2.7.1
16.2.7.2
16.2.7.3
16.2.7.4
16.2.7.5
16.2.7.6
16.2.7.7
16.2.8
16.2.8.1
16.2.8.2
16.2.8.3
26
1247
1248
1248
1248
1250
1251
1251
1251
1252
1252
1253
1253
1253
1253
1256
1256
1258
1258
1259
1259
1259
1261
1262
1262
1262
1263
1263
1263
1265
1267
1274
1275
1277
1280
1283
1283
1283
1284
AT332_UMR_E0
16.3
16.3.1
16.3.2
16.3.3
16.4
16.4.1
16.4.2
16.4.3
16.4.4
16.4.4.1
16.4.4.2
16.4.4.3
16.4.4.4
16.4.4.5
16.4.4.6
16.4.5
16.4.6
16.4.7
16.5
16.5.1
16.5.2
16.5.2.1
16.5.2.2
16.5.3
16.5.3.1
16.5.3.2
16.5.3.3
16.5.4
16.5.4.1
16.5.4.2
16.5.5
16.6
16.6.1
16.6.2
16.6.3
16.6.3.1
16.6.3.2
16.6.4
16.6.5
16.6.6
16.6.7
16.6.7.1
16.6.7.2
16.6.7.3
16.6.7.4
16.6.8
16.6.9
16.6.10
17
17.1
17.1.1
17.1.2
17.1.2.1
17.1.2.2
17.1.2.3
17.1.3
17.1.4
17.1.5
17.1.5.1
17.1.5.2
27
17.1.6
17.2
17.2.1
17.2.2
17.2.3
1316
1316
1316
1318
17.3
17.3.1
17.3.1.1
17.3.1.2
17.3.1.3
17.3.2
17.3.2.1
17.3.2.2
17.3.2.3
17.3.2.4
17.3.2.5
17.3.2.6
1319
1319
1319
1319
1319
1320
1320
1329
1338
1348
1355
1359
17.4
17.5
17.6
17.6.1
17.6.1.1
17.6.1.2
17.6.1.3
17.6.1.4
17.6.1.5
17.6.1.6
17.6.1.7
17.6.1.8
17.6.2
17.6.3
17.6.3.1
17.6.3.2
17.6.3.3
17.6.3.4
17.6.3.5
17.6.3.6
17.6.3.7
17.6.4
1362
1362
1362
1363
1364
1366
1367
1367
1368
1370
1370
1371
1373
1373
1374
1378
1378
1379
1380
1381
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1383
28
AT332_UMR_E0
About Atoll
Atoll is a 64-bit multi-technology wireless network design and optimisation platform. Atoll is open, scalable, flexible, and
supports wireless operators throughout the network life cycle, from initial design to densification and optimisation.
Atoll includes integrated single RAN multiple RAT network design capabilities for both 3GPP (GSM/UMTS/LTE) and 3GPP2
(CDMA/LTE) technology streams. It provides operators and vendors with a powerful native 64-bit framework for designing
and optimising current and future integrated multi-technology networks. Atoll supports multi-technology HetNets, small cell
planning, and Wi-Fi offloading.
Atolls integration and automation features help operators smoothly automate planning and optimisation processes through
flexible scripting and SOA-based mechanisms. Atoll supports a wide range of implementation scenarios, from standalone to
enterprise-wide server-based configurations.
If you are interested in learning more about Atoll, please contact your Forsk representative to inquire about our training solutions.
About Forsk
Forsk is an independent company providing radio planning and optimisation software solutions to the wireless industry since
1987.
In 1997, Forsk released the first version of Atoll, its flagship radio planning software. Since then, Atoll has evolved to become
a comprehensive radio planning and optimisation platform and, with more than 7000 installed licenses worldwide, has
reached the leading position on the global market. Atoll combines engineering and automation functions that enable operators to smoothly and gradually implement SON processes within their organisation.
Today, Forsk is a global supplier with over 450 customers in 120 countries and strategic partnerships with major players in the
industry. Forsk distributes and supports Atoll directly from offices and technical support centres in France, USA, and China as
well as through a worldwide network of distributors and partners.
Since the first release of Atoll, Forsk has been known for its capability to deliver tailored and turn-key radio planning and optimisation environments based on Atoll.
To help operators streamline their radio planning and optimisation processes, Forsk provides a complete range of implementation services, including integration with existing IT infrastructure, automation, as well as data migration, installation, and
training services.
Getting Help
The online help system that is installed with Atoll is designed to give you quick access to the information you need to use the
product effectively. It contains the same material as the Atoll 3.3.2 User Manual.
You can browse the online help from the Contents view, the Index view, or you can use the built-in Search feature.
You can also download manuals from the Forsk web site at:
http://www.forsk.com/MyForskAccount/
If you want to print a single topic, select Print the selected topic.
If you want to print an entire section, including all topics and sections in that section, select Print the selected
heading and all subtopics.
29
5. Click OK.
To read PDF manuals, download Adobe Reader from the Adobe web site at:
http://get.adobe.com/reader/
Hardcopy manuals are also available. For more information, contact to your Forsk representative.
Forsk US
For North and Central America, contact the Forsk US support team:
Forsk China
For China, contact the Forsk China support team:
Opening Hours: Monday to Friday 9.00am to 5.30pm (GMT+08:00) Beijing, Chongqing, Hong Kong, Urumqi.
30
Chapter 1
Working Environment
This chapter presents the Atoll working environment and
explains the tools and shortcuts available.
"Documents" on page 33
"Objects" on page 49
"Maps" on page 59
32
AT332_UMR_E0
1 Working Environment
The Atoll working environment provides a wide set of tools to create and design radio-planning projects in a single application
and to create and export results based on your projects.
In Atoll, radio-planning projects are modelled and managed through Atoll documents (files with the .ATL extension).
The Atoll working environment is flexible and supports standard Windows capabilities (such as simultaneous opening of
several windows, moving windows or objects by dragging and dropping them, commands accessible through context menus,
standard shortcuts).
Data and objects contained in an Atoll document are accessible from different ways:
Explorers: The explorers contain most of the objects in a document arranged in folders. Using the explorers, you can
manage all objects in the Atoll document: sites, transmitters, calculations, 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.
Maps: 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.
Data tables: The content of the folders in the explorers 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 enter
large amounts of information into a table by importing data or by cutting and pasting the information from any Windows spreadsheet into the table.
This chapter provides an overview of the Atoll working environment and covers the following topics:
"Documents" on page 33
"Atoll Work Area" on page 45
"Objects" on page 49
"Maps" on page 59
"Data Tables" on page 75
"Printing in Atoll" on page 90
"Grouping, Sorting, and Filtering Data" on page 94
"Toolbars and Shortcuts" on page 109.
1.1 Documents
In Atoll, radio-planning projects are modelled and managed through Atoll documents (files with the .ATL extension).
Each Atoll document can contain multiple technologies and assembles the following necessary information:
Radio equipment such as sites, transmitters, antennas, repeaters, and other equipment. For more information on
radio equipment, see the technology-specific chapters.
Radio data such as frequency bands, technology-specific parameters, coordinate systems. For more information on
radio data, see the technology-specific chapters.
Geographic data such as clutter classes, clutter heights, Digital Terrain Model (DTM), population maps. For more information on geographic data, see Chapter 2: Geographic Data.
In a single-user environment, Atoll documents are standalone documents. Atoll is delivered with document templates
that contain the data and folder structure necessary for the technologies you are using. You can also create your own
templates by opening an existing template, changing it to fit your own requirements, and then saving it as a new template.
In a multi-user environment, documents are connected to a database and can be created from an existing database.
When you create an Atoll document from a database, the database you connect to has been created with the technologies and data you need. Working with a database allows several users to share the same data while at the same
time managing data consistency.
33
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 must configure the basic parameters
of the Atoll document.
This section covers the following topics:
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
throughputs. 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 (1x 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.
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 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.
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.
Wi-Fi: Atoll Wi-Fi enables modelling of IEEE 802.11 wireless local area networks (WLAN) and to study mobile traffic
offloading to Wi-Fi networks.
LPWA: Atoll LPWA (Low Power Wide Area) can be used to design and optimise wireless internet of things (IoT) networks.
3GPP Multi-RAT: This template can be used to model 2G/3G/4G multi-technology projects. When starting a new 3GPP
multi-RAT project, Atoll allows you to model any GSM/UMTS/LTE technology combination in the same project.
The 3GPP multi-RAT template can also be used to create a GSM, UMTS, or LTE single-RAT
document. By using the 3GPP multi-RAT template to create a single-RAT document, you
make it possible to add other 3GPP technologies to the document at a later time.
34
3GPP2 Multi-RAT: This template can be used to model 3G/4G multi-technology projects. When starting a new 3GPP2
multi-RAT project, Atoll allows you to model the CDMA2000/LTE technology combination in the same project.
AT332_UMR_E0
The 3GPP2 multi-RAT template can also be used to create a CDMA2000 or LTE single-RAT
document. By using the 3GPP2 multi-RAT template to create a single-RAT document, you
make it possible to add the other 3GPP2 technology to the document at a later time.
Microsoft Access
Microsoft SQL Server
Oracle
Microsoft Data Link files
The exact procedure of connecting with the database differs from one database to another.
When you create an 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 in a multi-user environment, there are issues related to sharing data that do not arise when you are working
on a standalone 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.
This section covers the following topics:
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 is 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 is 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,
35
editing edit clutter or traffic in their respective projects, usually store these modifications locally, since these modifications rarely have an impact on other users.
Path loss matrices: Shared path loss matrices are calculated in the central Atoll project by the administrator. Users
can read these path loss data but cannot modify them. When the shared path loss data becomes invalid in a usersr
Atoll document, the new path loss matrices are calculated and stored locally, either embedded in the ATL file or
linked to an external file. The shared path loss data is not modified.
Shared path loss matrices are updated when the calculation administrator performs an update, taking into account the modifications made by other users that have been updated in the central database.
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.
36
AT332_UMR_E0
You can configure Atoll to always use a defined database type (MS Access, SQL
Server, or Oracle) by setting an option in the Atoll.ini file. In this case, the Open
from a Database dialog box is replaced by the database-specific authentication
dialog box. For more information, see the Administrator Manual.
Additional dialog boxes might 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 dialog box is displayed allowing you to select the data to load into the new Atoll document.
4. Select the Project, Site List, Custom Fields Groups, and Neighbours to be loaded from the database to create the document and click OK. If you load the intra-technology or the inter-technology neighbour list, the associated exceptional
pairs table is also loaded.
The new document opens with data loaded from the database.
If the north-west point of the project is by default the axis origin, the new document
opens with no site displayed in the map window. You can centre the document on the
data displayed in the Network explorer by expanding the Sites folder, right-clicking any
site, and selecting Centre in Map Window from the context menu (see "Centring the
Map Window on a Selection" on page 62).
If the document is connected to a database, the Database Connection dialog box appears.
If the document is a standalone document, a message is displayed to inform you that the document is not connected to a database. A document created from a template is not connected to any 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 dialog box
appears. For information, see "Archiving the Modifications in the Database" on
page 38.
37
3. Under Take into account, you can select the neighbour lists, Intra-technology Neighbours and Inter-technology
Neighbours, to refresh.
4. To create a report for the refresh process, select Generate Report under Modifications Since the Last Refresh.
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.
1.1.2.5.1
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 38.
4. Click Close when you are finished archiving.
1.1.2.5.2
38
AT332_UMR_E0
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 dialog box
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 dialog box, 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 dialog box appears, with the fields in conflict highlighted (see Figure 1.3). In the Conflict
in Changes dialog box, 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.
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 38.
Atoll displays a message explaining that the record you are trying to update has been deleted from the database
(see Figure 1.4). Select one of the following:
39
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.
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.
40
AT332_UMR_E0
shown appropriately at the expense of the other characteristics, or he must compromise on several characteristics1. The
projected zones are referenced using cartographic coordinates (metre, 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.
All imported raster geographic files must be use the same cartographic system. If not, you
must convert them to a single cartographic system.
5. Click OK. The selected coordinate system appears in the Projection field and, by default, in the Display field as well.
6. 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
tems (
) are available.
265629.9N
26d56m29.9sN
26.93914N
+26.93914
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.
41
Radio:
Radiated power: Select either "EIRP" (Effective Isotropically Radiated Power) or "ERP" ()
Antenna gain: Select either "dBi" (decibel (isotropic)) or "dBd" (decibel (dipole))
Transmission: Select either "dBm" (decibel (milliWatt)), "W" (Watt), or "kW" (kiloWatt)
Reception: Select either "dBm" (decibel (milliWatt)), "dBV" (decibel (microvolt)), "dBV/M" (decibel (microvolt per metre)), or "V/M" (volts per metre)
Geo:
Climate:
3. Click OK.
42
Title: You can set a descriptive name for the project that is different from the file name of the Atoll project file.
Date: You can enter a timestamp for the project and then click the Lock button to prevent it from being changed.
By default Atoll enters the current time as the timestamp. Each time you access the Project tab, Atoll will update
the timestamp.
Owner: You can enter the name of the person responsible for the project, and then click the Lock button to prevent it from being changed. By default Atoll enters the name you used to log on to the computer.
Status: You can enter a description of the project status.
Logo: You define a logo for the project by clicking the Browse button and browsing to a graphic file that can be
used as a logo for the project. The logo will be used in reports exported in RTF format
Comments: You can enter any comments in the Comments field.
AT332_UMR_E0
3. Click OK.
To link the copy of your Atoll document with the externalised calculation results files of the original document,
select Link with the externalised results of the original document.
To create copies of the externalised calculation results with the new document, select Make a copy of the externalised results.
To create a copy of your document without linking the externalised calculation results files of the original document, select Ignore the externalised results.
You can set an option in the [Settings] section of the Atoll.ini file to link, copy, or ignore
the externalised calculation results files and to hide the Externalised results dialog box
when saving a copy of a document.
3. Click OK in the Externalised results dialog box. The Save As dialog box is displayed.
4. Select the folder where the copy is to be stored, enter a File name, and click Save.
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 linked geographic data files.
To create an archive containing the ATL file and all linked geographic data files:
1. In the File menu, select Save to Zip. The Save As dialog box appears.
2. Select the folder where the created archive is to be stored, enter a File name for the archive to be created, select "Zip
Files (*.zip)" from the Save as type list, and click Save.
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, and so on).
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.
43
A "Geo" folder with all the linked geographic data available in the Geo explorer for the Atoll document.
This folder contains subfolders with the same names as the folders in the Geo explorer. Geographic data that are
found outside folders in the Geo explorer are stored in files under the Geo folder, and data present within folders
in the Geo explorer 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. In the File menu, select Open from Zip. The Open dialog box appears.
2. Select the ZIP file that contains the ATL file and linked geographic data files and click Open. The Browse For Folder
dialog box appears.
3. Select the folder where you want to extract the contents of the ZIP file.
4. 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 when working with archived ATL files.
The highest compression level is used when creating the archive.
44
AT332_UMR_E0
tions, 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.
You can easily recover your backup document and open it in Atoll just like any other Atoll
document. If the original document is named "filename.atl," the backup document is
stored in the same folder and is named "filename.atl.bak".
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.
A menu bar and several toolbars that give access to Atoll functions. For more information, see "Using Toolbars" on
page 109.
A document window that arranges by tab all the open Atoll documents, maps, data tables, and reports.
Explorers that arranges by folder data and objects contained in an Atoll document, such as network data, geographic
data, propagation models, and network settings.
Tool windows that are windows providing information or data and that can be docked or floating such as events
viewer, legend window, and panoramic window.
45
1.2.2 Explorers
Explorers play a central role in Atoll by grouping the data and objects contained in an Atoll document:
The Network explorer contains data related to sites, transmitters, predictions, simulations, interference matrices,
drive test data, and links.
The Site explorer allows you to view the elements located on the site that is currently selected in the Network explorer
or in the map. The transmitters and links of the selected site are displayed in technology-specific folders.
The Geo explorer allows you to manage the geographic data such as traffic maps, population, clutter heights, clutter
classes, Digital Terrain Model (DTM), and online maps.
The Parameters explorer allows you to manage propagation models, traffic parameters, radio network and microwave settings and equipment.
Each explorer contains objects and folders containing objects. The name of each folder containing at least one object is
preceded by an Expand button ( ) or a Collapse button ( ).
46
AT332_UMR_E0
You can expand or collapse all the folders in the explorer by pressing SHIFT while you click
on an expand or collapse button.
You can expand or collapse all folders that are selected as visible by pressing CTRL while
you click on an expand or collapse button.
In the Site explorer, you can expand or collapse all folders at a specific level by clicking the
arrow icons (
) in the title bar.
You can refresh the display of the Network explorer by clicking Refresh (
Each object and folder in the explorers 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.
The content of the folders in the explorers can be displayed in tables, allowing you to manage large amount of data. For information on working with tables, see "Data Tables" on page 75.
By default, explorers are displayed when launching Atoll. If the explorers are hidden you can display them by using the View
menu.
Events viewer: Atoll displays information about the current document in the Events viewer. The Events viewer displays information ( ), warning ( ), and error ( ) messages, as well as the progress of calculations. You can save
the information displayed in the Events viewer to a log file by selecting one or more events, right-clicking the selection,
and selecting Save As from the context menu. You can also automatically generate log files for each Atoll session and
select the level of information displayed in the Events viewer. For more information about these settings, see the
Administrator Manual.
Legend window: The Legend window contains information on the objects displayed on the map.
Panoramic window: The Panoramic window displays the entire map with all 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:
For more information, see "Using the Panoramic Window" on page 61.
Find on Map window: The Find on Map window allows you to find object on the map. For more information, see
"Searching for Objects on the Map" on page 63.
Favourite View window: The Favourite Views window allows you to navigate between different predefined views
saved as favourite views. For more information, see "Favourite Map Views" on page 62.
47
New Horizontal Tab Group: A new horizontal tab group is created and the selected document window is
added.
New Vertical Tab Group: A new vertical tab group and the selected document window is added.
You can also add a document window to a new tab group by clicking its title and then selecting New Horizontal Tab
Group or New Vertical Tab Group from the Window menu.
If you drag the window icon to the lower edge or right edge of an existing tab group, even
if there is only one tab group, an outline appears to indicate the tab group the window will
automatically be added to when you release the mouse.
3. Release the mouse. The explorer or toll window docks in its new position.
48
AT332_UMR_E0
When auto-hide is activated on an explorer window, all the other explorers are reduced
to vertical tabs at the edge of the work area.
You can display the hidden explorer or tool window by resting the pointer over the name of the explorer or the tool
window.
2. In the title bar of the explorer or tool window, click Auto Hide (
their former positions.
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
1.3 Objects
In Atoll, the items found in the Network explorer or the Geo explorer 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.
This section covers the following topics:
49
50
AT332_UMR_E0
3. To hide all the objects of an entire folder, clear the check box corresponding to the folder name in the Network or Geo
explorer.
4. To display an hidden object, select the check box corresponding to the object name in the Network or Geo explorer.
).
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 dialog box.
51
4. Click OK.
Unique: defines the same symbol for all objects of this type. By defining a unique symbol for an object type, objects
of different types, such as sites or transmitters, are immediately identifiable.
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 transmitters by antenna types, or to distinguish inactive sites from active ones.
Atoll applies colours automatically on 36-colour cycles. As opposed to shading, this is
particularly useful to distinguish neighbouring zones which have very close colour values.
You can configure Atoll to loop on as many user-defined colours as you want and you can
override user-defined colours, if any, and force shading (from red to blue) by setting
options in the Atoll.ini file. For more information, see the Administrator Manual.
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, and the altitude of sites.
Automatic: only available for transmitters; a colour is automatically assigned to each transmitter, ensuring that each
transmitter has a different colour than the transmitters surrounding it.
52
Properties: The Display Parameters dialog box opens, which enables you to define the appearance of the selected
symbol in the table.
Refresh: Select this option to refresh the table.
Select all: All the values in the table are selected.
Insert before: When "Value Intervals" is the selected display type, a new threshold is inserted in the table before
the threshold selected in the table.
Insert after: When "Value Intervals" is the selected display type, a new threshold is inserted in the table after the
threshold selected in the table.
Delete: The selected value is removed from the table.
Shading: The Shading dialog box appears.
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 configuration in a file.
AT332_UMR_E0
6. Click OK.
When you create a map object, for example, a site or a transmitter, you must click
the Refresh button (
) to assign a colour to the newly created object according
to the display type.
You can define the default symbol used for sites and how it is displayed by setting
an option in the Atoll.ini file. For more information, see the Administrator Manual.
53
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.
To remove a field from the Selected Fields list, select the field and click
To change the order of a field in the list, select the field and click
or
.
to move it up or down.
4. Click OK to close the Field Selection dialog box then OK to close the Properties dialog box. The objects will be grouped
in the order of the fields in the Selected Fields list, from top to bottom.
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 "Associating
a Tip Text to an Object" on page 54.
b. To remove a field from the Selected Fields list, select the field in the Selected Fields list and click
it.
to remove
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 keeping object-related information permanently visible. For more information on tip text, see "Associating a Label to
an Object" on page 53.
4. Click OK.
Once you have defined the tip text, you must activate the tip text function before it appears by clicking Display Tips (
text are displayed when the pointer is over the object.
). Tip
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.
The entries in the Legend column will appear in the Legend window.
54
AT332_UMR_E0
55
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 Network explorer. The context menu appears.
2. Select Properties from the context menu. The Properties dialog box appears.
3. Select the Display tab.
4. Select "Automatic" as the Display Type.
5. Click OK.
6. Click the Refresh button (
To change how the results of a signal level coverage prediction are displayed:
1. Expand the Predictions folder in the Network explorer and right-click the signal level prediction. The context menu
appears.
2. Select Properties from the context menu. The Properties dialog box appears.
3. Select the Display tab.
4. Click Actions to display the menu and select Shading. The Shading dialog box 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 dialog box.
7. Click OK to close the Properties dialog box and apply your changes.
56
AT332_UMR_E0
1.3.6.1
When you select a transmitter, it appears with a green point at both ends of the icon (
).
When one of the transmitters is already selected on the map, right-clicking on its location will display the context
menu of the selected transmitter.
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.
57
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 dialog box.
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. Move the pointer to the end
of the antenna with a green circle ( ). An arc with an arrow appears under the pointer.
2. 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.
3. 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 dialog box.
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.6.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 dialog box.
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 dialog box.
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
the toolbar) to undo the changes made.
58
Sites
Transmitters
in
AT332_UMR_E0
Change The coordinate system to use in export by clicking the Change button.
Select the fields you want to export. 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 field separately.
To select a field to be exported, select the field in the Available fields list and click
Exported fields list. All fields in the Exported fields list will be exported.
to move it to the
To remove a field from the list of Exported fields, select the field and click
To change the order in which the fields will be exported, select a field and click or to move it up or down.
The top-most field under Exported fields corresponds to the left-most field under Preview.
The actual X and Y coordinates are stored in a hidden GEOMETRY field. The X and Y fields
are informative.
6. Click Export. The selected network elements are exported to the vector file.
You can import vector files in Atoll using File > Import. For more information, see "Importing Vector Format Geo Data Files"
on page 120.
1.4 Maps
Atoll has the following functions to help you work with maps:
59
With the toolbars and scrollbars hidden, you can still navigate around the map window using the keyboard shortcuts:
2. Move the pointer over the map and drag the map in the desired direction.
You can also move the map in the document window by placing the pointer over the map,
pressing the mouse wheel, and dragging the map in the desired direction.
60
AT332_UMR_E0
3. To zoom in on a specific area of the map, click in the map on one of the four corners of the area you want to select
and drag to the opposite corner. When you release the mouse button, Atoll zooms in on the selected area.
4. To zoom out on the map, right-click the map where you want to zoom out.
5. To exit the zoom mode, click the Zoom icon (
The following tools can also be used to zoom in and out in the map:
Mouse wheel: Place the mouse cursor where you want to zoom in (respectively
zoom out) and rotate the mouse wheel forward (respectively backward) to zoom
in (respectively zoom out) on the map.
Keyboard shortcuts: Press Ctrl++ to zoom in on the map or Ctrl+ to zoom out on
the map.
View menu: Select Zoom > Zoom In from the View menu to zoom in on the map
or Zoom > Zoom Out from the View menu to zoom in on the map.
) 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 (
61
Zoom level and map centre (coordinates of the centre of the map window).
Geographic data set, such as map display settings, visibility status of the objects contained in the Geo explorer, and
order of the layers in the Geo explorer.
Optionally, the definition of a computation and a focus zone.
To save the definition of a computation zone and a focus zone in favourite views and to
restore those zones when applying a favourite view, an option must be set in the [FavouriteViews] section of the Atoll.ini file. For more information, see the Administrator Manual.
62
AT332_UMR_E0
By default, favourite views are stored in your user profile. You can store favourite views in
the document by setting an option in the [FavouriteViews] section of the Atoll.ini file. For
more information, see the Administrator Manual.
3. To save a favourite view in the document, right-click the favourite view under User Favourites and select Copy to Document Favourites from the context menu. The selected view is added to the Document Favourites list and will be
saved in the current document when the document is saved.
4. To save a favourite view of the document in your user profile, right-click the favourite view under Document Favourites and select Copy to User Favourites from the context menu. The selected view is added to the User Favourites list
and will be saved in your user profile.
5. To rename a favourite view, right-click the favourite view in the Favourite Views window and select Rename from the
context menu.
6. To delete a favourite view, right-click the favourite view in the Favourite Views window and select Delete from the
context menu.
7. To apply a favourite view, double-click the view in the Favourite Views window. The current applied view is identified
by the ( ) symbol in the Favourite Views window.
Vectors
Sites
Transmitters
Repeaters
Remote antennas
Transmitter cells
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
Cell
An asterisk ("*") to represent multiple characters at the beginning of the name. For example, "*X" will find all
names that contain "X".
A question mark ("?") to represent the first alphanumerical character of the name. For example, "?X" will find all
"AX" to "ZX" and "0X" to "9X".
63
It is not possible to combine the "?" wildcard with other wildcards or to use "?" in any
other position than as the first character.
4. Select the object from the list. Atoll centres it in the map window. If the corresponding data table is open, then the
line containing the object is selected. You can also right-click the object in the list to display the context menu for the
object. You can also click Copy ( ) to copy to the clipboard the list of the object names that correspond to your
search criteria.
Vectors
Sites
Transmitters
Repeaters
Remote antennas
Transmitter cells
To search for a map object by a text property 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
Cell
3. From the Field list, select the text property on which you want to search, for example "Support Type" when you are
looking for a "Site".
4. Enter the name of the object in the text box marked with an equal sign ("="). In the Find on Map window, Atoll
searches and displays the results as you type. You can use an asterisk ("*") as a wildcard by entering it as the first character. For example, entering "*X" will find all names which contain "X".
5. Select the object from the list. Atoll centres it in the map window.
You can right-click the object in the list to display the context menu for the object. You can also click Copy (
to the clipboard the list of the object names that correspond to your search criteria.
) to copy
1.4.8.4 Searching for a Point on the Map by its Full or Partial Postal Address
You can use Find on Map to search for a point by its postal address.
Atoll can use a geocoding service to locate a point on the map from a full or partial postal address. Atoll currently supports
the following geocoding providers: Microsoft Bing and MapQuest. To enable this service, see the Atoll Administrator Manual.
64
AT332_UMR_E0
This geocoding service is not part of Atoll and is governed by the terms and conditions of
its provider, which are subject to change without notice.
To search for a point on the map by its full or partial postal address:
1. Select Tools > Find on Map. The Find on Map window appears.
2. From the Find list, choose Online.
3. Enter a postal Address. You can specify a full or partial address, for example: street name, precinct, city, county,
country, and so on.
4. Click Search. Atoll automatically begins searching and displays the results in the Find on Map window.
5. Select a result from the list. Atoll centres it in the map window.
Path: The total distance between the first point and the last point of a line segment or a polyline.
Line: The distance between the first point and the pointers position (for a line segment), or distance between the last
point and the pointers position (for a polyline).
Total: The total distance between the first point and the pointers location.
Azimuth: The azimuth of the pointers position with respect to the first point of a line segment, or with respect to the
last point of a polyline.
).
2. Click the starting point on the map. The information displayed in the status bar changes from "Ready" to the following
message:
65
Filtering Zone: The filtering zone is a graphical filter that restricts the objects displayed on the map and in the Network
explorer to the objects inside the filtering zone. It also restricts which objects are used in calculations such as coverage
predictions, etc.
Computation Zone: In radio--planning projects, 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 explorer 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.
66
AT332_UMR_E0
The filtering zone is displayed with a blue contour on the map. The filtering zone is applied 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 explorer is selected. You must delete the zone if you no longer want to restrict the selection to sites within the filtering
zone.
Sites 78 and 95 are not in the computation zone, but their propagation zones intersect with the rectangle containing
the computation zone. Therefore, they are taken into consideration in the calculations.
The propagation zones of sites 71 and 93 do not intersect with the computation zone. Therefore, they are not taken
into account in the calculations.
Site 130 is within the coverage zone but has no active transmitters. Therefore, it is not taken into consideration.
The computation zone is considered whether or not it is visible. In other words, if you have drawn a computation zone, it is
taken into account whether or not its visibility check box in the Zones folder of the Geo explorer is selected. You must delete
the zone if you no longer want to define an area for the calculations.
67
Filtering zones
Focus zones
Computation zones
Hot spots
Printing zones
Geographic export zones
To create a zone:
1. In the Geo explorer, expand the Zones folder, right-click the type of zone that you want to create. The context menu
opens.
To draw a polygon:
i.
68
To draw a rectangle:
AT332_UMR_E0
i.
ii. Click the point on the map that will be one corner of the rectangle that will define the zone.
iii. Drag to the opposite corner of the rectangle that will define the zone. When you release the mouse, the zone
will be created from the rectangle defined by the two corners.
To fit the zone to the displayed map area, click Fit Zone to Map Window.
The following alternative methods also allow you to create a computation zone:
In the Vector Editor toolbar, select a type of zone (highlighted in blue) and use the New Polygon (
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 104.
Exporting the computation zone: You can export the computation zone by rightclicking the Computation Zone folder in the Geo explorer and selecting Export
from the context menu.
Selecting the polygon zone in the Zones folder in the Geo explorer,
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 the polygon zone in editing mode, you can edit it as explained in the following sections:
1.4.10.7.1
2. Edit the points on the contour as explained in "Editing Polygon Contours and Lines" on page 73
69
1.4.10.7.2
2. Edit the zone using the Vector Editor toolbar as explained in "Creating Complex Polygons" on page 73.
1.4.10.7.3
Deleting Zones
When you no longer need a polygon zone, you can remove the zone.
To remove a polygon zone:
1. In the Geo explorer, expand the Zones folder, right-click the folder containing the zone you want to remove, and select
Delete Zone from the context menu. The polygon zone is removed and all document data is now displayed.
You can also delete a zone by right-clicking the contour of the zone on the map and selecting Delete.
You can delete all zones by right-clicking the Zones folder and selecting Delete All Zones.
1.4.10.7.4
To copy the selected zone to the clipboard as a bitmap image, click Edit > Copy or press Ctrl-C.
To copy the selected zone as a bitmap image with a specific resolution, click Edit > Advanced Copy and follow the
following steps:
i.
In the Advanced Copy dialog box, select Bitmap image and specify a Custom resolution.
ii. Click OK
To copy the selected zone as a Windows metafile image, click Edit > Advanced Copy, select Metafile image, and
click OK.
To copy the selected zone as a list of coordinates, click Edit > Advanced Copy, select Georeference coordinates,
and click OK.
3. Open the application in which you want to paste the selected zone and select the Edit > Paste command (or press
Ctrl+V). The zone that you copied to the clipboard is pasted into the application document as an image or a list of coordinates.
1.4.10.7.5
Saving Zones
You can save zones as .geo files for later use or for sharing with other users. The type of zone and its shape and coordinates
are saved in the .geo file.
To save a zone:
1. In the Tools menu, select User Configuration and Save. The User Configurations window opens.
2. In the User Configuration window, select Zones and click OK. The Save As window opens.
70
AT332_UMR_E0
3. Select a directory, type a name for the .geo file, and click Save.
For more information on saving and loading user configurations, see "User Configurations" on page 103.
1.4.10.7.6
Loading Zones
You can load .geo zone files into the current Atoll document.
To load a zone:
1. In the Tools menu, select User Configuration and Load. The Open window is displayed.
2. Select a file to import, and click Load. The User Configurations window opens.
3. In the User Configuration window, select Zones and click OK. The zone is loaded.
By default, the loaded zone replaces an existing zone of the same type. An optional
merge feature allows you to merge the imported zone with the existing zone by adding
an option in the Atoll.ini configuration file. For more information, see the Atoll
Administrator Manual.
You can also use the File > Import menu to load zones. In this case, the imported zone
always replaces the existing zone regardless of the Atoll.ini setting.
For more information on saving and loading user configurations, see "User Configurations" on page 103.
1.4.10.7.7
Image files: BMP, PNG, ArcView Grid (TXT), TIFF, BIL, JPEG 2000, and JPG.
DTM files: TIF, BIL, or TXT format.
When saving in BIL format, Atoll allows you to save files larger than 2 Gb.
To export a map area as a raster file:
1. Select an existing zone or create geographic export zone or a printing zone as explained in "Creating Zones" on
page 68.
2. Select File > Save Image As. The Save As dialog box appears.
3. In the Save as dialog box, select a destination folder, enter a File name, and select a file type from the Save as type list.
4. Click Save. The Image Export Options dialog box appears.
5. In the Image Export Options dialog box, select the zone that you want to export and 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. A geo-referenced file is then created for the exported
image.
6. Click OK.
71
polygonal areas are in clockwise order, whereas the coordinates of the vertices of holes within polygonal areas are in counterclockwise order.
When you no longer need the polygon, line, or point, you can delete it from the map.
This section explains the different ways of editing polygons, lines, and points:
) on the Vector Editor toolbar. A folder named "Vectors" is created in the Geo
2. Right-click the Vector folder, click Rename, and type a name for the vector layer.
To draw a polygon:
i.
) in the toolbar.
To draw a rectangle:
i.
) in the toolbar.
ii. Click the point on the map that will be one corner of the rectangle that will define the zone.
iii. Drag to the opposite corner of the rectangle that will define the zone. When you release the mouse, the zone
will be created from 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 145.
To draw a line:
i.
) in the toolbar.
ii. Click once on the map where you want to begin the line.
72
AT332_UMR_E0
) in the toolbar and click once on the map where you want to place the point.
3. Press ESC to deselect the currently selected button on the Vector Editor toolbar.
To move a point:
i.
Position the pointer over the point that you want to move. The pointer changes (
).
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.
3. Select the polygon contour and edit the points of the polygon by performing any of the following actions:
To move a point:
i.
Position the pointer over the point that you want to move. The pointer changes (
).
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.
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.
73
To edit a vector object using the icons on the Vector Editor toolbar:
1. In the Network explorer or the Geo explorer that contains the vector layer, right-click the vector layer folder and select
Draw from the context menu. The vector tools on the Vector Editor toolbar are activated.
You can activate the vector tools by selecting the vector layer to edit from the Vector
Editor toolbar list.
2. Select the polygon contour and edit the polygon by performing any of the following actions:
).
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.
).
ii. Click the contour that you want to combine with the selected one. Atoll combines the two selected contours
into a single object, merging them if they overlap.
).
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.
).
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.
).
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.
Description
Meaning
The zone selection pointer indicates:
Selection arrow
74
AT332_UMR_E0
Appearance
Description
Meaning
Polygon drawing
pointer
The polygon drawing pointer indicates that 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 that you that can draw computation/focus/
Rectangle drawing
hot spot/filtering/printing/geographic export zones, or draw vector or raster
pointer
rectangles on the map. To define a zone, click and drag diagonally.
Hand
The hand pointer indicates that you can move the visible part of the displayed map.
Zoom tool
The zoom pointer indicates that you can click to zoom in at the location of the
mouse pointer, right-click to zoom out at the location of the mouse pointer, and click
and drag to zoom in on an area.
New transmitter
The transmitter pointer indicates that 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.
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 that 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 that 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 that 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 that the first CW measurement
CW measurement point has been set and you can now click other points on the map. Double-click to
path
end the CW measurement path.
The measurement pointer indicates that you can click on the map to set the start
Measurements on
point of your measurement. As you move the pointer, the distance between the first
the map
point and the pointer is displayed in the status bar.
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 explorer.
75
76
"(NOT USED)" indicating that the field is not used in the current Atoll release. The
corresponding check box is cleared in the Columns to be Displayed dialog box.
"(OBSOLETE)" indicating that the field is obsolete and will be removed in a future
Atoll release. The corresponding check box is not available in the Columns to be
Displayed dialog box.
AT332_UMR_E0
Name: Enter the Name for the field that will appear in the database.
Field names must not contain special characters or spaces.
Type: Select a type for the field (text, short integer, long integer, single, double, true/false, date/time, currency,
or binary).
Size (only available for "Text" type): Enter the number of characters. a size in characters.
Group: If necessary, you can define the groups to which this custom field will belong separating each group name
with a semicolon. When you open an Atoll document from a database, you can then select groups 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 user interface.
Read-only: Select the Read-only check box if you do not want the custom field to be modifiable in the user interface.
Default value: If necessary, enter a default value that will appear when you create a new record of this object type.
Choice list (only available if you have selected the "Text", "Short integer", or "Long integer" type): You can create
a choice list by entering the list items in the Choice list text box and press ENTER after each list item, keeping each
choice on a separate line. You can prevent entering values other than those listed in the Choice list by selecting
the Restricted option.
In the Choice list text box, you can enter:
77
Figure 1.22: Creation of a list of associations and display of this list in a data table
For integer choice lists (short integer and long integer):
You cannot mix integer values and associations in the same list. If a line contains
an equal sign, the choice list is considered as a list of associations and the lines
that do not contain an equal sign are ignored.
If you do not associate integer values with the labels defined in the integer choice
list, the association will automatically be done by incrementing an integer value
for each line, starting with zero.
Associating integer values with the labels of your integer choice list is not mandatory but strongly recommended.
1. Access the object types table fields as explained in "Accessing Table Fields" on page 76.
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.
78
AT332_UMR_E0
4. In the colour palette, select a background colour. The colour is applied to the background of the selected columns.
In the colour palette, you can click Other to open the Colours dialog box and select a colour that is not listed in the
main palette.
You can also click Default to revert to the default column background colour corresponding to your Windows theme.
To align the content of the selected cells to the left, click Align Left (
).
To align the content of the selected cells to the centre, click Centre (
).
To align the content of the selected cells to the right, click Align Right (
).
).
).
79
You can change the width of several columns at the same time by selecting their
headers before clicking and dragging the border separating any two column
headers.
Double-clicking the border separating two column headers resets the width of the
column to the left of the border.
You can change the height of several rows at the same time by selecting their
headers before clicking and dragging the border separating any two row headers.
Double-clicking the border separating two row headers resets the height of the
row above the border.
80
AT332_UMR_E0
You can search for a column in the table by entering its name in the search field.
You can display or hide all the columns by selecting or clearing the (Select all) check
box.
You can change the order of columns in the table by selecting them in the list and
clicking the Up
and Down buttons.
You can restore the default list of displayed and hidden columns by clicking the
Reset button.
Column display settings can be saved to and loaded from configuration files using
the Save and Load buttons under Configuration.
5. Click Close.
You can also hide one or more columns in the table by selecting their headers and clicking the Hide Columns button (
the Table toolbar.
) in
3. Right-click the selected header or headers and select Freeze Columns from the context menu or click the Freeze Columns button (
) in the Table toolbar. Frozen columns are grouped to the left of the table and separated from other
columns with a vertical red line.
To unfreeze columns:
Right-click the table and select Unfreeze All Columns from the context menu or click the Unfreeze All Columns button
(
81
To move a column:
1. Open the data table as explained in "Opening a Data Table" on page 76.
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 position. As you drag the column, the position the column
will occupy is indicated by a red line.
82
AT332_UMR_E0
1.5.5.2.1
5. Select Edit > Paste to paste the copied data into the new row. Atoll, creates a new record from the copied data. The
name of the new record is the same as that of the copied record, preceded by "Copy of." You can edit this name.
83
1.5.5.2.2
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 (
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 (
84
AT332_UMR_E0
1.5.5.2.3
1.5.5.3.1
1.5.5.3.2
2. In the Replace button, define the text you want to find and replace:
a. Enter the text you want to find in the Find what box.
b. Enter the text you want to replace the text in the Find what box in the Replace with box.
c. If desired, select the Match case check box.
3. Click Find Next. Atoll proceeds to the next entry of the text entered in the Find what box.
You can replace the text found:
Replace: Atoll replaces the selected text with the entry in the Replace with box.
Replace All: Atoll replaces all occurrences of the text in the Find what box with the entry in the Replace with box.
85
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 94.
To export a table:
1. Open the data table as explained in "Opening a Data Table" on page 76.
2. Right-click the table. The context menu appears.
3. Select Export from the context menu. The Export dialog box appears with, at the bottom, a Preview of the table you
want to export according to the current Field separator setting (see Figure 1.33).
86
AT332_UMR_E0
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 field separately.
To select a field to be exported, select the field in the Available Fields box and click
Exported Fields list. All fields in the Exported Fields list will be exported.
to move it to the
To remove a field from the list of Exported Fields, select the field and click
To change the order of a field in the list, select the field and click
or
to move it up or down. The top-most
field under Exported Fields corresponds to the left-most field under Preview.
You can save the choices you made in the Export dialog box via the Save button next to
Configuration file. The next time you export a data table, you can click Load in the Export
dialog box to open the configuration file you saved and reuse the same settings.
8. Click Export. The Save As dialog box appears.
9. In the Save As dialog box, 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 Network explorer and
pressing Ctrl+E.
For information on importing data into a data table, see "Importing Tables from Text Files" on page 88.
87
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.34). Select <Ignore> for the
columns that you do not want to import. In vector tables, you can also select <Create> to append custom fields, if any.
You can change the width of the columns to make the contents easier to work with. See
"Changing Column Widths and Row Heights" on page 79.
88
AT332_UMR_E0
You can save the choices you made in the Import dialog box via the Save button next to
Configuration file. The next time you import a data table, you can click Load in the Import
dialog box to open the configuration file you saved and reuse the same settings.
10. Select the Mode that will be used for import:
Add: use this mode to add records from the imported file which are missing in the current table. This is the safest
mode as records which are both in the imported file and the current table will not be modified in the current table.
Update and add: this mode (default) is identical to the Add mode with the addition that the values of records in
the current table will be updated with the corresponding values from the imported file.
An additional import mode is available when you import neighbour, secondary antenna, and GSM TRX records:
Reset and add: this mode is identical to Update and add with the addition that existing records will be deleted if
and when the imported file is found to contain data for the same transmitter or cell in the current table.
11. Neighbours only: At this point, you can compare the neighbour data you want to import with existing neighbour data.
Click Compare. The neighbour list to be imported is compared with the existing neighbour list and a comparison report
is displayed in text file, "NeighboursDeltaReport.txt", which sums up the changes that would occur after import.
"NeighboursDeltaReport.txt" lists the following:
The number of Existing Neighbour Link(s), i.e. existing neighbour relations that are also proposed in the imported
neighbour list, and a list of these relations.
A list of Existing Neighbour Link(s) can only be built in Update and add or Reset and add
import modes.
12. Click Import. The contents are imported in the current table according to the selected import Mode.
You can import data from text files into the Sites and Transmitters tables by selecting the
corresponding folder or view in the Network explorer and pressing Ctrl+I.
For information on exporting the information in a data table into a text file, see "Exporting Tables to Text Files and Spreadsheets" on page 86.
An index.xml file which contains the mapping between the data tables in Atoll and the XML file created for each table.
One XML file per data table which contains the data table format (schema) and the data.
The index.xml file stores the system (GSM, UMTS, etc.), the technology (TDMA, CDMA, TD-SCDMA, etc.) of the document, and
the version of Atoll used for exporting the data tables to XML files. It also contains the mapping between the data tables in
the Atoll document and the XML file corresponding to each data table. For more information on XML files, see the Data Structure Reference Guide.
To export all the data tables in your document to XML files:
1. Open your document and select Document > Data Exchange > XML Export from the Atoll menu. The Select Folder
dialog box appears.
2. Select or create the folder where you want the exported XML files to be stored.
3. Click Select Folder. All the data tables in the document are exported to XML files.
89
If you want to export only selected tables to XML files, you must set the AdvancedXML
option in the [Export] section of the Atoll.ini file. When this option is set, you can select the
tables you want to export. For more information, see the Administrator Manual.
the XML files and the current Atoll document must use the same system and technology,
and the Atoll version used to create the XML files must be identical to the Atoll version used to import the data.
When XML files are imported in a document, table and field definitions are not modified, i.e. "Networks" and "CustomFields"
tables are not imported. For more information on XML files, see the Data Structure Reference Guide.
To import data tables into your document from XML files:
1. Select Document > Data Exchange > XML Import. The Select Folder dialog box appears.
2. Select the folder containing the index.xml file.
3. Click OK. The data tables corresponding to the XML files listed in index.xml are imported in the document.
Tables are imported in the same order they appear in the index.xml file. You must not
modify the order of tables in index.xml. The order in which tables are imported is very
important; some data must be imported before other. For example, antennas used by
transmitters must be imported before the transmitters themselves.
When the data tables are imported:
Data that exist both in the tables and in the XML files are overwritten by the data from the XML files.
Data that exist only in the tables and not in the XML files are not deleted from the tables.
Data that only exist in the XML files and not in the tables are imported from the XML files as new records in the tables.
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.
90
AT332_UMR_E0
You can define an area of the map to be printed in one of the following ways:
You can accept the default layout or you can modify the print layout (see "Defining the Print Layout" on page 91).
You can preview how the map will appear once printed (see "Previewing Your Printing" on page 93).
Printing graphics is a memory-intensive operation and can put a heavy load on your
printer. Before printing for the first time, review the "Printing Recommendations" on
page 91 to avoid 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:
Create a printing zone or a focus zone as explained in "Creating Zones" on page 68.
Modify the print layout as explained in "Defining the Print Layout" on page 91.
Preview how the map will appear once printed as explained in "Previewing Your Printing" on page 93.
Points (vectors)
Roads and Lines (vectors)
Surface polygons (vectors)
Multi-format maps - population, 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. Visible objects in the Network explorer, for example, sites, transmitters, and predictions, are displayed above objects in the Geo explorer. To improve performance, you can place vector
layers, such as roads, over predictions. This ensures that those vector layers are visible when you print the map.
To place vector layers over predictions in the Geo explorer:
1. Select the Geo explorer.
2. Right-click the vector layer you want to move to the Network explorer. The context menu appears.
3. Select Move to Network Explorer from the context menu.
4. Select the Network explorer.
5. Drag the vector layer to a position above Predictions but below Sites, Antennas, and Transmitters.
91
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.
To define the appearance of the map when it is printed:
1. Select File > Print Setup. The Print Setup dialog box appears.
2. Click the Page tab to 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.
92
Select the Legend check box if you want to print a legend with the map.
AT332_UMR_E0
Click the Font button to open the Font dialog box 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 dialog box 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 to set the position of graphic items.
a. Select the Map title check box to define a title for the map and set its Position. Clicking the Properties button
opens a dialog box 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 dialog box appears.
By default, Atoll searches for a file named logo.bmp in the Atoll installation folder to use as the default header
logo. However, you can select a different file.
ii. In the Logo dialog box, click File. The Open dialog box 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.
Click the Next Page and Previous Page buttons ( and ) to preview different pages to print. If your printing
zone contains more than one polygon, each printing zone appears on a separate page.
93
Legend Window (for more information on this tool, see "Adding an Object Type to the Legend" on page 54)
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
If you want to print a Point Analysis window, click the tab you want to print.
94
AT332_UMR_E0
to sorting data in the data table because it puts all records with the selected property together. You can also define the properties by which you can group objects.
Once you have grouped data objects, you can access their Properties dialog box from the context menu to edit properties on
all grouped objects. You can save the grouping parameters as a folder configuration. For more information, see "Folder Configurations" on page 107.
This section covers the following topics:
To group transmitters by the sites they are located on, right-click the Transmitter folder and selectGroup By > Site.
The result of grouping can be seen in Figure 1.36.
95
To make a field appear in the Group By submenu, select the field in the Available fields list and click
it to the Fields of the group list.
To remove a field from the Fields of the group list, select the field in this list and click
To change the order of a field in the list, select the field and click
or
to move
to move it up or down.
4. Click OK to close the Configure Menu dialog box then OK to close the Properties dialog box. The Group By submenu
now contains only the fields you selected, in the same order as in the Fields of the group list, and from top to bottom.
96
AT332_UMR_E0
To select a field to be used to group the data objects, select the field in the Available Fields list and click
move it to the Fields of the group list.
To remove a field from the Fields of the group list, select the field in this list and click
To change the order of a field in the list, select the field and click
or
to
to move it up or down.
To undo advanced grouping of data objects, remove all the fields listed under Fields of the
group.
4. Click OK to close the Group dialog box then OK to close the Properties dialog box. The data objects are now grouped
by these properties in the corresponding folder or view, in the order of the fields in the Fields of the group list, from
top to bottom (for example: "Antenna", "Height (m)", and "Site" in Figure 1.38 on page 97).
97
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 (
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 (
98
AT332_UMR_E0
To sort data using the Sort function of the Properties dialog box:
1. In the Network explorer, right-click the folder whose data you want to sort, and select Properties from the context
menu.
2. In the Properties dialog box, select the General tab and click the Sort button. The Sort dialog box appears (see Figure
1.39).
3. 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.
4. 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.
5. Click OK.
You can save the filtering parameters as a folder configuration. For information, see "Folder Configurations" on page 107.
This section covers the following topics:
99
To filter data objects that are inside an existing computation or focus zone, select Filter Inside a Polygon > Computation Zone or Filter By Polygon > Focus Zone.
To filter data objects by drawing a polygon on the map, select Filter Inside a Polygon > Draw. The mouse pointer
changes to polygon mode (
). Draw the filtering zone as explained in "Creating Polygons, Lines, and Points" on
page 72.
When the filter is applied, only the data objects located inside the selected zone are available.
Filter by Selection: All records with the selected value or values are displayed. You can modify the filtered records
or make calculations on them as you would normally do with the entire data table (see Figure 1.40 on page 100).
Filter Excluding Selection: All records without the selected value or values are displayed. You can modify the filtered records or make calculations on them as you would normally do with the entire data table (see Figure 1.41
on page 101).
When the data in a table are filtered, a filter icon ( ) appears at the top of the leftmost
column and in the corresponding column header(s), as shown in Figure 1.40 and Figure
1.41. The icon in the leftmost column can prove useful when the column containing the
filtered data is not displayed due to a large table width.
100
AT332_UMR_E0
To express a filter on one or several fields combined with an AND operator (for example: a=1 AND b>5 AND b<10)
specify all the criteria on a single Criteria row, as in Figure 1.42. In the following example, the filtered table displays
antennas for which the manufacturer name starts with K and for which the gain is between 15 and 20 dBi:
Figure 1.42: The Advanced Filter tab - Conditions on multiple fields combined with an AND operator
To express a filter on a single field combined with an OR operator (for example: a<1 OR a>2) specify the first criteria
on the Criteria row and other criteria on the Or row, as in Figure 1.43. In the following example, the filtered table displays antennas for which the gain is either 17, or 18, or above 20 dBi:
101
Figure 1.43: The Advanced Filter tab - Conditions on a single field combined with an OR operator
To express a filter on multiple fields combined with an OR operator (for example: a=1 OR b=2) specify the first criteria
in the first column of the Criteria row and the other criteria on the OR row of the next column, as in Figure 1.44. You
can combine the OR expressions with AND expressions. In the following example, the filtered table displays antennas
for which either the manufacturer name starts with K, or the gain is between 15 and 20 dBi:
Figure 1.44: The Advanced Filter tab - Conditions on multiple fields combined with AND and OR operators
In the filtering table, the priority of AND and OR conditions is defined by combining them first horizontally, then vertically.
To create an advanced filter:
1. Open the data table as explained in "Opening a Data Table" on page 76.
2. Click the Advanced Filter button (
You can also access the Filter dialog box by clicking the Filter button on the General tab
of the Transmitter Properties dialog box.
102
AT332_UMR_E0
=X
<> X
<X
>X
<=X
>=X
=*X*
=X*
=*X
=?X
The ? wildcard cannot be combined with other wildcards or AND or OR operators and can
only be used as the first character.
To combine conditions with an AND operator, enter the conditions in separate columns on the same row.
To combine conditions with an OR operator, enter the conditions on separate rows.
5. Click OK to filter the data according to the criteria you have defined.
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.
Map Centre and Zoom Level: X and Y coordinates of the centre of the map window and the zoom level.
103
Zones: Filtering, focus, computation, printing, hot spot, and geographic export zones.
Network Data Table Configuration: Formats and settings of network data tables. For more information, see "Defining
the Table Format" on page 79.
Folder Configuration: Sort, group, and filter settings (the current folder configuration, even if not saved, and other
defined configurations for the folders), the filtering zone, the display settings of network data folders (including measurement display settings), and LTE and WiMAX AFP parameters (including constraint weights for frequency planning,
physical cell ID planning, and preamble index planning).
Automatic Neighbour Allocation Parameters: The input parameters of the automatic neighbour allocation.
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.
Prediction List: The list of all available prediction simulations.
GSM Automatic Frequency Planning Parameters: The calculation options that are selected when running GSM AFP
as well as calculation parameters used for interference histograms.
Automatic Scrambling Code Allocation Parameters: The parameters of the automatic scrambling code allocation for
UMTS and TD-SCDMA technologies.
CDMA Automatic PN Offset Allocation Parameters: The parameters of the automatic PN offset allocation.
LTE Automatic Resource Allocation Parameters: The calculation options that are selected when running LTE AFP.
WiMAX Automatic Resource Allocation Parameters: The calculation options that are selected when running the
WiMAX AFP.
Wi-Fi Automatic Resource Allocation Parameters: The calculation options that are selected when running Wi-Fi AFP.
For a detailed description of the user configuration file, see the Administrator Manual.
This section covers the following topics:
104
AT332_UMR_E0
Select the name of the site or transmitter in the row marked with the New Row icon (
).
105
4. Select the check box of the list or lists that you want to display and click OK.
5. Click OK to close the Properties dialog box. Only sites or transmitters that belong to the selected list are now displayed
in the Network explorer and in the map window.
106
AT332_UMR_E0
107
Once you have performed the actions on each view, you can compare the differences by displaying each view, with its grouping, sorting, or filtering settings, on the map. For more information on display properties, see "Setting the Display Properties
of Objects" on page 51.
108
AT332_UMR_E0
To compare views:
1. In the Network explorer, 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:
Export to Google Earth Add-in: This add-in can export items such as sites, transmitters, microwave links, their properties, and coverage prediction plots from Atoll single-RAT and multi-RAT documents to Google Earth.
Signal Level Export Add-in: This add-in is designed to export, from Atoll single-RAT and multi-RAT documents, the
signal levels received from transmitters at each pixel of a user-defined area. Transmitters are listed in decreasing
signal level order starting with the one with the strongest signal level.
Many other add-ins are available from the Forsk support web-site, at:
http://www.forsk.com/support/
For more information about installing add-ins and macros, see the Atoll Administrator Manual.
For information about using an add-in, see the user manual for each add-in. The user manual is located in the installation
directory of the add-in.
The add-in versions that are installed with the product are the latest available at the
release of the Atoll version. Check the Forsk web-site for updates.
109
110
AT332_UMR_E0
111
112
Ctrl+D:
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 and Spreadsheets" on page 86.
Ctrl+F:
Open the Find on Map window when the map is active (in the toolbar, click
Open the Find dialog box when a table is active (in the toolbar, click
Ctrl+H: Open the Replace dialog box when a table is active (in the toolbar, click
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 88.
Ctrl+N: Open the Project Templates dialog box (in the toolbar, click
Ctrl+O: Open the Open dialog box (in the toolbar, click
AT332_UMR_E0
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: Zoom in, zoom out, and define a zoom area on the map (in the toolbar, click
Ctrl+Y: Redo the previous undone modification (in the toolbar, click
)
)
ALT+: Previous zoom and location on the map (in the toolbar, click
ALT+: Next zoom and location on the map (in the toolbar, click
)
)
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.
113
114
Chapter 2
Geographic
Data
In this chapter, the following are explained:
116
AT332_UMR_E0
2 Geographic Data
Several different geographic data types are used in an Atoll document. For example: the digital terrain model (DTM), clutter
classes, clutter heights, online maps, population maps, traffic data maps, and scanned images 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 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 in the Network explorer, either by transferring them to the
Network explorer, or by importing them directly to the Network explorer.
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:
Traffic maps
Population maps
Custom maps
Scanned maps
Online maps
Images from web map services (WMS)
Contours, lines, and points representing, for example, roads, railways, or regions.
117
118
AT332_UMR_E0
Online Maps
You can display various types of online maps in the map window. From the Geo explorer, you can access these maps directly
or by specifying their server URLs. For more information, see "Displaying Online Maps" on page 136.
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, DXF, Planet, SHP, MIF, and TAB.
Vector traffic files in the following formats: AGD, DXF, Planet, SHP, MIF, and TAB.
Scanned image files in the following formats: TIF (1 to 24-bit), JPEG (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 imported raster maps must have the same projection coordinate system.
119
To import a digital terrain model (DTM), select Geo > Digital Terrain Model in the Import to list.
To import a clutter class map, select Geo > Clutter Classes in the Import to list.
To import a clutter heights map, select Geo > Clutter Heights in the Import to list.
To import a population map, select Geo > Population in the Import to list and select from the Use as list whether
the imported data is to be interpreted as a Density (number of inhabitants per square kilometre) or as a Value
(number of inhabitants).
To import a custom map image into an existing folder, select Geo in the Import to list.
To import custom map image into a new folder, click New Folder > in Geo, and type a name for the custom data
folder.
For more information on importing custom geo data, see "Custom Geo Data Maps" on page 133
To import traffic data maps, see "Importing Traffic Maps" on page 121
To import a raster image file into the Network explorer, select Network in the Import to list.
Typically, vector data should be stored in the Geo explorer. Importing into the Network
explorer can however be useful when comparing an image map file with a prediction for
example.
5. By default, the imported file is linked to the Atoll document. To embed the data file into the Atoll document, select
the Embed in Document check box. For information on embedding files, see "Embedding Geographic Data" on
page 125.
6. Click Import. The geo data file is imported and listed in the Geo explorer.
To import a vector file into the Network explorer, select Network in the Import to list.
Typically, vector data should be stored in the Geo explorer. Importing into the Network
explorer can however be useful when comparing an exported vector file with a prediction
for example.
120
AT332_UMR_E0
To import a vector file as a computation, filtering, printing, focus zone or a hot spot, select Geo > Zones and the
type of zone in the Import to list that you want to create. For more information on using zones, see "Using Zones
in the Map Window" on page 66.
To import geoclimatic data, select Geo > Geoclimatic Parameters in the Import to list.
The temperatures in the geoclimatic file must be expressed in Celsius whether the measurement unit defined for
temperatures in the Atoll document is Farhenheit or Celsius.
To import population data, select Geo > Population in the Import to list and specify the data fields:
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.
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 2.1 and Figure 2.2).
To import traffic data maps, see "Importing Traffic Maps" on page 121
To import custom vector data for reference purposes into an existing folder, select Geo in the Import to list.
To import custom vector data for reference purposes into a new folder, click New Folder > in Geo, and type a
name for the custom data folder.
For more information on importing custom geo data, see "Custom Geo Data Maps" on page 133
5. By default, the imported file is linked to the Atoll document. To embed the data file into the Atoll document, select
the Embed in Document check box. For information on embedding files, see "Embedding Geographic Data" on
page 125.
6. The Vector Import window displays the Coordinate system that is used in the current Atoll document. If necessary,
you can convert the file from a different coordinate system into the current coordinate system. Click the Change
button to specify the coordinate system of the file that you are importing.
7. Click Import. The geo data file is imported.
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.
121
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 dialog box.
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.
122
AT332_UMR_E0
Figure 2.3: Server URL list in the Web Map Services Data Import dialog box
The list of WMS servers that appears in the Server URL list is 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.
5. In the left pane of the Web Map Services Data Import dialog box, click the Expand button (
you want to add in the right pane.
6. Select the check box that precedes the image or the image group, i.e. a group preceded by an Expand button (
The images you select are automatically listed in the right pane.
).
Unless you select one or several images, the image or the group of images listed in the right pane will be imported.
To select the images you want to import:
i.
Click the first image, press Shift, and then click the last image to select contiguous images.
ii. Press Ctrl and click each image separately to select non-contiguous images.
7. Arrange the order in which you want multiple 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.
8. If you want, you can also click
9. Click Import in the Web Map Services Data Import dialog box. The WMS Map Import dialog box appears.
The following information is given about the imported WMS data:
10. In the WMS Map Import dialog box, 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 have to go through the import
process again.
11. In the Web Map Services Data Import dialog box, click Close.
12. In the Open dialog box, click Cancel to exit.
123
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 dialog box)
or the Import To list (on the Vector Import dialog box) when you import.
You can transfer geo data that has been imported from the Geo explorer to the Network
explorer, or vice versa. Right-click the data in the Explorer window and select Move to
Network or Move to Geo.
Figure 2.4: New folder for vectors or images in Network and Geo explorers
124
AT332_UMR_E0
You can change the name of the folder to give it a more descriptive name.
Select the Embed in Document check box on the File Import or Vector Import dialog box.
To embed a geo data file that is already linked to the current Atoll document:
1. Select the Geo explorer.
2. Right-click the file you want to embed in the current document.
3. Select Properties from the context menu.
4. Click the General tab of the Properties dialog box.
5. Click Embed.
6. Click OK. The geo data file is now embedded in the current Atoll document.
125
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.
3. Select Properties from the context menu.
4. On the General tab of the Properties dialog box, click the Find button.
5. Browse to the geo data file, select it and click OK.
For information on Display tab settings, see "Setting the Display Properties of Objects" on page 51.
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 dialog box.
126
AT332_UMR_E0
If Height is left blank, propagation models that use this value use 0 by default.
If clutter class heights are modified, you must recalculate path loss matrices by
clicking Force Calculation (
lations.
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 necessary, you can enter a value for each of the following fields applicable to the current document:
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. Use this setting to define a value of indoor loss per frequency. If a network item operates
on a frequency for which the indoor loss is not defined in the indoor loss graph, an indoor loss value is interpolated from the values available in the graph.
C/I Standard Deviation (DL) (dB): to calculate shadowing losses on the C/I values, as related to a user-defined
cell edge coverage probability.
Additional Transmit Diversity Gain (DL) (dB): to add to the 3 dB gain if Tx diversity is active at the subcell level.
Antenna Hopping Gain (DL) (dB): to apply on a calculated C/I if antenna hopping is active at the subcell level.
Ec/Io Standard Deviation (dB): to calculate shadowing losses on the Ec/Io values, as related to a user-defined
cell edge coverage probability.
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.
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.
127
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
support transmit diversity.
Additional Diversity Gain (UL) (dB): to add to the users uplink C/(I+N), if the user and its reference cell
support receive diversity.
128
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
support transmission diversity.
Additional Diversity Gain (UL) (dB): to add to the users uplink C/(I+N), if the user and its reference cell
support reception diversity.
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.
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 C/I Standard Deviation (DL) (dB): to calculate shadowing losses on the C/I values (from GSM transmitters
only), in relation to a user-defined cell edge coverage probability.
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 Ec/Io Standard Deviation (dB): to calculate shadowing losses on the Ec/Io values (from UMTS cells
only), in relation to a user-defined cell edge coverage probability.
UMTS DL Eb/Nt Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt values (from UMTS cells
only), in relation to a user-defined cell edge coverage probability.
UMTS UL Eb/Nt Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt values (from UMTS cells
only), in relation to a user-defined cell edge coverage probability.
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.
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.
AT332_UMR_E0
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 "Setting the Display Properties of Objects" on page 51, 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.
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 127.
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 143.
129
For information on Display tab settings, see "Setting the Display Properties of Objects" on page 51.
130
AT332_UMR_E0
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 98.
Filter: Click the Filter button to filter the data contained in the vector layer. For information on filtering, see
"Advanced Data Filtering" on page 101.
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 76.
5. Click the Display tab. You can use the Display tab to manage the vector layer display. For information on the Table tab,
see "Setting the Display Properties of Objects" on page 51.
131
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 dialog box appears.
3. Select Image or Scan from the Data Type list.
4. Click Import. The image files imported and listed in the Geo explorer.
132
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.
AT332_UMR_E0
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.
133
If the selected file is a raster file, the File Import dialog box appears.
If the selected file is a vector file, the Vector Import dialog box appears.
3. Click the Advanced button. The New Type dialog box appears (see Figure 2.6 on page 135).
4. Enter a Name for the custom geo data map. Atoll creates a folder with this name in the Geo explorer 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:
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 dialog box appears; if the imported file is a vector file, the Vector
Import dialog box appears:
134
File Import dialog box: From the Use as list, select whether the new data is to be used a Density or as a Value.
Vector Import dialog box: 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 2.1 on page 121 and Figure 2.2
on page 121).
AT332_UMR_E0
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 in the Geo explorer containing the geo data file you imported.
If the selected file is a raster file, the File Import dialog box appears .
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.
If the selected file is a vector file, the Vector Import dialog box appears.
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 2.1 on page 121 and Figure 2.2 on page 121).
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 in the Geo explorer containing the geo data file you
imported.
Description: This tab 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.
135
Table: This 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 76.
Data Mapping: This 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 136), 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: This 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:
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 "Setting the Display Properties of Objects" on page 51.
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.)
136
AT332_UMR_E0
3. Select New from the context menu. The Add a Tile Server dialog box appears.
4. Click the small triangle to the right of Name and select a tile server from the drop-down list.
Selecting a tile server from the drop-down list next to Name automatically fills the Name and Server URL fields.
Provider, Type, and Language fields remain greyed.
Name: Indicates the name of the tile server you selected. If you want, you can modify the name.
Server URL: (Read-only) Indicates the URL of the tile server you selected.
A server URL includes a tile set where:
"%z" represents the detail level, and "%x" and "%y" the tile coordinates, or
"%q" represents a quadkey identifying a single tile at a particular detail level.
5. Click OK to validate and close the Add a Tile Server dialog box. A new item appears in the Online Maps folder with the
online map icon ( ) followed by the Name currently defined in the Add a Tile Server dialog box.
6. In the Geo explorer, select the check box preceding the online map that you specified. The selected online map
appears in the background of the map window according to the scale currently defined in the toolbar.
The map tiles that you load in Atoll are stored in a specific cache directory named after the
corresponding tile server. By default, the location of this cache is "%TEMP%\OnlineMaps".
You can change this location by setting the TilesCachePath option in the [OnlineMaps]
section of the Atoll.ini file. For more information, see the Administrator Manual.
2.11.2 Displaying Online Maps from the Microsoft Bing Tile Server
To display online maps from the Microsoft Bing tile server:
1. Set the relevant option with a valid key in the [OnlineMaps] section of the Atoll.ini file, e.g. BingKey=<key>.
2. Make sure that a projection coordinate system is specified (see "Setting a Coordinate System" on page 41) and that it
is the same system supported by the tile server.
If the projection coordinate systems are different, the map tiles can look disproportionate
when you drag the map away from the area targeted by the projection coordinate system.
4. Select New from the context menu. The Add a Tile Server dialog box appears.
5. In the Add a Tile Server dialog box, set the following options:
Name: Type the name you want to display in the Geo explorer under the Online Maps folder, for this tile server.
Provider: Select a provider from the drop-down list, e.g. "Bing"
Type: Select a map type from the drop-down list, e.g. "Aerial", "Road", "Hybrid"
Language: Select a language from the drop-down list (default languages are "English", "French", and "Japanese").
You can display other languages if they are specified in the Atoll.ini file (for example if Provider="Bing", you must
set the BingLanguage"X" and BingCulture"X" options in the [OnlineMaps] section for each additional language ).
6. Click OK to validate and close the Add a Tile Server dialog box. A new item appears in the Online Maps folder with the
online map icon ( ) followed by the Name currently defined in the Add a Tile Server dialog box.
137
7. In the Geo explorer, select the check box preceding the online map that you specified. The selected online map
appears in the background of the map window, according to the scale currently defined in the toolbar.
The map tiles which are loaded in Atoll are stored in a specific cache directory named after
the corresponding tile server. By default, the location of this cache is "%TEMP%\OnlineMaps". You can change this location by setting the TilesCachePath option in the [OnlineMaps] section of the Atoll.ini file. For more information, see the Administrator Manual.
2. Follow the procedure described in "Loading a Geo Data Set" on page 142.
Colour: "Automatic"
Brightness: slider at 50%
Contrast: slider at 50%
5. If you set Colour to "Watermark", the Brightness and Contrast settings are automatically set to 80% and 20%, resp.
6. You can also change the Brightness and/or Contrast settings manually by moving the corresponding sliders.
Click Apply each time you change a setting to see on the map how it affects the displayed online map.
7. Click OK.
138
The display check box: The check box immediately to the left of the object name in the Geo explorer 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" on page 50.
The order of the layers: The layer at the top of the Geo explorer 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 in the Geo explorer
towards the top or the bottom of the tab.
AT332_UMR_E0
All objects in the Network explorer, such as transmitters, antennas, and predictions, are
displayed over all objects in the Geo explorer. Vector geo data, however, can be transferred to the Network explorer, 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 Explorer" on page 131.
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 "Setting the Transparency of Objects and Object Types" on page 53.
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 "Setting the Visibility Scale" on page 53.
In Figure 2.7, 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.
139
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 provide examples that illustrate how data is used in Atoll:
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.
Explorer window
Work space
Case 1
DTM
DTM 2 (20m)
DTM 1 (50m)
Case 2
DTM
DTM 1 (50m)
DTM 2 (20m)
Figure 2.8: Multi-layer management in calculations two DTM maps representing different areas
2.12.2.2 Example 2: Clutter Classes and DTM Maps Representing the Same Area
In this example, there are two imported maps:
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 2.9: Multi-layer management in calculations Clutter and DTM maps representing the same area
140
AT332_UMR_E0
In the case of two clutter class maps, Atoll uses the order of the maps in the Clutter Classes folder in the Geo explorer 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."
Explorer window
Work space
Case 1
Clutter classes
Clutter 2 (20m)
Clutter 1 (50m)
Case 2
Clutter classes
Clutter 1 (50m)
Clutter 2 (20m)
Figure 2.10: Multi-layer management in calculations two clutter maps representing the same area
Hold the pointer over the geo data until the tip text appears. The surface area is only given for closed polygons.
141
You can save and load other types of information with user configuration files as well. For
information, see the Administrator Manual.
142
AT332_UMR_E0
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.
Clutter classes (for more information, "Editing Clutter Class Maps" on page 143)
Contours, lines, and points (for more information, "Vector Objects" on page 71)
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 145)
Traffic data maps
Custom data maps (for more information, "Editing Population or Custom Data Maps" on page 145).
).
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.
143
You can copy the exact coordinates of a closed polygon by right-clicking it on the map and
selecting Properties from the context menu.
Moving a point:
i.
Position the pointer over the point you want to move. The pointer changes (
).
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.
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.
144
).
AT332_UMR_E0
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 (
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.
11. For Atoll to consider the new vector layer as part of the data map, you must map the vector layer. Right-click the Population or Custom Data folder. The context menu appears.
12. Select Properties from the context menu. The Properties dialog box appears.
13. Click the Data Mapping tab. For the following geo data:
Population Map:
i.
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 "Vector Objects" on page 71.
145
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 explorer, 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.
BMP Files (*.bmp): When you select BMP format, Atoll automatically creates the corresponding BPW file containing the georeference information.
PNG Files (*.png): When you select PNG format, Atoll automatically creates the corresponding PGW file containing the georeference information.
ArcView Grid Files (*.txt, *.asc): The ArcView text format is intended only for export; no corresponding geo-reference file is created.
TIFF Files (*.tif): When you select tagged image file format, Atoll automatically creates the corresponding TFW file
containing the georeference information.
BIL Files (*.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.
Vertical Mapper Files (*.grc,*.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 dialog box appears (see Figure 2.13).
146
AT332_UMR_E0
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.
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.
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 125).
You can simultaneously export the display configuration file (CFG) of the edited vector
layer by setting an option in the Atoll.ini file. The exported display configuration file will
have the same file name and will be saved in the same directory as the exported vectorformat file. For more information about setting options in the Atoll.ini file, see the
Administrator Manual.
To export a vector layer:
1. In the Explorer window, select the tab containing the vector layer you want to export.
2. Right-click the vector layer folder you want to export. The context menu appears.
3. Select Save As from the context menu. The Save As dialog box appears.
4. In the Save As dialog box, 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: "Atoll Geographic Data" vector format created for Atoll. The latter can read AGD files faster than the other
supported vector formats.
SHP: ArcView vector format can be used for vector layers containing only polygons, only lines, or only points. If a
vector file has a combination of polygons, lines, and points, you should use the AGD, MIF, or TAB formats instead.
MIF and TAB: MapInfo vector formats.
5. Click Save in the Save As dialog box. The Vector Export dialog box appears. It displays the current coordinate system
which you can change by clicking Change.
147
6. 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.
148
AT332_UMR_E0
If the geo data file is a vector file, the Vector Export dialog box appears.
a. The Vector Export dialog box displays the coordinate system of the file. To change the coordinate system used for
the exported file, click Change. The Coordinate Systems dialog box appears. For information on the Coordinate
Systems dialog box, see "Setting a Coordinate System" on page 41.
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 dialog box appears.
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 explorer.
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.
149
150
Chapter 3
Radio Antennas
and Equipment
This chapter provides the
information to work with
antennas and equipment in
Atoll.
152
AT332_UMR_E0
General tab: This tab contains general information about the antenna.
Frequencies: This specifies the Min and Max operating frequencies of the antenna. These fields are used by the
Antenna Selection Assistant to filter antennas and to suggest antennas that are compatible with the operating
frequency of the transmitter.
153
Horizontal Pattern and Vertical Pattern tabs: These tabs display the horizontal and vertical antenna pattern diagrams
and a table of attenuation in dB (Att.) per Angle. You can specify as many as 720 attenuation values for angles from
0 to 359. For more information on functions related to antenna patterns, see "Working With Antenna Patterns" on
page 157.
Other Properties tab: This tab provides access to additional information and custom fields.
To create an antenna:
1. Click the Parameters explorer.
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 Record Properties dialog box appears.
5. Click the General tab. You can enter information in the fields described in "Antenna Properties" on page 153.
6. Click the Horizontal Pattern tab. 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.
If there are blank rows in your data sheet, Atoll interpolates 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.
When Atoll performs linear interpolations on antenna pattern attenuation, interpolations
are calculated in Watts by default. You can change this setting to dB by adding an option
in the Atoll.ini file. For more information on changing options in the Atoll.ini file, see the
Administrator Manual.
g. Click Apply to display the pattern of the values you have pasted in.
154
AT332_UMR_E0
7. Click the Vertical Pattern tab. 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 OK.
Atoll checks whether the vertical and horizontal patterns are properly aligned at the extremities. The antenna patterns are
properly aligned when the following conditions are met:
Horizontal pattern attenuation at 0 is the same as the vertical pattern attenuation at the electrical tilt angle, and
Horizontal pattern attenuation at 180 is the same as the vertical pattern attenuation at "180 minus the electrical
tilt".
horizontal pattern attenuation at 0 is the same as the vertical pattern attenuation at the electrical tilt angle, and
horizontal pattern attenuation at 180 is the same as the vertical pattern attenuation at "180 minus the electrical tilt".
Atoll allows you to import Planet-format index files for pattern attenuations with as many
as 720 angles.
155
and vertical sections of the antenna pattern are displayed, Atoll uses the actual 3D pattern without the need to create 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 allowed value range is [0,360] and the smallest increment is 1.
Tilt angle: The allowed value ranges are [-90,90] and [0,180], and the smallest increment is 1.
Attenuation: The attenuation (in dB).
The text file describing 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:
1. Select the Parameters explorer.
2. Click the Expand button ( ) to expand the Radio Network Equipment folder.
3. Right-click the Antennas folder. The context menu appears.
4. Select Import from the context menu. The Open dialog box appears.
5. Select "3D Antenna Files (*.txt)"from the Files of type list.
6. Select the file you want to import and click Open. The Setup dialog box appears (see Figure 3.2).
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 assumes that the gain is "0."
156
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.
AT332_UMR_E0
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 dialog box as a configuration file by
clicking the Save button at the top of the dialog box 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.
157
2. In the Antenna Comparison window, click Add Pattern. The Antenna Selection Assistant window appears.
3. In the Antenna Selection Assistant window, find and select an antenna and click OK. For more information about the
Antenna Selection Assistant, see "Assigning Antennas to Transmitters" on page 159.
4. Repeat from step 2 to add as many antenna patterns as required. The patterns are displayed on top of each other in
the Horizontal Patterns and Vertical Patterns tabs.
5. Select Add antenna gain to display the patterns with the specified gain.
6. Click Close when you have finished comparing the antenna patterns.
Max Angle: Enter the maximum angle. Smoothing will be applied to the section of the pattern between 0 and the
maximum angle (clock-wise).
Peak-to-Peak Deviation: Enter the attenuation values to which smoothing will be applied. Atoll smooths 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.
6. Click OK.
To smooth the vertical and horizontal patterns of all the antennas in the Antennas folder, right-click the folder and select
Smooth from the context menu.
158
AT332_UMR_E0
In most cases, select Standard to filter suitable antennas based on any combination of the following parameters:
Half-power beamwidth, Electrical tilt, and Electrical azimuth.
If you have a very large number of available antennas or more complex requirements, you can select Advanced
and then click Filter to specify an advanced filter. You can specify complex filters by combining filtering conditions
on multiple fields using AND and OR operators. For more information on using this option, see "Advanced Data
Filtering" on page 101.
The Available antennas list displays the result of the standard or advanced filtering.
4. In the Available antennas list, select an antenna and click OK to apply the selected antenna to the transmitter.
Any filter applied to the Antennas folder is taken into account by the Antenna Selection
Assistant in the Available antennas list.
If the candidate already has a shared antenna name, you will see that name in the "Shared Antenna" column and
it appears greyed in the field beside Shared antenna at the top of the Antenna Sharing assistant.
If the candidate does not have a shared antenna name, you can enter a name in the Shared antenna field.
In addition to the antenna position offset (Dx, Dy), azimuth, height, and mechanical tilt, if you also want to use the
same antenna pattern for the transmitters using the shared antenna, enter a name in the Shared pattern field.
159
to change the azimuth of the shared antenna (see "Changing the Azimuth of the Antenna Using the Mouse" on
page 57), the objects sharing that antenna will move together on the map.
You can also specify a shared antenna for a transmitter, a repeater, or a remote antenna
in the Shared antenna field on the General tab of their Properties dialog boxes.
When you change the main antenna pattern on a shared antenna that uses a shared pattern, the pattern changes for all
transmitters that have the same shared antenna name and the same shared pattern name.
To change the antenna pattern for all shared antennas:
1. In the Network explorer, expand the Transmitter folder, right-click a transmitter, and click Properties. The Transmitter Properties window opens.
2. On the Transmitter tab of the Transmitter Properties window, under Main Antenna, select a new antenna pattern. If
necessary, click Select to use the Antenna Selection Assistant.
3. Click OK. The main antenna changes for all shared antennas that use the same shared antenna name and the same
shared pattern name.
160
AT332_UMR_E0
You can choose to display multiple-beam antennas with the mechanical azimuth only. This
superimposes all beams as a single transmitter on the map, but makes selection of each
individual transmitter more difficult.
To do this, in the Network explorer, right-click the Transmitter folder, select Properties,
click Display, and select Display mechanical azimuth only.
This only affects the display of the transmitter symbols. Predictions and simulations always
use the combination of mechanical and electrical azimuth.
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 161.
Feeder cables: Feeder cables connect the TMA to the antenna. To define feeder cables, see "Defining Feeder Cables"
on page 161.
Transmitter equipment: To define transmitter equipment, see "Defining Transmitter Equipment" on page 162.
Name: Enter a name for the TMA. This name will appear in other dialog boxes 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.
Name: Enter a name for the feeder cable. This name will appear in other dialog boxes 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.
161
Name: Enter a name for the transmitter equipment. This name appears in other dialog boxes 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.
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.
3.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 with the Friis transmission 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 dialog box, available by clicking the Equipment button on the Transmitter tab of
the transmitters Properties dialog box, or
Using the Transmitters table, available by right-clicking the Transmitters folder in the Network explorer and selecting
Open Table from the context menu.
When you assign equipment to a transmitter using the Equipment Specifications dialog box, Atoll updates the real values
when you click OK and close the dialog box. 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:
1. Select the Network explorer.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Calculations > Update Losses and Noise Figures from the context menu.
162
AT332_UMR_E0
To update the real values (total losses and transmitter equipment noise figure) with the calculated values of a group of transmitters:
1. Select the Network explorer.
2. Right-click the Transmitters folder. The context menu appears.
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:
163
164
Chapter 4
Radio
Calculations
and Models
This chapter provides the
information to work with
calculations in Atoll.
166
AT332_UMR_E0
Point predictions: 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, or service availability 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 Events viewer 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.
Frequency Range
Recommended Use
Terrain profile
d > 10 km
Low frequencies
Broadcast
ITU 1546
30 3000 MHz
Terrain profile
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
Okumura-Hata
(Automatic calibration)
Terrain profile
Statistical clutter (at the receiver)
1 < d < 20 km
GSM 900, CDMA2000, LTE
167
Model
Frequency Range
Recommended Use
Cost-Hata
(Automatic calibration)
Terrain profile
Statistical clutter (at the receiver)
1 < d < 20 km
GSM 1800, UMTS, CDMA2000,
LTE
ITU 529-3
Terrain profile
Statistical clutter (at the receiver)
Terrain profile
Statistical clutter
1 < d < 20 km
GSM, UMTS, CDMA2000, LTE,
WiMAX, Wi-Fi
Erceg-Greenstein (SUI)
Terrain profile
Statistical clutter (at the receiver)
Sakagami Extended
(Automatic calibration)
Terrain profile
Statistical clutter
1 < d < 20 km
LTE, WiMAX, Wi-Fi
Terrain profile
Statistical or deterministic clutter
3D building and line vectors
(optional)
Specific morphology, facets and
graphs data files (optional)
Terrain profile
Statistical or deterministic clutter
3D building and line vectors
(optional)
CrossWave Model
Aster PropagationModel
(Automatic calibration)
where:
PR
PTx
K1
K2
K3
H Tx
eff
DiffractionLoss
K5
K6
K7
H Rx
168
K4
eff
Kclutter
f(clutter)
AT332_UMR_E0
Khill, LOS
These parameters can be defined on the tabs (Parameters, and Clutter) of the Standard Propagation Model Properties dialog
box. You can also use a wizard to calibrate the Standard Propagation Model. For information on the Automatic Calibration
Wizard, see the Measurements and Model Calibration Guide.
This section covers the following topics:
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, this approach
is recommended.
Approach #2: If you consider clutter altitudes, do not define a 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
4.1 on page 170 this diffraction is displayed with a green line.
To consider indoor losses inside a building when only using a deterministic clutter map
(i.e., a clutter height map), disable the Indoor Coverage option when creating a
prediction. If the option is enabled, indoor losses are added twice (once for the entire
reception clutter class and once as indoor losses).
169
Figure 4.1: Diffraction caused by surrounding buildings when the receiver is indoors
Deygout
Epstein-Peterson
Deygout with correction
Millington
The methods for calculating diffraction are based on the general method for one or more obstacles described in the ITU 526-5
recommendations. Calculations include the curvature of the Earth. Along the transmitter-receiver profile, you can choose to
consider either the ground altitude only or both the ground altitude and the clutter height. If you choose to consider clutter
height, Atoll extracts information from the clutter heights file. Otherwise, it uses an average clutter height specified for each
clutter class. When clutter height information is statistical, Atoll also uses clearance values for each clutter class to establish
street models. For detailed information on each method, see the Technical Reference Guide.
To consider heights when calculating diffraction:
1. In the Parameters explorer, expand the Propagation Models folder and right-click Standard Propagation Model., and
select Properties from the context menu. The Properties dialog box appears.
2. Click the Clutter tab.
3. 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.
4. Click OK.
170
Minimum
Typical
Maximum
K1
Variable
Variable
Variable
K2
20
44.9
70
K3
-20
5.83
20
AT332_UMR_E0
Minimum
Typical
Maximum
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. The following table gives some possible values for K1.
Frequency (MHz)
K1
935
12.5
1805
22
1930
23
2110
23.8
1900
23
2300
24.7
2500
25.4
2700
26.1
3300
27.8
3500
28.3
Its value is heavily influenced by the values given to losses per clutter class.
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 dialog box. 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.
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
171
Clutter Class
Losses (dB)
Urban
Suburban
from -5 to -3
Industrial
from -5 to -3
Open in urban
from -6 to -4
Open
Water
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.
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 dialog box. 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 dialog box. Or, you can select "(default)" for the receiver height. When creating a coverage prediction, Atoll will then read the receiver height on the Calculation Parameters tab of the Network
Settings Properties dialog box in the Parameters explorer.
172
AT332_UMR_E0
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.
173
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.
K3: Enter the K3 value.
LOS calculations only: Select LOS calculations only ("1 - Yes") or LOS and NLOS calculations ("0 - No") .
Method: Select the method that will be used to calculate diffraction.
K4: Enter the K4 value.
3. Click OK.
174
AT332_UMR_E0
Clutter taken into account in diffraction: Select "1 - Yes" if you want the clutter heights to be taken into account
when calculating diffraction.
Receiver on top of clutter: Select "1 - Yes" if you want to consider that the receiver is located on top of the clutter,
for example if fixed receivers are located on building rooftops.
Indoor calculations only: Select "1 - Yes" to create coverage predictions based on indoor calculations only.
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 weigh
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: If necessary, enter the losses for each clutter class to be considered when calculating f(clutter).
Clearance: If necessary, enter a clearance around each receiver for each clutter class. The clearance information
is used to model streets when it is assumed that the receiver is in the street. The clearance is used to calculate
diffraction when statistical clutter is considered.
Rx Height: If necessary, enter a specific receiver height for each clutter class. Alternatively, you can select
"(default)" for the receiver height. When creating a coverage prediction, Atoll reads the receiver height on the Calculation Parameters tab of the Network Settings Properties dialog box in the Parameters explorer.
3. Click OK.
175
Vertical diffraction over rooftops based on Walfisch-Ikegami model and multiple knife-edge Deygout method.
Horizontal diffraction based on ray tracing.
Aster can use geographical data such as vectors for ray tracing, but it can also perform ray tracing with raster data only.
Extremely fast: Aster uses a unique high-speed ray-tracing technique, based on the raster sampling of building angles.
For example, 5 seconds are enough to calculate a 1,500 m radius cell with a 5m grid on an ordinary laptop.
Highly accurate: Aster can take all the main radio propagation effects into account, leading to highly accurate coverage
prediction results. Its accuracy applies to antennas above rooftops (where signal levels are mainly due to vertical diffractions) as well as antennas under rooftops (where signal levels are mainly due to horizontal diffractions).
Ready & Easy-to-use: Aster is fully integrated in the Atoll environment and there is no need for a special database or
for any type of data pre-processing.
Compatible with high resolution (less than 25 m) raster data and with all types of clutter data. It is also compatible
with vector data (ESRI Shapefiles SHP and MapInfo TAB formats are currently supported).
Compliant with all wireless technologies and frequencies ranging from 150 MHz to 5 GHz.
Supplied with pre-calibrated parameters using more than 1.5 million measurement points. The standard deviation
from measurements is typically less than 6.5 dB. Model configurations are intuitive and easy to access.
Auto-calibration: Aster supports measurement-based auto-calibration. The standard deviation can drop to less than
6.5 dB in scenarios and environments with high-resolution geo data and good-quality measurements.
176
General: use this tab to change the Aster model instance name, view the register signature, and enter comments.
Configuration: use this tab to define indoor calculation and indoor antennas parameters.
Clutter: use this tab to define clutter classes and propagation classes.
Geo: use this tab to map geo raster data to deterministic propagation classes and define vector files.
Ray Tracing: use this tab to modify the settings of the ray tracing algorithm.
AT332_UMR_E0
177
Reflection on mountains
Horizontal guided propagation
CrossWave supports automatic tuning based on CW measurements, but is also statistically pre-calibrated by incorporating
measurements from various countries and environment types. CrossWave benefits from several years of experience in modelling of basic components (antenna and profile modelling) and automatic tuning (multi-linear regression, neuronal networks,
etc.). Although highly complex, the CrossWave model combines accuracy, performance, versatility, and robustness.
CrossWave is developed by Orange Labs and is distributed and supported by Forsk as an
optional component for Atoll. For licensing information, contact your Forsk representative. For information on installing and using the CrossWave propagation model, see the
CrossWave user manual.
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 179)
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.
4. Click OK.
178
AT332_UMR_E0
5. 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 179.
6. 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.
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.
4. Click OK to save your changes and close the Formulas dialog box.
5. Click OK.
You can weight the diffraction loss by setting the diffraction multiplying factor
within the range [0;1].
Constant values and a 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.
Add diffraction loss: The Cost-Hata propagation model can consider losses due to diffraction by using both a 1knife-edge Deygout method, and the ground altitude provided by 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 environmental formula (See "Creating or Modifying Environment Formulas (Cost-Hata)" on
page 180)
179
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.
3. Click OK.
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.
4. Click OK to save your changes and close the Formulas dialog box.
5. 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.
180
AT332_UMR_E0
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 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 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.
3. Click OK.
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.
4. Click OK to save your changes and close the Formulas dialog box.
5. Click OK.
181
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:
1. In the Parameters explorer, expand the Propagation Models folder, right-click ITU370, and select Properties from the
context menu. The Properties dialog box appears.
2. Click the Parameters tab.
3. Under Calculate exceeded signal during, select one of the following:
4. 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.
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.
4. Click OK.
182
AT332_UMR_E0
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.
4. Click OK to save your changes and close the Formulas dialog box.
5. Click OK.
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
183
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 dialog box.
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.
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.
3. Click OK.
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).
184
AT332_UMR_E0
5. 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.
6. Click OK.
For more information, see the Technical Reference Guide and the ITU-R P.1546 recommendation.
Value Assigned
K1
K2
40
K3
-30
K4
K5
K6
K7
-5
For more information on working with the Standard Propagation Model, see "Standard Propagation Model" on page 168.
Properties: The Properties dialog box appears with the following tabs:
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.
Other tabs (Parameters, Clutter, Configuration, etc.): one or more additional tabs appear in the Properties
dialog box according to the selected propagation model.
Rename: You can enter a new name for the selected propagation model.
Delete: The selected propagation model is deleted.
185
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 explorer 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.
First, Atoll checks whether the path loss matrices exist and, if so, if 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.
If the path loss matrices do not exist or are not valid, Atoll calculates them. There must be at least one unlocked coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click Calculate
( ).
Atoll then 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 (
Predictions folder.
You can stop all calculations in progress by clicking the Stop Calculations button (
If you click Force Calculation (
pending simulations.
) instead of Calculate (
Calculating path loss matrices can be 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 distributed calculation server application on other workstations or on servers. Once the distributed calculation 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 setting up the distributed calculation server application, see The Atoll Administrator Manual.
186
AT332_UMR_E0
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 calculations. 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 simulations, and so on., 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 "Computation Zone" on page 67.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be studied.
The calculation radius determines the size of the area covered by calculations, where a wider radius requires more processing.
The resolution determines the size of a pixel, where a smaller pixel provides a higher resolution, which requires more processing.
Atoll enables you to calculate two levels of path loss matrices:
The extended matrix allows you to reduce calculation time and storage size by calculating lower resolution matrices in areas
that are far from the transmitter. The extended matrix is only calculated all three parameters are specified: 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. Under these circumstances, Atoll does not assign a calculation radius to transmitters. This
is possible when you let Atoll calculate the optimised main or extended calculation radii based on user-defined minimum
received signal levels. As an consequence, the disk storage dedicated to path loss matrices can be drastically reduced. For
more information, see "Optimising Path Loss Matrix Storage" on page 194.
When creating coverage predictions, you can define a coverage resolution that is different
from the resolution defined for the path loss matrices.
There are several methods of assigning propagation models for calculations. Therefore, it is important to understand which
propagation model Atoll uses in each specific case:
If assign a propagation model to a single transmitter, as explained in "Assigning Propagation Parameters to a Single
Transmitter" on page 188, or to a group of transmitters, as explained in "Assigning Propagation Parameters to a Group
of Transmitters" on page 189, this is the propagation model that is used.
A propagation model assigned to an individual transmitter or to a group of transmitters always has precedence over
any other assigned propagation model.
If you assign a propagation model globally to all transmitters, as explained in "Assigning Propagation Parameters to
All Transmitters" on page 189, this is the propagation model that is used for all transmitters except those to which you
have assigned a propagation model either individually or as part of a group.
If, after assigning a propagation model to an individual transmitter or to a group of
transmitters, you assign a propagation model globally, you will override the propagation
models that you had previously assigned to individual transmitters or to a group of
transmitters.
187
When you assign a propagation model globally, you override any selection you might
have made to an individual transmitter or to a group of transmitters.
If you assign a default propagation model for calculations, as described in "Specifying the Default Propagation Parameters" on page 188, this is the propagation model that is 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, then that
propagation model is used.
The radius and resolution of the extended matrix must be larger than the radius and resolution of the main matrix.
4. Click OK. The selected calculation parameters will be used for the selected transmitter.
188
AT332_UMR_E0
4. 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 Propagation Parameters to a Single Transmitter" on page 188 will override this
entry.
You can also optimise the radius of the path loss matrix as explained in "Optimising Path
Loss Matrix Storage" on page 194.
189
) in the Transmitters folder and with the defined colour on the map and inactive
) in the Transmitters folder and empty symbol on the map.
For technologies that support cells, you can also set the cell on a transmitter as active or inactive.
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 4: Radio Calculations and Models.
To set a single transmitter as active, right-click the transmitter and select Activate Transmitter from the context
menu. The transmitter is now active.
To set all transmitters as active, right-click the Transmitters folder and select Activate Transmitters from the context menu. All the transmitters in the folder are set as active.
To set a group of transmitters as active, expand the Transmitters folder, right-click the group of transmitters that
you want to set as active, and select Activate Transmitters from the context menu. All the transmitters in the
group are set as active.
To open the Transmitters table, select Open Table. The Transmitters table appears with each transmitters parameters in a row.
To open the Cells table, select Cells > Open Table. The Cells table appears with each cells parameters in a row.
2. For each transmitter or cell that you want to set as active, select the check box in the Active column.
190
AT332_UMR_E0
deal of memory. Therefore, in the case of large radio-planning projects, saving your path loss matrices externally will help
reduce the size of the file and the use of computer resources.
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 read only and shared by all users. When users change their radio data and recalculate path loss matrices, the changes to the
path loss matrices are stored locally; the centralised 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 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.
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.
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.
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 dialog box.
3. Click OK.
191
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.
Atoll calculates path loss matrices of co-located co-site transmitters in a single step, i.e., per site, instead of calculating each
transmitters matrix separately. The calculation of path losses comprises two mutually independent components:
1. The path loss due to electromagnetic wave propagation around the transmitter. This component is calculated by propagation models.
2. Attenuation due to antenna pattern (masking). This component is independent of the propagation calculation.
The first component, which is the most time-consuming, is the same for all co-located co-site transmitters. Therefore, by
calculating path loss matrices per site, Atoll is able to provide short calculation times. Atoll generates separate path loss
matrix results for each transmitter, combining both components of path loss calculations. Co-located co-site transmitters are
transmitters with the same site, antenna height, DX, DY, main and extended propagation models, main and extended calculation radii, and main and extended calculation resolutions.
By default, the per-site path loss calculation is enabled in Atoll 64-bit and disabled in Atoll 32-bit. You can enable and disable
this option as needed using the Atoll.ini file. For more information, see the Administrator Manual.
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 dialog box. 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.
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:
192
AT332_UMR_E0
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 195 for more information.
4. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialog box
appears (see Figure 4.7) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a
summary of the reasons for invalidity.
Click in the row containing the path loss matrix you want to delete. The selected row is highlighted.
ii. Right-click anywhere in the Results table and select Delete from the context menu, or click the Actions button
and select Delete from the menu. The deleted path loss matrix appears hatched.
Select contiguous rows by clicking the first row, pressing Shift, and clicking the last row, or non-contiguous
rows by pressing Ctrl and clicking each row separately. The selected rows are highlighted.
ii. Right-click anywhere in the Results table and select Delete from the context menu, or click the Actions button
and select Delete from the menu. The deleted path loss matrices appear hatched.
Figure 4.8: Available results for path loss matrices after selecting the Delete command
3. Click OK. The next time you display the Results dialog box via the Predictions folder, "No available result" will be indicated in red under File for the corresponding transmitters.
193
Figure 4.9: Available results for path loss matrices after selecting the Delete command
You can also delete path loss matrices via the Transmitters folder:
1. In the Network explorer, right-click the Transmitters folder and select Properties from the context menu. The Transmitters Properties dialog box appears.
2. Click the Propagation tab. The path loss matrix information is listed in the Available Results table.
3. In the Available Results table, select the path loss matrix/matrices you want to delete:
Click in the row containing the path loss matrix you want to delete. The selected row is highlighted.
ii. Right-click anywhere in the Available Results table and select Delete from the context menu. The deleted path
loss matrix appears hatched.
Select contiguous rows by clicking the first row, pressing Shift, and clicking the last row, or non-contiguous
rows by pressing Ctrl and clicking each row separately. The selected rows are highlighted.
ii. Right-click anywhere in the Available Results table and select Delete from the context menu. The deleted path
loss matrices appear hatched.
4. Click OK. The next time you click the Available results table via the Transmitters folder, "No available result" will be
indicated in red under File for the corresponding transmitters.
Display all results: All path loss matrices, including those which do not need optimisation, are displayed.
Display modified radii 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 transmitter:
194
AT332_UMR_E0
Optimised Extended Radius: The radius of the extended path loss matrix after optimisation.
6. Select the Commit check box for each transmitter for which you want to commit the optimised radius (or radii). You
can select one, several, or all the results and right-click in order to select, ignore or commit the results.
7. Click Commit. The calculation radius (or radii) for all transmitters whose Commit check box is selected is updated.
Clearing the Main matrices or Extended matrices check box at the top of the dialog box will not prevent the main or
extended matrices from being updated if the given check box was selected before you clicked the Calculate button. If
the calculation radii of extended matrices are changed, the extended matrices are deleted and will 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 "Setting the Storage Location of Path Loss Matrices" on
page 190 for more information). Invalid (or non-existent) 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 "Checking the Validity of Path Loss Matrices" on page 192 for more information). These 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 of the selected transmitter or transmitters will be optimised.
CW Measurements: You select the CW measurements from the CW Measurements folder as explained in "Tuning
Path Loss Matrices Using CW Measurements" on page 197. 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 198. 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 199. 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.
195
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.
2. Select Properties from the context menu. The Properties dialog box appears.
3. Select the Path Loss Tuning Parameters tab (see Figure 4.10).
Figure 4.10: Defining the ellipse for tuning path loss matrices
4. Under Tuning Ellipse, set the following parameters:
Radius of the Axis Parallel to Profile: Enter the radius of the ellipse axis oriented in the same direction as the transmitter (or repeater).
Radius of the Axis Perpendicular to Profile: Enter the radius of the ellipse axis perpendicular to the transmitter
(or repeater).
5. Click OK.
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.
2. Select Properties from the context menu. The Properties dialog box appears.
3. Select the Path Loss Tuning Parameters tab.
196
AT332_UMR_E0
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.
Minimum measurement threshold (dBm): Enter the measured signal level under which measurements are not
taken into account for the path loss tuning.
5. Click OK.
197
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 item.
198
AT332_UMR_E0
For each transmitter selected from the For the following transmitters list, select the check box for each measured
signal strength that will be used to tune the path loss matrices.
g. 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 Events viewer.
To tune the path loss matrices for selected transmitters using selected drive test data paths:
a. Right-click the Drive Test Data folder and select Tune Path Loss Matrices from the context menu. The Measurement Path Selection dialog box appears (see Figure 4.13).
b. Under Measurement Paths, select the option beside the list of drive test data paths.
c. Select the check box corresponding to the drive test data you want to use to tune the path loss matrices.
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 from the 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 Events viewer.
For repeaters, Atoll 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 item.
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:
4. Select the tuning path loss matrices you want to manage using the available catalogue:
199
a. 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.
b. Right-click inside the multiple selection. The context menu appears.
5. Select Path Loss Tuning Points from the context menu. The Path Loss Tuning Points dialog box appears.
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:
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:
1. In the Network explorer, right-click the Transmitters folder and select Properties from the context menu. The Properties dialog box appears.
2. Click the Propagation tab. The path loss matrix information is listed in the Available Results table.
3. In the Available Results table, select the tuning path loss matrices for which you want to import tuning files:
200
AT332_UMR_E0
a. 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.
b. Right-click inside the multiple selection. The context menu appears.
4. In the context menu, select Import Path Loss Tuning Catalogue from the context menu. The Open dialog box appears.
5. Select the DBF path loss tuning catalogue file you want to import.
6. 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.
Directory: Specify a directory where exported path loss matrices will be stored 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: ";").
) to represent the
If a transmitter was already selected on the map, a line appears connecting the selected transmitter and the receiver.
201
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 "Views of the Point Analysis Tool" on page 202.
) is available in the Point Analysis tool for CDMA and UMTS projects.
The AS Analysis view displays information on the pilot quality (EcI0), which is the main parameter used to define the
mobile active set, the connection status, and the active set of the probe mobile.
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 of the Point Analysis tool gives you information on reception for any point on the map where
there is scrambling code collision.
202
AT332_UMR_E0
The Details view displays the current position and height of the receiver, the clutter class it is located 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.
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.
) represents the receiver in the map window. You can change the position
2. Select Coordinates from the context menu. The Receiver Position dialog box appears.
3. Enter 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 (
tion dialog box appears.
) in the map window and select Centre on a Site from the context menu. The Site Selec-
2. 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 and the map window is centred on the receiver.
) in the Point Analysis window. The map window is centred on the receiver.
) at the top of the Point Analysis view. The Calculation Options dialog box appears.
2. Select the Indoor Coverage check box to add indoor losses to the total path loss.
203
) at the top of the Point Analysis view. The Calculation Options dialog box appears.
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.
Copying
Atoll also offers technology-specific coverage predictions, described in the technology-specific chapters, for example:
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 tip text. Furthermore, Atoll also allows you to filter, sort, or group results before displaying them.
This section covers the following topics:
204
AT332_UMR_E0
2. Select a coverage prediction from the Prediction Types dialog box and click OK. The coverage prediction Properties
dialog box appears.
The Properties dialog box for a coverage prediction common to all technologies has three tabs:
General tab: You can rename the coverage prediction, define the coverage resolution, and add comments. A readonly Unique ID is generated for each coverage prediction at creation time.
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.
To calculate indoor coverage, select the Indoor Coverage option. The indoor losses defined for the clutter classes
will be added to the total path loss for each pixel. Indoor losses are defined per clutter class. You can define a default indoor losses value for all clutter classes or you can define different indoor losses for each clutter class, to
take the characteristics of each clutter class into consideration.
To include shadowing calculation into the prediction, select Take shadowing into account and define the Cell Edge
Coverage Probability. Shadowing, or slow fading, is signal loss along a path that is caused by obstructions not
taken into consideration by the propagation model. Display tab: You can define how coverage prediction results
will be displayed.
3. 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 (
For more information on calculating coverage predictions, see "Calculating Coverage Predictions" on page 206.
You can create child folders in the Predictions folder by right-clicking the Predictions folder
and selecting New Folder. You can organise your predictions by dragging and dropping
them into these folders.
205
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.
A new read-only Unique ID is generated for the cloned coverage prediction.
206
AT332_UMR_E0
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.
After calculation, the results are displayed in the map window, if the coverage predictions visibility check box has
been selected.
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.
207
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.
Unlocked coverage predictions are displayed in the Predictions folder with the unlocked icon (
Locked coverage predictions are displayed in the Predictions folder with the locked icon ( ).
You can reverse this default behaviour by setting the CalculationResults option to
0 in the [Studies] section of the Atoll.ini file. CalculationResults setting changes
only impact new documents created after changing the setting and restarting
Atoll.
Once a new document is saved, the status of the Store prediction numerical
results check box is frozen and CalculationResults setting changes have no effect.
At this point, you can only manually select/clear the status of this check box.
If a prediction is calculated in a new unsaved document, the numerical prediction
results will not be saved even if the Store prediction numerical results is selected.
When the Store prediction numerical results check box is selected, the coverage prediction numerical results are stored in
BIL format outside the ATL file for the coverage predictions calculated by value intervals with the relevant Field setting (i.e. a
field calculated by the coverage prediction and not a value taken from the database), in the following folder:
C:\<ATL_path>\<ATL_name>.studies\{<GUID>}
Where "<GUID>" is a read-only Unique ID generated for each coverage prediction when it is created (see General tab in the
predictions Properties dialog box). This ID is written to the corresponding XML file, between "<GUID>" and "</GUID>" tags.
The string combining the above path and the longest file name must not exceed 260 characters.
Until you save your ATL document, the following path (including a temporary "\~" folder) is used instead of the above path:
C:\<ATL_path>\<ATL_name>.studies\~\{<GUID>}
When they exist, these externally stored numerical results spare you the need to recalculate a coverage prediction when the
legend is modified and they provide you with a numerical difference feature between basic predictions.
The storage of numerical results may require additional disk space when your document
contains several coverage predictions and transmitters, and/or when high resolutions are
used. If you have limited disk space, you can disable this feature by adding an option in the
Atoll.ini file.
The "{<GUID>}" folder always contains at least one XML file, one BIL file, and one HDR file.
208
AT332_UMR_E0
For example, when a Coverage by Transmitter (DL) prediction is calculated by "Value Intervals" with Field set to "Number of
Servers", the following files are created:
<prediction_name>.XML
<prediction_name>.BIL
<prediction_name>.HDR
If you delete in Atoll all the coverage predictions calculated by "Value intervals"
and save the document, the entire "<ATL_name>.studies" folder corresponding to
this document will be deleted.
If you delete in Atoll one of several coverage predictions calculated by " Value
intervals", the corresponding "{<GUID>}" folder will be deleted automatically
without the need for saving the document.
Except for the GUID, the externally stored coverage predictions results can be imported as customised coverage predictions.
For more information on importing customised coverage predictions, see "Saving Defined Coverage Predictions" on page 209.
"Per Transmitter" Coverage Predictions
Some coverage predictions are calculated on a "per transmitter" basis. In this case, a BIL file and the associated HDR file are
generated for each transmitter, and a DBF file is created with a reference to each transmitters HDR and BIL results files.
For example, when a Coverage by Transmitter (DL) prediction is calculated by "Value Intervals" with Field set to "DL Path Loss
(dB)", the following files are created:
<prediction_name>.XML
<transmitter_name>.BIL (one BIL file per transmitter)
<transmitter_name>.HDR (one HDR file per transmitter)
<prediction_name>.DBF
<prediction_name>.XML
<prediction_name>.BIL
<prediction_name>.HDR
<prediction_name>.SVR.BIL
<prediction_name>.SVR.HDR
<prediction_name>.SVR.MNU
209
2. 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. If you have other XML template files, you can click the Customised
Predictions button and select it in the Open dialog box.
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.
Supported raster formats: BIL, BMP, PNG, JPEG, TIFF, TXT, ArcView grid, and Vertical Mapper GRD and GRC.
Supported vector formats: ArcView SHP, MapInfo MIF and TAB, and AGD.
You can export coverage predictions one by one or several coverage predictions at the same time.
In this section, the following are explained:
3. Display the coverage prediction that you want to export on the map. For information on displaying objects in the map
window, see "Displaying or Hiding Objects on the Map" on page 50.
4. Right-click the coverage prediction that you want to export. The context menu appears.
5. Select Export the Coverage. The Save As dialog box appears.
6. Select a destination folder, enter a File name, and choose a vector format in the Save as type list.
7. Click Save. If you selected the AGD format, the coverage prediction results are immediately exported. If you selected
any other format, the Vector Export dialog box appears. In the Vector Export dialog box, select the following export
options:
210
Coordinate systems: The coverage prediction is exported using the Display coordinate system of the document.
If you want to export the coverage prediction using a different coordinate system, click Change and select the
coordinate system to use for the export.
Resolution: You can change the export resolution of the coverage prediction.
Filtering: Select the level of filtering to use for the export. For more information on how filtering works, see the
Technical Reference Guide.
Smoothing: Select the level of smoothing to use for the export either as Percentage or absolute value of the Maximum number of points.
AT332_UMR_E0
3. Display the coverage prediction that you want to export on the map. For information on displaying objects in the map
window, see "Displaying or Hiding Objects on the Map" on page 50.
4. Right-click the coverage prediction that you want to export. The context menu appears.
5. Select Export the Coverage. The Save As dialog box appears.
6. Select a destination folder, enter a File name, and choose a raster format in the Save as type list.
7. Click Save. The Raster Export dialog box appears. The Raster Export dialog box contains different export options
according to the raster export format selected in the Save as type list.
For "BIL Files (*.bil)" and "Vertical Mapper Files (*.grd, *.grc)" formats, select:
Region: The geographic region within which the coverage prediction results are to be exported. You can select the
Entire project area, the Computation zone, or the Geographic export zone.
Data to export: The data that you want to be exported. Select Pixel values to export the actual predicted values
for each pixel, or Coverage thresholds to export the values corresponding to the display thresholds defined for
the coverage prediction.
Filtering: If you choose to export Coverage thresholds, select the level of filtering to use for the export. For more
information on how filtering works, see the Technical Reference Guide.
The "Text Files (*.txt)" raster format allows you to export the actual predicted values for each pixel. This format is
available if the prediction was calculated with the Store prediction numerical results check box selected in the Predictions Properties dialog box. For "Text Files (*.txt)" format, select:
Format: The syntax for storing coverage prediction data values in the text file. Enter the Number of decimal digits
to define the precision of the exported values, select the Separator to use, and select the Use one line per server
check box to export values for a server in one line.
Region: The geographic region within which the coverage prediction results are to be exported. You can select the
Entire project area, the Computation zone, or the Geographic export zone.
The coverage prediction is exported using the Display coordinate system of the document.
If you want to export the coverage prediction using the Projection coordinate system, you
can set the CoordSystemForTextExportIsProjection option in the [Studies] section of the
Atoll.ini file. For more information, see the Administrator Manual.
All other raster formats allow you to export the values corresponding to the display thresholds defined for the coverage prediction. For other raster formats, select:
Region: The geographic region within which the coverage prediction results are to be exported. You can select the
Entire project area, the Computation zone, or the Geographic export zone.
Filtering: Select the level of filtering to use for the export. For more information on how filtering works, see the
Technical Reference Guide.
211
4. Under Select predictions to export, select the check boxes corresponding to the coverage predictions you want to
export. By default, the predictions visible on the map are already selected. The list also displays the coverage prediction calculation resolution, whether the prediction is of vector or raster format, and whether actual numerical values
of calculation results are available.
5. Under Options, select the following export options:
Directory: Enter the location where exported coverage predictions will be stored. You can click the Browse button
(
) and select a location in the Select Folder dialog box that appears.
Format: Select the format in which you want Atoll to export the coverage predictions.
Overwrite existing predictions: Select this check box to overwrite any existing coverage predictions in the same
location.
Timestamp: Select this check box if you want to add the date and time information to the file names of exported
coverage predictions. This check box is only available when Overwrite existing predictions is cleared.
Resolution: Enter the resolution for the exported coverage predictions.
212
AT332_UMR_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 load a configuration that you have saved previously and apply it to the current report:
a. Under Configuration, click the Load button. The Open dialog box 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 dialog box appears.
b. In the Save As dialog box, browse to the folder where you want to save the configuration and enter a File name.
4. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialog
box. 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 move it up or
213
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, and so on) or density data (revenue/km, number of customer/km, and so on). Data is
considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example, sociodemographic classes, rain zones, and so on. For information on integrable data in custom data maps, see "Integrable versus
Non-integrable Data" on page 136.
You can click a point on the diagram to display the values of the Y-axis against the coverage criterion along the Xaxis. The corresponding cell is highlighted in the legend table.
You can also zoom in the graph by selecting several contiguous cells. Select a cell to return to the default view.
You can copy the graph to the clipboard for use in an external program by clicking Copy ( ).
You can print the graph by clicking Print ( ).
2. Click Histogram (
function.
3. Click Values ( ) to display the covered area values along the Y-axis or Percentage ( ) to display the percentage of
the covered area along the Y-axis.
4. To specify a custom scale for the Y-axis, enter values in Min Y and Max Y and click OK (
ingly. Click Default ( ) to return to the default scale.
5. By default, "<No zone>" is selected in the Zone list, which means that the statistics are displayed for every site that
has been calculated. To filter the statistics according to a specific zone that contains a specific number of sites, select
a zone from the Zone list.
All zones defined in the Zones folder of the Geo explorer can be selected (computation zone, focus zone, hot spots,
and so on).
6. To compare with another prediction, select the Compare with check box and select the prediction.
You can select only predictions with the same shading options (same interval number and same maximum and minimum values).
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.
214
AT332_UMR_E0
Intersection: This display shows the area where both coverage predictions overlap (for example, pixels covered by
both predictions are displayed in red).
Merge: This display shows the area that is covered by either of the coverage predictions (for example, pixels covered
by at least one of the 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).
Value Difference: This display shows the dB difference between any two coverage predictions by signal level. This display option will not be available if the coverage predictions were calculated using different resolutions.
215
Figure 4.18: 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 dialog box 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.
216
AT332_UMR_E0
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
Merge
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 4.19, shows clearly the area covered only by the new
base station.
217
Intersection
Merge
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 4.22, shows clearly the increase in coverage due to the
change in antenna tilt.
218
AT332_UMR_E0
The slideshow feature can also be used with simulations. For more information, see
"Displaying Simulations as a Slideshow" on page 271.
If the simulation slideshow is started while the prediction slideshow is running, the prediction slideshow stops automatically. Likewise, if the prediction slideshow is started while
the simulation slideshow is running, the simulation slideshow stops.
To start the prediction slideshow:
1. Select the Network explorer.
2. Right-click the Predictions folder (or a prediction group folder). The context menu appears.
3. Select Start Slideshow from the context menu. The Slideshow dialog box appears.
All coverage predictions in the Predictions folder (or in the prediction group folder) are displayed one after the other
on the map. As the display cycles, the visibility check box of the corresponding coverage prediction is selected in the
Network explorer.
To change the speed of the slideshow, click inside the Duration field in the Slideshow dialog box and type the delay
between coverage predictions (in milliseconds). The speed of the slideshow changes dynamically.
To stop the slideshow from the Network explorer, click Stop Slideshow (
219
220
Chapter 5
Neighbour
Planning
This chapter provides
information on using
Atoll to plan intra- and intertechnology neighbours in
single-RAT and multi-RAT
networks..
222
AT332_UMR_E0
5 Neighbour Planning
Cell neighbour lists are necessary to ensure handovers between base stations. You can use Atoll to automatically allocate
neighbour relationships between cells. The cell to which a neighbour relation is allocated is referred to as the reference cell.
The cells that fulfil the requirements to be neighbours are referred to as potential neighbours.
The automatic allocation process allows you to manually declare exceptional pairs. These are particular neighbour relationships that are declared to be either forced or forbidden and therefore are not modified by the automatic neighbour allocation
process. Exceptional pair relationships can be either symmetrical or assymetrical.
Atoll manages neighbour relationships in both single-RAT and multi-RAT documents by using the following concepts:
Intra-technology neighbours are cells defined as neighbours that use the same radio technology as the reference cell.
In single-RAT documents, only Intra-technology neighbours are supported.
Inter-technology neighbours are cells defined as neighbours that use a different radio technology. Inter-technology
neighbours are available in co-planning environments (where two single-RAT documents are linked) and multi-RAT
documents.
Typically, you allocate neighbour relationships globally at the beginning of a radio planning project. Later, you can allocate
neighbour relationships to cells as you add them. You can use automatic allocation on all cells in the document, or you can
define a group of cells either by using a focus zone or by grouping cells in the explorer window. For information on creating a
focus zone, see "Focus Zone and Hot Spots" on page 68. For information on grouping cells in the explorer window, see "Grouping Data Objects" on page 94.
This chapter covers the following topics:
Forced neighbours: The selected cell will always be a neighbour of the reference cell.
Forbidden neighbours: The selected cell will never be a neighbour of the reference cell.
Intra-technology: You can define exceptional pairs for transmitters that use the same radio technology.
Inter-technology in a co-planning environment: You can define exceptional pairs for transmitters that use a different
radio technology between two single-RAT documents.
Inter-technology in a multi-RAT environment: You can define exceptional pairs for transmitters that use a different
radio technology in a multi-RAT document.
To define exceptional pairs in the same technology, select Neighbours > Intra-Technology > Open Exceptional
Pairs Table.
To define exceptional pairs between multiple technologies in a co-planning environment, select Neighbours >
Inter-Technology > Open Exceptional Pairs Table.
To define exceptional pairs between multiple technologies in a multi-RAT environment, select Neighbours >
<technology> > Open Exceptional Pairs Table.
223
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.
).
).
4. Select a cell to show its forced or forbidden neighbour relations on the map.
LTE: Depending on the best server selection method defined in the network settings, the automatic allocation of neighbour relations can be based on coverage
areas calculated for best servers based on the reference signal levels or RSRP.
WiMAX: Depending on the best server selection method defined in the network
settings, the automatic allocation of neighbour relations can be based on coverage
areas calculated for best servers based on the preamble C or preamble C/(I+N).
TD-SCDMA: For N-frequency mode compatible cells, neighbour relations are only
stored for master carriers. A slave carrier has the same neighbour relations as its
master carrier. Neighbour relations are not allocated to standalone carriers (nonN-frequency mode compatible).
UMTS: You can prevent Atoll from allocating inter-technology neighbours to UMTS
cells located on sites whose equipment do not support the compressed mode. by
adding the CompressModeEval option in the [Neighbours] section of the Atoll.ini
file. For more information, see the Administrator Manual.
When allocating neighbour relationships to all active and filtered cells, Atoll allocates neighbour relations only to the cells
within the focus zone and considers as potential neighbours all the active and filtered cells whose propagation zone intersects
the rectangle containing the computation zone. If there is no focus zone, Atoll allocates neighbour relations 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 explorer is
selected.
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 104.
This section covers the following topics:
224
AT332_UMR_E0
Intra-technology: This tab allows you to configure the automatic allocation for transmitters that use the same radio
technology as the selected transmitter or group of transmitters.
Inter-technology: This tab allows you to configure the automatic allocation for transmitters that use a different radio
technology from the selected transmitter or group of transmitters in a co-planning or multi-RAT environment.
Max inter-site distance: Specify the maximum distance between the reference cell and a potential neighbour.
By default, the automatic neighbour allocation compares the defined Max intersite distance with the effective inter-cell distance. As a consequence, there can be
cases where the real distance between assigned neighbours is higher than the Max
inter-site distance, because the effective distance is smaller.
If you want Atoll to compare the Max inter-site distance with the real inter-site
distance, set the RealInterSiteDistanceCondition option in the [Neighbours]
section of the Atoll.ini file. For more information, see the Administrator Manual.
You can consider repeaters and remote antennas in the maximum inter-site distance by setting the RepeaterInterSiteDistanceInAlloc option in the [Neighbours]
section of the Atoll.ini file. For more information, see the Administrator Manual.
Max no. of neighbours: Specify the maximum number of intra-technology or inter-technology neighbour relations
that can be allocated to a cell. This value can be either set here for all the cells, or specified for each cell separately in
their specific properties.
Carriers to allocate (for UMTS and CDMA2000 only):
On the Intra-carrier Neighbours tab, select the carriers on which you want to run the allocation. Atoll will allocate neighbour relations only to the cells using the selected carriers.
On the Inter-carrier Neighbours tab, select Source and Destination carriers. Atoll will allocate neighbour relations to the cells using the carriers defined next Source. Potential neighbours can be the cells using the carriers
defined beside Destination.
Use coverage conditions: Select this option to specify the coverage conditions.
When this option is selected, click Define to open the Coverage Conditions dialog box and change the parameters.
Coverage conditions are specific to each radio technology:
When Use coverage conditions is not selected, only the distance criterion is considered between neighbours and
reference cells.
% min covered area: Enter the smallest percentage of the reference cell coverage area that the coverage area of a
potential neighbour must overlap.
Force: Specify the calculation constraints. Calculation constraints are specific to each radio technology.
GSM: see "Calculation Constraints" on page 323
UMTS: see "Calculation Constraints" on page 561
CDMA: see "Calculation Constraints" on page 676
LTE: see "Calculation Constraints" on page 905
WiMAX: see "Calculation Constraints" on page 1084
Wi-Fi: see "Calculation Constraints" on page 1200
TD-SCDMA: see "Calculation Constraints" on page 788
Delete existing neighbours: Enable this option to delete all existing neighbour relations prior to automatic allocation.
When this option is disabled, existing neighbour relations are not deleted and Atoll only adds new neighbour relations
to the list.
225
Results table
After clicking Calculate, the Results table contains the following information:
Cause: Reason why Atoll has allocated the potential neighbour shown under Neighbour to the reference cell shown
on the same row under Transmitter or Cell. Possible causes depend on the technology:
Relation type (except GSM): Specify the type of neighbour relationship with respect to centre frequencies. The cells
that have channels with identical centre frequencies have an intra-carrier neighbour relation.
Coverage: Specify the amount of reference cell coverage area that the neighbour overlaps, in % and km.
Adjacency: Specify the area of the reference cell, in % and km, where the neighbour is best or second best server.
Commit: Select the option in this column to specify, for each potential neighbour, whether it should be committed.
The Results table is empty if the Deleting existing neighbours option is disabled and no
new potential neighbours are found.
To allocate single-RAT neighbours, select Neighbours > Intra-technology > Automatic Allocation.
To allocate neighbours that use a different radio-technology in a co-planning environment, select Neighbours >
Inter-technology > Automatic Allocation.
To allocate multi-RAT neighbours, select Neighbours > <technology> > Automatic Allocation.
The Automatic Neighbour Allocation dialog box appears with one or two tabs, according to the technology:
2. Define the automatic allocation settings as specified in "Automatic Neighbour Allocation Window" on page 225.
3. Click Calculate. The Event Viewer window appears and displays the progress of the neighbour allocation process.
During the calculation, the validity of path loss matrices for each neighbour is checked. If the matrices are not valid,
they are recalculated.
226
AT332_UMR_E0
4. When the calculation is finished, close the Event Viewer window. The Results table displays all neighbour candidates
for each cell.
If the Delete existing neighbours option is disabled and no new potential neighbours are found, then the list is empty.
Forbidden neighbours are not listed as neighbour candidates unless the neighbour
relation already exists and the Delete existing neighbours check box is cleared
when you start the new allocation.
When Exceptional pairs and Symmetric relations options are selected, the constraints between exceptional pairs are considered in both directions to respect the
symmetry. However, if the neighbour relation is forced in one direction and forbidden in the other, the symmetry cannot be respected.
For more information on the Results table, see "Automatic Neighbour Allocation Window" on page 225.
5. In the Results table, select the Commit box for each potential neighbour that you want to commit.
6. If necessary, click the Compare button to compare the list of potential neighbours proposed by Atoll with the list of
existing neighbours. A report is generated in the NeighboursDeltaReport.txt file and is displayed automatically.
The NeighboursDeltaReport.txt file lists the following:
7. Click Commit. The list of intra-technology neighbour relations for all cells in the Transmitters folder is updated.
To check the new neighbour relationships in the Neighbours table, right-click the Transmitters folder, and select
Neighbours > Intra-technology > Open Table or Neighbours > Inter-technology > Open Table.
To allocate single-RAT neighbours, select Neighbours > Intra-technology > Automatic Allocation.
To allocate single-RAT neighbours in a co-planning environment, select Neighbours > Inter-technology > Automatic Allocation.
To allocate multi-RAT neighbours, select Neighbours > <technology> > Automatic Allocation.
The Automatic Neighbour Allocation dialog box appears with one or two tabs, according to the technology.
3. Define the automatic allocation settings as specified in "Automatic Neighbour Allocation Window" on page 225 and
follow the steps described in "Automatically Allocating Neighbours to Multiple Cells" on page 226.
To check the new neighbour relationships in the Neighbours table, right-click the Transmitters folder, and select
Neighbours > Intra-technology > Open Table or Neighbours > Inter-technology > Open Table.
To allocate single-RAT neighbours, select Neighbours > Intra-technology > Automatic Allocation.
To allocate single-RAT neighbours in a co-planning environment, select Neighbours > Inter-technology > Automatic Allocation.
To allocate multi-RAT neighbours, select Neighbours > <technology> > Automatic Allocation.
The Automatic Neighbour Allocation dialog box appears with one or two tabs, according to the technology:
227
2. Define the automatic allocation settings as specified in "Automatic Neighbour Allocation Window" on page 225 and
follow the steps described in "Automatically Allocating Neighbours to Multiple Cells" on page 226.
To check the new neighbour relationships in the Neighbours table, right-click the Transmitters folder, and select
Neighbours > Intra-technology > Open Table or Neighbours > Inter-technology > Open Table.
GSM: Select Open Table. The Transmitters table appears with the cell names listed under Transmitter.
Other technologies: Select Cells > Open Table. The Cells table appears with the cell names listed under Name.
2. Double-click anywhere in the row containing the cell that you want to edit. The Properties dialog box for the corresponding cell appears.
3. Select the Intra-technology Neighbours or Inter-technology Neighbours tab. The existing neighbour relations appear
under List.
4. Click Edit. The List table can be edited.
5. To create a neighbour relationship:
a. In the List table, on the row containing the New Row icon (
icon ( ) appears on the right-hand side of the cell.
b. Click the arrow icon ( ) and select the cell that you want to define as a new neighbour.
c. Click inside another row to finish allocating the new neighbour. The distance from the neighbour to the reference
cell is indicated under Distance, Source is set to "manual", and neighbour Importance is set to "1".
6. To make neighbour relationship symmetrical:
a. In the List table, click in the left margin of the row containing a neighbour to select the row.
b. Right-click anywhere in the selected row and select Make Symmetrical from the context menu.
c. Click Apply. The corresponding check box under Symmetry is selected.
7. To delete a symmetric neighbour relationship:
a. In the List table, click in the left margin of the row containing a neighbour to select the row.
b. Right-click anywhere in the selected row and select Delete Symmetric Relation from the context menu.
c. Click Apply. The corresponding check box under Symmetry is cleared.
8. To delete a neighbour relationship:
a. In the List table, click in the left margin of the row containing a neighbour to select the row.
b. Right-click anywhere on the selected row and select Delete Link. The neighbour link is deleted from the List table.
9. Optionally, you can specify:
UMTS/CDMA: the Max number of intra-carrier and inter-carrier neighbours that can be allocated.
Other: the Max number of neighbours that can be allocated.
228
AT332_UMR_E0
To allocate single-RAT neighbours, select Neighbours > Intra-technology > Open Table.
To allocate single-RAT neighbours in a co-planning environment, select Neighbours > Inter-technology > Open
Table.
To allocate multi-RAT neighbours, select Neighbours > <technology> > Open Table.
b. Click the arrow icon ( ) and select the reference cell in the drop-down list.
c. On the same row, click inside the cell under Neighbour. An arrow icon ( ) appears on the right-hand side of the
cell.
d. Click the arrow icon ( ) and select the cell that you want to define as a neighbour.
e. Click in any other row to finish creating the new neighbour relation. As a result, Atoll adds the distance from the
neighbour to the reference cell under Distance, sets Source to "manual", and neighbour Importance to "1".
3. To delete neighbour relationships, select one or several rows in the table, right-click anywhere in the Neighbours table
and select Delete Link from the context menu. The neighbour relationship is deleted.
4. To create or delete symmetric neighbour relationships, select one or several rows in the table, right-click anywhere in
the Neighbours table and select Make Symmetrical or Delete Symmetric Relation from the context menu. The Symmetry check boxes for the selected neighbours are changed accordingly.
5. To take all exceptional pairs into account, right-click anywhere in the Neighbours table and select Force Exceptional
Pairs from the context menu.
).
3. Click the reference cell on the map. Its neighbour relationships are displayed.
4. To create a symmetric neighbour relationship, press Shift and click the target cell. The symmetric relationship is added
in the neighbours lists of both cells. Press Shift and click the target cell again to delete the relationship.
5. To create an outward neighbour relationship, press Ctrl and click the target cell. The neighbour relationship is added
in the neighbours list of the reference cell. Press Ctrl and click the target cell again to delete the relationship.
6. To create an inward neighbour relationship, press Shift and click the target cell to create a symmetric relationship, and
then press Ctrl and click the target cell. The symmetric relation is converted into an inward non-symmetric relation.
Press Shift and click the target cell again to delete the relationship.
229
Intra-technology: This tab allows you to evaluate neighbour importance for transmitters that use the same radio technology as the selected transmitter or group of transmitters.
Inter-technology: This tab allows you to evaluate neighbour importance for transmitters that use a different radio
technology from the selected transmitter or group of transmitters in a co-planning or multi-RAT environment.
Max inter-site distance: Maximum distance between the reference cell and a potential neighbour.
By default, the automatic neighbour allocation compares the defined Max intersite distance with the effective inter-cell distance. As a consequence, there can be
cases where the real distance between assigned neighbours is higher than the Max
inter-site distance, because the effective distance is smaller.
If you want Atoll to compare the Max inter-site distance with the real inter-site
distance, set the RealInterSiteDistanceCondition option in the [Neighbours]
section of the Atoll.ini file. For more information, see the Administrator Manual.
You can consider repeaters and remote antennas in the maximum inter-site distance by setting the RepeaterInterSiteDistanceInAlloc option in the [Neighbours]
section of the Atoll.ini file. For more information, see the Administrator Manual.
Take co-site factor into account: Select this option to verify that neighbours are located on the same site as their reference cell when calculating importance. If a transmitter has no antenna, it cannot be considered as a co-site neighbour.
Take cell adjacency into account (except GSM and Inter-carrier Neighbours tab in UMTS/CDMA): Select this option
to verify that neighbours are adjacent to their reference cell when calculating the neighbour importance.
Take HCS layer adjacency into account (GSM only): Select this option to verify that neighbours on other HCS layers
are adjacent to their reference cell when calculating neighbour importance.
Take layer adjacency into account (except GSM and TD-SCDMA): Select this option to verify that neighbours on other
layers are adjacent to their reference cell when calculating neighbour importance.
Filter: Click this button to open the Filter dialog box and define advanced filtering conditions to restrict the neighbours
to be calculated. The corresponding number of neighbours is indicated in the field beside the Filter button.
Use coverage conditions: Select this option to specify the coverage conditions.
When this option is selected, click Define to open the Coverage Conditions dialog box and change the parameters.
Coverage conditions are specific to each radio technology:
When Use coverage conditions is not selected, only the distance criterion is considered between neighbours and
reference cells.
Results table
After clicking Calculate, the Results table contains the following information:
Importance (%): The neighbour importance calculated with the specified importance factors. For more information,
see "Configuring Neighbour Importance Factors" on page 231
Cause: The reason why Atoll has allocated the value under Importance (%), according to the weights defined in the
corresponding Neighbour Importance Weighting dialog box. Possible causes depend on the technology:
230
AT332_UMR_E0
To configure the importance of single-RAT neighbours, select Neighbours > Intra-technology > Configure Importance.
To configure the importance of neighbours that use a different radio-technology in a co-planning environment,
select Neighbours > Inter-technology > Configure Importance.
To configure the importance of multi-RAT neighbours, select Neighbours > <technology> > Configure Importance.
The Neighbour Importance Weighting dialog box appears with one or two tabs, according to the technology:
Distance Factor: Set the Min and Max importance of a potential neighbour cell being located within the maximum
distance from the reference cell.
Coverage Factor: Set the Min and Max importance of a neighbour being admitted for coverage reasons.
Adjacency factor: Set the Min and Max importance of a potential neighbour cell being adjacent to the reference
cell. The Adjacency factor will be used when the following check boxes are selected in the Automatic Neighbour
Allocation dialog box:
GSM: Adjacent neighbours and Adjacent HCS layer neighbours
UMTS/CDMA/LTE: Adjacent cells as neighbours and Adjacent layers as neighbours
Other: Adjacent cells as neighbours
Adjacent neighbours are geographically adjacent cells based on their Best Server
coverages. Cell A is considered adjacent to cell B if there exists at least one pixel of
cell As Best Server coverage area where cell B is 2nd Best Server. The ranking of
the adjacent neighbour cell increases with the number of these pixels.
Cells are considered adjacent across layers if they belong to different layers and
have a coverage overlap of at least one pixel.
Co-site factor: Set the Min and Max importance of a potential neighbour cell being located on the same site as
the reference cell. The defined Co-site factor will not be taken into account when the following check box is
cleared in the Automatic Neighbour Allocation dialog box:
GSM: Co-site transmitters as neighbours
Other: Co-site cells as neighbours
3. Click OK to save your settings and close the Neighbour Importance Weighting dialog box.
To calculate the importance of single-RAT neighbours, select Neighbours > Intra-technology > Calculate Importance.
To calculate the importance of neighbours that use a different radio-technology in a co-planning environment,
select Neighbours > Inter-technology > Calculate Importance.
To calculate the importance of multi-RAT neighbours, select Neighbours > <technology> > Calculate Importance.
The Neighbour Importance Evaluation dialog box appears with one or two tabs, according to the technology:
231
2. Define the automatic allocation settings as specified in "Neighbour Importance Evaluation Window" on page 230.
3. Click Calculate. The Event Viewer window appears and displays the progress of the neighbour allocation process..
During the calculation, the validity of path loss matrices for each neighbour is checked. If the matrices are not valid,
they are recalculated.
4. Click Close in the Events viewer. The following values appear in the Neighbour Importance Evaluation dialog box:
5. Click Commit to commit these importance values and the reasons for neighbour allocation to the Neighbours table.
2. Under Links, select Display intra-technology links to display neighbour relationships that use the radio-technology of
the current document, and click Browse (
) to specify how neighbour relationships are displayed. The Neighbour
Display Settings dialog box appears.
a. From the Display Type list, select a display type:
Select Unique to colour the neighbour links of the selected cell with a unique colour.
Select Discrete values to colour the neighbour links of the selected cell according to:
- The colour of the source or target cell when Field is set to "Transmitter", "Cell", or "Neighbour"
- The relevant value in the table when Field is set to "Reason", "Source", "Neighbour.CellType" (GSM), "Neighbour.HCSLayer" (GSM), "Neighbour.FrequencyBand" (GSM/LTE/WiMAX/Wi-Fi), "Neighbour.Carrier" (UMTS/
CDMA/TD-SCDMA), or "Relation Type" (UMTS/CDMA/LTE/WiMAX/Wi-Fi)
Select Value Intervals to colour the neighbour links of the selected cell according to the "Importance" weights
defined in the corresponding Neighbour Importance Weighting dialog box.
You can display the number of handoff attempts for each cell-neighbour pair by creating a
new field of 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 when Display type is set to "Value Intervals". For
information on adding a new field to a table, see "Adding a Field to a Data Table" on
page 77.
b. If necessary, you can disable the display of the neighbour link types you want by clearing the corresponding visibility check boxes in the rightmost column.
c. Click the Browse button beside Tip text and select the characteristics to be displayed as tip text on neighbour links.
d. Click OK to save your settings and close the Neighbour Display Settings dialog box.
3. If you are in a co-planning environment, where a single-RAT document is linked to one or several other single-RAT documents, select Display inter-technology links to display neighbour relationships that use the radio-technologies of
linked co-planning documents.
232
AT332_UMR_E0
There are no display settings for inter-technology neighbours links in Co-planning. The
links appear on the map as dashed lines.
4. Under Coverages, select Highlight coverage areas to display the coverage areas of neighbours and click Browse to
specify how coverage areas are displayed. The Neighbour Display Settings dialog box appears.
a. From the Display type list, select a display type:
Unique: Select this option to colour the intra-technology coverage areas of the selected cells neighbours with
a unique colour and the coverage area of the source cell in yellow.
Figure 5.2: Example of intra-technology neighbour coverage (Display type: "Unique" with "Filter on neighbourhood")
Discrete values: Select this option to colour the intra-technology coverage areas of the selected cells neighbours according to:
- the colour of the source or target cell when Field is set to "Transmitter", "Cell", or "Neighbour"
- the relevant value in the table when Field is set to "Reason", "Source", or "Relation Type" (UMTS/CDMA/LTE/
WiMAX/Wi-Fi)
Figure 5.3: Example of intra-technology neighbour coverage (Display type: "Discrete values", Field: "Neighbour")
Value Intervals: Select this option to colour the intra-technology coverage areas of the selected cells neighbours according to the "Importance" weights defined in the corresponding Neighbour Importance Weighting
dialog box.
b. Click the Browse button beside Tip text and select the characteristics to be displayed as tip text on coverage areas.
c. Click OK to save your settings and close the Neighbour Display Settings dialog box.
5. Under Coverages, select whether to Filter on neighbourhoods and whether to Display relevant coverage types only.
6. Select the neighbour relations that you want to display:
Select Display non-symmetrical outwards to display a neighbour link when the selected cell is the reference cell
and the neighbour relation is not symmetric.
Select Display non-symmetrical inwards to display a neighbour link when the selected cell is the neighbour and
the neighbour relation is not symmetric.
Select Display symmetrics to display a neighbour link when the reference cell or the neighbour is selected and the
neighbour relation is symmetric.
233
7. Select Adjust Map Window if you want the map window to self-adjust to display all the neighbour relations of the
selected cell.
8. In the Labels drop-down list, specify the cell labels to display when the Edit Relations on the Map button (
pressed:
) is
9. Click OK to save your settings and close the Neighbour Display dialog box.
2. Under Links, select Display links to display neighbour relationships, click the Menu ( ) button and select a technology from the context menu to specify how neighbour relationships are displayed for that technology.
The Neighbour Display Settings dialog box appears with a separate tab for each technology combination.
3. For the intra-technology neighbours and each of the other neighbour combinations, specify the display settings:
a. From the Display Type list, select a display type:
Select Unique to colour the neighbour links of the selected cell with a unique colour.
Select Discrete values to colour the intra-technology neighbour links of the selected cell according to:
- the colour of the source or target cell when Field is set to "Transmitter", "Cell", or "Neighbour
- the relevant value in the table when Field is set to "Reason", "Source", "Neighbour.CellType" (GSM), "Neighbour.HCSLayer" (GSM), "Neighbour.FrequencyBand" (GSM/LTE), "Neighbour.Carrier" (UMTS/CDMA), or
"Relation Type" (UMTS/CDMA/LTE)
Select Value Intervals to colour the neighbour links of the selected cell according to the "Importance" weights
defined in the corresponding Neighbour Importance Weighting dialog box.
You can display the number of handoff attempts for each cell-neighbour pair by creating a
new field of 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 when Display type is set to "Value Intervals". For
information on adding a new field to a table, see "Adding a Field to a Data Table" on
page 77.
b. If necessary, you can disable the display of the neighbour link types you want by clearing the corresponding visibility check boxes in the rightmost column.
c. Click the Browse button beside Tip text and select the characteristics to be displayed as tip text on neighbour links.
d. Click OK to save your settings and close the Neighbour Display Settings dialog box.
4. Under Coverages, select Highlight coverage areas to display the coverage areas of neighbours and click Browse to
specify how coverage areas are displayed. The Neighbour Display Settings dialog box appears.
a. From the Display type list, select a display type:
Unique: to colour the intra-technology coverage areas of neighbours of the selected cell with a unique colour
and the coverage area of the source cell in yellow.
Discrete values: to colour the intra-technology coverage areas of the neighbours of the selected cell according
to:
- the colour of the source or target cell when Field is set to "Transmitter", "Cell", or "Neighbour"
- the relevant value in the table when Field is set to "Reason", "Source", or "Relation Type" (UMTS/CDMA/LTE/
WiMAX/Wi-Fi)
Value Intervals: to colour the intra-technology coverage areas of the neighbours of the selected cell according
to the "Importance" weights defined in the corresponding Neighbour Importance Weighting dialog box.
b. Click the Browse button beside Tip text and select the characteristics to be displayed as tip text on coverage areas.
c. Click OK to save your settings and close the Neighbour Display Settings dialog box.
234
AT332_UMR_E0
5. Under Coverages, select whether to Filter on neighbourhoods and whether to Display relevant coverage types only.
6. Select the neighbour relations that you want to display:
Select Display non-symmetrical outwards to display a neighbour link when the selected cell is the reference cell
and the neighbour relation is not symmetric.
Select Display non-symmetrical inwards to display a neighbour link when the selected cell is the neighbour and
the neighbour relation is not symmetric.
Select Display symmetrics to display a neighbour link when the reference cell or the neighbour is selected and the
neighbour relation is symmetric.
7. Select Adjust Map Window if you want the map window to self-adjust to display all the neighbour relations of the
selected cell.
8. In the Labels drop-down list, specify the cell labels to display when the Edit Relations on the Map button (
pressed:
) is
9. Click OK to save your settings and close the Neighbour Display dialog box.
Figure 5.4: Single-RAT intra-technology neighbour links with a "Coverage by Transmitter (DL)" prediction
To display neighbour relationships and coverage on the map:
1. In the Radio Planning toolbar, click the arrow ( ) beside the Edit Relations on the Map button (
bours from the context menu.
2. Click the Edit Relations on the Map button (
).
3. If you want to display the neighbour coverage areas, in the Network explorer, select the visibility check box of the Predictions folder in the Networks explorer.
4. Select a cell by performing either of the following actions:
In the Network explorer, expand the Transmitters folder, and select a cell.
Select a cell in Map window. For Multi-RAT documents, when there is more than one cell on the transmitter,
clicking the transmitter in the map window opens a context menu for cell selection (see "Selecting One out of Several Transmitters" on page 57).
In the Neighbours table, select a cell by clicking the leftmost cell in the row.
The neighbours of the cell are displayed on the map. If a prediction is selected in the Predictions folder, the coverage
areas of the neighbours of the selected cell are displayed on the map. The selected cell is highlighted in the Neighbours table if it is open.
Atoll displays the following information for the selected cell:
Symmetric neighbour relations of the selected cell are indicated by a simple line.
Outward neighbour relations are indicated by a line with an arrow pointing towards the neighbour.
Inward neighbour relations are indicated by a line with an arrow pointing towards the reference cell.
235
Neighbour links are displayed in grey if no shading is defined for the Value assigned
to them in the Neighbour Display Settings dialog box and they are not displayed
at all if the check box corresponding to the assigned Value is cleared.
You can display forced or forbidden neighbours by clicking the arrow ( ) beside the
Edit Relations on the Map button ( ) then selecting Forced Neighbours or Forbidden Neighbours.
).
5. Select Display Options from the context menu. The Neighbour Display dialog box appears.
6. Select the Highlight coverage areas check box and click the Browse button beside it. The Neighbour Display Settings
dialog box appears.
7. Set Display type to "Unique" then click OK to close the Neighbour Display Settings dialog box.
8. Click OK in the Neighbour Display dialog box.
9. Select the visibility check box of the Predictions folder in the Networks explorer.
10. In the map, select the inter-technology neighbour cell that you identified at the beginning of this procedure. The area
displayed in yellow is the coverage area of the inter-technology neighbour cell.
Neighbour Type (UMTS/CDMA): Select this option to set the audit on Intra-Carrier or Inter-Carrier neighbour relations.
Average no. of neighbours: Select this option to verify the average number of neighbours per cell.
Empty lists: Select this option to verify which cells have no neighbours (an empty neighbour list).
Full lists: Select this option to verify which cells have 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 the cells,
or specified for each cell in the Cells table.
Lists > max number: Select this option to verify which cells have more than the maximum number of neighbours
allowed. The maximum number of neighbours can be either set here for all the cells, or specified for each cell in
the Cells table.
Missing co-sites: Select this option to verify which cells have no co-site neighbours.
Missing symmetrics: Select this option to verify which cells have non-symmetric neighbour relations.
Exceptional pairs: Select this option to verify which cells have forced neighbours or forbidden neighbours.
Distance between neighbours: Select and enter the maximum distance between neighbours.
Same BCCH (GSM): Select this option to verify which cells have the same BCCH.
3. Click OK to perform the audit. Atoll produces the results of the audit in a text file named "InterNeighboursCheck.txt",
which appears at the end of the audit.
236
Neighbours with the same BCCH: X; total number of neighbours having the same BCCH.
AT332_UMR_E0
Syntax:
Average number of neighbours: X; 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:
GSM: |TRANSMITTER|
Other: |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:
Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour allocation plan.
Syntax:
Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour allocation plan.
Syntax:
Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour allocation plan.
Syntax:
Missing Forced: X; total number of forced neighbours missing in the audited neighbour allocation plan.
Syntax:
Distance between neighbours > Y: X; total number of neighbours existing in the audited neighbour allocation plan
that are located at a distance greater than Y.
Syntax:
Intra-technology: You can import and export neighbours that use the same radio technology.
Inter-technology in a co-planning environment: You can import and export neighbours that use a different radio technology between two single-RAT documents.
Inter-technology in a multi-RAT environment: You can import and export neighbours that use a different radio technology in a multi-RAT document.
237
To import neighbours from the same radio technology, select Neighbours > Intra-technology > Open Table.
To import neighbours from a different technology in a co-planning environment, select Neighbours > Inter-technology > Open Table.
To import neighbours from a different technology in a multi-RAT environment, select Neighbours > <technology>
Open Table.
To export neighbours from the same radio technology, select Neighbours > Intra-technology > Open Table.
To export neighbours from a different technology in a co-planning environment, select Neighbours > Inter-technology > Open Table.
To export neighbours from a different technology in a multi-RAT environment, select Neighbours > <technology>
Open Table.
2. When the table appears, export it as described in "Exporting Tables to Text Files and Spreadsheets" on page 86.
238
Chapter 6
Network
Capacity
and Traffic
This chapter provides
information on studying
network capacity and
performing traffic
simulations in Atoll.
240
AT332_UMR_E0
For GSM traffic: the downlink and uplink traffic loads, the uplink noise rise, etc.
For UMTS traffic: 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.
For the CDMA part of the traffic: the active set for each mobile, the required power of the mobile, the total DL power,
and the UL load per cell
For LTE traffic: the downlink and uplink traffic loads, the uplink noise rise, the user throughputs, etc.
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.
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.
In this section, the following are explained:
Name: A default name is provided, but you can set a more descriptive name.
Activity factor: The uplink and downlink activity factors are used to determine the probability of activity for users
accessing the service during Monte Carlo simulations. For packet-switched services (data), this parameter is used
when working with sector traffic maps and user density traffic maps. For circuit-switched services (voice), the parameter is taken into consideration with any traffic map.
Average Requested Throughput: You can enter the average requested throughput for uplink and downlink. This
throughput is the average throughput obtained by a user of the service. How the average requested throughput is
used in Atoll depends on the type of service:
241
Circuit or All except Packet (HSPA): This throughput is the average throughput 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 throughput is the requested average throughput which guarantees a minimum average
throughput 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.
Technology priorities (for Multi-RAT documents only): Click the Browse button beside Technology priorities to open
a dialog box enabling you to define the technologies that can use this service and their priority.
Type: You can select either "Circuit", "Packet (Max Bit Rate)" or "Packet (Constant Bit Rate)" as the service type. If you
select "Circuit", the only other applicable parameter is Max probability of blocking (or delay) (Erlang B or C, respectively).
Priority: Enter a priority for this service. "0" is the lowest priority.
Max throughput demand: The maximum uplink and downlink throughputs per user is used in the simulation process
for GPRS/EDGE networks.
Min throughput demand: The minimum uplink throughput per user is used in the simulation process for GPRS/EDGE
networks. The minimum downlink throughput per user is used in both dimensioning and simulation processes for
GPRS/EDGE networks.
Max probability of blocking (or delay): The maximum blocking rate defines the call blocking or call queuing rate for
the GSM voice services and the probability of delayed packets for GPRS/EDGE data services.
Max packet delay: The maximum period of time that a packet can be delayed before transmission.
Required availability for minimum throughput: The percentage of cell coverage where the minimum throughput (or
the guaranteed bit rate for constant bit rate packet-switched services) per user must be available. This value is also
used in dimensioning.
Max number of timeslots per carrier: The maximum number of timeslots per carrier is used during dimensioning to
limit the number of timeslots that can be assigned to a user using this service on a carrier. This parameter applies to
packet-switched services. For constant bit rate packet-switched services such as VoIP, this parameter has to be set to
"1".
Application throughput: You can define the Scaling factor and the Offset. The throughput scaling factor and offset
are used to determine the user or application level throughput in Radio Link Control (RLC) throughput or timeslot coverage prediction. The application throughput is calculated by multiplying the RLC throughput by the scaling factor and
subtracting the offset. These parameters model header information and other supplementary data that do not appear
at the application level.
Type: Select either "Speech", "1xRTT Data", "1xEV-DO Rev. 0 Data", "1xEV-DO Rev. A Data" or "1xEV-DO Rev. B Data".
The options available depend on the type of service:
Speech: The following options are available for services with the type "Speech":
Activity Factor FCH: Enter an activity factor for the FCH on the uplink (reverse link) and on the downlink
(forward link). The activity factor can be from "0," indicating no activity during connection, to "1," indicating
constant activity during connection. The activity factor is used to calculate the average power transmitted on
the FCH.
1xRTT Data: The following options are available for services with the type "1xRTT Data":
SCH Throughput Probabilities: Enter the probability of the service having the specified throughput, from 2 to
16 times the peak throughput (defined in the terminal properties), on the uplink (reverse link) and on the
downlink (forward link). The sum of the probabilities must be lower than or equal to 1. The throughput probabilities are used during simulations to determine the throughput requested by each user.
1xEV-DO Rev. 0 Data: The following options are available for services with the type "1xEV-DO Rev. 0 Data":
Downgrading Supported: Select this option if the service supports downgrading on the reverse link.
UL Throughput Probabilities: Under UL Throughput Probabilities, you can enter the probability of the service
having the specified throughput on the reverse link. The sum of the probabilities of the service having the
specified throughput must be lower than or equal to 1. The throughput probabilities are used during simulations to determine the throughput requested by each user.
If the service supports throughput downgrading, you can define the probability of the service being upgraded
or downgraded on the uplink (reverse link) for each 1xEV-DO Rev. 0 throughputs. The probabilities are taken
into account during the uplink load control part of simulations in order to determine if a user with a certain
throughput can be upgraded or downgraded. User throughput downgrading and upgrading occurs when the
cell is over- or underloaded.
The following table shows the throughput changes that are possible when a throughput is upgraded or downgraded. The probabilities are defined with a number from 1 to 255 for each throughput.
242
AT332_UMR_E0
From
To
From
To
9.6 kbps
19.2 kbps
153.6 kbps
76.8 kbps
19.2 kbps
38.4 kbps
76.8 kbps
38.4 kbps
38.4 kbps
76.8 kbps
38.4 kbps
19.2 kbps
76.8 kbps
153.6 kbps
19.2 kbps
9.6 kbps
UL Throughput due to TCP acknowledgement: If the Transmission Control Protocol (TCP) is used on the downlink (forward link), check the TCP Used check box. When TCP is used, reverse link traffic due to acknowledgements is generated. The traffic generated is calculated using the graph which describes the reverse link traffic
due to TCP acknowledgements as a function of the forward link application throughput. The generated traffic
is taken into account in simulation during the reverse link power control.
1xEV-DO Rev. A Data and 1xEV-DO Rev. B Data: The following options are available for services with the type
"1xEV-DO Rev. A Data" and "1xEV-DO Rev. B Data".
QoS Class: Select "Guaranteed Bit Rate" for services that require a minimum bit rate or "Best Effort" for besteffort applications.
Uplink Mode: This setting escribes the type of radio resource management required on uplink for that service.
Select either "Low Latency" for real-time applications, or "High Capacity" for non-real-time applications
Downgrading Supported: Select this option if the service supports downgrading on the reverse link.
Min throughput demand: If you have selected "Guaranteed Bit Rate" as QoS class, enter the minimum
required bit rate in order for the service to be available in the uplink and downlink. This parameter is not available for best-effort applications.
UL Throughput Probabilities: Under UL Throughput Probabilities, you can enter the probability of the service
having the specified uplink throughput. This parameter is available for best-effort applications only.
In the column marked with the New Column icon ( ), select a Radio Bearer Index and enter a Usage Probability. Atoll automatically creates a new blank column. The sum of the probabilities must be lower than or
equal to 1. The throughput probabilities are used during simulations to determine the throughput requested
by each user. If the bearer is not defined under UL Throughput Probabilities, it is assumed that there are no
users using the bearer.
For services requiring a minimum bit rate, the usage probability is automatically calculated according to the
number of selected radio bearers.
UL Throughput Due to TCP Acknowledgement: Select TCP Used if the downlink (forward link) uses Transmission Control Protocol (TCP). When TCP is used, reverse link traffic due to acknowledgements is generated. The
traffic generated is calculated using the graph which describes the reverse link traffic due to TCP acknowledgements as a function of the forward link application throughput. The generated traffic is taken into account in
simulation during the reverse link power control.
Best-effort services with the 1xEV-DO Rev. B Data type can be provided in multi-carrier
mode if the server and the user terminal support it.
If you selected "Speech" or "1xRTT Data" as the Type, you must define each possible combination of terminal, SCH
factor, and mobility by clicking the EbNt button. On the EbNt dialog box, The SCH factor is the multiplying factor of
the terminal peak throughput used to calculate the throughput. The following table lists the SCH factors available and
the corresponding throughputs.
SCH Factor
Throughput
243
SCH Factor
Throughput
16
For each combination, you must define the thresholds, targets, and gains:
Preferred Carrier: Select the preferred carrier for the service. This is the carrier that will be used during simulations,
if the transmitter supports it. If the preferred carrier is not available, Atoll will choose another carrier using the carrier
selection mode defined in the site equipment properties.
Priority: Enter a priority for the service. A priority of "0" gives the lowest priority. The priority is used during simulations to decide which terminal will be rejected when the network is overloaded.
Soft Handoff Allowed: Select the Soft Handoff Allowed check box if this service can have a soft handoff.
Application Throughput: The application throughput is not used for services with the type Speech.
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.
R99 Radio Bearer: Select an R99 radio bearer from the list. You can click the Browse button to edit the properties of
the selected R99 radio bearer.
Type: Select either if the following service types. The options available depend on the type of service:
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.
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 best effort applications that can use HSDPA and HSUPA channels. Set the following
parameters under HSPA parameters:
244
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.
Packet (HSPA - Variable Bit Rate): For variable bit rate services using HSDPA channels, select Packet (HSDPA - Variable Bit Rate). Specify the following HSPA parameters:
AT332_UMR_E0
Packet (HSDPA - Variable Bit Rate): For variable bit rate services using HSPA channels. Specify the following 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.
Max throughput demand and Min throughput demand: Enter the maximum and minimum bit rate that the
service can require in the uplink and downlink.
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.
Max throughput demand and Min throughput demand: Enter the maximum and minimum bit rate that the
service can require in the uplink and downlink.
Packet (HSPA - Constant Bit Rate): For constant bit rate services using HSPA channels. Specify the following 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.
Min throughput demand: Enter the minimum bit rate that the service can require in the uplink and downlink.
The uplink and downlink E-DPCCH/A-DPCH activity factors have been set to 0.1 and
cannot be changed. These values are used to estimate the average power on
E-DPCCH and A-DPCH channels.
Variable Bit Rate users are processed as Best Effort users when no value is defined
for the min and max throughput demands.
If you select a packet type, 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. In the Packet dialog box, you can set the following parameters for packet-switched services:
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.
Min size (Kbytes) and Max size (Kbytes): Enter the minimum and maximum size of a packet call in kilobytes for
the uplink and downlink.
Average time between two packets (ms): Enter the average time between two packets in milliseconds in the
uplink and downlink.
Size (Bytes): Enter the packet size in bytes in the uplink and downlink.
Preferred/Allowed Carriers: The specified carrier is considered in simulation when admitting a transmitter to the
mobile active set. If you select "Preferred Carriers" and the transmitter uses the specified carrier, Atoll selects it. Otherwise, it selects another carrier using the carrier selection mode defined in the site equipment properties. If no preferred carrier is specified, it considers the carrier selection mode defined in the site equipment properties. If you select
"Allowed Carriers", Atoll only uses the defined carriers. If they are not available, the service will be rejected.
The preferred/allowed carriers are not used in predictions (i.e., AS analysis, multi-point analysis and coverage predictions).
Bearer Downgrading: Select whether the service supports bearer downgrading on uplink and downkink. Bearer downgrading is not allowed for Packet (HSDPA - Variable Bit Rate) and Packet (HSPA - Variable Bit Rate) services.
Priority: Specify a priority for this service. "0" is the lowest priority.
Soft Handoff Allowed: Select whether 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.
Supported layers: You can select the network layers supported by the service. For more information on network
layers, see "Defining Network Deployment Layers" on page 962. The specified layers are considered in predictions
(i.e., AS analysis, multi-point analysis and coverage predictions) for best serving cell selection. Users are only allowed
to connect to cells of layers supported by their services. For more information on best serving cell selection, see "Best
Serving Cell and Active Set Determination" on page 622.
The supported layers are not used in simulations.
Application throughput: You can define the Scaling factor and the Offset. The throughput scaling factor and offset
are used to determine the user or application level throughput in Radio Link Control (RLC) throughput or timeslot cov-
245
erage prediction. The application throughput is calculated by multiplying the RLC throughput by the scaling factor and
subtracting the offset. These parameters model header information and other supplementary data that do not appear
at the application level.
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.
Type: You can select either "Voice" or "Data" as the service type.
Supported layers: You can select the network layers supported by the service. For more information on network
layers, see "Defining Network Deployment Layers" on page 962. During calculations, users are only allowed to connect
to cells of layers supported by their services.
QoS class identifier (QCI): You can select a QoS class identifier for the service. The information about the QoS class
used by any service is used by the schedulers for resource allocation.
QCI priority: The priority corresponding to the selected QoS class identifier (QCI). QCI values and their priorities are
defined by the 3GPP as follows:
QoS class identifier
QCI priority
Priority: Enter a user-defined priority for the service with respect to other services belonging to the same QoS class
identifier (QCI). "0" is the lowest priority.
Carrier aggregation: Select this check box if the service supports carrier aggregation.
Highest bearer: Select the highest bearer that the service can use in the uplink and downlink. This is considered as an
upper limit during bearer determination.
Lowest bearer: Select the lowest bearer that the service can use in the uplink and downlink. This is considered as a
lower limit during bearer determination.
Min throughput demand and Max throughput demand: Enter the minimum and maximum throughput that the service can demand in the uplink and downlink.
Min number of frequency blocks: Enter the minimum number of frequency blocks required for this service in uplink.
Application throughput: Under Application throughput, you can 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.
The application throughput parameters are used in throughput coverage predictions and for application throughput
calculation.
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 3 dB.
R99 Radio Bearer: Select an R99 radio bearer from the list. You can click the Browse button to edit the properties of
the selected R99 radio bearer.
Type: Select either if the following service types. The options available depend on the type of service:
A-DPCH activity factor: The downlink A-DPCH activity factor is used to estimate the average power on A-DPCH
channels.
Packet (HSPA): For packet services that can use HSDPA and HSUPA channels, select Packet (HSPA). Specify the
followinf settings:
E-UCCH/A-DPCH activity factor: The uplink E-UCCH and downlink A-DPCH activity factors are used to estimate
the average power on these channels.
If you select a packet type, 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. In the Packet dialog box, you can set the following parameters for packet-switched services:
246
Efficiency factor: The uplink and downlink efficiency factors are used to determine duration of usage by the user
during Monte Carlo simulations.
Average number ofpacket calls: Enter the average number of packet calls in the uplink and downlink during one
session.
Average tme between two packet calls: Enter the average time between two packet calls (in milliseconds) in the
uplink and downlink.
Min size (Kbytes) and Max size (Kbytes): Enter the minimum and maximum size of a packet call in kilobytes for
the uplink and downlink.
AT332_UMR_E0
Average time between two packets (ms): Enter the average time between two packets in milliseconds in the
uplink and downlink.
Size (Bytes): Enter the packet size in bytes in the uplink and downlink.
Preferred or Allowed Carriers: The specified carrier is considered in simulation when admitting a transmitter to the
mobile active set. If you select "Preferred Carriers" and the transmitter uses the specified carrier, Atoll selects it. Otherwise, it selects another carrier using the carrier selection mode defined in the site equipment properties. If no preferred carrier is specified, it considers the carrier selection mode defined in the site equipment properties. If you select
"Allowed Carriers", Atoll only uses the defined carriers. If they are not available, the service will be rejected.
The preferred/allowed carriers are not used in predictions (i.e., AS analysis, multi-point analysis and coverage predictions).
Priority: Specify a priority for this service. "0" is the lowest priority.
Application throughput: You can define the Scaling factor and the Offset. The throughput scaling factor and offset
are used to determine the user or application level throughput in Radio Link Control (RLC) throughput or timeslot coverage prediction. The application throughput is calculated by multiplying the RLC throughput by the scaling factor and
subtracting the offset. These parameters model header information and other supplementary data that do not appear
at the application level.
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.
For UMTS R99 bearers, see "Defining R99 Radio Bearers" on page 615.
For CDMA 1xEV-DO radio bearers, see "Defining the Forward Link 1xEV-DO Radio Bearers" on page 727 and "Defining
the Reverse Link 1xEV-DO Radio Bearers" on page 727.
For LTE radio bearers, see "Defining LTE Radio Bearers" on page 964.
For TD-SCDMA R99 bearers, see "Defining R99 Radio Bearers" on page 835
2. Click the General tab and specify a Name for the service.
3. If the document is Multi-RAT, click the Browse button beside Technology priorities to define the technologies that
can use this service and their priority.
To select a technology that can use this service, select the technology in the Available technologies list and
click
to move it to the Selected technologies list.
To remove a technology from the list of Selected technologies, select the technology in the Selected technologies list and click
to move it to the Available technologies list.
To change the priority of the technologies, select a technology and click or to move it up or down in the
list. The technology at the top of the list has the highest priority.
Click OK to close the dialog box and return to the Services: New Record Properties dialog box.
4. Click the tab of the technology for which you want to define the service and enter the parameters as described in "Service Properties" on page 241.
5. Click OK.
247
dependent on mobile speed. In LTE, information about the receiver mobility is required for determining which bearer selection threshold and quality graph to use from the LTE equipment referred to in the terminal or cell.
EcI0 Threshold: Under Active Set Management, enter or modify the minimum EcI0 required from a transmitter 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 EcNt from the HS-SCCH power set
in the cell properties and compares it to this threshold. This field is only used with HSDPA.
Under Active Set Management, enter or modify the following parameters in order to make the user active set
dependent on the mobility type:
Delta Min. EcI0: Enter a positive value in order to increase the minimum EcI0 required from a transmitter to be
the best server in the active set, or a negative value to decrease it.
Delta T_Drop: Enter a positive value in order to increase the minimum EcI0 required from a transmitter not to be
rejected from the active set, or a negative value to decrease it.
Min. EcNt (UL): Enter or modify the minimum EcNt required on the reverse link. This parameter is only used for
CDMA2000 1xEV-DO Rev 0. This parameter is considered during reverse link power control in order to calculate
the required reverse link pilot power.
DL Peak Throughput = f(CI): The graph of the throughput on the forward link as a function of (CI). This parameter
is only used for CDMA2000 1xEV-DO Rev 0.
Under Baton handover parameters, you can set the minimum pilot signal levels required from transmitters to enter
and exit the list of potential servers.
P-CCPCH EbNt threshold or P-CCPCH CI threshold: Enter or modify the minimum P-CCPCH EbNt or CI quality. This
value is used as the minimum requirement limit for the P-CCPCH Quality Analysis (EbNt) (DL) or P-CCPCH Quality
Analysis (CI) (DL) coverage predictions.
DwPCH RSCP threshold: Enter or modify the minimum signal level required for the DwPTS coverage. This value is used
as the minimum requirement limit for the Coverage by DwPCH RSCP coverage prediction.
DwPCH CI threshold: Enter or modify the minimum DwPCH CI quality. This value is used as the minimum requirement limit for the DwPCH Quality Analysis (CI) (DL) coverage prediction.
UpPCH RSCP threshold: Enter or modify the minimum signal level required for the UpPTS coverage. This value is used
as the minimum requirement limit for the Coverage by UpPCH RSCP coverage prediction.
Under HSDPA, you can set the minimum Ec/Nt levels required for HSDPA channels.
HS-SCCH EcNt threshold (DL): Enter or modify the minimum quality required for the HSDPA link to be available.
Atoll calculates the HS-SCCH EcNt from the HS-SCCH power set in the cell properties and compares it to this
threshold. This field is used only with HSDPA.
HS-SICH EcNt threshold (UL): Enter or modify the minimum quality required for the HSDPA link to be available.
Atoll calculates the HS-SICH EcNt from the HS-SICH power set in the terminal properties and compares it to this
threshold. This field is used only with HSDPA.
Under HSUPA, you can set the minimum Ec/Nt levels required for E-DCH channel.
248
P-CCPCH RSCP T_Add (P-CCPCH RSCP threshold): The minimum pilot signal level from transmitters required for
entering the list of potential servers.
P-CCPCH RSCP T_Drop: The signal level from transmitters below which a transmitter cannot enter the list of
potential servers.
E-DCH EcNt threshold (DL): Enter or modify the minimum quality required for the HSUPA link to be available. This
field is used only with HSUPA.
AT332_UMR_E0
2. You can enter or modify the following parameters in the Mobility Types: New Record Properties dialog box.
3. Click the General tab and specify a Name for the service and the movement Speed for the user that you want to
model.
4. If the document uses UMTS, CDMA2000, or TD-SCDMA, click the tab of the technology for which you want to define
the mobility and enter the parameters as described in "Mobility Properties" on page 248.
5. Click OK.
Main Band: The primary frequency band with which the terminal compatible.
Secondary Band: The secondary frequency band with which the terminal is compatible. The compatible frequency
bands are used to allocate the user to a transmitter using that frequency band if the network is a multi-band network.
Noise Figure: The noise caused by the terminal. This value is added to the thermal noise (set to -121 dBm by default)
in predictions when studying CN or CI + N instead of C or CI.
Technology: The technology with which the terminal is compatible. You can choose among GSM, GPRS (i.e., GSM/
GPRS), or GPRS/EDGE (i.e., GSM/GPRS/EDGE).
Codec Configuration: Select the codec configuration for the terminal. This parameter is optional.
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.
DTX: The DTX check box is selected if the terminal supports DTX (Discontinuous Transmission) technology.
If you selected "GSM," "GPRS," OR "GPRS/EDGE" under Technology, set the following parameters under GPRS\EDGE:
Coding Scheme Configuration: If the terminal is GPRS or EDGE-compatible, select the coding scheme configuration for the terminal. This parameter is optional.
Max. GPRS CS: If the terminal is GPRS-compatible, set the maximum number of coding schemes that the terminal
can use.
Max. EDGE CS: If the terminal is EDGE-compatible, set the maximum number of coding schemes that the terminal
can use.
The highest number of GPRS (or EDGE) coding schemes available to the terminal is limited
by the maximum number of GPRS (or EDGE) coding schemes defined for the TRX configuration assigned to a transmitter.
Number of DL Timeslots per carrier: If the terminal is GPRS or EDGE-compatible, you can enter the maximum
number of downlink timeslots the terminal can use on a carrier. Terminals using only circuit-switched services will
249
use only one downlink timeslot. Using more than one DL timeslot has an effect in the dimensioning process. For
more information, see "Dimensioning a GSM/GPRS/EDGE Network" on page 332.
Number of Simultaneous Carriers: If the terminal is EDGE evolution compatible (EGPRS2), you can enter the maximum number of simultaneous carriers the terminal can use. Terminals using either circuit-switched services,
GPRS, or EGPRS packet-switched services will use only one carrier at a time. Using more than one carrier has an
effect in the dimensioning process. For more information, see "Dimensioning a GSM/GPRS/EDGE Network" on
page 332.
When you model EDGE Evolution on the terminal side Atoll has to consider:
The support of high-order modulations and the use of turbo codes in specific
coding schemes which can be found in the selected GPRS/EDGE configuration.
The support of multi-carriers which can be set up on the terminal side.
The support of dual antenna terminals (mobile station receive diversity) and
enhanced single antenna terminals (single antenna interference cancellation).
Atoll offers a statistical modelling of these through the use of an EDGE evolution
configuration, with the effect of SAIC or diversity already included both in the
coding scheme admission thresholds and on the throughput versus C (or CI)
graphs.
Type: Select the terminal type. The following tabs are available depending on the selected type.
The first method consists of defining main, secondary and third frequency bands.
This enables you to give different priorities to the frequency bands in the Monte
Carlo simulation (the main frequency band will have the highest priority). A user
with such a tri-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
and so on.
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.
250
AT332_UMR_E0
For EV-DO-capable terminals, the FCH active set size also determines the active set size on
the reverse link.
Number of Fingers: Enter the maximum number of signals that the terminal can recombine. The value of this field
must be lower than the value of the active set size. The value in this field is the same for both FCH and SCH.
Peak Throughput: Set the peak throughput on both the Downlink and the Uplink.
Pilot Power Percentage: Enter the percentage of the total mobile power that is dedicated to the reverse link pilot
power. This parameter is used during the reverse link power control (if based on traffic quality) in order to calculate the mobile power.
The 1xEV-DO Rev 0 and 1xEV-DO Rev A tabs. The values on these tab are relative to the reverse link pilot power. They
are added to the required reverse link pilot power in order to calculate power on the ACK, RRI (for 1xEV-DO Rev A),
DRC, and traffic data channels. You can modify the following parameters:
Acknowledgement Channel Gain: Enter the gain on the acknowledgement (ACK) channel.
Radio Reverse Indicator (RRI) Channel Gain (for 1xEV-DO Rev A): Enter the gain on the radio reverse indicator
channel.
Data Rate Control Channel Gains (DRC): Under Data Rate Control Channel Gains (DRC), enter the gain for the following handoff types: No Handoff, Softer, and Soft handoff.
Data Channels/Auxiliary Pilot Gains: Under Data Channels/Auxiliary Pilot Gains, enter the gains on the traffic
data channel for both low latency and high capacity services and the gain on the auxiliary pilot channel according
to the radio bearer index. The auxiliary pilot is only used the highest throughputs.
1xEV-DO Rev A-capable terminals support the 16QAM modulation.
Handoff type: Select whether the terminal supports locked or unlocked mode. This parameter is taken into consideration when determining the terminal active set when multi-carrier mode is used. The active set of a multicarrier user consists of sub-active sets, each one being associated with one carrier. When locked mode is used, the
serving transmitters must be the same in all sub-active sets. In this case, the active set is rectangular (i.e., the same
number of serving cells in each sub-active set). With unlocked mode, the serving transmitters can be different
from one sub-active set to another. Here, the active set might be rectangular is not necessarily so (i.e., the number
of serving cells in each sub-active set can vary).
Atoll does not manage the non-rectangular active set configuration when locked mode is
selected.
Highest supported modulation: Select the highest modulation supported by the terminal. You can choose either
16QAM or 64QAM (if you select 64QAM, 64QAM, and 16QAM modulations can be used).
Max number of carriers in multi-carrier mode: Select the maximum number of EV-DO carriers that can be used
when multi-carrier mode is active.
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.
Min power and Max power: Specify the minimum and maximum transmission power. The minimum and maximum
transmission power make up the dynamic range for uplink power control.
Gain and Losses: Specify the antenna gain and reception losses.
DL Rake Factor: Set the DL rake factor. This enables Atoll to model the rake receiver on DL.
251
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 616.
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.
Supported frequency bands: Click the Configure button to select the list of frequency bands supported by the terminal. In the Supported Frequency Bands dialog box, select All for the terminal to support all the frequency bands or
List of selected frequency bands to define the list of supported Frequency bands with the corresponding Noise figures.
During calculations, users are only allowed to connect to cells of frequency bands supported by their terminals.
Default noise figure: Specify the default noise figure of the terminal.
Layers: You can select the network layers supported by the terminal. For more information on network layers, see
"Defining Network Deployment Layers" on page 962. The specified layers are considered in predictions (i.e., AS analysis, multi-point analysis and coverage predictions) for best serving cell selection. Users are only allowed to connect
to cells of layers supported by their terminals. For more information on best serving cell selection, see "Best Serving
Cell and Active Set Determination" on page 622.
Layers are not used in simulations.
Compressed Mode Supported: Select this option if the terminal uses compressed mode. Compressed mode is generally used to prepare hard-handover of users with single receiver terminals.
HSPA Support: Select the type of HSPA support the terminal has:
If you select DB-HSDPA or DB-HSPA, make sure that you have defined a terminal compatible with several frequency
bands.
If the terminal supports HSDPA, you can define the HSDPA parameters under HSDPA:
UE Category: Select the HSDPA user equipment category of the terminal. Click ... to display the properties of each
terminal category.
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 EcNt. MUD is modelled by a coefficient
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. Click ... to display the properties of each
terminal category.
252
Terminal
DL Connection
UL Connection
R99
1 HSDPA carrier
1 frequency band
R99
HSDPA terminal
1 frequency band
HSPA terminal
R99
1 HSDPA carrier
1 frequency band
R99
1 HSUPA carrier
1 frequency band
DC-HSPA terminal
R99
2 HSDPA carriers
1 frequency band
R99
2 HSUPA carriers
1 frequency band
AT332_UMR_E0
Terminal
DL Connection
UL Connection
MC-HSPA terminal
R99
8 HSDPA carriers
1 frequency band
R99
2 HSUPA carriers
1 frequency band
DB-MC-HSPA terminal
R99
8 HSDPA carriers
2 frequency bands
R99
2 HSUPA carriers
1 frequency band
To model the various terminals listed above, you have to set the following parameters:
HSDPA terminal: Select HSDPA as the HSPA support and an HSDPA UE category from Category 1 to 20.
HSPA terminal: Select HSPA as the HSPA support, choose an HSDPA UE category from Category 1 to 20, and an
HSUPA UE category from Category 1 to 8.
DC-HSPA terminal (dual-cell HSPA): Choose HSPA as the HSPA support, select an HSDPA UE category from Category 21 to 28, and a DC-HSUPA UE category from Category 8 to 9.
MC-HSPA (multi-cell HSPA) terminal: Choose HSPA as the HSPA support, select an HSDPA UE category from Category 21 to 36, and a DC-HSUPA UE category from Category 8 to 9.
DB-MC-HSPA (dual-band multi-cell HSPA) terminal: Choose DB-HSPA as the HSPA support, select an HSDPA UE
category from Category 21 to 36, a DC-HSUPA UE category from Category 8 to 9, and define at least two Frequency bands.
Min power and Max power: Enter the minimum and maximum transmission power of the terminal.
Noise figure: Enter the default noise figure of the terminal, which is used to calculate the downlink total noise.
Losses: Enter the losses of the terminal.
LTE equipment: Select an equipment from the list of available reception equipment. For more information on reception equipment, see "Defining LTE Reception Equipment" on page 965.
UE category: Select a UE category from the list of available UE categories. For more information on UE categories, see
"Defining LTE UE Categories" on page 970.
Supported layers: You can select the network layers supported by the terminal. For more information on network
layers, see "Defining Network Deployment Layers" on page 962. During calculations, users are only allowed to connect
to cells of layers supported by their terminals.
Supported frequency bands: Click the Configure button to select the list of frequency bands supported by the terminal. In the Supported Frequency Bands dialog box, select All for the terminal to support all the frequency bands or
List of selected frequency bands to define the list of supported Frequency bands with the corresponding Noise figures.
LTE-Advanced: Select this option if the terminal supports carrier aggregation or CoMP. For carrier aggregation, enter
the Max number of secondary cells for Downlink and Uplink. The number of uplink secondary cells must be less than
or equal to the number of downlink secondary cells. Setting the maximum numbers of secondary cells to 0 means that
the terminal does not support carrier aggregation. For CoMP, select whether the terminal supports in downlink,
uplink, or both.
Model: Select an antenna model from the list of available antennas. If you do not select an antenna for the terminal,
Atoll uses an isotropic antenna in calculations.
In case you do not select an antenna, Atoll uses an isotropic antenna, not an omni-directional antenna, in calculations. An isotropic antenna has spherical radiation patterns in the
horizontal as well as vertical planes.
Gain: Enter the terminal antenna gain if you have not selected an antenna model in the Model field. If you have
selected an antenna, the Gain field is disabled and shows the gain of the selected antenna.
Diversity support: Select the type of antenna diversity techniques supported by the terminal. Antenna diversity
gains will be applied to the users using any terminal type depending on the supported antenna diversity techniques, i.e., AAS, MIMO, or AAS+MIMO. If a terminal that supports AAS+MIMO is connected to a cell that supports both antenna diversity techniques, both AAS and MIMO gains will be applied.
Number of transmission antenna ports and Number of reception antenna ports: Enter the values for the terminal.
TD-SCDMA equipment: Select a type of reception equipment from the list. For more information on reception equipment, see "Receiver Equipment" on page 837.
No. of carriers supported: Select the number of carriers that the terminal can support.
Power: These settings allow you to set the minimum and maximum transmission power limits and the UpPCH power
for the UpPTS timeslot.
253
Min: Set the minimum transmission power. The minimum and maximum transmission powers make up the
dynamic range for uplink power control.
Max: Set the maximum transmission power.
UpPCH: The transmission power for the UpPTS timeslot (or the TS1 uplink timeslot in case of UpPCH shifting).
Gain and Losses: Set the antenna gain and reception losses.
HSPA support: Select the type of HSPA support for this terminal if the terminal is able to use HSPA channels: "None"
(R99 only), "HSDPA", or "HSPA".
For an HSDPA-capable terminal, you can set the following parameters under HSDPA:
UE category: The HSDPA user equipment category of the terminal. For more information on HSDPA UE categories,
see "HSDPA UE Categories" on page 838.
HS-SICH power: The transmission power for the HS-SICH channel. When you are modelling static power allocation,
the HS-SICH dynamic power allocation check box in the cell properties is cleared and the actual power per HSSICH channel is entered in this box. In case of dynamic HS-SCCH power allocation, the value entered here represents the maximum power for the HS-SICH channel.
For an HSPA-capable terminal, you can also set the following parameters under HSUPA:
UE category: The HSUPA user equipment category of the terminal. For more information on HSUPA UE categories,
see "HSDPA UE Categories" on page 838.
2. Click the General tab and specify a Name for the service.
3. If the document is Multi-RAT, click the arrow next to Supported technologies and select the check box of each technology supported by this terminal.
4. Click the tab of the technology that you want to configure for the terminal and enter the parameters as described in
"Terminal Properties" on page 249.
5. Click OK.
254
AT332_UMR_E0
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:
1. In the Parameters explorer, expand the Traffic Parameters folder, right-click the User Profiles folder, and select New
from the context menu. The User Profiles: New Record Properties dialog box 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.
2. In the User Profiles: New Record Properties dialog box, you can modify the following parameters:
Service: Select a service from the list. For information on services, see "Modelling Services" on page 241.
Terminal: Select a terminal from the list. For information on terminals, see "Modelling Terminals" on page 249.
Calls/Hour: For circuit-switched (voice) services and constant bit rate packet-switched services, enter the average
number of calls per hour for the service. The calls per hour is used to calculate the activity probability. For these
services, one call lasting 1000 seconds presents the same activity probability as two calls lasting 500 seconds each.
For packet-switched (data) services (max. bit rate), 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 might not use the service continually.
For example, with a web-browsing 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 might be downloading web pages
and other times he might not be using the application, or he might 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.
255
where:
Nk =
N Area =
Wk =
Weight of clutter k
Sk =
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.
b. Optionally, you can specify a percentage of indoor subscribers for each clutter class. During Monte Carlo simulations, indoor losses defined per frequency per clutter class will be added to the path losses of indoor mobiles.
4. Click OK. The environment is created.
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 257.
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 the following topics:
256
AT332_UMR_E0
For CDMA: Because each of the CDMA technologies has capabilities and services that are
specific to it, it is recommended to create separate traffic maps for voice, 1xRTT data, and
EV-DO data services.
This section covers the following topics:
You can create as many traffic maps as you want and they can be combined in simulations if selected.
To create a sector traffic map:
1. In the Geo explorer, right-click the Traffic Maps folder and select New Map from the context menu. The New Traffic
Map dialog box appears.
2. Select Sector Traffic Map.
3. Select the type of traffic information that you want to input. For simulations, you can choose between the following
inputs:
4. Click the Create button. The Sector Traffic Map dialog box 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.
5. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter.
6. Enter the data required in the Sector Traffic Map dialog box:
Uplink and Downlink Throughputs: enter the throughput demands in the uplink and downlink for each sector and
for each listed service.
Total Number of Users (All Activity Statuses): enter the number of connected users for each sector and for each
listed service.
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.
Downlink Throughputs/Erlangs for GSM traffic analysis (For GSM only): enter the amount of traffic for modelling
GSM traffic:
In erlangs for circuit services (e.g. voice) and constant bit rate packet services (e.g. VoIP). In the second case,
erlangs are internally transformed into Kbps by multiplying the value by a service-guaranteed bit rate per user.
257
7. Click OK. The Sector Traffic Map N Properties dialog box appears.
8. Select the Traffic tab.
Under Terminals (%), enter a percentage for each type of terminal used in the map. The total must equal 100.
Under Mobilities (%), enter a percentage for each mobility type used in the map. The total must equal 100.
9. Select the Clutter tab.
Under Distribution per clutter class, enter the following for each clutter class:
10. Click OK. Atoll creates the traffic map in the Traffic folder.
You can modify the sector traffic map after it has been created.
To modify a sector traffic map:
1. In the Geo explorer, expand the Traffic folder, right-click the traffic map based on live data that you want to update,
and select Properties from the context menu. The Sector Traffic Map dialog box appears.
2. In the Traffic and Clutter tabs, modify the Terminals (%), Mobilities (%), and Distribution per clutter class as required.
3. Click OK. Atoll saves the traffic map with its modified values.
You can update the information on the map afterwards. This can be useful if you add or remove a base station or if you modify
the clutter classes or their distribution. You must first recalculate the coverage prediction by transmitter. Once you have recalculated the coverage prediction, you can update the traffic map.
To update a sector traffic map:
1. In the Geo explorer, expand the Traffic folder, right-click the traffic map based on live data that you want to update
and select Update from the context menu. The Sector Traffic Map dialog box appears.
2. 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.
3. Click OK. The Sector Traffic Map Properties dialog box appears.
4. If necessary, in the Traffic and Clutter tabs, modify the Terminals (%), Mobilities (%), and Distribution per clutter class
as required.
5. 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 263.
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 square kilometre). For more information on environment classes, see "Modelling Environments" on page 255.
258
AT332_UMR_E0
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 in the Parameters explorer, 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 in
the Parameters explorer, 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.
259
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
in the Parameters explorer. If the imported user profile or mobility does not match,
Atoll will display a warning.
6. Select the Clutter tab.
a. Under Distribution per clutter class, 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 =
Weight of clutter k
Sk =
b. If required, you can specify a percentage of indoor subscribers for each clutter class. During Monte Carlo simulations, indoor losses defined per frequency per clutter class will be added to indoor user path losses.
7. Select the Display tab. For information on changing the display parameters, see "Setting the Display Properties of
Objects" on page 51.
8. Click OK to finish importing the traffic map.
260
AT332_UMR_E0
12. Select the Display tab. For information on changing the display parameters, see "Setting the Display Properties of
Objects" on page 51.
13. Click OK to finish importing the user profile environments based traffic map.
Draw Map
Delete
) 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.
7. Click the Close button to close the Environment Map Editor toolbar and end editing.
You can display the statistics of a user profile environment traffic map by right-clicking the
traffic map and selecting Statistics from the context menu.
If you do not have a focus zone defined, statistics are determined for the computation
zone. If a clutter classes map is available in the document, traffic statistics provided for
each environment class are listed per clutter class.
261
All activity statuses: Select this option if the map you are importing provides a density of users with any activity
status.
Active in uplink: Select this option if the map you are importing provides a density of users active in the uplink
only.
Active in downlink: Select this option if the map you are importing provides a density of users active in the downlink only.
Active in uplink and downlink: Select this option if the map you are importing provides a density of users with
both uplink and downlink activity.
Inactive: Select this option if the map you are importing provides a density of inactive users.
Downlink user density for GSM traffic analysis (for GSM only): Select Downlink user density for GSM traffic analysis if the map you are importing provides a density of users active in the downlink only, and with a view to use it
in a traffic capture. For more information on GSM traffic captures, see "Calculating and Displaying a Traffic Capture" on page 327.
Under Terminals (%), enter a percentage for each type of terminal used in the map. The total must equal 100.
Under Mobilities (%), enter a percentage for each mobility type used in the map. The total must equal 100.
Under Services (%), enter a percentage for each service type used in the map. The total must equal 100.
8. Click OK. Atoll creates the traffic map in the Traffic Maps folder.
All Activity Statuses: Select this option if the map you are drawing provides a density of users with any activity
status.
Active in Uplink: Select this option if the map you are drawing provides a density of users active in the uplink only.
Active in Downlink: Select this option if the map you are drawing provides a density of users active in the downlink
only.
Active in Uplink and Downlink: Select this option if the map you are drawing provides a density of users with both
uplink and downlink activity.
Inactive: Select this option if the map you are drawing provides a density of inactive users.
Downlink user density for GSM traffic analysis (GSM only): Select this option if the map that you are creating provides a density of users active in the downlink only when modelling GSM traffic. For more information, see "Studying GSM/GPRS/EDGE Network Capacity" on page 325
6. Click the Create button. The traffic maps properties dialog box appears.
7. Select the Traffic tab.
262
Under Services (%), enter a percentage for each service type used in the map. The total must equal 100.
Under Terminals (%), enter a percentage for each type of terminal used in the map. The total must equal 100.
Under Mobilities (%), enter a percentage for each mobility type used in the map. The total must equal 100.
AT332_UMR_E0
9. Click OK. Atoll creates the traffic map in the Traffic Maps folder.
10. Right-click the traffic map and select Edit from the context menu.
11. Use the tools available in the Vector Editor toolbar in order to draw contours. For more information on how to edit
contours, see "Vector Objects" on page 71. Atoll creates an item called Density values in the User Density Map folder.
12. Right-click the traffic map in the Traffic folder and select Open Table from the context menu.
13. In the table, enter a traffic density value (i.e., the number of users per km2) for each contour that you have drawn.
14. Right-click the traffic map in the Traffic folder and select Edit from the context menu to end editing.
6.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
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.
To create user density traffic maps from a sector traffic map:
1. In the Geo explorer, expand the Traffic folder and right-click the sector traffic map from which you want to create user
density traffic maps. The context menu appears.
2. 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.
3.
263
4. On the Display tab, specify how to display the fixed subscribers on the map. For more information on defining display
properties, see "Setting the Display Properties of Objects" on page 51.
5. Click OK. Atoll creates an empty traffic map in the Traffic Maps folder.
6. Right-click the fixed subscriber traffic map and select Open Table from the context menu. The fixed subscriber traffic
maps data table appears.
7. In the Table toolbar, click the Import (
8. Select a text or comma-separated value (CSV) file containing a tabulated list of fixed subscriber locations and click
Import. The Import dialog box appears. For information on importing table data, see "Importing Tables from Text
Files" on page 88.
9. Click Import.
You can also create custom fields in the fixed subscriber traffic maps data table at the
time of import. To do so, you must have these fields present in the source text or commaseparated value (CSV) file that you are about to import.
To import a fixed subscribers traffic map:
1. In the Geo explorer, right-click the Traffic folder and select New Map from the context menu. The New Traffic Map
dialog box appears.
2. Select Fixed Subscribers and click Import. The Open dialog box appears.
3. Select a text or comma-separated value (CSV) file containing a tabulated list of fixed subscriber locations and click
Import. The Import dialog box appears. For information on importing table data, see "Importing Tables from Text
Files" on page 88.
4. Click Import. Atoll imports the traffic map in to the Traffic Maps folder
You can also add subscriber locations to an existing traffic map by using the New Point
(
) button in the Vector Editor toolbar and clicking on the map using the mouse.
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.
5. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1.
264
AT332_UMR_E0
You must enter a resolution before exporting. If you do not enter a resolution, it
remains at "0" and no data will be exported.
6. 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 "Circuit services" to export traffic using any circuit service,
or select "Packet services" to export traffic using any packet service.
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 this option to export all users without any filter by activity status.
Uplink: Select this option to export terminals that are active in the uplink only.
Downlink: Select this option to export terminals that are active in the downlink only.
Uplink/Downlink: Select this option to export only terminals with both uplink and downlink activity.
Inactive: Select this option to export only inactive terminals.
7. 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.
8. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.
An export Resolution.
6.3 Simulations
Once you have modelled the network services and users and have created traffic maps, you can create simulations. Depending
on the radio technology, the simulation process consists of several 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 can be either active or inactive. Both active and inactive users
consume radio resources and create interference.
A shadowing error is randomly assigned to each user using the probability distribution that describes the shadowing
effect. 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. Technology selection: For each mobile generated at the beginning of the simulation, Atoll searches for its serving cell
in each possible technology. For multi-technology mobiles, an active list of transmitters is generated, possibly using
different technologies. Then, retained transmitters are sorted according to the priorities of technologies in the services.
In a 3GPP or 3GPP2 Multi-RAT environment, the very first part of the simulation consists, for each distributed mobile,
in analysing whether this mobile can be served by cells of different technologies. Each mobile dropped at the begin-
265
ning of the allocation has a specific mobility type and supports one or more technologies as explained in "Modelling
Terminals" on page 249.
For each supported technology, the mobile verifies whether it can be served by at least one transmitter or cell.
If the mobile supports GSM, Atoll determines a GSM best server according to an HCS server prediction where the
mobile can only be served by a GSM transmitter if its mobility does not exceed the maximum speed supported on
its HCS layer and the received signal level is stronger than its HCS layer threshold (see "Setting HCS Layers" on
page 484 for more information). If no transmitter fulfils these conditions, the mobile is not served by GSM.
If the mobile supports CDMA, a best CDMA server is determined based on the Ec/Io values of nearby CDMA cells.
If no cell fulfils these conditions, the mobile is not served by CDMA.
If the mobile supports UMTS, Atoll determines a UMTS best server based on the Ec/Io values of nearby UMTS cells.
If no cell fulfils these conditions, the mobile is not served by UMTS.
If the mobile supports LTE, Atoll determines an LTE best server as described in "Global Network Settings" on
page 959. If no cell respects these conditions, the mobile is not served by LTE.
3. Modelling network regulation mechanisms: Regulation mechanisms are modelled according to the technology, or set
of technologies, used by the network:
For the GSM traffic, Atoll manages the GSM resources as described in "Radio Resource Management in GSM" on
page 335
For CDMA traffic, the CDMA resources are managed as described in "The Power Control Simulation Algorithm" on
page 686.
For UMTS traffic, 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 for HSUPA
users. The power control simulation algorithm is described in "The Power Control Simulation Algorithm" on
page 572.
For LTE traffic, Atoll manages the LTE resources as described in "LTE Traffic Simulation Algorithm" on page 926.
For TD-SCDMA traffic: Atoll performs dynamic channel allocation and power control for mobiles generated in the
previous step. The power control simulation algorithm is described in "The Monte Carlo Simulation Algorithm" on
page 801.
Atoll selects the highest priority as defined in the service assigned to the mobile. Once determined, the serving technology
does not change for a given user distribution. For more information on the methods used for each radio technology, see the
following topics:
266
Information to retain (for UMTS, CDMA2000, and TD-SCDMA only): Select the level of detail that will be available
in the output:
Only the average simulation and statistics: Select this option if none of the individual simulations are to be displayed or available in the group. Only an average of all simulations and statistics is available.
AT332_UMR_E0
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 of 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.
3. If you are using a 3GPP or 3GPP2 Multi-RAT document, for each technology that you want to simulate, click the GSM,
UMTS, CDMA2000, or LTE tab, and click the Take the network into account option. When this check box is selected,
you can specify the following settings for each technology:
GSM: Convergence
UMTS: Load Constraints, Bearer negotiation, and Convergence.
CDMA2000: Load Constraints, and Convergence.
LTE: Load Constraints, Power Control, and Convergence
If you are using a single-RAT document, these settings are located on the Advanced tab
4. Specify the Convergence parameters:
a. If you are using a single-RAT document, click the Advanced tab.
If you are using a 3GPP or 3GPP2 Multi-RAT document, click the technology tab and set the Convergence parameters for each technology that you want to take into account.
b. For GSM, specify the following Convergence parameters:
DL traffic load: Enter the relative difference in terms of downlink traffic load that must be reached between
two iterations.
UL traffic load: Enter the relative difference in terms of uplink traffic load that must be reached between two
iterations.
DL power control gain: Enter the relative difference in terms of downlink power control gain that must be
reached between two iterations.
UL noise rise: Enter the relative difference in terms of uplink noise rise that must be reached between two
iterations.
c. For CDMA2000, UMTS, and TD-SCDMA, specify the following Convergence parameters:
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.
DL traffic load: Enter the relative difference in terms of downlink traffic load that must be reached between
two iterations.
UL traffic load: Enter the relative difference in terms of uplink traffic load that must be reached between two
iterations.
UL noise rise: Enter the relative difference in terms of uplink noise rise that must be reached between two
iterations.
f.
DL traffic load: Enter the relative difference in terms of downlink traffic load that must be reached between
two iterations.
UL traffic load: Enter the relative difference in terms of uplink traffic load that must be reached between two
iterations.
UL noise rise: Enter the relative difference in terms of uplink noise rise that must be reached between two
iterations.
267
Max number of iterations: Specify the maximum number of iterations that Atoll should run to reach a convergence.
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.
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 and
radio data 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.
5. For UMTS, CDMA2000, LTE, Wi-Fi, and WiMAX, specify the Load Constraints parameters:
a. If you are using a single-RAT document, click the Advanced tab.
If you are using a 3GPP or 3GPP2 Multi-RAT document, click the technology tab and repeat the procedure for each
technology that you want to take into account.
b. For UMTS, CDMA2000, enter the following Load Constraints parameters:
Number of CEs: Select the Number of CEs check box if you want the simulation to respect the number of channel elements defined for each site.
Iub throughputs (for UMTS only): 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 the simulation to respect the number of
OVSF codes available each cell.
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 (
Defined per cell.
c. For LTE, Wi-Fi and WiMAX, enter the following Load Constraints parameters:
Max DL traffic Load: If you want to enter a global value for the maximum downlink traffic load, click the button
(
) beside the box and select Global Threshold. Then, enter a maximum downlink traffic load. If you want to
use the maximum downlink traffic load as defined in the properties for each cell, click the button ( ) beside
the box and select Defined per Cell.
Max UL traffic Load: If you want to enter a global value for the maximum uplink traffic load, click the button
) beside the box and select Global Threshold. Then, enter a maximum uplink traffic load. If you want to
use the maximum uplink traffic load as defined in the properties for each cell, click the button ( ) beside the
box and select Defined per Cell.
Backhaul capacity: Select this option if you want Atoll to consider backhaul capacity during LTE simulation.
268
AT332_UMR_E0
grading is not selected, users will be rejected immediately, starting with users with the lowest service priority, if a
constraint cannot be respected.
7. For LTE, specify the Power Control parameters:
a. If you are using a single-RAT document, click the Advanced tab.
If you are using a 3GPP or 3GPP2 Multi-RAT document, click the LTE tab.
b. Under Power control, select the UL noise rise control (Best effort) check box if you want to activate the uplink
noise rise control in the simulations. For more information on the uplink noise rise control, see the Technical Reference Guide.
8. For TD-SCDMA, specify the following additional settings:
a. Click the TD-SCDMA tab.
b. Under Settings, enter an Angular step in degrees which is used to build the geometrical distributions of uplink and
downlink loads. Angular step in used with grid of beams, statistical, and adaptive beam modelling. For more information on the different smart antenna models, see "Smart Antenna Systems" on page 831.
c. Under DCA strategies, select the strategy to be used for selecting carriers and timeslots during the simulations.
There are four different strategies available:
For more information about the DCA strategies, see "The Monte Carlo Simulation Algorithm" on page 801.
d. Select the Calculate interference between mobiles check box and enter a maximum distance to consider between
interfering mobiles in the Max distance field.
e. Click the Advanced tab
f.
Under Quality threshold type, select whether the simulations will be carried out using the Eb/Nt or C/I. For more
information on the quality threshold type selection, see "Global Network Settings" on page 828.
Global scaling factor: If desired, enter a scaling factor to increase user density.
When you create simulations, you are basing them 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. 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 throughputs or users (for sector traffic maps). However, the global scaling factor does not
apply to fixed subscriber 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 based 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 "Working with Traffic Maps" on page 256.
Next to 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.
Under Convergence, enter the Max number of iterations that Atoll should run to make convergence.
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. 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 in the Network explorer.
269
To display the traffic distribution by activity status (see Figure 6.3), select "Discrete values" as Display type and
select "Activity Status" as the Field.
Figure 6.3: Displaying the traffic distribution by activity status (example for LTE)
270
To display the traffic distribution by connection status, select "Discrete values" as Display type and select "Connection Status" as the Field.
To display the traffic distribution by the service in a 3GPP document (see Figure 6.4), on each technology tab,
select "Discrete values" as the Display Type and "Service" as the Field.
AT332_UMR_E0
Figure 6.5: Displaying the traffic simulation results using tip text
271
For GSM:
For UMTS:
For CDMA2000:
UL Load Factor
Total DL Power
For LTE:
272
For TD-SCDMA:
DL traffic power
AT332_UMR_E0
UL load factor
UL reuse factor
Available HSDPA power
Angular distribution of UL and DL loads
For Wi-Fi:
Traffic load (DL) (%)
Traffic load (UL) (%)
UL noise rise (dB)
No. of users (DL)
No. of users (UL)
For WiMAX:
3. You can calculate the new simulation(s) immediately or save them and calculate them later:
Calculate: Click Calculate to save the defined simulation(s) and calculate them immediately.
OK: Click OK to save the defined simulation(s) without calculating them. You can calculate them later clicking the
Calculate button (
273
3. On the Traffic tab of the dialog box, select the Refresh Traffic Parameters check box if you want to take into account
traffic parameter changes in the replayed simulation.
4. On the CDMA2000 and LTE tabs, you can modify the Load constraints and the Convergence thresholds.
5. On the Advanced tab, you can set the following parameters:
Max number of iterations: Enter the maximum number of iterations that should run to make convergence.
DL traffic load: Enter the relative difference in terms of downlink traffic load that must be reached between two
iterations.
UL traffic load: Enter the relative difference in terms of uplink traffic load that must be reached between two iterations.
DL power control gain: Enter the relative difference in terms of downlink power control gain that must be reached
between two iterations.
UL noise rise: Enter the relative difference in terms of uplink noise rise that must be reached between two iterations.
274
Chapter 7
GSM/GPRS/
EDGE Networks
This chapter provides
information on using Atoll to
design, analyse, and
optimise a GSM/GPRS/EDGE
network.
276
AT332_UMR_E0
7 GSM/GPRS/EDGE Networks
Atoll enables you to create and modify all aspects of a GSM/GPRS/EDGE 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 GSM/GPRS/EDGE network is outlined in "Designing a GSM/GPRS/EDGE Network" on
page 277. Creating the network of base stations is explained in "Planning and Optimising GSM/GPRS/EDGE Base Stations" on
page 278. Allocating neighbours 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 GSM/GPRS/EDGE Network Capacity" on page 325, using traffic maps to study network capacity is explained.
Creating traffic captures and simulations using the traffic map information and dimensioning the network using these results
is also explained.
Using drive test data paths to verify the network is explained in "Analysing Network Performance Using Drive Test Data" on
page 471. Filtering imported drive test data paths, and using the data in coverage predictions is also explained.
).
You can open an existing Atoll document by selecting File > Open.
Creating a new Atoll document is explained in Chapter 1: Working Environment.
).
You can add and modify the following elements of base stations:
277
You can also add base stations using a base station template (see "Placing a New Station Using a Station Template" on
page 291).
3. Carry out basic coverage predictions (
).
).
6. Since you know the required number of TRXs, manually or automatically create a frequency plan (
).
)
).
7. Before making more advanced coverage predictions, you need to define cell load conditions (
).
You can generate realistic cell load conditions by creating a simulation based on a traffic map (
and
) (see
"Studying GSM/GPRS/EDGE Network Capacity" on page 325).
You can define them manually ("Importing OMC Traffic Data into the Subcells Table: Traffic Data" on page 326)
(
).
).
).
278
AT332_UMR_E0
7.2.1.1.1
Site Properties
The parameters of a site can be found in the sites Properties dialog box. The Properties dialog box has one tab:
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 dialog box afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 57.
279
7.2.1.1.2
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.
Transmitter Properties
The parameters of a transmitter can be found in the transmitters Properties dialog box. When you create a transmitter, the
Properties dialog box has four tabs: the General tab, the Transmitter tab, the TRXs tab, the AFP tab (see "Allocating Frequencies, BSICs, HSNs, MALs, MAIOs" on page 340), and the Configurations tab. Once you have created a transmitter, its Properties dialog box has four additional tabs: the Intra-Technology Neighbours tab, the Inter-technology Neighbours tab, the
Propagation tab, and the Display tab.
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 Administrators Manual.
ID: You can enter an ID for the transmitter. This is a user-definable network-level parameter for cell identification.
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 dialog box, see "Site Properties" on page 279. You can click the New button to create
a new site on which the transmitter will be located.
Shared antenna: This field is used to identify the transmitters, repeaters, and remote antennas located at the
same site or on sites with the same position and that share the same antenna. The entry in the field must be the
same for all transmitters, repeaters, and remote antennas sharing the same antenna. When changes are made to
the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared
antenna. This field is also used for multi-band transmitters to synchronise antenna parameters for different frequency bands. For more information, see "Advanced Modelling of Multi-Band Transmitters" on page 500.
Under HCS Layer:
You can select the HCS Layer (Hierarchical Cell Structure layer) for the transmitter.
Once you have selected the HCS layer, you can click the Browse button to open the properties of the HCS layer.
You can enter a specific HCS layer threshold for this transmitter. The threshold defined in the HCS Layer properties is considered only if no value is entered in this field.
For information on the HCS layer Properties dialog box, see "Setting HCS Layers" on page 484.
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.
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 explorer.
Only active transmitters are taken into consideration during calculations.
Transmitter Type: If you want Atoll to consider the transmitter as a potential server as well as an interferer, set
the transmitter type to Intra-Network (Server and Interferer). If you want Atoll to consider the transmitter only
as an interferer, set the type to Inter-Network (Interferer Only). No coverage for an Interferer Only transmitter
will be calculated for coverage predictions.
This enables you to model the co-existence of different networks in the same geographic area. For more information on how to study interference between co-existing networks, see "Modelling the Co-existence of Networks"
on page 506.
280
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 dialog box which appears when
you click the Equipment button.
On the Equipment Specifications dialog box (see Figure 7.3), the equipment you select and the gains and losses
you define are used to initialise total transmitter UL and DL losses:
AT332_UMR_E0
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 161.
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 161.
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 162.
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.
Power: Under Power, you can select to enter either Power or EIRP (Effective Isotropical Radiated Power). If you
select EIRP, you can enter the value yourself, without defining power and losses for the transmitter.
If you select Power, Atoll calculates losses and noise according to the characteristics of the equipment assigned
to the transmitter. Equipment can be assigned using the Equipment Specifications dialog box which appears when
you click the Equipment button. Atoll calculates EIRP with the following formula:
EIRP = Power + Gain - DL Losses
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 remote antenna 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.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
Mechanical Azimuth, Mechanical downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt display additional antenna parameters.
The Additional Electrical Downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
281
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.
The Additional Electrical Downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
Under GPRS/EDGE Properties, you must select the GPRS/EDGE Transmitter check box if the transmitter is going
to be a packet-switched capable transmitter. You can select a Coding Scheme Configuration from the list. You can
click the Browse button to access the properties of the configuration. For information on creating a coding scheme
configuration, see "Coding Scheme Configuration" on page 495.
When you model EDGE Evolution on the transmitter side Atoll has to consider:
The support of high order modulations and the use of turbo codes in specific
coding schemes which can be found in the selected GPRS/EDGE Configuration.
The support of dual antenna terminals (Mobile Station Receive Diversity) and
enhanced single antenna terminals (Single Antenna Interference Cancellation).
Atoll offers a statistical modelling of these through the use of an EDGE evolution
configuration, with the effect of SAIC or diversity already included both in the
coding scheme admission thresholds and on the throughput versus C (or CI)
graphs.
The support of multi-carriers which can be set up on the terminal side.
7.2.1.1.3
Under GSM Properties, you can select Codec Configuration from the list. You can click the Browse button to
access the properties of the codec configuration assigned to the GSM transmitter. For information on creating a
coding scheme configuration, see "Codec Configuration" on page 492.
Subcell Properties
In Atoll, a subcell refers to the characteristics of a group of TRXs on a transmitter sharing the same radio characteristics, the
same quality (C/I) requirements, and other settings.
The initial settings of a subcell of a transmitter depend on the cell type selected for the transmitter. Assigning a different cell
type to a transmitter changes the characteristics of the subcells (for information on the cell type, see "Cell Types" on
page 488). Once the cell type has been selected, the initial values of the subcell, taken from the cell type, can be modified,
with the exception of the TRX type. If you modify the cell type afterwards, for all transmitters based on that cell type, Atoll
offers you the choice of keeping current parameters or resetting them to the new cell type parameters.
The properties related to subcells are found on the TRXs tab of the Properties dialog box of the transmitter to which it is
assigned.
Prior to defining a subcell, you may want to define the minimum and maximum range of extended subcells. You can do that
through the General tab of the transmitters Properties dialog box:
Under Extended Cells, you can enter the minimum and maximum range of an extended subcell. Normally, coverage
of a GSM cell is limited to a 35 km radius. Extended GSM cells enable the operator to overcome this limit by taking this
delay into consideration when defining the timing advance for users in the extended cells. Extended cells may cover
distances from 70 to 140 km from the base station. For more information on extended cells, see "Defining Extended
Cells" on page 499.
Min. Range: You can enter the distance from the transmitter at which coverage begins.
Max. Range: You can enter the maximum range from the transmitter of its coverage.
Although coverage can be restricted within the set minimum range and maximum range,
interference from the transmitter is not limited within these ranges.
282
AT332_UMR_E0
TRX tab
Name: You can select the name of the Cell Type on which the transmitters subcells will be based from the list. You
can click the Browse button to access the properties of the cell type.
Relevant Frequency Band: The Relevant Frequency Band displays the frequency band that will be used to calculate the path loss matrix for the transmitter. The frequency band is the band used by the BCCH TRX type under
Subcell (TRX groups) Settings on the same tab.
Cell Reselect Offset: The offset which is applied to the reception threshold to determine the Reselect Criterion
(C2) in idle mode. The C2 value is used to select a server and as a display parameter in coverage predictions.
Max. No. of TRXs: The maximum number of TRXs that the transmitter can have. The value entered here will be
taken instead of the global value defined during dimensioning.
Under Identification:
BSIC Domain: You can select the BSIC (Base Station Identity Code) domain from the list. You can click the Browse
button to access the properties of the selected BSIC domain. For information on BSIC domains, see "Defining BSIC
Domains and Groups" on page 343.
BSIC: The BSIC (Base Station Identity Code) colour code is associated with a defined BCCH so that a mobile can
identify the base station to which both a particular BCCH and BSIC are assigned. The BSIC is derived from the NCC
(Network Colour Code) and the BCC (BTS Colour Code).
To assign a BSIC number to the current transmitter, you can assign a number from the BSIC Domain by selecting
it from the list. You can also enter the BSIC number in the format NCC-BCC. When you click Apply, Atoll converts
the entered NCC-BCC number into the single-number BSIC format. For information on the BSIC, see "Defining the
BSIC Format" on page 343.
BCCH: The BCCH text box displays the frequency of the BCCH (TS0 of the BCCH TRX) of the current transmitter. If
the BCCH subcell, under Subcell (TRX Groups) Settings on the TRXs tab, is in synthesised frequency hopping (SFH)
mode, you can enter the MAL channel which will be TS0.
NCC-BCC: The NCC (Network Colour Code), identifying the operator, and the BCC (BTS Colour Code), identifying
the base station are displayed in the NCC-BCC text box. The NCC and BCC are integers from 0 to 7.
Under Subcells, the information displayed depends on the type of subcell information selected from the Display list,
Standard Data, Traffic Data, AFP Indicators:
Standard: The information displayed is the standard information defining the subcell. The initial settings are from
the selected cell type and can be modified with the exception of the TRX Type:
TRX Type: The TRX Type can be one of the default TRX types available in the GSM/GPRS/EDGE project template:
BCCH: The broadcast control channel (BCCH) carrier
TCH: The default traffic (TCH) carrier
TCH_EGPRS: The EDGE traffic (TCH_EGPRS) carrier.
TCH_INNER: The inner traffic (TCH_INNER) carrier.
Frequency Domain: The frequency domain assigned to the TRX group. Only channels belonging to this frequency domain will be allocated to TRXs of this group during manual or automatic frequency planning.
The frequency domains assigned to the BCCH subcell and to the TCH subcell must reference the same frequency band, unless you are modelling multi-band transmitters. For
information on multi-band transmitters, see "Advanced Modelling of Multi-Band Transmitters" on page 500.
Excluded Channels: The defined frequency domain can have, as part of its definition, a list of excluded channels. Addition excluded channels for this subcell can be added in the Excluded Channels column.
Required TRXs: The number of TRXs required for the subcell. For subcells with the BCCH TRX Type, the number
of requested TRXs must be "1," the default value. For subcells with the TCH, TCH_EGPRS or TCH_INNER TRX
Type, the value in the Required TRXs column is a result of network dimensioning, which depends on the traffic
demand and the required quality.
DL Traffic Load: The DL usage rate of TRXs within a same subcell pool; its value must be from 0 to 1. The value
in the DL Traffic Load column can be either user-defined, obtained from Monte Carlo simulations, or the result
of network dimensioning, in which case it will be the same value for all subcells covering the same area (e.g.
BCCH and TCH). The traffic load is used to calculate DL interference and in automatic frequency planning.
UL Traffic Load: The UL usage rate of TRXs; its value must be from 0 to 1. The value in the UL Traffic Load
column can be either user-defined or obtained from Monte Carlo simulations. The traffic load is used to calculate UL interference.
283
DL Power Reduction (dB) : The reduction of power relative to the transmitter power. The DL Power Reduction
is used to model the power reduction of TCH TRXs, TCH_EGPRS and TCH_INNER TRXs. TCH_INNER TRXs are
concentric subcells, in other words, subcells that transmit a power lower than that used by the BCCH TRX and
by TCH TRXs.
DL power reduction can also be used to model in a simple way the coverage reduction of
a 1800 subcell compared to the BCCH 900 subcell, assuming that all subcells are transmitting at the same power. Atoll also enables advanced multi-band transmitter modelling. For
more information, see "Advanced Modelling of Multi-Band Transmitters" on page 500 and
the Administrator Manual.
284
Reception Threshold (dBm): The reception threshold defines the minimum reception level for the subcell. I
can be used as the minimum subcell reception sensitivity if the link budget is correctly defined.
C/I Threshold (dB): The minimum signal quality for the TRX Type. The C/I Threshold can be used in interference predictions and in the AFP.
Mean Power Control Gain (dB): The average reduction in interference due to power control in downlink. This
gain is used when calculating interference generated by the subcell. Interference generated by the subcell is
reduced by this value during C/I calculations. This value can be user-defined or the result of Monte Carlo simulations.
Timeslot Configuration: The timeslot configuration defines the distribution of circuit, packet and shared
timeslots for the subcell. For information on timeslot configurations, see "Timeslot Configurations" on
page 499.
DTX Supported: The DTX Supported check box is selected if the subcell supports DTX (Discontinuous Transmission) technology. Subcells supporting DTX can reduce the interference they produce by the defined voice
activity factor.
Hopping Mode: The frequency hopping mode supported by the selected TRX type. The hopping mode can be
either "Base Band Hopping" mode (BBH) or "Synthesised Hopping" mode (SFH). If frequency hopping is not
supported, select "Non Hopping."
Allocation Strategy: The allocation strategy used during manual or automatic frequency planning. There are
two available allocation strategies:
- Free: Any of the channels belonging to the frequency domain can be assigned to TRXs.
- Group Constrained: Only channels belonging to a same frequency group in the frequency domain can be
assigned. You can use the Preferred Frequency Group to define the preferred group of frequencies when
using the AFP.
Default TRX Configuration: The default TRX configuration selected in this column is applied to all TRXs belonging to the subcell. By selecting the default TRX configuration, the maximum number of coding schemes in GPRS
and in EDGE is set at the TRX type level. You can also define the TRX configuration for each TRX.
EDGE Power Backoff (dB): The average power reduction for EDGE transmitters due to 8PSK, 16QAM and
32QAM modulations in EDGE. This has an impact on the EDGE service zone which can be seen in traffic analysis
and EDGE predictions.
Diversity Mode: The type of diversity supported by the subcell ("None," "Tx Diversity," or "Antenna Hopping").
If you select "Tx Diversity," the signal is transmitted as many times that there are antennas. If you select
"Antenna Hopping," the signal is transmitted successively on each antenna. In "Tx Diversity" mode, transmitting on more than one antenna, the signal experiences a gain of 3 dB. For all diversity modes, an additional
transmission diversity gain can be defined per clutter class in order to correctly model gain due to the environment (for more information, see "Defining Clutter Class Properties" on page 127). The resulting gain will
increase the C/I value at the terminal served by the considered subcell.
Max MAL Length: The maximum length of the mobile allocation list (MAL), in other words, the maximum
number of channels allocated to the TRXs of the subcell during automatic frequency planning if the Hopping
Mode is either SFH (Synthesised Frequency Hopping) or BBH (Base Band Hopping) and if the Allocation Strategy is Free.
Synchronisation: The value entered in the Synchronisation column is used during frequency hopping;
frequency hopping is synthesised among all TRXs of subcells with the same string of characters in the Synchronisation column. By default, the name of the site is used as the value in the Synchronisation column, synchronising frequency hopping for all TRXs on the same site. However, you can, for example, enter different values
for each subcell to define synchronisation at the subcell level, or different values for each group of sites to
define synchronisation by sites group.
HSN Domain: Only hopping sequence numbers (HSN) belonging to the selected HSN domain will be allocated
to subcells during manual or automatic frequency planning. The HSNs are allocated if the Hopping Mode is
either SFH (Synthesised Frequency Hopping) or BBH (Base Band Hopping).
HSN: The hopping sequence number (HSN) of the subcell. All TRXs of the subcell have the same HSN. The HSN
can be entered manually or allocated automatically. This parameter is used if the Hopping Mode is either SFH
(Synthesised Frequency Hopping) or BBH (Base Band Hopping).
Lock HSN: When this check box is selected, the subcells currently assigned HSN is kept when a new AFP
session is started.
AT332_UMR_E0
The Lock HSN status can also be managed via the Network explorer from the context menu
of an individual transmitter or group of transmitters. For more information, see "AFP
Resource Status Management" on page 288.
Accepted Interference Percentage: The maximum level of interference allowable during automatic frequency
planning. The interference is defined as a percentage of area or traffic, as defined during the calculation of the
interference matrices.
Preferred Frequency Group: When the Group Constrained allocation strategy is selected, in any hopping
mode (including non-hopping), the AFP tries to assign frequencies from the preferred group during automatic
allocation. The preferred frequency group is a soft constraint used by the AFP to assign frequencies to TRXs.
When the AFP is unable to assign a frequency from the preferred group, and allocates a frequency from
outside the group, a corresponding cost is taken into account. The preferred group can also be the result of
allocation if the AFP model is able to allocate patterns based on the azimuth.
AFP Weight: Enter an AFP weight. The AFP weight is used to increase or decrease the importance of a subcell
during automatic frequency planning. The value must be a real number. The higher the AFP weight is, the
higher the constraint on the TRX type. The AFP weight artificially multiplies the cost which has to be minimised
by the AFP.
Lock Required TRXs: This option can be used by an AFP model which has the capability to optimise (i.e.,
increase or decrease) the number of required TRXs where the only goal is maximising the amount of correctly
served traffic. In other words, you might have fewer TRXs than required if they are not subject to any interference and the amount of correctly served traffic will be larger. When you select this option, the number of
required TRXs is blocked for that subcell.
If some subcell fields are empty (e.g., HSN domain, frequency domain, C/I Threshold), Atoll
uses the default values of the selected Cell type. For more information, see "Creating a Cell
Type" on page 488.
Traffic Data: The information displayed describes the traffic of the cell. Because subcells share the traffic of the
transmitter, in most cases, the traffic data for all TRXs is displayed together. All fields can be modified with the
exception of the TRX Type, Effective Rate of Traffic Overflow, and Traffic Load.
TRX Type: The type can be one of the default TRX types available in the GSM/GPRS/EDGE project template:
- BCCH: The broadcast control channel (BCCH) carrier
- TCH: The default traffic (TCH) carrier
- TCH_EGPRS: The EDGE traffic (TCH_EGPRS) carrier
- TCH_INNER: The inner traffic (TCH_INNER) carrier
Circuit Demand (Erlangs): The circuit demand indicates the amount of Erlangs necessary to absorb the circuitswitched demand. This value can be either user-defined or the result of a traffic capture, in which case it will
be the same value for all subcells covering the same area (e.g., BCCH and TCH).
Packet Average Demand (TS): The packet demand indicates the amount of timeslots necessary to absorb the
packet-switched demand. This value can be either user-defined or the result of a traffic capture, in which case
it will be the same value for all subcells covering the same area (e.g., BCCH and TCH).
Circuit and packet demands can be imported into this table from a real network. These value will then be taken
into account for dimensioning or KPI calculation if these calculations are not based on the default traffic capture.
Half-Rate Traffic Ratio (%): The percentage of half-rate voice traffic in the subcell. This value is used to calculate the number of timeslots required to respond to the voice traffic demand. This value can be user-defined
or the result of Monte Carlo simulations.
Target Rate of Traffic Overflow (%): The target rate of traffic overflow is used during traffic analysis to distribute the traffic between subcells and layers. The traffic located in the inner zone or in the service zone of a high
priority cell (see the figures below) contributes to the traffic demand of the inner subcell or the high priority
cell respectively. If the target rate of traffic overflow is greater than 0, a part of this traffic is re-injected, so
that it also contributes to the demand of outer zone (or to the low priority cell respectively). The key performance indicators calculation (and dimensioning process) transforms the traffic demand into a served demand
on one hand and an effective overflow on the other hand. If effective overflow rates are higher than target
overflow rates, it means there is a capacity reserve. If it is the other way around, it means that more TRXs are
needed. If rates are equal, the network is correctly optimised.
285
AFP Indicators: The information displayed comes from the results of an AFP model; it is displayed for informational purposes only and cannot be edited.
TRX Type: The type can be one of the default TRX types available in the GSM/GPRS/EDGE project template:
- BCCH: The broadcast control channel
- TCH: The default traffic channel
- TCH_EGPRS: The EDGE traffic channel
- TCH_INNER: The inner traffic channel
Total Cost: The total cost is the combination of the AFP Separation Cost, the Additional Cost, and the AFP Congestion cost.
AFP Separation Cost: The separation cost is the cost to the system when separation rules are not respected
between subcell pools. If separation constraints are violated, this has a direct effect on the interference level.
Additional Cost (Interference, Modification, Group): The additional cost is combination of other costs such as
interference, the cost of carrying modifications, and not respecting the preferred TRX group.
AFP Blocking Cost: The AFP blocking cost is the part of the cost where traffic is considered as blocked due to
a lack of resources.
Soft Blocking (Total Cost - Blocking): Total cost minus the AFP blocking cost.
AFP Congestion: The AFP congestion is the soft blocking cost, an estimation of the level of congestion for a
pool of subcells (e.g., BCCH and TCH are considered as a pool of subcells since they are managed together). In
other words, a highly congested pool of subcells will be a source of a high level of interference.
286
Effective Rate of Traffic Overflow (%): The percentage of traffic overflowing from a subcell. The effective rate
of traffic overview is a result of the calculation of key performance indicators.
DL Traffic Load: The DL usage rate of TRXs within a same subcell pool; its value must be from 0 to 1. The value
in the DL Traffic Load column can be either user-defined, obtained from Monte Carlo simulations, or the result
of network dimensioning, in which case it will be the same value for all subcells covering the same area (e.g.
BCCH and TCH). The traffic load is used to calculate DL interference and in automatic frequency planning.
UL Traffic Load: The UL usage rate of TRXs; its value must be from 0 to 1. The value in the UL Traffic Load
column can be either user-defined or obtained from Monte Carlo simulations. The traffic load is used to calculate UL interference.
Final Blocking Probability (%): Key performance indicator (KPI) calculated using a traffic capture and the AFP
module. This KPI is also part of a simplified traffic model used by the AFP module.
AT332_UMR_E0
7.2.1.1.4
The subcells of the entire GSM/GPRS/EDGE document are found in the Subcells
Table: Standard Data. You can open the Subcells Table: Standard Data by rightclicking the Transmitters folder in the Network explorer and then selecting
Subcells > Subcells Table: Standard Data from the context menu. In addition, you
can access specific views of the subcell table. The table containing the information
regarding traffic data, or the AFP indicators, can be accessed by right-clicking the
Transmitters folder in the Network explorer and then selecting Subcells > Subcells
Table: Traffic data (or AFP Indicators) from the context menu.
You can run a subcell audit to verify the consistency of data between the Subcell
and Transmitter tables. As well, this audit can correct unrealistic subcell values
(see "Checking Consistency in Subcells" on page 461 for more information).
TRX Properties
In Atoll, the TRX refers to the transmission/reception card. In GSM/GPRS/EDGE projects, frequencies and channels are defined
using TRXs. In non-hopping or base-band hopping mode, a single frequency or channel can be assigned to each TRX. In synthesised frequency hopping mode, more than one frequency can be assigned to each TRX.
The number of timeslots supported by a TRX defines the multiplexing factor of the frequency using that TRX.
In Atoll, TRXs are modelled using defined TRX types. Three TRX types are available in the GSM/GPRS/EDGE project template:
The TRXs and their properties are found on TRXs tab of the Properties dialog box of the transmitter to which they are assigned.
The TRXs of the entire GSM/GPRS/EDGE document are found in the TRXs Table. You can
access the TRXs Table by right-clicking the Transmitters folder in the Network explorer
and then selecting Subcells > TRXs Table from the context menu.
The TRXs tab has the following TRX-related options:
Under TRXs, the table lists each TRX allocated to the transmitter. The initial settings are from the selected cell type
and can be modified. You can sort the content of each column as described in "Sorting Data in Tables" on page 97, on
each column of the table.
Index: This is the identification number of the TRX. The number must be an integer and can be user-defined or
assigned automatically by Atoll when you close the dialog box.
TRX Type: The TRX Type can be one of the default TRX types available in the GSM GPRS EDGE project template:
Channels: The channels allocated to the TRX. You must specify 1 channel per TRX if the hopping mode for the TRX
type is "Non Hopping" or "Base Band Hopping," and more than one channel per TRX if the hopping mode for the
TRX type is "Synthesised Hopping." You can enter channels directly (separating them with a comma, a semi-colon,
or a space) or you can enter a range of channels separating the first and last channel with a hyphen (for example,
entering "1-5" corresponds to "1 2 3 4 5"). You can also select a channel from the list which offers you channels
from the frequency domain assigned to the TRX type that this TRX is based on.
MAIO: The MAIO (Mobile Allocation Index Offset) is used in frequency hopping (BBH or SFH) to avoid intra-site
collisions caused by two sites using the same or adjacent channels. This value is an integer ranging from 0 and N-1
(where "N" is the number of channels used in the hopping sequence). You can enter the MAIO or it can be allocated automatically using the AFP.
Lock Channels and MAIO: When this check box is selected, the TRXs currently assigned channels and MAIO are
kept when a new AFP session is started.
287
The Lock Channels and MAIO status can also be managed via the Network explorer from
the context menu of an individual transmitter or group of transmitters. For more information, see "AFP Resource Status Management" on page 288.
7.2.1.1.5
TRX Configuration: The selected TRX Configuration defines the highest possible coding scheme index number in
GPRS and in EDGE. For the TRX configuration to be used fully, the terminal must be capable of using a coding index
number that is as high as that of the TRX configuration. Otherwise, capacity will be limited by the highest index
number supported by the terminal.
EDGE Power Backoff (dB): The average power reduction for EDGE transmitters due to 8PSK, 16QAM and 32QAM
modulations in EDGE. This has an impact on the EDGE service zone which can be seen in traffic analyses and EDGE
predictions.
TRX Rank: The TRX rank is determined by the AFP. It indicates the quality of that TRX. The higher the TRX rank, the
higher the cost, in terms of the risk of interference. In other words, when you are trying to improve the solution
proposed by the AFP tool, you must concentrate on the TRXs with the highest TRX rank first.
Additional DL Noise Rise (dB): This noise rise represents the interference created by the mobiles of an external
network on the mobiles served by this TRX on the downlink. This noise rise will be taken into account in all interference-based calculations involving this TRX. For more information on inter-technology interference, see "Modelling Inter-technology Interference" on page 507.
Intra-technology UL Noise Rise (dB): This noise rise represents the interference created by the mobiles of the current network over this TRX on the uplink. The value can be either user-defined or obtained from Monte Carlo simulations. This noise rise is used to calculate UL interference.
Subcells Table
(Standard Data)
TRXs Table
Lock HSN
Lock HSN
Lock BSIC
Individual transmitters
Transmitters folder > Frequency Plan
Transmitters sub-folder > Frequency Plan
The following commands are available from each Lock and Unlock command group folder:
Transmitters
Neighbours
Donor Transmitters
288
AT332_UMR_E0
When one of these commands is invoked, the corresponding dialog box appears:
Lock > Transmitters and Unlock > Transmitters commands apply to all the transmitters in the selected folder or subfolder (or to the selected transmitter).
Lock > Neighbours and Unlock > Neighbours commands apply to all the GSM neighbours of all the transmitters in the
selected folder or sub-folder (or to the GSM neighbours of the selected transmitter).
Lock > Donor Transmitters and Unlock > Donor Transmitters commands apply to all the transmitters in the selected
folder or sub-folder which are donor transmitters of repeaters (or to the selected transmitter if it is a donor transmitter of a repeater).
7.2.1.2.1
7.2.1.2.2
289
5. Click OK. When you create a new transmitter, Atoll automatically assigns a cell type based on the default station template. For information on modifying the properties inherited from a cell type, see "Applying a New Cell Type" on
page 290.
To modify the properties of an existing transmitter:
1. Select the Network explorer.
2. Click the Expand button ( ) 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 dialog box appears.
5. Modify the parameters described in "Transmitter Properties" on page 280.
6. Click OK.
7.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 in the Network explorer and selecting Open Table
from the context menu. For information on copying and pasting data, see "Copying
and Pasting in Tables" on page 83.
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.
7.2.1.2.4
Modifying a Subcell
You can modify the parameters of an existing subcell. You can access the properties of a subcell, described in "Subcell Properties" on page 282, through the Properties dialog box of the transmitter where the subcell is located.
To create or modify a subcell:
1. Select the Network explorer.
2. Click the Expand button ( ) to expand the Transmitters folder.
3. Right-click the transmitter on which you want to create a subcell or whose subcell you want to modify. The context
menu appears.
4. Select Properties from the context menu. The transmitters Properties dialog box appears.
290
AT332_UMR_E0
7.2.1.2.5
If you are creating a new TRX, enter the parameters described in "TRX Properties" on page 287 in the row marked
with the New Row icon (
).
If you are modifying an existing TRX, modify the parameters described in "TRX Properties" on page 287.
7. Click OK.
If you are creating several TRXs at the same time, or modifying several existing TRXs, you
can do it more quickly by editing or pasting the data directly in the TRXs table. You can
open the TRXs table by right-clicking the Transmitters folder in the Network explorer
and selecting Subcells > TRXs Table from the context menu. For information on copying
and pasting data, see "Copying and Pasting in Tables" on page 83.
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 60.
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.
291
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.
7.2.1.4.1
292
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
Under Main antenna, you can select the main antenna Model, under Smart antenna, you can select the smart
antenna Equipment used by the transmitter, and under Number of antenna ports, you can enter the number of
antennas used for Transmission and for Reception for MIMO.
Under Path loss matrices, you can modify the following: the Main propagation model, the Main radius, and the Main
resolution, and the Extended propagation model, the Extended radius, and the Extended resolution. For information
on propagation models, see Chapter 4: Radio Calculations and Models.
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.
AT332_UMR_E0
Transmitter Tab
Use this tab to modify the following settings:
Transmitter Type: If you want Atoll to consider transmitters created using this template as potential servers as well
as interferer(s), set the transmitter type to Intra-Network (Server and Interferer). If you want Atoll to consider transmitters created using this template only as interferers, set the type to Intra-Network (Interferer Only). No coverage
for an Interferer Only transmitter will be calculated for coverage predictions.
This enables you to model the co-existence of different networks in the same geographic area. For more information
on studying interference between co-existing networks, see "Modelling the Co-existence of Networks" on page 506.
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 dialog box which appears when you click the Equipment button.
For information on the Equipment Specifications dialog box, see "Transmitter Properties" on page 280.
Power: Under Power, you can select to enter either Power or EIRP (Effective Isotropical Radiated Power). If you select
EIRP, you can enter the value yourself, without defining power and losses for the transmitter.
If you select Power, Atoll calculates losses and noise according to the characteristics of the equipment assigned to the
transmitter. Equipment can be assigned using the Equipment Specifications dialog box which appears when you click
the Equipment button. Atoll calculates EIRP with the following formula:
EIRP = Power + Gain - DL Losses
If you want transmitters created with this station template to be active by default, select the Active check box.
Configurations Tab
On this tab, you select the configuration used for GSM and GPRS/EDGE stations.
GPRS/EDGE Properties: Select the GPRS/EDGE Transmitter option if the transmitters are going to be packet-switched
capable transmitters, select a Coding Scheme Configuration from the list. For information on creating a coding
scheme configuration, see "Coding Scheme Configuration" on page 495.
When you model EDGE Evolution on the transmitter side Atoll has to consider:
The support of high order modulations and the use of turbo codes in specific
coding schemes which can be found in the selected GPRS/EDGE Configuration.
The support of dual antenna terminals (Mobile Station Receive Diversity) and
enhanced single antenna terminals (Single Antenna Interference Cancellation).
Atoll offers a statistical modelling of these through the use of an EDGE evolution
configuration, with the effect of SAIC or diversity already included both in the
coding scheme admission thresholds and on the throughput versus C (or CI)
graphs.
The support of multi-carriers which can be set up on the terminal side.
For all transmitters, select a codec configuration from the list. For information on creating a coding scheme configuration, see "Codec Configuration" on page 492.
Neighbours tab
Max number of neighbours: Set the maximum numbers of Intra-technology and Inter-technology neighbours. For information on defining neighbours, see "Neighbour Planning" on page 223.
Other Properties
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 dialog box.
7.2.1.4.2
293
7.2.1.4.3
7.2.1.4.4
7.2.1.4.5
7.2.1.4.6
294
AT332_UMR_E0
where you place the duplicated base station, Atoll will create a new site with the same parameters as the site of the original
base station. 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.
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 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.
5. Place the new base station on the map using the mouse:
Creating a duplicate base station and site: In the map window, move the pointer over the map to where you
would like to place the duplicate. The exact coordinates of the pointers current location are visible in the Status
bar.
Placing the duplicate base station on an existing site: In the map window, move the pointer over the existing site
where you would like to place the duplicate. When the pointer is over the site, the site is automatically selected.
The exact coordinates of the pointers current location are visible in the Status bar.
To place the base 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 60.
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.
295
) in the Radio Planning toolbar. The Point Analysis window appears and the
pointer changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and
the current position. You can move the receiver on the map (see "Moving the Receiver on the Map" on page 203).
3. Select the Profile view. The Profile view displays the profile between the transmitter and the receiver with the terrain
and clutter heights.
The received signal strength from the selected transmitter for the cell with the highest reference signal power
The propagation model used
The shadowing margin and the indoor loss (if selected)
The distance between the transmitter and the receiver.
4. If needed, select an other transmitter from the list. You can click the Properties button (
properties.
) to display the Calculation Options dialog box and change the following:
Change the X and Y coordinates to change the current position of the receiver.
Select the Shadowing taken into account check box and enter a Cell edge coverage probability. For more information, see "Taking Shadowing into Account in Point Analyses" on page 204.
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. Indoor losses are defined per frequency per
clutter class. For more information, see "Taking Indoor Losses into Account" on page 203.
7. In the Profile view toolbar, you can use the following tools:
296
) to view the geographic profile between the transmitter and the receiver.
) again to view the radio signal path between the transmitter and the
AT332_UMR_E0
Click the Detailed Report button ( ) to display a text document with details on the displayed profile analysis.
The detailed report is only available for the Standard Propagation Model.
Click the Copy button (
) to copy the content of the view and paste it as a graphic into a graphic editing or wordprocessing programme.
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 subcell data in the Subcells table, in that order.
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 83.
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 subcell data in the Subcells table, in that order.
For information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets" on page 86. For information on importing table data, see "Importing Tables from Text Files" on page 88.
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 291.
297
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 "Associating a
Label to an Object" on page 53.
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 "Associating a Tip Text to an Object" on page 54.
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.
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 "Setting the Display Type" on page 52.
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 (
same site with the same azimuth, you can differentiate them by selecting different symbols for each (
For information on defining the transmitter symbol, see "Setting the Display Type" on page 52.
and
).
298
AT332_UMR_E0
Broad-band repeaters are not modelled. Atoll assumes that all carriers from the 3G donor
transmitter are amplified.
):
e. Enter a Max. Downlink Power. This parameter is used to ensure that the downlink power is not exceeded after
amplification by the repeater.
f.
If desired, enter an Internal Delay and Comments. These fields are for information only and are not used in calculations.
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.
299
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 in the Network explorer 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 300.
When the donor is a transmitter, you can see to which base station the repeater is
connected by clicking it; Atoll displays a link to the donor transmitter. You can hide
the link by clicking it again.
When the donor is a repeater or a remote antenna, Atoll displays a spider-type link
showing the entire chain down to the donor transmitter. The same spider-type link
is displayed when you click any of the items belonging to the chain is clicked (i.e.,
donor transmitter, any repeater, or any remote antenna).
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 83.
You can change the Name of the repeater. By default, repeaters are named "SiteX_Y_RepZ" where "X" is the donor
site number, "Y" the donor transmitter number, and "Z" a number assigned to the repeater when it was created.
300
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, a remote antenna,
or another repeater. Clicking the Browse button opens the Properties dialog box of the selected donor.
You can change the Site on which the repeater is located. Clicking the Browse button opens the Properties dialog
box of the selected site.
You can enter a value in the Shared Antenna (coverage side) field for the repeater. This field is used to identify the
transmitters, repeaters, and remote antennas that are located on the same site or on sites with the same position
and that share an antenna. The entry in the field must be the same for all such transmitters, repeaters, and remote
antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of
one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote
antennas defined as having a shared antenna.
AT332_UMR_E0
This field is also used for multi-band transmitters to synchronise antenna parameters for
different frequency bands. For more information, see "Advanced Modelling of Multi-Band
Transmitters" on page 500.
Under Antenna Position, you can define the position of the repeater, if it is not located on the site itself:
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 dialog box 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:
If you select Microwave Link, enter the Link Losses and proceed to 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:
Model: The type of antenna is visible in the Model list. You can click the Browse button to access the properties of the antenna.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
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 repeater is situated on a building, the height entered must
include the height of building.
Mechanical Azimuth and Mechanical Downtilt display additional antenna parameters.
You can click the Calculate button to update the mechanical azimuth and mechanical
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 to access the properties of the feeder.
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
explorer) are calculated.
Under Transmission, enter the a value for EIRP (Effective Isotropically Radiated Power) or click Calculate to determine the actual gains. Atoll calculates the EIRP with the following formula:
EIRP = Power + Gain - Losses
Even if the EIRP is a DL parameter, Atoll can extract the corresponding gain from the
knowledge of the various transmission gains and losses. This gain is then re-used to evaluate UL power used in any UL calculation.
301
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 repeater 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. Click the Browse button
to access the properties of the antenna.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
Mechanical Azimuth, Mechanical downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt display additional antenna parameters.
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.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
Select a Type of feeder from the list. You can click the Browse button to access the properties of the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
Misc. losses: You can specify additional losses in dB for Transmission and Reception.
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 4: Radio Calculations and Models.
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 EIRP (Effective Isotropically Radiated Power) of all repeaters by selecting Repeaters > Calculate
EIRP from the Transmitters context menu.
You can prevent Atoll from updating the EIRP 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 EIRP from the Transmitters context menu, Atoll will only update the EIRP 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 57) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using
the Mouse" on page 58).
302
AT332_UMR_E0
that has antennas. This can be done by modelling a repeater. For information on creating a repeater, see "Creating a
Repeater" on page 298.
In this section, the following are explained:
When the donor is a transmitter, you can see to which base station the repeater is
connected by clicking it; Atoll displays a link to the donor transmitter. You can hide
the link by clicking it again.
When the donor is a repeater or a remote antenna, Atoll displays a spider-type link
showing the entire chain down to the donor transmitter. The same spider-type link
is displayed when you click any of the items belonging to the chain is clicked (i.e.,
donor transmitter, any repeater, or any remote antenna).
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.
The table you copy data from must have the same column layout as the table you are
pasting data into.
303
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 83.
You can change the Name of the remote antenna. By default, remote antennas are named "SiteX_Y_RemZ" where
"X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned to the remote antenna
when it was created.
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, another remote
antenna or a repeater. Clicking the Browse button opens the Properties dialog box of the selected donor.
You can change the Site on which the remote antenna is located. Clicking the Browse button opens the Properties
dialog box of the selected site.
You can enter a value in the Shared Antenna (coverage side) field for the remote antenna. This field is used to
identify the transmitters, repeaters, and remote antennas located on the same site or on sites with the same position. The entry in the field must be the same for all such transmitters, repeaters, and remote antennas. Shared
antennas are located on the same site or on sites with the same position. When changes are made to the position
offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the
same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna.
Under Antenna Position, you can define the position of the remote antenna, if it is not located on the site itself:
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 explorer) are calculated.
Under Transmission, enter the a value for EIRP (Effective Isotropically Radiated Power) or click Calculate to determine the actual gains. Atoll calculates the EIRP with the following formula:
EIRP = Power + Gain - Losses
Even if the EIRP is a DL parameter, Atoll can extract the corresponding gain from the
knowledge of the various transmission gains and losses. This gain is then re-used to evaluate UL power used in any UL calculation.
304
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 remote antenna 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.
AT332_UMR_E0
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
Mechanical Azimuth, Mechanical downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt display additional antenna parameters.
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.
The Additional Electrical Downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
Select a Type of feeder from the list. You can click the Browse button to access the properties of the selected
feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
Misc. losses: You can specify additional losses in dB for Transmission and Reception.
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 4: Radio Calculations and Models.
You can update the EIRP (Effective Isotropically Radiated Power) of all remote antennas by selecting Remote
Antennas > Calculate EIRP from the Transmitters context menu.
You can prevent Atoll from updating the EIRP 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
EIRP from the Transmitters context menu, Atoll will only update the EIRP 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 57) or its position relative to the site (see "Changing the Antenna Position Relative to the Site
Using the Mouse" on page 58).
305
Display Resolution
City Centre
5m
City
20 m
County
50 m
State
100 m
Country
The resolution specified here is only for display purposes. The calculated resolution is independently specified in the
propagation settings. For more information, see "Assigning Propagation Parameters" on page 187.
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the <GUID> and </GUID> tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
Receiver height: This displays the height of the receiver defined in the Calculation Parameters tab of the Network
Settings Properties dialog box
Comments: Specify an optional description of comment for the prediction.
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 99. The Group By and Sort buttons are not available when making a so-called
"global" coverage prediction (e.g., signal level coverage prediction).
The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction).
At the top of the Conditions tab, you can set the range of signal level to be considered for the current prediction. You
can click the down arrow button and select Subcell C Threshold to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range or Global C Threshold to enter
a threshold to be used for all subcells as the lower end of the signal level range.
Server: Select either All, Best Signal Level or Second Best Signal Level:
306
Shadowing taken into account: Select this option to consider shadowing in the prediction. For more information, see
"Modelling Shadowing" on page 506. If you select this option, you can change the Cell edge coverage probability. For
more information, see "Modelling Shadowing" on page 506.
AT332_UMR_E0
Indoor coverage: Select this option to consider indoor losses. Indoor losses are defined per frequency per clutter class.
Reception from Subcells: Select the TRX type to consider from the list.
The contents of this tab depends on the type of prediction. For more information, see "Signal Level Coverage Predictions" on
page 307.
The Display Tab
On the Display tab, you can modify how the results of the coverage prediction will be displayed.
7.2.8.2.1
307
2. Specify the propagation parameters as explained in "Assigning Propagation Parameters" on page 187.
3. In the GSM Transmitters folder, right-click the group of transmitters that you want to study and select Calculations >
Create a New Prediction from the context menu. The Prediction Types dialog box appears.
The Prediction Types dialog box lists the coverage prediction types available. They are divided into Standard Predictions, supplied with Atoll, and Customised Prediction. Unless you have already created some customised predictions,
the Customised Prediction list will be empty.
4. Select Coverage by Signal Level (DL) and click OK. The Coverage by Signal Level (DL) Properties dialog box appears.
5. Configure the parameters in the Properties dialog box as described in "GSM Prediction Properties" on page 306.
The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for
each pixel.
6. 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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
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 in the Network explorer. Atoll automatically locks the results of a
coverage prediction as soon as it is calculated, as indicated by the icon ( ) beside the coverage prediction in the Predictions
folder. When you click the Calculate button ( ), Atoll only calculates unlocked coverage predictions ( ).
7.2.8.2.2
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
308
AT332_UMR_E0
You can also display the best idle mode reselection criterion (C2) by selecting "Best C2" on
the Display tab. This allows you to compare the coverage in idle mode with the coverage
in dedicated mode. For more information on coverage predictions in idle mode, See
"Making a Coverage Prediction by Transmitter Based on the Best Idle Mode Reselection
Criterion (C2)" on page 313.
7.2.8.2.3
Click the down arrow button and select one of the following thresholds:
Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power
reduction) as the lower end of the signal level range.
Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range.
Under Server, select "All" to consider all servers. This option defines the server at which the UL signal level is evaluated.
In the Terminal list, select which terminal type is to be considered on each pixel. The UL transmitted power is
based on the max power of the selected terminal, gains and losses. The UL signal level is then a result of this output
power reduced by the path loss which is identical to the one in DL
For information on the Terminal Specifications dialog box, see "Modelling Terminals" on page 249.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
You can also base the transmitter service areas on the best idle mode reselection criterion
(C2) by selecting "Best C2" on the Display tab. This allows you to compare the coverage in
idle mode with the coverage in dedicated mode. For more information on coverage predictions in idle mode, See "Making a Coverage Prediction by Transmitter Based on the Best
Idle Mode Reselection Criterion (C2)" on page 313.
7.2.8.2.4
"Making a Coverage Prediction by Transmitter Based on the Best Signal Level" on page 310
"Making a Coverage Prediction by Transmitter Based on the Best Signal Level by HCS Layer" on page 310
"Making a Coverage Prediction by Transmitter on HCS servers" on page 311
309
"Making a Coverage Prediction by Transmitter for Highest Priority HCS Server" on page 312
"Making a Coverage Prediction by Transmitter Based on the Best Idle Mode Reselection Criterion (C2)" on page 313.
At the top of the Conditions tab, set the range of signal level to be considered. You can select one of the following
thresholds:
Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power
reduction) as the lower end of the signal level range.
Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range.
Under Server, select "Best Signal Level" to take the best signal level from all servers on all layers into consideration
(for more information, see "Comparing Service Areas in Calculations" on page 484).
Enter an Overlap margin. The default value is "4 dB."
You can select which TRX type to consider by selecting it from the Reception from Subcells list.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
You can also predict which server is second best server on each pixel by selecting "Second
Best Signal Level" on the Conditions tab and selecting "Discrete Values" as the Display
Type and "Transmitter" as the Field on the Display tab.
Making a Coverage Prediction by Transmitter Based on the Best Signal Level by HCS Layer
When you base a coverage prediction by transmitter on the best signal level by HCS layer, Atoll will consider the best signal
level by HCS layer on each pixel. Grouping the results by HCS layer will allow you to quickly select which HCS layer is displayed.
To make a coverage prediction by transmitter based on the best signal level per HCS layer:
1. In the Network explorer, right-click the Predictions folder and select New Prediction from the context menu. The
Prediction Types dialog box appears.
2. Select Coverage by Transmitter (DL) and click OK.
3. Configure the parameters in the Properties dialog box as described in "GSM Prediction Properties" on page 306.
310
AT332_UMR_E0
At the top of the Conditions tab, set the range of signal level to be considered. You can select one of the following
thresholds:
Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power
reduction) as the lower end of the signal level range.
Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range.
Under Server, select "Best Signal Level per HCS Layer" to take the best signal level from all servers on each HCS
layer into consideration (for more information, see "Comparing Service Areas in Calculations" on page 484).
Enter an Overlap margin. The default value is "4 dB."
You can select which TRX type to consider by selecting it from the Reception from Subcells list.
7. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. You can select which
HCS layer to display by clicking the Expand button ( ) to expand the coverage prediction in the Predictions folder and the
selecting only the visibility check box of the HCS layer you want to display.
You can also predict which server is second best server per HCS layer on each pixel by
selecting "Second Best Signal Level per HCS Layer" on the Conditions tab and selecting
"Discrete Values" as the Display Type and "Transmitter" as the Field on the Display tab.
Making a Coverage Prediction by Transmitter on HCS servers
When you base a coverage prediction by transmitter on HCS servers, Atoll will consider the best signal level by HCS layer on
each pixel, assuming the cell edge of each layer is defined by the HCS threshold.
To make a coverage prediction by transmitter on HCS servers:
1. In the Network explorer, right-click the Predictions folder and select New Prediction from the context menu. The
Prediction Types dialog box appears.
2. Select Coverage by Transmitter (DL) and click OK. The prediction Properties dialog box appears.
3. Configure the parameters in the Properties dialog box as described in "GSM Prediction Properties" on page 306.
On the Conditions tab, specify 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. You can click the down
arrow button and select one of the following thresholds:
Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power
reduction) as the lower end of the signal level range.
Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range.
Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level
311
or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations" on
page 484).
Enter an Overlap margin. The default value is "4 dB."
You can select which TRX type to consider by selecting it from the Reception from Subcells list.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Making a Coverage Prediction by Transmitter for Highest Priority HCS Server
When you base a coverage prediction by transmitter for highest priority HCS servers, Atoll will consider the best signal level
of the highest priority on each pixel, assuming priority is a combination of the priority field and the minimum threshold per
HCS layer.
To make a coverage prediction by transmitter for highest priority HCS servers:
1. In the Network explorer, right-click the Predictions folder and select New Prediction from the context menu. The
Prediction Types dialog box appears.
2. Select Coverage by Transmitter (DL) and click OK. The prediction Properties dialog box appears.
3. Configure the parameters in the Properties dialog box as described in "GSM Prediction Properties" on page 306.
4. On the Conditions tab, specify 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. You can click the down
arrow button and select one of the following thresholds:
Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power
reduction) as the lower end of the signal level range.
Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range.
Under Server, select "Highest priority HCS server" to take the best signal level of all the severs on the highest priority HCS layer into consideration, assuming the priority of the layer is defined by its priority field and its signal
level exceeds the minimum HCS threshold defined either at the HCS layer level or specifically for each transmitter
(for more information, see "Comparing Service Areas in Calculations" on page 484).
Enter an Overlap margin. The default value is "4 dB."
You can select which TRX type to consider by selecting it from the Reception from Subcells list.
6. 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 (
312
AT332_UMR_E0
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Making a Coverage Prediction by Transmitter Based on the Best Idle Mode Reselection Criterion (C2)
When you base a coverage prediction by transmitter on the best C2, Atoll will consider the best signal level in idle mode. Such
type of coverage can be used:
to compare idle and dedicated mode best servers for voice traffic
to display the GPRS/EDGE best server (based on the GSM idle mode)
The path loss criterion C1 used for cell selection and reselection is defined by:
C1 = BCCH Reception level - BCCH Reception Threshold
The path loss criterion (GSM03.22) is satisfied if C1>0. The reselection criterion C2 is used for cell reselection only and is
defined by:
C2= C1+ Cell Reselect Offset
To make a coverage prediction by transmitter based on the best signal level:
1. In the Network explorer, right-click the Predictions folder and select New Prediction from the context menu. The
Prediction Types dialog box appears.
2. Select Coverage by Transmitter (DL) and click OK. The prediction Properties dialog box appears.
3. Configure the parameters in the Properties dialog box as described in "GSM Prediction Properties" on page 306.
On the Conditions tab, specify 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. You can click the down
arrow button and select one of the following thresholds:
Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power
reduction) as the lower end of the signal level range.
Global C Threshold: to enter a threshold to be used for all BCCH subcells as the lower end of the signal level
range.
Under Server, select "Best Idle Mode Reselection Criterion (C2)" to consider the best C2 from all servers.
If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability.
For more information, see "Modelling Shadowing" on page 506.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
7.2.8.2.5
313
3. Configure the parameters in the Properties dialog box as described in "GSM Prediction Properties" on page 306.
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. You can click the down
arrow button and select one of the following thresholds:
Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power
reduction) as the lower end of the signal level range.
Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range.
Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming the signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level
or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations" on
page 484).
Enter an Overlap margin. The default value is "4 dB."
If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability.
For more information, see "Modelling Shadowing" on page 506.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
You can select which TRX type to consider by selecting it from the Reception from Subcells list.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
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.
7.2.8.3.1
314
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.
AT332_UMR_E0
7.2.8.3.2
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 7.9).
7.2.8.3.3
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 91.
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 "Geographic Export Zone" on page 68.
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 210.
) in the Radio Planning toolbar. The Point Analysis window appears and the
pointer changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and
the current position. You can move the receiver on the map (see "Moving the Receiver on the Map" on page 203).
2. At the top of the Point Analysis window, select the Reception (
) view.
315
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. 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. Select the HCS Layer and the Subcell to be analysed. If you select nothing from the HCS Layer list, the signals from all
HCS layers will be studied.
4. Click the Options button (
) to display the Calculation Options dialog box and 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. For more information, see "Modelling Shadowing" on page 506.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class. For more information, see "Taking Indoor Losses into Account" on page 203.
5. In the Reception view toolbar, you can use the following tools:
) to copy the content of the view and paste it as a graphic into a graphic editing or word-
Intersection: This display shows the area where both coverage predictions overlap (for example, pixels covered by
both predictions are displayed in red).
Merge: This display shows the area that is covered by either of the coverage predictions (for example, pixels covered
by at least one of the 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).
Value Difference: This display shows the dB difference between any two coverage predictions by signal level. This display option will not be available if the coverage predictions were calculated using different resolutions.
316
AT332_UMR_E0
Figure 7.12: Signal level coverage prediction of network with new base station
Now you can compare the two predictions.
317
Intersection
Merge
Union
Difference
To see the changes that adding a new base station made, choose Difference.
5. Click OK to create the comparison. The comparison in Figure 7.13, shows clearly the area covered only by the new
base station.
318
AT332_UMR_E0
Intersection
Merge
Union
319
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 predictions 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 7.16, shows clearly the increase in coverage due to the
change in antenna tilt.
7.2.8.6.1
320
Load conditions: Select "(Cells table)" to calculate the multi-point analysis using the load conditions defined in the
cells table. Select a simulation or a group of simulations to calculate the multi-point analysis using the load conditions
calculated by Monte Carlo simulations.
HCS Layer: Select the HCS layer for which you want to run the analysis.
Interference: Select the source of interference to be taken into account in the calculations, "Co-channel", "Adjacent",
or both.
Based on: Select "C/I" or "C/I+N".
Shadowing taken into account: Select this option to consider shadowing in the prediction. For more information, see
"Modelling Shadowing" on page 506. If you select this option, you can change the Cell edge coverage probability.
Indoor coverage: Select this option to consider indoor losses. Indoor losses are defined per frequency per clutter class.
AT332_UMR_E0
Position Id: The indexes of the points used for the multi-point analysis.
X and Y: The coordinates of the points used for the multi-point analysis.
Height (m): The height of the points used for the multi-point analysis.
Service: The services assigned to the points used for the multi-point analysis.
Terminal: The terminals assigned to the points used for the multi-point analysis.
Mobility: The mobility types assigned to the points used for the multi-point analysis.
7.2.8.6.2
Importing a list of points from an external file: Click the Actions button and select Import Table from the menu to
open the Open file dialog box. In this dialog box, select a TXT or CSV file containing a list of points and click Open.
For more information on importing data tables, see "Importing Tables from Text Files" on page 88.
Importing a list of points from a fixed subscriber traffic map: Click the Actions button and select Import from Fixed
Subscribers from the menu to open the Fixed Subscribers dialog box. In this dialog box, select one or more existing
fixed subscriber traffic maps and click OK.
Copying a list of points from an external file.
Creating points in the list by editing the table: Add new points by clicking the New Row icon ( ) and entering X
and Y coordinates as well as a service, a terminal, and a mobility.
The list of points must have the same coordinate system as the display coordinate system
used in the Atoll document. For more information on coordinate systems, see "Setting a
Coordinate System" on page 41.
It is also possible to leave the Points tab empty and add points to the analysis on
the map using the mouse once the point analysis item has been created. To add
points on the map using the mouse, right-click the point analysis item to which you
want to add points, and select Add Points from the context menu. The mouse
pointer changes to point creation mode (
want to add. Press ESC or click the Pointer button ( ) in the Map toolbar to finish
adding points.
You can also export the list of point from a point analysis to ASCII text files (TXT and
CSV formats) and MS Excel XML Spreadsheet files (XML format) by selecting
Actions > Export Table. For more information on exporting table data, see
"Exporting Tables to Text Files and Spreadsheets" on page 86.
4. On the Display tab, specify how to display point analysis results on the map according to any input or calculated
parameter. For more information on defining display properties, see "Setting the Display Properties of Objects" on
page 51.
5. Once you have defined the point analysis parameters, you can calculate it immediately or you can save it and calculate
it later:
Calculate: Click Calculate to save the point analysis and calculate it immediately.
OK: Click OK to save the point analysis without calculating it. You can calculate it later by opening the point analysis
properties and clicking the Calculate button.
Once Atoll has finished calculating the point analysis, the results are displayed in the map window. You can also access the
analysis results in a table format. For more information, see "Viewing Point Analysis Results" on page 322.
You can also organise point analyses in folders under the Multi-point Analysis folder by creating folders under the Multi-point
Analysis folder in the Network explorer. Folders may contain one or more point analyses items. You can move point analyses
items from one folder to another and rename folders.
321
7.2.8.6.3
Position Id: The indexes of the points used for the multi-point analysis.
X and Y: The coordinates of the points used for the multi-point analysis.
Height (m): The height of the points used for the multi-point analysis.
Service: The services assigned to the points used for the multi-point analysis.
Terminal: The terminals assigned to the points used for the multi-point analysis.
Mobility: The mobility types assigned to the points used for the multi-point analysis.
Transmitter: Names of the potential serving transmitters.
Distance (m): Distances from the potential serving cells.
BCCH - C (dBm): BCCH signal level.
BCCH - C/I (dB): BCCH signal quality.
Min C/I (dB): Minimum signal quality.
TRX: Name of the TRX.
Figure 7.17: GSM handover area between a reference cell and a potential neighbour
322
AT332_UMR_E0
When it is cleared, only the defined Distance will be used to allocate neighbours to a reference cell.
When it is selected, click Define to open the Coverage Conditions dialog box:
Figure 7.18: GSM coverage conditions for automatic intra-technology neighbour allocation
Resolution: Enter the resolution to be used to calculate cells coverage areas during automatic neighbour allocation.
Global reception threshold: Enter the minimum signal level which must be provided by reference cell A and
potential neighbour cell B.
Handover start (HO margin): Enter the signal level which indicates the beginning of the handover margin. The
handover start must be outside of the best server area of the reference cell.
Handover end: Enter the signal level indicating the end of the handover margin. The handover end must exceed
the value entered for the Handover start. The higher the value entered for the Handover end, the longer the list
of potential neighbours. The area between the Handover start and the Handover end constitutes the area in
which Atoll will search for neighbours.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability. For more information, see
"Modelling Shadowing" on page 506.
Indoor Coverage: Select this check box to take indoor losses into acccount in calculations. Indoor losses are
defined per frequency per clutter class.
Co-site transmitters as neighbours: cells located on the same site as the reference cell will automatically be considered as neighbours. A transmitter with no antenna cannot be considered as a co-site neighbour.
Adjacent neighbours: cells that are adjacent to the reference cell will automatically be considered as neighbours.
Adjacent HCS layer neighbours: cells that have HCS layer adjacency with the reference cell will automatically be considered as neighbours.
Symmetric relations: Select this check box if you want the neighbour relations to be reciprocal, i.e. any reference cell
is a potential neighbour of all the cells that are its neighbours.
Exceptional pairs: Select this check box to force the neighbour relations defined in the Intra-technology Exceptional
pairs table. For information on exceptional pairs, see "Exceptional Pairs" on page 223.
Description
When
Distance
Coverage
Co-Site
323
Cause
Description
When
Adjacent
Adjacent layer
Symmetry
Exceptional Pair
Exceptional pairs
is selected
Existing
When it is cleared, only the defined Distance will be used to allocate neighbours to a reference cell.
When it is selected, click Define for GSM to open the corresponding Coverage Conditions dialog box:
Figure 7.19: GSM coverage conditions for automatic inter-technology neighbour allocation
Resolution: Enter the resolution to be used to calculate cells coverage areas during automatic neighbour allocation.
Global reception threshold: Enter the minimum signal level which must be provided by reference cell A and
potential neighbour cell B.
Margin: Enter a handover margin.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability. For more information, see
"Modelling Shadowing" on page 506.
Indoor Coverage: Select this check box to take indoor losses into acccount in calculations. Indoor losses are
defined per frequency per clutter class.
324
Co-site neighbours: cells located on the same site as the reference cell will automatically be considered as neighbours.
A cell with no antenna cannot be considered as a co-site neighbour.
Exceptional pairs: Select this check box to force the neighbour relations defined in the Intra-technology Exceptional
pairs table. For information on exceptional pairs, see "Exceptional Pairs" on page 223.
AT332_UMR_E0
Description
When
Distance
Coverage
Co-Site
Exceptional Pair
Exceptional pairs
is selected
Existing
OMC traffic data: You can use OMC traffic data to calculate traffic demand and import the traffic demand into the
Subcells Table: Traffic Data.
Traffic captures: You can import traffic demand information from traffic maps and then use this information to create
a traffic capture.
Simulations: Like for the traffic captures, you can import traffic demand from traffic maps and then use this information to create one or several simulations.
A traffic capture is based on a macroscopic description of traffic as defined by one or more traffic maps. In a traffic capture,
the total traffic is broken down per transmitter, respecting the compatibility between the traffic and the transmitter. For
example, if two transmitters cover the same traffic:
The result of the traffic capture is the demand per transmitter, broken down by subcell, service, terminal, and mobility, in
terms of Kbps for packet-switched traffic (maximum bit rate or constant bit rate) and Erlangs for circuit-switched traffic. This
breakdown is made on the service zones defined for each subcell, as defined by the parameters set on the Conditions tab of
the traffic captures Properties dialog box.
Compared to a traffic capture, a simulation is based on a realistic distribution of voice or packet 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 UL and DL C/(I+N) for each mobile, the required power and the obtained coding (codec or
coding scheme) of the mobile, the DL/UL Traffic Load, the mean power control gain, the DL DTX gain and the Half-rate traffic
ratio of each subcell. 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.
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.
For information on studying network capacity in Atoll, see Chapter 6: Traffic and Capacity Planning.
This section covers the following topics for GSM networks:
"Importing OMC Traffic Data into the Subcells Table: Traffic Data" on page 326
"Defining Multi-service Traffic Data" on page 326
"Calculating and Displaying a Traffic Capture" on page 327
"Dimensioning a GSM/GPRS/EDGE Network" on page 330.
325
7.3.1 Importing OMC Traffic Data into the Subcells Table: Traffic
Data
As explained in "Subcell Properties" on page 282, subcell data is displayed in three subcell tables: Standard Data, Traffic Data,
and AFP Data. The data in the Subcells Table: Traffic Data can be used for a variety of different purposes in Atoll:
You can use OMC traffic data as a source of accurate traffic data and import it into the Subcells Table: Traffic Data. The first
step in using OMC traffic data is ensuring that the data is available in a form usable by Atoll. Normally, OMC traffic data is
measured in kbits instead of timeslots.
The major drawback of this method is the fact that, in many cases, the packet-switched OMC traffic demand is available in
kbits instead of timeslot units. In order to correctly translate Kbits into timeslots, you must create traffic maps as described in
the sections below. The traffic capture will analyse the radio conditions at each point, defining the coding schemes, modulation, and bit rates, in order to calculate how many timeslots are required for a given demands of kbits.
It is very common to use traffic maps based on OMC data per transmitter for the purpose
of retrieving interference matrices based on traffic. The best method of working with an
AFP is to use the OMC data of the subcells table and to generate interference matrices
based on clutter weighting as explained in "Calculating an Interference Matrix Based on
Clutter Weighting" on page 355.
Once the data has been converted into timeslots, you can import it into the Subcells Table: Traffic Data.
To import OMC traffic data into the Subcells Table: Traffic Data:
1. Select the Network explorer.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Subcells > Subcells Table: Traffic Data from the context menu. The Subcells Table: Traffic Data opens.
After modifying the available OMC data to change it from served traffic to traffic demand, you can import the following data
into the Subcells Table: Traffic Data:
For more information on working with data tables in Atoll, see "Data Tables" on page 75.
Codec Modes: Codecs are used by the network to compress voice and, as a consequence, to increase the voice traffic
in the network. The Codec Modes table lists all the available codec modes. Codec modes can be selected according to
radio conditions. Mappings between quality and codec modes are listed in the Codec configuration table. You can
create new codec configurations and modify existing ones by using the Codec Configuration table. For information on
codec mode configurations, see "Codec Configuration" on page 492.
Coding Schemes: Coding Schemes are used by the network for carrying packet-switched data. The Coding Schemes
table lists all the available coding schemes. Coding Schemes can be selected according to radio conditions. Mappings
between quality and coding schemes are listed in the Coding Schemes configuration table. You can create new coding
scheme configurations and modify existing ones by using the Coding Scheme Configuration table. For information on
coding scheme configurations, see "Coding Scheme Configuration" on page 495.
Services: Services are the various services, such as voice, VoIP, mobile internet access, etc., available to subscribers.
These services can be either circuit-switched or packet-switched. There are two types of packet-switched services:
max. bit rate or constant bit rate (e.g., VoIP). For each service, quality targets, such as quality of service in Erlangs for
circuit-switched services, are defined for network dimensioning. For information on modelling end-user services, see
"Modelling Services" on page 241.
326
AT332_UMR_E0
Mobility types: In GSM/GPRS/EDGE, information about receiver mobility is important to efficiently manage connections: a mobile used by a driver moving quickly or a pedestrian will not necessarily be connected to the same HCS layer.
For information on creating a mobility type, see "Modelling Mobility Types" on page 247.
Terminals: In GSM/GPRS/EDGE, 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. It is defined to ensure compliancy between transmitter equipment and supported frequency bands and GPRS/EDGE parameters. For information on creating a terminal, see "Modelling Terminals" on page 249.
Instead of using a default traffic capture, you can import the actual network traffic directly into the Subcells Table: Traffic Data
(see "Dimensioning a GSM/GPRS/EDGE Network" on page 330 for more information).
In this section, the following are explained:
A valid traffic map (see "Working with Traffic Maps" on page 256)
Correct GPRS-related parameters (see "Creating or Modifying a Base Station Element" on page 289), including:
Target rate for traffic overflow defined for subcells (see "Subcell Properties" on page 282)
Correctly defined service zones (see "Creating a Traffic Capture" on page 327)
Correctly defined HCS layers (see "Setting HCS Layers" on page 484).
Name: By default, Atoll names traffic captures sequentially. You can change the assigned name.
Comments: You can enter comments in this field if you want.
Filter: You can select the transmitters to be considered in the traffic capture by clicking the Filter button. For information on using the Filter dialog box, see "Advanced Data Filtering" on page 101.
Global Scaling Factor: If desired, enter a scaling factor to increase user density.
327
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 throughputs/users (for sector traffic maps). For information on
using the global scaling factor, see "Creating Simulations" on page 266.
Select Traffic Maps to Be Used: Each available traffic map in the project can be used for the current traffic capture
by assigning its traffic to all HCS layers (default mode) or by restricting its spread to a specific HCS layer. In order
to make the traffic capture, you must select at least one traffic map and assign its traffic to a single HCS layer or
to all.
Assigning traffic to all HCS layers means that for a given traffic map, its traffic will overflow from lowest to highest
priority layers as explained in "Subcell Properties" on page 282 and in Figure 7.5 on page 286. If the traffic of a map
is assigned to a specific layer, its traffic is only captured on that layer and the traffic only overflows within concentric cells.
You can select traffic maps of any type. However, if you have several different types of traffic maps and want to
make a traffic capture 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 "Working with Traffic Maps" on page 256.
6. Click the Conditions tab. The parameters on the Conditions tab define how the service zone for each transmitter and
the number of timeslots for circuit and packet services will be calculated.
7. Under Coverage Conditions, set the following parameters to define how the service area of each transmitter will be
calculated:
Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level
or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations" on
page 484).
Enter an Overlap margin. The default value is "4 dB."
If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability.
Shadowing margins (depending on the entered cell edge coverage probability and the model standard deviation
per clutter class) are applied to the values for C. For more information, see "Modelling Shadowing" on page 506.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
If shadowing is taken into account, the CI standard deviation per clutter class is used to
estimate the shadowing losses on the calculated CI values.
8. Under GPRS/EDGE, you can set the parameters to define how the number of timeslots for circuit and packet services
will be calculated. Select one of the following to define how the calculations in the traffic capture are going to be
made:
Select Calculations Based on C if you want to base the traffic capture on CN. Continue to step 14.
Select Calculations Based on CI and continue with the following step.
9. Select the DTX taken into account check box and enter the percentage of time during which a user is talking in the
Voice Activity Factor text box, if you want discontinuous transmission mode for TRXs which support it taken into
account.
10. From the Interference Sources list, select whether the interference should be calculated from adjacent channels, cochannels, or from both. The adjacent channel effect on the victim channel, i.e., the interference, is decreased by the
adjacent channel protection level.
Inter-technology interference is taken into account by default. For more information, see
"Modelling Inter-technology Interference" on page 624. By adding an option in the Atoll.ini
file, you can add an Inter-technology check box which will allow you to consider or not
inter-technology interference.
11. Select the Traffic Load that will be used to calculate interference:
12. Select the Ideal Link Adaptation check box if you want the coding scheme that offers the highest throughput for a
given C or CI to be selected. Otherwise, Atoll will choose the coding scheme by considering only the coding scheme
admission threshold in terms of C and/or CI.
13. Select the Thermal Noise Taken into Account check box if you want Atoll to consider thermal noise.
14. Click Calculate.
328
AT332_UMR_E0
After the traffic capture has been completed, two new tabs appear on the traffic capture Properties dialog box with
the results. For a detailed explanation of the results, see "GSM/GPRS/EDGE Traffic Capture Results" on page 329.
Results per Transmitter: The results on the Results per Transmitter tab give the traffic allocated to each transmitter:
Circuit demand (Erlangs): The total circuit-switched traffic demand in Erlangs for that transmitter. This is calculated by summing the circuit-switched traffic in Erlangs per pixel in the transmitter coverage area.
Circuit average demand (Timeslots): The average demand on circuit timeslots takes into consideration the effect
of half-rate circuit-switched traffic carried by the transmitter, i.e., it takes into consideration the fact that 2 halfrate users are equivalent to 1 full-rate user in terms of Erlangs of traffic.
Packet demand (Kbps): The total traffic demand in kilobits per second generated by the packet-switched users
within the coverage area of the transmitter.
Packet average demand (Timeslots): The number of timeslots needed to meet the packet traffic demand depends
on the maximum throughput that a packet timeslot can support.
Average Packet Timeslot Capacity (Kbps): The average packet timeslot capacity is calculated according to the
propagation conditions on each pixel of the transmitter coverage area. When calculating the traffic capture, you
can choose to base this on carrier power or on interference (C or CI).
Results per Subcell: The results on the Results per Subcell tab give the traffic per subcell. For each subcell (except for
the BCCH, which captures the same traffic as the corresponding TCH), Atoll indicates the types of traffic assigned by
service, mobility, and terminal and displays:
Packet Demand (Kbps): The total traffic demand in kilobits per second generated by the packet-switched users
within the coverage area of the transmitter.
Circuit Demand (Erlangs): The total circuit-switched traffic demand in Erlangs. In case of circuit switched services,
it depends whether the subcell supports half-rate traffic.
If the percentage of half-rate traffic of the subcell is 0, the average demand in circuit timeslots will be the same as
the traffic demand in Erlangs and the number of used timeslots will be the same as the traffic demand. If there is
a certain percentage of half-rate traffic, the number of used timeslots will depend on the percentage of traffic using half-rate connections.
Average demand (Timeslots): The average number of timeslots needed to match the demand in circuit-switched
and packet-switched traffic.
The demand in packet timeslots depends on the maximum throughput that a timeslot can support. Therefore, it
depends on the average timeslot capacity within the transmitter coverage area, which in turn depends on the
propagation conditions.
The traffic capture results provide traffic per transmitter. You can retrieve the amount of
traffic (Erlangs for circuit services, Kbps for max bit rate packet services) defined in the
input traffic map in output as follows:
1. Create a sector traffic map per HCS layer (see "Creating a Sector Traffic Map" on
page 257) based on a best server coverage prediction (HCS server option with
0 dB overlap margin). As a result, you will have as many sector traffic maps as the
number of HCS layers.
2. Create a traffic capture (HCS server option with 0 dB overlap margin) where the
traffic of each map is assigned to its respective layer (see "Creating a Traffic Capture" on page 327).
As a result, each transmitter will have the same amount of traffic (Erlangs for circuit
services, Kbps for max bit rate packet services) as the transmitter in the selected traffic
maps used for input. Constant bit rate services cannot be treated in the same way since
their input traffic is stated in Erlangs whereas the corresponding demand is evaluated in
Kbps as with any other packet-switched service.
For more information on how the results are calculated and on the formulas used, see the Technical Reference Guide.
329
Properties: Select Properties to open the traffic captures Properties dialog box. You can review the results of the
traffic capture, or change the parameters and recalculate the traffic capture. For a description of the results, see
"GSM/GPRS/EDGE Traffic Capture Results" on page 329. For information on the parameters available, see "Creating a Traffic Capture" on page 327.
Default: Select Default to set the current traffic capture as the default traffic capture. The default traffic capture
( ) is the one used to:
During dimensioning, Atoll evaluates a number of TRXs so as to have enough circuit timeslots (shared and dedicated) to match
the circuit traffic demand with the quality requirements defined in circuit-switched services (Erlang B or C). Then, Atoll calculates how many TRXs must be added to meet packet traffic demand, using the quality charts defined in the dimensioning
model.
In this section, the following are explained:
330
AT332_UMR_E0
e. Select Properties from the context menu. The Properties dialog box appears.
3. Click the General tab. You can set the following parameters:
Name: Atoll assigns a Name to the dimensioning model. You can change the default name, if desired.
Max. Number of TRXs per Transmitter: Enter the maximum number of TRXs that a transmitter can have. During
dimensioning, this value is used for transmitters for which this value is not defined on the TRXs tab of the Properties dialog box (see "Subcell Properties" on page 282).
Under Circuit:
Queuing Model: Enter the queuing model for GSM voice calls (Erlang B or Erlang C).
Under Packet:
Min. number of packet-dedicated timeslots per transmitter: Enter the minimum number of dedicated packetswitched timeslots that must be reserved for each transmitter.
Max. number of additional TRXs for packet services: Enter the maximum number of TRXs that can be added for
the subcell to satisfy the demand for packet-switched services after Atoll has dimensioned the circuit-switched
services.
KPIs to Take into Account: Select the key performance indicators you want taken into account during dimensioning. The values of the key performance indicators are defined by the quality graphs on the Quality Graphs tab
of the dimensioning model Properties dialog box.
Min. Throughput: Select the Min. Throughput check box if you want to take minimum required throughput
(or the guaranteed bit rate for constant bit rate packet-switched services) into account when performing dimensioning.
From the point of view of a GPRS/EDGE user, throughput is the average maximum throughput experienced by
the mobile terminal during a data call. If there is more than one user multiplexed on the same timeslot, which
occurs when the system accommodates many users, each multiplexed user will experience a reduction in
throughput. This reduction in throughput is described by the reduction factor defined in the reduction factor
graph. A reduction factor of 1, or almost 1, means that each user has the maximum throughput that a timeslot
can offer in a given environment (the maximum throughput per timeslot, in turn, depends on the carrier power and/or CI ratio at a given location). As the system load increases, the reduction factor starts decreasing,
corresponding to the decrease in throughput per user.
Max. Blocking Rate: Select the Max. Blocking Rate check box if you want to take blocking probability into
account when performing dimensioning.
The blocking probability and the delay in the GPRS/EDGE system are closely related. A user starts to experience more delay in service when the system is near saturation and the incoming packets are placed in a waiting queue as there are no resources available for immediate transfer. This buffering of packets is related to
the load of the system. The blocking probability is the probability that an incoming packet be placed in a
queue. The delay is the average delay the packet will undergo due to blocking as it waits its turn to be transmitted when resources are available.
In GPRS and EDGE, the term "system load" refers to the ratio of the number of used packet
timeslots to the number of packet switching (shared and dedicated) timeslots available in
the system.
Max. Delay: Select the Max. Delay check box if you want to take delay into account when performing dimensioning.
The delay is the average delay the packet will undergo due to blocking as it waits its turn to be transmitted
when resources are available.
The delay can be restricted to an allowed maximum in the properties of the service.
If the dimensioning model takes into account all three KPIs, the following conditions are
satisfied when the number of TRXs to add for packet service is calculated:
The throughput must be greater than the minimum throughput (or the guaranteed
bit rate for constant bit rate packet-switched services) even if a reduction factor is
applied to the throughput.
The delay and the blocking rate must be lower than the maximum delay and maximum blocking rate, respectively.
4. Click the Quality Charts tab. The Quality Charts tab displays the throughput reduction factor, delay, and blocking
probability graphs used for dimensioning packet switched traffic. The graphs are calculated as a function of the system
load, which is defined as the ratio of the number of used packet timeslots to the number of packet switching (shared
and dedicated) timeslots available in the system.
331
You can modify or replace the quality graphs with graphs generating using a third-party simulator.
If the quality graphs are modified incorrectly, the dimensioning and quality analysis
results that are based on the quality graphs will also be incorrect.
For the moment, Atoll does not provide a default delay graph; if desired, you can
enter your own values.
The blocking rate graph is based on a user multiplexing factor of 8. The user multiplexing factor corresponds to the number of timeslots on a GSM/GPRS/EDGE
frame.
5. Click OK.
Either a default traffic capture (for information on creating a traffic capture, see "Calculating and Displaying a Traffic
Capture" on page 327) or alternatively a populated traffic data part of the subcells table (see "Subcell Properties" on
page 282).
If you have modified the traffic map, traffic parameters, or transmitter properties (e.g.,
calculation area, coding scheme configuration, etc.), since creating the traffic capture, you
must recalculate the traffic capture before dimensioning.
A dimensioning model (for information on creating a or modifying a dimensioning model, see "Defining a GSM/GPRS/
EDGE Dimensioning Model" on page 330).
332
AT332_UMR_E0
4. Under Dimensioning parameters, select the dimensioning model from the Model list.
5. Under Traffic (circuit and packet demand), select whether the dimensioning is to be based on the traffic demand computed in the default traffic capture of from the current values (circuit and packet demands) in the subcells table.
If you selected "From subcell table," you will define the following additional parameters:
Specify the minimum throughput reduction factor that can be accepted in the network. When calculating a
traffic capture, this parameter is evaluated (but not displayed) during the calculation. The minimum throughput reduction factor models the fact that at the user level, the user throughput can be reduced due to how
much it will be multiplexed with other users. In other words, this parameter will be affected by the traffic load
which is a consequence of the dimensioning.
Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages
must equal 100.
Under Circuit Services (%), enter the percentage of each type of circuit service used in the map. The total
percentages must equal 100.
Under Packet Services (%), enter the percentage of each type of packet service used in the map (assuming the
packet services consist of max bit rate and constant bit rate packet services). The total percentages must equal
100.
TRX Type: For each transmitter, the results are given by TRX type (e.g., BCCH, TCH, TCH_EGPRS and TCH_INNER).
Together, the Transmitter and TRX Type columns identify the subcell.
Initial required number of TRXs: This is the required number of TRXs before dimensioning. For example, this value
might come from the actual number of TRXs or it might be the result of an estimate the number of required TRXs.
Required Number of TRXs: The number of TRXs required to satisfy both the subcell's circuit-switched and packetswitched traffic, while taking into account the quality of service criterion assigned for each.
The required number of TRXs is the most important result of the dimensioning process. If the number of required
TRXs exceeds the maximum number of TRXs per transmitter, Atoll displays the results for the subcell in red.
Required TRXs to add: The required TRXs to add is the difference between the obtained required number of TRXs
(before the dimensioning process) and the initial required number of TRXs. If the value is positive, it means that
the current dimensioning process has evaluated than more TRXs than the initial estimated value are needed to
absorb the traffic.
Load (%): The average demand in timeslots (packet and circuit), divided by the total number of timeslots available.
It represents the average occupancy of the TRXs. This parameter is one of the principal results of dimensioning
along with the number of TRXs. It is assigned to subcell pools when committing the results of dimensioning.
Multiplexing Factor: The user or Temporary Block Flow (TBF) multiplexing factor. The multiplexing factor is an
input of the dimensioning process. It corresponds to the number of packet switched service users that can be multiplexed onto the same timeslot in GPRS and EDGE.
Maximum Number of TRXs per Transmitter: The maximum number of TRXs that a transmitter can support is an
input of the dimensioning process. This parameter is provided by the equipment manufacturer. The value can be
set for each transmitter or taken from the dimensioning model for transmitters where this value is not set.
Target Rate of Traffic Overflow (%): This input parameter defines the percentage of traffic that is allowed to overflow from one subcell to another in case the traffic assigned to this subcell is greater than the maximum traffic
that it can accommodate. It can be considered an anticipation of the percentage of traffic that will be rejected
from higher priority subcells or layers to lower ones. The value is specified for each subcell.
Half-rate Traffic Ratio (%): This input parameter is defined per subcell and indicates the percentage of subcell
traffic that uses half-rate access.
If the values are different for BCCH and TCH subcells, Atoll will use the values for the target rate of traffic overflow
and the half-rate traffic ratio from the BCCH subcell.
Packet demand (Kbps): The Packet Traffic Demand is the total traffic demand in kilobits per second generated by
packet switched service users within the coverage area of the transmitter. This parameter comes from the traffic
capture or from the Subcells table, depending on the source you chose for the traffic demand. It is assigned to
subcell pools when committing the results of dimensioning.
Packet average demand (Timeslots): The number of timeslots needed to satisfy the packet traffic demand
depends on the maximum throughput that a packet timeslot can support.
Circuit Demand (Erlangs): The Circuit Traffic Demand is the total traffic demand in Erlangs generated by circuitswitched-service users within the coverage area of the transmitter. This parameter comes from the traffic capture
or from the subcells table, depending on the user selection for the traffic demand source. It is assigned to subcell
pools when committing the results of dimensioning.
333
Circuit average demand (Timeslots): The Average Demand in Circuit Timeslots is calculated taking into account
the effect of half-rate circuit-switched traffic: two half-rate users are equivalent to one full-rate user.
Served Circuit Traffic (Erlangs): The Served Circuit Traffic is the circuit-switched traffic in Erlangs that the subcell
can potentially serve, if the dimensioning results are applied. The served circuit-switched traffic is circuit traffic
demand less the effective overflowed circuit traffic.
Served Packet Traffic (Kbps): The Served Packet Traffic is the packet-switched traffic in kilobits per second that
the subcell can potentially serve, if the dimensioning results are applied. The served packet-switched traffic is
packet traffic demand less the effective overflowed packet traffic.
Effective Rate of Traffic Overflow (%): The Effective Rate of Traffic Overflow is the actual rate of traffic that is
rejected by the subcell because of a lack of packet timeslots. In a GSM network, the value is the same as the
blocking probability. In a more complex network, this value includes the traffic overflow from all services.
For Erlang B, the effective rate of traffic overflow corresponds to the effective blocking rate. This value is calculated from the required number of circuit timeslots (both shared and circuit timeslots) and the circuit traffic demand
in Erlang B tables.
For Erlang C, the effective rate of traffic overflow is zero except if the maximum number of TRXs is exceeded. The
effective blocking rate is inferred from the required number of circuit timeslots (both shared and circuit timeslots)
and the circuit traffic demand in Erlang C tables.
Circuit Blocking Rate (/Delay) (%): The Circuit Blocking Rate is the grade of service (GoS) indicator for circuitswitched traffic. It can be either the rate at which calls are blocked (Erlang B) or delayed (Erlang C), depending on
which queuing model the dimensioning model uses.
Minimum Throughput Reduction Factor (%): The Minimum Throughput Reduction Factor is the lowest
throughput reduction factor that can still guarantee service availability. The Minimum Throughput Reduction
Factor is one of the criteria for packet-switched traffic dimensioning. It is calculated using the parameters defined
for the services: the minimum service throughput (or the guaranteed bit rate for constant bit rate packet-switched
services); the maximum number of timeslots per connection; the required availability; and the per pixel timeslot
capacity of the subcell coverage area. This parameter is calculated when making the traffic capture or is userdefined, depending on the source of traffic demand on which the dimensioning is based.
Throughput Reduction Factor (%): The Throughput Reduction Factor is calculated from the quality charts using
the packet load and available connections for each subcell. This reduction factor must be greater than the minimum throughput reduction factor for packet-switched services for these services to be satisfactorily available in
the subcell.
Maximum Delay (s): The Maximum Delay is the defined delay in seconds that must not be exceeded for the service quality to be considered satisfactory.
Delay (s): The Delay is a key performance indicator (KPI) calculated using the quality graphs, the load, and the
number of connections available. This dimensioning output must not exceed the maximum delay defined for the
service for service availability to be considered satisfactory.
Maximum Packet Blocking Rate (/Delay) (%): The Maximum Packet Blocking Rate is defined for each packet service and is the highest probability that the service will be blocked that is acceptable in terms of service availability.
Packet Blocking Rate (Delay) (%): The Packet Blocking Rate is a dimensioning output and must not exceed the
Maximum Packet Blocking Rate defined for the service for service availability to be considered satisfactory.
334
AT332_UMR_E0
This section explains the specific mechanisms that are used to calculate GSM/GPRS/EDGE traffic simulations. For information
on working with traffic simulations in Atoll, see "Simulations" on page 265
7.3.5.1.1
MSA Definition
In order to understand the difference between each frequency hopping mode from the point of view of a mobile, you can
consider the Mobile Station Allocation. MSA is characterised by the pair channel list and MAIO. In the following, this concept
of MSA will be used to characterise the interference and resources set of a mobile.
For non-hopping (NH) mode, the channel list is 1 channel. For base-band hopping (BBH) or synthesised frequency hopping
(SFH), the channel list corresponds to the mobile allocation list (MAL).
For BBH, channels of MAL belong to the same TRX type.
Examples:
For NH, you have:
TRX index
Channel list
MAIO
MSA
53
(53,*)
54
(54,*)
For BBH, if you assume TRXs belong to the same TRX type, you have:
TRX index
Channel list
MAIO
MSA
53
([53,54,55],0)
54
([53,54,55],1)
55
([53,54,55],2)
TRX index
Channel list
MAIO
MSA
53 54 55 56
([53,54,55,56],2)
53 54 55 56
([53,54,55,56],3)
Therefore, from the point of view of a mobile station, BBH and SFH work in the same way. An MSA will be attached to each
mobile considered during the simulation and the level of interference will be evaluated on this MSA.
7.3.5.1.2
335
336
AT332_UMR_E0
4. It equally shares the remaining resources to packet-switched users who did not reach their maximum throughput
demands. Resources and throughputs are finally assigned to each packet-switched user.
5. It updates the DL traffic loads, power control gains, DTX gains, and half-rate traffic ratios of all the subcells according
to the resources in use and the total resources.
6. It updates the UL traffic loads of all the subcells and the UL noise rises of all the TRXs according to the resources in use
and the total resources.
7. It performs a convergence test to see whether the differences between the current and the new loads and noise rises
are within the convergence thresholds.
8. Repeats the previous steps (from step 2. to step 7.) for the iteration k+1 using the new calculated load conditions as
the current load and noise rise.
At the end of the simulations, active users can be connected in the direction corresponding to their activity status if:
If users are rejected during server determination, the cause of rejection is "No Coverage". If users are rejected because quality
is too low to obtain any codec mode or coding scheme, the cause of rejection is "No Service". If users are rejected because
they cannot be allocated a sufficient number of resources to obtain the codec mode or coding scheme, the cause of rejection
is "Resource Saturation," i.e., all of the cells resources were used up by other users.
7.3.5.2.1
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 throughputs that all active users could theoretically generate are provided.
The breakdown per service (total number of users, number of users per activity status) is given.
The Sites tab: The Sites tab contains the following information per site:
DL and UL Throughput for Each Service: The throughput in kbitss for each service. The result is detailed on the
downlink and uplink only when relevant.
337
The Subcells tab: The Cells tab contains the following information, per transmitter and TRX Type:
The TRXs tab: The TRXs tab contains the following information:
Hopping Mode: The hopping mode of the subcell to which the TRX belongs
Channels: The channel list to which the TRX is part of. In case of non hopping, it corresponds to a unique channel.
In case of any hopping mode, it corresponds to a MAL.
MAIO: The MAIO defined at this TRX in case of SFH only
TRX Rank: The rank assigned to the TRX during an automatic frequency allocation
Intra-technology UL Noise Rise (dB): the resulting noise rise caused by the surrounding UL traffic at the TRX. This
result is the output which can be committed to the TRXs table.
The Mobiles tab: The Mobiles tab contains the following information:
338
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.
Connection Status: The connection status indicates whether the user is connected 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.
Server: The transmitter serving the mobile on its MSA.
HCS Layer: The HCS Layer of the serving cell
Best Server Signal Level (dBm): The received signal strength of the serving cell.
Frequency Band: The frequency band used by the transmitter-mobile link.
TRX Type: The TRX type of the subcell to which the mobile is attached.
DL Requested Throughput (kbps): The DL max throughput demand defined in the service.
DL Obtained Throughput (kbps): The DL obtained throughput depending on the resources allocated to the user.
This value must be between the minimum and the maximum throughput demands.
UL Requested Throughput (kbps): The UL max throughput demand defined in the service.
UL Obtained Throughput (kbps): The UL obtained throughput depending on the resources allocated to the user.
This value must be between the minimum and the maximum throughput demands.
Timeslots (DL): the number of DL timeslots used. It should be 0 if it is not connected. Then for circuit-switched
services, depending on the served codec mode, it can be 0,5 or 1, but has to be the same as for UL. For packetswitched services, this is the number of timeslots corresponding to the DL total obtained throughput.
Timeslots (UL): the number of UL timeslots used. It should be 0 if it is not connected. Then for circuit-switched
services, depending on the served codec mode, it can be 0,5 or 1, but has to be the same as for DL. For packetswitched services, this is the number of timeslots corresponding to the UL total obtained throughput.
Initial C/(I+N) (DL) (dB): The C/(I+N) of the served MSA at the user location in the downlink before power control.
Final C/(I+N) (DL) (dB): The C/(I+N) of the served MSA at the user location in the downlink after power control.
Target Threshold (DL) (dB): The DL C/(I+N) to get the coding (coding scheme of codec mode) at the current location.
Initial C/(I+N) (UL) (dB): The C/(I+N) of the served MSA at the serving cell in the uplink before power control.
Final C/(I+N) (UL) (dB): The C/(I+N) of the served MSA at the serving cell in the uplink after power control.
Target Threshold (UL) (dB): The UL C/(I+N) to get the coding (coding scheme of codec mode) at the serving cell.
Mobile Total Power (dBm): The mobile total power corresponds to the total power transmitted by the terminal.
Channels: The channel or list of channels allocated to the mobile station during the simulation. It has to be 1
channel in case of "Non Hopping" and a list of channel in case of frequency hopping.
MAIO: The Mobile Allocation Index Offset assigned in case of frequency hopping (BBH or SFH) to avoid intra-site
collisions caused by two sites using the same or adjacent channels. This value has to be an integer ranging from 0
and N-1 (where "N" is the number of channels used in the hopping sequence)
AT332_UMR_E0
Codec or Coding scheme (DL): According to the capability of both the base station and the terminal, this value is
either the codec mode (for a circuit-switched service) or the coding scheme (for a packet-switched service) served
at the terminal.
Codec or Coding scheme (UL): According to the capability of both the base station and the terminal, this value is
either the codec mode (for a circuit-switched service) or the coding scheme (for a packet-switched service) served
at the cell.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
7.3.5.2.2
The parameters related to the clutter classes, including the default values.
3. Right-click the group of simulations on which you want to average the results.
4. Select Average Simulation and from the context menu. A properties dialog box appears.
One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialog box contain simulation results for all simulations, both averaged.
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 throughputs that all active users could theoretically generate are provided.
The breakdown per service (total number of users, number of users per activity status) is given.
The Sites (Average) tab: The Sites (Average) tab contains the following average information per site:
DL and UL Throughput for Each Service: The throughput in kbitss for each service. The result is detailed on the
downlink and uplink only when relevant.
The Subcells (Average) tab: The Subcells (Average) tab contains the following average information per transmitter
and TRX Type:
The TRXs (Average) tab: The TRXs tab contains the following information:
Hopping Mode: The hopping mode of the subcell to which the TRX belongs
Channels: The channel list to which the TRX is part of. In case of non hopping, it corresponds to a unique channel.
In case of any hopping mode, it corresponds to a MAL.
339
The Initial Conditions tab: The Initial Conditions tab contains the following information:
The parameters related to the clutter classes, including the default values.
The channel, MAIO, and MAL are allocated at the TRX level: each TRX requires one channel (or MAL) and one MAIO.
The HSN is allocated at the subcell level: each subcell performing frequency hopping requires an HSN (however cells
that do not perform frequency hopping do not need to be allocated an HSN). The allocation of HSNs is managed using
domains and groups.
The BSIC is allocated at the cell level and the BSIC-BCCH pair is used to identify the transmitters in the network. The
allocation of BSICs is managed using domains and groups.
Frequencies are managed on three different levels: frequency bands, and then domains, and finally groups.
The frequency band is the highest level and is defined by the frequencies allocated to GSM/GPRS/EDGE in the area covered
by the project. It can therefore be considered as a fixed item. The frequency bands usually follow the Absolute Radio
Frequency Channel Number (ARFCN) standards. The frequency bands are mainly used for base station and terminal compatibility. A frequency domain is a subset of the frequencies contained by the frequency band. The frequency domain can contain
one or more groups. While the frequency band is fixed, frequency groups and domains can be defined and modified.
The second level on which frequencies are managed, and the highest level on which BSICs and HSNs are managed, is the
domain. The main role of the domain is to limit the resources to the subset of those resources available. For BSICs and HSNs,
the domain is the highest level on which they can be managed. Much like frequency domains, BSIC and HSN domains can
contain one or more groups. However, while the resources defined in a frequency domain are limited by the frequency band
the domain belongs to, the resources in a BSIC or HSN domain are defined by the GSM standard.
The lowest level at which frequencies, BSICs, and HSNs are managed is at the group level. A group belongs to a domain. All
frequencies in a group must belong to the frequency band the domain belongs to. In the case of BSIC or HSN groups, the
entries must be valid BSIC or HSN numbers.
This section begins with an explanation of how to manually allocate resources. By beginning with manual allocation, you will
have a better understanding of how Atoll manages the various resources.
When the project is too large or when there are too many variables to co-ordinate, manually allocating resources will be too
time-consuming and complex. At that point, you will probably need to use Automatic Frequency Planning (AFP). By allocating
resources efficiently within defined parameters, the AFP can enhance network performance. However, before you can
perform an automatic allocation, you must be certain that the pre-requisites have been filled: you must have valid interference matrices, you must determine the number of required TRXs, and you must define separation rules and quality targets.
Along with manual and automatic allocation, Atoll also allows you to allocate resources using Interactive Frequency Planning
(IFP). The IFP enables you to verify the frequency allocation of each transmitter and interactively improve an existing
frequency plan by selecting the most appropriate channels to assign to individual TRXs. The IFP uses the installed AFP module
to calculate the costs associated with the current and modified frequency plans.
By using the AFP to allocate channels and find the best solution in terms of allocated channels, i.e., the frequency allocation
that provides the lowest overall cost, the IFP lets you use your knowledge of the network to improve the frequency plan
proposed by the AFP.
Automatic and interactive allocation are implemented using an AFP module. Many AFP modules work with Atoll. Because
each module is different, in this section only the general allocation process will be described.
340
AT332_UMR_E0
For more information on the optional Atoll AFP module, see "Automatic Frequency Planning" on page 391.
This section covers the following topics:
7.4.1.1.1
Name: Enter a name for the frequency, for example, "GSM 1900." This name will appear in other dialog boxes
when you select a frequency band.
Frequency (MHz): Enter the average frequency.
Channel Width (kHz): Enter the width, in kHz, that each channel will cover.
First channel: Enter the number of the first channel in this frequency band.
Last channel: Enter the number of the last channel in this frequency band.
Excluded channels: Enter the channels that will not be included in this frequency band, even though they are
between the first and last channels.
Multiplexing factor: Enter the multiplexing factor of the frequency band. The user multiplexing factor corresponds
to the number of timeslots in a GSM/GPRS/EDGE frame.
Max channel number: Enter the maximum channel number after which the channel number count restarts at 0.
The GSM 900 frequency band in Atoll includes the P-GSM (primitive GSM), R-GSM (GSM for railways), and E-GSM
(extended GSM) bands, i.e., channels from 1 to 124 (P-GSM), from 955 to 974 (R-GSM), and from 975 to 1023 and
0 (E-GSM). The channel numbers 0 and 1023 will be considered adjacent if you enter a Max Channel Number of
1024 for this frequency band.
341
You can also modify the properties of a frequency band using its Properties dialog box. You
can open the frequency band Properties dialog box by double-clicking the left margin of
the row with the frequency band. The frequency band Properties dialog box has a General
tab which allows you to modify the properties described above, a Frequency Domains tab
which indicates the frequency domains that belong to the frequency band, and, if userdefined fields have been added to the Frequency Bands table, an Other Properties tab.
The absolute radio frequency channel numbers are determined in Atoll with the following equation:
ARFCN of X = First Channel Number + (Channel Frequency of X - First Channel Frequency)/200 kHz
7.4.1.1.2
Name: Enter a name for the frequency domain, for example, "GSM 1900 domain." This name will appear in other
dialog boxes when you select a frequency domain.
Frequency Band: Select the frequency band the domain will belong to from the list.
7. Select the row containing the frequency domain and click the Properties button (
quency domains Properties dialog box appears.
In the frequency domains Properties dialog box, you can modify the properties of the frequency domain and create
frequency groups.
8. Under Groups, in the row marked with the New Row icon (
), enter the following parameters to define a frequency
group (for information on working with data tables, see "Data Tables" on page 75):
Name: Enter a name for the frequency group, for example, "GSM 1900 domain Group1." This name will appear in
other dialog boxes when you select a frequency group.
Min.: Enter the number of the first channel in this frequency group.
Max.: Enter the number of the last channel in this frequency group.
Step: Enter the value interval between channels in this frequency group.
Excluded: Enter the channels that you do not want to use in this frequency group. You can enter or paste a list of
channels; the values must be separated with either a comma, or a semi-colon, or a space. You can also enter a
range of channels to be excluded from this group, by entering the first and last channel of the range separated by
a hyphen. For example, entering 520-525 corresponds to entering 520 521 522 523 524 525.
Extra: Enter the additional channels, outside the first and last channels of the group, that you want to use in this
frequency group. You can enter or paste a list of channels; the values must be separated with either a comma, or
a semi-colon, or a space. You can also enter a range of channels to be excluded from this group, by entering the
first and last channel of the range separated by a hyphen. For example, entering 520-525 corresponds to entering
520 521 522 523 524 525.
342
AT332_UMR_E0
7.4.1.2.1
Decimal format: In decimal format, all numbers from 0 to 9 can be used to define the BSIC. Because both the NCC and
the BCC are in octal format (using the numbers from 0 to 7), their combined value must be converted to decimal
format with the following equation:
NCCx8 + BCC
The resulting value is the BSIC in decimal format. For example, the NCC-BCC pair 3-2 results in a decimal BSIC value of
26.
Octal format: Both the NCC and the BCC are already in octal format (using the numbers from 0 to 7), so they can be
combined directly to express the resulting BSIC. For example, the NCC-BCC pair 3-2 results in an octal BSIC value of 32.
The octal format is more commonly used than the decimal format.
In Atoll, you define the format globally for the entire GSM/GPRS/EDGE document.
When you import drive test data, you must ensure that the defined BSIC format is the
same as that of the drive test data before you import the data.
7.4.1.2.2
Decimal
Octal
7. Select the row containing the BSIC domain and click the Properties button (
domains Properties dialog box appears.
In the BSIC domains Properties dialog box, you can modify the properties of the BSIC domain and create BSIC groups.
343
8. Under Groups, in the row marked with the New Row icon (
), enter the following parameters to define a BSIC group
(for information on working with data tables, see "Data Tables" on page 75):
When defining the BSIC group, ensure that the entered values are consistent with the
defined BSIC format (see "Defining the BSIC Format" on page 343).
Name: Enter a name for the BSIC group. This name will appear in other dialog boxes when you select a BSIC group.
Min.: Enter the first BSIC in this BSIC group.
Max.: Enter the last BSIC in this BSIC group.
Step: Enter the value interval between BSICs in this BSIC group.
Excluded: Enter the BSICs that you do not want to use in this BSIC group. You can enter or paste a list of BSICs; the
values must be separated with either a comma, or a semi-colon, or a space. You can also enter a range of BSICs to
be excluded from this group, by entering the first and last BSIC of the range separated by a hyphen. For example,
entering 0-5 corresponds to entering 0 1 2 3 4 5.
Extra: Enter the additional BSICs, outside the first and last BSICs of the group, that you want to use in this BSIC
group. You can enter or paste a list of BSICs; the values must be separated with either a comma, or a semi-colon,
or a space. You can also enter a range of BSICs to be excluded from this group, by entering the first and last BSIC
of the range separated by a hyphen. For example, entering 0-5 corresponds to entering 0 1 2 3 4 5.
Manual and automatic HSN allocation is based on the HSN domains assigned to TRX types in cell types; when you define a cell
type, you must assign an HSN domain to each TRX type. The assigned HSN domain will be used as a constraint during automatic HSN allocation.
To define frequency domains and groups:
1. Select the Parameters explorer.
2. Click the Expand button ( ) to expand the GSM Network Settings folder.
3. Click the Expand button ( ) to expand the HSNs folder.
4. In the HSNs folder, right-click Domains. The context menu appears.
5. Select Open Table. The HSNs Domains table appears. The HSN Domains table contains a default domain called "ALL
HSNs;" it contains all 64 HSNs.
6. In the row marked with the New Row icon (
7. Select the row containing the HSN domain and click the Properties button (
domains Properties dialog box appears.
In the HSN domains Properties dialog box, you can modify the properties of the HSN domain and create HSN groups.
8. Under Groups, in the row marked with the New Row icon (
), enter the following parameters to define a HSN group
(for information on working with data tables, see "Data Tables" on page 75):
344
Name: Enter a name for the HSN group. This name will appear in other dialog boxes when you select a HSN group.
AT332_UMR_E0
345
346
AT332_UMR_E0
7. Select a Frequency Domain from the list. Only channels belonging to this frequency domain will be allocated to TRXs
of this group during automatic or manual frequency planning.
The frequency domains assigned to the BCCH subcell and to the TCH subcell must reference the same frequency band. If the transmitter has more than one subcell with the TRX
type TCH, only one must reference the same frequency band as the BCCH subcell.
8. If desired, add Excluded Channels. The defined frequency domain can have, as part of its definition, a list of excluded
channels. Addition excluded channels for this subcell can be added in the Excluded Channels column.
9. Click OK.
If you are defining frequency domains for several transmitters, you can group them by
frequency band (for information on grouping transmitters, see "Grouping Data Objects" on
page 94) and then open the Transmitters table for the selected transmitters and assign the
frequency domain to all transmitters at the same time. For information on working with
data tables, see "Data Tables" on page 75.
7.4.2.4.1
347
If you want to import the BSIC at the same time, you can also import the frequency list into
the Transmitters table, which you can open by right-clicking the Transmitters folder and
selecting Open Table from the context menu.
If you are modifying the frequency list of a single transmitter, it is easier to modify the
information directly on the TRXs tab of the transmitters Properties dialog box. For more
information, see "Subcell Properties" on page 282.
7.4.2.4.2
6. Click OK.
If you are adding TRXs to several transmitters, it is easier to use the TRXs table.
To add TRXs using the TRXs table:
1. Select the Network explorer.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Subcells > TRXs Table from the context menu. The TRXs table appears.
4. Scroll down to the row marked with the New Row icon (
).
5. In the Transmitter column, select the transmitter to which the TRXs will be added.
6. Enter the parameters described in "TRX Properties" on page 287.
7.4.2.4.3
7.4.2.4.4
348
AT332_UMR_E0
7.4.2.4.5
Used as BCCH
Used as TCH
8. Select the Adjacent channels check box if you want Atoll to display adjacent channels as well as the selected channel.
9. Click the Search button. The map window displays the coverage areas with the selected channel along with coverage
areas using adjacent channels, if you selected the Adjacent channels check box.
By repeating the search with other channels you can find a frequency with few adjacent channels close by that you
can allocate to the selected transmitter.
In the following example, channel 11 would not be a good choice because it is used by a neighbour. Channels 10 and 12 are
adjacent channels that are also used by neighbours of the selected transmitter.
349
350
AT332_UMR_E0
When you assign frequencies manually, you do not need an interference matrix, traffic, or separation rules; you will be using
your knowledge of the network. On the other hand, when you assign frequencies automatically (or interactively) you need to
supply the additional information to the AFP.
Level 1: The AFP can base its calculations on neighbour relations and work without an interference matrix
Level 2: You can calculate an interference matrix based on uniform traffic spreading
Level 3: You can calculate an interference matrix with clutter weighting
Level 4: You can use OMC or drive-test-based interference matrices
Level 5: You can use any combination of levels 2, 3, and 4.
351
7.4.3.1.1
Server: Select "HCS Servers" in order to correctly consider HCS priorities for service zone selection. Selecting "All"
is not recommended because the results are not significantly better under most circumstances and the calculation
consumes a great deal of resources. or with "best idle mode reselection criterion (C2)", (only for packet switched
IM). For more information, see "Comparing Service Areas in Calculations" on page 484.
Enter an Overlap margin. The default value is "4 dB."
If you select the Shadowing Taken into Account check box, you can change the Cell edge coverage probability
(see "Reliability Recommendations" on page 352). Using shadowing is recommended. For more information, see
"Modelling Shadowing" on page 506.
5. Under Traffic spreading, you can select whether you want to calculate interference on the percentage of interfered
traffic or on the percentage of interfered area:
Based on the maps used in the default traffic capture: If you choose this option, Atoll will calculate interference
on the interfered traffic for each pair of subcells (interfered-interferer).
Uniform (probability expressed in % of interfered area): If you choose this option, Atoll will calculate interference
on the interfered areas for each pair of subcells (interfered-interferer). This method cannot accurately consider
local concentration of traffic, but is faster than calculating interference based on maps.
The unlocked part of the AFP cost will be 0 and, because of this, the AFP will stops.
Frequencies will be reused in too close proximity to each other in the resulting frequency plan.
The distribution of frequency use will not be even and some frequencies will seldom be used.
To correct an unacceptable distribution of frequencies, you will have to create a more reliable interference matrix, thereby
putting more constraints on the AFP.
The best way to create a more reliable interference matrix is to increase the cell edge coverage probability and recalculate
the interference matrices. When the reliability requirement is raised, the part of the standard deviation is reduced from the
signal ("C") when calculating the C/I distribution for each IM entry. This gives a lower C/I for each given "reuse" and therefore
a lower probability of meeting the required C/I target and, consequently, more interference. Raising the interference in the
interference matrix increases the constraints placed on the AFP.
You should also verify that the standard deviation's default value is properly defined and that it is properly defined in all clutter
classes. This step is particularly important for Atoll documents converted from older versions or connected to a database.
352
AT332_UMR_E0
7.4.3.1.2
Mean power control gains are not taken into account when calculating interference matrices. They are only applied when the interference matrices are used in
calculations (IFP, AFP, etc.). The same is the case with the power offset.
When you calculate an interference matrix, you would expect to have full interference for all transmitters over which the AFP will perform a cost calculation. The
interference matrix scope is therefore defined by the AFP scope which is described
in "The Scope of the AFP and the Scope of the Interference Matrix" on page 372.
ii. Right-click the Network Settings folder. The context menu appears.
iii. Select Properties from the context menu.
iv. On the Calculation Parameters tab, set the Min. interferer reception threshold.
This threshold defines the level from which all interferers are ignored. If you increase it to -115 dB or -110 dB,
you will lose very little interference information, but calculations will be much faster.
2. Define a large handover margin, for example, 2 to 4 dB:
353
To save IMs externally, see "Storing Interference Matrices Externally" on page 357.
To save coverage predictions externally, see "External Storage of Coverage Prediction Numerical Results" on
page 208.
354
AT332_UMR_E0
The computation zones do not need to overlap because the AFP scope extends beyond the
computation zone. For more information, see "The Scope of the AFP and the Scope of the
Interference Matrix" on page 372.
7.4.3.1.3
From the Environment Map Editor toolbar, select the environment created in step 2.
For information on creating a traffic capture, see "Calculating and Displaying a Traffic Capture" on page 327.
3. Calculate the interference matrix.
7.4.3.1.4
When calculating the interference matrix, select the option Traffic spreading based on the maps used in the
default traffic capture in the IM calculation dialog box.
355
OMC IMs can be based on reselection mobile measurements or upon HO mobile measurements. In most cases, the HO mobile
measurements are used to create the interference matrix. The main weakness of this approach is that HO mobile measurements are limited to the list of neighbours, and that this list is limited in size.
To overcome this considerable limitation, the OMC can temporarily apply neighbours. However, when this is done, the statistical analysis must take into account the partial time over which each temporary neighbour is tested.
An other limitation which applies to all OMC statistic-based interference matrices is the fact that the BSIC-BCCH pair is the
means used to identify a transmitter. The BSIC-BCCH pairs are sufficient for identifying a server or a potential strong neighbour
for HO candidate, but they are not sufficient to identify an interferer.
The final limitation is the simple fact that the BCCH plan has an effect on the IM when the IM is calculated: if two transmitters
interfere but have the same BCCH, their interference will not be present in the OMC interference matrix.
This limitation can be avoided by adding the BCCH plan to the IM scope. This allows the Atoll AFP to ensure that certain interference entries, (or more precisely no interference entries) have 0 likelihood, and will supplement the information with propagation interference information.
7.4.3.1.5
For more information on the interference matrix file formats, see the Technical Reference Guide.
In this section, the following are explained:
Click Yes to save the imported interference matrix in the GSM/GPRS/EDGE document.
When you save an imported interference matrix in the GSM/GPRS/EDGE document, you can still choose to save
it to an external file linked to the GSM/GPRS/EDGE document. For information, see "Storing Interference Matrices
Externally" on page 357.
356
Click No to store the interference matrix externally, but linked to the GSM/GPRS/EDGE document.
AT332_UMR_E0
7. The interference matrices are imported into the current Atoll document and appear as new items in the GSM Interference Matrices folder.
You can also extract interference matrices from real network data. Using drive test data
paths in which the signal strengths of several transmitters have been measured at each
point, Atoll can generate interference matrix files containing probabilities of CI per transmitter-subcell pair (see "Generating Interference Matrices from a Drive Test Data Path" on
page 483).
Storing Interference Matrices Externally
You can save interference matrices to external files that are linked to the GSM/GPRS/EDGE document. Linking interference
matrices to the GSM/GPRS/EDGE document can reduce file size when the Atoll document is extremely large.
Because the interference matrices are stored externally in ASCI format, reading and writing to file can be time consuming.
When Atoll reads an externally stored IM, it remains in memory. Therefore, to improve AFP performance, it is recommended
to embed interference matrices. You should only save interference matrices externally when the project file is getting large
(for example, when the project file exceeds 2 Gb). To store an interference matrix externally:
1. Select the Network explorer.
2. Click the Expand button ( ) to expand the GSM Interference Matrices folder.
3. Right-click the interference matrix you want to store externally. The context menu appears.
4. Select Properties from the context menu. The Properties dialog box appears.
5. On the General tab, under Interference Matrices Storage, click the Externalise button. A confirmation message
appears.
6. Click Yes to confirm. The Save As dialog box appears.
7. Select the file type from the Save as Type list.
8. Enter the File name and click Save. The interference matrix is stored externally but remains linked to the GSM/GPRS/
EDGE document.
Exporting Interference Matrices
Atoll supports IM0, IM1, IM2, and CLC interference matrix files.
To export interference matrices:
1. Select the Network explorer.
2. Click the Expand button ( ) to expand the GSM Interference Matrices folder.
3. Right-click the interference matrix you want to export. The context menu appears.
4. Select Export from the context menu. The Save As dialog box appears.
5. Select the file type from the Save as Type list.
6. Enter the File name and click Save. The interference matrix is exported.
7.4.3.1.6
357
bour information. Another reason for low reliability is that interference information is collected from handover
regions only, instead of from the service area.
4. Interference matrices based on RXLEV statistics from the OMC (neighbours as well as temporary neighbours)
They can be a very good source of interference information if they are statistically stable because they are not sensitive to data errors. On the other hand, they have many disadvantages, such as:
Transmitters with the same BSIC and BCCH can not be differentiated.
Transmitters having the same BCCH will never have an interference entry.
Information is lost when more than 6 interferers exist at any location.
If many interferers share the same BCCH, they increase each others interference levels.
HCS layers can cause problems because there are more servers at any point, macro layer servers are stronger, or
a correction margin might be introduced for some equipment, etc.
This type of interference matrix can be created using an extended neighbours list.
5. Interference matrices based on drive test data
Reliability can be low because usually the drive test data sampling zone and the traffic model are not related.
Secondly, the measurements are carried out for existing neighbours.
6. Interference matrices based on CW measurements
Their reliability can be low because the measurements usually do not reflect the traffic model. However, this source
of information can be very reliable for a subset of transmitters that were properly scanned. Carrying out CW measurements is expensive which means that the collected information is often partial or out of date.
7. Interference matrices based on scan data drive tests
They are highly reliable and an excellent source of information, but are not useful in a radio planning tool because no
information is available to map transmitters to the received signals at any pixel.
8. Upper bound interference matrix
The source of this type of interference matrix is not defined. It can be based on user experience. The information
contained in this interference matrix is used as an upper limit, i.e., if this interference matrix indicates a certain level
of interference, it should not be exceeded because other interference matrices show higher interference. If an upper
bound interference matrix does not contain information about an entry, it is ignored.
9. Lower bound interference matrix
The source of this type of interference matrix is not defined. It can be based on user experience. The information
contained in this interference matrix is used as a lower limit. This type of interference matrix can be very useful
because you can edit entries in this interference matrix, and be certain that the interference will be at least as high as
the value you entered. This approach can be used when user experience shows a certain level of interference which
the radio network planning tool is unable to calculate.
To define the interference matrix type:
1. Select the Network explorer.
2. Click the Expand button ( ) to expand the GSM Interference Matrices folder.
3. Right-click the interference matrix for which you want to define the type. The context menu appears.
4. Select Properties from the context menu. The Interference Matrix Properties dialog box appears.
5. On the Advanced tab, select the Interference Matrix Type from the list.
Depending on the matrix type, the quality indicators available in the Advanced tab include:
358
AT332_UMR_E0
The standard deviation, depending on the equipment quality and measurement post-processing
The average number of points collected at each matrix calculation point.
The standard deviation, depending on the equipment quality and measurement post-processing
The average number of points collected at each matrix calculation point
The volume of information
Whether the interference information (probabilities) correspond to traffic or surface area.
The standard deviation, depending on the equipment quality and measurement post-processing
The average number of points collected at each matrix calculation point
The volume of information
Whether the interference information (probabilities) correspond to traffic or surface area.
The standard deviation, depending on the equipment quality and measurement post-processing
The average number of points collected at each matrix calculation point
The volume of information
Whether the interference information (probabilities) correspond to traffic or surface area.
The context in which an interference matrix was created is not part of the interference matrix files. You must therefore set up
the type and quality indicators of the interference matrix manually.
7.4.3.1.7
AFP Module Properties: For information on the options, see "Automatic Frequency Planning" on page 391.
AFP Parameters: In the AFP Launching Parameters dialog box, you can set the following parameters:
i.
Under Traffic loads, indicate whether the AFP should take traffic loads From the subcells table or use loads
Based on the default traffic capture results.
ii. If you want the AFP to consider discontinuous transmission mode for TRXs which support it in calculating the
interference, select the DTX check box and enter the Voice activity factor.
iii. Select the Load all the subcells involved in separation constraints check box if you want all subcells potentially involved to be loaded.
iv. Select the Load all the potential interferers check box if you want all potential interferers to be loaded. If this
check box is not selected, the cost function will consist only of the separation violation cost.
Separation Rules: For information on the options, see "Channel Separations" on page 362.
Exceptional Pairs: For information on the options, see "Channel Separations" on page 362.
359
Intra-Technology Neighbours: For information on the options, see "Studying GSM/GPRS/EDGE Network Capacity"
on page 325.
7. Click Calculate. The interference probability values are displayed in the right-most column of the Interference Matrix
Analysis tab.
The tool calculates and displays interference probabilities using the active interference matrices available in the GSM
Interference Matrices folder in the Network explorer. If the interference matrices in the GSM Interference Matrices
folder are inactive or if interference matrices are not available, the analysis tool only calculates and displays the interference from a transmitter and its TRXs on itself.
In the map window, arrows from the studied transmitter to each interfered or interfering transmitter are displayed.
The colour of the arrow is the same as the colour of the studied transmitter. The probabilities of interference are
displayed as captions for the arrows. The thickness of the arrows are indicate the interference probability.
8. Select the interference information to display in the rightmost column:
Under the Status column, you can display the interference matrix information with the studied transmitter as the
Victim or the Interferer.
Under the Frequency Reuse column, you can display Co-channel or Adjacent Channel interference information
for the studied transmitter.
Under the Filtering column, you can display the Strongly Interfered, All Interfered, or the Neighbour Violations
of the studied transmitter. You can choose more than one of these options by pressing and holding Ctrl and
clicking each option.
360
AT332_UMR_E0
7.4.3.1.8
A table with the number of times the listed transmitter has been interfered
The total number of entries in the selected interference matrix
The number of transmitters covered by the interference matrix
The average number of interferers per interfered subcell in the interference matrix.
361
7.4.3.1.9
A table with the number of times the listed transmitter has been interfered
The total number of entries in the selected interference matrices
The number of transmitters covered by the interference matrices
The average number of interferers per interfered subcell in the interference matrices.
362
AT332_UMR_E0
7.4.3.2.1
7.4.3.2.2
), select the following parameters for each separation rule you want
Type of Relation: Select the type of relation, co-transmitter, co-site, or neighbour, between the two TRXs.
TRX Type: Select the first TRX type.
TRX Type 2: Select the second TRX type.
Default Min. Separation: Enter the minimum difference in channels that must exist between the two TRX types.
Entering "0" means that they can use the same channel.
7.4.3.2.3
), select the following parameters for each separation rule you want
Transmitter: Select the transmitter on which the TRX in TRX Type is located.
TRX Type: Select the first TRX type.
Transmitter 2: Select the transmitter on which the TRX in TRX Type 2 is located.
TRX Type 2: Select the second TRX type.
Separation: Enter the minimum difference in channels that must exist between the two TRX types. Entering "0"
means that they can use the same channel.
You can also define exceptional pairs from the AFP results. Subcells which do not respect
separation constraints can be defined as exceptional pairs in order to force the AFP to
modify its allocation priority and to avoid this violation. See "AFP Results" on page 377 for
more information.
7.4.3.2.4
363
4. Select the Transmitter 1 TRX Type and the Transmitter 2 TRX Type to display.
When you select "All" as either Transmitter 1 TRX Type or Transmitter 2 TRX Type, Atoll
does not display all TRX types. Rather it displays only exceptional frequency separations for
which the TRX type constraint is defined as "All."
5. Click the arrow ( ) next to the Edit Relations on the Map button (
appears.
8. Click a transmitter on the map to display the exceptional frequency separations. If the selected transmitter has
defined exceptional frequency separations that fit the display options, Atoll displays the following information (see
Figure 7.29):
The exceptional frequency separations of the selected transmitter are indicated by a heavy line in the same
colour as the other transmitter in the defined pair.
The defined minimum channel separation is indicated beside the line linking the two transmitters.
) again.
You can define exceptional pairs directly on the map. For information, see "Adding or
Removing Exceptional Frequency Separations Using the Mouse" on page 364.
7.4.3.2.5
).
8. Click the reference transmitter on the map. Atoll displays the existing exceptional frequency separations for this transmitter.
364
AT332_UMR_E0
To add an exceptional frequency separation: Press Ctrl and click on the second transmitter. A dialog box appears
where you enter the minimum separation between the transmitters. When you click OK, the exceptional frequency separation is created and indicated by a heavy line in the same colour as the second transmitter. The minimum separation is indicated next to the link. The exceptional separation constraint is automatically added to the
Exceptional Separation Constraints table.
To remove an exceptional frequency separation: Press Ctrl and click on the second transmitter of an existing
exceptional frequency separation. The exceptional frequency separation is removed from the map and from the
Exceptional Separation Constraints table.
9. In order to restore colours and cancel the neighbour display, click the Edit Relations on the Map button (
) again.
You can display the coverage areas of exceptional pairs in much the same way as you
would display the coverage of a transmitters neighbours, with the exception that you
select Exceptional Pairs (AFP) when you click the arrow ( ) next to the Edit Relations on
the Map button (
) in the Radio Planning toolbar. For more information, see "Editing
Neighbours on the Map" on page 229.
7.4.3.2.6
calculated by Atoll
imported, based on OMC statistics, or
imported and completed by a calculation performed in Atoll
This section gives several examples of how you can adjust the relative importance of neighbours.
Review the neighbour allocation before running the AFP. Often poorly defined neighbour
relations are the cause of a poorly defined frequency plan.
If you are running an automatic neighbour allocation so that Atoll can use the calculated neighbour calculation in the AFP, you
should change the values:
After you have run the automatic neighbour allocation and the latter has calculated the neighbour importance, you can
commit the results and run the AFP.
Example 2: Importing Neighbour Importance
There are several possible external sources of neighbour importance. For example:
OMC HO statistics
Test mobile data measurements (providing the measurements ignore interference between non-neighbours).
As with any source of information, it is up to the user to prepare and import this external data. Neighbour importance is measured in terms of probabilities.
365
366
AT332_UMR_E0
Impor tan ce =
1ifY X
Y
---- IfY X
X
This way, when a relationship has an above-average number of handovers, its importance will be the highest possible in Atoll,
i.e., 100%. Otherwise, its importance will be below average.
The AFP will try to assign the required number of TRXs. The number of required TRXs is an important part of the AFP
traffic information.
The cost of interference is proportional to the traffic load.
For frequency hopping, the interference caused by a given interferer usually increases when its traffic load increases.
At its most advanced level, the Atoll AFP can optimise the trade-offs between interfered traffic and blocked traffic
(i.e., when the AFP is permitted to adapt the number of TRXs to the spectrum availability conditions).
There is more than one method of providing traffic information to the AFP. In this section, the methods of providing traffic
information are explained from the simplest to the most advanced.
Method 1: Setting All Traffic Loads to 1
When all traffic loads are set to "1," the amount of traffic is determined exclusively by the number of required TRXs. As a
result, all TRXs are considered equally. This method has to be used whenever the only information you have is the number of
required TRXs.
367
On the Global Parameters tab of the AFP dialog box, select Based on default traffic capture results under Traffic.
By committing the required number of TRXs you have already committed the load and the demand information to the cells
or subcells. You are now ready to use the AFP.
368
AT332_UMR_E0
number of TRXs needed per subcell, see "Dimensioning a GSM/GPRS/EDGE Network" on page 330. For information on adding
TRXs manually, see "Creating or Modifying a TRX" on page 291.
When you dimension the network, Atoll also calculates the required number of shared, circuit, and packet timeslots required
for all TRXs of the subcell.
The other AFP-relevant parameters in the network concern the subcells and related TRXs. In Atoll, a subcell refers to the characteristics of a group of TRXs on a transmitter sharing the same radio characteristics, the same quality (C/I) requirements, and
other settings.
The following subcell settings can be modified globally by modifying the cell type or for a specific transmitter by modifying the
parameters under Subcells on the TRXs tab of the transmitters Properties dialog box. The parameters are displayed in three
different tables under Subcells: Standard Data, for the standard information defining a subcell, Traffic Data, for information
describing the traffic in the cell, and AFP indicators, for information resulting from running an AFP model. For information on
modifying cell types, see "Cell Types" on page 488. For information on modifying transmitter properties, see "Creating or
Modifying a Transmitter" on page 289.
The following are the most important AFP-relevant parameters under Subcells on the TRXs tab of the transmitters Properties
dialog box:
Traffic Load: The Traffic Load indicates the usage rate of TRXs; its value must be from 0 to 1. The value in the Traffic
Load column can be either user-defined or the result of network dimensioning, in which case it will be the same value
for all subcells covering the same area (e.g., BCCH and TCH). The traffic load is used to calculate interference and in
automatic frequency planning.
Total Circuit Demand: The circuit demand indicates the amount of Erlangs necessary to absorb the circuit-switched
demand. This value can be either user-defined or the result of a traffic capture, in which case it will be the same value
for all subcells covering the same area (e.g., BCCH and TCH). This value can be used by an advanced AFP model to optimise the number of TRXs and maximise the amount of correctly served traffic. The Total Circuit Demand is found in
the Traffic Data table.
Total Packet Demand: The packet demand indicates the amount of timeslots necessary to absorb the packet-switched
demand. This value can be either user-defined or the result of a traffic capture, in which case it will be the same value
for all subcells covering the same area (e.g. BCCH and TCH). This value can be used by an advanced AFP model to optimise the number of TRXs and maximise the amount of correctly served traffic. The Total Packet Demand is found in
the Traffic Data table.
C/I Threshold (dB): The minimum signal quality for the TRX Type, under which the subcell interface is taken into consideration. The C/I Threshold is found in the Standard table.
Reception Threshold (dBm): The minimum received signal for the TRX Type. The Reception Threshold is found in the
Standard table.
Frequency Domain: (including excluded channels), from which the AFP tool can choose frequencies. The Frequency
Domain is found in the Standard table. The Relevant Frequency Band used by the model when assigning cell types to
transmitters is also visible on the TRXs tab, but is a parameter of the cell type and can not be changed here.
The other AFP-relevant parameters under Subcells on the TRXs tab of the transmitters Properties dialog box are:
Allocation Strategy: The allocation strategy used during manual or automatic frequency planning. The Allocation
Strategy is found in the Standard table. There are two available allocation strategies:
Free: Any of the channels belonging to the frequency domain can be assigned to TRXs.
Group Constrained: Only channels belonging to the same frequency group in the frequency domain can be
assigned. You can use the Preferred Frequency Group to define the preferred group of frequencies when using
the AFP.
Preferred Frequency Group: When the Group Constrained allocation strategy is selected, in any hopping mode
(including non-hopping), the AFP tries to assign frequencies from the preferred group during automatic allocation. The
preferred frequency group is a soft constraint used by the AFP to assign frequencies to TRXs. When the AFP is unable
to assign a frequency from the preferred group and allocates a frequency from outside the group, a corresponding
cost is taken into account. The preferred group can also be the result of allocation if the AFP model is able to allocate
patterns based on azimuth. The Preferred Frequency Group is found in the Standard table.
Max. MAL Length: The maximum length of the mobile allocation list (MAL), in other words, the maximum number of
channels allocated to the TRXs of the subcell during automatic frequency planning if the Hopping Mode is either SFH
(Synthesised Frequency Hopping) or BBH (Base Band Hopping) and if the Allocation Strategy is Free. The Max. MAL
Length is found in the Standard table.
Hopping Mode: The frequency hopping mode supported by the selected TRX type. The hopping mode can be either
"Base Band Hopping mode (BBH)" or "Synthesised Hopping mode (SFH)." If frequency hopping is not supported, select
"Non Hopping." The Hopping Mode is found in the Standard table.
If SFH is the frequency hopping mode, the settings in the AFP module must match the
settings in the subcell. For information on configuring the optional Atoll AFP module, see
"Automatic Frequency Planning" on page 391.
369
Synchronisation: The Synchronisation is used during frequency hopping; frequency hopping is synchronised among
all TRXs of subcells with the same string of characters in the Synchronisation column. By default, the name of the site
is used as the value in the Synchronisation column, synchronising frequency hopping for all TRXs on the same site.
The Synchronisation is found in the Standard table.
DTX Supported: The DTX Supported check box is selected if the subcell supports DTX (Discontinuous Transmission)
mode. Subcells supporting DTX can reduce interference they produce according to the defined voice activity factor.
DTX does not apply to the BCCH since it is assumed that the BCCH is always on air. The DTX Supported check box is
found in the Standard table.
Lock required TRXs: This option can be used by an AFP model which has the capability to optimise (i.e., increase or
decrease) the number of required TRXs where the only goal is maximising the amount of correctly served traffic. In
other words, you might have fewer TRXs than required if they are not subject to any interference and the amount of
correctly served traffic will be larger. When you select this option, the number of required TRXs is blocked for that
subcell. The Lock required TRXs option is found in the Standard table.
Although you can manually set the values of the following required timeslot numbers, these values are calculated during the
dimensioning process. On the AFP tab of a transmitters Properties dialog box, under Parameters related to automatic planning, you can set the weight and reuse distance to be used for the selected transmitter during the AFP:
Weight: Enter the AFP weight. The AFP weight is used to increase or decrease the importance of a subcell during automatic frequency planning. The value must be a real number. The higher the AFP weight is, the higher the constraint
on the TRX type. The AFP weight artificially multiplies the cost function which has to be minimised by the AFP. The
Weight is found in the Standard table.
Reuse distance: Enter a reuse distance. The reuse distance is taken into consideration when assigning frequencies or
BSIC. Using a minimum reuse distance can help compensate for inaccuracies in the interference matrices or other
input data.
If certain resources have already been allocated, on the AFP tab of a transmitters Properties dialog box you can choose to
lock the resources that have already been allocated to the selected transmitter. During automatic frequency planning, these
resources, which can be allocated as part of the process, will not be changed.
Lock Channels and MAIO: When selected, the transmitters currently assigned channels and MAIO are kept when a
new AFP session is started. On the TRXs tab, under TRXs, you can lock the channels and MAIO for individual TRXs
assigned to the transmitter.
Lock HSN: When selected, the transmitters currently assigned HSN is kept when a new AFP session is started. On the
TRXs tab, under Subcells, you can lock the HSN for individual subcells assigned to the transmitter.
Lock BSIC: When selected, the transmitters currently assigned BSIC is kept when a new AFP session is started.
The Lock BSIC status can also be managed via the Network explorer from the context
menu of an individual transmitter or group of transmitters. For more information, see "AFP
Resource Status Management" on page 288.
On the AFP tab, under Exceptional separation constraints with other transmitters, you can enter exceptional separation
constraints with other transmitters. Exceptional separation constraints you enter here also appear in the Exceptional Separation Constraints table. For information on creating exceptional separation constraints, see "Defining Exceptional Frequency
Separations" on page 363.
By adding two options in the Atoll.ini file, you can force the Atoll AFP model to restrict
channel allocation to a limited spectrum for each transmitter in the same way that it is
implemented on some equipment. For more information, see the Administrator Manual.
370
AT332_UMR_E0
HO margins, more HSC layers mean more overlapping in the network. As the overlapping increases, the constraint level in the
interference matrix and the amount of interference in an interference prediction also increase.
When using this method, you must study the priority mechanism in your network, both in the re-selection process and in the
handover process. Define the corresponding HCS layers once you know its working. When using a traffic map, you must ensure
that there are enough mobility types to model high speed and low speed mobilities.
Method 3: With this method, you study the settings of the TCH TRXs and how they manage radio resources. There might be
differences between the TRXs on at least one of the following items:
A customised definition of multi-subcell transmitters can permit the AFP to exploit these differences. This is often called the
underlay overlay layout, (or intelligent underlay overlay). For detailed information on the technical aspects of cell type definition, see "Cell Types" on page 488.
With this method, there is more than one way to improve the accuracy of the network model. The common point is the fact
that they all require multi-subcell transmitters. Theoretically, these combined methods should provide over 40% additional
spectrum efficiency (40% in the case of voice, for packet-switched services it can be much higher). However, you can assume
that the gains are lower when the HCS layers are intelligently defined. In other words, if you improve the efficient use of spectrum by accurately defining the HCS layers, you can not get an equivalent amount through the accurate definition of concentric cells.
Concentric cells are necessary whenever some TRXs have a bigger interference area than others, or when some TRXs serve
traffic which is more widely spread than others, or when some TRXs are used for more robust services than others, (i.e., for
services which do not need as high a quality as others).
Each of these refinements, alone or combined, can reduce the constraint level, leading to a much better frequency plan.
Method 4: With this method, youll have to check the network as described in this section before starting the AFP:
1. Create a traffic map based on environments, using an appropriate clutter weighting. For information on creating an
environment-based traffic map, see "Creating a User Profile Environment-based Traffic Map" on page 261.
2. Import the current frequency plan into your Atoll document. For information on importing a frequency plan into an
Atoll document, see "Importing a Frequency List" on page 347.
3. Create a traffic capture and calculate it. For information on creating a traffic capture, see "Calculating and Displaying
a Traffic Capture" on page 327.
4. Perform a KPI calculation and commit it. For information on KPI calculation, see "Calculating Key Performance Indicators of a GSM/GPRS/EDGE Network" on page 465.
5. Adjust the traffic coefficient in the traffic capture so that the average level of traffic loads is correct.
6. Study the cases where traffic loads are either too low or too high. This can easily be managed by colouring transmitters
according to their traffic load. The reasons for this can be the following:
A high priority cell is taking all the traffic from another cell. This means that the HCS parameters in Atoll do not
reflect reality.
There exist a cell that is no longer used and, in fact, has been removed from the OMC but still exists in the Atoll.
This cell is absorbing the traffic and reduces to 0 the load of another cell.
Other parameters are not correct: Height, power, tilt, etc.
371
evaluate possible frequency plans and to find the frequency plan with the lowest costs. The cost function can be different from
one AFP to another. The cost function of the Atoll AFP module is described in "Automatic Frequency Planning" on page 391.
The quality of the final resource allocation depends on the level of preparation you make for the AFP. An advanced level
requires an understanding of the cost function, the algorithm, and the parameters specific to that module. Therefore, in this
section, only basic preparation is explained since it is common to all AFP modules that work with Atoll. Advanced use of the
Atoll AFP is explained in "Automatic Frequency Planning" on page 391.
Before using the AFP for automatic resource allocation, you should understand the following:
The scope of the AFP (i.e., in other words, the area and parameters that will be affected by the AFP). For more information, see "The Scope of the AFP and the Scope of the Interference Matrix" on page 372.
The network validation process that takes place before the AFP starts. For more information, see "The Network Validation Process" on page 373.
An understanding of the AFP dialog box. For more information, see "Running an Automatic Frequency Allocation" on
page 374
The AFP results. Understanding the displayed AFP results enables you to assess the proposed frequency plan before
committing the frequency plan. For more information, see "AFP Results" on page 377.
7.4.4.1 The Scope of the AFP and the Scope of the Interference Matrix
In this section, the following are explained:
7.4.4.1.1
Active: The Active group includes all active transmitters that are filtered in the Transmitters folder and in the Sites
folder.
Selected: The Selected group is a subgroup of the Active group and contains all the transmitters in the folder from
which the AFP was started and that are located inside the focus zone and the computation zone.
Ring: Transmitters that are part of the Active group, but not part of the Selected group belong to the Ring group if
they affect transmitters in the Active group. For example, neighbours of transmitters in the Selected group would be
in the Ring group, as would the second transmitter of an exceptional pair. Additionally, if some transmitters are
defined as interferers only (see "Transmitter Properties" on page 280), they are part of the AFP scope because they
might affect the transmitters to which frequencies will be allocated but their frequency plan cannot be modified.
Finally, if BSIC are being assigned, all second-order neighbours are in the Ring group as well. Finally, if interference is
taken into account during the AFP process (by selecting the Load all interferers propagating in the focus zone check
box), any transmitter whose calculation radius intersects the calculation radius of a transmitter in the Selected group,
is included in the Ring group. If a site has a large calculation radius (e.g. 20 km), a potentially large number of transmitters can be loaded into the Ring group.
In this example, the Selected and Ring groups are both loaded into the network and form the AFP scope. However, the transmitters in the Ring group are locked; the AFP-related parameters (BSIC, HSN, MAL, MAIO, and channels) can not be changed.
As for the transmitters in the Selected group, the AFP can assign any of the resources specified in the AFP dialog box, with the
following exceptions:
You can lock individual transmitters for channel (and MAL), HSN or BSIC assignment.
You can lock individual TRXs for channel (and MAL) assignment.
You can lock individual subcells for HSN assignment.
In Atoll's AFP, locked TRXs are reported as locked during cost calculation, however the AFP
can still modify the cost of locked TRXs under the following circumstances: if the locked
TRX has a bad neighbour relation (in terms of cost) with another TRX which is not locked,
Atoll's AFP reports to the user which part of the cost can be modified and which part can
not.
7.4.4.1.2
372
AT332_UMR_E0
matrices in the folder. For more information on the definition of the interference matrix, see "Interference Matrices" on
page 351.
In terms of the AFP, the scope of the interference matrix is the same as that of the AFP, as described in "The Scope of the AFP"
on page 372. In other words, the scope of the interference matrix during an automatic resource allocation includes the transmitters that are active and filtered and within the focus zone and the computation zone, as well the transmitters which will
be taken into consideration by the AFP but will not be affected.
Including the transmitters that are not affected by the AFP (but that affect other transmitters during the allocation of
resources) can be quite demanding on computer resources. By drawing a filtering zone around all of the transmitters to which
resources are to be allocated (the Selected group in the example given in "The Scope of the AFP" on page 372), you can cause
the AFP to ignore transmitters outside of the group of affected transmitters in the interference matrix zone.
Values
0 - 63
10,000
0 - 77
62
0 - 100
2 - 25
12
Comments
373
Range Check
Values
25
-50
-116
-102
Must be <= 7
50
Comments
MAL: The MAL is used by subcells that have either the BBH or the SFH hopping mode. You must also allocate
MAIO, HSN, and channels.
MAIO: The MAIO is used by subcells that have either the BBH or the SFH hopping mode. You must also allocate
MAL, HSN, and channels.
Channels: All subcells must be allocated channels, independently of their hopping mode.
HSN: The HSN is used by subcells that have either the BBH or the SFH hopping mode. You must also allocate
MAL, MAIO, and channels.
BSIC: The BSIC is used by all transmitters, independently of the hopping mode.
Atoll will not create TRXs without channels. Therefore, if you do not allocate MAL and
MAIO, all the SFH subcells are considered locked and no TRXs will be created for them. By
the same token, if you allocate only MAL and MAIO, all NH and BBH subcells will be considered locked and no TRXs will be created.
c. Under Strategies, select the check boxes corresponding to the allocation strategies you want the AFP to use.
Optimisation of the number of TRXs: When subcells have low traffic loads and are located in a zone of heavy
spectral congestion, reducing the number of TRXs to be assigned can present an advantage. On the other
hand, when some subcells have a high traffic demand, the AFP may increase the number of TRXs compared to
what is required to reduce the amount of blocked traffic.
Azimuth-oriented allocation (Pattern 1/X): The azimuth-oriented allocation strategy consists of allocating
preferred frequency groups to group-constrained subcells according to the azimuth of the subcell. If the frequency groups are correctly configured (i.e., if X comparably sized frequency groups for X azimuths), then the
pattern of allocation will be 1/X. If the geometry of the network is incompatible with an azimuth-oriented allocation, the AFP will not attempt to allocate preferred frequency groups.
d. Under Indicators to allocate, select the check boxes corresponding to the indicators you want the Atoll AFP to
allocate.
374
TRX Rank: The AFP can calculate the TRX rank of each TRX. The higher the TRX rank, the higher the cost, in
terms of the risk of interference..
AT332_UMR_E0
Subcell Indicators: AFP cost, congestion, blocking and separation cost can be estimated by the AFP module
per pool of subcells (e.g., a BCCH pool or a TCH pool). These indicators are a way of precisely estimating the
allocation quality at the subcell level and provide some directions to improve the plan, if necessary.
e. Select the Load all interferers propagating in the focus zone check box if you want the AFP scope to be extended
to include all potential interferers. For more information on the AFP scope, see "The Scope of the AFP and the
Scope of the Interference Matrix" on page 372.
4. Click Next. The second page of the AFP dialog box appears with the Separations tab. On this page, you can modify the
network's default separation requirements as well the exceptional pairs. For more information on the separation
requirements, see "Defining Exceptional Frequency Separations" on page 363. For more information on the exceptional pairs, see "Exceptional Pairs" on page 223.
5. Click Next. The third page of the AFP dialog box appears with the Global Parameters tab.
6. Under Allocation of subcells of type, select the check boxes corresponding to the subcells for which resources will be
allocated to TRXs.
Missing TRXs will not be created for any subcell not selected under Allocation of subcells
of type.
7. Under Locking of existing TRXs of type, select the check boxes corresponding to the subcells for which you want the
existing TRXs to be locked during allocation. The existing TRXs will not be affected.
You can lock the resources allocated to individual TRXs in either the Transmitters table, the
Standard Data Subcells table, the TRXs table, or the Properties dialog box of each transmitter.
8. Under Traffic (Subcell load, demand and target rate of traffic overflow), select the source of the traffic information:
From Subcells table: The traffic information in the Subcells table can come from one of three sources:
9. If you want the AFP to consider discontinuous transmission mode for TRXs which support it in calculating the interference, select the DTX check box and enter the Voice activity factor.
10. If you want the AFP to consider reuse distance as a factor in interference, select the Reuse distance check box and, if
desired, change the Default value.
You can enter a reuse distance for each transmitter in the Reuse Distance column of the
Transmitters table.
11. Click OK. The AFP verifies the parameters you have defined. The AFP dialog box that appears (see Figure 7.35) gives a
summary of the verification process as well as the messages displayed in the Events viewer.
375
376
AT332_UMR_E0
General: On the General tab, you will find information on the current status of the AFP, with the elapsed CPU time,
the remaining CPU time corresponding to the speed-to-quality ratio you specified with the Convergence slider, and
the number of solutions evaluated to that point.
CPU time is based on one calculation thread. Since the AFP uses more than one thread in
most multi-core computers, the CPU time is actually about 2.5 times faster than real time.
Quality Indicators: On the Quality Indicators tab, you will find a summary of the current Modifiable cost, Total cost,
and Total traffic, with details for each frequency plan currently retained by the AFP given in the form of a table. You
can select what information is displayed in the table by clicking the Display Options button. The following options are
available for each component of the cost (total, separation, intermodulation, blocking, additional, taxes, spectrum
modification, etc.):
Summed Costs
Modifiable Costs
Locked Costs
Histogram: On the Histogram tab, you can display histograms of the frequency cost and usage distribution for both
the initial plan and best plan. The histogram represents the channels as a function of the frequency of their use.
Moving the pointer over the histogram displays the cost or frequency of use of each channel. The results are highlighted simultaneously in the Zoom on selected values list. You can zoom in on values by clicking and dragging in the
Zoom on selected values list. Atoll will zoom in on the selected values.
You can pause or stop the AFP process at any time by clicking the Pause/Stop button. When you click the Pause/Stop button,
the Details dialog box appears. For information on the Details dialog box, see "AFP Results" on page 377.
You can continue the AFP process, if you want, by clicking the Resume button in the Details dialog box.
377
ters located within the focus zone are listed in the Details dialog box. If the focus zone is not available, the results are displayed
for all the transmitters within the computation zone.
The Details dialog box is composed of four tabs: Summary, Allocation, Subcells, and Histogram.
7.4.4.5.1
Summary Tab
The Summary tab shows the progress of the AFP plan and the improvements obtained by comparing the initial plan (i.e., as it
existed before running the AFP) and the best plan. In addition, you can verify all the cost components for each solution which
has improved the plan in the AFP Progress dialog box (see Figure 7.35).
7.4.4.5.2
Allocation Tab
The Allocation tab contains the allocation results. On this tab, you can edit the frequency plan created by the AFP.
The results are displayed by transmitter, TRX type, and TRX and they are colour-coded. There are two colour families:
Else:
Black: The resource has been not been modified.
Light blue: The resource is locked and has not been modified.
Green: The resource has been modified according to the defined separation constraints.
Brown: The resource has not been modified but there is a separation constraint violation.
Blue: The resource has been created according to the defined separation constraints.
By default, AFP results are displayed in basic view (see Figure 7.37).
A more detailed view can be displayed using Display Options > Display Detailed Constraint Violations (see Figure 7.37).
378
AT332_UMR_E0
Figure 7.38: AFP Results > Allocation tab (displaying important violations only)
Also, if the AFP has removed resources such as TRXs to obtain the lowest blocking cost, the initial resource value is displayed
but the corresponding line is dithered. The resources are actually deleted from the TRXs table.
When hovering the mouse pointer over a resource in the table, the corresponding tip text displays the reason for the status
indicated by the colour.
Under Display, for each combination of transmitter (Transmitter column), subcell (TRX Type column), and TRX (Index
column), Atoll will display one of the following columns according to the selected resources:
BSIC
HSN
Channels
The TRX Rank column indicates the quality of the TRX in that subcell. The higher the TRX rank, the higher the cost, in terms of
risk of interference. In other words, when you are trying to improve the solution proposed by the AFP, you must concentrate
on the TRXs with the highest TRX ranks. You can hide the TRX Rank column by clicking the Display Options button and deselecting Display AFP Indicators.
Separation constraint violations, if any, are listed in the Separations violations column.
379
To display the details of a separation constraint violation (in basic view only):
1. Click the violation in the Separations violations column. A message box appears with details on the violation.
Yes: to define the pair currently in violation as an exceptional pair. Because separation constraints between exceptional pairs have more weight than default separation constraints, you will be able to re-run the AFP and force it
to try to avoid this violation
No: to close the message box without defining the pair currently in violation as an exceptional pair.
The bottom of the Allocation tab displays the messages related to the last solution (which may not be the best solution) as
well as potentially related allocation problems.
380
AT332_UMR_E0
Display the Plan to be Committed: When this option is selected, Atoll displays the frequency plan as it now stands,
that is the post-AFP frequency plan with the modifications you made after running the AFP. You can only modify the
entries in the Channel Assignment column in the current plan.
Display the Final AFP Plan: When this option is selected, Atoll displays the post-AFP frequency plan as it stood before
you began making modifications.
Display the Initial Plan: When this option is selected, Atoll displays the frequency plan before the AFP session.
You can also cancel all the modifications you have made to the current AFP plan using Actions > Reset Channel Allocation.
Resolving Separation Constraint Violations Automatically
When you resolve separation constraint violations automatically, Atoll deletes the TRXs that respond to set criteria and that
are involved in the violations.
To resolve separation constraint violations automatically:
1. Click the Actions button. The context menu appears.
2. Select Resolve Constraint Violations. The Constraint Violations Resolution dialog box appears.
381
All the TRXs: Atoll will delete all TRXs that do not respect the separation constraints.
Only the TRXs modified by the AFP: Atoll will delete only TRXs that were modified by the AFP that do not respect
the separation constraints.
4. Under Violation types to consider, select the check boxes corresponding to the separation constraint violations that
you want Atoll to take into consideration:
5. Under Collision Probabilities, select the collision probability you want Atoll to take into consideration:
All: Select this option if you want Atoll to consider all co-channel and adjacent channel collision probabilities.
If the co-channel collision probability is >=: Select this option and enter a value if you want Atoll to consider cochannel collision probabilities greater than or equal to the defined value.
If the co- or adjacent channel collision probability is >=: Select this option and enter a value if you want Atoll to
consider co-channel and adjacent collision probabilities greater than or equal to the defined value.
6. Under TRX types, select the check boxes of the TRX types you want Atoll to take into consideration:
Apply to control channel TRXs: If you select this option, control channel TRXs (i.e., BCCH TRXs) will be deleted.
Apply to other TRXs: If you select this option, TRXs on non-control channel TRX types (i.e., TCH, TCH_EGPRS or
TCH_INNER) will be deleted.
7. Click OK. Atoll deletes the TRXs that are involved in the separation constraint violations and that respond to the
defined criteria.
Defining the Display of the Allocation Tab
You can sort the contents of the table on the Allocation tab by using the context menu or by selecting an option displayed by
clicking the Display Options button.
By default, the contents of the table under Display are sorted by the content of the Transmitters column. If desired, you can
sort the content of the table by any other column, such as, for example, the BSIC column.
To sort the contents of the table:
1. Right-click the name of the column by which you want to sort the contents of the table. The context menu appears.
2. Select Sort Ascending or Sort Descending from the context menu.
Atoll enables you to filter the contents of the table to display only a selection of data.
382
AT332_UMR_E0
Filter by Selection: When you select this option, all records with the selected value or values are displayed.
Filter Excluding Selection: When you this option, all records without the selected value or values are displayed.
Advanced Filter: When you select this option, the Filter dialog box appears. Using the Filter dialog box, you can
use advanced data filtering to combine several criteria in different fields to create complex filters. For more information on advanced data filtering, see "Advanced Data Filtering" on page 101.
If you have filtered information, you can remove the filter and display all the data again by right-clicking a cell in the table
under Display and selecting Remove Filter from the context menu.
You can also define how the contents on the Allocation tab are displayed by clicking the Display Options button and selecting
one of the options that appear:
You can select the columns that will appear on the Allocation tab:
You can Display AFP Indicators if you calculated them during the AFP session.
You can select one of the following plans to appear in the table:
Display the Plan to Be Committed: The plan to be committed represents the results obtained from the AFP and
your possible modifications (deletion of allocated resources, rollback to initial values, etc.). Only this plan can be
committed to the network.
Display the Final AFP Plan: The AFP plan shows the gross results of the AFP session, in other words, the final
results of the best plan. When this plan is displayed, the Commit button is not available. To make it available,
select the option Display the Plan to Be Committed.
Display the Initial Plan: The initial plan shows the network frequency plan before the AFP session. This plan is the
one before you commit any AFP results, in other words, the current plan.
You can Display Detailed Constraint Violations. In this mode, the hyperlinks under Separation Violations are removed
(and the corresponding violations are listed in full) and three additional columns appear on the right:
With the TRX: contains hyperlinks, each indicating which TRX of which transmitter is causing the violation. If you
click a hyperlink, you will jump directly to the cell containing the index of the TRX causing the violation.
P(co-channel): probability of the violation being due a co-channel.
P(adjacent): probability of the violation being due to an adjacent channel.
383
You can Display Important Violations Only. This option can prove very useful when too many low importance violations are displayed on the Allocation tab. In this mode, you can choose to delete the faulty TRXs individually (see
"Resolving Separation Constraint Violations Manually" on page 380) or all at once (see "Resolving Important Separation Constraint Violations" on page 380).
By adding options in the Atoll.ini file, you can specify the thresholds above which important violations will be highlighted.
You can select one of the following plans to appear in the table:
Co-transmitter Violations: Select this option to show/hide co-transmitter separation constraint violations.
Co-site Violations: Select this option to show/hide co-site separation constraint violations.
Neighbour Violations: Select this option to show/hide neighbour separation constraint violations.
Exceptional Pair Violations: Select this option to show/hide exceptional pair separation constraint violations.
Figure 7.44: AFP Results > Allocation tab > Detailed AFP Report
384
Site, Transmitter, TRX Type, Index, Channels (or MAL), MAIO, HSN
Type of Violation
AT332_UMR_E0
AFP Separation Cost, Penalty p (between 0 and 1), Violating Transmitter, Violating TRX Type, Violating TRX Index,
Violating Channels (or MAL), Violating MAIO
Separation constraint violations are considered for TRXs if, and only if, the TRXs are not corrupted.
In case of corrupted TRXs, the AFP will fix them or delete them.
However, corrupted TRXs can still be present in the output plan (if frozen for example). For each of these corrupted
TRXs, a specific line is issued to indicate the state of corruption and the reason.
In Atoll, the various separation constraints are compiled into a TRX-level non-symmetric relation. Each ordered TRX pair points
to one single "requirement" composed of the separation magnitude and the highest priority separation type. Since two
transmitters can simultaneously be co-site, be co-transmitter, be neighbours, and form an exceptional pair, the following
hierarchical order is considered:
When AFP is set to Automatic Assignment (for large networks), the detailed violation reports are exported automatically.
Figure 7.45: Automatic assignment of the best obtained plan to the document
The full content of the detailed report is split into 5 files that will be saved in the ATL document directory.
File Name
(generated at 11:35 on 03/09/2015)
File Content
FP_AutoCommit__11h35_21_10_2015__exPairViolations.txt
FP_AutoCommit__11h35_ 21_10_2015__coCellViolations.txt
FP_AutoCommit__11h35_ 21_10_2015__coSiteViolations.txt
FP_AutoCommit__11h35_ 21_10_2015__neighborViolation.txt
FP_AutoCommit__11h35_ 21_10_2015__corruptedTrxs.txt
385
7.4.4.5.3
Subcells Tab
The Subcells tab (see Figure 7.46) shows the subcell indicators, the variation of the number of required TRXs (and corresponding traffic loads), and the allocated preferred frequency groups estimated by the AFP model, if you selected these options
when starting the AFP. For each parameter, the table gives the initial and final results. When committing them, they are
assigned to the corresponding subcells.
If the AFP has been run with the azimuth-oriented allocation strategy, the Subcells tab will also display the preferred groups.
If the geometry of the network was incompatible with an azimuth-oriented allocation, the AFP will not attempt to allocate
frequency groups.
7.4.4.5.4
Histogram Tab
On the Histogram tab (see Figure 7.47), you can display histograms of the frequency cost and usage distribution for both the
initial plan and best plan. The histogram represents the channels as a function of the frequency of their use. Moving the
pointer over the histogram displays the cost or frequency of use of each channel. The results are highlighted simultaneously
in the Zoom on selected values list. You can zoom in on values by clicking and dragging in the Zoom on selected values list.
Atoll will zoom in on the selected values.
386
AT332_UMR_E0
7.4.4.6.1
Display the Plan to be Committed: When you select this option, Atoll displays the frequency plan as it now stands,
in other words, Atoll displays the AFP plan with your modifications. You can only modify the entries in the Channel
Assignment column in the current plan.
Display the Final AFP Plan: When you select this option, Atoll displays the AFP plan as it stood before you began
making modifications.
Display the Initial Plan: When you select this option, Atoll displays the frequency plan before the AFP session.
3. Click Commit.
7.4.4.6.2
Display the Plan to be Committed: When you select this option, Atoll displays the frequency plan as it now stands,
in other words, Atoll displays the AFP plan with your modifications. You can only modify the entries in the Channel
Assignment column in the current plan.
Display the Final AFP Plan: When you select this option, Atoll displays the AFP plan as it stood before you began
making modifications.
Display the Initial Plan: When you select this option, Atoll displays the frequency plan as it was after the AFP
stopped, in other words, Atoll displays the AFP plan without your modifications.
3. Click the Actions button and select Export Results. The Export dialog box appears.
4. Export the frequency plan as explained in "Exporting Tables to Text Files and Spreadsheets" on page 86.
If you are not satisfied with the current frequency plan, you can click the Resume button
to restart the AFP process from the last proposed solution in order to try to improve it.
387
Figure 7.48: Selected TRX in Non Hopping mode (cost components and indicators for channel 565)
In Figure 7.49, candidate channel 545 is better than channel 565 even if interfered by TRXs of BRU002_G4 and BRU038_G5.
The Replace button becomes active for replacement.
Figure 7.49: Selected TRX in Non Hopping mode (candidate channel 545 for replacement of channel 565)
To allocate frequencies interactively using the IFP:
1. Select Tools > Interactive Frequency Planning (IFP). The Interactive Frequency Planning (IFP) window appears.
2. Select the Channel Allocation and Analysis view at the top of the Interactive Frequency Planning (IFP) window.
3. Select a transmitter from the Transmitter list or by clicking its symbol in the map window.
4. Select the TRX type from the Subcell list.
5. Select an AFP module from the AFP list.
6. If you want, click the Parameters button to modify the parameters that will influence frequency planning:
388
AFP Module Properties: For information on the options, see "Automatic Frequency Planning" on page 391.
AFP Parameters: the AFP Launching Parameters dialog box appears:
Under Traffic Loads, indicate whether the AFP should take traffic loads From the subcells table or use loads
Based on the default traffic capture results.
If you want the AFP to consider discontinuous transmission mode for TRXs which support it in calculating the
interference, select the DTX check box and enter the Voice Activity Factor.
Select Display best candidates only if you want to limit the number of solutions to be calculated and displayed.
Selecting this option might reduce calculation time for large networks.
Select Load all the subcells involved in separation constraints if you want all the subcells that are potentially
involved in separation constraints to be loaded.
Select Load all interferers propagating in the focus zone> if you want all potential interferers propagating in
the focus zone to be loaded. If not selected, the cost function will consist only of the separation violation cost.
Separation Rules: see "Defining Separation Rules" on page 363.
Exceptional Pairs: see "Defining Exceptional Frequency Separations" on page 363.
Intra-technology Neighbours: see "Adjusting the Relative Importance of Neighbours" on page 365.
AT332_UMR_E0
7. Click Calculate. The IFP calculates and displays the cost of the current channel allocation for the selected transmitter.
The tool calculates and displays interference probabilities using the active interference matrices available in the GSM
Interference Matrices folder in the Network explorer. If the interference matrices in the GSM Interference Matrices
folder are not active or if interference matrices are not available, the analysis tool only calculates and displays the
interference from a transmitter and its TRXs on itself.
In the map window, arrows are displayed from the selected transmitter to each interfered or interfering transmitter.
The colour of the arrow is the same as the colour of the studied transmitter. The probabilities of interference are
displayed as captions on the arrows. The thickness of the lines indicates the interference probability.
Different information and options are available depending on the hopping mode of the selected transmitters TRXs:
Non Hopping mode
1st column: The header indicates the number of "existing TRXs" and "TRXs required" for the transmitter under
study, according to the TRX type currently selected beside Subcell. The "existing TRXs" are listed with the channel
and MAL assigned to each, and the allocation cost. "New TRX" appears at the beginning of the list after calculation
for TCH.
2nd column: The header indicates the number of "candidate(s)" and "channels in domain". The candidate channels are listed with the corresponding costs if allocated to the selected transmitter.
3rd column: In this column, you can select the information that should appear in the 4th column and on the map.
All the information below is selected by default. To filter it, press the Ctrl key and select the information you want:
penalties due to Major separation violations, Separation violations, Interference and Neighbour relations
KPIs and other components
4th column: The last column displays information on the way the allocation cost has been evaluated (traffic load,
cost components). In addition, it displays the interference probabilities between the selected TRX and interfering
TRXs according to the options selected in the Filtering column.
Filter
Displayed Information
When only this filter is selected, only the penalties due to important
separation violations appear in the 4th column and on the map.
Separation violations
When only this filter is selected, all the penalties due separation violations
appear in the 4th column and on the map.
When only this filter is selected, only the penalties due to interference appear
in the 4th column and on the map.
Interference (IM and distance)
When Separation violations is also selected, the penalty displayed on the map
is the sum of the penalties due to interference and separation violations.
Neighbour relations
When only this filter is selected, only the penalties due to the neighbours
currently in the Neighbours table appear in the 4th column and on the map.
1st column: The header indicates the number of "existing TRXs" and "TRXs required" for the transmitter under
study, according to the TRX type currently selected beside Subcell. The "existing TRXs" are listed with the channel
and MAL assigned to each, and the allocation cost. When an "existing TRX" is selected, the IFP will try to replace
the frequency defined in this TRX; the replaced frequency is one of the frequencies in the MAL. "New TRX" appears
at the beginning of the list after calculation for TCH.
2nd column: The header indicates the number of "candidate(s)" and the number of "channels in domain". The
candidate channels are listed with the corresponding MAL and cost when a channel is allocated to the TRX
selected in the 1st column.
3rd column: In this column, you can select the information that should appear in the 4th column and on the map.
All the information below is selected by default. To filter it, press the Ctrl key and select the information you want:
penalties due to Major separation violations, Separation violations, Interference and Neighbour relations
KPIs and other components
4th column: The last column displays information on the way the allocation cost has been evaluated (traffic load,
cost components). In addition, it displays the interference probabilities between the selected TRX and interfering
TRXs according to the options selected in the Filtering column. For more details, see table in No Hopping mode.
1st column: The header indicates that there is "No alternative proposed since the subcell is in SFH". Existing TRXs
appear with the channel and MAIO assigned to each, as well as the corresponding allocation cost.
389
Figure 7.50: Selected TRX in SFH mode (cost components and indicators for channel 565)
2nd column: The MAIO and allocation cost appear for the TRX selected in the first column.
Unlike in "Non Hopping" and "Base Band Hopping" modes, there are no candidate channels in "Synthesised Hopping" mode since a channel should be assigned to several TRXs; in
addition, a candidate MAIO should also be proposed. The only usage of IFP in "Synthesised
Frequency Hopping" mode is to analyse the cost.
3rd column: In this column, you can select the information that should appear in the 4th column and on the map.
All the information below is selected by default. To filter it, press the Ctrl key and select the information you want:
penalties due to Major separation violations, Separation violations, Interference and Neighbour relations
KPIs and other components
4th column: The last column displays information on the way the allocation cost has been evaluated (traffic load,
cost components). In addition, it displays the interference probabilities between the selected TRX and interfering
TRXs according to the options selected in the Filtering column. For more details, see table in No Hopping mode.
You can double-click any item in any column to display additional information on this item. For example, the following dialog
box appears when you double-click a candidate channel in the 2nd column:
390
AT332_UMR_E0
7.4.4.7.1
7.4.4.7.2
7.4.4.7.3
391
Figure 7.52: The Cost tab of the AFP Module Properties dialog box
7. Select the Modified TRX check box to restrict the number of modifications to the existing plan.
8. Select the Intermodulation Tax check box in order to try avoiding these products.
9. Click OK to save your changes to the AFP module and close the AFP Module Properties dialog box.
All the other AFP settings should be left with their default values.
To run a simple AFP process:
1. Select the Network explorer.
2. Right-click the Transmitters folder. The context menu appears.
392
AT332_UMR_E0
3. Select Frequency Plan > Automatic Allocation from the context menu. The AFP dialog box appears with the AFP
Model and Allocations tab displayed.
4. On the AFP Model and Allocations tab, click Next without modifying any of the options. The Separations tab appears.
5. On the Separations tab, click Next without modifying any of the separation rules and without defining any exceptional
pairs. The Global Parameters tab appears.
6. On the Global Parameters tab, select From subcells table under Traffic (load and demand). In the third page of the
AFP wizard, extract the traffic data from the subcells table.
7. Clear all the check boxes under Locking of existing TRXs of type and clear the DTX check box.
8. Click OK. The final AFP dialog box appears.
9. Set the Convergence to a relatively short period, i.e. move the corresponding slider closer to Speed than Quality.
For more information on running an automatic frequency allocation, see "Automatic Resource Allocation Using an AFP
Module" on page 371.
7.5.2.1.1
"The Cost Function as a Combination of Separation Violation and Interference Probabilities" on page 393
"Counting Bad TRXs (Nodes) Instead of Bad Relations (Edges)" on page 394
"The Cost of Each TRX" on page 394
"Cost of Each Subcell" on page 394
"An Example of Separation Violation Cost with Frequency Hopping" on page 395
"Interference Cost" on page 396
"Probabilistic Cost Combination" on page 396
"The Cost of Missing and Corrupted TRXs" on page 397
"Cost of Out-of-domain Frequency Assignment" on page 397
"Preferred Group Cost" on page 397
"Intermodulation Cost" on page 397
"Quality Target" on page 399
"Quality Target" on page 399
"AFP Shadowing" on page 399.
393
7.5.2.1.2
The cost component of assigned frequencies that are not in the assigned domain
The cost component of blocked traffic (calculated only when you set the AFP to optimise the number of required TRXs)
The cost component of intermodulation.
Case 2
This example shows the particularity of the node-oriented cost approach. AtollAFP is node oriented by default. You can set
Atoll's AFP to be edge oriented; these parameters are explained in "XREF" on page start here XREF. The three main advantages
of the node-oriented approach are:
The cost function has units which are easy to understand: interfered traffic.
It has a greater capacity to optimise the number of TRXs.
It has the ability to respect a TRX-based quality target, i.e., to disregard interference at a TRX below a certain value
(for more information, see start here XREF).
The node-oriented approach provides a better correspondence between the AFP cost and the network quality.
7.5.2.1.3
If TRX is corrupted, the cost of being corrupted is added to the total cost, and multiplied by T( ), where T( ) is an
estimate of the traffic time slots for TRX weighted by the AFP weight for this TRX.
If TRX is missing (i.e., if the required number of TRXs and the actual number of TRXs is different), the cost of the
missing TRX is added to the total cost, and multiplied by T( ).
If TRX has frequencies assigned to it that do not belong to its domain, the cost is added to the total cost, and multiplied by T( ).
Otherwise, the separation cost, the interference cost, the changing load, and the preferred group respect ratio of this
TRX are added together (probabilistically) and added to the total cost, and multiplied by T( ).
If this amount is very small, it is discarded (for more information, see "Quality Target" on page 399).
You can control the AFP cost target by determining the value of the cost function parameters. Some of these parameters are
part of the data model, e.g., "Maximum MAL Length" and "Minimum C/I", while others belong to the AFP. For more information on each of these parameters, see XREF.
7.5.2.1.4
394
AT332_UMR_E0
7.5.2.1.5
Figure 7.53: The Separation tab of the AFP Module Properties dialog box
In this example, there is a network with two TRXs on the same cell. The first, TRXi, has a MAL referred to as MALi. It is interfered
by TRXk with MALk. TRXi and TRXk have a separation requirement of 2. Their MAL lengths are 5 and 4, respectively. Unfortunately, one of their frequencies is the same (i.e., the separation is 0), while all other frequencies are correct. For a co-channel
violation when the required separation is 2, the cost of the separation violation is 90%, as indicated in Figure 7.53 on page 395.
Because only one channel of each TRX causes interference, and the length of MALi is 5 and the length of MALi is 4, the collision
probability is 1/20. Therefore, the cost to consider is divided by 20: 90/20 or 4.5% for each TRX.
Because this example uses frequency hopping, there is an additional hopping gain which provides a slight cost reduction. The
exact gain is obtained from the Frequency diversity gain table on the Advanced tab of the Atoll AFP Module Properties dialog
box. The gain values are given in dB, and because the two TRXs have different MAL lengths, they have different diversity gains:
a gain of 1.4 for a MAL length of 5 and a gain of 1.2 for a MAL length of 4 (assuming the default values were not changed).
The diversity gain of 1.4 dB is applied to the separation cost using the following equation:
10
1,4
--------
10
1,38
In order to calculate the exact contribution to the separation cost component, these values are multiplied by the traffic load
(Erlangs/timeslot) and by the number of traffic carrier timeslots for each TRX. Assuming the traffic load is 1 and that each TRX
has 8 traffic carrier timeslots, the result is (8 x 3.25 + 8 x 3.41), or about 0.5 Erlangs for the two TRXs combined.
395
In this example, the AFP weight was assumed to be 1, the traffic loads were assumed to be
1, no DTX was used, no other interference or separation violation was combined with the
given cost, the global separation cost was set to 1, and the co-transmitter separation
weight was set to 1 as well.
7.5.2.1.6
Interference Cost
Traffic on a TRX is interfered if and only if interfering transmitters use the same channel or an adjacent channel. Each case of
reuse reduces the amount of good traffic and increases the interference cost. The reuse is weighted by the global interference
weighting factor, and takes into account the burst collision probability in the same way as in the example in start here XREF.
This example explains how a single interference cost component is calculated. In this example, the network contains only two
TRXs belonging to [TX1, BCCH] and [TX2, BCCH]. The interference matrix entry between these two subcells is given in the form
of a CDF, a cumulative density function, displayed in Figure 7.54.
Figure 7.54: The interference matrix entry between [TX1, BCCH] and [TX2, BCCH]
You can see that the probability of C/I (BCCH of TX2 affecting the BCCH of TX1) being greater than 0 is 100%. The probability
of having a C/I at least equal to 31 dB is 31.1%. In the Subcells table, the Min C/I field of the TX1's BCCH subcell of is 12. Therefore, for a C/I level of 12 dB, the probability of interference is 6.5% (because this requirement has a probability of 93.5% of
being fulfilled).
In order to be converted into cost, the probability of interference 6.5% must be multiplied by the number of time slots, their
loads, and the AFP weight.
For more information, see the cost function formula in start here (todo put ref XXXXX)
7.5.2.1.7
P1, P2, .Pn are the costs of the probability of a violation of a TRX (one for each of "n" violations).
Pn+1, Pn+2, .Pm are the costs of the probability of interference of a TRX (one for each of "m-n" interferences).
Pm+1 is the changing TRX cost described below:
396
i=1
AT332_UMR_E0
m+1
1 P i 1
1 P i
i=1
i=1
The interference cost uses the "min C/I" value, defined at the subcell level, for which it might have precise interference information. It can apply various gains to this C/I quality target due to frequency hopping and/or DTX.
7.5.2.1.8
By default, 100% of the traffic that a corrupted TRX is supposed to carry is considered impaired.
In some cases, correcting the assignment of resources for a group of corrupted TRXs will not only result in these TRXs being
considered corrupted but many other TRXs that, otherwise, would have correctly assigned resources, will also be considered
corrupted.
When you enable the optimisation of the number of TRXs, the costs for missing TRXs and
corrupted TRXs change to a fixed value. For missing TRXs, this value multiplies the absolute
difference between the number of assigned TRXs and the number of required TRXs.
If you do not enable the optimisation of the number of TRXs, the weights for missing and
corrupted TRXs are multiplied by the traffic (time slots, load, and AFP weight).
7.5.2.1.9
7.5.2.1.10
When a preferred frequency group is assigned in the subcell table, all frequencies not belonging to this group are considered as interfered if assigned to TRXs of this subcell.
If an azimuth-oriented pattern is required by the AFP, then the AFP itself will choose the preferred frequency groups.
The AFP will correlate its choice with the azimuth direction.
The group constraint weight is meant to be kept very low. Otherwise it becomes equivalent to a domain constraint.
The group constraint weight in converted into a cost as follows: each use of an out-of-group frequency is equivalent to a small
amount of interference. This interference is then combined with the other sources of interference and multiplied by the traffic
(time slots, load, and AFP weight).
7.5.2.1.11
Intermodulation Cost
The purpose of this cost component is to avoid cases where intermodulation can cause problems. It is therefore defined
slightly more strictly than in real cases where intermodulation effects occur.
The intermodulation violations are summarised as a tax, since they always have relatively low interference probabilities.
This tax is applied when the combination of allocated frequencies generates a frequency already allocated within the same
site. The weight of the tax depends on the type of combination (order, harmonics, or various amplification spreading violation), on whether the combination of DL frequencies affects UL frequencies, or whether the intermodulation takes place
within a same site, transmitter or equipment.
Each physical frequency used in a site can be subject to an Nth order (2, 3, or 5) or or a VASP (Various Amplification Spreading
Violation) intermodulation separation violation.
397
If there are 2 frequencies, X and Y where X < Y, the following table describes the separation constraint:
Constraint Order
Condition
Constraint Applied To
Y=2X
X and Y
VASP
X and Y
If there are 3 frequencies, f, f1, and f2, the following table describes the separation constraint:
Constraint Order
Condition
Constraint Applied To
Second order
f=f1+f2
f, f1 and f2
Third order
f=2f1-f2
f=2f2-f1
f, f1 and f2
Fifth order
f=3f1-2f2
f=3f2-f1
f, f1 and f2
The preceding tables summarise five types of violations. Each type has a default weight:
Constraint Type
Weight
Second Order
0.01
Harmonics
0.005
3rd order
0.004
5th order
0.0028
VASP
0.0002
The costs detailed up to this point are added together and weighted with the inter-modulation weight W, the UL/DL component weight, and the equipment sharing weight.
In each intermodulation violation there is an interfering frequency (or frequencies) and an interfered frequency. In all the
preceding equations except the VASP, the generator frequency is on the right side of the equations while the interfered
frequency is on the left site. The VASP case corresponds to two violations: in the first, the lower frequency is the generator,
and the higher frequency is the interfered.
It is assumed that the generator frequencies are either all on the uplink or all on the downlink, otherwise, no violation is
considered. The interfered frequency can be a downlink or uplink frequency as well. Therefore, there are 4 cases for which 4
weights will multiply the violation cost.
Generator
Frequencies
Interfered
Frequencies
Weight
Description
DL
UL
UL
UL
DL
DL
UL
DL
The final weight concerns the equipment sharing. This aspect has a crucial effect on the importance of intermodulation. In
Atoll, it is assumed that sharing a site implies sharing a transmitter and that sharing a feeder and antenna implies co-cell
cohabitation.
For co-cell intermodulation (generator frequencies as well as IM belong to the same cell), the intermodulation cost is multiplied by 5.
To display the Intermodulation Cost column on the Summary tab of the AFP Details window (see Figure 7.55), you must select
Component Details from the Display Options drop-down menu:
398
AT332_UMR_E0
Figure 7.55: Displaying the Intermodulation Cost column the Summary tab of the AFP Details window
7.5.2.1.12
Quality Target
It is often necessary to deal with small and large amounts of interference differently. For example, an operator might prefer
to have 10 transmitters with 2% interfered traffic on each, rather than to have 2 transmitters with 10% interfered traffic on
each.
On the Cost tab of the Atoll AFP Properties dialog box, you can choose to ignore the interference and separation costs that
do not add up to the value of the Accepted Interference Percentage set in the Subcells table for each subcell by clearing the
Summed cost of all TRXs check box. TRXs that have a lower percentage of interference than the Accepted Interference
Percentage are considered to have no interference and are excluded from the total cost. In other words, the AFP dismisses
any TRX whose quality is better than the quality target, enabling it to concentrate the optimisation on the TRXs that really
need improvement.
7.5.2.1.13
The tax on reuse distance is defined on the Protection tab of the Atoll AFP Properties dialog box. The tax applied on reuse
distance is associated with any additional protection against adjacent channel reuse. The greater the additional protection
against adjacent channel reuse defined on the Protection tab, the greater the distance tax.
The number of relations based on distance taken into consideration for each transmitter is limited for performance reasons.
You can define the maximum number of relations by setting the "GlobalDistanceMatrixDegreeUB" option in the Atoll.ini file.
For information on setting options in the Atoll.ini file, see the Administrator Manual.
7.5.2.1.14
AFP Shadowing
Shadowing is important for the AFP. Within the context of the AFP, shadowing is implemented by setting the definition of
interference as Flexible on the Protection tab of the Atoll AFP Properties dialog box. Shadowing is so important that in some
cases it is enabled automatically, for example, if the interference matrices themselves were not calculated with shadowing.
AFP shadowing is applied in relation to the quality threshold. When enabled, traffic having C/I conditions slightly worse than
the required threshold is not considered 100% interfered. At the same time, traffic having C/I conditions that are only slightly
better than the threshold is not considered as 100% good.
This shadowing is performed by repeatedly accessing the CDF function as explained in "Interference Cost" on page 396.
399
4. Right-click the Atoll AFP Module folder. The context menu appears.
5. Select Properties from the context menu. The Atoll AFP Module Properties dialog box appears.
The Atoll AFP Module Properties dialog box consists of 10 tabs: General, Cost, Separation Weights, Interference Matrices,
HSN, MAL, Execution, Spacing, Protections, and Advanced. The Cost, Separation Weights, Interference Matrices, Protections, and Advanced tabs include parameters that are taken into account when estimating the cost. The Finalisation tab
provides options on how the AFP runs. The other tabs are used to define the allocation strategies for HSN, MAL, MAIO, and
BSICs assigned by the AFP.
You can make copies of the Atoll AFP module and set different parameters for each copy (for information on copying modules,
see start here XREF). All copies will be available in each AFP session. In other words, you will be able to choose from the list
of all Atoll AFP modules, each with its own defined parameters.
The settings of each Atoll AFP module are saved in the Atoll document but they can also be archived in the database so that
all users connected to the same centralised database can use them. For more information on archiving Atoll AFP module
settings, see the Administrator Manual.
For information on setting the parameters on each of the tabs of the Atoll AFP module, see the following:
7.5.2.2.1
7.5.2.2.2
400
Cost
Effect
AT332_UMR_E0
Selecting the Summed cost of all TRXs check box makes the AFP take the cost of all TRXs into account, whether or not they
exceed this quality target. If you clear this check box, the AFP will only take into account the costs of TRXs which do not fulfil
the quality thresholds defined in their corresponding subcells. In other words, the AFP dismisses any TRX whose quality is
better than the quality target, enabling it to concentrate the optimisation on the TRXs that really need improvement.
To display the Cost tab of the Atoll AFP module Properties dialog box:
1. Open the Atoll AFP Module Properties dialog box as explained in "Setting the Parameters of the Atoll AFP Module"
on page 399.
2. Click the Cost tab (see Figure 7.56).
For each missing or extra TRX: If desired, select the check box to make it active and set the cost for each missing
or unnecessary TRX.
For each corrupted TRX: If desired, select the check box to make it active and set the cost for each corrupted TRX.
For each out-of-domain TRX : If desired, select the check box to make it active and set the cost for each TRX that
has frequencies allocated to it that do not belong to its domain.
4. If desired, select the Intermodulation Tax check box to make it active and set the cost each applied to the total cost
each time intermodulation might occur because of the allocated frequencies.
5. Under Component per TRX, set the following parameters:
Interference: Set the cost for interference for each TRX. For more information on the AFP and interference, see
"Interference Cost" on page 396.
Separation: Set the cost for separation violation for each TRX. For more information on the AFP and separation
violation, see "An Example of Separation Violation Cost with Frequency Hopping" on page 395.
Modified TRX: If desired, select the check box to make it active and set the cost of modifying a TRX. For more information on the cost of modifying a TRX, see "The Cost of Missing and Corrupted TRXs" on page 397.
Outside preferred group: If desired, select the check box to make it active and set the cost of an allocated frequency being outside of the preferred group. For more information on the cost of using a frequency outside of the
preferred group, see "Preferred Group Cost" on page 397.
6. If desired, select the Sum of the costs of all TRXs check box to make it active. The AFP will take into account the sum
of th costs of all TRXs, including those that fulfil the quality thresholds defined in their corresponding subcells.
7. Under Traffic, select the traffic source the AFP will use during optimisation:
401
7.5.2.2.3
Based on the traffic demand (from the Subcells table or default traffic capture): If you choose to use the traffic
demand, the AFP will use either the traffic demand defined in the Subcells table or the default traffic capture
(depending on what you select when you run the AFP optimisation).
Based on the traffic demand calculated from traffic load, number of required TRXs, blocking probability, and
Erlang B formula: If you choose to use this option, the AFP will calculate the traffic demand from the traffic load,
the number of required TRXs, the blocking probability, and the Erlang B formula.
The Partial separation constraint violations section enables you to define the cost of the actual separation ("k") when a different separation ("s") is required. You can define the percentage of traffic of each TRX to be considered infor a partial separation
constraint violation. You can also add and remove partial separation constraints using the Add Separation and Remove Separation buttons at the bottom of the tab.
To display the Separations tab of the Atoll AFP module Properties dialog box:
1. Open the Atoll AFP Module Properties dialog box as explained in "Setting the Parameters of the Atoll AFP Module"
on page 399.
2. Click the Separations tab (see Figure 7.57).
402
AT332_UMR_E0
Click the Remove separation button. Atoll removes the last separation.
To add a separation:
Click the Add separation button. Atoll adds a separation entry to the end of the list under Properties and fills in
default values for each "k" value.
7.5.2.2.4
Co-transmitter violations
Co-site violations
Violations between neighbours
Violations between exceptional pairs
For more information on how Atoll combines interference matrices, see the Administrator Manual.
To display the Interference Matrices tab of the Atoll AFP Module Properties dialog box:
1. Open the Atoll AFP Module Properties dialog box as explained in "Setting the Parameters of the Atoll AFP Module"
on page 399.
2. Click the Interference Matrices tab (see Figure 7.58).
Figure 7.58: AFP Module Properties dialog box - Interference Matrices tab
The first component in combining interference matrices is whether a given interference matrix entry is within the
scope of the AFP.
3. Under The type of interference matrix, define the parameters for each section:
403
7.5.2.2.5
Measurement analysis
OMC statistics
Under Component depending on the interference matrix quality indicators, the Active check box is selected and
cannot be cleared. The Atoll AFP always includes the quality matrix specific to each type of interference matrix when
combining interference matrices.
7.5.2.2.6
By Subcell
By Transmitter
By Site
Free.
404
AT332_UMR_E0
4. Under MAL allocation type, select how the MAL will be allocated for groups of synchronised subcells.
5. Under MAL length, set the constraints that the Atoll AFP will follow to define the MAL length:
a. The first constraint concerns group-constrained subcells: the choice of MAL length for group-constrained subcells
is limited. Only the group lengths of each subcell frequency domain can be chosen.
b. Select either Max MAL length or Adjust MAL lengths. If you select Max MAL length, you do not need to set any
other constraints.
If you select Max MAL Length, it is not necessary to set any other constraints.
c. If you selected Adjust MAL lengths, set the following parameters to define how the Atoll AFP will set MAL lengths:
i.
Define the value that MAL length/Domain size must not be equal to or greater than.
ii. If you selected Different MALs within a synchronised set as the MAL allocation type in step 7.5.2.2.7, you can
select a Long or Short MAL Strategy (with the option of keeping MAL long enough to allow a certain pattern).
iii. Define a Target fractional load and select the Automatic adjustment check box if you want to give the AFP
the possibility of modifying this value automatically. The fractional load is the ratio of the number of TRXs with
a given MAL over the number of frequencies in the same MAL.
It is recommended that you let the AFP automatically adjust the target fractional load.
7.5.2.2.7
405
Fixed duration: If you select Fixed Duration, the AFP stops when this time has elapsed. If a stable solution has
been found prior to this limit, the allocation stops. Fixed duration corresponds to the minimum amount of time
you reserve for the AFP to find the best solution.
Directive duration: This is the Atoll AFP's default. If you select Directive duration, the Convergence criterion you
set in the AFP dialog box is used by the AFP to estimate the methods which will be used to find the best solution.
If the corresponding CPU time is long enough, the AFP will attempt to modify its internal calibration to better
match the network on which frequencies and resources are being allocated.
If the corresponding CPU time is shorter, the AFP will select a smaller number of methods and will not calibrate
its internal parameters.
If the AFP finds a stable solution before the end of the corresponding CPU time, the AFP will stop. On the other
hand, if convergence has not been reached by the end of the corresponding CPU time, the AFP will continue.
4. Under Result Assignment, select how the AFP assigns the results once the automatic allocation has stopped:
7.5.2.2.8
Manual Assignment: You can analyse the best plan before committing it to the document.
Automatic Assignment: The AFP automatically assigns the best plan to the document. This approach is recommended if Auto Backup is enabled.
406
AT332_UMR_E0
Min.: The AFP chooses the most compact scheme permitted by the constraints.
Max.: The AFP attempts to distribute the BSICs homogeneously.
5. Under Channels, define the spacing between channels to be used between channels during allocation:
6. Under MAIO, define the MAIO allocation strategy for frequency hopping:
7.5.2.2.9
407
For more information about protection against adjacent channel reuse, see "Adjacency Suppression" on page 408.
4. Under Interference definition with respect to the required quality threshold, set a C/I weighting margin around the
required quality threshold in order for the AFP to consider the traffic having close-to-threshold C/I conditions as neither 100% satisfactory nor 100% corrupted. For more information, "Interference Cost" on page 396.
Rigid: If you select Rigid, the AFP will evaluate interference only at the defined quality threshold.
Intermediate: If you select Intermediate, the AFP will evaluate interference at 3 reference points: the defined
quality threshold, and at +/- 2 dB of the quality threshold.
Flexible: If you select Flexible, the AFP will evaluate interference at 5 reference points: the defined quality
threshold, at +/- 2 dB of the quality threshold, and at +/- 4 dB of the quality threshold. Selecting Flexible has the
same effect as shadowing.
For interference matrices based on propagation, Atoll can determine whether they have
been calculated with shadowing. If shadowing has not been taken into account, the AFP
can adapt its settings to more realistically model the network. In other words, if you do not
take shadowing into consideration when calculating the interference matrix, Atoll can
automatically change its definition of interference from rigid to intermediate, or even to
flexible.
Adjacency Suppression
Adjacency suppression is defined as the difference between the required C/I and the required C/A (C/A being the "Carrier to
Adjacent Intensity ratio"). By default this is set to 18 dB following the GSM specification. You can change this value in the Properties dialog box of the Network Settings folder.
When the value of this parameter is used in the AFP (to extract the interference caused by an adjacent channel) you can apply
a small safety margin, temporarily reducing the 18 dB to 16.5, or even to 15.5. This safety margin is applied only in the AFP;
Atoll's predictions continue to apply the full adjacency suppression.
408
AT332_UMR_E0
For interference matrices based on propagation, Atoll can determine whether they have
been calculated with an overlap margin. If the overlap margin has not been used, the AFP
can adapt its settings to more realistically model the network. In other words, if you do not
take the overlap margin into consideration when calculating the interference matrix, Atoll
can automatically change the adjacent channel additional protection from none to weak
or to strong.
7.5.2.2.10
We have more frequencies over which the cost effects are counted.
It is harder to find clean frequencies since all frequencies are used all over.
The more the MALs are long, the less we have the benefice of FDM principle which is the main source of the GSM spectral
efficiency.
It is therefore easy to prove and to demonstrate that the fractional load cost all alone will privilege non hopping and base band
hopping plans, where the fractional load is 1. (m = n)
This corresponds to the case where all gains are 0 in the advanced property page below:
409
When setting non-0 gains in these tables (as by default), both the Interference diversity gain and the frequency diversity gain
are combined in order to reduce the interference probability. On the other hand, when it comes to separation calculation,
only the Interference diversity gains are considered.
The other options in this page were grouped into it because they share only one characteristic: They are all administrator
parameters. If you wish to change something in this page, please read the manual until the end of this chapter.
7.5.2.3.1
7.5.2.3.2
Currently, the AFP always assigns the same MAL to all TRXs within a subcell.
The "group constrained" assignment mode is applicable for SFH only. In NH and
BBH, the group constrained mode will only concern the respect of the preferred
group. Which is a different issue.
There is no contradiction between proffered group respect and the pre defined
MAL assignment in SFH. When both are relevant, each of the predefined MALs can
be more or less included in the preferred group and therefore more or less "preferred".
When azimuth oriented pattern allocation is performed at the same time as predefined MAL allocation, only the biggest groups in the domain will be used for the
pattern, while the small ones will be used for MAL assignment.
If two subcells have different domains, they cannot belong to the same atom.
If two subcells have different limitations on "Max MAL Length", they cannot belong to the same atom.
A warning is generated when HSN assignment directives contradict with these restrictions.
You can force the AFP to always assign the same MAL among the subcells of the Atom.
When calculating the cost of a TRX in an Atom:
It is possible that none of the co-Atom TRXs interfere with the given TRX. This is the most common case, and it is due to the
fact that the "on air" frequencies are never the same. However, it is possible that intra-Atom interference exists. In that case,
the burst collision which is calculated conform to the MAIO definitions, multiplies the interference probability.
410
AT332_UMR_E0
7.5.2.3.3
Synchronous Networks
Through working at atom level, and consulting a user defined synchronisation reference given in the subcell table, the AFP
can fully exploit the benefits of synchronisation in a GSM network. It is capable of extending Atoms beyond the limit of a site
and, by doing so, using the MAIO assignment to further resolve violations or interference. (For this you must choose the free
HSN assignment option, and enable the HSN assignment).
7.5.2.3.4
7.5.2.3.5
Fractional Load
The Atoll AFP uses the user-defined fractional load as a guide when assigning the HSN and determining the MAL length. A
fractional load of X is obtained if the number of TRXs using a certain MAL is only X times the length of the MAL. In Atoll, fractional load does not take the traffic load into consideration.
Because the fractional load cannot always be met, this parameter is considered a guide rather than a constraint. When it can
be met, the AFP chooses either a MAL length 1/X times longer than the number of TRXs in the biggest subcell of the atom or
a MAL length 1/X times longer than the sum of all TRXs in the atom. These are called "the short MAL strategy" and "the long
MAL strategy" respectively. You can choose between the two in the MAL tab of the properties dialog box. The value of the
fractional load parameter can also be edited and, furthermore, it can even be automatically calibrated by the AFP.
7.5.2.3.6
7.5.2.3.7
HSN Allocation
The AFP assigns HSNs at subcell level. It chooses different HSNs for interfering and non-synchronous subcells. For synchronous
subcells (usually within a site), the AFP can opt to assign the same HSN and different MAIOs within the set of same-HSN
subcells.
According to the adapted convention on HSNs for BBH TRXs, the AFP allocates different HSNs to the BCCH TRX and TCH TRXs.
The 1st HSN corresponds to timeslots 1 through 7 of the BCCH and TCH TRXs, and the second HSN corresponds to the timeslot
0 of the TCH TRXs only. The second HSN is used in predictions.
The user can control the HSN allocation so that it performs one of the following:
7.5.2.3.8
MAIO Allocation
The AFP assigns MAIOs to TRXs so that the same MAL can be reused within a subcell, within a transmitter or even within a
site. The separation requirements must be satisfied for frequencies that are on air, at all frame numbers. The cost function
411
averages the cost upon all frame numbers in the synchronised case and upon all collision probabilities in the non-synchronised
case.
The subcells must be or in synthesised hopping mode, or must have a group constrained allocation directive. This condition is also the condition that determines weather a user defined preferred group can impact the cost.
The pattern directive in the AFP property pages defines if we are doing 1/1, 1/3 or 1/5 pattern allocation. By default
it is set to 1/3. We will now refer to its value as X.
The AFP group weight must not be 0.
Only the X biggest groups in the domain will be considered as candidates for the proffered group allocation.
Only transmitters in the AFP scope will get a preferred group.
The AFP assigned preferred group will overwrite whatever used defined preferred group.
Only transmitters that are not lonely in their site will be entitled to a preferred group:
The pattern allocation associates the X main direction axes with the X biggest groups in the domains
Not lonely means that other transmitters of the same band, and layer, (and also active), exist in the site.
It assumes these groups are disjoint.
It finds the main axis azimuth as the most commune azimuth, and then it spans the other directions so that all the
X axes are equi spread.
It matches each directional axis to a group.
The AFP will only allocate a preferred group if the transmitters azimuth is clearly aligned with one of the directional
axes.
Even if only 50% of the subcells receive a preferred group, the allocation can be very strongly impacted because of
second order influence.
We recommend using this because it regulates the assignments, and helps the AFP to exist local minima. Be sure to always
have 3 big and disjoint groups in your domain.
(If the majority of your sites are X-sectorial, X should replace 3).
We recommend not imposing the pattern very strongly on your network. It should be kept as a guideline.
Hard Constraint: The same BSIC must not be allocated to two transmitters that:
It is only based on first and second order neighbour relations and BCCH co-channel reuse.
Soft Constraint: The same BSIC should not be allocated to two transmitters that:
It is based on first- and second-order neighbour relations, interference matrices, and co- and adjacent channel BCCH
reuse. This means that the soft constraint is more demanding than the hard constraint, and has a higher probability
of not being satisfied.
If the AFP is unable to satisfy the soft constraints, the BSIC allocation algorithm assigns the "least interfering" BSIC to
transmitters depending on the interference and separation relations. This leads to increasing the same BSIC+BCCH
reuse distance as much as possible.
412
AT332_UMR_E0
In the preceding definitions, all neighbour relations between transmitters are considered, independently of the direction, as
shown in Figure 7.64 on page 413.
Min.: The AFP assigns the minimum possible number of BSICs that satisfies the constraints.
Max.: The AFP assigns as many BSICs as possible while keeping them evenly distributed.
The goal of the AFP is to determine the best trade-off between the blocking due to interferences (also called soft blocking)
and the blocking due to traffic (also called hard blocking) by the optimisation of the number of TRXs.
In order to control the process of optimising the number of TRxs, you can modify the following parameters:
Increasing the missing TRX tax influences the Atoll AFP Module to respect the number of required TRXs.
Increasing the interference weight influences the creation of a small number of TRXs
In the case of high values of traffic loads (which forces the Atoll AFP Module to create extra TRXs), reducing the maximum blocking rate limits the number of extra TRXs.
This strategy may also affect the initial subcell loads and KPIs would have to be recalculated after the automatic frequency
planning process.
In this chapter, we will explain the entire process, so that you fully understand this optimization capacity and by thus understand how to control it.
413
7.5.3.1.1
When evaluating the resulting frequency plan, it is important to keep in mind how this frequency plan was created: it was
created to maximise the correctly served traffic instead of trying to simply minimise the interfered traffic. For example, if
plan A has more TRXs than plan B, it is possible that an interference prediction for plan A will display more interference, even
if plan A is the best plan. It consists on the positive attitude: trying to maximise the correctly served traffic instead of trying to
minimise the interfered traffic. This is taken into consideration in the method used to evaluate the AFP results (todo XXXX put
ref).
The AFP and Local Frequency Availability
Combining both soft and hard blocking, the AFP optimises the amount of correctly served traffic for each individual transmitter using frequencies available to it. In this example, there is a transmitter with two subcells: TCH and BCCH. The two subcells
absorb the traffic demand together. Let us assume that the traffic demand consists of 25 Erlangs of circuit-switched traffic,
and 5 timeslots of packet-switched traffic. Let us also assume that the required number of TCH TRXs is 2 with 1 BCCH TRX.
The AFP could just assign 3 TRXs in this cell, exactly as required, or it could study a few additional possibilities:
414
AT332_UMR_E0
Blocked
Traffic
(Timeslots)
Traffic
load
(%)
Interfered traffic
on f1 and f2
(Timeslots)
2 TRXs: using
f1 and f2.
21
7.4
100%
1.5
0: Since it is
not used
0: Since it is
not used
Frequency
plan 2:
3 TRXs: using
f1, f2 and f3.
32.2
0.55
97.7%
1.46
1.56
0: Since it is
not used
Frequency
plan 3:
4 TRXs: using
f1, f2, f3, and
f4.
43.4
0: No
blocking
with 4 TRXs.
74%
1.1
1.18
1.77
Frequency
Plan
TRXs
Frequency
plan 1:
Interfered
traffic on f3
(Timeslots)
Interfered
traffic on f4
(Timeslots)
The best plan depends on the locally available frequencies: if there was less interference, the AFP would have chosen
frequency plan 3. If f3 and f4 where heavily interfered, the AFP would have chosen frequency plan 1. Because the AFP tries to
minimise what is in bold in the table above (i.e., the blocked and interfered traffic), it chooses frequency plan 2 (in which the
figures in bold add up to 3.57 timeslots).
7.5.3.1.2
7.5.3.1.3
415
The more demand exists, the higher will be the pressure on the AFP to allocate more transmitters. As said above, the demand
can come from the traffic model, from the subcell table, or from the traffic load values. If demand come from the traffic
capture, you can increase demand by recalculating the capture with a higher traffic coefficients. If demand comes from the
OMC, you can boost it by using a spreadsheet. If demand comes from traffic loads you can do the following:
In the AFP property pages, where you indicate that the demand should be regenerated from the traffic loads, you are also
requested to bound the actual blocking rate (actual with respect to the number of required transmitters). This is because of
the following reason:
If your served traffic load is 100%, theoretically, only an infinite circuit demand can generate such a load
7.5.3.1.4
416
AT332_UMR_E0
Less Interference
The example shows that interference can be greatly reduced. The following graphs show the effect of adjusting the number
of TRXs on the interfered and served traffic, compared to the initial dimensioning.
417
The preceding 4 frequency plans were all generated using exactly 50 frequencies. All other network parameters remained the
same.
In the plan "Dim - 76 TRXs" many TRXs were removed by the AFP (76 out of 820). Removing the TRXs reduced interference by
a considerable margin but had no impact on the amount of served traffic because reducing TRXs was only considered if the
transmitter's load was low.
Re-adjusting the Number of TRXs to Match OMC Traffic
In a real network, it is often necessary to re-adjust the number of TRXs to match evolution of the traffic.
A typical situation is the following snap shot; taken before any adaptation is made.
418
AT332_UMR_E0
Figure 7.69: Frequency reuse balancing with or without TRX number adjustment
In this example, most TRXs that were removed were removed in the 900 band (In the first half of the graph, the red line is
almost always below the blue line.)
7.5.3.2.1
The context of an interference matrix is used mainly to indicate the statistical quality off the interference matrix so that the
AFP can weight the information read from the interference matrix accordingly.
Atoll supports a wide number of AFP tools. The interference matrix combination process, which is a part of the cost function,
can be different in different AFP tools. The concept of an interference matrix context permits a common representation and
significance of the parameters influencing the combination process. These parameters are, therefore, described as a set of
quality indicators, with meaningful units, such as the number of measurement days, standard deviation, calculation resolution, and whether the interference matrix is based on traffic or surface area.
The nine predefined types of interference matrices are divided into four groups with respect to their quality indicator representation: OMC-based, drive-test-based, propagation-based, and others. The General tab of the Interference Matrix Properties dialog box gives you access to this information:
419
420
The standard deviation, depending on the equipment quality and measurement post-processing
The average number of measurement points in the test mobile data that correspond to a single matrix calculation
point.
The standard deviation, depending on the equipment quality and measurement post-processing
The average number of measurement points in the handover statistics that correspond to a single matrix calculation point
The volume of information
Whether the interference information (probabilities) correspond to traffic or surface area.
The standard deviation, depending on the equipment quality and measurement post-processing
The average number of CW measurement points that correspond to a single matrix calculation point
The volume of information
Whether the interference information (probabilities) correspond to traffic or surface area.
AT332_UMR_E0
The standard deviation, depending on the equipment quality and measurement post-processing
The average number of measurement points in the scan data drive test data that correspond to a single matrix
calculation point
The volume of information
Whether the interference information (probabilities) correspond to traffic or surface area.
The context of an interference matrix is not systematically included in the interference matrix files. That is why Atoll asks the
user to set up the type and quality indicators of the interference matrix manually.
7.5.3.2.2
In other words, the lack of information can be interpreted as either no interference or as unknown interference.
If there is only one interference matrix (i.e., only one source of interference information) then no interference is the same as
unknown interference.
If there is more than one interference matrix, the information missing in one matrix might be available in another. Therefore,
it becomes very important to distinguish between the two cases in order to intelligently combine different interference matrices.
421
For example, if you have three interference matrices and, for a given pair of subcells, you have 60% interference in one,
unknown interference in the second, and unknown interference in the third, the resulting interference when the three matrices are combined will be 60%. However, if for the same pair of subcells, you have 60% interference in one, no interference in
the second, and no interference in the third, the resulting interference when the three matrices are combined will be only
20%.
The ideal method for differentiating between no interference and unknown interference would be to keep a matrix of values
in memory, which would indicate the reliability of each matrix entry, and thereby indicate the entries for which the interference is "Unknown" as unreliable entries. Unfortunately, this would be completely impractical because this matrix of values
would be too large to work with.
Therefore, Atoll implements a slightly restricted approach for storing the scope of interference matrices. Interference matrices contain two reliability indicators at transmitter level, i.e., the reliability when a transmitter is the victim, and the reliability
when it is the interferer. This information is stored in the columns % of Victim Coverage and % of Interferer Coverage.
The reliability of an entry (i, j) is calculated as follows:
VictimCoverage(Transmitter(i)) * InterfererCoverage(Transmitter(j))
This implementation is simple and sufficient for the most interference matrices.
Creation of the Interference Matrix Scope
The scope of an interference matrix is created by the tool that creates the interference matrix. If the interference matrix is
created by Atoll, the AFP scope will be set to the initial set of victims, corresponding to SEL + RING (see "The Scope of the AFP
and the Scope of the Interference Matrix" on page 372). This means that even when only one transmitter is present inside the
computation zone, many other transmitters might be taken into account. Atoll adds all potential interferers to this set, and
calculates the interference matrix entries between all pairs of this set. This set becomes the scope of the interference matrix,
with 100% at both victim and interferer coverage.
Other software can be used to edit the interference matrix scope using the general API features, or by saving the interference
matrix as a CLC file and editing it. The CLC file format can store all the interference matrix information (see the Technical Reference Guide for more information).
The scopes of the interference matrices are automatically created when old CLC,
IM0, IM1, or IM2 files are imported. The scope is created using the current BSIC
and BCCH allocation, and finding the set of all victims and the set of all interferers.
The interference matrix scope internally manages the transmitter IDs. When
exchanging information with a CLC file, these ID's are visible to the user. They are
arbitrary numbers used to index the interference matrix entries. Even if an addin
is used to create the interference matrix, the association of transmitter names to
IDs is carried out by Atoll. The addin will associate the interference information to
pairs of transmitter ID's.
The CLC and DCT files have the same mapping of transmitter names to transmitter
IDs. There are no restrictions on transmitter IDs as long as they are unique integers
under 231.
Two possibilities (examples) for editing the interference matrix information could be:
An addin that imports an interference matrix should know its scope. For example, if it is an OMC addin, and the OMC
covers 50 transmitters, the scope will contain 50 transmitters. Their indexes will be supplied by Atoll once added to
the scope. The percentage of victim and interferer coverage should be 100%.
When generating an interference matrix from CW measurements, there might be a few transmitters which were correctly scanned and others that were not. In this case, the correctly scanned transmitters would have good percentage
of victim and interferer coverage, while the others would not.
7.5.3.2.3
422
AT332_UMR_E0
Instead of updating the interference matrix every time a transmitter is renamed or deleted, Atoll stores the events in memory,
and updates the interference matrix only when it is used. It checks the ADO record ID's and, if they have been changed, the
changes are taken into account.
When an Interference matrix is externalised, Atoll does not always manage to keep it updated as described above.
Calculate your Interference Matrices as often as you calculate your path loss matrices.
7.5.3.2.4
The cost function definition does not change. If earlier, interference values were read from a single interference
matrix. Now, they are read from more than one interference matrix.
When the interference matrices are correctly managed in Atoll, no further parameterisation (weighting) is required.
The Interference Matrices tab (see "The Interference Matrices Tab" on page 403) available in the Atoll AFP Module properties
dialog box displays and lets to modify the weights that control the interference matrix combination.
The interference matrix combination is carried out as follows:
1. The Atoll AFP Module asks Atoll to load a subset of the active interference matrices of the document. This subset is
determined by comparing each interference matrix scope with the AFP scope. Only the interference matrices whose
scope intersects the AFP scope are loaded.
2. The Atoll AFP Module then reads the scope and context information of each loaded interference matrix.
The interference, p(i, v, x), of subcell i (interferer) on subcell v (victim) for a given C/I level x, can be read from more
than one interference matrix.
3. The Atoll AFP Module combines all the values of p(i, v, x) by performing a weighted average. Therefore, it calculates
as many weights as the number of p(i, v, x) entries for a pixel. These "reliability weights" are calculated by multiplying
the following three components:
a. Component quantifying the membership to the AFP scope:
VictimCoverage(Transmitter(v)) x InterfererCoverage(Transmitter(i))
For interference matrices based on OMC statistics, if the scope indicates that both i and v had the same BCCH, the
component will be 0.
b. Component depending on the interference matrix type.
c. Component depending on the interference matrix quality indicators: The "Reliability Calculation". The equations
are different for the different classes of types since the quality indicators are different as well:
i.
Where is the standard deviation of the propagation model, and r is the calculation resolution. A resolution
of 50 m and a standard deviation of 7.5 dB gives a weight of 1.
ii. Interference matrix based on measurements from the OMC performed during n days:
1+n
Component C = ---------------3
1 + n r + 1
Component C = --------------------------------------------4 + 1
423
An external ID space of the TRXs of a transmitter (important for import and export utilities).
MAL/channel at TRX level.
MAIO at TRX level.
Fine locking: The user can lock specific TRXs in an unlocked transmitter.
The TRX table does not contain an "active" field. Therefore, all TRXs in it should contain a valid frequency or MAL and are all
considered to be on air. It is better to remove a TRX record than removing only the frequency or MAL from its channels list.
There are certain factors which affect the AFP directives that can be set at different levels in the GSM project:
During an AFP optimisation, the channels and MAIO currently assigned to a TRX will not be changed if the TRX is locked
in the TRXs table or if the transmitter is locked in the Transmitters table.
The AFP weighing can be set at the transmitter level and at the subcell level. The final AFP weight will be the product
of both weights (i.e., the transmitter AFP weight multiplied by the subcell AFP weight).
The domain definition can be modified at the subcell level by defining excluded channels.
Some AFP-relevant entries can be found in the TRXs, Subcells, and Transmitters tables, creating a certain level of redundancy:
The channel list in the Transmitters table is a combination of all channels appearing in the TRXs of a transmitter
(depending on the hopping modes used and the number of subcells).
The hopping mode of a transmitter is the hopping mode of its default traffic carrier (the TCH TRX Type).
The frequency band of the transmitter (the one used by the propagation model), is read from the domain of the BCCH
subcell of the transmitter.
Atoll considers the lowest level of information as the accurate source. For example:
Atoll automatically updates the TRXs table if the channel list of a transmitter in the Transmitters table is modified.
The frequency band of a transmitter cannot be edited.
In cases where the data management is perfectly controlled (for example, when several users are working on the same
project), it can happen that issues of consistency can occur. In that case, you might want to run a subcell audit as explained in
"Checking Consistency in Subcells" on page 461 to verify where consistency has been lost and how to correct it.
7.5.3.3.1
As it is during an AFP process that frequencies and MALs/MAIOs for different TRXs of a subcell are chosen, the AFP tool stores
and manipulates the information about TRXs in good and in bad conditions.
If you choose AFP Rank indicator to be allocated when starting an AFP session, each cost improving solution will go through a
TRX rank assignment. If no improving plan is found, TRX rank will be assigned for the initial plan (like BSIC). TRX ranking within
a subcell is performed on the basis of TRX costs.
A TRX will be considered locked for TRX Rank assignment if and only if it is not selected for AFP allocation or if it has been
locked.
The Theory of "Scheduling" in Frequency Planning
TRX rank is Atoll's AFP implementation of "Scheduling", which can help increase performance in certain particular cases.
Example: imagine the case where a cell and its neighbour are not loaded with traffic at the same time (for example, a stadium
424
AT332_UMR_E0
and its parking lot). In such cases, it is possible to decrease call blocking by adding one or two dirty TRXs to the concerned cells.
(assuming clean TRXs do not exist for spectral reasons). What you will need to do is the following:
1. You need an OMC that can be informed about the TRX ranking, and that knows not to use the bad TRXs when load is
normal or low. They get into use only when the load is high.
2. You need to relax the interference matrix entries and the separation relation constraints between the two oppositely
correlated cells.
3. You need to run the AFP with TRX rank.
The spectral efficiency of scheduling can not be fully acquired by real time RRM, since the latest is of a caustic nature. You can
be sure to obtain a bigger gain if the scheduling order is predefined.
7.5.3.3.2
7.5.3.3.3
7.5.3.4.1
First, we launch the AFP during X/2 hours, then; we stop it and commit the results (if good).
Lock all TRXs in the network.
Find the areas that generate problems. For example, some sites with separation violations.
Unlock the worst 10 sites.
For each such site, unlock 2 - 4 neighbouring transmitters.
Run the AFP for an additional X * 30 minutes (the remaining half of the time).
A more simple way to detect the hard spots is by committing cell or site level KPIs to the corresponding tables. The principle
remains the same: Let the AFP work only on the small part where the interference is strongest.
7.5.3.4.2
425
7. Specify a long execution time (1500 to 4000 minutes) and let the AFP work on the core for this entire target time. The
target time should be long enough for the AFP to generate at least 800 solutions. The AFP should be run using a cost
for changing the TRX channel. (we want to minimise the number of changes).
8. Assuming that the long execution on a small area had improved the result, commit the plan.
9. If not, reduce the cost of changing a TRX, or reduce the number of locked transmitters, or both. Repeat the two previous steps until an improving long execution is achieved.
10. Now you can run the AFP on entire network. Keep the same cost for changing a TRX, so that the basic plan obtained
in the beginning is not too strongly modified.
If step N 10 has provided a good plan then it might be worth while sharing your AFP experience with all the other users:
7.5.3.4.3
426
AT332_UMR_E0
demonstrates the fact that geographic interference combination is more accurate than the interference cost of the AFP
because of counting this point only once as an interfered point (and not twice as in the AFP).
7.5.3.4.4
The mixed option: The interference information contains the traffic information as well. In this way, each IM entry will
contain the quantity of traffic interfered if a co-channel or adjacent channel reuse exists.
The separated option: The AFP has separate access to traffic load information and to interference probabilities (As in
Atoll).
The main reasons for choosing the second implementation are the following:
Option 2 is a superset that contains option 1. But option 1, being a subset, does not contain option 2 (i.e. once the
information are mixed they cannot be separated).
It does not create any overhead (the size of the additional information is negligible compared to the size of the IM).
It helps keeping the unit definitions simpler.
It facilitates merging IMs with different traffic units.
The traffic information can be used for weighting the separation violation component, as well as the interference component.
The traffic load can be used in deciding whether a TRX can be left uncreated.
The gain introduced by the traffic load of the interferer depends on the hopping mode and the MAL length. Incorporating this gain in the IM (as a result of the mixed option) means that the IMs become hopping-mode and MAL-size
dependent. This is a bad idea since the AFP should be able to change the MAL. And the user should be able to change
the hopping mode without recalculating the IM. In addition, an IM calculated externally to Atoll, with a non-hopping
BCCH can be used for the hopping TCH.
427
Figure 7.74: Condition settings for an Interfered Zones (DL) coverage prediction
3. Under Coverage Conditions:
428
AT332_UMR_E0
After defining and calculating the coverage prediction as explained in "Studying Interference Areas" on page 436, generate a
report as explained in ""Generating Coverage Prediction Reports" on page 212. When the Columns to Be Displayed dialog box
appears, select the check boxes corresponding to the following columns (see Figure 7.74):
Figure 7.76: Defining the report on the Interfered Zones coverage prediction
The resulting report is shown in Figure 7.77.
429
For each TRX, a given amount of traffic is spread uniformly over the TRX service zone.
Part of this traffic is interfered because the C/I conditions are bad. The part that is interfered is added up in the report.
In Figure 7.77, the interfered traffic for channel 25 is outlined in red.
The total amount of traffic per TRX is the sum of:
Served load (timeslots weighted by the AFP weight): The traffic load is multiplied first by the AFP cost factor and
then multiplied by the number of timeslots.
Served load (Erlangs weighted by the half rate traffic ratio): The traffic load is multiplied first by the number of
timeslots and then multiplied by 1/(1 - Half of the half-rate ratio)
The total amount of traffic per TRX is given in parentheses, and added. This way, you can see the ratio between interfered
traffic and the total amount of traffic. The final ratio is outlined in green in Figure 7.77.
Atoll's AFP cost function is given using the same units as those used to display the data in the column called Served load
(Timeslots weighted by the AFP weight)
The report displayed in Figure 7.77 is TRX-based and is therefore much more precise than worst case surface estimations that
are usually observed when you look at the results of a coverage prediction in the map window.
430
AT332_UMR_E0
You can also study interference areas by using the Point Analysis window:
"Analysing Interference Areas Using the Point Analysis Tool" on page 439
"Example of Analysing Interference Using a Point Analysis" on page 441.
Atoll also enables you to model interference coming from an external project. For more information, see "Modelling Intertechnology Interference" on page 507.
Non-hopping mode: A TRX channel of the selected TRX type (BCCH, TCH, TCH_EGPRS or TCH_INNER).
Base-band hopping: The MAL of the subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER).
Synthesised-frequency hopping: The MAL-MAIO of the subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER).
"studies.XML" file created in the installation folder if at least one coverage prediction is saved using the Save as Customised Prediction command.
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 99.
6. Click the Conditions tab. On this tab, you can define the signals that will be considered for each pixel.
431
Figure 7.79: Condition settings for a Coverage by C/I Level (DL) prediction
7. Under Coverage Conditions:
Click the down arrow button and select one of the following thresholds:
Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power
reduction) as the lower end of the signal level range.
Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range.
Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level
or specifically for each transmitter. When you select "HCS Servers" or "All," there might be areas where several
transmitters experience interference. On these pixels, several DL CI values are calculated. Therefore, on the Display tab, you select to display either the lowest DL CI level or the highest DL CI level (for more information, see
"Comparing Service Areas in Calculations" on page 484).
Enter an Overlap margin. The default value is "4 dB."
If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability.
Shadowing margins (depending on the entered cell edge coverage probability and the model standard deviation
per clutter class) are applied only to the values for C. For more information, see "Modelling Shadowing" on
page 506.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
You can select the type of TRX to consider as a potential victim by selecting it from the Interfered Subcells list.
You can filter the subcells by Channel or by Frequency Band. Atoll will calculate interference only for the selected
channel or frequency band in this coverage prediction.
432
Channel: Select Channel as shown in Figure 7.80 and enter the channel number for which Atoll will calculate
interference in this prediction. Atoll ignores by default all the TRXs using baseband or synthesised hopping. If
you clear the Non-Hopping Only check box, all the TRXs using the defined channel will be considered as potential victims. If the Non-Hopping Only check box is cleared and the defined channel is in a MAL, interference
will be calculated for the entire MAL. When you define a channel, Atoll uses it to identify only victim TRXs; all
TRXs are taken into account as interferers.
AT332_UMR_E0
Figure 7.80: Filtering subcells by channel in Coverage by C/I Level (DL) predictions
Frequency Band: Select Frequency Band as shown in Figure 7.81 and choose from the drop-down menu the
frequency band for which Atoll will calculate interference in this prediction. Atoll ignores by default all the
TRXs using baseband or synthesised hopping. If you clear the Non-Hopping Only check box, all the TRXs using
the selected frequency band will be considered as potential victims.
Figure 7.81: Filtering subcells by frequency band in Coverage by C/I Level (DL) predictions
Click the down arrow button and select one of the following thresholds:
Subcell C/I Threshold: to use the CI threshold specified for each subcell (including the defined power reduction) as the lower end of the CI range.
Global C/I Threshold: to enter a threshold to be used for all subcells as the lower end of the CI range.
Subcell C/I Threshold: to use the CI threshold specified for each subcell (including the defined power reduction) as the upper end of the CI range.
Global C/I Threshold: to enter a threshold to be used for all subcells as the upper end of the CI range.
The defined CI values define the range of CI values to be displayed. Values outside of this
range are not displayed.
You can not select Subcell C/I Threshold as both the lower and the upper end of the CI
range to be considered.
Select whether you want the defined DL CI or CI+N condition to be Satisfied By:
At least one TRX: When you select the option At least one TRX, the defined interference condition must be
satisfied by at least one TRX on a given pixel for the results to be displayed on that pixel.
The worst TRX: When you select the option The worst TRX, Atoll selects the worst results for each pixel. If the
worst results do not satisfy the defined interference condition, the results will not be displayed on that pixel.
These options are available only if a lower C/I Threshold is set.
If you have selected "C/(I+N)", you can define the value to be added to the interference. The defined noise figure
is added to the thermal noise value (defined by default at -121 dBm) to calculate the value of N. Select one of the
following:
Based on Terminal: Select Based on Terminal if you want to use the noise figure defined for a terminal and
select the terminal from the list.
Fixed Value: Select Fixed Value if you want to enter a value and then enter the noise figure in the text box.
9. If you want discontinuous transmission mode for TRXs which support it taken into account during the calculation of
interference, select the DTX taken into account check box and enter the percentage of time during which a user is
talking in the Voice Activity Factor text box.
10. Select the Traffic Load that will be used to calculate interference:
433
11. From the Interference Sources list, select whether interference should be calculated from adjacent channels, co-channels, or from both. The adjacent channel effect on the victim channel, i.e., the interference, is decreased by the adjacent channel protection level.
Inter-technology interference is taken into account by default. For more information, see
"Modelling Inter-technology Interference" on page 624. By adding an option in the Atoll.ini
file, you can add an Inter-technology check box which will allow you to consider or not
inter-technology interference.
12. Select the Detailed Results check box if you want to display detailed results per transmitter. The results displayed
depend on the subcell frequency hopping mode:
Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping mode.
Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in synthesised
frequency hopping mode.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
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.
Non-hopping mode: A TRX channel of the selected TRX type (BCCH, TCH, TCH_EGPRS or TCH_INNER).
Base-band hopping: The MAL of the subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER).
Synthesised-frequency hopping: The MAL-MAIO of the subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER).
434
AT332_UMR_E0
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the "<GUID>" and "</GUID>" tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction is saved using the Save as Customised Prediction command.
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 99.
6. Click the Conditions tab. On this tab, you can define the signals that will be considered for each pixel.
Figure 7.82: Condition settings for a Coverage by C/I Level (UL) prediction
7. Under DL Coverage Conditions, set the following parameters:
Click the down arrow button and select one of the following thresholds:
Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power
reduction) as the lower end of the signal level range.
Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range.
Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level
or specifically for each transmitter.
Enter an Overlap margin. The default value is "4 dB."
If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability.
Shadowing margins (depending on the entered cell edge coverage probability and the model standard deviation
per clutter class) are applied only to the values for C. For more information, see "Modelling Shadowing" on
page 506.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
Select the terminal type to be considered on each pixel by selecting it from the Terminal list. The UL transmitted
power is based on the max power of the selected terminal, gains and losses.
For information on the Terminal Specifications dialog box, see "Modelling Terminals" on page 249.
Click the down arrow button and select one of the following thresholds:
Subcell C/I Threshold: to use the CI threshold specified for each subcell (including the defined power reduction) as the lower end of the C(I+N) range.
Global C/I Threshold: to enter a threshold to be used for all subcells as the lower end of the C(I+N) range. You
may also let this field blank in order not to consider any lower C(I+N) boundary.
Click the down arrow button and select one of the following thresholds:
435
Subcell C/I Threshold: to use the CI threshold specified for each subcell (including the defined power reduction) as the upper end of the CI range.
Global C/I Threshold: to enter a threshold to be used for all subcells as the upper end of the CI range. You
may also let this field blank in order not to consider any upper C(I+N) boundary.
The defined CI values define the range of CI values to be displayed. Values outside of this
range are not displayed.
9. Select the Detailed Results check box if you want to display detailed results per transmitter. The results displayed
depend on the subcell frequency hopping mode:
Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping mode.
Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in synthesised
frequency hopping mode.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
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.
Non-hopping mode: A TRX channel of the selected TRX type (BCCH, TCH, TCH_EGPRS or TCH_INNER).
Base-band hopping: The MAL of the subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER).
Synthesised-frequency hopping: The MAL-MAIO of the subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER).
436
AT332_UMR_E0
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the "<GUID>" and "</GUID>" tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction is saved using the Save as Customised Prediction command.
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 99.
6. Click the Conditions tab. On this tab, you can define the signals that will be considered for each pixel.
Click the down arrow button and select one of the following thresholds:
Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power
reduction) as the lower end of the signal level range.
Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range.
In Figure 7.79, a Global C Threshold less than or equal to -105 dBm will be considered.
Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level
or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations" on
page 484).
Enter an Overlap margin. The default value is "4 dB."
If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability.
Shadowing margins (depending on the entered cell edge coverage probability and the CI standard deviation per
clutter class) are applied only to the values for C. Shadowing margins are not taken into account in determining
the values for interference. For more information, see "Modelling Shadowing" on page 506.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
437
You can select the type of TRX to consider as a potential victim by selecting it from the Interfered Subcells list.
You can filter the interfered subcells by Channel or by Frequency Band. Atoll will calculate interference only for
the selected channel or frequency band in this coverage prediction.
Channel: Select Channel as shown in Figure 7.84 and enter the channel number for which Atoll will calculate
interference in this prediction. Atoll ignores by default all the TRXs using baseband or synthesised hopping. If
you clear the Non-Hopping Only check box, all the TRXs using the defined channel will be considered as potential victims. If the Non-Hopping Only check box is cleared and the defined channel is in a MAL, interference
will be calculated for the entire MAL. When you define a channel, Atoll uses it to identify only victim TRXs; all
TRXs are taken into account as interferers.
Figure 7.84: Filtering subcells by channel in Interfered Zones (DL) coverage prediction
Frequency Band: Select Frequency Band as shown in Figure 7.85 and choose from the drop-down menu the
frequency band for which Atoll will calculate interference in this prediction. Atoll ignores by default all the
TRXs using baseband or synthesised hopping. If you clear the Non-Hopping Only check box, all the TRXs using
the selected frequency band will be considered as potential victims.
Figure 7.85: Filtering subcells by frequency band in Interfered Zones (DL) coverage prediction
Click the down arrow button and select one of the following thresholds:
Subcell C/I Threshold: to use the CI threshold specified for each subcell (including the defined power reduction) as the lower end of the CI range.
Global C/I Threshold: to enter a threshold to be used for all subcells as the lower end of the CI range.
Subcell C/I Threshold: to use the CI threshold specified for each subcell (including the defined power reduction) as the upper end of the CI range.
Global C/I Threshold: to enter a threshold to be used for all subcells as the upper end of the CI range.
If you have selected "C/(I+N)", you can define the value to be added to the interference. The defined noise figure
is added to the thermal noise value (defined at -121 dBm) to calculate the value of N. Select one of the following:
Based on Terminal: Select Based on Terminal if you want to use the noise figure defined for a terminal and
select the terminal from the list.
Fixed Value: Select Fixed Value if you want to enter a value and then enter the noise figure in the text box.
9. If you want discontinuous transmission mode for TRXs which support it taken into account during the calculation of
interference, select the DTX taken into account check box and enter the percentage of time during which a user is
talking in the Voice Activity Factor text box.
10. Select the Traffic Load that will be used to calculate interference:
11. From the Interference Sources list, select whether the interference should be calculated from adjacent channels, cochannels, or from both. The adjacent channel effect on the victim channel, i.e., the interference, is decreased by the
adjacent channel protection level.
Inter-technology interference is taken into account by default. For more information, see
"Modelling Inter-technology Interference" on page 624. By adding an option in the Atoll.ini
file, you can add an Inter-technology check box which will allow you to consider or not
inter-technology interference.
438
AT332_UMR_E0
12. Select the Detailed Results check box if you want to display detailed results per transmitter. The results displayed
depend on the subcell frequency hopping mode:
Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping mode.
Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in synthesised
frequency hopping mode.
The quality received on each interfered area: Select "Value Intervals" as the Display Type and "C/I Level (dB)" as
the Field. In the Network explorer, the coverage prediction results are first arranged by interfered transmitter and
then by C/I level.
For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
14. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
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.
As explained in "Generating Coverage Prediction Reports" on page 212, you can
display a prediction report on the interfered predictions indicating the amount of
correctly served traffic out of the total traffic covered by the coverage prediction
by selecting the options Served load (Timeslots weighted either by the AFP
weight or by the Half rate traffic ratio) after having calculated the prediction
report.
The total served load (Timeslots weighted by the AFP weight) is obtained by the
product between the number of timeslots, the AFP weight and the traffic load.
The total served load (Timeslots weighted by the HR Ratio) is obtained by the product between the number of timeslots, 1 1 HR 2 and the traffic load.
The actual loads given by the report come from the ratio between the covered area
and the total service area.
) in the Radio Planning toolbar. The Point Analysis window appears and the
pointer changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and
the current position. You can move the receiver on the map or centre the map window on the receiver (see "Moving
the Receiver on the Map" on page 203).
3. Select the Interference view.
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. The information displayed in the bar graph depends on the hopping mode of the subcell identified in the
left margin of the graph:
439
In Non-Hopping Mode, you can study the interference level on either a specific channel or on the most interfered
one of either of a specific subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER) or all of the selected transmitter.
In Base Band Hopping Mode, you can study the interference level on either a specific MAL or on the most interfered one of either of a specific subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER) or all of the selected transmitter.
In Synthesised Frequency Hopping Mode, you can study the interference level on either a specific MAL-MAIO pair
or on the most interfered one of either of a specific subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER) or all of the
selected transmitter.
Figure 7.86 on page 441 gives an example of the Interference view. The signal level of the transmitter, Site10_3, is
-95.61 dB and is indicated by a red bar. The black bar indicates the total interference experienced by the receiver
(-98.65 dB). The seven interferers are responsible for -102.69 dB (olive green), -103.06 dB (yellow), -107.31 dB
(purple), -111.56 dB (olive green), -115.38 dB (green), -115.50 dB (pink), and -117.13 dB (olive green). The bars indicating the interference caused by Site17_1 and Site15_1 are only partially filled. The entire bar indicates the interference that could potentially be caused by the transmitter whereas the filled part of the bar indicates the actual
interference caused. A transmitters actual interference can be lower than its potential interference:
In the map window, arrows from the receiver to each transmitter are displayed in the colour of the transmitters they
represent. The interference levels at the receiver from transmitters are displayed as captions for these arrows. 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-channel or adjacent channel interference.
4. You can change the following options at the top of the Interference view:
Transmitter: Select the transmitter from the list. The transmitters in the list are sorted in the order of decreasing
signal level received at the pointer location.
Subcell: Select the subcell type (or ALL) to be analysed.
TRX: Select whether you want the interference to be studied on a specific item (channel, MAL or MAL-MAIO
according to the hopping mode) or the most interfered item.
Interference: Select whether the interference should be calculated from adjacent channels, co-channels, or from
both.
Inter-technology interference is taken into account by default. For more information, see
"Modelling Inter-technology Interference" on page 624. By adding an option in the Atoll.ini
file, you can add an Inter-technology check box which will allow you to consider or not
inter-technology interference.
) to display the Calculation Options dialog box and 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. For more information, see "Modelling Shadowing" on page 506.
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. Indoor losses are defined per frequency per
clutter class. For more information, see "Taking Indoor Losses into Account" on page 203.
6. In the Interference view toolbar, you can use the following tools:
) to copy the content of the view and paste it as a graphic into a graphic editing or word-
440
AT332_UMR_E0
along with information on the channel being interfered and the type of interference, i.e., co-channel or adjacent channel.
8. You can change the following options at the top of the Details tab:
Interference Method: Select whether the interference is calculated by CI or by C(I+N). Thermal noise is taken
into account in the second method only.
For each transmitter, you can display the interference on each subcell or on the most interfered one. You can click the
Expand button ( ) of each transmitter order to expand the list of all its interferers and their individual I and C/I levels.
In this example, the studied transmitter is Site10_3. Potential interference from all interferers (both co-channel and adjacent
channel) received on all its TRXs is studied; in other words, the worst case is studied. The requested cell edge coverage probability is 75%. As with interfered zones coverage predictions and coverage predictions by CI levels, Atoll analyses the most
interfered channel of the studied transmitter if it is using non-hopping model.
BRU038_G2 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined.
Channel 17 is assigned to the TCH TRX.
BRU099_G1 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined.
Channel 17 is assigned to the TCH TRX.
BRU005_G1 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined.
Channel 16 is assigned to the BCCH TRX.
BRU063_G1 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined.
Channel 17 is assigned to the BCCH TRX.
BRU096_G3 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined.
Channel 17 is assigned to the BCCH TRX.
BRU061_G3 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined.
Channel 17 is assigned to the BCCH TRX.
441
BRU094_G3 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined.
Channel 17 is assigned to the TCH TRX.
BRU065_G3 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined.
Channel 18 is assigned to the TCH TRX.
BRU006_G3 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined.
Channel 16 is assigned to the TCH TRX.
Non-hopping mode is assigned to the all the subcells, whatever the TRX type is (BCCH or TCH).
The signal level of the transmitter BRU038_G2 is -81.33 dBm and is indicated by a light green bar. It could have been
-75.94 dB, but was decreased by 5.39 dB due to the shadowing margin. Only the signal level (C) is reduced by the shadowing margin (as calculated by the cell edge coverage probability and the CI standard deviation defined per clutter
class). The interference level (I) is not affected by the shadowing margin.
The black bar indicates the total interference experienced by the receiver (-84.74 dB). Atoll calculates the interference
level by considering 100% of the voice activity factor and traffic load. Neither DTX, nor the traffic load of TRXs are taken
into account in evaluating the interference levels.
The eight interferers are responsible for -86.56 dB (Dark Blue), -93.94 dB (Green), -95.13 dB (Cyan), -96.44 dB (Light
Green), -101.56 dB (Orange), -103.13 dB (Yellow), -107.06 dB (Yellow) and -109.19 dB (Green). The bars indicating the
interference caused by BRU005_G1, BRU065_G3 and BRU006_G3 are only partially filled. An entire bar indicates the
interference that could potentially be caused by the transmitter whereas a filled part of the bar indicates the actual
interference caused.
Intra-technology third order intermodulation interference can also be optionally displayed. This option requires activation through changes in the database. When available, the intra-technology third order intermodulation interference level is displayed as a bar with the title format "Interferer Name: I3 (first channel, second channel)". For more
information on how to activate this option, contact support.
At the top of the Interference view, the name of the most interfered channel on BRU038_G2 is channel 17 and the C/I received
is 3.41 dB. An analysis of the interferers gives the following information:
The bars representing BRU099_G1, BRU063_G1, BRU096_G3, BRU061_G3 and BRU094_G3 are full. On two out of five
transmitters, channel 17 is assigned to the TCH TRX of the transmitter. For the other three transmitters, channel 17 is
assigned to the BCCH TRX. They are, therefore, co-channel interferers. No power reduction is defined, therefore the
interference is not reduced.
The bars representing BRU065_G3, BRU006_G3 and BRU005_G1 are partly full. The bars are only partly full because
the interference is reduced: on these transmitters, channel 17 is not assigned; channel 16 is assigned to the BCCH TRX
of BRU005_G1 and to the TCH TRX of BRU006_G3. In addition, channel 18 is assigned to the TCH TRX of BRU065_G3.
They are, therefore, adjacent channel interferers and their interference is reduced by the adjacent channel protection
level of 18 dB (the default value defined in the GSM Network Settings properties). No power reduction is defined for
this subcell. If a power reduction of 3 dB had been defined for this subcell, the interference would have been reduced
by an additional 3 dB. A fractional load might be another reason for reduced interference.
442
AT332_UMR_E0
You can make a coverage prediction of the coding schemes for either GPRS, for EDGE, or for both. The choice of coding scheme
is based on the DL radio conditions (C, C and C/I, or C/N, C/N and C/(I+N)). Therefore, the better the values for C and CI are,
the higher the throughput of the selected coding scheme will be.
As well, you can restrict the coverage prediction to a selected terminal or mobility or to a combination of terminal and mobility. When you restrict the coverage prediction to a selected terminal, Atoll bases the coverage prediction on the C and CI
graphs for the selected terminal, as well as on its noise figure. As well, Atoll respects the terminals defined coding scheme
limit. When you select a mobility, Atoll considers which transmitters have the coding scheme configuration that can support
the selected mobility and the coding scheme threshold for that mobility. For information on defining a terminal, see "Modelling Terminals" on page 249.
A coverage prediction by coding schemes enables you to determine the coding scheme assigned to transmitters sharing either
an identical channel or an adjacent channel with other transmitters. Coding schemes are assigned according to the DL radio
condition (i.e., C, C and C/I, with or without thermal noise) and optionally according to a specific hopping mode, frequency
band, mobility type and MAL (See "Creating or Modifying a Coding Scheme Configuration" on page 496 for more information).
To make a coverage prediction by GPRS/EDGE coding schemes:
1. Select the Network explorer.
2. Right-click the Predictions folder. The context menu appears.
3. Select New Prediction from the context menu. The Prediction Types dialog box appears.
4. Select Coverage by GPRS/EDGE Coding Scheme (DL) and click OK.
5. Click the General tab. On this tab, you can change the Name of the prediction, the Resolution, and add Comments.
The Receiver height corresponds to the height of the receiver defined in the Calculation Parameters tab of the Network Settings Properties dialog box.
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the "<GUID>" and "</GUID>" tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction is saved using the Save as Customised Prediction command.
Under Display Configuration, you can create a Filter to select which sites to display in the results. You can also display
the results grouped in the Network explorer 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 99;
for information on grouping, see "Advanced Grouping of Data Objects" on page 96; for information on sorting, see
"Advanced Sorting" on page 98.
6. Click the Conditions tab. On this tab, you can define the signals that will be considered for each pixel.
443
Figure 7.87: Condition settings for a coverage prediction by GPRS/EDGE coding scheme
7. Under Coverage Conditions, set the following parameters:
Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level
or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations" on
page 484).
Enter an Overlap margin. The default value is "4 dB."
If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability.
Shadowing margins (depending on the entered cell edge coverage probability and the CI standard deviation per
clutter class) are applied only to the values for C. Shadowing margins are not taken into account in determining
the values for interference. For more information, see "Modelling Shadowing" on page 506.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
8. Under Interference Condition, you can define how Atoll will calculate interference for the GPRS/EDGE coding scheme
coverage prediction.
If, under GPRS/EDGE, you select C and not CI for the coverage prediction, the only option
you need to select under Interference Condition is the TRX type to consider from the TRXs
list.
You can select the following parameters:
You can select which TRX type to consider as potential victim by selecting it from the Interfered Subcells list.
If you want discontinuous transmission mode for TRXs which support it taken into account, select the DTX taken
into account check box and enter the percentage of time during which a user is talking in the Voice Activity Factor
text box.
Select the Traffic Load that will be used to calculate interference:
444
From the Interference Sources list, select whether the interference should be calculated from adjacent channels,
co-channels, or from both. The adjacent channel effect on the victim channel, i.e., the interference, is decreased
by the adjacent channel protection level.
AT332_UMR_E0
Inter-technology interference is taken into account by default. For more information, see
"Modelling Inter-technology Interference" on page 624. By adding an option in the Atoll.ini
file, you can add an Inter-technology check box which will allow you to consider or not
inter-technology interference.
Select the Detailed Results check box if you want to display detailed results per transmitter. The results displayed
depend on the subcell frequency hopping mode:
Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping mode.
Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in synthesised frequency hopping mode.
From the Coding Schemes list, select the technology on which the coding scheme calculation will be based:
All: If you select All, both GPRS coding schemes and EDGE coding schemes will be used.
GPRS: If you select GPRS, only GPRS coding schemes will be used.
EDGE: If you select EDGE, only EDGE coding schemes will be used. Depending on the selected GPRS/EDGE
configurations, EDGE coding schemes can be of the type EGPRS (Standard EDGE) or EGPRS2 (EDGE Evolution).
Select whether you want to base the coverage prediction on C or C and CI. If you select C, the only option you
need to select under Interference Condition is the TRX type to consider from the TRXs list.
If desired, select which Terminal you want to base the coding scheme coverage prediction on. When you restrict
the coverage prediction to a selected terminal, Atoll bases the coverage prediction on the C and CI graphs for the
selected terminal, as well as on its noise figure. As well, Atoll respects the terminals defined coding scheme limit.
If desired, select which Mobility you want to base the coding scheme coverage prediction on. When you select a
mobility, Atoll considers which transmitters have the coding scheme configuration that can support the selected
mobility and relative threshold.
Enter a Noise Figure. By default, a noise figure of 8 dB is used if no terminal is selected.
Select the Thermal Noise Taken into Account check box if you want Atoll to consider thermal noise.
Select the Ideal Link Adaptation check box if you want the coding scheme that offers the highest throughput to
be selected. Otherwise, Atoll will choose the coding scheme according to signal level and quality.
11. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
RLC throughput per timeslot: Based on the coding scheme determined on each pixel (see "Making a Coverage Prediction by GPRS/EDGE Coding Schemes" on page 442) and the calculated quality, Atoll extracts the RLC throughput per
timeslot as defined in the coding scheme configuration assigned to transmitters.
Application throughput per timeslot for a selected service: Using the RLC throughput per timeslot and the application
throughput parameters (scaling factor and offset) defined for the selected service (see "Modelling Services" on
page 241), Atoll evaluates the throughput per timeslot on the application layer.
445
Effective RLC Throughput for a selected service-terminal pair: Using the RLC throughput per timeslot, Atoll can evaluate a maximum throughput for a selected terminal, assuming that the terminal uses several timeslots to transmit the
packet-switched data. The number of timeslots used by the terminal is given by the product of the number of DL
timeslots per carrier and the number of simultaneous carriers (for EDGE evolution terminals) as defined in the terminal properties (see "Modelling Terminals" on page 249). For example, for an EDGE evolution terminal using 4 DL
timeslots on a carrier and 2 simultaneous carriers, the maximum throughput will be 8 times the corresponding RLC
throughput per timeslot. In addition, the number of timeslots per carrier defined in the terminal can be limited by the
maximum number of timeslots permitted for the considered service (see "Modelling Services" on page 241).
Application Throughput for a selected service-terminal pair: Using the application throughput per timeslot for a
selected service, Atoll can evaluate a maximum throughput for a selected terminal, assuming that the terminal uses
several timeslots to transmit the packet-switched data. The number of timeslots used by the terminal is given by the
product of the number of DL timeslots per carrier and the number of simultaneous carriers (for EDGE evolution terminals) as defined in the terminal properties (see "Modelling Terminals" on page 249). For example, for an EDGE evolution terminal using 4 DL timeslots on a carrier and 2 simultaneous carriers, the maximum throughput will be 8 times
the corresponding application throughput per timeslot. In addition, the number of timeslots per carrier defined in the
terminal can be limited by the maximum number of timeslots permitted for the considered service (see "Modelling
Services" on page 241).
Application throughput per User for a selected service-terminal pair and considering the reduction factor obtained
from a selected dimensioning model: Using the maximum throughput for a selected service terminal, Atoll can evaluate an end-user throughput by applying a reduction factor expressing the actual capacity of the serving transmitter
and its occupancy to the maximum throughput. The reduction factor is obtained from the dimensioning model graphs
(see "Defining a GSM/GPRS/EDGE Dimensioning Model" on page 330) and is the function of the number of available
connections and the subcell traffic load. The number of connections is the ratio between the number of available
packet timeslots (the sum of dedicated packet-switched and shared timeslots) and the number of terminal timeslots
(as seen above).
You can make a throughput coverage prediction for either GPRS, for EDGE, or for both. As well, you can restrict the coverage
prediction to a selected terminal or mobility or to a combination of terminal and mobility. When you restrict the coverage
prediction to a selected terminal, Atoll bases the coverage prediction on the C and CI graphs for the selected terminal. As
well, Atoll respects the terminals defined coding scheme limit. When you select a mobility, Atoll considers which transmitters
have the coding scheme configuration that can support the selected mobility. Atoll can use the noise figure defined for the
selected terminal or a user-defined noise figure if no terminal is selected or if the calculations are based on an interpolation
of the values for CI and C(I+N). For information on defining a terminal, see "Modelling Terminals" on page 249.
To make a coverage prediction by packet throughput per timeslot:
1. Select the Network explorer.
2. Right-click the Predictions folder. The context menu appears.
3. Select New Prediction from the context menu. The Prediction Types dialog box appears.
4. Select Packet Quality and Throughput Analysis (DL) and click OK.
5. Click the General tab. On this tab, you can change the Name of the prediction, the Resolution, and add Comments.
The Receiver height corresponds to the height of the receiver defined in the Calculation Parameters tab of the Network Settings Properties dialog box.
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the "<GUID>" and "</GUID>" tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction is saved using the Save as Customised Prediction command.
Under Display Configuration, you can create a Filter to select which sites to display in the results. You can also display
the results grouped in the Network explorer 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 99;
for information on grouping, see "Advanced Grouping of Data Objects" on page 96; for information on sorting, see
"Advanced Sorting" on page 98.
6. Click the Conditions tab. On this tab, you can define the signals that will be considered for each pixel.
446
AT332_UMR_E0
Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming the signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level
or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations" on
page 484).
Enter an Overlap margin. The default value is "4 dB."
If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability.
Shadowing margins (depending on the entered cell edge coverage probability and the CI standard deviation per
clutter class) are applied only to the values for C. Shadowing margins are not taken into account in determining
the values for interference. For more information, see "Modelling Shadowing" on page 506.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
Select the Detailed Results check box if you want to display detailed results per transmitter. The results displayed
depend on the subcell frequency hopping mode:
Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping mode.
Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in synthesised frequency hopping mode.
8. Under Interference Condition, you can define how Atoll will evaluate interference for the coding scheme and consequently the throughputs.
If, under GPRS/EDGE, you select Based on C for the coverage prediction, the only option
you need to select under Interference Condition is the TRX type to consider from the TRXs
list.
You can select the following parameters:
You can select which TRX type to consider as potential victim by selecting it from the Interfered Subcells list.
If you want discontinuous transmission mode for TRXs which support it taken into account, select the DTX taken
into account check box and enter the percentage of time during which a user is talking in the Voice Activity Factor
text box.
Select the Traffic Load that will be used to calculate interference:
447
From subcell table: The subcell traffic load as defined or as calculated during dimensioning.
From the Interference Sources list, select whether the interference should be calculated from adjacent channels,
co-channels, or from both. The adjacent channel effect on the victim channel, i.e., the interference, is decreased
by the adjacent channel protection level.
Inter-technology interference is taken into account by default. For more information, see
"Modelling Inter-technology Interference" on page 624. By adding an option in the Atoll.ini
file, you can add an Inter-technology check box which will allow you to consider or not
inter-technology interference.
From the Coding Schemes list, select the technology for which the packet throughput per timeslot calculation will
be calculated:
All: If you select All both GPRS coding schemes and EDGE coding schemes will be used.
GPRS: If you select GPRS only GPRS coding schemes will be used.
EDGE: If you select EDGE only EDGE coding schemes will be used. Depending on the selected GPRS/EDGE
configurations, EDGE coding schemes can be of the type EGPRS (Standard EDGE) or EGPRS2 (EDGE Evolution).
Select Based on C if you want to base the coverage prediction on C. If you select Based on C, the only option you
need to select under Interference Condition is the TRX type to consider from the TRXs list. Otherwise, select Based
on CI.
If desired, select which Terminal you want to base the coverage prediction on. When you restrict the coverage
prediction to a selected terminal, Atoll bases the coverage prediction on the C and CI graphs for the selected terminal. As well, Atoll respects the terminals defined coding scheme limit and noise figure. Selecting a terminal is
obligatory if you are making a maximum or user throughput coverage prediction because it is necessary to know
the number terminal timeslots.
If desired, select which Mobility you want to base the coding scheme coverage prediction on. When you select a
mobility, Atoll considers which transmitters have the coding scheme configuration that can support the selected
mobility.
Enter a Noise Figure. By default, the noise figure is 8 dB.
Select the Thermal Noise Taken into Account check box if you want Atoll to consider thermal noise.
If you want to display either an application throughput/timeslot coverage prediction, or a maximum or an enduser throughput coverage prediction, select the service from which the application throughput parameters will be
extracted.
Select the Ideal Link Adaptation check box if you want the coding scheme that offers the highest throughput per
timeslot for a given C or C and CI to be selected. Otherwise, Atoll will choose the coding scheme by considering
only the coding scheme admission threshold in terms of C and/or CI.
10. Under Application Throughput per User, select the dimensioning model from which the load reduction factor can be
extracted in order to display an end-user throughput prediction.
11. Click the Display tab.
For a coverage prediction by packet throughput, the Display Type "Value Intervals" based on the Field "Effective RLC
Throughput/Timeslot" is selected by default. If desired, you can change the values displayed by selecting one of the
following values from the Field list:
448
Effective RLC Throughput/Timeslot: Each layer shows the Effective RLC Throughput/Timeslot that a transmitter
can carry on one timeslot per pixel.
Max Effective RLC Throughput/Timeslot: The resulting coverage provides the maximal Effective RLC Throughput/
Timeslot on each pixel from the previous display.
Average Effective RLC Throughput/Timeslot: Gives the average Effective RLC Throughput/Timeslot that the transmitter can carry on one timeslot averaged on each pixel. If there are different coverage areas for different TRXs,
this coverage prediction will calculate the union of these coverages and display the average values over these coverage areas, whereas the other coverage predictions for Effective RLC Throughput/Timeslot perform an intersection of these coverage zones, keeping the minimum value of throughput per pixel.
Application Throughput/Timeslot: Each layer shows the application throughput/timeslot that a transmitter can
carry on one timeslot for a particular service per pixel.
Max Application Throughput/Timeslot: The resulting coverage provides the maximal application throughput/
timeslot on each pixel for a particular service provided by a specific terminal from the previous display.
Average Application Throughput/Timeslot: The average application throughput/timeslot that the transmitter
can carry on one timeslot averaged on each pixel for a particular service. If there are different coverage areas for
different TRXs, this coverage prediction will calculate the union of these coverages and display the average values
over these coverage areas, whereas the other coverage predictions for application throughput/timeslot perform
an intersection of these coverage zones, keeping the minimum value of throughput per pixel.
Effective RLC Throughput: Each layer shows the max RLC throughput that a transmitter can provide to a selected
terminal per pixel.
AT332_UMR_E0
Max Effective RLC Throughput: The resulting coverage provides the maximal RLC throughput on each pixel from
the previous display.
Average Effective RLC Throughput: Gives the average RLC throughput that a transmitter can provide to a selected
terminal averaged on each pixel. If there are different coverage areas for different TRXs, this coverage prediction
will calculate the union of these coverages and display the average values over these coverage areas, whereas the
other coverage predictions for max RLC throughput perform an intersection of these coverage zones, keeping the
minimum value of throughput per pixel.
Application Throughput: Each layer shows the throughput that a transmitter can provide to a selected terminal
per pixel.
Max Application Throughput: The resulting coverage gives the maximal throughput on each from the previous
display.
Average Application Throughput: Gives the average throughput that the transmitter can provide to a selected terminal averaged on each pixel. If there are different coverage areas for different TRXs, this coverage prediction will
calculate the union of these coverages and display the average values over these coverage areas, whereas the
other coverage predictions for throughput perform an intersection over these coverage zones keeping the minimum value of throughput per pixel.
Application Throughput per User: Each layer shows the throughput that a transmitter can provide to a user on a
pixel, considering load reduction factors.
Max Application Throughput per User: The resulting coverage gives the maximal user application throughput on
each pixel from the previous display.
Average Application Throughput per User: The average throughput that the transmitter can provide to a user
averaged on each pixel. If there are different coverage areas for different TRXs, this coverage prediction will calculate the union of these coverages and display the average values over these coverage areas, whereas the other
coverages for throughput perform an intersection over these coverage zones, keeping the minimum value of
throughput per pixel.
For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
12. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
449
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the "<GUID>" and "</GUID>" tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction is saved using the Save as Customised Prediction command.
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 99.
6. Click the Conditions tab. On this tab, you can define the signals that will be considered for each pixel.
Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level
or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations" on
page 484).
Enter an Overlap margin. The default value is "4 dB."
If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability.
Shadowing margins (depending on the entered cell edge coverage probability and the model standard deviation
per clutter class) are applied to the values for C. For more information, see "Modelling Shadowing" on page 506.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
Select the Detailed Results check box if you want to display detailed results per transmitter. The results displayed
depend on the subcell frequency hopping mode:
Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping mode.
Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in synthesised frequency hopping mode.
8. Under Interference Conditions, you can define how Atoll will calculate CI for the BLER coverage prediction.
450
AT332_UMR_E0
You can select which TRX type to consider as potential victim by selecting it from the Interfered Subcells list.
If you want discontinuous transmission mode for TRXs which support it taken into account, select the DTX taken
into account check box and enter the percentage of time during which a user is talking in the Voice Activity Factor
text box.
Select the Traffic Load that will be used to calculate interference:
From the Interference sources list, select whether the interference should be calculated from adjacent channels,
co-channels, or from both. The adjacent channel effect on the victim channel, i.e., the interference, is decreased
by the adjacent channel protection level.
If the coverage prediction is set to be Based on C (under GPRS/EDGE), you can only
select the Interfered sources and the TRX type to consider (Interfered subcells).
Inter-technology interference is taken into account by default. For more information, see "Modelling Inter-technology Interference" on page 507. By adding an
option in the Atoll.ini file, you can add an Inter-technology check box which will
allow you to consider or not inter-technology interference.
From the Coding Schemes list, select the technology for which the packet throughput per timeslot calculation will
be calculated:
All: If you select All both GPRS coding schemes and EDGE coding schemes will be used.
GPRS: If you select GPRS only GPRS coding schemes will be used.
EDGE: If you select EDGE only EDGE coding schemes will be used. Depending on the selected GPRS/EDGE
configurations, EDGE coding schemes can be of the type EGPRS (Standard EDGE) or EGPRS2 (EDGE Evolution).
Select Based on C if you want to base the coverage prediction on C. If you select Based on C, the only option you
need to select under Interference Condition is the TRX type to consider from the TRXs list. Otherwise, select Based
on CI.
If desired, select which Terminal you want to base the coverage prediction on. When you restrict the coverage
prediction to a selected terminal, Atoll bases the coverage prediction on the C and CI graphs for the selected terminal, as well as on its noise figure. As well, Atoll respects the terminals defined coding scheme limit.
If desired, select which Mobility you want to base the coding scheme coverage prediction on. When you select a
mobility, Atoll considers which transmitters have the coding scheme configuration that can support the selected
mobility and relative threshold.
Enter a Noise Figure. By default, a noise figure of 8 dB is used if no terminal is selected.
Select the Thermal Noise Taken into Account check box if you want Atoll to consider thermal noise.
Select the Ideal Link Adaptation check box if you want the coding scheme that offers the highest throughput to
be selected. Otherwise, Atoll will chose the coding scheme according to signal level and quality.
BLER (%): The coverage is coloured according to the block error rate measured per transmitter. If the throughput
per timeslot is greater than the maximum throughput per timeslot, the BLER is 0%.
Max BLER: Gives the coverage according to the maximum block error rate per pixel for each transmitter.
For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
11. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
451
If a terminal type is not defined or does not have codec configuration assigned, Atoll considers the codec configuration
assigned to the transmitter only.
If the terminal and the transmitter have different codec configuration, Atoll determines the intersection of the codec
modes contained in the transmitter and terminal codec configuration. The codec mode is then selected according to
the calculated CN or CN and CI + N on and optionally according to a specific hopping mode, frequency band,
mobility type and MAL (See "Creating or Modifying Codec Configuration" on page 493 for more information) each
pixel. For a given quality or a given codec mode, look-up tables defined in codec configuration provide the circuit
quality indicator (BER, FER, or MOS) displayed as a result.
The quality indicator used for ideal link adaptation is determined by the codec configuration assigned to the transmitters.
To make a circuit quality indicator coverage prediction:
1. Select the Network explorer.
2. Right-click the Predictions folder. The context menu appears.
3. Select New Prediction from the context menu. The Prediction Types dialog box appears.
4. Select Circuit Quality Indicator Analysis (DL) and click OK. The coverage prediction Properties dialog box appears.
5. Click the General tab. On this tab, you can change the Name of the prediction, the Resolution, and add Comments.
The Receiver height corresponds to the height of the receiver defined in the Calculation Parameters tab of the Network Settings Properties dialog box.
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the "<GUID>" and "</GUID>" tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction is saved using the Save as Customised Prediction command.
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 99.
6. Click the Conditions tab. On this tab, you can define the signals that will be considered for each pixel.
452
AT332_UMR_E0
Figure 7.90: Condition settings for a Circuit Quality Indicator Analysis (DL) prediction
7. Under Coverage Conditions, set the following parameters:
Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level
or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations" on
page 484).
Enter an Overlap margin. The default value is "4 dB."
If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability.
Shadowing margins (depending on the entered cell edge coverage probability and the model standard deviation
per clutter class) are applied to the values for C. For more information, see "Modelling Shadowing" on page 506.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
Select the Detailed Results check box if you want to display detailed results per transmitter. The results displayed
depend on the subcell frequency hopping mode:
Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping mode.
Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in synthesised frequency hopping mode.
8. Under Interference Condition, you can define how Atoll will calculate interference for the throughput per timeslot
coverage prediction.
If, under Quality Indicators Calculation, you select Calculations Based on CN for the
coverage prediction, the only option you need to select under Interference Condition is
the TRX type to consider from the TRXs list.
You can select the following parameters:
You can select which TRX type to consider as potential victim by selecting it from the Interfered Subcells list.
If you want discontinuous transmission mode for TRXs which support it taken into account, select the DTX taken
into account check box and enter the percentage of time during which a user is talking in the Voice Activity Factor
text box.
Select the Traffic Load that will be used to calculate interference:
From the Interference Sources list, select whether the interference should be calculated from adjacent channels,
co-channels, or from both. The adjacent channel effect on the victim channel, i.e., the interference, is decreased
by the adjacent channel protection level.
453
Inter-technology interference is taken into account by default. For more information, see
"Modelling Inter-technology Interference" on page 624. By adding an option in the Atoll.ini
file, you can add an Inter-technology check box which will allow you to consider or not
inter-technology interference.
9. Under Quality Indicators Calculation, set the following parameters:
Select Calculations Based on CN if you want to base the coverage prediction on CN. If you select Calculations
Based on CN for the coverage prediction, the only option you need to select under Interference Condition is the
TRX type to consider from the TRXs list. The codec mode is selected only according to signal level.
Select Calculations Based on C(I+N) if you want to base the coverage prediction on CN and C(I+N).
If desired, select which Terminal you want to base the coverage prediction on. When you restrict the coverage
prediction to a selected terminal and the terminal type and the transmitter have different codec configuration,
Atoll determines the intersection of the codec modes contained in the transmitter and terminal codec configuration. The codec mode is then selected according to the calculated CN or CN and CI + N on each pixel. For a given
quality or a given codec mode, look-up tables defined in codec configuration provide the circuit quality indicator
(BER, FER, or MOS) displayed as a result.
If desired, select which Mobility you want to base the coding scheme coverage prediction on. When you select a
mobility, Atoll considers the codec mode applicable for the selected mobility on the codec configuration.
Enter a Noise Figure. By default, a noise figure of 8 dB is used if no terminal is selected.
BER: The coverage is coloured according to the bit error rate measured per transmitter.
FER: The coverage is coloured according to the frame erasure rate measured per transmitter.
MOS: The coverage is coloured according to the mean opinion score measured per transmitter.
Max BER: The coverage is coloured according to the maximum bit error rate per pixel of the covering transmitters.
Max FER: The coverage is coloured according to the maximum frame erasure rate per pixel of the covering transmitters.
Max MOS: The coverage is coloured according to the maximum mean opinion score per pixel of the covering
transmitters.
For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
11. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The results of circuit
quality indicator coverage predictions based on BER, FER, or MOS are broken down by transmitter, as you can see by clicking
the Expand button ( ) to expand the results of the coverage prediction after you have calculated it. The results of circuit quality indicator coverage predictions based on Max BER, Max FER, or Max MOS are broken down by threshold.
454
AT332_UMR_E0
You can make service area analysis coverage predictions whether channels have been allocated or not. If you have not yet
allocated frequencies, you can do so before carrying out the coverage prediction described in this section. For information on
creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, MAIOs" on page 340.
You can also restrict the coverage prediction to a selected terminal or mobility or to a combination of terminal and mobility.
When you restrict the coverage prediction to a selected terminal, the coverage prediction is based on the C and CI graphs for
the selected terminal, as well as on its noise figure. The defined codec mode (or coding scheme) limit of the terminal is
respected. When you select a mobility, the transmitters that have a codec (or coding scheme) configuration that supports the
selected mobility and the codec mode (or coding scheme) threshold for that mobility are considered. For information on
defining a terminal, see "Modelling Terminals" on page 249.
To make a coverage prediction on a service area:
1. Select the Network explorer.
2. Right-click the Predictions folder. The context menu appears.
3. Select New Prediction from the context menu. The Prediction Types dialog box appears.
4. Select one of the following predictions and click OK:
"studies.XML" file created in the installation folder if at least one coverage prediction is saved using the Save as Customised Prediction command.
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 99.
6. Click the Conditions tab. On this tab, you can define the signals that will be considered for each pixel.
455
Figure 7.91: Condition settings for a Service Area Analysis (DL) prediction
7. Under Coverage Conditions, set the following parameters:
Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level
or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations" on
page 484).
Enter an Overlap margin. The default value is "4 dB."
If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability.
Shadowing margins (depending on the entered cell edge coverage probability and the model standard deviation
per clutter class) are applied to the values for C. For more information, see "Modelling Shadowing" on page 506.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
8. Under Interference Condition, you can define how interference is evaluated for the codec mode (or coding scheme)
selection.
You can select the following parameters:
You can select which TRX type to consider as a potential victim by selecting it from the Interfered Subcells list.
If you want discontinuous transmission mode is supported by the TRXs, select DTX taken into account and in the
Voice activity factor, enter the percentage of time during which a user talks.
Select the Traffic load that will be used to calculate interference:
From the Interference Sources list, select whether the interference should be calculated from adjacent channels,
co-channels, or from both. The adjacent channel effect on the victim channel, i.e., the interference, is decreased
by the adjacent channel protection level.
Inter-technology interference is taken into account by default. For more information, see
"Modelling Inter-technology Interference" on page 624. By adding an option in the Atoll.ini
file, you can add an Inter-technology check box which will allow you to consider or not
inter-technology interference.
456
From the Coding Schemes list, select the technology for which the packet throughput per timeslot calculation will
be calculated:
AT332_UMR_E0
All: If you select All, both GPRS coding schemes and EDGE coding schemes will be used.
GPRS: If you select GPRS, only GPRS coding schemes will be used.
EDGE: If you select EDGE, only EDGE coding schemes will be used. Depending on the selected GPRS/EDGE
configurations, EDGE coding schemes can be of the type EGPRS (Standard EDGE) or EGPRS2 (EDGE Evolution).
Select Ideal Link Adaptation to select the coding scheme that offers the highest throughput. Otherwise, Atoll
chooses the coding scheme according to signal level and quality.
Select Calculations Based on CN if you want to base the coverage prediction on CN. If you select Calculations
based on CN for the coverage prediction, the only option to select under Interference conditions is the TRX type
to consider from the TRXs list. The codec mode (or coding scheme) is selected according to signal level and
receiver noise N.
Select Calculations Based on C(I+N) if you want to base the coverage prediction on CN and C(I+N).
If necessary, select the Terminal on which you want to base the coverage prediction. When you restrict the coverage prediction to a selected terminal and the terminal type and the transmitter have different codec (or coding
scheme) configurations, Atoll determines the intersection of the codec modes (or coding schemes) contained in
the transmitter and terminal codec (or coding scheme) configuration. The codec mode (or coding scheme) is then
selected according to the calculated CN or CN and CI + N on each pixel.
If necessary, select the Mobility on which you want to base the coding scheme coverage prediction. When you
select a mobility, Atoll considers the codec mode (or coding scheme) applicable for the selected mobility on the
codec configuration.
Enter a Noise Figure. By default, a noise figure of 8 dB is used if no terminal is selected.
Select which Service you want to base the coverage prediction on. If you select a circuit-switched service, the service will be served if at least one codec mode can be selected. If you select a packet-switched service, the service
will be served if at least one coding scheme can be selected.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Select the transmitter whose signal is interfered from the Victim list or click the Victim button (
the transmitter by clicking it on the map.
Select the transmitter whose signal is interfering from the Interferer list or click the Interferer button (
select the transmitter by clicking it on the map.
The victim and interferer transmitters are displayed on the map with specific icons (
and
) and select
) and
).
3. Under Coverage conditions, select what you are going to base the interference calculation on:
457
4. Click Calculate. The interference will be displayed on the map if you have selected the Visible check box (see Figure
7.92).
After you have calculated the interference as explained earlier in this section, click the Histogram button. The Statistics window appears.
Under Histogram based on covered areas, you can select to view a histogram, CDF, or inverse CDF based on area
or percentage.
The Zoom on selected values section displays the covered area values, or the percentage of the covered area,
along the y-axis against the coverage criterion along the x-axis. You can zoom in on values by clicking and dragging
in the Zoom on selected values list. Atoll will zoom in on the selected values.
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.
The transmitters to be allocated: The transmitters to be allocated, or TBA transmitters, are the active and filtered
transmitters belonging to the transmitters folder from which the AFP was started and that are located within the focus
zone.
The potential interferers: The potential interferers are transmitters whose calculation radius intersects the calculation radius of any TBA transmitter.
Transmitters involved in the separation conditions with TBA transmitters: These are the neighbours, co-site transmitters, transmitters or subcells of exceptional pairs and, in case of BSIC allocation, neighbours of neighbours.
The frequency plan audit automatically checks certain points and allows you to define additional points to be verified. The
points which are automatically verified are:
458
AT332_UMR_E0
Subcell parameters respect the cell type on which the subcell is based.
TRX parameters respect the TRX type on which the TRX is based.
No frequency, HSN, or BSIC domain is empty.
For subcells where the hopping mode is NH or BBH, each TRX has a single, unique frequency.
For subcells where the hopping mode is SSH, each TRX has a defined frequency list.
For subcells where the hopping mode is SSH, the maximum MAL length is respected.
For subcells where the hopping mode is SSH, the MAIO is lower than the number of frequencies in the MAL.
The number of timeslots per subcell is lower than or equal to the multiplexing factor (or, for the BCCH subcell, the
number of timeslots equals the multiplexing factor minus one).
The number of timeslots per subcell is 0.
The non-existence of multi-band transmitters when these are not expected to be present.
In multi-RAT networks, detection of UMTS inter-technology neighbour transmitters with identical scrambling codes.
In multi-RAT networks, detection of LTE inter-technology neighbours with identical physical cell IDs.
You can configure the frequency plan audit to verify the following points as well:
Load all the subcells involved in separation constraints: Select this check box if you want all transmitters
involved in separation constraints to be considered in the audit. You can review and modify separation
constraints and exceptional pairs on the Separation tab of the dialog box (see step 5.).
Load all interferers propagating in the focus zone: Select this check box if you want all potential interferers
to be considered in the audit.Check this box to load all the potential servers potentially involved in interferences with servers to be normally taken into account through the computation zone.
b. Under Optional Checking, select the check boxes of the domain constraints you want to have verified by the audit:
Frequencies: Select this check box if you want the audit to verify that the current frequency plan respects the
assigned frequency domains.
HSN: Select this check box if you want the audit to verify that the assigned HSNs belong to the assigned HSN
domains.
Compliance with the Allocation Strategy: Select this check box if you want the audit to verify that the current
frequency plan respects the assigned allocation strategy (free or group-constrained).
BSIC: Select this check box if you want the audit to verify that the assigned BSICs belong to the assigned BSIC
domains.
c. Select the Separation Constraints check box if you want the audit to verify that the currently defined separation
constraints are respected. You can review and modify separation constraints and exceptional pairs on the Separation tab of this dialog box (see step 5.). When the Separation Constraints check box is not cleared, you can select an AFP module next to Violations Importance and click the Browse button to display its Properties dialog box.
d. Select the (BSIC, BCCH) pairs check box if you want the audit to verify the following:
That no transmitter has the same BSIC-BCCH pair as one of its neighbours.
That no transmitter has two neighbours with the same BSIC-BCCH pair.
5. Click the Separations tab if you want to define/modify separation constraints and exceptional separation constraints:
a. Click the Exceptional Pairs button to open the Exceptional Separation Constraints dialog box and define exceptional frequency separations to define channel separations that apply to specific pairs of TRXs. During automatic
frequency planning, the separation rules are first considered, but they can be overridden by specific entries in the
459
Exceptional Separation Constraints table. For information on defining exceptional separation constraints, see
"Defining Exceptional Frequency Separations" on page 363.
b. When you have finished entering exceptional separation constraints, click Close to close the Exceptional Separation Constraints dialog box.
c. In the table on the Separations tab, enter or modify the separation rules. The separation rules set the channel separation that should exist between pairs of TRXs on the same transmitter, same site, or on adjacent sites. For information on defining separation rules, see "Defining Separation Rules" on page 363.
6. Click the Detailed Results tab to select the type of information you want in the report.
Error Messages: If you select this check box, the audit displays global warnings and error messages, as well as a
summary of separation constraint violations by transmitter/subcell/TRX pair and by TRX.
Warnings Related to Separations: If you select this check box, the audit displays a description of each separation
constraint violation.
Additional Warnings: If you select this check box, the audit displays additional detailed warnings.
Postpone the Global Summary and Part of the Tests: You can select this check box for faster display of the results.
The audit results will be displayed immediately and you can generate the global summary at that point.
7. Click OK to start the audit. The Checking Planning Consistency dialog box appears (see Figure 7.93). The results are
given in a grid under Separation Violations. Under Messages are the detailed results as defined in step 6.
You can define the display of the Allocation tab from the Display Options menu. For more information, see "Defining
the Display of the Allocation Tab" on page 382.
If you had selected to Postpone the Global Summary and Part of the Tests in step 6., the Messages area will be empty.
You can generate global summary now by clicking the Actions button and selecting Generate the Global Summary.
460
AT332_UMR_E0
Click Yes if you want to define the pair currently in violation as an exceptional pair. Because separation constraints
between exceptional pairs have more weight than default separation constraints, you will be able to re-run the
AFP and force it to try to avoid this violation.
Or click No to close the message box without defining the pair currently in violation as an exceptional pair.
The number of TRXs in the Transmitters table corresponds to the number of TRXs defined for this transmitter in the
TRXs table.
The list of channels used by the transmitter consists of all the channels assigned to TRXs of the transmitter.
The BCCH of the transmitter is the same as the channel assigned to the BCCH TRX of the transmitter.
The number of required TRXs indicated in the Transmitters table equals the sum of required TRXs of the transmitters
subcells.
The hopping mode of the transmitter corresponds to the hopping mode defined for its TCH subcell.
For each subcell, Atoll checks the following values: number of required TRXs, number of required BCCHs, traffic load, reception threshold, min C/I, half-rate traffic ratio, mean power control gain, DL power reduction, AFP weight, target rate of traffic
overflow, max percentage of interference, maximum MAL length.
To make a subcell audit:
1. Select the Network explorer.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Subcells > Audit from the context menu. The Subcell Audit dialog box appears.
4. Under Consistency of redundant values in the transmitters, subcells, and TRXs tables, select the Audit the values
and generate a report in the event viewer check box. Problems found during the audit will be displayed in the Events
viewer and grouped by transmitter.
5. If you want Atoll to update the transmitter parameters that are inconsistent with their subcells and TRXs, select the
Fix inconsistencies between transmitters and their subcells check box.
6. Under Compatibility of the main subcell values, select the Audit the values and generate a report in the event viewer
check box. Warnings will be displayed in the Events viewer for inconsistent values:
7. If you want Atoll to fix the subcell values as follows, select the Fix incompatibilities found in the main values check
box.
461
8. Click OK.
If you choose to fix the incompatible values, Atoll displays the report in the Events viewer. Values that are inconsistent are
changed and Atoll displays warnings to inform you of unrealistic values.
Used as BCCH: Atoll will search for the channel when used as a BCCH.
Used as TCH: Atoll will search for the channel when used as a TCH.
By default, Find on Map displays only co-channel subcells. If you want adjacent channels to be displayed as well, select
the Adjacent channels check box.
5. Click Search.
When you search for both BCCH and TCH TRX types, transmitters with the same channel for BCCH are displayed in red.
Transmitters with the same channel for any TCH are displayed in orange. Transmitters with two adjacent channels
(i.e., a channel higher and a channel lower) are displayed in yellow. Transmitters with a lower adjacent channel are
displayed in green; transmitters with a higher adjacent channel are displayed in green. Colours used for co-channel
cases take precedence over the colours used for adjacent channels. All other transmitters are displayed as grey lines.
When you search for the BCCH or TCH TRX types, transmitters with the same channel are displayed in red. Transmitters with two adjacent channels (i.e., a channel higher and a channel lower) are displayed in yellow. Transmitters with
a lower adjacent channel are displayed in green; transmitters with a higher adjacent channel are displayed in green.
Colours used for co-channel take precedence over the colours used for adjacent channels. All other transmitters are
displayed as grey lines.
If you cleared the Adjacent channels check box, transmitters using the same channel are displayed in red; all others,
including transmitters with adjacent channels, are displayed as grey lines.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
462
AT332_UMR_E0
BCCH channel: Enter a BCCH channel number. If you do not enter a BCCH channel number, Atoll will search all
specified channels according to the other parameters.
BSIC or NCC-BCC: Enter either a BSIC or a value for the NCC and for the BCC.
4. Click Search.
Transmitters that match the defined search parameters are displayed in red. All other transmitters are displayed as
grey lines.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
To find a BCCH or TCH channel or a combination of channel (BCCH or TCH) and HSN or MAIO:
1. Click Tools > Find on Map. The Find on Map window appears.
2. From the Find list, select "Channel-HSN/MAIO Pair."
3. From the Channel list, select a BCCH or TCH channel number and the parameter on which you want to search:
HSN: to search for a combination of channel number and HSN, select HSN and an HSN number.
MAIO: to search for a combination of channel number and MAIO, select MAIO and a MAIO number.
The Find on Map tool can also return results for a specific HSN or MAIO when the Channel
field is empty. In this case, the Results window will list all the transmitters for which the
specified HSN or MAIO was defined.
4. Click Search.
Transmitters that match the defined search parameters are displayed in red. All other transmitters are displayed as
grey lines.
To restore the initial transmitter colours, click the Reset Display button in the Find on Map window.
BCCH: To display the BCCH of a transmitter, select "Discrete values" as the Display Type and "BCCH" as the Field.
BSIC: To display the BSIC of a transmitter, select "Discrete values" as the Display Type and "BSIC" as the Field.
You can display the following information in the transmitter label or tip text:
BCCH: To display the BCCH of a transmitters subcells, select "BCCH" from the Label or Tip Text Field Definition
dialog box.
BSIC: To display the BSIC of a transmitter, select "BSIC" from the Label or Tip Text Field Definition dialog box.
Channels: To display the channels allocated to a transmitter, select "Channels" from the Label or Tip Text Field
Definition dialog box.
HSN: To display the HSN allocated to a transmitters subcells, select "HSN" from the Label or Tip Text Field Definition dialog box.
MAIO: To display the MAIO allocated to a transmitters subcells, select "MAIO" from the Label or Tip Text Field
Definition dialog box.
Cell type: To display the cell type allocated to a transmitter, select "Cell type" from the Label or Tip Text Field Definition dialog box.
463
Required TRXs per Transmitter or Subcell: To display the number of required TRXs per transmitter or per subcell,
select "Required TRXs" or "Subcell: Required TRXs," respectively, from the Label or Tip Text Field Definition dialog
box.
Number of TRXs Assigned: To display the number of TRXs assigned to a transmitter, select "Number of TRXs" from
the Label or Tip Text Field Definition dialog box.
Frequency Band: To display the frequency band assigned to a transmitter, select "Frequency Band" from the Label
or Tip Text Field Definition dialog box.
GPRS/EDGE: To display which transmitters are GPRS/EDGE-capable, select "GPRS/EDGE" from the Label or Tip
Text Field Definition dialog box.
Coding Scheme Configuration: To display the coding scheme configuration assigned to a transmitter, select
"Coding Scheme Configuration" from the Label or Tip Text Field Definition dialog box.
Codec Configuration: To display the codec configuration assigned to a transmitter, select "Codec Configuration"
from the Label or Tip Text Field Definition dialog box.
Because labels are always displayed, you should avoid displaying too much information at
the same time.
5. Click OK.
For information on display options, see "Setting the Display Properties of Objects" on page 51.
Frequency band
Channels
6. Click
to add the parameter to the Group these fields in this order list. The selected parameter is added to the list
of parameters on which the transmitters will be grouped.
7. If you do not want the transmitters to be sorted by a certain parameter, select it in the Group these fields in this order
list and click
grouped.
. The selected parameter is removed from the list of parameters on which the transmitters will be
8. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters to
be grouped:
a. Select a parameter and click
9. Click OK to save your changes and close the Group dialog box.
The load is the same as the number of TRXs if synthesised hopping is not used. When synthesised hopping is used, the
frequency load is the sum of 1/(MAL length) of all the TRXs using this frequency.
The scope of this tool is the same as the scope of the AFP. For more information on the AFP scope, see "The Scope of the AFP
and the Scope of the Interference Matrix" on page 372.
464
AT332_UMR_E0
The frequency load distribution can be displayed as a histogram by clicking the Histogram button. The histogram is similar to
the one on the Histogram tab in the AFP Progress dialog box. For more information, see "Histogram Tab" on page 386.
The Relationship Between Uniform Distribution and Quality
You should be aware that uniform distribution is not always synonymous with quality. While it is clear that in some cases the
frequency usage distribution can be a quality indicator, it is not always the case. For this reason the Atoll AFP does not have
a cost dedicated to non-uniformity of spectral use. Therefore Atoll AFP can create non-uniform frequency distributions.
When the frequency assignment problem (FAP) is easy, the AFP reaches a 0-cost solution and stops immediately. If it
was instructed to use the minimum spectrum possible, the AFP will use the smaller ARFCNs more than the larger ones
(and will leave the largest ARFCNs untouched, for future use). Otherwise, the AFP will try to spread spectrum use. By
default this directive is free for AFP tuning.
In many cases, a large volume of allocation constraints exists for adjacent channel reuse. The two end-channels, (the
biggest and the smallest in the domain), have fewer constraints, because they have only one adjacent channel in use,
and are therefore heavily used. The adjacent channels (the second in the domain, and the one before the biggest in
the domain) are used less often than the others because they each have a heavily used adjacent channel. Because the
third domain frequency is adjacent to a seldom used channel, it will be used more often than usual. In the case of a
continuous domain, which is small, and whose size is impair, this effect will resonate strongly and will provide a significant reduction in usage of the 2nd, 4th, 6th, etc., frequencies of the domain.
After you have manually or automatically allocated frequencies, you can view channel allocation in the form of a table or a
histogram. For each channel used, Atoll displays both the channel load (i.e., the number of times the channel is used, weighted
by the fractional load) and the total number of times the channel is used. The information in the table can either be copied or
exported for use in another application.
To display the channel allocation table or histogram:
1. Select the Network explorer.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Frequency Plan > Channel Distribution. The Channel Use Statistics table appears.
4. You can do the following:
Export: Click the Export button to open the Export dialog box and export the Channel Use Statistics table contents
as a TXT, CSV, or XLS file. For information on using the Export dialog box, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
Histogram: Click the Histogram button to display the Distribution Histogram dialog box. The histogram represents
the channels as a function of the frequency of their use. You can move the pointer over the histogram to display
the frequency of use of each channel. The results are highlighted simultaneously in the Zoom on selected values
list. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on
the selected values.
In the Distribution Histogram dialog box, you have the following options:
Copy: Click the Copy button to copy the histogram to the clipboard. You can paste the histogram as a graphic
into another application, for example, a word-processor.
Print: Click the Print button to print the histogram.
If you select From subcell table, define the following additional parameters:
Specify the Minimum throughput reduction factor that can be accepted in the network. When running a traffic capture, this parameter is evaluated (but not displayed) during the calculation. The minimum throughput
reduction factor models the fact that, at the user level, the user throughput can be reduced because of how
465
much it will be multiplexed with other users. In other words, this parameter will be affected by the traffic load
which is a consequence of dimensioning.
Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages
must equal 100.
Under Circuit Services (%), enter the percentage of each type of circuit service used in the map. The total
percentages must equal 100.
Under Packet Services (%), enter the percentage of each type of packet service used in the map (assuming the
packet is made of maximum bit rate and constant bit rate packet services). The total percentages must equal
100.
TRX Type: For each transmitter, the results are given by TRX type (e.g., BCCH, TCH, TCH_EGPRS and TCH_INNER).
Together, the Transmitter and TRX Type columns identify the subcell.
Number of TRXs: The number of TRXs assigned for both the subcell's circuit-switched and packet-switched traffic,
while taking into account the quality of service criterion assigned for each.
Load (%): The average demand in timeslots (packet and circuit), divided by the total number of timeslots available.
It represents the average occupancy of the TRXs. This parameter is one of the principal results of dimensioning
along with the number of TRXs. In addition, this parameter might have been updated by an AFP model which is
capable of optimising (i.e., reduce or increase) the number of required TRXs. This results in the subcell load being
modified.
Multiplexing Factor: The user or Temporary Block Flow (TBF) multiplexing factor. The multiplexing factor corresponds to the number of timeslots per frame.
Maximum Number of TRXs per Transmitter: The maximum number of TRXs that a transmitter can support is an
input of the KPI calculation. This parameter is provided by the equipment manufacturer. The value can be set for
each transmitter or taken from the dimensioning model for transmitters where this value is not set.
Target Rate of Traffic Overflow (%): This input parameter defines the percentage of traffic that is allowed to overflow from one subcell to another in case the traffic assigned to this subcell is greater than the maximum traffic
that it can accommodate. It can be considered an anticipation of the percentage of traffic that will be rejected
from higher priority subcells or layers to lower ones. The value is specified for each subcell.
Half-rate Traffic Ratio (%): This input parameter is defined per subcell and indicates the percentage of subcell
traffic that uses half-rate access.
If the values are different for BCCH and TCH subcells, Atoll will use the values for the target rate of traffic overflow
and the half-rate traffic ratio from the BCCH subcell.
Packet demand (Kbps): The Packet Traffic Demand is the total traffic demand in kilobits per second generated by
packet-switched service users within the coverage area of the transmitter.
Packet average demand (timeslots): The number of timeslots needed to satisfy the packet traffic demand
depends on the maximum throughput that a packet timeslot can support.
Average Number of Timeslots per Connection (Packet): This input parameter defines the average number of
timeslots used by packet-switched-traffic users while accessing services. Packet-switched services allow up to
eight timeslots per connection. The average number of timeslots per connection corresponds to the average
number of downlink timeslots (multiplied by the number of simultaneous carriers in EDGE Evolution, if any) over
which a single mobile terminal can communicate at one time.
Circuit Demand (Erlangs): The Circuit Traffic Demand is the total traffic demand in Erlangs generated by circuitswitched-service users within the coverage area of the transmitter.
For concentric cell types, the traffic demand on TCH subcells is different from the one
calculated during the traffic capture. For concentric cell types, the traffic demand on TCH
subcells is calculated from the traffic demand of the capture and the effective rate of traffic
overflow.
Circuit average demand (timeslots): The Average Demand in Circuit Timeslots is calculated taking into account
the effect of half-rate circuit-switched traffic: two half-rate users are equivalent to one full-rate user.
Average Number of Timeslots per Connection (Circuit): The Average Number of Timeslots per Connection (Circuit) is an input parameter. The number of timeslots per connection is "1" for full-rate traffic, otherwise it depends
on the half-rate traffic ratio.
At present, Atoll only models circuit calls using 1 timeslot per connection; this parameter is for forward compatibility.
466
AT332_UMR_E0
Served Circuit Traffic (Erlangs): The Served Circuit Traffic is the circuit-switched traffic in Erlangs that the subcell
can serve.
The served circuit-switched traffic is circuit traffic demand less the effective overflowed circuit traffic.
Served Packet Traffic (Kbps): The Served Packet Traffic is the packet-switched traffic in kilobits per second that
the subcell can serve.
The served packet-switched traffic is packet traffic demand less the effective overflowed packet traffic.
Effective Rate of Traffic Overflow (%): The Effective Rate of Traffic Overflow is the actual rate of traffic that is
rejected by the subcell and overflows because of a lack of packet timeslots. In a GSM network, the value is the
same as the blocking probability. In a more complex network, this value includes the traffic overflow from all services.
In case of Erlang B, the effective rate of traffic overflow corresponds to the effective blocking rate. This value is
calculated from the required number of circuit timeslots (both shared and circuit timeslots) and the circuit traffic
demand in Erlang B tables.
In case of Erlang C, the effective rate of traffic overflow is zero except if the maximum number of TRXs is exceeded.
The effective blocking rate is inferred from the required number of circuit timeslots (both shared and circuit timeslots) and the circuit traffic demand in Erlang C tables.
Probability of Circuit Blocking Rate (or Delay) (%): The Circuit Blocking Rate is the grade of service (GoS) indicator
for circuit-switched traffic. It can be either the rate at which calls are blocked (Erlang B) or delayed (Erlang C),
depending on which queuing model the dimensioning model uses.
Minimum Throughput Reduction Factor (%): The Minimum Throughput Reduction Factor is the lowest
throughput reduction factor that can still guarantee service availability. The Minimum Throughput Reduction
Factor is one of the criteria for packet-switched traffic dimensioning. It is calculated using the parameters defined
for the services: the minimum service throughput; the maximum number of timeslots per connection; the
required availability; and the per pixel timeslot capacity of the subcell coverage area. This parameter is calculated
when making the traffic capture or is user-defined depending on the source of traffic demand on which the KPI
calculation is based.
Throughput Reduction Factor (%): The Throughput Reduction Factor is calculated from the quality charts using
the packet load and available connections for each subcell. This reduction factor must be greater than the minimum throughput reduction factor for packet-switched services for these services to be satisfactorily available in
the subcell.
Maximum Packet Delay (s): The Maximum Packet Delay is the defined delay in seconds that must not be
exceeded for the service quality to be considered satisfactory.
Packet Delay (s): The Delay is a key performance indicator (KPI) calculated using the quality graphs, the load, and
the number of connections available. This dimensioning output must not exceed the maximum delay defined for
the service for service availability to be considered satisfactory.
Maximum Probability of Packet Delay (%): The Maximum Probability of Packet Delay is defined for each packet
service and is the highest probability that the service will be blocked that is acceptable in terms of service availability.
Probability of Packet Delay (Delay) (%): The Probability of Packet Delay is a dimensioning output and must not
exceed the Maximum Probability of Packet Delay defined for the service for service availability to be considered
satisfactory.
5. Click Commit to assign the load and the effective rate of traffic overflow to the subcells.
KPI calculation is based on a traffic capture. Modifications to traffic maps, traffic parameters, and transmitter properties (e.g., calculation area, coding scheme configuration, etc.)
have an influence on the traffic capture. Therefore, if you modify some of these data, you
must recalculate the traffic capture before calculating KPIs.
467
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.
ACP uses user-defined objectives to evaluate the optimisation, as well as to calculate its implementation cost. Once you have
defined the objectives and the network parameters to be optimised, ACP uses an efficient global search algorithm to test
many network configurations and propose the reconfigurations that best meet the objectives. ACP presents the changes
ordered from the most to the least beneficial, allowing phased implementation or implementation of just a subset of the
suggested changes.
ACP is technology-independent and can be used to optimise networks using different radio access technologies. Chapter 17:
Automatic Cell Planning explains how you configure the ACP module, how you create and run an optimisation setup, and how
you can view the results of an optimisation. In this section, only the concepts specific to GSM networks are explained:
GSM Coverage
GSM Cell Dominance
You can also create the following objectives from the context menu of Objectives in the left-hand pane of the Objectives tab:
You define the optimisation objectives using the Objectives tab of the ACP Setup dialog box. For information on setting objective parameters, see "Setting Objective Parameters" on page 1329.
468
AT332_UMR_E0
If you base the evaluation of a qualiy analysis prediction on a calculated Atoll prediction, ACP will use the display settings of the calculated Atoll prediction in the
qualiy analysis prediction calculated for that objective.
If you saved the display settings of a qualiy analysis prediction as defaults, or if you
are using a configuration file for ACP, these display settings will be used by default
and will override the display settings of the calculated Atoll prediction. For more
information on changing the display settings of a quality analysis prediction, see
"Changing the Display Properties of ACP Predictions" on page 1379.
CINR Co-channel
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by C/I level.
Base prediction settings on > "Coverage by C/I Level (DL)": ACP will evaluate coverage by C/I level based on the
parameters used to calculate the selected "Coverage by C/I Level (DL)" prediction in Atoll.
Base prediction settings on > "Manual configuration": If you select this option, you can Enable shadowing margin
and define a 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.
Base prediction settings on > "Coverage by Signal Level (DL)": ACP will evaluate the coverage by signal level based
on the parameters used to calculate the selected "Coverage by Signal Level (DL)" prediction in Atoll.
Base prediction settings on > "Manual configuration": If you select this option, you can Enable shadowing margin
and define a 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.
Overlap / 1st-Nth to define in the right-hand pane how ACP will evaluate overlapping coverage and coverage by 1stNth difference.
Overlap
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by overlapping zones or by
1st-Nth difference.
Base prediction settings on > "Overlapping Zones (DL)": ACP will evaluate coverages by overlapping based on
the parameters used to calculate the selected "Overlapping Zones (DL)" prediction in Atoll.
Only the Atoll predictions displaying a "Number of Servers" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": If you select this option, set the Minimum signal level
to "Subcell C Threshold" (reception threshold defined per subcell) or "Global C Threshold" and specify the
Overlap threshold margin to be used for all subcells.
1st-Nth
Base prediction settings on > "Overlapping Zones (DL)": ACP will evaluate coverages by 1st-Nth difference
based on the parameters used to calculate the selected "Overlapping Zones (DL)" prediction in Atoll.
Since there is no Atoll prediction type equivalent to ACPs GSM 1st-Nth Difference objective, the parameters
recovered by ACP from the selected Atoll prediction are limited to the minimum signal level and the shading.
The number of servers must always be specified manually next to No. servers.
Base prediction settings on > "Manual configuration": If you select this option, set the Minimum signal level
to "Subcell C Threshold" or "Global C Threshold" and specify the No. serversthreshold margin to be used for
all subcells.
In both cases, the value you specify next to No. servers determines "Nth" in the GSM 1st-Nth Difference objective. For instance if you set No. servers to 4, then the "1st-4th Difference" quality parameter will be auto-
469
matically selected by default in the Quality column of the GSM 1st-Nth Difference properties page.
- Allowed values for No. servers range from 3 to 100, with only one value available per technology.
- The "1st-2nd Difference" quality parameter (based on No. servers = 2) is provided by default.
Figure 7.95: ACP Quality Analysis Prediction Types for a GSM Network
ACP quality analysis predictions are equivalent to some of Atolls coverage predictions. The following table lists the quality
analysis predictions available in ACP for GSM and the equivalent GSM coverage predictions in Atoll.
Overlap
CINR Co-channel
1st-Nth Difference
N/A
(1) For more information, see "Making a Coverage Prediction by DL Signal Level" on page 308.
(2) For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 313.
(3) For more information, see "Making DL Quality Predic
Making these predictions 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 predictions 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 predictions produced by ACP, you should keep the following
recommendations in mind:
470
You should verify the results with a different Atoll coverage prediction, such as the interfered zones prediction.
ACP generated predictions are generated using the entire set of proposed changes. They do not take into account the
change subset defined on the Change Details tab.
The predictions are only provided for the used or requested carrier (GSM900, GSM1800, etc.) separately.
Even after committing the optimisation results, small differences can appear between ACP predictions and the predictions resulting from Atoll coverage predictions.
AT332_UMR_E0
You can view the exact BCCH value on any pixel by letting the pointer rest over the pixel. The BCCH value is then displayed in
tip text.
For ACP overlapping zones predictions, you can:
For each network quality coverage prediction, ACP offers a prediction showing the initial network state, the final network
state, and a prediction showing the changes between the initial and final state.
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 subcells, neighbour subcells, or any other subcells). Transmitters may be identified by their IDs or their BCCH and BSIC.
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:
1. Select the Network explorer.
2. Right-click the Drive Test Data folder. The context menu appears.
3. Select Import from the context menu. The Open dialog box 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 dialog box appears.
471
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 dialog box.
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 dialog box. 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 dialog box, 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,
472
AT332_UMR_E0
Figure 7.96: The Setup tab of the Import of Measurement Files dialog box
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 dialog box 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.
ii. In the By ID identifier box, enter a string found in the column name that identifies the cell Ids of scanned transmitters. For example, if the string "Cell_ID" is found in the column names that identify the Cell_ID of scanned
transmitters, enter it here. Atoll will then search for the column with this string in the column name.
e. If you are importing data using BSIC and BCCH as transmitter identifiers:
i.
ii. In the BSIC identifier box, enter a string that is found in the column names identifying the BSICs of the scanned
subcells. For example, if the string "BSIC" is found in the column names identifying the BSIC of the scanned
subcells, enter it here. Atoll will then search for columns with this string in the column name.
iii. In the BCCH identifier box, enter a string that is found in the column names identifying the BCCH of the
scanned subcells. For example, if the string "BCCH" is found in the column names identifying the BCCH of
scanned subcells, enter it here. Atoll will then search for columns with this string in the column name.
If there is no BCCH information contained in the drive test data file, leave the BCCH identifier box empty.
iv. In the BSIC format list, select the scrambling code format, "Decimal" or "Octal."
f.
473
If you have correctly entered the information under File on the Setup tab, and the
necessary values in the Drive Test Data Setup dialog box, Atoll should recognise 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 BCCH
and the BSIC are placed before the data columns for each subcell. 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 dialog box 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 Import 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 dialog box.
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 is imported into the current Atoll document.
474
AT332_UMR_E0
3. Right-click the drive test data path whose display you want to define. The context menu appears.
4. Select Properties from the context menu.
5. Click the Display tab.
Each single point can be displayed by a unique attribute, or according to:
In addition, a last option is available which permits to display points according to more than one criterion at a time. By selecting Advanced Display from the Display Type, a dialog box opens in which you can define the following display for each single
point of the measurement path:
With such settings, you can, for example, display a signal level by colour, choose a symbol type for Transmitter 1 (circle, triangle, cross, etc.) and a size according to the altitude.
Fast Display forces Atoll to use the lightest symbol to display points. Fast Display
is useful when you have a very large amount of points which would require a great
amount of computer resources to display.
Using Advanced Display on symbols is possible only if the Fast Display check box
is cleared.
You can sort drive test data paths in alphabetical order in the Network explorer by
selecting Sort Alphabetically from the Drive Test Data 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 dialog box and select Save or Load from
the Display Configuration submenu.
"Filtering Measurement Points Along Drive Test Data Paths" on page 475
"Predicting the Signal Level on Drive Test Data Points" on page 477
"Creating Coverage Predictions on Drive Test Data Paths" on page 478
"Displaying Statistics Over a Drive Test Data Path" on page 480
"Extracting a Field From a Drive Test Data Path for a Transmitter" on page 480
"Analysing Data Variations Along the Path" on page 480.
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. The context
menu appears.
3. Select Filter from the context menu. The CW Measurement Filter dialog box appears.
475
4. In the Per Clutter 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 that are 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:
1. Select the Network explorer.
2. 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. The context
menu appears.
3. Select Filter from the context menu. The CW Measurement Filter dialog box appears.
4. Click More. The Filter dialog box appears.
5. Click the Filter tab:
6. Select a Field from the list.
7. 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.
8. Click the Advanced tab:
9. 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 7.97).
476
Underneath each column name, enter the criteria on which the column will be filtered as explained in the following table:
Formula
=X
<> X
<X
>X
<=X
>=X
*X*
*X
AT332_UMR_E0
Formula
X*
ii. Click OK to filter the data according to the criteria you have defined.
Combinations of filters are first made horizontally, then vertically. For more information on filters, see "Advanced Data Filtering" on page 101.
iii. Click OK to apply the filter and close the dialog box.
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.
Figure 7.99: Selecting measured signal levels for which errors will be calculated
7. Click OK. A new point prediction is created for the selected drive test data path.
8. Right-click the drive test data path. The context menu appears.
9. Select Calculations > Calculate All the Predictions from the context menu.
477
If you chose to have Atoll calculate the errors between measured and predicted signal levels, new columns are added to the
drive test data table for the predicted point signal level from the serving cell and the errors between the measured and
predicted values.
Figure 7.100: Drive Test Data Table after Point Signal Level Prediction (with Error Calculations)
New columns are also added for the predicted point signal level from each neighbour cell and the errors between the
predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For
more information on the Drive Test Data analysis tool, see "Analysing Data Variations Along the Path" on page 480.
The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main
matrix. For more information on propagation models, see Chapter 4: Radio Calculations and Models.
At the top of the Conditions tab, you can set the range of signal level to be considered. You can click the down
arrow button and select one of the following thresholds:
Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power
reduction) as the lower end of the signal level range.
Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range.
478
On the Conditions tab, you can define the signals that will be considered for each pixel. You can click the down
arrow button and select one of the following thresholds:
Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power
reduction) as the lower end of the signal level range.
Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range.
Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer
level or specifically for each transmitter. When you select "Best Signal Level per HCS Layer" or "All," there
might be areas where several transmitters experience interference. On these pixels, several CI values are
calculated. Therefore, on the Display tab, you select to display either the lowest CI level or the highest CI
level (for more information, see "Comparing Service Areas in Calculations" on page 484).
Enter an Overlap margin. The default value is "4 dB."
AT332_UMR_E0
If you select Shadowing Taken into Account, you can change the Cell Edge Coverage Probability. Shadowing
margins (depending on the entered cell edge coverage probability and the model standard deviation per clutter class) are applied to the values for C. For more information, see "Modelling Shadowing" on page 506.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency
per clutter class.
Under Interference Conditions, you can select which TRX type to consider as potential victim by selecting it
from the Interfered Subcells list.
Select "CI" or "C(I+N)". On the same line, click the down arrow buttons on the left and on the right and select
one of the following thresholds:
Subcell C/I Threshold: to use the CI threshold specified for each subcell (including the defined power reduction) as the lower end of the CI range.
Global C/I Threshold: to enter a threshold to be used for all subcells as the lower end of the CI range.
You can not select Subcell C/I Threshold as both the lower and the upper end of the CI
range to be considered.
Select whether you want the defined interference condition to be Satisfied By:
At least one TRX: When you select this option, the defined interference condition must be satisfied by at least
one TRX on a given pixel for the results to be displayed on that pixel.
The worst TRX: When you select this option, Atoll selects the worst results for each pixel. If the worst results
do not satisfy the defined interference condition, the results will not be displayed on that pixel.
If you selected C/(I+N), you can define the value to be added to the interference. The defined noise figure is
added to the thermal noise value (defined at -121 dBm) to calculate the value of N. Select one of the following:
Based on Terminal: to use the noise figure defined for a terminal and select the terminal from the list.
Fixed Value: to enter a value and then enter the noise figure in the text box.
If you want discontinuous transmission mode for TRXs which support it taken into account during the calculation of interference, select the DTX taken into account check box and enter the percentage of time during
which a user is talking in the Voice Activity Factor text box.
Select the Traffic Load that will be used to calculate interference:
100%: The maximum traffic load (subcells entirely loaded).
From subcell table: The subcell traffic load as defined or as calculated during dimensioning.
From the Interference Sources list, select whether the interference should be calculated from adjacent channels, co-channels, or from both. The adjacent channel effect on the victim channel, i.e., the interference, is
decreased by the adjacent channel protection level.
Inter-technology interference is taken into account by default. For more information, see
"Modelling Inter-technology Interference" on page 624. By adding an option in the Atoll.ini
file, you can add an Inter-technology check box which will allow you to consider or not
inter-technology interference.
Select the Detailed Results check box if you want to display detailed results per transmitter. The results
displayed depend on the subcell frequency hopping mode:
Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping mode.
Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in synthesised frequency hopping mode.
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
context menu appears.
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 4: Radio Calculations and
Models).
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 480.
479
7.8.4.5 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:
1. Select the Network explorer.
2. Click the Expand button ( ) to expand the Drive Test Data folder.
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 Selection for a Given Transmitter dialog box 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 transmitters.
Atoll can display the seven servers per point. 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 data table for the selected transmitters and with the
selected values.
480
AT332_UMR_E0
Select the check box next to any field you want to display in the Drive Test Data window.
If you wish, 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 dialog box.
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.
481
6. You can display the data in the drive test data path in two ways:
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 on page 481). 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 "Setting the Display Type" on page 52.
7. 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 dialog box. 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 dialog box.
8. 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 on one end of the range of data you want to zoom in on.
482
AT332_UMR_E0
483
Priority
Layer reception threshold
Maximum speed.
The priority and layer reception threshold are used to determine the best server on each pixel. When there are several possible transmitters, the best server will be determined by the priority. If there are transmitters on different layers having the
same priority, the transmitter for which the difference between the received signal level and the layer reception threshold
will be selected as the best server. Transmitters whose received signal level is below the layer reception threshold will be
ranked by signal level, but will not be chosen as best server. The HCS layer reception threshold is considered only if no specific
HCS layer reception threshold has been defined at the transmitter level (on the General tab of the transmitters Properties
dialog box).
You can set Atoll to select the transmitter with the highest received signal level as the serving transmitter by changing an option in the Atoll.ini file. For more information on changing
options in the Atoll.ini file, see the Administrator Manual.
The maximum speed is used to select HCS layer users according to the speed defined in the mobility.
To define HCS layers:
1. Select the Parameters explorer.
2. Click the Expand button ( ) to expand the GSM Network Settings folder.
3. Right-click the HCS Layers folder. The context menu appears.
4. Select Open Table. The HCS Layers table appears.
5. In the row marked with the New Row icon (
), enter the following parameters to define a HCS layer (for information
on working with data tables, see "Data Tables" on page 75):
Name: Enter a name for the HCS layer. This name will appear in other dialog boxes when you select a HCS layer.
Priority: Enter a priority for the HCS layer. "0" is the lowest priority.
Max. Speed (km/h): Enter a maximum mobility speed for the HCS layer.
Layer Reception Threshold (dBm): Enter a default layer reception threshold in dBm. This threshold can be used
as a border for the HCS layer in some predictions when the HCS server option is selected.
484
AT332_UMR_E0
Highest Priority HCS Server: The best signal level of all the severs on the highest priority HCS layer will be taken into
consideration, assuming the priority of the layer is defined by its priority field and its signal level exceeds the minimum
HCS threshold defined either at the HCS layer level or specifically for each transmitter.
Best Idle Mode Reselection Criterion (C2): The best C2 from all servers will be taken into consideration.
A server is considered on a pixel if its calculated signal level exceeds the lower boundary of the signal level defined either globally on the Conditions tab of the coverage prediction or specifically for each subcell in coverage prediction, traffic analysis,
and interference matrix calculations.
Selecting the server to be taken into consideration retains one or several servers on each pixel, according to a combination of
HCS layer properties (layer priority, maximum speed allowed on the layer, layer admission threshold) and the calculated signal
level on each pixel.
Example of Service Areas
In this example, the following network is used:
The umbrella layer is defined to overlap the macro layer, which overlaps the micro layer.
The HCS layers are defined with the following characteristics:
Name
Priority (0:Lowest)
Macro Layer
100
-90
Micro Layer
10
-84
Umbrella Layer
300
-105
The subcell reception threshold is -102 dBm for the micro cells and -105 dBm for the macro and the umbrella cells. Three
mobility types are defined in this project: Pedestrian (3km/h), 50 km/h and 90 km/h
The resulting services areas are displayed in the following graphics for each selection.
Composite Coverage
Best Signal Level: The best signal level from all servers on all layers is taken into consideration.
485
Composite Coverage
Figure 7.104: Coverage by Transmitter (DL) for the Best Signal Level
Figure 7.104 shows the service areas of the transmitters having the best signal level on each pixel, without any layer taken
into consideration. Cells are in competition if their calculated signal level is higher than the subcell reception thresholds. Overlapping between transmitters and between HCS layers is not possible.
Best Signal Level per HCS Layer: The best signal level from all servers on each HCS layer is taken into consideration.
Composite Coverage
Figure 7.105: Coverage by Transmitter (DL) for the Best Signal Level per HCS Layer
Figure 7.105 shows the service areas of the transmitters having the best signal level on each pixel, for each HCS layer. Cells
are in competition per layer if their computed signal level is higher than its subcell reception thresholds. Overlapping between
HCS layers is possible, but overlapping between transmitters on a given HCS layer is not possible.
486
HCS Servers: The best signal level by HCS layer on each pixel is taken into consideration, assuming the signal level on
each layer exceeds the minimum HCS threshold defined either at the HCS layer level or specifically for each transmitter.
AT332_UMR_E0
Composite Coverage
Highest Priority HCS Server: The best signal level of all the severs on the highest priority HCS layer are taken into consideration, assuming the priority of the layer is defined by its priority field and its signal level exceeds the minimum
HCS threshold defined either at the HCS layer level or specifically for each transmitter.
Composite Coverage
Figure 7.107: Coverage by Transmitter (DL) for the Highest Priority HCS Server
487
Figure 7.107 shows the service areas of the transmitters having the best signal level on each pixel, on the highest priority HCS
layer. The priority HCS layer is the layer for which the priority value is the highest and for which the calculated signal level is
higher than its subcell reception thresholds and the HCS layer reception threshold. Overlapping between HCS layers and
between transmitters of a given HCS layer is not possible.
If two layers have the same priority, the traffic is served by the transmitter for which the
difference between the received signal strength and the HCS threshold is the highest. The
way competition is managed between layers with the same priority can be modified. For
more information, see the Administrator Manual.
If necessary, you can define additional TRX types by creating them in the GSM/GPRS/EDGE document template. The template
is located in the templates directory, within the Atoll install directory, and is called "GSM GPRS EDGE.mdb." For information
on the Atoll document template, see the Administrator Manual.
), enter the name of the new cell type. This name will appear in other
6. Select the row containing the cell type and click the Properties button (
erties dialog box appears.
In the cell types Properties dialog box, you can add and define the TRX types that will constitute the cell type.
7. Under TRX Types, in the row marked with the New Row icon (
), enter the following parameters to define a TRX
type (for information on working with data tables, see "Data Tables" on page 75):
488
AT332_UMR_E0
DTX Supported: If the TRX type supports DTX (Discontinuous Transmission) technology, select the DTX Supported
check box. Subcells supporting DTX can reduce interference they produce according to the defined voice activity
factor. This option has no impact on BCCH TRX type.
Timeslot Configuration: Select a timeslot configuration from the list. The timeslot configuration defines the distribution of circuit, packet and shared timeslots for the subcell, respecting the number of TRXs.
Half-Rate Traffic Ratio (%): Enter the percentage of half-rate voice traffic in for this TRX type. This value is used to
calculate the number of timeslots required to respond to the voice traffic demand.
The target rate of traffic overflow and the half-rate traffic ratio must be the same for
BCCH and TCH TRX types. If the values are different for BCCH and TCH TRX types, Atoll
will use the values for the target rate of traffic overflow and the half-rate traffic ratio
from the BCCH TRX type.
Target Rate of Traffic Overflow (%): Enter the target rate of traffic overflow. The target rate of traffic overflow is
used during traffic analysis to distribute the traffic between subcells and layers. The value is the percentage of candidate traffic overflowing to a subcell with a lower priority. It has an impact on the traffic capture between inner
and outer subcells, and between micro and macro layers. In other words, The target rate of traffic overflow can
be considered to an estimation of the allowed percentage of traffic rejected from subcells or layers of higher priority to subcells or layers of lower subcells (see Figure 7.5).
If the traffic overflow target is set to a value lower than the grade of service, it means that
the traffic rejected (according to the queuing model selected in the dimensioning model:
Erlang B or Erlang C) will be lost and will not overflow to other subcells.
Hopping Mode: Select the frequency hopping mode supported by this TRX type. The hopping mode can be either
"Base Band Hopping mode (BBH)" or "Synthesised Hopping mode (SFH)." If frequency hopping is not supported,
select "Non Hopping."
Allocation Strategy: Select the allocation strategy used during manual or automatic frequency planning. There are
two available allocation strategies:
Free: Any of the channels belonging to the frequency domain can be assigned to TRXs.
Group Constrained: Only channels belonging to a same frequency group in the frequency domain can be
assigned. You can use the Preferred Frequency Group to define the preferred group of frequencies when
using the AFP.
Max. MAL Length: Enter the maximum length of the mobile allocation list (MAL), in other words, the maximum
number of channels allocated to the TRXs of subcells based on this TRX type during automatic frequency planning
if the Hopping Mode is either SFH (Synthesised Frequency Hopping) or BBH (Base Band Hopping) and if the Allocation Strategy is Free.
HSN Domain: Select the HSN domain for this TRX type. Only hopping sequence numbers (HSN) belonging to the
selected HSN domain will be allocated to subcells during automatic or manual frequency planning. The HSNs are
allocated if the Hopping Mode is either SFH (Synthesised Frequency Hopping) or BBH (Base Band Hopping).
Lock HSN: If the HSN assigned to this TRX type is to be kept when a new AFP session is started, select the Lock HSN
check box.
The Lock HSN status can also be managed via the Network explorer from the context menu
of an individual transmitter or group of transmitters. For more information, see "AFP
Resource Status Management" on page 288.
AFP Weight: Enter an AFP weight. The AFP weight is used to increase or decrease the importance of a subcell
during automatic frequency planning. The value must be a real number. The higher the AFP weight is, the higher
the constraint on the TRX type. The AFP weight artificially multiplies the cost function which has to be minimised
by the AFP.
% Max. Interference: Enter the maximum level of interference allowable during automatic frequency planning.
The interference is defined as a percentage of area or traffic, as defined during the calculation of the interference
matrices.
Mean Power Control Gain (dB): The average reduction in interference due to power control in downlink. This gain
is used when calculating interference generated by the subcell. Interference generated by the subcell is reduced
by this value during C/I calculations.
Default TRX Configuration: Select the default TRX configuration for this TRX type. It will apply to all TRXs belonging
to a subcell based on this TRX type. By selecting the default TRX configuration, the maximum number of GPRS and
EDGE coding schemes is set at the TRX type level. You can also define the TRX configuration for each TRX.
EDGE Power Backoff (dB): Enter the average power reduction for EDGE transmitters due to 8PSK, 16QAM and
32QAM modulations in EDGE. This has an impact on the EDGE service zone which can be seen in traffic analysis
and EDGE predictions.
489
Diversity Mode: The type of diversity supported by the subcell ("None," "Tx Diversity," or "Antenna Hopping"). If
you select "Tx Diversity," the signal is transmitted as many times as there are antennas. If you select "Antenna
Hopping," the signal is transmitted successively on each antenna. In "Tx Diversity mode," transmitting on more
than one antenna, the signal experiences a gain of 3 dB. For any diversity mode, an additional transmission diversity gain can be defined per clutter class in order to correctly model gain due to the environment (see "Defining
Clutter Class Properties" on page 127 for more information). The resulting gain will increase the C/I value at the
terminal served by the considered subcell.
An Other Properties tab appears on the Properties dialog box if you have added userdefined fields to the Cell Types table.
The following table describes the parameters to be specified for each hopping mode.
490
Parameter
Frequency domain
Hopping mode
Non hopping
BBH
SFH
Not used
Allocation strategy
C/I threshold
Interference predictions,
Automatic frequency planning
DL power reduction
= 0 for BCCH
= 0 for TCH
= 0 for BCCH
= 0 for TCH
= 0 for BCCH
= 0 for TCH
Hopping mode
Interference predictions
Non Hopping
Base Band
Hopping
Synthesised
Hopping
Reception threshold
AFP weight
HSN domain
Not used
Lock HSN
DTX supported
Traffic analysis
Traffic analysis
Timeslot configuration
Dimensioning
AT332_UMR_E0
Parameter
Hopping mode
Non hopping
BBH
SFH
Traffic analysis,
Packet predictions
Traffic analysis,
Packet predictions
Diversity Mode
The following table describes the parameters to be specified for each hopping mode.
Parameter
Frequency domain
Hopping mode
Non hopping
BBH
SFH
Not used
Allocation strategy
C/I threshold
Interference predictions,
Automatic frequency planning
DL power reduction
= 0 for BCCH
=> 0 for TCH
<> 0 for
TCH_INNER
= 0 for BCCH
=> 0 for TCH
<> 0 for
TCH_INNER
= 0 for BCCH
=> 0 for TCH
<> 0 for
TCH_INNER
Hopping mode
Interference predictions
Non Hopping
Base Band
Hopping
Synthesised
Hopping
Reception threshold
AFP weight
HSN domain
Not used
Lock HSN
DTX supported
Traffic analysis
Traffic analysis
Timeslot configuration
Dimensioning
491
The coding scheme index number is an input in traffic captures (and, therefore, in dimensioning) and in GPRS coverage predictions. It is important to keep in mind that, before dimensioning, in other words, before TRXs have been allocated to transmitters, the TRX configuration defined per subcell is used in calculations. However, once TRXs have been allocated, the value for
the TRX configuration is read from the TRXs. The TRX configuration, and any parameters or limitations, will have be defined
again for the TRXs. Otherwise, the configuration will not be taken into account during calculations.
In Atoll, you can create or import a TRX configuration for GSM/GPRS/EDGE documents.
To create a new TRX configuration:
1. In the Parameters explorer, expand the GSM Network Settings folder, right-click the TRX Configurations folder, and
select Open Table. The TRX Configurations table appears.
2. In the row marked with the New Row icon (
), enter the following parameters to create a TRX configuration (for
information on working with data tables, see "Data Tables" on page 75):
If you have a TRX configuration data in text or comma-separated value (CSV) format, you can import it into the TRX Configuration table 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 TRX Configuration table of your current Atoll document. When you are importing, Atoll allows you to
select what values you import into which columns of the table.
To import a new TRX configuration:
1. Select the Network explorer.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Network Settings > TRX Configurations. The TRX Configuration table appears. The HSN Domains table contains
a entry called "Standard."
4. Right-click the TRX Configuration table. The context menu appears.
5. Select Import from the context menu. For information on importing table data, see "Importing Tables from Text Files"
on page 88.
492
AT332_UMR_E0
Ideal Link Adaptation: Select the Ideal Link Adaptation check box if you want the codec mode that offers the best
quality indicator (BER, FER, or MOS) to be selected. Otherwise, Atoll will choose the codec mode with the highest
priority from those requiring an adaptation threshold lower than the calculated qualIty (CN or CN and CI + N).
QI for Ideal Link Adaptation: Select the quality indicator to be used if the Ideal Link Adaptation check box is
selected.
Reference Noise (dBm): Enter the receiver noise that provided the mapping (thresholds - codecs). In coverage predictions, for a specific terminal leading to another receiver total noise, the thresholds will be shifted by the noise
difference.
You can add new fields to the Codec Configuration table by right-clicking the table and
selecting Table Fields from the context menu. The new fields will appear in the Codec
Configuration table and on the Other Properties tab of the selected codec configurations
Properties dialog box.
493
4. In the Codec Modes folder, right-click Configurations. The context menu appears.
5. Select Open Table. The Codec Configurations table appears.
6. In the Codec Configuration table, right-click the record describing the codec configuration for which you want to
define adaptation thresholds. The context menu appears.
7. Select Record Properties from the context menu. The codec configuration Properties dialog box appears.
8. Select the Adaptation Thresholds tab. Each codec mode adaptation threshold has the following parameters:
9. Click OK.
494
AT332_UMR_E0
QI = f(C/I): The values of the graph defining the selected quality indicator threshold as a function of CI. You can
view the graph and edit its values by selecting the row containing the quality indicator and clicking the CI Graph
button.
If intra-technology third order intermodulation interference is taken into account, Atoll assumes that the CI
graphs include the effect of this interference whereas the CN graphs do not. This option requires activation
through changes in the database. For more information, contact support.
MAL Length: The mobile allocation list length to which the quality indicator graph corresponds.
You can create a new quality indicator threshold by entering the parameters in the row
marked with the New Row icon (
).
9. Click OK.
495
Number: The coding scheme number. By default the limit is 4 in GPRS, 9 in GPRS, and 12 in GPRS2 (EDGE evolution)
Technology: The technology the coding scheme can be used for: GPRS or EDGE. EGPRS and EGPRS2 (EDGE evolution) are grouped together into EDGE.
Modulation: The modulation of the coding scheme. For any coding scheme except the ones using the modulations
GMSK (GPRS) and QPSK (DBS-5 and DBS-6 in EGPRS2), a power backoff is applied on the GPRS/EDGE service area.
Coding: The coding of the selected coding scheme. Coding is convolutional for GPRS and EGPRS, turbo for EGPRS2
(EDGE evolution).
Peak RLC Throughput/Timeslot (Kbps): For a given quality, if several codec modes are possible, the one with the
highest priority (highest number) is retained.
Technology: Select the technology that this configuration can be used with: GPRS/EDGE or just GPRS.
Reference Noise (dBm): Enter the total noise at the receiver. The reference noise is used to convert values of C in
graphs to values of CN.
You can add new fields to the Coding Scheme Configurations table by right-clicking the
table and selecting Table Fields from the context menu. The new fields will appear in the
Coding Scheme Configurations table and on the Other Properties tab of the selected
coding scheme configurations Properties dialog box.
8. In the Coding Scheme Configurations table, right-click the record describing the coding scheme configuration for
which you want to define adaptation thresholds. The context menu appears.
9. Select Record Properties from the context menu. The coding scheme configurations Properties dialog box appears.
The coding scheme configurations Properties dialog box has a General tab which allows you to modify the properties
described above.
10. Select the Thresholds tab. Each coding scheme threshold has the following parameters:
496
AT332_UMR_E0
Effective RLC Throughput = f(C) (Kbps): The values of the graph defining the throughput per timeslot as a function
of C. You can view the graph and edit its values by selecting the row containing the coding scheme and clicking the
C Graph button.
Effective RLC Throughput = f(C/I) (Kbps): The values of the graph defining the throughput per timeslot as a function of CI. You can view the graph and edit its values by selecting the row containing the coding scheme and
clicking the CI Graph button.
If intra-technology third order intermodulation interference is taken into account, Atoll assumes that the CI
graphs include the effect of this interference whereas the C graphs do not. This option requires activation through
changes in the database. For more information, contact support.
Frequency Hopping: The type of frequency hopping to which this coding scheme applies. You can select "All" if
you want it to apply to all types of frequency hopping.
Mobility: The mobility to which this coding scheme applies. You can select "All" if you want it to apply to all mobilities.
Frequency Band: The frequency band to which this coding scheme applies. You can select "All" if you want it to
apply to all frequency bands.
MAL Length: The mobile allocation list length to which the coding scheme (and its related quality thresholds)
applies.
You can create a new coding scheme threshold by entering the parameters in the row
marked with the New Row icon (
).
497
C Graph: Click the C Graph button to display a graph defining the throughput as a function of C.
C/I Graph: Click the C/I Graph button to display a graph defining the throughput as a function of CI.
If intra-technology third order intermodulation interference is taken into account, Atoll assumes that the CI graphs
include the effect of this interference whereas the C graphs do not. This option requires activation through changes
in the database. For more information, contact support.
10. Click OK to close the dialog box.
498
AT332_UMR_E0
Under Mapping between TRX numbers and timeslot configurations, each row corresponds to a distribution of timeslots and is identified by an index number. During dimensioning, Atoll determines the number of circuit and packet
timeslots required to meet the traffic demand. Atoll uses the timeslot configuration to determine how many TRXs are
needed to meet the need in timeslots. If, during dimensioning, there are not enough index numbers in the timeslot
configuration, Atoll reuses the last index number in the timeslot configuration.
7. In the timeslot configurations Properties dialog box, enter the following information for each index number:
Number of Shared Timeslots: The number of timeslots that can be used for both circuit-switched (GSM) and
packet-switched (GPRS and EDGE) services.
Number of Circuit Timeslots: The number of timeslots that can be used only for both circuit-switched (GSM) services.
Number of Packet Timeslots: The number of timeslots that can be used only for packet-switched (GPRS and EDGE)
services.
In GSM/GPRS/EDGE the total number of timeslots per index number must not exceed 8 for
timeslot configurations intended for TCH TRXs and 7 for timeslot configurations intended
for BCCH TRXs.
499
7.9.8.2.1
Coverage predictions
Traffic captures
Dimensioning
Interference matrices
500
AT332_UMR_E0
Name: Read-only string made of the name of the transmitter and the "@0" suffix (e.g. Site156_1@0).
ID: The ID is a user-definable network-level parameter for cell identification. You can enter an ID that is different
from the name of the base transmitter.
Site: The Site on which the base transmitter is located. This field cannot be edited.
Shared Antenna: This field is used to identify the transmitters, repeaters, and remote antennas located at the
same site or on sites with the same position and that share the same antenna. The entry in the field must be the
same for all transmitters, repeaters, and remote antennas sharing the same antenna. When changes are made to
the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared
antenna.
Under Antenna Position, you can modify the position of the antenna:
Relative to Site: Select this option if you want to enter the antenna position as an offset 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.
10. Click the Transmitter tab. You can set the following parameters:
Total Losses: You can enter a value for Total Losses or let Atoll calculate losses according to the characteristics of
the equipment assigned to the transmitter. The Equipment Specifications dialog box can be accessed by clicking
the Equipment button.
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. The other fields, Azimuth, Mechanical Downtilt, and Additional
Electrical Downtilt, display additional antenna parameters.
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.
The Additional Electrical Downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
11. Click the Propagation tab. On the Propagation tab, you can modify the following: the Propagation Model, Radius, and
Resolution for both the Main Matrix and the Extended Matrix.
12. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the
Transmitters table.
13. Click OK.
7.9.8.2.2
To create a multi-band template, you must have an appropriate multi-band cell type to
assign to the template. If you have not already created a multi-band cell type, you must do
so before creating the template. For information on creating a cell type, see "Creating a
Cell Type" on page 488.
501
Add a new station template: If you select this option and click OK, Atoll creates a new station template based
on the selected one.
Add a new multi-band station template for the frequency band: If you select this option and click OK, Atoll
allows you to set the propagation parameters for the selected frequency band.
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 antennas.
The Additional Electrical Downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
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 4: Radio
Calculations and Models.
On the Transmitter tab, under Transmission, you can set the Total losses. Atoll calculates the losses according to
the characteristics of the equipment assigned to the transmitter. Equipment can be assigned using the Equipment
502
AT332_UMR_E0
Specifications dialog box which appears when you click the Equipment button. For information on the Equipment
Specifications dialog box, see "Transmitter Properties" on page 280.
Figure 7.109: Properties dialog box for frequency band of a multi-band template - General Tab
On the Transmitter tab, under Transmission/Reception, you can see the total losses and the noise figure of the
transmitter for this specific frequency band. 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 dialog box which appears when you click the Equipment button.
For information on the Equipment Specifications dialog box, see "Transmitter Properties" on page 280.
Figure 7.110: Properties dialog box for frequency band of a multi-band template - Transmitter Tab
8. Click OK. The properties defined for the frequency band appear in the Station Template Properties dialog box with a
name composed of the multi-band template they belong to followed by the frequency band, separated by "@".
9. Repeat step 7. for every frequency band modelled by the multi-band template.
7.9.8.2.3
503
Min. interferer reception threshold: This limit is used by Atoll to limit the input of interferers in calculations. When
the interferer reception threshold is set, the performance of calculations based on CI, such as coverage by CI level,
interfered zones. and GPRS/EDGE predictions can be improved. As well, the performance of calculations using the
Interference view of the Point Analysis window, traffic analyses, and interference histograms can also be improved.
This value is used as a filter criterion on interferers. Atoll discards all interferers with a signal level lower than this
value.
Height/ground: The receiver height at which the path loss matrices and coverage predictions are calculated. Calculations made on mobile users (from traffic maps) in Monte Carlo simulations are also carried out at this receiver height.
Antenna: Select an antenna for the receiver.
Losses: Specify any receiver losses.
Adjacent channel protection level: The maximum coverage range of transmitters in the network.
Default max range: The maximum coverage range of transmitters in the network.
504
AT332_UMR_E0
Figure 7.111: Codec Configuration Properties: Quality Graphs tab (with MAL length definition)
In quality indicators coverage predictions (see "Making a Circuit Quality Indicator (BER, FER, or MOS) Prediction" on page 452),
Atoll will extract, for a specified quality indicator and a given codec mode, the quality indicator value corresponding to the
MAL of the receiver being studied. If graphs for the mobile MAL length are not defined, Atoll selects the graphs to which the
MAL length is the most similar, i.e.:
if the mobile MAL length exceeds all the MAL lengths defined in the quality indicator graphs, the closest MAL length
is selected;
if the mobile MAL length is between two MAL lengths defined in the quality indicator graphs, Atoll carries out an interpolation on the graphs to extract the appropriate quality indicator value.
For coding scheme configurations, it means that you can define a specific coding scheme graph per MAL length where the
graph efficiency increases whereas the MAL length increases too (See Figure 7.112 on page 505).
Figure 7.112: Coding Scheme Configuration Properties (with MAL length definition)
In GPRS/EDGE coverage predictions (see "Packet-Specific Coverage Predictions" on page 442), Atoll will extract, for a given
coding scheme, the throughput corresponding to the MAL of the studied receiver. If graphs for the mobile MAL length are not
defined, Atoll selects the graphs for which the MAL length is the most similar, i.e.:
if the mobile MAL length exceeds all the MAL lengths defined in the coding scheme graphs, the closest MAL length is
selected;
if the mobile MAL length is between two MAL lengths defined in the coding scheme graphs, Atoll carries out an interpolation on the graphs to extract the appropriate throughput.
505
For a more precise description of these fields, see the Administrator Manual.
A point analysis (see "Studying the Profile Around a Base Station" on page 295)
A coverage prediction (see "Studying DL Signal Level Coverage of a Single Base Station" on page 307, "Interference
Coverage Predictions" on page 430, "Packet-Specific Coverage Predictions" on page 442, and "Making a Circuit Quality
Indicator (BER, FER, or MOS) Prediction" on page 452)
Neighbours (see "Automatically Allocating Neighbours to Multiple Cells" on page 226)
Traffic capture (see "Calculating and Displaying a Traffic Capture" on page 327).
Cell Edge Coverage Probability: Enter the probability of coverage at the edge of the cell. The value you enter in
this dialog box is for information only.
Standard Deviation: Select the type of standard deviation to be used to calculate the shadowing margin:
From Model: The model standard deviation. Atoll will display the shadowing margin on the signal level.
CI: The CI standard deviation. Atoll will display the shadowing margin on the CI level.
506
AT332_UMR_E0
Interference received by mobiles on the downlink: Interference can be received by mobiles in a GSM network on the
downlink from external base stations and mobiles in the vicinity.
Interference from external base stations (also called downlink-to-downlink interference) can 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.
Interference from external mobiles (also called uplink-to-downlink interference) can be created by insufficient separation between the uplink frequency used by the external network and the downlink frequency used by your GSM
network. Such interference may also come from co-existing TDD networks. The effect of this interference is modelled
in Atoll using the Additional DL Noise Rise definable for each TRX in the GSM network. This noise rise is taken into
account in all interference-based calculations. For more information on the Additional DL Noise Rise, see "TRX Properties" on page 287.
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 GSM document, i.e. in co-planning mode or in a multi-RAT document.
To define the inter-technology IRFs in the victim network:
1. Select the Parameters explorer.
2. Click the Expand button ( ) to expand the Radio Network Equipment folder.
3. In the Radio Network Equipment folder, right-click Inter-technology Interference Reduction Factors. The context
menu appears.
4. Select Open Table. 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:
507
Reduction Factors (dB): Click the cell corresponding to the Reduction Factors (dB) column and the current row in
the table. The Reduction Factors (dB) dialog box 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.
6. When you have finished defining interference reduction factors, click OK.
508
Chapter 8
UMTS HSPA
Networks
This chapter covers the following topics:
510
AT332_UMR_E0
R99 users: The Circuit (R99) and Packet (R99) service users. These require an R99 bearer.
HSDPA users: The users that only support HSDPA. These have an HSDPA-capable terminal and one of the following
services:
HSDPA users require an R99 bearer (i.e. the A-DPCH radio bearer) and an HSDPA bearer.
HSPA users: The users that support both HSDPA and HSUPA. These have an HSPA-capable terminal and one of the
following services:
HSPA users require an R99 bearer (i.e. the E-DPCCH/A-DPCH radio bearer), an HSDPA bearer and an HSUPA bearer.
DC-HSPA users: The dual-cell HSPA users. Users with DC-HSPA-capable terminals that can simultaneously connect to
two HSPA cells of the transmitter for data transfer. The R99 A-DPCH bearer is transmitted on one of the cells, which
is called the anchor cell. The user can be assigned HSDPA and HSUPA bearers in each of the cells.
MC-HSPA users: The multi-cell HSPA users. Users with MC-HSPA-capable terminals that can simultaneously connect
to several HSPA cells of the transmitter for data transfer. The R99 A-DPCH bearer is transmitted on one of the cells,
which is called the anchor cell. The user can be assigned HSDPA and HSUPA bearers in each of the cells.
DB-MC-HSPA users: The dual-band multi-cell HSPA users. Users with DB-MC-HSPA-capable terminals that can simultaneously connect to several HSPA cells on co-site transmitters using different frequency bands. The R99 A-DPCH
bearer is transmitted on one of the cells, which is called the anchor cell. The user can be assigned HSDPA and HSUPA
bearers in each of the cells.
BE services: Best Effort services.
VBR services: Variable Bit Rate services.
CBR services: Constant Bit Rate services. CBR services do not support multi-cell mode.
511
Network Configuration
- Add Network Elements
- Change Parameters
Basic Predictions
(Best Server, Signal Level)
Neighbour Allocation
Traffic Maps
5a
5b
Monte-Carlo
Simulations
User-defined values
Cell Load
Conditions
5c
6a
UMTS/HSPA Predictions
).
You can open an existing Atoll document by selecting File > Open.
Creating a new a new Atoll document is explained in Chapter 1: Working Environment.
).
You can add and modify the following base station elements:
You can also add base stations using a base station template (see "Placing a New Station Using a Station Template" on
page 522).
3. Carry out basic coverage predictions (
).
5. Before making more advanced coverage predictions, you need to define cell load conditions (
).
You can generate realistic cell load conditions by creating a simulation based on a traffic map ( 5a and 5b ) (see
"Studying UMTS Network Capacity" on page 571).
You can define them manually either on the Cells tab of each transmitters Properties dialog box or in the Cells
table (see "Creating or Modifying a Cell" on page 521) (
5c
).
6. Make UMTS-specific coverage predictions using the defined cell load conditions (
512
).
).
AT332_UMR_E0
TMA
Antenna
- Height
Feeder Cable
Transmitter
- Noise figure
- Power
Site
- X, Y coordinates
513
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 dialog box afterwards. For
information on placing sites using the mouse, see "Moving a Site Using the Mouse" on
page 57.
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.
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 616.
If no equipment is assigned to the site, Atoll considers the following default values:
514
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 dialog box, see "Site Properties" on page 513. 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 dialog box, see "Defining Frequency Bands" on page 612.
Shared antenna: This field is used to identify the transmitters, repeaters, and remote antennas located at the same
site or on sites with the same position and that share the same antenna. The entry in the field must be the same for
all transmitters, repeaters, and remote antennas sharing the same antenna. When changes are made to the position
offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same
changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. This field is
also used for multi-band transmitters to synchronise antenna parameters for different frequency bands.
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.
Max Range: You can define a maximum coverage range for the transmitter.
AT332_UMR_E0
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 in the Network explorer.
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 dialog box which appears when you click
the Equipment button.
In the Equipment Specifications dialog box, the equipment that you select and the gains and losses that you define
are used to initialise the 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 161.
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 161.
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 162.
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.
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 dialog box. 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.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
Mechanical Azimuth, Mechanical downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt display additional antenna parameters.
The Additional Electrical Downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
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 621.
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).
515
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.
The Additional Electrical Downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
Cell Tab
When you create a transmitter, Atoll automatically creates a cell for the transmitter using the properties of the currently
selected station template.
The cell tab enables you to configure the properties for every cell of a transmitter. For more information on the properties of
a cell, see "Cell Properties" on page 516.
Propagation Tab
Transmitters are taken into account during calculations. Therefore, you must specify their 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. For information on propagation models, see "Assigning Propagation Parameters" on page 187.
Display Tab
On the Display tab, you can modify how a transmitters are displayed. For information on changing display properties, see
"Setting the Display Properties of Objects" on page 51.
The following HSDPA options apply to all the cells of the transmitter:
Multi-cell mode: Select whether the transmitter supports carrier aggregation in the downlink (DL multi-cell), or in the
downlink and in the uplink (UL/DL multi-cell). When multi-cell is active, the user can simultaneously connect to several
carriers of the transmitter for data transfer (up to eight carriers in the downlink and two carriers in the uplink) and be
assigned HSDPA and HSUPA bearers in each of the cells. The R99 A-DPCH bearer is transmitted on one of the cells,
which is called the anchor cell. The maximum number of cells to which the user can simultaneously connect depends
on the HSDPA and HSUPA UE categories of the terminal.
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.
The following parameters can be set for each individual cell of the transmitter:
516
AT332_UMR_E0
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 Administrator 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.
Order: The display order of a cell within the transmitter. This value is used to determine the order in which information
related to a cell will be displayed in the Network explorer and on the map. This field is automatically filled by Atoll but
you can change these default values to display cells in a user-defined order.
The consistency between values stored in this field is verified by Atoll. However, inconsistencies may arise when tools other than Atoll modify the database. You can check for inconsistencies in the cell display order and fix them by selecting Data Audit > Cell Display Order
Check in the Document menu.
Layer: The network layer to which the cell belongs. This information is used in determining the best serving cell. For
more information on defining layers, see "Defining Network Deployment Layers" on page 614.
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 transmitted 110 of the time. Consequently, the value entered for
the SCH power should only be 110 of its value when transmitted, 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 active set threshold. It is the EcI0 margin in comparison with the EcI0 of the best server. It is
used to determine which cells, apart from the best server, will be part of the active set.
Min RSCP (dBm): The minimum pilot RSCP required for a user to be connected to the cell. The pilot RSCP is compared
with this threshold to determine whether or not a user can be connected to the cell.
When this field is empty, Atoll uses the Default Min Pilot RSCP Threshold defined on the
Calculation Parameters tab of the Network Settings Properties dialog box.
Handover margin (dB): You can define the handover margin to use for best serving cell selection. The handover
margin is used in UMTS networks to avoid handover ping-pong between cells. For more information on best serving
cell selection, see "Best Serving Cell and Active Set Determination" on page 622.
Cell individual offset (dB): You can define the cell individual offset to use for best serving cell selection. The cell individual offset (CIO) is used in UMTS networks in order to tune or bias the ranking of potential servers for best serving
cell selection in connected mode. For more information on best serving cell selection, see "Best Serving Cell and Active
Set Determination" on page 622.
DL Max Throughput per User (kbps): The downlink max throughput per user in kbps. The DL max throughput per user
is the maximum connection rate in the downlink for a user. The DL and UL peak throughputs are taken into account
during power control simulation.
UL Max Throughput per User (kbps): The uplink max throughput per user in kbps. The UL max throughput per user is
the maximum connection rate in the uplink for a user. The DL and UL peak throughputs 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 the 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
in the Parameters explorer and selecting Properties from the context menu. Then, on the
Global Parameters tab of the Properties dialog box, under DL Load, you can select
% Pmax. The total power value is automatically converted and set as a percentage of the
maximum power.
517
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.
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.
SC Locked: The status of the primary scrambling code allocated to the cell. If the SC Locked check box is checked, the
automatic allocation tool considers that the current primary scrambling code is not modifiable.
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.
Additional 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 interference-based calculations involving this cell in the simulation. It is not used in predictions (AS Analysis, multi-point analysis and coverage
predictions). In predictions, Atoll calculates the uplink total interference from the UL load factor which includes intertechnology uplink interference. For more information on inter-technology interference, see "Modelling Inter-technology Interference" on page 624.
Additional 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 interferencebased calculations involving this cell. For more information on inter-technology interference, see "Modelling Intertechnology Interference" on page 624.
Neighbours: You can access a dialog box in which you can set both intra-technology (intra-carrier and inter-carrier)
and inter-technology neighbours by clicking the Browse button. For information on defining neighbours, see "Editing
Neighbours in the Cell Properties" on page 228.
The Browse button may 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) or HSPA+.
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 bearer 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.
518
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 bearer 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 bearer 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 bearer user during the simulation cannot exceed this maximum
value.
AT332_UMR_E0
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 bearer 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 Best Effort), Packet (HSDPA - Variable Bit Rate), Packet (HSPA - Best Effort), and Packet (HSPA - Variable Bit Rate)
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.
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 - Best Effort)
users, Packet (HSDPA - Variable Bit Rate) users, Packet (HSPA - Best Effort) users, Packet (HSPA - Variable Bit
Rate) 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 bearer users to be
served. You can select the scheduler from the list of schedulers available in the Schedulers table. For more information, see "Defining HSDPA Schedulers" on page 620.
MIMO Support: The MIMO method used by the cell when it supports HSPA+. You can choose between None,
Transmit Diversity, or Spatial Multiplexing.
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 - Best Effort)
users, Packet (HSPA - Variable Bit Rate) 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 in the Parameters explorer and selecting Properties
from the context menu. Then, on the Global Parameters tab of the Properties dialog box,
under DL Powers, you can select Relative to Pilot. The SCH power, the CCH power, the HSSCCH power, and the HSUPA power values are automatically converted and set as relative
to the pilot power.
519
)and the coordinates of the mouse cursor are displayed in the status bar.
2. Click the map at the location where you want to place the new site. A new site is created with default values at the
corresponding location.
Alternatively, you can create a new site by entering its coordinates and properties as
described in "Site Properties" on page 513, by right-clicking the Sites folder and selecting
New from the context menu.
To create a transmitter, right-click the UMTS Transmitters select New from the context menu.
To modify an existing transmitter, expand the UMTS Transmitters folder, right-click the transmitter that you want
to modify, and select Properties from the context menu.
520
AT332_UMR_E0
An alternative way of creating several transmitters at the same time, or modifying several
existing transmitters, is to edit or paste the data directly in the Transmitters table. You can
open the Transmitters table by right-clicking the LTE Transmitters folder in the Network
explorer and selecting Open Table from the context menu. For information on copying and
pasting data, see "Copying and Pasting in Tables" on page 83.
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.
TMA: Select a tower-mounted amplifier (TMA) from the list. Click the Browse button to access the properties of
the TMA. For information on creating a TMA, see "Defining TMA Equipment" on page 161.
Feeder: Select a feeder cable from the list. Click the Browse button to access the properties of the feeder. For
information on creating a feeder cable, see "Defining Feeder Cables" on page 161.
Transmitter equipment: Select transmitter equipment from the Transmitter list. Click the Browse button to
access the properties of the transmitter equipment. For information on creating transmitter equipment, see
"Defining Transmitter Equipment" on page 162.
Feeder length: Enter the feeder length at transmission and reception.
Miscellaneous losses: Enter any additional losses at transmission and reception. The value must be positive.
Receiver antenna diversity gain:
Loss related to repeater noise rise:
4. Click OK.
521
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 60.
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.
3. 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.
8.2.2.8.1
522
AT332_UMR_E0
Electrical Azimuth, Electrical Downtilt, and Additional electrical downtilt display additional antenna parameters.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
Under Main antenna, you can select the main antenna Model, under Smart antenna, you can select the smart
antenna Equipment used by the transmitter, and under Number of antenna ports, you can enter the number of
antennas used for Transmission and for Reception for MIMO.
Under Path loss matrices, you can modify the following: the Main propagation model, the Main radius, and the Main
resolution, and the Extended propagation model, the Extended radius, and the Extended resolution. For information
on propagation models, see Chapter 4: Radio Calculations and Models.
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.
Transmitter Tab
Under Transmission/Reception, you can click the Equipment button to open the Equipment Specifications dialog box
and modify the tower-mounted amplifier (TMA), feeder cables, or transmitter equipment. For information on the
Equipment Specifications dialog box, see "Transmitter Properties" on page 514.
The information in the real Total Losses in transmission and reception boxes is calculated from the information you
entered in the Equipment Specifications dialog box. 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 dialog box. 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 621.
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).
UMTS Tab
On this tab, you modify the Carriers (each corresponding to a cell) that this station supports. For information on carriers and
cells, see "Cell Properties" on page 516.
Carrier: You can select the 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, click the Browse button and select the carriers to be created for each sector of the station.
Primary Scrambling Code: Specify 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 Max Throughput/User, the Max UL Load Factor, and the UL Max Throughput/User.
Under Load Conditions, you can modify the Total Transmitted Power, the UL Load Factor, and the UL Reuse Factor.
Under Additional Interference, 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 624.
You can also modify the Number of Uplink and Downlink Channel Elements, the Max Iub Uplink and Downlink Backhaul Throughputs and select the Equipment.
HSPA/HSPA+ Tab
On these tabs, 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+. When HSDPA functionality is supported, you can modify the following under
HSDPA (for more information on the fields, see "Cell Properties" on page 516):
Multi-cell mode: You can select whether the transmitter supports carrier aggregation in the downlink (DL multi-cell),
or in the downlink and in the uplink (UL/DL multi-cell). When multi-cell is active, users can simultaneously connect to
several carriers of the transmitter for data transfer (up to eight carriers in the downlink and two carriers in the uplink).
523
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 bearer users. At the end of the simulation, you can commit
the calculated available HSDPA power and total power values to each cell.
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. For the Proportional Fair scheduler, to edit the MUG graph, see "Defining HSDPA Schedulers" on page 620.
Under HSUPA, if HSUPA functionality is supported, you can modify the following (for more information on the fields,
see "Cell Properties" on page 516):
You can modify the DL Power, the UL Load, the Max Number of Users, and the Number of Users.
Neighbours tab
Max number of neighbours: Set the maximum numbers of Intra-technology and Inter-technology neighbours. For information on defining neighbours, see "Neighbour Planning" on page 223.
Other Properties
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 dialog box.
8.2.2.8.2
8.2.2.8.3
8.2.2.8.4
524
AT332_UMR_E0
8.2.2.8.5
8.2.2.8.6
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.
If you want to duplicate the base station without the intra- and inter-technology neighbours of its transmitters,
select Duplicate > Without 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, select Duplicate > With Outward Neighbours from the context menu,
3. In the map window, place the new base station on the map using the mouse:
To create a duplicate base station and site, move the pointer over the map to where you would like to place the
duplicate. The exact coordinates of the pointers current location are visible in the Status bar.
To place the duplicate base station on an existing site, move the pointer over the existing site where you would
like to place the duplicate. When the pointer is over the site, the site is automatically selected. The exact coordinates of the pointers current location are visible in the Status bar.
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 60.
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.
525
Any duplicated remote antennas and repeaters will retain the same donor transmitter
as the original. If you want the duplicated remote antenna or repeater to use a
transmitter on the duplicated base station, you must change the donor transmitter
manually.
You can also place a series of duplicate base stations by pressing and holding Ctrl in step 4. and clicking to place each
duplicate base station.
For more information on the site, transmitter, and cell properties, see "Definition of a UMTS Base Station" on page 513.
) in the Radio Planning toolbar. The Point Analysis window opens and the pointer
changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and the
receiver. You can move the receiver on the map (see "Moving the Receiver on the Map" on page 203).
3. Select the Profile view. The Profile view displays the profile between the transmitter and the receiver with the terrain
and clutter heights.
Transmitter selection list.
Display
area
including:
received signal,
shadowing
margin,
cell
edge coverage
probability,
propagation
model
used,
and transmitter-receiver
distance.
Fresnel ellipsoid
Line of sight
526
The received signal strength from the selected transmitter for the cell with the highest reference signal power
The propagation model used
The shadowing margin and the indoor loss (if selected)
The distance between the transmitter and the receiver.
AT332_UMR_E0
4. If needed, select an other transmitter from the list. You can click the Properties button (
properties.
) to display the Calculation Options dialog box and change the following:
Change the X and Y coordinates to change the current position of the receiver.
Select the Shadowing taken into account check box and enter a Cell edge coverage probability. For more information, see "Taking Shadowing into Account in Point Analyses" on page 204.
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. Indoor losses are defined per frequency per
clutter class. For more information, see "Taking Indoor Losses into Account" on page 203.
7. In the Profile view toolbar, you can use the following tools:
) to view the geographic profile between the transmitter and the receiver.
) again to view the radio signal path between the transmitter and the
Click the Detailed Report button ( ) to display a text document with details on the displayed profile analysis.
The detailed report is only available for the Standard Propagation Model.
Click the Copy button (
) to copy the content of the view and paste it as a graphic into a graphic editing or wordprocessing programme.
) again.
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.
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 83.
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 and Spreadsheets" on page 86. For information on importing table data, see "Importing Tables from Text Files" on page 88.
527
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 "Associating a
Label to an Object" on page 53.
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 "Associating a Tip Text to an Object" on page 54.
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.
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 "Setting the Display Type" on page 52.
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 (
and
).
For information on defining the transmitter symbol, see "Setting the Display Type" on page 52.
Defining the frequency bands in the document (see "Defining Frequency Bands" on page 612).
Selecting and calibrating a propagation model for each frequency band (see "Assigning Propagation Parameters" on
page 187).
Assigning a frequency band, with its propagation model, to each transmitter (see "Creating or Modifying a Cell" on
page 521 and "Creating or Modifying a Transmitter" on page 520).
Defining the frequency bands with which terminals are compatible (see "Modelling Terminals" on page 249).
528
AT332_UMR_E0
3. Defining the layers with which services and terminals are compatible (see "Modelling Services" on page 241 and
"Modelling Terminals" on page 249).
Repeaters are defined in the Repeaters table. Each repeater is assigned repeater equipment with specific noise, gain, and
power characteristics, which are specified in the Repeater Equipment table.
This section covers the following topics:
Name: You can change the Name of the repeater. By default, repeaters are named "SiteX_Y_RepZ" where "X" is the
donor site number, "Y" the donor transmitter number, and "Z" a number assigned to the repeater when it was created.
Donor: The donor of a repeater can be a transmitter, a remote antenna, or another repeater. Click Browse to open
the Properties of the donor.
Site: Specify the site on which the repeater is located. Click Browse to open the Properties of the site.
Shared antenna: Specify the identifier (coverage side) of the transmitters, repeaters, and remote antennas that are
located at the same site or on sites with the same position and that share an antenna. The identifier must be the same
for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all
other transmitters, repeaters, and remote antennas defined as having a shared antenna.
Antenna position: If the repeater is not located exactly on the site, you can specify its location.
Relative to site: Select this option to specify the position of the repeater relative to the site itself and then enter
the Dx and Dy offsets.
Coordinates: Select this option to specify the position of the repeater by its X and Y absolute coordinates.
Equipment: Select an equipment from the list. Click Browse to open the Properties of the equipment.
Amplifier Gain: Specify a gain for the amplifier. The amplifier gain is used in the link budget to evaluate the repeater
total gain.
Donor-repeater link, specify the type of link between the donor and the repeater:
529
Air: Select this option to specify an off-air repeater. Select a Propagation model and either enter the Propagation
losses between the donor and the repeater or click Calculate to determine the actual propagation losses based
on the propagation model. 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.
Microwave link: Select this option to specify a microwave link. Specify the total Link losses for the link between
the donor transmitter and the repeater.
Optical fibre link: Select this option to specify an optical fibre link. Specify the total Fibre losses for the link
between the donor transmitter and the repeater
If you select Air under Donor-repeater link, enter the following information under Antenna:
Model: Select the antenna model from the list. Click Browse to open the antenna properties.
Click Select to open the Antenna Selection Assistant. This assistant lists all the antennas that match the currently selected physical antenna and whose minimum and maximum operating frequencies include the operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
Height/ground: Specify the height of the antenna above the ground. This is added to the altitude of the site
as given by the DTM. If the repeater is situated on a building, the height entered must include the height of
the building.
Mechanical Azimuth and Mechanical Downtilt : Specify additional antenna parameters.
You can click the Calculate button to update the mechanical azimuth and mechanical
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 select Air under Donor-repeater link, enter the following information under Feeders:
Type: Select the type of feeder from the list. Click Browse to open the feeder properties.
Length: Enter the Length of the repeater feeder cable for Transmission and Reception.
Active: specify whether the repeater is active. Only active repeaters (displayed in red in the Transmitters folder in the
Network explorer) are calculated.
Total gain: Specify the total gain (in downlink and uplink) or click Calculate to determine the actual gain in both directions. If you have modified any settings in the General, Donor Side, or Coverage Side tabs, click Apply before clicking
the Calculate button.
In downlink, the total gain is applied to each power (pilot power, SCH power, and so on).
In uplink, the total gain is applied to each terminal power.
The total gain takes into account losses between the donor transmitter and the repeater, donor characteristics (donor
antenna gain, reception feeder losses), amplifier gain, and coverage characteristics (coverage antenna gain, transmission feeder losses).
Height/ground: Specify the height of the antenna above the ground. This is added to the altitude of the site as
provided by the DTM. If the repeater is located on a building, the height entered must include the height of
building.
Model: Select antenna model from the list. Click Browse to open the antenna properties.
Click Select to open the Antenna Selection Assistant. This assistant lists all the antennas that match the currently
selected physical antenna and whose minimum and maximum operating frequencies include the operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on page 159
530
Mechanical Azimuth, Mechanical Downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt: Specify the additional antenna parameters.
Secondary antennas: Select one or more secondary antennas in the Antenna column and enter their Azimuth,
Mechanical downtilt, Additional electrical downtilt, and % Power.
AT332_UMR_E0
The Additional electrical downtilt can be made available through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
):
If necessary, enter a Max uplink power, an Internal delay and Comments. These fields are for information only
and are not used in calculations.
531
When the donor is a transmitter, you can see to which base station the repeater is
connected by clicking it; Atoll displays a link to the donor transmitter. You can hide
the link by clicking it again.
When the donor is a repeater or a remote antenna, Atoll displays a spider-type link
showing the entire chain down to the donor transmitter. The same spider-type link
is displayed when you click any of the items belonging to the chain is clicked (i.e.,
donor transmitter, any repeater, or any remote antenna).
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.
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".
532
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 57) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using
the Mouse" on page 58).
AT332_UMR_E0
Name: You can change the Name of the remote antenna. By default, remote antennas are named "SiteX_Y_RepZ"
where "X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned to the remote
antenna when it was created.
Donor: Specify whether the donor of the remote antenna is a transmitter, another remote antenna, or a repeater.
Click Browse to open the Properties of the donor.
Site: Specify the site on which the remote antenna is located. Click Browse to open the Properties of the site.
Shared antenna: Specify the identifier (coverage side) of the transmitters, repeaters, and remote antennas that are
located at the same site or on sites with the same position and that share an antenna. The identifier must be the same
for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all
other transmitters, repeaters, and remote antennas defined as having a shared antenna.
Antenna position: If the remote antenna is not located exactly on the site, you can specify its location.
Relative to site: Select this option to specify the position of the remote antenna relative to the site itself and then
enter the Dx and Dy offsets.
Coordinates: Select this option to specify the position of the remote antenna by its X and Y absolute coordinates.
Remote antennas do not have assigned equipment.
Donor-repeater link: specify Optical fibre link. Specify the total Fibre losses for the link between the donor transmitter and the repeater
For remote antennas, you must select Optical fibre link. Do not select Air or Microwave
link.
Active: specify whether the remote antenna is active. Only active remote antennas (displayed in red in the Transmitters folder in the Network explorer) are calculated.
533
Total gain: Specify the total gain (in downlink and uplink) or click Calculate to determine the actual gain in both directions. If you have modified any settings in the General, Donor Side, or Coverage Side tabs, click Apply before clicking
the Calculate button.
In downlink, the total gain is applied to each power (pilot power, SCH power, and so on).
In uplink, the total gain is applied to each terminal power.
The total gain takes into account losses between the donor transmitter and the remote antenna, donor characteristics
(donor antenna gain, reception feeder losses), amplifier gain, and coverage characteristics (coverage antenna gain,
transmission feeder losses).
Height/ground: Specify the height of the antenna above the ground. This is added to the altitude of the site as
provided by the DTM. If the remote antenna is located on a building, the height entered must include the height
of building.
Model: Select antenna model from the list. Click Browse to open the antenna properties.
Click Select to open the Antenna Selection Assistant. This assistant lists all the antennas that match the currently
selected physical antenna and whose minimum and maximum operating frequencies include the operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on page 159
Mechanical Azimuth, Mechanical Downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt: Specify the additional antenna parameters.
Secondary antennas: Select one or more secondary antennas in the Antenna column and enter their Azimuth,
Mechanical downtilt, Additional electrical downtilt, and % Power.
The Additional electrical downtilt can be made available through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
534
AT332_UMR_E0
When the donor is a transmitter, you can see to which base station the repeater is
connected by clicking it; Atoll displays a link to the donor transmitter. You can hide
the link by clicking it again.
When the donor is a repeater or a remote antenna, Atoll displays a spider-type link
showing the entire chain down to the donor transmitter. The same spider-type link
is displayed when you click any of the items belonging to the chain is clicked (i.e.,
donor transmitter, any repeater, or any remote antenna).
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 57) or its position relative to the site (see "Changing the Antenna Position Relative to the Site
Using the Mouse" on page 58).
535
Display Resolution
City Centre
5m
City
20 m
County
50 m
State
100 m
Country
The resolution specified here is only for display purposes. The calculated resolution is independently specified in the
propagation settings. For more information, see "Assigning Propagation Parameters" on page 187.
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the <GUID> and </GUID> tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
Receiver height: This displays the height of the receiver defined in the Calculation Parameters tab of the Network
Settings Properties dialog box
Comments: Specify an optional description of comment for the prediction.
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 99. The Group By and Sort buttons are not available when making a so-called
"global" coverage prediction (e.g., signal level coverage prediction).
536
AT332_UMR_E0
The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction).
At the top of the Conditions tab, you can specify the range to be considered for the current prediction.
Server: Select either All, Best Signal Level or Second Best Signal Level:
Shadowing taken into account: Select this option to consider shadowing in the prediction. For more information, see
"Modelling Shadowing" on page 623. If you select this option, you can change the Cell edge coverage probability.
Indoor coverage: Select this option to consider indoor losses. Indoor losses are defined per frequency per clutter class.
Carrier: Select the carrier to be studied, or select the "Best" carrier of a frequency band or of all frequency bands. In
this case, Atoll takes the highest pilot power of carriers to calculate the pilot signal level received from a transmitter.
"Studying Signal Level Coverage for a Single Base Station" on page 538
"Making a Coverage Prediction by Signal Level" on page 538
537
8.2.10.2.1
2. Specify the propagation parameters as explained in "Assigning Propagation Parameters" on page 187.
3. In the UMTS 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 dialog box appears.
The Prediction Types dialog box 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.
4. Select Coverage by Signal Level (DL) and click OK. The Coverage by Signal Level (DL) Properties dialog box appears.
5. Configure the parameters in the Properties dialog box as described in "UMTS Prediction Properties" on page 536.
The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for
each pixel.
6. Click the Display tab and specify the following options:
7. 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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
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 in the Network explorer. Atoll automatically locks the results of a
coverage prediction as soon as it is calculated, as indicated by the icon ( ) beside the coverage prediction in the Predictions
folder. When you click the Calculate button ( ), Atoll only calculates unlocked coverage predictions ( ).
8.2.10.2.2
538
AT332_UMR_E0
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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 8.5 on
page 539).
8.2.10.2.3
539
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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
You can also predict which server is 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.
8.2.10.2.4
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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
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.
540
AT332_UMR_E0
In this section, the UMTS-specific coverage predictions are 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 must set the UL load factor and DL total power. These are explained in the following
sections:
"Setting the UL Load Factor and the DL Total Power" on page 541.
This section explains the coverage predictions available for analysing the signal quality and interference. The following are
explained:
8.2.10.3.1
8.2.10.3.2
541
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 241. You must
also select the network Layer or Carrier to be considered for the determination of best servers. Otherwise, you can
calculate the prediction for all layers or carriers.
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. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab.
For a pilot signal quality prediction, the Display Type "Value Intervals" based on the Field "EcI0 (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 "Setting the Display Properties of Objects" on page 51.
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.
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 signal level: Select "Value Intervals" as the Display Type and "Ec (dBm)" as the Field.
The pilot quality relative to the EcI0 threshold: Select "Value Intervals" as the Display Type and "EcI0 margin
(dB)" as the Field.
6. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
8.2.10.3.3
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 241. You must
also select the network Layer or Carrier to be considered for the determination of best servers. Otherwise, you can
calculate the prediction for all layers or carriers.
If you want the service area (EbNt) 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.
You can also select the Indoor coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
542
AT332_UMR_E0
You can select the Bearer downgrading check box if you want the service area (EbNt) 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.
5. Click the Display tab.
For a service area (Eb/Nt) coverage prediction, the Display Type "Value Intervals" based on the Field "Max EbNt (dB)"
is selected by default. The Field you choose determines which information the service area (EbNt) downlink or uplink
prediction makes available. Each pixel is displayed in a colour corresponding to the traffic channel quality. For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
You can also set parameters to display the following results:
The traffic channel quality relative to the EbNt threshold: Select "Value Intervals" as the Display Type and
"EbNt 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 traffic 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 (EbNt) (DL) coverage prediction, you can also display the following results:
The R99 effective RLC throughput: Select "Value Intervals" as the Display Type and "Effective RLC Throughput
(kbps)" as the Field.
The R99 application throughput: Select "Value Intervals" as the Display Type and "Application Throughput (kbps)"
as the Field.
For a service area (EbNt) (UL) coverage prediction, 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.
6. 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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
8.2.10.3.4
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 241. You must
also select the network Layer or Carrier to be considered for the determination of best servers. Otherwise, you can
calculate the prediction for all layers or carriers.
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. Indoor losses are defined per frequency per
clutter class.
543
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.
5. Click the Display tab.
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
"Setting the Display Properties of Objects" on page 51.
6. 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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
8.2.10.3.5
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.
544
AT332_UMR_E0
In the following example, you will create a quality prediction showing BLER, for a user on foot, and with mobile internet access.
To create a quality prediction showing BLER for a user on foot, and with mobile internet access:
1. In the Network explorer, right-click the Predictions folder and select New Prediction from the context menu. The
Prediction Types dialog box appears.
2. Select Service Area Analysis (EbNt) (DL) and click OK. The Service Area Analysis (EbNt) (DL) Properties dialog box
appears.
3. Configure the parameters in the Properties dialog box as described in "UMTS Prediction Properties" on page 536.
4. On the Conditions tab, 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.
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 the network Layer or Carrier to be considered for the determination of best servers. Otherwise,
you can calculate the prediction for all layers or carriers
If you want the service area (EbNt) (DL) 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. Indoor losses are defined per frequency per
clutter class.
You can select the Bearer downgrading check box if you want the service area (EbNt) downlink 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.
5. Click the Display tab.
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 "Setting the Display Properties of Objects" on page 51.
6. 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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Atoll calculates for each pixel the DL traffic channel quality (EbNt) (provided when using the maximum traffic channel power
allowed). Then, it calculates the corresponding BLER value from the quality graph (BLER=f(DL EbNt)). The pixel is coloured if
the condition is fulfilled (i.e., if BLER is evaluated as being higher than the specified threshold).
The BLER is also used in the service area (DL) prediction (as described in "Studying Downlink and Uplink Service Areas (EbNt)" on page 542) in order to evaluate R99 peak RLC and
application throughputs.
8.2.10.3.6
545
4. On the Conditions tab, 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, and Service, as defined in "Service and User Modelling" on page 241. You must also select
the network Layer or Carrier to be considered for the determination of best servers. Otherwise, you can calculate the
prediction for all layers or carriers
You can also select the Indoor coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab.
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:
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:
For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
6. 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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
8.2.10.3.7
546
AT332_UMR_E0
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 241. You must
also select the network Layer or Carrier to be considered for the determination of best servers. Otherwise, you can
calculate the prediction for all layers or carriers.
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.
You can also select the Indoor coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab.
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 "Setting the Display Properties of Objects" on
page 51.
6. 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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
8.2.10.3.8
You must select a Terminal and a Service, as defined in "Service and User Modelling" on page 241. You must also select
the network Layer or Carrier to be considered for the determination of best servers. Otherwise, you can calculate the
prediction for all layers or carriers.
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.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab to specify the display parameters of the prediction as described in "UMTS Prediction Properties"
on page 536.
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 "Setting the
Display Properties of Objects" on page 51.
6. 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.
547
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
8.2.10.3.9
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 241. You must
also select the network Layer or Carrier to be considered for the determination of best servers. Otherwise, you can
calculate the prediction for all layers or carriers.
If you want the handoff status 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.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab.
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:
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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
548
AT332_UMR_E0
You must select a Mobility, as defined in "Service and User Modelling" on page 241. 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 the network Layer or Carrier to be considered for the determination of best serving cells. Otherwise, you can calculate the prediction for all layers or carriers.
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.
You can set the following parameters:
To model a DC-HSPA user: Select a DC-HSPA capable terminal as the Terminal and a BE or VBR Service with HSPA.
To model a MC-HSPA user: Select a MC-HSPA capable terminal as the Terminal and a BE or VBR Service with HSPA.
To model a DB-MC-HSPA user: Select a DB-MC-HSPA capable terminal as the Terminal, a BE or VBR Service with
HSPA.
For these configurations, selecting one specific carrier or one layer associated with one unique carrier is not suitable.
To display the global throughput, you have to select several carriers ("Best HSPA (All/Specific band)" as the carrier) or
layers associated with several carriers.
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.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab to specify the display parameters of the prediction as described in "UMTS Prediction Properties"
on page 536.
If you have selected "All" as the HSDPA radio bearer in the Conditions tab, you can set the following parameters:
The maximum DL A-DPCH quality relative to the EbNt threshold: Select "Max DL A-DPCH EbNt (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 relative to the EbNt threshold: Select "Max UL A-DPCH EbNt (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.
549
The HS-SCCH EcNt per HS-SCCH channel relative to the EcNt threshold: Select "HS-SCCH EcNt (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 bearer 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 relative to the EcNt threshold: Select "HS-PDSCH Ec/Nt" as the Field. Atoll calculates
the best HS-PDSCH EcNt on each pixel.
The channel quality indicator (CQI) relative 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 dialog box (see "Network Settings Properties" on
page 613).
If you are modelling an MC-HSPA user, the best carrier is determined using the best serving cell selection algorithm. The secondary carriers must belong to the same transmitter and are chosen among the adjacent carriers
according to the CQI. When two adjacent carriers are available, the one with the highest CQI value is selected. Atoll selects secondary cells as long as HSDPA carriers are available in the transmitter and the maximum number of
cells to which the user can simultaneously connect is not exceeded.
If you are modelling a DB-MC-HSPA user, the best carrier among all supported frequency bands is selected based
on the best serving cell selection algorithm. The secondary cells are taken in the same band as the best carrier (i.e.,
they belong to the same transmitter), as long as carriers are available. Then, if additional carriers are required and
if there are no more carriers available in this transmitter, Atoll selects the carriers in a transmitter using the second
frequency band. Within one frequency band, the secondary cells are first selected according to an adjacency criterion and then, according to the CQI value. When two adjacent carriers are available, Atoll takes the one with the
highest CQI value.
For MC-HSPA and DB-MC-HSPA users, all selected carriers are taken into consideration to calculate the throughputs.
The peak MAC throughput relative to the threshold: Select "Peak MAC Throughput (kbps)" as the Field. Atoll
calculates the peak MAC throughput from the transport block size of the selected HSDPA bearer.
The Effective MAC throughput relative to the threshold: Select "Effective MAC Throughput (kbps)" as the
Field. The Effective MAC throughput is calculated from the peak MAC throughput.
The peak RLC throughput relative to the threshold: Select "Peak RLC Throughput (kbps)" as the Field. Atoll
displays the peak RLC throughput that the selected HSDPA bearer can be supplied with. The peak RLC throughput is a characteristic of the HSDPA bearer.
The effective RLC throughput relative to the threshold: Select "Effective RLC Throughput (kbps)" as the Field.
Atoll calculates the effective RLC throughput from the peak RLC throughput.
The average effective RLC throughput relative to the threshold: Select "Average Effective RLC Throughput
(kbps)" as the Field.
The application throughput relative to the threshold: Select "Application Throughput (kbps)" as the Field.
Using the peak RLC throughput, 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.).
In order to be covered, VBR service users have to obtain an HSDPA bearer with a peak RLC throughput exceeding
their minimum throughput demands. When the peak RLC throughput of the best HSDPA bearer exceeds the user
maximum throughput demand, the HSDPA bearer is downgraded until the peak RLC throughput is lower than the
maximum throughput demand.
MC-HSPA users with VBR services are not covered if they cannot obtain the minimum throughput demand on their
best carrier.
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. If you are modelling a single-band or DB-MC-HSPA user (where n is the number of cells to which the
user is connected), the following throughputs are calculated for the n best carriers.
You can display the following results:
550
The average effective MAC throughput per user relative to the threshold: Select "Effective MAC Throughput
per User (kbps)" as the Field. Atoll calculates the average MAC throughput per user from the from the MAC
throughput of each user.
The average effective RLC throughput per user relative to the threshold: Select "Effective RLC Throughput
per User (kbps)" as the Field. Atoll calculates the average RLC throughput per user from the RLC throughput
of each user.
The average application throughput per user relative to the threshold: Select "Application Throughput per
User (kbps)" as the Field. Using the peak RLC throughput, the BLER, the HSDPA service scaling factor, and the
AT332_UMR_E0
throughput offset, Atoll calculates the average application throughput per user 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 peak RLC throughput 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:
Total transmitted power = 50% of the maximum power (i.e, 40 dBm if the maximum power is set to 43 dBm)
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
properties, see "Setting the Display Properties of Objects" on page 51.
6. 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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
You must select a Mobility, as defined in "Service and User Modelling" on page 241. 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 the network Layer or Carrier to be considered for the determination of best servers. Otherwise,
you can calculate the prediction for all layers or carriers.
You can set the following parameters:
To model a DC-HSPA user: Select a DC-HSPA capable terminal as the Terminal and a BE or VBR Service with HSPA.
551
To model a MC-HSPA user: Select a MC-HSPA capable terminal as the Terminal and a BE or VBR Service with HSPA.
To model a DB-MC-HSPA user: Select a DB-MC-HSPA capable terminal as the Terminal, a BE or VBR Service with
HSPA.
For these configurations, selecting one specific carrier or one layer associated with one unique carrier is not suitable.
To display the global throughput, you have to select several carriers ("Best HSPA (All/Specific band)" as the carrier) or
layers associated with several carriers.
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.
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.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
When no value is defined in the Cells table, Atoll uses the following default values for input parameters:
5. Click the Display tab to specify the display parameters of the prediction as described in "UMTS Prediction Properties"
on page 536. You can set parameters to display the following results:
The required E-DPDCH EcNt relative to the threshold: Select "Required E-DPDCH EcNt (dB)" as the Field. Atoll
selects the best HSUPA bearer whose required E-DPDCH EcNt does not exceed the maximum E-DPDCH EcNt
allowed. The required E-DPDCH EcNt 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 EcNt.
The peak MAC Throughput relative to the threshold: Select "Peak MAC Throughput (kbps)" as the Field. Atoll calculates the peak MAC throughput from the transport block size of the selected HSUPA bearer.
The peak RLC throughput relative to the threshold: Select "Peak RLC Throughput (kbps)" as the Field. Atoll displays the peak RLC throughput that the selected HSUPA bearer can supply. The peak RLC throughput 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 peak RLC throughput, 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).
To be connected to two carriers in the uplink, DC-HSPA, MC-HSPA and DB-MC-HSPA users must first initiate a connection to several carriers in the downlink. The best carrier is the one selected in the downlink. The secondary carrier
belongs to the same transmitter; it is the second best carrier among the adjacent carriers selected in the downlink. All
selected carriers are taken into consideration to calculate the throughputs.
In order to be covered, VBR users have to obtain an HSUPA bearer with a peak RLC throughput exceeding their minimum throughput demands. When the peak RLC throughput of the best HSUPA bearer exceeds the user maximum
throughput demand, the HSUPA bearer is downgraded until the peak RLC throughput is lower than the maximum
throughput demand.
DC-HSPA, MC-HSPA and DB-MC-HSPA users with VBR services are not covered if they cannot obtain the minimum
throughput demand on their best carrier.
For information on selecting the best bearer, see the Technical Reference Guide. For information on defining display
properties, see "Setting the Display Properties of Objects" on page 51.
552
AT332_UMR_E0
6. 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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
8.2.10.6.1
8.2.10.6.2
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 8.6).
8.2.10.6.3
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 91.
553
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 "Geographic Export Zone" on page 68.
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, 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 210.
8.2.10.7.1
) in the Radio Planning toolbar. The Point Analysis window opens and the pointer
changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and the
current position. You can move the receiver on the map ("Moving the Receiver on the Map" on page 203).
2. At the top of the Point Analysis window, select the Reception view (see Figure 8.7).
The predicted signal level from the 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. The name of the transmitter is followed by
the carrier number (between parentheses). 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. In the Reception view, select the carrier to be analysed. You can make the prediction for a specific carrier or select
"Best (All Bands)" to consider the best carrier of all bands.
) to display the Calculation Options dialog box and change the following:
Change the X and Y coordinates to change the current position of the receiver.
Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. For more information, see "Taking Shadowing into Account in Point Analyses" on page 204.
Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class. For more information, see "Taking Indoor Losses into Account" on page 203.
5. In the Reception view toolbar, you can use the following tools:
554
) to copy the content of the view and paste it as a graphic into a graphic editing or word-
AT332_UMR_E0
6. To get the details about the received signal levels and quality in the form of a table, select the Details view (see
"Obtaining Numerical Values of Signal Levels and Signal Quality" on page 556).
7. Click the Point Analysis button (
You can display a point analysis that uses the settings from an existing prediction by
right-clicking the prediction in the Network explorer and selecting Open Point Analysis
from the context menu.
8.2.10.7.2
) in the Radio Planning toolbar. The Point Analysis window opens and the pointer
changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and the
current position. You can move the receiver on the map ("Moving the Receiver on the Map" on page 203).
2. Select the AS Analysis view.
3. Select "Cells Table" from the Loads list.
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 Layer or Carrier to be considered for the determination of best servers. Otherwise, you can make the
AS analysis for all layers or carriers.
b. Select the same Terminal, Service, and Mobility studied in the coverage prediction.
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 (
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. For more
information, see "Taking Shadowing into Account in Point Analyses" on page 204.
Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class. For more information, see "Taking Indoor Losses into Account" on page 203.
555
The pilot quality (EcI0) of all cells using the selected carrier (the colour of the bar corresponds to the colour of the
transmitter on the map).
The thresholds of the active set (EcI0 threshold, best server active set threshold). The portion of the graph with
the grey background indicates the cells in the active set.
The pilot and the availability of service on UL, DL, HSDPA, and HSUPA.
If there is at least one successful connection (for pilot, DL, UL, HSDPA, or HSUPA), double-clicking the icons in the righthand frame will open a dialog box with additional information.
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.
7. In the AS Analysis view toolbar, you can use the following tools:
Click the Report button ( ) to generate a report that contains the information from the Point Analysis window.
The Analysis Report dialog box opens.
) to copy the content of the view and paste it as a graphic into a graphic editing or word-
You can display a point analysis that uses the settings from an existing prediction by
right-clicking the prediction in the Network explorer and selecting Open Point Analysis
from the context menu.
8.2.10.7.3
556
AT332_UMR_E0
) in the Radio Planning toolbar. The Point Analysis window opens and the pointer
changes (
) to represent the receiver. You can move the receiver on the map ("Moving the Receiver on the Map"
on page 203).
2. Select the Details view.
3. Select "Cells table" from the Loads list.
4. If you are making a detailed analysis to verify a coverage prediction, you can recreate the conditions of the coverage
prediction:
a. Select the same Terminal, Mobility, and Service studied in the coverage prediction.
b. Select the Layer or Carrier to be considered for the determination of best servers. Otherwise, you can make the
analysis for all layers or carriers.
c. Click the Options button (
i.
Edit the X and Y coordinates to change the present position of the receiver.
ii. Select the Shadowing taken into account check box and enter a Cell edge coverage probability. For more information, see "Taking Shadowing into Account in Point Analyses" on page 204.
iii. Select the Indoor coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class. For more information, see "Taking Indoor Losses into Account" on page 203.
iv. Click OK in the Calculation Options dialog box.
5. Move the pointer over the map to make a detailed analysis for the current location of the pointer. The Details view
displays the following information in the form of a table:
Transmitter: The name of the transmitter from which the received signal levels are displayed. The cells are listed
in decreasing order of RSCP.
Distance (m): The distance from the transmitter to the current location of the pointer on the map.
Scrambling Code: The scrambling code of the transmitter.
Path Loss (dB): The path loss from the transmitter to the current location of the pointer on the map.
RSCP (dBm): The received pilot signal level from the transmitter to the current location of the pointer on the map.
Ec/Io (dB): The Ec/Io from the transmitter to the current location of the pointer on the map.
DL Eb/Nt (dB): The downlink Eb/Nt from the transmitter to the current location of the pointer on the map.
UL Eb/Nt (dB): The uplink Eb/Nt from the transmitter to the current location of the pointer on the map.
6. In the Details view toolbar, you can use the following tools:
8.2.10.8.1
557
Load conditions: Select "(Cells table)" to calculate the point analysis using the load conditions defined in the cells
table. Select a simulation or a group of simulations to calculate the point analysis using the load conditions calculated
by Monte Carlo simulations.
Carrier: Select the carriers for which you want to run the analysis or select "Best." The best carrier depends on the cell
selection method.
Shadowing taken into account: Select this option to consider shadowing in the point analysis. For more information,
see "Modelling Shadowing" on page 623. If you select this option, you can change the Cell edge coverage probability.
Indoor coverage: Select this option to consider indoor losses. Indoor losses are defined per frequency per clutter class.
Bearer Downgrading: Select this check box if you want to permit bearer downgrading.
Position Id: The indexes of the points used for the point analysis.
X and Y: The coordinates of the points used for the point analysis.
Height (m): The height of the points used for the point analysis.
Service: The services assigned to the points used for the point analysis.
Terminal: The terminals assigned to the points used for the point analysis.
Mobility: The mobility types assigned to the points used for the point analysis.
8.2.10.8.2
Importing a list of points from an external file: Click the Actions button and select Import Table from the menu to
open the Open file dialog box. In this dialog box, select a TXT or CSV file containing a list of points and click Open.
For more information on importing data tables, see "Importing Tables from Text Files" on page 88.
Importing a list of points from a fixed subscriber traffic map: Click the Actions button and select Import from Fixed
Subscribers from the menu to open the Fixed Subscribers dialog box. In this dialog box, select one or more existing
fixed subscriber traffic maps and click OK.
Copying a list of points from an external file.
Creating points in the list by editing the table: Add new points by clicking the New Row icon ( ) and entering X
and Y coordinates as well as a service, a terminal, and a mobility.
The list of points must have the same coordinate system as the display coordinate system
used in the Atoll document. For more information on coordinate systems, see "Setting a
Coordinate System" on page 41.
558
AT332_UMR_E0
It is also possible to leave the Points tab empty and add points to the analysis on
the map using the mouse once the point analysis item has been created. To add
points on the map using the mouse, right-click the point analysis item to which you
want to add points, and select Add Points from the context menu. The mouse
pointer changes to point creation mode (
want to add. Press ESC or click the Pointer button ( ) in the Map toolbar to finish
adding points.
You can also export the list of point from a point analysis to ASCII text files (TXT and
CSV formats) and MS Excel XML Spreadsheet files (XML format) by selecting
Actions > Export Table. For more information on exporting table data, see
"Exporting Tables to Text Files and Spreadsheets" on page 86.
4. On the Display tab, specify how to display point analysis results on the map according to any input or calculated
parameter. For more information on defining display properties, see "Setting the Display Properties of Objects" on
page 51.
5. Once you have defined the point analysis parameters, you can calculate it immediately or you can save it and calculate
it later:
Calculate: Click Calculate to save the point analysis and calculate it immediately.
OK: Click OK to save the point analysis without calculating it. You can calculate it later by opening the point analysis
properties and clicking the Calculate button.
Once Atoll has finished calculating the point analysis, the results are displayed in the map window. You can also access the
analysis results in a table format. For more information, see "Viewing Point Analysis Results" on page 559.
You can also organise point analyses in folders under the Multi-point Analysis folder by creating folders under the Multi-point
Analysis folder in the Network explorer. Folders may contain one or more point analyses items. You can move point analyses
items from one folder to another and rename folders.
8.2.10.8.3
Position Id: The indexes of the points used for the point analysis.
X and Y: The coordinates of the points used for the point analysis.
Height (m): The height of the points used for the point analysis.
Service: The services assigned to the points used for the point analysis.
Terminal: The terminals assigned to the points used for the point analysis.
Mobility: The mobility types assigned to the points used for the point analysis.
Cell: Names of the potential serving cells.
Distance (m): Distances from the potential serving cells.
Path Loss (dB): Path losses to the potential serving cells.
RSCP (dBm): Received signal code powers from to the potential serving cells.
Ec/Io (dB): Ec/Io from to the potential serving cells.
DL Eb/Nt (dB): Downlink Eb/Nt corresponding to the potential serving cells.
UL Eb/Nt (dB): Uplink Eb/Nt corresponding to the potential serving cells.
Scrambling Code: Scrambling codes of the potential serving cells.
559
Figure 8.10: UMTS intra-carrier handover area between reference cell and potential neighbour
Figure 8.11: UMTS inter-carrier handover area between reference cell and potential neighbour
In this section, only the concepts that are specific to automatic neighbour allocation in UMTS networks are explained.
For more information on neighbour planning, see "Neighbour Planning" on page 223
8.2.11.1.1
When it is cleared, only the defined Distance will be used to allocate neighbours to a reference cell.
When it is selected, click Define to open the Coverage Conditions dialog box and specify the following settings:
560
Resolution: Enter the resolution to be used to calculate cells coverage areas during automatic neighbour allocation.
Global min RSCP: Enter the minimum RSCP to be provided by the reference cell and the potential neighbour. Atoll
uses the highest value between the Global min RSCP and the following:
AT332_UMR_E0
8.2.11.1.2
If Global min RSCP is not defined, Atoll uses the Min RSCP in individual cells properties
If Global min RSCP is not defined and no Min RSCP is available in a cells properties, Atoll uses the Default min
Pilot RSCP threshold defined on the Calculation Parameters tab of the Network Settings Properties dialog
box.
Min EcIo: Enter the minimum EcIo 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.
AS Threshold: Enter the maximum difference of EcI0 between reference cell A and potential neighbour cell B in
the overlapping area.
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.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this check box to take indoor losses into acccount in calculations. Indoor losses are
defined per frequency per clutter class.
When it is cleared, only the defined Distance will be used to allocate neighbours to a reference cell.
When it is selected, click Define to open the Coverage Conditions dialog box and specify the following settings:
Resolution: Enter the resolution to be used to calculate cells coverage areas during automatic neighbour allocation.
Global min RSCP: Enter the minimum RSCP to be provided by the reference cell and the potential neighbour. Atoll
uses the highest value between the Global min RSCP and the following:
If Global min RSCP is not defined, Atoll uses the Min RSCP in individual cells properties
If Global min RSCP is not defined and no Min RSCP is available in a cells properties, Atoll uses the Default min
Pilot RSCP threshold defined on the Calculation Parameters tab of the Network Settings Properties dialog
box.
Min EcIo: Enter the minimum EcIo 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.
Handover margin: Enter the maximum difference of EcIo between reference cell A and potential neighbour cell B
in the overlapping area. You can select whether Atoll should use a Global value of the handover margin for all
cells, or the handover margins Defined per 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.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this check box to take indoor losses into account in calculations. Indoor losses are defined
per frequency per clutter class.
Co-site cells as neighbours: cells located on the same site as the reference cell will automatically be considered as
neighbours. A cell with no antenna cannot be considered as a co-site neighbour.
Adjacent cells as neighbours (Intra-carrier Neighbours tab): cells that are adjacent to the reference cell will automatically be considered as neighbours. A cell is considered adjacent if there is at least one pixel in the reference cells coverage area where the potential neighbour cell is the best server, or where the potential neighbour cell is the second
best server in the reference cells active set.
Adjacent layers as neighbours: cells that are adjacent to the reference cell across layers will be automatically considered as neighbours.
Symmetric relations: Select this check box if you want the neighbour relations to be reciprocal, i.e. any reference cell
is a potential neighbour of all the cells that are its neighbours.
Exceptional pairs: Select this check box to force the neighbour relations defined in the Intra-technology Exceptional
pairs table. For information on exceptional pairs, see "Exceptional Pairs" on page 223.
561
Cause
Description
When
Distance
Coverage
Co-Site
Adjacent
(intra-carrier)
Adjacent layer
Symmetry
Exceptional Pair
Exceptional pairs
is selected
Existing
562
AT332_UMR_E0
A 16 + B 16 + C
For example, the hexadecimal value "3Fh" would be calculated as shown below:
2
0 16 + 3 16 + 15 = 63
3. Click in another cell of the table to create the new domain and add a new blank row to the table.
4. Double-click the domain to which you want to add a group. The domains Properties dialog box appears.
5. Under Groups, enter the following information for each group you want to create.
6. Click in another cell of the table to create the new group and add a new blank row to the table.
563
To create a pair of cells that cannot have the same scrambling code:
1. In the Network explorer, right-click the Transmitters folder, and select Primary Scrambling Codes > Exceptional Pairs.
The Exceptional Separation Constraints table appears.
For information on working with data tables, see "Data Tables" on page 75.
2. In the row marked with the New Row icon (
), 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.
3. Click in another cell of the table to create the new exceptional pair and add a new blank row to the table.
8.2.12.4.1
Under Intra-technology Neighbours, you can set the constraint violation cost for 1st Order, 2nd Order, and 3rd
Order neighbours.
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.
8.2.12.4.2
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.
564
AT332_UMR_E0
3. Select Primary Scrambling Codes > Automatic Allocation. The Primary Scrambling Codes dialog box 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 560.
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 609
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 dialog box, you can change the following parameters:
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 EcI0 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.
EcI0 Margin: Enter the maximum difference of EcI0 between reference cell A and possible neighbour cell B
in the area with overlapping coverage.
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.
Indoor losses are defined per frequency per clutter class.
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 dialog box 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.
565
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.
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 104.
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.
8.2.12.4.3
566
AT332_UMR_E0
Transmitters and cells involved in a scrambling code collision are not necessarily
located inside the Focus Zone or Computation Zone, when any is defined.
No. of Codes per Cluster: Enter the number of scrambling codes per cluster.
Neighbours: Select this box 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: 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: 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: Select this box to 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: Select this box to 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: Select this box to 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: Select this box to check for and list base stations whose cells have scrambling codes coming
from more than one cluster.
Distance: Select this box and set a reuse distance to 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 dialog box. 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: Select this box to 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.
8.2.12.6.1
567
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 539.
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 Find on Map window.
8.2.12.6.2
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 dialog box.
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 dialog box.
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 dialog box.
5. Click OK.
For information on display options, see "Setting the Display Properties of Objects" on page 51.
8.2.12.6.3
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.
568
AT332_UMR_E0
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
10. Click OK to save your changes and close the Group dialog box.
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.
8.2.12.6.4
8.2.12.6.5
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
Under Display Configuration, you can create a Filter to select which sites to display in the results. You can also display
the results grouped in the Network explorer 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 99;
for information on grouping, see "Advanced Grouping of Data Objects" on page 96; for information on sorting, see
"Advanced Sorting" on page 98.
6. Click the Conditions tab. 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.
569
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 241. You must
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.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
7. Click the Display tab.
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 "Setting the Display
Properties of Objects" on page 51.
You can also set parameters to display the following results:
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.
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 Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
8.2.12.6.6
) to display the Calculation Options dialog box. 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, and, select
"EcI0" from the Shadowing Margin list.
Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class.
570
AT332_UMR_E0
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. 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.
7. Click the Point Analysis button (
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 615.
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 Services" on page 241.
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 transmitters. EcI0
requirements and EbNt targets per radio bearer and per link (uplink or downlink) are largely dependent on mobile
speed. For information on creating a mobility type, see "Modelling Mobility Types" on page 247.
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 Terminals" on page 249.
571
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 can 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 bearer users and an additional loop modelling noise rise
scheduling for HSUPA bearer users. The power control simulation algorithm is described in "The Power Control Simulation Algorithm" on page 572.
This section explains the specific mechanisms that are used to calculate UMTS traffic simulations. For information on working
with traffic simulations in Atoll, see "Simulations" on page 265
572
AT332_UMR_E0
Either as a single-cell HSPA user if the best carrier and all the other carriers to
which he is connected are on two different frequency bands.
Or as a DC-HSPA user if the best carrier and at least one of the other carriers are in
the same frequency band.
In the HSUPA portion, Atoll processes all users as single-cell HSPA users.
Therefore, we will only differentiate single-cell and DC-HSPA users in the next sections.
573
On the downlink, either the pilot signal level is lower than the defined minimum RSCP threshold or the pilot quality
is not high enough (no cell in the user active set): the status is "EcI0 < (EcI0)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"
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"
[
Figure 8.13: HSDPA bearer selection
The HSDPA and HS-SCCH powers of a cell are evaluated before calculating HS-PDSCH EcNt. 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 attain the HS-SCCH EcNt 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 EcNt and, from that, the corresponding CQI (from the graph CQI=f(HS-PDSCH EcNt) 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. For BE service users, the selected HSDPA bearer is the best HSDPA bearer that the user
can obtain.
For VBR service users, Atoll downgrades the HSDPA bearer to a lower one if the associated peak RLC throughput exceeds the
maximum throughput demand defined for the service. Downgrading occurs until the peak RLC throughput of the selected
HSDPA bearer is lower than the maximum throughput demand. Additionally, the selected HSDPA bearer must provide a peak
RLC throughput higher than the minimum throughput demand defined for the service.
574
AT332_UMR_E0
For CBR 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
peak RLC throughput higher than the minimum throughput demand defined for the service.
Two CQI values are calculated for DC-HSPA users, one for each carrier, and two HSDPA bearers are determined.
CBR service users have the highest priority and are processed first, in the order established during the generation of the user
distribution. The scheduler manages 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 peak
RLC throughput higher than the minimum throughput demand defined for the service. To achieve the highest cell capacity,
the scheduler can hold several packets over a TTI (Transmission Time Interval). Atoll models this "intelligent scheduling" by
allowing several CBR 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 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, CBR service users can be connected or rejected. They are rejected if:
The maximum number of HSDPA bearer users per cell is exceeded: the status is "HSDPA Scheduler Saturation"
The lowest HSDPA bearer they can obtain does not provide a peak RLC throughput higher than the minimum
throughput demand: 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 CBR service users, Atoll processes the remaining HSDPA bearer users (i.e., HSDPA VBR and BE service
users, and HSPA VBR and BE service users), without exceeding the maximum number of users within each cell.
VBR service users have the highest priority and are managed before BE service users. For each type of service, 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 bearer users defined for the cell minus
the number of CBR 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 bearer users defined for the
cell minus the number of CBR 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 CBR service users have been served) is shared between them. 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 throughput.
For VBR services, 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, VBR service users can be connected or rejected. They are rejected if:
The maximum number of HSDPA bearer users per cell is exceeded: the status is "HSDPA Scheduler Saturation"
The lowest HSDPA bearer they can obtain does not provide a peak RLC throughput higher than the minimum
throughput demand: the status is "HSDPA Resource Saturation"
There are no more HS-SCCH channels available: the status is "HS-SCCH Channels 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"
For BE services, 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.
575
At this point, BE service users can be connected, rejected, or delayed. They are rejected if the maximum number of HSDPA
bearer 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"
The maximum number of HSUPA bearer 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 peak RLC throughput higher than the minimum throughput demand: 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 VBR service users. For these users, the list of compatible bearers is restricted to HSUPA bearers that
provide a peak RLC throughput between the maximum and the minimum throughput demands. Atoll performs a new noise
rise scheduling and distributes the remaining cell load factor available after all CBR service users have been served. From this
value, Atoll selects an HSUPA bearer for each VBR service user.
Finally, Atoll carries out radio resource control on VBR 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,
576
AT332_UMR_E0
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, VBR service users can be either connected, or rejected. They are rejected if:
The maximum number of HSUPA bearer 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 peak RLC throughput higher than the minimum throughput demand: 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 BE service users. It performs a new noise rise scheduling and distributes the remaining cell load factor
available after all CBR and VBR service users have been served. From this value, Atoll selects an HSUPA bearer for each BE
service user. Then, Atoll checks that each BE service user has obtained the average requested throughput (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, BE service users can be either connected, or rejected. They are rejected if:
The maximum number of HSUPA bearer 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 HSPA users
directly; it downgrades them first.
The R99 to R99 bearer downgrading occurs when:
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.
577
8.3.2.2.1
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 throughputs 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 throughputs) is given.
The Sites tab: The Sites tab contains the following information per site:
578
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
uplink and downlink.
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.
AT332_UMR_E0
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 peak RLC throughput to be added to the peak RLC throughput. The total value corresponds to the Iub backhaul throughput required by the HSDPA bearer users 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 Throughput (kbps): The Instantaneous HSDPA Throughput (kbps).
Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps).
DL and UL Throughput for Each Service: The throughput in kbitss 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 Losses (dB): The reception losses as defined in the transmitter properties.
Transmission Losses (dB): The transmission losses 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.
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 dialog box.
Max DL Load (% Pmax): The maximum percentage of power that the cell can use. It is defined either in the cell
properties, or in the simulation creation dialog box.
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 dialog
box).
DL Load Factor (%): The DL load factor of the cell i corresponds to the ratio (DL average interference [due to transmitter signals on the same and adjacent carriers] for terminals in the transmitter 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).
579
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.).
Min. HSDPA Peak RLC Throughput (kbps): The minimum HSDPA peak RLC throughput corresponds to the lowest
of peak RLC throughputs obtained by HSDPA bearer users connected to the cell. For DC-HSPA users, this is the
lower of the two minimum HSDPA peak RLC throughputs.
Max HSDPA Peak RLC Throughput (kbps): The maximum HSDPA peak RLC throughput corresponds to the highest
of peak RLC throughputs obtained by HSDPA bearer users connected to the cell. For DC-HSPA users, this is the
higher of the two maximum HSDPA peak RLC throughputs.
Avg. Instantaneous HSDPA Throughput (kbps): The average instantaneous HSDPA throughput (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 DC-HSPA users is the sum of their HSDPA throughputs on both cells.
Instantaneous HSDPA Throughput (kbps): The instantaneous HSDPA throughput (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 throughput of DC-HSPA users is the sum of their HSDPA throughputs on both cells.
Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps) that the cell
carries. The HSDPA throughput of DC-HSPA 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. DC-HSPA users are considered once in each cell they are connected to.
No. of HSDPA Users: The number of connected and delayed HSDPA bearer users. DC-HSPA users are considered
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 (11), softer (12), soft (22), softer-soft
(23) and soft-soft (33) 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.
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 266, you select either "Standard information about mobiles" or
"Detailed information about mobiles" under Information to Retain.
580
AT332_UMR_E0
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. DC-HSPA 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 Throughput (kbps): For R99 users, the DL and UL total requested throughputs correspond to the DL and UL peak throughputs of the R99 bearer associated to the service.
For HSDPA users, the uplink requested throughput corresponds to the peak throughput of ADPCH R99 radio bearer and the downlink requested throughput is the sum of the ADPCH radio bearer peak throughput and the peak
RLC throughput(s) that the selected HSDPA radio bearer(s) can provide. Here, the 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 HSPA users, the uplink requested throughput is equal to the sum of the ADPCH-EDPCCH radio bearer peak
throughput and the peak RLC throughput of the requested HSUPA radio bearer. The requested HSUPA radio bearer is selected from the HSUPA bearers compatible with the user equipment. Here, the 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 requested throughput is the sum of the ADPCH-EDPCCH radio bearer peak
throughput and the peak RLC throughput(s) that the requested HSDPA radio bearer(s) can provide.
DL and UL Total Obtained Throughput (kbps): For R99 service users, the obtained throughput is the same as the
requested throughput if he is connected without being downgraded. Otherwise, the obtained throughput is lower
(it corresponds to the peak throughput of the selected R99 bearer). If the user is rejected, the obtained throughput
is zero.
In the downlink, HSDPA bearer users can be connected to a single cell or to two cells of the same transmitter when
the user has a DC-HSPA-capable terminal and when the transmitter supports the multi-cell HSDPA mode.
For a single-carrier HSDPA service user connected to an HSDPA bearer, the downlink obtained throughput corresponds to the instantaneous throughput; this is the sum of the A-DPCH radio bearer peak throughput and the peak
RLC throughput provided by the selected HSDPA radio bearer after scheduling and radio resource control. If the
user is delayed (he is only connected to an R99 radio bearer), downlink obtained throughput corresponds to the
downlink peak throughput of the ADPCH 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 downlink obtained throughput is zero.
For a dual-carrier HSDPA service user connected to two HSDPA bearers, the downlink obtained throughput corresponds to the instantaneous throughput; this is the sum of the peak throughput provided by the A-DPCH radio
bearer in the anchor cell and the peak RLC throughputs provided by the selected HSDPA radio bearers after scheduling and radio resource control. If the user is connected to one cell and delayed in the other cell, the downlink
obtained throughput is the sum of the peak throughput provided by the A-DPCH radio bearer in the anchor cell
and the peak RLC throughput provided by the selected HSDPA radio bearer after scheduling and radio resource
control. If the user is delayed in the two cells (he is only connected to an R99 radio bearer in the anchor cell), the
downlink obtained throughput corresponds to the downlink peak throughput of the ADPCH radio bearer in the
anchor cell. 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 downlink obtained throughput is zero.
In the uplink, HSDPA service users can only have a single-carrier connection. When the user is either connected or
delayed, the uplink obtained throughput corresponds to the uplink peak throughput of the ADPCH radio bearer.
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 obtained throughput is zero.
For single-carrier HSPA VBR and BE service users, on downlink, if the user is connected to an HSDPA bearer, the
downlink obtained throughput corresponds to the instantaneous throughput. The instantaneous throughput is
the sum of the ADPCH-EDPCCH radio bearer peak throughput and the peak RLC throughput provided by the selected HSDPA radio bearer after scheduling and radio resource control. If the user is delayed, the downlink obtained throughput corresponds to the downlink peak throughput of ADPCH-EDPCCH radio bearer. If the user is
rejected, the downlink obtained throughput is "0".
For dual-carrier HSPA VBR and BE service users connected to two HSDPA bearers, the downlink obtained throughput corresponds to the instantaneous throughput; this is the sum of the peak throughput provided by the ADPCHEDPCCH radio bearer in the anchor cell and the peak RLC throughputs provided by the selected HSDPA radio bearers after scheduling and radio resource control. If the user is connected to one cell and delayed in the other cell,
581
the downlink obtained throughput is the sum of the peak throughput provided by the ADPCH-EDPCCH radio bearer in the anchor cell and the peak RLC throughput provided by the selected HSDPA radio bearer after scheduling
and radio resource control. If the user is delayed in the two cells (he is only connected to an R99 radio bearer in
the anchor cell), the downlink obtained throughput corresponds to the downlink peak throughput of the ADPCHEDPCCH radio bearer in the anchor cell. Finally, if the user is rejected, the downlink obtained throughput is zero.
In uplink, HSPA VBR and BE service users can only have a single-carrier connection. When the user is connected to
an HSUPA bearer, the uplink obtained throughput is the sum of the ADPCH-EDPCCH radio bearer peak throughput
and the peak RLC throughput provided by the selected HSUPA radio bearer after noise rise scheduling. If the user
is rejected, the uplink obtained throughput is zero.
For a connected HSPA CBR service user, the uplink and downlink total obtained throughputs are the sum of the
ADPCH-EDPCCH radio bearer peak throughput and the minimum throughput demand defined for the service. If
the user is rejected, the uplink and downlink total obtained throughputs 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, 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 HSDPA and HSPA users only), the status is "HSDPA delayed".
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/Io AS1, AS2, AS3, AS4, (dB): EcIo is given in a separate column for each cell in the active set. The Ec/Io AS 1
column lists the Ec/Io 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 266, you select "Detailed information about mobiles" under Information to Retain:
DL and UL Requested Peak RLC Throughputs (kbps): Downlink and uplink requested peak RLC throughputs are
not calculated for R99 users.
For HSDPA users, the uplink peak RLC throughput is not calculated and the downlink requested peak RLC throughput is the throughput that the selected HSDPA radio bearer(s) can provide.
For HSPA users, the requested uplink peak RLC throughput is the throughput of the requested HSUPA radio bearer.
The requested HSUPA radio bearer is selected from the HSUPA bearers compatible with the user equipment. Here,
the 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. If the user is connected to one or two HSDPA bearers
in the downlink, the downlink requested peak RLC throughput is the throughput that the requested HSDPA radio
bearer(s) can provide. The requested HSDPA radio bearer is determined as explained in the previous paragraph.
DL and UL Obtained Peak RLC Throughput (kbps): Downlink and uplink obtained peak RLC throughputs are not
calculated for R99 users.
For HSDPA users connected to one or two HSDPA bearers, the uplink obtained peak RLC throughput is not calculated, and the downlink obtained peak RLC throughput is the throughput provided by the selected HSDPA radio
bearer(s) after scheduling and radio resource control.
For connected HSPA BE and VBR service users, on uplink, if the user is connected to an HSUPA bearer, the obtained
uplink peak RLC throughput is the throughput provided by the selected HSUPA radio bearer after noise rise scheduling. On downlink, if the user is connected to one or two HSDPA bearers, the downlink obtained peak RLC
throughput is the throughput provided by the selected HSDPA radio bearer(s) after scheduling and radio resource
control.
For a connected HSPA CBR service user, the uplink and downlink obtained peak RLC throughputs are the uplink
and downlink minimum throughput demands defined for the service.
582
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 throughput (i.e.,
the DL obtained throughput), 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 throughput.
Required HSDPA Power (dBm): The required HSDPA power is the HSDPA power required to provide the HSDPA
bearer user with the downlink requested throughput. 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.
AT332_UMR_E0
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 throughput, 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
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 266, you select "Detailed information about
mobiles" under Information to Retain.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
583
8.3.2.2.2
The parameters related to the clutter classes, including the default values.
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 throughputs 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 throughputs) is given.
Results: Under Results, you will find data on the connection results:
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:
584
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
uplink and downlink.
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.
AT332_UMR_E0
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 peak RLC throughput to be added to the peak RLC throughput. 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 Throughput (kbps): The Instantaneous HSDPA Throughput (kbps).
Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps).
DL and UL Throughput for Each Service: The throughput in kbitss 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 Losses (dB): The reception losses as defined in the transmitter properties.
Transmission Losses (dB): The transmission losses 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.
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 dialog box.
Max DL Load (% Pmax): The maximum percentage of power that the cell can use. It is defined either in the cell
properties, or in the simulation creation dialog box.
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 dialog
box).
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 transmitter signals on the same carrier] for terminals in the transmitter 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
585
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 throughput (i.e.,
the DL obtained throughput), the BLER, the HSDPA service scaling factor and the throughput offset.
Min. HSDPA Peak RLC Throughput (kbps): The minimum HSDPA peak RLC throughput corresponds to the lowest
of peak RLC throughputs obtained by HSDPA bearer users connected to the cell. For DC-HSPA users, this is the
lower of the two minimum HSDPA peak RLC throughputs.
Max HSDPA Peak RLC Throughput (kbps): The maximum HSDPA peak RLC throughput: It corresponds to the
highest of peak RLC throughputs obtained by HSDPA bearer users connected to the cell. For DC-HSPA users, this
is the higher of the two maximum HSDPA peak RLC throughputs.
Avg. Instantaneous HSDPA Throughput (kbps): The average instantaneous HSDPA throughput (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 DC-HSPA users is the sum of their HSDPA throughputs on both cells.
Instantaneous HSDPA Throughput (kbps): The instantaneous HSDPA throughput (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 throughput of DC-HSPA users is the sum of their HSDPA throughputs on both cells.
Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps) that the cell
carries. The HSDPA throughput of DC-HSPA 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. DC-HSPA users are considered 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. DCHSPA users are considered 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 (11), softer (12), soft (22), softer-soft
(23) and soft-soft (33) 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:
586
AT332_UMR_E0
The parameters related to the clutter classes, including the default values.
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 can be saturated.
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 (
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.
587
To move the pointer again, click the point analysis pointer on the map and drag it to a new position.
10. Click the Point Analysis button (
Handoff Zones (DL): For information on making a Handoff Zones (DL), see "Making a Handoff Status Coverage Prediction" on page 548.
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 545.
Pilot Pollution Analysis (DL): For information on making a coverage by pilot polluter, see "Studying Pilot Pollution"
on page 546.
Pilot Quality Analysis (DL): For information on making a pilot quality analysis, see "Studying Pilot Signal Quality"
on page 541.
Service Area Analysis (Eb/Nt) (DL): For information on making a coverage prediction on the downlink service area,
see "Studying Downlink and Uplink Service Areas (EbNt)" on page 542.
Service Area Analysis (Eb/Nt) (UL): For information on making a coverage prediction on the uplink service area,
see "Studying Downlink and Uplink Service Areas (EbNt)" on page 542.
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 543.
HSDPA Quality and Throughput Analysis (DL): For information on making an HSDPA coverage prediction, see
"HSDPA Coverage Predictions" on page 549.
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 (UL): For information on making an HSUPA coverage prediction, see
"HSUPA Coverage Predictions" on page 551.
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:
1. Click the Conditions tab.
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:
588
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.
AT332_UMR_E0
You can also create the following objectives from the context menu of Objectives in the left-hand pane of the Objectives tab:
HSDPA EcNt
UMTS RSSI
UMTS Pilot Pollution
UMTS Soft Handover
UMTS 1st-Nth Difference
HSDPA RLC Peak Rate
Custom Coverage
You define the optimisation objectives using the Objectives tab of the ACP Setup dialog box. For information on setting objective parameters, see "Setting Objective Parameters" on page 1329.
589
RSCP
EcIo
Overlap
Best Server Distance
HSDPA EcNt
1st-2nd Difference
1st-Nth Difference
RSSI
HSDPA RLC Peak Rate
If you base the evaluation of a qualiy analysis prediction on a calculated Atoll prediction, ACP will use the display settings of the calculated Atoll prediction in the
qualiy analysis prediction calculated for that objective.
If you saved the display settings of a qualiy analysis prediction as defaults, or if you
are using a configuration file for ACP, these display settings will be used by default
and will override the display settings of the calculated Atoll prediction. For more
information on changing the display settings of a quality analysis prediction, see
"Changing the Display Properties of ACP Predictions" on page 1379.
590
Base prediction settings on > "HSDPA Quality and Throughput Analisys (DL)": ACP will evaluate coverages by
HSDPA RLC Peak Rate based on the parameters used to calculate the selected "HSDPA Quality and Throughput
Analisys (DL)" prediction in Atoll.
Only the Atoll predictions displaying a "HS-PDSCH Ec/Nt (dB)" per pixel can be accessed by the ACP.
AT332_UMR_E0
Manual configuration: If you select this option, you can Enable shadowing margin and define a 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. Additionally, you can specify:
The Service, Terminal, and Mobility that will be used during the calculation of HSDPA RLC Peak Rate through
gain and losses (i.e., the service body loss, the gain and loss of the terminal antenna, and the terminal noise
factor).
RSCP
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by RSCP.
Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, ACP will evaluate the coverage by RSCP using the same parameters that were used to calculate the coverage prediction.
Manual configuration: If you select this option, you can Enable shadowing margin and define a 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.
Ec/Io
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by Ec/Io.
Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, ACP will evaluate the coverage by Ec/Io using the same parameters that were used to calculate the coverage prediction.
Manual configuration: If you select this option, you can Enable shadowing margin and define a 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 EcIo calculation. Additionally, you
can specify:
The Service and Terminal that will be used during the calculation of EcIo through gain and losses (i.e., the
service body loss, the gain and loss of the terminal antenna, and the terminal noise factor).
Overlap / 1st-Nth
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by overlapping zones or by 1stNth difference.
Overlap
Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, ACP will
evaluate overlapping coverage using the same parameters that were used to calculate the coverage prediction. Only coverage predictions displaying a Number of Servers per pixel can be accessed by the ACP.
Manual configuration: If you select this option, specify a Minimum signal level and an Overlap threshold
margin.
1st-Nth
Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, ACP will
evaluate coverage by 1st-Nth difference based on the parameters used to calculate the selected prediction.
Only Atoll predictions displaying a "Number of Servers" per pixel can be accessed by the ACP.
Since there is no coverage prediction type in Atoll equivalent to ACPs UMTS 1st-Nth Difference objective, the
parameters recovered by ACP from the selected Atoll prediction are limited to the minimum signal level and
the prediction shading. The number of servers must always be specified manually next to No. servers.
Manual configuration: If you select this option, specify a Minimum signal level and the No. servers.
In both cases, the value you specify next to No. servers determines "Nth" in the UMTS 1st-Nth Difference objective. For instance if you set No. servers to 4, then the "1st-4th Difference" quality parameter will be automatically
selected by default in the Quality column of the UMTS 1st-Nth Difference properties page.
Allowed values for No. servers range from 3 to 100, with only one value available per technology.
The "1st-2nd Difference" quality parameter (based on No. servers = 2) is provided by default.
HSDPA EcNt
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by HSDPA EcNt.
Manual configuration: If you select this option, you can Enable shadowing margin and define a 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. Additionally, you can specify:
The Service, Terminal, and Mobility that will be used during the calculation of HSDPA EcNt through gain and
losses (i.e., the service body loss, the gain and loss of the terminal antenna, and the terminal noise factor).
RSSI
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by RSSI.
Manual configuration: If you select this option, you can Enable shadowing margin and define a 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. Additionally, you can specify:
The Service and Terminal that will be used during the calculation of RSSI through gain and losses (i.e., the
service body loss, the gain and loss of the terminal antenna, and the terminal noise factor).
591
Figure 8.15: ACP Quality Analysis Prediction Types for an UMTS Network
The quality analysis predictions created in ACP are equivalent to those created by different Atoll coverage predictions. The
correspondence table below shows the ACP predictions and their equivalents in Atoll.
RSCP
EcIo
Overlap
HSDPA EcNt
RSSI
1st-Nth Difference
N/A
(1) For more information, see "Making a Coverage Prediction by Signal Level" on page 538.
(2)
For more information, see "Studying Pilot Signal Quality" on page 541.
(3) For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 540.
(4)
(5)
Making these predictions 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 predictions display results very similar to those
that Atoll would display if you committed the optimisation results and calculated Atoll coverage predictions, however, before
592
AT332_UMR_E0
basing any decision to commit the optimisation results on the predictions produced by ACP, you should keep the following
recommendations in mind:
You should verify the results with a different coverage prediction, such as the pilot pollution analysis.
ACP generated predictions 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-carrier optimisation is supported in UMTS. However the predictions are provided separately for each carrier.
Even after committing the optimisation results, differences can remain between the ACP predictions and the predictions resulting from Atoll coverage predictions.
You can view the exact RSCP and EcIo values on any pixel by letting the pointer rest over the pixel. The RSCP or EcIo value is
then displayed in tip text.
For ACP overlapping zones predictions, you can:
For each network quality coverage prediction, ACP offers a prediction showing the initial network state, the final network
state, and a prediction showing the changes between the initial and final states.
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). Cells can be identified by their IDs or scrambling codes.
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:
1. In the Network explorer, right-click the Drive Test Data folder and select Import from the context menu. The Open
dialog box appears.
2. Select the file or files that you want to open. You can import one or several files.
593
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.
3. Click Open. The Import of Measurement Files dialog box 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 dialog box.
4. 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 dialog box. If you do not have
an import configuration, continue with step 5.
a. Under Import configuration, select an import configuration from the Import configuration list.
b. Continue with step 8.
When importing a drive test data path file, existing configurations are available in
the Files of type list of the Open dialog box, 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.
5. 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,
594
AT332_UMR_E0
Figure 8.16: The Setup tab of the Import of Measurement Files dialog box
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 dialog box 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.
ii. In the By 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.
e. If you are importing data that uses scrambling codes as cell identifiers:
i.
ii. 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.
iii. In the Scrambling code format list, select the scrambling code format, "Decimal" or "Hexadecimal."
iv. 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.
v. If you are importing drive test data for a specific carrier, select the carrier for which you are importing the drive
test data in the Carrier number list. If you are importing drive test data for more than one carrier, select "All".
f.
595
If you have correctly entered the information under File on the Setup tab, and the
necessary values in the Drive Test Data Setup dialog box, Atoll should recognise 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.
7. 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 dialog box 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 dialog box.
You can delete an existing import configuration by selecting the import configuration under Import configuration and clicking the Delete button.
8. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The mobile
data is imported into the current Atoll document.
596
AT332_UMR_E0
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 dialog box opens in which you can define the following
display for each single point of the measurement path:
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 in the Network explorer 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 dialog box and select Save or Load from
the Display Configuration submenu.
"Filtering Measurement Points Along Drive Test Data Paths" on page 597
"Predicting Signal Level on Drive Test Data Points" on page 598
"Predicting Signal Level on Drive Test Data Points" on page 598
"Displaying Statistics Over a Drive Test Data Path" on page 600
"Extracting a Field From a Drive Test Data Path for a Transmitter" on page 600
"Analysing Measurement Variations Along the Path" on page 600.
You can apply a filter on all the drive test data paths in the Drive Test Data folder
by selecting Filter from the context menu of the folder.
If you want to use the measurement points that you permanently deleted, you
must import the drive test data path again.
597
Figure 8.17: Selecting Measured Signal Levels for which Errors will be Calculated
4. Click OK. A new point prediction is created for the selected drive test data path.
5. Right-click the drive test data path. The context menu appears.
6. Select Calculations > Calculate All the Predictions from the context menu.
If you chose to have Atoll calculate the errors between measured and predicted signal levels, new columns are added to the
drive test data table for the predicted point signal level from the serving cell and the errors between the measured and
predicted values.
Figure 8.18: Drive Test Data Table after Point Signal Level Prediction (with Error Calculations)
New columns are also added for the predicted point signal level from each neighbour cell and the errors between the
predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For
more information on the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 600.
598
AT332_UMR_E0
The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main
matrix. For more information on propagation models, see Chapter 4: Radio Calculations and Models.
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 241.
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
account check box and enter a percentage in the Cell edge coverage probability text box.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency
per clutter class.
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. Indoor losses are defined per frequency per clutter class. 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 241.
You must also select which Carrier is to be considered.
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.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency
per clutter class.
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 241.
You must also select which Carrier is to be considered.
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.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency
per clutter class.
599
3. When you have finished setting the parameters for the coverage prediction, click OK.
You can create a new coverage prediction by repeating step 1 and step 2 for each new coverage prediction.
4. When you have finished creating new coverage predictions for these drive test data, right-click the drive test data. The
context menu appears.
5. 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 4: Radio Calculations and
Models).
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 Measurement Variations Along the Path" on page 600.
8.5.4.5 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:
1. In the Network explorer, expand the Drive Test Data folder, right-click the drive test data from which you want to
extract a field, and select Focus on a Transmitter from the context menu. The Field Selection for a Given Transmitter
dialog box appears.
2. Select a transmitter from the On the Transmitter list.
3. Click the For the Fields list. The list opens.
4. 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.
5. Click OK. Atoll creates a new column in the drive test data path table for the selected transmitters and with the
selected values.
600
AT332_UMR_E0
To analyse measurement variations using the Drive Test Data analysis tool.
1. In the Network explorer, expand the Drive Test Data folder, right-click the drive test data you want to analyse, and
select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 8.19).
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 dialog box.
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.
4. You can display the data in the drive test data path in two ways:
601
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 8.19 on page 601). 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 "Setting the Display Type" on page 52.
5. 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 dialog box. 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 dialog box.
6. 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 on one end of the range of data you want to zoom in on.
602
AT332_UMR_E0
4. Click OK. Atoll creates new CW measurements for transmitters satisfying the parameters set in the CW Measurement
Extraction dialog box.
For more information about CW measurements, see the Model Calibration Guide.
To print the Drive Test Data analysis tool, select Print from the context menu.
To export the Drive Test Data analysis tool, select Copy from the context menu, then paste.
Select File > Open or File > New > From an Existing Database.
603
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 With > Browse. The Link With dialog box 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].
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.
604
AT332_UMR_E0
the tip text to enable you to distinguish the objects and data displayed on the map. For more information on tip text, see
"Associating a Tip Text to an Object" on page 54.
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 "Changing the Order of
Layers" on page 51.
Figure 8.21 shows an example of UMTS transmitters with labels, and GSM transmitter data displayed in tip text.
When you click the Calculate button, Atoll first 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 and Unlocking Coverage Predictions" on page 207.
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.
605
To force Atoll to recalculate all path loss matrices before calculating coverage predictions:
1. Click the Force Calculate button (
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.
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.
8.6.2.2.1
8.6.2.2.2
606
AT332_UMR_E0
8.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.
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 8.6). 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.
8.6.2.2.4
607
Figure 8.24: GSM coverage by transmitter high transparency with full interior coloured by BCCH, with BCCH/BSIC
information available in tip text
8.6.2.2.5
608
AT332_UMR_E0
Figure 8.25: 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 Refresh Folder Configuration and have to be set up manually.
UMTS-specific coverage conditions in automatic inter-technology neighbour allocation are described below.
Other concepts that are specific to UMTS networks are explained in "Planning Neighbours" on page 560
When it is cleared, only the defined Distance will be used to allocate neighbours to a reference transmitter.
When it is selected, click Define to open the Coverage Conditions dialog box:
Resolution: Enter the resolution to be used to calculate cells coverage areas during automatic neighbour allocation.
Global min RSCP: Enter the minimum RSCP to be provided by the reference cell and the potential neighbour. Atoll
uses the highest value between the Global min RSCP and the following:
If Global min RSCP is not defined, Atoll uses the Min RSCP in individual cells properties
If Global min RSCP is not defined and no Min RSCP is available in a cells properties, Atoll uses the Default min
Pilot RSCP threshold defined on the Calculation Parameters tab of the Network Settings Properties dialog
box.
609
Min EcIo: Enter the minimum EcIo 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.
Handover margin: Enter the maximum difference of Ec/Io between reference cell A and possible neighbour cell B
in the overlapping area. You can select whether Atoll should use a Global value of the handover margin for all the
cells, or the handover margins Defined per cell.
Max EcIo: If you want, you can select this check box then enter the maximum difference of EcIo between reference cell A and potential neighbour cell B in the overlapping area.
The Max Ec/Io field is not available when UMTS is the target technology.
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.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this check box to take indoor losses into acccount in calculations. Indoor losses are
defined per frequency per clutter class.
Co-site neighbours: cells located on the same site as the reference transmitter will automatically be considered as
neighbours. A transmitter/cell with no antenna cannot be considered as a co-site neighbour.
Exceptional pairs: Select this check box to force the neighbour relations defined in the Inter-technology Exceptional
pairs table. For more information, see "Exceptional Pairs" on page 223.
Description
When
Distance
Coverage
Co-Site
Exceptional Pair
Exceptional pairs
is selected
Existing
610
AT332_UMR_E0
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 1359. For
information on the optimisation results, see "Viewing Optimisation Results" on page 1362.
611
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.
Name: Enter a name for the frequency, for example, "Band 2100." This name will appear in other dialog boxes
when you select a frequency band.
Bandwidth (MHz): Enter the bandwidth for each carrier in the frequency band.
DL Start Frequency (MHz): Enter the downlink start 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.
Step: Enter the step between any two consecutive carrier numbers in the frequency band.
Excluded Carriers: Enter the carrier numbers which do not belong to the frequency band. You can enter non-consecutive carrier numbers separated with a comma, or you can enter a range of carrier numbers separating the first
and last index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
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
3. When you have finished adding frequency bands, click the Close button (
).
For example, if you wish to define the UTRA Band I and UARFCNs corresponding to the centre frequencies of the carriers
(10562, 10587, 10612), you can set:
612
AT332_UMR_E0
You can also access the properties dialog box of each individual frequency band by double-clicking the left margin of the row
with the frequency band.
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. Atoll automatically 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). Atoll automatically 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.
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
deviation value of EbNt on the uplink defined per clutter 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
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 EcI0, 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 Activation Threshold: You can select the EcI0 Active check box and enter a EcI0 Activation Threshold.
You must select either the RSCP Active check box or the EcI0 Active check box or both.
613
EbNt UL and DL Target Increase: When compressed mode is activated, EbNt requirements in UL and DL are
increased. In order to take this into account, Atoll adds UL and DL EbNt target increase values to the UL and DL
EbNt requirements set for each radio bearer.
HSDPA: Under HSDPA, you can define how total noise is calculated and how the CQI (Channel Quality Indicator) is
evaluated for HSDPA.
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 EcNt or you can
select Based on HS-PDSCH quality and Atoll will measure the CQI based on the HS-PDSCH EcNt. 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 dialog box of the terminal equipment. The calculated CQI will be used to determine the best
bearer.
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.
Default min. pilot RSCP threshold: The default minimum pilot RSCP required for a user to be connected to the
cell. The RSCP is compared with this threshold to determine whether or not a user can be connected to the cell.
A minimum pilot RSCP threshold can be defined at the cell level (in the cell Properties
dialog box or in the Cells table). If defined, a cell-specific minimum pilot RSCP threshold will
be used instead of the value entered here.
Receiver: Under Receiver, you can enter the Height of the receiver.
Default max range: The maximum coverage range of transmitters in the network.
Index: The layer index is automatically assigned by Atoll to each new layer that you create.
Name: The name of the network layer.
Priority: The priority of the network layer.
Max speed (km/h): The highest speed of a mobile user that can connect to cells of this layer.
3. When you have finished adding network layers, click the Close button (
614
).
AT332_UMR_E0
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 (
).
Uplink Peak Throughput (Kbps): Enter or modify the uplink peak throughput in kilobytes per second.
Downlink Peak Throughput (Kbps): Enter or modify the downlink peak throughput 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 dialog box. 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.
HSDPA bearers using QPSK and 16QAM modulations. They can be selected for users connected to HSPA and HSPA+
capable cells.
615
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:
1. In the Parameters explorer, expand the UMTS Network Settings folder and the Radio Bearers folder, right-click the
HSDPA Radio Bearers folder, and select Open Table from the context menu. The HSDPA Radio Bearers table appears
with the following information:
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.
616
Name: The name you enter will be the one used to identify this piece of equipment.
Manufacturer: The name of the manufacturer of this piece of equipment.
AT332_UMR_E0
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. The specified carrier selection mode is not taken into account in predictions (AS
analysis, multi-point 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 peak RLC throughput to be added to the peak RLC throughput. The total value corresponds to the
Iub backhaul throughput required by the HSDPA bearer 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.
Dual-band HSDPA: Select Active if the site supports the dual-band HSDPA mode. Otherwise, select Inactive. When
dual-band HSDPA is active, HSDPA bearer users with suitable terminals can simultaneously connect to two co-site
transmitters using different frequency bands. If the two co-site transmitters work on the same frequency band,
then HSDPA bearer users can only connect to the HSDPA cells of one transmitter.
Scheduler Algorithm: The scheduling technique used by the Node B to rank the HSDPA bearer users to be served
when the Node B supports the multi-cell HSDPA mode. You can select the scheduler from the list of schedulers
available in the Schedulers table. For more information, see "Defining HSDPA Schedulers" on page 620.
8.7.6.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.
617
To define channel element and Iub backhaul throughput consumption during UMTS simulations:
1. In the Parameters explorer, expand the UMTS Network Settings folder and the Radio Resource Management folder,
right-click R99 Resource Consumption, and select Open Table from the context menu. The R99 Resource Consumption table appears.
2. 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.
8.7.6.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:
1. Select the Parameters explorer.
1. In the Parameters explorer, expand the UMTS Network Settings folder and the Radio Resource Management folder,
right-click HSUPA Resource Consumption, and select Open Table from the context menu. The HSUPA Resource
Consumption table appears.
2. 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.
3. Click the General tab. On the General tab, you can define the Name of the reception equipment.
4. Click the R99 Bearer Selection tab. On the R99 Bearer Selection tab, you can define downlink and uplink EbNt
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 EbNt. You can
specify gains on received downlink and uplink EbNt for each diversity configuration. Atoll will consider them when Tx
or Rx diversity configurations are assigned to transmitters.
618
AT332_UMR_E0
Downlink Closed Loop Diversity Gain (dB): Enter or modify the downlink closed loop diversity gain in dB.
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.
619
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 621.
RX
No MIMO gain (diversity, spatial multiplexing) is applied if N TX
Ant = N Ant = 1 .
17. Click OK to close the reception equipment types Properties dialog box.
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.
DL Multi-cell Mode: Select the type of multi-cell mode supported by the category, i.e., the maximum number of
cells to which an HSDPA bearer user can simultaneously connect. If the category does not support multi-cell
HSDPA, select None.
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.
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.
UL Multi-cell Mode: Select 2C (dual-cell) whether the category supports multi-cell. If the category does not support multi-cell, select None.
Max Number of E-DPDCH Codes: The maximum number of E-DPDCH codes allowed for the category.
620
AT332_UMR_E0
Max C/I: "n" HSDPA bearer users (where "n" corresponds to the sum of the maximum numbers of HSDPA bearer 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 bearer users are scheduled in the same order as in the simulation (i.e., in random order).
Proportional Fair: "n" HSDPA bearer users (where "n" corresponds to the maximum number of HSDPA bearer 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
the Atoll.ini file. For more information, see the Administrator Manual.
The Schedulers table lists the available schedulers. You can add, remove, and modify scheduler properties, if you want.
To define schedulers:
1. In the Parameters explorer, expand the LTE Network Settings folder, right-click Schedulers, and select Open Table.
The Schedulers table appears.
2. In the table, enter one scheduler per row. For information on working with data tables, see "Data Tables" on page 75.
For each scheduler, enter:
Name: Enter a name for the scheduler. This name will appear in the cell properties.
Scheduling method: Select the scheduling method used to rank the HSDPA bearer users to be served.
You can open a schedulers properties dialog box by double-clicking the corresponding row in the Schedulers table. In
the properties dialog box, a MUG tab is available for Proportional fair schedulers. On the MUG tab, you can define
the throughput gain due to multi-user diversity. 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" and if you have set the peak HSDPA throughput option in the Atoll.ini file. For more information, see the Administrator Manual.
Note that you can enter MUG graphs for different configurations in terms of numbers of cells to which the users are
connected.
3. Click the Close button (
621
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 sufficient HS-PDSCH EcNt conditions.
In Atoll, you can define whether a cell supports spatial multiplexing by selecting HSPA+ and Spatial Multiplexing in the cell
properties (see "Cell Properties" on page 516). 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 618.
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 EcNt.
Because spatial multiplexing improves the channel capacity or throughputs, the HS-PDSCH EcNt of a user is determined first.
Once the HS-PDSCH EcNt 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 127.
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
Ec
TX
RX
is the chanMIMO system using N Ant transmission and N Ant reception antenna ports. CCSISO = Log 2 1 + -------
Nt HS PDSCH
nel capacity for a single antenna system at a given HS-PDSCH EcNt. HS-PDSCH EcNt is used as a ratio (and not dB) in these
formulas. You can replace the default spatial multiplexing capacity gain graphs with graphs extracted from simulated or measured values.
They must use a frequency band with which the terminal is compatible.
They must also belong to layers supported by the service and the terminal, and these layers must support a speed
higher than the user mobility.
In addition, the pilot signal level received from these cells must exceed the defined minimum RSCP threshold.
The candidate cells are ranked according to the best server indicator ( I BS ). The cell with the highest I BS is selected as the
best serving cell.
Each other cell of the active set is selected among the potential serving cells as follows:
622
AT332_UMR_E0
table. For an explanation of how to set the AS Restricted to Neighbours option, see "Creating Site Equipment" on
page 616.
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.
For a description of the properties of a cell, see "Cell Properties" on page 516. For information on accessing the parameters
defined for a given cell, see "Creating or Modifying a Cell" on page 521. For more information on defining layers, see "Defining
Network Deployment Layers" on page 614.
You can return to the old best serving cell selection mechanism as in Atoll 3.2.1, by setting
an option in the Atoll.ini file. For more information about setting options in the Atoll.ini file,
see the Administrator Manual.
A point analysis (see "Studying the Profile Around a Base Station" on page 526)
A coverage prediction (see "Studying Signal Level Coverage for a Single Base Station" on page 538).
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.
To display the shadowing margins and macro-diversity gain per clutter class:
1. In the Network explorer, right-click the Predictions folder and select Shadowing Margins from the context menu. The
Shadowing Margins and Gains dialog box appears.
2. 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 dialog box 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 EcI0 standard deviation. Atoll will display the EcI0 shadowing margin and the resulting 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.
UL EbNt: The EbNt UL standard deviation. Atoll will display the EbNt UL shadowing margin and the resulting
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 EbNt DL standard deviation. Atoll will display the EbNt DL shadowing margin.
3. If you select "EcI0" or "EbNt UL" as the standard deviation 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 "EcI0" as the standard deviation under Standard Deviation, enter
the allowed EcI0 difference between the best server and the second one. This value is used to calculate DL macrodiversity gains. If you selected "EbNt UL" as the standard deviation under Standard Deviation, enter the allowed
623
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 "EcI0" as the standard deviation under Standard Deviation, enter
the allowed EcI0 difference between the second-best server and the third one. This value is used to calculate DL
macro-diversity gains. If you selected "EbNt UL" as the standard deviation 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.
4. Click Calculate. The calculated shadowing margin is displayed. If you selected "EcI0" or "EbNt UL" as the standard
deviation under Standard Deviation, Atoll also displays the macro-diversity gains for two links and for three links.
5. Click Close to close the dialog box.
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) can 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.
Interference from external mobiles (also called uplink-to-downlink interference) can 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 Additional 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 Additional DL Noise Rise, see "Cell Properties" on page 516.
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 547.
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) can 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) can 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 Additional 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, multi-point analysis and coverage predictions) and does not have
an impact on the calculation of the cell reuse factor. For more information on the Additional UL Noise Rise, see "Cell
Properties" on page 516.
624
AT332_UMR_E0
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. in co-planning mode or in a multi-RAT document.
To define the inter-technology IRFs in the victim network:
1. In the Parameters explorer, expand the Radio Network Equipment folder, right-click Inter-technology Interference
Reduction Factors and select Open Table from the context menu. The Inter-technology Interference Reduction
Factors table appears.
2. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter:
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.
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 603. 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 Atoll will calculate interference from all the external base stations in all the linked documents.
625
626
Chapter 9
CDMA2000
Networks
This chapter covers the following topics:
628
AT332_UMR_E0
9 CDMA2000 Networks
Atoll enables you to create and modify all aspects of CDMA2000 1xRTT (1st eXpansion Radio Telephone Technology) and
CDMA2000 1xEV-DO (1xEvolution Data Only) Rev. 0, Rev. A and Rev. B networks. 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.
Planning the CDMA network and creating the network of base stations is explained in "Planning and Optimising CDMA Base
Stations" on page 629. Allocating neighbours is explained in "Neighbour Planning" on page 223 and allocating PN offsets is
explained in "Planning PN Offsets" on page 677. 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 CDMA2000 Network Capacity" on page 685, 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 "Analysing Network Performance Using Drive Test Data" on
page 701. Filtering imported drive test data paths, and using the data in coverage predictions is also explained.
A Note on the Terminology Used in This Chapter
The terminology used in CDMA is slightly different from the standard terminology used in Atoll. Therefore, the terminology
used in explanations reflects the standard CDMA terminology with the equivalent Atoll terminology given when references
are made to the user interface.
CDMA
Atoll
handoff
handover
radio configuration
terminal
reverse link
uplink (UL)
forward link
downlink (DL)
A n te n n a
- A z im u t h
- M e c h a n i c a l t i lt
TMA
A n te n n a
- H e ig h t
F e e d e r C a b le
T r a n s m it t e r
- N o is e fig u r e
- P ow er
S it e
- X , Y c o o r d in a t e s
629
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 analysed.
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 coverage predictions, such as effective service area, noise, or handoff status
predictions, on the network.
In this section, the following are explained:
630
AT332_UMR_E0
9.1.1.1.1
Site Description
The parameters of a site can be found in the sites Properties dialog box. The Properties dialog box has two tabs:
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 dialog box afterwards. For
information on placing sites using the mouse, see "Moving a Site Using the Mouse" on
page 57.
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.
Max Number of Uplink Channel Elements per Carrier: The maximum number of physical radio resources on the
reverse link per carrier for the current site. By default Atoll enters the maximum possible (256).
Max Number of Downlink Channel Elements per Carrier: The maximum number of physical radio resources on
the forward link per carrier for the current site. By default Atoll enters the maximum possible (256).
Max Number of EV-DO Channel Elements per Carrier: The maximum number of EV-DO radio resources on the
reverse link per carrier for the current site. This parameter is used only with CDMA2000 1xEV-DO. By default Atoll
enters the maximum possible (96).
With 1xEV-DO, only one user on the forward link can be served at a given time. This user consumes only one channel element. On the reverse link, there can be more than one user with each user consuming one channel element,
therefore, the maximum number of EV-DO radio resources applies only to the reverse link.
Equipment: You can select equipment from the list. To create new site equipment, see "Creating Site Equipment"
on page 727.
If no equipment is assigned to the site, Atoll uses the following default values:
9.1.1.1.2
Transmitter Properties
The parameters of a transmitter can be found in the transmitters Properties dialog box. When you create a transmitter, the
Properties dialog box has two tabs: the General tab and the Transmitter tab. Once you have created a transmitter, its Prop-
631
erties dialog box has three additional tabs: the Cells tab (see "Cell Properties" on page 633), the Propagation tab (see "Assigning Propagation Parameters" on page 187), and the Display tab (see "Setting the Display Properties of Objects" on page 51).
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 dialog box, see "Site Description" on page 631. 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 dialog box, see "Defining Frequency Bands" on page 723.
Shared antenna: This field is used to identify the transmitters, repeaters, and remote antennas located at the
same site or on sites with the same position and that share the same antenna. The entry in the field must be the
same for all transmitters, repeaters, and remote antennas sharing the same antenna. When changes are made to
the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared
antenna.
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 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.
Max Range: You can define a maximum coverage range from the transmitter.
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 explorer.
Only active transmitters are taken into consideration during calculations.
Transmission/Reception: Under Transmission/Reception, you can define the total losses and the noise figure in
the Real text boxes. Atoll can calculate losses and noise according to the characteristics of the equipment assigned
to the transmitter; the calculated values are indicated in the Computed text boxes. Atoll always considers the
values in the Real boxes in coverage predictions even if they are different from the values in the Computed boxes.
You can update the values in the Real boxes with the values in the Computed text boxes. For information, see
"Updating the Values for Total Losses and the Transmitter Equipment Noise Figure" on page 162.
You can assign equipment by using the Equipment Specifications dialog box which appears when you click the
Equipment button. For information on the Equipment Specifications dialog box, see "Assigning Equipment to a
Transmitter" on page 637.
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.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
632
Mechanical Azimuth, Mechanical downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt display additional antenna parameters.
AT332_UMR_E0
The Additional Electrical Downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
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 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.
The Additional Electrical Downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
Cell Tab
When you create a transmitter, Atoll automatically creates a cell for the transmitter using the properties of the currently
selected station template.
The cell tab enables you to configure the properties for every cell of a transmitter. For more information on the properties of
a cell, see "Cell Properties" on page 633.
Propagation Tab
Transmitters are taken into account during calculations. Therefore, you must specify their 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. For information on propagation models, see "Assigning Propagation Parameters" on page 187.
Display Tab
On the Display tab, you can modify how a transmitters are displayed. For information on changing display properties, see
"Setting the Display Properties of Objects" on page 51.
9.1.1.1.3
Cell Properties
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 CDMA multi-carrier network. In other words, a transmitter has one cell for every carrier.
This section explains the Parameters of a CDMA cell. As you create a cell, Atoll calculates appropriate values for some fields
based on the information you have entered.
The properties of a CDMA cell are found on Cells tab of the Properties dialog box of the transmitter to which it is assigned.
You can also display the properties of a cell by double-clicking the cell in the Site explorer.
The following 1xEV-DO Rev B options apply to all the 1xEV-DO cells of the transmitter:
Under EV-DO Rev B, the following 1xEV-DO Rev B options are available:
Multi-carrier support: You can define whether the transmitter supports the multi-carrier EV-DO operation. When
multi-carrier EV-DO is active, multi-carrier EV-DO users can simultaneously connect with two or more EV-DO carriers of transmitters that support the mode (i.e., multi-carrier EV-DO users receive the data on several separate
carriers. In Atoll, a multi-carrier EV-DO user is referred to as a user with multi-carrier EV-DO-based services and a
multi-carrier terminal.
MUG Table: You can access the MUG (Multi-User Gain) table by clicking the Browse button. The MUG table is a
graph of gain as a function of the number of users. The average cell throughput is higher with multiple users than
with a single user. This is modelled by the MUG graph. It is used to calculate the downlink average cell throughput.
For transmitters that support multi-carrier EV-DO, this MUG graph is used in calculations instead of the MUG
graph set per cell.
Min Ec/Nt (UL): You can enter or modify the minimum Ec/Nt to operate multi-carrier EV-DO in the reverse link.
The following parameters can be set for each individual cell of the transmitter:
633
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 Administrator 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 and the type of carrier. You can choose 1xRTT or 1xEV-DO as the carrier type.
Order: The display order of a cell within the transmitter. This value is used to determine the order in which information
related to a cell will be displayed in the Network explorer and on the map. This field is automatically filled by Atoll but
you can change these default values to display cells in a user-defined order.
The consistency between values stored in this field is verified by Atoll. However, inconsistencies may arise when tools other than Atoll modify the database. You can check for inconsistencies in the cell display order and fix them by selecting Data Audit > Cell Display Order
Check in the Document menu.
The following parameters are available for 1xRTT and 1xEV-DO carriers:
Active: If this cell is active, you must select the Active check box.
PN Offset Domain: The Pseudo Noise (PN) offset domain to which the cell belongs. The PN offset domain is a set
of groups, with each group containing several PN offsets.
Co-PN Reuse Distance (m): The distance within which the PN offset defined for this cell cannot be reused.
PN Offset: The PN offset is a time offset used by a cell to shift a Pseudo Noise sequence.
Ec/Io Threshold (dB): Enter the minimum EcI0 required from the cell to be the best server in the active set.
T_Drop: Enter the minimum EcI0 required from the cell not to be rejected from the active set.
Min RSCP (dBm): The minimum pilot RSCP required for a user to be connected to the cell. The pilot RSCP is compared with this threshold to determine whether or not a user can be connected to the cell.
When this field is empty, Atoll uses the Default Min Pilot RSCP Threshold defined on the
Calculation Parameters tab of the Network Settings Properties dialog box.
Additional UL Noise Rise: This noise rise represents the interference created by mobiles and base stations of an
external network on this cell on the uplink. This noise rise will be taken into account in all uplink interferencebased calculations involving this cell in simulations. 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 intertechnology uplink interference. For more information on inter-technology interference, see "Modelling Intertechnology Interference" on page 733.
Additional 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 733.
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.
Neighbours: You can access a dialog box in which you can set both intra-technology (intra-carrier and inter-carrier)
and inter-technology neighbours by clicking the Browse button. For information on defining neighbours, see
"Editing Neighbours in the Cell Properties" on page 228.
The Browse button may not be visible in the Neighbours box if this is a new cell. You can
make the Browse button appear by clicking Apply.
634
AT332_UMR_E0
By default, the synchronisation power and paging power are set as absolute values. You
can set these values as relative to the pilot power by right-clicking the Network Settings
folder in the Parameters explorer and selecting Properties from the context menu. Then,
on the Global Parameters tab of the Properties dialog box, under DL Powers, you can
select Relative to Pilot. The synchronisation power and paging power values are automatically converted and set as relative to the pilot power.
Max DL Load (% Pmax): The percentage of the maximum forward link power (set in Max Power) not to be
exceeded. This limit will be taken into account during the simulation if the options DL Load and Max DL Load
defined per cell are selected. If these options are not selected during a simulation, this value is not taken into consideration.
Max UL Load Factor (%): The maximum reverse link load factor not to be exceeded. This limit can be taken into
account during the simulation. This limit will be taken into account during the simulation if the options UL Load
Factor and Max UL Load Factor defined per cell are selected. If these options are not selected during a simulation,
this value is not taken into consideration.
Total Power (dBm or %): The total transmitted power on forward link. This value can be a simulation result or can
be entered by the user.
By default, the total power is set as absolute value. You can set this value as a percentage
of the maximum power of the cell by right-clicking the Network Settings folder in the
Parameters explorer and selecting Properties from the context menu. Then, on the Global
Parameters tab of the Properties dialog box, under DL Load, you can select % Pmax. The
total power value is automatically converted and set as a percentage of the maximum
power.
UL Load Factor (%): The reverse link cell load factor. This factor corresponds to the ratio between the reverse link
total interference and the reverse link total noise. This is the global value of reverse link load factor including the
reverse link inter-technology interference. This value can be a simulation result or can be entered by the user.
Power Reserved for Pooling (dB): The power reserved for pooling is the maximum amount of power that can be
allocated to this cell by other transmitters on the site using the same carrier. This value is only used if the site
equipment allows power pooling between transmitters.
Max Power (dBm): The power transmitted by a 1xEV-DO cell when there is at least one user. For 1xEV-DO carriers,
the transmitter equipment always transmits at maximum power (the DL maximum power) unless it has no user to
support. When there is no user, the transmitter equipment transmits a very low level of power during idle traffic
slots (DL maximum power + Idle gain).
Idle Power Gain (dB): The gain applied to the DL power when there is no active user connected to the cell. It must
be a negative value.
MUG Table: You can access the MUG (Multi-User Gain) table by clicking the Browse button. The MUG table is a
graph of gain as a function of the number of users. The average cell throughput is higher with multiple users than
with a single user. This is modelled by the MUG graph.
In transmitters that support multi-carrier EV-DO, this MUG graph is used in calculations instead of the MUG graph
set per cell.
Noise Rise Threshold (dB): The noise rise threshold. The noise rise threshold and the acceptable noise rise margin
are considered in the simulation during reverse link congestion. Atoll ensures that the cell reverse link noise rise
is within a range defined by the noise rise threshold plus the margin and the noise rise threshold minus the margin.
Acceptable Noise Rise Margin (dB): The acceptable noise rise margin.
DRC Error Rate (%): The error rate as a percentage received by the cell on the Data Rate Control (DRC) channel.
The cell may receive the DRC channel from a mobile incorrectly. If this happens, the mobile will not be scheduled
for data transmission. This value is taken into account during rate control when Atoll calculates the average cell
throughput on the forward link.
EV-DO Timeslots Dedicated to BCMCS (%): The percentage of timeslots dedicated to Broadcast/Multicast Services
(BCMCS). This parameter is taken into account during rate control when Atoll calculates the cell average forward
link throughput.
EV-DO Timeslots Dedicated to Control Channels (%): The percentage of timeslots dedicated to control channels
(control, pilot, and ACK channels). This parameter is taken into account during rate control when Atoll calculates
the cell average forward link throughput.
BCMCS Throughput (kbps): The BCMCS throughput. Two throughput values are available: 204.8 kbps and
409.6 kbps. This parameter is taken into account during rate control when Atoll calculates the cell average forward link throughput.
Max UL Load Factor (%): The maximum reverse link load factor not to be exceeded. This limit can be taken into
account during the simulation.
635
Total Power (dBm): The total transmitted power on forward link. This value can be a simulation result or can be
entered by the user.
UL Load Factor (%): The reverse link cell load factor. This factor corresponds to the ratio between the reverse link
total interference and the reverse link total noise. This is the global value for the reverse link load factor including
the reverse link inter-technology interference. This value can be a simulation result or can be entered by the user.
Max No. of EV-DO Users: The maximum number of EV-DO carrier users that this cell can support at any given time.
Multi-carrier EV-DO users are counted once in each cell they are connected to.
9.1.1.2.1
9.1.1.2.2
636
AT332_UMR_E0
9.1.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 in the Network explorer and selecting Open Table
from the context menu. For information on copying and pasting data, see "Copying
and Pasting in Tables" on page 83.
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.
9.1.1.2.4
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 in the Network explorer 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 83), or
import data into the table (see "Importing Tables from Text Files" on page 88).
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.
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 161.
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 161.
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 162.
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.
637
Any loss related to the noise due to a transmitters repeater is included in the calculated
reception losses.
4. Click OK.
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 60.
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.
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.
9.1.1.4.1
638
AT332_UMR_E0
1st sector mechanical azimuth from which the azimuth of the other sectors are offset to offer complete coverage
of the area.
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 the building).
Mechanical downtilt for the antennas.
Electrical Azimuth, Electrical Downtilt, and Additional electrical downtilt display additional antenna parameters.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
Under Path loss matrices, you can modify the following: the Main propagation model, the Main radius, and the Main
resolution, and the Extended propagation model, the Extended radius, and the Extended resolution. For information
on propagation models, see Chapter 4: Radio Calculations and Models.
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.
Transmitter Tab
Active: Select this option to specify whether the transmitter is active. Active transmitters are displayed in red in the
CDMA Transmitters folder of the Network explorer.
Only active transmitters are taken into consideration during calculations.
Click the Equipment button to modify the tower-mounted amplifier (TMA), feeder cables, or transmitter equipment.
For information on the Equipment Specifications dialog box, see "Assigning Equipment to a Transmitter" on page 637.
The Total losses (transmission and reception) and Noise figure (reception) in the Computed columns is calculated
from the information that was entered in the Equipment Specifications dialog box. The Total losses (transmission and
reception) Noise figure (reception) in the Real columns can be edited. Any value that you enter must be positive.
Any loss related to the noise due to the repeater of a transmitter is included in the calculated losses. Atoll always considers the values in the Real boxes in coverage predictions
even if they are different from the values in the Computed boxes.
CDMA Tab
On this tab, you can modify the specifications of the Carriers (each corresponding to a cell) that each transmitter supports.
Carrier: You can select the 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, click the Browse button and select the carriers to be created for each sector of the station.
PN Offset: Define the Reuse Distance and the Domain of the pseudo noise offset.
Power: Specify the Pilot, the Paging, and the Synchro powers, and the Idle Power Gain.
Simulation Constraints: Specify the Max Power, the Max DL Load (defined as a percentage of the maximum
power), and the Max UL Load Factor.
Load Conditions: Specify the Total Transmitted Power and the UL Load Factor.
Active Set: Specify the Min Ec/Io and the T-Drop.
Additional Interference: Set the DL Noise Rise and the UL Noise Rise. For more information on inter-technology
interference, see "Modelling Inter-technology Interference" on page 733.
You can also modify the Number of Uplink and Downlink Channel Elements and select the Equipment.
For information on carriers and cells, see "Cell Properties" on page 633.
639
CDMA2000 Tab
Use this tab to specify additional carrier parameters (each corresponding to a cell) that each transmitter supports. For information on carriers and cells, see "Cell Properties" on page 633.
Power Reserved for Pooling: Specify the power that is reserved for pooling.
1xRTT: Specify the Pilot Power, the Paging Power, and the Synchro Power.
1xEV-DO: Specify the Idle Power Gain, the Max. Number of EV-DO Channel Elements per Carrier, and you can modify
the MUG (multi-user gain) table.
Rev. 0: Specify the Noise Rise Threshold, the Acceptable Noise Rise Margin, and the DRC Error Rate.
Rev. A: Set the Timeslot BCMCS, the Timeslot Control Channels, and the BCMCS Throughput.
Rev. B: Select whether Multi-carrier EV-DO is supported and you can enter a MUG=f(No. Users) graph and define the
min Ec/Nt (UL).
Neighbours Tab
On this tab, you can modify the Max Number of Intra- and Inter-Carrier Neighbours and the Max Number of Intertechnology Neighbours. For information on defining neighbours, see "Neighbour Planning" on page 223.
Other Properties Tab
This tab only appears if you have defined additional fields in the Sites table, or if you have defined an additional field in the
Station Template Properties dialog box.
9.1.1.4.2
9.1.1.4.3
9.1.1.4.4
640
AT332_UMR_E0
9.1.1.4.5
9.1.1.4.6
Quickly create a new base station with the same settings as an original base station in order to study the effect of a
new station on the coverage and capacity of the network, and
Quickly create a new homogeneous network with stations that have the same characteristics.
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 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.
5. Place the new base station on the map using the mouse:
Creating a duplicate base station and site: In the map window, move the pointer over the map to where you
would like to place the duplicate. The exact coordinates of the pointers current location are visible in the Status
bar.
Placing the duplicate base station on an existing site: In the map window, move the pointer over the existing site
where you would like to place the duplicate. When the pointer is over the site, the site is automatically selected.
The exact coordinates of the pointers current location are visible in the Status bar.
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 60.
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.
641
A new base station is placed on the map. If the duplicate base station was placed on a new site, 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. If the duplicate base station was placed on an existing site, the transmitters, and cells of the new base station have the same names as the transmitters, and cells of the original base station
with each name preceded by the name of the site on which the duplicate was placed.
All the remote antennas and repeaters of any transmitter on the original site are also duplicated.
Any duplicated remote antennas and repeaters will retain the same donor transmitter as
the original. If you want the duplicated remote antenna or repeater to use a transmitter
on the duplicated base station, you must change the donor transmitter manually.
You can also place a series of duplicate base stations by pressing and holding Ctrl in step 6. and clicking to place each
duplicate base station.
For more information on the site, transmitter, and cell properties, see "Definition of a Base Station" on page 630.
) in the Radio Planning toolbar. The Point Analysis window appears and the
pointer changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and
the current position. You can move the receiver on the map (see "Moving the Receiver on the Map" on page 203).
3. Select the Profile view.
642
AT332_UMR_E0
intersects the Fresnel ellipsoid the most. Propagation models that use a 3 knife-edge Deygout diffraction method may
also display two additional diffraction edges. The total attenuation is displayed above the main diffraction edge.
The results of the analysis are displayed at the top of the Profile view:
The received signal strength from the selected transmitter for the cell with the highest reference signal power
The propagation model used
The shadowing margin and the indoor loss (if selected)
The distance between the transmitter and the receiver.
4. If needed, select an other transmitter from the list. You can click the Properties button (
properties.
) to display the Calculation Options dialog box and change the following:
Change the X and Y coordinates to change the current position of the receiver.
Select the Shadowing taken into account check box and enter a Cell edge coverage probability. For more information, see "Taking Shadowing into Account in Point Analyses" on page 204.
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. Indoor losses are defined per frequency per
clutter class. For more information, see "Taking Indoor Losses into Account" on page 203.
7. In the Profile view toolbar, you can use the following tools:
) to view the geographic profile between the transmitter and the receiver.
) again to view the radio signal path between the transmitter and the
Click the Detailed Report button ( ) to display a text document with details on the displayed profile analysis.
The detailed report is only available for the Standard Propagation Model.
Click the Copy button (
) to copy the content of the view and paste it as a graphic into a graphic editing or wordprocessing programme.
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.
The table you copy from must have the same column layout as the table you are pasting
data into.
643
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 83.
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 and Spreadsheets" on page 86. For information on importing table data, see "Importing Tables from Text Files" on page 88.
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 638.
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 "Associating a
Label to an Object" on page 53.
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 "Associating a Tip Text to an Object" on page 54.
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.
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 "Setting the Display Type" on page 52.
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 (
same site with the same azimuth, you can differentiate them by selecting different symbols for each (
For information on defining the transmitter symbol, see "Setting the Display Type" on page 52.
644
and
).
AT332_UMR_E0
):
645
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 box (
box.
e. Enter the maximum power that the equipment can transmit on the downlink in the Maximum 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 Maximum Uplink Power, an Internal Delay and Comments. These fields are for information
only and are not used in calculations.
To modify repeater equipment:
1. Select the Parameters explorer.
2. Click the Expand button ( ) to expand the Radio Network Equipment folder.
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.
When the donor is a transmitter, you can see to which base station the repeater is
connected by clicking it; Atoll displays a link to the donor transmitter. You can hide
the link by clicking it again.
When the donor is a repeater or a remote antenna, Atoll displays a spider-type link
showing the entire chain down to the donor transmitter. The same spider-type link
is displayed when you click any of the items belonging to the chain is clicked (i.e.,
donor transmitter, any repeater, or any remote antenna).
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 83.
646
AT332_UMR_E0
You can change the Name of the repeater. By default, repeaters are named "SiteX_Y_RepZ" where "X" is the donor
site number, "Y" the donor transmitter number, and "Z" a number assigned to the repeater when it was created.
If the donor is a remote antenna or another repeater, then "RepZ" is preceded by "RemA_"
or "RepB_" where "A" and "B" identify the donor remote antenna and the donor repeater.
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, a remote antenna,
or another repeater. Clicking the Browse button opens the Properties dialog box of the selected donor.
You can change the Site on which the repeater is located. Clicking the Browse button opens the Properties dialog
box of the selected site.
You can enter a value in the Shared antenna (coverage side) field for the repeater. This field is used to identify the
transmitters, repeaters, and remote antennas that are located at the same site or on sites with the same position
and that share an antenna. The entry in the field must be the same for all such transmitters, repeaters, and remote
antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of
one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote
antennas defined as having a shared antenna.
Under Antenna Position, you can define the position of the repeater, if it is not located on the site itself:
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 dialog box of
the equipment.
You can change the Amplifier Gain. 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:
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:
Model: The type of antenna is visible in the Model list. You can click the Browse button to access the properties of the antenna.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
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 repeater is situated on a building, the height entered must
include the height of building.
Mechanical Azimuth and Mechanical Downtilt display additional antenna parameters.
647
You can click the Calculate button to update the mechanical azimuth and mechanical
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 to access the properties of the feeder.
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
explorer) are calculated.
Under Total Gain, enter the gain in the forward and reverse links (DL/UL) or click Calculate to determine the actual
gain in the forward and reverse links. If you have modified any parameter in the General, Donor Side, or Coverage
Side tabs, click Apply before clicking the Calculate button.
In the forward link, the total gain is applied to each power (pilot power, SCH power, etc.).
In the reverse link, the total gain is applied to each terminal power.
The total gain takes into account losses between the donor transmitter and the repeater, donor characteristics
(donor antenna gain, reception feeder losses), amplifier gain, and coverage characteristics (coverage antenna
gain, transmission feeder losses).
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 repeater 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.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
Mechanical Azimuth, Mechanical downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt display additional antenna parameters.
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.
The Additional Electrical Downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
Select a Type of feeder from the list. You can click the Browse button to access the properties of the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
Under Losses, the Loss related to repeater noise rise is displayed and you can modify the following information:
Misc. losses: You can specify additional losses in dB for Transmission and Reception.
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 4: Radio Calculations and Models.
648
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 reverse link and forward link total gains of all repeaters by selecting Repeaters > Calculate Gains
from the Transmitters context menu.
AT332_UMR_E0
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 57) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using
the Mouse" on page 58).
649
When the donor is a transmitter, you can see to which base station the repeater is
connected by clicking it; Atoll displays a link to the donor transmitter. You can hide
the link by clicking it again.
When the donor is a repeater or a remote antenna, Atoll displays a spider-type link
showing the entire chain down to the donor transmitter. The same spider-type link
is displayed when you click any of the items belonging to the chain is clicked (i.e.,
donor transmitter, any repeater, or any remote antenna).
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 83.
You can change the Name of the remote antenna. By default, remote antennas are named "SiteX_Y_RemZ" where
"X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned to the remote antenna
when it was created.
If the donor is a repeater or another remote antenna, then "RemZ" is preceded by "RepA_"
or "RemB_" where "A" and "B" identify the donor repeater and the donor remote antenna.
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, another remote
antenna or a repeater. Clicking the Browse button opens the Properties dialog box of the selected donor.
You can change the Site on which the remote antenna is located. Clicking the Browse button opens the Properties
dialog box of the selected site.
You can enter a value in the Shared Antenna (coverage side) field for the remote antenna. This field is used to
identify the transmitters, repeaters, and remote antennas that are located at the same site or on sites with the
same position and that share an antenna. The entry in the field must be the same for all such transmitters,
repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height,
or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters,
repeaters, and remote antennas defined as having a shared antenna.
Under Antenna Position, you can define the position of the remote antenna, if it is not located on the site itself:
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:
650
AT332_UMR_E0
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 explorer) are calculated.
Under Total Gain, enter the gain in the forward and reverse links (DL/UL) or click Calculate to determine the actual
gain in the forward and reverse links. If you have modified any parameter in the General, Donor Side, or Coverage
Side tabs, click Apply before clicking the Calculate button.
In the forward link, the total gain is applied to each power (pilot power, SCH power, etc.).
In the reverse link, the total gain is applied to each terminal power.
The total gain takes into account losses between the donor transmitter and the remote antenna.
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 remote antenna is situated on a building, the height entered
must include the height of the 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.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
Mechanical Azimuth, Mechanical downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt display additional antenna parameters.
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.
The Additional Electrical Downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
Select a Type of feeder from the list. You can click the Browse button to access the properties of the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
Under Losses, the Loss related to repeater noise rise is displayed and you can modify the following information:
Misc. losses: You can specify additional losses in dB for Transmission and Reception.
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 4: Radio Calculations and Models.
You can update the reverse link and forward link 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 57) or its position relative to the site (see "Changing the Antenna Position Relative to the Site
Using the Mouse" on page 58).
651
Display Resolution
City Centre
5m
City
20 m
County
50 m
State
100 m
Country
The resolution specified here is only for display purposes. The calculated resolution is independently specified in the
propagation settings. For more information, see "Assigning Propagation Parameters" on page 187.
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the <GUID> and </GUID> tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
Receiver height: This displays the height of the receiver defined in the Calculation Parameters tab of the Network
Settings Properties dialog box
Comments: Specify an optional description of comment for the prediction.
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 99. The Group By and Sort buttons are not available when making a so-called
"global" coverage prediction (e.g., signal level coverage prediction).
652
AT332_UMR_E0
The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction).
At the top of the Conditions tab, you can specify the range to be considered for the current prediction.
Server: Select either All, Best Signal Level or Second Best Signal Level:
Shadowing taken into account: Select this option to consider shadowing in the prediction. For more information, see
"Modelling Shadowing" on page 730. If you select this option, you can change the Cell edge coverage probability.
Indoor coverage: Select this option to consider indoor losses. Indoor losses are defined per frequency per clutter class.
Carrier: Select the carrier to be studied or select the "Best" carrier of a frequency band or of all frequency bands. In
CDMA2000, 1xEV-DO always transmits at full power, unlike 1xRTT. Therefore, if you select "Best", the values displayed
will always be for the maximum power transmitted by the cell, in other words, the power for the 1xEV-DO carrier.
Under Field, select "Best Signal Level." "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
"Setting the Display Properties of Objects" on page 51.
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.
653
9.1.8.2.1
2. Specify the propagation parameters as explained in "Assigning Propagation Parameters" on page 187.
3. In the CDMA 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 dialog box appears.
The Prediction Types dialog box lists the coverage predictions available. They are divided into Standard Predictions,
supplied with Atoll, and Customised Predictions. Unless you have already created some customised predictions, the
Customised Predictions list will be empty.
4. Select Coverage by Signal Level (DL) and click OK. The Coverage by Signal Level (DL) Properties dialog box appears.
5. Configure the parameters in the Properties dialog box as described in "CDMA Prediction Properties" on page 652.
The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for
each pixel.
6. 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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
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 in the Network explorer. 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 (
9.1.8.2.2
).
654
AT332_UMR_E0
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 "Setting the Display Properties of Objects" on page 51.
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.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
You can run a specific prediction study displaying a coverage by pilot signal level for a given
terminal, service, mobility and carrier as explained in "Studying Pilot Signal Quality" on
page 657.
9.1.8.2.3
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
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.
9.1.8.2.4
655
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
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.
"Setting the Reverse Link Load Factor and the Forward Link Total Power" on page 656.
This section explains the coverage predictions available for analysing the signal quality and interference. The following are
explained:
9.1.8.3.1
Setting the Reverse Link Load Factor and the Forward Link Total Power
If you are setting the reverse link load factor and the forward link total power for a single transmitter, you can set these parameters on the Cells tab of the transmitters Properties dialog box. However, you can set the reverse link load factor and the
forward link total power for all cells using the Cells table.
656
AT332_UMR_E0
To set the reverse link load factor and the forward link total power using the Cells table:
1. In the Network explorer, right-click the Transmitters folder and select Cells > Open Table from the context menu. The
Cells table appears.
2. Enter a value in the following columns:
9.1.8.3.2
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 241. You must
also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the
"Best (All/Main/Second/Third 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. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab.
For a pilot signal quality prediction, the Display Type "Value Intervals" based on the Field "EcI0 (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 "Setting the Display Properties of Objects" on page 51.
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.
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 signal level: Select "Value Intervals" as the Display Type and "Ec (dBm)" as the Field.
The pilot quality relative to the EcI0 threshold: Select "Value Intervals" as the Display Type and "EcI0 Margin
(dB)" as the Field.
6. 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.
657
OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the
Calculate button (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
9.1.8.3.3
You must select a 1xRTT-capable Terminal, a 1xRTT Service, and a Mobility, as defined in "Service and User Modelling"
on page 241. You must also select a 1xRTT Carrier.
If you want the service area (EbNt) 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.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab.
For a service area (Eb/Nt) coverage prediction, the Display Type "Value Intervals" based on the Field "Max EbNt (dB)"
is selected by default. The Field you choose determines which information the service area (EbNt) forward link or
reverse link prediction makes available. Each pixel is displayed in a colour corresponding to the traffic channel quality.
For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
You can also set parameters to display the following results:
The traffic channel quality relative to the EbNt threshold: Select "Value Intervals" as the Display Type and
"EbNt 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 traffic 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.
The throughput on the forward or reverse link: Select "Discrete values" as the Display Type and "Rate (Kbps)" as
the Field.
6. 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 (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
658
AT332_UMR_E0
You must select an EV-DO-capable Terminal, an EV-DO Service, and a Mobility, as defined in "Service and User Modelling" on page 241. You must also select an EV-DO Carrier.
In order to model a multi-carrier EV-DO user, select an EV-DO Rev. B-capable Terminal, an EV-DO Rev. B Service with
the "Best Effort" QoS and "Best (1xEV-DO)" as carrier.
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.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab.
By default, the Display Type "Value Intervals" based on the Field "Max EbNt (dB)" is selected when you make a
service area (Eb/Nt) coverage prediction. For a forward link EV-DO throughput coverage prediction, you can, however,
change the display to one of the following:
The EcNt ratio: Select "Value Intervals" as the Display Type and "CI (dB)" as the Field.
The throughput on the forward link: Select "Discrete values" as the Display Type and "Rate (Kbps)" as the Field.
For multi-carrier EV-DO users, Atoll will calculate the throughput on each carrier and will display the total
throughput (i.e., the sum of the throughputs obtained on each carrier) as prediction results.
The average throughput on the forward link: This information is available when you model EV-DO Rev. A users,
single-carrier and multi-carrier EV-DO Rev. B users. Select "Discrete values" as the Display Type and "Average Rate
(Kbps)" as the Field. Atoll calculates the average EV-DO throughput on the forward link using the early termination
probabilities, defined in the terminals reception equipment, to model HARQ (Hybrid Automatic Repeat Request).
For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
6. 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 (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
9.1.8.3.4
659
3. Configure the general parameters in the Properties dialog box as described in "CDMA Prediction Properties" on
page 652.
4. Click the Conditions tab. 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 reverse
link load factor and the forward link 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 an EV-DO-capable Terminal, an EV-DO Service, and a Mobility, as defined in "Service and User Modelling" on page 241. You must also select an EV-DO Carrier.
In order to model a multi-carrier EV-DO user, select an EV-DO Rev. B-capable Terminal, an EV-DO Rev. B Service with
the "Best Effort" QoS and "Best (1xEV-DO)" as carrier.
If you want the service area (EbNt) 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.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab.
For a service area (Eb/Nt) coverage prediction, the Display Type "Value Intervals" based on the Field "Max EbNt (dB)"
is selected by default. The Field you choose determines which information the service area (EbNt) reverse link prediction makes available. Each pixel is displayed in a colour corresponding to the traffic channel quality with an uplink data
channel throughput of 9.6 kbps for EVDO Rev.0 users and 4.8 kbps for EVDO Rev. A and Rev. B users. For information
on defining display properties, see "Setting the Display Properties of Objects" on page 51.
You can also set parameters to display the following results:
The traffic channel quality relative to the EbNt threshold: Select "Value Intervals" as the Display Type and
"EbNt 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 traffic 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.
The throughput: Select "Discrete values" as the Display Type and "Rate (Kbps)" as the Field. For multi-carrier EVDO users, Atoll shares the available terminal power between each carrier in order to calculate the throughput
obtained on each carrier. It displays the results for the best configuration among all combinations of carriers, i.e.,
the combination which provides the highest total throughput.
The average EV-DO throughput: This information is available when you model EV-DO Rev. A users, single-carrier
and multi-carrier EV-DO Rev. B users. Select "Discrete values" as the Display Type and "Average Throughput
(Kbps)" as the Field. Atoll calculates the average EV-DO throughput on the reverse link using the early termination
probabilities, defined in the terminals reception equipment, to model HARQ (Hybrid Automatic Repeat Request).
6. 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 (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
9.1.8.3.5
660
AT332_UMR_E0
4. Click the Conditions tab and 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
reverse link load factor and the forward link 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 241. You must
also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the
"Best (All/Main/Second/Third band)" 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. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab.
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. In the calculations, Atoll considers 1xRTT users with
the peak FCH throughput, EVDO Rev. A users with a data channel throughput of 9.6 kbps in the reverse link and 38.4
kbps in the forward link, and EVDO Rev. B users with a data channel throughput of 4.8 kbps in the reverse and the
forward links. For information on defining display properties, see "Setting the Display Properties of Objects" on
page 51.
6. 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 (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
9.1.8.3.6
Used for Packet Services: Select the Used for Packet Services check box if the quality indicator is to be used for
data services (i.e., 1xRTT, 1xEV-DO Rev. 0, or 1xEV-DO Rev. A).
Used for Circuit Services: Select the Used for Circuit Services check box if the quality indicator is to be used for
voice services.
Measured Parameter for QI: From the list, select the parameter that will be measured to indicate quality.
QI Interpolation: Select the QI Interpolation check box if you want Atoll to interpolate between two existing QI
values. Clear the QI Interpolation check box if you want Atoll to take the closest QI value.
661
7. Ensure that a Quality Indicator has been chosen for each Service. 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 graph gives the variation of the quality indicator as a function of the measured parameter.
8. Click OK to close the reception equipment types Properties dialog box.
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 coverage prediction. How you define a coverage prediction according to the measured quality indicator,
depends several parameters:
In the following example, you will create a quality coverage prediction showing BLER, for a user on foot, and with a 1xRTT data
service.
To create a quality coverage prediction showing BLER for a user on foot, and with a 1xRTT data service:
1. In the Network explorer, right-click the Predictions folder and select New Prediction from the context menu. The
Prediction Types dialog box appears.
2. Select Service Area Analysis (EbNt) (DL) and click OK. The coverage prediction Properties dialog box appears.
3. Configure the general parameters in the Properties dialog box as described in "CDMA Prediction Properties" on
page 652.
4. Click the Conditions tab and 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
reverse link load factor and the forward link 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.
Terminal: Select the appropriate radio configuration for mobile Internet access from the Terminal list.
Service: Select "1xRTT Data" from the Service list.
Mobility: Select "Pedestrian" from the Mobility list.
Carrier: Select "1xRTT" from the Carrier list.
If you want the service area (EbNt) downlink 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. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab.
Select "Value intervals" as the Display Type and "BLER" as the Field. The exact of the field value will depend on the
name given in the Quality Indicators table. For information on defining display properties, see "Setting the Display
Properties of Objects" on page 51.
6. 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 (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Atoll calculates for each pixel the forward link traffic channel quality (EbNt) (provided when using the maximum traffic channel power allowed). Then, it calculates the corresponding BLER value from the quality graph (BLER=f(DL EbNt)). The pixel is
coloured if the condition is fulfilled (i.e., if BLER is evaluated as being higher than the specified threshold).
9.1.8.3.7
662
AT332_UMR_E0
To make a forward link total noise or forward link noise rise prediction:
1. In the Network explorer, right-click the Predictions folder and select New Prediction from the context menu. The
Prediction Types dialog box appears.
2. Select Total Noise Level Analysis (DL) and click OK. The Total Noise Level Analysis (DL) Properties dialog box appears.
3. Configure the general parameters in the Properties dialog box as described in "CDMA Prediction Properties" on
page 652.
4. Click the Conditions tab. 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 reverse
link load factor and the forward link 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 241. 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.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab.
For a forward link total noise prediction, the Display Type "Value Intervals" is selected by default. The Field you choose
determines which information the forward link total noise prediction makes available.
For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
6. 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 (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
9.1.8.3.8
663
You must select a Terminal, Service, and Mobility as defined in "Service and User Modelling" on page 241. You must
also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the
"Best (All/Main/Second/Third band)" carrier selected according to the carrier selection method defined for the site
equipment.
If you want the Pilot Pollution Analysis 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. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab.
For a Pilot Pollution Analysis, the Display Type "Value Intervals" and the Field "Number of Polluters" are selected by
default. For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
6. 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 (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
9.1.8.3.9
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
664
AT332_UMR_E0
9.1.8.3.10
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 241.
If you want the forward link total noise or forward link noise rise 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. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab. The settings you select on the Display tab determine the information that the coverage prediction will display.
ii. Select "Status" from the Field list. The coverage prediction will display the number of cells the probe mobile
is connected to and the number of sites these cells are located on.
ii. Select "Potential active transmitter nb" from the Field list. the coverage prediction will display the number of
potential active transmitters.
For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
6. 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 (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
665
9.1.8.4.1
9.1.8.4.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.
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 9.5).
9.1.8.4.3
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 91.
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 "Geographic Export Zone" on page 68.
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, 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 210.
666
AT332_UMR_E0
9.1.8.5.1
) in the Radio Planning toolbar. The Point Analysis window opens and the pointer
changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and the
current position. You can move the receiver on the map ("Moving the Receiver on the Map" on page 203).
2. Select the Reception view (
).
The predicted signal level from the 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. The name of the transmitter is followed by
the carrier number (between parentheses). 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. You can make the prediction for a specific carrier,
or select "Best (All Bands/Specific Band)" to consider the best carrier of all bands or the best carrier of a particular
band.
) to display the Calculation Options dialog box and 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. For more information, see "Taking Shadowing into Account in Point Analyses" on page 204.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class. For more information, see "Taking Indoor Losses into Account" on page 203.
5. In the Reception view toolbar, you can use the following tools:
) to copy the content of the view and paste it as a graphic into a graphic editing or word-
6. To get the details about the received signal levels and quality in the form of a table, you can use the Details view of
the Point Analysis tool (see "Obtaining Numerical Values of Signal Levels and Signal Quality" on page 669).
You can display a point analysis that uses the settings from an existing prediction by
right-clicking the prediction in the Network explorer and selecting Open Point Analysis
from the context menu.
9.1.8.5.2
667
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. For more
information, see "Taking Shadowing into Account in Point Analyses" on page 204.
Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class. For more information, see "Taking Indoor Losses into Account" on page 203.
668
The pilot quality (EcI0) of all transmitters using the selected carrier (the colour of the bar corresponds to the
colour of the transmitter on the map).
The thresholds required to enter the active set as best server and not to be rejected from the active set. The portion of the graph with the grey background indicates the transmitters in the active set.
AT332_UMR_E0
The pilot and the availability of service on the reverse link and forward link.
If there is at least one successful connection (for pilot, forward link, or reverse link), double-clicking the icons in the
right-hand frame will open a dialog box with additional information.
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.
7. In the AS Analysis view toolbar, you can use the following tools:
Click the Report button ( ) to generate a report that contains the information from the Point Analysis window.
The Analysis Report dialog box opens.
) to copy the content of the view and paste it as a graphic into a graphic editing or word-
You can display a point analysis that uses the settings from an existing prediction by
right-clicking the prediction in the Network explorer and selecting Open Point Analysis
from the context menu.
9.1.8.5.3
) in the Radio Planning toolbar. The Point Analysis window opens and the pointer
changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and the
current position. You can move the receiver on the map ("Moving the Receiver on the Map" on page 203).
2. Select the Details view.
3. Select "Cells table" from the Loads list.
4. If you are making a detailed analysis to verify a coverage prediction, you can recreate the conditions of the coverage
prediction:
a. Select the same Terminal, Mobility, Service, Carrier, DL Rate, and UL Rate 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 (All/Main/
Second/Third band)" carrier selected according to the carrier selection method defined for the site equipment.
c. 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. For more
information, see "Taking Shadowing into Account in Point Analyses" on page 204.
Select the Indoor coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class. For more information, see "Taking Indoor Losses into Account" on page 203.
Cell: The name of the cell from which the received signal levels are displayed. The cells are listed in decreasing
order of RSCP.
Distance (m): The distance from the transmitter to the current location of the pointer on the map.
Path Loss (dB): The path loss from the transmitter to the current location of the pointer on the map.
RSCP (dBm): The received pilot signal level from the transmitter to the current location of the pointer on the map.
Ec/Io (dB): The Ec/Io from the transmitter to the current location of the pointer on the map.
PN Offset: The PN offset of the transmitter.
For Speech type services:
DL Eb/Nt (dB): The downlink Eb/Nt from the transmitter to the current location of the pointer on the map.
669
UL Eb/Nt (dB): The uplink Eb/Nt from the transmitter to the current location of the pointer on the map.
For 1xRTT Data type services:
DL FCH Eb/Nt (dB): The downlink Eb/Nt over the FCH from the transmitter to the current location of the pointer
on the map.
UL FCH Eb/Nt (dB): The uplink Eb/Nt over the FCH from the transmitter to the current location of the pointer on
the map.
DL SCH Eb/Nt (dB): The downlink Eb/Nt over the SCH from the transmitter to the current location of the pointer
on the map.
UL SCH Eb/Nt (dB): The uplink Eb/Nt over the SCH from the transmitter to the current location of the pointer on
the map.
For 1xEV-DO Rev.0 Data, 1xEV-DO Rev.A Data, and 1xEV-DO Rev.B Data type services:
C/I (dB): The downlink C/I from the transmitter to the current location of the pointer on the map.
UL Eb/Nt (dB): The uplink Eb/Nt from the transmitter to the current location of the pointer on the map.
6. In the Details view toolbar, you can use the following tools:
Intersection: This display shows the area where both coverage predictions overlap (for example, pixels covered by
both predictions are displayed in red).
Merge: This display shows the area that is covered by either of the coverage predictions (for example, pixels covered
by at least one of the 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).
Value Difference: This display shows the dB difference between any two coverage predictions by signal level. This display option will not be available if the coverage predictions were calculated using different resolutions.
670
AT332_UMR_E0
A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal
Level" on page 654. The results are displayed in Figure 9.9. An area with poor coverage is visible on the right side of the figure.
Figure 9.10: 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 dialog box 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:
671
Intersection
Merge
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 9.11, shows clearly the area covered only by the new site.
672
AT332_UMR_E0
Intersection
Merge
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 9.14, shows clearly the increase in coverage due at the
change in antenna tilt.
673
Figure 9.15: CDMA intra-carrier handover area between a reference cell and a potential neighbour
Figure 9.16: CDMA inter-carrier handover area between a reference cell and a potential neighbour
674
AT332_UMR_E0
9.1.9.1.1
When it is cleared, only the defined Distance will be used to allocate neighbours to a reference transmitter.
When it is selected, click Define to open the Coverage Conditions dialog box:
Figure 9.18: CDMA coverage conditions for automatic intra-carrier neighbour allocation
Resolution: Enter the resolution to be used to calculate cells coverage areas during automatic neighbour allocation.
Global min RSCP: Enter the minimum RSCP to be provided by the reference cell and the potential neighbour. Atoll
uses the highest value between the Global min RSCP and the following:
If Global min RSCP is not defined, Atoll uses the Min RSCP in individual cells properties
If Global min RSCP is not defined and no Min RSCP is available in a cells properties, Atoll uses the Default min
Pilot RSCP threshold defined on the Calculation Parameters tab of the Network Settings Properties dialog
box.
Min EcIo: Enter the minimum EcIo 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.
675
9.1.9.1.2
T_Drop (Intra-carrier Neighbours tab): Enter the maximum difference of EcIo between reference cell A and
potential neighbour cell B in the overlapping area.
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.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this check box to take indoor losses into acccount in calculations. Indoor losses are
defined per frequency per clutter class.
When it is cleared, only the defined Distance will be used to allocate neighbours to a reference transmitter.
When it is selected, click Define to open the Coverage Conditions dialog box:
Figure 9.19: CDMA coverage conditions for automatic inter-carrier neighbour allocation
Resolution: Enter the resolution to be used to calculate cells coverage areas during automatic neighbour allocation.
Global min RSCP: Enter the minimum RSCP to be provided by the reference cell and the potential neighbour. Atoll
uses the highest value between the Global min RSCP and the following:
If Global min RSCP is not defined, Atoll uses the Min RSCP in individual cells properties
If Global min RSCP is not defined and no Min RSCP is available in a cells properties, Atoll uses the Default min
Pilot RSCP threshold defined on the Calculation Parameters tab of the Network Settings Properties dialog
box.
Margin: Enter the handover margin for all cells.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this check box to take indoor losses into acccount in calculations. Indoor losses are
defined per frequency per clutter class.
Co-site cells as neighbours: When selected, the cells located on the same site as the reference cell will be automatically considered as neighbours. A cell with no antenna cannot be considered as a co-site neighbour.
Adjacent cells as neighbours: When selected, the cells that are adjacent to the reference cell will 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 potential neighbour cell is the best server, or where the potential neighbour cell is the second best
server respecting the handover end.
Symmetric relations: Select this check box if you want the neighbour relations to be reciprocal, i.e. any reference
transmitter/cell is a potential neighbour of all the cells that are its neighbours.
Exceptional pairs: Select this check box to force the neighbour relations defined in the Intra-technology Exceptional
pairs table. For information on exceptional pairs, see "Exceptional Pairs" on page 223.
676
AT332_UMR_E0
Cause
Description
When
Distance
Coverage
Co-Site
Adjacent
(intra-carrier)
Symmetry
Exceptional Pair
Exceptional pairs
is selected
Existing
Allocating PN offsets
677
Max 1st, 2nd, and 3rd Order Neighbours: Enter the maximum costs for 1st, 2nd, and 3rd order neighbour constraint violations.
Co-planning Share: Enter the cost for inter-technology neighbour constraint violations. In 3GPP2 multi-RAT documents, this cost applies to CDMA neighbours of the same LTE cell.
Max Reuse Distance: Enter the maximum cost for reuse distance constraint violations.
Exceptional Pair: Enter the cost for exceptional pair constraint violations.
4. Click OK. The allocation constraint costs are stored and will be used in the automatic allocation.
Automatically Allocating PN Offsets to CDMA Cells
The allocation algorithm enables you to automatically allocate PN offsets 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.
678
PN Offset per Cell: The purpose of this strategy is to reduce the spectrum of allocated PN offsets the maximum possible. Atoll will allocate the first possible PN offsets in the domain.
Adjacent PN-Clusters per Site: This strategy consists of allocating one cluster of adjacent PN offsets to each base station, then, one PN offset of the cluster to each cell of each transmitter according to its azimuth. 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 PN-Clusters per Site: This strategy consists of allocating one cluster of PN offsets to each base station in
the network, then, one PN offset of the cluster to each cell of each transmitter according to its azimuth. With this
strategy, the cluster is made of PN offsets separated as much as possible. 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.
AT332_UMR_E0
Within the context of PN offset allocation, the term "PN-cluster" refers to a sub-group of
PN offsets that Atoll assigns to base stations during the allocation process. Atoll allows you
to change the number of PN offsets in a PN-cluster.
The following example explains the difference between "Adjacent PN-clusters" and
"Distributed PN-clusters".
The PILOT_INC has been set to 4 and the PN-cluster size to 3. There are:
128 PN offsets that can be allocated: they are from 4 to 508 with a separation
interval of 4.
Each PN-cluster consists of three PN offsets. Therefore, there are 42 PN-clusters
available.
If you select "Adjacent PN-cluster per site" as allocation strategy, Atoll will consider PNclusters consisted of adjacent PN offsets (e.g., {4,8,12}, {16,20,24}, ..., {496,500,504}).
If you select "Distributed PN-cluster per site" as allocation strategy, Atoll will consider PNclusters consisted of PN offsets separated as much as possible (e.g., {4,172,340},
{8,176,344}, ..., {168,336,504}).
To automatically allocate PN offsets:
1. Select the Network explorer.
2. Right-click the Transmitters folder. The context menu appears.
3. Select PN Offsets > Automatic Allocation. The PN Offsets dialog box appears.
4. Set the following parameters in the PN Offsets dialog box:
Under Constraints, you can set the constraints on automatic PN offset allocation.
PILOT_INC: The pilot PN sequence offset index increment. It is the interval between pilots, in units of 64 PNchips, of cells. The PILOT_INC value must be from 1 to 15. Atoll uses this parameter to determine the pool of
possible PN offsets (512 divided by PILOT_INC value). The first PN offset is PILOT_INC and other ones are multiples of this value.
For example: When PILOT_INC is set to 4, the pool of possible PN offsets consists of PN offsets from 4 to 508
with a separation interval of 4 (i.e., [4,8,12,16,...508]).
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 PN offset as its neighbours.
Second Order: No cell will be allocated the same PN offset as its neighbours or its second order neighbours.
Third Order: No cell will be allocated the same PN offset as its neighbours or its second order neighbours or
third order neighbours.
Atoll can only consider neighbour relations if neighbours have already been allocated. For information on allocating neighbours, see "Neighbour Planning" on page 223.
In 3GPP2 multi-RAT documents, Atoll also attempts to allocate different PN offsets to CDMA cells that are
neighbours of a common LTE cell.
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 PN offset as the reference cell. Click Define to change the overlapping
conditions. In the Coverage Conditions dialog box, you can change the following parameters:
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 EcI0 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.
T_Drop: Enter or modify the minimum EcI0 required from a transmitter not to be rejected from the active set.
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.
679
Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses in the calculations.
Indoor losses are defined per frequency per clutter class.
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 PN offset.
A reuse distance can be defined at the cell level (in the cell Properties dialog box 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 the automatic allocation process to consider the exceptional pair constraints.
PN Offset per Cell
Adjacent PN-Clusters per Site
Distributed PN-Clusters per Site
Carrier: Select the Carrier on which you want to run the allocation. You may choose one carrier (Atoll will assign
PN offsets to transmitters using the selected carrier) or all of them.
PN-Cluster Size: The number of PN offsets per cluster. This parameter is used only by the Adjacent PN-Clusters per
Site and Distributed PN-Clusters per Site allocation strategies. It should correspond to the average number of
transmitters located on a site.
Use a Max of Codes: Select the Use a Max of Codes check box to make Atoll use the maximum number of PN offsets. For example, if there are two cells using the same domain with two PN offsets, Atoll will assign the remaining
PN offset 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 PN offset in the list.
Delete Existing PN Offsets: Select the Delete Existing PN Offsets check box if you want Atoll to delete currently
allocated PN offsets and recalculate all PN offsets. If you do not select this option, Atoll will keep currently allocated PN offsets and will only allocate PN offsets to cells that do not yet have PN offsets allocated.
Allocate Carriers Identically: Select the Allocate Carriers Identically check box if you want Atoll to allocate the
same PN offset to each carrier of a transmitter. If you do not select this option, Atoll allocates PN offsets independently for each carrier.
If you need to allocate PN offsets to the cells on one transmitter, you can allocate
them automatically by selecting Allocate PN Offsets from the transmitters context
menu.
If you need to allocate PN offsets to all the cells on group of transmitters, you can
allocate them automatically by selecting Cells > PN Offsets > Automatic Allocation
from the transmitter groups context menu.
680
AT332_UMR_E0
Transmitters and cells involved in a PN offset collision are not necessarily located
inside the Focus Zone or Computation Zone, when any is defined.
Neighbours: Select Neighbours in order to check PN offset 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 PN offset as any of its neighbours.
Second Order: Atoll will check that no cell has the same PN offset as any of its neighbours or any of the neighbours
of its neighbours.
Third Order: Atoll will check that no cell has the same PN offset 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 one of these constraints. In addition, it will indicate the allocated PN offset and the neighbourhood level.
Domain Compliance: If you select the Domain Compliance check box, Atoll will check if allocated PN offsets
belong to domains assigned to cells. The report will list any cells with PN offsets that do not belong to domains
assigned to the cell.
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 among the values defined for the two cells in their properties and the value that you set in the Code Audit
dialog box. Cell pairs that do not respect the reuse distance condition are listed in increasing order of the distance
between them. The PN offset 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 PN offsets.
5. Click OK. Atoll displays the results of the audit in a text file called CodeCheck.txt, which opens at the end of the audit.
For each selected criterion, Atoll gives the number of detected inconsistencies and details each of them.
681
PN Offset: If you want to find a PN offset, select PN Offset and select it from the list.
PN Offset Group: If you want to find a PN offset group, select PN Offset 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 Find on Map tool.
Displaying PN Offset Allocation Using Transmitter Display Settings
You can use the display characteristics of transmitters to display PN offset-related information.
To display PN offset-related information on the map:
1. Select the Network explorer.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialog box appears.
4. Click the Display tab.
You can display the following information per transmitter:
PN Offset: To display the PN offset of a transmitters cell, select "Discrete values" as the Display Type and "Cells:
PN Offset" as the Field.
Ranges of PN Offsets: To display ranges of PN offsets, select "Value intervals" as the Display Type and "Cells: PN
Offset" as the Field.
PN Offset domain: To display the PN offset domain of a transmitters cell, select "Discrete values" as the Display
Type and "Cells: PN Offset Domain" as the Field.
You can display the following information in the transmitter label or tip text:
PN Offset: To display the PN offset of a transmitters cell in the transmitter label or tip text, "Cells: PN Offset" from
the Label or Tip Text Field Definition dialog box.
PN Offset domain: To display the PN offset domain of a transmitters cell in the transmitter label or tip text, "Cells:
PN Offset Domain" from the Label or Tip Text Field Definition dialog box.
5. Click OK.
For information on display options, see "Setting the Display Properties of Objects" on page 51.
Grouping Transmitters by PN Offset
You can group transmitters in the Network explorer by their PN offset or by their PN offset domain.
To group transmitters by PN offset:
1. Select the Network explorer.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialog box appears.
4. On the General tab, click Group by. The Group dialog box appears.
5. Under Available Fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
682
AT332_UMR_E0
PN Offset
PN Offset Domain
7. Click
to add the parameter to the Group these fields in this order list. The selected parameter is added to the list
of parameters on which the transmitters will be grouped. For more information on grouping objects, see "Advanced
Grouping of Data Objects" on page 96.
8. Click OK to save your changes and close the Group dialog box.
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.
Displaying the PN Offset Allocation Histogram
You can use a histogram to analyse the use of allocated PN offsets in a network. The histogram represents the PN offsets as a
function of the frequency of their use.
To display the PN offset histogram:
1. In the Network explorer, right-click the Transmitters folder and select PN Offset > PN Offset Distribution from the
context menu appears. The Distribution Histograms dialog box appears.
Each bar represents a PN offset, its height depending on the frequency of its use.
2. Move the pointer over the histogram to display the frequency of use of each PN offset. The results are highlighted
simultaneously in the Zoom on selected values list.
You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the
selected values.
Making a PN Offset Collision Zone Prediction
You can make a PN offset collision zone prediction to view areas covered by cells using the same PN offset. For each pixel,
Atoll checks if the best serving cell and the cells that fulfil all criteria to enter the active set (without any active set size limitation) have the same PN offset. If so, Atoll considers that there is a PN offset collision.
To make a PN offset collision zone prediction:
1. In the Network explorer, right-click the Predictions folder and select New Prediction from the context menu. The
Prediction Types dialog box appears.
2. Select PN Offset Collision Zones (DL) and click OK.
3. Click the General tab. On the General tab, you can change the assigned Name of the coverage prediction, the Resolution, and you can add a Comment. The Receiver height corresponds to the height of the receiver defined in the Calculation Parameters tab of the Network Settings Properties dialog box.
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the <GUID> and </GUID> tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
Under Display Configuration, you can create a Filter to select which sites to display in the results. You can also display
the results grouped in the Network explorer 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 99;
for information on grouping, see "Advanced Grouping of Data Objects" on page 96; for information on sorting, see
"Advanced Sorting" on page 98.
4. Click the Conditions tab. 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 reverse
link load factor and the forward link 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.
683
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 241. You must
also select which Carrier is to be considered.
If you want the PN offset 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.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
5. Click the Display tab.
For a PN offset collision zone prediction, the Display Type "Discrete Values" based on the Field "Transmitter" is
selected by default. Each pixel with PN offset collision is displayed with the same colour as that defined for the interfered transmitter. In the Explorer window, the coverage prediction results are ordered first by interfered transmitter
and then by interferer. For information on defining display properties, see "Setting the Display Properties of Objects"
on page 51.
You can also set parameters to display the following results:
The number of interferers for each transmitter: Select "Value Intervals" as the Display Type and "Number of
Interferers per Transmitter" as the Field. In the Explorer window, the coverage prediction results are arranged by
interfered transmitter.
The total number of interferers on one pixel: Select "Value Intervals" as the Display Type and "Number of Interferers" as the Field. In the Explorer window, the coverage prediction results are arranged according to the number
of interferers.
6. Once you have created the coverage prediction, you can run it immediately or you can save it and run 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 (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Making a PN Offset Collision Analysis
The PNO Collisions view of the Point Analysis window gives you information on the reception for any point on the map where
there is PN offset collision. PN offset collision occurs when the best serving cell and the cells that fulfil all criteria to enter the
active set (without any active set size limitation) have the same PN offset. When there is a PN offset collision, Atoll displays
the pilot quality (EcI0) received from interfered and interferer transmitters.
Analysis is based on the UL load percentage and the DL total power of cells. The analysis is provided for a user-definable probe
receiver which has a terminal, a mobility and a service.
You can make a PN offset collision analysis to review the PN offset collision zone coverage prediction. In this case, before you
make the PN offset collision analysis, you should ensure that the coverage prediction you want to use in the PN offset collision
analysis is displayed on the map.
To make a PN offset collision analysis:
1. Click the Point Analysis 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. For more
information, see "Taking Shadowing into Account in Point Analyses" on page 204.
Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class. For more information, see "Taking Indoor Losses into Account" on page 203.
684
AT332_UMR_E0
5. Move the pointer over the map to make a PN offset collision analysis for the current location of the pointer.
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.
7. Click the Point Analysis button (
Services: Services are the various services, such as voice, mobile internet access, etc., available to subscribers. For
information on modelling end-user services, see "Modelling Services" on page 241.
Mobility type: In CDMA, 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 transmitters.
EcI0 requirements and EbNt targets per radio bearer and per link (forward or reverse) are largely dependent on
mobile speed. For information on creating a mobility type, see "Modelling Mobility Types" on page 247.
Radio configuration: In CDMA, a radio configuration is the user equipment that is used in the network, for example,
a mobile phone, a PDA, or a cars on-board navigation device. In Atoll, radio configurations are modelled using terminals. For information on creating a terminal, see "Modelling Terminals" on page 249.
685
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 CDMA2000 1xRTT users, and performs
the forward link power control on the FCH and SCH and the reverse link power control on either the pilot channel or
on the FCH and SCH for 1xRTT users. For users of 1xEV-DO, Atoll performs the reverse link power control on the pilot
channel. On the forward link, Atoll performs rate control based on the CI ratio calculated for the mobile. The power
control simulation algorithm is described in "The Power Control Simulation Algorithm" on page 686.
This section explains the specific mechanisms that are used to calculation CDMA2000 traffic simulations. For information on
working with traffic simulations in Atoll, see "Simulations" on page 265
686
AT332_UMR_E0
The total forward link power of a cell is lower than the maximum power allowed,
The number of channel elements consumed on the forward link by a site is lower than the maximum number of
channel elements allowed,
The number of Walsh codes used by a cell is lower than the maximum number of Walsh codes available per cell.
Downgraded SCH throughputs cannot be lower than the FCH peak throughput. When downgrading the SCH throughput does
not solve the problem, the SCH is not allocated to the mobile. In this case, if the requirements of a mobile cannot be met by
using the FCH alone, the mobile is rejected.
At this point, users can be either connected or rejected. They are rejected if:
On the forward link, either the pilot signal level is lower than the defined minimum RSCP threshold or the pilot
quality is not high enough (no cell in the user active set): status is "EcI0 < (EcI0)min."
On the reverse link, there is not enough power to transmit: the status is "Pmob > PmobMax."
On the forward link, the quality of the received signal is not high enough on the traffic channel: the status is "Ptch >
PtchMax."
The maximum reverse link load factor is exceeded (at admission or during congestion control): the status is either
"Admission Rejection" or "UL Load Saturation."
There are not enough available channel elements on the site: the status is "Ch. Elts Saturation."
There is not enough power for cells: the status is "DL Load Saturation."
There are no more Walsh codes available: the status is "Walsh Code Saturation."
687
On the forward link, either the pilot signal level is lower than the defined minimum RSCP threshold or the pilot
quality is not high enough (no cell in the user active set): status is "EcI0 pilot < EcI0 min. pilot".
On the reverse link, there is not enough power to transmit: the status is "Pmob > Pmob max".
The obtained downlink bit rate is lower than the downlink guaranteed bit rate: the status is "Obtained DL throughput
< Guaranteed DL bit rate". This rejection cause applies to guaranteed bit rate service users only.
The maximum reverse link load factor is exceeded (at admission or during congestion control): the status is either
"Admission rejection" or "UL load saturation".
There are not enough available channel elements on the site: the status is "channel element saturation".
There are not enough MAC indexes per cell or the maximum number of EV-DO users per cell is exceeded during
the radio resource control: the status is "1xEV-DO resources saturation".
688
AT332_UMR_E0
9.2.2.2.1
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 started. 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 reverse link and forward link throughputs that all users could theoretically generate are
provided.
The breakdown per service (total number of users, number of users per activity status, and reverse link and
forward link throughputs) is given.
Results: Under Results, you will find data on the connection results:
The Sites tab: The Sites tab contains the following information per site:
Max No. of DL and UL CEs per Carrier: The maximum number of channel elements available per 1xRTT carrier on
the forward and reverse links.
Max No. of EV-DO CEs per Carrier: The maximum number of channel elements available per 1xEV-DO carrier.
No. of DL and UL FCH CEs: The number of channel elements used by the FCH on the forward and reverse links by
the site.
No. of DL and UL SCH CEs: The number of channel elements used by the SCH on the forward and reverse links by
the site.
No. EV-DO CEs: The number of channel elements used by EV-DO users.
No. of DL and UL FCH CEs Due to SHO Overhead: The number of extra channel elements due to soft handoff, on
reverse link and forward link for CDMA2000 1xRTT users.
No. of DL and UL SCH CEs Due to SHO Overhead: The number of extra channel elements due to soft handoff, on
reverse link and forward link for CDMA2000 1xRTT users.
No. of EV-DO CEs Due to SHO Overhead: The number of extra channel elements due to soft handoff, on reverse
link and forward link for CDMA2000 1xEV-DO users.
Carrier Selection: The carrier selection method 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 the reverse
link.
MUD Factor: The multi-user detection factor, defined on the site equipment, is used to decrease intra-cell interference on the reverse link.
Peak UL Throughput per 1xEV-DO service (kbps): The peak uplink throughput in kbitss for each 1xEV-DO data
service (rev. 0, rev. A, rev. B).
Peak DL FCH Throughput per service (Uplink and Downlink) (kbps): The peak throughput in kbitss for speech service and each 1xRTT data service on the FCH. The result is detailed on the forward and reverse link only when relevant.
Peak DL SCH Throughput per service (Uplink and Downlink) (kbps): The throughput in kbitss for each 1xRTT data
service on the SCH. The result is detailed on the forward and reverse link only when relevant.
The Cells (1xRTT) tab: The Cells (1xRTT) tab contains the following information, per site, transmitter, and 1xRTT
carrier:
Max Power (dBm): The maximum power as defined in the cell properties.
689
Pilot Power (dBm): The pilot power as defined in the cell properties.
Synchro Power (dBm): The synchro power as defined in the cell properties.
Paging Power (dBm): The paging power as defined in the 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 DL Power (dBm): The total transmitted power on the forward link.
Total Transmitted DL FCH Power (dBm): The total power used on the forward link for the FCH.
Total Transmitted DL SCH Power (dBm): The total power used on the forward link for the SCH.
UL Total Noise (dBm): The total noise on the reverse link.
UL Load Factor (%): The cell load factor on the reverse link corresponds to the ratio between the total interference
on the reverse link and the total noise on the reverse link. If the constraint "UL Load Factor" has been selected,
the cell load factor on the reverse link is not allowed to exceed the user-defined maximum load factor on the
reverse link (defined either in the cell properties, or in the simulation creation dialog box).
DL Load Factor (%): The load factor of the cell i on the forward link corresponds to the ratio (average interference
on the forward link [due to transmitter signals on the same carrier] for terminals in the transmitter i area)
(average total noise on the forward link [due to transmitter signals and to thermal noise of terminals] for terminals
in the transmitter i area).
DL Noise Rise (dB): The noise rise on the forward link is calculated from the load factor on the forward link. These
data indicate signal degradation due to cell load (interference margin in the link budget).
DL Load (% Pmax): The percentage of power used is determined by the total transmitted power-maximum power
ratio (power stated in W). When the constraint "DL load" is set, the DL Load can not exceed the user-defined Max
DL Load (defined either in the cell properties, or in the simulation).
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 the forward and reverse links and indicates the number of users
connected to the cell on the forward and reverse links. 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.
UL Noise Rise (dB): The noise rise on the reverse link is calculated from the load factor on the reverse link. These
data indicate signal degradation due to cell load (interference margin in the link budget).
UL Reuse Factor: The reverse link reuse factor is the ratio between the reverse link total interference and the intracell interference.
UL Reuse Efficiency Factor: The reuse efficiency factor on the reverse link is the reciprocal of the reuse factor on
the reverse link.
No. of Codes (128 bits): The total number of 128-bit Walsh codes used by cell.
No. of FCH Codes (128 bits): The total number of 128-bit Walsh codes used by the FCH of the cell.
No. of SCH Codes (128 bits): The total number of 128-bit Walsh codes used by the SCH of the cell.
The Types of Handoff as a Percentage: Atoll estimates the percentages of handoff types for each transmitter.
Atoll only lists the results for the following handoff status, no handoff (11), softer (12), soft (22), softer-soft (23)
and soft-soft (33) handoffs; the other handoff status (other HO) are grouped.
No. of DL and UL FCH CEs: The number of channel elements used by the FCH on the forward and reverse links.
No. of DL and UL SCH CEs: The number of channel elements used by the SCH on the forward and reverse links.
FCH Throughput (Uplink and Downlink) (kbps): The throughput of the FCH on the forward and reverse links.
SCH Throughput (Uplink and Downlink) (kbps): The throughput of the SCH on the forward and reverse links.
Min TCH Pwr (dBm): The minimum power allocated to a traffic channel for supplying services.
Max TCH Pwr (dBm): The maximum power allocated to a traffic channel for supplying services.
Avg TCH Pwr (dBm): The average power allocated to a traffic channel for supplying services.
Rejected Users: The number of rejected users per cell are sorted by the following reasons: Pmob > PmobMax,
Ptch > PtchMax, EcIo < (EcIo)min, UL Load Saturation, Ch. Elts Saturation, DL Load Saturation, Walsh Code Saturation, and Admission Rejection.
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 Cells (1xEV-DO) tab: The Cells (1xEV-DO) tab contains the following information, per site, transmitter, and
1xEV-DO carrier:
690
Max Power (dBm): The maximum power as defined in the cell properties.
Idle Power Gain (dB): The idle power gain as defined in the 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.
UL Total Noise (dBm): The total noise received by the cell on the reverse link.
UL Load Factor (%): The cell load factor on the reverse link corresponds to the ratio between the total interference
on the reverse link and the total noise on the reverse link. If the constraint "UL Load Factor" has been selected,
AT332_UMR_E0
the cell load factor on the reverse link is not allowed to exceed the user-defined maximum load factor on the
reverse link (defined either in the cell properties or in the simulation creation dialog box).
UL Noise Rise (dB): The noise rise on the reverse link is calculated from the load factor on the reverse link. These
data indicate signal degradation due to cell load (interference margin in the link budget).
UL Reuse Factor: The reverse link reuse factor is the ratio between the reverse link total interference and the intracell interference.
UL Reuse Efficiency Factor: The reuse efficiency factor on the reverse link is the reciprocal of the reuse factor on
the reverse link.
Number of UL Radio Links: The number of radio links on the reverse link. Multi-carrier users are counted once in
each cell they are connected to.
No. of Active Users: The number of active users connected to the cell. Multi-carrier users are counted once in each
cell they are connected to.
No. of Inactive Users: The number of inactive users among the users connected to the cell. Multi-carrier users are
counted once in each cell they are connected to.
Connection Success Rate (%): The percentage of connections that are successfully made.
The Types of Handoff as a Percentage: Atoll estimates the percentages of handoff types for each transmitter on
the reverse link. Atoll only lists the results for the following handoff status, no handoff (11), softer (12), soft (22),
softer-soft (23) and soft-soft (33) handoffs; the other handoff status (other HO) are grouped.
UL and DL Throughput (kbps): The throughput on the forward and reverse links.
No. of MAC Index: The number of MAC indexes used by the cell.
Rejected Users: The number of rejected users per cell are sorted by the following reasons: Pmob > PmobMax,
Ptch > PtchMax, EcIo < (EcIo)min, UL Load Saturation, Ch. Elts Saturation, DL Load Saturation, Walsh Code Saturation, Admission Rejection, and 1xEV-DO Resources Saturation.
Connection Success Rate (%) For Each Service: For each service, the connection success rate gives the percentage
of connected users from the total number of users of that service in the cell.
The Mobiles (1xRTT) tab: The Mobiles (1xRTT) tab contains the following information for CDMA2000 1xRTT users:
The Mobiles (1xRTT) tab only appears if, when creating the simulation as explained in
"Creating Simulations" on page 266, 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 radio configuration.
User Profile: The assigned 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.
DL and UL Requested Throughput (kbps): The downlink and uplink requested throughputs correspond to the forward and reverse throughputs requested by the user before power control.
DL and UL Obtained Throughput (kbps): The obtained throughputs are the same as the requested throughputs if
the user is connected without being downgraded. If the user has been downgraded, the throughput is calculated
using the downgrading factor. If the user was rejected, the obtained throughput is zero.
Carrier: The carrier used for the mobile-transmitter connection.
Frequency Band: The frequency band used for the mobile-transmitter connection.
Mobile Total Power (dBm): This value corresponds to the total power transmitted by the terminal.
Uplink Pilot Power (dBm): The power transmitted by the terminal on the reverse pilot channel.
Mobile FCH Power (dBm): The power transmitted by the terminal on the FCH channel.
Mobile SCH Power (dBm): power transmitted by the terminal on the SCH channel.
Connection Status: The connection status indicates whether the user is connected 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.
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, AS5, AS6: 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/Io AS1, AS2, AS3, AS4, AS5, AS6 (dB): EcI0 is given in a separate column for each cell in the active set. The Ec/
Io AS1 column lists the Ec/Io from the best server for the rejected mobiles as well.
Indoor: This field indicates whether indoor losses have been added or not.
691
The following columns only appear if, when creating the simulation as explained in "Creating Simulations" on
page 266, you select "Detailed Information About Mobiles" under Information to retain:
DL and UL Downgrading Factor (SCH): The downgrading factor for the SCH on both the forward and the reverse
links. The downgrading factor is used to calculated how much the SCH throughput will be downgraded if the
requested throughput cannot be provided.
DL Ntot AS1, AS2, AS3, AS4, AS5, AS6 (dBm): The total noise on the forward link for each link between the mobile
and a transmitter in the active set.
Cell FCH Power AS1, AS2, AS3, AS4, AS5, AS6 (DL) (dBm): The cell power transmitted on the FCH forward link is
given for each link between the mobile and a transmitter in the active set.
Cell SCH Power AS1, AS2, AS3, AS4, AS5, AS6 (DL) (dBm): The cell power transmitted on the SCH forward link is
given for each link between the mobile and a transmitter in the active set.
Load Factor AS1, AS2, AS3, AS4, AS5, AS6 (DL) (%): The load factor on the forward link for each link between the
mobile and a transmitter in the active set. It corresponds to the ratio between the total interference on the forward link and total noise at the terminal.
Noise Rise AS1, AS2, AS3, AS4, AS5, AS6 (DL) (dB): The noise rise on the forward link for each link between the
mobile and a transmitter in the active set.
Reuse Factor AS1, AS2, AS3, AS4, AS5, AS6 (DL): The forward link reuse factor is the ratio between the forward
link total interference and the intra-cell interference. It is calculated for each link between the mobile and a transmitter in the active set.
Iintra AS1, AS2, AS3, AS4, AS5, AS6 (DL) (dBm): The intra-cell interference on the forward link for each cell (I) of
the active set.
DL
DL
Iextra AS1, AS2, AS3, AS4, AS5, AS6 (DL) (dBm): The extra-cell interference on the forward link for each cell (I) of
the active set.
DL
I extra ic =
DL
P tot ic
txj j i
Total Loss AS1, AS2, AS3, AS4, AS5, AS6 (dB): The total attenuation for each link between the mobile and a transmitter in the active set.
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 Walsh 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.
DL and UL FCH SHO Gain (dB): The soft handoff gain for the FCH on the forward and the reverse link. The soft
handoff gain on the forward link is calculated if mobile receivers are connected either on the forward link or on
the forward link and the reverse link.
DL and UL SCH SHO Gain (dB): The soft handoff gain for the SCH on the forward and the reverse link. The soft
handoff gain on the forward link is calculated if mobile receivers are connected either on the forward link or on
the forward link and the reverse link.
The Mobiles (1xEV-DO) tab: The Mobiles (1xEV-DO) tab contains the following information for CDMA2000 1xEV-DO
users:
The Mobiles (1xEV-DO) tab only appears if, when creating the simulation as explained in
"Creating Simulations" on page 266, you select either "Standard information about
mobiles" or "Detailed information about mobiles" under Information to Retain.
692
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 radio configuration.
User: The assigned 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.
UL Requested Throughput (kbps): The UL Requested Throughput corresponds to the throughput, including the
control channel throughput, requested by the user before power control.
UL Obtained Throughput (kbps): For a 1xEV-DO Rev. 0 service user, the obtained throughput is the same as the
requested throughput if the user is connected without being downgraded. If the user has been downgraded, the
uplink throughput is calculated using the downgrading factor. If the user was rejected, the obtained throughput
is "0".
AT332_UMR_E0
The uplink total throughput obtained by the 1xEV-DO Rev. A and Rev. B service users depends on the service QoS
class (i.e., whether this is a guaranteed bit rate or a variable bit rate service). For a guaranteed bit rate service user,
when the user is connected, the uplink obtained throughput equals the guaranteed bit rate defined for the service.
For variable bit rate service users, the uplink obtained throughput is the same as the requested throughput. If the
user is rejected, the uplink obtained throughput is throughput is "0".
DL Peak Throughput: The maximum throughput on the forward link depends on the value of CI at the terminal.
Atoll calculates this value from the Peak throughput=f(CI) graph specified in the mobility type properties.
Carrier: The carrier used for the mobile-transmitter connection. Multi-carrier users are connected to several carriers. Details can be displayed per carrier by clicking the Actions button and then selecting Detailed Display from
the menu.
Frequency Band: The frequency band used for the mobile-transmitter connection.
Mobile Total Power (dBm): The mobile total power corresponds to the total power transmitted by the terminal.
For constant bit rate service users, the percentage of bearer consumption is taken into account.
Connection Status: The connection status indicates whether the user is connected 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.
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, AS5, AS6: 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/Io AS1, AS2, AS3, AS4, AS5, AS6 (dB): EcI0 is given in a separate column for each cell in the active set. The Ec/
Io AS1 column lists the Ec/Io from the best server for the rejected mobiles as well.
DL C/I: The CI for the pilot on the forward link.
Indoor: This field indicates whether indoor losses have been added or not.
The following columns only appear if, when creating the simulation as explained in "Creating Simulations" on
page 266, you select "Detailed information about mobiles" under Information to Retain:
UL Throughput due to TCP (kbps): The uplink throughput due to TCP aknowledgements.
UL Requested Peak Throughput (kbps): The uplink requested peak throughput corresponds to the throughput
requested by the user before power control.
UL Obtained Peak Throughput (kbps): For a 1xEV-DO Rev. 0 service user, the uplink obtained peak throughput is
the same as the requested peak throughput if the user is connected without being downgraded. If the user has
been downgraded, it is calculated using the downgrading factor. If the user was rejected, the obtained peak
throughput is zero.
The uplink peak throughput obtained by the 1xEV-DO Rev. A and Rev. B service users depends on the service QoS
class (i.e., whether this is a guaranteed bit rate or a variable bit rate service). For a guaranteed bit rate service user,
when the user is connected, the uplink obtained peak throughput equals the guaranteed bit rate defined for the
service. For variable bit rate service users, the uplink obtained peak throughput is the same as the uplink requested peak throughput. If the user is rejected, the uplink obtained peak throughput is "0".
UL Downgrading Factor: The downgrading factor on the reverse link. The downgrading factor is used to calculated
how much the throughput will be downgraded if the requested throughput cannot be provided.
DL Ntot (Data) (dBm): The total noise on the forward link.
DL Load Factor (%): The load factor on the forward link. It corresponds to the ratio between the total interference
on the forward link and total noise at the terminal.
DL Noise Rise (dB): The noise rise on the forward link.
Total Loss AS1, AS2, AS3, AS4, AS5, AS6 (dB): The total attenuation for each link between the mobile and a transmitter in the active set.
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 Walsh 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 soft handoff gain on the reverse link.
Transition flags (Upgrading 9.6k->19.2k, Upgrading 19.2k->38.4k, Upgrading 38.4k->76.8k, Upgrading
76.8k->153.6k, Downgrading 19.2k->9.6k, Downgrading 38.4k->19.2k, Downgrading 76.8k->38.4k, Downgrading 153.6k->76.8k): The boolean transition flags ("True" or "False") generated by Atoll for each throughput
transition and for each 1xEV-DO user. If the flag for a throughput transition is "True," the throughput can be
upgraded or downgraded if necessary during the uplink load control.
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 potential transmitters. Atoll selects the transmitters which
693
have the receiver in their propagation zone and have the lowest path losses. The ten transmitters with the lowest path
losses are selected and sorted in ascending order by path loss.
The Mobiles (Shadowing Values) tab only appears if, when creating the simulation as
explained in "Creating Simulations" on page 266, you select "Detailed information about
mobiles" under Information to Retain.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
9.2.2.2.2
The parameters related to the clutter classes, including the default values.
Request: Under Request, you will find data on the connection requests:
Results: Under Results, you will find data on the connection results:
694
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 started. 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 reverse link and forward link throughputs that all users could theoretically generate are
provided.
The breakdown per service (total number of users, number of users per activity status, and reverse link and
forward link throughputs) is given.
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
are determined at the end of the simulation and depend on the network design.
The number and percentage of users connected to a cell, the number of users per frequency band for multiband networks, the number of users per activity status, and the reverse link and forward link throughputs they
generate.
The breakdown per service (total number of users, number of users per frequency band for multi-band
networks, number of users per activity status, and reverse link and forward link throughputs) is given.
AT332_UMR_E0
The Cells (Average - 1xRTT) and Cells (Standard Deviation - 1xRTT) tabs: The Cells (Average - 1xRTT) and Cells (Standard Deviation - 1xRTT) tabs contain the following average and standard deviation information, respectively, per site,
transmitter, and 1xRTT carrier:
UL Total Noise (dBm): The total noise on the reverse link 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 (total interference on the reverse link) and the thermal noise.
UL Load Factor (%): The cell load factor on the reverse link corresponds to the ratio between the total interference
on the reverse link and the total noise on the reverse link. If the constraint "UL Load Factor" has been selected,
the cell load factor on the reverse link is not allowed to exceed the user-defined maximum load factor on the
reverse link (defined either in the cell properties, or in the simulation creation dialog box).
UL Noise Rise (dB): The noise rise on the reverse link is calculated from the load factor on the reverse link. These
data indicate signal degradation due to cell load (interference margin in the link budget).
UL Reuse Factor: The reverse link reuse factor is the ratio between the reverse link total interference and the intracell interference.
UL Reuse Efficiency Factor: The reverse link reuse efficiency factor is the reciprocal of the reverse link reuse factor.
DL Load Factor (%): The forward link load factor of the cell i corresponds to the ratio (forward link average interference [due to transmitter signals on the same carrier] for terminals in the transmitter i area) (forward link
average total noise [due to transmitter signals and to thermal noise of terminals] for terminals in the transmitter
i area).
DL Noise Rise (dB): The forward link noise rise is calculated from the forward link load factor. These data indicate
signal degradation due to cell load (interference margin in the link budget).
Total Transmitted DL Power (dBm): The total power transmitted on the forward link.
DL Load (% Pmax): The percentage of power used is determined by the total transmitted power-maximum power
ratio (power stated in W). When the constraint "DL load" is set, the DL Load can not exceed the user-defined Max
DL Load (defined either in the cell properties, or in the simulation).
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 the forward and reverse links and indicates the number of users
connected to the cell on the forward and reverse links. 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.
No. of Codes (128 bits): The average number of 128-bit Walsh codes used per cell.
The types of handoff as a percentage: Atoll estimates the percentages of handoff types for each transmitter. Atoll
only lists the results for the following handoff status, no handoff (11), softer (12), soft (22), softer-soft (23) and
soft-soft (33) handoffs; the other handoff status (other HO) are grouped.
FCH Throughput (Uplink and Downlink) (kbps): The throughput of the FCH on the forward and reverse links.
SCH Throughput (Uplink and Downlink) (kbps): The throughput of the SCH on the forward and reverse links.
Min TCH Pwr (dBm): The minimum power allocated to a traffic channel for supplying services.
Max TCH Pwr (dBm): The maximum power allocated to a traffic channel for supplying services.
Avg TCH Pwr (dBm): The average power allocated to a traffic channel for supplying services.
Rejected Users: The number of rejected users per cell are sorted by the following reasons: Pmob > PmobMax,
Ptch > PtchMax, EcIo < (EcIo)min, UL Load Saturation, Ch. Elts Saturation, DL Load Saturation, Walsh Code Saturation, and Admission Rejection.
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 Cells (Average - 1xEV-DO) and Cells (Standard Deviation - 1xEV-DO) tabs: The Cells (Average - 1xEV-DO) and Cells
(Standard Deviation - 1xEV-DO) tabs contain the following average and standard deviation information, respectively,
per site, transmitter, and 1xEV-DO carrier:
UL Total Noise (dBm): The total noise on the reverse link 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 (total interference on the reverse link) and the thermal noise.
UL Load Factor (%): The cell load factor on the reverse link corresponds to the ratio between the total interference
on the reverse link and the total noise on the reverse link. If the constraint "UL Load Factor" has been selected,
the cell load factor on the reverse link is not allowed to exceed the user-defined maximum load factor on the
reverse link (defined either in the cell properties, or in the simulation creation dialog box).
UL Noise Rise (dB): The noise rise on the reverse link is calculated from the load factor on the reverse link. These
data indicate signal degradation due to cell load (interference margin in the link budget).
UL Reuse Factor: The reverse link reuse factor is the ratio between the reverse link total interference and the intracell interference.
UL Reuse Efficiency Factor: The reverse link reuse efficiency factor is the reciprocal of the reverse link reuse factor.
Number of UL Radio Links: The number of radio links on the reverse link.
Connection Success Rate (%): The percentage of connections that are successfully made.
The types of handoff as a percentage: Atoll estimates the percentages of handoff types for each transmitter. Atoll
only lists the results for the following handoff status, no handoff (11), softer (12), soft (22), softer-soft (23) and
soft-soft (33) handoffs; the other handoff status (other HO) are grouped.
695
UL and DL Throughput (kbps): The throughput on the forward and reverse links.
No. of MAC Index: The number of MAC indexes used by the cell.
Rejected Users: The number of rejected users per cell are sorted by the following reasons: Pmob > PmobMax,
Ptch > PtchMax, EcIo < (EcIo)min, UL Load Saturation, Ch. Elts Saturation, DL Load Saturation, Walsh Code Saturation, Admission Rejection, and 1xEV-DO Resources Saturation.
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 parameters related to the clutter classes, including the default values.
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 can be saturated.
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, Mobility, Carrier, and DL and UL Throughputs.
696
AT332_UMR_E0
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.
Pilot Quality Analysis (DL): For information on making a Pilot Quality Analysis, see "Studying Pilot Signal Quality"
on page 657.
Service Area Analysis (Eb/Nt) (DL): For information on making a coverage prediction on the forward link service
area, see "Studying 1xRTT Forward and Reverse Link Service Areas (EbNt)" on page 658 or "Studying the Forward
Link EV-DO Throughput" on page 659.
Service Area Analysis (Eb/Nt) (UL): For information on making a coverage prediction on the reverse link service
area, see "Studying 1xRTT Forward and Reverse Link Service Areas (EbNt)" on page 658 or "Studying 1xEV-DO
Reverse Link Service Area (EbNt)" on page 659.
Effective Service Area Analysis (Eb/Nt) (DL+UL): For information on making a pilot pollution coverage analysis,
see "Studying the Effective Service Area" on page 660.
Coverage by Total Noise Level (DL): For information on making a forward link total noise coverage prediction, see
"Studying Forward Link Total Noise" on page 662.
Pilot Pollution Analysis (DL): For information on making a pilot pollution coverage analysis, see "Studying Pilot
Pollution" on page 663.
Handoff Zones (DL): For information on making a handoff status coverage prediction, see "Making a Handoff
Status Coverage Prediction" on page 665.
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:
1. Click the Conditions tab.
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: 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.
697
You can also create the following objectives from the context menu of Objectives in the left-hand pane of the Objectives tab:
You define the optimisation objectives using the Objectives tab of the ACP Setup dialog box. For information on setting objective parameters, see "Setting Objective Parameters" on page 1329.
698
AT332_UMR_E0
Signal level
EcIo
Overlap
Best Server Distance
1st-2nd Difference
1st-Nth Difference
If you base the evaluation of a qualiy analysis prediction on a calculated Atoll prediction, ACP will use the display settings of the calculated Atoll prediction in the
qualiy analysis prediction calculated for that objective.
If you saved the display settings of a qualiy analysis prediction as defaults, or if you
are using a configuration file for ACP, these display settings will be used by default
and will override the display settings of the calculated Atoll prediction. For more
information on changing the display settings of a quality analysis prediction, see
"Changing the Display Properties of ACP Predictions" on page 1379.
Signal Level
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by signal level.
Base prediction settings on > "Coverage by Signal Level (DL)": ACP will evaluate coverages by signal level based
on the parameters used to calculate the selected "Coverage by Signal Level (DL)" prediction in Atoll.
Only the coverage predictions displaying a "Best Signal Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": if you select this option, you can Enable shadowing margin
and define a Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no
clutter information available, default values are used.
699
EcIo
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by Ec/Io.
Base prediction settings on > "Pilot Quality Analysis (DL)": ACP will evaluate coverages by signal level based on
the parameters used to calculate the selected "Pilot Quality Analysis (DL)" prediction in Atoll.
Base prediction settings on > Manual configuration: If you select this option, you can Enable shadowing margin
and define a 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. Additionally, you can specify:
Service and Terminal that will be used during the calculation of EcIo through gain and losses (i.e., the service
body loss, the gain and loss of the terminal antenna, and the terminal noise factor).
Overlap / 1st-Nth
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by overlapping zones or by 1stNth difference.
Overlap
Base prediction settings on > "Overlapping Zones (DL)": ACP will evaluate coverages by overlapping based on
the parameters used to calculate the selected "Overlapping Zones (DL)" prediction in Atoll.
Only the Atoll predictions displaying a "Number of Servers" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": If you select this option, you can set a Minimum signal
level and a Threshold margin.
1st-Nth
Base prediction settings on > "Overlapping Zones (DL)": ACP will evaluate coverages by 1st-Nth difference
based on the parameters used to calculate the selected "Overlapping Zones (DL)" prediction in Atoll.
Since there are no Atoll prediction types equivalent to ACPs CDMA 1xRTT 1st-Nth Difference and CDMA EvDO 1st-Nth Difference objectives, the parameters recovered by ACP from the selected Atoll predictions are
limited to the minimum signal level and the shading. The number of servers must always be specified manually
next to No. servers.
Manual configuration: If you select this option, specify a Minimum signal level and the No. servers.
In both cases, the value you specify next to No. servers determines "Nth" in the CDMA 1xRTT 1st-Nth Difference and CDMA Ev-DO 1st-Nth Difference objectives. For instance if you set No. servers to 4, then the "1st4th Difference" quality parameter will be automatically selected by default in the Quality column of the CDMA
1xRTT 1st-Nth Difference and CDMA Ev-DO 1st-Nth Difference properties pages.
- Allowed values for No. servers range from 3 to 100, with only one value available per technology.
- The "1st-2nd Difference" quality parameter (based on No. servers = 2) is provided by default.
Figure 9.23: ACP Quality Analysis Prediction Types for a CDMA Network
700
AT332_UMR_E0
ACP quality analysis predictions are equivalent to some of Atolls coverage predictions. The following table lists the quality
analysis predictions available in ACP for LTE and the equivalent LTE coverage predictions in Atoll.
Signal Level
EcIo
Overlap
1st-Nth Difference
N/A
(1) For more information, see "Making a Coverage Prediction by Signal Level" on page 654.
(2) For more information, see "Creating Coverage Predictions on Drive Test Data Paths" on page 708.
(3) For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 655.
Making these predictions 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. ACP predictions 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 predictions 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 analysis.
ACP-generated predictions 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-carrier optimisation is supported in CDMA. However the predictions are provided separately for each carrier.
Even after committing the optimisation results, differences can remain between ACP and Atoll predictions.
You can view the exact signal level and EcIo values on any pixel by letting the pointer rest over the pixel. The signal level or
EcIo value is then displayed in tip text.
For ACP overlapping zones predictions, you can:
For each network quality coverage prediction, ACP offers a prediction showing the initial network state, the final network
state, and a prediction showing the changes between the initial and final state.
701
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 that identifies scanned cells (for example, serving cells, neighbour cells, or any other cells). Cells may be
identified by their IDs or PN offsets.
The data in the file must be structured so that the columns identifying the PN offset group and the PN offset are placed before
the data columns for each cell. Otherwise Atoll will not be able to properly import the file.
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:
1. Select the Network explorer.
2. Right-click the Drive Test Data folder. The context menu appears.
3. Select Import from the context menu. The Open dialog box 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 dialog box 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 dialog box.
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 dialog box. 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 dialog box, 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,
702
AT332_UMR_E0
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 9.24).
Figure 9.24: The Setup tab of the Import of Measurement Files dialog box
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 dialog box 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.
ii. In the By ID identifier box, enter a string found in the column name that identifies the cell Ids of scanned cells.
For example, if the string "Cell_ID" is found in the column names that identify the cell ID of scanned cells, enter
it here. Atoll will then search for the column with this string in the column name.
e. If you are importing data that uses the PN offset as cell identifier:
i.
ii. In the PN offset identifier box, enter a string that is found in the column names identifying the PN offset of
scanned cells. For example, if the string "PN" is found in the column names identifying the PN offset of scanned
cells, enter it here. Atoll then searches for columns with this string in the column name.
iii. In the PN offset format list, select the PN offset format, "Decimal" or "Hexadecimal."
iv. In the PN offset group identifier box, enter a string that must be found in the column names identifying the
PN offset group of scanned cells. For example, if the string "PN_Group" is found in the column names identifying the PN offset group of scanned cells, enter it here. Atoll will then search for columns with this string in
the column name.
If there is no PN offset group information contained in the drive test data file, leave the PN offset group identifier box empty.
703
v. If you are importing drive test data for a specific carrier, select the carrier for which you are importing the drive
test data in the Carrier number list. If you are importing drive test data for more than one carrier, select "All".
f. Click OK to close the Drive Test Data Setup dialog box.
If you have correctly entered the information under File on the Setup tab, and the
necessary values in the Drive Test Data Setup dialog box, Atoll should recognise 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.
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 dialog box 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 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 dialog box.
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.
704
AT332_UMR_E0
To display the Display tab of a drive test data paths Properties dialog box:
1. Select the Network explorer.
2. Click the Expand button ( ) to expand the Drive Test Data folder.
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,
5. Click the Display tab.
Each point can be displayed by a unique attribute or according to:
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 dialog box opens in which you can define the following display for
each single point of the measurement path:
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 in the Network explorer 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 dialog box and select Save or Load from
the Display Configuration submenu.
"Filtering Incompatible Points Along Drive Test Data Paths" on page 705
"Creating Coverage Predictions on Drive Test Data Paths" on page 708
"Displaying Statistics Over a Drive Test Data Path" on page 709
"Extracting a Field From a Drive Test Data Path for a Transmitter" on page 710
"Analysing Data Variations Along the Path" on page 710.
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 path.
705
3. Select Filter from the context menu. The Drive Test Data Filter dialog box appears.
4. In the Per Clutter 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 permenantly 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:
1. Select the Network explorer.
2. In the Network explorer, 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.
706
Formula
=X
<> X
<X
>X
<=X
>=X
*X*
AT332_UMR_E0
Formula
*X
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 how filters work, see "Advanced Data
Filtering" on page 101.
You can permanently delete the points that do not fulfil the filter conditions by selecting
the Delete points outside the filter check box.
Figure 9.27: Selecting measured signal levels for which errors will be calculated
7. Click OK. A new point prediction is created for the selected drive test data path.
8. Right-click the drive test data path. The context menu appears.
9. Select Calculations > Calculate All the Predictions from the context menu.
707
If you chose to have Atoll calculate the errors between measured and predicted signal levels, new columns are added to the
drive test data table for the predicted point signal level from the serving cell and the errors between the measured and
predicted values.
Figure 9.28: Drive Test Data table after Point Signal Level Prediction (with error calculations)
New columns are also added for the predicted point signal level from each neighbour cell and the errors between the
predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For
more information on the Drive Test Data analysis tool, see "Analysing Data Variations Along the Path" on page 710.
The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main
matrix. For more information on propagation models, see Chapter 4: Radio Calculations and Models.
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 241.
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
account check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency
per clutter class.
708
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 an Overlap 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. Indoor losses are defined per frequency per clutter class. 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.
AT332_UMR_E0
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 241.
You must also select which Carrier is to be considered.
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.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency
per clutter class.
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 241.
You must also select which Carrier is to be considered.
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.
You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency
per clutter class.
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
context menu appears.
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 4: Radio Calculations and
Models).
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 710.
709
9.4.4.5 Extracting a Field From a Drive Test Data Path for a Transmitter
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:
1. Select the Network explorer.
2. Click the Expand button ( ) to expand the Drive Test Data folder.
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 dialog box
appears.
5. Select one or more transmitters from the For the Transmitters list.
6. Select the fields that contain the previously predicted values that you want to use for predictions. Only one type of
value can be compared at a time (signal level or quality).
7. Select the fields that contain the measured values that you want to use for predictions. 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 popup 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.
9.4.4.6 Extracting a Field From a Drive Test Data Path for a Transmitter
You can extract the information from a specific field for a given transmitter on each point of an existing drive test data path.
The extracted information will be added to a new column in the drive test data table.
To extract a field from a drive test data path:
1. Select the Network explorer.
2. Click the Expand button ( ) to expand the Drive Test Data folder.
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 Selection for a Given Transmitter dialog box 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 extract for the selected transmitter.
8. Click OK. Atoll creates a new column in the drive test data path table for the selected transmitters and with the
selected values.
710
AT332_UMR_E0
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 dialog box.
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:
711
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 9.29 on page 711). 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 "Setting the Display Type" on page 52.
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 dialog box. 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 dialog box.
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 on one end of the range of data you want to zoom in on.
712
AT332_UMR_E0
713
Select File > Open or File > New > From an Existing Database.
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.
714
AT332_UMR_E0
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, 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, because working document is the main document, any changes made in the main document are not automatically taken into account in the linked document.
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 107. 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
"Associating a Tip Text to an Object" on page 54.
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 "Changing the Order of
Layers" on page 51.
Figure 9.31 shows an example of CDMA transmitters with labels and displayed in the Legend window, and GSM transmitter
data displayed in tip text.
715
) in the toolbar.
When you click the Calculate button, Atoll first 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 and Unlocking Coverage Predictions" on page 207.
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:
) 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.
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.
9.5.2.2.1
716
AT332_UMR_E0
Coverage Prediction by Transmitter" on page 655 and "Studying Signal Level Coverage of a Single Base Station" on
page 654.
2. Create and calculate a Coverage by Transmitter (DL) (best server with 0 dB overlap margin) coverage prediction and
a Coverage by Signal Level (DL) 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 dialog box.
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 714.
5. Optimise the main network by changing parameters such as antenna azimuth and tilt or the pilot power.
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 717 and "Studying Differences Between Coverage Areas" on page 718.
7. Calculate the linked coverage predictions again to study the effects of the changes on the linked coverage predictions.
9.5.2.2.2
9.5.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.
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 9.5). 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.
9.5.2.2.4
717
9.5.2.2.5
718
AT332_UMR_E0
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:
1. Click the main documents map window.
2. Select the Network explorer.
3. Right-click the Transmitters folder of the main document. The context menu appears.
4. Select Apply Current Configuration from the context menu.
Figure 9.33: 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 Apply Configuration and have to be set up manually.
When it is disabled, only the defined Distance will be used to allocate neighbours to a reference transmitter.
When it is enabled, there are two cases:
"Coverage Conditions when CDMA is the Source Technology" on page 720
"Coverage Conditions when CDMA is the Target Technology" on page 720
719
9.5.4.1.1
Figure 9.34: CDMA coverage conditions for automatic inter-technology neighbour allocation (CDMA is source technology)
9.5.4.1.2
Resolution: Enter the resolution to be used to calculate cells coverage areas during automatic neighbour allocation.
Global min RSCP: Enter the minimum RSCP to be provided by the reference cell and the potential neighbour. Atoll
uses the highest value between the Global min RSCP and the following:
If Global min RSCP is not defined, Atoll uses the Min RSCP in individual cells properties
If Global min RSCP is not defined and no Min RSCP is available in a cells properties, Atoll uses the Default min
Pilot RSCP threshold defined on the Calculation Parameters tab of the Network Settings Properties dialog
box.
Min EcIo: Enter the minimum EcIo 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.
Handover margin: Enter the maximum difference of Ec/Io between reference cell A and possible neighbour cell B
in the overlapping area. You can select whether Atoll should use a Global value of the handover margin for all the
cells, or the handover margins Defined per cell.
Max EcIo: If you want, you can select this check box then enter the maximum difference of EcIo between reference cell A and potential neighbour cell B in the overlapping area.
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.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this check box to take indoor losses into acccount in calculations. Indoor losses are
defined per frequency per clutter class.
Figure 9.35: CDMA coverage conditions for automatic inter-technology neighbour allocation (CDMA is target technology)
Similar to "Coverage Conditions when CDMA is the Source Technology" on page 720 without the Max Ec/Io field.
720
Co-site neighbours: cells located on the same site as the reference transmitter will automatically be considered as
neighbours. A transmitter/cell with no antenna cannot be considered as a co-site neighbour.
AT332_UMR_E0
Exceptional pairs: Select this check box to force the neighbour relations defined in the Inter-technology Exceptional
pairs table. For more information, see "Exceptional Pairs" on page 223.
Description
When
Distance
Coverage
Co-Site
Exceptional Pair
Exceptional pairs
is selected
Existing
721
4. Right-click the setup you created in "Creating a New Co-planning Optimisation Setup" on page 721. 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.
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 1359. For
information on the optimisation results, see "Viewing Optimisation Results" on page 1362.
722
AT332_UMR_E0
"Creating PN Offset Domains and Groups for PN Offset Allocation" on page 732
"Modelling Inter-technology Interference" on page 733.
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.
Name: Enter a name for the frequency, for example, "Band 1900." This name will appear in other dialog boxes
when you select a frequency band.
Bandwidth (MHz): Enter the bandwidth for each carrier in the frequency band.
DL Start Frequency (MHz): Enter the downlink start 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.
Step: Enter the step between any two consecutive carrier numbers in the frequency band.
Excluded Carriers: Enter the carrier numbers which do not belong to the frequency band. You can enter non-consecutive carrier numbers separated with a comma, or you can enter a range of carrier numbers separating the first
and last index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
723
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 1900: First carrier: 0; Last carrier 1 and Band 700: First carrier: 2 and
Last carrier: 2
7. When you have finished adding frequency bands, click the Close button (
).
For example, if you wish to define the 1900 MHz Band and the corresponding CDMA channel numbers (25, 50, 75), you can
set:
You can also access the properties dialog box of each individual frequency band by double-clicking the left margin of the row
with the frequency band.
724
DL Powers: Under DL Powers, you can define whether the power values on the forward link are Absolute or Relative
to Pilot. The power values affected are the synchronisation power and the paging power defined in the cell properties
and the TCH power in 1xRTT and Speech service properties. Atoll automatically converts the power values defined in
the cell properties (i.e., synchronisation channel and paging powers) when changing the option. On the other hand,
the values for the TCH powers have to be modified manually.
DL Load: Under DL Load, you can define whether the total power values on the forward link are Absolute or a percentage of the maximum power (% Pmax). Atoll automatically converts the total power values when changing the
option.
UL 1xRTT Power Control Based On: Under UL 1xRTT Power Control Based On, you can define whether the reverse
link power control for the 1xRTT network is based on Traffic Quality or Pilot Quality.
Interferences: Under Interferences, you can define the method used to calculate interference on the forward link
(Nt):
AT332_UMR_E0
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 reverse link.
Default UL Macro-Diversity Gain: You can set a default value for the reverse link gain due to macro-diversity on
soft and soft-soft handoffs. 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 reverse link macro-diversity gain, based on the
standard deviation value of EbNt on the reverse link defined per clutter class.
+MRC in Softer/Soft: If you select the +MRC (maximal ratio combining) in Softer/Soft check box, Atoll selects the
serving cell during a softer/soft handoff by recombining the signal of co-site transmitters and multiplying the
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.
Calculation limitation: Under Calculation limitation, you can define the following data:
Min. interferer reception threshold: This value is used by Atoll to limit the input of interferers in calculations. The
performance of CDMA-specific coverage predictions and Monte Carlo simulations can be improved by setting a
high value for the 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.
Default min. pilot RSCP threshold: The default minimum pilot RSCP required for a user to be connected to the
cell. The pilot RSCP is compared with this threshold to determine whether or not a user can be connected to the
cell.
A minimum pilot RSCP threshold can be defined at the cell level (in the cell Properties
dialog box or in the Cells table). If defined, a cell-specific minimum pilot RSCP threshold will
be used instead of the value entered here.
Receiver: Under Receiver, you can enter the Height of the receiver.
Default max range: The maximum coverage range of transmitters in the network.
725
Service
Reverse Link
Forward Link
Speech
N FCH *
N FCH
1xRTT Data
N FCH
N FCH
3 X N FCH
3 X N FCH
5 X N FCH
5 X N FCH
9 X N FCH
9 X N FCH
17 X N FCH
17 X N FCH
9.6
38.4
19.2
76.8
38.4
153.6
76.8
307.6
153.6
614.4
921.6
1228.8
1843.2
2457.6
1xEV-DO Rev. A Data
4.8
4.8
9.6
9.6
19.2
19.2
38.4
38.4
76.8
76.8
115.2
115.2
153.6
153.6
230.4
230.4
307.2
307.2
460.8
460.8
614.4
614.4
921.6
921.6
1228.8
1228.8
1848.2
1848.2
2457.6
3072.0
726
AT332_UMR_E0
Radio Bearer Index: You can modify the index number of the radio bearer. This index number is used to identify
the 1xEV-DO forward link radio bearer. If you are creating a new 1xEV-DO forward link radio bearer, enter an index
number in the row marked with the New Row icon (
).
Transport Block Size (bits): Enter or modify the packet size in bits transmitted in one timeslot.
Peak RLC Throughput (kbps): Enter or modify the peak RLC throughput in kbits per second.
Radio Bearer Index: You can modify the index number of the radio bearer. This index number is used to identify
the 1xEV-DO reverse link radio bearer. If you are creating a new 1xEV-DO reverse link radio bearer, enter an index
number in the row marked with the New Row icon (
).
Transport Block Size (bits): Enter or modify the packet size in bits transmitted in one subframe (4 timeslots).
Peak RLC Throughput (kbps): Enter or modify the peak RLC throughput in kbits per second.
Name: The name you enter will be the one used to identify this piece of equipment.
727
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 (when 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 coverage predictions (AS analysis and coverage predictions). Choose one of the following:
Min. UL Load Factor: The carrier with the minimum reverse link noise (carrier with the lowest reverse link load
factor) is selected.
Min. DL Total Power: The carrier with the minimum forward link 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 reverse link load factor is reached, the second carrier is chosen and so on.
Downlink and Uplink Overhead Resources for Common Channels/Cell: The reverse link and forward link overhead resources for common channels/cell correspond to the number of channel elements that a cell uses for
common channels in the forward and the reverse link. This setting is also used for Walsh code allocation; it indicates the number of Walsh 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.
Pool of Shared CEs: Select this option if you want all cells on the site to share channel elements.
Power Pooling Between Transmitters: Select this option if you want all cells on the site to share power on the
traffic channels.
9.6.7.2 Defining Channel Element Consumption per CDMA Site Equipment and
Radio Configuration
The number of channel elements consumed by a user depends on the site equipment, on the radio configuration, and the link
direction (forward or reverse). The number of channel elements consumed can be defined for CDMA simulations.
To define channel element consumption during CDMA simulations:
1. Select the Parameters explorer.
2. Click the Expand button ( ) to expand the Network Settings folder.
3. Click the Expand button ( ) to expand the Radio Resource Management folder.
4. Right-click CE Consumption. The context menu appears.
5. Select Open Table from the context menu. The CE Consumption table appears.
6. For each equipment-radio configuration pair, enter in the CE Consumption table the number of reverse link and forward link channel elements that Atoll will consume during the power control simulation.
7. Click the Close button (
728
AT332_UMR_E0
5. Click the General tab. On the General tab, you can define the Name of the reception equipment.
6. Click the Quality Graphs tab.
7. Ensure that a Quality Indicator has been chosen for each Service. 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
coverage predictions.
8. Click the 1xEV-DO Radio Bearer Selection (Downlink) tab.
9. Enter the Required CI (dB), the Modulation used (you can choose between QPSK, 8PSK, 16QAM, or 64QAM) and the
Early Termination Probabilities for each Radio Bearer Index, with Mobility and No. of Slots. The radio bearer index
with the number of timeslots and the modulation indicates the downlink transmission format.
The Required C/I values are used in simulations and in the Service Area Analysis (Eb/Nt) (DL) coverage prediction to
select the downlink 1xEV-DO radio bearer and then to calculate the throughput provided on downlink. A downlink
1xEV-DO radio bearer is selected only if the user terminal supports the modulation required by the radio bearer. 1xEVDO Rev. A-capable terminals support 16QAM modulation while 1xEV-DO Rev. B-capable terminals can support
16QAM and 64QAM modulations.
The Early Termination Probabilities are used in the Service Area Analysis (Eb/Nt) (DL) coverage prediction to calculate
the average 1xEV-DO throughput when HARQ (Hybrid Automatic Repeat Request) is used.
10. Click the 1xEV-DO Radio Bearer Selection (Uplink) tab.
11. Enter the following for each Radio Bearer Index with Mobility and No. of Subframes:
Required EcNt (High Capacity) (dB): The Ec/Nt required for services with high capacity uplink mode.
Required EcNt (Low Latency) (dB): Ec/Nt required for services with low latency uplink mode.
Early Termination Probabilities
Modulation: The modulation used. You can choose between QPSK, 8PSK, 16QAM or 64QAM.
The Required Ec/Nt values are used in simulations and in the Service Area Analysis (Eb/Nt) (UL) coverage prediction
to select the uplink 1xEV-DO radio bearer and then to calculate the throughput provided on uplink. An uplink 1xEV-DO
729
radio bearer is selected only if the user terminal supports the modulation required by the radio bearer. 1xEV-DO
Rev. A-capable terminals support 16QAM modulation while 1xEV-DO Rev. B-capable terminals support the 16QAM
and 64QAM modulations. The Early Termination Probabilities are used in the Service Area Analysis (Eb/Nt) (UL) coverage prediction to calculate the average 1xEV-DO throughput when HARQ (Hybrid Automatic Repeat Request) is used.
12. Click OK to close the reception equipment types Properties dialog box.
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 637. For a description of the properties of a
cell, see "Cell Properties" on page 633.
The pilot quality of the transmitter must exceed a threshold. The threshold depends both on the type of carrier and
the mobility type. It is equal to the sum of T_Drop defined in the properties of the best server and the Delta T_Drop
defined in the properties of the mobility type.
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 727.
For multi-carrier EVDO Rev. B users, the active set can consist of several sub-active sets, each one being associated with one
carrier. The number of sub-active sets depends on the maximum number of carriers supported by the terminal. As described
earlier, the quality of the pilot (EcI0) determines whether or not a transmitter can belong to a sub-active set. The sub-active
set associated with the best carrier is the same as the active set of a single-carrier user. For other carriers, the uplink EcNt
received by the best server on the best carrier and on the studied carrier determines whether or not a carrier can have a subactive set, and the transmitters in the sub-active sets depend on the mode supported by the terminal (locked mode or
unlocked mode):
The Ec/Nt received by the best serving transmitter on the best carrier must exceed the minimum uplink Ec/Nt.
The Ec/Nt received by the best serving transmitter on the studied carrier must exceed the minimum uplink Ec/Nt.
When locked mode is used, the serving transmitters must be the same in all sub-active sets. With unlocked mode, the
serving transmitters can be different from one sub-active set to another.
730
AT332_UMR_E0
the model standard deviation and the EcI0 and EbNt standard deviations for each clutter class or for all clutter classes, see
"Defining Clutter Class Properties" on page 127.
Shadowing can be taken into consideration when Atoll calculates the signal level, EcI0, and EbNt for:
A point analysis (see "Studying the Profile Around a Base Station" on page 642)
A coverage prediction (see "Studying Signal Level Coverage of a Single Base Station" on page 654).
Atoll always takes shadowing into consideration when calculating a Monte Carlo-based CDMA 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 731.
9.6.10.1 Displaying the Shadowing Margins and Macro-diversity Gain per Clutter
Class
To display the shadowing margins and macro-diversity gain per clutter class:
1. Select the Network explorer.
2. Right-click the Predictions folder. The context menu appears.
3. Select Shadowing Margins from the context menu. The Shadowing Margins and Gains dialog box appears (see Figure
9.36).
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 dialog box is for information only.
Standard Deviation: Select the type of standard deviation to be used to calculate the shadowing margin or macrodiversity gains:
From Model: The model standard deviation. Atoll will display the shadowing margin of the signal level.
EcI0: The EcI0 standard deviation. Atoll will display the EcI0 shadowing margin and the resulting forward
link 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.
UL EbNt: The EbNt reverse link standard deviation. Atoll will display the EbNt reverse link shadowing margin
and the resulting reverse link 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 EbNt forward link standard deviation. Atoll will display the EbNt forward link shadowing
margin.
5. If you select "EcI0" or "EbNt UL" as the standard deviation 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 "EcI0" as the standard deviation under Standard Deviation, enter
the allowed EcI0 difference between the best server and the second one. This value is used to calculate forward
link macro-diversity gains. If you selected "EbNt UL" as the standard deviation under Standard Deviation, enter
the allowed Eb/Nt difference between the best server and the second one. This value is used to calculate reverse
link macro-diversity gains.
2nd - 3rd Best Signal Difference: If you selected "EcI0" as the standard deviation under Standard Deviation, enter
the allowed EcI0 difference between the second-best server and the third one. This value is used to calculate forward link macro-diversity gains. If you selected "EbNt UL" as the standard deviation under Standard Deviation,
enter the allowed EbNt difference between the second-best server and the third one. This value is used to calculate reverse link macro-diversity gains.
6. Click Calculate. The calculated shadowing margin is displayed. If you selected "EcI0" or "EbNt 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 dialog box.
731
7. Click 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 dialog box appears.
9. Under Groups, enter the following information for each group you want to create. The definition of the group must
be consistent with the default domain defined using the PILOT_INC parameter.
10. Click in another cell of the table to create the new group and add a new blank row to the table.
732
AT332_UMR_E0
Interference received by mobiles on the downlink: Interference can be received by mobiles in a CDMA network on
the downlink from external base stations and mobiles in the vicinity.
Interference from external base stations (also called downlink-to-downlink interference) can 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.
Interference from external mobiles (also called uplink-to-downlink interference) can be created by insufficient separation between the uplink frequency used by the external network and the downlink frequency used by your CDMA
network. Such interference may also come from co-existing TDD networks. The effect of this interference is modelled
in Atoll using the Additional DL Noise Rise definable for each cell in the CDMA 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 Additional DL Noise Rise, see "Cell Properties" on page 633.
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 Noise" on page 664.
Interference received by cells on the uplink: Interference can be received by cells of a CDMA network on the uplink
from external base stations and mobiles in the vicinity.
Interference from external base stations (also called downlink-to-uplink interference) can be created by insufficient
separation between the downlink frequency used by the external network and the uplink frequency used by your
CDMA network. Such interference may also come from co-existing TDD networks.
Interference from external mobiles (also called uplink-to-uplink interference) can 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 Additional UL Noise Rise definable for each cell in the CDMA 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 Additional UL Noise Rise, see "Cell Properties" on
page 633.
733
Interference received from external base stations on mobiles of your CDMA network can be calculated by Atoll. Atoll uses the
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
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 CDMA document, i.e. in co-planning mode or in a multi-RAT document.
To define the inter-technology IRFs in the victim network:
1. In the Parameters explorer, expand the Radio Network Equipment folder, right-click Inter-technology Interference
Reduction Factors, and select Open Table. The Inter-technology Interference Reduction Factors table appears.
2. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter:
Enter the interference reduction factors in the Reduction (dB) column for different frequency separations,
Freq. Delta (MHz), values relative to the centre frequency of the channel (carrier) used in the main document.
3. When you have finished defining interference reduction factors, click OK.
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 714. 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 Atoll will calculate interference from all the external base stations in all the linked documents.
734
Chapter 10
TD-SCDMA
Networks
This chapter covers the following topics:
736
AT332_UMR_E0
10 TD-SCDMA Networks
Atoll enables you to create and modify all aspects of a TD-SCDMA network. Once you have created the network, Atoll offers
many tools to let you verify it. Based on the results of your tests, you can modify any of the parameters defining the network.
The process of planning and creating a TD-SCDMA network is outlined in "Designing a TD-SCDMA Network" on page 737.
Creating the network of base stations is explained in "Planning and Optimising TD-SCDMA Base Stations" on page 738.
Allocating neighbours is explained in "Planning Neighbours" on page 788.
In this section, you will also find information on how you can display information about base stations on the map and how you
can use the tools in Atoll to study base stations.
In "Studying TD-SCDMA Network Capacity" on page 798, using traffic maps to study network capacity is explained. Creating
simulations using traffic map information and analysing the results of simulations is also explained.
Using drive test data paths to verify the network is explained in "Analysing Network Performance Using Drive Test Data" on
page 811. Filtering imported drive test data paths, and using the data in coverage predictions is also explained.
).
You can open an existing Atoll document by selecting File > Open.
Creating a new Atoll document is explained in Chapter 1: Working Environment.
).
You can add and modify the following elements of base stations:
You can also add base stations using a base station template (see "Placing a New Base Station Using a Station
Template" on page 747).
737
4. Allocate neighbours (
).
5. Before making more advanced coverage predictions, you need to define cell load conditions (
).
You can generate realistic cell load conditions by creating a simulation based on a traffic map ( 5a and 5b ) (see
"Studying TD-SCDMA Network Capacity" on page 798).
You can define them manually either on the Cells tab of each transmitters Properties dialog box or in the Cells
table (see "Creating or Modifying a Cell" on page 746) (
5c
).
6. Make TD-SCDMA-specific coverage predictions using the defined cell load conditions (
).
).
738
AT332_UMR_E0
This section explains the various parts of the base station process:
10.2.1.1.1
Site Properties
The parameters of a site can be found in the sites Properties dialog box. The Properties dialog box has the following tabs:
The General tab
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 dialog box afterwards. For
information on placing sites using the mouse, see "Moving a Site Using the Mouse" on
page 57.
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.
10.2.1.1.2
Equipment: You can select equipment from the list. To create new site equipment, see "Creating Site Equipment"
on page 837. If no equipment is assigned to the site, Atoll considers that the JD factor and MCJD factor have a
value of "0".
Transmitter Properties
The parameters of a transmitter can be found in the transmitters Properties dialog box. When you create a transmitter, the
Properties dialog box has two tabs: the General tab and the Transmitter tab. Once you have created a transmitter, its Properties dialog box has three additional tabs: the Cells tab (see "Cell Properties" on page 742), the Propagation tab (see Chapter
4: Radio Calculations and Models), and the Display tab (see "Setting the Display Properties of Objects" on page 51).
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. For information on the site Properties dialog box, see
"Site Properties" on page 739. You can click the New button to create a new site for the transmitter.
Shared antenna: This field is used to identify the transmitters, repeaters, and remote antennas located at the
same site or on sites with the same position and that share the same antenna. The entry in the field must be the
same for all transmitters, repeaters, and remote antennas sharing the same antenna. When changes are made to
the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared
antenna. This field is also used for dual-band transmitters to synchronise antenna parameters for different frequency bands.
739
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 frequency band. For information on the frequency band Properties dialog box, see "Defining Frequency Bands" on page 828.
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.
Max Range: You can define a maximum coverage range for the current transmitter.
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 explorer.
Only active transmitters are taken into consideration during calculations.
TransmissionReception: Under TransmissionReception, 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.
Click the Equipment button to modify the tower-mounted amplifier (TMA), feeder cables, or transmitter equipment.
For information on the Equipment Specifications dialog box, see "Assigning Equipment to a Transmitter" on page 746.
Antennas:
Heightground: The Heightground 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.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
Mechanical Azimuth, Mechanical Downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt display additional antenna parameters.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
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.
Diversity: Under Diversity, you can select the No. of ports on the Transmission and Reception sides, as well
as the Type of diversity, if there is more than one port on the Transmission side.
Smart antenna: Under Smart antenna, the available smart antenna equipment are visible in the Equipment
list. You can click the Browse button to access the properties of the smart antenna equipment. When you click
the Browse button, the Smart Antenna Equipment Properties dialog box appears. If you are using a grid of
beams or an adaptive beam, under Smart antenna model, clicking the Parameters button opens the Grid of
Beams (GOB) Modelling or Adaptive Beam Modelling dialog box. Under Patterns, clicking the Combined button opens a dialog box displaying the combined antenna patterns of all the smart antenna beams and the main
antenna (see Figure 10.2).
For more information on smart antenna equipment, see "Smart Antenna Equipment" on page 834. The smart
antenna has the same height and tilt as the main antenna.
If you have smart antenna equipment based on Grid of Beams (GOB) or Adaptive Beam modelling, it is recommended to verify that the smart antenna beams be consistent with the main antenna pattern.
You can use the combined antenna pattern display to understand any inconsistencies in smart antenna results. If the gird of beams and the main antenna do not have the same gains, the smart antenna could provide
worse results than the main antenna for traffic timeslots.
740
AT332_UMR_E0
Under Secondary antennas, you can select one or more secondary antennas in the Antenna column and enter
their Azimuth, Mechanical 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.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna patterns,
see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
The transmission power is distributed among the main and secondary antennas. This is not
compatible with smart antennas. You must not assign smart antennas to transmitters with
secondary antennas, and vice versa.
In calculations, repeaters and remote antennas are transparent to the donor transmitters
and the served users. For example, beam forming smart antennas on donor transmitters
create beams directly towards the served users, and not towards the repeater or remote
antenna that covers the users. This results in a combined signal level received from the
transmitter using the smart antenna and from the repeater or remote antenna. If this
approach does not match how your equipment works, you must not assign smart antennas
to transmitters with repeaters and remote antennas, and vice versa.
The main antenna is used to transmit the pilot signals. Coverage predictions based on the P-CCPCH signal are
performed using the main antenna. It is also used for traffic signals if there is no smart antenna equipment selected
for the transmitter.
If there is smart antenna equipment assigned to the transmitter, traffic data is transmitted and received using the
smart antenna, while the pilot and other common channels are transmitted using the main antenna.
Cell Tab
When you create a transmitter, Atoll automatically creates a cell for the transmitter using the properties of the currently
selected station template.
The cell tab enables you to configure the properties for every cell of a transmitter. For more information on the properties of
a cell, see "Cell Properties" on page 742.
Propagation Tab
Transmitters are taken into account during calculations. Therefore, you must specify their 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. For information on propagation models, see "Assigning Propagation Parameters" on page 187.
Display Tab
On the Display tab, you can modify how a transmitters are displayed. For information on changing display properties, see
"Setting the Display Properties of Objects" on page 51.
741
10.2.1.1.3
Cell Properties
In Atoll, a cell is defined as an RF carrier, with all its characteristics, on a transmitter; the cell is the mechanism by which you
can configure a TD-SCDMA multi-carrier network. In other words, a transmitter has one cell for every carrier.
This section describes the parameters of a TD-SCDMA cell. The properties of a TD-SCDMA cell are found on Cells tab of the
Properties dialog box of the transmitter to which it belongs.
You can also display the properties of a cell by double-clicking the cell in the Site explorer.
N-Frequency mode: If the transmitter is compatible with N-frequency mode, you must select the N-Frequency mode
check box. Transmitters compatible with the N-frequency mode have one master carrier, and may have one or more
slave carriers. Transmitters which are not compatible with the N-frequency mode have stand-alone carriers. Master
carriers have P-CCPCH, DwPCH, and other CCH powers defined, while slave carriers do not. For more information on
the N-frequency mode and allocation of carrier types, see "Planning Frequencies" on page 785.
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 Administrator Manual.
Active: If this cell is to be active, you must select the Active check box.
Carrier: The number of the carrier.
Order: The display order of a cell within the transmitter. This value is used to determine the order in which information
related to a cell will be displayed in the Network explorer and on the map. This field is automatically filled by Atoll but
you can change these default values to display cells in a user-defined order.
The consistency between values stored in this field is verified by Atoll. However, inconsistencies may arise when tools other than Atoll modify the database. You can check for inconsistencies in the cell display order and fix them by selecting Data Audit > Cell Display Order
Check in the Document menu.
P-CCPCH power [TS0] (dBm): The power of the P-CCPCH channel transmitted on TS0.
Other CCH power [TS0] (dBm): The average power of the control channels (including S-CCPCH) that are not transmitted continuously on TS0. For example, if P dBm is transmitted during 1 s every 10 s , you should enter
P10 dBm in order to correctly represent the average interference from these channels.
DwPCH power [DwPTS] (dBm): The power transmitted on the DwPTS timeslot.
By default, the DwPCH power and the other CCH power are set as absolute values. You can
set these values as relative to the pilot power in the Global Parameters. For more information, see "Global Network Settings" on page 828.
742
P-CCPCH RSCP T_Comp [TS0] (dB): The P-CCPCH RSCP comparative threshold for determining the transmitters to keep
in the list of potential servers. This parameter is used in the baton handover coverage prediction along with P-CCPCH
RSCP T_Add and P-CCPCH RSCP T_Drop parameters set for different mobility types.
Min RSCP (dBm): The minimum P-CCPCH RSCP required for a user to be connected to the cell. The P-CCPCH RSCP is
compared with this threshold to determine whether or not a user can be connected to the cell.
AT332_UMR_E0
Timeslot configuration: The configuration of the traffic timeslots in the frame. When the UpPCH channel is present in
the UpPTS timeslot, you can select from five possible timeslot configurations, i.e., (D)UDDDDD, (D)UUDDDD,
(D)UUUDDD, (D)UUUUDD, and (D)UUUUUD. When the UpPCH is shifted to TS1, you can select from two more timeslot
configurations, i.e., (D)UpUDDDD, (D)UpUUDDD. When UpPCH is shifted, TS1 is blocked, i.e., it is not used to carry
traffic. For more information on UpPCH shifting and studying the interference on the UpPCH, see Figure
10.2.8.3.9"Studying UpPCH Interference" on page 776.
There are two switching points in the frame, one after the first mandatory downlink timeslot (D), and the other can
be after 1 to 5 uplink timeslots. The symmetric configuration is selected by default.
Required UL resource units: The number of resource units required in the uplink.
Required DL resource units: The number of resource units required in the downlink. Atoll can calculate the number
of required resource units in the uplink and downlink. For information on calculating network capacity, see "Calculating TD-SCDMA Network Capacity" on page 798.
Comments: If desired, you can enter any comments in this field.
HSPA Support: The HSPA functionality supported by the cell. You can choose between None (i.e., R99 only), HSDPA,
or HSPA (i.e., HSDPA and HSUPA).
When HSDPA is supported, the following fields are available:
HS-PDSCH power dynamic allocation: If you are modelling dynamic power allocation, you should select this check
box. During simulations, Atoll first allocates power to R99 users and then dynamically allocates the remaining
power of the cell to the HS-PDSCH channels of HSDPA users. At the end of the simulation, you can commit the
calculated HS-PDSCH power and total power values to each cell and timeslot.
In the context of dynamic power allocation, the total power is the maximum power minus
the power headroom.
Available HS-PDSCH power per DL TS (dBm): When you are modelling static power allocation, the HS-PDSCH
power dynamic allocation check box is cleared and the HS-PDSCH power available for each downlink timeslot is
entered in this box. This is the default value of power available per timeslot for the HS-PDSCH channels of HSDPA
users. In case of dynamic HS-PDSCH power allocation, the value entered here represents the maximum power for
the HS-PDSCH of HSDPA users per timeslot.
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, you should select this check
box and enter a value in HS-SCCH power per DL TS (dBm). The HS-SCCH power calculated for HS-SCCH channel
during a simulation cannot exceed the value defined in HS-SCCH power per DL TS (dBm). During power control,
Atoll controls HS-SCCH power in order to meet the minimum quality threshold (as defined for each mobility type).
HS-SCCH power per DL TS (dBm): When you are modelling static power allocation, the HS-SCCH dynamic power
allocation check box is cleared and the actual power per HS-SCCH channel is entered in this box. In case of dynamic
HS-SCCH power allocation, the value entered here represents the maximum power for the HS-SCCH channel per
HSDPA user.
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 transmission time
interval), the number of HSDPA users cannot exceed the number of HS-SCCH channels per cell.
HS-SICH dynamic power allocation: If you are modelling dynamic power allocation, you should select this check
box. During power control, Atoll controls HS-SICH power of the HSDPA-capable terminal in order to meet the minimum quality threshold (as defined for each mobility type) in the uplink.
Number of HS-SICH channels: The maximum number of HS-SICH channels for this cell. Each Packet (HSDPA) and
Packet (HSPA) user consumes one HS-SICH channel. Therefore, at any given time (over a transmission time
interval), the number of HSPA users cannot exceed the number of HS-SICH channels per cell.
Min number of HS-PDSCH codes per DL TS: The minimum number of OVSF codes available for HS-PDSCH channels
for each downlink timeslot. This value will be taken into account during simulations in order to find a suitable
bearer.
Max number of HS-PDSCH codes per DL TS: The maximum number of OVSF codes available for HS-PDSCH channels for each downlink timeslot. This value will be taken into account during simulations and coverage predictions
in order to find a suitable bearer.
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 descend-
743
ing 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
the Atoll.ini file. For more information, see the Administrator Manual.
Max number of HSDPA users: The maximum number of HSDPA bearer users (i.e., Packet (HSDPA) users and
Packet (HSPA) users 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.
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) that this
cell can support at any given time.
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.
E-DCH dynamic power allocation: If you are modelling dynamic power allocation, you should select this check box
and enter a value in E-DCH power per DL TS (dBm). The E-DCH power calculated for E-DCH channel during a simulation cannot exceed the value defined in E-DCH power per DL TS (dBm). During power control, Atoll controls
E-DCH power in order to meet the minimum quality threshold (as defined for each mobility type).
E-DCH power per DL TS (dBm): When you are modelling static power allocation, the E-DCH dynamic power allocation check box is cleared and the actual power per E-DCH channel is entered in this box. In case of dynamic EDCH power allocation, the value entered here represents the maximum power for the E-DCH channel per HSUPA
user.
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.
Max Number of Intra-technology Neighbours: The maximum number of intra-technology neighbours for this cell. This
value is used by the intra-technology 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.
Neighbours: You can access a dialog box in which you can set both intra-technology and inter-technology neighbours
by clicking the Browse button. For information on defining neighbours, see "Editing Neighbours in the Cell Properties"
on page 228.
Timeslots: You can access information about the cells traffic timeslots, i.e, for each of the six traffic timeslots, by
clicking the Browse button.
The Browse buttons ( ) might not be visible in the Neighbours and Timeslot boxes if
this is a new cell. You can make the Browse buttons appear by clicking Apply.
744
Blocked: If this timeslot is to be blocked, i.e., not used for traffic, you must select the Blocked check box. A blocked
timeslot is not used by the Dynamic Channel Allocation (DCA) algorithm and does not carry any traffic.
Timeslot type: The type of traffic that the timeslot can carry, i.e., R99, HSDPA, HSUPA, etc.
Other CCH power (dBm): The power of other common channels (S-CCPCH, FPACH, and PICH) on the traffic
timeslot. Other common control channels can be transmitted on a downlink traffic timeslot using the main
antenna.
DL traffic power (dBm): The traffic power transmitted on downlink is the power necessary to serve users on the
downlink timeslots. This value can be a simulation result or can be entered by the user.
UL load factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between the
uplink total interference and the uplink total noise. This value can be a simulation result or can be entered by the
user.
Angular distribution of UL and DL loads: The angular distribution of downlink transmitted power and uplink loads
calculated for cells whose transmitters have smart antenna equipment. This value is a simulation result.
Resource units overhead: The number of resource units corresponding to overhead. This overhead is used in network dimensioning. For information on calculating network capacity, see "Calculating TD-SCDMA Network
Capacity" on page 798.
Max DL load (% Pmax): The percentage of the maximum downlink power (set in Max power [Traffic TS]) not to
be exceeded. This limit can be taken into account during simulations.
Max UL load factor (%): The maximum uplink load factor not to be exceeded. This limit can be taken into account
during simulations.
AT332_UMR_E0
Available HS-PDSCH power (dBm): When you are modelling static power allocation, the HS-PDSCH dynamic
power allocation check box in the Cells tab is cleared and the HS-PDSCH power available for the downlink timeslot
is entered in this box. This power is available for the HS-PDSCH channels of HSDPA users. In case of dynamic HSPDSCH power allocation, the value entered here represents the maximum power for the HS-PDSCH of HSDPA
users.
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. If no value is defined here,
the value defined for the cell is considered for the timeslot.
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. If
no value is defined here, the value defined for the cell is considered for the timeslot.
10.2.1.2.1
10.2.1.2.2
745
5. Click OK.
To modify the properties of an existing transmitter:
1. Select the Network explorer.
2. Click the Expand button ( ) 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 dialog box appears.
5. Modify the parameters described in "Transmitter Properties" on page 739.
6. Click OK. If you are creating 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 746.
10.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 in the Network explorer and selecting Open Table
from the context menu. For information on copying and pasting data, see "Copying
and Pasting in Tables" on page 83.
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.
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 161.
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 161.
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 162.
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.
4. Click OK.
10.2.1.2.4
746
AT332_UMR_E0
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 in the Network explorer 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 83), or
import data into the table (see "Importing Tables from Text Files" on page 88).
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.
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 base 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 60.
If you let the pointer rest over the base station you have placed, Atoll displays its
tip text with its exact coordinates, allowing you to verify that the location is correct.
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 base station.
747
10.2.1.4.1
1st sector mechanical azimuth from which the azimuth of the other sectors are offset to offer complete coverage
of the area.
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 the building).
Mechanical downtilt for the antennas.
Electrical Azimuth, Electrical Downtilt, and Additional electrical downtilt display additional antenna parameters.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
Under Path loss matrices, you can modify the following: the Main propagation model, the Main radius, and the Main
resolution, and the Extended propagation model, the Extended radius, and the Extended resolution. For information
on propagation models, see Chapter 4: Radio Calculations and Models.
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.
Transmitter Tab
Active: Select this option to specify whether the transmitter is active. Active transmitters are displayed in red in the
CDMA Transmitters folder of the Network explorer.
Only active transmitters are taken into consideration during calculations.
Click the Equipment button to modify the tower-mounted amplifier (TMA), feeder cables, or transmitter equipment.
For information on the Equipment Specifications dialog box, see "Assigning Equipment to a Transmitter" on page 746.
The Total losses (transmission and reception) and Noise figure (reception) in the Computed columns is calculated
from the information that was entered in the Equipment Specifications dialog box. The Total losses (transmission and
reception) Noise figure (reception) in the Real columns can be edited. Any value that you enter must be positive.
Any loss related to the noise due to the repeater of a transmitter is included in the calculated losses. Atoll always considers the values in the Real boxes in coverage predictions
even if they are different from the values in the Computed boxes.
Diversity: Select the No. of ports on the Transmission and Reception sides, as well as the Type of diversity, if there is
more than one port on the Transmission side.
TD-SCDMA Tab
On this tab, you can modify the specifications of the Carriers (each corresponding to a cell) that each transmitter supports.
748
N-frequency mode: Select whether the transmitters created with this template are compatible with N-frequency
mode. If you select this option, the transmitters created using this station template will have at least one master carrier with P-CCPCH, DwPCH, and Other CCH powers. If there is more than one carrier on the transmitters, the rest of
the carriers will be slave carriers. Slave carriers will not have any P-CCPCH, DwPCH, or Other CCH powers. If this option
is disabled, the transmitters created using this template will have stand-alone carriers.
AT332_UMR_E0
Carrier: You can select the 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, click the Browse button and select the carriers to be created for each sector of the station.
Primary scrambling code: Specify the Reuse distance and the scrambling code Domain.
Power: Specify the Max, P-CCPCH, DwPCH, and the Other CCH powers.
Timeslots: Select a default Timeslot configuration for the cells and set the numbers of UL required resource units and
DL required resource units.
Equipment: Specify a default equipment for the sites.
HSPA Tab
Use this tab to specify additional carrier parameters (each corresponding to a cell) that each transmitter supports. For information on carriers and cells, see "Cell Properties" on page 742.
HSPA support: Choose between None (i.e., R99 only), HSDPA, or HSPA (i.e., HSDPA and HSUPA).
If you select HSDPA as HSPA support, you can set the following HSDPA parameters:
HS-PDSCH: Select either Static or Dynamic allocation strategy for HS-PDSCH power, enter the Fixed power, if you
selected Static power allocation, and enter the Min. and Max number of codes for HS-PDSCH.
HS-SCCH: Select either Static or Dynamic allocation strategy for HS-SCCH power, enter the HS-SCCH power for
HS-SCCH, if you selected Static power allocation, and define the Number of channels for HS-SCCH.
Scheduler: Select the scheduler Algorithm and enter the Max number of users.
When you create an HSDPA-capable base station using a station template, the timeslots of all the cells created automatically are by default set to support R99 and HSDPA.
If you select HSDPA as HSPA support, you can also set the following HSUPA parameters:
HSDPA: Select Dynamic allocation strategy for E-DCH power and enter the Max number of users.
When you create an HSPA-capable base station using a station template, the timeslots of all the cells created automatically
are by default set to support R99 and HSPA.
Neighbours Tab
On this tab, you can modify the Max Number of Intra- and Inter-Carrier Neighbours and the Max Number of Intertechnology Neighbours. For information on defining neighbours, see "Neighbour Planning" on page 223.
Other Properties Tab
This tab only appears if you have defined additional fields in the Sites table, or if you have defined an additional field in the
Station Template Properties dialog box.
10.2.1.4.2
10.2.1.4.3
749
10.2.1.4.4
10.2.1.4.5
10.2.1.4.6
Quickly create a new base station with the same settings as an original one in order to study the effect of a new station
on the coverage and capacity of the network, and
Quickly create a new homogeneous network with stations that have the same characteristics.
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 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.
5. Place the new base station on the map using the mouse:
750
Creating a duplicate base station and site: In the map window, move the pointer over the map to where you
would like to place the duplicate. The exact coordinates of the pointers current location are visible in the Status
bar.
AT332_UMR_E0
Placing the duplicate base station on an existing site: In the map window, move the pointer over the existing site
where you would like to place the duplicate. When the pointer is over the site, the site is automatically selected.
The exact coordinates of the pointers current location are visible in the Status bar.
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 60.
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.
) in the Radio Planning toolbar. The Point Analysis window opens and the pointer
changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and the
receiver. You can move the receiver on the map (see "Moving the Receiver on the Map" on page 203).
Select the Profile view. The Profile view displays the profile between the transmitter and the receiver with the terrain and
clutter heights.
751
The received signal strength from the selected transmitter for the cell with the highest reference signal power
The propagation model used
The shadowing margin and the indoor loss (if selected)
The distance between the transmitter and the receiver.
3. If needed, select an other transmitter from the list. You can click the Properties button (
properties.
) to display the Calculation Options dialog box and change the following:
Change the X and Y coordinates to change the current position of the receiver.
Select the Shadowing taken into account check box and enter a Cell edge coverage probability. For more information, see "Taking Shadowing into Account in Point Analyses" on page 204.
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. Indoor losses are defined per frequency per
clutter class. For more information, see "Taking Indoor Losses into Account" on page 203.
6. In the Profile view toolbar, you can use the following tools:
) to view the geographic profile between the transmitter and the receiver.
) again to view the radio signal path between the transmitter and the
Click the Detailed Report button ( ) to display a text document with details on the displayed profile analysis.
The detailed report is only available for the Standard Propagation Model.
) to copy the content of the view and paste it as a graphic into a graphic editing or wordClick the Copy button (
processing programme.
752
) again.
AT332_UMR_E0
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.
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 83.
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 and Spreadsheets" on page 86. For information on importing table data, see "Importing Tables from Text Files" on page 88.
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 Base
Station Using a Station Template" on page 747.
753
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 "Associating a
Label to an Object" on page 53.
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 "Associating a Tip Text to an Object" on page 54.
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.
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 "Setting the Display Type" on page 52.
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 (
same site with the same azimuth, you can differentiate them by selecting different symbols for each (
For information on defining the transmitter symbol, see "Setting the Display Type" on page 52.
and
).
Broadband repeaters are not modelled. Atoll assumes that all carriers of 3G donor
transmitters are amplified.
In calculations, repeaters are transparent to the donor transmitters and the served
users. For example, beamforming smart antennas at donor transmitters create beams
directly towards the served users, and not towards the repeater that covers the users.
This results in a combined signal level received from the transmitter using the smart
antenna and from the repeater. If this approach does not match how your equipment
works, you must not assign smart antennas to transmitters with repeaters and vice
versa.
In this section, the following are explained:
754
AT332_UMR_E0
):
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.
755
When the donor is a transmitter, you can see to which base station the repeater is
connected by clicking it; Atoll displays a link to the donor transmitter. You can hide
the link by clicking it again.
When the donor is a repeater or a remote antenna, Atoll displays a spider-type link
showing the entire chain down to the donor transmitter. The same spider-type link
is displayed when you click any of the items belonging to the chain is clicked (i.e.,
donor transmitter, any repeater, or any remote antenna).
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 83.
You can change the Name of the repeater. By default, repeaters are named "SiteX_Y_RepZ" where "X" is the donor
site number, "Y" the donor transmitter number, and "Z" a number assigned to the repeater when it was created.
If the donor is a remote antenna or another repeater, then "RepZ" is preceded by "RemA_"
or "RepB_" where "A" and "B" identify the donor remote antenna and the donor repeater.
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, a remote antenna,
or another repeater. Clicking the Browse button opens the Properties dialog box of the selected donor.
You can change the Site on which the repeater is located. Clicking the Browse button opens the Properties dialog
box of the selected site.
You can enter a value in the Shared antenna (coverage side) field for the repeater. This field is used to identify the
transmitters, repeaters, and remote antennas that are located at the same site or on sites with the same position
and that share an antenna. The entry in the field must be the same for all such transmitters, repeaters, and remote
antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of
one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote
antennas defined as having a shared antenna.
Under Antenna position, you can define the position of the repeater, if it is not located on the site itself:
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 dialog box of
the equipment.
You can change the Amplifier gain. The amplifier 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:
756
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,
AT332_UMR_E0
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:
Model: The type of antenna is visible in the Model list. You can click the Browse button to access the properties of the antenna.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
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 repeater is situated on a building, the height entered must
include the height of building.
Mechanical Azimuth and Mechanical Downtilt display additional antenna parameters.
You can click the Calculate button to update the mechanical azimuth and mechanical
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 to access the properties of the feeder.
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
explorer) are calculated.
Total Gain: enter the gain (in downlink and uplink) or click Calculate to determine the actual gain in both directions. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply before
clicking the Calculate button.
In downlink, the total gain is applied to each power (P-CCPCH power, DwPCH power, etc.).
In uplink, the total gain is applied to each terminal power.
The total gain considers losses between the donor transmitter and the repeater, donor characteristics (donor antenna gain, reception feeder losses), amplifier gain, and coverage characteristics (coverage antenna gain, transmission feeder losses).
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 repeater 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.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
Mechanical Azimuth, Mechanical Downtilt, and Additional Electrical Downtilt display additional antenna
parameters.
Mechanical Azimuth, Mechanical downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt display additional antenna parameters.
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.
757
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
Select a Type of feeder from the list. You can click the Browse button to access the properties of the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
Under Losses, the Loss related to repeater noise rise is displayed and you can modify the following information:
Misc. losses: You can specify additional losses in dB for Transmission and Reception.
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 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 4: Radio Calculations and Models.
You can update the calculated azimuths and downtilts 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.
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 57) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using
the Mouse" on page 58).
758
AT332_UMR_E0
2. Click the arrow next to the New Repeater or Remote Antenna button (
When the donor is a transmitter, you can see to which base station the repeater is
connected by clicking it; Atoll displays a link to the donor transmitter. You can hide
the link by clicking it again.
When the donor is a repeater or a remote antenna, Atoll displays a spider-type link
showing the entire chain down to the donor transmitter. The same spider-type link
is displayed when you click any of the items belonging to the chain is clicked (i.e.,
donor transmitter, any repeater, or any remote antenna).
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 83.
759
You can change the Name of the remote antenna. By default, remote antennas are named "SiteX_Y_RemZ" where
"X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned as the remote antenna
is created.
If the donor is a repeater or another remote antenna, then "RemZ" is preceded by "RepA_"
or "RemB_" where "A" and "B" identify the donor repeater and the donor remote antenna.
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, another remote
antenna or a repeater. Clicking the Browse button opens the Properties dialog box of the selected donor.
You can change the Site on which the remote antenna is located. Clicking the Browse button opens the Properties
dialog box of the selected site.
You can enter a value in the Shared Antenna (coverage side) field for the remote antenna. This field is used to
identify the transmitters, repeaters, and remote antennas that are located at the same site or on sites with the
same position and that share an antenna. The entry in the field must be the same for all such transmitters,
repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height,
or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters,
repeaters, and remote antennas defined as having a shared antenna.
Under Antenna position, you can define the position of the remote antenna, if it is not located on the site itself:
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 with in red in the Transmitters folder in the
Network explorer) are calculated.
Total Gain: enter the gain (in downlink and uplink) or click Calculate to determine the actual gain in both directions. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply before
clicking the Calculate button.
In downlink, the total gain is applied to each power (P-CCPCH power, DwPCH power, etc.).
In uplink, the total gain is applied to each terminal power.
The total gain considers losses between the donor transmitter and the remote antenna.
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 remote antenna is situated on a building, the height entered
must include the height of the 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.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
760
Mechanical Azimuth, Mechanical downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt display additional antenna parameters.
AT332_UMR_E0
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.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
Select a Type of feeder from the list. You can click the Browse button to access the properties of the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
Under Losses, the Loss related to repeater noise rise is displayed and you can modify the following information:
Misc. losses: You can specify additional losses in dB for Transmission and Reception.
6. Click the Propagation tab. As remote antennas are taken into account during calculations, you must set propagation
parameters as with transmitters. On the Propagation tab, you can modify 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 4: Radio Calculations and Models.
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 57) or its position relative to the site (see "Changing the Antenna Position Relative to the Site
Using the Mouse" on page 58).
761
Display Resolution
City Centre
5m
City
20 m
County
50 m
State
100 m
Country
The resolution specified here is only for display purposes. The calculated resolution is independently specified in the
propagation settings. For more information, see "Assigning Propagation Parameters" on page 187.
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the <GUID> and </GUID> tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
Receiver height: This displays the height of the receiver defined in the Calculation Parameters tab of the Network
Settings Properties dialog box.
Comments: Specify an optional description of comment for the prediction.
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 99. The Group By and Sort buttons are not available when making a so-called
"global" coverage prediction (e.g., signal level coverage prediction).
The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction).
762
AT332_UMR_E0
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.
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 dialog box. 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 104.
The following standard coverage predictions are explained in this section:
10.2.8.2.1
763
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 propagation models best suited for the main and extended matrices.
e. In the Main matrix column:
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal
properties are used.
Service: The service to be considered in the coverage prediction. The body loss defined in the service properties
is used.
Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP T_Add (P-CCPCH RSCP
threshold) defined in the mobility properties is used as the minimum requirement for the coverage prediction.
Carrier: You can select the carrier to be studied, or select "Best".
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best", Atoll will display the coverage
prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
6. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The P-CCPCH RSCP
coverage prediction can be found in the Predictions folder in the Network explorer. 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 (
10.2.8.2.2
).
764
AT332_UMR_E0
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal
properties are used.
Service: The service to be considered in the coverage prediction. The body loss defined in the service properties
is used.
Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP T_Add (P-CCPCH RSCP
threshold) defined in the mobility properties is used as the minimum requirement for the coverage prediction.
Carrier: You can select the carrier to be studied, or select "Best".
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist on a
transmitter, there will not be any pixels covered by this transmitter. If you select "Best", Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service
properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master
carrier in case of N-frequency mode compatible transmitters.
RSCP margin: Select "Value intervals" as the Display type and "RSCP margin" as the Field. RSCP Margin is the
margin between the calculated P-CCPCH RSCP and the P-CCPCH RSCP T_Add given for the selected mobility.
Cell edge coverage probability: Select "Value intervals" as the Display type and "Cell edge coverage probability"
as the Field.
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 (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
10.2.8.2.3
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal
properties are used.
765
Service: The service to be considered in the coverage prediction. The body loss defined in the service properties
is used.
Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP T_Add (P-CCPCH RSCP
threshold) defined in the mobility properties is used as the minimum requirement for the coverage prediction.
Carrier: You can select the carrier to be studied, or select "Best".
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best", Atoll will display the coverage
prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
Timeslot: The coverage prediction by P-CCPCH best server is performed for TS0.
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. Indoor losses are defined per frequency per
clutter class.
Figure 10.6: Condition settings for a coverage prediction by P-CCPCH best server
4. Click the Display tab.
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 "Setting the Display Properties of Objects" on page 51.
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 (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
10.2.8.2.4
766
AT332_UMR_E0
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal
properties are used.
Service: The service to be considered in the coverage prediction. The body loss defined in the service properties
is used.
Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP T_Add (P-CCPCH RSCP
threshold) defined in the mobility properties is used as the minimum requirement for the coverage prediction.
Carrier: You can select the carrier to be studied, or select "Best".
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage
prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
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 (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
10.2.8.2.5
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal
properties are used.
Service: The service to be considered in the coverage prediction. The body loss defined in the service properties
is used.
Mobility: The mobility type to be considered in the coverage prediction. The DwPCH RSCP threshold defined in
the mobility properties is used as the minimum requirement for the coverage prediction.
Carrier: You can select the carrier to be studied, or select "Best".
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest DwPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best", Atoll will display the coverage
prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
Timeslot: The coverage prediction by DwPCH RSCP is performed for DwPTS timeslot.
If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability.
767
You can select the Indoor coverage check box to add indoor losses. Indoor losses are defined per frequency per
clutter class.
RSCP margin: Select "Value Intervals" as the Display type and "RSCP margin" as the Field. RSCP margin is the
margin between the calculated DwPCH RSCP and the DwPCH RSCP threshold given for the selected mobility.
Cell edge coverage probability: Select "Value Intervals" as the Display type and "Cell edge coverage probability"
as the Field.
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 (
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
10.2.8.2.6
768
Terminal: The terminal to be considered in the coverage prediction. The UpPCH power, gains, and losses defined
in the terminal properties are used.
Service: The service to be considered in the coverage prediction. The body loss defined in the service properties
is used.
Mobility: The mobility type to be considered in the coverage prediction. UpPCH RSCP threshold defined in the
mobility properties is used as the minimum requirement for the coverage prediction.
Carrier: You can select the carrier to be studied, or select "Best".
AT332_UMR_E0
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage
prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
Timeslot: The coverage prediction by UpPCH RSCP is performed for UpPTS timeslot.
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. Indoor losses are defined per frequency per
clutter class.
RSCP margin: Select "Value intervals" as the Display type and "RSCP margin" as the Field. RSCP margin is the
margin between the calculated UpPCH RSCP and the UpPCH RSCP threshold given for the selected mobility.
Cell edge coverage probability: Select "Value intervals" as the Display type and "Cell edge coverage probability"
as the Field.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
"Setting the UL Load Factor and the DL Traffic Power" on page 770.
Several different types of signal quality coverage predictions, based either on EbNt, CI, or traffic channel quality, are
explained in this section:
769
10.2.8.3.1
DL traffic power (dBm): The value of downlink traffic power for downlink timeslots.
UL load factor (%): The value of uplink load factor for uplink timeslots.
You can see the configuration of the uplink and downlink timeslots by referring to the cells timeslot configuration. For
a definition of the values, see "Cell Properties" on page 742.
10.2.8.3.2
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal
properties are used.
Service: The service to be considered in the coverage prediction. The body loss defined in the service properties
is used.
Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH EbNt threshold or P-CCPCH
CI threshold defined in the mobility properties is used as the minimum requirement for the coverage prediction.
Carrier: You can select the carrier to be studied, or select "Best".
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage
prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
Timeslot: The P-CCPCH reception analysis predictions are performed for TS0.
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. Indoor losses are defined per frequency per
clutter class.
770
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately.
AT332_UMR_E0
OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the
Calculate button (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window.
10.2.8.3.3
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal
properties are used.
Service: The service to be considered in the coverage prediction. The body loss defined in the service properties
is used.
Mobility: The mobility type to be considered in the coverage prediction. The DwPCH CI threshold defined in the
mobility properties is used as the minimum requirement for the coverage prediction.
Carrier: You can select the carrier to be studied, or select "Best".
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best", Atoll will display the coverage
prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
Timeslot: The DwPCH reception analysis (CI) predictions are performed for DwPTS.
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. Indoor losses are defined per frequency per
clutter class.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window.
10.2.8.3.4
771
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal
properties are used. For the uplink traffic channel coverage prediction, Atoll calculates the RSCP using the maximum power defined for the selected terminal.
Service: The R99 service to be considered in the coverage prediction. The uplink TCH RSCP threshold or downlink
TCH RSCP threshold defined in the properties of the R99 radio bearer of the service is used as the minimum
requirement for the coverage prediction. The body loss defined in the service properties is also used. For the
downlink traffic channel, Atoll calculates the RSCP using the maximum allowed downlink traffic channel power
defined for the R99 bearer of the selected service.
Mobility: The mobility type to be considered in the coverage prediction. The uplink TCH RSCP threshold or the
downlink TCH RSCP threshold defined in the selected services R99 bearer and corresponding to the selected
mobility type is used as the minimum requirement for the coverage prediction.
Carrier: You can select the carrier to be studied, or select "Best".
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage
prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
Timeslot: The coverage predictions by TCH RSCP can be performed for any downlink or uplink timeslot.
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. Indoor losses are defined per frequency per
clutter class.
RSCP Margin: Select "Value Intervals" as the Display type and "RSCP margin" as the Field. The RSCP margin is the
margin between the calculated DL or UL TCH RSCP and the DL or UL TCH RSCP threshold, respectively, given for
the selected services R99 bearer.
Cell Edge Coverage Probability: Select "Value intervals" as the Display type and "Cell edge coverage probability"
as the Field.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window.
10.2.8.3.5
772
AT332_UMR_E0
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal
properties are used. For the uplink service area coverage prediction, Atoll calculates the EbNt or CI using the
maximum power defined for the selected terminal.
Service: The R99 service to be considered in the coverage prediction. The uplink TCH EbNt threshold and downlink TCH EbNt threshold (or uplink TCH CI threshold and downlink TCH CI threshold) defined for the services
R99 radio bearer are used as the minimum requirement for the coverage prediction. The body loss defined in the
service properties is also used. For the downlink traffic channel, Atoll calculates the EbNt or CI using the maximum allowed downlink traffic channel power defined for the R99 bearer of the selected service. The processing
gains are also used for the EbNt coverage predictions.
Mobility: The mobility type to be considered in the coverage prediction. The uplink and downlink TCH EbNt
thresholds (or uplink or downlink TCH CI thresholds), defined in the service selected above, corresponding to the
selected mobility type are used as the minimum requirement for the coverage prediction.
Carrier: You can select the carrier to be studied, or select "Best".
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best" Atoll will display the coverage
prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
Timeslot: The service area coverage predictions can be performed for any downlink or uplink timeslot.
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. Indoor losses are defined per frequency per
clutter class.
The traffic channel quality relative to the EbNt or CI threshold: Select "Value intervals" as the Display type and
"EbNt margin (dB)" or "CI margin (dB)" as the Field.
The power required to reach the EbNt or CI threshold: Select "Value intervals" as the Display type and
"Required power (dB)" as the Field.
Where traffic channel quality exceeds the EbNt or CI threshold for each mobility type: On the Conditions tab,
select "All" as the Mobility type. The parameters on the Display tab are automatically set.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window.
773
10.2.8.3.6
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal
properties are used. For the uplink, Atoll calculates the EbNt or CI using the maximum power defined for the
selected terminal.
Service: The R99 service to be considered in the coverage prediction. The uplink TCH EbNt threshold and downlink TCH EbNt threshold (or uplink TCH CI threshold and downlink TCH CI threshold) defined for the services
R99 radio bearer are used as the minimum requirement for the coverage prediction. The body loss defined in the
service properties is also used. For the downlink traffic channel, Atoll calculates the EbNt or CI using the maximum allowed downlink traffic channel power defined for the R99 bearer of the selected service. The processing
gains are also used for the EbNt coverage predictions.
Mobility: The mobility type to be considered in the coverage prediction. The uplink TCH EbNt threshold and
downlink TCH EbNt threshold (or uplink TCH CI threshold and downlink TCH CI threshold), defined in the
selected services R99 bearer, corresponding to the selected mobility type are used as the minimum requirement
for the coverage prediction.
Carrier: You can select the carrier to be studied, or select "Best".
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage
prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
Timeslot: The effective service area coverage predictions are performed for all downlink and uplink timeslots.
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. Indoor losses are defined per frequency per
clutter class.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window.
10.2.8.3.7
774
AT332_UMR_E0
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal
properties are used.
Service: The service to be considered in the coverage prediction. The body loss defined in the service properties
is used.
Mobility: The downlink total noise calculation does not depend on the mobility type.
Carrier: You can select the carrier to be studied, or select "Best".
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best", Atoll will display the coverage
prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
Timeslot: The downlink total noise coverage predictions can be performed for any downlink timeslot.
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. Indoor losses are defined per frequency per
clutter class.
For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window.
10.2.8.3.8
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal
properties are used.
Service: The R99 service to be considered in the coverage prediction. The body loss defined in the service properties is used.
775
Timeslot: The cell-to-cell interference coverage prediction can be performed for any timeslot.
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. Indoor losses are defined per frequency per
clutter class.
4. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window.
10.2.8.3.9
776
AT332_UMR_E0
ties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
Timeslot: The UpPCH interference coverage predictions are performed for TS1 uplink timeslot for UpPCH shifting.
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. Indoor losses are defined per frequency per
clutter class.
Figure 10.8: Condition settings for an UpPCH interference zones coverage prediction
4. Click the Display tab.
Select "Value intervals" as the Display type and one of the following options from the Field list:
For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window.
10.2.8.3.10
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal
properties are used.
Service: The service to be considered in the coverage prediction. The body loss defined in the service properties
is used.
777
Mobility: The mobility type to be considered in the coverage prediction. P-CCPCH RSCP T_Add, and P-CCPCH RSCP
T_Drop defined in the mobility properties are used to define the signal level range for transmitters to enter the
preliminary handover set.
Carrier: You can select the carrier to be studied, or select "Best".
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage
prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
4. Click the Display tab. The settings you select on the Display tab determine the information that the prediction will
display.
For a baton handover analysis, the Display type "Value intervals" and the Field "Number of potential neighbours" are
selected by default. You can also display only the baton handover coverage surface area by selecting "Unique" as the
Display type. For information on defining display properties, see "Setting the Display Properties of Objects" on
page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window.
Terminal: The HSDPA-compatible terminal to be considered in the coverage prediction. The gain, losses, and
HSDPA UE category defined in the terminal properties are used.
Service: The HSDPA-compatible service to be considered in the coverage prediction. The body loss defined in the
service properties is used.
Mobility: The mobility type to be considered in the coverage prediction. The downlink HS-SCCH EcNt threshold
defined in the mobility properties is used as the minimum requirement for the coverage prediction.
Carrier: You can select the carrier to be studied, or select "Best".
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage
prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
778
Timeslot: The HSDPA coverage prediction can be performed for any downlink or all timeslots. If you select "All"
timeslots, you can select an HSDPA bearer for which the prediction will be carried out.
AT332_UMR_E0
HSDPA radio bearer: The HSDPA bearer for which the coverage prediction is to be performed. Accessing an HSDPA
radio bearer requires at least two timeslots. Therefore, this option can only be selected when "All" timeslots are
selected.
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. Indoor losses are defined per frequency per
clutter class.
4. 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" timeslots in the Conditions tab, you can set the following parameters:
The HS-PDSCH RSCP relative to the RSCP threshold: Select one of the following in the Field list:
The HS-PDSCH EcNt relative to the EcNt threshold: Select one of the following in the Field list:
The peak RLC throughput relative to the threshold: Select "peak RLC throughput (kbps)" as the Field. Atoll displays the peak RLC throughput that the selected HSDPA bearer can provide. The peak RLC throughput is a characteristic of the HSDPA bearer.
The peak MAC throughput relative to the threshold: Select "Peak MAC throughput (kbps)" as the Field. Atoll calculates the peak MAC throughput from the transport block size of the selected HSDPA bearer.
If you have selected a particular timeslot in the Conditions tab, you can set the following parameters:
The uplink and downlink A-DPCH qualities: Select one of the following in the Field list:
The HS-SCCH power, reception level, or quality: Select one of the following in the Field list:
HS-SCCH power: Atoll determines the HS-SCCH power required per pixel to get an HS-SCCH Ec/Nt better than
the minimum required HS-SCCH Ec/Nt. The coverage is limited by the HS-SCCH Ec/Nt threshold defined for the
selected mobility type.
HS-SCCH RSCP: Atoll determines the HS-SCCH RSCP using the HS-SCCH power required per pixel to get an HSSCCH Ec/Nt better than the minimum required HS-SCCH Ec/Nt. The coverage is limited by the HS-SCCH Ec/Nt
threshold defined for the selected mobility type.
HS-SCCH Ec/Nt: Atoll determines the HS-SCCH Ec/Nt per pixel. The coverage is limited by the HS-SCCH Ec/Nt
threshold defined for the selected mobility type.
The HS-SICH power, reception level, or quality: Select one of the following in the Field list:
Max DL A-DPCH EbNt (dB): Atoll determines downlink A-DPCH quality at the receiver for the maximum traffic
channel power allowed for the selected timeslot.
Max UL A-DPCH EbNt (dB): Atoll determines uplink A-DPCH quality at the receiver for the maximum terminal
power allowed.
HS-SICH power: Atoll determines the HS-SICH power required per pixel to get an HS-SICH Ec/Nt better than
the minimum required HS-SICH Ec/Nt. The coverage is limited by the HS-SICH Ec/Nt threshold defined for the
selected mobility type.
HS-SICH RSCP: Atoll determines the HS-SICH RSCP using the HS-SICH power required per pixel to get an HSSICH Ec/Nt better than the minimum required HS-SICH Ec/Nt. The coverage is limited by the HS-SICH Ec/Nt
threshold defined for the selected mobility type.
HS-SICH Ec/Nt: Atoll determines the HS-SICH Ec/Nt per pixel. The coverage is limited by the HS-SICH Ec/Nt
threshold defined for the selected mobility type.
The HS-PDSCH reception level or quality: Select one of the following in the Field list:
HS-PDSCH RSCP: Atoll determines the HS-PDSCH RSCP using the HS-PDSCH power of the timeslot.
HS-PDSCH Ec/Nt: Atoll determines the HS-PDSCH Ec/Nt using the HS-PDSCH power of the timeslot.
For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window.
779
10.2.8.5.1
10.2.8.5.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.
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 10.9).
10.2.8.5.3
780
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 91.
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 "Geographic Export Zone" on page 68.
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 210.
AT332_UMR_E0
) in the Radio Planning toolbar. The Point Analysis window opens and the pointer
changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and the
current position. You can move the receiver on the map ("Moving the Receiver on the Map" on page 203).
2. At the top of the Point Analysis window, select the Reception view (see Figure 10.10).
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 receiver to its best server is also displayed in the
map window. The best server of the receiver is the transmitter from which the receiver 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. In the Reception view, select the carrier to be analysed.
) to display the Calculation Options dialog box and change the following:
Change the X and Y coordinates to change the current position of the receiver.
Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. For more information, see "Taking Shadowing into Account in Point Analyses" on page 204.
Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class. For more information, see "Taking Indoor Losses into Account" on page 203.
5. In the Reception view toolbar, you can use the following tools:
) to copy the content of the view and paste it as a graphic into a graphic editing or word-
You can display a point analysis that uses the settings from an existing prediction by
right-clicking the prediction in the Network explorer and selecting Open Point Analysis
from the context menu.
781
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 coverage predictions overlap (for example, pixels covered by
both predictions are displayed in red).
Merge: This display shows the area that is covered by either of the coverage predictions (for example, pixels covered
by at least one of the 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).
782
AT332_UMR_E0
Figure 10.12: Coverage prediction by P-CCPCH RSCP of the network with a 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 dialog box 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
Merge
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 10.13, shows clearly the area covered only by the new
base station.
783
Figure 10.14: Coverage prediction by P-CCPCH best server for the 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 dialog box.
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 10.15).
Figure 10.15: Coverage prediction by P-CCPCH best server of the 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 dialog box 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:
784
Intersection
Merge
Union
Difference
AT332_UMR_E0
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 10.16, shows clearly the increase in coverage due at the
change in antenna tilt.
For more information on automatic frequency allocation, see "Allocating Frequencies Automatically" on page 785.
785
Co-N-frequency allocation: The same carriers are allocated to cells of N-frequency mode compatible co-site transmitters.
Co-site transmitters using different frequency bands are not allocated carriers in co-N-frequency mode.
Diff-N-frequency allocation: Different carriers are allocated to cells of N-frequency mode compatible co-site
transmitters.
10.2.9.3.1
786
AT332_UMR_E0
The transmitters are coloured according to the carrier type, and the master carrier number is displayed on the map with each
transmitter.
10.2.9.3.2
Create, calculate, and display a coverage prediction by P-CCPCH best server, with the Display type set to "Discrete
values" and the Field set to "Cells: Carrier type". For information on creating a coverage by transmitter prediction, see
"Making a Coverage Prediction by P-CCPCH Best Server" on page 765.
Master carriers:
Stand-alone carriers:
Transmitters in N-frequency mode: The transmitters that are not N-frequency mode compatible.
One master carrier per transmitter: The transmitters that have either no or more than one master carrier.
Defined P-CCPCH power: The transmitters whose master carriers do not have a P-CCPCH power defined.
Defined P-CCPCH power: The transmitters whose stand-alone carriers do not have a P-CCPCH power defined.
Slave Carriers:
Linked to a master carrier: The transmitters whose slave carriers are not linked to any master carrier. In other
words, the transmitters that do not have any master carrier, but have slave carriers.
P-CCPCH, DwPCH, and Other CCH fields empty: The transmitters whose slave carriers have P-CCPCH, DwPCH,
and other CCH powers defined.
Timeslot configurations, Scrambling codes, and Neighbours same as the master carrier: Select this check box
if you want the audit to check for slave carriers that do not have the same timeslot configurations, scrambling
codes, and neighbours as the master carrier.
5. Click Calculate. Atoll performs the audit and lists the results under Problems occurred during the audit: X transmitters have inconsistencies, where X is the number of transmitters with problems. The list includes:
Several master carriers: Transmitters that have more than one master carrier.
Master P-CCPCH power not defined: Transmitters whose master carrier does not have a P-CCPCH power defined.
Stand-alone P-CCPCH power not defined: Transmitters whose stand-alone carriers do not have P-CCPCH powers
defined.
Slaves without masters: Transmitters that have only slave carriers and no master carrier.
Slave power defined: Transmitters whose slave carriers have P-CCPCH, DwPCH, or other CCH powers defined.
Master-slave attribute differences: Transmitters whose slave carriers have different timeslot configurations,
scrambling codes, and neighbours than the master carrier.
Inconsistency: N-frequency modecarrier types: Transmitters that are not N-frequency mode compatible.
787
6. Click Resolve to resolve the inconsistencies found by the audit. Atoll makes the timeslot configurations and scrambling
codes of the slave carriers the same as the master carrier. It also empties the neighbour list of the slave carriers.
7. Click Close to close the N-Frequency Mode Audit dialog box.
When it is cleared, only the defined Distance will be used to allocate neighbours to a reference transmitter.
When it is selected, click Define to open the Coverage Conditions dialog box:
Figure 10.17: TD-SCDMA coverage conditions for automatic intra-technology neighbour allocation
When it is cleared, only the defined Distance will be used to allocate neighbours to a reference transmitter.
When it is selected, click Define to open the Coverage Conditions dialog box and change the parameters below:
Resolution: Enter the resolution to be used to calculate cells coverage areas during automatic neighbour allocation.
P-CCPCH RSCP T_Add: Enter the minimum P-CCPCH RSCP required for a serving transmitter. If there is more than
one transmitter whose P-CCPCH RSCP is higher than P-CCPCH RSCP T_Add, the transmitter with the highest PCCPCH RSCP is kept as the serving transmitter.
P-CCPCH RSCP T_Drop: Enter the minimum P-CCPCH RSCP required for transmitters to enter a preliminary handover set. All the transmitters whose P-CCPCH RSCP is higher than P-CCPCH RSCP T_Drop are added to the set.
P-CCPCH RSCP T_Comp: Enter the handover set limit. From among the transmitters listed in the preliminary handover set using the P-CCPCH RSCP T_Drop, only the transmitters whose P-CCPCH RSCP is within the range defined
by the P-CCPCH RSCP from the best server and the P-CCPCH RSCP T_Comp margin are kept in the handover set.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this check box to take indoor losses into acccount in calculations. Indoor losses are
defined per frequency per clutter class.
788
Co-site cells as neighbours: When selected, the cells located on the same site as the reference cell will be automatically considered as neighbours. A cell with no antenna cannot be considered as a co-site neighbour.
Adjacent cells as neighbours (Intra-carrier Neighbours tab only): When selected, the cells that are adjacent to the reference cell will be automatically considered as neighbours. A cell is considered adjacent if there is at least one pixel in
AT332_UMR_E0
the reference cells coverage area where the potential neighbour cell is the best server, or where the potential neighbour cell is the second best server respecting the handover end.
Symmetric relations: Select this check box if you want the neighbour relations to be reciprocal, i.e. any reference
transmitter/cell is a potential neighbour of all the cells that are its neighbours.
Exceptional pairs: Select this check box to force the neighbour relations defined in the Intra-technology Exceptional
pairs table. For information on exceptional pairs, see "Exceptional Pairs" on page 223.
Description
When
Distance
Coverage
Co-Site
Adjacent
Symmetry
Exceptional Pair
Exceptional pairs
is selected
Existing
789
X 16 + Y 16 + Z
For example, the hexadecimal value "3Fh" would be calculated as shown below:
2
0 16 + 3 16 + 15 = 63
7. Click 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 dialog box appears.
9. Under Groups, enter the following information for each group you want to create.
790
AT332_UMR_E0
Excluded: Enter the scrambling codes within the range defined by the Min and Max fields 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, 36" means that the
extra scrambling codes are "1, 2, 3, 4, 5, 6".
10. Click another cell of the table to create the new group and add a new blank row to the table.
5. In the Code list column, enter the list of scrambling codes belonging to the new relativity cluster. Scrambling codes in
the code list must be separated by a single space.
6. Click another line of the table to create the new relativity cluster.
791
Under Intra-technology neighbours, you can set the constraint violation costs for Close neighbours, 1st order,
2nd order, and 3rd order neighbours. The close neighbour constraint violation cost should be higher than the 1st
order neighbour constraint violation cost, which should be higher than the 2nd order and the 3rd order should be
the lowest among all of these costs.
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 TD-SCDMA Cells
The allocation algorithm enables you to automatically allocate scrambling code 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: This strategy consists in using as many clusters as possible. Atoll will preferentially allocate codes
from different clusters.
One SYNC_DL code per site: This strategy allocates one SYNC_DL code to each base station, then, one code of the
cluster associated with the SYNC_DL code to each cell of each base station. When all the SYNC_DL codes have been
allocated and there are still base stations remaining to be allocated, Atoll reuses the SYNC_DL codes at another base
station. Select this strategy if you want to allocate the same scrambling code to the master and the slave carriers. For
more information on master and slave carriers, see "Planning Frequencies" on page 785.
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.
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 neighbour relations and
then choose the neighbourhood level to take into account:
Neighbours of a cell are referred to as first order neighbours, neighbours neighbours are referred to as second
order neighbours and neighbours neighbours neighbours as 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 "Neighbour Planning" on page 223.
792
AT332_UMR_E0
Atoll can take into account inter-technology neighbour relations as constraints to allocate
different scrambling codes to the TD-SCDMA 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 Atolldocument accessible in the TD-SCDMA Atoll
document. For information on making links between GSM and TD-SCDMA Atoll documents, see "Creating a TD-SCDMA Sector From a Sector in the Other Network" on
page 825.
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 scrambling code.
A reuse distance can be defined at the cell level (in the cell Properties dialog box or in the
Cells table). If defined, a cell-specific reuse distance will be used instead of the value
entered here.
Exceptional pairs: Select the Exceptional pairs check box if you want the automatic allocation process to consider the exceptional pair constraints.
Close neighbours: Select the Close neighbours check box if you want to take into account the scrambling code
relativity clusters in the automatic allocation. Enter the minimum Importance value and the maximum
Distance for determining the close neighbours.
Close neighbours are first order neighbours whose importance is higher than the minimum importance value
and are located within the maximum distance from the studied cell. Atoll will assign scrambling codes from
different relativity clusters to close neighbours. The Close neighbours constraint can be taken into account in
Clustered and Distributed per cell allocation strategies. For more information on scrambling code relativity
clusters, see "Defining Scrambling Code Relativity Clusters" on page 791.
From the Strategy list, you can select an automatic allocation strategy:
Clustered
Distributed per cell
One SYNC_DL code 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
scrambling codes to transmitters using the selected carrier) or all of them.
No. of codes per SYNC_DL: According to 3GPP specifications, the number of scrambling codes per SYNC_DL is 4.
If you want, you can change the number of codes per SYNC_DL.
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 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 keeps the currently
allocated scrambling codes and only allocates scrambling codes to cells that do not yet have codes allocated.
793
6. Click Commit. The scrambling codes are stored in the cell properties.
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 104.
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 in a group of transmitters,
you can allocate them automatically by selecting Scrambling Codes > Automatic
Allocation from the transmitter groups context menu.
No. of codes per SYNC_DL: Enter the number of scrambling codes per SYNC_DL. This number is set to 4 by default,
which is the number of scrambling codes attached to each SYNC_DL.
Neighbours: Select Neighbours in order 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: 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: 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.
794
AT332_UMR_E0
The report will list the cells and the neighbours that do not meet one of these constraints. In addition, it will indicate the allocated primary scrambling code and the neighbourhood level.
Neighbours in different SYNC_DLs: If you select the Neighbours in different SYNC_DLs check box, Atoll will check
that neighbour cells have scrambling codes from different SYNC_DLs. The report will list any neighbour cells that
has scrambling codes from the same SYNC_DL.
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, with respect to the configured
allocation constraints) is empty.
One SYNC_DL per site: If you select the One SYNC_DL per site check box, Atoll will check for and list base stations
whose cells have scrambling codes coming from more than one SYNC_DL.
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 among the ones defined for the two cells in their properties and the value that you set in the Code and
SYNC_DL Audit dialog box. Cell pairs that do not respect the reuse distance condition are listed according to the
distance between them, from the closest to the furthest away. The 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 have the same scrambling code allocated.
5. Click OK. Atoll displays the results of the audit in a text file called CodeCheck.txt. For each selected criterion, Atoll gives
the number of detected inconsistencies and the details of each.
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 Find on Map window.
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:
1. Select the Network explorer.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialog box appears.
795
Scrambling code: Select "Discrete values" as the Display type and "Cells: Scrambling code" as the Field.
Ranges of scrambling codes: Select "Value intervals" as the Display type and "Cells: Scrambling code" as the Field.
Scrambling code domain: 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:
Scrambling code: Select "Cells: Scrambling Code" from the Label or Tip Text Field Definition dialog box.
Scrambling code domain: Select "Cells: Scrambling Code Domain" from the Label or Tip Text Field Definition
dialog box.
5. Click OK.
For information on display options, see "Setting the Display Properties of Objects" on page 51.
Grouping Transmitters by Scrambling Code
You can group transmitters in the Network explorer by their scrambling code or scrambling code domain.
To group transmitters by scrambling code:
1. Select the Network explorer.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialog box appears.
4. On the General tab, click Group by. The Group dialog box appears.
5. Under Available fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
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
10. Click OK to save your changes and close the Group dialog box.
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.
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 SYNC_DLs as a function of the frequency of their use.
To display the scrambling code histogram:
1. Select the Network explorer.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Scrambling Codes > Code Distribution. The Distribution Histograms dialog box appears.
Each bar represents a scrambling code or a SYNC_DL code, its height depending on the frequency of its use.
4. Select Scrambling codes to display scrambling code use and Clusters to display SYNC_DL code use.
5. Move the pointer over the histogram to display the frequency of use of each scrambling code or SYNC_DL. The results
are highlighted simultaneously in the Zoom on selected values list.
796
AT332_UMR_E0
You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the
selected values.
Studying Scrambling Code Collision
You can make a scrambling code collision zones coverage prediction to view areas covered by cells using the same scrambling
code. For each pixel, Atoll checks if the best serving cell and the cells that fulfil all criteria to enter the active set (without any
active set size limitation) have the same scrambling code. If so, Atoll considers that there is a scrambling code collision.
To make a scrambling code collision zone coverage prediction:
1. Select the Network explorer.
2. Right-click the Predictions folder. The context menu appears.
3. Select New Prediction from the context menu. The Prediction Types dialog box appears.
4. Select Scrambling Code Collision Zones (DL) and click OK. The prediction Properties dialog box appears.
5. Click the General tab. On the General tab, you can change the assigned Name of the coverage prediction, the Resolution, and you can add a Comment. The Receiver height corresponds to the height of the receiver defined in the Calculation Parameters tab of the Network Settings Properties dialog box.
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the <GUID> and </GUID> tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
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 99.
6. Click the Conditions tab (see Figure 10.18). The coverage prediction parameters on the Conditions tab allow you to
define the signals that will be considered for each pixel. You can set:
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal
properties are used.
Service: The service to be considered in the coverage prediction. The body loss defined in the service properties
is used.
Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP threshold defined in
the mobility properties is used as the minimum requirement for the coverage prediction.
Carrier: The carrier to be considered in the coverage prediction.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the
highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter.
Timeslot: The scrambling code collision coverage prediction is performed for TS0.
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. Indoor losses are defined per frequency per
clutter class.
Pollution margin: The margin for determining which signals to consider. Atoll considers signal levels which are
within the defined margin of the best signal level.
797
Figure 10.18: Condition settings for a Scrambling Code Collision Zones coverage prediction
7. Click the Display tab.
For a scrambling code collision analysis coverage prediction, the Display type "Value intervals" based on the Field
"Interfered scrambling code" is available. Each interference zone will then be displayed in a colour corresponding to
the interfered scrambling code per pixel. For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
8. Click OK to save your settings.
9. Click the Calculate button (
) in the Radio Planning toolbar to calculate the scrambling code collision zone coverage
prediction. The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
A specific colour is assigned to areas where more than one scrambling code has interference. You can analyse these areas in
more detail using the Find on Map tool. For more information on using the Find on Map tool for scrambling code collision
analysis, see "Using Find on Map to Display Scrambling Code Allocation" on page 795.
798
AT332_UMR_E0
Timeslot Configuration
UDDDDD
16
80
UUDDDD
32
64
UUUDDD
48
48
UUUUDD
64
32
UUUUUD
80
16
UpUDDDD
16
64
UpUUDDD
32
48
TS0 is not used for traffic. TS1 is not used for traffic either in case of UpPCH shifting.
Assuming ideal dynamic channel allocation (DCA), all the resource units within a subframe, i.e., 6 x 16 = 96, can be allocated
and used. The total resource units in a network, i.e., the network capacity, is given by:
Network Capacity = Number of Timeslots per Subframe Number of Codes per Timeslot Number of Carriers
Resource units from different carriers can be shared and allocated to the same mobile connected to an N-frequency mode
compatible transmitter.
This section explains the network capacity and network dimensioning analysis tools:
Global scaling factor: If desired, enter a scaling factor to increase user density.
799
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 users (for environment and user profile traffic maps) or the rates per users (for live traffic maps per sector).
Select traffic maps to be used: Select the traffic maps you want to use for dimensioning.
Under Coverage, select the P-CCPCH best server coverage prediction to be used to distribute the traffic among the
cells of the network.
4. Click Calculate. Atoll distributes the traffic among cells using the information from traffic maps and the coverage prediction, calculates the capacity of each cell, and displays the results in the Results per Cell tab.
The Results per Cell tab has five columns which list the names of the cells in the network, and the numbers of uplink
and downlink resource units available and required per cell. The last row in this dialog box displays the total uplink
and downlink resource units, required and available. Cells for which the required resource units exceed the available
units are displayed in red. The uplink and downlink resource units overhead defined for each timeslot per cell is
considered when calculating the number of available resource units.
5. Click Commit to store the number of required resource units per cell in the Cells table.
6. Click Close to close the dialog box.
Changing transmitter parameters does not affect the dimensioning results if you have not updated the coverage by P-CCPCH
best server used for the dimensioning calculations. If you want to compare dimensioning results after modifying some transmitter parameters, you will have to calculate the coverage by P-CCPCH best server again and run the dimensioning calculations based on the new coverage prediction.
800
AT332_UMR_E0
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 using the R99 Radio
Bearer table. For information on defining R99 radio bearers, see "Defining R99 Radio Bearers" on page 835.
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 Services" on page 241.
Mobility types: In TD-SCDMA, information about receiver mobility is important to accurately model the channel characteristics: a mobile used in a speeding car or by a pedestrian will not necessarily undergo the same radio wave behaviour. EbNt or CI targets for uplink and downlink are largely dependent on mobile speed. For information on creating
a mobility type, see "Modelling Mobility Types" on page 247.
Terminals: In TD-SCDMA, 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 Terminals" on
page 249.
801
Atoll selects the preferred carrier defined in the properties of the service being used by the user if the preferred carrier
is available on the best server and if there are enough resources available on it to accommodate the user. Otherwise,
Atoll selects the carrier according to the selected DCA strategy.
Available RUs: The cell or timeslot with the most available resource units is selected.
Cell: Atoll calculates the number of available resource units for all the timeslots of all the cells of the users best
server. Next, Atoll selects the carrier with most number of available resource units.
Timeslot: Atoll selects the timeslots with the most available resource units.
Direction of Arrival: The cell or timeslot selected is the one which does not have an interfering mobile located nearby
at the same angle as the direction of arrival of the targeted mobile.
802
Cell: Atoll calculates the ISCP (Interference Signal Code Power) for all the timeslots of all the cells of the users best
server considering the effect of smart antenna equipment, if any. Next, Atoll selects the carrier with the lowest
ISCP and the lowest load that has enough free timeslots to support the users service.
Timeslot: Atoll selects the least loaded timeslots that have enough free OVSF codes for the users service.
Cell: Atoll calculates the number of interfering mobiles which are located in the same direction as the targeted
user for all the timeslots of all the cells of the users best server. Next, Atoll selects the carrier with the lowest
number of interfering mobiles in the direction of the targeted user.
AT332_UMR_E0
Timeslot: Atoll selects the timeslots with the lowest number of interfering mobiles in the direction of the targeted
user.
Cell: Atoll allocates the carriers to users one by one. For example, if there are 3 carriers, Atoll allocates carrier 0
to user 0, carrier 1 to user 1, carrier 2 to user 2, carrier 0 to user 3, and so on.
Timeslot: Atoll allocates timeslots to users one by one.
DCA reduces interference and maximises the usage of resource units. Resource units from different carriers can be shared and
allocated to the same mobile connected to an N-frequency mode compatible transmitter.
In TD-SCDMA networks, interference for a given timeslot can be of the following four types:
Next, Atoll performs uplink and downlink power control considering the effect of smart antenna equipment, if any. Atoll first
calculates the required terminal power in order to reach the EbNt or CI threshold required by the service in the uplink,
followed by the required traffic channel power in order to reach the EbNt or CI threshold required by the service in the
downlink. Atoll updates the downlink and uplink ISCP for all the users.
After carrying out power control, Atoll updates the cell load parameters. For each cell whose transmitter has smart antenna
equipment assigned, Atoll updates the geometrical distribution of power transmitted using the smart antenna in the downlink
for each timeslot, which has to be updated for each user. Atoll also saves the geometrical distribution of uplink loads calculated using the smart antenna in the uplink.
Atoll then carries out congestion and radio resource control, verifying the UL load, the total transmitted power, the number
of resource units, and OVSF codes consumed considering the services which require several timeslots.
At this point, the users can be either connected or rejected. They are rejected if:
On the downlink, the P-CCPCH RSCP is not high enough: status is "P-CCPCH RSCP < Min. P-CCPCH RSCP"
On the downlink, the power required to reach the user is greater than the maximum allowed: the status is "Ptch >
Max Ptch"
On the uplink, there is not enough power to transmit: the status is "Pmob > Max Pmob"
Even if constraints above are respected, the network (cell and timeslot) can 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 resource units in the cell: the status is "RU Saturation"
There is not enough power for cells: the status is "DL Load Saturation"
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
HS-PDSCH EcNt.
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
803
according to a random parameter which corresponds to a combination of the user rank in the simulation and the
HS-PDSCH EcNt.
After mobile scheduling, Atoll carries out a second fast link adaptation. HSDPA users are processed in the order defined by
the scheduler and the cells HSDPA power is shared among them.
10.3.3.2.1
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 and an activity status. The number of users per
activity status and the UL and DL throughputs 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 throughputs) is given.
The Sites tab: The Sites tab contains the following information per site:
JD Factor: The joint detection factor, defined in the site equipment, is used to decrease intra-cellular interference
in uplink.
MCJD Factor: The multi-cell joint detection factor, defined in the site equipment, is used to decrease uplink interference from mobiles in other cells.
Instantaneous HSDPA throughput (kbps): The instantaneous HSDPA throughput in kbps.
DL throughput (kbps): For each service, the aggregate downlink throughput of all the transmitters at each site.
UL throughput (kbps): For each service, the aggregate uplink throughput of all the transmitters at each site.
The Cells tab: Cell level results are determined from the results calculated per timeslot. The Cells tab contains the
following information, per site, transmitter, carrier:
804
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.
Max power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties.
AT332_UMR_E0
P-CCPCH power [TS0] (dBm): The P-CCPCH power as defined in the cell properties.
DwPCH power [DwPTS] (dBm): The DwPCH power as defined in the cell properties.
Other CCH power [DL Traffic TS] (dBm): The power of other common channels per timeslot.
DL load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total transmitted
power and the maximum power (powers stated in W). When the constraint "DL load" is set, the DL Load cannot
Used
exceed the user-defined maximum DL load. P Cell =
PTimeslot
Used
i DL
DL traffic power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic timeslot.
UL load factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between the
UL Load
UL Load
= Avg F Timeslot
uplink total interference and the uplink total noise. F Cell
i UL
UL noise rise (dB): The uplink noise rise is calculated from the uplink load factor. It indicates the signal degradation
due to cell load (interference margin in the link budget).
DL load factor (%): The downlink load factor for downlink timeslots. This factor corresponds to the ratio between
DL Load
DL Load
= Avg F Timeslot
the downlink total interference and the downlink total noise. F Cell
i DL
DL noise rise (dB): The downlink noise rise is calculated from the downlink load factor. It indicates the signal degradation due to cell load (interference margin in the link budget).
Number of DL radio links: The number of downlink radio links corresponds to the number of user-transmitter links
on the same carrier (i.e., the sum of the number of connected mobiles and the number of inactive mobiles). This
data indicates the number of users connected to the cell on the downlink.
Number of UL radio links: The number of uplink radio links corresponds to the number of user-transmitter links
on the same carrier (i.e., the sum of the number of connected mobiles and the number of inactive mobiles). This
data indicates the number of users connected to the cell on the uplink.
Connection success rate (%): The connection success rate gives the ratio of connected users to the total number
of users in the cell.
UL total requested throughput (kbps): The sum of all the uplink throughputs requested by the mobiles attempting
to connect to a carrier.
DL total requested rhroughput (kbps): The sum of all the downlink throughputs requested by mobiles attempting
to connect to a carrier.
UL total obtained throughput (kbps): The traffic carried by the cell in terms of throughput in the uplink.
DL total obtained throughput (kbps): The traffic carried by the cell in terms of throughput in the downlink.
Required UL resource units: The number of resource units required to carry the traffic demand in the uplink.
UL resource units: The number of resource units used in the cell in the uplink.
Required DL resource units: The number of resource units required to carry the traffic demand in the downlink.
DL resource units: The number of resource units used in the cell in the downlink.
Connection success rate (%) for each service: For each service, the connection success rate gives the ratio of connected users to the total number of users of that service in the cell.
The Timeslots tab: The Timeslots tab contains the following information, per site, transmitter, carrier, and timeslot:
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.
Max power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties.
P-CCPCH power [TS0] (dBm): The P-CCPCH power as defined in the cell properties.
Resource units: The number of resource units on a timeslot for carrying traffic. Each timeslot can have a maximum
of 16 resource units.
Other CCH power (dBm): The power of other common channels per timeslot.
DL traffic power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic timeslot.
Available HS-PDSCH power (dBm): The available HS-PDSCH power as defined in the timeslot properties. This is
the power available for the HS-PDSCH of HSDPA users. The value is either defined when the HS-PDSCH power is
allocated statically, or determined by a simulation when the option HS-PDSCH dynamic power allocation is
selected.
Transmitted HSDPA power (dBm): The power transmitted by the cell to serve users connected to HSDPA radio
bearers. If HSDPA power is allocated statically, the transmitted HSDPA power is equal to the available HSDPA
power. If HSDPA power is allocated dynamically, the transmitted HSDPA power is the remaining power after allocation of power to the users connected to R99 radio bearers, and the power headroom.
Angular distribution of UL and DL loads: The angular distribution of downlink transmitted power and uplink loads
computed for cells whose transmitters have smart antenna equipment. This field contains binary data if you are
using a third-party smart antenna model.
Max DL load (% Pmax): The maximum percentage of downlink power that a cell can use. It is defined either in the
cell properties or in the simulation creation dialog box.
DL load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total transmitted
power and the maximum power (powers stated in W). When the constraint "DL Load" is set, the DL Load cannot
exceed the user-defined Max DL Load.
805
Max UL load factor (%): The maximum uplink load factor not to be exceeded. This limit is taken into account during
the simulation if the option UL Load is selected. If the UL load option is not selected during a simulation, this value
is not taken into consideration.
UL load factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between the
uplink total interference and the uplink total noise.
UL noise rise (dB): The uplink noise rise is calculated from the uplink load factor. It indicates the signal degradation
due to cell load (interference margin in the link budget).
DL load factor (%): The downlink load factor for downlink timeslots. This factor corresponds to the ratio between
the downlink total interference and the downlink total noise.
DL noise rise (dB): The downlink noise rise is calculated from the downlink load factor. It indicates the signal degradation due to cell load (interference margin in the link budget).
The Mobiles tab: The Mobiles tab contains the following information:
Name: The name of the mobile as assigned during the random user generation.
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.
DL activity status: The activity status on the downlink assigned during the first random trial, during the generation
of the user distribution.
UL activity status: The activity status on the uplink assigned during the first random trial, during the generation of
the user distribution.
Indoor: This field indicates whether indoor losses have been added or not.
Connection status: The connection status indicates whether the user is connected 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.
HSDPA connection status: The connection status indicates whether the user is connected to an HSDPA radio
bearer, delayed, or rejected at the end of the simulation.
Best server: The users best server.
P-CCPCH RSCP: The received signal code power on the P-CCPCH pilot channel.
UL total requested throughput (kbps): For an R99 user, the uplink total requested throughput corresponds to the
uplink peak throughput of the R99 bearer associated to the service. For an HSDPA user, the uplink total requested
throughput corresponds to the peak throughput of ADPCH-UL64 R99 bearer.
DL total requested throughput (kbps): For an R99 user, the downlink total requested throughput corresponds to
the downlink peak throughput of the R99 bearer associated to the service. For an HSDPA user, the downlink total
requested throughput is the sum of the ADPCH-UL64 radio bearer peak throughput and the peak RLC throughput
that the selected HSDPA radio bearer can provide.
UL total obtained throughput (kbps): For an R99 user, the total obtained throughput is the same as the total
requested throughput if he is connected. If the user was rejected, the total obtained throughput is zero.
For an HSDPA user connected to an HSDPA bearer, the uplink total obtained throughput equals the total requested throughput. If the HSDPA user is delayed (he is only connected to an R99 radio bearer), the uplink total obtained throughput corresponds to the uplink peak throughput of ADPCH-UL64 radio bearer. Finally, if the HSDPA
user is rejected either in the R99 part or in the HSDPA part (because the HSDPA scheduler is saturated), the uplink
total obtained throughput is zero.
DL total obtained throughput (kbps): For an R99 user, the total obtained throughput is the same as the total
requested throughput if he is connected. If the user was rejected, the total obtained throughput is zero.
For an HSDPA user connected to an HSDPA bearer, the downlink total obtained throughput corresponds to the
instantaneous throughput; this is the sum of the ADPCH-UL64 radio bearer peak throughput and the peak RLC
throughput provided by the selected HSDPA radio bearer after scheduling and radio resource control. If the HSDPA
user is delayed (he is only connected to an R99 radio bearer), the downlink total obtained throughput corresponds
to the downlink peak throughput of ADPCH-UL64 radio bearer. Finally, if the HSDPA user is rejected either in the
R99 part or in the HSDPA part (because the HSDPA scheduler is saturated), the downlink total obtained throughput
is zero.
806
1st, 2nd, 3rd DL TS rank (carrier): A mobile can have at most three timeslots allocated for traffic. These timeslots
can be located on different carriers (cells) of the same transmitter. These columns list the numbers of the 1st, 2nd,
and 3rd timeslot assigned to a user, and the carrier number on which the timeslots are located. For example, if a
user is assigned two downlink timeslots, 4 and 6, on the carriers 0 and 2, the 1st DL TS Rank (Carrier) will be "4 (0)"
and 2nd DL TS Rank (Carrier) will be "6 (2)".
1st, 2nd, 3rd UL TS rank (carrier): A mobile can have at most three timeslots allocated for traffic. These timeslots
can be located on different carriers (cells) of the same transmitter. These columns list the numbers of the 1st, 2nd,
and 3rd timeslot assigned to a user, and the carrier number on which the timeslots are located. For example, if a
AT332_UMR_E0
user is assigned two uplink timeslots, 2 and 3, on the carriers 0 and 2, the 1st UL TS Rank (Carrier) will be "2 (0)"
and 2nd UL TS Rank (Carrier) will be "3 (2)".
1st, 2nd, 3rd TS mobile total power (UL) (dBm): The total mobile power corresponds to the total power transmitted by the terminal on the uplink and on the timeslots assigned to the mobile.
1st, 2nd, 3rd TS cell total power (DL) (dBm): The cell traffic power corresponds to the power transmitted by the
cell on the downlink for a mobile on the timeslots assigned to the mobile.
The following columns only appear if, when creating the simulation as explained in "Creating Simulations" on
page 266, you select "Detailed information about mobiles" under Information to retain:
1st, 2nd, 3rd TS extra interference of UL mobiles (DL) (dBm): The interference received on downlink timeslots
from mobiles transmitting in the uplink. This interference is calculated if you select the Calculate Interference
Between Mobiles option when creating the simulation.
1st, 2nd, 3rd TS required HSDPA power (dBm): This is the HSDPA power required to provide the HSDPA bearer
user with the downlink requested throughput.
1st, 2nd, 3rd TS obtained HSDPA power (dBm): This is the HSDPA power required to provide the HSDPA bearer
user with the downlink obtained throughput.
1st, 2nd, 3rd HSDPA TS rank (carrier): These columns list the numbers of the 1st, 2nd, and 3rd timeslot assigned
to an HSDPA user, and the carrier number on which the timeslots are located.
Requested HSDPA bearer index: The HSDPA bearer requested by an HSDPA user.
Obtained HSDPA bearer index: The HSDPA bearer assigned to an HSDPA user by the DCA and resource allocation
algorithm.
Clutter: The clutter class on which the mobile is located.
DL and UL 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.
Spreading angle (): The spreading angle used in the simulation. The value used is the spreading angle set in the
clutter classes.
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 266, you select "Detailed information about
mobiles" under Information to retain.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
The parameters related to the clutter classes, including the default values.
807
10.3.3.2.2
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 and an activity status. The number of users per
activity status and the UL and DL throughputs 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 throughputs) is given.
The Sites tab: The Sites tab contains the following information per site:
JD Factor: The joint detection factor, defined in the site equipment, is used to decrease intra-cellular interference
in uplink.
MCJD Factor: The multi-cell joint detection factor, defined in the site equipment, is used to decrease uplink interference from mobiles in other cells.
Instantaneous HSDPA throughput (kbps): The instantaneous HSDPA throughput in kbps.
DL throughput (kbps): For each service, the aggregate downlink throughput of all the transmitters at each site.
UL throughput (kbps): For each service, the aggregate uplink throughput of all the transmitters at each site.
The Cells tab: Cell level results are determined from the results calculated per timeslot. The Cells tab contains the
following information, per site, transmitter, carrier:
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.
Max power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties.
P-CCPCH power [TS0] (dBm): The P-CCPCH power as defined in the cell properties.
DwPCH power [DwPTS] (dBm): The DwPCH power as defined in the cell properties.
Other CCH power [DL Traffic TS] (dBm): The power of other common channels per timeslot.
DL load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total transmitted
power and the maximum power (powers stated in W). When the constraint "DL load" is set, the DL Load cannot
Used
PTimeslot
Used
i DL
DL traffic power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic timeslot.
UL load factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between the
UL Load
UL Load
= Avg F Timeslot
uplink total interference and the uplink total noise. F Cell
i UL
808
UL noise rise (dB): The uplink noise rise is calculated from the uplink load factor. It indicates the signal degradation
due to cell load (interference margin in the link budget).
AT332_UMR_E0
DL load factor (%): The downlink load factor for downlink timeslots. This factor corresponds to the ratio between
DL Load
DL Load
= Avg F Timeslot
the downlink total interference and the downlink total noise. F Cell
i DL
DL noise rise (dB): The downlink noise rise is calculated from the downlink load factor. It indicates the signal degradation due to cell load (interference margin in the link budget).
Number of DL radio links: The number of downlink radio links corresponds to the number of user-transmitter links
on the same carrier (i.e., the sum of the number of connected mobiles and the number of inactive mobiles). This
data indicates the number of users connected to the cell on the downlink.
Number of UL radio links: The number of uplink radio links corresponds to the number of user-transmitter links
on the same carrier (i.e., the sum of the number of connected mobiles and the number of inactive mobiles). This
data indicates the number of users connected to the cell on the uplink.
Connection success rate (%): The connection success rate gives the ratio of connected users to the total number
of users in the cell.
UL total requested throughput (kbps): The sum of all the uplink throughputs requested by the mobiles attempting
to connect to a carrier.
DL total requested rhroughput (kbps): The sum of all the downlink throughputs requested by mobiles attempting
to connect to a carrier.
UL total obtained throughput (kbps): The traffic carried by the cell in terms of throughput in the uplink.
DL total obtained throughput (kbps): The traffic carried by the cell in terms of throughput in the downlink.
Required UL resource units: The number of resource units required to carry the traffic demand in the uplink.
UL resource units: The number of resource units used in the cell in the uplink.
Required DL resource units: The number of resource units required to carry the traffic demand in the downlink.
DL resource units: The number of resource units used in the cell in the downlink.
Connection success rate (%) for each service: For each service, the connection success rate gives the ratio of connected users to the total number of users of that service in the cell.
The Timeslots tab: The Timeslots tab contains the following information, per site, transmitter, carrier, and timeslot:
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.
Max power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties.
P-CCPCH power [TS0] (dBm): The P-CCPCH power as defined in the cell properties.
Resource units: The number of resource units on a timeslot for carrying traffic. Each timeslot can have a maximum
of 16 resource units.
Other CCH power (dBm): The power of other common channels per timeslot.
DL traffic power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic timeslot.
Available HS-PDSCH power (dBm): The available HS-PDSCH power as defined in the timeslot properties. This is
the power available for the HS-PDSCH of HSDPA users. The value is either defined when the HS-PDSCH power is
allocated statically, or determined by a simulation when the option HS-PDSCH dynamic power allocation is
selected.
Transmitted HSDPA power (dBm): The power transmitted by the cell to serve users connected to HSDPA radio
bearers. If HSDPA power is allocated statically, the transmitted HSDPA power is equal to the available HSDPA
power. If HSDPA power is allocated dynamically, the transmitted HSDPA power is the remaining power after allocation of power to the users connected to R99 radio bearers, and the power headroom.
Angular distribution of UL and DL loads: The angular distribution of downlink transmitted power and uplink loads
computed for cells whose transmitters have smart antenna equipment. This field contains binary data if you are
using a third-party smart antenna model.
Max DL load (% Pmax): The maximum percentage of downlink power that a cell can use. It is defined either in the
cell properties or in the simulation creation dialog box.
DL load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total transmitted
power and the maximum power (powers stated in W). When the constraint "DL Load" is set, the DL Load cannot
exceed the user-defined Max DL Load.
Max UL load factor (%): The maximum uplink load factor not to be exceeded. This limit is taken into account during
the simulation if the option UL Load is selected. If the UL load option is not selected during a simulation, this value
is not taken into consideration.
UL load factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between the
uplink total interference and the uplink total noise.
UL noise rise (dB): The uplink noise rise is calculated from the uplink load factor. It indicates the signal degradation
due to cell load (interference margin in the link budget).
DL load factor (%): The downlink load factor for downlink timeslots. This factor corresponds to the ratio between
the downlink total interference and the downlink total noise.
DL noise rise (dB): The downlink noise rise is calculated from the downlink load factor. It indicates the signal degradation due to cell load (interference margin in the link budget).
The Initial Conditions tab: The Initial Conditions tab contains the following information:
809
The parameters related to the clutter classes, including the default values.
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:
Baton Handover Zones (DL): For information on making a baton handover coverage prediction, see "Making a
Baton Handover Coverage Prediction" on page 777.
810
Total Noise Level Analysis (DL): For information on making a downlink total noise coverage prediction, see "Studying Downlink Total Noise" on page 774.
Cell to Cell Interference Zones: For information on making a coverage analysis for cell-to-cell interference, see
"Studying Cell-to-Cell Interference" on page 775.
UpPCH Interference Zones: For information on making a coverage analysis for UpPCH interference in case of
UpPCH shifting, see "Studying UpPCH Interference" on page 776.
P-CCPCH Quality Analysis (EbNt) (DL) or P-CCPCH Quality Analysis (CI) (DL): For information on making a PCCPCH reception analysis, see "Making a Pilot Signal Quality Prediction" on page 770.
DwPCH Quality Analysis (CI) (DL): For information on making a DwPCH reception analysis, see "Making a DwPCH
Signal Quality Prediction" on page 771.
Service Area Analysis (EbNt) (DL) or Service Area Analysis (CI) (DL): For information on making a coverage prediction the downlink service area, see "Studying Downlink and Uplink Service Areas" on page 772.
Service Area Analysis (EbNt) (UL) or Service Area Analysis (CI) (UL): For information on making a coverage prediction the uplink service area, see "Studying Downlink and Uplink Service Areas" on page 772.
Effective Service Area Analysis (EbNt) or Effective Service Area Analysis (CI): For information on making a coverage analysis for the effective service area, see "Studying the Effective Service Area" on page 774.
HSDPA Quality and Throughput Analysis (DL): For information on making an HSDPA coverage prediction, see
"HSDPA Coverage Predictions" on page 778.
AT332_UMR_E0
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). Cells may be identified by their IDs or scrambling codes.
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:
1. Select the Network explorer.
2. Right-click the Drive Test Data folder. The context menu appears.
3. Select Import from the context menu. The Open dialog box appears.
4. Select the file or files you want to open. You can import one or several files.
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 dialog box 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 dialog box.
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 dialog box. 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 9.
811
When importing a drive test data path file, existing configurations are available in
the Files of type list of the Open dialog box, 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,
Figure 10.21: The Setup tab of the Import of Measurement Files dialog box
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 dialog box 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.
ii. In the By 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.
812
AT332_UMR_E0
ii. In the Scrambling code identifier box, enter a string that is found in the column names that identify the scrambling code of scanned cells. For example, if the string "SC" is found in the column names that identify the
scrambling code of scanned cells, enter it here. Atoll then searches for columns with this string in the column
name.
iii. In the Scrambling code format list, select the scrambling code format, "Decimal" or "Hexadecimal."
iv. In the Scrambling code group identifier box, enter a string that must be found in the column names that identify the scrambling code group of scanned cells. For example, if the string "SC_Group" is found in the column
names that identify 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.
f.
If you have correctly entered the information under File on the Setup tab, and the
necessary values in the Drive Test Data Setup dialog box, Atoll should recognise 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.
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 dialog box 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 Import 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 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 dialog box.
You can delete an existing import configuration by selecting the import configuration under Import configuration and clicking the Delete button.
9. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The drive
test data is imported into the current Atoll document.
813
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 10.25 on page 818), 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 "Setting the Display
Type" on page 52.
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 dialog box opens in which you can define the following display for
each single point of the measurement path:
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
useful when you have a very large number of points.
You can not use Advanced if the Fast display check box has been selected.
You can sort drive test data paths in alphabetical order in the Network explorer by
right-clicking the drive test data path 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 dialog box and select Save or Load from
the Display Configuration submenu.
814
"Filtering Incompatible Points Along Drive Test Data Paths" on page 815
"Predicting the Signal Level on Drive Test Data Points" on page 815
"Displaying Statistics Over a Drive Test Data Path" on page 816
"Extracting a Field From a Drive Test Data Path for a Transmitter" on page 817
"Analysing Data Variations Along the Path" on page 817.
AT332_UMR_E0
You can apply a filter on all the drive test data paths in the Drive Test Data folder
by selecting Filter from the context menu of the folder.
If you want to use the measurement points that you permanently deleted, you will
have to import the drive test data path again.
815
Figure 10.23: Selecting Measured Signal Levels for which Errors will be Calculated
7. Click OK. A new point prediction is created for the selected drive test data path.
8. Right-click the drive test data path. The context menu appears.
9. Select Calculations > Calculate All the Predictions from the context menu.
If you chose to have Atoll calculate the errors between measured and predicted signal levels, new columns are added to the
drive test data table for the predicted point signal level from the serving cell and the errors between the measured and
predicted values.
Figure 10.24: Drive Test Data Table after Point Signal Level Prediction (with Error Calculations)
New columns are also added for the predicted point signal level from each neighbour cell and the errors between the
predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For
more information on the Drive Test Data analysis tool, see "Analysing Data Variations Along the Path" on page 817.
The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main
matrix. For more information on propagation models, see Chapter 4: Radio Calculations and Models.
816
AT332_UMR_E0
10.4.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:
1. Select the Network explorer.
2. Click the Expand button ( ) to expand the Drive Test Data folder.
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 Selection for a Given Transmitter dialog box appears.
5. Under On the transmitter, select the transmitter for which you wish to extract a field.
6. Under For the fields, select the fields that you wish to extract for the selected transmitter.
7. Click OK. Atoll creates a new column in the drive test data path table for the selected transmitter and with the selected
values.
817
To analyse data variations using the Drive Test Data analysis tool.
1. Select Tools > Drive Test Data from the menu bar. The Drive Test Data analysis tool appears (see Figure 10.25).
Select the check box next to each field you want to display in the Drive Test Data analysis tool.
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 dialog box.
You can change the display status or the colour of more than one field at the same time by
selecting several fields. 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 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 analysis tool.
818
AT332_UMR_E0
4. You can display the data in the drive test data path in the following ways:
5. 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 10.25 on page 818). 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 "Setting the Display Type" on page 52.
6. You can display a secondary 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 dialog box. You select the value to be
displayed from the right-hand list at the top of the Drive Test Data analysis tool. The values are displayed in the colour
defined in the Display Parameters dialog box.
7. You can zoom in on the graph displayed in the Drive Test Data analysis tool in the following ways:
Zoom in or out:
i.
Right-click the Drive Test Data analysis tool. The context menu appears.
Right-click the Drive Test Data analysis tool on one end of the range of data you want to zoom in on. The context menu appears.
819
10.4.7 Printing and Exporting the Drive Test Data Analysis Tool
You can print and export the contents of the Drive Test Data analysis tool.
To print or export the contents of the Drive Test Data analysis tool:
1. Select Tools > Drive Test Data from the menu bar. The Drive Test Data analysis tool appears (see Figure 10.25 on
page 818).
2. Define the display parameters and zoom level as explained in "Analysing Data Variations Along the Path" on page 817.
3. Right-click the Drive Test Data analysis tool. The context menu appears.
To print the Drive Test Data analysis tool, select Print from the context menu.
To export the Drive Test Data window, select Copy from the context menu, then paste.
820
AT332_UMR_E0
Before starting a co-planning project, make sure that your main and linked documents
have the same geographic coordinate systems.
Select File > Open or File > New > From an Existing Database.
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.
821
ments. However, because working document is the main document, any changes made in the main document are not automatically taken into account in the linked document.
If you close the linked document, Atoll displays a warning icon (
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 107. 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
"Associating a Tip Text to an Object" on page 54.
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 "Changing the Order of
Layers" on page 51.
Figure 10.27 shows an example of TD-SCDMA transmitters with labels and displayed in the Legend window, and GSM transmitter data displayed in tip text.
822
AT332_UMR_E0
When you click the Calculate button, Atoll first 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 and Unlocking Coverage Predictions" on page 207.
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:
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.
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.
10.5.2.2.1
823
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 824 and "Studying Differences Between Coverage Areas" on page 825.
7. Calculate the linked coverage predictions again to study the effects of the changes on the linked coverage predictions.
10.5.2.2.2
10.5.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.
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 10.9). 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.
10.5.2.2.4
824
AT332_UMR_E0
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.
12. Select Properties from the context menu. The coverage prediction Properties dialog box appears.
13. Modify the display parameters of the coverage prediction.
14. Calculate the two coverage predictions again, if needed.
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 "Changing the Order of
Layers" on page 51.
10.5.2.2.5
825
Figure 10.29: 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 Refresh Folder Configuration and have to be set up manually.
When it is cleared, only the defined Distance will be used to allocate neighbours to a reference transmitter.
When it is selected, click Define for TD-SCDMA to open the corresponding Coverage Conditions dialog box:
Figure 10.30: TD-SCDMA coverage conditions for automatic inter-technology neighbour allocation
Resolution: Enter the resolution to be used to calculate cells coverage areas during automatic neighbour allocation.
Min pilot signal level: Enter a minimum pilot signal level.
Margin: Enter a handover margin.
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.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this check box to take indoor losses into acccount in calculations. Indoor losses are
defined per frequency per clutter class.
826
AT332_UMR_E0
Co-site neighbours: cells located on the same site as the reference transmitter will automatically be considered as
neighbours. A transmitter/cell with no antenna cannot be considered as a co-site neighbour.
Exceptional pairs: Select this check box to force the neighbour relations defined in the Inter-technology Exceptional
pairs table. For more information, see "Exceptional Pairs" on page 223.
Description
When
Distance
Coverage
Co-Site
Exceptional Pair
Exceptional pairs
is selected
Existing
827
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.
Name: Enter a name for the frequency, for example, "Band 2010." This name will appear in other dialog boxes
when you select a frequency band.
DL Start Frequency (MHz): Enter the downlink start 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 2010: First carrier: 0; Last carrier 1 and Band 900: First carrier: 2; Last
carrier: 2
7. When you have finished adding frequency bands, click the Close button (
).
You can also access the properties dialog box of each individual frequency band by double-clicking the left margin of the row
with the frequency band.
828
AT332_UMR_E0
DL powers: Under DL powers, you can define whether the power values on the downlink are Absolute or Relative to
pilot. The power values affected are the DwPCH powers and other common channel powers defined in the cell properties for TS0 and for each timeslot, as well as the minimum and maximum traffic channel powers defined for services.
Atoll converts the power values defined in the cell properties (i.e., DwPCH and other common channel 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.
Quality threshold type: Under Quality threshold type, you can select whether the signal quality thresholds entered
in the mobility types and radio bearers are EbNt or CI.
Atoll ensures consistency between the quality threshold parameter and the parameter which is calculated during
coverage predictions and Monte Carlo simulations. For example, if you set the Quality threshold type to EbNt, all the
signal quality thresholds are considered to be defined in terms of EbNt. If you calculate a CI-based coverage prediction or simulation, Atoll converts the thresholds from EbNt to CI, by removing the processing gain from the EbNt
values, in order to calculate and compare CI. Similarly, if the Quality threshold type is set to CI, and the calculations
are performed for Eb/Nt, Atoll converts all CI thresholds to EbNt for the calculations.
Spreading rate: The chip rate used in TD-SCDMA for spreading the user signals (1.28 Mcps by default).
P-CCPCH processing gain: The processing gain is the ratio of the spread bandwidth to the unspread bandwidth. It is
set to 13.8 dB (= 24 times) by default.
Processing Gain Calculation Example
The processing gain is the ratio between the chip rate transmitted on the air interface and
the throughput of a service.
W
G P = Processing Gain = ----R
Where W is the chip rate for TD-SCDMA, and R is the throughput per timeslot of the
service.
TS
The chip rate is calculated from the number of data chips per timeslot ( N Data Chips ) and the
subframe duration ( D Subframe ):
TS
N Data Chips
704
W = -------------------------= --------------- = 140800 bps
0,005
D Subframe
If the downlink and uplink throughputs of a service are 384 kbps and 64 kbps respectively,
the service throughputs per timeslot can be calculated by dividing by the number of timeslots (here, 3 in downlink and 1 in uplink):
R
DL
UL
384000
64000
= -------------------- = 128000 bps and R
= ---------------- = 64000 bps
3
1
GP
UL
140800
140800
= -------------------- = 1,1 = 0,414 dB and G P = -------------------- = 2,2 = 3,4242 dB
128000
64000
Spreading factor: Under Spreading factor, you have the minimum and maximum spreading factors allowed in
TD-SCDMA:
Min: The lowest spreading factor that can be used (1).
Max: The highest spreading factor that can be used (16).
Interference: Under Interference, you can define the parameter used to calculate interference on the downlink.
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.
HSDPA: Under HSDPA, you can define how total noise is calculated for HSDPA.
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.
829
Frame: Under Frame, you have all the frame and subframe parameters:
Number of timeslots per subframe: There are 7 timeslots in a TD-SCDMA subframe. These timeslots can be used
for uplink or downlink according to the timeslot configuration selected for each cell.
Duration: Under Duration, you have the frame and subframe duration:
Subframe: The duration of a TD-SCDMA subframe (5 ms).
Frame: The duration of a TD-SCDMA frame (10 ms). A frame includes two subframes of equal duration.
Number of chips per timeslot: Under Number of chips per timeslot, you have the number of chips corresponding
to the data, midamble, and the guard periods.
Guard period: The number of chips in the guard period of each timeslot (16).
Data: The number of data chips in each timeslot (704).
Midamble: The number of midamble chips in each timeslot (144).
The subframe duration, the number of timeslots per subframe, and the numbers of chips per timeslot are used to
calculate the processing gain for each service (see example below).
Number of pilot chips: Under Number of pilot chips, you have the description of the pilot timeslot:
Guard period: The number of chips in the guard period between DwPTS and UpPTS (96).
DwPTS: The Total number of chips used in the DwPTS timeslot (96), which are divided into a Guard period (32)
and a Synch period (64).
UpPTS: The Total number of chips used in the UpPTS timeslot (160), which are divided into a Guard period
(32) and a Synch period (128).
Min interferer reception threshold: This value is used by Atoll to limit the input of interferers in calculations. The performance of TD-SCDMA-specific coverage predictions and Monte Carlo simulations can be improved by setting a high
value of the 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 P-CCPCH RSCP threshold: The default minimum P-CCPCH RSCP required for a user to be connected to the cell.
The P-CCPCH RSCP is compared with this threshold to determine whether or not a user can be connected to the cell.
A minimum P-CCPCH RSCP threshold can be defined at the cell level (in the cell Properties
dialog box or in the Cells table). If defined, a cell-specific minimum P-CCPCH RSCP threshold will be used instead of the value entered here.
Height: The receiver height at which the path loss matrices and coverage predictions are calculated. Calculations
made on mobile users (from traffic maps) in Monte Carlo simulations are also carried out at this receiver height.
Default max range: The maximum coverage range of transmitters in the network.
Each transmitter in a TDD network has a maximum coverage range. This maximum system range is defined by the
distance after which the uplink and downlink signals can interfere with each other. The default value for the maximum
system range is 11250 m, which is the distance corresponding to the duration of the guard period in the pilot timeslot.
The maximum system range can be calculated as follows:
Each subframe of 5 ms duration contains 1 pilot timeslot and 7 downlink or uplink timeslots. The pilot timeslot is
divided into a downlink pilot timeslot (DwPTS), a guard period (GP), and uplink pilot timeslot (UpPTS). The lengths of
DwPTS, GP, and UpPTS are 96, 96, and 160 chips, respectively. Each of the other 7 timeslots contains 704 data chips,
144 midamble chips, and 16 guard period chips. All in all, a 5 ms subframe contains 6400 chips. The duration of the
guard period of the pilot can be calculated as:
0,005
D GP = --------------- 96 = 75 s
6400
The maximum system range is half the distance that the RF signal can travel in DGP:
8
75 s 3 10 m/s
R System = ----------------------------------------------------- = 11250 m
2
830
AT332_UMR_E0
3. Select Properties from the context menu. The Properties dialog box appears.
4. Select the Global Parameters tab.
In this tab you can set the following parameters: DL powers (Absolute or Relative to pilot), Quality threshold type
(Eb/Nt or C/I), Spreading rate, P-CCPCH processing gain, Spreading factor (Min and Max), Nt in Interference calculations (Total noise or Without useful signal).
5. Select the Calculation Parameters tab. On this tab you can set the following parameters:
Calculation limitation: In the Calculation limitation section, you can enter the Min interferer reception threshold
and Min P-CCPCH RSCP threshold.
Receiver: In the Receiver section, you can enter the receiver Height.
System: In the System section, select the Default max range check box if you want to apply a maximum system
range limit, and enter the maximum system range in the text box to the right.
For more information on the global network settings, see "TD-SCDMA Network Settings Properties" on page 829.
Grid of beams, optimum beamformer, conventional beamformer, adaptive beam, and third-party models require Monte
Carlo simulations to simulate the effect of the dynamic channel allocation (DCA) and power control. The results generated by
the Monte Carlo simulations using the smart antenna equipment based on any of these methods are stored in the TD-SCDMA
document, and can be reused for coverage predictions.
The statistical model does not require Monte Carlo simulations. Statistical modelling is based on simulation results in terms
of probabilities of CI gains, and can be used directly in coverage predictions. The smart antenna equipment that uses statistical modelling contains a list of CI gain graphs that depend on the spreading angle.
The following section explains how to work with smart antenna equipment in Atoll:
How smart antennas are used in dynamic channel allocation (DCA) during the Monte Carlo simulations is described in "The
Monte Carlo Simulation Algorithm" on page 801.
831
Although the number of beams in a GOB is not limited, calculation times with a large
number of beams will be longer.
10.6.4.1.1
).
6. Click the Properties button. The New Antenna List Properties dialog box appears.
7. Select the antennas from the Antennas column to add to the antenna list in each new row.
8. Click OK.
9. Click the Close button (
You can also export an antenna list to an external file by clicking the Export button, or import an existing antenna list by clicking the Import button in the New Antenna List Properties dialog box.
Adding Antennas to a Grid of Beams (GOB)
You can add antennas, or beams, from the antennas folder to an existing grid of beams or antenna list.
To add antennas to an antenna list:
1. Select the Parameters explorer.
2. Click the Expand button ( ) to expand the Radio Network Equipment folder.
3. Click the Expand button ( ) to expand the Antennas folder.
4. Right-click the antenna that you want to add to an antenna list. The context menu appears.
5. Select Add the Antenna to a List from the context menu. The Antenna Addition in a List dialog box appears.
6. Select the antenna list to which you want to add the antenna from the Antenna list.
7. Click OK to add the antenna to the list.
You can also add all the antennas in the Antennas folder or a view to an antenna list by selecting Antenna List > Add Antennas
to a List from the folders context menu.
Importing a Grid of Beams (GOB)
You can import existing antenna lists to be used as grids of beams in Atoll.
To import an antenna list:
1. Select the Parameters explorer.
2. Click the Expand button ( ) to expand the Radio Network Equipment folder.
3. Right-click the Antennas folder. The context menu appears.
4. Select Antenna List > Import Antennas from a List from the context menu. The Open dialog box appears.
5. Select an Index file to import.
6. Click Open to import the antenna list to Atoll. The Import of antennas from a list dialog box appears.
7. Enter a name for the new antenna list.
832
AT332_UMR_E0
833
You can create smart antenna equipment by defining how many antenna elements the equipment has and assigning it a single
element pattern from the antennas available in the Antennas folder.
During Monte Carlo simulations, smart antenna equipment using this model form a beam towards each served mobile in the
downlink by calculating the complex weights of the steering vector. In the uplink, apart from forming a beam in the direction
of each served mobile, the smart antenna equipment is also capable of cancelling interference by steering nulls (high attenuation points formed by the smart antenna) towards the interferers.
834
AT332_UMR_E0
8. Select Record Properties. The smart antenna properties dialog box appears.
9. On the General tab of this dialog box, you can modify the Name, Smart antenna model, and Comments.
10. Under Smart antenna model, click the Parameters button. A dialog box opens with the parameters specific to the
selected smart antenna model.
If you selected Grid of Beams (GOB) or Adaptive Beam as smart antenna model, this dialog box lets you select the
downlink and uplink beam patterns (from the Antennas Lists table). You can also view the beam patterns.
You can use the combined antenna pattern display to understand any inconsistencies in smart antenna results. If the beams and the main antenna do not have the
same gains, the smart antenna could provide worse results than the main antenna
for traffic timeslots.
If you selected Conventional Beamformer or Optimum Beamformer as the smart antenna model, this lets you
define the number of elements in the smart antenna array and select a single element pattern to be used in downlink as well as uplink.
If you selected Statistic as smart antenna model, this dialog box lets you define the probability threshold used to
read the CI gain graphs, and the CI gain graphs for different spreading angles.
Properties of external third-party smart antenna models may vary. You can access their
properties from the Smart Antenna Models folder in the Parameters explorer.
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 (
).
Uplink peak throughput (kbps): Enter or modify the uplink peak throughput.
Downlink peak throughput (kbps): Enter or modify the downlink peak throughput.
835
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.
Min TCH power (dBm): Enter the minimum downlink traffic channel power. The minimum and maximum traffic
channel power make up the dynamic range for downlink power control.
Max TCH power (dBm): Enter the maximum downlink traffic channel power.
The maximum and minimum traffic channel powers can be either absolute values or values
relative to the pilot power. For more information, see "Global Network Settings" on
page 828.
To define the number of downlink and uplink timeslots for different spreading factors:
7. Right-click an R99 bearer in the table. The context menu appears.
8. Select Record Properties. The R99 bearers properties dialog box appears.
9. Under Resource units, click the Browse button to the right of the timeslot field. The Resource Unit Consumption
dialog box appears.
10. In the Resource Unit Consumption dialog box, you can enter the number of OVSF codes of each length used for each
timeslot. This information is used to carry out network dimensioning and to simulate the Dynamic Channel Allocation
(DCA) algorithm. For information on calculating network capacity, see "Calculating TD-SCDMA Network Capacity" on
page 798. For information on the dynamic channel allocation, see "The Monte Carlo Simulation Algorithm" on
page 801.
11. Click OK.
12. Click the Close button (
836
AT332_UMR_E0
Name: The name you enter will be the one used to identify this piece of equipment.
Manufacturer: The name of the manufacturer of this piece of equipment.
JD factor: Joint Detection (JD) is a technology used to decrease intra-cellular interference in the uplink. JD is modelled by a coefficient from 0 to 1; this factor is considered in the UL interference calculation. In case JD is not supported by equipment, enter 0 as value.
MCJD factor: Multi-Cell Joint Detection (MCJD) is used to decrease uplink interference from mobiles in other cells.
MCJD is modelled by a coefficient from 0 to 1; this factor is considered in the UL interference calculation. If MCJD
is not supported by the equipment, enter 0 as value.
837
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 General tab. On the General tab, you can define the Name of the reception equipment.
6. Click the R99 Bearer Selection tab. On the R99 Bearer Selection tab, you can define downlink and uplink EbNt or CI
requirements (in dB) and the TCH thresholds (in dBm). The EbNt, or CI, quality targets are used to determine the
coverage area for the service, and the TCH thresholds must be reached to provide users with the service. These parameters depend on the mobility type.
Using Transmission and Reception diversity results in a quality gain on received downlink and uplink EbNt or CI. You
can specify gains on received downlink and uplink EbNt or CI for each diversity configuration. Atoll considers them
when transmission and reception diversity configurations are assigned to transmitters.
7. Click the HSDPA Bearer Selection tab. On the HSDPA Bearer Selection tab, you can enter the values of the Required
HS-PDSCH Ec/Nt for the Radio bearer index of each HSDPA radio bearer for different Mobility types. If you leave the
Mobility column empty, the same value will be considered valid for all mobility types.
8. Click the HSUPA Bearer Selection tab. On the HSUPA Bearer Selection tab, you can enter the values of the Required
E-PUCH Ec/Nt for the Radio bearer index of each HSDPA radio bearer for different Mobility types. If you leave the
Mobility column empty, the same value will be considered valid for all mobility types.
9. Click OK to close the reception equipment types Properties dialog box.
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 used by HSDPA TS: The maximum number of HS-PDSCH channels allowed to
be used by HSDPA timeslots for the category.
Max transport block size (bits): The maximum transport block size allowed for the category.
Highest modulation: The highest modulation supported by the UE category.
Max number of HS-PDSCH TS per TTI: The maximum number of HS-PDSCH timeslots allowed within a TTI (transmission time interval).
838
AT332_UMR_E0
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-PUCH channels used by HSUPA TS: The maximum number of E-PUCH channels allowed to be
used by HSUPA timeslots for the category.
Max transport block size (bits): The maximum transport block size allowed for the category.
Highest modulation: The highest modulation supported by the UE category.
Max number of HS-PUCH TS per TTI: The maximum number of E-PUCH timeslots allowed within a TTI (transmission time interval).
A point analysis (see "Studying the Profile Around a Base Station" on page 751).
A coverage prediction (see "Studying P-CCPCH RSCP for a Single Base Station" on page 763).
Atoll always takes shadowing into consideration when calculating a Monte Carlo-based TD-SCDMA simulation.
You can display the shadowing margins per clutter class. For information, see "Displaying the Shadowing Margins per Clutter
Class" on page 839.
Cell edge coverage probability: Enter the probability of coverage at the edge of the cell. The value you enter in
this dialog box is for information only.
Standard deviation: Select the type of standard deviation to be used to calculate the shadowing margin or macrodiversity gains:
From model: The model standard deviation. Atoll will display the shadowing margin of the signal level.
P-CCPCH EbNt or CI: The P-CCPCH EbNt or CI standard deviation. Atoll will display the P-CCPCH EbNt or C/
I shadowing margin.
DL EbNt or CI: The DL EbNt or CI standard deviation. Atoll will display the DL EbNt or CI shadowing margin.
UL EbNt or CI: The UL EbNt or CI standard deviation. Atoll will display the UL EbNt or CI shadowing margin
839
840
Chapter 11
LTE Networks
This chapter provides
information on using Atoll to
design, analyse, and
optimise an LTE network.
842
AT332_UMR_E0
11 LTE Networks
LTE (Long Term Evolution) refers to the set of 3GPP (3rd Generation Partnership Project) Release 8 and later specifications
that describe the next steps, or evolution, of the existing GERAN (GSM EDGE Radio Access Networks) and UTRAN (UMTS
Terrestrial Radio Access Networks) specifications. The 3GPP LTE specifications describe the building blocks of E-UTRA (Evolved
UTRA) networks.
LTE uses SOFDMA (Scalable Orthogonal Frequency Division Multiple Access) and SC-FDMA (Single-Carrier Frequency Division
Multiple Access) technologies in the downlink and the uplink, respectively. The aim of LTE is to provide mobile broadband
wireless access that supports handovers between LTE cells as well as between LTE and UMTS/GSM cells at high user speeds.
The Atoll LTE module enables you to design and optimise LTE broadband wireless access networks. You can use Atoll to
predict radio coverage, manage mobile and fixed subscriber data, and evaluate network capacity. The LTE module also
supports smart antennas, MIMO, carrier aggregation, and coordinated multipoint transmission and reception (CoMP).
With Atoll, you can model fixed and mobile users in LTE environments. The data input corresponding to mobile users and fixed
subscribers is modelled through comprehensive support of mobile user traffic maps and subscriber databases. You can carry
out calculations on fixed subscriber locations as well as base your calculations on mobile user scenarios during Monte Carlo
simulations. You can also perform interference predictions, resource allocation, and other calculations on mobile users.
Atoll uses Monte Carlo simulations to generate realistic network scenarios (snapshots) using a Monte Carlo statistical engine
for scheduling and resource allocation. Realistic user distributions can be generated using different types of traffic maps. Atoll
uses these user distributions as input for the simulations.
You can create coverage predictions to analyse the following and other parameters for LTE channels in downlink and in uplink:
Signal levels
Carrier-to-interference-and-noise ratio
Service areas and radio bearer coverage
Cell capacity and throughputs per cell
Coverage predictions that depend on network traffic loads can be created from either Monte Carlo simulation results or from
a user-defined network load configuration (uplink and downlink traffic loads, and uplink noise rise). GSM GPRS EDGE, UMTS
HSPA, CDMA2000, TD-SCDMA, and WiMAX networks can be planned in the same Atoll session.
Before working with the LTE module for the first time, it is highly recommended to go
through the "Glossary of LTE Terms" on page 984. This will help you get accustomed to the
terminology used by the 3GPP and in the product.
You can open an existing Atoll document by selecting File > Open.
You can create a new Atoll document as explained in Chapter 1: Working Environment.
You can also add base stations using a base station template (see "Placing a New Base Station Using a Station
Template" on page 855) and study the terrain profile in different directions from a base station (see "Studying the
Profile Around a Base Station" on page 859).
3. Carry out basic coverage predictions ( 3 ).
4. Allocate neighbours ( 4 ).
5. Allocate frequencies ( 5 ).
843
7. Before making more advanced coverage predictions, you need to define cell load conditions ( 7 ).
You can define cell load conditions in the following ways:
You can generate realistic cell load conditions by creating a simulation based on traffic maps ( 7a , 7b , and 7c )
(see "Studying LTE Network Capacity" on page 924).
You can define cell load conditions manually either on the Cells tab of each transmitter Properties dialog box or
in the Cells table (see "Creating or Modifying a Cell" on page 855) ( 7d ).
8. Make LTE-specific signal quality coverage predictions using the defined cell load conditions ( 8 ).
9. If necessary, modify network parameters to study the network with a different frequency plan ( 10 ). After modifying
the networks frequency plan, you must perform steps 7 and 8 again.
1
7a
7d
7c
7b
10
844
AT332_UMR_E0
feeder cables, and so on. In an LTE project, you must also add cells to each transmitter. A cell refers to the characteristics of
an RF channel on a transmitter.
Atoll lets you create one site, transmitter, or cell at a time, or create several at once using station templates. In Atoll, a base
station refers to a site and a transmitter with its antennas, equipment, and cells.
In Atoll, you can study a single base station or a group of base stations using coverage predictions. You can make a variety of
coverage predictions, such as signal level or signal quality coverage predictions. The results of calculated coverage predictions
can be displayed on the map, compared, and studied.
Atoll enables you to model network traffic by creating services, users, user profiles, traffic environments, and terminals. This
data can be then used to make coverage predictions that depend on network load, such as C/(I+N), service area, radio bearer,
and throughput coverage predictions.
This section covers the following topics:
Name: A default name is proposed for each new site. You can modify the default name here. If you want to change
the default name, 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 dialog box afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 57.
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.
LTE Tab
S1 interface throughputs: You can enter the maximum S1 interface throughputs supported in downlink and uplink by
the site. The S1 interface connects eNode-Bs to the evolved packet core (EPC) entities, the mobility management
entity (MME) and the serving gateway (S-GW). The capacity of the S1 interface between the eNode-B and the serving
gateway imposes a limit on the cumulated throughput served by the cells of the same eNode-B (site in Atoll). Hence,
this limit also imposes a limit on the throughput of each individual user served by the eNode-B. Here you must enter
the capacity of the S1-U interface (S1-U is the user-plane interface between eNode-Bs and the serving gateways). The
845
maximum S1 interface throughputs that you enter here can be taken into account in Monte Carlo simulations as backhaul constraints.
Relay Link: If the site is a relay node, click the Relay Link button to define the relay-to-donor backhaul parameters. For
more information on relay links, see "Creating a Relay Node" on page 873.
Name: By default, the transmitter is named after the site it is on, suffixed with an underscore and a number.
You can enter a name for the transmitter. However, it is better to use the name assigned
by Atoll to ensure consistency. 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. For information on the site Properties dialog box, see "Site
Properties" on page 845. You can click the New button to create a new site for the transmitter.
Shared antenna: This field identifies the transmitters, repeaters, and remote antennas that are located at the same
site or on sites with the same position and that share the same antenna. The entry in the field must be the same for
all transmitters, repeaters, and remote antennas that share the same antenna. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the
same changes to all other transmitters, repeaters, and remote antennas that are defined as having a shared antenna.
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 relative to the site coordinates, and 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.
Transmitter Tab
Active: Select this option to specify whether the transmitter is active or inactive. Transmitters are displayed in the Network explorer with an active ( ) or inactive ( )icon.
Only active transmitters are taken into consideration during calculations.
Transmitter type: Specify whether the transmitter is to be considered as a server. This enables you to model the coexistence of different networks in the same geographic area.
If the transmitter is a potential server as well as an interferer, set the transmitter type to Intra-network (Server
and interferer).
If the transmitter is to be considered only as an interferer, set the type to Inter-network (Interferer only). Interferer-only transmitters are ignored by coverage calculations and do not serve any mobile in Monte Carlo simulations.
For more information on how to study interference between co-existing networks, see "Modelling the Co-existence
of Networks" on page 980.
846
Transmission/Reception: This area displays the total losses and the noise figure of the transmitter. Losses and noise
are calculated according to the characteristics of the equipment that is assigned to the transmitter. To assign equipment, open the Equipment Specifications window by clicking the Equipment button. For more information about
assigning equipment to a transmitter, see "Assigning Equipment to a Transmitter" on page 854.
AT332_UMR_E0
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 coverage predictions even if
they are different from the values in the Computed boxes. The information in the real
Noise figure box is calculated from the information you entered in the Equipment Specifications dialog box. You can modify the real Total losses at transmission and reception and
the real Noise figure at reception. 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.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on page 159
Mechanical Azimuth, Mechanical Downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt display additional antenna parameters.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
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.
Smart antenna: Under Smart antenna, the smart antenna equipment is available in the Equipment list. You can
click the Browse button to access the properties of the smart antenna equipment. When you select smart antenna
equipment, you can choose whether to keep the current main antenna model or to replace it with the main
antenna model defined for the selected smart antenna equipment, if any. For more information on smart antenna
equipment, see "Smart Antenna Systems" on page 970.
Number of antenna ports: Select the number of antenna ports used for MIMO in the Transmission and Reception
fields. For more information on how the number of antenna ports are used, see "Multiple Input Multiple Output
Systems" on page 972.
Under Secondary antennas, you can select one or more secondary antennas in the Antenna column and enter
their Azimuth, Mechanical 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.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
The transmission power is divided among the main and secondary antennas. This
is not compatible with smart antennas. You must not assign smart antennas to
transmitters with secondary antennas, and vice versa.
In calculations, repeaters and remote antennas are transparent to the donor transmitters and the served users. For example, smart antennas at donor transmitters
target the served users directly and not the repeater or remote antenna that covers
the users. This results in a combined signal level received from the transmitter using
the smart antenna and from the repeater or remote antenna. If this approach does
not match how your equipment works, you must not assign smart antennas to
transmitters with repeaters and remote antennas, and vice versa. This is also true
for MIMO.
The main antenna is used to transmit the control channels. Coverage predictions based on the reference signals are
performed using the main antenna. The main antenna is also used for traffic if there is no smart antenna equipment
selected for the transmitter, or if the cells do not support AAS.
847
If smart antenna equipment is assigned to the transmitter and the cells support AAS, traffic data is transmitted and
received using the smart antenna, whereas the control channels are transmitted using the main antenna.
Cell Tab
When you create a transmitter, Atoll automatically creates a cell for the transmitter using the properties of the currently
selected station template.
The cell tab enables you to configure the properties for every cell of a transmitter. For more information on the properties of
a cell, see "Cell Properties" on page 848.
Propagation Tab
Transmitters are taken into account during calculations. Therefore, you must specify their 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. For information on propagation models, see "Assigning Propagation Parameters" on page 187.
Display Tab
On the Display tab, you can modify how a transmitter will be displayed. For information on changing display properties, see
"Setting the Display Properties of Objects" on page 51.
Name: By default, Atoll names the cell after its transmitter, adding a suffix in parentheses. If you change transmitter
name, 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 Administrator Manual.
ID: You can enter an ID for the cell. This is a user-definable network-level parameter for cell identification.
Active: If this cell is to be active, you must select the Active check box.
Layer: The network layer to which the cell belongs. This information is used in determining the serving cell. For more
information on defining layers, see "Defining Network Deployment Layers" on page 962. For more information on the
cell selection options, see "Global Network Settings" on page 959.
Cell type: This indicates whether the cell supports LTE (3GPP releases 8 and 9) or LTE-Advanced (3GPP releases 10 and
later) including carrier aggregation and CoMP. A cell can support LTE as well as LTE-A, so it can be configured as an LTE
cell, an LTE-A PCell (primary cell), or an LTE-A SCell (secondary cell).
Both LTE and LTE-A users can connect to LTE-only cells without the possibility of performing carrier aggregation or
CoMP. Cells that only support LTE-A, and not LTE, can only serve LTE-A users. The process of only allowing LTE-A users
to connect to a cell and excluding all LTE users is called cell barring.
If the cell type is left empty, the cell is considered LTE-only.
A cell must be an LTE-A SCell in downlink in order to also be an LTE-A SCell in uplink.
For more information on carrier aggregation modes and groups, see "Working With Cell
Groups" on page 862.
Only cells of type LTE-A PCell can perform coordinated multipoint transmission and reception (CoMP). Whether an LTE-A PCell performs CoMP is defined through CoMP cell groups,
or CoMP sets. For more information, see "Working With Cell Groups" on page 862.
Frequency band: The cells frequency band from the frequency band list.
Channel number: The number of the channel from the list of available channels.
For calculating path loss matrices of a multi-cell transmitter, Atoll uses the downlink start
frequency of the frequency band assigned to the cell with the highest priority layer.
848
AT332_UMR_E0
Order: The display order of a cell within the transmitter. This value is used to determine the order in which information
related to a cell is displayed in the Network explorer and on the map. This field is automatically filled by Atoll but you
can change these default values to display cells in a different order.
The consistency between cell order values is verified by Atoll. However, inconsistencies
may arise if other tools modify the database. You can check for inconsistencies in the cell
display order and fix them by selecting Data Audit > Cell Display Order Check in the Document menu.
Channel allocation status: The status of the current channel allocated to the cell:
Not allocated: The AFP considers a Not allocated channel modifiable without cost.
Allocated: The AFP considers an Allocated channel modifiable but only if absolutely necessary.
Locked: The AFP considers a Locked channel not modifiable.
For more information on the AFP, see "Configuring Network Parameters Using the AFP" on page 905.
Physical cell ID: The physical cell ID of the cell. It is an integer value from 0 to 503. The physical cell IDs are defined in
the 3GPP specifications. There are 504 unique physical-layer cell identities. The physical cell IDs are grouped into 168
unique cell ID groups (called SSS IDs in Atoll), with each group containing 3 unique identities (called PSS IDs in Atoll).
An SSS ID is thus uniquely defined by a number from 0 to 167, and a PSS ID is defined by a number from 0 to 2. Each
cells reference signals transmit a pseudo-random sequence corresponding to the physical cell ID of the cell.
Physical cell IDs also indicate the subcarriers being used for reference signal transmission in the downlink. Reference
signal hopping, or v-shifting, is the calculation of the index of the subcarrier being used for reference signal resource
elements. The v-shifting index is calculated as (PCI)Mod 6 for single-antenna transmitters and as (PCI)Mod 3 for multiantenna transmitters.
PSS ID: The PSS ID corresponding to the current physical cell ID. This value is determined automatically from the physical cell ID.
PSS ID status: The status of the PSS ID currently assigned to the cell:
Not allocated: The AFP considers a Not allocated PSS ID modifiable without cost.
Allocated: The AFP considers an Allocated PSS ID modifiable but only if absolutely necessary.
Locked: The AFP considers a Locked PSS ID not modifiable.
SSS ID: The SSS ID corresponding to the current physical cell ID. This value is determined automatically from the physical cell ID.
SSS ID status: The status of the SSS ID currently assigned to the cell:
Not allocated: The AFP considers a Not allocated SSS ID as modifiable without cost.
Allocated: The AFP considers an Allocated SSS ID as modifiable only if absolutely necessary.
Locked: The AFP considers a Locked SSS ID as not modifiable.
To lock the physical cell ID assigned to a cell, you must set both PSS ID status and SSS ID
status to Locked.
Physical cell ID domain: The physical cell ID domain to which the allocated physical cell ID belongs. This and the reuse
distance are used by the AFP for physical cell ID allocation.
PRACH Root Sequences: The logical PRACH root sequences allocated to the cell. The assigned logical PRACH RSIs are
always consecutive values and are listed using the convention "X-Y" with X being the smallest logical PRACH RSI in the
list and Y the largest.
Number of Required PRACH RSI: The number of required PRACH RSIs for this cell. The number or PRACH RSIs needed
for any cell depends on the used PRACH preamble format and the cell size. For theoretical values of the required numbers of PRACH RSIs mapped to various cell sizes, see "Mapping of Cell Size to Required Numbers of PRACH RSIs" on
page 981. The minimum value for the required number of PRACH RSIs is 1. If you enter 0, it will be considered as 1 by
the AFP.
PRACH RSI Allocation Status: The status of the current PRACH root sequence indexes allocated to the cell:
Not allocated: The AFP considers a Not allocated PRACH RSIs as modifiable without cost.
Allocated: The AFP considers an Allocated PRACH RSIs as modifiable only if absolutely necessary.
Locked: The AFP considers a Locked PRACH RSIs as not modifiable.
PRACH RSI domain: The PRACH RSI domain to which the allocated PRACH root sequences belong. This is used, alongside the reuse distance, by the AFP for PRACH RSI allocation.
Reuse distance: The minimum reuse distance after which the channel, physical cell ID, or PRACH root sequence
indexes assigned to this cell can be assigned to another cell by the AFP.
For more information on the AFP, see "Configuring Network Parameters Using the AFP" on page 905.
Max power (dBm): The cells maximum transmission power. You can enter or modify this value if the RS EPRE option
under the Advanced options on the Global Parameters tab of the LTE Network Settings folders Properties dialog box
is set to any of the following:
849
The transmission powers corresponding to different channels are calculated using Max power, the energy per
resource element offsets defined for the SS, PBCH, PDSCH, and PDCCH, and the number of resource elements corresponding to each channel, all of which are also calculated by Atoll.
Max power is calculated by Atoll from the user-defined RS EPRE value if the RS EPRE option in the Global Parameters
of the LTE Network Settings folder is set to User-defined.
RS EPRE per antenna port (dBm): The reference signal energy per resource element. You can enter or modify this
value if the RS EPRE option under the Advanced options on the Global Parameters tab of the LTE Network Settings
folders Properties dialog box is set to User-defined or Independent of max power.
This value is calculated by Atoll from the user-defined max power value if the RS EPRE option under the Advanced
options on the Global Parameters tab of the LTE Network Settings folders Properties dialog box is set to any of the
following:
SS EPRE Offset/RS (dB): The difference in the energy of a resource element belonging to the synchronisation signals
with respect to the energy of a reference signal resource element. This value is used to calculate the transmission
power corresponding to the primary and secondary synchronisation signals (PSS, SSS).
PBCH EPRE Offset/RS (dB): The difference in the energy of a resource element belonging to the PBCH with respect to
the energy of a reference signal resource element. This value is used to calculate the transmission power corresponding to the physical broadcast channel (PBCH).
PDCCH EPRE Offset/RS (dB): The difference in the energy of a resource element belonging to the PDCCH with respect
to the energy of a reference signal resource element. This value is used to calculate the transmission power corresponding to the physical downlink control channel (PDCCH).
PDSCH EPRE Offset/RS (dB): The difference in the energy of a resource element belonging to the PDSCH with respect
to the energy of a reference signal resource element. This value is used to calculate the transmission power corresponding to the physical downlink shared channel (PDSCH).
Atoll first calculates the energy per resource element corresponding to the reference signal resource elements, the
SS, PBCH, PDSCH, and PDCCH. Once the energies available for each of these resource element types are known, they
are converted into transmission powers for further calculations. In the offset fields above, you must enter the offsets,
i.e., the difference in the energy levels, for one resource element of each type. For example, if a resource element
belonging to the SS has 3 dB less energy than a resource element of the downlink reference signals, you should enter
-3 dB in the SS EPRE Offset. Atoll will then calculate the actual transmission power of the SS, i.e., all the resource
elements of the SS, from this offset and the number of SS resource elements per frame.
Instantaneous RS power (dBm): The instantaneous reference signal transmission power calculated from the maximum power or RS EPRE and the EPRE offsets.
Instantaneous SS power (dBm): The instantaneous SS transmission power calculated from the maximum power or RS
EPRE and the EPRE offsets.
Instantaneous PBCH power (dBm): The instantaneous PBCH transmission power calculated from the maximum
power or RS EPRE and the EPRE offsets.
Average PDCCH power (dBm): The average PDCCH transmission power calculated from the maximum power or RS
EPRE and the EPRE offsets.
Average PDSCH power (dBm): The average PDSCH transmission power calculated from the maximum power or RS
EPRE and the EPRE offsets.
If the cells transmitter has a beamforming smart antenna equipment assigned to it, the transmission powers of the
cell increase by 10 Log n (in dB), where n is the number of antenna elements of the beamforming smart antenna.
This gain in transmission powers is referred to as the AAS power combining gain.
850
Min RSRP (dBm): The minimum RSRP required for a user to be connected to the cell. The RSRP is compared with this
threshold to determine whether or not a user is within the cells coverage or not.
Cell selection threshold (dB): You can define the cell selection threshold to use for cell selection based on layer priority. The cell selection threshold is used in LTE networks in order to adjust the Min RSRP threshold of cells belonging
to different priority layers. This cell-level parameter is also known as "ThreshHighx,p".
Cell individual offset (dB): Specify the cell individual offset (CIO) to use for cell selection. The CIO is used in LTE networks in order to tune or bias the ranking of potential servers for cell selection in connected mode.
AT332_UMR_E0
When opening an existing Atoll 3.2.1 document in Atoll 3.3.2, the Cell individual offset
(dB) field is automatically filled using the contents of the custom field
CELL_RESELECT_OFFSET if it had been added to the Cells table in Atoll 3.2.1.
CELL_RESELECT_OFFSET (also known as Qoffset) is no longer used in calculations as these
have been enhanced to model the connected mode mobility rather than the idle mode cell
selection.
If you want to return to the cell selection mechanism based on the CELL_RESELECT_OFFSET
as in Atoll 3.2.1, you must add a custom field named CELL_RESELECT_OFFSET of type float
to the Cells table.
Handover margin (dB): Specify the handover margin to use for cell selection. The handover margin is used in LTE networks to avoid handover ping-pong between cells.
Reception equipment: You can select the cells reception equipment from the reception equipment list. For more
information, see "Defining LTE Reception Equipment" on page 965.
Scheduler: The scheduler used by the cell for bearer selection and resource allocation. You can select the scheduler
from the list of schedulers available in the Schedulers table. For more information see "Defining LTE Schedulers" on
page 968.
Max number of users: The maximum number of simultaneous connected users supported by the cell.
No. of users (DL): The number of users connected to the cell in the downlink. This can be user-defined or an output
of Monte Carlo simulations.
No. of users (UL): The number of users connected to the cell in the uplink. This can be user-defined or an output of
Monte Carlo simulations.
TDD subframe configuration: The subframe configuration used by the cell when the cells frequency band is TDD. You
can select a subframe configuration of type DSUUU-DSUUU, DSUUD-DSUUD, DSUDD-DSUDD, DSUUU-DSUUD,
DSUUU-DDDDD, DSUUD-DDDDD, or DSUDD-DDDDD.
TDD subframe configuration is hidden when there is no TDD frequency band defined in
the Frequency Bands table (see "Defining Frequency Bands" on page 958.
Diversity support (DL): The type of antenna diversity technique (none, transmit diversity, SU-MIMO, MU-MIMO, and
AAS) supported by the cell in downlink.
Diversity support (UL): The type of antenna diversity technique (none, receive diversity, SU-MIMO. and MU-MIMO)
supported by the cell in uplink.
Specific calculations are performed (and gains applied) for terminals supporting AAS and MIMO.
Number of co-scheduled MU-MIMO users (DL): The average number of MU-MIMO users that share the same
resources on the downlink. This can be either user-defined or an output of Monte Carlo simulations. In downlink
throughput coverage predictions, cell capacity is multiplied by this gain on pixels where MU-MIMO is used.
Number of co-scheduled MU-MIMO users (UL): The average number of MU-MIMO users that share the same
resources on the uplink. This can be either user-defined or an output of Monte Carlo simulations. In uplink throughput
coverage predictions, cell capacity is multiplied by this gain on pixels where MU-MIMO is used.
Fractional power control factor: This factor is used for path loss compensation when performing fractional power
control on the uplink. For example, if this factor is set to 0.8, only 80% of the actual path loss will be considered when
estimating the received power. Therefore, the received power from any mobile on the uplink will be estimated to be
higher than it would actually be (using 100% of the path loss), which will be interpreted by the mobile as a need to
reduce its transmission power. This factor is represented by in 3GPP specifications. This factor represents the influence of the serving cell on the fractional power of any mobile.
Max PUSCH C/(I+N) (dB): This value is used for power control on the uplink. The difference between the Max PUSCH
C/(I+N) and the uplink noise rise of the cell corresponds to the nominal PUSCH power for the cell. The nominal PUSCH
power is a cell-specific parameter from which a limit on the uplink transmission powers of mobiles in the cell can be
extracted. This factor is represented by P O_PUSCH in 3GPP specifications. Max PUSCH C/(I+N) is updated during uplink
noise rise control in Monte Carlo simulations based on the maximum noise rise constraints of the neighbouring cells.
Almost Blank Subframe (ABS) Pattern: The transmission pattern of normal and almost blank subframes. Almost blank
subframes do not carry any traffic. Only reference signals are transmitted over an ABS. The ABS pattern is a bit map,
i.e., a series of 0s and 1s where each bit corresponds to one subframe. In an ABS pattern, each 0 signifies a normal
subframe and 1 implies an almost blank subframe. For example, the ABS pattern "0100001000" means that subframes
1 and 6 are almost blank subframes whereas all the other subframes are normal subframes carrying traffic.
ABS patterns are used in conjunction with cell range expansion for eICIC (enhanced inter-cell interference coordination, also known as time-domain ICIC) in an effort to minimise cell-edge interference between macro and small cells
in heterogeneous LTE networks (HetNets).
851
The ABS pattern specified here is applicable to downlink as well as uplink, and does
not depend on the ICIC mode specified in the cells frame configuration. The ICIC
mode defined in the frame configurations is exclusively used for frequency domain
ICIC.
The standard lengths of the ABS pattern bit maps as defined by the 3GPP are as follows:
FDD cells: 40 bits
TDD cells using the frame configuration 0: 70 bits
TDD cells using the frame configuration 1 through 5: 20 bits
TDD cells using the frame configuration 6: 60 bits
Atoll uses the same ABS pattern format as the LTE eNode-B information element
format. Therefore, ABS patterns can be directly imported from the network into
Atoll.
You are not required to enter all the bits in the pattern to match the standard
lengths. You can define non-repeating and repeating ABS patterns using the
asterisk as in the following example (for FDD cells):
Interference coordination support: The frequency-domain inter-cell interference coordination (ICIC) technique supported by the cell. You can select Static DL or Static UL. You can select from various ICIC modes available in the cells
frame configurations. This frequency-domain inter-cell interference coordination method can be used in addition to
the eICIC ABS patterns.
Frame configuration: The frame configuration used by the cell in downlink and uplink. Among other frame structure
parameters, this configuration also defines ICIC settings for a cell supporting Static DL or Static UL inter-cell interference coordination. For more information, see "Defining Frame Configurations" on page 963.
Cell Edge Margin (dB): The maximum difference between the path loss of the second best server and the path loss of
the best server to be considered at cell edge. Certain interference management actions are carried out on cell-edge
regions, such as ICIC, eICIC, and CoMP.
852
You can change the cell-edge determination method by using the CellEdgeMethod
option in the [LTE] section of the Atoll.ini file. This option allows you to determine
the cell-edge areas based on the difference between the highest and second
highest RSRP values rather than the lowest and the second lowest path loss values.
For more information, see the Administrator Manual and the Technical Reference
Guide.
If you set the cell edge calculation method to use RSRP rather than path losses,
Atoll calculates the cell-edge regions for CoMP by comparing the cell-edge margin
with the difference between the best server RSRP and the second best server RSRP
belonging to the same CoMP set.
Max traffic load (DL) (%): The downlink traffic load not to be exceeded. This limit can be taken into account during
Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have a downlink
traffic load greater than this maximum.
Traffic load (DL) (%): The downlink traffic load percentage. This can be user-defined or an output of Monte Carlo simulations.
Cell-edge traffic ratio (DL) (%): You can set the percentage of the total downlink traffic load that corresponds to the
resources allocated to cell-edge users. For example, if the downlink traffic load is 80%, and you set the cell-edge traffic
ratio to 50%, it means that 40% of the downlink traffic load corresponds to cell-edge users and 40% to the cell-centre
users. This can be user-defined or an output of Monte Carlo simulations.
Max traffic load (UL) (%): The uplink traffic load not to be exceeded. This limit can be taken into account during Monte
Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have an uplink traffic
load greater than this maximum.
Traffic load (UL) (%): The uplink traffic load percentage. This can be user-defined or an output of Monte Carlo simulations.
AT332_UMR_E0
UL noise rise (dB): The uplink noise rise in dB. This can be user-defined or an output of Monte Carlo simulations. This
is the global value of uplink noise rise including the inter-technology uplink noise rise.
ICIC UL noise rise (dB): The uplink noise rise of the cell resources covering cell-edge users. This noise rise is only used
when the ICIC support for the cell includes Static UL. This can be user-defined or an output of Monte Carlo simulations.
Max UL noise rise (dB): The upper limit on both uplink noise rise values, i.e., the UL noise rise and the ICIC UL noise
rise. It is used for uplink noise rise control during Monte Carlo simulations. This parameter represents the maximum
interference that a cell can tolerate on the uplink.
Angular distributions of interference (AAS): The Monte Carlo simulation results generated for transmitters using a
smart antenna. These results are the angular distributions of the downlink traffic power spectral density.
AAS usage (DL) (%): The total downlink traffic load that corresponds to the traffic loads of the users supported by the
smart antenna. For example, if the downlink traffic load is 80%, and you set the AAS usage to 50%, it means that 40%
downlink traffic load is supported by the smart antenna equipment while the other 40% is supported by the main
antenna. AAS usage is calculated during Monte Carlo simulations, and cannot be modified manually because the AAS
usage values correspond to the angular distributions of interference.
Additional UL noise rise: This noise rise represents the interference created by mobiles and base stations of an
external network on this cell on the uplink. This noise rise will be taken into account in all uplink interference-based
calculations involving this cell in Monte Carlo simulations. It is not used in predictions where Atoll calculates the uplink
total interference from the uplink noise rise which includes inter-technology uplink interference. For more information on inter-technology interference, see "Modelling Inter-technology Interference" on page 975.
Additional 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 interferencebased calculations involving this cell. For more information on inter-technology interference, see "Modelling Intertechnology Interference" on page 975.
Max number of intra-technology neighbours: The maximum number of LTE neighbours that the cell can have.
Max number of inter-technology neighbours: The maximum number of other technology neighbours that the cell can
have.
Neighbours: You can access a dialog box in which you can set both intra-technology and inter-technology neighbours
by clicking the Browse button. For information on defining neighbours, see "Configuring Network Parameters Using
the AFP" on page 905.
The Browse button may not be visible in the Neighbours box if this is a new cell. You can
make the Browse button appear by clicking Apply.
)and the coordinates of the mouse cursor are displayed in the status bar.
2. Click the map at the location where you want to place the new site. A new site is created with default settings at the
corresponding location.
853
Alternatively, you can create a new site by entering its coordinates and properties as
described in "Site Properties" on page 845, by right-clicking the Sites folder and selecting
New from the context menu.
To create a transmitter, right-click the LTE Transmitters and select New from the context menu.
To modify an existing transmitter, expand the LTE Transmitters folder, right-click the transmitter that you want to
modify, and select Properties from the context menu.
854
TMA: Select a tower-mounted amplifier (TMA) from the list. Click the Browse button to access the properties of
the TMA. For information on creating a TMA, see "Defining TMA Equipment" on page 161.
Feeder: Select a feeder cable from the list. Click the Browse button to access the properties of the feeder. For
information on creating a feeder cable, see "Defining Feeder Cables" on page 161.
Transmitter: Select a transmitter equipment from the Transmitter list. Click the Browse button to access the properties of the transmitter equipment. For information on creating a transmitter equipment, see "Defining Transmitter Equipment" on page 162.
AT332_UMR_E0
4. Click OK.
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 base station more accurately, you can zoom in on the map before you click
the New Transmitter or Station button ( ). For information on using the zooming tools,
see "Changing the Map Scale" on page 60.
If you let the pointer rest over the base station you have placed, Atoll displays its tip text
with its exact coordinates, allowing you to verify that the location is correct.
3. 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.
855
11.2.2.8.1
The Name of the station template, the number of Sectors, each with a transmitter, the Hexagon radius, i.e., the theoretical radius of the hexagonal area covered by each sector, and the Transmitter type, i.e., whether the transmitter
belongs to your network or to an external network.
Under Antennas, you can modify the following: 1st sector azimuth, from which the azimuth of the other sectors are
offset to offer complete coverage of the area, 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 the building),
and the Mechanical downtilt for the antennas.
Electrical Azimuth, Electrical Downtilt, and Additional electrical downtilt display additional antenna parameters.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
Under Main antenna, you can select the main antenna Model, under Smart antenna, you can select the smart
antenna Equipment used by the transmitter, and under Number of antenna ports, you can enter the number of
antennas used for Transmission and for Reception for MIMO.
Under Path loss matrices, you can modify the following: the Main propagation model, the Main radius, and the Main
resolution, and the Extended propagation model, the Extended radius, and the Extended resolution. For information
on propagation models, see Chapter 4: Radio Calculations and Models.
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.
Transmitter Tab
Use this tab to modify the following settings:
Active: Select this option to specify whether the transmitter is active. Active transmitters are displayed in red in the
LTE Transmitters folder of the Network explorer.
Only active transmitters are taken into consideration during calculations.
You can click the Equipment button to modify the tower-mounted amplifier (TMA), feeder cables, or transmitter
equipment. For information on the Equipment Specifications dialog box, see "Assigning Equipment to a Transmitter"
on page 854.
856
AT332_UMR_E0
The Total losses (transmission and reception) and Noise figure (reception) in the Computed columns is calculated
from the information that was entered in the Equipment Specifications dialog box. The Total losses (transmission and
reception) Noise figure (reception) in the Real columns can be edited. Any value that you enter must be positive.
Any loss related to the noise due to the repeater of a transmitter is included in the calculated losses. Atoll always considers the values in the Real boxes in coverage predictions
even if they are different from the values in the Computed boxes.
Cell Tab
Power and EPRE offsets relative to the reference signals EPRE: You can modify the Max power, RS EPRE, and the EPRE
offsets for the SS, PBCH, PDSCH, and PDCCH in SS offset, PBCH offset, PDCCH offset, and PDSCH offset.
Cell definition per sector: Click this button to open the Cell Definition per Sector, where you can assign channel and
physical cell ID per cell per sector.
Sector: Select the sector for which you want to define cell parameters, including the channel number and physical
cell ID.
Number of cells: Enter the number of celles that the selected sector will have. The number of rows in the grid
below depends on the number of cells that you enter.
For each sector, assign layers, channels, and physical cell ID to each cell.
Frequency band, Reuse distance, Reception equipment, Cell type, Min RSRP, Cell selection threshold, Cell individual
offset, Handover margin, Scheduler, Max number of users, TDD subframe configuration, and the Number of
required PRACH RSIs.
Antenna diversity: Select the Diversity support in downlink and uplink.
Default loads: Enter the default values for DL traffic load, UL traffic load, UL noise rise, and the Max DL traffic load
and Max UL traffic load.
Additional interference: Set the DL noise rise and the UL noise rise. For more information on inter-technology interference, see "Modelling Inter-technology Interference" on page 975.
Neighbours Tab
Max number of neighbours: Set the maximum numbers of Intra-technology and Inter-technology neighbours. For information on defining neighbours, see "Planning Neighbours" on page 904.
Other Properties Tab
This tab only appears if you have defined additional fields in the Sites table, or if you have defined an additional field in the
Station Template Properties dialog box.
11.2.2.8.2
11.2.2.8.3
857
3. Modify the station template parameters as described in "Station Template Properties" on page 856
4. Click OK.
11.2.2.8.4
11.2.2.8.5
11.2.2.8.6
Quickly create a base station with the same settings as an original one in order to study the effect of a new station on
the coverage and capacity of the network, and
Quickly create a homogeneous network with base stations that have the same characteristics.
If you want to duplicate the base station without the intra- and inter-technology neighbours of its transmitters,
select Duplicate > Without Neighbours.
If you want to duplicate the base station along with the lists of intra- and inter-technology neighbours of its transmitters, select Duplicate > With Outward Neighbours.
3. In the map window, place the new base station on the map using the mouse:
858
To create a duplicate base station and site, move the pointer over the map to where you would like to place the
duplicate. The exact coordinates of the pointers current location are visible in the Status bar.
To place the duplicate base station on an existing site, move the pointer over the existing site where you would
like to place the duplicate. When the pointer is over the site, the site is automatically selected. The exact coordinates of the pointers current location are visible in the Status bar.
AT332_UMR_E0
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 60.
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.
4. Click to place the duplicate base station.
A new base station is placed on the map. If the duplicate base station was placed on a new site, 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. If the duplicate base station was placed on an existing site, the transmitters, and cells of the new base station have the same names as the transmitters, and cells of the original base station
with each name preceded by the name of the site on which the duplicate was placed.
All the remote antennas and repeaters of any transmitter on the original site are also duplicated.
Any duplicated remote antennas and repeaters will retain the same donor transmitter as
the original. If you want the duplicated remote antenna or repeater to use a transmitter
on the duplicated base station, you must change the donor transmitter manually.
You can also place a series of duplicate base stations by pressing and holding Ctrl in step 4. and clicking to place each
duplicate station.
For more information on the site, transmitter, and cell properties, see "Definition of an LTE Base Station" on page 845.
) in the Radio Planning toolbar. The Point Analysis window opens and the pointer
changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and the
receiver. You can move the receiver on the map (see "Moving the Receiver on the Map" on page 203).
3. Select the Profile view. The Profile view displays the profile between the transmitter and the receiver with the terrain
and clutter heights.
Transmitter selection list.
Display
area
including:
received signal,
shadowing
margin,
cell
edge coverage
probability,
propagation
model
used,
and transmitter-receiver
distance.
Fresnel ellipsoid
Line of sight
859
The distance between the transmitter and the receiver is displayed at the top of the Profile view. The altitude 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. A green line indicates the line of sight (LOS) with the angle of
the LOS as read from the vertical antenna pattern.
Along the profile, if the signal meets an obstacle, the obstacle causes attenuation with diffraction displayed by a red
vertical line (if the selected propagation model is able to calculate diffraction). The main diffraction edge is the one
that intersects the Fresnel ellipsoid the most. Propagation models that use a 3 knife-edge Deygout diffraction method
may also display two additional diffraction edges. The total attenuation is displayed above the main diffraction edge.
The results of the analysis are displayed at the top of the Profile view:
The received signal strength from the selected transmitter for the cell with the highest reference signal power
The propagation model used
The shadowing margin and the indoor loss (if selected)
The distance between the transmitter and the receiver.
4. If needed, select an other transmitter from the list. You can click the Properties button (
properties.
5. Click the Options button (
) to display the Calculation Options dialog box and change the following:
Change the X and Y coordinates to change the current position of the receiver.
Select the Shadowing taken into account check box and enter a Cell edge coverage probability. For more information, see "Taking Shadowing into Account in Point Analyses" on page 204.
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. Indoor losses are defined per frequency per
clutter class. For more information, see "Taking Indoor Losses into Account" on page 203.
6. In the Profile view toolbar, you can use the following tools:
) to view the geographic profile between the transmitter and the receiver.
) again to view the radio signal path between the transmitter and the
Click the Detailed Report button ( ) to display a text document with details on the displayed profile analysis.
The detailed report is only available for the Standard Propagation Model.
Click the Copy button (
) to copy the content of the view and paste it as a graphic into a graphic editing or wordprocessing programme.
860
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.
AT332_UMR_E0
The table you copy 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 83.
Importing data: If you have base station 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 and Spreadsheets" on page 86. For information on importing table data, see "Importing Tables from Text Files" on page 88.
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 in the label will make it harder to distinguish the information you are looking for. For
information on defining the label, see "Associating a Label to an Object" on page 53.
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 "Associating a Tip Text to an Object" on page 54.
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 transmitters. 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 "Setting the Display Type" on page 52.
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 (
and
).
For information on defining the transmitter symbol, see "Setting the Display Type" on page 52.
Defining the frequency bands in the document (see "Defining Frequency Bands" on page 958).
861
Selecting and calibrating a propagation model for each frequency band (see "Assigning Propagation Parameters" on
page 187).
Assigning a frequency band to each cell and a relevant propagation model to each transmitter (see "Creating or Modifying a Cell" on page 855 and "Creating or Modifying a Transmitter" on page 854).
Defining the frequency bands with which terminals are compatible (see "Modelling Terminals" on page 249).
Groups of cells that perform carrier aggregation with each other, and
Groups of cells that perform coordinated multipoint transmission and reception (CoMP) with each other.
In multi-user environments, cell groups can be stored in the database. When you open a document from a database, Atoll
loads all the cell groups by default. If you want Atoll to only load cell groups relevant to the cells being loaded, you must set
the option FilterUsedGroups option in the [LTE] section of the Atoll.ini file. In a large radio-planning project, this may allow
you to more effectively manage cell groups by reducing the unnecessary data you retrieve from the database.
The items in the LTE Transmitters folder can be grouped by cell groups. For more
information, see "Grouping, Sorting, and Filtering Data" on page 94.
The LTE transmitter display settings can be based on cell groups. For more information, see "Setting the Display Properties of Objects" on page 51.
Intra-eNode-B carrier aggregation (default) implies that only cells that belong to the same site can perform carrier
aggregation with each other.
Multi-eNode-B carrier aggregation means that cells belonging to any site can perform carrier aggregation with each
other.
Group-based carrier aggregation means that cells belonging to the same group can perform carrier aggregation with
each other.
You can switch between these carrier aggregation modes using the following Atoll.ini option:
[LTE]
CAWithinENB = 0; For multi-eNode-B carrier aggregation
CAWithinENB = 1; For intra-eNode-B carrier aggregation (default)
CAWithinENB = 2; For group-based carrier aggregation
If you want to work with group-based carrier aggregation, you must define groups of cells that can perform carrier aggregation
with each other.
To create carrier aggregation groups:
1. In the Network explorer, right-click the LTE Transmitters folder and select Cells > CA Groups > Open Table from the
context menu. The CA Groups table appears.
2. In the CA Groups table, enter one carrier aggregation group per row.
This table lists the carrier aggregation groups that exist in your document and shows the number of cells that belong
to each group.
If you delete a carrier aggregation group in this table, it will also delete all the corresponding records in the Cell-to-Group Mappings table.
862
AT332_UMR_E0
Coordinated multipoint transmission and reception is performed between co-channel cells within the cell-edge regions
defined by the Cell Edge Margin. If you set the cell edge calculation method to use RSRP rather than path losses, Atoll calculates the cell-edge regions for CoMP by comparing the cell-edge margin with the difference between the best server RSRP and
the second best server RSRP belonging to the same CoMP set. For more information, see the Administrator Manual. For
CoMP, the definition of co-channel cells is the same as that of intra-frequency cells according to the 3GPP: cells using
frequency channels with the same centre frequency irrespective of their channel widths.
You can define groups of cells that can coordinate with each other, i.e., CoMP sets, as well as the CoMP mode applicable to
each CoMP set in the CoMP sets definition tables.
To create CoMP sets:
1. In the Network explorer, right-click the LTE Transmitters folder and select Cells > CoMP Sets > Open Table from the
context menu. The CoMP Sets table appears.
2. In the CoMP Sets table, enter one CoMP set per row.
This table lists the CoMP sets that exist in your document and shows the number of cells that belong to each CoMP
set. For each CoMP set, you can define:
863
Only cells of type LTE-A PCell can perform coordinated multipoint transmission and
reception (CoMP).
Even if you delete the cell-to-CoMP set mapping records in this table, the associated CoMP set is not deleted in the CoMP Sets table. To delete a CoMP set permanently, you must also delete it in the CoMP Sets table.
864
AT332_UMR_E0
You can create a new group by entering a name in the list instead of selecting the name
from the list. The cells of the selected transmitter will be added to the new group.
4. Click OK. The cells of the selected transmitter are added to the group.
To add cells to a CoMP set:
1. In the map window, right-click the transmitter whose cells you want to add to a CoMP set. The context menu appears.
2. Select Cells > Add Cells to a CoMP Set from the context menu. A dialog box appears.
3. Select the name of the CoMP set from the dialog box.
4. Click OK. The cells of the selected transmitter are added to the CoMP set.
4. Click OK. The cells contained in the zone are added to the selected group.
To add the cells contained in a zone to a CoMP set:
1. In the Geo explorer, right-click the filtering, computation, focus, printing, or geographic export zone, or a hot spot. The
context menu appears.
2. Select Add > Add Cells to a CoMP Set from the context menu. A dialog box appears.
3. Select the name of the CoMP Set from the dialog box.
4. Click OK. The cells contained in the zone are added to the selected CoMP set.
865
Repeaters are defined in the Repeaters table. Each repeater is assigned repeater equipment with specific noise, gain, and
power characteristics, which are specified in the Repeater Equipment table.
This section covers the following topics:
Name: Specify the Name of the repeater. By default, repeaters are named "SiteX_Y_RepZ" where "X" is the donor site
number, "Y" the donor transmitter number, and "Z" a number assigned to the repeater when it was created.
Donor: Select the donor of the repeater, which can be a transmitter, a remote antenna, or another repeater. Click
Browse to access the Properties of the donor.
Site: Specify the site on which the repeater is located. Click Browse to access the Properties of the site.
Shared antenna: Specify the identifier (coverage side) of the transmitters, repeaters, and remote antennas that are
located at the same site or on sites with the same position and that share an antenna. The identifier must be the same
for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all
other transmitters, repeaters, and remote antennas defined as having a shared antenna.
Antenna position: If the repeater is not located exactly on the site, you can specify its location.
866
Relative to site: Select this option to specify the position of the repeater relative to the site itself and then enter
the Dx and Dy offsets.
Coordinates: Select this option to specify the position of the repeater by its X and Y absolute coordinates.
Equipment: Select an equipment from the list. Click Browse to access the Properties of the equipment.
Amplifier Gain: Specify a gain for the amplifier. The amplifier gain is used in the link budget to evaluate the repeater
total gain.
AT332_UMR_E0
Donor Tab
Donor-repeater link, specify the type of link between the donor and the repeater:
Air: Select this option to specify an off-air repeater. Select a Propagation model and either enter the Propagation
losses between the donor and the repeater or click Calculate to determine the actual propagation losses based
on the propagation model. 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.
Microwave link: Select this option to specify a microwave link. Specify the total Link losses for the link between
the donor transmitter and the repeater.
Optical fibre link: Select this option to specify an optical fibre link. Specify the total Fibre losses for the link
between the donor transmitter and the repeater
If you want to create a remote antenna, you must select Optical fibre link.
If you select Air under Donor-repeater link, enter the following information under Antenna:
Model: Select the antenna model from the list. Click Browse to open the antenna properties.
Click Select to open the Antenna Selection Assistant. This assistant lists all the antennas that match the currently selected physical antenna and whose minimum and maximum operating frequencies include the operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
Height/ground: Specify the height of the antenna above the ground. This is added to the altitude of the site
as given by the DTM. If the repeater is situated on a building, the height entered must include the height of
the building.
Mechanical Azimuth and Mechanical Downtilt: Specify additional antenna parameters.
You can click the Calculate button to update the mechanical azimuth and mechanical
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 select Air under Donor-repeater link, enter the following information under Feeders:
Type: Select the type of feeder from the list. Click Browse to open the feeder properties.
Length: Enter the Length of the repeater feeder cable for Transmission and Reception.
Coverage Side
Active: specify whether the repeater is active. Only active repeaters (displayed in red in the Transmitters folder in the
Network explorer) are calculated.
Total gain: Specify the total gain in downlink and uplink) or click Calculate to determine the actual gain in both directions. If you have modified any settings in the General, Donor Side, or Coverage Side tabs, click Apply before clicking
the Calculate button.
In downlink, the total gain is applied to RS, SS, PBCH, PDCCH, and PDSCH powers and EPREs.
In uplink, the total gain is applied to the PUCCH and PUSCH powers.
The total gain takes into account losses between the donor transmitter and the repeater, donor characteristics (donor
antenna gain, reception feeder losses), amplifier gain, and coverage characteristics (coverage antenna gain, transmission feeder losses).
Height/ground: Specify the height of the antenna above the ground. This is added to the altitude of the site as
provided by the DTM. If the repeater is located on a building, the height entered must include the height of
building.
Model: Select antenna model from the list. Click Browse to open the antenna properties.
Click Select to open the Antenna Selection Assistant. This assistant lists all the antennas that match the currently
selected physical antenna and whose minimum and maximum operating frequencies include the operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on page 159
867
Mechanical Azimuth, Mechanical Downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt: Specify the additional antenna parameters.
Secondary antennas: Select one or more secondary antennas in the Antenna column and enter their Azimuth,
Mechanical downtilt, Additional electrical downtilt, and % Power.
The Additional electrical downtilt can be made available through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
Propagation Tab
Repeaters are taken into account during calculations. Therefore, you must specify their 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 "Assigning Propagation Parameters" on page 187.
):
868
AT332_UMR_E0
f.
If necessary, enter a Max uplink power, an Internal delay and Comments. These fields are for information only
and are not used in calculations.
When the donor is a transmitter, you can see to which base station the repeater is
connected by clicking it; Atoll displays a link to the donor transmitter. You can hide
the link by clicking it again.
When the donor is a repeater or a remote antenna, Atoll displays a spider-type link
showing the entire chain down to the donor transmitter. The same spider-type link
is displayed when you click any of the items belonging to the chain is clicked (i.e.,
donor transmitter, any repeater, or any remote antenna).
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.
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 57) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using
the Mouse" on page 58).
869
Name: You can change the Name of the remote antenna. By default, remote antennas are named "SiteX_Y_RepZ"
where "X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned to the remote
antenna when it was created.
Donor: Specify whether the donor of the remote antenna is a transmitter, another remote antenna, or a repeater.
Click Browse to access the Properties of the donor.
Site: Specify the site on which the remote antenna is located. Click Browse to access the Properties of the site.
Shared antenna: Specify the identifier (coverage side) of the transmitters, repeaters, and remote antennas that are
located at the same site or on sites with the same position and that share an antenna. The identifier must be the same
for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all
other transmitters, repeaters, and remote antennas defined as having a shared antenna.
Antenna position: If the remote antenna is not located exactly on the site, you can specify its location.
Relative to site: Select this option to specify the position of the remote antenna relative to the site itself and then
enter the Dx and Dy offsets.
Coordinates: Select this option to specify the position of the remote antenna by its X and Y absolute coordinates.
Remote antennas do not have assigned equipment.
Donor Tab
870
Donor-repeater link: specify Optical fibre link. Specify the total Fibre losses for the link between the donor transmitter and the repeater
AT332_UMR_E0
For remote antennas, you must select Optical fibre link. Do not select Air or Microwave
link.
Active: Specify whether the remote antenna is active. Only active remote antennas (displayed in red in the Transmitters folder in the Network explorer) are calculated.
Total gain: Specify the total gain (in downlink and uplink). You can click Calculate to determine the actual gain in both
directions. If you have modified any settings in the General, Donor Side, or Coverage Side tabs, click Apply before
clicking the Calculate button.
In downlink, the total gain is applied to RS, SS, PBCH, PDCCH, and PDSCH powers and EPREs.
In uplink, the total gain is applied to the PUCCH and PUSCH powers.
The total gain takes into account losses between the donor transmitter and the remote antenna, donor characteristics
(donor antenna gain, reception feeder losses), amplifier gain, and coverage characteristics (coverage antenna gain,
transmission feeder losses).
Height/ground: Specify the height of the antenna above the ground. This is added to the altitude of the site as
provided by the DTM. If the remote antenna is located on a building, the height entered must include the height
of building.
Model: Select an antenna model from the list. Click Browse to access the antenna properties.
Click Select to open the Antenna Selection Assistant. This assistant lists all the antennas that match the currently
selected physical antenna and whose minimum and maximum operating frequencies include the operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on page 159
Mechanical Azimuth, Mechanical Downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt: Specify the corresponding additional antenna parameters.
Secondary antennas: Select one or more secondary antennas in the Antenna column and enter their Azimuth,
Mechanical downtilt, Additional electrical downtilt, and % Power.
The Additional electrical downtilt can be made available through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
Propagation Tab
Remote antennas are taken into account during calculations in the same way as transmitters. Therefore, you must
specify their propagation parameters. On the Propagation tab, you can modify 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 "Assigning Propagation Parameters" on page 187.
871
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 create several repeaters. The table you copy data from must have the same
column layout as the table you are pasting data into.
You can also use this method to create a large number of remote antennas in a single operation.
For information on copying and pasting data, see "Copying and Pasting in Tables" on
page 83.
When the donor is a transmitter, you can see to which base station the repeater is
connected by clicking it; Atoll displays a link to the donor transmitter. You can hide
the link by clicking it again.
When the donor is a repeater or a remote antenna, Atoll displays a spider-type link
showing the entire chain down to the donor transmitter. The same spider-type link
is displayed when you click any of the items belonging to the chain is clicked (i.e.,
donor transmitter, any repeater, or any remote antenna).
872
You can update the UL and DL total gains of all remote antennas by selecting Remote Antennas > Calculate Gains from
the Transmitters context menu.
AT332_UMR_E0
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 57) or its position relative to the site (see "Changing the Antenna Position Relative to the Site
Using the Mouse" on page 58).
Model: The type of antenna is visible in the Model list. You can click the Browse button to access the properties of the antenna. Click the Select button to open the Antenna Selection Assistant. For more information,
see "Assigning Antennas to Transmitters" on page 159
Mechanical Azimuth and Mechanical Downtilt show the orientation of the antenna towards the donor cell.
Electrical Azimuth and Electrical Downtilt display additional antenna information.
You can click the Calculate Angles button to update the mechanical azimuth and mechanical downtilt values.
Select a Type of feeder from the list. You can click the Browse button to access the properties of the feeder.
Enter the Length of the feeder cable at Transmission and at Reception.
873
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 83.
Display Resolution
City Centre
5m
City
20 m
County
50 m
State
100 m
Country
The resolution specified here is only for display purposes. The calculated resolution is independently specified in the
propagation settings. For more information, see "Assigning Propagation Parameters" on page 187.
874
AT332_UMR_E0
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the <GUID> and </GUID> tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
Receiver height: This displays the height of the receiver defined in the Calculation Parameters tab of the Network
Settings Properties dialog box
Comments: Specify an optional description of comment for the prediction.
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 99. The Group By and Sort buttons are not available when making a "global"
coverage prediction (for example, a signal level coverage prediction).
At the top of the Conditions tab, you can specify the range to be considered for the current prediction.
Server: Select either All, Best Signal Level or Second Best Signal Level:
Shadowing taken into account: Select this option to consider shadowing in the prediction. For more information, see
"Modelling Shadowing in LTE" on page 974. If you select this option, you can change the Cell edge coverage probability.
Indoor coverage: Select this option to consider indoor losses. Indoor losses are defined per frequency per clutter class.
Channel: Select All or select one or several channels to carry out the prediction for the best channel among several
selected channels. For any transmitter, the best channel is the one whose cell has the highest maximum power, reference signal power, or reference signal EPRE depending on the related Atoll.ini options. For more information, see
the Administrator Manual.
875
parameters you want to study, you can create a new coverage prediction more quickly than by creating a 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 104.
The following standard coverage predictions are explained in this section:
"Studying Signal Level Coverage for a Single Base Station" on page 876
"Making a Coverage Prediction by Signal Level" on page 877
"Making a Coverage Prediction by Transmitter" on page 877
"Making a Coverage Prediction on Overlapping Zones" on page 878.
Coverage predictions specific to LTE are covered in "LTE Coverage Predictions" on page 879.
11.2.11.2.1
2. Specify the propagation parameters as explained in "Assigning Propagation Parameters" on page 187.
3. In the LTE Transmitters folder, right-click the group of transmitters that you want to study and select Calculations >
Create a New Prediction from the context menu. The Prediction Types dialog box appears.
The Prediction Types dialog box lists the coverage prediction types available. They are divided into Standard Predictions, supplied with Atoll, and Customised Prediction. Unless you have already created some customised predictions,
the Customised Prediction list will be empty.
4. Select Coverage by Signal Level (DL) and click OK. The Coverage by Signal Level (DL) Properties dialog box appears.
5. Configure the parameters in the Properties dialog box as described in "LTE Prediction Properties" on page 874.
The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for
each pixel.
6. 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.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
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 in the Network explorer. Atoll automatically locks the results of a
coverage prediction as soon as it is calculated, as indicated by the icon ( ) beside the coverage prediction in the Predictions
folder. When you click the Calculate button ( ), Atoll only calculates unlocked coverage predictions ( ).
876
AT332_UMR_E0
11.2.11.2.2
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.4).
11.2.11.2.3
877
The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for
each pixel.
4. Click the Display tab.
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 "Setting the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.5).
11.2.11.2.4
878
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately.
AT332_UMR_E0
OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the
Calculate button (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.6).
11.2.11.3.1
"Studying LTE-Specific Signal Levels, Best Servers, and Cell Edge Areas" on page 880.
"Studying Interference and C/(I+N) Levels" on page 882.
"Studying Downlink and Uplink Service Areas" on page 884.
"Studying the Effective Service Area" on page 886.
"Making a Coverage Prediction by Throughput" on page 888.
"Making a Cumulated Throughput Coverage Prediction Using Simulation Results" on page 891.
"Making a Coverage Prediction by Quality Indicator" on page 891.
879
3. Select Cells > Open Table from the context menu. The Cells table appears.
4. Enter a value in the following columns:
Although, you can also set a value for the Traffic load (UL) (%) column as an indication of cells uplink loads, this parameter is not used in the coverage prediction calculations. The measure of interference in the uplink is given by the uplink
noise rise values. For a definition of the values, see "Cell Properties" on page 848.
To enter the same values in one column for all cells in the table by copying the contents of
one cell into other cells, you can use the Fill Down and Fill Up commands. For more information on working with tables in Atoll, see "Data Tables" on page 75.
11.2.11.3.2
Studying LTE-Specific Signal Levels, Best Servers, and Cell Edge Areas
Downlink and uplink effective signal analysis coverage predictions predict the effective signal levels of different types of LTE
signals, such as reference signals, SS, PBCH, PDCCH, PDSCH, and PUSCH, in the part of the network being studied. These predictions can also be used to predict the best servers and cell-edge areas for these servers. This section explains the effective
signal analysis coverage predictions.
Atoll determines the serving cell for each pixel using the standard cell selection mechanism (see the Technical Reference
Guide). Then, depending on the prediction definition, it calculates the required effective signal or parameter. Pixels are
coloured if the display threshold condition is fulfilled.
To make an effective signal analysis coverage prediction:
1. In the Network explorer, right-click the Predictions folder and select New Prediction from the context menu. The
Prediction Types dialog box appears.
2. Select Effective Signal Analysis (DL) or Effective Signal Analysis (UL) and click OK. The coverage predictions Properties dialog box appears.
3. Configure the parameters in the Properties dialog box as described in "LTE Prediction Properties" on page 874.
4. Click the Conditions tab.
a. Select "(Cells table)" from Load conditions. In this case, the coverage prediction is not based on load conditions
taken from a simulation. The coverage prediction is calculated using the cell load that is stored 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.
The Effective Signal Analysis (DL) and Effective Signal Analysis (UL) coverage predictions use load conditions to calculate interference for diversity mode selection
if the SU-MIMO criterion, MU-MIMO criterion, or AAS criterion, in the Advanced
Parameters dialog box of the LTE Network Settings, is based on C/(I+N).
The uplink signal level calculation in Effective Signal Analysis (UL) coverage predictions also depends on the load conditions due to uplink power control.
b. Select the network Layers that you want the calculations to take into account. You can also calculate the prediction for all layers.
c. Select the frequency Channels that you want the calculations to take into account. You can also calculate the prediction for all channels.
d. Select the Cell type, LTE/LTE-A PCell or an LTE-A SCell, for which you want to calculate the coverage prediction.
e. Select a Terminal, a Mobility type, and a Service. The Noise figure defined in the terminal types properties dialog
box is used in the coverage prediction to determine the total noise in the downlink, and the Noise figure of the
transmitter is used to determine the total noise in the uplink. For more information on services, terminals, mobility types, and reception equipment, see "Service and User Modelling" on page 241, and "Defining LTE Reception
Equipment" on page 965, respectively.
If the selected terminal supports CoMP, the coverage prediction considers the coordinated multipoint transmission and reception characteristics of the CoMP set definitions of the cells.
880
For coordinated scheduling, interference from coordinated CoMP cells is weighted by the CoMP collision probability.
AT332_UMR_E0
f.
For coherent joint transmission, signals from CoMP servers are constructively combined resulting in an additive as well as probabilistic macro-diversity gain.
For non-coherent joint transmission, the CoMP servers allocate resources to the CoMP user resulting in aggregated throughput.
For dynamic point selection, a macro-diversity gain is calculated and applied to reduce the required shadowing
margin. For more information, see the Technical Reference Guide.
If you want the coverage prediction to consider shadowing, select the Shadowing taken into account check box
and enter a percentage in the Cell edge coverage probability text box. The shadowing margin is based on the C/I
standard deviation.
g. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
5. Click the Display tab.
a. From the Display type list of an Effective Signal Analysis (DL) coverage prediction, select "Value intervals" to display the coverage prediction by RSRP, signal levels, C/N levels, or cell edge margin, or select "Discrete values" to
display the coverage prediction by transmitter, cell-edge areas, CoMP sets, or number of CoMP servers.
b. From the Display type list of an Effective Signal Analysis (UL) coverage prediction, select "Value intervals" to display the coverage prediction by PUSCH & PUCCH signal level or C/N level, or select "Discrete values" to display the
coverage prediction by CoMP sets or number of CoMP servers.
For information on adjusting the display, see "Setting the Display Properties of Objects" on page 51.
6. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.7 and
Figure 11.8).
881
11.2.11.3.3
882
AT332_UMR_E0
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the <GUID> and </GUID> tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
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 99.
4. Click the Conditions tab. On the Conditions tab:
a. 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 cell loads stored 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.
b. Select the network Layers that you want the calculations to take into account. You can also calculate the prediction for all layers.
c. Select the frequency Channels that you want the calculations to take into account. You can also calculate the prediction for all channels.
d. Select the Cell type, LTE/LTE-A PCell or an LTE-A SCell, for which you want to calculate the coverage prediction.
e. Select a Terminal, a Mobility type, and a Service. The Noise figure defined in the terminal types properties dialog
box is used in the coverage prediction to determine the total noise in the downlink, and the Noise figure of the
transmitter is used to determine the total noise in the uplink. For more information on services, terminals, mobility types, and reception equipment, see "Service and User Modelling" on page 241, and "Defining LTE Reception
Equipment" on page 965, respectively.
If the selected terminal supports CoMP, the coverage prediction considers the coordinated multipoint transmission and reception characteristics of the CoMP set definitions of the cells.
f.
For coordinated scheduling, interference from coordinated CoMP cells is weighted by the CoMP collision probability.
For coherent joint transmission, signals from CoMP servers are constructively combined resulting in an additive as well as probabilistic macro-diversity gain.
For non-coherent joint transmission, the CoMP servers allocate resources to the CoMP user resulting in aggregated throughput.
For dynamic point selection, a macro-diversity gain is calculated and applied to reduce the required shadowing
margin. For more information, see the Technical Reference Guide.
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. The shadowing margin is based
on the C/I standard deviation.
g. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
5. Click the Display tab.
6. From the Display type list, select "Value intervals" to display the coverage prediction by RSRQ, RSSI, C/(I+N) levels, or
total noise (I+N) levels.
For information on adjusting the display, see "Setting the Display Properties of Objects" on page 51.
You can also display the uplink C/(I+N) for all frequency blocks, i.e., without uplink bandwidth reduction, by setting
the Uplink bandwidth allocation target to Full bandwidth for the scheduler being used and then selecting the display
option PUSCH & PUCCH C/(I+N) Level (UL). For more information on schedulers, see "Defining LTE Schedulers" on
page 968.
7. 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 (
883
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.9 and
Figure 11.10).
11.2.11.3.4
884
AT332_UMR_E0
3. Click the General tab. On the General tab, you can change the assigned Name of the coverage prediction, the Resolution, and you can add a Comment. The Receiver height corresponds to the height of the receiver defined in the Calculation Parameters tab of the LTE Network Settings Properties dialog box.
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the <GUID> and </GUID> tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
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 99.
4. Click the Conditions tab. On the Conditions tab:
a. 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 cell loads stored 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.
b. Select the network Layers that you want the calculations to take into account. You can also calculate the prediction for all layers.
c. Select the frequency Channels that you want the calculations to take into account. You can also calculate the prediction for all channels.
d. Select the Cell type, LTE/LTE-A PCell or an LTE-A SCell, for which you want to calculate the coverage prediction.
e. Select a Terminal, a Mobility type, and a Service. The Noise figure defined in the terminal types properties dialog
box is used in the coverage prediction to determine the total noise in the downlink, and the Noise figure of the
transmitter is used to determine the total noise in the uplink. As well, the bearer selection for each pixel according
to the C(I+N) level is performed using the bearer selection thresholds defined in the reception equipment. This
reception equipment is the one defined in the selected terminal for the downlink coverage predictions, and the
one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used
to index the bearer selection threshold graph to use.
You can make Atoll use only the bearers for which selection thresholds are defined in both
the terminals and the cells reception equipment by adding an option in the Atoll.ini file.
For more information, see the Administrator Manual.
For more information on services, terminals, mobility types, and reception equipment, see "Service and User
Modelling" on page 241, and "Defining LTE Reception Equipment" on page 965, respectively.
If the selected terminal supports CoMP, the coverage prediction considers the coordinated multipoint transmission and reception characteristics of the CoMP set definitions of the cells.
f.
For coordinated scheduling, interference from coordinated CoMP cells is weighted by the CoMP collision probability.
For coherent joint transmission, signals from CoMP servers are constructively combined resulting in an additive as well as probabilistic macro-diversity gain.
For non-coherent joint transmission, the CoMP servers allocate resources to the CoMP user resulting in aggregated throughput.
For dynamic point selection, a macro-diversity gain is calculated and applied to reduce the required shadowing
margin. For more information, see the Technical Reference Guide.
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. The shadowing margin is based
on the C/I standard deviation.
g. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
5. Click the Display tab.
885
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.11 and
Figure 11.12).
11.2.11.3.5
886
AT332_UMR_E0
depends upon the bearer selection thresholds of the highest and lowest bearers defined in the properties of the service
selected for the prediction.
To make an effective service area coverage prediction:
1. In the Network explorer, right-click the Predictions folder and select New Prediction from the context menu. The
Prediction Types dialog box appears.
2. Select Effective Service Area Analysis (DL+UL) and click OK. The coverage predictions Properties dialog box appears.
3. Click the General tab. On the General tab, you can change the assigned Name of the coverage prediction, the Resolution, and you can add a Comment. The Receiver height corresponds to the height of the receiver defined in the Calculation Parameters tab of the LTE Network Settings Properties dialog box.
A read-only Unique ID is generated when you create a new coverage prediction. This ID can
later be found between the <GUID> and </GUID> tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
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 99.
4. Click the Conditions tab. On the Conditions tab:
a. 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 cell loads stored 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.
b. Select the network Layers that you want the calculations to take into account. You can also calculate the prediction for all layers.
c. Select the frequency Channels that you want the calculations to take into account. You can also calculate the prediction for all channels.
d. Select the Cell type, LTE/LTE-A PCell or an LTE-A SCell, for which you want to calculate the coverage prediction.
e. Select a Terminal, a Mobility type, and a Service. The Noise figure defined in the terminal types properties dialog
box is used in the coverage prediction to determine the total noise in the downlink, and the Noise figure of the
transmitter is used to determine the total noise in the uplink. As well, the bearer selection for each pixel according
to the C(I+N) level is performed using the bearer selection thresholds defined in the reception equipment. This
reception equipment is the one defined in the selected terminal for the downlink coverage predictions, and the
one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used
to index the bearer selection threshold graph to use.
You can make Atoll use only the bearers for which selection thresholds are defined in both
the terminals and the cells reception equipment by adding an option in the Atoll.ini file.
For more information, see the Administrator Manual.
For more information on services, terminals, mobility types, and reception equipment, see "Service and User
Modelling" on page 241, and "Defining LTE Reception Equipment" on page 965, respectively.
If the selected terminal supports CoMP, the coverage prediction considers the coordinated multipoint transmission and reception characteristics of the CoMP set definitions of the cells.
For coordinated scheduling, interference from coordinated CoMP cells is weighted by the CoMP collision probability.
For coherent joint transmission, signals from CoMP servers are constructively combined resulting in an additive as well as probabilistic macro-diversity gain.
For non-coherent joint transmission, the CoMP servers allocate resources to the CoMP user resulting in aggregated throughput.
For dynamic point selection, a macro-diversity gain is calculated and applied to reduce the required shadowing
margin. For more information, see the Technical Reference Guide.
887
f. 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. The shadowing margin is based
on the C/I standard deviation.
g. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
5. Click the Display tab.
For an effective service area prediction, the Display type "Unique" is selected by default. The coverage prediction will
display where a service is available in both downlink and uplink. For information on defining display properties, see
"Setting the Display Properties of Objects" on page 51.
When creating a coverage prediction by unique values, you can not export the values per
pixel.
6. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
11.2.11.3.6
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
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 99.
6. Click the Conditions tab. On the Conditions tab:
a. 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 cell loads stored 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.
888
AT332_UMR_E0
b. Select the network Layers that you want the calculations to take into account. You can also calculate the prediction for all layers.
c. Select the frequency Channels that you want the calculations to take into account. You can also calculate the prediction for all channels.
d. Select the Cell type, LTE/LTE-A PCell or an LTE-A SCell, for which you want to calculate the coverage prediction.
For carrier aggregation, i.e., throughput aggregated over different carriers, select more than one Cell type.
e. Select a Terminal, a Mobility type, and a Service. The Noise figure defined in the terminal types properties dialog
box is used in the coverage prediction to determine the total noise in the downlink, and the Noise figure of the
transmitter is used to determine the total noise in the uplink. As well, the bearer selection for each pixel according
to the C(I+N) level is performed using the bearer selection thresholds defined in the reception equipment. This
reception equipment is the one defined in the selected terminal for the downlink coverage predictions, and the
one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used
to index the bearer selection threshold graph to use.
You can make Atoll use only the bearers for which selection thresholds are defined in both
the terminals and the cells reception equipment by adding an option in the Atoll.ini file.
For more information, see the Administrator Manual.
For more information on services, terminals, mobility types, and reception equipment, see "Service and User
Modelling" on page 241, and "Defining LTE Reception Equipment" on page 965, respectively.
If the selected terminal supports CoMP, the coverage prediction considers the coordinated multipoint transmission and reception characteristics of the CoMP set definitions of the cells.
f.
For coordinated scheduling, interference from coordinated CoMP cells is weighted by the CoMP collision probability.
For coherent joint transmission, signals from CoMP servers are constructively combined resulting in an additive as well as probabilistic macro-diversity gain.
For non-coherent joint transmission, the CoMP servers allocate resources to the CoMP user resulting in aggregated throughput.
For dynamic point selection, a macro-diversity gain is calculated and applied to reduce the required shadowing
margin. For more information, see the Technical Reference Guide.
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. The shadowing margin is based
on the C/I standard deviation.
g. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
7. Click the Display tab.
8. From the Display type list, select "Value intervals" to display the coverage prediction by peak RLC, effective RLC, or
application throughputs, or select "Discrete values" to display the effective number of aggregated servers.
For information on adjusting the display, see "Setting the Display Properties of Objects" on page 51.
9. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Atoll determines the total number of symbols in the downlink and the uplink frames from the information in the global transmitter parameters and the frequency bands that are assigned to cells. Then, it determines the bearer at each pixel and multiplies the bearer efficiency by the number of symbols in the frame to determine the peak RLC channel throughputs. The
amount of cell resources, especially at cell-edges, depends on the cell ABS pattern as well as on the number of cells cell-edge
resource blocks defined for frequency-domain (Static DL and Static UL) inter-cell interference coordination in the cells frame
configuration.
The effective RLC throughputs are the peak RLC throughputs reduced by retransmission due to errors, or the Block Error Rate
(BLER). Atoll uses the block error rate graphs of the reception equipment defined in the selected terminal for downlink or the
reception equipment of the cell of the serving transmitter for uplink.
The application throughput is the effective RLC throughput reduced by the overheads of the different layers between the RLC
and the Application layers.
889
The cell capacity display types let you calculate and display the throughputs available at each pixel of the coverage area taking
into account the maximum traffic load limits set for each cell. In other words, the cell capacity is equal to channel throughput
when the maximum traffic load is set to 100 %, and is equal to a throughput limited by the maximum allowed traffic loads
otherwise. Cell capacities are, therefore, channel throughputs scaled down to respect the maximum traffic load limits.
The per-user throughput in downlink is calculated by dividing the downlink cell capacity by the number of downlink users of
the serving cell. In uplink, the per-user throughput is either the allocated bandwidth throughput or the uplink cell capacity
divided by the number of uplink users of the serving cell, whichever it smaller.
The allocated bandwidth throughputs are the throughputs corresponding to the number of frequency blocks allocated to the
terminal at different locations. Users located far from the base stations use less numbers of frequency blocks than users
located near so that they can concentrate their transmission power over a bandwidth narrower than the channel bandwidth
in order to maintain the connection in uplink.
For more information on throughput calculation, see the Technical Reference Guide. For more information on the Global
Parameters, see "Global Network Settings" on page 959.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
890
AT332_UMR_E0
11.2.11.3.7
11.2.11.3.8
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
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 99.
4. Click the Conditions tab. On the Conditions tab:
a. 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 cell loads stored 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.
b. Select the network Layers that you want the calculations to take into account. You can also calculate the prediction for all layers.
c. Select the frequency Channels that you want the calculations to take into account. You can also calculate the prediction for all channels.
d. Select the Cell type, LTE/LTE-A PCell or an LTE-A SCell, for which you want to calculate the coverage prediction.
891
e. Select a Terminal, a Mobility type, and a Service. The Noise figure defined in the terminal types properties dialog
box is used in the coverage prediction to determine the total noise in the downlink, and the Noise figure of the
transmitter is used to determine the total noise in the uplink. As well, the bearer selection for each pixel according
to the C(I+N) level is performed using the bearer selection thresholds defined in the reception equipment, and
the quality indicator graphs from the reception equipment are used to determine the values of the selected quality indicator on each pixel. This reception equipment is the one defined in the selected terminal for the downlink
coverage predictions, and the one defined in the cell properties of the serving transmitter for the uplink coverage
predictions. Mobility is used to index the bearer selection threshold graph to use.
You can make Atoll use only the bearers for which selection thresholds are defined in both
the terminals and the cells reception equipment by adding an option in the Atoll.ini file.
For more information, see the Administrator Manual.
For more information on services, terminals, mobility types, and reception equipment, see "Service and User
Modelling" on page 241, and "Defining LTE Reception Equipment" on page 965, respectively.
If the selected terminal supports CoMP, the coverage prediction considers the coordinated multipoint transmission and reception characteristics of the CoMP set definitions of the cells.
For coordinated scheduling, interference from coordinated CoMP cells is weighted by the CoMP collision probability.
For coherent joint transmission, signals from CoMP servers are constructively combined resulting in an additive as well as probabilistic macro-diversity gain.
For non-coherent joint transmission, the CoMP servers allocate resources to the CoMP user resulting in aggregated throughput.
For dynamic point selection, a macro-diversity gain is calculated and applied to reduce the required shadowing
margin. For more information, see the Technical Reference Guide.
f. 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. The shadowing margin is based
on the C/I standard deviation.
g. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
5. Click the Display tab.
You can choose between displaying results by BER, BLER, FER, or any other quality indicator that you might have
added to the document. For more information, see "Defining LTE Quality Indicators" on page 964. The coverage
prediction results will be in the form of thresholds. For information on adjusting the display, see "Setting the Display
Properties of Objects" on page 51.
6. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.15 and
Figure 11.16).
892
AT332_UMR_E0
893
11.2.11.4.1
11.2.11.4.2
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 11.17).
11.2.11.4.3
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 91.
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 "Geographic Export Zone" on page 68.
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 210.
11.2.11.5.1
894
AT332_UMR_E0
) in the Radio Planning toolbar. The Point Analysis window opens and the pointer
2. At the top of the Point Analysis window, select the Reception view.
Select the load conditions to use in this analysis
from simulations or from the Cells table.
The connection
status for the
current point.
Successful
Failed
In the map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they
represent. The line from the pointer to its best server is slightly thicker than the other lines. The best server of the
pointer is the transmitter from which the pointer receives the highest RSRP or reference signal level.
4. In the Reception view toolbar, select the "Cells table" load condition the Loads list.
The bar graph displays the following information:
The RS, SS, or PDSCH signal levels, or the RSRP (depending on the selection made from the Display list) from different transmitters (the colour of the bar corresponds to the colour of the transmitter on the map). For coherent
joint transmission CoMP, the signals from all the servers are combined hence the same value is displayed for all
the servers.
The minimum RSRP: The empty portion of the bar indicates signal levels below the minimum RSRP.
The availability of reference signal coverage, and service in downlink and uplink.
If there is at least one successful connection (for reference signals, downlink, or uplink), double-clicking the icons in
the right-hand frame opens a dialog box with additional information with respect to the best server:
RS: Azimuth and tilt of the receiver, total losses, received reference signal power, reference signal C/(I+N), RSRP,
RSRQ, RSSI.
Downlink: Diversity mode, CoMP set, CoMP mode, CoMP collision probability, CoMP macro-diversity gain, list of
CoMP servers, received powers of the downlink channels, received total noise on the downlink channels, C/(I+N)
of the downlink channels, bearer, channel throughputs, cell capacities, and per-user throughputs.
Uplink: Diversity mode, CoMP set, CoMP mode, CoMP collision probability, list of CoMP servers, received powers
of the uplink channels, transmission power, allocated bandwidth, total noise on the uplink channels, C/(I+N) of the
uplink channels, bearer, channel throughputs, cell capacities, allocated bandwidth throughputs, and per-user
throughputs.
5. Select one of the bars in the bar graph to display the connection status for the corresponding cell in the right-hand
column.
6. If you are analysing reception to verify a coverage prediction, you can recreate the conditions of the coverage prediction by specifying the parameters of the study:
a. If necessary, in Layer and Channel, specify a layer and channel filter for the serving cells.
b. Select the same Terminal, Mobility, and Service as studied in the coverage prediction.
c. In the Reception view toolbar, click the Options button (
Edit the X and Y coordinates to change the current position of the receiver.
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. Indoor losses are defined per frequency per clutter
class.
895
7. 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.
8. In the Reception view toolbar, you can use the following tools:
Click the Report button ( ) to generate a report that contains the information from the point analysis window.
For an LTE-A terminal connected to more than one LTE-A cell, the report contains all the above-mentioned information for all the servers as well as aggregated throughput values combining the throughputs provided by all the
servers.
) to copy the content of the view and paste it as a graphic into a graphic editing or word-
If you want to get the details about the servers and interferers in the form of a table, you can use the Details view of the Point
Analysis tool (see "Obtaining Numerical Values of Signal Levels and Interference" on page 897).
You can display a point analysis that uses the settings from an existing prediction by
right-clicking the prediction in the Network explorer and selecting Open Point Analysis
from the context menu.
11.2.11.5.2
Analysing Interference
In Atoll, you can study the interferers of a transmitter using the Point Analysis tool. The Interference view gives you information on interference received on any downlink channel on any point on the map. The analysis is provided for a user-definable
probe receiver which has a terminal, a mobility, and a service. The downlink and uplink load conditions can be taken from the
Cells table or from Monte Carlo simulations.
To perform an interference point analysis:
1. Click the Point Analysis button (
view.
On the map, the pointer changes (
) in the Radio Planning toolbar. The Point Analysis window opens with the Profile
) to represent the receiver.
The signal level from the best server (topmost bar), total noise (black bar), and interference from other cells.
In the map window, a thick arrow from the pointer to its best server is displayed. The best server of the pointer is the
transmitter from which the pointer receives the highest RSRP or reference signal level. Thinner arrows are also
displayed from the interfering cells towards the pointer, indicating the interferers. 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.
4. In the Interference view toolbar, select "Cells table" from the Loads list.
The Interference view displays a bar graph showing the signal level from the best server, a black bar indicating the
total noise (I+N) received by the receiver, and the interference received from each interferer. If you let the pointer
rest on a bar, details are displayed in the tip text:
896
AT332_UMR_E0
For the best server: Name, received signal level, and C/(I+N).
For the total noise (I+N): The values of each component, i.e., I, N, and the downlink inter-technology noise rise.
For each interferer: The effective interference and the various interference reduction factors.
5. Select Inter-technology interference to display interference from other technologies. The Interference bar graph displays the interference received from each inter-technology interferer. Disable Inter-technology interference to display intra-technology interference only.
6. In the Interference view toolbar, in the Display list, select the channel on which you want to study the interference.
7. If you are analysing interference to verify a coverage prediction, you can recreate the conditions of the coverage prediction by specifying the parameters of the study:
a. If necessary, in Layer and Channel, specify a layer and channel filter for the serving cells.
b. Select the same Terminal, Mobility, and Service as studied in the coverage prediction.
c. In the Reception view toolbar, click the Options button (
Edit the X and Y coordinates to change the current position of the receiver.
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. Indoor losses are defined per frequency per clutter
class.
) to copy the content of the view and paste it as a graphic into a graphic editing or word-
You can display a point analysis that uses the settings from an existing prediction by
right-clicking the prediction in the Network explorer and selecting Open Point Analysis
from the context menu.
11.2.11.5.3
) in the Radio Planning toolbar. The Point Analysis window opens and the pointer
changes (
) to represent the receiver. You can move the receiver on the map ("Moving the Receiver on the Map"
on page 203).
2. Select the Details view. The Details view displays the following information in the form of a table:
Cell: The name of the cell from which the received signal levels are displayed. The cells are listed in decreasing
order of RSRP. The first row of the table is displayed in bold and italic indicating the best server of the pointer on
the map.
Distance (m): The distance from the cell to the current location of the pointer on the map.
Physical Cell ID: The physical cell ID of the cell.
ICIC Zone: Whether the pointer is located within the cell-centre or the cell-edge of its best serving cell.
Diversity Mode (DL): The diversity mode currently selected by the best server for the pointer in downlink.
Path Loss (dB): The path loss between the receiver and the cell.
Received RS Power (dBm): The received reference power from the cell.
RSRP (DL) (dBm): The RSRP received from the cell.
RSSI (DL) (dBm): The RSSI received at the receiver location.
Received PDCCH Power (dBm): The received PDCCH power from the cell.
Received PDCCH EPRE (dBm): The received energy per PDCCH resource element from the cell.
Received PDSCH Power (dBm): The received PDSCH power from the cell.
Received PDSCH EPRE (dBm): The received energy per PDSCH resource element from the cell.
897
Atoll lists all the cells from which the pointer receives an RSRP higher than the Min RSRP defined for these cells.
3. Move the pointer (
In the map window, a thick arrow from the pointer to its best server is displayed. The best server of the pointer is the
transmitter from which the pointer receives the highest RSRP or reference signal level. Thinner arrows are also
displayed from the interfering cells towards the pointer, indicating the interferers. If you let the pointer rest on an
arrow, the interference level received on the reference signals from the corresponding transmitter at the receiver
location will be displayed in the tip text.
4. Select "Cells table" from the Loads list.
5. If you are analysing interference to verify a coverage prediction, you can recreate the conditions of the coverage prediction by specifying the parameters of the study:
a. If necessary, in Layer and Channel, specify a layer and channel filter for the serving cells.
b. Select the same Terminal, Mobility, and Service as studied in the coverage prediction.
c. Select Inter-technology interference to display interference from other technologies.
d. Select Show interferers only to hide cells that do not interfere in the Details table.
e. In the Reception view toolbar, click the Options button (
Edit the X and Y coordinates to change the current position of the receiver.
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. Indoor losses are defined per frequency per clutter
class.
) in the Details view toolbar. The Columns to be Displayed dialog box opens.
CoMP Set (DL): The name of the CoMP set to which the receiver is connected.
RS C/(I+N) (DL) (dB): The RS C/(I+N) received from the cell.
RSRQ (DL) (dB): The RSRQ received from the cell.
RS Interference (dBm): The interference received from various downlink channels of the interfering cell on the
reference signals of the best server.
PDCCH Interference (dBm): The interference received from various downlink channels of the interfering cell on
the PDCCH of the best server.
PDSCH Interference (dBm): The interference received from various downlink channels of the interfering cell on
the PDSCH of the best server.
SS Interference (dBm): The interference received from the SS of the interfering cell on the SS of the best server.
PBCH Interference (dBm): The interference received from the PBCH of the interfering cell on the PBCH of the best
server.
PDSCH AAS Interference (dBm): The interference received from the angular interference distribution diagram of
the interfering cell on the PDSCH of the best server.
Channel Overlap Factor (dB): The co- and adjacent channel overlap between the frequency channel used by the
interfering cell and the best server.
Collision Probability (%): The inter-cell interference coordination collision probability between the interfering cell
which is not synchronised with the best server.
The interference values displayed for the best server (first row) are the sum of all the interference levels from all the
interfering cells listed in the following rows.
To display only interfering cells for the pointer on the map (cells whose C/N is above the Min Interferer C/N Threshold
defined in the Calculation Parameters tab of the LTE Network Settings Properties dialog box), select the Show interferers only check box.
8. Click the Point Analysis button (
898
AT332_UMR_E0
You can display a point analysis that uses the settings from an existing prediction by rightclicking the prediction in the Network explorer and selecting Open Point Analysis from the
context menu.
This section also covers the following topics related to subscriber analyses:
11.2.11.6.1
Load conditions: Select "(Cells table)" to calculate the point analysis using the load conditions defined in the cells
table. Select a simulation or a group of simulations to calculate the point analysis using the load conditions calculated
by Monte Carlo simulations.
Shadowing taken into account: Select this option to consider shadowing in the point analysis. For more information,
see "Modelling Shadowing in LTE" on page 974. If you select this option, you can change the Cell edge coverage probability.
Indoor coverage: Select this option to consider indoor losses. Indoor losses are defined per frequency per clutter class.
Position Id: The indexes of the points used for the point analysis.
X and Y: The coordinates of the points used for the point analysis.
Height (m): The height of the points used for the point analysis.
Service: The services assigned to the points used for the point analysis.
Terminal: The terminals assigned to the points used for the point analysis.
Mobility: The mobility types assigned to the points used for the point analysis.
11.2.11.6.2
899
Importing a list of points from an external file: Click the Actions button and select Import Table from the menu to
open the Open file dialog box. In this dialog box, select a TXT or CSV file containing a list of points and click Open.
For more information on importing data tables, see "Importing Tables from Text Files" on page 88.
Importing a list of points from a fixed subscriber traffic map: Click the Actions button and select Import from Fixed
Subscribers from the menu to open the Fixed Subscribers dialog box. In this dialog box, select one or more existing
fixed subscriber traffic maps and click OK.
Copying a list of points from an external file.
Creating points in the list by editing the table: Add new points by clicking the New Row icon ( ) and entering X
and Y coordinates as well as a service, a terminal, and a mobility.
The list of points must have the same coordinate system as the display coordinate system
used in the Atoll document. For more information on coordinate systems, see "Setting a
Coordinate System" on page 41.
It is also possible to leave the Points tab empty and add points to the analysis on
the map using the mouse once the point analysis item has been created. To add
points on the map using the mouse, right-click the point analysis item to which you
want to add points, and select Add Points from the context menu. The mouse
pointer changes to point creation mode (
want to add. Press ESC or click the Pointer button ( ) in the Map toolbar to finish
adding points.
You can also export the list of point from a point analysis to ASCII text files (TXT and
CSV formats) and MS Excel XML Spreadsheet files (XML format) by selecting
Actions > Export Table. For more information on exporting table data, see
"Exporting Tables to Text Files and Spreadsheets" on page 86.
4. On the Display tab, specify how to display point analysis results on the map according to any input or calculated
parameter. For more information on defining display properties, see "Setting the Display Properties of Objects" on
page 51.
5. Once you have defined the point analysis parameters, you can calculate it immediately or you can save it and calculate
it later:
Calculate: Click Calculate to save the point analysis and calculate it immediately.
OK: Click OK to save the point analysis without calculating it. You can calculate it later by opening the point analysis
properties and clicking the Calculate button.
Once Atoll has finished calculating the point analysis, the results are displayed in the map window. You can also access the
analysis results in a table format. For more information, see "Viewing Point Analysis Results" on page 900.
You can also organise point analyses in folders under the Multi-point Analysis folder by creating folders under the Multi-point
Analysis folder in the Network explorer. Folders may contain one or more point analyses items. You can move point analyses
items from one folder to another and rename folders.
11.2.11.6.3
900
Position Id: The indexes of the points used for the point analysis.
X and Y: The coordinates of the points used for the point analysis.
Height (m): The height of the points used for the point analysis.
Service: The services assigned to the points used for the point analysis.
Terminal: The terminals assigned to the points used for the point analysis.
Mobility: The mobility types assigned to the points used for the point analysis.
AT332_UMR_E0
CoMP Set (DL): The name of the CoMP set to which the receiver is connected.
RS C/(I+N) (DL) (dB): The RS C/(I+N) received from the best serving cell.
RSRQ (DL) (dB): The RSRQ received from the best serving cell.
RS Interference (dBm): The interference received from various downlink channels of interfering cells on the reference signals of the best server.
PDCCH Interference (dBm): The interference received from various downlink channels of interfering cells on the
PDCCH of the best server.
PDSCH Interference (dBm): The interference received from various downlink channels of interfering cells on the
PDSCH of the best server.
SS Interference (dBm): The interference received from the SS of interfering cells on the SS of the best server.
PBCH Interference (dBm): The interference received from the PBCH of interfering cells on the PBCH of the best
server.
PDSCH AAS Interference (dBm): The interference received from the angular interference distribution diagram of
interfering cells on the PDSCH of the best server.
Channel Overlap Factor (dB): The co- and adjacent channel overlap between the frequency channel used by interfering cells and the best server.
Collision Probability (%): The inter-cell interference coordination collision probability between interfering cells
which is not synchronised with the best server.
The interference values displayed for the best server (first row) are the sum of all the interference levels of all the
interfering cells listed in the following rows.
You can export the point analysis results table to ASCII text files (TXT and CSV formats) and
MS Excel XML Spreadsheet files (XML format) by selecting Actions > Export. For more
information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets"
on page 86.
3. Click Close.
11.2.11.6.4
901
11.2.11.6.5
Calculate: Click Calculate to save the subscriber analysis and calculate it immediately.
OK: Click OK to save the subscriber analysis without calculating it. You can calculate it later by opening the subscriber analysis properties and clicking the Calculate button.
Once Atoll has finished calculating the subscriber analysis, the results are displayed in the map window. You can also access
the analysis results in a table format. For more information, see "Viewing Subscriber Analysis Results" on page 902.
You can also organise subscriber analyses in folders under the Multi-point Analysis folder by creating folders under the Multipoint Analysis folder in the Network explorer. Folders may contain one or more subscriber analyses items. You can move
subscriber analyses items from one folder to another and rename folders.
11.2.11.6.6
902
AT332_UMR_E0
RSRP (RS EPRE) (DL) (dBm): The RSRP (received reference signal energy per resource element) received at the subscriber location in the downlink.
RSSI (DL) (dBm): The RSSI received at the subscriber location in the downlink.
RSRQ (DL) (dB): The RSRQ (reference signal received quality) at the subscriber location in the downlink.
Received RS power (DL) (dBm): The reference signal level received at the subscriber location in the downlink.
Received SS power (DL) (dBm): The SS signal level received at the subscriber location in the downlink.
Received PBCH power (DL) (dBm): The PBCH signal level received at the subscriber location in the downlink.
Received PDCCH power (DL) (dBm): The PDCCH signal level received at the subscriber location in the downlink.
Received PDSCH power (DL) (dBm): The PDSCH signal level received at the subscriber location in the downlink.
RS C/(I+N) (DL) (dB): The reference signal C/(I+N) at the subscriber location in the downlink.
SS C/(I+N) (DL) (dB): The SS C/(I+N) at the subscriber location in the downlink.
PBCH C/(I+N) (DL) (dB): The PBCH C/(I+N) at the subscriber location in the downlink.
PDCCH C/(I+N) (DL) (dB): The PDCCH C/(I+N) at the subscriber location in the downlink.
PDSCH C/(I+N) (DL) (dB): The PDSCH C/(I+N) at the subscriber location in the downlink.
RS total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the subscriber location in
the downlink on the reference signals.
SS & PBCH total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the subscriber location in the downlink on the SS and PBCH.
PDCCH total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the subscriber location
in the downlink on the PDCCH.
PDSCH total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the subscriber location
in the downlink on the PDSCH.
Bearer (DL): The highest LTE bearer available for the PDSCH C/(I+N) level at the subscriber location in the downlink.
BLER (DL): The Block Error Rate read from the subscriber terminals reception equipment for the PDSCH C/(I+N)
level at the subscriber location in the downlink.
Diversity mode (DL): The diversity mode used by the cell in downlink for the subscriber.
Peak RLC channel throughput (DL) (kbps): The maximum RLC channel throughput attainable using the highest
bearer available at the subscriber location in the downlink.
Effective RLC channel throughput (DL) (kbps): The effective RLC channel throughput attainable using the highest
bearer available at the subscriber location in the downlink. It is calculated from the peak RLC throughput and the
BLER.
Application channel throughput (DL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, and so on). It is calculated from the effective RLC throughput, the throughput
scaling factor of the service and the throughput offset.
Received PUSCH & PUCCH power (UL) (dBm): The PUSCH & PUCCH signal level received at the serving transmitter
from the subscriber terminal in the uplink.
PUSCH & PUCCH total noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the serving
transmitter of the subscriber in the uplink on the PUSCH.
PUSCH & PUCCH C/(I+N) (UL) (dB): The PUSCH & PUCCH C/(I+N) at the serving transmitter of the subscriber in the
uplink.
Bearer (UL): The highest LTE bearer available for the PUSCH & PUCCH C/(I+N) level at the serving transmitter of
the subscriber in the uplink.
BLER (UL): The Block Error Rate read from the serving cells reception equipment for the PUSCH & PUCCH C/(I+N)
level at the serving transmitter of the subscriber in the uplink.
Diversity mode (UL): The diversity mode used by the cell in uplink for the subscriber.
Transmission power (UL) (dBm): The transmission power of the subscriber terminal after power control in the
uplink.
Allocated bandwidth (UL) (No. of frequency blocks): The number of frequency blocks allocated to the subscriber
in the uplink by the eNode-B.
Peak RLC channel throughput (UL) (kbps): The maximum RLC channel throughput attainable using the highest
bearer available at the subscriber location in the uplink.
Effective RLC channel throughput (UL) (kbps): The effective RLC channel throughput attainable using the highest
bearer available at the subscriber location in the uplink. It is calculated from the peak RLC throughput and the
BLER.
Application channel throughput (UL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, and so on). It is calculated from the effective RLC throughput, the throughput
scaling factor of the service and the throughput offset.
Peak RLC allocated bandwidth throughput (UL) (kbps): The maximum RLC throughput attainable for the number
of frequency blocks allocated to the subscriber using the highest bearer available at the user location in the uplink.
Effective RLC allocated bandwidth throughput (UL) (kbps): The effective RLC throughput attainable for the
number of frequency blocks allocated to the subscriber using the highest bearer available at the subscriber location in the uplink. It is calculated from the peak RLC throughput and the BLER.
Application allocated bandwidth throughput (UL) (kbps): The application throughput is the net throughput
without coding (redundancy, overhead, addressing, and so on). It is calculated from the effective RLC throughput,
the throughput scaling factor of the service and the throughput offset.
903
Figure 11.20: LTE handover area between a reference cell and a potential neighbour
In this section, only the following concepts that are specific to automatic neighbour allocation in LTE networks are explained:
For general information on neighbour planning in Atoll, see "Neighbour Planning" on page 223:
When Use coverage conditions is not selected, the defined Distance is used to allocate neighbours to a reference
transmitter.
When Use coverage conditions is selected, click Define to open the Coverage Conditions dialog box:
904
Resolution: Enter the resolution to be used to calculate cell coverage areas for automatic neighbour allocation.
Global reception threshold: Select this option to set a global reception threshold. If you set a value here, Atoll will
use this value or the per-cell Min RSRP value if it is higher.
Handover start (HO margin): Define the handover margin that corresponds to the beginning of the handover process. You can define a global value for the handover margin or use the handover margins defined per cell.
Handover end: Enter a the margin that corresponds to the end of the handover process. This margin is considered
beyond Handover start. The larger the Handover end, the longer the list of potential neighbours. The area
between Handover start and Handover end is the area in which Atoll will search for neighbours.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this option to take indoor losses into account in calculations. Indoor losses are defined
per frequency per clutter class.
AT332_UMR_E0
Co-site cells as neighbours: cells located on the same site as the reference cell will automatically be considered as
neighbours. A cell with no antenna cannot be considered as a co-site neighbour.
Adjacent cells as neighbours: cells that are adjacent to the reference cell will automatically be considered as neighbours. A cell is considered adjacent if there is at least one pixel in the reference cells coverage area where the potential neighbour cell is the best server, or where the potential neighbour cell is the second best server in the reference
cells active set.
Adjacent layers as neighbours: cells that are adjacent to the reference cell across layers will be automatically considered as neighbours.
Symmetric relations: Select this check box if you want the neighbour relations to be reciprocal, i.e. any reference
transmitter/cell is a potential neighbour of all the cells that are its neighbours.
Exceptional pairs: Select this check box to force the neighbour relations defined in the Intra-technology Exceptional
pairs table. For information on exceptional pairs, see "Exceptional Pairs" on page 223.
Cause
Description
When
Distance
Coverage
Co-Site
Adjacent
Adjacent layer
Symmetry
Exceptional Pair
Exceptional pairs
is selected
Existing
Once the AFP input elements have been set up, the AFP can be used for:
905
Once you have completed an automatic allocation, you can analyse the results with the tools that Atoll provides:
5. Once you have created the new interference matrix, you can calculate it immediately or you can save it and calculate
it later:
Calculate: Click Calculate to save the defined interference matrix and calculate it immediately.
OK: Click OK to save the defined interference matrix without calculating it. You can calculate it later by clicking the
Calculate button (
Once calculated, the new interference matrix is available in the Interference Matrices folder and will be available for use the
next time you run the AFP.
You can modify the properties of an existing interference matrix by selecting Properties from the interference matrix context
menu. You can recalculate an existing interference matrix by selecting Calculate from the interference matrix context menu.
906
AT332_UMR_E0
3. Click in another cell of the table to create the new domain and add a new blank row to the table.
4. Double-click the domain to which you want to add a group. The domains Properties dialog box appears.
5. Under Groups, enter the following information for each group you want to create.
907
6. Click in another cell of the table to create the new group and add a new blank row to the table.
3. Click in another cell of the table to create the new domain and add a new blank row to the table.
4. Double-click the domain to which you want to add a group. The domains Properties dialog box appears.
5. Under Groups, enter the following information for each group you want to create.
6. Click in another cell of the table to create the new group and add a new blank row to the table.
1st order neighbours: The relative weight assigned to a first order neighbour relationship violation.
Interference matrices: The relative weight assigned to an interference matrix-based relationship violation.
Distance: The relative weight assigned to a distance-based relationship violation.
You can click the Reset button to set the weights to their default values.
5. Click the Physical Cell ID Allocation tab.
908
In the Relation weights frame, you can set the weights for the following cost components:
1st order neighbours: The relative weight assigned to a first order neighbour relationship violation.
Second order neighbours: The relative weight assigned to a second order neighbour relationship violation.
Neighbours of a common cell: The relative weight assigned to the violation of an indirect neighbour relationship between neighbours of a common cell.
AT332_UMR_E0
Interference matrices: The relative weight assigned to a interference matrix-based relationship violation.
Distance: The relative weight assigned to a distance-based relationship violation.
You can click the Reset button to set the weights to their default values.
In the Constraint violation weights frame, you can set the weights for the following constraints:
Physical cell ID: The relative weight assigned to a physical cell ID collision between two related cells.
PSS ID: The relative weight assigned to a PSS ID (PCI Mod 3) collision between two related cells.
Strategy for co-site cells: The relative weight assigned to any allocation strategy used for co-site cells.
PCI Mod 6 (DL RS): The relative weight assigned to a downlink reference signal shifting (PCI Mod 6) collision
between two related cells.
PCI Mod 30 (UL DMRS): The relative weight assigned to an uplink demodulation reference signal sequence
group (PCI Mod 30) collision between two related cells.
PCFICH REG: The relative weight assigned to a physical control format indicator channel resource element
group (PCI Mod (number of frequency blocks / 2)) collision between two related cells.
You can click the Reset button to set the weights to their default values.
Constraint violation weights may be determined based on the numbers of available
resources for each constraint. For example, if the following constraints need to be taken
into account, their respective violation weights may be calculated supposing that the
constraint violation of a single resource of any given type presents the same amount of
imbalance in the network:
Constraint type
Number of resources
Violation weighta
Physical cell ID
504
71
PSS ID
1b
SSS ID
168
23
PCI Mod 30
17
PCFICH REG
21c
Total
713
100
a.
ROUND(Number of resources/Total)
b.
Artificially kept at 1 by slightly reducing the SSS ID weight so that
the PSS weight is not 0.
c.
For a 10 MHz channel.
6. Click the PRACH RSI Allocation tab. On this tab, you can set the weights for the following cost components:
1st order neighbours: The relative weight assigned to a first order neighbour relationship violation.
Second order neighbours: The relative weight assigned to a second order neighbour relationship violation.
Interference matrices: The relative weight assigned to a interference matrix-based relationship violation.
Distance: The relative weight assigned to a distance-based relationship violation.
You can click the Reset button to set the weights to their default values.
7. Click OK.
909
The top line contains global information about the current allocation (resource being allocated and the total cost
of the current plan).
The left-hand side of the dialog box contains tabs with input parameters.
The right-hand side of the dialog box provides the allocation results.
2. From the Allocate list, select Frequencies for automatic frequency planning.
3. On the Relation Types tab, you can set the relations to take into account in automatic allocation:
Existing neighbours: Select this option if you want the AFP to take neighbour relations into account for the allocation. The AFP will try to allocate different frequencies to a cell and its neighbours.
Atoll can only take neighbour relations into account if neighbours have already been allocated. For information
on allocating neighbours, see "Configuring Network Parameters Using the AFP" on page 905.
Interference matrix: Select this option if you want the AFP to take interference matrices into account for the allocation, and select an interference matrix from the list. For Atoll to take interference matrices into account, they
must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, and imported in the Interference Matrices folder. For more information on interference matrices, see
"Working with Interference Matrices" on page 906.
Reuse distance: Select this option if you want the AFP to take relations based on distance into account for the allocation. You can enter a Default reuse distance within which two cells must not have the same channel assigned.
However, it is highly recommended to define a reuse distance for each individual cell depending on the size of the
cells coverage area and the network density around the cell. If defined, a cell-specific reuse distance is used
instead of the default value entered here.
4. On the right-hand side of the Automatic Resource Allocation dialog box, Atoll displays the Total cost of the current
frequency allocation. You can click Update to calculate the total cost take into account the parameters set in step 3.
You can click the Weights button to open the Weights dialog box and modify the cost
component weights. For more information, see "Configuring Cost Component Weights" on
page 908.
5. Click Start. Atoll begins the process of allocating frequencies. Any messages generated by the AFP during automatic
allocation are reported on the Events tab.
While Atoll allocates frequencies, you can:
Once Atoll has finished allocating frequencies, or if you pause the automatic allocation, the Statistics tab shows the
number of proposed changes to the allocation plan and the numbers of different relations, violations, and collisions.
910
AT332_UMR_E0
It also shows the numbers of violations and collisions in the current plan compared to the initial one (in brackets). The
Results tab shows the proposed allocation plan:
In order to better view the progress graph and the results table, you can expand
the right-hand side zone of the Automatic Resource Allocation dialog box by
clicking the Hide Inputs button
. You can also resize the dialog box.
You can export the contents of table grids to TXT, CSV, and XML Spreadsheet files
by right-clicking the table and selecting Export from the context menu. For more
information on exporting data tables, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
You can select the columns to display in different tabs by right-clicking the table
and selecting Display Columns from the context menu. For more information, see
"Displaying and Hiding Columns" on page 80.
6. Click Commit. The proposed frequency plan is assigned to the cells of the network.
7. Click Close.
When you allocate frequencies to a large number of cells, it is easiest to let Atoll allocate them automatically. However, if you
want to assign a frequency to one cell or to modify it, you can do it by accessing the properties of the cell.
The top line contains global information about the current allocation (resource being allocated and the total cost
of the current plan).
The left-hand side of the dialog box contains tabs with input parameters.
The right-hand side of the dialog box provides the allocation results.
2. From the Allocate list, select Physical Cell IDs for automatic physical cell ID planning.
3. On the Relation Types tab, you can set the relations to take into account in automatic allocation:
911
Existing neighbours: Select this check box if you want the AFP to take neighbour relations into account for the allocation. The AFP will try to allocate different physical cell IDs to a cell and its neighbours, and to the neighbours of
a common cell. In 3GPP multi-RAT documents, the AFP will also try to allocate different physical cell IDs to LTE cells
that are neighbours of a common GSM transmitter or UMTS cell. In 3GPP2 multi-RAT documents, the AFP will also
try to allocate different physical cell IDs to LTE cells that are neighbours of a common CDMA cell.
The AFP can take neighbours into account only if neighbours have already been allocated. If you want the AFP to
take both first and second order neighbours into account, you must set an option in the Atoll.ini file (see the Administrator Manual).
Interference matrix: Select this check box if you want the AFP to take interference matrices into account for the
allocation, and select an interference matrix from the list. For Atoll to take interference matrices into account,
they must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be
calculated, and imported in the Interference Matrices folder. For more information on interference matrices, see
"Working with Interference Matrices" on page 906.
Reuse distance: Select this check box if you want the AFP to take relations based on distance into account for the
allocation. You can enter a Default reuse distance within which two cells must not have the same physical cell ID
assigned. However, it is highly recommended to define a reuse distance for each individual cell depending on the
size of the cells coverage area and the network density around the cell. If defined, a cell-specific reuse distance is
used instead of the default value entered here. A macro that automatically calculates a reuse distance for each
cell can be provided upon request.
When using the "Reuse Distance" macro on 64-bit versions of Atoll, the Windows regional
settings must be consistent.
To check that the regional settings are consistent, select Control Panel > Region and
Language, and make sure that the Format setting in the Format tab matches the Current
language for non-Unicode programs in the Administrative tab. If necessary, change the
current language by clicking Change system locale and restart the computer.
4. On the Constraints tab, you can set the constraints to take into account in automatic allocation:
Allocation domain: You can choose Per cell to allocate physical cell IDs from the physical cell ID domains defined
per cell, you can choose to allocate from the Entire (0-503) domain, or you can choose Custom and enter the
Excluded resources to exclude some physical cell IDs from the allocation.
You can enter non-consecutive physical cell IDs separated with a comma, or you can enter a range of physical cell
IDs separating the first and last one with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
Select an allocation Strategy for co-site cells. If you select Same SSS ID, the AFP will try to allocate the same
SSS ID to all the cells of a site. If you select Fixed PCI step and enter a value for the required Step, the AFP will
try to allocate PCIs to co-site cells according to the defined regular step. For example, for a required step of 4,
PCIs 0, 4, 8, and so on will be allocated to co-site cells.
Steps of 0 and 1 are not allowed and 8 is used instead.
Select the Take into account frequency plan check box if you want the AFP to consider the frequency plan
when determining physical cell ID collisions.
5. On the right-hand side of the Automatic Resource Allocation dialog box, Atoll displays the Total cost of the current
physical cell ID allocation. You can click Update to calculate the total cost take into account the parameters set in
step 3.
You can click the Weights button to open the Weights dialog box and modify the cost
component weights. For more information, see "Configuring Cost Component Weights" on
page 908.
6. Click Start. Atoll begins the process of allocating physical cell IDs. Any messages generated by the AFP during automatic allocation are reported on the Events tab.
While Atoll allocates physical cell IDs, you can:
912
AT332_UMR_E0
Resume the automatic allocation process by clicking Continue or start the automatic allocation from the initial
state by clicking Restart.
Once Atoll has finished allocating physical cell IDs, or if you pause the automatic allocation, the Statistics tab shows
the number of proposed changes to the allocation plan and the numbers of different relations, violations, and collisions. It also shows the numbers of violations and collisions in the current plan compared to the initial one (in brackets). The Results tab shows the proposed allocation plan:
In order to better view the progress graph and the results table, you can expand
the right-hand side zone of the Automatic Resource Allocation dialog box by
clicking the Hide Inputs button
. You can also resize the dialog box.
You can export the contents of table grids to TXT, CSV, and XML Spreadsheet files
by right-clicking the table and selecting Export from the context menu. For more
information on exporting data tables, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
You can select the columns to display in different tabs by right-clicking the table
and selecting Display Columns from the context menu. For more information, see
"Displaying and Hiding Columns" on page 80.
7. Click Commit. The proposed physical cell ID plan is assigned to the cells of the network.
8. Click Close.
When you allocate physical cell IDs to a large number of cells, it is easiest to let Atoll allocate them automatically. However,
if you want to assign a physical cell ID to one cell or to modify it, you can do it by accessing the properties of the cell.
To allocate a physical cell ID to an LTE cell manually:
1. On the map or in the LTE Transmitters folder in the Network explorer, right-click the transmitter to whose cell you
want to allocate a physical cell ID. The context menu appears.
2. Select Properties from the context menu. The transmitters Properties dialog box appears.
3. Select the Cells tab.
4. Enter a Physical cell ID in the cells column.
5. You can set the PSS ID Status and SSS ID Status to Locked if you want to lock the physical cell ID that you assigned.
6. Click OK.
913
The top line contains global information about the current allocation (resource being allocated and the total cost
of the current plan).
The left-hand side of the dialog box contains tabs with input parameters.
The right-hand side of the dialog box provides the allocation results.
2. From the Allocate list, select PRACH Root Sequence Indexes for automatic PRACH RSI planning.
3. On the Relation Types tab, you can set the relations to take into account in automatic allocation:
Existing neighbours: Select this check box if you want the AFP to take neighbour relations into account for the allocation. The AFP will try to allocate different PRACH RSIs to a cell and its neighbours. Atoll can only take neighbour
relations into account if neighbours have already been allocated. For information on allocating neighbours, see
the User Manual.
Interference matrix: Select this check box if you want the AFP to take interference matrices into account for the
allocation, and select an interference matrix from the list. For Atoll to take interference matrices into account,
they must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be
calculated, and imported in the Interference Matrices folder. For more information on interference matrices, see
the User Manual.
Reuse distance: Select this check box if you want the AFP to take relations based on distance into account for the
allocation. You can enter a Default reuse distance within which two cells must not have the same PRACH RSI
assigned. However, it is highly recommended to define a reuse distance for each individual cell depending on the
size of the cells coverage area and the network density around the cell. If defined, a cell-specific reuse distance is
used instead of the default value entered here.
4. On the Constraints tab, you can set the constraints to take into account in automatic allocation:
Allocation domain: You can choose Per cell to allocate PRACH RSIs from the PRACH RSI domains defined per cell,
you can choose to allocate from the Entire (0-838 / 0-138) domain, or you can choose Custom and enter the
Excluded resources to exclude some PRACH RSIs from the allocation.
You can enter non-consecutive PRACH RSIs separated with a comma, or you can enter a range of PRACH RSIs separating the first and last one with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
Allocation strategies: You can select the Take into account frequency plan check box if you want the AFP to consider the frequency plan when determining PRACH RSI collisions.
5. On the right-hand side of the Automatic Resource Allocation dialog box, Atoll displays the Total cost of the current
frequency allocation. You can click Update to calculate the total cost take into account the parameters set in step 3.
You can click the Weights button to open the Weights dialog box and modify the cost
component weights. For more information, see "Configuring Cost Component Weights" on
page 908.
6. Click Start. Atoll begins the process of allocating PRACH RSIs. Any messages generated by the AFP during automatic
allocation are reported on the Events tab.
While Atoll allocates PRACH RSIs, you can:
914
AT332_UMR_E0
Compare the distribution histograms of the initial and current allocation plans in the Distribution tab.
Pause the automatic allocation process by clicking Pause.
Resume the automatic allocation process by clicking Continue or start the automatic allocation from the initial
state by clicking Restart.
Once Atoll has finished allocating PRACH RSIs, or if you pause the automatic allocation, the Statistics tab shows the
number of proposed changes to the allocation plan and the numbers of different relations, violations, and collisions.
It also shows the numbers of violations and collisions in the current plan compared to the initial one (in brackets). The
Results tab shows the proposed allocation plan:
the proposed allocation plan is available on the Results tab. The Results tab contains the following information:
In order to better view the progress graph and the results table, you can expand
the right-hand side zone of the Automatic Resource Allocation dialog box by
clicking the Hide Inputs button
. You can also resize the dialog box.
You can export the contents of table grids to TXT, CSV, and XML Spreadsheet files
by right-clicking the table and selecting Export from the context menu. For more
information on exporting data tables, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
You can select the columns to display in different tabs by right-clicking the table
and selecting Display Columns from the context menu. For more information, see
"Displaying and Hiding Columns" on page 80.
7. Click Commit. The proposed PRACH RSI plan is assigned to the cells of the network.
8. Click Close to exit.
When you allocate PRACH RSIs to a large number of cells, it is easiest to let Atoll allocate them automatically. However, if you
want to assign a PRACH RSI list to one cell or to modify it, you can do it by accessing the properties of the cell.
"Using the Find on Map Tool to Display AFP Results" on page 915.
"Grouping Transmitters by Channels or Physical Cell IDs" on page 917.
915
To restore the initial transmitter colours, click the Reset display button in the Find on Map window.
To find a channel number using Find on Map:
1. Select Tools > Find on Map. The Find on Map window opens.
2. From the Find list, select "LTE Channel."
3. From the Band list, select a frequency band.
4. From the Channel list, select the channel number.
By default, Find on Map displays only co-channel transmitter cells. If you want adjacent channels to be displayed as
well, select the Adjacent channels check box.
5. Click Search.
Transmitters whose cells use the selected frequency band and channel number are displayed in red. Transmitters with
cells using two adjacent channel numbers in the same frequency band (i.e., a channel higher and a channel lower) are
displayed in yellow. Transmitters with cells using a lower adjacent channel number in the same frequency band are
displayed in green. Transmitters with cells using a higher adjacent channel number in the same frequency band are
displayed in blue. All other transmitters are displayed as grey lines.
If you cleared the Adjacent channels check box, transmitters with cells using the same channel number are displayed
in red, and all others, including transmitters with adjacent channels, are displayed as grey lines.
To restore the initial transmitter colours, click the Reset display button in the Find on Map window.
By including the frequency band and channel number of each cell in the transmitter label,
the search results will be easier to understand. For information on defining the label, see
"Associating a Label to an Object" on page 53.
To find a physical cell ID, PSS ID, SSS ID, or PRACH RSI using Find on Map:
1. Click Tools > Find on Map. The Find on Map window opens.
2. From the Find list, select "Cell Identifier."
3. Select what you want to search for:
Physical cell ID: Select Physical cell ID and enter a physical cell ID in the edit box.
PSS ID: Select PSS ID and select the PSS ID from the list: "All," "0," "1," or "2."
SSS ID: Select SSS ID and enter an SSS ID in the edit box.
PRACH RSI: Select PRACH RSI and enter a PRACH RSI in the edit box.
4. Click Search.
When you select a physical cell ID, an SSS ID, or a PRACH RSI, transmitters with cells matching the search criteria are
displayed in red. Transmitters that do not match the search criteria are displayed as grey lines.
When you select a specific PSS ID, transmitters whose cells use the selected ID are displayed in red. Transmitters with
cells that use other IDs are displayed as grey lines. When you choose to search for all PSS IDs, transmitters whose first
cells use ID 0 are displayed in red, transmitters whose first cells use ID 1 are displayed in yellow, and transmitters
whose first cells use ID 2 are displayed in green.
To restore the initial transmitter colours, click the Reset display button in the Search Tool window.
By including the physical cell ID of each cell in the transmitter label, the search
results will be easier to understand. For information on defining the label, see
"Associating a Label to an Object" on page 53.
Transmitters with more than one cell might use different PSS IDs in different cells.
Therefore, the search for all PSS IDs is only valid for single-cell transmitters.
916
AT332_UMR_E0
You can also display the frequency band and channel number in the transmitter label or tip text by selecting "Cells: Frequency
band" and "Cells: Channel number" from the Label or Tip Text Field Selection dialog box.
To display physical cell ID allocation on the map:
1. In the Network explorer, right-click the LTE Transmitters folder and select Properties from the context menu. The
Properties dialog box appears.
2. Click the Display tab.
3. Select "Discrete values" as the Display type and "Cells: Physical cell ID" as the Field.
4. Click OK. Transmitters are displayed by physical cell ID.
You can also display the physical cell ID in the transmitter label or tip text by selecting "Cells: Physical cell ID" from the Label
or Tip Text Field Selection dialog box.
For information on display options, see "Setting the Display Properties of Objects" on page 51.
Frequency band
Channel number
Physical cell ID
PRACH root sequences
5. Click
to add the parameter to the Group these fields in this order list. The selected parameter is added to the list
of parameters on which the transmitters will be grouped.
6. If you do not want the transmitters to be sorted by a certain parameter, select the parameter in the Group these fields
in this order list and click
ters will be grouped.
. The selected parameter is removed from the list of parameters on which the transmit-
7. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters to
be grouped:
a. Select a parameter and click
8. Click OK to save your changes and close the Group dialog box.
917
The top line contains global information about the current allocation (resource being audited and the total cost of
the current plan).
The left-hand side of the dialog box contains tabs with input parameters.
The right-hand side of the dialog box provides the audit results.
Existing Neighbours: Select this check box if you want the audit to take neighbours into account. Atoll can only
take neighbour relations into account if neighbours have already been allocated. For information on allocating
neighbours, see "Configuring Network Parameters Using the AFP" on page 905.
Interference matrix: Select this check box if you want the audit to take interference matrices into account, and
select an interference matrix from the list. For Atoll to take interference matrices into account, they must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, and
imported in the Interference Matrices folder. For more information on interference matrices, see "Working with
Interference Matrices" on page 906.
Reuse distance: Select this check box if you want the audit to take reuse distance into account. For cells that do
not have a reuse distance defined in their properties, the value entered next to Default will be used for the audit.
4. On the right-hand side of the Resource Allocation Audit dialog box, Atoll displays the Total cost of the current frequency allocation.
You can click the Weights button to open the Weights dialog box and modify the cost
component weights. For more information, see "Configuring Cost Component Weights" on
page 908.
5. Click Calculate. Atoll performs an audit of the current frequency plan. Any messages generated by the audit are
reported on the Events tab. The audit results are reported on the following tabs:
The Statistics tab provides overall statistics such as the numbers of various types of relations considered by the AFP
for frequency planning and the number of violated relations.
The Relations tab lists all the relations between active and filtered cells in the document. The Relations tab can display
the following information:
ii. Under Include relations by type, select all the options representing the relation types and select (All) from
their respective lists.
iii. Click Apply. The data table in the Relations tab shows all the relations between cells.
To view only the relations that violate the frequency allocation requirements:
i.
ii. Under Include relations by type, select all the options representing the relation types and select (All) from
their respective lists.
918
AT332_UMR_E0
iii. Click Apply. The data table in the Relations tab shows only the relations that violate the frequency allocation
requirements.
To view only the important relations that violate the frequency allocation requirements:
i.
ii. Under Include relations by type, select the relation types that you consider important and select some or all
of their characteristics from their respective lists.
iii. Click Apply. The data table in the Relations tab shows the relations according to the user-defined filter.
The Cells tab lists the current allocation plan and the following information:
The Distribution tab shows the histogram of the current allocation plan.
You can expand the right pane of the Resource Allocation Audit dialog box by
clicking the Hide button ( ). You can also resize the dialog box.
You can export the contents of table grids to TXT, CSV, and XML Spreadsheet files
by right-clicking the table and selecting Export from the context menu. For more
information on exporting data tables, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
You can select the columns to display in different tabs by right-clicking the table
and selecting Display Columns from the context menu. For more information, see
"Displaying and Hiding Columns" on page 80.
LTE cells with identical physical cell IDs that are neighbours of the same GSM transmitter,
LTE cells with identical physical cell IDs that are neighbours of the same UMTS cell,
LTE cells with identical physical cell IDs that are neighbours of the same CDMA cell.
The top line contains global information about the current allocation (resource being audited and the total cost of
the current plan).
The left-hand side of the dialog box contains tabs with input parameters.
The right-hand side of the dialog box provides the audit results.
Existing Neighbours: Select this check box if you want the audit to take neighbours into account. Atoll can only
take neighbour relations into account if neighbours have already been allocated. For information on allocating
neighbours, see "Configuring Network Parameters Using the AFP" on page 905.
Interference matrix: Select this check box if you want the audit to take interference matrices into account, and
select an interference matrix from the list. For Atoll to take interference matrices into account, they must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, and
imported in the Interference Matrices folder. For more information on interference matrices, see "Working with
Interference Matrices" on page 906.
Reuse distance: Select this check box if you want the audit to take reuse distance into account. For cells that do
not have a reuse distance defined in their properties, the value entered next to Default will be used for the audit.
919
4. On the right-hand side of the Resource Allocation Audit dialog box, Atoll displays the Total cost of the current physical
cell ID allocation.
You can click the Weights button to open the Weights dialog box and modify the cost
component weights. For more information, see "Configuring Cost Component Weights" on
page 908.
5. On the Constraints tab, you can set the constraints to take into account in the audit:
Allocation domain: You can choose Per cell to check if the allocated physical cell IDs belong to the physical cell ID
domains defined per cell, or you can choose to the Entire (0-503) domain or define a Custom domain by entering
the Excluded resources.
You can enter non-consecutive physical cell IDs separated with a comma, or you can enter a range of physical cell
IDs separating the first and last one with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
Allocation strategies: You can select the Same per site strategy for the SSS ID to check whether the same SSS ID
has been allocated to the cells of the same site. You can select the Different PSS ID per site check box to have the
audit verify whether co-site cells have different PSS IDs.
You can select the Take into account frequency plan check box if you want the audit to consider the frequency
plan when determining physical cell ID collisions.
6. Click Calculate. Atoll performs an audit of the current physical cell ID plan. Any messages generated by the audit are
reported on the Events tab. The audit results are reported on the following tabs:
The Statistics tab provides overall statistics such as the numbers of various types of relations considered by the AFP
for physical cell ID planning, the numbers of violated relations of each type, the number of collisions for each resource
type, the number of cells not satisfying the domain compliance criteria, and numbers of strategy violations for
selected allocation strategies.
The Relations tab lists all the relations between active and filtered cells in the document. The Relations tab can display
the following information:
920
AT332_UMR_E0
The data table in the Relations tab can be filtered. For example, you can view all the relations, only the relations
that violate the physical cell ID allocation requirements, or apply a filter to exclude unimportant ones. To filter the
relations listed in the Relations tab, click the Show button (
ii. Under Include relations by type, select all the options representing the relation types and select (All) from
their respective lists.
iii. Click Apply. The data table in the Relations tab shows all the relations between cells.
To view only the relations that violate the physical cell ID allocation requirements:
i.
ii. Under Include relations by type, select all the options representing the relation types and select (All) from
their respective lists.
iii. Click Apply. The data table in the Relations tab shows only the relations that violate the physical cell ID allocation requirements.
To view only the important relations that violate the physical cell ID allocation requirements:
i.
ii. Under Include relations by type, select the relation types that you consider important and select some or all
of their characteristics from their respective lists.
iii. Click Apply. The data table in the Relations tab shows the relations according to the user-defined filter.
The Cells tab lists the current allocation plan and the following information:
The Distribution tab shows the histogram of the current allocation plan.
The exclamation mark icon ( ) indicates that the collision may or may not be a
problem depending on your network design rules and selected strategies. The
cross icon ( ) implies an error.
You can expand the right pane of the Resource Allocation Audit dialog box by
clicking the Hide button ( ). You can also resize the dialog box.
You can export the contents of table grids to TXT, CSV, and XML Spreadsheet files
by right-clicking the table and selecting Export from the context menu. For more
information on exporting data tables, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
You can select the columns to display in different tabs by right-clicking the table
and selecting Display Columns from the context menu. For more information, see
"Displaying and Hiding Columns" on page 80.
921
The top line contains global information about the current allocation (resource being audited and the total cost of
the current plan).
The left-hand side of the dialog box contains tabs with input parameters.
The right-hand side of the dialog box provides the audit results.
Existing Neighbours: Select this check box if you want the audit to take neighbours into account. Atoll can only
take neighbour relations into account if neighbours have already been allocated. For information on allocating
neighbours, see the User Manual.
Interference matrix: Select this check box if you want the audit to take interference matrices into account, and
select an interference matrix from the list. For Atoll to take interference matrices into account, they must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, and
imported in the Interference Matrices folder. For more information on interference matrices, see the User
Manual.
Reuse distance: Select this check box if you want the audit to take reuse distance into account. For cells that do
not have a reuse distance defined in their properties, the value entered next to Default will be used for the audit.
6. On the Constraints tab, you can set the constraints to take into account in the audit:
Allocation domain: You can choose Per cell to allocate PRACH RSIs from the PRACH RSI domains defined per cell,
you can choose to allocate from the Entire (0-838 / 0-138) domain, or you can choose Custom and enter the
Excluded resources to exclude some PRACH RSIs from the audit.
You can enter non-consecutive PRACH RSIs separated with a comma, or you can enter a range of PRACH RSIs separating the first and last one with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
Allocation strategies: You can select the Take into account frequency plan check box if you want the AFP to consider the frequency plan when determining PRACH RSI collisions.
7. On the right-hand side of the Resource Allocation Audit dialog box, Atoll displays the Total cost of the current PRACH
RSI allocation.
You can click the Weights button to open the Weights dialog box and modify the cost
component weights. For more information, see "Configuring Cost Component Weights" on
page 908.
8. Click Calculate. Atoll performs an audit of the current PRACH RSI plan. Any messages generated by the audit are
reported on the Events tab. The audit results are reported on the following tabs:
The Statistics tab provides overall statistics such as the numbers of various types of relations considered by the AFP
for PRACH RSI planning, the numbers of violated relations of each type, and the number of cells not satisfying the
domain compliance criteria.
The Relations tab lists all the relations between active and filtered cells in the document. The Relations tab can display
the following information:
922
AT332_UMR_E0
PRACH RSI overlap factor: The ratio of overlap between the PRACH RSIs used by Cell 1 and Cell 2.
Distance: The distance between Cell 1 and Cell 2.
Reuse distance: Reuse distance defined for Cell 1.
Distance relation importance: The importance of the distance-based relation between Cell 1 and Cell 2.
Interference Matrices: Whether an interference matrix relation exists ( ) between Cell 1 and Cell 2 or not.
Interference matrix importance: The importance of the interference matrix relation between Cell 1 and Cell 2.
Neighbour: Whether a neighbour relation exists ( ) between Cell 1 and Cell 2 or not.
Neighbour importance: The importance of the neighbour relation between Cell 1 and Cell 2.
Second order neighbour: Whether a second-order neighbour relation exists ( ) between Cell 1 and Cell 2 or not.
Second order neighbour importance: The importance of the second-order neighbour relation between Cell 1 and
Cell 2.
The data table in the Relations tab can be filtered. For example, you can view all the relations, only the relations
that violate the PRACH RSI allocation requirements, or apply a filter to exclude unimportant ones. To filter the relations listed in the Relations tab, click the Show button (
ii. Under Include relations by type, select all the options representing the relation types and select (All) from
their respective lists.
iii. Click Apply. The data table in the Relations tab shows all the relations between cells.
To view only the relations that violate the PRACH RSI allocation requirements:
i.
ii. Under Include relations by type, select all the options representing the relation types and select (All) from
their respective lists.
iii. Click Apply. The data table in the Relations tab shows only the relations that violate the PRACH RSI allocation
requirements.
To view only the important relations that violate the PRACH RSI allocation requirements:
i.
ii. Under Include relations by type, select the relation types that you consider important and select some or all
of their characteristics from their respective lists.
iii. Click Apply. The data table in the Relations tab shows the relations according to the user-defined filter.
The Cells tab lists the current allocation plan and the following information:
The Distribution tab shows the histogram of the current allocation plan.
You can expand the right pane of the Resource Allocation Audit dialog box by
clicking the Hide button ( ). You can also resize the dialog box.
You can export the contents of table grids to TXT, CSV, and XML Spreadsheet files
by right-clicking the table and selecting Export from the context menu. For more
information on exporting data tables, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
You can select the columns to display in different tabs by right-clicking the table
and selecting Display Columns from the context menu. For more information, see
"Displaying and Hiding Columns" on page 80.
923
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
Under Display Configuration, you can create a Filter to select which sites to display in the results. You can also display
the results grouped in the Network explorer 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 99;
for information on grouping, see "Advanced Grouping of Data Objects" on page 96; for information on sorting, see
"Advanced Sorting" on page 98.
4. Click the Conditions tab. 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.
The Server parameter is set to "Best Signal Level." You can enter an Overlap 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. Indoor losses are defined per frequency per
clutter class.
You can select the Take frequency plan into account check box to determine the cell identifier collisions based on
the current frequency plan of the network.
Under Identifier, you can select the cell identifier for which you want to calculate the coverage prediction.
Click Calculate to save the defined coverage prediction and perform the calculation immediately.
Click OK to save the defined coverage prediction without calculating it. You can calculate the prediction later by
clicking the Calculate button ( ) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Events viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
924
AT332_UMR_E0
noise which can be overcome by increasing the signal-to-noise ratio (SNR), co-channel interference cannot be countered by
increasing the carrier power of a transmitter. This is because an increase in carrier transmission power will increase the interference to neighbouring co-channel cells. To reduce co-channel interference, co-channel cells must be physically separated
sufficiently by a distance, called the reuse distance. For a network with a limited number of frequency channels, a large reuse
distance can guarantee a high QoS for the system, but the capacity will be decreased.
Another type of interference in LTE networks is adjacent channel interference. Adjacent channel interference results from
imperfect receiver filters which allow nearby frequencies to interfere with the used frequency channel. Adjacent channel
interference can be minimised through careful filtering and channel assignment.
In Atoll, a simulation is based on a realistic distribution of 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 downlink and uplink traffic loads, the uplink noise rise, the user throughputs, and so on. 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.
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.
For general information on studying network capacity in Atoll, see Chapter 6: Traffic and Capacity Planning.
This section covers the following topics for LTE networks:
LTE radio bearers: Radio bearers are used by the network for carrying information. The LTE Radio Bearer table lists all
the available radio bearers. You can create new radio bearers and modify existing ones by using the LTE Radio Bearer
table. For information on defining radio bearers, see "Defining LTE Radio Bearers" on page 964.
Services: Services are the various services, such as VoIP, FTP download, and so on, available to users. These services
can be either of the type "voice" or "data". For information on modelling end-user services, see "Modelling Services"
on page 241.
Mobility types: In LTE, information about receiver mobility is important to determine the users radio conditions and
throughputs. For information on modelling mobility types, see "Modelling Mobility Types" on page 247.
Terminals: In LTE, 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 modelling terminals, see "Modelling Terminals" on
page 249.
925
This section explains the specific mechanisms that are used to calculate LTE traffic simulations. For information on working
with traffic simulations in Atoll, see "Simulations" on page 265
926
AT332_UMR_E0
Carrier aggregation and coordinated multipoint transmission and reception (CoMP) are also taken into account. A user
may be connected to more than one server for carrier aggregation, CoMP, or both. For a user whose service, terminal,
and best server support carrier aggregation, the user throughput is improved according to its aggregation capabilities
and the available primary and secondary cells. For a user whose terminal and best server support CoMP, different
effects of the various CoMP modes are taken into account: coordinated scheduling decreases the interference
between coordinated CoMP servers, coherent joint transmission constructively combines the signals from the CoMP
servers resulting in an additive as well as probabilistic gain, and non-coherent joint transmission aggregates user
throughput over the CoMP servers who allocate resources to the CoMP user. For more information, see the Technical
Reference Guide.
4. Uplink Calculations
The uplink calculations include the calculation of PUSCH & PUCCH C/(I+N), determination of the best available bearer
for the PUSCH & PUCCH C/(I+N), uplink power control and uplink bandwidth allocation, resource allocation (RRM),
update of uplink noise rise values for cells, and calculation of user throughputs.
Enhanced inter-cell interference coordination (eICIC or time-domain ICIC) is performed on the uplink if ABS patterns
have been defined for cells. Interference calculation is based on the collisions between normal and blank subframes
used by the different cells. Frequency-domain inter-cell interference coordination is performed on the uplink if the
cell supports Static UL ICIC. Here, interference calculation is based on the probabilities of collision between the cellcentre and cell-edge resources used by the different cells.
Carrier aggregation and coordinated multipoint transmission and reception (CoMP) are also taken into account. A user
may be connected to more than one server for carrier aggregation, CoMP, or both. For a user whose service, terminal,
and best server support carrier aggregation, the user throughput is improved according to its aggregation capabilities
and the available primary and secondary cells. For a user whose terminal and best server support CoMP, coordinated
scheduling decreases the interference between coordinated CoMP servers. For more information, see the Technical
Reference Guide.
During uplink noise rise control, if the maximum uplink noise rise is higher than the actual noise rise for a cell, the maximum PUSCH C/(I+N) of its neighbour cells is increased by the difference. This allows the users served by the neighbour
cells to transmit at higher powers, i.e., they are allowed to create more interference. If the maximum uplink noise rise
is less than the actual noise rise for a cell, the maximum PUSCH C/(I+N) of its neighbour cells is decreased by the difference. This causes the users served by the neighbour cells to transmit at lower powers, i.e., they are forced to create
less interference. This can also lead to an increase or decrease in the number of users served by the neighbouring cells
in the uplink.
5. Radio Resource Management and Cell Load Calculation
Atoll uses an intelligent scheduling algorithm to perform radio resource management. The scheduling algorithm is
explained in detail in the Technical Reference Guide. The scheduler performs the following steps:
a. Determines the total amount of resources in each cell. The amounts of cell resources, specially at cell-edges, depend on the cells ABS pattern as well as on the number of cells cell-edge resource blocks defined for Static DL
inter-cell interference coordination in the cells frame configuration.
b. Selects the first N users from the users generated in the first step, where N is the Max number of users defined in
the cell properties.
c. Sorts the users in decreasing order by service priority.
The effective service priority is determined by the QCI priority and the user-defined service
priority. For example:
A service with QCI 1 will have a higher priority than any service with QCI 2, irrespective of the user-defined service priority.
A service with QCI 1 and user-defined service priority 1 will have a higher priority
than any service with QCI 1 and user-defined service priority 0.
The priorities of the different QoS class identifiers are defined by the 3GPP are listed in
"Modelling Services" on page 241.
d. Allocates the resources required to satisfy the minimum throughput demands of the users starting from the first
user (with the highest priority service) to the last user.
e. If resources still remain in the resource pool after this allocation, allocates resources to the users with maximum
throughput demands according to the used scheduling algorithm.
927
For their minimum throughput demands, LTE-A users are only scheduled on their primary
serving cells. At this stage, LTE-A users may be rejected due to "Scheduler Saturation" or
"Resource Saturation".
For their maximum throughput demands, LTE-A users are scheduled separately on each of
their serving cells (primary and secondary for carrier aggregation / non-coherent joint
transmission CoMP servers). Each users remaining throughput demand (maximum minimum) is distributed over each of its serving cells proportionally to the resources available
on each serving cell and to the users downlink effective RLC channel throughput or uplink
effective RLC allocated bandwidth throughput on each of its serving cell.
For carrier aggregation, only secondary cells whose PDSCH C/(I+N) is higher than or equal
to the secondary cell activation threshold defined in the terminal reception equipment
properties are activated for aggregation in downlink. Similarly, only secondary cells whose
PDSCH C/(I+N) and PUSCH C/(I+N) are both higher than or equal to the secondary cell activation threshold defined in the terminal and cell reception equipment properties, respectively, are activated for aggregation in uplink. User throughput demands are distributed
among the primary cell and active secondary cells.
Within each active serving cell, resource allocation for the maximum throughput demands
is carried out according to the scheduler used by that cell.
An alternate method for distributing LTE-A users remaining throughput demand over their
serving cells is also available through an option in the Atoll.ini file. For more information,
see the Administrator Manual.
The total user throughput is the sum of the throughputs obtained from each of the users
servers. For detailed information on RRM and scheduling, see the Technical Reference
Guide.
At the end of the simulations, active users can be connected in the direction corresponding to his activity status if the following
conditions are met:
Users may be rejected in step 2. for "No Coverage," step 3. or step 4. for "No Service," and step 5. for the following motives:
"Scheduler Saturation": The user is not among the users selected for resource allocation.
"Resource Saturation" : All of the cells resources were used up by other users or if, for a user active in uplink, the minimum uplink throughput demand was higher than the uplink allocated bandwidth throughput.
"Backhaul Saturation": The user was among the lowest priority service users served by a cell of a site whose defined
maximum S1 interface throughputs were exceeded while allocating resources for the minimum throughput demands.
Rejected LTE-A users are only counted in the statistics of their primary serving cells.
Connected LTE-A users are counted in the statistics of all their serving cells, primary and secondary.
11.4.2.2.1
928
AT332_UMR_E0
Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; radio resource allocation 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 throughput demands 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 throughput demands) is given.
The Sites tab: The Sites tab contains the following information per site:
Peak RLC cumulated throughput (DL) (kbps): The sum of peak RLC user throughputs of all the users connected in
the downlink in all the cells of the site.
Effective RLC cumulated throughput (DL) (kbps): The sum of effective RLC user throughputs of all the users connected in the downlink in all the cells of the site.
Cumulated application throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink in all the cells of the site.
Peak RLC cumulated throughput (UL) (kbps): The sum of peak RLC user throughputs of all the users connected in
the uplink in all the cells of the site.
Effective RLC cumulated throughput (UL) (kbps): The sum of effective RLC user throughputs of all the users connected in the uplink in all the cells of the site.
Cumulated application throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink in all the cells of the site.
Connection success rate (%): The percentage of users connected to any cell of the site with respect to the number
of users covered by the cells of the site.
Total number of connected users: The total number of users connected to any cell of the site in downlink, uplink,
or downlink and uplink both.
Number of connected users (DL+UL): The number of users connected to any cell of the site in downlink and uplink
both.
Number of connected users (DL): The number of users connected to any cell of the site in downlink.
Number of connected users (UL): The number of users connected to any cell of the site in uplink.
Number of connected users (inactive): The number of inactive users connected to any cell of the site.
No service: The number of users unable to connect to any cell of the site for which the rejection cause was "No
service."
No service (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was
"No service."
Scheduler saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Scheduler saturation."
Scheduler saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Scheduler saturation."
Resource saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Resource saturation."
Resource saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Resource saturation."
Backhaul saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Backhaul saturation."
Backhaul saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Backhaul saturation."
Peak RLC cumulated throughput (DL) (kbps) for each service: For each service, the sum of peak RLC user throughputs of the users connected in the downlink in all the cells of the site.
929
Effective RLC cumulated throughput (DL) (kbps) for each service: For each service, the sum of effective RLC user
throughputs of the users connected in the downlink in all the cells of the site.
Cumulated application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink in all the cells of the site.
Peak RLC cumulated throughput (UL) (kbps) for each service: For each service, the sum of peak RLC user throughputs of the users connected in the uplink in all the cells of the site.
Effective RLC cumulated throughput (UL) (kbps) for each service: For each service, the sum of effective RLC user
throughputs of the users connected in the uplink in all the cells of the site.
Cumulated application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink in all the cells of the site.
Connection success rate (%) for each service: For each service, the percentage of users connected to any cell of
the site with respect to the number of users covered by the cells of the site.
The Cells tab: The Cells tab contains the following information, per site and transmitter:
930
AT332_UMR_E0
Peak RLC cumulated throughput (DL) (kbps) for each service: For each service, the sum of peak RLC user throughputs of the users connected in the downlink.
Effective RLC cumulated throughput (DL) (kbps) for each service: For each service, the sum of effective RLC user
throughputs of the users connected in the downlink.
Cumulated application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink.
Peak RLC cumulated throughput (UL) (kbps) for each service: For each service, the sum of peak RLC user throughputs of the users connected in the uplink.
Effective RLC cumulated throughput (UL) (kbps) for each service: For each service, the sum of effective RLC user
throughputs of the users connected in the uplink.
Cumulated application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink.
Connection success rate (%) for each service: For each service, the percentage of users connected to the cell with
respect to the number of users covered by the cell.
The Mobiles tab: The Mobiles tab contains the following information:
X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the second
random trial).
Height: The height of the user terminal (antenna).
User profile: The assigned user profile. Atoll uses the assigned service and activity status to determine the terminal and the user profile.
Subscriber ID: The ID of the user if the user is generated from a subscriber list and not from a traffic map.
Subscriber list: The subscriber list of the user if the user is generated from a subscriber list and not from a traffic
map.
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.
Mobility: The mobility type assigned during the first random trial during the generation of the user distribution.
Activity status: The assigned activity status. It can be Active DL, Active UL, Active DL+UL, or Inactive.
Connection status: The connection status indicates whether the user is connected 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.
Clutter class: The code of the clutter class where the user is located.
Indoor: This field indicates whether indoor losses have been added or not.
Best server: The best server of the user.
Serving cell: The serving cell of the user.
Layer: The layer to which the serving cell belongs.
Multiserver Context: The reason of multiserver connection: carrier aggregation, CoMP, or both.
Number of servers (DL): The total number of aggregated or coordinated servers in downlink.
Number of servers (UL): The total number of aggregated or coordinated servers in uplink.
Azimuth: The orientation of the users terminal antenna in the horizontal plane. Azimuth is always considered
with respect to the North. Atoll points the user antenna towards its best server.
Downtilt: The orientation of the users terminal antenna in the vertical plane. Mechanical downtilt is positive
when it is downwards and negative when upwards. Atoll points the user antenna towards its best server.
Path loss (dB): The path loss from the best server calculated for the user.
2nd best server: The second best server of the user.
2nd best server path loss (dB): The path loss from the second best server calculated for the user.
3rd best server: The third best server of the user.
3rd best server path loss (dB): The path loss from the third best server calculated for the user.
RSRP (RS EPRE) (DL) (dBm): The RSRP (received reference signal energy per resource element) received at the user
location in the downlink.
RSSI (DL) (dBm): The RSSI received at the user location in the downlink.
RSRQ (DL) (dB): The RSRQ (reference signal received quality) at the user location in the downlink.
Received RS power (DL) (dBm): The reference signal level received at the user location in the downlink.
Received SS power (DL) (dBm): The SS signal level received at the user location in the downlink.
Received PBCH power (DL) (dBm): The PBCH signal level received at the user location in the downlink.
Received PDCCH power (DL) (dBm): The PDCCH signal level received at the user location in the downlink.
Received PDSCH power (DL) (dBm): The PDSCH signal level received at the user location in the downlink.
RS C/(I+N) (DL) (dB): The reference signal C/(I+N) at the user location in the downlink.
SS C/(I+N) (DL) (dB): The SS C/(I+N) at the user location in the downlink.
PBCH C/(I+N) (DL) (dB): The PBCH C/(I+N) at the user location in the downlink.
PDCCH C/(I+N) (DL) (dB): The PDCCH C/(I+N) at the user location in the downlink.
PDSCH C/(I+N) (DL) (dB): The PDSCH C/(I+N) at the user location in the downlink.
RS total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the user location in the
downlink on the reference signals.
SS & PBCH total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the user location
in the downlink on the SS and PBCH.
931
932
PDCCH total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the user location in the
downlink on the PDCCH.
PDSCH total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the user location in the
downlink on the PDSCH.
Bearer (DL): The highest LTE bearer available for the PDSCH C/(I+N) level at the user location in the downlink.
BLER (DL): The Block Error Rate read from the user terminals reception equipment for the PDSCH C/(I+N) level at
the user location in the downlink.
Diversity mode (DL): The diversity mode used by the cell in downlink for the user.
Peak RLC channel throughput (DL) (kbps): The maximum RLC channel throughput attainable using the highest
bearer available at the user location in the downlink.
Effective RLC channel throughput (DL) (kbps): The effective RLC channel throughput attainable using the highest
bearer available at the user location in the downlink. It is calculated from the peak RLC throughput and the BLER.
Application channel throughput (DL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, and so on). It is calculated from the effective RLC throughput, the throughput
scaling factor of the service and the throughput offset.
Peak RLC user throughput (DL) (kbps): The maximum RLC user throughput attainable using the highest bearer
available at the user location in the downlink.
Effective RLC user throughput (DL) (kbps): The effective RLC user throughput attainable using the highest bearer
available at the user location in the downlink. It is calculated from the peak RLC throughput and the BLER.
Application user throughput (DL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, and so on). It is calculated from the effective RLC throughput, the throughput
scaling factor of the service and the throughput offset.
Received PUSCH & PUCCH power (UL) (dBm): The PUSCH & PUCCH signal level received at the serving transmitter
from the user terminal in the uplink.
PUSCH & PUCCH total noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the serving
transmitter of the user in the uplink on the PUSCH.
PUSCH & PUCCH C/(I+N) (UL) (dB): The PUSCH & PUCCH C/(I+N) at the serving transmitter of the user in the
uplink.
Bearer (UL): The highest LTE bearer available for the PUSCH & PUCCH C/(I+N) level at the serving transmitter of
the user in the uplink.
BLER (UL): The Block Error Rate read from the serving cells reception equipment for the PUSCH & PUCCH C/(I+N)
level at the serving transmitter of the user in the uplink.
Diversity mode (UL): The diversity mode used by the cell in uplink for the user.
Transmission power (UL) (dBm): The transmission power of the user terminal after power control in the uplink.
Allocated bandwidth (UL) (No. of frequency blocks): The number of frequency blocks allocated to the user in the
uplink by the eNode-B.
Peak RLC channel throughput (UL) (kbps): The maximum RLC channel throughput attainable using the highest
bearer available at the user location in the uplink.
Effective RLC channel throughput (UL) (kbps): The effective RLC channel throughput attainable using the highest
bearer available at the user location in the uplink. It is calculated from the peak RLC throughput and the BLER.
Application channel throughput (UL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, and so on). It is calculated from the effective RLC throughput, the throughput
scaling factor of the service and the throughput offset.
Peak RLC allocated bandwidth throughput (UL) (kbps): The maximum RLC throughput attainable for the number
of frequency blocks allocated to the user using the highest bearer available at the user location in the uplink.
Effective RLC allocated bandwidth throughput (UL) (kbps): The effective RLC throughput attainable for the
number of frequency blocks allocated to the user using the highest bearer available at the user location in the
uplink. It is calculated from the peak RLC throughput and the BLER.
Application allocated bandwidth throughput (UL) (kbps): The application throughput is the net throughput
without coding (redundancy, overhead, addressing, and so on). It is calculated from the effective RLC throughput,
the throughput scaling factor of the service and the throughput offset.
Peak RLC user throughput (UL) (kbps): The maximum RLC user throughput attainable using the highest bearer
available at the user location in the uplink.
Effective RLC user throughput (UL) (kbps): The effective RLC user throughput attainable using the highest bearer
available at the user location in the uplink. It is calculated from the peak RLC throughput and the BLER.
Application user throughput (UL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, and so on). It is calculated from the effective RLC throughput, the throughput
scaling factor of the service and the throughput offset.
AT332_UMR_E0
Calculated radio parameters (signal levels, C/(I+N), and so on) corresponding to:
Aggregated over all the servers (carrier aggregation and non-coherent joint
transmission CoMP),
Corresponding to the composite signal quality due to signal combination in
joint transmission CoMP.
To display detailed results for LTE-A users, select Actions > Detailed Display. The Mobiles
tab displays one line per aggregated or coordinated server showing the calculated radio
parameters (signal levels, C/(I+N), and so on) and throughputs corresponding to each serving cell. For coherent joint transmission CoMP, however, the radio signal quality values as
well as throughputs are the same for all combined servers, and the throughputs are not
aggregated between servers.
Moreover, the throughput of any rejected user is zero.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
11.4.2.2.2
The parameters related to the clutter classes, including the default values.
Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; radio resource allocation 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 throughput demands that all users could theoretically generate are provided.
933
The breakdown per service (total number of users, number of users per activity status, and UL and DL throughput demands) is given.
The Sites (Average) tab: The Sites (Average) tab contains the following average information per site:
Peak RLC cumulated throughput (DL) (kbps): The sum of peak RLC user throughputs of all the users connected in
the downlink in all the cells of the site.
Effective RLC cumulated throughput (DL) (kbps): The sum of effective RLC user throughputs of all the users connected in the downlink in all the cells of the site.
Cumulated application throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink in all the cells of the site.
Peak RLC cumulated throughput (UL) (kbps): The sum of peak RLC user throughputs of all the users connected in
the uplink in all the cells of the site.
Effective RLC cumulated throughput (UL) (kbps): The sum of effective RLC user throughputs of all the users connected in the uplink in all the cells of the site.
Cumulated application throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink in all the cells of the site.
Connection success rate (%): The percentage of users connected to any cell of the site with respect to the number
of users covered by the cells of the site.
Total number of connected users: The total number of users connected to any cell of the site in downlink, uplink,
or downlink and uplink both.
Number of connected users (DL+UL): The number of users connected to any cell of the site in downlink and uplink
both.
Number of connected users (DL): The number of users connected to any cell of the site in downlink.
Number of connected users (UL): The number of users connected to any cell of the site in uplink.
No service: The number of users unable to connect to any cell of the site for which the rejection cause was "No
service."
No service (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was
"No service."
Scheduler saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Scheduler saturation."
Scheduler saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Scheduler saturation."
Resource saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Resource saturation."
Resource saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Resource saturation."
Backhaul saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Backhaul saturation."
Backhaul saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Backhaul saturation."
Peak RLC cumulated throughput (DL) (kbps) for each service: For each service, the sum of peak RLC user throughputs of the users connected in the downlink in all the cells of the site.
Effective RLC cumulated throughput (DL) (kbps) for each service: For each service, the sum of effective RLC user
throughputs of the users connected in the downlink in all the cells of the site.
Cumulated application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink in all the cells of the site.
Peak RLC cumulated throughput (UL) (kbps) for each service: For each service, the sum of peak RLC user throughputs of the users connected in the uplink in all the cells of the site.
Effective RLC cumulated throughput (UL) (kbps) for each service: For each service, the sum of effective RLC user
throughputs of the users connected in the uplink in all the cells of the site.
Cumulated application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink in all the cells of the site.
Connection success rate (%) for each service: For each service, the percentage of users connected to any cell of
the site with respect to the number of users covered by the cells of the site.
The Cells (Average) tab: The Cells (Average) tab contains the following average information per cell:
934
Traffic load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation.
Cell-edge Traffic Ratio (DL) (%): The percentage of the downlink traffic load that corresponds to the cell-edge
users.
Traffic load (UL) (%): The traffic loads of the cells calculated on the uplink during the simulation.
AT332_UMR_E0
UL noise rise (dB): The noise rise of the cells calculated on the uplink during the simulation.
ICIC UL noise rise (dB): The noise rise of the cells calculated on the uplink during the simulation for the cell-edge
users.
Max PUSCH C/(I+N) (dB): The maximum PUSCH C/(I+N) for the cell. It is updated during uplink noise rise control
based on the maximum noise rise constraints of the neighbouring cells.
Angular distribution of interference (AAS): The simulation results generated for transmitters using a smart
antenna. These results are the angular distributions of the downlink traffic power spectral density.
AAS usage (DL) (%): The percentage of the downlink traffic load that corresponds to the traffic carried by the smart
antennas.
Number of co-scheduled MU-MIMO users (DL): The average number of MU-MIMO users that share the same
resources on the downlink.
Number of co-scheduled MU-MIMO users (UL): The average number of MU-MIMO users that share the same
resources on the uplink.
Peak RLC cumulated throughput (DL) (kbps): The sum of peak RLC user throughputs of all the users connected in
the downlink.
Effective RLC cumulated throughput (DL) (kbps): The sum of effective RLC user throughputs of all the users connected in the downlink.
Cumulated application throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink.
Peak RLC cumulated throughput (UL) (kbps): The sum of peak RLC user throughputs of all the users connected in
the uplink.
Effective RLC cumulated throughput (UL) (kbps): The sum of effective RLC user throughputs of all the users connected in the uplink.
Cumulated application throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink.
Connection success rate (%): The percentage of users connected to the cell with respect to the number of users
covered by the cell.
Total number of connected users: The total number of users connected to the cell in downlink, uplink, or downlink
and uplink both.
Number of connected users (DL+UL): The number of users connected to the cell in downlink and uplink both.
Number of connected users (DL): The number of users connected to the cell in downlink.
Number of connected users (UL): The number of users connected to the cell in uplink.
No service: The number of users unable to connect to the cell for which the rejection cause was "No service."
No service (%): The percentage of users unable to connect to the cell for which the rejection cause was "No service."
Scheduler saturation: The number of users unable to connect to the cell for which the rejection cause was "Scheduler saturation."
Scheduler saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Scheduler saturation."
Resource saturation: The number of users unable to connect to the cell for which the rejection cause was
"Resource saturation."
Resource saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Resource saturation."
Backhaul saturation: The number of users unable to connect to the cell for which the rejection cause was "Backhaul saturation."
Backhaul saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Backhaul saturation."
Peak RLC cumulated throughput (DL) (kbps) for each service: For each service, the sum of peak RLC user throughputs of the users connected in the downlink.
Effective RLC cumulated throughput (DL) (kbps) for each service: For each service, the sum of effective RLC user
throughputs of the users connected in the downlink.
Cumulated application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink.
Peak RLC cumulated throughput (UL) (kbps) for each service: For each service, the sum of peak RLC user throughputs of the users connected in the uplink.
Effective RLC cumulated throughput (UL) (kbps) for each service: For each service, the sum of effective RLC user
throughputs of the users connected in the uplink.
Cumulated application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink.
Connection success rate (%) for each service: For each service, the percentage of users connected to the cell with
respect to the number of users covered by the cell.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
935
The parameters related to the clutter classes, including the default values.
Coverage by C/(I+N) Level: For information on making a downlink or uplink coverage by C/(I+N) level, see "Studying
Interference and C/(I+N) Levels" on page 882.
Service Area Analysis: For information on making a downlink or uplink service area analysis, see "Studying Downlink
and Uplink Service Areas" on page 884.
Effective Service Area Analysis: For information on making an effective service area analysis, see "Studying the Effective Service Area" on page 886.
Coverage by Throughput: For information on making a downlink or uplink coverage by throughput, see "Making a
Coverage Prediction by Throughput" on page 888.
Coverage by Quality Indicator: For information on making a downlink or uplink coverage by quality indicator, see
"Making a Coverage Prediction by Quality Indicator" on page 891.
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:
1. Click the Conditions tab.
2. From the Load conditions list, select the simulation or group of simulations on which you want to base the coverage
prediction.
936
AT332_UMR_E0
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.
ACP uses user-defined objectives to evaluate the optimisation, as well as to calculate its implementation cost. Once you have
defined the objectives and the network parameters to be optimised, ACP uses an efficient global search algorithm to test
many network configurations and propose the reconfigurations that best meet the objectives. ACP presents the changes
ordered from the most to the least beneficial, allowing phased implementation or implementation of just a subset of the
suggested changes.
ACP is technology-independent and can be used to optimise networks using different radio access technologies. Chapter 17:
Automatic Cell Planning explains how you configure the ACP module, how you create and run an optimisation setup, and how
you can view the results of an optimisation. In this section, only the concepts specific to LTE networks are explained:
LTE RSRP
LTE RSRQ
You can also create the following objectives from the context menu of Objectives in the left-hand pane of the Objectives tab:
LTE RS Coverage
LTE RS CINR
LTE RSSI
LTE PDSCH CINR
LTE RLC Peak Rate
LTE 1st-Nth Difference
Custom Coverage
You define the optimisation objectives using the Objectives tab of the ACP Setup dialog box. For information on setting objective parameters, see "Setting Objective Parameters" on page 1329.
937
In projects using LTE, either alone, or in a co-planning or multi-RAT mode, the following Quality parameters are proposed in
the Pixel Rules frame of the objectives properties pages:
Signal level
RS C
RS CN
RSRP
RS CINR
RSRQ
Overlap
Best Server Distance
RSSI
PDSCH CINR
RLC Peak Rate
1st-2nd Difference
1st-Nth Difference
If you base the evaluation of a quality analysis prediction on a calculated Atoll prediction, ACP will use the display settings of the calculated Atoll prediction in the
quality analysis prediction calculated for that objective.
If you saved the display settings of a quality analysis prediction as defaults, or if you
are using a configuration file for ACP, these display settings will be used by default
and will override the display settings of the calculated Atoll prediction. For more
information on changing the display settings of a quality analysis prediction, see
"Changing the Display Properties of ACP Predictions" on page 1379.
Signal Level: Click this parameter to define in the right-hand pane how ACP will evaluate coverage by signal level.
Base prediction settings on > "Coverage by Signal Level (DL)": ACP will evaluate coverages by signal level based
on the parameters used to calculate the selected "Coverage by Signal Level (DL)" prediction in Atoll.
Only the coverage predictions displaying a "Best Signal Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": if you select this option, you can Enable shadowing margin
and define a Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no
clutter information available, default values are used.
RS C & RSRP: Click this parameter to define in the right-hand pane how ACP will evaluate coverage by RS C or RSRP.
Base prediction settings on > "Effective Signal Analysis (DL)": ACP will evaluate coverages by RS C or RSRP based
on the parameters used to calculate the selected "Effective Signal Analysis (DL)" prediction in Atoll.
Only the Atoll predictions displaying an "RS Signal Level" or "RSRP Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": if you select this option, you can Enable shadowing margin
and define a Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no
clutter information available, default values are used. Additionally, you can specify the following:
Service and Terminal that will be used during the calculation of RS C or RSRP through gain and losses (i.e., the
service body loss, the gain and loss of the terminal antenna, and the terminal noise factor).
RS CN: Click this parameter to define in the right-hand pane how ACP will evaluate coverage by RS CN.
Base prediction settings on > "Effective Signal Analysis (DL)": ACP will evaluate coverages by RS CN based on the
parameters used to calculate the selected "Effective Signal Analysis (DL)" prediction in Atoll.
Only the Atoll predictions displaying an "RS C/N Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": if you select this option, you can Enable shadowing margin
and define a Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no
clutter information available, default values are used. Additionally, you can specify the following:
Service and Terminal that will be used during the calculation of RS CN through gain and losses (i.e., the service
body loss, the gain and loss of the terminal antenna, and the terminal noise factor).
RS CINR & RSRQ: Click this parameter to define in the right-hand pane how ACP will evaluate coverage by RS CINR or
RSRQ.
938
AT332_UMR_E0
Base prediction settings on > "Coverage by C/(I+N) Level (DL)": ACP will evaluate coverages by RS CINR or RSRQ
based on the parameters used to calculate the selected "Coverage by C/(I+N) Level (DL)" prediction in Atoll.
Only the Atoll predictions displaying an "RS C/(I+N) Level" or "RSRQ Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": if you select this option, you can Enable shadowing margin
and define a Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no
clutter information available, default values are used. Additionally, you can specify the following:
Service and Terminal that will be used during the calculation of RS CINR or RSRQ through gain and losses (i.e.,
the service body loss, the gain and loss of the terminal antenna, and the terminal noise factor).
Calculation Method for RS CINR & RSRQ (select Consider frequency plan or Ignoring frequency plan).
RSSI: Click this parameter to define in the right-hand pane how ACP will evaluate coverage by RSSI.
Base prediction settings on > "Coverage by C/(I+N) Level (DL)": ACP will evaluate coverages by overlapping based
on the parameters used to calculate the selected "Coverage by C/(I+N) Level (DL)" prediction in Atoll.
Only the Atoll predictions displaying an "RSSI Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": if you select this option, you can Enable shadowing margin
and define a Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no
clutter information available, default values are used. Additionally, you can specify the following:
Service and Terminal that will be used during the calculation of RSSI through gain and losses (i.e., the service
body loss, the gain and loss of the terminal antenna, and the terminal noise factor).
Calculation Method for RSSI (select Consider frequency plan or Ignoring frequency plan).
PDSCH CINR: Click this parameter to define in the right-hand pane how ACP will evaluate coverage by PDSCH CINR.
Base prediction settings on > "Coverage by Throughput (DL)": ACP will evaluate coverages by overlapping based
on the parameters used to calculate the selected "Coverage by Throughput (DL)" prediction in Atoll.
Only the Atoll predictions displaying a "PDSCH C/(I+N) Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": If you select this option, you can Enable shadowing margin
and define a 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. Additionally, you can specify:
Service, Terminal, and Mobility that will be used during the calculation of PDSCH CINR through gain and losses
(i.e., the service body loss, the gain and loss of the terminal antenna, and the terminal noise factor),
Calculation Method for PDSCH CINR (select Consider frequency plan or Ignoring frequency plan).
RLC Peak Rate: Click this parameter to define in the right-hand pane how ACP will evaluate coverage by RLC Peak Rate.
Base prediction settings on > "Coverage by Throughput (DL)": ACP will evaluate coverages by RLC Peak Rate
based on the parameters used to calculate the selected "Coverage by Throughput (DL)" prediction in Atoll.
Only the Atoll predictions displaying a "Peak RLC Channel Throughput" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": if you select this option, the evaluation is done using the
parameters defined for PDSCH CINR.
Overlap / 1st-Nth: Click this parameter to define in the right-hand pane how ACP will evaluate coverage by overlapping zones or by 1st-Nth difference.
Overlap
Base prediction settings on > "Overlapping Zones (DL)": ACP will evaluate coverages by overlapping based on
the parameters used to calculate the selected "Overlapping Zones (DL)" prediction in Atoll.
Only the Atoll predictions displaying a "Number of Servers" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": If you select this option, you can set a Minimum signal
level and a Threshold margin.
1st-Nth
Base prediction settings on > "Overlapping Zones (DL)": ACP will evaluate coverages by 1st-Nth difference
based on the parameters used to calculate the selected "Overlapping Zones (DL)" prediction in Atoll.
Since there is no Atoll prediction type equivalent to ACPs LTE 1st-Nth Difference objective, the parameters
recovered by ACP from the selected Atoll prediction are limited to the minimum signal level and the shading.
The number of servers must always be specified manually next to No. servers.
Base prediction settings on > "Manual configuration": If you select this option, specify a Minimum signal
level and the No. servers.
In both cases, the value you specify next to No. servers determines "Nth" in the LTE 1st-Nth Difference objective. For instance if you set No. servers to 4, then the "1st-4th Difference" quality parameter will be automatically selected by default in the Quality column of the LTE 1st-Nth Difference properties page.
- Allowed values for No. servers range from 3 to 100, with only one value available per technology.
- The "1st-2nd Difference" quality parameter (based on No. servers = 2) is provided by default.
939
Figure 11.23: ACP Quality Analysis Prediction Types for an LTE Network
ACP quality analysis predictions are equivalent to some of Atolls coverage predictions. The following table lists the quality
analysis predictions available in ACP for LTE and the equivalent LTE coverage predictions in Atoll.
Signal Level
RS C
RSRP
RS CINR
RSRQ
Overlap
RSSI
PDSCH CINR
1st-Nth Difference
N/A
(1) For more information, see "Studying Signal Level Coverage for a Single Base Station" on page 876.
(2) For more information, see "Studying Interference and C/(I+N) Levels" on page 882.
(3) For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 878.
(4) For more information, see "Making a Coverage Prediction by Throughput" on page 888.
Making these predictions 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 predictions display results very similar to those
that Atoll would display if you committed the optimisation results and calculated Atoll coverage predictions, however, before
940
AT332_UMR_E0
basing any decision to commit the optimisation results on the predictions 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 overlapping zones prediction.
ACP generated predictions 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 frequency band optimisation is supported in LTE. However the predictions are provided separately for the
requested frequency band.
Even after committing the optimisation results, differences can remain between the ACP predictions and the predictions resulting from Atoll coverage predictions.
You can view the exact RS coverage value on any pixel by letting the pointer rest over the pixel. The RS coverage value is then
displayed in a tip text.
For ACP overlapping zones predictions, you can:
For each network quality coverage prediction, ACP offers a prediction showing the initial network state, the final network
state, and a prediction showing the changes between the initial and final states.
Optimise Max Power with Varying RS EPRE: In this mode, the Max Power is optimised with a varying RS EPRE. Both
values are mutually dependent. The Max Power check box appears by default on the Reconfiguration > LTE cells vertical tab of new ACP setups.
As a result, the initial and final values of Max Power appear on the Sectors and Commit tabs of ACP optimisations.
Optimise RS EPRE with Varying Max Power: In this mode, the RS EPRE is optimised with a varying Max Power. Both
are mutually dependent. When you display the Reconfiguration > LTE cells vertical tab in the properties of a new ACP
setup:
the RS EPRE check box replaces the Max Power check box
the RS EPRE (dBm) and Max Power (dBm) columns are inverted
As a result, the initial and final values of RS EPRE appear on the Sectors and Commit tabs of ACP optimisations.
Optimise Max Power (or RS EPRE) with Fixed RS EPRE (or Max Power): In this mode, you can choose to:
strictly optimise the Max Power without affecting the RS EPRE initial values
or strictly optimise the RS EPRE without affecting the Max Power initial values
If you now display the Reconfiguration > LTE cells vertical tab in the properties of a new ACP setup:
As a result, the initial and final values of Max Power (or RS EPRE) appear on the Sectors and Commit tabs of ACP optimisations
To specify the ACP strategy for reconfiguring LTE cells:
1. Open the LTE Radio Network Settings Properties dialog box (see "Modifying Global Network Settings" on page 962).
2. Select the Global Parameters tab and click the Advanced button. The Advanced Parameters dialog box appears.
3. Under Downlink transmit power calculation, select one of the following settings:
To optimise RS EPRE with varying max power, set RS EPRE to "1- User-defined".
To optimise max power or RS EPRE with a fixed RS EPRE, set RS EPRE to "4 - Independent of max power".
941
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). Cells may be identified by their IDs or physical cell IDs.
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 with 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:
1. In the Network explorer, right-click the Drive Test Data folder and select Import from the context menu. The Open
dialog box appears.
2. Select the file or files that you want to open. You can import one or several files.
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.
3. Click Open. The Import of Measurement Files dialog box appears.
Files with the extension PLN, as well as some FMT files (created with old versions of TEMS)
are imported directly into Atoll; you will not be asked to define the data structure using
the Import of Measurement Files dialog box.
4. 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 dialog box. If you do not have
an import configuration, continue with step 5.
a. Under Import configuration, select an import configuration from the Import configuration list.
b. Continue with step 8.
942
AT332_UMR_E0
When importing a drive test data path file, existing configurations are available in
the Files of type list of the Open dialog box, 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.
5. 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
necessary.
Under Receiver, set the Height of the receiver antenna and the Gain and Losses.
Under Measurement conditions,
Figure 11.24: The Setup tab of the Import of Measurement Files dialog box
a. In the File area, 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 dialog box 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 that uses cells IDs as a cell identifier:
943
i.
ii. In the By ID identifier box, enter a string found in the column name that identifies the scanned cells IDs. For
example, if the string "ID" is found in the column names that identify the cell IDs of scanned cells, enter it here.
Atoll will then search for the column with this string in the column name.
e. If you are importing data that uses a physical cell ID as a cell identifier:
i.
ii. In the By physical cell ID identifier box, enter a string found in the column name identifying the physical cell
IDs of scanned cells. For example, if the string "PCI" is found in the column names identifying the physical cell
IDs of scanned cells, enter it here. Atoll will then search for the column with this string in the column name.
iii. Select the Physical cell ID format, Decimal or Hexadecimal.
iv. Under Additional identifier, you can select an additional identifier if the drive test data file being imported
contains additional columns for cell identification. You can select either Channel number or Frequency as additional identifier and the column containing the additional identifier of the scanned cells. If you select Frequency as additional identifier, you must also define the frequency unit used in the drive test data being
imported.
f. Click OK to close the Drive Test Data Setup dialog box.
If you have correctly entered the information under File on the Setup tab, and the
necessary values in the Drive Test Data Setup dialog box, Atoll should recognise 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>". Columns marked with
"<Ignore>" will not be imported.
The data in the file must be structured so that the column identifying the physical
cell ID is placed before the data columns for each cell. Otherwise Atoll will not be
able to properly import the file.
7. 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 dialog box appears.
b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atolls installation folder. In
case you cannot write into that folder, you can click Browse to choose a different location.
c. Enter a Configuration name and an Extension of the files that this import configuration will describe (for example,
"*.txt").
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 can select this
import configuration from the Configuration list.
You do not need to complete the import procedure to save the import configuration and have it available for future use.
When importing a 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 dialog box.
You can delete an existing import configuration by selecting the import configuration under Import configuration and clicking the Delete button.
8. Click Import, if you are only importing a single file, or Import all, if you are importing more than one file. The drive test
data is imported into the current Atoll document.
944
AT332_UMR_E0
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, the Shadings dialog box opens in which you can define the
following display for each single point of the measurement path:
You can, for example, display a signal level in a certain colour, choose a symbol for each transmitter (a circle, triangle,
cross, and so on) 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 in the Network explorer 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 dialog box and select Save or Load from
the Display Configuration submenu.
"Filtering Measurement Points Along Drive Test Data Paths" on page 945
"Predicting the Signal Level on Drive Test Data Points" on page 946
"Creating Coverage Predictions on Drive Test Data Paths" on page 947
"Displaying Statistics Over a Drive Test Data Path" on page 947
"Extracting a Field From a Drive Test Data Path for a Transmitter" on page 948
"Analysing Measurement Variations Along the Path" on page 948.
945
You can filter out unreliable measurement points from the drive test data path either geographically, by filtering by clutter
classes and the focus zone, or using an advanced filter.
To filter out measurement points by clutter class:
1. In the Network explorer, expand the Drive Test Data folder, right-click the drive test data path on which you want to
filter out measurement points, and select Filter from the context menu. The Drive Test Data Filter dialog box appears.
2. Under Clutter classes, clear the check boxes of the clutter classes you want to exclude. Measurement points located
on the excluded clutter classes will be filtered out.
3. If you want to use the focus zone as part of the filter, select the Use focus zone to filter check box. Measurement
points located outside the focus zone will be filtered out.
4. If you want to permanently delete the measurement points outside the filter, select the Delete points outside the
filter check box.
You can apply a filter on all the drive test data paths in the Drive Test Data folder
by selecting Filter from the context menu of the folder.
If you want to use the measurement points that you permanently deleted, you
must import the drive test data path again.
Figure 11.25: Selecting Measured Signal Levels for which Errors will be Calculated
4. Click OK. A new point prediction is created for the selected drive test data path.
5. Right-click the drive test data path. The context menu appears.
6. Select Calculations > Calculate All the Predictions from the context menu.
946
AT332_UMR_E0
If you chose to have Atoll calculate the errors between measured and predicted signal levels, new columns are added to the
drive test data table for the predicted point signal level from the serving cell and the errors between the measured and
predicted values.
Figure 11.26: Drive Test Data table after Point Signal Level Prediction (with error calculations)
New columns are also added for the predicted point signal level from each neighbour cell and the errors between the
predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For
more information on the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 948.
The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main
matrix. For more information on propagation models, see Chapter 4: Radio Calculations and Models.
947
11.6.4.5 Extracting a Field From a Drive Test Data Path for a Transmitter
You can extract information for a selected transmitter from a field of a drive test data path. The extracted information is available in a new column in the drive test data table.
To extract a field from a drive test data path:
1. In the Network explorer, expand the Drive Test Data folder, right-click the drive test data from which you want to
extract a field, and select Focus on a Transmitter from the context menu. The Field Selection for a Given Transmitter
dialog box appears.
2. Under On the transmitter, select the transmitter for which you want to extract a field.
3. Under For the fields, select the fields that you want to extract for the selected transmitter.
4. Click OK. A new column is created in the drive test data path table for the selected transmitter and with the selected
values.
948
AT332_UMR_E0
Select the check box next to each field you want to display in the Drive Test Data analysis tool.
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 dialog box.
You can change the display status or the colour of more than one field at the same time by
selecting several fields. 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 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 analysis tool.
4. You can display the data in the drive test data path in the following ways:
The drive test data path appears in the map window as an arrow pointing towards the best server (see Figure 11.27
on page 948) in the same colour as the transmitter.
5. You can display a secondary 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 dialog box. You select the value to be
displayed from the right-hand list at the top of the Drive Test Data analysis tool. The values are displayed in the colour
defined in the Display Parameters dialog box.
6. You can zoom in on the graph displayed in the Drive Test Data analysis tool in the following ways:
Zoom in or out:
i.
Right-click the Drive Test Data analysis tool. The context menu appears.
Right-click the Drive Test Data analysis tool on one end of the range of data you want to zoom in on. The context menu appears.
949
11.6.7 Printing and Exporting the Drive Test Data Analysis Tool
You can print and export the contents of the Drive Test Data analysis tool.
To print or export the contents of the Drive Test Data analysis tool:
1. Select Tools > Drive Test Data from the menu bar. The Drive Test Data analysis tool appears.
2. Define the display parameters and zoom level as explained in "Analysing Measurement Variations Along the Path" on
page 948.
3. Right-click the Drive Test Data analysis tool. The context menu appears.
To print the Drive Test Data analysis tool, select Print from the context menu.
To export the Drive Test Data analysis tool, select Copy from the context menu, then paste.
950
AT332_UMR_E0
bours 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 the Atoll Automatic Cell Planning (ACP) module.
This section covers the following topics:
Select File > Open or File > New > From an Existing Database.
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.
951
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 an LTE document).
To display sites from the linked document in the main document:
1. Click the map window of the linked document. The linked document map window becomes active and the explorer
window shows the contents of the main document and the linked folders from the linked document.
2. In the Network explorer, right-click the Sites folder and 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, DTM, and so on., 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, because working document is the main document, any changes made in the main document are not automatically taken into account in the linked document.
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 107. 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
"Associating a Tip Text to an Object" on page 54.
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 "Changing the Order of
Layers" on page 51.
Figure 11.29 shows an example of LTE transmitters with labels and displayed in the Legend window, and GSM transmitter data
displayed in a tip text.
952
AT332_UMR_E0
When you click the Calculate button, Atoll first 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 and Unlocking Coverage Predictions" on page 207.
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 recalculate all path loss matrices before calculating coverage predictions:
1. Click the Force Calculate button (
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.
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.
11.7.2.2.1
953
The recommended process for analysing coverage areas, and the effect of parameter modifications in one on the other, is as
follows:
1. Create and calculate a Coverage by Transmitter (DL) (best server with 0 dB overlap margin) coverage prediction and
a Coverage by Signal Level (DL) coverage prediction in the main document. For more information, see "Making a
Coverage Prediction by Transmitter" on page 877 and "Making a Coverage Prediction by Signal Level" on page 877.
2. Create and calculate a Coverage by Transmitter (DL) (best server with 0 dB overlap margin) coverage prediction and
a Coverage by Signal Level (DL) 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 dialog box.
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 951.
5. Optimise the main network by changing parameters such as antenna azimuth and tilt or the cell 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 954 and "Studying Differences Between Coverage Areas" on page 955.
7. Calculate the linked coverage predictions again to study the effects of the changes on the linked coverage predictions.
11.7.2.2.2
11.7.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.
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 11.17). 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.
11.7.2.2.4
954
AT332_UMR_E0
11.7.2.2.5
955
Figure 11.31: New sector Before and after applying the configuration
The azimuths and mechanical tilts of secondary antennas and remote antennas are not
included when you select Refresh Folder Configuration and must be set up manually.
When Use coverage conditions is not selected, the defined Distance is used to allocate neighbours to a reference
transmitter.
When Use coverage conditions is selected, click Define for LTE to open the Coverage Conditions dialog box:
Resolution: Enter the resolution to be used to calculate cell coverage areas during automatic neighbour allocation.
Margin: Enter a handover margin.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this check box to take indoor losses into account in calculations. Indoor losses are defined
per frequency per clutter class.
Co-site neighbours: cells located on the same site as the reference transmitter will automatically be considered as
neighbours. A transmitter/cell with no antenna cannot be considered as a co-site neighbour.
Exceptional pairs: Select this check box to force the neighbour relations defined in the Inter-technology Exceptional
pairs table. For more information, see "Exceptional Pairs" on page 223.
956
Cause
Description
When
Distance
Coverage
AT332_UMR_E0
Cause
Description
When
Co-Site
Exceptional Pair
Exceptional pairs
is selected
Existing
Click Run to run the optimisation immediately. For information on running the optimisation, see "Running an Optimisation Setup" on page 1359. For information on the optimisation results, see "Viewing Optimisation Results" on
page 1362.
Click the Create Setup button to save the defined optimisation to be run later.
957
958
Name: Enter a name for the frequency band, for example, "2.1 GHz - 10 MHz." Each LTE frequency band has a specific channel width. Mentioning the channel width in the frequency band name is a good approach. This name will
appear in other dialog boxes when you select a frequency band.
Channel width (MHz): Enter the width for each channel in the frequency band.
Inter-channel spacing (MHz): Enter the spacing between any two consecutive channels in the frequency band.
First channel: Enter the number of the first channel in this frequency band.
Last channel: Enter the number of the last channel in this frequency band. If this frequency band has only one carrier, enter the same number as entered in the First channel field.
Step: Enter the step between any two consecutive channel numbers in the frequency band.
Excluded channels: Enter the channel numbers which do not constitute the frequency band. You can enter nonconsecutive channel numbers separated with a comma, or you can enter a range of channel numbers separating
the first and last index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
Start frequencies (MHz): Enter the start frequency for TDD frequency bands, and the downlink and the uplink start
frequencies for FDD frequency bands.
Adjacent channel suppression factor (dB): Enter the adjacent channel interference suppression factor in dB. Interference received from adjacent channels is reduced by this factor during the calculations.
Number of frequency blocks: Enter the number of frequency blocks (i.e., the number of resource block widths in
the frequency domain) used for the channel bandwidth.
Sampling frequency (MHz): Enter the sampling frequency used for the channel bandwidth.
Duplexing method: Select the duplexing method used in the frequency band from the list.
AT332_UMR_E0
TDD subframe configuration (see "Cell Properties" on page 848) is hidden when there is
no TDD frequency band defined in the Frequency Bands table.
3. When you have finished adding frequency bands, click the Close button (
).
For example, if you want to define the E-UTRA Band 1 with 10 MHz channels and EARFCNs corresponding to the centre
frequencies of the channels (50, 150, 250, 350, 450, 550), you can set:
You can also access the properties dialog box of each individual frequency band by double-clicking the left margin of the
row with the frequency band.
Default cyclic prefix: The total symbol duration in LTE comprises the useful part of the symbol, carrying the data bits,
and a cyclic prefix part, which is a portion of the useful data part repeated at the beginning of each symbol. The cyclic
prefix is the method used by LTE to counter inter-symbol interference (ISI). The cyclic prefix and the orthogonality of
subcarriers ensure that there is negligible intra-cell interference in LTE. LTE supports two cyclic prefix types: normal
and extended.
PDCCH overhead: The Physical Downlink Control Channel (PDCCH) can take up to 4 symbol durations in each subframe
in the downlink. In Atoll, the PDCCH is considered to include the PCFICH, PHICH, and PCH as well.
The PBCH, PSS, SSS, and the downlink reference signals consume a fixed amount of resources in the downlink. Their
corresponding overheads are hard-coded in Atoll in accordance with the 3GPP specifications.
PUCCH overhead: The Physical Uplink Control Channel (PUCCH) can consume a number of frequency blocks in the
uplink.
The uplink demodulation and sounding reference signals consume a fixed amount of resources in the uplink. Their
corresponding overheads are hard-coded in Atoll in accordance with the 3GPP specifications.
The amounts of resources corresponding to different signals and channels in LTE can be calculated and displayed in
Atoll. For more information, see "Displaying LTE Cell Details" on page 980.
Default special subframe configuration (TDD only): The configuration of the special subframe in TDD frames. This
configuration describes the durations and formats of DwPTS, GP, and UpPTS in the special subframe.
DwPTS is used for transmission of the reference signal, PDCCH, PSS, and PDSCH. Reference signals are located in a
DwPTS in the same manner as in any normal subframe. The PDCCH can at most be transmitted over two OFDM
symbols (symbol durations) because the third symbol duration in a DwPTS is used for the PSS transmission. The
resource elements left in DwPTS after excluding the RS, PDCCH, and PSS overheads are used for data transmission,
i.e., PDSCH. UpPTS is only used for SRS and PRACH.
RS EPRE: The reference signal energy per resource element can be either calculated automatically using the maximum
power and the EPRE offsets for different downlink channels defined per cell, or entered per cell by the user.
Calculated (equal distribution of unused EPRE): The reference signal EPRE for each cell will be calculated by Atoll
using the cells maximum power (user-definable) and the EPRE offsets. For transmitters with more than one trans-
959
mission antenna port, the energy belonging to the unused resource elements (resource elements reserved for reference signal transmission on other antennas) will be distributed among all the downlink signals and channels
equally.
Calculated (with boost): The reference signal EPRE for each cell will be calculated by Atoll using the cells maximum power (user-definable) and the EPRE offsets. For transmitters with more than one transmission antenna
port, the energy belonging to the unused resource elements (resource elements reserved for reference signal
transmission on other antennas) will be allotted to the reference signal resource elements only. This corresponds
to a 3 dB boost in the RS EPRE with 2 transmission antenna ports and 6 dB boost with 4 ports.
Calculated (without boost): The reference signal EPRE for each cell will be calculated by Atoll using the cells maximum power (user-definable) and the EPRE offsets. For transmitters with more than one transmission antenna
port, the energy belonging to the unused resource elements (resource elements reserved for reference signal
transmission on other antennas) will be considered lost.
User-defined: You will be able to enter the reference signal EPRE for each cell. The cells maximum power will be
calculated by Atoll using the RS EPRE and the EPRE offsets.
Independent of max power: You can enter the reference signal EPRE and the maximum power. Atoll does not
verify the validity of the entered values.
Best server selection criterion: You can select the best server selection criterion: reference signal level or RSRP.
Depending on the selected method, Atoll compares either the reference signal level or the RSRP from different transmitters at each pixel (or mobile) to determine the best server.
Best server selection method: Select either Standard or Random as the best server selection method to be used in
Monte Carlo simulations. For more information on the cell selection methods, see the Technical Reference Guide.
For carrier aggregation, Atoll selects multiple servers by processing lists of potential servers according to the Standard
or Random cell selection method:
LTE users:
a. A list of potential serving cells whose cell type includes LTE
LTE-A users:
a. A list of potential primary serving cells whose cell type includes LTE and LTE-A PCell
b. A list of potential secondary serving cells whose cell type may include LTE-A SCell DL and LTE-A SCell UL
Atoll selects the serving cell for LTE users from the list a. and a primary serving cell for LTE-A users from the remaining
list b.
Once a primary serving cell has been selected, Atoll eliminates the selected cell as well as any other co-channel cell
from list c. Here, co-channel cells are cells whose channels overlap the channel being used the primary serving cell.
In intra-eNode-B carrier aggregation, at this stage Atoll also eliminates cells belonging to
other eNode-Bs than that of the selected primary cell.
In group-based carrier aggregation, at this stage Atoll also eliminates potential servers that
do not belong to the carrier aggregation groups to which the selected primary cell belongs.
If the primary serving cell belongs to more than one carrier aggregation group, Atoll
searches for secondary serving cells in the first carrier aggregation group among the largest carrier aggregation groups (most member cells) sorted alphabetically.
For more information on carrier aggregation groups and modes, see "Working With Cell
Groups" on page 862.
For LTE-A users with a primary serving cell of type LTE-A PCell selected from list b., Atoll selects secondary serving
cells from list c.
This step is carried out until either list c. is empty, or the numbers of downlink or uplink secondary serving cells
assigned to the user become equal to the maximum numbers defined in the terminal properties. Secondary cells are
selected based on the reference signal level or RSRP, according to the defined best server selection criterion.
Only secondary cells whose PDSCH C/(I+N) is higher than or equal to the secondary cell activation threshold defined
in the terminal reception equipment properties are activated for aggregation in downlink. Similarly, only secondary
cells whose PDSCH C/(I+N) and PUSCH C/(I+N) are both higher than or equal to the secondary cell activation threshold
defined in the terminal and cell reception equipment properties, respectively, are activated for aggregation in uplink.
The primary and secondary serving cells once assigned to a mobile do not change during a Monte Carlo simulation.
For more information on defining layers, see "Defining Network Deployment Layers" on page 962.
For coordinated multipoint transmission and reception (CoMP), i.e., within the best servers cell-edge region, Atoll
also determines additional CoMP servers in downlink and uplink (1 or 2, depending on the defined maximum transmission and reception set sizes) from the same CoMP set as the best server.
960
AT332_UMR_E0
SU-MIMO criterion: You can select whether the SU-MIMO selection will be based on the RS C/N, RS C/(I+N), or PDSCH
or PUSCH C/(I+N). Atoll compares the selected criterion with the SU-MIMO threshold defined for the reception equipment.
MU-MIMO criterion: You can select whether MU-MIMO is activated based on the RS C/N, RS C/(I+N), or PDSCH or
PUSCH C/(I+N). Atoll compares the selected criterion with the MU-MIMO threshold defined for the reception equipment.
AAS criterion: You can select whether AAS is activated based on the RS C/N, RS C/(I+N), or PDSCH C/(I+N). Atoll compares the selected criterion with the AAS threshold defined for the reception equipment.
Multi-antenna interference calculation method: You can select the calculation method for interference from non-synchronised and adjacent channel multi-antenna cells. The calculated interference can be either proportional to the
number of antennas or independent of the number of antennas.
Uplink power adjustment margin: The margin (in dB) that will be added to the bearer selection threshold, for safety
against fast fading, when performing power control in uplink.
Figure 11.32 and Figure 11.33 give examples of downlink and uplink FDD resource blocks for the single antenna case using the
normal cyclic prefix.
961
Min interferer C/N threshold: Minimum requirement for interferers to be considered in calculations. Interfering cells
from which the received carrier-power-to-noise ratio is less than this threshold are discarded.
For example, setting this value to -20 dB means that interfering cells from which the received signals are 100 times
lower than the thermal noise level will be discarded in calculations. The calculation performance of interferencebased coverage predictions, interference matrices calculations, and Monte Carlo simulations can be improved by
setting a high value for this threshold.
Height/ground: The receiver height at which the path loss matrices and coverage predictions are calculated. Calculations made on mobile users (from traffic maps) in Monte Carlo simulations are also carried out at this receiver height.
Calculations made on fixed subscribers in Monte Carlo simulations are carried out at their respective heights.
Default max range: The maximum coverage range of transmitters in the network.
Downlink transmit power calculation: Under Downlink transmit power calculation, you can select the downlink
reference signal EPRE calculation method or set it to user-defined.
Best server selection: In this section, you can choose the serving cell layer selection Criterion and Method.
Diversity mode selection: In this section, you can choose the SU-MIMO, MU-MIMO, and AAS selection criteria.
Multi-antenna interference calculation: In this section, you can choose the multi-antenna interference calculation Method.
Uplink power adjustment: In this section, you can enter the uplink power adjustment Margin.
5. Select the Calculation Parameters tab. In this tab you can set:
Calculation limitation: In this section, you can enter the Min interferer C/N threshold.
Receiver: In this section, you can enter the receiver Height.
System: In this section, select the Max range check box if you want to apply a maximum system range limit, and
enter the maximum system range in the text box to the right.
6. Click OK. The global parameters are used during coverage predictions and simulations for the entire network.
962
Index: The layer index is automatically assigned by Atoll to each new layer that you create.
Name: The name of the network layer.
Priority: The priority of the network layer.
Max speed (km/h): The highest speed of a mobile user that can connect to cells of this layer.
AT332_UMR_E0
Selection margin (dB) of the layers table is no longer used in calculations as these have
been enhanced to model the connected mode mobility as defined by the 3GPP specifications. If you want to return to the cell selection mechanism based on the layer selection
margin as in Atoll 3.2.1, you must add a custom field named SELECTION_MARGIN of type
float to the Layers table.
14521
77290
29511
107269
2811
The PRACH preamble format 4 can only be used for TDD cells. The best server coverage limit due to PRACH preamble format 4 is only used when a cell uses a TDD
frequency band and:
If a cells PRACH preamble format is set to 4 but the above conditions are not true,
PRACH preamble format 0 is used in the calculations instead.
The PRACH preamble format models the distance-related boundary of the best
server coverage. In order to model the PRACH overhead, you must use the Max
Traffic Load (UL) (%) field available per cell. For example, for a PRACH overhead of
5 % of the frame, you can set the Max Traffic Load (UL) (%) to 95 %.
ICIC mode: The inter-cell interference coordination method. You can select from Time-switched FFR, Hard FFR,
Soft FFR, and Partial Soft FFR. For more information on different ICIC modes, see "Inter-cell Interference Coordination" on page 974.
963
Cell-edge power boost (DL) (dB): The downlink cell-edge power boost, i.e., the ratio of the power transmitted on
the cell-edge resource blocks with respect to the power transmitted on cell-centre resource blocks, for Soft FFR
and Partial Soft FFR ICIC modes. If you leave this column empty, Atoll automatically calculates the power boost
depending on the numbers of cell-centre and cell-edge frequency blocks.
Group 0 frequency blocks: The frequency blocks associated with PSS ID 0.
Group 1 frequency blocks: The frequency blocks associated with PSS ID 1.
Group 2 frequency blocks: The frequency blocks associated with PSS ID 2.
You can enter non-consecutive frequency block numbers separated with a comma, or you can enter a range of
frequency blocks separating the first and last index with a hyphen (for example, entering "1-5" corresponds to "1,
2, 3, 4, 5").
In time-switched and soft FFR, the frequency block group associated with a cells PSS ID serves cell-centre as well
as cell-edge users. The other two frequency block groups, associated with the other two PSS IDs, only serve cellcentre users.
In hard and partial soft FFR, the frequency block group associated with a cells PSS ID covers cell-centre as well as
cell-edge users. The other two frequency block groups, associated with the other two PSS IDs, serve neither celledge nor cell centre users.
If no frame configuration is defined for a cell using static ICIC, Atoll considers that group 0 frequency blocks correspond to the first 1/3rd of the total number of frequency blocks, group 1 frequency blocks correspond to the
second 1/3rd of the total number of frequency blocks, and group 2 frequency blocks correspond to the third 1/
3rd of the total number of frequency blocks.
Radio bearer index: Enter a bearer index. This bearer index is used to identify the bearer in other tables, such as
the bearer selection thresholds and the quality graphs in reception equipment.
Name: Enter a name for the bearer, for example, "16QAM 3/4." This name will appear in other dialog boxes and
results.
Modulation: Select a modulation from the list of available modulation types. This column is for information and
display purposes only.
Coding rate: Enter the coding rate used by the bearer. This column is for information and display purposes only.
Bearer efficiency (bits/symbol): Enter the number of useful bits that the bearer can carry in a symbol. This information is used in throughput calculations.
For information on the relation between bearer efficiency and spectral efficiency, see "Relation Between Bearer
Efficiency And Spectral Efficiency" on page 978.
Name: Enter a name for the quality indicator, for example, "BLER" for Block Error Rate. This name will appear in
other dialog boxes and results.
Used for data services: Select this check box to indicate that this quality indicator can be used for data services.
Used for voice services: Select this check box to indicate that this quality indicator can be used for voice services.
964
AT332_UMR_E0
General: On this tab, you can define the Name of the reception equipment.
Thresholds: On this tab (see Figure 11.34), you can modify the bearer selection thresholds, the SU-MIMO thresholds, MU-MIMO thresholds, AAS thresholds as well as secondary cells activation thresholds for different
mobility types.
A bearer is selected for data transfer at a given pixel if the received carrier-to-interference-and-noise ratio is higher than its selection threshold. For more information on bearers, see "Defining LTE Radio Bearers" on page 964.
SU-MIMO threshold is the RS C/N, RS C/(I+N), or PDSCH or PUSCH C/(I+N) threshold, according to the option set
in the Advanced parameters ("Global Network Settings" on page 959), above which SU-MIMO can be used. If left
empty, SU-MIMO is considered to be accessible.
MU-MIMO threshold is the RS C/N, RS C/(I+N), or PDSCH or PUSCH C/(I+N) threshold, according to the option set
in the Advanced parameters ("Global Network Settings" on page 959), above which MU-MIMO can be used. If left
empty, MU-MIMO is considered to be accessible
AAS threshold is the RS C/N, RS C/(I+N), or PDSCH C/(I+N) threshold, according to the option set in the Advanced
parameters ("Global Network Settings" on page 959), below which AAS can be used. If left empty, AAS is considered to be inaccessible.
Secondary cell activation threshold is the PDSCH or PUSCH C/(I+N) threshold above which secondary cells will be
activated.
Click the Selection thresholds button. The C/(I+N) Thresholds (dB) dialog box appears (see Figure 11.35).
ii. Enter the graph values. The values defined in the C/(I+N) Thresholds (dB) column must be unique and not repeated.
iii. Click OK.
965
Quality Graphs: On this tab (see Figure 11.36), you can modify the quality indicator graphs for different bearers
and for different mobility types. These graphs depict the performance characteristics of the equipment under different radio conditions. For more information on bearers, quality indicators, and mobility types, see "Defining LTE
Radio Bearers" on page 964, "Defining LTE Quality Indicators" on page 964, and "Modelling Mobility Types" on
page 247, respectively.
Click the Quality graph button. The Quality Graph dialog box appears (see Figure 11.37).
966
AT332_UMR_E0
PDSCH/PUSCH MIMO Gains: On this tab (see Figure 11.38), you can modify the SU-MIMO and diversity gains for
different bearers, mobility types, BLER values, and numbers of transmission and reception antenna ports. The
MIMO throughput gain is the increase in channel capacity compared to a SISO system. Diversity gains can be
defined for different diversity modes: transmit/receive diversity, SU-MIMO, and MU-MIMO. Diversity gain is
applied to the PDSCH or PUSCH C/N and C/(I+N) when the diversity mode is transmit or receive diversity. SUMIMO diversity gain is applied to the PDSCH or PUSCH C/N and C/(I+N) when the diversity mode is SU-MIMO. MUMIMO diversity gain is applied to the PDSCH or PUSCH C/N and C/(I+N) when the diversity mode is MU-MIMO.
For more information on bearers and mobility types, see "Defining LTE Radio Bearers" on page 964 and "Modelling
Mobility Types" on page 247, respectively. For more information on the different MIMO systems, see "Multiple
Input Multiple Output Systems" on page 972.
No MIMO gain (diversity, SU-MIMO, and MU-MIMO) is applied if the numbers of transmission and reception antennas are both equal to 1.
Click the Max MIMO gain graphs button. The Max MIMO Gain dialog box appears (see Figure 11.39).
967
You can define the gains for any combination of mobility type, bearer, and BLER, as well as the default gains for
"All" mobility types, "All" bearers, and a Max BLER of 1. During calculations, Atoll uses the gains defined for a
specific combination if available, otherwise it uses the default gains.
PBCH/PDCCH MIMO Gains: On this tab (see Figure 11.40), you can enter diversity gains for PBCH and PDCCH for
different mobility types, and numbers of transmission and reception antenna ports. The PBCH diversity gain is
applied to the PBCH C/N and C/(I+N) when the cell and terminal both support any form of MIMO in downlink. The
PDCCH diversity gain is applied to the PDCCH C/N and C/(I+N) when the cell and terminal both support any form
of MIMO in downlink.
968
AT332_UMR_E0
keeps only as many users as the maximum number defined for resource allocation. If no limit has been set, all the
users generated during Monte Carlo simulations for this cell are considered, and the scheduler continues to allocate
resources as long as there are remaining resources.
2. Resource allocation for supporting the Min throughput demands: This is the minimum throughput that a service
must get in order to work properly. The scheduler is either able to allocate the exact amount of resources required to
fully support the minimum throughput demands, or the service does not get any resources at all.
The scheduler allocates resources, for supporting the minimum throughput demands, in the order of service priority.
The effective service priority is determined based on the QCI priority and the user-defined service priority. For example, the order of resource allocation will be as follows: users of the service with the highest QCI priority and the highest
user-defined service priority to users of the service with the lowest QCI priority and the lowest user-defined service
priority.
In order to be connected, users active in downlink and uplink must be able to get their minimum throughput in both
directions. If a user active in downlink and uplink gets his minimum throughput in only one direction, he will be
rejected.
3. Resource allocation for supporting the Max throughput demands: Once the resources have been allocated for supporting the minimum throughput demands in the previous step, the remaining resources can be allocated in different
ways to support the maximum throughput demands of the users.
For allocating resources to support the maximum throughput demands, the following types of scheduling methods
are available:
Proportional fair: The proportional fair scheduling method allocates the same amount of resources to all the users
with a maximum throughput demand. Therefore, the resources allocated to each user are either the resources it
requires to achieve its maximum throughput demand or the total amount of resources divided by the total
number of users in the cell, which ever is smaller. The proportional fair scheduler can also model the effect of
resource scheduling over time, i.e., how a proportional fair scheduler benefits from fast fading, by applying multiuser diversity gains (MUG) to user throughputs.
Proportional demand: The proportional demand scheduling method allocates resources proportional to the
demands of users who have a maximum throughput demand. Therefore, users with higher maximum throughput
demands will have higher resulting throughputs than the users with lower maximum throughput demands.
Round Robin: The round robin scheduling method allocates the same amount of resources to all the users with a
maximum throughput demand. Therefore, the resources allocated to each user are either the resources it requires
to achieve its maximum throughput demand or the total amount of resources divided by the total number of users
in the cell, which ever is smaller.
Max C/I: This scheduling method allocates the resources required by the users to achieve their maximum
throughput demands in the order of their PDSCH C/(I+N) in downlink and of their PUSCH & PUCCH C/(I+N) in
uplink. This means that users who are under good radio conditions will get the resources they require. The end
result of this scheduling method is that the cumulated cell throughputs are maximised.
For all the scheduling methods, resources are allocated to support the maximum throughput demand until either the
maximum throughput demands of all the users are satisfied or the scheduler runs out of resources.
The Schedulers table lists the available schedulers. You can add, remove, and modify scheduler properties, if you want.
To define LTE schedulers:
1. In the Parameters explorer, expand the LTE Network Settings folder, right-click Schedulers and select Open Table.
The Schedulers table appears.
2. In the table, enter one scheduler per row. For information on working with data tables, see "Data Tables" on page 75.
For each scheduler, enter:
Name: Enter a name for the scheduler. This name will appear in the cell properties.
Scheduling method: Select the scheduling method used by the scheduler for allocating resources to support the
maximum throughput demands.
Target throughput for voice services: Select the throughput that the scheduler will target to satisfy for all voicetype services.
Target throughput for data services: Select the throughput that the scheduler will target to satisfy for all datatype services.
Bearer selection criterion: Select the criterion for the selection of the best bearer.
Bearer index: The best bearer selected for throughput calculations is the one with the highest bearer index
among the bearers available in the reception equipment.
Peak RLC throughput: The best bearer selected for throughput calculations is the one with the highest peak
RLC throughput (including SU-MIMO gains) among the bearers available in the reception equipment.
Effective RLC throughput: The best bearer selected for throughput calculations is the one with the highest
effective RLC throughput (including SU-MIMO gains) among the bearers available in the reception equipment.
969
Uplink bandwidth allocation target: Select the aim of the uplink bandwidth allocation.
Full bandwidth: All the frequency blocks are used for the PUSCH & PUCCH C/(I+N) calculations, i.e., no bandwidth reduction is performed.
Maintain connection: The number of frequency blocks is reduced one by one in order to increase the PUSCH
& PUCCH C/(I+N) so that the mobile is able to get at least the lowest bearer.
Best bearer: The number of frequency blocks is reduced in order to increase the PUSCH & PUCCH C/(I+N) so
that the mobile is able to get the highest bearer available. The definition of the highest bearer depends on the
Bearer selection criterion, i.e., highest index, highest peak RLC throughput, or highest effective RLC throughput.
When the Bearer selection criterion is set to Effective RLC throughput, Atoll calculates the effective RLC
throughput for all possible combinations of [number of frequency blocks, bearers], and keeps the number of
frequency blocks and the bearer which provide the highest effective RLC throughput.
3. Double-click a row corresponding to any scheduler in the Schedulers table. The schedulers properties dialog box
appears.
The General tab contains the scheduler properties described above. For Proportional fair schedulers, the properties
dialog box displays an additional MUG tab. On the MUG tab, you can edit the downlink and uplink throughput gains
due to multi-user diversity for different radio bearers and mobility types. You can also define the maximum PDSCH
and PUSCH C/(I+N) values above which their are no gains due to multi-user diversity.
To edit the downlink multi-user diversity gains for a radio bearer and a mobility type:
a. Click the DL MUG Graph button. The DL MUG dialog boxes appears.
b. Edit the downlink multi-user diversity gain values for different numbers of simultaneously connected downlink users.
c. Click OK.
To edit the uplink multi-user diversity gains for a radio bearer and a mobility type:
a. Click the UL MUG Graph button. The UL MUG dialog boxes appears.
b. Edit the uplink multi-user diversity gain values for different numbers of simultaneously connected uplink users.
c. Click OK.
4. Click OK.
5. Click the Close button ( ) to close the Schedulers table.
970
AT332_UMR_E0
For information on LTE transmission modes, their equivalent Atoll settings, and the algorithm of diversity mode selection, see "LTE Transmission Modes and Equivalent Settings in
Atoll" on page 982.
The Atoll LTE module includes:
A conventional beamforming smart antenna that models linear adaptive array systems: The conventional beamformer works by forming beams in the direction of the served mobiles. The smart antenna model dynamically calculates and applies weights on each antenna element in order to create beams in the direction of served users. The
antenna patterns thus created have a main beam pointed in the direction of the useful signal.
During Monte Carlo simulations, the power transmitted towards the served mobile from a cell is calculated by forming
a beam in that direction. For cells using smart antennas, the smart antenna weights are dynamically calculated for
each mobile being served. Beamforming is performed in interfered as well as interfering cells if the PDSCH C/(I+N) is
less than the AAS threshold defined in the terminal reception equipment properties. With beamforming, the downlink
C/(I+N) is calculated by taking into account the effects of beamforming. The smart antenna simulation results include
the angular distribution of the transmitted power spectral density for each cell. These results are then used to carry
out interference-based coverage predictions for the base stations using smart antennas. In coverage predictions,
beamforming is performed to calculate the smart antenna gain towards each pixel of the studied cell dynamically in
order to determine the received power. To calculate the interference, the simulation results for the angular distributions of downlink transmitted power spectral density are used in order to determine the power transmitted by an
interfering cell in the direction of each served pixel of the studied cell.
A grid-of-beams (GOB) smart antenna that models beam-switching antenna systems: Such antenna systems include
predefined array weights corresponding to various transmission patterns or beams. Each user is served using the bestsuited array weights. A grid of beams in Atoll comprises a list of antenna patterns. Each antenna pattern usually has
a different azimuth. All the antenna patterns are stored in the Antennas table, and can be accessed individually from
the Antennas folder.
During Monte Carlo simulations, Atoll selects the best suited beam from the GOB for each mobile generated. The best
suited beam is the one which provides the highest gain in the direction of the mobile. Interfering signals received at
each mobile are attenuated according to the antenna pattern of the selected beam. If the targeted and interfered
users are in the same direction with respect to the beam selected for the targeted user, the interference will be high.
Otherwise, the interfering signals will be attenuated.
Although the number of beams in a GOB is not limited, calculation times with a large
number of beams will be longer.
TDD LTE networks are more suitable for smart antennas than FDD because of the similar uplink and downlink channel characteristics in TDD. Information gathered from a mobile in the uplink can be assumed valid for downlink as well.
Smart antenna equipment are used to define conventional beamforming smart antenna and grid-of-beams (GOB) smart
antenna systems.
To create smart antenna equipment:
1. In the Parameters explorer, expand the Radio Network Equipment folder and the Smart Antennas folder, right-click
Smart Antenna Equipment, and select Open Table from the context menu. The Smart Antenna Equipment table
appears.
2. In the Smart Antenna Equipment table, each row describes a piece of smart antenna equipment. For information on
working with data tables, see "Data Tables" on page 75. For the new smart antenna equipment, enter:
3. Double-click the equipment entry in the Smart Antenna Equipment table once your new equipment has been added
to the table. The equipments Properties dialog box opens.
4. Under the General tab, you can modify the parameters that you set previously.
5. To modify the properties of the smart antenna model assigned to the smart antenna equipment, click the Parameters
button under Smart Antenna Model. The smart antenna models properties dialog box appears.
a. Click the General tab. On the General tab, you can change the default Name of the smart antenna model.
b. Click the Properties tab. On the Properties tab, you can define the following:
971
Number of elements: The number of antenna elements in the smart antenna system.
Single element pattern: The antenna model to be used for each antenna element. You can select an antenna
model from the list. The list contains the antennas available in the Antennas folder.
Diversity gain (cross-polarisation): Select the Diversity gain (cross-polarisation) check box if you are using
cross-polarised smart antennas and want to add diversity gains to the calculated downlink (all channels except
RS) beamforming gains. You can define the diversity gains per clutter class on the Clutter tab of the smart
antenna models properties dialog box.
For the Grid Of Beams smart antenna model, select the antenna patterns corresponding to the various beams of
the model. This list contains all the antenna patterns defined in the Antennas table whose Physical Antenna name
contains "GOB". The horizontal patterns of the selected beams are shown in the bottom pane.
c. If you are working with a Conventional Beamformer smart antenna model, a Clutter tab is also available. On the
Clutter tab, you can define the following parameters per clutter class:
Array gain offset (dB): Enter an offset to be added to the calculated beamforming array gains on the PDSCH.
Positive offset values are considered as gains while negative values as losses.
Power combining gain offset (dB): Enter an offset to be added to the calculated power combining gains on
the RS, SS, PBCH, PDCCH, and PDSCH. Positive offset values are considered as gains while negative values as
losses.
Diversity gain (cross-polarisation) (dB): Enter the diversity gains for cross-polarised smart antennas to be
applied to the SS, PBCH, PDCCH, and PDSCH.
972
AT332_UMR_E0
tion antenna ports, the throughput over the transmitter-receiver link can be theoretically increased M or N times, whichever
is smaller, M or N. SU-MIMO improves the throughput (channel capacity) for a given C/(I+N), and is used for the regions of a
cell that have sufficient C/(I+N) conditions. SU-MIMO (single-user MIMO) is also referred to as SM (spatial multiplexing) or
MIMO.
In Atoll, you can set whether a cell supports SU-MIMO by selecting the corresponding diversity support mode in cell properties
(see "Cell Properties" on page 848). SU-MIMO capacity gains can be defined in the reception equipment for different numbers
of transmission and reception antenna ports, mobility types, bearers, and maximum BLER. For more information on SU-MIMO
gains, see "Defining LTE Reception Equipment" on page 965.
During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell that
supports SU-MIMO, will benefit from the SU-MIMO gain in its throughput depending on its PDSCH or PUSCH C/(I+N) if the
received SU-MIMO criterion (RS C/N, RS C/(I+N), or PDSCH or PUSCH C/(I+N)) is higher than or equal to the SU-MIMO threshold defined in the reception equipment of the terminal or cell, respectively.
As SU-MIMO improves the channel capacity or throughputs, the PDSCH or PUSCH C/(I+N) of a user is first determined. Once
the C/(I+N) is known, Atoll calculates the user throughput based on the bearer available at the user location. The obtained
user throughput is then increased according to the SU-MIMO capacity gain and the SU-MIMO gain factor of the users clutter
class. The capacity gains defined in Max SU-MIMO gain graphs are the maximum theoretical capacity gains using SU-MIMO.
SU-MIMO requires rich multipath environment, without which the gain is reduced. In the worst case, there is no gain. Therefore, it is possible to define an SU-MIMO gain factor per clutter class whose value can vary from 0 to 1 (0 = no gain, 1 = 100 %
gain). For information on setting the SU-MIMO gain factor for each clutter class or for all clutter classes, see "Defining Clutter
Class Properties" on page 127.
The SU-MIMO capacity gain vs. C/(I+N) graphs available in Atoll by default have been generated based on the maximum theoretical SU-MIMO capacity gains obtained using the following equations:
CC MIMO
G MIMO = --------------------CC SISO
TX
RX
C I + N
Where CC MIMO = Min N Ant N Ant Log 2 1 + ----------------------------------------- is the channel capacity at a given C/(I+N) for a MIMO system
TX
RX
TX
RX
using N Ant transmission and N Ant reception antenna ports. CC SISO = Log 2 1 + C I + N is the channel capacity for a
single antenna system at a given C/(I+N). C/(I+N) is used as a ratio (not dB) in these formulas. You can replace the default
SU-MIMO capacity gain graphs with graphs extracted from simulated or measured values.
973
No FFR
Time-switched FFR
Hard FFR
Soft FFR
974
AT332_UMR_E0
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.
In LTE projects, the model standard deviation is used to calculate shadowing margins on signal levels. You can also calculate
shadowing margins on C/I values. For information on setting the model standard deviation and the C/I standard deviations for
each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 127.
Shadowing can be taken into consideration when Atoll calculates the signal level and C/(I+N) for:
A point analysis (see "Studying the Profile Around a Base Station" on page 859)
A coverage prediction (see "Studying Signal Level Coverage for a Single Base Station" on page 876).
Atoll always takes shadowing into consideration when calculating a Monte Carlo simulations. Atoll uses the values defined
for the model standard deviations per clutter class when calculating the signal level coverage predictions. Atoll uses the values
defined for the C/I standard deviations per clutter class when calculating the interference- based coverage predictions.
To display the shadowing margins per clutter class:
1. Select the Network explorer.
2. Right-click the Predictions folder. The context menu appears.
3. Select Shadowing Margins from the context menu. The Shadowing Margins dialog box appears.
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 dialog box is for information only.
Standard deviation: Select the type of standard deviation to be used to calculate the shadowing margin:
Model: The model standard deviation. Atoll will display the shadowing margin of the signal level.
C/I: The C/I standard deviation. Atoll will display the C/I shadowing margin.
Interference received by mobiles on the downlink: Interference can be received by mobiles in an LTE network on the
downlink from external base stations and mobiles in the vicinity.
Interference from external base stations (also called downlink-to-downlink interference) might 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 (GSM, UMTS, CDMA2000, and so on). 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.
Interference from external mobiles (also called uplink-to-downlink interference) might be created by insufficient
separation between the uplink frequency used by the external network and the downlink frequency used by your LTE
network. Such interference may also come from co-existing TDD networks. The effect of this interference is modelled
in Atoll using the Additional DL noise rise definable for each cell in the LTE network. This noise rise is taken into
account in all downlink interference-based calculations. For more information on the Additional DL noise rise, see
"Cell Properties" on page 848.
975
Interference received by cells on the uplink: Interference can be received by cells of an LTE network on the uplink
from external base stations and mobiles in the vicinity.
Interference from external base stations (also called downlink-to-uplink interference) can be created by insufficient
separation between the downlink frequency used by the external network and the uplink frequency used by your LTE
network. Such interference may also come from co-existing TDD networks.
Interference from external mobiles (also called uplink-to-uplink interference) can 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 Additional UL noise rise definable for each cell in the LTE network. This noise
rise is taken into account in uplink interference-based calculations in Monte Carlo simulations but not in coverage
predictions. For more information on the Additional UL noise rise, see "Cell Properties" on page 848.
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 LTE document, i.e. in co-planning mode or in a multi-RAT document.
To define the inter-technology IRFs in the victim network:
1. In the Parameters explorer, expand the Radio Network Equipment folder, right-click Inter-technology Interference
Reduction Factors, and select Open Table. The Inter-technology Interference Reduction Factors table appears.
2. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter:
976
AT332_UMR_E0
Victim bandwidth (kHz): 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) dialog box appears.
i.
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.
Calls/hour = 1.
Duration (sec.) = 3600.
Calls/hour = 1.
UL volume (KBytes) = Service uplink average requested throughput x 3600/8.
DL volume (KBytes) = Service downlink average requested throughput x 3600/8.
The above settings will set the user activity probabilities to 100 %. If you create a traffic map based on environment classes,
the user density values that you define in your environment classes will be the actual user densities. This means that, for
X users/km defined in the environment class for a given user profile, the Monte Carlo simulator will generate exactly X users/
km for each service of the user profile.
In this way, you can know beforehand the exact number of active users, and their services, generated during the simulations.
This procedure should only be used when appropriate traffic data is not available.
977
Where RS is the receiver sensitivity in dBm, NF is the noise figure of the receiver in dB, SF is the sampling frequency in MHz,
N Used is the number of subcarriers corresponding to the number of frequency blocks, N Total is the total number of subcarriers, i.e., the FFT size.
In the above explanation, the term receiver refers to the base station in uplink and to the mobile/user equipment in the downlink.
bps Hz
Where BLER is the Block Error Rate, r is the coding rate for the bearer, and M is the number of modulation states. For simplification, we set BLER = 0, and use QPSK1/2, i.e., four modulation states and r = 0.5. With these values, we get a spectral effi-
978
AT332_UMR_E0
ciency of 1 bps/Hz for QPSK1/2. In other words, a communication channel using QPSK1/2 modulation and coding scheme can
send 1 bps of useful data per unit bandwidth.
In order to compare the bearer efficiency and spectral efficiency of QPSK1/2, lets say that QPSK1/2 has a bearer efficiency of
1 bits/symbol. Here as well, the number of bits refers to useful data bits. The width of a subcarrier in LTE is F = 15 kHz ,
1
from which we can calculate the useful symbol duration as well: T U = ------= 66,67 sec . In one second, there can be
F
1 sec 66,67 sec = 15000 symbol durations. If 15000 symbols are transmitted using QPSK1/2, this gives us a throughput
of 15000 Symbols/sec 1 bits/Symbol = 15000 bps , which is the throughput achievable using one subcarrier of 15 kHz. We
can find the spectral efficiency by normalizing the throughput to unit bandwidth. This gives:
15000 bps/subcarrier 15 kHz/subcarrier = 1 bps/Hz .
In order to compare equivalent quantities, we have ignored some system parameters, such as the cyclic prefix, and have
considered that the entire frame is transmitted in one direction, uplink or downlink.
b. Set the Target throughput for voice services to "2 - Application Throughput" for the scheduler being used.
In this way, Atoll will allocate resources to the users of this service such that they get 64 kbps application throughput,
and around 85.6 kbps of effective RLC throughput.
b. Set the Target throughput for voice services to "2 - Application Throughput" for the scheduler being used.
In this way, Atoll will allocate resources to the users of this service such that they get 8 kbps application throughput,
and around 29.6 kbps of effective RLC throughput.
979
For FDD frequency bands, the downlink and uplink EARFCNs are offset by 18000, so you can use either the downlink or the
uplink EARFCNs as channel numbers in Atoll.
Total RE (DL): The total number of resource elements in the downlink subframes.
RS RE (DL) and RS RE (DL) (%): The number and percentage of resource elements used to transmit the cell specific
reference signals.
An average number of transmitted reference signals is considered in Atoll. More specifically, when four antenna
ports are used, eight reference signals are transmitted on two antenna ports and four are transmitted on the other
two antenna ports. In this case, Atoll considers an average of six transmitted reference signals per antenna port.
SSS RE (DL) and SSS RE (DL) (%): The number and percentage of resource elements belonging to the SSS.
PSS RE (DL) and PSS RE (DL) (%): The number and percentage of resource elements belonging to the PSS.
PBCH RE (DL) and PBCH RE (DL) (%): The number and percentage of resource elements belonging to the PBCH.
PDCCH+PCFICH+PHICH RE (DL) and PDCCH+PCFICH+PHICH RE (DL) (%): The number and percentage of resource
elements belonging to the PDCCH (which is considered to include the PCFICH and PHICH).
PDSCH RE (DL) and PDSCH RE (DL) (%): The number and percentage of resource elements remaining in the PDSCH
after removing the reference signals, synchronisation signals, and control channel overheads.
Unused RE and Unused RE (%): The number and percentage of resource elements not used for transmission.
980
Total RE (UL): The total number of resource elements in the uplink subframes.
DRS RE (UL) and DRS RE (UL) (%): The number and percentage of resource elements belonging to the DRS.
AT332_UMR_E0
SRS RE (UL) and SRS RE (UL) (%): The number and percentage of resource elements belonging to the SRS.
PUCCH RE (UL) and PUCCH RE (UL) (%): The number and percentage of resource elements belonging to the
PUCCH.
PUSCH RE (UL) and PUSCH RE (UL) (%): The number and percentage of resource elements remaining in the PUSCH
after removing the reference signals and control channel overheads.
The following calculated power values are displayed for LTE frames:
For more information on the LTE logical and transport channels, see "Glossary of LTE Terms" on page 984.
Cyclic
shift size
Number of cyclic
shifts per sequence
PRACH preamble
duration (us)
Corresponding
Number of required
maximum cell radius (m) sequences per cell
839
13
64
800
12.40
1859.36
839
15
55
800
14.30
2145.41
839
18
46
800
17.16
2574.49
839
22
38
800
20.98
3146.60
839
26
32
800
24.79
3718.71
839
32
26
800
30.51
4576.88
839
38
22
800
36.23
5435.04
839
46
18
800
43.86
6579.26
839
59
14
800
56.26
8438.62
839
76
11
800
72.47
10870.08
839
93
800
88.68
13301.55
839
119
800
113.47
17020.26
10
839
167
800
159.24
23885.58
13
839
279
800
266.03
39904.65
22
839
419
800
399.52
59928.49
32
839
839
800
800.00
120000.00
64
Cyclic
shift size
Number of cyclic
shifts per sequence
PRACH preamble
duration (us)
Corresponding
Number of required
maximum cell radius (m) sequences per cell
839
15
55
800
14.30
2145.41
839
18
46
800
17.16
2574.49
981
Cyclic
shift size
Number of cyclic
shifts per sequence
PRACH preamble
duration (us)
Corresponding
Number of required
maximum cell radius (m) sequences per cell
839
22
38
800
20.98
3146.60
839
26
32
800
24.79
3718.71
839
32
26
800
30.51
4576.88
839
38
22
800
36.23
5435.04
839
46
18
800
43.86
6579.26
839
55
15
800
52.44
7866.51
839
68
12
800
64.84
9725.86
839
82
10
800
78.19
11728.25
839
100
800
95.35
14302.74
839
128
800
122.05
18307.51
11
839
158
800
150.66
22598.33
13
839
202
800
192.61
28891.54
16
839
237
800
225.98
33897.50
22
Cyclic
shift size
Number of cyclic
shifts per sequence
PRACH preamble
duration (us)
Corresponding
Number of required
maximum cell radius (m) sequences per cell
139
69
133
1.91
287.05
139
34
133
3.83
574.10
139
23
133
5.74
861.15
139
17
133
7.65
1148.20
139
10
13
133
9.57
1435.25
139
12
11
133
11.48
1722.30
139
15
133
14.35
2152.88
The above mapping tables show values calculated for ideal conditions (no delay spread) and perfect equipment (no processing/implementation delay). Different equipment and propagation conditions may imply additional delays and margins which
impact the calculation of the number of required root sequence indexes per cell. For example, the maximum delay spread for
the normal cyclic prefix is 6.25 us and that for the extended cyclic prefix is 16.67 us. Moreover, as transmission/reception
equipment is not perfect, a certain margin may need be added in the calculation in order to compensate for implementation
delays. Supposing the implementation delay margin to be 1.2 us, the maximum cell radius for Set 1: Unrestricted set for nominal cells will be calculated to be:
RSI
length
( N ZC )
Cyclic
shift size
( N CS )
Number of cyclic
shifts per sequence
839
32
839
PRACH preamble
duration (us)
Corresponding
maximum cell radius (m)
(R )
Number of required
sequences per cell
26
800
30.51
3639.38
119
800
113.47
16082.76
10
(T )
Speed of Light
CS
Delay
- Delay Spread -------------------------------------- Implementation
Where R = T ------------------------------------------------------------------
N ZC
2
2 3,3
982
AT332_UMR_E0
Transmission Mode
Terminal
None
None
Transmit/Receive Diversity
MIMO
SU-MIMO
MIMO
SU-MIMO
MIMO
MU-MIMO
N/A
Transmit/Receive Diversity
MIMO
AAS
AAS
AAS+Transmit/Receive Diversity
AAS+SU-MIMO
AAS+AMS
AAS+MU-MIMO
AAS+MIMO
AAS+Transmit/Receive Diversity
AAS+SU-MIMO
AAS+AMS
AAS+MU-MIMO
AAS+MIMO
The difference between transmission modes 2 and 6 and 3 and 4 is the absence and presence of channel state feedback (open and closed loop methods). In Atoll, this is interpreted as higher gains in the MIMO lookup tables for the reception equipment
corresponding to the closed loop mode compared to the open loop mode.
Depending on radio conditions, transmission modes can be downgraded as follows (downgrades already supported in Atoll
are highlighted):
Atoll allows selecting multiple MIMO modes simultaneously. The MIMO mode used for calculations for any user depends on
the modes activation thresholds and selection priorities as follows:
1. If SU-MIMO is supported by the cell and the value of the SU-MIMO criterion >= SU-MIMO threshold
MIMO mode = SU-MIMO
2. If MU-MIMO is supported by the cell and the value of the MU-MIMO criterion >= MU-MIMO threshold
MIMO mode = MU-MIMO
3. If transmit/receive diversity is supported by the cell
MIMO mode = Transmit diversity in downlink and receive diversity in uplink
4. Otherwise
MIMO mode = None.
In parallel to the MIMO modes, the AAS mode will be selected or not as follows:
1. If AAS is supported by the cell and the value of the AAS criterion < AAS threshold
AAS mode = AAS
2. Otherwise
AAS mode = None.
The user diversity mode displayed in calculation results is a combination of both MIMO and AAS modes.
983
User: A general term that can also designate a subscriber, mobile, and receiver.
Mobile: Users generated and distributed during simulations. These users have, among other parameters, defined services, terminal types, and mobility types assigned for the duration of the simulations.
Receiver: A probe mobile, with the minimum required parameters needed for the calculation of path loss, used for
propagation loss and raster coverage predictions.
Radio Bearer: A Modulation and Coding Scheme (MCS) used to carry data over the channel.
Peak RLC Throughput: The maximum RLC layer throughput (user or channel) that can be achieved at a given location
using the highest LTE bearer available. This throughput is the raw throughput without considering the effects of
retransmission due to errors and higher layer coding and encryption.
Effective RLC Throughput: The net RLC layer throughput (user or channel) that can be achieved at a given location
using the highest LTE bearer available computed taking into account the reduction of throughput due to retransmission due to errors.
Application Throughput: The application layer throughput (user or channel) that can be achieved at a given location
using the highest LTE bearer available computed taking into account the reduction of throughput due to PDU/SDU
header information, padding, encryption, coding, and other types of overhead.
Channel Throughputs: Peak RLC, effective RLC or application throughputs achieved at a given location using the
highest LTE bearer available with the entire cell resources (downlink or uplink).
Allocated Bandwidth Throughputs: Uplink peak RLC, effective RLC or application throughputs achieved at a given
location using the best possible LTE bearer with the number of subchannels calculated.
User Throughputs: Peak RLC, effective RLC or application throughputs achieved at a given location using the highest
LTE bearer available with the amount of resources allocated to a user by the scheduler.
Traffic Loads: The uplink and downlink traffic loads are the percentages of the uplink and the downlink frames in use
(allocated) to the traffic (mobiles) in the uplink and in the downlink, respectively.
Resources: In Atoll, the term "resource" is used to refer to the average number of resource units, expressed in percentage (as traffic loads, when the average is performed over a considerably long duration) of the total number of
resource units in a superframe of 1 sec.
Uplink Noise Rise: Uplink noise rise is a measure of uplink interference with respect to the uplink noise:
I UL + N UL
NR UL = ------------------------ , or NR UL = 10 Log I UL + N UL 10 Log N UL in dB. This parameter is one of the two
N UL
methods in which uplink interference can be expressed with respect to the noise. The other parameter often used
I
I UL + N UL
UL
- . Usually, the uplink load factor is kept as a
instead of the uplink noise rise is the uplink load factor: L UL = ------------------------
linear value (in percentage) while the uplink noise rise is expressed in dB. The two parameters express exactly the
same information, and can be inter-converted as follows:
I
I+NN
I
I+N
N
I
N
N
I
I+N
1
------------ = ---------------------- => ------------ = ------------ ------------ => ------------ = 1 ------------ => ------------ = 1 ------------ => ------------ = --------------------I
I+N
I+N
I+N
I+N I+N
I+N
I+N
I+N
I+N
N
1 -----------I+N
1
=> NR = -----------
1L
The following table shows the relation between interference, load factor, and noise rise.
Interference (I)
0
=N
=9xN
= 99 x N
Noise Rise
1
2
10
100
The reason why uplink interference is expressed in terms of noise rise (in dB) in Atoll instead of load factor (in percentage) is that the load factor varies somewhat exponentially with the increase in interference.
984
Frame: An LTE frame is 10 ms long. The duration of a frame is a system-level constant. Each frame comprises 10 1 mslong subframes, with each subframe containing 2 0.5 ms-long slots. Each slot can have 7 or 6 symbol durations for
normal or extended cyclic prefix, respectively, and for a 15 kHz subcarrier width. A slot can have 3 symbol durations
for extended cyclic prefix used with a 7.5 kHz subcarrier width. LTE includes specific frame structures for FDD and TDD
AT332_UMR_E0
systems as shown in Figure 11.46. For TDD systems, two switching point periodicities can be used; half-frame or full
frame. Half-frame periodicity provides the same half-frame structure as a TD-SCDMA subframe. The PBCH, PSS, and
SSS are carried by subframes 0 and 5, which means that these 2 subframes are always used in downlink. A subframe
is synonymous with TTI (transmission time interval), i.e., the minimum unit of resource allocation in the time domain.
Figure 11.46: LTE frame structures (DL: blue, UL: orange, DL or UL: green)
Resource Element, Symbol, or Modulation Symbol: In Atoll, a symbol refers to one resource element or one modulation symbol, which is 1 symbol duration long and 1 subcarrier width wide, as shown in Figure 11.45.
Symbol Duration: In Atoll, a symbol duration refers to one OFDM symbol, which is the duration of one modulation
symbol over all the subcarriers/frequency blocks being used.
Subcarrier: An OFDM channel comprises many narrowband carriers called subcarriers. OFDM subcarriers are orthogonal frequency-domain waveforms generated using fast fourier transforms (see Figure 11.47).
Frequency Block: It is the minimum unit of resource allocation in the frequency domain, i.e., the width of a resource
block, 180 kHz. It is a system-level constant. A frequency block can either contain 12 subcarriers of 15 kHz each (see
Figure 11.47) or 24 subcarriers of 7.5 kHz each.
Resource Block: It is the minimum unit of resource allocation, i.e., 1 frequency block by 1 slot (see Figure 11.47).
Schedulers are able perform resource allocation every subframe (TTI, transmission time interval), however, the granularity of resource allocation 1 slot in time, i.e., the duration of a resource block, and 1 frequency block in frequency.
LTE Logical Channels: LTE logical channels include (see Figure 11.48):
Broadcast Control Channel (BCCH) (DL): Carries broadcast control information.
Paging Control Channel (PCCH) (DL): Carries paging control information.
Common Control Channel (CCCH) (DL and UL): Carries common control information.
Dedicated Control Channel (DCCH) (DL and UL): Carries control information dedicated to users.
Dedicated Traffic Channel (DTCH) (DL and UL): Carries user traffic data.
Multicast Control Channel (MCCH) (DL): Carries multicast control information.
Multicast Traffic Channel (MTCH) (DL): Carries multicast traffic data.
LTE Transport Channels: LTE transport channels include (see Figure 11.48):
Broadcast Channel (BCH) (DL): Carries broadcast information.
Paging Channel (PCH) (DL): Carries paging information.
985
Downlink Shared Channel (DL-SCH) (DL): Carries common and dedicated control information and user traffic data.
It can also be used to carry broadcast and multicast control information and traffic in addition to the BCH and
MCH.
Uplink Shared Channel (UL-SCH) (UL): Carries common and dedicated control information and user traffic data.
Multicast Channel (MCH) (DL): Carries multicast information.
Random Access Channel (RACH) (UL): Carries random access requests from users.
LTE Physical Layer Channels: LTE physical layer channels include (see Figure 11.48):
Physical Broadcast Channel (PBCH) (DL): Carries broadcast information.
Physical Downlink Shared Channel (PDSCH) (DL): Carries paging information, common and dedicated control
information, and user traffic data. It can also be used to carry broadcast and multicast control information and
traffic in addition to the PBCH and PMCH. Parts of this channel carry the primary and secondary synchronisation
signals (PSS and SSS), the downlink reference signals, the physical downlink control channel (PDCCH), the physical
HARQ indicator channel (PHICH), and the physical control format indicator channel (PCFICH).
Physical Uplink Shared Channel (PUSCH) (UL): Carries common and dedicated control information and user traffic
data.
Physical Uplink Control Channel (PUCCH) (UL): Carries control information.
Physical Multicast Channel (PMCH) (DL): Carries multicast information.
Physical Random Access Channel (PRACH) (UL): Carries random access requests from users.
Figure 11.48: LTE logical, transport, and physical layer channels (DL: blue, UL: orange, DL or UL: green)
986
Chapter 12
3GPP Multi-RAT
Networks
This chapter explains how to
use Atoll to design, analyse,
and optimise a multi-RAT
network.
988
AT332_UMR_E0
5b
5a
5c
5
6
7
8
10
11
989
The steps involved in planning a 3GPP multi-RAT network are described below. The numbers refer to Figure 12.1.
1. Open an existing 3GPP multi-RAT-planning document or create a new one (
).
You can open an existing Atoll 3GPP multi-RAT document by selecting File > Open.
Creating a new Atoll 3GPP multi-RAT document is explained in "Creating a Standalone Document" on page 35.
).
You can add and modify the following elements of base stations:
You can also add base stations using a base station template (see "Creating a Base Station" on page 992).
3. Carry out basic coverage predictions (
4. Allocate neighbours (
) from the analysis of base stations: "Studying Base Stations" on page 994
).
5. For the GSM part of the network, estimate the required number of TRXs (
You can import or create traffic maps ( 5a ) and use them as a basis for dimensioning 5b ) (see "Studying GSM/
GPRS/EDGE Network Capacity" on page 325 in Chapter 7: GSM/GPRS/EDGE Networks).
You can define them manually either on the TRXs tab of each transmitters Properties dialog box or in the Subcells
table (see "Modifying a Subcell" on page 290) (
5c
).
6. Once you have the required number of TRXs in the GSM part of the network, manually or automatically create a frequency plan (
).
).
8. For the LTE part of the network, allocate frequencies and physical cell IDs ( 8 ).
9. Before making more advanced coverage predictions, you need to define cell load conditions ( 9 ).
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 ( 9a and 9b ) (see
"Optimising Network Parameters Using ACP" on page 1007).
You can define them manually in GSM ("Importing OMC Traffic Data into the Subcells Table: Traffic Data" on
page 326), UMTS ("Setting the UL Load Factor and the DL Total Power" on page 541) and LTE ("Setting Cell Loads
and Noise Rise Values" on page 879) ( 9c ).
990
AT332_UMR_E0
A n te n n a
- A z im u t h
- M e c h a n i c a l t i lt
TMA
A n te n n a
- H e ig h t
F e e d e r C a b le
T r a n s m it t e r
- N o is e fig u r e
- Pow er
S it e
- X , Y c o o r d in a t e s
991
To create a GSM GPRS EDGE base station, see "Creating a GSM/GPRS/EDGE Base Station" on page 279
To create a UMTS HSPA base station, see "Creating UMTS Base Stations" on page 519
To create an LTE base station, see "Creating LTE Base Stations" on page 853.
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. Because a 3GPP multi-RAT document models several technologies, the new
transmitter will be created using the technology (GSM, UMTS or LTE) of the station
template currently selected in the toolbar.
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 or subcell data in the Cells or Subcells table, in that order.
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 a Table Record" on page 83.
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 or subcell data in the Cells or Subcells table, in that order.
For information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets" on page 86. For information on importing table data, see "Importing Tables from Text Files" on page 88.
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 291.
992
AT332_UMR_E0
map. You can also select a site to display all of the transmitters located on it in the Site explorer. When selecting a transmitter,
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: Working Environment:
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 "Associating a
Label to an Object" on page 53.
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 "Associating a Tip Text to an Object" on page 54.
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.
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 "Setting the Display Type" on page 52.
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 (
same site with the same azimuth, you can differentiate them by selecting different symbols for each (
For information on defining the transmitter symbol, see "Setting the Display Type" on page 52.
and
).
To create a GSM GPRS EDGE repeater, see "Creating a Repeater" on page 298
To create a UMTS HSPA repeater, see "Creating Repeaters" on page 529
To create a LTE repeater, see "Creating Repeaters" on page 866
993
that has antennas. This can be done by modelling a repeater. For information on creating a repeater, see "Creating a
Repeater" on page 993.
In a 3GPP multi-RAT network, you can define remote antennas for GSM, UMTS and LTE transmitters. Remote antennas are
managed in a 3GPP multi-RAT network the same way for each technology. In the Network explorer, remote antennas are
found in the transmitter folder of the technology they belong to.
To create a GSM GPRS EDGE remote antenna, see "Creating a Remote Antenna" on page 302
To create a UMTS HSPA remote antenna, see "Creating Remote Antennas" on page 533
To create a LTE remote antenna, see "Creating Remote Antennas" on page 870
To study GSM GPRS EDGE base stations, see "Studying GSM Base Stations" on page 305
To study UMTS HSPA base stations, see "Studying UMTS Base Stations" on page 536
To study LTE base stations, see "Studying LTE Base Stations" on page 874.
Some technology-specific coverage predictions use terminal, mobility type, and service parameters in calculations. For information on these parameters, see "Service and User Modelling" on page 241.
This section covers the following topics:
GSM: the allocated frequency plan and the subcell DL traffic load
UMTS: the DL total power and UL load factor (defined at the UMTS cell level)
LTE: the allocated frequency plan, the DL traffic load and UL noise rise (defined at the LTE cell level).
For the purpose of these predictions, each pixel is considered a non-interfering receiver with a defined service, mobility type,
and terminal as explained in "Service and User Modelling" on page 241.
The following 3GPP multi-RAT coverage predictions are explained in this section:
12.2.7.1.1
994
The GSM part is based on the GSM Effective Service Area Analysis (DL+UL), as explained in "Making a Service Area
Prediction" on page 454. Radio conditions are evaluated over the HCS server area with a margin of 4 dB, on all the
interfered subcells. Codec modes and coding schemes are obtained from these radio conditions based on C/(I+N)
without ideal link adaptation. This implies that a frequency plan has to be defined in order to obtain this GSM/GPRS/
EDGE coverage.
The UMTS part is based on the UMTS Effective Service Area Analysis (EbNt) (DL+UL) analysis, as explained in "Studying the Effective Service Area" on page 543. For HSPA services, the coverage is based on a combination of HSDPA et
HSUPA service areas as explained in "HSDPA Coverage Predictions" on page 549 and "HSUPA Coverage Predictions"
on page 551.
The LTE part is based on the LTE Effective Service Area Analysis (DL+UL), as explained in "Studying the Effective Service Area" on page 886.
AT332_UMR_E0
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 by clicking
the Calculate button (
The progress of the calculation, as well as any messages, are displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
12.2.7.1.2
The GSM part is based on the GSM Packet Throughput Analysis (DL), as explained in "Making a Coverage Prediction
by Packet Throughput" on page 445
The 3GPP multi-RAT effective RLC throughput is obtained from the maximum effective RLC throughput of the GSM
layer. The 3GPP multi-RAT application throughput from the maximum application throughput of the GSM layer.
The UMTS part is based on the R99 Service Area Analysis (EbNt) (DL) prediction, as explained in "Studying Downlink
and Uplink Service Areas (EbNt)" on page 542 and on the HSDPA Throughput Analysis (DL), as explained in "HSDPA
Coverage Predictions" on page 549.
The 3GPP multi-RAT effective RLC and application throughputs are respectively obtained from the effective RLC and
application throughputs of the R99 or the HSDPA layer.
The LTE part is based on the LTE Coverage by Throughput (DL), as explained in "Making a Coverage Prediction by
Throughput" on page 888.
The 3GPP multi-RAT effective RLC and application throughputs are respectively obtained from the effective RLC channel throughput (DL) and the application channel throughput (DL) coverage predictions.
Effective RLC Throughput: The throughput on the RLC layer that a cell can provide to the selected terminal per pixel
taking into account possible transmission errors (BLER) for the highest priority technology.
Max Effective RLC Throughput: The maximum throughput on the RLC layer that a cell can provide to the selected terminal per pixel taking into account possible transmission errors (BLER), considering all available technologies.
995
Application Throughput: The throughput on the application layer that a cell can provide to the selected terminal per
pixel taking into account possible transmission errors (BLER) for the highest priority technology.
Max Application Throughput: the maximum throughput on the application layer that a cell can provide to the selected
terminal per pixel taking into account possible transmission errors (BLER), considering all available technologies.
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 by clicking
the Calculate button (
The progress of the calculation, as well as any messages, are displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
12.2.7.2.1
996
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.
AT332_UMR_E0
12.2.7.2.2
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 12.3).
12.2.7.3.1
"Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 997.
"Generating a Coverage Prediction Report" on page 998.
"Exporting a Coverage Prediction Report" on page 1000.
Draw Polygon
i.
Click once on the map to start drawing the focus zone or hot spot.
ii. Click once on the map to define each point on the map where the border of the focus zone or hot spot changes
direction.
iii. Click twice to finish drawing and close the focus zone or hot spot.
Draw Rectangle
i.
Click the point on the map that will be one corner of the rectangle that will define the focus zone or hot spot.
ii. Drag to the opposite corner of the rectangle that will define the focus zone or hot spot. When you release the
mouse, the focus zone or hot spot will be created from the rectangle defined by the two corners.
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 explorer, it will no longer be displayed but will still be taken into account.
997
You can save the focus zone or hot spots, so that you can use it in a different Atoll
document, in the following ways:
12.2.7.3.2
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 104.
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 in the Geo
explorer and selecting Export from the context menu.
You can include population statistics in the focus or hot spot by importing a population map. For information on importing maps, see "Importing Raster Format Geo
Data Files" on page 120.
998
to move it up or
AT332_UMR_E0
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 dialog box 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 dialog box appears.
b. In the Save As dialog box, 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 dialog
box. 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 generate a report for all the coverage predictions currently displayed on the map:
1. Select the Network explorer.
2. Click the Expand button ( ) to expand the Predictions folder.
3. Select the check box in front of each coverage prediction that you want to include in the report.
4. Right-click the Predictions folder. The context menu appears.
5. Select Generate Report from the context menu. The Columns to Be Displayed dialog box appears.
In case a hot spot was imported in your Atoll document, additional fields will appear at the bottom of the Columns to
Be Displayed dialog box if the hot spot description contains parameters other than Atoll-specific parameters.
6. 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
999
"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 136.
12.2.7.3.3
2. In the Save As dialog box, enter the File name and select the format from the Save as type list:
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 91.
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 "Geographic Export Zone" on page 68.
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 210.
1000
Intersection: This display mode shows the area where both coverage predictions overlap (for example, pixels covered
by both predictions are displayed in red).
Merge: This display mode shows the area that is covered by either of the coverage predictions (for example, pixels
covered by at least one of the 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 mode 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).
Value Difference: This display mode shows the dB difference between any two coverage predictions by signal level.
This display option will not be available if the coverage predictions were calculated using different resolutions.
AT332_UMR_E0
1001
Figure 12.5: Signal level coverage prediction of network with new base station
Now you can compare the two coverage predictions.
To compare two coverage 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 dialog box 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 names and
resolutions.
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
Merge
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 12.6, shows clearly the area covered only by the new
base station.
1002
AT332_UMR_E0
1003
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
Merge
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 12.9, shows clearly the increase in coverage due at the
change in antenna tilt.
For information on LTE fixed subscriber analyses, see "Multi-point Analyses" on page 899.
12.2.7.6.1
1004
Importing a list of points from an external file: Click the Actions button and select Import Table from the menu to
open the Open file dialog box. In this dialog box, select a TXT or CSV file containing a list of points and click Open.
For more information on importing data tables, see "Importing Tables from Text Files" on page 88.
Importing a list of points from a fixed subscriber traffic map: Click the Actions button and select Import from Fixed
Subscribers from the menu to open the Fixed Subscribers dialog box. In this dialog box, select one or more existing
fixed subscriber traffic maps and click OK.
Copying a list of points from an external file.
AT332_UMR_E0
Creating points in the list by editing the table: Add new points by clicking the New Row icon (
and Y coordinates as well as a service, a terminal, and a mobility.
) and entering X
The list of points must have the same coordinate system as the display coordinate system
used in the Atoll document. For more information on coordinate systems, see "Setting a
Coordinate System" on page 41.
It is also possible to leave the Points tab empty and add points to the analysis on
the map using the mouse once the point analysis item has been created. To add
points on the map using the mouse, right-click the point analysis item to which you
want to add points, and select Add Points from the context menu. The mouse
pointer changes to point creation mode (
want to add. Press ESC or click the Pointer button ( ) in the Map toolbar to finish
adding points.
You can also export the list of point from a point analysis to ASCII text files (TXT and
CSV formats) and MS Excel XML Spreadsheet files (XML format) by selecting
Actions > Export Table. For more information on exporting table data, see
"Exporting Tables to Text Files and Spreadsheets" on page 86.
4. On the Display tab, specify how to display point analysis results on the map according to any input or calculated
parameter. For more information on defining display properties, see "Setting the Display Properties of Objects" on
page 51.
5. Once you have defined the point analysis parameters, you can calculate it immediately or you can save it and calculate
it later:
Calculate: Click Calculate to save the point analysis and calculate it immediately.
OK: Click OK to save the point analysis without calculating it. You can calculate it later by opening the point analysis
properties and clicking the Calculate button.
Once Atoll has finished calculating the point analysis, the results are displayed in the map window. You can also access the
analysis results in a table format. For more information, see "Viewing Point Analysis Results" on page 1005.
You can also organise point analyses in folders under the Multi-point Analysis folder by creating folders under the Multi-point
Analysis folder in the Network explorer. Folders may contain one or more point analyses items. You can move point analyses
items from one folder to another and rename folders.
12.2.7.6.2
2. Click Close.
1005
When it is cleared, only the defined Distance will be used to allocate neighbours to a reference transmitter.
When it is selected, click Define to open the Coverage Conditions dialog box:
GSM
- Intra-technology planning: see "Coverage Conditions" on page 323
- Inter-technology planning: see "Coverage Conditions" on page 324
UMTS
- Intra-technology planning: see "Coverage Conditions" on page 560
- Inter-technology planning: see "Coverage Conditions" on page 609
LTE
- Intra-technology planning: see "Coverage Conditions" on page 904
- Inter-technology planning: see "Coverage Conditions" on page 956
1006
You can import or create traffic maps and use them as a basis for dimensioning (see "Studying GSM/GPRS/EDGE Network Capacity" on page 325 in the GSM GPRS EDGE section).
AT332_UMR_E0
You can define them manually either on the TRXs tab of each transmitters Properties dialog box or in the Subcells
table (see "Modifying a Subcell" on page 290).
Once you have the required number of TRXs, manually or automatically create a frequency plan.
Allocating frequencies, BSICs, HSNs, and MAIOs is explained in "Allocating Frequencies, BSICs, HSNs, MALs, MAIOs" on
page 340
Using the optional Atoll module is explained in "Automatic Frequency Planning" on page 391.
Allocating and planning scrambling codes is explained in "Planning Scrambling Codes" on page 562.
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 3GPP multi-RAT 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 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.
ACP uses user-defined objectives to evaluate the optimisation, as well as to calculate its implementation cost. Once you have
defined the objectives and the network parameters to be optimised, ACP uses an efficient global search algorithm to test
many network configurations and propose the reconfigurations that best meet the objectives. ACP presents the changes
ordered from the most to the least beneficial, allowing phased implementation or implementation of just a subset of the
suggested changes.
ACP is technology-independent and can be used to optimise networks using different radio access technologies. Chapter 17:
Automatic Cell Planning explains how you configure the ACP module, how you create and run an optimisation setup, and how
you can view the results of an optimisation. In this section, only the concepts specific to 3GPP multi-RAT networks are
explained:
For information on setting objective parameters, see "Setting Objective Parameters" on page 1329.
1007
If you are modelling GSM/GPRS/EDGE, see "Analysing Network Performance Using Drive Test Data" on page 471.
If you are modelling UMTS HSPA , see "Analysing Network Performance Using Drive Test Data" on page 593
If you are modelling LTE, see "Analysing Network Performance Using Drive Test Data" on page 942.
Select File > Open or File > New > From an Existing Database.
The main and linked documents must have the same geographic coordinate systems.
1008
AT332_UMR_E0
1009
1010
Chapter 13
3GPP2 MultiRAT Networks
This chapter provides
information on using Atoll to
design, analyse, and
optimise a multi-RAT
network.
1012
AT332_UMR_E0
).
You can open an existing Atoll 3GPP2 multi-RAT document by selecting File > Open.
Creating a new Atoll 3GPP2 multi-RAT document is explained in "Creating a Standalone Document" on page 35.
).
You can add and modify the following elements of base stations:
You can also add base stations using a base station template (see "Creating a Base Station" on page 1015).
1013
) from the analysis of base stations: "Studying Base Stations" on page 1017
).
).
6. For the LTE part of the network, allocate frequencies and physical cell IDs (
and
).
7. Before making more advanced coverage predictions, you need to define cell load conditions ( 8 ).
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 (see Chapter 6:
Traffic and Capacity Planning).
You can define them manually in CDMA ("Setting the Reverse Link Load Factor and the Forward Link Total Power"
on page 656) and LTE ("Setting Cell Loads and Noise Rise Values" on page 879).
1014
AT332_UMR_E0
A n te n n a
- A z im u t h
- M e c h a n i c a l t i lt
TMA
A n te n n a
- H e ig h t
F e e d e r C a b le
T r a n s m it t e r
- N o is e fig u r e
- Pow er
S it e
- X , Y c o o r d in a t e s
To create a CDMA base station, see "Creating a CDMA Base Station" on page 630
To create an LTE base station, see "Creating LTE Base Stations" on page 853.
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. Because a 3GPP2 multi-RAT document models several technologies, the new
transmitter will be created using the technology (CDMA or LTE) of the station template
currently selected in the toolbar.
1015
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 41.
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.
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 a Table Record" on page 83.
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 and Spreadsheets" on page 86. For information on importing table data, see "Importing Tables from Text Files" on page 88.
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 291.
1016
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 "Associating a
Label to an Object" on page 53.
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,
AT332_UMR_E0
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 "Associating a Tip Text to an Object" on page 54.
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.
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 "Setting the Display Type" on page 52.
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 (
same site with the same azimuth, you can differentiate them by selecting different symbols for each (
For information on defining the transmitter symbol, see "Setting the Display Type" on page 52.
and
).
To create a CDMA remote antenna, see "Creating a Remote Antenna" on page 649
To create a LTE remote antenna, see "Creating Remote Antennas" on page 870
To study CDMA base stations, see "Studying CDMA Base Stations" on page 652
To study LTE base stations, see "Studying LTE Base Stations" on page 874.
Some technology-specific coverage predictions use terminal, mobility type, and service parameters in calculations. For information on these parameters, see "Service and User Modelling" on page 241.
This section covers the following topics:
1017
In CDMA: the DL total power and UL load factor (defined at the CDMA cell level)
In LTE: the allocated frequency plan, the DL traffic load and UL noise rise (defined at the LTE cell level).
For the purpose of these predictions, each pixel is considered a non-interfering receiver with a defined service, mobility type,
and terminal as explained in "Service and User Modelling" on page 241.
The following 3GPP2 Multi-RAT coverage predictions are explained in this section:
13.2.7.1.1
The CDMA part is based on the CDMA Effective Service Area Analysis (EbNt) (DL+UL) analysis, as explained in "Studying the Effective Service Area" on page 660.
The LTE part is based on the LTE Effective Service Area Analysis (DL+UL), as explained in "Studying the Effective Service Area" on page 886.
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 by clicking
the Calculate button (
The progress of the calculation, as well as any messages, are displayed in the Events viewer.
1018
AT332_UMR_E0
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
13.2.7.1.2
The CDMA part is based on the Service Area Analysis (EbNt) (DL) prediction, as explained in "Studying 1xRTT Forward
and Reverse Link Service Areas (EbNt)" on page 658 and "Studying the Forward Link EV-DO Throughput" on page 659.
The 3GPP2 multi-RAT effective RLC and application throughputs are respectively obtained from the effective RLC and
application throughputs of the 1xRTT or the 1xEV-DO layer.
The LTE part is based on the LTE Coverage by Throughput (DL), as explained in "Making a Coverage Prediction by
Throughput" on page 888.
The 3GPP2 multi-RAT effective RLC and application throughputs are respectively obtained from the effective RLC
channel throughput (DL) and the application channel throughput (DL) coverage predictions.
Effective RLC Throughput: The throughput on the RLC layer that a cell can provide to the selected terminal per pixel
taking into account possible transmission errors (BLER) for the highest priority technology.
Max Effective RLC Throughput: The maximum throughput on the RLC layer that a cell can provide to the selected terminal per pixel taking into account possible transmission errors (BLER), considering all available technologies.
Application Throughput: The throughput on the application layer that a cell can provide to the selected terminal per
pixel taking into account possible transmission errors (BLER) for the highest priority technology.
Max Application Throughput: the maximum throughput on the application layer that a cell can provide to the selected
terminal per pixel taking into account possible transmission errors (BLER), considering all available technologies.
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 by clicking
the Calculate button (
The progress of the calculation, as well as any messages, are displayed in the Events viewer.
1019
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
13.2.7.2.1
13.2.7.2.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.
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 13.3).
13.2.7.3.1
"Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 1020.
"Generating a Coverage Prediction Report" on page 1021.
"Exporting a Coverage Prediction Report" on page 1023.
1020
AT332_UMR_E0
Draw Polygon
i.
Click once on the map to start drawing the focus zone or hot spot.
ii. Click once on the map to define each point on the map where the border of the focus zone or hot spot changes
direction.
iii. Click twice to finish drawing and close the focus zone or hot spot.
Draw Rectangle
i.
Click the point on the map that will be one corner of the rectangle that will define the focus zone or hot spot.
ii. Drag to the opposite corner of the rectangle that will define the focus zone or hot spot. When you release the
mouse, the focus zone or hot spot will be created from the rectangle defined by the two corners.
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 explorer, it will no longer be displayed but will still be taken into account.
You can also create a focus or hot spot as follows:
You can save the focus zone or hot spots, so that you can use it in a different Atoll
document, in the following ways:
13.2.7.3.2
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 104.
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 in the Geo
explorer and selecting Export from the context menu.
You can include population statistics in the focus or hot spot by importing a population map. For information on importing maps, see "Importing Raster Format Geo
Data Files" on page 120.
1021
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 dialog box 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 dialog box appears.
b. In the Save As dialog box, 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 dialog
box. 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 generate a report for all the coverage predictions currently displayed on the map:
1. Select the Network explorer.
2. Click the Expand button ( ) to expand the Predictions folder.
3. Select the check box in front of each coverage prediction that you want to include in the report.
4. Right-click the Predictions folder. The context menu appears.
5. Select Generate Report from the context menu. The Columns to Be Displayed dialog box appears.
In case a hot spot was imported in your Atoll document, additional fields will appear at the bottom of the Columns to
Be Displayed dialog box if the hot spot description contains parameters other than Atoll-specific parameters.
6. 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
1022
AT332_UMR_E0
By default, the ranges which do not contain any pixels do not appear in the report. By
setting an option in the Atoll.ini file, you can include these ranges in the report. For more
information, see the Administrator Manual.
You can include population statistics in the focus zone or hot spots by importing a population map. For information on importing maps, see "Importing Raster Format Geo Data Files" on page 120. 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" on page 50.
2. Display the report as explained above.
3. Select Format > Display Columns. The Columns to Be Displayed dialog box appears.
4. Select the following columns, where "Population" is the name of the folder in the Geo explorer containing the population map:
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 136.
13.2.7.3.3
2. In the Save As dialog box, enter the File name and select the format from the Save as type list:
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 91.
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 "Geographic Export Zone" on page 68.
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 210.
1023
Intersection: This display mode shows the area where both coverage predictions overlap (for example, pixels covered
by both predictions are displayed in red).
Merge: This display mode shows the area that is covered by either of the coverage predictions (for example, pixels
covered by at least one of the 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 mode 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).
Value Difference: This display mode shows the dB difference between any two coverage predictions by signal level.
This display option will not be available if the coverage predictions were calculated using different resolutions.
1024
AT332_UMR_E0
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 base station (see Figure 13.5).
Figure 13.5: Signal level coverage prediction of network with new base station
Now you can compare the two coverage predictions.
To compare two coverage 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 dialog box 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 names and
resolutions.
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
Merge
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 13.6, shows clearly the area covered only by the new
base station.
1025
1026
AT332_UMR_E0
Intersection
Merge
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 13.9, shows clearly the increase in coverage due at the
change in antenna tilt.
1027
When it is cleared, only the defined Distance will be used to allocate neighbours to a reference transmitter.
When it is selected, click Define to open the Coverage Conditions dialog box:
CDMA
- Intra-technology planning: see "Coverage Conditions" on page 674
- Inter-technology planning: see "Coverage Conditions" on page 719
LTE
- Intra-technology planning: see "Coverage Conditions" on page 904
- Inter-technology planning: see "Coverage Conditions" on page 956
1028
AT332_UMR_E0
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 3GPP2 multi-RAT 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 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.
ACP uses user-defined objectives to evaluate the optimisation, as well as to calculate its implementation cost. Once you have
defined the objectives and the network parameters to be optimised, ACP uses an efficient global search algorithm to test
many network configurations and propose the reconfigurations that best meet the objectives. ACP presents the changes
ordered from the most to the least beneficial, allowing phased implementation or implementation of just a subset of the
suggested changes.
ACP is technology-independent and can be used to optimise networks using different radio access technologies. Chapter 17:
Automatic Cell Planning explains how you configure the ACP module, how you create and run an optimisation setup, and how
you can view the results of an optimisation. In this section, only the concepts specific to 3GPP2 multi-RAT networks are
explained:
For information on setting objective parameters, see "Setting Objective Parameters" on page 1329.
1029
If you are modelling CDMA2000, see "Analysing Network Performance Using Drive Test Data" on page 701
If you are modelling LTE, see "Analysing Network Performance Using Drive Test Data" on page 942
Select File > Open or File > New > From an Existing Database.
The main and linked documents must have the same geographic coordinate systems.
1030
AT332_UMR_E0
The same process can be used to display in the main document any folder or folder item of the linked document that has a
Make Accessible In option available in its context menu.
Once folders are linked, you can access their properties and the properties of the items they contain from either documents.
Any changes you make in a linked folder are taken into account in both documents.
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 re-open the linked document in Atoll by right-clicking the
linked item in the explorer window of the main document, and selecting Open Linked Document.
1031
1032
Chapter 14
WiMAX BWA
Networks
This chapter covers the following topics:
1034
AT332_UMR_E0
Signal levels
The carrier-to-interference-and-noise ratio
Service areas and radio bearer coverage
Coverage predictions that depend on the network traffic loads can be created from either Monte Carlo simulation results or
from a user-defined network load configuration (uplink and downlink traffic loads, and uplink noise rise). GSM GPRS EDGE,
CDMA2000, UMTS HSPA, TD-SCDMA, and LTE networks can be planned in the same Atoll session.
Before working with the Atoll WiMAX module for the first time, it is highly recommended
to go through the "Glossary of WiMAX Terms" on page 1160. This will help you get accustomed to the terminology used in Atoll.
You can open an existing Atoll document by selecting File > Open.
You can create an Atoll document as explained in Chapter 1: Working Environment.
You can also add base stations using a station template (see "Placing a New Base Station Using a Station Template" on
page 1044).
3. Carry out basic coverage predictions. See "Signal Level Coverage Predictions" on page 1059.
4. Allocate neighbours. See "Planning Neighbours" on page 1083.
5. Allocate frequencies. See "Planning Frequencies" on page 1087.
6. Allocate preamble indexes. See "Planning Preamble Indexes" on page 1089.
7. Before making more advanced coverage predictions, you need to define cell load conditions in one of the following
ways:
You can generate realistic cell load conditions by creating a simulation based on traffic maps (see "Studying
WiMAX Network Capacity" on page 1102).
You can define cell load conditions manually either on the Cells tab of each transmitter Properties dialog box or
in the Cells table (see "Creating or Modifying a Cell" on page 1044).
8. Make WiMAX-specific signal quality coverage predictions using the defined cell load conditions. See "WiMAX Coverage Predictions" on page 1062.
1035
9. If necessary, modify network parameters to study the network with a different frequency plan. After modifying the
network frequency plan, you must perform steps 7 and 8 again.
1
7a
7d
7c
7b
10
1036
AT332_UMR_E0
Name: A default name is proposed 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 .
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 dialog box afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 57.
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.
Backhaul Tab
Backhaul throughputs: You can specify the maximum backhaul throughputs supported in downlink and uplink by the
site. Enter the capacity of the backhaul links between sites and serving gateways. The maximum backhaul throughputs
that you enter here are taken into account as backhaul constraints in Monte Carlo simulations.
Name: By default, the transmitter is named after the site it is on, suffixed with an underscore and a number.
You can enter a name for the transmitter. However, it is better to use the name assigned
by Atoll to ensure consistency. 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. For information on the site Properties dialog box, see "Site
Properties" on page 1037. You can click the New button to create a site for the transmitter.
Shared antenna: This field identifies the transmitters, repeaters, and remote antennas located at the same site or on
sites with the same position and that share the same antenna. The entry in the field must be the same for all transmitters, repeaters, and remote antennas sharing the same antenna. When changes are made to the position offset
(Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same
1037
changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. This field is
also used for dual-band transmitters to synchronise antenna parameters for different frequency bands.
Under Antenna position, you can modify the position of the antennas (main and secondary):
Relative to site: Select Relative to site to enter the antenna positions as offsets from the site location, and 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.
Transmitter Tab
Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are displayed with
a specific icon in the Transmitters folder of the Network explorer.
Only active transmitters are taken into consideration during calculations.
Transmitter type: Specify whether the transmitter is to be considered as a server. This enables you to model the coexistence of different networks in the same geographic area.
If the transmitter is to be considered as a potential server as well as an interferer, set the transmitter type to Intranetwork (Server and interferer).
If the transmitter is to be considered only as an interferer, set the type to Inter-network (Interferer only). Interferer-only transmitters are ignored by coverage calculations and do not serve any mobile in Monte Carlo simulations.
For more information on how to study interference between co-existing networks, see "Modelling the Co-existence
of Networks" on page 1160.
Transmission/Reception: This area displays the total losses and the noise figure of the transmitter. Losses and noise
are calculated according to the characteristics of the equipment assigned to the transmitter. Equipment can be
assigned using the Equipment Specifications dialog box by clicking the Equipment button. For more information
about assigning equipment to a transmitter, see "Assigning Equipment to a Transmitter" on page 1043.
Any loss related to the noise due to a transmitter repeater is included in the calculated
losses. Atoll always considers the values in the Real boxes in coverage predictions even if
they are different from the values in the Calculated boxes. The information in the real
Noise figure box is calculated from the information you entered in the Equipment Specifications dialog box. You can modify the real Total losses at transmission and reception and
the real Noise figure at reception. 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 given by the DTM. If the transmitter is situated on a building, the height entered must include
the height of building.
AAS power combining gain: The AAS power combining gain is calculated automatically depending on the number
of antenna elements of the smart antenna equipment, if any, assigned to the transmitter. This gain is applied to
the downlink transmission power for preamble and other signals transmitted using the main antenna.
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.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on page 159
Mechanical Azimuth, Mechanical Downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt display additional antenna parameters.
1038
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
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.
AT332_UMR_E0
Smart antenna: Under Smart antenna, the smart antenna equipment is available in the Equipment list. You can
click the Browse button to access the properties of the smart antenna equipment. When you select a smart
antenna equipment, you can choose whether to keep the current main antenna model or to replace it with the
main antenna model defined for the selected smart antenna equipment, if any. For more information on smart
antenna equipment, see "Defining Smart Antenna Equipment" on page 1147.
Number of MIMO antennas: Enter the number of antennas used for MIMO in the Transmission and Reception
fields. For more information on how the number of MIMO antennas are used, see "Multiple Input Multiple Output
(MIMO) Systems" on page 1148.
Secondary antennas: 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.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
The transmission power is divided among the main and secondary antennas. This
is not compatible with smart antennas. You must not assign smart antennas to
transmitters with secondary antennas, and vice versa.
In calculations, repeaters and remote antennas are transparent to the donor transmitters and the served users. For example, beamforming smart antennas at donor
transmitters create beams directly towards the served users, and not towards the
repeater or remote antenna that covers the users. This results in a combined signal
level received from the transmitter using the smart antenna and from the repeater
or remote antenna. If this approach does not match how your equipment works,
you must not assign smart antennas to transmitters with repeaters and remote
antennas, and vice versa. This is also true for MIMO.
The main antenna is used to transmit the preamble. Coverage predictions based on the preamble signal are performed
using the main antenna. The main antenna is also used for traffic signals if there is no smart antenna equipment
selected for the transmitter, or if the permutation zones do not support AAS.
If a smart antenna equipment is assigned to the transmitter and the permutation zones support AAS, traffic data is
transmitted and received using the smart antenna, whereas the preamble is transmitted using the main antenna.
Cells Tab
When you create a transmitter, Atoll automatically creates a cell for the transmitter using the properties of the currently
selected station template.
The Cells tab enables you to configure the properties for every cell of a transmitter. For more information on the properties
of a cell, see "Cell Properties" on page 1039.
Propagation Tab
Transmitters are taken into account during calculations. Therefore, you must set the propagation parameters. On the Propagation tab, you can modify the Propagation model, Radius, and Resolution for both the Main matrix and the Extended
matrix. For information on propagation models, see "Assigning Propagation Parameters" on page 187.
Display Tab
On the Display tab, you can modify how a transmitter will be displayed. For information on changing display properties, see
"Setting the Display Properties of Objects" on page 51.
1039
You can also display the properties of a cell by double-clicking the cell in the Site explorer.
Name: By default, Atoll names the cell after its transmitter, adding a suffix in parentheses. If you change transmitter
name, 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 Administrator Manual.
Active: If this cell is to be active, you must select the Active check box.
Order: The display order of a cell within the transmitter. This value is used to determine the order in which information
related to a cell will be displayed in the Network explorer and on the map. This field is automatically filled by Atoll but
you can change these default values to display cells in a user-defined order.
The consistency between values stored in this field is verified by Atoll. However, inconsistencies may arise when tools other than Atoll modify the database. You can check for inconsistencies in the cell display order and fix them by selecting Data Audit > Cell Display Order
Check in the Document menu.
Layer: The coverage layer to which the cell belongs. This information is used to determine the serving cell. For more
information on defining layers, see "Defining Network Deployment Layers" on page 1137. For more information on
the different cell selection methods, see "Network Settings" on page 1134.
BSID: The base station ID.
Frequency band: The cell frequency band from the frequency band list.
Channel number: The number of the channel from the list of available channels.
For calculating path loss matrices of a multi-cell transmitter, Atoll uses the downlink start
frequency of the frequency band assigned to the cell with the highest priority layer.
Channel allocation status: The status of the channel allocated to the cell:
Not allocated: The AFP considers a Not allocated channel modifiable without cost.
Allocated: The AFP considers an Allocated channel modifiable but only if absolutely necessary.
Locked: The AFP considers a Locked channel not modifiable.
For more information on the AFP, see "Configuring Network Parameters Using the AFP" on page 1084.
Preamble index domain: The preamble index domain to which the allocated preamble index belongs. This and the
reuse distance are used by the AFP for preamble index allocation.
Preamble index: The preamble index of the cell. It is an integer value from 0 to 113. The preamble indices are defined
in the IEEE 802.16 specifications. They provide the segment number and cell permbase (IDCell for the first permutation zone of the frame).
Cell PermBase: The cell permbase corresponding to the current preamble index. This value is determined automatically from the preamble index.
Preamble index status: The status of the preamble index currently assigned to the cell:
Not allocated: The AFP considers a Not allocated preamble index modifiable without cost.
Allocated: The AFP considers an Allocated preamble index modifiable but only if absolutely necessary.
Locked: The AFP considers a Locked preamble index not modifiable.
Segment: The segment number corresponding to the current preamble index. This value is determined automatically
from the preamble index.
Segment locked: Whether the segment number corresponding to the current preamble index is locked or not. If the
segment is not locked, the AFP might change the cells preamble index depending on the preamble index status. If the
segment is locked, the AFP can only change the cells preamble index such that the cells segment number does not
change.
DL Zone PermBase: The zone permbase for a downlink permutation zone. It is an integer value from 0 to 31.
DL Zone PermBase status: The status of the downlink permutation zone permbase currently assigned to the cell:
Not allocated: The AFP considers a Not allocated downlink permutation zone permbase modifiable without cost.
Allocated: The AFP considers an Allocated downlink permutation zone permbase modifiable but only if absolutely
necessary.
Locked: The AFP considers a Locked downlink permutation zone permbase not modifiable.
UL Zone PermBase: The zone permbase for an uplink permutation zone. It is an integer value from 0 to 69.
UL Zone PermBase status: The status of the uplink permutation zone permbase currently assigned to the cell:
1040
Not allocated: The AFP considers a Not allocated uplink permutation zone permbase modifiable without cost.
AT332_UMR_E0
Allocated: The AFP considers an Allocated uplink permutation zone permbase modifiable but only if absolutely
necessary.
Locked: The AFP considers a Locked uplink permutation zone permbase not modifiable.
Reuse distance: The reuse distance after which the channel, preamble index, downlink, or uplink permbases assigned
to this cell can be assigned to another cell by the AFP.
Preamble power (dBm): The cells transmission power over the preamble of the frame.
Traffic power reduction (dB): The power reduction to be subtracted from the power defined in the Preamble power
(dBm) field to determine the transmission power of the traffic subcarriers during the loaded part of the frame. Traffic
subcarriers are off during the empty part of the frame.
Pilot power reduction (dB): The power reduction to be subtracted from the power defined in the Preamble power
(dBm) field to determine the transmission power of the pilot subcarriers during the loaded part of the frame.
Idle pilot power reduction (dB): The power reduction to be subtracted from the power defined in the Preamble
power (dBm) field to determine the transmission power of the pilot subcarriers during the empty part of the frame.
If the cells transmitter has a smart antenna equipment assigned, the transmission powers of cell increase by
10 Log n (in dB), where n is the number of antenna elements of the smart antenna. This gain in the transmission
power is referred to as the AAS power combining gain.
Preamble C/N threshold (dB): The minimum preamble C/N required for a user to be connected to the cell. The preamble C/N is compared with this threshold to determine whether or not a user can be connected to a cell.
Frame configuration: The frame configuration used by the cell. For more information on frame configurations, see
"Defining Frame Configurations" on page 1138.
DL:UL ratio: The number of symbol durations available in the downlink and uplink subframes for the cell. This field is
not stored in the Cells table. It is automatically calculated and its value depends on the cells channel bandwidth, sampling factor, and cyclic prefix as well as global network settings including the DL:UL ratio and frame duration.
Reception equipment: You can select the cell reception equipment from the reception equipment list. For more information, see "Defining WiMAX Reception Equipment" on page 1140.
Scheduler: The scheduler used by the cell for resource allocation during Monte Carlo simulations. You can select the
scheduler from the list of schedulers available in the Schedulers table. For more information see "Defining WiMAX
Schedulers" on page 1143.
Traffic load (DL) (%): The downlink traffic load percentage. This can be user-defined or an output of Monte Carlo simulations.
Traffic load (UL) (%): The uplink traffic load percentage. This can be user-defined or an output of Monte Carlo simulations.
UL noise rise (dB): The uplink noise rise in dB. This can be user-defined or an output of Monte Carlo simulations. This
is the global value of uplink noise rise including the inter-technology uplink noise rise.
Max traffic load (DL) (%): The downlink traffic load not to be exceeded. This limit can be taken into account during
Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have a downlink
traffic load greater than this maximum.
Max traffic load (UL) (%): The uplink traffic load not to be exceeded. This limit can be taken into account during Monte
Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have an uplink traffic
load greater than this maximum.
Segmentation usage (DL) (%): You can set the percentage of the total downlink traffic load that corresponds to the
segmented part of the frame. For example, if the downlink traffic load is 80%, and you set the segmentation usage to
50%, it means that 40% downlink traffic load is on the segmented part of the frame while the other 40% is on the nonsegmented part. You can set the value of segmentation usage manually or store a calculated value from simulation
results.
To see examples of how to set up cells with and without segmentation, and how to set up cells with PUSC, FUSC, and
permutation zones of other subchannel allocation modes, see "Tips and Tricks" on page 1152.
Segmentation switching point (DL): The number of downlink OFDM symbol durations that correspond to the average
length of the segmented permutation zone. This column is automatically calculated from Segmentation usage (DL)
(%).
Segmented zone UL noise rise (dB): The uplink noise rise in dB for the segmented permutation zone, if any. Zone 8
(PUSC UL) can be segmented in the frame configuration properties. This can be user-defined or an output of Monte
Carlo simulations.
Additional UL noise rise: This noise rise represents the interference created by the mobiles and base stations of an
external network on this cell on the uplink. This noise rise will be taken into account in all uplink interference-based
calculations involving this cell in Monte Carlo simulations. It is not used in predictions where Atoll calculates the uplink
total interference from the uplink noise rise which includes inter-technology uplink interference. For more information on inter-technology interference, see "Modelling Inter-technology Interference" on page 1150.
Additional DL noise rise: This noise rise represents the interference created by the 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 interferencebased calculations involving this cell. For more information on inter-technology interference, see "Modelling Intertechnology Interference" on page 1150.
AMS & MU-MIMO threshold (dB): For AMS, the preamble C/N or C/(I+N) threshold, according to the option set in the
Advanced parameters ("Network Settings" on page 1134), for switching from SU-MIMO to STTD/MRC as the preamble signal conditions get worse than the given value. For MU-MIMO, it is the minimum required preamble CNR for
1041
using MU-MIMO. For more information on Adaptive MIMO switching, see "Multiple Input Multiple Output (MIMO)
Systems" on page 1148.
MU-MIMO capacity gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO. This can be userdefined or an output of Monte Carlo simulations. In uplink throughput coverage predictions, the cell capacity will be
multiplied by this gain on pixels where MU-MIMO is used.
AAS usage (DL) (%): This is the percentage of the total downlink traffic load that corresponds to the traffic loads of the
users supported by the smart antenna equipment. For example, if the downlink traffic load is 80%, and you set the
AAS usage to 50%, it means that 40% downlink traffic load is supported by the smart antenna equipment while the
other 40% is supported by the main antenna. AAS usage is calculated during Monte Carlo simulations, and cannot be
modified manually because the AAS usage values correspond to the angular distributions of interference.
Angular distributions of interference (AAS): This field stores the simulation results generated for transmitters using
a smart antenna. During Monte Carlo simulations, both smart antenna models available in Atoll, conventional beamformer and optimum beamformer, perform beamforming in downlink. In uplink, the conventional beamformer performs beamforming only whereas the optimum beamformer uses the MMSE (Minimum Mean Square Error) algorithm
to cancel interference. After the simulations, the smart antenna results can be stored in the cell properties. The results
stored in this field are the angular distributions of the downlink traffic power spectral density and the uplink noise rise.
You can view these patterns in the Cells table. You can display the downlink results diagram taking into account the
effect of the antenna pattern of the single element. For more information, see the Administrator Manual.
Number of users (DL): The number of users connected to the cell in the downlink. This can be user-defined or an
output of Monte Carlo simulations.
Number of users (UL): The number of users connected to the cell in the uplink. This can be user-defined or an output
of Monte Carlo simulations.
Max number of users: The maximum number of simultaneous users supported by the cell.
Max number of intra-technology neighbours: The maximum number of WiMAX neighbours that the cell can have.
Max number of inter-technology neighbours: The maximum number of other technology neighbours that the cell can
have.
Neighbours: You can access a dialog box in which you can set both intra-technology and inter-technology neighbours
by clicking the Browse button. For information on defining neighbours, see "Neighbour Planning" on page 223.
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.
1042
AT332_UMR_E0
Alternatively, you can create a site by right-clicking the Sites folder, selecting New from the
context menu, and entering coordinates and properties as described in "Site Properties"
on page 1037.
To create a transmitter, right-click the Transmitters folder, and select New from the context menu.
To modify an existing transmitter, expand the Transmitters folder, right-click the transmitter that you want to
modify, and select Properties from the context menu.
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 in the Network explorer and selecting Open Table
from the context menu. For information on copying and pasting data, see "Copying
and Pasting in Tables" on page 83.
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.
1043
TMA: Select a tower-mounted amplifier (TMA) from the list. Click the Browse button to access the properties of
the TMA. For information on creating a TMA, see "Defining TMA Equipment" on page 161.
Feeder: Select a feeder cable from the list. Click the Browse button to access the properties of the feeder. For
information on creating a feeder cable, see "Defining Feeder Cables" on page 161.
Transmitter: Select a transmitter equipment from the Transmitter list. Click the Browse button to access the properties of the transmitter equipment. For information on creating transmitter equipment, see "Defining Transmitter Equipment" on page 162.
Feeder length: Enter the feeder length at transmission and reception.
Miscellaneous losses: Enter any additional losses at transmission and reception. The value must be positive.
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 in the Network explorer 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 83),
or import data into the table (see "Importing Tables from Text Files" on page 88).
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.
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 base station.
To place the base 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 60.
If you let the pointer rest over the base station you have placed, Atoll displays its
tip text with its exact coordinates, allowing you to verify that the location is correct.
1044
AT332_UMR_E0
3. Move the pointer to the site on the map. When the frame appears around the site, indicating it is selected, click to
place the base station.
14.2.2.8.1
The Name of the station template, the number of Sectors, each with a transmitter, the Hexagon radius, which is the
theoretical radius of the hexagonal area covered by each sector, and the Transmitter type, which defines whether the
transmitter belongs to the current network or to another network.
Under Antennas, you can modify the following:
1st sector mechanical azimuth, from which the azimuth of the other sectors are offset to offer complete coverage
of the area, the Height/ground of the antennas from the ground (which is the height over the DTM; if the transmitter is situated on a building, the height entered must include the height of the building), and the Mechanical
downtilt for the antennas.
Electrical Azimuth, Electrical Downtilt, and Additional electrical downtilt display additional antenna parameters.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
Under Main antenna, you can select the main antenna Model.
Under Smart antenna, you can select the smart antenna Equipment used by the transmitter.
Under Number of MIMO Antennas, you can enter the number of antennas used for Transmission and for Reception for MIMO.
Under Path loss matrices, you can modify the following: the Main propagation model, the Main radius, and the Main
resolution, and the Extended propagation model, the Extended radius, and the Extended resolution. For information
on propagation models, see Chapter 4: Radio Calculations and Models.
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.
Transmitter Tab
Active: Select this option to specify whether the transmitter is active. Only active transmitters are taken into consideration during calculations.
Transmission/Reception: This area displays the total losses and the noise figure of the transmitter. Losses and noise
are calculated according to the characteristics of the equipment assigned to the transmitter.
You can click the Equipment button to modify the tower-mounted amplifier (TMA), feeder cables, or transmitter
equipment. For more information, see "Assigning Equipment to a Transmitter" on page 1043.
1045
Any loss related to the noise due to a transmitter repeater is included in the calculated
losses. Atoll always considers the values in the Real boxes in coverage predictions even if
they are different from the values in the Computed boxes. The information in the real
Noise figure box is calculated from the information you entered in the Equipment Specifications dialog box. You can modify the real Total losses at transmission and reception and
the real Noise figure at reception. Any value you enter must be positive.
Cell Tab
Powers: Modify the Preamble power and the power reductions for the data and pilot subcarriers in Traffic power
reduction, Pilot power reduction, and Idle pilot power reduction.
Cell definition per sector: Assign a channel and a preamble index per cell per sector by clicking the Cell definition per
sector button. The Cell Definition per Sector dialog box appears.
Sector: Select the sector for which you want to define cell parameters, that is to say the channel number and preamble index.
Number of cells: Enter the number of cells that the selected sector will have. The number of rows in the grid below
depends on the number of cells that you enter.
For each sector, assign a layer, a channel number, and a preamble index to each cell.
Frequency band, Reception equipment, Frame configuration, Max number of users, Reuse distance, Scheduler, Preamble C/N threshold, and the AMS & MU-MIMO threshold.
Default loads: Enter the default values for DL traffic load, UL traffic load, UL noise rise, Max DL traffic load, Max UL
traffic load, and DL segmentation usage.
Additional interference: Set the DL noise rise and the UL noise rise. For more information on inter-technology interference, see "Modelling Inter-technology Interference" on page 1150.
Neighbours Tab
Max number of neighbours: Set the maximum numbers of Intra-technology and Inter-technology neighbours.
Other Properties Tab
The Other Properties tab only appears if you have defined additional fields in the Sites table, or if you have defined
an additional field in the Station Template Properties dialog box.
14.2.2.8.2
14.2.2.8.3
1046
AT332_UMR_E0
14.2.2.8.4
14.2.2.8.5
14.2.2.8.6
Quickly create a base station with the same settings as an original one in order to study the effect of a new base station
on the coverage and capacity of the network, and
Quickly create an homogeneous network with base stations that have the same characteristics.
If you want to duplicate the base station without the intra and inter-technology neighbours of its transmitters,
select Duplicate > Without Neighbours.
If you want to duplicate the base station along with the lists of intra and inter-technology neighbours of its transmitters, select Duplicate > With Outward Neighbours.
2. Place the new base station on the map using the mouse:
To create a duplicate base station and site, move the pointer over the map to where you would like to place the
duplicate. The exact coordinates of the pointers current location are visible in the Status bar.
To place the duplicate base station on an existing site, move the pointer over the existing site where you would
like to place the duplicate. When the pointer is over the site, the site is automatically selected. The exact coordinates of the pointers current location are visible in the Status bar.
To place the base 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 60.
If you let the pointer rest over the base station you have placed, Atoll displays tip
text with its exact coordinates, allowing you to verify that the location is correct.
1047
A new base station is placed on the map. If the duplicate base station was placed on a new site, the site, transmitters,
and cells of the new station have the same names as the site, transmitters, and cells of the original station with each
name marked as "Copy of." The site, transmitters, and cells of the duplicate station have the same settings as those
of the original station. If the duplicate base station was placed on an existing site, the transmitters, and cells of the
new base station have the same names as the transmitters, and cells of the original base station with each name
preceded by the name of the site on which the duplicate was placed.
All the remote antennas and repeaters of any transmitter on the original site are also duplicated.
Any duplicated remote antennas and repeaters will retain the same donor transmitter as
the original. If you want the duplicated remote antenna or repeater to use a transmitter
on the duplicated base station, you must change the donor transmitter manually.
You can also place a series of duplicate base stations by pressing and holding Ctrl in step 3. and clicking to place each
duplicate base station.
For more information on the site, transmitter, and cell properties, see "Definition of a WiMAX Base Station" on page 1037.
) in the Radio Planning toolbar. The Point Analysis window opens and the pointer
changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and the
receiver. You can move the receiver on the map (see "Moving the Receiver on the Map" on page 203).
3. Select the Profile view. The Profile view displays the profile between the transmitter and the receiver with clutter
heights.
You can select a different transmitter.
Displays data,
including
received signal,
shadowing
margin, cell
edge coverage
probability,
propagation
model used,
and transmitter-receiver
distance.
Fresnel ellipsoid
Line of sight
1048
AT332_UMR_E0
intersects the Fresnel ellipsoid the most. Propagation models that use a 3 knife-edge Deygout diffraction method may
also display two additional diffraction edges. The total attenuation is displayed above the main diffraction edge.
The results of the analysis are displayed at the top of the Profile view:
The received signal strength from the selected transmitter for the cell with the highest reference signal power
The propagation model used
The shadowing margin and the indoor loss (if selected)
The distance between the transmitter and the receiver.
4. If needed, select an other transmitter from the list. You can click the Properties button (
properties.
5. Click the Options button (
) to display the Calculation Options dialog box and change the following:
Change the X and Y coordinates to change the current position of the receiver.
Select the Shadowing taken into account check box and enter a Cell edge coverage probability. For more information, see "Taking Shadowing into Account in Point Analyses" on page 204.
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. Indoor losses are defined per frequency per
clutter class. For more information, see "Taking Indoor Losses into Account" on page 203.
6. In the Profile view toolbar, you can use the following tools:
) to view the geographic profile between the transmitter and the receiver.
) again to view the radio signal path between the transmitter and the
Click the Detailed Report button ( ) to display a text document with details on the displayed profile analysis.
The detailed report is only available for the Standard Propagation Model.
Click the Copy button (
) to copy the content of the view and paste it as a graphic into a graphic editing or wordprocessing programme.
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.
The table you copy 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 83.
Importing data: If you have base station 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
1049
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 and Spreadsheets" on page 86. For information on importing table data, see "Importing Tables from Text Files" on page 88.
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 in the label will make it harder to distinguish the information you are looking for. For
information on defining the label, see "Associating a Label to an Object" on page 53.
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 "Associating a Tip Text to an Object" on page 54.
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 transmitters. 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 "Setting the Display Type" on page 52.
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 (
same site with the same azimuth, you can differentiate them by selecting different symbols for each (
For information on defining the transmitter symbol, see "Setting the Display Type" on page 52.
and
).
1050
AT332_UMR_E0
Name: Specify the name of the repeater. By default, repeaters are named "SiteX_Y_RepZ" where "X" is the donor site
number, "Y" the donor transmitter number, and "Z" a number assigned to the repeater when it was created.
If the donor is a remote antenna or another repeater, then "RepZ" is preceded by "RemA_"
or "RepB_" where "A" and "B" identify the donor remote antenna and the donor repeater.
Donor: The donor of a repeater can be a transmitter, a remote antenna, or another repeater. Click the Browse button
to open the donor Properties dialog box.
Site: Specify the site on which the repeater is located. Click the Browse button to open the site Properties dialog box.
Shared antenna: Specify the identifier (coverage side) of the transmitters, repeaters, and remote antennas that are
located at the same site or on sites with the same position and that share an antenna. The identifier must be the same
for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all
other transmitters, repeaters, and remote antennas defined as having a shared antenna.
Antenna position: If the repeater is not located exactly on the site, you can specify its location.
Relative to site: Select this option if you want to define the position of the repeater relative to the site itself and
then enter the XY offsets.
Coordinates: Select this option to specify the position of the repeater by its X and Y absolute coordinates.
Equipment: Select an equipment from the list. Click the Browse button to open the equipment Properties dialog box.
Amplifier Gain: Specify a gain for the amplifier. The amplifier gain is used in the link budget to evaluate the repeater
total gain.
1051
Donor-repeater link: Specify the type of link between the donor and the repeater:
Air: Select this option to specify an off-air repeater. 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.
Microwave link: Select this option to specify a microwave link and enter the total Link losses for the link between
the donor transmitter and the repeater
Optical fibre link: Select this option to specify an optical fibre link and enter the total Fibre losses for the link
between the donor transmitter and the repeater.
If you want to create a remote antenna, you must select Optical Fibre Link.
Model: Select the antenna model from the list. Click the Browse button to access the access properties.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on page 159
Height/ground: Specify the height of the antenna above the ground. This is added to the altitude of the site as
given by the DTM. If the repeater is situated on a building, the height entered must include the height of building.
Mechanical Azimuth and Mechanical Downtilt: Specify additional antenna parameters.
You can click the Calculate button to update the mechanical azimuth and mechanical
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.
Type: Select the type of feeder from the list. Click the Browse button to access the feeder properties.
Length: Enter the Length of the feeder cable at Transmission and at Reception.
Active: Specify whether the repeater is active. Only active repeaters (displayed in red in the Transmitters folder in the
Network explorer) are calculated.
Total gain: Specify the total gain in downlink and uplink. You can click Calculate to determine the actual gain in both
directions. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply before
clicking the Calculate button.
In downlink, the total gain is applied to preamble, traffic, and pilot powers.
In uplink, the total gain is applied to each terminal power.
The total gain takes into account losses between the donor transmitter and the repeater, donor characteristics (donor
antenna gain, reception feeder losses), amplifier gain, and coverage characteristics (coverage antenna gain, transmission feeder losses).
Antennas:
Height/ground: Specify the height of the antenna above the ground. This is added to the altitude of the site as
given by the DTM. If the repeater is situated on a building, the height entered must include the height of building.
Main antenna:
Model: Select an antenna model from the list. Click the Browse button to access the antenna properties.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
1052
Mechanical Azimuth, Mechanical Downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt: Specify additional antenna parameters.
AT332_UMR_E0
Secondary antennas: Select one or more secondary antennas in the Antenna column and enter their Azimuth,
Mechanical downtilt, Additional electrical downtilt, and % Power.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
Feeders:
Type: Select a type of feeder from the list. You can click the Browse button to access the feeder properties.
Length: Enter the length of the feeder cable at Transmission and at Reception.
Losses:
Propagation Tab
Repeaters are taken into account during calculations. Therefore, you must set the propagation parameters. On the
Propagation tab, you can modify 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 4: Radio
Calculations and Models.
):
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.
1053
When the donor is a transmitter, you can see to which station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter. You can hide the
link by clicking it again.
When the donor is a repeater or a remote antenna, Atoll displays a spider-type link
showing the entire chain down to the donor transmitter. The same spider-type link
is displayed when you click any of the items belonging to the chain is clicked (i.e.,
donor transmitter, any repeater, or any remote antenna).
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 83.
1054
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.
AT332_UMR_E0
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 57) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using
the Mouse" on page 58).
Name: You can change the name of the remote antenna. By default, remote antennas are named "SiteX_Y_RemZ"
where "X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned to the remote
antenna when it was created.
If the donor is a repeater or another remote antenna, then "RemZ" is preceded by "RepA_"
or "RemB_" where "A" and "B" identify the donor repeater and the donor remote antenna.
Donor: Specify whether the donor of the remote antenna is a transmitter, another remote antenna, or a repeater.
Click Browse to open the Properties dialog box of the selected donor.
Site: Specify the site on which the remote antenna is located. Click Browse to open the Properties dialog box of the
selected site.
Shared antenna: Specify the identifier (coverage side) of the transmitters, repeaters, and remote antennas that are
located at the same site or on sites with the same position and that share an antenna. The identifier must be the same
for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all
other transmitters, repeaters, and remote antennas defined as having a shared antenna.
Antenna position: If the remote antenna is not located exactly on the site, you can specify its location.
1055
Relative to site: Select this option to specify the position of the remote antenna relative to the site itself and then
enter the XY offsets.
Coordinates: Select this option to specify the position of the remote antenna by its X and Y absolute coordinates.
Remote antennas do not have assigned equipment.
Donor-Repeater Link: Select Optical fibre link and enter the Fibre losses.
Active: Specify whether the remote antenna is active. Only active remote antennas (displayed in red in the Transmitters folder in the Network explorer) are calculated.
Total gain: Enter the total gain in downlink and uplink. You can click Calculate to determine the actual gain in both
directions. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply before
clicking the Calculate button.
In downlink, the total gain is applied to preamble, traffic, and pilot powers.
In uplink, the total gain is applied to each terminal power.
The total gain takes into account losses between the donor transmitter and the remote antenna.
Antennas:
Height/ground: Specify the height of the antenna above the ground. This is added to 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.
Main antenna:
Model: Select a remote antenna type from the list. Click Browse to access the properties of the remote antenna.
Click Select to open the Antenna Selection Assistant. This assistant lists all the antennas that match the currently selected physical antenna and whose minimum and maximum operating frequencies include the operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
Mechanical Azimuth, Mechanical downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt: Specify additional antenna parameters.
Secondary antennas: Select one or more secondary antennas in the Antenna column and enter their Azimuth,
Mechanical downtilt, Additional electrical downtilt, and % Power.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
Feeders:
Type: Select a type of feeder from the list. Click Browse to access the properties of the feeder.
Length: Enter the length of the feeder cable at Transmission and at Reception.
Losses:
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 4: Radio Calculations and Models.
1056
AT332_UMR_E0
When the donor is a transmitter, you can see to which base station the repeater is
connected by clicking it; Atoll displays a link to the donor transmitter. You can hide
the link by clicking it again.
When the donor is a repeater or a remote antenna, Atoll displays a spider-type link
showing the entire chain down to the donor transmitter. The same spider-type link
is displayed when you click any of the items belonging to the chain is clicked (i.e.,
donor transmitter, any repeater, or any remote antenna).
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 83.
1057
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 57) or its position relative to the site (see "Changing the Antenna Position Relative to the Site
Using the Mouse" on page 58).
1058
Display Resolution
City Centre
5m
City
20 m
County
50 m
State
100 m
Country
AT332_UMR_E0
A read-only Unique ID is generated when you create a coverage prediction. This ID can
later be found between the <GUID> and </GUID> tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
Receiver height: This parameter displays the height of the receiver defined in the Calculation Parameters tab of the
Network Settings Properties dialog box.
Comments: Specify an optional description of comment for the prediction.
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 99. The Group By and Sort buttons are not available when making a so-called
"global" coverage prediction (e.g., signal level coverage prediction).
If you create a coverage prediction from the context menu of the Predictions folder, you
can select the sites using the Group By, Sort, and Filter buttons under Display configuration. However, if you create a coverage prediction from the context menu of the Transmitters folder, only the Filter button is available, because, by creating a coverage prediction
directly from the Transmitters folder, you have effectively already selected the target
sites.
Conditions Tab
The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each
pixel.
At the top of the Conditions tab, you can set the range to be considered for the current prediction.
Server: Select one of the following:
Shadowing taken into account: Select this option to consider shadowing in the prediction. When you select this
option, you can change the Cell edge coverage probability.
Indoor coverage: Select this option to consider indoor losses. Indoor losses are defined per frequency per clutter class.
Channel: Select a channel or carry out the prediction for the "Best" channel of a frequency band or of all frequency
bands. For any transmitter, the best channel is the one whose cell has the highest preamble power.
Display Tab
On the Display tab, you can modify how the results of the coverage prediction will be displayed.
1059
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 coverage prediction more quickly than by creating a 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 104.
The following standard coverage predictions are explained in this section:
14.2.9.2.1
2. Specify the propagation parameters as explained in "Assigning Propagation Parameters" on page 187.
3. 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 dialog box appears.
The Prediction Types dialog box lists the coverage prediction types available. They are divided into Standard Predictions, supplied with Atoll, and Customised Predictions. Unless you have already created some customised predictions, the Customised Predictions list will be empty.
4. Select Coverage by Signal Level (DL) and click OK. A coverage prediction properties dialog box appears.
5. Configure the parameters in the Properties dialog box as described in "WiMAX Prediction Properties" on page 1058.
6. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
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 in the Network explorer. 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 (
1060
).
AT332_UMR_E0
14.2.9.2.2
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
14.2.9.2.3
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window
14.2.9.2.4
1061
When creating a coverage prediction displaying the number of servers, you cannot export
the values per pixel.
4. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
14.2.9.3.1
Highest bearer
Lowest bearer
Throughput scaling factor
Throughput offset
Body loss
Minimum number of subchannels in uplink
You can create a service or modify an existing service by specifying the following parameters in the General tab of the service
Properties dialog box (some fields depend on the type of service you choose):
1062
Name: Atoll proposes a name for the new service, but you can set a more descriptive name.
Type: You can select either Voice or Data as the service type.
Priority: Enter a priority for this service. "0" is the lowest priority.
AT332_UMR_E0
QoS class: Select a QoS class for the service. You have the option to choose from UGS (Unsolicited Grant Service), ErtPS
(Extended Real-Time Polling Service), rtPS (Real-Time Polling Service), nrtPS (Non-Real-Time Polling Service), and BE
(Best Effort). The information about the QoS class used by any service is used by the schedulers for resource allocation.
For more information about how schedulers work in Atoll, see "Defining WiMAX Schedulers" on page 1143.
Activity factor: The uplink and downlink activity factors are used to determine the probability of activity for users
accessing the service during Monte Carlo simulations. For Voice services, this parameter is used when working with
sector traffic maps and user density traffic maps. For Data services, Atoll distributes the users according to the activity
factors when importing user density traffic maps for all activity statuses.
Highest bearer: Select the highest bearer that the service can use in the uplink and downlink. This is considered as an
upper limit during bearer determination.
Lowest bearer: Select the lowest bearer that the service can use in the uplink and downlink. This is considered as a
lower limit during bearer determination.
Max throughput demand: Enter the highest throughput that the service can demand in the uplink and downlink. This
value is not considered for services UGS as the quality of service.
Min throughput demand: Enter the minimum required throughput that the service should have in order to be available in the uplink and downlink. This value is not considered for BE services.
Min number of subchannels: Enter the minimum number of subchannels required for this service in uplink.
Average requested throughput: Enter the average requested throughput for uplink and downlink. The average
requested throughput is used in a simulation during user distribution generation in order to calculate the number of
users attempting a connection.
Application throughput: Under Application throughput, you can set a Scaling factor between the application
throughput and the MAC (Medium Access Control) throughput and a throughput Offset. These parameters model the
header information and other supplementary data that does not appear at the application level.
The application throughput parameters are used in throughput coverage predictions and for application throughput
calculation.
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 3 dB.
For information on creating or modifying a service, see "Creating Services" on page 247.
Modelling Mobility Types
In WiMAX, information about the receiver mobility is required for determining which bearer selection threshold and quality
graph to use from the reception equipment referred to in the terminal or cell. Mobiles used at high speeds and at walking
speeds do not have the same quality characteristics. C/(I+N) requirements for different radio bearers are largely dependent
on mobile speed.
You can create or modify a mobility type by specifying the following parameters in the General tab of the mobility type Properties dialog box:
For information on creating or modifying mobility types, see "Modelling Mobility Types" on page 247.
Modelling Terminals
In WiMAX, a terminal is the user equipment that is used in the network, for example, a mobile phone, a PDA, or a cars onboard navigation device.
You can create or modify a terminal by specifying the following parameters in the General tab of the terminal Properties
dialog box:
Model: Select an antenna model from the list of available antennas. If you do not select an antenna for the terminal, Atoll uses an isotropic antenna in calculations.
1063
In case you do not select an antenna, Atoll uses an isotropic antenna, not an omni-directional antenna, in calculations. An isotropic antenna has spherical radiation patterns in the
horizontal as well as vertical planes.
Gain: Enter the terminal antenna gain if you have not selected an antenna model in the Model field. If you have
selected an antenna, the Gain field is disabled and shows the gain of the selected antenna.
Diversity support: Select the type of antenna diversity techniques supported by the terminal. Antenna diversity
gains will be applied to the users using any terminal type depending on the supported antenna diversity techniques, i.e., AAS, MIMO, or AAS+MIMO. If a terminal that supports AAS+MIMO is connected to a permutation
zone that supports both antenna diversity techniques, both AAS and MIMO gains will be applied.
MIMO: Enter the Number of transmission antennas and the Number of reception antennas available in the terminal.
For information on creating or modifying terminals, see "Modelling Terminals" on page 249.
14.2.9.3.2
Although, you can also set a value for the Traffic load (UL) (%) column as an indication of cells uplink loads, this parameter is not used in the coverage prediction calculations. The measure of interference in the uplink is given by the uplink
noise rise values. For a definition of the values, see "Cell Properties" on page 1039.
To enter the same values in one column for all cells in the table by copying the contents of
one cell into other cells, you can use the Fill Down and Fill Up commands. For more information on working with tables in Atoll, see "Data Tables" on page 75.
14.2.9.3.3
1064
AT332_UMR_E0
transmitter is used to determine the total noise in the uplink. For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1062, "Modelling Terminals" on page 1063,
"Modelling Mobility Types" on page 1063, and "Defining WiMAX Reception Equipment" on page 1140, respectively.
c. 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. The shadowing margin is based
on the model standard deviation.
d. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
4. Click the Display tab. From the Display type list, choose one of the following:
Discrete values: Select "Discrete values" to display the coverage prediction by permutation zones or segment
numbers.
Value intervals: Select "Value intervals" to display the coverage prediction by signal levels or C/N levels.
For information on adjusting the display, see "Setting the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
14.2.9.3.4
1065
b. If you wish, select the network Layers for the determination of best servers. Otherwise, you can calculate the prediction for all layers.
c. Select a Terminal, a Mobility type, and a Service. The Noise figure defined in the terminal types properties dialog
box is used in the coverage prediction to determine the total noise in the downlink, and the Noise figure of the
transmitter is used to determine the total noise in the uplink. For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1062, "Modelling Terminals" on page 1063,
"Modelling Mobility Types" on page 1063, and "Defining WiMAX Reception Equipment" on page 1140, respectively.
d. 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. The shadowing margin is based
on the C/I standard deviation.
e. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
4. Click the Display tab. From the Display type list, select "Value intervals" to display the coverage prediction by C/(I+N)
levels or total noise (I+N) levels.
For information on adjusting the display, see "Setting the Display Properties of Objects" on page 51.
You can also display the uplink C/(I+N) for all subchannels, i.e., without uplink subchannelisation, by setting the Uplink
bandwidth allocation target to Full bandwidth for the scheduler being used and then selecting the display option C/
(I+N) Level (UL). For more information on schedulers, see "Defining WiMAX Schedulers" on page 1143.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
14.2.9.3.5
b. If you wish, select the network Layers for the determination of best servers. Otherwise, you can calculate the prediction for all layers.
c. Select a Terminal, a Mobility type, and a Service. The Noise figure defined in the terminal types properties dialog
box is used in the coverage prediction to determine the total noise in the downlink, and the Noise figure of the
transmitter is used to determine the total noise in the uplink. As well, the bearer selection for each pixel according
to the C(I+N) level is performed using the bearer selection thresholds defined in the reception equipment. This
reception equipment is the one defined in the selected terminal for the downlink coverage predictions, and the
one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used
to index the bearer selection threshold graph to use.
1066
AT332_UMR_E0
You can make Atoll use only the bearers for which selection thresholds are defined in both
the terminals and the cells reception equipment by adding an option in the Atoll.ini file.
For more information, see the Administrator Manual.
For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services"
on page 1062, "Modelling Terminals" on page 1063, "Modelling Mobility Types" on page 1063, and "Defining
WiMAX Reception Equipment" on page 1140, respectively.
d. 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. The shadowing margin is based
on the C/I standard deviation.
e. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
4. Click the Display tab. From the Display type list, select display by bearer or modulation.
For information on adjusting the display, see "Setting the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
14.2.9.3.6
b. If you wish, select the network Layers for the determination of best servers. Otherwise, you can calculate the prediction for all layers.
c. Select a Terminal, a Mobility type, and a Service. The Noise figure defined in the terminal types properties dialog
box is used in the coverage prediction to determine the total noise in the downlink, and the Noise figure of the
transmitter is used to determine the total noise in the uplink. As well, the bearer selection for each pixel according
to the C(I+N) level is performed using the bearer selection thresholds defined in the reception equipment. This
reception equipment is the one defined in the selected terminal for the downlink coverage predictions, and the
one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used
to index the bearer selection threshold graph to use.
You can make Atoll use only the bearers for which selection thresholds are defined in both
the terminals and the cells reception equipment by adding an option in the Atoll.ini file.
For more information, see the Administrator Manual.
1067
For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services"
on page 1062, "Modelling Terminals" on page 1063, "Modelling Mobility Types" on page 1063, and "Defining
WiMAX Reception Equipment" on page 1140, respectively.
d. 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. The shadowing margin is based
on the C/I standard deviation.
e. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
4. Click the Display tab. For an effective service area prediction, the Display type "Unique" is selected by default. The
coverage prediction will display where a service is available in both downlink and uplink. For information on defining
display properties, see "Setting the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
14.2.9.3.7
b. If you wish, select the network Layers for the determination of best servers. Otherwise, you can calculate the prediction for all layers.
c. Select a Terminal, a Mobility type, and a Service. The Noise figure defined in the terminal types properties dialog
box is used in the coverage prediction to determine the total noise in the downlink, and the Noise figure of the
transmitter is used to determine the total noise in the uplink. As well, the bearer selection for each pixel according
to the C(I+N) level is performed using the bearer selection thresholds defined in the reception equipment. This
reception equipment is the one defined in the selected terminal for the downlink coverage predictions, and the
one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used
to index the bearer selection threshold graph to use.
You can make Atoll use only the bearers for which selection thresholds are defined in both
the terminals and the cells reception equipment by adding an option in the Atoll.ini file.
For more information, see the Administrator Manual.
For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services"
on page 1062, "Modelling Terminals" on page 1063, "Modelling Mobility Types" on page 1063, and "Defining
WiMAX Reception Equipment" on page 1140, respectively.
1068
AT332_UMR_E0
d. 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. The shadowing margin is based
on the C/I standard deviation.
e. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
4. Click the Display tab. From the Display type list, select "Value intervals" to display the coverage prediction by peak
MAC, effective MAC, or application throughputs.
For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Atoll calculates the peak MAC channel throughputs from the information provided in the Global Parameters and in the terminal and mobility properties for the terminal and mobility selected in the coverage prediction. Atoll determines the total
number of symbols in the downlink and the uplink subframes from the information in the Global Parameters. Then, Atoll
determines the bearer at each pixel and multiplies the bearer efficiency by the number of symbols in the frame to determine
the peak MAC channel throughputs.
The effective MAC throughputs are the peak MAC throughputs reduced by retransmission due to errors, or the Block Error
Rate (BLER). Atoll uses the block error rate graphs of the reception equipment defined in the selected terminal for downlink
or the reception equipment of the cell of the serving transmitter for uplink.
The application throughput is the effective MAC throughput reduced by the overheads of the different layers between the
MAC and the Application layers.
The cell capacity display types let you calculate and display the throughputs available on each pixel of the coverage area taking
into account the maximum traffic load limits set for each cell. In other words, the cell capacity is equal to channel throughput
when the maximum traffic load is set to 100%, and is equal to a throughput limited by the maximum allowed traffic loads
otherwise. Cell capacities are, therefore, channel throughputs scaled down to respect the maximum traffic load limits.
The per-user throughput in downlink is calculated by dividing the downlink cell capacity by the number of downlink users of
the serving cell. In uplink, the per-user throughput is either the allocated bandwidth throughput or the uplink cell capacity
divided by the number of uplink users of the serving cell, whichever it smaller.
The allocated bandwidth throughputs are the throughputs corresponding to the number of subchannels allocated to the
terminal at different locations. Subchannelisation in uplink allows mobiles to use different numbers of subchannels depending
on the radio conditions. For example, users located far from the base stations use less subchannels than users located near
so that they can concentrate their transmission power over a bandwidth narrower than the channel bandwidth in order to
maintain the connection in uplink.
For more information on throughput calculation, see the Technical Reference Guide. For more information on the Global
Parameters, see "Network Settings" on page 1134.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
14.2.9.3.8
1069
This coverage prediction displays the surface area covered by each cell and colours it according to its aggregate throughput.
For more information on using simulation results in coverage predictions, see "Making Coverage Predictions Using Simulation
Results" on page 1112.
14.2.9.3.9
b. If you wish, select the network Layers for the determination of best servers. Otherwise, you can calculate the prediction for all layers.
c. Select a Terminal, a Mobility type, and a Service. The Noise figure defined in the terminal type properties dialog
box is used in the coverage prediction to determine the total noise in the downlink, and the Noise figure of the
transmitter is used to determine the total noise in the uplink. As well, the bearer selection for each pixel according
to the C(I+N) level is performed using the bearer selection thresholds defined in the reception equipment, and
the quality indicator graphs from the reception equipment are used to determine the values of the selected quality indicator on each pixel. This reception equipment is the one defined in the selected terminal for the downlink
coverage predictions, and the one defined in the cell properties of the serving transmitter for the uplink coverage
predictions. Mobility is used to index the bearer selection threshold graph to use.
You can make Atoll use only the bearers for which selection thresholds are defined in both
the terminal and the cell reception equipment by adding an option in the Atoll.ini file. For
more information, see the Administrator Manual.
For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services"
on page 1062, "Modelling Terminals" on page 1063, "Modelling Mobility Types" on page 1063, and "Defining
WiMAX Reception Equipment" on page 1140, respectively.
d. 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. The shadowing margin is based
on the C/I standard deviation.
e. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
4. Click the Display tab. You can choose from displaying results by BER, BLER, FER, or any other quality indicator that you
might have added to the document. For more information, see "Defining WiMAX Quality Indicators" on page 1139.
The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Setting
the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
1070
AT332_UMR_E0
14.2.9.4.1
14.2.9.4.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.
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 14.4).
14.2.9.4.3
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 91.
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 "Geographic Export Zone" on page 68.
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 210.
1071
14.2.9.5.1
) on the Radio Planning toolbar. The Point Analysis window opens and the pointer
The preamble signal level from the best server (topmost bar) and all interfering cells. Solid bars indicate
signal levels above the preamble C/N threshold.
The connection
status for the
current point.
Successful
Failed
The preamble, traffic, or pilot signal levels or C/N (depending on the selection made from the Display list) from
different transmitters (the colour of the bar corresponds to the colour of the transmitter on the map).
The preamble C/N thresholds: The empty portion of the bar indicates signal levels below the preamble C/N thresholds.
The availability of preamble coverage and service in downlink and uplink.
If there is at least one successful connection (for preamble, downlink, or uplink), double-clicking the icons in the righthand frame opens a dialog box with additional information about the best server:
Preamble: Azimuth and tilt of the receiver, total losses, received preamble power, preamble total noise, preamble
C/(I+N).
Downlink: Diversity mode, permutation zone, pilot and traffic received powers, traffic total noise, pilot and traffic
C/(I+N), bearer, channel throughputs, cell capacities, and per-user throughputs.
Uplink: Diversity mode, permutation zone, received power, transmission power, allocated bandwidth, total noise,
C/(I+N), bearer, channel throughputs, cell capacities, allocated bandwidth throughputs, and per-user throughputs.
1072
AT332_UMR_E0
6. If you are analysing reception to verify a coverage prediction, you can recreate the conditions of the coverage prediction by specifying the parameters if the study:
a. If necessary, select a layer filter for the serving cells from the Layer list.
a. Select the same Terminal, Mobility, and Service studied in the coverage prediction.
b. In the Reception view toolbar, click Options (
i.
Edit the X and Y coordinates to change the present position of the receiver.
ii. Select the Shadowing taken into account check box and enter a Cell edge coverage probability.
iii. Select the Indoor coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class.
iv. Click OK.
7. 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.
8. In the Reception view toolbar, you can use the following tools:
Click Report (
Click Copy (
programme.
) to generate a report that contains the information from the point analysis window.
Click Print (
) to print the content of the view.
Click Centre on Map ( ) to centre the map window on the receiver.
) to copy the content of the view and paste it as a graphic into a graphic editing or word-processing
You can display a point analysis that uses the settings from an existing prediction by
right-clicking the prediction in the Network explorer and selecting Open Point Analysis
from the context menu.
14.2.9.5.2
Analysing Interference
In Atoll, you can study the interferers of a transmitter using the Point Analysis tool. The Interference view gives you information on interference received on any downlink channel on any point on the map. The analysis is provided for a user-definable
probe receiver which has a terminal, a mobility, and a service. The downlink and uplink load conditions can be taken from the
Cells table or from Monte Carlo simulations.
To make an interference analysis:
1. Click the Point Analysis button (
changes (
) on the Radio Planning toolbar. The Point Analysis window opens and the pointer
1073
the interfering cells towards the pointer, indicating the interferers. 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.
4. In the Interference view, select "Cells table" from the Loads list.
The Interference view displays, in the form of a bar graph, the signal level from the best server, a black bar indicating
the total noise (I+N) received by the receiver, and bars representing the interference received from each interferer. If
you let the pointer rest on a bar, details are displayed in the tip text:
For the best server: Name, received signal level, and C/(I+N).
For the total noise (I+N): The values of each component, i.e., I, N, and the downlink inter-technology noise rise.
For each interferer: The effective interference and the various interference reduction factors.
5. Select Inter-technology interference to display interference from other technologies. The Interference bar graph displays the interference received from each inter-technology interferer. Disable Inter-technology interference to display intra-technology interference only.
6. Select the channel on which you want to study the interference from the Display list.
7. If you are analysing interferences to verify a coverage prediction, you can recreate the conditions of the coverage prediction by specifying the parameters of the study:
a. If necessary, select a layer filter for the serving cells from the Layer list.
a. Select the same Terminal, Mobility, and Service studied in the coverage prediction.
b. In the Reception view toolbar, click Options (
i.
Edit the X and Y coordinates to change the present position of the receiver.
ii. Select the Shadowing taken into account check box and enter a Cell edge coverage probability.
iii. Select the Indoor coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class.
iv. Click OK.
8. 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.
9. In the Interference view toolbar, you can use the following tools:
Click the Report button ( ) to generate a report that contains the information from the Point Analysis window.
The Analysis Report dialog box opens.
) to copy the content of the view and paste it as a graphic into a graphic editing or word-
You can display a point analysis that uses the settings from an existing prediction by
right-clicking the prediction in the Network explorer and selecting Open Point Analysis
from the context menu.
14.2.9.5.3
) on the Radio Planning toolbar. The Point Analysis window opens and the pointer
1074
AT332_UMR_E0
Cell: The name of the cell from which the received signal levels are displayed. The cells are listed in decreasing
order of preamble signal levels. The first row of the table is displayed in bold and italic indicating the best server
of the pointer on the map.
Distance (m): The distance from the cell to the current location of the pointer on the map.
Preamble C (dBm): The received preamble signal level from the cell.
Preamble C/N (dB): The received preamble C/N level from the cell.
Preamble I (dBm): The interference level received from interfering cells on the preamble of the cell.
Atoll lists all the cells from which the pointer receives a preamble C/N higher than the Preamble C/N Threshold
defined for these cells.
3. Move the pointer over the map to make an interference analysis for the current location of the pointer.
In the map window, a thick arrow from the pointer to its best server is displayed. The best server of the pointer is the
transmitter from which the pointer receives the highest preamble signal level. Thinner arrows are also displayed from
the interfering cells towards the pointer, indicating the interferers.
4. In the Details view, select "Cells table" from the Loads list.
5. If you are making a detailed analysis to verify a coverage prediction, you can recreate the conditions of the coverage
prediction by specifying the parameters of the study:
a. If necessary, select a layer filter for the serving cells from the Layer list.
a. Select the same Terminal, Mobility, and Service studied in the coverage prediction.
b. In the Reception view toolbar, click Options (
i.
Edit the X and Y coordinates to change the present position of the receiver.
ii. Select the Shadowing taken into account check box and enter a Cell edge coverage probability.
iii. Select the Indoor coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class.
iv. Click OK.
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.
7. In the Details view toolbar, you can use the following tools:
8. To display only interfering cells for the pointer on the map, which means cells whose C/N is above the Min Interferer
C/N Threshold defined in the Calculation Parameters tab of the Radio Network Settings Properties dialog box, select
the Show interferers only check box.
9. Click Point Analysis (
Intersection: This display shows the area where both coverage predictions overlap (for example, pixels covered by
both predictions are displayed in red).
Merge: This display shows the area that is covered by either of the coverage predictions (for example, pixels covered
by at least one of the 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).
Value Difference: This display shows the dB difference between any two coverage predictions by signal level. This display option will not be available if the coverage predictions were calculated using different resolutions.
1075
1076
AT332_UMR_E0
Figure 14.8: 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, select Compare with and, from the menu that opens, select the prediction you
want to compare with the first. The Comparison Properties dialog box appears.
2. 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 names and
resolutions.
3. Click the Display tab and choose how you want the results of the comparison to be displayed among:
Intersection
Merge
Union
Difference
In order to see what changes adding a new base station made, it is recommended to choose Difference.
4. Click OK to create the comparison. The comparison in Figure 14.9, shows the area covered only by the new base station.
1077
1078
Intersection
Merge
AT332_UMR_E0
Union
Difference
In order to see what changes modifying the antenna tilt made, choose Union. This mode displays 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, is immediately clear.
4. Click OK to create the comparison. The comparison in Figure 14.12, shows the increase in coverage due at the change
in antenna tilt.
This section also covers the following topics related to subscriber analyses:
14.2.9.7.1
Load conditions: Select "(Cells table)" to calculate the point analysis using the load conditions defined in the cells
table. Select a simulation or a group of simulations to calculate the point analysis using the load conditions calculated
by Monte Carlo simulations.
Shadowing taken into account: Select this option to consider shadowing in the point analysis. For more information,
see "Modelling Shadowing" on page 1150. If you select this option, you can change the Cell edge coverage probability.
Indoor coverage: Select this option to consider indoor losses. Indoor losses are defined per frequency per clutter class.
1079
Position Id: The indexes of the points used for the point analysis.
X and Y: The coordinates of the points used for the point analysis.
Height (m): The height of the points used for the point analysis.
Service: The services assigned to the points used for the point analysis.
Terminal: The terminals assigned to the points used for the point analysis.
Mobility: The mobility types assigned to the points used for the point analysis.
14.2.9.7.2
Importing a list of points from an external file: Click the Actions button and select Import Table from the menu to
open the Open file dialog box. In this dialog box, select a TXT or CSV file containing a list of points and click Open.
For more information on importing data tables, see "Importing Tables from Text Files" on page 88.
Importing a list of points from a fixed subscriber traffic map: Click the Actions button and select Import from Fixed
Subscribers from the menu to open the Fixed Subscribers dialog box. In this dialog box, select one or more existing
fixed subscriber traffic maps and click OK.
Copying a list of points from an external file.
Creating points in the list by editing the table: Add new points by clicking the New Row icon ( ) and entering X
and Y coordinates as well as a service, a terminal, and a mobility.
The list of points must have the same coordinate system as the display coordinate system
used in the Atoll document. For more information on coordinate systems, see "Setting a
Coordinate System" on page 41.
It is also possible to leave the Points tab empty and add points to the analysis on
the map using the mouse once the point analysis item has been created. To add
points on the map using the mouse, right-click the point analysis item to which you
want to add points, and select Add Points from the context menu. The mouse
pointer changes to point creation mode (
want to add. Press ESC or click the Pointer button ( ) in the Map toolbar to finish
adding points.
You can also export the list of point from a point analysis to ASCII text files (TXT and
CSV formats) and MS Excel XML Spreadsheet files (XML format) by selecting
Actions > Export Table. For more information on exporting table data, see
"Exporting Tables to Text Files and Spreadsheets" on page 86.
4. On the Display tab, specify how to display point analysis results on the map according to any input or calculated
parameter. For more information on defining display properties, see "Setting the Display Properties of Objects" on
page 51.
5. Once you have defined the point analysis parameters, you can calculate it immediately or you can save it and calculate
it later:
Calculate: Click Calculate to save the point analysis and calculate it immediately.
OK: Click OK to save the point analysis without calculating it. You can calculate it later by opening the point analysis
properties and clicking the Calculate button.
Once Atoll has finished calculating the point analysis, the results are displayed in the map window. You can also access the
analysis results in a table format. For more information, see "Viewing Point Analysis Results" on page 1080.
1080
AT332_UMR_E0
You can also organise point analyses in folders under the Multi-point Analysis folder by creating folders under the Multi-point
Analysis folder in the Network explorer. Folders may contain one or more point analyses items. You can move point analyses
items from one folder to another and rename folders.
14.2.9.7.3
Position Id: The indexes of the points used for the point analysis.
X and Y: The coordinates of the points used for the point analysis.
Height (m): The height of the points used for the point analysis.
Service: The services assigned to the points used for the point analysis.
Terminal: The terminals assigned to the points used for the point analysis.
Mobility: The mobility types assigned to the points used for the point analysis.
Cell: The names of the potential serving cells.
Distance (m): The distance from the potential serving cells.
Preamble Index: The preamble indexes of the potential serving cells.
Preamble C (dBm): The received preamble signal level from the potential serving cells.
Preamble C/N (dB): The received preamble C/N from the best serving cell.
Preamble I (dBm): The received interference on the preamble from the potential serving cells.
14.2.9.7.4
14.2.9.7.5
1081
Calculate: Click Calculate to save the subscriber analysis and calculate it immediately.
OK: Click OK to save the subscriber analysis without calculating it. You can calculate it later by opening the subscriber analysis properties and clicking the Calculate button.
Once Atoll has finished calculating the subscriber analysis, the results are displayed in the map window. You can also access
the analysis results in a table format. For more information, see "Viewing Subscriber Analysis Results" on page 1081.
You can also organise subscriber analyses in folders under the Multi-point Analysis folder by creating folders under the Multipoint Analysis folder in the Network explorer. Folders may contain one or more subscriber analyses items. You can move
subscriber analyses items from one folder to another and rename folders.
14.2.9.7.6
1082
AT332_UMR_E0
Effective MAC channel throughput (DL) (kbps): The effective MAC channel throughput attainable using the
highest bearer available at the subscriber location in the downlink. It is calculated from the peak MAC throughput
and the BLER.
Application channel throughput (DL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
Received power (UL) (dBm): The signal level received at the serving transmitter from the subscriber terminal in
the uplink.
C/(I+N) (UL) (dB): The C/(I+N) at the serving transmitter of the subscriber in the uplink.
Total noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the serving transmitter of the
subscriber in the uplink.
Bearer (UL): The highest WiMAX bearer available for the C/(I+N) level at the serving transmitter of the subscriber
in the uplink.
Permutation zone (UL): The uplink permutation zone allocated to the subscriber.
BLER (UL): The Block Error Rate read from the serving cells reception equipment for the C/(I+N) level at the
serving transmitter of the subscriber in the uplink.
Diversity mode (UL): The diversity mode supported by the cell or permutation zone in uplink.
Transmission power (UL) (dBm): The transmission power of the subscriber terminal after power control in the
uplink.
Allocated bandwidth (UL) (No. of Subchannels): The bandwidth allocated to the subscriber in terms of the
number of subchannels allocated in the uplink after subchannelisation.
Peak MAC channel throughput (UL) (kbps): The maximum MAC channel throughput attainable using the highest
bearer available at subscriber location in the uplink.
Effective MAC channel throughput (UL) (kbps): The effective MAC channel throughput attainable using the
highest bearer available at the subscriber location in the uplink. It is calculated from the peak MAC throughput
and the BLER.
Application channel throughput (UL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
Peak MAC allocated bandwidth throughput (UL) (kbps): The maximum MAC throughput attainable for the
number of subchannels allocated to the subscriber using the highest bearer available at the user location in the
uplink.
Effective MAC allocated bandwidth throughput (UL) (kbps): The effective MAC throughput attainable for the
number of subchannels allocated to the subscriber using the highest bearer available at the user location in the
uplink. It is calculated from the peak MAC throughput and the BLER.
Application allocated bandwidth throughput (UL) (kbps): The application throughput is the net throughput
without coding (redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the
throughput scaling factor of the service and the throughput offset.
1083
Figure 14.13: WiMAX handover area between reference cell and potential neighbour
When Use coverage conditions is not selected, the defined Distance is used to allocate neighbours to a reference
transmitter.
When Use coverage conditions is selected, click Define to open the Coverage Conditions dialog box:
Resolution: Enter the resolution to be used to calculate cells coverage areas during automatic neighbour allocation.
Global preamble C/N threshold: Select this check box to set a global value for the preamble C/N threshold. If you
set a global value here, Atoll will use this value or the Preamble C/N threshold value defined for each cell, whichever is higher. The preamble signal level threshold (in dBm) is calculated for each cell from its preamble C/N
threshold (in dB) considering the channel bandwidth of the cell and using the terminal that has the highest difference between its gain and losses so that the most number of potential neighbours can be processed.
Handover start: Enter the margin, with respect to the best server coverage area of the reference cell (cell A), from
which the handover process starts.
Handover end: Enter the margin, with respect to the best server coverage area of the reference cell (cell A), at
which the handover process ends. The value entered for the Handover end must be greater than the value for the
Handover start. The higher the value entered for the Handover end, the longer the list of potential neighbours.
The area between the Handover start and the Handover end constitutes the area within which Atoll will search
for neighbours.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this option to take indoor losses into account in calculations. Indoor losses are defined
per frequency per clutter class.
Co-site cells as neighbours: When selected, the cells located on the same site as the reference cell are automatically
considered as neighbours. A cell with no antenna cannot be considered as a co-site neighbour.
Adjacent cells as neighbours (Intra-carrier Neighbours tab only): When selected, the cells that are adjacent to the reference cell are automatically considered as neighbours. A cell is considered adjacent if there is at least one pixel in the
reference cells coverage area where the potential neighbour cell is the best server, or where the potential neighbour
cell is the second best server respecting the handover end.
Symmetric relations: Select this option if you want the neighbour relations to be reciprocal, which means that any
reference transmitter/cell is a potential neighbour of all the cells that are its neighbours.
Exceptional pairs: Select this option to force the neighbour relations defined in the Intra-technology Exceptional pairs
table. For information on exceptional pairs, see "Defining Exceptional Pairs" on page 223.
1084
AT332_UMR_E0
Cause
Description
When
Distance
Coverage
Co-Site
Adjacent
Symmetry
Exceptional Pair
Exceptional pairs
is selected
Existing
Once the AFP input elements have been set up, the AFP can be used for:
Once you have completed an automatic allocation, you can analyse the results with the tools that Atoll provides:
1085
interfered if the C/(I+N) is lower than the preamble C/N threshold defined for the interfered cell. For adjacent channel interference, a pixel is considered interfered if the C/(I+N) is lower than the preamble C/N threshold defined for the interfered cell
less the adjacent channel suppression factor defined for the frequency band of the interfered cell.
You can amplify the degradation of the C/(I+N) by using a high quality margin when calculating the interference matrices. For
example, a 3 dB quality margin would imply that each interferer is considered to be twice as strong compared to a calculation
without any quality margin (which means 0 dB).
To calculate interference matrices:
1. In the Network explorer, right-click the Interference Matrices folder and select New from the context menu. The
Interference Matrices Properties dialog box appears.
2. On the General tab, you can set the following parameters:
3. Once you have created the interference matrix, you can calculate it immediately or you can save it and calculate it
later:
Calculate: Click Calculate to save the defined interference matrix and calculate it immediately.
OK: Click OK to save the defined interference matrix without calculating it. You can calculate it later clicking the
Calculate button (
Once calculated, the new interference matrix is available in the Interference Matrices folder and will be available for use the
next time you run the AFP.
You can modify the properties of an existing interference matrix by selecting Properties from the interference matrix context
menu. An existing interference matrix can be calculated again by selecting Calculate from the interference matrix context
menu.
1086
For information on configuring neighbour importance weighting, see "Configuring Neighbour Importance Factors" on
page 231.
AT332_UMR_E0
For more information on calculating neighbour importance values, see "Evaluating Neighbour Importance" on
page 231.
For more details on the calculation of neighbour importance values, see the Technical Reference Guide.
6. Click in another cell of the table to create the new group and add a new blank row to the table.
1st order neighbours: The relative weight assigned to a first order neighbour relationship violation.
Interference matrices: The relative weight assigned to an interference matrix-based relationship violation.
Distance: The relative weight assigned to a distance-based relationship violation.
You can click the Reset button to set the weights to their default values.
3. Click the Preamble Index Allocation tab.
In the Relation weights frame, you can set the weights for the following cost components:
1st order neighbours: The relative weight assigned to a first order neighbour relationship violation.
2nd order neighbours: The relative weight assigned to a second order neighbour relationship violation.
1087
Neighbours of a common cell: The relative weight assigned to the violation of an indirect neighbour relationship between neighbours of a common cell.
Interference matrices: The relative weight assigned to a interference matrix-based relationship violation.
Distance: The relative weight assigned to a distance-based relationship violation.
You can click the Reset button to set the weights to their default values.
In the Constraint violation weights frame, you can set the weights for the following constraints:
Preamble index: The relative weight assigned to a preamble index collision between two related cells.
Segment: The relative weight assigned to a segment collision between two related cells.
Cell permbase: The relative weight assigned to the cell permbase constraint violation (occurrence of two
different cell permbases) between two related co-site cells.
You can click the Reset button to set the weights to their default values.
4. Click OK.
The top line contains global information about the current allocation (resource being allocated and the total cost
of the current plan).
The left-hand side of the dialog box contains tabs with input parameters.
The right-hand side of the dialog box provides the allocation results.
2. From the Allocate list, select Frequencies for automatic frequency planning.
3. On the Relation Types tab, you can set the relations to take into account in automatic allocation:
1088
Interference matrix: Select this check box if you want the AFP to take interference matrices into account for the
allocation, and select an interference matrix from the list. For Atoll to take interference matrices into account,
they must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be
calculated, imported, and edited in the Interference Matrices folder. For more information on interference
matrices, see "Working with Interference Matrices" on page 1085.
Existing neighbours: Select the Existing neighbours check box if you want the AFP to take neighbour relations into
account for the allocation. The AFP will try to allocate different frequencies to a cell and its neighbours. Atoll can
only take neighbour relations into account if neighbours have already been allocated. For information on allocating neighbours, see "Neighbour Planning" on page 223.
Reuse distance: Select this check box if you want the AFP to take relations based on distance into account for the
allocation. You can enter a Default reuse distance within which two cells must not have the same channel
assigned. However, it is highly recommended to define a reuse distance for each individual cell depending on the
AT332_UMR_E0
size of the cells coverage area and the network density around the cell. If defined, a cell-specific reuse distance is
used instead of the default value entered here.
4. On the right-hand side of the Automatic Resource Allocation dialog box, Atoll displays the Total cost of the current
frequency allocation. Click Update to calculate the total cost take into account the parameters set in step 3.
You can click the Weights button to open the Weights dialog box and modify the cost
component weights. For more information, see "Configuring Cost Component Weights" on
page 1087.
5. Click Start. Atoll begins the process of allocating frequencies. Any messages generated by the AFP during automatic
allocation are reported on the Events tab.
While Atoll allocates frequencies, you can:
Once Atoll has finished allocating frequencies, or if you pause the automatic allocation, the Statistics tab shows the
number of proposed changes to the allocation plan and the numbers of different relations, violations, and collisions.
It also shows the numbers of violations and collisions in the current plan compared to the initial one (in brackets). The
Results tab shows the proposed allocation plan:
In order to better view the progress graph and the results table, you can expand
the right-hand side zone of the Automatic Resource Allocation dialog box by
clicking the Hide Inputs button
. You can also resize the dialog box.
You can export the contents of table grids to TXT, CSV, and XML Spreadsheet files
by right-clicking the table and selecting Export from the context menu. For more
information on exporting data tables, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
You can select the columns to display in different tabs by right-clicking the table
and selecting Display Columns from the context menu. For more information, see
"Displaying and Hiding Columns" on page 80.
6. Click Commit. The proposed frequency plan is assigned to the cells of the network.
7. Click Close to exit.
1089
Where n is the segment number (0, 1, or 2), and k is a running index from 0 to 567, 0 to 283, 0 to 142, and 0 to 35 for FFT sizes
2048, 1024, 512, and 128, respectively. Therefore, each preamble carrier set uses every third subcarrier.
Atoll facilitates the management of preamble indexes by letting you create groups of preamble indexes and domains, where
each domain is a defined set of groups. For more information, see "Setting Resources Available for Allocation" on page 1086.
You can assign preamble indexes manually or automatically to any cell in the network. Once allocation is completed, you can
audit the preamble indexes, view preamble index reuse on the map, and make an analysis of preamble index distribution.
Atoll can automatically assign preamble indexes to the cells taking into account the selected cell permbase allocation strategy
(free or same per site), allowed allocation domain, interference matrices, reuse distance, and any constraints imposed by
neighbours.
To automatically allocate preamble indexes:
1. In the Network explorer, right-click the Transmitters folder and select AFP > Automatic Allocation. The Automatic
Resource Allocation dialog box appears.
The Automatic Resource Allocation dialog box is divided into three zones:
The top line contains global information about the current allocation (resource being allocated and the total cost
of the current plan).
The left-hand side of the dialog box contains tabs with input parameters.
The right-hand side of the dialog box provides the allocation results.
2. From the Allocate list, select Preamble Indexes for automatic preamble index planning.
3. On the Relation Types tab, you can set the relations to take into account in automatic allocation:
Interference matrix: Select this option if you want the AFP to take interference matrices into account for the allocation, and select an interference matrix from the list. For Atoll to take interference matrices into account, they
must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, imported, and edited in the Interference Matrices folder. For more information on interference matrices,
see "Working with Interference Matrices" on page 1085.
Existing neighbours: Select this option if you want the AFP to take neighbour relations into account for the allocation. The AFP will try to allocate different preamble indexes to a cell and its neighbours. The AFP can take neighbours into account only if neighbours have already been allocated. If you want the AFP to take both first and
second order neighbours into account, you must set an option in the Atoll.ini file (see the Administrator Manual).
For information on allocating neighbours, see "Neighbour Planning" on page 223.
Reuse distance: Select this option if you want the AFP to take relations based on distance into account for the allocation. You can enter a Default reuse distance within which two cells must not have the same preamble index
assigned. However, it is highly recommended to define a reuse distance for each individual cell depending on the
size of the cells coverage area and the network density around the cell. If defined, a cell-specific reuse distance is
used instead of the default value entered here.
4. On the Constraints tab, you can set the constraints to take into account in automatic allocation:
Allocation domain: You can choose Per cell to allocate preamble indexes from the preamble index domains
defined per cell, you can choose to allocate from the Entire (0-113) domain or a Restricted (0-95) domain, or you
can choose Custom and enter the Excluded resources to exclude some preamble indexes from the allocation.
You can enter non-consecutive preamble indexes separated with a comma, or you can enter a range of preamble
indexes separating the first and last one with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
Allocation strategies: You can select Same per site as the Cell permbase allocation strategy if you want the AFP
to allocate the same cell permbase to all the cells of a site. Select Free as the Cell permbase allocation strategy if
you want the AFP to ignore the cell permbase collisions. With free allocation, the cell permbase will not necessarily
be the same for all the cells of a site.
You can select the Allocate the same segment to co-transmitter cells check box if you want to allocate preamble
indexes to co-transmitter cells so that they all have the same segment number assigned. If you do not select this
check box, the allocation will not consider any constraint on the segment number allocation to co-transmitter
cells.
You can select the Take into account frequency plan check box if you want the AFP to consider the frequency plan
when determining preamble index collisions.
5. On the right-hand side of the Automatic Resource Allocation dialog box, Atoll displays the Total cost of the current
preamble index allocation. Click Update to calculate the total cost take into account the parameters set in step 3.
You can click the Weights button to open the Weights dialog box and modify the cost
component weights. For more information, see "Configuring Cost Component Weights" on
page 1087.
1090
AT332_UMR_E0
6. Click Start. Atoll begins the process of allocating preamble indexes. Any messages generated by the AFP during automatic allocation are reported on the Events tab.
While Atoll allocates preamble indexes, you can:
Once Atoll has finished allocating preamble indexes, or if you pause the automatic allocation, the Statistics tab shows
the number of proposed changes to the allocation plan and the numbers of different relations, violations, and collisions. It also shows the numbers of violations and collisions in the current plan compared to the initial one (in brackets). The Results tab shows the proposed allocation plan:
In order to better view the progress graph and the results table, you can expand
the right-hand side zone of the Automatic Resource Allocation dialog box by
clicking the Hide Inputs button
. You can also resize the dialog box.
You can export the contents of table grids to TXT, CSV, and XML Spreadsheet files
by right-clicking the table and selecting Export from the context menu. For more
information on exporting data tables, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
You can select the columns to display in different tabs by right-clicking the table
and selecting Display Columns from the context menu. For more information, see
"Displaying and Hiding Columns" on page 80.
7. Click Commit. The proposed preamble index plan is assigned to the cells of the network.
When you allocate preamble indexes to a large number of cells, it is easiest to let Atoll allocate them automatically. However,
if you want to assign a preamble index to one cell or to modify it, you can do it by accessing the properties of the cell.
To allocate a preamble index to a WiMAX cell manually:
1. On the map, right-click the transmitter to whose cell you want to allocate a preamble index and select Properties from
the context menu. The transmitter Properties dialog box appears.
2. Select the Cells tab.
3. Enter a Preamble index in the cell column.
4. You can set the Preamble index status to Locked if you want to lock the preamble index that you assigned.
5. Click OK.
1091
one in uplink. These permbases are called zone permbases in Atoll. There are 32 possible permbases in downlink, numbered
from 0 to 31, and 70 in uplink, numbered from 0 to 69.
You can assign zone permbases manually or automatically to any cell in the network. Once allocation is completed, you can
view zone permbase reuse on the map. Atoll can automatically assign zone permbases to the cells taking into account the
allowed allocation domain, interference matrices, reuse distance, and any constraints imposed by neighbours.
To automatically allocate permutation zone permbases:
1. In the Network explorer, right-click the Transmitters folder and select AFP > Automatic Allocation. The Automatic
Resource Allocation dialog box appears.
The Automatic Resource Allocation dialog box is divided into three zones:
The top line contains global information about the current allocation (resource being allocated and the total cost
of the current plan).
The left-hand side of the dialog box contains tabs with input parameters.
The right-hand side of the dialog box provides the allocation results.
2. From the Allocate list, select DL Zone PermBase or UL Zone PermBase to allocate downlink or uplink permutation
zone permbases to cells automatically.
3. On the Relation Types tab, you can set the relations to take into account in automatic allocation:
Interference matrix: Select this option if you want the AFP to take interference matrices into account for the allocation, and select an interference matrix from the list. For Atoll to take interference matrices into account, they
must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, imported, and edited in the Interference Matrices folder. For more information on interference matrices,
see "Working with Interference Matrices" on page 1085.
Existing neighbours: Select this option if you want the AFP to take neighbour relations into account for the allocation. The AFP will try to allocate different permbases to a cell and its neighbours. The AFP can take neighbours
into account only if neighbours have already been allocated. If you want the AFP to take both first and second
order neighbours into account, you must set an option in the Atoll.ini file (see the Administrator Manual). For
information on allocating neighbours, see "Neighbour Planning" on page 223.
Reuse distance: Select this option if you want the AFP to take relations based on distance into account for the allocation. You can enter a Default reuse distance within which two cells must not have the same zone permbase
assigned. However, it is highly recommended to define a reuse distance for each individual cell depending on the
size of the cells coverage area and the network density around the cell. If defined, a cell-specific reuse distance is
used instead of the default value entered here.
4. On the Constraints tab, you can set the constraints to take into account in automatic allocation.
Select the Allocation domain. You can choose to allocate permbases from Entire (0-31) for downlink permutation
zone permbase or Entire (0-69) for uplink permutation zone permbase, or you can choose Custom and enter the
Excluded resources to exclude some permbases from the allocation.
You can enter non-consecutive permbases separated with a comma, or you can enter a range of permbases separating
the first and last one with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
5. On the right-hand side of the Automatic Resource Allocation dialog box, Atoll displays the Total cost of the current
zone permbase allocation. Click Update to calculate the total cost take into account the parameters set in step 3.
You can click the Weights button to open the Weights dialog box and modify the cost
component weights. For more information, see "Configuring Cost Component Weights" on
page 1087.
6. Click Start. Atoll begins the process of allocating zone permbases. Any messages generated by the AFP during automatic allocation are reported on the Events tab.
While Atoll allocates zone permbases, you can:
Once Atoll has finished allocating zone permbases, or if you pause the automatic allocation, the Statistics tab shows
the number of proposed changes to the allocation plan and the numbers of different relations, violations, and collisions. It also shows the numbers of violations and collisions in the current plan compared to the initial one (in brackets). The Results tab shows the proposed allocation plan:
1092
AT332_UMR_E0
In order to better view the progress graph and the results table, you can expand
the right-hand side zone of the Automatic Resource Allocation dialog box by
clicking the Hide Inputs button
. You can also resize the dialog box.
You can export the contents of table grids to TXT, CSV, and XML Spreadsheet files
by right-clicking the table and selecting Export from the context menu. For more
information on exporting data tables, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
You can select the columns to display in different tabs by right-clicking the table
and selecting Display Columns from the context menu. For more information, see
"Displaying and Hiding Columns" on page 80.
7. Click Commit. The proposed zone permbase plan is assigned to the cells of the network.
When you allocate permutation zone permbases to a large number of cells, it is easiest to let Atoll allocate them automatically. However, if you want to assign a permutation zone permbase to one cell or to modify it, you can do it by accessing the
properties of the cell.
To allocate a permutation zone permbase to a WiMAX cell manually:
1. On the map, right-click the transmitter to whose cell you want to allocate a zone permbase and select Properties from
the context menu. The transmitter Properties dialog box appears.
2. Select the Cells tab.
3. Enter a DL Zone PermBase or UL Zone PermBase in the cell column.
4. Set the DL Zone PermBase Status or UL Zone PermBase Status to Locked if you want to lock the permutation zone
permbase that you assigned.
5. Click OK.
1093
Preamble index: If you want to find a preamble index, select Preamble index and select the preamble index from
the list.
Segment: If you want to find a segment number, select Segment and select the segment number from the list:
"All," "0," "1," or "2."
Cell permbase: If you want to find a cell permbase, select Cell permbase and select the cell permbase from the list.
4. Click Search.
When you select a preamble index or a cell permbase, transmitters with cells matching the search criteria are
displayed in red. Transmitters that do not match the search criteria are displayed as grey lines.
When you select a specific segment number, transmitters whose cells use the selected segment are displayed in red.
Transmitters with cells that use other segments are displayed as grey lines. When you choose to search for all
segments, transmitters whose first cells use segment 0 are displayed in red, transmitters whose first cells use segment
1 are displayed in yellow, and transmitters whose first cells use segment 2 are displayed in green.
To restore the initial transmitter colours, click the Reset display button in the Search Tool window.
By including the preamble index of each cell in the transmitter label, the search
results will be easier to understand. For information on defining the label, see
"Associating a Label to an Object" on page 53.
Transmitters with more than one cell may use different segments in different cells.
Therefore, the search for all segments is only valid for single-cell transmitters.
1094
AT332_UMR_E0
You can also display the frequency band and channel number in the transmitter label or tip text by selecting "Cells: Frequency
band" and "Cells: Channel number" from the Label or Tip Text Field Selection dialog box.
To display preamble index allocation on the map:
1. In the Network explorer, right-click the Transmitters folder and select Properties from the context menu. The Properties dialog box appears.
2. Click the Display tab.
3. Select "Discrete values" as the Display type and "Cells: Preamble index" as the Field.
4. Click OK. Transmitters are displayed by preamble index.
You can also display the preamble index in the transmitter label or tip text by selecting "Cells: Preamble index" from the Label
or Tip Text Field Selection dialog box.
To display the downlink or uplink permutation zone permbase allocation on the map:
1. In the Network explorer, right-click the Transmitters folder and select Properties from the context menu. The Properties dialog box appears.
2. Click the Display tab.
3. Select "Discrete values" as the Display type and "Cells: DL zone permbase" or "Cells: UL zone permbase" as the Field.
4. Click OK. Transmitters are displayed by the downlink or uplink permutation zone permbase.
You can also display the permutation zone permbase in the transmitter label or tip text by selecting "Cells: DL zone permbase"
and "Cells: UL zone permbase" from the Label or Tip Text Field Selection dialog box.
For information on display options, see "Setting the Display Properties of Objects" on page 51.
Frequency band
Channel number
Preamble index
DL zone permbase
UL zone permbase
5. Click
to add the parameter to the Group these fields in this order list. The selected parameter is added to the list
of parameters on which the transmitters will be grouped.
6. If you do not want the transmitters to be grouped by a certain parameter, select the parameter in the Group these
fields in this order list and click
transmitters will be grouped.
. The selected parameter is removed from the list of parameters on which the
7. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters to
be grouped:
a. Select a parameter and click
8. Click OK to save your changes and close the Group dialog box.
1095
The top line contains global information about the current allocation (resource being audited and the total cost of
the current plan).
The left-hand side of the dialog box contains tabs with input parameters.
The right-hand side of the dialog box provides the audit results.
Interference matrix: Select this option if you want the audit to take interference matrices into account, and select
an interference matrix from the list. For Atoll to take interference matrices into account, they must be available
in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, and
imported in the Interference Matrices folder. For more information on interference matrices, see "Working with
Interference Matrices" on page 1085.
Existing Neighbours: Select this check box if you want the audit to take neighbours into account. Atoll can only
take neighbour relations into account if neighbours have already been allocated. For information on allocating
neighbours, see "Configuring Network Parameters Using the AFP" on page 1084.
Reuse distance: Select this check box if you want the audit to take reuse distance into account. For cells that do
not have a reuse distance defined in their properties, the value entered next to Default will be used for the audit.
4. On the right-hand side of the Resource Allocation Audit dialog box, Atoll displays the Total cost of the current frequency allocation.
You can click the Weights button to open the Weights dialog box and modify the cost
component weights. For more information, see "Configuring Cost Component Weights" on
page 1087.
5. Click Calculate. Atoll performs an audit of the current frequency plan. Any messages generated by the audit are
reported on the Events tab. The audit results are reported on the following tabs:
The Statistics tab provides overall statistics such as the numbers of various types of relations considered by the AFP
for frequency planning and the number of violated relations.
The Relations tab lists all the relations between active and filtered cells in the document. The Relations tab can display
the following information:
1096
AT332_UMR_E0
ii. Under Include relations by type, select all the options representing the relation types and select (All) from
their respective lists.
iii. Click Apply. The data table in the Relations tab shows all the relations between cells.
To view only the relations that violate the frequency allocation requirements:
i.
ii. Under Include relations by type, select all the options representing the relation types and select (All) from
their respective lists.
iii. Click Apply. The data table in the Relations tab shows only the relations that violate the frequency allocation
requirements.
To view only the important relations that violate the frequency allocation requirements:
i.
ii. Under Include relations by type, select the relation types that you consider important and select some or all
of their characteristics from their respective lists.
iii. Click Apply. The data table in the Relations tab shows the relations according to the user-defined filter.
The Cells tab lists the current allocation plan and the following information:
The Distribution tab shows the histogram of the current allocation plan.
You can expand the right pane of the Resource Allocation Audit dialog box by
clicking the Hide button ( ).
You can export the contents of table grids to TXT, CSV, and XML Spreadsheet files
by right-clicking the table and selecting Export from the context menu. For more
information on exporting data tables, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
You can select the columns to display in different tabs by right-clicking the table
and selecting Display Columns from the context menu. For more information, see
"Displaying and Hiding Columns" on page 80.
The top line contains global information about the current allocation (resource being audited and the total cost of
the current plan).
The left-hand side of the dialog box contains tabs with input parameters.
The right-hand side of the dialog box provides the audit results.
Interference matrix: Select this option if you want the audit to take interference matrices into account, and select
an interference matrix from the list. For Atoll to take interference matrices into account, they must be available
in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, and
1097
imported in the Interference Matrices folder. For more information on interference matrices, see "Working with
Interference Matrices" on page 1085.
Existing Neighbours: Select this check box if you want the audit to take neighbours into account. Atoll can only
take neighbour relations into account if neighbours have already been allocated. For information on allocating
neighbours, see "Neighbour Planning" on page 223.
Reuse distance: Select this check box if you want the audit to take reuse distance into account. For cells that do
not have a reuse distance defined in their properties, the value entered next to Default will be used for the audit.
4. On the right-hand side of the Resource Allocation Audit dialog box, Atoll displays the Total cost of the current frequency allocation.
You can click the Weights button to open the Weights dialog box and modify the cost
component weights. For more information, see "Configuring Cost Component Weights" on
page 1087.
5. On the Constraints tab, you can set the constraints to take into account in the audit:
Allocation domain: You can choose Per cell to check if the allocated preamble indexes belong to the preamble
index domains defined per cell, to the Entire (0-113) domain, a Restricted (0-95) domain, or to a Custom domain
by entering the Excluded resources.
You can enter non-consecutive preamble indexes separated with a comma, or you can enter a range of preamble
indexes separating the first and last one with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
Allocation strategies: You can select the Same per site strategy for the Cell permbase to check whether the same
cell permbase has been allocated to the cells of the same site. You can select the Segments of co-site cells and
Segments of co-transmitter cell check boxes to check whether the same or different ones have been allocated.
You can select the Take into account frequency plan check box if you want the audit to consider the frequency
plan when determining preamble index collisions.
6. Click Calculate. Atoll performs an audit of the current preamble index plan. Any messages generated by the audit are
reported on the Events tab. The audit results are reported on the following tabs:
The Statistics tab provides overall statistics such as the numbers of various types of relations considered by the AFP
for preamble index planning, the numbers of violated relations of each type, the number of collisions for each
resource type, the number of cells not satisfying the domain compliance criteria, and numbers of strategy violations
for selected allocation strategies.
The Relations tab lists all the relations between active and filtered cells in the document. The Relations tab can display
the following information:
1098
AT332_UMR_E0
Second order neighbour: Whether a second-order neighbour relation exists ( ) between Cell 1 and Cell 2 or not.
Second order neighbour importance: The importance of the second-order neighbour relation between Cell 1 and
Cell 2.
Neighbours of a common cell: Whether Cell 1 and Cell 2 are ( ) neighbours of a common cell or not.
Importance of neighbours of a common cell: The importance of the relation between Cell 1 and Cell 2 through a
common neighbour cell.
The data table in the Relations tab can be filtered. For example, you can view all the relations, only the relations
that violate the preamble index allocation requirements, or apply a filter to exclude unimportant ones. To filter
the relations listed in the Relations tab, click the Show button (
appear.
ii. Under Include relations by type, select all the options representing the relation types and select (All) from
their respective lists.
iii. Click Apply. The data table in the Relations tab shows all the relations between cells.
To view only the relations that violate the preamble index allocation requirements:
i.
ii. Under Include relations by type, select all the options representing the relation types and select (All) from
their respective lists.
iii. Click Apply. The data table in the Relations tab shows only the relations that violate the preamble index allocation requirements.
To view only the important relations that violate the preamble index allocation requirements:
i.
ii. Under Include relations by type, select the relation types that you consider important and select some or all
of their characteristics from their respective lists.
iii. Click Apply. The data table in the Relations tab shows the relations according to the user-defined filter.
The Cells tab lists the current allocation plan and the following information:
) or not (
).
).
The Distribution tab shows the histogram of the current allocation plan.
1099
The exclamation mark icon ( ) signifies that the collision may or may not be a
problem depending on your network design rules and selected strategies. On the
other hand, the cross icon ( ) implies an error.
You can expand the right pane of the Resource Allocation Audit dialog box by
clicking the Hide button ( ).
You can export the contents of table grids to TXT, CSV, and XML Spreadsheet files
by right-clicking the table and selecting Export from the context menu. For more
information on exporting data tables, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
You can select the columns to display in different tabs by right-clicking the table
and selecting Display Columns from the context menu. For more information, see
"Displaying and Hiding Columns" on page 80.
The top line contains global information about the current allocation (resource being audited and the total cost of
the current plan).
The left-hand side of the dialog box contains tabs with input parameters.
The right-hand side of the dialog box provides the audit results.
Interference matrix: Select this option if you want the audit to take interference matrices into account, and select
an interference matrix from the list. For Atoll to take interference matrices into account, they must be available
in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, and
imported in the Interference Matrices folder. For more information on interference matrices, see "Working with
Interference Matrices" on page 1085.
Existing Neighbours: Select this check box if you want the audit to take neighbours into account. Atoll can only
take neighbour relations into account if neighbours have already been allocated. For information on allocating
neighbours, see "Neighbour Planning" on page 223.
Reuse distance: Select this check box if you want the audit to take reuse distance into account. For cells that do
not have a reuse distance defined in their properties, the value entered next to Default will be used for the audit.
4. On the right-hand side of the Resource Allocation Audit dialog box, Atoll displays the Total cost of the current frequency allocation.
You can click the Weights button to open the Weights dialog box and modify the cost
component weights. For more information, see "Configuring Cost Component Weights" on
page 1087.
5. On the Constraints tab, you can set the constraints to take into account in the audit:
Allocation domain: You can choose the Entire (0-31) domain for the DL zone permbase or Entire (0-69) domain
for the UL zone permbase, or choose a Custom domain by entering the Excluded resources.
You can enter non-consecutive zone permbases separated with a comma, or you can enter a range of permbases
separating the first and last one with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
6. Click Calculate. Atoll performs an audit of the current zone permbase plan. Any messages generated by the audit are
reported on the Events tab. The audit results are reported on the following tabs:
The Statistics tab provides overall statistics such as the numbers of various types of relations considered by the AFP
for zone permbase planning, the numbers of violated relations of each type, and the number of cells not satisfying the
domain compliance criteria.
1100
AT332_UMR_E0
The Relations tab lists all the relations between active and filtered cells in the document. The Relations tab can display
the following information:
ii. Under Include relations by type, select all the options representing the relation types and select (All) from
their respective lists.
iii. Click Apply. The data table in the Relations tab shows all the relations between cells.
To view only the relations that violate the zone permbase allocation requirements:
i.
ii. Under Include relations by type, select all the options representing the relation types and select (All) from
their respective lists.
iii. Click Apply. The data table in the Relations tab shows only the relations that violate the zone permbase allocation requirements.
To view only the important relations that violate the zone permbase allocation requirements:
i.
ii. Under Include relations by type, select the relation types that you consider important and select some or all
of their characteristics from their respective lists.
iii. Click Apply. The data table in the Relations tab shows the relations according to the user-defined filter.
The Cells tab lists the current allocation plan and the following information:
The Distribution tab shows the histogram of the current allocation plan.
1101
The exclamation mark icon ( ) signifies that the collision may or may not be a
problem depending on your network design rules and selected strategies. On the
other hand, the cross icon ( ) implies an error.
You can expand the right pane of the Resource Allocation Audit dialog box by
clicking the Hide button ( ).
You can export the contents of table grids to TXT, CSV, and XML Spreadsheet files
by right-clicking the table and selecting Export from the context menu. For more
information on exporting data tables, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
You can select the columns to display in different tabs by right-clicking the table
and selecting Display Columns from the context menu. For more information, see
"Displaying and Hiding Columns" on page 80.
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
Under Display Configuration, you can create a Filter to select which sites to display in the results. You can also display
the results grouped in the Network explorer 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 99;
for information on grouping, see "Advanced Grouping of Data Objects" on page 96; for information on sorting, see
"Advanced Sorting" on page 98.
4. Click the Conditions tab. 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.
The Server parameter is set to "Best Signal Level." You can enter an Overlap 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. Indoor losses are defined per frequency per
clutter class.
You can select the Take frequency plan into account option to determine the cell identifier collisions based on the
current frequency plan of the network.
Under Identifier, you can select the cell identifier for which you wish to calculate the coverage prediction. AC:
remove the following image.
Click Calculate to save the defined coverage prediction and perform the calculation immediately.
Click OK to save the defined coverage prediction without performing the calculation. You can calculate the prediction later by clicking the Calculate button (
1102
AT332_UMR_E0
The progress of the calculation and any error messages are displayed in the Events viewer. Once Atoll has finished calculating
the coverage prediction, the results are displayed in the map window.
WiMAX radio bearers: Radio bearers are used by the network for carrying information. The WiMAX Radio Bearer
table lists all the available radio bearers. You can create new radio bearers and modify existing ones by using the
WiMAX Radio Bearer table. For information on defining radio bearers, see "Defining WiMAX Radio Bearers" on
page 1139.
Services: Services are the various services, such as VoIP and FTP download, available to users. These services can be
either of the type "voice" or "data". For information on modelling end-user services, see "Modelling Services" on
page 1062.
Mobility types: Information about receiver mobility is important to determine the users radio conditions and
throughputs. For information on modelling mobility types, see "Modelling Mobility Types" on page 1063.
Terminals: 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 modelling terminals, see "Modelling Terminals" on page 1063.
1103
In Atoll, a simulation corresponds to a given distribution of WiMAX users. It is a snapshot of a WiMAX network. The principal
outputs of a simulation are a geographic user distribution with a certain traffic demand, resources allocated to each user of
this distribution, and cell loads.
You can create groups for one or more simulations and carry out as many simulations as required. A new simulation for each
different traffic scenario can help visualise the network response to different traffic demands. Each user distribution (each
simulation generates a new user distribution) is a Poisson distribution of the number of active users. Therefore, each simulation may have a varying number of users accessing the network.
WiMAX simulation results can be displayed on the map as well as listed in tabular form for analysis. Simulation outputs include
results related to sites, cells, and mobiles.
WiMAX simulation results can be stored in the cells table and used in C/(I+N) based coverage predictions.
In this section, the following are explained:
This section explains the specific mechanisms that are used to calculate WiMAX traffic simulations. For information on working with traffic simulations in Atoll, see "Simulations" on page 265.
1104
AT332_UMR_E0
1105
Atoll uses an intelligent scheduling algorithm to perform radio resource management. The scheduling algorithm is
explained in detail in the Technical Reference Guide. The scheduler:
a. Determines the total amount of resources in each cell.
b. Selects the first N users from the users generated in the first step, where N is the Max number of users defined in
the cell properties.
c. Sorts the users in decreasing order by service priority.
d. Allocates the resources required to satisfy the minimum throughput demands of the users starting from the first
user (with the highest priority service) to the last user.
e. If resources still remain in the resource pool after this allocation, allocates resources to the users with maximum
throughput demands according to the used scheduling algorithm.
The service priority is determined by the pair QoS Class-Priority. A UGS-Priority 1 service
will have higher service priority than a UGS-Priority 0 service. The QoS classes are UGS,
ErtPS, rtPS, nrtPS, and Best Effort, in order of decreasing priority.
At the end of the simulations, active users can be connected in the direction corresponding to his activity status if the following
conditions are met:
A user may be rejected in step 2. for "No Coverage" step 3. or step 4. for "No Service" and step 5. for:
"Scheduler Saturation": The user is not among the users selected for resource allocation.
"Resource Saturation": All of the cells resources were used up by other users or if, for a user active in uplink, the minimum uplink throughput demand was higher than the uplink allocated bandwidth throughput.
"Backhaul Saturation": The user was among the lowest priority service users served by a cell of a site whose defined
maximum backhaul throughputs were exceeded while allocating resources for the minimum throughput demands.
As a distribution map. To display distribution maps of a simulation, see "Displaying Simulation Results on the Map" on
page 270.
By accessing the actual values of the simulation. Actual values can be displayed either for a single simulation or as
average values for a group of simulations.
14.4.2.2.1
Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; radio resource allocation 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 throughput demands 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 throughput demands) is given.
Results: Data on the connection results:
1106
AT332_UMR_E0
The total number and percentage of users unable to connect: rejected users, and the number of rejected users
per rejection cause.
The number and percentage of users connected to a cell, the number of users per activity status, and the total
UL and DL throughputs they generate. This data is also provided by service.
Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink in all the cells of the site.
Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink in all the cells of the site.
Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink in all the cells of the site.
Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink in all the cells of the site.
Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink in all the cells of the site.
Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink in all the cells of the site.
Connection success rate (%): The percentage of users connected to any cell of the site with respect to the number
of users covered by the cells of the site.
Total number of connected users: The total number of users connected to any cell of the site in downlink, uplink,
or downlink and uplink both.
Number of connected users (DL+UL): The number of users connected to any cell of the site in downlink and uplink
both.
Number of connected users (DL): The number of users connected to any cell of the site in downlink.
Number of connected users (UL): The number of users connected to any cell of the site in uplink.
No service: The number of users unable to connect to any cell of the site for which the rejection cause was "No
service."
No service (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was
"No service."
Scheduler saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Scheduler saturation."
Scheduler saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Scheduler saturation."
Resource saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Resource saturation."
Resource saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Resource saturation."
Backhaul saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Backhaul saturation."
Backhaul saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Backhaul saturation."
Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink in all the cells of the site.
Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the downlink in all the cells of the site.
Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink in all the cells of the site.
Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink in all the cells of the site.
Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the uplink in all the cells of the site.
Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink in all the cells of the site.
Connection success rate (%) for each service: For each service, the percentage of users connected to any cell of
the site with respect to the number of users covered by the cells of the site.
The Cells tab contains the following information, per site and transmitter:
1107
Angular distributions of interference (AAS): The simulation results generated for transmitters using a smart
antenna. The results stored in this field are the angular distributions of the downlink traffic power spectral density
and the uplink noise rise. You can make the display of the downlink results diagram take into account the effect
of the antenna pattern of the single element. For more information, see the Administrator Manual.
AAS usage (DL) (%): The percentage of the downlink traffic load that corresponds to the traffic carried by the smart
antennas.
AAS usage (UL) (%): The percentage of the uplink traffic load that corresponds to the traffic carried by the smart
antennas.
MU-MIMO capacity gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO.
Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink.
Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink.
Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink.
Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink.
Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink.
Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink.
Connection success rate (%): The percentage of users connected to the cell with respect to the number of users
covered by the cell.
Total number of connected users: The total number of users connected to the cell in downlink, uplink, or downlink
and uplink both.
Number of connected users (DL+UL): The number of users connected to the cell in downlink and uplink both.
Number of connected users (DL): The number of users connected to the cell in downlink.
Number of connected users (UL): The number of users connected to the cell in uplink.
No service: The number of users unable to connect to the cell for which the rejection cause was "No service."
No service (%): The percentage of users unable to connect to the cell for which the rejection cause was "No service."
Scheduler saturation: The number of users unable to connect to the cell for which the rejection cause was "Scheduler saturation."
Scheduler saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Scheduler saturation."
Resource saturation: The number of users unable to connect to the cell for which the rejection cause was
"Resource saturation."
Resource saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Resource saturation."
Backhaul saturation: The number of users unable to connect to the cell for which the rejection cause was "Backhaul saturation."
Backhaul saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Backhaul saturation."
Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink.
Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the downlink.
Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink.
Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink.
Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the uplink.
Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink.
Connection success rate (%) for each service: For each service, the percentage of users connected to the cell with
respect to the number of users covered by the cell.
1108
X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the second
random trial).
Height: The height of the user terminal (antenna).
User profile: The assigned user profile. Atoll uses the assigned service and activity status to determine the terminal and the user profile.
Subscriber ID: The ID of the user if the user is generated from a subscriber list and not from a traffic map.
Subscriber list: The subscriber list of the user if the user is generated from a subscriber list and not from a traffic
map.
AT332_UMR_E0
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.
Mobility: The mobility type assigned during the first random trial during the generation of the user distribution.
Activity status: The assigned activity status. It can be Active DL, Active UL, Active DL+UL, or Inactive.
Connection status: The connection status indicates whether the user is connected 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.
Clutter class: The code of the clutter class where the user is located.
Indoor: This field indicates whether indoor losses have been added or not.
Best server: The best server of the user.
Serving cell: The serving cell of the serving transmitter of the user.
Layer: The layer of the serving cell of the user.
Azimuth: The orientation of the users terminal antenna in the horizontal plane. Azimuth is always considered
with respect to the North. Atoll points the user antenna towards its best server.
Downtilt: The orientation of the users terminal antenna in the vertical plane. Mechanical downtilt is positive
when it is downwards and negative when upwards. Atoll points the user antenna towards its best server.
Path loss (dB): The path loss from the best server calculated for the user.
2nd best server: The second best server of the user.
2nd best server path loss (dB): The path loss from the second best server calculated for the user.
3rd best server: The third best server of the user.
3rd best server path loss (dB): The path loss from the third best server calculated for the user.
Received preamble power (DL) (dBm): The preamble signal level received at the user location in the downlink.
Received traffic power (DL) (dBm): The traffic signal level received at the user location in the downlink.
Received pilot power (DL) (dBm): The pilot signal level received at the user location in the downlink.
Preamble C/(I+N) (DL) (dB): The preamble C/(I+N) at the user location in the downlink.
Traffic C/(I+N) (DL) (dB): The traffic C/(I+N) at the user location in the downlink.
Pilot C/(I+N) (DL) (dB): The pilot C/(I+N) at the user location in the downlink.
Preamble total noise (I+N) (DL) (dBm): The sum of the preamble interference and noise experienced at the user
location in the downlink.
Traffic total noise (I+N) (DL) (dBm): The sum of the traffic interference and noise experienced at the user location
in the downlink.
Bearer (DL): The highest WiMAX bearer available for the traffic C/(I+N) level at the user location in the downlink.
Permutation zone (DL): The downlink permutation zone allocated to the user.
BLER (DL): The Block Error Rate read from the user terminals reception equipment for the traffic C/(I+N) level at
the user location in the downlink.
Diversity mode (DL): The diversity mode supported by the cell or permutation zone in downlink.
Peak MAC channel throughput (DL) (kbps): The maximum MAC channel throughput attainable using the highest
bearer available at the user location in the downlink.
Effective MAC channel throughput (DL) (kbps): The effective MAC channel throughput attainable using the
highest bearer available at the user location in the downlink. It is calculated from the peak MAC throughput and
the BLER.
Application channel throughput (DL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
Peak MAC user throughput (DL) (kbps): The maximum MAC user throughput attainable using the highest bearer
available at the user location in the downlink.
Effective MAC user throughput (DL) (kbps): The effective MAC user throughput attainable using the highest
bearer available at the user location in the downlink. It is calculated from the peak MAC throughput and the BLER.
Application user throughput (DL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
Received power (UL) (dBm): The signal level received at the serving transmitter from the user terminal in the
uplink.
C/(I+N) (UL) (dB): The C/(I+N) at the serving transmitter of the user in the uplink.
Total noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the serving transmitter of the
user in the uplink.
Bearer (UL): The highest WiMAX bearer available for the C/(I+N) level at the serving transmitter of the user in the
uplink.
Permutation zone (UL): The uplink permutation zone allocated to the user.
BLER (UL): The Block Error Rate read from the serving cells reception equipment for the C/(I+N) level at the
serving transmitter of the user in the uplink.
Diversity mode (UL): The diversity mode supported by the cell or permutation zone in uplink.
Transmission power (UL) (dBm): The transmission power of the user terminal after power control in the uplink.
Allocated bandwidth (UL) (No. of Subchannels): The bandwidth allocated to the user in terms of the number of
subchannels allocated in the uplink after subchannelisation.
1109
Peak MAC channel throughput (UL) (kbps): The maximum MAC channel throughput attainable using the highest
bearer available at user location in the uplink.
Effective MAC channel throughput (UL) (kbps): The effective MAC channel throughput attainable using the
highest bearer available at the user location in the uplink. It is calculated from the peak MAC throughput and the
BLER.
Application channel throughput (UL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
Peak MAC allocated bandwidth throughput (UL) (kbps): The maximum MAC throughput attainable for the
number of subchannels allocated to the user using the highest bearer available at the user location in the uplink.
Effective MAC allocated bandwidth throughput (UL) (kbps): The effective MAC throughput attainable for the
number of subchannels allocated to the user using the highest bearer available at the user location in the uplink.
It is calculated from the peak MAC throughput and the BLER.
Application allocated bandwidth throughput (UL) (kbps): The application throughput is the net throughput
without coding (redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the
throughput scaling factor of the service and the throughput offset.
Peak MAC user throughput (UL) (kbps): The maximum MAC user throughput attainable using the highest bearer
available at the user location in the uplink.
Effective MAC user throughput (UL) (kbps): The effective MAC user throughput attainable using the highest
bearer available at the user location in the uplink. It is calculated from the peak MAC throughput and the BLER.
Application user throughput (UL) (kbps): The application throughput is the net throughput without coding (such
as redundancy, overhead, addressing). It is calculated from the effective MAC throughput, the throughput scaling
factor of the service and the throughput offset.
14.4.2.2.2
Frame duration
Default cyclic prefix ratio
Uplink and downlink fixed overheads
Uplink and downlink variable overheads
TDD-specific parameters: DL:UL ratio, TTG, and RTG
Uplink power control margin
Best server selection criterion
Serving cell selection method
Permutation zone selection criterion
Adaptive MIMO switching criterion
Multi-antenna interference calculation method
The input parameters specified when creating the simulation:
1110
AT332_UMR_E0
Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; radio resource allocation 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 throughput demands 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 throughput demands) is given.
The Sites (Average) tab contains the following average information per site:
Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink in all the cells of the site.
Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink in all the cells of the site.
Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink in all the cells of the site.
Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink in all the cells of the site.
Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink in all the cells of the site.
Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink in all the cells of the site.
Connection success rate (%): The percentage of users connected to any cell of the site with respect to the number
of users covered by the cells of the site.
Total number of connected users: The total number of users connected to any cell of the site in downlink, uplink,
or downlink and uplink both.
Number of connected users (DL+UL): The number of users connected to any cell of the site in downlink and uplink
both.
Number of connected users (DL): The number of users connected to any cell of the site in downlink.
Number of connected users (UL): The number of users connected to any cell of the site in uplink.
No service: The number of users unable to connect to any cell of the site for which the rejection cause was "No
service."
No service (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was
"No service."
Scheduler saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Scheduler saturation."
Scheduler saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Scheduler saturation."
Resource saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Resource saturation."
Resource saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Resource saturation."
Backhaul saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Backhaul saturation."
Backhaul saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Backhaul saturation."
Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink in all the cells of the site.
Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the downlink in all the cells of the site.
Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink in all the cells of the site.
Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink in all the cells of the site.
Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the uplink in all the cells of the site.
Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink in all the cells of the site.
Connection success rate (%) for each service: For each service, the percentage of users connected to any cell of
the site with respect to the number of users covered by the cells of the site.
1111
The Cells (Average) tab contains the following average information per cell:
Traffic load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation.
Segmentation usage (DL) (%): The percentage of the downlink traffic load that corresponds to the first downlink
PUSC zone, if it is segmented.
Traffic load (UL) (%): The traffic loads of the cells calculated on the uplink during the simulation.
UL noise rise (dB): The noise rise of the cells calculated on the uplink during the simulation.
Segmented zone UL noise rise (dB): The noise rise of the cells calculated on the uplink during the simulation for
the segmented uplink permutation zone.
Angular distributions of interference (AAS): The simulation results generated for transmitters using a smart
antenna. The results stored in this field are the angular distributions of the downlink traffic power spectral density
and the uplink noise rise. You can make the display of the downlink results diagram take into account the effect
of the antenna pattern of the single element. For more information, see the Administrator Manual.
AAS usage (DL) (%): The percentage of the downlink traffic load that corresponds to the traffic carried by the smart
antennas.
AAS usage (UL) (%): The percentage of the uplink traffic load that corresponds to the traffic carried by the smart
antennas.
MU-MIMO capacity gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO.
Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink.
Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink.
Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink.
Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink.
Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink.
Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink.
Connection success rate (%): The percentage of users connected to the cell with respect to the number of users
covered by the cell.
Total number of connected users: The total number of users connected to the cell in downlink, uplink, or downlink
and uplink both.
Number of connected users (DL+UL): The number of users connected to the cell in downlink and uplink both.
Number of connected users (DL): The number of users connected to the cell in downlink.
Number of connected users (UL): The number of users connected to the cell in uplink.
No service: The number of users unable to connect to the cell for which the rejection cause was "No service."
No service (%): The percentage of users unable to connect to the cell for which the rejection cause was "No service."
Scheduler saturation: The number of users unable to connect to the cell for which the rejection cause was "Scheduler saturation."
Scheduler saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Scheduler saturation."
Resource saturation: The number of users unable to connect to the cell for which the rejection cause was
"Resource saturation."
Resource saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Resource saturation."
Backhaul saturation: The number of users unable to connect to the cell for which the rejection cause was "Backhaul saturation."
Backhaul saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Backhaul saturation."
Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink.
Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the downlink.
Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink.
Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink.
Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the uplink.
Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink.
Connection success rate (%) for each service: For each service, the percentage of users connected to the cell with
respect to the number of users covered by the cell.
1112
AT332_UMR_E0
Frame duration
Default cyclic prefix ratio
Uplink and downlink fixed overheads
Uplink and downlink variable overheads
TDD-specific parameters: DL:UL ratio, TTG, and RTG
Uplink power control margin
Best server selection criterion
Serving cell selection method
Permutation zone selection criterion
Adaptive MIMO switching criterion
Multi-antenna interference calculation method
The input parameters specified when creating the simulation:
Coverage by C/(I+N) Level: For information on making a downlink or uplink coverage by C/(I+N) level, see "Studying
Interference and C/(I+N) Levels" on page 1065.
Service Area Analysis: For information on making a downlink or uplink service area analysis, see "Studying Downlink
and Uplink Service Areas" on page 1066.
Effective Service Area Analysis: For information on making an effective service area analysis, see "Studying Downlink
and Uplink Service Areas" on page 1066.
Coverage by Throughput: For information on making a downlink or uplink coverage by throughput, see "Making a
Coverage Prediction by Throughput" on page 1068.
Coverage by Quality Indicator: For information on making a downlink or uplink coverage by quality indicator, see
"Making a Coverage Prediction by Quality Indicator" on page 1070.
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:
1. Click the Conditions tab.
2. From the Load conditions list, select the simulation or group of simulations on which you want to base the coverage
prediction.
1113
WiMAX 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 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.
ACP uses user-defined objectives to evaluate the optimisation, as well as to calculate its implementation cost. Once you have
defined the objectives and the network parameters to be optimised, ACP uses an efficient global search algorithm to test
many network configurations and propose the reconfigurations that best meet the objectives. ACP presents the changes
ordered from the most to the least beneficial, allowing phased implementation or implementation of just a subset of the
suggested changes.
ACP is technology-independent and can be used to optimise networks using different radio access technologies. Chapter 17:
Automatic Cell Planning explains how you configure the ACP module, how you create and run an optimisation setup, and how
you can view the results of an optimisation. In this section, only the concepts specific to WiMAX networks are explained:
WiMAX Coverage
WiMAX Preamble CINR
You can also create the following objectives from the context menu of Objectives in the left-hand pane of the Objectives tab:
You define the optimisation objectives using the Objectives tab of the ACP Setup dialog box. For information on setting objective parameters, see "Setting Objective Parameters" on page 1329.
1114
Signal Level
Preamble C
AT332_UMR_E0
Preamble CN
Preamble CINR
Overlap
Best Server Distance
1st-2nd Difference
1st-Nth Difference
If you base the evaluation of a quality analysis prediction on a calculated Atoll prediction, ACP will use the display settings of the calculated Atoll prediction in the
quality analysis prediction calculated for that objective.
If you saved the display settings of a quality analysis prediction as defaults, or if you
are using a configuration file for ACP, these display settings will be used by default
and will override the display settings of the calculated Atoll prediction. For more
information on changing the display settings of a quality analysis prediction, see
"Changing the Display Properties of ACP Predictions" on page 1379.
Signal Level
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by signal level.
Base prediction settings on > "Coverage by Signal Level (DL)": ACP will evaluate coverages by signal level based
on the parameters used to calculate the selected "Coverage by Signal Level (DL)" prediction in Atoll.
Only the coverage predictions displaying a "Best Signal Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": If you select this option, you can Enable shadowing margin
and define a Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no
clutter information available, default values are used.
Preamble C
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by preamble C.
Base prediction settings on > "Effective Signal Analysis (DL)": ACP will evaluate the coverage by preamble C based
on the parameters used to calculate the selected "Effective Signal Analysis (DL)" prediction in Atoll.
Only the coverage predictions displaying a "Preamble Signal Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": If you select this option, you can Enable shadowing margin
and define a 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. Additionally, you can specify:
Service and Terminal that will be used during the calculation of preamble C through gain and losses (i.e., the
service body loss, the gain and loss of the terminal antenna, and the terminal noise factor).
Preamble C/N
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by preamble C/N.
Base prediction settings on > "Effective Signal Analysis (DL)": ACP will evaluate the coverage by preamble C/N
based on the parameters used to calculate the selected "Effective Signal Analysis (DL)" prediction in Atoll.
Only the coverage predictions displaying a "Preamble C/N Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": If you select this option, you can Enable shadowing margin
and define a 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. Additionally, you can specify:
Service and Terminal that will be used during the calculation of preamble C/N through gain and losses (i.e.,
the service body loss, the gain and loss of the terminal antenna, and the terminal noise factor).
Preamble CINR
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by preamble CINR.
Base prediction settings on > "Coverage by C/(I+N) Level (DL)": ACP will evaluate the coverage by preamble CINR
based on the parameters used to calculate the selected "Coverage by C/(I+N) Level (DL)" prediction in Atoll.
Only the coverage predictions displaying a "Preamble C/(I+N) Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": If you select this option, you can Enable shadowing margin
and define a 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. Additionally, you can specify:
1115
Service and Terminal that will be used during the calculation of preamble CINR through gain and losses (i.e.,
the service body loss, the gain and loss of the terminal antenna, and the terminal noise factor).
Calculation Method for preamble CINR. Select Using frequency plan (with or without Segmentation) or Ignoring frequency plan & segmentation.
Overlap / 1st-Nth
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by overlapping zones or by 1stNth difference.
Overlap
Base prediction settings on > "Overlapping Zones (DL)": ACP will evaluate coverages by overlapping based on
the parameters used to calculate the selected "Overlapping Zones (DL)" prediction in Atoll.
Only the Atoll predictions displaying a "Number of Servers" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": If you select this option, you can set a Minimum signal
level and a Threshold margin.
1st-Nth
Base prediction settings on > "Overlapping Zones (DL)": ACP will evaluate coverages by 1st-Nth difference
based on the parameters used to calculate the selected "Overlapping Zones (DL)" prediction in Atoll.
Since there is no Atoll prediction type equivalent to ACP WiMAX 1st-Nth Difference objective, the parameters
recovered by ACP from the selected Atoll prediction are limited to the minimum signal level and the shading.
The number of servers must always be specified manually next to No. servers.
Base prediction settings on > "Manual configuration": If you select this option, specify a Minimum signal
level and the No. servers.
In both cases, the value you specify next to No. servers determines "Nth" in the WiMAX 1st-Nth Difference
objective. For instance if you set No. servers to 4, then the "1st-4th Difference" quality parameter will be automatically selected by default in the Quality column of the WiMAX 1st-Nth Difference properties page.
- Allowed values for No. servers range from 3 to 100, with only one value available per technology.
- The "1st-2nd Difference" quality parameter (based on No. servers = 2) is provided by default.
Figure 14.16: ACP Quality Analysis Prediction Types for a WiMAX Network
1116
AT332_UMR_E0
ACP quality analysis predictions are equivalent to some of Atoll coverage predictions. The following table lists the quality analysis predictions available in ACP for WiMAX and the equivalent WiMAX coverage predictions in Atoll.
Signal Level
Preamble C
Preamble C/N
Preamble CINR
Overlap
1st-Nth Difference
N/A
(1) For more information, see "Making a Coverage Prediction by Signal Level" on page 1061.
(2) For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 1061.
Making these predictions 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 predictions 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 predictions 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 overlapping zones prediction.
ACP generated predictions are generated using the entire set of proposed changes. They do not take into account the
change subset defined on the Change Details tab.
ACP supports optimisation for transmitters belonging to different frequency bands, with predictions provided separately for each frequency band. However multiple-carrier optimisation is not supported in WiMAX (case of carriers
within same transmitters belonging to different frequency bands).
Even after committing the optimisation results, differences can remain between the ACP predictions and the predictions resulting from Atoll coverage predictions.
You can view the exact preamble CINR value on any pixel by letting the pointer rest over the pixel. The preamble CINR value
is then displayed in a tip text.
For ACP overlapping zones predictions, you can:
For each network quality coverage prediction, ACP offers a prediction showing the initial network state, the final network
state, and a prediction showing the changes between the initial and final state.
1117
The data contained in a drive test data path is used to verify the accuracy of current network parameters and to optimise the
network.
This section covers the following topics:
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 WiMAX networks, a cell can be identified by its BSID (6-byte MAC address) or its preamble index.
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 with 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:
1. In the Network explorer, right-click the Drive Test Data folder and select Import from the context menu. The Open
dialog box appears.
2. Select the file or files you want to open. You can import one or several files.
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.
3. Click Open. The Import of Measurement Files dialog box appears.
Files with the extension PLN, as well as some FMT files (created with old versions of TEMS)
are imported directly into Atoll; you will not be asked to define the data structure using
the Import of Measurement Files dialog box.
4. 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 dialog box. If you do not have
an import configuration, continue with step 5.
a. Under Import configuration, select an import configuration from the Configuration list.
b. Continue with step 8.
When importing a drive test data path file, existing configurations are available in
the Files of type list of the Open dialog box, 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.
5. Click the General tab. On the General tab, you can set the following parameters:
1118
Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if
desired.
AT332_UMR_E0
Under Receiver, set the Height of the receiver antenna and the Gain and Losses.
Under Measurement conditions:
Figure 14.17: The Setup tab of the Import of Measurement Files dialog box
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 dialog box 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 that uses BSID as the cell identifier:
i.
ii. In the By BSID identifier box, enter a string found in the column name that identifies the BSID of scanned cells.
For example, if the string "BSID" is found in the column names identifying the BSID of scanned cells, enter it
here. Atoll will then search for the column with this string in the column name.
e. If you are importing data that uses the preamble index as the cell identifier:
i.
ii. In the By preamble index identifier box, enter a string found in the column name that identifies the preamble
indexes of scanned cells. For example, if the string "Preamble" is found in the column names identifying the
preamble indexes of scanned cells, enter it here. Atoll will then search for the column with this string in the
column name.
f.
1119
If you have correctly entered the information under File on the Setup tab, and the
necessary values in the Drive Test Data Setup dialog box, Atoll should recognise 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>". Columns marked with
"<Ignore>" will not be imported.
The data in the file must be structured so that the column identifying the preamble
index or the BSID is placed before the data columns for each cell. Otherwise Atoll
will not be able to properly import the file.
7. 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 dialog box appears.
b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atoll installation folder. In
case you cannot write into that folder, you can click Browse to choose a different location.
c. Enter a Configuration name and an Extension of the files that this import configuration will describe (for example,
"*.txt").
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 can select this
import configuration from the Import 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 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 dialog box.
You can delete an existing import configuration by selecting the import configuration file under Import configuration and clicking the Delete button.
8. Click Import, if you are only importing a single file, or Import all, if you are importing more than one file. The drive test
data is imported into the current Atoll document.
1120
AT332_UMR_E0
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, the Shadings dialog box opens in which you can define the
following display for each single point of the measurement path:
You can, for example, display a signal level in a certain colour, choose a symbol for each transmitter (such as a circle,
triangle, cross) 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 in the Network explorer 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 dialog box and select Save or Load from
the Display Configuration submenu.
"Filtering Measurement Points Along Drive Test Data Paths" on page 1120
"Predicting the Signal Level on Drive Test Data Points" on page 1121
"Creating Coverage Predictions on Drive Test Data Paths" on page 1122
"Displaying Statistics Over a Drive Test Data Path" on page 1123
"Extracting a Field From a Drive Test Data Path for a Transmitter" on page 1123
"Analysing Measurement Variations Along the Path" on page 1123
You can apply a filter on all the drive test data paths in the Drive Test Data folder
by selecting Filter from the context menu of the folder.
If you want to use the measurement points that you permanently deleted, you will
have to import the drive test data path again.
1121
5. Click More to filter out measurement points using an advanced filter. The Filter dialog box appears. For more information on using the Filter dialog box, see "Advanced Data Filtering" on page 101.
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 folder.
Figure 14.19: Selecting Measured Signal Levels for which Errors will be Calculated
4. Click OK. A point prediction is created for the selected drive test data path.
5. Right-click the drive test data path and select Calculations > Calculate All the Predictions from the context menu.
If you chose to have Atoll calculate the errors between measured and predicted signal levels, new columns are added to the
drive test data table for the predicted point signal level from the serving cell and the errors between the measured and
predicted values.
1122
AT332_UMR_E0
Figure 14.20: Drive Test Data Table after Point Signal Level Prediction (with Error Calculations)
New columns are also added for the predicted point signal level from each neighbour cell and the errors between the
predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For
more information on the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 1123.
The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main
matrix. For more information on propagation models, see Chapter 4: Radio Calculations and Models.
On the Conditions tab, you can set the range of the 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 an Overlap 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. Indoor losses are defined per frequency
per clutter class.
On the Conditions tab, you can select which simulation to study in the Load conditions list. Or you can select
a group of simulations to perform an average statistical analysis of all simulations.
If you want to perform the coverage prediction without a simulation, you can select "(Cells Table)" from Load
conditions.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 1062.
You can also select a cell Layer, or carry out the prediction for the "Best" layer.
If you want the preamble C/(I+N) 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 select the Indoor coverage check box to add indoor losses. Indoor losses are defined per frequency
per clutter class.
3. When you have finished setting the parameters for the coverage prediction, click OK.
You can create other coverage predictions by repeating the procedure from step 1. to step 3. for each new coverage
prediction.
4. When you have finished creating coverage predictions for these drive test data, right-click the drive test data and
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 4: Radio Calculations and
Models).
You can display the information in these new columns in the Drive Test Data analysis tool. For more information on
the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 1123.
1123
14.6.4.5 Extracting a Field From a Drive Test Data Path for a Transmitter
You can extract information for a selected transmitter from a field of a drive test data path. The extracted information is available in a new column in the drive test data table.
To extract a field from a drive test data path:
1. In the Network explorer, expand the Drive Test Data folder, right-click the drive test data from which you want to
extract a field, and select Focus on a Transmitter from the context menu. The Field Selection for a Given Transmitter
dialog box appears.
2. Under On the transmitter, select the transmitter for which you want to extract a field.
3. Under For the fields, select the fields that you want to extract for the selected transmitter.
4. Click OK. Atoll creates a new column in the drive test data path table for the selected transmitter and with the selected
values.
1124
AT332_UMR_E0
2. In the Drive Test Data analysis tool, click the Display button. The Display Parameters dialog box appears (see Figure
14.22).
Select the check box next to each field you want to display in the Drive Test Data analysis tool.
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.
You can change the display status or the colour of more than one field at the same time by
selecting several fields. 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 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 analysis tool.
4. You can display the data in the drive test data path in the following ways:
The drive test data path appears in the map window as an arrow pointing towards the best server (see Figure 14.21
on page 1123) in the same colour as the transmitter.
5. You can display a secondary 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 dialog box. You select the value to be
displayed from the right-hand list at the top of the Drive Test Data analysis tool. The values are displayed in the colour
defined in the Display Parameters dialog box.
6. You can zoom in on the graph displayed in the Drive Test Data analysis tool in the following ways:
Zoom in or out:
i.
Right-click the Drive Test Data analysis tool. The context menu appears.
Right-click the Drive Test Data analysis tool on one end of the range of data you want to zoom in on. The context menu appears.
1125
If you open the table for the drive test data you are displaying in the Drive Test Data analysis tool, Atoll will automatically display in the table the data for the point that is displayed
in the map and in the Drive Test Data analysis tool (see Figure 14.21 on page 1123).
1126
AT332_UMR_E0
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 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 the Atoll Automatic Cell Planning (ACP) module.
This section covers the following topics:
Select File > Open or File > New > From an Existing Database.
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.
1127
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.
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 107. 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
"Associating a Tip Text to an Object" on page 54.
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 "Changing the Order of
Layers" on page 51.
Figure 14.23 shows an example of WiMAX transmitters with labels and displayed in the Legend window, and GSM transmitter
data displayed in a tip text.
1128
AT332_UMR_E0
When you click the Calculate button, Atoll first 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 and Unlocking Coverage Predictions" on page 207.
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 recalculate all path loss matrices before calculating coverage predictions:
1. Click the Force Calculate button (
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.
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.
1129
14.7.2.2.1
14.7.2.2.2
14.7.2.2.3
1130
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 14.4). 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.
AT332_UMR_E0
14.7.2.2.4
14.7.2.2.5
1131
Figure 14.25: 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 Apply Configuration and have to be set up manually.
When Use coverage conditions is not selected, the defined Distance is used to allocate neighbours to a reference
transmitter.
When Use coverage conditions is selected, click Define for IEEE 802.16e to open the corresponding Coverage Conditions dialog box:
1132
Resolution: Enter the resolution to be used to calculate cell coverage areas during automatic neighbour allocation.
Margin: Enter a handover margin.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this option to take indoor losses into account in calculations. Indoor losses are defined
per frequency per clutter class.
AT332_UMR_E0
Co-site neighbours: Cells located on the same site as the reference transmitter will automatically be considered as
neighbours. A transmitter/cell with no antenna cannot be considered as a co-site neighbour.
Exceptional pairs: Select this option to force the neighbour relations defined in the Inter-technology Exceptional pairs
table. For more information, see "Defining Exceptional Pairs" on page 223.
Description
When
Distance
Coverage
Co-Site
Exceptional Pair
Exceptional pairs
is selected
Existing
1133
Click the Run button to run the optimisation immediately. For information on running the optimisation, see "Running
an Optimisation Setup" on page 1359. For information on the optimisation results, see "Viewing Optimisation Results"
on page 1362.
Click the Create Setup button to save the defined optimisation to be run later.
1134
AT332_UMR_E0
Name: Enter a name for the frequency band, for example, "3.3 GHz - 10 MHz". Each WiMAX frequency band has
a specific channel width. Mentioning the channel width in the frequency band name is a good approach. This name
will appear in other dialog boxes when you select a frequency band.
Duplexing method: Select the duplexing method used in the frequency band from the list.
Start frequencies (MHz): Enter the start frequency for TDD frequency bands, and the downlink and the uplink start
frequencies for FDD frequency bands.
Channel width (MHz): Enter the channel width for each channel in the frequency band.
Inter-channel spacing (MHz): Enter the spacing between any two consecutive channels in the frequency band.
Sampling factor: Enter the sampling factor for calculating the sampling frequency.
First channel: Enter the number of the first channel in this frequency band.
Last channel: Enter the number of the last channel in this frequency band. If this frequency band has only one carrier, enter the same number as entered in the First channel field.
Step: Enter the step between any two consecutive channel numbers in the frequency band.
Excluded channels: Enter the channel numbers which do not belong to the frequency band. You can enter nonconsecutive channel numbers separated with a comma, or you can enter a range of channel numbers separating
the first and last index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
Adjacent channel suppression factor (dB): Enter the adjacent channel interference suppression factor in dB. Interference received from adjacent channels is reduced by this factor during the calculations.
3. When you have finished adding frequency bands, click the Close button (
).
You can also access the properties dialog box of each individual frequency band by double-clicking the left margin of the table
row containing the frequency band.
Frame duration: The frame length in milliseconds. You can choose from a list of frame durations defined in the IEEE
802.16 specifications.
Default cyclic prefix ratio: The total symbol duration in WiMAX comprises the useful part of the symbol, carrying the
data bits, and a CRC part, which is a portion of the useful data part repeated at the beginning of each symbol. Cyclic
prefix is used in WiMAX to counter inter-symbol interference (ISI). The cyclic prefix and the orthogonality of subcarriers ensure that there is negligible intra-cell interference in WiMAX. This value is used in calculations if no cyclic prefix
is defined in a cell frame configuration.
Fixed and variable overheads: The fixed and variable overheads in the uplink and downlink subframes are used to
model the preamble and other time-domain overheads such as broadcast messages including DL-MAP, UL-MAP, UCD,
and DCD, and the FCH, in downlink, and Ranging and Bandwidth Request messages in the uplink. The preamble is
always one symbol duration long and can be modelled using the fixed overhead, while other messages whose lengths
vary according to either the frame duration or the channel bandwidth can be modelled using the variable overheads.
Due to this reason, fixed overheads are available in terms of symbol durations (SD) and the variable overheads in
terms of percentages of the uplink and downlink subframes. Variable overheads are percentages of the downlink and
the uplink subframes excluding the fixed overheads.
1135
DL:UL ratio (TDD only): This ratio represents the fractions of the frame duration which correspond to downlink and
uplink subframes. In FDD networks, the downlink and uplink subframes have the same durations as the frame itself.
In TDD networks, the downlink and uplink subframes use the same frequency but are duplexed in time.
You can define the DL:UL ratio as percentages: you can enter the percentage of the DL subframe with respect to the
total frame duration and the percentage corresponding to the uplink subframe is assumed to be equal to the remaining part of the frame. You can choose to define the DL:UL ratio in terms of fractions of the total number of symbol
durations available in one frame. For example, if the WiMAX frame contains 47 symbol durations, you can set the
downlink fraction to 32 and uplink to 15 (instead of a percentage of 66.667%) so that Atoll uses the exact numbers of
downlink and uplink symbol durations as entered in calculations.
The exact number of symbol durations in one frame depends on various parameters (channel bandwidth, frame duration, cyclic prefix lengths, sampling factor, and so on). Some of
these parameters can be different in each cell. Therefore, the exact numbers of symbol
durations in downlink and uplink subframes can be different in each cell as well. The exact
numbers of symbol durations in the downlink and uplink subframes are calculated by Atoll
for each cell according to the DL:UL ratio that you set on the Global Parameters tab. For
example, a DL:UL ratio of 36:12 would actually give 36:12 for a 5 MHz channel (sampling
factor = 1.12 and FFT size = 512) but would give 26:8 for a 7 MHz channel (sampling factor
= 1.14286 and FFT size = 1024) with the following configuration:
Frame Duration = 5 ms
Cyclic Prefix = 1/8
DL Fixed Overhead = UL Fixed Overhead = 0
TTG = RTG = 0 ms
DL:UL Ratio = 36:12
For more information on how this is calculated, see the Technical Reference Guide.
Transmission and reception time guards (TDD only): Transmission and reception time guards are also time domain
overheads, which means that these are portions of the frame which cannot be used for data transfer. You can enter
TTG and RTG times in milliseconds.
Best server selection criterion: You can select whether the best server selection will be based on the preamble C or
the preamble C/(I+N). Depending on the selected method, Atoll compares either the preamble C or the preamble C/
(I+N) from different transmitters at each pixel (or mobile) to determine the best server.
Serving cell selection method: The serving cell selection method is used to determine the serving cell for transmitters
supporting more than one cell. The best serving transmitter for a pixel, subscriber, or mobile is determined according
to the received preamble signal level from the cell with the highest preamble power. If more than one cell of the same
transmitter covers the pixel, subscriber, or mobile, the serving cell is determined according to the selected method:
Random: When calculating coverage predictions and in calculations on subscriber lists, the cell of the highest priority layer is selected as the serving cell. In Monte Carlo simulations, a random cell is selected as the serving cell.
Distributive: When calculating coverage predictions and in calculations on subscriber lists, the cell of the highest
priority layer is selected as the serving cell. In Monte Carlo simulations, mobiles are distributed among cell layers
one by one, i.e., if more than one cell layer covers a set of mobiles, the first mobile is assigned to the highest priority layer, the second mobile to the second highest priority layer, and so on.
The serving cell once assigned to a mobile does not change during Monte Carlo simulations. For more information on
defining layers, see "Defining Network Deployment Layers" on page 1137.
Uplink power control margin: The margin (in dB) that will be added to the bearer selection threshold, for safety
against fast fading, when performing power control in uplink.
Permutation zone selection criterion: You can select whether the permutation zone selection will be based on the
preamble C/N or the preamble C/(I+N). Depending on the selected criterion, Atoll compares either the preamble C/N
or the preamble C/(I+N) with the quality threshold defined for the permutation zones in the Frame Configurations
properties. For more information on the permutation zone quality threshold, see "Defining Frame Configurations" on
page 1138.
Adaptive MIMO switching criterion: You can select whether the MIMO mode selection will be based on the preamble
C/N or the preamble C/(I+N). Depending on the selected criterion, Atoll compares either the preamble C/N or the preamble C/(I+N) with the AMS threshold defined for the cell.
Multi-antenna interference calculation method: You can select the calculation method for interference from multiantenna cells. The calculated interference can be either proportional to the number of antennas or independent of
the number of antennas.
Figure 14.26 depicts a WiMAX frame with the described parameters marked.
1136
AT332_UMR_E0
Min interferer C/N threshold: Minimum requirement for interferers to be considered in calculations. Interfering cells
from which the received carrier-power-to-noise ratio is less than this threshold are discarded.
For example, setting this value to -20 dB means that interfering cells from which the received signals are 100 times
lower than the thermal noise level will be discarded in calculations. The calculation performance of interferencebased coverage predictions, interference matrices calculations, and Monte Carlo simulations can be improved by
setting a high value of this threshold.
Height/ground: The receiver height at which the path loss matrices and coverage predictions are calculated. Calculations made on mobile users (from traffic maps) in Monte Carlo simulations are also carried out at this receiver height.
Calculations made on fixed subscribers (from subscriber lists) in Monte Carlo simulations are carried out at their
respective heights.
Default max range: The maximum coverage range of transmitters in the network.
You can use the Default max range parameter to limit the coverage range of transmitters in order to avoid uplink-todownlink interference in TDD networks. In TDD networks, the TTG and RTG parameters, available on the Global
Parameters tab of the Radio Network Settings folder properties dialog box, define the time delays required by the
cell and mobile equipment to switch from transmission to reception modes and vice versa. You can determine the
maximum coverage range that the sectors of your WiMAX network should have from the values of TTG and RTG and
use this range as the Default max range parameter. You can calculate the maximum system range from TTG and RTG
values as follows:
Max Range (m) = Min(TTG, RTG) x 300000/2
Here TTG and RTG are values in milliseconds, "Max range" is in metres, and the "Min()" function returns the lower of
the two values given to it in the parentheses.
1137
The DL:UL ratio entered as a fraction must include the symbol duration(s) used by the preamble or any other fixedduration overheads. During calculations, Atoll first determines the total amount of resources available in one frame
and then the resources effectively available for user data by removing any fixed and variable overheads that you have
defined.
Best server selection: In this section, you can choose the best server selection Criterion.
Serving cell selection: In this section, you can choose the serving cell selection Method.
Uplink power control: In this section, you can enter the uplink power control Margin.
Permutation zone selection: In this section, you can choose the permutation zone selection Criterion.
Adaptive MIMO switching: In this section, you can choose the adaptive MIMO switching Criterion.
Multi-antenna interference calculation: In this section, you can choose the multi-antenna interference calculation Method.
5. Select the Calculation Parameters tab. On this tab you can set:
Calculation limitation: In this section, you can enter the Min interferer C/N threshold.
Receiver: In this section, you can enter the receiver Height.
System: In this section, select the Default max range check box if you want to apply a maximum system range
limit, and enter the maximum system range in the text box to the right.
6. Click OK. The global parameters are used during coverage predictions and simulations for the entire network.
Index: The layer index is automatically assigned by Atoll to each new layer that you create.
Name: The name of the network layer.
Priority: The priority of the network layer.
3. When you have finished adding network layers, click the Close button (
1138
).
AT332_UMR_E0
3. Double-click the frame configuration row in the table once the new frame configuration has been added to the table.
The frame configuration Properties dialog box opens.
4. Under the General tab, you can modify the parameters that you set previously.
5. Under the Permutation Zones tab, you have the following parameters:
Max speed: The maximum vehicular speed supported by the permutation zone.
Max distance: The maximum distance from the base station covered by the permutation zone.
Priority: The priority of the permutation zone in terms of its allocation to a user.
Diversity support: The type of antenna diversity technique (AAS, STTD/MRC, SU-MIMO, AMS, or MU-MIMO) supported by the permutation zone. You cannot select more than one type of MIMO technique (STTD/MRC, SUMIMO, MU-MIMO, or AMS) at a time.
Specific calculations are performed (and gains applied) for terminals supporting AAS and MIMO. A permutation
zone that only supports None does not have any antenna diversity mechanism, and all the terminal types can connect to this zone. A permutation zone that supports None and one or more antenna diversity techniques can also
support terminals capable of those diversity techniques. For example, None+AAS can support simple as well as
AAS-capable terminals, and None+AMS can support simple and MIMO-capable terminals. Simple terminals cannot connect to a permutation zone that does not support None.
Zone 0 subchannel groups (segment 0): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned
to the segment 0 for the permutation zone 0.
Zone 0 subchannel groups (segment 1): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned
to the segment 1 of the permutation zone 0.
Zone 0 subchannel groups (segment 2): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned
to the segment 2 of the permutation zone 0.
Zone 8 subchannels (segment 0): The subchannels assigned to the segment 0 for the permutation zone 8.
1139
Zone 8 subchannels (segment 1): The subchannels assigned to the segment 1 for the permutation zone 8.
Zone 8 subchannels (segment 2): The subchannels assigned to the segment 2 for the permutation zone 8.
You can enter non-consecutive subchannel numbers separated with a comma, or you can enter a range of subchannels separating the first and last index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4,
5").
Permutation zones are allocated to users based on the Quality threshold (dB), Max speed (km/h), Max distance, and Priority
parameters. The quality threshold, maximum speed, and maximum distance criteria are used to determine the possible
permutation zones for each user. Then, the highest priority permutation zone among the possible permutation zones is allocated to the user.
During Monte Carlo simulations, two values of uplink noise rise are calculated per cell, one for the segmented permutation
zone and one for the non-segmented permutation zones. For cells using smart antennas, one angular distribution of uplink
noise rise is calculated per cell. This angular distribution of uplink noise rise is considered to include both segmented and nonsegmented permutation zones.
To see examples of how to set up cells with and without downlink segmentation, and how to set up cells with PUSC, FUSC,
and permutation zones of other subchannel allocation modes, see "Tips and Tricks" on page 1152.
Radio bearer index: Enter a bearer index. This bearer index is used to identify the bearer in other tables, such as
the bearer selection thresholds and the quality graphs in reception equipment.
Name: Enter a name for the bearer, for example, "16QAM3/4." This name will appear in other dialog boxes and
results.
Modulation: Select a modulation from the list of available modulation types. This column is for information and
display purposes only.
Channel coding rate: Enter the coding rate used by the bearer. This column is for information and display purposes
only.
Bearer efficiency (bits/symbol): Enter the number of useful bits that the bearer can carry in a symbol. This information is used in throughput calculations.
For information on the relation between bearer efficiency and spectral efficiency, see "Relation Between Bearer
Efficiency And Spectral Efficiency" on page 1153.
Name: Enter a name for the quality indicator, for example, "BLER" for Block Error Rate. This name will appear in
other dialog boxes and results.
Used for data services: Select this check box to indicate that this quality indicator can be used for data services.
Used for voice services: Select this check box to indicate that this quality indicator can be used for voice services.
1140
AT332_UMR_E0
General: On this tab, you can define the Name of the reception equipment.
Thresholds: On this tab (see Figure 14.28), you can modify the bearer selection thresholds for different mobility
types. A bearer is selected for data transfer at a given pixel if the received carrier-to-interference-and-noise ratio
is higher than its selection threshold. For more information on bearers and mobility types, see "Defining WiMAX
Radio Bearers" on page 1139 and "Modelling Mobility Types" on page 1063, respectively.
Click the Selection thresholds button. The C/(I+N) Thresholds (dB) dialog box appears (see Figure 14.29).
1141
Quality Graphs: On this tab (see Figure 14.30), you can modify the quality indicator graphs for different bearers
and mobility types. These graphs depict the performance characteristics of the equipment under different radio
conditions. For more information on bearers, quality indicators, and mobility types, see "Defining WiMAX Radio
Bearers" on page 1139, "Defining WiMAX Quality Indicators" on page 1139, and "Modelling Mobility Types" on
page 1063, respectively.
Click the Quality graph button. The Quality Graph dialog box appears (see Figure 14.31).
Traffic MIMO Gains: On this tab (see Figure 14.32), you can modify the SU-MIMO and STTD/MRC gains for different bearers, mobility types, subchannel allocation modes, BLER values, and numbers of transmission and reception antennas. The MIMO throughput gain is the increase in channel capacity compared to a SISO system. Diversity
gains can be defined for different diversity modes: STTD/MRC, SU-MIMO, and MU-MIMO. STTD/MRC gain is
applied to the traffic and pilot C/(I+N) when the diversity mode is STTD/MRC. SU-MIMO diversity gain is applied
to the traffic and pilot C/(I+N) when the diversity mode is SU-MIMO. MU-MIMO diversity gain is applied to the
traffic and pilot C/(I+N) when the diversity mode is MU-MIMO.
For more information on bearers and mobility types, see "Defining WiMAX Radio Bearers" on page 1139 and
"Modelling Mobility Types" on page 1063, respectively. For more information on the different MIMO systems, see
"Multiple Input Multiple Output (MIMO) Systems" on page 1148.
1142
AT332_UMR_E0
No MIMO gain (STTD/MRC, SU-MIMO, and MU-MIMO) is applied if the numbers of transmission and reception antennas are both equal to 1.
Click the Max MIMO gain graphs button. The Max MIMO Gain dialog box appears (see Figure 14.33).
Preamble MIMO Gains: On this tab (see Figure 14.34), you can enter diversity gains for the preamble for different
mobility types, and numbers of transmission and reception antennas. The preamble diversity gain is applied to the
preamble C/N and C/(I+N) when the cell and terminal both support any form of MIMO in downlink.
1143
Priority
UGS
Highest
ErtPS
rtPS
nrtPS
Best Effort
Lowest
Throughput Demands
1144
AT332_UMR_E0
...
c. Users of a service with QoS class = ErtPS, Service priority = N
d. Users of a service with QoS class = ErtPS, Service priority = N-1
...
e. Users of a service with QoS class = rtPS, Service priority = N
f.
...
g. Users of a service with QoS class = nrtPS, Service priority = N
h. Users of a service with QoS class = nrtPS, Service priority = N-1
In order to be connected, users active in downlink and uplink must be able to get their minimum throughput in both
directions. If a user active in downlink and uplink gets his minimum throughput in only one direction, he will be
rejected.
3. Resource allocation for supporting the Max throughput demands: Once the resources have been allocated for supporting the minimum throughput demands in the previous step, the remaining resources can be allocated in different
ways to support the maximum throughput demands of the users. The last four QoS classes can have maximum
throughput demand requirements.
For allocating resources to support the maximum throughput demands, the following types of scheduling methods
are available:
Proportional fair: The proportional fair scheduling method allocates the same amount of resources to all the users
with a maximum throughput demand. Therefore, the resources allocated to each user are either the resources it
requires to achieve its maximum throughput demand or the total amount of resources divided by the total
number of users in the cell, which ever is smaller. The proportional fair scheduler can also model the effect of
resource scheduling over time, i.e., how a proportional fair scheduler benefits from fast fading, by applying multiuser diversity gains (MUG) to user throughputs.
Proportional demand: The proportional demand scheduling method allocates resources proportional to the
demands of users who have a maximum throughput demand. Therefore, users with higher maximum throughput
demands will have higher resulting throughputs than the users with lower maximum throughput demands.
Biased (QoS class): The biased scheduling method first determines the amount of resources available for the users
of each QoS class, and then allocates these resources among the users of each QoS class like a proportional fair
scheduler. The percentage of the remaining resources that are available for any QoS class is determined based on
the QoS class bias factor and the priorities of the QoS classes:
1 i
N i ---
- 100
% of resources available for QoS Class i = ---------------------------------i
N 1
- i
Where i represents the QoS classes that have a maximum throughput demand, i.e., ErtPS (i = 1), rtPS (i = 2), nrtPS
(i = 3), and Best Effort (i = 4). N i is the number users of QoS class i, and is the QoS class bias determined from
QoS
QoS
f
100
Bias
-.
the QoS class bias factor f Bias as follows: = 1 + ----------
The QoS class bias factor should be set so as to achieve a valid value of . For example, for
equal numbers of users in each QoS class,
QoS
QoS
Max aggregate throughput: This scheduling method allocates the resources required by the users to achieve their
maximum throughput demands in the order of their traffic C/(I+N). This means that users who are under good
radio conditions, high traffic C/(I+N), will get the resources they require. The end result of this scheduling method
is that the aggregate cell throughputs are maximised.
1145
Round robin: The round robin scheduling method allocates the same amount of resources to all the users with a
maximum throughput demand. Therefore, the resources allocated to each user are either the resources it requires
to achieve its maximum throughput demand or the total amount of resources divided by the total number of users
in the cell, which ever is smaller.
For all the scheduling methods, resources are allocated to support the maximum throughput demand until either the
maximum throughput demands of all the users are satisfied or the scheduler runs out of resources.
The Schedulers table lists the available schedulers. You can add, remove, and modify scheduler properties, if you want.
To define WiMAX schedulers:
1. In the Parameters explorer, expand the Radio Network Settings folder, right-click Schedulers and select Open Table.
The Schedulers table appears.
2. In the table, enter one scheduler per row. For information on working with data tables, see "Data Tables" on page 75.
For each scheduler, enter:
Name: Enter a name for the scheduler. This name will appear in the cell properties.
Scheduling method: Select the scheduling method used by the scheduler for allocating resources to support the
maximum throughput demands.
QoS class bias factor: For the schedulers using Biased (QoS class) scheduling method, enter the bias factor to be
used for distributing resources between different QoS classes. QoS class bias factor = 0 means no bias.
Target throughput for voice services: Select the throughput that the scheduler will target to satisfy for all voicetype services.
Target throughput for data services: Select the throughput that the scheduler will target to satisfy for all datatype services.
Bearer selection criterion: Select the criterion for the selection of the best bearer.
Bearer index: The best bearer selected for throughput calculations is the one with the highest bearer index
among the bearers available in the reception equipment.
Peak MAC throughput: The best bearer selected for throughput calculations is the one with the highest peak
MAC throughput (including SU-MIMO gains) among the bearers available in the reception equipment.
Effective MAC throughput: The best bearer selected for throughput calculations is the one with the highest
effective MAC throughput (including SU-MIMO gains) among the bearers available in the reception equipment.
Uplink bandwidth allocation target: Select the goal of the uplink subchannelisation (bandwidth allocation).
Full bandwidth: All the subchannels are used for the uplink C/(I+N) calculations, which means that no
subchannelisation is performed.
Maintain connection: The number of subchannels is reduced one by one in order to increase the uplink C/
(I+N) so that the mobile is able to get at least the lowest bearer.
Best bearer: The number of subchannels is reduced in order to increase the uplink C/(I+N) so that the mobile
is able to get the best bearer available. The definition of the highest bearer depends on the Bearer selection
criterion, i.e., highest index, highest peak MAC throughput, or highest effective MAC throughput.
When Bearer selection criterion is set to Effective MAC throughput, Atoll calculates the effective MAC
throughput for all possible combinations of [number of subchannels, bearers], and keeps the number of
subchannels and the bearer which provide the highest effective MAC throughput.
You can open a scheduler properties dialog box by double-clicking the corresponding row in the Schedulers table. In
the properties dialog box, a MUG tab is available for the Proportional fair scheduling method. On the MUG tab, you
can enter the throughput gains due to multi-user diversity for different mobility types and the maximum traffic C/(I+N)
above which the gains are not applied.
3. Click the Close button (
1146
AT332_UMR_E0
also be one or more nulls in the directions of the interfering signals. If the optimum beamformer uses L antenna elements, it
is possible to create L1 nulls and, thereby, cancel L1 interfering signals.
In a mobile environment where the sources of interference are not stationary, the antenna patterns are adjusted so that the
nulls remain in the direction of the moving interference sources. Atoll smart antenna models support linear adaptive array
systems.
TDD WiMAX networks are more suitable for smart antennas than FDD because of the similar uplink and downlink channel
characteristics in TDD. Information gathered from a mobile in the uplink can be assumed valid for downlink as well.
Atoll WiMAX module includes the following smart antenna modelling types:
The following section explains how to work with smart antenna equipment in Atoll:
1147
3. Double-click the equipment entry in the Smart Antenna Equipment table once your new equipment has been added
to the table. The equipment Properties dialog box opens.
4. Under the General tab, you can modify the parameters that you set previously.
5. To modify the properties of the smart antenna model assigned to the smart antenna equipment, click the Parameters
button under Smart antenna models. The smart antenna model properties dialog box appears.
a. Click the General tab. On the General tab, you can change the default Name of the smart antenna model.
b. Click the Properties tab (see Figure 14.35). On the Properties tab, you can define:
Number of elements: The number of antenna elements in the smart antenna system.
Single element pattern: The antenna model to be used for each antenna element. You can select an antenna
model from the list. The list contains the antennas available in the Antennas folder.
Diversity gain (cross-polarisation): Select the Diversity gain (cross-polarisation) check box if you are using
cross-polarised smart antennas and want to add diversity gains to the calculated downlink beamforming gains.
You can define the diversity gains per clutter class on the Clutter tab of the smart antenna model properties
dialog box.
1148
Array gain offset (dB): Enter an offset to be added to the calculated beamforming array gains on pilot and traffic subcarriers. Positive offset values are considered as gains while negative values are considered as losses.
Power combining gain offset (dB): Enter an offset to be added to the calculated power combining gains on
preamble, pilot, and traffic subcarriers. Positive offset values are considered as gains while negative values are
considered as losses.
AT332_UMR_E0
Diversity gain (cross-polarisation) (dB): Enter the diversity gains for cross-polarised smart antennas to be
applied to preamble, pilot, and traffic subcarriers.
1149
In Atoll, you can set whether a permutation zone supports SU-MIMO by selecting the corresponding diversity support mode
frame configuration properties (see "Defining Frame Configurations" on page 1138). SU-MIMO capacity gains can be defined
in the reception equipment for different numbers of transmission and reception antennas, mobility types, bearers, subchannel allocation modes, and maximum BLER. For more information on SU-MIMO gains, see "Defining WiMAX Reception Equipment" on page 1140.
During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to uplink and
downlink permutation zones that support SU-MIMO, will benefit from the SU-MIMO gain in its throughput depending on its
traffic C/(I+N).
When SU-MIMO improves the channel capacity or throughputs, the traffic C/(I+N) of a user is first determined. Once the traffic C/(I+N) is known, Atoll calculates the user throughput based on the bearer available at the user location. The obtained user
throughput is then increased according to the SU-MIMO capacity gain and the SU-MIMO gain factor of the user clutter class.
The capacity gains defined in Max SU-MIMO gain graphs are the maximum theoretical capacity gains using SU-MIMO. SUMIMO requires rich multipath environment, without which the gain is reduced. In the worst case, there is no gain. Therefore,
it is possible to define an SU-MIMO gain factor per clutter class whose value can vary from 0 to 1 (0 = no gain, 1 = 100% gain).
For information on setting the SU-MIMO gain factor for each clutter class or for all clutter classes, see "Defining Clutter Class
Properties" on page 127.
The SU-MIMO capacity gain vs. C/(I+N) graphs available in Atoll by default have been generated based on the maximum theoretical SU-MIMO capacity gains obtained using the following equations:
CC MIMO
G MIMO = --------------------CC SISO
TX
RX
C I + N
Where CC MIMO = Min N Ant N Ant Log 2 1 + ----------------------------------------- is the channel capacity at a given C/(I+N) for a MIMO system
TX
RX
TX
RX
using N Ant transmission and N Ant reception antenna ports. CC SISO = Log 2 1 + C I + N is the channel capacity for a
single antenna system at a given C/(I+N). C/(I+N) is used as a ratio (not dB) in these formulas. You can replace the default SUMIMO capacity gain graphs with graphs extracted from simulated or measured values.
1150
AT332_UMR_E0
lation of uplink throughput coverage predictions. The channel throughput is multiplied by this gain for pixels where MU-MIMO
is used as the diversity mode.
A point analysis (see "Studying the Profile Around a Base Station" on page 1048)
A coverage prediction (see "Studying Signal Level Coverage of a Single Base Station" on page 1060).
Atoll always takes shadowing into consideration when calculating a Monte Carlo simulations. Atoll uses the values defined
for the model standard deviations per clutter class when calculating the signal level coverage predictions. Atoll uses the values
defined for the C/I standard deviations per clutter class when calculating the interference-based coverage predictions.
You can display the shadowing margins per clutter class.
To display the shadowing margins per clutter class:
1. In the Network explorer, right-click the Predictions folder and select Shadowing Margins from the context menu. The
Shadowing Margins dialog box appears.
2. 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 dialog box is for information only.
Standard deviation: Select the type of standard deviation to be used to calculate the shadowing margin:
Model: The model standard deviation. Atoll will display the shadowing margin of the signal level.
C/I: The C/I standard deviation. Atoll will display the C/I shadowing margin.
Interference received by mobiles on the downlink: Interference can be received by mobiles in a WiMAX network on
the downlink from external base stations and mobiles in the vicinity.
Interference from external base stations (also called downlink-to-downlink interference) can 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
(such as GSM, UMTS, CDMA2000). 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.
Interference from external mobiles (also called uplink-to-downlink interference) can be created by insufficient separation between the uplink frequency used by the external network and the downlink frequency used by your WiMAX
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 WiMAX network. This noise rise is taken
1151
into account in all downlink interference-based calculations. For more information on the Inter-technology DL noise
rise, see "Cell Properties" on page 1039.
Interference received by cells on the uplink: Interference can be received by cells of a WiMAX network on the uplink
from external base stations and mobiles in the vicinity.
Interference from external base stations (also called downlink-to-downlink interference) can be created by insufficient separation between the downlink frequency used by the external network and the uplink frequency used by your
WiMAX network. Such interference may also come from co-existing TDD networks.
Interference from external mobiles (also called uplink-to-downlink interference) can 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 WiMAX network.
This noise rise is taken into account in uplink interference calculations in Monte Carlo simulations, but not in coverage
predictions. For more information on the Inter-technology UL noise rise, see "Cell Properties" on page 1039.
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 WiMAX document, which means in co-planning mode. For more information on how to
switch to co-planning mode, see "Switching to Co-planning Mode" on page 1126.
To define the inter-technology IRFs in the victim network:
1. In the Parameters explorer, expand the Radio Network Equipment folder, right-click Inter-technology Interference
Reduction Factors, and select Open Table. The Inter-technology Interference Reduction Factors table appears.
2. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter:
1152
AT332_UMR_E0
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.
You can link more than one Atoll document with your main document following the procedure described in "Switching to Coplanning Mode" on page 1126. 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 Atoll will calculate interference from all the
external base stations in all the linked documents.
Calls/hour = 1
Duration (sec.) = 3600
Calls/hour = 1
UL volume (KBytes) = Service uplink average requested throughput x 3600/8
DL volume (KBytes) = Service downlink average requested throughput x 3600/8
The above settings will set the user activity probabilities to 100 %. If you create a traffic map based on environment classes,
the user density values that you define in your environment classes will be the actual user densities. This means that, for
X users/km defined in the environment class for a given user profile, the Monte Carlo simulator will generate exactly X users/
km for each service of the user profile.
In this way, you can know beforehand the exact number of active users, and their services, generated during the simulations.
This procedure should only be used when appropriate traffic data is not available.
1153
N Total
Where RS is the receiver sensitivity in dBm, NF is the noise figure of the receiver in dB, n is the sampling factor, BW is the channel bandwidth in MHz, N Used is the number of used subcarriers, N Total is the total number of subcarriers, R is the number of
retransmissions, and L Imp is the implementation loss in dB. If you do not know the values for R and L Imp , you can ignore the
corresponding terms and simplify the equation.
Here the term receiver refers to the base station in uplink and to the mobile/user equipment in the downlink.
1154
AT332_UMR_E0
bps Hz
Where BLER is the Block Error Rate, r is the coding rate for the bearer, and M is the number of modulation states. For simplification, we set BLER = 0, and use QPSK1/2, i.e., four modulation states and r = 0.5. With these values, we get a spectral efficiency of 1 bps/Hz for QPSK1/2. In other words, a communication channel using QPSK1/2 modulation and coding scheme can
send 1 bps of useful data per unit bandwidth.
In order to compare the bearer efficiency and spectral efficiency of QPSK1/2, lets say that QPSK1/2 has a bearer efficiency of
1 bits/symbol. Here as well, the number of bits refers to useful data bits. The width of a subcarrier in WiMAX is
1
F = 10,94 kHz , from which we can calculate the useful symbol duration as well: T U = ------- = 91,4 sec . In one second,
F
there can be 1 sec 91,4 sec = 10940 symbol durations. If 10940 symbols are transmitted using QPSK1/2, this gives us
a throughput of 10940 Symbols/sec 1 bits/Symbol = 10940 bps , which is the throughput achievable using one subcarrier
of 10.94 kHz. We can find the spectral efficiency by normalizing the throughput to unit bandwidth. This gives:
10940 bps/subcarrier 10,94 kHz/subcarrier = 1 bps/Hz
In order to compare equivalent quantities, we have ignored the system parameters such as the cyclic prefix, TTG, RTG, and
have considered that the entire frame is transmitted in one direction, uplink or downlink.
TL
DL
All Cells
DL:UL ratio = -----------------------------------------------------------------DL
UL
TL +
TL
All Cells
All Cells
You can then set this value of DL:UL ratio in the Global Parameters tab of the Radio Network Settings folders properties
dialog box, for optimising your network resource usage.
Open the Frame Configurations table as explained in "Defining Frame Configurations" on page 1138.
1155
ii. Verify that the Segmentation support (DL) check box is not selected for FFT Size 512.
iii. Double-click the frame configuration FFT Size 512.
iv. Click the Permutation Zones tab.
v. Activate the permutation zones 0 (PUSC DL) and 8 (PUSC UL).
vi. Click OK.
vii. Close the Frame Configurations tables.
b. Set up the cells:
i.
Right-click the Transmitters folder and select Cells > Open Table from the context menu. The Cells table appears.
Channel number: 0
Frame configuration: FFT Size 512
Figure 14.41: Downlink Traffic C/(I+N) Coverage Prediction - PUSC Without Segmentation
Figure 14.42: Downlink Channel Throughput Coverage Prediction - PUSC Without Segmentation
1156
AT332_UMR_E0
2. With a segmented PUSC permutation zone, which means a frequency reuse plan of N=3.
a. Set up the frame configuration:
i.
Open the Frame Configurations table as explained in "Defining Frame Configurations" on page 1138.
ii. Select the Segmentation support (DL) check box for FFT Size 512.
iii. Double-click the frame configuration FFT Size 512.
iv. Click the Permutation Zones tab.
v. Activate the permutation zones 0 (PUSC DL) and 8 (PUSC UL).
vi. Click OK.
vii. Close the Frame Configurations tables.
b. Set up the cells:
i.
Right-click the Transmitters folder and select Cells > Open Table from the context menu. The Cells table appears.
Channel number: 0
Frame configuration: FFT Size 512
Preamble index: 0 for the 1st sector, 32 for the 2nd sector, and 64 for the 3rd sector of each 3-sector site.
Segmentation usage (DL) (%): 100%
Figure 14.43: Downlink Traffic C/(I+N) Coverage Prediction - PUSC With Segmentation
1157
Figure 14.44: Downlink Channel Throughput Coverage Prediction - PUSC With Segmentation
3. With a segmented PUSC permutation zone and one or more non-segmented zones, which means a frequency reuse
plan of pseudo-N=3.
a. Set up the frame configuration:
i.
Open the Frame Configurations table as explained in "Defining Frame Configurations" on page 1138.
ii. Select the Segmentation support (DL) check box for FFT Size 512.
iii. Double-click the frame configuration FFT Size 512. The Permutation Zones table appears.
iv. Activate the permutation zones 0 (PUSC DL), 2 (FUSC) and 8 (PUSC UL).
v. Click OK.
vi. Close the Frame Configurations tables.
b. Set up the cells:
i.
Right-click the Transmitters folder and select Cells > Open Table from the context menu. The Cells table appears.
Channel Number: 0
Frame Configuration: FFT Size 512
Preamble Index: 0 for the 1st sector, 32 for the 2nd sector, and 64 for the 3rd sector of each 3-sector site.
Create or import a traffic map, as explained in "Working with Traffic Maps" on page 256, to be used as input
to the Monte Carlo simulator.
ii. Create a Monte Carlo simulation as explained in "Creating Simulations" on page 266.
iii. Open the simulation results, and commit the results to the Cells table as explained in "Updating Cell Values
With Simulation Results" on page 272.
d. Create a coverage by downlink traffic C/(I+N) level and a coverage by downlink channel throughput as explained
in "Studying Interference and C/(I+N) Levels" on page 1065 and "Making a Coverage Prediction by Throughput" on
page 1068, respectively.
In this case, the 5 MHz channel is divided into 3 segments. Each segment is allocated to one of the three sectors of
each 3-sector site. There is no interference between segments because the preamble indexes give a different segment
and same cell permbase (IDCell in IEEE specifications). Each segment uses 1/3rd of the total number of used subcarriers, i.e., 140. However, there is also a non-segmented FUSC permutation zone, which uses the entire channel width
of 5 MHz. The sectors receive co-channel interference during the FUSC part of the frame but not during the segmented
PUSC part of the frame. The traffic C/(I+N) and throughput coverage predictions would be as shown in Figure 14.45
and Figure 14.46.
1158
AT332_UMR_E0
Figure 14.45: Downlink Traffic C/(I+N) Coverage Prediction - Segmented PUSC + FUSC
Figure 14.46: Downlink Channel Throughput Coverage Prediction - Segmented PUSC + FUSC
If you compare the traffic C/(I+N) and throughput coverage predictions in the above cases, you will observe that the traffic C/
(I+N) improves with segmentation, but the throughput is reduced.
b. Set the Target throughput for voice services to "2 - Application throughput" for the scheduler being used.
1159
In this way, Atoll will allocate resources to the users of this service such that they get 64 kbps application throughput,
and around 85.6 kbps of effective MAC throughput.
b. Set the Target throughput for voice services to "2 - Application throughput" for the scheduler being used.
In this way, Atoll will allocate resources to the users of this service such that they get 8 kbps application throughput,
and around 29.6 kbps of effective MAC throughput.
Type
Name
Number of Bins in 1
Subchannel
Number of
Subcarriers in 1
Subchannel
Length (Number of
Symbol Durations)
Total Number of
Modulation Symbols in
One Slot
1
2
3
4
6 x 1 (Default)
3x2
2x3
1x6
6
3
2
1
6 x 9 = 54
3 x 9 = 27
2 x 9 = 18
1x9=9
1
2
3
6
54 x 1 = 54
27 x 2 = 54
18 x 3 = 54
9 x 6 = 54
As the above table shows, each type of AMC subchannels has a different number of bins. However, the duration of an AMC
slot varies corresponding to the number of bins in the subchannel in order to maintain the number of modulation symbols in
one slot constant.
In the first type (6 x 1; default in Atoll), a slot consists of a subchannel of 6 consecutive bins (54 subcarriers) over 1 symbol
duration. A slot of the second type (3 x 2) consists of a subchannel of 3 consecutive bins (27 subcarriers) over 2 symbol durations. A slot of the third type (2 x 3) consists of a subchannel of 2 consecutive bins (18 subcarriers) over 3 symbol durations.
And, a slot of the fourth type (1 x 6) consists of a subchannel of 1 bin (9 subcarriers) over 6 symbol durations. In all the cases,
a slot comprises 54 modulation symbols.
1160
AT332_UMR_E0
The values of the numbers of subchannels per channel in the frame configurations available by default in Atoll represent the
first (default) type of AMC subchannels. The number of subchannels per channel is calculated by dividing the total number of
subcarriers in the channel by the number of subcarriers in one subchannel. Therefore, for modelling any other type of AMC
subchannels, you will have to increase the number of subchannels per channel accordingly, i.e., multiply the current value by
2, 3, or 6, for modelling the second, third, or fourth type, respectively.
User: A general term that can also designate a subscriber, mobile, and receiver.
Mobile: Users generated and distributed during simulations. These users have, among other parameters, defined services, terminal types, and mobility types assigned for the duration of the simulations.
Receiver: A probe mobile, with the minimum required parameters needed for the calculation of path loss, used for
propagation loss and raster coverage predictions.
Radio Bearer: A Modulation and Coding Scheme (MCS) used to carry data over the channel.
Peak MAC Throughput: The maximum MAC layer throughput (user or channel) that can be achieved at a given location using the highest WiMAX bearer available. This throughput is the raw throughput without considering the effects
of retransmission due to errors and higher layer coding and encryption.
Effective MAC Throughput: The net MAC layer throughput (user or channel) that can be achieved at a given location
using the highest WiMAX bearer available computed taking into account the reduction of throughput due to retransmission due to errors.
Application Throughput: The application layer throughput (user or channel) that can be achieved at a given location
using the highest WiMAX bearer available computed taking into account the reduction of throughput due to PDU/SDU
header information, padding, encryption, coding, and other types of overhead.
Channel Throughputs: Peak MAC, effective MAC or application throughputs achieved at a given location using the
highest WiMAX bearer available with the entire cell resources (uplink or downlink).
Allocated Bandwidth Throughputs: Uplink peak MAC, effective MAC or application throughputs achieved at a given
location using the best possible WiMAX bearer with the number of subchannels calculated after subchannelisation.
User Throughputs: Peak MAC, effective MAC or application throughputs achieved at a given location using the highest
WiMAX bearer available with the amount of resources allocated to a user by the scheduler.
Traffic Loads: The uplink and downlink traffic loads are the percentages of the uplink and the downlink subframes in
use (allocated) to the traffic (mobiles) in the uplink and in the downlink, respectively.
Resources: In Atoll, the term "resource" is used to refer to the average number of slots, expressed in percentage (as
traffic loads, when the average is performed over a considerably long duration) of the total number of slots in a superframe of 1 sec.
1161
Uplink Noise Rise: Uplink noise rise is a measure of uplink interference with respect to the uplink noise:
I UL + N UL
NR UL = ------------------------ , or NR UL = 10 Log I UL + N UL 10 Log N UL in dB. This parameter is one of the two
N UL
methods in which uplink interference can be expressed with respect to the noise. The other parameter often used
I
I UL + N UL
UL
instead of the uplink noise rise is the uplink load factor: L UL = ------------------------ . Usually, the uplink load factor is kept as a
linear value (in percentage) while the uplink noise rise is expressed in dB. The two parameters express exactly the
same information, and can be inter-converted as follows:
I
I+NN
I
I+N
N
I
N
N
I
I+N
1
------------ = ---------------------- => ------------ = ------------ ------------ => ------------ = 1 ------------ => ------------ = 1 ------------ => ------------ = --------------------I
I+N
I+N
I+N
I+N I+N
I+N
I+N
I+N
I+N
N
1 -----------I+N
1
=> NR = -----------
1L
The following table shows the relation between interference, load factor, and noise rise.
Interference (I)
0
=N
=9xN
= 99 x N
Noise Rise
1
2
10
100
The reason why uplink interference is expressed in terms of noise rise (in dB) in Atoll instead of load factor (in percentage) is that the load factor varies exponentially with the increase in interference.
Symbol: A symbol is the modulation symbol, corresponding to one frequency unit (subcarrier) over one time unit
(symbol duration or OFDM symbol).
Symbol Duration (SD): The symbol duration is the length of each symbol in the frame. The length of a frame, i.e., the
frame duration, can be expressed in terms of the number of symbol durations in the frame. It is referred to as OFDM
symbol in the IEEE 802.16 specifications.
Subchannels: A subchannel is a group of subcarriers. A channel can be divided into a number of subchannels. You can
set the number of these subchannels at the network level in Atoll.
Subcarriers (or tone): A channel contains a number of subcarriers including the upper and lower guard bands, the pilot
subcarriers, and the data subcarriers. The guards, pilots, and the DC subcarrier can not be used for data transfer. The
total thermal noise over the entire channel bandwidth is calculated according to the number of used subcarriers out
of the total number of subcarriers. The used subcarriers are the data and the pilot subcarriers. The data transfer
capacity of a channel is calculated by considering the data subcarriers only.
Frame Configuration: A frame configuration is the description of a frame in the frequency as well as in the time dimension. In the frequency domain, it defines how many subcarriers exist in the channel width used, and how many of these
subcarriers are used and for which purpose, i.e., pilot, data, DC, guard. In the time domain, it defines how long the
frame is, and its composition.
The frame configuration depends on the channel width because the system uses Scalable OFDMA. The IEEE specifications define different frame configurations for different channel widths. For example, a cell using a 10 MHz channel
width will have 1024 subcarriers, but one using a 5 MHz channel will have 512. As well, in the time domain, the
number of active permutation zones in the frame and the subchannel allocation modes of these zones depend on the
operator and the equipment used. You can create or modify frame configurations and their corresponding permutation zones in Atoll as explained in "Defining Frame Configurations" on page 1138.
1162
Permutation Zone: A permutation zone is a subdivision of a WiMAX frame in the time domain. According to the IEEE
specifications, there can be as many as 8 permutation zones in the downlink and 3 in the uplink. Each permutation
zone can use a different subchannel allocation mode (or a permutation scheme), and can have different numbers of
used, pilot, and data subcarriers. The different subchannel allocation modes are: PUSC, FUSC, OFUSC, AMC, TUSC1,
and TUSC2 in downlink, and PUSC, OPUSC, and AMC in uplink.
Segmentation: The PUSC subchannel allocation mode allows the allocation of groups of subchannels to cells.
According to the IEEE specifications, there are 6 subchannel groups in the downlink PUSC subchannel allocation mode.
You can, for example, use 2 subchannel groups at each sector of a 3-sector site, and completely eliminate interference
between these sectors by correctly planning the preamble indexes. On one hand, segmentation improves the CINR by
allowing you to different segments of the same channel at different sectors, but on the other hand, it reduces the
available cell capacity (throughput) because the channel width used at each sector is reduced. For examples on how
to use segmentation in Atoll, see "Working With Frame Configurations, Permutation Zones, and Downlink Segmentation: Examples" on page 1154.
Primary and Secondary Subchannel Groups (PUSC DL): The primary subchannel groups (0, 2, and 4) and secondary
subchannel groups (1, 3, and 5) are mapped to subchannel numbers as follows:
AT332_UMR_E0
Total Number of
Subcarriers
Total Number of
Subcarriers
0-5
N/A
6-9
10-15
128
1024
3
N/A
16-19
20-25
N/A
26-29
0-4
0-11
N/A
12-19
5-9
20-31
512
2048
3
N/A
32-39
10-14
40-51
N/A
52-59
1163
1164
Chapter 15
Wi-Fi Networks
This chapter provides
information on using Atoll to
design, analyse, and
optimise a Wi-Fi network.
1164
AT332_UMR_E0
15 Wi-Fi Networks
Wi-Fi refers to a group of WLAN (Wireless Local Area Network) standards from the IEEE. The WLAN air interface is described
in the IEEE 802.11 standards family. Atoll enables you to design OFDM-based IEEE 802.11 networks using various technologies
and operating frequencies for WLAN, including:
802.11a
802.11g
802.11n
802.11pa
802.11adb
802.11ac
Released
1999
2003
Rev. 2007
2009
2010
2012
2012
Technology
OFDM
OFDM
OFDM
OFDM
OFDM
2.4
2.4, 5
60
20
20
20, 40
10
2160
Modulations
a.
b.
c.
+ 256QAM
MIMO Capabilities
4x4 (Maximum)
8x8 (Maximum)
54
54
27
6756 (OFDM)
4620 (SC)
2503 (LPSC
Also known as DSRC (Dedicated Short Range Communication) or WAVE (Wireless Access in Vehicular Environments)
Also known as directional multi-gigabit
Guard Interval
Atoll can predict radio coverage, evaluate network capacity, and analyse the amount of mobile traffic that can be offloaded
from a mobile network to a Wi-Fi network.
Atoll uses Monte Carlo simulations to generate and analyse realistic network scenarios (snapshots) by carrying out scheduling
and resource allocation. Realistic user distributions can be generated using different types of traffic maps. You can create
coverage predictions to analyse received signal levels, signal quality, service areas, and throughputs in downlink and in uplink.
Mobile (LTE, CDMA2000, UMTS, LTE, etc.) and Wi-Fi networks can be planned in the same Atoll session. New mobile access
technologies, such as HSPA, HSPA+, and LTE, have triggered a significant increase in data traffic. Mobile operators are looking
for viable solutions for delivering high speed data access with satisfactory QoS. Among many available options, Wi-Fi provides
operators with a feasible approach for mobile network traffic offloading due to the following factors:
Atoll Wi-Fi provides comprehensive Wi-Fi modelling with advanced traffic offload analysis features that enable operators to
assess different traffic offloading options and make the right decision for their network.
You can open an existing Atoll document by selecting File > Open.
You can create an Atoll document as explained in Chapter 1: Working Environment.
You can also add access points using a station template (see "Placing a New Access Point Using a Station Template"
on page 1171).
3. Carry out basic coverage predictions. See "Signal Level Coverage Predictions" on page 1179.
1165
You can generate realistic cell load conditions by creating a simulation based on traffic maps (see "Studying Wi-Fi
Network Capacity" on page 1207).
You can define cell load conditions manually either on the Cells tab of each transmitter Properties dialog box or
in the Cells table (see "Creating or Modifying a Cell" on page 1171).
7. Make Wi-Fi-specific signal quality coverage predictions using the defined cell load conditions. See "Wi-Fi Coverage
Predictions" on page 1182.
8. If necessary, modify network parameters to study the network.
1166
Name: A default name is proposed 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 .
AT332_UMR_E0
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 dialog box afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 57.
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.
Backhaul Tab
Backhaul throughputs: You can specify the maximum backhaul throughputs supported in downlink and uplink by the
site. Enter the capacity of the backhaul links between sites and serving gateways. The maximum backhaul throughputs
that you enter here are taken into account as backhaul constraints in Monte Carlo simulations.
Name: By default, the transmitter is named after the site it is on, suffixed with an underscore and a number.
You can enter a name for the transmitter. However, it is better to use the name assigned
by Atoll to ensure consistency. 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. For information on the site Properties dialog box, see "Site
Properties" on page 1166. You can click the New button to create a site for the transmitter.
Shared antenna: This field identifies the transmitters located at the same site or on sites with the same position and
that share the same antenna. The entry in the field must be the same for all transmitters sharing the same antenna.
When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna,
Atoll automatically synchronises the same changes to all other transmitters defined as having a shared antenna. This
field is also used for dual-band transmitters to synchronise antenna parameters for different frequency bands.
Under Antenna position, you can modify the position of the antennas (main and secondary):
Relative to site: Select Relative to site to enter the antenna positions as offsets from the site location, and 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.
Transmitter Tab
Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are displayed with
a specific icon in the Transmitters folder of the Network explorer.
Only active transmitters are taken into consideration during calculations.
Transmitter type: Specify whether the transmitter is to be considered as a server. This enables you to model the coexistence of different networks in the same geographic area.
If the transmitter is to be considered as a potential server as well as an interferer, set the transmitter type to Intranetwork (Server and interferer).
If the transmitter is to be considered only as an interferer, set the type to Inter-network (Interferer only). Interferer-only transmitters are ignored by coverage calculations and do not serve any mobile in Monte Carlo simulations.
For more information on how to study interference between co-existing networks, see "Modelling the Co-existence
of Networks" on page 1244.
Transmission/Reception: This area displays the total losses and the noise figure of the transmitter.
1167
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 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.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on page 159
Mechanical Azimuth, Mechanical Downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt display additional antenna parameters.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
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.
Number of MIMO antennas: Enter the number of antennas used for MIMO in the Transmission and Reception
fields. For more information on how the number of MIMO antennas are used, see "Multiple Input Multiple Output
(MIMO) Systems" on page 1240.
Cells Tab
When you create a transmitter, Atoll automatically creates a cell for the transmitter using the properties of the currently
selected station template.
The Cells tab enables you to configure the properties for every cell of a transmitter. For more information on the properties
of a cell, see "Cell Properties" on page 1168.
Propagation Tab
Transmitters are taken into account during calculations. Therefore, you must set the propagation parameters. On the Propagation tab, you can modify the Propagation model, Radius, and Resolution for both the Main matrix and the Extended
matrix. For information on propagation models, see "Assigning Propagation Parameters" on page 187.
Display Tab
On the Display tab, you can modify how a transmitter will be displayed. For information on changing display properties, see
"Setting the Display Properties of Objects" on page 51.
1168
Name: By default, Atoll names the cell after its transmitter, adding a suffix in parentheses. If you change transmitter
name, 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 Administrator Manual.
Active: If this cell is to be active, you must select the Active check box.
Order: The display order of a cell within the transmitter. This value is used to determine the order in which information
related to a cell will be displayed in the Network explorer and on the map. This field is automatically filled by Atoll but
you can change these default values to display cells in a user-defined order.
AT332_UMR_E0
The consistency between values stored in this field is verified by Atoll. However, inconsistencies may arise when tools other than Atoll modify the database. You can check for inconsistencies in the cell display order and fix them by selecting Data Audit > Cell Display Order
Check in the Document menu.
Channel allocation status: The status of the channel allocated to the cell:
Not allocated: The AFP considers a Not allocated channel modifiable without cost.
Allocated: The AFP considers an Allocated channel modifiable but only if absolutely necessary.
Locked: The AFP considers a Locked channel not modifiable.
For more information on the AFP, see "Configuring Network Parameters Using the AFP" on page 1200.
Reuse distance: The reuse distance after which the channel assigned to this cell can be assigned to another cell by the
AFP.
Power (dBm): The cell transmission power over the frame.
Min C/N (dB): The minimum C/N required for a user to be connected to the cell. Calculated C/N is compared with this
threshold to determine whether or not a user can be connected to a cell.
Frame configuration: The frame configuration used by the cell. For more information on frame configurations, see
"Defining Frame Configurations" on page 1237.
Reception equipment: You can select the cell reception equipment from the reception equipment list. For more information, see "Defining Wi-Fi Reception Equipment" on page 1238.
Traffic load (DL) (%): The downlink traffic load percentage. This can be user-defined or an output of Monte Carlo simulations.
Traffic load (UL) (%): The uplink traffic load percentage. This can be user-defined or an output of Monte Carlo simulations.
UL noise rise (dB): The uplink noise rise in dB. This can be user-defined or an output of Monte Carlo simulations. This
is the global value of uplink noise rise including the inter-technology uplink noise rise.
Max traffic load (DL) (%): The downlink traffic load not to be exceeded. This limit can be taken into account during
Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have a downlink
traffic load greater than this maximum.
Max traffic load (UL) (%): The uplink traffic load not to be exceeded. This limit can be taken into account during Monte
Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have an uplink traffic
load greater than this maximum.
Additional UL noise rise: This noise rise represents the interference created by the mobiles and access points of an
external network on this cell on the uplink. This noise rise will be taken into account in all uplink interference-based
calculations involving this cell in Monte Carlo simulations. It is not used in predictions where Atoll calculates the uplink
total interference from the uplink noise rise which includes inter-technology uplink interference. For more information on inter-technology interference, see "Modelling Inter-technology Interference" on page 1242.
Additional DL noise rise: This noise rise represents the interference created by the 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 interferencebased calculations involving this cell. For more information on inter-technology interference, see "Modelling Intertechnology Interference" on page 1242.
AMS & MU-MIMO threshold (dB): For AMS, the C/N threshold for switching from SU-MIMO to STTD/MRC as the radio
conditions get worse than the given value. For MU-MIMO, it is the minimum required preamble CNR for using
MU-MIMO. For more information on Adaptive MIMO switching, see "Multiple Input Multiple Output (MIMO) Systems" on page 1240.
MU-MIMO capacity gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO. This can be userdefined or an output of Monte Carlo simulations. In uplink throughput coverage predictions, the cell capacity will be
multiplied by this gain on pixels where MU-MIMO is used.
Number of users (DL): The number of users connected to the cell in the downlink. This can be user-defined or an
output of Monte Carlo simulations.
Number of users (UL): The number of users connected to the cell in the uplink. This can be user-defined or an output
of Monte Carlo simulations.
Max number of users: The maximum number of simultaneous users supported by the cell.
Max number of intra-technology neighbours: The maximum number of Wi-Fi neighbours that the cell can have.
Max number of inter-technology neighbours: The maximum number of other technology neighbours that the cell can
have.
1169
Neighbours: You can access a dialog box in which you can set both intra-technology and inter-technology neighbours
by clicking the Browse button. For information on defining neighbours, see "Neighbour Planning" on page 223.
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.
1170
AT332_UMR_E0
To create a transmitter, right-click the Transmitters folder, and select New from the context menu.
To modify an existing transmitter, expand the Transmitters folder, right-click the transmitter that you want to
modify, and select Properties from the context menu.
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 in the Network explorer and selecting Open Table
from the context menu. For information on copying and pasting data, see "Copying
and Pasting in Tables" on page 83.
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.
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 in the Network explorer 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 83),
or import data into the table (see "Importing Tables from Text Files" on page 88).
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.
1171
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 access point.
To place the access point 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 60.
If you let the pointer rest over the access point you have placed, Atoll displays its
tip text with its exact coordinates, allowing you to verify that the location is correct.
3. Move the pointer to the site on the map. When the frame appears around the site, indicating it is selected, click to
place the access point.
15.2.2.7.1
The Name of the station template, the number of Sectors, each with a transmitter, the Hexagon radius, which is the
theoretical radius of the hexagonal area covered by each sector, and the Transmitter type, which defines whether the
transmitter belongs to the current network or to another network.
Under Antennas, you can modify the following:
1st sector mechanical azimuth, from which the azimuth of the other sectors are offset to offer complete coverage
of the area, the Height/ground of the antennas from the ground (which is the height over the DTM; if the transmitter is situated on a building, the height entered must include the height of the building), and the Mechanical
downtilt for the antennas.
Electrical Azimuth, Electrical Downtilt, and Additional electrical downtilt display additional antenna parameters.
1172
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
AT332_UMR_E0
Under Main antenna, you can select the main antenna Model.
Under Number of MIMO Antennas, you can enter the number of antennas used for Transmission and for Reception for MIMO.
Under Path loss matrices, you can modify the following: the Main propagation model, the Main radius, and the Main
resolution, and the Extended propagation model, the Extended radius, and the Extended resolution. For information
on propagation models, see Chapter 4: Radio Calculations and Models.
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.
Transmitter Tab
Active: Select this option to specify whether the transmitter is active. Only active transmitters are taken into consideration during calculations.
Transmission/Reception: This area displays the total losses and the noise figure of the transmitter. Losses and noise
are calculated according to the characteristics of the equipment assigned to the transmitter.
Cell Tab
Power: Modify the cell transmission power over the frame (in dBm).
Cell definition per sector: Assign a channel per cell per sector by clicking the Cell definition per sector button. The Cell
Definition per Sector dialog box appears.
Sector: Select the sector for which you want to define cell parameters, that is to say the channel number.
Number of cells: Enter the number of cells that the selected sector will have. The number of rows in the grid below
depends on the number of cells that you enter.
Frequency band, Reception equipment, Frame configuration, Max number of users, Reuse distance, Min C/N, and
the AMS threshold.
Default loads: Enter the default values for DL traffic load, UL traffic load, UL noise rise, Max DL traffic load, and Max
UL traffic load.
Additional interference: Set the DL noise rise and the UL noise rise. For more information on inter-technology interference, see "Modelling Inter-technology Interference" on page 1242.
Neighbours Tab
Max number of neighbours: Set the maximum numbers of Intra-technology and Inter-technology neighbours.
Other Properties Tab
The Other Properties tab only appears if you have defined additional fields in the Sites table, or if you have defined
an additional field in the Station Template Properties dialog box.
15.2.2.7.2
15.2.2.7.3
1173
15.2.2.7.4
15.2.2.7.5
15.2.2.7.6
Quickly create an access point with the same settings as an original one in order to study the effect of a new access
point on the coverage and capacity of the network, and
Quickly create an homogeneous network with access points that have the same characteristics.
If you want to duplicate the access point without the intra and inter-technology neighbours of its transmitters,
select Duplicate > Without Neighbours.
If you want to duplicate the access point along with the lists of intra and inter-technology neighbours of its transmitters, select Duplicate > With Outward Neighbours.
2. Place the new access point on the map using the mouse:
1174
To create a duplicate access point and site, move the pointer over the map to where you would like to place the
duplicate. The exact coordinates of the pointers current location are visible in the Status bar.
To place the duplicate access point on an existing site, move the pointer over the existing site where you would
like to place the duplicate. When the pointer is over the site, the site is automatically selected. The exact coordinates of the pointers current location are visible in the Status bar.
AT332_UMR_E0
To place the access point 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 60.
If you let the pointer rest over the access point you have placed, Atoll displays tip
text with its exact coordinates, allowing you to verify that the location is correct.
) in the Radio Planning toolbar. The Point Analysis window opens and the pointer
changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and the
receiver. You can move the receiver on the map (see "Moving the Receiver on the Map" on page 203).
3. Select the Profile view. The Profile view displays the profile between the transmitter and the receiver with clutter
heights.
You can select a different transmitter.
Displays data,
including
received signal,
shadowing
margin, cell
edge coverage
probability,
propagation
model used,
and transmitter-receiver
distance.
Fresnel ellipsoid
Line of sight
1175
intersects the Fresnel ellipsoid the most. Propagation models that use a 3 knife-edge Deygout diffraction method may
also display two additional diffraction edges. The total attenuation is displayed above the main diffraction edge.
The results of the analysis are displayed at the top of the Profile view:
The received signal strength from the selected transmitter for the cell with the highest reference signal power
The propagation model used
The shadowing margin and the indoor loss (if selected)
The distance between the transmitter and the receiver.
4. If needed, select an other transmitter from the list. You can click the Properties button (
properties.
5. Click the Options button (
) to display the Calculation Options dialog box and change the following:
Change the X and Y coordinates to change the current position of the receiver.
Select the Shadowing taken into account check box and enter a Cell edge coverage probability. For more information, see "Taking Shadowing into Account in Point Analyses" on page 204.
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. Indoor losses are defined per frequency per
clutter class. For more information, see "Taking Indoor Losses into Account" on page 203.
6. In the Profile view toolbar, you can use the following tools:
) to view the geographic profile between the transmitter and the receiver.
) again to view the radio signal path between the transmitter and the
Click the Detailed Report button ( ) to display a text document with details on the displayed profile analysis.
The detailed report is only available for the Standard Propagation Model.
Click the Copy button (
) to copy the content of the view and paste it as a graphic into a graphic editing or wordprocessing programme.
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 access
points 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.
The table you copy 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 83.
1176
Importing data: If you have access point 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
AT332_UMR_E0
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 access points 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 and Spreadsheets" on page 86. For information on importing table data, see "Importing Tables from Text Files" on page 88.
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 in the label will make it harder to distinguish the information you are looking for. For
information on defining the label, see "Associating a Label to an Object" on page 53.
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 "Associating a Tip Text to an Object" on page 54.
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 transmitters. 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 "Setting the Display Type" on page 52.
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 (
same site with the same azimuth, you can differentiate them by selecting different symbols for each (
For information on defining the transmitter symbol, see "Setting the Display Type" on page 52.
and
).
1177
Display Resolution
City Centre
5m
City
20 m
County
50 m
State
100 m
Country
A read-only Unique ID is generated when you create a coverage prediction. This ID can
later be found between the <GUID> and </GUID> tags in the following files:
1178
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
Receiver height: This parameter displays the height of the receiver defined in the Calculation Parameters tab of the
Network Settings Properties dialog box.
Comments: Specify an optional description of comment for the prediction.
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 99. The Group By and Sort buttons are not available when making a so-called
"global" coverage prediction (e.g., signal level coverage prediction).
AT332_UMR_E0
If you create a coverage prediction from the context menu of the Predictions folder, you
can select the sites using the Group By, Sort, and Filter buttons under Display configuration. However, if you create a coverage prediction from the context menu of the Transmitters folder, only the Filter button is available, because, by creating a coverage prediction
directly from the Transmitters folder, you have effectively already selected the target
sites.
Conditions Tab
The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each
pixel.
At the top of the Conditions tab, you can set the range to be considered for the current prediction.
Server: Select one of the following:
Shadowing taken into account: Select this option to consider shadowing in the prediction. When you select this
option, you can change the Cell edge coverage probability.
Indoor coverage: Select this option to consider indoor losses. Indoor losses are defined per frequency per clutter class.
Channel: Select a channel or carry out the prediction for the "Best" channel of a frequency band or of all frequency
bands. For any transmitter, the best channel is the one whose cell has the highest power.
Display Tab
On the Display tab, you can modify how the results of the coverage prediction will be displayed.
1179
15.2.7.2.1
2. Specify the propagation parameters as explained in "Assigning Propagation Parameters" on page 187.
3. 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 dialog box appears.
The Prediction Types dialog box lists the coverage prediction types available. They are divided into Standard Predictions, supplied with Atoll, and Customised Predictions. Unless you have already created some customised predictions, the Customised Predictions list will be empty.
4. Select Coverage by Signal Level (DL) and click OK. A coverage prediction properties dialog box appears.
5. Configure the parameters in the Properties dialog box as described in "Wi-Fi Prediction Properties" on page 1178.
6. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
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 in the Network explorer. 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 (
15.2.7.2.2
).
1180
AT332_UMR_E0
4. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
15.2.7.2.3
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window
15.2.7.2.4
4. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
1181
15.2.7.3.1
Highest bearer
Lowest bearer
Throughput scaling factor
Throughput offset
Body loss
You can create a service or modify an existing service by specifying the following parameters in the General tab of the service
Properties dialog box (some fields depend on the type of service you choose):
1182
Name: Atoll proposes a name for the new service, but you can set a more descriptive name.
Type: You can select either Voice or Data as the service type.
Priority: Enter a priority for this service. "0" is the lowest priority.
Activity factor: The uplink and downlink activity factors are used to determine the probability of activity for users
accessing the service during Monte Carlo simulations. For Voice services, this parameter is used when working with
sector traffic maps and user density traffic maps. For Data services, Atoll distributes the users according to the activity
factors when importing user density traffic maps for all activity statuses.
Highest bearer: Select the highest bearer that the service can use in the uplink and downlink. This is considered as an
upper limit during bearer determination.
Lowest bearer: Select the lowest bearer that the service can use in the uplink and downlink. This is considered as a
lower limit during bearer determination.
Max throughput demand: Enter the highest throughput that the service can demand in the uplink and downlink. This
value is not considered for services UGS as the quality of service.
Min throughput demand: Enter the minimum required throughput that the service should have in order to be available in the uplink and downlink. This value is not considered for BE services.
Average requested throughput: Enter the average requested throughput for uplink and downlink. The average
requested throughput is used in a simulation during user distribution generation in order to calculate the number of
users attempting a connection.
Application throughput: Under Application throughput, you can set a Scaling factor between the application
throughput and the MAC (Medium Access Control) throughput and a throughput Offset. These parameters model the
header information and other supplementary data that does not appear at the application level.
AT332_UMR_E0
The application throughput parameters are used in throughput coverage predictions and for application throughput
calculation.
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 3 dB.
For information on creating or modifying a service, see "Creating Services" on page 247.
Modelling Mobility Types
In Wi-Fi, information about the receiver mobility is required for determining which bearer selection threshold and quality
graph to use from the reception equipment referred to in the terminal or cell. Mobiles used at high speeds and at walking
speeds do not have the same quality characteristics. C/(I+N) requirements for different radio bearers are largely dependent
on mobile speed.
You can create or modify a mobility type by specifying the following parameters in the General tab of the mobility type Properties dialog box:
For information on creating or modifying mobility types, see "Modelling Mobility Types" on page 247.
Modelling Terminals
In Wi-Fi, 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.
You can create or modify a terminal by specifying the following parameters in the General tab of the terminal Properties
dialog box:
Model: Select an antenna model from the list of available antennas. If you do not select an antenna for the terminal, Atoll uses an isotropic antenna in calculations.
In case you do not select an antenna, Atoll uses an isotropic antenna, not an omni-directional antenna, in calculations. An isotropic antenna has spherical radiation patterns in the
horizontal as well as vertical planes.
Gain: Enter the terminal antenna gain if you have not selected an antenna model in the Model field. If you have
selected an antenna, the Gain field is disabled and shows the gain of the selected antenna.
Diversity support: Select whether the terminal support MIMO or not.
MIMO: Enter the Number of transmission antennas and the Number of reception antennas available in the terminal.
For information on creating or modifying terminals, see "Modelling Terminals" on page 249.
15.2.7.3.2
1183
Although, you can also set a value for the Traffic load (UL) (%) column as an indication of cells uplink loads, this parameter is not used in the coverage prediction calculations. The measure of interference in the uplink is given by the uplink
noise rise values. For a definition of the values, see "Cell Properties" on page 1168.
To enter the same values in one column for all cells in the table by copying the contents of
one cell into other cells, you can use the Fill Down and Fill Up commands. For more information on working with tables in Atoll, see "Data Tables" on page 75.
15.2.7.3.3
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
15.2.7.3.4
1184
AT332_UMR_E0
b. Select a Terminal, a Mobility type, and a Service. The C/(I+N) coverage prediction is a best server coverage prediction. The Noise figure defined in the terminal types properties dialog box is used in the coverage prediction to
determine the total noise in the downlink, and the Noise figure of the transmitter is used to determine the total
noise in the uplink. For more information on services, terminals, mobility types, and reception equipment, see
"Modelling Services" on page 1182, "Modelling Terminals" on page 1183, "Modelling Mobility Types" on
page 1183, and "Defining Wi-Fi Reception Equipment" on page 1238, respectively.
c. 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. The shadowing margin is based
on the C/I standard deviation.
d. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
4. Click the Display tab. From the Display type list, select "Value intervals" to display the coverage prediction by C/(I+N)
levels or total noise (I+N) levels.
For information on adjusting the display, see "Setting the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
15.2.7.3.5
1185
b. Select a Terminal, a Mobility type, and a Service. The best bearer coverage prediction is always based on the best
server. The Noise figure defined in the terminal types properties dialog box is used in the coverage prediction to
determine the total noise in the downlink, and the Noise figure of the transmitter is used to determine the total
noise in the uplink. As well, the bearer selection for each pixel according to the C(I+N) level is performed using
the bearer selection thresholds defined in the reception equipment. This reception equipment is the one defined
in the selected terminal for the downlink coverage predictions, and the one defined in the cell properties of the
serving transmitter for the uplink coverage predictions. Mobility is used to index the bearer selection threshold
graph to use.
You can make Atoll use only the bearers for which selection thresholds are defined in both
the terminals and the cells reception equipment by adding an option in the Atoll.ini file.
For more information, see the Administrator Manual.
For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services"
on page 1182, "Modelling Terminals" on page 1183, "Modelling Mobility Types" on page 1183, and "Defining WiFi Reception Equipment" on page 1238, respectively.
c. 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. The shadowing margin is based
on the C/I standard deviation.
d. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
4. Click the Display tab. From the Display type list, select display by bearer or modulation.
For information on adjusting the display, see "Setting the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
15.2.7.3.6
b. Select a Terminal, a Mobility type, and a Service. The best bearer coverage prediction is always based on the best
server. The Noise figure defined in the terminal types properties dialog box is used in the coverage prediction to
determine the total noise in the downlink, and the Noise figure of the transmitter is used to determine the total
noise in the uplink. As well, the bearer selection for each pixel according to the C(I+N) level is performed using
the bearer selection thresholds defined in the reception equipment. This reception equipment is the one defined
in the selected terminal for the downlink coverage predictions, and the one defined in the cell properties of the
serving transmitter for the uplink coverage predictions. Mobility is used to index the bearer selection threshold
graph to use.
1186
AT332_UMR_E0
You can make Atoll use only the bearers for which selection thresholds are defined in both
the terminals and the cells reception equipment by adding an option in the Atoll.ini file.
For more information, see the Administrator Manual.
For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services"
on page 1182, "Modelling Terminals" on page 1183, "Modelling Mobility Types" on page 1183, and "Defining WiFi Reception Equipment" on page 1238, respectively.
c. 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. The shadowing margin is based
on the C/I standard deviation.
d. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
4. Click the Display tab. For an effective service area prediction, the Display type "Unique" is selected by default. The
coverage prediction will display where a service is available in both downlink and uplink. For information on defining
display properties, see "Setting the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
15.2.7.3.7
b. Select a Terminal, a Mobility type, and a Service. The throughput coverage prediction is always based on the best
server. The Noise figure defined in the terminal types properties dialog box is used in the coverage prediction to
determine the total noise in the downlink, and the Noise figure of the transmitter is used to determine the total
noise in the uplink. As well, the bearer selection for each pixel according to the C(I+N) level is performed using
the bearer selection thresholds defined in the reception equipment. This reception equipment is the one defined
in the selected terminal for the downlink coverage predictions, and the one defined in the cell properties of the
serving transmitter for the uplink coverage predictions. Mobility is used to index the bearer selection threshold
graph to use. The service is used for the application throughput parameters defined in the service Properties dialog box.
You can make Atoll use only the bearers for which selection thresholds are defined in both
the terminals and the cells reception equipment by adding an option in the Atoll.ini file.
For more information, see the Administrator Manual.
1187
For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services"
on page 1182, "Modelling Terminals" on page 1183, "Modelling Mobility Types" on page 1183, and "Defining WiFi Reception Equipment" on page 1238, respectively.
c. 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. The shadowing margin is based
on the C/I standard deviation.
d. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
4. Click the Display tab. From the Display type list, select "Value intervals" to display the coverage prediction by peak
MAC, effective MAC, or application throughputs.
For information on defining display properties, see "Setting the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Atoll calculates the peak MAC channel throughputs from the information provided in the frame configuration and in the
terminal and mobility properties for the terminal and mobility selected in the coverage prediction. Atoll determines the
bearer at each pixel and multiplies the bearer efficiency by the number of symbols in the frame to determine the peak MAC
channel throughputs.
The effective MAC throughputs are the peak MAC throughputs reduced by retransmission due to errors, or the Block Error
Rate (BLER). Atoll uses the block error rate graphs of the reception equipment defined in the selected terminal for downlink
or the reception equipment of the cell of the serving transmitter for uplink.
The application throughput is the effective MAC throughput reduced by the overheads of the different layers between the
MAC and the Application layers.
The cell capacity display types let you calculate and display the throughputs available on each pixel of the coverage area taking
into account the maximum traffic load limits set for each cell. In other words, the cell capacity is equal to channel throughput
when the maximum traffic load is set to 100%, and is equal to a throughput limited by the maximum allowed traffic loads
otherwise. Cell capacities are, therefore, channel throughputs scaled down to respect the maximum traffic load limits.
The per-user throughput in downlink is calculated by dividing the downlink cell capacity by the number of downlink users of
the serving cell. In uplink, the per-user throughput is either the allocated bandwidth throughput or the uplink cell capacity
divided by the number of uplink users of the serving cell, whichever it smaller.
For more information on throughput calculation, see the Technical Reference Guide. For more information on the Global
Parameters, see "Network Settings" on page 1236.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
15.2.7.3.8
1188
AT332_UMR_E0
15.2.7.3.9
b. Select a Terminal, a Mobility type, and a Service. The quality indicator coverage prediction is always based on the
best server. The Noise figure defined in the terminal type properties dialog box is used in the coverage prediction
to determine the total noise in the downlink, and the Noise figure of the transmitter is used to determine the total
noise in the uplink. As well, the bearer selection for each pixel according to the C(I+N) level is performed using
the bearer selection thresholds defined in the reception equipment, and the quality indicator graphs from the reception equipment are used to determine the values of the selected quality indicator on each pixel. This reception
equipment is the one defined in the selected terminal for the downlink coverage predictions, and the one defined
in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used to index the
bearer selection threshold graph to use.
You can make Atoll use only the bearers for which selection thresholds are defined in both
the terminal and the cell reception equipment by adding an option in the Atoll.ini file. For
more information, see the Administrator Manual.
For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services"
on page 1182, "Modelling Terminals" on page 1183, "Modelling Mobility Types" on page 1183, and "Defining WiFi Reception Equipment" on page 1238, respectively.
c. 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. The shadowing margin is based
on the C/I standard deviation.
d. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
4. Click the Display tab. You can choose from displaying results by BER, BLER, FER, or any other quality indicator that you
might have added to the document. For more information, see "Defining Wi-Fi Quality Indicators" on page 1238. The
coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Setting the
Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
1189
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" on page 50.
Once you have completed a prediction, you can also generate reports and statistics with the tools that Atoll provides. For
more information, see "Generating Coverage Prediction Reports" on page 212 and "Displaying Coverage Prediction Statistics"
on page 214.
In this section, the following tools are explained:
15.2.7.4.1
15.2.7.4.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.
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 15.3).
15.2.7.4.3
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 91.
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 "Geographic Export Zone" on page 68.
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 210.
1190
AT332_UMR_E0
15.2.7.5.1
) on the Radio Planning toolbar. The Point Analysis window opens and the pointer
The signal levels or C/N (depending on the selection made from the Display list) from different transmitters (the
colour of the bar corresponds to the colour of the transmitter on the map).
The C/N thresholds: The empty portion of the bar indicates signal levels below the C/N thresholds.
The availability of coverage and service in downlink and uplink.
If there is at least one successful connection, double-clicking the icons in the right-hand frame opens a dialog box with
additional information about the best server:
Edit the X and Y coordinates to change the present position of the receiver.
ii. Select the Shadowing taken into account check box and enter a Cell edge coverage probability.
iii. Select the Indoor coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class.
iv. Click OK.
1191
7. 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.
8. In the Reception view toolbar, you can use the following tools:
Click Report (
) to generate a report that contains the information from the point analysis window.
Click Copy (
programme.
Click Print (
) to print the content of the view.
Click Centre on Map ( ) to centre the map window on the receiver.
) to copy the content of the view and paste it as a graphic into a graphic editing or word-processing
You can display a point analysis that uses the settings from an existing prediction by
right-clicking the prediction in the Network explorer and selecting Open Point Analysis
from the context menu.
15.2.7.5.2
Analysing Interference
In Atoll, you can study the interferers of a transmitter using the Point Analysis tool. The Interference view gives you information on interference received on any downlink channel on any point on the map. The analysis is provided for a user-definable
probe receiver which has a terminal, a mobility, and a service. The downlink and uplink load conditions can be taken from the
Cells table or from Monte Carlo simulations.
To make an interference analysis:
1. Click the Point Analysis button (
changes (
) on the Radio Planning toolbar. The Point Analysis window opens and the pointer
1192
For the best server: Name, received signal level, and C/(I+N).
For the total noise (I+N): The values of each component, i.e., I, N, and the downlink inter-technology noise rise.
For each interferer: The effective interference and the various interference reduction factors.
AT332_UMR_E0
5. Select Inter-technology interference to display interference from other technologies. The Interference bar graph displays the interference received from each inter-technology interferer. Disable Inter-technology interference to display intra-technology interference only.
6. Select the channel on which you want to study the interference from the Display list.
7. If you are analysing interferences to verify a coverage prediction, you can recreate the conditions of the coverage prediction by specifying the parameters of the study:
a. If necessary, select a layer filter for the serving cells from the Layer list.
a. Select the same Terminal, Mobility, and Service studied in the coverage prediction.
b. In the Reception view toolbar, click Options (
i.
Edit the X and Y coordinates to change the present position of the receiver.
ii. Select the Shadowing taken into account check box and enter a Cell edge coverage probability.
iii. Select the Indoor coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class.
c. Click OK.
8. 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.
9. In the Interference view toolbar, you can use the following tools:
Click the Report button ( ) to generate a report that contains the information from the Point Analysis window.
The Analysis Report dialog box opens.
) to copy the content of the view and paste it as a graphic into a graphic editing or word-
You can display a point analysis that uses the settings from an existing prediction by
right-clicking the prediction in the Network explorer and selecting Point Analysis from
the context menu.
Intersection: This display shows the area where both coverage predictions overlap (for example, pixels covered by
both predictions are displayed in red).
Merge: This display shows the area that is covered by either of the coverage predictions (for example, pixels covered
by at least one of the 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).
Value Difference: This display shows the dB difference between any two coverage predictions by signal level. This display option will not be available if the coverage predictions were calculated using different resolutions.
1193
Figure 15.7: Signal level coverage prediction of network with new access point
1194
AT332_UMR_E0
Intersection
Merge
Union
Difference
In order to see what changes adding a new access point made, it is recommended to choose Difference.
4. Click OK to create the comparison. The comparison in Figure 15.8, shows the area covered only by the new access
point.
1195
Intersection
Merge
Union
Difference
In order to see what changes modifying the antenna tilt made, choose Union. This mode displays 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, is immediately clear.
4. Click OK to create the comparison. The comparison in Figure 15.11, shows the increase in coverage due at the change
in antenna tilt.
1196
AT332_UMR_E0
15.2.7.7.1
15.2.7.7.2
Calculate: Click Calculate to save the subscriber analysis and calculate it immediately.
1197
OK: Click OK to save the subscriber analysis without calculating it. You can calculate it later by opening the subscriber analysis properties and clicking the Calculate button.
Once Atoll has finished calculating the subscriber analysis, the results are displayed in the map window. You can also access
the analysis results in a table format. For more information, see "Viewing Subscriber Analysis Results" on page 1198.
You can also organise subscriber analyses in folders under the Multi-point Analysis folder by creating folders under the Multipoint Analysis folder in the Network explorer. Folders may contain one or more subscriber analyses items. You can move
subscriber analyses items from one folder to another and rename folders.
15.2.7.7.3
1198
AT332_UMR_E0
Effective MAC channel throughput (UL) (kbps): The effective MAC channel throughput attainable using the
highest bearer available at the subscriber location in the uplink. It is calculated from the peak MAC throughput
and the BLER.
Application channel throughput (UL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
Figure 15.12: Wi-Fi handover area between reference cell and potential neighbour
When Use coverage conditions is not selected, the defined Distance is used to allocate neighbours to a reference
transmitter.
When Use coverage conditions is selected, click Define to open the Coverage Conditions dialog box:
Resolution: Enter the resolution to be used to calculate cells coverage areas during automatic neighbour allocation.
Global C/N threshold: Select this check box to set a global value for the C/N threshold. If you set a global value
here, Atoll will use this value or the C/N threshold value defined for each cell, whichever is higher. The signal level
threshold (in dBm) is calculated for each cell from its C/N threshold (in dB) considering the channel bandwidth of
the cell and using the terminal that has the highest difference between its gain and losses so that the most number
of potential neighbours can be processed.
Handover start: Enter the margin, with respect to the best server coverage area of the reference cell (cell A), from
which the handover process starts.
1199
Handover end: Enter the margin, with respect to the best server coverage area of the reference cell (cell A), at
which the handover process ends. The value entered for the Handover end must be greater than the value for the
Handover start. The higher the value entered for the Handover end, the longer the list of potential neighbours.
The area between the Handover start and the Handover end constitutes the area within which Atoll will search
for neighbours.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this option to take indoor losses into account in calculations. Indoor losses are defined
per frequency per clutter class.
Co-site cells as neighbours: When selected, the cells located on the same site as the reference cell are automatically
considered as neighbours. A cell with no antenna cannot be considered as a co-site neighbour.
Adjacent cells as neighbours (Intra-carrier Neighbours tab only): When selected, the cells that are adjacent to the reference cell are automatically considered as neighbours. A cell is considered adjacent if there is at least one pixel in the
reference cells coverage area where the potential neighbour cell is the best server, or where the potential neighbour
cell is the second best server respecting the handover end.
Symmetric relations: Select this option if you want the neighbour relations to be reciprocal, which means that any
reference transmitter/cell is a potential neighbour of all the cells that are its neighbours.
Exceptional pairs: Select this option to force the neighbour relations defined in the Intra-technology Exceptional pairs
table. For information on exceptional pairs, see "Defining Exceptional Pairs" on page 223.
Description
When
Distance
Coverage
Co-Site
Adjacent
Symmetry
Exceptional Pair
Exceptional pairs
is selected
Existing
1200
AT332_UMR_E0
Once the AFP input elements have been set up, the AFP can be used for:
Once you have completed an automatic allocation, you can analyse the results with the tools that Atoll provides:
3. Once you have created the interference matrix, you can calculate it immediately or you can save it and calculate it
later:
Calculate: Click Calculate to save the defined interference matrix and calculate it immediately.
OK: Click OK to save the defined interference matrix without calculating it. You can calculate it later clicking the
Calculate button (
Once calculated, the new interference matrix is available in the Interference Matrices folder and will be available for use the
next time you run the AFP.
You can modify the properties of an existing interference matrix by selecting Properties from the interference matrix context
menu. An existing interference matrix can be calculated again by selecting Calculate from the interference matrix context
menu.
1201
If the interference matrix file being imported contains the same interfered-interferer pair more than once, Atoll keeps the last
description of the pair.
Atoll does not perform a validity check on the imported interference file; you must therefore ensure that the imported information is consistent with the current configuration. Furthermore, Atoll only imports interference matrices for active transmitters.
To import an interference matrix:
1. In the Network explorer, right-click the Interference Matrices folder and select Import from the context menu. The
Open dialog box appears.
2. Select the file containing the interference matrix and click Open. The table Import dialog box appears.
For more information on importing table data, see "Importing Tables from Text Files" on page 88.
To export an interference matrix:
1. In the Network explorer, expand the Interference Matrices folder, right-click the interference matrix you want to
export, and select Export from the context menu. The Export dialog box appears.
For information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets" on page 86.
For information on configuring neighbour importance weighting, see "Configuring Neighbour Importance Factors" on
page 231.
For more information on calculating neighbour importance values, see "Evaluating Neighbour Importance" on
page 231.
For more details on the calculation of neighbour importance values, see the Technical Reference Guide.
1st order neighbours: The relative weight assigned to a first order neighbour relationship violation.
Interference matrices: The relative weight assigned to an interference matrix-based relationship violation.
Distance: The relative weight assigned to a distance-based relationship violation.
You can click the Reset button to set the weights to their default values.
3. Click OK.
1202
AT332_UMR_E0
The top line contains global information about the current allocation (resource being allocated and the total cost
of the current plan).
The left-hand side of the dialog box contains tabs with input parameters.
The right-hand side of the dialog box provides the allocation results.
2. From the Allocate list, select Frequencies for automatic frequency planning.
3. On the Relation Types tab, you can set the relations to take into account in automatic allocation:
Interference matrix: Select this check box if you want the AFP to take interference matrices into account for the
allocation, and select an interference matrix from the list. For Atoll to take interference matrices into account,
they must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be
calculated, imported, and edited in the Interference Matrices folder. For more information on interference
matrices, see "Working with Interference Matrices" on page 1201.
Existing neighbours: Select the Existing neighbours check box if you want the AFP to take neighbour relations into
account for the allocation. The AFP will try to allocate different frequencies to a cell and its neighbours. Atoll can
only take neighbour relations into account if neighbours have already been allocated. For information on allocating neighbours, see "Neighbour Planning" on page 223.
Reuse distance: Select this check box if you want the AFP to take relations based on distance into account for the
allocation. You can enter a Default reuse distance within which two cells must not have the same channel
assigned. However, it is highly recommended to define a reuse distance for each individual cell depending on the
size of the cells coverage area and the network density around the cell. If defined, a cell-specific reuse distance is
used instead of the default value entered here.
4. On the right-hand side of the Automatic Resource Allocation dialog box, Atoll displays the Total cost of the current
frequency allocation. Click Update to calculate the total cost take into account the parameters set in step 3.
You can click the Weights button to open the Weights dialog box and modify the cost
component weights. For more information, see "Configuring Cost Component Weights" on
page 1202.
5. Click Start. Atoll begins the process of allocating frequencies. Any messages generated by the AFP during automatic
allocation are reported on the Events tab.
While Atoll allocates frequencies, you can:
Once Atoll has finished allocating frequencies, or if you pause the automatic allocation, the Statistics tab shows the
number of proposed changes to the allocation plan and the numbers of different relations, violations, and collisions.
1203
It also shows the numbers of violations and collisions in the current plan compared to the initial one (in brackets). The
Results tab shows the proposed allocation plan:
In order to better view the progress graph and the results table, you can expand
the right-hand side zone of the Automatic Resource Allocation dialog box by
clicking the Hide Inputs button
. You can also resize the dialog box.
You can export the contents of table grids to TXT, CSV, and XML Spreadsheet files
by right-clicking the table and selecting Export from the context menu. For more
information on exporting data tables, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
You can select the columns to display in different tabs by right-clicking the table
and selecting Display Columns from the context menu. For more information, see
"Displaying and Hiding Columns" on page 80.
6. Click Commit. The proposed frequency plan is assigned to the cells of the network.
7. Click Close to exit.
1204
AT332_UMR_E0
5. Click Search.
Transmitters whose cells use the selected frequency band and channel number are displayed in red. Transmitters with
cells using two adjacent channel numbers in the same frequency band (which means a channel higher and a channel
lower) are displayed in yellow. Transmitters with cells using a lower adjacent channel number in the same frequency
band are displayed in green. Transmitters with cells using a higher adjacent channel number in the same frequency
band are displayed in blue. All other transmitters are displayed as grey lines.
If you cleared the Adjacent channels check box, transmitters with cells using the same channel number are displayed
in red, and all others, including transmitters with adjacent channels, are displayed as grey lines.
To restore the initial transmitter colours, click the Reset display button in the Find on Map tool window.
By including the frequency band and channel number of each cell in the transmitter label,
the search results will be easier to understand. For information on defining the label, see
"Associating a Label to an Object" on page 53.
Frequency band
Channel number
5. Click
to add the parameter to the Group these fields in this order list. The selected parameter is added to the list
of parameters on which the transmitters will be grouped.
6. If you do not want the transmitters to be grouped by a certain parameter, select the parameter in the Group these
fields in this order list and click
transmitters will be grouped.
. The selected parameter is removed from the list of parameters on which the
7. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters to
be grouped:
a. Select a parameter and click
8. Click OK to save your changes and close the Group dialog box.
1205
The top line contains global information about the current allocation (resource being audited and the total cost of
the current plan).
The left-hand side of the dialog box contains tabs with input parameters.
The right-hand side of the dialog box provides the audit results.
Interference matrix: Select this option if you want the audit to take interference matrices into account, and select
an interference matrix from the list. For Atoll to take interference matrices into account, they must be available
in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, and
imported in the Interference Matrices folder. For more information on interference matrices, see "Working with
Interference Matrices" on page 1201.
Existing Neighbours: Select this check box if you want the audit to take neighbours into account. Atoll can only
take neighbour relations into account if neighbours have already been allocated. For information on allocating
neighbours, see "Configuring Network Parameters Using the AFP" on page 1200.
Reuse distance: Select this check box if you want the audit to take reuse distance into account. For cells that do
not have a reuse distance defined in their properties, the value entered next to Default will be used for the audit.
4. On the right-hand side of the Resource Allocation Audit dialog box, Atoll displays the Total cost of the current frequency allocation.
You can click the Weights button to open the Weights dialog box and modify the cost
component weights. For more information, see "Configuring Cost Component Weights" on
page 1202.
5. Click Calculate. Atoll performs an audit of the current frequency plan. Any messages generated by the audit are
reported on the Events tab. The audit results are reported on the following tabs:
The Statistics tab provides overall statistics such as the numbers of various types of relations considered by the AFP
for frequency planning and the number of violated relations.
The Relations tab lists all the relations between active and filtered cells in the document. The Relations tab can display
the following information:
1206
AT332_UMR_E0
Neighbour importance: The importance of the neighbour relation between Cell 1 and Cell 2.
The data table in the Relations tab can be filtered. For example, you can view all the relations, only the relations
that violate the frequency allocation requirements, or apply a filter to exclude unimportant ones. To filter the relations listed in the Relations tab, click the Show button (
ii. Under Include relations by type, select all the options representing the relation types and select (All) from
their respective lists.
iii. Click Apply. The data table in the Relations tab shows all the relations between cells.
To view only the relations that violate the frequency allocation requirements:
i.
ii. Under Include relations by type, select all the options representing the relation types and select (All) from
their respective lists.
iii. Click Apply. The data table in the Relations tab shows only the relations that violate the frequency allocation
requirements.
To view only the important relations that violate the frequency allocation requirements:
i.
ii. Under Include relations by type, select the relation types that you consider important and select some or all
of their characteristics from their respective lists.
iii. Click Apply. The data table in the Relations tab shows the relations according to the user-defined filter.
The Cells tab lists the current allocation plan and the following information:
The Distribution tab shows the histogram of the current allocation plan.
You can expand the right pane of the Resource Allocation Audit dialog box by
clicking the Hide button ( ).
You can export the contents of table grids to TXT, CSV, and XML Spreadsheet files
by right-clicking the table and selecting Export from the context menu. For more
information on exporting data tables, see "Exporting Tables to Text Files and
Spreadsheets" on page 86.
You can select the columns to display in different tabs by right-clicking the table
and selecting Display Columns from the context menu. For more information, see
"Displaying and Hiding Columns" on page 80.
1207
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.
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.
This section covers the following topics:
Wi-Fi radio bearers: Radio bearers are used by the network for carrying information. The Wi-Fi Radio Bearer table
lists all the available radio bearers. You can create new radio bearers and modify existing ones by using the Wi-Fi Radio
Bearer table. For information on defining radio bearers, see "Defining Wi-Fi Radio Bearers" on page 1237.
Services: Services are the various services, such as VoIP and FTP download, available to users. These services can be
either of the type "voice" or "data". For information on modelling end-user services, see "Modelling Services" on
page 1182.
Mobility types: Information about receiver mobility is important to determine the users radio conditions and
throughputs. For information on modelling mobility types, see "Modelling Mobility Types" on page 1183.
Terminals: 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 modelling terminals, see "Modelling Terminals" on page 1183.
This section explains the specific mechanisms that are used to calculate Wi-Fi traffic simulations. For information on working
with traffic simulations in Atoll, see "Simulations" on page 265.
1208
AT332_UMR_E0
Each mobile generated during the simulations is assigned a service, a mobility type, and a terminal according to the
user profile assigned to it. A transmission status is determined according to the activity probabilities. The transmission
status is an important output of the simulation as it has a direct impact on the next step of the simulation process, i.e.,
the radio resource management (RRM), and has an impact on the interference level in the network.
Unless fixed, the geographical location of each mobile is determined randomly for the mobiles generated based on
the traffic data from traffic maps.
1209
At the end of the simulations, active users can be connected in the direction corresponding to his activity status if the following
conditions are met:
A user may be rejected in step 2. for "No Coverage" step 3. for "No Service" and step 4. for:
"Scheduler Saturation": The user is not among the users selected for resource allocation.
"Resource Saturation": All of the cells resources were used up by other users or if, for a user active in uplink, the minimum uplink throughput demand was higher than the uplink allocated bandwidth throughput.
"Backhaul Saturation": The user was among the lowest priority service users served by a cell of a site whose defined
maximum backhaul throughputs were exceeded while allocating resources for the minimum throughput demands.
As a distribution map. To display distribution maps of a simulation, see "Displaying Simulation Results on the Map" on
page 270.
By accessing the actual values of the simulation. Actual values can be displayed either for a single simulation or as
average values for a group of simulations.
15.4.2.2.1
Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; radio resource allocation 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 throughput demands 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 throughput demands) is given.
Results: Data on the connection results:
1210
Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink in all the cells of the site.
Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink in all the cells of the site.
Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink in all the cells of the site.
Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink in all the cells of the site.
Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink in all the cells of the site.
Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink in all the cells of the site.
AT332_UMR_E0
Connection success rate (%): The percentage of users connected to any cell of the site with respect to the number
of users covered by the cells of the site.
Total number of connected users: The total number of users connected to any cell of the site in downlink, uplink,
or downlink and uplink both.
Number of connected users (DL+UL): The number of users connected to any cell of the site in downlink and uplink
both.
Number of connected users (DL): The number of users connected to any cell of the site in downlink.
Number of connected users (UL): The number of users connected to any cell of the site in uplink.
No service: The number of users unable to connect to any cell of the site for which the rejection cause was "No
service."
No service (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was
"No service."
Scheduler saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Scheduler saturation."
Scheduler saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Scheduler saturation."
Resource saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Resource saturation."
Resource saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Resource saturation."
Backhaul saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Backhaul saturation."
Backhaul saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Backhaul saturation."
Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink in all the cells of the site.
Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the downlink in all the cells of the site.
Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink in all the cells of the site.
Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink in all the cells of the site.
Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the uplink in all the cells of the site.
Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink in all the cells of the site.
Connection success rate (%) for each service: For each service, the percentage of users connected to any cell of
the site with respect to the number of users covered by the cells of the site.
The Cells tab contains the following information, per site and transmitter:
Traffic load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation.
Traffic load (UL) (%): The traffic loads of the cells calculated on the uplink during the simulation.
UL noise rise (dB): The noise rise of the cells calculated on the uplink during the simulation.
Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink.
Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink.
Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink.
Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink.
Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink.
Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink.
Connection success rate (%): The percentage of users connected to the cell with respect to the number of users
covered by the cell.
Total number of connected users: The total number of users connected to the cell in downlink, uplink, or downlink
and uplink both.
Number of connected users (DL+UL): The number of users connected to the cell in downlink and uplink both.
Number of connected users (DL): The number of users connected to the cell in downlink.
Number of connected users (UL): The number of users connected to the cell in uplink.
No service: The number of users unable to connect to the cell for which the rejection cause was "No service."
No service (%): The percentage of users unable to connect to the cell for which the rejection cause was "No service."
Scheduler saturation: The number of users unable to connect to the cell for which the rejection cause was "Scheduler saturation."
1211
Scheduler saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Scheduler saturation."
Resource saturation: The number of users unable to connect to the cell for which the rejection cause was
"Resource saturation."
Resource saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Resource saturation."
Backhaul saturation: The number of users unable to connect to the cell for which the rejection cause was "Backhaul saturation."
Backhaul saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Backhaul saturation."
Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink.
Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the downlink.
Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink.
Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink.
Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the uplink.
Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink.
Connection success rate (%) for each service: For each service, the percentage of users connected to the cell with
respect to the number of users covered by the cell.
1212
X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the second
random trial).
Height: The height of the user terminal (antenna).
User profile: The assigned user profile. Atoll uses the assigned service and activity status to determine the terminal and the user profile.
Subscriber ID: The ID of the user if the user is generated from a subscriber list and not from a traffic map.
Subscriber list: The subscriber list of the user if the user is generated from a subscriber list and not from a traffic
map.
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.
Mobility: The mobility type assigned during the first random trial during the generation of the user distribution.
Activity status: The assigned activity status. It can be Active DL, Active UL, Active DL+UL, or Inactive.
Connection status: The connection status indicates whether the user is connected 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.
Clutter class: The code of the clutter class where the user is located.
Indoor: This field indicates whether indoor losses have been added or not.
Best server: The best server of the user.
Serving cell: The serving cell of the serving transmitter of the user.
Azimuth: The orientation of the users terminal antenna in the horizontal plane. Azimuth is always considered
with respect to the North. Atoll points the user antenna towards its best server.
Downtilt: The orientation of the users terminal antenna in the vertical plane. Mechanical downtilt is positive
when it is downwards and negative when upwards. Atoll points the user antenna towards its best server.
Path loss (dB): The path loss from the best server calculated for the user.
2nd best server: The second best server of the user.
2nd best server path loss (dB): The path loss from the second best server calculated for the user.
3rd best server: The third best server of the user.
3rd best server path loss (dB): The path loss from the third best server calculated for the user.
Received power (DL) (dBm): The signal level received at the user location in the downlink.
C/(I+N) (DL) (dB): The C/(I+N) at the user location in the downlink.
Total noise (I+N) (DL) (dBm): The sum of the traffic interference and noise experienced at the user location in the
downlink.
Bearer (DL): The highest Wi-Fi bearer available for the traffic C/(I+N) level at the user location in the downlink.
Permutation zone (DL): The downlink permutation zone allocated to the user.
BLER (DL): The Block Error Rate read from the user terminals reception equipment for the traffic C/(I+N) level at
the user location in the downlink.
Diversity mode (DL): The diversity mode supported by the cell or permutation zone in downlink.
Peak MAC channel throughput (DL) (kbps): The maximum MAC channel throughput attainable using the highest
bearer available at the user location in the downlink.
AT332_UMR_E0
Effective MAC channel throughput (DL) (kbps): The effective MAC channel throughput attainable using the
highest bearer available at the user location in the downlink. It is calculated from the peak MAC throughput and
the BLER.
Application channel throughput (DL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
Peak MAC user throughput (DL) (kbps): The maximum MAC user throughput attainable using the highest bearer
available at the user location in the downlink.
Effective MAC user throughput (DL) (kbps): The effective MAC user throughput attainable using the highest
bearer available at the user location in the downlink. It is calculated from the peak MAC throughput and the BLER.
Application user throughput (DL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
Received power (UL) (dBm): The signal level received at the serving transmitter from the user terminal in the
uplink.
C/(I+N) (UL) (dB): The C/(I+N) at the serving transmitter of the user in the uplink.
Total noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the serving transmitter of the
user in the uplink.
Bearer (UL): The highest Wi-Fi bearer available for the C/(I+N) level at the serving transmitter of the user in the
uplink.
BLER (UL): The Block Error Rate read from the serving cells reception equipment for the C/(I+N) level at the
serving transmitter of the user in the uplink.
Diversity mode (UL): The diversity mode supported by the cell or permutation zone in uplink.
Transmission power (UL) (dBm): The transmission power of the user terminal after power control in the uplink.
Peak MAC channel throughput (UL) (kbps): The maximum MAC channel throughput attainable using the highest
bearer available at user location in the uplink.
Effective MAC channel throughput (UL) (kbps): The effective MAC channel throughput attainable using the
highest bearer available at the user location in the uplink. It is calculated from the peak MAC throughput and the
BLER.
Application channel throughput (UL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
Peak MAC user throughput (UL) (kbps): The maximum MAC user throughput attainable using the highest bearer
available at the user location in the uplink.
Effective MAC user throughput (UL) (kbps): The effective MAC user throughput attainable using the highest
bearer available at the user location in the uplink. It is calculated from the peak MAC throughput and the BLER.
Application user throughput (UL) (kbps): The application throughput is the net throughput without coding (such
as redundancy, overhead, addressing). It is calculated from the effective MAC throughput, the throughput scaling
factor of the service and the throughput offset.
15.4.2.2.2
1213
Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; radio resource allocation 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 throughput demands 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 throughput demands) is given.
The Sites (Average) tab contains the following average information per site:
1214
Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink in all the cells of the site.
Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink in all the cells of the site.
Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink in all the cells of the site.
Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink in all the cells of the site.
Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink in all the cells of the site.
Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink in all the cells of the site.
Connection success rate (%): The percentage of users connected to any cell of the site with respect to the number
of users covered by the cells of the site.
Total number of connected users: The total number of users connected to any cell of the site in downlink, uplink,
or downlink and uplink both.
Number of connected users (DL+UL): The number of users connected to any cell of the site in downlink and uplink
both.
Number of connected users (DL): The number of users connected to any cell of the site in downlink.
Number of connected users (UL): The number of users connected to any cell of the site in uplink.
No service: The number of users unable to connect to any cell of the site for which the rejection cause was "No
service."
No service (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was
"No service."
Scheduler saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Scheduler saturation."
Scheduler saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Scheduler saturation."
Resource saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Resource saturation."
Resource saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Resource saturation."
Backhaul saturation: The number of users unable to connect to any cell of the site for which the rejection cause
was "Backhaul saturation."
Backhaul saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection
cause was "Backhaul saturation."
Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink in all the cells of the site.
Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the downlink in all the cells of the site.
Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink in all the cells of the site.
Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink in all the cells of the site.
Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the uplink in all the cells of the site.
Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink in all the cells of the site.
Connection success rate (%) for each service: For each service, the percentage of users connected to any cell of
the site with respect to the number of users covered by the cells of the site.
AT332_UMR_E0
The Cells (Average) tab contains the following average information per cell:
Traffic load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation.
Traffic load (UL) (%): The traffic loads of the cells calculated on the uplink during the simulation.
UL noise rise (dB): The noise rise of the cells calculated on the uplink during the simulation.
Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink.
Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink.
Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink.
Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink.
Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink.
Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink.
Connection success rate (%): The percentage of users connected to the cell with respect to the number of users
covered by the cell.
Total number of connected users: The total number of users connected to the cell in downlink, uplink, or downlink
and uplink both.
Number of connected users (DL+UL): The number of users connected to the cell in downlink and uplink both.
Number of connected users (DL): The number of users connected to the cell in downlink.
Number of connected users (UL): The number of users connected to the cell in uplink.
No service: The number of users unable to connect to the cell for which the rejection cause was "No service."
No service (%): The percentage of users unable to connect to the cell for which the rejection cause was "No service."
Scheduler saturation: The number of users unable to connect to the cell for which the rejection cause was "Scheduler saturation."
Scheduler saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Scheduler saturation."
Resource saturation: The number of users unable to connect to the cell for which the rejection cause was
"Resource saturation."
Resource saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Resource saturation."
Backhaul saturation: The number of users unable to connect to the cell for which the rejection cause was "Backhaul saturation."
Backhaul saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was
"Backhaul saturation."
Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink.
Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the downlink.
Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink.
Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink.
Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user
throughputs of the users connected in the uplink.
Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink.
Connection success rate (%) for each service: For each service, the percentage of users connected to the cell with
respect to the number of users covered by the cell.
1215
Coverage by C/(I+N) Level: For information on making a downlink or uplink coverage by C/(I+N) level, see "Studying
Interference and C/(I+N) Levels" on page 1184.
Service Area Analysis: For information on making a downlink or uplink service area analysis, see "Studying Downlink
and Uplink Service Areas" on page 1185.
Effective Service Area Analysis: For information on making an effective service area analysis, see "Studying Downlink
and Uplink Service Areas" on page 1185.
Coverage by Throughput: For information on making a downlink or uplink coverage by throughput, see "Making a
Coverage Prediction by Throughput" on page 1187.
Coverage by Quality Indicator: For information on making a downlink or uplink coverage by quality indicator, see
"Making a Coverage Prediction by Quality Indicator" on page 1189.
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:
1. Click the Conditions tab.
2. From the Load conditions list, select the simulation or group of simulations on which you want to base the coverage
prediction.
1216
AT332_UMR_E0
WiFi Coverage
WiFi CINR
You can also create the following objectives from the context menu of Objectives in the left-hand pane of the Objectives tab:
You define the optimisation objectives using the Objectives tab of the ACP Setup dialog box. For information on setting objective parameters, see "Setting Objective Parameters" on page 1329.
Signal Level
C
CN
CINR
Overlap
Best Server Distance
1st-2nd Difference
1st-Nth Difference
1217
You can base the evaluation of a qualiy analysis prediction on a calculated Atoll prediction,
if any, or on a manual configuration.
If you base the evaluation of a qualiy analysis prediction on a calculated Atoll prediction, ACP will use the display settings of the calculated Atoll prediction in the
qualiy analysis prediction calculated for that objective.
If you saved the display settings of a qualiy analysis prediction as defaults, or if you
are using a configuration file for ACP, these display settings will be used by default
and will override the display settings of the calculated Atoll prediction. For more
information on changing the display settings of a quality analysis prediction, see
"Changing the Display Properties of ACP Predictions" on page 1379.
Signal Level
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by signal level.
Base prediction settings on > "Coverage by Signal Level (DL)": ACP will evaluate coverages by signal level based
on the parameters used to calculate the selected "Coverage by Signal Level (DL)" prediction in Atoll.
Only the coverage predictions displaying a "Best Signal Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": If you select this option, you can Enable shadowing margin
and define a Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no
clutter information available, default values are used.
C
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by C.
Base prediction settings on > "Effective Signal Analysis (DL)": ACP will evaluate the coverage by C based on the
parameters used to calculate the selected "Effective Signal Analysis (DL)" prediction in Atoll.
Only the coverage predictions displaying a "Signal Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": If you select this option, you can Enable shadowing margin
and define a 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. Additionally, you can specify:
Service and Terminal that will be used during the calculation of C through gain and losses (i.e., the service body
loss, the gain and loss of the terminal antenna, and the terminal noise factor).
C/N
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by C/N.
Base prediction settings on > "Effective Signal Analysis (DL)": ACP will evaluate the coverage by C/N based on the
parameters used to calculate the selected "Effective Signal Analysis (DL)" prediction in Atoll.
Only the coverage predictions displaying a "C/N Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": If you select this option, you can Enable shadowing margin
and define a 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. Additionally, you can specify:
Service and Terminal that will be used during the calculation of C/N through gain and losses (i.e., the service
body loss, the gain and loss of the terminal antenna, and the terminal noise factor).
CINR
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by CINR.
Base prediction settings on > "Coverage by C/(I+N) Level (DL)": ACP will evaluate the coverage by CINR based on
the parameters used to calculate the selected "Coverage by C/(I+N) Level (DL)" prediction in Atoll.
Only the coverage predictions displaying a "C/(I+N) Level" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": If you select this option, you can Enable shadowing margin
and define a 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. Additionally, you can specify:
Service and Terminal that will be used during the calculation of CINR through gain and losses (i.e., the service
body loss, the gain and loss of the terminal antenna, and the terminal noise factor).
Calculation Method for CINR. Select Using frequency plan or Ignoring frequency plan & segmentation.
Overlap / 1st-Nth
Click this parameter to define in the right-hand pane how ACP will evaluate coverage by overlapping zones or by 1stNth difference.
Overlap
Base prediction settings on > "Overlapping Zones (DL)": ACP will evaluate coverages by overlapping based on
the parameters used to calculate the selected "Overlapping Zones (DL)" prediction in Atoll.
Only the Atoll predictions displaying a "Number of Servers" per pixel can be accessed by the ACP.
Base prediction settings on > "Manual configuration": If you select this option, you can set a Minimum signal
level and a Threshold margin.
1st-Nth
1218
AT332_UMR_E0
Base prediction settings on > "Overlapping Zones (DL)": ACP will evaluate coverages by 1st-Nth difference
based on the parameters used to calculate the selected "Overlapping Zones (DL)" prediction in Atoll.
Since there is no Atoll prediction type equivalent to ACP WiFi 1st-Nth Difference objective, the parameters
recovered by ACP from the selected Atoll prediction are limited to the minimum signal level and the shading.
The number of servers must always be specified manually next to No. servers.
Base prediction settings on > "Manual configuration": If you select this option, specify a Minimum signal
level and the No. servers.
In both cases, the value you specify next to No. servers determines "Nth" in the WiFi 1st-Nth Difference objective. For instance if you set No. servers to 4, then the "1st-4th Difference" quality parameter will be automatically selected by default in the Quality column of the WiFi 1st-Nth Difference properties page.
- Allowed values for No. servers range from 3 to 100, with only one value available per technology.
- The "1st-2nd Difference" quality parameter (based on No. servers = 2) is provided by default.
Figure 15.15: ACP Quality Analysis Prediction Types for a Wi-Fi Network
ACP quality analysis predictions are equivalent to some of Atoll coverage predictions. The following table lists the quality analysis predictions available in ACP for Wi-Fi and the equivalent Wi-Fi coverage predictions in Atoll.
Signal Level
C/N
CINR
Overlap
1st-Nth Difference
N/A
(1) For more information, see "Making a Coverage Prediction by Signal Level" on page 1180.
(2) For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 1181.
Making these predictions 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 predictions display results very similar to those
that Atoll would display if you committed the optimisation results and calculated Atoll coverage predictions, however, before
1219
basing any decision to commit the optimisation results on the predictions 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 overlapping zones prediction.
ACP generated predictions are generated using the entire set of proposed changes. They do not take into account the
change subset defined on the Change Details tab.
ACP supports optimisation for transmitters belonging to different frequency bands, with predictions provided separately for each frequency band. However multiple-carrier optimisation is not supported in Wi-Fi (case of carriers
within same transmitters belonging to different frequency bands).
Even after committing the optimisation results, differences can remain between the ACP predictions and the predictions resulting from Atoll coverage predictions.
You can view the exact CINR value on any pixel by letting the pointer rest over the pixel. The CINR value is then displayed in a
tip text.
For ACP overlapping zones predictions, you can:
By entering a value next to Threshold margin in the Overlap / 1st-Nth properties page,
Or by setting the param.wifi.overlap.margin option with the same value in the [ACPTplObjectivePage] section of
the ACP.ini file.
For each network quality coverage prediction, ACP offers a prediction showing the initial network state, the final network
state, and a prediction showing the changes between the initial and final state.
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 Wi-Fi networks,
a cell can be identified by its BSID (6-byte MAC address).
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 with 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.
1220
AT332_UMR_E0
When importing a drive test data path file, existing configurations are available in
the Files of type list of the Open dialog box, 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.
5. 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:
d. Under Server identification, select By BSID and the column containing the BSIDs of the scanned cells in the By
BSID list.
e. Click OK to close the Drive Test Data Setup dialog box.
1221
If you have correctly entered the information under File on the Setup tab, and the
necessary values in the Drive Test Data Setup dialog box, Atoll should recognise 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>". Columns marked with
"<Ignore>" will not be imported.
The data in the file must be structured so that the column identifying the BSID is
placed before the data columns for each cell. Otherwise Atoll will not be able to
properly import the file.
7. 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 dialog box appears.
b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atoll installation folder. In
case you cannot write into that folder, you can click Browse to choose a different location.
c. Enter a Configuration name and an Extension of the files that this import configuration will describe (for example,
"*.txt").
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 can select this
import configuration from the Import 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 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 dialog box.
You can delete an existing import configuration by selecting the import configuration file under Import configuration and clicking the Delete button.
8. Click Import, if you are only importing a single file, or Import all, if you are importing more than one file. The drive test
data is imported into the current Atoll document.
1222
AT332_UMR_E0
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, the Shadings dialog box opens in which you can define the
following display for each single point of the measurement path:
You can, for example, display a signal level in a certain colour, choose a symbol for each transmitter (such as a circle,
triangle, cross) 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 in the Network explorer 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 dialog box and select Save or Load from
the Display Configuration submenu.
"Filtering Measurement Points Along Drive Test Data Paths" on page 1223
"Predicting the Signal Level on Drive Test Data Points" on page 1224
"Creating Coverage Predictions on Drive Test Data Paths" on page 1225
"Displaying Statistics Over a Drive Test Data Path" on page 1225
"Extracting a Field From a Drive Test Data Path for a Transmitter" on page 1226
"Analysing Measurement Variations Along the Path" on page 1226
You can apply a filter on all the drive test data paths in the Drive Test Data folder
by selecting Filter from the context menu of the folder.
If you want to use the measurement points that you permanently deleted, you will
have to import the drive test data path again.
1223
5. Click More to filter out measurement points using an advanced filter. The Filter dialog box appears. For more information on using the Filter dialog box, see "Advanced Data Filtering" on page 101.
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 folder.
Figure 15.17: Selecting Measured Signal Levels for which Errors will be Calculated
4. Click OK. A point prediction is created for the selected drive test data path.
5. Right-click the drive test data path and select Calculations > Calculate All the Predictions from the context menu.
If you chose to have Atoll calculate the errors between measured and predicted signal levels, new columns are added to the
drive test data table for the predicted point signal level from the serving cell and the errors between the measured and
predicted values.
1224
AT332_UMR_E0
Figure 15.18: Drive Test Data Table after Point Signal Level Prediction (with Error Calculations)
New columns are also added for the predicted point signal level from each neighbour cell and the errors between the
predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For
more information on the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 1226.
The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main
matrix. For more information on propagation models, see Chapter 4: Radio Calculations and Models.
On the Conditions tab, you can set the range of the 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 an Overlap 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. Indoor losses are defined per frequency
per clutter class.
3. When you have finished setting the parameters for the coverage prediction, click OK.
You can create other coverage predictions by repeating the procedure from step 1. to step 3. for each new coverage
prediction.
4. When you have finished creating coverage predictions for these drive test data, right-click the drive test data and
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 4: Radio Calculations and
Models).
You can display the information in these new columns in the Drive Test Data analysis tool. For more information on
the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 1226.
1225
4. Under Select the measured values, select the fields that contain the measured values that you want to use in the statistics.
5. Enter the Measured values range for the statistics. Only the measured values within this range will be included in the
statistics.
6. Click OK.
Atoll opens a window listing statistics of comparison between measured and predicted values.
15.6.4.5 Extracting a Field From a Drive Test Data Path for a Transmitter
You can extract information for a selected transmitter from a field of a drive test data path. The extracted information is available in a new column in the drive test data table.
To extract a field from a drive test data path:
1. In the Network explorer, expand the Drive Test Data folder, right-click the drive test data from which you want to
extract a field, and select Focus on a Transmitter from the context menu. The Field Selection for a Given Transmitter
dialog box appears.
2. Under On the transmitter, select the transmitter for which you want to extract a field.
3. Under For the fields, select the fields that you want to extract for the selected transmitter.
4. Click OK. Atoll creates a new column in the drive test data path table for the selected transmitter and with the selected
values.
Select the check box next to each field you want to display in the Drive Test Data analysis tool.
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.
You can change the display status or the colour of more than one field at the same time by
selecting several fields. 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 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 analysis tool.
4. You can display the data in the drive test data path in the following ways:
The drive test data path appears in the map window as an arrow pointing towards the best server in the same colour
as the transmitter.
5. You can display a secondary 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 dialog box. You select the value to be
displayed from the right-hand list at the top of the Drive Test Data analysis tool. The values are displayed in the colour
defined in the Display Parameters dialog box.
6. You can zoom in on the graph displayed in the Drive Test Data analysis tool in the following ways:
Zoom in or out:
i.
Right-click the Drive Test Data analysis tool. The context menu appears.
1226
AT332_UMR_E0
i.
Right-click the Drive Test Data analysis tool on one end of the range of data you want to zoom in on. The context menu appears.
1227
Select File > Open or File > New > From an Existing Database.
1228
AT332_UMR_E0
As soon as a link is created between the two documents, Atoll switches to co-planning mode and the 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 synchronises 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.
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 107. 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
"Associating a Tip Text to an Object" on page 54.
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 "Changing the Order of
Layers" on page 51.
1229
Global scaling factor: If needed, 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 throughputs/users (for sector traffic maps).
Select traffic maps to be used: Select the traffic maps in the mobile network technology (linked) document that
you want to use for the simulation.
5. On the technology-specific tab, named after the technology of the linked mobile network document, define the load
constraints and convergence criteria specific to the mobile network.
6. On the Wi-Fi tab, select the Take the Wi-Fi network into account check box and enter the following:
Under Load constraints, enter the Max DL traffic load and Max UL traffic load.
If you want to enter a global value for a maximum traffic load, click the button (
Global threshold. Then, enter a maximum traffic load.
If you want to use the maximum traffic load as defined in the properties for each cell, click the button (
beside the box and select Defined per cell.
Under Convergence, enter the following parameters:
DL traffic load convergence threshold: Enter the relative difference in terms of downlink traffic load that must
be reached between two iterations.
UL traffic load convergence threshold: Enter the relative difference in terms of uplink traffic load that must
be reached between two iterations.
UL noise rise convergence threshold: Enter the relative difference in terms of uplink noise rise that must be
reached between two iterations.
Max number of iterations: Enter the maximum number of iterations that Atoll should run to make convergence.
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.
8. Once you have defined the simulation, click Calculate to save the defined simulation and calculate it immediately.
When you calculate a Monte Carlo simulation in co-planning mode with Wi-Fi network taken into account, Atoll carries out
the following steps:
1. Creates a mobile user distribution on the map based on the selected traffic maps from the mobile network document.
2. Sends this mobile distribution to the main Wi-Fi document.
3. Creates and runs a Wi-Fi Monte Carlo simulation in the Wi-Fi document, with the same parameters as those set in the
mobile network document when creating the co-planning simulation, using the mobile distribution received from the
mobile network document. In other words, traffic maps in the mobile network document are used to generate the
traffic scenario. Any traffic maps available in the Wi-Fi document are not used.
4. In order for a mobile generated by Atoll in step 1. to be taken into account in the Wi-Fi Monte Carlo simulation, the
mobiles service, terminal, and mobility type must exist in the traffic parameter definition in the Wi-Fi document.
5. Once the Wi-Fi Monte Carlo simulation is complete, the list of mobiles unable to connect to Wi-Fi is sent back to the
mobile network document as potential users attempting to connect to the mobile network, and the list of mobiles
connected to Wi-Fi is sent back to the mobile network document with their connection status set to "Connected WiFi."
6. Runs the mobile network Monte Carlo simulation using the list of mobiles unable to connect to Wi-Fi.
1230
AT332_UMR_E0
The Monte Carlo simulation results in the mobile network document contain the number of mobiles connected to Wi-Fi, in
addition to the usual results of the mobile network Monte Carlo simulations. The Wi-Fi Monte Carlo simulation results, in the
Wi-Fi document, contain detailed results for the mobiles connected to Wi-Fi. For more information on the Monte Carlo simulation results available in Wi-Fi, see "Wi-Fi Simulation Results" on page 1210.
In order to study the impact of a Wi-Fi network on your mobile network, you can perform Monte Carlo simulations in your
mobile network document with and without taking the Wi-Fi network into account, and compare the statistics on the
numbers of connected and rejected users, throughputs, and cell loads, in the two cases.
When you click the Calculate button, Atoll first 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 and Unlocking Coverage Predictions" on page 207.
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 recalculate all path loss matrices before calculating coverage predictions:
1. Click the Force Calculate button (
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.
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.
1231
15.7.3.2.1
15.7.3.2.2
15.7.3.2.3
15.7.3.2.4
1232
AT332_UMR_E0
15.7.3.2.5
When Use coverage conditions is not selected, the defined Distance is used to allocate neighbours to a reference
transmitter.
When Use coverage conditions is selected, click Define for eWi-Fi to open the corresponding Coverage Conditions
dialog box:
Resolution: Enter the resolution to be used to calculate cell coverage areas during automatic neighbour allocation.
Margin: Enter a handover margin.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this option to take indoor losses into account in calculations. Indoor losses are defined
per frequency per clutter class.
1233
Co-site neighbours: Cells located on the same site as the reference transmitter will automatically be considered as
neighbours. A transmitter/cell with no antenna cannot be considered as a co-site neighbour.
Exceptional pairs: Select this option to force the neighbour relations defined in the Inter-technology Exceptional pairs
table. For more information, see "Defining Exceptional Pairs" on page 223.
Description
When
Distance
Coverage
Co-Site
Exceptional Pair
Exceptional pairs
is selected
Existing
1234
AT332_UMR_E0
Click the Run button to run the optimisation immediately. For information on running the optimisation, see "Running
an Optimisation Setup" on page 1359. For information on the optimisation results, see "Viewing Optimisation Results"
on page 1362.
Click the Create Setup button to save the defined optimisation to be run later.
Name: Enter a name for the frequency band, for example, "2.4 GHz - 20 MHz". Each Wi-Fi frequency band has a
specific channel width. Mentioning the channel width in the frequency band name is a good approach. This name
will appear in other dialog boxes when you select a frequency band.
Start frequencies (MHz): Enter the downlink and the uplink start frequencies.
Channel width (MHz): Enter the channel width for each channel in the frequency band.
Inter-channel spacing (MHz): Enter the spacing between any two consecutive channels in the frequency band.
1235
First channel: Enter the number of the first channel in this frequency band.
Last channel: Enter the number of the last channel in this frequency band. If this frequency band has only one carrier, enter the same number as entered in the First channel field.
Step: Enter the step between any two consecutive channel numbers in the frequency band.
Excluded channels: Enter the channel numbers which do not belong to the frequency band. You can enter nonconsecutive channel numbers separated with a comma, or you can enter a range of channel numbers separating
the first and last index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
Adjacent channel suppression factor (dB): Enter the adjacent channel interference suppression factor in dB. Interference received from adjacent channels is reduced by this factor during the calculations.
3. When you have finished adding frequency bands, click the Close button (
).
For example, to define the 2.4 GHz band with 20 MHz channels and channel numbers of non-overlapping channels (1, 5, 9,
13), you can set:
You can also access the properties dialog box of each individual frequency band by double-clicking the left margin of the table
row containing the frequency band.
Min interferer C/N threshold: Minimum requirement for interferers to be considered in calculations. Interfering cells
from which the received carrier-power-to-noise ratio is less than this threshold are discarded.
For example, setting this value to -20 dB means that interfering cells from which the received signals are 100 times
lower than the thermal noise level will be discarded in calculations. The calculation performance of interferencebased coverage predictions, interference matrices calculations, and Monte Carlo simulations can be improved by
setting a high value of this threshold.
Height/ground: The receiver height at which the path loss matrices and coverage predictions are calculated. Calculations made on mobile users (from traffic maps) in Monte Carlo simulations are also carried out at this receiver height.
Calculations made on fixed subscribers in Monte Carlo simulations are carried out at their respective heights.
Default max range: The maximum coverage range of transmitters in the network.
Calculation limitation: In this section, you can enter the Min interferer C/N threshold.
Receiver: In this section, you can enter the receiver Height.
System: In this section, select the Default max range check box if you want to apply a maximum system range
limit, and enter the maximum system range in the text box to the right.
3. Click OK. The global parameters are used during coverage predictions and simulations for the entire network.
1236
AT332_UMR_E0
3. Double-click the frame configuration row in the table once the new frame configuration has been added to the table.
The frame configuration Properties dialog box opens.
4. Under the General tab, you can modify the parameters that you set previously. You can also modify the following
parameters:
Number of used subcarriers: The number of subcarriers used for transmission. This number includes the pilot and
data subcarriers.
Number of traffic subcarriers: The number of subcarriers used for user data traffic.
Downlink diversity support: The type of antenna diversity technique (STTD/MRC, SU-MIMO, or AMS) supported.
Uplink diversity support: The type of antenna diversity technique (STTD/MRC, SU-MIMO, AMS, or MU-MIMO)
supported.
You cannot select more than one type of MIMO technique at a time. Specific calculations are performed (and gains
applied) for terminals supporting MIMO. A frame configuration that only supports None does not have any antenna diversity mechanism, and all the terminal types can connect to this zone. A frame configuration that supports
None and one or more antenna diversity techniques can also support terminals capable of those diversity techniques. For example, None+STTD/MRC can support simple as well as MIMO-capable terminals. Simple terminals
cannot connect to a cell whose frame configuration does not support None.
Radio bearer index: Enter a bearer index. This bearer index is used to identify the bearer in other tables, such as
the bearer selection thresholds and the quality graphs in reception equipment.
Name: Enter a name for the bearer, for example, "16QAM3/4." This name will appear in other dialog boxes and
results.
Modulation: Select a modulation from the list of available modulation types. This column is for information and
display purposes only.
Channel coding rate: Enter the coding rate used by the bearer. This column is for information and display purposes
only.
Bearer efficiency (bits/symbol): Enter the number of useful bits that the bearer can carry in a symbol. This information is used in throughput calculations.
1237
Name: Enter a name for the quality indicator, for example, "BLER" for Block Error Rate. This name will appear in
other dialog boxes and results.
Used for data services: Select this check box to indicate that this quality indicator can be used for data services.
Used for voice services: Select this check box to indicate that this quality indicator can be used for voice services.
General: On this tab, you can define the Name of the reception equipment.
Thresholds: On this tab (see Figure 15.19), you can modify the bearer selection thresholds for different mobility
types. A bearer is selected for data transfer at a given pixel if the received carrier-to-interference-and-noise ratio
is higher than its selection threshold. For more information on bearers and mobility types, see "Defining Wi-Fi
Radio Bearers" on page 1237 and "Modelling Mobility Types" on page 1183, respectively.
Click the Selection thresholds button. The C/(I+N) Thresholds (dB) dialog box appears (see Figure 15.20).
1238
AT332_UMR_E0
Quality Graphs: On this tab, you can modify the quality indicator graphs for different bearers and mobility types.
These graphs depict the performance characteristics of the equipment under different radio conditions. For more
information on bearers, quality indicators, and mobility types, see "Defining Wi-Fi Radio Bearers" on page 1237,
"Defining Wi-Fi Quality Indicators" on page 1238, and "Modelling Mobility Types" on page 1183, respectively.
i.
Click the Quality graph button. The Quality Graph dialog box appears.
Traffic MIMO Gains: On this tab, you can modify the SU-MIMO and STTD/MRC gains for different bearers, mobility
types, BLER values, and numbers of transmission and reception antennas. The MIMO throughput gain is the
increase in channel capacity compared to a SISO system. Diversity gains can be defined for different diversity
modes: STTD/MRC, SU-MIMO, and MU-MIMO. STTD/MRC gain is applied to the C/(I+N) when the diversity mode
is STTD/MRC. SU-MIMO diversity gain is applied to the C/(I+N) when the diversity mode is SU-MIMO. MU-MIMO
diversity gain is applied to the C/(I+N) when the diversity mode is MU-MIMO.
For more information on bearers and mobility types, see "Defining Wi-Fi Radio Bearers" on page 1237 and "Modelling Mobility Types" on page 1183, respectively. For more information on the different MIMO systems, see "Multiple Input Multiple Output (MIMO) Systems" on page 1240.
No MIMO gain (STTD/MRC, SU-MIMO, and MU-MIMO) is applied if the numbers of transmission and reception antennas are both equal to 1.
i.
Click the Max MIMO gain graphs button. The Max MIMO Gain dialog box appears (see Figure 15.21).
1239
1240
AT332_UMR_E0
When SU-MIMO improves the channel capacity or throughputs, the C/(I+N) of a user is first determined. Once the C/(I+N) is
known, Atoll calculates the user throughput based on the bearer available at the user location. The obtained user throughput
is then increased according to the SU-MIMO capacity gain and the SU-MIMO gain factor of the user clutter class. The capacity
gains defined in Max SU-MIMO gain graphs are the maximum theoretical capacity gains using SU-MIMO. SU-MIMO requires
rich multipath environment, without which the gain is reduced. In the worst case, there is no gain. Therefore, it is possible to
define an SU-MIMO gain factor per clutter class whose value can vary from 0 to 1 (0 = no gain, 1 = 100% gain). For information
on setting the SU-MIMO gain factor for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on
page 127.
A point analysis (see "Studying the Profile Around an Access Point" on page 1175)
A coverage prediction (see "Studying Signal Level Coverage of a Single Access Point" on page 1180).
1241
Atoll always takes shadowing into consideration when calculating a Monte Carlo simulations. Atoll uses the values defined
for the model standard deviations per clutter class when calculating the signal level coverage predictions. Atoll uses the values
defined for the C/I standard deviations per clutter class when calculating the interference-based coverage predictions.
You can display the shadowing margins per clutter class.
To display the shadowing margins per clutter class:
1. In the Network explorer, right-click the Predictions folder and select Shadowing Margins from the context menu. The
Shadowing Margins dialog box appears.
2. 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 dialog box is for information only.
Standard deviation: Select the type of standard deviation to be used to calculate the shadowing margin:
Model: The model standard deviation. Atoll will display the shadowing margin of the signal level.
C/I: The C/I standard deviation. Atoll will display the C/I shadowing margin.
Interference received by mobiles on the downlink: Interference can be received by mobiles in a Wi-Fi network on the
downlink from external base stations and mobiles in the vicinity.
Downlink-to-downlink interference can 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 (such as LTE, UMTS, CDMA2000). These graphs are
then used for calculating the interference from the external sources. This interference is taken into account in all
downlink interference-based calculations.
Uplink-to-downlink interference can be created by insufficient separation between the uplink frequency used by the
external network and the downlink frequency used by your Wi-Fi network. The effect of this interference is modelled
in Atoll using the Inter-technology DL noise rise definable for each cell in the Wi-Fi network. This noise rise is taken
into account in all downlink interference-based calculations. For more information on the Inter-technology DL noise
rise, see "Cell Properties" on page 1168.
Interference received by cells on the uplink: Interference can be received by cells of a Wi-Fi network on the uplink
from other-network interferers in the vicinity.
Downlink-to-downlink interference can be created by insufficient separation between the downlink frequency used
by the external network and the uplink frequency used by your Wi-Fi network. Such interference may also come from
co-existing TDD networks.
Uplink-to-downlink interference can be created by the use of same or nearby frequencies for uplink in both networks.
The effect of this interference is modelled in Atoll using the Inter-technology UL noise rise definable for each cell in
the Wi-Fi network. This noise rise is taken into account in uplink interference calculations in Monte Carlo simulations,
but not in coverage predictions. For more information on the Inter-technology UL noise rise, see "Cell Properties" on
page 1168.
1242
AT332_UMR_E0
IRFs are used by Atoll to calculate the interference from external sources only if the Atoll document containing the other
networks is linked to your Wi-Fi document, which means in co-planning mode. For more information on how to switch to coplanning mode, see "Switching to Co-planning Mode" on page 1228.
To define the inter-technology IRFs in the victim network:
1. In the Parameters explorer, expand the Radio Network Equipment folder, right-click Inter-technology Interference
Reduction Factors, and select Open Table. The Inter-technology Interference Reduction Factors table appears.
2. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter:
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.
You can link more than one Atoll document with your main document following the procedure described in "Switching to Coplanning Mode" on page 1228. 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 Atoll will calculate interference from all the
external access points in all the linked documents.
1243
Where RS is the receiver sensitivity in dBm, NF is the noise figure of the receiver in dB, BW is the channel bandwidth in MHz,
N Used is the number of used subcarriers, N Total is the total number of subcarriers, and L Imp is the implementation loss in
dB. If you do not know the value for L Imp , you can ignore the corresponding term and simplify the equation. According to
IEEE, typical values for NF and L Imp are 10 and 5 dB, respectively.
Here the term receiver refers to the access point in uplink and to the mobile/user equipment in the downlink.
1244
Chapter 16
LPWA Networks
This chapter covers how to use Atoll to design,
analyse, and optimise LPWA-based wireless IoT
networks, including LoRa, Wireless MBus, and
other low-throughput ultra-narrowband
technologies.
1246
AT332_UMR_E0
16 LPWA Networks
Low Power Wide Area (LPWA) refers to technologies that enable wireless internet of things (IoT) networks. Such technologies
include LoRa, Wireless MBus, and other low-throughput ultra-narrowband technologies. Most of the LPWA technologies work
over unlicensed frequency bands and use various proprietary channel structures, frame structures, and modulations. LPWA
networks may range from city- to country-wide networks comprising long-range transmission and reception points (gateways)
to cover large numbers of connected objects and end-devices.
The Atoll LPWA module enables you to design and optimise LPWA-based wireless IoT networks. You can use Atoll to predict
radio coverage, carry out calculations on fixed locations of end-devices, and evaluate network capacity. Atoll supports
licensed as well as unlicensed frequency bands, technology-specific channel configurations, and modulation techniques with
or without link adaptation, and transmission and reception diversity. You can create coverage predictions to analyse the
following and other parameters for LPWA channels in downlink and uplink:
Signal levels
Number of servers
Carrier-to-interference-and-noise ratio
Services areas
Throughputs per cell
Moreover, the Atoll LPWA ACP can be used for LPWA site selection based on server redundancy as well as signal level and
quality objectives. The ACP can also be used to optimise operational IoT networks.
You can open an existing Atoll document by selecting File > Open.
You can create an Atoll document as explained in Chapter 1: Working Environment.
You can also add gateways using a station template (see "Placing a New Gateway Using a Station Template" on
page 1253).
3. Carry out basic coverage predictions. See "Signal Level Coverage Predictions" on page 1265.
4. Allocate neighbours. See "Planning Neighbours" on page 1283.
5. Before making more advanced coverage predictions, you need to define cell load conditions manually either on the
Cells tab of each transmitter Properties dialog box or in the Cells table (see "Creating or Modifying a Cell" on
page 1253).
6. Make LPWA-specific signal quality coverage predictions using the defined cell load conditions. See "LPWA Coverage
Predictions" on page 1267.
7. If necessary, modify network parameters to study the network.
1247
In Atoll, you can study a single gateway or a group of gateways using coverage predictions. Atoll allows you to make a variety
of coverage predictions, such as signal level or signal quality coverage predictions. The results of calculated coverage predictions can be displayed on the map, compared, and studied.
Atoll enables you to model network traffic by creating services, users, user profiles, traffic environments, and terminals. This
data can be then used to make coverage predictions that depend on network load, such as C/(I+N), service area, radio bearer,
and throughput coverage predictions.
This section covers the following topics:
Name: A default name is proposed 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.
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 dialog box afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 57.
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.
Name: By default, the transmitter is named after the site it is on, suffixed with an underscore and a number.
You can enter a name for the transmitter. However, it is better to use the name assigned
by Atoll to ensure consistency. To change the way Atoll names transmitters, see the
Administrator Manual.
1248
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. For information on the site Properties dialog box, see "Site
Properties" on page 1248. You can click the New button to create a site for the transmitter.
AT332_UMR_E0
Shared antenna: This field identifies the transmitters, repeaters, and remote antennas located at the same site or on
sites with the same position and that share the same antenna. The entry in the field must be the same for all transmitters, repeaters, and remote antennas sharing the same antenna. When changes are made to the position offset
(Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same
changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. This field is
also used for dual-band transmitters to synchronise antenna parameters for different frequency bands.
Under Antenna position, you can modify the position of the antennas (main and secondary):
Relative to site: Select Relative to site to enter the antenna positions as offsets from the site location, and 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.
Transmitter Tab
Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are displayed with
a specific icon in the Transmitters folder of the Network explorer.
Only active transmitters are taken into consideration during calculations.
Transmitter type: Specify whether the transmitter is to be considered as a server. This enables you to model the coexistence of different networks in the same geographic area.
If the transmitter is to be considered as a potential server as well as an interferer, set the transmitter type to Intranetwork (Server and interferer).
If the transmitter is to be considered only as an interferer, set the type to Inter-network (Interferer only). Interferer-only transmitters are ignored by coverage calculations.
For more information on how to study interference between co-existing networks, see "Modelling the Co-existence
of Networks" on page 1307.
Transmission/Reception: This area displays the total losses and the noise figure of the transmitter. Losses and noise
are calculated according to the characteristics of the equipment assigned to the transmitter. Equipment can be
assigned using the Equipment Specifications dialog box by clicking the Equipment button. For more information
about assigning equipment to a transmitter, see "Assigning Equipment to a Transmitter" on page 1252.
Any loss related to the noise due to a transmitter repeater is included in the calculated
losses. Atoll always considers the values in the Real boxes in coverage predictions even if
they are different from the values in the Calculated boxes. The information in the real
Noise figure box is calculated from the information you entered in the Equipment Specifications dialog box. You can modify the real Total losses at transmission and reception and
the real Noise figure at reception. 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 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.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on page 159
Mechanical Azimuth, Mechanical Downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt display additional antenna parameters.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
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.
1249
Number of MIMO antennas: Enter the number of antennas used for MIMO in the Transmission and Reception
fields. For more information on how the number of MIMO antennas are used, see "Multiple Input Multiple Output
(MIMO) Systems" on page 1304.
Secondary antennas: 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.
Cells Tab
When you create a transmitter, Atoll automatically creates a cell for the transmitter using the properties of the currently
selected station template.
The Cells tab enables you to configure the properties for every cell of a transmitter. For more information on the properties
of a cell, see "Cell Properties" on page 1250.
Propagation Tab
Transmitters are taken into account during calculations. Therefore, you must set the propagation parameters. On the Propagation tab, you can modify the Propagation model, Radius, and Resolution for both the Main matrix and the Extended
matrix. For information on propagation models, see "Assigning Propagation Parameters" on page 187.
Display Tab
On the Display tab, you can modify how a transmitter will be displayed. For information on changing display properties, see
"Setting the Display Properties of Objects" on page 51.
Name: By default, Atoll names the cell after its transmitter, adding a suffix in parentheses. If you change transmitter
name, 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 Administrator Manual.
Active: If this cell is to be active, you must select the Active check box.
Order: The display order of a cell within the transmitter. This value is used to determine the order in which information
related to a cell will be displayed in the Network explorer and on the map. This field is automatically filled by Atoll but
you can change these default values to display cells in a user-defined order.
The consistency between values stored in this field is verified by Atoll. However, inconsistencies may arise when tools other than Atoll modify the database. You can check for inconsistencies in the cell display order and fix them by selecting Data Audit > Cell Display Order
Check in the Document menu.
1250
AT332_UMR_E0
Max traffic load (UL) (%): The uplink traffic load not to be exceeded. If the cell traffic load is limited by this value, the
cell will not be allowed to have an uplink traffic load greater than this maximum.
Additional DL noise rise: This noise rise represents the interference created by the 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 interferencebased calculations involving this cell. For more information on inter-technology interference, see "Modelling Intertechnology Interference" on page 1306.
AMS & MU-MIMO threshold (dB): For AMS, the C/N threshold for switching from SU-MIMO to STTD/MRC as the conditions get worse than the given value. For MU-MIMO, it is the minimum required preamble CNR for using MU-MIMO.
For more information on Adaptive MIMO switching, see "Multiple Input Multiple Output (MIMO) Systems" on
page 1304.
MU-MIMO capacity gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO. In uplink throughput
coverage predictions, the cell capacity will be multiplied by this gain on pixels where MU-MIMO is used.
Number of users (DL): The number of users connected to the cell in the downlink.
Number of users (UL): The number of users connected to the cell in the uplink.
Max number of users: The maximum number of simultaneous users supported by the cell.
Max number of intra-technology neighbours: The maximum number of LPWA neighbours that the cell can have.
Max number of inter-technology neighbours: The maximum number of other technology neighbours that the cell can
have.
Neighbours: You can access a dialog box in which you can set both intra-technology and inter-technology neighbours
by clicking the Browse button. For information on defining neighbours, see "Neighbour Planning" on page 223.
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.
1251
To create a transmitter, right-click the Transmitters folder, and select New from the context menu.
To modify an existing transmitter, expand the Transmitters folder, right-click the transmitter that you want to
modify, and select Properties from the context menu.
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 in the Network explorer and selecting Open Table
from the context menu. For information on copying and pasting data, see "Copying
and Pasting in Tables" on page 83.
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.
1252
TMA: Select a tower-mounted amplifier (TMA) from the list. Click the Browse button to access the properties of
the TMA. For information on creating a TMA, see "Defining TMA Equipment" on page 161.
Feeder: Select a feeder cable from the list. Click the Browse button to access the properties of the feeder. For
information on creating a feeder cable, see "Defining Feeder Cables" on page 161.
Transmitter: Select a transmitter equipment from the Transmitter list. Click the Browse button to access the properties of the transmitter equipment. For information on creating transmitter equipment, see "Defining Transmitter Equipment" on page 162.
Feeder length: Enter the feeder length at transmission and reception.
AT332_UMR_E0
Miscellaneous losses: Enter any additional losses at transmission and reception. The value must be positive.
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 in the Network explorer 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 83),
or import data into the table (see "Importing Tables from Text Files" on page 88).
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.
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 gateway.
To place the gateway 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 60.
If you let the pointer rest over the gateway you have placed, Atoll displays its tip
text with its exact coordinates, allowing you to verify that the location is correct.
3. Move the pointer to the site on the map. When the frame appears around the site, indicating it is selected, click to
place the gateway.
1253
16.2.2.8.1
The Name of the station template, the number of Sectors, each with a transmitter, the Hexagon radius, which is the
theoretical radius of the hexagonal area covered by each sector, and the Transmitter type, which defines whether the
transmitter belongs to the current network or to another network.
Under Antennas, you can modify the following:
1st sector mechanical azimuth, from which the azimuth of the other sectors are offset to offer complete coverage
of the area, the Height/ground of the antennas from the ground (which is the height over the DTM; if the transmitter is situated on a building, the height entered must include the height of the building), and the Mechanical
downtilt for the antennas.
Electrical Azimuth, Electrical Downtilt, and Additional electrical downtilt display additional antenna parameters.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
Under Main antenna, you can select the main antenna Model.
Under Number of MIMO Antennas, you can enter the number of antennas used for Transmission and for Reception for MIMO.
Under Path loss matrices, you can modify the following: the Main propagation model, the Main radius, and the Main
resolution, and the Extended propagation model, the Extended radius, and the Extended resolution. For information
on propagation models, see Chapter 4: Radio Calculations and Models.
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.
Transmitter Tab
Active: Select this option to specify whether the transmitter is active. Only active transmitters are taken into consideration during calculations.
Transmission/Reception: This area displays the total losses and the noise figure of the transmitter. Losses and noise
are calculated according to the characteristics of the equipment assigned to the transmitter.
Cell Tab
Power: Modify the cell transmission power over the frame (in dBm).
Frequency band, Reception equipment, Channel configuration, Max number of users, Min C/N, and the AMS
threshold.
Default loads: Enter the default values for DL traffic load, UL traffic load, UL noise rise, Max DL traffic load, and Max
UL traffic load.
Additional interference: Set the DL noise rise and the UL noise rise. For more information on inter-technology interference, see "Modelling Inter-technology Interference" on page 1306.
Neighbours Tab
Max number of neighbours: Set the maximum numbers of Intra-technology and Inter-technology neighbours.
1254
AT332_UMR_E0
16.2.2.8.2
16.2.2.8.3
16.2.2.8.4
16.2.2.8.5
16.2.2.8.6
1255
Quickly create a gateway with the same settings as an original one in order to study the effect of a new gateway on
the coverage and capacity of the network, and
Quickly create an homogeneous network with gateways that have the same characteristics.
If you want to duplicate the gateway without the intra and inter-technology neighbours of its transmitters, select
Duplicate > Without Neighbours.
If you want to duplicate the gateway along with the lists of intra and inter-technology neighbours of its transmitters, select Duplicate > With Outward Neighbours.
To create a duplicate gateway and site, move the pointer over the map to where you would like to place the duplicate. The exact coordinates of the pointers current location are visible in the Status bar.
To place the duplicate gateway on an existing site, move the pointer over the existing site where you would like
to place the duplicate. When the pointer is over the site, the site is automatically selected. The exact coordinates
of the pointers current location are visible in the Status bar.
To place the gateway 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 60.
If you let the pointer rest over the gateway you have placed, Atoll displays tip text
with its exact coordinates, allowing you to verify that the location is correct.
1256
AT332_UMR_E0
) in the Radio Planning toolbar. The Point Analysis window opens and the pointer
changes (
) to represent the receiver. A line appears on the map connecting the selected transmitter and the
receiver. You can move the receiver on the map (see "Moving the Receiver on the Map" on page 203).
3. Select the Profile view. The Profile view displays the profile between the transmitter and the receiver with the terrain
and clutter heights.
You can select a different transmitter.
Displays data,
including
received signal,
shadowing
margin, cell
edge coverage
probability,
propagation
model used,
and transmitter-receiver
distance.
Fresnel ellipsoid
Line of sight
The received signal strength from the selected transmitter for the cell with the highest reference signal power
The propagation model used
The shadowing margin and the indoor loss (if selected)
The distance between the transmitter and the receiver.
4. If needed, select an other transmitter from the list. You can click the Properties button (
properties.
5. Click the Options button (
) to display the Calculation Options dialog box and change the following:
Change the X and Y coordinates to change the current position of the receiver.
Select the Shadowing taken into account check box and enter a Cell edge coverage probability. For more information, see "Taking Shadowing into Account in Point Analyses" on page 204.
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. Indoor losses are defined per frequency per
clutter class. For more information, see "Taking Indoor Losses into Account" on page 203.
6. In the Profile view toolbar, you can use the following tools:
) to view the geographic profile between the transmitter and the receiver.
) again to view the radio signal path between the transmitter and the
Click the Detailed Report button ( ) to display a text document with details on the displayed profile analysis.
The detailed report is only available for the Standard Propagation Model.
1257
) to copy the content of the view and paste it as a graphic into a graphic editing or word-
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 gateways
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.
The table you copy 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 83.
Importing data: If you have gateway 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 gateways 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 and Spreadsheets" on page 86. For information on importing table data, see "Importing Tables from Text Files" on page 88.
1258
AT332_UMR_E0
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 in the label will make it harder to distinguish the information you are looking for. For
information on defining the label, see "Associating a Label to an Object" on page 53.
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 "Associating a Tip Text to an Object" on page 54.
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 transmitters. 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 "Setting the Display Type" on page 52.
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 (
same site with the same azimuth, you can differentiate them by selecting different symbols for each (
For information on defining the transmitter symbol, see "Setting the Display Type" on page 52.
and
).
1259
General Tab
Name: Specify the name of the repeater. By default, repeaters are named "SiteX_Y_RepZ" where "X" is the donor site
number, "Y" the donor transmitter number, and "Z" a number assigned to the repeater when it was created.
If the donor is another repeater, then "RepZ" is preceded by "RepB_" where "B" identifies
the donor repeater.
Donor: The donor of a repeater can be a transmitter or another repeater. Click the Browse button to open the donor
Properties dialog box.
Site: Specify the site on which the repeater is located. Click the Browse button to open the site Properties dialog box.
Shared antenna: Specify the identifier (coverage side) of the transmitters and repeaters that are located at the same
site or on sites with the same position and that share an antenna. The identifier must be the same for all such transmitters and repeaters. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical
tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters and repeaters defined
as having a shared antenna.
Antenna position: If the repeater is not located exactly on the site, you can specify its location.
Relative to site: Select this option if you want to define the position of the repeater relative to the site itself and
then enter the XY offsets.
Coordinates: Select this option to specify the position of the repeater by its X and Y absolute coordinates.
Equipment: Select an equipment from the list. Click the Browse button to open the equipment Properties dialog box.
Amplifier Gain: Specify a gain for the amplifier. The amplifier gain is used in the link budget to evaluate the repeater
total gain.
Donor-repeater link: Specify the type of link between the donor and the repeater:
Air: Select this option to specify an off-air repeater. 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.
Microwave link: Select this option to specify a microwave link and enter the total Link losses for the link between
the donor transmitter and the repeater
Optical fibre link: Select this option to specify an optical fibre link and enter the total Fibre losses for the link
between the donor transmitter and the repeater.
Antenna: only available if you selected Air under Donor-repeater link:
Model: Select the antenna model from the list. Click the Browse button to access the access properties.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on page 159
Height/ground: Specify the height of the antenna above the ground. This is added to the altitude of the site as
given by the DTM. If the repeater is situated on a building, the height entered must include the height of building.
Mechanical Azimuth and Mechanical Downtilt: Specify additional antenna parameters.
You can click the Calculate button to update the mechanical azimuth and mechanical
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.
Type: Select the type of feeder from the list. Click the Browse button to access the feeder properties.
Length: Enter the Length of the feeder cable at Transmission and at Reception.
1260
Active: Specify whether the repeater is active. Only active repeaters (displayed in red in the Transmitters folder in the
Network explorer) are calculated.
AT332_UMR_E0
Total gain: Specify the total gain in downlink and uplink. You can click Calculate to determine the actual gain in both
directions. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply before
clicking the Calculate button.
In downlink, the total gain is applied to preamble, traffic, and pilot powers.
In uplink, the total gain is applied to each terminal power.
The total gain takes into account losses between the donor transmitter and the repeater, donor characteristics (donor
antenna gain, reception feeder losses), amplifier gain, and coverage characteristics (coverage antenna gain, transmission feeder losses).
Antennas:
Height/ground: Specify the height of the antenna above the ground. This is added to the altitude of the site as
given by the DTM. If the repeater is situated on a building, the height entered must include the height of building.
Main antenna:
Model: Select an antenna model from the list. Click the Browse button to access the antenna properties.
Click the Select button to open the Antenna Selection Assistant. This assistant lists all the antennas that match
the currently selected physical antenna and whose minimum and maximum operating frequencies include the
operating frequency of the transmitter. For more information, see "Assigning Antennas to Transmitters" on
page 159
Mechanical Azimuth, Mechanical Downtilt, Electrical Azimuth, Electrical Downtilt, and Additional electrical
downtilt: Specify additional antenna parameters.
Secondary antennas: Select one or more secondary antennas in the Antenna column and enter their Azimuth,
Mechanical downtilt, Additional electrical downtilt, and % Power.
The Additional electrical downtilt can be made accessible through an option in the
Atoll.ini file. For more information, see the Administrator Manual.
For more information on the effect of additional electrical downtilt on antenna
patterns, see the Technical Reference Guide.
For information on working with data tables, see "Data Tables" on page 75.
Feeders:
Type: Select a type of feeder from the list. You can click the Browse button to access the feeder properties.
Length: Enter the length of the feeder cable at Transmission and at Reception.
Losses:
Propagation Tab
Repeaters are taken into account during calculations. Therefore, you must set the propagation parameters. On the
Propagation tab, you can modify 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 4: Radio
Calculations and Models.
1261
):
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.
When the donor is a transmitter, you can see to which station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter. You can hide the
link by clicking it again.
When the donor is a repeater, Atoll displays a spider-type link showing the entire
chain down to the donor transmitter. The same spider-type link is displayed when
you click any of the items belonging to the chain is clicked (i.e., donor transmitter
or any repeater).
1262
AT332_UMR_E0
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.
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 57) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using
the Mouse" on page 58).
Display Resolution
City Centre
5m
1263
City
20 m
County
50 m
State
100 m
Country
A read-only Unique ID is generated when you create a coverage prediction. This ID can
later be found between the <GUID> and </GUID> tags in the following files:
"studies.XML" file created in the installation folder if at least one coverage prediction was saved using the Save as Customised Prediction command.
"<prediction_name>.XML" files (one per prediction) created in the following folder
if coverage predictions were calculated with Display type = "Value intervals":
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}
Receiver height: This parameter displays the height of the receiver defined in the Calculation Parameters tab of the
Network Settings Properties dialog box.
Comments: Specify an optional description of comment for the prediction.
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 99. The Group By and Sort buttons are not available when making a so-called
"global" coverage prediction (e.g., signal level coverage prediction).
If you create a coverage prediction from the context menu of the Predictions folder, you
can select the sites using the Group By, Sort, and Filter buttons under Display configuration. However, if you create a coverage prediction from the context menu of the Transmitters folder, only the Filter button is available, because, by creating a coverage prediction
directly from the Transmitters folder, you have effectively already selected the target
sites.
Conditions Tab
The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each
pixel.
At the top of the Conditions tab, you can set the range to be considered for the current prediction.
Server: Select one of the following:
Shadowing taken into account: Select this option to consider shadowing in the prediction. When you select this
option, you can change the Cell edge coverage probability.
Indoor coverage: Select this option to consider indoor losses. Indoor losses are defined per frequency per clutter class.
Channel: Select a channel or carry out the prediction for the "Best" channel of a frequency band or of all frequency
bands. For any transmitter, the best channel is the one whose cell has the highest power.
Display Tab
On the Display tab, you can modify how the results of the coverage prediction will be displayed.
1264
AT332_UMR_E0
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.
16.2.7.2.1
2. Specify the propagation parameters as explained in "Assigning Propagation Parameters" on page 187.
3. 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 dialog box appears.
The Prediction Types dialog box lists the coverage prediction types available. They are divided into Standard Predictions, supplied with Atoll, and Customised Predictions. Unless you have already created some customised predictions, the Customised Predictions list will be empty.
4. Select Coverage by Signal Level (DL) and click OK. A coverage prediction properties dialog box appears.
5. Configure the parameters in the Properties dialog box as described in "LPWA Prediction Properties" on page 1263.
6. 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.
1265
OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the
Calculate button (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
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 in the Network explorer. 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 (
16.2.7.2.2
).
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
16.2.7.2.3
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window
16.2.7.2.4
1266
AT332_UMR_E0
4. 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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
16.2.7.3.1
Highest bearer
Lowest bearer
Throughput scaling factor
Throughput offset
Body loss
1267
You can create a service or modify an existing service by specifying the following parameters in the General tab of the service
Properties dialog box (some fields depend on the type of service you choose):
Name: Atoll proposes a name for the new service, but you can set a more descriptive name.
Type: You can select either Voice or Data as the service type.
Priority: Enter a priority for this service. "0" is the lowest priority.
Activity factor: The uplink and downlink activity factors are used to determine the probability of activity for users
accessing the service. For Voice services, this parameter is used when working with sector traffic maps and user density traffic maps. For Data services, Atoll distributes the users according to the activity factors when importing user
density traffic maps for all activity statuses.
Highest bearer: Select the highest bearer that the service can use in the uplink and downlink. This is considered as an
upper limit during bearer determination.
Lowest bearer: Select the lowest bearer that the service can use in the uplink and downlink. This is considered as a
lower limit during bearer determination.
Max throughput demand: Enter the highest throughput that the service can demand in the uplink and downlink. This
value is not considered for services UGS as the quality of service.
Min throughput demand: Enter the minimum required throughput that the service should have in order to be available in the uplink and downlink. This value is not considered for BE services.
Average requested throughput: Enter the average requested throughput for uplink and downlink.
Application throughput: Under Application throughput, you can set a Scaling factor between the application
throughput and the MAC (Medium Access Control) throughput and a throughput Offset. These parameters model the
header information and other supplementary data that does not appear at the application level.
The application throughput parameters are used in throughput coverage predictions and for application throughput
calculation.
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 3 dB.
For information on creating or modifying a service, see "Creating Services" on page 247.
Modelling Mobility Types
In LPWA, information about the receiver mobility is required for determining which bearer selection threshold and quality
graph to use from the reception equipment referred to in the terminal or cell. Mobiles used at high speeds and at walking
speeds do not have the same quality characteristics. C/(I+N) requirements for different radio bearers are largely dependent
on mobile speed.
You can create or modify a mobility type by specifying the following parameters in the General tab of the mobility type Properties dialog box:
For information on creating or modifying mobility types, see "Creating Mobility Types" on page 249.
Modelling Terminals
In LPWA, 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.
You can create or modify a terminal by specifying the following parameters in the General tab of the terminal Properties
dialog box:
Model: Select an antenna model from the list of available antennas. If you do not select an antenna for the terminal, Atoll uses an isotropic antenna in calculations.
In case you do not select an antenna, Atoll uses an isotropic antenna, not an omni-directional antenna, in calculations. An isotropic antenna has spherical radiation patterns in the
horizontal as well as vertical planes.
1268
AT332_UMR_E0
Gain: Enter the terminal antenna gain if you have not selected an antenna model in the Model field. If you have
selected an antenna, the Gain field is disabled and shows the gain of the selected antenna.
Diversity support: Select whether the terminal support MIMO or not.
MIMO: Enter the Number of transmission antennas and the Number of reception antennas available in the terminal.
For information on creating or modifying terminals, see "Creating Terminals" on page 254.
16.2.7.3.2
Although, you can also set a value for the Traffic load (UL) (%) column as an indication of cells uplink loads, this parameter is not used in the coverage prediction calculations. The measure of interference in the uplink is given by the uplink
noise rise values. For a definition of the values, see "Cell Properties" on page 1250.
To enter the same values in one column for all cells in the table by copying the contents of
one cell into other cells, you can use the Fill Down and Fill Up commands. For more information on working with tables in Atoll, see "Data Tables" on page 75.
16.2.7.3.3
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately.
1269
OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the
Calculate button (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
16.2.7.3.4
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
16.2.7.3.5
1270
AT332_UMR_E0
transmitter is used to determine the total noise in the uplink. As well, the bearer selection for each pixel according
to the C(I+N) level is performed using the bearer selection thresholds defined in the reception equipment. This
reception equipment is the one defined in the selected terminal for the downlink coverage predictions, and the
one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used
to index the bearer selection threshold graph to use.
You can make Atoll use only the bearers for which selection thresholds are defined in both
the terminals and the cells reception equipment by adding an option in the Atoll.ini file.
For more information, see the Administrator Manual.
For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services"
on page 1267, "Modelling Terminals" on page 1268, "Modelling Mobility Types" on page 1268, and "Defining
LPWA Reception Equipment" on page 1303, respectively.
b. 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. The shadowing margin is based
on the C/I standard deviation.
c. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
4. Click the Display tab. From the Display type list, select display by bearer or modulation.
For information on adjusting the display, see "Setting the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
16.2.7.3.6
1271
c. You can also have the coverage prediction take Indoor coverage into consideration. Indoor losses are defined per
frequency per clutter class.
4. Click the Display tab. For an effective service area prediction, the Display type "Unique" is selected by default. The
coverage prediction will display where a service is available in both downlink and uplink. For information on defining
display properties, see "Setting the Display Properties of Objects" on page 51.
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
16.2.7.3.7
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
Atoll calculates the peak MAC channel throughputs from the information provided in the frame configuration and in the
terminal and mobility properties for the terminal and mobility selected in the coverage prediction. Atoll determines the
bearer at each pixel and multiplies the bearer efficiency by the number of symbols in the frame to determine the peak MAC
channel throughputs.
1272
AT332_UMR_E0
The effective MAC throughputs are the peak MAC throughputs reduced by retransmission due to errors, or the Block Error
Rate (BLER). Atoll uses the block error rate graphs of the reception equipment defined in the selected terminal for downlink
or the reception equipment of the cell of the serving transmitter for uplink.
The application throughput is the effective MAC throughput reduced by the overheads of the different layers between the
MAC and the Application layers.
The cell capacity display types let you calculate and display the throughputs available on each pixel of the coverage area taking
into account the maximum traffic load limits set for each cell. In other words, the cell capacity is equal to channel throughput
when the maximum traffic load is set to 100%, and is equal to a throughput limited by the maximum allowed traffic loads
otherwise. Cell capacities are, therefore, channel throughputs scaled down to respect the maximum traffic load limits.
The per-user throughput in downlink is calculated by dividing the downlink cell capacity by the number of downlink users of
the serving cell. In uplink, the per-user throughput is either the allocated bandwidth throughput or the uplink cell capacity
divided by the number of uplink users of the serving cell, whichever it smaller.
For more information on throughput calculation, see the Technical Reference Guide. For more information on the Global
Parameters, see "Network Settings" on page 1301.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
16.2.7.3.8
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 (
The progress of the calculation, as well as any error messages, is displayed in the Events viewer.
1273
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
16.2.7.4.1
16.2.7.4.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.
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 16.3).
16.2.7.4.3
1274
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 91.
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 "Geographic Export Zone" on page 68.
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 210.
AT332_UMR_E0
16.2.7.5.1
) on the Radio Planning toolbar. The Point Analysis window opens and the pointer
The signal levels or C/N (depending on the selection made from the Display list) from different transmitters (the
colour of the bar corresponds to the colour of the transmitter on the map).
The C/N thresholds: The empty portion of the bar indicates signal levels below the C/N thresholds.
The availability of coverage and service in downlink and uplink.
If there is at least one successful connection, double-clicking the icons in the right-hand frame opens a dialog box with
additional information about the best server:
Edit the X and Y coordinates to change the present position of the receiver.
ii. Select the Shadowing taken into account check box and enter a Cell edge coverage probability.
iii. Select the Indoor coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class.
iv. Click OK.
7. 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.
8. In the Reception view toolbar, you can use the following tools:
Click Report (
Click Copy (
programme.
) to generate a report that contains the information from the point analysis window.
Click Print (
) to print the content of the view.
Click Centre on Map ( ) to centre the map window on the receiver.
) to copy the content of the view and paste it as a graphic into a graphic editing or word-processing
1275
You can display a point analysis that uses the settings from an existing prediction by
right-clicking the prediction in the Network explorer and selecting Open Point Analysis
from the context menu.
16.2.7.5.2
Analysing Interference
In Atoll, you can study the interferers of a transmitter using the Point Analysis tool. The Interference view gives you information on interference received on any downlink channel on any point on the map. The analysis is provided for a user-definable
probe receiver which has a terminal, a mobility, and a service. The downlink and uplink load conditions can be taken from the
Cells table.
To make an interference analysis:
1. Click the Point Analysis button (
changes (
) on the Radio Planning toolbar. The Point Analysis window opens and the pointer
For the best server: Name, received signal level, and C/(I+N).
For the total noise (I+N): The values of each component, i.e., I, N, and the downlink inter-technology noise rise.
For each interferer: The effective interference and the various interference reduction factors.
5. Select Inter-technology interference to display interference from other technologies. The Interference bar graph displays the interference received from each inter-technology interferer. Disable Inter-technology interference to display intra-technology interference only.
6. Select the channel on which you want to study the interference from the Display list.
7. If you are analysing interferences to verify a coverage prediction, you can recreate the conditions of the coverage prediction by specifying the parameters of the study:
a. If necessary, select a layer filter for the serving cells from the Layer list.
a. Select the same Terminal, Mobility, and Service studied in the coverage prediction.
b. In the Reception view toolbar, click Options (
i.
Edit the X and Y coordinates to change the present position of the receiver.
ii. Select the Shadowing taken into account check box and enter a Cell edge coverage probability.
iii. Select the Indoor coverage check box to add indoor losses. Indoor losses are defined per frequency per clutter
class.
c. Click OK.
8. 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.
9. In the Interference view toolbar, you can use the following tools:
Click the Report button ( ) to generate a report that contains the information from the Point Analysis window.
The Analysis Report dialog box opens.
1276
) to copy the content of the view and paste it as a graphic into a graphic editing or word-
AT332_UMR_E0
You can display a point analysis that uses the settings from an existing prediction by
right-clicking the prediction in the Network explorer and selecting Point Analysis from
the context menu.
Intersection: This display shows the area where both coverage predictions overlap (for example, pixels covered by
both predictions are displayed in red).
Merge: This display shows the area that is covered by either of the coverage predictions (for example, pixels covered
by at least one of the 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).
Value Difference: This display shows the dB difference between any two coverage predictions by signal level. This display option will not be available if the coverage predictions were calculated using different resolutions.
1277
Figure 16.5: Signal level coverage prediction of network with new gateway
Now you can compare the two predictions.
To compare two predictions:
1. Right-click one of the two predictions, select Compare with and, from the menu that opens, select the prediction you
want to compare with the first. The Comparison Properties dialog box appears.
2. 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 names and
resolutions.
3. Click the Display tab and choose how you want the results of the comparison to be displayed among:
1278
Intersection
Merge
Union
Difference
AT332_UMR_E0
In order to see what changes adding a new gateway made, it is recommended to choose Difference.
4. Click OK to create the comparison. The comparison in Figure 16.6, shows the area covered only by the new gateway.
1279
Intersection
Merge
Union
Difference
In order to see what changes modifying the antenna tilt made, choose Union. This mode displays 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, is immediately clear.
4. Click OK to create the comparison. The comparison in Figure 16.9, shows the increase in coverage due at the change
in antenna tilt.
1280
AT332_UMR_E0
16.2.7.7.1
16.2.7.7.2
Calculate: Click Calculate to save the subscriber analysis and calculate it immediately.
OK: Click OK to save the subscriber analysis without calculating it. You can calculate it later by opening the subscriber analysis properties and clicking the Calculate button.
Once Atoll has finished calculating the subscriber analysis, the results are displayed in the map window. You can also access
the analysis results in a table format. For more information, see "Viewing Subscriber Analysis Results" on page 1281.
You can also organise subscriber analyses in folders under the Multi-point Analysis folder by creating folders under the Multipoint Analysis folder in the Network explorer. Folders may contain one or more subscriber analyses items. You can move
subscriber analyses items from one folder to another and rename folders.
16.2.7.7.3
1281
Activity status: The assigned activity status. It can be Active DL, Active UL, Active DL+UL, or Inactive.
Clutter class: The code of the clutter class where the subscriber is located.
Indoor: This field indicates whether indoor losses have been added or not.
Best server: The best server of the subscriber.
Serving cell: The serving cell of the serving transmitter of the subscriber.
Azimuth: The orientation of the subscribers terminal antenna in the horizontal plane. Azimuth is always considered with respect to the North. Atoll points the subscriber antenna towards its best server.
Downtilt: The orientation of the subscribers terminal antenna in the vertical plane. Mechanical downtilt is positive when it is downwards and negative when upwards. Atoll points the subscriber antenna towards its best
server.
Path loss (dB): The path loss from the best server calculated for the subscriber.
Received power (DL) (dBm): The signal level received at the subscriber location in the downlink.
C/(I+N) (DL) (dB): The C/(I+N) at the subscriber location in the downlink.
Total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the subscriber location in the
downlink.
Bearer (DL): The highest bearer available for the C/(I+N) level at the subscriber location in the downlink.
BLER (DL): The Block Error Rate read from the subscriber terminals reception equipment for the C/(I+N) level at
the subscriber location in the downlink.
Diversity mode (DL): The diversity mode supported by the cell in downlink.
Peak MAC channel throughput (DL) (kbps): The maximum MAC channel throughput attainable using the highest
bearer available at the subscriber location in the downlink.
Effective MAC channel throughput (DL) (kbps): The effective MAC channel throughput attainable using the
highest bearer available at the subscriber location in the downlink. It is calculated from the peak MAC throughput
and the BLER.
Application channel throughput (DL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
Received power (UL) (dBm): The signal level received at the serving transmitter from the subscriber terminal in
the uplink.
C/(I+N) (UL) (dB): The C/(I+N) at the serving transmitter of the subscriber in the uplink.
Total noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the serving transmitter of the
subscriber in the uplink.
Bearer (UL): The highest bearer available for the C/(I+N) level at the serving transmitter of the subscriber in the
uplink.
BLER (UL): The Block Error Rate read from the serving cells reception equipment for the C/(I+N) level at the
serving transmitter of the subscriber in the uplink.
Diversity mode (UL): The diversity mode supported by the cell or permutation zone in uplink.
Transmission power (UL) (dBm): The transmission power of the subscriber terminal after power control in the
uplink.
Peak MAC channel throughput (UL) (kbps): The maximum MAC channel throughput attainable using the highest
bearer available at subscriber location in the uplink.
Effective MAC channel throughput (UL) (kbps): The effective MAC channel throughput attainable using the
highest bearer available at the subscriber location in the uplink. It is calculated from the peak MAC throughput
and the BLER.
Application channel throughput (UL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
1282
AT332_UMR_E0
Figure 16.10: LPWA handover area between reference cell and potential neighbour
When Use coverage conditions is not selected, the defined Distance is used to allocate neighbours to a reference
transmitter.
When Use coverage conditions is selected, click Define to open the Coverage Conditions dialog box:
Resolution: Enter the resolution to be used to calculate cells coverage areas during automatic neighbour allocation.
Global C/N threshold: Select this check box to set a global value for the C/N threshold. If you set a global value
here, Atoll will use this value or the C/N threshold value defined for each cell, whichever is higher. The signal level
threshold (in dBm) is calculated for each cell from its C/N threshold (in dB) considering the channel bandwidth of
the cell and using the terminal that has the highest difference between its gain and losses so that the most number
of potential neighbours can be processed.
Handover start: Enter the margin, with respect to the best server coverage area of the reference cell (cell A), from
which the handover process starts.
Handover end: Enter the margin, with respect to the best server coverage area of the reference cell (cell A), at
which the handover process ends. The value entered for the Handover end must be greater than the value for the
Handover start. The higher the value entered for the Handover end, the longer the list of potential neighbours.
The area between the Handover start and the Handover end constitutes the area within which Atoll will search
for neighbours.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this option to take indoor losses into account in calculations. Indoor losses are defined
per frequency per clutter class.
Co-site cells as neighbours: When selected, the cells located on the same site as the reference cell are automatically
considered as neighbours. A cell with no antenna cannot be considered as a co-site neighbour.
Adjacent cells as neighbours (Intra-carrier Neighbours tab only): When selected, the cells that are adjacent to the reference cell are automatically considered as neighbours. A cell is considered adjacent if there is at least one pixel in the
reference cells coverage area where the potential neighbour cell is the best server, or where the potential neighbour
cell is the second best server respecting the handover end.
Symmetric relations: Select this option if you want the neighbour relations to be reciprocal, which means that any
reference transmitter/cell is a potential neighbour of all the cells that are its neighbours.
Exceptional pairs: Select this option to force the neighbour relations defined in the Intra-technology Exceptional pairs
table. For information on exceptional pairs, see "Defining Exceptional Pairs" on page 223.
1283
Description
When
Distance
Coverage
Co-Site
Adjacent
Symmetry
Exceptional Pair
Exceptional pairs
is selected
Existing
LPWA Coverage
LPWA Server Counter
You can also create the following objectives from the context menu of Objectives in the left pane of the Objectives tab:
1284
AT332_UMR_E0
Custom Coverage
You define the optimisation objectives using the Objectives tab of the ACP Setup dialog box. For more information on setting
objective parameters, see "Setting Objective Parameters" on page 1329.
Signal Level
C
Overlap
Server Counter
1st-Nth
Coverage by Signal Level (DL): ACP evaluates coverages by signal level based on the parameters used to calculate
the selected "Coverage by Signal Level (DL)" prediction in Atoll. Only the coverage predictions displaying a "Best
Signal Level" per pixel can be accessed by the ACP.
Manual configuration: When this option is selected, you can Enable shadowing margin and define a Cell edge
coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information
available, default values are used.
C: To define how ACP will evaluate coverage by C, you can base prediction settings on:
Effective Signal Analysis (DL): ACP evaluates coverages by C based on the parameters used to calculate the
selected "Effective Signal Analysis (DL)" prediction in Atoll. Only the coverage predictions displaying a "Signal
Level" per pixel can be accessed by the ACP.
Manual configuration: When this option is selected, you can Enable shadowing margin and define a Cell edge
coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information
available, default values are used. Additionally, you can specify Service and Terminal that will be used during the
calculation of C through gain and losses (which means the service body loss, the gain and loss of the terminal
antenna, and the terminal noise factor).
Overlap / 1st-Nth / Server Counter: To define how ACP will evaluate coverage by overlapping zones or by 1st-Nth
difference.
Overlap: You can base prediction settings on:
Overlapping Zones (DL): ACP evaluates coverages by overlapping based on the parameters used to calculate
the selected "Overlapping Zones (DL)" prediction in Atoll. Only the coverage predictions displaying a "Number
of Servers" per pixel can be accessed by the ACP.
Manual configuration: When this option is selected, you can set a Minimum signal level and a Threshold
margin.
Overlapping Zones (DL): ACP evaluates coverages by overlapping based on the parameters used to calculate
the selected "Overlapping Zones (DL)" prediction in Atoll. Since there is no Atoll prediction type equivalent to
ACP LPWA 1st-Nth Difference objective, the parameters recovered by ACP from the selected Atoll prediction
are limited to the minimum signal level and the shading. The number of servers must always be specified manually in Number of servers.
Manual configuration: When this option is selected, specify a Minimum signal level and the Number of servers.
In both cases, the Number of servers value that you specify determines "Nth" in the LPWA 1st-Nth Difference
objective. For instance, if you set Number of servers to 4, then the "1st-Nth Difference" quality parameter will
1285
be automatically selected by default in the Quality column of the LPWA 1st-Nth Difference properties. The
allowed values for Number of servers range from 3 to 100, with only one value available per technology. The
"1st-2nd Difference" quality parameter (based on Number of servers set to 2) is provided by default.
Server Counter: You can base prediction settings on:
Overlapping Zones (DL): ACP evaluates coverages by overlapping based on the absolute number of servers respecting the Minimum signal level constraint.
Manual configuration: When this option is selected, specify a Minimum signal level.
Signal Level
Overlap
1st-Nth
N/A
Server Counter
(1) For more information, see "Making a Coverage Prediction by Signal Level" on page 1266.
(2) For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 1266.
Making these predictions 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 predictions 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 predictions produced by ACP, it is recommended to:
Check the results with a different Atoll coverage prediction, such as the overlapping zones prediction.
ACP predictions are generated using the entire set of proposed changes. They do not take into account the change
subset defined in the Change Details tab.
ACP supports optimisation for transmitters belonging to different frequency bands, with predictions provided separately for each frequency band. However multi-carrier optimisation is not supported in LPWA (case of carriers within
same transmitters belonging to different frequency bands).
Even after committing the optimisation results, differences can remain between the ACP predictions and the predictions resulting from Atoll coverage predictions.
For each network quality coverage prediction, ACP offers a prediction showing the initial network state, the final network
state, and a prediction showing the changes between the initial and final state.
1286
AT332_UMR_E0
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 networks, a
cell can be identified by its BSID (6-byte MAC address).
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 with 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:
1. In the Network explorer, right-click the Drive Test Data folder and select Import from the context menu. The Open
dialog box appears.
2. Select the file or files you want to open. You can import one or several files.
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.
3. Click Open. The Import of Measurement Files dialog box appears.
Files with the extension PLN, as well as some FMT files (created with old versions of TEMS)
are imported directly into Atoll; you will not be asked to define the data structure using
the Import of Measurement Files dialog box.
4. 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 dialog box. If you do not have
an import configuration, continue with step 5.
a. Under Import configuration, select an import configuration from the Configuration list.
b. Continue with step 8.
1287
When importing a drive test data path file, existing configurations are available in
the Files of type list of the Open dialog box, 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.
5. 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:
If you have correctly entered the information under File on the Setup tab, and the
necessary values in the Drive Test Data Setup dialog box, Atoll should recognise 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>". Columns marked with
"<Ignore>" will not be imported.
The data in the file must be structured so that the column identifying the BSID is
placed before the data columns for each cell. Otherwise Atoll will not be able to
properly import the file.
7. 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 dialog box appears.
b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atoll installation folder. In
case you cannot write into that folder, you can click Browse to choose a different location.
c. Enter a Configuration name and an Extension of the files that this import configuration will describe (for example,
"*.txt").
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 can select this
import configuration from the Import configuration list.
1288
AT332_UMR_E0
You do not have to complete the import procedure to save the import configuration and have it available for future use.
When importing a 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 dialog box.
You can delete an existing import configuration by selecting the import configuration file under Import configuration and clicking the Delete button.
8. Click Import, if you are only importing a single file, or Import all, if you are importing more than one file. The drive test
data is imported into the current Atoll document.
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, the Shadings dialog box opens in which you can define the
following display for each single point of the measurement path:
You can, for example, display a signal level in a certain colour, choose a symbol for each transmitter (such as a circle,
triangle, cross) 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 in the Network explorer 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 dialog box and select Save or Load from
the Display Configuration submenu.
1289
"Filtering Measurement Points Along Drive Test Data Paths" on page 1290
"Predicting the Signal Level on Drive Test Data Points" on page 1290
"Creating Coverage Predictions on Drive Test Data Paths" on page 1291
"Displaying Statistics Over a Drive Test Data Path" on page 1292
"Extracting a Field From a Drive Test Data Path for a Transmitter" on page 1292
"Analysing Measurement Variations Along the Path" on page 1293
You can apply a filter on all the drive test data paths in the Drive Test Data folder
by selecting Filter from the context menu of the folder.
If you want to use the measurement points that you permanently deleted, you will
have to import the drive test data path again.
5. Click More to filter out measurement points using an advanced filter. The Filter dialog box appears. For more information on using the Filter dialog box, see "Advanced Data Filtering" on page 101.
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 folder.
1290
AT332_UMR_E0
Figure 16.12: Selecting Measured Signal Levels for which Errors will be Calculated
4. Click OK. A point prediction is created for the selected drive test data path.
5. Right-click the drive test data path and select Calculations > Calculate All the Predictions from the context menu.
If you chose to have Atoll calculate the errors between measured and predicted signal levels, new columns are added to the
drive test data table for the predicted point signal level from the serving cell and the errors between the measured and
predicted values.
Figure 16.13: Drive Test Data Table after Point Signal Level Prediction (with Error Calculations)
New columns are also added for the predicted point signal level from each neighbour cell and the errors between the
predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For
more information on the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 1293.
The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main
matrix. For more information on propagation models, see Chapter 4: Radio Calculations and Models.
1291
On the Conditions tab, you can set the range of the 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 an Overlap 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. Indoor losses are defined per frequency
per clutter class.
3. When you have finished setting the parameters for the coverage prediction, click OK.
You can create other coverage predictions by repeating the procedure from step 1. to step 3. for each new coverage
prediction.
4. When you have finished creating coverage predictions for these drive test data, right-click the drive test data and
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 4: Radio Calculations and
Models).
You can display the information in these new columns in the Drive Test Data analysis tool. For more information on
the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 1293.
16.4.4.5 Extracting a Field From a Drive Test Data Path for a Transmitter
You can extract information for a selected transmitter from a field of a drive test data path. The extracted information is available in a new column in the drive test data table.
To extract a field from a drive test data path:
1. In the Network explorer, expand the Drive Test Data folder, right-click the drive test data from which you want to
extract a field, and select Focus on a Transmitter from the context menu. The Field Selection for a Given Transmitter
dialog box appears.
2. Under On the transmitter, select the transmitter for which you want to extract a field.
3. Under For the fields, select the fields that you want to extract for the selected transmitter.
4. Click OK. Atoll creates a new column in the drive test data path table for the selected transmitter and with the selected
values.
1292
AT332_UMR_E0
Select the check box next to each field you want to display in the Drive Test Data analysis tool.
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.
You can change the display status or the colour of more than one field at the same time by
selecting several fields. 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 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 analysis tool.
4. You can display the data in the drive test data path in the following ways:
The drive test data path appears in the map window as an arrow pointing towards the best server in the same colour
as the transmitter.
5. You can display a secondary 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 dialog box. You select the value to be
displayed from the right-hand list at the top of the Drive Test Data analysis tool. The values are displayed in the colour
defined in the Display Parameters dialog box.
6. You can zoom in on the graph displayed in the Drive Test Data analysis tool in the following ways:
Zoom in or out:
i.
Right-click the Drive Test Data analysis tool. The context menu appears.
Right-click the Drive Test Data analysis tool on one end of the range of data you want to zoom in on. The context menu appears.
1293
1294
AT332_UMR_E0
cated on criteria such as the distance between sectors or overlapping coverage. In addition, you can optimise the settings of
the two networks using the Atoll Automatic Cell Planning (ACP) module.
This section covers the following topics:
Select File > Open or File > New > From an Existing Database.
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.
1295
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 107. 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
"Associating a Tip Text to an Object" on page 54.
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 "Changing the Order of
Layers" on page 51.
When you click the Calculate button, Atoll first 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 and Unlocking Coverage Predictions" on page 207.
1296
AT332_UMR_E0
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 recalculate all path loss matrices before calculating coverage predictions:
1. Click the Force Calculate button (
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.
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.
16.5.2.2.1
16.5.2.2.2
1297
16.5.2.2.3
16.5.2.2.4
16.5.2.2.5
1298
AT332_UMR_E0
When Use coverage conditions is not selected, the defined Distance is used to allocate neighbours to a reference
transmitter.
When Use coverage conditions is selected, click Define for e to open the corresponding Coverage Conditions dialog
box:
Resolution: Enter the resolution to be used to calculate cell coverage areas during automatic neighbour allocation.
Margin: Enter a handover margin.
Shadowing Taken into Account: If selected, enter a Cell edge coverage probability.
Indoor Coverage: Select this option to take indoor losses into account in calculations. Indoor losses are defined
per frequency per clutter class.
Co-site neighbours: Cells located on the same site as the reference transmitter will automatically be considered as
neighbours. A transmitter/cell with no antenna cannot be considered as a co-site neighbour.
Exceptional pairs: Select this option to force the neighbour relations defined in the Inter-technology Exceptional pairs
table. For more information, see "Defining Exceptional Pairs" on page 223.
Description
When
Distance
Coverage
Co-Site
Exceptional Pair
Exceptional pairs
is selected
Existing
1299
Click the Run button to run the optimisation immediately. For information on running the optimisation, see "Running
an Optimisation Setup" on page 1359. For information on the optimisation results, see "Viewing Optimisation Results"
on page 1362.
Click the Create Setup button to save the defined optimisation to be run later.
1300
AT332_UMR_E0
Name: Enter a name for the frequency band. Each LPWA frequency band has a specific channel width. Mentioning
the channel width in the frequency band name is a good approach. This name will appear in other dialog boxes
when you select a frequency band.
Start frequencies (MHz): Enter the downlink and the uplink start frequencies.
Bandwidth (MHz): Enter the bandwidth of the frequency band.
3. When you have finished adding frequency bands, click the Close button (
).
You can also access the properties dialog box of each individual frequency band by double-clicking the left margin of the table
row containing the frequency band.
Min interferer C/N threshold: Minimum requirement for interferers to be considered in calculations. Interfering cells
from which the received carrier-power-to-noise ratio is less than this threshold are discarded.
For example, setting this value to -20 dB means that interfering cells from which the received signals are 100 times
lower than the thermal noise level will be discarded in calculations. The calculation performance of interferencebased coverage predictions can be improved by setting a high value of this threshold.
Height/ground: The receiver height at which the path loss matrices and coverage predictions are calculated.
Default max range: The maximum coverage range of transmitters in the network.
1301
Calculation limitation: In this section, you can enter the Min interferer C/N threshold.
Receiver: In this section, you can enter the receiver Height.
System: In this section, select the Default max range check box if you want to apply a maximum system range
limit, and enter the maximum system range in the text box to the right.
3. Click OK. The global parameters are used during coverage predictions for the entire network.
Radio bearer index: Enter a bearer index. This bearer index is used to identify the bearer in other tables, such as
the bearer selection thresholds and the quality graphs in reception equipment.
Name: Enter a name for the bearer, for example, "16QAM3/4." This name will appear in other dialog boxes and
results.
Modulation: Select a modulation from the list of available modulation types. This column is for information and
display purposes only.
Channel coding rate: Enter the coding rate used by the bearer. This column is for information and display purposes
only.
Bearer efficiency (bits/symbol): Enter the number of useful bits that the bearer can carry in a symbol. This information is used in throughput calculations.
Name: Enter a name for the quality indicator, for example, "BLER" for Block Error Rate. This name will appear in
other dialog boxes and results.
Used for data services: Select this check box to indicate that this quality indicator can be used for data services.
Used for voice services: Select this check box to indicate that this quality indicator can be used for voice services.
1302
AT332_UMR_E0
General: On this tab, you can define the Name of the reception equipment.
Thresholds: On this tab, you can modify the bearer selection thresholds for different mobility types. A bearer is
selected for data transfer at a given pixel if the received carrier-to-interference-and-noise ratio is higher than its
selection threshold. For more information on bearers and mobility types, see "Defining LPWA Radio Bearers" on
page 1302 and "Modelling Mobility Types" on page 1268, respectively.
i.
Click the Selection thresholds button. The C/(I+N) Thresholds (dB) dialog box appears.
Quality Graphs: On this tab, you can modify the quality indicator graphs for different bearers and mobility types.
These graphs depict the performance characteristics of the equipment under different radio conditions. For more
information on bearers, quality indicators, and mobility types, see "Defining LPWA Radio Bearers" on page 1302,
"Defining LPWA Quality Indicators" on page 1302, and "Modelling Mobility Types" on page 1268, respectively.
i.
Click the Quality graph button. The Quality Graph dialog box appears.
Traffic MIMO Gains: On this tab, you can modify the SU-MIMO and STTD/MRC gains for different bearers, mobility
types, BLER values, and numbers of transmission and reception antennas. The MIMO throughput gain is the
increase in channel capacity compared to a SISO system. Diversity gains can be defined for different diversity
modes: STTD/MRC, SU-MIMO, and MU-MIMO. STTD/MRC gain is applied to the C/(I+N) when the diversity mode
is STTD/MRC. SU-MIMO diversity gain is applied to the C/(I+N) when the diversity mode is SU-MIMO. MU-MIMO
diversity gain is applied to the C/(I+N) when the diversity mode is MU-MIMO.
For more information on bearers and mobility types, see "Defining LPWA Radio Bearers" on page 1302 and "Modelling Mobility Types" on page 1268, respectively. For more information on the different MIMO systems, see "Multiple Input Multiple Output (MIMO) Systems" on page 1304.
No MIMO gain (STTD/MRC, SU-MIMO, and MU-MIMO) is applied if the numbers of transmission and reception antennas are both equal to 1.
i.
Click the Max MIMO gain graphs button. The Max MIMO Gain dialog box appears.
1303
4. Click OK. The Properties dialog box closes. The settings are stored.
1304
AT332_UMR_E0
When SU-MIMO improves the channel capacity or throughputs, the C/(I+N) of a user is first determined. Once the C/(I+N) is
known, Atoll calculates the user throughput based on the bearer available at the user location. The obtained user throughput
is then increased according to the SU-MIMO capacity gain and the SU-MIMO gain factor of the user clutter class. The capacity
gains defined in Max SU-MIMO gain graphs are the maximum theoretical capacity gains using SU-MIMO. SU-MIMO requires
rich multipath environment, without which the gain is reduced. In the worst case, there is no gain. Therefore, it is possible to
define an SU-MIMO gain factor per clutter class whose value can vary from 0 to 1 (0 = no gain, 1 = 100% gain). For information
on setting the SU-MIMO gain factor for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on
page 127.
A point analysis (see "Studying the Profile Around a Gateway" on page 1256)
A coverage prediction (see "Studying Signal Level Coverage of a Single Gateway" on page 1265).
Atoll uses the values defined for the model standard deviations per clutter class when calculating the signal level coverage
predictions. Atoll uses the values defined for the C/I standard deviations per clutter class when calculating the interferencebased coverage predictions.
You can display the shadowing margins per clutter class.
1305
Cell edge coverage probability: Enter the probability of coverage at the edge of the cell. The value you enter in
this dialog box is for information only.
Standard deviation: Select the type of standard deviation to be used to calculate the shadowing margin:
Model: The model standard deviation. Atoll will display the shadowing margin of the signal level.
C/I: The C/I standard deviation. Atoll will display the C/I shadowing margin.
Interference received by mobiles on the downlink: Interference can be received by mobiles in a network on the
downlink from external base stations and mobiles in the vicinity.
Downlink-to-downlink interference can 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 (such as , UMTS, CDMA2000). These graphs are then
used for calculating the interference from the external. This interference is taken into account in all downlink interference-based calculations.
Uplink-to-downlink interference can be created by insufficient separation between the uplink frequency used by the
external network and the downlink frequency used by your network. The effect of this interference is modelled in
Atoll using the Inter-technology DL noise rise definable for each cell in the network. This noise rise is taken into
account in all downlink interference-based calculations. For more information on the Inter-technology DL noise rise,
see "Cell Properties" on page 1250.
Interference received by cells on the uplink: Interference can be received by cells of a network on the uplink from in
the vicinity.
Downlink-to-downlink interference can be created by insufficient separation between the downlink frequency used
by the external network and the uplink frequency used by your network. Such interference may also come from coexisting TDD networks.
Uplink-to-downlink interference can be created by the use of same or nearby frequencies for uplink in both networks.
The effect of this interference is modelled in Atoll using the Inter-technology UL noise rise definable for each cell in
the network. For more information on the Inter-technology UL noise rise, see "Cell Properties" on page 1250.
1306
AT332_UMR_E0
IRFs are used by Atoll to calculate the interference from external only if the Atoll document containing the is linked to your
document, which means in co-planning mode. For more information on how to switch to co-planning mode, see "Switching
to Co-planning Mode" on page 1295.
To define the inter-technology IRFs in the victim network:
1. In the Parameters explorer, expand the Radio Network Equipment folder, right-click Inter-technology Interference
Reduction Factors, and select Open Table. The Inter-technology Interference Reduction Factors table appears.
2. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter:
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.
You can link more than one Atoll document with your main document following the procedure described in "Switching to Coplanning Mode" on page 1295. 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 Atoll will calculate interference from all the
external in all the linked documents.
1307
1308
Chapter 17
Automatic Cell
Planning
This chapter provides
information on using
the Atoll ACP to optimise
radio networks.
1310
AT332_UMR_E0
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 transmission or transmitter/cell power. ACP can also be used during the
initial planning stage of a 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 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.
ACP uses user-defined objectives to evaluate the optimisation, as well as to calculate its implementation cost. Once you have
defined the objectives and the network parameters to be optimised, ACP uses an efficient global search algorithm to test
many network configurations and propose the reconfigurations that best meet the objectives. ACP presents the changes
ordered from the most to the least beneficial, allowing phased implementation or implementation of just a subset of the
suggested changes.
In this section, the following are explained:
Antenna electrical tilt: ACP adjusts the electrical tilt by selecting the best antenna from the antenna group assigned
to this transmitter.
Power: The power (transmission power in GSM, pilot power in UMTS, max power or RS EPRE in LTE, preamble power
in WiMAX) is set within a defined value range for each cell or subcell.
When optimising a network that is still in the planning phase, 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. ACP also uses as candidates, transmitters in the Atoll project that have been
planned but are not active. ACP can also automatically create a list of candidate sites, following user-defined parameters.
ACP optimises the network using objectives to evaluate the optimisation, as well as to calculate its implementation cost. Each
objective is defined by a set of rules and a target. A rule is a single quality indicator on a single technology layer fulfilling a
defined threshold. The target defines the required percentage of pixels in the target zone which must fulfil the set of rules in
order for the objective to be met.
In this section, the following are explained:
1311
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, for each zone based on clutter classes, and for each imported zone. Moreover, ACP enables you to define
quality objectives separately for each zone or to use each zone separately when creating candidate sites.
In this section, the following are explained:
"Using the Computation Zone and the Focus Zone" on page 1312
"Using Custom Zones" on page 1313
"Using the Filtering Zone" on page 1313.
1312
AT332_UMR_E0
Based on traffic maps: if you select this option, specify one or more traffic maps and the Extraction resolution
From file: if you select this option, click the Browse button and choose a traffic map.
1313
You can set ACP to not take macro-diversity gains in UMTS 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.
Native models: ACP provides the same prediction results as the original propagation model, by using the Optimised
method. For more information, see "Native Propagation Models" on page 1314.
Non-native models: If the propagation model is not native to Atoll, ACP offers three different methods of antenna
masking. For more information, see "Non-Native Propagation Models" on page 1314.
Power optimisation, site selection (without reconfiguration), and antenna height optimisation are made independently of the method used to determine changes to path loss
attenuation.
Direct calculation: ACP calculates incidence angles by direct calculation using the raster data.
Delegating to the model: ACP calculates incidence angles by delegating the calculation to the propagation model, providing that the propagation model implements the appropriate methods of Atoll's API.
ACP automatically selects which internal method to use for each native propagation model:
1314
Basic: The Basic mode is ACPs internal antenna masking method. Because ACPs Basic masking method is not the
same as the one used to calculate the original path loss matrices, accuracy cannot be guaranteed. ACPs Basic masking
method should deliver acceptable results for any propagation model similar to Atolls Standard Propagation Model.
You can adjust the following parameters when using the Basic mode:
Antenna pattern interpolation: The antenna gain calculation method for deriving the antenna gain from a set of
angles of incidence. You can select either of the following methods:
Native 3D Interpolation method: The method used by Atoll. For more information, see the Technical Reference Guide.
Linear Interpolation method: A simple linear method with optional smoothing.
Direct view: When selected, the angle of incidence will be the direct Tx-Rx angle.
Use clutter height: Specify whether clutter heights should be applied along the profiles between transmitter and
receiver. Clutter heights are either extracted from the clutter height file, or from default clutter heights based on
the clutter class file.
AT332_UMR_E0
Improved: This mode performs antenna masking by delegating the calculation of the angles of incidence to the propagation model. If the propagation model does not implement the appropriate methods of Atolls API, the Improved
mode is not available. You can adjust the following parameter when using the Improved mode:
Antenna pattern interpolation: The antenna gain calculation method for deriving the antenna gain from a set of
angles of incidence. You can select either of the following methods:
Native 3D Interpolation method: The method used by Atoll. For more information, see the Technical Reference Guide.
Linear Interpolation method: A simple linear method with optional smoothing.
Antenna Correction: This mode is only available if the relevant API is implemented in the propagation model. It performs antenna masking by delegating the calculation of the angles of incidence to the propagation model. A specific
antenna pattern interpolation, if performed by the model, will be considered. If the propagation model does not
implement the appropriate methods of Atoll s API, the Antenna Correction mode is not available. You can adjust the
following parameter when using the Antenna Correction mode:
Receiver on top of clutter: Specify whether the receiver should be considered to be on top of the clutter or not.
Antenna pattern interpolation: The antenna gain calculation method for deriving the antenna gain from a set of
angles of incidence. You can select either of the following methods:
Native 3D Interpolation method: The method used by Atoll. For more information on Atolls method for 3D
interpolation, see the Technical Reference Guide.
Linear Interpolation method: A simple linear method with optional smoothing.
Full Path loss: With this method, ACP precalculates all path loss matrices for all combinations of the parameters which
are to be tested. This is a fall-back method for complex propagation models not supported by any other method.
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 is considerable savings in both time and computer resources.
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.
Penetration loss (dB): The loss occurring when the signal enters the object.
Linear loss (dB/m): A linear loss applied for each metre within an object. The loss is applied only after a given number
of metres, 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.
1315
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.
The current Atoll project: You can define certain options using the ACP module and choose to embed them in the current project. Embedding the options in the current project ensures that the document is portable; if you open the Atoll
document on a different computer, you will have the same default ACP settings.
The user-defined ACP.ini: When you define options using the ACP module, you can choose to save them in a userdefined ACP.ini file. Defining the ACP options using the ACP.ini file enables you to use the same settings in different
Atoll documents. Additionally, you can manually define settings directly in the ACP.ini file, especially settings which
can not be defined using the ACP module.
The global ACP.ini: The global ACP.ini file (normally the ACP.ini file found in the Atoll installation directory) contains
all the options that can be set for ACP. Unless the same options have been set in either the current project or the userdefined ACP.ini file, ACP will use the options set in the global ACP.ini to initialise a new ACP setup. Setting options in
the global ACP.ini ensures that all users of Atoll using that machine will be using the same base set of parameters.
Defining ACP options by editing the global ACP.ini file also offers advantages, namely, consistent settings across Atoll
documents and the ability to define settings which can not be set using the ACP module.
For information on the options available in the ACP.ini file, see the Administrator Manual.
In this section, the following are explained:
Embedded: Atoll will store ACP settings in the current Atoll document. Embedding the options in the current project ensures that the document is portable; if you open the Atoll document on a different computer, you will have
the same default ACP settings.
Default User Location: Atoll will store ACP settings in the default location for the user-defined ACP.ini file.
Defining ACP options using the ACP.ini file enables you to use the same settings in different Atoll documents.
Browse: Clicking Browse enables you to select a location to store the ACP.ini file or to select an existing ACP.ini file.
1316
AT332_UMR_E0
Antenna masking method: indicates which antenna masking method is used, "Optimised" for native propagation
models and "Basic," "Improved", "Full Pathloss", or "Antenna Correction" for non-native propagation models.
Additional Parameters: click the Browse button available for non-native propagation models to open the Default
Propagation Model Parameters dialog box. In this dialog box, you can define the following parameters for each
propagation model for which ACP uses the "Basic" or "Improved" method as its default method:
Basic and Improved methods:
Antenna pattern interpolation: Antenna pattern interpolation is the method used to derive the antenna gain
from a set of angles of incidence. You can select either the "Native 3D Interpolation" method or the "Linear
Interpolation" method. When you select the linear interpolation method, you can also define the degree of
smoothing applied.
Direct view: Select this 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.
Use clutter height: Select this check box if you want ACP to apply clutter heights along the profile between the
transmitter and the receiver.
Receiver on top of clutter: Select this check box if you want ACP to consider the receiver on top of the clutter.
5. Click OK.
1317
Optimisation: You can adjust the Calculation Setting slider to define whether you want ACP to provide quicker
results (High Speed), at the expense of precision, or more accurate results (High Precision), at the expense of
speed. You can also select an intermediate Default ratio.
High Speed reduces the number of cells monitored for each pixel, some of which may
only create a bit of interference at first, but can create much more interference after
antenna parameters are changed during optimisation. Select High Precision to avoid
this problem; however more time and computer resources will be required.
Implementation Plan: You can adjust the Low Quality Improvement changes slider to define whether you want
ACP to Keep or Discard low quality improvements. You can also select an intermediate Default ratio.
The total number of changes in the implementation plan (see list on Change Details tab)
will vary according to the position of the Low Quality Improvement changes slider.
Select Keep to make a maximum number of changes including the ones that have little
impact on global quality, or select Discard to make the smallest number changes.
Predictions: You can adjust the Transparency % slider to define a default prediction transparency percentage.
Extensions: You can select the check boxe(s) you want to display the corresponding label(s) on the Optimisation
tab:
Multi-Storey: Select this check box to display the Multi-Storey label in the left pane of the Optimisation tab.
You will then have to click on that label to display the Multi-Storey page in the right pane, select the Enable
Multi-Storey check box, and finally define the parameters you want to optimise reception on all floors of
multiple-storey buildings.
EMF Exposure: Select this check box to display the EMF Exposure label in the left pane of the Optimisation
tab. You will then have to click on that label to display the EMF Exposure page in the right pane, select the
Enable EMF Exposure Calculation check box, and finally define the parameters you want to optimise EMF exposure.
3. Select the Setup Template tab to set options that are normally set in the ACP.ini file for the following categories:
Antenna Masking Method (for more information, see "Defining the Antenna Masking Method" on page 1316)
Optimisation
Objective
Reconfiguration
Multi-Storey
EMF Exposure
For more information on the various options and their possible values, see the Administrator Manual.
4. Select the Storage Directory tab to define the directory to be used by ACP to store precalculated path loss matrices
as well as the path loss matrices for antenna height optimisation and for new site candidates. This directory is also
used to store the matrices of the angles of incidence and other temporary data.
Under Private Directory, enter the name of the directory or click the arrow to the right of the current directory
(
) to navigate to the new directory.
Under Shared Directory, enter the name of the directory shared by several users or click the Browse button beside
the current directory to navigate to the new directory.
When ACP reads a specific path loss or incidence matrix, it first attempts to read it from the Shared Directory. If
the entry does not exist in the Shared Directory, ACP then tries to read the information from the Private Directory.
If ACP can not find the information in the Private Directory, it then calculates the matrix and stores the results in
the Private Directory.
1318
AT332_UMR_E0
ACP never writes directly to the Shared Directory. There should only be one user with
administrator rights who populates this Shared Directory with the results of his Private
Directory. No other user should set the Shared Directory as his Private Directory in order
to avoid concurrent access.
5. Click OK to save your changes.
Click Run if you want to run an optimisation immediately. For information on optimisation results, see "Viewing
Optimisation Results" on page 1362.
Click Create Setup if you want to save the new setup and run an optimisation at a later time.
Partial update: The duplicated ACP setup will have only the data that was changed by ACP during optimisation.
Duplicating ACP-generated data permits you to create a 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.
Click Run if you want to run an optimisation immediately. For information on optimisation results, see "Viewing
Optimisation Results" on page 1362, or
Click Create Setup if you want to save the duplicated setup and run an optimisation at a later time.
1319
17.3.2.1.1
1320
AT332_UMR_E0
Name: You can change the name of the technology layer by clicking it and entering a new name.
Use: You can select which technology 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 technology
layers will be taken into consideration during the optimisation process. If the transmitters and sites in the selected
technology 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 the technology layers here ensures that ACP will take them into consideration. Transmitters and sites in
technology layers which are not selected are treated by 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 technology layer that is optimised is linked (by the Shared
Antenna field in the Atoll Transmitter table) with a transmitter on another technology
layer that is not used in the optimisation, the second transmitter will not appear on the
Reconfiguration tab but any changes to the first transmitter will be applied to the linked
transmitter as well.
Reconfiguration: If you want the technology layer to be taken into consideration for reconfiguration, you can
select the check box in the Reconfiguration column.
If a transmitter on one selected technology layer that is optimised is linked (by the Shared
Antenna field in the Atoll Transmitter table) with a transmitter on another technology
layer that is not reconfigured, the second transmitter will appear on the Reconfiguration
tab but none of its sectors will be reconfigured (except for the electrical tilt, if you are optimising it). It is still possible for you to manually select these transmitters for reconfiguration on the Reconfiguration tab.
Site Selection: If you want the technology layer to be taken into consideration for site selection, you can select the
check box in the Site Selection column. If this check box is cleared, all sites belonging to this technology layer will
be considered as existing sites and you will not be able to deselect them on the Reconfiguration tab.
The following columns give information about the technology layer; they can not be edited:
17.3.2.1.2
1321
Figure 17.4: Setup properties > Optimisation tab > Zones page
4. Evaluation zone: This is a polygon defining the target evaluation zone where the objectives will be computed, i.e.
where the evaluation pixels are distributed. Next to Evaluate on, select Computation (default) to preselect only the
pixels in the computation zone or Focus to preselect only the pixels in the focus zone for reconfiguration. If there is
no focus zone in the project to be optimised, the computation zone is automatically selected.
5. Reconfiguration zone: This is a set of cells defining the area where the optimisation will actually be performed:
Optimize inside zone: Select Focus (default) to optimise only the sectors in the focus zone or Computation to optimise all the sectors in the computation zone.
Smart improve: Select this mode and define a Best Server Threshold if you want ACP to automatically select the
sectors that can be optimised to improve the evaluation zone without degrading the area outside it. ACP locks all
the sectors which can have a significant effect on the area outside the evaluation zone, and therefore protects this
outside area from sector changes inside the evaluation zone. More precisely, a sector located inside the evaluation
zone will only be optimised if it is not a secondary server within a Best Server Threshold from the best server,
when looking at pixels outside the evaluation zone.
6. Zone parameters: Each hot spot defined in the Atoll document is automatically included as a custom zone under Zone
Parameters. For each new custom zone, enter a Name in the row marked with the New Row icon (
) and click the
Browse button to open the Zone Definition dialog box. You can:
Import a file (in SHP, MIF, or TAB format) defining a polygon, a line, or a list of points by selecting From file and
clicking the Browse button.
Use an existing hot spot zone in the Atoll document by selecting From hotspot and selecting the hot spot zone
from the list.
Create a custom zone composed of all areas in the reconfiguration zones that are included in one or more clutter
class by selecting From clutter classes and selecting the check box(es) corresponding to the clutter class(es) you
want to study.
If you have set an option in the ACP.ini file so that ACP only uses clutter classes of one resolution (usually the lower resolution), you can also set an option so that the other clutter
classes are not displayed in the Zone Definition dialog box. For more information on the
ACP.ini file, see the Administrator Manual.
1322
AT332_UMR_E0
Figure 17.5: Setup properties > Optimisation tab > Zones page > Zone Definition dialog box
7. If you want to ignore a zone during optimisation, select the corresponding check box under Ignore Zone.
8. For each zone under Zone Parameters, specify in the Resolution column whether or not the Default resolution (m)
indicated at the top of the Optimisation tab will be used.
Computation zone, Focus zone, Hot spots, and custom zones (polygon or line only):
17.3.2.1.3
Select "Default" to use the Default resolution (m). You can modify the Default resolution (m) to increase the
resolution in the optimisation of a hot spot area. The estimated amount of required memory, displayed to the
right of the Default resolution (m) is updated automatically when the resolution is modified.
Or select "Ignore" if you do not want ACP to create evaluation points in this zone. ACP predictions will not
contain any pixel inside this ignored area (black or transparent colour according to the type of prediction).
Select "Use" and ACP will distribute evaluation points in that zone based on the Default resolution (m).
Or select "Ignore" if you do not want ACP to create evaluation points in this zone. ACP predictions will not
contain any pixel inside this ignored area (black or transparent colour according to the type of prediction).
1323
Figure 17.6: Setup properties > Optimisation tab > Cost Control page
Under Cost Control (see Figure 17.6), 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:
No cost control: If you select this option, ACP will not take cost into consideration when optimising the network.
Maximum cost: If you select this option, you can enter a maximum cost not to be exceeded and define the costs
under Cost Setting.
Quality/Cost trade-off: If you select this option, ACP will find a compromise between cost and quality. You can use
the slider to define whether ACP should put more emphasis on quality (Priority to Quality) or cost (Priority to
Cost).
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.
By default, the cost is only a ratio: defining a cost as "0" means that there is no cost associated with a change; defining a cost as "2" means that this change costs twice as much as another change with a defined cost of "1". You
can, however, define the cost as a monetary value. You can define the monetary value to be used, for example,
yen or dollars, by editing the "Cost: Unit" parameter under Optimisation on the Setup Template tab of the ACP Automatic Cell Planning Properties dialog box. For more information about the ACP - Automatic Cell Planning
Properties dialog box, see "Configuring Default Settings" on page 1318.
In the Site Selection Cost section, under Cost Setting, define the individual costs for each site selection option.
1324
AT332_UMR_E0
Figure 17.7: Setup properties > Optimisation tab > Advanced Cost Control page
Under Maximum number of changes, you can define the maximum number of changes to be made.
No limit: If you select this option, ACP will consider no limit on the number of changes.
Limit to number: If you select this option, enter a value for the maximum number of changes to be made.
Limit to ratio of antennas in computation zone (%): If you select this option, the number of changes ACP will effectively make depends on the value you entered for the maximum number of changes to be made and the ratio of
antennas in the computation zone.
Under Implementation plan, you can use the slider to define whether ACP should put more emphasis on Low ranking
cost importance (i.e. changes with the lowest cost are performed first) or High ranking cost importance.
Defining Site Classes for Cost Control
On the Optimisation tab of the ACP Setup dialog box, 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:
1. Create an ACP setup (or display the properties of an existing ACP setup) and select the Optimisation tab.
2. In the left pane, click Cost Control.
Under Cost Control (see Figure 17.6), 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:
1. Click the arrow beside the Site Classes list and select a site class.
2. Define the individual costs for each reconfiguration option as explained in "Defining Cost Control Parameters" on
page 1323.
To create a site class:
1. Click the New Site Class button (
2. Enter the name for the site class and click OK. The new site class now appears in the list of site classes.
3. Define the individual costs for each reconfiguration option of the new site class as explained in "Defining Cost Control
Parameters" on page 1323.
To delete a site class:
1. Click the arrow beside the Site Classes list and select the site class you want to delete.
2. Click the Delete Site Class button (
site class.
). The selected site class is immediately deleted. You can not delete the "Default"
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.
17.3.2.1.4
1325
Figure 17.8: Setup properties > Optimisation tab > Constraints page
3. To specify a maximum number of active sites, select the Maximum number of active sites check box under Site selection and enter a value.
The number of sites indicated after Currently visible on map corresponds to the
total number of sites displayed on the Reconfiguration > Sites vertical tab when
Current Site Selection and Current Candidate Selection are selected and Display
on is set to "All".
The Maximum number of active sites can be greater than the displayed number
of sites Currently visible on map. For example, other candidate sites can be activated when a New Candidate List is made available from the New Candidate Setup
dialog box.
4. To specify a minimum distance between candidate sites, select Minimum inter-site distance for candidates (m) under
Site selection and enter a distance value (in metres). This constraint is checked for a technology layer, which means
that an LTE site can be near a UMTS site without respecting the specified minimum distance.
You can specify the minimum distance between candidate sites by setting the appropriate
option in the ACP.ini file. For more information, see the Administrator Manual.
17.3.2.1.5
1326
AT332_UMR_E0
Figure 17.9: Setup properties > Optimisation tab > Multi-Storey page
3. Select the Enable Multi-storey check box if you want ACP to optimise reception in multi-storey buildings.
4. Under Vertical Points Distribution, define how ACP will distribute the measurement points it will use to optimise the
reception in multi-storey buildings represented in the clutter height maps:
Distribution zone: Select the zone on which multi-story measurement points are to be distributed. ACP only distribute points in a three-dimensional pattern where there are clutter height maps, but, by selecting a distribution
zone, you can limit calculations to areas where multi-storey reception optimisation is most important, for
example, downtown.
Storey height: Define the height of each storey. ACP will use this height to calculate the receiver height for the
defined number of storeys.
Calculation steps: Define, as a number of storeys, the size of vertical steps between storeys on which ACP distributes measurement points. The resulting receiver heights are calculated using the defined step and storey height
and displayed beside the Storey height.
Ignore buildings smaller than: Define the minimum height (in storeys as defined by the Storey height) of buildings
for ACP to distribute measurement points in three dimensions.
Vertical weight sharing: Select this check box if you want ACP to divide the weight of each measurement point
evenly between all 3D pixels at a given (x, y) location. For example, if a pixel at ground level has a weight of 1 and
there is a total of 5 points (1 point at ground level and 1 point every 3 metres) at that location, each 3D pixel will
have a weight of 0.2.
If the Vertical weight sharing check box is cleared, each measurement point will have the same weight. For example, if a pixel at ground level has a weight of 1 and there are a total of 5 points (1 point at ground level and 1 point
every 3 metres) at that location, the total weight of all measurement points will be five, as opposed to a weight of
one outdoors.
17.3.2.1.6
1327
Figure 17.10: Setup properties > Optimisation tab > EMF Exposure page
Select the Enable EMF exposure calculation check box if you want ACP to optimise EMF exposure.
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 does 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.
Under Distribution of Evaluation Points, define how the evaluation points will be distributed:
Resolution XY (m): Define in metres the horizontal resolution of the evaluation points.
Resolution Z (m): Define in metres the vertical resolution of the evaluation points (only for three-dimensional
EMF exposure analysis).
Building front only: Select the Building front only check box if you only want evaluation points to be distributed on the building faade.
Indoor distance analysis (m): If you want evaluation 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 evaluation points are
distributed inside the building.
Evaluation on zone: Select the zone (computation, focus, or individual hot spot zone) on which evaluation
points will be distributed and on which the EMF exposure will be optimised.
Under Raster and Vector Inputs, set the data that will be used to define the profile of the terrain.
By default, the first entry under Raster and Vector Inputs is "Native clutter classes and clutter heights," the
terrain profile obtained from the geo data in Atoll (the clutter classes and DTM). You can map the clutter classes to ACP propagation classes by clicking the Browse button in the Definition column. In the Clutter Definition
dialog box that opens (see Figure 17.11), you can map each clutter class to a corresponding propagation class
and select the check box of each clutter class that is to be used for EMF evaluation.
Figure 17.11: Setup properties > Optimisation tab > EMF Exposure page > Clutter Definition dialog box
1328
You can add a file describing the terrain by clicking the Browse button in the File column. The file must be an
ArcView vector file (SHP). Once you have selected a file, the Vector File Definition dialog box appears.
AT332_UMR_E0
In the Vector File Definition dialog box, you can define the parameters of the vector file, i.e., the field defining
height, the correspondence between vector class and propagation class, and select which vector class should
be used for EMF evaluation.
Ignore clutter: If you have vector files that fully model the terrain, you can remove the Atoll geo data by selecting
the Ignore clutter check box.
Back up configuration: 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.
Figure 17.12: Setup properties > Optimisation tab > EMF Exposure > Propagation page
4. Under Propagation Class Definition, set the following parameters for each propagation class. If you want to create a
propagation class, enter the parameters in the row marked with the New Row icon (
).
Use diffraction: This option is currently disabled; evaluation points that are not in the line of sight experience infinite diffraction loss. In other words, points that are not in the line of sight do not experience any EMF exposure.
Free space model (worst case): Select the Free space model (worst case) check box if you want ACP to calculate
the worst possible EMF exposure levels under the current conditions. When you select the Free space model
(worst case) check box, ACP treats all objects (i.e., buildings, etc.) as fully transparent and no indoor loss is applied.
In other words, even points which are not in line of sight are calculated as if they were in line of sight.
Calculation radius (m): Define the maximum distance from a transmitter for which its EMF exposure contribution
is calculated.
1329
The default objectives are technology dependent. In each technology, a certain number of objectives are proposed that you
can then modify. You can create objectives and add them to the optimisation setup. For information on creating a new objective, see "Creating Objectives" on page 1334.
For information on the individual technology-dependent objectives, see the technology-specific chapter:
Figure 17.13: Setup properties > Objectives tab > Objectives page
2. In the left pane, under Objectives, click an objective to define the coverage parameters of that objective. For example,
in UMTS select UMTS RSCP Coverage or UMTS EcIo.
Figure 17.14: Setup properties > Objectives tab > Specific Objective page
Name: Name suggested by ACP that you can modify. This name appears in the left pane under Objectives.
Weight: You can set the importance of the objective by defining a weight. Giving the objective a weight of "0"
means that ACP will not consider coverage of this objective in determining the success of the optimisation.
Pixel Weighting: Click the Browse button to open the Pixel Weighting dialog box where you can:
1330
Select the Based on traffic maps option and select a map in the frame below, if any is available.
Select the From file option and click the Browse button to find the map you want.
AT332_UMR_E0
Apply Zone Weighting: Select this check box if you want to apply zone weighting on this objective. Traffic will be
globally scaled according to the weighting defined under Parameters > Zone Weighting (see Figure 17.16 on
page 1332).
Target Zone: Select the zone on which the objective is to be evaluated.
Under Pixel Rules, define the rule or rules that will be used to evaluate the objective. Each row in the table contains one rule. Each rule is an evaluation of a specific quality indicator for a single technology layer and for a
defined zone.
Each quality indicator is technology-dependent. By combining rules, you can create an objective that evaluates
quality indicators on different technology layers within the same technology or, for projects that combine several
radio access technologies, that evaluates quality indicators from different technologies.
In the row with the rule you want to edit, or in the row marked with the New Row icon (
a rule, set the following parameters:
In the first column, select the boolean operator (AND or OR) that will be used to combine the rules.
Technology Layer: In this column, select the technology layer that the rule will be evaluated on.
Quality: In the Quality column, select the quality indicator.
In the following column, select the operator (greater than ">", greater than or equal to ">=", lower than "<",
lower than or equal to "<=", ) that will be used to evaluate the rule in relation to the Threshold.
Threshold: In the Threshold column, enter the threshold to be used to evaluate the rule. Click the Browse
button to open a Thresholds Definition dialog box where you can define a threshold for each zone.
Each pixel can belong to more than one zone. However, for each pixel, the quality is only evaluated according to
the threshold of the zone with the highest priority: first the hot spot, then the focus zone, and finally the computation zone.
Figure 17.15: Case of an objective with a target zone (computation zone) including a hot spot zone
with a highest priority and a different threshold
Progressive thresholds are proposed by default in some quality parameters. You can disable the feature by setting useProgressiveThreshold to 0 in the [ACPCore] section of the
ACP.ini file. For more information, see "Considering Progressive Thresholds in Some Quality Parameters" on page 1333.
Once you have defined more than one rule, you can combine them or change the order in which ACP takes them
into consideration.
You can combine rules by selecting them and clicking the Group button. You can then select a boolean operator (AND or OR) that will be used to combine the rules with other defined rules.
You can change the order in which ACP takes them into consideration by selecting the rule and then clicking
the Up button (
).
Under Target, define the required percentage of pixels in the target zone (after applying any defined weight)
which must fulfil the rule.
Target Zone: Select the target zone on which the objective is to be evaluated. For more information on using
zones with ACP, see "Using Zones with ACP" on page 1312.
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 filter the points on which the objective will be evaluated, click Filter at the bottom of the dialog box.
Click the row marked with the New Row icon (
In the first column, select the boolean operator (AND or OR) that will be used to combine the filter conditions.
Technology Layer: In this column, select the technology layer where measurement points will be evaluated.
Quality: In this column, select the quality indicator.
In the next column, select the operator (greater than ">" or less than "<") that will be used to evaluate the
quality indicator in relation to the Threshold.
1331
Threshold: In this column, enter the threshold to be used to evaluate the quality indicator. Clicking the Browse
button opens a dialog box where you can define which threshold to use for each zone.
When two or more filter conditions are defined, you can combine them or change the priority.
You can combine filter conditions by selecting them and clicking the Group button. You can then select a
boolean operator (AND or OR) 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 then clicking the Up button (
).
Select the check box in the Use column for each zone in the project for which you want to redefine the default
threshold or the weight taken into consideration in the EMF exposure optimisation.
Enter a Maximum Threshold (Vm) for each zone selected in the Use column.
Define a Weight for each zone. Evaluation 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 evaluation point
within this zone is of the same importance as improving the EMF exposure by two evaluation points in a zone with
a weighting of "1".
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 the zone will not be
considered when trying to reach the set objectives.
5. In the left pane, click Zone Weighting under Parameters to set the weight accorded to each defined zone: the computation zone, the focus zone, and any hot spot.
Figure 17.16: Setup properties > Objectives tab > Zone Weighting
With zone weighting, ACP adds an extra weight to all the pixels of a zone. Because one pixel can belong to several
zones, the weight applied to that pixel is the weight of the zone with the highest priority. Zone priority is considered
according to the order defined in the Zone parameters table of the Optimisation tab (see "Defining Zone-related
Parameters" on page 1321).
For example, a pixel can be inside both the focus zone and the computation zone and in a hot spot. For a new setup,
the zone with the highest priority is by default the hot spot zone, then the pixel weight is multiplied by the hot spot
zone weight.
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 the zone will
not be considered when trying to reach the set objectives.
An objective with a weight of "0" can be used to calculate statistics without any
impact on the optimisation.
Zone weighting is used to focus optimisation on the appropriate areas. The assigned weights are used to weight the
traffic and population densities. However, if no traffic maps are available, zone weighting can be used to ensure that
ACP prioritises the optimisation of areas of high traffic or population density.
6. In the left pane under Parameters, click the technology (for example, UMTS).
In the right pane, select the Enable indoor coverage check box if you want all pixels to be considered as indoor.
The indoor loss per clutter class will be applied or, if no clutter classes are available, a default value will be applied.
7. In the left pane under Parameters > Technology (for example UMTS), you can define the quality parameters for that
technology. For information on the quality parameters for each technology, see the technology-specific chapters:
1332
AT332_UMR_E0
17.3.2.2.1
This allows ACP to evaluate the amount of improvement or degradation of each objective within entire value ranges, for
example [-110dBm,-40dBm] for RSCP, and with a variable weighting. That leads ACP to more intelligent decisions on improvements that may cause degradations elsewhere in the network. By default, an ACP objective is evaluated on a "fixed-threshold
basis", on each pixel and in a logical manner, whether the objective is met or not.
When progressive thresholds are supported for a quality parameter, a Progressive Threshold check box can be selected in the
Thresholds Definition dialog box.
Figure 17.17: Setup properties > Objectives tab > Thresholds Definition dialog box
The Progressive Threshold check box can only be selected/cleared if the corresponding technology layer is first on the list
under Pixel Rules. It is greyed otherwise. When progressive thresholds are supported, the following consequences apply:
In the main Objectives table, the quality parameters under Type appear in bold for that objective.
In the objective Pixel Rules table, the values under Threshold appear in bold for all the listed technology layers.
After an optimisation, these values also appear in bold under Input criteria:
on the Statistics tab of the optimisation Properties window
in any report exported in XLS or HTML format via the Export button of the Statistics tab
Also, the list of quality parameters available for a technology layer depends on the position of the technology layer in the Pixel
Rules list:
First position: Any of the quality parameters normally available for a a technology layer appear under Quality.
Any other position: Only compatible quality parameters appear (RSCP/EcIo in UMTS or RSRP/RSRQ/RSCINR in LTE), as
shown in Figure 17.18.
Figure 17.18: Setup properties > Objectives tab > Available Quality Parameters with Progressive Thresholds
Only the OR operator is available (the AND operator has no meaning).
1333
17.3.2.2.2
Creating Objectives
ACP enables you to create and define objectives and add them to your optimisation setup.
To create an objective:
1. Create an ACP setup or display the properties of an existing ACP setup.
2. In the Objectives tab, right-click Objectives in the right pane. The context menu appears.
Figure 17.19: Setup properties > Objectives tab > New objectives
3. Select a new objective from the context menu.
You can create a custom objective by selecting New Custom Coverage Objective. The new objective appears at the
bottom of the Objectives list in the left pane.
The objective types that are available from the context menu come from a default list
which you can modify through an option in the ACP.ini file. For information ACP.ini, see the
Administrator Manual.
4. Click the new objective in the left pane. The corresponding parameters appear in the right pane.
5. Define the parameters, the target, and the pixel rules as explained in "Setting Objective Parameters" on page 1329.
17.3.2.2.3
1334
AT332_UMR_E0
Figure 17.20: Setup properties > Objectives tab > Capacity page (no traffic map defined)
2. Set Traffic Map to "None". The Density (users/km2) column appears in the Services definition table and you can
choose to Scale traffic according to zone weighting.
3. Define the following parameters:
Each service is associated with a list of traffic capture conditions defining the required minimum quality for a cell to
capture the given traffic.
When several technologies are present, one condition is provided per technology. ACP is
designed to perform load balancing across multiple layers and technologies. The
requested traffic will be shared across all the layers available in the allowed technologies
for this service.
4. If you want, you can Scale traffic according to zone weighting. The traffic load will be scaled according to the zone
weightings defined under Parameters.
Defining Traffic Capacity Parameters with One or More Traffic Maps
1. In the left pane, click Capacity. The Capacity page appears in the right pane.
2. Click the Browse button next to Traffic Map to specify one or more traffic maps. The Traffic Map Properties dialog
box appears.
1335
None: no traffic map. See "Defining Traffic Capacity Parameters without a Traffic Map" on page 1335.
Based on traffic maps: when selected, specify one or more traffic maps and the Extraction resolution.
From file: when selected, click the Browse button and choose a traffic map.
3. Select one or more traffic maps, or define a single map From file.
4. Click OK to return to the Capacity page. In the Services definition table, the Scale Factor column replaces the Density
(users/km2) column and the Scale traffic according to zone weighting option is disabled.
Figure 17.22: Setup properties > Objectives tab > Capacity page (with selected traffic map)
5. Define the following parameters:
Each service is associated with a list of traffic capture conditions defining the required minimum quality for a cell to
capture the given traffic. Also, the service/terminal/mobility selection filters the data extracted from the traffic map.
When several technologies are present, one condition is provided per technology. ACP is
designed to perform load balancing across multiple layers and technologies. The
requested traffic will be shared across all the layers available in the allowed technologies
for this service.
17.3.2.2.4
Some sectors are up-tilted, thus increasing the amount of traffic served.
Some sectors are down-tilted, thus decreasing the amount of traffic served.
For instance, when the amount of traffic captured by a UMTS cell increases, the cell load increases both in terms of transmitted downlink power and uplink noise rise, which can lead to:
1336
Call blocking when downlink power exceeds the maximum output power.
AT332_UMR_E0
Figure 17.23: Setup properties > Objectives tab > Load Balancing page
3. Select the Enable load balancing check box.
4. Define the following parameters:
Target Zone: Load balancing will equalize the capacity load for the cells which are located in this zone.
Balance Target (%): Load balancing will try to improve the load balance figure (in %) to reach this target.
Weight: Overall importance of the load balancing objective compared to other objectives (coverage or quality).
Select technology layers to consider: Select under Use the technology layers for which load balancing will be considered when traffic capacity is scaled.
The ACP reconfiguration zone selects the geographical area for the cells to be optimised
(which means the focus zone). Ideally, the target zone used for load balancing should
include these cells and surrounding cells. Surrounding cells, which define a transition zone
(also called a ring), must be controlled by ACP in order to avoid degrading quality indicators
while optimising the reconfiguration zone. For instance, the computation zone can be used
by default as target zone for the Load Balancing objective if the reconfiguration zone is the
focus zone.
17.3.2.2.5
1337
Figure 17.24: Setup properties > Objectives tab > Throughput page
3. Select the Enable throughput optimisation check box.
4. Define the following parameters:
Target Zone: Throughput will be optimised for the cells which are located in this zone.
Weight: Overall importance of the throughput optimisation compared to other objectives (coverage or quality).
Select technology layers to consider: Select under Use the technology layers for which throughput optimisation
will be considered when traffic capacity is scaled.
1338
AT332_UMR_E0
17.3.2.3.1
Figure 17.25: Setup properties > Reconfiguration tab > Cells vertical tab ( optimisation for EMF exposure disabled)
Figure 17.26: Setup properties > Reconfiguration tab > Cells vertical tab (optimisation for EMF exposure enabled)
1339
You can limit the cells displayed on the Reconfiguration tab by selecting the zone they are
located in from the Display on list. This list only affects the displayed cells, not the optimised cells. It is available at the top of Sites, Transmitters, and Cells tabs. Any selection you
make from the Display on list on one tab affects what will be displayed on all other tabs.
2. Select whether you want the power of each selected cell to be set within a defined value range and in the defined
number of steps:
When Power min/max as offset is selected, the Min. Offset and Max. Offset
values are set instead of Min. and Max. for each cell (or each BCCH TRX in GSM).
In LTE, the RS EPRE and the Max Power are mutually dependent, i.e. each is calculated from the other. If you select RS EPRE = "user-defined" (see "Modifying Global
Network Settings" on page 962), ACP optimises the RS EPRE according to the
defined Max Power setting.
You can make the same changes to several cells at once using the Fill Up (Ctrl+U) or Fill Down (Ctrl+D) command. For
more information on these commands, see "Pasting the Same Data into Several Cells" on page 84.
You can sort the content of any column with the Sort Ascending or Sort Descending command from the context menu.
Cells that have been filtered out, either by zone or by clearing the corresponding check
boxes in the table, will not be optimised but they are still present in the network and
hence will still generate interferences.
GSM Cells tab
a. Select the Power check box for the transmission power of each transmitter to be set within a defined minimum
and maximum value and in the defined number of steps. If desired, you can select the Power max/min as offset
check box and define the values for minimum and maximum power as offsets of the current power.
b. Define the power settings for each BCCH TRX.
Use: Select the Use check box corresponding to the BCCH TRX to include it in the optimisation of the transmission power.
Current: The current transmission power for the BCCH TRX.
Min. and Max.: Set a minimum and maximum power to be respected during the optimisation process.
c. Select the Lock cell power for co-site cells check box to ensure that all cells on the same site are assigned the same
cell power. If you are optimising EMF exposure, the cell power of co-site cells is automatically synchronised. In other words, if, in order to meet the EMF exposure objectives, the cell power of one cell must be set to a given level,
then the cell power of all co-site cells will be set accordingly.
Or select the Lock cell power for co-sector cells check box to ensure that all cells on the same sector are assigned
the same cell power. If you are optimising EMF exposure, the cell power of co-sector cells is automatically synchronised. In other words, if, in order to meet the EMF exposure 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 (i.e. if the check box in the Use
column is cleared), when cell power is synchronised, its assigned cell power is forced to
that of the optimised cells.
d. Define the pilot power settings for each cell.
1340
Use: Select the Use check box corresponding to the cell to include it in the optimisation of the pilot power.
AT332_UMR_E0
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).
When "DL powers relative to pilot" is used as a global parameter, the common
power levels associated to the pilot power ("SCH Power" and "Other CCH Power")
are changed accordingly in order to maintain the same ratio during optimisation.
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.
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 1xRTT 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).
1341
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.
d. Define the power settings for each cell.
Use: Select this check box corresponding to the cell to include it in the optimisation of the maximum power.
Current: The current maximum power for the cell.
Min. and Max.: Set the minimum/maximum power to be considered during the optimisation process.
Step (dB): Set the step that ACP should use when attempting to find the optimal maximum power.
17.3.2.3.2
Use: Select this check box corresponding to the cell to include it in the optimisation of the preamble power.
Current: The current preamble power for the cell.
Min. and Max.: Set the minimum/maximum preamble power to be respected during the optimisation process.
Step (dB): Set the step that ACP should use when attempting to find the optimal preamble power.
1342
AT332_UMR_E0
17.3.2.3.3
Figure 17.27: Setup properties > Reconfiguration tab > Transmitters vertical tab
2. 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 only if you are also optimising the electrical tilt. If the electrical tilt is not being optimised, ACP will try to keep the current electrical tilt on the
new antenna.
In a co-planning or multi-RAT project:
the Min and Max values are displayed once per physical antenna. You can set
an option in the ACP.ini file to display these values separately for each linked
transmitter, while keeping in mind that the Min/Max range is unique for all
linked transmitters.
if the Shared Pattern fields of linked transmitters have the same content, then
the reconfigured electrical tilts will be identical for both transmitters.
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 Inter Sector Lock > Azimuth check box corresponding to that 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.
1343
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 (when the Antenna Height check box is selected, the Inter Sector Lock > Height
column should appear on the Reconfiguration > Sites vertical tab).
By default, ACP optimises the antenna height of each sector of a site individually
and it automatically detects whether a sites antennas are co-located (i.e., have the
same coordinates). However, you may want to optimise the antenna height jointly
for all antennas of the same site. If this is the case, you can select the Inter Sector
Lock > Height check box corresponding to that site on the Sites vertical tab.
If you are optimising for EMF exposure, you cannot optimise antenna heights:
Antenna Height check box is greyed on the Transmitters vertical tab
Inter Sector Lock > Height column is not available on the Sites vertical tab
For each selected parameter, the table displays the current setting of each cell located in the selected zone and the
currently defined optimisation parameters.
Select the Show advanced table check box to display the following additional columns on
the Reconfiguration > Transmitters and Reconfiguration > Remotes vertical tabs:
The displayed Antenna Masking Method is derived from the default method used for the
propagation model and it cannot be modified here. For more information, see "ACP and
Antenna Masking" on page 1314.
3. Define the settings to be optimised for each cell.
If you are optimising the antenna azimuth, you can enter either of the following in the Variation column:
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 these
commands, see "Pasting the Same Data into Several Cells" on page 84.
17.3.2.3.4
1344
AT332_UMR_E0
17.3.2.3.5
17.3.2.3.6
1345
9. If you want only transmitters of the imported list to be used on the Reconfiguration tab, select Use Only Tx(s) in list.
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.
10. 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.
11. Click the Import button to import the file and replace the settings in the Reconfiguration tab.
17.3.2.3.7
1346
AT332_UMR_E0
To set the reconfiguration parameters for secondary antennas, remote antennas and repeaters:
1. Create an ACP setup (or display the properties of an existing ACP setup) and select the Reconfiguration > Remotes tab.
Figure 17.29: Setup > Reconfiguration tab > Remotes vertical tab
On the Remotes tab, the Name and Remote Type of each secondary antenna, remote antenna, or repeater is given,
as well as the name of the Donor transmitter and the Site on which the donor transmitter is located. If any entry on
the Remotes tab itself has a secondary antenna, remote antenna, or repeater, the number of is given in the No.
Remotes column.
You can use the No. Remotes column to identify all cascading repeaters, in order to only
optimise the final repeater. Right-click on the No. Remotes column header and select Sort
Ascending or Sort Descending from the context menu; all entries on the Remotes tab will
end up at the top or bottom of the table (depending on the sort you chose). You can then
clear the Use check box for any optimisation you do not want to apply to an entry that has
itself a repeater.
2. 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 remote antenna or repeater.
Electrical tilt: Select the Electrical tilt check box for ACP to select the best electrical tilt from the antenna group
assigned to each selected antenna or repeater within the defined range.
When ACP selects the best antenna type, it will also choose the best electrical tilt from the
antenna group only if you are also optimising the electrical tilt. If the electrical tilt is not
being optimised, ACP will try to keep the current electrical tilt on the new antenna.
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. ACP accepts decimal values for the azimuth however the step must be an
integer.
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.
1347
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. ACP accepts decimal values for the mechanical tilt however the step must be
an integer.
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.
The height of secondary antennas can not be optimised; it is linked to the height of the donor transmitter.
Repeater Amplifier Gain: Select the Repeater Amplifier Gain check box if you want ACP to optimise the repeater
amplifier gain within the defined range and in the defined number of steps.
The table displays, for each parameter selected, both the current settings for each cell in the selected zone and the
currently defined optimisation parameters.
If you want ACP to display more information on each transmitter, you can select the Show
Advanced Table check box. ACP will then display the following columns for each remote
antenna: antenna masking method, propagation model, shared antenna, shared pattern,
site name and status.
The antenna masking method displayed is derived from the default method used for the
propagation model. It cannot be changed here (for more information, see "ACP and
Antenna Masking" on page 1314).
3. Define the settings to be optimised for each secondary antenna, remote antenna, or repeater.
If you 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 84.
Limitation:
If path loss matrices are embedded, all sites with secondary/remote antennas or repeaters
will be locked in site selection. This means that:
This limitation does not apply when path losses are stored externally.
1348
AT332_UMR_E0
17.3.2.4.1
Figure 17.30: Setup > Reconfiguration tab > Sites vertical tab
2. Select the Current Site Selection check box to enable site selection. You can then define how sites will be added or
removed.
3. Select the Current Candidate Selection check box if you want ACP to use deactivated sites in the project as candidates.
Deactivated sites in the project will then appear in the table with the status "Candidate."
4. In the table, define how each site will be treated during site selection:
If you are working on a co-planning or multi-RAT project, a Technology column will appear
after the Site Name column indicating which technology or technologies are used on this
site.
Select the Disable check box for any site on which you want to prevent ACP from making changes (either to
the antenna or to the cell, as defined in the Transmitters and [Technology] Cells tabs).
ii. Select the Inter Sector Lock > Azimuth or Inter Sector Lock > Height check box for any site on which sectors
are locked for azimuth or height, knowing that:
Sectors locked for azimuth: all sectors rotate together preserving angular separations between antennas.
Sectors locked for height: the sectors keep the same height difference when they are modified.
b. Under [Technology] Site Selection, select the Use check box for each site that is to be used in the site selection
process. The status of the sites which are not in Use will not change, e.g. existing sites are not deactivated by ACP.
If you have many sites that you do not want to be affected by site selection, you can select
and disable them using the Advanced section. For more information on the options in the
Advanced section, see "Selecting Sites for Reconfiguration" on page 1354.
c. The status for each site that is in Use is given under Status:
1349
Existing: All sites that are active in the initial network are marked automatically as "Existing." 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: If you selected the Current Candidate Selection check box in step 3., sites with inactive transmitters appear in the list of sites and are marked automatically as "Candidate." ACP will add a candidate site
during the optimisation process if adding the site will improve network quality. If the Sectors Removable
check box is checked, only one or more sectors of the candidate site might be added. You can select "Candidate" for any site you want ACP to consider the site as a "Candidate."
You can also define candidate sites by selecting the New Candidate Selection check box and clicking the Setup
button. For more information on defining candidate sites, see "Creating New Candidate Sites" on page 1350.
d. Select the Sectors Removable check box for each site that can have sectors removed to improve network quality.
e. Select the Site Removable check box for each site that can be removed to improve network quality. The Site Removable check box is unavailable for sites that are marked as "Candidate".
f. If desired, assign the sites that you want (any "Existing" or "Candidate" site) to a Group by selecting a group from
the list in the corresponding row. If a site does not belong to a group, no further constraints are imposed on ACP
during optimisation. If a site belongs to a group, ACP will take the group constraints into account.
If a site group has no sites belonging to it, it is automatically deleted.
i.
In Group column, click the down-arrow and select New from the list. The New Site Group dialog box appears.
ii. Enter a group Name and define the Min and Max number of sites from this group (from 0 to 1000) that must
be considered by ACP during optimisation. If there is no limit that ACP must consider, leave the field blank.
iii. Click OK to create the group and return to the Site Selection tab.
17.3.2.4.2
Zone: Select the zone (computation, focus, or hot spot zone defined on the Optimisation tab) from the list.
Default Station Template: Select the station template that any candidate site ACP adds in the selected zone will
be based on.
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 more
information, see "Setting Station Template Reconfiguration Parameters" on page 1342.
Default Group: Select the group that the candidate site will belong to by default.
Frequency Band: The frequency band of the station template is indicated.
4. Under New Candidate List, define the individual candidate sites. For each candidate site set the following:
1350
AT332_UMR_E0
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: This column appears if you defined a site class under Cost Control on the Optimisation tab. You can
define for each candidate the site class that will be used to determine the cost of implementing this site, or leave
the "Default" site class.
Frequency Band: Frequency band defined for this station template.
5. Select Use multi-band antenna when possible (linked transmitters) to use linked transmitters on candidate sites
whenever possible, that is to say to force the candidate to share physical antennas with an existing site at the same
location.
6. Click the Action button to automatically update the list of new candidates and create candidates using 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 in the current document that have no transmitters. The sites imported are those in
the reconfiguration zones selected on the Optimisation tab.
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 in the Auto Antenna Height Definition dialog box.
Automatic Candidate Positioning: Select Automatic Candidate Positioning to have ACP create a list of candidate
sites according to user-defined rules. For more information, see "Automatically Creating Candidate Sites" on
page 1351.
If you are using ACP on a co-planning or multi-RAT project, you have an additional option. This option enables you to,
for example, upgrade an existing network from one technology to another.
17.3.2.4.3
Import from Existing [Technology] Sites: Select Import from Existing [Technology] Sites to import all the sites
from one technology as candidate sites for the other technology.
You can modify the default 500m inter-candidate distance via the interSiteDist
option in the [ACPAutoCandPosDlg] section of the ACP.ini file.
For areas (polygon zones only, not polylines),you can modify the default 25% ratio
via the minInterSiteDistRatio option in the [ACPAutoCandPosDlg] section of the
ACP.ini file.
To create the list of candidate sites, ACP fills the selected zone with a hexagonal pattern based on the defined inter-candidate
distance. Only nodes within the zone will be used for candidate sites. If the station template on which the candidates are
based is tri-sector, the candidate sites will be placed at the intersection of the hexagons (see Figure 17.31). The inter-candidate distance is then 1.5 times the cell range.
1351
1352
AT332_UMR_E0
If the zone in which the candidate sites are to be created is too small, the node of each hexagon used by ACP to place
candidate sites might fall outside of the zone itself. Therefore, no candidate site will be created. Consequently, automatic candidate positioning is not well suited to small polygons.
It can be useful to use a smaller inter-candidate distance than that used in the network and let ACP only select those
sites which contribute the most to the coverage and quality. However, if the inter-candidate distance is too small, too
many candidate sites will be created, which will slow down ACP due to the high number of path loss matrices that
need to be calculated. It can also cause inconsistency with Atoll coverage predictions because ACP is limited in the
number of sectors monitored by each pixel. Therefore, when using a smaller inter-candidate distance in order to
create more candidate sites, it is recommended to:
Set the Calculation setting to High precision to increase the number of monitored sectors, thereby reducing
potential inconsistency with Atoll coverage predictions (for more information, see "Configuring Default Settings"
on page 1318).
Consider performing a second ACP optimisation on the results of the first one, in order to fine-tune it and suppress
mismatches.
Figure 17.34: Defining new candidate sites > Automatic Candidate Positioning dialog box
4. For each zone, select the Use check box if you want ACP to automatically create candidate sites in that zone.
5. Define an Inter Candidate Distance in metres.
6. If you want to change the default settings ACP will use to place candidate sites, click the button corresponding to each
zone under Design Rule. The Automatic Candidate Positioning: Design Rules dialog box appears (see Figure 17.35).
ACP can automatically place candidate sites either according to forbidden or preferred clutter classes or according to
higher positions within a defined radius.
1353
Figure 17.35: Defining new candidate sites > Automatic Candidate Positioning Design Rules dialog box
Under Clutter classes, define the forbidden and preferred clutter classes. A clutter class can not be selected in
both the Forbidden and Preferred columns.
Forbidden: If you do not want ACP to place a candidate site on a given clutter class, select the check box corresponding to the clutter class under Forbidden. If the hexagonal pattern would place the candidate site on a
forbidden clutter class, ACP will search within the defined Search radius to place the candidate site on a clutter
class that is not forbidden. If no such clutter class can be found within the defined Search radius, no candidate
site will be placed.
Preferred: If you want ACP to try to place a candidate site preferentially on certain clutter classes, select the
check box corresponding to the clutter class under Preferred. Starting from the point defined by the hexagonal
pattern, ACP will search within the defined Search radius to find a preferred clutter class on which to place the
candidate site. If no such clutter class can be found within the defined Search radius, the candidate site will
be placed on the point defined by the hexagonal pattern.
You can not define preferred clutter classes if you have selected the option Select high
points to place candidate sites on a point within the defined Search radius that is higher
than the defined amount.
Search high points: If you select Search high points, ACP will place the sites a strict hexagonal pattern, unless there
is a point within the defined Search radius that will increase the altitude more than the set amount.
7. Under Design rules, define a Search radius as a percentage of the inter-candidate distance. ACP normally places candidate sites in a strict hexagonal pattern. However, ACP can search for a more appropriate site within the Search
radius according to the defined rules. The maximum Search radius is 40% of the inter-candidate distance, in order to
prevent ACP from attempting to place two candidate sites at the same location.
8. Click Apply to save the design rules and close the Automatic Candidate Positioning: Design Rules dialog box.
9. Click Apply to close the Automatic Candidate Positioning dialog box.
Atoll creates the candidate sites according to the defined rules and displays them under New Candidate List in the New Candidate Setup dialog box.
17.3.2.4.4
1354
AT332_UMR_E0
Figure 17.36: Setup > Reconfiguration tab > Sites vertical tab > Advanced section > Global Change
4. Select the Global Change tab.
5. 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 or multi-RAT 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.
6. Select the Set "Use Site Selection" check box and click Apply if you want to use the selected sites. The unused sites
will not be affected by the site addition or removal options.
Antenna Element: An antenna element groups all instances of an antenna, belonging to the same frequency band,
with different electrical tilts.
Physical Antenna: A physical antenna is a multi-band antenna, grouping all antenna elements from different frequency bands which are physically the same antenna.
Antenna Groups (optional): An antenna group is a user-defined subset of the physical antenna enabling you to select
antenna model reconfiguration to be done within this subset. The Antenna Groups vertical tab will only appear on the
Antenna tab of the Setup Properties dialog box if the Antenna Type check box is selected on the Reconfiguration tab.
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 1338.
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.
Antenna group creation is only required if the Antenna Type check box is selected on the
Reconfiguration tab (not selected by default).
"Creating Antenna Elements, Physical Antennas, and Antenna Groups Automatically" on page 1356
"Creating and Grouping Antennas by Pattern" on page 1356
"Grouping Antenna Patterns Automatically" on page 1357
"Defining Multi-band Antennas" on page 1358
"Creating Antenna Groups" on page 1358.
1355
17.3.2.5.1
Make sure to assign the same name to all patterns belonging to the same physical
antenna even when they are on different frequency bands.
To ensure that ACP correctly defines multi-band antennas, it is recommended to
correctly set the minimum and maximum frequency of the antenna pattern in the
Antennas table. If you do not do it in the Antennas table, you can still configure this
in the ACP Setup dialog box.
Minimum and maximum frequency fields are used in ACP to automatically define
the frequency band of the antenna pattern. For more details, refer to the "Antenna
Setup" section in the Technical Reference Guide.
2. For each antenna identified in the Antennas table, enter the same name for all antenna patterns corresponding to
physical antenna that belong to the same group. ACP will automatically group all physical antenna into a new group
with the name given entered in the column.
ACP will now automatically create antenna elements, physical antennas, and antenna groups based on the entries in
the custom fields of the Antennas table of the Atoll document database.
You can create another custom column in the Antennas table to automatically link antenna elements of a multi-band
physical antenna which have the same electrical tilt. You must identify this column using the antenna.etilt.share
option in the [ACPCustomFieldExtraction] section of the ACP.ini file. In the ACP Setup dialog box, this is accomplished
by selecting the check box in the Same Elec. Tilt column on the Physical Antenna tab.
17.3.2.5.2
1356
AT332_UMR_E0
Figure 17.37: Setup > Antenna tab > Patterns vertical tab > Antenna Pattern Table
2. Click the New button to create a 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.
3. Assign antennas to a group to create physical antenna elements or to associate antenna patterns to define a radiation
diagram 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 identified
by this 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 (
).
4. 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 Min. and Max. limits
Atoll must respect for each antenna to be optimised.
By defining custom columns in the Antennas table and setting additional options in the
[ACPAntennaPage] section of the ACP.ini file, you can define AEDT optimisation parameters that ACP will use as default values for the AEDT optimisation parameters in the
Antenna Pattern Table. For more information, see the Administrator Manual.
17.3.2.5.3
1357
4. Click the Build from Expression button to create antenna groups according to the defined regular expression.
17.3.2.5.4
17.3.2.5.5
On the Antenna Groups vertical tab, the "Default" group is always listed on the right side under Antenna Groups. The
"Default" group is created automatically by ACP and contains all the physical antennas.
2. Click the New button to create a group under Antenna Groups. You can change the name of the new group or any
other group by right-clicking the group name under Antenna Groups, selecting Rename from the context menu, and
entering the new name.
You can delete a group by selecting the group under Antenna Groups and clicking the Delete button. You can delete
all groups at once by clicking the Delete All button.
3. 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 identified
by this 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 ( ).
1358
AT332_UMR_E0
General: This tab allows you to change the name of the optimisation results.
Graphs: This tab displays a graph with the iterations on the X axis and the technology-specific optimisation objectives
on the Y axis (see Figure 17.38), as well as the total cost, if you have chosen to calculate it. The values displayed are
indicated with a legend.
Changes: This 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: This tab displays coverage quality predictions of the improvement of the optimisation quality indicator. If
more than one technology layer is being optimised, you can select the technology layer displayed at the top of the tab.
The predictions 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 1329), the ranges and colours
defined in the selected coverage prediction will be used for the quality predictions, unless you have already defined
display defaults for ACP, either by saving an ACP predictions settings as the default (see "Changing the Display Properties of ACP Predictions" on page 1379).
Objectives: This 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: This tab displays predictions indicating EMF exposure improvement performed to that point.
Figure 17.38: Running optimisation > Graphs, Changes, Quality, and Objectives tabs
1359
Figure 17.38: Running optimisation > Graphs, Changes, Quality, and Objectives tabs
1360
AT332_UMR_E0
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, e.g. if you added transmitters or changed some
transmitter settings, the data that optimisation results are based on can be different
from the current Atoll document data. If you run an optimisation based on settings
made before the changes, the changed data will not be taken into account.
ACP normally detects changes in the Atoll document data and can lock a group if it is
impossible to run an optimisation that is consistent with existing data. For example, ACP
can lock a group if you commit optimisation results after path loss recalculation that are
no longer consistent with the data used to run the optimisation.
When this happens you either have to:
Properties: opens the optimisations properties dialog box. You can modify all of the optimisation parameters (for
information on the optimisation parameters, see "Defining Optimisation Parameters" on page 1320).
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: displays the Open dialog box. 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 Configuration dialog box. You can then select
the check boxes corresponding to the optimisation information you want to save. Clicking OK displays the Save As
dialog box where you can name the PRJ file the optimisation settings will be saved in. You can then use this PRJ
file to quickly configure an optimisation.
Saving a configuration is a quick way to save your settings in an external file. You
can then easily create configurations using the same settings as a basis without
having to recreate them.
The calculation and focus zone definitions on the Optimisation tab come from the
current ATL document and cannot be read from a configuration file. They are the
active zones in the ATL document and are loaded in ACP when the setup is created
or after a full ACP setup duplication. See Figure 17.41 on page 1361. These zones
appear as read-only in the Zone Parameters table and cannot be modified
(locked).
Duplicate: displays the Duplicate Options dialog box. Duplicating a setup allows you to create a setup with up-todate data when data from the original setup is no longer valid.
Partial update: partial duplication of the setup which to resynchronise only the data modified by ACP.
1361
Full update: full duplication of the setup to resynchronise all the data of the setup.
Statistics: displays a synthesised view of the optimisation results of the objectives and of the EMF exposure optimisation, if one was made. For more information, see "Statistics Tab" on page 1362.
Sectors: displays a table with the reconfigured cells in green, sites and sectors which have been added or removed,
and the objective coverage quality per cell before and after optimisation. For more information , see "Sectors Tab"
on page 1363.
Graph: displays a graph with the iterations on the X axis and the optimisation objectives (technology-specific
objectives, 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. The values displayed are indicated with a legend. For more information, see "Graph
Tab" on page 1364.
Quality: displays the computation zone with coverage quality predictions before and after optimisation, and for
the EMF exposure optimisation, if one was made. For more information, see "Quality Tab" on page 1366.
Load Balancing: displays a list of all the capacity load values per cell, for the initial and optimised networks. You
can view the cells per zone and per technology layer. For more information, see "Load Balancing Tab" on
page 1367.
Throughput (LTE only): displays a list of all the throughput values per cell, for the initial and optimised networks.
You can view the cells per zone and per technology layer. For more information, see "Throughput Tab" on
page 1367.
Change Details: displays an ordered list of changes recommended by ACP that you can use to analyse the improvements caused by each reconfiguration option. For more information, see "Change Details Tab" on page 1368.
Commit: enables you to commit the selected changes. For more information, see "Commit Tab" on page 1370.
1362
AT332_UMR_E0
Show Change Statistics: change statistics showing the reconfiguration and site selection statistics, including, for multiRAT optimisations, the number of sites where a radio access technology has been added or removed.
Show Detailed Zone Results: detailed quality figures on each zone (hot spot and zone based on selected clutter
classes). Detailed statistics are given only for zones included in the objective target zone.
Show Detailed Multi-Storey Results: change statistics showing the improvement in coverage for zones on which
multi-storey optimisation was performed, if you selected to perform multi-story optimisation.
Show Input: input settings for this optimisation.
You can export the results by clicking the Export button. The Save As dialog box that appears allows you to select the format
in which you want to save the results: XLS, TXT, HTML, or XML.
1363
1364
AT332_UMR_E0
Dark blue: when 2/3 of the defined number of iterations has been reached, which corresponds to the default switch
point between optimisation and tuning phases.
Light blue: when no more improvements can be made prior to the default switch point, corresponding to a flat objective curve. The light blue vertical line indicates the new switch point between optimisation and tuning phases.
Red: if the user pressed the Stop button during the optimisation phase AND before either of the above switch points.
A warning message appears in the Events viewer to indicate that.
To show the values along a curve, click the Show Values button (
) then drag the mouse cursor along the curve and left-click.
Figure 17.45: Optimisation results > Graph tab (with values displayed on a selected point)
1365
The coverage quality predictions are displayed for each quality indicator, on each technology layer, before and after optimisation. They indicate the value of each quality indicator (for example signal level, overlap, etc.) while objective predictions
indicate the coverage status for each objective on each pixel.
Figure 17.46: Optimisation results > Quality tab > Load Balancing Predictions
The predictions 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 1329), the ranges and colours defined in the selected coverage prediction
will be used for the quality predictions, unless you have already defined display defaults for ACP, either by saving ACP prediction settings as the default (see "Changing the Display Properties of ACP Predictions" on page 1379) or by using a configuration
file (see "Configuring Default Settings" on page 1318).
This range can be modified in the Prediction Properties dialog box (see Figure 17.47) accessed through the tool button (
1366
).
AT332_UMR_E0
In addition to the prediction, a histogram is provided for quick evaluation of the improvement seen across the entire range of
values. This histogram displays the statistics within the defined zone if selected. It should be also noted that the statistics are
given using pixel weighting when traffic or density 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.
Load Balancing tab: capacity load statistics can be displayed for all cells, including
cells from other technology layers not considered in the load balancing objective.
Sectors tab: capacity load statistics are displayed only for the cells currently
selected for reconfiguration.
1367
The Throughput tab displays the initial and final throughput predictions and a list of all the per-cell throughput values, before
and after optimisation. You can display predictions per zone and filter cell results per technology layer.
Throughput tab: Throughput statistics can be displayed for all cells, including cells
from other technology layers not considered in the throughput objective.
Sectors tab: Throughput statistics are displayed only for the cells currently selected
for reconfiguration.
1368
AT332_UMR_E0
Selecting a subset of changes to be implemented, e.g. you might find that implementing only 1/3 of the recommended
changes will provide 80% of the benefit. You could then choose to commit only those changes to the Atoll document.
Finding 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 "Commit Tab" on page 1370.
1369
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 Events viewer.
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.
1370
To compare the current optimisation with one of the optimisations in the same setup, select one of the optimisations in the context menu.
To compare the current optimisation with an optimisation from a different setup:
AT332_UMR_E0
i.
Select Others from the context menu. The ACP Optimisation Comparison dialog box appears.
General tab: allows you to change the name of the optimisation results
Statistics tab: displays a synthesised view of the comparison of the two optimisation. The initial and final figures
are given for the objectives, as well as the absolute improvement. These figures are given for the target zone
selected for the objective. Additionally, the variation between the two optimisations is also given. You can see
more detailed information of each optimisation, along with the variation between the two by clicking the links at
the bottom of the Statistics tab:
Show Change Statistics: The change statistics showing the reconfiguration and site selection statistics.
Show Detailed Zone Results: The detailed quality figures on each zone (hot spot and zone based on selected
clutter classes). Detailed statistics are given only for zones included in the objective target zone.
Show Detailed Multi-Storey Results: The change statistics showing the improvement in coverage for zones on
which multi-storey optimisation was performed, if you selected to perform multi-storey optimisation.
Show Input: The input settings of this optimisation.
1371
coverage prediction will be used for ACP quality predictions, unless you have already defined display defaults for ACP, either
by saving an ACP predictions settings as the default or by using a configuration file.
To view the results of the optimisation in the map window:
1. In the Network explorer, expand the ACP - Automatic Cell Planning folder and the folder of the setup containing the
optimisation results you want to view.
2. Right-click the optimisation and select New Prediction from the context menu. The ACP Prediction Types dialog box
appears (see Figure 17.54).
The predictions available in the ACP Prediction Types dialog box are organised by category.
3. Select a prediction category or expand a category and select a prediction type.
4. Click OK to create the predictions. The selected prediction(s) are created and appear in the optimisation folder.
Figure 17.54: ACP Prediction Types and Corresponding Predictions in the Network Explorer
You can display a prediction by selecting the corresponding visibility check box in the optimisations folder. The display properties can be changed for a single prediction or for all predictions. For more information, see "Changing the Display Properties
of ACP Predictions" on page 1379.
Additional predictions can be made available by setting the relevant options in the ACP.ini
file. For more information, see the Administrator Manual.
Once ACP predictions have been calculated, the following can be done:
1372
AT332_UMR_E0
Display values seen at ground level (defined receiver height): Only the values of ground pixels are shown.
Display max. values seen at a given position: When several values are available on a given pixel (1 at ground level +
1 or more at different heights), the maximum value will be shown.
Display values at the given storey: Only the value at the selected storey are shown.
Continuously preview the map: The map is refreshed automatically when a height parameter is changed.
17.6.3.2.1
Load Balancing
These prediction types allow you to analyse the relative cell capacity load compared to the average cell capacity load, before
and after optimisation. Each pixel is assigned the maximum of the load of its serving cell across technology layers. Data is
expressed in dB compared to the average cell capacity load.
A bigger value means overload and a lower value means underload (by default, displayed in green and blue). The dB scale is
the usual one, i.e. 3dB means twice as much load.
The three load balancing predictions can also be displayed on the Quality tab of the optimisation results, via the Load Balancing folder.
1373
17.6.3.2.2
Throughput
Throughput optimisation is available in LTE only. Throughput prediction types appear only
in the following Atoll templates: LTE, 3GPP Multi-RAT, and 3GPP2 Multi-RAT.
These prediction types allow you to analyse the throughput before and after optimisation. Each pixel is assigned the value of
its serving cell per technology layer. These predictions also cover all technology layers.
17.6.3.3.1
1374
AT332_UMR_E0
These prediction types allow you to analyse quality predictions per technology layer, before and after optimisation. They are
identical to the corresponding predictions displayed on the Quality tab of the optimisations Properties dialog box.
If the Enable multi-storey optimisation check box was selected in the Optimisation >
Multi-storey property page before running the optimisation, a Height tab will be available
in the properties window of each of these predictions. For more information, see Figure
17.55 on page 1373.
For technology-specific information on quality analysis predictions, see the following chapters:
17.6.3.3.2
GSM/GPRS/EDGE: see "GSM Quality Analysis Predictions" on page 470 in Chapter 7: GSM/GPRS/EDGE Networks
UMTS HSPA: see "UMTS Quality Analysis Predictions" on page 592 in Chapter 8: UMTS HSPA Networks
CDMA2000: see "CDMA2000 Quality Analysis Predictions" on page 700 in Chapter 9: CDMA2000 Networks.
LTE: see "LTE Quality Analysis Predictions" on page 939 in Chapter 11: LTE Networks.
WiMAX: see "WiMAX Quality Analysis Predictions" on page 1115 in Chapter 14: WiMAX BWA Networks.
Reconfiguration Types: In this folder, there is a separate prediction for each reconfiguration option displaying the
changes to the network: power, antenna pattern, azimuth, and mechanical tilt. The changes are displayed for the best
server zone. The predictions can be displayed individually to display each reconfiguration option separately or
together to display all reconfiguration options.
Sector Selection Types: In this folder, there are predictions to display which sectors or sites have been added or
removed. These predictions are only available if the site selection was activated during optimisation.
Change Order: This prediction displays the order of changes (as displayed on the Change Details tab). You can define
the colours used to display the order of changes by right-clicking the Change Order prediction 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 prediction, you can see where the most important changes to be made to the network are located.
Change of Electrical Tilt, Mechanical Tilt, Azimuth, Height, Power, and Change Cost: These predictions show the variation of a specific 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 prediction is made available even when the change was to the antenna type.
1375
17.6.3.3.3
Figure 17.60: Best Server Analysis prediction types per Technology Layer
These prediction types allow you to analyse cell-related parameters with respect to the best server. The following predictions
are available by default:
Initial/Final Coverage by Transmitter: new ACP setups store the current transmitter colours ("Discrete Values") as
default colours whereas "Full Update" ACP duplicates reload the current transmitter colours. Hence, when a new "Initial/Final Coverage by Transmitter" prediction is created from ACP, the current transmitter colours in Atoll are used.
If a transmitter cannot be found in Atoll (e.g. deleted or filtered) the default colours will be
recovered from the ACP setup and used. If the Reset to Default command is used from the
display properties of an ACP "Initial/Final Coverage by Transmitter" prediction, the coverage picks up the default colours stored in the ACP setup.
17.6.3.3.4
You can create "Initial/Final Coverage by Aerial" predictions by setting showBestServerAerialPrediction in the [ACPNewPredictionDlg] section of the ACP.ini file.
You can also create "Initial/Final Coverage by Layer" predictions (UMTS and LTE) by
setting showBestServerLayerPrediction in the same section of the ACP.ini file.
Figure 17.61: Objective Sector Analysis prediction types per Technology Layer
These prediction types allow you to display a coverage for each objective defined in a technology layer, before and after optimisation. You can view the objective values relative to the defined thresholds on any pixel by letting the pointer rest over the
pixel. The value is then displayed in tip text. The tip text also provides the best server, whose signal is used to calculate the
coverage objectives.
1376
AT332_UMR_E0
17.6.3.3.5
Figure 17.62: Capacity Sector Analysis prediction types per Technology Layer
These prediction types allow you to analyse the following:
Cell load percentages per technology layer, before and after optimisation.
The cell load values in these predictions are also available on the Load Balancing and Sectors tabs.
Cell throughput percentages per technology layer, before and after optimisation.
Throughput optimisation is available in LTE only. The Initial and Final Cell Throughput
prediction types appear only in the following Atoll templates: LTE, 3GPP Multi-RAT, and
3GPP2 Multi-RAT.
The cell throughput values in these predictions are also available on the Throughput and Sectors tabs.
These predictions are also displayed per technology layer on the Quality tab, from the Capacity Predictions section.
17.6.3.3.6
Figure 17.63: Layer Throughput Analysis prediction types per Technology Layer
These prediction types allow you to display the throughput percentage per technology layer (and per layer), before and after
optimisation. Each pixel is assigned the value of its serving cell per technology layer and per layer (small cell, macro, etc.).
1377
17.6.3.4.1
Quality Analysis
These prediction types allow you to analyse EMF exposure values before and after optimisation, the EMF exposure gain, and
the EMF exposure coverage improvement.
17.6.3.4.2
Sector Analysis
These prediction types allow you to analyse the per-sector V/m contribution before and after optimisation, corresponding to
the values available on the Sectors tab, in order to quickly identify the most critical sectors.
1378
AT332_UMR_E0
To compare a prediction with a prediction from a different prediction type or with a prediction from a different optimisation:
1. After creating and inserting the coverage analysis predictions into the folder of the setup containing the optimisation
results as explained in "Viewing Optimisation Results in the Map Window" on page 1371, right-click the prediction you
want to compare. The context menu appears.
2. From the context menu, select Compare With > Others. The ACP Prediction Comparison dialog box appears. By
default, this dialog box displays only the predictions from the same optimisation as the prediction you want to compare.
Show all ACP setups: Select the Show all ACP setups check box if you want to be able to compare with a prediction
from a different optimisation.
Show only predictions of same type: Select the Show only predictions of same type check box if you want to
restrict the predictions displayed to predictions displaying comparable information.
4. Select the prediction with which you want to compare the first one and click OK. ACP creates a new prediction in the
optimisation folder and displays it in the prediction window with the pixels that are displayed on both predictions or
only on a single prediction.
By first defining a display interval of "1" in both predictions and then comparing them,
the resulting comparison prediction will have more meaningful results. For information
on defining display properties, see "Changing the Display Properties of ACP Predictions"
on page 1379.
1379
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 prediction using the slider.
Add to legend: You can display the range of values of the optimisation prediction 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 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 dialog box 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 predictions 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 ACP defaults. You can also use
Reset to Default to return to 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 prediction window. The value on that pixel will
be displayed in tip text.
1380
AT332_UMR_E0
2. Right-click the optimisation results and select Show Histogram from the context menu.
The Histogram window appears with a graph of the area defined by the zone used for the optimisation setup (Setup
> Optimisation tab > Zones > Reconfiguration zone) and a legend table.
You can click a point on the diagram to display the values of the Y-axis against the coverage criterion along the Xaxis. The corresponding cell is highlighted in the legend table.
You can also zoom in the graph by selecting several contiguous cells. Select a cell to return to the default view.
You can copy the graph to the clipboard for use in an external program by clicking Copy ( ).
You can print the graph by clicking Print ( ).
3. Click Histogram (
function.
4. Click Values ( ) to display the covered area values along the Y-axis or Percentage ( ) to display the percentage of
the covered area along the Y-axis.
5. Click a point on the diagram to display the covered area values or the percentage of the covered area along the Y-axis
against the coverage criterion along the X-axis. The corresponding values are highlighted in the table.
6. To specify a custom scale for the Y-axis, enter values in Min Y and Max Y and click OK (
ingly. Click Default ( ) to return to the default scale.
1381
1382
AT332_UMR_E0
Index
Symbols
+MRC in Softer/Soft (CDMA) 725
+MRC in Softer/Soft (UMTS) 613
Numerics
3-D antenna pattern
defining attenuation 156
defining azimuth 156
defining tilt angle 156
importing 155
3GPP multi-RAT
template 34
A
acceptable noise rise margin, defining for EV-DO cells (CDMA) 635
access point
creating (Wi-Fi) 1170
creating with station template (Wi-Fi) 1172
definition (Wi-Fi) 1166
duplicating (Wi-Fi) 1174
ACP
antenna azimuth, reconfiguration 1311, 1343, 1347
antenna height, reconfiguration 1311, 1344, 1348
antenna masking 1314
antenna type, reconfiguration 1311, 1343, 1347
antennas, AEDT 1356
antennas, electrical tilt, setting range 1356
antennas, grouping automatically 1357
antennas, mechanical tilt, setting range 1356
candidates, creating automatically 1351
configuration, loading 1361
configuration, saving 1361
co-planning optimisation process, creating 957, 1132, 1234, 1300
co-planning optimisation process, importing second technology
957, 1133, 1235, 1300
1383
1384
B
backup
configuring 44
recovering a backup 45
base station
assigning equipment (GSM) 280
assigning equipment (UMTS) 515
copying into document (CDMA) 643
copying into document (GSM) 297
copying into document (LTE) 860
copying into document (TD-SCDMA) 753
copying into document (UMTS) 527
copying into document (WiMAX) 1049
creating (LTE) 853
creating (WiMAX) 1042
creating with template (CDMA) 638
creating with template (GSM) 291
creating with template (TD-SCDMA) 747
creating with template (UMTS) 522
creating with template (WiMAX) 1044
definition (CDMA) 630
definition (GSM) 279
definition (LTE) 845
definition (TD-SCDMA) 739
definition (UMTS) 513
definition (WiMAX) 1037
duplicating (GSM) 294
AT332_UMR_E0
C
C/(I+N) level coverage prediction (LTE) 882
C/(I+N) level coverage prediction (WiMAX) 1065
C/I levels coverage prediction (GSM) 431, 434
calculation
defining Min. interferer reception threshold (CDMA) 725
defining Min. interferer reception threshold (TD-SCDMA) 830
defining Min. P-CCPCH RSCP threshold 830
defining Min. pilot RSCP threshold (CDMA) 725
defining Min.P-CCPCH RSCP threshold (TD-SCDMA) 830
min. interferer reception threshold, defining (UMTS) 614
1385
1386
AT332_UMR_E0
creating 204
creating from existing 205
displaying results with tip text (CDMA) 666
displaying results with tip text (GSM) 315
displaying results with tip text (LTE) 894
displaying results with tip text (TD-SCDMA) 780
displaying results with tip text (UMTS) 553
displaying results with tip text (WiMAX) 1071
downlink and uplink traffic channel (TD-SCDMA) 772
downlink total noise (CDMA) 662
downlink total noise (TD-SCDMA) 774
downlink total noise (UMTS) 545
duplicating 205
effective service area (3GPP) 995
effective service area (3GPP2) 1018
effective service area (CDMA) 660
effective service area (LTE) 887
effective service area (TD-SCDMA) 774
effective service area (UMTS) 543
effective service area (WiMAX) 1067
effective signal (LTE) 880
effective signal (WiMAX) 1064
exporting in user configuration 210
exporting results 210
forcing calculation 207
geographic export zone, defining 68
geographic export zone, defining (CDMA) 666
geographic export zone, defining (GSM) 315
geographic export zone, defining (LTE) 894
geographic export zone, defining (TD-SCDMA) 780
1387
D
Data Rate Control, see "DRC"
data tables
1388
adding a field 77
changing column width 79
changing row height 79
copying data 83
deleting a field 78
displaying columns 80
editing 82
exporting data 58, 86
filtering 97
filtering by selection 100
filtering by several criteria 101
find text 85
formatting column headers 79
formatting table columns 79
freezing columns 81
hiding columns 80
importing data 88
moving columns 81
opening 76
opening record properties from table 78
pasting data 83
printing 90
replace text 85
restoring after filtering 103
sorting 97
sorting by one column 98
sorting by several columns 98
unfreezing columns 81
viewing properties 76
XML files, importing from 90
database
archiving all modifications 38
connecting to 36
creating a document from 36
refreshing document 37
working with 35
defining 203
definition (Wi-Fi) 1165
defraction
smoothing vertical antenna pattern 158
display
changing properties 51
defining display type 52
display type, automatic 52
display type, discrete values 52
display type, unique 52
display type, value intervals 52
display coordinate system 40
display resolution (CDMA) 652
display resolution (GSM) 306
display resolution (LTE) 874
display resolution (TD-SCDMA) 761, 764
display resolution (UMTS) 536
Distance Measurement tool 65
diversity
reception (TD-SCDMA) 838
reception (UMTS) 523, 618
AT332_UMR_E0
E
Ec/I0 threshold (UMTS) 248
effective service area coverage prediction (3GPP) 995
effective service area coverage prediction (3GPP2) 1018
effective service area coverage prediction (CDMA) 660
effective service area coverage prediction (LTE) 887
effective service area coverage prediction (TD-SCDMA) 774
effective service area coverage prediction (UMTS) 543
effective service area coverage prediction (WiMAX) 1067
effective signal coverage prediction (LTE) 880
effective signal coverage prediction (WiMAX) 1064
electrical azimuth 153
electrical tilt 153
EMF exposure
ACP, studying with 1315
environment
creating (GSM) 255
modifying (GSM) 255
equipment
creating (LTE) 965
creating (WiMAX) 1140
modifying (LTE) 965
modifying (WiMAX) 1140
Equipment Specifications (GSM) 280
Equipment Specifications (TD-SCDMA) 746
Equipment Specifications (UMTS) 521
Equipment Specifications dialogue (LTE) 637, 854
Equipment Specifications dialogue (UMTS) 515
Equipment Specifications dialogue (WiMAX) 1043
equipment, repeater, see "repeater equipment"
Erceg-Greenstein (SUI) propagation model 182
assigning environment formulas 182
creating environment formula 183
defining default environment formula 182
modifying environment formula 183
taking diffraction into account 182
EV-DO
acceptable noise rise margin, defining (CDMA) 635
active set size on reverse link on terminal (CDMA) 251
BCMCS throughput, defining (CDMA) 635
carrier type, defining globally (CDMA) 724
carrier type, defining in cell (CDMA) 634
carriers, parameters for (CDMA) 635
data rates, available (CDMA) 725
DRC error rate, defining (CDMA) 635
FCH active set size on terminal (CDMA) 251
forward link radio bearer index 727
forward link radio bearer, defining 727
handoff status coverage prediction (CDMA) 665
idle power gain, defining (CDMA) 635
max channel elements per carrier, equipment (CDMA) 631
max rate = f/C/1), defining for mobility (CDMA) 248
maximum number of users per cell, defining (CDMA) 636
maximum power transmitted, defining (CDMA) 635
maximum UL load factor, defining (CDMA) 635
min. Ec/Nt (UL), defining for mobility (CDMA) 248
1389
F
fast link adaptation (TD-SCDMA) 803
fast link adaptation (UMTS) 574
favourite views 62
feeder
assigning (CDMA) 637
assigning (GSM) 281
assigning (TD-SCDMA) 746
assigning (UMTS) 515
defining cables 161
defining length (CDMA) 637
defining length (TD-SCDMA) 746
length, defining (GSM) 281
length, defining (LTE) 855
length, defining (UMTS) 515, 521
length, defining (WiMAX) 1044
1390
AT332_UMR_E0
G
gain
defining antenna 153
Geo explorer 46
geographic export zone
creating 68
creating (CDMA) 666
creating (GSM) 315
creating (LTE) 894
creating (TD-SCDMA) 780
creating (UMTS) 554
creating (WiMAX) 1071
global network settings
modifying (CDMA) 725
modifying (TD-SCDMA) 830
global network settings (CDMA) 724
global network settings (GSM) 504
global network settings (TD-SCDMA) 829
global network settings (UMTS) 613
global transmitter parameters
modifying (UMTS) 614
GPRS/EGPRS coding schemes coverage prediction (GSM) 443
GPRS/EGPRS equipment
coding scheme thresholds, adapting (GSM) 498
coding scheme throughput graphs, displaying (GSM) 498
terminals, assigning to (GSM) 497
transmitters, assigning to (GSM) 497
grid of beams (GOB) smart antenna model (TD-SCDMA) 831
H
handoff status
coverage prediction (CDMA) 665
handover status
coverage prediction (UMTS) 548
happy bit (UMTS) 576
HCS layers
defining (GSM) 484
selecting (GSM) 280
HIDD_COMMON_SERVICE_PP 241
HIDD_IMAGE_PP 117
HIDD_MAPLAYER_GRAPHIC_PP 136
histogram
displaying coverage prediction statistics 214
PN offsets (CDMA) 683
scrambling code (TD-SCDMA) 796
scrambling code (UMTS) 569
viewing optimisation results (ACP) 1381
hopping gain
advanced modelling (GSM) 504
hot spot zone
explanation 68
population statistics 214
population statistics (3GPP) 999
population statistics (3GPP2) 1023
using to display coverage prediction report 68
HSDPA
activating (TD-SCDMA) 743
activating (UMTS) 518
bearer selection, explanation 803
bearer selection, explanation (UMTS) 574
configuring (TD-SCDMA) 743
configuring (UMTS) 518
coverage prediction 778
coverage prediction (UMTS) 549
editing user equipment category 838
scheduler algorithm 519
scheduler algorithm (TD-SCDMA) 743
template 34
terminal, enabling 254
user equipment category 252, 254
user equipment category, editing (UMTS) 620
HSDPA radio bearer
defining (TD-SCDMA) 836
defining (UMTS) 615
HSDPA schedulers
defining 621
HSN
domains, defining (GSM) 344
1391
I
idle power gain, defining for EV-DO cells (CDMA) 635
indoor coverage
activating in AS analysis (CDMA) 668
activating in coverage prediction (TD-SCDMA) 764, 765, 766, 767,
768, 769, 797
1392
J
JD, see "joint detection"
joint detection factor
defining in site equipment (TD-SCDMA) 837
L
label 53
Lambert Conformal-Conic projection 41
layers 51
legend
adding object type 54
co-planning, displaying window in (UMTS) 606
displaying 60
displaying Legend window 60
displaying window in co-planning (CDMA) 717
displaying window in co-planning (LTE) 954
displaying window in co-planning (TD-SCDMA) 824
displaying window in co-planning (WiMAX) 1129
printing Legend window 94
legend, displaying (CDMA) 666
legend, displaying (GSM) 314
legend, displaying (LTE) 894
legend, displaying (TD-SCDMA) 780
legend, displaying (UMTS) 553
AT332_UMR_E0
M
macro-diversity gain
clutter class, displaying per (CDMA) 731
clutter class, displaying per (UMTS) 623
map
centring on a selected object 61, 62
exporting as image 70
favourite views 62
measuring distances 65
moving 60
saving as image 68
map scale
displaying 59
Map toolbar 110
master carrier (TD-SCDMA) 785
masthead amplifier, see "TMA"
matrix, see "path loss matrix"
maximum UL load factor (CDMA) 635
measurement units, setting 42
measuring distances on the map 65
MIMO
adaptive MIMO switch (LTE) 973
adaptive MIMO switch (WiMAX) 1149
collaborative MIMO (LTE) 973
collaborative MIMO (WiMAX) 1149
maximum ratio combining (WiMAX) 1148
MU-MIMO (LTE) 973
MU-MIMO (WiMAX) 1149
number of antenna ports, defining (LTE) 847
number of antennas, defining (WiMAX) 1039
receive diversity (LTE) 972
receive diversity (UMTS) 621
space-time transmit diversity (WiMAX) 1148
space-time transmit diversity gains (WiMAX) 1141
spatial multiplexing (LTE) 972
spatial multiplexing (UMTS) 621
spatial multiplexing (WiMAX) 1148
spatial multiplexing gains (LTE) 967
spatial multiplexing gains (WiMAX) 1141
N
Neighbour Planning 223
3GPP Networks 1005
3GPP2 Networks 1028
Intra-technology Neighbours (CDMA) 674
Intra-technology Neighbours (GSM) 322
Intra-technology Neighbours (LTE) 904
Intra-technology Neighbours (TD-SCDMA) 788
Intra-technology Neighbours (UMTS) 560
Intra-technology Neighbours (WiMAX) 1083
network
global parameters (CDMA) 724
global parameters (TD-SCDMA) 829
1393
O
objectives of ACP optimisation
CDMA 698
GSM 468
LPWA 1284
LTE 937
UMTS 589
Wi-Fi 1217
WiMAX 1113
objects
changing transparency 53
deleting 50
displaying 50
displaying properties 51
grouping 94
hiding 50
label 53
tip text 54
visibility scale 53
Okumura-Hata model 178, 179
Okumura-Hata propagation model 178, 179
assigning environment formulas 178
creating environment formula 179
defining default environment formula 178
modifying environment formula 179
taking diffraction into account 178
optimisation
ACP optimisation parameters, defining 1320
1394
P
packet throughput per timeslot coverage prediction (GSM) 446
Page Setup, see "printing"
Panoramic window 61
Parameters explorer 46
path loss calculation
radial 173, 175
path loss matrices
adjusting using CW measurements 196
tuning using measurement data 194, 195
path loss matrix
calculation process (LTE) 186
exporting 201
resolution (CDMA) 639
resolution (GSM) 292, 502
resolution (LTE) 856
resolution (TD-SCDMA) 748
resolution (UMTS) 523
resolution (WiMAX) 1045
AT332_UMR_E0
storing 190
P-CCPCH pollution coverage prediction (TD-SCDMA) 766
permutation zone
creating (WiMAX) 1138
permutation zone (WiMAX) 1138
permutation zone permbases
audit of plan (WiMAX) 1099
automatically allocating (WiMAX) 1091
permutation zone permbases (WiMAX) 1091
allocating manually 1092
physical cell IDs
allocating manually (LTE) 913
audit of plan (LTE) 919
automatically allocating (LTE) 911
defining available (LTE) 907, 908
displaying allocation (LTE) 915
displaying on transmitter (LTE) 916
domains and groups, creating (LTE) 907, 908
grouping transmitters by (LTE) 917
using Find on Map with (LTE) 915
physical cell IDs (LTE) 911
pilot channel, power control for EV-DO (CDMA) 686
pilot pollution coverage prediction (CDMA) 663
pilot pollution coverage prediction (UMTS) 546
pilot power
reconfiguration with ACP 1340
reconfiguration with ACP (CDMA) 1341
reconfiguration with ACP (GSM) 1340
reconfiguration with ACP (UMTS) 1340
reconfiguration with ACP (WiMAX) 1342
pilot reception analysis (Ec/I0) based on test mobile data path
(CDMA) 708
pilot reception analysis (Ec/I0) based on test mobile data path
(UMTS) 599
pilot signal quality coverage prediction (CDMA) 657
pilot signal quality coverage prediction (TD-SCDMA) 770
pilot signal quality coverage prediction (UMTS) 541
Planet
importing antennas 155
PN offsets
audit of plan (CDMA) 681
automatically allocating (CDMA) 678
defining constraint costs (CDMA) 678
defining per cell (CDMA) 634
displaying allocation (CDMA) 681
displaying on transmitter (CDMA) 682
domain, defining per cell (CDMA) 634
grouping transmitters by (CDMA) 682
histogram (CDMA) 683
interference zone coverage prediction (CDMA) 683
manually allocating (CDMA) 680
reuse distance, defining per cell (CDMA) 634
using Find on Map with (CDMA) 682
PN offsets (CDMA) 677
point analysis
opening Point Analysis Tool window 201
shadowing, calculating 204
starting 201
Point Analysis window
active set analysis of simulation (CDMA) 696
active set analysis of simulation (UMTS) 587
Interference view (CDMA) 669
Interference view (GSM) 439
Interference view (LPWA) 1276
Interference view (LTE) 896, 897
Interference view (Wi-Fi 1192
Interference view (WiMAX) 1073
printing 94
Profile view (CDMA) 642
Profile view (GSM) 296
Profile view (LPWA) 1257
Profile view (LTE) 859
Profile view (TD-SCDMA) 751
Profile view (UMTS) 526
Profile view (Wi-Fi) 1175
Profile view (WiMAX) 1048
Reception tab (CDMA) 667
Reception tab (LPWA) 1275
Reception tab (LTE) 894
Reception tab (TD-SCDMA) 781
Reception tab (UMTS) 554
Reception tab (Wi-Fi) 1191
Reception tab (WiMAX) 1072
Reception view (GSM) 315
polygon
deleting polygon filter 70
using as computation zone 69
using as filter 66
population statistics
including in report 214
including in report (3GPP) 999
including in report (3GPP2) 1023
integrable data 214
integrable data (3GPP) 999
integrable data (3GPP2) 1023
power
maximum power in cells, defining (CDMA) 634
maximum power in cells, defining (UMTS) 517
maximum power transmitted by EV-DO cells, defining (CDMA)
635
1395
power, defining
defining DwPTS power in cells (TD-SCDMA) 742
defining maximum power in cells (TD-SCDMA) 742
defining other CCH power in cells (TD-SCDMA) 742
defining P-CCPCH power in cells (TD-SCDMA) 742
defining UpPTS power (TD-SCDMA) 254
PRACH RSIs
allocating manually (LTE) 915
audit of plan (LTE) 922
automatically allocating (LTE) 914
preamble analysis based on drive test data path (WiMAX) 1122
preamble index (WiMAX) 1040
preamble indexes
allocating manually (WiMAX) 1091
audit of plan (WiMAX) 1097
automatically allocating (WiMAX) 1089
defining available (WiMAX) 1086
displaying allocation (WiMAX) 1093
displaying on transmitter (WiMAX) 1094
domains and groups, creating (WiMAX) 1086
grouping transmitters by (WiMAX) 1094
using Find on Map with (WiMAX) 1093
preamble indexes (WiMAX) 1089
preamble power
reconfiguration with ACP 1340
predictions
overview 204
printing
antenna patterns 94, 157
coverage prediction results (CDMA) 666
coverage prediction results (GSM) 315
coverage prediction results (LTE) 894
coverage prediction results (TD-SCDMA) 780
coverage prediction results (UMTS) 553
coverage prediction results (WiMAX) 1071
CW Measurement Analysis Tool 94
data tables and reports 90
defining print layout 91
docking windows 94
Legend window 94
Point Analysis window 94
print preview 93
recommendations 91
Test Mobile Data Analysis Tool 94
Profile 173, 175
Systematic extraction 173, 175
profile
radial extraction 173, 175
projection coordinate system 40
Lambert Conformal-Conic projection 41
Universal Transverse Mercator projection 41
propagation model
ACP, natively supported 1314
ACP, not natively supported 1314
ACP, using precalculated path loss matrices with 1315, 1316
ACP, using with 1314
assigning a default model for predictions 188
1396
Q
QoS Class, defining (WiMAX) 1063
quality analysis predictions (ACP)
CDMA 700
GSM 470
LPWA 1286
LTE 939
UMTS 592
Wi-Fi 1219
WiMAX 1115
quality indicator coverage prediction (CDMA) 661
quality indicator coverage prediction (LTE) 891
quality indicator coverage prediction (UMTS) 544
quality indicator coverage prediction (WiMAX) 1070
quality indicators
defining (LTE) 964
defining (WiMAX) 1139
quality parameters (ACP)
CDMA 699
GSM 468
LPWA 1285
LTE 937
UMTS 590
Wi-Fi 1217
WiMAX 1113
R
R99 radio bearer
creating (UMTS) 615
defining (TD-SCDMA) 835
AT332_UMR_E0
1397
1398
S
Sakagami extended propagation model 185
scale level, choosing 61
SC-FDMA, definition (LTE) 843
scheduler
choosing the HSDPA scheduler algorithm (TD-SCDMA) 743
explanation of scheduling technique (TD-SCDMA) 803
explanation of scheduling technique (UMTS) 575
HSDPA scheduler algorithm, selecting 519
scrambling codes
allocating, automatically (UMTS) 564
allocating, manually (UMTS) 566
audit of plan (TD-SCDMA) 794
audit of plan (UMTS) 566
automatic allocation costs (TD-SCDMA) 793
automatically allocating (TD-SCDMA) 792
constraint costs, defining (UMTS) 564
defining constraint costs (TD-SCDMA) 791
defining exceptional pairs (CDMA) 677
defining exceptional pairs (TD-SCDMA) 791
defining format (TD-SCDMA) 790
defining relativity clusters (TD-SCDMA) 791
displaying allocation (TD-SCDMA) 795
displaying allocation (UMTS) 567
displaying on transmitter (TD-SCDMA) 795
displaying on transmitter (UMTS) 568
exceptional pairs, defining (UMTS) 563
Find on Map, finding with (UMTS) 567
format, defining (UMTS) 563
grouping transmitters by (TD-SCDMA) 796
grouping transmitters by (UMTS) 568
histogram (TD-SCDMA) 796
histogram (UMTS) 569
AT332_UMR_E0
service area (Eb/Nt) uplink based on test mobile data path (UMTS)
599
services
creating (Multi-RAT) 247
creating (WiMAX) 1062
definition (CDMA) 685
definition (GSM) 326
definition (LTE) 925
definition (TD-SCDMA) 801
definition (UMTS) 571
definition (WiMAX) 1103
modifying (Multi-RAT) 247
modifying (WiMAX) 1062
parameters used in predictions (Multi-RAT) 241
parameters used in predictions (WiMAX) 1062
priority, defining (UMTS) 245, 247
soft handover, activating (UMTS) 245
shadowing 204, 205
point analysis, calculating in 204
shadowing (CDMA) 725, 730
shadowing (GSM) 506
shadowing (LTE) 974
shadowing (TD-SCDMA) 839
shadowing (UMTS) 613, 623
shadowing (Wi-Fi) 1241
shadowing (WiMAX) 1150
shadowing margin
clutter class, displaying per (CDMA) 731
clutter class, displaying per (GSM) 506
clutter class, displaying per (LTE) 975
clutter class, displaying per (TD-SCDMA) 839
clutter class, displaying per (UMTS) 623
clutter class, displaying per (WiMAX) 1150
signal level coverage
1399
1400
AT332_UMR_E0
T
T_Drop, defining per cell (CDMA) 634
table columns
formatting 79
Table toolbar 111
tables, see "data tables"
TDD frame configuration (LTE) 851
TD-SCDMA
template 34
template
coverage prediction, using as 209
templates 34
3GPP multi-RAT 34
CDMA2000 1xRTT 1xEV-DO 34
GSM/GPRS/EGPRS 34
LPWA 34
LTE 34
TD-SCDMA 34
UMTS HSDPA HSUPA 34
Wi-Fi 34
WiMAX 34
terminal
creating (UMTS) 254
creating (WiMAX) 1063
definition (CDMA) 685
definition (GSM) 327
definition (LTE) 925
definition (TD-SCDMA) 801
definition (UMTS) 571
definition (WiMAX) 1103
HSDPA, enabling 254
HSUPA, terminal 254
modifying (UMTS) 254
modifying (WiMAX) 1063
Test Mobile Data Analysis Tool
printing 94
test mobile data path
analysing variations (CDMA) 710
analysing variations (GSM) 480
coverage by C/I, using for (GSM) 478
coverage by signal level, using for (GSM) 478
coverage prediction, using in (GSM) 478
1401
1402
AT332_UMR_E0
U
ue categories
defining (LTE) 970
UL load factor (CDMA) 636
UMTS HSDPA HSUPA
template 34
UMTS schedulers
scheduling methods 620
Universal Transverse Mercator projection 41
uplink load factor, setting (TD-SCDMA) 770
uplink load factor, setting (UMTS) 541
uplink noise rise, setting (LTE) 879
uplink noise rise, setting (WiMAX) 1064
uplink traffic channel coverage prediction (TD-SCDMA) 772
UpPCH interference coverage prediction (TD-SCDMA) 776
user configuration 103
coverage prediction, exporting 210
creating 104
exporting 104
importing 104
user densities
using instead of user profiles (LTE) 977
using instead of user profiles (WiMAX) 1152
user density traffic map
creating from sector traffic maps (GSM) 263
user distribution (CDMA) 685
user distribution (TD-SCDMA) 801
user distribution, Monte Carlo-based (UMTS) 571
user distribution, Monte-Carlo-based (GSM) 334
user distribution, Monte-Carlo-based (UMTS) 265
user equipment category, HSDPA 252, 254
user equipment category, HSDPA, editing 838
user equipment category, HSDPA, editing (UMTS) 620
user equipment category, HSUPA 254
user equipment category, HSUPA, editing 838
user equipment category, HSUPA, editing (UMTS) 620
user profile
creating (GSM) 254
modifying (GSM) 254
V
Vector Editor toolbar 111
Vienna 93 model 180, 181
views
creating 108
visibility scale 53
W
Walsh codes
orthogonality factor, default (CDMA) 725
Wi-Fi 1165
template 34
Wi-Fi, definition 1165
WiMAX 1035
cyclic prefix ratio 1134, 1138
frame duration 1134
glossary 1160
template 34
WiMAX radio bearers 1103, 1139
WiMAX schedulers
defining 1145
scheduling methods 1143
WiMAX, definition 1035
Windows toolbar 111
wireless local loop propagation model 183
WLL (Wireless Local Loop) propagation model 183
X
XML
importing data tables from 90
Z
zones
creating 68
zooming
choosing a scale 61
in and out 60
in on a specific area 60
1403
1404
Radio Planning
New from template (Ctrl+N)
Station template
New transmitter
Save (Ctrl+S)
Import file
Calculate (F7)
Stop calculations
Cut (Ctrl+X)
Copy (Ctrl+C)
Paste (Ctrl+V)
Undo (Ctrl+Z)
New repeater
Redo (Ctrl+Y)
Help (F1)
Map
Channel arrangement
Refresh (F5)
Export report
Pointer (Esc)
Stop calculations
New node
New segment
Vector Editor
New vector layer
Vector layer to edit
New polygon
New rectangle
New line
Windows
Draw points
Network tab
Combine polygons
Geo tab
Parameters tab
Event viewer
Split a polygon
Panoramic window
Legend window
Site configuration
Toolbars
Table
Import data
Export data
Display statistics
Fill up (Ctrl+U)
Display columns
Align left
Align centre
Align right
Bold
Italic
Advanced filter
Find
Remove filter
Replace
Keyboard Shortcuts
You can access some of the more common functions in Atoll by using keyboard shortcuts.
General
You can use the following shortcuts anywhere in Atoll.
Ctrl+N
Ctrl+Z
Ctrl+Shift+N
Ctrl+Y
Open a file
Ctrl+O
Calculate
F7
Ctrl+P
Force calculations
Ctrl+F7
Ctrl+S
Alt+F8
On-line help
F1
Ctrl+E
Ctrl+F
Ctrl+I
Refresh display
F5
Ctrl+Shift+I
Map Shortcuts
You can use the following shortcuts in the map window.
Next view
Alt+Right Arrow
Zoom on area
Ctrl+W
Previous view
Alt+Left Arrow
Zoom in
Ctrl++
Move map
Ctrl+D
Zoom out
Ctrl+-
Find on map
Ctrl+F
Zoom in/out
Ctrl+Q
Copy
Ctrl+C
Fill down
Ctrl+D
Cut
Ctrl+X
Fill up
Ctrl+U
Paste
Ctrl+V
Find
Ctrl+F
Select all
Ctrl+A
Replace
Ctrl+H
Table Shortcuts
You can use the following shortcuts in a table.
Head Office
7 rue des Briquetiers
31700 Blagnac, France
Tel: +33 562 747 210
Fax: +33 562 747 211
AT332_UMR_E0
US Office
China Office
www.forsk.com
November 2016
AT332_UMR_E0
93